From b44d0d3e5c0c907c5c0080a3f1a8339818dd4a69 Mon Sep 17 00:00:00 2001 From: "james.haytko" Date: Mon, 24 Aug 2026 12:08:23 -0500 Subject: [PATCH 01/36] vale dale ppe 11.2 --- .../admin/cmdlets/cmdgetppeserverversion.md | 4 +- .../11.2/admin/hibpupdater.md | 15 +++---- .../admin/manage-policies/manage_policies.md | 2 +- .../11.2/admin/manage-policies/messages.md | 2 +- .../manage-policies/rules/dictionary_rule.md | 2 +- .../11.2/admin/manage-policies/rules/rules.md | 2 +- .../11.2/admin/manage-policies/testpolicy.md | 20 ++++----- .../11.2/admin/manage-policies/usersgroups.md | 6 +-- .../configuring_the_password_policy_client.md | 18 ++++---- .../password_policy_client.md | 13 +++--- .../11.2/admin/ppe_tool.md | 27 ++++++----- .../11.2/admin/troubleshooting.md | 4 +- .../11.2/evaluation/conclusion.md | 2 +- .../evaluation/configuring_policy_rules.md | 12 ++--- .../creating_a_password_policy.md | 3 +- .../policy_templates.md | 7 +-- .../evaluation/enforcing_multiple_policies.md | 6 +-- .../11.2/evaluation/evaluation_overview.md | 8 ++-- .../improving_the_password_policy.md | 8 ++-- .../11.2/evaluation/installforeval.md | 2 +- .../11.2/evaluation/preparing_the_computer.md | 13 +++--- .../evaluation/testing_the_password_policy.md | 32 ++++++------- docs/passwordpolicyenforcer/11.2/index.md | 2 +- .../11.2/installation/installationclient.md | 4 +- .../11.2/installation/installationserver.md | 2 +- .../11.2/web-overview/configuration.md | 6 +-- .../web-overview/editing_html_templates.md | 45 ++++++++++--------- .../11.2/web-overview/installationweb.md | 21 +++++---- .../11.2/web-overview/securing_web.md | 8 ++-- .../11.2/web-overview/using_web.md | 18 ++++---- .../11.2/web-overview/web_overview.md | 2 +- 31 files changed, 158 insertions(+), 158 deletions(-) diff --git a/docs/passwordpolicyenforcer/11.2/admin/cmdlets/cmdgetppeserverversion.md b/docs/passwordpolicyenforcer/11.2/admin/cmdlets/cmdgetppeserverversion.md index cf879a4d71..63f38e9e3a 100644 --- a/docs/passwordpolicyenforcer/11.2/admin/cmdlets/cmdgetppeserverversion.md +++ b/docs/passwordpolicyenforcer/11.2/admin/cmdlets/cmdgetppeserverversion.md @@ -16,8 +16,8 @@ The **Get-PPEServerVersion** cmdlet returns the Password Policy Enforcer server **-DC** `<_string_>` -Name of the domain controller running the PPE Server. If not specified, the current domain -controller is used. +Name of the domain controller running the PPE Server. If you don't specify one, PPE uses the current +domain controller. **-Local** `<_SwitchParameter_>` diff --git a/docs/passwordpolicyenforcer/11.2/admin/hibpupdater.md b/docs/passwordpolicyenforcer/11.2/admin/hibpupdater.md index db986c9188..78d46cbb95 100644 --- a/docs/passwordpolicyenforcer/11.2/admin/hibpupdater.md +++ b/docs/passwordpolicyenforcer/11.2/admin/hibpupdater.md @@ -26,7 +26,7 @@ location. If you copy and store the HIBP database locally on the Domain Controllers: - The HIBP database takes up additional space on the machine where it is copied. (Aproximetly 13GB but subject to change) -- If doing local the database needs to be on every Domain Controller in the same location as specified in the Rule. +- If you use a local database, place it on every domain controller in the same location specified in the rule. - A network connection isn't involved and doesn't affect the performance of checking the password against the HIBP database - PPE checks the pending password candidate against the archived hash file locally. If the password hash matches an entry, PPE rejects the pending password change. @@ -37,11 +37,11 @@ If you keep the HIBP database on a Network Share: - Requires a working network connection from the Domain Controllers to the Network Share with Read permissions to check: - The pending password candidate from Domain Controller against the HIBP Database stored on the Network Share, this could affect LSASS/Password Change performance depending on the environment. - HIBP database space isn't required on the domain controllers but on one Network Location. -- At the time of a password change, if the Network Share isn't available, the Domain Controller must assume the hash is okay and the possibility of a known compromised password being accepted. +- At the time of a password change, if the Network Share isn't available, the Domain Controller must assume the hash is okay, which means it could accept a known compromised password. ## Installation and Configuration -The HIBP Updater is installed when you install the Password Policy Enforcer Configuration Console. +Installing the Password Policy Enforcer Configuration Console also installs the HIBP Updater. :::info Only run this from one server. @@ -71,8 +71,7 @@ Netwrix website. ![HIBP Updater](/images/passwordpolicyenforcer/11.2/administration/hibpupdater.webp) :::warning -Ensure the initial update of the database occurs during non-office hours. Due to the -size of the hash file, this download takes up a significant amount of CPU and download time. +Schedule the initial database update for non-office hours. Because of the hash file's size, this download uses significant CPU and network resources. ::: @@ -112,9 +111,9 @@ size of the hash file, this download takes up a significant amount of CPU and do - Apply: - - If Website is selected, then clicking **Apply** downloads the HIBP database from the Netwrix + - If you select Website, then clicking **Apply** downloads the HIBP database from the Netwrix website and then processes the database for use by the application - - If File is selected, then clicking **Apply** processes the local copy of the (manually obtained) database for use by the application + - If you select File, then clicking **Apply** processes the local copy of the (manually obtained) database for use by the application ### Hash File Replication @@ -135,7 +134,7 @@ to receive hash file updates, then use the Sysvol share for file replication and scheduled task to copy the file to a local folder. :::warning -%SystemRoot%. hash files should only be read from a local disk. Using shared hash files +%SystemRoot%. Only read hash files from a local disk. Using shared hash files degrades performance, and could jeopardize security. ::: diff --git a/docs/passwordpolicyenforcer/11.2/admin/manage-policies/manage_policies.md b/docs/passwordpolicyenforcer/11.2/admin/manage-policies/manage_policies.md index cde1f80b19..2b1b9e1cb1 100644 --- a/docs/passwordpolicyenforcer/11.2/admin/manage-policies/manage_policies.md +++ b/docs/passwordpolicyenforcer/11.2/admin/manage-policies/manage_policies.md @@ -42,7 +42,7 @@ Click **Test Policy** to check if Password Policy Enforcer's current configurati ## Set policy priorities -Policy priorities help Password Policy Enforcer resolve [policy assignment conflicts](usersgroups.md#policy-assignment-conflicts). If more than one policy is assigned to a user, and PPE can't decide which policy to enforce using the other conflict resolution rules, then PPE always enforces the policy with the highest priority. +Policy priorities help Password Policy Enforcer resolve [policy assignment conflicts](usersgroups.md#policy-assignment-conflicts). If a user has more than one assigned policy, and PPE can't decide which policy to enforce using the other conflict resolution rules, then PPE always enforces the policy with the highest priority. Click **Set priorities** to view or modify policy priorities. This button is only visible if you have more than one password policy. diff --git a/docs/passwordpolicyenforcer/11.2/admin/manage-policies/messages.md b/docs/passwordpolicyenforcer/11.2/admin/manage-policies/messages.md index e321ffd2ea..c0ade528ef 100644 --- a/docs/passwordpolicyenforcer/11.2/admin/manage-policies/messages.md +++ b/docs/passwordpolicyenforcer/11.2/admin/manage-policies/messages.md @@ -28,7 +28,7 @@ The [Password Policy Client](../password-policy-client/password_policy_client.md - PPE uses the **Password policy** template for the message that users see while they change their password. This message explains the password policy. It can also display a "live" policy to show users which rules their password complies with as they type. - PPE uses the **Rejection reason** template for the message it shows when it rejects a password. This message tells users which rules their password doesn't comply with. -- PPE also uses the **Generic rejection** template when a password is rejected, but only if it doesn't know the rejection reason. This most commonly happens when a [Windows password policy](../../installation/disable_windows_rules.md) rejects the password. This message doesn't tell users which rules their password doesn't comply with. +- PPE also uses the **Generic rejection** template when it rejects a password, but only if it doesn't know the rejection reason. This most commonly happens when a [Windows password policy](../../installation/disable_windows_rules.md) rejects the password. This message doesn't tell users which rules their password doesn't comply with. ### Password policy template diff --git a/docs/passwordpolicyenforcer/11.2/admin/manage-policies/rules/dictionary_rule.md b/docs/passwordpolicyenforcer/11.2/admin/manage-policies/rules/dictionary_rule.md index 159a8d563b..647d5e82b0 100644 --- a/docs/passwordpolicyenforcer/11.2/admin/manage-policies/rules/dictionary_rule.md +++ b/docs/passwordpolicyenforcer/11.2/admin/manage-policies/rules/dictionary_rule.md @@ -55,7 +55,7 @@ Increase the tolerance if [testing](../testpolicy.md#by-user) shows that this ru Click **Add dictionary** if you want PPE to use a secondary dictionary file. This is useful if you want to keep your own words in a separate file, or if you need different settings for the second file. Clicking **Add dictionary** displays a second group of identical configuration settings for the secondary file. :::tip -A secondary dictionary can be combined with the [passphrase](../passphrases.md) feature to enforce a password policy that allows dictionary words in passphrases, while still rejecting certain words such as the organization's name, seasons, local sporting teams, etc. Configure the passphrase feature to disable only the primary dictionary file for passphrases, and keep the secondary (smaller) dictionary file enabled for all passwords. +You can combine a secondary dictionary with the [passphrase](../passphrases.md) feature to enforce a password policy that allows dictionary words in passphrases, while still rejecting certain words such as the organization's name, seasons, local sporting teams, etc. Configure the passphrase feature to disable only the primary dictionary file for passphrases, and keep the secondary (smaller) dictionary file enabled for all passwords. ::: ## Dictionary file replication diff --git a/docs/passwordpolicyenforcer/11.2/admin/manage-policies/rules/rules.md b/docs/passwordpolicyenforcer/11.2/admin/manage-policies/rules/rules.md index 9aa8f7e9c7..f67ce18b37 100644 --- a/docs/passwordpolicyenforcer/11.2/admin/manage-policies/rules/rules.md +++ b/docs/passwordpolicyenforcer/11.2/admin/manage-policies/rules/rules.md @@ -51,7 +51,7 @@ Some rules have a **Detect character substitution** checkbox. PPE tests password Some rules have a **Tolerance** dropdown. The tolerance controls how strictly PPE enforces the rule. -Tolerance typically refers to the maximum allowable number of consecutive matching characters in the password and some other parameter. Password Policy Enforcer rejects a password if it exceeds the specified tolerance. For example, the logon name "mary**jones**", and the password "**Jones**town" contain five consecutive matching characters (shown in bold). Password Policy Enforcer rejects this password if the tolerance for the User Logon Name rule is four or lower, and accepts it if the tolerance is five or higher. +Tolerance is the maximum number of consecutive matching characters allowed between the password and another parameter. Password Policy Enforcer rejects a password if it exceeds the specified tolerance. For example, the logon name "mary**jones**", and the password "**Jones**town" contain five consecutive matching characters (shown in bold). Password Policy Enforcer rejects this password if the tolerance for the User Logon Name rule is four or lower, and accepts it if the tolerance is five or higher. Some rules have an Auto tolerance option. Setting the tolerance to Auto tells Password Policy Enforcer to reject only passwords that contain the entire comparison parameter. This is useful when the length of the comparison parameter is unknown. For example, if you want PPE to reject passwords that contain the user's entire logon name, then you can't specify a fixed tolerance unless all logon names are the same length. Setting the tolerance to Auto lets Password Policy Enforcer calculate an appropriate tolerance during the password change. diff --git a/docs/passwordpolicyenforcer/11.2/admin/manage-policies/testpolicy.md b/docs/passwordpolicyenforcer/11.2/admin/manage-policies/testpolicy.md index b768040759..1002e08218 100644 --- a/docs/passwordpolicyenforcer/11.2/admin/manage-policies/testpolicy.md +++ b/docs/passwordpolicyenforcer/11.2/admin/manage-policies/testpolicy.md @@ -6,7 +6,7 @@ sidebar_position: 60 # Test Policy -You can quickly test your Password Policy Enforcer configuration by simulating a password change. +You can test your Password Policy Enforcer configuration by simulating a password change. Click **Test Policy** from the Configuration Console dashboard or when you are setting up a policy. Test policy opens in a separate window. Remember to **Save** your rules and changes before testing. @@ -28,8 +28,8 @@ up a policy. ![Failing Password](/images/passwordpolicyenforcer/11.2/administration/testuserfail.webp) -The entered password is failing in this example, due to not meeting the length requirement. There is -a red x indicating the failure. You can hover over the requirements to see the rule name. +In this example, the password fails because it doesn't meet the length requirement. A red x +indicates the failure. You can hover over the requirements to see the rule name. In this example, the password passes. Notice the green check beside the entered password. @@ -37,8 +37,8 @@ In this example, the password passes. Notice the green check beside the entered Expand the **View log** for details: -- Computer the configuration was read from. -- Policy was assigned to the user, and why. +- The computer from which Password Policy Enforcer read the configuration. +- The policy Password Policy Enforcer assigned to the user, and why. - Dictionary word or keyboard pattern matched with the password. - Errors or warnings occurred during testing. @@ -62,7 +62,7 @@ up a policy. **Step 4 –** **Browse** to the text file containing the passwords to test. Processing is faster if the file isn't on a shared drive. -**Step 5 –** Click **Test passwords**. The **Statistics** are displayed. +**Step 5 –** Click **Test passwords**. The **Statistics** appear. ![Test results](/images/passwordpolicyenforcer/11.2/administration/testbulkresult.webp) @@ -89,13 +89,13 @@ You can use the **Report settings** to customize the report: - Policy testing simulates a password change, but it may not always reflect what happens when a user changes their password. A password change may yield different results to a policy test because: -- Policy testing doesn't simulate the Windows password policy rules. If the Windows password rules - are enabled, then Windows may reject a password even though it complies with all the Password +- Policy testing doesn't simulate the Windows password policy rules. If you enable the Windows + password rules, then Windows may reject a password even though it complies with all the Password Policy Enforcer rules. - Policy testing doesn't enforce the Minimum Age rule. - Policy testing doesn't enforce the History rule. -- Policy testing enforces the password policy even if Password Policy Enforcer or the assigned - policy is disabled. Use this to test your configuration before enabling Password Policy +- Policy testing enforces the password policy even if you disable Password Policy Enforcer or the + assigned policy. Use this to test your configuration before enabling Password Policy Enforcer, or a new password policy. - Policy testing occurs on the computer that the Configuration Console is running on. If the Configuration Console is connected to a remote domain configuration, then it may not find the dictionary file on diff --git a/docs/passwordpolicyenforcer/11.2/admin/manage-policies/usersgroups.md b/docs/passwordpolicyenforcer/11.2/admin/manage-policies/usersgroups.md index 9ec3de5ec5..dd1fb776f0 100644 --- a/docs/passwordpolicyenforcer/11.2/admin/manage-policies/usersgroups.md +++ b/docs/passwordpolicyenforcer/11.2/admin/manage-policies/usersgroups.md @@ -9,7 +9,7 @@ sidebar_position: 20 Password Policy Enforcer (PPE) uses policy assignments to decide which policy to enforce for a user. You can assign domain policies to users, groups, and containers (Organizational Units, or OUs). You can assign local policies only to users. See [Domain and Local Policies](../../installation/domain_and_local_policies.md) to learn how domain and local policies differ. :::warning -Domain policy assignments for users and groups reference the object's Security Identifier (SID), so they remain valid even if the user or group is renamed. Local policy assignments reference the username directly, so renaming the user invalidates the assignment. +Domain policy assignments for users and groups reference the object's Security Identifier (SID), so they remain valid even if you rename the user or group. Local policy assignments reference the username directly, so renaming the user invalidates the assignment. ::: ## Add a policy assignment @@ -44,7 +44,7 @@ When you assign a policy to an OU, PPE enforces the policy for all users in the ## Policy assignment conflicts -A policy assignment conflict occurs when more than one policy is assigned to a user. Password Policy Enforcer can resolve these conflicts and choose one policy for each user. +A policy assignment conflict occurs when you assign more than one policy to a user. Password Policy Enforcer can resolve these conflicts and choose one policy for each user. PPE first tries to resolve a policy assignment conflict by examining the assignment type. Assignments by user take precedence over assignments by group, and assignments by group take precedence over assignments by container. For example, if you assign Policy A to a user by group, and Policy B to the same user by container, then PPE enforces Policy A because assignments by group take precedence over assignments by container. @@ -60,7 +60,7 @@ Password Policy Enforcer enforces the default policy for any user who doesn't ha If Password Policy Enforcer has only one policy, and that policy is also the default policy, then PPE enforces the policy for all users. If you want to deploy a single policy gradually, don't make it the default until the deployment is complete. ::: -## Check which policy is enforced for a user +## Check which policy PPE enforces for a user Use the [**Test Policy by User** feature](testpolicy.md#by-user) to check which policy PPE enforces for a user. Enter a username on the left, and the right pane shows the enforced policy. diff --git a/docs/passwordpolicyenforcer/11.2/admin/password-policy-client/configuring_the_password_policy_client.md b/docs/passwordpolicyenforcer/11.2/admin/password-policy-client/configuring_the_password_policy_client.md index 3f13758096..7af2bd92fd 100644 --- a/docs/passwordpolicyenforcer/11.2/admin/password-policy-client/configuring_the_password_policy_client.md +++ b/docs/passwordpolicyenforcer/11.2/admin/password-policy-client/configuring_the_password_policy_client.md @@ -10,7 +10,7 @@ The Password Policy Client is self-configuring and doesn't require manual config cases. See the [Install Password Policy Enforcer Client](/docs/passwordpolicyenforcer/11.2/installation/installationclient.md) topic for additional details. You may need to manually configure the Password Policy Client if: -- You want to install it in a disabled state to be enabled later. +- You want to install it in a disabled state and enable it later. - You want to change the display settings for small screens. - Password Policy Client displays policy messages in the wrong language. - Default communication settings aren't suitable (for example, if you change the default Password @@ -18,7 +18,7 @@ additional details. You may need to manually configure the Password Policy Clien Password Policy Enforcer includes an administrative template to help configure the Password Policy Client. You can use Active Directory GPOs to configure many computers, or the Local Group Policy -Editor to configure one computer. The Password Policy Client configuration is stored in the +Editor to configure one computer. Windows stores the Password Policy Client configuration in the HKLM\SOFTWARE\Policies\ANIXIS\Password Policy Client\ registry key. **Install the Password Policy Client Administrative Template** @@ -48,7 +48,7 @@ Client. If not, see the topic's section for additional information. **``**, right-click **``** and select **Create a GPO** in this domain and Link it here. -After the GPO is configured, this view is available: +After you configure the GPO, this view is available: ![ppc_configuration3](/images/passwordpolicyenforcer/11.2/administration/ppc_configuration3.webp) @@ -77,12 +77,12 @@ message in a message box to draw attention to the password policy. ![the_password_policy_client_3](/images/passwordpolicyenforcer/11.2/administration/the_password_policy_client_3.webp) -You can change the default display settings to control which user interface elements are hidden, and -the point at which they are hidden. The display of the Password Policy message box is also -configurable. +You can change the default display settings to control which user interface elements the Password +Policy Client hides, and the point at which it hides them. The display of the Password Policy +message box is also configurable. -Follow the steps to change the default display settings for the Password Policy Client on -Windows 10 and 11. +To change the default display settings for the Password Policy Client on +Windows 10 and 11: **Step 1 –** Use the **Group Policy Management Console** (gpmc.msc) to display the GPOs linked at the domain level. @@ -103,6 +103,6 @@ Templates**, **Classic Administrative Templates** (**ADM**), **Password Policy E Group Policy Management Editor. :::note -Information about each option is shown in the Help box. +The Help box shows information about each option. ::: diff --git a/docs/passwordpolicyenforcer/11.2/admin/password-policy-client/password_policy_client.md b/docs/passwordpolicyenforcer/11.2/admin/password-policy-client/password_policy_client.md index 7c3578ecae..26de500987 100644 --- a/docs/passwordpolicyenforcer/11.2/admin/password-policy-client/password_policy_client.md +++ b/docs/passwordpolicyenforcer/11.2/admin/password-policy-client/password_policy_client.md @@ -6,13 +6,12 @@ sidebar_position: 50 # Password Policy Client -The Password Policy Client helps users to choose a compliant password. Detailed information is -provided if their new password is rejected. +The Password Policy Client helps users to choose a compliant password. If Password Policy Enforcer +rejects a new password, the Password Policy Client provides detailed information. -The Password Policy Client is optional. If it isn't installed, the -[Similarity Rule](/docs/passwordpolicyenforcer/11.2/admin/manage-policies/rules/similarity_rule.md) can't be enforced. Users only see the default Windows error -message if their password is rejected, not the detailed help they receive from the Password Policy -Client. +The Password Policy Client is optional. If it isn't installed, Password Policy Enforcer can't enforce +the [Similarity Rule](/docs/passwordpolicyenforcer/11.2/admin/manage-policies/rules/similarity_rule.md). If Password Policy Enforcer rejects a password, users only see the default Windows error +message, not the detailed help they receive from the Password Policy Client. ![the_password_policy_client](/images/passwordpolicyenforcer/11.2/administration/the_password_policy_client.webp) @@ -20,7 +19,7 @@ Client. The Password Policy Client displays the password policy during a password change so that users can see the policy while they choose their password. The Password Policy Client also displays a detailed -rejection message to explain why a password was rejected. Both these messages are customizable. +rejection message to explain why Password Policy Enforcer rejected the password. Both these messages are customizable. :::note The Password Policy Client doesn't modify any Windows system files. It also doesn't send diff --git a/docs/passwordpolicyenforcer/11.2/admin/ppe_tool.md b/docs/passwordpolicyenforcer/11.2/admin/ppe_tool.md index ed70ed2e1b..cc0fd9e66e 100644 --- a/docs/passwordpolicyenforcer/11.2/admin/ppe_tool.md +++ b/docs/passwordpolicyenforcer/11.2/admin/ppe_tool.md @@ -24,7 +24,7 @@ The PPE Tool installs with the default installation of Password Policy Enforcer `C:\Program Files\Netwrix\Password Policy Enforcer\ppetool` folder. After installation, the PPE Tool supports a number of operations related to Password Policy Enforcer functionality, which are described in the following table. :::note -All PPE Tool operations can be executed from the Command Prompt, if run with administrator +You can execute all PPE Tool operations from the Command Prompt if you run them with administrator rights. ::: @@ -42,34 +42,33 @@ shouldn't execute the /e (Export) and /i (Import) operations simultaneously; y | Operation | Operation Name | Operation Description | | --------- | ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| /? | help |
  • Displays Help and exits the application. All other options are ignored.
| +| /? | help |
  • Displays Help and exits the application. The PPE Tool ignores all other options.
| | /m | minimal |
  • Configures the PPE Tool to operate in Minimal mode.
  • This operation strips away all extraneous information (e.g., policy messages, license information, etc.) while importing or exporting to the PPE Tool.
  • By default, the PPE Tool imports and exports all information available (e.g., policy messages, license information, etc.).
| -| /d | domain [in controller] |
  • Configures the PPE Tool to operate in Domain mode.
  • The default controller is localhost.
  • This operation makes PPE Tool work with the LDAP Password Policy Enforcer instance. PPE Tool imports or exports configurations from the local registry.
  • To use this operation , you must run PPE Tool as a domain administrator user. However, this operation can be used on both the domain controller and on any member. If an invalid domain controller is provided as an argument, then the PPE Tool will fail at the import / export stage.
  • This operation is ignored when used to create reports from the file source (present with the /c (Config [in file name]) option). When the PPE Tool starts in a domain environment without the /d (Domain [in controller]) operation, a warning message appears. However, this won't prevent the PPE Tool from operating on a local environment.
| -| /c | config [in file name] |
  • Uses a config file instead of Password Policy Enforcer export when exporting reports (in the case of /i (Import), /h (Human [out file name]), and /r (Report [out file name]).
  • The default file is `config.xml`.
  • This operation defines the input file for the i/ (Import) operation, and thus is necessary for importing files to the PPE Tool. An error message will appear if the /c (Config [in file name]) option is omitted.
  • By default, the /h (Human [out file name]) and /r (Report [out file name]) operations use the Password Policy Enforcer instance as the reporting source. The /c (Config [in file name]) operation should provide the source configuration file as an argument to create reports. If an invalid file name is provided as an argument in this operation, the PPE Tool displays the appropriate error message and exits.
| +| /d | domain [in controller] |
  • Configures the PPE Tool to operate in Domain mode.
  • The default controller is localhost.
  • This operation makes PPE Tool work with the LDAP Password Policy Enforcer instance. PPE Tool imports or exports configurations from the local registry.
  • To use this operation , you must run PPE Tool as a domain administrator user. However, you can use this operation on both the domain controller and on any member. If you provide an invalid domain controller as an argument, the PPE Tool fails at the import / export stage.
  • The PPE Tool ignores this operation when you use it to create reports from the file source (present with the /c (Config [in file name]) option). When the PPE Tool starts in a domain environment without the /d (Domain [in controller]) operation, a warning message appears. However, this won't prevent the PPE Tool from operating on a local environment.
| +| /c | config [in file name] |
  • Uses a config file instead of Password Policy Enforcer export when exporting reports (in the case of /i (Import), /h (Human [out file name]), and /r (Report [out file name]).
  • The default file is `config.xml`.
  • This operation defines the input file for the i/ (Import) operation, and thus is necessary for importing files to the PPE Tool. An error message appears if you omit the /c (Config [in file name]) option.
  • By default, the /h (Human [out file name]) and /r (Report [out file name]) operations use the Password Policy Enforcer instance as the reporting source. The /c (Config [in file name]) operation should provide the source configuration file as an argument to create reports. If you provide an invalid file name as an argument in this operation, the PPE Tool displays the appropriate error message and exits.
| Operations PPE Tool options are as follows: | Task | Task Name | Task Description | | ---- | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| /e | export [out file name] |
  • Exports config data (default) from the Password Policy Enforcer instance to the file.
  • This operations is enabled by default.
  • This operation can't be used with /c (Config [in file name]) or i/ (Import) operations, but can be combined with /h (Human [out file name]).
| -| /i | import |
  • Imports the config file.
  • Imports existing configuration using the input configuration file defined by the /d (Domain [in controller]) . If the /c (Config [in file name]) operation is omitted, the PPE Tool displays an error message and exits.
  • When i/ (Import) is used with the /h (Human [out file name]) or /r (Report [out file name]) operations, the latter is ignored.
  • /d (Domain [in controller]) and /m (Minimal) operations may affect the result of the import.
| -| /h | human [out file name] |
  • Converts the config file to a human-readable format and produces a human-readable report based on the current Password Policy Enforcer instance configuration or the configuration provided by the /d (Domain [in controller]).
  • If no custom file name is provided, the default file name is `config_human_readable.xml`.
| -| /r | report [out file name] |
  • Converts the config file to HTML and produces an HTML report file based on the current Password Policy Enforcer instance configuration or the configuration provided by the /d (Domain [in controller]).
  • Generates the HTML report into `C:\Program Files\Netwrix\Password Policy Enforcer\Report` alongside the .css file.
  • The default files name is `report.html`.
| +| /e | export [out file name] |
  • Exports config data (default) from the Password Policy Enforcer instance to the file.
  • The PPE Tool enables this operation by default.
  • You can't use this operation with the /c (Config [in file name]) or /i (Import) operations, but you can combine it with /h (Human [out file name]).
| +| /i | import |
  • Imports the config file.
  • Imports existing configuration using the input configuration file defined by the /d (Domain [in controller]) . If you omit the /c (Config [in file name]) operation, the PPE Tool displays an error message and exits.
  • When you use /i (Import) with the /h (Human [out file name]) or /r (Report [out file name]) operations, the PPE Tool ignores the latter operation.
  • /d (Domain [in controller]) and /m (Minimal) operations may affect the result of the import.
| +| /h | human [out file name] |
  • Converts the config file to a human-readable format and produces a human-readable report based on the current Password Policy Enforcer instance configuration or the configuration that /d (Domain [in controller]) provides.
  • If you don't provide a custom file name, the default file name is `config_human_readable.xml`.
| +| /r | report [out file name] |
  • Converts the config file to HTML and produces an HTML report file based on the current Password Policy Enforcer instance configuration or the configuration that /d (Domain [in controller]) provides.
  • Generates the HTML report into `C:\Program Files\Netwrix\Password Policy Enforcer\Report` alongside the .css file.
  • The default files name is `report.html`.
| ### PPE Usage Samples This section covers some sample operations usable in either the PPE Tool or in the Command console -(with administrator rights). Each operation can be executed after the following commands have been -executed: +(with administrator rights). You can execute each operation after you run the following commands: C:\Windows/system32>cd.. `C:\`[location of PPE Tool]`>`[operation] -After this location has been accessed in the Command console, enter one of the following commands in -the [operation] variable above to execute a PPE Tool operation in the Command console. +After you access this location in the Command console, enter one of the following commands in +place of [operation] to execute a PPE Tool operation in the Command console. | Action | Operation | Message | | -------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -87,9 +86,9 @@ root elements which name match each file name. Each root tag contains child tags Each tag has the following attributes: - name — Contains the original tag name from the input configuration file. If this attribute is - missed, then the original tag and its value are absent in the human-readable report. + omitted, then the original tag and its value are absent in the human-readable report. - DisplayName — Contains the user-friendly description for the original tag. If this attribute is - missed, then the original tag and its value appear in the report without a description. + omitted, then the original tag and its value appear in the report without a description. The `` tag can also contain the child `` tag. This tag can have an optional attribute 'mode' and this attribute can have the following values: diff --git a/docs/passwordpolicyenforcer/11.2/admin/troubleshooting.md b/docs/passwordpolicyenforcer/11.2/admin/troubleshooting.md index 0d51e3e4ac..4eb319358e 100644 --- a/docs/passwordpolicyenforcer/11.2/admin/troubleshooting.md +++ b/docs/passwordpolicyenforcer/11.2/admin/troubleshooting.md @@ -9,8 +9,8 @@ sidebar_position: 90 This topic contains troubleshooting information for the most common support questions. Contact Netwrix support with any questions. -Password policy assigned to some users is being enforced for all users. Check the Default Policy in -the PPS Properties page. Users must comply with the default policy if no other policy is assigned to +PPE enforces a password policy assigned to some users for all users. Check the Default Policy in +the Password Policy Server (PPS) Properties page. Users must comply with the default policy if no other policy is assigned to them. Select the first (blank) item in the dropdown list if you don't want a default policy. #### Password policy not displayed during password change diff --git a/docs/passwordpolicyenforcer/11.2/evaluation/conclusion.md b/docs/passwordpolicyenforcer/11.2/evaluation/conclusion.md index 02f9c9c8fc..e02b5bdf6d 100644 --- a/docs/passwordpolicyenforcer/11.2/evaluation/conclusion.md +++ b/docs/passwordpolicyenforcer/11.2/evaluation/conclusion.md @@ -11,7 +11,7 @@ Enforcer. This guide is an introduction to Password Policy Enforcer's capabiliti almost any password policy imaginable with Password Policy Enforcer, customize the Password Policy Client messages, and even synchronize passwords with other networks and applications. The [Administration](/docs/passwordpolicyenforcer/11.2/admin/administration_overview.md) topic contains more information to -help you get the most out of Password Policy Enforcer. +help you use Password Policy Enforcer's full capabilities. The [Password Policy Enforcer Web](/docs/passwordpolicyenforcer/11.2/web-overview/web_overview.md) application lets users securely manage their passwords from a web browser, ensuring passwords comply with the password policy, and helping users choose compliant passwords. diff --git a/docs/passwordpolicyenforcer/11.2/evaluation/configuring_policy_rules.md b/docs/passwordpolicyenforcer/11.2/evaluation/configuring_policy_rules.md index 7e1eb4fa07..10d3ac0e13 100644 --- a/docs/passwordpolicyenforcer/11.2/evaluation/configuring_policy_rules.md +++ b/docs/passwordpolicyenforcer/11.2/evaluation/configuring_policy_rules.md @@ -22,7 +22,7 @@ any time by clicking the policy name on the Configuration Console dashboard. Requirement: Password must contain at least seven characters. -This condition is set with the **Length** rule. +You set this condition with the **Length** rule. **Step 1 –** Select **Length**. @@ -35,7 +35,7 @@ the default. Requirement: Password must contain at least one lowercase alpha character. -This condition is set with the **Characters (Complexity)** rule. +You set this condition with the **Characters (Complexity)** rule. **Step 1 –** Select **Characters (Complexity)**. @@ -51,7 +51,7 @@ This condition is set with the **Characters (Complexity)** rule. Password must contain at least one uppercase character. -This condition is set with the **Characters (Granular)** rule. +You set this condition with the **Characters (Granular)** rule. **Step 1 –** Select **Characters (Granular)**. @@ -67,7 +67,7 @@ This condition is set with the **Characters (Granular)** rule. Requirement: Password must not be similar to the user's logon name. -This condition is set with the **Similarity** rule. +You set this condition with the **Similarity** rule. **Step 1 –** Select **Similarity**. @@ -79,7 +79,7 @@ This condition is set with the **Similarity** rule. Requirement: Password must not exist in a dictionary of common passwords. -This condition is set with the **Dictionary** rule. +You set this condition with the **Dictionary** rule. **Step 1 –** Select **Dictionary**. @@ -91,4 +91,4 @@ This condition is set with the **Dictionary** rule. ![Enable the sample dictionary](/images/passwordpolicyenforcer/11.2/evaluation/evaldict.webp) -When you have added all the rules, click **Save** to save your new policy. +When you have added all the rules, click **Save**. diff --git a/docs/passwordpolicyenforcer/11.2/evaluation/creating-a-password-policy/creating_a_password_policy.md b/docs/passwordpolicyenforcer/11.2/evaluation/creating-a-password-policy/creating_a_password_policy.md index 337ced5786..3b2ec0bab8 100644 --- a/docs/passwordpolicyenforcer/11.2/evaluation/creating-a-password-policy/creating_a_password_policy.md +++ b/docs/passwordpolicyenforcer/11.2/evaluation/creating-a-password-policy/creating_a_password_policy.md @@ -24,8 +24,7 @@ getting started with Password Policy Enforcer. **Step 2 –** Click **Add policy**. -**Step 3 –** Enter a unique policy name. Maximum is 32 characters. **Eval Policy** is used for this -example. +**Step 3 –** Enter a unique policy name. Maximum is 32 characters. This example uses **Eval Policy**. **Step 4 –** Select a Policy template or **None** if you are creating your own. For a list of policies see [Policy Templates ](/docs/passwordpolicyenforcer/11.2/evaluation/creating-a-password-policy/policy_templates.md). diff --git a/docs/passwordpolicyenforcer/11.2/evaluation/creating-a-password-policy/policy_templates.md b/docs/passwordpolicyenforcer/11.2/evaluation/creating-a-password-policy/policy_templates.md index 04045959ca..ec9b8cf220 100644 --- a/docs/passwordpolicyenforcer/11.2/evaluation/creating-a-password-policy/policy_templates.md +++ b/docs/passwordpolicyenforcer/11.2/evaluation/creating-a-password-policy/policy_templates.md @@ -21,13 +21,14 @@ most popular regulatory frameworks. - Defense Federal Acquisition Regulation Supplement (DFARS) - Gramm-Leach-Bliley Act (FedRAMP) - Federal Information Security Management Act (FISMA) -- Health Insurance Portability and Accountability Act (HIPPA) – HIPAA Security Rule requires that - organizations must implement procedures for creating, changing, and safeguarding passwords. +- Health Insurance Portability and Accountability Act (HIPPA) – HIPAA Security Rule requires + organizations to implement procedures for creating, changing, and safeguarding passwords. - It also recommends training the workforce on ways to safeguard password information and establish guidelines to create and change passwords in a periodic cycle. - HIPAA doesn’t offer any specific password complexity guidelines. To comply with HIPAA, - organizations are better off following NIST password guidelines. + organizations are better off following National Institute of Standards and Technology (NIST) + password guidelines. - Most of healthcare institutions use the NIST framework. - International Organization for Standardization (ISO/IEC) 27002 – See the diff --git a/docs/passwordpolicyenforcer/11.2/evaluation/enforcing_multiple_policies.md b/docs/passwordpolicyenforcer/11.2/evaluation/enforcing_multiple_policies.md index 6e4c43d1f7..6b0f6520ea 100644 --- a/docs/passwordpolicyenforcer/11.2/evaluation/enforcing_multiple_policies.md +++ b/docs/passwordpolicyenforcer/11.2/evaluation/enforcing_multiple_policies.md @@ -38,8 +38,8 @@ local **Location** depending on your evaluation set up. ![Domain Admins added](/images/passwordpolicyenforcer/11.2/evaluation/evaldomainadmins.webp) -- Members of the Domain Admins group (or the PPETestAdmin user, if not using a domain controller) - must now comply with the Administrators policy. All other users must comply with the Users policy. +- Members of the Domain Admins group (or, if you aren't using a domain controller, the PPETestAdmin + user) must now comply with the Administrators policy. All other users must comply with the Users policy. Users won't notice any difference at this point because the two polices are enforcing identical rules. @@ -72,6 +72,6 @@ should enforce the Eval policy for **PPETestUser**, and the Admins policy for ** :::note The [Set Priorities](/docs/passwordpolicyenforcer/11.2/admin/manage-policies/manage_policies.md#set-policy-priorities) topic contains more information about policy assignments, and how Password Policy Enforcer resolves policy -assignment conflicts that occur when more than one policy is assigned to a user. +assignment conflicts that occur when more than one policy applies to a user. ::: diff --git a/docs/passwordpolicyenforcer/11.2/evaluation/evaluation_overview.md b/docs/passwordpolicyenforcer/11.2/evaluation/evaluation_overview.md index c1f7272970..54b2f68b99 100644 --- a/docs/passwordpolicyenforcer/11.2/evaluation/evaluation_overview.md +++ b/docs/passwordpolicyenforcer/11.2/evaluation/evaluation_overview.md @@ -7,15 +7,15 @@ sidebar_position: 50 # Evaluate Password Policy Enforcer Netwrix Password Policy Enforcer is an advanced password filter for Windows. Use this guide to -quickly install, configure, and test an evaluation version of Password Policy Enforcer. Netwrix +install, configure, and test an evaluation version of Password Policy Enforcer. Netwrix Password Policy Enforcer helps secure your network by ensuring users set strong passwords. When a user enters a password that doesn't comply with the password policy, Password Policy Enforcer -immediately rejects the password and details why the password was rejected. +immediately rejects the password and details why it rejected the password. ![introduction_3](/images/passwordpolicyenforcer/11.2/evaluation/introduction_3.webp) -Unlike password cracking products that check passwords after they are accepted by the operating -system, Password Policy Enforcer checks new passwords immediately to ensure that weak passwords do +Unlike password cracking products that check passwords after the operating system accepts them, +Password Policy Enforcer checks new passwords immediately to ensure that weak passwords do not jeopardize system security. :::note diff --git a/docs/passwordpolicyenforcer/11.2/evaluation/improving_the_password_policy.md b/docs/passwordpolicyenforcer/11.2/evaluation/improving_the_password_policy.md index 56d15b6a89..e549b8c292 100644 --- a/docs/passwordpolicyenforcer/11.2/evaluation/improving_the_password_policy.md +++ b/docs/passwordpolicyenforcer/11.2/evaluation/improving_the_password_policy.md @@ -6,14 +6,14 @@ sidebar_position: 60 # Improve the Password Policy -Password Policy Enforcer rules have properties that control how rules are enforced. You can improve +Password Policy Enforcer rules have properties that control how Password Policy Enforcer enforces +them. You can improve the effectiveness of the Users policy by enabling character substitution detection and bi-directional analysis (words typed backwards) for the **Similarity** and **Dictionary** rules. -When character substitution detection is enabled, Password Policy Enforcer searches passwords for +When you enable character substitution detection, Password Policy Enforcer searches passwords for common character substitutions. For example, an S replaced with a $. If a password only complies -with the policy because of the substitution ( the substitution is needed to make the password -compliant), then Password Policy Enforcer rejects the password. +with the policy because of the substitution, then Password Policy Enforcer rejects the password. Bi-directional analysis tests passwords with their characters reversed to stop users from circumventing a rule by entering a non-compliant password backwards. For example, "drowssapym" diff --git a/docs/passwordpolicyenforcer/11.2/evaluation/installforeval.md b/docs/passwordpolicyenforcer/11.2/evaluation/installforeval.md index cf1e299991..52e546e9c4 100644 --- a/docs/passwordpolicyenforcer/11.2/evaluation/installforeval.md +++ b/docs/passwordpolicyenforcer/11.2/evaluation/installforeval.md @@ -12,7 +12,7 @@ The evaluation installation uses the standard installation packages: evaluating. You can install manually using the procedure in [Install Password Policy Enforcer on a Server](/docs/passwordpolicyenforcer/11.2/installation/installationserver.md) or automatically with [Install with Group Policy Management](/docs/passwordpolicyenforcer/11.2/installation/installationgpm.md) procedure. Installing - Password Policy Enforcer doesn't extend the Active Directory schema. Be sure and install the + Password Policy Enforcer doesn't extend the Active Directory schema. Be sure to install the **Configuration Console** feature on at least one server. - Client Installation: install on each workstation you are evaluating. The Password Policy Client is an optional Password Policy Enforcer component to help users choose compliant passwords. Follow diff --git a/docs/passwordpolicyenforcer/11.2/evaluation/preparing_the_computer.md b/docs/passwordpolicyenforcer/11.2/evaluation/preparing_the_computer.md index ec68cc0670..0ddbf13c14 100644 --- a/docs/passwordpolicyenforcer/11.2/evaluation/preparing_the_computer.md +++ b/docs/passwordpolicyenforcer/11.2/evaluation/preparing_the_computer.md @@ -6,15 +6,16 @@ sidebar_position: 10 # Prepare the Computer -You only need one computer for the evaluation. A Windows Server 2016, 2019, or 2022 domain -controller in its own domain is recommended. You can also use Windows 10 or 11 if you only need to +You only need one computer for the evaluation. Netwrix recommends a Windows Server 2016, 2019, or +2022 domain controller in its own domain. You can also use Windows 10 or 11 if you only need to enforce policies for local accounts. ## Disable the Windows Password Policy Rules -If the Password Policy Enforcer and Windows password policies are both enabled, then users must -comply with both policies. This isn't recommended for the evaluation because the Windows policy may -stop users from reusing recent passwords, or from changing their password more than once a day. +If you enable both the Password Policy Enforcer and Windows password policies, then users must +comply with both policies. Netwrix doesn't recommend this for the evaluation because the Windows +policy may stop users from reusing recent passwords, or from changing their password more than once +a day. These restrictions can make it difficult to evaluate Password Policy Enforcer. This procedure disables the Windows password policy: @@ -41,7 +42,7 @@ This procedure disables the Windows password policy: **Step 4 –** Enter **0** in the text box, then click **OK**. -**Step 5 –** Repeat the step above for the Maximum Password Age and Minimum Password Length +**Step 5 –** Repeat Step 4 for the Maximum Password Age and Minimum Password Length policies. **Step 6 –** Double-click the **Group Policy Management Editor**. diff --git a/docs/passwordpolicyenforcer/11.2/evaluation/testing_the_password_policy.md b/docs/passwordpolicyenforcer/11.2/evaluation/testing_the_password_policy.md index b77654438c..670fc1f5b8 100644 --- a/docs/passwordpolicyenforcer/11.2/evaluation/testing_the_password_policy.md +++ b/docs/passwordpolicyenforcer/11.2/evaluation/testing_the_password_policy.md @@ -6,9 +6,9 @@ sidebar_position: 50 # Test the Password Policy -You can test the policy from the policy settings right where you are in the policy settings. You can -also test it from the Password Policy Enforcer configuration console dashboard, the Windows Change -Password screen, or the Active Directory Users and Computers / Local Users and Groups consoles. +You can test the policy directly from the policy settings. You can also test it from the Password +Policy Enforcer configuration console dashboard, the Windows Change Password screen, or the Active +Directory Users and Computers / Local Users and Groups consoles. ## Configuration Console @@ -62,11 +62,11 @@ From the Windows Change Password screen: **Step 5 –** Click the **submit arrow**. -You may have noticed that the Change Password screen looks different after installing Password -Policy Enforcer. The Password Policy Enforcer password policy is shown during password changes if -the Password Policy Client is installed. This helps users to choose a compliant password. The -Password Policy Client also changes the message that users see when their password is rejected. Both -these messages are customizable. +The Change Password screen looks different after you install Password Policy Enforcer. Password +Policy Enforcer shows its password policy during password changes if you install the Password Policy +Client. This helps users to choose a compliant password. The Password Policy Client also changes the +message that users see when Password Policy Enforcer rejects their password. Both these messages are +customizable. ![introduction_3](/images/passwordpolicyenforcer/11.2/evaluation/introduction_3.webp) @@ -78,16 +78,17 @@ Policy Enforcer Client are also available. Administrators often change domain passwords from the Active Directory Users and Computers console and local passwords from the Local Users and Groups console. In fact, these consoles don't change -passwords; they reset them. This is an important distinction because a password reset is: +passwords; they reset them. This is an important distinction because a password reset: -- Restricted to privileged users -- Performed without knowing the current password +- Requires privileged access +- Doesn't require knowing the current password Password Policy Enforcer can enforce the password policy for both password changes and password resets. It does this by default, but you can configure it to only enforce the password policy for -password changes. The Minimum Age rule is never enforced when a password is reset. +password changes. Password Policy Enforcer never enforces the Minimum Age rule when someone resets a +password. -Follow the steps to test password policies from these consoles. +To test password policies from these consoles: **Step 1 –** Open the appropriate console: @@ -102,13 +103,14 @@ Follow the steps to test password policies from these consoles. **Step 4 –** Click **OK**. :::note -These consoles don't explain why a password was rejected. Use the Password Policy +These consoles don't explain why Password Policy Enforcer rejected a password. Use the Password Policy Enforcer configuration console, or the Change Password screen with the Password Policy Enforcer Client installed to see this information. ::: -Here are some sample passwords and expected test results when the Users policy is enforced. Try to +Here are some sample passwords and expected test results when Password Policy Enforcer enforces the +Users policy. Try to change the password for the PPETestUser account to confirm that Password Policy Enforcer is enforcing the password policy correctly. diff --git a/docs/passwordpolicyenforcer/11.2/index.md b/docs/passwordpolicyenforcer/11.2/index.md index f32029918b..2b70361052 100644 --- a/docs/passwordpolicyenforcer/11.2/index.md +++ b/docs/passwordpolicyenforcer/11.2/index.md @@ -24,7 +24,7 @@ The disk space requirement doesn't include the compromised database. If you want ## System components ### Password Policy Server (PPS) -The Password Policy Server is the component that enforces the password policy. Install it on all the domain controllers to enforce a password policy for Active Directory user accounts. You can also install the PPS on individual servers and workstations to enforce a password policy for local user accounts on those computers. +The Password Policy Server enforces the password policy. Install it on all the domain controllers to enforce a password policy for Active Directory user accounts. You can also install the PPS on individual servers and workstations to enforce a password policy for local user accounts on those computers. ### Configuration Console The Configuration Console configures PPE. You will typically install this on your own computer or a management server, but you can also install it on the domain controllers. The Configuration Console also includes some PowerShell cmdlets. Use of the cmdlets is optional. diff --git a/docs/passwordpolicyenforcer/11.2/installation/installationclient.md b/docs/passwordpolicyenforcer/11.2/installation/installationclient.md index bc43d995ad..d6d12cd5eb 100644 --- a/docs/passwordpolicyenforcer/11.2/installation/installationclient.md +++ b/docs/passwordpolicyenforcer/11.2/installation/installationclient.md @@ -56,9 +56,9 @@ Add an exclusion for `%ProgramFiles%\Netwrix\Password Policy Enforcer\PPEClt.DLL ## Testing the Password Policy Client Test the Password Policy Client by logging on to a computer, pressing **Ctrl+Alt+Del**, and clicking **Change a password**. You should see the password policy rules on the password change screen. If you don't see the rules, then ensure that: -- The [Password Policy Server (PPS)](installationserver.md) is installed on all domain controllers in the domain. +- You installed the [Password Policy Server (PPS)](installationserver.md) on all domain controllers in the domain. - You restarted all domain controllers after installing the PPS. -- A PPE policy is [assigned](../admin/manage-policies/usersgroups.md) to the logged on user account. +- You [assigned](../admin/manage-policies/usersgroups.md) a PPE policy to the logged on user account. ## Uninstalling diff --git a/docs/passwordpolicyenforcer/11.2/installation/installationserver.md b/docs/passwordpolicyenforcer/11.2/installation/installationserver.md index 283329d6f2..8f217d37f5 100644 --- a/docs/passwordpolicyenforcer/11.2/installation/installationserver.md +++ b/docs/passwordpolicyenforcer/11.2/installation/installationserver.md @@ -39,7 +39,7 @@ To manually install one or more server components: ![Server Setup](/images/passwordpolicyenforcer/11.2/install/serversetup5.webp) -6. Click **Finish** when installation is complete. If prompted to restart the computer, then restart before using the installed components. +6. Click **Finish** when installation is complete. If the installer prompts you to restart the computer, then restart before using the installed components. ## Automated deployment diff --git a/docs/passwordpolicyenforcer/11.2/web-overview/configuration.md b/docs/passwordpolicyenforcer/11.2/web-overview/configuration.md index d54297fd37..04a09aa3c1 100644 --- a/docs/passwordpolicyenforcer/11.2/web-overview/configuration.md +++ b/docs/passwordpolicyenforcer/11.2/web-overview/configuration.md @@ -18,13 +18,13 @@ Enforcer integration. See the Password Policy Enforcer topic for additional info ### Domain List -When Password Policy Enforcer Web is first installed, the Domain List is empty and users must type +When you first install Password Policy Enforcer Web, the Domain List is empty and users must type their domain name. You can configure Password Policy Enforcer Web to display a list of domains instead of an empty text box. **Add Domain** -Follow the steps to add a domain to the list. +To add a domain to the list: **Step 1 –** Click the **Add...** button. @@ -41,7 +41,7 @@ them alphabetically. **Remove Domain** -Follow the steps to remove a domain from the list. +To remove a domain from the list: **Step 1 –** Select the domain name from the Domain List. diff --git a/docs/passwordpolicyenforcer/11.2/web-overview/editing_html_templates.md b/docs/passwordpolicyenforcer/11.2/web-overview/editing_html_templates.md index 4cb2470275..33dbb44a24 100644 --- a/docs/passwordpolicyenforcer/11.2/web-overview/editing_html_templates.md +++ b/docs/passwordpolicyenforcer/11.2/web-overview/editing_html_templates.md @@ -6,12 +6,12 @@ sidebar_position: 60 # Edit HTML Templates -Password Policy Enforcer Web's user interface is built with customizable templates. Modify the user interface by editing the templates. +Netwrix built Password Policy Enforcer Web's user interface with customizable templates. Modify the user interface by editing the templates. ### User Interface Files Password Policy Enforcer Web installs four .htm files for every language. Each filename starts with -a language code. The files for the US English language are: +a language code. The files for the American English language are: | Filename | Content | | --------------- | -------------------------------------------------------------------------------------------------------------------------------------- | @@ -22,18 +22,18 @@ a language code. The files for the US English language are: The other user interface files are language independent. Most of the formatting is in ppeweb.css, and some additional CSS for Internet Explorer is in ppeweb_ie.css. The image files are in the images -folder. These files are installed into the `\Inetpub\wwwroot\ppeweb\` folder by default. +folder. By default, the installer places these files in the `\Inetpub\wwwroot\ppeweb\` folder. :::note -Always backup the user interface files before and after editing them. Your changes may be -overwritten when Password Policy Enforcer Web is upgraded, and some changes could stop Password +Always backup the user interface files before and after editing them. Upgrading Password Policy +Enforcer Web may overwrite your changes, and some changes could stop Password Policy Enforcer Web from working correctly. Web browsers display pages differently, so test your changes with several versions of the most popular browsers to ensure compatibility. ::: The en_default.htm contains static HTML, but the other .htm files contain special comment tags that -are used to prepare the pages. Some of these comments define ranges. A range looks like this: +Password Policy Enforcer Web uses to prepare the pages. Some of these comments define ranges. A range looks like this: `Some text or HTML` @@ -43,8 +43,8 @@ called a field. `` -Fields are replaced by some other information. For example, the field above is replaced with a -username. +Password Policy Enforcer Web replaces fields with other information. For example, it replaces +`` with a username. #### Resource Strings @@ -65,8 +65,8 @@ right. Resource strings are always inside a range called RESOURCE_STRINGS. Passw Web deletes this range before sending the page to the user's web browser. :::warning -You may rebrand the Password Policy Enforcer Web user interface, but it is a violation -of the License Agreement to modify, remove, or obscure any copyright notice. +You may rebrand the Password Policy Enforcer Web user interface, but modifying, removing, or +obscuring any copyright notice violates the License Agreement. ::: @@ -75,13 +75,14 @@ of the License Agreement to modify, remove, or obscure any copyright notice. This topic contains examples of common customizations. Use these examples to gain a better understanding of Password Policy Enforcer Web's templates. You don't need to be an expert in HTML to follow these examples, but a basic understanding of HTML will help. Work through them carefully, and -backup files before you edit them. The examples in this section are from the US English files, but +backup files before you edit them. The examples in this section are from the American English files, but the format is the same for all languages. ### Replacing the Netwrix Logo -The Netwrix logo is shown in the top left corner of the Welcome page. The logo is installed into the -`\Inetpub\wwwroot\ppeweb\images\` folder by default, and it is called logo.gif. You can replace this +Password Policy Enforcer Web shows the Netwrix logo in the top left corner of the Welcome page. By +default, the installer places the logo in the `\Inetpub\wwwroot\ppeweb\images\` folder, and it is +called logo.gif. You can replace this file with one containing your organization's logo. Your logo may appear distorted if it isn't the same size as the Netwrix logo. You can fix this by @@ -97,7 +98,7 @@ want to modify. Instructions are inside ranges called SECTION_A and SECTION_B. Each section contains the instructions for a page in the template. Ensure you edit the instructions in the correct section, -or they may be displayed on the wrong page. +or Password Policy Enforcer Web may display them on the wrong page. `` @@ -113,12 +114,12 @@ or they may be displayed on the wrong page. ### Edit Validation Error Messages -Validation error messages are shown in a yellow box below the page instructions. Validation errors -are normally caused by invalid user input. +Password Policy Enforcer Web shows validation error messages in a yellow box below the page +instructions. Invalid user input normally causes validation errors. ![using_ppe_web_1](/images/passwordpolicyenforcer/11.2/web/using_ppe_web_1.webp) -Validation error messages are defined in en_ppeweb.htm. The error messages are in the resource +en_ppeweb.htm defines the validation error messages. The error messages are in the resource strings section near the end of the file. See the Resource Strings topic for additional information. | String | Error Message | @@ -129,14 +130,14 @@ strings section near the end of the file. See the Resource Strings topic for add ### Edit Critical Error Messages -All the critical error messages are defined in `en_error.htm`. The error messages are in the +`en_error.htm` defines all the critical error messages. The error messages are in the resource strings section near the end of the file. See the Resource Strings topic for additional information. ![using_ppe_web_2](/images/passwordpolicyenforcer/11.2/web/using_ppe_web_2.webp) -You may see placeholders like %1 and %2 in some error messages. These are replaced with more -information about the error. You should keep these as they provide important information about the +You may see placeholders like %1 and %2 in some error messages. Password Policy Enforcer Web +replaces these with more information about the error. You should keep these as they provide important information about the error, but you can delete them if you don't want them. | String | Error Message | @@ -158,8 +159,8 @@ If you want to display some text for all error messages, then insert your text a ### Edit Finished Message -The finished message is shown after users successfully change their password. This message is -defined in en_finished.htm. +Password Policy Enforcer Web shows the finished message after users successfully change their +password. en_finished.htm defines this message. ![editing_the_html_templates_1](/images/passwordpolicyenforcer/11.2/web/editing_the_html_templates_1.webp) diff --git a/docs/passwordpolicyenforcer/11.2/web-overview/installationweb.md b/docs/passwordpolicyenforcer/11.2/web-overview/installationweb.md index fd165bb83b..8fbc91b588 100644 --- a/docs/passwordpolicyenforcer/11.2/web-overview/installationweb.md +++ b/docs/passwordpolicyenforcer/11.2/web-overview/installationweb.md @@ -18,12 +18,12 @@ Click the following link to download Password Policy Enforcer Web: The Setup Wizard copies the required files onto the server and configures IIS to run the Password Policy Enforcer Web application. -Follow the steps to install PPE Web. +To install PPE Web: **Step 1 –** Start the Password Policy Enforcer Web Setup Wizard (PPEWeb711.exe). -**Step 2 –** If another version of Password Policy Enforcer Web is detected, the Setup Wizard may -required older files to be backed up. Back up these files if the original files have been modified. +**Step 2 –** If the Setup Wizard detects another version of Password Policy Enforcer Web, it may +require you to back up older files. Back up these files if you modified the original files. Click **Next**. **Step 3 –** Click **Next**. @@ -48,18 +48,17 @@ Password Policy Enforcer Web should be installed in its own virtual directory. #### Upgrading from PPE Web V7.x -Some planning is needed to ensure a smooth upgrade from PPE Web V7.x. A trial run on a lab network -is recommended. +Plan carefully to ensure a smooth upgrade from PPE Web V7.x. Run a trial on a lab network first. #### Before You Begin -The HTML templates and associated images are overwritten during an upgrade. You must back up and -customized HTML templates and images before upgrading. The HTML templates and images are installed -in the `\Inetpub\wwwroot\ppeweb\` folder by default. +Upgrading overwrites the HTML templates and associated images. You must back up and +customized HTML templates and images before upgrading. By default, the installer places the HTML +templates and images in the `\Inetpub\wwwroot\ppeweb\` folder. :::note -A full backup of the PPE Web server is recommended. Use it to roll back to the -previous version if the upgrade can't be completed. You may need to restart Windows after +Take a full backup of the PPE Web server. Use it to roll back to the +previous version if you can't complete the upgrade. You may need to restart Windows after upgrading. ::: @@ -74,7 +73,7 @@ integration. #### Upgrading to V7.11 **Step 1 –** Start the PPE Web Setup Wizard and follow the prompts. The Setup Wizard uninstalls the -previous version. There is no need to manually uninstall previous versions. +previous version. You don't need to manually uninstall previous versions. **Step 2 –** Restore any customized HTML templates and images after upgrading. Don't restore PPEWeb.dll from the backup as it belongs to the previous version. diff --git a/docs/passwordpolicyenforcer/11.2/web-overview/securing_web.md b/docs/passwordpolicyenforcer/11.2/web-overview/securing_web.md index 111fa59091..e79942ec0e 100644 --- a/docs/passwordpolicyenforcer/11.2/web-overview/securing_web.md +++ b/docs/passwordpolicyenforcer/11.2/web-overview/securing_web.md @@ -6,9 +6,9 @@ sidebar_position: 50 # Secure Password Policy Enforcer Web -Password Policy Enforcer Web is designed to operate securely, but you must ensure that the web +Netwrix designed Password Policy Enforcer Web to operate securely, but you must ensure that the web server is also secure. Follow Microsoft's recommendations to secure the web server, and always -install and use an SSL certificate if Password Policy Enforcer Web is used on an unencrypted network. +install and use an SSL certificate if you use Password Policy Enforcer Web on an unencrypted network. ## Install an SSL Certificate @@ -30,6 +30,6 @@ See the [Configure Server Certificates in IIS 7](https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc732230(v=ws.10)?redirectedfrom=MSDN) Microsoft knowledge base article for additional information. -Ensure that users only access Password Policy Enforcer Web over an encrypted connection after the -SSL certificate is installed. The URL should start with https://. Web browsers can be redirected to +Ensure that users only access Password Policy Enforcer Web over an encrypted connection after you +install the SSL certificate. The URL should start with https://. You can redirect web browsers to always use the secure URL. diff --git a/docs/passwordpolicyenforcer/11.2/web-overview/using_web.md b/docs/passwordpolicyenforcer/11.2/web-overview/using_web.md index c084bff0cf..5af05573c7 100644 --- a/docs/passwordpolicyenforcer/11.2/web-overview/using_web.md +++ b/docs/passwordpolicyenforcer/11.2/web-overview/using_web.md @@ -23,15 +23,15 @@ You can also include the username and/or domain in the URL: `http://[server]/ppeweb/ppeweb.dll?username=maryjones&domain=ANIXIS` :::info -Install the SSL Certificate the web server and use the HTTPS protocol if Password -Policy Enforcer Web is used on an unencrypted network. See the +Install the SSL Certificate the web server and use the HTTPS protocol if you use Password +Policy Enforcer Web on an unencrypted network. See the [Install an SSL Certificate](/docs/passwordpolicyenforcer/11.2/web-overview/securing_web.md) topic for additional information. ::: :::note -A license reminder message is shown occasionally when Password Policy Enforcer Web is used +Password Policy Enforcer Web occasionally shows a license reminder message when you use it without a license key. Contact Netwrix support if you would like to evaluate Password Policy Enforcer Web without the reminder message. ::: @@ -61,18 +61,18 @@ enabled. ## Error Messages -Validation errors are shown in a yellow box below the page instructions. Validation errors are -normally caused by invalid user input. They can often be overcome by changing the value of one or -more input fields and resubmitting the form. +Password Policy Enforcer Web shows validation errors in a yellow box below the page instructions. +Invalid user input normally causes validation errors. You can often overcome them by changing the +value of one or more input fields and resubmitting the form. ![using_ppe_web_1](/images/passwordpolicyenforcer/11.2/web/using_ppe_web_1.webp) -Critical errors are shown on their own page. These errors are mostly a result of configuration or -system errors. Users can sometimes overcome a critical error by following the instructions in the +Password Policy Enforcer Web shows critical errors on their own page. These errors are mostly a +result of configuration or system errors. Users can sometimes overcome a critical error by following the instructions in the error message, but most critical errors are beyond the user's control. ![using_ppe_web_2](/images/passwordpolicyenforcer/11.2/web/using_ppe_web_2.webp) -Validation and critical error messages are stored in the HTML templates. You can modify the default +The HTML templates store validation and critical error messages. You can modify the default messages by editing the templates. See the [Edit HTML Templates](/docs/passwordpolicyenforcer/11.2/web-overview/editing_html_templates.md) topic for additional information. diff --git a/docs/passwordpolicyenforcer/11.2/web-overview/web_overview.md b/docs/passwordpolicyenforcer/11.2/web-overview/web_overview.md index 222368bf98..a57d9fbb73 100644 --- a/docs/passwordpolicyenforcer/11.2/web-overview/web_overview.md +++ b/docs/passwordpolicyenforcer/11.2/web-overview/web_overview.md @@ -21,7 +21,7 @@ server in a DMZ for extra security, then consider using Netwrix Password Reset i Policy Enforcer Web. Password Reset also lets users change their password from a web browser, but it has many other -features including the ability to work in a DMZ without any domain controllers. Use Password Reset +features, including working in a DMZ without any domain controllers. Use Password Reset if you need to: - Users can reset a forgotten password or unlock their account by answering questions about From 9364e9bb1c5625254c2f7f8fd154e028206f9734 Mon Sep 17 00:00:00 2001 From: "claude[bot]" <41898282+claude[bot]@users.noreply.github.com> Date: Mon, 24 Aug 2026 17:20:31 +0000 Subject: [PATCH 02/36] fix(vale): auto-fix style issues (Vale + Dale) --- .../11.2/admin/hibpupdater.md | 22 ++++++++--------- .../11.2/admin/manage-policies/rules/rules.md | 4 ++-- .../11.2/admin/manage-policies/testpolicy.md | 14 +++++------ .../configuring_the_password_policy_client.md | 8 +++---- .../password_policy_client.md | 4 ++-- .../11.2/admin/ppe_tool.md | 24 +++++++++---------- .../11.2/admin/troubleshooting.md | 24 +++++++++---------- .../evaluation/configuring_policy_rules.md | 9 +++---- .../creating_a_password_policy.md | 8 +++---- .../policy_templates.md | 2 +- .../evaluation/enforcing_multiple_policies.md | 5 ++-- .../improving_the_password_policy.md | 2 +- .../evaluation/testing_the_password_policy.md | 8 +++---- .../11.2/web-overview/configuration.md | 4 ++-- .../web-overview/editing_html_templates.md | 12 +++++----- .../11.2/web-overview/installationweb.md | 2 +- .../11.2/web-overview/using_web.md | 8 +++---- .../11.2/web-overview/web_overview.md | 8 +++---- 18 files changed, 83 insertions(+), 85 deletions(-) diff --git a/docs/passwordpolicyenforcer/11.2/admin/hibpupdater.md b/docs/passwordpolicyenforcer/11.2/admin/hibpupdater.md index 78d46cbb95..b89ea50c8d 100644 --- a/docs/passwordpolicyenforcer/11.2/admin/hibpupdater.md +++ b/docs/passwordpolicyenforcer/11.2/admin/hibpupdater.md @@ -25,7 +25,7 @@ location. If you copy and store the HIBP database locally on the Domain Controllers: -- The HIBP database takes up additional space on the machine where it is copied. (Aproximetly 13GB but subject to change) +- The HIBP database takes up additional space on the machine you copy it to. (Aproximetly 13GB but subject to change) - If you use a local database, place it on every domain controller in the same location specified in the rule. - A network connection isn't involved and doesn't affect the performance of checking the password against the HIBP database - PPE checks the pending password candidate against the archived hash file locally. If the password hash matches an entry, PPE rejects the pending password change. @@ -127,11 +127,11 @@ Compromised rule to read the files from: See the [Compromised Rule](/docs/passwordpolicyenforcer/11.2/admin/manage-policies/rules/compromised_rule.md) topic for additional information. -The preceding path only works if the computer has a Sysvol share. This won't be the case if you are -using a workstation for policy testing, or if you are using Password Policy Enforcer to enforce -local policies. If you are using Password Policy Enforcer for local policies and want all computers -to receive hash file updates, then use the Sysvol share for file replication and a script or -scheduled task to copy the file to a local folder. +The preceding path only works if the computer has a Sysvol share. This won't be the case if you use +a workstation for policy testing, or if you use Password Policy Enforcer to enforce local policies. +If you use Password Policy Enforcer for local policies and want all computers to receive hash file +updates, then use the Sysvol share for file replication and a script or scheduled task to copy the +file to a local folder. :::warning %SystemRoot%. Only read hash files from a local disk. Using shared hash files @@ -141,9 +141,9 @@ degrades performance, and could jeopardize security. ## Scheduler -Password Policy Enforcer administrators can use the Scheduler portion of the HIBP Updater to -automate the tool to retrieve and/or prepare the HIBP dataset. The Scheduler uses Microsoft Task -Scheduler technology to execute the process. +Password Policy Enforcer administrators can use the Scheduler in the HIBP Updater to automate +retrieving and preparing the HIBP dataset. The Scheduler uses Microsoft Task Scheduler to run the +process. ### How to Schedule a Task @@ -156,13 +156,13 @@ Updater window. **Step 3 –** Enter the Name and Description of the schedule. -**Step 4 –** Select **Add Trigger** to add the interval that you want to have the schedule run. +**Step 4 –** Select **Add Trigger** to add the interval at which you want the schedule to run. - You can add as many triggers as you want to a schedule. **Step 5 –** Select the Update Type and Location to get the update. -**Step 6 –** After you have set up your schedule, click **OK** to save the schedule. +**Step 6 –** After you set up your schedule, click **OK** to save it. PPE updates the HIBP database according to the schedule. diff --git a/docs/passwordpolicyenforcer/11.2/admin/manage-policies/rules/rules.md b/docs/passwordpolicyenforcer/11.2/admin/manage-policies/rules/rules.md index f67ce18b37..cbac3ddc33 100644 --- a/docs/passwordpolicyenforcer/11.2/admin/manage-policies/rules/rules.md +++ b/docs/passwordpolicyenforcer/11.2/admin/manage-policies/rules/rules.md @@ -51,9 +51,9 @@ Some rules have a **Detect character substitution** checkbox. PPE tests password Some rules have a **Tolerance** dropdown. The tolerance controls how strictly PPE enforces the rule. -Tolerance is the maximum number of consecutive matching characters allowed between the password and another parameter. Password Policy Enforcer rejects a password if it exceeds the specified tolerance. For example, the logon name "mary**jones**", and the password "**Jones**town" contain five consecutive matching characters (shown in bold). Password Policy Enforcer rejects this password if the tolerance for the User Logon Name rule is four or lower, and accepts it if the tolerance is five or higher. +Tolerance is the maximum number of consecutive matching characters that PPE allows between the password and another parameter. Password Policy Enforcer rejects a password if it exceeds the specified tolerance. For example, the logon name "mary**jones**", and the password "**Jones**town" contain five consecutive matching characters (shown in bold). Password Policy Enforcer rejects this password if the tolerance for the User Logon Name rule is four or lower, and accepts it if the tolerance is five or higher. -Some rules have an Auto tolerance option. Setting the tolerance to Auto tells Password Policy Enforcer to reject only passwords that contain the entire comparison parameter. This is useful when the length of the comparison parameter is unknown. For example, if you want PPE to reject passwords that contain the user's entire logon name, then you can't specify a fixed tolerance unless all logon names are the same length. Setting the tolerance to Auto lets Password Policy Enforcer calculate an appropriate tolerance during the password change. +Some rules have an Auto tolerance option. Setting the tolerance to Auto tells Password Policy Enforcer to reject only passwords that contain the entire comparison parameter. This is useful when you don't know the length of the comparison parameter. For example, if you want PPE to reject passwords that contain the user's entire logon name, then you can't specify a fixed tolerance unless all logon names are the same length. Setting the tolerance to Auto lets Password Policy Enforcer calculate an appropriate tolerance during the password change. Password Policy Enforcer sets the tolerance to the length of the comparison parameter minus one. The following table shows some parameter values and the calculated tolerance. PPE rejects a password if it contains all the text in the Value column (or a derivative of it if you enable **Detect character substitution** or **Detect words typed backwards**). diff --git a/docs/passwordpolicyenforcer/11.2/admin/manage-policies/testpolicy.md b/docs/passwordpolicyenforcer/11.2/admin/manage-policies/testpolicy.md index 1002e08218..3512d0914a 100644 --- a/docs/passwordpolicyenforcer/11.2/admin/manage-policies/testpolicy.md +++ b/docs/passwordpolicyenforcer/11.2/admin/manage-policies/testpolicy.md @@ -7,7 +7,7 @@ sidebar_position: 60 # Test Policy You can test your Password Policy Enforcer configuration by simulating a password change. -Click **Test Policy** from the Configuration Console dashboard or when you are setting up a policy. +Click **Test Policy** from the Configuration Console dashboard or when setting up a policy. Test policy opens in a separate window. Remember to **Save** your rules and changes before testing. @@ -19,8 +19,8 @@ Test policy opens on the **By user** tab. Policy testing simulates a password change, but it doesn't change the password. -**Step 1 –** Click **Test policy** from the Configuration Console dashboard or when you are setting -up a policy. +**Step 1 –** Click **Test policy** from the Configuration Console dashboard or when setting up a +policy. **Step 2 –** Select a **user**. @@ -42,7 +42,7 @@ Expand the **View log** for details: - Dictionary word or keyboard pattern matched with the password. - Errors or warnings occurred during testing. -Turn on **Verbose Logging** to view the performed tests and results. +Turn on **Verbose Logging** to view the tests that Password Policy Enforcer performed and their results. ![Verbose logging](/images/passwordpolicyenforcer/11.2/administration/testuserverbose.webp) @@ -50,8 +50,8 @@ Turn on **Verbose Logging** to view the performed tests and results. The Bulk Password Test feature lets you check a large number of passwords against a selected policy and get a report of the accepted and rejected passwords. -**Step 1 –** Click **Test policy** from the Configuration Console dashboard or when you are setting -up a policy. +**Step 1 –** Click **Test policy** from the Configuration Console dashboard or when setting up a +policy. **Step 2 –** Open the **Password bulk test** tab. @@ -73,7 +73,7 @@ the file isn't on a shared drive. | Accepted | Number of accepted passwords. | | Rejected | Number of rejected passwords. | | Number of lines | Number of lines within the file. | -| Lines processed | Shows the number of the processed lines. | +| Lines processed | Number of processed lines. | Click **Show full report** to view the test details. diff --git a/docs/passwordpolicyenforcer/11.2/admin/password-policy-client/configuring_the_password_policy_client.md b/docs/passwordpolicyenforcer/11.2/admin/password-policy-client/configuring_the_password_policy_client.md index 7af2bd92fd..6a3d88e485 100644 --- a/docs/passwordpolicyenforcer/11.2/admin/password-policy-client/configuring_the_password_policy_client.md +++ b/docs/passwordpolicyenforcer/11.2/admin/password-policy-client/configuring_the_password_policy_client.md @@ -31,12 +31,12 @@ Policy Enforcer) and copy the **PPEClt.adml** and **PPEClt.admx** files (highlig ![ppc_configuration](/images/passwordpolicyenforcer/11.2/administration/ppc_configuration.webp) -**Step 3 –** Go to C:\Windows\Policy Definitions and paste the .admx file in the root of this +**Step 3 –** Go to `C:\Windows\Policy Definitions` and paste the .admx file in the root of this folder. ![ppc_configuration2](/images/passwordpolicyenforcer/11.2/administration/ppc_configuration2.webp) -**Step 4 –** Go to C:\Windows\Policy Definitions\en-US and paste the .adml file in the root of this +**Step 4 –** Go to `C:\Windows\Policy Definitions\en-US` and paste the .adml file in the root of this folder. ![ppc_configuration1](/images/passwordpolicyenforcer/11.2/administration/ppc_configuration1.webp) @@ -78,8 +78,8 @@ message in a message box to draw attention to the password policy. ![the_password_policy_client_3](/images/passwordpolicyenforcer/11.2/administration/the_password_policy_client_3.webp) You can change the default display settings to control which user interface elements the Password -Policy Client hides, and the point at which it hides them. The display of the Password Policy -message box is also configurable. +Policy Client hides, and the point at which it hides them. You can also configure whether the +Password Policy message box appears. To change the default display settings for the Password Policy Client on Windows 10 and 11: diff --git a/docs/passwordpolicyenforcer/11.2/admin/password-policy-client/password_policy_client.md b/docs/passwordpolicyenforcer/11.2/admin/password-policy-client/password_policy_client.md index 26de500987..523aa14673 100644 --- a/docs/passwordpolicyenforcer/11.2/admin/password-policy-client/password_policy_client.md +++ b/docs/passwordpolicyenforcer/11.2/admin/password-policy-client/password_policy_client.md @@ -9,9 +9,9 @@ sidebar_position: 50 The Password Policy Client helps users to choose a compliant password. If Password Policy Enforcer rejects a new password, the Password Policy Client provides detailed information. -The Password Policy Client is optional. If it isn't installed, Password Policy Enforcer can't enforce +The Password Policy Client is optional. If you don't install it, Password Policy Enforcer can't enforce the [Similarity Rule](/docs/passwordpolicyenforcer/11.2/admin/manage-policies/rules/similarity_rule.md). If Password Policy Enforcer rejects a password, users only see the default Windows error -message, not the detailed help they receive from the Password Policy Client. +message instead of the detailed help the Password Policy Client provides. ![the_password_policy_client](/images/passwordpolicyenforcer/11.2/administration/the_password_policy_client.webp) diff --git a/docs/passwordpolicyenforcer/11.2/admin/ppe_tool.md b/docs/passwordpolicyenforcer/11.2/admin/ppe_tool.md index cc0fd9e66e..51edc3ffd3 100644 --- a/docs/passwordpolicyenforcer/11.2/admin/ppe_tool.md +++ b/docs/passwordpolicyenforcer/11.2/admin/ppe_tool.md @@ -6,12 +6,11 @@ sidebar_position: 80 # PPE Tool -The PPE Tool is designed to configure local and domain instances of Password Policy Enforcer and -produce reports pertaining to the configuration of Password Policy Enforcer. The PPE Tool is -designed to perform the following functions: +The PPE Tool configures local and domain instances of Password Policy Enforcer and +produces reports about the Password Policy Enforcer configuration. The PPE Tool performs the following functions: -- Export the configuration from the existing instance of Password Policy Enforcer, regardless if the - server is local or domain. +- Export the configuration from the existing instance of Password Policy Enforcer, regardless of + whether the server is local or domain. - Import existing PPE configurations on another PPE server instance. - Generate user-friendly reports that contain configuration values and descriptions. - Create HTML reports with configuration values and descriptions of the PPE server instance. @@ -21,7 +20,7 @@ This topic covers how to install the PPE Tool, how to customize and run reports, ## Using the PPE Tool The PPE Tool installs with the default installation of Password Policy Enforcer under the -`C:\Program Files\Netwrix\Password Policy Enforcer\ppetool` folder. After installation, the PPE Tool supports a number of operations related to Password Policy Enforcer functionality, which are described in the following table. +`C:\Program Files\Netwrix\Password Policy Enforcer\ppetool` folder. After installation, the PPE Tool supports several operations related to Password Policy Enforcer functionality. The following table describes them. :::note You can execute all PPE Tool operations from the Command Prompt if you run them with administrator @@ -32,8 +31,7 @@ rights. ### PPE Tool Operations :::info -PPE Tool operations should only be executed one at a time. For example, you -shouldn't execute the /e (Export) and /i (Import) operations simultaneously; you shouldn't run /e +PPE Tool operations must run one at a time. For example, don't run the /e (Export) and /i (Import) operations simultaneously, and don't run the /e (Export) and /r (Report) operations simultaneously. ::: @@ -48,7 +46,7 @@ shouldn't execute the /e (Export) and /i (Import) operations simultaneously; y | /c | config [in file name] |
  • Uses a config file instead of Password Policy Enforcer export when exporting reports (in the case of /i (Import), /h (Human [out file name]), and /r (Report [out file name]).
  • The default file is `config.xml`.
  • This operation defines the input file for the i/ (Import) operation, and thus is necessary for importing files to the PPE Tool. An error message appears if you omit the /c (Config [in file name]) option.
  • By default, the /h (Human [out file name]) and /r (Report [out file name]) operations use the Password Policy Enforcer instance as the reporting source. The /c (Config [in file name]) operation should provide the source configuration file as an argument to create reports. If you provide an invalid file name as an argument in this operation, the PPE Tool displays the appropriate error message and exits.
| -Operations PPE Tool options are as follows: +The PPE Tool options are as follows: | Task | Task Name | Task Description | | ---- | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -85,10 +83,10 @@ example, the PPE Tool searches for the file tagname.xml (or, ppe.xml in this ca root elements which name match each file name. Each root tag contains child tags (e.g., ``). Each tag has the following attributes: -- name — Contains the original tag name from the input configuration file. If this attribute is - omitted, then the original tag and its value are absent in the human-readable report. -- DisplayName — Contains the user-friendly description for the original tag. If this attribute is - omitted, then the original tag and its value appear in the report without a description. +- name — Contains the original tag name from the input configuration file. If you omit this + attribute, then the original tag and its value are absent in the human-readable report. +- DisplayName — Contains the user-friendly description for the original tag. If you omit this + attribute, then the original tag and its value appear in the report without a description. The `` tag can also contain the child `` tag. This tag can have an optional attribute 'mode' and this attribute can have the following values: diff --git a/docs/passwordpolicyenforcer/11.2/admin/troubleshooting.md b/docs/passwordpolicyenforcer/11.2/admin/troubleshooting.md index 4eb319358e..0d8232f85b 100644 --- a/docs/passwordpolicyenforcer/11.2/admin/troubleshooting.md +++ b/docs/passwordpolicyenforcer/11.2/admin/troubleshooting.md @@ -10,13 +10,13 @@ This topic contains troubleshooting information for the most common support ques Netwrix support with any questions. PPE enforces a password policy assigned to some users for all users. Check the Default Policy in -the Password Policy Server (PPS) Properties page. Users must comply with the default policy if no other policy is assigned to -them. Select the first (blank) item in the dropdown list if you don't want a default policy. +the Password Policy Server (PPS) Properties page. Users must comply with the default policy if you +haven't assigned another policy to them. Select the first (blank) item in the dropdown list if you don't want a default policy. #### Password policy not displayed during password change -Open the Programs and Features list in Control Panel on the computer you are changing the password -from, and check if the Password Policy Client is in the list of installed programs. If it isn't, +Open the Programs and Features list in Control Panel on the computer where you change the password, +and check if the Password Policy Client is in the list of installed programs. If it isn't, then install the Password Policy Client. See the [Password Policy Client](/docs/passwordpolicyenforcer/11.2/admin/password-policy-client/password_policy_client.md) topic for additional information. @@ -29,11 +29,11 @@ local policies, search the Application Event Log on the local computer. If there is a firewall between the client computer and the domain controllers (including Windows Firewall), then you must create firewall rules to allow the Password Policy Client and Password -Policy Server to communicate. Windows firewall is enabled by default on Windows Server 2008 and +Policy Server to communicate. Windows Firewall runs by default on Windows Server 2008 and later. -Use the Test Policies page to test a password for the user. Click the **Log** tab to see if a -password policy is assigned to the user. +Use the Test Policies page to test a password for the user. Click the **Log** tab to see whether the +user has an assigned password policy. Ensure that the Password Policy Server is enabled. @@ -55,9 +55,9 @@ the Test Policies page rejects the password, you must configure the policy. See [Policy Testing vs. Password Changes](/docs/passwordpolicyenforcer/11.2/admin/manage-policies/testpolicy.md#policy-testing-vs-password-changes) topic for additional information. -If the **Enforce policy when password is reset** checkbox isn't selected in the PPS Properties -page, then Password Policy Enforcer won't enforce the password policy for passwords that are -reset from the Active Directory Users and Computers console, or the Local Users and Groups console. +If you don't select the **Enforce policy when password is reset** checkbox in the PPS Properties +page, then Password Policy Enforcer won't enforce the password policy for passwords reset from the +Active Directory Users and Computers console, or the Local Users and Groups console. You should select this option during testing, or test password changes from the Windows Change Password screen. @@ -70,8 +70,8 @@ the Test Policies page rejects the password, you must configure the policy. See additional information. Set **User must change password at next logon** for the user and repeat the password change test. If -the password is accepted, then either Windows or Password Policy Enforcer is configured to enforce a -minimum password age. Disable the Minimum Age rule in Windows and Password Policy Enforcer to +Password Policy Enforcer accepts the password, then either Windows or Password Policy Enforcer is +enforcing a minimum password age. Disable the Minimum Age rule in Windows and Password Policy Enforcer to facilitate testing. If you can't disable the Minimum Age rule, then set User must change password at next logon before every password change test to bypass the rule. diff --git a/docs/passwordpolicyenforcer/11.2/evaluation/configuring_policy_rules.md b/docs/passwordpolicyenforcer/11.2/evaluation/configuring_policy_rules.md index 10d3ac0e13..99696b6c1c 100644 --- a/docs/passwordpolicyenforcer/11.2/evaluation/configuring_policy_rules.md +++ b/docs/passwordpolicyenforcer/11.2/evaluation/configuring_policy_rules.md @@ -15,8 +15,9 @@ the policy to enforce these rules: - Password must not be similar to the user's logon name. - Password must not exist in a dictionary of common passwords. -When you create a policy, the policy settings are opened. You can open the settings for a policy at -any time by clicking the policy name on the Configuration Console dashboard. +When you create a policy, Password Policy Enforcer opens the policy settings. You can open the +settings for a policy at any time by clicking the policy name on the Configuration Console +dashboard. ![New policy open for settings](/images/passwordpolicyenforcer/11.2/evaluation/newpolicysettings.webp) @@ -45,7 +46,7 @@ You set this condition with the **Characters (Complexity)** rule. **Step 4 –** Select **Lower Alpha (a-z)**. -**Step 5 –** Select **Upper Alpha (A-Z)** for the next requirement while you are here. +**Step 5 –** Select **Upper Alpha (A-Z)** now for the next requirement. ![Set upper and lower case requirements](/images/passwordpolicyenforcer/11.2/evaluation/evalchars.webp) @@ -91,4 +92,4 @@ You set this condition with the **Dictionary** rule. ![Enable the sample dictionary](/images/passwordpolicyenforcer/11.2/evaluation/evaldict.webp) -When you have added all the rules, click **Save**. +After you add all the rules, click **Save**. diff --git a/docs/passwordpolicyenforcer/11.2/evaluation/creating-a-password-policy/creating_a_password_policy.md b/docs/passwordpolicyenforcer/11.2/evaluation/creating-a-password-policy/creating_a_password_policy.md index 3b2ec0bab8..95c04f1ded 100644 --- a/docs/passwordpolicyenforcer/11.2/evaluation/creating-a-password-policy/creating_a_password_policy.md +++ b/docs/passwordpolicyenforcer/11.2/evaluation/creating-a-password-policy/creating_a_password_policy.md @@ -6,10 +6,10 @@ sidebar_position: 30 # Create a Password Policy -Password Policy Enforcer has no password policies defined when first installed. You can now +Password Policy Enforcer has no password policies after you install it. You can now create your first Password Policy Enforcer password policy. Password Policy Enforcer accepts all passwords in this state, so users only need to comply with the Windows password policy rules (if -enabled). +you enable them). **Step 1 –** Open the Configuration Console: @@ -19,8 +19,8 @@ Double click the **PPE Configuration** desktop shortcut. ![Configuration Console Dashboard](/images/passwordpolicyenforcer/11.2/evaluation/ppedashboard.webp) -The Configuration Console dashboard shows **No password policies have been set up** when you are -getting started with Password Policy Enforcer. +The Configuration Console dashboard shows **No password policies have been set up** when you first +start using Password Policy Enforcer. **Step 2 –** Click **Add policy**. diff --git a/docs/passwordpolicyenforcer/11.2/evaluation/creating-a-password-policy/policy_templates.md b/docs/passwordpolicyenforcer/11.2/evaluation/creating-a-password-policy/policy_templates.md index ec9b8cf220..9eaf52e331 100644 --- a/docs/passwordpolicyenforcer/11.2/evaluation/creating-a-password-policy/policy_templates.md +++ b/docs/passwordpolicyenforcer/11.2/evaluation/creating-a-password-policy/policy_templates.md @@ -27,7 +27,7 @@ most popular regulatory frameworks. - It also recommends training the workforce on ways to safeguard password information and establish guidelines to create and change passwords in a periodic cycle. - HIPAA doesn’t offer any specific password complexity guidelines. To comply with HIPAA, - organizations are better off following National Institute of Standards and Technology (NIST) + organizations should follow National Institute of Standards and Technology (NIST) password guidelines. - Most of healthcare institutions use the NIST framework. diff --git a/docs/passwordpolicyenforcer/11.2/evaluation/enforcing_multiple_policies.md b/docs/passwordpolicyenforcer/11.2/evaluation/enforcing_multiple_policies.md index 6b0f6520ea..7ff93a7114 100644 --- a/docs/passwordpolicyenforcer/11.2/evaluation/enforcing_multiple_policies.md +++ b/docs/passwordpolicyenforcer/11.2/evaluation/enforcing_multiple_policies.md @@ -40,8 +40,7 @@ local **Location** depending on your evaluation set up. - Members of the Domain Admins group (or, if you aren't using a domain controller, the PPETestAdmin user) must now comply with the Administrators policy. All other users must comply with the Users policy. - Users won't notice any difference at this point because the two polices are enforcing identical - rules. + Users won't notice any difference yet because the two policies enforce identical rules. ### Differentiate Password Policies @@ -62,7 +61,7 @@ to nine characters. **Step 6 –** Select the **PPETestAdmin** user. The results pane shows that the **Admins Policy** applies, and that the password must **contain at least 9 characters**. -![Admins policy is being tested](/images/passwordpolicyenforcer/11.2/evaluation/evaladmin.webp) +![Testing the Admins policy](/images/passwordpolicyenforcer/11.2/evaluation/evaladmin.webp) Use the Password Policy Enforcer configuration console, the Windows Change Password screen, the Active Directory Users and Computers console, or the Local Users and Groups console to test password diff --git a/docs/passwordpolicyenforcer/11.2/evaluation/improving_the_password_policy.md b/docs/passwordpolicyenforcer/11.2/evaluation/improving_the_password_policy.md index e549b8c292..37d6c562f3 100644 --- a/docs/passwordpolicyenforcer/11.2/evaluation/improving_the_password_policy.md +++ b/docs/passwordpolicyenforcer/11.2/evaluation/improving_the_password_policy.md @@ -35,7 +35,7 @@ backwards**. **Step 5 –** Click **Save**. -Test the improved policy with passwords that were accepted under the previous policy. Password +Test the improved policy with passwords that the previous policy accepted. Password Policy Enforcer should reject all of them. | Password | Result | Reason | diff --git a/docs/passwordpolicyenforcer/11.2/evaluation/testing_the_password_policy.md b/docs/passwordpolicyenforcer/11.2/evaluation/testing_the_password_policy.md index 670fc1f5b8..d40ca04ee6 100644 --- a/docs/passwordpolicyenforcer/11.2/evaluation/testing_the_password_policy.md +++ b/docs/passwordpolicyenforcer/11.2/evaluation/testing_the_password_policy.md @@ -77,8 +77,8 @@ Policy Enforcer Client are also available. ## Active Directory Users / Computers Console and local Users and Groups Console Administrators often change domain passwords from the Active Directory Users and Computers console -and local passwords from the Local Users and Groups console. In fact, these consoles don't change -passwords; they reset them. This is an important distinction because a password reset: +and local passwords from the Local Users and Groups console. In fact, these consoles reset +passwords rather than change them. This is an important distinction because a password reset: - Requires privileged access - Doesn't require knowing the current password @@ -109,8 +109,8 @@ Client installed to see this information. ::: -Here are some sample passwords and expected test results when Password Policy Enforcer enforces the -Users policy. Try to +The following table shows sample passwords and expected test results when Password Policy Enforcer +enforces the Users policy. Try to change the password for the PPETestUser account to confirm that Password Policy Enforcer is enforcing the password policy correctly. diff --git a/docs/passwordpolicyenforcer/11.2/web-overview/configuration.md b/docs/passwordpolicyenforcer/11.2/web-overview/configuration.md index 04a09aa3c1..c14928fe9c 100644 --- a/docs/passwordpolicyenforcer/11.2/web-overview/configuration.md +++ b/docs/passwordpolicyenforcer/11.2/web-overview/configuration.md @@ -57,8 +57,8 @@ Enforcer to help users choose a compliant password. ![configuring_ppe_web_1](/images/passwordpolicyenforcer/11.2/web/configuring_ppe_web_1.webp) -Password Policy Enforcer Web displays the Password Policy Enforcer password policy message when a -user is prompted for their new password, and the Password Policy Enforcer rejection message if the +Password Policy Enforcer Web displays the Password Policy Enforcer password policy message when it +prompts a user for their new password, and the Password Policy Enforcer rejection message if the new password doesn't comply with the password policy. Select the **Password Policy Enforcer integration** checkbox if you have installed and configured Password Policy Enforcer on your domain controllers. diff --git a/docs/passwordpolicyenforcer/11.2/web-overview/editing_html_templates.md b/docs/passwordpolicyenforcer/11.2/web-overview/editing_html_templates.md index 33dbb44a24..c52c653b03 100644 --- a/docs/passwordpolicyenforcer/11.2/web-overview/editing_html_templates.md +++ b/docs/passwordpolicyenforcer/11.2/web-overview/editing_html_templates.md @@ -72,8 +72,8 @@ obscuring any copyright notice violates the License Agreement. ## Examples -This topic contains examples of common customizations. Use these examples to gain a better -understanding of Password Policy Enforcer Web's templates. You don't need to be an expert in HTML to +This topic contains examples of common customizations. Use these examples to better understand +Password Policy Enforcer Web's templates. You don't need to be an expert in HTML to follow these examples, but a basic understanding of HTML will help. Work through them carefully, and backup files before you edit them. The examples in this section are from the American English files, but the format is the same for all languages. @@ -85,8 +85,8 @@ default, the installer places the logo in the `\Inetpub\wwwroot\ppeweb\images\` called logo.gif. You can replace this file with one containing your organization's logo. -Your logo may appear distorted if it isn't the same size as the Netwrix logo. You can fix this by -opening en_default.htm in a text editor such as Notepad. Search for the following line, and replace the width (116) and height (69) with the dimensions of your logo in pixels. +Your logo may appear distorted if it isn't the same size as the Netwrix logo. To fix this, open +en_default.htm in a text editor such as Notepad. Search for the following line, and replace the width (116) and height (69) with the dimensions of your logo in pixels. `` @@ -137,8 +137,8 @@ information. ![using_ppe_web_2](/images/passwordpolicyenforcer/11.2/web/using_ppe_web_2.webp) You may see placeholders like %1 and %2 in some error messages. Password Policy Enforcer Web -replaces these with more information about the error. You should keep these as they provide important information about the -error, but you can delete them if you don't want them. +replaces these with more information about the error. Keep these placeholders because they provide +important information about the error, but you can delete them if you don't want them. | String | Error Message | | ----------------------- | ---------------------------------------------- | diff --git a/docs/passwordpolicyenforcer/11.2/web-overview/installationweb.md b/docs/passwordpolicyenforcer/11.2/web-overview/installationweb.md index 8fbc91b588..16af365a02 100644 --- a/docs/passwordpolicyenforcer/11.2/web-overview/installationweb.md +++ b/docs/passwordpolicyenforcer/11.2/web-overview/installationweb.md @@ -38,7 +38,7 @@ Enforcer Web documentation and tools, then click **Next**. needed. :::note -Password Policy Enforcer Web should be installed in its own virtual directory. +Install Password Policy Enforcer Web in its own virtual directory. ::: diff --git a/docs/passwordpolicyenforcer/11.2/web-overview/using_web.md b/docs/passwordpolicyenforcer/11.2/web-overview/using_web.md index 5af05573c7..b48ed33ec8 100644 --- a/docs/passwordpolicyenforcer/11.2/web-overview/using_web.md +++ b/docs/passwordpolicyenforcer/11.2/web-overview/using_web.md @@ -54,8 +54,8 @@ To change a password with Password Policy Enforcer Web: :::note Windows increments the bad password count in Active Directory every time a user enters -their old password incorrectly. This may trigger a lockout if the Windows account lockout policy is -enabled. +their old password incorrectly. This may trigger a lockout if you enable the Windows account lockout +policy. ::: @@ -67,8 +67,8 @@ value of one or more input fields and resubmitting the form. ![using_ppe_web_1](/images/passwordpolicyenforcer/11.2/web/using_ppe_web_1.webp) -Password Policy Enforcer Web shows critical errors on their own page. These errors are mostly a -result of configuration or system errors. Users can sometimes overcome a critical error by following the instructions in the +Password Policy Enforcer Web shows critical errors on their own page. Configuration or system +problems usually cause these errors. Users can sometimes overcome a critical error by following the instructions in the error message, but most critical errors are beyond the user's control. ![using_ppe_web_2](/images/passwordpolicyenforcer/11.2/web/using_ppe_web_2.webp) diff --git a/docs/passwordpolicyenforcer/11.2/web-overview/web_overview.md b/docs/passwordpolicyenforcer/11.2/web-overview/web_overview.md index a57d9fbb73..c52863bce0 100644 --- a/docs/passwordpolicyenforcer/11.2/web-overview/web_overview.md +++ b/docs/passwordpolicyenforcer/11.2/web-overview/web_overview.md @@ -24,10 +24,10 @@ Password Reset also lets users change their password from a web browser, but it features, including working in a DMZ without any domain controllers. Use Password Reset if you need to: -- Users can reset a forgotten password or unlock their account by answering questions about - themselves, such as their date of birth, first pet's name, etc. Users can access APR from the web - browser, or from the Windows Logon and Unlock screens if the APR Client is installed. -- Send e-mail alerts to users whenever their account is used in the password management system. +- Let users reset a forgotten password or unlock their account by answering questions about + themselves, such as their date of birth, first pet's name, etc. Users can access Password Reset + from a web browser, or from the Windows Logon and Unlock screens if you install the Password Reset Client. +- Send e-mail alerts to users whenever someone uses their account in the password management system. - Keep a detailed, searchable audit log of all user activity. - Separate the web server from he internal network for extra security. From 55b8d46788d4739b21efe29a7aa641c6e05f776a Mon Sep 17 00:00:00 2001 From: "james.haytko" Date: Mon, 24 Aug 2026 15:40:03 -0500 Subject: [PATCH 03/36] vale-dale aa --- .../operations/computerdetails.md | 15 +- .../operations/creategroups.md | 8 +- .../activedirectory/operations/createusers.md | 6 +- .../operations/disableenablecomputers.md | 2 +- .../operations/disableenableusers.md | 2 +- .../operations/groupdetails.md | 17 +- .../operations/groupmembership.md | 8 +- .../activedirectory/operations/moveobjects.md | 4 +- .../activedirectory/operations/operations.md | 18 +- .../operations/setresetpassword.md | 2 +- .../activedirectory/operations/sidhistory.md | 20 +- .../admin/action/activedirectory/options.md | 5 +- .../admin/action/activedirectory/overview.md | 17 +- .../admin/action/activedirectory/summary.md | 5 +- .../admin/action/activedirectory/target.md | 17 +- .../11.6/admin/action/filesystem/action.md | 16 +- .../admin/action/filesystem/appletsettings.md | 10 +- .../admin/action/filesystem/destination.md | 16 +- .../admin/action/filesystem/environment.md | 8 +- .../11.6/admin/action/filesystem/operation.md | 4 +- .../11.6/admin/action/filesystem/options.md | 40 ++- .../11.6/admin/action/filesystem/overview.md | 15 +- .../action/filesystem/parameters/addtags.md | 18 +- .../filesystem/parameters/changeowner.md | 2 +- .../parameters/changepermissioninheritance.md | 2 +- .../parameters/changepermissionsauditing.md | 2 +- .../parameters/changesharepermissions.md | 2 +- .../filesystem/parameters/parameters.md | 8 +- .../parameters/removefilepermissions.md | 2 +- .../parameters/removesharepermissions.md | 2 +- .../filesystem/parameters/removetags.md | 20 +- .../11.6/admin/action/filesystem/rollback.md | 2 +- .../11.6/admin/action/filesystem/summary.md | 5 +- .../11.6/admin/action/filesystem/target.md | 12 +- .../11.6/admin/action/libraries.md | 21 +- .../admin/action/mailbox/affectedmailboxes.md | 2 +- .../admin/action/mailbox/delegaterights.md | 8 +- .../admin/action/mailbox/folderconditions.md | 22 +- .../action/mailbox/folderidentification.md | 4 +- .../admin/action/mailbox/identification.md | 2 +- .../admin/action/mailbox/messageactions.md | 4 +- .../admin/action/mailbox/messageconditions.md | 26 +- .../11.6/admin/action/mailbox/operations.md | 2 +- .../11.6/admin/action/mailbox/overview.md | 7 +- .../11.6/admin/action/mailbox/permissions.md | 18 +- .../11.6/admin/action/mailbox/samplinghost.md | 14 +- .../11.6/admin/action/mailbox/trustedusers.md | 9 +- .../11.6/admin/action/overview.md | 38 ++- .../action/powershell/executionoptions.md | 4 +- .../11.6/admin/action/powershell/overview.md | 3 +- .../11.6/admin/action/powershell/script.md | 10 +- .../11.6/admin/action/publicfolder/action.md | 16 +- .../11.6/admin/action/publicfolder/folders.md | 4 +- .../admin/action/publicfolder/mapisettings.md | 2 +- .../admin/action/publicfolder/operations.md | 37 +-- .../admin/action/publicfolder/overview.md | 14 +- .../admin/action/publicfolder/prioractions.md | 4 +- .../admin/action/publicfolder/rollback.md | 4 +- .../11.6/admin/action/publicfolder/summary.md | 5 +- .../11.6/admin/action/registry/operations.md | 18 +- .../11.6/admin/action/registry/overview.md | 15 +- .../11.6/admin/action/registry/summary.md | 5 +- .../11.6/admin/action/registry/targethosts.md | 4 +- .../11.6/admin/action/sendmail/message.md | 10 +- .../11.6/admin/action/sendmail/overview.md | 8 +- .../11.6/admin/action/sendmail/properties.md | 6 +- .../11.6/admin/action/sendmail/summary.md | 5 +- .../11.6/admin/action/sendmail/viewstatus.md | 2 +- .../admin/action/servicenow/authentication.md | 4 +- .../admin/action/servicenow/description.md | 6 +- .../action/servicenow/incidentcreation.md | 10 +- .../11.6/admin/action/servicenow/overview.md | 28 +- .../11.6/admin/action/servicenow/summary.md | 5 +- .../11.6/admin/action/survey/htmlstyle.md | 4 +- .../11.6/admin/action/survey/introduction.md | 4 +- .../11.6/admin/action/survey/mailmessage.md | 18 +- .../admin/action/survey/mailproperties.md | 4 +- .../11.6/admin/action/survey/overview.md | 10 +- .../11.6/admin/action/survey/questions.md | 6 +- .../11.6/admin/action/survey/testsurvey.md | 4 +- .../admin/action/webrequest/destination.md | 14 +- .../11.6/admin/action/webrequest/header.md | 6 +- .../11.6/admin/action/webrequest/overview.md | 8 +- .../admin/action/webrequest/parameters.md | 14 +- .../11.6/admin/action/webrequest/summary.md | 5 +- .../11.6/admin/analysis/autoaction.md | 9 +- .../admin/analysis/businessrules/appliesto.md | 12 +- .../admin/analysis/businessrules/logic.md | 24 +- .../admin/analysis/businessrules/overview.md | 6 +- .../changedetection/additionalfields.md | 2 +- .../admin/analysis/changedetection/input.md | 5 +- .../analysis/changedetection/inputscope.md | 5 +- .../admin/analysis/changedetection/options.md | 4 +- .../analysis/changedetection/overview.md | 4 +- .../admin/analysis/changedetection/summary.md | 4 +- .../admin/analysis/notification/changetype.md | 4 +- .../analysis/notification/commandline.md | 8 +- .../admin/analysis/notification/criteria.md | 4 +- .../admin/analysis/notification/eventlog.md | 6 +- .../11.6/admin/analysis/notification/hosts.md | 14 +- .../admin/analysis/notification/overview.md | 2 +- .../11.6/admin/analysis/notification/smtp.md | 18 +- .../admin/analysis/notification/summary.md | 5 +- .../admin/analysis/notification/timewindow.md | 4 +- .../11.6/admin/analysis/overview.md | 34 +-- .../11.6/admin/analysis/sqlscripting.md | 29 +- .../admin/analysis/sqlviewcreation/columns.md | 12 +- .../admin/analysis/sqlviewcreation/export.md | 6 +- .../admin/analysis/sqlviewcreation/filter.md | 4 +- .../admin/analysis/sqlviewcreation/input.md | 10 +- .../analysis/sqlviewcreation/inputscope.md | 2 +- .../analysis/sqlviewcreation/joincolumns.md | 18 +- .../analysis/sqlviewcreation/overview.md | 6 +- .../admin/analysis/sqlviewcreation/result.md | 5 +- .../sqlviewcreation/resultconstraints.md | 8 +- .../analysis/sqlviewcreation/resultsample.md | 4 +- .../admin/analysis/sqlviewcreation/summary.md | 5 +- .../analysis/sqlviewcreation/timewindow.md | 6 +- .../11.6/admin/analysis/vbscripting.md | 8 +- .../datacollector/activedirectory/options.md | 4 +- .../datacollector/activedirectory/overview.md | 10 +- .../datacollector/activedirectory/results.md | 6 +- .../datacollector/activedirectory/summary.md | 5 +- .../datacollector/adactivity/category.md | 2 +- .../datacollector/adactivity/cleartables.md | 6 +- .../datacollector/adactivity/connection.md | 10 +- .../datacollector/adactivity/overview.md | 6 +- .../admin/datacollector/adactivity/results.md | 7 +- .../admin/datacollector/adactivity/scope.md | 8 +- .../admin/datacollector/adactivity/share.md | 6 +- .../adactivity/standardtables.md | 4 +- .../admin/datacollector/adactivity/summary.md | 7 +- .../datacollector/adinventory/category.md | 2 +- .../datacollector/adinventory/cleartables.md | 10 +- .../adinventory/customattributes.md | 41 ++- .../adinventory/indexupdateoptions.md | 4 +- .../datacollector/adinventory/options.md | 18 +- .../datacollector/adinventory/overview.md | 18 +- .../datacollector/adinventory/results.md | 12 +- .../adinventory/standardtables.md | 4 +- .../datacollector/adinventory/summary.md | 7 +- .../datacollector/adpermissions/category.md | 3 +- .../adpermissions/customfilter.md | 8 +- .../datacollector/adpermissions/overview.md | 10 +- .../adpermissions/removetables.md | 14 +- .../datacollector/adpermissions/results.md | 7 +- .../datacollector/adpermissions/scope.md | 2 +- .../adpermissions/standardtables.md | 2 +- .../datacollector/adpermissions/summary.md | 7 +- .../11.6/admin/datacollector/aws/criteria.md | 12 +- .../admin/datacollector/aws/droptables.md | 7 +- .../datacollector/aws/filters3objects.md | 8 +- .../admin/datacollector/aws/loginroles.md | 4 +- .../11.6/admin/datacollector/aws/overview.md | 13 +- .../11.6/admin/datacollector/aws/results.md | 7 +- .../admin/datacollector/aws/sensitivedata.md | 6 +- .../11.6/admin/datacollector/aws/summary.md | 5 +- .../azureadinventory/category.md | 2 +- .../azureadinventory/configurejob.md | 12 +- .../azureadinventory/customattributes.md | 18 +- .../azureadinventory/overview.md | 6 +- .../datacollector/azureadinventory/results.md | 11 +- .../azureadinventory/standardtables.md | 6 +- .../datacollector/azureadinventory/summary.md | 7 +- .../azureadinventory/troubleshooting.md | 8 +- .../box/activityoperationscope.md | 8 +- .../box/activitytimeframescope.md | 4 +- .../datacollector/box/additionalscoping.md | 4 +- .../admin/datacollector/box/authenticate.md | 2 +- .../admin/datacollector/box/exclusions.md | 8 +- .../11.6/admin/datacollector/box/overview.md | 15 +- .../11.6/admin/datacollector/box/results.md | 7 +- .../admin/datacollector/box/scopebyuser.md | 10 +- .../admin/datacollector/box/standardtables.md | 4 +- .../11.6/admin/datacollector/box/summary.md | 7 +- .../commandlineutility/definefields.md | 4 +- .../commandlineutility/overview.md | 12 +- .../commandlineutility/profileparameters.md | 4 +- .../commandlineutility/profiletype.md | 6 +- .../commandlineutility/results.md | 8 +- .../commandlineutility/scripteditor.md | 12 +- .../commandlineutility/summary.md | 7 +- .../admin/datacollector/diskinfo/overview.md | 10 +- .../admin/datacollector/diskinfo/results.md | 8 +- .../admin/datacollector/diskinfo/summary.md | 5 +- .../datacollector/diskinfo/targetdisks.md | 4 +- .../11.6/admin/datacollector/dns/overview.md | 6 +- .../11.6/admin/datacollector/dns/results.md | 8 +- .../11.6/admin/datacollector/dns/summary.md | 5 +- .../datacollector/dropboxaccess/completion.md | 11 +- .../dropboxaccess/configurejob.md | 8 +- .../dropboxaccess/dlpauditsettings.md | 10 +- .../datacollector/dropboxaccess/overview.md | 21 +- .../dropboxaccess/scanoptions.md | 12 +- .../dropboxaccess/selectdlpcriteria.md | 10 +- .../dropboxaccess/standardtables.md | 4 +- .../11.6/admin/datacollector/eventlog.md | 20 +- .../datacollector/ewsmailbox/category.md | 2 +- .../datacollector/ewsmailbox/criteria.md | 8 +- .../admin/datacollector/ewsmailbox/filter.md | 12 +- .../admin/datacollector/ewsmailbox/options.md | 2 +- .../datacollector/ewsmailbox/overview.md | 13 +- .../admin/datacollector/ewsmailbox/results.md | 2 +- .../admin/datacollector/ewsmailbox/scope.md | 4 +- .../datacollector/ewsmailbox/scopeselect.md | 4 +- .../datacollector/ewsmailbox/sddoptions.md | 4 +- .../ewsmailbox/searchfilter/bodyoptions.md | 2 +- .../searchfilter/folderconditions.md | 8 +- .../searchfilter/messageconditions.md | 14 +- .../ewsmailbox/searchfilter/searchfilter_1.md | 10 +- .../admin/datacollector/ewsmailbox/summary.md | 5 +- .../ewspublicfolder/critieria.md | 4 +- .../datacollector/ewspublicfolder/filter.md | 21 +- .../datacollector/ewspublicfolder/options.md | 2 +- .../datacollector/ewspublicfolder/overview.md | 10 +- .../datacollector/ewspublicfolder/results.md | 8 +- .../searchfilter/bodyoptions.md | 4 +- .../searchfilter/folderconditions.md | 13 +- .../searchfilter/messageconditions.md | 17 +- .../searchfilter/searchfilter_1.md | 8 +- .../datacollector/ewspublicfolder/summary.md | 5 +- .../datacollector/exchange2k/category.md | 2 +- .../datacollector/exchange2k/mapisettings.md | 6 +- .../admin/datacollector/exchange2k/options.md | 8 +- .../datacollector/exchange2k/overview.md | 10 +- .../admin/datacollector/exchange2k/results.md | 6 +- .../admin/datacollector/exchange2k/scope.md | 2 +- .../admin/datacollector/exchange2k/summary.md | 5 +- .../datacollector/exchangemailbox/options.md | 8 +- .../datacollector/exchangemailbox/overview.md | 26 +- .../exchangemailbox/properties.md | 6 +- .../datacollector/exchangemailbox/scope.md | 14 +- .../exchangemailbox/sddcriteria.md | 22 +- .../datacollector/exchangemailbox/summary.md | 5 +- .../datacollector/exchangemetrics/category.md | 2 +- .../exchangemetrics/collectmode.md | 6 +- .../exchangemetrics/messageactivityfilter.md | 18 +- .../exchangemetrics/messagesizes.md | 12 +- .../datacollector/exchangemetrics/options.md | 8 +- .../datacollector/exchangemetrics/overview.md | 8 +- .../datacollector/exchangemetrics/results.md | 8 +- .../datacollector/exchangemetrics/scope.md | 10 +- .../datacollector/exchangemetrics/summary.md | 5 +- .../exchangemetrics/timeframes.md | 12 +- .../datacollector/exchangeps/category.md | 56 ++-- .../datacollector/exchangeps/configurejob.md | 24 +- .../datacollector/exchangeps/filtermessage.md | 20 +- .../datacollector/exchangeps/mailboxlogons.md | 8 +- .../datacollector/exchangeps/mailflow.md | 2 +- .../admin/datacollector/exchangeps/options.md | 10 +- .../datacollector/exchangeps/overview.md | 20 +- .../admin/datacollector/exchangeps/results.md | 6 +- .../admin/datacollector/exchangeps/scope.md | 11 +- .../exchangeps/scopedatabases.md | 14 +- .../exchangeps/scopemailboxes.md | 10 +- .../exchangeps/scopepublicfolders.md | 16 +- .../admin/datacollector/exchangeps/summary.md | 9 +- .../exchangepublicfolder/category.md | 2 +- .../exchangepublicfolder/options.md | 4 +- .../exchangepublicfolder/overview.md | 20 +- .../exchangepublicfolder/probableowner.md | 14 +- .../exchangepublicfolder/properties.md | 6 +- .../exchangepublicfolder/scope.md | 24 +- .../exchangepublicfolder/summary.md | 5 +- .../11.6/admin/datacollector/file/category.md | 4 +- .../11.6/admin/datacollector/file/overview.md | 8 +- .../11.6/admin/datacollector/file/results.md | 14 +- .../admin/datacollector/file/targetfiles.md | 4 +- .../datacollector/fsaa/activitysettings.md | 28 +- .../fsaa/appletsettings/appletsettings.md | 4 +- .../datacollector/fsaa/azuretenantmapping.md | 8 +- .../admin/datacollector/fsaa/bulkimport.md | 4 +- .../certificatemanagement.md | 42 ++- .../manualcertificate.md | 18 +- .../defaultscopingoptions.md | 7 +- .../fsaa/defaultscopingoptions/filedetails.md | 13 +- .../defaultscopingoptions/fileproperties.md | 4 +- .../defaultscopingoptions/scansettings.md | 20 +- .../datacollector/fsaa/queryselection.md | 14 +- .../datacollector/fsaa/scanserverselection.md | 4 +- .../admin/datacollector/fsaa/scansettings.md | 18 +- .../datacollector/fsaa/scopingoptions.md | 8 +- .../datacollector/fsaa/scopingqueries.md | 8 +- .../fsaa/sensitivedatasettings.md | 4 +- .../datacollector/fsaa/standardtables.md | 4 +- .../admin/datacollector/fsaa/workflows.md | 50 ++-- .../datacollector/grouppolicy/category.md | 16 +- .../datacollector/grouppolicy/options.md | 6 +- .../datacollector/grouppolicy/overview.md | 10 +- .../datacollector/grouppolicy/policieslist.md | 10 +- .../datacollector/grouppolicy/summary.md | 5 +- .../admin/datacollector/grouppolicy/target.md | 8 +- .../admin/datacollector/inifile/overview.md | 4 +- .../admin/datacollector/inifile/properties.md | 9 +- .../admin/datacollector/inifile/summary.md | 7 +- .../datacollector/inifile/targetfiles.md | 6 +- .../11.6/admin/datacollector/ldap.md | 31 +- .../11.6/admin/datacollector/nis/category.md | 2 +- .../admin/datacollector/nis/configurejob.md | 14 +- .../11.6/admin/datacollector/nis/overview.md | 6 +- .../11.6/admin/datacollector/nis/query.md | 4 +- .../11.6/admin/datacollector/nis/results.md | 14 +- .../11.6/admin/datacollector/nis/settings.md | 4 +- .../admin/datacollector/nis/sidmappings.md | 9 +- .../admin/datacollector/nis/standardtables.md | 9 +- .../11.6/admin/datacollector/nis/summary.md | 7 +- .../admin/datacollector/nosql/category.md | 6 +- .../admin/datacollector/nosql/configurejob.md | 18 +- .../admin/datacollector/nosql/criteria.md | 14 +- .../11.6/admin/datacollector/nosql/filter.md | 26 +- .../11.6/admin/datacollector/nosql/options.md | 20 +- .../admin/datacollector/nosql/overview.md | 12 +- .../11.6/admin/datacollector/nosql/results.md | 6 +- .../11.6/admin/datacollector/nosql/summary.md | 9 +- .../11.6/admin/datacollector/overview.md | 46 +-- .../passwordsecurity/dictionaries.md | 30 +- .../passwordsecurity/overview.md | 4 +- .../datacollector/passwordsecurity/results.md | 6 +- .../datacollector/passwordsecurity/summary.md | 6 +- .../admin/datacollector/permissionmatrix.md | 19 +- .../datacollector/powershell/editquery.md | 15 +- .../admin/datacollector/powershell/options.md | 6 +- .../datacollector/powershell/overview.md | 4 +- .../admin/datacollector/powershell/results.md | 2 +- .../datacollector/powershell/sampleserver.md | 6 +- .../admin/datacollector/powershell/summary.md | 6 +- .../11.6/admin/datacollector/registry.md | 35 +-- .../11.6/admin/datacollector/script/add.md | 10 +- .../11.6/admin/datacollector/script/editor.md | 12 +- .../admin/datacollector/script/example1.md | 27 +- .../admin/datacollector/script/example2.md | 18 +- .../datacollector/script/methodsproperties.md | 2 +- .../admin/datacollector/script/overview.md | 9 +- .../admin/datacollector/script/properties.md | 53 ++-- .../admin/datacollector/script/reference.md | 12 +- .../11.6/admin/datacollector/script/run.md | 8 +- .../11.6/admin/datacollector/services.md | 16 +- .../smartlog/collectionmethod.md | 18 +- .../admin/datacollector/smartlog/criteria.md | 19 +- .../datacollector/smartlog/eventlogoptions.md | 4 +- .../admin/datacollector/smartlog/logstate.md | 10 +- .../admin/datacollector/smartlog/logtype.md | 10 +- .../admin/datacollector/smartlog/overview.md | 10 +- .../admin/datacollector/smartlog/results.md | 5 +- .../datacollector/smartlog/samplehost.md | 12 +- .../admin/datacollector/smartlog/summary.md | 4 +- .../smartlog/targetlog/filedetectionlog.md | 4 +- .../smartlog/targetlog/targetlog.md | 8 +- .../smartlog/targetlog/windowseventlog.md | 4 +- .../datacollector/spaa/activitydatescope.md | 10 +- .../spaa/activityloglocations.md | 12 +- .../datacollector/spaa/additionalscoping.md | 26 +- .../admin/datacollector/spaa/agentsettings.md | 8 +- .../datacollector/spaa/bulkimportsettings.md | 6 +- .../11.6/admin/datacollector/spaa/category.md | 6 +- .../admin/datacollector/spaa/configurejob.md | 40 +-- .../datacollector/spaa/dlpauditsettings.md | 30 +- .../admin/datacollector/spaa/droptables.md | 12 +- .../11.6/admin/datacollector/spaa/overview.md | 22 +- .../11.6/admin/datacollector/spaa/results.md | 11 +- .../datacollector/spaa/scanscopingoptions.md | 22 +- .../datacollector/spaa/selectdlpcriteria.md | 20 +- .../11.6/admin/datacollector/spaa/settings.md | 61 ++-- .../datacollector/spaa/standardtables.md | 4 +- .../11.6/admin/datacollector/spaa/summary.md | 6 +- .../admin/datacollector/spaa/testaccess.md | 8 +- .../11.6/admin/datacollector/sql/category.md | 6 +- .../admin/datacollector/sql/configurejob.md | 35 +-- .../11.6/admin/datacollector/sql/criteria.md | 12 +- .../datacollector/sql/customqueryoracle.md | 4 +- .../admin/datacollector/sql/customquerysql.md | 4 +- .../11.6/admin/datacollector/sql/filter.md | 30 +- .../11.6/admin/datacollector/sql/options.md | 14 +- .../11.6/admin/datacollector/sql/overview.md | 24 +- .../11.6/admin/datacollector/sql/results.md | 6 +- .../11.6/admin/datacollector/sql/rowkey.md | 6 +- .../11.6/admin/datacollector/sql/settings.md | 2 +- .../11.6/admin/datacollector/sql/summary.md | 5 +- .../datacollector/systeminfo/filetypes.md | 6 +- .../datacollector/systeminfo/jobscope.md | 2 +- .../admin/datacollector/systeminfo/options.md | 6 +- .../datacollector/systeminfo/overview.md | 9 +- .../datacollector/systeminfo/probableowner.md | 6 +- .../admin/datacollector/systeminfo/results.md | 10 +- .../admin/datacollector/systeminfo/summary.md | 6 +- .../datacollector/systeminfo/vipmembership.md | 4 +- .../textsearch/advancedcriteria.md | 10 +- .../datacollector/textsearch/overview.md | 9 +- .../admin/datacollector/textsearch/results.md | 8 +- .../textsearch/searchcriteria.md | 4 +- .../datacollector/textsearch/sourcefiles.md | 16 +- .../admin/datacollector/textsearch/summary.md | 6 +- .../admin/datacollector/unix/editscript.md | 2 +- .../11.6/admin/datacollector/unix/input.md | 4 +- .../11.6/admin/datacollector/unix/overview.md | 5 +- .../11.6/admin/datacollector/unix/results.md | 12 +- .../datacollector/usersgroups/overview.md | 7 +- .../usersgroups/results/groups.md | 2 +- .../usersgroups/results/results.md | 4 +- .../usersgroups/results/security.md | 4 +- .../usersgroups/results/users.md | 8 +- .../datacollector/usersgroups/summary.md | 6 +- .../datacollector/wmicollector/classes.md | 6 +- .../datacollector/wmicollector/overview.md | 10 +- .../datacollector/wmicollector/properties.md | 6 +- .../datacollector/wmicollector/samplehost.md | 8 +- .../datacollector/wmicollector/summary.md | 5 +- .../11.6/admin/hostdiscovery/activities.md | 8 +- .../11.6/admin/hostdiscovery/log.md | 10 +- .../11.6/admin/hostdiscovery/overview.md | 4 +- .../11.6/admin/hostdiscovery/queries.md | 8 +- .../wizard/addomaincontrollers.md | 20 +- .../admin/hostdiscovery/wizard/adexchange.md | 20 +- .../admin/hostdiscovery/wizard/adgeneral.md | 22 +- .../11.6/admin/hostdiscovery/wizard/csv.md | 18 +- .../admin/hostdiscovery/wizard/database.md | 30 +- .../admin/hostdiscovery/wizard/ipnetwork.md | 26 +- .../admin/hostdiscovery/wizard/overview.md | 12 +- .../11.6/admin/hostmanagement/actions/add.md | 20 +- .../hostmanagement/actions/deletehost.md | 24 +- .../hostmanagement/actions/deletelist.md | 16 +- .../admin/hostmanagement/actions/editlist.md | 2 +- .../admin/hostmanagement/actions/editquery.md | 4 +- .../admin/hostmanagement/actions/export.md | 2 +- .../hostmanagement/actions/importhost.md | 30 +- .../hostmanagement/actions/importlocation.md | 35 ++- .../admin/hostmanagement/actions/overview.md | 6 +- .../admin/hostmanagement/actions/refresh.md | 4 +- .../admin/hostmanagement/actions/rename.md | 4 +- .../hostmanagement/actions/savetolist.md | 4 +- .../admin/hostmanagement/actions/saveview.md | 12 +- .../admin/hostmanagement/actions/suspend.md | 2 +- .../11.6/admin/hostmanagement/datagrid.md | 6 +- .../11.6/admin/hostmanagement/lists.md | 18 +- .../11.6/admin/hostmanagement/overview.md | 6 +- .../11.6/admin/jobs/features.md | 36 +-- .../11.6/admin/jobs/group/overview.md | 28 +- .../admin/jobs/group/settings/connection.md | 6 +- .../11.6/admin/jobs/group/settings/history.md | 6 +- .../group/settings/hostlistsassignment.md | 14 +- .../admin/jobs/group/settings/reporting.md | 4 +- .../admin/jobs/group/settings/settings.md | 22 +- .../11.6/admin/jobs/group/settings/storage.md | 4 +- .../11.6/admin/jobs/instantiate.md | 16 +- .../ad_passwordexpirationnotification.md | 84 +++--- .../instantjobs/ex_registerazureappauth.md | 18 +- .../admin/jobs/instantjobs/fs_defend_sdd.md | 8 +- .../jobs/instantjobs/fs_migrateschema.md | 42 +-- .../11.6/admin/jobs/instantjobs/overview.md | 18 +- .../instantjobs/sas_executionstatistics.md | 4 +- .../instantjobs/sp_registerazureappauth.md | 20 +- .../admin/jobs/instantjobs/sp_removehost.md | 4 +- .../11.6/admin/jobs/job/configure/actions.md | 6 +- .../jobs/job/configure/analysis/analysis.md | 6 +- .../analysiscustomizableparameters.md | 10 +- .../11.6/admin/jobs/job/configure/hosts.md | 12 +- .../11.6/admin/jobs/job/configure/overview.md | 10 +- .../11.6/admin/jobs/job/configure/queries.md | 33 ++- .../11.6/admin/jobs/job/configure/reports.md | 16 +- .../11.6/admin/jobs/job/create.md | 14 +- .../11.6/admin/jobs/job/disableenable.md | 37 ++- .../11.6/admin/jobs/job/overview.md | 53 ++-- .../admin/jobs/job/properties/autoretry.md | 4 +- .../admin/jobs/job/properties/connection.md | 12 +- .../11.6/admin/jobs/job/properties/general.md | 13 +- .../11.6/admin/jobs/job/properties/history.md | 6 +- .../admin/jobs/job/properties/notification.md | 8 +- .../admin/jobs/job/properties/overview.md | 8 +- .../admin/jobs/job/properties/performance.md | 17 +- .../admin/jobs/job/properties/reportroles.md | 33 ++- .../jobs/job/properties/reportsettings.md | 8 +- .../11.6/admin/jobs/job/properties/storage.md | 6 +- .../11.6/admin/jobs/job/properties/viewxml.md | 4 +- .../11.6/admin/jobs/job/results.md | 30 +- .../11.6/admin/jobs/job/status.md | 19 +- .../11.6/admin/jobs/overview.md | 45 +-- .../11.6/admin/maintenance/backuprecovery.md | 28 +- .../11.6/admin/maintenance/bestpractices.md | 39 ++- .../11.6/admin/maintenance/troubleshooting.md | 20 +- .../11.6/admin/maintenance/updatepasswords.md | 23 +- .../11.6/admin/navigate/activitiespane.md | 6 +- .../11.6/admin/navigate/datagrid.md | 84 +++--- .../11.6/admin/navigate/overview.md | 10 +- .../11.6/admin/navigate/pane.md | 16 +- .../accessanalyzer/11.6/admin/navigate/top.md | 2 +- docs/accessanalyzer/11.6/admin/overview.md | 21 +- .../11.6/admin/report/cleanup.md | 20 +- .../11.6/admin/report/create.md | 26 +- docs/accessanalyzer/11.6/admin/report/edit.md | 19 +- .../report/interactivegrids/copyingcells.md | 6 +- .../admin/report/interactivegrids/grouping.md | 8 +- .../admin/report/interactivegrids/overview.md | 10 +- .../admin/report/interactivegrids/paging.md | 8 +- .../report/interactivegrids/searchfilter.md | 22 +- .../11.6/admin/report/overview.md | 12 +- docs/accessanalyzer/11.6/admin/report/tags.md | 18 +- docs/accessanalyzer/11.6/admin/report/view.md | 10 +- .../11.6/admin/report/wizard/authoring.md | 16 +- .../11.6/admin/report/wizard/email.md | 10 +- .../11.6/admin/report/wizard/layout.md | 17 +- .../11.6/admin/report/wizard/overview.md | 14 +- .../admin/report/wizard/publishsecurity.md | 10 +- .../11.6/admin/report/wizard/widgets.md | 26 +- .../11.6/admin/runninginstances/jobdetails.md | 7 +- .../11.6/admin/runninginstances/overview.md | 14 +- .../11.6/admin/schedule/overview.md | 6 +- .../11.6/admin/schedule/wizard.md | 24 +- .../admin/schema/fsaadc/views/overview.md | 4 +- .../admin/schema/sqldc/coretables/overview.md | 6 +- .../schema/sqldc/enumeration/overview.md | 10 +- .../11.6/admin/schema/sqldc/overview.md | 272 +++++++++--------- .../schema/sqldc/reportingtables/overview.md | 8 +- .../11.6/admin/schema/sqldc/views/overview.md | 2 +- .../11.6/admin/settings/access/overview.md | 10 +- .../access/restapi/assignappaccess.md | 17 +- .../admin/settings/access/restapi/getdata.md | 12 +- .../settings/access/restapi/obtaintoken.md | 16 +- .../admin/settings/access/restapi/overview.md | 4 +- .../access/restapi/powershellcommands.md | 2 +- .../settings/access/restapi/refreshtoken.md | 16 +- .../settings/access/rolebased/assignroles.md | 58 ++-- .../access/rolebased/configureroles.md | 40 +-- .../settings/access/rolebased/customroles.md | 26 +- .../admin/settings/access/rolebased/faq.md | 58 ++-- .../settings/access/rolebased/overview.md | 46 +-- .../access/rolebased/roledefinitions.md | 39 +-- .../rolebased/scheduleserviceaccount.md | 28 +- .../access/rolebased/securereports.md | 22 +- .../settings/access/rolebased/workflow.md | 22 +- .../admin/settings/application/overview.md | 69 ++--- .../11.6/admin/settings/application/vault.md | 42 +-- .../connection/create/activedirectory.md | 12 +- .../admin/settings/connection/create/aws.md | 10 +- .../settings/connection/create/create.md | 61 ++-- .../connection/create/exchangemodernauth.md | 4 +- .../connection/create/localwindows.md | 10 +- .../settings/connection/create/oracle.md | 22 +- .../admin/settings/connection/create/sql.md | 4 +- .../admin/settings/connection/create/task.md | 8 +- .../admin/settings/connection/create/unix.md | 4 +- .../connection/cyberarkintegration.md | 59 ++-- .../11.6/admin/settings/connection/gmsa.md | 4 +- .../admin/settings/connection/overview.md | 12 +- .../11.6/admin/settings/exchange.md | 37 ++- .../11.6/admin/settings/history.md | 36 +-- .../11.6/admin/settings/hostdiscovery.md | 14 +- .../11.6/admin/settings/hostinventory.md | 45 ++- .../11.6/admin/settings/notification.md | 45 +-- .../11.6/admin/settings/overview.md | 18 +- .../11.6/admin/settings/reporting.md | 45 +-- .../11.6/admin/settings/schedule.md | 72 ++--- .../admin/settings/sensitivedata/criteria.md | 12 +- .../settings/sensitivedata/exclusions/add.md | 6 +- .../sensitivedata/exclusions/delete.md | 4 +- .../settings/sensitivedata/exclusions/edit.md | 4 +- .../sensitivedata/exclusions/export.md | 8 +- .../sensitivedata/exclusions/import.md | 15 +- .../sensitivedata/exclusions/overview.md | 12 +- .../admin/settings/sensitivedata/overview.md | 2 +- .../11.6/admin/settings/servicenow.md | 14 +- .../11.6/admin/settings/storage/add.md | 20 +- .../11.6/admin/settings/storage/default.md | 20 +- .../11.6/admin/settings/storage/delete.md | 8 +- .../11.6/admin/settings/storage/overview.md | 19 +- .../11.6/admin/settings/storage/updateauth.md | 6 +- docs/accessanalyzer/11.6/cdsa/job.md | 14 +- docs/accessanalyzer/11.6/cdsa/overview.md | 4 +- docs/accessanalyzer/11.6/cdsa/presentation.md | 2 +- docs/accessanalyzer/11.6/gettingstarted.md | 38 +-- docs/accessanalyzer/11.6/index.md | 22 +- .../install/application/database/database.md | 76 ++--- .../application/database/otherlanguages.md | 42 +-- .../11.6/install/application/firstlaunch.md | 47 +-- .../11.6/install/application/overview.md | 6 +- .../11.6/install/application/reports/adfs.md | 22 +- .../install/application/reports/disclaimer.md | 10 +- .../install/application/reports/domains.md | 12 +- .../install/application/reports/entraidsso.md | 30 +- .../application/reports/kerberosencryption.md | 36 +-- .../11.6/install/application/reports/okta.md | 18 +- .../install/application/reports/overview.md | 20 +- .../install/application/reports/secure.md | 60 ++-- .../11.6/install/application/reports/sso.md | 22 +- .../install/application/reports/timeout.md | 10 +- .../11.6/install/application/updatelicense.md | 24 +- .../install/application/upgrade/overview.md | 19 +- .../upgrade/solutionconsiderations.md | 52 ++-- .../install/application/upgrade/wizard.md | 97 ++++--- .../11.6/install/application/wizard.md | 16 +- .../filesystemproxy/configuredatacollector.md | 2 +- .../11.6/install/filesystemproxy/overview.md | 86 +++--- .../install/filesystemproxy/silentinstall.md | 24 +- .../filesystemproxy/troubleshooting.md | 10 +- .../11.6/install/filesystemproxy/uninstall.md | 14 +- .../11.6/install/filesystemproxy/upgrade.md | 16 +- .../11.6/install/filesystemproxy/wizard.md | 28 +- docs/accessanalyzer/11.6/install/overview.md | 4 +- .../sensitivedatadiscovery/overview.md | 4 +- .../install/sensitivedatadiscovery/upgrade.md | 2 +- .../install/sensitivedatadiscovery/wizard.md | 26 +- .../11.6/install/sharepointagent/overview.md | 16 +- .../11.6/install/sharepointagent/upgrade.md | 8 +- .../11.6/install/sharepointagent/wizard.md | 6 +- .../appendix.md | 17 +- .../stealthaudit_mapi_cdo_installation.md | 24 +- .../activedirectory/activedirectory.md | 4 +- .../activedirectory/activedirectory/access.md | 28 +- .../activedirectory/activity/activity.md | 81 +++--- .../activedirectory/activity/filearchive.md | 36 +-- .../activity/threatprevention.md | 29 +- .../activedirectory/overview.md | 24 +- .../11.6/requirements/aws/aws.md | 13 +- .../11.6/requirements/aws/configurescans.md | 45 ++- .../11.6/requirements/aws/target.md | 8 +- .../11.6/requirements/box/target.md | 2 +- .../11.6/requirements/databases/databases.md | 19 +- .../11.6/requirements/databases/db2.md | 4 +- .../11.6/requirements/databases/mongodb.md | 2 +- .../11.6/requirements/databases/mysql.md | 2 +- .../databases/oracle/leastprivilege.md | 55 ++-- .../requirements/databases/oracle/oracle.md | 2 +- .../11.6/requirements/databases/postgresql.md | 2 +- .../11.6/requirements/databases/redshift.md | 2 +- .../requirements/databases/sql/azuresql.md | 18 +- .../databases/sql/azuresqlaccess.md | 41 ++- .../11.6/requirements/databases/sql/sql.md | 4 +- .../11.6/requirements/dropbox/dropbox.md | 4 +- .../11.6/requirements/dropbox/target.md | 10 +- .../requirements/entraid/entraid/access.md | 44 +-- .../requirements/entraid/entraid/overview.md | 4 +- .../11.6/requirements/exchange/exchange.md | 6 +- .../exchange/exchangeonline/access.md | 54 ++-- .../exchange/exchangeonline/exchangeonline.md | 2 +- .../requirements/exchange/support/mailflow.md | 8 +- .../requirements/exchange/support/mapi.md | 2 +- .../exchange/support/powershell.md | 57 ++-- .../exchange/support/remoteconnections.md | 4 +- .../exchange/support/webservicesapi.md | 2 +- .../11.6/requirements/exchange/target.md | 12 +- .../requirements/filesystem/filesystem.md | 22 +- .../filesystems/azureinformationprotection.md | 28 +- .../filesystems/dellcelerravnx/access.md | 4 +- .../dellcelerravnx/activity/activity.md | 22 +- .../dellcelerravnx/activity/installcee.md | 42 +-- .../dellcelerravnx/activity/validate.md | 19 +- .../filesystems/dellcelerravnx/overview.md | 4 +- .../dellpowerscale/activity/activity.md | 24 +- .../dellpowerscale/activity/installcee.md | 14 +- .../activity/manualconfiguration.md | 24 +- .../dellpowerscale/activity/validate.md | 22 +- .../filesystems/dellpowerscale/overview.md | 12 +- .../filesystems/dellunity/access.md | 2 +- .../dellunity/activity/activity.md | 16 +- .../dellunity/activity/installcee.md | 16 +- .../dellunity/activity/setupunisphere.md | 6 +- .../dellunity/activity/validate.md | 19 +- .../filesystems/dellunity/overview.md | 4 +- .../filesystem/filesystems/filesystems.md | 4 +- .../filesystems/hitachi/activity/activity.md | 8 +- .../hitachi/activity/configureaccesstologs.md | 6 +- .../hitachi/activity/configurelogs.md | 4 +- .../filesystems/hitachi/overview.md | 2 +- .../filesystem/filesystems/nasuni/access.md | 21 +- .../filesystem/filesystems/nasuni/activity.md | 26 +- .../filesystem/filesystems/nasuni/overview.md | 4 +- .../filesystems/netapp7mode/access/access.md | 2 +- .../netapp7mode/access/provisionaccess.md | 6 +- .../netapp7mode/activity/activity.md | 10 +- .../netapp7mode/activity/configurefpolicy.md | 16 +- .../netapp7mode/activity/customizefpolicy.md | 2 +- .../netapp7mode/activity/enablehttp.md | 6 +- .../netapp7mode/activity/provisionactivity.md | 7 +- .../filesystems/netapp7mode/overview.md | 4 +- .../filesystems/netappcmode/access/access.md | 43 ++- .../access/configureemptyfpolicy.md | 51 ++-- .../netappcmode/activity/activity.md | 20 +- .../netappcmode/activity/configurefirewall.md | 16 +- .../netappcmode/activity/configurefpolicy.md | 81 +++--- .../netappcmode/activity/provisionactivity.md | 12 +- .../filesystems/netappcmode/overview.md | 4 +- .../filesystem/filesystems/nutanix/access.md | 2 +- .../filesystems/nutanix/overview.md | 2 +- .../filesystem/filesystems/qumulo/activity.md | 2 +- .../filesystem/filesystems/qumulo/overview.md | 2 +- .../filesystems/windowsfile/access.md | 16 +- .../filesystems/windowsfile/activity.md | 14 +- .../filesystems/windowsfile/overview.md | 2 +- .../appletmodescans/appletmodepermissions.md | 10 +- .../appletmodescans/appletmodeports.md | 2 +- .../localmodescans/localmodepermissions.md | 10 +- .../localmodescans/localmodeports.md | 2 +- .../asaservice/proxymodeserviceports.md | 4 +- .../proxymodescans/proxymodeserver.md | 16 +- .../withapplet/proxymodeappletpermissions.md | 6 +- .../withapplet/proxymodeappletports.md | 4 +- .../filesystem/scanoptions/scanoptions.md | 22 +- .../11.6/requirements/overview.md | 16 +- .../agentbasedscans/agentpermissions.md | 30 +- .../scanoptions/agentbasedscans/agentports.md | 2 +- .../sharepoint/scanoptions/scanoptions.md | 29 +- .../requirements/sharepoint/sharepoint.md | 36 ++- .../sharepoint/sharepoint/sharepoint.md | 2 +- .../sharepoint/sharepoint/access.md | 19 +- .../sharepoint/sharepoint/activity.md | 4 +- .../sharepoint/sharepoint/overview.md | 12 +- .../sharepoint/sharepointonline/access.md | 42 ++- .../sharepoint/sharepointonline/activity.md | 49 ++-- .../sharepoint/sharepointonline/overview.md | 12 +- .../11.6/requirements/unix/target.md | 32 +-- .../11.6/requirements/unix/unix.md | 4 +- .../11.6/requirements/windows/windows.md | 4 +- .../criteriaeditor/configuration.md | 24 +- .../criteriaeditor/keyword.md | 4 +- .../criteriaeditor/overview.md | 19 +- .../criteriaeditor/regularexpression.md | 10 +- .../criteriaeditor/summary.md | 11 +- .../11.6/sensitivedatadiscovery/overview.md | 9 +- .../supportedformats.md | 8 +- .../activity/ad_activitycollection.md | 55 ++-- .../activity/ad_ldapqueries.md | 19 +- .../activedirectory/activity/ad_lockouts.md | 6 +- .../changes/ad_computermodifications.md | 2 +- .../activity/changes/ad_groupmodifications.md | 8 +- .../activity/changes/ad_usermodifications.md | 2 +- .../activity/changes/overview.md | 2 +- .../activity/groupusage/ad_accesschanges.md | 2 +- .../activity/groupusage/ad_grouphosts.md | 4 +- .../groupusage/ad_groupmemberactivity.md | 8 +- .../operations/ad_authenticationprotocol.md | 2 +- .../operations/ad_domaincontrollertraffic.md | 4 +- .../activity/operations/ad_hardcodeddcs.md | 2 +- .../activity/operations/ad_loadbalancing.md | 6 +- .../activity/operations/ad_machineowners.md | 2 +- .../activity/operations/overview.md | 4 +- .../activedirectory/activity/overview.md | 6 +- .../privilegedaccounts/ad_adminaccounts.md | 10 +- .../ad_serviceaccountauth.md | 2 +- .../activedirectory/activity/recommended.md | 16 +- .../activedirectory/ad_securityassessment.md | 12 +- .../cleanup/ad_cleanupprogress.md | 8 +- .../computers/ad_deprovisioncomputers.md | 12 +- .../ad_deprovisioncomputers_status.md | 2 +- .../cleanup/computers/overview.md | 6 +- .../cleanup/configuretargetou.md | 8 +- .../deprovision/ad_deprovisiongroups.md | 12 +- .../ad_deprovisiongroups_status.md | 2 +- .../cleanup/groups/overview.md | 6 +- .../stamping/ad_groupcleanup_permissions.md | 4 +- .../groups/stamping/ad_groupstamping.md | 2 +- .../activedirectory/cleanup/recommended.md | 2 +- .../cleanup/users/ad_deprovisionusers.md | 22 +- .../users/ad_deprovisionusers_status.md | 2 +- .../activedirectory/cleanup/users/overview.md | 6 +- .../computers/ad_computerdelegation.md | 6 +- .../computers/ad_stalecomputers.md | 8 +- .../activedirectory/computers/overview.md | 4 +- .../activedirectory/computers/recommended.md | 12 +- .../activedirectory/domains/ad_dcsummary.md | 2 +- .../activedirectory/domains/ad_domaininfo.md | 4 +- .../domains/ad_dsrmsettings.md | 13 +- .../collection/ad_domaincontrollers.md | 8 +- .../domains/collection/ad_dsrm.md | 11 +- .../domains/collection/ad_timesync.md | 2 +- .../domains/collection/overview.md | 8 +- .../activedirectory/domains/overview.md | 7 +- .../activedirectory/domains/recommended.md | 4 +- .../grouppolicy/ad_cpassword.md | 6 +- .../grouppolicy/ad_grouppolicy.md | 4 +- .../grouppolicy/ad_overlappinggpos.md | 4 +- .../grouppolicy/ad_passwordpolicies.md | 6 +- .../activedirectory/grouppolicy/overview.md | 2 +- .../grouppolicy/recommended.md | 2 +- .../groups/ad_circularnesting.md | 2 +- .../groups/ad_dclogongroups.md | 4 +- .../groups/ad_duplicategroups.md | 2 +- .../activedirectory/groups/ad_emptygroups.md | 2 +- .../groups/ad_groupprobableowners.md | 2 +- .../groups/ad_largestgroups.md | 7 +- .../groups/ad_mailsecuritygroups.md | 2 +- .../activedirectory/groups/ad_nestedgroups.md | 6 +- .../groups/ad_sensitivesecuritygroups.md | 2 +- .../activedirectory/groups/ad_stalegroups.md | 4 +- .../activedirectory/groups/overview.md | 8 +- .../activedirectory/groups/recommended.md | 6 +- .../users/ad_directmembership.md | 4 +- .../users/ad_duplicateusers.md | 8 +- .../activedirectory/users/ad_orphanedusers.md | 2 +- .../users/ad_passwordstatus.md | 2 +- .../users/ad_serviceaccounts.md | 4 +- .../activedirectory/users/ad_sidhistory.md | 4 +- .../activedirectory/users/ad_staleusers.md | 10 +- .../users/ad_userattributecompletion.md | 2 +- .../users/ad_userdelegation.md | 4 +- .../activedirectory/users/ad_usertoken.md | 2 +- .../activedirectory/users/ad_weakpasswords.md | 15 +- .../activedirectory/users/overview.md | 4 +- .../activedirectory/users/recommended.md | 22 +- .../activedirectoryinventory/1-ad_scan.md | 34 +-- .../activedirectoryinventory/2-ad_changes.md | 27 +- .../3-ad_exceptions.md | 10 +- .../activedirectoryinventory/overview.md | 2 +- .../activedirectoryinventory/recommended.md | 12 +- .../ad_brokeninheritance.md | 2 +- .../ad_openaccess.md | 2 +- .../ad_oupermissions.md | 2 +- .../ad_shadowaccess.md | 22 +- .../collection/ad_computerrights.md | 4 +- .../collection/ad_containerrights.md | 4 +- .../collection/ad_domainrights.md | 4 +- .../collection/ad_grouprights.md | 4 +- .../collection/ad_ourights.md | 4 +- .../collection/ad_siterights.md | 4 +- .../collection/ad_userrights.md | 4 +- .../computers/ad_computerpermissions.md | 2 +- .../computers/ad_lapspermissions.md | 2 +- .../containers/ad_adminsdholder.md | 4 +- .../containers/ad_containerpermissions.md | 4 +- .../containers/overview.md | 2 +- .../domains/ad_domainpermissions.md | 2 +- .../domains/ad_domainreplication.md | 2 +- .../groups/ad_groupmembershippermissions.md | 6 +- .../groups/ad_grouppermissions.md | 2 +- .../groups/overview.md | 2 +- .../overview.md | 4 +- .../recommended.md | 2 +- .../sites/ad_dcshadowpermissions.md | 6 +- .../sites/ad_sitepermissions.md | 2 +- .../sites/overview.md | 2 +- .../users/ad_resetpasswordpermissions.md | 6 +- .../users/ad_userpermissions.md | 2 +- .../users/overview.md | 2 +- .../11.6/solutions/anyid/anyid_csv.md | 14 +- .../11.6/solutions/anyid/anyid_epicclarity.md | 16 +- .../11.6/solutions/anyid/anyid_paycom.md | 22 +- .../11.6/solutions/anyid/anyid_salesforce.md | 18 +- .../11.6/solutions/anyid/overview.md | 28 +- .../solutions/aws/collection/1.aws_orgscan.md | 2 +- .../solutions/aws/collection/2.aws_s3scan.md | 4 +- .../solutions/aws/collection/3.aws_iamscan.md | 4 +- .../aws/collection/4.aws_s3sddscan.md | 6 +- .../11.6/solutions/aws/collection/overview.md | 2 +- .../solutions/aws/groups/aws_groupmembers.md | 2 +- .../aws/groups/aws_nopolicygroups.md | 4 +- .../solutions/aws/groups/aws_stalegroups.md | 14 +- .../aws/organizations/aws_accounts.md | 2 +- .../organizations/aws_memberaccountusers.md | 6 +- .../solutions/aws/organizations/overview.md | 2 +- .../11.6/solutions/aws/overview.md | 28 +- .../aws/policies/aws_custommanagedpolicies.md | 2 +- .../aws/policies/aws_inlinepolicies.md | 2 +- .../aws/policies/aws_managedpolicies.md | 2 +- .../aws/policies/aws_sensitivepolicies.md | 2 +- .../aws/policies/aws_unusedmanagedpolicies.md | 10 +- .../aws/policies/aws_userpolicies.md | 2 +- .../11.6/solutions/aws/recommended.md | 22 +- .../11.6/solutions/aws/roles/aws_roles.md | 2 +- .../solutions/aws/roles/aws_staleroles.md | 18 +- .../11.6/solutions/aws/roles/overview.md | 2 +- .../solutions/aws/s3content/aws_s3buckets.md | 2 +- .../aws/s3content/aws_s3buckettags.md | 2 +- .../s3permissions/aws_brokeninheritance.md | 2 +- .../s3permissions/aws_effectivepermissions.md | 2 +- .../aws/s3permissions/aws_openbuckets.md | 2 +- .../aws/sensitivedata/aws_sensitivedata.md | 2 +- .../aws_sensitivedata_permissions.md | 2 +- .../solutions/aws/users/aws_accesskeys.md | 2 +- .../11.6/solutions/aws/users/aws_mfastatus.md | 2 +- .../solutions/aws/users/aws_rootaccounts.md | 2 +- .../solutions/aws/users/aws_staleusers.md | 10 +- .../box/activity/forensics/box_deletions.md | 2 +- .../box/activity/forensics/box_downloads.md | 2 +- .../forensics/box_externaluseractivity.md | 2 +- .../box_externalusercollaborations.md | 2 +- .../forensics/box_permissionchanges.md | 2 +- .../box/activity/forensics/box_sharing.md | 2 +- .../box/activity/forensics/overview.md | 4 +- .../suspiciousactivity/box_failedlogins.md | 2 +- .../box_firsttimefolderaccess.md | 2 +- .../box_unusualdownloadactivity.md | 4 +- .../box_unusualuseractivity.md | 4 +- .../suspiciousactivity/box_weekendactivity.md | 2 +- .../usagestatistics/box_folders_mostactive.md | 2 +- .../usagestatistics/box_folders_stale.md | 2 +- .../usagestatistics/box_users_mostactive.md | 2 +- .../11.6/solutions/box/box_access.md | 4 +- .../11.6/solutions/box/box_groupmembership.md | 2 +- .../box/collection/1-box_access_scans.md | 30 +- .../box/collection/1-box_activity_scans.md | 18 +- .../solutions/box/collection/2-box_import.md | 6 +- .../11.6/solutions/box/collection/overview.md | 8 +- .../solutions/box/content/box_filemetrics.md | 4 +- .../box/content/box_foldermetrics.md | 4 +- .../11.6/solutions/box/overview.md | 10 +- .../11.6/solutions/box/recommended.md | 35 ++- .../db2/collection/db2_configuration.md | 8 +- .../db2/collection/db2_permissionscan.md | 14 +- .../db2/collection/db2_sensitivedatascan.md | 27 +- .../databases/db2/db2_databasesizing.md | 2 +- .../11.6/solutions/databases/db2/overview.md | 4 +- .../db2/permissions/db2_directpermissions.md | 2 +- .../permissions/db2_effectivepermissions.md | 2 +- .../solutions/databases/db2/recommended.md | 8 +- .../db2/sensitivedata/db2_sensitivedata.md | 2 +- .../db2_sensitivedatapermissions.md | 2 +- .../collection/mongodb_configuration.md | 2 +- .../collection/mongodb_sensitivedatascan.md | 12 +- .../databases/mongodb/collection/overview.md | 2 +- .../mongodb/mongodb_databasesizing.md | 2 +- .../mongodb/mongodb_sensitivedata.md | 2 +- .../solutions/databases/mongodb/overview.md | 14 +- .../databases/mongodb/recommended.md | 11 +- .../mysql/collection/mysql_configuration.md | 2 +- .../collection/mysql_sensitivedatascan.md | 12 +- .../mysql/collection/mysql_tableprivileges.md | 4 +- .../databases/mysql/mysql_databasesizing.md | 2 +- .../solutions/databases/mysql/overview.md | 20 +- .../solutions/databases/mysql/recommended.md | 16 +- .../sensitivedata/mysql_sensitivedata.md | 2 +- .../mysql_sensitivedatapermissions.md | 2 +- .../oracle/activity/oracle_activity.md | 2 +- .../oracle/activity/oracle_logons.md | 2 +- .../activity/oracle_permissionchanges.md | 2 +- .../oracle/activity/oracle_schemachanges.md | 2 +- .../activity/oracle_sensitivedataactivity.md | 2 +- .../activity/oracle_suspiciousactivity.md | 4 +- .../oracle/activity/oracle_unusualactivity.md | 2 +- .../databases/oracle/activity/overview.md | 2 +- .../oracle/collection/0-oracle_servers.md | 6 +- .../collection/1-oracle_permissionsscan.md | 10 +- .../collection/2-oracle_sensitivedatascan.md | 10 +- .../collection/3-oracle_activityscan.md | 10 +- .../4-oracle_defaultpasswordusers.md | 8 +- .../collection/5-oracle_configuration.md | 8 +- .../configuration/oracle_databaselinks.md | 6 +- .../configuration/oracle_databasesizing.md | 2 +- .../oracle_datadictionaryprotection.md | 2 +- .../oracle_instancenameissues.md | 4 +- .../oracle_remoteosauthentication.md | 2 +- .../oracle/configuration/overview.md | 6 +- .../solutions/databases/oracle/overview.md | 22 +- .../oracle_domainuserpermissions.md | 2 +- .../permissions/oracle_objectpermissions.md | 2 +- .../permissions/oracle_publicpermissions.md | 2 +- .../permissions/oracle_serverpermissions.md | 2 +- .../oracle_sysschemapermissions.md | 2 +- .../solutions/databases/oracle/recommended.md | 39 ++- .../sensitivedata/oracle_sensitivedata.md | 2 +- .../oracle_sensitivedatapermissions.md | 2 +- .../usersroles/oracle_passwordissues.md | 4 +- .../oracle/usersroles/oracle_rolemembers.md | 2 +- .../usersroles/oracle_systemadministrators.md | 2 +- .../oracle/usersroles/oracle_users.md | 2 +- .../11.6/solutions/databases/overview.md | 12 +- .../collection/pgsql_configuration.md | 2 +- .../collection/pgsql_sensitivedatascan.md | 16 +- .../collection/pgsql_tableprivileges.md | 7 +- .../databases/postgresql/overview.md | 22 +- .../postgresql/pgsql_databasesizing.md | 2 +- .../databases/postgresql/recommended.md | 24 +- .../sensitivedata/pgsql_sensitivedata.md | 2 +- .../pgsql_sensitivedatapermissions.md | 2 +- .../databases/redshift/collection/overview.md | 2 +- .../collection/redshift_configuration.md | 2 +- .../collection/redshift_sensitivedatascan.md | 19 +- .../collection/redshift_tableprivileges.md | 4 +- .../solutions/databases/redshift/overview.md | 29 +- .../databases/redshift/recommended.md | 8 +- .../redshift/redshift_databasesizing.md | 4 +- .../redshift/sensitivedata/overview.md | 2 +- .../sensitivedata/redshift_sensitivedata.md | 2 +- .../redshift_sensitivedatapermissions.md | 2 +- .../databases/sql/activity/sql_activity.md | 2 +- .../databases/sql/activity/sql_logons.md | 2 +- .../sql/activity/sql_permissionchanges.md | 2 +- .../sql/activity/sql_sensitivedataactivity.md | 2 +- .../sql/activity/sql_unusualactivity.md | 2 +- .../0-azuresql_instancediscovery.md | 2 +- .../1-azuresql_permissionscan.md | 10 +- .../2-azuresql_sensitivedatascan.md | 2 +- .../3-azuresql_activityscan.md | 2 +- .../4-azuresql_serversettings.md | 2 +- .../sql/collection/0-sql_instancediscovery.md | 2 +- .../sql/collection/1-sql_permissionsscan.md | 12 +- .../sql/collection/2-sql_sensitivedatascan.md | 12 +- .../sql/collection/3-sql_activityscan.md | 12 +- .../sql/collection/4-sql_serverlogons.md | 2 +- .../sql/collection/5-sql_serversettings.md | 18 +- .../databases/sql/configuration/overview.md | 6 +- .../sql/configuration/sql_authentication.md | 6 +- .../sql/configuration/sql_bestpractices.md | 2 +- .../sql/configuration/sql_cmdshell.md | 6 +- .../sql/configuration/sql_databasesizing.md | 2 +- .../sql/configuration/sql_linkedservers.md | 6 +- .../11.6/solutions/databases/sql/overview.md | 10 +- .../databases/sql/permissions/overview.md | 2 +- .../sql/permissions/sql_controlserver.md | 2 +- .../sql/permissions/sql_directpermissions.md | 2 +- .../permissions/sql_domainuserpermissions.md | 2 +- .../sql/permissions/sql_publicpermissions.md | 6 +- .../sql/permissions/sql_serverpermissions.md | 2 +- .../solutions/databases/sql/recommended.md | 58 ++-- .../sql/sensitivedata/sql_sensitivedata.md | 2 +- .../sql_sensitivedatapermissions.md | 2 +- .../databases/sql/usersroles/overview.md | 2 +- .../sql/usersroles/sql_databaseprinciples.md | 6 +- .../sql/usersroles/sql_passwordissues.md | 6 +- .../sql/usersroles/sql_rolemembers.md | 2 +- .../sql/usersroles/sql_serverprincipals.md | 2 +- .../databases/sql/usersroles/sql_sqllogins.md | 2 +- .../databases/sql/usersroles/sql_sysadmins.md | 2 +- .../collection/1-dropbox_permissions_scan.md | 14 +- .../dropbox/collection/1-dropbox_sdd_scan.md | 12 +- .../2-dropbox_permissions_bulk_import.md | 8 +- .../collection/2-dropbox_sdd_bulk_import.md | 6 +- .../solutions/dropbox/collection/overview.md | 28 +- .../11.6/solutions/dropbox/dropbox_access.md | 6 +- .../11.6/solutions/dropbox/dropbox_content.md | 14 +- .../dropbox/dropbox_groupmembership.md | 2 +- .../dropbox/dropbox_sensitivedata.md | 12 +- .../11.6/solutions/dropbox/dropbox_sharing.md | 8 +- .../11.6/solutions/dropbox/overview.md | 22 +- .../11.6/solutions/dropbox/recommended.md | 22 +- .../entraid/groups/aad_circularnesting.md | 6 +- .../entraid/groups/aad_duplicategroups.md | 4 +- .../entraid/groups/aad_emptygroups.md | 2 +- .../entraid/groups/aad_groupdirsync.md | 2 +- .../entraid/groups/aad_largestgroups.md | 10 +- .../entraid/groups/aad_nestedgroups.md | 6 +- .../entraid/groups/aad_probableowners.md | 6 +- .../entraid/groups/aad_stalegroups.md | 4 +- .../11.6/solutions/entraid/groups/overview.md | 17 +- .../11.6/solutions/entraid/overview.md | 4 +- .../11.6/solutions/entraid/recommended.md | 10 +- .../entraid/users/aad_directmembership.md | 4 +- .../entraid/users/aad_disabledusers.md | 4 +- .../solutions/entraid/users/aad_staleusers.md | 6 +- .../users/aad_userattributecompletion.md | 4 +- .../entraid/users/aad_userdirsync.md | 2 +- .../11.6/solutions/entraid/users/overview.md | 10 +- .../solutions/entraidinventory/1-aad_scan.md | 14 +- .../entraidinventory/2-aad_exceptions.md | 19 +- .../solutions/entraidinventory/overview.md | 2 +- .../solutions/entraidinventory/recommended.md | 22 +- .../exchange/casmetrics/ex_activesync.md | 10 +- .../exchange/casmetrics/ex_aspolicies.md | 16 +- .../exchange/casmetrics/ex_iislogs.md | 14 +- .../exchange/casmetrics/ex_owatraffic.md | 4 +- .../exchange/casmetrics/ex_rpctraffic.md | 8 +- .../solutions/exchange/casmetrics/overview.md | 6 +- .../exchange/casmetrics/recommended.md | 6 +- .../databases/collection/ex_dbinfo.md | 4 +- .../databases/collection/ex_pfinfo.md | 4 +- .../exchange/databases/collection/overview.md | 4 +- .../exchange/databases/ex_dbsizing.md | 8 +- .../exchange/databases/ex_dbtrending.md | 4 +- .../exchange/databases/recommended.md | 4 +- .../distributionlists/ex_dlcleanup.md | 2 +- .../distributionlists/ex_groupexpansion.md | 2 +- .../membershipanalysis/ex_circularnesting.md | 2 +- .../membershipanalysis/ex_emptygroups.md | 2 +- .../membershipanalysis/ex_largestgroups.md | 2 +- .../membershipanalysis/ex_nestedgroups.md | 2 +- .../membershipanalysis/ex_stalegroups.md | 2 +- .../membershipanalysis/overview.md | 2 +- .../exchange/distributionlists/overview.md | 2 +- .../exchange/distributionlists/recommended.md | 2 +- .../solutions/exchange/ex_useroverview.md | 7 +- .../collection/appletstatuscheck.md | 2 +- .../collection/ex_metricscollection.md | 34 +-- .../collection/ex_metricsdetails.md | 14 +- .../hubmetrics/collection/overview.md | 10 +- .../exchange/hubmetrics/ex_deliverytimes.md | 2 +- .../exchange/hubmetrics/ex_dlmetrics.md | 2 +- .../exchange/hubmetrics/ex_domainmetrics.md | 4 +- .../exchange/hubmetrics/ex_hourlymetrics.md | 8 +- .../exchange/hubmetrics/ex_messagesize.md | 2 +- .../exchange/hubmetrics/ex_servermetrics.md | 2 +- .../exchange/hubmetrics/ex_usermetrics.md | 2 +- .../solutions/exchange/hubmetrics/overview.md | 6 +- .../exchange/hubmetrics/recommended.md | 6 +- .../exchange/mailboxes/ex_features.md | 2 +- .../mailboxes/logons/ex_mailboxlogons.md | 4 +- .../solutions/exchange/mailboxes/overview.md | 4 +- .../permissions/collection/ex_sendas.md | 2 +- .../mailboxes/permissions/ex_admingroups.md | 2 +- .../mailboxes/permissions/ex_mailboxaccess.md | 10 +- .../mailboxes/permissions/overview.md | 2 +- .../exchange/mailboxes/recommended.md | 12 +- .../mailboxes/sizing/ex_mailboxsizes.md | 8 +- .../mailboxes/sizing/ex_stalemailboxes.md | 4 +- .../mailboxes/sizing/ex_storesizes.md | 2 +- .../exchange/online/mailflow/ex_mailflow.md | 14 +- .../online/mailflow/ex_mailflow_dl.md | 8 +- .../online/mailflow/ex_mailflow_domain.md | 6 +- .../online/mailflow/ex_mailflow_mailbox.md | 6 +- .../mailflow/ex_mailflow_orgoverview.md | 4 +- .../exchange/online/mailflow/overview.md | 2 +- .../solutions/exchange/online/recommended.md | 2 +- .../11.6/solutions/exchange/overview.md | 29 +- .../publicfolders/content/pf_content.md | 2 +- .../publicfolders/content/pf_contentscans.md | 2 +- .../growthsize/pf_folderscans.md | 2 +- .../publicfolders/growthsize/pf_foldersize.md | 4 +- .../exchange/publicfolders/overview.md | 4 +- .../publicfolders/ownership/overview.md | 2 +- .../ownership/pf_folderownership.md | 14 +- .../publicfolders/ownership/pf_owners.md | 2 +- .../permissions/pf_entitlements.md | 2 +- .../permissions/pf_entitlementscans.md | 2 +- .../exchange/publicfolders/pf_overview.md | 2 +- .../exchange/publicfolders/recommended.md | 8 +- .../11.6/solutions/exchange/recommended.md | 12 +- .../collection/ex_mailbox_sdd.md | 16 +- .../collection/ex_publicfolder_sdd.md | 12 +- .../exchange/sensitivedata/ex_sddresults.md | 8 +- .../exchange/sensitivedata/overview.md | 2 +- .../exchange/sensitivedata/recommended.md | 4 +- .../activity/forensics/fs_deletions.md | 15 +- .../forensics/fs_permissionchanges.md | 2 +- .../activity/fs_leastprivilegedaccess.md | 6 +- .../activity/security/fs_adminactvity.md | 4 +- .../activity/security/fs_highriskactivity.md | 4 +- .../activity/security/fs_localuseractivity.md | 2 +- .../suspiciousactivity/fs_deniedactivity.md | 2 +- .../fs_highesthourlyactivity.md | 2 +- .../fs_hourlyshareactivity.md | 2 +- .../suspiciousactivity/fs_modifiedbinaries.md | 2 +- .../fs_peergroupactivity.md | 2 +- .../suspiciousactivity/fs_ransomware.md | 8 +- .../fs_sensitivedataactivity.md | 2 +- .../fs_stalefileactivity.md | 2 +- .../fs_usershareactivity.md | 2 +- .../suspiciousactivity/fs_weekendactivity.md | 2 +- .../activity/suspiciousactivity/overview.md | 6 +- .../activity/usagestatistics/fs_groupusage.md | 2 +- .../usagestatistics/fs_mostactiveservers.md | 2 +- .../usagestatistics/fs_mostactiveusers.md | 2 +- .../usagestatistics/fs_staleshares.md | 2 +- .../filesystem/adhocaudits/fs_shareaudit.md | 2 +- .../adhocaudits/fs_trusteepermissions.md | 4 +- .../filesystem/adhocaudits/overview.md | 2 +- .../cleanup/delete/fs_deletefiles.md | 8 +- .../cleanup/delete/fs_deletefiles_status.md | 2 +- .../cleanup/fs_cleanupassessment.md | 16 +- .../filesystem/cleanup/fs_cleanupprogress.md | 2 +- .../cleanup/notify/fs_notifyowners.md | 19 +- .../cleanup/notify/fs_notifyowners_status.md | 2 +- .../solutions/filesystem/cleanup/overview.md | 8 +- .../cleanup/quarantine/fs_quarantinedata.md | 8 +- .../quarantine/fs_quarantinedata_status.md | 2 +- .../quarantine/fs_restoreinheritance.md | 6 +- .../fs_restoreinheritance_status.md | 4 +- .../filesystem/cleanup/quarantine/overview.md | 2 +- .../filesystem/collection/0-create_schema.md | 8 +- .../filesystem/collection/0-fs_nasuni.md | 17 +- .../collection/0-fsdfs_system_scans.md | 6 +- .../collection/1-fsaa_system_scans.md | 23 +- .../collection/1-fsac_system_scans.md | 2 +- .../collection/1-seek_system_scans.md | 24 +- .../collection/2-fsaa_bulk_import.md | 4 +- .../collection/2-fsac_bulk_import.md | 2 +- .../collection/2-seek_bulk_import.md | 2 +- .../collection/3-fsaa_exceptions.md | 28 +- .../collection/3-fsac_exceptions.md | 8 +- .../filesystem/collection/overview.md | 177 ++++++------ .../filesystem/content/fs_filetypes.md | 2 +- .../filesystem/content/fs_stalecontent.md | 2 +- .../content/sizing/fs_emptyresources.md | 2 +- .../content/sizing/fs_largestresources.md | 2 +- .../content/sizing/fs_smallestresources.md | 2 +- .../filesystem/content/tags/fs_aiplabels.md | 6 +- .../filesystem/content/tags/fs_filetags.md | 2 +- .../filesystem/content/tags/overview.md | 3 +- .../directpermissions/fs_domainuseracls.md | 4 +- .../directpermissions/fs_highriskacls.md | 2 +- .../fs_localusersandgroups.md | 2 +- .../fs_missingfullcontrol.md | 6 +- .../directpermissions/fs_nestedshares.md | 4 +- .../directpermissions/fs_sidhistory.md | 4 +- .../directpermissions/fs_unresolvedsids.md | 2 +- .../filesystem/filesystemoverview.md | 6 +- .../filesystem/fs_brokeninheritance.md | 12 +- .../solutions/filesystem/fs_dlpresults.md | 4 +- .../solutions/filesystem/fs_openaccess.md | 6 +- .../solutions/filesystem/fs_probableowner.md | 6 +- .../filesystem/fs_securityassessment.md | 4 +- .../11.6/solutions/filesystem/overview.md | 40 ++- .../11.6/solutions/filesystem/recommended.md | 84 +++--- .../fs_resourcebasedgroupaicimport.md | 34 ++- .../fs_resourcebasedgroups.md | 78 +++-- .../resourcebasedgroups/fs_traversegroups.md | 56 ++-- .../resourcebasedgroups/overview.md | 28 +- .../11.6/solutions/nisinventory/nis_scan.md | 24 +- .../11.6/solutions/nisinventory/overview.md | 6 +- .../solutions/nisinventory/recommended.md | 20 +- .../accessanalyzer/11.6/solutions/overview.md | 10 +- .../sharepoint/activity/forensics/overview.md | 2 +- .../activity/forensics/sp_deletions.md | 4 +- .../forensics/sp_permissionchanges.md | 6 +- .../forensics/sp_sensitivedataactivity.md | 8 +- .../solutions/sharepoint/activity/overview.md | 6 +- .../activity/usagestatistics/overview.md | 2 +- .../usagestatistics/sp_inactivesites.md | 4 +- .../usagestatistics/sp_mostactivesites.md | 4 +- .../usagestatistics/sp_mostactiveusers.md | 6 +- .../collection/1-spseek_systemscans.md | 12 +- .../collection/2-spaa_systemscans.md | 12 +- .../collection/3-spac_systemscans.md | 4 +- .../collection/4-spseek_bulkimport.md | 14 +- .../collection/5-spaa_bulkimport.md | 20 +- .../collection/6-spac_bulkimport.md | 20 +- .../collection/7-spaa_exceptions.md | 24 +- .../sharepoint/collection/overview.md | 54 ++-- .../solutions/sharepoint/content/overview.md | 6 +- .../sharepoint/content/sp_largestfiles.md | 2 +- .../sharepoint/content/sp_stalefiles.md | 10 +- .../directpermissions/sp_domainusers.md | 2 +- .../sp_emptydomaingroupperms.md | 2 +- .../sp_highriskpermissions.md | 4 +- .../sp_sitecollectionperms.md | 8 +- .../directpermissions/sp_staleusers.md | 9 +- .../directpermissions/sp_unresolvedsids.md | 2 +- .../effectiveaccessaudits/overview.md | 7 +- .../effectiveaccessaudits/sp_trusteeaccess.md | 14 +- .../effectiveaccessaudits/sp_trusteeaudit.md | 2 +- .../solutions/sharepoint/m365/overview.md | 2 +- .../sharepoint/m365/sp_externalusers.md | 4 +- .../solutions/sharepoint/m365/sp_onedrives.md | 2 +- .../sharepoint/m365/sp_sharedlinks.md | 2 +- .../sharepoint/m365/sp_staleteamsites.md | 10 +- .../solutions/sharepoint/m365/sp_teams.md | 4 +- .../m365/sp_teamsexternaluseractivity.md | 4 +- .../sharepoint/m365/sp_teamssensitivedata.md | 4 +- .../11.6/solutions/sharepoint/overview.md | 47 ++- .../11.6/solutions/sharepoint/recommended.md | 38 +-- .../sharepoint/sp_brokeninheritance.md | 13 +- .../solutions/sharepoint/sp_openaccess.md | 13 +- .../11.6/solutions/sharepoint/sp_overview.md | 11 +- .../solutions/sharepoint/sp_probableowner.md | 10 +- .../solutions/sharepoint/sp_sensitivedata.md | 6 +- .../11.6/solutions/unix/overview.md | 2 +- .../privilegedaccess/sudoers/ux_sudoers.md | 2 +- .../unix/privilegedaccess/ux_criticalfiles.md | 4 +- .../11.6/solutions/unix/recommended.md | 12 +- .../unix/sharing/collection/overview.md | 2 +- .../sharing/collection/ux_nfsconfiguration.md | 2 +- .../collection/ux_sambaconfiguration.md | 2 +- .../11.6/solutions/unix/sharing/ux_nfs.md | 2 +- .../11.6/solutions/unix/sharing/ux_samba.md | 4 +- .../solutions/unix/usersgroups/overview.md | 8 +- .../unix/usersgroups/ux_duplicategroups.md | 2 +- .../unix/usersgroups/ux_emptygroups.md | 2 +- .../unix/usersgroups/ux_largegroups.md | 10 +- .../unix/usersgroups/ux_localgroups.md | 2 +- .../unix/usersgroups/ux_localusers.md | 2 +- .../unix/usersgroups/ux_passwordsettings.md | 2 +- .../unix/usersgroups/ux_usersandgroups.md | 6 +- .../applications/sg_installedapplications.md | 4 +- .../windows/applications/sg_runatboot.md | 2 +- .../windows/applications/sg_scheduledtasks.md | 2 +- .../windows/authentication/overview.md | 12 +- .../windows/authentication/sg_lsasettings.md | 12 +- .../sg_securitysupportproviders.md | 6 +- .../authentication/sg_wdigestsettings.md | 4 +- .../windows/openaccess/recommended.md | 6 +- .../windows/openaccess/sg_openfolders.md | 10 +- .../11.6/solutions/windows/overview.md | 12 +- .../localadministrators/overview.md | 4 +- .../localadministrators/sg_localadmins.md | 2 +- .../localadministrators/sg_microsoftlaps.md | 2 +- .../localadministrators/sg_sessions.md | 4 +- .../logonrights/collection/overview.md | 10 +- .../logonrights/collection/sg_grouppolicy.md | 4 +- .../collection/sg_localmembership.md | 2 +- .../logonrights/collection/sg_localusers.md | 4 +- .../logonrights/overview.md | 4 +- .../logonrights/sg_accountprivileges.md | 4 +- .../logonrights/sg_localpolicies.md | 6 +- .../windows/privilegedaccounts/recommended.md | 12 +- .../privilegedaccounts/sg_serviceaccounts.md | 4 +- .../11.6/solutions/windows/recommended.md | 6 +- .../openportscan/overview.md | 10 +- .../openportscan/remoteopenport.md | 2 +- .../openportscan/retrievenetstat.md | 8 +- .../windows/securityutilities/overview.md | 10 +- .../windows/securityutilities/recommended.md | 6 +- .../sg_powershellcommands.md | 32 +-- .../windows/sg_securityassessment.md | 8 +- .../operations/computerdetails.md | 12 +- .../operations/creategroups.md | 8 +- .../activedirectory/operations/createusers.md | 6 +- .../operations/disableenablecomputers.md | 2 +- .../operations/disableenableusers.md | 2 +- .../operations/groupdetails.md | 12 +- .../operations/groupmembership.md | 12 +- .../activedirectory/operations/moveobjects.md | 4 +- .../activedirectory/operations/operations.md | 12 +- .../operations/setresetpassword.md | 2 +- .../activedirectory/operations/sidhistory.md | 8 +- .../admin/action/activedirectory/options.md | 5 +- .../admin/action/activedirectory/overview.md | 19 +- .../admin/action/activedirectory/summary.md | 6 +- .../admin/action/activedirectory/target.md | 12 +- .../12.0/admin/action/filesystem/action.md | 14 +- .../admin/action/filesystem/appletsettings.md | 10 +- .../admin/action/filesystem/destination.md | 14 +- .../admin/action/filesystem/environment.md | 6 +- .../12.0/admin/action/filesystem/operation.md | 4 +- .../12.0/admin/action/filesystem/options.md | 42 ++- .../12.0/admin/action/filesystem/overview.md | 30 +- .../action/filesystem/parameters/addtags.md | 18 +- .../filesystem/parameters/changeowner.md | 2 +- .../parameters/changepermissioninheritance.md | 2 +- .../parameters/changepermissionsauditing.md | 4 +- .../parameters/changesharepermissions.md | 6 +- .../filesystem/parameters/parameters.md | 10 +- .../parameters/removefilepermissions.md | 2 +- .../parameters/removesharepermissions.md | 2 +- .../filesystem/parameters/removetags.md | 18 +- .../12.0/admin/action/filesystem/rollback.md | 2 +- .../12.0/admin/action/filesystem/summary.md | 6 +- .../12.0/admin/action/filesystem/target.md | 18 +- .../12.0/admin/action/libraries.md | 19 +- .../admin/action/mailbox/affectedmailboxes.md | 2 +- .../admin/action/mailbox/delegaterights.md | 12 +- .../admin/action/mailbox/folderconditions.md | 24 +- .../action/mailbox/folderidentification.md | 4 +- .../admin/action/mailbox/identification.md | 2 +- .../admin/action/mailbox/messageactions.md | 8 +- .../admin/action/mailbox/messageconditions.md | 26 +- .../12.0/admin/action/mailbox/operations.md | 2 +- .../12.0/admin/action/mailbox/overview.md | 6 +- .../12.0/admin/action/mailbox/permissions.md | 25 +- .../12.0/admin/action/mailbox/samplinghost.md | 6 +- .../12.0/admin/action/mailbox/trustedusers.md | 7 +- .../12.0/admin/action/overview.md | 34 +-- .../action/powershell/executionoptions.md | 4 +- .../12.0/admin/action/powershell/overview.md | 3 +- .../12.0/admin/action/powershell/script.md | 16 +- .../12.0/admin/action/publicfolder/action.md | 15 +- .../12.0/admin/action/publicfolder/folders.md | 6 +- .../admin/action/publicfolder/mapisettings.md | 2 +- .../admin/action/publicfolder/operations.md | 34 +-- .../admin/action/publicfolder/overview.md | 14 +- .../admin/action/publicfolder/prioractions.md | 4 +- .../admin/action/publicfolder/rollback.md | 4 +- .../12.0/admin/action/publicfolder/summary.md | 6 +- .../12.0/admin/action/registry/operations.md | 18 +- .../12.0/admin/action/registry/overview.md | 12 +- .../12.0/admin/action/registry/summary.md | 6 +- .../12.0/admin/action/registry/targethosts.md | 2 +- .../12.0/admin/action/sendmail/message.md | 12 +- .../12.0/admin/action/sendmail/overview.md | 6 +- .../12.0/admin/action/sendmail/properties.md | 6 +- .../12.0/admin/action/sendmail/summary.md | 6 +- .../12.0/admin/action/sendmail/viewstatus.md | 2 +- .../admin/action/servicenow/authentication.md | 2 +- .../admin/action/servicenow/description.md | 6 +- .../action/servicenow/incidentcreation.md | 12 +- .../12.0/admin/action/servicenow/overview.md | 34 +-- .../12.0/admin/action/servicenow/summary.md | 6 +- .../12.0/admin/action/survey/introduction.md | 4 +- .../12.0/admin/action/survey/mailmessage.md | 16 +- .../admin/action/survey/mailproperties.md | 4 +- .../12.0/admin/action/survey/overview.md | 8 +- .../12.0/admin/action/survey/questions.md | 6 +- .../12.0/admin/action/survey/testsurvey.md | 5 +- .../admin/action/webrequest/destination.md | 14 +- .../12.0/admin/action/webrequest/header.md | 6 +- .../12.0/admin/action/webrequest/overview.md | 8 +- .../admin/action/webrequest/parameters.md | 14 +- .../12.0/admin/action/webrequest/summary.md | 6 +- .../12.0/admin/analysis/autoaction.md | 10 +- .../admin/analysis/businessrules/appliesto.md | 4 +- .../admin/analysis/businessrules/logic.md | 18 +- .../admin/analysis/businessrules/overview.md | 10 +- .../changedetection/additionalfields.md | 2 +- .../admin/analysis/changedetection/input.md | 4 +- .../analysis/changedetection/inputscope.md | 4 +- .../admin/analysis/changedetection/options.md | 4 +- .../analysis/changedetection/overview.md | 2 +- .../admin/analysis/changedetection/summary.md | 5 +- .../admin/analysis/notification/changetype.md | 4 +- .../analysis/notification/commandline.md | 8 +- .../admin/analysis/notification/criteria.md | 4 +- .../admin/analysis/notification/eventlog.md | 6 +- .../12.0/admin/analysis/notification/hosts.md | 14 +- .../admin/analysis/notification/overview.md | 2 +- .../12.0/admin/analysis/notification/smtp.md | 16 +- .../admin/analysis/notification/summary.md | 6 +- .../admin/analysis/notification/tabletype.md | 12 +- .../admin/analysis/notification/timewindow.md | 4 +- .../12.0/admin/analysis/overview.md | 36 +-- .../12.0/admin/analysis/sqlscripting.md | 33 ++- .../admin/analysis/sqlviewcreation/columns.md | 14 +- .../admin/analysis/sqlviewcreation/export.md | 8 +- .../admin/analysis/sqlviewcreation/filter.md | 2 +- .../admin/analysis/sqlviewcreation/input.md | 10 +- .../analysis/sqlviewcreation/inputscope.md | 2 +- .../analysis/sqlviewcreation/joincolumns.md | 13 +- .../analysis/sqlviewcreation/overview.md | 7 +- .../admin/analysis/sqlviewcreation/result.md | 6 +- .../sqlviewcreation/resultconstraints.md | 12 +- .../analysis/sqlviewcreation/resultsample.md | 4 +- .../admin/analysis/sqlviewcreation/summary.md | 5 +- .../analysis/sqlviewcreation/timewindow.md | 6 +- .../12.0/admin/analysis/vbscripting.md | 10 +- .../activedirectory/directoryscope.md | 2 +- .../datacollector/activedirectory/options.md | 4 +- .../datacollector/activedirectory/overview.md | 10 +- .../datacollector/activedirectory/results.md | 10 +- .../datacollector/activedirectory/summary.md | 8 +- .../datacollector/adactivity/category.md | 6 +- .../datacollector/adactivity/cleartables.md | 8 +- .../datacollector/adactivity/connection.md | 11 +- .../datacollector/adactivity/overview.md | 9 +- .../admin/datacollector/adactivity/results.md | 9 +- .../admin/datacollector/adactivity/scope.md | 14 +- .../admin/datacollector/adactivity/share.md | 12 +- .../adactivity/standardtables.md | 9 +- .../admin/datacollector/adactivity/summary.md | 8 +- .../datacollector/adinventory/category.md | 8 +- .../datacollector/adinventory/cleartables.md | 9 +- .../adinventory/customattributes.md | 47 ++- .../datacollector/adinventory/domains.md | 2 +- .../adinventory/indexupdateoptions.md | 4 +- .../datacollector/adinventory/options.md | 27 +- .../datacollector/adinventory/overview.md | 21 +- .../datacollector/adinventory/results.md | 13 +- .../adinventory/standardtables.md | 4 +- .../datacollector/adinventory/summary.md | 8 +- .../datacollector/adpermissions/category.md | 4 +- .../adpermissions/customfilter.md | 11 +- .../datacollector/adpermissions/options.md | 6 +- .../datacollector/adpermissions/overview.md | 12 +- .../adpermissions/removetables.md | 15 +- .../datacollector/adpermissions/results.md | 8 +- .../datacollector/adpermissions/scope.md | 2 +- .../adpermissions/standardtables.md | 2 +- .../datacollector/adpermissions/summary.md | 8 +- .../12.0/admin/datacollector/aws/criteria.md | 13 +- .../admin/datacollector/aws/droptables.md | 10 +- .../datacollector/aws/filters3objects.md | 6 +- .../admin/datacollector/aws/loginroles.md | 10 +- .../12.0/admin/datacollector/aws/overview.md | 18 +- .../12.0/admin/datacollector/aws/results.md | 8 +- .../admin/datacollector/aws/sensitivedata.md | 13 +- .../12.0/admin/datacollector/aws/summary.md | 6 +- .../azureadinventory/category.md | 6 +- .../azureadinventory/configurejob.md | 12 +- .../azureadinventory/customattributes.md | 33 ++- .../azureadinventory/overview.md | 4 +- .../datacollector/azureadinventory/results.md | 12 +- .../azureadinventory/standardtables.md | 11 +- .../datacollector/azureadinventory/summary.md | 9 +- .../azureadinventory/troubleshooting.md | 8 +- .../box/activityoperationscope.md | 8 +- .../box/activitytimeframescope.md | 10 +- .../datacollector/box/additionalscoping.md | 8 +- .../admin/datacollector/box/authenticate.md | 2 +- .../admin/datacollector/box/exclusions.md | 8 +- .../12.0/admin/datacollector/box/overview.md | 14 +- .../12.0/admin/datacollector/box/results.md | 6 +- .../admin/datacollector/box/scopebyuser.md | 14 +- .../admin/datacollector/box/standardtables.md | 10 +- .../12.0/admin/datacollector/box/summary.md | 8 +- .../commandlineutility/definefields.md | 4 +- .../commandlineutility/overview.md | 12 +- .../commandlineutility/profileparameters.md | 18 +- .../commandlineutility/profiletype.md | 8 +- .../commandlineutility/results.md | 8 +- .../commandlineutility/scripteditor.md | 4 +- .../commandlineutility/summary.md | 9 +- .../admin/datacollector/diskinfo/overview.md | 10 +- .../admin/datacollector/diskinfo/results.md | 9 +- .../admin/datacollector/diskinfo/summary.md | 7 +- .../datacollector/diskinfo/targetdisks.md | 20 +- .../12.0/admin/datacollector/dns/overview.md | 8 +- .../12.0/admin/datacollector/dns/results.md | 8 +- .../12.0/admin/datacollector/dns/summary.md | 7 +- .../datacollector/dropboxaccess/completion.md | 10 +- .../dropboxaccess/configurejob.md | 12 +- .../dropboxaccess/dlpauditsettings.md | 14 +- .../datacollector/dropboxaccess/overview.md | 20 +- .../dropboxaccess/scanoptions.md | 15 +- .../dropboxaccess/selectdlpcriteria.md | 6 +- .../dropboxaccess/standardtables.md | 6 +- .../admin/datacollector/entra/overview.md | 4 +- .../12.0/admin/datacollector/entra/results.md | 6 +- .../12.0/admin/datacollector/entra/summary.md | 7 +- .../12.0/admin/datacollector/eventlog.md | 32 +-- .../datacollector/ewsmailbox/category.md | 2 +- .../datacollector/ewsmailbox/criteria.md | 8 +- .../admin/datacollector/ewsmailbox/filter.md | 10 +- .../admin/datacollector/ewsmailbox/options.md | 2 +- .../datacollector/ewsmailbox/overview.md | 12 +- .../admin/datacollector/ewsmailbox/results.md | 8 +- .../admin/datacollector/ewsmailbox/scope.md | 6 +- .../datacollector/ewsmailbox/scopeselect.md | 8 +- .../datacollector/ewsmailbox/sddoptions.md | 6 +- .../ewsmailbox/searchfilter/bodyoptions.md | 2 +- .../ewsmailbox/searchfilter/filterwizard.md | 6 +- .../searchfilter/folderconditions.md | 6 +- .../searchfilter/messageconditions.md | 10 +- .../admin/datacollector/ewsmailbox/summary.md | 5 +- .../ewspublicfolder/critieria.md | 4 +- .../datacollector/ewspublicfolder/filter.md | 22 +- .../datacollector/ewspublicfolder/options.md | 4 +- .../datacollector/ewspublicfolder/overview.md | 8 +- .../datacollector/ewspublicfolder/results.md | 8 +- .../ewspublicfolder/sddoptions.md | 4 +- .../searchfilter/bodyoptions.md | 4 +- .../searchfilter/filterwizard.md | 6 +- .../searchfilter/folderconditions.md | 8 +- .../searchfilter/messageconditions.md | 12 +- .../datacollector/ewspublicfolder/summary.md | 6 +- .../datacollector/exchange2k/category.md | 2 +- .../datacollector/exchange2k/mapisettings.md | 10 +- .../admin/datacollector/exchange2k/options.md | 2 +- .../datacollector/exchange2k/overview.md | 14 +- .../admin/datacollector/exchange2k/results.md | 6 +- .../admin/datacollector/exchange2k/scope.md | 2 +- .../admin/datacollector/exchange2k/summary.md | 5 +- .../datacollector/exchangemailbox/options.md | 2 +- .../datacollector/exchangemailbox/overview.md | 16 +- .../exchangemailbox/properties.md | 6 +- .../datacollector/exchangemailbox/scope.md | 8 +- .../exchangemailbox/sddcriteria.md | 10 +- .../datacollector/exchangemailbox/summary.md | 6 +- .../datacollector/exchangemetrics/category.md | 2 +- .../exchangemetrics/collectmode.md | 6 +- .../exchangemetrics/messageactivityfilter.md | 15 +- .../exchangemetrics/messagesizes.md | 8 +- .../datacollector/exchangemetrics/options.md | 2 +- .../datacollector/exchangemetrics/overview.md | 4 +- .../datacollector/exchangemetrics/results.md | 7 +- .../datacollector/exchangemetrics/scope.md | 12 +- .../datacollector/exchangemetrics/summary.md | 5 +- .../exchangemetrics/timeframes.md | 8 +- .../datacollector/exchangeps/category.md | 42 +-- .../datacollector/exchangeps/configurejob.md | 20 +- .../datacollector/exchangeps/errorlogging.md | 2 +- .../datacollector/exchangeps/filtermessage.md | 20 +- .../datacollector/exchangeps/mailboxlogons.md | 8 +- .../datacollector/exchangeps/mailflow.md | 2 +- .../admin/datacollector/exchangeps/options.md | 4 +- .../datacollector/exchangeps/overview.md | 16 +- .../admin/datacollector/exchangeps/results.md | 6 +- .../admin/datacollector/exchangeps/scope.md | 4 +- .../exchangeps/scopedatabases.md | 14 +- .../exchangeps/scopemailboxes.md | 12 +- .../exchangeps/scopepublicfolders.md | 12 +- .../admin/datacollector/exchangeps/summary.md | 7 +- .../exchangepublicfolder/category.md | 2 +- .../exchangepublicfolder/options.md | 12 +- .../exchangepublicfolder/overview.md | 18 +- .../exchangepublicfolder/probableowner.md | 12 +- .../exchangepublicfolder/properties.md | 8 +- .../exchangepublicfolder/scope.md | 20 +- .../12.0/admin/datacollector/file/category.md | 2 +- .../12.0/admin/datacollector/file/overview.md | 10 +- .../12.0/admin/datacollector/file/results.md | 14 +- .../12.0/admin/datacollector/file/summary.md | 8 +- .../admin/datacollector/file/targetfiles.md | 43 ++- .../datacollector/fsaa/activitysettings.md | 31 +- .../fsaa/appletsettings/appletsettings.md | 14 +- .../fsaa/appletsettings/spnmapping.md | 2 +- .../datacollector/fsaa/azuretenantmapping.md | 14 +- .../admin/datacollector/fsaa/bulkimport.md | 8 +- .../certificateauthority.md | 8 +- .../certificatemanagement.md | 46 ++- .../manualcertificate.md | 22 +- .../defaultscopingoptions.md | 6 +- .../fsaa/defaultscopingoptions/filedetails.md | 18 +- .../defaultscopingoptions/fileproperties.md | 4 +- .../defaultscopingoptions/scansettings.md | 12 +- .../12.0/admin/datacollector/fsaa/overview.md | 8 +- .../datacollector/fsaa/queryselection.md | 30 +- .../datacollector/fsaa/scanserverselection.md | 10 +- .../admin/datacollector/fsaa/scansettings.md | 36 +-- .../datacollector/fsaa/scopingoptions.md | 38 +-- .../datacollector/fsaa/scopingqueries.md | 16 +- .../admin/datacollector/fsaa/sddcriteria.md | 4 +- .../fsaa/sensitivedatasettings.md | 15 +- .../datacollector/fsaa/standardtables.md | 20 +- .../admin/datacollector/fsaa/workflows.md | 91 +++--- .../datacollector/grouppolicy/category.md | 14 +- .../datacollector/grouppolicy/options.md | 6 +- .../datacollector/grouppolicy/overview.md | 12 +- .../datacollector/grouppolicy/policieslist.md | 10 +- .../datacollector/grouppolicy/summary.md | 6 +- .../admin/datacollector/grouppolicy/target.md | 14 +- .../admin/datacollector/inifile/overview.md | 4 +- .../admin/datacollector/inifile/properties.md | 8 +- .../admin/datacollector/inifile/summary.md | 7 +- .../datacollector/inifile/targetfiles.md | 2 +- .../12.0/admin/datacollector/ldap.md | 14 +- .../12.0/admin/datacollector/nis/category.md | 2 +- .../admin/datacollector/nis/configurejob.md | 16 +- .../12.0/admin/datacollector/nis/overview.md | 6 +- .../12.0/admin/datacollector/nis/query.md | 4 +- .../12.0/admin/datacollector/nis/results.md | 16 +- .../12.0/admin/datacollector/nis/settings.md | 8 +- .../admin/datacollector/nis/sidmappings.md | 9 +- .../admin/datacollector/nis/standardtables.md | 7 +- .../12.0/admin/datacollector/nis/summary.md | 8 +- .../admin/datacollector/nosql/category.md | 2 +- .../admin/datacollector/nosql/configurejob.md | 19 +- .../admin/datacollector/nosql/criteria.md | 12 +- .../12.0/admin/datacollector/nosql/filter.md | 22 +- .../12.0/admin/datacollector/nosql/options.md | 22 +- .../admin/datacollector/nosql/overview.md | 12 +- .../12.0/admin/datacollector/nosql/results.md | 9 +- .../12.0/admin/datacollector/nosql/summary.md | 9 +- .../12.0/admin/datacollector/overview.md | 61 ++-- .../passwordsecurity/dictionaries.md | 46 +-- .../datacollector/passwordsecurity/options.md | 4 +- .../passwordsecurity/overview.md | 6 +- .../datacollector/passwordsecurity/results.md | 6 +- .../datacollector/passwordsecurity/summary.md | 5 +- .../admin/datacollector/permissionmatrix.md | 15 +- .../datacollector/powershell/editquery.md | 18 +- .../admin/datacollector/powershell/options.md | 10 +- .../datacollector/powershell/overview.md | 6 +- .../admin/datacollector/powershell/results.md | 4 +- .../datacollector/powershell/sampleserver.md | 8 +- .../admin/datacollector/powershell/summary.md | 5 +- .../12.0/admin/datacollector/registry.md | 29 +- .../12.0/admin/datacollector/script/add.md | 10 +- .../12.0/admin/datacollector/script/editor.md | 12 +- .../admin/datacollector/script/example1.md | 28 +- .../admin/datacollector/script/example2.md | 23 +- .../datacollector/script/methodsproperties.md | 6 +- .../admin/datacollector/script/overview.md | 10 +- .../admin/datacollector/script/properties.md | 34 +-- .../admin/datacollector/script/reference.md | 18 +- .../12.0/admin/datacollector/script/run.md | 8 +- .../12.0/admin/datacollector/services.md | 17 +- .../smartlog/collectionmethod.md | 18 +- .../admin/datacollector/smartlog/criteria.md | 19 +- .../datacollector/smartlog/eventlogoptions.md | 6 +- .../admin/datacollector/smartlog/logstate.md | 10 +- .../admin/datacollector/smartlog/logtype.md | 8 +- .../admin/datacollector/smartlog/overview.md | 6 +- .../admin/datacollector/smartlog/results.md | 4 +- .../datacollector/smartlog/samplehost.md | 12 +- .../admin/datacollector/smartlog/summary.md | 4 +- .../smartlog/targetlog/filedetectionlog.md | 2 +- .../smartlog/targetlog/targetlog.md | 8 +- .../smartlog/targetlog/windowseventlog.md | 6 +- .../datacollector/spaa/activitydatescope.md | 10 +- .../spaa/activityloglocations.md | 14 +- .../datacollector/spaa/additionalscoping.md | 26 +- .../admin/datacollector/spaa/agentsettings.md | 8 +- .../datacollector/spaa/bulkimportsettings.md | 10 +- .../12.0/admin/datacollector/spaa/category.md | 6 +- .../admin/datacollector/spaa/configurejob.md | 44 +-- .../datacollector/spaa/dlpauditsettings.md | 31 +- .../admin/datacollector/spaa/droptables.md | 22 +- .../12.0/admin/datacollector/spaa/overview.md | 16 +- .../12.0/admin/datacollector/spaa/results.md | 11 +- .../datacollector/spaa/scanscopingoptions.md | 43 +-- .../datacollector/spaa/selectdlpcriteria.md | 16 +- .../12.0/admin/datacollector/spaa/settings.md | 60 ++-- .../datacollector/spaa/standardtables.md | 30 +- .../12.0/admin/datacollector/spaa/summary.md | 7 +- .../admin/datacollector/spaa/testaccess.md | 8 +- .../12.0/admin/datacollector/sql/category.md | 2 +- .../admin/datacollector/sql/configurejob.md | 38 +-- .../12.0/admin/datacollector/sql/criteria.md | 12 +- .../datacollector/sql/customqueryoracle.md | 6 +- .../admin/datacollector/sql/customquerysql.md | 6 +- .../12.0/admin/datacollector/sql/filter.md | 38 +-- .../12.0/admin/datacollector/sql/options.md | 12 +- .../12.0/admin/datacollector/sql/overview.md | 6 +- .../12.0/admin/datacollector/sql/results.md | 6 +- .../12.0/admin/datacollector/sql/rowkey.md | 6 +- .../12.0/admin/datacollector/sql/settings.md | 2 +- .../12.0/admin/datacollector/sql/summary.md | 7 +- .../datacollector/systeminfo/filetypes.md | 6 +- .../datacollector/systeminfo/jobscope.md | 2 +- .../admin/datacollector/systeminfo/options.md | 6 +- .../datacollector/systeminfo/overview.md | 10 +- .../datacollector/systeminfo/probableowner.md | 6 +- .../admin/datacollector/systeminfo/results.md | 6 +- .../admin/datacollector/systeminfo/summary.md | 5 +- .../datacollector/systeminfo/vipmembership.md | 4 +- .../textsearch/advancedcriteria.md | 8 +- .../datacollector/textsearch/overview.md | 10 +- .../admin/datacollector/textsearch/results.md | 6 +- .../textsearch/searchcriteria.md | 4 +- .../datacollector/textsearch/sourcefiles.md | 14 +- .../admin/datacollector/textsearch/summary.md | 5 +- .../admin/datacollector/unix/editscript.md | 2 +- .../12.0/admin/datacollector/unix/input.md | 4 +- .../12.0/admin/datacollector/unix/overview.md | 10 +- .../12.0/admin/datacollector/unix/results.md | 12 +- .../datacollector/usersgroups/overview.md | 10 +- .../usersgroups/results/groups.md | 4 +- .../usersgroups/results/results.md | 2 +- .../usersgroups/results/security.md | 4 +- .../usersgroups/results/users.md | 10 +- .../datacollector/usersgroups/summary.md | 5 +- .../datacollector/wmicollector/classes.md | 4 +- .../datacollector/wmicollector/overview.md | 10 +- .../datacollector/wmicollector/properties.md | 10 +- .../datacollector/wmicollector/samplehost.md | 6 +- .../datacollector/wmicollector/summary.md | 4 +- .../12.0/admin/hostdiscovery/activities.md | 2 +- .../12.0/admin/hostdiscovery/log.md | 4 +- .../12.0/admin/hostdiscovery/overview.md | 2 +- .../12.0/admin/hostdiscovery/queries.md | 8 +- .../wizard/addomaincontrollers.md | 12 +- .../admin/hostdiscovery/wizard/adexchange.md | 10 +- .../admin/hostdiscovery/wizard/adgeneral.md | 10 +- .../12.0/admin/hostdiscovery/wizard/csv.md | 10 +- .../admin/hostdiscovery/wizard/database.md | 14 +- .../admin/hostdiscovery/wizard/ipnetwork.md | 18 +- .../admin/hostdiscovery/wizard/overview.md | 9 +- .../12.0/admin/hostmanagement/actions/add.md | 10 +- .../hostmanagement/actions/deletehost.md | 20 +- .../hostmanagement/actions/deletelist.md | 12 +- .../admin/hostmanagement/actions/editlist.md | 2 +- .../admin/hostmanagement/actions/editquery.md | 4 +- .../admin/hostmanagement/actions/export.md | 2 +- .../hostmanagement/actions/importhost.md | 22 +- .../hostmanagement/actions/importlocation.md | 34 +-- .../admin/hostmanagement/actions/overview.md | 13 +- .../admin/hostmanagement/actions/refresh.md | 4 +- .../admin/hostmanagement/actions/rename.md | 4 +- .../hostmanagement/actions/savetolist.md | 2 +- .../admin/hostmanagement/actions/saveview.md | 12 +- .../admin/hostmanagement/actions/suspend.md | 4 +- .../admin/hostmanagement/actions/viewhost.md | 6 +- .../12.0/admin/hostmanagement/datagrid.md | 6 +- .../12.0/admin/hostmanagement/lists.md | 35 +-- .../12.0/admin/hostmanagement/overview.md | 8 +- .../12.0/admin/jobs/features.md | 44 +-- .../12.0/admin/jobs/group/overview.md | 38 +-- .../admin/jobs/group/settings/connection.md | 23 +- .../12.0/admin/jobs/group/settings/history.md | 14 +- .../group/settings/hostlistsassignment.md | 18 +- .../admin/jobs/group/settings/reporting.md | 16 +- .../admin/jobs/group/settings/settings.md | 20 +- .../12.0/admin/jobs/group/settings/storage.md | 12 +- .../12.0/admin/jobs/instantiate.md | 8 +- .../ad_passwordexpirationnotification.md | 52 ++-- .../instantjobs/ex_registerazureappauth.md | 10 +- .../jobs/instantjobs/fs_migrateschema.md | 42 +-- .../12.0/admin/jobs/instantjobs/overview.md | 12 +- .../instantjobs/sas_executionstatistics.md | 4 +- .../instantjobs/sp_registerazureappauth.md | 8 +- .../admin/jobs/instantjobs/sp_removehost.md | 4 +- .../12.0/admin/jobs/job/configure/actions.md | 2 +- .../analysiscustomizableparameters.md | 8 +- .../12.0/admin/jobs/job/configure/hosts.md | 2 +- .../12.0/admin/jobs/job/configure/queries.md | 14 +- .../12.0/admin/jobs/job/configure/reports.md | 2 +- .../12.0/admin/jobs/job/create.md | 6 +- .../12.0/admin/jobs/job/disableenable.md | 16 +- .../12.0/admin/jobs/job/overview.md | 10 +- .../admin/jobs/job/properties/autoretry.md | 2 +- .../admin/jobs/job/properties/connection.md | 2 +- .../12.0/admin/jobs/job/properties/general.md | 4 +- .../12.0/admin/jobs/job/properties/history.md | 4 +- .../admin/jobs/job/properties/performance.md | 6 +- .../admin/jobs/job/properties/reportroles.md | 8 +- .../jobs/job/properties/reportsettings.md | 4 +- .../12.0/admin/jobs/job/properties/storage.md | 2 +- .../12.0/admin/jobs/job/results.md | 2 +- .../12.0/admin/jobs/job/status.md | 2 +- .../12.0/admin/jobs/overview.md | 6 +- .../12.0/admin/maintenance/backuprecovery.md | 10 +- .../12.0/admin/maintenance/bestpractices.md | 36 +-- .../12.0/admin/maintenance/troubleshooting.md | 10 +- .../12.0/admin/navigate/activitiespane.md | 6 +- .../12.0/admin/navigate/datagrid.md | 34 +-- .../12.0/admin/navigate/overview.md | 6 +- .../12.0/admin/navigate/pane.md | 2 +- .../accessanalyzer/12.0/admin/navigate/top.md | 2 +- docs/accessanalyzer/12.0/admin/overview.md | 2 +- .../admin/report/chartwizard/chartformat.md | 2 +- .../admin/report/chartwizard/configure.md | 28 +- .../admin/report/chartwizard/datasource.md | 4 +- .../12.0/admin/report/chartwizard/overview.md | 4 +- .../12.0/admin/report/cleanup.md | 10 +- .../12.0/admin/report/create.md | 16 +- docs/accessanalyzer/12.0/admin/report/edit.md | 8 +- .../report/interactivegrids/copyingcells.md | 2 +- .../admin/report/interactivegrids/grouping.md | 8 +- .../admin/report/interactivegrids/overview.md | 6 +- .../admin/report/interactivegrids/paging.md | 10 +- .../report/interactivegrids/searchfilter.md | 14 +- .../12.0/admin/report/overview.md | 2 +- docs/accessanalyzer/12.0/admin/report/tags.md | 8 +- docs/accessanalyzer/12.0/admin/report/view.md | 4 +- .../12.0/admin/report/wizard/authoring.md | 10 +- .../12.0/admin/report/wizard/email.md | 8 +- .../12.0/admin/report/wizard/layout.md | 8 +- .../12.0/admin/report/wizard/overview.md | 10 +- .../admin/report/wizard/publishsecurity.md | 4 +- .../12.0/admin/report/wizard/widgets.md | 2 +- .../12.0/admin/runninginstances/jobdetails.md | 2 +- .../12.0/admin/runninginstances/overview.md | 6 +- .../12.0/admin/schedule/overview.md | 2 +- .../12.0/admin/schedule/renamewizard.md | 8 +- .../12.0/admin/schedule/wizard.md | 10 +- .../admin/schema/sqldc/coretables/overview.md | 6 +- .../schema/sqldc/enumeration/overview.md | 10 +- .../schema/sqldc/reportingtables/overview.md | 8 +- .../12.0/admin/schema/sqldc/views/overview.md | 2 +- .../access/restapi/assignappaccess.md | 12 +- .../admin/settings/access/restapi/getdata.md | 8 +- .../settings/access/restapi/obtaintoken.md | 2 +- .../settings/access/restapi/refreshtoken.md | 8 +- .../settings/access/rolebased/assignroles.md | 26 +- .../access/rolebased/configureroles.md | 20 +- .../settings/access/rolebased/customroles.md | 10 +- .../admin/settings/access/rolebased/faq.md | 61 ++-- .../settings/access/rolebased/overview.md | 52 ++-- .../access/rolebased/roledefinitions.md | 42 +-- .../rolebased/scheduleserviceaccount.md | 30 +- .../access/rolebased/securereports.md | 30 +- .../settings/access/rolebased/workflow.md | 41 +-- .../admin/settings/application/overview.md | 72 ++--- .../12.0/admin/settings/application/vault.md | 43 +-- .../connection/create/activedirectory.md | 16 +- .../admin/settings/connection/create/aws.md | 10 +- .../settings/connection/create/create.md | 56 ++-- .../settings/connection/create/dropbox.md | 4 +- .../settings/connection/create/entraid.md | 2 +- .../connection/create/exchangemodernauth.md | 4 +- .../connection/create/localwindows.md | 14 +- .../settings/connection/create/oracle.md | 22 +- .../admin/settings/connection/create/sql.md | 6 +- .../admin/settings/connection/create/task.md | 8 +- .../admin/settings/connection/create/unix.md | 4 +- .../settings/connection/create/webservices.md | 4 +- .../connection/cyberarkintegration.md | 57 ++-- .../12.0/admin/settings/connection/gmsa.md | 8 +- .../admin/settings/connection/overview.md | 34 +-- .../12.0/admin/settings/exchange.md | 46 +-- .../12.0/admin/settings/history.md | 55 ++-- .../12.0/admin/settings/hostdiscovery.md | 29 +- .../12.0/admin/settings/hostinventory.md | 51 ++-- .../12.0/admin/settings/notification.md | 57 ++-- .../12.0/admin/settings/overview.md | 20 +- .../12.0/admin/settings/reporting.md | 57 ++-- .../12.0/admin/settings/schedule.md | 85 +++--- .../admin/settings/sensitivedata/criteria.md | 21 +- .../settings/sensitivedata/exclusions/add.md | 12 +- .../sensitivedata/exclusions/delete.md | 4 +- .../settings/sensitivedata/exclusions/edit.md | 4 +- .../sensitivedata/exclusions/export.md | 4 +- .../sensitivedata/exclusions/import.md | 11 +- .../sensitivedata/exclusions/overview.md | 11 +- .../admin/settings/sensitivedata/overview.md | 2 +- .../12.0/admin/settings/servicenow.md | 17 +- .../12.0/admin/settings/storage/add.md | 22 +- .../12.0/admin/settings/storage/default.md | 31 +- .../12.0/admin/settings/storage/delete.md | 8 +- .../12.0/admin/settings/storage/overview.md | 12 +- .../12.0/admin/settings/storage/updateauth.md | 5 +- docs/accessanalyzer/12.0/cdsa/job.md | 16 +- docs/accessanalyzer/12.0/cdsa/overview.md | 2 +- docs/accessanalyzer/12.0/cdsa/presentation.md | 8 +- docs/accessanalyzer/12.0/gettingstarted.md | 34 +-- docs/accessanalyzer/12.0/index.md | 21 +- .../install/application/database/database.md | 70 ++--- .../application/database/otherlanguages.md | 44 ++- .../12.0/install/application/firstlaunch.md | 51 ++-- .../12.0/install/application/overview.md | 17 +- .../12.0/install/application/reports/adfs.md | 20 +- .../install/application/reports/disclaimer.md | 13 +- .../install/application/reports/domains.md | 12 +- .../install/application/reports/entraidsso.md | 32 +-- .../application/reports/kerberosencryption.md | 38 +-- .../12.0/install/application/reports/okta.md | 18 +- .../install/application/reports/overview.md | 24 +- .../install/application/reports/secure.md | 65 ++--- .../12.0/install/application/reports/sso.md | 22 +- .../install/application/reports/timeout.md | 6 +- .../12.0/install/application/updatelicense.md | 23 +- .../install/application/upgrade/overview.md | 44 +-- .../upgrade/solutionconsiderations.md | 41 ++- .../install/application/upgrade/wizard.md | 102 +++---- .../12.0/install/application/wizard.md | 17 +- .../filesystemproxy/configuredatacollector.md | 2 +- .../12.0/install/filesystemproxy/overview.md | 84 +++--- .../install/filesystemproxy/silentinstall.md | 24 +- .../filesystemproxy/troubleshooting.md | 11 +- .../12.0/install/filesystemproxy/uninstall.md | 14 +- .../12.0/install/filesystemproxy/upgrade.md | 22 +- .../12.0/install/filesystemproxy/wizard.md | 44 +-- .../12.0/install/mapicdo/appendix.md | 12 +- .../12.0/install/mapicdo/installation.md | 22 +- docs/accessanalyzer/12.0/install/overview.md | 2 +- .../12.0/install/sharepointagent/overview.md | 10 +- .../12.0/install/sharepointagent/upgrade.md | 8 +- .../12.0/install/sharepointagent/wizard.md | 10 +- .../activedirectory/activedirectory.md | 4 +- .../activedirectory/target/access.md | 6 +- .../target/activity/activity.md | 82 +++--- .../target/activity/filearchive.md | 44 +-- .../target/activity/threatprevention.md | 26 +- .../activedirectory/target/overview.md | 20 +- .../target.md | 2 +- .../12.0/requirements/aws/aws.md | 19 +- .../12.0/requirements/aws/configurescans.md | 42 ++- .../12.0/requirements/aws/target.md | 2 +- .../12.0/requirements/box/box.md | 4 +- .../databases/azuresql/azuresql.md | 10 +- .../databases/azuresql/azuresqlaccess.md | 12 +- .../12.0/requirements/databases/databases.md | 4 +- .../12.0/requirements/databases/db2.md | 2 +- .../12.0/requirements/databases/mongodb.md | 2 +- .../12.0/requirements/databases/mysql.md | 2 +- .../databases/oracle/leastprivilege.md | 71 ++--- .../requirements/databases/oracle/oracle.md | 2 +- .../12.0/requirements/databases/postgresql.md | 2 +- .../12.0/requirements/databases/redshift.md | 2 +- .../12.0/requirements/dropbox/dropbox.md | 23 +- .../12.0/requirements/dropbox/target.md | 10 +- .../12.0/requirements/entraid/entraid.md | 4 +- .../requirements/entraid/entraid/access.md | 52 ++-- .../entraid/entraid/entraroles.md | 40 +-- .../requirements/entraid/entraid/overview.md | 10 +- .../12.0/requirements/exchange/exchange.md | 25 +- .../exchange/exchangeonline/access.md | 62 ++-- .../exchange/exchangeonline/exchangeonline.md | 2 +- .../requirements/exchange/support/mailflow.md | 10 +- .../requirements/exchange/support/mapi.md | 2 +- .../exchange/support/powershell.md | 54 ++-- .../exchange/support/remoteconnections.md | 8 +- .../exchange/support/webservicesapi.md | 2 +- .../12.0/requirements/exchange/target.md | 14 +- .../requirements/filesystem/filesystem.md | 42 +-- .../filesystem/filesystems/azurefiles.md | 20 +- .../filesystems/azureinformationprotection.md | 14 +- .../filesystems/dellcelerravnx/access.md | 2 +- .../dellcelerravnx/activity/activity.md | 12 +- .../dellcelerravnx/activity/installcee.md | 30 +- .../dellcelerravnx/activity/validate.md | 35 ++- .../filesystems/dellcelerravnx/overview.md | 28 +- .../dellpowerscale/activity/activity.md | 26 +- .../dellpowerscale/activity/installcee.md | 16 +- .../activity/manualconfiguration.md | 17 +- .../dellpowerscale/activity/validate.md | 38 ++- .../filesystems/dellpowerscale/overview.md | 34 ++- .../filesystems/dellunity/access.md | 2 +- .../dellunity/activity/activity.md | 16 +- .../dellunity/activity/installcee.md | 18 +- .../dellunity/activity/setupunisphere.md | 8 +- .../dellunity/activity/validate.md | 35 ++- .../filesystems/dellunity/overview.md | 28 +- .../filesystem/filesystems/filesystems.md | 6 +- .../filesystems/hitachi/activity/activity.md | 8 +- .../hitachi/activity/configureaccesstologs.md | 10 +- .../hitachi/activity/configurelogs.md | 6 +- .../filesystems/hitachi/overview.md | 16 +- .../filesystem/filesystems/nasuni/access.md | 21 +- .../filesystem/filesystems/nasuni/activity.md | 20 +- .../filesystem/filesystems/nasuni/overview.md | 4 +- .../filesystems/netapp7mode/access/access.md | 2 +- .../netapp7mode/access/provisionaccess.md | 6 +- .../netapp7mode/activity/activity.md | 30 +- .../netapp7mode/activity/configurefpolicy.md | 26 +- .../netapp7mode/activity/customizefpolicy.md | 2 +- .../netapp7mode/activity/provisionactivity.md | 4 +- .../filesystems/netapp7mode/overview.md | 4 +- .../filesystems/netappcmode/access/access.md | 18 +- .../access/configureemptyfpolicy.md | 26 +- .../netappcmode/activity/activity.md | 26 +- .../netappcmode/activity/configurefirewall.md | 16 +- .../netappcmode/activity/configurefpolicy.md | 48 ++-- .../netappcmode/activity/provisionactivity.md | 14 +- .../filesystems/netappcmode/overview.md | 4 +- .../filesystem/filesystems/nutanix/access.md | 2 +- .../filesystems/nutanix/activity.md | 4 +- .../filesystems/nutanix/overview.md | 2 +- .../filesystem/filesystems/qumulo/activity.md | 7 +- .../filesystem/filesystems/qumulo/overview.md | 2 +- .../filesystems/windowsfile/access.md | 14 +- .../filesystems/windowsfile/activity.md | 14 +- .../filesystems/windowsfile/overview.md | 2 +- .../appletmodepermissions.md | 8 +- .../applet-mode-scans/appletmodeports.md | 2 +- .../local-mode-scans/localmodepermissions.md | 10 +- .../local-mode-scans/localmodeports.md | 2 +- .../proxymodeservicepermissions.md | 2 +- .../as-a-service/proxymodeserviceports.md | 4 +- .../proxy-mode-scans/proxymodeserver.md | 12 +- .../with-applet/proxymodeappletpermissions.md | 13 +- .../with-applet/proxymodeappletports.md | 12 +- .../filesystem/scanoptions/scanoptions.md | 26 +- .../12.0/requirements/overview.md | 35 ++- .../agent-based-scans/agentpermissions.md | 38 +-- .../agent-based-scans/agentports.md | 6 +- .../agent-less-scans/agentlesspermissions.md | 2 +- .../sharepoint/scanoptions/scanoptions.md | 6 +- .../requirements/sharepoint/sharepoint.md | 18 +- .../sharepoint/sharepoint/sharepoint.md | 2 +- .../sharepoint/sharepoint/access.md | 8 +- .../sharepoint/sharepoint/activity.md | 8 +- .../sharepoint/sharepoint/overview.md | 14 +- .../sharepoint/sharepointonline/access.md | 25 +- .../sharepoint/sharepointonline/activity.md | 40 ++- .../sharepoint/sharepointonline/overview.md | 14 +- .../12.0/requirements/unix/target.md | 22 +- .../criteriaeditor/configuration.md | 26 +- .../criteriaeditor/keyword.md | 4 +- .../criteriaeditor/overview.md | 19 +- .../criteriaeditor/regularexpression.md | 12 +- .../criteriaeditor/summary.md | 14 +- .../sensitivedatadiscovery/metadatatags.md | 2 +- .../12.0/sensitivedatadiscovery/overview.md | 7 +- .../supportedformats.md | 19 +- .../activity/ad_activitycollection.md | 31 +- .../activity/ad_ldapqueries.md | 18 +- .../activedirectory/activity/ad_lockouts.md | 2 +- .../changes/ad_computermodifications.md | 2 +- .../activity/changes/ad_groupmodifications.md | 4 +- .../activity/changes/ad_usermodifications.md | 2 +- .../activity/changes/overview.md | 2 +- .../activity/groupusage/ad_accesschanges.md | 8 +- .../activity/groupusage/ad_grouphosts.md | 4 +- .../groupusage/ad_groupmemberactivity.md | 13 +- .../operations/ad_authenticationprotocol.md | 4 +- .../operations/ad_domaincontrollertraffic.md | 8 +- .../activity/operations/ad_hardcodeddcs.md | 2 +- .../activity/operations/ad_loadbalancing.md | 8 +- .../activity/operations/ad_machineowners.md | 2 +- .../activity/operations/overview.md | 14 +- .../activedirectory/activity/overview.md | 6 +- .../privilegedaccounts/ad_adminaccounts.md | 9 +- .../ad_serviceaccountauth.md | 2 +- .../activity/privilegedaccounts/overview.md | 2 +- .../activedirectory/activity/recommended.md | 20 +- .../activedirectory/ad_securityassessment.md | 16 +- .../certificateauthority/ad_cacollection.md | 5 +- .../ad_certificateaudit.md | 4 +- .../ad_certificaterequests.md | 16 +- .../cleanup/ad_cleanupprogress.md | 12 +- .../computers/ad_deprovisioncomputers.md | 18 +- .../ad_deprovisioncomputers_status.md | 2 +- .../cleanup/computers/overview.md | 6 +- .../cleanup/configuretargetou.md | 8 +- .../deprovision/ad_deprovisiongroups.md | 36 +-- .../ad_deprovisiongroups_status.md | 2 +- .../cleanup/groups/overview.md | 14 +- .../stamping/ad_groupcleanup_permissions.md | 4 +- .../groups/stamping/ad_groupstamping.md | 2 +- .../activedirectory/cleanup/overview.md | 5 +- .../activedirectory/cleanup/recommended.md | 2 +- .../cleanup/users/ad_deprovisionusers.md | 22 +- .../users/ad_deprovisionusers_status.md | 2 +- .../activedirectory/cleanup/users/overview.md | 6 +- .../computers/ad_computerdelegation.md | 12 +- .../computers/ad_stalecomputers.md | 12 +- .../activedirectory/computers/overview.md | 8 +- .../activedirectory/computers/recommended.md | 16 +- .../activedirectory/domains/ad_dcsummary.md | 2 +- .../activedirectory/domains/ad_domaininfo.md | 4 +- .../domains/ad_dsrmsettings.md | 8 +- .../domains/ad_kerberoastingrisk.md | 13 +- .../collection/ad_domaincontrollers.md | 14 +- .../domains/collection/ad_dsrm.md | 8 +- .../domains/collection/ad_timesync.md | 2 +- .../domains/collection/overview.md | 12 +- .../activedirectory/domains/overview.md | 6 +- .../activedirectory/domains/recommended.md | 4 +- .../grouppolicy/ad_cpassword.md | 8 +- .../grouppolicy/ad_grouppolicy.md | 4 +- .../grouppolicy/ad_overlappinggpos.md | 4 +- .../grouppolicy/ad_passwordpolicies.md | 4 +- .../activedirectory/grouppolicy/overview.md | 6 +- .../grouppolicy/recommended.md | 4 +- .../groups/ad_circularnesting.md | 2 +- .../groups/ad_dclogongroups.md | 4 +- .../groups/ad_duplicategroups.md | 2 +- .../activedirectory/groups/ad_emptygroups.md | 2 +- .../groups/ad_groupprobableowners.md | 6 +- .../groups/ad_largestgroups.md | 6 +- .../groups/ad_mailsecuritygroups.md | 2 +- .../activedirectory/groups/ad_nestedgroups.md | 6 +- .../groups/ad_sensitivesecuritygroups.md | 2 +- .../activedirectory/groups/ad_stalegroups.md | 4 +- .../activedirectory/groups/overview.md | 15 +- .../activedirectory/groups/recommended.md | 10 +- .../users/ad_directmembership.md | 4 +- .../users/ad_duplicateusers.md | 2 +- .../activedirectory/users/ad_orphanedusers.md | 2 +- .../users/ad_passwordstatus.md | 2 +- .../users/ad_serviceaccounts.md | 2 +- .../activedirectory/users/ad_sidhistory.md | 2 +- .../activedirectory/users/ad_staleusers.md | 10 +- .../users/ad_userattributecompletion.md | 2 +- .../users/ad_userdelegation.md | 4 +- .../activedirectory/users/ad_usertoken.md | 2 +- .../activedirectory/users/ad_weakpasswords.md | 16 +- .../activedirectory/users/overview.md | 6 +- .../activedirectory/users/recommended.md | 22 +- .../activedirectoryinventory/1-ad_scan.md | 33 ++- .../activedirectoryinventory/2-ad_changes.md | 30 +- .../3-ad_exceptions.md | 6 +- .../activedirectoryinventory/overview.md | 11 +- .../activedirectoryinventory/recommended.md | 10 +- .../ad_brokeninheritance.md | 2 +- .../ad_openaccess.md | 2 +- .../ad_oupermissions.md | 4 +- .../ad_shadowaccess.md | 18 +- .../collection/ad_certificaterights.md | 4 +- .../collection/ad_computerrights.md | 4 +- .../collection/ad_containerrights.md | 4 +- .../collection/ad_domainrights.md | 4 +- .../collection/ad_grouprights.md | 4 +- .../collection/ad_ourights.md | 4 +- .../collection/ad_siterights.md | 4 +- .../collection/ad_userrights.md | 4 +- .../collection/overview.md | 2 +- .../computers/ad_computerpermissions.md | 4 +- .../computers/ad_lapspermissions.md | 2 +- .../containers/ad_adminsdholder.md | 4 +- .../containers/ad_containerpermissions.md | 4 +- .../containers/overview.md | 2 +- .../domains/ad_certificateauthorityrights.md | 4 +- .../domains/ad_certificatetemplates.md | 2 +- .../domains/ad_certificatevulnerabilities.md | 4 +- .../domains/ad_domainpermissions.md | 2 +- .../domains/ad_domainreplication.md | 2 +- .../groups/ad_groupmembershippermissions.md | 2 +- .../groups/ad_grouppermissions.md | 4 +- .../overview.md | 14 +- .../recommended.md | 8 +- .../sites/ad_dcshadowpermissions.md | 2 +- .../sites/ad_sitepermissions.md | 2 +- .../users/ad_resetpasswordpermissions.md | 2 +- .../users/ad_userpermissions.md | 4 +- .../12.0/solutions/anyid/anyid_csv.md | 19 +- .../12.0/solutions/anyid/anyid_epicclarity.md | 21 +- .../12.0/solutions/anyid/anyid_paycom.md | 27 +- .../12.0/solutions/anyid/anyid_salesforce.md | 23 +- .../12.0/solutions/anyid/overview.md | 24 +- .../solutions/aws/collection/1.aws_orgscan.md | 2 +- .../solutions/aws/collection/2.aws_s3scan.md | 4 +- .../solutions/aws/collection/3.aws_iamscan.md | 4 +- .../aws/collection/4.aws_s3sddscan.md | 6 +- .../12.0/solutions/aws/collection/overview.md | 2 +- .../solutions/aws/groups/aws_groupmembers.md | 2 +- .../aws/groups/aws_nopolicygroups.md | 4 +- .../solutions/aws/groups/aws_stalegroups.md | 14 +- .../aws/organizations/aws_accounts.md | 2 +- .../organizations/aws_memberaccountusers.md | 6 +- .../solutions/aws/organizations/overview.md | 6 +- .../12.0/solutions/aws/overview.md | 32 +-- .../aws/policies/aws_custommanagedpolicies.md | 2 +- .../aws/policies/aws_inlinepolicies.md | 2 +- .../aws/policies/aws_managedpolicies.md | 2 +- .../aws/policies/aws_sensitivepolicies.md | 2 +- .../aws/policies/aws_unusedmanagedpolicies.md | 14 +- .../aws/policies/aws_userpolicies.md | 2 +- .../12.0/solutions/aws/policies/overview.md | 4 +- .../12.0/solutions/aws/recommended.md | 50 ++-- .../12.0/solutions/aws/roles/aws_roles.md | 2 +- .../solutions/aws/roles/aws_staleroles.md | 20 +- .../12.0/solutions/aws/roles/overview.md | 4 +- .../solutions/aws/s3content/aws_s3buckets.md | 2 +- .../aws/s3content/aws_s3buckettags.md | 6 +- .../12.0/solutions/aws/s3content/overview.md | 2 +- .../s3permissions/aws_brokeninheritance.md | 2 +- .../s3permissions/aws_effectivepermissions.md | 2 +- .../aws/s3permissions/aws_openbuckets.md | 2 +- .../aws/sensitivedata/aws_sensitivedata.md | 2 +- .../aws_sensitivedata_permissions.md | 2 +- .../solutions/aws/users/aws_accesskeys.md | 2 +- .../12.0/solutions/aws/users/aws_mfastatus.md | 2 +- .../solutions/aws/users/aws_rootaccounts.md | 2 +- .../solutions/aws/users/aws_staleusers.md | 10 +- .../box/activity/forensics/box_deletions.md | 2 +- .../box/activity/forensics/box_downloads.md | 2 +- .../forensics/box_externaluseractivity.md | 2 +- .../box_externalusercollaborations.md | 2 +- .../forensics/box_permissionchanges.md | 4 +- .../box/activity/forensics/box_sharing.md | 2 +- .../box/activity/forensics/overview.md | 2 +- .../12.0/solutions/box/activity/overview.md | 5 +- .../suspiciousactivity/box_failedlogins.md | 2 +- .../box_firsttimefolderaccess.md | 2 +- .../box_unusualdownloadactivity.md | 4 +- .../box_unusualuseractivity.md | 4 +- .../suspiciousactivity/box_weekendactivity.md | 2 +- .../usagestatistics/box_folders_mostactive.md | 2 +- .../usagestatistics/box_folders_stale.md | 2 +- .../usagestatistics/box_users_mostactive.md | 2 +- .../12.0/solutions/box/box_access.md | 4 +- .../12.0/solutions/box/box_groupmembership.md | 2 +- .../box/collection/1-box_access_scans.md | 43 ++- .../box/collection/1-box_activity_scans.md | 31 +- .../solutions/box/collection/2-box_import.md | 12 +- .../12.0/solutions/box/collection/overview.md | 18 +- .../solutions/box/content/box_filemetrics.md | 4 +- .../box/content/box_foldermetrics.md | 4 +- .../12.0/solutions/box/overview.md | 12 +- .../12.0/solutions/box/recommended.md | 39 ++- .../1-azuresql_permissionscan.md | 4 +- .../solutions/databases/azuresql/overview.md | 5 +- .../databases/azuresql/recommended.md | 2 +- .../db2/collection/db2_configuration.md | 10 +- .../db2/collection/db2_permissionscan.md | 14 +- .../db2/collection/db2_sensitivedatascan.md | 26 +- .../databases/db2/db2_databasesizing.md | 2 +- .../12.0/solutions/databases/db2/overview.md | 31 +- .../db2/permissions/db2_directpermissions.md | 2 +- .../permissions/db2_effectivepermissions.md | 2 +- .../solutions/databases/db2/recommended.md | 27 +- .../db2/sensitivedata/db2_sensitivedata.md | 2 +- .../db2_sensitivedatapermissions.md | 2 +- .../collection/mongodb_configuration.md | 4 +- .../collection/mongodb_sensitivedatascan.md | 16 +- .../databases/mongodb/collection/overview.md | 6 +- .../mongodb/mongodb_database_sizing.md | 2 +- .../mongodb/mongodb_sensitivedata.md | 4 +- .../solutions/databases/mongodb/overview.md | 36 +-- .../databases/mongodb/recommended.md | 29 +- .../mysql/collection/mysql_configuration.md | 4 +- .../collection/mysql_sensitivedatascan.md | 24 +- .../mysql/collection/mysql_tableprivileges.md | 6 +- .../databases/mysql/collection/overview.md | 12 +- .../databases/mysql/mysql_databasesizing.md | 2 +- .../solutions/databases/mysql/overview.md | 18 +- .../solutions/databases/mysql/recommended.md | 22 +- .../sensitivedata/mysql_sensitivedata.md | 2 +- .../mysql_sensitivedatapermissions.md | 2 +- .../oracle/activity/oracle_activity.md | 2 +- .../oracle/activity/oracle_logons.md | 2 +- .../activity/oracle_permissionchanges.md | 2 +- .../oracle/activity/oracle_schemachanges.md | 2 +- .../activity/oracle_sensitivedataactivity.md | 2 +- .../activity/oracle_suspiciousactivity.md | 4 +- .../oracle/activity/oracle_unusualactivity.md | 2 +- .../databases/oracle/activity/overview.md | 2 +- .../oracle/collection/0-oracle_servers.md | 6 +- .../collection/1-oracle_permissionsscan.md | 12 +- .../collection/2-oracle_sensitivedatascan.md | 10 +- .../collection/3-oracle_activityscan.md | 12 +- .../4-oracle_defaultpasswordusers.md | 10 +- .../collection/5-oracle_configuration.md | 8 +- .../configuration/oracle_databaselinks.md | 6 +- .../configuration/oracle_databasesizing.md | 2 +- .../oracle_datadictionaryprotection.md | 2 +- .../oracle_instancenameissues.md | 4 +- .../oracle_remoteosauthentication.md | 2 +- .../oracle/configuration/overview.md | 4 +- .../solutions/databases/oracle/overview.md | 18 +- .../oracle_domainuserpermissions.md | 2 +- .../permissions/oracle_objectpermissions.md | 2 +- .../permissions/oracle_publicpermissions.md | 2 +- .../permissions/oracle_serverpermissions.md | 2 +- .../oracle_sysschemapermissions.md | 2 +- .../solutions/databases/oracle/recommended.md | 38 ++- .../sensitivedata/oracle_sensitivedata.md | 2 +- .../oracle_sensitivedatapermissions.md | 2 +- .../usersroles/oracle_passwordissues.md | 4 +- .../oracle/usersroles/oracle_rolemembers.md | 2 +- .../usersroles/oracle_systemadministrators.md | 2 +- .../oracle/usersroles/oracle_users.md | 2 +- .../12.0/solutions/databases/overview.md | 8 +- .../collection/pgsql_configuration.md | 2 +- .../collection/pgsql_sensitivedatascan.md | 20 +- .../collection/pgsql_tableprivileges.md | 4 +- .../databases/postgresql/overview.md | 31 +- .../postgresql/pgsql_databasesizing.md | 2 +- .../databases/postgresql/recommended.md | 20 +- .../sensitivedata/pgsql_sensitivedata.md | 2 +- .../pgsql_sensitivedatapermissions.md | 2 +- .../databases/redshift/collection/overview.md | 2 +- .../collection/redshift_configuration.md | 2 +- .../collection/redshift_sensitivedatascan.md | 25 +- .../collection/redshift_tableprivileges.md | 4 +- .../solutions/databases/redshift/overview.md | 18 +- .../databases/redshift/recommended.md | 14 +- .../redshift/redshift_databasesizing.md | 6 +- .../redshift/sensitive_data/overview.md | 2 +- .../sensitive_data/redshift_sensitivedata.md | 2 +- .../redshift_sensitivedatapermissions.md | 2 +- .../databases/sql/activity/sql_activity.md | 2 +- .../databases/sql/activity/sql_logons.md | 2 +- .../sql/activity/sql_permissionchanges.md | 2 +- .../sql/activity/sql_sensitivedataactivity.md | 2 +- .../sql/activity/sql_unusualactivity.md | 2 +- .../sql/collection/0-sql_instancediscovery.md | 2 +- .../sql/collection/1-sql_permissionsscan.md | 14 +- .../sql/collection/2-sql_sensitivedatascan.md | 12 +- .../sql/collection/3-sql_activityscan.md | 14 +- .../sql/collection/4-sql_serverlogons.md | 2 +- .../sql/collection/5-sql_serversettings.md | 18 +- .../databases/sql/configuration/overview.md | 8 +- .../sql/configuration/sql_authentication.md | 8 +- .../sql/configuration/sql_bestpractices.md | 2 +- .../sql/configuration/sql_cmdshell.md | 6 +- .../sql/configuration/sql_databasesizing.md | 2 +- .../sql/configuration/sql_linkedservers.md | 6 +- .../12.0/solutions/databases/sql/overview.md | 4 +- .../databases/sql/permissions/overview.md | 2 +- .../sql/permissions/sql_controlserver.md | 2 +- .../sql/permissions/sql_directpermissions.md | 2 +- .../permissions/sql_domainuserpermissions.md | 2 +- .../sql/permissions/sql_publicpermissions.md | 4 +- .../sql/permissions/sql_serverpermissions.md | 2 +- .../solutions/databases/sql/recommended.md | 18 +- .../sql/sensitivedata/sql_sensitivedata.md | 2 +- .../sql_sensitivedatapermissions.md | 2 +- .../databases/sql/sql_securityassessment.md | 4 +- .../sql/usersroles/sql_databaseprinciples.md | 2 +- .../sql/usersroles/sql_passwordissues.md | 6 +- .../sql/usersroles/sql_rolemembers.md | 2 +- .../sql/usersroles/sql_serverprincipals.md | 2 +- .../databases/sql/usersroles/sql_sqllogins.md | 2 +- .../databases/sql/usersroles/sql_sysadmins.md | 2 +- .../12.0/solutions/databases/update-schema.md | 2 +- .../collection/1-dropbox_permissions_scan.md | 16 +- .../dropbox/collection/1-dropbox_sdd_scan.md | 8 +- .../2-dropbox_permissions_bulk_import.md | 6 +- .../collection/2-dropbox_sdd_bulk_import.md | 4 +- .../solutions/dropbox/collection/overview.md | 26 +- .../12.0/solutions/dropbox/dropbox_access.md | 2 +- .../12.0/solutions/dropbox/dropbox_content.md | 14 +- .../dropbox/dropbox_groupmembership.md | 2 +- .../dropbox/dropbox_sensitivedata.md | 4 +- .../12.0/solutions/dropbox/dropbox_sharing.md | 8 +- .../12.0/solutions/dropbox/overview.md | 16 +- .../12.0/solutions/dropbox/recommended.md | 37 +-- .../entraid/groups/aad_circularnesting.md | 2 +- .../entraid/groups/aad_duplicategroups.md | 2 +- .../entraid/groups/aad_emptygroups.md | 2 +- .../entraid/groups/aad_groupdirsync.md | 2 +- .../entraid/groups/aad_largestgroups.md | 8 +- .../entraid/groups/aad_nestedgroups.md | 8 +- .../entraid/groups/aad_probableowners.md | 8 +- .../entraid/groups/aad_stalegroups.md | 4 +- .../12.0/solutions/entraid/groups/overview.md | 13 +- .../12.0/solutions/entraid/overview.md | 2 +- .../12.0/solutions/entraid/recommended.md | 10 +- .../entraid/users/aad_directmembership.md | 4 +- .../entraid/users/aad_disabledusers.md | 4 +- .../solutions/entraid/users/aad_staleusers.md | 6 +- .../users/aad_userattributecompletion.md | 2 +- .../entraid/users/aad_userdirsync.md | 2 +- .../12.0/solutions/entraid/users/overview.md | 4 +- .../solutions/entraidinventory/1-aad_scan.md | 8 +- .../entraidinventory/2-aad_exceptions.md | 9 +- .../solutions/entraidinventory/recommended.md | 14 +- .../exchange/casmetrics/ex_activesync.md | 6 +- .../exchange/casmetrics/ex_aspolicies.md | 14 +- .../exchange/casmetrics/ex_iislogs.md | 6 +- .../exchange/casmetrics/ex_owatraffic.md | 4 +- .../exchange/casmetrics/ex_rpctraffic.md | 4 +- .../solutions/exchange/casmetrics/overview.md | 4 +- .../exchange/casmetrics/recommended.md | 6 +- .../databases/collection/ex_dbinfo.md | 2 +- .../databases/collection/ex_pfinfo.md | 4 +- .../exchange/databases/collection/overview.md | 4 +- .../exchange/databases/ex_dbsizing.md | 10 +- .../exchange/databases/ex_dbtrending.md | 4 +- .../solutions/exchange/databases/overview.md | 2 +- .../exchange/databases/recommended.md | 4 +- .../distributionlists/ex_dlcleanup.md | 2 +- .../distributionlists/ex_groupexpansion.md | 2 +- .../membershipanalysis/ex_circularnesting.md | 2 +- .../membershipanalysis/ex_emptygroups.md | 2 +- .../membershipanalysis/ex_largestgroups.md | 2 +- .../membershipanalysis/ex_nestedgroups.md | 2 +- .../membershipanalysis/ex_stalegroups.md | 2 +- .../exchange/distributionlists/recommended.md | 2 +- .../solutions/exchange/ex_useroverview.md | 7 +- .../collection/appletstatuscheck.md | 2 +- .../collection/ex_metricscollection.md | 32 +-- .../collection/ex_metricsdetails.md | 12 +- .../hubmetrics/collection/overview.md | 4 +- .../exchange/hubmetrics/ex_deliverytimes.md | 2 +- .../exchange/hubmetrics/ex_dlmetrics.md | 2 +- .../exchange/hubmetrics/ex_domainmetrics.md | 2 +- .../exchange/hubmetrics/ex_hourlymetrics.md | 4 +- .../exchange/hubmetrics/ex_messagesize.md | 2 +- .../exchange/hubmetrics/ex_servermetrics.md | 2 +- .../exchange/hubmetrics/ex_usermetrics.md | 2 +- .../solutions/exchange/hubmetrics/overview.md | 8 +- .../exchange/hubmetrics/recommended.md | 6 +- .../exchange/mailboxes/ex_features.md | 2 +- .../mailboxes/logons/ex_mailboxlogons.md | 4 +- .../exchange/mailboxes/logons/overview.md | 4 +- .../solutions/exchange/mailboxes/overview.md | 4 +- .../permissions/collection/ex_sendas.md | 2 +- .../mailboxes/permissions/ex_admingroups.md | 2 +- .../mailboxes/permissions/ex_mailboxaccess.md | 6 +- .../mailboxes/permissions/overview.md | 2 +- .../exchange/mailboxes/recommended.md | 22 +- .../mailboxes/sizing/ex_mailboxsizes.md | 6 +- .../mailboxes/sizing/ex_stalemailboxes.md | 4 +- .../mailboxes/sizing/ex_storesizes.md | 2 +- .../exchange/online/mailflow/ex_mailflow.md | 16 +- .../online/mailflow/ex_mailflow_dl.md | 2 +- .../online/mailflow/ex_mailflow_domain.md | 6 +- .../online/mailflow/ex_mailflow_mailbox.md | 6 +- .../mailflow/ex_mailflow_orgoverview.md | 4 +- .../solutions/exchange/online/recommended.md | 16 +- .../12.0/solutions/exchange/overview.md | 26 +- .../publicfolders/content/pf_content.md | 2 +- .../publicfolders/content/pf_contentscans.md | 2 +- .../growthsize/pf_folderscans.md | 2 +- .../publicfolders/growthsize/pf_foldersize.md | 6 +- .../ownership/pf_folderownership.md | 16 +- .../publicfolders/ownership/pf_owners.md | 2 +- .../permissions/pf_entitlements.md | 4 +- .../permissions/pf_entitlementscans.md | 2 +- .../exchange/publicfolders/pf_overview.md | 2 +- .../exchange/publicfolders/recommended.md | 4 +- .../12.0/solutions/exchange/recommended.md | 14 +- .../collection/ex_mailbox_sdd.md | 14 +- .../collection/ex_publicfolder_sdd.md | 8 +- .../exchange/sensitivedata/ex_sddresults.md | 6 +- .../exchange/sensitivedata/overview.md | 2 +- .../activity/forensics/fs_deletions.md | 27 +- .../forensics/fs_permissionchanges.md | 2 +- .../activity/fs_leastprivilegedaccess.md | 8 +- .../activity/security/fs_adminactvity.md | 4 +- .../activity/security/fs_highriskactivity.md | 4 +- .../activity/security/fs_localuseractivity.md | 2 +- .../suspiciousactivity/fs_deniedactivity.md | 2 +- .../fs_highesthourlyactivity.md | 2 +- .../fs_hourlyshareactivity.md | 2 +- .../suspiciousactivity/fs_modifiedbinaries.md | 2 +- .../fs_peergroupactivity.md | 2 +- .../suspiciousactivity/fs_ransomware.md | 9 +- .../fs_sensitivedataactivity.md | 2 +- .../fs_stalefileactivity.md | 2 +- .../fs_usershareactivity.md | 2 +- .../suspiciousactivity/fs_weekendactivity.md | 2 +- .../activity/usagestatistics/fs_groupusage.md | 2 +- .../usagestatistics/fs_mostactiveservers.md | 2 +- .../usagestatistics/fs_mostactiveusers.md | 2 +- .../usagestatistics/fs_staleshares.md | 2 +- .../filesystem/adhocaudits/fs_shareaudit.md | 2 +- .../adhocaudits/fs_trusteepermissions.md | 4 +- .../filesystem/adhocaudits/overview.md | 2 +- .../cleanup/delete/fs_deletefiles.md | 8 +- .../cleanup/delete/fs_deletefiles_status.md | 2 +- .../cleanup/fs_cleanupassessment.md | 12 +- .../filesystem/cleanup/fs_cleanupprogress.md | 2 +- .../cleanup/notify/fs_notifyowners.md | 12 +- .../cleanup/notify/fs_notifyowners_status.md | 2 +- .../solutions/filesystem/cleanup/overview.md | 8 +- .../cleanup/quarantine/fs_quarantinedata.md | 6 +- .../quarantine/fs_quarantinedata_status.md | 2 +- .../quarantine/fs_restoreinheritance.md | 6 +- .../fs_restoreinheritance_status.md | 2 +- .../filesystem/collection/0-create_schema.md | 8 +- .../filesystem/collection/0-fs_nasuni.md | 6 +- .../collection/0-fsdfs_system_scans.md | 8 +- .../collection/1-fsac_system_scans.md | 2 +- .../collection/1-seek_system_scans.md | 4 +- .../collection/2-fsaa_bulk_import.md | 4 +- .../collection/2-fsac_bulk_import.md | 2 +- .../collection/2-seek_bulk_import.md | 2 +- .../collection/3-fsaa_exceptions.md | 22 +- .../collection/3-fsac_exceptions.md | 8 +- .../collection/fs_azuretenantscan.md | 8 +- .../filesystem/collection/overview.md | 143 ++++----- .../filesystem/content/fs_filetypes.md | 2 +- .../filesystem/content/fs_stalecontent.md | 2 +- .../content/sizing/fs_emptyresources.md | 2 +- .../content/sizing/fs_largestresources.md | 2 +- .../content/sizing/fs_smallestresources.md | 2 +- .../filesystem/content/tags/fs_aiplabels.md | 6 +- .../filesystem/content/tags/fs_filetags.md | 2 +- .../directpermissions/fs_domainuseracls.md | 6 +- .../directpermissions/fs_highriskacls.md | 2 +- .../fs_localusersandgroups.md | 2 +- .../fs_missingfullcontrol.md | 6 +- .../directpermissions/fs_nestedshares.md | 4 +- .../directpermissions/fs_sidhistory.md | 4 +- .../directpermissions/fs_unresolvedsids.md | 2 +- .../filesystem/directpermissions/overview.md | 2 +- .../filesystem/filesystemoverview.md | 6 +- .../filesystem/fs_brokeninheritance.md | 6 +- .../solutions/filesystem/fs_dlpresults.md | 4 +- .../solutions/filesystem/fs_openaccess.md | 4 +- .../solutions/filesystem/fs_probableowner.md | 6 +- .../filesystem/fs_securityassessment.md | 4 +- .../12.0/solutions/filesystem/overview.md | 46 +-- .../12.0/solutions/filesystem/recommended.md | 41 ++- .../fs_resourcebasedgroupaicimport.md | 31 +- .../fs_resourcebasedgroups.md | 80 +++--- .../resourcebasedgroups/fs_traversegroups.md | 64 ++--- .../resourcebasedgroups/overview.md | 26 +- .../12.0/solutions/nisinventory/nis_scan.md | 12 +- .../12.0/solutions/nisinventory/overview.md | 10 +- .../solutions/nisinventory/recommended.md | 14 +- .../accessanalyzer/12.0/solutions/overview.md | 6 +- .../activity/forensics/sp_deletions.md | 2 +- .../forensics/sp_permissionchanges.md | 4 +- .../forensics/sp_sensitivedataactivity.md | 2 +- .../solutions/sharepoint/activity/overview.md | 2 +- .../usagestatistics/sp_inactivesites.md | 2 +- .../usagestatistics/sp_mostactivesites.md | 4 +- .../usagestatistics/sp_mostactiveusers.md | 2 +- .../collection/1-spseek_systemscans.md | 8 +- .../collection/2-spaa_systemscans.md | 12 +- .../collection/3-spac_systemscans.md | 4 +- .../collection/4-spseek_bulkimport.md | 10 +- .../collection/5-spaa_bulkimport.md | 18 +- .../collection/6-spac_bulkimport.md | 18 +- .../collection/7-spaa_exceptions.md | 20 +- .../sharepoint/collection/overview.md | 48 ++-- .../solutions/sharepoint/content/overview.md | 11 +- .../sharepoint/content/sp_largestfiles.md | 2 +- .../sharepoint/content/sp_stalefiles.md | 10 +- .../sharepoint/directpermissions/overview.md | 8 +- .../directpermissions/sp_domainusers.md | 2 +- .../sp_emptydomaingroupperms.md | 4 +- .../sp_highriskpermissions.md | 4 +- .../sp_sitecollectionperms.md | 8 +- .../directpermissions/sp_staleusers.md | 6 +- .../directpermissions/sp_unresolvedsids.md | 2 +- .../effectiveaccessaudits/overview.md | 6 +- .../effectiveaccessaudits/sp_trusteeaccess.md | 12 +- .../effectiveaccessaudits/sp_trusteeaudit.md | 2 +- .../solutions/sharepoint/m365/overview.md | 2 +- .../sharepoint/m365/sp_externalusers.md | 8 +- .../solutions/sharepoint/m365/sp_onedrives.md | 4 +- .../sharepoint/m365/sp_sharedlinks.md | 10 +- .../sharepoint/m365/sp_staleteamsites.md | 8 +- .../solutions/sharepoint/m365/sp_teams.md | 2 +- .../m365/sp_teamsexternaluseractivity.md | 2 +- .../sharepoint/m365/sp_teamssensitivedata.md | 2 +- .../12.0/solutions/sharepoint/overview.md | 44 +-- .../12.0/solutions/sharepoint/recommended.md | 42 +-- .../sharepoint/sp_brokeninheritance.md | 6 +- .../solutions/sharepoint/sp_openaccess.md | 8 +- .../12.0/solutions/sharepoint/sp_overview.md | 8 +- .../solutions/sharepoint/sp_probableowner.md | 6 +- .../solutions/sharepoint/sp_sensitivedata.md | 2 +- .../12.0/solutions/unix/overview.md | 2 +- .../unix/privilegedaccess/overview.md | 2 +- .../privilegedaccess/sudoers/ux_sudoers.md | 2 +- .../unix/privilegedaccess/ux_criticalfiles.md | 4 +- .../12.0/solutions/unix/recommended.md | 12 +- .../unix/sharing/collection/overview.md | 2 +- .../sharing/collection/ux_nfsconfiguration.md | 2 +- .../collection/ux_sambaconfiguration.md | 2 +- .../12.0/solutions/unix/sharing/ux_nfs.md | 2 +- .../12.0/solutions/unix/sharing/ux_samba.md | 4 +- .../solutions/unix/usersgroups/overview.md | 2 +- .../unix/usersgroups/ux_duplicategroups.md | 2 +- .../unix/usersgroups/ux_emptygroups.md | 2 +- .../unix/usersgroups/ux_largegroups.md | 4 +- .../unix/usersgroups/ux_localgroups.md | 2 +- .../unix/usersgroups/ux_localusers.md | 2 +- .../unix/usersgroups/ux_passwordsettings.md | 2 +- .../unix/usersgroups/ux_usersandgroups.md | 4 +- .../applications/sg_installedapplications.md | 4 +- .../windows/applications/sg_runatboot.md | 2 +- .../windows/applications/sg_scheduledtasks.md | 2 +- .../windows/authentication/overview.md | 8 +- .../windows/authentication/sg_lsasettings.md | 14 +- .../sg_securitysupportproviders.md | 2 +- .../authentication/sg_wdigestsettings.md | 6 +- .../windows/openaccess/recommended.md | 6 +- .../windows/openaccess/sg_openfolders.md | 12 +- .../12.0/solutions/windows/overview.md | 10 +- .../localadministrators/overview.md | 2 +- .../localadministrators/sg_localadmins.md | 2 +- .../localadministrators/sg_microsoftlaps.md | 2 +- .../localadministrators/sg_sessions.md | 2 +- .../logonrights/collection/overview.md | 4 +- .../collection/sg_localmembership.md | 2 +- .../logonrights/collection/sg_localusers.md | 2 +- .../logonrights/overview.md | 4 +- .../logonrights/sg_accountprivileges.md | 2 +- .../logonrights/sg_localpolicies.md | 4 +- .../windows/privilegedaccounts/recommended.md | 6 +- .../privilegedaccounts/sg_serviceaccounts.md | 2 +- .../12.0/solutions/windows/recommended.md | 2 +- .../openportscan/overview.md | 6 +- .../openportscan/remoteopenport.md | 2 +- .../openportscan/retrievenetstat.md | 4 +- .../windows/securityutilities/overview.md | 8 +- .../windows/securityutilities/recommended.md | 6 +- .../sg_powershellcommands.md | 32 +-- .../windows/sg_securityassessment.md | 6 +- .../configurations/application-settings.md | 12 +- .../2601/configurations/logs.md | 14 +- .../2601/configurations/sensitive-data.md | 14 +- .../service-accounts/client-id-certificate.md | 8 +- .../service-accounts/client-id-secret.md | 4 +- .../service-accounts/overview.md | 2 +- .../service-accounts/ssh-username-key.md | 2 +- .../service-accounts/username-password.md | 4 +- .../source-groups/scan-executions.md | 8 +- .../source-groups/scanners/best-practices.md | 12 +- .../source-groups/scanners/deploy-scanner.md | 12 +- .../source-groups/scanners/manage-scanners.md | 6 +- .../source-groups/scanners/overview.md | 4 +- .../source-groups/scanners/requirements.md | 8 +- .../configurations/source-groups/scans.md | 22 +- .../source-groups/source-groups.md | 8 +- .../2601/configurations/users.md | 12 +- .../2601/connectors/activedirectory.md | 2 +- .../entra-id/app-registration-secret.md | 10 +- .../connectors/entra-id/entra-requirements.md | 4 +- .../2601/connectors/file-servers/celerra.md | 2 +- .../2601/connectors/file-servers/cifs.md | 2 +- .../connectors/file-servers/dell-unity.md | 2 +- .../file-servers/isilon-powerscale.md | 2 +- .../2601/connectors/file-servers/netapp.md | 4 +- .../2601/connectors/file-servers/vnx.md | 4 +- .../sharepoint-online/azure-permissions.md | 4 +- .../connectors/sharepoint-online/overview.md | 2 +- .../tenant-certificate-config.md | 2 +- .../2601/dashboards-reports/my-reports.md | 4 +- .../2601/dashboards-reports/reports.md | 4 +- .../active-directory/active-directory.md | 4 +- .../active-directory/reports.md | 2 +- .../active-directory/schema-reference.md | 12 +- .../active-directory/set-up-source-group.md | 4 +- .../2601/gettingstarted/entra-id/entra-id.md | 6 +- .../2601/gettingstarted/entra-id/reports.md | 6 +- .../entra-id/scanning-options.md | 4 +- .../entra-id/schema-reference.md | 10 +- .../entra-id/set-up-source-group.md | 2 +- .../file-servers/file-servers.md | 4 +- .../gettingstarted/file-servers/reports.md | 8 +- .../file-servers/scanning-options.md | 2 +- .../file-servers/schema-reference.md | 16 +- .../file-servers/set-up-source-group.md | 4 +- .../sharepoint-online/scanning-options.md | 4 +- .../sharepoint-online/schema-reference.md | 20 +- .../sharepoint-online/set-up-source-group.md | 4 +- .../sharepoint-online/sharepoint-online.md | 6 +- .../2601/install/identity-provider.md | 14 +- .../2601/install/quickinstall.md | 2 +- docs/accessanalyzer/2601/install/security.md | 12 +- .../2601/install/system/certificates.md | 4 +- .../2601/install/system/kubernetes.md | 8 +- .../2601/install/system/network.md | 2 +- .../2601/overview/keyconcepts.md | 34 +-- docs/accessanalyzer/2601/overview/overview.md | 16 +- 2647 files changed, 14252 insertions(+), 14557 deletions(-) diff --git a/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/computerdetails.md b/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/computerdetails.md index 14798ebe26..8e9d086842 100644 --- a/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/computerdetails.md +++ b/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/computerdetails.md @@ -12,14 +12,14 @@ Use the Computers Details page to select computer attributes to change. Highlight the attribute to edit: -- Insert field – Use the drop-down list to select a field (column) from the source table. Then click +- Insert field – Use the dropdown list to select a field (column) from the source table. Then click the blue arrow to insert the item into the Value box. The executed action replaces the AD Object property with the specified value from the source table. - Add Attribute – Adds a custom attribute to the Computer Details attribute list - Remove Attribute – Removes a selected attribute Computer Details attribute list - Edit Attribute – Click this icon to change the name of the selected custom attribute -- Import Attribute – Opens the Import Custom Attributes Import Wizard where one or more custom - attributes can be imported. See the +- Import Attribute – Opens the Import Custom Attributes Import Wizard, where you can import one or + more custom attributes. See the [Custom Attribute Import Wizard](#custom-attribute-import-wizard) topic for additional information. - Value – This field contains selections from the Insert field. If the Manager attribute is @@ -30,8 +30,7 @@ Highlight the attribute to edit: ## Custom Attribute Import Wizard -The Custom Attributes Import Wizard is used to import a list of custom attributes. Follow the steps -to use the Custom Attributes Import Wizard. +Use the Custom Attributes Import Wizard to import a list of custom attributes. **Step 1 –** On the Computer Details page of the Active Directory Action Module Wizard, click **Import**. The Custom Attribute Import Wizard opens. @@ -39,7 +38,7 @@ to use the Custom Attributes Import Wizard. ![Custom Attributes Import Wizard Credentials page](/images/accessanalyzer/11.6/admin/action/activedirectory/operations/credentials.webp) **Step 2 –** On the Credentials page, identify a domain either by entering one manually or selecting -one from the **Domain Name** drop-down menu which displays a list of domains trusted by the one in +one from the **Domain Name** dropdown menu which displays a list of domains trusted by the one in which the Enterprise Auditor Console server resides. Then set the credentials for reading the attributes list from the domain: @@ -52,11 +51,11 @@ attributes list from the domain: ![Custom Attributes Import Wizard Attributes page](/images/accessanalyzer/11.6/admin/action/activedirectory/operations/attributescomputer.webp) **Step 4 –** The wizard populates available attributes from the domain specified on the Attributes -page. Expand the desired object class and select the checkboxes for the custom attributes to be +page. Expand the object class you want and select the checkboxes for the custom attributes to be imported. Then click **Next**. ![Custom Attributes Import Wizard Completion page](/images/accessanalyzer/11.6/admin/action/activedirectory/operations/completionpage.webp) **Step 5 –** On the Completion page, click **Finish**. -The selected attributes have been added to the attribute list on the Computer Details page. +The wizard adds the selected attributes to the attribute list on the Computer Details page. diff --git a/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/creategroups.md b/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/creategroups.md index 968a2496e5..4b090d5590 100644 --- a/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/creategroups.md +++ b/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/creategroups.md @@ -12,12 +12,12 @@ Use the Create Groups page to configure the action to create groups on the selec Use the following options to configure the action: -- Insert field – Use the drop-down list to select a field (column) from the source table. Then, +- Insert field – Use the dropdown list to select a field (column) from the source table. Then, click the blue arrow to insert the item into the OU, Group name, or Group name (pre Windows 2000) boxes. - OU – The organizational unit that contains the group - - Create target OU location if it does not already exist – Select this checkbox to create the + - Create target OU location if it doesn't already exist – Select this checkbox to create the target OU - Group Name – The name of the group that being created. This field is required. @@ -27,10 +27,10 @@ Use the following options to configure the action: - Universal - Global - DomainLocal - - SqlField – Enter a value from the drop-down list + - SqlField – Enter a value from the dropdown list - Group type – The type of group being created. Select from the following: - Security - Distribution - - SqlField – Enter a value from the drop-down list + - SqlField – Enter a value from the dropdown list diff --git a/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/createusers.md b/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/createusers.md index a16d6e3572..788d9b0691 100644 --- a/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/createusers.md +++ b/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/createusers.md @@ -12,11 +12,11 @@ Use the Create Users page to create users on the selected target. Use the following options to configure the action: -- Insert field – Use the drop-down list to select a field (column) from the source table. Then, +- Insert field – Use the dropdown list to select a field (column) from the source table. Then, click the blue arrow to insert the item into the selected box. - OU – The organizational unit in which to create the user - - Create target OU location if it does not already exist - Select this checkbox to create the + - Create target OU location if it doesn't already exist - Select this checkbox to create the target OU. - First Name – The first name of the user being created @@ -31,6 +31,6 @@ Optionally, select from the following checkboxes: - User must change password at next logon – Require the user to change the password at the next logon -- User cannot change password +- User can't change password - Password never expires - Account is disabled diff --git a/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/disableenablecomputers.md b/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/disableenablecomputers.md index 5c327b7414..a594d4ea81 100644 --- a/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/disableenablecomputers.md +++ b/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/disableenablecomputers.md @@ -11,7 +11,7 @@ options on target computers. ![Active Directory Action Module Wizard Disable/Enable Computers page](/images/accessanalyzer/11.6/admin/action/activedirectory/operations/disableenablecomputers.webp) -Select the radio button for the desired option: +Select the radio button for the option you want: - Enable – Enables users' operation options - Disable – Disables users' operation options diff --git a/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/disableenableusers.md b/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/disableenableusers.md index 7df84ae685..b62217fc0c 100644 --- a/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/disableenableusers.md +++ b/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/disableenableusers.md @@ -10,7 +10,7 @@ Use the Disable/Enable Users page to enable or disable target users. ![Active Directory Action Module Wizard Disable/Enable Users page](/images/accessanalyzer/11.6/admin/action/activedirectory/operations/disableenableusers.webp) -Select the radio button for the desired option: +Select the radio button for the option you want: - Disable – Select this radio button to disable users' operation options - Enable – Select this radio button to enable users' operation options diff --git a/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/groupdetails.md b/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/groupdetails.md index 352dce77b3..22adcf16bd 100644 --- a/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/groupdetails.md +++ b/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/groupdetails.md @@ -18,13 +18,13 @@ The options at the bottom of the page vary based on the highlighted attribute. ::: -- Insert field – Use the drop-down list to select a field (column) from the source table. Then, +- Insert field – Use the dropdown list to select a field (column) from the source table. Then, click the blue arrow to insert the item into the Value box. - Add Attribute – Adds a custom attribute to the Computer Details attribute list - Remove Attribute – Removes a selected attribute from the action - Edit Attribute – Click this icon to change the name of the selected custom attribute -- Import Attribute – Opens the Import Custom Attributes Import Wizard where current attributes for - an object is viewed and can be imported for editing. See the +- Import Attribute – Opens the Import Custom Attributes Import Wizard, where you can view an + object's current attributes and import them for editing. See the [Custom Attribute Import Wizard](#custom-attribute-import-wizard) topic for additional information. - Value/Name – This field derives its name from selections made on the page. It can contain @@ -36,8 +36,7 @@ the action. ## Custom Attribute Import Wizard -The Custom Attributes Import Wizard is used to import a list of custom attributes. Follow the steps -to use the Custom Attributes Import Wizard. +Use the Custom Attributes Import Wizard to import a list of custom attributes. **Step 1 –** On the Group Details page of the Active Directory Action Module Wizard, click **Import**. The Custom Attribute Import Wizard opens. @@ -45,7 +44,7 @@ to use the Custom Attributes Import Wizard. ![Custom Attributes Import Wizard Credentials page](/images/accessanalyzer/11.6/admin/action/activedirectory/operations/credentials.webp) **Step 2 –** On the Credentials page, identify a domain either by entering one manually or selecting -one from the **Domain Name** drop-down menu which displays a list of domains trusted by the one in +one from the **Domain Name** dropdown menu which displays a list of domains trusted by the one in which the Enterprise Auditor Console server resides. Then set the credentials for reading the attributes list from the domain: @@ -58,11 +57,11 @@ attributes list from the domain: ![Custom Attributes Import Wizard Attributes page](/images/accessanalyzer/11.6/admin/action/activedirectory/operations/attributesgroup.webp) **Step 4 –** The wizard populates available attributes from the domain specified on the Attributes -page. Expand the desired object class and select the checkboxes for the custom attributes to be +page. Expand the object class you want and select the checkboxes for the custom attributes to be imported. Then click **Next**. ![Custom Attributes Import Wizard Completion page](/images/accessanalyzer/11.6/admin/action/activedirectory/operations/completionpage.webp) -**Step 5 –** On the Completion page, click **Finish**. On the Completion page, click **Finish**. +**Step 5 –** On the Completion page, click **Finish**. -The selected attributes have been added to the attribute list on the Group Details page. +The wizard adds the selected attributes to the attribute list on the Group Details page. diff --git a/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/groupmembership.md b/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/groupmembership.md index 2221b605e4..7fca0421cb 100644 --- a/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/groupmembership.md +++ b/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/groupmembership.md @@ -13,7 +13,7 @@ be used to specify if the object will be added or removed. Use the following options to configure the action: -- Insert field – Use the drop-down list to select a field (column) from the source table. Then, +- Insert field – Use the dropdown list to select a field (column) from the source table. Then, click the blue arrow to insert the item into the selected box. - Select one of the following: @@ -22,18 +22,18 @@ Use the following options to configure the action: - OU – The organizational unit that contains the group. This field is required. - - Create target OU location if it does not already exist – Select this checkbox to create the + - Create target OU location if it doesn't already exist – Select this checkbox to create the target OU. - Group (CN, not a pre-Windows 2000 name) – The group to create. This field is required. - - Create target Group if it does not already exist + - Create target Group if it doesn't already exist - Select one of the following: - Add members - Remove members - - Add/Remove members – Enables the ChangeType Column drop down list + - Add/Remove members – Enables the ChangeType Column dropdown list - ChangeType Column – The value to use from the source table to specify if the object is added or removed. The contents of the ChangeType column should be a 0 for Add or a 1 for Remove. diff --git a/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/moveobjects.md b/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/moveobjects.md index fb6dc814b4..7841f7e8bf 100644 --- a/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/moveobjects.md +++ b/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/moveobjects.md @@ -13,8 +13,8 @@ Use the Move Objects page to specify the OU in which to move objects. Use the following options to configure the action: - Insert Field – Contains available values from populated from the source table -- OU – Use the drop-down list to select a field (column) from the source table. Then, click the blue +- OU – Use the dropdown list to select a field (column) from the source table. Then, click the blue arrow to insert the item into the OU box. - - Create target OU location if it does not already exist – Select this checkbox to create the + - Create target OU location if it doesn't already exist – Select this checkbox to create the target OU diff --git a/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/operations.md b/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/operations.md index fa857d4cbd..ec41ad6a70 100644 --- a/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/operations.md +++ b/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/operations.md @@ -11,7 +11,7 @@ Active Directory objects. Some operations have wizard pages to specify the confi ![Active Directory Action Module Wizard Operations page](/images/accessanalyzer/11.6/admin/action/activedirectory/operations.webp) -The Operations drop-down menu contains the following operations: +The Operations dropdown menu contains the following operations: - [Clear/Set SID History ](/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/sidhistory.md) - [Computer Details](/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/computerdetails.md) @@ -28,7 +28,7 @@ The Operations drop-down menu contains the following operations: - [Unlock Users ](#unlock-users) - [Users Details ](/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/usersdetails.md) -Select an operation from the drop-down list and then click **Add**. The selection appears in the +Select an operation from the dropdown list and then click **Add**. The selection appears in the Selections pane as well as the navigation pane if there is an associated configuration page. If performing multiple operations, the action executes the operations in the order in which they appear here. To change the order, select an operation and use the **Down** and **Up** buttons. @@ -36,20 +36,20 @@ here. To change the order, select an operation and use the **Down** and **Up** b ## Delete Objects :::warning -Once deleted, objects from Active Directory cannot be restored. +Once deleted, objects from Active Directory can't be restored. ::: Select this operation to delete objects from Active Directory, such as users, groups, or computers. -The source table determines which objects are deleted from the Active Directory. Therefore, this -operation does not possess its own wizard window. +The source table determines which objects the action deletes from Active Directory. This operation +doesn't have its own wizard window. ## Groups Remove All Members -Select this operation to remove all members from groups located in the source table. There is not a -wizard window associated with this operation. No configuration is required. +Select this operation to remove all members from groups located in the source table. This operation +doesn't have an associated wizard window and requires no configuration. ## Unlock Users -Select this operation to unlock the account of the specified users in the source table. There is not -a wizard window associated with this operation. No configuration is required. +Select this operation to unlock the account of the specified users in the source table. This +operation doesn't have an associated wizard window and requires no configuration. diff --git a/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/setresetpassword.md b/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/setresetpassword.md index 0935607c8d..cc2205ca77 100644 --- a/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/setresetpassword.md +++ b/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/setresetpassword.md @@ -12,7 +12,7 @@ Use the Set/Reset Users Password page to set or reset user passwords with the sp Use the following options to configure the action: -- Insert field – Use the drop-down list to select a field (column) from the source table. Then, +- Insert field – Use the dropdown list to select a field (column) from the source table. Then, click the blue arrow to insert the item into the Password box. - Password – The field with the passwords to set or reset. This field is required. diff --git a/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/sidhistory.md b/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/sidhistory.md index e3be5ab370..d7c122b5b6 100644 --- a/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/sidhistory.md +++ b/docs/accessanalyzer/11.6/admin/action/activedirectory/operations/sidhistory.md @@ -7,7 +7,7 @@ sidebar_position: 10 # Clear/Set SID History Use the Clear/Set SID History page to overwrite or append to the SID history for targeted objects. -Please review the restrictions for this operation in the Notes box. +review the restrictions for this operation in the Notes box. The source table used for this operation must contain a column with the following information: @@ -20,15 +20,15 @@ Configure the action with the following options: - Overwrite – Overwrites the SID History - Append – Adds to the SID History - Clear – Clears the SID History -- Insert Field – This drop-down list is enabled when the Overwrite or Append radio buttons are - selected. Use the drop-down list to select a field (column) from the source table. Then, click the - blue arrow to insert the item into the SID History box. The SID history is overwritten with the - selected fields or appended to with the selected fields depending on the selected radio button. -- SID History – This box is enabled by selecting the Overwrite or Append radio buttons. The SID - history is overwritten or appended to with the inserted fields, depending on the selected radio - button. Populate the SID History box using either of the following methods: - - - Select one or more fields at the Insert Field drop-down menu +- Insert Field – Selecting the Overwrite or Append radio button enables this dropdown list. Use the + dropdown list to select a field (column) from the source table. Then, click the blue arrow to + insert the item into the SID History box. Depending on which radio button you select, the action + overwrites the SID history with the selected fields or appends the selected fields to it. +- SID History – Selecting the Overwrite or Append radio button enables this box. Depending on which + radio button you select, the action overwrites the SID history with the inserted fields or appends + the inserted fields to it. Populate the SID History box using either of the following methods: + + - Select one or more fields at the Insert Field dropdown menu - Click the **ellipsis (…)** to access the Select Users or Groups window to populate this field - Reference link – Accesses a Microsoft web page called Using DsAddSidHistory containing important diff --git a/docs/accessanalyzer/11.6/admin/action/activedirectory/options.md b/docs/accessanalyzer/11.6/admin/action/activedirectory/options.md index 2ff644ec16..431cfb729f 100644 --- a/docs/accessanalyzer/11.6/admin/action/activedirectory/options.md +++ b/docs/accessanalyzer/11.6/admin/action/activedirectory/options.md @@ -6,14 +6,13 @@ sidebar_position: 30 # Active Directory Action Options -The Options page provides the option to select to use the default domain or specific a domain to -use. +Use the Options page to select the default domain or specify a domain to use. ![Active Directory Action Module Wizard Options page](/images/accessanalyzer/11.6/admin/action/activedirectory/options.webp) Use the following options to configure the action: -- Insert field – Use the drop-down list to select a field (column) from the source table. Then, +- Insert field – Use the dropdown list to select a field (column) from the source table. Then, click the blue arrow to insert the item into the **Specify domain (controller) to use** box. - Use default domain (controller) – Use the default domain controller for the action - Specify domain (controller) to use – Click the ellipsis to open the Browse for Domain window and diff --git a/docs/accessanalyzer/11.6/admin/action/activedirectory/overview.md b/docs/accessanalyzer/11.6/admin/action/activedirectory/overview.md index e3ced73024..7ebef66c05 100644 --- a/docs/accessanalyzer/11.6/admin/action/activedirectory/overview.md +++ b/docs/accessanalyzer/11.6/admin/action/activedirectory/overview.md @@ -11,9 +11,8 @@ Use the Active Directory Action Module to make bulk changes to objects in Micros Auditor license. :::warning -Be careful when using this action module. Make sure that only the changes required are -applied and only to those target systems desired. Actions perform their functions on all rows in a -table. +Be careful when using this action module. Apply only the changes you need, and only to the target +systems you intend. Actions perform their functions on all rows in a table. ::: @@ -27,7 +26,7 @@ requirements for the type of data contained in the columns in the source table. Active Directory object, group, user, or computer, the source table columns must contain values that uniquely identify each Active Directory object referenced. Active Directory objects correspond to rows in a Enterprise Auditor source table. Active Directory object attributes correspond to columns. -Once the source table has been scoped, use the Target page to specify the field that identifies the +After you scope the source table, use the Target page to specify the field that identifies the target objects along with the field type to indicate the type of data contained in the field. The Operations page lists the operations that may be performed by the Active Directory Action @@ -39,7 +38,7 @@ Module. Each operation may have its own source table column requirements as foll | Computer Details | No specific columns required | | Disable/Enable Computers | No specific columns required | | Create Groups | No specific columns required | -| Create Users | Column containing the user logon name
**_RECOMMENDED:_** It is recommended that the source table has columns containing the following information:
  • First Name
  • Last name
  • Initials
  • Full name
  • Password
  • OU in which to create the user (This can also be created on the Create Users page)
| +| Create Users | Column containing the user logon name
**_RECOMMENDED:_** The source table should have columns containing the following information:
  • First Name
  • Last name
  • Initials
  • Full name
  • Password
  • OU in which to create the user (This can also be created on the Create Users page)
| | Delete Objects (Users, Groups, Computers, etc.) | No specific columns required | | Disable/Enable Users | No specific columns required | | Group Details | No specific columns required | @@ -67,6 +66,8 @@ introductory and caution information about the Active Directory Action Module. ![Active Directory Action Module Wizard Welcome page](/images/accessanalyzer/11.6/admin/action/activedirectory/welcome.webp) -The navigation pane contains links to the pages in the wizard. Note that the operations added on the -Operations page will affect the list of pages in the navigation pane. Several operations have -associated configuration pages. +The navigation pane contains links to the pages in the wizard. + +:::note +Operations added on the Operations page affect the list of pages in the navigation pane. Several operations have associated configuration pages. +::: diff --git a/docs/accessanalyzer/11.6/admin/action/activedirectory/summary.md b/docs/accessanalyzer/11.6/admin/action/activedirectory/summary.md index 16c584b531..be4ad14acb 100644 --- a/docs/accessanalyzer/11.6/admin/action/activedirectory/summary.md +++ b/docs/accessanalyzer/11.6/admin/action/activedirectory/summary.md @@ -10,6 +10,5 @@ The Summary page displays a summary of the configured settings for the action. ![Active Directory Action Module Wizard Summary page](/images/accessanalyzer/11.6/admin/action/activedirectory/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Active Directory Action Module Wizard to ensure that no accidental -clicks are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** instead to +close the Active Directory Action Module Wizard without saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/action/activedirectory/target.md b/docs/accessanalyzer/11.6/admin/action/activedirectory/target.md index bc90bf11c5..be0eaa73d3 100644 --- a/docs/accessanalyzer/11.6/admin/action/activedirectory/target.md +++ b/docs/accessanalyzer/11.6/admin/action/activedirectory/target.md @@ -9,7 +9,7 @@ sidebar_position: 10 Use the Target (Identification Criteria) page to select one or more fields (columns) in the Enterprise Auditor source table that uniquely identifies the target Active Directory objects upon which to perform the action. This process enables Enterprise Auditor to locate those objects within -Active Directory. Added fields are displayed in the textbox. +Active Directory. The textbox displays added fields. ![Active Directory Action Module Wizard Target page](/images/accessanalyzer/11.6/admin/action/activedirectory/target.webp) @@ -19,12 +19,12 @@ Use the following options to configure the action: - Delete – Removes the highlighted operation from the Selection pane - Field – The name of the column in the Enterprise Auditor source table. Select the field that uniquely identifies the target AD objects (represented by rows in the Enterprise Auditor table). - The drop-down list displays the fields from the source data table specified on the Action - Properties page. The list excludes any default fields such as HOSTSTATUS, on which actions cannot - be performed. + The dropdown list displays the fields from the source data table specified on the Action + Properties page. The list excludes any default fields such as HOSTSTATUS, on which you can't + perform actions. - Field Type – The type of data contained in the specified field. Enterprise Auditor must know the - data type of the field selected above. Otherwise, errors may appear upon execution of the action - and report results may be incomplete. The drop-down list contains the following field types: + data type of the selected field. Otherwise, errors may appear upon execution of the action + and report results may be incomplete. The dropdown list contains the following field types: - Distinguished Name or DN - GUID @@ -34,7 +34,6 @@ Use the following options to configure the action: - Employee (employeeID) :::note -While one field is usually sufficient to identify AD objects, if specifying multiple -fields, each field type can only be used once. - +While one field is usually sufficient to identify AD objects, if you specify multiple fields, you +can use each field type only once. ::: diff --git a/docs/accessanalyzer/11.6/admin/action/filesystem/action.md b/docs/accessanalyzer/11.6/admin/action/filesystem/action.md index 9f8b3c0f0c..2d21457d7a 100644 --- a/docs/accessanalyzer/11.6/admin/action/filesystem/action.md +++ b/docs/accessanalyzer/11.6/admin/action/filesystem/action.md @@ -6,19 +6,19 @@ sidebar_position: 10 # File System Action: Action -On the Action page, select the type of action to be configured, define a new action, and additional +On the Action page, select the type of action to configure, define a new action, and additional capabilities. ![File System Action Module Wizard Action page](/images/accessanalyzer/11.6/admin/action/filesystem/action.webp) The following options are available: -- Define a new action – Enables the Operation page where operations are selected on which the action - is based -- Rollback a previously executed action – Enables the Prior Actions page where lists of previously - executed actions and rollback actions can be selected. Not all operations support rollback. Enable - the Support Rollback option prior to execution for the action in order to perform a rollback. +- Define a new action – Enables the Operation page, where you select the operations the action is + based on +- Rollback a previously executed action – Enables the Prior Actions page, where you can select lists + of previously executed actions and rollback actions. Not all operations support rollback. Enable + the Support Rollback option before execution for the action to perform a rollback. - Remove the applet service from a host – If an executed action installs an applet service on a host - from a Enterprise Auditor Console, it remains installed after the action is completed for other - Enterprise Auditor consoles to perform actions using the same applet service. This setting removes + from a Enterprise Auditor Console, it remains installed after the action completes so other + Enterprise Auditor consoles can perform actions using the same applet service. This setting removes the action’s applet service from that host. diff --git a/docs/accessanalyzer/11.6/admin/action/filesystem/appletsettings.md b/docs/accessanalyzer/11.6/admin/action/filesystem/appletsettings.md index d29f67bc20..046f63e835 100644 --- a/docs/accessanalyzer/11.6/admin/action/filesystem/appletsettings.md +++ b/docs/accessanalyzer/11.6/admin/action/filesystem/appletsettings.md @@ -16,21 +16,21 @@ Specify how the operations will be executed: - Local Enterprise Auditor server - Specific remote server: - - Fields – Use the drop-down list to select a field (column) from the source table, then click + - Fields – Use the dropdown list to select a field (column) from the source table, then click the blue arrow to insert the item into the **Remote server** field - - Environment Variables – Select an item from the drop-down list, then click the blue arrow to + - Environment Variables – Select an item from the dropdown list, then click the blue arrow to insert the item into the **Remote Server** field - Remote Server – Enter the path to the server - Click the **ellipsis (…)** to browse for server - Click the **tick** icon to show a preview of the path - Click the **Help** icon for additional information -- Preview – Shows what the compound path specified will be resolved in to. The text here is used to - initialize the path specification selection dialog. +- Preview – Shows what the specified compound path resolves to. The text here initializes the path + specification selection dialog. - Specific remote servers – Click the **ellipsis (…)** to browse for servers - Click **Add** to add the server - Click **Remove** to remove the server -- Fall back to the local Enterprise Auditor server if an applet cannot start – Check to enable this +- Fall back to the local Enterprise Auditor server if an applet can't start – Check to enable this option diff --git a/docs/accessanalyzer/11.6/admin/action/filesystem/destination.md b/docs/accessanalyzer/11.6/admin/action/filesystem/destination.md index 5d89170892..832f75a13b 100644 --- a/docs/accessanalyzer/11.6/admin/action/filesystem/destination.md +++ b/docs/accessanalyzer/11.6/admin/action/filesystem/destination.md @@ -12,18 +12,18 @@ The Destination page is available only if the following operations are selected: - Move - Rename -Define the destination location of the files that will be copied, moved, or renamed by building the -destination path using the Fields and Environment Variables options as needed. +Define the destination location for the files to copy, move, or rename by building the destination +path using the Fields and Environment Variables options as needed. ![File System Action Module Wizard Destination page](/images/accessanalyzer/11.6/admin/action/filesystem/destination.webp) -Use the fields provided to select destination items and hosts from the drop-down lists and populate +Use the fields provided to select destination items and hosts from the dropdown lists and populate the Destination field, or edit the field manually. The Preview field updates based on the contents of the Destination field. -- Fields – Use the drop-down list to select a field (column) from the source table, then click the +- Fields – Use the dropdown list to select a field (column) from the source table, then click the blue arrow to insert the item into the **Destination** field -- Environment Variables – Select an item from the drop-down list, then click the blue arrow to +- Environment Variables – Select an item from the dropdown list, then click the blue arrow to insert the item into the **Destination** field - Target Items – Enter the path to the target file or folder @@ -31,11 +31,11 @@ of the Destination field. - Click the **tick** icon to show a preview of the specified path - Click the **Help** icon for additional information -- Host – Select the field that identifies the systems or manually type the host destination +- Host – Select the field that identifies the systems or manually enter the host destination - Use path type – Choose from the following options: - Local – Uses the local path - UNC – Uses the UNC path -- Preview – Shows what the compound path specified will be resolved in to. The text here is used to - initialize the file specification selection dialog. +- Preview – Shows what the specified compound path resolves to. The text here initializes the file + specification selection dialog. diff --git a/docs/accessanalyzer/11.6/admin/action/filesystem/environment.md b/docs/accessanalyzer/11.6/admin/action/filesystem/environment.md index 13a5e3f11e..90bf0d3d04 100644 --- a/docs/accessanalyzer/11.6/admin/action/filesystem/environment.md +++ b/docs/accessanalyzer/11.6/admin/action/filesystem/environment.md @@ -7,11 +7,11 @@ sidebar_position: 40 # File System Action: Environment The Environment (Environment Variables) page is available only if the selected operation requires -the selection of a sample host. +selecting a sample host. -Use this page to select and connect to a sample host, via which a set of remote environment -variables for use in scoping the action are loaded. Then, on the Target page, use the environment -variables to build dynamic file path locations for the selected operation. +Use this page to select and connect to a sample host, which loads a set of remote environment +variables that you use to scope the action. Then, on the Target page, use the environment variables +to build dynamic file path locations for the selected operation. :::note The environment variables from the local system load by default. diff --git a/docs/accessanalyzer/11.6/admin/action/filesystem/operation.md b/docs/accessanalyzer/11.6/admin/action/filesystem/operation.md index 1d12d268f7..c3399755e6 100644 --- a/docs/accessanalyzer/11.6/admin/action/filesystem/operation.md +++ b/docs/accessanalyzer/11.6/admin/action/filesystem/operation.md @@ -7,11 +7,11 @@ sidebar_position: 20 # File System Action: Operation The Operation page is available when **Define a new action** is selected on the Action page. On the -Operation page, define the action by selecting an operation from the drop-down list. +Operation page, define the action by selecting an operation from the dropdown list. ![File System Action Module Wizard Operation page](/images/accessanalyzer/11.6/admin/action/filesystem/operation.webp) -At the Available Operations drop-down selection list, choose the operation for the action to +At the Available Operations dropdown selection list, choose the operation for the action to perform. The selection determines which pages are available in the wizard. The following operations are available: diff --git a/docs/accessanalyzer/11.6/admin/action/filesystem/options.md b/docs/accessanalyzer/11.6/admin/action/filesystem/options.md index 69b5c57a7b..820fc017cc 100644 --- a/docs/accessanalyzer/11.6/admin/action/filesystem/options.md +++ b/docs/accessanalyzer/11.6/admin/action/filesystem/options.md @@ -14,50 +14,48 @@ available. Select from the following additional operations: -- Delete locked files on reboot – Files that are locked can be queued to be deleted at the next - system start up -- Overwrite existing files – Files in the destination location are overwritten. This action cannot - be undone. -- Terminate associated process – Files that are locked cannot be actively moved, renamed or deleted - without stopping the associated process. If selected, this may cause an interruption to any users - of that target system and service. -- Create shortcuts to the moved files in the source directory – A shortcut will be created in the - source directory that points to the new location of a moved file +- Delete locked files on reboot – Queues locked files for deletion at the next system startup +- Overwrite existing files – Overwrites files in the destination location. This action can't be + undone. +- Terminate associated process – You can't move, rename, or delete locked files without stopping the + associated process. Selecting this option may interrupt any users of that target system and + service. +- Create shortcuts to the moved files in the source directory – Creates a shortcut in the source + directory that points to the new location of a moved file - Preserve file access – Copy the file ACL from the source directory to the destination to preserve file access. Child objects, with inherited permissions or broken inheritance, targeted by copy or - move actions retain their permissions. Parent folders with inherited permissions are changed to - explicit. -- Enable SACL modification – Request system security access when opening files in order to make SACL + move actions retain their permissions. Parent folders with inherited permissions become explicit. +- Enable SACL modification – Request system security access when opening files to make SACL changes - Retry failed rows – Enter the following information: - Number of times to retry - - Do not retry error codes – Rows of data with error codes listed within this textbox are - excluded from the action performed. Common errors are included for certain actions, and may be - customized to add or remove error codes. See the Microsoft + - Don't retry error codes – Excludes rows of data with error codes listed in this textbox from + the action performed. The action already includes common error codes for certain actions; you + can customize the list to add or remove error codes. See the Microsoft [System Error Codes](https://docs.microsoft.com/en-us/windows/desktop/Debug/system-error-codes) article for additional information. - Delay between retries - Enable batching – (For big data sets) Enabling batching breaks the data set into batches so the - action does not attempt to execute all lines at once. Actions performed on tables with a large - number of input rows may fail due to network failure, and it is difficult to determine the actions - that were executed before the failure. + action doesn't attempt to execute all lines at once. Actions performed on tables with a large + number of input rows may fail due to network failure, making it hard to determine which actions + ran before the failure. - Batch size – Specify the batch size. **Start Process** -Select the desired start process. +Select the start process you want. :::warning -Due to system security limitations, some applications and programs cannot be restarted +Due to system security limitations, some applications and programs can't be restarted or run remotely using this option. Additionally, starting interactive processes (such as Word, Excel, and so on) will load them into memory, but may not make them available for interaction by the end user. ::: -Use the fields provided to select target items and hosts from the drop-down lists and populate the +Use the fields provided to select target items and hosts from the dropdown lists and populate the Set working directory field, or edit the field manually. The Preview field updates based on the contents of the Set working directory field. diff --git a/docs/accessanalyzer/11.6/admin/action/filesystem/overview.md b/docs/accessanalyzer/11.6/admin/action/filesystem/overview.md index 15cf335f21..2de10f6efe 100644 --- a/docs/accessanalyzer/11.6/admin/action/filesystem/overview.md +++ b/docs/accessanalyzer/11.6/admin/action/filesystem/overview.md @@ -13,9 +13,8 @@ moving, and renaming file system contents. It is available with a special Enterp license. :::warning -Be careful when using this Action Module. Make sure that only the changes required are -applied and only to those target systems desired. Actions perform their functions on all rows in a -table. +Be careful when using this Action Module. Apply only the changes you need, and only to the target +systems you intend. Actions perform their functions on all rows in a table. ::: @@ -61,12 +60,12 @@ is present. Otherwise, applets are deployed to `C:\Program Files (x86)\STEALTHbi Individual action modules, including File System Action Module, may have their own column requirements. To take action on a file system resource, the source table must contain a column with values to uniquely identify it. File System resources correspond to rows in a Enterprise Auditor -table. File System attributes correspond to columns. Once the source table has been scoped, use the +table. File System attributes correspond to columns. After you scope the source table, use the Target page to specify the field that identifies the target attribute along with any environmental variables. -These columns are required to use the File System Action Module. Otherwise, errors may occur upon -execution of the action and with analysis and reports downstream. +The File System Action Module requires these columns. Otherwise, errors may occur upon execution of +the action and with analysis and reports downstream. | Required Columns | Description | | ---------------- | ---------------------------------------------------------------------------------------------------------------------------- | @@ -75,11 +74,11 @@ execution of the action and with analysis and reports downstream. :::tip Remember, the individual File System actions may have their own column requirements in addition to -the above. These columns are made available through the File System Action Module wizard. +these. The File System Action Module wizard makes these columns available. ::: -The Operations page lists the operations that may be performed by the File System Action Module. +The Operations page lists the operations that the File System Action Module can perform. Each operation has its own source table column requirements as follows: | Operation | Column requirements | diff --git a/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/addtags.md b/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/addtags.md index b9aca251d5..577e54059b 100644 --- a/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/addtags.md +++ b/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/addtags.md @@ -10,7 +10,7 @@ Use the Parameters page to specify the file tags the action adds. ![File System Action Module Wizard Add Tags Parameters page](/images/accessanalyzer/11.6/admin/action/filesystem/parameters/addtags.webp) -Use the fields provided to select tags from the drop-down lists and populate the Tag field, or edit +Use the fields provided to select tags from the dropdown lists and populate the Tag field, or edit the field manually. The Preview field updates based on the contents of the Tag field. - Add Mode: @@ -19,16 +19,15 @@ the field manually. The Preview field updates based on the contents of the Tag f - Overwrite existing tags - Removes all existing tags before adding newly configured tags :::note -If choosing the option to overwrite tags, the action module will clear out both normal -tags and Boldon James tags and then proceed to apply the tags configured for overwrite. If choosing -the option to remove all tags, the action module will clear out both normal tags and Boldon James -tags. +If you choose the option to overwrite tags, the action module clears out both normal tags and +Boldon James tags, then applies the tags configured for overwrite. If you choose the option to +remove all tags, the action module clears out both normal tags and Boldon James tags. ::: -- Fields – Use the drop-down list to select a field (column) from the source table, then click the +- Fields – Use the dropdown list to select a field (column) from the source table, then click the blue arrow to insert the item into the **Tag** field -- Environment Variables – Select an item from the drop-down list, then click the blue arrow to +- Environment Variables – Select an item from the dropdown list, then click the blue arrow to insert the item into the **Tag** field - Preview – Shows what the compound path specified will be resolved in to - Click **Add** to add the tag field to the list @@ -36,15 +35,14 @@ tags. ![Boldon James Column on Add Tags Parameters page](/images/accessanalyzer/11.6/admin/action/filesystem/parameters/addremovetagsboldonjames.webp) -- Type - Select which type of tag to add. The two types of tags that can be added are: +- Type - Select which type of tag to add. The two types of tags you can add are: - Regular - Configure new tag as a regular tag - Boldon James - Configure new tag as a Boldon James tag :::note The Boldon James column indicates whether a file tag is a regular tag or a Boldon - James tag. Regular tags will be identified with **0**. Boldon James tags will be identified - with **1**. + James tag. The column marks regular tags with **0** and Boldon James tags with **1**. ::: diff --git a/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/changeowner.md b/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/changeowner.md index fa06f14d31..26642e31d0 100644 --- a/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/changeowner.md +++ b/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/changeowner.md @@ -12,7 +12,7 @@ Use the Change Owner Parameters page to select a trustee to be the new owner. Use the options to enter the trustees: -- Insert field – Use the drop-down list to select a field (column) from the source table, then click +- Insert field – Use the dropdown list to select a field (column) from the source table, then click the blue arrow - Alternatively click **Select** to select a user or group object - Replace owner on all child objects – Check to enable diff --git a/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/changepermissioninheritance.md b/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/changepermissioninheritance.md index 49f7125b62..8e3daa083a 100644 --- a/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/changepermissioninheritance.md +++ b/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/changepermissioninheritance.md @@ -11,4 +11,4 @@ permissions. ![File System Action Module Wizard Change Permissions Inheritance Parameters page](/images/accessanalyzer/11.6/admin/action/filesystem/parameters/changepermissionsinheritance.webp) -Select the desired options for adding or removing inheritance. +Select the options you want for adding or removing inheritance. diff --git a/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/changepermissionsauditing.md b/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/changepermissionsauditing.md index 11f629366c..6b1f65d565 100644 --- a/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/changepermissionsauditing.md +++ b/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/changepermissionsauditing.md @@ -13,7 +13,7 @@ settings the action changes. Use the following options to enter the Permissions: -- Insert field – Use the drop-down list to select a field (column) from the source table, then click +- Insert field – Use the dropdown list to select a field (column) from the source table, then click the blue arrow - Group or user names: diff --git a/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/changesharepermissions.md b/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/changesharepermissions.md index 5df320491a..bad1482740 100644 --- a/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/changesharepermissions.md +++ b/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/changesharepermissions.md @@ -11,4 +11,4 @@ users are to be changed. ![File System Action Module Wizard Change Share Permissions Parameters page](/images/accessanalyzer/11.6/admin/action/filesystem/parameters/changesharepermissions.webp) -Select the desired options for changing the permissions control of the selected group or users. +Select the options you want for changing the permissions control of the selected group or users. diff --git a/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/parameters.md b/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/parameters.md index 5ad81ec4bd..95c68d7d42 100644 --- a/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/parameters.md +++ b/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/parameters.md @@ -6,9 +6,9 @@ sidebar_position: 60 # File System Action: Parameters -The Parameters page is available for some of the selections on the Operation page. The list of -operations below provides access to the operation-specific versions of the Parameters page for this -wizard. Click on an operation to view its associated Parameters page. +The Parameters page is available for some of the selections on the Operation page. The following +list of operations provides access to the operation-specific versions of the Parameters page for +this wizard. Click an operation to view its associated Parameters page. - [Change Attributes](/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/changeattributes.md) - [Change Permissions and Auditing](/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/changepermissionsauditing.md) @@ -23,4 +23,4 @@ wizard. Click on an operation to view its associated Parameters page. ![File System Action Module Wizard Change File Attributes Parameters page](/images/accessanalyzer/11.6/admin/action/filesystem/changeattributes.webp) The Navigation pane will list this as the Parameters page, but the title for each version indicates -the type of parameter to be configured. +the type of parameter to configure. diff --git a/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/removefilepermissions.md b/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/removefilepermissions.md index b99a37adf5..fbbd2156b1 100644 --- a/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/removefilepermissions.md +++ b/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/removefilepermissions.md @@ -13,7 +13,7 @@ removes. Use the options to enter the Permissions: -- Insert field – Use the drop-down list to select a field (column) from the source table, then click +- Insert field – Use the dropdown list to select a field (column) from the source table, then click the blue arrow - Group or user names: - Click **Add** to select a user or group object diff --git a/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/removesharepermissions.md b/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/removesharepermissions.md index 5d95bcbb10..497fd51ee5 100644 --- a/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/removesharepermissions.md +++ b/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/removesharepermissions.md @@ -13,7 +13,7 @@ removes. Use the options to enter the Permissions: -- Insert field – Use the drop-down list to select a field (column) from the source table, then click +- Insert field – Use the dropdown list to select a field (column) from the source table, then click the blue arrow - Group or user names: diff --git a/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/removetags.md b/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/removetags.md index c3cab4de19..fee0761797 100644 --- a/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/removetags.md +++ b/docs/accessanalyzer/11.6/admin/action/filesystem/parameters/removetags.md @@ -10,7 +10,7 @@ Use the Parameter page to specify the file tags the action removes. ![File System Action Module Wizard Remove Tags Parameters page](/images/accessanalyzer/11.6/admin/action/filesystem/parameters/removetags.webp) -Use the fields provided to select tags from the drop-down lists and populate the Tag field, or edit +Use the fields provided to select tags from the dropdown lists and populate the Tag field, or edit the field manually. The Preview field updates based on the contents of the Tag field. - Remove Mode: @@ -19,32 +19,30 @@ the field manually. The Preview field updates based on the contents of the Tag f - Remove all tags - Remove all existing tags :::note -If choosing the option to overwrite tags, the action module will clear out both normal -tags and Boldon James tags and then proceed to apply the tags configured for overwrite. If choosing -the option to remove all tags, the action module will clear out both normal tags and Boldon James -tags. +If you choose the option to overwrite tags, the action module clears out both normal tags and +Boldon James tags, then applies the tags configured for overwrite. If you choose the option to +remove all tags, the action module clears out both normal tags and Boldon James tags. ::: -- Fields – Use the drop-down list to select a field (column) from the source table, then click the +- Fields – Use the dropdown list to select a field (column) from the source table, then click the blue arrow to insert the item into the **Tag** field -- Environment Variables – Select an item from the drop-down list, then click the blue arrow to +- Environment Variables – Select an item from the dropdown list, then click the blue arrow to insert the item into the **Tag** field -- Preview – Shows what the compound path specified will be resolved in to +- Preview – Shows what the specified compound path resolves to - Click **Add** to add the tag field to the list for removal - Click **Remove** to remove the tag field from the list for removal ![Boldon James Column on Remove Tags Parameters page](/images/accessanalyzer/11.6/admin/action/filesystem/parameters/addremovetagsboldonjames.webp) -- Type - Select which type of tag to remove. The two types of tags that can be removed are: +- Type - Select which type of tag to remove. The two types of tags you can remove are: - Regular - Specify a regular tag for removal - Boldon James - Specify a Boldon James tag for removal :::note The Boldon James column indicates whether a file tag is a regular tag or a Boldon - James tag. Regular tags will be identified with **0**. Boldon James tags will be identified - with **1**. + James tag. The column marks regular tags with **0** and Boldon James tags with **1**. ::: diff --git a/docs/accessanalyzer/11.6/admin/action/filesystem/rollback.md b/docs/accessanalyzer/11.6/admin/action/filesystem/rollback.md index bce3530933..dda58f37df 100644 --- a/docs/accessanalyzer/11.6/admin/action/filesystem/rollback.md +++ b/docs/accessanalyzer/11.6/admin/action/filesystem/rollback.md @@ -6,7 +6,7 @@ sidebar_position: 80 # File System Action: Rollback -Use the Rollback page to apply rollback support to the action. This option provides the ability to +Use the Rollback page to apply rollback support to the action. This option lets you undo failed actions and reapply the original action settings when the action continues from where it left off. diff --git a/docs/accessanalyzer/11.6/admin/action/filesystem/summary.md b/docs/accessanalyzer/11.6/admin/action/filesystem/summary.md index 090ff29663..045e3cc310 100644 --- a/docs/accessanalyzer/11.6/admin/action/filesystem/summary.md +++ b/docs/accessanalyzer/11.6/admin/action/filesystem/summary.md @@ -10,6 +10,5 @@ The Summary page displays a summary of the configured action. ![File System Action Module Wizard Summary page](/images/accessanalyzer/11.6/admin/action/filesystem/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the File System Action Module Wizard to ensure that no accidental clicks -are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** instead to +close the File System Action Module Wizard without saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/action/filesystem/target.md b/docs/accessanalyzer/11.6/admin/action/filesystem/target.md index e9e1b0ccee..c89890a574 100644 --- a/docs/accessanalyzer/11.6/admin/action/filesystem/target.md +++ b/docs/accessanalyzer/11.6/admin/action/filesystem/target.md @@ -13,13 +13,13 @@ field. ![File System Action Module Wizard Target page](/images/accessanalyzer/11.6/admin/action/filesystem/target.webp) -Use the fields provided to select target items and hosts from the drop-down lists and populate the +Use the fields provided to select target items and hosts from the dropdown lists and populate the Target items field, or edit the field manually. The Preview field updates based on the contents of the Target items field. -- Fields – Use the drop-down list to select a field (column) from the source table, then click the +- Fields – Use the dropdown list to select a field (column) from the source table, then click the blue arrow to insert the item into the **Target items** field -- Environment Variables – Select an item from the drop-down list, then click the blue arrow to +- Environment Variables – Select an item from the dropdown list, then click the blue arrow to insert the item into the Target items field - Target items – Enter the path to the target file or folder @@ -27,12 +27,12 @@ the Target items field. - Click the **tick** icon to show a preview of the specified path - Click the **Help** icon for additional information -- Host – Select the field that identifies the systems or manually type the host to take action +- Host – Select the field that identifies the systems or manually enter the host to take action against - Use path type – Choose from the following options: - Local – Uses the local path - UNC – Uses the UNC path -- Preview – Shows what the compound path specified will be resolved in to. The text here is used to - initialize the file specification selection dialog. +- Preview – Shows what the specified compound path resolves to. The text here initializes the file + specification selection dialog. diff --git a/docs/accessanalyzer/11.6/admin/action/libraries.md b/docs/accessanalyzer/11.6/admin/action/libraries.md index a844c4ae40..2d729fdb96 100644 --- a/docs/accessanalyzer/11.6/admin/action/libraries.md +++ b/docs/accessanalyzer/11.6/admin/action/libraries.md @@ -6,10 +6,10 @@ sidebar_position: 10 # Action Libraries -When creating a new action on a job, you have the ability to load action tasks that have been -preconfigured with table input, script body, and parameters. This helps you: +When creating a new action on a job, you can load action tasks preconfigured with table input, +script body, and parameters. This helps you: -- Perform operations that are not available in one of the out of the box action modules +- Perform operations that aren't available in the built-in action modules - Build custom action workflows to satisfy common use cases - Build custom remediation workflows, such as: @@ -22,15 +22,15 @@ window with the available Action Libraries and operations: ![Libraries window](/images/accessanalyzer/11.6/admin/action/libraries.webp) -When a specific operation within a library is chosen, the action is added in the disabled state to -the job. The Action Properties page opens, which has a description, action module, and source table -with relevant filters applied. +When you choose a specific operation within a library, the wizard adds the action to the job in the +disabled state. The Action Properties page opens, which has a description, action module, and +source table with relevant filters applied. When you click the **Configure Action** link, the action module's wizard opens. ![PowerShell Action Module Wizard](/images/accessanalyzer/11.6/admin/action/powershellmodulewizard.webp) -The following Action Libraries and Templates leverage the PowerShell Action module for running +The following Action Libraries and Templates use the PowerShell Action module to run actions within the specific environment: - Active Directory @@ -39,14 +39,13 @@ actions within the specific environment: - SharePoint Online - Windows -Prerequisite information for each of the PowerShell scripts is included as part of the script -comments. Typically, a script requires necessary cmdlets available and installed, as well as -parameter inputs configured. +The script comments include prerequisite information for each PowerShell script. Typically, a +script requires necessary cmdlets available and installed, as well as parameter inputs configured. ## Create a Custom Action Library You can also create and maintain custom libraries of action tasks for easy reference and use. Once -you configure an action task as desired, follow the steps to add it to an Action Library. +you configure an action task as desired, add it to an Action Library: **Step 1 –** From within the Action Selections view where the custom action tasks exists, right-click and copy the task. diff --git a/docs/accessanalyzer/11.6/admin/action/mailbox/affectedmailboxes.md b/docs/accessanalyzer/11.6/admin/action/mailbox/affectedmailboxes.md index 64ddd3d39d..ba4612bf91 100644 --- a/docs/accessanalyzer/11.6/admin/action/mailbox/affectedmailboxes.md +++ b/docs/accessanalyzer/11.6/admin/action/mailbox/affectedmailboxes.md @@ -20,7 +20,7 @@ Select mailboxes to process using the following options: - Users found in the following column – Select this option to identify users via a data table column - - Use the drop-down menu to select a data table column containing either the Mailbox display + - Use the dropdown menu to select a data table column containing either the Mailbox display name or email address - Select a data type for the selected field using the following options: diff --git a/docs/accessanalyzer/11.6/admin/action/mailbox/delegaterights.md b/docs/accessanalyzer/11.6/admin/action/mailbox/delegaterights.md index 978fba73ec..3bdeb0e957 100644 --- a/docs/accessanalyzer/11.6/admin/action/mailbox/delegaterights.md +++ b/docs/accessanalyzer/11.6/admin/action/mailbox/delegaterights.md @@ -14,7 +14,7 @@ operation. Set delegate rights using the following options: -- The following delegate rights can be chosen to access each mailbox folder: +- Choose one of the following delegate rights to access each mailbox folder: - None - Reviewer @@ -26,13 +26,13 @@ Set delegate rights using the following options: - Publishing Editor - Owner -- Select a right from the drop-down menu of any desired mailbox folder, including: +- Select a right from the dropdown menu of any desired mailbox folder, including: - Calendar :::note - If Editor or a higher rights level is selected, the **Delegate receives copies of - meeting-related messages sent to me** option is enabled for selection. + If you select Editor or a higher rights level, the wizard enables the **Delegate + receives copies of meeting-related messages sent to me** option. ::: diff --git a/docs/accessanalyzer/11.6/admin/action/mailbox/folderconditions.md b/docs/accessanalyzer/11.6/admin/action/mailbox/folderconditions.md index 7cb63cc1b7..c11676f591 100644 --- a/docs/accessanalyzer/11.6/admin/action/mailbox/folderconditions.md +++ b/docs/accessanalyzer/11.6/admin/action/mailbox/folderconditions.md @@ -7,7 +7,7 @@ sidebar_position: 60 # Mailbox: Folder Conditions Use the Folder Conditions page to customize folder search filter conditions. It is a wizard page for -the **No, the query results do not contain a mailbox identification** column option on the Folder +the **No, the query results don't contain a mailbox identification** column option on the Folder Identification page. ![New Mailbox Action Wizard Folder Conditions page](/images/accessanalyzer/11.6/admin/action/mailbox/folderconditions.webp) @@ -19,7 +19,7 @@ Customize folder search conditions using the following options: - With specific folder type - With search terms in the folder name - - With specific folder(s) to include/exclude + - With specific folders to include/exclude - Edit conditions – Any selected conditions populate here. To modify filter conditions, click the underlined portion of the condition, which opens a corresponding window. @@ -27,8 +27,8 @@ Customize folder search conditions using the following options: ## Folder Type Window Use the Folder Type window to select which folder types to run the action against. The Folder Type -window opens if **specific** in **with specific folder type** is selected in the Edit Conditions -box. . +window opens if you select **specific** in **with specific folder type** in the Edit Conditions +box. ![Folder Type Window](/images/accessanalyzer/11.6/admin/action/mailbox/foldertypewindow.webp) @@ -46,13 +46,13 @@ Select the checkbox next to any desired folder type to include it in the search ## Search Terms Window Use the Search Terms window to select terms contained in folder names to run the action against.The -Search Terms window opens if **search terms** is selected in the Edit Conditions box. +Search Terms window opens if you select **search terms** in the Edit Conditions box. ![Search Terms Window](/images/accessanalyzer/11.6/admin/action/mailbox/searchtermswindow.webp) Edit the search terms using the following options: -- To add a term to the search, enter the desired term into the upper text box and click **Add** +- To add a term to the search, enter the term you want into the upper text box and click **Add** - To remove a term from the search, select a term in the lower text box and click **Remove** - Click **Clear** to clear all terms from the lower box - Select a qualifier option: @@ -67,8 +67,8 @@ Edit the search terms using the following options: ## Folder Inclusion/Exclusion Window Use the Folder Inclusion/Exclusion window to select individual folders to add to or remove from the -action. The Folder Inclusion/Exclusion window opens if **specific** in **with specific folder(s) to -include/exclude** is selected in the Edit Conditions box. +action. The Folder Inclusion/Exclusion window opens if you select **specific** in **with specific folders +to include/exclude** in the Edit Conditions box. ![Folder Inclusion/Exclusion Window](/images/accessanalyzer/11.6/admin/action/mailbox/folderinclusionexclusionwindow.webp) @@ -78,13 +78,13 @@ Include/Exclude folders using the following options: ![New field added on Folder Inclusion/Exclusion window](/images/accessanalyzer/11.6/admin/action/mailbox/folderinclusionexclusionwindownew.webp) -- Click the ellipsis (**…**) or enter the path to the desired folder in the text box -- Scope auto-populates with **This folder**. Click **This folder** to reveal a drop-down menu to +- Click the ellipsis (**…**) or enter the path to the folder you want in the text box +- Scope auto-populates with **This folder**. Click **This folder** to reveal a dropdown menu to select from the following scope options: - This folder - This folder and subfolders - Subfolders only -- The Remove button becomes enabled once a folder is added to either section. To remove a folder +- The Remove button becomes enabled once you add a folder to either section. To remove a folder from the scope, select it and click **Remove**. diff --git a/docs/accessanalyzer/11.6/admin/action/mailbox/folderidentification.md b/docs/accessanalyzer/11.6/admin/action/mailbox/folderidentification.md index 00203aca87..864270c9d4 100644 --- a/docs/accessanalyzer/11.6/admin/action/mailbox/folderidentification.md +++ b/docs/accessanalyzer/11.6/admin/action/mailbox/folderidentification.md @@ -16,7 +16,7 @@ options: - Yes, the query results contain a mailbox folder identification column - - Select the mailbox identification column using the drop-down menu + - Select the mailbox identification column using the dropdown menu - Folder Identifier Type – Choose which mailbox identifier the selected column uses: - Folder Path and Name – Select this option if the specified field contains a fully @@ -24,7 +24,7 @@ options: - Entry ID – Select this option if the selected field is an EntryID that is a unique identifier for a folder -- No, the query results do not contain a mailbox folder identification column – Selecting this +- No, the query results don't contain a mailbox folder identification column – Selecting this enables the Folder Conditions page, used to identify specific folders to target. See the [Mailbox: Folder Conditions](/docs/accessanalyzer/11.6/admin/action/mailbox/folderconditions.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/admin/action/mailbox/identification.md b/docs/accessanalyzer/11.6/admin/action/mailbox/identification.md index 5c1337d4fd..dbeaa14594 100644 --- a/docs/accessanalyzer/11.6/admin/action/mailbox/identification.md +++ b/docs/accessanalyzer/11.6/admin/action/mailbox/identification.md @@ -18,7 +18,7 @@ Select which mailboxes to target using the following options: - Users found in the following column – Select this option to identify users via a data table column - - Use the drop-down menu to select a data table column containing either the Mailbox display + - Use the dropdown menu to select a data table column containing either the Mailbox display name or email address - Select a data type for the selected field using the following options: diff --git a/docs/accessanalyzer/11.6/admin/action/mailbox/messageactions.md b/docs/accessanalyzer/11.6/admin/action/mailbox/messageactions.md index 2fade6f7b9..93a4e0102a 100644 --- a/docs/accessanalyzer/11.6/admin/action/mailbox/messageactions.md +++ b/docs/accessanalyzer/11.6/admin/action/mailbox/messageactions.md @@ -16,8 +16,8 @@ To select a message action, use the following options: - Select an action – Select the checkbox next to a message action to apply it to the search. The selected action displays in the Edit Actions box. Possible actions include: - - Delete – Items can be recovered via the Deleted Contents table (folder dumpster) - - Permanent Delete – Items are not recoverable + - Delete – You can recover items from the Deleted Contents table (folder dumpster) + - Permanent Delete – Items aren't recoverable - Move to Deleted Items folder - Delete Attachment (Append Text Options) – Deletes attachment and adds **Append Text Options** to the Edit Conditions box diff --git a/docs/accessanalyzer/11.6/admin/action/mailbox/messageconditions.md b/docs/accessanalyzer/11.6/admin/action/mailbox/messageconditions.md index 47a33bcfe6..e5c36d91c7 100644 --- a/docs/accessanalyzer/11.6/admin/action/mailbox/messageconditions.md +++ b/docs/accessanalyzer/11.6/admin/action/mailbox/messageconditions.md @@ -13,7 +13,7 @@ for the Delete Mailbox Contents operation. Customize the folder search conditions using the following options: -- Message Category – Use the drop-down menu to select a message category +- Message Category – Use the dropdown menu to select a message category :::note Each selection may populate various conditions in the Select Conditions section. @@ -39,14 +39,14 @@ Customize the folder search conditions using the following options: - Edit conditions – Any selected conditions populate here - To edit filter conditions, click the underlined portion of the condition. This opens a - corresponding window to configure the condition, with the exception of **has attachment(s)**. + corresponding window to configure the condition, with the exception of **has attachments**. - - Clicking **has attachment(s)** changes it to **has no attachment(s** and vice versa + - Clicking **has attachments** changes it to **has no attachment(s** and vice versa ## MessageClasses Window Use the MessageClasses window to select a message class to apply to the scope of the action. The -MessageClasses window opens if **specific** in **with specific message classes** is selected in the +MessageClasses window opens if you select **specific** in **with specific message classes** in the Edit Conditions box. ![MessageClasses Window](/images/accessanalyzer/11.6/admin/action/mailbox/messageclasseswindow.webp) @@ -57,8 +57,8 @@ Modify message classes using the following options: ![New class added in MessageClasses Window](/images/accessanalyzer/11.6/admin/action/mailbox/messageclasseswindownew.webp) -- Click the ellipsis (**…**) or enter the path to the desired folder in the text box -- Matching Strategy auto-populates with **Exact Match**. Click **Exact Match** to reveal a drop-down +- Click the ellipsis (**…**) or enter the path to the folder you want in the text box +- Matching Strategy auto-populates with **Exact Match**. Click **Exact Match** to reveal a dropdown menu to select from the following scope options: - Exact Match @@ -71,8 +71,8 @@ Modify message classes using the following options: ## Data Range Selection Window Use the Date Range Selection window to determine a time period to scope. The Date Range Selection -window opens if **in specific date** in either the **that is created in specific date** or **that is -received in specific date** conditions is selected in the Edit condition box. +window opens if you select **in specific date** in either the **that is created in specific date** +or **that is received in specific date** conditions in the Edit condition box. ![Data Range Selection Window](/images/accessanalyzer/11.6/admin/action/mailbox/datarangeselectionwindow.webp) @@ -86,18 +86,18 @@ To specify a date range, use the following options: - After - Between -- Configure the date range using the textbox or drop-down menus for the selected option +- Configure the date range using the textbox or dropdown menus for the selected option ## Search Terms Window Use the Search Terms window to select terms in messages to run the action against. The Search Terms -window opens if **search terms** in any condition is selected in the Edit Conditions box. +window opens if you select **search terms** in any condition in the Edit Conditions box. ![Search Terms Window](/images/accessanalyzer/11.6/admin/action/mailbox/searchtermswindow.webp) Edit the search terms using the following options: -- To add a term to the search, enter the desired term into the upper text box and click **Add** +- To add a term to the search, enter the term you want into the upper text box and click **Add** - To remove a term from the search, select a term in the lower text box and click **Remove** - Click **Clear** to clear all terms from the lower box - Specify a qualifier option: @@ -110,11 +110,11 @@ Edit the search terms using the following options: ## Values Window Use the Values window to add or remove values to or from the search. The Values window opens if -**specific** in **with specific Message ID** is selected in the Edit Conditions box. +you select **specific** in **with specific Message ID** in the Edit Conditions box. ![Values Window](/images/accessanalyzer/11.6/admin/action/mailbox/valueswindow.webp) -- To add a term to the search, enter the desired term into the upper text box and click **Add** +- To add a term to the search, enter the term you want into the upper text box and click **Add** - To remove a term from the search, select a term in the lower text box and click **Remove** - Click **Clear** to clear all terms from the lower box - Click **Import CSV** to open a file explorer and select a CSV file to import diff --git a/docs/accessanalyzer/11.6/admin/action/mailbox/operations.md b/docs/accessanalyzer/11.6/admin/action/mailbox/operations.md index ff34c3eedf..ff1a54ac36 100644 --- a/docs/accessanalyzer/11.6/admin/action/mailbox/operations.md +++ b/docs/accessanalyzer/11.6/admin/action/mailbox/operations.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Mailbox: Operations -Use the Operations page to specify the operation to be performed as part of the action. +Use the Operations page to specify the operation to perform as part of the action. ![New Mailbox Action Wizard Operations page](/images/accessanalyzer/11.6/admin/action/mailbox/operations.webp) diff --git a/docs/accessanalyzer/11.6/admin/action/mailbox/overview.md b/docs/accessanalyzer/11.6/admin/action/mailbox/overview.md index a76ce5a86a..97cfa08b73 100644 --- a/docs/accessanalyzer/11.6/admin/action/mailbox/overview.md +++ b/docs/accessanalyzer/11.6/admin/action/mailbox/overview.md @@ -6,19 +6,18 @@ sidebar_position: 40 # Mailbox Action Module -The Mailbox action module allows you to perform bulk operations on Microsoft Exchange mailboxes, for +Use the Mailbox action module to perform bulk operations on Microsoft Exchange mailboxes, for example deleting mailbox content and modifying permissions and delegates. :::warning This action module can add, change, or remove permissions and delegates from an -environment. Always verify the data and target mailboxes prior to executing any action. +environment. Always verify the data and target mailboxes before executing any action. ::: ## Mailbox Action Source Table Configuration -All data tables used in Enterprise Auditor action modules require the presence of certain data -columns. In addition, individual action modules including Mailbox may have their own column +All data tables used in Enterprise Auditor action modules require certain data columns. In addition, individual action modules including Mailbox may have their own column requirements. The Mailbox action module requires a column containing mailbox names. ## Configuration diff --git a/docs/accessanalyzer/11.6/admin/action/mailbox/permissions.md b/docs/accessanalyzer/11.6/admin/action/mailbox/permissions.md index 1bd5f22ed1..5c8eb32e5a 100644 --- a/docs/accessanalyzer/11.6/admin/action/mailbox/permissions.md +++ b/docs/accessanalyzer/11.6/admin/action/mailbox/permissions.md @@ -11,7 +11,7 @@ Use the Permissions page to determine which permissions to remove. It is a wizar ![New Mailbox Action Wizard Permissions page](/images/accessanalyzer/11.6/admin/action/mailbox/permissions.webp) -Use the following options to add, change or remove Permissions: +Use the following options to add, change, or remove Permissions: - User – Specifies user permissions to add or change. To select different users, click the down-arrow to display the User window. See the [User Window](#user-window) topic for additional @@ -22,8 +22,8 @@ Use the following options to add, change or remove Permissions: window. See the [Permission Window](#permission-window) topic for additional information. - Propagate permissions to child folders – Propagates permissions to the child folders of the selected folders -- Once User, Folder, and Permission are selected, click **Add** to add them to the summary of the - action to be taken +- Once you select User, Folder, and Permission, click **Add** to add them to the summary of the + action - To remove an added Permission, select it in the panel and click **Remove** ## User Window @@ -37,7 +37,7 @@ Select a user using the following options: - Users found in the following column – Select this option to identify users via a data table column - - Use the drop-down menu to select a data table column containing either the Mailbox display + - Use the dropdown menu to select a data table column containing either the Mailbox display name or email address - Select a data type for the selected field using the following options: @@ -81,7 +81,7 @@ Select a folder using the following options: - The list of folders – Select one of the default folders - - Select a folder from the drop-down menu and click **Add** + - Select a folder from the dropdown menu and click **Add** - To remove a folder, select it and click **Remove** ## Permission Window @@ -93,9 +93,9 @@ Use the Permission window to specify permissions. The Permission window opens wh Specify permissions using the following options: -- Permissions Level – Each permission level has a set of default selections. If a setting is - changed, the Permissions Level field changes to **Custom**. Permission levels are associated with - the different permissions available for assignment through Outlook. Options include: +- Permissions Level – Each permission level has a set of default selections. If you change a + setting, the Permissions Level field changes to **Custom**. Permission levels correspond to the + different permissions available for assignment through Outlook. Options include: - None - Contributor @@ -131,7 +131,7 @@ Specify permissions using the following options: - Folder Contact – User receives automated messages about the folder such as replication conflict messages, requests from users for additional permissions, and other changes to folder status - - Folder visible – User can see the folder but cannot read or edit the items within + - Folder visible – User can see the folder but can't read or edit the items within - To add anonymous permissions, choose **None** diff --git a/docs/accessanalyzer/11.6/admin/action/mailbox/samplinghost.md b/docs/accessanalyzer/11.6/admin/action/mailbox/samplinghost.md index fa3bbbd762..9b19d95449 100644 --- a/docs/accessanalyzer/11.6/admin/action/mailbox/samplinghost.md +++ b/docs/accessanalyzer/11.6/admin/action/mailbox/samplinghost.md @@ -16,17 +16,17 @@ Select an Exchange server to target using the following options: - Select the **Use Global Setting** checkbox to query the global Exchange setting - Use the radio buttons to select a specific host - System Attendant (2003 & 2007) – Audits Microsoft Exchange 2007 or older versions -- Use the mailbox associated with the Windows account that Enterprise Auditor is run with – Uses +- Use the mailbox associated with the Windows account under which Enterprise Auditor runs – Uses either the account logged into the Enterprise Auditor Console server or the account set to run the Enterprise Auditor application to access the Exchange mailbox -- Exchange Mailbox (2010 and newer) – Allows Exhange Mailbox Alias to be specified for MAPI +- Exchange Mailbox (2010 and newer) – Allows specifying an Exchange Mailbox Alias for MAPI connections - - When Exchange Mailbox (2010 and newer) is selected, the textbox is enabled. Enter the Alias - name in the textbox. The Alias needs to be an Exchange 2010 or newer mailbox, not a - mail-enabled service account. However, this mailbox does not need rights on the Exchange + - When you select Exchange Mailbox (2010 and newer), the textbox becomes enabled. Enter the + Alias name in the textbox. The Alias needs to be an Exchange 2010 or newer mailbox, not a + mail-enabled service account. However, this mailbox doesn't need rights on the Exchange Organization; it only needs to reside within it. - Client Access Server – Enter the name of the physical CAS in the textbox. This server can be part of an array, but do enter the name of a CAS Array. This should also be the Exchange CAS - where both Remote PowerShell and Windows Authentication on the PowerShell Virtual Directory - have been enabled. + where you've enabled both Remote PowerShell and Windows Authentication on the PowerShell + Virtual Directory. diff --git a/docs/accessanalyzer/11.6/admin/action/mailbox/trustedusers.md b/docs/accessanalyzer/11.6/admin/action/mailbox/trustedusers.md index ceaeb397ef..6984333bb0 100644 --- a/docs/accessanalyzer/11.6/admin/action/mailbox/trustedusers.md +++ b/docs/accessanalyzer/11.6/admin/action/mailbox/trustedusers.md @@ -6,7 +6,7 @@ sidebar_position: 110 # Mailbox: Trusted Users -Use the Trusted Users page to select delegates to add. Users can be added individually or from a +Use the Trusted Users page to select delegates to add. You can add users individually or from a server with a mailbox environment. It is a wizard page for the following operations: - Add Delegates @@ -18,7 +18,7 @@ Select Trusted User delegates using the following options: - Users found in the following column – Select this option to identify users via a data table column - - Use the drop-down menu to select a data table column containing either the Mailbox display + - Use the dropdown menu to select a data table column containing either the Mailbox display name or email address - Select a data type for the selected field using the following options: @@ -50,7 +50,6 @@ The following additional options are available for the Remove Delegates operatio - Remove Permissions from Child Folders – Removes permissions from child folders :::note - This option is only enabled if the **Remove Permissions for Delegate** option is - selected. - + This option is only enabled if you select the **Remove Permissions for Delegate** + option. ::: diff --git a/docs/accessanalyzer/11.6/admin/action/overview.md b/docs/accessanalyzer/11.6/admin/action/overview.md index 262977833c..430f737a6f 100644 --- a/docs/accessanalyzer/11.6/admin/action/overview.md +++ b/docs/accessanalyzer/11.6/admin/action/overview.md @@ -11,8 +11,8 @@ Enterprise Auditor. This overview topic describes the basic procedure for creati action module as well the initial steps to take when configuring an action. Each action module is described in detail in the relevant topics. -The Enterprise Auditor actions are capable of changing users, permissions, files, and objects from a -variety of environments. Action modules are assigned to a job at the **Configure** > **Actions** +Enterprise Auditor actions can change users, permissions, files, and objects from a variety of +environments. Action modules are assigned to a job at the **Configure** > **Actions** node. See the [Actions Node](/docs/accessanalyzer/11.6/admin/jobs/job/configure/actions.md) topic for additional information on the Action Selection view. @@ -22,7 +22,7 @@ topic for additional information on the Action Selection view. Configure the action through the Action Properties page. Navigate to the job’s **Configure** > **Actions** node. Select **Create Action** to add a new action task to a job. Select an existing action and click **Action Properties** to modify its configuration. The Action Properties page opens -for either option. Pre-configured action tasks can be added from the Action Library. See the +for either option. You can add pre-configured action tasks from the Action Library. See the [Action Libraries](/docs/accessanalyzer/11.6/admin/action/libraries.md) topic for additional information. @@ -54,7 +54,7 @@ while the SendMail Action Module can send an email to a dynamic list of users. The basic procedure consists of the following steps. -**Step 1 –** Create a data table containing the target objects to be modified and exclude any +**Step 1 –** Create a data table containing the target objects to modify and exclude any extraneous columns. **Step 2 –** Configure an action task using the configuration wizard for the selected action module. @@ -64,9 +64,8 @@ Target the selected objects and apply selected operations to the data. ### Executing Actions -Actions with the checkbox next to their name selected in the Action Selection view are executed -automatically as part of the job’s execution. The actions are executed in the order in which they -appear in the Selection table. You can also manually execute selected actions without running the +The job automatically executes actions with the checkbox next to their name selected in the Action +Selection view. It executes the actions in the order they appear in the Selection table. You can also manually execute selected actions without running the job by clicking on the **Action Execute** link on the Action Selection view. ## Caution on Action Modules @@ -74,15 +73,14 @@ job by clicking on the **Action Execute** link on the Action Selection view. :::warning Enterprise Auditor action modules apply bulk changes to targeted objects within the target environment. Actions perform operations on selected objects listed in each row of the source -table. Exercise caution to ensure the action applies only the desired changes and only to the -desired target objects. +table. Exercise caution to ensure the action applies only to the changes and target objects you want. ::: :::info -Prior to configuring the action module, scope the source data table to include -only the desired data. It is also recommended to run the action in a test environment before making -changes to a production environment. +Before configuring the action module, scope the source data table to include +only the data you want. Also run the action in a test environment before making changes to a +production environment. ::: @@ -101,7 +99,7 @@ created action tasks. - Name – Action task name. For new actions, an editable default name displays. - Description – Action task description. For new actions, this editable field is blank. -- Action Module – Drop-down menu of available action modules +- Action Module – dropdown menu of available action modules - Configure Action – Opens the configuration wizard for the selected action module @@ -113,7 +111,7 @@ created action tasks. - ID – Unique identifier, or GUID, of the action task generated by the application. With this ID, the database can distinguish actions, even those with identical configurations. - Data Grid – Displays a sample of the selected Source table. This data grid functions the same as - all data grids within Enterprise Auditor. Data can be filtered, and columns can be regrouped. See + all data grids within Enterprise Auditor. You can filter data and regroup columns. See the [Data Grid Functionality](/docs/accessanalyzer/11.6/admin/navigate/datagrid.md) topic for additional information. @@ -134,20 +132,20 @@ analysis and reports downstream. | RowKey | Identifies each data row as unique. Sometimes the value is a GUID, but the datatype in the table is a varchar (text string). | :::tip -Remember, the individual action modules may have their own column requirements in addition to the -above. +Remember, the individual action modules may have their own column requirements in addition to +these. ::: #### Data Tables -Enterprise Auditor native data tables generally contain all of the above columns. However, if all -required columns are not present by default, add them manually. +Enterprise Auditor native data tables generally contain all of these columns. However, if all +required columns aren't present by default, add them manually. :::warning -Do not use native data tables in action modules. Source data tables in actions should +Don't use native data tables in action modules. Source data tables in actions should include only the data desired for the operation. Scope the data tables to include only the required -columns prior to configuring the action. +columns before configuring the action. ::: diff --git a/docs/accessanalyzer/11.6/admin/action/powershell/executionoptions.md b/docs/accessanalyzer/11.6/admin/action/powershell/executionoptions.md index c0a45771a3..d9c041965e 100644 --- a/docs/accessanalyzer/11.6/admin/action/powershell/executionoptions.md +++ b/docs/accessanalyzer/11.6/admin/action/powershell/executionoptions.md @@ -21,8 +21,8 @@ The options on the Execution Options page are: - Execute script remotely on a target server – Enable this to execute the PowerShell script on a remote target server - - Use the **Remote host** dropdown to select the database column that will be used as the target - server name or type in a network host name + - Use the **Remote host** dropdown to select the database column to use as the target server + name, or type in a network host name - Select the **Fall back to the local Enterprise Auditor server if the remote execution fails** option to use the Enterprise Auditor server if remote execution fails diff --git a/docs/accessanalyzer/11.6/admin/action/powershell/overview.md b/docs/accessanalyzer/11.6/admin/action/powershell/overview.md index 9d218aa1c7..fd880a22ec 100644 --- a/docs/accessanalyzer/11.6/admin/action/powershell/overview.md +++ b/docs/accessanalyzer/11.6/admin/action/powershell/overview.md @@ -10,8 +10,7 @@ The PowerShell action module provides methods of running PowerShell scripts on t on remote hosts. Define PowerShell scripting actions using the PowerShell Action Module Wizard. :::warning -Ensure that only the changes required are applied and only to those target systems -desired. +Apply only the changes you need, and only to the target systems you intend. ::: diff --git a/docs/accessanalyzer/11.6/admin/action/powershell/script.md b/docs/accessanalyzer/11.6/admin/action/powershell/script.md index 05c2909a94..6a041b6f82 100644 --- a/docs/accessanalyzer/11.6/admin/action/powershell/script.md +++ b/docs/accessanalyzer/11.6/admin/action/powershell/script.md @@ -6,15 +6,15 @@ sidebar_position: 10 # PowerShell Action: Script -The Script page enables you to input the PowerShell script that will be used to perform the +Use the Script page to input the PowerShell script that performs the requested action. Built-in variables are available for use in the script. ![PowerShell Action Module Wizard Script page](/images/accessanalyzer/11.6/admin/action/powershell/script.webp) -The PowerShell script can be entered manually into the Script window at the top of the Script page. +You can enter the PowerShell script manually into the Script window at the top of the Script page. To open a pre-existing PowerShell script from a file, click **Open** to select the script file. -At the bottom of the page are three tabs that can be used to configure the PowerShell action module +Use the three tabs at the bottom of the page to configure the PowerShell action module further. The tabs are: - [Columns](#columns) @@ -27,7 +27,7 @@ Use the Columns tab to select the available columns. ![Columns tab](/images/accessanalyzer/11.6/admin/action/powershell/scriptcolumns.webp) -The table in the Columns tab displays the Columns that can be used for the PowerShell script. To use +The table in the Columns tab displays the columns you can use for the PowerShell script. To use a Column, select the checkbox under the **Use** column. ![Right-click menu](/images/accessanalyzer/11.6/admin/action/powershell/scriptrightclickoption.webp) @@ -53,7 +53,7 @@ The options are: - Delete – Delete a selected parameter :::note -The built-in default parameters cannot be edited or deleted. +You can't edit or delete the built-in default parameters. ::: diff --git a/docs/accessanalyzer/11.6/admin/action/publicfolder/action.md b/docs/accessanalyzer/11.6/admin/action/publicfolder/action.md index bb5dbd2887..218bc14426 100644 --- a/docs/accessanalyzer/11.6/admin/action/publicfolder/action.md +++ b/docs/accessanalyzer/11.6/admin/action/publicfolder/action.md @@ -10,8 +10,8 @@ The Action page specifies the basic action to perform on public folders. The pag selection in the Steps pane adjust based on this selection. :::note -Once an action is selected and saved, and the wizard is closed, this page is no longer -available and the selection cannot be altered. +Once you select and save an action and close the wizard, this page is no longer available, and +you can't alter the selection. ::: @@ -19,9 +19,9 @@ available and the selection cannot be altered. Choose from the following actions: -- Define a new action – Enables the Operation page where the operation on which the action is based - is selected -- Rollback a previously executed action – Enables the Prior Actions page where a list of previously - executed actions is displayed and a selected action may be rolled back. Not all operations support - rollback, and the Support Rollback option must be enabled prior to execution for the action to be - eligible for rollback. +- Define a new action – Enables the Operation page, where you select the operation the action is + based on +- Rollback a previously executed action – Enables the Prior Actions page, which displays a list of + previously executed actions and lets you roll back a selected action. Not all operations support + rollback. Enable the Support Rollback option before execution to make the action eligible for + rollback. diff --git a/docs/accessanalyzer/11.6/admin/action/publicfolder/folders.md b/docs/accessanalyzer/11.6/admin/action/publicfolder/folders.md index c0696f87cf..6f932804c2 100644 --- a/docs/accessanalyzer/11.6/admin/action/publicfolder/folders.md +++ b/docs/accessanalyzer/11.6/admin/action/publicfolder/folders.md @@ -17,8 +17,8 @@ The options on this page are: - Field – Column names :::note - The displayed fields vary depending on the Source Table selected during the - creation of the new action + The displayed fields vary depending on the Source Table selected when you create + the new action. ::: diff --git a/docs/accessanalyzer/11.6/admin/action/publicfolder/mapisettings.md b/docs/accessanalyzer/11.6/admin/action/publicfolder/mapisettings.md index a9772d6738..5320c8e34d 100644 --- a/docs/accessanalyzer/11.6/admin/action/publicfolder/mapisettings.md +++ b/docs/accessanalyzer/11.6/admin/action/publicfolder/mapisettings.md @@ -16,6 +16,6 @@ Use the following options to configure the action: - System Attendant (2003 & 2007) - Use the mailbox associated with the Windows account on which Enterprise Auditor is run - Exchange Mailbox (2010 and newer) – If targeting a 2010 Exchange Server, specify the CAS server. - This is also where the MAPI setting is selected. + This is also where you select the MAPI setting. - Client Access Server – Enter the Domain Name in this field diff --git a/docs/accessanalyzer/11.6/admin/action/publicfolder/operations.md b/docs/accessanalyzer/11.6/admin/action/publicfolder/operations.md index 70aa217f55..8e9d816954 100644 --- a/docs/accessanalyzer/11.6/admin/action/publicfolder/operations.md +++ b/docs/accessanalyzer/11.6/admin/action/publicfolder/operations.md @@ -10,8 +10,8 @@ Use the Operations page to specify the operations to perform as part of the acti ![Public Folder Action Module Wizard Operations page](/images/accessanalyzer/11.6/admin/action/publicfolder/operations.webp) -The **Add operation** drop-down menu lists the operations that can be performed. Each operation -opens a corresponding window. Operations include: +The **Add operation** dropdown menu lists the operations you can perform. Each operation opens a +corresponding window. Operations include: - Rename – See the [Rename Folder Window](#rename-folder-window) topic for additional information - Change permissions – See the [Change Permissions Window](#change-permissions-window) topic for @@ -22,9 +22,9 @@ opens a corresponding window. Operations include: - Limits – See the [Limits Window](#limits-window) topic for additional information - Delete – See the [Delete Folder Window](#delete-folder-window) topic for additional information -The buttons to the right of the drop-down control the operations in the field: +The buttons to the right of the dropdown control the operations in the field: -- Edit – Allows you to alter operation settings +- Edit – Alters operation settings - Add – Places selected operation one step above its current position - Down – Places selected operation one step below its current position - Delete – Removes a selected operation @@ -66,7 +66,7 @@ Change permissions using the following options: - Mode – Select whether to change or remove permissions - Permissions – Determine Permission level and assign permissions to the user - - Permission level – Use the drop-down menu to select a permission level from the following: + - Permission level – Use the dropdown menu to select a permission level from the following: - Reviewer - Contributor @@ -84,20 +84,20 @@ Change permissions using the following options: - Read items – User can read items - Create Subfolders – User can create subfolders - Folder owner – User can view and move the public folder, create subfolders, and set - permissions for the folder, but cannot read, edit, delete, or create items + permissions for the folder, but can't read, edit, delete, or create items - Folder contact – Set user as the contact for the specified public folder - - Folder visible – User can view the specified public folder but cannot read or edit the + - Folder visible – User can view the specified public folder but can't read or edit the items within :::note - Different permissions become automatically selected based on which permission - level is selected. To override this default, select the checkbox of the unwanted permission - to deselect it. If a desired checkbox is blocked by a black square, click the square to - unblock the checkbox. The checkbox can then be selected or unselected. + Selecting a permission level automatically selects different permissions. To + override this default, select the checkbox of the unwanted permission to deselect it. If a + black square blocks a desired checkbox, click the square to unblock the checkbox. You can + then select or unselect the checkbox. ::: - - Edit items – Use the drop-down menu to determine user editing permissions from the following: + - Edit items – Use the dropdown menu to determine user editing permissions from the following: - No change - None @@ -106,7 +106,7 @@ Change permissions using the following options: - Own only - All - - Delete items – Use the drop-down menu to determine user deletion permissions from the + - Delete items – Use the dropdown menu to determine user deletion permissions from the following: - No change @@ -145,11 +145,12 @@ Use the Replicas window to replicate servers. It is a wizard page for the Replic Replicate servers using the following options: -- Select a server from the dropdown menu and click **Add**. The servers listed will be replicated. +- Select a server from the dropdown menu and click **Add**. The action replicates the servers + listed. - Select a server from the list and click **Delete** to remove it from the list of replicated servers -- Select the **Remove last replica** option to delete the replica created when the action was last - run +- Select the **Remove last replica** option to delete the replica created the last time the action + ran ## Limits Window @@ -182,5 +183,5 @@ Select deletion settings using the following options: - Optionally, select a checkbox to apply any exception - - Do not delete folders with subfolders - - Do not delete folders with content + - Don't delete folders with subfolders + - Don't delete folders with content diff --git a/docs/accessanalyzer/11.6/admin/action/publicfolder/overview.md b/docs/accessanalyzer/11.6/admin/action/publicfolder/overview.md index 3e4d0f4c91..f50777173b 100644 --- a/docs/accessanalyzer/11.6/admin/action/publicfolder/overview.md +++ b/docs/accessanalyzer/11.6/admin/action/publicfolder/overview.md @@ -6,24 +6,22 @@ sidebar_position: 60 # PublicFolder Action Module -The Public Folder action module allows users to make bulk changes to selected Microsoft Exchange +Use the Public Folder action module to make bulk changes to selected Microsoft Exchange public folders by adding, changing, or removing folders and permissions from the environment. Use the Pubic Folder Action Module Wizard to choose the data table column that identifies the folders and to configure the operations performed against the selected folders. -Prior to configuring the Pubic Folder Action Module Wizard, scope the source data table to ensure -the actions apply only to the desired folders. +Before configuring the Public Folder Action Module Wizard, scope the source data table to ensure +the actions apply only to the folders you want. :::warning -Be careful when using this action module. Make sure that only the changes required are -applied and only to those target folders desired. Always verify the data prior to execution of any -action. +Be careful when using this action module. Apply only the changes you need, and only to the +target folders you intend. Always verify the data before executing any action. ::: :::info -Although rollbacks for some actions are available, having to use one should be -avoided +Although rollbacks are available for some actions, avoid relying on them. ::: diff --git a/docs/accessanalyzer/11.6/admin/action/publicfolder/prioractions.md b/docs/accessanalyzer/11.6/admin/action/publicfolder/prioractions.md index a1a29f42e7..ea946f26b7 100644 --- a/docs/accessanalyzer/11.6/admin/action/publicfolder/prioractions.md +++ b/docs/accessanalyzer/11.6/admin/action/publicfolder/prioractions.md @@ -10,8 +10,8 @@ The Prior Actions page selects previously executed actions for rollback. It is a **Rollback a previously executed action** is selected on the Action page. :::note -Once an action is selected and saved, and the wizard is closed, this page is no longer -available and the selection cannot be altered. +Once you select and save an action and close the wizard, this page is no longer available, and +you can't alter the selection. ::: diff --git a/docs/accessanalyzer/11.6/admin/action/publicfolder/rollback.md b/docs/accessanalyzer/11.6/admin/action/publicfolder/rollback.md index f4f6155ac4..81b1ebbb12 100644 --- a/docs/accessanalyzer/11.6/admin/action/publicfolder/rollback.md +++ b/docs/accessanalyzer/11.6/admin/action/publicfolder/rollback.md @@ -6,8 +6,8 @@ sidebar_position: 60 # Public Folder: Rollback -Use the Rollback page to enable rollback capabilities for the action. If rollback isn’t selected at -this step, the applied operations cannot be rolled back after execution of the action module. +Use the Rollback page to enable rollback capabilities for the action. If you don't select rollback +at this step, you can't roll back the applied operations after execution of the action module. ![Public Folder Action Module Wizard Rollback page](/images/accessanalyzer/11.6/admin/action/publicfolder/rollback.webp) diff --git a/docs/accessanalyzer/11.6/admin/action/publicfolder/summary.md b/docs/accessanalyzer/11.6/admin/action/publicfolder/summary.md index e93c5f1c56..d9bfa54ad9 100644 --- a/docs/accessanalyzer/11.6/admin/action/publicfolder/summary.md +++ b/docs/accessanalyzer/11.6/admin/action/publicfolder/summary.md @@ -10,6 +10,5 @@ The Summary page summarizes the configuration of the action. ![Public Folder Action Module Wizard Summary page](/images/accessanalyzer/11.6/admin/action/publicfolder/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Public Folder Action Module Wizard to ensure that no accidental clicks -are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** instead to +close the Public Folder Action Module Wizard without saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/action/registry/operations.md b/docs/accessanalyzer/11.6/admin/action/registry/operations.md index 2243484cb3..e6f6d6bc5e 100644 --- a/docs/accessanalyzer/11.6/admin/action/registry/operations.md +++ b/docs/accessanalyzer/11.6/admin/action/registry/operations.md @@ -14,11 +14,11 @@ for additional information. Select and configure the operations using the following options: -- Add operation – Use the drop-down menu to select an operation to perform on the target host. This +- Add operation – Use the dropdown menu to select an operation to perform on the target host. This opens a corresponding window for configuration. Operations include: :::note - Window options vary based on the operation selected from the drop-down menu. + Window options vary based on the operation selected from the dropdown menu. ::: @@ -45,12 +45,12 @@ Select a key using the following options: - Computer name – By default, the Registry browser connects to the local machine - - If the desired registry item is on the local machine, browse the registry, and select the item + - If the registry item you want is on the local machine, browse the registry, and select the item - To connect to the registry of another machine: - Enter the hostname in the **Computer name** textbox - Click **Connect**, then browse the registry of that machine - - Select the desired registry item + - Select the registry item you want - Connect – Attempts to connect to the registry of the machine specified in the **Computer name** field @@ -65,14 +65,14 @@ Use the Select Users or Groups window to select a user, group, or built-in secur The options are: -- Select this object type – Displays types that are queried against +- Select this object type – Displays types to query against - Click **Object Types** to open the Object Types window and select the types to query against. See the [Object Types Window](#object-types-window) topic for additional information. -- From this location – Displays the location the intended objects are found +- From this location – Displays the location where the intended objects reside - - Click **Locations** to open the Locations window and set the location to be queried. See the + - Click **Locations** to open the Locations window and set the location to query. See the [Locations Window](#locations-window) topic for additional information. - Enter the object names to select – Select names of objects to query @@ -127,8 +127,8 @@ following additional options: - Columns – Click **Columns** to open the Choose Columns window. See the [Choose Columns Window](#choose-columns-window) topic for additional information. - Find now – Click **Find Now** to search for objects matching the selected criteria -- Stop – While a search is running , the **Stop** button is available. Click **Stop** to halt the - search before it is completed. +- Stop – While a search is running, the **Stop** button is available. Click **Stop** to halt the + search before it completes. - Search Results – Displays results from a search #### Choose Columns Window diff --git a/docs/accessanalyzer/11.6/admin/action/registry/overview.md b/docs/accessanalyzer/11.6/admin/action/registry/overview.md index b54d0144c6..6aa1b5399a 100644 --- a/docs/accessanalyzer/11.6/admin/action/registry/overview.md +++ b/docs/accessanalyzer/11.6/admin/action/registry/overview.md @@ -6,13 +6,13 @@ sidebar_position: 70 # Registry Action Module -The Registry action module allows users to make bulk changes to the Microsoft Windows Registry. Use +Use the Registry action module to make bulk changes to the Microsoft Windows Registry. Use the Registry Action Module Wizard to choose the data table column that identifies the folders and to configure the operations performed against the selected folders. The Registry action module requires -a column containing the hosts to be targeted. +a column containing the hosts to target. -Prior to configuring the Registry Action Module Wizard, scope the source data table to ensure the -actions apply only to the desired hosts. +Before configuring the Registry Action Module Wizard, scope the source data table to ensure the +actions apply only to the hosts you want. :::warning Unexpected values in the registry can cause major system failures when deleting or @@ -28,10 +28,9 @@ module. ## Registry Action Source Table Configuration -All data tables used in Enterprise Auditor action modules require the presence of certain data -columns. In addition, individual action modules including Registry may have their own column -requirements. The Registry action module requires a column containing the hosts that are going to be -targeted. +All data tables used in Enterprise Auditor action modules require certain data columns. In +addition, individual action modules including Registry may have their own column requirements. The +Registry action module requires a column containing the hosts to target. ## Configuration diff --git a/docs/accessanalyzer/11.6/admin/action/registry/summary.md b/docs/accessanalyzer/11.6/admin/action/registry/summary.md index 34296427d6..f85a233694 100644 --- a/docs/accessanalyzer/11.6/admin/action/registry/summary.md +++ b/docs/accessanalyzer/11.6/admin/action/registry/summary.md @@ -10,6 +10,5 @@ The Summary page summarizes the configuration of the action. ![Registry Action Module Wizard Summary page](/images/accessanalyzer/11.6/admin/action/registry/summary.webp) -When done configuring the action, click **Finish**. If no changes were made, it is a best practice -to click **Cancel** to close the Registry Action Module Wizard to ensure that no accidental clicks -are saved. +When done configuring the action, click **Finish**. If you made no changes, click **Cancel** instead +to close the Registry Action Module Wizard without saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/action/registry/targethosts.md b/docs/accessanalyzer/11.6/admin/action/registry/targethosts.md index 74b13179cf..651da3298b 100644 --- a/docs/accessanalyzer/11.6/admin/action/registry/targethosts.md +++ b/docs/accessanalyzer/11.6/admin/action/registry/targethosts.md @@ -11,6 +11,6 @@ alters. ![Registry Action Module Wizard Target hosts page](/images/accessanalyzer/11.6/admin/action/registry/targethosts.webp) -Use the drop-down menu to select the field that identifies the systems to be targeted. The list -displays columns from the specified source table. The action applies the specified operations to all +Use the dropdown menu to select the field that identifies the systems to target. The list displays +columns from the specified source table. The action applies the specified operations to all systems in the field. diff --git a/docs/accessanalyzer/11.6/admin/action/sendmail/message.md b/docs/accessanalyzer/11.6/admin/action/sendmail/message.md index 924a56476e..a5f564895e 100644 --- a/docs/accessanalyzer/11.6/admin/action/sendmail/message.md +++ b/docs/accessanalyzer/11.6/admin/action/sendmail/message.md @@ -15,8 +15,8 @@ Use the following fields to specify the text of the email: - Subject – Specify a subject for the email. The contents of this field displays as the subject line of the delivered email. Enter text directly and optionally use the Insert field to insert one or more data fields. This is a required field. -- Insert Field – Inserts a data field into the subject or body of the email. The drop-down menu - displays a list of available fields. Once a selection displays in the field, click on the blue Up +- Insert Field – Inserts a data field into the subject or body of the email. The dropdown menu + displays a list of available fields. Once a selection displays in the field, click the blue Up and Down arrows to insert the field into the body or the subject, respectively. This field is optional. - Show sample input source data – To display a table of sample source data, click the icon next to @@ -54,7 +54,7 @@ Use the following fields to specify the text of the email: ## Text Entry Box -The Text Entry box allows you to compose a message. A Microsoft Word-style editor provides +Use the Text Entry box to compose a message. A Microsoft Word-style editor provides formatting options including the ability to insert dynamic text from the specified table (such as a username) through the Insert field option. Use the editor to personalize the content and appearance of each message. @@ -62,13 +62,13 @@ of each message. Example: Assume the source table includes a column containing the names of intended recipients. Place the -cursor in the greeting section of the email. Next, select that field from the Insert field drop-down +cursor in the greeting section of the email. Next, select that field from the Insert field dropdown list and click the down arrow to insert a dynamic field. The column name appears in the Text Entry box, enclosed by brackets: Dear [ProbableOwner]; -You are approaching your Mailbox storage quota. Please clean up any unneeded items. +You are approaching your Mailbox storage quota. clean up any unneeded items. **Thank you,** diff --git a/docs/accessanalyzer/11.6/admin/action/sendmail/overview.md b/docs/accessanalyzer/11.6/admin/action/sendmail/overview.md index 6373ff339b..5032254031 100644 --- a/docs/accessanalyzer/11.6/admin/action/sendmail/overview.md +++ b/docs/accessanalyzer/11.6/admin/action/sendmail/overview.md @@ -16,15 +16,15 @@ The SendMail Action Module has multiple uses, for example: workflow to contact clients and solicit feedback for use in the decision-making process :::warning -This module sends one or more electronic messages to a selected audience. Prior to -executing the action, ensure the audience consists of only the desired members. +This module sends one or more electronic messages to a selected audience. Before +executing the action, ensure the audience consists of only the members you want. ::: ## Source Table Configuration -All data tables used in Enterprise Auditor action modules require the presence of certain data -columns. In addition, individual action modules including SendMail may have their own column +All data tables used in Enterprise Auditor action modules require certain data columns. In +addition, individual action modules including SendMail may have their own column requirements. The SendMail Action Module requires a column containing well-formatted email addresses (for example, `hfinn@netwrix.com`) for your recipients. diff --git a/docs/accessanalyzer/11.6/admin/action/sendmail/properties.md b/docs/accessanalyzer/11.6/admin/action/sendmail/properties.md index 4fca40536f..8b0d1b3a89 100644 --- a/docs/accessanalyzer/11.6/admin/action/sendmail/properties.md +++ b/docs/accessanalyzer/11.6/admin/action/sendmail/properties.md @@ -12,16 +12,16 @@ Use the Properties page to specify the recipients of the email. Use the following fields to specify the recipient information: -- Recipient column – Use the drop-down menu to specify the column from the data table containing +- Recipient column – Use the dropdown menu to specify the column from the data table containing intended recipients, for example a column containing email addresses -- Recipient type – Use the drop-down menu to specify the data type of the Recipient column, for +- Recipient type – Use the dropdown menu to specify the data type of the Recipient column, for example SMTP mail address - Carbon copy (CC) – Optionally, specify one or more additional email addresses to receive a carbon-copy of the SendMail message, for example an address not included in the source table. - Use the following email address – Enter one or more additional email addresses. Separate multiple addresses with a semi-colon and a space. - - Use a column from the table – Use the drop-down menu to specify a column from the data table + - Use a column from the table – Use the dropdown menu to specify a column from the data table - Combine multiple messages into a single message when all recipients are the same – Select this checkbox to send only one message to each recipient as a result of this action (even recipients diff --git a/docs/accessanalyzer/11.6/admin/action/sendmail/summary.md b/docs/accessanalyzer/11.6/admin/action/sendmail/summary.md index 3ddd53330b..a9b39d99ac 100644 --- a/docs/accessanalyzer/11.6/admin/action/sendmail/summary.md +++ b/docs/accessanalyzer/11.6/admin/action/sendmail/summary.md @@ -10,9 +10,8 @@ The Summary page displays the SendMail configuration. ![Send Mail Action Module Wizard Summary page](/images/accessanalyzer/11.6/admin/action/sendmail/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Send Mail Action Module Wizard to ensure that no accidental clicks are -saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** instead to +close the Send Mail Action Module Wizard without saving accidental clicks. To view the status of executed SendMail actions, see the [Viewing the Status of SendMail Actions](/docs/accessanalyzer/11.6/admin/action/sendmail/viewstatus.md) diff --git a/docs/accessanalyzer/11.6/admin/action/sendmail/viewstatus.md b/docs/accessanalyzer/11.6/admin/action/sendmail/viewstatus.md index 60f8b5ef94..c04c14e46c 100644 --- a/docs/accessanalyzer/11.6/admin/action/sendmail/viewstatus.md +++ b/docs/accessanalyzer/11.6/admin/action/sendmail/viewstatus.md @@ -6,7 +6,7 @@ sidebar_position: 40 # Viewing the Status of SendMail Actions -Follow the steps to view the status of an executed SendMail action: +To view the status of an executed SendMail action: ![Analysis Properties page for SendMail View Status Analysis task](/images/accessanalyzer/11.6/admin/action/sendmail/viewstatusanalysisproperties.webp) diff --git a/docs/accessanalyzer/11.6/admin/action/servicenow/authentication.md b/docs/accessanalyzer/11.6/admin/action/servicenow/authentication.md index e57708b738..3a8157bf70 100644 --- a/docs/accessanalyzer/11.6/admin/action/servicenow/authentication.md +++ b/docs/accessanalyzer/11.6/admin/action/servicenow/authentication.md @@ -8,8 +8,8 @@ sidebar_position: 10 The Authentication page implements signing into a ServiceNow account. -A ServiceNow account must be set up and configured to determine which incidents will be visible on -the Incident Creation page. +You must set up and configure a ServiceNow account to determine which incidents are visible on the +Incident Creation page. ![ServiceNow Action Module wizard Authentication page](/images/accessanalyzer/11.6/admin/action/servicenow/authentication.webp) diff --git a/docs/accessanalyzer/11.6/admin/action/servicenow/description.md b/docs/accessanalyzer/11.6/admin/action/servicenow/description.md index 9197650dee..451d398f80 100644 --- a/docs/accessanalyzer/11.6/admin/action/servicenow/description.md +++ b/docs/accessanalyzer/11.6/admin/action/servicenow/description.md @@ -7,15 +7,15 @@ sidebar_position: 30 # ServiceNow Action: Description The Description page provides details on the incidents entered into a field on the Incident Creation -page. A description of the incident and related comments are included with the incident’s report to -provide additional feedback to the system administrator, and may be saved to a template. +page. The incident's report includes a description of the incident and related comments, providing +additional feedback to the system administrator. You can save this information to a template. ![ServiceNow Action Module wizard Description page](/images/accessanalyzer/11.6/admin/action/servicenow/description.webp) Create a report using the following options: - Short Description – Displays entered words or phrases used to summarize the incident -- Insert Field – Use the drop-down menu to select a field (column) from the source table +- Insert Field – Use the dropdown menu to select a field (column) from the source table - Click the **blue down arrow** to insert the item into the Short Description section - Click the **blue up arrow** to insert the item in to the Comments section diff --git a/docs/accessanalyzer/11.6/admin/action/servicenow/incidentcreation.md b/docs/accessanalyzer/11.6/admin/action/servicenow/incidentcreation.md index 773c7e974f..03f0c785e8 100644 --- a/docs/accessanalyzer/11.6/admin/action/servicenow/incidentcreation.md +++ b/docs/accessanalyzer/11.6/admin/action/servicenow/incidentcreation.md @@ -6,10 +6,10 @@ sidebar_position: 20 # ServiceNow Action: Incident Creation -The Incident Creation page is available once the ServiceNow credentials are approved. Incidents on -this page belong to two fields: Mandatory and Optional. The type of field and its incidents are -chosen within ServiceNow’s configuration page. Selecting a field and entering a value will include -the incident within ServiceNow’s incident report. +The Incident Creation page is available once you get ServiceNow approval for your credentials. +Incidents on this page belong to two fields: Mandatory and Optional. ServiceNow's configuration page +determines the type of field and its incidents. Selecting a field and entering a value includes the +incident in ServiceNow's incident report. ![ServiceNow Action Module wizard New Incident page](/images/accessanalyzer/11.6/admin/action/servicenow/incidentcreation.webp) @@ -18,5 +18,5 @@ ServiceNow’s incident report. The ServiceNow account entered on the Authentica which incidents are available within the fields on the Incidents Creation page and are adjusted in ServiceNow. -Fields with a drop-down menu have a set of preconfigured options to select. Fields with ellipsis +Fields with a dropdown menu have a set of preconfigured options to select. Fields with ellipsis choose members from a preconfigured list. diff --git a/docs/accessanalyzer/11.6/admin/action/servicenow/overview.md b/docs/accessanalyzer/11.6/admin/action/servicenow/overview.md index ead5014b23..311504d9ee 100644 --- a/docs/accessanalyzer/11.6/admin/action/servicenow/overview.md +++ b/docs/accessanalyzer/11.6/admin/action/servicenow/overview.md @@ -6,18 +6,18 @@ sidebar_position: 90 # ServiceNow Action Module -The ServiceNow Action Module is primarily intended to allow for the automated creation of ServiceNow -incidents from data collected by the Netwrix suite of data security tools. By facilitating -communication between tools like Enterprise Auditor and ServiceNow’s incident management capability, -security risks in an organization’s environment can not only be identified, but presented to admins, +The ServiceNow Action Module automates the creation of ServiceNow incidents from data collected by +the Netwrix suite of data security tools. By facilitating communication between tools like +Enterprise Auditor and ServiceNow's incident management capability, this module doesn't just +identify security risks in an organization's environment — it also presents them to admins, managers, and other stakeholders in a familiar way, with respect to chains of command and approval as dictated by employee relationships and business workflows implemented in ServiceNow. When account lockouts occur, the Active Directory Inventory Data Collector makes that information available. From the Enterprise Auditor console, the ServiceNow Action Module transmits customized information regarding the locked out accounts directly to those responsible for account management, -alerting them of the issue and requesting that appropriate action is taken to re-enable user -accounts before effected users are aware of the problem. +alerting them of the issue and requesting that they take appropriate action to re-enable user +accounts before affected users become aware of the problem. This section describes the following pages in the configuration wizard. @@ -32,16 +32,16 @@ The ServiceNow Action Module requires an active ServiceNow account with: ## Permissions -The following permissions are required to utilize Enterprise Auditor’s ServiceNow Action Module: +The following permissions are required to use Enterprise Auditor’s ServiceNow Action Module: - ServiceNow admin account – An Administrator Role by an organization’s ServiceNow administrator -- The **Settings** > **ServiceNow** node at the global level can be configured with a credential +- You can configure the **Settings** > **ServiceNow** node at the global level with a credential provisioned to create incidents as Callers in the **Assigned to** field, and any other ServiceNow incident field that references the sys_user table. ## Connecting ServiceNow with Enterprise Auditor -The following instructions can only be performed with a ServiceNow admin account and access to the +You can only perform the following instructions with a ServiceNow admin account and access to the ServiceNow Action Module XML file. ![ServiceNow Action Module XML file in Windows file explorer](/images/accessanalyzer/11.6/admin/action/servicenow/actionmodulexmlfile.webp) @@ -50,23 +50,23 @@ ServiceNow Action Module XML file. `STEALTHbits SN Action Module v1.0_merged_rev2.0` file to use on ServiceNow’s website. **Step 2 –** Visit servicenow.com, sign into the administrator account, expand **System Update -Sets**, and click on **Retrieved Update Sets**. +Sets**, and click **Retrieved Update Sets**. -**Step 3 –** Under **Related Links**, click on **Import Update Set from XML**. +**Step 3 –** Under **Related Links**, click **Import Update Set from XML**. **Step 4 –** Attach the `STEALTHbits SN Action Module v1.0_merged_rev2.0` file, and then click **Upload**. -**Step 5 –** After the file is uploaded, click on the **STEALTHbits SN Action Module** within the +**Step 5 –** After you upload the file, click the **STEALTHbits SN Action Module** within the list of updated sets. -**Step 6 –** Click on the **Preview Update Set** button. Wait until the update set preview is +**Step 6 –** Click the **Preview Update Set** button. Wait until the update set preview is finished and then click **Commit Update Set**. Then, close the Update Set Commit window. **Step 7 –** On the navigation page, expand **System Definitions** and click **Plugins**. Then click on the **Insert Multiple Web Service plugin** -**Step 8 –** Under **Related Links**, click on **Activate/Upgrade** and click **Activate** on the +**Step 8 –** Under **Related Links**, click **Activate/Upgrade** and click **Activate** on the Activate Plugin window. When the Activation is complete, click **Close** to close the window. **Step 9 –** Click **Reload** on the System Plugin page and confirm the Status is Active. diff --git a/docs/accessanalyzer/11.6/admin/action/servicenow/summary.md b/docs/accessanalyzer/11.6/admin/action/servicenow/summary.md index 8ba192aa09..94dae04e3f 100644 --- a/docs/accessanalyzer/11.6/admin/action/servicenow/summary.md +++ b/docs/accessanalyzer/11.6/admin/action/servicenow/summary.md @@ -10,6 +10,5 @@ The Summary page displays a summary of the configured query. ![ServiceNow Action Module wizard Summary page](/images/accessanalyzer/11.6/admin/action/servicenow/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the ServiceNow Action Module Wizard to ensure that no accidental clicks -are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** instead to +close the ServiceNow Action Module Wizard without saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/action/survey/htmlstyle.md b/docs/accessanalyzer/11.6/admin/action/survey/htmlstyle.md index 775af7c781..81e4649296 100644 --- a/docs/accessanalyzer/11.6/admin/action/survey/htmlstyle.md +++ b/docs/accessanalyzer/11.6/admin/action/survey/htmlstyle.md @@ -12,7 +12,7 @@ Choose an HTML style from the HTML Styles list. The Sample pane displays a previ The configurable options are: -- HTML Style List – Select which HTML Style is used for Surveys using the HTML Style list. An - example of the style shows in the Sample box at the bottom of the wizard. +- HTML Style List – Select which HTML Style the survey uses from the HTML Style list. An example of + the style shows in the Sample box at the bottom of the wizard. - Hide and Lock Previous Responses – Select the checkbox to prevent users from changing their survey responses once they exit the survey diff --git a/docs/accessanalyzer/11.6/admin/action/survey/introduction.md b/docs/accessanalyzer/11.6/admin/action/survey/introduction.md index fd076a30d8..3bc6a507c7 100644 --- a/docs/accessanalyzer/11.6/admin/action/survey/introduction.md +++ b/docs/accessanalyzer/11.6/admin/action/survey/introduction.md @@ -10,7 +10,7 @@ Use this page to specify web page introductory text (if any) for the web page sp Server page. See the [Survey: Web Server](/docs/accessanalyzer/11.6/admin/action/survey/webserver.md) topic for additional information. The introductory text appears on the landing page when recipients -click on the survey link in the email. +click the survey link in the email. ![Survey Action Module Wizard Introduction Page](/images/accessanalyzer/11.6/admin/action/survey/introduction.webp) @@ -21,7 +21,7 @@ The configurable options are: are limited to data from the SQL table specified at the Source Table field on the Action Properties page. - Place the cursor in the text where a field should appear. Next, click on the drop-down and + Place the cursor in the text where a field should appear. Next, click the dropdown and select a field from the list. When a selection appears in the field, click the blue down arrow. The field appears in the text. diff --git a/docs/accessanalyzer/11.6/admin/action/survey/mailmessage.md b/docs/accessanalyzer/11.6/admin/action/survey/mailmessage.md index d6fe03f343..af8ec4a920 100644 --- a/docs/accessanalyzer/11.6/admin/action/survey/mailmessage.md +++ b/docs/accessanalyzer/11.6/admin/action/survey/mailmessage.md @@ -13,7 +13,7 @@ not using them. ![Survey Action Module Wizard Mail – Message page](/images/accessanalyzer/11.6/admin/action/survey/mailmessage.webp) Placeholder text displays in the Message box. This text includes a hyperlink to the web page hosting -the survey. Placeholder text can be modified but the link cannot be removed. The link does not +the survey. You can modify the placeholder text, but you can't remove the link. The link doesn't activate until the message is sent. Use the following fields to specify the text of the email: @@ -21,8 +21,8 @@ Use the following fields to specify the text of the email: - Subject – Specify subject text for the email. The contents of this field displays as the Subject line of the delivered email. Enter text directly and use the **Insert field** to insert one or more data fields. This is a required field. -- Insert Field – Inserts a data field into the subject or body of the email. The drop-down menu - displays a list of available fields. Once a selection displays in the field, click on the blue +- Insert Field – Inserts a data field into the subject or body of the email. The dropdown menu + displays a list of available fields. Once a selection displays in the field, click the blue Down and Up arrows to insert the field into the body or the subject, respectively. This field is optional. - The following are buttons appearing on a bar below the Subject field: @@ -33,18 +33,18 @@ Use the following fields to specify the text of the email: the blue arrows to display the SMTP Options dialog box - Preview – Displays the Messages Preview window containing a preview of the current email message. Click **Send** to send a single message to the addresses in the Recipient field in - the Message Preview window. The Preview button is active only if the Recipients field is - populated. See the [Messages Preview Window](#messages-preview-window) topic for additional + the Message Preview window. The Preview button is active only if you populate the Recipients + field. See the [Messages Preview Window](#messages-preview-window) topic for additional information. - Clear Template – Clears any content from the Subject and Text Entry box -- Load from template – Survey templates are a legacy feature. It is strongly recommended not use - templates when creating surveys. +- Load from template – Survey templates are a legacy feature. Netwrix strongly recommends not + using templates when creating surveys. - Save to template – Saves the current email subject and content to a template. If an existing template name appears in the **Load from template** field, clicking this button updates that template. If the **Load from template** field is empty or contains a name other than one of the - existing templates, clicking this button accesses the Save SendMail Template window and changes - can be saved to a new template. Templates reside locally on the host computer as XML files, in the + existing templates, clicking this button opens the Save SendMail Template window and saves the + changes to a new template. Templates reside locally on the host computer as XML files, in the `Actions/SM_Templates` folder. ## Messages Preview Window diff --git a/docs/accessanalyzer/11.6/admin/action/survey/mailproperties.md b/docs/accessanalyzer/11.6/admin/action/survey/mailproperties.md index 97bb5860a7..8e90dd4a41 100644 --- a/docs/accessanalyzer/11.6/admin/action/survey/mailproperties.md +++ b/docs/accessanalyzer/11.6/admin/action/survey/mailproperties.md @@ -14,10 +14,10 @@ Use the following fields to specify the recipient information: - Recipient column – Specify the data table columns containing intended recipient information - - For example, a column containing email addresses. The drop-down menu displays a list of + - For example, a column containing email addresses. The dropdown menu displays a list of possible column types. -- Recipient type – Specify the data type of the Recipient column. The drop-down menu displays a list +- Recipient type – Specify the data type of the Recipient column. The dropdown menu displays a list of recipient types, for example **SMTP email address**. - Carbon copy (CC) – (Optional) Specify one or more additional email addresses to receive a carbon-copy of the SendMail message, for example an address not included in the source table. diff --git a/docs/accessanalyzer/11.6/admin/action/survey/overview.md b/docs/accessanalyzer/11.6/admin/action/survey/overview.md index b43afe14a6..ef88a4f2e2 100644 --- a/docs/accessanalyzer/11.6/admin/action/survey/overview.md +++ b/docs/accessanalyzer/11.6/admin/action/survey/overview.md @@ -10,21 +10,21 @@ Use this action module to create surveys and make them available to targeted rec For example, a survey can solicit feedback from clients or poll employees on company issues. The Survey Action Module Wizard builds customizable, web-based surveys containing questions created -by the user. Once the survey is defined, a list of recipients can then be specified. When executing +by the user. After you define the survey, you can specify a list of recipients. When executing the action, the process simultaneously sends an email to the recipients containing a link to the survey and creates a web page to host the survey. :::warning -This module sends one or more electronic messages to a selected audience. Prior to -executing the action, ensure the audience consists of only the desired members. Netwrix recommends +This module sends one or more electronic messages to a selected audience. Before +executing the action, ensure the audience consists of only the members you want. Netwrix recommends using this and all other Enterprise Auditor actions with caution. ::: ## Survey Action Source Table Configuration -All data tables used in Enterprise Auditor action modules require the presence of certain data -columns. In addition, individual action modules including Survey may have their own column +All data tables used in Enterprise Auditor action modules require certain data columns. In +addition, individual action modules including Survey may have their own column requirements. The Survey action module requires a column containing well-formatted email addresses (for example, `hfinn@netwrix.com`) for your recipients. diff --git a/docs/accessanalyzer/11.6/admin/action/survey/questions.md b/docs/accessanalyzer/11.6/admin/action/survey/questions.md index 6c0c74d4ff..48ccf382d3 100644 --- a/docs/accessanalyzer/11.6/admin/action/survey/questions.md +++ b/docs/accessanalyzer/11.6/admin/action/survey/questions.md @@ -39,7 +39,7 @@ The configurable options are: available: - Text – Specify the survey question - - Subjects – Click on the ellipses (**…**) to open the Select subjects window. Specify the + - Subjects – Click the ellipses (**…**) to open the Select subjects window. Specify the object to which a question is directed. The selected subjects show in the Subjects field. See the [Select Subjects Window](#select-subjects-window) topic for additional information. - Answer Column Name – The Survey action module inserts the results of the survey directly into @@ -49,11 +49,11 @@ The configurable options are: - Yes/No - Text - - Multiple Choice – If this option is selected, the **Answers** button activates. Click this + - Multiple Choice – If you select this option, the **Answers** button activates. Click this button to open the Answers window and specify the response options to the multiple choice question via the **Add** button. - - Answers – This button activates if Multiple Choice in the Question Type field is selected. + - Answers – This button activates if you select Multiple Choice in the Question Type field. Click to access the Answers window. - Description – Specify any additional explanation of the survey question. The text appears on the survey below the associated question. diff --git a/docs/accessanalyzer/11.6/admin/action/survey/testsurvey.md b/docs/accessanalyzer/11.6/admin/action/survey/testsurvey.md index 57d40c4694..8fe2056200 100644 --- a/docs/accessanalyzer/11.6/admin/action/survey/testsurvey.md +++ b/docs/accessanalyzer/11.6/admin/action/survey/testsurvey.md @@ -13,6 +13,6 @@ Use this page to test a survey and verify proper configuration. The configurable options are: - Start test – Click to test your survey configuration -- Survey full test – Once the survey configuration test passes inspection, a full survey can be - tested against a single user (for example, your own email account) to verify a survey matches +- Survey full test – After the survey configuration test passes inspection, test a full survey + against a single user (for example, your own email account) to verify a survey matches design criteria diff --git a/docs/accessanalyzer/11.6/admin/action/webrequest/destination.md b/docs/accessanalyzer/11.6/admin/action/webrequest/destination.md index e38789132c..a85a58af94 100644 --- a/docs/accessanalyzer/11.6/admin/action/webrequest/destination.md +++ b/docs/accessanalyzer/11.6/admin/action/webrequest/destination.md @@ -12,7 +12,7 @@ Use the Destination page to specify all settings for the destination of the web Use the following categories to establish the location of the web request: -- Insert field – Select a field using the drop-down menu +- Insert field – Select a field using the dropdown menu :::note The fields available varies based on the source table columns. @@ -41,12 +41,12 @@ Use the following categories to establish the location of the web request: - Resource – URL destination to send the data via the web request - - Select a field using the drop-down menu, place the cursor in the Resource textbox, and click + - Select a field using the dropdown menu, place the cursor in the Resource textbox, and click the blue down-arrow to add it to the Resource box - Manually enter a resource in the textbox :::note - A red circle with an x indicates that the Resource field cannot be empty. + A red circle with an x indicates that the Resource field can't be empty. ::: @@ -56,17 +56,17 @@ Use the following categories to establish the location of the web request: - Basic – Basic authentication - JWT – JSON Web Token, a URL-safe authentication method - Basic and JWT authentications are pulled from the credential profile set in the job. It inserts - that data into the authentication header of the web request with the proper format expected (for + The action pulls Basic and JWT authentications from the credential profile set in the job. It + inserts that data into the authentication header of the web request with the proper format expected (for example, Basic [Base64 encoded credentials] or Bearer [JWT token] for Basic and JWT authentication respectively). **Test Connection** -- Drop-down menu – Select a method to test. Currently locked to GET. +- dropdown menu – Select a method to test. locked to GET. - URI textbox – Input the resource to receive the test message - - Select a field using the drop-down menu, place the cursor in text area, and click the blue + - Select a field using the dropdown menu, place the cursor in text area, and click the blue down-arrow to add it to the URI textbox - Manually enter a resource in the field diff --git a/docs/accessanalyzer/11.6/admin/action/webrequest/header.md b/docs/accessanalyzer/11.6/admin/action/webrequest/header.md index b8d3ce0bab..b420fbc573 100644 --- a/docs/accessanalyzer/11.6/admin/action/webrequest/header.md +++ b/docs/accessanalyzer/11.6/admin/action/webrequest/header.md @@ -12,7 +12,7 @@ Use the Header page to enter the header values for the request. Use the following options to enter header values: -- Insert field – Select a field to include in the request using the drop-down menu +- Insert field – Select a field to include in the request using the dropdown menu :::note The fields available varies based on the source table columns. @@ -26,6 +26,6 @@ Use the following options to enter header values: - Key / Value fields – The name or value of the attribute - - Select a field using the drop-down menu, place the cursor in the cell of the desired Key or - Value, and click the blue down-arrow to add it to the selected cell + - Select a field using the dropdown menu, place the cursor in the cell of the Key or + Value you want, and click the blue down-arrow to add it to the selected cell - Manually enter a field in the cell diff --git a/docs/accessanalyzer/11.6/admin/action/webrequest/overview.md b/docs/accessanalyzer/11.6/admin/action/webrequest/overview.md index 54573a24d5..21d1ed2e61 100644 --- a/docs/accessanalyzer/11.6/admin/action/webrequest/overview.md +++ b/docs/accessanalyzer/11.6/admin/action/webrequest/overview.md @@ -7,12 +7,12 @@ sidebar_position: 110 # WebRequest Action Module The Web Request action module provides methods of applying bulk changes to REST endpoints. At this -stage, target endpoints should be identified to invoke web requests against. This wizard allows the -definition of requests to perform. +stage, identify target endpoints to invoke web requests against. This wizard lets you define the +requests to perform. :::warning -Ensure that only the changes required are applied and only those target systems desired -when using this action module. +Apply only the changes you need, and only to the target systems you intend, when using this +action module. ::: diff --git a/docs/accessanalyzer/11.6/admin/action/webrequest/parameters.md b/docs/accessanalyzer/11.6/admin/action/webrequest/parameters.md index bff375e905..3935b8c2e5 100644 --- a/docs/accessanalyzer/11.6/admin/action/webrequest/parameters.md +++ b/docs/accessanalyzer/11.6/admin/action/webrequest/parameters.md @@ -12,7 +12,7 @@ Use the Parameters page to enter the parameter values. Enter parameter values using the following options: -- Insert Field – Select a field to include in the request from the drop-down menu. +- Insert Field – Select a field to include in the request from the dropdown menu. :::note The fields available varies based on the source table. @@ -36,8 +36,8 @@ Enter parameter values using the following options: - Key / Value Fields – The name or value of the attribute - - Select a field using the drop-down menu, place the cursor in the cell of the desired Key or - Value, and click the blue down-arrow to add it to the selected cell + - Select a field using the dropdown menu, place the cursor in the cell of the Key or + Value you want, and click the blue down-arrow to add it to the selected cell - Select a cell and click the green circle with plus sign to open the Custom Attribute Editor window and add the attribute to the cell - Manually enter a field in the cell @@ -51,16 +51,16 @@ and advanced functions. Create custom attributes using the following options: -- Insert field – Select a field to insert using the drop-down menu -- Unique name – Name of the custom attribute that will be created +- Insert field – Select a field to insert using the dropdown menu +- Unique name – Name of the custom attribute to create - - Select a field using the drop-down menu, place the cursor in the Unique name textbox, and + - Select a field using the dropdown menu, place the cursor in the Unique name textbox, and click the blue down-arrow to add it to the Unique name textbox - Manually enter the name - Data – The actual value of the custom attribute (can be database value or manually specified) - - Select a field using the drop-down menu, place the cursor in the Data textbox, and click the + - Select a field using the dropdown menu, place the cursor in the Data textbox, and click the blue down-arrow to add it to the Data textbox - Manually enter the data diff --git a/docs/accessanalyzer/11.6/admin/action/webrequest/summary.md b/docs/accessanalyzer/11.6/admin/action/webrequest/summary.md index aad9c73ae4..8246cbdf52 100644 --- a/docs/accessanalyzer/11.6/admin/action/webrequest/summary.md +++ b/docs/accessanalyzer/11.6/admin/action/webrequest/summary.md @@ -10,6 +10,5 @@ The Summary page displays a summary of the configured action. ![Web Request Action Module Wizard Summary page](/images/accessanalyzer/11.6/admin/action/webrequest/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Web Request Action Module Wizard to ensure that no accidental clicks -are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** instead to +close the Web Request Action Module Wizard without saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/analysis/autoaction.md b/docs/accessanalyzer/11.6/admin/analysis/autoaction.md index d15a206db6..df0b1f9f23 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/autoaction.md +++ b/docs/accessanalyzer/11.6/admin/analysis/autoaction.md @@ -19,13 +19,12 @@ topic for additional information. ## Select Action Window -The Select Action window lists the actions that currently exist within the Job that can be selected +The Select Action window lists the actions that exist within the Job that you can select to automatically run upon job execution. ![Select Action Window](/images/accessanalyzer/11.6/admin/analysis/autoaction.webp) Select an action from the list. Click **OK** to exit the window, and then click **Save** to preserve -the changes made to the analysis module. The action now executes as part of the analysis task. If no -actions were selected, it is best practice to click **Cancel** to close the Select Action window to -ensure no accidental selections are saved. Actions only display if they exist within the Actions -node of the current Job. +the changes made to the analysis module. The action now executes as part of the analysis task. If you selected no actions, click **Cancel** +instead to close the Select Action window without saving accidental selections. Actions only +display if they exist within the Actions node of the current Job. diff --git a/docs/accessanalyzer/11.6/admin/analysis/businessrules/appliesto.md b/docs/accessanalyzer/11.6/admin/analysis/businessrules/appliesto.md index 3ac22ba524..8fb875ef70 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/businessrules/appliesto.md +++ b/docs/accessanalyzer/11.6/admin/analysis/businessrules/appliesto.md @@ -6,9 +6,9 @@ sidebar_position: 30 # Applies To Tab -Use the Applies To tab to specify the scope for application of the analysis rules. Rules are applied -to data collected from all hosts, from specific hosts, or from the specific host running the job -(local data). Data is filtered based on a specified time window. +Use the Applies To tab to specify the scope for application of the analysis rules. The analysis +module applies rules to data collected from all hosts, from specific hosts, or from the specific +host running the job (local data). It filters data based on a specified time window. ![Edit Rules window Applies To tab](/images/accessanalyzer/11.6/admin/analysis/businessrules/appliesto.webp) @@ -20,17 +20,17 @@ The Applies To tab provides the following options: - All Source Data – Select this option to run the action using all data - Source Data from this Console only – Select this option to run the action specifically using data from only this Enterprise Auditor console - - Time Window for source table – Use the drop-down menu to specify a time window from the + - Time Window for source table – Use the dropdown menu to specify a time window from the following options: - Most recent data – Use only the most recently collected data - Cumulative data for offline hosts – Use data collected from offline hosts - Most recent data filtering duplicate and offline hosts – Use most recent data excluding duplicate and offline hosts - - Do not filter data – Use unfiltered data + - Don't filter data – Use unfiltered data - Hosts Filtering – Specify source hosts - Apply to All Hosts – Select this checkbox to use all hosts to query - - Host List – Select any desired hosts to query. If **Apply to All Hosts** is selected, the list + - Host List – Select any desired hosts to query. If you select **Apply to All Hosts**, the list is unavailable. diff --git a/docs/accessanalyzer/11.6/admin/analysis/businessrules/logic.md b/docs/accessanalyzer/11.6/admin/analysis/businessrules/logic.md index c044f64a45..eed0ad6e1d 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/businessrules/logic.md +++ b/docs/accessanalyzer/11.6/admin/analysis/businessrules/logic.md @@ -16,7 +16,7 @@ The Logic tab contains the following sections and options: - Rule Name – The field defaults with the name on the Analysis Properties page and is manually editable - - Table – Select a table from the drop-down menu containing the baseline values to evaluate + - Table – Select a table from the dropdown menu containing the baseline values to evaluate - To view data from a selected table, click the ellipsis (**…**) to open the Sample Data Viewer window, or select a table within the viewer. See the @@ -48,20 +48,20 @@ Use the Sample Data Viewer window to examine data in a selected table. The Sample Data Viewer window provides the following options: -- Use the drop-down menu to select a table to view the table’s data. The field defaults with the +- Use the dropdown menu to select a table to view the table’s data. The field defaults with the table selected in the Logic tab if previously selected. -- Show First [Number] rows – Adjusts the presentation of the number of rows of the selected table. - The default value is 50. It can be manually adjusted with values between 0 and all. +- Show First [Number] rows – Sets how many rows of the selected table to show. The default value is + 50. You can manually adjust it to any value between 0 and all. ## EditConditionsForm Window -Use the EditConditionsForm to configure conditions to be applied to the table. +Use the EditConditionsForm to configure conditions to apply to the table. ![EditConditionsForm Window](/images/accessanalyzer/11.6/admin/analysis/businessrules/editconditionsform.webp) The EditConditionsForm contains the following options: -- Column – Use the drop-down menu to select a column from the table selected in the Logic tab +- Column – Use the dropdown menu to select a column from the table selected in the Logic tab - Operator – Use the dropdown to select an operator: - `<` – Search for items in the selected column with values less than a selected value @@ -101,14 +101,14 @@ The Configure Scorecard Options window provides the following options: - Action Name – Enter a name for the action - Description – Enter a description for the action -- Action Classification – This section allows you to group scorecard action results for reporting +- Action Classification – Use this section to group scorecard action results for reporting purposes - Category – Enter a desired category name in the field or use the dropdown to select from previously titled categories - Index – Enter a desired index value for the scorecard action -- Action Score – This section allows you to rank the action’s importance relative to other scorecard +- Action Score – Use this section to rank the action’s importance relative to other scorecard actions - Score – Enter a desired score value for the scorecard action @@ -119,9 +119,9 @@ The Configure Scorecard Options window provides the following options: - Knowledge – Enter information to assist issue resolution, for example a website URL -- Captured Values – This section allows you to select up to five optional properties whose values - will be captured and stored with the scorecard entry. For each property selected, a name column - and value column appear in the scorecard. +- Captured Values – Use this section to select up to five optional properties. The scorecard entry + captures and stores the values of the properties you select. For each property selected, a name + column and value column appear in the scorecard. - - Property [1-5] – Select a property from the selected table using the drop-down menu to capture + - Property [1-5] – Select a property from the selected table using the dropdown menu to capture and store its values with the scorecard diff --git a/docs/accessanalyzer/11.6/admin/analysis/businessrules/overview.md b/docs/accessanalyzer/11.6/admin/analysis/businessrules/overview.md index b44ad6870c..27792be297 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/businessrules/overview.md +++ b/docs/accessanalyzer/11.6/admin/analysis/businessrules/overview.md @@ -17,10 +17,10 @@ original baseline expectations. ## Scorecard -Business Rules analysis module results are displayed in a table called a scorecard. The scorecard -determines which of the rules are applied, and in what order. A scorecard table contains only +A table called a scorecard displays Business Rules analysis module results. The scorecard +determines which rules apply, and in what order. A scorecard table contains only exceptions and deviations from the business rule criteria when compared to a baseline value. The -table does not include matches to the criteria. All scorecard table names are suffixed with +table doesn't include matches to the criteria. All scorecard table names are suffixed with `_SCORECARD` for easy identification. ## Edit Rules Window diff --git a/docs/accessanalyzer/11.6/admin/analysis/changedetection/additionalfields.md b/docs/accessanalyzer/11.6/admin/analysis/changedetection/additionalfields.md index 9d8751be77..809f7df89e 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/changedetection/additionalfields.md +++ b/docs/accessanalyzer/11.6/admin/analysis/changedetection/additionalfields.md @@ -7,7 +7,7 @@ sidebar_position: 50 # Change Detection: Additional Fields Use the Additional Fields page to choose any additional fields to include with the change analysis. -These fields do not detect change, but may provide additional information to help diagnose and +These fields don't detect change, but may provide additional information to help diagnose and analyze the changes reported. ![Change Detection Data Analysis Module wizard Additional Fields page](/images/accessanalyzer/11.6/admin/analysis/changedetection/additionalfields.webp) diff --git a/docs/accessanalyzer/11.6/admin/analysis/changedetection/input.md b/docs/accessanalyzer/11.6/admin/analysis/changedetection/input.md index 48061695ae..96091e8c06 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/changedetection/input.md +++ b/docs/accessanalyzer/11.6/admin/analysis/changedetection/input.md @@ -12,10 +12,9 @@ Use the Input Data Source page to choose a data source to analyze for changes. The configurable option is: -- Please select a data source – Select a data source table from the list +- select a data source – Select a data source table from the list :::note - The selectable data sources change based on which option is selected on the Input + The selectable data sources change based on which option you select on the Input Scope page. - ::: diff --git a/docs/accessanalyzer/11.6/admin/analysis/changedetection/inputscope.md b/docs/accessanalyzer/11.6/admin/analysis/changedetection/inputscope.md index 9bfe2ee296..81a1e996f0 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/changedetection/inputscope.md +++ b/docs/accessanalyzer/11.6/admin/analysis/changedetection/inputscope.md @@ -12,12 +12,11 @@ Use the Input Scope page to specify the input scope of the data source. Identify the scope of the data source from the following options: -- Tables from Current Job – Select tables from only the currently selected job +- Tables from Current Job – Select tables from only the selected job - All Enterprise Auditor Tables – Select from all Enterprise Auditor tables within the SQL Server database - All tables in the database – Select all tables within the SQL Server database :::note -This selection affects the tables that are available for selection on the Input page. - +This selection affects which tables are available on the Input page. ::: diff --git a/docs/accessanalyzer/11.6/admin/analysis/changedetection/options.md b/docs/accessanalyzer/11.6/admin/analysis/changedetection/options.md index 325265b03c..039eed919c 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/changedetection/options.md +++ b/docs/accessanalyzer/11.6/admin/analysis/changedetection/options.md @@ -13,7 +13,7 @@ made within a certain time period, or only changes between the last two runs of Configure the additional options using the following: -- Save change detection results for xx days – Modify the number of days that results for the Change - Detection task are saved for +- Save change detection results for xx days – Modify the number of days the action saves results + for the Change Detection task - Only save most recent change (per unique key) – Select the checkbox to only save changes between the last two runs of the source set diff --git a/docs/accessanalyzer/11.6/admin/analysis/changedetection/overview.md b/docs/accessanalyzer/11.6/admin/analysis/changedetection/overview.md index 418bd1bf02..24cdca0dc5 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/changedetection/overview.md +++ b/docs/accessanalyzer/11.6/admin/analysis/changedetection/overview.md @@ -12,8 +12,8 @@ selected data items and compares result rows from previous collection activity w most recent collection. This module compares values collected for two different query instances. Therefore, as change -detection depends on the existence of a **JobRunTimeKey**, history must be enabled and data -collected at least twice to produce the desired results. Configure History settings under the job’s +detection depends on the existence of a **JobRunTimeKey**, you must enable history and collect data +at least twice to produce the results you want. Configure History settings under the job’s **Settings** > **History** node. See the [History](/docs/accessanalyzer/11.6/admin/settings/history.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/admin/analysis/changedetection/summary.md b/docs/accessanalyzer/11.6/admin/analysis/changedetection/summary.md index 346789e8d2..e2b5ef7480 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/changedetection/summary.md +++ b/docs/accessanalyzer/11.6/admin/analysis/changedetection/summary.md @@ -10,5 +10,5 @@ The Summary page summarizes the configuration of the action. ![Change Detection Data Analysis Module wizard Summary page](/images/accessanalyzer/11.6/admin/analysis/changedetection/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, click **Cancel** to close -the Change Detection Data Analysis Module wizard to ensure no accidental configurations are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** instead to +close the Change Detection Data Analysis Module wizard without saving accidental configurations. diff --git a/docs/accessanalyzer/11.6/admin/analysis/notification/changetype.md b/docs/accessanalyzer/11.6/admin/analysis/notification/changetype.md index 35b8327d27..649e3b41c5 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/notification/changetype.md +++ b/docs/accessanalyzer/11.6/admin/analysis/notification/changetype.md @@ -7,8 +7,8 @@ sidebar_position: 30 # Notification: Change Type Use the Select Change Type page to choose the types of changes for which to trigger a notification. -The selections on this page are optional. This page is only active if Change Detection Table is -selected on the Table Type page. +The selections on this page are optional. This page is only active if you select Change Detection +Table on the Table Type page. ![Notification Data Analysis Module wizard Select Change Type page](/images/accessanalyzer/11.6/admin/analysis/notification/changetype.webp) diff --git a/docs/accessanalyzer/11.6/admin/analysis/notification/commandline.md b/docs/accessanalyzer/11.6/admin/analysis/notification/commandline.md index 156c69eebd..568eb64599 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/notification/commandline.md +++ b/docs/accessanalyzer/11.6/admin/analysis/notification/commandline.md @@ -6,8 +6,8 @@ sidebar_position: 80 # Notification: Command Line -The Command Line properties page is available when the Command-line Executable notification type is -selected on the Type page. +The Command Line properties page is available when you select the Command-line Executable +notification type on the Type page. ![Notification Data Analysis Module wizard Command Line properties page](/images/accessanalyzer/11.6/admin/analysis/notification/commandline.webp) @@ -17,7 +17,7 @@ The following options are available: view and select from a list of executable files. - Arguments – If required, specify command line inputs for the application in the text box. If the argument must come from a value in the database (for example, a timeout value), insert it here via - the Fields drop-down menu above. + the Fields dropdown menu above. - - Fields – To pass one or more fields into the command line arguments, click the drop-down menu, + - Fields – To pass one or more fields into the command line arguments, click the dropdown menu, select a field from the lists, and click **Add** diff --git a/docs/accessanalyzer/11.6/admin/analysis/notification/criteria.md b/docs/accessanalyzer/11.6/admin/analysis/notification/criteria.md index 41576a795e..42d4c534a3 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/notification/criteria.md +++ b/docs/accessanalyzer/11.6/admin/analysis/notification/criteria.md @@ -12,8 +12,8 @@ Use the Notification Criteria page to specify criteria to trigger a notification The following options are available: -- No Criteria – Set no criteria to trigger a notification if any property changes. If selected, any - row will trigger the notification. +- No Criteria – Set no criteria to trigger a notification if any property changes. If you select + this option, any row triggers the notification. - Simple Criteria – Select criteria to send a notification based on the value of a specific property or column in the database. The trigger can be if the property or column value is greater than, equal to, or less than the value provided. diff --git a/docs/accessanalyzer/11.6/admin/analysis/notification/eventlog.md b/docs/accessanalyzer/11.6/admin/analysis/notification/eventlog.md index 3ba486b98a..d387675c80 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/notification/eventlog.md +++ b/docs/accessanalyzer/11.6/admin/analysis/notification/eventlog.md @@ -6,7 +6,7 @@ sidebar_position: 90 # Notification: Event Log -The Event Log properties page is available when the Event log notification type is selected on the +The Event Log properties page is available when you select the Event log notification type on the Type page. Use this page to specify the type of event, the event ID, and the description for the event. @@ -15,7 +15,7 @@ event. The following options are available: - Log – The event log name is Enterprise Auditor -- Type – Specify the log type. The drop-down menu displays the following options: +- Type – Specify the log type. The dropdown menu displays the following options: - Information - Warning @@ -26,5 +26,5 @@ The following options are available: - Event ID – Specify the event ID - Description – Enter a description of the event - - Fields – To pass fields into the description, click on the drop-down list, select a field from + - Fields – To pass fields into the description, click the dropdown list, select a field from the list, then click **Add** diff --git a/docs/accessanalyzer/11.6/admin/analysis/notification/hosts.md b/docs/accessanalyzer/11.6/admin/analysis/notification/hosts.md index ca41f15f33..4e1a3fa961 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/notification/hosts.md +++ b/docs/accessanalyzer/11.6/admin/analysis/notification/hosts.md @@ -16,11 +16,11 @@ The following options are available: - I want notifications sent only for the hosts listed below - I want notifications sent for all hosts except the ones listed below -If the first option is selected, the host list selection window is not enabled. If either the second -or third option is selected, the following options are enabled: +If you select the first option, the host list selection window isn't enabled. If you select either +the second or third option, the wizard enables the following options: -- Show me all host lists – Activates the host list selection window, from which individual host - lists can be selected -- Enter hosts manually – Manually enter specific host names. Once the name is entered, click the add - (**+**) button to add it to the selection box. Ensure the checkbox next to the host name is - selected to include it in the list of hosts. +- Show me all host lists – Activates the host list selection window, from which you can select + individual host lists +- Enter hosts manually – Manually enter specific host names. After you enter the name, click the add + (**+**) button to add it to the selection box. Select the checkbox next to the host name to + include it in the list of hosts. diff --git a/docs/accessanalyzer/11.6/admin/analysis/notification/overview.md b/docs/accessanalyzer/11.6/admin/analysis/notification/overview.md index 039a4dad2e..518fccf625 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/notification/overview.md +++ b/docs/accessanalyzer/11.6/admin/analysis/notification/overview.md @@ -6,7 +6,7 @@ sidebar_position: 40 # Notification Analysis Module -The Notification Data analysis module provides the ability to send an email or command-line +The Notification Data analysis module lets you send an email or command-line notification to selected targets based on the values contains in any table. The Notification Data Analysis Module has the following prerequisites: diff --git a/docs/accessanalyzer/11.6/admin/analysis/notification/smtp.md b/docs/accessanalyzer/11.6/admin/analysis/notification/smtp.md index 10d4aaecb2..dcf64a399e 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/notification/smtp.md +++ b/docs/accessanalyzer/11.6/admin/analysis/notification/smtp.md @@ -6,7 +6,7 @@ sidebar_position: 70 # Notification: SMTP -The SMTP properties page is available when the Email notification type is selected on the Type page. +The SMTP properties page is available when you select the Email notification type on the Type page. Use this page to specify SMTP notification properties, including recipients, subject line, and email body. @@ -24,13 +24,13 @@ The following options are available: - Subject – Specify a subject for the email. The subject can include field variables. :::info - If configuring a Notification analysis module for a pre-configured job, it is - recommended not to change the existing field variables. + If you're configuring a Notification analysis module for a pre-configured job, avoid + changing the existing field variables. ::: - Insert Field – Select a source data column to add to the message body or subject line. Click the - drop-down to see a list of columns. Once the column displays in the field, click an arrow to + dropdown to see a list of columns. After the column displays in the field, click an arrow to insert the field. - Down arrow – Adds the selected source column to the message text @@ -39,9 +39,9 @@ The following options are available: - Embed HTML Report – Embed a HTML report in the notification email. Click the Embed HTML Report button to navigate to the HTML file. - Show sample input source data – Opens the Sample Source Data window, containing sample input - source data as it currently exists in the database -- Show dialog to set SMTP options – Opens the SMTP Options window, where SMTP global settings can be - overwritten through manual configuration + source data as it exists in the database +- Show dialog to set SMTP options – Opens the SMTP Options window, where you can manually overwrite + SMTP global settings - Preview – Displays a preview of the email. :::note @@ -49,9 +49,9 @@ The following options are available: ::: -- Clear Template – Clears all data from the subject and message boxes. Does not clear e-mail +- Clear Template – Clears all data from the subject and message boxes. Doesn't clear e-mail addresses. - Text Box – Specify the text of the email message. The toolbar above the text box contains various icons providing access to text editing and formatting tools. To insert fields from Enterprise - Auditor, choose a field from the drop-down menu and click the Down arrow. Block tag formatting is + Auditor, choose a field from the dropdown menu and click the Down arrow. Block tag formatting is supported. diff --git a/docs/accessanalyzer/11.6/admin/analysis/notification/summary.md b/docs/accessanalyzer/11.6/admin/analysis/notification/summary.md index a9661f29ef..b35cef6dda 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/notification/summary.md +++ b/docs/accessanalyzer/11.6/admin/analysis/notification/summary.md @@ -11,6 +11,5 @@ previous pages of the wizard. ![Notification Data Analysis Module wizard Summary page](/images/accessanalyzer/11.6/admin/analysis/notification/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is best practice to -click **Cancel** to close the Notification Data Analysis Module wizard to ensure no accidental -clicks are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** instead to +close the Notification Data Analysis Module wizard without saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/analysis/notification/timewindow.md b/docs/accessanalyzer/11.6/admin/analysis/notification/timewindow.md index e2cdd181bf..6dcb42d167 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/notification/timewindow.md +++ b/docs/accessanalyzer/11.6/admin/analysis/notification/timewindow.md @@ -16,7 +16,7 @@ The following option is available: task to the most recent data :::note - The checkbox is only enabled if the table selected on the Select Table page has a - Enterprise Auditor **JobRunTimeKey** property. Otherwise, the checkbox is cleared by default. + Enterprise Auditor enables the checkbox only if the table selected on the Select Table page has + a **JobRunTimeKey** property. Otherwise, it clears the checkbox by default. ::: diff --git a/docs/accessanalyzer/11.6/admin/analysis/overview.md b/docs/accessanalyzer/11.6/admin/analysis/overview.md index 2c03bb784f..b3a4923538 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/overview.md +++ b/docs/accessanalyzer/11.6/admin/analysis/overview.md @@ -6,17 +6,17 @@ sidebar_position: 90 # Analysis Modules -The Enterprise Auditor analysis modules are capable of finding unique data and notifying users of -its location from a variety of environments. Analysis modules are assigned to a job at the -**Configure** > **Analysis** node. See the +The Enterprise Auditor analysis modules find unique data and notify users of its location from a +variety of environments. Assign analysis modules to a job at the **Configure** > **Analysis** node. +See the [Analysis Node](/docs/accessanalyzer/11.6/admin/jobs/job/configure/analysis/analysis.md) topic for information on the Analysis Selection view. ![Configure an analysis](/images/accessanalyzer/11.6/admin/analysis/configure.webp) -Analysis tasks are configured through the Analysis Properties page. Navigate to the job’s -**Configure** > Analysis node. The Analysis Properties page is opened from the Analysis Selection -page by either of the following options: +Configure analysis tasks through the Analysis Properties page. Navigate to the job’s +**Configure** > Analysis node. Open the Analysis Properties page from the Analysis Selection +page using either of the following options: - Select **Create Analysis** to add a new analysis task to a job - Select an existing analysis and click **Analysis Properties** to modify its configuration @@ -30,7 +30,7 @@ Auditor. | Analysis Module | Description | | --------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- | | [AutoAction Analysis Module](/docs/accessanalyzer/11.6/admin/analysis/autoaction.md) | Performs a specified action at the conclusion of an analysis task’s execution | -| [Business Rules Analysis Module](/docs/accessanalyzer/11.6/admin/analysis/businessrules/overview.md) | Finds data that does not match user expectations for the target environment | +| [Business Rules Analysis Module](/docs/accessanalyzer/11.6/admin/analysis/businessrules/overview.md) | Finds data that doesn't match user expectations for the target environment | | [Change Detection Analysis Module](/docs/accessanalyzer/11.6/admin/analysis/changedetection/overview.md) | Notifies when a change occurs in the results of a job and identifies the location of the change | | [Notification Analysis Module](/docs/accessanalyzer/11.6/admin/analysis/notification/overview.md) | Sends notifications to specified recipients when a specified event occurs | | [SQLscripting Analysis Module](/docs/accessanalyzer/11.6/admin/analysis/sqlscripting.md) | Executes free-form SQL scripts | @@ -41,16 +41,16 @@ Auditor. ## Executing Analyses Analysis tasks execute automatically if enabled through the Analysis Selection page for jobs with -analysis modules configured. Analysis tasks can be enabled or disabled by selecting the checkbox -next to the analysis tasks. Analysis tasks execute in the order shown in the Analysis Selection -window. Tasks can be manually executed without running the job by right-clicking on the task and -selecting **Execute Analyses** from the dropdown menu. +analysis modules configured. Select the checkbox next to an analysis task to enable or disable it. +Analysis tasks execute in the order shown in the Analysis Selection window. To run a task manually +without running the job, right-click the task and select **Execute Analyses** from the dropdown +menu. ## Analysis Selection Page -Analysis tasks can be created, deleted, and configured through the Analysis Selection page. For jobs -with existing analysis tasks, the Analysis Selection page is used to change the order in which tasks -are run, as well as enabling or disabling tasks. +Use the Analysis Selection page to create, delete, and configure analysis tasks. For jobs +with existing analysis tasks, use the Analysis Selection page to change the run order and to enable +or disable tasks. ![Analysis Selection Page](/images/accessanalyzer/11.6/admin/analysis/analysisselectionpage.webp) @@ -78,8 +78,8 @@ The Analysis Selection page has the following options: ## Analysis Properties Page -Configure task properties through the Analysis Properties page. The Analysis Properties page is -accessed through the Analysis Selection page. +Configure task properties through the Analysis Properties page. Access the Analysis Properties page +through the Analysis Selection page. ![Analysis Properties Page](/images/accessanalyzer/11.6/admin/analysis/analysispropertiespage.webp) @@ -88,7 +88,7 @@ The Analysis Properties page has the following options: - Name – Name of the analysis task. Default names can be changed. - Description – Description of the analysis task. Analysis tasks for default solutions reference associate data tables. Descriptions for new tasks are blank by default. -- Analysis Module – Click the drop-down to select an analysis module for the task +- Analysis Module – Click the dropdown to select an analysis module for the task - Configure Analysis – Click to access the configuration wizard for the selected analysis module - ID – Unique identifying number of the analysis task. The database uses distinct IDs to distinguish between analysis tasks, even those with identical configurations. diff --git a/docs/accessanalyzer/11.6/admin/analysis/sqlscripting.md b/docs/accessanalyzer/11.6/admin/analysis/sqlscripting.md index 92fb473daa..3bf32af20a 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/sqlscripting.md +++ b/docs/accessanalyzer/11.6/admin/analysis/sqlscripting.md @@ -12,7 +12,7 @@ Use the SQLscripting analysis module to apply SQL scripting to the selected job. The SQLscripting analysis module evaluates the Enterprise Auditor user’s permission level to determine whether to allow the connected user to run the scripted command. Since this evaluation is -based on specific SQL database permissions and is not always under Enterprise Auditor’s control, +based on specific SQL database permissions and isn't always under Enterprise Auditor’s control, some scripts with correct syntax may fail due to insufficient permissions. The SQL Script Editor window has the following options: @@ -25,13 +25,13 @@ The SQL Script Editor window has the following options: - Syntax Check – Checks SQL script syntax - - Syntax Check does not identify logic errors, only instances where syntax is incorrect. Click + - Syntax Check doesn't identify logic errors, only instances where syntax is incorrect. Click **Syntax Check** to open the Script Errors window which identifies syntax errors. - Syntax Check reports back syntax errors starting from the beginning of the script to the end. - Syntax Check does not return a list of errors. + Syntax Check doesn't return a list of errors. -- Load file – Opens a File Explorer which can be used to navigate to a SQL file -- Save to File – Saves the currently configured script into a SQL file +- Load file – Opens a File Explorer window you can use to navigate to a SQL file +- Save to File – Saves the configured script into a SQL file - Undo – Undo the previous changes made to script (Ctrl+Z) - Redo – Redo the previous changes made to script (Ctrl+Y) - Cut – Cuts the highlighted script from the SQL script editor (Ctrl+X) @@ -41,14 +41,13 @@ The SQL Script Editor window has the following options: [Transact-SQL Reference](https://learn.microsoft.com/en-us/previous-versions/sql/sql-server-2005/ms189826(v=sql.90)) article -Click **Save and Close** to return to the Analysis Properties page. If no changes were made or -intended, it is best practice to click **Cancel** to close the SQL Script Editor wizard to ensure no -accidental changes are saved. +Click **Save and Close** to return to the Analysis Properties page. If you made no changes, click +**Cancel** to close the SQL Script Editor wizard and avoid saving accidental changes. ## Parameters Use the Parameters window to add, edit, and delete temporary variables and tables defined by -SQLscripting and users. The window only displays when **Parameters** is clicked. +SQLscripting and users. The window displays only when you click **Parameters**. ![Parameters window](/images/accessanalyzer/11.6/admin/analysis/sqlscriptparameters.webp) @@ -75,8 +74,8 @@ The parameters have the following properties: - Name – Name of the variable or table - Type – Type of variable or table - - String variables utilize a text string input - - Integers and floats are able to handle invalid inputs + - String variables use a text string input + - Integers and floats can handle invalid inputs - Boolean variables only take True/False input, in SQL they are 1/0 - Percentages only take whole numbers 0-100, converted to 0.0 to 1.0 in SQL - Temporary and Variable Tables @@ -110,8 +109,8 @@ The Edit table window has the following options: - Delete – Deletes the selected value - Up/Down – Changes the value position higher or lower -A CSV file is created under the job’s directory when a parameter table is added to the analysis. A -pre-existing CSV file can also be uploaded to populate the table. +Enterprise Auditor creates a CSV file under the job’s directory when you add a parameter table to +the analysis. You can also upload a pre-existing CSV file to populate the table. -Click **OK** to confirm changes to the table. If no changes were made or intended, click **Cancel** -to close the Edit Table window to ensure no accidental changes are saved. +Click **OK** to confirm changes to the table. If you made no changes, click **Cancel** to close the +Edit Table window and avoid saving accidental changes. diff --git a/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/columns.md b/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/columns.md index 75f2787874..c3ecf5f76b 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/columns.md +++ b/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/columns.md @@ -11,7 +11,7 @@ The Result Columns page lists the tables selected on the Input Select page. ![View and Table Creation Analysis Module wizard Result Columns page](/images/accessanalyzer/11.6/admin/analysis/sqlviewcreation/columns.webp) Expand the table to show its columns. Then, select the checkbox next to the column to include it in -the resulting table or view. If two data tables are being joined, the resulting table displays at +the resulting table or view. If you join two data tables, the resulting table displays at the bottom of the grid. Use the scroll bar to view any hidden tables or data points. The grid provides the following options for formatting the resulting table or view: @@ -21,14 +21,14 @@ The grid provides the following options for formatting the resulting table or vi - Add Column – Opens the New Trend Column window, where columns can be added to the table - Delete – Deletes a selected column - - Original columns cannot be deleted. Only columns that have been added by users can be deleted. + - Original columns can't be deleted. Only columns that have been added by users can be deleted. -- Show All Columns/Hide Unchecked Columns – Hides rows that are not currently selected ,or if - columns are currently hidden, displays all columns in the table +- Show All Columns/Hide Unchecked Columns – Hides rows that aren't selected, or if + columns are hidden, displays all columns in the table - Checked – Selects data columns for inclusion in the resulting table or view - Column Name – Displays the data column name - Group Operation – Accesses the available group operations that can be applied to individual data - points. Click on a cell in this column to display the drop-down arrow. The following operations + points. Click a cell in this column to display the dropdown arrow. The following operations are available: - (none) @@ -43,7 +43,7 @@ The grid provides the following options for formatting the resulting table or vi column name on the materialized table or view. If applying a group operation, a default data label shows. To apply a custom label, click in the cell and enter the label. - Order By Operation – Accesses the available order-by operations that can be applied to individual - data points. Click on a cell in this column to display the drop-down arrow. The following + data points. Click a cell in this column to display the dropdown arrow. The following operations are available: - None diff --git a/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/export.md b/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/export.md index 98377a96c7..76d46f5e30 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/export.md +++ b/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/export.md @@ -13,9 +13,9 @@ Use the Export settings page to specify data export settings. Select the **Export results data** checkbox to enable the settings. The following options control the file type and destination of the exported data: -- Format – Use the drop-down menu to select the file format of the exported data +- Format – Use the dropdown menu to select the file format of the exported data - - MS Excel file – Converts file to Microsoft Excel format. If Excel is not installed on the + - MS Excel file – Converts file to Microsoft Excel format. If Excel isn't installed on the console, a warning message shows and another export file format needs to be selected. - CSV file – Converts file to Comma-Separated Values format. Includes the option to compress the file to a zip file. @@ -29,4 +29,4 @@ the file type and destination of the exported data: **Location** field. To specify a different location, clear the checkbox and edit the **Location** field. -Once the options are selected, click **Next**. +After you select the options, click **Next**. diff --git a/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/filter.md b/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/filter.md index a83d9f9d14..5e36ffdb80 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/filter.md +++ b/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/filter.md @@ -11,8 +11,8 @@ Use this page to add custom filters to the table using the Filter Builder. ![View and Table Creation Analysis Module wizard Filter page](/images/accessanalyzer/11.6/admin/analysis/sqlviewcreation/filter.webp) Filters reduce the amount of data visible in a column imported to the resulting table or view. By -default, when the filter page is blank, all the data within each column is included. Use the -following options to add and remove filters: +default, when the filter page is blank, Enterprise Auditor includes all the data within each column. +Use the following options to add and remove filters: - Edit – Opens the Filter window diff --git a/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/input.md b/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/input.md index 2c3988e9a3..a6b3118dc6 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/input.md +++ b/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/input.md @@ -11,16 +11,16 @@ aggregate into a resulting table or view. ![View and Table Creation Analysis Module wizard Input Source page](/images/accessanalyzer/11.6/admin/analysis/sqlviewcreation/input.webp) -At the first drop-down, select a table. The drop-down lists on this page are determined by the -selection made on the Input Scope page. To join or aggregate data from two tables, select a second -table at the second drop-down menu. To remove the second table from the field, click the **X** +At the first dropdown, select a table. The selection you make on the Input Scope page determines +the dropdown lists on this page. To join or aggregate data from two tables, select a second +table at the second dropdown menu. To remove the second table from the field, click the **X** button. :::note -It is important to choose tables that are compatible with one another or share similar +Choose tables that are compatible with one another or share similar columns. ::: -When the two sources of data are selected, click **Next** to create a joint column within the +After you select the two data sources, click **Next** to create a joint column within the resulting table or view. diff --git a/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/inputscope.md b/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/inputscope.md index 2f8dd2f40c..ede863422d 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/inputscope.md +++ b/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/inputscope.md @@ -11,7 +11,7 @@ available for selection on the subsequent pages. ![View and Table Creation Analysis Module wizard Input Selection page](/images/accessanalyzer/11.6/admin/analysis/sqlviewcreation/inputscope.webp) -Select the source data to be used from the following options: +Select the source data to use from the following options: - Tables from Current Job – Targets all tables generated by the current job within the SQL Server database diff --git a/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/joincolumns.md b/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/joincolumns.md index 6eac2de3b7..bdcebe3de7 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/joincolumns.md +++ b/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/joincolumns.md @@ -7,8 +7,8 @@ sidebar_position: 30 # SQLViewCreations: Join Columns Use the Join Columns page to select a column from each source table to join together on the -resulting table or view. The options on this page are only enabled if two tables are selected on the -Input Source page. +resulting table or view. Enterprise Auditor enables the options on this page only if you select two +tables on the Input Source page. :::note The SQLViewCreation analysis module can join two tables, using a simple equi-join @@ -22,17 +22,17 @@ for additional information. ![View and Table Creation Analysis Module wizard Join Columns page](/images/accessanalyzer/11.6/admin/analysis/sqlviewcreation/joincolumns.webp) Use the **Table 1 join property** and **Table 2 join property** fields to select join predicates -from both tables. Join predicates are columns containing analogous values that are used to match -records in referenced tables. +from both tables. Join predicates are columns containing analogous values that match records in +referenced tables. Next, specify how to join these tables. To automatically select the appropriate join type, select one or more of the checkboxes. The selection in the **Join Type** field updates based on user selections. -To manually select, use the **Join Type** field. The selection here may update the above checkboxes. -The following options are available: +To manually select, use the **Join Type** field. The selection here may update the checkboxes you +selected earlier. The following options are available: -- Join Type – Select a join type from the drop-down: +- Join Type – Select a join type from the dropdown: :::note Left is the first table referenced, right is the second table. @@ -48,8 +48,8 @@ The following options are available: :::note The join property is the column found within both tables. The two columns can have -different names. However, in the results set, everywhere a value in the first column matches the -value in the second column, rows from the respective tables are joined together. +different names. However, in the results set, wherever a value in the first column matches the +value in the second column, Enterprise Auditor joins rows from the respective tables. ::: diff --git a/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/overview.md b/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/overview.md index d089d61de6..b0328feabb 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/overview.md +++ b/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/overview.md @@ -6,8 +6,8 @@ sidebar_position: 60 # SQLViewCreation Analysis Module -The SQLViewCreation analysis module provides the ability to create new views or tables that are used -in Enterprise Auditor actions and reports. These views or tables are re-created during job +The SQLViewCreation analysis module lets you create new views or tables for use in Enterprise +Auditor actions and reports. Enterprise Auditor re-creates these views or tables during job execution. :::warning @@ -19,7 +19,7 @@ tables. Tables require more storage space in the database. ## Configuration This analysis module provides the View and Table Creation Analysis Module wizard to assist in -configuring the module. Before the wizard, collect the desired data for manipulation. +configuring the module. Before the wizard, collect the data you want to manipulate. The wizard contains the following pages: diff --git a/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/result.md b/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/result.md index 8b869aa60e..4e520a295e 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/result.md +++ b/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/result.md @@ -16,9 +16,10 @@ two sourced tables. Select from the following two options: - Create Table – Creates a table output for the resulting dataset - Create View – Creates a view output for the resulting dataset -A default name of `SA_[job name]_Result` is provided in the name field. You can customize this name +The name field defaults to `SA_[job name]_Result`. You can customize this name for the resulting table or view. -The name must start with `SA` to be recognized as a Enterprise Auditor table or view. +The name must start with `SA` so Enterprise Auditor recognizes it as an Enterprise Auditor table or +view. After selecting the resulting table or view’s visual representation and name, click **Next**. diff --git a/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/resultconstraints.md b/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/resultconstraints.md index a6125a9b4d..39e73782b7 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/resultconstraints.md +++ b/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/resultconstraints.md @@ -10,7 +10,7 @@ Use the Result Constraints page to impose restraints on the dataset. ![View and Table Creation Analysis Module wizard Result constraints page](/images/accessanalyzer/11.6/admin/analysis/sqlviewcreation/resultconstraints.webp) -Select one of the following options to choose if and how much data should be returned: +Select one of the following options to choose whether and how much data to return: - Duplicate rows can appear in the result set - Only unique rows can appear in the result set @@ -18,7 +18,7 @@ Select one of the following options to choose if and how much data should be ret of measurement to return for the rows that appear in the resulting table or view - With ties – Include all instances of identical values in the sorted columns with the results. - To include only one instance of identical values, do not select this option.. See the + To include only one instance of identical values, don't select this option.. See the [With Ties Example](#with-ties-example) topic for additional information. :::note @@ -40,8 +40,8 @@ Consider a table that has ten rows with one repeating entry under the value colu ![cid:image025.webp@01D4CF74.8A56D750](/images/accessanalyzer/11.6/admin/analysis/sqlviewcreation/examplereduced.webp) -If the table is sorted by the value column in ascending order and the **Return only** option is set -to **40 percent**, then there should be four rows visible in the resulting table or view output. +If you sort the table by the value column in ascending order and set the **Return only** option +to **40 percent**, four rows should be visible in the resulting table or view output. ![cid:image026.webp@01D4CF74.8A56D750](/images/accessanalyzer/11.6/admin/analysis/sqlviewcreation/examplereducedwithties.webp) diff --git a/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/resultsample.md b/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/resultsample.md index df0454396f..4ab6fb517e 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/resultsample.md +++ b/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/resultsample.md @@ -11,10 +11,10 @@ Use this page to preview a sampling of the completed data manipulation. ![View and Table Creation Analysis Module wizard Result Sample page](/images/accessanalyzer/11.6/admin/analysis/sqlviewcreation/resultsample.webp) Click **Show Preview** to populate the window with the selections from the previous pages. If the -window does not populate, check the configurations for errors and try again. +window doesn't populate, check the configurations for errors and try again. :::note -The **Show Preview** option does not always apply the filter conditions specified within +The **Show Preview** option doesn't always apply the filter conditions specified within the wizard, but the resulting table or view applies all filters. ::: diff --git a/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/summary.md b/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/summary.md index 8b6f99f889..226353fbbb 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/summary.md +++ b/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/summary.md @@ -10,6 +10,5 @@ This page provides an overview of all the settings configured in the wizard. ![View and Table Creation Analysis Module wizard Summary page](/images/accessanalyzer/11.6/admin/analysis/sqlviewcreation/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the View and Table Creation Analysis Module wizard to ensure that no -accidental clicks are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** to close +the View and Table Creation Analysis Module wizard and avoid saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/timewindow.md b/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/timewindow.md index 66a25fd662..f74ce9a335 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/timewindow.md +++ b/docs/accessanalyzer/11.6/admin/analysis/sqlviewcreation/timewindow.md @@ -6,8 +6,8 @@ sidebar_position: 60 # SQLViewCreation: Time Window -Use the Source and Time Window page to specify which data to access if using multiple Enterprise -Auditor Consoles or history is enabled. +Use the Source and Time Window page to specify which data to access when using multiple Enterprise +Auditor Consoles or with history enabled. ![View and Table Creation Analysis Module wizard Source and Time Window page](/images/accessanalyzer/11.6/admin/analysis/sqlviewcreation/timewindow.webp) @@ -28,5 +28,5 @@ data was collected: - Data from this Enterprise Auditor Console only – Uses only data from the Enterprise Auditor Console generating the current analysis module -- Time Window – Select a time window for each table in the analysis. The drop-down menu selections +- Time Window – Select a time window for each table in the analysis. The dropdown menu selections vary based on each table's history settings. diff --git a/docs/accessanalyzer/11.6/admin/analysis/vbscripting.md b/docs/accessanalyzer/11.6/admin/analysis/vbscripting.md index f1a02b4b27..c4869a2190 100644 --- a/docs/accessanalyzer/11.6/admin/analysis/vbscripting.md +++ b/docs/accessanalyzer/11.6/admin/analysis/vbscripting.md @@ -16,13 +16,13 @@ The VBScript Editor has the following options: - Save and Close – Saves the script and closes the window - Syntax Check – Checks VB script syntax - - Syntax Check does not identify logic errors, only instances where syntax is incorrect. Click + - Syntax Check doesn't identify logic errors, only instances where syntax is incorrect. Click **Syntax Check** to open the Script Errors window which identifies syntax errors. - Syntax Check reports back syntax errors starting from the beginning of the script to the end. - Syntax Check does not return a list of errors. + Syntax Check doesn't return a list of errors. -- Load file – Opens a File Explorer which can be used to navigate to a VBS file -- Save to File – Saves the currently configured script into a VBS file +- Load file – Opens a File Explorer window you can use to navigate to a VBS file +- Save to File – Saves the configured script into a VBS file - Undo – Undo the previous changes made to script (Ctrl+Z) - Redo – Redo the previous changes made to script (Ctrl+Y) - Cut – Cuts the highlighted script from the VB script editor (Ctrl+X) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/activedirectory/options.md b/docs/accessanalyzer/11.6/admin/datacollector/activedirectory/options.md index 8390ab1a7b..ef6343746b 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/activedirectory/options.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/activedirectory/options.md @@ -15,11 +15,11 @@ The Options page provides format options for returned data. It is a wizard page - Return data as collected - Return data in a separate row for each property set in the following group - - Select the group from the drop-down menu + - Select the group from the dropdown menu - Return each value of the following property in a separate row - - Select the property from the drop-down menu + - Select the property from the dropdown menu - How to return multi-valued properties in one cell – Select from the following options: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/activedirectory/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/activedirectory/overview.md index 856e530282..17ad37a48e 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/activedirectory/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/activedirectory/overview.md @@ -6,8 +6,8 @@ sidebar_position: 20 # ActiveDirectory Data Collector -The ActiveDirectory Data Collector audits objects published in Active Directory. It has been -preconfigured within the Active Directory Solution. Both this data collector and the solution are +The ActiveDirectory Data Collector audits objects published in Active Directory. Netwrix +preconfigures it within the Active Directory Solution. Both this data collector and the solution are available with a special Enterprise Auditor license. See the [Active Directory Solution](/docs/accessanalyzer/11.6/solutions/activedirectory/overview.md) topic for additional information. @@ -30,7 +30,7 @@ topic for additional information. ## ActiveDirectory Query Configuration -The ActiveDirectory Data Collector is configured through the Active Directory Data Collector Wizard, +Configure the ActiveDirectory Data Collector through the Active Directory Data Collector Wizard, which contains the following wizard pages: - Welcome @@ -42,5 +42,5 @@ which contains the following wizard pages: ![Active Directory Data Collector Wizard Welcome page](/images/accessanalyzer/11.6/admin/datacollector/activedirectory/welcome.webp) -The Welcome page can be hidden by selecting the **Do not display this page the next time** checkbox -when the wizard is open and configuration settings are saved. +To hide the Welcome page, select the **Don't display this page the next time** checkbox while the +wizard is open, and save the configuration settings. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/activedirectory/results.md b/docs/accessanalyzer/11.6/admin/datacollector/activedirectory/results.md index 9d284bc3c8..c14e5f3314 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/activedirectory/results.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/activedirectory/results.md @@ -6,11 +6,11 @@ sidebar_position: 30 # ActiveDirectory: Results -The Results page is where Active Directory object properties to be gathered are selected. It is a +Use the Results page to select the Active Directory object properties to gather. It is a wizard page for all categories. ![Active Directory Data Collector Wizard Results page](/images/accessanalyzer/11.6/admin/datacollector/activedirectory/results.webp) -Properties can be selected individually or the **Check all**, **Uncheck all**, and **Reset to -defaults** buttons can be used. All selected properties are gathered. Available properties vary +You can select properties individually, or use the **Check all**, **Uncheck all**, and **Reset to +defaults** buttons. Enterprise Auditor gathers all selected properties. Available properties vary based on the category selected. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/activedirectory/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/activedirectory/summary.md index 98e5d90d7c..058b0bb673 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/activedirectory/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/activedirectory/summary.md @@ -10,6 +10,5 @@ The Summary page displays a summary of the configured query. It wizard page for ![Active Directory Data Collector Wizard Summary page](/images/accessanalyzer/11.6/admin/datacollector/activedirectory/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Active Directory Data Collector Wizard to ensure that no accidental -clicks are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** to close +the Active Directory Data Collector Wizard and avoid saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/adactivity/category.md b/docs/accessanalyzer/11.6/admin/datacollector/adactivity/category.md index e455ea4cc4..fe43f07caa 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/adactivity/category.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/adactivity/category.md @@ -6,7 +6,7 @@ sidebar_position: 20 # ADActivity: Category -Use the Category page to identify how activity data is retrieved or removed. +Use the Category page to identify how the data collector retrieves or removes activity data. ![Active Directory Activity DC wizard Category page](/images/accessanalyzer/11.6/admin/datacollector/adactivity/category.webp) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/adactivity/cleartables.md b/docs/accessanalyzer/11.6/admin/datacollector/adactivity/cleartables.md index 4ab7037eef..8b878ed0de 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/adactivity/cleartables.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/adactivity/cleartables.md @@ -19,13 +19,13 @@ Tables** category task. ![Active Directory Activity DC wizard Results page for Remove Tables category](/images/accessanalyzer/11.6/admin/datacollector/adactivity/resultsremovetables.webp) **Step 3 –** Click **Next** to go to the Results page. Optionally, select the **Success** checkbox -to display a confirmation of successful removal in the results after the job is run. +to display a confirmation of successful removal in the results after you run the job. **Step 4 –** Click **Next** and then Click **Finish** to close the Active Directory Activity DC Wizard. Click **OK** to close the Query Properties window. :::warning -When the job is run, all of the ADActivity standard reference tables are removed from -the database. +When you run the job, Enterprise Auditor removes all of the ADActivity standard reference tables +from the database. ::: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/adactivity/connection.md b/docs/accessanalyzer/11.6/admin/datacollector/adactivity/connection.md index c9a8ad53d1..da4dac7b07 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/adactivity/connection.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/adactivity/connection.md @@ -6,14 +6,14 @@ sidebar_position: 30 # ADActivity: SAM Connection -The SAM connection page is where the port number is configured to send Active Directory data from +Use the SAM connection page to configure the port number for sending Active Directory data from Netwrix Activity Monitor. It is a wizard page for the category of: - Import from SAM ![Active Directory Activity DC wizard SAM connection settings page](/images/activitymonitor/7.1/config/activedirectory/namconnection.webp) -The following connection setting can be configured to connect to the Netwrix Activity Monitor +Configure the following connection setting to connect to the Netwrix Activity Monitor archive via an API Server: - Port – Enter the API server port. The default is 4494. @@ -24,14 +24,14 @@ archive via an API Server: scan to continue - Test SAM host – Enter the Activity Monitor API server name in a qualified domain name format. - Click Connect to test the connection. A successful result populates the section underneath with a + Click Connect to test the connection. A successful result populates the following section with a Refresh token. - Exclude – Select archives to be ignored by the Active Directory Activity DC scan :::warning Save the Refresh token to a Text Editor for later use. The Refresh token resets - each time the Test SAM host option is connected to. It must be replaced in the Connection - profile if it is regenerated. + each time you connect using the Test SAM host option. If it regenerates, replace it in the + Connection profile. ::: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/adactivity/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/adactivity/overview.md index 6db6f96a5c..0f500513f7 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/adactivity/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/adactivity/overview.md @@ -7,7 +7,7 @@ sidebar_position: 30 # ADActivity Data Collector The ADActivity Data Collector integrates with the Netwrix Activity Monitor by reading the Active -Directory activity log files. It has been preconfigured within the Active Directory Solution. Both +Directory activity log files. Netwrix preconfigures it within the Active Directory Solution. Both this data collector and the solution are available with a special Enterprise Auditor license. See the [Active Directory Solution](/docs/accessanalyzer/11.6/solutions/activedirectory/overview.md) @@ -30,8 +30,8 @@ topic for additional information. ## ADActivity Query Configuration -The ADActivity Data Collector is configured through the Active Directory Activity DC wizard, which -contains the following wizard pages, which change based up on the query category selected: +Configure the ADActivity Data Collector through the Active Directory Activity DC wizard, which +contains the following wizard pages that change based on the query category you select: - [ADActivity: Category](/docs/accessanalyzer/11.6/admin/datacollector/adactivity/category.md) - [ADActivity: SAM Connection](/docs/accessanalyzer/11.6/admin/datacollector/adactivity/connection.md) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/adactivity/results.md b/docs/accessanalyzer/11.6/admin/datacollector/adactivity/results.md index 12eeb60a14..b8b1b3495e 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/adactivity/results.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/adactivity/results.md @@ -6,10 +6,11 @@ sidebar_position: 60 # ADActivity: Results -The Results page is where the properties to be gathered are selected. It is a wizard page for all of +Use the Results page to select the properties to gather. It is a wizard page for all of the categories. ![Active Directory Activity DC wizard Results page](/images/accessanalyzer/11.6/admin/datacollector/adactivity/results.webp) -Properties can be selected individually or the **Select All** and **Clear All** buttons can be used. -All selected properties are gathered. Available properties vary based on the category selected. +You can select properties individually, or use the **Select All** and **Clear All** buttons. +Enterprise Auditor gathers all selected properties. Available properties vary based on the category +selected. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/adactivity/scope.md b/docs/accessanalyzer/11.6/admin/datacollector/adactivity/scope.md index ba4c1bb14c..46d7179cfd 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/adactivity/scope.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/adactivity/scope.md @@ -14,18 +14,18 @@ the categories of: ![Active Directory Activity DC wizard Scoping and Retention page](/images/activitymonitor/7.1/config/activedirectory/scope.webp) -The Timespan is defined according to the following two elements: +Define the Timespan according to the following two elements: - Relative Timespan – Number of days AD Activity is collected when the scan is run - Absolute Timespan – Set the date range for the scan to collect AD Activity :::info - The threshold should be set for after the Netwrix Activity Monitor collects - and archives its data but before they are deleted after a set retention period. + Set the threshold to a time after the Netwrix Activity Monitor collects + and archives its data, but before it deletes the data at the end of the retention period. ::: -The Retention section sets what event type is collected and how many days Enterprise Auditor keeps +The Retention section sets which event type Enterprise Auditor collects and how many days it keeps the collected data in its SQL database. The table has the following columns: - Event Type – The event type that may be enabled for the scan. The event types are: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/adactivity/share.md b/docs/accessanalyzer/11.6/admin/datacollector/adactivity/share.md index d2679dd4c4..adb06ff81f 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/adactivity/share.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/adactivity/share.md @@ -13,13 +13,13 @@ of: ![Active Directory Activity DC wizard Share settings page](/images/activitymonitor/7.1/config/activedirectory/share.webp) -The following connection setting can be configured to connect to the AD activity archives that must +Configure the following connection setting to connect to the AD activity archives that must be located on a Domain Controller share: -- UNC Path – Enter the path of the share that stores AD Activity from the AD Agent(s). The ellipsis +- UNC Path – Enter the path of the share that stores AD Activity from the AD Agents. The ellipsis (**…**) opens a file explorer where the path can be navigated to and selected. - - _Remember,_ all AD Agent logs must be archived to this location or the AD Activity data is not + - _Remember,_ all AD Agent logs must be archived to this location or the AD Activity data isn't queried by Enterprise Auditor - Include Sub-Directories – Select to include sub-directories on the targeted share. Use this option diff --git a/docs/accessanalyzer/11.6/admin/datacollector/adactivity/standardtables.md b/docs/accessanalyzer/11.6/admin/datacollector/adactivity/standardtables.md index f53868ae5a..0bc22ed3ce 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/adactivity/standardtables.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/adactivity/standardtables.md @@ -10,7 +10,7 @@ The ADActivity Data Collector gathers essential user and group activity informat reference tables. Unlike other Enterprise Auditor data collectors, the ADActivity Data Collector writes data to these tables regardless of the job executing the query. -These tables and their associated views are outlined below: +The following table outlines these tables and their associated views: | Table | Details | | -------------------------------- | --------------------------------------------------------------------- | @@ -36,7 +36,7 @@ These tables and their associated views are outlined below: | SA_ADActivity_SPNs | Contains a unique identifier for each logon account | Views are the recommended way for Enterprise Auditor users to obtain the information gathered by the -ADActivity Data Collector. They contain additional information for building queries easily. The +ADActivity Data Collector. They contain additional information for building queries. The following is an explanation of the corresponding views created for some of the tables generated by the ADActivity Data Collector: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/adactivity/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/adactivity/summary.md index e4f4365772..22f8f053d5 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/adactivity/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/adactivity/summary.md @@ -6,11 +6,10 @@ sidebar_position: 70 # ADActivity: Summary -The Summary page is where configuration settings are summarized. It is a wizard page for all of the +The Summary page summarizes the configuration settings. It is a wizard page for all of the categories. ![Active Directory Activity DC wizard Summary page](/images/accessanalyzer/11.6/admin/datacollector/adactivity/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Active Directory Activity DC wizard to ensure that no accidental -clicks are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** to close +the Active Directory Activity DC wizard and avoid saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/adinventory/category.md b/docs/accessanalyzer/11.6/admin/datacollector/adinventory/category.md index 5038a8bec6..2012bcabbb 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/adinventory/category.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/adinventory/category.md @@ -26,6 +26,6 @@ The categories include the following tasks: :::note The Scan Active Directory category is the pre-configured setting for the .Active Directory Inventory Job Group. Therefore, accessing the Active Directory Inventory DC Wizard from the query -within that job group does not display the Category wizard page. +within that job group doesn't display the Category wizard page. ::: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/adinventory/cleartables.md b/docs/accessanalyzer/11.6/admin/datacollector/adinventory/cleartables.md index 68fb9be767..b80ced2bd6 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/adinventory/cleartables.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/adinventory/cleartables.md @@ -10,8 +10,7 @@ Sometimes when troubleshooting an ADInventory issue, it becomes necessary to cle reference tables. Follow the steps. :::warning -Be careful when using this query task. It will result in the deletion of collected -data. +Be careful when using this query task. It deletes collected data. ::: @@ -25,7 +24,8 @@ Tables** category task. **Step 3 –** Click **Next** and then **Finish** to close the Active Directory Inventory DC Wizard. Click **OK** to close the Query Properties window. -When the job is run, all of the ADInventory standard reference tables are removed from the database. +When you run the job, Enterprise Auditor removes all of the ADInventory standard reference tables +from the database. :::warning Never leave the query task selected after job execution. Accidental data loss can @@ -34,6 +34,6 @@ occur. :::tip -Remember, this job deletes data from the Enterprise Auditor database. Check the job has been -configured correctly prior to job execution. +Remember, this job deletes data from the Enterprise Auditor database. Verify that you configured +the job correctly before running it. ::: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/adinventory/customattributes.md b/docs/accessanalyzer/11.6/admin/datacollector/adinventory/customattributes.md index 024fdeb001..00a0971269 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/adinventory/customattributes.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/adinventory/customattributes.md @@ -6,25 +6,25 @@ sidebar_position: 70 # ADInventory: Custom Attributes -The Custom Attributes page provides ability to add Active Directory attributes that are unique to -the environment or not collected by default to be gathered. It is a wizard page for the category of -Scan Active Directory. +The Custom Attributes page lets you add Active Directory attributes that are unique to +the environment or that Enterprise Auditor doesn't collect by default. It is a wizard page for the +category of Scan Active Directory. The [Standard Reference Tables & Views for the ADInventory Data Collector](/docs/accessanalyzer/11.6/admin/datacollector/adinventory/standardtables.md) -topic provides information on what is collected by default. Custom attributes added on this page are -stored in the **SA_ADInventory_ExtendedAttributes** table. +topic provides information on what Enterprise Auditor collects by default. Enterprise Auditor stores +custom attributes added on this page in the **SA_ADInventory_ExtendedAttributes** table. ![Active Directory Inventory DC Wizard Custom Attributes page](/images/accessanalyzer/11.6/admin/datacollector/adinventory/customattributes.webp) -The Custom Attribute is defined according to the following three elements: +Define the Custom Attribute according to the following three elements: - Domain Filter – Short or fully qualified name - Object Class – User, Group, or Computer - Attribute Name – As listed within Active Directory Use the **Add**, **Edit**, and **Remove** buttons at the bottom of the window to configure the -custom attributes to be gathered by the scan. See the +custom attributes the scan gathers. See the [Manually Add Custom Attributes](#manually-add-custom-attributes) topic for additional information. The **Import** button opens the Custom Attributes Import Wizard. See the @@ -38,30 +38,29 @@ article. #### Manually Add Custom Attributes The **Add** and **Edit** buttons on the Custom Attributes page open the Custom Attribute window. -Follow the steps to manually add custom attributes. +To manually add custom attributes: **Step 1 –** On the Custom Attributes page of the Active Directory Inventory DC Wizard, click **Add**. The Custom Attribute window opens. ![Custom Attribute window](/images/accessanalyzer/11.6/admin/datacollector/adinventory/customattributesadd.webp) -**Step 2 –** Enter the **Domain Filter**. This can be entered either as the short domain name or the +**Step 2 –** Enter the **Domain Filter**. Enter this as either the short domain name or the fully qualified domain name. -**Step 3 –** Select the checkbox for the desired **Object Class**. +**Step 3 –** Select the checkbox for the **Object Class** you want. **Step 4 –** Enter the **Attribute Name** as it appears in Active Directory. -**Step 5 –** Click **OK**. The Custom Attribute window closes and the specified attribute is added -in the Custom Attributes page. +**Step 5 –** Click **OK**. The Custom Attribute window closes, and Enterprise Auditor adds the +specified attribute to the Custom Attributes page. -Repeat this process until all desired Custom Attributes have been included. +Repeat this process until you've included all desired Custom Attributes. #### Custom Attributes Import Wizard -The Custom Attributes Import Wizard is used to import a list of custom attributes into the -ADInventory Data Collector configurations. Follow the steps to use the Custom Attributes Import -Wizard. +Use the Custom Attributes Import Wizard to import a list of custom attributes into the +ADInventory Data Collector configurations: **Step 1 –** On the Custom Attributes page of the Active Directory Inventory DC Wizard, click **Import**. The Custom Attribute Import Wizard opens. @@ -69,7 +68,7 @@ Wizard. ![Custom Attributes Import Wizard Credentials page](/images/accessanalyzer/11.6/admin/datacollector/adinventory/customattributesimportcredentials.webp) **Step 2 –** On the Credentials page, identify a domain either by entering one manually or selecting -one from the **Domain Name** drop-down menu which displays a list of domains trusted by the one in +one from the **Domain Name** dropdown menu which displays a list of domains trusted by the one in which the Enterprise Auditor Console server resides. Then set the credentials for reading the attributes list from the domain: @@ -82,12 +81,12 @@ Click **Next** to continue. ![Custom Attributes Import Wizard Attributes page](/images/accessanalyzer/11.6/admin/datacollector/adinventory/customattributesimportattributes.webp) **Step 3 –** The wizard populates available attributes from the domain specified on the Attributes -page. Expand the desired object class and select the checkboxes for the custom attributes to be -imported. Then click **Next**. +page. Expand the object class you want and select the checkboxes for the custom attributes you want +to import. Then click **Next**. ![Custom Attributes Import Wizard Summary page](/images/accessanalyzer/11.6/admin/datacollector/adinventory/customattributesimportsummary.webp) **Step 4 –** On the Summary page, click **Finish**. -The selected attributes are added on the Custom Attributes page of the Active Directory Inventory DC -Wizard. +Enterprise Auditor adds the selected attributes to the Custom Attributes page of the Active +Directory Inventory DC Wizard. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/adinventory/indexupdateoptions.md b/docs/accessanalyzer/11.6/admin/datacollector/adinventory/indexupdateoptions.md index 25ad1450fd..1213b20dd9 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/adinventory/indexupdateoptions.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/adinventory/indexupdateoptions.md @@ -6,8 +6,8 @@ sidebar_position: 60 # ADInventory: Index Update Options -Configure options for maintaining SQL Server indexes while running queries using the Index Update -Options page. +Use the Index Update Options page to configure options for maintaining SQL Server indexes while +running queries. ![Active Directory Inventory DC Wizard Index Update Options page](/images/accessanalyzer/11.6/admin/datacollector/adinventory/indexupdateoptions.webp) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/adinventory/options.md b/docs/accessanalyzer/11.6/admin/datacollector/adinventory/options.md index 72e8327edd..b48b4262a3 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/adinventory/options.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/adinventory/options.md @@ -19,10 +19,10 @@ The Options page has the following configuration options: - Ignore certificate errors? (For testing only) – Ignores untrusted certificate authority errors and allows the scan to continue. This option is for testing purposes only. -- Collect SID History from domain migrations – During a domain migration, the new infrastructure is - created alongside the old infrastructure. The old account SID is typically added to the SID - history attribute for the new account. The option to collect SID history is made available within - the ADInventory Data Collector to assist resolving SIDs for domain migrations. +- Collect SID History from domain migrations – A domain migration creates the new infrastructure + alongside the old infrastructure. The migration typically adds the old account SID to the SID + history attribute for the new account. The ADInventory Data Collector provides the option to + collect SID history to help resolve SIDs for domain migrations. - Collect only updates since the last scan (recommended) – Default setting for differential scanning. The updates collected are any changes to: group membership, attributes on user objects, attributes on group objects, and so on. @@ -30,7 +30,7 @@ The Options page has the following configuration options: - Track changes into Change tracking tables – Records all changes since the last scan in separate tables - Limit Last Logon TimeStamp Changes – When selected, changes to the Last Logon TimeStamp - Attribute are not recorded + Attribute aren't recorded :::info If tracking changes, use the Limit Last Logon TimeStamp Changes option. @@ -40,16 +40,16 @@ The Options page has the following configuration options: - Number of days you want to keep changes in the database – Use the arrow buttons or manually enter a number to set the number of days to keep changes - Target previously scanned domain controller – Collects updated information from the last - domain controller targeted to reduce the scan time. Below are some considerations: + domain controller targeted to reduce the scan time. Consider the following: - If the last domain controller is unavailable, the targeted domain controller is the specified domain controller from the host list. If using the domain name, it attempts to find the last scanned domain controller. - - If that domain controller is determined to be unavailable, then it runs a full scan on the + - If that domain controller turns out to be unavailable, it runs a full scan on the next domain controller that responds. Then, it will scan the new domain controller for changes going forward. Selecting the **Track changes into Change tracking tables** option enables the **Number of days - you want to keep changes in the database** box. This allows for changes in Active Directory to - be tracked. When change tracking is enabled, notification analysis tasks can be used to send + you want to keep changes in the database** box. This allows Enterprise Auditor to track changes + in Active Directory. With change tracking enabled, use notification analysis tasks to send alerts. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/adinventory/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/adinventory/overview.md index b62afd5a40..c835906efc 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/adinventory/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/adinventory/overview.md @@ -9,11 +9,11 @@ sidebar_position: 40 The extraction and correlation of user, group, and computer attributes drastically transforms the meaning of data collected across the many systems and applications that are linked to Active Directory. The ADInventory Data Collector is designed as a highly scalable and useful data -collection mechanism to catalogue user, group, and computer object information that can be used by -other solutions within Enterprise Auditor. +collection mechanism to catalogue user, group, and computer object information that other solutions +within Enterprise Auditor can use. -The ADInventory Data Collector is a core component of Enterprise Auditor and has been preconfigured -to be used within the .Active Directory Inventory Solution. Both this data collector and the +The ADInventory Data Collector is a core component of Enterprise Auditor. Netwrix preconfigures it +for use within the .Active Directory Inventory Solution. Both this data collector and the solution are available with all Enterprise Auditor license options. See the [.Active Directory Inventory Solution](/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/overview.md) topic for additional information. @@ -44,14 +44,14 @@ topic for additional information. ## Functional Design of the ADInventory Data Collector -The ADInventory Data Collector has been designed to update incrementally. Once it has run against a +The ADInventory Data Collector updates incrementally. After it runs against a domain controller, additional collections gather changes made since the last scan. This enables the -ADInventory Data Collector to function efficiently within large environments. Each time it is run +ADInventory Data Collector to function efficiently within large environments. Each time you run it against different domain controllers, it restarts the cycle. ## ADInventory Query Configuration -The ADInventory Data Collector is configured through the Active Directory Inventory DC Wizard, which +Configure the ADInventory Data Collector through the Active Directory Inventory DC Wizard, which contains the following wizard pages: - Welcome @@ -64,5 +64,5 @@ contains the following wizard pages: ![Active Directory Inventory DC Wizard Welcome page](/images/accessanalyzer/11.6/admin/datacollector/adinventory/welcome.webp) -The Welcome page can be hidden by selecting the **Do not display this page the next time** checkbox -when the wizard is open and configuration settings are saved. +To hide the Welcome page, select the **Don't display this page the next time** checkbox while the +wizard is open, and save the configuration settings. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/adinventory/results.md b/docs/accessanalyzer/11.6/admin/datacollector/adinventory/results.md index e6bc6261d4..3326e6c1cd 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/adinventory/results.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/adinventory/results.md @@ -6,14 +6,14 @@ sidebar_position: 30 # ADInventory: Results -The Results page is where properties from Active Directory to be gathered are selected. It is a +Use the Results page to select the properties from Active Directory to gather. It is a wizard page for the category of Scan Active Directory. ![Active Directory Inventory DC Wizard Results page](/images/accessanalyzer/11.6/admin/datacollector/adinventory/results.webp) -Properties can be selected individually or the **Select All** or **Clear All** buttons can be used. -All selected properties are gathered. +You can select properties individually, or use the **Select All** or **Clear All** buttons. +Enterprise Auditor gathers all selected properties. -This information is not available within the standard reference tables and views. Instead, this -information can be viewed in the SA_ADInventory_DEFAULT table, which is created when any of these -properties are selected. +This information isn't available within the standard reference tables and views. Instead, you can +view it in the SA_ADInventory_DEFAULT table, which Enterprise Auditor creates when you select any of +these properties. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/adinventory/standardtables.md b/docs/accessanalyzer/11.6/admin/datacollector/adinventory/standardtables.md index 1a4a8f00d3..315be0fd7b 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/adinventory/standardtables.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/adinventory/standardtables.md @@ -10,7 +10,7 @@ The ADInventory Data Collector gathers essential user and group inventory inform reference tables. Unlike other Enterprise Auditor data collectors, the ADInventory Data Collector writes data to these tables regardless of the job executing the query. -These tables and their associated views are outlined below: +The following table outlines these tables and their associated views: | Table | Details | AD Object Reference Article | | ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | @@ -33,7 +33,7 @@ These tables and their associated views are outlined below: Views are the recommended way for you to obtain the information gathered by the ADInventory Data -Collector. They contain additional information for building queries easily. +Collector. They contain additional information for building queries. The following is an explanation of the corresponding views created for some of the tables generated by the ADInventory Data Collector: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/adinventory/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/adinventory/summary.md index ebcc0ead07..44316d83f7 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/adinventory/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/adinventory/summary.md @@ -6,11 +6,10 @@ sidebar_position: 80 # ADInventory: Summary -The Summary page is where configuration settings are summarized. It is a wizard page for all of the +The Summary page summarizes the configuration settings. It is a wizard page for all of the categories. ![Active Directory Inventory DC Wizard Summary page](/images/accessanalyzer/11.6/admin/datacollector/adinventory/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Active Directory Inventory DC Wizard to ensure that no accidental -clicks are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** to close +the Active Directory Inventory DC Wizard and avoid saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/category.md b/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/category.md index 60ea8d5c14..166934a165 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/category.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/category.md @@ -6,8 +6,7 @@ sidebar_position: 20 # ADPermissions: Category -The ADPermissions Data Collector Category page identifies what kind of information to retrieve using -the Category wizard page. +The ADPermissions Data Collector Category page identifies what kind of information to retrieve. ![ADPermissions Data Collector wizard Category page](/images/accessanalyzer/11.6/admin/datacollector/adpermissions/category.webp) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/customfilter.md b/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/customfilter.md index a1cf116329..35c106ffab 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/customfilter.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/customfilter.md @@ -7,7 +7,7 @@ sidebar_position: 40 # ADPermissions: Custom Filter The Custom Filter page provides options to configure settings for object permission collection. It -is only available if the Custom Filter option is checked on the Scope page. It is a wizard page for +is only available if you check the Custom Filter option on the Scope page. It is a wizard page for the categories of: - Scan Active Directory Permissions @@ -19,11 +19,11 @@ The configurable options are: - Root Path – Enter the AD root path - - Select the distinguished name from the drop-down menu to the right of the Root Path + - Select the distinguished name from the dropdown menu to the right of the Root Path - Click **Preview** to show an example of the complete path - LDAP Filter – Enter a custom filter string -- Scope – Select an option from the drop-down menu: +- Scope – Select an option from the dropdown menu: - Base – Limits the scope to the base object. The maximum number of objects returned is always one. @@ -31,4 +31,4 @@ The configurable options are: object itself - Sub tree – (or a deep scope) includes all child objects as well as the base object -- Click **Add** to add the filter criteria to the list. Multiple filters can be used. +- Click **Add** to add the filter criteria to the list. You can use multiple filters. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/overview.md index dc95436186..14b0801253 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/overview.md @@ -6,8 +6,8 @@ sidebar_position: 50 # ADPermissions Data Collector -The ADPermissions Data Collector collects the advanced security permissions of objects in AD. It is -preconfigured within the Active Directory Permissions Analyzer Solution. Both this data collector +The ADPermissions Data Collector collects the advanced security permissions of objects in AD. +Netwrix preconfigures it within the Active Directory Permissions Analyzer Solution. Both this data collector and the solution are available with a special Enterprise Auditor license. See the [Active Directory Permissions Analyzer Solution](/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/overview.md) topic for additional information. @@ -32,9 +32,9 @@ topic for additional information. ## ADPermissions Query Configuration -The ADPermissions Data Collector is configured through the Active Directory Permissions Data -Collector Wizard. The wizard contains the following pages, which change based upon the query -category selected: +Configure the ADPermissions Data Collector through the Active Directory Permissions Data +Collector Wizard. The wizard contains the following pages, which change based on the query +category you select: - [ADPermissions: Category](/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/category.md) - [ADPermissions: Scope](/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/scope.md) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/removetables.md b/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/removetables.md index 06eaf2440e..e2c0300dbf 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/removetables.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/removetables.md @@ -12,7 +12,7 @@ Connection Profile applied should be the same as the one used for the associated Permissions Analyzer** > **0.Collection** Job. Follow the steps. :::warning -Using this query task results in the deletion of collected data. +Using this query task deletes collected data. ::: @@ -21,23 +21,23 @@ Using this query task results in the deletion of collected data. **Step 2 –** In the Active Directory Permissions Data Collector Wizard, on the Category page select the **Remove Tables** category and click **Next**. -**Step 3 –** On the Results page, make sure all the Available Properties are selected and click +**Step 3 –** On the Results page, ensure all the Available Properties are selected and click **Next**. **Step 4 –** Click **Finish** to close the Active Directory Permissions Data Collector Wizard. Click **OK** to close the Query Properties window. -When the job is run, all of the ADPermissions standard reference tables are removed from the -database. +When you run the job, Enterprise Auditor removes all of the ADPermissions standard reference tables +from the database. :::tip -Remember, this job deletes data from the Enterprise Auditor database. Ensure the job has been -configured correctly prior to executing the job. +Remember, this job deletes data from the Enterprise Auditor database. Ensure you configure the job +correctly before running it. ::: :::warning -Never leave the query task selected after the job has been executed. Accidental data +Never leave the query task selected after you execute the job. Accidental data loss can occur. ::: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/results.md b/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/results.md index a6d16adbf8..e6ebc7d718 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/results.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/results.md @@ -6,10 +6,11 @@ sidebar_position: 60 # ADPermissions: Results -The Results page is where properties that will be gathered are selected. It is a wizard page for all +Use the Results page to select the properties to gather. It is a wizard page for all of the categories. ![ADPermissions Data Collector wizard Results page](/images/accessanalyzer/11.6/admin/datacollector/adpermissions/results.webp) -Available properties vary based on the category selected. Properties can be selected individually or -the **Select All** and **Clear All** buttons can be used. All selected properties are gathered. +Available properties vary based on the category selected. You can select properties individually, +or use the **Select All** and **Clear All** buttons. Enterprise Auditor gathers all selected +properties. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/scope.md b/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/scope.md index e396153073..704da21387 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/scope.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/scope.md @@ -6,7 +6,7 @@ sidebar_position: 30 # ADPermissions: Scope -The Scope page is where the scope for the Active Directory permissions scan is configured. It is a +Use the Scope page to configure the scope for the Active Directory permissions scan. It is a wizard page for the categories of: - Scan Active Directory Permissions diff --git a/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/standardtables.md b/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/standardtables.md index aadb080a7d..bf31d93dfa 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/standardtables.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/standardtables.md @@ -10,7 +10,7 @@ The ADPermissions Data Collector gathers essential user and group inventory info standard reference tables. Unlike other Enterprise Auditor data collectors, the ADPermissions Data Collector writes data to these tables regardless of the job executing the query. -These tables and their associated views are outlined below: +The following table outlines these tables and their associated views: | Table | Details | | -------------------------------------- | ------------------------------------------------- | diff --git a/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/summary.md index 986edb0600..1e8f18a578 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/adpermissions/summary.md @@ -6,11 +6,10 @@ sidebar_position: 70 # ADPermissions: Summary -The Summary page is where configuration settings are summarized. It is a wizard page for all of the +The Summary page summarizes the configuration settings. It is a wizard page for all of the categories. ![ADPermissions Data Collector wizard Summary page](/images/accessanalyzer/11.6/admin/datacollector/adpermissions/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Active Directory Permissions Data Collector Wizard ensuring that no -accidental clicks are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** to close +the Active Directory Permissions Data Collector Wizard and avoid saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/aws/criteria.md b/docs/accessanalyzer/11.6/admin/datacollector/aws/criteria.md index f74bfdd72f..baa19c1492 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/aws/criteria.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/aws/criteria.md @@ -6,8 +6,8 @@ sidebar_position: 50 # AWS: Criteria -The Criteria (Select DLP criteria for this scan) page is where criteria to be used for discovering -sensitive data during a scan is configured. It is a wizard page for the category of Collect SDD +Use the Criteria (Select DLP criteria for this scan) page to configure the criteria for discovering +sensitive data during a scan. It is a wizard page for the category of Collect SDD Data. This page requires the Sensitive Data Discovery Add-On to be been installed on the Enterprise @@ -17,11 +17,11 @@ topic for additional information. ![AWS Query SDD Criteria](/images/accessanalyzer/11.6/admin/datacollector/aws/criteria.webp) -Default criteria is set at the **Global Settings** > **Sensitive Data** node. Choose between the +Set default criteria at the **Global Settings** > **Sensitive Data** node. Choose between the **Use Global Criteria** Selection and the **Use the Following Selected Criteria** radio buttons. -For custom criteria, select the checkbox for the criteria to be used to search for sensitive data. -There are **Select All** and **Clear All** buttons that can be used. +For custom criteria, select the checkbox for the criteria to use to search for sensitive data. +You can use the **Select All** and **Clear All** buttons. The table contains the following types of criteria: @@ -34,7 +34,7 @@ Criteria and User Criteria nodes are visible in the table. ::: -User-defined criteria is created in the Criteria Editor, accessed through the **Global Settings** > +Create user-defined criteria in the Criteria Editor, accessed through the **Global Settings** > **Sensitive Data** node. See the [Sensitive Data Discovery Add-On](/docs/accessanalyzer/11.6/sensitivedatadiscovery/overview.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/aws/droptables.md b/docs/accessanalyzer/11.6/admin/datacollector/aws/droptables.md index 5d56597c3e..999e27cec5 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/aws/droptables.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/aws/droptables.md @@ -7,7 +7,7 @@ sidebar_position: 80 # Drop AWS Tables Sometimes when troubleshooting an AWS issue, it becomes necessary to clear the AWS DC data and -tables from the Enterprise Auditor database. Follow the steps to configure a job to remove tables. +tables from the Enterprise Auditor database. To configure a job to remove tables: **Step 1 –** Create a new job. @@ -24,13 +24,14 @@ tables from the Enterprise Auditor database. Follow the steps to configure a job Collector Wizard. Click **OK** to close the Query Properties window. :::warning -When the job is run, all of the AWS DC data and tables are removed from the database. +When you run the job, Enterprise Auditor removes all of the AWS DC data and tables +from the database. ::: The job is now configured and ready to run. :::note -An AWS connection profile is not required for the Drop AWS DC Tables task. +An AWS connection profile isn't required for the Drop AWS DC Tables task. ::: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/aws/filters3objects.md b/docs/accessanalyzer/11.6/admin/datacollector/aws/filters3objects.md index d8af8074f0..f301f4493b 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/aws/filters3objects.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/aws/filters3objects.md @@ -6,8 +6,8 @@ sidebar_position: 30 # AWS: Filter S3 Objects -The Filter S3 Objects page provides the options to filter which objects stored in S3 should be -queried for permissions and sensitive data. It is a wizard page for the categories of: +The Filter S3 Objects page provides options to filter which objects stored in S3 to query for +permissions and sensitive data. It is a wizard page for the categories of: - Collect S3 - Collect SDD Data @@ -32,7 +32,7 @@ Select from the available buckets and click **OK** to add them to the Filter S3 ## Add Custom Filter -The Add Custom Filter window allows a custom filter to be configured. +The Add Custom Filter window lets you configure a custom filter. ![Add Custom Filter window](/images/accessanalyzer/11.6/admin/datacollector/aws/customfilter.webp) @@ -41,6 +41,6 @@ Configure a custom filter using the following format: - The characters `*` and `?` are wildcards - `*` – matches any number of characters - `?` – matches a single character -- ARN should follow the format: `arn:aws:s3:::/` +- The Amazon Resource Name (ARN) should follow the format: `arn:aws:s3:::/` Click **Save** to add the custom filter to the Filter S3 Objects page. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/aws/loginroles.md b/docs/accessanalyzer/11.6/admin/datacollector/aws/loginroles.md index 4d4a926275..392983642f 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/aws/loginroles.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/aws/loginroles.md @@ -6,7 +6,7 @@ sidebar_position: 20 # AWS: Login Roles -The Login Roles page is where the previously created AWS Roles are added. It is a wizard page for +Use the Login Roles page to add the previously created AWS Roles. It is a wizard page for the categories of: - Collect Org data @@ -25,5 +25,5 @@ topic for additional information. The page has the following options: - Remove – Remove the selected role from the list - Clear – Remove all roles from the list - Max Session Duration (hours) – Specify the maximum time the account can be logged in for. This - value should not exceed the SessionDuration configured for the role in AWS. The default value is 1 + value shouldn't exceed the SessionDuration configured for the role in AWS. The default value is 1 and the maximum value is 12. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/aws/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/aws/overview.md index 34b28d7390..7c591d1b4a 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/aws/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/aws/overview.md @@ -7,8 +7,9 @@ sidebar_position: 60 # AWS Data Collector The AWS Data Collector collects IAM users, groups, roles, and policies, as well as S3 permissions, -content, and sensitive data from the target Amazon Web Services (AWS) accounts. The AWS Data -Collector has been preconfigured for the AWS Solution. Both this data collector and the solution are +content, and sensitive data from the target Amazon Web Services (AWS) accounts. Netwrix +preconfigures the AWS Data Collector for the AWS Solution. Both this data collector and the solution +are available with a special Enterprise Auditor license. See the [AWS Solution](/docs/accessanalyzer/11.6/solutions/aws/overview.md) topic for additional information. @@ -46,15 +47,15 @@ topic for additional information. **Sensitive Data Discovery Considerations** The Sensitive Data Discovery Add-On must be installed on the Enterprise Auditor Console server, -which enables Sensitive Data criteria for scans. If running Sensitive Data Discovery (SDD) scans, it -will be necessary to increase the minimum amount of RAM. Each thread requires a minimum of 2 +which enables Sensitive Data criteria for scans. If running Sensitive Data Discovery (SDD) scans, +increase the minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For example, if the job is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are required (8x2=16). ## AWS Query Configuration -The AWS Data Collector is configured through the Amazon Web Services Data Collector Wizard. The -wizard contains the following pages, which change based up on the query category selected: +Configure the AWS Data Collector through the Amazon Web Services Data Collector Wizard. The +wizard contains the following pages, which change based on the query category you select: - [AWS: Category](/docs/accessanalyzer/11.6/admin/datacollector/aws/category.md) - [AWS: Login Roles](/docs/accessanalyzer/11.6/admin/datacollector/aws/loginroles.md) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/aws/results.md b/docs/accessanalyzer/11.6/admin/datacollector/aws/results.md index 178c7939bc..723f80c7fb 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/aws/results.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/aws/results.md @@ -6,10 +6,11 @@ sidebar_position: 60 # AWS: Results -The Results page is where properties that will be gathered are selected. It is a wizard page for all +Use the Results page to select the properties to gather. It is a wizard page for all of the categories. ![Results page](/images/accessanalyzer/11.6/admin/datacollector/aws/results.webp) -Properties can be checked individually or the **Select All** or **Clear All** buttons can be used. -All checked properties are gathered. Available properties vary based on the category selected. +You can check properties individually, or use the **Select All** or **Clear All** buttons. +Enterprise Auditor gathers all checked properties. Available properties vary based on the category +selected. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/aws/sensitivedata.md b/docs/accessanalyzer/11.6/admin/datacollector/aws/sensitivedata.md index 8d939f7ce8..ffde7f3b03 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/aws/sensitivedata.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/aws/sensitivedata.md @@ -6,7 +6,7 @@ sidebar_position: 40 # AWS: Sensitive Data Settings -The Sensitive Data Settings page is where sensitive data discovery settings are configured. It is a +Use the Sensitive Data Settings page to configure sensitive data discovery settings. It is a wizard page for the category of Collect SDD Data. ![Sensitive Data Settings page](/images/accessanalyzer/11.6/admin/datacollector/aws/sensitivedata.webp) @@ -46,7 +46,7 @@ Configure the following options: - Spreadsheets - Text/Markup files -- Perform differential scan of – Enables you to choose whether to employ incremental scanning: +- Perform differential scan of – Choose whether to employ incremental scanning: - Files modified since last scan – Scans only files modified since the last scan - Files modified since [date] – Only scans files modified after the specified date @@ -54,7 +54,7 @@ Configure the following options: of days - Number of SDD scan processes [number] – Increases the number of SDD scanner processes that spawn - as part of a scan, increasing parallel scanning. The value should not exceed 2x the number of CPU + as part of a scan, increasing parallel scanning. The value shouldn't exceed 2x the number of CPU threads available. :::tip diff --git a/docs/accessanalyzer/11.6/admin/datacollector/aws/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/aws/summary.md index 10e5b4883b..c58b7a8458 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/aws/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/aws/summary.md @@ -10,6 +10,5 @@ The Summary page displays a summary of the configured query. It is a wizard page ![summary](/images/accessanalyzer/11.6/admin/datacollector/aws/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Amazon Web Services Data Collector Wizard to ensure that no accidental -clicks are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** to close +the Amazon Web Services Data Collector Wizard and avoid saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/category.md b/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/category.md index 020b9f42d7..8cec1e8662 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/category.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/category.md @@ -21,5 +21,5 @@ The two categories are: topic for more information. The Scan Entra ID category is the pre-configured setting for the .Entra ID Inventory Job Group. -Therefore, accessing the Entra ID Inventory DC Wizard from the query within that job group does not +Therefore, accessing the Entra ID Inventory DC Wizard from the query within that job group doesn't display the Category wizard page. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/configurejob.md b/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/configurejob.md index 6f12c1484b..67963e0688 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/configurejob.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/configurejob.md @@ -6,14 +6,14 @@ sidebar_position: 20 # Microsoft Entra ID Connection Profile & Host List -The AzureADInventory Data Collector requires a custom Connection Profile and host list to be created -and assigned to the job or job group conducting the data collection. The host inventory option -during host list creation makes it necessary to configure the Connection Profile first. +The AzureADInventory Data Collector requires you to create a custom Connection Profile and host +list, and assign them to the job or job group conducting the data collection. The host inventory +option during host list creation requires you to configure the Connection Profile first. ## Connection Profile -Creating the Connection Profile requires having the Client ID and Key that was generated when -Enterprise Auditor was registered as a web application with Microsoft Entra ID. See the +Creating the Connection Profile requires the Client ID and Key generated when you registered +Enterprise Auditor as a web application with Microsoft Entra ID. See the [Microsoft Entra ID Auditing Configuration](/docs/accessanalyzer/11.6/requirements/entraid/entraid/access.md) for additional information. @@ -33,7 +33,7 @@ Create a Connection Profile and set the following information on the User Creden [Generate the Client Secret Key](/docs/accessanalyzer/11.6/requirements/entraid/entraid/access.md#generate-the-client-secret-key) topic for additional information. -Once the Connection Profile is created, it is time to create the custom host list. See the +After you create the Connection Profile, create the custom host list. See the [Connection](/docs/accessanalyzer/11.6/admin/settings/connection/overview.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/customattributes.md b/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/customattributes.md index 96b5ddf68c..204675d91f 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/customattributes.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/customattributes.md @@ -6,8 +6,7 @@ sidebar_position: 50 # AzureADInventory: Custom Attributes -Use the Custom Attributes wizard page to define custom attributes that will be used in the Microsoft -Entra ID scan. +Use the Custom Attributes wizard page to define custom attributes for the Microsoft Entra ID scan. ![Entra ID Inventory Data Collector Wizard Custom Attributes page](/images/accessanalyzer/11.6/admin/datacollector/azureadinventory/customattributes.webp) @@ -21,7 +20,7 @@ Configuration options for Custom Attributes include: will only scan changes since the last scan was performed. :::warning - A full scan is required when new attributes are added or removed. + You must run a full scan when you add or remove attributes. ::: @@ -35,7 +34,7 @@ Configuration options for Custom Attributes include: Attributes Import Wizard. Use the **Add**, **Edit**, and **Remove** buttons at the bottom of the window to configure the -custom attributes to be gathered by the scan. Use the **Add** button to open the +custom attributes the scan gathers. Use the **Add** button to open the [Custom Attribute Window](#custom-attribute-window). The **Import** button opens the [Custom Attributes Import Wizard](#custom-attributes-import-wizard). @@ -48,7 +47,7 @@ window. The options on the Custom Attributes window are: -- Tenant Filter – Use a Tenant Name or wildcard to target the desired environment. Wildcards (\*) +- Tenant Filter – Use a Tenant Name or wildcard to target the environment you want. Wildcards (\*) can be used. - Object Class – One or more object class for the attribute can be selected: - User @@ -58,7 +57,7 @@ The options on the Custom Attributes window are: - Collect all sub-attributes – Allows the collection of sub-attributes - Sub-Attribute Name – Define the sub-attribute name. Wildcards (\*) can be used. -Repeat this process until all desired Custom Attributes have been included. Click **OK** to save the +Repeat this process until you include all desired Custom Attributes. Click **OK** to save the attribute. #### Custom Attributes Import Wizard @@ -72,8 +71,9 @@ Custom Attributes Import Wizard opens. ![Custom Attributes Import Wizard](/images/accessanalyzer/11.6/admin/datacollector/azureadinventory/customattributesimportwizard.webp) -**Step 2 –** On the Connection page, enter the Tenant Name of the instance of Microsoft Entra ID to -be targeted, and then select the method of supplying credentials for the specified tenant instance: +**Step 2 –** On the Connection page, enter the Tenant Name of the Microsoft Entra ID instance you +want to target, and then select the method of supplying credentials for the specified tenant +instance: - Use the following connection profile entry – Select an Azure Connection Profile from the dropdown list @@ -94,7 +94,7 @@ or the [Microsoft Entra ID Connection Profile & Host List](/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/configurejob.md) topics for additional information. -**Step 3 –** Click **Test Connection** in order to connect to the tenant with the supplied +**Step 3 –** Click **Test Connection** to connect to the tenant with the supplied credentials. If they are correct, the Schema Attributes and Application Attributes pages become available. Click **Next** to navigate to them. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/overview.md index 9fa942223c..8dea1ff3af 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/overview.md @@ -8,7 +8,7 @@ sidebar_position: 70 The AzureADInventory Data Collector catalogs user and group object information from Microsoft Entra ID, formerly Azure Active Directory. This data collector is a core component of Enterprise Auditor -and is preconfigured in the .Entra ID Inventory Solution. +and Netwrix preconfigures it in the .Entra ID Inventory Solution. Both this data collector and the solution are available with all Enterprise Auditor license options. See the @@ -50,7 +50,7 @@ topic for additional information. ## AzureADInventory Query Configuration -The AzureADInventory Data Collector is configured through the Entra ID Inventory DC Wizard, which +Configure the AzureADInventory Data Collector through the Entra ID Inventory DC Wizard, which contains the following wizard pages: - Welcome @@ -62,5 +62,5 @@ contains the following wizard pages: ![Entra ID Inventory Data Collector Wizard Welcome page](/images/accessanalyzer/11.6/admin/datacollector/azureadinventory/welcome.webp) -Hide the Welcome page the next time this data collected is accessed by selecting the **Do not +To hide the Welcome page the next time you access this data collector, select the **Don't display this page the next time** checkbox. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/results.md b/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/results.md index 3b2653b831..5281eabeaf 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/results.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/results.md @@ -6,12 +6,13 @@ sidebar_position: 60 # AzureADInventory: Results -The Results page is where the properties from Microsoft Entra ID to be gathered are selected. It is +Use the Results page to select the properties from Microsoft Entra ID to gather. It is a wizard page for the category of Scan Entra ID. ![Entra ID Inventory DC Wizard Results page](/images/accessanalyzer/11.6/admin/datacollector/azureadinventory/results.webp) -Properties can be checked individually or the **Select All** and **Clear All** buttons can be used. -All checked properties are collected. This information is not available within the standard -reference tables and views. Instead, this information can be viewed in the -**SA_AzureADInventory_DEFAULT** table, which is created when any of these properties are selected. +You can check properties individually, or use the **Select All** and **Clear All** buttons. +Enterprise Auditor collects all checked properties. This information isn't available within the +standard reference tables and views. Instead, you can view this information in the +**SA_AzureADInventory_DEFAULT** table, which Enterprise Auditor creates when you select any of +these properties. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/standardtables.md b/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/standardtables.md index 3427100659..3ba859981a 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/standardtables.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/standardtables.md @@ -10,7 +10,7 @@ The AzureADInventory Data Collector collects essential user and group inventory standard reference tables. Unlike other Enterprise Auditor data collectors, the AzureADInventory Data Collector writes data to these tables regardless of the job executing the query. -These tables and their associated views are outlined below: +The following table outlines these tables and their associated views: | Table | Details | | ----------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -27,7 +27,7 @@ These tables and their associated views are outlined below: | SA_AzureADInventory_Users | Contains extended information about users, department, title, and so on | Views are the recommended way for you to obtain the information gathered by the AzureADInventory -Data Collector. They contain additional information for building queries easily. The following is an +Data Collector. They contain additional information for building queries. The following is an explanation of the corresponding views created for some of the tables generated by the AzureADInventory Data Collector: @@ -43,7 +43,7 @@ AzureADInventory Data Collector: ### AzureADInventory Exception Types Translated -The following table translates the Type of Exceptions that can found. +The following table translates the types of exceptions you might encounter. | Type | Exception | Description | | ---- | -------------------- | ------------------------------------------------------------------------- | diff --git a/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/summary.md index b55ed855b9..c0b3b96258 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/summary.md @@ -6,11 +6,10 @@ sidebar_position: 70 # AzureADInventory: Summary -The Summary page is where configuration settings are summarized. It is a wizard page for both of the +The Summary page summarizes the configuration settings. It is a wizard page for both of the categories. ![Entra ID Inventory DC Wizard Summary page](/images/accessanalyzer/11.6/admin/datacollector/azureadinventory/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Entra ID Inventory DC Wizard to ensure that no accidental clicks are -saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** to close +the Entra ID Inventory DC Wizard and avoid saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/troubleshooting.md b/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/troubleshooting.md index d69b108d63..94cbe50746 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/troubleshooting.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/troubleshooting.md @@ -19,8 +19,8 @@ category task. **Step 3 –** Click **Next** and then **Finish** to close the Entra ID Inventory DC Wizard. Click **OK** to close the Query Properties window. -When the job is run, all of the AzureADInventory standard reference tables are removed from the -database. +When you run the job, Enterprise Auditor removes all of the AzureADInventory standard reference +tables from the database. ## Troubleshooting Error Messages @@ -28,12 +28,12 @@ Change the XML parameters to address the following errors: Error: Microsoft.Graph.ServiceException: Code: timeout Message: The request timed out -Update the `` parameter to update the number of retries to run the query. +Update the `` parameter to set the number of query retries. The default is 3. Error: An existing connection was forcible closed by the remote host -Update the `` parameter to update the max delta token age. The default is 6. +Update the `` parameter to set the maximum delta token age. The default is 6. See the [View Job XML File](/docs/accessanalyzer/11.6/admin/jobs/job/properties/viewxml.md) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/box/activityoperationscope.md b/docs/accessanalyzer/11.6/admin/datacollector/box/activityoperationscope.md index b1c066f5b8..cb8ac9770f 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/box/activityoperationscope.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/box/activityoperationscope.md @@ -6,13 +6,13 @@ sidebar_position: 70 # Box: Activity Operation Scope -The Activity Operation Scope page (ActivityOperationScope) is where Box Enterprise events can be -selected or unselected for scans. It is a wizard page for the Scan Box Activity category. +Use the Activity Operation Scope page (ActivityOperationScope) to select or unselect Box Enterprise +events for scans. It is a wizard page for the Scan Box Activity category. ![Box DC Wizard Activity Operation Scope page](/images/accessanalyzer/11.6/admin/datacollector/box/activityoperation.webp) -Event filters can be selected by group or the group may be expanded and the filters selected -individually. All selected filters are gathered from the Box environment. +You can select event filters by group, or expand the group and select filters individually. +Enterprise Auditor gathers all selected filters from the Box environment. Event filters include: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/box/activitytimeframescope.md b/docs/accessanalyzer/11.6/admin/datacollector/box/activitytimeframescope.md index fa09bd3e8b..a83f83b341 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/box/activitytimeframescope.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/box/activitytimeframescope.md @@ -6,8 +6,8 @@ sidebar_position: 60 # Box: Activity Timeframe Scope -The Activity Timespan Scope page (ActivityTimeframeScope) is where Box activity data collection is -configured. It is a wizard page for the Scan Box Activity category. +Use the Activity Timespan Scope page (ActivityTimeframeScope) to configure Box activity data +collection. It is a wizard page for the Scan Box Activity category. ![Box DC Wizard Activity Timespan Scope page](/images/accessanalyzer/11.6/admin/datacollector/box/activitytimeframe.webp) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/box/additionalscoping.md b/docs/accessanalyzer/11.6/admin/datacollector/box/additionalscoping.md index 9063678bdc..33a1bf6543 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/box/additionalscoping.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/box/additionalscoping.md @@ -6,7 +6,7 @@ sidebar_position: 50 # Box: Additional Scoping -The Additional Scoping page is where the scan can be limited by depth of the scan. It is a wizard +Use the Additional Scoping page to limit the scan by depth. It is a wizard page for the Scan Box Permissions category. ![Box DC Wizard Additional Scoping page](/images/accessanalyzer/11.6/admin/datacollector/box/additionalscoping.webp) @@ -14,7 +14,7 @@ page for the Scan Box Permissions category. Configure the scan depth level: - Limit scanned depth to: [number] level – Select the checkbox and set the scan depth level to the - desired depth. If this checkbox is not selected, then the entire Box environment will be scanned, + desired depth. If this checkbox isn't selected, then the entire Box environment will be scanned, according to the [Box: Exclusions Page](/docs/accessanalyzer/11.6/admin/datacollector/box/exclusions.md) settings. If the scoping depth is set to **0** then only root will be scanned. Each increment will diff --git a/docs/accessanalyzer/11.6/admin/datacollector/box/authenticate.md b/docs/accessanalyzer/11.6/admin/datacollector/box/authenticate.md index d504fce9b4..46b70744b0 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/box/authenticate.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/box/authenticate.md @@ -6,7 +6,7 @@ sidebar_position: 80 # Box: Authenticate -The Authenticate page is where connection to the Box environment is configured. It is a wizard page +Use the Authenticate page to configure the connection to the Box environment. It is a wizard page for all categories. ![Box DC Wizard Authentication page](/images/accessanalyzer/11.6/admin/datacollector/box/authentication.webp) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/box/exclusions.md b/docs/accessanalyzer/11.6/admin/datacollector/box/exclusions.md index d2ea84b4dc..b14c744d96 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/box/exclusions.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/box/exclusions.md @@ -6,21 +6,21 @@ sidebar_position: 30 # Box: Exclusions Page -The Exclude or Include folders page (ExclusionsPage) is where the scan can be limited to include or -to exclude folders within the Box Enterprise. It is a wizard page for of Scan Box Permissions +Use the Exclude or Include folders page (ExclusionsPage) to limit the scan to include or +exclude folders within the Box Enterprise. It is a wizard page for of Scan Box Permissions category. ![Box DC Wizard Exclude or Include folders page](/images/accessanalyzer/11.6/admin/datacollector/box/exclusions.webp) The options on the Exclusions Page are: -- Add as inclusion – Type the path of a folder in the text box to include in the scan. The folder +- Add as inclusion – Enter the path of a folder in the text box to include in the scan. The folder path must not include a slash at the end. - Example format: `/All Files/Folder/SubFolder` - Incorrect format: `/All Files/Folder/SubFolder/` -- Add as exclusion – Type the path of a folder in the text box to exclude from the scan +- Add as exclusion – Enter the path of a folder in the text box to exclude from the scan The **Remove** option will delete a selected folder from the list. The **Clear List** option will remove all folders from the list. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/box/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/box/overview.md index 85ee6431d3..4b81a5f14d 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/box/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/box/overview.md @@ -9,13 +9,12 @@ sidebar_position: 80 The Box Data Collector audits access, group membership, and content within a Box enterprise. :::note -If the Box Data Collector is used in a new job, outside of the Box Solution, it is -necessary to deselect the **Skip Hosts that do not respond to PING** option on the job’s -**Properties** > **Performance** tab. +If you use the Box Data Collector in a new job, outside of the Box Solution, deselect the +**Skip Hosts that don't respond to PING** option on the job’s **Properties** > **Performance** tab. ::: -The Box Data Collector has been preconfigured within the Box Solution. Both this data collector and +Netwrix preconfigures the Box Data Collector within the Box Solution. Both this data collector and the solution are available with a special Enterprise Auditor license. See the [Box Solution](/docs/accessanalyzer/11.6/solutions/box/overview.md) topic for additional information. @@ -36,8 +35,8 @@ topic for additional information. ## Box Query Configuration -The Box Data Collector is configured through the Box Data Collector Wizard. The wizard contains the -following pages, which change based up on the query category selected: +Configure the Box Data Collector through the Box Data Collector Wizard. The wizard contains the +following pages, which change based on the query category you select: - Welcome - [Box: Category](/docs/accessanalyzer/11.6/admin/datacollector/box/category.md) @@ -56,5 +55,5 @@ introductory and caution information about the Box Data Collector before proceed ![Box DC Wizard Welcome page](/images/accessanalyzer/11.6/admin/datacollector/box/welcome.webp) -The Welcome page can be hidden by checking the **Do not display this page the next time** box when -the wizard is open and configuration settings are saved. +To hide the Welcome page, check the **Don't display this page the next time** box while the wizard +is open, and save the configuration settings. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/box/results.md b/docs/accessanalyzer/11.6/admin/datacollector/box/results.md index 4d9bd5cb9b..5319c58864 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/box/results.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/box/results.md @@ -6,10 +6,11 @@ sidebar_position: 90 # Box: Results -The Results page is where properties that will be gathered are selected. It is a wizard page for all +Use the Results page to select the properties to gather. It is a wizard page for all categories. ![Box DC Wizard Results page](/images/accessanalyzer/11.6/admin/datacollector/box/results.webp) -Properties can be selected individually or the **Select All** or **Clear All** buttons can be used. -All selected properties will be gathered. Available properties vary based on the category selected. +You can select properties individually, or use the **Select All** or **Clear All** buttons. +Enterprise Auditor gathers all selected properties. Available properties vary based on the category +selected. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/box/scopebyuser.md b/docs/accessanalyzer/11.6/admin/datacollector/box/scopebyuser.md index d4b64f3e83..4bc79bdfb6 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/box/scopebyuser.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/box/scopebyuser.md @@ -6,8 +6,8 @@ sidebar_position: 40 # Box: Scope by User Page -The User Scope Settings page (ScopeByUserPage) is where the scope of the scan can be limited to -specified users and the resulting scan will only scan for the specified users. It is a wizard page +Use the User Scope Settings page (ScopeByUserPage) to limit the scope of the scan to +specified users; the resulting scan only scans for the specified users. It is a wizard page for the Scan Box Permissions category. ![Box DC Wizard User Scope Settings page](/images/accessanalyzer/11.6/admin/datacollector/box/scopebyuser.webp) @@ -18,8 +18,8 @@ included in the scan. The CSV file should have one email address per row. :::note The query will collect information related to User names and Group membership for all -users in a target environment. However, if the query is scoped to specific users, no additional -information is collected for users outside out of the scope. User names and group membership for the -target environment is necessary to generate the Box Solution reports. +users in a target environment. However, if you scope the query to specific users, Enterprise +Auditor doesn't collect additional information for users outside the scope. User names and group +membership for the target environment is necessary to generate the Box Solution reports. ::: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/box/standardtables.md b/docs/accessanalyzer/11.6/admin/datacollector/box/standardtables.md index a9dc756331..b113634a14 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/box/standardtables.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/box/standardtables.md @@ -7,7 +7,7 @@ sidebar_position: 10 # Standard Reference Tables & Views For the Box Data Collector The Box Data Collector gathers essential user and group inventory information into standard -reference tables. These tables and their associated views are outlined below: +reference tables. The following table outlines these tables and their associated views: | Table | Details | | -------------------------- | ----------------------------------------------------------------------------------------------------------------------- | @@ -28,7 +28,7 @@ reference tables. These tables and their associated views are outlined below: | SA_Box_Users | Contains one row per user and displays information on users of any teams present | Views are the recommended way for Enterprise Auditor users to obtain the information gathered by the -Box Data Collector. They contain additional information for building queries easily. The following +Box Data Collector. They contain additional information for building queries. The following is an explanation of the corresponding views created for some of the tables generated by the Box Data Collector: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/box/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/box/summary.md index feb45fbee9..cc64d0ff9b 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/box/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/box/summary.md @@ -6,11 +6,10 @@ sidebar_position: 100 # Box: Summary -The Summary page is where configuration settings are summarized. It is a wizard page for all of the +The Summary page summarizes the configuration settings. It is a wizard page for all of the categories. ![Box DC Wizard Summary page](/images/accessanalyzer/11.6/admin/datacollector/box/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Box Data Collector Wizard ensuring that no accidental clicks are -saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** to close +the Box Data Collector Wizard and avoid saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/commandlineutility/definefields.md b/docs/accessanalyzer/11.6/admin/datacollector/commandlineutility/definefields.md index 2062a34163..f591152bcd 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/commandlineutility/definefields.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/commandlineutility/definefields.md @@ -12,7 +12,7 @@ output. It is a wizard page for the **Edit Profile** and **Create a New Profile* ![Command Line Utility Data Collector Wizard Define Fields page](/images/accessanalyzer/11.6/admin/datacollector/commandlineutility/definefields.webp) :::warning -Do not modify this page without guidance from Netwrix or the data may not be processed -by Enterprise Auditor. +Don't modify this page without guidance from Netwrix, or Enterprise Auditor may not process the +data. ::: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/commandlineutility/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/commandlineutility/overview.md index ed4a8f2a03..2dbb2611b1 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/commandlineutility/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/commandlineutility/overview.md @@ -6,8 +6,8 @@ sidebar_position: 90 # CommandLineUtility Data Collector -The CommandLineUtility Data Collector provides the ability to remotely spawn, execute, and extract -data provided by a Microsoft native or third-party command line utility. It allows users to easily +The CommandLineUtility Data Collector lets you remotely spawn, execute, and extract +data provided by a Microsoft native or third-party command line utility. It lets you execute a command line utility and capture its output as Enterprise Auditor data. This data collector is a core component of Enterprise Auditor and is available with all Enterprise Auditor licenses. @@ -28,8 +28,8 @@ licenses. ## CommandLineUtility Query Configuration -The CommandLineUtility Data Collector executes a command line utility and captures the output. It is -configured through the Command Line Utility Data Collector Wizard, which contains the following +The CommandLineUtility Data Collector executes a command line utility and captures the output. +Configure it through the Command Line Utility Data Collector Wizard, which contains the following pages: - Welcome @@ -43,5 +43,5 @@ pages: ![Command Line Utility Data Collector Wizard Welcome page](/images/accessanalyzer/11.6/admin/datacollector/commandlineutility/welcome.webp) -The Welcome page can be hidden by selecting the **Do not display this page the next time** checkbox -when the wizard is open and configuration settings are saved. +To hide the Welcome page, select the **Don't display this page the next time** checkbox while the +wizard is open, and save the configuration settings. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/commandlineutility/profileparameters.md b/docs/accessanalyzer/11.6/admin/datacollector/commandlineutility/profileparameters.md index 67f8f965bb..e2eef672f1 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/commandlineutility/profileparameters.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/commandlineutility/profileparameters.md @@ -24,7 +24,7 @@ Profile parameters include: - Start in path for task (Optional) – Working directory for the command line that executes the program or script. This should be either the path to the program or script file, or the path to the files that are used by the executable file. -- Command Line – Command that the utility executes. If the utility is self-executable and does not +- Command Line – Command that the utility executes. If the utility is self-executable and doesn't need a command, leave this field blank. -- Output File Name – Enter the desired name for the output file. By default, the output file name +- Output File Name – Enter the name you want for the output file. By default, the output file name matches the profile name. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/commandlineutility/profiletype.md b/docs/accessanalyzer/11.6/admin/datacollector/commandlineutility/profiletype.md index 832918416f..5cf09b5e99 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/commandlineutility/profiletype.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/commandlineutility/profiletype.md @@ -12,10 +12,10 @@ The Profile Type page contains options to select a new or existing profile. The options on the Profile Type page are: -- Select Profile – Allows you to change the properties of a profile from the results page -- Edit Profile – Allows you to edit a profile's execution options and properties. Enables the Define +- Select Profile – Changes the properties of a profile from the results page +- Edit Profile – Edits a profile's execution options and properties. Enables the Define Fields and Script Editor pages. -- Create a New Profile – Allows you to create a new profile. Enables the Define Fields and Script +- Create a New Profile – Creates a new profile. Enables the Define Fields and Script Editor pages. The profile type selected may alter the availability of the subsequent wizard steps. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/commandlineutility/results.md b/docs/accessanalyzer/11.6/admin/datacollector/commandlineutility/results.md index 5f8726f46f..ea0bbefbee 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/commandlineutility/results.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/commandlineutility/results.md @@ -6,11 +6,11 @@ sidebar_position: 60 # CLU: Results -The Results page is where the properties to be returned as columns in the results table are -selected. It is a wizard page for all profile types. +Use the Results page to select the properties to return as columns in the results table. It is a +wizard page for all profile types. ![Command Line Utility Data Collector Wizard Results page](/images/accessanalyzer/11.6/admin/datacollector/commandlineutility/results.webp) -Select one or more properties to be returned as columns in the results table. Click **Select All** -to select all of the properties, or click **Clear All** to clear all the currently selected +Select one or more properties to return as columns in the results table. Click **Select All** +to select all of the properties, or click **Clear All** to clear all the selected properties. The available properties vary based on the selections on previous wizard pages. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/commandlineutility/scripteditor.md b/docs/accessanalyzer/11.6/admin/datacollector/commandlineutility/scripteditor.md index 3d0812db1d..376081dd97 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/commandlineutility/scripteditor.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/commandlineutility/scripteditor.md @@ -6,15 +6,15 @@ sidebar_position: 50 # CLU: Script Editor -The Script Editor page provides options to create or edit a Visual Basic script that is used to -parse the output file created by the data collector after execution. The Script Editor page is -enabled when **Edit Profile** or **Create a New Profile** is selected on the Profile Type page. The -page is disabled when the **Select Profile** option is selected on the Profile Type page. +The Script Editor page provides options to create or edit a Visual Basic script that parses the +output file the data collector creates after execution. Enterprise Auditor enables the Script Editor +page when you select **Edit Profile** or **Create a New Profile** on the Profile Type page, and +disables it when you select the **Select Profile** option on the Profile Type page. ![Command Line Utility Data Collector Wizard Script Editor page](/images/accessanalyzer/11.6/admin/datacollector/commandlineutility/scripteditor.webp) :::warning -Do not modify this page without guidance from Netwrix or the data may not be processed -by Enterprise Auditor. +Don't modify this page without guidance from Netwrix, or Enterprise Auditor may not process the +data. ::: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/commandlineutility/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/commandlineutility/summary.md index 5d5c10b8a4..12ba9ef200 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/commandlineutility/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/commandlineutility/summary.md @@ -6,11 +6,10 @@ sidebar_position: 70 # CLU: Summary -The Summary page provides a summary of the query that has been created or edited. It is a wizard +The Summary page provides a summary of the query you created or edited. It is a wizard page for all profile types. ![Command Line Utility Data Collector Wizard Summary page](/images/accessanalyzer/11.6/admin/datacollector/commandlineutility/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Command Line Utility Data Collector Wizard to ensure that no -accidental clicks are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** to close +the Command Line Utility Data Collector Wizard and avoid saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/diskinfo/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/diskinfo/overview.md index 8578260f6e..4b9dfc6b0f 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/diskinfo/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/diskinfo/overview.md @@ -6,8 +6,8 @@ sidebar_position: 100 # DiskInfo Data Collector -The DiskInfo Data Collector provides enumeration of disks and their associated properties. When -targeting the local host for a DiskInfo query, it is necessary to select the **Systems Default** +The DiskInfo Data Collector enumerates disks and their associated properties. When +targeting the local host for a DiskInfo query, select the **Systems Default** option as the connection profile. This data collector is a core component of Enterprise Auditor and is available with all Enterprise Auditor licenses. @@ -27,7 +27,7 @@ is available with all Enterprise Auditor licenses. ## DiskInfo Query Configuration -The DiskInfo Data Collector is configured through the Disk Info wizard, which contains the following +Configure the DiskInfo Data Collector through the Disk Info wizard, which contains the following wizard pages: - Welcome @@ -37,5 +37,5 @@ wizard pages: ![Disk Info wizard Welcome page](/images/accessanalyzer/11.6/admin/datacollector/diskinfo/welcome.webp) -The Welcome page can be hidden by selecting the **Do not display this page the next time** checkbox -when the wizard is open and configuration settings are saved. +To hide the Welcome page, select the **Don't display this page the next time** checkbox while the +wizard is open, and save the configuration settings. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/diskinfo/results.md b/docs/accessanalyzer/11.6/admin/datacollector/diskinfo/results.md index 86982c80d7..57a6adaaa7 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/diskinfo/results.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/diskinfo/results.md @@ -6,14 +6,14 @@ sidebar_position: 20 # DiskInfo: Results -The Results page provides a checklist of the data that is available for return by the query. Any -number of options can be selected at once, but at least one must be selected in order to complete +The Results page provides a checklist of the data that is available for return by the query. You +can select any number of options at once, but you must select at least one to complete the wizard. ![Disk Info wizard Results page](/images/accessanalyzer/11.6/admin/datacollector/diskinfo/results.webp) -Properties can be selected individually, or you can use the **Select all** and **Clear all** -buttons. The table below describes the available options. +You can select properties individually, or use the **Select all** and **Clear all** +buttons. The following table describes the available options. | Checklist Result | Description | | ----------------------------- | ------------------------------------------------------------------------------------------------------------------- | diff --git a/docs/accessanalyzer/11.6/admin/datacollector/diskinfo/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/diskinfo/summary.md index b5444f941e..702a53499e 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/diskinfo/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/diskinfo/summary.md @@ -10,6 +10,5 @@ The Summary page displays a summary of the configured query. ![Disk Info wizard Summary page](/images/accessanalyzer/11.6/admin/datacollector/diskinfo/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Disk Info Data Collector Wizard to ensure that no accidental clicks -are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** to close +the Disk Info Data Collector Wizard and avoid saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/diskinfo/targetdisks.md b/docs/accessanalyzer/11.6/admin/datacollector/diskinfo/targetdisks.md index ddead664e6..4a46474225 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/diskinfo/targetdisks.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/diskinfo/targetdisks.md @@ -11,9 +11,9 @@ target host after a query. ![Disk Info wizard Target Disks page](/images/accessanalyzer/11.6/admin/datacollector/diskinfo/targetdisks.webp) -Use the options to select the desired target disk. +Use the options to select the target disk you want. -- The Enumerate all storage devices – Allows all internal drives to be scanned. In order to expand +- The Enumerate all storage devices – Allows all internal drives to be scanned. to expand the scan, two sub-options can be included together, separately, or not at all. - Include removable storage devices – Scans removable devices that are plugged into the target diff --git a/docs/accessanalyzer/11.6/admin/datacollector/dns/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/dns/overview.md index 145d8669dc..cb96ec2cb0 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/dns/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/dns/overview.md @@ -25,7 +25,7 @@ special Enterprise Auditor license. ## DNS Query Configuration -The DNS Data Collector is configured through the Domain Name System Data Collector Wizard, which +Configure the DNS Data Collector through the Domain Name System Data Collector Wizard, which contains the following wizard pages: - Welcome @@ -35,5 +35,5 @@ contains the following wizard pages: ![Domain Name System Data Collector Wizard Welcome page](/images/accessanalyzer/11.6/admin/datacollector/dns/welcome.webp) -The Welcome page can be hidden by selecting the Do not display this page the next time checkbox when -the wizard is open and configuration settings are saved. +To hide the Welcome page, select the Don't display this page the next time checkbox while the +wizard is open, and save the configuration settings. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/dns/results.md b/docs/accessanalyzer/11.6/admin/datacollector/dns/results.md index 2479df0bf1..5297e9d71a 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/dns/results.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/dns/results.md @@ -6,11 +6,11 @@ sidebar_position: 20 # DNS: Results -The Results page is where DNS properties to be gathered are selected. It is a wizard page for all +Use the Results page to select the DNS properties to gather. It is a wizard page for all categories. ![Domain Name System Data Collector Wizard Results page](/images/accessanalyzer/11.6/admin/datacollector/dns/results.webp) -Available properties can be selected individually, or the **Select All**, **Clear All**, and **Reset -to defaults** buttons can be used. All selected properties are gathered. Available properties vary -based on the category selected. +You can select available properties individually, or use the **Select All**, **Clear All**, and +**Reset to defaults** buttons. Enterprise Auditor gathers all selected properties. Available +properties vary based on the category selected. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/dns/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/dns/summary.md index a894836ea5..07d14e8d0a 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/dns/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/dns/summary.md @@ -10,6 +10,5 @@ The Summary page displays a summary of the configured query. It is a wizard page ![Domain Name System Data Collector Wizard Summary page](/images/accessanalyzer/11.6/admin/datacollector/dns/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Domain Name System Data Collector Wizard to ensure that no accidental -clicks are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** to close +the Domain Name System Data Collector Wizard and avoid saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/completion.md b/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/completion.md index bc4c8be2ca..46304dd2db 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/completion.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/completion.md @@ -6,17 +6,16 @@ sidebar_position: 80 # DropboxAccess: Summary (Completion) -The Completion page, is where configuration settings are summarized. This page is a wizard page for -all categories. +Use the Completion page to review a summary of configuration settings. This page is a wizard page +for all categories. ![Dropbox Access Auditor Data Collector Wizard Completion page](/images/accessanalyzer/11.6/admin/datacollector/dropboxaccess/completion.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Dropbox Access Auditor Data Collector Wizard ensuring that no -accidental clicks are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** to close +the Dropbox Access Auditor Data Collector Wizard to avoid saving accidental clicks. :::tip -Remember, if an Access Token was generated, use it as the credential within the Connection +Remember, if you generated an Access Token, use it as the credential within the Connection Profile. Then assign it to the job group or job which will be scanning the targeted Dropbox environment. See the [Custom Dropbox Connection Profile & Host List](/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/configurejob.md) topic diff --git a/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/configurejob.md b/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/configurejob.md index fc0c85fadd..63fb0a1cd1 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/configurejob.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/configurejob.md @@ -6,12 +6,12 @@ sidebar_position: 20 # Custom Dropbox Connection Profile & Host List -The DropboxAccess Data Collector requires a custom Connection Profile to be created and assigned to -the job or job group conducting the data collection. +The DropboxAccess Data Collector requires you to create a custom Connection Profile and assign it +to the job or job group conducting the data collection. ## Connection Profile -Creating the Connection Profile requires an access token. The access token is generated on the Scan +Creating the Connection Profile requires an access token. You generate the access token on the Scan Options page of the Dropbox Access Auditor Data Collector Wizard. Create a Connection Profile and set the following information on the User Credentials window: @@ -32,6 +32,6 @@ topic for additional information. ## Host List -The host list should be set to: +Set the host list to: - Local host diff --git a/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/dlpauditsettings.md b/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/dlpauditsettings.md index 167aaf4cb4..5723b15fc6 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/dlpauditsettings.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/dlpauditsettings.md @@ -27,13 +27,13 @@ Configure the DLP audit settings: the scan: - Store discovered sensitive data – Stores a copy of any potentially sensitive data that matches - the selected criteria in the Enterprise Auditor database. This copy can be used to check for - false positives, data that matches the selected criteria but is not actually sensitive. + the selected criteria in the Enterprise Auditor database. Use this copy to check for + false positives, data that matches the selected criteria but isn't actually sensitive. - Limit stored matches per criteria to [number] – Identifies the number of potentially sensitive data matches that are copied to the database. The default is 5 matches. This option is available only if the **Store discovered sensitive data** option is selected. -- Perform differential scan of – Enables users to choose whether to employ incremental scanning: +- Perform differential scan of – Choose whether to employ incremental scanning: - Files modified since last scan – Scans only files modified since the last scan - Files modified since [date] – Only scans files modified after the specified date @@ -41,8 +41,8 @@ Configure the DLP audit settings: of days :::tip -Remember, the sensitive data discovery options require the Sensitive Data Discovery Add-On to have -been installed on the Enterprise Auditor Console. See the +Remember, the sensitive data discovery options require you to install the Sensitive Data Discovery +Add-On on the Enterprise Auditor Console. See the [Sensitive Data Discovery Add-On Installation](/docs/accessanalyzer/11.6/install/sensitivedatadiscovery/overview.md) topic for additional information. ::: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/overview.md index 669e23d7af..5dc546964c 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/overview.md @@ -8,8 +8,8 @@ sidebar_position: 120 The DropboxAccess Data Collector audits access, group membership, and content within a Dropbox environment. Dropbox can scan the contents of over 400 file types to discover which files contain -sensitive data using the Sensitive Data Discovery Add-on. The DropboxAccess Data Collector has been -preconfigured within the Dropbox Solution. Both this data collector and the solution are available +sensitive data using the Sensitive Data Discovery Add-on. Netwrix preconfigures the DropboxAccess +Data Collector within the Dropbox Solution. Both this data collector and the solution are available with a special Enterprise Auditor license. See the [Dropbox Solution](/docs/accessanalyzer/11.6/solutions/dropbox/overview.md) topic for additional information. @@ -31,16 +31,15 @@ topic for additional information. **Sensitive Data Discovery Considerations** The Sensitive Data Discovery Add-On must be installed on the Enterprise Auditor Console server, -which enables Sensitive Data criteria for scans. If running Sensitive Data Discovery (SDD) scans, it -will be necessary to increase the minimum amount of RAM. Each thread requires a minimum of 2 -additional GB of RAM per host. For example, if the job is configured to scan 8 hosts at a time , -then an extra 16 GB of RAM are required (8x2=16). +which enables Sensitive Data criteria for scans. If you run Sensitive Data Discovery (SDD) scans, increase the minimum amount of RAM. Each thread +requires a minimum of 2 additional GB of RAM per host. For example, if you configure the job to +scan 8 hosts at a time, it requires an extra 16 GB of RAM (8x2=16). ## Query Configuration -The DropboxAccess Data Collector is configured through the Dropbox Access Auditor Data Collector -Wizard. The wizard contains the following pages, which change based upon the query category -selected: +Configure the DropboxAccess Data Collector through the Dropbox Access Auditor Data Collector +Wizard. The wizard contains the following pages, which change based on the query category you +select: - Welcome - [DropboxAccess: Category](/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/category.md) @@ -52,5 +51,5 @@ selected: ![Dropbox Access Auditor Data Collector Wizard Welcome page](/images/accessanalyzer/11.6/admin/datacollector/dropboxaccess/welcome.webp) -The Welcome page can be hidden by selecting the **Do not display this page the next time** checkbox -when the wizard is open and configuration settings are saved. +To hide the Welcome page, select the **Don't display this page the next time** checkbox while the +wizard is open, and save the configuration settings. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/scanoptions.md b/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/scanoptions.md index cb8d995385..06daec978a 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/scanoptions.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/scanoptions.md @@ -11,8 +11,8 @@ DropboxAccess Data Collector to access and scan an organization’s Dropbox envi Token is used as the credential in the Connection Profile. :::note -The Access Token needs to be generated only once, prior to the first execution of any job -in which the DropboxAccess Data Collector is used in a query. +You need to generate the Access Token only once, before the first execution of any job +that uses the DropboxAccess Data Collector in a query. ::: @@ -21,7 +21,7 @@ The Scan Options page is a wizard page for the following categories: - Scan Dropbox Access - Scan for Sensitive Content -Follow the steps to create the Access Token: +To create the Access Token: ![Dropbox Access Auditor Data Collector Wizard Scan Options page](/images/accessanalyzer/11.6/admin/datacollector/dropboxaccess/scanoptions.webp) @@ -33,7 +33,7 @@ Follow the steps to create the Access Token: ![Copy Access Token](/images/accessanalyzer/11.6/admin/datacollector/dropboxaccess/scanoptionsaccesstoken.webp) -**Step 3 –** Once the Access Token has been generated, click **Copy to Clipboard**. Click **Next** +**Step 3 –** After Enterprise Auditor generates the Access Token, click **Copy to Clipboard**. Click **Next** to finish choosing the configuration options or click **Cancel** to close the Dropbox Access Auditor Data Collector Wizard. @@ -42,6 +42,6 @@ Create a Connection Profile using this access token as the credential. See the topic for additional information on configuring the Dropbox credential. :::tip -Remember, assign this Connection Profile to the job group or job where the host assignment for the -Dropbox environment to be targeted has been assigned. +Remember, assign this Connection Profile to the job group or job that has the host assignment for +the targeted Dropbox environment. ::: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/selectdlpcriteria.md b/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/selectdlpcriteria.md index f1a5b5154e..31abf4607a 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/selectdlpcriteria.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/selectdlpcriteria.md @@ -7,7 +7,7 @@ sidebar_position: 70 # DropboxAccess: Select DLP Criteria Use the Select DLP criteria for this scan page to configure criteria to use for discovering -sensitive data. This page requires the Sensitive Data Discovery Add-On to be been installed on the +sensitive data. This page requires you to install the Sensitive Data Discovery Add-On on the Enterprise Auditor Console to define the criteria and enable the Criteria Editor. See the [Sensitive Data Discovery Add-On Installation](/docs/accessanalyzer/11.6/install/sensitivedatadiscovery/overview.md) topic for additional information. @@ -17,7 +17,7 @@ category. ![Dropbox Access Auditor Data Collector Wizard Select DLP criteria page](/images/accessanalyzer/11.6/admin/datacollector/dropboxaccess/selectdlpcriteria.webp) -Select the checkbox next to each criteria to be included in the search for sensitive data. You can +Select the checkbox next to each criteria to include it in the search for sensitive data. You can also use the **Select All** and **Clear All** buttons. The table contains the following types of criteria: @@ -26,12 +26,12 @@ The table contains the following types of criteria: - User Criteria – Lists user-defined criteria :::note -Until the Sensitive Data Discovery Add-On is installed, only the headers for the System +Until you install the Sensitive Data Discovery Add-On, only the headers for the System Criteria and User Criteria nodes are visible in the table. ::: -Use the **Edit** button to access the Criteria Editor where user-defined criteria can be created or -customized. See the +Use the **Edit** button to access the Criteria Editor, where you can create or customize +user-defined criteria. See the [Sensitive Data Criteria Editor](/docs/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/overview.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/standardtables.md b/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/standardtables.md index 4eeaba2c74..c1e1882208 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/standardtables.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/standardtables.md @@ -12,7 +12,7 @@ DropboxAccess Data Collector writes data to these tables regardless of the job e ## Dropbox Access Auditing Tables & Views -These tables and their associated views are outlined below: +The following table outlines these tables and their associated views: | Table | Details | | --------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | @@ -40,7 +40,7 @@ Data Collector: ## Dropbox Sensitive Data Discovery Auditing (SEEK) Tables & Views -These tables and their associated views are outlined below: +The following table outlines these tables and their associated views: | Table | Details | | -------------------- | ------------------------------------------------------------------------------------------------------------------------ | diff --git a/docs/accessanalyzer/11.6/admin/datacollector/eventlog.md b/docs/accessanalyzer/11.6/admin/datacollector/eventlog.md index ee5cc9ba7a..9ea96ca46c 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/eventlog.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/eventlog.md @@ -27,7 +27,7 @@ Enterprise Auditor licenses. ## EventLog Query Configuration -The EventLog Data Collector is configured through the Event Log Browser window. +Configure the EventLog Data Collector through the Event Log Browser window. ![Event Log Browser window](/images/accessanalyzer/11.6/admin/datacollector/eventlogbrowser.webp) @@ -39,7 +39,7 @@ In the Sample section, select from the following options: - Host – Enter a sample host that contains a log with the type of events desired for the query. Click **Connect** to generate a list of logs available for extraction. - - Log name – Select a log from the drop-down list. Events from the selected log are populated in + - Log name – Select a log from the dropdown list. Events from the selected log are populated in the table. - From file @@ -51,7 +51,7 @@ In the Sample section, select from the following options: File path box :::note - A preview displays automatically if the folder icons is used to navigate to the log. + A preview displays automatically if you use the folder icon to navigate to the log. ::: @@ -62,11 +62,11 @@ In the Sample section, select from the following options: In the Search Criteria section, add a search filter to the table by configuring the following criteria: -- Event Source – Select the event source from the drop-down list. Typically, select **Any Source**. -- Even Type – Select the event type from the drop-down list. Typically, select **Any Type**. +- Event Source – Select the event source from the dropdown list. Typically, select **Any Source**. +- Even Type – Select the event type from the dropdown list. Typically, select **Any Type**. - Event ID – Enter the event ID for the type of event to search -Once the information above has been entered, click **Add** to add the configured event to the query. +After you enter this information, click **Add** to add the configured event to the query. Add as many events as desired. - Latest event only – Select this checkbox to only search the latest event @@ -83,7 +83,7 @@ Click **Apply Filter** to filter the list of sample events to the search criteri **Options** -In the Options section, select the desired processing options: +In the Options section, select the processing options you want: - Process offline logs only – Select this checkbox to process only offline logs - Process offline logs if required – Select this checkbox to process offline logs if needed @@ -93,14 +93,14 @@ In the Options section, select the desired processing options: **Available Properties** -In the Available Properties section, select which properties will be collected by the browser. +In the Available Properties section, select which properties the browser collects. - Add Icon – Add properties from those available in the list to add the properties to the search - - The Description properties provide the ability to extract the bracketed pieces of information + - The Description properties let you extract the bracketed pieces of information found within the description and display each bracketed piece of information in its own column - Remove Icon – Use to remove properties from the search -Once all options have been configured, click **OK** to save changes and exit the browser. Click +After you configure all options, click **OK** to save changes and exit the browser. Click **Cancel** to exit without saving. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/category.md b/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/category.md index c23088fa71..7fa3a4745a 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/category.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/category.md @@ -6,7 +6,7 @@ sidebar_position: 10 # EWSMailbox: Category -The Category page identifies which type of EWSMailbox information is retrieved during the scan. +The Category page identifies which type of EWSMailbox information the scan retrieves. ![EWS Mailbox Data Collector Wizard Category page](/images/accessanalyzer/11.6/admin/datacollector/ewsmailbox/category.webp) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/criteria.md b/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/criteria.md index f587e4d35c..b5c81ee60e 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/criteria.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/criteria.md @@ -6,10 +6,10 @@ sidebar_position: 60 # EWSMailbox: Criteria -The Select DLP criteria for this scan page is where to select the criteria to use for the sensitive -data scan are selected. It is a wizard page for the Sensitive Data category. +Use the Select DLP criteria for this scan page to select the criteria to use for the sensitive +data scan. It is a wizard page for the Sensitive Data category. -This page requires the Sensitive Data Discovery Add-On to be been installed on the Enterprise +This page requires you to install the Sensitive Data Discovery Add-On on the Enterprise Auditor Console to define the criteria and enable the Criteria Editor. See the [Sensitive Data Discovery Add-On Installation](/docs/accessanalyzer/11.6/install/sensitivedatadiscovery/overview.md) topic for additional information. @@ -32,7 +32,7 @@ The options on the Criteria page are: The table contains the following types of criteria: :::note -Until the Sensitive Data Discovery Add-On is installed, only the headers for the System +Until you install the Sensitive Data Discovery Add-On, only the headers for the System Criteria and User Criteria nodes are visible in the table. ::: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/filter.md b/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/filter.md index 34c718604d..e57eada4d2 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/filter.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/filter.md @@ -15,13 +15,13 @@ the categories of: ![EWS Mailbox Data Collector Wizard Filter page](/images/accessanalyzer/11.6/admin/datacollector/ewsmailbox/filter.webp) -All folders and attachments are scanned by default. Scope the scan for specific folders and -attachments: +Enterprise Auditor scans all folders and attachments by default. Scope the scan for specific +folders and attachments: -- Include Folders – Type the folder paths to filter the scan to specific mailbox folders -- Include Attachments – Type the attachment file names to filter to specific attachments -- Exclude Folders – Type the folder paths to exclude mailbox folders from the scan -- Exclude Attachments – Type the file names for the attachments to exclude attachments from the scan +- Include Folders – Enter the folder paths to filter the scan to specific mailbox folders +- Include Attachments – Enter the attachment file names to filter to specific attachments +- Exclude Folders – Enter the folder paths to exclude mailbox folders from the scan +- Exclude Attachments – Enter the file names for the attachments to exclude attachments from the scan Use `*` and `?` for matching wildcard and single characters. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/options.md b/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/options.md index 82d32664b6..6ef9a11e3b 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/options.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/options.md @@ -27,7 +27,7 @@ Select the checkboxes to apply any desired scan options: - Scan archives – Scans for archived mailbox data - Scan recoverable items – Scans for recoverable items -- Authentication – Select an Authentication type from the drop down: +- Authentication – Select an Authentication type from the dropdown: - Negotiate - Basic diff --git a/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/overview.md index d56d758b86..7f650ae421 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/overview.md @@ -7,8 +7,8 @@ sidebar_position: 140 # EWSMailbox Data Collector The EWSMailbox Data Collector provides configuration options to scan mailbox contents, permissions, -and sensitive data, and is preconfigured within the Exchange Solution. Both this data collector and -the solution are available with a special Enterprise Auditor license. See the +and sensitive data. Netwrix preconfigures it within the Exchange Solution. Both this data collector +and the solution are available with a special Enterprise Auditor license. See the [Exchange Solution](/docs/accessanalyzer/11.6/solutions/exchange/overview.md) topic for additional information. @@ -33,14 +33,13 @@ topic for additional information. **Sensitive Data Discovery Considerations** The Sensitive Data Discovery Add-On must be installed on the Enterprise Auditor Console server, -which enables Sensitive Data criteria for scans. If running Sensitive Data Discovery (SDD) scans, it -will be necessary to increase the minimum amount of RAM. Each thread requires a minimum of 2 -additional GB of RAM per host. For example, if the job is configured to scan 8 hosts at a time , -then an extra 16 GB of RAM are required (8x2=16). +which enables Sensitive Data criteria for scans. If you run Sensitive Data Discovery (SDD) scans, increase the minimum amount of RAM. Each thread +requires a minimum of 2 additional GB of RAM per host. For example, if you configure the job to +scan 8 hosts at a time, it requires an extra 16 GB of RAM (8x2=16). ## EWSMailbox Query Configuration -The EWSMailbox Data Collector is configured through the Exchange Mailbox Data Collector Wizard, +Configure the EWSMailbox Data Collector through the Exchange Mailbox Data Collector Wizard, which contains the following wizard pages: :::note diff --git a/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/results.md b/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/results.md index 8c1be99693..5ae020732b 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/results.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/results.md @@ -6,7 +6,7 @@ sidebar_position: 90 # EWSMailbox: Results -Use the Results page to select which properties are gathered out of those available for the +Use the Results page to select which properties to gather out of those available for the category. It is a wizard page for all of the categories. ![EWS Mailbox Data Collector Wizard Results page](/images/accessanalyzer/11.6/admin/datacollector/ewsmailbox/results.webp) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/scope.md b/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/scope.md index 778a3d32f1..5828dccda0 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/scope.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/scope.md @@ -6,12 +6,12 @@ sidebar_position: 30 # EWSMailbox: Scope -The Mailbox scope settings page is used to select which mailboxes are searched by the scan. It is a +Use the Mailbox scope settings page to select which mailboxes the scan searches. It is a wizard page for all categories. ![EWS Mailbox Data Collector Wizard Scope page](/images/accessanalyzer/11.6/admin/datacollector/ewsmailbox/scope.webp) -Select an option to specify which mailboxes are searched: +Select an option to specify which mailboxes to search: - All mailboxes – Search all mailboxes - Select mailboxes from list – Search only specific selected mailboxes. This option enables the diff --git a/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/scopeselect.md b/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/scopeselect.md index 42962d38fc..d3bee34061 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/scopeselect.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/scopeselect.md @@ -6,8 +6,8 @@ sidebar_position: 40 # EWSMailbox: Scope Select -The Scope select page is used to select specific mailboxes to scan. It is a wizard page for all -categories when the **Select mailboxes from list** option is selected on the +Use the Scope select page to select specific mailboxes to scan. It is a wizard page for all +categories when you select the **Select mailboxes from list** option on the [EWSMailbox: Scope](/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/scope.md) page. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/sddoptions.md b/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/sddoptions.md index dbb5879759..e035f3ca9e 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/sddoptions.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/sddoptions.md @@ -6,8 +6,8 @@ sidebar_position: 50 # EWSMailbox: SDD Options -The Sensitive data scan options page is where options to be used for discovering sensitive data are -configured. It is a wizard page for the Sensitive Data category. +Use the Sensitive data scan options page to configure options for discovering sensitive data. It is +a wizard page for the Sensitive Data category. The Sensitive Data Discovery Add-on is required to use the sensitive data collection option. See the [Sensitive Data Discovery Add-On Installation](/docs/accessanalyzer/11.6/install/sensitivedatadiscovery/overview.md) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/searchfilter/bodyoptions.md b/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/searchfilter/bodyoptions.md index 466de0ccdc..dff23d1c5c 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/searchfilter/bodyoptions.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/searchfilter/bodyoptions.md @@ -10,7 +10,7 @@ Use the BodyOptions page to select the size unit of messages. ![Filter Wizard BodyOptions page](/images/accessanalyzer/11.6/admin/datacollector/ewsmailbox/filterwizard/bodyoptions.webp) -Select the desired message size unit: +Select the message size unit you want: - KB - MB diff --git a/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/searchfilter/folderconditions.md b/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/searchfilter/folderconditions.md index 9f833582bd..548f4752e9 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/searchfilter/folderconditions.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/searchfilter/folderconditions.md @@ -33,7 +33,7 @@ Customize folder search conditions using the following options: ## Folder Type Window Use the Folder Type window to determine folder types to search for. The Folder Type window opens if -**specific** is selected in the Edit Conditions box on the Folder Conditions page. +you select **specific** in the Edit Conditions box on the Folder Conditions page. ![Folder Type window](/images/accessanalyzer/11.6/admin/datacollector/ewsmailbox/filterwizard/foldertypewindow.webp) @@ -42,17 +42,17 @@ Select the checkbox next to any folder type to include it in the search filter. ## Search Terms Window Use the Search Terms window to determine terms for the search. The Search Terms window opens if -**search terms** is selected in the Edit Conditions box. +you select **search terms** in the Edit Conditions box. ![Search Terms window](/images/accessanalyzer/11.6/admin/datacollector/ewsmailbox/filterwizard/searchtermswindow.webp) Determine terms for the search using the following options: -- Type the desired term into the upper text box and click **Add** to add the term to the lower text +- Enter the term you want into the upper text box and click **Add** to add the term to the lower text box, which adds the term to the search - Select a term in the lower text box, and click **Remove** to remove the term from the search - Click **Clear** to clear all terms from the lower box -- Select the desired qualifier option: +- Select the qualifier option you want: - Contains ALL of the following search terms (And) – Search only returns results containing all of the search terms diff --git a/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/searchfilter/messageconditions.md b/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/searchfilter/messageconditions.md index 6e3eb9a498..711923302f 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/searchfilter/messageconditions.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/searchfilter/messageconditions.md @@ -63,20 +63,20 @@ Customize message search filter conditions using the following options: - Click **search terms** to open the Search Terms Window. See the [Search Terms Window (Message Conditions)](#search-terms-window-message-conditions) topic for additional information. - - Click **has attachment(s)** to convert the condition to **has no attachment(s)** and vice + - Click **has attachments** to convert the condition to **has no attachments** and vice versa ## MessageClasses Window (Message Conditions) Use the MessageClasses window to alter criteria related to message class. The Message Classes window -opens if **specific** is clicked in the Edit Conditions box on the Message Conditions page. +opens if you click **specific** in the Edit Conditions box on the Message Conditions page. ![MessagesClasses window](/images/accessanalyzer/11.6/admin/datacollector/ewsmailbox/filterwizard/messageclassesmessage.webp) Determine MessageClass-related criteria using the following options: - To add a class, click **Add** -- Enter the desired Message Class in the corresponding textbox +- Enter the Message Class you want in the corresponding textbox - Click **Exact Match** to reveal a dropdown menu of other search criteria under Matching Strategy and select the preferred option: @@ -91,7 +91,7 @@ Determine MessageClass-related criteria using the following options: ## Date Range Selection Window Use the Date Range Selection window to select a time period or range for the search. The Date Range -Selection window opens if **in specific date** is clicked in the Edit Conditions box on the Message +Selection window opens if you click **in specific date** in the Edit Conditions box on the Message Conditions page. ![Date Range Selection window](/images/accessanalyzer/11.6/admin/datacollector/ewsmailbox/filterwizard/daterangeselectionmessage.webp) @@ -107,17 +107,17 @@ Determine the time period or range of the search using the following options: ## Search Terms Window (Message Conditions) Use the Search Terms window to determine terms for the search. The Search Terms window opens if -**search terms** is selected in the Edit Conditions box. +you select **search terms** in the Edit Conditions box. ![Search Terms window](/images/accessanalyzer/11.6/admin/datacollector/ewsmailbox/filterwizard/searchtermswindow.webp) Determine terms for the search using the following options: -- Type the desired term into the upper text box and click **Add** to add the term to the lower text +- Enter the term you want into the upper text box and click **Add** to add the term to the lower text box, which adds the term to the search - Select a term in the lower text box, and click **Remove** to remove the term from the search - Click **Clear** to clear all terms from the lower box -- Select the desired qualifier option: +- Select the qualifier option you want: - Contains ALL of the following search terms (And) – Search only returns results containing all of the search terms diff --git a/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/searchfilter/searchfilter_1.md b/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/searchfilter/searchfilter_1.md index 3dd187682c..5a862aeb64 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/searchfilter/searchfilter_1.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/searchfilter/searchfilter_1.md @@ -26,18 +26,18 @@ Customize folder search conditions using the following options: ::: - - Click either **IPM.Note** or **IPM.Appointment**, to open the MessageClasses Window with + - Click either **IPM.Note** or **IPM.Appointment** to open the MessageClasses Window with IPM.Note or IPM.Appointment class populated, respectively. See the [MessageClasses Window ](#messageclasses-window) topic for additional information. - Click **over 90 Day ago** to open the Date Range Selection Window. See the [Date Range Selection Window](#date-range-selection-window) topic for additional information. - - Click **has attachment(s)** to convert the condition to **has no attachment(s)** and vice + - Click **has attachments** to convert the condition to **has no attachments** and vice versa ## MessageClasses Window Use the MessageClasses window to alter criteria related to message class. The Message Classes window -opens if **Ipm.Note** or **Ipm.Appointment** is clicked in the Edit Conditions box on the Search +opens if you click **Ipm.Note** or **Ipm.Appointment** in the Edit Conditions box on the Search Filter page. ![MessagesClasses window](/images/accessanalyzer/11.6/admin/datacollector/ewsmailbox/filterwizard/messageclassessearchfilter.webp) @@ -45,7 +45,7 @@ Filter page. Determine MessageClass-related criteria using the following options: - To add a class, click **Add** -- Enter the desired Message Class in the corresponding textbox +- Enter the Message Class you want in the corresponding textbox - Click **Exact Match** to reveal a dropdown menu of other search criteria under Matching Strategy and select the preferred option: @@ -60,7 +60,7 @@ Determine MessageClass-related criteria using the following options: ## Date Range Selection Window Use the Date Range Selection window to select a time period or range for the search. The Date Range -Selection window opens if **over 90 Day ago** is clicked in the Edit Conditions box on the Search +Selection window opens if you click **over 90 Day ago** in the Edit Conditions box on the Search Filter page. ![Date Range Selection window](/images/accessanalyzer/11.6/admin/datacollector/ewsmailbox/filterwizard/daterangeselectionsearchfilter.webp) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/summary.md index fd4446325d..3130f67319 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/summary.md @@ -10,6 +10,5 @@ The Summary page displays a summary of the configured query. It wizard page for ![EWS Mailbox Data Collector Wizard Summary page](/images/accessanalyzer/11.6/admin/datacollector/ewsmailbox/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the EWS Mailbox Data Collector Wizard to ensure that no accidental clicks -are saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** +instead to close the EWS Mailbox Data Collector Wizard without saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/critieria.md b/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/critieria.md index 6fbf4bff90..d6b9fee304 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/critieria.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/critieria.md @@ -26,13 +26,13 @@ The options on the Criteria page are: sensitive data criteria to scan for - Select All - Click **Select All** to enable all sensitive data criteria for scanning - Clear All - Click **Clear All** to remove all selections from the table -- Select the checkboxes next to the sensitive data criteria options to enable it to be scanned for +- Select the checkboxes next to the sensitive data criteria options to include them in the scan during job execution The table contains the following types of criteria: :::note -Until the Sensitive Data Discovery Add-On is installed, only the headers for the System +Until you install the Sensitive Data Discovery Add-On, only the headers for the System Criteria and User Criteria nodes are visible in the table. ::: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/filter.md b/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/filter.md index e4b58bd93f..7866458feb 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/filter.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/filter.md @@ -15,13 +15,13 @@ the categories of: ![EWS Public Folder Data Collector Wizard Filter page](/images/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/filter.webp) -All folders and attachments are scanned by default. Scope the scan for specific folders and +The scan includes all folders and attachments by default. Scope the scan for specific folders and attachments: -- Include Folders – Type the folder paths to filter the scan to specific mailbox folders -- Include Attachments – Type the attachment file names to filter to specific attachments -- Exclude Folders – Type the folder paths to exclude mailbox folders from the scan -- Exclude Attachments – Type the file names for the attachments to exclude attachments from the scan +- Include Folders – Enter the folder paths to filter the scan to specific mailbox folders +- Include Attachments – Enter the attachment file names to filter to specific attachments +- Exclude Folders – Enter the folder paths to exclude mailbox folders from the scan +- Exclude Attachments – Enter the file names for the attachments to exclude attachments from the scan Use `*` and `?` for matching wildcard and single characters. @@ -30,10 +30,10 @@ Use `*` and `?` for matching wildcard and single characters. - Limit attachments size to [numerical value] – Select to limit attachment size and define a threshold for maximum size of an attachment returned in the scan. The default value is 20000 KB. -Public folders can also be included or excluded from the scan by retrieving a list of public folders -and selecting the desired folders. +You can also include or exclude public folders from the scan by retrieving a list of public folders +and selecting the folders you want. -Follow the steps to filter the scan by selecting public folders from a list. +To filter the scan by selecting public folders from a list: ![Choose folder to include window on Filter settings page](/images/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/filterpublicfolders.webp) @@ -42,7 +42,8 @@ open the Choose folders to include or Choose folders to exclude window. **Step 2 –** Click **Retrieve** to load the list of public folders that can be selected. -**Step 3 –** Select the desired public folders and click **Add** to add the folders to the Include +**Step 3 –** Select the public folders you want and click **Add** to add the folders to the Include Folders or Exclude Folders list. -After the configuration changes are saved, scans are filtered by the selected public folders. +After you save the configuration changes, the data collector filters scans by the selected public +folders. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/options.md b/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/options.md index f71aa21c9c..c2f8145b5d 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/options.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/options.md @@ -22,7 +22,7 @@ Select any desired scan options: ::: -- Authentication – Select an Authentication type from the drop down: +- Authentication – Select an Authentication type from the dropdown: - Negotiate - Basic diff --git a/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/overview.md index dcd7f55988..a22593a6d5 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/overview.md @@ -32,11 +32,11 @@ topic for additional information. **Sensitive Data Discovery Considerations** -The Sensitive Data Discovery Add-On must be installed on the Enterprise Auditor Console server, -which enables Sensitive Data criteria for scans. If running Sensitive Data Discovery (SDD) scans, it -will be necessary to increase the minimum amount of RAM. Each thread requires a minimum of 2 -additional GB of RAM per host. For example, if the job is configured to scan 8 hosts at a time , -then an extra 16 GB of RAM are required (8x2=16). +You must install the Sensitive Data Discovery Add-On on the Enterprise Auditor Console server to +enable Sensitive Data criteria for scans. If you run Sensitive Data Discovery (SDD) scans, increase +the minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For +example, if you configure the job to scan 8 hosts at a time, you need an extra 16 GB of RAM +(8 x 2 = 16). ## EWSPublicFolder Query Configuration diff --git a/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/results.md b/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/results.md index 7b7b8dbf25..3a8f627709 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/results.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/results.md @@ -6,15 +6,15 @@ sidebar_position: 70 # EWSPublicFolder: Results -The Results page is used to select which properties will be gathered out of those available for the -category. It is a wizard page for all of the categories. +Use the Results page to select which properties to gather out of those available for the category. +It is a wizard page for all of the categories. ![EWS Public Folder Data Collector Wizard Results page](/images/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/results.webp) Select criteria using the following options: -- Select the checkbox of any property to include it in the summary. All selected properties will be - gathered. +- Select the checkbox of any property to include it in the summary. The data collector gathers all + selected properties. :::note Available properties vary based on the category selected. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/searchfilter/bodyoptions.md b/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/searchfilter/bodyoptions.md index 9e8dac56fd..e47f5e75a1 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/searchfilter/bodyoptions.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/searchfilter/bodyoptions.md @@ -6,11 +6,11 @@ sidebar_position: 40 # EWSPublicFolder FW: BodyOptions -The BodyOptions page is where the size of messages is selected. +Use the BodyOptions page to select the size of messages. ![Filter Wizard BodyOptions page](/images/accessanalyzer/11.6/admin/datacollector/ewsmailbox/filterwizard/bodyoptions.webp) -Select the desired message size unit: +Select the message size unit you want: - KB - MB diff --git a/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/searchfilter/folderconditions.md b/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/searchfilter/folderconditions.md index 3092c48c3e..aa207105de 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/searchfilter/folderconditions.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/searchfilter/folderconditions.md @@ -6,7 +6,7 @@ sidebar_position: 20 # EWSPublicFolder FW: Folder Conditions -The Folder Conditions page is where folder-related filter criteria can be applied to the search. +Use the Folder Conditions page to apply folder-related filter criteria to the search. ![Filter Wizard Folder Conditions page](/images/accessanalyzer/11.6/admin/datacollector/ewsmailbox/filterwizard/folderconditions.webp) @@ -33,7 +33,7 @@ Customize folder search conditions using the following options: ## Folder Type Window Use the Folder Type window to determine folder types to search for. The Folder Type window opens if -**specific** is selected in the Edit Conditions box on the Folder Conditions page. +you select **specific** in the Edit Conditions box on the Folder Conditions page. ![Folder Type window](/images/accessanalyzer/11.6/admin/datacollector/ewsmailbox/filterwizard/foldertypewindow.webp) @@ -41,18 +41,17 @@ Select the checkbox next to any folder type to include it in the search filter. ## Search Terms Window -Use the Search Terms window to determine terms for the search. The Search Terms window opens if -**search terms** is selected in the Edit Conditions box. +Use the Search Terms window to determine terms for the search. The Search Terms window opens if you +select **search terms** in the Edit Conditions box. ![Search Terms window](/images/accessanalyzer/11.6/admin/datacollector/ewsmailbox/filterwizard/searchtermswindow.webp) Determine terms for the search using the following options: -- Type the desired term into the upper text box and click **Add** to add the term to the lower text - box, which adds the term to the search +- Enter the term you want in the upper text box, then click **Add** to add it to the search - Select a term in the lower text box, and click **Remove** to remove the term from the search - Click **Clear** to clear all terms from the lower box -- Select the desired qualifier option: +- Select the qualifier option you want: - Contains ALL of the following search terms (And) – Search only returns results containing all of the search terms diff --git a/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/searchfilter/messageconditions.md b/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/searchfilter/messageconditions.md index d0a4a4f8b0..6971694146 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/searchfilter/messageconditions.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/searchfilter/messageconditions.md @@ -61,20 +61,20 @@ Customize message search filter conditions using the following options: [Date Range Selection Window](#date-range-selection-window) topic for additional information. - Click **search terms** to open the Search Terms Window. See the [Search Terms Window](#search-terms-window) topic for additional information. - - Click **has attachment(s)** to convert the condition to **has no attachment(s)** and vice + - Click **has attachments** to convert the condition to **has no attachments** and vice versa ## MessageClasses Window Use the MessageClasses window to alter criteria related to message class. The Message Classes window -opens if **specific** is clicked in the Edit Conditions box on the Message Conditions page. +opens if you click **specific** in the Edit Conditions box on the Message Conditions page. ![MessagesClasses window](/images/accessanalyzer/11.6/admin/datacollector/ewsmailbox/filterwizard/messageclassesmessage.webp) Determine MessageClass-related criteria using the following options: - To add a class, click **Add** -- Enter the desired Message Class in the corresponding textbox +- Enter the Message Class you want in the corresponding textbox - Click **Exact Match** to reveal a dropdown menu of other search criteria under Matching Strategy and select the preferred option: @@ -89,7 +89,7 @@ Determine MessageClass-related criteria using the following options: ## Date Range Selection Window Use the Date Range Selection window to select a time period or range for the search. The Date Range -Selection window opens if **in specific date** is clicked in the Edit Conditions box on the Message +Selection window opens if you click **in specific date** in the Edit Conditions box on the Message Conditions page. ![Date Range Selection window](/images/accessanalyzer/11.6/admin/datacollector/ewsmailbox/filterwizard/daterangeselectionmessage.webp) @@ -104,18 +104,17 @@ Determine the time period or range of the search using the following options: ## Search Terms Window -Use the Search Terms window to determine terms for the search. The Search Terms window opens if -**search terms** is selected in the Edit Conditions box. +Use the Search Terms window to determine terms for the search. The Search Terms window opens if you +select **search terms** in the Edit Conditions box. ![Search Terms window](/images/accessanalyzer/11.6/admin/datacollector/ewsmailbox/filterwizard/searchtermswindow.webp) Determine terms for the search using the following options: -- Type the desired term into the upper text box and click **Add** to add the term to the lower text - box, which adds the term to the search +- Enter the term you want in the upper text box, then click **Add** to add it to the search - Select a term in the lower text box, and click **Remove** to remove the term from the search - Click **Clear** to clear all terms from the lower box -- Select the desired qualifier option: +- Select the qualifier option you want: - Contains ALL of the following search terms (And) – Search only returns results containing all of the search terms diff --git a/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/searchfilter/searchfilter_1.md b/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/searchfilter/searchfilter_1.md index 43116f49bd..6983c8e272 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/searchfilter/searchfilter_1.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/searchfilter/searchfilter_1.md @@ -31,13 +31,13 @@ Customize folder search conditions using the following options: [MessageClasses Window](#messageclasses-window) topic for additional information. - Click **over 90 Day ago** to open the Date Range Selection Window. See the [Date Range Selection Window](#date-range-selection-window) - - Click **has attachment(s)** to convert the condition to **has no attachment(s)** and vice + - Click **has attachments** to convert the condition to **has no attachments** and vice versa ## MessageClasses Window Use the MessageClasses window to alter criteria related to message class. The Message Classes window -opens if **Ipm.Note** or **Ipm.Appointment** is clicked in the Edit Conditions box on the Search +opens if you click **Ipm.Note** or **Ipm.Appointment** in the Edit Conditions box on the Search Filter page. ![MessagesClasses window](/images/accessanalyzer/11.6/admin/datacollector/ewsmailbox/filterwizard/messageclassessearchfilter.webp) @@ -45,7 +45,7 @@ Filter page. Determine MessageClass-related criteria using the following options: - To add a class, click **Add** -- Enter the desired Message Class in the corresponding textbox +- Enter the Message Class you want in the corresponding textbox - Click **Exact Match** to reveal a dropdown menu of other search criteria under Matching Strategy and select the preferred option: @@ -60,7 +60,7 @@ Determine MessageClass-related criteria using the following options: ## Date Range Selection Window Use the Date Range Selection window to select a time period or range for the search. The Date Range -Selection window opens if **over 90 Day ago** is clicked in the Edit Conditions box on the Search +Selection window opens if you click **over 90 Day ago** in the Edit Conditions box on the Search Filter page. ![Date Range Selection window](/images/accessanalyzer/11.6/admin/datacollector/ewsmailbox/filterwizard/daterangeselectionsearchfilter.webp) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/summary.md index 0c4f732e18..f01a4880cf 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/summary.md @@ -10,6 +10,5 @@ The Summary page displays a summary of the configured query. It wizard page for ![EWS Public Folder Data Collector Wizard Summary page](/images/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the EWS Public Folder Data Collector Wizard to ensure that no accidental -clicks are saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** +instead to close the EWS Public Folder Data Collector Wizard without saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchange2k/category.md b/docs/accessanalyzer/11.6/admin/datacollector/exchange2k/category.md index efc4ad087e..5f48decdb1 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchange2k/category.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchange2k/category.md @@ -28,7 +28,7 @@ focus: - Recipient Update Services - Message Delivery – System-wide message settings - Instant Messaging – Instant messaging settings - - Exchange Mailbox Store Logons – The users currently logged on to Microsoft Exchange 2007 and + - Exchange Mailbox Store Logons – The users logged on to Microsoft Exchange 2007 and 2010 - Exchange 2007/2010 Hub Transport Configuration diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchange2k/mapisettings.md b/docs/accessanalyzer/11.6/admin/datacollector/exchange2k/mapisettings.md index 98c00ef374..cc47b8357e 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchange2k/mapisettings.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchange2k/mapisettings.md @@ -6,10 +6,10 @@ sidebar_position: 40 # Exchange2K: MAPI Settings -The MAPI Settings page is used to enter configurations to connect to target Exchange servers. By +Use the MAPI Settings page to enter configurations to connect to target Exchange servers. By default, Enterprise Auditor connects to Exchange using System Attendant. For Exchange 2010 and 2013, -a mailbox and a client access server need to be entered in order to make a MAPI connection. These -settings only need to be configured if not configured at the Global Settings level. It is a wizard +enter a mailbox and a client access server to make a MAPI connection. You only need to configure +these settings if you haven't already configured them at the Global Settings level. It is a wizard page for the categories of: - Exchange Organization > Users diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchange2k/options.md b/docs/accessanalyzer/11.6/admin/datacollector/exchange2k/options.md index 411b60821d..7592544755 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchange2k/options.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchange2k/options.md @@ -13,7 +13,7 @@ depending on the category selected. It is a wizard page for all of the categorie Configure the Options step using the following options: -- How to format collected – Select how the table will be formatted according to the return data +- How to format collected – Select how to format the table based on the return data - Return data as collected - Return each value of the following property in a separate row – Enabled for specific @@ -21,12 +21,12 @@ Configure the Options step using the following options: - Return data in a separate row for each property set in the following group – Enabled for specific properties selected on the Results page -- How to return multi-valued properties – Select how the table will be formatted when the return - data contains multi-valued properties +- How to return multi-valued properties – Select how to format the table when the return data + contains multi-valued properties - Concatenated – Return the data in a continuous string without gaps - - Delimiter – Enter the desired delimiter to be used between values + - Delimiter – Enter the delimiter to use between values - First-value only – Only display the first value diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchange2k/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/exchange2k/overview.md index 7eb1b3771b..9324a75618 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchange2k/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchange2k/overview.md @@ -7,12 +7,12 @@ sidebar_position: 160 # Exchange2K Data Collector The Exchange2K Data Collector extracts configuration details from Exchange organizations for -versions 2003 and later. This is a MAPI-based data collector which requires the **Settings** > -**Exchange** node to be enabled and configured. See the +versions 2003 and later. This is a MAPI-based data collector, which requires you to enable and +configure the **Settings** > **Exchange** node. See the [Exchange](/docs/accessanalyzer/11.6/admin/settings/exchange.md) topic for additional information. -The Exchange2K Data Collector has been preconfigured within the Exchange Solution. Both this data +The Exchange2K Data Collector comes preconfigured within the Exchange Solution. Both this data collector and the solution are available with a special Enterprise Auditor license. See the [Exchange Solution](/docs/accessanalyzer/11.6/solutions/exchange/overview.md) topic for additional information. @@ -53,5 +53,5 @@ contains the following wizard pages: ![Exchange 2K+ Data Collector Wizard Welcome page](/images/accessanalyzer/11.6/admin/datacollector/exchange2k/welcome.webp) -The Welcome page can be hidden by selecting the **Do not show this page the next time** checkbox -when the wizard is open and configuration settings are saved. +To hide the Welcome page, select the **Don't show this page the next time** checkbox while the +wizard is open, then save the configuration settings. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchange2k/results.md b/docs/accessanalyzer/11.6/admin/datacollector/exchange2k/results.md index 73b8d96286..7d96ec4d90 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchange2k/results.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchange2k/results.md @@ -6,12 +6,12 @@ sidebar_position: 30 # Exchange2K: Results -The Results page is where properties that will be gathered are selected. It is a wizard page for +Use the Results page to select properties to gather. It is a wizard page for all. ![Exchange 2K+ Data Collector Wizard Results page](/images/accessanalyzer/11.6/admin/datacollector/exchange2k/results.webp) -Properties can be selected individually or the **Check All**, **Uncheck All**, or **Reset Defaults** -buttons can be used. All Selected properties will be gathered. Click **Expand All** to expand all +Select properties individually, or use the **Check All**, **Uncheck All**, or **Reset Defaults** +buttons. The data collector gathers all selected properties. Click **Expand All** to expand all properties, or **Collapse All** to collapse all properties. Available properties vary based on the category selected. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchange2k/scope.md b/docs/accessanalyzer/11.6/admin/datacollector/exchange2k/scope.md index 675d0b615b..0d43a7574f 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchange2k/scope.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchange2k/scope.md @@ -6,7 +6,7 @@ sidebar_position: 20 # Exchange2K: Scope -The Scope page is used to define where to search. It is a wizard page for the categories of: +Use the Scope page to define where to search. It is a wizard page for the categories of: - Exchange Organization > Users - Exchange Organization > Groups diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchange2k/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/exchange2k/summary.md index e368a2a233..8a870a7011 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchange2k/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchange2k/summary.md @@ -11,6 +11,5 @@ categories. ![Exchange 2K+ Data Collector Wizard Summary page](/images/accessanalyzer/11.6/admin/datacollector/exchange2k/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Exchange 2K+ Data Collector Wizard to ensure that no accidental clicks -are saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** +instead to close the Exchange 2K+ Data Collector Wizard without saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangemailbox/options.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangemailbox/options.md index 410d705363..c910bebc39 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangemailbox/options.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangemailbox/options.md @@ -16,7 +16,7 @@ the following categories: ![Exchange Mailbox Data Collector Wizard Options page](/images/accessanalyzer/11.6/admin/datacollector/exchangemailbox/options.webp) -The following options can be configured: +Configure the following options: :::note Options available vary based upon the category selected. @@ -30,8 +30,8 @@ Options available vary based upon the category selected. - Folders - - All Folders – Select to include all folders in the query. When deselected, the other options - of the category become available. + - All Folders – Select to include all folders in the query. When you deselect this option, the + other options of the category become available. - Include root folder – Include root folders of the selected folders in the query - - – Enter the name of a folder to include and click **+** to add it to the list of @@ -46,7 +46,7 @@ Options available vary based upon the category selected. - Count attachment types – Counts attachment types as part of the query. When selected, this enables the following options: - - Add New – Adds another line to the list of attachment types which is manually edited + - Add New – Adds another line to the list of attachment types that you can edit manually - Load Defaults – Reverts the list to default attachment types - Remove – Remove selected attachment type from the list diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangemailbox/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangemailbox/overview.md index a343ec9db1..81d42d4f0f 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangemailbox/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangemailbox/overview.md @@ -34,11 +34,11 @@ topic for additional information. **Sensitive Data Discovery Considerations** -The Sensitive Data Discovery Add-On must be installed on the Enterprise Auditor Console server, -which enables Sensitive Data criteria for scans. If running Sensitive Data Discovery (SDD) scans, it -will be necessary to increase the minimum amount of RAM. Each thread requires a minimum of 2 -additional GB of RAM per host. For example, if the job is configured to scan 8 hosts at a time , -then an extra 16 GB of RAM are required (8x2=16). +You must install the Sensitive Data Discovery Add-On on the Enterprise Auditor Console server to +enable Sensitive Data criteria for scans. If you run Sensitive Data Discovery (SDD) scans, increase +the minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For +example, if you configure the job to scan 8 hosts at a time, you need an extra 16 GB of RAM +(8 x 2 = 16). ## ExchangeMailbox Query Configuration @@ -62,18 +62,18 @@ permissions on the Welcome page. Select one of the following options for the connection setting: -- Use Global setting – The configured Global Setting is displayed next to this checkbox. Select the - checkbox to use the global setting. -- System Attendant (2003 & 2007) – Enabled when the **Use Global Setting** checkbox is not selected. +- Use Global setting – This checkbox shows the configured Global Setting. Select the checkbox to use + the global setting. +- System Attendant (2003 & 2007) – Enabled when the **Use Global Setting** checkbox isn't selected. Select this option to use System Attendant (2003 & 2007) for the connection. - Use the mailbox associated with the Windows account that Enterprise Auditor is run with – Enabled - when the **Use Global Setting** checkbox is not selected. Select this option to use the mailbox + when the **Use Global Setting** checkbox isn't selected. Select this option to use the mailbox associated with the Windows account that Enterprise Auditor is run with for the connection. -- Exchange Mailbox (2010 and newer) – Enabled when the **Use Global Setting** checkbox is not - selected. Select this option to use an Exchange Mailbox (2010 and newer) for the connection. The - Client Access Server must be entered unless specified in the Global Settings. +- Exchange Mailbox (2010 and newer) – Enabled when the **Use Global Setting** checkbox isn't + selected. Select this option to use an Exchange Mailbox (2010 and newer) for the connection. Enter + the Client Access Server unless you specified it in the Global Settings. - - Client Access Server – A private store server is needed if the Exchange server only has public + - Client Access Server – Use a private store server if the Exchange server only has public stores **Test Connection Setting** diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangemailbox/properties.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangemailbox/properties.md index db4e183657..61ee703e68 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangemailbox/properties.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangemailbox/properties.md @@ -6,13 +6,13 @@ sidebar_position: 30 # ExchangeMailbox: Properties -The Properties page is where properties that will be gathered are selected. The available properties +Use the Properties page to select the properties to gather. The available properties depend on the category selected. It is a wizard page for all of the categories. ![Exchange Mailbox Data Collector Wizard Properties page](/images/accessanalyzer/11.6/admin/datacollector/exchangemailbox/properties.webp) -Properties can be selected individually or you can use the Select All, Clear All, and Reset All -buttons. All selected properties will be gathered. Click **Message Classes** to open the Message +Select properties individually, or use the **Select All**, **Clear All**, and **Reset All** +buttons. The data collector gathers all selected properties. Click **Message Classes** to open the Message classes filters window. ![Message classes filters window](/images/accessanalyzer/11.6/admin/datacollector/exchangemailbox/messageclassesfilterswindow.webp) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangemailbox/scope.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangemailbox/scope.md index 20200fb2cb..60486d6063 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangemailbox/scope.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangemailbox/scope.md @@ -6,13 +6,13 @@ sidebar_position: 20 # ExchangeMailbox: Scope -The Scope page is used to define which mailboxes are to be queried. It is a wizard page for all of +Use the Scope page to define which mailboxes to query. It is a wizard page for all of the categories. ![Exchange Mailbox Data Collector Wizard Scope page](/images/accessanalyzer/11.6/admin/datacollector/exchangemailbox/scope.webp) -At the top, configure the mailboxes to be queried. The selected option changes how the mailboxes are -identified for scoping. +At the top, configure the mailboxes to query. The selected option changes how the data collector +identifies mailboxes for scoping. - All mailboxes – Searches all mailboxes - Selected mailboxes from server – Retrieves all mailboxes in the Exchange organization, making them @@ -23,7 +23,7 @@ identified for scoping. - Retrieve – Enter the server and select Retrieve to display the list of mailboxes on that server - - Add – Select the desired mailboxes to add to the query. The added mailboxes display in the + - Add – Select the mailboxes you want to add to the query. The added mailboxes display in the **Selected mailboxes** list. - Remove – Deletes selected mailboxes from the list - Select All – Click the Select All icon to select all mailboxes in the list @@ -34,7 +34,7 @@ identified for scoping. ![Scope page with Selected table selected](/images/accessanalyzer/11.6/admin/datacollector/exchangemailbox/scopeselectedtable.webp) - - Table – Filters this list by tables. Select the table which hosts the list of mailboxes for - which this query will be scoped. - - Field containing EmailAddressDNs – This list will be populated with columns from the selected + - Table – Filters this list by tables. Select the table that hosts the list of mailboxes to scope + this query to. + - Field containing EmailAddressDNs – This list populates with columns from the selected table. Select the appropriate column from the list. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangemailbox/sddcriteria.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangemailbox/sddcriteria.md index 7e2f125f45..ae6e671bb5 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangemailbox/sddcriteria.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangemailbox/sddcriteria.md @@ -6,17 +6,17 @@ sidebar_position: 40 # ExchangeMailbox: SDD Criteria -The SDD Criteria page is where criteria to be used for discovering sensitive data are configured. It -is a wizard page for the Mailbox sensitive data discovery category. This page requires the Sensitive -Data Discovery Add-On to be been installed on the Enterprise Auditor Console to define the criteria +Use the SDD Criteria page to configure criteria for discovering sensitive data. It +is a wizard page for the Mailbox sensitive data discovery category. This page requires you to +install the Sensitive Data Discovery Add-On on the Enterprise Auditor Console to define the criteria and enable the Criteria Editor. See the [Sensitive Data Discovery Add-On Installation](/docs/accessanalyzer/11.6/install/sensitivedatadiscovery/overview.md) topic for additional information. ![Exchange Mailbox Data Collector Wizard SDD Criteria page](/images/accessanalyzer/11.6/admin/datacollector/exchangemailbox/sddcriteria.webp) -Select the checkbox for the criteria to be used to search for sensitive data. Criteria can also be -selected using the **Select All** and **Select None** buttons. +Select the checkbox for each criterion you want to use to search for sensitive data. You can also +select criteria using the **Select All** and **Select None** buttons. The table contains the following types of criteria: @@ -24,19 +24,19 @@ The table contains the following types of criteria: - User Criteria – Lists user-defined criteria :::note - Until the Sensitive Data Discovery Add-On is installed, only the headers for the + Until you install the Sensitive Data Discovery Add-On, only the headers for the System Criteria and User Criteria nodes will be visible in the table. ::: -- Edit – Click this button to access the Criteria Editor where user-defined criteria can be created - or customized. See the +- Edit – Click this button to access the Criteria Editor, where you can create or customize + user-defined criteria. See the [Sensitive Data Criteria Editor](/docs/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/overview.md) topic for additional information. - Store discovered sensitive data – Stores the potentially sensitive data that matches the selected criteria in the Enterprise Auditor database. Select this checkbox to store a copy of the criteria - match data. This copy can be used to check for false positives, data that matches the selected - criteria but is not actually sensitive. + match data. Use this copy to check for false positives, data that matches the selected + criteria but isn't actually sensitive. - Limit stored matches per criteria to [number] – Identifies the number of potentially sensitive - data matches that are copied to the database. The default is 5 matches. This option is only + data matches copied to the database. The default is 5 matches. This option is only available if the **Store discovered sensitive data** option is selected. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangemailbox/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangemailbox/summary.md index 9a2b55361d..e08dc2ffdf 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangemailbox/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangemailbox/summary.md @@ -10,6 +10,5 @@ The Summary page displays a summary of the configured query. It wizard page for ![Exchange Mailbox Data Collector Wizard Summary page](/images/accessanalyzer/11.6/admin/datacollector/exchangemailbox/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Exchange Mailbox Data Collector Wizard to ensure that no accidental -clicks are saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** +instead to close the Exchange Mailbox Data Collector Wizard without saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/category.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/category.md index 530a41959d..49d7ceb9bd 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/category.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/category.md @@ -6,7 +6,7 @@ sidebar_position: 10 # ExchangeMetrics: Category -The Category page is used to identify the type of Exchange Metrics information to retrieve. +Use the Category page to identify the type of Exchange Metrics information to retrieve. ![Exchange Metrics Data Collector Wizard Category page](/images/accessanalyzer/11.6/admin/datacollector/exchangemetrics/category.webp) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/collectmode.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/collectmode.md index ea34d6aff4..6cbcb70fa8 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/collectmode.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/collectmode.md @@ -6,7 +6,7 @@ sidebar_position: 40 # ExchangeMetrics: Collect Mode -The Collect Mode page is where to set the collection mode. It is a wizard page for the categories +Use the Collect Mode page to set the collection mode. It is a wizard page for the categories of: - Server Volume @@ -27,8 +27,8 @@ of: There are two types of collection modes: - Query Summary Data Only – In this mode, the applet gathers only existing summary data and returns - it to the Enterprise Auditor Console. In order to process Exchange tracking log files, another - instance of the applet must be configured. + it to the Enterprise Auditor Console. To process Exchange tracking log files, configure another + instance of the applet. - Process Exchange Tracking Logs and Query Summary Data – In this mode, the applet processes missing summary data and returns it to the Enterprise Auditor Console. This mode includes an additional setting for **Summary data path**. Choose between: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/messageactivityfilter.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/messageactivityfilter.md index c080266193..5bb1ca6db2 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/messageactivityfilter.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/messageactivityfilter.md @@ -7,9 +7,10 @@ sidebar_position: 80 # ExchangeMetrics: Message Activity Filter The Message Activity Filter page configures which domains the data collector should return mail flow -from specific senders and to specific recipients. For example, if `@netwrix.com` is entered in the -Senders list and `@netwrix.com` in the Recipients list, message activity will be returned only for -mail sent to and received from an `@netwrix.com` address. It is a wizard page for the categories of: +from specific senders and to specific recipients. For example, if you enter `@netwrix.com` in the +Senders list and `@netwrix.com` in the Recipients list, the data collector returns message activity +only for mail sent to and received from an `@netwrix.com` address. It is a wizard page for the +categories of: - User’s Message Activity - User’s Message Activity Per Hour @@ -18,9 +19,8 @@ mail sent to and received from an `@netwrix.com` address. It is a wizard page fo Configure the Message Activity Filter using the following options: -- Add – To add a filter to the desired category, click **Add** in the desired category to add an - entry to that category -- Select **Exact Match** in the added filter to reveal a drop-down list with the following condition +- Add – To add an entry to a category, click **Add** in that category +- Select **Exact Match** in the added filter to reveal a dropdown list with the following condition options: - Exact matches @@ -30,7 +30,7 @@ Configure the Message Activity Filter using the following options: - Kind – Select **(Custom…)** to open the Custom Filter menu. The Custom Filter menu provides options to create and configure other filters. -- Value – Type the filter to be applied +- Value – Enter the filter to apply -The columns in the entry tables can be sorted and or filtered, using the same sorting and filtering -methods of Enterprise Auditor data grids. The **Remove** option will delete a selected filter. +You can sort and filter the columns in the entry tables using the same sorting and filtering +methods as Enterprise Auditor data grids. The **Remove** option will delete a selected filter. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/messagesizes.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/messagesizes.md index 98f6a3f8b7..dc710cfc4a 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/messagesizes.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/messagesizes.md @@ -6,17 +6,17 @@ sidebar_position: 60 # ExchangeMetrics: Message Sizes -The Message Sizes page is used to configure message size frames for which to return summary metrics +Use the Message Sizes page to configure message size frames for which to return summary metrics by server. It is a wizard page for the category of: - Message Size Statistics Custom. ![Exchange Metrics Data Collector Wizard Message Sizes page](/images/accessanalyzer/11.6/admin/datacollector/exchangemetrics/messagesizes.webp) -Configure the desired message size frames using the following options: +Configure the message size frames you want using the following options: -- Frame name – Name the configured message size parameters. Can either be entered manually or a - default will populate when query limits are set. +- Frame name – Name the configured message size parameters. Enter a name manually, or let a default + populate when you set query limits. - Start – Specify the lower limit of the message sizes (in MB) - End – Specify the upper limit of the message sizes (in MB) @@ -27,6 +27,6 @@ For example, a **Start** value of **1** and an **End** value of **2** returns me value of **5** with the **Infinite** checkbox selected retrieves all messages which are 5 megabytes or larger. -Once the frame is configured, click **Add**. The configured message size frame will appear in the -list. Multiple frames can be configured. Select a frame and click **Replace** to modify an existing +After you configure the frame, click **Add**. The configured message size frame will appear in the +list. You can configure multiple frames. Select a frame and click **Replace** to modify an existing frame. Use **Remove** to delete an existing frame. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/options.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/options.md index b93def53fb..3e499d7b2c 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/options.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/options.md @@ -43,7 +43,7 @@ Available options vary depending on Category selected. - Applet Logging - Enable Logging – Enables the applet to log - - Applet log level – Select the desired log level using the dropdown list: + - Applet log level – Select the log level you want using the dropdown list: - None - Debug @@ -55,9 +55,9 @@ Available options vary depending on Category selected. - Applet History - - Enable Persistent Log State – Search the log from where the previous search left off. A state - file is created for each host configured in the query. State files can be viewed within - Enterprise Auditor and are named by the query GUID. State files display the record the + - Enable Persistent Log State – Search the log from where the previous search left off. The job + creates a state file for each host configured in the query. You can view state files within + Enterprise Auditor, where they're named by the query GUID. State files display the record the previous search left off on, the event log, and the date of the last entry. - AD Database Creation diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/overview.md index 95bcfb5c9b..a42857e88e 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/overview.md @@ -13,7 +13,7 @@ summarized metrics from the Message Tracking Log. See the [Exchange Support and Permissions Explained](/docs/accessanalyzer/11.6/requirements/exchange/support/support.md) topic for a complete list of supported platforms. -The ExchangeMetrics Data Collector has been preconfigured within the Exchange Solution. Both this +The ExchangeMetrics Data Collector comes preconfigured within the Exchange Solution. Both this data collector and the solution are available with a special Enterprise Auditor license. See the [Exchange Solution](/docs/accessanalyzer/11.6/solutions/exchange/overview.md) topic for additional information. @@ -30,7 +30,7 @@ topic for additional information. **Permissions** -- Member of the local Administrator group on the targeted Exchange server(s) +- Member of the local Administrator group on the targeted Exchange servers See the [Exchange Mail-Flow Permissions](/docs/accessanalyzer/11.6/requirements/exchange/support/mailflow.md) @@ -59,5 +59,5 @@ which contains the following wizard pages: ![Exchange Metrics Data Collector Wizard Welcome page](/images/accessanalyzer/11.6/admin/datacollector/exchangemetrics/welcome.webp) -The Welcome page can be hidden by checking the **Do not display this page the next time** box when -the wizard is open and configuration settings are saved. +To hide the Welcome page, check the **Don't display this page the next time** box while the wizard +is open, then save the configuration settings. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/results.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/results.md index 1e480d6904..cd076754ad 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/results.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/results.md @@ -6,11 +6,11 @@ sidebar_position: 30 # ExchangeMetrics: Results -The Results page is where properties that will be gathered are selected. It is a wizard page for all +Use the Results page to select properties to gather. It is a wizard page for all of the categories. ![Exchange Metrics Data Collector Wizard Results page](/images/accessanalyzer/11.6/admin/datacollector/exchangemetrics/results.webp) -Properties can be selected individually or the **Check All**, **Uncheck All**, or **Reset Defaults** -buttons can be used. Click **Expand All** to expand all property categories. All selected properties -will be gathered. Available properties vary based on the category selected. +Select properties individually, or use the **Check All**, **Uncheck All**, or **Reset Defaults** +buttons. Click **Expand All** to expand all property categories. The data collector gathers all +selected properties. Available properties vary based on the category selected. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/scope.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/scope.md index 52aa2ceaeb..5b7fe7f4d3 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/scope.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/scope.md @@ -6,7 +6,7 @@ sidebar_position: 20 # ExchangeMetrics: Scope -The Scope page is used to define where to search. It is a wizard page for the categories of: +Use the Scope page to define where to search. It is a wizard page for the categories of: - Server Volume - Internal Traffic Summary @@ -26,8 +26,8 @@ The Scope page is used to define where to search. It is a wizard page for the ca Define the scope of the query using the following options: -- Return data for section – Select the time period for which data will be collected. GMT time is - used by Exchange Metrics to calculate the result. +- Return data for section – Select the time period to collect data for. Exchange Metrics uses GMT + time to calculate the result. - Today - Yesterday @@ -37,11 +37,11 @@ Define the scope of the query using the following options: - Last Month - Last [number] days - Within time frame: - - From [calendar date] to [calendar date] – Use the drop-down arrows to select calendar dates. + - From [calendar date] to [calendar date] – Use the dropdown arrows to select calendar dates. - Return results section – Select the table design for the collected data - - One row for – Use the drop-down list to select one of the following options: + - One row for – Use the dropdown list to select one of the following options: - All period - Day diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/summary.md index 3c23a0267e..b3a20425d5 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/summary.md @@ -11,6 +11,5 @@ categories. ![Exchange Metrics Data Collector Wizard Summary page](/images/accessanalyzer/11.6/admin/datacollector/exchangemetrics/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Exchange Metrics Data Collector Wizard to ensure that no accidental -clicks are saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** +instead to close the Exchange Metrics Data Collector Wizard without saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/timeframes.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/timeframes.md index 134fc2565f..7cb4041929 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/timeframes.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/timeframes.md @@ -6,17 +6,17 @@ sidebar_position: 50 # ExchangeMetrics: Time Frames -The Time Frames page is used to configure message delivery time frames for which to return summary +Use the Time Frames page to configure message delivery time frames for which to return summary metrics by server. It is a wizard page for the category of: - Delivery Time Custom. ![Exchange Metrics Data Collector Wizard Time Frames page](/images/accessanalyzer/11.6/admin/datacollector/exchangemetrics/timeframes.webp) -Configure the desired time frames using the following options: +Configure the time frames you want using the following options: -- Frame name – Name the configured time frame. Can either be entered manually or a default will - populate when frame limits are set. +- Frame name – Name the configured time frame. Enter a name manually, or let a default populate when + you set frame limits. - Start – Specify the lower limit of the delivery time frame - End – Specify the upper limit of the delivery time frame - Select the time unit of the time frame: @@ -32,6 +32,6 @@ selected returns messages delivered in 1 to 2 minutes. **Start** value of **2** with the **Infinite** checkbox selected retrieves all messages that took 2 seconds/minutes/hours or longer to deliver. -Once the frame is configured, click **Add**. The configured message time frame will appear in the -list. Multiple time frames can be configured. Select a frame and click **Replace** to modify an +After you configure the frame, click **Add**. The configured message time frame will appear in the +list. You can configure multiple time frames. Select a frame and click **Replace** to modify an existing frame. Use **Remove** to delete an existing frame. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/category.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/category.md index 345a69e179..5b93633747 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/category.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/category.md @@ -6,8 +6,8 @@ sidebar_position: 20 # ExchangePS: Category -The Category page contains a connection section where connection options are defined. It is also -where the query category is selected. The available query categories are sub-divided by auditing +The Category page contains a connection section where you define connection options. It's also +where you select the query category. The available query categories are sub-divided by auditing focus. ![ExchangePS Data Collector Wizard Category page](/images/accessanalyzer/11.6/admin/datacollector/exchangeps/category.webp) @@ -29,15 +29,15 @@ In the Connection section, select the method for connecting to the target Exchan **Exchange** node) - Exchange 2013 & 2016 – Require an actual CAS server name: - - If the **Settings** > **Exchange** node was configured for MAPI over HTTP, then an actual - CAS server name was supplied and will be used by the ExchangePS Data Collector - - If the **Settings** > **Exchange** node was configured for MAPI over HTTPS, then the - global configuration will have a web address instead of an actual server. Therefore, each - query requires the CAS server to be set as the specific server on the Category page. + - If you configured the **Settings** > **Exchange** node for MAPI over HTTP, the ExchangePS + Data Collector uses the actual CAS server name you supplied + - If you configured the **Settings** > **Exchange** node for MAPI over HTTPS, the global + configuration has a web address instead of an actual server. Therefore, each query + requires you to set the CAS server as the specific server on the Category page. - Use Office 365 – Connect to Office 365 -- Use pipelined PowerShell – Processes each mailbox object in turn. When selected, the data - collector streams data to the database instead of transferring batches of data. +- Use pipelined PowerShell – Processes each mailbox object in turn. When you select this option, the + data collector streams data to the database instead of transferring batches of data. - This option uses less memory but is more sensitive to network conditions - Only available for Exchange 2013+ target environments @@ -54,7 +54,7 @@ focus: - Mailbox Databases – Collects information on mailbox databases :::note - This option is not available for Office 365 target environments + This option isn't available for Office 365 target environments ::: @@ -111,7 +111,7 @@ Get-MailboxStatistics Get-MailboxDatabase ``` -When this category is selected, the following ExchangePS Data Collector Wizard pages are available +When you select this category, the following ExchangePS Data Collector Wizard pages are available for configuration: - [ExchangePS: Scope](/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scope.md) @@ -132,7 +132,7 @@ Get-MailboxStatistics Get-MailboxDatabase ``` -When this category is selected, the following ExchangePS Data Collector Wizard pages are available +When you select this category, the following ExchangePS Data Collector Wizard pages are available for configuration: - [ExchangePS: Scope](/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scope.md) @@ -150,7 +150,7 @@ PowerShell query this category runs is as follows: Get-MailboxDatabase ``` -When this category is selected, the following ExchangePS Data Collector Wizard pages are available +When you select this category, the following ExchangePS Data Collector Wizard pages are available for configuration: - [ExchangePS: Scope](/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scope.md) @@ -168,7 +168,7 @@ PowerShell query this category runs is as follows: Get-MailboxDatabase ``` -When this category is selected, the following ExchangePS Data Collector Wizard pages are available +When you select this category, the following ExchangePS Data Collector Wizard pages are available for configuration: - [ExchangePS: Scope](/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scope.md) @@ -186,7 +186,7 @@ PowerShell query this category runs is as follows: Get-MailboxDatabase ``` -When this category is selected, the following ExchangePS Data Collector Wizard pages are available +When you select this category, the following ExchangePS Data Collector Wizard pages are available for configuration: - [ExchangePS: Scope](/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scope.md) @@ -206,7 +206,7 @@ Get-Mailbox Get-MailboxDatabase ``` -When this category is selected, the following ExchangePS Data Collector Wizard pages are available +When you select this category, the following ExchangePS Data Collector Wizard pages are available for configuration: - [ExchangePS: Scope](/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scope.md) @@ -218,8 +218,8 @@ for configuration: **Mailbox Access Logons** -This category returns the Mailbox Access Auditing log details. Mailbox Access Auditing does need to -be enabled on the Mailboxes in order for this job to return any information. The PowerShell queries +This category returns the Mailbox Access Auditing log details. You must enable Mailbox Access +Auditing on the mailboxes for this job to return any information. The PowerShell queries this category runs are as follows: ``` @@ -227,7 +227,7 @@ Search-MailboxAuditLog Get-Mailbox ``` -When this category is selected, the following ExchangePS Data Collector Wizard pages are available +When you select this category, the following ExchangePS Data Collector Wizard pages are available for configuration: - [ExchangePS: Scope](/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scope.md) @@ -253,7 +253,7 @@ Get-Mailbox Get-ThrottlingPolicyAssociation ``` -When this category is selected, the following ExchangePS Data Collector Wizard pages are available +When you select this category, the following ExchangePS Data Collector Wizard pages are available for configuration: - [ExchangePS: Scope](/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scope.md) @@ -276,7 +276,7 @@ Get-ActiveSyncDeviceStatistics Get-Mailbox ``` -When this category is selected, the following ExchangePS Data Collector Wizard pages are available +When you select this category, the following ExchangePS Data Collector Wizard pages are available for configuration: - [ExchangePS: Scope](/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scope.md) @@ -291,8 +291,8 @@ Public Folder Information audit focus contains the following categories: **Public Folder Content** -This category returns general statistics and sizing for the public folder environment. When it is -selected, the following ExchangePS Data Collector Wizard pages are available for configuration: +This category returns general statistics and sizing for the public folder environment. When you +select it, the following ExchangePS Data Collector Wizard pages are available for configuration: - [ExchangePS: Scope](/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scope.md) - [ExchangePS: Results](/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/results.md) @@ -302,8 +302,8 @@ selected, the following ExchangePS Data Collector Wizard pages are available for **Public Folder Permissions** -This category returns permissions information for the public folder environment. When it is -selected, the following ExchangePS Data Collector Wizard pages are available for configuration: +This category returns permissions information for the public folder environment. When you +select it, the following ExchangePS Data Collector Wizard pages are available for configuration: - [ExchangePS: Scope](/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scope.md) - [ExchangePS: Results](/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/results.md) @@ -317,8 +317,8 @@ Office 365 audit focus contains the following category: **Mail Flow Metrics** -This category returns information about mail flow in the target Exchange Online environment. When it -is selected, the following ExchangePS Data Collector Wizard pages are available for configuration: +This category returns information about mail flow in the target Exchange Online environment. When +you select it, the following ExchangePS Data Collector Wizard pages are available for configuration: - [ExchangePS: Scope](/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scope.md) - [ExchangePS: Mail Flow](/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/mailflow.md) @@ -333,7 +333,7 @@ Domain Information audit focus contains the following category: **Domains** -This category returns information about domains in the Exchange environment. When it is selected, +This category returns information about domains in the Exchange environment. When you select it, the following ExchangePS Data Collector Wizard pages are available for configuration: - [ExchangePS: Scope](/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scope.md) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/configurejob.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/configurejob.md index a6b2d0983d..f268e41920 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/configurejob.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/configurejob.md @@ -6,12 +6,12 @@ sidebar_position: 10 # Exchange Custom Connection Profile & Host List -The ExchangePS Data Collector requires a custom Connection Profile and host list to be created and -assigned to the job conducting the data collection. The host inventory option during host list -creation makes it necessary to configure the Connection Profile first. +The ExchangePS Data Collector requires you to create a custom Connection Profile and host list and +assign them to the job that collects the data. The host inventory option during host list +creation requires you to configure the Connection Profile first. :::note -It is not possible to target both Exchange Online and on-premises Exchange environments +You can't target both Exchange Online and on-premises Exchange environments from the same job. Therefore, the Connection Profile should only contain the credentials for one type of environment. ::: @@ -28,21 +28,21 @@ The provisioned credential used should be an Active Directory account. Create a and set the following information on the User Credentials window: - Select Account Type – Active Directory Account -- Domain – Drop-down menu with available trusted domains will appear. Either type the short domain +- Domain – dropdown menu with available trusted domains will appear. Either enter the short domain name in the textbox or select a domain from the menu. -- User name – Type the user name +- User name – Enter the user name - Password Storage – Choose the for credential password storage: - Application – Uses the configured Profile Security setting as selected at the **Settings** > **Application** node - CyberArk – Uses the CyberArk Enterprise Password Vault -- Password – Type the password -- Confirm – Re-type the password +- Password – Enter the password +- Confirm – Re-enter the password ### Exchange On-Premise Host List -The ExchangePS Data Collector should be set to run against: +Set the ExchangePS Data Collector to run against: - Local host @@ -53,7 +53,7 @@ Exchange Online. ### Exchange Online Credential for a Connection Profile -The provisioned credential must be created with the Exchange Modern Authentication account type. +Create the provisioned credential with the Exchange Modern Authentication account type. Create a Connection Profile and set the following information on the User Credentials window: - Select Account Type – Exchange Modern Authentication @@ -61,11 +61,11 @@ Create a Connection Profile and set the following information on the User Creden **Settings** > **Application** node. See the [Application](/docs/accessanalyzer/11.6/admin/settings/application/overview.md) topic for additional information.) -- Organization – The primary domain name of the Microsoft Entra tenant being leveraged to make the +- Organization – The primary domain name of the Microsoft Entra tenant used to make the connection. See the [Identify the Tenant's Name](/docs/accessanalyzer/11.6/requirements/exchange/exchangeonline/access.md#identify-the-tenants-name) topic for additional information. -- Email Address – The email address for the mailbox to be leveraged in Exchange Online environment +- Email Address – The email address for the mailbox used in Exchange Online environment scans. The mailbox must belong to the primary domain used in the Organization field. - AppID – Application (client) ID of the Enterprise Auditor application registered with Microsoft Entra ID. See the diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/filtermessage.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/filtermessage.md index 717b8df657..42d7205c08 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/filtermessage.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/filtermessage.md @@ -6,7 +6,7 @@ sidebar_position: 70 # ExchangePS: Filter by Message -The Filter by Message page is used to define the filter conditions of the search. It is a wizard +Use the Filter by Message page to define the filter conditions of the search. It is a wizard page for the category of: - Mailbox Search @@ -36,16 +36,16 @@ Available conditions to select from include: See the [Date Range Selection Window](#date-range-selection-window) and [Words Window](#words-window) topics for additional information. -In the Select Search Mailbox Parameters section, select the desired filter parameters: +In the Select Search Mailbox Parameters section, select the filter parameters you want: -- Do not Include Archive +- Don't Include Archive - Include Unsearchable Items - Search Dumpster - Search Dumpster Only #### Date Range Selection Window -The Date Range Selection window is opened by the **Specify Date Range...** option for a date related +The **Specify Date Range...** option opens the Date Range Selection window for a date-related filter on the Filter by Message page. ![Date Range Selection window](/images/accessanalyzer/11.6/admin/datacollector/exchangeps/daterangeselectionwindow.webp) @@ -56,19 +56,19 @@ Select the range category on the left and configure the range setting in the ena **Years**. - Last – Select the number and time units. The available time units are: **Days**, **Months**, or **Years**. -- Before – Drop-down menu opens a calendar selection view, choose the end date -- After – Drop-down menu opens a calendar selection view, choose the start date -- Between (Date) – Drop-down menus open calendar selection view, choose the start and end dates -- Between – Select the numbers for the lower and upper range boundary, and the desired time units. +- Before – dropdown menu opens a calendar selection view, choose the end date +- After – dropdown menu opens a calendar selection view, choose the start date +- Between (Date) – dropdown menus open calendar selection view, choose the start and end dates +- Between – Select the numbers for the lower and upper range boundary, and the time units you want. The available time units are: **Days**, **Months**, or **Years**. -When the date range is specified, click **OK**. The selected date range shows as a filter on the +After you specify the date range, click **OK**. The selected date range shows as a filter on the Filter by Message page. Click the filter to open the Date Range Selection window to modify the date range. #### Words Window -The Words window is opened by the **Specify words...** option for a word related filter on the +The **Specify words...** option opens the Words window for a word-related filter on the Filter by Message page. ![Words window](/images/accessanalyzer/11.6/admin/datacollector/exchangeps/wordswindow.webp) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/mailboxlogons.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/mailboxlogons.md index 55d8c2d3ad..d2283361d1 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/mailboxlogons.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/mailboxlogons.md @@ -6,13 +6,13 @@ sidebar_position: 80 # ExchangePS: Mailbox Logons -The Mailbox Logons page is used to define the type of mailbox logon events to return, as well as the -date range to be returned. It is a wizard page for the category of Mailbox Information > Mailbox +Use the Mailbox Logons page to define the type of mailbox logon events to return, as well as the +date range to return. It is a wizard page for the category of Mailbox Information > Mailbox Access Logons. ![ExchangePS Data Collector Wizard Mailbox Logons page](/images/accessanalyzer/11.6/admin/datacollector/exchangeps/mailboxlogons.webp) -Select the desired checkboxes to indicate which logons to audit: +Select the checkboxes you want to indicate which logons to audit: - Delegate - Admin @@ -27,4 +27,4 @@ Specify the date range for the logons: ::: -- Between (Date) – Use the drop-down menus to open calendars to select the start and end dates +- Between (Date) – Use the dropdown menus to open calendars to select the start and end dates diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/mailflow.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/mailflow.md index 661a143ad6..e461c9ca20 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/mailflow.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/mailflow.md @@ -21,5 +21,5 @@ Date range must be 7 days or less. - Last – Select the number of days -- Between (Date) – Use the drop-down menus to open the calendar selection view to choose the start +- Between (Date) – Use the dropdown menus to open the calendar selection view to choose the start and end dates diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/options.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/options.md index 04bbf6a131..304814bf23 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/options.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/options.md @@ -6,12 +6,12 @@ sidebar_position: 110 # ExchangePS: Options -The Options page is used to configure additional options. It is a wizard page for all of the +Use the Options page to configure additional options. It is a wizard page for all of the categories. ![ExchangePS Data Collector Wizard Options page](/images/accessanalyzer/11.6/admin/datacollector/exchangeps/options.webp) -The following options can be configured: +Configure the following options: - Message size units - Select the message size for the query: @@ -19,7 +19,7 @@ The following options can be configured: - MB - GB -- How to format collected results – Select how table will be formatted according to the return data: +- How to format collected results – Select how to format the table based on the return data: - Return data as collected - Return each value of the following property in a separate row – Enabled for specific @@ -27,11 +27,11 @@ The following options can be configured: - Return data in a separate row for each property set in the following group – Enabled for specific properties selected on the Results page -- How to return multi-valued properties – Select how the table will be formatted when the return +- How to return multi-valued properties – Select how to format the table when the return data contains multi-valued properties: - Concatenated - - Delimiter – Enter the desired delimiter to be used between values + - Delimiter – Enter the delimiter to use between values - First-value only diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/overview.md index dbce74ca75..8ca553ea89 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/overview.md @@ -6,9 +6,9 @@ sidebar_position: 190 # ExchangePS Data Collector -The ExchangePS Data Collector utilizes the Exchange CMDlets to return information about the Exchange -environment utilizing PowerShell. This data collector has been designed to work with Exchange 2010 -and newer. The ExchangePS Data Collector has been preconfigured within the Exchange Solution. Both +The ExchangePS Data Collector uses the Exchange CMDlets to return information about the Exchange +environment using PowerShell. This data collector works with Exchange 2010 +and newer. The ExchangePS Data Collector comes preconfigured within the Exchange Solution. Both this data collector and the solution are available with a special Enterprise Auditor license. See the [Exchange Solution](/docs/accessanalyzer/11.6/solutions/exchange/overview.md) @@ -42,9 +42,9 @@ topic for additional information. ## Remote PowerShell -The ExchangePS Data Collector will utilize Remote PowerShell when connecting to Exchange 2010 or -newer. This behavior simulates what the Exchange Management Shell does when loading. The below -PowerShell syntax is an example of how the connection is loaded through PowerShell. +The ExchangePS Data Collector will use Remote PowerShell when connecting to Exchange 2010 or +newer. This behavior simulates what the Exchange Management Shell does when loading. The following +PowerShell syntax is an example of how PowerShell loads the connection. ``` $JobUserName = '{insert domain\username}' @@ -62,14 +62,14 @@ topic for instructions on enabling Remote PowerShell. ## The Exchange Applet -The Exchange Applet will run on the Exchange server by the ExchangePS Data Collector in the +The ExchangePS Data Collector runs the Exchange Applet on the Exchange server in the following circumstances: -- An actual Client Access Server (CAS) server is not specified either in the global configuration +- An actual Client Access Server (CAS) server isn't specified either in the global configuration (**Settings** > **Exchange** node) or on the Category page of the ExchangePS Data Collector Wizard -- Remote PowerShell has not been enabled for targeting Exchange 2010 +- You haven't enabled Remote PowerShell for targeting Exchange 2010 -The following Exchange Snap-in is used when the applet is utilized: +The applet uses the following Exchange Snap-in: - Add-pssnapin Microsoft.Exchange.Management.Powershell.E2010 diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/results.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/results.md index e6523713e3..3a57499d8b 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/results.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/results.md @@ -6,10 +6,10 @@ sidebar_position: 100 # ExchangePS: Results -The Results page is where properties that will be gathered are selected. It is a wizard page for all +Use the Results page to select properties to gather. It is a wizard page for all of the categories. ![ExchangePS Data Collector Wizard Results page](/images/accessanalyzer/11.6/admin/datacollector/exchangeps/results.webp) -Properties can be selected individually or the **Select All** and **Clear All** buttons can be used. -All selected properties will be gathered. Available properties vary based on the category selected. +Select properties individually, or use the **Select All** and **Clear All** buttons. +The data collector gathers all selected properties. Available properties vary based on the category selected. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scope.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scope.md index d9465574ac..c7ea3c43bb 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scope.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scope.md @@ -6,7 +6,8 @@ sidebar_position: 30 # ExchangePS: Scope -The Scope page establishes how mailboxes are scoped. It is a wizard page for all of the categories. +The Scope page establishes how the data collector scopes mailboxes. It is a wizard page for all of +the categories. ![ExchangePS Data Collector Wizard Scope page](/images/accessanalyzer/11.6/admin/datacollector/exchangeps/scope.webp) @@ -15,14 +16,14 @@ Available scoping options vary based on the category selected. Scoping options i - No Scoping Target Host: Local Host – Returns all results for the entire targeted Exchange Organization - - If this option is selected, then the data collector should be run against the host specified + - If you select this option, run the data collector against the host specified on the Summary page. See the [ExchangePS: Summary](/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/summary.md) topic for additional information. - When using the applet, the data collector gathers information about the Exchange Forest in - which the Enterprise Auditor Console currently resides + which the Enterprise Auditor Console resides - For Remote PowerShell, the data collector gathers information about the Exchange Organization - to which the Remote PowerShell connection was made. This refers to the server entered in the + to which you made the Remote PowerShell connection. This refers to the server entered in the Client Access Server (CAS) field of the global configuration from the **Settings** > **Exchange** node or on the this page. @@ -39,7 +40,7 @@ Available scoping options vary based on the category selected. Scoping options i - When using the applet, the data collector deploys a process to the targeted host to run the PowerShell on that server - - For Remote PowerShell, the data collector does not deploy anapplet and utilizes the WinRM + - For Remote PowerShell, the data collector doesn't deploy anapplet and uses the WinRM protocol to gather information about the objects on that server. See the [Remote PowerShell](/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/overview.md#remote-powershell) and diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scopedatabases.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scopedatabases.md index 2319d5bbdd..5093c72b4d 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scopedatabases.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scopedatabases.md @@ -6,20 +6,20 @@ sidebar_position: 40 # ExchangePS: Scope by DB -The Scope by Databases page is used to define specific databases to search. This page is enabled -when **Scope by Database Target Host: Local Host** option is selected on the Scope page. See the +Use the Scope by Databases page to define specific databases to search. You enable this page by +selecting the **Scope by Database Target Host: Local Host** option on the Scope page. See the [ExchangePS: Scope](/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scope.md) topic for additional information. When using the applet, the data collector returns databases for the Exchange Organization in which -the Enterprise Auditor Console currently resides, and only returns information about those +the Enterprise Auditor Console resides, and only returns information about those databases. For Remote PowerShell, the data collector returns databases for the Exchange Forest and only returns information about those databases. ![ExchangePS Data Collector Wizard Scope by Databases page](/images/accessanalyzer/11.6/admin/datacollector/exchangeps/scopedatabases.webp) Click **Retrieve** to return all databases in the Exchange Organization and populate them in the -Available Databases list. Select the desired databases from Available Databases and click **Add**. -The selected databases are added in the Selected Databases list. To remove undesired databases from -Selected Databases, select them and click **Remove**. The Select All and Clear All buttons can be -used for quick selection. +Available Databases list. Select the databases you want from Available Databases and click **Add**. +The wizard adds the selected databases to the Selected Databases list. To remove undesired databases +from Selected Databases, select them and click **Remove**. Use the Select All and Clear All buttons +for quick selection. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scopemailboxes.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scopemailboxes.md index 6c48cd69ca..603fca79aa 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scopemailboxes.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scopemailboxes.md @@ -6,13 +6,13 @@ sidebar_position: 50 # ExchangePS: Scope by Mailboxes -The Scope by Mailboxes page is used to define specific mailboxes to search. This page is enabled -when the **Scope by Mailbox Target Host: Local Host** option is selected on the Scope page. See the +Use the Scope by Mailboxes page to define specific mailboxes to search. You enable this page by +selecting the **Scope by Mailbox Target Host: Local Host** option on the Scope page. See the [ExchangePS: Scope](/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scope.md) topic for additional information. When using the applet, the data collector will return mailboxes for the Exchange Forest in which the -Enterprise Auditor Console currently resides, and only return information about those mailboxes. For +Enterprise Auditor Console resides, and only return information about those mailboxes. For Remote PowerShell, the data collector will return mailboxes for the Exchange Forest as well as return information about those mailboxes. @@ -20,6 +20,6 @@ return information about those mailboxes. Click **Retrieve** to return all mailboxes in the Exchange Organization and populate them in the Available Mailboxes list. Select desired mailboxes from the Available Mailboxes list and click -**Add**. The selected mailboxes are added in the Selected Mailboxes list. To remove undesired +**Add**. The wizard adds the selected mailboxes to the Selected Mailboxes list. To remove undesired mailboxes from Selected Mailboxes, select them and click **Remove**. The Select All and Clear All -buttons can be used for quick selection. +buttons let you select quickly. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scopepublicfolders.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scopepublicfolders.md index 53de73fca0..9c4b1c2b9f 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scopepublicfolders.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scopepublicfolders.md @@ -6,17 +6,17 @@ sidebar_position: 60 # ExchangePS: Scope by Public Folders -The Scope by Public Folders page is used to define specific public folders to search. This page is -enabled when the **Scope by Public Folder** option is selected on the Scope page. See the +Use the Scope by Public Folders page to define specific public folders to search. You enable this +page by selecting the **Scope by Public Folder** option on the Scope page. See the [ExchangePS: Scope](/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scope.md) topic for additional information. -Configure the **Scope** option using the drop-down. The available options are: +Configure the **Scope** option using the dropdown. The available options are: - Selected Public Folder - Selected Table -The option selected changes how the public folders are identified for scoping. +The selected option changes how the data collector identifies public folders for scoping. ## Selected Public Folder @@ -25,9 +25,9 @@ organization, populating them in the Available list. ![ExchangePS Data Collector Wizard Scope by Public Folders page with Selected Public Folders option](/images/accessanalyzer/11.6/admin/datacollector/exchangeps/scopepublicfolders.webp) -The **Search** feature filters this list. Select the desired public folders and click **Add**. The -selected public folders are added to the Selected list. Use the **Remove** option to delete selected -public folders from the list. The Select All or Deselect All buttons can be used for quick +The **Search** feature filters this list. Select the public folders you want and click **Add**. The +wizard adds the selected public folders to the Selected list. Use the **Remove** option to delete selected +public folders from the list. Use the Select All or Deselect All buttons for quick selection. Additional scoping options include: - Return only these folders – Audits only the selected public folders @@ -42,5 +42,5 @@ Enterprise Auditor database. ![ExchangePS Data Collector Wizard Scope by Public Folders page with Selected Table option](/images/accessanalyzer/11.6/admin/datacollector/exchangeps/scopepublicfoldersselectedtable.webp) The **Search** feature filters this list. Select the table that houses the list of public folders -for which this query will be scoped. The Field containing EntryIDs list is populated with columns +to scope this query to. The Field containing EntryIDs list populates with columns from the selected table. Select the appropriate column from the list. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/summary.md index b559203a10..9baa3a555c 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/summary.md @@ -6,11 +6,10 @@ sidebar_position: 130 # ExchangePS: Summary -The Summary page is where configuration settings are summarized. It is a wizard page for all of the -categories. +Use the Summary page to review a summary of the configuration settings. It is a wizard page for all +of the categories. ![ExchangePS Data Collector Wizard Summary page](/images/accessanalyzer/11.6/admin/datacollector/exchangeps/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the ExchangePS Data Collector Wizard to ensure that no accidental clicks -are saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** +instead to close the ExchangePS Data Collector Wizard without saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/category.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/category.md index f0ea77570f..57b2fc723c 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/category.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/category.md @@ -6,7 +6,7 @@ sidebar_position: 10 # ExchangePublicFolder: Category -The Category page is used to select the objects to search. +Use the Category page to select the objects to search. ![Exchange Public Folder Data Collector Wizard Category page](/images/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/category.webp) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/options.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/options.md index 7c8848080d..eedf4dcfda 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/options.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/options.md @@ -16,7 +16,7 @@ The Options page contains the following options: - Process folders that physically reside on the target server only – This option will limit extraction to only the subset of public folders which reside on this server when selected. Clear this option if targeting the Exchange 2010 Public Folder Server. The ability to scope to the - targeted server is not available for Exchange 2010. The entire public folder hierarchy is + targeted server isn't available for Exchange 2010. The entire public folder hierarchy is returned. - Message size units: @@ -28,7 +28,7 @@ The Options page contains the following options: Scope page settings. See the [ExchangeMetrics: Scope](/docs/accessanalyzer/11.6/admin/datacollector/exchangemetrics/scope.md) topic for additional information. -- Large attachment threshold (Kb) – Configure the desired size limit for attachments. The default +- Large attachment threshold (Kb) – Configure the size limit you want for attachments. The default value is 500. In the Attachment types section, configure attachment count types. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/overview.md index 6ad208c975..6c49e0c8e2 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/overview.md @@ -7,12 +7,12 @@ sidebar_position: 200 # ExchangePublicFolder Data Collector The ExchangePublicFolder Data Collector audits an Exchange Public Folder, including contents, -permissions, ownership, and replicas. This is a MAPI-based data collector which requires the -**Settings > Exchange** node to be enabled and configured. See the +permissions, ownership, and replicas. This is a MAPI-based data collector, which requires you to +enable and configure the **Settings > Exchange** node. See the [Exchange](/docs/accessanalyzer/11.6/admin/settings/exchange.md) topic for additional information. -The ExchangePublicFolder Data Collector has been preconfigured within the Exchange Solution. Both +The ExchangePublicFolder Data Collector comes preconfigured within the Exchange Solution. Both this data collector and the solution are available with a special Enterprise Auditor license. See the [Exchange Solution](/docs/accessanalyzer/11.6/solutions/exchange/overview.md) @@ -35,11 +35,11 @@ topic for additional information. **Sensitive Data Discovery Considerations** -The Sensitive Data Discovery Add-On must be installed on the Enterprise Auditor Console server, -which enables Sensitive Data criteria for scans. If running Sensitive Data Discovery (SDD) scans, it -will be necessary to increase the minimum amount of RAM. Each thread requires a minimum of 2 -additional GB of RAM per host. For example, if the job is configured to scan 8 hosts at a time , -then an extra 16 GB of RAM are required (8x2=16). +You must install the Sensitive Data Discovery Add-On on the Enterprise Auditor Console server to +enable Sensitive Data criteria for scans. If you run Sensitive Data Discovery (SDD) scans, increase +the minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For +example, if you configure the job to scan 8 hosts at a time, you need an extra 16 GB of RAM +(8 x 2 = 16). ## ExchangePublicFolder Query Configuration @@ -62,7 +62,7 @@ permissions on the Welcome page. In the Connection Setting section, choose to either maintain the global inheritance, or configure query specific settings. -The **Use Global setting** option specifies what setting is being inherited. Clear this option to +The **Use Global setting** option specifies which setting the query inherits. Clear this option to break inheritance, and then select one of the following options: - System Attendant (2003 & 2007) @@ -74,6 +74,6 @@ See the [Exchange](/docs/accessanalyzer/11.6/admin/settings/exchange.md) topic for additional information. -In the Sampling server section, enter the Exchange server in the textbox to be used to test the +In the Sampling server section, enter the Exchange server in the textbox to test the connection settings. Click **Test sampling server** to ensure there is access to the server. The box at the bottom of the page displays information regarding the test connection in progress. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/probableowner.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/probableowner.md index a8ede5385c..565c56064b 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/probableowner.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/probableowner.md @@ -6,14 +6,14 @@ sidebar_position: 50 # ExchangePublicFolder: Probable Owner -The Probable Owner Settings page provides configuration options to determine an owner. It is enabled -when the Probable Owner property is selected on the Properties page. See the +The Probable Owner Settings page provides configuration options to determine an owner. You enable it +by selecting the Probable Owner property on the Properties page. See the [ExchangePublicFolder: Properties](/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/properties.md) topic for additional information. ![Exchange Public Folder Data Collector Wizard Probable Owner page](/images/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/probableowner.webp) -In the Determine owner section, select the desired option to specify what setting to use to +In the Determine owner section, select the option you want to specify what setting to use to determine an owner: - Determine owner from folder hierarchy – Select to determine the probable owner with a weight of @@ -48,15 +48,15 @@ In the Exclusions section, select one or more of the following checkboxes to spe - Remove selected – Select a user or users to remove from the Exclude users list and click **Remove selected** to remove the users -In the Output Options section, select the desired output option: +In the Output Options section, select the output option you want: - Get one most probable owner – Return one probable owner - Get probable owners with relative deviation to the most probable owner – Return probable owners based on the deviation from percentage from the most probable owner - - Maximum deviation [number] percents – Use the arrow buttonss to enter the desired percent of - deviation from the most probable owner from which to return probable owners + - Maximum deviation [number] percents – Use the arrow buttons to enter the percent of + deviation you want from the most probable owner from which to return probable owners - Get multiple probable owners – Return multiple probable owners - - Count – Use the arrow buttons to enter the desired number of probable owners to return + - Count – Use the arrow buttons to enter the number of probable owners you want to return diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/properties.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/properties.md index d38082209f..ad0c258e33 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/properties.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/properties.md @@ -6,13 +6,13 @@ sidebar_position: 30 # ExchangePublicFolder: Properties -The Properties page is where properties that will be gathered are selected. It is a wizard page for +Use the Properties page to select the properties to gather. It is a wizard page for all of the categories. ![Exchange Public Folder Data Collector Wizard Properties page](/images/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/properties.webp) -Properties can be selected individually or you can use the **Select All**, **Clear All**, or **Reset -All** buttons. All selected properties will be gathered. The **Message Classes** button opens the +Select properties individually, or use the **Select All**, **Clear All**, or **Reset +All** buttons. The data collector gathers all selected properties. The **Message Classes** button opens the Message classes filters window. ![Message classes filters window](/images/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/messageclassesfilterswindow.webp) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/scope.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/scope.md index cfc7227708..bfee7640d6 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/scope.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/scope.md @@ -6,7 +6,7 @@ sidebar_position: 20 # ExchangePublicFolder: Scope -The Scope page is used to define which folders will be included will be searched by this query. It +Use the Scope page to define which folders this query searches. It is a wizard page for all of the categories. ![Exchange Public Folder Data Collector Wizard Scope page](/images/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/scope.webp) @@ -15,12 +15,12 @@ In the Choose Type of Public Folders to be queried section, select either: - Default Public Folders – User can access these folders directly with client applications such as Microsoft Outlook. In its default configuration, Exchange System Manager displays these folders - when a public folder tree is expanded. -- System Public Folders – Users cannot access these folders directly. Client applications, such as + when you expand a public folder tree. +- System Public Folders – Users can't access these folders directly. Client applications, such as Microsoft Outlook, use these folders to store information such as free and busy data, offline address lists, and organizational forms. Other folders hold configuration information that is used by custom applications or by Exchange itself. The Public Folders tree contains extra system - folders, such as the EFORMS REGISTRY folder, that do not exist in general-purpose public folder + folders, such as the EFORMS REGISTRY folder, that don't exist in general-purpose public folder trees. In the Choose Scope of Public Folders to be queried section, select one of the following options: @@ -39,14 +39,14 @@ In the Choose Scope of Public Folders to be queried section, select one of the f ## Scope to the Selected Public Folders -When Scope to **Selected Public Folders** is selected on the Scope page, the options to specify the -desired folders are enabled. +When you select Scope to **Selected Public Folders** on the Scope page, the options to specify the +desired folders become available. ![Scope page with Selected Public Folders option selected](/images/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/scopeselectedpublicfolders.webp) Configure the scope of the selected public folders to be queried: -- Select public folders from – Enter the name of the server hosting the desired public folders and +- Select public folders from – Enter the name of the server hosting the public folders you want and click **Retrieve**. The box will populate with available public folders. - Add – Adds the selected folders - Add Recursive – Adds the selected folders and all child folders. Not adding recursive folders will @@ -55,13 +55,13 @@ Configure the scope of the selected public folders to be queried: selected host. If enabled, physically housed folders show in bold text in the list that is returned after clicking **Retrieve**. -The selected public folders are added in the table at the bottom. Click **Remove** to delete a +The wizard adds the selected public folders to the table at the bottom. Click **Remove** to delete a selected word from the filter list. ## Scope to Selected Table -When Scope to **Selected Table** is selected on the Scope page, the options to specify the desired -tables are enabled. +When you select Scope to **Selected Table** on the Scope page, the options to specify the desired +tables become available. ![Scope page with Selected Table option selected](/images/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/scopeselectedtable.webp) @@ -71,7 +71,7 @@ Configure the selected tables to be queried: table. Click **Retrieve** to populate the Table name box with all available tables within the database. - - The Table name box can be filtered by entering a name in the textbox and clicking **Retrieve** + - Filter the Table name box by entering a name in the textbox and clicking **Retrieve** -- Field name – Select the desired table and the available fields will populate the Field names box. +- Field name – Select the table you want, and the available fields populate the Field names box. Select the field containing the public folder names. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/summary.md index d8babeaac7..60adc7e846 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/summary.md @@ -11,6 +11,5 @@ categories. ![Exchange Public Folder Data Collector Wizard Summary page](/images/accessanalyzer/11.6/admin/datacollector/exchangepublicfolder/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Exchange Public Folder Data Collector Wizard to ensure that no -accidental clicks are saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** +instead to close the Exchange Public Folder Data Collector Wizard without saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/file/category.md b/docs/accessanalyzer/11.6/admin/datacollector/file/category.md index 8d202a2b40..e9fce7d9b6 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/file/category.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/file/category.md @@ -13,8 +13,8 @@ Use the Category page to identify the type of information to retrieve in this qu The categories are: - Calculate Group Size (Files Only) – Scans of disk space for the amount used by files in each - folder location. This option scopes the query to files so that any information involving the - folders that hold the files is not retrieved. + folder location. This option scopes the query to files so that the query doesn't retrieve any + information involving the folders that hold the files. - File or Folder Properties – Scans the target host for specific attributes and properties associated with certain files and folders in the environment. This option is selected by default. - File or Folder Permissions – Scans files or folders for permission settings and effective diff --git a/docs/accessanalyzer/11.6/admin/datacollector/file/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/file/overview.md index 0f054f8b4f..ef2e849576 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/file/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/file/overview.md @@ -6,8 +6,8 @@ sidebar_position: 210 # File Data Collector -The File Data Collector provides file and folder enumeration, properties, and permissions. It is -used to find files and folders on a target host. The File Data Collector finds one or more files on +The File Data Collector provides file and folder enumeration, properties, and permissions. It finds +files and folders on a target host. The File Data Collector finds one or more files on the target hosts. It can target any file extension. This data collector is a core component of Enterprise Auditor and is available with all Enterprise Auditor licenses. @@ -52,5 +52,5 @@ following wizard pages: ![File Search Wizard Welcome page](/images/accessanalyzer/11.6/admin/datacollector/file/welcome.webp) -The Welcome page can be hidden by selecting the **Do not display this page the next time** checkbox -when the wizard is open and configuration settings are saved. +To hide the Welcome page, select the **Don't display this page the next time** checkbox while the +wizard is open, then save the configuration settings. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/file/results.md b/docs/accessanalyzer/11.6/admin/datacollector/file/results.md index 2eb57750ad..ff6318f956 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/file/results.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/file/results.md @@ -6,13 +6,13 @@ sidebar_position: 30 # File: Results -The Results page provides a list of available properties to be searched for and returned by the job -execution. The properties selected display as table columns in the results of the query. It is a -wizard page for all of the categories. +The Results page provides a list of available properties for the job to search for and return. The +properties selected display as table columns in the results of the query. It is a wizard page for +all of the categories. ![File Search Wizard Results page](/images/accessanalyzer/11.6/admin/datacollector/file/results.webp) -Properties can be selected individually or in groups with the **Select All** or **Clear All** +Select properties individually or in groups with the **Select All** or **Clear All** buttons. The properties available vary based on the category selected. :::note @@ -26,15 +26,15 @@ options on the Results page are grayed out. - This option is available for the **File or Folder Properties** category -- Only return permissions for the following user(s) – Defines users for the query. Enter the desired +- Only return permissions for the following users – Defines users for the query. Enter the desired users in the textbox. - This option is available for the **File or Folder Permissions** category -- Only return permissions for the following group(s) – Defines groups for the query. Enter the +- Only return permissions for the following groups – Defines groups for the query. Enter the desired users in the textbox. - This option is available for the **File or Folder Permissions** category -- Size Units – Identifies the unit in which the values will be displayed. The options are: +- Size Units – Identifies the unit for displaying values. The options are: **Bytes**, **Kb**, **Mb**, or **Gb**. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/file/targetfiles.md b/docs/accessanalyzer/11.6/admin/datacollector/file/targetfiles.md index 7384d4c38a..93735f1f9e 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/file/targetfiles.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/file/targetfiles.md @@ -11,7 +11,7 @@ results for the specific folder or file. It is a wizard page for all of the cate ![File Search Wizard Target Files page](/images/accessanalyzer/11.6/admin/datacollector/file/targetfiles.webp) -Within the Target files configuration page, select the desired method to refine the query. +Within the Target files configuration page, select the method you want to refine the query. :::note Some options are grayed out depending on the option selected. @@ -59,7 +59,7 @@ network neighborhoods which begin with `\\`. used for the lookup by the query - Registry Value – This value is automatically populated from the registry key - - Levels – After a registry path has been selected, the Levels slider can be used to + - Levels – After you select a registry path, use the Levels slider to truncate the path for the key value in the Adjust Path dialog box - Current Value – Displays the type of data each registry value contains - Query 32-bit View – Select this checkbox to query a 32-bit view diff --git a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/activitysettings.md b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/activitysettings.md index e25295ec93..5493e0713e 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/activitysettings.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/activitysettings.md @@ -6,8 +6,8 @@ sidebar_position: 50 # FSAA: Activity Settings -The File System Activity Auditor Scan Filter Settings page is where activity scan filter settings -are configured. It is a wizard page for the category of File System Activity Scan. +Use the File System Activity Auditor Scan Filter Settings page to configure activity scan filter +settings. It is a wizard page for the category of File System Activity Scan. ![FSAA Data Collector Wizard Activity Settings page](/images/accessanalyzer/11.6/admin/datacollector/fsaa/activitysettings.webp) @@ -28,16 +28,16 @@ In the Scan Limit section, configure the following: - Set Log Processing Limit – Stops the scan after the set number of MB or GB of log files are processed and the threshold number is reached -These filters affect what data is collected from the activity logs. However, enabling these filters -also causes the corresponding bulk import query to purge the database of selected activity +These filters affect what data the scan collects from the activity logs. However, enabling these +filters also causes the corresponding bulk import query to purge the database of selected activity information older than the time filter specified here. -If either is left deselected, all available log files are collected and stored. This has a direct -impact on both scan time and database size. +If you leave either deselected, the scan collects and stores all available log files. This has a +direct impact on both scan time and database size. :::tip -Remember, the file activity options require the Activity Monitor to be deployed, configured, and -services running. +Remember, the file activity options require you to deploy and configure the Activity Monitor and run +its services. ::: @@ -55,7 +55,7 @@ Query window. ![Host Mapping Query window](/images/accessanalyzer/11.6/admin/datacollector/fsaa/hostmappingquery.webp) -When the Enable host mapping checkbox is selected, the query textbox is enabled. The SQL query +When you select the Enable host mapping checkbox, the query textbox becomes available. The SQL query provided by a user should return a set of log locations, target hosts, and host names of the Monitored Hosts in the Activity Monitor. The target tables must reside within the Enterprise Auditor database and contain at least the following columns: @@ -71,21 +71,21 @@ database and contain at least the following columns: - Host – Name of the host being targeted in the FSAC scan and Bulk Import which the activity events will be mapped to -Enter the SQL query by clicking Sample Query then replacing the sample text in the textbox, as shown -above. The SQL query must target tables that have the required columns populated with the host +Enter the SQL query by clicking **Sample Query**, then replace the sample text in the textbox as +needed. The SQL query must target tables that have the required columns populated with the host mapping. (Optional) Enter a host in the **Host parameter value (@host)** textbox to test the query to retrieve the data for that host. Select **Test Query** to open a preview of the results in the Query Results window. Ensure that the -data being retrieved by the query is expected. When this option is selected, the data collector runs +query retrieves the expected data. When you select this option, the data collector runs against the target table. ### Host-Agent Mapping -Enterprise Auditor can be configured via the Host Mapping feature to support the use of Multiple -Activity Monitor Agents for a single targeted Host. See the examples below: +You can configure Enterprise Auditor via the Host Mapping feature to support the use of Multiple +Activity Monitor Agents for a single targeted Host. See the following examples: Single-Host Single-Agent Example: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/appletsettings/appletsettings.md b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/appletsettings/appletsettings.md index 985de0e99c..cad2cbf0fd 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/appletsettings/appletsettings.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/appletsettings/appletsettings.md @@ -87,8 +87,8 @@ In the Applet Settings section, configure the following options: while the proxy server is busy, before it enters the job engine queue - Applet communication timeout: [number] minutes – This option determines the length of time (in minutes) the Enterprise Auditor Console attempts to reach the proxy before giving up. Depending on - the job configuration, the data collector behaves in one of three ways after the timeout value has - been exceeded: + the job configuration, the data collector behaves in one of three ways after the timeout value + expires: - If a communication timeout is reached and the **Stop scan on applet communication timeout** option is unchecked, the scan continues running. When the proxy is available again, the data collector gets the database files on the next scan of that host. It will either bring the diff --git a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/azuretenantmapping.md b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/azuretenantmapping.md index 45160fb776..b15c993303 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/azuretenantmapping.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/azuretenantmapping.md @@ -6,7 +6,7 @@ sidebar_position: 70 # FSAA: Azure Tenant Mapping -The Azure Tenant Mapping page is where the target domain or Tenant ID are configured for Azure +Use the Azure Tenant Mapping page to configure the target domain or Tenant ID for Azure Information Protection (AIP) scanning. It is a wizard page for the categories of: - File System Access/Permission Auditing Scan @@ -15,8 +15,8 @@ Information Protection (AIP) scanning. It is a wizard page for the categories of Remember, select the **Enable scanning of files protected by Azure Information Protection** checkbox on the [FSAA: Scan Settings](/docs/accessanalyzer/11.6/admin/datacollector/fsaa/scansettings.md) -page to enable this page in the data collector wizard. In order for FSAA to scan files protected by -AIP, ensure that the prerequisites are met and an Azure Connection Profile is successfully created. +page to enable this page in the data collector wizard. For FSAA to scan files protected by +AIP, ensure that you meet the prerequisites and successfully create an Azure Connection Profile. See the [Azure Information Protection Target Requirements](/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/azureinformationprotection.md) topic for additional information on configuring the File System solution to scan for AIP labels. @@ -24,7 +24,7 @@ topic for additional information on configuring the File System solution to sca ![FSAA Data Collector Wizard Azure Tenant Mapping page](/images/accessanalyzer/11.6/admin/datacollector/fsaa/azuretenantmapping.webp) Populate this page with the App ID (created during prerequisites) and a domain name or Tenant ID for -an Azure environment. These values must be associated with each application ID in the Azure +an Azure environment. Associate these values with each application ID in the Azure Connection Profile. Use the **Add** and **Remove** buttons and manually enter or **Paste** into the textbox the required diff --git a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/bulkimport.md b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/bulkimport.md index 71da515a0f..f11f300589 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/bulkimport.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/bulkimport.md @@ -6,7 +6,7 @@ sidebar_position: 130 # FSAA: Bulk Import Settings -The Bulk Import Settings page is where the bulk import process settings are configured. It is a +Use the Bulk Import Settings page to configure the bulk import process settings. It is a wizard page for the categories of: - Bulk Import File System Access/Permission Auditing @@ -16,5 +16,5 @@ wizard page for the categories of: ![FSAA Data Collector Wizard Bulk Import Settings page](/images/accessanalyzer/11.6/admin/datacollector/fsaa/bulkimport.webp) Select the **Import incomplete scan data** checkbox to enable imports of partial scan data. If the -scan is stopped before successful completion, this option must be checked in order to bulk import +scan stops before successful completion, check this option to bulk import the data from a partially scanned host. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/certificatemanagement/certificatemanagement.md b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/certificatemanagement/certificatemanagement.md index 8b12508a04..819c0cb9a0 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/certificatemanagement/certificatemanagement.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/certificatemanagement/certificatemanagement.md @@ -7,7 +7,7 @@ sidebar_position: 160 # FSAA Applet Certificate Management Overview Communication between the FSAA Data Collector and the FSAA Applet is secure by default using HTTPS. -For authentication, at least three certificates are required and need to be stored in the correct +Authentication requires at least three certificates, which you must store in the correct certificate store managed by the FSAA Data Collector. These three certificates are: - The certificate authority (stored in the FSAA Certificate Authority Store) @@ -16,10 +16,10 @@ certificate store managed by the FSAA Data Collector. These three certificates a :::note The FSAA Data Collector and Applet server support certificates in both the user’s -certificate store and the computer’s certificate store. It is recommended to store certificates in -the user's certificate store that is running the FSAA Data Collector or Applet server because -administrative access is required for the computer's certificate store. When certificates are -generated using the Automatic option below, they are stored in the user’s certificate store. +certificate store and the computer’s certificate store. Store certificates in +the user's certificate store that is running the FSAA Data Collector or Applet server, because +the computer's certificate store requires administrative access. When you generate certificates +using the Automatic option, Enterprise Auditor stores them in the user’s certificate store. ::: @@ -27,21 +27,19 @@ generated using the Automatic option below, they are stored in the user’s cert There are three Certificate Exchange Options provided by the FSAA Data collector: -- Automatic (Default Option) – The creation of a self-signed certificate and certificate exchange - between the FSAA Data Collector and Applet are handled entirely by the FSAA Data Collector and - Applet server +- Automatic (Default Option) – The FSAA Data Collector and Applet server handle the creation of a + self-signed certificate and certificate exchange entirely - The self-signed CA generated will be valid for two years and the FSAA Data Collector and Applet server will also manage expired certificates and remove certificates that are no longer valid from the FSAA stores - Manual – The FSAA Data Collector will expect all certificates to be valid and in their respective - certificate stores prior to running a scan + certificate stores before running a scan - - To create and store certificates, the `FSAACertificateManager.exe` tool can be used. This - application was created to simplify the process of creating certificates and will store the - certificates in the location that the FSAA Data Collector and Applet server expect them to be - stored. See the + - To create and store certificates, use the `FSAACertificateManager.exe` tool. This tool + simplifies the process of creating certificates and stores them in the location that the FSAA + Data Collector and Applet server expect. See the [FSAA Manual Certificate Configuration](/docs/accessanalyzer/11.6/admin/datacollector/fsaa/certificatemanagement/manualcertificate.md) topic for additional information. @@ -51,30 +49,30 @@ There are three Certificate Exchange Options provided by the FSAA Data collector with the `-help` command. :::note - If the FSAA Data Collector and Applet are on separate domains without a trust, this - option must be used. + If the FSAA Data Collector and Applet are on separate domains without a trust, use this + option. ::: - Provide Certificate Authority – The certificate exchange process is the same as with the Automatic option. However, instead of creating a self-signed certificate, the FSAA Data Collector uses a - certificate you provide through the FSAA Data Collector Wizard. The provided certificate is stored - in the FSAA Certificate Authority Store. + certificate you provide through the FSAA Data Collector Wizard. The FSAA Data Collector stores the + provided certificate in the FSAA Certificate Authority Store. :::note - If the provided certificate is not self-signed as the Certificate Authority, the root - certificate and the Certificate Authority’s certificate chain must also be stored in the FSAA + If the provided certificate isn't self-signed as the Certificate Authority, you must also store + the root certificate and the Certificate Authority’s certificate chain in the FSAA Certificate Authority Store on both the client and server hosts. ::: :::warning - The FSAA Applet does not support password-protected certificates. Certificates + The FSAA Applet doesn't support password-protected certificates. Certificates generated when the Automatic option is selected have no password. When manually creating a - certificate for use with the FSAA Applet the password parameter should be omitted. + certificate for use with the FSAA Applet, omit the password parameter. ::: -Additionally, the port used for secure certificate exchange can be configured by selecting the +Additionally, you can configure the port used for secure certificate exchange by selecting the Specify certificate exchange port checkbox on the Applet Settings page of the FSAA Data Collector Wizard. The default port is 8767. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/certificatemanagement/manualcertificate.md b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/certificatemanagement/manualcertificate.md index 53d8371a77..f915047be0 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/certificatemanagement/manualcertificate.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/certificatemanagement/manualcertificate.md @@ -14,16 +14,16 @@ case-sensitive. ## Create and store the required certificates :::note -In these steps, some commands need to be run on the Enterprise Auditor console and some on +In these steps, you run some commands on the Enterprise Auditor console and others on the Proxy host. In the provided example commands: ::: -- All files that are generated by the Certificate Manager or copied to the Enterprise Auditor - console are placed in the +- The Certificate Manager places any files it generates, or that you copy to the Enterprise Auditor + console, in the `%SAInstallDir%\PrivateAssemblies\FILESYSTEMACCESS\Applet\My Certificates` directory. The tool creates this folder if it doesn't already exist. -- When operating on the proxy host, files are placed into the root of the **FSAA** folder +- When you run the tool on the proxy host, it places files into the root of the **FSAA** folder :::tip Remember, all commands in the `FSAACertificateManager.exe` tool are case-sensitive. @@ -131,7 +131,7 @@ copied to: - Replace the CN (`proxy01.my.domain.com`) with the FQDN of the proxy host - Replace the alternate subject name (`proxy01`) with the short name for the proxy host -- The generated certificate signing request and key are stored in the same directory as +- The tool stores the generated certificate signing request and key in the same directory as `FSAACertificateManager.exe` on the proxy host The following message appears when the command completes successfully: @@ -186,12 +186,12 @@ Successfully added FSAA_Server_Auth to Server **Step 11 –** Repeat Steps 6-10 for each proxy host. -**Step 12 –** Delete all the PFX, CER, and Key files that were generated or copied in the earlier +**Step 12 –** Delete all the PFX, CER, and Key files generated or copied in the earlier steps from the output locations. -You have now stored all the required FSAA certificates in the FSAA managed certificate stores. The -FSAA queries need to be configured to use the **Manual** certificate exchange option. This option -can be found under Applet Settings in the FSAA Data Collector Wizard. See the +You have now stored all the required FSAA certificates in the FSAA managed certificate stores. +Configure the FSAA queries to use the **Manual** certificate exchange option. You can find this +option under Applet Settings in the FSAA Data Collector Wizard. See the [FSAA: Applet Settings](/docs/accessanalyzer/11.6/admin/datacollector/fsaa/appletsettings/appletsettings.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/defaultscopingoptions/defaultscopingoptions.md b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/defaultscopingoptions/defaultscopingoptions.md index 0e010abf76..748eaa6d38 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/defaultscopingoptions/defaultscopingoptions.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/defaultscopingoptions/defaultscopingoptions.md @@ -6,10 +6,9 @@ sidebar_position: 80 # FSAA: Default Scoping Options -The Default Scoping Options page is where scan settings, file details, and file properties settings -can be configured for every resource in the targeted environment by the data collector. The settings -assigned on this page are used by all resources involved in the scan. It is a wizard page for the -categories of: +Use the Default Scoping Options page to configure scan settings, file details, and file properties +settings for every resource the data collector targets in the environment. All resources involved in +the scan use the settings you assign on this page. It is a wizard page for the categories of: - File System Access/Permission Auditing Scan - Sensitive Data Scan diff --git a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/defaultscopingoptions/filedetails.md b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/defaultscopingoptions/filedetails.md index a97d5056fd..dac91f59c6 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/defaultscopingoptions/filedetails.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/defaultscopingoptions/filedetails.md @@ -6,11 +6,11 @@ sidebar_position: 20 # File Details Tab -The File Details tab allows configuration of settings for file detail collection. +Use the File Details tab to configure settings for file detail collection. ![FSAA Data Collector Wizard Default Scoping Options page File Details tab](/images/accessanalyzer/11.6/admin/datacollector/fsaa/defaultscopingoptions/filedetails.webp) -Select the desired settings for additional scoping: +Select the settings you want for additional scoping: - Scan file-level details – Turns on file-level scanning and collects a full list of files, file size, last modified, and last accessed @@ -35,11 +35,10 @@ provides a count for the number of occurrences of each tag. **Scan filter settings** -The Scan filter settings options are enabled if the **Scan file-level details** checkbox is -selected. +You enable the Scan filter settings options by selecting the **Scan file-level details** checkbox. - Only files larger than [number] [size unit] – Filters the results to only collect file data on - files larger than the set value. If this option is not set, all file sizes are collected. + files larger than the set value. If this option isn't set, all file sizes are collected. - Only files last modified more than [number] [time period] ago – Filters results to only collect file data on files modified older than the set value - Only files last modified less than [number] [time period] ago – Filters results to only collect @@ -49,7 +48,7 @@ selected. not set, all file types are collected. :::warning -Be careful when configuring these settings. If no filters are applied when file detail -scanning has been enabled, it can result in returning large amounts of data to the database. +Be careful when configuring these settings. If you don't apply filters after enabling file +detail scanning, the scan can return large amounts of data to the database. ::: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/defaultscopingoptions/fileproperties.md b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/defaultscopingoptions/fileproperties.md index c8d65e5e3a..577e8cb293 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/defaultscopingoptions/fileproperties.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/defaultscopingoptions/fileproperties.md @@ -6,8 +6,8 @@ sidebar_position: 30 # File Properties (Folder Summary) Tab -The File Properties (Folder Summary) tab is where file property collection settings for the scan is -configured. +Use the File Properties (Folder Summary) tab to configure file property collection settings for the +scan. ![FSAA Data Collector Wizard Default Scoping Options page File Properties (Folder Summary) tab](/images/accessanalyzer/11.6/admin/datacollector/fsaa/defaultscopingoptions/fileproperties.webp) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/defaultscopingoptions/scansettings.md b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/defaultscopingoptions/scansettings.md index 361cfe4a9d..e6f97f664f 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/defaultscopingoptions/scansettings.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/defaultscopingoptions/scansettings.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Scan Settings Tab -The Scan Settings tab allows configuration of data collection settings. +Use the Scan Settings tab to configure data collection settings. ![FSAA Data Collector Wizard Default Scoping Options page Scan Settings tab](/images/accessanalyzer/11.6/admin/datacollector/fsaa/scansettings.webp) @@ -18,16 +18,16 @@ The Scan Settings tab has the following configurable options: - Exclude snapshot directories on NetApp server – Excludes folders on NetApp Filers that begin with ~snapshot -- Exclude system shares – Part of the OS that most users don’t have access to so its hidden by - Microsoft +- Exclude system shares – Excludes parts of the OS that most users can't access; Microsoft hides + these by default - Exclude hidden shares – Excludes shares with names ending with $ - Last Access Time (LAT) preservation – Preserves Data Access timestamp attribute on files that are scanned for Metadata tags and sensitive data - - Warn if unable to preserve Last Access Time – Scan throws a warning if the LAT cannot be - preserved. The file is still scanned unless the Skip file if unable to preserve Last Access - Time checkbox is also selected. - - Skip file if unable to preserve Last Access Time – Scan skips the file if the LAT cannot be + - Warn if unable to preserve Last Access Time – Scan throws a warning if the LAT can't be + preserved. The scan still processes the file unless you also select the Skip file if unable to + preserve Last Access Time checkbox. + - Skip file if unable to preserve Last Access Time – Scan skips the file if the LAT can't be preserved Selecting the **Last Access Time (LAT) preservation** checkbox enables the **Action on failure to @@ -37,13 +37,13 @@ enable LAT preservation** and **Action on changed LAT after scan** dropdown me - Action on failure to enable LAT Preservation – Before scanning each file, FSAA attempts to enable an operating system feature to preserve the LAT when accessing the file. This operation may fail - for a variety of reasons, which include but are not limited to: the operating system or file - system where the file is located does not support LAT preservation, or insufficient permissions + for a variety of reasons, which include but aren't limited to: the operating system or file + system where the file is located doesn't support LAT preservation, or insufficient permissions from the service account trying to access the file. The following configuration addresses a failure to enable the LAT preservation mode: - Continue to scan file silently – FSAA scans the file with the possibility that LAT - preservation is not possible. No warning will be shown. + preservation isn't possible. No warning will be shown. - Continue to scan file with warning – FSAA scans the file with the possibility that LAT will not be preserved. A warning will be shown for this file. - Skip file silently – FSAA will not scan the file. No warning will be shown. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/queryselection.md b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/queryselection.md index 673710961e..9edd796708 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/queryselection.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/queryselection.md @@ -28,7 +28,7 @@ auditing focus: - Scan and import – Collects Distributed File System information :::note - Starting with v8.1, DFS Audits are completed with a streaming method and do not + Starting with v8.1, DFS Audits are completed with a streaming method and don't require a bulk import query following the scan query. ::: @@ -61,9 +61,9 @@ Once a query scan using the FSAA DC has been executed, the **Maintenance** butto allow troubleshooting of scan errors that may have occurred. :::warning -Do not use the Maintenance button unless instructed by -[Netwrix Support](https://www.netwrix.com/support.html). It is possible to cause corruption of the -database and loss of data to occur. +Don't use the Maintenance button unless instructed by +[Netwrix Support](https://www.netwrix.com/support.html). Using it incorrectly can corrupt the +database and cause data loss. ::: @@ -75,7 +75,7 @@ errors. ![Maintenance Wizard Maintenance Selection page](/images/accessanalyzer/11.6/admin/datacollector/fsaa/maintenancewizardselection.webp) -The Maintenance Selection page allows you to select the type of maintenance to be performed: +Use the Maintenance Selection page to select the type of maintenance to perform: - Reset Hosts – Resets the Access GUID column value in the SA_FSAA_Hosts table for the Hosts selected. Allows data to be bulk imported when there is a GUID mismatch. @@ -89,14 +89,14 @@ selection made. ![Maintenance Wizard Reset Hosts page](/images/accessanalyzer/11.6/admin/datacollector/fsaa/maintenancewizardresethosts.webp) - Select the desired hosts to reset the SQL data for, and click **Reset Hosts** to perform the + Select the hosts you want to reset the SQL data for, and click **Reset Hosts** to perform the maintenance. - If Repair was selected, the Repair Tool page displays: ![Maintenance Wizard Repair Tool page](/images/accessanalyzer/11.6/admin/datacollector/fsaa/maintenancewizardrepair.webp) - Select the desired hosts to repair the SQL data for, and click **Run** to perform the + Select the hosts you want to repair the SQL data for, and click **Run** to perform the maintenance. Click **Finish** to close the wizard when you have completed the required maintenance. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/scanserverselection.md b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/scanserverselection.md index 07eec1a634..3a2f14bdfc 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/scanserverselection.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/scanserverselection.md @@ -46,7 +46,7 @@ Using the radio buttons, select where the execution of the applet will take plac choose from. If more than one list is selected, scanning is distributed across each host. :::info -It is best practice in global implementations to utilize a specific remote server or proxy scanner +It is best practice in global implementations to use a specific remote server or proxy scanner that is located in the same data center as the target hosts. This is particularly beneficial if the Enterprise Auditor Console server is in a different data center. See the [Proxy Scanning Architecture](/docs/accessanalyzer/11.6/install/filesystemproxy/overview.md#proxy-scanning-architecture) @@ -55,7 +55,7 @@ topic for additional information. In the bottom section, the checkbox options affect the execution of the applet: -- Fallback to local mode if applet can't start – If the applet cannot be deployed on the target +- Fallback to local mode if applet can't start – If the applet can't be deployed on the target host, it is deployed locally on the same server as the Enterprise Auditor Console and the scan collects data across the network - Run remote applet with normal priority (non-proxy applet server uses background priority by diff --git a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/scansettings.md b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/scansettings.md index 9bef9e0467..6e9b531d84 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/scansettings.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/scansettings.md @@ -14,16 +14,16 @@ wizard page for the categories of: ![FSAA Data Collector Wizard Scan Settings page](/images/accessanalyzer/11.6/admin/datacollector/fsaa/scansettings_1.webp) -In the Scan Protocols section, select the desired checkboxes for including certain types of shared +In the Scan Protocols section, select the checkboxes you want for including certain types of shared folders: - Scan Windows (SMB/CIFS) shares – Includes types of Windows and NAS shares - Scan NFS exports (shares) – Includes this type of UNIX and NAS shares -In the middle section, select the desired checkboxes for additional settings: +In the middle section, select the checkboxes you want for additional settings: - Enable file system scan streaming – Sends the streamed data directly to the Enterprise Auditor - database. A bulk import query is not required when this option is selected + database. A bulk import query isn't required when this option is selected - Enable scanning of files protected by Azure Information Protection – Adds additional options to this wizard to scan for protection labels and encrypted files for sensitive data @@ -37,7 +37,7 @@ In the middle section, select the desired checkboxes for additional settings: permissions. Click **Configure Query** to open the Manual Shares Query window. See the [Enable the Use SQL Query to Manually Specify Shares](#enable-the-use-sql-query-to-manually-specify-shares) topic for additional information. -- NetApp communication security – This option provides the ability to choose levels of encryption +- NetApp communication security – This option lets you choose levels of encryption and authentication applied during Access Auditing scans of NetApp devices ![NetApp communication security options](/images/accessanalyzer/11.6/admin/datacollector/fsaa/scansettingsnetapp.webp) @@ -83,7 +83,7 @@ columns for all shares in the target environment: - Host – Name of host where the share resides matching the Host Master table Name field value :::info - Use this column but it is not required. + Use this column but it isn't required. ::: @@ -121,7 +121,7 @@ When this option is selected, the data collector runs against the target table t in the environment. :::tip -Remember, if a share is not in the target table, the data collector assumes that the share does +Remember, if a share isn't in the target table, the data collector assumes that the share does not exist and marks it as deleted. ::: @@ -130,7 +130,7 @@ not exist and marks it as deleted. The HTTPS encryption options for the NetApp communication security setting of the global Remote Data Collection Configuration page in the File System Access Auditor Data Collector Wizard requires a -certificate. If the organization uses a self-signed certificate, it is necessary to add this +certificate. If the organization uses a self-signed certificate, add this certificate to enable HTTPS encryption of Enterprise Auditor communications. The certificate (`cacert.pem`) which is shipped with Enterprise Auditor is in the DC folder of the @@ -140,14 +140,14 @@ installation directory. The default location is: If employing remote applet mode or proxy servers, then the certificate (`cacert.pem`) must exist in the FSAA folder where the `FSAAAppletServer.exe` process is running (applet/proxy host). Therefore, -it is necessary to also copy it to the FSAA folder on the target hosts andr proxy servers. This is +also copy it to the FSAA folder on the target hosts andr proxy servers. This is done at runtime when using remote applet mode, but any updates or custom certificates must be copied manually. The default location is: **…\STEALTHbits\StealthAUDIT\FSAA** :::info -Do not overwrite this certificate. It is fully trusted by Netwrix. Instead, add +Don't overwrite this certificate. It is fully trusted by Netwrix. Instead, add an underscore (_) character to the start of the file name. Then copy the organization's self-signed certificate to this location with the name `cacert.pem`. ::: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/scopingoptions.md b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/scopingoptions.md index 519ceed7e2..99c5a1412a 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/scopingoptions.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/scopingoptions.md @@ -31,7 +31,7 @@ The Scoping Options buttons have the following: imported, the user will be prompted to resolve the conflict by either keeping the existing configuration or importing the new one, which will overwrite the scoping option. -- Export – Take the currently configured scoping options in the job and export it to a `.fsaascope` +- Export – Take the configured scoping options in the job and export it to a `.fsaascope` file By default, priority is assigned in the order it is added to the table. Priority can also be @@ -54,7 +54,7 @@ default scoping settings for the selected resource. Set the Resource Name and Host Name: - Resource Name – Specify a local path or individual share to the target folder or the share name -- Host Name – Apply scoping options to a specific target host. If a host name is not supplied, all +- Host Name – Apply scoping options to a specific target host. If a host name isn't supplied, all hosts targeted by the job have the scoping options applied. Both the Resource Name and Host Name textboxes support regular expressions and pattern matching. @@ -94,7 +94,7 @@ Then set Scoping Type and Priority: :::note Any included files or folders inherit all options previously checked in the [FSAA: Default Scoping Options](/docs/accessanalyzer/11.6/admin/datacollector/fsaa/defaultscopingoptions/defaultscopingoptions.md) - page. Manually apply new options if the default ones are not desired in this scan. + page. Manually apply new options if the default ones aren't desired in this scan. ::: @@ -178,7 +178,7 @@ All other folder paths are excluded. **Additional Considerations** -The scoping options listed above can be used to scope for SMB shares and NFS exports but NFS exports +Use the scoping options listed above to scope for SMB shares and NFS exports, but NFS exports are enumerated differently. The include/exclude logic outlined above should be the same for both, but when scoping for NFS exports the Resource Name should be the full path to the export. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/scopingqueries.md b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/scopingqueries.md index 0ea1057685..3d0b23540c 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/scopingqueries.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/scopingqueries.md @@ -48,7 +48,7 @@ The Scoping Queries buttons have the following functionality: :::note These two Scan Resource Filters are both Share Include queries by default. To restrict the -scan to only Open Shares or only DFS Shares it is necessary to also configure the Scoping Options on +scan to only Open Shares or only DFS Shares, also configure the Scoping Options on the previous page of the wizard to exclude all other shares. ::: @@ -68,8 +68,8 @@ topic for additional information and common scoping scenarios. ## Scoping Query Configuration Window -The Scoping Query Configuration window allows you to create a custom Scoping Query to specify shares -and folders to be included in or excluded from the scan. +Use the Scoping Query Configuration window to create a custom Scoping Query that specifies shares +and folders to include in or exclude from the scan. ![Scoping Query Configuration window](/images/accessanalyzer/11.6/admin/datacollector/fsaa/scopingqueryconfiguration.webp) @@ -94,7 +94,7 @@ Scoping Options Query Configuration window. ![Advanced Scoping Options Query Configuration window](/images/accessanalyzer/11.6/admin/datacollector/fsaa/advancedscopingoptionsqueryconfiguration.webp) -Follow the steps to configure a query. +To configure a query: **Step 1 –** Enter a SQL Query that will return a list of resources to be included in or excluded from the scan. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/sensitivedatasettings.md b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/sensitivedatasettings.md index 55b1884eb6..caa24f90a6 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/sensitivedatasettings.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/sensitivedatasettings.md @@ -45,7 +45,7 @@ Use the radio buttons to select the File types to scan: - Spreadsheets - Text/Markup files -- Perform differential scan of – Enables users to choose whether to employ incremental scanning: +- Perform differential scan of – Lets you choose whether to use incremental scanning: - Files modified or newly discovered since last scan – Scans newly discovered files and files with a modified date after the previous scan date @@ -62,7 +62,7 @@ been installed on the Enterprise Auditor Console. The Performance Options section allows the user to modulate the efficiency of SDD scans. - Number of SDD scan processes [number] – Increases the number of SDD scanner processes that spawn - as part of a scan, increasing parallel scanning. The value should not exceed 2x the number of CPU + as part of a scan, increasing parallel scanning. The value shouldn't exceed 2x the number of CPU threads available. :::info diff --git a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/standardtables.md b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/standardtables.md index 94045aa074..b8ebf7321f 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/standardtables.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/standardtables.md @@ -26,8 +26,8 @@ The tables and their associated views are grouped by types. | Tables | Details | | -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| SA_FSAA_Trustees | Contains information about any domain user, group, or security principal that has been assigned permissions. This table does not contain local users and groups since none of the trustees in this table are specific to any one host. | -| SA_FSAA_LocalTrustees | Contains information about any trustees that do not belong to a domain, primarily local users and local groups | +| SA_FSAA_Trustees | Contains information about any domain user, group, or security principal that has been assigned permissions. This table doesn't contain local users and groups since none of the trustees in this table are specific to any one host. | +| SA_FSAA_LocalTrustees | Contains information about any trustees that don't belong to a domain, primarily local users and local groups | | SA_FSAA_TrusteeEquivalence | Contains information about Local Group membership. The trustees described can be found in the SA_FSAA_LocalTrustees table. | **Access Calculation Tables** diff --git a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/workflows.md b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/workflows.md index 7088b7f5df..f55364e625 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/workflows.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/workflows.md @@ -33,12 +33,12 @@ job it is applied to. ## Remove File System Access Scan Category -The FSAA Data Collector can be used to clean-up or troubleshoot the applet and proxy scanning +Use the FSAA Data Collector to clean up or troubleshoot the applet and proxy scanning servers. This would need to be done through a new job’s query. Set the host list and Connection -Profile to target the desired applet and proxy servers. +Profile to target the applet and proxy servers you want. -Follow these steps to build a new query using the FSAA Data Collector with the Remove scan -executables and data category. +To build a new query using the FSAA Data Collector with the Remove scan +executables and data category: **Step 1 –** Navigate to the **Configure** node of a new or chosen job and select the **Queries** node. @@ -46,7 +46,7 @@ node. **Step 2 –** In the Query Selection view, click the **Create Query** link. The Query Properties window displays. -**Step 3 –** Select the **Data Source** tab. From the **Data Collector** drop-down menu, select +**Step 3 –** Select the **Data Source** tab. From the **Data Collector** dropdown menu, select **FILESYSTEMACCESS** and then click the **Configure** button. The File System Access Auditor Data Collector Wizard opens. @@ -62,20 +62,20 @@ audit scan applet and data from the target server. Run the job to clean-up the t ## Update Proxy Service Category -The FSAA Data Collector can be used to upgrade the File System Proxy Service already installed on +Use the FSAA Data Collector to upgrade the File System Proxy Service already installed on proxy servers. The FS_UpdateProxy Job is preconfigured to run with the default settings with the category of Update proxy service. It is available through the Instant Job Library under the File System library. The Update Proxy Service category option enables users with the ability to update v8.0+ File System Proxy Service installations to newer versions. When this query is employed, the job compresses the -updated binaries and deploy them to the proxy server. Once the proxy server has no active sessions, +updated binaries and deploy them to the proxy server. When the proxy server has no active sessions, the Netwrix Enterprise Auditor FSAA Proxy Scanner service shuts down and the components are updated. Finally, the service restarts itself. :::note -This option is not for updating v7.x File System Proxy installations. Those must be -manually updated to at least v8.0 on the proxy server before this query can be used to automate the +This option isn't for updating v7.x File System Proxy installations. Those must be +manually updated to at least v8.0 on the proxy server before you can use this query to automate the process. ::: @@ -86,14 +86,14 @@ and use the FS_UpdateProxy Job. ## Remove Host Category -The FSAA Data Collector can be used to clean-up the Standard Reference Tables by removing data for +Use the FSAA Data Collector to clean up the Standard Reference Tables by removing data for particular hosts. This would need to be done through a new job’s query. The host to be removed is set as the host list for the new job. The Connection Profile applied should be the same as the one used for the associated **FileSystem** > **0.Collection** > … **Bulk Import** Job. :::warning Be careful when applying this query task, as it results in the deletion of collected -data. Ensure proper configuration prior to job execution. +data. Ensure proper configuration before job execution. ::: @@ -102,8 +102,8 @@ Manually enter individual hosts into the host list executing this query. ::: -Follow the steps to build a new query using the FSAA Data Collector with the Remove host data -category. +To build a new query using the FSAA Data Collector with the Remove host data +category: **Step 1 –** Navigate to the **Configure** node of a new or chosen job and select the **Queries** node. @@ -111,7 +111,7 @@ node. **Step 2 –** In the Query Selection view, click the **Create Query** link. The Query Properties window displays. -**Step 3 –** Select the **Data Source** tab. From the **Data Collector** drop-down menu, select +**Step 3 –** Select the **Data Source** tab. From the **Data Collector** dropdown menu, select **FILESYSTEMACCESS** and then click **Configure**. The File System Access Auditor Data Collector Wizard opens. @@ -127,14 +127,14 @@ job’s **Configure** > **Hosts** node. Run the job to clean-up the targeted hos :::tip Remember, this job deletes data from the Enterprise Auditor database. Use caution and ensure -proper configuration prior to job execution. +proper configuration before job execution. ::: ## Remove Host and Criteria SDD Data The FS_SDD_DELETE job removes host and criteria sensitive data matches from the Tier 1 database. It -is preconfigured to run analysis tasks with temporary tables that requires modification prior to job +is preconfigured to run analysis tasks with temporary tables that requires modification before job execution. It is available through the Instant Job Library under the File System library. See the [Instant Job Wizard](/docs/accessanalyzer/11.6/admin/jobs/instantjobs/overview.md) topic for additional information. @@ -161,10 +161,10 @@ Applying these analysis tasks result in the deletion of collected data. ### Configure the FS_SDD_DELETE Analysis Tasks -Follow the steps to configure and run the analysis tasks. +To configure and run the analysis tasks: -**Step 1 –** Prior to job execution, modify the desired analysis tasks using the -[Customizable Analysis Parameters for FS_SDD_DELETE Job](#customizable-analysis-parameters-for-fs_sdd_delete-job) +**Step 1 –** Before job execution, modify the analysis tasks you want using the +[Customizable Analysis Parameters for FS_SDD_DELETE Job](#customizable-analysis-parameters-for-fssdddelete-job) instructions. **Step 2 –** In the Analysis Selection Pane, check the type of analysis task that will be run. @@ -176,7 +176,7 @@ status is visible from the **Running Instances** node. analysis tasks. :::warning -Do not leave these analysis tasks checked in order to avoid accidental data loss. +Don't leave these analysis tasks checked to avoid accidental data loss. ::: @@ -195,11 +195,11 @@ be deleted during this job’s analysis. | Remove Host & Criteria | #Criteria #hosts | List of Criteria and Host Names to be removed | The parameters that can be customized are listed in a section at the bottom of the SQL Script -Editor. Follow the steps to customize analysis task parameters. +Editor. To customize analysis task parameters: **Step 1 –** Navigate to the **FS_SDD_DELETE** > **Configure** node and select **Analysis**. -**Step 2 –** In the Analysis Selection view, select the desired analysis task and click on +**Step 2 –** In the Analysis Selection view, select the analysis task you want and click **Analysis Configuration**. The SQL Script Editor opens. ![ FS_SDD_DELETE Job Analysis Task in SQL Script Editor](/images/accessanalyzer/11.6/admin/datacollector/fsaa/sdddeletesqlscripteditor.webp) @@ -209,7 +209,7 @@ or **#hosts** row, depending on the analysis task chosen, and then **Edit Table* window opens. :::warning -Do not change any parameters where the Value states `Created during execution`. +Don't change any parameters where the Value states `Created during execution`. ::: @@ -264,7 +264,7 @@ Applying these analysis tasks result in the deletion of collected data. - **4. Drop FSDFS Tables** – Drops the File System DFS Auditing tables imported from the previous runs - **5. Drop FSAA Tables** – Drops File System Access Auditing tables imported from the previous runs -Do not try to run these tasks separately, as they are designed to work together. Follow these steps +Don't try to run these tasks separately, as they are designed to work together. Follow these steps to run the analysis tasks: **Step 1 –** In the Analysis Selection Pane, click **Select All**. All tasks will be checked. @@ -276,7 +276,7 @@ status is visible from the **Running Job** node. All** to deselect these analysis tasks. :::warning -Do not leave these analysis tasks checked in order to avoid accidental data loss. +Don't leave these analysis tasks checked to avoid accidental data loss. ::: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/grouppolicy/category.md b/docs/accessanalyzer/11.6/admin/datacollector/grouppolicy/category.md index 023fdd9ac9..a54f972b0d 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/grouppolicy/category.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/grouppolicy/category.md @@ -6,23 +6,23 @@ sidebar_position: 10 # GroupPolicy: Category -On the GroupPolicy Data Collector Category page, select the required query category to be executed. +On the GroupPolicy Data Collector Category page, select the query category to run. ![Group Policy Data Collector Wizard Category page](/images/accessanalyzer/11.6/admin/datacollector/grouppolicy/category.webp) The available categories are: - Group Policy Objects – Retrieves the GPO’s list in the domain and where each is linked -- Policies State – Provides the ability to return information on configured policies and policy - parts from the individual policies which have been selected +- Policies State – lets you return information on configured policies and policy + parts from the individual policies you select - - For example, selecting **Account Policies** > **Policy Password** will result in **Account - Policies** > **Policy Password** being returned for the targeted domains + - For example, if you select **Account Policies** > **Policy Password**, the query returns + **Account Policies** > **Policy Password** for the targeted domains -- Policies State for all GPOs – Provides the ability to return information on selected policy parts +- Policies State for all GPOs – lets you return information on selected policy parts from all policies within the domain - - For example, selecting **Account Policies** > **Password Policy** will result in **Password - Policy** being returned for all policies in the targeted domains + - For example, if you select **Account Policies** > **Password Policy**, the query returns + **Password Policy** for all policies in the targeted domains - Local policies – Returns effective security policies in effect at the individual workstation diff --git a/docs/accessanalyzer/11.6/admin/datacollector/grouppolicy/options.md b/docs/accessanalyzer/11.6/admin/datacollector/grouppolicy/options.md index b169c86ec8..a1d2ab1bdd 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/grouppolicy/options.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/grouppolicy/options.md @@ -6,14 +6,14 @@ sidebar_position: 40 # GroupPolicy: Options -The Options page is used to configure how to return multi-valued properties and how policy results -are presented. It is a wizard page for all categories. +Use the Options page to configure how to return multi-valued properties and how to present policy +results. It is a wizard page for all categories. ![Group Policy Data Collector Wizard Options page](/images/accessanalyzer/11.6/admin/datacollector/grouppolicy/options.webp) The configurable options are: -- Result Presentation – Select one of the following options. This section is not available for the +- Result Presentation – Select one of the following options. This section isn't available for the Group Policy Objects category. - Each part of each policy on a new row diff --git a/docs/accessanalyzer/11.6/admin/datacollector/grouppolicy/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/grouppolicy/overview.md index 87c82a94a4..261d7b1905 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/grouppolicy/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/grouppolicy/overview.md @@ -6,13 +6,13 @@ sidebar_position: 230 # GroupPolicy Data Collector -The GroupPolicy Data Collector provides the ability to retrieve the GPO’s list in the domain and +The GroupPolicy Data Collector lets you retrieve the GPO’s list in the domain and where they are linked, return information on configured policies and policy parts from the -individual policies that have been selected, return information on selected policy parts from all +individual policies you select, return information on selected policy parts from all policies within the domain, and return effective security policies in effect at the individual workstation. -The GroupPolicy Data Collector is a core component of Enterprise Auditor, but it has been +The GroupPolicy Data Collector is a core component of Enterprise Auditor, but it comes preconfigured within the Active Directory Solution and the Windows Solution. While the data collector is available with all Enterprise Auditor license options, the Windows Solution is only available with a special Enterprise Auditor licenses. See the following topics for additional @@ -52,5 +52,5 @@ pages: ![Group Policy Data Collector Wizard Welcome page](/images/accessanalyzer/11.6/admin/datacollector/grouppolicy/welcome.webp) -The Welcome page can be hidden by selecting the **Do not display this page the next time** checkbox -when the wizard is open and configuration settings are saved. +To hide the Welcome page, select the **Don't display this page the next time** checkbox while the +wizard is open, then save the configuration settings. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/grouppolicy/policieslist.md b/docs/accessanalyzer/11.6/admin/datacollector/grouppolicy/policieslist.md index 623a093613..46a74efc15 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/grouppolicy/policieslist.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/grouppolicy/policieslist.md @@ -6,7 +6,7 @@ sidebar_position: 30 # GroupPolicy: Policies List -The Policies List page is where the policies from the desired GPOs to be queried are selected. It is +The Policies List page is where you select the policies from the GPOs you want to query. It is a wizard page for the categories of: - Policies State @@ -15,10 +15,10 @@ a wizard page for the categories of: ![Group Policy Data Collector Wizard Policies List page](/images/accessanalyzer/11.6/admin/datacollector/grouppolicy/policieslist.webp) -Select the policies or policy parts to be audited. The category dictates how this selection is -applied across the domain or local host. +Select the policies or policy parts to audit. The category dictates how the query applies this +selection across the domain or local host. -To search parts of a policy, drill into the policy and select the desired policy parts. Click +To search parts of a policy, drill into the policy and select the policy parts you want. Click **Check all** to select all properties, and click **Uncheck all** to deselect all properties. Search for a policy by entering a policy name in the Search box and clicking **Search**. @@ -27,4 +27,4 @@ The policy parts returned may have multiple values. ::: -At least one policy or policy part must be selected in order to proceed to the next wizard page. +Select at least one policy or policy part to proceed to the next wizard page. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/grouppolicy/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/grouppolicy/summary.md index c2096cf70e..2985e40d1f 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/grouppolicy/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/grouppolicy/summary.md @@ -10,6 +10,5 @@ The Summary page displays a summary of the configured query. It is a wizard page ![Group Policy Data Collector Wizard Summary page](/images/accessanalyzer/11.6/admin/datacollector/grouppolicy/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Group Policy Data Collector Wizard to ensure that no accidental clicks -are saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** +instead to close the Group Policy Data Collector Wizard without saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/grouppolicy/target.md b/docs/accessanalyzer/11.6/admin/datacollector/grouppolicy/target.md index 4e5dad5f6a..5e3a0d7d17 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/grouppolicy/target.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/grouppolicy/target.md @@ -6,8 +6,8 @@ sidebar_position: 20 # GroupPolicy: Target -The Target page is where a host from which to get data (in wizard only) and .admx source are -identified. It is a wizard page for the categories of: +Use the Target page to identify a host to get data from (in wizard only) and the .admx source. It is +a wizard page for the categories of: - Policies State - Policies State for all GPOs @@ -19,9 +19,9 @@ In the Connect to section of the page, select from the following options: - Default domain – Select this option to connect to the default domain - This domain – Select this option and click the ellipsis to open the Browse for Domain window. Then - select the desired domain. Click **OK**. + select the domain you want. Click **OK**. -In the Use these job credentials to browse section of the page, if multiple credentials are set up, +In the Use these job credentials to browse section of the page, if you set up multiple credentials, select the credentials to use for the query from the dropdown menu. :::note diff --git a/docs/accessanalyzer/11.6/admin/datacollector/inifile/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/inifile/overview.md index fd6c07dc23..8764c21a56 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/inifile/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/inifile/overview.md @@ -36,5 +36,5 @@ following wizard pages: ![INI File Data Collector Wizard Welcome page](/images/accessanalyzer/11.6/admin/datacollector/inifile/welcome.webp) -The Welcome page can be hidden by selecting the **Do not display this page the next time** box when -the wizard is open and configuration settings are saved. +To hide the Welcome page, select the **Don't display this page the next time** box while the wizard +is open, then save the configuration settings. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/inifile/properties.md b/docs/accessanalyzer/11.6/admin/datacollector/inifile/properties.md index 503cb4b141..15ae1c6c3c 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/inifile/properties.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/inifile/properties.md @@ -15,7 +15,7 @@ Use the following options to determine which data to adult: - All contents – Collect all contents from the INI file :::note - `*` can be used for matching wildcard or single characters. + Use `*` to match wildcard or single characters. ::: @@ -27,7 +27,8 @@ Use the following options to determine which data to adult: - Click the ellipses (**…**) to open a file explorer window - Select an appropriate .INI file -- Properties – Select a checkbox next to any desired properties. **Select All** or **Clear All** can - also be used. +- Properties – Select a checkbox next to any desired properties. You can also use **Select All** or + **Clear All**. - If **Differences from standard** is selected, all properties are selected and cannot be altered. + If you select **Differences from standard**, the wizard selects all properties, and you can't + change them. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/inifile/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/inifile/summary.md index f4dc38e6cb..68494c8be4 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/inifile/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/inifile/summary.md @@ -6,10 +6,9 @@ sidebar_position: 30 # INIFile: Summary -The Summary page is where the selected configuration settings are listed. +Use the Summary page to review the selected configuration settings. ![INI File Data Collector Wizard Summary page](/images/accessanalyzer/11.6/admin/datacollector/inifile/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the INIFile Data Collector Wizard ensuring that no accidental clicks are -saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** +instead to close the INIFile Data Collector Wizard without saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/inifile/targetfiles.md b/docs/accessanalyzer/11.6/admin/datacollector/inifile/targetfiles.md index 4ce177dd9c..9cab813399 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/inifile/targetfiles.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/inifile/targetfiles.md @@ -17,10 +17,10 @@ Configure the Target Files options: `drive:\filepath` - Registry Lookup – Select this option to obtain a path from a registry key that exists on the target host in the environment. Click the ellipsis (**…**) to open the Enterprise Auditor Registry - Browser and connect to a host to select a registry key and path to be used for the lookup. + Browser and connect to a host to select a registry key and path to use for the lookup. - - Registry Value – This value is automatically populated from the registry key - - Levels – The Levels slider can be used to truncate the path for the key value in the Adjust + - Registry Value – The wizard automatically populates this value from the registry key + - Levels – Use the Levels slider to truncate the path for the key value in the Adjust Path dialog box - Current value – Displays the current value for the registry key diff --git a/docs/accessanalyzer/11.6/admin/datacollector/ldap.md b/docs/accessanalyzer/11.6/admin/datacollector/ldap.md index 2e8c3c049c..6cef45eced 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/ldap.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/ldap.md @@ -7,11 +7,11 @@ sidebar_position: 250 # LDAP Data Collector The LDAP Data Collector uses LDAP to query Active Directory returning the specified objects and -attributes. For example, a query can be configured to return all user objects at the selected level. -Another query can be configured to return a master list of all user objects found within the target -domain. Wildcards and LDAP filters can be applied to the query configurations. +attributes. For example, you can configure a query to return all user objects at the selected level. +You can configure another query to return a master list of all user objects found within the target +domain. You can apply wildcards and LDAP filters to the query configurations. -The LDAP Data Collector is a core component of Enterprise Auditor, but it has been preconfigured +The LDAP Data Collector is a core component of Enterprise Auditor, but it comes preconfigured within the Active Directory Solution. While the data collector is available with all Enterprise Auditor license options, the Active Directory Solution is only available with a special Enterprise Auditor license. See the @@ -39,13 +39,13 @@ following configuration options: - Connect to the server – Use the default domain controller entered in the box, or enter an alternate server -- Naming context – Select a directory partition from the drop-down list: **Default Context**, +- Naming context – Select a directory partition from the dropdown list: **Default Context**, **Configuration Context**, or **Schema Context** -- Connect – Connects to the domain specified. The root folder of the domain is displayed in the left - pane of the window. +- Connect – Connects to the domain specified. The left pane of the window displays the root folder of + the domain. :::note - Before clicking **Connect**, the server port must be configured. To configure the + Before clicking **Connect**, configure the server port. To configure the server port, click **Options** to open the Options window and configure the server port as described in the Options Window section. ::: @@ -55,8 +55,7 @@ following configuration options: options. See the [Options Window](#options-window) topic for additional information. - List of attributes – Table in the upper right corner lists attributes for the object selected in the left pane -- Root path – The Root path textbox is populated with the path to the highlighted attributes to be - collected +- Root path – The Root path textbox shows the path to the highlighted attributes to collect - LDAP filter – The LDAP filter textbox shows the filters applied to the objects. Click the ellipses (**…**) to open the Filter Options window. See the [Filter Options Window](#filter-options-window) topic for additional information. @@ -78,7 +77,7 @@ The Options window contains configure connection options and multi-value results - Server Port - If the Connect Securely with TLS/SSL option is selected, use Server Port `686` - - If the Connect Securely with TLS/SSL option is not selected, use Server Port `389` + - If the Connect Securely with TLS/SSL option isn't selected, use Server Port `389` - Authentication Type @@ -86,17 +85,17 @@ The Options window contains configure connection options and multi-value results - Simple - TreeView Node Limit – Typically set to 500 -- Multi-valued attributes – Indicates how multi-valued properties are returned +- Multi-valued attributes – Indicates how the query returns multi-valued properties - - Concatenated – All values are listed in one cell using the delimiter specified + - Concatenated – Lists all values in one cell using the delimiter specified - Delimiter – Symbol used to separate values in the cell - - First Value Only – Only the first value is listed in the cell + - First Value Only – Lists only the first value in the cell ### Filter Options Window -The Filter Options window is where to add filters to the query. Click the ellipses (**…**) button +Use the Filter Options window to add filters to the query. Click the ellipses (**…**) button located to the right of the **LDAP filter** box in the LDAP template form to open this window. ![filteroptions](/images/accessanalyzer/11.6/admin/datacollector/filteroptions.webp) @@ -120,7 +119,7 @@ The Custom Filter window provides options for creating a complex filter. ![Custom Filter window](/images/accessanalyzer/11.6/admin/datacollector/customfilter.webp) -Select a **Field** and **Condition** from the drop-down lists. Enter a **Value** for the condition. +Select a **Field** and **Condition** from the dropdown lists. Enter a **Value** for the condition. Click **Add** to add the filter to the Filter Lines table. - Filter Lines will be combined with a logical – Select the **AND** or **OR** option. **AND** is diff --git a/docs/accessanalyzer/11.6/admin/datacollector/nis/category.md b/docs/accessanalyzer/11.6/admin/datacollector/nis/category.md index 284e141783..70a0e9b257 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/nis/category.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/nis/category.md @@ -6,7 +6,7 @@ sidebar_position: 30 # NIS: Category -The Category page is used to identify which type of NIS information to retrieve. +Use the Category page to identify which type of NIS information to retrieve. ![NIS Data Collector Wizard Category page](/images/accessanalyzer/11.6/admin/datacollector/nis/category.webp) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/nis/configurejob.md b/docs/accessanalyzer/11.6/admin/datacollector/nis/configurejob.md index 2a71af83f3..82c7b3fafc 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/nis/configurejob.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/nis/configurejob.md @@ -6,13 +6,13 @@ sidebar_position: 20 # Unix Connection Profile & Host List -The NIS Data Collector requires a custom Connection Profile and host list be created and assigned to -the job or job group conducting the data collection. The host inventory option during host list -creation makes it necessary to configure the Connection Profile first. +The NIS Data Collector requires you to create a custom Connection Profile and host list and assign +them to the job or job group that collects the data. The host inventory option during host list +creation requires you to configure the Connection Profile first. ## Connection Profile -Creating the Connection Profile requires having an account with access to the targeted NIS server. +To create the Connection Profile, you need an account with access to the targeted NIS server. Create a Connection Profile and set the following information on the User Credentials window: @@ -25,12 +25,12 @@ Create a Connection Profile and set the following information on the User Creden - Password/Confirm - If not using a private key, enter the **Password** and re-type in the **Confirm** field - - If using a private key, then the password is not needed. Provide the private key information + - If you use a private key, you don't need the password. Provide the private key information in the **Use the following private key when connecting** field. - Use the following port/ports(CSV) for SSH - - The SSH port needs to be opened in software and hardware firewalls + - You must open the SSH port in software and hardware firewalls - If desired, select this option and provide the port value - Use the following private key when connecting @@ -43,7 +43,7 @@ Create a Connection Profile and set the following information on the User Creden - If desired, select this option and provide the key value -Once the Connection Profile is created, it is time to create the custom host list. See the +After you create the Connection Profile, create the custom host list. See the [Connection](/docs/accessanalyzer/11.6/admin/settings/connection/overview.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/nis/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/nis/overview.md index 27844ef590..4b5857a318 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/nis/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/nis/overview.md @@ -7,7 +7,7 @@ sidebar_position: 260 # NIS Data Collector The NIS Data Collector inventories a NIS domain for user and group information, mapping to -Windows-style SIDs. This data collector is a core component of Enterprise Auditor and has been +Windows-style SIDs. This data collector is a core component of Enterprise Auditor and comes preconfigured within the .NIS Inventory Solution. Both this data collector and the solution are available with all Enterprise Auditor license options. See the [.NIS Inventory Solution](/docs/accessanalyzer/11.6/solutions/nisinventory/overview.md) @@ -41,5 +41,5 @@ following wizard pages: ![NIS Data Collector Wizard Welcome page](/images/accessanalyzer/11.6/admin/datacollector/nis/welcome.webp) -The Welcome page can be hidden by selecting the **Do not display this page the next time** checkbox -when the wizard is open and configuration settings are saved. +To hide the Welcome page, select the **Don't display this page the next time** checkbox while the +wizard is open, then save the configuration settings. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/nis/query.md b/docs/accessanalyzer/11.6/admin/datacollector/nis/query.md index 87928a3937..22a23f2e1e 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/nis/query.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/nis/query.md @@ -6,7 +6,7 @@ sidebar_position: 60 # NIS: NIS Query -The NIS Query page is where the NIS query regular expressions are configured and tested. It is a +Use the NIS Query page to configure and test NIS query regular expressions. It is a wizard page for the category of: - Custom NIS Scan @@ -18,7 +18,7 @@ The Data Source configuration options are: - NIS Map – Specify the name of the NIS map to query - Load Data – Fetches the first 50 rows of data of the specified NIS map from the test host - Paste Data – Uses text from the clipboard as the test data source -- Open File – Allows using a text file as test data. The test data is shown in the preview box. +- Open File – Allows using a text file as test data. The preview box shows the test data. The Query Expressions configuration options are: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/nis/results.md b/docs/accessanalyzer/11.6/admin/datacollector/nis/results.md index f25b5cd003..05440d0913 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/nis/results.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/nis/results.md @@ -6,15 +6,15 @@ sidebar_position: 70 # NIS: Results -The Results page is where properties from Unix to be gathered are selected. It is a wizard page for +Use the Results page to select properties from Unix to gather. It is a wizard page for both categories. ![NIS Data Collector Wizard Results page](/images/accessanalyzer/11.6/admin/datacollector/nis/results.webp) -Available properties have checkboxes that can be selected individually, or you can use the **Select -All**, **Clear All**, and **Reset to defaults** buttons. All selected properties are gathered. -Available properties vary based on the category selected. +Select available properties individually using their checkboxes, or use the **Select +All**, **Clear All**, and **Reset to defaults** buttons. The data collector gathers all selected +properties. Available properties vary based on the category selected. -This information is not available within the standard reference tables and views. Instead, this -information can be viewed in the `SA_[Job Name]_DEFAULT` table, which is created when any of these -properties are selected. +This information isn't available within the standard reference tables and views. Instead, you can +view this information in the `SA_[Job Name]_DEFAULT` table, which the data collector creates when +you select any of these properties. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/nis/settings.md b/docs/accessanalyzer/11.6/admin/datacollector/nis/settings.md index 9700073687..e47b43cc8a 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/nis/settings.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/nis/settings.md @@ -6,7 +6,7 @@ sidebar_position: 40 # NIS: NIS Settings -The NIS Settings page is where the NIS domain and a NIS server are configured for testing. It is a +Use the NIS Settings page to configure the NIS domain and a NIS server for testing. It is a wizard page for both categories. ![NIS Data Collector Wizard NIS Settings page](/images/accessanalyzer/11.6/admin/datacollector/nis/settings.webp) @@ -15,7 +15,7 @@ Configure the NIS domain and sample NIS server: - NIS Domain Name – Enter the case-sensitive name of the NIS domain to scan. This is the value returned by `/bin/domainname` on UNIX systems. -- (Optional) Sample NIS Server – Enter the host name or IP address of a NIS server for the above +- (Optional) Sample NIS Server – Enter the host name or IP address of a NIS server for this domain to use for testing. This system should be running the `ypserv` process and be accessible from the Enterprise Auditor Console. Then, click **Test**. - Test – The data collector attempts to connect to the specified server and access information from diff --git a/docs/accessanalyzer/11.6/admin/datacollector/nis/sidmappings.md b/docs/accessanalyzer/11.6/admin/datacollector/nis/sidmappings.md index 544dfe423f..6b3fc95d38 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/nis/sidmappings.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/nis/sidmappings.md @@ -6,13 +6,14 @@ sidebar_position: 50 # NIS: SID Mappings -The SID Mappings page is where the Windows-style SID mappings for the Unix User ID and Group ID are -specified. It is a wizard page for the category of: +Use the SID Mappings page to specify the Windows-style SID mappings for the Unix User ID and Group +ID. It is a wizard page for the category of: - Scan NIS User and Groups ![NIS Data Collector Wizard SID Mappings page](/images/accessanalyzer/11.6/admin/datacollector/nis/sidmappings.webp) The default settings work for most environments. Use this page to **Add**, **Edit**, or **Remove** -ID Mappings. Multiple entries are allowed. For each range of User ID or Group ID entered, the offset -is added to the ID and the resulting SID is the format with `%d` replaced by the ID. +ID Mappings. You can add multiple entries. For each range of User ID or Group ID you enter, the +wizard adds the offset to the ID, and the resulting SID uses the format with `%d` replaced by the +ID. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/nis/standardtables.md b/docs/accessanalyzer/11.6/admin/datacollector/nis/standardtables.md index 33032c1e2b..b24eeea0df 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/nis/standardtables.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/nis/standardtables.md @@ -10,7 +10,7 @@ The NIS Data Collector gathers essential user and group inventory information in reference tables. Unlike other Enterprise Auditor data collectors, the NIS Data Collector writes data to these tables regardless of the job executing the query. -These tables and their associated views are outlined below: +The following table outlines these tables and their associated views: | Table | Details | | ------------------- | -------------------------------------------------------------------------------------- | @@ -18,10 +18,9 @@ These tables and their associated views are outlined below: | SA_NIS_Groups | Contains extended information about groups, mail enabled, security enabled, and so on. | | SA_NIS_Users | Contains extended information about users, department, title, and so on | -Views are the recommended way for Enterprise Auditor users to obtain the information gathered by the -NIS Data Collector. They contain additional information for building queries easily. The following -is an explanation of the corresponding view created for some of the tables generated by the NIS Data -Collector: +Views are the recommended way for Enterprise Auditor users to obtain the information the NIS Data +Collector gathers. They contain additional information useful for building queries. The following +explains the corresponding view for some of the tables the NIS Data Collector generates: | Views | Details | | ----------------------- | ------------------------------------- | diff --git a/docs/accessanalyzer/11.6/admin/datacollector/nis/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/nis/summary.md index f68bcaf7a9..89ef6cef84 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/nis/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/nis/summary.md @@ -6,11 +6,10 @@ sidebar_position: 80 # NIS: Summary -The Summary page is where configuration settings are summarized. It is a wizard page for both +Use the Summary page to review a summary of the configuration settings. It is a wizard page for both categories. ![NIS Data Collector Wizard Summary page](/images/accessanalyzer/11.6/admin/datacollector/nis/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the NIS Data Collector Wizard to ensure that no accidental clicks are -saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** +instead to close the NIS Data Collector Wizard without saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/nosql/category.md b/docs/accessanalyzer/11.6/admin/datacollector/nosql/category.md index 73640bd34c..2e1f650903 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/nosql/category.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/nosql/category.md @@ -17,8 +17,8 @@ The query categories are: - Sensitive Data Collection – Scan databases for sensitive data - - The Sensitive Data category options require the Sensitive Data Discovery Add-on to be - installed on the Enterprise Auditor Console before the NoSQL Data Collector can collect + - The Sensitive Data category options require you to install the Sensitive Data Discovery + Add-on on the Enterprise Auditor Console before the NoSQL Data Collector can collect sensitive data. See the [Sensitive Data Discovery Add-On Installation](/docs/accessanalyzer/11.6/install/sensitivedatadiscovery/overview.md) topic for additional information. @@ -37,5 +37,5 @@ The query categories are: - NoSQL Utilities - - Remove NoSQL Storage Tables — All connection related and filter data will be removed for + - Remove NoSQL Storage Tables — Removes all connection-related and filter data for NoSQL databases diff --git a/docs/accessanalyzer/11.6/admin/datacollector/nosql/configurejob.md b/docs/accessanalyzer/11.6/admin/datacollector/nosql/configurejob.md index 4ac697d676..20d21900ea 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/nosql/configurejob.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/nosql/configurejob.md @@ -19,9 +19,9 @@ window. For an Active Directory account, set the following on the User Credentials window: - Select Account Type – Active Directory Account -- Domain – Drop-down menu with available trusted domains will appear. Either type the short domain +- Domain – dropdown menu with available trusted domains will appear. Either enter the short domain name in the textbox or select a domain from the menu. -- User name – Type the user name +- User name – Enter the user name - Password Storage – Choose the option for credential password storage: - Application – Uses the configured Profile Security setting as selected at the **Settings** > @@ -30,11 +30,11 @@ For an Active Directory account, set the following on the User Credentials windo topic for additional information. - CyberArk – Uses the CyberArk Enterprise Password Vault. See the [CyberArk Integration](/docs/accessanalyzer/11.6/admin/settings/connection/cyberarkintegration.md) - topic for additional information. The password fields do not apply for CyberArk password + topic for additional information. The password fields don't apply for CyberArk password storage. -- Password – Type the password -- Confirm – Re-type the password +- Password – Enter the password +- Confirm – Re-enter the password **SQL** @@ -46,8 +46,8 @@ For a SQL account, set the following on the User Credentials window: **Settings** > **Application** node. See the [Application](/docs/accessanalyzer/11.6/admin/settings/application/overview.md) topic for additional information.) -- Password – Type the password -- Confirm – Re-type the password +- Password – Enter the password +- Confirm – Re-enter the password See the [Connection](/docs/accessanalyzer/11.6/admin/settings/connection/overview.md) @@ -58,13 +58,13 @@ topics for additional information. ## Host List Jobs using the NoSQL Data Collector must create a host list with the servers containing the target -databases. Setup the list of MongoDB hosts that needs to be monitored. Be sure to use a specific +databases. Set up the list of MongoDB hosts to monitor. Be sure to use a specific host name (if forcing the connection to a secondary host) or just the cluster name if connecting to the cluster. See the [Host Management](/docs/accessanalyzer/11.6/admin/hostmanagement/overview.md) topic for additional information. -Additionally, the database clusters / instances must be added to the Filter page in the query +Additionally, add the database clusters/instances to the Filter page in the query configuration. See the [NoSQL: Filter](/docs/accessanalyzer/11.6/admin/datacollector/nosql/filter.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/nosql/criteria.md b/docs/accessanalyzer/11.6/admin/datacollector/nosql/criteria.md index 86d3ef3ecc..c2f09d2210 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/nosql/criteria.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/nosql/criteria.md @@ -6,10 +6,10 @@ sidebar_position: 40 # NoSQL: Criteria -The Criteria page is where the criteria to be used for discovering sensitive data is configured. It +Use the Criteria page to configure the criteria for discovering sensitive data. It is a wizard page for the category of Sensitive Data Collection. -This page requires the Sensitive Data Discovery Add-On to be installed on the Enterprise Auditor +This page requires you to install the Sensitive Data Discovery Add-On on the Enterprise Auditor Console to define the criteria and enable the Criteria Editor. See the [Sensitive Data Discovery Add-On Installation](/docs/accessanalyzer/11.6/install/sensitivedatadiscovery/overview.md) topic for additional information. @@ -27,13 +27,13 @@ The options on the Criteria page are: - Select All – Click **Select All** to enable all sensitive data criteria for scanning - Clear All – Click **Clear All** to remove all selections from the table - - Select the checkboxes next to the sensitive data criteria options to enable it to be scanned - for during job execution + - Select the checkboxes next to the sensitive data criteria options to include them in the scan + during job execution The table contains the following types of criteria: :::note -Until the Sensitive Data Discovery Add-On is installed, only the headers for the System +Until you install the Sensitive Data Discovery Add-On, only the headers for the System Criteria and User Criteria nodes are visible in the table. ::: @@ -48,7 +48,7 @@ Criteria and User Criteria nodes are visible in the table. :::note Adding unnecessary criteria can adversely impact the scanner performance and can cause the -scanning job to take a long time. If performance is adversely affected, revisit the sensitive data -scanning criteria and remove criteria that is not required. +scanning job to take a long time. If performance suffers, revisit the sensitive data +scanning criteria and remove criteria that isn't required. ::: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/nosql/filter.md b/docs/accessanalyzer/11.6/admin/datacollector/nosql/filter.md index 2daebc20ee..68cdc0626f 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/nosql/filter.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/nosql/filter.md @@ -6,10 +6,10 @@ sidebar_position: 50 # NoSQL: Filter -The Filter page is where the query can be scoped to target specific databases or instances. It is a +Use the Filter page to scope the query to target specific databases or instances. It is a wizard page for the Sensitive Data Collection category. -It is necessary to populate the available Mongo databases/instances before the query can be scoped. +Populate the available Mongo databases/instances before scoping the query. See the [Manage Connections Window](#manage-connections-window) topic for additional information. ![NoSQL Data Collector Wizard Filter page](/images/accessanalyzer/11.6/admin/datacollector/nosql/filter.webp) @@ -33,24 +33,24 @@ The configurable filter options are: - Exclude — Excludes selected databases/instances and displays them in red - Include — Reverts an exclusion. By default, all sub tables are included. - - Build Pattern — Opens the Build Pattern dialogue to build a custom filter to be applied to the + - Build Pattern — Opens the Build Pattern dialogue to build a custom filter to apply to the selected database objects. See the [Build or Edit Pattern](#build-or-edit-pattern) topic for additional information. -- Selections — Displays selected database objects for which the query has been scoped. Right click +- Selections — Displays selected database objects the query is scoped to. Right click to open context menu: - - Remove Pattern — Selected database/instance will be removed from the query + - Remove Pattern — Removes the selected database/instance from the query - Edit Pattern — Opens the Edit Pattern dialogue with the following options (See the [Build or Edit Pattern](#build-or-edit-pattern) topic for additional information): - Exclude — Excludes selected databases/instances and displays them in red - Include — Reverts an exclusion. By default, all sub tables are included. - - Pattern — Build a custom filter to be applied to the selected database objects + - Pattern — Build a custom filter to apply to the selected database objects ## Manage Connections Window -The Manage Connections window enables users to add MongoDB database instances to search for +Use the Manage Connections window to add MongoDB database instances to search for sensitive data. Click **Connections** to open the window. ![Manage Connections window](/images/accessanalyzer/11.6/admin/datacollector/nosql/manageconnections.webp) @@ -64,8 +64,8 @@ additional information on how to connect to a MongoDB database, see the MongoDB - Is Active — Select the checkbox to include the database on the Servers Pane on the Filter page - Server Label — The name of the server - Host — Name or IP address of the host where the database is located -- Port Number — Port number for the database. The default port is 27017. If a non-default port is - being used, it should be specified in the Port Number section. +- Port Number — Port number for the database. The default port is 27017. If you use a non-default + port, specify it in the Port Number section. - Auth Database — The database used for authorization. Typically it is the **admin** database. - Read Preference — Read preference describes how MongoDB clients route read operations to the members of a replica set by default, an application directs its read operations to the primary @@ -80,7 +80,7 @@ In the Manage Connections table, the following information is also listed: information has been validated. **N** indicates the information has not been validated. - Last Inspected — Indicates the date and time of when the connection information was last inspected. If blank, the connection information has not yet been validated. -- Enable Impersonation – Impersonation does not apply to MongoDB and this column will be blank. +- Enable Impersonation – Impersonation doesn't apply to MongoDB and this column will be blank. The Manage Connections window has the following buttons: @@ -92,7 +92,7 @@ The Manage Connections window has the following buttons: #### Build or Edit Pattern -The Build / Edit Pattern window enables users to apply a custom scoping filter to the query. +Use the Build / Edit Pattern window to apply a custom scoping filter to the query. ![Edit Existing Pattern window](/images/accessanalyzer/11.6/admin/datacollector/nosql/editpattern.webp) @@ -104,7 +104,7 @@ The Build / Edit Pattern window has the following features: - Pattern — Build a custom filter to be applied to the selected database objects :::note - Color-coding indicating Excluded and Included objects does not display until after a - selection is validated using the **Validate Selections** button on the Filter page. + Color-coding indicating Excluded and Included objects doesn't display until after you validate + a selection using the **Validate Selections** button on the Filter page. ::: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/nosql/options.md b/docs/accessanalyzer/11.6/admin/datacollector/nosql/options.md index 9d959bfb70..e0c0f0671f 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/nosql/options.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/nosql/options.md @@ -21,13 +21,13 @@ The sensitive data scan settings are: database or cluster - Limit of documents to scan — Scan limited number of documents in each database or cluster. This option is ideal when discovering sensitive data and has minimal impact on the MongoDB - cluster performance. However, if the Subject Profile Request feature is being leveraged, then - all the documents in all the database or cluster need to be scanned. + cluster performance. However, if you use the Subject Profile Request feature, you need to + scan all the documents in all the databases or clusters. - Scan documents randomly — Enterprise Auditor requests a set of documents from each database - when scanning for sensitive data. The database engine does not return random data from a - collection. Instead, Enterprise Auditor returns sequential documents in a collection. In order - to ensure a statistical discrete uniform distribution of data being scanned, this option can - be selected. When selected, the Enterprise Auditor sensitive data scanner requests randomized + when scanning for sensitive data. The database engine doesn't return random data from a + collection. Instead, Enterprise Auditor returns sequential documents in a collection. To + ensure a statistical discrete uniform distribution of scanned data, select this option. + When you select this option, the Enterprise Auditor sensitive data scanner requests randomized documents from each collection in all the targeted databases. - Scan database names for sensitive data – Scans database names for sensitive data if the database @@ -39,11 +39,11 @@ The sensitive data scan settings are: **DLP Options** - Store discovered sensitive data – Stores potentially sensitive data in the Enterprise Auditor - database. Any sampled sensitive data discovered based on the matched criteria is stored in the - Enterprise Auditor database. This functionality can be disabled by clearing this checkbox. + database. The scan stores any sampled sensitive data discovered based on the matched criteria in + the Enterprise Auditor database. Clear this checkbox to disable this functionality. :::note - The **Store discovered sensitive data** option is required to view Content Audit + You must select the **Store discovered sensitive data** option to view Content Audit reports in the Access Information Center for MongoDB data. ::: @@ -58,6 +58,6 @@ The sensitive data scan settings are: scan was stopped as a result of an error :::tip -Remember, the Sensitive Data Discovery Add-on is required to use the sensitive data collection +Remember, you need the Sensitive Data Discovery Add-on to use the sensitive data collection option. ::: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/nosql/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/nosql/overview.md index 39c9098e38..cc06496747 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/nosql/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/nosql/overview.md @@ -10,7 +10,7 @@ The NoSQL Data Collector for MongoDB provides information on MongoDB Cluster con user permissions, scans collections for sensitive data, and identifies who has access to sensitive data. It also supports the execution of custom queries against all targeted MongoDB cluster nodes. -The NoSQL Data Collector has been preconfigured within the MongoDB Solution. Both this data +The NoSQL Data Collector comes preconfigured within the MongoDB Solution. Both this data collector and the solution are available with a special Enterprise Auditor license. See the [MongoDB Solution](/docs/accessanalyzer/11.6/solutions/databases/mongodb/overview.md) topic for additional information. @@ -41,11 +41,11 @@ topic for additional information. **Sensitive Data Discovery Considerations** -The Sensitive Data Discovery Add-On must be installed on the Enterprise Auditor Console server, -which enables Sensitive Data criteria for scans. If running Sensitive Data Discovery (SDD) scans, it -will be necessary to increase the minimum amount of RAM. Each thread requires a minimum of 2 -additional GB of RAM per host. For example, if the job is configured to scan 8 hosts at a time , -then an extra 16 GB of RAM are required (8x2=16). +You must install the Sensitive Data Discovery Add-On on the Enterprise Auditor Console server to +enable Sensitive Data criteria for scans. If you run Sensitive Data Discovery (SDD) scans, increase +the minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For +example, if you configure the job to scan 8 hosts at a time, you need an extra 16 GB of RAM +(8 x 2 = 16). ## NoSQL Query Configuration diff --git a/docs/accessanalyzer/11.6/admin/datacollector/nosql/results.md b/docs/accessanalyzer/11.6/admin/datacollector/nosql/results.md index 459d023f2a..b606ce4c52 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/nosql/results.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/nosql/results.md @@ -6,11 +6,11 @@ sidebar_position: 60 # NoSQL: Results -The Results page is where the properties that will be gathered are selected. It is a wizard page for +Use the Results page to select the properties to gather. It is a wizard page for all of the categories. ![NoSQL Data Collector Wizard Results page](/images/accessanalyzer/11.6/admin/datacollector/nosql/results.webp) -Properties can be selected individually, or the **Select All**, **Clear All**, and **Reset to -Defaults** buttons can be used. All selected properties are gathered. Available properties vary +Select properties individually, or use the **Select All**, **Clear All**, and **Reset to +Defaults** buttons. The data collector gathers all selected properties. Available properties vary based on the category selected. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/nosql/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/nosql/summary.md index a3f9259991..9be82750a2 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/nosql/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/nosql/summary.md @@ -6,11 +6,10 @@ sidebar_position: 70 # NoSQL: Summary -The Summary page is where the configuration settings are summarized. It is a wizard page for all of -the categories. +Use the Summary page to review a summary of the configuration settings. It is a wizard page for all +of the categories. ![NoSQL Data Collector Wizard Summary page](/images/accessanalyzer/11.6/admin/datacollector/nosql/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the NoSQL Data Collector Wizard ensuring that no accidental clicks are -saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** +instead to close the NoSQL Data Collector Wizard without saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/overview.md index 250e27f19c..d0986e7eaa 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/overview.md @@ -13,7 +13,7 @@ for additional information on job configuration. ## Query Selection The Enterprise Auditor data collectors can collect information from a wide range of environments. -Data collection tasks are assigned to jobs at the **Configure** > **Queries** node level. See the +You assign data collection tasks to jobs at the **Configure** > **Queries** node level. See the [Queries Node](/docs/accessanalyzer/11.6/admin/jobs/job/configure/queries.md) topic for additional information. @@ -27,7 +27,7 @@ following options: - Rename Table – Rename the current table selected - Delete Table – Delete the current table selected -The Queries section is where the Data Collectors are configured. The Queries section has the +Use the Queries section to configure the Data Collectors. The Queries section has the following options: - Add from Library – Opens the Libraries window. Add a pre-built query from the Enterprise Auditor @@ -35,25 +35,25 @@ following options: information. - Create Query – Click **Create Query** to add a new query task to a job. See the [Create or Modify a Query](#create-or-modify-a-query) topic for additional information. -- Delete Query – Delete the currently selected query +- Delete Query – Delete the selected query - Query Properties – Select an existing query and click **Query Properties** to modify its configuration ### Add Query from Library -Pre-built queries can be added to the Data Collector job through the Libraries window. +You can add pre-built queries to the Data Collector job through the Libraries window. ![Libraries window](/images/accessanalyzer/11.6/admin/datacollector/addqueryfromlibrary.webp) The Libraries window toolbar has the following options: -- Create New Library – Create a new library entry. The new Library will be added to the Library +- Create New Library – Create a new library entry. The new Library appears in the Library dropdown menu. -- Delete Library – Deletes the currently selected library +- Delete Library – Deletes the selected library - Cut – Cut the selected task in the library to the clipboard - Copy – Copy the selected task in the library to the clipboard -- Paste – Paste cut or copied item from the clipboard into the currently selected library -- Delete Selected Task – Deletes the currently selected task +- Paste – Paste cut or copied item from the clipboard into the selected library +- Delete Selected Task – Deletes the selected task Click **Add** to confirm the query selection and add it to the Queries list on the Query Selection page. If no selection is needed or intended, click **Cancel** to close the Libraries window without @@ -62,8 +62,8 @@ adding a pre-built query into the Queries list. ### Create or Modify a Query To open the Query Properties window, click **Create Query** for a new query or **Query Properties** -for an existing query. There are three tabs in the Query Properties window where queries can be -configured. These tabs are:. +for an existing query. The Query Properties window has three tabs where you can configure queries. +These tabs are: - [General Tab](#general-tab) - [Data Source Tab](#data-source-tab) @@ -88,10 +88,10 @@ The General tab displays: - Within the SQL database, the table name will be prefaced with `SA_[Job Name]_` - ID – Query GUID generated by Enterprise Auditor for this query task. - - The query GUID is referenced by the **SMARTLog** Data Collector, **ExchangeMetrics** Data - Collector, and the **PowerShell** Data Collector. - - When using the **SMARTLog** Data Collector or the **ExchangeMetrics** Data Collector, the - `state` file for the query’s Persist log state feature can be found in the SA_CommonData + - The **SMARTLog** Data Collector, **ExchangeMetrics** Data Collector, and **PowerShell** Data + Collector all reference the query GUID. + - When using the **SMARTLog** Data Collector or the **ExchangeMetrics** Data Collector, you can + find the `state` file for the query’s Persist log state feature in the SA_CommonData folder in the Enterprise Auditor installation directory: …/STEALTHbits/StealthAUDIT/Jobs/SA_CommonData/[Data Collector]/[Query GUID]/[Target @@ -112,15 +112,15 @@ Use the Data Source tab to configure the data collector and query. The Data Source tab displays: -- Data Collector – Data collector selected from the drop-down menu. +- Data Collector – Data collector selected from the dropdown menu. - Query – Query configuration string. - Configure – Opens the wizard for the selected data collector. Each Data Collector task has its own Configuration Wizard. - Properties – Configured query properties. -When creating a new query, expand the **Data Collector** drop-down menu, which provides a list of -all licensed data collectors in alphabetical order. The **Query** and **Property** sections are -auto-filled according to the configuration. The buttons at the bottom of the Property section are +When creating a new query, expand the **Data Collector** dropdown menu, which provides a list of +all licensed data collectors in alphabetical order. The wizard auto-fills the **Query** and +**Property** sections according to the configuration. The buttons at the bottom of the Property section are for advanced features to manipulate the query. The **+** and **–** buttons manually add or remove individual properties from the query. The script button opens the VBScript Editor window for query manipulation scripts. @@ -147,15 +147,15 @@ The Filter tab has the following items: - Use the **+** and **–** buttons to add and remove filters from the query - Key – Labels identifying the configurable value in the filter - Value – When applicable, add a new value to the filter using the dropdown menu. Otherwise, create - a new one by typing in the desired value. + a new one by typing in the value you want. :::info -Use the default settings for filters. Filters can be used to substitute or delete +Use the default settings for filters. Use filters to substitute or delete data values during data collection. For more information on the impacts of adding filters to queries, contact [Netwrix Support](https://www.netwrix.com/support.html). ::: -Click **OK** to save changes and exist the Query Properties window. If no changes were made or -intended, it is best practice to click **Cancel** to exit the Query Properties window to ensure -unintended changes are not saved. +Click **OK** to save changes and exist the Query Properties window. If you didn't make or intend any +changes, click **Cancel** instead to exit the Query Properties window without saving unintended +changes. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/passwordsecurity/dictionaries.md b/docs/accessanalyzer/11.6/admin/datacollector/passwordsecurity/dictionaries.md index da136413ab..e1f4551dc1 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/passwordsecurity/dictionaries.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/passwordsecurity/dictionaries.md @@ -6,7 +6,7 @@ sidebar_position: 30 # PasswordSecurity: Dictionaries -The Dictionaries page provides configuration settings for storing passwords to be used as a +The Dictionaries page provides configuration settings for storing passwords to use as a reference for the scan. ![Password Security Data Collection Wizard Dictionary options page](/images/accessanalyzer/11.6/admin/datacollector/passwordsecurity/dictionaries.webp) @@ -14,20 +14,20 @@ reference for the scan. The configurable dictionary options are: - Use Stealthbits dictionary (> 100,000 passwords) – If enabled, compares passwords against - out-of-the-box dictionary comprised of commonly used password hashes + built-in dictionary comprised of commonly used password hashes - Automatically update the Stealthbits dictionary – Checks for the latest version of the Stealthbits dictionary file when the job is executed, and downloads the latest version from the [Netwrix website](https://www.netwrix.com/) - - If the Enterprise Auditor server does not have an internet connection, the Stealthbits - dictionary can be downloaded directly from the + - If the Enterprise Auditor server doesn't have an internet connection, you can download the + Stealthbits dictionary directly from the [My Products](https://www.netwrix.com/my_products.html) page of the Netwrix website. - Update Dictionary – Checks for the latest version of the dictionary file, and updates if necessary - Add – Add a custom dictionary file in one of the following formats: - Plaintext – Line separated in a text file - - NLTM Hashes – Can be added with hashes or sorted hashes. The haveibeenpwned dictionary can be + - NLTM Hashes – You can add these as hashes or sorted hashes. The haveibeenpwned dictionary can be used. See the [Download and Configure the Have I Been Pwnd (HIBP) Hash List](#download-and-configure-the-have-i-been-pwnd-hibp-hash-list) topic for additional information. @@ -41,8 +41,8 @@ The configurable dictionary options are: ## Download the Stealthbits dictionary -**Step 1 –** If the Enterprise Auditor server does not have an internet connection, the Stealthbits -dictionary can be downloaded directly from the +**Step 1 –** If the Enterprise Auditor server doesn't have an internet connection, you can download +the Stealthbits dictionary directly from the [My Products](https://www.netwrix.com/my_products.html) page of the Netwrix website. **Step 2 –** After downloading the dictionary file manually do one the following: @@ -74,8 +74,8 @@ get the latest breached hashes from the Have I Been Pwnd (HIBP) database. :::note The -[](https://github.com/HaveIBeenPwned/PwnedPasswordsDownloader)[Pwnd Passwords Downloader](https://github.com/HaveIBeenPwned/PwnedPasswordsDownloader) -is a third party, open source tool, created by the HaveIBeenPwned team and distributed under a BSD +[Pwnd Passwords Downloader](https://github.com/HaveIBeenPwned/PwnedPasswordsDownloader) +is a third-party, open source tool that the HaveIBeenPwned team created and distributes under a BSD 3-Clause License. You might experience issues during the hash download process, depending on your threading settings or the load on the CloudFlare backend. The Pwnd Passwords Downloader tool will automatically retry to continue downloading the hashes until it fully completes the download @@ -92,14 +92,14 @@ The Pwnd Passwords Downloader has the following prerequisite: can download .NET 6 from Microsoft: [https://dotnet.microsoft.com/en-us/download/dotnet/6.0](https://dotnet.microsoft.com/en-us/download/dotnet/6.0) -The HIBP database takes up additional space on the machine where it is copied (approximately 13 GB, -but subject to change). The Have I Been Pwnd database (HIBP) hashes can take up to 30 GB. Make sure +The HIBP database takes up additional space on the machine where you copy it (approximately 13 GB, +but subject to change). The Have I Been Pwnd database (HIBP) hashes can take up to 30 GB. ensure that you have enough free space on your disk in your Netwrix Enterprise Auditor install directory (`%sainstalldir%`). ### Install the Pwnd Passwords Downloader -Follow the steps to install the Pwnd Passwords Downloader. +To install the Pwnd Passwords Downloader: **Step 3 –** Open command prompt, and navigate to your .NET install folder (for example, `C:\Program Files (x86)\dotnet`). @@ -116,7 +116,7 @@ dotnet tool install --global haveibeenpwned-downloader ### Update an Installed Pwnd Passwords Downloader -Follow the steps to update an installed Pwnd Passwords Downloader. +To update an installed Pwnd Passwords Downloader: **Step 1 –** Open the command prompt. @@ -130,7 +130,7 @@ dotnet tool update --global haveibeenpwned-downloader ### Download NTML Hashes with the Pwnd Passwords Downloader -Follow the steps to download NTLM hashes. +To download NTLM hashes: **Step 1 –** Navigate to the folder where you want to download the hashes. @@ -153,5 +153,5 @@ This screenshot shows the completed download. haveibeenpwned-downloader.exe -n pwnedpasswords_ntlm -o ``` -For a complete list of available parameters, please check the +For a complete list of available parameters, check the [Pwnd Passwords Downloader GitHub page](https://github.com/HaveIBeenPwned/PwnedPasswordsDownloader). diff --git a/docs/accessanalyzer/11.6/admin/datacollector/passwordsecurity/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/passwordsecurity/overview.md index 8d7df8fef7..06bfa6cbe2 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/passwordsecurity/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/passwordsecurity/overview.md @@ -10,8 +10,8 @@ The PasswordSecurity Data Collector compares passwords stored in Active Director passwords in the Netwrix dictionary or custom dictionaries. The PasswordSecurity Data Collector also checks for common misconfigurations with passwords in Active Directory. -The PasswordSecurity Data Collector is a core component of Enterprise Auditor, but it has been -preconfigured within the Active Directory Solution. While the data collector is available with all +The PasswordSecurity Data Collector is a core component of Enterprise Auditor, and the Active +Directory Solution includes it as a preconfigured component. While the data collector is available with all Enterprise Auditor license options, the Active Directory Solution is only available with a special Enterprise Auditor license. See the [Active Directory Solution](/docs/accessanalyzer/11.6/solutions/activedirectory/overview.md) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/passwordsecurity/results.md b/docs/accessanalyzer/11.6/admin/datacollector/passwordsecurity/results.md index 4de0c8602b..7daf1f4c9c 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/passwordsecurity/results.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/passwordsecurity/results.md @@ -6,9 +6,9 @@ sidebar_position: 40 # PasswordSecurity: Results -The Results page is where Active Directory properties to be gathered are selected. +Use the Results page to select the Active Directory properties to gather. ![Password Security Data Collection Wizard Results page](/images/accessanalyzer/11.6/admin/datacollector/passwordsecurity/results.webp) -Properties can be selected individually or by using the **Select All** or **Clear All** buttons. All -selected properties are gathered. +Select properties individually, or use the **Select All** or **Clear All** buttons. Enterprise +Auditor gathers all selected properties. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/passwordsecurity/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/passwordsecurity/summary.md index 6543cc95ba..1347c374aa 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/passwordsecurity/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/passwordsecurity/summary.md @@ -10,6 +10,6 @@ The Summary page displays a summary of the configured query. ![Password Security Data Collection Wizard Summary page](/images/accessanalyzer/11.6/admin/datacollector/passwordsecurity/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Active Directory Data Collector Wizard to ensure that no accidental -clicks are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** to close +the Active Directory Data Collector Wizard instead. This prevents the wizard from saving accidental +clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/permissionmatrix.md b/docs/accessanalyzer/11.6/admin/datacollector/permissionmatrix.md index a0d710127e..8c3cff0469 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/permissionmatrix.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/permissionmatrix.md @@ -6,12 +6,11 @@ sidebar_position: 10 # Permissions by Data Collector (Matrix) -The Enterprise Auditor data collectors are capable of collecting information from a variety of -sources. Each data collector requires specific protocols, ports, and permissions for the collection -of data to occur. +The Enterprise Auditor data collectors collect information from a variety of sources. Each data +collector requires specific protocols, ports, and permissions to collect data. -Many data collectors are included as core components. However, some data collectors require specific -license features. The following table provides a quick reference for each data collector. +Netwrix includes many data collectors as core components. However, some data collectors require +specific license features. The following table provides a quick reference for each data collector. | Data Collector | Description | Protocols | Ports Used | Recommended Permissions | | -------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -22,7 +21,7 @@ license features. The following table provides a quick reference for each data c | AWS | The AWS Data Collector collects IAM users, groups, roles, and policies, as well as S3 permissions, content, and sensitive data from the target Amazon Web Services (AWS) accounts. |
  • HTTPS
|
  • 443
| To collect details about the AWS Organization, the following permission is required:
  • organizations:DescribeOrganization
To collect details regarding IAM, the following permissions are required:
  • iam:GenerateCredentialReport
  • iam:GenerateServiceLastAccessedDetails
  • iam:Get\*
  • iam:List\*
  • iam:Simulate\*
  • sts:GetAccessKeyInfo
To collect details related to S3 buckets and objects, the following permissions are required:
  • s3:Describe\*
  • s3:Get\*
  • s3:HeadBucket
  • s3:List\*
| | AzureADInventory | The AzureADInventory Data Collector catalogs user and group object information from Microsoft Entra ID, formerly Azure Active Directory. This data collector is a core component of Enterprise Auditor and is preconfigured in the .Entra ID Inventory Solution. |
  • HTTP
  • HTTPS
  • REST
|
  • TCP 80 and 443
|**Microsoft Graph API**
Application Permissions:
  • AuditLog.Read.All – Read all audit log data
  • Directory.Read.All – Read directory data
Delegated Permissions:
  • Group.Read.All – Read all groups
  • User.Read.All – Read all users' full profiles
**Access URLs**
  • https://login.windows.net
  • https://graph.windows.net
  • https://login.microsoftonline.com
  • https://graph.microsoft.com
  • All sub-directories of the access URLs listed
| | Box _\*requires license_ | The Box Data Collector audits access, group membership, and content within a Box enterprise. |
  • HTTP
  • HTTPS
|
  • TCP 80
  • TCP 443
|
  • Box Enterprise Administrator
| -| CommandLineUtility | The CommandLineUtility Data Collector provides the ability to remotely spawn, execute, and extract data provided by a Microsoft native or third-party command line utility. |
  • Remote Registry
  • RPC
|
  • TCP 135-139
  • Randomly allocated high TCP ports
|
  • Member of the local Administrators group
| +| CommandLineUtility | The CommandLineUtility Data Collector lets you remotely spawn, execute, and extract data provided by a Microsoft native or third-party command line utility. |
  • Remote Registry
  • RPC
|
  • TCP 135-139
  • Randomly allocated high TCP ports
|
  • Member of the local Administrators group
| | DiskInfo | The DiskInfo Data Collector provides enumeration of disks and their associated properties. |
  • RPC
  • WMI
|
  • TCP 135
  • Randomly allocated high TCP ports
|
  • Member of the local Administrators group
| | DNS _\*requires license_ | The DNS Data Collector provides information regarding DNS configuration and records. |
  • RPC
|
  • TCP 135
  • Randomly allocated high TCP ports
|
  • Member of the Domain Administrators group
| | DropboxAccess _\*requires license_ | The DropboxAccess Data Collector audits access, group membership, and content within a Dropbox environment. |
  • HTTP
  • HTTPS
|
  • TCP 80
  • TCP443
|
  • Dropbox Team Administrator
| @@ -31,12 +30,12 @@ license features. The following table provides a quick reference for each data c | EWSPublicFolder _\*requires license_ | The EWSPublicFolder Data Collector provides configuration options to extract public folder contents, permissions, and sensitive data, and is preconfigured within the Exchange Solution. |
  • HTTPS
  • ADSI
  • LDAP
|
  • TCP 389
  • TCP 443
| For Exchange servers:
  • Exchange Admin Role
  • Discovery Management Role
  • Application Impersonation Role
  • Exchange Online License with a mailbox
For Exchange Online:
  • Exchange Admin Role
  • Discovery Management Role
  • Exchange Online License with a mailbox
| | Exchange2K _\*requires license_ | The Exchange2K Data Collector extracts configuration details from Exchange organizations for versions 2003 and later. |
  • LDAP
  • MAPI
  • PowerShell
  • RPC
  • WMI
|
  • TCP 135-139
  • Randomly allocated high TCP ports
  • TCP 389
  • Optional TCP 445
|
  • Member of the Exchange Administrator group
  • Domain Admin for AD property collection
  • Public Folder Management
| | ExchangeMailbox _\*requires license_ | The ExchangeMailbox Data Collector extracts configuration details from the Exchange Store to provide statistical, content, permission, and sensitive data reporting on mailboxes. |
  • MAPI
  • RPC
|
  • TCP 135
  • Randomly allocated high TCP ports
|
  • Member of the Exchange Administrator group
  • Organization Management
  • Discovery Management
| -| ExchangeMetrics _\*requires license_ | The ExchangeMetrics Data Collector collects Mail-Flow metrics from the Exchange Message Tracking Logs on the Exchange servers. Some examples of this include server volume and message size statistics. |
  • RPC
  • WMI
|
  • TCP 135
  • Randomly allocated high TCP ports
|
  • Member of the local Administrator group on the targeted Exchange server(s)
| -| ExchangePS _\*requires license_ | The ExchangePS Data Collector utilizes the Exchange CMDlets to return information about the Exchange environment utilizing PowerShell. This data collector has been designed to work with Exchange 2010 and newer. |
  • PowerShell
|
  • TCP 135
  • Randomly allocated high TCP ports
| For Exchange servers:
  • Remote PowerShell enabled on a single Exchange server
  • Windows Authentication enabled for the PowerShell Virtual Directory on the same Exchange server where Remote PowerShell has been enabled
  • View-Only Organization Management Role Group
  • Discovery Search Management Role Group
  • Public Folder Management Role Group
  • Mailbox Search Role
For Exchange Online:
  • Discovery Management Role
  • Organization Management Role
| +| ExchangeMetrics _\*requires license_ | The ExchangeMetrics Data Collector collects Mail-Flow metrics from the Exchange Message Tracking Logs on the Exchange servers. Some examples of this include server volume and message size statistics. |
  • RPC
  • WMI
|
  • TCP 135
  • Randomly allocated high TCP ports
|
  • Member of the local Administrator group on the targeted Exchange servers
| +| ExchangePS _\*requires license_ | The ExchangePS Data Collector uses the Exchange CMDlets to return information about the Exchange environment using PowerShell. This data collector has been designed to work with Exchange 2010 and newer. |
  • PowerShell
|
  • TCP 135
  • Randomly allocated high TCP ports
| For Exchange servers:
  • Remote PowerShell enabled on a single Exchange server
  • Windows Authentication enabled for the PowerShell Virtual Directory on the same Exchange server where Remote PowerShell has been enabled
  • View-Only Organization Management Role Group
  • Discovery Search Management Role Group
  • Public Folder Management Role Group
  • Mailbox Search Role
For Exchange Online:
  • Discovery Management Role
  • Organization Management Role
| | ExchangePublicFolder _\*requires license_ | The ExchangePublicFolder Data Collector audits an Exchange Public Folder, including contents, permissions, ownership, and replicas. |
  • MAPI
  • RPC
|
  • TCP 135
  • Randomly allocated high TCP ports
|
  • Member of the Exchange Administrator group
  • Organization Management
| | File | The File Data Collector provides file and folder enumeration, properties, and permissions. |
  • RPC
  • WMI
|
  • TCP 135-139
  • Randomly allocated high TCP ports
  • Optional TCP 445
|
  • Member of the Local Administrators group
| | FileSystemAccess (FSAA) _\*requires license_ | The FileSystemAccess (FSAA) Data Collector collects permissions, content, and activity, and sensitive data information for Windows and NAS file systems. |
  • Remote Registry
  • WMI
|
  • Ports vary based on the Scan Mode Option selected. See the [File System Scan Options](/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/scanoptions.md) topic for additional information.
|
  • Permissions vary based on the Scan Mode Option selected. See the [File System Supported Platforms](/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/filesystems.md) topic for additional information.
| -| GroupPolicy | The GroupPolicy Data Collector provides the ability to retrieve the GPO’s list in the domain and where they are linked, return information on configured policies and policy parts from the individual policies that have been selected, return information on selected policy parts from all policies within the domain, and return effective security policies in effect at the individual workstation. |
  • LDAP
  • RPC
|
  • TCP 389
  • TCP 135-139
  • Randomly allocated high TCP ports
|
  • Member of the Domain Administrators group (if targeting domain controllers)
  • Member of the Local Administrators group
| +| GroupPolicy | The GroupPolicy Data Collector lets you retrieve the GPO’s list in the domain and where they are linked, return information on configured policies and policy parts from the individual policies that have been selected, return information on selected policy parts from all policies within the domain, and return effective security policies in effect at the individual workstation. |
  • LDAP
  • RPC
|
  • TCP 389
  • TCP 135-139
  • Randomly allocated high TCP ports
|
  • Member of the Domain Administrators group (if targeting domain controllers)
  • Member of the Local Administrators group
| | INIFile | The INIFile Data Collector provides options to configure a task to collect information about log entries on target hosts. |
  • RPC
|
  • TCP 135-139
  • Randomly allocated high TCP ports
  • Optional TCP 445
|
  • Member of the Local Administrators group
| | LDAP | The LDAP Data Collector uses LDAP to query Active Directory returning the specified objects and attributes. |
  • LDAP
|
  • TCP 389
|
  • Member of the Domain Administrators group
| | NIS | The NIS Data Collector inventories a NIS domain for user and group information, mapping to Windows-style SIDs. |
  • NIS
|
  • TCP 111 or UDP 111
  • Randomly allocated high TCP ports
|
  • No special permissions are needed aside from access to a NIS server
| @@ -51,7 +50,7 @@ license features. The following table provides a quick reference for each data c | Services | The Services Data Collector enumerates status and settings from remote services. |
  • RPC
  • WMI
|
  • TCP 135-139
  • Randomly allocated high TCP ports
|
  • Member of the Local Administrators group
| | SharePointAccess (SPAA) _\*requires license_ | The SharePointAccess (SPAA) Data Collector audits access, group membership, and content within a SharePoint on-premises and SharePoint Online environment. The SPAA Data Collector has been preconfigured within the SharePoint Solution. |
  • MS SQL
  • Remote Registry
  • SP CSOM (Web Services via HTTP & HTTPS)
  • SP Server API
  • WCF AUTH via TCP (configurable)
|
  • Ports vary based on the Scan Mode selected and target environment. See the [SharePoint Scan Options](/docs/accessanalyzer/11.6/requirements/sharepoint/scanoptions/scanoptions.md) topic for additional information.
|
  • Permissions vary based on the Scan Mode selected and target environment. See the [SharePoint Support](/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepoint.md) topic for additional information.
| | SMARTLog | The SMARTLog Data Collector provides search and extraction of details from Windows Event Logs (online or offline) and Microsoft Exchange Internet Information Server (IIS) logs. |
  • Log
  • Remote Event
  • RPC
|
  • TCP 135
  • TCP 445
  • Randomly allocated high TCP ports
|
  • Member of the Domain Administrators group (if targeting domain controllers)
  • Member of the local Administrators group
| -| SQL _\*requires license_ | The SQL Data Collector provides information on database configuration, permissions, data extraction, application name of the application responsible for activity events, an IP Address or Host name of the client server, and sensitive data reports. This data collector also provides information on Oracle databases including infrastructure and operations. | TCP | For Db2 Target:
  • Specified by Instances table (default is 5000)
For MySQL Target:
  • Specified by Instances table (default is 3306)
For Oracle Target:
  • Specified by Instances table (default is 1521)
For PostgreSQL Target:
  • Specified by Instances table (default is 5432)
For SQL Target:
  • Specified by Instances table (default is 1433)
| **For MySQL Target:**
  • Read access to MySQL instance to include all databases contained within each instance
  • Windows Only — Domain Admin or Local Admin privilege
**For Oracle Target:**
  • User with SYSDBA role
  • Local Administrator on the target servers – Only applies to Windows Servers and not on Linux or Unix operating systems
**For PostgreSQL Target:**
  • Read access to all the databases in PostgreSQL cluster or instance
  • Windows Only — Domain Admin or Local Admin privilege
**For Redshift Target:**
  • Read-access to the following tables:
  • pg_tables
  • pg_user
**For SQL Target:**
For Instance Discovery, local rights on the target SQL Servers:
  • Local group membership to Remote Management Users
  • Permissions on the following WMI NameSpaces: `root\Microsoft\SQLServer, root\interop`
For permissions for data collection:
  • Read access to SQL instance
  • Requires SQL Full-Text and Semantic Extractions for Search feature to be installed on the target SQL instance(s) when using the **Scan full rows for sensitive data** option on the Options wizard page
  • Grant Authenticate Server to [DOMAIN\USER]
  • Grant Connect SQL to [DOMAIN\USER]
  • Grant View any database to [DOMAIN\USER]
  • Grant View any definition to [DOMAIN\USER]
  • Grant View server state to [DOMAIN\USER]
  • Grant Control Server to [DOMAIN\USER] (specifically required for the Weak Passwords Job)
| +| SQL _\*requires license_ | The SQL Data Collector provides information on database configuration, permissions, data extraction, application name of the application responsible for activity events, an IP Address or Host name of the client server, and sensitive data reports. This data collector also provides information on Oracle databases including infrastructure and operations. | TCP | For Db2 Target:
  • Specified by Instances table (default is 5000)
For MySQL Target:
  • Specified by Instances table (default is 3306)
For Oracle Target:
  • Specified by Instances table (default is 1521)
For PostgreSQL Target:
  • Specified by Instances table (default is 5432)
For SQL Target:
  • Specified by Instances table (default is 1433)
| **For MySQL Target:**
  • Read access to MySQL instance to include all databases contained within each instance
  • Windows Only — Domain Admin or Local Admin privilege
**For Oracle Target:**
  • User with SYSDBA role
  • Local Administrator on the target servers – Only applies to Windows Servers and not on Linux or Unix operating systems
**For PostgreSQL Target:**
  • Read access to all the databases in PostgreSQL cluster or instance
  • Windows Only — Domain Admin or Local Admin privilege
**For Redshift Target:**
  • Read-access to the following tables:
  • pg_tables
  • pg_user
**For SQL Target:**
For Instance Discovery, local rights on the target SQL Servers:
  • Local group membership to Remote Management Users
  • Permissions on the following WMI NameSpaces: `root\Microsoft\SQLServer, root\interop`
For permissions for data collection:
  • Read access to SQL instance
  • Requires SQL Full-Text and Semantic Extractions for Search feature to be installed on the target SQL instances when using the **Scan full rows for sensitive data** option on the Options wizard page
  • Grant Authenticate Server to [DOMAIN\USER]
  • Grant Connect SQL to [DOMAIN\USER]
  • Grant View any database to [DOMAIN\USER]
  • Grant View any definition to [DOMAIN\USER]
  • Grant View server state to [DOMAIN\USER]
  • Grant Control Server to [DOMAIN\USER] (specifically required for the Weak Passwords Job)
| | SystemInfo | The SystemInfo Data Collector extracts information from the target system based on the selected category. |
  • Remote Registry
  • RPC
  • WMI
|
  • TCP 135-139
  • Randomly allocated high TCP ports
|
  • Member of the Local Administrators group
| | TextSearch | The TextSearch Data Collector enables searches through text based log files. |
  • RPC
|
  • TCP 135-139
  • Randomly allocated high TCP ports
|
  • Member of the Local Administrators group
| | Unix _\*requires license_ | The Unix Data collector provides host inventory, software inventory, and logical volume inventory on UNIX & Linux platforms. |
  • SSH
|
  • TCP 22
  • User configurable
|
  • Root permissions in Unix/Linux
| diff --git a/docs/accessanalyzer/11.6/admin/datacollector/powershell/editquery.md b/docs/accessanalyzer/11.6/admin/datacollector/powershell/editquery.md index f35c18a8a1..89df5cd647 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/powershell/editquery.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/powershell/editquery.md @@ -15,9 +15,8 @@ The options on the Edit Query page are: - Open – Click to import and open a PowerShell script - Script Editor – Input PowerShell script to use for the configured job -- Parameters – The Parameters tab located on the right-hand side of the Edit Query page is used to - bring up the Parameters window. See the [Parameters](#parameters) topic for additional - information. +- Parameters – Use the Parameters tab on the right-hand side of the Edit Query page to open the + Parameters window. See the [Parameters](#parameters) topic for additional information. - Use table input for PowerShell script – select the checkbox to bring up the Input options for the PowerShell script. See the [Input Options](#input-options) topic for additional information. @@ -36,8 +35,8 @@ The options in the Parameters Window are: - Delete – Delete a parameter :::note -Only user created parameters can be edited or deleted. Pre-configured parameters cannot be -edited or deleted. +You can edit or delete only user-created parameters. You can't edit or delete preconfigured +parameters. ::: @@ -64,14 +63,14 @@ The options in the Add/Edit Variable window are: ## Input Options -When the Use table input for PowerShell script option is selected on the Edit Query page, additional +When you select the Use table input for PowerShell script option on the Edit Query page, additional options display to define the source for input data. ![Edit Query page input options](/images/accessanalyzer/11.6/admin/datacollector/powershell/editqueryinput.webp) The input options are: -- Please select name – Select the input table to be used from the drop-down menu +- select name – Select the input table to use from the dropdown menu - Filter nulls – Excludes values that are null from input - Filter duplicates – Excludes any values that are duplicate from input - Text Box – Displays an example of how the input can be used in a PowerShell script @@ -81,5 +80,5 @@ The input options are: ![Text Box and the Columns tab populated with information](/images/accessanalyzer/11.6/admin/datacollector/powershell/editqueryinputtable.webp) -Selecting an input table in the **Please select name** dropdown populates the Text Box and the +Selecting an input table in the **select name** dropdown populates the Text Box and the Columns tab with information. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/powershell/options.md b/docs/accessanalyzer/11.6/admin/datacollector/powershell/options.md index ec45b7f865..9b564d847f 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/powershell/options.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/powershell/options.md @@ -12,11 +12,11 @@ The Options page provides the option to execute the script remotely on the targe The configurable options are: -- Execute remotely – Remotely executes the script on the target host. If this checkbox is not - selected, the script will be executed from the Enterprise Auditor Console server. +- Execute remotely – Remotely executes the script on the target host. If you don't select this + checkbox, the script runs from the Enterprise Auditor Console server. - Use impersonation within server executable – Executes the script with the job credentials For cmdlets requiring explicit credentials, a single credential set from the job's Connection Profile can be referenced using `Get-Credential` or the `$JobCredential` variable, a `PSCredential` -type object. All credentials from the job’s Connection Profile may be accessed via the +type object. You can access all credentials from the job's Connection Profile via the `$JobCredentials` array. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/powershell/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/powershell/overview.md index 25bd9200cf..5b54ff7b19 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/powershell/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/powershell/overview.md @@ -37,5 +37,5 @@ contains the following pages: ![PowerShell Data Collector Wizard Welcome page](/images/accessanalyzer/11.6/admin/datacollector/powershell/welcome.webp) -The Welcome page can be hidden by checking the **Do not display this page the next time** box when -the wizard is open and configuration settings are saved. +Check the **Don't display this page the next time** box to hide the Welcome page. The wizard saves +this setting with your configuration changes. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/powershell/results.md b/docs/accessanalyzer/11.6/admin/datacollector/powershell/results.md index 90d7231608..3d5474bf4b 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/powershell/results.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/powershell/results.md @@ -14,4 +14,4 @@ components. The Results page options are: - Properties to return – List of available properties which can be gathered for the PowerShell query -- ROWKEY's components – List of available properties based on which ROWKEY will be built +- ROWKEY's components – List of available properties for building ROWKEY diff --git a/docs/accessanalyzer/11.6/admin/datacollector/powershell/sampleserver.md b/docs/accessanalyzer/11.6/admin/datacollector/powershell/sampleserver.md index 628eb570d4..078e307f31 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/powershell/sampleserver.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/powershell/sampleserver.md @@ -13,10 +13,10 @@ The Sample Server page provides a box to select a server to generate the result The Select Server page options are: - Server name – Server to be used during configuration -- Validate – Validates the script results and retrieves result columns. Validation must be run in - order to populate and enable the Results page. +- Validate – Validates the script results and retrieves result columns. Run validation to populate + and enable the Results page. The server selected here replaces any `[SAHOSTNAME]` tokens in the PowerShell script. During -execution, the `[SAHOSTNAME]` tokens are replaced in turn by each host in the host list. If no +execution, each host in the host list replaces the `[SAHOSTNAME]` tokens in turn. If no `[SAHOSTHAME]` tokens exist in the PowerShell script, then the server name and the hosts in the host list have no effect. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/powershell/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/powershell/summary.md index 29b4869d11..797704ca3d 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/powershell/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/powershell/summary.md @@ -11,6 +11,6 @@ Data Collector Wizard. ![PowerShell Data Collector Wizard Summary page](/images/accessanalyzer/11.6/admin/datacollector/powershell/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the PowerShell Data Collector Wizard ensuring that no accidental clicks -are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** to close +the PowerShell Data Collector Wizard instead. This prevents the wizard from saving accidental +clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/registry.md b/docs/accessanalyzer/11.6/admin/datacollector/registry.md index 881da9ff90..399ef48ffa 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/registry.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/registry.md @@ -7,13 +7,14 @@ sidebar_position: 300 # Registry Data Collector The Registry Data Collector queries the registry and returns keys, key values, and permissions on -the keys. The data in the native tables returned by the Registry Data Collector is dependent upon -the query configuration. For example, a query could be configured to only show permissions on -registry keys in a 32-bit view. Another query could be configured to show a listing of all keys and -key values in a 64-bit view. Wildcards can also be used in query configurations. - -The Registry Data Collector is a core component of Enterprise Auditor, but it has been preconfigured -within both the Active Directory Solution and the Windows Solution. While the data collector is +the keys. The data in the native tables returned by the Registry Data Collector depends on the query +configuration. For example, you can configure a query to show only permissions on registry keys in +a 32-bit view. You can configure another query to show a listing of all keys and key values in a +64-bit view. You can also use wildcards in query configurations. + +The Registry Data Collector is a core component of Enterprise Auditor, and the Active Directory +Solution and the Windows Solution both include it as a preconfigured component. While the data +collector is available with all Enterprise Auditor license options, these solutions are only available with a special Enterprise Auditor licenses. See the following topics for additional information: @@ -42,16 +43,16 @@ The Registry Data Collector is configured through the Registry Browser window. The configurable options are: -- Sample Host – The host to connect to. If this box is left blank, the connection is to the local - host. +- Sample Host – The host to connect to. If you leave this box blank, the connection defaults to the + local host. - 64-bit view – The default view is 32-bit. Select the **64-bit view** checkbox to switch to a 64-bit view. -- Connect – Connect to host’s registry. If no host is specified in the Sample Host box, the - connection is to the local host’s registry. +- Connect – Connect to host's registry. If you don't specify a host in the Sample Host box, the + connection defaults to the local host's registry. - Query 32-bit view – Select this checkbox to query the 32-bit view of the registry - Query 64-bit view – Select this checkbox to query the 64-bit view of the registry -- Name – The key value. Key values can be added to the Selected Properties list by pressing the - **ctrl** key, selecting the keys to add, and then clicking the **Add currently selected value** +- Name – The key value. Add key values to the Selected Properties list by pressing the + **ctrl** key, selecting the keys to add, and clicking the **Add selected value** button. - Type – The key value type - Data – The key value path @@ -71,11 +72,11 @@ to do the following: | Icon | Name | | ------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------- | | ![Select all peer keys for this node](/images/accessanalyzer/11.6/admin/datacollector/selectall.webp) | Select all peer keys for this node | -| ![Add name of currently selected key](/images/accessanalyzer/11.6/admin/datacollector/addname.webp) | Add name of currently selected key | -| ![Add full path of the currently selected key](/images/accessanalyzer/11.6/admin/datacollector/addpath.webp) | Add full path of the currently selected key | -| ![Add last write date/time of currently selected key](/images/accessanalyzer/11.6/admin/datacollector/adddatetime.webp) | Add last write date/time of currently selected key | +| ![Add name of selected key](/images/accessanalyzer/11.6/admin/datacollector/addname.webp) | Add name of selected key | +| ![Add full path of the selected key](/images/accessanalyzer/11.6/admin/datacollector/addpath.webp) | Add full path of the selected key | +| ![Add last write date/time of selected key](/images/accessanalyzer/11.6/admin/datacollector/adddatetime.webp) | Add last write date/time of selected key | | ![Add security properties for selected key](/images/accessanalyzer/11.6/admin/datacollector/addproperties.webp) | Add security properties for selected key | | ![Enumerate all values for this key](/images/accessanalyzer/11.6/admin/datacollector/enumeratevalues.webp) | Enumerate all values for this key | -| ![Add currently selected value](/images/accessanalyzer/11.6/admin/datacollector/addvalue.webp) | Add currently selected value | +| ![Add selected value](/images/accessanalyzer/11.6/admin/datacollector/addvalue.webp) | Add selected value | | ![Delete properties from selection](/images/accessanalyzer/11.6/admin/datacollector/delete.webp) | Delete properties from selection | | ![Go to selected key](/images/accessanalyzer/11.6/admin/datacollector/goto.webp) | Go to selected key | diff --git a/docs/accessanalyzer/11.6/admin/datacollector/script/add.md b/docs/accessanalyzer/11.6/admin/datacollector/script/add.md index 56bd8dc118..79b0bfee78 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/script/add.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/script/add.md @@ -6,17 +6,17 @@ sidebar_position: 20 # Add a Script to an Existing Query -The Query Properties window provides the ability to add a script to an existing query. Typically, a -script is used to augment a query providing services such as conversion of returned data. +The Query Properties window lets you add a script to an existing query. Typically, you use a script +to augment a query, providing services such as conversion of returned data. -Follow the steps to add a script. +To add a script: **Step 1 –** Navigate to the job's **Configure** node and select **Queries**. **Step 2 –** Click **Create Query** to open the Query Properties window. -**Step 3 –** Select the **Data Source** tab and select the desired data collector in the Data -Collector drop-down menu. +**Step 3 –** Select the **Data Source** tab and select the data collector you want in the Data +Collector dropdown menu. ![Query Properties window](/images/accessanalyzer/11.6/admin/datacollector/script/querypropertiesexisting.webp) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/script/editor.md b/docs/accessanalyzer/11.6/admin/datacollector/script/editor.md index 60d19cf53c..f069884d81 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/script/editor.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/script/editor.md @@ -6,7 +6,7 @@ sidebar_position: 30 # VBScript Editor -The VBScript Editor window provides the means to add a script. The window is ideal for editing small +The VBScript Editor window lets you add a script. The window is ideal for editing small scripts and for pasting larger scripts from external scripting tools. ![VBScript Editor window](/images/accessanalyzer/11.6/admin/datacollector/script/vbscripteditor.webp) @@ -14,10 +14,10 @@ scripts and for pasting larger scripts from external scripting tools. The options in the VBScript Editor are: - Save and Close – Use this option to save the script and close the window -- Syntax Check – Use this option to check the syntax of your script. This does not identify logic +- Syntax Check – Use this option to check the syntax of your script. This doesn't identify logic errors, only cases where the script syntax is incorrect. It helps reduce the overhead of debugging - a script. When selected, a Script Errors window opens and a syntax check is performed. Any - syntactical errors are displayed within the window. + a script. When you select this option, a Script Errors window opens and runs a syntax check. The + window displays any syntax errors. - Load from file – Use this option to load a VB script from a .vbs file - Save to file – Use this option to save the current script in the Editor - Undo – Undo previous changes made to the script (Shortcut is Ctrl+Z) @@ -25,8 +25,8 @@ The options in the VBScript Editor are: - Cut – Cut the highlighted text - Copy – Copy the highlighted text - Paste – Paste cut or copied text into the VB Script Editor -- Online VBScript Language Reference – Opens internet browser to the Microsoft Technical - Documentation website from where documentation for Visual Basic Script can be navigated to +- Online VBScript Language Reference – Opens a browser to the Microsoft Technical + Documentation website, where you can find documentation for Visual Basic Script After adding or modifying a script, click **Save and close**. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/script/example1.md b/docs/accessanalyzer/11.6/admin/datacollector/script/example1.md index d9be2daa43..19a31a55d9 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/script/example1.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/script/example1.md @@ -7,26 +7,25 @@ sidebar_position: 70 # Script Example 1: Conversion of Data This script example demonstrates how to perform a query and modify returned data. The script -provides the data collector with the information that would have been provided if the user interface -had been used to design the query. However, in this case it is all done through script. The data -collector returns a value that is then converted and stored by Enterprise Auditor. +provides the data collector with the information you would provide if you used the user interface to +design the query. However, in this case, the script does it all. The data collector returns a value, +and Enterprise Auditor converts and stores it. -This script starts by defining a query using the Perfmon Data Collector. Notice that the -**WorkingQuery** object is used, not the Query object. This is done to preserve the Query object, -since the Query object will be used to store the results that are different from what the data -collector is providing. +This script starts by defining a query using the Perfmon Data Collector. Notice that the script uses +the **WorkingQuery** object, not the Query object. This preserves the Query object, since the script +uses it to store results that differ from what the data collector provides. -The script then issues the query by calling `WorkingQuery.Execute`. When the query completes, -**WorkingQuery** is set to view the first row of results by setting the **ResultRow** property. The -value within the **System Up Time** property is then transferred into the `REMAINDER` variable so -that it can be more easily manipulated. +The script then issues the query by calling `WorkingQuery.Execute`. When the query completes, the +script sets **WorkingQuery** to view the first row of results by setting the **ResultRow** property. +The script then transfers the value of the **System Up Time** property into the `REMAINDER` variable +for easier manipulation. The script then takes the value of `REMAINDER`, which is in seconds, and converts it to days, hours, -minutes, and seconds. These values are then recorded in the Query object so that Enterprise Auditor -can store this data. +minutes, and seconds. The script then records these values in the Query object so that Enterprise +Auditor can store the data. :::note -In this task, the hours, minutes, and seconds properties were specified manually using the +This example specifies the hours, minutes, and seconds properties manually using the task dialog. See the [Script Properties](/docs/accessanalyzer/11.6/admin/datacollector/script/properties.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/script/example2.md b/docs/accessanalyzer/11.6/admin/datacollector/script/example2.md index 2c2d88d90a..20dccf5b19 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/script/example2.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/script/example2.md @@ -11,25 +11,25 @@ database list from SQL Server and then proceeds to the File System Data Collecto the database file, essentially inventorying the installed databases, their paths, and sizes. :::note -Because the object instances are not thread-safe, scripts like these that use objects -external to Enterprise Auditor should be run with only one thread. +Because the object instances aren't thread-safe, run scripts like these that use objects +external to Enterprise Auditor with only one thread. ::: -In this example, a connection is opened with a SQL server. The SQL server name is provided by -Enterprise Auditor during the query. Enterprise Auditor provides the active host to the script using +In this example, the script opens a connection with a SQL server. Enterprise Auditor provides the +SQL server name during the query and provides the active host to the script using the **Query.Host** property. The script then queries the Master database, requesting a **recordset** containing all databases and proceeds to get the row count. Setting the **Query.ResultRows** property creates a row of storage for each record in the recordset. It then proceeds to read data from each row by looping row by row. -For each row, the database name, filename, and ID are captured. The script then calls a function to -get the size of the file. The **FileSize** function uses the database filename to construct a query -to the File System Data Collector, which ultimately returns the size of the file. +For each row, the script captures the database name, filename, and ID. The script then calls a +function to get the size of the file. The **FileSize** function uses the database filename to +construct a query to the File System Data Collector, which ultimately returns the size of the file. -The data for each database is stored in the Query object. +The script stores the data for each database in the Query object. -Finally, the SQL objects are freed. +Finally, the script frees the SQL objects. ## Example of Compound Query Script diff --git a/docs/accessanalyzer/11.6/admin/datacollector/script/methodsproperties.md b/docs/accessanalyzer/11.6/admin/datacollector/script/methodsproperties.md index c42438b310..d8741d0ccf 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/script/methodsproperties.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/script/methodsproperties.md @@ -26,7 +26,7 @@ The Query and Working Query objects support the following methods and properties | Path : sting | Sets or retrieves the path | | Paths : integer | Sets or retrieves the current path for multi-path tasks | | ResultData (Property : string) : Variant | Sets or retrieves the value for the property specified | -| ResultData (PropertyIndex : integer) : Variant | Sets ResultRow to the desired row before accessing this property | +| ResultData (PropertyIndex : integer) : Variant | Sets ResultRow to the row you want before accessing this property | | ResultRow : integer | Sets or retrieves the current row. For non-enumerated tasks, ResultRow will always be 0. | | ResultRows : integer | Sets or returns the count of rows. Use this to determine the number of rows returned after an enumerated task is executed. Set this property to create a multi-row return value. | | Message (index : integer, type : string) | Sets or returns a message in the indicated position. Use MessageCount to determine the number of messages. These messages appear in the job MessageLog. | diff --git a/docs/accessanalyzer/11.6/admin/datacollector/script/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/script/overview.md index 5a7ee04537..b1bb108ae7 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/script/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/script/overview.md @@ -18,15 +18,16 @@ The following examples describe situations where using a script may be useful: another, for example `build1230` to `at risk`. See the [Script Example 1: Conversion of Data](/docs/accessanalyzer/11.6/admin/datacollector/script/example1.md) topic for additional information. -- Compound Queries – This is a query that cannot be performed using a single query. See the +- Compound Queries – This is a query that you can't perform using a single query. See the [Script Example 2: Command Query](/docs/accessanalyzer/11.6/admin/datacollector/script/example2.md) topic for additional information. - Interfacing with External Systems – This is a query that requires access to external data. For example, the query needs to access a corporate database to obtain a location code. -The Script Data Collector is a core component of Enterprise Auditor, but it has been preconfigured -within the Windows Solution. While the data collector is available with all Enterprise Auditor -license options, the Windows Solution is only available with a special Enterprise Auditor license. +The Script Data Collector is a core component of Enterprise Auditor, and the Windows Solution +includes it as a preconfigured component. While the data collector is available with all Enterprise +Auditor license options, the Windows Solution is only available with a special Enterprise Auditor +license. See the [Windows Solution](/docs/accessanalyzer/11.6/solutions/windows/overview.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/script/properties.md b/docs/accessanalyzer/11.6/admin/datacollector/script/properties.md index 0a7e34e619..05e3cd9026 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/script/properties.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/script/properties.md @@ -6,9 +6,9 @@ sidebar_position: 60 # Script Properties -The Data Source tab is used to select the data collector to be used. The configurable options are: +Use the Data Source tab to select the data collector. The configurable options are: -- Source – Used to select data collector +- Source – Select the data collector - Path – Displays the returned path from the data collector :::warning @@ -17,24 +17,23 @@ The Data Source tab is used to select the data collector to be used. The configu ::: - - The path is used to identify the selection from within the data collector. The path - essentially tells the data collector where the data is and depending on the data collector, - may define selected options. It is sometimes convenient to edit the path manually. - - For example: If defining a file system query using the File System Data Collector, the path - would automatically be filled in with the selected details. A minor change like changing the - file location can be done manually by editing the path. + - The path identifies the selection within the data collector. The path essentially tells the + data collector where the data is and, depending on the data collector, may define selected + options. It's sometimes convenient to edit the path manually. + - For example, if you define a file system query using the File System Data Collector, + Enterprise Auditor automatically fills in the path with the selected details. You can manually + edit the path to make a minor change, like changing the file location. -- Properties – As the Path is used to define where the target data is, the properties are used to - define what data is desired. Each property has a series of attributes including: +- Properties – While the path defines where the target data is, the properties define what data you + want. Each property has a series of attributes including: - Name – Identifies the target data. Modifying this affects what data the data collector returns. - Column – Specifies the column name within the result data. Use this to specify the column name - that will be used within the report output. This is set by default to match the **Name** - attribute. - - DataType – Used to determine the format of the data for reporting purposes. It affects sorting - order and the ability to graph content. In some cases, the data collector is unable to - determine the correct data type for the returned data. + for the report output. By default, this matches the **Name** attribute. + - DataType – Determines the format of the data for reporting purposes. It affects sorting + order and the ability to graph content. In some cases, the data collector can't determine the + correct data type for the returned data. :::warning Setting this value manually to an incorrect data type may render your results @@ -42,25 +41,25 @@ The Data Source tab is used to select the data collector to be used. The configu ::: - - For example: Querying the registry for a value stored as **REG_SZ** returns a string, as - **REG_SZ** is a string type in the registry. However, sometimes numbers are recorded in - **REG_SZ** entries. If you determine that the content returned could always be interpreted as - numeric, you could override the default `STRING` value and set it to `NUMERIC`. This provides - proper sorting and charting ability. + - For example, querying the registry for a value stored as **REG_SZ** returns a string, as + **REG_SZ** is a string type in the registry. However, REG_SZ entries sometimes contain + numbers. If you determine that the returned content is always numeric, you can override the + default `STRING` value and set it to `NUMERIC`. This provides proper sorting and charting + ability. -- Size – Used to determine the width of the field used to hold String data. Setting the size smaller +- Size – Determines the width of the field used to hold String data. Setting the size smaller than the actual returned data will cause Enterprise Auditor to truncate the data in the view. However, the actual stored data in the result table will contain the full result. - Value – Reserved for internal use -- Key – Used to identify a key property. A key property is used to identify the property that - contains a unique value for enumerated tasks. A Key value is required for Change Detection and - Conformance Management on enumerated tasks. To identify a property that uniquely identifies each - row, set the Key attribute to `YES`. +- Key – Identifies a key property. A key property identifies the property that contains a unique + value for enumerated tasks. Enumerated tasks require a Key value for Change Detection and + Conformance Management. To identify a property that uniquely identifies each row, set the Key + attribute to `YES`. ## Adding and Removing Properties Manually -Although the property list is automatically populated by the data collectors, additional properties -may be added manually. Doing so allocates storage within Enterprise Auditor during data collection +Although the data collectors automatically populate the property list, you can add additional +properties manually. Doing so allocates storage within Enterprise Auditor during data collection and creates corresponding columns in the output table. Use a script to reference and populate these properties. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/script/reference.md b/docs/accessanalyzer/11.6/admin/datacollector/script/reference.md index 1af55b8fb7..47a07e6205 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/script/reference.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/script/reference.md @@ -7,20 +7,20 @@ sidebar_position: 50 # Script Reference Enterprise Auditor provides extensions to standard Visual Basic Script. These extensions allow -access to and manipulation of task data, in addition to invoking queries. They are implemented -through two objects. +access to and manipulation of task data, in addition to invoking queries. Enterprise Auditor +implements them through two objects. **Query Object** The Query object provides access to the current query configuration and data. Use this to examine -the results of a query or to manipulate the query before it is executed. Changing properties of this -object will change the way the task is executed by Enterprise Auditor. +the results of a query or to manipulate the query before Enterprise Auditor executes it. Changing +properties of this object changes how Enterprise Auditor executes the task. **Working Query Object** The Working Query object is identical to the Query object. This object supports the same methods and -properties as the Query object but its properties and methods do not access the current query. Think -of this object as allowing the ability to create a task on the fly. Use this object to perform +properties as the Query object but its properties and methods don't access the current query. Think +of this object as allowing the ability to create a task dynamically. Use this object to perform queries, while leaving the original task undisturbed. This is valuable when performing compound queries isneeded. See the [Script Example 2: Command Query](/docs/accessanalyzer/11.6/admin/datacollector/script/example2.md) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/script/run.md b/docs/accessanalyzer/11.6/admin/datacollector/script/run.md index a2b837a967..9e35418288 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/script/run.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/script/run.md @@ -6,16 +6,16 @@ sidebar_position: 10 # Run a Stand-Alone Script -Some situations require a script to be used exclusively without defining a data source. The Query -Properties window provides the ability to add and run a script. +Some situations require you to use a script exclusively, without defining a data source. The Query +Properties window lets you add and run a script. -Follow the steps to add a script. +To add a script: **Step 1 –** Go to the job's **Configure** node and select **Queries**. **Step 2 –** Click **Create Query** to open the Query Properties window. -**Step 3 –** Select the **Data Source** tab, and select **SCRIPT** in the Data Collector drop-down +**Step 3 –** Select the **Data Source** tab, and select **SCRIPT** in the Data Collector dropdown menu. ![Query Properties window](/images/accessanalyzer/11.6/admin/datacollector/script/querypropertiesstandalone.webp) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/services.md b/docs/accessanalyzer/11.6/admin/datacollector/services.md index d93d05d765..e3a3ddf300 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/services.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/services.md @@ -7,8 +7,9 @@ sidebar_position: 320 # Services Data Collector The Services Data Collector enumerates status and settings from remote services. The Services Data -Collector is a core component of Enterprise Auditor, but it has been preconfigured within the -Windows Solution. While the data collector is available with all Enterprise Auditor license options, +Collector is a core component of Enterprise Auditor, and the Windows Solution includes it as a +preconfigured component. While the data collector is available with all Enterprise Auditor license +options, the Windows Solution is only available with a special Enterprise Auditor license. See the [Windows Solution](/docs/accessanalyzer/11.6/solutions/windows/overview.md) topic for additional information. @@ -37,14 +38,15 @@ The Services Data Collector is configured through the Service Browser window. - All Services – Select this option to build the query to extract information from all services on the target host - Specific Services – Select this option to build the query to extract information from specific - services on the target host. Select the checkboxes next to the desired services for the query + services on the target host. Select the checkboxes next to the services you want for the query after clicking **Connect**. - Connect – Click **Connect** to connect to the host and display a list of all services found -- Available Properties – Select the properties to be returned +- Available Properties – Select the properties to return :::note -In cases where the query does not find the selected services on the target host, the -`InternalName` column that is returned reflects the `DisplayName` column and no other values are -retrieved. If the services are found on the host, the `DisplayName` value in the table is resolved. +In cases where the query doesn't find the selected services on the target host, the +returned `InternalName` column reflects the `DisplayName` column, and the query doesn't retrieve +any other values. If the query finds the services on the host, it resolves the `DisplayName` value +in the table. ::: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/smartlog/collectionmethod.md b/docs/accessanalyzer/11.6/admin/datacollector/smartlog/collectionmethod.md index 45d1c67c9f..09cc807732 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/smartlog/collectionmethod.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/smartlog/collectionmethod.md @@ -6,13 +6,13 @@ sidebar_position: 60 # SMARTLog: Collection Method -The Collection Method page is used to select the collection method employed by the data collector. -It is a wizard page for all log types. +Use the Collection Method page to select the collection method the data collector uses. It's a +wizard page for all log types. ![SMART Log DC Wizard Collection Method page](/images/accessanalyzer/11.6/admin/datacollector/smartlog/collectionmethod.webp) -Select the collection method from the following options to set how the collection routine is -executed to collect the data from the target. +Select the collection method from the following options to set how the collection routine collects +the data from the target. - Using network query – Connects to the target log over the network via RPC and reads events - Using server side applet – Deploys a remote executable to the target host and then runs as a @@ -20,17 +20,17 @@ executed to collect the data from the target. Enterprise Auditor Console. :::note - The applet cannot be used to target the local host. + You can't use the applet to target the local host. ::: - Copy the log locally and process (Not available for all query scenarios) – Extract events from an - offline log by moving the log to the Enterprise Auditor Console and having it processed on the - local host instead of the target host. In order to use this option, the log type selected for the + offline log by moving the log to the Enterprise Auditor Console and processing it on the local + host instead of the target host. To use this option, the log type selected for the query must be **Windows Event Log (Archived)**. -The Applet Options section is only visible when the **Using server side applet** collection method -is selected. +The Applet Options section is visible only when you select the **Using server side applet** +collection method. - Connection retries count – The number of times to retry a failed connection. The default is 15. - Retry delay (ms) – The time between retries of a failed connection. The default is 5000 diff --git a/docs/accessanalyzer/11.6/admin/datacollector/smartlog/criteria.md b/docs/accessanalyzer/11.6/admin/datacollector/smartlog/criteria.md index 1720440c87..d2295a3ea6 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/smartlog/criteria.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/smartlog/criteria.md @@ -6,15 +6,15 @@ sidebar_position: 50 # SMARTLog: Criteria -The Criteria page is used to specify the search criteria. A test query can be run with the sample -host entered on the Sample Host page to confirm the results that will be returned by the query. It -is a wizard page for all log types. +Use the Criteria page to specify the search criteria. You can run a test query with the sample +host entered on the Sample Host page to confirm the results the query returns. It's a wizard page +for all log types. ![SMART Log DC Wizard Criteria page](/images/accessanalyzer/11.6/admin/datacollector/smartlog/criteria.webp) The **Limit number of records to** setting has a default of `1000`. -Follow the steps to configure the search criteria. +To configure the search criteria: ![Filter button on Criteria page](/images/accessanalyzer/11.6/admin/datacollector/smartlog/criteriafilter.webp) @@ -36,12 +36,11 @@ that level. The available options are **AND**, **OR**, **NOT AND**, and **NOT O - To remove a row (condition or group), click the ellipsis (**…**) on the row and select **Remove Row** -- To remove all currently configured criteria, click **Filter** and select **Clear All** +- To remove all configured criteria, click **Filter** and select **Clear All** -**Step 6 –** Click **Show data** to run a test query and sample the data that will be returned that -is connected to a target log based upon the configured criteria. The data is displayed in the -Records found table. +**Step 6 –** Click **Show data** to run a test query and sample the data connected to a target log +based on the configured criteria. The Records found table displays the data. -The search criteria has now been configured and the results it returns tested. Configure the -criteria further if the returned results are not as expected, or click **Next** to continue to the +You've now configured the search criteria and tested the results it returns. Configure the +criteria further if the returned results aren't as expected, or click **Next** to continue to the next wizard page. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/smartlog/eventlogoptions.md b/docs/accessanalyzer/11.6/admin/datacollector/smartlog/eventlogoptions.md index 7479b4d0e3..25ca82e608 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/smartlog/eventlogoptions.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/smartlog/eventlogoptions.md @@ -6,12 +6,12 @@ sidebar_position: 80 # SMARTLog: Event Log Options -The Event Log Options page is used to configure additional options. It is a wizard page for all log +Use the Event Log Options page to configure additional options. It's a wizard page for all log types. ![SMART Log DC Wizard Event Log Options page](/images/accessanalyzer/11.6/admin/datacollector/smartlog/eventlogoptions.webp) -The following additional options can be selected: +You can select the following additional options: - Lookup user name – Resolves SIDs found in the event descriptions to friendly display name values - Resolve GUIDs – Resolves GUIDs found in the event descriptions to friendly display name values diff --git a/docs/accessanalyzer/11.6/admin/datacollector/smartlog/logstate.md b/docs/accessanalyzer/11.6/admin/datacollector/smartlog/logstate.md index ec75b027a9..03926809bc 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/smartlog/logstate.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/smartlog/logstate.md @@ -6,12 +6,12 @@ sidebar_position: 70 # SMARTLog: Log State -The Log State page is used to configure how to search the log. It is a wizard page for all log +Use the Log State page to configure how to search the log. It's a wizard page for all log types. ![SMART Log DC Wizard Log State page](/images/accessanalyzer/11.6/admin/datacollector/smartlog/logstate.webp) -Select the **Persist log state** checkbox to search the log from where the search last left off. A -state file is created for each host configured in the query. State files can be viewed within -Enterprise Auditor and are named by the query GUID. State files display the record the search last -left off on, the event log, and the date of the last entry. +Select the **Persist log state** checkbox to search the log from where the search last left off. +Enterprise Auditor creates a state file for each host configured in the query. You can view state +files within Enterprise Auditor, and Enterprise Auditor names them by the query GUID. State files +display the record the search last left off on, the event log, and the date of the last entry. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/smartlog/logtype.md b/docs/accessanalyzer/11.6/admin/datacollector/smartlog/logtype.md index 1a49a2b279..5d9a62b0d6 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/smartlog/logtype.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/smartlog/logtype.md @@ -6,7 +6,7 @@ sidebar_position: 10 # SMARTLog: Log Type -The Log Type page is used to select the log type to be processed. +Use the Log Type page to select the log type to process. ![SMART Log DC Wizard Log Type page](/images/accessanalyzer/11.6/admin/datacollector/smartlog/logtype.webp) @@ -15,16 +15,16 @@ The log types are: - Windows Event Log – Connects to and extract information from any Windows event log made available on the target host - Windows Event Log (Archived) – Extract events from an offline log by moving the log to the - Enterprise Auditor Console and having it processed on the local host instead of the target host + Enterprise Auditor Console and processing it on the local host instead of the target host - Internet Information Server Log – An Exchange query that returns information from Outlook Web Access IIS logs found on CAS servers - - The IIS log must be configured to generate specific columns in order for the SMARTLog Data - Collector to audit them. See the + - Configure the IIS log to generate specific columns so the SMARTLog Data + Collector can audit them. See the [IIS Log Auditing Requirements](#iis-log-auditing-requirements) topic for additional information. -- File Change Detection Log – This is a legacy option. It should not be selected. +- File Change Detection Log – This is a legacy option. Don't select it. ## IIS Log Auditing Requirements diff --git a/docs/accessanalyzer/11.6/admin/datacollector/smartlog/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/smartlog/overview.md index e0dd4cca04..f5e4b2da72 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/smartlog/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/smartlog/overview.md @@ -9,11 +9,11 @@ sidebar_position: 340 The SMARTLog Data Collector provides search and extraction of details from Windows Event Logs (online or offline) and Microsoft Exchange Internet Information Server (IIS) logs. -The SMARTLog Data Collector is a core component of Enterprise Auditor, but it has been preconfigured -within the Active Directory Solution, Exchange Solution, SQL Solution, and the Windows Solution. -While the data collector is available with all Enterprise Auditor license options, these solutions -are only available with a special Enterprise Auditor licenses. See following sections for additional -information: +The SMARTLog Data Collector is a core component of Enterprise Auditor, and the Active Directory +Solution, Exchange Solution, SQL Solution, and Windows Solution all include it as a preconfigured +component. While the data collector is available with all Enterprise Auditor license options, these +solutions are only available with a special Enterprise Auditor license. See following sections for +additional information: - [Active Directory Solution](/docs/accessanalyzer/11.6/solutions/activedirectory/overview.md) - [Exchange Solution](/docs/accessanalyzer/11.6/solutions/exchange/overview.md) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/smartlog/results.md b/docs/accessanalyzer/11.6/admin/datacollector/smartlog/results.md index 961bb3baf8..7d3d202e77 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/smartlog/results.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/smartlog/results.md @@ -6,9 +6,8 @@ sidebar_position: 40 # SMARTLog: Results -The Results page is where the events to be returned by the query are selected. It is a wizard page -for all log types. The description strings within the log records can also be selected for the -query. +Use the Results page to select the events the query returns. It's a wizard page for all log types. +You can also select the description strings within the log records for the query. ![SMART Log DC Wizard Results page](/images/accessanalyzer/11.6/admin/datacollector/smartlog/results.webp) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/smartlog/samplehost.md b/docs/accessanalyzer/11.6/admin/datacollector/smartlog/samplehost.md index 6269dad4a5..c33d324f16 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/smartlog/samplehost.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/smartlog/samplehost.md @@ -6,14 +6,14 @@ sidebar_position: 20 # SMARTLog: Sample Host -The Sample Host page is used to configure the host. It is a wizard page for all log types. +Use the Sample Host page to configure the host. It's a wizard page for all log types. ![SMART Log DC Wizard Sample Host page](/images/accessanalyzer/11.6/admin/datacollector/smartlog/samplehost.webp) Select a host for running a test query on the Criteria page from the following radio buttons: - Local Computer – localhost -- Another computer – If selecting another computer for the host, click the ellipsis to open the +- Another computer – If you select another computer for the host, click the ellipsis to open the Select Computer window. See the [Select Computer Window](#select-computer-window) topic for additional information. @@ -21,7 +21,7 @@ Select a host for running a test query on the Criteria page from the following r ![Select Computer window](/images/accessanalyzer/11.6/admin/datacollector/smartlog/selectcomputerwindow.webp) -If selecting another computer for the host, click the ellipsis to open the Select Computer window +If you select another computer for the host, click the ellipsis to open the Select Computer window and select a computer. The options in the Select Computer window are: - Object Types – Either enter the object type name in the textbox or click **Object Types** to @@ -41,13 +41,13 @@ and select a computer. The options in the Select Computer window are: The Common Queries section is included on the advanced Select Computer window in addition to object type and location in the original Select Computer window. -- Name – Select a qualifier from the drop-down menu and enter a name of an object in the associated +- Name – Select a qualifier from the dropdown menu and enter a name of an object in the associated text box -- Description – Select a qualifier from the drop-down menu and enter a description in the associated +- Description – Select a qualifier from the dropdown menu and enter a description in the associated text box - Select the **Disabled accounts** checkbox to include disabled accounts in the search - Select the **Non-expiring password** checkbox to include non-expiring passwords in the search -- Select the number of **Days since last logon** from the drop-down menu +- Select the number of **Days since last logon** from the dropdown menu - Click the **Columns** button to open the Choose Columns window ![Choose Columns window](/images/accessanalyzer/11.6/admin/datacollector/smartlog/choosecolumnswindow.webp) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/smartlog/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/smartlog/summary.md index 527a451840..c518779a07 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/smartlog/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/smartlog/summary.md @@ -10,5 +10,5 @@ The Summary page displays a summary of the configured query. It is a wizard page ![SMART Log DC Wizard Summary page](/images/accessanalyzer/11.6/admin/datacollector/smartlog/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the SMART Log DC Wizard to ensure that no accidental clicks are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** to close +the SMART Log DC Wizard instead. This prevents the wizard from saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/smartlog/targetlog/filedetectionlog.md b/docs/accessanalyzer/11.6/admin/datacollector/smartlog/targetlog/filedetectionlog.md index 953f22dfb9..2f30e5f9e3 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/smartlog/targetlog/filedetectionlog.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/smartlog/targetlog/filedetectionlog.md @@ -6,7 +6,7 @@ sidebar_position: 20 # SMARTLog: Target Log for File Detection Log Type -The Target Log page is where logs are selected to be collected. This version is a wizard page for +Use the Target Log page to select the logs to collect. This version is a wizard page for the File Change Detection log type. ![SMART Log DC Wizard Target Log page for File Change Detection Log](/images/accessanalyzer/11.6/admin/datacollector/smartlog/targetlogtype/targetlogfiledetection.webp) @@ -16,6 +16,6 @@ of the following options: - Automatic (Local for NAS device hosts, Remote for Windows hosts) - Local Enterprise Auditor Server -- Specific Remote Server – If selected, enter the server name in the Server textbox +- Specific Remote Server – If you select this option, enter the server name in the Server textbox In the Log files to be processed section, set the filter criteria. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/smartlog/targetlog/targetlog.md b/docs/accessanalyzer/11.6/admin/datacollector/smartlog/targetlog/targetlog.md index c2906387d3..49ea0b400b 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/smartlog/targetlog/targetlog.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/smartlog/targetlog/targetlog.md @@ -6,7 +6,7 @@ sidebar_position: 30 # SMARTLog: Target Log -The Target Log page is where logs are selected to be collected. There are three versions of this +Use the Target Log page to select the logs to collect. There are three versions of this wizard page that change based on log type. This version is a wizard page for the log types of: - Windows Event Log (Archived) @@ -23,9 +23,9 @@ topics for information on the other versions of this wizard page. The configurable options are: - Path – Enter or browse to the path to the log -- File mask – Enter file names to limit the file names to return from the path entered. Asterisks - can be used for wildcards. For example, `u_ex*.log` would match **u_ex170530.log**. When no mask - is set, all files from the listed path are returned. +- File mask – Enter file names to limit the file names to return from the path entered. Use asterisks + for wildcards. For example, `u_ex*.log` would match **u_ex170530.log**. When you don't set a mask, + Enterprise Auditor returns all files from the listed path. - Log files to be processed – Select from the following options: - All diff --git a/docs/accessanalyzer/11.6/admin/datacollector/smartlog/targetlog/windowseventlog.md b/docs/accessanalyzer/11.6/admin/datacollector/smartlog/targetlog/windowseventlog.md index 73e70357ba..951c5e8f7b 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/smartlog/targetlog/windowseventlog.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/smartlog/targetlog/windowseventlog.md @@ -6,10 +6,10 @@ sidebar_position: 10 # SMARTLog: Target Log for Windows Event Log Type -The Target Log page is where logs are selected to be collected. This version is a wizard page for +Use the Target Log page to select the logs to collect. This version is a wizard page for the log type of Windows Event Log. ![SMART Log DC Wizard Target Log page for Windows Event Log](/images/accessanalyzer/11.6/admin/datacollector/smartlog/targetlogtype/targetlogwindowsevent.webp) -Only one log can be targeted per query task. The selected log is displayed at the bottom of the +You can target only one log per query task. The selected log displays at the bottom of the wizard page. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/spaa/activitydatescope.md b/docs/accessanalyzer/11.6/admin/datacollector/spaa/activitydatescope.md index dc6170a79f..d4322f428b 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/spaa/activitydatescope.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/spaa/activitydatescope.md @@ -6,17 +6,17 @@ sidebar_position: 110 # SPAA: Activity Date Scope -The Activity Date Scope page is where the range of dates for which the SharePoint activity scan will -collect data is configured. It is a wizard page for the category of Scan SharePoint Activity. +Use the Activity Date Scope page to configure the range of dates for which the SharePoint activity +scan collects data. It's a wizard page for the category of Scan SharePoint Activity. ![Activity Date Scope page](/images/accessanalyzer/11.6/admin/datacollector/spaa/activitydatescope.webp) Use the radio buttons to select the **Scan Filters**. - Relative Timespan - - Collect Activity from the last 180 days – The number of days to collect activity can be - configured with the up and down arrows - - Retain data – The timespan for data retention. Select from the drop-down list: + - Collect Activity from the last 180 days – Configure the number of days to collect activity + with the up and down arrows + - Retain data – The timespan for data retention. Select from the dropdown list: - within timespan - forever - Absolute Timespan diff --git a/docs/accessanalyzer/11.6/admin/datacollector/spaa/activityloglocations.md b/docs/accessanalyzer/11.6/admin/datacollector/spaa/activityloglocations.md index 0470e3f5b8..b9e6d94dfc 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/spaa/activityloglocations.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/spaa/activityloglocations.md @@ -6,8 +6,8 @@ sidebar_position: 120 # SPAA: Activity Log Locations -The Activity Log Locations page is where to manually configure log locations to avoid requiring -remote registry access to locate the activity event log files. It is a wizard page for the category +Use the Activity Log Locations page to manually configure log locations, avoiding the need for +remote registry access to locate the activity event log files. It's a wizard page for the category of Scan SharePoint Activity. ![Activity Log Locations page](/images/accessanalyzer/11.6/admin/datacollector/spaa/activityloglocations.webp) @@ -16,7 +16,7 @@ The options in the Activity Log Locations page are: - Add – Opens the Customize Activity Log UNC Paths location window to add a new host - Add Default – Opens the Customize Activity Log UNC Paths location window for the default host -- Edit – Opens the Customize Activity Log UNC Paths window for the selected host. If edits are made, +- Edit – Opens the Customize Activity Log UNC Paths window for the selected host. If you make edits, click **OK** to save the changes. - Remove – Removes the selected host @@ -31,17 +31,17 @@ The options in the Customize Activity Log UNC Paths Window are: Activity Logs (as configured in **Activity Monitor** > **Monitored Hosts**) :::note - For On-Premises environments you do not need to specify an Activity Log UNC path as + For On-Premises environments you don't need to specify an Activity Log UNC path as the Data Collector will default to finding the log locations via the registry. ::: - Activity archive UNC path – UNC path to the archive location of Activity Logs (as configured in - **Activity Monitor** > **Agents**). If archiving is not enabled in Activity Monitor this can be + **Activity Monitor** > **Agents**). If archiving isn't enabled in Activity Monitor this can be left blank. :::note -In any UNC paths, `%HOST%` will be replaced with the host name. +In any UNC paths, Enterprise Auditor replaces `%HOST%` with the host name. ::: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/spaa/additionalscoping.md b/docs/accessanalyzer/11.6/admin/datacollector/spaa/additionalscoping.md index a3ae335519..45a96fd2cd 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/spaa/additionalscoping.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/spaa/additionalscoping.md @@ -6,33 +6,33 @@ sidebar_position: 60 # SPAA: Additional Scoping -The Additional Scoping page is where the scan can be limited by depth of the scan. It is a wizard +Use the Additional Scoping page to limit the scan by depth. It's a wizard page for the categories of: - Scan SharePoint Access - Scan For Sensitive Content :::warning -Users should not change scans in a way that would result in less data being returned on -a subsequent scan (i.e. scanning fewer web applications, scanning fewer site collections, or a -shallower depth scan). Those resources not included in a subsequent scan are marked as deleted in -the Tier 2 database and subsequently removed from the Tier 1 database. +Don't change scans in a way that results in a subsequent scan returning less data (for example, +scanning fewer web applications, scanning fewer site collections, or using a shallower depth scan). +Enterprise Auditor marks resources not included in a subsequent scan as deleted in the Tier 2 +database and subsequently removes them from the Tier 1 database. ::: ![Additional Scoping page](/images/accessanalyzer/11.6/admin/datacollector/spaa/additionalscoping.webp) -If checked, set the **Limit scanned depth to: [number] level(s)** option to the desired depth. If -this option is not checked then the entire farm is scanned. If the scoping depth is set to **0** -then only root site collections are scanned. Each increment to the depth adds an additional level of -depth from that point. +If you check this option, set the **Limit scanned depth to: [number] levels** option to the depth +you want. If you don't check this option, the scan covers the entire farm. If you set the scoping +depth to **0**, the scan covers only root site collections. Each increment to the depth adds an +additional level of depth from that point. Check the **Perform differential scan** box to enable the job to run a differential scan. -Differential scanning is enabled by default. When this option is enabled, SPAA scan will only parse -files for content/SDD if it has been modified since the last scan. +Differential scanning is on by default. When you enable this option, the SPAA scan only parses +files for content/SDD that have changed since the last scan. :::note -This option only applies to Tag collection and Sensitive data collection. Files will be -still be scanned for permissions regardless of whether this option is checked or not. +This option only applies to Tag collection and Sensitive data collection. Enterprise Auditor +still scans files for permissions regardless of whether you check this option. ::: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/spaa/agentsettings.md b/docs/accessanalyzer/11.6/admin/datacollector/spaa/agentsettings.md index 5ee2ba010d..1c3ac9a7a2 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/spaa/agentsettings.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/spaa/agentsettings.md @@ -6,20 +6,20 @@ sidebar_position: 70 # SPAA: Agent Settings -The Agent Settings page is where the SharePoint Agent Service is configured. It is a wizard page for +Use the Agent Settings page to configure the SharePoint Agent Service. It's a wizard page for the category of Scan SharePoint Access. ![Agent Settings page](/images/accessanalyzer/11.6/admin/datacollector/spaa/agentsettings.webp) The **Enable Agent Service Scans** checkbox enables collecting SharePoint data through the agent -services instead of directly from SharePoint. This option requires a **Network Port** to be entered. +services instead of directly from SharePoint. This option requires you to enter a **Network Port**. Agent Service Identity radio buttons are: - Use Job Credentials when job has same credentials as agent services - Use Custom Identity for other agent service credential scenarios - Specify identity in the format `spn:name` or `upn:name` - - The token `%HOST%` may be substituted for the host name + - You may substitute the token `%HOST%` for the host name -This option requires the SharePoint Agent to be installed on the application server. See the +This option requires you to install the SharePoint Agent on the application server. See the [SharePoint Agent Installation](/docs/accessanalyzer/11.6/install/sharepointagent/overview.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/spaa/bulkimportsettings.md b/docs/accessanalyzer/11.6/admin/datacollector/spaa/bulkimportsettings.md index a2f25fcd5f..c82dc8f231 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/spaa/bulkimportsettings.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/spaa/bulkimportsettings.md @@ -6,7 +6,7 @@ sidebar_position: 80 # SPAA: Bulk Import Settings -The Bulk Import Settings page is where the bulk import process settings are configured. It is a +Use the Bulk Import Settings page to configure the bulk import process settings. It's a wizard page for the categories of: - Bulk Import Access Scan Results @@ -15,6 +15,6 @@ wizard page for the categories of: ![Bulk Import Settings page](/images/accessanalyzer/11.6/admin/datacollector/spaa/bulkimportsettings.webp) Subsequent hosts in job lists will get host IDs incremented by 1. The Host Identifier may require an -offset to avoid overlapping IDs in collected data. If the **Set Host ID** checkbox is left -unchecked, then Enterprise Auditor assigns values starting from 1 to every host. This feature is +offset to avoid overlapping IDs in collected data. If you leave the **Set Host ID** checkbox +unchecked, Enterprise Auditor assigns values starting from 1 to every host. This feature is intended only for SQL Server Replication. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/spaa/category.md b/docs/accessanalyzer/11.6/admin/datacollector/spaa/category.md index cc9944b76a..7a9bafb111 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/spaa/category.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/spaa/category.md @@ -30,7 +30,7 @@ The options on the Category page are: Auditor database :::tip -Remember, the sensitive data discovery options require the Sensitive Data Discovery Add-On to be -installed on the Enterprise Auditor Console. If the SharePoint Agent is used, then it must also be -installed on the application server that hosts the Central Administration component. +Remember, the sensitive data discovery options require you to install the Sensitive Data Discovery +Add-On on the Enterprise Auditor Console. If you use the SharePoint Agent, you must also install it +on the application server that hosts the Central Administration component. ::: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/spaa/configurejob.md b/docs/accessanalyzer/11.6/admin/datacollector/spaa/configurejob.md index 4aca22f190..09569531db 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/spaa/configurejob.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/spaa/configurejob.md @@ -6,12 +6,12 @@ sidebar_position: 20 # SharePoint Custom Connection Profile & Host List -The SPAA Data Collector requires a custom Connection Profile and a custom host list to be created -and assigned to the job conducting the data collection. The host inventory option during host list -creation makes it necessary to configure the Connection Profile first. While SharePoint on-premises -uses the Active Directory account type for the credential within a Connection Profile, it is -necessary for online credentials to be listed first in the credentials list within a Connection -Profile housing credentials to both environments. +The SPAA Data Collector requires you to create a custom Connection Profile and a custom host list +and assign them to the job conducting the data collection. The host inventory option during host +list creation makes it necessary to configure the Connection Profile first. While SharePoint +on-premises uses the Active Directory account type for the credential within a Connection Profile, +you must list online credentials first in the credentials list within a Connection Profile housing +credentials to both environments. ## SharePoint Farm @@ -25,17 +25,17 @@ The provisioned credential used should be an Active Directory account. Create a Connection Profile and set the following information on the User Credentials window: - Select Account Type – Active Directory Account -- Domain – Drop-down menu with available trusted domains displays. Either type the short domain name +- Domain – dropdown menu with available trusted domains displays. Either enter the short domain name in the textbox or select a domain from the menu. -- User name – Type the user name +- User name – Enter the user name - Password Storage – Choose the for credential password storage: - Application – Uses Enterprise Auditor’s configured Profile Security setting as selected at the **Settings** > **Application** node - CyberArk – Uses the CyberArk Enterprise Password Vault -- Password – Type the password -- Confirm – Re-type the password +- Password – Enter the password +- Confirm – Re-enter the password -Once the Connection Profile is created, it is time to create the custom host list. See the +After you create the Connection Profile, create the custom host list. See the [Connection](/docs/accessanalyzer/11.6/admin/settings/connection/overview.md) topic for additional information. @@ -44,7 +44,7 @@ topic for additional information. The custom host list should include: - One application server per farm -- Host name without a domain suffix, this means the host name should not contain a period character +- Host name without a domain suffix, this means the host name shouldn't contain a period character See the [Add Hosts](/docs/accessanalyzer/11.6/admin/hostmanagement/actions/add.md) @@ -91,14 +91,14 @@ Create a Connection Profile and set the following information on the User Creden (x86)\STEALTHbits\StealthAUDIT\PrivateAssemblies\spaa_cert_myorg.pfx,PasswordGoesHere,0 :::note - `PasswordGoesHere` should be replaced with the password used when generating the + Replace `PasswordGoesHere` with the password used when generating the self-signed X.509 certificate if the Microsoft Entra ID Application was Registered and - Provisioned manually or the $appPassword parameter used in the SP_RegisterAzureAppAuth Instant - Job if that method was used. + Provisioned manually, or with the $appPassword parameter used in the SP_RegisterAzureAppAuth + Instant Job if that method was used. ::: -Once the Connection Profile is created, it is time to create the custom host list. See the +After you create the Connection Profile, create the custom host list. See the [Connection](/docs/accessanalyzer/11.6/admin/settings/connection/overview.md) topic for additional information. @@ -106,11 +106,11 @@ topic for additional information. The custom host list should include: -- Web or cloud hosts should be specified using the full web DNS part of the site URL, for example an - Office 365 site with the URL http://TestSite.sharepoint.com should be added as a host with name +- Specify web or cloud hosts using the full web DNS part of the site URL. For example, add an + Office 365 site with the URL http://TestSite.sharepoint.com as a host named TestSite.sharepoint.com -- Do not use the admin site, for example TestSite-admin.sharepoint.com -- Do not use IP Addresses +- Don't use the admin site, for example TestSite-admin.sharepoint.com +- Don't use IP Addresses - Host name must be in DNS format See the diff --git a/docs/accessanalyzer/11.6/admin/datacollector/spaa/dlpauditsettings.md b/docs/accessanalyzer/11.6/admin/datacollector/spaa/dlpauditsettings.md index 371f8995f1..89ddb04e10 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/spaa/dlpauditsettings.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/spaa/dlpauditsettings.md @@ -6,14 +6,14 @@ sidebar_position: 90 # SPAA: DLP Audit Settings -The DLP Audit Settings page is where sensitive data discovery settings are configured. It is a -wizard page for the category of Scan For Sensitive Content. +Use the DLP Audit Settings page to configure sensitive data discovery settings. It's a wizard page +for the category of Scan For Sensitive Content. :::warning -Users should not change scans in a way that would result in less data being returned on -a subsequent scan (i.e. scanning fewer web applications, scanning fewer site collections, or a -shallower depth scan). Those resources not included in a subsequent scan are marked as deleted in -the Tier 2 database and subsequently removed from the Tier 1 database. +Don't change scans in a way that results in a subsequent scan returning less data (for example, +scanning fewer web applications, scanning fewer site collections, or using a shallower depth scan). +Enterprise Auditor marks resources not included in a subsequent scan as deleted in the Tier 2 +database and subsequently removes them from the Tier 1 database. ::: @@ -21,11 +21,11 @@ the Tier 2 database and subsequently removed from the Tier 1 database. Configure the **Scan Performance** options: -- Don’t process files larger than: Size Limit [number] MB – Limits the files to be scanned for +- Don’t process files larger than: Size Limit [number] MB – Limits the files scanned for sensitive content to only files smaller than the specified size. The checkbox is selected by default. The default size is 2 MB. - Number of SDD scan processes [number] – Increases the number of SDD scanner processes that spawn - as part of a scan, increasing parallel scanning. The value should not exceed 2x the number of CPU + as part of a scan, increasing parallel scanning. The value shouldn't exceed 2x the number of CPU threads available. Use the radio buttons to select the **File types to scan**: @@ -46,13 +46,13 @@ Use the radio buttons to select the **File types to scan**: Use the checkboxes to select to **Store Match Hits**: - Store discovered sensitive data – Stores match hits for sensitive data in the SPAA Tier 2 - database. If this option is not selected, then the match hits for sensitive data are still - reported but the data columns are masked in the database. -- Limit stored matches per criteria to [number] – Enabled when the Store discovered sensitive data - checkbox is selected. Limits the number of stored matches per criteria to the specified number. + database. If you don't select this option, Enterprise Auditor still reports the match hits for + sensitive data but masks the data columns in the database. +- Limit stored matches per criteria to [number] – Available when you select the Store discovered + sensitive data checkbox. Limits the number of stored matches per criteria to the specified number. :::tip -Remember, the sensitive data discovery options require the Sensitive Data Discovery Add-On to be -installed on the Enterprise Auditor Console. If the SharePoint Agent is used, then it must also be -installed on the application server that hosts the Central Administration component. +Remember, the sensitive data discovery options require you to install the Sensitive Data Discovery +Add-On on the Enterprise Auditor Console. If you use the SharePoint Agent, you must also install it +on the application server that hosts the Central Administration component. ::: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/spaa/droptables.md b/docs/accessanalyzer/11.6/admin/datacollector/spaa/droptables.md index 3ad886496a..aec4a70137 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/spaa/droptables.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/spaa/droptables.md @@ -10,7 +10,7 @@ If it becomes necessary to clear the SPAA Data Collector tables and views to res SP_DropTables Job is preconfigured to run analysis tasks that drop functions and views for the SharePoint Solution as well as the standard tables and views generated by the **SPAA** Data Collector. It is available through the Instant Job Library under the SharePoint library. Since this -job does not require a host to target, select **Local host** on the Hosts page of the Enterprise +job doesn't require a host to target, select **Local host** on the Hosts page of the Enterprise Auditor Instant Job Wizard. See the [Instant Job Wizard](/docs/accessanalyzer/11.6/admin/jobs/instantjobs/overview.md) topic for additional information. @@ -38,10 +38,10 @@ The default analysis tasks are: - **4. Drop SPAA Tables** – Drops the SharePoint Access Auditing tables imported from the previous runs -Do not try to run these tasks separately, as they are designed to work together. Follow these steps +Don't try to run these tasks separately, as they are designed to work together. Follow these steps to run the analysis tasks: -**Step 1 –** In the Analysis Selection Pane, click **Select All**. All tasks will be checked. +**Step 1 –** In the Analysis Selection Pane, click **Select All** to check all tasks. **Step 2 –** Right-click the **SP_DropTables** Job and select **Run Job**. The analysis execution status will be visible from the **Running Jobs** node. @@ -50,9 +50,9 @@ status will be visible from the **Running Jobs** node. All** to deselect these analysis tasks. :::info -Do not leave these analysis tasks checked in order to avoid accidental data loss. +Don't leave these analysis tasks checked to avoid accidental data loss. ::: -All of these tables have been dropped from the SQL Server database and the data is no longer -available. +The tasks have now dropped all of these tables from the SQL Server database, and the data is no +longer available. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/spaa/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/spaa/overview.md index 59cf7b9152..2174838b2a 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/spaa/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/spaa/overview.md @@ -7,8 +7,8 @@ sidebar_position: 330 # SharePointAccess Data Collector The SharePointAccess (SPAA) Data Collector audits access, group membership, and content within a -SharePoint on-premises and SharePoint Online environment. The SPAA Data Collector has been -preconfigured within the SharePoint Solution. Both this data collector and the solution are +SharePoint on-premises and SharePoint Online environment. The SharePoint Solution includes the SPAA +Data Collector as a preconfigured component. Both this data collector and the solution are available with a special Enterprise Auditor license. See the [SharePoint Solution](/docs/accessanalyzer/11.6/solutions/sharepoint/overview.md) topic for additional information. The SPAA Data Collector has the following requirements: @@ -35,15 +35,15 @@ topic for additional information. The SPAA Data Collector has the following requ **Sensitive Data Discovery Considerations** -The Sensitive Data Discovery Add-On must be installed on the Enterprise Auditor Console server, -which enables Sensitive Data criteria for scans. If running Sensitive Data Discovery (SDD) scans, it -will be necessary to increase the minimum amount of RAM. Each thread requires a minimum of 2 -additional GB of RAM per host. For example, if the job is configured to scan 8 hosts at a time , -then an extra 16 GB of RAM are required (8x2=16). +You must install the Sensitive Data Discovery Add-On on the Enterprise Auditor Console server, +which enables Sensitive Data criteria for scans. If you run Sensitive Data Discovery (SDD) scans, +you must increase the minimum amount of RAM. Each thread requires a minimum of 2 +additional GB of RAM per host. For example, if you configure the job to scan 8 hosts at a time, +you need an extra 16 GB of RAM (8x2=16). :::tip -Remember, if employing the Enterprise Auditor SharePoint Agent, it is also necessary for the -Sensitive Data Discovery Add-on to be installed on the server where the agent is installed. +Remember, if you use the Enterprise Auditor SharePoint Agent, you must also install the +Sensitive Data Discovery Add-on on the server where the agent is installed. ::: @@ -70,5 +70,5 @@ Category selected: ![SPAA Data Collector Wizard Welcome Page](/images/accessanalyzer/11.6/admin/datacollector/spaa/welcomepage.webp) -The Welcome page can be hidden by checking the **Do not display this page the next time** box when -the wizard is open and configuration settings are saved. +Check the **Don't display this page the next time** box to hide the Welcome page. The wizard saves +this setting with your configuration changes. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/spaa/results.md b/docs/accessanalyzer/11.6/admin/datacollector/spaa/results.md index d8db50e71d..b65fcb9104 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/spaa/results.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/spaa/results.md @@ -6,12 +6,13 @@ sidebar_position: 140 # SPAA: Results -The Results page is where properties that will be gathered are selected. It is a wizard page for all +Use the Results page to select the properties to gather. It's a wizard page for all of the categories. ![Results page](/images/accessanalyzer/11.6/admin/datacollector/spaa/results.webp) -Properties can be checked individually, or the **Select All**and **Clear All** buttons can be used. -All checked properties are gathered. Available properties vary based on the category selected. This -information is not available within the standard reference tables. Instead, this information can be -viewed in the table created by the query task, for example SA_1-SPAA_SystemScans_Access table. +Check properties individually, or use the **Select All** and **Clear All** buttons. +Enterprise Auditor gathers all checked properties. Available properties vary based on the category +selected. This information isn't available within the standard reference tables. Instead, you can +view this information in the table created by the query task, for example the +SA_1-SPAA_SystemScans_Access table. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/spaa/scanscopingoptions.md b/docs/accessanalyzer/11.6/admin/datacollector/spaa/scanscopingoptions.md index 68d1862708..2e72ee88ec 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/spaa/scanscopingoptions.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/spaa/scanscopingoptions.md @@ -6,7 +6,7 @@ sidebar_position: 50 # SPAA: Scan Scoping Options -The Scan Scoping Options page provides scoping options to specify the list of URLs to be scanned. It +The Scan Scoping Options page provides scoping options to specify the list of URLs to scan. It is a wizard page for the categories of: - Scan SharePoint Access @@ -24,19 +24,19 @@ The options on the Scan Scoping Options page are: topic for additional information. :::note - If sites are included in the Scope box, all other sites are excluded from the scan. + If you include sites in the Scope box, the scan excludes all other sites. ::: - Import CSV – Opens a file explorer to browse for a CSV file - Scope box – Lists all added URLs -- Scope drop-down list – Select include to include a URL in the scan. Select exclude to exclude a +- Scope dropdown list – Select include to include a URL in the scan. Select exclude to exclude a URL from the scan. - Remove – Removes the selected URL from the Scope box ## Scoping to SharePoint Host Named Site Collections -In order to scope to objects within host named site collections, add a scope line which includes the +to scope to objects within host named site collections, add a scope line which includes the URL of the web application containing the host named site collection. To scope the host named site collection URL `http://sample.com/documents/` for a host named site collection that exists under the web application URL `http://example.com`, follow the steps: @@ -56,17 +56,17 @@ the HNSCs. Click **Add**. ![Scan Scoping Options example](/images/accessanalyzer/11.6/admin/datacollector/spaa/scanscopingoptionsexample.webp) -**Step 4 –** The Web App URL must appear above the HNSC URL, as depicted in the example above. +**Step 4 –** The Web App URL must appear above the HNSC URL, as depicted in the preceding example. **Step 5 –** The SharePoint Access Auditor Data Collector Wizard is now configured to filter for the URL inside the SharePoint Host Named Site Collections. ## Virtual Hosts -In order to decrease the scan time in large SharePoint Online environments, it is possible to break +To decrease the scan time in large SharePoint Online environments, you can break Site Collections for a single host down into subsets, or **Virtual Hosts**, that are treated as -separate hosts by Enterprise Auditor. This allows multiple scans of a single host to be run -concurrently. Follow the steps to configure this. +separate hosts by Enterprise Auditor. This allows multiple scans of a single host to run +concurrently. To configure this: ![CSV file with host and site collection information](/images/accessanalyzer/11.6/admin/datacollector/spaa/virtualhostscsv.webp) @@ -96,8 +96,8 @@ will also see a separate line on the Running Instances tab for each Virtual Host scan. :::note -The Host List for Bulk Import should be configured to contain each Virtual Host included -in the above scan using the `HOSTNAME#DESIGNATOR` format. After Bulk Import, the data contained in -Tier 1 Database tables and views will resemble a scan run against multiple hosts. +Configure the Host List for Bulk Import to contain each Virtual Host included +in the preceding scan, using the `HOSTNAME#DESIGNATOR` format. After Bulk Import, the data contained +in Tier 1 Database tables and views resembles a scan run against multiple hosts. ::: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/spaa/selectdlpcriteria.md b/docs/accessanalyzer/11.6/admin/datacollector/spaa/selectdlpcriteria.md index b2ee467545..7c798c8c34 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/spaa/selectdlpcriteria.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/spaa/selectdlpcriteria.md @@ -6,19 +6,19 @@ sidebar_position: 100 # SPAA: Select DLP Criteria -The Select Criteria page is where criteria to be used for discovering sensitive data are configured. -It is a wizard page for the category of Scan For Sensitive Content. This page requires the Sensitive -Data Discovery Add-On to be been installed on the Enterprise Auditor Console to define the criteria -and enable the Criteria Editor. If the SharePoint Agent is used, then it must also be installed on +Use the Select Criteria page to configure the criteria for discovering sensitive data. +It's a wizard page for the category of Scan For Sensitive Content. This page requires you to +install the Sensitive Data Discovery Add-On on the Enterprise Auditor Console to define the criteria +and enable the Criteria Editor. If you use the SharePoint Agent, you must also install it on the application server that hosts the Central Administration component. See the [Sensitive Data Discovery Add-On Installation](/docs/accessanalyzer/11.6/install/sensitivedatadiscovery/overview.md) topic for additional information. :::warning -Users should not change scans in a way that would result in less data being returned on -a subsequent scan (i.e. scanning fewer web applications, scanning fewer site collections, or a -shallower depth scan). Those resources not included in a subsequent scan are marked as deleted in -the Tier 2 database and subsequently removed from the Tier 1 database. +Don't change scans in a way that results in a subsequent scan returning less data (for example, +scanning fewer web applications, scanning fewer site collections, or using a shallower depth scan). +Enterprise Auditor marks resources not included in a subsequent scan as deleted in the Tier 2 +database and subsequently removes them from the Tier 1 database. ::: @@ -34,8 +34,8 @@ The options on the Select DLP Criteria page are: data criteria to scan for - Select All - Click **Select All** to enable all sensitive data criteria for scanning - Clear All - Click **Clear All** to remove all selections from the table -- Check the boxes next to the sensitive data criteria options to enable it to be scanned for during - job execution +- Check the boxes next to the sensitive data criteria options to enable the query to scan for them + during job execution The table contains the following types of criteria: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/spaa/settings.md b/docs/accessanalyzer/11.6/admin/datacollector/spaa/settings.md index af9a25ea5e..00a6d6f9b5 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/spaa/settings.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/spaa/settings.md @@ -6,51 +6,52 @@ sidebar_position: 40 # SPAA: SharePoint Data Collection Settings -The SharePoint data collection settings page is where additional scan settings are configured. It is +Use the SharePoint data collection settings page to configure additional scan settings. It's a wizard page for the categories of: - Scan SharePoint Access - Scan For Sensitive Content :::warning -Users should not change scans in a way that would result in less data being returned on -a subsequent scan (i.e. scanning fewer web applications, scanning fewer site collections, or a -shallower depth scan). Those resources not included in a subsequent scan are marked as deleted in -the Tier 2 database and subsequently removed from the Tier 1 database. +Don't change scans in a way that results in a subsequent scan returning less data (for example, +scanning fewer web applications, scanning fewer site collections, or using a shallower depth scan). +Enterprise Auditor marks resources not included in a subsequent scan as deleted in the Tier 2 +database and subsequently removes them from the Tier 1 database. ::: ![SharePoint data collection settings page](/images/accessanalyzer/11.6/admin/datacollector/spaa/datacollectionsettings.webp) -The Probable Owners section provides options for how probable ownership will be calculated: +The Probable Owners section provides options for how Enterprise Auditor calculates probable +ownership: - Limit maximum number of Probable Owners per resource: [number] – Return the maximum user supplied number of probable owners per resource The Collect Personal Sites checkbox enables or disables collection during the scan of personal site -collections of individual users. Personal site collections are a SharePoint feature which gives -every user their own site collection, and which are used by Office 365 to store a user’s OneDrive -files. Personal sites are configured by default to only be accessible by the user to whom they -belong, and so it is likely that the Connection Profile that the data collector is assigned may not -have access to some users’ personal sites. There are three radio buttons for identifying how the -query treats personal sites to which it does not have access: - -- Skip inaccessible personal sites – Inaccessible personal sites are not scanned +collections of individual users. Personal site collections are a SharePoint feature that gives +every user their own site collection, and Office 365 uses them to store a user's OneDrive +files. By default, only the user to whom a personal site belongs can access it, so the Connection +Profile that the data collector is assigned may not have access to some users' personal sites. There +are three radio buttons for identifying how the +query treats personal sites to which it doesn't have access: + +- Skip inaccessible personal sites – The query doesn't scan inaccessible personal sites - Force scan account as admin of inaccessible personal sites – Make the Connection Profile - credentials a Site Collection Administrator of any personal sites to which it does not have + credentials a Site Collection Administrator of any personal sites to which it doesn't have access: - - The personal sites will be scanned - - When the scan is complete, the permissions are restored to what they were prior to the scan, - referring to those credentials made a Site Collection Administrator of personal sites in order - to conduct the scan. + - The query scans the personal sites + - When the scan is complete, Enterprise Auditor restores the permissions to what they were + before the scan, referring to those credentials made a Site Collection Administrator of + personal sites in order to conduct the scan. - Requires the account used in the Connection Profile credentials to have the Global Administrator role for SharePoint Online or be a Farm Administrator for SharePoint on premise. This permission is required to facilitate altering the administrators of site collections. :::note - The Microsoft SharePoint API employed to remove personal Site Collection - Administrator is unreliable, and occasionally the scanning account is left as a Site + The Microsoft SharePoint API used to remove personal Site Collection + Administrator access is unreliable and occasionally leaves the scanning account as a Site Collection Administrator of personal sites. This may leave the scanning account visible to SharePoint users on the permissions of the files in their personal sites. ::: @@ -58,17 +59,17 @@ query treats personal sites to which it does not have access: :::info Only use this option if that account is clearly identifiable as an - administrative account, and users are advised of the possibility that the account could - appear on the permissions of their personal site collection documents. + administrative account, and advise users that the account could appear on the permissions + of their personal site collection documents. ::: - Force Company Administrator as admin of inaccessible personal sites – Make the special Company - Administrator account an administrator of any personal sites to which it does not have access + Administrator account an administrator of any personal sites to which it doesn't have access - - The personal sites will be scanned - - When the scan is complete, the Company Administrator account is left as an administrator of - the users’ personal site collections + - The query scans the personal sites + - When the scan is complete, the Company Administrator account remains an administrator of + the users' personal site collections - Requires the account used in the Connection Profile credentials to have the Global Administrator role for SharePoint Online or be a Farm Administrator for SharePoint on premise. This permission is required to facilitate altering the administrators of site collections. @@ -80,11 +81,11 @@ query treats personal sites to which it does not have access: The **Extract Document Tags** option enables the collection of metadata tags from Microsoft Office -files in SharePoint. Since this option requires the retrieval and scanning of each document, it +files in SharePoint. Since this option requires retrieving and scanning each document, it results in a noticeable increase in scan time. -- Select a preferred zone – Use the drop-down list to select a preferred zone within the web - application to target the scan. If a targeted web application does not have the selected preferred +- Select a preferred zone – Use the dropdown list to select a preferred zone within the web + application to target the scan. If a targeted web application doesn't have the selected preferred zone, the scan targets the default zone for that web application. Options include: - Default diff --git a/docs/accessanalyzer/11.6/admin/datacollector/spaa/standardtables.md b/docs/accessanalyzer/11.6/admin/datacollector/spaa/standardtables.md index 603a9528c6..65b7b9427b 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/spaa/standardtables.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/spaa/standardtables.md @@ -30,7 +30,7 @@ The tables and their associated views are grouped by types. | Tables | Details | | --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| SA_SPAA_Trustees | Contains information about any domain user, group, or security principal that has been assigned permissions. This table does not contain local user and groups, as none of the trustees in this table are specific to any one host. | +| SA_SPAA_Trustees | Contains information about any domain user, group, or security principal that has been assigned permissions. This table doesn't contain local user and groups, as none of the trustees in this table are specific to any one host. | | SA_SPAA_TrusteeGroupMembers | Table contains information on SharePoint group membership. | **Access Calculation Tables** @@ -46,7 +46,7 @@ The tables and their associated views are grouped by types. | Tables | Details | | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| SA_SPAA_Exceptions | Contains information about security issues and concerns. One out-of-the-box exception stored inside this table is the Open Resource exception, which identifies where resources are open to Everyone, Authenticated Users, or Domain Users. | +| SA_SPAA_Exceptions | Contains information about security issues and concerns. One built-in exception stored inside this table is the Open Resource exception, which identifies where resources are open to Everyone, Authenticated Users, or Domain Users. | | SA_SPAA_ExceptionTypes | Contains summary information about exceptions. It details how many exceptions are found on each host scanned and breaks them down by exception type. | **Content Tables** diff --git a/docs/accessanalyzer/11.6/admin/datacollector/spaa/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/spaa/summary.md index bcf573f3be..3ff75a4218 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/spaa/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/spaa/summary.md @@ -11,6 +11,6 @@ categories. **-![Summary Page](/images/accessanalyzer/11.6/admin/datacollector/spaa/summarypage.webp)** -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the SharePoint Access Auditor Data Collector Wizard ensuring that no -accidental clicks are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** to close +the SharePoint Access Auditor Data Collector Wizard instead. This prevents the wizard from saving +accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/spaa/testaccess.md b/docs/accessanalyzer/11.6/admin/datacollector/spaa/testaccess.md index ec8d45dc04..0ec0da31dc 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/spaa/testaccess.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/spaa/testaccess.md @@ -22,12 +22,12 @@ The options and sections on the Test Access page are: Server text box. Click **Check Access** to test access to the SharePoint environment. - For example – `sbnjqasp30` or `sbnjqasp3.qa.com` - - Do not include `http[s]://` or use a URL for the server name. The Test Access function cannot - be scoped to individual Web applications. + - Don't include `http[s]://` or use a URL for the server name. You can't scope the Test + Access function to individual Web applications. - Access Test Results – Displays information on test results. Test criteria are listed in the - **Description** column. Test results will be returned as either **Pass** or **Fail** in the - Results column. + **Description** column. The Test Access page returns test results as either **Pass** or **Fail** + in the Results column. - Save Report – Click **Save Report** to export and save a text version of the test results | | | diff --git a/docs/accessanalyzer/11.6/admin/datacollector/sql/category.md b/docs/accessanalyzer/11.6/admin/datacollector/sql/category.md index 61c462800e..909873c070 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/sql/category.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/sql/category.md @@ -26,8 +26,8 @@ The query categories are: - Sensitive Data Collection – Scan databases for sensitive data :::note - The Sensitive Data category options require the Sensitive Data Discovery Add-on to - have been installed on the Enterprise Auditor Console before the SQL Data Collector can collect + The Sensitive Data category options require you to install the Sensitive Data Discovery Add-on + on the Enterprise Auditor Console before the SQL Data Collector can collect sensitive data. See the [Sensitive Data Discovery Add-On Installation](/docs/accessanalyzer/11.6/install/sensitivedatadiscovery/overview.md) topic for additional information. @@ -100,7 +100,7 @@ The query categories are: - Latest Week Backup – Information about the latest week backup - Oldest and Newest Backup – Information about the oldest and the most recent backups - - Database File Without Backup – Indicates file names of the files that are not present in + - Database File Without Backup – Indicates file names of the files that aren't present in the RMAN backup - Utilities diff --git a/docs/accessanalyzer/11.6/admin/datacollector/sql/configurejob.md b/docs/accessanalyzer/11.6/admin/datacollector/sql/configurejob.md index 113c0393a2..855b3f62b2 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/sql/configurejob.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/sql/configurejob.md @@ -6,8 +6,8 @@ sidebar_position: 10 # SQL Custom Connection Profile & Default Dynamic Host List -The SQL Data Collector requires a custom Connection Profile and Host List. The **SQL SERVERS** -default host list can be used with this data collector for the SQL Solution. The host inventory +The SQL Data Collector requires a custom Connection Profile and Host List. You can use the +**SQL SERVERS** default host list with this data collector for the SQL Solution. The host inventory option during host list creation makes it necessary to configure the Connection Profile first. ## Connection Profile @@ -17,10 +17,10 @@ Create a Connection Profile and set the following information on the User Creden - For an Active Directory account: - Select Account Type – Active Directory Account - - Domain – Drop-down menu with available trusted domains will appear. Either type the short + - Domain – dropdown menu with available trusted domains will appear. Either enter the short domain name in the textbox or select a domain from the menu. - - User name – Type the user name - - Password Storage – Choose the desired option for credential password storage: + - User name – Enter the user name + - Password Storage – Choose the option you want for credential password storage: - Application – Uses the configured Profile Security setting as selected at the **Settings** > **Application** node. See the @@ -28,11 +28,11 @@ Create a Connection Profile and set the following information on the User Creden topic for additional information. - CyberArk – Uses the CyberArk Enterprise Password Vault. See the [CyberArk Integration](/docs/accessanalyzer/11.6/admin/settings/connection/cyberarkintegration.md) - topic for additional information. The password fields do not apply for CyberArk password + topic for additional information. The password fields don't apply for CyberArk password storage. - - Password – Type the password - - Confirm – Re-type the password + - Password – Enter the password + - Confirm – Re-enter the password - For a SQL account: @@ -42,8 +42,8 @@ Create a Connection Profile and set the following information on the User Creden the **Settings** > **Application** node. See the [Application](/docs/accessanalyzer/11.6/admin/settings/application/overview.md) topic for additional information.) - - Password – Type the password - - Confirm – Re-type the password + - Password – Enter the password + - Confirm – Re-enter the password See the [Connection](/docs/accessanalyzer/11.6/admin/settings/connection/overview.md) @@ -51,27 +51,28 @@ topic for additional information. ## Host List -The required host list depends on the database that the SQL data collector is being used for. +The required host list depends on the database for which you're using the SQL data collector. ### Default Dynamic Host List (SQL) Jobs using the SQL Data Collector can use the SQL Servers default host list. This is a dynamic host -list that is populated from hosts in the Host Master Table which meet the host inventory criteria -for the list, `IsSQLServer = True`. Since the SQL Servers host list is default, it is available to +list that Enterprise Auditor populates from hosts in the Host Master Table that meet the host +inventory criteria for the list, `IsSQLServer = True`. Since the SQL Servers host list is default, +it is available to jobs and job groups for host assignment. See the [Host Management](/docs/accessanalyzer/11.6/admin/hostmanagement/overview.md) topic for additional information. ### Oracle / MySQL / PostgreSQL / Db2 -Jobs in the Oracle, MySQL, Postgre SQL, or Db2 solution using the SQL Data Collector must be -configured to query a host list with the servers containing the target databases. Setup the list of -hosts that needs to be monitored. Be sure to use a specific host name (if forcing the connection to +You must configure jobs in the Oracle, MySQL, Postgre SQL, or Db2 solution that use the SQL Data +Collector to query a host list with the servers containing the target databases. Set up the list of +hosts you need to monitor. Be sure to use a specific host name (if forcing the connection to a secondary host) or just the server name if connecting to the server. See the [Host Management](/docs/accessanalyzer/11.6/admin/hostmanagement/overview.md) topic for additional information. -Additionally, the database instances must be added to the Filter page in the query configuration. +Additionally, you must add the database instances to the Filter page in the query configuration. See the [SQL: Filter](/docs/accessanalyzer/11.6/admin/datacollector/sql/filter.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/sql/criteria.md b/docs/accessanalyzer/11.6/admin/datacollector/sql/criteria.md index 9afa0ffc98..f7e87e8589 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/sql/criteria.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/sql/criteria.md @@ -6,10 +6,10 @@ sidebar_position: 40 # SQL: Criteria -The Criteria page is where criteria to be used for discovering sensitive data are configured. It is +Use the Criteria page to configure the criteria for discovering sensitive data. It's a wizard page for the Sensitive Data Collection category. -This page requires the Sensitive Data Discovery Add-On to be installed on the Enterprise Auditor +This page requires you to install the Sensitive Data Discovery Add-On on the Enterprise Auditor Console to define the criteria and enable the Criteria Editor. See the [Sensitive Data Discovery Add-On Installation](/docs/accessanalyzer/11.6/install/sensitivedatadiscovery/overview.md) topic for additional information. @@ -27,8 +27,8 @@ The options on the Criteria page are: - Select All– Click **Select All** to enable all sensitive data criteria for scanning - Clear All – Click **Clear All** to remove all selections from the table - - Select the checkboxes next to the sensitive data criteria options to enable it to be scanned - for during job execution + - Select the checkboxes next to the sensitive data criteria options to enable the query to scan + for them during job execution The table contains the following types of criteria: @@ -48,7 +48,7 @@ Criteria and User Criteria nodes are visible in the table. :::note Adding unnecessary criteria can adversely impact the scanner performance and can cause the -scanning job to take a long time. If performance is adversely affected, revisit the sensitive data -scanning criteria and remove criteria that is not required. +scanning job to take a long time. If unnecessary criteria adversely affect performance, revisit the +sensitive data scanning criteria and remove criteria that isn't required. ::: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/sql/customqueryoracle.md b/docs/accessanalyzer/11.6/admin/datacollector/sql/customqueryoracle.md index 5a8cfa00b3..61fb085415 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/sql/customqueryoracle.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/sql/customqueryoracle.md @@ -16,8 +16,8 @@ The configurable options are: - Test Database: - - Data Source – Select the host\instance from the drop-down menu - - Database – Select the database from the drop-down menu + - Data Source – Select the host\instance from the dropdown menu + - Database – Select the database from the dropdown menu - Convert CDB to DBA on non-container databases diff --git a/docs/accessanalyzer/11.6/admin/datacollector/sql/customquerysql.md b/docs/accessanalyzer/11.6/admin/datacollector/sql/customquerysql.md index 13d2a62dbc..d151d50a34 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/sql/customquerysql.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/sql/customquerysql.md @@ -20,8 +20,8 @@ The configurable options are: - Test Database: - - Data Source – Select the host\instance from the drop-down menu - - Database – Select the database from the drop-down menu + - Data Source – Select the host\instance from the dropdown menu + - Database – Select the database from the dropdown menu - SQL Query textbox – Enter the custom SQL script - Validate Query – Click to test the query, results display in the box diff --git a/docs/accessanalyzer/11.6/admin/datacollector/sql/filter.md b/docs/accessanalyzer/11.6/admin/datacollector/sql/filter.md index 74144f6a52..9615661ea4 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/sql/filter.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/sql/filter.md @@ -6,7 +6,7 @@ sidebar_position: 50 # SQL: Filter -The Filter page is where the query can be scoped to target specific databases or instances. It is a +Use the Filter page to scope the query to target specific databases or instances. It's a wizard page for the categories of: - Permissions > Permissions Collection @@ -46,14 +46,14 @@ wizard page for the categories of: - Utilities – Remove Storage Data -It is necessary for the SA_SQL_Instances table to be populated before available databases/instances -can populate the Available Server audits list. For Oracle and SQL, the SA_SQL_Instances table is -populated through an instance discovery query. See the +You must populate the SA_SQL_Instances table before available databases/instances can populate the +Available Server audits list. For Oracle and SQL, an instance discovery query populates the +SA_SQL_Instances table. See the [0-SQL_InstanceDiscovery Job](/docs/accessanalyzer/11.6/solutions/databases/sql/collection/0-sql_instancediscovery.md) -topic for additional information. For PostgreSQL and MySQL Scans, the SA_SQL_Instances table is -populated manually in the Manage Connections window. See the -[Manage Connections Window](#manage-connections-window) topic for additional information. Once the -table has been populated, a query can be scoped. +topic for additional information. For PostgreSQL and MySQL scans, you populate the +SA_SQL_Instances table manually in the Manage Connections window. See the +[Manage Connections Window](#manage-connections-window) topic for additional information. After you +populate the table, you can scope a query. ![SQL Data Collector Wizard Filter page](/images/accessanalyzer/11.6/admin/datacollector/sql/filter.webp) @@ -72,13 +72,13 @@ The configurable filter options are: - Select from the available list and click **Add** -- Selected databases or instances — Displays selected database objects for which the query has been - scoped. Additional options include: +- Selected databases or instances — Displays selected database objects the query is scoped to. + Additional options include: - Remove — Removes the selected database/instance from the query - Include — Reverts an exclusion. By default, all sub tables are included. - Exclude — Excludes selected databases/instances and displays them in red - - Add Custom Filter — Opens the Add custom filter window to build a custom filter to be applied + - Add Custom Filter — Opens the Add custom filter window to build a custom filter to apply to the selected databases/instances. See the [Add Custom Filter Window](#add-custom-filter-window) topic for additional information. - Import CSV — Import a list of databases/instances from a CSV file @@ -86,7 +86,7 @@ The configurable filter options are: ## Manage Connections Window -The Manage Connections window enables you to add database instances to search. Click the +Use the Manage Connections window to add database instances to search. Click the **Connections** button to open it. ![Manage Connections window](/images/accessanalyzer/11.6/admin/datacollector/sql/manageconnections.webp) @@ -99,8 +99,8 @@ Select a row in the table to edit that instance, or create a new instance to add - Database System — Select from a list of available databases - Service Name — Name of the service - Host — Name or IP address of the host where the database is located -- Port Number — Port number for the database. If a non-default port is being used, it should be - specified in the Port Number section. +- Port Number — Port number for the database. If you use a non-default port, specify it in the + Port Number section. - Default Database — Account used to access the database. Admin is recommended. - Enable impersonation — Select to enable impersonation - Service Type— If applicable, select whether the service type is **Service** or **SID** @@ -127,7 +127,7 @@ you to apply a custom scoping filter to the query. ![Add custom filter window](/images/accessanalyzer/11.6/admin/datacollector/sql/addcustomfilter.webp) -Type the filter in the window and click Save. The following characters can be used in the filter: +Enter the filter in the window and click Save. You can use the following characters in the filter: - Forward slash (/) – Path separator - Asterisk (\*) – Wild card for any combination of characters diff --git a/docs/accessanalyzer/11.6/admin/datacollector/sql/options.md b/docs/accessanalyzer/11.6/admin/datacollector/sql/options.md index 340fc17edf..1eb7d78ebc 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/sql/options.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/sql/options.md @@ -76,11 +76,12 @@ The sensitive data scan settings are: **SDD Options** - Store discovered sensitive data – Stores potentially sensitive data in the Enterprise Auditor - database. Any sampled sensitive data discovered based on the matched criteria is stored in the - Enterprise Auditor database. This functionality can be disabled by clearing this option. + database. Enterprise Auditor stores any sampled sensitive data discovered based on the matched + criteria in the Enterprise Auditor database. You can disable this functionality by clearing this + option. :::note - The **Store discovered sensitive data** option is required to view Content Audit + You must enable the **Store discovered sensitive data** option to view Content Audit reports in the Access Information Center for SQL data. ::: @@ -91,10 +92,9 @@ The sensitive data scan settings are: ::: -- Resume scan from last point on error – Resumes scan from where the previous scan left off when the - previous scan was stopped as a result of an error +- Resume scan from last point on error – Resumes scan from where the previous scan left off if an + error stopped the previous scan :::tip -Remember, the Sensitive Data Discovery Add-on is required to use the sensitive data collection -option. +Remember, using the sensitive data collection option requires the Sensitive Data Discovery Add-on. ::: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/sql/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/sql/overview.md index 69cbc51c77..122a1ef6ad 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/sql/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/sql/overview.md @@ -11,9 +11,9 @@ application name of the application responsible for activity events, an IP Addre the client server, and sensitive data reports. This data collector also provides information on Oracle databases including infrastructure and operations. -The SQL Data Collector has been preconfigured within the Database data collection jobs for Db2, -MySQL, Oracle, PostgreSQL, Redshift, and SQL Server databases. Both this data collector and the -Database Solution are available with a special Enterprise Auditor license. See the following topics +The Database data collection jobs for Db2, MySQL, Oracle, PostgreSQL, Redshift, and SQL Server +databases include the SQL Data Collector as a preconfigured component. Both this data collector +and the Database Solution are available with a special Enterprise Auditor license. See the following topics for additional information: - [Db2 Solution](/docs/accessanalyzer/11.6/solutions/databases/db2/overview.md) @@ -84,8 +84,8 @@ For SQL: - For permissions for data collection: - Read access to SQL instance - - Requires SQL Full-Text and Semantic Extractions for Search feature to be installed on the - target SQL instance(s) when using the **Scan full rows for sensitive data** option on the + - Requires you to install the SQL Full-Text and Semantic Extractions for Search feature on the + target SQL instances when using the **Scan full rows for sensitive data** option on the Options wizard page - Grant Authenticate Server to [DOMAIN\USER] - Grant Connect SQL to [DOMAIN\USER] @@ -102,11 +102,11 @@ topic for additional information. **Sensitive Data Discovery Considerations** -The Sensitive Data Discovery Add-On must be installed on the Enterprise Auditor Console server, -which enables Sensitive Data criteria for scans. If running Sensitive Data Discovery (SDD) scans, it -will be necessary to increase the minimum amount of RAM. Each thread requires a minimum of 2 -additional GB of RAM per host. For example, if the job is configured to scan 8 hosts at a time , -then an extra 16 GB of RAM are required (8x2=16). +You must install the Sensitive Data Discovery Add-On on the Enterprise Auditor Console server, +which enables Sensitive Data criteria for scans. If you run Sensitive Data Discovery (SDD) scans, +you must increase the minimum amount of RAM. Each thread requires a minimum of 2 +additional GB of RAM per host. For example, if you configure the job to scan 8 hosts at a time, +you need an extra 16 GB of RAM (8x2=16). ## SQL Query Configuration @@ -114,8 +114,8 @@ The SQL Data Collector is configured through the SQL Data Collector Wizard. The following pages, which change based upon the query category selected: :::note -The SQL Data Collector is used in multiple Enterprise Auditor Solutions, and the query -categories used are dependent on the solution. +Enterprise Auditor uses the SQL Data Collector in multiple Solutions, and the query +categories used depend on the solution. ::: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/sql/results.md b/docs/accessanalyzer/11.6/admin/datacollector/sql/results.md index 5340fcf494..a5053b6e51 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/sql/results.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/sql/results.md @@ -6,11 +6,11 @@ sidebar_position: 90 # SQL: Results -The Results page is where the properties that will be gathered are selected. It is a wizard page for +Use the Results page to select the properties to gather. It's a wizard page for all of the categories. ![SQL Data Collector Wizard Results Page](/images/accessanalyzer/11.6/admin/datacollector/sql/results.webp) -Properties can be selected individually, or the **Select All** and **Clear All** buttons can be -used. All selected properties are gathered. Available properties vary based on the category +Select properties individually, or use the **Select All** and **Clear All** buttons. +Enterprise Auditor gathers all selected properties. Available properties vary based on the category selected. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/sql/rowkey.md b/docs/accessanalyzer/11.6/admin/datacollector/sql/rowkey.md index 6d2b828a31..eb1b09b65e 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/sql/rowkey.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/sql/rowkey.md @@ -11,6 +11,6 @@ categories. ![SQL Data Collector Wizard Rowkey Page](/images/accessanalyzer/11.6/admin/datacollector/sql/rowkey.webp) -Properties selected on the Results page are listed. Select the property or properties to act as the -Rowkey. Properties can be selected individually, or the **Select All** and **Clear All** buttons can -be used. +The Rowkey page lists the properties selected on the Results page. Select the property or +properties to act as the Rowkey. Select properties individually, or use the **Select All** and +**Clear All** buttons. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/sql/settings.md b/docs/accessanalyzer/11.6/admin/datacollector/sql/settings.md index 88fa35bb0e..6dda0c7131 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/sql/settings.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/sql/settings.md @@ -11,7 +11,7 @@ instances. It is a wizard page for the category of Utilities. ![SQL Data Collector Wizard Data removal settings Page](/images/accessanalyzer/11.6/admin/datacollector/sql/settings.webp) -Data from the selected categories will be removed from the Enterprise Auditor database: +Enterprise Auditor removes data from the selected categories: - Permissions - Audits diff --git a/docs/accessanalyzer/11.6/admin/datacollector/sql/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/sql/summary.md index f64e2de89e..17de9a7ccf 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/sql/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/sql/summary.md @@ -11,6 +11,5 @@ the categories. ![SQL Data Collector Wizard Summary Page](/images/accessanalyzer/11.6/admin/datacollector/sql/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the SQL Data Collector Wizard ensuring that no accidental clicks are -saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** to close +the SQL Data Collector Wizard instead. This prevents the wizard from saving accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/filetypes.md b/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/filetypes.md index 7cc778c6d7..d6fe2c100f 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/filetypes.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/filetypes.md @@ -6,9 +6,9 @@ sidebar_position: 70 # SystemInfo: File Types -The File Types page is where to enable count file types and specify filename masks if it is desired -to count files of given types. Two properties are generated for every mask provided, one for size -and one for count. It is a wizard page for the category of File Shares. +The File Types page is where you enable counting file types and specify filename masks if you want +to count files of given types. Enterprise Auditor generates two properties for every mask provided, +one for size and one for count. It's a wizard page for the category of File Shares. ![System Info Data Collector Wizard File Types page](/images/accessanalyzer/11.6/admin/datacollector/systeminfo/filetypes.webp) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/jobscope.md b/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/jobscope.md index 3f9ecb0414..a4b4ce07c9 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/jobscope.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/jobscope.md @@ -6,7 +6,7 @@ sidebar_position: 60 # SystemInfo: Job Scope -The Job Scope page is where to select whether or not scoping should be used during execution. It is +The Job Scope page is where you select whether to use scoping during execution. It's a wizard page for the category of File Shares. ![System Info Data Collector Wizard Job Scope page](/images/accessanalyzer/11.6/admin/datacollector/systeminfo/jobscope.webp) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/options.md b/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/options.md index 43caa5f70f..b0f83752ae 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/options.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/options.md @@ -26,11 +26,11 @@ For the File Shares and Open File Shares categories: ![System Info Data Collector Wizard Options page for File Shares category](/images/accessanalyzer/11.6/admin/datacollector/systeminfo/optionsfileshares.webp) Select from the following options to control the depth of processing and the amount of information -to be returned by the query: +the query returns: - Include file level permissions - - Do not collect inherited file permissions + - Don't collect inherited file permissions - Return All Folders @@ -38,7 +38,7 @@ to be returned by the query: - Limit returned subfolders depth to – Specify the number of levels -- Size units for corresponding properties – Select the desired size unit: +- Size units for corresponding properties – Select the size unit you want: - Bytes - KBytes diff --git a/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/overview.md index a65e6d7d40..9ba25f0ca0 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/overview.md @@ -7,8 +7,9 @@ sidebar_position: 360 # SystemInfo Data Collector The SystemInfo Data Collector extracts information from the target system based on the selected -category. The SystemInfo Data Collector is a core component of Enterprise Auditor, but it has been -preconfigured within the Windows Solution. While the data collector is available with all Enterprise +category. The SystemInfo Data Collector is a core component of Enterprise Auditor, and the Windows +Solution includes it as a preconfigured component. While the data collector is available with all +Enterprise Auditor license options, the Windows Solution is only available with a special Enterprise Auditor license. See the [Windows Solution](/docs/accessanalyzer/11.6/solutions/windows/overview.md) @@ -46,5 +47,5 @@ contains the following wizard pages: ![System Info Data Collector Wizard Welcome page](/images/accessanalyzer/11.6/admin/datacollector/systeminfo/welcome.webp) -The Welcome page can be hidden by selecting the **Do not display this page the next time** checkbox -when the wizard is open and configuration settings are saved. +Select the **Don't display this page the next time** checkbox to hide the Welcome page. The wizard +saves this setting with your configuration changes. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/probableowner.md b/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/probableowner.md index 842a0717df..2830bc7a92 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/probableowner.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/probableowner.md @@ -7,7 +7,7 @@ sidebar_position: 40 # SystemInfo: Probable Owner On the Probable Owner page, select options for determining the owner using weighted calculations. -This page is enabled when the **Probable Owner** property is selected on the Results page. +This page becomes available when you select the **Probable Owner** property on the Results page. ![System Info Data Collector Wizard Probable Owner page](/images/accessanalyzer/11.6/admin/datacollector/systeminfo/probableowner.webp) @@ -20,7 +20,7 @@ In the Determine owner section, select from the following options: - Determine owner from Current User - Determine owner from Last User - Custom weights – Select this radio button to use custom weights to determine the probable owner. - These weights can be set by clicking the ellipsis next to the Result weights box to open the + You can set these weights by clicking the ellipsis next to the Result weights box to open the Probable Owner Settings window. ![Custom weights Probable Owner Settings window](/images/accessanalyzer/11.6/admin/datacollector/systeminfo/customweights.webp) @@ -52,7 +52,7 @@ Click **Set Users to Exclude** to open the Probable Owner Settings window: In the Output options section, select from the following options: -- Get the most probable owner(s) +- Get the most probable owners - Get probable owners with relative deviation to the most probable owner – Enables the following option: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/results.md b/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/results.md index 52822df5ac..f544e9c63a 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/results.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/results.md @@ -6,11 +6,11 @@ sidebar_position: 20 # SystemInfo: Results -The Results page is used to select which properties are gathered out of those available for the -category. It is a wizard page for all categories. +Use the Results page to select which properties to gather from those available for the category. +It's a wizard page for all categories. ![System Info Data Collector Wizard Results page](/images/accessanalyzer/11.6/admin/datacollector/systeminfo/results.webp) -Properties can be selected individually or the **Check all**, **Uncheck all**, and **Reset to -defaults** buttons can be used. All selected properties are gathered. Available properties vary -based on the category selected. +Select properties individually, or use the **Check all**, **Uncheck all**, and **Reset to +defaults** buttons. Enterprise Auditor gathers all selected properties. Available properties vary +based on the selected category. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/summary.md index 10bb545f7b..b0f8f779e2 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/summary.md @@ -10,6 +10,6 @@ The Summary page displays a summary of the configured query. It is a wizard page ![System Info Data Collector Wizard Summary page](/images/accessanalyzer/11.6/admin/datacollector/systeminfo/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the System Info Data Collector Wizard ensuring that no accidental clicks -are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** to close +the System Info Data Collector Wizard instead. This prevents the wizard from saving accidental +clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/vipmembership.md b/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/vipmembership.md index 8bedcd8af3..5eec9acea9 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/vipmembership.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/vipmembership.md @@ -7,8 +7,8 @@ sidebar_position: 50 # SystemInfo: VIP Membership The VIP Membership provides the option to add members to a VIP List and exclude them from contact -about probable ownership. Any users can be added to VIP membership. This page is enabled when the -VIPList property is selected on the Results page. +about probable ownership. You can add any users to VIP membership. This page becomes available when +you select the VIPList property on the Results page. ![System Info Data Collector Wizard VIP Membership page](/images/accessanalyzer/11.6/admin/datacollector/systeminfo/vipmembership.webp) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/textsearch/advancedcriteria.md b/docs/accessanalyzer/11.6/admin/datacollector/textsearch/advancedcriteria.md index 8b925f069e..d7f18993e8 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/textsearch/advancedcriteria.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/textsearch/advancedcriteria.md @@ -6,8 +6,8 @@ sidebar_position: 30 # TextSearch: Advanced Criteria -The Advanced Criteria page is displayed if the **Use advanced criteria (instead of simple -criteria)** checkbox is selected on the Search Criteria page. This page provides configuration +The Advanced Criteria page displays if you select the **Use advanced criteria (instead of simple +criteria)** checkbox on the Search Criteria page. This page provides configuration options to specify the text to search for across the entire row of each file or within the specified column in each row. @@ -17,8 +17,8 @@ The configurable options are: - Return Multiple Columns – Return data values in multiple columns - Load Sample Data – Click this button to browse for sample data to test the filters entered. If the - sample data file is large, it is recommended to sample an excerpt of the file to reduce the amount - of time it takes to load the data. + sample data file is large, sample an excerpt of the file to reduce the time it takes to load the + data. - Customize – Click this button to open the Filter builder ![Filter builder window](/images/accessanalyzer/11.6/admin/datacollector/textsearch/filterbuilder.webp) @@ -27,4 +27,4 @@ The configurable options are: [Filtration Dialog](/docs/accessanalyzer/11.6/admin/navigate/datagrid.md#filtration-dialog) topic for information on using the Filter builder. -The filter section cannot be blank. +The filter section can't be blank. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/textsearch/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/textsearch/overview.md index e88a8d5970..d0078f321f 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/textsearch/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/textsearch/overview.md @@ -7,8 +7,9 @@ sidebar_position: 370 # TextSearch Data Collector The TextSearch Data Collector enables searches through text based log files. The TextSearch Data -Collector is a core component of Enterprise Auditor, but it has been preconfigured within the -Windows Solution. While the data collector is available with all Enterprise Auditor license options, +Collector is a core component of Enterprise Auditor, and the Windows Solution includes it as a +preconfigured component. While the data collector is available with all Enterprise Auditor license +options, the Windows Solution is only available with a special Enterprise Auditor license. See the [Windows Solution](/docs/accessanalyzer/11.6/solutions/windows/overview.md) topic for additional information. @@ -40,5 +41,5 @@ contains the following wizard pages: ![Text Search Data Collector Wizard Welcome page](/images/accessanalyzer/11.6/admin/datacollector/textsearch/welcome.webp) -The Welcome page can be hidden by selecting the **Do not display this page the next time** checkbox -when the wizard is open and configuration settings are saved. +Select the **Don't display this page the next time** checkbox to hide the Welcome page. The wizard +saves this setting with your configuration changes. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/textsearch/results.md b/docs/accessanalyzer/11.6/admin/datacollector/textsearch/results.md index 2771955a07..d6c4c431fb 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/textsearch/results.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/textsearch/results.md @@ -6,13 +6,13 @@ sidebar_position: 40 # TextSearch: Results -The Results page is where properties that will be gathered are selected. +Use the Results page to select the properties to gather. ![Text Search Data Collector Wizard Results page](/images/accessanalyzer/11.6/admin/datacollector/textsearch/results.webp) -Properties can be selected individually or the **Check all**, **Uncheck All**, and **Reset to -Defaults** buttons can be used. All selected properties are gathered. Available properties vary -based on the category selected. +Select properties individually, or use the **Check all**, **Uncheck All**, and **Reset to +Defaults** buttons. Enterprise Auditor gathers all selected properties. Available properties vary +based on the selected category. - Size units – Select from the following: diff --git a/docs/accessanalyzer/11.6/admin/datacollector/textsearch/searchcriteria.md b/docs/accessanalyzer/11.6/admin/datacollector/textsearch/searchcriteria.md index b0e2162a88..e696535442 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/textsearch/searchcriteria.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/textsearch/searchcriteria.md @@ -14,8 +14,8 @@ entire row of each file. The configurable functions are: - Use advanced criteria (instead of simple criteria) – Select this checkbox to display the Advanced - Criteria page and configure the search with additional filtering options. Advanced search criteria - is configured on the Advanced Criteria page. See the + Criteria page and configure the search with additional filtering options. Configure advanced + search criteria on the Advanced Criteria page. See the [TextSearch: Advanced Criteria](/docs/accessanalyzer/11.6/admin/datacollector/textsearch/advancedcriteria.md) topic for additional information. - Simple Criteria diff --git a/docs/accessanalyzer/11.6/admin/datacollector/textsearch/sourcefiles.md b/docs/accessanalyzer/11.6/admin/datacollector/textsearch/sourcefiles.md index 32e311b337..0980b88d27 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/textsearch/sourcefiles.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/textsearch/sourcefiles.md @@ -21,11 +21,11 @@ The Location section provides options to scope the search. - Current Job Directory – Search the job’s root folder for the specified file - Registry Lookup – Select this option to programmatically obtain a file path from a registry key that exists on the target host in the environment. Click the ellipsis to open the Enterprise - Auditor Registry Browser and connect to a host to select a registry key and path to be used for + Auditor Registry Browser and connect to a host to select a registry key and path to use for the lookup. - - Value Name – This value is automatically populated from the registry key - - Levels – The Levels slider can be used to truncate the path for the key value in the Adjust + - Value Name – Enterprise Auditor automatically populates this value from the registry key + - Levels – Use the Levels slider to truncate the path for the key value in the Adjust Path dialog box - Current value data – Displays the current value for the registry key - Query 32-bit – Select this checkbox to query a 32-bit view @@ -37,8 +37,8 @@ The Files section provides options to define the object or set of objects to fin - File name – Enter file names to search in the following format: `filename.extension`. Separate multiple file names with a semicolon and no spaces between the names. Wild cards can be used. -- File type – Select the extension type of the file name entered above to tell the collection - routine how the data within the underlying file is structured and should be handled: +- File type – Select the extension type of the file name you entered to tell the collection + routine how the data within the underlying file is structured and how to handle it: - Autodetect – Select this when the data type is unknown. The data collection routine will attempt to figure out what type of data it is and handle it appropriately. @@ -48,7 +48,7 @@ The Files section provides options to define the object or set of objects to fin - Binary - Space Separated Text -- First line is header captions line – Enabled when CSV, TSV, or Space Separated Text is selected +- First line is header captions line – Enabled when you select CSV, TSV, or Space Separated Text **Options** @@ -71,13 +71,13 @@ The Last Modification Time Filter section provides options to apply time filters Clicking the ellipsis in the Location section of the Source Files page opens the Remote Folder Explorer search window. In the Remote Folder Explorer window, navigate to the file folder location -and add the path to the scope. Multiple paths can be added to the scope. +and add the path to the scope. You can add multiple paths to the scope. ![Remote Folder Explorer window](/images/accessanalyzer/11.6/admin/datacollector/textsearch/remotefolderexplorer.webp) The Remote Folder Explorer functions are: -- Sample from host (path) – If the desired file does not exist on the local Enterprise Auditor +- Sample from host (path) – If the file you want doesn't exist on the local Enterprise Auditor Console, enter the name of the host that contains the file and click **Connect** to browse that host - Selected Path – Displays the path selected in the box above diff --git a/docs/accessanalyzer/11.6/admin/datacollector/textsearch/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/textsearch/summary.md index f00f3d2f7e..9508450a82 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/textsearch/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/textsearch/summary.md @@ -10,6 +10,6 @@ The Summary page displays a summary of the configured query. ![Text Search Data Collector Wizard Summary page](/images/accessanalyzer/11.6/admin/datacollector/textsearch/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Text Search Data Collector Wizard ensuring that no accidental clicks -are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** to close +the Text Search Data Collector Wizard instead. This prevents the wizard from saving accidental +clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/unix/editscript.md b/docs/accessanalyzer/11.6/admin/datacollector/unix/editscript.md index e42ba648a1..546651a8f9 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/unix/editscript.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/unix/editscript.md @@ -6,7 +6,7 @@ sidebar_position: 30 # Unix: Edit Script -The Edit Script page allows the script to be customized. +The Edit Script page lets you customize the script. ![Unix Data Collector Wizard Edit Script page](/images/accessanalyzer/11.6/admin/datacollector/unix/editscript.webp) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/unix/input.md b/docs/accessanalyzer/11.6/admin/datacollector/unix/input.md index b06b28b3d5..711d167483 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/unix/input.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/unix/input.md @@ -15,12 +15,12 @@ The configurable options are: - Use SQL table for scoping input – Select the checkbox to enable scoping options - Input Table - - Name – Select the SQL table from the drop-down menu + - Name – Select the SQL table from the dropdown menu - Filter Nulls – Select the checkbox to ignore blank rows in the table - Filter Duplicates – Select the checkbox to ignore duplicate rows in the table - Filter by host column – Select the checkbox to sort rows by host -- Columns – Select the desired rows from the SQL table +- Columns – Select the rows you want from the SQL table - Data Input Method - Run command once per table row diff --git a/docs/accessanalyzer/11.6/admin/datacollector/unix/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/unix/overview.md index 8b4323b74c..a198609ca8 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/unix/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/unix/overview.md @@ -7,7 +7,8 @@ sidebar_position: 380 # Unix Data Collector The Unix Data collector provides host inventory, software inventory, and logical volume inventory on -UNIX & Linux platforms. The Unix Data Collector has been preconfigured within the Unix Solution. +UNIX & Linux platforms. The Unix Solution includes the Unix Data Collector as a preconfigured +component. Both this data collector and the solution are available with a special Enterprise Auditor license. See the [Unix Solution](/docs/accessanalyzer/11.6/solutions/unix/overview.md) @@ -26,7 +27,7 @@ topic for additional information. - Root permissions in Unix/Linux -If the Root permission is unavailable, a least privileged model can be used. See the +If the Root permission is unavailable, you can use a least privileged model. See the [Least Privilege Model](/docs/accessanalyzer/11.6/requirements/unix/target.md#least-privilege-model) topic additional information. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/unix/results.md b/docs/accessanalyzer/11.6/admin/datacollector/unix/results.md index cdd0674370..b5b35ab6b5 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/unix/results.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/unix/results.md @@ -6,16 +6,16 @@ sidebar_position: 50 # Unix: Results -On the Results page, select which properties will be gathered out of those available for the query. -Additionally select properties based on which ROWKEY will be built. +On the Results page, select which properties to gather from those available for the query. +Additionally, select properties for building ROWKEY. ![Unix Data Collector Wizard Results page](/images/accessanalyzer/11.6/admin/datacollector/unix/results.webp) The configurable options are: -- Properties to return – Select the desired columns -- ROWKEY's components – Select the desired columns +- Properties to return – Select the columns you want +- ROWKEY's components – Select the columns you want Click **Finish** to save the configuration changes, or **Back** to return to the previous page. If -no changes were made, it is a best practice to click **Cancel** to close the Unix Data Collector -Wizard to make sure that no accidental settings are saved. +you made no changes, click **Cancel** to close the Unix Data Collector Wizard instead. This +prevents the wizard from saving accidental settings. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/usersgroups/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/usersgroups/overview.md index a3688a533d..76ca2d1904 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/usersgroups/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/usersgroups/overview.md @@ -9,7 +9,8 @@ sidebar_position: 390 The UsersGroups Data Collector audits user and group accounts for both local and domain, extracting system policies. -The UsersGroups Data Collector has been preconfigured within the Windows Solution. Both this data +The Windows Solution includes the UsersGroups Data Collector as a preconfigured component. Both +this data collector and the solution are available with a special Enterprise Auditor license. See the [Windows Solution](/docs/accessanalyzer/11.6/solutions/windows/overview.md) topic for additional information. @@ -47,5 +48,5 @@ contains the following wizard pages: ![Users and Groups Browser wizard Welcome page](/images/accessanalyzer/11.6/admin/datacollector/usersgroups/welcome.webp) -The Welcome page can be hidden by selecting the **Do not display this page the next time** box when -the wizard is open and configuration settings are saved. +Select the **Don't display this page the next time** box to hide the Welcome page. The wizard +saves this setting with your configuration changes. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/usersgroups/results/groups.md b/docs/accessanalyzer/11.6/admin/datacollector/usersgroups/results/groups.md index 3e73d1ea75..32cbc2231e 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/usersgroups/results/groups.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/usersgroups/results/groups.md @@ -47,7 +47,7 @@ options opens the Find a Group or Find a User browser. ![Find a group window](/images/accessanalyzer/11.6/admin/datacollector/usersgroups/category/findagroup.webp) The Find a Group and Find a User browsers display a list of groups or users, depending on which one -is being used, that can be selected for the option. Select from a specific host using the Sample +you use, that you can select for the option. Select from a specific host using the Sample from host option, or leave the text field blank and click **Connect** to retrieve all user groups or users that are selectable. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/usersgroups/results/results.md b/docs/accessanalyzer/11.6/admin/datacollector/usersgroups/results/results.md index 828b6f3cb9..d870e26f12 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/usersgroups/results/results.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/usersgroups/results/results.md @@ -6,8 +6,8 @@ sidebar_position: 10 # UsersGroups: Results -The Results page is where the type of data to be returned is configured. Each type has a different -set of options. +Use the Results page to configure the type of data to return. Each type has a different set of +options. ![Users and Groups Browser wizard Results page Category selection](/images/accessanalyzer/11.6/admin/datacollector/usersgroups/results.webp) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/usersgroups/results/security.md b/docs/accessanalyzer/11.6/admin/datacollector/usersgroups/results/security.md index fc62bc2d8f..94636be680 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/usersgroups/results/security.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/usersgroups/results/security.md @@ -6,11 +6,11 @@ sidebar_position: 30 # UsersGroups: Security Category -This Security policy is used to audit security policies. +This Security policy audits security policies. ![Users and Groups Browser wizard Results page Security category](/images/accessanalyzer/11.6/admin/datacollector/usersgroups/category/security.webp) -Select from the following options for what data will be returned: +Select from the following options for what data to return: - Security Policy (User Rights Assignment) – Identifies user rights assignment for each individual policy part that grants or removes rights diff --git a/docs/accessanalyzer/11.6/admin/datacollector/usersgroups/results/users.md b/docs/accessanalyzer/11.6/admin/datacollector/usersgroups/results/users.md index 7447032700..46f53a6580 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/usersgroups/results/users.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/usersgroups/results/users.md @@ -15,11 +15,11 @@ In the Users section, select from the following options: - All users – All users found on the target host - All users in the following groups – Click the ellipsis (**…**) to open the Find a Group browser window and specify a group. See the [Find a Group/User Browser](#find-a-groupuser-browser) topic - for additional information. A specific group can also be entered manually into the text field. + for additional information. You can also enter a specific group manually into the text field. - These users – Click the ellipsis (**…**) to open the Find a User browser window and specify one or more users. See the [Find a Group/User Browser](#find-a-groupuser-browser) topic for additional - information. A specific user can also be entered manually into the text field. -- Special users – The users found can be flagged as special users in the following categories: + information. You can also enter a specific user manually into the text field. +- Special users – You can flag users found as special users in the following categories: - Administrator - Guest @@ -65,7 +65,7 @@ opens the Find a Group or Find a User browser. ![Find a group window](/images/accessanalyzer/11.6/admin/datacollector/usersgroups/category/findagroup.webp) The Find a Group and Find a User browsers display a list of groups or users, depending on which one -is being used, that can be selected for the option. Select from a specific host using the Sample +you use, that you can select for the option. Select from a specific host using the Sample from host option, or leave the text field blank and click **Connect** to retrieve all user groups or users that are selectable. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/usersgroups/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/usersgroups/summary.md index d7037777b8..0415fa0a41 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/usersgroups/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/usersgroups/summary.md @@ -10,6 +10,6 @@ The Summary page displays a summary of the configured query. ![Users and Groups Browser wizard Summary page](/images/accessanalyzer/11.6/admin/datacollector/usersgroups/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Users and Groups Browser wizard ensuring that no accidental clicks are -saved. +Click **Finish** to save configuration changes. If you didn't make changes, it is a best practice to +click **Cancel** to close the Users and Groups Browser wizard, which prevents the wizard from saving +accidental clicks. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/wmicollector/classes.md b/docs/accessanalyzer/11.6/admin/datacollector/wmicollector/classes.md index 19daea50d4..9c57242898 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/wmicollector/classes.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/wmicollector/classes.md @@ -10,6 +10,6 @@ On the Classes page, configure the WMICollector namespaces and classes to use as ![WMI Browser wizard Classes page](/images/accessanalyzer/11.6/admin/datacollector/wmicollector/classes.webp) -Select the **Namespace** and **Class** from the drop-down lists to use as a data source. The default -namespace, **root\CIMV2**, is typically what should be used. Select the **Win32 classes only** -checkbox to use only Win32 classes. +Select the **Namespace** and **Class** from the dropdown lists to use as a data source. Typically, use +the default namespace, **root\CIMV2**. Select the **Win32 classes only** checkbox to use only Win32 +classes. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/wmicollector/overview.md b/docs/accessanalyzer/11.6/admin/datacollector/wmicollector/overview.md index 2cd2779126..81e534d0bc 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/wmicollector/overview.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/wmicollector/overview.md @@ -7,9 +7,9 @@ sidebar_position: 400 # WMICollector Data Collector The WMICollector Data Collector identifies data for certain types of WMI classes and namespaces. The -WMICollector Data Collector is a core component of Enterprise Auditor, but it has been preconfigured -within the Windows Solution. While the data collector is available with all Enterprise Auditor -license options, the Windows Solution is only available with a special Enterprise Auditor license. +WMICollector Data Collector is a core component of Enterprise Auditor, but the Windows Solution has +preconfigured it. While the data collector is available with all Enterprise Auditor license options, +the Windows Solution is only available with a special Enterprise Auditor license. See the [Windows Solution](/docs/accessanalyzer/11.6/solutions/windows/overview.md) topic for additional information. @@ -30,7 +30,7 @@ topic for additional information. ## WMICollector Query Configuration -The WMICollector Data Collector is configured through the WMI Browser wizard, which contains the +You configure the WMICollector Data Collector through the WMI Browser wizard, which contains the following wizard pages: - Welcome @@ -41,5 +41,5 @@ following wizard pages: ![WMI Browser wizard Welcome page](/images/accessanalyzer/11.6/admin/datacollector/wmicollector/welcome.webp) -The Welcome page can be hidden by selecting the **Do not display this page the next time** checkbox +The Welcome page can be hidden by selecting the **Don't display this page the next time** checkbox when the wizard is open and configuration settings are saved. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/wmicollector/properties.md b/docs/accessanalyzer/11.6/admin/datacollector/wmicollector/properties.md index 573a2f6fff..2e219c8bab 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/wmicollector/properties.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/wmicollector/properties.md @@ -10,10 +10,10 @@ On the Properties page, select the properties to extract. ![WMI Browser wizard Properties page](/images/accessanalyzer/11.6/admin/datacollector/wmicollector/properties.webp) -If the **Extract only selected instances** checkbox is not selected, data is returned from all +If you don't select the **Extract only selected instances** checkbox, the query returns data from all process instances displayed in the **Instances of `\`** box. To return data from a single process instance, select an instance and select the **Extract only selected instances** -checkbox. Only one instance can be selected at a time. +checkbox. You can select only one instance at a time. -In the **Instance data** box, select the checkboxes next to the desired properties to return during +In the **Instance data** box, select the checkboxes next to the properties you want to return during query execution. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/wmicollector/samplehost.md b/docs/accessanalyzer/11.6/admin/datacollector/wmicollector/samplehost.md index 1a31c8b981..3eec84cfeb 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/wmicollector/samplehost.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/wmicollector/samplehost.md @@ -10,7 +10,7 @@ On the Sample Host page, enter a sample host to populate options for the query. ![WMI Browser wizard Sample Host page](/images/accessanalyzer/11.6/admin/datacollector/wmicollector/samplehost.webp) -On the Sample Host page, if the desired classes and namespaces to audit reside on the local host, -click **Next**. (The local host is represented by `.` in the **Sample host name** box). If a -different sample host is needed to populate the namespace and class options, enter the name for the -remote host and click **Next**. +On the Sample Host page, if the classes and namespaces you want to audit reside on the local host, +click **Next**. (In the **Sample host name** box, `.` represents the local host). If you need a +different sample host to populate the namespace and class options, enter the name for the remote +host and click **Next**. diff --git a/docs/accessanalyzer/11.6/admin/datacollector/wmicollector/summary.md b/docs/accessanalyzer/11.6/admin/datacollector/wmicollector/summary.md index cebcdd093f..0820553fa6 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/wmicollector/summary.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/wmicollector/summary.md @@ -10,5 +10,6 @@ The Summary page, or Results page, displays a summary of the configured query. ![WMI Browser wizard Summary page](/images/accessanalyzer/11.6/admin/datacollector/wmicollector/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the WMI Browser wizard ensuring that no accidental clicks are saved. +Click **Finish** to save configuration changes. If you didn't make changes, it is a best practice to +click **Cancel** to close the WMI Browser wizard, which prevents the wizard from saving accidental +clicks. diff --git a/docs/accessanalyzer/11.6/admin/hostdiscovery/activities.md b/docs/accessanalyzer/11.6/admin/hostdiscovery/activities.md index 6c532985aa..8d8a76a44b 100644 --- a/docs/accessanalyzer/11.6/admin/hostdiscovery/activities.md +++ b/docs/accessanalyzer/11.6/admin/hostdiscovery/activities.md @@ -19,7 +19,7 @@ The options are: - A confirmation window displays. Click **Yes** to complete the deletion - Run Query – Begins an immediate execution of the selected query -- Stop Query – Stops the selected query which is currently running +- Stop Query – Stops the selected query which is running - No action occurs if the query is **Idle** @@ -38,6 +38,6 @@ The options are: [Host Management](/docs/accessanalyzer/11.6/admin/hostmanagement/overview.md) node directly to the selected query’s generated host list -These options are also available through a pop-up menu accessed by right-clicking on a query. -**Create Query** and **Suspend Query Queue** are additionally available through a pop-up menu -accessed by right-clicking on the **Host Discovery** node. +You can also access these options through a pop-up menu by right-clicking a query. You can also +access **Create Query** and **Suspend Query Queue** through a pop-up menu by right-clicking the +**Host Discovery** node. diff --git a/docs/accessanalyzer/11.6/admin/hostdiscovery/log.md b/docs/accessanalyzer/11.6/admin/hostdiscovery/log.md index ce38115c35..4be07d5e28 100644 --- a/docs/accessanalyzer/11.6/admin/hostdiscovery/log.md +++ b/docs/accessanalyzer/11.6/admin/hostdiscovery/log.md @@ -6,12 +6,12 @@ sidebar_position: 40 # Discovery Log -The **Host Discovery** > **Discovery Log** node lists host discovery logs. These logs house -transactions that transpire during the running of host discovery and host inventory tasks. +The **Host Discovery** > **Discovery Log** node lists host discovery logs. These logs record +transactions that occur while host discovery and host inventory tasks run. ![Discovery Log](/images/accessanalyzer/11.6/admin/hostdiscovery/discoverylog.webp) -The Discovery Log logging level is configured within the **Settings** > **Host Discovery** node. See +Configure the Discovery Log logging level within the **Settings** > **Host Discovery** node. See the [Host Discovery](/docs/accessanalyzer/11.6/admin/settings/hostdiscovery.md) topic for additional information. @@ -19,9 +19,9 @@ topic for additional information. The following options are above the data grid: - Reload Log – Refresh the log data for the selected Log date and Query Name -- Log date – Select the desired **Log date** from the drop-down menu to view transactions +- Log date – Select the **Log date** you want from the dropdown menu to view transactions - Query Name – The default selection is **All Queries**. To narrow the data to a desired query, - select a query name from the drop-down menu. + select a query name from the dropdown menu. The data grid contains the following columns: diff --git a/docs/accessanalyzer/11.6/admin/hostdiscovery/overview.md b/docs/accessanalyzer/11.6/admin/hostdiscovery/overview.md index 45dde6857c..d164f800ba 100644 --- a/docs/accessanalyzer/11.6/admin/hostdiscovery/overview.md +++ b/docs/accessanalyzer/11.6/admin/hostdiscovery/overview.md @@ -6,12 +6,12 @@ sidebar_position: 40 # Host Discovery Node -Use the **Host Discovery** node to discover hosts to audit. Host Discovery queries are created in +Use the **Host Discovery** node to discover hosts to audit. Create Host Discovery queries in the Host Discovery node to discover hosts within the targeted environment that match the desired criteria (for example, all domain controllers for Active Directory auditing). The Host Discovery queries view displays a list of previously configured queries, opens the Host -Discovery Wizard to create new queries, and is where host inventory process can be automated. The +Discovery Wizard to create new queries, and lets you automate host inventory. The **Host Discovery** node houses the Discovery Log. The **Settings** > **Host Discovery** node contains the global settings that affect discovery queries. See the [Host Discovery](/docs/accessanalyzer/11.6/admin/settings/hostdiscovery.md) diff --git a/docs/accessanalyzer/11.6/admin/hostdiscovery/queries.md b/docs/accessanalyzer/11.6/admin/hostdiscovery/queries.md index 98a52aff75..51063fdb75 100644 --- a/docs/accessanalyzer/11.6/admin/hostdiscovery/queries.md +++ b/docs/accessanalyzer/11.6/admin/hostdiscovery/queries.md @@ -10,7 +10,7 @@ The Host Discovery Queries Pane contains a list of previously-configured queries ![Host Discovery Queries Pane](/images/accessanalyzer/11.6/admin/hostdiscovery/queries.webp) -The list of previously configured queries is provided in a table format with the following columns: +The list of previously configured queries appears in a table format with the following columns: - Name – Displays the name assigned to the query during creation - Query Source – Identifies where the query searches for hosts @@ -27,13 +27,13 @@ The list of previously configured queries is provided in a table format with the - Snapshot – Only shows host found during the most recent query execution :::note - The Snapshot mode is configured on the Options page of the Host Discovery Wizard. + Configure Snapshot mode on the Options page of the Host Discovery Wizard. ::: ## View Hidden Columns -Follow the steps to view the hidden columns in the table: +To view the hidden columns in the table: **Step 1 –** Right-click a header in the table, which opens a context menu. @@ -47,7 +47,7 @@ Follow the steps to view the hidden columns in the table: ![Drag hidden colum into table](/images/accessanalyzer/11.6/admin/hostdiscovery/queriesaddhiddencolumn.webp) -**Step 4 –** Drag and drop the desired column between any header of the table. +**Step 4 –** Drag and drop the column you want between any header of the table. ![Host Discovery Queries table with column added](/images/accessanalyzer/11.6/admin/hostdiscovery/querieshiddencolumnadded.webp) diff --git a/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/addomaincontrollers.md b/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/addomaincontrollers.md index 8fa8740ed2..9c572e703d 100644 --- a/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/addomaincontrollers.md +++ b/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/addomaincontrollers.md @@ -20,8 +20,8 @@ Directory server (Discover Domain Controllers)** option. Click **Next**. **Step 2 –** On the Query page, name the query and select the credentials used to access the source. - Query Name – Provide a unique descriptive name for this query by typing over the `NEWQUERY` - default name. Two queries can't have the same name. If you use an existing name, a number is - automatically appended to the query name, for example `NEWQUERY` becomes `NEWQUERY1`. + default name. Two queries can't have the same name. If you use an existing name, Enterprise Auditor + automatically appends a number to the query name, for example `NEWQUERY` becomes `NEWQUERY1`. - Credentials – Select a Connection Profile. These credentials require the appropriate permissions for querying the source: @@ -74,7 +74,7 @@ Click **Next** to continue. - Run the query when jobs that reference it are run – Select this option to automatically execute the Host Discovery query before executing a job that has the host list generated by this query - assigned. This ensures any new hosts have been discovered and are available for auditing. + assigned. This ensures the query discovers any new hosts and makes them available for auditing. :::info Use this setting only for host lists tied to specific jobs that require @@ -94,11 +94,11 @@ Click **Next** to continue. ![Host Discovey Wizard Inventory page for AD Domain Controllers query](/images/accessanalyzer/11.6/admin/hostdiscovery/wizard/inventory_2.webp) -**Step 5 –** On the Inventory page, the host inventory process can be automatically included with +**Step 5 –** On the Inventory page, you can automatically include the host inventory process with the discovery query. - Refresh inventory every time when the host discovery query completes – Automates the host - inventory process and is dependent on the **Settings** > **Host Inventory** node configuration for + inventory process and depends on the **Settings** > **Host Inventory** node configuration for the age of previously inventoried records. Leaving this option deselected applies the global settings for host inventory. - Credentials – Select a Connection Profile. These credentials require the appropriate permissions @@ -129,12 +129,12 @@ configuration process. query at another time. Both options close the Host Discovery Wizard and return to the Host Discovery Queries view on the -Host Discovery node. If **Yes** is selected, the **Query State** indicates the running query. +Host Discovery node. If you select **Yes**, the **Query State** indicates the running query. ## Required Permissions -This query only requires an authenticated domain user account — no elevated Active Directory -administrative role (such as Domain Admin or Enterprise Admin) is needed to enumerate domain +This query only requires an authenticated domain user account — you don't need an elevated Active +Directory administrative role (such as Domain Admin or Enterprise Admin) to enumerate domain controllers, domains, or sites. Because the query reads domain and site information from the forest-wide Configuration partition (the @@ -142,8 +142,8 @@ Because the query reads domain and site information from the forest-wide Configu capable of servicing a query against the Configuration naming context. :::info -Domain Controllers are a high-value target class. If **Refresh inventory every time the host -discovery query completes** is enabled on the Inventory page, the account used for inventory needs +Domain Controllers are a high-value target class. If you enable **Refresh inventory every time the +host discovery query completes** on the Inventory page, the account used for inventory needs local administrator rights on every discovered domain controller — effectively equivalent to Domain Admin. Use a dedicated, tightly scoped service account for this purpose rather than an existing Domain Admin credential. See the diff --git a/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/adexchange.md b/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/adexchange.md index 5cb389dbd3..60c5c56d15 100644 --- a/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/adexchange.md +++ b/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/adexchange.md @@ -21,8 +21,8 @@ Directory server (Discover Exchange servers)** option. Click **Next**. **Step 2 –** On the Query page, name the query and select the credentials used to access the source. - Query Name – Provide a unique descriptive name for this query by typing over the `NEWQUERY` - default name. Two queries can't have the same name. If you use an existing name, a number is - automatically appended to the query name, for example `NEWQUERY` becomes `NEWQUERY1`. + default name. Two queries can't have the same name. If you use an existing name, Enterprise Auditor + automatically appends a number to the query name, for example `NEWQUERY` becomes `NEWQUERY1`. - Credentials – Select a Connection Profile. These credentials require the appropriate permissions for querying the source: @@ -54,7 +54,7 @@ topic for instructions. Click **Next**. - Run the query when jobs that reference it are run – Select this option to automatically execute the Host Discovery query before executing a job that has the host list generated by this query - assigned. This ensures any new hosts have been discovered and are available for auditing. + assigned. This ensures the query discovers any new hosts and makes them available for auditing. :::info Use this setting only for host lists tied to specific jobs that require @@ -74,11 +74,11 @@ Click **Next** to continue. ![Host Discovery Wizard Inventory page for AD Exchange](/images/accessanalyzer/11.6/admin/hostdiscovery/wizard/inventory_5.webp) -**Step 5 –** On the Inventory page, the host inventory process can be automatically included with +**Step 5 –** On the Inventory page, you can automatically include the host inventory process with the discovery query. - Refresh inventory every time when the host discovery query completes – Automates the host - inventory process and is dependent on the **Settings** > **Host Inventory** node configuration for + inventory process and depends on the **Settings** > **Host Inventory** node configuration for the age of previously inventoried records. Leaving this option deselected applies the global settings for host inventory. - Credentials – Select a Connection Profile. These credentials require the appropriate permissions @@ -109,13 +109,13 @@ configuration process. query at another time. Both options close the Host Discovery Wizard and return to the Host Discovery Queries view on the -Host Discovery node. If **Yes** is selected, the **Query State** indicates the running query. +Host Discovery node. If you select **Yes**, the **Query State** indicates the running query. ## Required Permissions -This query only requires an authenticated domain user account — no Exchange administrative role -(such as Organization Management or View-Only Organization Management) is needed to read Exchange -server objects from Active Directory. +This query only requires an authenticated domain user account — you don't need an Exchange +administrative role (such as Organization Management or View-Only Organization Management) to read +Exchange server objects from Active Directory. Because the search targets the Exchange Configuration container (`CN=Microsoft Exchange,CN=Services,CN=Configuration`), which is part of the forest-wide @@ -124,7 +124,7 @@ servicing a query against the Configuration naming context. Any domain controlle holds a copy of this partition, so this isn't limited to domain controllers local to the Enterprise Auditor Console. -If **Refresh inventory every time the host discovery query completes** is enabled on the Inventory +If you enable **Refresh inventory every time the host discovery query completes** on the Inventory page, Enterprise Auditor also queries each discovered Exchange server for inventory data (including Exchange role and version), which requires local administrator rights (or explicitly delegated Remote Registry and WMI access, including the Exchange WMI provider) on that host. See the diff --git a/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/adgeneral.md b/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/adgeneral.md index 933984a47e..01d40810b1 100644 --- a/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/adgeneral.md +++ b/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/adgeneral.md @@ -21,8 +21,8 @@ Directory server (General)** option. Click **Next**. **Step 2 –** On the Query page, name the query and select the credentials used to access the source. - Query Name – Provide a unique descriptive name for this query by typing over the `NEWQUERY` - default name. Two queries can't have the same name. If you use an existing name, a number is - automatically appended to the query name, for example `NEWQUERY` becomes `NEWQUERY1`. + default name. Two queries can't have the same name. If you use an existing name, Enterprise Auditor + automatically appends a number to the query name, for example `NEWQUERY` becomes `NEWQUERY1`. - Credentials – Select a Connection Profile. These credentials require the appropriate permissions for querying the source: @@ -78,7 +78,7 @@ Click **Next** to continue. - Run the query when jobs that reference it are run – Select this option to automatically execute the Host Discovery query before executing a job that has the host list generated by this query - assigned. This ensures any new hosts have been discovered and are available for auditing. + assigned. This ensures the query discovers any new hosts and makes them available for auditing. :::info Use this setting only for host lists tied to specific jobs that require @@ -98,11 +98,11 @@ Click **Next** to continue. ![Host Discovery Wizard Inventory page for AD General](/images/accessanalyzer/11.6/admin/hostdiscovery/wizard/inventory_4.webp) -**Step 5 –** On the Inventory page, the host inventory process can be automatically included with +**Step 5 –** On the Inventory page, you can automatically include the host inventory process with the discovery query. - Refresh inventory every time when the host discovery query completes – Automates the host - inventory process and is dependent on the **Settings** > **Host Inventory** node configuration for + inventory process and depends on the **Settings** > **Host Inventory** node configuration for the age of previously inventoried records. Leaving this option deselected applies the global settings for host inventory. - Credentials – Select a Connection Profile. These credentials require the appropriate permissions @@ -133,21 +133,21 @@ configuration process. query at another time. Both options close the Host Discovery Wizard and return to the Host Discovery Queries view on the -Host Discovery node. If **Yes** is selected, the **Query State** indicates the running query. +Host Discovery node. If you select **Yes**, the **Query State** indicates the running query. ## Required Permissions Querying Active Directory for computer objects only requires an authenticated domain user -account — no elevated Active Directory rights (such as Domain Admin or specific delegated -permissions) are needed to read computer objects in a standard Active Directory environment. This -applies regardless of which Connection Profile option is selected. +account — you don't need elevated Active Directory rights (such as Domain Admin or specific +delegated permissions) to read computer objects in a standard Active Directory environment. This +applies regardless of which Connection Profile option you select. :::info If the targeted OUs have restricted read access (for example, hardened Tier 0 OUs in a tiered -administration model), the account used must be explicitly granted read access to those OUs. +administration model), you must explicitly grant the account used read access to those OUs. ::: -If **Refresh inventory every time the host discovery query completes** is enabled on the Inventory +If you enable **Refresh inventory every time the host discovery query completes** on the Inventory page, Enterprise Auditor also queries each discovered computer for inventory data, which requires local administrator rights (or explicitly delegated Remote Registry and WMI access) on that host in addition to the Active Directory read access described earlier. See the diff --git a/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/csv.md b/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/csv.md index c303efe3b6..efadbf94fc 100644 --- a/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/csv.md +++ b/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/csv.md @@ -31,8 +31,8 @@ The source in this case is the Enterprise Auditor Console server. - Query Name – Provide a unique descriptive name for this query by typing over the `NEWQUERY` - default name. Two queries can't have the same name. If you use an existing name, a number is - automatically appended to the query name, for example `NEWQUERY` becomes `NEWQUERY1`. + default name. Two queries can't have the same name. If you use an existing name, Enterprise Auditor + automatically appends a number to the query name, for example `NEWQUERY` becomes `NEWQUERY1`. - Credentials – Select a Connection Profile. These credentials require the appropriate permissions for querying the source: @@ -70,7 +70,7 @@ Click **Next** to continue. - Run the query when jobs that reference it are run – Select this option to automatically execute the Host Discovery query before executing a job that has the host list generated by this query - assigned. This ensures any new hosts have been discovered and are available for auditing. + assigned. This ensures the query discovers any new hosts and makes them available for auditing. :::info Use this setting only for host lists tied to specific jobs that require @@ -90,11 +90,11 @@ Click **Next** to continue. ![Host Discovery Wizard Inventory page for CSV import](/images/accessanalyzer/11.6/admin/hostdiscovery/wizard/inventory_3.webp) -**Step 5 –** On the Inventory page, the host inventory process can be automatically included with +**Step 5 –** On the Inventory page, you can automatically include the host inventory process with the discovery query. - Refresh inventory every time when the host discovery query completes – Automates the host - inventory process and is dependent on the **Settings** > **Host Inventory** node configuration for + inventory process and depends on the **Settings** > **Host Inventory** node configuration for the age of previously inventoried records. Leaving this option deselected applies the global settings for host inventory. - Credentials – Select a Connection Profile. These credentials require the appropriate permissions @@ -125,12 +125,12 @@ configuration process. query at another time. Both options close the Host Discovery Wizard and return to the Host Discovery Queries view on the -Host Discovery node. If **Yes** is selected, the **Query State** indicates the running query. +Host Discovery node. If you select **Yes**, the **Query State** indicates the running query. ## Required Permissions -No domain credentials are required to import a host list from a CSV file. The account used only -needs read access to the folder containing the CSV file. If the file is stored on a local drive of +You don't need domain credentials to import a host list from a CSV file. The account used only +needs read access to the folder containing the CSV file. If you store the file on a local drive of the Enterprise Auditor Console server, the Console service account's own permissions are sufficient. If the file is on a network share (a UNC path), the credential selected must have read access to that share instead. @@ -140,7 +140,7 @@ This query doesn't contact any of the hosts listed in the CSV during the import only reads the file and populates the host list. ::: -If **Refresh inventory every time the host discovery query completes** is enabled on the Inventory +If you enable **Refresh inventory every time the host discovery query completes** on the Inventory page, Enterprise Auditor also queries each imported host for inventory data, which requires local administrator rights (or explicitly delegated Remote Registry and WMI access) on that host. See the [Host Inventory](/docs/accessanalyzer/11.6/admin/settings/hostinventory.md) topic for details. diff --git a/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/database.md b/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/database.md index 9d9cb7dbae..a7e08efc0d 100644 --- a/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/database.md +++ b/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/database.md @@ -26,8 +26,8 @@ database** option. Click **Next**. **Step 2 –** On the Query page, name the query and select the credentials used to access the source. - Query Name – Provide a unique descriptive name for this query by typing over the `NEWQUERY` - default name. Two queries can't have the same name. If you use an existing name, a number is - automatically appended to the query name, for example `NEWQUERY` becomes `NEWQUERY1`. + default name. Two queries can't have the same name. If you use an existing name, Enterprise Auditor + automatically appends a number to the query name, for example `NEWQUERY` becomes `NEWQUERY1`. - Credentials – Select a Connection Profile. These credentials require the appropriate permissions for querying the source: @@ -66,16 +66,16 @@ names are located: ![Test connection succeeded confirmation window](/images/accessanalyzer/11.6/admin/hostdiscovery/wizard/datalinkpropertiestestconnection.webp) - - Click **Test Connection** to confirm a connection has been established. Click **OK** on the + - Click **Test Connection** to confirm the connection succeeded. Click **OK** on the confirmation window. - Database – Select the **Select the database on the server** option and use the dropdown menu to select the database - - The other tabs in the Data Link Properties window shouldn't be modified + - Don't modify the other tabs in the Data Link Properties window - Provider tab – The database connector, dictated by the source of the data and the data - sources that are available on the Enterprise Auditor Console server. This is set by - default to the **Microsoft OLE DB Provider for SQL Server**. - - Advanced tab – Allows modifications of the connection timeout to the database server in + sources that are available on the Enterprise Auditor Console server. By default, + Enterprise Auditor sets this to the **Microsoft OLE DB Provider for SQL Server**. + - Advanced tab – Lets you modify the connection timeout to the database server in case the server is slow or far away - All tab – Don't modify this tab @@ -94,7 +94,7 @@ Click **Next** to continue. - Run the query when jobs that reference it are run – Select this option to automatically execute the Host Discovery query before executing a job that has the host list generated by this query - assigned. This ensures any new hosts have been discovered and are available for auditing. + assigned. This ensures the query discovers any new hosts and makes them available for auditing. :::info Use this setting only for host lists tied to specific jobs that require @@ -114,11 +114,11 @@ Click **Next** to continue. ![Host Discovery Wizard Inventory page for database import](/images/accessanalyzer/11.6/admin/hostdiscovery/wizard/inventory.webp) -**Step 5 –** On the Inventory page, the host inventory process can be automatically included with +**Step 5 –** On the Inventory page, you can automatically include the host inventory process with the discovery query. - Refresh inventory every time when the host discovery query completes – Automates the host - inventory process and is dependent on the **Settings** > **Host Inventory** node configuration for + inventory process and depends on the **Settings** > **Host Inventory** node configuration for the age of previously inventoried records. Leaving this option deselected applies the global settings for host inventory. - Credentials – Select a Connection Profile. These credentials require the appropriate permissions @@ -149,13 +149,13 @@ configuration process. query at another time. Both options close the Host Discovery Wizard and return to the Host Discovery Queries view on the -Host Discovery node. If **Yes** is selected, the **Query State** indicates the running query. +Host Discovery node. If you select **Yes**, the **Query State** indicates the running query. ## Required Permissions The account configured in the Data Link Properties window only needs permission to connect to the -database and read (`SELECT`) from the single table used by the query. No write access, additional -tables, or server-level roles are required. +database and read (`SELECT`) from the single table used by the query. The query doesn't require +write access, additional tables, or server-level roles. :::info Enterprise Auditor doesn't restrict the query to the selected table/column at the database @@ -164,12 +164,12 @@ grant the account `SELECT` only on the specific table (or a view exposing just t rather than reusing a broader-access account. ::: -If **Use Windows NT Integrated security** is selected, the query reuses whatever database access +If you select **Use Windows NT Integrated security**, the query reuses whatever database access the Enterprise Auditor Console's service account already has, which may be broader than this query needs. A dedicated SQL authentication account scoped to this one table is generally the safer choice. -If **Refresh inventory every time the host discovery query completes** is enabled on the Inventory +If you enable **Refresh inventory every time the host discovery query completes** on the Inventory page, Enterprise Auditor also queries each imported host for inventory data, which requires local administrator rights (or explicitly delegated Remote Registry and WMI access) on that host. See the [Host Inventory](/docs/accessanalyzer/11.6/admin/settings/hostinventory.md) topic for details. diff --git a/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/ipnetwork.md b/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/ipnetwork.md index a315ce48c0..00d75d32a9 100644 --- a/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/ipnetwork.md +++ b/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/ipnetwork.md @@ -20,8 +20,8 @@ option. Click **Next**. **Step 2 –** On the Query page, name the query and select the credentials used to access the source. - Query Name – Provide a unique descriptive name for this query by typing over the `NEWQUERY` - default name. Two queries can't have the same name. If you use an existing name, a number is - automatically appended to the query name, for example `NEWQUERY` becomes `NEWQUERY1`. + default name. Two queries can't have the same name. If you use an existing name, Enterprise Auditor + automatically appends a number to the query name, for example `NEWQUERY` becomes `NEWQUERY1`. - Credentials – Select a Connection Profile. These credentials require the appropriate permissions for querying the source: @@ -63,10 +63,10 @@ Click **Next** to continue. - IP Ranges box – Displays the selected range of IP Addresses. Use the links at the top of the box to edit the list: - - Add as inclusion – Adds information provided in the IP Address Textboxes into the to be - collected list - - Add as exclusion – Adds information provided in the IP Address Textboxes into the to be - ignored list + - Add as inclusion – Adds information provided in the IP Address Textboxes to the inclusion + list + - Add as exclusion – Adds information provided in the IP Address Textboxes to the exclusion + list - Remove – Removes the selection from the IP Ranges box - (Optional) Only include host with the following ports open – If selected, this option limits the @@ -85,7 +85,7 @@ Click **Next** to continue. - Run the query when jobs that reference it are run – Select this option to automatically execute the Host Discovery query before executing a job that has the host list generated by this query - assigned. This ensures any new hosts have been discovered and are available for auditing. + assigned. This ensures the query discovers any new hosts and makes them available for auditing. :::info Use this setting only for host lists tied to specific jobs that require @@ -105,11 +105,11 @@ Click **Next** to continue. ![Host Discovey Wizard Inventory page for IP network scan](/images/accessanalyzer/11.6/admin/hostdiscovery/wizard/inventory_1.webp) -**Step 5 –** On the Inventory page, the host inventory process can be automatically included with +**Step 5 –** On the Inventory page, you can automatically include the host inventory process with the discovery query. - Refresh inventory every time when the host discovery query completes – Automates the host - inventory process and is dependent on the **Settings** > **Host Inventory** node configuration for + inventory process and depends on the **Settings** > **Host Inventory** node configuration for the age of previously inventoried records. Leaving this option deselected applies the global settings for host inventory. - Credentials – Select a Connection Profile. These credentials require the appropriate permissions @@ -140,7 +140,7 @@ configuration process. query at another time. Both options close the Host Discovery Wizard and return to the Host Discovery Queries view on the -Host Discovery node. If **Yes** is selected, the **Query State** indicates the running query. +Host Discovery node. If you select **Yes**, the **Query State** indicates the running query. ## Required Permissions @@ -150,14 +150,14 @@ standard DNS to resolve their names — none of these steps authenticate to the :::info The Connection Profile selected on the Query page isn't required for the IP sweep step itself. It -only becomes relevant if Host Inventory Refresh is also enabled. +only becomes relevant if you also enable Host Inventory Refresh. ::: -If **Only include host with the following ports open** is selected, Enterprise Auditor only +If you select **Only include host with the following ports open**, Enterprise Auditor only verifies that the specified TCP ports accept a connection. This confirms network reachability, not that any particular service is running or that any credential would succeed against it. -If **Refresh inventory every time the host discovery query completes** is enabled on the Inventory +If you enable **Refresh inventory every time the host discovery query completes** on the Inventory page, Enterprise Auditor also queries each discovered host for inventory data. This requires the Remote Registry service to be running on the target and the account used to have local administrator rights (or an account explicitly delegated Remote Registry and WMI namespace permissions) on that host. See the diff --git a/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/overview.md b/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/overview.md index d8e42381dd..9e5cd98bfc 100644 --- a/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/overview.md +++ b/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/overview.md @@ -6,13 +6,13 @@ sidebar_position: 30 # Host Discovery Wizard -The Host Discovery Wizard gives complete control over how hosts are discovered on the targeted -network and which hosts are discovered. +The Host Discovery Wizard gives you complete control over how the query discovers hosts on the +targeted network and which hosts it discovers. ![Console with Create Query Option Highlighted](/images/accessanalyzer/11.6/admin/hostdiscovery/wizard/createqueryhighlighted.webp) Use the Host Discovery Wizard to create new queries. The wizard opens in the Results pane. Use any -of the following methods in order to access the Host Discovery Wizard from the Host Discovery node: +of the following methods to access the Host Discovery Wizard from the Host Discovery node: - Select **Create Query** in the Activities pane - Right-click the **Host Discovery** node and select **Create Query** from the pop-up menu @@ -28,8 +28,8 @@ for hosts. Hosts are discoverable using one of the following options: – Scans a specified range of IP Addresses for active hosts and resolves the names of machines using DNS - [Query an Active Directory Server (General)](/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/adgeneral.md) - – Scans the default domain controller or a specified server for all computer objects, can be - scoped + – Scans the default domain controller or a specified server for all computer objects; you can + scope it - [Query an Active Directory Server (Discover Exchange servers)](/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/adexchange.md) – Scans the default domain controller or a specified server but is scoped to return only computer objects sitting in the configuration container for Exchange servers @@ -42,7 +42,7 @@ for hosts. Hosts are discoverable using one of the following options: – Imports a host list from a specified SQL Server database :::note -The Advanced Options checkbox in the lower-left corner is a legacy item and should not be +The Advanced Options checkbox in the lower-left corner is a legacy item and shouldn't be selected. ::: diff --git a/docs/accessanalyzer/11.6/admin/hostmanagement/actions/add.md b/docs/accessanalyzer/11.6/admin/hostmanagement/actions/add.md index 9176772e84..2e88ba2c54 100644 --- a/docs/accessanalyzer/11.6/admin/hostmanagement/actions/add.md +++ b/docs/accessanalyzer/11.6/admin/hostmanagement/actions/add.md @@ -6,8 +6,8 @@ sidebar_position: 10 # Add Hosts -The **Add Hosts** option creates a new host list. It can be accessed through the **Host Management** -node. Follow the steps to add a new host list. +The **Add Hosts** option creates a new host list. You can access it through the **Host Management** +node. To add a new host list: ![Add Hosts option on Activities pane of the Host Management node](/images/accessanalyzer/11.6/admin/hostmanagement/actions/addhosts.webp) @@ -18,9 +18,9 @@ node. Follow the steps to add a new host list. **Step 2 –** On the Manual Host Entry page, choose to either enter the hosts manually one at a time, or use the **Import** option. When the list is completed, click **Next**. -- To enter hosts manually, type the host name in the **Host name** textbox. Then click **Add**. The - entry will appear in the **Host list** box. Repeat the process until all hosts for this list have - been entered. +- To enter hosts manually, enter the host name in the **Host name** textbox. Then click **Add**. The + entry will appear in the **Host list** box. Repeat the process until you've entered all hosts for + this list. - The **Import** option opens the Import Hosts window. See the [Import Hosts Option](/docs/accessanalyzer/11.6/admin/hostmanagement/actions/importhost.md) topic for additional information. @@ -31,11 +31,11 @@ or use the **Import** option. When the list is completed, click **Next**. **Step 3 –** On the Specify Host List Properties page, provide a unique descriptive **Host List Name**. -- There cannot be two host lists with the same name. Enterprise Auditor automatically appends a +- There can't be two host lists with the same name. Enterprise Auditor automatically appends a numeral to the end of a host list name to avoid duplicates. -**Step 4 –** On the Specify Host List Properties page, configure when inventory fields should be -refreshed for hosts in the list and set the credentials to use to conduct the host inventory. +**Step 4 –** On the Specify Host List Properties page, configure when to refresh inventory fields +for hosts in the list and set the credentials to use to conduct the host inventory. - Refresh inventory every time when the host discovery query completes – Automates the host inventory process and is dependent on the **Settings** > **Host Inventory** node configuration for @@ -57,5 +57,5 @@ refreshed for hosts in the list and set the credentials to use to conduct the ho **Step 5 –** Click **Finish** to save the host list and close the Host Lost Wizard. The new list displays at the bottom of the host lists under the **Host Management** node in the -Navigation pane. Every host added is included in the host master table at the Host Management node -as well as in the newly created host list. +Navigation pane. Enterprise Auditor includes every added host in the host master table at the Host +Management node as well as in the newly created host list. diff --git a/docs/accessanalyzer/11.6/admin/hostmanagement/actions/deletehost.md b/docs/accessanalyzer/11.6/admin/hostmanagement/actions/deletehost.md index c077bbfc3f..e3f235175f 100644 --- a/docs/accessanalyzer/11.6/admin/hostmanagement/actions/deletehost.md +++ b/docs/accessanalyzer/11.6/admin/hostmanagement/actions/deletehost.md @@ -4,24 +4,24 @@ description: "Delete Host(s)" sidebar_position: 30 --- -# Delete Host(s) +# Delete Hosts -Use the **Delete Host(s)** option at the **Host Management** node to permanently delete a host from +Use the **Delete Hosts** option at the **Host Management** node to permanently delete a host from the master host table, or at an individual host list node to remove the host from the selected list. ## Delete From Host Management Node -Follow the steps to delete a host from the Host Management node. +To delete a host from the Host Management node: **Step 1 –** In the Host Management node, select the host in the data grid and click **Delete -Host(s)** on the Activities pane. +Hosts** on the Activities pane. ![Confirm dialog box](/images/accessanalyzer/11.6/admin/hostmanagement/actions/confirmdeletehost.webp) :::warning -A deletion from the host master table at the Host Management node cannot be undone, as +A deletion from the host master table at the Host Management node can't be undone, as it deletes it from the host management database tables. It also removes the host from any host list -to which it has been assigned. Click **Cancel** to stop the deletion. +it's assigned to. Click **Cancel** to stop the deletion. ::: @@ -32,9 +32,9 @@ The host is no longer in the master host table. ## Delete From Individual Host List -Follow the steps to delete a host from an individual host list. +To delete a host from an individual host list: -**Step 1 –** In the host list, select the host in the data grid and click **Delete Host(s)** on the +**Step 1 –** In the host list, select the host in the data grid and click **Delete Hosts** on the Activities pane. ![Confirm dialog box](/images/accessanalyzer/11.6/admin/hostmanagement/actions/confirmdeletehost.webp) @@ -42,18 +42,18 @@ Activities pane. **Step 2 –** A dialog box asks for confirmation of the action. Click **OK** to proceed with the deletion. -Enterprise Auditor checks to see if the host exists in any other static host lists. If so, the -deletion is limited to removing the selected host from the current host list. +Enterprise Auditor checks to see if the host exists in any other static host lists. If so, +Enterprise Auditor limits the deletion to removing the selected host from the current host list. ![Confirm deletion from master host table dialog box](/images/accessanalyzer/11.6/admin/hostmanagement/actions/confirmdeletehostmaster.webp) :::warning -A deletion from the host master table cannot be undone, as it deletes it from the host +A deletion from the host master table can't be undone, as it deletes it from the host management database tables. ::: -**Step 3 –** If the host is not found in another static host list, Enterprise Auditor asks if you +**Step 3 –** If Enterprise Auditor doesn't find the host in another static host list, it asks if you also want to remove the host from the Host Master Table. On the Confirm dialog, select the desired action. diff --git a/docs/accessanalyzer/11.6/admin/hostmanagement/actions/deletelist.md b/docs/accessanalyzer/11.6/admin/hostmanagement/actions/deletelist.md index 641ddd860d..c5cf628389 100644 --- a/docs/accessanalyzer/11.6/admin/hostmanagement/actions/deletelist.md +++ b/docs/accessanalyzer/11.6/admin/hostmanagement/actions/deletelist.md @@ -10,7 +10,7 @@ Use the **Delete List** option to remove the selected list. This option is avail individual host list node. :::info -Before deleting a host list, first ensure it is not assigned to a job. +Before deleting a host list, first ensure no job uses it. ::: @@ -19,26 +19,26 @@ Before deleting a host list, first ensure it is not assigned to a job. ![Confirm dialog box](/images/accessanalyzer/11.6/admin/hostmanagement/actions/confirmdeletelist.webp) :::warning -This action cannot be undone. Click **Cancel** to stop the deletion. +This action can't be undone. Click **Cancel** to stop the deletion. ::: **Step 2 –** On the Confirm dialog box, click **OK** to continue with the deletion. -Enterprise Auditor checks to see if any hosts within the host list are found in any other static +Enterprise Auditor checks to see if any hosts within the host list exist in any other static host lists. ![Confirm deletion of orphaned hosts from master host table dialog box](/images/accessanalyzer/11.6/admin/hostmanagement/actions/confirmdeletelistmaster.webp) -**Step 3 –** If no hosts are found in any other host list, then Enterprise Auditor asks if you want -to remove the host from the master host table. On the Confirm dialog box, select the desired option. +**Step 3 –** If Enterprise Auditor doesn't find any hosts in another host list, it asks if you want +to remove the host from the master host table. On the Confirm dialog box, select the option you want. - Yes – Deletes the specified host from the master host table -- No – Does not delete the specified host from the master host table -- No to All – Does not delete other hosts that are not found in another static host list from the +- No – Doesn't delete the specified host from the master host table +- No to All – Doesn't delete other hosts that aren't found in another static host list from the master host table - Yes to All – Deletes other hosts not found in any other static host list from the master host table When the operation is complete, the list is no longer visible under the Host Management node in the -Navigation pane and it cannot be used to execute jobs against. +Navigation pane and you can't use it to execute jobs against. diff --git a/docs/accessanalyzer/11.6/admin/hostmanagement/actions/editlist.md b/docs/accessanalyzer/11.6/admin/hostmanagement/actions/editlist.md index eae811a35a..4a71ff6895 100644 --- a/docs/accessanalyzer/11.6/admin/hostmanagement/actions/editlist.md +++ b/docs/accessanalyzer/11.6/admin/hostmanagement/actions/editlist.md @@ -19,7 +19,7 @@ the Specify Host List Properties page where you can modify the following: - Host List Name :::warning - Changing the name of a host list that has been assigned to a job can cause the job + Changing the name of a host list assigned to a job can cause the job to fail. ::: diff --git a/docs/accessanalyzer/11.6/admin/hostmanagement/actions/editquery.md b/docs/accessanalyzer/11.6/admin/hostmanagement/actions/editquery.md index 74d076325b..42058596f6 100644 --- a/docs/accessanalyzer/11.6/admin/hostmanagement/actions/editquery.md +++ b/docs/accessanalyzer/11.6/admin/hostmanagement/actions/editquery.md @@ -11,7 +11,7 @@ Use the **Edit Query** option to modify host lists created by a Host Discovery q ![Edit Query option on Activities pane](/images/accessanalyzer/11.6/admin/hostmanagement/actions/editquery.webp) In the Navigation pane, select the query-created host list to edit and click **Edit Query**. The -Host Discovery Wizard opens to the Query page where the query settings for the selected -query-created host list are modified. See the +Host Discovery Wizard opens to the Query page, where you can modify the query settings for the +selected query-created host list. See the [Host Discovery Wizard](/docs/accessanalyzer/11.6/admin/hostdiscovery/wizard/overview.md) topic for information on modifying these settings. diff --git a/docs/accessanalyzer/11.6/admin/hostmanagement/actions/export.md b/docs/accessanalyzer/11.6/admin/hostmanagement/actions/export.md index 091d0a0703..88d627a375 100644 --- a/docs/accessanalyzer/11.6/admin/hostmanagement/actions/export.md +++ b/docs/accessanalyzer/11.6/admin/hostmanagement/actions/export.md @@ -7,7 +7,7 @@ sidebar_position: 70 # Export Data Use the **Export Data** option to export all information available in the current grid view for the -selected host list to a HTML, XML , or CSV file. Follow the steps to export data. +selected host list to a HTML, XML , or CSV file. To export data: **Step 1 –** Select the Host Management or individual host list node to export data from, and configure the data grid to contain all the columns you want to export. See the diff --git a/docs/accessanalyzer/11.6/admin/hostmanagement/actions/importhost.md b/docs/accessanalyzer/11.6/admin/hostmanagement/actions/importhost.md index 695b062a59..f4e890c4b6 100644 --- a/docs/accessanalyzer/11.6/admin/hostmanagement/actions/importhost.md +++ b/docs/accessanalyzer/11.6/admin/hostmanagement/actions/importhost.md @@ -6,10 +6,10 @@ sidebar_position: 20 # Import Hosts Option -On the Manual Host Entry page of the Host List Wizard, the **Import** option allows hosts to be -imported from either a CSV file or a database into the host list being created. +On the Manual Host Entry page of the Host List Wizard, the **Import** option lets you import hosts +from either a CSV file or a database into the host list you're creating. -Follow the steps to import hosts. +To import hosts: ![Import option on the Manual Host Entry page of the Host List Wizard](/images/accessanalyzer/11.6/admin/hostmanagement/actions/hostlistwizardimport.webp) @@ -28,11 +28,11 @@ step. - CSV File - - File Name – Click the ellipsis (**…**) to open a browser window and select the CSV file. This - file needs to be stored on the Enterprise Auditor Console server. Once selected, a preview of - the file is shown in the preview box. + - File Name – Click the ellipsis (**…**) to open a browser window and select the CSV file. You + must store this file on the Enterprise Auditor Console server. Once selected, the preview box + shows a preview of the file. - Includes header row – Select this checkbox if the file contains a header row. Otherwise, the - header row will be included in the import (visible within the preview box). + import includes the header row (visible within the preview box). ![Import Hosts window for importing from Database](/images/accessanalyzer/11.6/admin/hostmanagement/actions/importhostsdatabase.webp) @@ -45,23 +45,23 @@ step. topic for additional information. :::note - The Provider, Advanced, and All tabs of the Data Link Properties window should not - be modified. + Don't modify the Provider, Advanced, and All tabs of the Data Link Properties window. ::: - - Table – Use the dropdown to select the table that contains the hosts to be imported. A preview - of the selected table is displayed in the preview box. + - Table – Use the dropdown to select the table that contains the hosts to be imported. The + preview box displays a preview of the selected table. -**Step 4 –** Use either the drop-down menu or click on the column in the preview box to select the -column containing the host names. The selected column is highlighted in the preview box. +**Step 4 –** Use either the dropdown menu or click the column in the preview box to select the +column containing the host names. The preview box highlights the selected column. **Step 5 –** Click **OK** to complete the import. ![Imported hosts added in the Host list box on the Manual Host Entry page of the Host List Wizard](/images/accessanalyzer/11.6/admin/hostmanagement/actions/importhostscomplete.webp) -The Import Hosts window closes, and the imported list of host names is added in the Host list box on -the Manual Host Entry page of the Host List Wizard. Click **Next** to proceed with configuring the +The Import Hosts window closes, and Enterprise Auditor adds the imported list of host names to the +Host list box on the Manual Host Entry page of the Host List Wizard. Click **Next** to proceed with +configuring the host list. See the [Add Hosts](/docs/accessanalyzer/11.6/admin/hostmanagement/actions/add.md) topic for additional information on the Host List Wizard. diff --git a/docs/accessanalyzer/11.6/admin/hostmanagement/actions/importlocation.md b/docs/accessanalyzer/11.6/admin/hostmanagement/actions/importlocation.md index 00e1311559..2a98ff2f18 100644 --- a/docs/accessanalyzer/11.6/admin/hostmanagement/actions/importlocation.md +++ b/docs/accessanalyzer/11.6/admin/hostmanagement/actions/importlocation.md @@ -12,14 +12,14 @@ database without creating a new host list. See the [Host Inventory Data Grid](/docs/accessanalyzer/11.6/admin/hostmanagement/datagrid.md) topic for information on the Location column of host inventory. -Follow the steps to import physical location data for hosts. +To import physical location data for hosts: **Step 1 –** Ensure the import source file has columns for both the host name as it is identified within Enterprise Auditor and the location. :::note -When a host name does not match any existing hosts within the Host Master Table, it can be -added as a new host. +When a host name doesn't match any existing hosts within the Host Master Table, Enterprise Auditor +can add it as a new host. ::: @@ -37,11 +37,11 @@ step. - CSV File - - File Name – Click the ellipsis (**…**) to open a browser window and select the CSV file. This - file needs to be stored on the Enterprise Auditor Console server. Once selected, a preview of - the file is shown in the preview box. + - File Name – Click the ellipsis (**…**) to open a browser window and select the CSV file. You + must store this file on the Enterprise Auditor Console server. Once selected, the preview box + shows a preview of the file. - Includes header row – Select this checkbox if the file contains a header row. Otherwise, the - header row will be included in the import (visible within the preview box). + import includes the header row (visible within the preview box). - Database @@ -52,33 +52,32 @@ step. topic for additional information. :::note - The Provider, Advanced, and All tabs of the Data Link Properties window should not - be modified. + Don't modify the Provider, Advanced, and All tabs of the Data Link Properties window. ::: - - Table – Use the dropdown to select the table that contains the hosts to be imported. A preview - of the selected table is displayed in the preview box. + - Table – Use the dropdown to select the table that contains the hosts to be imported. The + preview box displays a preview of the selected table. -**Step 5 –** Use either the drop-down menu or click on the column in the preview box to select the -column containing the host names. The selected column is highlighted in the preview box. +**Step 5 –** Use either the dropdown menu or click the column in the preview box to select the +column containing the host names. The preview box highlights the selected column. ![Import Hosts window Location column selection](/images/accessanalyzer/11.6/admin/hostmanagement/actions/importlocationcsv.webp) -**Step 6 –** Use the **Import column** drop-down menu to select the column containing the location -information. The selected column is highlighted a lighter color in the preview box. +**Step 6 –** Use the **Import column** dropdown menu to select the column containing the location +information. The preview box highlights the selected column in a lighter color. **Step 7 –** Click **OK** to complete the import. ![Imported Location column data in the data grid](/images/accessanalyzer/11.6/admin/hostmanagement/actions/importlocationcomplete.webp) The Location column now contains the imported information. If any of the hosts included in the -import file are not already in the Host Master Table, Enterprise Auditor prompts for confirmation on -whether or not to import the host. Selecting **Yes** or **Yes to All** adds the new hosts to the +import file aren't already in the Host Master Table, Enterprise Auditor prompts for confirmation on +whether to import the host. Selecting **Yes** or **Yes to All** adds the new hosts to the Host Master Table but not to any individual host lists. :::note -Any new hosts that match dynamic host list criteria will be added to the appropriate +Enterprise Auditor adds any new hosts that match dynamic host list criteria to the appropriate dynamic host lists. ::: diff --git a/docs/accessanalyzer/11.6/admin/hostmanagement/actions/overview.md b/docs/accessanalyzer/11.6/admin/hostmanagement/actions/overview.md index 4d37a94089..9d902005f0 100644 --- a/docs/accessanalyzer/11.6/admin/hostmanagement/actions/overview.md +++ b/docs/accessanalyzer/11.6/admin/hostmanagement/actions/overview.md @@ -20,9 +20,9 @@ The available actions are: the Host Management node) - [View/Edit Host](/docs/accessanalyzer/11.6/admin/hostmanagement/actions/viewhost.md) – Open the Host Details View, which displays the collected host inventory information for the - selected host in an easier-to-read format and allows you to manually edit the host inventory + selected host in an easier-to-read format and lets you manually edit the host inventory information -- [Delete Host(s)](/docs/accessanalyzer/11.6/admin/hostmanagement/actions/deletehost.md) +- [Delete Hosts](/docs/accessanalyzer/11.6/admin/hostmanagement/actions/deletehost.md) – Delete host from the selected list (permanently deletes host from the host master table if used in the Host Management node) - [Import Location](/docs/accessanalyzer/11.6/admin/hostmanagement/actions/importlocation.md) @@ -58,7 +58,7 @@ Activities available only at the individual host list nodes are: - [Edit Query](/docs/accessanalyzer/11.6/admin/hostmanagement/actions/editquery.md) – Edit the Host Discovery query settings for the selected query-created host list - [Rename List](/docs/accessanalyzer/11.6/admin/hostmanagement/actions/rename.md) - – Rename the selected host list (should not be used if the host list has already been assigned to + – Rename the selected host list (shouldn't be used if the host list has already been assigned to a job for execution) - [Delete List](/docs/accessanalyzer/11.6/admin/hostmanagement/actions/deletelist.md) – Delete the selected host list diff --git a/docs/accessanalyzer/11.6/admin/hostmanagement/actions/refresh.md b/docs/accessanalyzer/11.6/admin/hostmanagement/actions/refresh.md index 17f14e4b59..2fed8dcc2e 100644 --- a/docs/accessanalyzer/11.6/admin/hostmanagement/actions/refresh.md +++ b/docs/accessanalyzer/11.6/admin/hostmanagement/actions/refresh.md @@ -6,7 +6,7 @@ sidebar_position: 90 # Refresh Hosts -Use the **Refresh Hosts** option to manually execute the Host Inventory query. It can be selected +Use the **Refresh Hosts** option to manually execute the Host Inventory query. You can select it for the following: - All hosts – Use from the Host Management node @@ -21,4 +21,4 @@ Select the hosts or host list to inventory and then click **Refresh Hosts** in t ![Refresh Hosts Confirm dialog](/images/accessanalyzer/11.6/admin/hostmanagement/actions/refreshhostsconfirm.webp) -When only particular hosts are selected in a list, a dialog box asks for confirmation of the action. +When you select only particular hosts in a list, a dialog box asks for confirmation of the action. diff --git a/docs/accessanalyzer/11.6/admin/hostmanagement/actions/rename.md b/docs/accessanalyzer/11.6/admin/hostmanagement/actions/rename.md index 976f3a0ae4..5af8fa52b9 100644 --- a/docs/accessanalyzer/11.6/admin/hostmanagement/actions/rename.md +++ b/docs/accessanalyzer/11.6/admin/hostmanagement/actions/rename.md @@ -10,7 +10,7 @@ Use the Rename List option to change the name of a selected host list. This opti from an individual host list node. :::warning -Changing the name on a host list that has been assigned to a job can cause the job to +Changing the name on a host list assigned to a job can cause the job to fail. ::: @@ -21,7 +21,7 @@ Select the host list to rename and click **Rename List** to open the Host list n the new name for the host list and click **OK**. :::note -Host list names can also be changed using the **Edit List** option, see the +You can also change host list names using the **Edit List** option. See the [Edit List](/docs/accessanalyzer/11.6/admin/hostmanagement/actions/editlist.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/admin/hostmanagement/actions/savetolist.md b/docs/accessanalyzer/11.6/admin/hostmanagement/actions/savetolist.md index 13fe5591a1..c813ee25f2 100644 --- a/docs/accessanalyzer/11.6/admin/hostmanagement/actions/savetolist.md +++ b/docs/accessanalyzer/11.6/admin/hostmanagement/actions/savetolist.md @@ -9,8 +9,8 @@ sidebar_position: 120 Use the **Save Selected To List** option to create a static host list. This option is available from either the Host Management node or an individual host list node. See the [Static Host Lists](/docs/accessanalyzer/11.6/admin/hostmanagement/lists.md#static-host-lists) -topic for additional information on static host lists. This option is inactive until at least one -host within the data grid is selected. +topic for additional information on static host lists. This option is inactive until you select at +least one host within the data grid. ![Save Selected To List option in Host Management node](/images/accessanalyzer/11.6/admin/hostmanagement/actions/savetolist.webp) diff --git a/docs/accessanalyzer/11.6/admin/hostmanagement/actions/saveview.md b/docs/accessanalyzer/11.6/admin/hostmanagement/actions/saveview.md index dd0a4525be..88eb7484b7 100644 --- a/docs/accessanalyzer/11.6/admin/hostmanagement/actions/saveview.md +++ b/docs/accessanalyzer/11.6/admin/hostmanagement/actions/saveview.md @@ -8,11 +8,11 @@ sidebar_position: 110 Use the **Save Current View** option to create a dynamic host list. This option is available from either the Host Management node or an individual host list node. The option is inactive until you -apply a filter to the data grid. Follow the steps to create a dynamic host list. +apply a filter to the data grid. To create a dynamic host list: **Step 1 –** Select the Host Management or individual host list node to create the host list from. -**Step 2 –** Filter the data grid for the desired criteria. See the +**Step 2 –** Filter the data grid for the criteria you want. See the [Host Inventory Data Grid](/docs/accessanalyzer/11.6/admin/hostmanagement/datagrid.md) topic for additional information. @@ -27,12 +27,12 @@ and click **OK**. The new host list displays under the Host Management node. When the Enterprise Auditor Console closes the host lists under the Host Management node, the hosts reorganize in alphanumeric order. -Like the default host lists, custom dynamic host lists are auto-populated and updated according to -host inventory. +Like the default host lists, Enterprise Auditor auto-populates and updates custom dynamic host lists +according to host inventory. :::info -Do not modify the criteria once a dynamic based list has been created. It is -better to delete and recreate the list in order to modify a dynamic-based list. +Don't modify the criteria once you've created a dynamic-based list. To modify a dynamic-based list, +delete and recreate it instead. ::: diff --git a/docs/accessanalyzer/11.6/admin/hostmanagement/actions/suspend.md b/docs/accessanalyzer/11.6/admin/hostmanagement/actions/suspend.md index 699200272d..860a726d77 100644 --- a/docs/accessanalyzer/11.6/admin/hostmanagement/actions/suspend.md +++ b/docs/accessanalyzer/11.6/admin/hostmanagement/actions/suspend.md @@ -14,7 +14,7 @@ Once clicked, the option changes to **Resume Host Inventory** and the **In progr inventories change to an **In queue** state. :::note -Clicking **Refresh Hosts** while inventory is suspended adds to the queue but does not +Clicking **Refresh Hosts** while inventory is suspended adds to the queue but doesn't resume the inventory. ::: diff --git a/docs/accessanalyzer/11.6/admin/hostmanagement/datagrid.md b/docs/accessanalyzer/11.6/admin/hostmanagement/datagrid.md index b45c972394..edd9d9a96a 100644 --- a/docs/accessanalyzer/11.6/admin/hostmanagement/datagrid.md +++ b/docs/accessanalyzer/11.6/admin/hostmanagement/datagrid.md @@ -13,7 +13,7 @@ topic for information on host lists. ![Host Inventory Data Grid](/images/accessanalyzer/11.6/admin/hostmanagement/datagrid.webp) -The icon for each host entry is an indicator of its inventory state: +The icon for each host entry indicates its inventory state: | Icon | Inventory State | | ---------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | @@ -32,10 +32,10 @@ Use the horizontal scrollbar at the bottom to view the host inventory data, whic queue**) :::note - If the Enterprise Auditor application is stopped during host inventory collection, + If the Enterprise Auditor application stops during host inventory collection, hosts queued for inventory retain the **InventoryState** of **In queue** within the Host Management node data grid, as this is the last known state of inventory. It retains that state - until the next host inventory collection is executed against the host. + until the next host inventory collection runs against the host. ::: diff --git a/docs/accessanalyzer/11.6/admin/hostmanagement/lists.md b/docs/accessanalyzer/11.6/admin/hostmanagement/lists.md index 36a75bb4ba..cd2d63bfcd 100644 --- a/docs/accessanalyzer/11.6/admin/hostmanagement/lists.md +++ b/docs/accessanalyzer/11.6/admin/hostmanagement/lists.md @@ -6,7 +6,7 @@ sidebar_position: 20 # Hosts Lists -A host list is a grouping of hosts for the purpose of executing jobs against. Every host list +A host list is a grouping of hosts to execute jobs against. Every host list created can be accessed by expanding the **Host Management** node in the Navigation pane. ![Host Management Node in the Jobs Tree](/images/accessanalyzer/11.6/admin/hostmanagement/jobstree.webp) @@ -44,26 +44,26 @@ both the default host lists and custom created dynamic host lists. See the topic for a list of the default host lists and instructions on controlling which of these lists are visible under the Host Management node. -Custom dynamic host lists are created by filtering the data grid and using the +Create custom dynamic host lists by filtering the data grid and using the [Save Current View](/docs/accessanalyzer/11.6/admin/hostmanagement/actions/saveview.md) -option in the Activities pane or right-click menu. This can be done at the Host Management node with +option in the Activities pane or right-click menu, either at the Host Management node with the Host Master Table or at any host list node. See the [Filter](/docs/accessanalyzer/11.6/admin/navigate/datagrid.md#filter) topic for additional information on filtering data grids. :::info -Do not modify the criteria once a dynamic based list has been created. It is -better to delete and recreate the list in order to modify a dynamic-based list. +Don't modify the criteria after you create a dynamic-based list. To modify a +dynamic-based list, delete and recreate it instead. ::: ## Static Host Lists -Static host lists are created either through host discovery queries or manually entered within the +You create static host lists either through host discovery queries or by manually entering them within the **Host Management** node. Lists created by [Host Discovery Node](/docs/accessanalyzer/11.6/admin/hostdiscovery/overview.md) queries are updated each time the query is run, manually or scheduled. Other static host lists can -only be changed manually. Custom host lists are frequently created in order to scope a job to +only be changed manually. You frequently create custom host lists to scope a job to execute against a select set of hosts. For example, a user running the Exchange Solution might create a list to just run Mailbox queries @@ -75,8 +75,8 @@ There are two common ways to create static host lists: - Use the [Add Hosts](/docs/accessanalyzer/11.6/admin/hostmanagement/actions/add.md) option in the Activities pane or right-click menu to access the Host List Wizard -- Select multiple hosts from the data grid using the Windows Ctrl and left-click function. This can - be done from the Host Mast Table or any host list under the Host Management node. Then use the +- Select multiple hosts from the data grid using the Windows Ctrl and left-click function, from the + Host Mast Table or any host list under the Host Management node. Then use the [Save Selected To List](/docs/accessanalyzer/11.6/admin/hostmanagement/actions/savetolist.md) option in the Activities pane or right-click menu to open the Host List Wizard with a pre-filled in Manual Host Entry page. diff --git a/docs/accessanalyzer/11.6/admin/hostmanagement/overview.md b/docs/accessanalyzer/11.6/admin/hostmanagement/overview.md index 908049bc2d..ea4ca468e7 100644 --- a/docs/accessanalyzer/11.6/admin/hostmanagement/overview.md +++ b/docs/accessanalyzer/11.6/admin/hostmanagement/overview.md @@ -6,8 +6,8 @@ sidebar_position: 30 # Host Management -The **Host Management** node is used to manage hosts in a targeted environment. Hosts configured -under the **Host Management** node can be audited using other features in Enterprise Auditor. This +Use the **Host Management** node to manage hosts in a targeted environment. You can audit hosts +configured under the **Host Management** node using other features in Enterprise Auditor. This node maintains information for audited computers. To view information on all computers in the environment, use the [.Active Directory Inventory Solution](/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/overview.md), @@ -16,7 +16,7 @@ specifically the Active Directory Summary report. The Host Management node provides a master list of every host ever introduced to Enterprise Auditor. Introduce hosts through [Host Discovery Node](/docs/accessanalyzer/11.6/admin/hostdiscovery/overview.md) -queries or by entering them manually. Hosts are removed from this list only by manually deleting +queries or by entering them manually. You can only remove hosts from this list by manually deleting them. This master listing of hosts, or the Host Master Table, is designed around unique host names, not necessarily unique hosts themselves. The data grid provides all host inventory information collected on the hosts. See the diff --git a/docs/accessanalyzer/11.6/admin/jobs/features.md b/docs/accessanalyzer/11.6/admin/jobs/features.md index a50c9acbec..69fb080e18 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/features.md +++ b/docs/accessanalyzer/11.6/admin/jobs/features.md @@ -11,8 +11,8 @@ Enterprise Auditor users should be familiar. **View XML Files** -Job, query, analysis, and action property windows all have the **View XML** option. These provide -the ability to edit through an XML text window. +Job, query, analysis, and action property windows all have the **View XML** option. These let you +edit through an XML text window. **Open Explore Folder** @@ -21,20 +21,20 @@ using the **Explore Folder** option in the right-click menu. **Publish Reports after Report Generation** -Reports that have been generated but not published can be sent to the Web Console using the +Send reports that have been generated but not published to the Web Console using the **Publish** option in the right-click menu from the selected Jobs tree, job group, or job node. See the [Publish Reports Window](#publish-reports-window) topic for additional information. **Job Configuration Change Tracking** -Jobs configuration changes can be tracked using the **Changes** option in the right-click menu from +Track job configuration changes using the **Changes** option in the right-click menu from the selected Jobs tree, job group, or job node. See the [Changes Window](/docs/accessanalyzer/11.6/admin/jobs/overview.md#changes-window) topic for additional information. **Job Export** -Jobs can be exported to a ZIP file using the **Export** option in the right-click menu from the +Export jobs to a ZIP file using the **Export** option in the right-click menu from the selected job group or job node. See the [Export Job to Zip Archive Window](#export-job-to-zip-archive-window) topic for additional information. @@ -62,33 +62,33 @@ There are two options for where to save the ZIP file: - Save in the exported folder – Saves the file in the job’s directory, for example `%sainstalldir%Jobs\GROUP_.Active Directory Inventory\.Active Directory Inventory.zip` -- Save in the following location – Allows you to either type or browse to the desired save location +- Save in the following location – Enter or browse to the save location you want -The **Email this archive**checkbox provides the opportunity to send an email notification with the +The **Email this archive**checkbox lets you send an email notification with the attached ZIP file. ![Support Email window](/images/accessanalyzer/11.6/admin/jobs/supportemail.webp) When the archive has been created, the Enterprise Auditor Support Email window opens. By default, -the recipient is set to [Netwrix Support](https://www.netwrix.com/support.html) but it can be -modified prior to sending. Additional recipients can be added, and the Subject and email body can be -modified. +the recipient is set to [Netwrix Support](https://www.netwrix.com/support.html) but you can +modify it before sending. You can also add additional recipients and modify the Subject and email +body. ## Publish Reports Window -The **Publish Reports** wizard allows you to better manage the list of reports published to the Web +Use the **Publish Reports** wizard to better manage the list of reports published to the Web Console. -When you right-click on a job group or job and select **Publish**, the Publish Reports wizard opens. +When you right-click a job group or job and select **Publish**, the Publish Reports wizard opens. You can choose the list of reports to be published or removed from the Web Console. -Follow the steps to publish the reports. +To publish the reports: -**Step 1 –** Right-click on a job group or job and select **Publish** from the drop-down list. +**Step 1 –** Right-click a job group or job and select **Publish** from the dropdown list. ![Publish Reports wizard Action Type page](/images/accessanalyzer/11.6/admin/jobs/publishreportsactiontype.webp) -**Step 2 –** On the Action Type page, select the type of action to be performed on the reports and +**Step 2 –** On the Action Type page, select the type of action to perform on the reports and click **Next**: - Publish Reports @@ -96,13 +96,13 @@ click **Next**: ![Publish Reports wizard Report Tree page](/images/accessanalyzer/11.6/admin/jobs/publishreportsreporttree.webp) -**Step 3 –** On the Report Tree page, select the reports to be published or removed (depending on -the Action Type selected in the previous step). Click **Next** to proceed with the action. +**Step 3 –** On the Report Tree page, select the reports to publish or remove (depending on +the Action Type you selected in the previous step). Click **Next** to proceed with the action. **Step 4 –** The Progress page shows you the status of the action. When it has completed, click **Finish** to exit the wizard. -Published reports can be viewed under the **[Job]** > **Results** node or through the Web Console. +You can view published reports under the **[Job]** > **Results** node or through the Web Console. See the [Reporting](/docs/accessanalyzer/11.6/admin/report/overview.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/admin/jobs/group/overview.md b/docs/accessanalyzer/11.6/admin/jobs/group/overview.md index 538bb39452..8a68211767 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/group/overview.md +++ b/docs/accessanalyzer/11.6/admin/jobs/group/overview.md @@ -6,8 +6,8 @@ sidebar_position: 10 # Job Groups -Job groups are designed to manage related jobs and can contain sub-job groups to ensure that related -jobs are executed in the correct order. To create a new job group, right-click on the desired +Job groups manage related jobs and can contain sub-job groups to ensure that related +jobs execute in the correct order. To create a new job group, right-click the desired location (Jobs tree or another job group) and select **Create Group**. Then provide a unique, descriptive name taking into consideration the alphanumeric ordering of the Jobs tree. @@ -16,7 +16,7 @@ descriptive name taking into consideration the alphanumeric ordering of the Jobs Job groups are organized similar to the Jobs tree, with the Settings node at the top, followed by sub-job groups (job group for collection first, if applicable), then followed by analysis and reporting jobs. Both are sorted in alphanumeric order. This is necessary because data collection -jobs must run prior to the analysis and reporting jobs that rely on the collected data without +jobs must run before the analysis and reporting jobs that rely on the collected data without consideration to the job’s name (alphanumeric order). ## Job Group Description Page @@ -43,13 +43,13 @@ Job Library, and creating a job. Pre-configured job group description pages provide users with shortcuts and links to many of the -functions that can be accessed in the Jobs Tree in the Navigation Pane. +functions you can access in the Jobs Tree in the Navigation Pane. ![Job Group Description page](/images/accessanalyzer/11.6/admin/jobs/group/descriptionpage.webp) The sections of the job group description page are: -- Job Group Settings Shortcuts – These pages can also be accessed through the job group Settings +- Job Group Settings Shortcuts – You can also access these pages through the job group Settings Nodes in the Navigation Pane. See the [Job Groups Settings Node](/docs/accessanalyzer/11.6/admin/jobs/group/settings/settings.md) topic for additional information. @@ -62,11 +62,11 @@ The sections of the job group description page are: - Help – Opens the [Netwrix Technical Knowledge Center](https://helpcenter.netwrix.com/) in a browser to a relevant landing page for the job group -- Run Now – Runs the currently selected job group +- Run Now – Runs the selected job group - Schedule – Opens the Schedule page to schedule the job group - Open Folder – Opens the job group’s folder location with supporting files in the Windows Explorer -- Create Group – Creates a job group within the currently selected job group -- Create Job – Creates a job within the currently selected Job +- Create Group – Creates a job group within the selected job group +- Create Job – Creates a job within the selected Job - Add Instant Job – Add an Instant Job using the Instant Job Wizard. See the [Instant Job Wizard](/docs/accessanalyzer/11.6/admin/jobs/instantjobs/overview.md) topic for additional information. @@ -79,12 +79,12 @@ following information: - Assigned Host List – Hovering over the **Assigned Host List** button shows a tool-tip with information on the hosts lists are assigned to the job group - - Click on the **Assigned Host List** button to go to the Job Group's Host List Assignment node. + - Click the **Assigned Host List** button to go to the Job Group's Host List Assignment node. See the [Host Lists Assignment](/docs/accessanalyzer/11.6/admin/jobs/group/settings/hostlistsassignment.md) topic for additional information. -- Show Inherited Settings – Click on the **Show Inherited Settings** button to view information on +- Show Inherited Settings – Click the **Show Inherited Settings** button to view information on the following: - Connection Profile @@ -93,18 +93,18 @@ following information: - Reporting Settings - Storage Account -- Contents – Shows the job groups and jobs contained within the currently selected job group +- Contents – Shows the job groups and jobs contained within the selected job group :::note -If applicable, the page shows special instructions for which hosts need to be targeted for +If applicable, the page shows special instructions for which hosts to target for proper job group execution. ::: ### Job Settings: Inherited and Directly Applied -Job group settings can be applied directly or inherited. On the job group level, it is considered -that all settings are applied directly. +Job group settings can be applied directly or inherited. At the job group level, all settings +apply directly. ![Show Inherited Settings on Job Overview page](/images/accessanalyzer/11.6/admin/jobs/group/showinheritedsettings.webp) diff --git a/docs/accessanalyzer/11.6/admin/jobs/group/settings/connection.md b/docs/accessanalyzer/11.6/admin/jobs/group/settings/connection.md index 1a6535d771..a1192237e5 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/group/settings/connection.md +++ b/docs/accessanalyzer/11.6/admin/jobs/group/settings/connection.md @@ -16,8 +16,8 @@ level or a parent job group. See the [Connection](/docs/accessanalyzer/11.6/admin/settings/connection/overview.md) topic for additional information. -If the Default Setting is not preferred, select the custom type of connection settings desired -below: +If you don't want the default setting, select one of the following custom connection settings +types: - System default @@ -28,7 +28,7 @@ below: - Select one of the following user defined profiles - - Select a pre-configured Connection Profile from the drop-down menu + - Select a pre-configured Connection Profile from the dropdown menu Selecting the **Set all the child objects to inherit these settings** option forces inheritance of this setting to all sub-groups and jobs within the job group. When enabled, this option overrides diff --git a/docs/accessanalyzer/11.6/admin/jobs/group/settings/history.md b/docs/accessanalyzer/11.6/admin/jobs/group/settings/history.md index 48f5973d5e..a7e6a5445f 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/group/settings/history.md +++ b/docs/accessanalyzer/11.6/admin/jobs/group/settings/history.md @@ -17,12 +17,12 @@ By default, all job groups are set to inherit **Use Default Setting** option fro for additional information. :::warning -It is important to understand that some pre-configured jobs require history retention -while others do not support it. See job group and job descriptions for additional information. +Some pre-configured jobs require history retention +while others don't support it. See job group and job descriptions for additional information. ::: -If the Default Setting is not preferred, select the custom type of retention settings desired below: +If you don't want the default setting, select one of the following custom retention settings types: - Data Retention Period diff --git a/docs/accessanalyzer/11.6/admin/jobs/group/settings/hostlistsassignment.md b/docs/accessanalyzer/11.6/admin/jobs/group/settings/hostlistsassignment.md index ba757122e8..8ae6152036 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/group/settings/hostlistsassignment.md +++ b/docs/accessanalyzer/11.6/admin/jobs/group/settings/hostlistsassignment.md @@ -11,9 +11,9 @@ job group. ![Job Group Host Lists Assignment](/images/accessanalyzer/11.6/admin/jobs/group/hostlistassignment.webp) -At a top-level job group, there is no host list to be inherited. The **Use Default Settings** option -is grayed-out. However, a sub-job group can inherit host lists from a parent job group. Host lists -are configured through the **Host Management** node. See the +At a top-level job group, there is no host list to inherit. The **Use Default Settings** option +is grayed-out. However, a sub-job group can inherit host lists from a parent job group. You configure +host lists through the **Host Management** node. See the [Host Management](/docs/accessanalyzer/11.6/admin/hostmanagement/overview.md) topic for additional information. @@ -21,10 +21,10 @@ Several pre-defined solutions have default host lists already assigned to the so the .Active Directory Inventory Job Group has the Default domain controller assigned at the job group and inherited to the jobs. -Select the host lists to be targeted by the job group. The **Filter host lists by** feature scopes -the list to match the search string provided. At the bottom of the list is an indicator of how many -hosts lists have been selected out of the total number of hosts lists known to the Enterprise -Auditor Console. If a filter has been applied, there is also an indicator of how many host lists +Select the host lists to target for the job group. The **Filter host lists by** feature scopes +the list to match the search string provided. At the bottom of the list, an indicator shows how many +host lists you've selected out of the total number of host lists known to the Enterprise +Auditor Console. If you apply a filter, an indicator also shows how many host lists matched the search string. Selecting the **Set all the child objects to inherit these settings** option forces inheritance of diff --git a/docs/accessanalyzer/11.6/admin/jobs/group/settings/reporting.md b/docs/accessanalyzer/11.6/admin/jobs/group/settings/reporting.md index 13440faeb2..ff5590220a 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/group/settings/reporting.md +++ b/docs/accessanalyzer/11.6/admin/jobs/group/settings/reporting.md @@ -15,8 +15,8 @@ topic for additional information. :::note If the Role Based Access feature is enabled, it also displays a list of all accounts -granted access to the published reports via the Web Console that are generated by any jobs within -the job group. +granted access to the published reports via the Web Console that any jobs within +the job group generate. ::: diff --git a/docs/accessanalyzer/11.6/admin/jobs/group/settings/settings.md b/docs/accessanalyzer/11.6/admin/jobs/group/settings/settings.md index 43430b5e88..8524bdf3ab 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/group/settings/settings.md +++ b/docs/accessanalyzer/11.6/admin/jobs/group/settings/settings.md @@ -6,12 +6,12 @@ sidebar_position: 10 # Job Groups Settings Node -A job group’s Settings node is where custom configurations can be set and where the host lists are -assigned to a job group. +A job group’s Settings node is where you can set custom configurations and assign host lists to +a job group. ![Job group settings in the Jobs Tree](/images/accessanalyzer/11.6/admin/jobs/group/settings.webp) -These settings inherit the global settings down by default unless inheritance is broken at a job +These settings inherit the global settings down by default unless you break inheritance at a job group or a job level. - [Connection Node](/docs/accessanalyzer/11.6/admin/jobs/group/settings/connection.md) @@ -25,7 +25,7 @@ group or a job level. lists for this job group :::note - Host List Assignments is not a global setting. The pre-configured solutions may + Host List Assignments isn't a global setting. The pre-configured solutions may contain Host List Assignments configured to use Global Default Host Lists, for example All Domain Controllers. See the [Default Host Lists](/docs/accessanalyzer/11.6/admin/settings/hostinventory.md#default-host-lists) @@ -39,14 +39,14 @@ group or a job level. - [Storage Node](/docs/accessanalyzer/11.6/admin/jobs/group/settings/storage.md) – Use the default storage profile or break inheritance on where this job group's data is stored -If changes are made, click **Save** to implement the changes. Changes are not implemented unless -they are saved. +If you make changes, click **Save** to implement them. Changes aren't implemented unless +you save them. -**Host List Assignment** and **Connection** are the two settings that should always be confirmed +You should always confirm **Host List Assignment** and **Connection** before executing a job group or job when data collection is included. The assigned host lists -contains the hosts that are targeted by the job’s data collection queries. The assigned Connection -Profile must have the appropriate level of permissions in order for the data collection to be -successful. See the +contains the hosts that the job’s data collection queries target. The assigned Connection +Profile must have the appropriate level of permissions for the data collection to +succeed. See the [Permissions by Data Collector (Matrix)](/docs/accessanalyzer/11.6/admin/datacollector/permissionmatrix.md) -topic for information on the recommended permissions needed on the targeted hosts in order to +topic for information on the recommended permissions needed on the targeted hosts to collect data. diff --git a/docs/accessanalyzer/11.6/admin/jobs/group/settings/storage.md b/docs/accessanalyzer/11.6/admin/jobs/group/settings/storage.md index d00106cb2e..58ba3843e2 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/group/settings/storage.md +++ b/docs/accessanalyzer/11.6/admin/jobs/group/settings/storage.md @@ -14,9 +14,9 @@ topic for additional information. ![Job Group Storage Settings](/images/accessanalyzer/11.6/admin/jobs/group/storage.webp) By default, all job groups are set to inherit the **Use Default Profile** option from the global -level or a parent job group. If it is necessary for a job group to send data to a different +level or a parent job group. If a job group needs to send data to a different database, the Storage Profile must already exist at the global level. Select the **Use This -Profile** radio button and choose the non-default Storage Profile from the drop-down menu. +Profile** radio button and choose the non-default Storage Profile from the dropdown menu. Selecting the **Set all the child objects to inherit these settings** option forces inheritance of this setting to all sub-groups and jobs within the job group. When enabled, this option overrides diff --git a/docs/accessanalyzer/11.6/admin/jobs/instantiate.md b/docs/accessanalyzer/11.6/admin/jobs/instantiate.md index f78e06fc17..523019a785 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/instantiate.md +++ b/docs/accessanalyzer/11.6/admin/jobs/instantiate.md @@ -14,7 +14,7 @@ Jobs directory. The default location is: ![Explore Folder option from Jobs Tree](/images/accessanalyzer/11.6/admin/jobs/explorefolder.webp) -The folder is opened from within the Enterprise Auditor Console by right-clicking on the desired +Open the folder from within the Enterprise Auditor Console by right-clicking the desired **Jobs** node and selecting **Explore Folder**. ![Jobs folder in File Explorer](/images/accessanalyzer/11.6/admin/jobs/explorefolderfileexplorer.webp) @@ -23,21 +23,21 @@ The naming convention of the folders controls what is visible in the Jobs tree. prefix for all job groups. `JOB_` is the prefix for all jobs. Changing the prefix removes the object from the Jobs tree without deleting it. -Instantiating new, external jobs is as easy as copying and pasting the job or job group into this -location. However, copying an existing job within the Jobs directory is not supported. If the job +To instantiate new, external jobs, copy and paste the job or job group into this +location. However, copying an existing job within the Jobs directory isn't supported. If the job already exists within the Enterprise Auditor Console server, copying outside of the console may result in reporting issues. :::warning -Do not use these steps to copy an existing job. +Don't use these steps to copy an existing job. ::: There is no need to close the Enterprise Auditor application to instantiate a new job. Follow the steps to instantiate a new job into the Enterprise Auditor Jobs tree: -**Step 1 –** Obtain the job or job group to be instantiated. If it has been sent by Netwrix, a -colleague, or other entity, it is most likely in one of two formats: +**Step 1 –** Obtain the job or job group to instantiate. If Netwrix, a +colleague, or another entity sent it, it's most likely in one of two formats: - Archive (.zip, .rar, and so on) - Folder containing the job content (JOB*[name of job] or GROUP*[name of job group]) @@ -50,7 +50,7 @@ colleague, or other entity, it is most likely in one of two formats: ![Extract zip file contents to the Jobs folder](/images/accessanalyzer/11.6/admin/jobs/instantiateextract.webp) -- If in archive format, extract the desired content to the Jobs directory +- If in archive format, extract the content you want to the Jobs directory - Use the default path or specify a specific path using the browse button (…) - Select whether to **Show extracted files when complete**. This option is selected by default. @@ -64,7 +64,7 @@ match that of the jobs or job groups that are already there. ![Refresh Tree](/images/accessanalyzer/11.6/admin/jobs/refreshtree.webp) -**Step 4 –** In the Enterprise Auditor Console, right-click on the **Jobs** node and select +**Step 4 –** In the Enterprise Auditor Console, right-click the **Jobs** node and select **Refresh Tree**. ![Job displayed in the Jobs Tree](/images/accessanalyzer/11.6/admin/jobs/instantiatejobstree.webp) diff --git a/docs/accessanalyzer/11.6/admin/jobs/instantjobs/ad_passwordexpirationnotification.md b/docs/accessanalyzer/11.6/admin/jobs/instantjobs/ad_passwordexpirationnotification.md index ea767b3f60..af02433149 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/instantjobs/ad_passwordexpirationnotification.md +++ b/docs/accessanalyzer/11.6/admin/jobs/instantjobs/ad_passwordexpirationnotification.md @@ -7,10 +7,10 @@ sidebar_position: 10 # AD_PasswordExpirationNotification Job The AD_PasswordExpirationNotification Job determines when Active Directory user passwords are about -to expire and can be configured to send notifications to users prior to password expiration. It is +to expire, and you can configure it to send notifications to users before password expiration. It is available through the Instant Job Library under the Active Directory library. See the [Instant Job Wizard](/docs/accessanalyzer/11.6/admin/jobs/instantjobs/overview.md) -section for instructions to add this instant job into the Jobs tree. Since this job does not require +section for instructions to add this instant job into the Jobs tree. Since this job doesn't require a host to target, select Local host on the Hosts page of the Instant Job Wizard. ![AD_PasswordExpirationNotification job in the Jobs tree](/images/accessanalyzer/11.6/admin/jobs/instantjobs/jobstree_3.webp) @@ -26,8 +26,8 @@ Runtime Details: The AD_PasswordExpirationNotification Job runs analysis tasks that generate tables and configure password expiration notifications. It also generates a report on passwords expiring within a -specified parameter, by default within 15 days. If desired, notifications of password expiration can -be configured to send to a help desk email (through an analysis task) and to the user (through an +specified parameter, by default within 15 days. If desired, you can configure notifications of password expiration +to send to a help desk email (through an analysis task) and to the user (through an action task). ## Analysis Tasks for the AD_PasswordExpirationNotification Job @@ -44,7 +44,7 @@ The default analysis tasks are: - Contains a configurable parameter for the number of days until a password expires to be identified - See the - [Customizable Analysis Tasks for the AD_PasswordExpirationNotification Job](#customizable-analysis-tasks-for-the-ad_passwordexpirationnotification-job) + [Customizable Analysis Tasks for the AD_PasswordExpirationNotification Job](#customizable-analysis-tasks-for-the-adpasswordexpirationnotification-job) topic for additional information. - **2. Domain Summary** – Creates an interim processing table in the database for use by downstream analysis and report generation @@ -56,7 +56,7 @@ The default analysis tasks are: the job’s Results node - **5. Help Desk Notification** – Sends notification of users with passwords set to expire in X days - See the - [Notification Analysis Task in the AD_PasswordExpirationNotification Job](#notification-analysis-task-in-the-ad_passwordexpirationnotification-job) + [Notification Analysis Task in the AD_PasswordExpirationNotification Job](#notification-analysis-task-in-the-adpasswordexpirationnotification-job) topic for additional information. ## Action for the AD_PasswordExpirationNotification Job @@ -77,7 +77,7 @@ The default actions are: password expiration - Requires the Notification Actions license feature - See the - [Action Task in the AD_PasswordExpirationNotification Job](#action-task-in-the-ad_passwordexpirationnotification-job) + [Action Task in the AD_PasswordExpirationNotification Job](#action-task-in-the-adpasswordexpirationnotification-job) topic for additional information. In addition to the tables created by the analysis and action tasks, the @@ -91,12 +91,12 @@ AD_PasswordExpirationNotification Job produces the following pre-configured repo ## Customizable Analysis Tasks for the AD_PasswordExpirationNotification Job Customizable parameters enable Enterprise Auditor users to set the values used to classify user and -group objects during this job’s analysis. The parameters can be customized and are listed in a -section at the bottom of the SQL Script Editor. Follow the steps to customize an analysis task’s -parameters. +group objects during this job’s analysis. You can customize the parameters, which appear in a +section at the bottom of the SQL Script Editor. To customize an analysis task’s +parameters: :::warning -Do not change the table names or report name to align with a different value supplied +Don't change the table names or report name to align with a different value supplied for this parameter. Modifying the table names will result in analysis and report errors downstream. Only the report title and descriptions can be modified within the report configuration. ::: @@ -106,22 +106,22 @@ Only the report title and descriptions can be modified within the report configu | ---------------------------- | --------------------------- | ------------- | ------------------------------------------------------------------------------------------------- | | 1. User Password Information | @pswLen | 15 | Number of days left until a password expires, should be set according to an organizations policy. | -The parameters that can be customized are listed in a section at the bottom of the SQL Script -Editor. Follow the steps to customize an analysis task’s parameters. +The parameters you can customize appear in a section at the bottom of the SQL Script +Editor. To customize an analysis task’s parameters: **Step 1 –** Navigate to the **AD_PasswordExpirationNotification** > **Configure** node and select **Analysis** to view the analysis tasks. **Step 2 –** In the Analysis Selection view, select the **1. User Password Information** Analysis -Task and click on **Analysis Configuration**. The SQL Script Editor opens. +Task and click **Analysis Configuration**. The SQL Script Editor opens. ![1. User Password Information Analysis Task in SQL Script Editor](/images/accessanalyzer/11.6/admin/jobs/instantjobs/customizeanalysistask.webp) **Step 3 –** In the parameters section at the bottom of the editor, find the Value column. -Double-click on the current value and change as desired. +Double-click the current value and change as desired. :::warning -Do not change any parameters where the Value states **Created during execution**. +Don't change any parameters where the Value states **Created during execution**. ::: @@ -131,7 +131,7 @@ The new value will be applied to the next job execution. ## Notification Analysis Task in the AD_PasswordExpirationNotification Job -The Notification Analysis Task can be used to send a single email to specified recipients containing +Use the Notification Analysis Task to send a single email to specified recipients containing a list of all users whose passwords will expire in the specified number of days, that is the users listed in the PasswordExpirationNotification_ExpiresWithin15Days table. The analysis is enabled by default. Therefore, when the job is executed the following message is sent to the specified @@ -141,7 +141,7 @@ recipient, such as the organization’s help desk, with information from the ass > > Support Team, > -> Heads-up.  The following users are facing password expiration in seven days or less: +> Heads-up. The following users are facing password expiration in seven days or less: > > [ -- Password for [User] ([NTAccount]) expires in [DaysUntilExpiration] days] > @@ -150,22 +150,22 @@ recipient, such as the organization’s help desk, with information from the ass > Netwrix :::warning -Do not modify the tags, highlighted in bold text above. +Don't modify the tags, highlighted in bold text in the preceding message. ::: -The Subject or message body can be modified, for example to replace `Netwrix` with the -organization’s name. Follow the steps to configure the 5. Help Desk Notification Analysis Task. +You can modify the Subject or message body, for example to replace `Netwrix` with the +organization’s name. To configure the 5. Help Desk Notification Analysis Task: **Step 1 –** Navigate to the **AD_PasswordExpirationNotification** > **Configure** node and select **Analysis** to view the Analysis tasks. **Step 2 –** In the Analysis Selection view, select the **5. Help Desk Notification Analysis Task** -and click on **Analysis Configuration**. The Notification Data Analysis Module opens. +and click **Analysis Configuration**. The Notification Data Analysis Module opens. ![SMTP properties page](/images/accessanalyzer/11.6/admin/jobs/instantjobs/smtpproperties.webp) -**Step 3 –** Use the **Next** button to navigate to the SMTP properties page. Do not make changes to +**Step 3 –** Use the **Next** button to navigate to the SMTP properties page. Don't make changes to the preceding pages. The email configuration takes place on the SMTP page. Provide the recipients’ email addresses, Message Subject, and add the notification email content. @@ -173,7 +173,7 @@ email addresses, Message Subject, and add the notification email content. In the Recipients section, provide the email addresses in the text box or distribution lists in the E-mail field (fully qualified address) for those who are to receive this notification, for example -the organization’s Help Desk. Multiple addresses can be input by adding a semicolon (;) and space +the organization’s Help Desk. You can input multiple addresses by adding a semicolon (;) and space between entries. Use the **Add** and **Remove** buttons to add or remove the address in the E-mail field from the @@ -183,16 +183,16 @@ per user. ![Message section of SMTP properties page](/images/accessanalyzer/11.6/admin/jobs/instantjobs/smtppropertiesmessage.webp) -In the Message section, the **Subject** should be configured. Then set the email content in the text +In the Message section, configure the **Subject**. Then set the email content in the text box as desired. **Step 4 –** To save these configuration changes, use the **Next** button to navigate to the Summary -page. Do not make changes to any other pages. Click **Finish**. The Notification Data Analysis +page. Don't make changes to any other pages. Click **Finish**. The Notification Data Analysis Module window closes. ![Analyis Tasks view](/images/accessanalyzer/11.6/admin/jobs/instantjobs/analysistaskshelpdesknotification.webp) -**Step 5 –** This notification analysis task is now configured to send emails. In the Analysis +**Step 5 –** You have now configured this notification analysis task to send emails. In the Analysis Selection view, ensure the 5. Help Desk Notification Analysis Task is checked so that notifications can be sent automatically during the execution of the AD_PasswordExpirationNotification Job. @@ -203,7 +203,7 @@ is executed. The 1. User Notification Action Task uses the SendMail Action Module to send users notification of password expiration. It targets the SMTP Address Column of the users whose passwords are going to -expire within the desired number of days, that is the users listed in the +expire within the number of days you want, that is the users listed in the PasswordExpirationNotification_ExpiresWithin15Days_UserNotifications table. The action is enabled by default. Therefore, when the job is executed the following message is sent to all users in the associated table: @@ -212,8 +212,8 @@ associated table: > > Hello **[User]**, > -> The password for the account **[NTAccount]** expires on **[ExpirationDate]**. Please change the ->password prior to the expiration date.  If account profiles are used on mobile devices, please +> The password for the account **[NTAccount]** expires on **[ExpirationDate]**. change the +>password before the expiration date. If account profiles are used on mobile devices, >remember to update the password on each device used. > > Thank you, @@ -221,19 +221,19 @@ associated table: > Netwrix :::warning -Do not change the recipient for the action task. While the tags can be moved, do not -remove or modify the tags, which are highlighted in bold text above. +Don't change the recipient for the action task. While you can move the tags, don't +remove or modify them, which are highlighted in bold text in the preceding message. ::: -The subject or message body can be modified, for example to replace `Netwrix` with the -organization’s name. Follow the steps to modify the Subject or message body within the 1. User -Notification Action Task. +You can modify the subject or message body, for example to replace `Netwrix` with the +organization’s name. To modify the Subject or message body within the 1. User +Notification Action Task: :::note -It is necessary for the -PasswordExpirationNotification_ExpiresWithin15Days_UserNotifications table to exist in the database -before this action task can be modified. +The +PasswordExpirationNotification_ExpiresWithin15Days_UserNotifications table must exist in the database +before you can modify this action task. ::: @@ -244,12 +244,12 @@ before this action task can be modified. on **Action Properties** to view the actions. :::warning -Do not modify the action task properties. +Don't modify the action task properties. ::: **Step 3 –** In the Action Properties view, the action properties and a preview of the users from -the associated table are displayed. Click **Configure Action**. The Send Mail Action Module Wizard +the associated table appear. Click **Configure Action**. The Send Mail Action Module Wizard opens. ![Send Mail Action Module Wizard Message page](/images/accessanalyzer/11.6/admin/jobs/instantjobs/actionwizardmessage.webp) @@ -262,5 +262,5 @@ Wizard closes. **Step 6 –** Click **Save** on the Action Properties view. -When the action task is enabled, it executes as part of the job. Optionally, the action task can be -manually executed. +When the action task is enabled, it executes as part of the job. Optionally, you can +manually execute the action task. diff --git a/docs/accessanalyzer/11.6/admin/jobs/instantjobs/ex_registerazureappauth.md b/docs/accessanalyzer/11.6/admin/jobs/instantjobs/ex_registerazureappauth.md index adc87d905e..dd774918aa 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/instantjobs/ex_registerazureappauth.md +++ b/docs/accessanalyzer/11.6/admin/jobs/instantjobs/ex_registerazureappauth.md @@ -22,7 +22,7 @@ authentication and provision appropriate permissions for Exchange Online scans. - Azure AD PowerShell module installed on targeted hosts :::note - If the module is not already installed, the job will attempt to install it. + If the module isn't already installed, the job will attempt to install it. ::: @@ -49,10 +49,10 @@ authentication and provision appropriate permissions for Exchange Online scans. ## Using the EX_RegisterAzureAppAuth Job -Follow the steps to configure and run the EX_RegisterAzureAppAuth Job. +To configure and run the EX_RegisterAzureAppAuth Job: **Step 1 –** In Enterprise Auditor navigate to the Exchange Job Group (or any other Job Group you -wish to place the EX_RegistureAzureApp job into). +want to place the EX_RegistureAzureApp job into). **Step 2 –** Click **Add Instant Job** to open the Instant Job Wizard. @@ -79,7 +79,7 @@ to provide the full environment name. For a standard tenant, leave this option b **Step 7 –** On the **Configure** > **Hosts** node, select the target hosts. The targeted hosts should be the Microsoft Entra tenant name (for example, `myorg.onmicrosoft.com`). Click **Save**. -The job is now ready to be run. +The job is now ready to run. **Step 8 –** Run the EX_RegisterAzureAppAuth Job. @@ -87,16 +87,16 @@ The job is now ready to be run. Log-in as a Global Administrator, and grant administrator consent to the Application's configured API Permissions. -- If this login attempt fails or you close the browser, you will need to login to Microsoft Entra ID +- If this login attempt fails or you close the browser, you will need to log in to Microsoft Entra ID as a Global Administrator and navigate to the Application's API Permissions to grant Admin Consent - before the Application can be used for Exchange scans in Enterprise Auditor. + before you can use the Application for Exchange scans in Enterprise Auditor. -The Microsoft Entra ID application is now provisioned with the necessary permissions for Exchange -Online scans. There will be a new Connection Profile for this Application. Restart the Enterprise +The job has now provisioned the Microsoft Entra ID application with the necessary permissions for +Exchange Online scans. There will be a new Connection Profile for this Application. Restart the Enterprise Auditor Console and enter a password to use this Connection Profile. :::tip -Remember, the required rights and roles for Exchange Online still need to be configured. See the +Remember, you still need to configure the required rights and roles for Exchange Online. See the [Target Exchange Online Requirements, Permissions, and Ports](/docs/accessanalyzer/11.6/requirements/exchange/exchangeonline/exchangeonline.md) topic for additional information. ::: diff --git a/docs/accessanalyzer/11.6/admin/jobs/instantjobs/fs_defend_sdd.md b/docs/accessanalyzer/11.6/admin/jobs/instantjobs/fs_defend_sdd.md index 68c700c5b4..a805572cc2 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/instantjobs/fs_defend_sdd.md +++ b/docs/accessanalyzer/11.6/admin/jobs/instantjobs/fs_defend_sdd.md @@ -26,7 +26,7 @@ Runtime Details: - A Connection Profile must be created using the Web Services (JWT) credential account type with the specified Threat Manager App Token and assigned to this job - See the - [Custom Connection Profile for FS_DEFEND_SDD Job](#custom-connection-profile-for-fs_defend_sdd-job) + [Custom Connection Profile for FS_DEFEND_SDD Job](#custom-connection-profile-for-fsdefendsdd-job) topic for additional information - Assign the Connection Profile on the Connection tab of the job’s Properties - The Threat Manager host name with port, [HOST]:8080, and App Token are generated within Threat @@ -81,9 +81,9 @@ The default action is: ## Custom Connection Profile for FS_DEFEND_SDD Job -The FS_DEFEND_SDD Job requires a custom Connection Profile to authenticate to Threat Manager. The -credential for the Connection Profile must be created with the Web Services (JWT) account type. -Remember, the Threat Manager App Token is generated within Threat Manager. +The FS_DEFEND_SDD Job requires a custom Connection Profile to authenticate to Threat Manager. You +must create the credential for the Connection Profile with the Web Services (JWT) account type. +Remember, Threat Manager generates the App Token. Create a Connection Profile and set the following information on the User Credentials window: diff --git a/docs/accessanalyzer/11.6/admin/jobs/instantjobs/fs_migrateschema.md b/docs/accessanalyzer/11.6/admin/jobs/instantjobs/fs_migrateschema.md index 38cd823e48..642cd93993 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/instantjobs/fs_migrateschema.md +++ b/docs/accessanalyzer/11.6/admin/jobs/instantjobs/fs_migrateschema.md @@ -6,7 +6,7 @@ sidebar_position: 40 # FS_MigrateSchema Job -The FS_Migrate_Schema Job migrates the schema in order to support the use of 64-bit ResourceID's +The FS_Migrate_Schema Job migrates the schema to support the use of 64-bit ResourceID's without affecting data. It is available through the Instant Job Library under the File System library. See the [Instant Job Wizard](/docs/accessanalyzer/11.6/admin/jobs/instantjobs/overview.md) @@ -25,7 +25,7 @@ Runtime Details: - Multi-console Support – Not supported - Additional Notes – None -The FS_Migrate Schema Job migrates the schema in order to support the use of 64-bit ResourceID's +The FS_Migrate Schema Job migrates the schema to support the use of 64-bit ResourceID's without affecting data. ## Analysis Tasks for the FS_MigrateSchema Job @@ -34,7 +34,7 @@ Navigate to the **Jobs** > **FS_MigrateSchema** > **Configure** node and select the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -43,23 +43,23 @@ preconfigured for this job. The default analysis tasks are: -- 1.Migrate Resources – Migrates the SA_FSAA_Resources table to leverage 64-bit IDs -- 2.Migrate UnixRights – Migrates the SA_FSAA_UnixRights table to leverage 64-bit IDs -- 3.Migrate Gates – Migrates the SA_Gates table to leverage 64-bit IDs -- 4.Migrate GatesProxy – Migrates the SA_FSAA_GatesProxy table to leverage 64-bit IDs -- 5.Migrate Exceptions – Migrates the SA_FSAA_Exceptions table to leverage 64-bit IDs -- 6.Migrate ProbableOwners – Migrates the SA_FSAA_ProbableOwners table to leverage 64-bit IDs -- 7.Migrate FileSizes – Migrates the SA_FSAA_FileSizes table to leverage 64-bit IDs -- 8.Migrate FileTypes – Migrates the SA_FSAA_FileTypes table to leverage 64-bit IDs -- 9.Migrate FileAges – Migrates the SA_FSAA_FileAges table to leverage 64-bit IDs -- 10.Migrate FileTags – Migrates the SA_FSAA_FileTags table to leverage 64-bit IDs -- 11.Migrate DFS Links – Migrates the SA_FSDFS_Links table to leverage 64-bit IDs -- 12.Migrate DLP Matches – Migrates the SA_FSDLP_Matches table to leverage 64-bit IDs -- 13.Migrate DLP MatchHits – Migrates the SA_FSDLP_MatchHits table to leverage 64-bit IDs +- 1.Migrate Resources – Migrates the SA_FSAA_Resources table to use 64-bit IDs +- 2.Migrate UnixRights – Migrates the SA_FSAA_UnixRights table to use 64-bit IDs +- 3.Migrate Gates – Migrates the SA_Gates table to use 64-bit IDs +- 4.Migrate GatesProxy – Migrates the SA_FSAA_GatesProxy table to use 64-bit IDs +- 5.Migrate Exceptions – Migrates the SA_FSAA_Exceptions table to use 64-bit IDs +- 6.Migrate ProbableOwners – Migrates the SA_FSAA_ProbableOwners table to use 64-bit IDs +- 7.Migrate FileSizes – Migrates the SA_FSAA_FileSizes table to use 64-bit IDs +- 8.Migrate FileTypes – Migrates the SA_FSAA_FileTypes table to use 64-bit IDs +- 9.Migrate FileAges – Migrates the SA_FSAA_FileAges table to use 64-bit IDs +- 10.Migrate FileTags – Migrates the SA_FSAA_FileTags table to use 64-bit IDs +- 11.Migrate DFS Links – Migrates the SA_FSDFS_Links table to use 64-bit IDs +- 12.Migrate DLP Matches – Migrates the SA_FSDLP_Matches table to use 64-bit IDs +- 13.Migrate DLP MatchHits – Migrates the SA_FSDLP_MatchHits table to use 64-bit IDs - 14.Migrate DLP MatchHits Subject Profile – Migrates the SA_FSDLP_MatchHits_SubjectProfile table to - leverage 64-bit IDs -- 15.Migrate FSAC ActivityEvents – Migrates the SA_FSAC_ActivityEvents table to leverage 64-bit IDs -- 16.Migrate DailyActivity – Migrates the SA_FSAC_DailyActivity table to leverage 64-bit IDs -- 17.Migrate FSAC RenameTargets – Migrates the SA_FSAC_RenameTargets table to leverage 64-bit IDs -- 18.Migrate FSAC Exceptions – Migrates the SA_FSAC_Exceptions table to leverage 64-bit IDs + use 64-bit IDs +- 15.Migrate FSAC ActivityEvents – Migrates the SA_FSAC_ActivityEvents table to use 64-bit IDs +- 16.Migrate DailyActivity – Migrates the SA_FSAC_DailyActivity table to use 64-bit IDs +- 17.Migrate FSAC RenameTargets – Migrates the SA_FSAC_RenameTargets table to use 64-bit IDs +- 18.Migrate FSAC Exceptions – Migrates the SA_FSAC_Exceptions table to use 64-bit IDs - 19.Refresh Views – Updates viewable metadata diff --git a/docs/accessanalyzer/11.6/admin/jobs/instantjobs/overview.md b/docs/accessanalyzer/11.6/admin/jobs/instantjobs/overview.md index d27180b6ab..1c337e15f4 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/instantjobs/overview.md +++ b/docs/accessanalyzer/11.6/admin/jobs/instantjobs/overview.md @@ -13,12 +13,12 @@ problems. The instant solutions available align to an organization’s license k the[Solutions](/docs/accessanalyzer/11.6/solutions/overview.md) topic for additional information. -Follow the steps to install an instant solution or an instant job with the Instant Job Wizard. +To install an instant solution or an instant job with the Instant Job Wizard: ![Add Instant Job from context menu](/images/accessanalyzer/11.6/admin/jobs/instantjobs/addinstantjob.webp) -**Step 1 –** Select the Jobs tree (for an instant solution) or the desired job group (for an instant -job), right-click on the node, and select **Add Instant Job**. +**Step 1 –** Select the Jobs tree (for an instant solution) or the job group you want (for an instant +job), right-click the node, and select **Add Instant Job**. ![Instant Job Wizard Welcome page](/images/accessanalyzer/11.6/admin/jobs/instantjobs/welcome.webp) @@ -31,15 +31,15 @@ category, or click the plus icon (+) to expand a category group. ![Selected Instant Job](/images/accessanalyzer/11.6/admin/jobs/instantjobs/selectinstantjob.webp) -**Step 4 –** Select the desired instant solution or job. To select multiple instant solutions or +**Step 4 –** Select the instant solution or job you want. To select multiple instant solutions or jobs, press the Windows **Ctrl** key and select the items to install. Click **Next**. ![Host Assignment page](/images/accessanalyzer/11.6/admin/jobs/instantjobs/hostassignment.webp) -**Step 5 –** Some of the Library selections add a Host Assignment page. If this page does not +**Step 5 –** Some of the Library selections add a Host Assignment page. If this page doesn't appear, skip to Step 7. If the page does appear, select either the **Use default settings (Inherit -from the parent group, if any)** or **Specify individual hosts or hosts lists** option. If the first -option is selected, skip to Step 7. If the second option is selected, click **Next** to go to the +from the parent group, if any)** or **Specify individual hosts or hosts lists** option. If you selected the first +option, skip to Step 7. If you selected the second option, click **Next** to go to the Host Lists and Individual Hosts wizard pages. | ![Host Lists page](/images/accessanalyzer/11.6/admin/jobs/instantjobs/hostlists.webp) | | ![Individual Hosts page](/images/accessanalyzer/11.6/admin/jobs/instantjobs/individualhosts.webp) | @@ -47,8 +47,8 @@ Host Lists and Individual Hosts wizard pages. | Host Lists page | | Individual Hosts page | **Step 6 –** Some of the Library selections add a Host Lists, and Individual Hosts page. If these -pages do not appear with the selection, skip to Step 7. If the pages do appear, check the host list -to be assigned to the job group or job. Alternatively enter hosts manually. Then click **Next**. +pages don't appear with the selection, skip to Step 7. If the pages do appear, check the host list +to assign to the job group or job. Alternatively enter hosts manually. Then click **Next**. ![Summary page](/images/accessanalyzer/11.6/admin/jobs/instantjobs/summary.webp) diff --git a/docs/accessanalyzer/11.6/admin/jobs/instantjobs/sas_executionstatistics.md b/docs/accessanalyzer/11.6/admin/jobs/instantjobs/sas_executionstatistics.md index 89d6d66871..850f4aa832 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/instantjobs/sas_executionstatistics.md +++ b/docs/accessanalyzer/11.6/admin/jobs/instantjobs/sas_executionstatistics.md @@ -10,7 +10,7 @@ The SAS_ExecutionStatistics Job tracks historical performance of Enterprise Audi functions and highlights when a particular task takes an abnormal length of time to execute. It is available through the Instant Job Library under the Enterprise Auditor Utilities library. See the [Instant Job Wizard](/docs/accessanalyzer/11.6/admin/jobs/instantjobs/overview.md) -section for instructions to add this instant job into the Jobs tree. Since this job does not require +section for instructions to add this instant job into the Jobs tree. Since this job doesn't require a host to target, select Local host on the Hosts page of the Instant Job Wizard. The job is dependent upon the Job Statistics Retention configuration in the **Settings** > @@ -40,7 +40,7 @@ Navigate to the **Jobs** > **SAS_ExecutionStatistics** > **Configure** node and to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/admin/jobs/instantjobs/sp_registerazureappauth.md b/docs/accessanalyzer/11.6/admin/jobs/instantjobs/sp_registerazureappauth.md index cab680351c..5ced6b9651 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/instantjobs/sp_registerazureappauth.md +++ b/docs/accessanalyzer/11.6/admin/jobs/instantjobs/sp_registerazureappauth.md @@ -15,14 +15,14 @@ authentication and provision appropriate permissions for SharePoint Online scans - Microsoft Entra ID Global Admin credential - A credential with the username `newapp` that contains the password for the new application -- Microsoft Graph API PowerShell module to be installed on targeted hosts +- Microsoft Graph API PowerShell module installed on targeted hosts ## Instantiate the SP_RegisterAzureAppAuth Job. -Follow the steps to instantiate the SP_RegisterAzureAppAuth Job. +To instantiate the SP_RegisterAzureAppAuth Job: **Step 1 –** In Enterprise Auditor navigate to the SharePoint Job Group (or any other Job Group you -wish to place the SP_RegistureAzureApp job into). +want to place the SP_RegistureAzureApp job into). **Step 2 –** Click **Add Instant Job** to open the Instant Job Wizard. @@ -36,13 +36,13 @@ Microsoft Entra ID application. Click **Save**. **Step 5 –** On the **Configure** > **Hosts** node, select the targeted host. The targeted host should be the Microsoft Entra ID tenant on which you want to install the Microsoft Entra ID -application (for example, `myorg.onmicrosoft.com`). Click **Save**. The job is now ready to be run. +application (for example, `myorg.onmicrosoft.com`). Click **Save**. The job is now ready to run. -After the job successfully runs it will open a browser window to Microsoft Entra ID that, when -logged-in as a Global Administrator, allows the user to grant administrator consent to the +After the job successfully runs, it opens a browser window to Microsoft Entra ID. Log in as a +Global Administrator to grant administrator consent to the Application's configured API Permissions. If the login attempt fails, or the user closes the -browser, they will need to login to Microsoft Entra ID as a Global Administrator and navigate to the -Application's API Permissions to grant Admin Consent before the Application can be used for +browser, they will need to log in to Microsoft Entra ID as a Global Administrator and navigate to the +Application's API Permissions to grant Admin Consent before you can use the Application for SharePoint scans in Enterprise Auditor. **Additional Considerations** @@ -53,8 +53,8 @@ SharePoint scans in Enterprise Auditor. directory), the Microsoft Entra ID application's password, and a numeric designator for the Microsoft 365 environment (0 is the default for production environments; the other supported options are 1 for pre-production environments, 2 for China, 3 for Germany, 4 for US Government, 5 - for US Government-High, and 6 for US Government-DoD). To allow for multiple unique certificates - for different Microsoft Entra ID tenants to be stored on the same Enterprise Auditor server, the + for US Government-High, and 6 for US Government-DoD). To allow multiple unique certificates + for different Microsoft Entra ID tenants to reside on the same Enterprise Auditor server, the script appends the targeted host name (without the domain) to the filename of the PFX file generated by the script. For example, if the targeted host is `myorg.onmicrosoft.com`, then the password for the connection profile would be: diff --git a/docs/accessanalyzer/11.6/admin/jobs/instantjobs/sp_removehost.md b/docs/accessanalyzer/11.6/admin/jobs/instantjobs/sp_removehost.md index cdd86c59ca..90e483a0bf 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/instantjobs/sp_removehost.md +++ b/docs/accessanalyzer/11.6/admin/jobs/instantjobs/sp_removehost.md @@ -31,7 +31,7 @@ Navigate to the **Jobs** > **SP_RemoveHost** > **Configure** node and select **A the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -40,4 +40,4 @@ preconfigured for this job. The default analysis tasks are: -- Remove Host(s) — Remove Scanned Hosts from Tier 1 +- Remove Hosts — Remove Scanned Hosts from Tier 1 diff --git a/docs/accessanalyzer/11.6/admin/jobs/job/configure/actions.md b/docs/accessanalyzer/11.6/admin/jobs/job/configure/actions.md index ff20b9a08c..7e38ec915a 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/job/configure/actions.md +++ b/docs/accessanalyzer/11.6/admin/jobs/job/configure/actions.md @@ -7,8 +7,8 @@ sidebar_position: 40 # Actions Node The Actions node uses Enterprise Auditor action modules to take action on collected and analyzed -data. Action can be taken on objects leveraging collected data or analyzed data, for example from a -listing of locked-out accounts, an action can be executed to unlock those accounts. +data. You can take action on objects leveraging collected data or analyzed data. For example, from a +listing of locked-out accounts, you can execute an action to unlock those accounts. :::note Action modules are available with a special Enterprise Auditor license. @@ -52,7 +52,7 @@ The Actions section at the top has five options: - Execute Action – Opens the Action Execution window and starts executing the selected action - - Does not require an action task to be checked, only selected + - Doesn't require checking an action task, only selecting it ![Buttons at the bottom of Action Selection page](/images/accessanalyzer/11.6/admin/jobs/job/configure/actionselectiontablebuttons.webp) diff --git a/docs/accessanalyzer/11.6/admin/jobs/job/configure/analysis/analysis.md b/docs/accessanalyzer/11.6/admin/jobs/job/configure/analysis/analysis.md index 94cf694ddb..003b9096aa 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/job/configure/analysis/analysis.md +++ b/docs/accessanalyzer/11.6/admin/jobs/job/configure/analysis/analysis.md @@ -10,9 +10,9 @@ The Analysis node uses Enterprise Auditor analysis modules to run analysis tasks There are two basic types of analysis modules. Most analysis modules correlate, format, and transform collected data into powerful data views for end-stage reports and graphs. -The Notification analysis module allows for the ability to send an email notice when a trigger is -met, for example an email can be sent to an administrator to notify that disk space has reached a -particular point (the trigger) and needs to be addressed before space runs out. +The Notification analysis module lets you send an email notice when a trigger is +met. For example, it can send an email to an administrator to notify that disk space has reached a +particular point (the trigger) and needs attention before space runs out. ![Analysis Selection page](/images/accessanalyzer/11.6/admin/jobs/job/configure/analysisselection.webp) diff --git a/docs/accessanalyzer/11.6/admin/jobs/job/configure/analysis/analysiscustomizableparameters.md b/docs/accessanalyzer/11.6/admin/jobs/job/configure/analysis/analysiscustomizableparameters.md index ba702b437e..cdf7d88483 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/job/configure/analysis/analysiscustomizableparameters.md +++ b/docs/accessanalyzer/11.6/admin/jobs/job/configure/analysis/analysiscustomizableparameters.md @@ -6,12 +6,12 @@ sidebar_position: 10 # Configure the Customizable Parameters in an Analysis Task -The parameters that can be customized and are listed in a section at the bottom of the SQL Script -Editor. Follow the steps to customize an analysis task’s parameters. +You can customize the parameters, which appear in a section at the bottom of the SQL Script +Editor. To customize an analysis task’s parameters: **Step 1 –** Navigate to the Job’s **Configure** node and select **Analysis**. -**Step 2 –** In the Analysis Selection view, select the desired analysis task and click **Analysis +**Step 2 –** In the Analysis Selection view, select the analysis task you want and click **Analysis Configuration**. The SQL Script Editor opens. **Step 3 –** At the top of the SQL Script Editor, select **Parameters**. @@ -27,11 +27,11 @@ based on the Job. **Step 4 –** In the parameters section at the bottom of the editor, find the Value column. :::warning -Do not change any parameters where the Value states **Created during execution**. +Don't change any parameters where the Value states **Created during execution**. ::: -- Double-click on the customizable value and change as desired +- Double-click the customizable value and change as desired **Step 5 –** Click **Save and Close** to finalize the customization and close the SQL Script Editor. diff --git a/docs/accessanalyzer/11.6/admin/jobs/job/configure/hosts.md b/docs/accessanalyzer/11.6/admin/jobs/job/configure/hosts.md index e7036abdef..8f0df880ac 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/job/configure/hosts.md +++ b/docs/accessanalyzer/11.6/admin/jobs/job/configure/hosts.md @@ -7,7 +7,7 @@ sidebar_position: 10 # Hosts Node The Hosts node provides the option to assign a preconfigured host list at the job level. It also -provides a way to manually assign hosts to be targeted by the job using Host Selection pane. +provides a way to manually assign hosts for the job to target using Host Selection pane. ![Host Selection page](/images/accessanalyzer/11.6/admin/jobs/job/configure/hostselection.webp) @@ -20,12 +20,12 @@ it triggers a host inventory query according to the global settings. The host wi any individual host lists. See the [Manually Add Hosts to a Job](#manually-add-hosts-to-a-job) topic for additional information. -Click **Save** to apply any changes to the host selection. Changes are not implemented unless they -are saved. +Click **Save** to apply any changes to the host selection. Changes aren't implemented unless you +save them. ## Manually Add Hosts to a Job -Hosts can be added manually at the job level even when inheritance (Use Default Setting) is used for +You can manually add hosts at the job level even when inheritance (Use Default Setting) is used for host list assignment. The job targets the hosts in any assigned host lists as well as any manually added at the job level. Follow these directions to manually add a host to a job. @@ -38,8 +38,8 @@ added at the job level. Follow these directions to manually add a host to a job. **Step 2 –** In the Individual hosts section of the Host Selection view, enter the Host name in the textbox and click **Add**. -**Step 3 –** Repeat the previous step for each host to be added. +**Step 3 –** Repeat the previous step for each host to add. **Step 4 –** Click **Save** and then **OK** to confirm the changes. -The manually added host is now targeted by the job. +The job now targets the manually added host. diff --git a/docs/accessanalyzer/11.6/admin/jobs/job/configure/overview.md b/docs/accessanalyzer/11.6/admin/jobs/job/configure/overview.md index af3887843d..658cb56575 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/job/configure/overview.md +++ b/docs/accessanalyzer/11.6/admin/jobs/job/configure/overview.md @@ -6,8 +6,8 @@ sidebar_position: 30 # Configure Node -Changes to configurations for the job’s assigned Host Lists, Queries, Analyses, Actions, and Reports -are created through the **[Job]** > **Configure** node or through the Configure shortcut on the +You create changes to configurations for the job’s assigned Host Lists, Queries, Analyses, Actions, +and Reports through the **[Job]** > **Configure** node or through the Configure shortcut on the job’s Description page. | | | @@ -18,7 +18,7 @@ job’s Description page. The sub-nodes under the **[Job]** > **Configure** node are: - [Hosts Node](/docs/accessanalyzer/11.6/admin/jobs/job/configure/hosts.md) - – Assign a host list at the job level or manually add hosts to be targeted by the job + – Assign a host list at the job level or manually add hosts for the job to target - [Queries Node](/docs/accessanalyzer/11.6/admin/jobs/job/configure/queries.md) – Select and configure a Enterprise Auditor data collector to scan targeted hosts - [Analysis Node](/docs/accessanalyzer/11.6/admin/jobs/job/configure/analysis/analysis.md) @@ -26,11 +26,11 @@ The sub-nodes under the **[Job]** > **Configure** node are: - [Actions Node](/docs/accessanalyzer/11.6/admin/jobs/job/configure/actions.md) – Create and configure Action tasks for taking action on collected and analyzed data - [Reports Node](/docs/accessanalyzer/11.6/admin/jobs/job/configure/reports.md) - – Create and configure Reports to be generated during job execution + – Create and configure Reports to generate during job execution ## Configure Page -The job's Configure Page provides an overview with shortcuts for options that are configured in the +The job's Configure Page provides an overview with shortcuts for options you configure in the job's Configure Node. ![Configure page](/images/accessanalyzer/11.6/admin/jobs/job/configure/configurepage.webp) diff --git a/docs/accessanalyzer/11.6/admin/jobs/job/configure/queries.md b/docs/accessanalyzer/11.6/admin/jobs/job/configure/queries.md index 47b7259675..44cbd213ae 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/job/configure/queries.md +++ b/docs/accessanalyzer/11.6/admin/jobs/job/configure/queries.md @@ -7,29 +7,29 @@ sidebar_position: 20 # Queries Node The Queries node uses a Enterprise Auditor data collector to run scans against the targeted hosts. -Different data collectors are designed for different types of collection. It is necessary for the -Connection Profile associated with the target hosts to have a sufficient level of rights for the -selected data collector. See the +Different data collectors are designed for different types of collection. The Connection Profile +associated with the target hosts must have a sufficient level of rights for the selected data +collector. See the [Permissions by Data Collector (Matrix)](/docs/accessanalyzer/11.6/admin/datacollector/permissionmatrix.md) topic for a chart with recommended permissions per data collector. ![Query Selection page](/images/accessanalyzer/11.6/admin/jobs/job/configure/queryselection.webp) -The Query Selection view lists all queries for the selected job. Though it is possible to have -multiple queries in a single job, it is not usually recommended. The listed information includes: +The Query Selection view lists all queries for the selected job. Though a job can have +multiple queries, avoid using more than one when possible. The listed information includes: - Name – Name of the query (as provided by the creator of the query) - Source – Name of the Enterprise Auditor data collector - Table – Name of the Native Data table -- Enumerates – Whether or not the data collector will return enumerated data, or multiple lines of +- Enumerates – Whether the data collector will return enumerated data, or multiple lines of data per target host - If **Yes**, only one query can write to a single table - If **No**, then multiple related queries can write to a single table - Properties – Number of the properties to be returned - Filters – Number of in-line filters applied to the data being returned by the query -- Script – Whether or not a VB Script was added to the query +- Script – Whether a VB Script was added to the query - If **Yes**, a VB Script was added to query execution - - If **No**, a VB Script was not added to query execution + - If **No**, a VB Script wasn't added to query execution - Description – Description of the query (as provided by the creator of the query) ## Tables @@ -43,18 +43,17 @@ The Tables section at the top has three options: - Add Table – Adds an additional native data table and associated query to the selected job - Rename Table – Opens the Rename Table window for changing the native data table name - Delete Table – Deletes the selected table from the list, all associated query tasks, and the - database table if it has already been created. This action does require confirmation. + database table if it has already been created. This action requires confirmation. :::warning - Do not delete the last table in a job’s Query Selection view. Doing so will also - delete the Messages table. In order to delete the last table, it is necessary to delete the job. + Don't delete the last table in a job’s Query Selection view. Doing so will also + delete the Messages table. To delete the last table, delete the job. ::: ## Queries -The Queries section is where the job’s preconfigured queries can be edited and where new queries can -be added. +The Queries section is where you can edit the job’s preconfigured queries and add new queries. ![Queries section of Query Selection page](/images/accessanalyzer/11.6/admin/jobs/job/configure/queryselectionqueries.webp) @@ -65,7 +64,7 @@ The Queries section has four options and includes the list of queries for the se [Add Query from Library](/docs/accessanalyzer/11.6/admin/datacollector/overview.md#add-query-from-library) topic for additional information. - Create Query – Opens the Query Properties window for creating and configuring queries -- Delete Query – Deletes the selected query from the list. This action does require confirmation. +- Delete Query – Deletes the selected query from the list. This action requires confirmation. - Query Properties – Opens the Query Properties window for the selected query - This option is used for query modifications - See the @@ -102,9 +101,9 @@ The options in the Queries node right-click menu are: ## Host List -Jobs with configured queries require a host list to be assigned. This can be done at either the Job -Group or Job level. Whichever location is used to set the host list for query execution should also -be the location where the Connection Profile is assigned. See the +Jobs with configured queries require you to assign a host list. You can do this at either the Job +Group or Job level. Whichever location you use to set the host list for query execution should also +be the location where you assign the Connection Profile. See the [Job Properties](/docs/accessanalyzer/11.6/admin/jobs/job/properties/overview.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/admin/jobs/job/configure/reports.md b/docs/accessanalyzer/11.6/admin/jobs/job/configure/reports.md index 3dbdc05381..fd95df388a 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/job/configure/reports.md +++ b/docs/accessanalyzer/11.6/admin/jobs/job/configure/reports.md @@ -6,17 +6,17 @@ sidebar_position: 50 # Reports Node -The Reports node is for configuring reports to be generated during job execution. +The Reports node is for configuring reports to generate during job execution. ![Reports page](/images/accessanalyzer/11.6/admin/jobs/job/configure/reports.webp) -The Reports view lists any reports that have been configured for the selected job and options +The Reports view lists any reports you've configured for the selected job and options related to configuring reports. The options at the top of the Reports view are: - Properties – Opens the [Job Properties](/docs/accessanalyzer/11.6/admin/jobs/job/properties/overview.md) page for the job that the report is for -- Run Now – Runs the currently selected job that the report is for +- Run Now – Runs the selected job that the report is for - Open Folder – Opens the Report’s folder location with supporting files in the Windows Explorer - View Log – Opens the log for the job that the report is for @@ -33,8 +33,8 @@ contains the following options for adding reports to the table: - Paste – Paste a cut or copied report into the selected job - - The paste option is accessed from the vertical ellipsis menu of the header row of the Reports - table + - You can access the paste option from the vertical ellipsis menu of the header row of the + Reports table ![Reports table row options](/images/accessanalyzer/11.6/admin/jobs/job/configure/reportstablerowoptions.webp) @@ -48,9 +48,9 @@ on a reports row: - Copy – Copies the report to the clipboard - Delete – Deletes the report -Once a report is generated, it can be viewed in several locations depending on the configuration. -Report configurations may also be copied to other reports to generate preferred outputs for -alternate jobs. However, all generated reports can be viewed in the job’s **Results** node. +After you generate a report, you can view it in several locations depending on the configuration. +You can also copy report configurations to other reports to generate preferred outputs for +alternate jobs. However, you can view all generated reports in the job’s **Results** node. See the [Reporting](/docs/accessanalyzer/11.6/admin/report/overview.md) topic diff --git a/docs/accessanalyzer/11.6/admin/jobs/job/create.md b/docs/accessanalyzer/11.6/admin/jobs/job/create.md index c5e3cdabbd..cccaab75e0 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/job/create.md +++ b/docs/accessanalyzer/11.6/admin/jobs/job/create.md @@ -6,11 +6,11 @@ sidebar_position: 50 # Create a New Job -Follow the steps to create a new job. +To create a new job: ![Create Job from Jobs Tree context menu](/images/accessanalyzer/11.6/admin/jobs/job/createjob.webp) -**Step 1 –** Select the Jobs tree or the desired job group to add the new job to. Right-click and +**Step 1 –** Select the Jobs tree or the job group you want to add the new job to. Right-click and select **Create Job**. ![New Job added to Jobs Tree](/images/accessanalyzer/11.6/admin/jobs/job/newjob.webp) @@ -19,20 +19,20 @@ select **Create Job**. considerations for naming conventions: :::warning -Do not end a job name with a space. +Don't end a job name with a space. ::: - There can never be two jobs with the same name. Enterprise Auditor automatically appends a numeral to the end of a job name to avoid duplicates, for example `NewJob1`. -- No special characters can be used. See the Microsoft +- Don't use special characters. See the Microsoft [Naming Conventions](https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file#naming-conventions) article for limitations. -- Jobs in a group are run alphanumerically +- Enterprise Auditor runs jobs in a group alphanumerically - When possible, keep names short to avoid report path errors caused by Microsoft’s maximum path - length. See the Microsoft article referenced above. + length. See the Microsoft article referenced earlier in this topic. -The new job is now ready to be configured. See the +You can now configure the new job. See the [Data Collectors](/docs/accessanalyzer/11.6/admin/datacollector/overview.md), [Analysis Modules](/docs/accessanalyzer/11.6/admin/analysis/overview.md), [Action Modules](/docs/accessanalyzer/11.6/admin/action/overview.md), diff --git a/docs/accessanalyzer/11.6/admin/jobs/job/disableenable.md b/docs/accessanalyzer/11.6/admin/jobs/job/disableenable.md index b331f29003..d3be385bc8 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/job/disableenable.md +++ b/docs/accessanalyzer/11.6/admin/jobs/job/disableenable.md @@ -6,57 +6,56 @@ sidebar_position: 60 # Disable or Enable a Job -Job groups may contain individual jobs that should not be run when the entire job group is run. Some -job groups also contain jobs that can optionally be run separately from the rest of the job group. -Individual jobs can be disabled or enabled at the job group or job level. Disabled jobs do not -execute when the parent job group is run. +Job groups may contain individual jobs that shouldn't run when you run the entire job group. Some +job groups also contain jobs that you can optionally run separately from the rest of the job group. +You can disable or enable individual jobs at the job group or job level. Disabled jobs don't +execute when you run the parent job group. -If the role based access feature is enabled, the ability to enable and disable jobs is limited by -the assigned role. See the +If you enable the role based access feature, the assigned role limits the ability to enable and +disable jobs. See the [Role Based Access](/docs/accessanalyzer/11.6/admin/settings/access/rolebased/overview.md) topic for additional information. ## Disable a Job -Jobs can be disabled from the Jobs tree. Disabled jobs cannot be run manually, through a scheduled -task, or executed as part of the job group. Follow the steps to disable a job. +You can disable jobs from the Jobs tree. You can't run a disabled job manually, through a scheduled +task, or as part of job group execution. To disable a job: **Step 1 –** Select a job group or job. :::note -When disabling jobs at the job group level, all jobs contained in the job group are -disabled, but the job group is not disabled. Any additional jobs added to that job group at a later -time will be enabled by default. +When you disable jobs at the job group level, all jobs in the job group become disabled, but the +job group itself remains enabled. Any additional jobs added to that job group later are enabled by +default. ::: ![Disable Job from Jobs Tree](/images/accessanalyzer/11.6/admin/jobs/job/disablejob.webp) -**Step 2 –** Right-click on the job group or job and select **Disable Job(s)** from the menu. +**Step 2 –** Right-click the job group or job and select **Disable Jobs** from the menu. ![Disabled Job in the Jobs Tree](/images/accessanalyzer/11.6/admin/jobs/job/disabledjob.webp) -The job is now disabled. If a job group was selected, all the jobs in the group are now disabled. +The job is now disabled. If you selected a job group, all the jobs in the group are now disabled. Disabled jobs are grayed out, and a red cross is displayed in front of the job. ![Disabled Job Description page banner](/images/accessanalyzer/11.6/admin/jobs/job/disabledjob2.webp) A yellow banner also notifies users that a job is disabled in the Job’s Description page. -Additionally, if a disabled job is run, a warning message appears in the Messages table stating: -`[UserName] requested [JobName] to run but it is in a disabled state`. Job statistics also do not +Additionally, if you run a disabled job, a warning message appears in the Messages table stating: +`[UserName] requested [JobName] to run but it is in a disabled state`. Job statistics also don't display on the job’s description page. ## Enable a Job -Jobs that have been disabled can be enabled from the Jobs tree. Following the steps to enable a -disabled job. +You can enable disabled jobs from the Jobs tree. Follow these steps to enable a disabled job. **Step 1 –** Select the disabled job. If multiple jobs in a job group are disabled, select the job group to enable all of the disabled jobs. ![Enable Job from Jobs Tree](/images/accessanalyzer/11.6/admin/jobs/job/enablejob.webp) -**Step 2 –** Right-click on the job group or job and select **Enable Job(s)** from the menu. +**Step 2 –** Right-click the job group or job and select **Enable Jobs** from the menu. -The job is now enabled. If a job group was selected, all the jobs in the group are now enabled. +The job is now enabled. If you selected a job group, all the jobs in the group are now enabled. diff --git a/docs/accessanalyzer/11.6/admin/jobs/job/overview.md b/docs/accessanalyzer/11.6/admin/jobs/job/overview.md index 4ec41b025c..57983013cd 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/job/overview.md +++ b/docs/accessanalyzer/11.6/admin/jobs/job/overview.md @@ -7,8 +7,8 @@ sidebar_position: 20 # Jobs An Enterprise Auditor job is responsible for running data collection, conducting data analysis, -executing actions on collected or analyzed data, or generating reports. Each of these are configured -in the corresponding section under the job’s Configure node. A single job can be configured to +executing actions on collected or analyzed data, or generating reports. You configure each of these +in the corresponding section under the job’s Configure node. You can configure a single job to execute one or multiple tasks. See the [Configure Node](/docs/accessanalyzer/11.6/admin/jobs/job/configure/overview.md) topic for additional information. @@ -22,20 +22,20 @@ structure to run those jobs together in the proper order. ::: -Jobs do not have a Settings node like a job group. Job Properties provide the option to break +Jobs don't have a Settings node like a job group. Job Properties provide the option to break inheritance on global or job group settings. See the [Job Properties](/docs/accessanalyzer/11.6/admin/jobs/job/properties/overview.md) topic for additional information. -Once a job has been configured and is being executed, job progress can be viewed at the **Running +After you configure and execute a job, you can view job progress at the **Running Instances** node on the Navigation pane. See the [Running Instances Node](/docs/accessanalyzer/11.6/admin/runninginstances/overview.md) topic for additional information. ![Running Job](/images/accessanalyzer/11.6/admin/jobs/job/jobrunning.webp) -At the bottom of the Enterprise Auditor Console, there is an indication of how many jobs are in -queue and the **View Job Progress** link, which opens the Running Instances node. +At the bottom of the Enterprise Auditor Console, an indicator shows how many jobs are in +queue, along with the **View Job Progress** link, which opens the Running Instances node. When a job execution has completed, the tables, views, and reports generated by the job are accessible under the job’s Status and Results nodes. See the @@ -46,7 +46,7 @@ topics for additional information. Reports are also accessible through the Web C ## Job Description Page The Job Description page displays shortcuts, links, and important information on the job. The Job -Page allows users to view and modify common job configurations, such as Connection and Storage +Page lets users view and modify common job configurations, such as Connection and Storage profiles, job properties, SQL analysis parameters, and PowerShell parameters. Depending on the type of job, the description page will appear different and display information specific to the job selected. @@ -58,13 +58,12 @@ selected. The two types of Job Groups in Enterprise Auditor are: - Pre-configured – The job description page provides a brief summary of the purpose of the job, the - reports and data contained within it, and summary information of the last five times the job was - executed -- User Created – The job description page of User Created jobs will be blank until the job is - configured + reports and data contained within it, and summary information of the last five times the job ran +- User Created – The job description page of User Created jobs will be blank until you configure + the job Pre-configured job description pages provide users with shortcuts and links to many of the functions -that can be accessed under the **[Job Group]** > **[Job]** node in the Jobs Tree in the Navigation +that you can access under the **[Job Group]** > **[Job]** node in the Jobs Tree in the Navigation Pane. ![Job Description page options](/images/accessanalyzer/11.6/admin/jobs/job/descriptionpageoptions.webp) @@ -93,10 +92,10 @@ The sections and options of the job description page are: The Overview section provides summary information about the job, and includes the following information: -- Inherited settings – Job settings can be applied directly or inherited from a parent job group or - even the General Settings level. See the +- Inherited settings – You can apply job settings directly or inherit them from a parent job group + or even the General Settings level. See the [Jobs with Inherited Settings](#jobs-with-inherited-settings) topic for additional information. -- Reports – Displays a list of reports that are generated by this job +- Reports – Displays a list of reports this job generates - Results – Displays a list of data tables and views created and populated by the job - Configuration - If applicable, configure parameters for the job's analysis tasks @@ -109,9 +108,9 @@ information: - Status – Displays information on job status (Running, Success, Error) - Duration – Displays length of time each job took -- Graph – Displays a line graph that has information for the last five times the job was executed +- Graph – Displays a line graph that has information for the last five times the job ran -Prior to running any job or job group, ensure the following have been properly configured: +Before running any job or job group, ensure the following have been properly configured: - Queries, Analysis, Actions, and Reports are configured as desired - If collecting data, at least one host list has been assigned @@ -123,13 +122,13 @@ and that the inheritance of settings is adjusted accordingly. ### Jobs with Inherited Settings -Job settings can be applied directly or inherited from a parent job group or even the General -Settings level. If settings are applied directly to a job, these are shown in the Overview section -under the job description: +You can apply job settings directly or inherit them from a parent job group or even the General +Settings level. If you apply settings directly to a job, the Overview section shows them under the +job description: ![Job Inherited settings](/images/accessanalyzer/11.6/admin/jobs/job/inheritedsettings.webp) -In the example above, the **Assigned 1 Host List** setting is applied directly to the job. Other +In the preceding example, the **Assigned 1 Host List** setting is applied directly to the job. Other settings are inherited from the parent job group. Clicking the **Show inherited settings** button opens this list of the inherited settings. @@ -147,22 +146,22 @@ The following settings can be inherited from a parent: ### Parameter Configuration -If a job has analysis parameters that can be customized, those parameters can be configured in the +If a job has analysis parameters you can customize, you can configure those parameters in the Configuration section of the Job Description Page. -Follow the steps to configure customizable parameters using the Configuration option on the Job +To configure customizable parameters using the Configuration option on the Job Description Page: **Step 1 –** Navigate to the **Jobs > [Job Group] > [Job]** node. If the job has customizable -parameters, they will be located under Configuration in the job's Overview section. +parameters, they appear under Configuration in the job's Overview section. ![Configuration section of Job description page](/images/accessanalyzer/11.6/admin/jobs/job/descriptionpageconfigurationsection.webp) -**Step 2 –** Click on a parameter to open the Parameter Configuration window. +**Step 2 –** Click a parameter to open the Parameter Configuration window. :::note To view a tool-tip that contains information about the Variable Name and the Task Name -that the parameter is associated with, hover the mouse over the parameter. +associated with the parameter, hover the mouse over the parameter. ::: @@ -171,7 +170,7 @@ that the parameter is associated with, hover the mouse over the parameter. **Step 3 –** Configure the parameter in the Parameter Configuration window. Click **Save** to save changes and exit the window. Click **Cancel** to exit without saving. -The parameter has now been configured. The parameters can also be configured in the Analysis Node +You have now configured the parameter. You can also configure parameters in the Analysis Node under the job's Configure Node. See the [Analysis Node](/docs/accessanalyzer/11.6/admin/jobs/job/configure/analysis/analysis.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/admin/jobs/job/properties/autoretry.md b/docs/accessanalyzer/11.6/admin/jobs/job/properties/autoretry.md index 0cd9afcc45..4d2b6d02da 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/job/properties/autoretry.md +++ b/docs/accessanalyzer/11.6/admin/jobs/job/properties/autoretry.md @@ -11,7 +11,7 @@ the selected host status values: Offline, Failed, Errors, and Warnings. ![Auto Retry tab of Job Properties](/images/accessanalyzer/11.6/admin/jobs/job/properties/autoretry.webp) -Check the desired Host Status values to generate a retry, and then configure the Refresh Data and +Check the Host Status values you want to generate a retry, and then configure the Refresh Data and Retry Options settings. Finally, enter a User name (domain\user) and Password in the Scheduler Authentication section. @@ -22,4 +22,4 @@ field. Click **OK** to save configuration changes and close the Job Properties window. Click **Cancel** if -no changes were made. +you didn't make changes. diff --git a/docs/accessanalyzer/11.6/admin/jobs/job/properties/connection.md b/docs/accessanalyzer/11.6/admin/jobs/job/properties/connection.md index aeee232a16..713137fb78 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/job/properties/connection.md +++ b/docs/accessanalyzer/11.6/admin/jobs/job/properties/connection.md @@ -12,18 +12,18 @@ the system default (the account being used to run Enterprise Auditor), or to sel Connection Profile. :::note -It is a best practice to set the Connection Profile at the same level where the job’s host -list is set. For example, if the host list is set under the job group’s **Settings** node, then that -is where the Connection Profile should be configured. If the host list is set under the **[Job]** > -**Configure** node, then this is where the Connection Profile should be configured. +As a best practice, set the Connection Profile at the same level where you set the job’s +host list. For example, if you set the host list under the job group’s **Settings** node, configure +the Connection Profile there. If you set the host list under the **[Job]** > +**Configure** node, configure the Connection Profile there. ::: ![Connection tab of the Jop Properties](/images/accessanalyzer/11.6/admin/jobs/job/properties/viewxml.webp) -Select the desired option to identify the required Connection Profile for the job. See the +Select the option you want to identify the required Connection Profile for the job. See the [Connection Node](/docs/accessanalyzer/11.6/admin/jobs/group/settings/connection.md) topic for additional information for the three connection options. Click **OK** to save configuration changes and close the Job Properties window. Click **Cancel** if -no changes were made. +you didn't make changes. diff --git a/docs/accessanalyzer/11.6/admin/jobs/job/properties/general.md b/docs/accessanalyzer/11.6/admin/jobs/job/properties/general.md index 9f1e54c2f7..b527eb4e06 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/job/properties/general.md +++ b/docs/accessanalyzer/11.6/admin/jobs/job/properties/general.md @@ -14,13 +14,14 @@ The following options are available: - Job Name - Description -- Log Level – Indicates the job log level, which can be inherited from the global **Settings** > - **Application** log level or customized here. See below for additional information. +- Log Level – Indicates the job log level, which you can inherit from the global **Settings** > + **Application** log level or customize here. See the following Log Level section for additional + information. - Write CSV Files To Job Output Directory – Exports the native data table created by a query to a CSV file in the job’s output directory. If there are multiple tables in the job, this option creates one file per table. - Timeout [value] minutes – Job’s thread timeout value -- Command – Provides the ability to enter a command that will be executed from the command line upon +- Command – lets you enter a command that runs from the command line upon job completion ## Log Level @@ -30,7 +31,7 @@ The log level feature includes the following options: - Use global setting – use the Application log level feature, configured at the global level. :::note - By selecting the another option from the drop-down list, you break inheritance for + By selecting the another option from the dropdown list, you break inheritance for this job. ::: @@ -39,8 +40,8 @@ The log level feature includes the following options: - Records all Info level information - Records everything else that happens - Creates the largest file -- Info – Records information about what stage of the job is being performed when errors or warnings - occurred +- Info – Records information about what stage the job is in when errors or warnings + occur - Records all Warning level information - Records job progress information - Warning – Records all warnings which occur during job execution diff --git a/docs/accessanalyzer/11.6/admin/jobs/job/properties/history.md b/docs/accessanalyzer/11.6/admin/jobs/job/properties/history.md index 4875602277..b98adebbb2 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/job/properties/history.md +++ b/docs/accessanalyzer/11.6/admin/jobs/job/properties/history.md @@ -14,10 +14,10 @@ broken inheritance at a job group level, or to configure settings just for this By default, all jobs are set to inherit the Data Retention Period and Log Retention Period settings, the **Use Default Setting** option. Deselect the **Use Default Settings** option to configure custom -settings for the job. Then provide the desired Data Retention Period and Log Retention Period -settings. See the +settings for the job. Then provide the Data Retention Period and Log Retention Period settings you +want. See the [History](/docs/accessanalyzer/11.6/admin/settings/history.md) topic for additional information. Click **OK** to save configuration changes and close the Job Properties window. Click **Cancel** if -no changes were made. +you didn't make changes. diff --git a/docs/accessanalyzer/11.6/admin/jobs/job/properties/notification.md b/docs/accessanalyzer/11.6/admin/jobs/job/properties/notification.md index 7673df14e4..2dc5f2f033 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/job/properties/notification.md +++ b/docs/accessanalyzer/11.6/admin/jobs/job/properties/notification.md @@ -12,9 +12,9 @@ inherit the global configuration or to configure settings just for this job. ![Notification tab of Job Properties](/images/accessanalyzer/11.6/admin/jobs/job/properties/notification.webp) Deselect the **Use Global Settings** option to configure custom settings for the job. Then provide a -specific list of recipients for email notifications generated by this job. Multiple email addresses -can be input by adding a semicolon (;) and space between entries. This is specific to Notification -analysis module tasks. +specific list of recipients for email notifications generated by this job. You can input multiple +email addresses by adding a semicolon (;) and space between entries. This is specific to +Notification analysis module tasks. Click **OK** to save configuration changes and close the Job Properties window. Click **Cancel** if -no changes were made. +you didn't make changes. diff --git a/docs/accessanalyzer/11.6/admin/jobs/job/properties/overview.md b/docs/accessanalyzer/11.6/admin/jobs/job/properties/overview.md index 157fbfbf2e..e78454e3d6 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/job/properties/overview.md +++ b/docs/accessanalyzer/11.6/admin/jobs/job/properties/overview.md @@ -6,15 +6,15 @@ sidebar_position: 40 # Job Properties -Jobs can be configured to inherit global settings down through parent job groups or to be -individually configured at the job level through the Job Properties window. +You can configure jobs to inherit global settings down through parent job groups or configure them +individually at the job level through the Job Properties window. ![Open Job Properties from Jobs Tree](/images/accessanalyzer/11.6/admin/jobs/job/properties/jobstree.webp) To configure a job’s properties, open the Job Properties window by right-clicking on the job's node in the Navigation pane and selecting **Properties**. -The properties can be configured at the job level within the Job Properties window using the +You can configure the properties at the job level within the Job Properties window using the following tabs: - [General Tab](/docs/accessanalyzer/11.6/admin/jobs/job/properties/general.md) @@ -33,4 +33,4 @@ the for additional information. Click **OK** to save configuration changes and close the Job Properties window. Click **Cancel** if -no changes were made. +you didn't make changes. diff --git a/docs/accessanalyzer/11.6/admin/jobs/job/properties/performance.md b/docs/accessanalyzer/11.6/admin/jobs/job/properties/performance.md index 6bb3a1af2b..0938178a5f 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/job/properties/performance.md +++ b/docs/accessanalyzer/11.6/admin/jobs/job/properties/performance.md @@ -6,22 +6,21 @@ sidebar_position: 20 # Performance Tab -The Performance tab provides options that can be used to improve job performance and runtime. +Use the Performance tab options to improve job performance and runtime. ![Performance tab of Job Properties](/images/accessanalyzer/11.6/admin/jobs/job/properties/performance.webp) Adjust the following settings by sliding the needle up and down the line: - Concurrent Worker Threads – The number of worker threads selected equals the number of hosts being - queried concurrently. If needed, this value can be increased. -- Skip Hosts that do not respond to PING – Selected by default. Deselect if a target host has been - configured to not respond to PING requests, allowing Enterprise Auditor to scan the target host - without a PING response. + queried concurrently. If needed, you can increase this value. +- Skip Hosts that don't respond to PING – Selected by default. Deselect if you configured a target + host to not respond to PING requests, allowing Enterprise Auditor to scan the target host without + a PING response. :::note - In most cases, it is not recommend to deselect this option, as it causes the job to - continue querying offline hosts until the job timeout value is reached, set by default to 20 - minutes. + In most cases, avoid deselecting this option. Doing so causes the job to continue + querying offline hosts until the job timeout value is reached, set by default to 20 minutes. ::: @@ -29,4 +28,4 @@ Adjust the following settings by sliding the needle up and down the line: offline for not responding to PING Click **OK** to save configuration changes and close the Job Properties window. Click **Cancel** if -no changes were made. +you didn't make changes. diff --git a/docs/accessanalyzer/11.6/admin/jobs/job/properties/reportroles.md b/docs/accessanalyzer/11.6/admin/jobs/job/properties/reportroles.md index 883f1c837c..4d50bec43c 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/job/properties/reportroles.md +++ b/docs/accessanalyzer/11.6/admin/jobs/job/properties/reportroles.md @@ -6,30 +6,29 @@ sidebar_position: 50 # Report Roles Tab -The Report Roles tab is part of the Role Bases Access feature of Enterprise Auditor. If Role Based -Access has been enabled, the table displays all accounts that can view reports within the Web -Console. If Role Based Access has not been enabled, all accounts have access to all reports, and the +The Report Roles tab is part of the Role Bases Access feature of Enterprise Auditor. If you enable +Role Based Access, the table displays all accounts that can view reports within the Web +Console. If you haven't enabled Role Based Access, all accounts have access to all reports, and the table is blank. See the [Role Based Access](/docs/accessanalyzer/11.6/admin/settings/access/rolebased/overview.md) topic for additional information. ![Report Roles tab of Job Properties](/images/accessanalyzer/11.6/admin/jobs/job/properties/reportroles.webp) -On the Report Roles tab, report role inheritance cannot be broken. Access to reports is inherited -from the global level to job groups to jobs to report configuration. All user roles configured at -the global level (**Settings** > **Roles**) are inherited down to all reports. Only the Global -Options Administrator, the Access Administrator, and the Host Management Administrator do not have -access to reports. +On the Report Roles tab, you can't break report role inheritance. Reports inherit access from the +global level to job groups to jobs to report configuration. All reports inherit the user roles +configured at the global level (**Settings** > **Roles**). Only the Global Options Administrator, +the Access Administrator, and the Host Management Administrator don't have access to reports. -The **Include Report Viewers from this object's parent** option can be unchecked to automatically +You can uncheck the **Include Report Viewers from this object's parent** option to automatically remove any user with the Report Viewer role inherited from a parent object to the job. Remember, -this does not apply to global inheritance. +this doesn't apply to global inheritance. -Additional accounts can be added with the Report Viewer role at the job level and inherited down to -all reports generated by the job. Click **Add Report Viewer** to open the Select User or Group -window and grant a new account access to these reports. Inheritance can be broken for accounts that -have not inherited the report role from the global level. Select an account and click **Delete -Report Viewer** to deny access to the reports. +You can add additional accounts with the Report Viewer role at the job level. Enterprise Auditor +inherits their access down to all reports generated by the job. Click **Add Report Viewer** to open +the Select User or Group window and grant a new account access to these reports. You can break +inheritance for accounts that haven't inherited the report role from the global level. Select an +account and click **Delete Report Viewer** to deny access to the reports. The table displays the following information: @@ -37,7 +36,7 @@ The table displays the following information: - Type – Account type (user or group) - Role – Role assigned to account which grants access to reports - Inherited From – Indicates the level at which the account was granted access to reports. Remember, - global inheritance cannot be broken. + you can't break global inheritance. Click **OK** to save configuration changes and close the Job Properties window. Click **Cancel** if -no changes were made. +you didn't make changes. diff --git a/docs/accessanalyzer/11.6/admin/jobs/job/properties/reportsettings.md b/docs/accessanalyzer/11.6/admin/jobs/job/properties/reportsettings.md index 6ee838770a..3808ed50f6 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/job/properties/reportsettings.md +++ b/docs/accessanalyzer/11.6/admin/jobs/job/properties/reportsettings.md @@ -13,12 +13,12 @@ this job. ![Report Settings tab of Job Properties](/images/accessanalyzer/11.6/admin/jobs/job/properties/reportsettings.webp) -Use the Publish Options drop-down menu to customize the publish setting for the job. To configure +Use the Publish Options dropdown menu to customize the publish setting for the job. To configure custom Email settings for the job, select the **Use These Email Settings** option and then provide -the desired Email information. Multiple email addresses can be input by adding a semicolon (;) and -space between entries. See the +the Email information you want. You can input multiple email addresses by adding a semicolon (;) +and space between entries. See the [Reporting Node](/docs/accessanalyzer/11.6/admin/jobs/group/settings/reporting.md) topic for additional information on the Publish and Email options. Click **OK** to save configuration changes and close the Job Properties window. Click **Cancel** if -no changes were made. +you didn't make changes. diff --git a/docs/accessanalyzer/11.6/admin/jobs/job/properties/storage.md b/docs/accessanalyzer/11.6/admin/jobs/job/properties/storage.md index 21f28834eb..38c271d000 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/job/properties/storage.md +++ b/docs/accessanalyzer/11.6/admin/jobs/job/properties/storage.md @@ -12,12 +12,12 @@ group level, or to configure settings just for this job. ![Storage tab of the Job Properties](/images/accessanalyzer/11.6/admin/jobs/job/properties/storage.webp) -By default, all jobs are set to inherit the storage setting, the **Use Default** option. To +By default, all jobs inherit the storage setting through the **Use Default** option. To configure a different profile for the job, select the **Use This Profile** option and select the -desired Storage Profile from the drop-down menu. Storage Profiles can only be configured at the +desired Storage Profile from the dropdown menu. You can only configure Storage Profiles at the **Settings** > **Storage** node. See the [Storage](/docs/accessanalyzer/11.6/admin/settings/storage/overview.md) topic for additional information. Click **OK** to save configuration changes and close the Job Properties window. Click **Cancel** if -no changes were made. +you didn't make changes. diff --git a/docs/accessanalyzer/11.6/admin/jobs/job/properties/viewxml.md b/docs/accessanalyzer/11.6/admin/jobs/job/properties/viewxml.md index a5e6c1d781..216422b239 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/job/properties/viewxml.md +++ b/docs/accessanalyzer/11.6/admin/jobs/job/properties/viewxml.md @@ -14,7 +14,7 @@ At the bottom of the Job Properties window is the **View XML** button. To view t | Job Properties Window | Job XML File | This opens the job’s XML file, which contains all of the job, query, and reporting configurations. -When the log level is directly set at job level, the job XML `` parameter will show a +When you directly set the log level at job level, the job XML `` parameter shows a value of: - 0 for Debug @@ -23,6 +23,6 @@ value of: - 3 for Error :::note -Job analysis configurations are kept in a separate XML file. +Enterprise Auditor keeps job analysis configurations in a separate XML file. ::: diff --git a/docs/accessanalyzer/11.6/admin/jobs/job/results.md b/docs/accessanalyzer/11.6/admin/jobs/job/results.md index f86ffc9258..aff6164474 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/job/results.md +++ b/docs/accessanalyzer/11.6/admin/jobs/job/results.md @@ -6,31 +6,31 @@ sidebar_position: 20 # Results Node -Once a job has been executed, the query populated native data tables, the analysis and action -populated materialized tables and views, and the generated reports can be viewed under the job’s +Once you execute a job, you can view the query-populated native data tables, the analysis- and +action-populated materialized tables and views, and the generated reports under the job’s Results node. :::note -Native data tables are only populated by jobs with configured queries. Materialized tables -and views are only generated by jobs with configured analysis or action tasks. Reports are only -generated by jobs with configured reports. +Jobs with configured queries only populate native data tables. Jobs with configured analysis +or action tasks only generate materialized tables and views. Jobs with configured reports only +generate reports. ::: ![Results Node](/images/accessanalyzer/11.6/admin/jobs/job/resultsnode.webp) Every job generates a native data table when executed, which appears at the top of the Results node. -The native data table, or raw data table, is produced by query execution. It contains all raw data -collected by the scan. It is often named DEFAULT, but may have another name that is set during query -configuration. If no query is executed by the job, the DEFAULT table is listed as a placeholder only -and will be empty (0 rows). It is possible to have multiple queries in the same job, though not -recommended. These queries could write to the same native data table, or each query could write to -its own native data table. If multiple native data tables are being generated by one job, they are -listed in alphanumeric order at the top of the Results node list. - -Analysis tasks can be configured to generate materialized tables and views. Action tasks create +Query execution produces the native data table, or raw data table. It contains all raw data +collected by the scan. It is often named DEFAULT, but may have another name that you set during +query configuration. If the job executes no query, the DEFAULT table appears as a placeholder only +and remains empty (0 rows). A job can have multiple queries, though avoid using more than one when +possible. These queries could write to the same native data table, or each query could write to +its own native data table. If one job generates multiple native data tables, they appear in +alphanumeric order at the top of the Results node list. + +You can configure analysis tasks to generate materialized tables and views. Action tasks create action status tables. These appear beneath the native data tables under the Results node in alphanumeric order. -Finally, any reports generated by the job, both published and unpublished, will be listed beneath +Finally, any reports generated by the job, both published and unpublished, appear beneath the materialized tables and views in alphanumeric order. diff --git a/docs/accessanalyzer/11.6/admin/jobs/job/status.md b/docs/accessanalyzer/11.6/admin/jobs/job/status.md index 8fcd3d06d0..cfa7e97ea5 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/job/status.md +++ b/docs/accessanalyzer/11.6/admin/jobs/job/status.md @@ -6,16 +6,15 @@ sidebar_position: 10 # Status Node -Once a job has been executed, it always generates the tables providing information on host -connection status, job statistics, job task statistics, and error and warning messages can be viewed -under the job’s Status node: +After a job runs, tables containing information on host connection status, job statistics, job task +statistics, and error and warning messages appear under the job’s Status node: ![Status Node](/images/accessanalyzer/11.6/admin/jobs/job/statusnode.webp) The Status node tables are: - ConnectStatus table – Lists all hosts queried during job execution and the access status of the - scan, unless the System Default is being used + scan, unless you're using the System Default - Job Stats table – Provides information on the selected job’s runtime details, according to the global configuration set in the **Settings** > **Application** node. By default, this is set to not filter the data. @@ -25,8 +24,8 @@ The Status node tables are: :::note The Job Statistics Retention settings in the **Settings** > **Application** node - control how long the job statistics history is kept in the database and displayed Job Stats and - Task Stats tables. See the + control how long the database keeps the job statistics history and displays it in the Job Stats + and Task Stats tables. See the [Application](/docs/accessanalyzer/11.6/admin/settings/application/overview.md) topic for additional information. ::: @@ -36,7 +35,7 @@ The Status node tables are: execution of the job. For example, a frequently generated message is `WARNING: No Host found for processing`. - - If this message is generated by an analysis or reporting job, then there is no problem as that - type of job does not need a host list assigned - - However, if this message is generated by a job running a data collection query, this warning - would explain why the native data table is empty + - If an analysis or reporting job generates this message, there is no problem as that + type of job doesn't need a host list assigned + - However, if a job running a data collection query generates this message, this warning + explains why the native data table is empty diff --git a/docs/accessanalyzer/11.6/admin/jobs/overview.md b/docs/accessanalyzer/11.6/admin/jobs/overview.md index 722b87d4b4..34e27e362f 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/overview.md +++ b/docs/accessanalyzer/11.6/admin/jobs/overview.md @@ -6,8 +6,8 @@ sidebar_position: 70 # Jobs Tree -Jobs are the fundamental unit of Enterprise Auditor. It is through jobs that all data collection -queries, analysis tasks, notification tasks, action tasks, and report generation occur. Jobs are +Jobs are the fundamental unit of Enterprise Auditor. All data collection queries, analysis tasks, +notification tasks, action tasks, and report generation occur through jobs. Jobs are housed within the Jobs tree of the Navigation pane. The Jobs Tree is located in the Navigation Pane on the Enterprise Auditor Console. @@ -36,27 +36,27 @@ Each component within the Jobs tree has an icon for quick reference. The icons a | ![jobsdata](/images/accessanalyzer/11.6/admin/jobs/jobsdata.webp) | Job’s Data Table or View | | ![jobsreport](/images/accessanalyzer/11.6/admin/jobs/jobsreport.webp) | Job’s Report | -A green checkmark over a Job or Job Group icon indicates a configuration change has been made to the -job or job group. The global settings configured under the Settings node are inherited down through -the Jobs tree to the job unless inheritance is broken in a job group’s Settings node, a job’s +A green checkmark over a Job or Job Group icon indicates you made a configuration change to the +job or job group. The Jobs tree inherits the global settings configured under the Settings node down +to the job unless you break inheritance in a job group’s Settings node, a job’s Configure node, or a job’s Properties window. See the [Navigating the Console](/docs/accessanalyzer/11.6/admin/navigate/overview.md) for additional information. ## Job Execution Options -Enterprise Auditor is designed to execute jobs one at a time in the order assigned. If a job group -is run, the jobs execute in the order listed within the job group. Job groups are designed to run -data collection jobs before running analysis and reporting jobs. If multiple jobs are independently -triggered to run, the jobs execute in the order triggered. +Enterprise Auditor is designed to execute jobs one at a time in the order assigned. If you run a job +group, the jobs execute in the order listed within the job group. Job groups are designed to run +data collection jobs before running analysis and reporting jobs. If you independently trigger +multiple jobs to run, the jobs execute in the order triggered. Jobs execution options include: - Manual or Ad Hoc - Applies logged in user’s credentials to execute the job on the Enterprise Auditor Console server - - Job progress can be monitored through the **Running Instances** node - - Order of job execution can be manipulated on the **Running Instances** node + - You can monitor job progress through the **Running Instances** node + - You can manipulate the order of job execution on the **Running Instances** node - Closing the Enterprise Auditor Console terminates the running job and clear the jobs queue - Schedule - Applies Schedule Service Account credentials to execute the job through Windows Task Scheduler @@ -66,19 +66,19 @@ Jobs execution options include: ## Changes Window -The Changes window is where jobs are created by customers or professional services engineers. Custom -jobs can be enabled to track changes to configuration settings. When enabled, configuration changes -are tracked in change logs stored within the job folder. Changes can also be viewed within this -window. +The Changes window is where customers or professional services engineers create jobs. You can +enable custom jobs to track changes to configuration settings. When enabled, Enterprise Auditor +tracks configuration changes in change logs stored within the job folder. You can also view +changes within this window. -Remember, custom jobs are not shipped with Enterprise Auditor but instead user created. +Remember, Enterprise Auditor doesn't ship custom jobs; users create them instead. The Changes window opens from the **Changes** option in the right-click menu from the selected Jobs tree, job group, or job node. ![Changes Window](/images/accessanalyzer/11.6/admin/jobs/changeswindow.webp) -Select **Enabled** from the drop-down menu in the upper-left corner to turn on change tracking of +Select **Enabled** from the dropdown menu in the upper-left corner to turn on change tracking of configuration settings. Select a modification from the table and click **Undo** to revert the change. @@ -97,9 +97,10 @@ The window columns display the following information: Select a modification from the table and click **Undo** to revert the change. -If configuration change tracking is **Disabled**, configuration changes are only written directly to -the job’s XML file. If the configuration change tracking feature was previously enabled and then -disabled at a later time, an option is provided to merge changes back into the job’s XML file. +If configuration change tracking is **Disabled**, Enterprise Auditor only writes configuration +changes directly to the job’s XML file. If you previously enabled the configuration change tracking +feature and then disabled it at a later time, Enterprise Auditor provides an option to merge changes +back into the job’s XML file. ![Change Window Merge Changes](/images/accessanalyzer/11.6/admin/jobs/changeswindowmerge.webp) @@ -109,10 +110,10 @@ the Enterprise Auditor pop-up window to confirm the merge. ![Changes Window Locked](/images/accessanalyzer/11.6/admin/jobs/changeswindowlocked.webp) -Changes between releases are tracked. Only jobs that are locked can be upgraded. +Enterprise Auditor tracks changes between releases. You can only upgrade jobs that are locked. :::note -Jobs that are included in Enterprise Auditor are locked and changes cannot be made to +Jobs that are included in Enterprise Auditor are locked, and you can't make changes to those jobs. ::: diff --git a/docs/accessanalyzer/11.6/admin/maintenance/backuprecovery.md b/docs/accessanalyzer/11.6/admin/maintenance/backuprecovery.md index 5770907d5b..11183e5a33 100644 --- a/docs/accessanalyzer/11.6/admin/maintenance/backuprecovery.md +++ b/docs/accessanalyzer/11.6/admin/maintenance/backuprecovery.md @@ -6,20 +6,20 @@ sidebar_position: 30 # Backup and Recovery -For data recovery purposes, the Enterprise Auditor does not need a complete image back up of the -Enterprise Auditor Console server. Rather a standard file level back up of a few key components is -all that is necessary. This document contains a step-by-step guide for back up and recovery. The -choice of back up utility is left to the Enterprise Auditor user. +For data recovery purposes, the Enterprise Auditor doesn't need a complete image back up of the +Enterprise Auditor Console server. Rather, a standard file level back up of a few key components is +sufficient. This document contains a step-by-step guide for back up and recovery. The +Enterprise Auditor user chooses the back up utility. :::note -This does not cover back up of the Enterprise Auditor database. +This doesn't cover back up of the Enterprise Auditor database. ::: ## Steps to Back Up the Console Server -Follow these steps to back up the key components necessary for data recovery of the Enterprise -Auditor Console server. +To back up the key components necessary for data recovery of the Enterprise +Auditor Console server: **Step 1 –** Obtain or save the installation media for Enterprise Auditor. @@ -37,8 +37,8 @@ built-in environment variable `%SAINSTALLDIR%`): - ...\ STEALTHbits\StealthAUDIT\rba.conf: Contains the Role Based Access Configuration - ...\ STEALTHbits\StealthAUDIT\StealthAUDIT.LIC: The license key -**Step 3 –** Back up all Scheduled Tasks. The method of back up is determined by the Enterprise -Auditor user. This can be as simple as copying the contents of the tasks folder from the following +**Step 3 –** Back up all Scheduled Tasks. The Enterprise Auditor user determines the method of back +up. This can be as simple as copying the contents of the tasks folder from the following two locations: ![C:\Windows\Tasks](/images/accessanalyzer/11.6/admin/maintenance/maintenance_3.webp) @@ -49,18 +49,18 @@ two locations: - C:\Windows\System32\Tasks -All key components necessary for data recovery have now been backed up. +You have now backed up all key components necessary for data recovery. ## Steps to Restore the Console Server Follow these steps for data recovery of the Enterprise Auditor Console server. -**Step 1 –** Confirm the prerequisites have been met on the Enterprise Auditor Console Server. See +**Step 1 –** Confirm that you've met the prerequisites on the Enterprise Auditor Console Server. See the [Requirements](/docs/accessanalyzer/11.6/requirements/overview.md) topic for specific prerequisites. -**Step 2 –** Install the Enterprise Auditor application. Do not start the Enterprise Auditor +**Step 2 –** Install the Enterprise Auditor application. Don't start the Enterprise Auditor application at this time. **Step 3 –** Restore all of the backed up files and folders from Step 2 of Steps to Back up the @@ -92,7 +92,7 @@ SET SA_Node = @NHost Where SA_Node = @OHost; ``` -**Step 6 –** Start Enterprise Auditor and confirm all settings and jobs have been restored. +**Step 6 –** Start Enterprise Auditor and confirm that you've restored all settings and jobs. **Step 7 –** Enable Role Based Access to write the necessary registry keys: @@ -106,4 +106,4 @@ Where SA_Node = @OHost; [Role Based Access](/docs/accessanalyzer/11.6/admin/settings/access/rolebased/overview.md) topic for more information -The Enterprise Auditor Console Server is now restored. +You have now restored the Enterprise Auditor Console Server. diff --git a/docs/accessanalyzer/11.6/admin/maintenance/bestpractices.md b/docs/accessanalyzer/11.6/admin/maintenance/bestpractices.md index 7736a2680d..d06c47d12d 100644 --- a/docs/accessanalyzer/11.6/admin/maintenance/bestpractices.md +++ b/docs/accessanalyzer/11.6/admin/maintenance/bestpractices.md @@ -6,20 +6,19 @@ sidebar_position: 50 # Best Practices -With any new product, a few pointers can really get us started on the right foot. In the spirit of -making you successful, here are some tips that will help you become an effective user of the -Enterprise Auditor in no time. Enjoy! +With any new product, a few pointers can help you get started effectively. Here are some tips to +help you become an effective user of Enterprise Auditor quickly. ## Do The following is a list of best practices to use for Enterprise Auditor: -- Read all Job and Job Group descriptions and instructions prior to running any solution -- Scope all collection queries to target just the desired objects, locations, or hosts you want to +- Read all Job and Job Group descriptions and instructions before running any solution +- Scope all collection queries to target just the objects, locations, or hosts you want to collect information from -- Run new solutions against a single host or subset of data prior to running against all to ensure +- Run new solutions against a single host or subset of data before running against all to ensure proper operation, configuration, and output of each job -- Leverage service accounts (if possible) containing the proper permissions to access the +- Use service accounts (if possible) containing the proper permissions to access the information you want to audit rather than personal user accounts (this will reduce “access denied” warnings due to insufficient privileges) - Set a username and password for any scheduled task @@ -27,31 +26,31 @@ The following is a list of best practices to use for Enterprise Auditor: Enterprise Auditor System Requirements & Installation Notes document for details) - Set a connection profile inside the Job “properties” menu for any job that runs using the Exchange Metrics data collector -- Check the “Messages” table within any Job’s “Results” node if reports do not generate or +- Check the “Messages” table within any Job’s “Results” node if reports don't generate or collection doesn’t appear to be working properly - Configure history settings at the Job level (as opposed to at the Global or Job Group level) to avoid unnecessary storage consumption within SQL - Contact Netwrix Support with ANY questions you have -## Do Not +## Don't The following is a list of practices to avoid for Enterprise Auditor. -- Do not change Job or Job Group names within the Job Tree -- Do not attempt to run an entire Solution Set without configuring your scoping options first -- Do not confuse WARNINGS for errors in data collection. Warnings are purely informational -- Do not change the name of your Enterprise Auditor database -- Do not edit a job’s configuration or open any query or analysis rule while that job is running -- Do not use the Fully Qualified Domain Name of a host when manually entering hosts to run queries +- Don't change Job or Job Group names within the Job Tree +- Don't attempt to run an entire Solution Set without configuring your scoping options first +- Don't confuse WARNINGS for errors in data collection. Warnings are purely informational +- Don't change the name of your Enterprise Auditor database +- Don't edit a job’s configuration or open any query or analysis rule while that job is running +- Don't use the Fully Qualified Domain Name of a host when manually entering hosts to run queries against; instead, use the Common Name -- Do not enable “Debug” logging unless needed for additional troubleshooting -- Do not change the database Enterprise Auditor writes to at the global level; instead, change the +- Don't enable “Debug” logging unless needed for additional troubleshooting +- Don't change the database Enterprise Auditor writes to at the global level; instead, change the database at the job level if desired ### Contact Support -When the checklist items do not resolve the issue, contact support with as much applicable -information as possible from the table below. It is possible that a hot fix may already exist for +When the checklist items don't resolve the issue, contact support with as much applicable +information as possible from the following information. A hot fix may already exist for the product. **What is the version of the Access Analyzer application?** @@ -87,4 +86,4 @@ See the Export Job to Zip Archive Window section for additional instruction. Jobs > [Solution] > [Job Group and/or Job] > Status > Messages table **Are there any messages in the ConnectStatus Table?** -Jobs > [Solution] > [Job Group and/or Job] > Status > ConnectStatus table \ No newline at end of file +Jobs > [Solution] > [Job Group and/or Job] > Status > ConnectStatus table diff --git a/docs/accessanalyzer/11.6/admin/maintenance/troubleshooting.md b/docs/accessanalyzer/11.6/admin/maintenance/troubleshooting.md index 3a006c46b0..34e3335af5 100644 --- a/docs/accessanalyzer/11.6/admin/maintenance/troubleshooting.md +++ b/docs/accessanalyzer/11.6/admin/maintenance/troubleshooting.md @@ -15,16 +15,16 @@ installed. The default installation directory is: `C:\Program Files (x86)\STEALTHbits\StealthAUDIT\` -If the installation directory was customized during installation, it will be: +If you customized the installation directory during installation, it will be: `…\STEALTHbits\StealthAUDIT\` -The Enterprise Auditor install directory has several logs that can be accessed for troubleshooting +The Enterprise Auditor install directory has several logs that you can access for troubleshooting purposes. This includes: - The Application log which contains logging of all activities within Enterprise Auditor - The Upgrade log which logs activities related to the upgrade process -- The upgrade archive which is a zip file containing all of your Enterprise Auditor jobs prior to +- The upgrade archive which is a zip file containing all of your Enterprise Auditor jobs before the upgrade process - Sensitive Data logs that contain details from sensitive data scans performed against various repositories @@ -35,14 +35,14 @@ See the [Logs](#logs) topic for additional information. ## Logs -Enterprise Auditor has a few areas where it stores logs. Make sure the log level is set to DEBUG in -Enterprise Auditor to gather all necessary information. Once the logs have been created and sent to -Netwrix Support, then reset the logging level to save disc space. +Enterprise Auditor has a few areas where it stores logs. Ensure you set the log level to DEBUG in +Enterprise Auditor to gather all necessary information. After you create and send the logs to +Netwrix Support, reset the logging level to save disc space. To set your logging level to debug go to **Settings** > **Application** – **Set the Application log level to Debug** and restart the application. -#### Where Are the Logs Located? +#### Log File Locations | Log Name | Log Location | | ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -70,13 +70,13 @@ and DFS scan types: FSAA Trace Logs: -Below are two types of FSAA trace logs created while in local, applet, or proxy modes: +The following are two types of FSAA trace logs created while in local, applet, or proxy modes: - Parent Trace Log – StealthAUDITRPC*[YYYYMMDD_hhmmss]*[Execution_Host].log - - ProccessID is logged in the job log + - ProccessID appears in the job log - Child Trace Log – StealthAUDITRPC*[session_id]*[ScanType]_[Execution_host]_[Target_host]_[YYMMDD_hhmmss].log - - ProcessID is logged in the Parent trace log + - ProcessID appears in the Parent trace log When running StealthAUDITRPC as a service, the parent trace log reads as: diff --git a/docs/accessanalyzer/11.6/admin/maintenance/updatepasswords.md b/docs/accessanalyzer/11.6/admin/maintenance/updatepasswords.md index 467d1b885d..b33f9471a1 100644 --- a/docs/accessanalyzer/11.6/admin/maintenance/updatepasswords.md +++ b/docs/accessanalyzer/11.6/admin/maintenance/updatepasswords.md @@ -6,10 +6,9 @@ sidebar_position: 20 # Updating Passwords -Credential passwords in Enterprise Auditor occasionally need to be updated due to reasons such as -the password expiring due to existing password expiration polices or for security purposes. If a -password change is required, there are multiple types of accounts where credential passwords must be -updated: +You occasionally need to update credential passwords in Enterprise Auditor due to reasons such as +existing password expiration policies or security purposes. If you need to change a password, there +are multiple types of accounts where you must update credential passwords: - [Storage Profiles](#storage-profiles) - [Connection Profiles ](#connection-profiles) @@ -51,8 +50,8 @@ topic for additional information. ## Schedule Service Accounts Enterprise Auditor uses the Schedule Service Account to run scheduled tasks on the Enterprise -Auditor Console server. The global account is configured at the Settings > Schedule node. However, a -custom account can be assigned to either a Job or a Scheduled Task. +Auditor Console server. You configure the global account at the Settings > Schedule node. However, +you can assign a custom account to either a Job or a Scheduled Task. ### Settings > Schedule Node @@ -63,22 +62,22 @@ topic for additional information on editing the user credentials for the account ### Schedules Node -The Schedules Node opens the Scheduled Actions pages where scheduled tasks are listed. From this -page, actions can be scheduled using the Schedule wizard. See the +The Schedules Node opens the Scheduled Actions pages, which list scheduled tasks. From this +page, you can schedule actions using the Schedule wizard. See the [Schedule Wizard](/docs/accessanalyzer/11.6/admin/schedule/wizard.md) topic for additional information on updating the credentials password in the Schedule wizard. ### Jobs -Jobs are typically scheduled with the global scheduled account. However, Jobs can also be scheduled -with a custom account. See the +Enterprise Auditor typically schedules Jobs with the global scheduled account. However, you can +also schedule Jobs with a custom account. See the [Auto Retry Tab](/docs/accessanalyzer/11.6/admin/jobs/job/properties/autoretry.md) topic for information on updating the Schedule Authentication credentials. ## Notifications (if enabled) -Email notifications are configured in the Notifications node. The following steps only apply if -Notification authentication has been enabled for the Enterprise Auditor Console. See the +You configure email notifications in the Notifications node. The following steps only apply if +you've enabled Notification authentication for the Enterprise Auditor Console. See the [Update Notification Authentication Credentials](/docs/accessanalyzer/11.6/admin/settings/notification.md#update-notification-authentication-credentials) topic for information on updating Notification authentication credentials. diff --git a/docs/accessanalyzer/11.6/admin/navigate/activitiespane.md b/docs/accessanalyzer/11.6/admin/navigate/activitiespane.md index 84f4c0c255..4fc3f928c4 100644 --- a/docs/accessanalyzer/11.6/admin/navigate/activitiespane.md +++ b/docs/accessanalyzer/11.6/admin/navigate/activitiespane.md @@ -6,10 +6,10 @@ sidebar_position: 40 # Activities Pane -The Activities pane displays a list of activities which can be conducted within the currently +The Activities pane displays a list of activities that you can perform within the selected console section. It is only visible if there are activities available for the selected section. In the few cases where the Results pane is a wizard, this pane becomes the navigation pane -for the wizard, e.g. the Enterprise Auditor Host Discovery Wizard. If the currently selected console +for the wizard, e.g. the Enterprise Auditor Host Discovery Wizard. If the selected console section has an associated Activities Pane, it can be found on the right-hand side of the Enterprise Auditor Console. @@ -23,4 +23,4 @@ The following console sections have associated Activities Panes: - Jobs > [Job Group/Job] > Settings node The Guidance section of the Activities Pane will display context sensitive information depending on -what the currently selected console section is. +what the selected console section is. diff --git a/docs/accessanalyzer/11.6/admin/navigate/datagrid.md b/docs/accessanalyzer/11.6/admin/navigate/datagrid.md index c9d3db0a4e..4c32645cf4 100644 --- a/docs/accessanalyzer/11.6/admin/navigate/datagrid.md +++ b/docs/accessanalyzer/11.6/admin/navigate/datagrid.md @@ -21,15 +21,15 @@ The different grouping, filtering, and search methods in the Data Grid are: The Show maximum [value] of total [value] rows, located in the upper-right hand corner of the Data Grid view in the Results Pane, indicates how many rows of data are available within this data grid (the first value) and how many rows of data are available in the Enterprise Auditor database for -this data grid (the second value). The maximum value can be changed by the user and only affects the -maximum number of rows available for this data grid within the Enterprise Auditor Console. The total -value is automatically supplied from the Enterprise Auditor database and cannot be changed by the -user. If the total value is less than the maximum value, then all available data for this grid is +this data grid (the second value). The user can change the maximum value, and it only affects the +maximum number of rows available for this data grid within the Enterprise Auditor Console. The +Enterprise Auditor database automatically supplies the total value, and the user can't change it. +If the total value is less than the maximum value, then all available data for this grid is present for sorting, filtering, and searching. ## Data Grid Right-Click Menu -The right-click menu that affects data grid functionality is accessible by right-clicking on the +Access the right-click menu that affects data grid functionality by right-clicking on the data grid header row. ![Data Grid Functionality](/images/accessanalyzer/11.6/admin/navigate/datagridfunctionality1.webp) @@ -57,7 +57,7 @@ for information on right-click menus within a data grid. ### Customization Window -The Customization window can be used to customize the data grid to only display specific columns. +Use the Customization window to customize the data grid to only display specific columns. ![Customization Window](/images/accessanalyzer/11.6/admin/navigate/datagridfunctionality2.webp) @@ -65,8 +65,8 @@ To open the Customization window, select Field Chooser from the column header ri ![Customization Window](/images/accessanalyzer/11.6/admin/navigate/datagridfunctionality3.webp) -Any column that has been removed from the data grid, either by dragging it off the screen or by -dropping it into this window, will be listed here. A column not currently displayed can be returned +Any column that you remove from the data grid, either by dragging it off the screen or by +dropping it into this window, appears here. You can return a column that isn't displayed to the data grid by dragging-and-dropping it from this window onto the header row. ### Footer @@ -80,8 +80,8 @@ To enable the footer, right-click in a column header and select Footer from the ![Footer display](/images/accessanalyzer/11.6/admin/navigate/datagridfunctionality5.webp) -The footer appears as a gray bar at the bottom of the grid (or grid group). Right-click on the -footer under the desired column. Only the options applicable to the desired column will be valid for +The footer appears as a gray bar at the bottom of the grid (or grid group). Right-click the +footer under the column you want. Only the options applicable to that column will be valid for selection. ![Footer options](/images/accessanalyzer/11.6/admin/navigate/datagridfunctionality6.webp) @@ -97,7 +97,7 @@ The different footer options are: ## Sort -The data grid can be sorted in alphanumeric order by clicking on a column header. +You can sort the data grid in alphanumeric order by clicking on a column header. ![Sort Order](/images/accessanalyzer/11.6/admin/navigate/datagridfunctionality7.webp) @@ -118,22 +118,22 @@ a ‘count’ of records within each group. Expand the group to view the data. ![Expand Group View](/images/accessanalyzer/11.6/admin/navigate/datagridfunctionality10.webp) -Multiple columns can be dragged into the Group By area to form tiered groupings. +You can drag multiple columns into the Group By area to form tiered groupings. :::note -Sorting by the FQDN column is an easy way to see if there are two entries for the same +Sort by the FQDN column to see if there are two entries for the same host. ::: ![Column Header](/images/accessanalyzer/11.6/admin/navigate/datagridfunctionality11.webp) -The data grid can also be grouped by dragging a column header beneath the other column headers +You can also group the data grid by dragging a column header beneath the other column headers either to the stationary section on the left or to the mobile section on the right. Each record counts as a single row for the total rows value, but displays in two rows with the second row dedicated for the moved column. -Drag the column header(s) back to the table to remove the grouping or use the Clear Sort option in +Drag the column headers back to the table to remove the grouping or use the Clear Sort option in the [Data Grid Right-Click Menu](#data-grid-right-click-menu). Additionally, the sort will clear when the user navigates to another place in the console. @@ -145,9 +145,9 @@ dialog located above the Activities Pane. ![Filter](/images/accessanalyzer/11.6/admin/navigate/datagridfunctionality12.webp) -In the header of every column is a drop-down arrow. This provides users with the ability to filter -the data grid for a particular item or items within a column. The drop-down menu has the options of -(All), (Custom…), and an alphabetical listing of all items currently within that column for the data +In the header of every column is a dropdown arrow. This provides users with the ability to filter +the data grid for a particular item or items within a column. The dropdown menu has the options of +(All), (Custom…), and an alphabetical listing of all items within that column for the data grid. - [Custom Filter](#custom-filter) – Click Custom Filter in the header dropdown to open the Custom @@ -171,44 +171,44 @@ The Custom Filter window options are: - Second Comparison Operator – Select from a list of different logical operators that will apply to the second custom filter criteria. - Two wildcard options: - - The underscore (_) can be used to represent any single character - - The asterisk (\*) can be used to represent any series of characters + - Use the underscore (_) to represent any single character + - Use the asterisk (\*) to represent any series of characters #### Creating a Custom Filter -Follow the steps to create a Custom Filter: +To create a Custom Filter: -**Step 1 –** Click the dropdown arrow in the column header for the column where the Custom Filter is -going to be applied and select (Custom…) from the list. The Custom Filter window opens. +**Step 1 –** Click the dropdown arrow in the column header for the column where you want to apply +the Custom Filter and select (Custom…) from the list. The Custom Filter window opens. ![Creating a Custom Filter](/images/accessanalyzer/11.6/admin/navigate/datagridfunctionality14.webp) -**Step 2 –** Set the desired criteria for the custom filter. Select the logical operator from the -drop-down menu on the left and set the criteria in the textbox on the right. +**Step 2 –** Set the criteria you want for the custom filter. Select the logical operator from the +dropdown menu on the left and set the criteria in the textbox on the right. **Step 3 –** Select either AND/OR and set the second criteria field, following the same method as Step 2. -**Step 4 –** Click OK to confirm changes. The custom filter criteria is now applied to the Data -Grid. +**Step 4 –** Click OK to confirm changes. Enterprise Auditor now applies the custom filter criteria +to the Data Grid. -In the example above, OSName is like \*2008\* AND not like \*Standard\*, the filter returns all data +In this example, OSName is like \*2008\* AND not like \*Standard\*, the filter returns all data records with an operating system name that contains “2008” but not “Standard,” e.g. Windows Server -2008 Enterprise Edition, 64 bit and Windows Server 2008 R2 Datacenter Edition, 64-bit, etc. Complex -filters can be created using the Advanced Search option in the Filtration Dialog. +2008 Enterprise Edition, 64 bit and Windows Server 2008 R2 Datacenter Edition, 64-bit, etc. You can +create complex filters using the Advanced Search option in the Filtration Dialog. ![Selected Filter Criteria](/images/accessanalyzer/11.6/admin/navigate/datagridfunctionality15.webp) The selected filter criteria will appear at the top of the data grid. A red X appears in the filtration dialog, and the total rows value drops to the number of records that match the filter -criteria. Additional filter statements can be added for other columns by repeating the process to +criteria. You can add additional filter statements for other columns by repeating the process to build complex filters. The filtration dialog also provides other ways to filter and search the data set. See the [Filtration Dialog](#filtration-dialog) topic for additional information on this feature. -Filters can be cleared by clicking the red X in the filtration dialog (to clear all filter -statements), selecting All from the column’s drop-down menu (to clear filters one column at a time), -or by navigating to another place in the console (to clear all filter statements). However, the +You can clear filters by clicking the red X in the filtration dialog (to clear all filter +statements), selecting All from the column’s dropdown menu (to clear filters one column at a time), +or navigating to another place in the console (to clear all filter statements). However, the Recent Filters option in the filtration dialog provides a list of the most recent filters applied to the data set for users to quickly return to a filtered view. @@ -237,8 +237,8 @@ The filter options and logical operators are: - Add Condition - Add Group - Clear All -- Logical Operator – The logical operator (red text) beside the Filter button can be changed by - clicking on it to open a menu with: +- Logical Operator – Click the logical operator (red text) beside the Filter button to open a menu + with: - AND - OR - NOT AND @@ -248,12 +248,12 @@ The filter options and logical operators are: - Add Condition - Add Group - Remove Row -- Column Selection – The selected column (green text) can be changed by clicking on it to open a +- Column Selection – Click the selected column (green text) to open a menu with all available columns for the data grid. -- Comparison Operator – The comparison operator (dark red text) can be changed by clicking on it to +- Comparison Operator – Click the comparison operator (dark red text) to open a menu with: - equals - - does not equal + - doesn't equal - is less than - is less than or equal to - is greater than @@ -261,11 +261,11 @@ The filter options and logical operators are: - like - not like - is blank - - is not blank + - isn't blank - between - not between - in - not in -- Filter Criteria – The filter criteria (blue text) can be changed by clicking on it and typing in - the textbox that appears. The Custom Filter builder wildcards can also be used in the Set Filter +- Filter Criteria – Click the filter criteria (blue text) and type in + the textbox that appears. You can also use the Custom Filter builder wildcards in the Set Filter builder. diff --git a/docs/accessanalyzer/11.6/admin/navigate/overview.md b/docs/accessanalyzer/11.6/admin/navigate/overview.md index 56597d06f1..782f573774 100644 --- a/docs/accessanalyzer/11.6/admin/navigate/overview.md +++ b/docs/accessanalyzer/11.6/admin/navigate/overview.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Navigating the Console -There are several options that can be used to navigate the Enterprise Auditor Console. This section +Use several options to navigate the Enterprise Auditor Console. This section covers basic Enterprise Auditor Console navigation, including menu options, buttons, and the different panes through which users can access Enterprise Auditor’s various functions and options. @@ -18,15 +18,15 @@ The primary sections of the Enterprise Auditor Console are: Comprised of the Menu Bar and the Actions Bar - [Navigation Pane](/docs/accessanalyzer/11.6/admin/navigate/pane.md) – Navigate through all of Enterprise Auditor’s major functions using the Navigation Pane. - Selecting a node or sub-folder in the Navigation Pane will change what can be done in the Results + Selecting a node or sub-folder in the Navigation Pane will change what you can do in the Results Pane. - [Results Pane](/docs/accessanalyzer/11.6/admin/navigate/resultspane.md) - – Displays various interfaces based on what is selected in the Navigation Pane or Activities Pane + – Displays various interfaces based on what you select in the Navigation Pane or Activities Pane - [Activities Pane](/docs/accessanalyzer/11.6/admin/navigate/activitiespane.md) - – Displays a list of activities which can be conducted within the currently selected console + – Displays a list of activities that you can perform within the selected console section -Enterprise Auditor Data Grids also have specific navigation options that enable users to filter, +Enterprise Auditor Data Grids also have specific navigation options that let users filter, group, and search through data. See the [Data Grid Functionality](/docs/accessanalyzer/11.6/admin/navigate/datagrid.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/admin/navigate/pane.md b/docs/accessanalyzer/11.6/admin/navigate/pane.md index 397e36100d..168f91dbf8 100644 --- a/docs/accessanalyzer/11.6/admin/navigate/pane.md +++ b/docs/accessanalyzer/11.6/admin/navigate/pane.md @@ -37,14 +37,14 @@ The items in the Navigation Pane are: [Jobs Tree](/docs/accessanalyzer/11.6/admin/jobs/overview.md) topic for additional information. -The title above the Navigation Pane will change depending on what is selected. There are also +The title above the Navigation Pane will change depending on what you select. There are also several right-click or context menus available throughout the console. See the [Navigation Pane Right-click Menus](#navigation-pane-right-click-menus) topic for additional information. ## Navigation Pane Right-click Menus -There are several contextual right-click menus that are accessed by right-clicking on individual +You can access several contextual right-click menus by right-clicking on individual nodes or sub-nodes in the Navigation Pane. The different right-click menus are: - Host Management Right-click Menus @@ -60,7 +60,7 @@ topic for additional information on these actions. #### Discovery Node -The Discovery node right click-menu can be accessed in the Host Management node in the Navigation +You can access the Discovery node right-click menu in the Host Management node in the Navigation Pane. ![Discovery Node options](/images/accessanalyzer/11.6/admin/navigate/navigationpane1.webp) @@ -73,7 +73,7 @@ The Discovery node right-click menu options are: #### All Hosts Node -The All Hosts node right-click menu can be accessed in the Host Management node in the Navigation +You can access the All Hosts node right-click menu in the Host Management node in the Navigation Pane. ![All Hosts Node options](/images/accessanalyzer/11.6/admin/navigate/navigationpane2.webp) @@ -96,7 +96,7 @@ The All Hosts right-click menu options are: #### All Hosts > [Host List] Node -The All Hosts > [Host List] right-click menu can be accessed in the Host Management node in the +You can access the All Hosts > [Host List] right-click menu in the Host Management node in the Navigation Pane. ![Host List Node options](/images/accessanalyzer/11.6/admin/navigate/navigationpane3.webp) @@ -156,7 +156,7 @@ Menu items include: job. This option only applies to Role Based Access. See the [Role Based Access](/docs/accessanalyzer/11.6/admin/settings/access/rolebased/overview.md) for additional information. -- Enable/Disable Job(s) – Disables the selected job or job group and skips them during scan +- Enable/Disable Jobs – Disables the selected job or job group and skips them during scan execution. When a job group is disabled, all existing jobs within the job group are disabled. See the [Disable or Enable a Job](/docs/accessanalyzer/11.6/admin/jobs/job/disableenable.md) topic @@ -193,9 +193,9 @@ Menu items include: and/or the job log and SA_Debug log. - Save the ZIP file to a desired location, and optionally attach it to an email to [Netwrix Support](https://www.netwrix.com/support.html). - - Email option requires + - Email option requires you to configure [Notification](/docs/accessanalyzer/11.6/admin/settings/notification.md) - settings to be configured. + settings. - Create Job (Ctrl+Alt+A) – Creates a new job at the same location as the selected job group or job. See the [Create a New Job](/docs/accessanalyzer/11.6/admin/jobs/job/create.md) diff --git a/docs/accessanalyzer/11.6/admin/navigate/top.md b/docs/accessanalyzer/11.6/admin/navigate/top.md index 383fa595a6..9fe5381c36 100644 --- a/docs/accessanalyzer/11.6/admin/navigate/top.md +++ b/docs/accessanalyzer/11.6/admin/navigate/top.md @@ -168,4 +168,4 @@ The options in the Button Bar are: | ![paste](/images/accessanalyzer/11.6/admin/navigate/paste.webp) | Clipboard with paper | Paste the query from the clipboard (Ctrl + V) | | ![delete](/images/accessanalyzer/11.6/admin/navigate/delete.webp) | Red X | Delete the selected query | -Select a button for the desired action. +Select a button for the action you want. diff --git a/docs/accessanalyzer/11.6/admin/overview.md b/docs/accessanalyzer/11.6/admin/overview.md index a8e7d3de16..4d1183123e 100644 --- a/docs/accessanalyzer/11.6/admin/overview.md +++ b/docs/accessanalyzer/11.6/admin/overview.md @@ -6,7 +6,7 @@ sidebar_position: 40 # Administration -The Enterprise Auditor application is the power behind the solutions. It has the automation, +The Enterprise Auditor application powers the solutions. It has the automation, management, and integration building blocks that ensure the solutions’ advanced data collection and analysis deliver meaningful results to an organization’s infrastructure and other technologies. Users manage and control access to unstructured and structured data, systems, and critical @@ -14,7 +14,7 @@ applications with the application. ## Data Collectors Overview -Enterprise Auditor leverages a wide variety of APIs and protocols to connect to and communicate with +Enterprise Auditor uses a wide variety of APIs and protocols to connect to and communicate with the systems and applications in an organization’s environment. From MAPI to PowerShell, WMI, LDAP, CIFS, and more. It uses the best, most appropriate data collection methodology for every data collection task. The majority of Enterprise Auditor data comes from agentless scans and log @@ -23,8 +23,8 @@ application types. Though Enterprise Auditor does use applets and kernel-level drivers for certain data collection requirements, e.g. real-time file level activity monitoring, these agent-based advanced data -collection methods allow the kind of deep rich information, which can usually be obtained only by -substantial manual effort. +collection methods provide the kind of deep, rich information that otherwise requires substantial +manual effort to obtain. See the [Data Collectors](/docs/accessanalyzer/11.6/admin/datacollector/overview.md) @@ -32,9 +32,8 @@ topic for additional information. ## Analysis Modules Overview -Enterprise Auditor employs a series of powerful, yet easy-to-use Analysis Modules which provide -end-users with the ability to perform very simple and sophisticated data analysis routines with -ease: +Enterprise Auditor employs a series of powerful Analysis Modules which provide +end-users with the ability to perform both simple and sophisticated data analysis routines: - Correlation – Easily correlate data from multiple datasets to create meaningful views - Policy – Create rules and policies which automatically categorize your data output, i.e. Severity, @@ -66,12 +65,12 @@ topic for additional information. The Enterprise Auditor custom report authoring engine, dashboards, and open data views provide information to multiple audiences within an organization, both technical and non-technical. Its -reporting capabilities include a distribution and viewing mechanism allowing reports to be -automatically distributed via email or posted to one or more network locations and/or websites for +reporting capabilities include a distribution and viewing mechanism that automatically distributes +reports via email or posts them to one or more network locations and/or websites for simple, secure, and on-demand access to information. The Enterprise Auditor Report Index provides access to published Enterprise Auditor reports through a web-based console, granting access to -reports without requiring access to the Enterprise Auditor Console. It is accessed through the -Stealthbits Web Console, which is created during the installation of Enterprise Auditor. The Web +reports without requiring access to the Enterprise Auditor Console. Users access it through the +Stealthbits Web Console, created when they install Enterprise Auditor. The Web Console can also provide access to the Access Information Center, and other Stealthbits products. See the diff --git a/docs/accessanalyzer/11.6/admin/report/cleanup.md b/docs/accessanalyzer/11.6/admin/report/cleanup.md index cd249dbef1..d6a55dd9ba 100644 --- a/docs/accessanalyzer/11.6/admin/report/cleanup.md +++ b/docs/accessanalyzer/11.6/admin/report/cleanup.md @@ -6,18 +6,18 @@ sidebar_position: 70 # Report Cleanup when Deleting a Job or Job Group -When deleting a job or job group, the Delete Job and Delete Group wizards allow you to delete any -published reports contained in the jobs that are being deleted. Follow the steps to delete a job or -job group that contains published reports. +When deleting a job or job group, the Delete Job and Delete Group wizards let you delete any +published reports contained in the jobs you're deleting. To delete a job or +job group that contains published reports: :::warning -Deleted objects cannot be restored. +Deleted objects can't be restored. ::: ![Delete Group on right-click menu](/images/accessanalyzer/11.6/admin/report/jobstree.webp) -**Step 1 –** In the Jobs tree, right-click on the job or group that you want to delete and select +**Step 1 –** In the Jobs tree, right-click the job or group that you want to delete and select **Delete Job/Group**. ![Delete Group wizard page](/images/accessanalyzer/11.6/admin/report/deletegroup.webp) @@ -41,12 +41,12 @@ group or job. Click **Next** to proceed with the deletion. **Step 4 –** The Progress page shows you the status of the deletion process. When it has completed, click **Finish** to exit the wizard. -The job or job group and all of the selected published reports have been deleted. If you chose not -to delete any of the published reports contained in any of the deleted jobs, then those remaining -reports can still be viewed in the Web Console, even though the parent has been removed from the -Enterprise Auditor Console. +Enterprise Auditor deletes the job or job group and all of the selected published reports. If you +chose not to delete any of the published reports contained in any of the deleted jobs, then you can +still view those remaining reports in the Web Console, even though the parent no longer appears in +the Enterprise Auditor Console. ![Delete Published Reports page with a report from previous deletion](/images/accessanalyzer/11.6/admin/report/reportfrompreviousdeletion.webp) -The remaining published reports that weren't deleted are shown in the wizard if you are deleting the +The wizard shows the remaining published reports that weren't deleted if you delete the parent group of the previously deleted job or group. diff --git a/docs/accessanalyzer/11.6/admin/report/create.md b/docs/accessanalyzer/11.6/admin/report/create.md index 7c1dea1e3e..42c590c861 100644 --- a/docs/accessanalyzer/11.6/admin/report/create.md +++ b/docs/accessanalyzer/11.6/admin/report/create.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Creating a Report -Creating and customizing reports allows you to design outputs uniquely crafted to your requirements. +Creating and customizing reports lets you design outputs uniquely crafted to your requirements. Reports can vary by section order, sourced data, file format, and other elements within the reports configuration. @@ -16,8 +16,8 @@ You can add additional reports by the following methods: - [Copy an Existing Report](#copy-an-existing-report) :::note -It is important to consider whether a report should be added to an existing job, or a new -job created to generate the report. Contact [Netwrix Support](https://www.netwrix.com/support.html) +Consider whether to add a report to an existing job or create a new +job to generate the report. Contact [Netwrix Support](https://www.netwrix.com/support.html) for additional information on report outputs. ::: @@ -33,39 +33,39 @@ to create a new report. **Step 2 –** On the Reports page, click Create. -**Step 3 –** The Report Configuration wizard is automatically launched. Use the wizard to configure +**Step 3 –** The Report Configuration wizard launches automatically. Use the wizard to configure the new report as required, see the [Report Configuration Wizard](/docs/accessanalyzer/11.6/admin/report/wizard/overview.md) topic for instructions. Click **Finish** on the final page of the wizard to create the report. -The new report is added to the Reports table. +Enterprise Auditor adds the new report to the Reports table. ![Generate report](/images/accessanalyzer/11.6/admin/report/generate.webp) **Step 4 –** Click the vertical ellipsis menu next to the report and select Generate. -The report is now created. To access the new report, see the +Enterprise Auditor generates the report. To access the new report, see the [Viewing Generated Reports](/docs/accessanalyzer/11.6/admin/report/view.md) topic. ## Copy an Existing Report You can create a new report by copying an existing report and pasting it in a job’s Reports node. -You can then optionally customize the report as required. Follow the steps to create a copy of an -existing report. +You can then optionally customize the report as required. To create a copy of an +existing report: ![Copy Report](/images/accessanalyzer/11.6/admin/report/copy.webp) -**Step 1 –** Navigate to the Reports node where the desired report to copy is located. Click the +**Step 1 –** Navigate to the Reports node where the report you want to copy is located. Click the vertical ellipsis menu next to the report and select Copy. ![Paste Report](/images/accessanalyzer/11.6/admin/report/paste.webp) -**Step 2 –** Navigate to the Reports node in the desired destination for the new report. Click the +**Step 2 –** Navigate to the Reports node in the destination you want for the new report. Click the vertical ellipsis menu in the header row of the Reports table and select Paste. -The copy of the report is added to the Reports table. Reports that are copied maintain the same -configuration settings as the original report. +Enterprise Auditor adds the copy of the report to the Reports table. Copied reports maintain the +same configuration settings as the original report. :::note If the report copied to the job’s Reports node has the same name as an existing report, @@ -81,6 +81,6 @@ topic for instructions. **Step 4 –** Click the vertical ellipsis menu next to the report and select Generate. -The report is now created. To access the new report, see the +Enterprise Auditor generates the report. To access the new report, see the [Viewing Generated Reports](/docs/accessanalyzer/11.6/admin/report/view.md) topic. diff --git a/docs/accessanalyzer/11.6/admin/report/edit.md b/docs/accessanalyzer/11.6/admin/report/edit.md index 181c89cff2..3d8ceeec9f 100644 --- a/docs/accessanalyzer/11.6/admin/report/edit.md +++ b/docs/accessanalyzer/11.6/admin/report/edit.md @@ -6,14 +6,15 @@ sidebar_position: 20 # Editing Existing Reports -It is not recommended to edit existing reports unless there are changes to a job’s settings at the -global level, job group level, or job level. Changes to when data is collected, the types of data -collected, and the properties of collected data are not reflected in a report’s configuration. As a -result, generated reports could appear with blank fields or misleading information about the purpose -of the collected data, unless the report is modified to reflect the changes to the job's settings. +Avoid editing existing reports unless there are changes to a job’s settings at the +global level, job group level, or job level. Changes to when Enterprise Auditor collects data, the +types of data it collects, and the properties of that data don't appear in a report’s configuration. +As a result, generated reports could appear with blank fields or misleading information about the +purpose of the collected data, unless you modify the report to reflect the changes to the job's +settings. To modify a report, use the Report Configuration Wizard. -Follow the steps to modify an existing report. +To modify an existing report: **Step 1 –** Navigate to the Reports node that contains the report. @@ -26,10 +27,10 @@ Follow the steps to modify an existing report. topic for instructions. - You must go through all pages of the wizard, and click **Finish** on the final page to save your - changes. Skip any sections or pages that do not require changes to the existing configuration. You + changes. Skip any sections or pages that don't require changes to the existing configuration. You can click **Cancel** on any page to exit the wizard without saving your changes. -Your configuration updates have been saved. To view the updated report you need to first generate -the report or run it's associated job. See the +Enterprise Auditor saves your configuration updates. To view the updated report you need to first +generate the report or run it's associated job. See the [Viewing Generated Reports](/docs/accessanalyzer/11.6/admin/report/view.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/admin/report/interactivegrids/copyingcells.md b/docs/accessanalyzer/11.6/admin/report/interactivegrids/copyingcells.md index d07019b724..e08c042851 100644 --- a/docs/accessanalyzer/11.6/admin/report/interactivegrids/copyingcells.md +++ b/docs/accessanalyzer/11.6/admin/report/interactivegrids/copyingcells.md @@ -7,12 +7,12 @@ sidebar_position: 40 # Copying Cells Copying an individual cell within a generated report enables easier searching for information using -the AIC or other tools. The copy feature can only be used on interactive grids. Each cell listed -under a column can be selected and copied to the clipboard. +the Access Information Center (AIC) or other tools. You can only use the copy feature on interactive +grids. You can select and copy each cell listed under a column to the clipboard. ![Copy Cell Data](/images/accessanalyzer/11.6/admin/report/interactivegrids/copycell.webp) -To copy a cell, select the cell, then right-click on it and select **Copy Cell Data**. +To copy a cell, select the cell, then right-click it and select **Copy Cell Data**. :::note You may need to allow programmatic clipboard access for your browser the first time you diff --git a/docs/accessanalyzer/11.6/admin/report/interactivegrids/grouping.md b/docs/accessanalyzer/11.6/admin/report/interactivegrids/grouping.md index 0e407b6227..f3ded4769b 100644 --- a/docs/accessanalyzer/11.6/admin/report/interactivegrids/grouping.md +++ b/docs/accessanalyzer/11.6/admin/report/interactivegrids/grouping.md @@ -6,11 +6,11 @@ sidebar_position: 10 # Grouping Data -If grouping is enabled, the **Group by** field provides a drop-down list of categories by which the +If grouping is enabled, the **Group by** field provides a dropdown list of categories by which the data can be grouped. :::note -Grouping and filtering cannot be enabled at the same time. If grouping is enabled, the +Grouping and filtering can't be enabled at the same time. If grouping is enabled, the Filter icon is disabled in the report. ::: @@ -21,5 +21,5 @@ topic for additional information. ![Group by option](/images/accessanalyzer/11.6/admin/report/interactivegrids/groupby.webp) -The drop-down list to the right of the Group by field can be accessed by clicking the down arrow. -Click an item from the drop-down list to group the report by that category. +The dropdown list to the right of the Group by field can be accessed by clicking the down arrow. +Click an item from the dropdown list to group the report by that category. diff --git a/docs/accessanalyzer/11.6/admin/report/interactivegrids/overview.md b/docs/accessanalyzer/11.6/admin/report/interactivegrids/overview.md index de74522ea3..78fc8ecb37 100644 --- a/docs/accessanalyzer/11.6/admin/report/interactivegrids/overview.md +++ b/docs/accessanalyzer/11.6/admin/report/interactivegrids/overview.md @@ -6,8 +6,8 @@ sidebar_position: 60 # Interactive Grids -Interactive grids in the table section of a report provide the ability to interact with the data and -filter it as required. Interactive grids allow you to perform the following actions: +Interactive grids in the table section of a report let you interact with the data and +filter it as required. Use interactive grids to perform the following actions: - Group data - Search and filter data @@ -19,7 +19,7 @@ filter it as required. Interactive grids allow you to perform the following acti The toolbar in an interactive grid can display the following options: - Filter icon – Click this icon to activate searching and filter the data -- Group by – Provides a drop-down list of available categories to select for grouping. When grouping +- Group by – Provides a dropdown list of available categories to select for grouping. When grouping is enabled, searching is disabled. - Up arrow and down arrow – Click to expand or collapse the groups - Download Data – Click to download all data to a CSV file. This option is displayed when the @@ -27,8 +27,8 @@ The toolbar in an interactive grid can display the following options: [Grid](/docs/accessanalyzer/11.6/admin/report/wizard/widgets.md#grid) topic for additional information. -When enumeration is set on an interactive grid, a second download button is displayed. A CSV file -can be downloaded that contains only data for the selected enumeration. +When enumeration is set on an interactive grid, a second download button is displayed. You can +download a CSV file that contains only data for the selected enumeration. ![Group by loading data](/images/accessanalyzer/11.6/admin/report/interactivegrids/groupbyloadingdata.webp) diff --git a/docs/accessanalyzer/11.6/admin/report/interactivegrids/paging.md b/docs/accessanalyzer/11.6/admin/report/interactivegrids/paging.md index d1c4626b3f..4ae3b467fe 100644 --- a/docs/accessanalyzer/11.6/admin/report/interactivegrids/paging.md +++ b/docs/accessanalyzer/11.6/admin/report/interactivegrids/paging.md @@ -6,21 +6,21 @@ sidebar_position: 30 # Paging -Paging allows users to interact with large sets of data more efficiently when viewing, filtering, +Paging lets users interact with large sets of data more efficiently when viewing, filtering, and sorting generated report tables by limiting the amount of data being displayed at a given time. -Reports provide the ability to navigate to specific pages using arrows at the bottom of the report. +Reports let you navigate to specific pages using arrows at the bottom of the report. Paging is enabled by default. See the [Grid](/docs/accessanalyzer/11.6/admin/report/wizard/widgets.md#grid) topic for additional information. :::note -Paging and grouping cannot be enabled at the same time. When Paging is enabled, the +Paging and grouping can't be enabled at the same time. When Paging is enabled, the Grouping options are disabled for the report. ::: ![Paging](/images/accessanalyzer/11.6/admin/report/interactivegrids/paging.webp) -When paging is enabled, arrows are displayed that allow you to navigate to the next page, last page, +When paging is enabled, arrows are displayed that let you navigate to the next page, last page, previous page, or first page. If the data is filtered, it is indicated at the end of the line. Each page contains 10 records. diff --git a/docs/accessanalyzer/11.6/admin/report/interactivegrids/searchfilter.md b/docs/accessanalyzer/11.6/admin/report/interactivegrids/searchfilter.md index 6ff5da7c06..48c60bd5c4 100644 --- a/docs/accessanalyzer/11.6/admin/report/interactivegrids/searchfilter.md +++ b/docs/accessanalyzer/11.6/admin/report/interactivegrids/searchfilter.md @@ -6,11 +6,10 @@ sidebar_position: 20 # Searching and Filtering Data -When dealing with large sets of data, it may be useful to search for a desired attribute. This can -be done using the Filter icon. +When dealing with large sets of data, use the Filter icon to search for a desired attribute. :::note -Searching and grouping cannot be enabled at the same time. If grouping is enabled, the +Searching and grouping can't be enabled at the same time. If grouping is enabled, the Search icon is disabled in the report. ::: @@ -24,7 +23,7 @@ topic for additional information. Enter search criteria in the boxes under the columns to filter the data. Click the search icon again to clear the filters. -Click on a column to sort by that column. Clicking on a cell in a column automatically expands the +Click a column to sort by that column. Clicking on a cell in a column automatically expands the column size to fit the largest length of text contained in the column. ## Searching Enumerated Tables @@ -36,22 +35,21 @@ types to display as enumerated tables. To change the enumeration in the report, select an option from the enumerated column list. When enumeration is set on an interactive grid, a second download button is displayed with the name of -the currently selected enumerated column. You can use this to download a CSV file that only contains +the selected enumerated column. You can use this to download a CSV file that only contains the data for the selected enumeration. ## Filtering on Dates & Times -Data can also be filtered on dates and times. Expanding the column’s width activates hyperlinks to +You can also filter data on dates and times. Expanding the column’s width activates hyperlinks to filter on specific time periods. ![Date column filter](/images/accessanalyzer/11.6/admin/report/interactivegrids/datefilter.webp) -Enter a Start and End date and select the desired time period. +Enter a Start and End date and select the time period you want. ## Filtering on Numeric Columns -Comparison operators can also be used for filtering. Comparison operators which can be used for -filtering include the following: +Use comparison operators to filter numeric columns. Available comparison operators include the following: | Description | Operator | | ------------------------ | -------- | @@ -64,9 +62,9 @@ filtering include the following: ## Adding & Removing Columns -Columns can be added or removed from the table. +You can add or remove columns from the table. ![Add and remove columns](/images/accessanalyzer/11.6/admin/report/interactivegrids/addremovecolumns.webp) -Right-click on a column to display a list of the available columns. Select the checkboxes of the -columns you want to be displayed. Click the up or down arrows to scroll through the list of columns. +Right-click a column to display a list of the available columns. Select the checkboxes of the +columns you want to display. Click the up or down arrows to scroll through the list of columns. diff --git a/docs/accessanalyzer/11.6/admin/report/overview.md b/docs/accessanalyzer/11.6/admin/report/overview.md index 96f1bd91bc..7b69145246 100644 --- a/docs/accessanalyzer/11.6/admin/report/overview.md +++ b/docs/accessanalyzer/11.6/admin/report/overview.md @@ -6,7 +6,7 @@ sidebar_position: 110 # Reporting -Enterprise Auditor provides the ability to report on collected data in multiple ways such as tables, +Enterprise Auditor lets you report on collected data in multiple ways such as tables, views, graphs, and emails. Depending on the type of data collected, different reporting methods can simplify how to present and understand the information. @@ -15,17 +15,17 @@ simplify how to present and understand the information. The Reports node, contained within a job’s Configure node, lists any reports that are configured for the job. The page contains options to create a report, configure existing reports, and a link to view generated reports. The configuration of reports vary by use case, but they contain the same -elements. The layout and elements of a report are configured using the +elements. You configure the layout and elements of a report using the [Report Configuration Wizard](/docs/accessanalyzer/11.6/admin/report/wizard/overview.md). -In addition, there are various ways to view and interact with generated reports. Generated reports -can be viewed in the Enterprise Auditor Console or in the Web Console. Reports can also be +In addition, there are various ways to view and interact with generated reports. You can view +generated reports in the Enterprise Auditor Console or in the Web Console. Reports can also be configured to be downloaded as a CSV file, or sent as an email in various forms. See the [Viewing Generated Reports](/docs/accessanalyzer/11.6/admin/report/view.md) topic for additional information. -The global settings configured under the Settings node are inherited down through the Jobs tree to -the job unless inheritance is broken in a job group’s Settings node, a job’s Properties window, or +The global settings configured under the Settings node inherit down through the Jobs tree to +the job unless you break inheritance in a job group’s Settings node, a job’s Properties window, or in the Report Configuration Wizard. See the [Reporting](/docs/accessanalyzer/11.6/admin/settings/reporting.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/admin/report/tags.md b/docs/accessanalyzer/11.6/admin/report/tags.md index 6f61efafe5..857d4aa0b6 100644 --- a/docs/accessanalyzer/11.6/admin/report/tags.md +++ b/docs/accessanalyzer/11.6/admin/report/tags.md @@ -6,38 +6,38 @@ sidebar_position: 50 # Tags -Tags can be added to reports to describe the content of the report and use cases for the report. For -example, tags can be included in a report to show the compliance frameworks to which the report -maps. To view tags or click on tag links, reports must be viewed in the Web Console. Tags are not +You can add tags to reports to describe the content of the report and use cases for the report. For +example, you can include tags in a report to show the compliance frameworks to which the report +maps. To view tags or click tag links, you must view reports in the Web Console. Tags aren't supported in reports in the Jobs tree. ![Web Console Home Page](/images/accessanalyzer/11.6/admin/report/webconsolehome.webp) -If Reports from solutions that have been run have tags added to them, those tags can be found under +If reports from solutions you've run have tags, you can find those tags under the Tags tab in the Navigation section on the right-hand side of the Published Reports homepage. | ![Tags tab on Web Console homepage](/images/accessanalyzer/11.6/admin/report/tagstab.webp) | ![Priviliged Accounts tag page](/images/accessanalyzer/11.6/admin/report/privilegedaccountstag.webp) | | -------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | | Privileged Accounts Tag on Published Reports homepage | Privileged Accounts Tag page | -Click on a tag to view all reports that contain the selected tag. +Click a tag to view all reports that contain the selected tag. ![Job Group view in the Web Console](/images/accessanalyzer/11.6/admin/report/jobgroupview.webp) Clicking on a job group in the Published Reports menu displays the reports contained in that job -group. Jobs within that job group that have tags are identified with a tag icon along with the tag +group. Jobs within that job group that have tags show a tag icon along with the tag name. ![Report header](/images/accessanalyzer/11.6/admin/report/reportheader.webp) When viewing a report in either the Web Console or the Enterprise Auditor console, tags are -displayed below the report title. Click on a tag to view all reports that contain that tag. If the -tag is selected from the Reports view in the Enterprise Auditor Console, the Published Reports Web +displayed below the report title. Click a tag to view all reports that contain that tag. If you select the +tag from the Reports view in the Enterprise Auditor Console, the Published Reports Web Console opens and direct users to the tag page. ## Default Tags in Reports -The following sections list out of the box reports that contain each tag. The tags are: +The following sections list the default reports that contain each tag. The tags are: ### Open Access diff --git a/docs/accessanalyzer/11.6/admin/report/view.md b/docs/accessanalyzer/11.6/admin/report/view.md index a7302c8ddb..9c6d303194 100644 --- a/docs/accessanalyzer/11.6/admin/report/view.md +++ b/docs/accessanalyzer/11.6/admin/report/view.md @@ -6,8 +6,8 @@ sidebar_position: 40 # Viewing Generated Reports -Reports can be viewed either in the Enterprise Auditor Console in the Results Node of the related -job, or published reports can be viewed in the Web Console. +You can view reports either in the Enterprise Auditor Console in the Results Node of the related +job, or view published reports in the Web Console. - [Results Node](#results-node) – All reports generated by a job are always accessible under the job’s Results node @@ -16,12 +16,12 @@ job, or published reports can be viewed in the Web Console. ## Results Node -Each job contains a results node where reports generated by that job can be viewed. Even if the +Each job contains a results node where you can view reports generated by that job. Even if the report is unpublished, the report is still displayed here. ![Report in the Results node](/images/accessanalyzer/11.6/admin/report/viewresultsnode.webp) -Select the desired report to be viewed. The report displays in the Results pane of the console. +Select the report you want to view. The report displays in the Results pane of the console. ![Access report from configure page](/images/accessanalyzer/11.6/admin/report/viewconfigure.webp) @@ -45,7 +45,7 @@ that solution’s job group. This list includes reports with changed Publish Pat Clicking a report name link opens the selected report, or navigate through the folders to select a report. -From within the Web Console, reports cannot be edited or deleted. However, the interactive grid +From within the Web Console, you can't edit or delete reports. However, the interactive grid functions are enabled. See the [Interactive Grids](/docs/accessanalyzer/11.6/admin/report/interactivegrids/overview.md) topic for additional information. An additional feature available within the Web Console is the diff --git a/docs/accessanalyzer/11.6/admin/report/wizard/authoring.md b/docs/accessanalyzer/11.6/admin/report/wizard/authoring.md index a1e5b2393e..180fba4d0e 100644 --- a/docs/accessanalyzer/11.6/admin/report/wizard/authoring.md +++ b/docs/accessanalyzer/11.6/admin/report/wizard/authoring.md @@ -25,7 +25,7 @@ Configure the following settings as required: - Author – Name of the person or group who created the report. This is displayed at the top of the generated report. - Tags – Use the tag editor to add and remove tags, see the - [Add Tags to a Report](#add-tags-to-a-report) topic below for more information. Tags are displayed + [Add Tags to a Report](#add-tags-to-a-report) topic for more information. Tags are displayed in the header of the generated reported. - Description – A description of the report content. It is displayed beneath the report Title in the generated report. @@ -42,7 +42,7 @@ Configure the following settings as required: [Report Settings Tab](/docs/accessanalyzer/11.6/admin/jobs/job/properties/reportsettings.md) topics for additional information.) - Publish report – Select this option to publish the report - - Do not publish report – Select this option to not publish the report + - Don't publish report – Select this option to not publish the report - Publish State – Shows the current publish state of the report. If the report is already published, you can click the link to open the report in the Web Console. @@ -50,22 +50,22 @@ Configure the following settings as required: You can add tags to reports to describe the content and use cases of the report (see the [Tags](/docs/accessanalyzer/11.6/admin/report/tags.md) topic for -additional information). The Tag Editor allows you to select the tags for a report, including +additional information). Use the Tag Editor to select the tags for a report, including creating new ones to select. -Follow the steps to select tags using the Tag Editor. +To select tags using the Tag Editor: **Step 1 –** On the Authoring page of the Report Configuration wizard, click the **Edit** button located next to the Tags text box. ![Tag Editor](/images/accessanalyzer/11.6/admin/report/wizard/tageditor.webp) -**Step 2 –** In the Tag editor, select the checkbox next to the tags that should be applied to the +**Step 2 –** In the Tag editor, select the checkbox next to the tags you want to apply to the report. -- In addition to selecting existing tags, you can also add new tags to be selected. To create a tag, - enter the desired tag name in the text box and click **Add**. +- In addition to selecting existing tags, you can also add new tags to select. To create a tag, + enter the tag name you want in the text box and click **Add**. **Step 3 –** Click **OK**. -The selected tags are now shown in the Tags field as a comma separated list. +The Tags field now shows the selected tags as a comma separated list. diff --git a/docs/accessanalyzer/11.6/admin/report/wizard/email.md b/docs/accessanalyzer/11.6/admin/report/wizard/email.md index 76b9b10f20..9a42f91c29 100644 --- a/docs/accessanalyzer/11.6/admin/report/wizard/email.md +++ b/docs/accessanalyzer/11.6/admin/report/wizard/email.md @@ -21,14 +21,14 @@ topics for additional information). If you want to keep the default, then you ca the wizard by clicking **Next**. :::note -In order for reports to be emailed, the SMTP server information must be configured in the +To email reports, configure the SMTP server information in the **Settings** > **Notification** node. See the [Notification](/docs/accessanalyzer/11.6/admin/settings/notification.md) topic for additional information. ::: -To configure the setting for the report, use the Settings drop-down menu to select one of the +To configure the setting for the report, use the Settings dropdown menu to select one of the following options: - Use default setting – The default option. Applies the Global notification settings, or whatever @@ -36,9 +36,9 @@ following options: **Email this report** is enabled by default, then using this option sends the report to the recipients configured at the parent level where the inheritance begins. - Email this report – Select this option if you want to email the report and the inherited setting - is **Do not email this report**, or if you want to configure specific email settings for the + is **Don't email this report**, or if you want to configure specific email settings for the report. If it is selected, you must then configure the additional fields below. -- Do not email this report – Select this option to not email the report +- Don't email this report – Select this option to not email the report ![Settings configured to email the report](/images/accessanalyzer/11.6/admin/report/wizard/emailconfigured.webp) @@ -57,7 +57,7 @@ configure: automatically populated. - Send-To / Send-Cc / Send-Bcc – Enter the email addresses of the required recipients for the email notification. Use a semicolon (;) to separate multiple recipients. -- Do not e-mail this report if blank – Select this checkbox to not email the report if all elements +- Don't e-mail this report if blank – Select this checkbox to not email the report if all elements of it are blank when it is generated - A blank report can occur if there is an error in data collection or if the report is configured for data which might not always be present (for example, new computer objects diff --git a/docs/accessanalyzer/11.6/admin/report/wizard/layout.md b/docs/accessanalyzer/11.6/admin/report/wizard/layout.md index 0de8ee2e94..a85dd4d4cc 100644 --- a/docs/accessanalyzer/11.6/admin/report/wizard/layout.md +++ b/docs/accessanalyzer/11.6/admin/report/wizard/layout.md @@ -6,18 +6,18 @@ sidebar_position: 40 # Layout Page -The Layout page allows you to configure the layout of the report's content. +Use the Layout page to configure the layout of the report's content. ![layout](/images/accessanalyzer/11.6/admin/report/wizard/layout.webp) -Follow the steps to select the layout: +To select the layout: -**Step 1 –** Click the **Select the number of rows** drop-down menu and select an option from: 1 +**Step 1 –** Click the **Select the number of rows** dropdown menu and select an option from: 1 row, 2 rows, or 3 rows. -**Step 2 –** Click on the layout tile you want for the report. +**Step 2 –** Click the layout tile you want for the report. -The layout for the report has been selected. Each box on the selected tile corresponds to a separate +You've selected the layout for the report. Each box on the selected tile corresponds to a separate widget that you next need to configure on the [Widgets Page](/docs/accessanalyzer/11.6/admin/report/wizard/widgets.md) page of the Report Configuration wizard. @@ -29,9 +29,10 @@ number of already configured widgets, then the Element Downgrade Editor automati ![Element Downgrade Editor](/images/accessanalyzer/11.6/admin/report/wizard/elementdowngradeeditor.webp) -The maximum number of elements allowed by the correctly selected layout is specified at the top of -the editor. Select the checkboxes next to the title of all the configured widgets you want to keep -up to this limit, then click **OK**. Any widgets not selected will be removed from the report. +The top of the editor specifies the maximum number of elements allowed by the correctly selected +layout. Select the checkboxes next to the title of all the configured widgets you want to keep +up to this limit, then click **OK**. Enterprise Auditor removes any widgets you don't select from +the report. :::note You can click **Cancel** to return to the layout page to select a different layout with diff --git a/docs/accessanalyzer/11.6/admin/report/wizard/overview.md b/docs/accessanalyzer/11.6/admin/report/wizard/overview.md index 58f219e24f..5f4d7de91f 100644 --- a/docs/accessanalyzer/11.6/admin/report/wizard/overview.md +++ b/docs/accessanalyzer/11.6/admin/report/wizard/overview.md @@ -6,17 +6,17 @@ sidebar_position: 30 # Report Configuration Wizard -You can use the Report Configuration Wizard to configure reports. The wizard can be launched for an +You can use the Report Configuration Wizard to configure reports. You can launch the wizard for an existing report or when creating a new report. See the [Creating a Report](/docs/accessanalyzer/11.6/admin/report/create.md) and [Editing Existing Reports](/docs/accessanalyzer/11.6/admin/report/edit.md) topics for additional information. -Follow the steps to configure a report using the wizard. +To configure a report using the wizard: :::note -Skip any sections or pages that do not require changes to the existing configuration. +Skip any sections or pages that don't require changes to the existing configuration. ::: @@ -33,12 +33,12 @@ page, use the inherited settings or configure report specific settings. Click ** **Step 4 –** The [Publish Security Page](/docs/accessanalyzer/11.6/admin/report/wizard/publishsecurity.md) page is only enabled if role-based access is configured for the Enterprise Auditor console. On this -page you can view and configure accounts with permissions to view the report. If you are not using +page you can view and configure accounts with permissions to view the report. If you aren't using role-based access, you can skip this page. Click **Next**. **Step 5 –** On the [Layout Page](/docs/accessanalyzer/11.6/admin/report/wizard/layout.md) -page, select the number of rows using the dropdown menu. Then select the desired pre-defined layout +page, select the number of rows using the dropdown menu. Then select the pre-defined layout you want from the options displayed. Click **Next**. **Step 6 –** On the @@ -47,9 +47,9 @@ page, configure widgets for each element of the layout. **Step 7 –** Click **Finish** to save your changes. -- If you do not want to save your changes or have not made any changes, click **Cancel** on any page +- If you don't want to save your changes or have not made any changes, click **Cancel** on any page to exit the wizard without saving your changes. -Your configuration has been saved. For information on how to view your report, see the +Enterprise Auditor has saved your configuration. For information on how to view your report, see the [Viewing Generated Reports](/docs/accessanalyzer/11.6/admin/report/view.md) topic. diff --git a/docs/accessanalyzer/11.6/admin/report/wizard/publishsecurity.md b/docs/accessanalyzer/11.6/admin/report/wizard/publishsecurity.md index 188b43be04..dd7522f901 100644 --- a/docs/accessanalyzer/11.6/admin/report/wizard/publishsecurity.md +++ b/docs/accessanalyzer/11.6/admin/report/wizard/publishsecurity.md @@ -19,8 +19,8 @@ topic for additional information. ![Publish Security page](/images/accessanalyzer/11.6/admin/report/wizard/publishsecurity.webp) -Roles assigned at the global level are inherited down to the report configuration. Additional report -viewer privileges can also be added at the job group or job levels. +Roles assigned at the global level inherit down to the report configuration. You can also add +additional report viewer privileges at the job group or job levels. De-select the Include Report Reviewers from this object's parent checkbox to remove all inherited accounts with the Report Viewer role. @@ -33,15 +33,15 @@ steps to add an account. ![Select User, Service Account, or Group window](/images/accessanalyzer/11.6/admin/report/wizard/addreportviewer.webp) -**Step 2 –** On the Select User, Service Account or Group window, select the desired account and +**Step 2 –** On the Select User, Service Account or Group window, select the account you want and then click **OK**. ![Report Viewer user added in wizard](/images/accessanalyzer/11.6/admin/report/wizard/reportviewer.webp) -The selected account is added to the list with a Role of Report Viewer. +Enterprise Auditor adds the selected account to the list with a Role of Report Viewer. :::note -The permission for accounts that are not Inherited can also be removed using the wizard. +You can also remove the permission for accounts that aren't Inherited using the wizard. To remove an account, select it and then click **Remove**. ::: diff --git a/docs/accessanalyzer/11.6/admin/report/wizard/widgets.md b/docs/accessanalyzer/11.6/admin/report/wizard/widgets.md index 2f76aebf33..fc84734283 100644 --- a/docs/accessanalyzer/11.6/admin/report/wizard/widgets.md +++ b/docs/accessanalyzer/11.6/admin/report/wizard/widgets.md @@ -11,12 +11,12 @@ text that form the report. ![Widgets page](/images/accessanalyzer/11.6/admin/report/wizard/widgets.webp) -At the top of the page the selected layout is described. The table contains the available element -locations where widgets need to be configured. +The top of the page describes the selected layout. The table contains the available element +locations where you need to configure widgets. ![Configure widgets](/images/accessanalyzer/11.6/admin/report/wizard/widgetsconfigure.webp) -To add a new widget to an empty element, click **Configure** and select the desired widget type from +To add a new widget to an empty element, click **Configure** and select the widget type you want from the dropdown menu. The following widgets are available: - [Grid](#grid) @@ -38,7 +38,7 @@ following actions by selecting a row and clicking the relevant button: ## Grid -Use the Grid widget type to configure a table to be displayed on generated reports. +Use the Grid widget type to configure a table for generated reports. ![Grid configuration window](/images/accessanalyzer/11.6/admin/report/wizard/widgetgrid.webp) @@ -74,7 +74,7 @@ To generate results, select a location as the data source. **Export CSV Options** -You can configure the table to allow the data to be exported as a CSV file. +You can configure the table to allow exporting the data as a CSV file. - Export table data as CSV – Select this option to enable a report’s table section to be exportable as a CSV file from the generated report @@ -83,7 +83,7 @@ You can configure the table to allow the data to be exported as a CSV file. [Interactive Grids](/docs/accessanalyzer/11.6/admin/report/interactivegrids/overview.md) topic for details about interactive grids. :::warning - Only interactive grids can be exported. Non-interactive grids display an "EOIeError" pop-up when you attempt to export a non-interactive grid as CSV. + You can only export interactive grids. Non-interactive grids display an "EOIeError" pop-up when you attempt to export a non-interactive grid as CSV. ::: - Rows – Limits the amount of rows exported to the CSV file. The default is **Visible**. - Visible – Only includes the amount of rows set by the **Limit Maximum number of displayed rows @@ -142,8 +142,8 @@ The following settings are available when Interactive grid is selected: ### Data -The selected data for the table is shown in the section at the bottom of the window. Use this section -to configure the data to be displayed in the table. +The section at the bottom of the window shows the selected data for the table. Use this section +to configure the data to display in the table. ![Data display](/images/accessanalyzer/11.6/admin/report/wizard/widgetgriddata.webp) @@ -212,7 +212,7 @@ The following options are the available in the Chart Properties: - Stacked – Consolidated bar chart for comparing values :::note - Negative numbers can't be plotted. + You can't plot negative numbers. ::: @@ -220,7 +220,7 @@ The following options are the available in the Chart Properties: - Enum Column – Groups the data in chart by the selected column name - Assign color for pie slice – Available only for pie charts. Use this option to customize the color for each slice. Select the column header name from the dropdown menu, then use the color selector - window to choose the desired color. + window to choose the color you want. ### Link @@ -233,8 +233,8 @@ report to link to and click **Ok**. ### Data -The table of data for the chart is displayed in the middle of the window. Use this table to -customize the data to be shown in the chart. +The middle of the window displays the table of data for the chart. Use this table to +customize the data to show in the chart. ![Data table](/images/accessanalyzer/11.6/admin/report/wizard/widgetchartdata.webp) @@ -274,7 +274,7 @@ Text Editor. On this dialog, select either the Basic or Advanced Text Editor and Editor**. The selected editor then opens. :::note -Once a Text Editor is selected for a Text element, it can't be changed. +Once you select a Text Editor for a Text element, you can't change it. ::: diff --git a/docs/accessanalyzer/11.6/admin/runninginstances/jobdetails.md b/docs/accessanalyzer/11.6/admin/runninginstances/jobdetails.md index baa41cb257..9de54db7ff 100644 --- a/docs/accessanalyzer/11.6/admin/runninginstances/jobdetails.md +++ b/docs/accessanalyzer/11.6/admin/runninginstances/jobdetails.md @@ -38,7 +38,7 @@ The tab includes: - Status – Execution status, for example **Queued**, **Running**, **Success**, or **Warning**. - Message – Enterprise Auditor message regarding runtime activity - Runtime – Duration of task execution -- Stop – Aborts all currently running instances +- Stop – Aborts all running instances ## History Tab @@ -74,13 +74,14 @@ topic for additional information. ## Queued Jobs Tab -The Queued Jobs tab displays a list of jobs in queue and the order in which they are executed. +The Queued Jobs tab displays a list of jobs in queue and the order in which Enterprise Auditor +executes them. ![Queued Jobs tab](/images/accessanalyzer/11.6/admin/runninginstances/jobdetailsqueuedjobs.webp) The tab includes: -- Order – Order in which the queued jobs are executed. This order can be changed on the Queued Jobs +- Order – Order in which the queued jobs are executed. You can change this order on the Queued Jobs tab by using the buttons at the bottom. - Job Path – Folder path in Jobs directory - State – Queue status, for example **Running** or  **Waiting** diff --git a/docs/accessanalyzer/11.6/admin/runninginstances/overview.md b/docs/accessanalyzer/11.6/admin/runninginstances/overview.md index c7c9524e0d..ce8f1c3091 100644 --- a/docs/accessanalyzer/11.6/admin/runninginstances/overview.md +++ b/docs/accessanalyzer/11.6/admin/runninginstances/overview.md @@ -6,8 +6,8 @@ sidebar_position: 50 # Running Instances Node -The Running Instances node displays progress for all running jobs. This includes jobs that are run -by a scheduled task, interactively within the open Enterprise Auditor instance, or interactively in +The Running Instances node displays progress for all running jobs. This includes jobs that run +via a scheduled task, interactively within the open Enterprise Auditor instance, or interactively in any other running instance of Enterprise Auditor. The Running Instances node displays the instance name, its status and position in the queue, run times for all instances, and detailed views of each instance. @@ -43,13 +43,13 @@ It also has hyperlinks for: Clicking on any of the hyperlinks displays more information about the running job. The **ProcessID**, **View Details, View Log**, and **Stop** links only work while the job is running. -Once the job is complete, these links are disabled. The host and Connection Profile links continue +After the job is complete, these links are disabled. The host and Connection Profile links continue to work. The **View Schedule** link only displays and is valid for jobs that are running via a -scheduled task and is not enabled for interactive job executions. +scheduled task and isn't enabled for interactive job executions. ![Number of jobs running on bottom bar](/images/accessanalyzer/11.6/admin/runninginstances/overviewbottombar.webp) -The number of jobs currently being run can be found in the lower-left-hand corner of the Enterprise +You can find the number of jobs being run in the lower-left-hand corner of the Enterprise Auditor Console. ## View Host @@ -98,7 +98,7 @@ topic for additional information. ## View Log -The log for this running job can be opened in a text editor, such as Notepad. +You can open the log for this running job in a text editor, such as Notepad. ![View Log link](/images/accessanalyzer/11.6/admin/runninginstances/viewlog.webp) @@ -129,7 +129,7 @@ for additional information. ## Stop -The job execution can be stopped if needed. +You can stop the job execution if needed. ![Stop button](/images/accessanalyzer/11.6/admin/runninginstances/stop.webp) diff --git a/docs/accessanalyzer/11.6/admin/schedule/overview.md b/docs/accessanalyzer/11.6/admin/schedule/overview.md index bf4bad66f7..92e3e384df 100644 --- a/docs/accessanalyzer/11.6/admin/schedule/overview.md +++ b/docs/accessanalyzer/11.6/admin/schedule/overview.md @@ -11,7 +11,7 @@ Account, the Enterprise Auditor application can run multiple tasks simultaneousl [Schedule](/docs/accessanalyzer/11.6/admin/settings/schedule.md) topic for information on configuring the Schedule Service Account. -The following tasks can be scheduled: +You can schedule the following tasks: - Job or Job Group – Schedule jobs to run at the job or job group level. See the [Schedule Jobs](#schedule-jobs) topic for additional information. @@ -25,11 +25,11 @@ The following tasks can be scheduled: ## Schedule Jobs -Jobs can be scheduled at the job group or job level. +You can schedule jobs at the job group or job level. ![Schedule option from Job Tree](/images/accessanalyzer/11.6/admin/schedule/jobtree.webp) -Select the desired job group or job. Right-click on the node and select **Schedule** to open the +Select the job group or job you want. Right-click the node and select **Schedule** to open the Schedule wizard. ![Schedule Job wizard](/images/accessanalyzer/11.6/admin/schedule/schedule.webp) diff --git a/docs/accessanalyzer/11.6/admin/schedule/wizard.md b/docs/accessanalyzer/11.6/admin/schedule/wizard.md index 87cc0e0e88..b28735f84e 100644 --- a/docs/accessanalyzer/11.6/admin/schedule/wizard.md +++ b/docs/accessanalyzer/11.6/admin/schedule/wizard.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Schedule Wizard -The schedule wizard allows you to configure scheduled tasks for jobs, job groups, Host Discovery +Use the schedule wizard to configure scheduled tasks for jobs, job groups, Host Discovery queries, and Host Inventory queries. The wizard has five wizard pages with options for setting up the schedule task: @@ -17,16 +17,16 @@ the schedule task: - [Options](#options) On the Schedule page, click **New** to schedule when the task will run. The Host List and Connection -pages are optional customizations. See the relevant section below for more information on the +pages are optional customizations. See the relevant section for more information on the settings on each wizard page. -When the settings on the wizard pages are configured as desired, click **OK** to save the changes +When you've configured the settings on the wizard pages as desired, click **OK** to save the changes and close the window. The task is visible in the Schedule Actions view, at the Schedules node. ## Schedule -The Schedule page is for setting the schedule of when and how often the task will run. This tab -needs to be properly configured for every scheduled task. +The Schedule page is for setting the schedule of when and how often the task will run. You need to +properly configure this tab for every scheduled task. ![Schedule wizard page](/images/accessanalyzer/11.6/admin/schedule/schedule.webp) @@ -54,11 +54,11 @@ The options in the Trigger window are: Days [value] of the month or the [value] [Day of the Week] of the month. By default, this is set to recur every month. To select only specific months, use Months dropdown menu and deselect the undesired months. - - The drop-down menu next to **Start** opens a calendar view for selecting the date + - The dropdown menu next to **Start** opens a calendar view for selecting the date - Selecting the **Synchronize across time zones** checkbox will synchronize the scheduled task to run without respect to the time zone -The remaining schedule frequencies are supplied by Windows Task Scheduler and not applicable to +Windows Task Scheduler supplies the remaining schedule frequencies, which aren't applicable to Enterprise Auditor task scheduling. See the Microsoft [Task Scheduler Overview](https://technet.microsoft.com/en-us/library/cc721871.aspx) article for additional information. @@ -78,24 +78,24 @@ configuration of this tab is optional. ![Host List wizard page](/images/accessanalyzer/11.6/admin/schedule/hostlist.webp) -Choose the desired setting from the following options: +Choose the setting you want from the following options: - Use Host list from Job – A default setting and applies the host list designated at the job or job group level. This is also the recommended setting. - Use Alternate Host List – Allows a host list to be selected from the list of Hosts Lists provided. The list is from the Host Management host lists. -Under the selection window, the number of selected hosts are identified. In addition, the **Select +Under the selection window, the number of selected hosts appears. In addition, the **Select All** and **Clear All** links provide for quick selection and deselection. ## Connection -The Connection page identifies the Connection Profile that is applied to the targeted hosts being +The Connection page identifies the Connection Profile applied to the targeted hosts being queried by the task being scheduled. Customizations to the configuration of this tab is optional. ![Connection wizard page](/images/accessanalyzer/11.6/admin/schedule/connection.webp) -Choose the desired setting from the following options: +Choose the setting you want from the following options: - Use Profile from Job – A default setting and applies the Connection Profile designated at the job or job group level @@ -124,7 +124,7 @@ The options on the Run as wizard page are: - Use default Schedule Service Account – Uses the default Schedule Service Account that is set at the **Settings** > **Schedule** node - Use selected Schedule Service Account – Select the Schedule Service Account to use for the task - from a list of available accounts in the drop-down menu + from a list of available accounts in the dropdown menu - Use Custom Credentials – Use custom credentials not stored in the Enterprise Auditor Console. Enter the User Name for the custom credentials. diff --git a/docs/accessanalyzer/11.6/admin/schema/fsaadc/views/overview.md b/docs/accessanalyzer/11.6/admin/schema/fsaadc/views/overview.md index 63efdbc8f3..c2c749a154 100644 --- a/docs/accessanalyzer/11.6/admin/schema/fsaadc/views/overview.md +++ b/docs/accessanalyzer/11.6/admin/schema/fsaadc/views/overview.md @@ -3,7 +3,7 @@ FSAA, FSAC, and FSDLP views provide pre-joined, human-readable projections of the underlying tables. Reports and the FSAA web UI consume these views rather than the raw tables. :::note -For views, column sizes are derived from the underlying source columns and the SQL `CASE` expressions in the view definitions; on a populated database the actual `sys.columns.max_length` may differ slightly. Use `EXEC sp_help ''` to inspect a view's exact runtime shape. +The underlying source columns and the SQL `CASE` expressions in the view definitions determine column sizes for views; on a populated database the actual `sys.columns.max_length` may differ slightly. Use `EXEC sp_help ''` to inspect a view's exact runtime shape. ::: --- @@ -549,7 +549,7 @@ For views, column sizes are derived from the underlying source columns and the S **Description:** Surface view over `SA_FSAC_PermissionChanges` that resolves the affected trustee and decodes the ACL / ACE / inheritance / access-rights bitmasks into descriptive strings. :::note -This view doesn't join `SA_FSAC_ActivityEvents` or `SA_FSAA_Resources` — the access time and resource path aren't exposed; reports needing them must join `SA_FSAC_ActivityEvents` themselves. +This view doesn't join `SA_FSAC_ActivityEvents` or `SA_FSAA_Resources`, so it doesn't expose the access time or resource path; reports needing them must join `SA_FSAC_ActivityEvents` themselves. ::: **Source tables:** `SA_FSAC_PermissionChanges`, `SA_FSAA_Hosts`, UDF `SA_FSAA_GetTrusteeInformation`. diff --git a/docs/accessanalyzer/11.6/admin/schema/sqldc/coretables/overview.md b/docs/accessanalyzer/11.6/admin/schema/sqldc/coretables/overview.md index f0ffba48f0..02edc15bb3 100644 --- a/docs/accessanalyzer/11.6/admin/schema/sqldc/coretables/overview.md +++ b/docs/accessanalyzer/11.6/admin/schema/sqldc/coretables/overview.md @@ -49,7 +49,7 @@ |---|---|---|---|---|---|---|---| | id | int | | No | PK | | IDENTITY | Surrogate primary key | | instance_id | int | | No | | | | Reference to the hosting SQL Server instance | -| active_database_id | int | | Yes | | FK | | FK to `SA_SQLServer_Databases.id`; links to the currently active database record | +| active_database_id | int | | Yes | | FK | | FK to `SA_SQLServer_Databases.id`; links to the active database record | | name | nvarchar | 128 | No | | | | Database name as recorded in audit events | | minimum_event_datetime | datetime2 | | Yes | | | | Earliest event timestamp recorded for this database | @@ -715,7 +715,7 @@ **Indexes:** `UQ_SA_SQLServer_Events_StaleDataLookup` on `(file_id, event_time)` (nonclustered, non-unique despite UQ_ prefix) -> **Note:** Despite the `UQ_` prefix used in some environments, this index is **not unique** per the live schema (`is_unique = 0`). +> **Note:** Despite the `UQ_` prefix used in some environments, this index **isn't unique** per the live schema (`is_unique = 0`). --- @@ -950,7 +950,7 @@ | instance_id | int | | No | PK | | IDENTITY | Auto-incrementing surrogate primary key | | instance_label | nvarchar | 256 | No | | | | Unique display label for the instance | | service_name | nvarchar | 128 | Yes | | | | Named instance or service/database name | -| is_active | bit | | No | | | `1` | Whether the instance is currently active for data collection | +| is_active | bit | | No | | | `1` | Whether the instance is active for data collection | | enable_impersonation | bit | | No | | | `0` | Whether Windows impersonation is enabled for connecting to this instance | | database_type | int | | No | | | | Database platform type (see Section 6.11) | | host_name | nvarchar | 150 | No | | | | Server hostname or IP address | diff --git a/docs/accessanalyzer/11.6/admin/schema/sqldc/enumeration/overview.md b/docs/accessanalyzer/11.6/admin/schema/sqldc/enumeration/overview.md index 8ff9afaedf..9dbf419d41 100644 --- a/docs/accessanalyzer/11.6/admin/schema/sqldc/enumeration/overview.md +++ b/docs/accessanalyzer/11.6/admin/schema/sqldc/enumeration/overview.md @@ -265,13 +265,13 @@ Used to compute the `Database Type` column in `SA_SQLServer_EffectiveRoleMembers | `5` | MySql | MySQL | | `6` | AzureSqlServerManagedInstance | Azure SQL Managed Instance | | `7` | SaDataSource | StealthAUDIT Data Source | -| `8` | AWSPostgres | AWS PostgreSQL (not currently supported) | -| `9` | AWSMySql | AWS MySQL (not currently supported) | -| `10` | EDBPostgreSql | EDB PostgreSQL (not currently supported) | -| `11` | SqlServerCluster | SQL Server Cluster (not currently supported) | +| `8` | AWSPostgres | AWS PostgreSQL (not supported) | +| `9` | AWSMySql | AWS MySQL (not supported) | +| `10` | EDBPostgreSql | EDB PostgreSQL (not supported) | +| `11` | SqlServerCluster | SQL Server Cluster (not supported) | | `12` | Db2LUW | IBM Db2 LUW | | `20` | MongoDb | MongoDB | :::note Within the SQL Server Data Collector context, only values `0` (Unset), `1` (SqlServer), `2` (AzureSqlServer), and `6` (AzureSqlServerManagedInstance) are applicable. The remaining values are used by other database collector modules that share the `SA_SQL_Instances` table. -::: \ No newline at end of file +::: diff --git a/docs/accessanalyzer/11.6/admin/schema/sqldc/overview.md b/docs/accessanalyzer/11.6/admin/schema/sqldc/overview.md index d1a7779780..36d3354fe8 100644 --- a/docs/accessanalyzer/11.6/admin/schema/sqldc/overview.md +++ b/docs/accessanalyzer/11.6/admin/schema/sqldc/overview.md @@ -8,201 +8,201 @@ This is a comprehensive schema documentation for the **NAA 11.6 SQL Server Data The tables fall into two categories: -1. **Core Data Collection Tables** (44 tables) — Normalized tables populated directly by data collectors. These contain raw audit data with full foreign key relationships. Includes shared infrastructure tables (`SA_SQL_Instances`, `SA_SQL_Patches`) used across all database collector modules. +1. **Core Data Collection Tables** (44 tables) — Normalized tables that data collectors populate directly. These contain raw audit data with full foreign key relationships. Includes shared infrastructure tables (`SA_SQL_Instances`, `SA_SQL_Patches`) used across all database collector modules. -2. **Reporting / Summary Tables** (59 tables) — Denormalized, report-ready tables populated by analysis jobs. These use human-readable column names (e.g., `"Instance"`, `"Database"`, `"Permission"`). +2. **Reporting / Summary Tables** (59 tables) — Denormalized, report-ready tables that analysis jobs populate. These use human-readable column names (e.g., `"Instance"`, `"Database"`, `"Permission"`). --- ### [Core Data Collection Tables](coretables/overview.md) - - [SA_SQLServer_Instances](coretables/overview.md#sa_sqlserver_instances) - - [SA_SQLServer_Databases](coretables/overview.md#sa_sqlserver_databases) - - [SA_SQLServer_EventDatabases](coretables/overview.md#sa_sqlserver_eventdatabases) - - [SA_SQLServer_Schemas](coretables/overview.md#sa_sqlserver_schemas) - - [SA_SQLServer_Objects](coretables/overview.md#sa_sqlserver_objects) - - [SA_SQLServer_Columns](coretables/overview.md#sa_sqlserver_columns) - - [SA_SQLServer_ServerPrincipalTypes](coretables/overview.md#sa_sqlserver_serverprincipaltypes) - - [SA_SQLServer_DatabasePrincipalTypes](coretables/overview.md#sa_sqlserver_databaseprincipaltypes) - - [SA_SQLServer_ServerPrincipals](coretables/overview.md#sa_sqlserver_serverprincipals) - - [SA_SQLServer_DatabasePrincipals](coretables/overview.md#sa_sqlserver_databaseprincipals) - - [SA_SQLServer_EventServerPrincipals](coretables/overview.md#sa_sqlserver_eventserverprincipals) - - [SA_SQLServer_EventDatabasePrincipals](coretables/overview.md#sa_sqlserver_eventdatabaseprincipals) - - [SA_SQLServer_SqlLogins](coretables/overview.md#sa_sqlserver_sqllogins) - - [SA_SQLServer_ServerRoleMembers](coretables/overview.md#sa_sqlserver_serverrolemembers) - - [SA_SQLServer_DatabaseRoleMembers](coretables/overview.md#sa_sqlserver_databaserolemembers) - - [SA_SQLServer_EffectiveRoleMembership](coretables/overview.md#sa_sqlserver_effectiverolemembership) - - [SA_SQLServer_PermissionNames](coretables/overview.md#sa_sqlserver_permissionnames) - - [SA_SQLServer_PermissionClasses](coretables/overview.md#sa_sqlserver_permissionclasses) - - [SA_SQLServer_PermissionStates](coretables/overview.md#sa_sqlserver_permissionstates) - - [SA_SQLServer_ServerPermissions](coretables/overview.md#sa_sqlserver_serverpermissions) - - [SA_SQLServer_DatabasePermissions](coretables/overview.md#sa_sqlserver_databasepermissions) - - [SA_SQLServer_AsymmetricKeys](coretables/overview.md#sa_sqlserver_asymmetrickeys) - - [SA_SQLServer_AuditInformation](coretables/overview.md#sa_sqlserver_auditinformation) - - [SA_SQLServer_AuditFiles](coretables/overview.md#sa_sqlserver_auditfiles) - - [SA_SQLServer_AuditClassType](coretables/overview.md#sa_sqlserver_auditclasstype) - - [SA_SQLServer_AuditActions](coretables/overview.md#sa_sqlserver_auditactions) - - [SA_SQLServer_Statements](coretables/overview.md#sa_sqlserver_statements) - - [SA_SQLServer_AdditionalInformation](coretables/overview.md#sa_sqlserver_additionalinformation) - - [SA_SQLServer_UserEvents](coretables/overview.md#sa_sqlserver_userevents) - - [SA_SQLServer_Events](coretables/overview.md#sa_sqlserver_events) - - [SA_SQLServer_ExpressionDependencies](coretables/overview.md#sa_sqlserver_expressiondependencies) - - [SA_SQLServer_SDD_Criteria](coretables/overview.md#sa_sqlserver_sdd_criteria) - - [SA_SQLServer_SDD_InstanceCriteria](coretables/overview.md#sa_sqlserver_sdd_instancecriteria) - - [SA_SQLServer_SDD_DatabaseCriteria](coretables/overview.md#sa_sqlserver_sdd_databasecriteria) - - [SA_SQLServer_SDD_ResourceTypes](coretables/overview.md#sa_sqlserver_sdd_resourcetypes) - - [SA_SQLServer_SDD_Resources](coretables/overview.md#sa_sqlserver_sdd_resources) - - [SA_SQLServer_SDD_Matches](coretables/overview.md#sa_sqlserver_sdd_matches) - - [SA_SQLServer_SDD_MatchHits](coretables/overview.md#sa_sqlserver_sdd_matchhits) - - [SA_SQLServer_SDD_MatchHits_SubjectProfile](coretables/overview.md#sa_sqlserver_sdd_matchhits_subjectprofile) - - [SA_SQLServer_SDD_ScanHistory](coretables/overview.md#sa_sqlserver_sdd_scanhistory) - - [SA_SQLServer_SDD_SupportedDataTypes](coretables/overview.md#sa_sqlserver_sdd_supporteddatatypes) - - [SA_SQL_Patches](coretables/overview.md#sa_sql_patches) - - [SA_SQL_Instances](coretables/overview.md#sa_sql_instances) - - [SA_SQL_PasswordIssues_LIST](coretables/overview.md#sa_sql_passwordissues_list) + - [SA_SQLServer_Instances](coretables/overview.md#sasqlserverinstances) + - [SA_SQLServer_Databases](coretables/overview.md#sasqlserverdatabases) + - [SA_SQLServer_EventDatabases](coretables/overview.md#sasqlservereventdatabases) + - [SA_SQLServer_Schemas](coretables/overview.md#sasqlserverschemas) + - [SA_SQLServer_Objects](coretables/overview.md#sasqlserverobjects) + - [SA_SQLServer_Columns](coretables/overview.md#sasqlservercolumns) + - [SA_SQLServer_ServerPrincipalTypes](coretables/overview.md#sasqlserverserverprincipaltypes) + - [SA_SQLServer_DatabasePrincipalTypes](coretables/overview.md#sasqlserverdatabaseprincipaltypes) + - [SA_SQLServer_ServerPrincipals](coretables/overview.md#sasqlserverserverprincipals) + - [SA_SQLServer_DatabasePrincipals](coretables/overview.md#sasqlserverdatabaseprincipals) + - [SA_SQLServer_EventServerPrincipals](coretables/overview.md#sasqlservereventserverprincipals) + - [SA_SQLServer_EventDatabasePrincipals](coretables/overview.md#sasqlservereventdatabaseprincipals) + - [SA_SQLServer_SqlLogins](coretables/overview.md#sasqlserversqllogins) + - [SA_SQLServer_ServerRoleMembers](coretables/overview.md#sasqlserverserverrolemembers) + - [SA_SQLServer_DatabaseRoleMembers](coretables/overview.md#sasqlserverdatabaserolemembers) + - [SA_SQLServer_EffectiveRoleMembership](coretables/overview.md#sasqlservereffectiverolemembership) + - [SA_SQLServer_PermissionNames](coretables/overview.md#sasqlserverpermissionnames) + - [SA_SQLServer_PermissionClasses](coretables/overview.md#sasqlserverpermissionclasses) + - [SA_SQLServer_PermissionStates](coretables/overview.md#sasqlserverpermissionstates) + - [SA_SQLServer_ServerPermissions](coretables/overview.md#sasqlserverserverpermissions) + - [SA_SQLServer_DatabasePermissions](coretables/overview.md#sasqlserverdatabasepermissions) + - [SA_SQLServer_AsymmetricKeys](coretables/overview.md#sasqlserverasymmetrickeys) + - [SA_SQLServer_AuditInformation](coretables/overview.md#sasqlserverauditinformation) + - [SA_SQLServer_AuditFiles](coretables/overview.md#sasqlserverauditfiles) + - [SA_SQLServer_AuditClassType](coretables/overview.md#sasqlserverauditclasstype) + - [SA_SQLServer_AuditActions](coretables/overview.md#sasqlserverauditactions) + - [SA_SQLServer_Statements](coretables/overview.md#sasqlserverstatements) + - [SA_SQLServer_AdditionalInformation](coretables/overview.md#sasqlserveradditionalinformation) + - [SA_SQLServer_UserEvents](coretables/overview.md#sasqlserveruserevents) + - [SA_SQLServer_Events](coretables/overview.md#sasqlserverevents) + - [SA_SQLServer_ExpressionDependencies](coretables/overview.md#sasqlserverexpressiondependencies) + - [SA_SQLServer_SDD_Criteria](coretables/overview.md#sasqlserversddcriteria) + - [SA_SQLServer_SDD_InstanceCriteria](coretables/overview.md#sasqlserversddinstancecriteria) + - [SA_SQLServer_SDD_DatabaseCriteria](coretables/overview.md#sasqlserversdddatabasecriteria) + - [SA_SQLServer_SDD_ResourceTypes](coretables/overview.md#sasqlserversddresourcetypes) + - [SA_SQLServer_SDD_Resources](coretables/overview.md#sasqlserversddresources) + - [SA_SQLServer_SDD_Matches](coretables/overview.md#sasqlserversddmatches) + - [SA_SQLServer_SDD_MatchHits](coretables/overview.md#sasqlserversddmatchhits) + - [SA_SQLServer_SDD_MatchHits_SubjectProfile](coretables/overview.md#sasqlserversddmatchhitssubjectprofile) + - [SA_SQLServer_SDD_ScanHistory](coretables/overview.md#sasqlserversddscanhistory) + - [SA_SQLServer_SDD_SupportedDataTypes](coretables/overview.md#sasqlserversddsupporteddatatypes) + - [SA_SQL_Patches](coretables/overview.md#sasqlpatches) + - [SA_SQL_Instances](coretables/overview.md#sasqlinstances) + - [SA_SQL_PasswordIssues_LIST](coretables/overview.md#sasqlpasswordissueslist) ### [Reporting Tables](reportingtables/overview.md) #### [Activity](reportingtables/overview.md#activity) - - [SA_SQLServer_Activity_Details](reportingtables/overview.md#sa_sqlserver_activity_details) - - [SA_SQLServer_Activity_UserDatabaseSummary](reportingtables/overview.md#sa_sqlserver_activity_userdatabasesummary) - - [SA_SQLServer_Activity_UserInstanceSummary](reportingtables/overview.md#sa_sqlserver_activity_userinstancesummary) + - [SA_SQLServer_Activity_Details](reportingtables/overview.md#sasqlserveractivitydetails) + - [SA_SQLServer_Activity_UserDatabaseSummary](reportingtables/overview.md#sasqlserveractivityuserdatabasesummary) + - [SA_SQLServer_Activity_UserInstanceSummary](reportingtables/overview.md#sasqlserveractivityuserinstancesummary) #### [Authentication](reportingtables/overview.md#authentication) - - [SA_SQLServer_Authentication_Details](reportingtables/overview.md#sa_sqlserver_authentication_details) - - [SA_SQLServer_Authentication_Summary](reportingtables/overview.md#sa_sqlserver_authentication_summary) + - [SA_SQLServer_Authentication_Details](reportingtables/overview.md#sasqlserverauthenticationdetails) + - [SA_SQLServer_Authentication_Summary](reportingtables/overview.md#sasqlserverauthenticationsummary) #### [Control Server](reportingtables/overview.md#control-server) - - [SA_SQLServer_ControlServer_Details](reportingtables/overview.md#sa_sqlserver_controlserver_details) - - [SA_SQLServer_ControlServer_DomainUsers](reportingtables/overview.md#sa_sqlserver_controlserver_domainusers) - - [SA_SQLServer_ControlServer_InstanceSummary](reportingtables/overview.md#sa_sqlserver_controlserver_instancesummary) + - [SA_SQLServer_ControlServer_Details](reportingtables/overview.md#sasqlservercontrolserverdetails) + - [SA_SQLServer_ControlServer_DomainUsers](reportingtables/overview.md#sasqlservercontrolserverdomainusers) + - [SA_SQLServer_ControlServer_InstanceSummary](reportingtables/overview.md#sasqlservercontrolserverinstancesummary) #### [Database Principals](reportingtables/overview.md#database-principals) - - [SA_SQLServer_DatabasePrincipals_Details](reportingtables/overview.md#sa_sqlserver_databaseprincipals_details) - - [SA_SQLServer_DatabasePrincipals_InstanceSummary](reportingtables/overview.md#sa_sqlserver_databaseprincipals_instancesummary) + - [SA_SQLServer_DatabasePrincipals_Details](reportingtables/overview.md#sasqlserverdatabaseprincipalsdetails) + - [SA_SQLServer_DatabasePrincipals_InstanceSummary](reportingtables/overview.md#sasqlserverdatabaseprincipalsinstancesummary) #### [Database Size](reportingtables/overview.md#database-size) - - [SA_SQLServer_DatabaseSize_Details](reportingtables/overview.md#sa_sqlserver_databasesize_details) - - [SA_SQLServer_DatabaseSize_Summary](reportingtables/overview.md#sa_sqlserver_databasesize_summary) + - [SA_SQLServer_DatabaseSize_Details](reportingtables/overview.md#sasqlserverdatabasesizedetails) + - [SA_SQLServer_DatabaseSize_Summary](reportingtables/overview.md#sasqlserverdatabasesizesummary) #### [Direct Permissions](reportingtables/overview.md#direct-permissions) - - [SA_SQLServer_DirectPermissions_DatabaseDetails](reportingtables/overview.md#sa_sqlserver_directpermissions_databasedetails) - - [SA_SQLServer_DirectPermissions_DatabaseSummary](reportingtables/overview.md#sa_sqlserver_directpermissions_databasesummary) - - [SA_SQLServer_DirectPermissions_SchemaDetails](reportingtables/overview.md#sa_sqlserver_directpermissions_schemadetails) - - [SA_SQLServer_DirectPermissions_SchemaSummary](reportingtables/overview.md#sa_sqlserver_directpermissions_schemasummary) - - [SA_SQLServer_DirectPermissions_ServerDetails](reportingtables/overview.md#sa_sqlserver_directpermissions_serverdetails) - - [SA_SQLServer_DirectPermissions_ServerSummary](reportingtables/overview.md#sa_sqlserver_directpermissions_serversummary) + - [SA_SQLServer_DirectPermissions_DatabaseDetails](reportingtables/overview.md#sasqlserverdirectpermissionsdatabasedetails) + - [SA_SQLServer_DirectPermissions_DatabaseSummary](reportingtables/overview.md#sasqlserverdirectpermissionsdatabasesummary) + - [SA_SQLServer_DirectPermissions_SchemaDetails](reportingtables/overview.md#sasqlserverdirectpermissionsschemadetails) + - [SA_SQLServer_DirectPermissions_SchemaSummary](reportingtables/overview.md#sasqlserverdirectpermissionsschemasummary) + - [SA_SQLServer_DirectPermissions_ServerDetails](reportingtables/overview.md#sasqlserverdirectpermissionsserverdetails) + - [SA_SQLServer_DirectPermissions_ServerSummary](reportingtables/overview.md#sasqlserverdirectpermissionsserversummary) #### [Domain User Permissions](reportingtables/overview.md#domain-user-permissions) - - [SA_SQLServer_DomainUserPermissions_Details](reportingtables/overview.md#sa_sqlserver_domainuserpermissions_details) - - [SA_SQLServer_DomainUserPermissions_Summary](reportingtables/overview.md#sa_sqlserver_domainuserpermissions_summary) + - [SA_SQLServer_DomainUserPermissions_Details](reportingtables/overview.md#sasqlserverdomainuserpermissionsdetails) + - [SA_SQLServer_DomainUserPermissions_Summary](reportingtables/overview.md#sasqlserverdomainuserpermissionssummary) #### [Effective Role Members](reportingtables/overview.md#effective-role-members) - - [SA_SQLServer_EffectiveRoleMember_Summary](reportingtables/overview.md#sa_sqlserver_effectiverolemember_summary) + - [SA_SQLServer_EffectiveRoleMember_Summary](reportingtables/overview.md#sasqlservereffectiverolemembersummary) #### [Instance Summary](reportingtables/overview.md#instance-summary) - - [SA_SQLServer_InstanceSummary](reportingtables/overview.md#sa_sqlserver_instancesummary) + - [SA_SQLServer_InstanceSummary](reportingtables/overview.md#sasqlserverinstancesummary) #### [Logons](reportingtables/overview.md#logons) - - [SA_SQLServer_Logons_Details](reportingtables/overview.md#sa_sqlserver_logons_details) - - [SA_SQLServer_Logons_Summary](reportingtables/overview.md#sa_sqlserver_logons_summary) + - [SA_SQLServer_Logons_Details](reportingtables/overview.md#sasqlserverlogonsdetails) + - [SA_SQLServer_Logons_Summary](reportingtables/overview.md#sasqlserverlogonssummary) #### [Password Issues](reportingtables/overview.md#password-issues) - - [SA_SQLServer_PasswordIssues_Details](reportingtables/overview.md#sa_sqlserver_passwordissues_details) - - [SA_SQLServer_PasswordIssues_Summary](reportingtables/overview.md#sa_sqlserver_passwordissues_summary) + - [SA_SQLServer_PasswordIssues_Details](reportingtables/overview.md#sasqlserverpasswordissuesdetails) + - [SA_SQLServer_PasswordIssues_Summary](reportingtables/overview.md#sasqlserverpasswordissuessummary) #### [Permission Changes](reportingtables/overview.md#permission-changes) - - [SA_SQLServer_PermissionChanges_Details](reportingtables/overview.md#sa_sqlserver_permissionchanges_details) - - [SA_SQLServer_PermissionChanges_InstanceSummary](reportingtables/overview.md#sa_sqlserver_permissionchanges_instancesummary) + - [SA_SQLServer_PermissionChanges_Details](reportingtables/overview.md#sasqlserverpermissionchangesdetails) + - [SA_SQLServer_PermissionChanges_InstanceSummary](reportingtables/overview.md#sasqlserverpermissionchangesinstancesummary) #### [Public Permissions](reportingtables/overview.md#public-permissions) - - [SA_SQLServer_PublicPermissions_Details](reportingtables/overview.md#sa_sqlserver_publicpermissions_details) - - [SA_SQLServer_PublicPermissions_DatabaseSummary](reportingtables/overview.md#sa_sqlserver_publicpermissions_databasesummary) - - [SA_SQLServer_PublicPermissions_InstanceSummary](reportingtables/overview.md#sa_sqlserver_publicpermissions_instancesummary) - - [SA_SQLServer_PublicPermissions_NonDefault](reportingtables/overview.md#sa_sqlserver_publicpermissions_nondefault) + - [SA_SQLServer_PublicPermissions_Details](reportingtables/overview.md#sasqlserverpublicpermissionsdetails) + - [SA_SQLServer_PublicPermissions_DatabaseSummary](reportingtables/overview.md#sasqlserverpublicpermissionsdatabasesummary) + - [SA_SQLServer_PublicPermissions_InstanceSummary](reportingtables/overview.md#sasqlserverpublicpermissionsinstancesummary) + - [SA_SQLServer_PublicPermissions_NonDefault](reportingtables/overview.md#sasqlserverpublicpermissionsnondefault) #### [Role Members](reportingtables/overview.md#role-members) - - [SA_SQLServer_RoleMember_Details](reportingtables/overview.md#sa_sqlserver_rolemember_details) - - [SA_SQLServer_RoleMember_Summary](reportingtables/overview.md#sa_sqlserver_rolemember_summary) + - [SA_SQLServer_RoleMember_Details](reportingtables/overview.md#sasqlserverrolememberdetails) + - [SA_SQLServer_RoleMember_Summary](reportingtables/overview.md#sasqlserverrolemembersummary) #### [Security Assessment](reportingtables/overview.md#security-assessment) - - [SA_SQLServer_SecurityAssessment_Results](reportingtables/overview.md#sa_sqlserver_securityassessment_results) - - [SA_SQLServer_SecurityAssessment_CategorySummary](reportingtables/overview.md#sa_sqlserver_securityassessment_categorysummary) + - [SA_SQLServer_SecurityAssessment_Results](reportingtables/overview.md#sasqlserversecurityassessmentresults) + - [SA_SQLServer_SecurityAssessment_CategorySummary](reportingtables/overview.md#sasqlserversecurityassessmentcategorysummary) #### [Sensitive Data](reportingtables/overview.md#sensitive-data) - - [SA_SQLServer_SensitiveData_Details](reportingtables/overview.md#sa_sqlserver_sensitivedata_details) - - [SA_SQLServer_SensitiveData_DatabaseSummary](reportingtables/overview.md#sa_sqlserver_sensitivedata_databasesummary) - - [SA_SQLServer_SensitiveData_EnterpriseSummary](reportingtables/overview.md#sa_sqlserver_sensitivedata_enterprisesummary) + - [SA_SQLServer_SensitiveData_Details](reportingtables/overview.md#sasqlserversensitivedatadetails) + - [SA_SQLServer_SensitiveData_DatabaseSummary](reportingtables/overview.md#sasqlserversensitivedatadatabasesummary) + - [SA_SQLServer_SensitiveData_EnterpriseSummary](reportingtables/overview.md#sasqlserversensitivedataenterprisesummary) #### [Sensitive Data Activity](reportingtables/overview.md#sensitive-data-activity) - - [SA_SQLServer_SensitiveDataActivity_Details](reportingtables/overview.md#sa_sqlserver_sensitivedataactivity_details) - - [SA_SQLServer_SensitiveDataActivity_UserSummary](reportingtables/overview.md#sa_sqlserver_sensitivedataactivity_usersummary) + - [SA_SQLServer_SensitiveDataActivity_Details](reportingtables/overview.md#sasqlserversensitivedataactivitydetails) + - [SA_SQLServer_SensitiveDataActivity_UserSummary](reportingtables/overview.md#sasqlserversensitivedataactivityusersummary) #### [Sensitive Data Permissions](reportingtables/overview.md#sensitive-data-permissions) - - [SA_SQLServer_SensitiveDataPermissions_Details](reportingtables/overview.md#sa_sqlserver_sensitivedatapermissions_details) - - [SA_SQLServer_SensitiveDataPermissions_DatabaseSummary](reportingtables/overview.md#sa_sqlserver_sensitivedatapermissions_databasesummary) + - [SA_SQLServer_SensitiveDataPermissions_Details](reportingtables/overview.md#sasqlserversensitivedatapermissionsdetails) + - [SA_SQLServer_SensitiveDataPermissions_DatabaseSummary](reportingtables/overview.md#sasqlserversensitivedatapermissionsdatabasesummary) #### [Server Permissions](reportingtables/overview.md#server-permissions) - - [SA_SQLServer_ServerPermission_Details](reportingtables/overview.md#sa_sqlserver_serverpermission_details) - - [SA_SQLServer_ServerPermission_InstanceSummary](reportingtables/overview.md#sa_sqlserver_serverpermission_instancesummary) + - [SA_SQLServer_ServerPermission_Details](reportingtables/overview.md#sasqlserverserverpermissiondetails) + - [SA_SQLServer_ServerPermission_InstanceSummary](reportingtables/overview.md#sasqlserverserverpermissioninstancesummary) #### [Server Principals](reportingtables/overview.md#server-principals) - - [SA_SQLServer_ServerPrincipals_Details](reportingtables/overview.md#sa_sqlserver_serverprincipals_details) - - [SA_SQLServer_ServerPrincipals_InstanceSummary](reportingtables/overview.md#sa_sqlserver_serverprincipals_instancesummary) + - [SA_SQLServer_ServerPrincipals_Details](reportingtables/overview.md#sasqlserverserverprincipalsdetails) + - [SA_SQLServer_ServerPrincipals_InstanceSummary](reportingtables/overview.md#sasqlserverserverprincipalsinstancesummary) #### [SysAdmins](reportingtables/overview.md#sysadmins) - - [SA_SQLServer_SysAdmins_Details](reportingtables/overview.md#sa_sqlserver_sysadmins_details) - - [SA_SQLServer_SysAdmins_DomainUsers](reportingtables/overview.md#sa_sqlserver_sysadmins_domainusers) - - [SA_SQLServer_SysAdmins_InstanceSummary](reportingtables/overview.md#sa_sqlserver_sysadmins_instancesummary) + - [SA_SQLServer_SysAdmins_Details](reportingtables/overview.md#sasqlserversysadminsdetails) + - [SA_SQLServer_SysAdmins_DomainUsers](reportingtables/overview.md#sasqlserversysadminsdomainusers) + - [SA_SQLServer_SysAdmins_InstanceSummary](reportingtables/overview.md#sasqlserversysadminsinstancesummary) #### [Unusual Activity](reportingtables/overview.md#unusual-activity) - - [SA_SQLServer_UnusualHourlyUserActivity](reportingtables/overview.md#sa_sqlserver_unusualhourlyuseractivity) - - [SA_SQLServer_UnusualActivitySummary](reportingtables/overview.md#sa_sqlserver_unusualactivitysummary) + - [SA_SQLServer_UnusualHourlyUserActivity](reportingtables/overview.md#sasqlserverunusualhourlyuseractivity) + - [SA_SQLServer_UnusualActivitySummary](reportingtables/overview.md#sasqlserverunusualactivitysummary) #### [User Logins](reportingtables/overview.md#user-logins) - - [SA_SQLServer_UserLogins_Details](reportingtables/overview.md#sa_sqlserver_userlogins_details) - - [SA_SQLServer_UserLogins_Summary](reportingtables/overview.md#sa_sqlserver_userlogins_summary) + - [SA_SQLServer_UserLogins_Details](reportingtables/overview.md#sasqlserveruserloginsdetails) + - [SA_SQLServer_UserLogins_Summary](reportingtables/overview.md#sasqlserveruserloginssummary) #### [Best Practices](reportingtables/overview.md#best-practices) - - [SA_SQL_BestPractices](reportingtables/overview.md#sa_sql_bestpractices) - - [SA_SQL_BestPractices_Summary](reportingtables/overview.md#sa_sql_bestpractices_summary) + - [SA_SQL_BestPractices](reportingtables/overview.md#sasqlbestpractices) + - [SA_SQL_BestPractices_Summary](reportingtables/overview.md#sasqlbestpracticessummary) #### [CMD Shell](reportingtables/overview.md#cmd-shell) - - [SA_SQL_CMDShell_Status](reportingtables/overview.md#sa_sql_cmdshell_status) + - [SA_SQL_CMDShell_Status](reportingtables/overview.md#sasqlcmdshellstatus) #### [Linked Servers](reportingtables/overview.md#linked-servers) - - [SA_SQL_LinkedServer_Details](reportingtables/overview.md#sa_sql_linkedserver_details) - - [SA_SQL_LinkedServer_Summary](reportingtables/overview.md#sa_sql_linkedserver_summary) + - [SA_SQL_LinkedServer_Details](reportingtables/overview.md#sasqllinkedserverdetails) + - [SA_SQL_LinkedServer_Summary](reportingtables/overview.md#sasqllinkedserversummary) ### [Views](views/overview.md) - - [SA_SQLServer_FullEventsView](views/overview.md#sa_sqlserver_fulleventsview) - - [SA_SQLServer_ServerPrincipalsView](views/overview.md#sa_sqlserver_serverprincipalsview) - - [SA_SQLServer_SqlLoginsView](views/overview.md#sa_sqlserver_sqlloginsview) - - [SA_SQLServer_DatabasePrincipalsView](views/overview.md#sa_sqlserver_databaseprincipalsview) - - [SA_SQLServer_PermissionsView](views/overview.md#sa_sqlserver_permissionsview) - - [SA_SQLServer_RoleMembersView](views/overview.md#sa_sqlserver_rolemembersview) - - [SA_SQLServer_SqlDatabaseView](views/overview.md#sa_sqlserver_sqldatabaseview) - - [SA_SQLServer_DailyLogonsView](views/overview.md#sa_sqlserver_dailylogonsview) - - [SA_SQLServer_SDD_ResourcesView](views/overview.md#sa_sqlserver_sdd_resourcesview) - - [SA_SQLServer_SDD_MatchesView](views/overview.md#sa_sqlserver_sdd_matchesview) - - [SA_SQLServer_SDD_MatchHitsView](views/overview.md#sa_sqlserver_sdd_matchhitsview) - - [SA_SQLServer_SensitiveDataPermissionsView](views/overview.md#sa_sqlserver_sensitivedatapermissionsview) - - [SA_SQLServer_SDD_MatchHits_SubjectProfileView](views/overview.md#sa_sqlserver_sdd_matchhits_subjectprofileview) - - [SA_SQLServer_SensitiveDataFullPermissionsView](views/overview.md#sa_sqlserver_sensitivedatafullpermissionsview) - - [SA_SQLServer_EffectiveRoleMembershipView](views/overview.md#sa_sqlserver_effectiverolemembershipview) - - [SA_SQL_SDD_MatchesView](views/overview.md#sa_sql_sdd_matchesview) - - [SA_SQL_SDD_MatchHitsView](views/overview.md#sa_sql_sdd_matchhitsview) + - [SA_SQLServer_FullEventsView](views/overview.md#sasqlserverfulleventsview) + - [SA_SQLServer_ServerPrincipalsView](views/overview.md#sasqlserverserverprincipalsview) + - [SA_SQLServer_SqlLoginsView](views/overview.md#sasqlserversqlloginsview) + - [SA_SQLServer_DatabasePrincipalsView](views/overview.md#sasqlserverdatabaseprincipalsview) + - [SA_SQLServer_PermissionsView](views/overview.md#sasqlserverpermissionsview) + - [SA_SQLServer_RoleMembersView](views/overview.md#sasqlserverrolemembersview) + - [SA_SQLServer_SqlDatabaseView](views/overview.md#sasqlserversqldatabaseview) + - [SA_SQLServer_DailyLogonsView](views/overview.md#sasqlserverdailylogonsview) + - [SA_SQLServer_SDD_ResourcesView](views/overview.md#sasqlserversddresourcesview) + - [SA_SQLServer_SDD_MatchesView](views/overview.md#sasqlserversddmatchesview) + - [SA_SQLServer_SDD_MatchHitsView](views/overview.md#sasqlserversddmatchhitsview) + - [SA_SQLServer_SensitiveDataPermissionsView](views/overview.md#sasqlserversensitivedatapermissionsview) + - [SA_SQLServer_SDD_MatchHits_SubjectProfileView](views/overview.md#sasqlserversddmatchhitssubjectprofileview) + - [SA_SQLServer_SensitiveDataFullPermissionsView](views/overview.md#sasqlserversensitivedatafullpermissionsview) + - [SA_SQLServer_EffectiveRoleMembershipView](views/overview.md#sasqlservereffectiverolemembershipview) + - [SA_SQL_SDD_MatchesView](views/overview.md#sasqlsddmatchesview) + - [SA_SQL_SDD_MatchHitsView](views/overview.md#sasqlsddmatchhitsview) ### [Enumeration & Lookup Values Reference](enumeration/overview.md) - - [Server Principal Types](enumeration/overview.md#server-principal-types-sa_sqlserver_serverprincipaltypes) - - [Database Principal Types](enumeration/overview.md#database-principal-types-sa_sqlserver_databaseprincipaltypes) - - [Permission States](enumeration/overview.md#permission-states-sa_sqlserver_permissionstates) - - [Permission Classes](enumeration/overview.md#permission-classes-sa_sqlserver_permissionclasses) - - [Permission Names](enumeration/overview.md#permission-names-sa_sqlserver_permissionnames) - - [Audit Class Types](enumeration/overview.md#audit-class-types-sa_sqlserver_auditclasstype) - - [Audit Actions (Common)](enumeration/overview.md#audit-actions-common-sa_sqlserver_auditactions) - - [SDD Resource Types](enumeration/overview.md#sdd-resource-types-sa_sqlserver_sdd_resourcetypes) + - [Server Principal Types](enumeration/overview.md#server-principal-types-sasqlserverserverprincipaltypes) + - [Database Principal Types](enumeration/overview.md#database-principal-types-sasqlserverdatabaseprincipaltypes) + - [Permission States](enumeration/overview.md#permission-states-sasqlserverpermissionstates) + - [Permission Classes](enumeration/overview.md#permission-classes-sasqlserverpermissionclasses) + - [Permission Names](enumeration/overview.md#permission-names-sasqlserverpermissionnames) + - [Audit Class Types](enumeration/overview.md#audit-class-types-sasqlserverauditclasstype) + - [Audit Actions (Common)](enumeration/overview.md#audit-actions-common-sasqlserverauditactions) + - [SDD Resource Types](enumeration/overview.md#sdd-resource-types-sasqlserversddresourcetypes) - [SDD Match Location Bitmask](enumeration/overview.md#sdd-match-location-bitmask) - - [Membership Source](enumeration/overview.md#membership-source-sa_sqlserver_effectiverolemembershipmembership_source) - - [Database Type](enumeration/overview.md#database-type-sa_sqlserver_effectiverolemembershipdatabase_type) + - [Membership Source](enumeration/overview.md#membership-source-sasqlservereffectiverolemembershipmembershipsource) + - [Database Type](enumeration/overview.md#database-type-sasqlservereffectiverolemembershipdatabasetype) ### [Table Relationship Diagrams (ERD)](erd/overview.md) - [High-Level Overview](erd/overview.md#high-level-overview) @@ -215,8 +215,8 @@ The tables fall into two categories: - [Complete Index List](indexreference/overview.md#complete-index-listing) ### [Scalar Functions & Stored Procedures](functions/overview.md) - - [SA_SQL_GetFriendlyName](functions/overview.md#sa_sql_getfriendlyname-scalar-function) - - [SA_SQLServer_BinarySIDToString](functions/overview.md#sa_sqlserver_binarysidtostring-scalar-function) - - [SA_SQLServer_GetAuditFileComparisonString](functions/overview.md#sa_sqlserver_getauditfilecomparisonstring-scalar-function) - - [SA_SQLServer_CreateOrUpdateSDDResource](functions/overview.md#sa_sqlserver_createorupdatesddresource-stored-procedure) + - [SA_SQL_GetFriendlyName](functions/overview.md#sasqlgetfriendlyname-scalar-function) + - [SA_SQLServer_BinarySIDToString](functions/overview.md#sasqlserverbinarysidtostring-scalar-function) + - [SA_SQLServer_GetAuditFileComparisonString](functions/overview.md#sasqlservergetauditfilecomparisonstring-scalar-function) + - [SA_SQLServer_CreateOrUpdateSDDResource](functions/overview.md#sasqlservercreateorupdatesddresource-stored-procedure) diff --git a/docs/accessanalyzer/11.6/admin/schema/sqldc/reportingtables/overview.md b/docs/accessanalyzer/11.6/admin/schema/sqldc/reportingtables/overview.md index 024266a3db..b2c72588ce 100644 --- a/docs/accessanalyzer/11.6/admin/schema/sqldc/reportingtables/overview.md +++ b/docs/accessanalyzer/11.6/admin/schema/sqldc/reportingtables/overview.md @@ -1,6 +1,6 @@ # Reporting Tables -The following 59 tables are **denormalized reporting tables** populated by NAA analysis jobs. They use human-readable column names with spaces (e.g., `"Database Type"`, `"Instance"`) and are designed for direct consumption by the NAA console and reports. They do not participate in foreign key relationships with the core tables. +The following 59 tables are **denormalized reporting tables** that NAA analysis jobs populate. They use human-readable column names with spaces (e.g., `"Database Type"`, `"Instance"`) and support direct consumption by the NAA console and reports. They don't participate in foreign key relationships with the core tables. :::note All reporting tables share a common `Database Type` column (varchar/nvarchar) that identifies the SQL Server platform variant (e.g., `"SQL Server"`, `"Azure SQL Database"`, `"Azure SQL Managed Instance"`). None of these tables have primary keys or foreign keys — they are heap tables optimized for bulk INSERT/TRUNCATE patterns. @@ -625,7 +625,7 @@ All reporting tables share a common `Database Type` column (varchar/nvarchar) th | Database | nvarchar | 128 | Yes | | Database name | | Schema | nvarchar | 128 | Yes | | Schema name | | Table | nvarchar | 128 | Yes | | Table name containing sensitive data | -| Criteria | nvarchar | MAX | Yes | | Matched SDD criteria name(s) | +| Criteria | nvarchar | MAX | Yes | | Matched SDD criteria names | | Table Row Count | bigint | | Yes | | Total rows in the table | | Match Count | bigint | | Yes | | Number of sensitive data matches | | Match Types | nvarchar | MAX | Yes | | Types of matches found | @@ -679,7 +679,7 @@ All reporting tables share a common `Database Type` column (varchar/nvarchar) th | Client | nvarchar | 128 | Yes | | Client IP or hostname | | Application | nvarchar | 128 | Yes | | Application name | | Action | nvarchar | 56 | Yes | | Action type (SELECT, INSERT, UPDATE, etc.) | -| Criteria | nvarchar | 256 | Yes | | SDD criteria name(s) for the object | +| Criteria | nvarchar | 256 | Yes | | SDD criteria names for the object | | Match Data | nvarchar | 256 | Yes | | Sample match data | --- @@ -710,7 +710,7 @@ All reporting tables share a common `Database Type` column (varchar/nvarchar) th | Instance | nvarchar | 128 | Yes | | SQL Server instance name | | Database | nvarchar | 128 | Yes | | Database name | | Object | nvarchar | 128 | Yes | | Object name containing sensitive data | -| Criteria | nvarchar | MAX | Yes | | SDD criteria name(s) | +| Criteria | nvarchar | MAX | Yes | | SDD criteria names | | Permission | nvarchar | 128 | Yes | | Permission name | | Grantee | nvarchar | 513 | Yes | | Grantee principal | | Grantee Id | nvarchar | 128 | Yes | | Grantee identifier | diff --git a/docs/accessanalyzer/11.6/admin/schema/sqldc/views/overview.md b/docs/accessanalyzer/11.6/admin/schema/sqldc/views/overview.md index 2d74f9ba6a..06a84c8dd1 100644 --- a/docs/accessanalyzer/11.6/admin/schema/sqldc/views/overview.md +++ b/docs/accessanalyzer/11.6/admin/schema/sqldc/views/overview.md @@ -117,7 +117,7 @@ | is_policy_checked | bit | | No | SA_SQLServer_SqlLogins.is_policy_checked | Whether password policy is enforced | | is_expiration_checked | bit | | No | SA_SQLServer_SqlLogins.is_expiration_checked | Whether password expiration is enforced | | password_hash | varbinary | 256 | Yes | SA_SQLServer_SqlLogins.password_hash | Hashed password value | -| is_locked | bit | | Yes | SA_SQLServer_SqlLogins.is_locked | Whether the account is currently locked out | +| is_locked | bit | | Yes | SA_SQLServer_SqlLogins.is_locked | Whether the account is locked out | | is_expired | bit | | Yes | SA_SQLServer_SqlLogins.is_expired | Whether the password has expired | | is_must_change | bit | | Yes | SA_SQLServer_SqlLogins.is_must_change | Whether the password must be changed at next login | | password_hash_algorithm | int | | Yes | SA_SQLServer_SqlLogins.password_hash_algorithm | Algorithm used to hash the password | diff --git a/docs/accessanalyzer/11.6/admin/settings/access/overview.md b/docs/accessanalyzer/11.6/admin/settings/access/overview.md index e8b678351d..065d297c40 100644 --- a/docs/accessanalyzer/11.6/admin/settings/access/overview.md +++ b/docs/accessanalyzer/11.6/admin/settings/access/overview.md @@ -6,12 +6,12 @@ sidebar_position: 10 # Access -Configure what applications, users, and groups have access to Enterprise Auditor using the Access -node +Use the Access node to configure what applications, users, and groups have access to Enterprise +Auditor. ![Access Window](/images/accessanalyzer/11.6/admin/settings/access/access.webp) -The first type of access that can be granted is Role Based Access for a user or group accessing the +The first type of access you can grant is Role Based Access for a user or group accessing the Enterprise Auditor Console. The second type of access grants access to an application accessing data remotely through the Web Service using the REST API. See these sections for additional information: @@ -24,7 +24,7 @@ credentials stored by the Enterprise Auditor application. See the topic for additional information. The **Cancel** and **Save** buttons are in the lower-right corner of the Roles view. These buttons -are enabled when modifications are made to the Roles global setting. +become enabled when you modify the Roles global setting. -Whenever changes are made at the global level, click **Save** and then **OK** to confirm the +Whenever you make changes at the global level, click **Save** and then **OK** to confirm the changes. Otherwise, click **Cancel** if no changes were intended. diff --git a/docs/accessanalyzer/11.6/admin/settings/access/restapi/assignappaccess.md b/docs/accessanalyzer/11.6/admin/settings/access/restapi/assignappaccess.md index 95cf99ccad..aabb917057 100644 --- a/docs/accessanalyzer/11.6/admin/settings/access/restapi/assignappaccess.md +++ b/docs/accessanalyzer/11.6/admin/settings/access/restapi/assignappaccess.md @@ -6,8 +6,7 @@ sidebar_position: 10 # Assign Application Access through the Web Service -An application can be assigned to access data remotely through the Web Service. Follow the steps to -assign roles in the Console. +You can assign an application to access data remotely through the Web Service. To assign roles in the Console: ![Add Access option on Access page](/images/accessanalyzer/11.6/admin/settings/access/rolebased/addaccess.webp) @@ -21,8 +20,8 @@ opens. ![Application Access page of the Access Role Wizard](/images/accessanalyzer/11.6/admin/settings/access/restapi/applicationaccess.webp) -**Step 3 –** The Application Access window displays a list of objects available in the database that -are available for access. Select the database objects the application will access and click **Add** +**Step 3 –** The Application Access window displays a list of database objects available for access. +Select the database objects the application will access and click **Add** to open the Select database objects window. ![Select database objects window](/images/accessanalyzer/11.6/admin/settings/access/restapi/selectdatabaseobjects.webp) @@ -50,11 +49,11 @@ name** box to filter the list of objects by the characters entered. app token. - Application name – The name of the application accessing that data -- Access Expiration – The expiration for the client secret. Select an option for the desired access - expiration: +- Access Expiration – The expiration for the client secret. Select an option for the access + expiration you want: - - Access expires within – Select a time frame from the drop-down list. The default is 72 hours. - - Access expires on specified date – Select a date from the drop-down list + - Access expires within – Select a time frame from the dropdown list. The default is 72 hours. + - Access expires on specified date – Select a date from the dropdown list - Generate – Click this button to generate the Client ID and Client secret - Client ID – Copy the Client ID into the application accessing data remotely through the Web @@ -64,4 +63,4 @@ app token. **Step 6 –** Click **Finish** to confirm the changes. -The application is added to the table on the Access page. +Enterprise Auditor adds the application to the table on the Access page. diff --git a/docs/accessanalyzer/11.6/admin/settings/access/restapi/getdata.md b/docs/accessanalyzer/11.6/admin/settings/access/restapi/getdata.md index 0795d56eb1..3ccd08a67e 100644 --- a/docs/accessanalyzer/11.6/admin/settings/access/restapi/getdata.md +++ b/docs/accessanalyzer/11.6/admin/settings/access/restapi/getdata.md @@ -27,15 +27,15 @@ GET, POST **PARAMETERS** - **object-name** – Required value that specifies the unique object name. - **alias-name** – Required value that specifies the unique alias associated with the table, available as a more thoughtfully designed namespace. -- **jobRuntimeKey**(Optional) – The execution to retrieve information for. If this is omitted the latest report is provided. -- **filters** (Optional) – A filter to be applied prior to returning data, multiple filters are applied with `and` operators. If an array is specified for the value field for a filter, the filter returns any successful match from the array of values. String comparisons are case insensitive. A list of the available functions is below. Filter functions: +- **jobRuntimeKey**(Optional) – The execution to retrieve information for. If you omit this parameter, the endpoint returns the latest report. +- **filters** (Optional) – A filter to apply before returning data. Multiple filters are applied with `and` operators. If an array is specified for the value field for a filter, the filter returns any successful match from the array of values. String comparisons are case insensitive. The following filter functions are available: - equals - not_equals - greater (greater_equal) - less (less_equal) - contains - starts_with -- **columns** (Optional) – A list of columns to be returned. When not specified all columns are returned. The columns specified by the **groupby** parameter should be omitted from this array. +- **columns** (Optional) – A list of columns to return. If you don't specify this parameter, the endpoint returns all columns. Omit the columns specified by the **groupby** parameter from this array. - **groupby** (Optional) – A list of columns to group each row by, resulting in a JSON object that contains those keys followed by an array of entries. Sample JSON request: @@ -81,7 +81,7 @@ Sample JSON response: **ERRORS** - 400 One or more the parameters passed in are invalid. -- 404 The object requested does not exist. +- 404 The object requested doesn't exist. ## PROC @@ -100,7 +100,7 @@ POST **PARAMETERS** - **object-name** – Required value that specifies the unique object name. -- **groupby**(Optional) – A list of columns to group each row by, resulting in a JSON object that contains those keys followed by an array of entries. The parameters passed in here are passed to the stored procedure untouched. Arrays are mapped to a user defined table type, currently only single value arrays are supported. +- **groupby**(Optional) – A list of columns to group each row by, resulting in a JSON object that contains those keys followed by an array of entries. The endpoint passes the parameters you provide here to the stored procedure untouched. It maps arrays to a user-defined table type and supports only single-value arrays. Sample JSON request: @@ -139,4 +139,4 @@ Sample JSON request: **ERRORS** - 400 One or more the parameters passed in are invalid. -- 404 The object requested does not exist. \ No newline at end of file +- 404 The object requested doesn't exist. diff --git a/docs/accessanalyzer/11.6/admin/settings/access/restapi/obtaintoken.md b/docs/accessanalyzer/11.6/admin/settings/access/restapi/obtaintoken.md index 7f000d9066..b29dff97d1 100644 --- a/docs/accessanalyzer/11.6/admin/settings/access/restapi/obtaintoken.md +++ b/docs/accessanalyzer/11.6/admin/settings/access/restapi/obtaintoken.md @@ -6,17 +6,17 @@ sidebar_position: 20 # Use the Client Credentials Grant to Obtain an Access Token -An access token is a credential that can be used by an application to access an API. To obtain an +An access token is a credential an application uses to access an API. To obtain an access token, the application accessing data remotely through the Web Service must connect to the Enterprise Auditor token endpoint and use the Client ID and Client Secret to authenticate the access -request. This is done using the Client Credentials grant. The Client Credentials grant is used when -applications request an access token to access their own resources, not on behalf of a user. The -following request parameters should be used: +request. This process uses the Client Credentials grant. Applications use the Client Credentials +grant when they request an access token to access their own resources, not on behalf of a user. Use +the following request parameters: - `grant_type` (required) – The `grant_type` parameter must be set to `client_credentials` - `scope` (optional) – Your service may support different scopes for the client credentials grant -The client must then be authenticated for the request. Typically, the service will allow either +The service must then authenticate the client for the request. Typically, the service will allow either additional request parameters, `client_ID` and `client_secret`, or accept those parameters in the HTTP Basic auth header. @@ -31,15 +31,15 @@ grant_type=client_credentials ``` :::info -Tokens contain sensitive information and should be stored securely. See the +Store tokens securely because they contain sensitive information. See the Microsoft [ConvertTo-SecureString](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.security/convertto-securestring?view=powershell-7.4) article for additional information. ::: -If the token does not have the ability to perform this request, is invalid, or the specific resource -has been blocked from access remotely, an HTTP status code of 401 is returned. +If the token can't perform this request, is invalid, or the specific resource has been blocked from +access remotely, the server returns an HTTP status code of 401. If the request for an access token is valid, the authorization server generates an access token and returns it to the client. The following example shows a successful access token response: diff --git a/docs/accessanalyzer/11.6/admin/settings/access/restapi/overview.md b/docs/accessanalyzer/11.6/admin/settings/access/restapi/overview.md index c8f052bb18..f28ac347a9 100644 --- a/docs/accessanalyzer/11.6/admin/settings/access/restapi/overview.md +++ b/docs/accessanalyzer/11.6/admin/settings/access/restapi/overview.md @@ -6,8 +6,8 @@ sidebar_position: 20 # Web Service REST API for Applications Accessing Data Remotely -The Enterprise Auditor REST API is integrated into the Web Service as an endpoint using an OAuth 2.0 -client credentials grant for authentication and providing the following access role: +The Web Service integrates the Enterprise Auditor REST API as an endpoint that uses an OAuth 2.0 +client credentials grant for authentication and provides the following access role: - Read-Only – Read data only diff --git a/docs/accessanalyzer/11.6/admin/settings/access/restapi/powershellcommands.md b/docs/accessanalyzer/11.6/admin/settings/access/restapi/powershellcommands.md index eb33afabe5..32f0d5ea60 100644 --- a/docs/accessanalyzer/11.6/admin/settings/access/restapi/powershellcommands.md +++ b/docs/accessanalyzer/11.6/admin/settings/access/restapi/powershellcommands.md @@ -25,7 +25,7 @@ $refresh_token = $content.refresh_token; ``` :::info -Tokens contain sensitive information and should be stored securely. See the +Store tokens securely because they contain sensitive information. See the Microsoft [ConvertTo-SecureString](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.security/convertto-securestring?view=powershell-7.4) article for additional information. diff --git a/docs/accessanalyzer/11.6/admin/settings/access/restapi/refreshtoken.md b/docs/accessanalyzer/11.6/admin/settings/access/restapi/refreshtoken.md index a52d82f245..de14df02bd 100644 --- a/docs/accessanalyzer/11.6/admin/settings/access/restapi/refreshtoken.md +++ b/docs/accessanalyzer/11.6/admin/settings/access/restapi/refreshtoken.md @@ -11,9 +11,9 @@ refresh token when the access token expires. - `grant_type` (Required) – The `grant_type` parameter must be set to `client_credentials` - `refresh_token` (Required) – The refresh token previously issue to the client -- `scope` (Optional) – The requested scope must not include additional scopes that were not issued - in the original access token. If the scope is not included in the request, the service issues an - access token with the same scope as previously issued. +- `scope` (Optional) – The requested scope must not include additional scopes that the service + didn't issue in the original access token. If the request doesn't include a scope, the service + issues an access token with the same scope it previously issued. - Client Authentication – Required if the client was issued a secret The authentication server then verifies the access request. If the request is valid, the service @@ -30,12 +30,12 @@ grant_type=refresh_token &client_secret=xxxxxxxxxx ``` -If the token does not have the ability to perform this request, is invalid, or the specific resource -has been blocked from access remotely, an HTTP status code of 401 is returned. +If the token can't perform this request, is invalid, or the specific resource has been blocked from +access remotely, the server returns an HTTP status code of 401. -The response for a refresh token is the same as the response for an access token. Optionally, a new -refresh token can be included in the response. If a new refresh token is not included in the -response, the current refresh token will continue to be valid. The following example shows a +The response for a refresh token is the same as the response for an access token. Optionally, the +service can include a new refresh token in the response. If the response doesn't include a new +refresh token, the current refresh token remains valid. The following example shows a successful access token response: ``` diff --git a/docs/accessanalyzer/11.6/admin/settings/access/rolebased/assignroles.md b/docs/accessanalyzer/11.6/admin/settings/access/rolebased/assignroles.md index f09a26f12a..5b87e7318a 100644 --- a/docs/accessanalyzer/11.6/admin/settings/access/rolebased/assignroles.md +++ b/docs/accessanalyzer/11.6/admin/settings/access/rolebased/assignroles.md @@ -6,12 +6,12 @@ sidebar_position: 50 # Assign User to Role Members -Role Based Access becomes enabled within Enterprise Auditor as soon as the first role has been -assigned in the Access Role wizard. When saving the first role or set of roles added to the Role -Membership list in the Roles view, the Administrator role must be included for a least one user or -an error message displays. +Role Based Access becomes enabled within Enterprise Auditor as soon as you assign the first role +in the Access Role wizard. When you save the first role or set of roles added to the Role +Membership list in the Roles view, you must include the Administrator role for at least one user, +or an error message displays. -Follow the steps to assign roles in the Enterprise Auditor Console. +To assign roles in the Enterprise Auditor Console: ![Add Access option on the Access page](/images/accessanalyzer/11.6/admin/settings/access/rolebased/addaccess.webp) @@ -31,33 +31,33 @@ ellipsis (**…**) to browse for accounts with the Select User or Group window. [Group Managed Service Accounts](https://learn.microsoft.com/en-us/windows-server/security/group-managed-service-accounts/group-managed-service-accounts-overview) article for additional information. - - Change the location to the desired domain and click **Object Types**, then select **Service + - Change the location to the domain you want and click **Object Types**, then select **Service Accounts**. - Add the gMSA name (`gMSAadmin$`), then click **OK**. - The Member Type will show as `msDS-GroupManagedServiceAccount` on the Access page. ![Console Access page with user added](/images/accessanalyzer/11.6/admin/settings/access/rolebased/consoleaccessfinish.webp) -**Step 4 –** Select a role for the group or user from the Role list. Click **Finish**. The group or -user and role is added to the Role Membership list in the Roles view. +**Step 4 –** Select a role for the group or user from the Role list, and click **Finish** to add the +group or user and role to the Role Membership list in the Roles view. **Step 5 –** Repeat Steps 1-4 to assign roles to other groups or users. -**Step 6 –** Click **Save** and then **OK** to confirm the changes. All applied roles are lost if -they are not saved. +**Step 6 –** Click **Save** and then **OK** to confirm the changes. If you don't save the changes, you +lose all applied roles. -Role Based Access is enabled when the first role has been assigned. +Role Based Access becomes enabled when you assign the first role. -![Error message when Administrator role is not specified](/images/accessanalyzer/11.6/admin/settings/access/rolebased/noadminerror.webp) +![Error message when Administrator role isn't specified](/images/accessanalyzer/11.6/admin/settings/access/rolebased/noadminerror.webp) The first role or set of roles saved must include the Administrator role. Clicking **Save** for the first role or set or roles without including the Administrator generates an error message in the Enterprise Auditor Console. When Role Based Access is first enabled, restart the Enterprise Auditor application to ensure all -roles are properly active. When saving roles for the first time, permissions for the local Users -group are applied to the Enterprise Auditor directory. This allows roles to be leveraged without -requiring local Administrator rights. +roles are properly active. When you save roles for the first time, Enterprise Auditor applies +permissions for the local Users group to the Enterprise Auditor directory. This lets you use roles +without requiring local Administrator rights. | | | | ----------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -71,46 +71,46 @@ There are two separate sets of permissions: ## Edit Role Members' Responsibilities -Follow the steps to edit a Enterprise Auditor user’s role. +To edit a Enterprise Auditor user's role: ![Edit Member Role](/images/accessanalyzer/11.6/admin/settings/access/rolebased/editmemberrole.webp) -**Step 1 –** On the Access page, select the desired user and click **Edit Member Role**. +**Step 1 –** On the Access page, select the user you want and click **Edit Member Role**. ![Edit Console Access wizard page](/images/accessanalyzer/11.6/admin/settings/access/rolebased/consoleaccessedit.webp) **Step 2 –** Select a new role for the user from the Roles list. -**Step 3 –** Click **Finish**. The role is updated on the Access page. +**Step 3 –** Click **Finish** to update the role on the Access page. **Step 4 –** Repeat Steps 1-3 to edit other users’ roles. -**Step 5 –** Click **Save** and then **OK** to confirm the changes. All applied roles are lost if -they are not saved. +**Step 5 –** Click **Save** and then **OK** to confirm the changes. If you don't save the changes, you +lose all applied roles. The changed roles take affect the next time the users logs into the Enterprise Auditor application. -If a user is actively logged into Enterprise Auditor at the same time the role for that user is -changed, then the user needs to exit and re-launch the application for the role to take effect. +If a user is actively logged into Enterprise Auditor when an administrator changes that user's +role, the user needs to exit and re-launch the application for the role change to take effect. ## Delete Role Member -Follow the steps to delete a user from having access to the Enterprise Auditor Console. +To delete a user's access to the Enterprise Auditor Console: ![Delete Role Member](/images/accessanalyzer/11.6/admin/settings/access/rolebased/deleterolemember.webp) -**Step 1 –** On the Access page, select the desired user and click **Delete Role Member**. The -selected user will be removed from the list. +**Step 1 –** On the Access page, select the user you want and click **Delete Role Member** to remove +the user from the list. :::note -No confirmation will be requested. However the changes will not be finalized until Step 3 -is completed. +Enterprise Auditor doesn't request confirmation. However, the changes aren't final until you +complete Step 3. ::: **Step 2 –** Repeat Step 1 to remove other users as desired. -**Step 3 –** Click **Save** and then **OK** to confirm the deletions. The users will not be deleted -if the changes are not saved. +**Step 3 –** Click **Save** and then **OK** to confirm the deletions. Enterprise Auditor doesn't +delete the users unless you save the changes. The deleted users will no longer be able to log into the Enterprise Auditor application. If a user is actively logged into Enterprise Auditor at the same time of the deletion, the user will need to diff --git a/docs/accessanalyzer/11.6/admin/settings/access/rolebased/configureroles.md b/docs/accessanalyzer/11.6/admin/settings/access/rolebased/configureroles.md index 8d66d70fb1..a5a771f889 100644 --- a/docs/accessanalyzer/11.6/admin/settings/access/rolebased/configureroles.md +++ b/docs/accessanalyzer/11.6/admin/settings/access/rolebased/configureroles.md @@ -6,7 +6,7 @@ sidebar_position: 40 # Configuring Roles -To ensure a least privilege access model, roles need to be configured within both the Enterprise +To ensure a least-privilege access model, configure roles within both the Enterprise Auditor Console for folder rights and SQL Management Studio for database access rights. This is a three-part process: @@ -23,7 +23,7 @@ This is a three-part process: - Delete Role Members :::note -This configuration process is not required if only using Role Based Access to secure +This configuration process isn't required if only using Role Based Access to secure Published Reports. See the [Securing Published Reports Only](/docs/accessanalyzer/11.6/admin/settings/access/rolebased/securereports.md) topic for additional information. @@ -32,12 +32,12 @@ topic for additional information. ## Configure the Installation Account -The Enterprise Auditor Installation Account is used both to perform the initial installation of -Enterprise Auditor and to change Storage Profile settings. It needs additional rights in order to +Enterprise Auditor uses the Installation Account both to perform the initial installation of +Enterprise Auditor and to change Storage Profile settings. It needs additional rights to query objects in the master database. This is only necessary so the user can enumerate the available databases to choose from when configuring the Enterprise Auditor Storage Profile. -The following script can be executed to give these necessary rights only to the account performing +Run the following script to give these necessary rights only to the account that performs the initial installation of Enterprise Auditor and any changes to the database where Enterprise Auditor writes data: @@ -57,15 +57,15 @@ GO ## Configure Roles in SQL Management Studio -It is necessary to provision rights to the SQL Server database so the Enterprise Auditor application +Provision rights to the SQL Server database so the Enterprise Auditor application rights and database access rights are consistent and provide the minimum rights necessary to support -the Enterprise Auditor roles. This approach involves creating custom database roles which will be -assigned rights and privileges. Then, individual domain user accounts must be assigned to these +the Enterprise Auditor roles. This approach involves creating custom database roles and assigning +rights and privileges to them. Then, assign individual domain user accounts to these roles. :::note -For any SQL Server version prior to 2012, Windows groups cannot be used because SQL Server -does not allow the assignment of default schemas to Windows groups. Enterprise Auditor requires the +For any SQL Server version before 2012, you can't use Windows groups because SQL Server +doesn't allow assigning default schemas to Windows groups. Enterprise Auditor requires the default schema of [dbo] to function properly. ::: @@ -77,7 +77,7 @@ To create the roles within the SQL Server database, run the following script. ![Query Window](/images/accessanalyzer/11.6/admin/settings/access/rolebased/sqlcreateroles.webp) Be sure to set the context of this query to the Enterprise Auditor database by selecting the right -database from the drop-down window. Alternatively, prefix the script with a +database from the dropdown window. Alternatively, prefix the script with a `USE [Enterprise Auditor DATABASE NAME]` clause. ``` @@ -119,20 +119,20 @@ GO ``` -Once the script has been successfully executed, assign domain users to these database roles. +After the script runs successfully, assign domain users to these database roles. ### Assigning Users to SQL Roles -Now that the SQL Server database roles have been created the next step is to assign domain users to -those roles. This can be done interactively in SQL Management Studio. Follow the steps to assign -users to SQL Server database roles. +Now that you've created the SQL Server database roles, the next step is to assign domain users to +those roles. You can do this interactively in SQL Management Studio. To assign +users to SQL Server database roles: **Step 1 –** Connect to the Enterprise Auditor database through SQL Management Studio. ![Database Roles](/images/accessanalyzer/11.6/admin/settings/access/rolebased/sqldatabaseroles.webp) -**Step 2 –** Validate that the roles have been properly created by navigating to **Security** > -**Roles** > **Database Roles**. The three new roles should be visible: +**Step 2 –** Navigate to **Security** > **Roles** > **Database Roles** to confirm the script created +the three new roles. The three new roles should be visible: - SMP_Admin - SMP_Builder @@ -142,8 +142,8 @@ users to SQL Server database roles. | ----------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | | ![New User Option](/images/accessanalyzer/11.6/admin/settings/access/rolebased/sqlusers.webp) | ![New User Option](/images/accessanalyzer/11.6/admin/settings/access/rolebased/sqlusersnewuser.webp) | -**Step 3 –** After confirmation of role creation, the next step is to map users to these roles. -Right-click on the **Security** > **Users** node and select **New User**. +**Step 3 –** After you confirm the roles were created, map users to these roles by right-clicking the +**Security** > **Users** node and selecting **New User**. ![Database User Window](/images/accessanalyzer/11.6/admin/settings/access/rolebased/sqluserwindow.webp) @@ -162,5 +162,5 @@ Right-click on the **Security** > **Users** node and select **New User**. [Role Definitions](/docs/accessanalyzer/11.6/admin/settings/access/rolebased/roledefinitions.md) topic for more information. -When all of the users have been assigned to the appropriate SQL Server database roles, complete the +After you assign all users to the appropriate SQL Server database roles, complete the process by assigning users to roles within the Enterprise Auditor Console. diff --git a/docs/accessanalyzer/11.6/admin/settings/access/rolebased/customroles.md b/docs/accessanalyzer/11.6/admin/settings/access/rolebased/customroles.md index e971771900..19e9578e3b 100644 --- a/docs/accessanalyzer/11.6/admin/settings/access/rolebased/customroles.md +++ b/docs/accessanalyzer/11.6/admin/settings/access/rolebased/customroles.md @@ -6,11 +6,11 @@ sidebar_position: 20 # Custom Roles -A custom role can be created within Enterprise Auditor to combine the rights of other defined roles. -Follow the steps below to create a custom role. +You can create a custom role within Enterprise Auditor to combine the rights of other defined roles. +Follow these steps to create a custom role. **Step 1 –** In the Enterprise Auditor directory, navigate to **PrivateAssemblies** and edit the -**rba-roles.conf** file.  Add a new section for the custom role as shown in the following +**rba-roles.conf** file. Add a new section for the custom role as shown in the following instructions: ``` @@ -23,25 +23,25 @@ instructions: ``` -- Replace `Special User` between the double quotes in the script above with the name of the new +- Replace `Special User` between the double quotes with the name of the new role. -- Replace `Description of Special User` between the double quotes in the script above with a - description of what a user assigned the new role is able to do. +- Replace `Description of Special User` between the double quotes with a + description of what a user assigned the new role can do. -**Step 2 –** Add privileged values for the desired rights on new lines between the beginning comment -`` and ending comment `` in the script above. +**Step 2 –** Add privileged values for the rights you want on new lines between the beginning comment +`` and ending comment ``. - For example, to create a single role which has the same privileges as the Host Management Administrator and Global Options Administrator roles, copy the privileges from the sections of the **rba-roles.conf** file to the newly added section, and remove duplicate values if there is any overlap. -See the sections below for examples of how roles should be added in the **rba-roles.conf** file. +See the following sections for examples of how to add roles in the **rba-roles.conf** file. ## Default Global Options Administrator Privileges -The following example shows what is currently contained in the Global Options Administrator role, -and how the created role should be added in the **rba-roles.conf** file. +The following example shows what the Global Options Administrator role contains and how to add the +created role in the **rba-roles.conf** file. ``` @@ -85,8 +85,8 @@ and how the created role should be added in the **rba-roles.conf** file. ## Default Host Management Administrator Privileges -The following example shows what is currently contained in the Host Management Administrator role, -and how the created role should be added in the **rba-roles.conf** file. +The following example shows what the Host Management Administrator role contains and how to add the +created role in the **rba-roles.conf** file. ``` diff --git a/docs/accessanalyzer/11.6/admin/settings/access/rolebased/faq.md b/docs/accessanalyzer/11.6/admin/settings/access/rolebased/faq.md index de92a9199f..5e05b9623a 100644 --- a/docs/accessanalyzer/11.6/admin/settings/access/rolebased/faq.md +++ b/docs/accessanalyzer/11.6/admin/settings/access/rolebased/faq.md @@ -11,24 +11,25 @@ Auditor. **How do locked jobs affect the role functionality?** -A lock on a job represents the approval by the Job Approver, and is therefore deemed acceptable to +A lock on a job represents the Job Approver's approval and therefore makes the job acceptable to execute. Once a job is locked, Job Builders can no longer modify the job configuration. Furthermore, -only locked jobs can be run. Therefore, the Job Initiator can only run or schedule jobs which have -already been locked. +Enterprise Auditor allows only locked jobs to run. Therefore, the Job Initiator can only run or +schedule jobs that have already been locked. :::note -Locked jobs do not affect the functionality of the Administrator role. See the +Locked jobs don't affect the functionality of the Administrator role. See the [Role Definitions](/docs/accessanalyzer/11.6/admin/settings/access/rolebased/roledefinitions.md) topic for more information. ::: -How can I make sure that a lock on a job will not get tampered with through the associated XML file? +How can you ensure that a lock on a job isn't tampered with through the associated XML file? The Scheduling Service Account provides limited rights for the Job Approver. Previously, the Job -Approver required permissions on the Jobs folder in order to apply the lock to a job. Now, the -credentials specified in the Scheduling Service Account will be used to apply the locks. Therefore, -the Job Approver no longer needs access to the Jobs folder and cannot manually remove or tamper with +Approver required permissions on the Jobs folder to apply the lock to a job. Now, +Enterprise Auditor uses the credentials specified in the Scheduling Service Account to apply the +locks. Therefore, +the Job Approver no longer needs access to the Jobs folder and can't manually remove or tamper with the associated XML file. :::note @@ -44,31 +45,31 @@ topics for more information. Why can the Host Management Administrator not manage settings for the Host Discovery and Host Inventory nodes under Settings? -The Host Management Administrator role is designed specifically to access the Host Management node. -Therefore, this role does not grant access to the global settings menu under the Settings node. +The Host Management Administrator role provides access only to the Host Management node. +Therefore, this role doesn't grant access to the global settings menu under the Settings node. :::note -In order to access this node, the user must have either the Administrator or the Global +to access this node, the user must have either the Administrator or the Global Options Administrator role. See the [Role Definitions](/docs/accessanalyzer/11.6/admin/settings/access/rolebased/roledefinitions.md) topic for more information. ::: -What rights do I need to give the user on the local machine in order to use Enterprise Auditor? +What rights do you need to give the user on the local machine to use Enterprise Auditor? Enabling Role Based Access removes the necessity to explicitly provide users rights on the Enterprise Auditor folder structure. Instead, when the Administrator role is first assigned and Role Based Access is enabled, the roles will set permissions to allow all members of the local users group the necessary access to Enterprise Auditor. -When a user’s role is changed, when does the new role take affect? +When an administrator changes a user's role, when does the new role take effect? -If a user’s role has been altered while they are in an active Enterprise Auditor session, the user -must exit the Enterprise Auditor Console and re-open the application for the new role to take -effect. This is also true if a user has been given an additional role or removed from role -membership. The capabilities of the new role will not come into effect until the Enterprise Auditor -application has been restarted. +If an administrator has altered a user's role while the user is in an active Enterprise Auditor +session, the user must exit the Enterprise Auditor Console and re-open the application for the new +role to take effect. This is also true if an administrator has given a user an additional role or +removed the user from role membership. The capabilities of the new role don't come into effect +until the user restarts the Enterprise Auditor application. :::note See the @@ -79,14 +80,14 @@ topics for more information. ::: -I locked a job, but when going back to it, it appears to be unlocked. Why? +A job was locked, but it appears unlocked when you go back to it. Why? -A locked job signifies that the job has been approved for execution and should not be modified. If a -job is modified in any way, the lock is immediately removed. Although most roles should not be able -to modify locked jobs, the Administrator role can. This role is not governed by the limitations of -Role Based Access. Thus, if a locked job is modified by an Administrator, the job will become -unlocked. This event will be logged as a job-change related event by Administrator in the Enterprise -Auditor Event Log. +A locked job signifies that the Job Approver has approved the job for execution and that you +shouldn't modify it. If you modify a job in any way, Enterprise Auditor immediately removes the +lock. Although most roles shouldn't be able to modify locked jobs, the Administrator role can. This +role isn't governed by the limitations of Role Based Access. Thus, if an Administrator modifies a +locked job, the job becomes unlocked. Enterprise Auditor logs this event as a job-change-related +event performed by the Administrator in the Enterprise Auditor Event Log. :::note If using a Job Initiator’s credentials for the Schedule Service Account, all jobs must be @@ -102,13 +103,12 @@ topics for more information. What should be the group type when assigning Role Based Access to an AD group in a multi-domain environment? -When assigning an Role Based Access to an AD group, it is important to consider the domain +When assigning Role Based Access to an AD group, consider the domain relationship between the AD group and the Enterprise Auditor server. If the Enterprise Auditor server and the AD group are in different domains then the AD group must be -a universal group. If the group type is not universal then it will result in the RBA being unable to -access the user's group membership and the user who is a member of that AD group will be unable to -view any reports. +a universal group. If the group type isn't universal, Role Based Access can't access the user's +group membership, and the user in that AD group can't view any reports. However, if both the Enterprise Auditor server and the AD group are in the same domain, the AD group can be either a local group, global group, or universal group. diff --git a/docs/accessanalyzer/11.6/admin/settings/access/rolebased/overview.md b/docs/accessanalyzer/11.6/admin/settings/access/rolebased/overview.md index 08533e3f5a..31c05a8f41 100644 --- a/docs/accessanalyzer/11.6/admin/settings/access/rolebased/overview.md +++ b/docs/accessanalyzer/11.6/admin/settings/access/rolebased/overview.md @@ -6,45 +6,45 @@ sidebar_position: 10 # Role Based Access -Role Based Access allows Enterprise Auditor users to not have local Administrator rights on the -console server. This is done through the creation of different roles which cover all aspects of the -Enterprise Auditor work flow introduced by enabling Role Based Access. These roles can be leveraged -without such elevated rights. Responsibilities within the Enterprise Auditor Console have been -divided among these roles. - -Role Based Access also allows users to secure published reports when accessed through the Web -Console. This is done by first enabling Role Based Access and then by assigning users/groups as -viewers to the reports to which they should have access. - -Report security through Role Based Access can be applied without implementing a least privileged -access model to the Enterprise Auditor Console. See the +With Role Based Access, Enterprise Auditor users don't need local Administrator rights on the +console server. Enterprise Auditor achieves this by creating different roles that cover all aspects +of the Enterprise Auditor workflow introduced by enabling Role Based Access. You can use these roles +without such elevated rights. These roles divide responsibilities within the Enterprise Auditor +Console. + +Role Based Access also secures published reports when accessed through the Web +Console. To do this, first enable Role Based Access, then assign users or groups as viewers to the +reports they should access. + +You can apply report security through Role Based Access without implementing a least-privileged +access model for the Enterprise Auditor Console. See the [Securing Published Reports Only](/docs/accessanalyzer/11.6/admin/settings/access/rolebased/securereports.md) topic for additional information. :::note -The least privileged access model to the Enterprise Auditor Console does not work in -conjunction with the Exchange Solution. Role Based Access can be enabled, but the Administrator role -is required to run the Exchange Solution jobs. +The least-privileged access model to the Enterprise Auditor Console doesn't work with the Exchange +Solution. You can enable Role Based Access, but running the Exchange Solution jobs requires the +Administrator role. ::: :::warning -Please use caution when enabling Role Based Access, as it is a very powerful tool -within the console designed to be difficult to disable once activated. If Role Based Access is -enabled by accident, please contact [Netwrix Support](https://www.netwrix.com/support.html) for -assistance in disabling it. +Use caution when enabling Role Based Access, as it's a very powerful tool +within the console that's difficult to disable once activated. If you enable Role Based Access +by accident, contact [Netwrix Support](https://www.netwrix.com/support.html) for +help disabling it. ::: The account used to perform the initial Enterprise Auditor installation, as well as to change -Storage Profile settings after installation, require additional rights in order to query objects in +Storage Profile settings after installation, require additional rights to query objects in the master database. See the [Configure the Installation Account](/docs/accessanalyzer/11.6/admin/settings/access/rolebased/configureroles.md#configure-the-installation-account) topic for additional information on this account. -To enable Role Based Access within Enterprise Auditor, corresponding roles must first be created -within SQL Management Studio. Then Enterprise Auditor users must be assigned roles both in SQL -Management Studio and in Enterprise Auditor. +To enable Role Based Access within Enterprise Auditor, first create the corresponding roles within +SQL Management Studio. Then assign roles to Enterprise Auditor users both in SQL Management Studio +and in Enterprise Auditor. The first Enterprise Auditor user assigned a role must be an Administrator. Assigning this first user role officially enables Role Based Access within Enterprise Auditor. See the diff --git a/docs/accessanalyzer/11.6/admin/settings/access/rolebased/roledefinitions.md b/docs/accessanalyzer/11.6/admin/settings/access/rolebased/roledefinitions.md index dd80a902ff..164ed134d6 100644 --- a/docs/accessanalyzer/11.6/admin/settings/access/rolebased/roledefinitions.md +++ b/docs/accessanalyzer/11.6/admin/settings/access/rolebased/roledefinitions.md @@ -6,19 +6,20 @@ sidebar_position: 10 # Role Definitions -The following is a list of all roles leveraged within Enterprise Auditor once Role Based Access is +The following is a list of all roles used within Enterprise Auditor once Role Based Access is enabled, including their intended functionality. A user may have more than one role assigned to them. :::note -When a job is moved or copied to a separate job group, it inherits the assigned roles at -the parent and global level from the new job group. Any previous role inheritance is overwritten. +When you move or copy a job to a separate job group, it inherits the assigned roles at +the parent and global level from the new job group. Enterprise Auditor overwrites any previous +role inheritance. ::: - OS Administrator – Used only for installation purposes - - This is not not a configured role, but rather the access required during installation + - This isn't not a configured role, but rather the access required during installation - Administrator – At least one must be set before any other roles are assigned @@ -27,8 +28,8 @@ the parent and global level from the new job group. Any previous role inheritanc - Rights to preform an upgrade on Enterprise Auditor :::note -In order to use Role Base Access with the Exchange Solution, all Exchange users must be -assigned the Administrator role. This is because the solution requires local Administrator rights on +To use Role Based Access with the Exchange Solution, assign the Administrator role to all Exchange +users. This is necessary because the solution requires local Administrator rights on the Enterprise Auditor Console server. ::: @@ -58,7 +59,7 @@ the Enterprise Auditor Console server. - Global Options Administrator - Able to modify global settings, except for the **Setting** > **Access** node - - The Exchange node is the exception due to its requirements. Therefore, this node cannot be + - The Exchange node is the exception due to its requirements. Therefore, this node can't be modified by the Global Options Administrator. - Rights to view report Tags within the Web Console but not report content or permissions @@ -120,8 +121,8 @@ the Enterprise Auditor Console server. **Configure** > **Reports**> **Configure** > **Publish Security** page) – Able to view only this report -By default, many roles are granted rights to view all reports and report content. The inheritance of -the Report Viewer role can be broken at the job group, job, or report configuration levels. See the +By default, many roles have rights to view all reports and report content. You can break the Report +Viewer role's inheritance at the job group, job, or report configuration levels. See the [Report Viewer Inheritance](#report-viewer-inheritance) topic for additional information. ## Enterprise Auditor Console Roles & Rights @@ -194,15 +195,15 @@ This table identifies the rights granted to users who have access only to the We ## SQL Server Database Roles & Rights -This table describes the roles that will be created within the SQL Server database and what rights -they will have to the Enterprise Auditor database. It also describes which Enterprise Auditor roles -they are mapped to. +This table describes the roles that you'll create within the SQL Server database and what rights +they'll have to the Enterprise Auditor database. It also describes which Enterprise Auditor roles +map to them. -| Database Role(s) | Enterprise Auditor Role | Rights | Role Description | +| Database Roles | Enterprise Auditor Role | Rights | Role Description | | --------------------------------------------- | ------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | SMP Administrator db_datareader db_datawriter | Administrator Job Initiator Job Initiator (No Actions) | On the dbo schema: ALTER, EXECUTE, INSERT, UPDATE, REFERENCES On the Enterprise Auditor database: CREATE TABLE, CREATE VIEW, CREATE PROCEDURE, CREATE FUNCTION, CREATE TYPE | This role is used by full Administrators and Job Initiators who must run the 2-FSAA Bulk Import Job which requires manipulation of the Enterprise Auditor database | | SMP Builder | Job Builder Host Management Administrator | On the dbo schema: ELECT, INSERT, DELETE On the Enterprise Auditor database: CREATE TABLE | This role is used by the Job Builder who must be able to create/delete tables, view data, and insert and delete hosts from the Enterprise Auditor Console | -| SMP Viewer | Job Viewer Access Administrator Job Approver All other roles | On the dbo schema: SELECT | This role is used by all roles who do not require anything more than just reading data and information from the database | +| SMP Viewer | Job Viewer Access Administrator Job Approver All other roles | On the dbo schema: SELECT | This role is used by all roles who don't require anything more than just reading data and information from the database | ## Report Viewer Inheritance @@ -218,9 +219,9 @@ reports and their content: - Job Viewer - Web Administrator -Additional users can be assigned the Report Viewer role at the global, job group, job, or report -configuration levels. These rights are inherited down through child objects. However, the Report -Viewer role inheritance can be broken at any level. Break inheritance to remove the right to view +You can assign additional users the Report Viewer role at the global, job group, job, or report +configuration levels. Child objects inherit these rights. However, you can break the Report +Viewer role's inheritance at any level. Break inheritance to remove the right to view specific reports at: - Job Group level – **[Job Group]** >**Settings** > **Reporting** node @@ -241,5 +242,5 @@ There are two options that control inheritance for Report Viewers when selected: Viewer role inherited from a parent object at the lower levels - Set all the child objects to inherit these settings – Only available at the Job Group level. Sets all Jobs and Reports to inherit group settings for all child objects by automatically selecting - the **Include Report Viewers from this object’s parent** option. Any previous configurations are - overwritten once **Yes** is selected in the confirmation window. + the **Include Report Viewers from this object’s parent** option. The system overwrites any + previous configurations once you select **Yes** in the confirmation window. diff --git a/docs/accessanalyzer/11.6/admin/settings/access/rolebased/scheduleserviceaccount.md b/docs/accessanalyzer/11.6/admin/settings/access/rolebased/scheduleserviceaccount.md index 2f44f82dc7..5889a53bc7 100644 --- a/docs/accessanalyzer/11.6/admin/settings/access/rolebased/scheduleserviceaccount.md +++ b/docs/accessanalyzer/11.6/admin/settings/access/rolebased/scheduleserviceaccount.md @@ -6,8 +6,8 @@ sidebar_position: 30 # Roles & the Schedule Service Account -Once Role-Based Access is enabled, a user or group with the appropriate access role has the ability -to schedule a job or job group as a Schedule Service Account at the **Settings** > **Schedule** +Once Role-Based Access is enabled, a user or group with the appropriate access role can schedule +a job or job group as a Schedule Service Account at the **Settings** > **Schedule** node. Multiple accounts can be added as needed. **Who Configures This Account?** @@ -25,18 +25,18 @@ Whose Credentials Should Be Used as the Schedule Service Account? - Job Initiator role :::note -In order to run or schedule a Host Inventory query, the Schedule Service Account must have +to run or schedule a Host Inventory query, the Schedule Service Account must have an Administrator, Power User, or Host Management Administrator role. Therefore, if the account has the Job Initiator role assigned, it must have the Host Management Administrator role as well. ::: -The Schedule Service Account is used to access the Task folders when scheduling tasks and to apply -locks on jobs. +Enterprise Auditor uses the Schedule Service Account to access the Task folders when scheduling +tasks and to apply locks on jobs. - Schedule Tasks - - In order to have the appropriate level of rights to schedule tasks, the credentials specified + - to have the appropriate level of rights to schedule tasks, the credentials specified must at least have the following: - Create Files/Write Data rights on the Windows Task Folder @@ -44,7 +44,7 @@ locks on jobs. - Otherwise, they should have local Administrator privileges on the Enterprise Auditor Console server - - The user whose credentials are specified must also have a role that allows the scheduling of + - The user whose credentials are specified must also have a role that allows scheduling tasks – Administrator, Power User, or Job Initiator - Apply Locks @@ -55,19 +55,19 @@ locks on jobs. ::: - - These credentials are used to apply locks on jobs, enabling the Job Approver to have fewer - rights on the Jobs directory. Therefore, the credentials specified must at least have the - following: + - Enterprise Auditor uses these credentials to apply locks on jobs, so the Job Approver needs + fewer rights on the Jobs directory. Therefore, the credentials specified must at least have + the following: - Modify rights on this directory - Otherwise, these credentials should have local Administrator privileges on the Enterprise Auditor Console server - - The Job Approver uses these credentials to apply locks. Therefore, the Job Approver must be - added to the local policy **Impersonate a client after Authentication**. + - The Job Approver uses these credentials to apply locks. Therefore, add the Job Approver to + the local policy **Impersonate a client after Authentication**. -Do not choose the **Use local System account to schedule tasks** option. This account does not have -the appropriate rights to apply locks on jobs. Therefore, it does not work in conjunction with Role +Don't choose the **Use local System account to schedule tasks** option. This account doesn't have +the appropriate rights to apply locks on jobs. Therefore, it doesn't work with Role Based Access. See the diff --git a/docs/accessanalyzer/11.6/admin/settings/access/rolebased/securereports.md b/docs/accessanalyzer/11.6/admin/settings/access/rolebased/securereports.md index 6cded2f9a2..3d11630e8b 100644 --- a/docs/accessanalyzer/11.6/admin/settings/access/rolebased/securereports.md +++ b/docs/accessanalyzer/11.6/admin/settings/access/rolebased/securereports.md @@ -6,9 +6,9 @@ sidebar_position: 60 # Securing Published Reports Only -In order to secure published reports through the Web Console, it is necessary to enable Role Based -Access within the Enterprise Auditor Console. If that is the only reason the Role Based Access -feature is being enabled, ensure the following requirements are met: +To secure published reports through the Web Console, enable Role Based +Access within the Enterprise Auditor Console. If that's the only reason you're enabling the Role +Based Access feature, ensure you meet the following requirements: - Administrator role assigned to all Enterprise Auditor Console users @@ -25,7 +25,7 @@ feature is being enabled, ensure the following requirements are met: - Job Level Assignment – Access to reports published by the job - Report Configuration Level Assignment – Access to the specific report -Follow the steps to assign roles at the global level. +To assign roles at the global level: **Step 1 –** Navigate to the **Settings** > **Access** node. @@ -44,8 +44,8 @@ ellipsis (**…**) to browse for accounts with the Select User or Group window. ![Console Access page with user added](/images/accessanalyzer/11.6/admin/settings/access/rolebased/consoleaccessfinish.webp) -**Step 5 –** Select a role for the group or user from the Role list. Click **Finish**. The group or -user and role is added to the Role Membership list in the Roles view. +**Step 5 –** Select a role for the group or user from the Role list, and click **Finish** to add the +group or user and role to the Role Membership list in the Roles view. :::warning The first role or set of roles saved must include the Administrator role. Clicking Save @@ -57,19 +57,19 @@ the Enterprise Auditor Console. **Step 6 –** Repeat Steps 2-4 to assign the Administrator, Web Administrator, and Report Viewer roles to other groups or users. -**Step 7 –** Click **Save** and then **OK** to confirm the changes. All applied roles are lost if -they are not saved. +**Step 7 –** Click **Save** and then **OK** to confirm the changes. If you don't save the changes, +you lose all applied roles. -Role Based Access is enabled when the first role has been assigned. +Role Based Access becomes enabled when you assign the first role. -![Error message when Administrator role is not specified](/images/accessanalyzer/11.6/admin/settings/access/rolebased/noadminerror.webp) +![Error message when Administrator role isn't specified](/images/accessanalyzer/11.6/admin/settings/access/rolebased/noadminerror.webp) The first role or set of roles saved must include the Administrator role. Clicking **Save** for the first role or set or roles without including the Administrator generates an error message in the Enterprise Auditor Console. When Role Based Access is first enabled, restart the Enterprise Auditor application to ensure all -roles are properly active. The Report Viewer role can be assigned at the job group, job, and report +roles are properly active. You can assign the Report Viewer role at the job group, job, and report configuration levels. See the [Reporting Node](/docs/accessanalyzer/11.6/admin/jobs/group/settings/reporting.md), [Report Roles Tab](/docs/accessanalyzer/11.6/admin/jobs/job/properties/reportroles.md), diff --git a/docs/accessanalyzer/11.6/admin/settings/access/rolebased/workflow.md b/docs/accessanalyzer/11.6/admin/settings/access/rolebased/workflow.md index 670df1d19e..ac8f8d32cc 100644 --- a/docs/accessanalyzer/11.6/admin/settings/access/rolebased/workflow.md +++ b/docs/accessanalyzer/11.6/admin/settings/access/rolebased/workflow.md @@ -16,11 +16,11 @@ rejects it ![Lock Job option in right-click menu](/images/accessanalyzer/11.6/admin/settings/access/rolebased/lockjob.webp) -- If a job is approved, then a lock needs to be applied by right-clicking the job title in the Jobs +- If a job is approved, apply a lock by right-clicking the job title in the Jobs tree and selecting **Lock Job** - If a job is rejected, then the job remains unlocked - If the **Lock Job** option is visible, then the job has not yet been approved -- If the **Lock Job** option is not visible, then the job has been approved +- If the **Lock Job** option isn't visible, then the job has been approved ![Unlock Job option in right-click menu](/images/accessanalyzer/11.6/admin/settings/access/rolebased/unlockjob.webp) @@ -32,9 +32,9 @@ approved by the grayed-out **Unlock Job** option in the right-click menu. - For the Job Initiator (No Actions) role, the user is unable to execute a job which contains configured actions, even if it is approved and locked - - Both roles can enable and disable job groups and jobs regardless of whether or not they are - locked. Disabled jobs are grayed out with a red x next to it and are not executed with the job - group. When applied at the job group level, all nested jobs are disabled and do not run. + - Both roles can enable and disable job groups and jobs regardless of whether they are + locked. Disabled jobs are grayed out with a red x next to it and aren't executed with the job + group. When applied at the job group level, all nested jobs are disabled and don't run. However, any new job added to that group is enabled by default. :::note @@ -50,8 +50,8 @@ approved by the grayed-out **Unlock Job** option in the right-click menu. ![Report under the Results Node in the Jobs Tree](/images/accessanalyzer/11.6/admin/settings/access/rolebased/reportjobstree.webp) -**Step 4 –** After a job has been successfully run, the **Job Viewer** can now view the results of -the job under the job’s Status and Results node, or in the Web Console. See the +**Step 4 –** After the Job Initiator successfully runs a job, the **Job Viewer** can view the +results of the job under the job’s Status and Results node, or in the Web Console. See the [Viewing Generated Reports](/docs/accessanalyzer/11.6/admin/report/view.md) topic for additional information. @@ -64,10 +64,10 @@ Console. ## Other Console Roles -Any modifications needed in the Settings or Host Management nodes must be done by the corresponding -administrator role (Global Options Administrator, Access Administrator, or Host Management -Administrator). These roles can be used in conjunction with any other role (for example, a user can -be a Job Builder and Global Options Administrator in order to build jobs and manage corresponding +The corresponding administrator role (Global Options Administrator, Access Administrator, or Host +Management Administrator) must make any modifications needed in the Settings or Host Management +nodes. You can combine these roles with any other role (for example, a user can +be a Job Builder and Global Options Administrator to build jobs and manage corresponding Connection Profiles). ### Web Administrator diff --git a/docs/accessanalyzer/11.6/admin/settings/application/overview.md b/docs/accessanalyzer/11.6/admin/settings/application/overview.md index dafde901ff..e90e06d388 100644 --- a/docs/accessanalyzer/11.6/admin/settings/application/overview.md +++ b/docs/accessanalyzer/11.6/admin/settings/application/overview.md @@ -19,9 +19,9 @@ Enterprise Auditor application log. ![Application Log](/images/accessanalyzer/11.6/admin/settings/application/applicationlog.webp) The Application log level controls the types of messages generated for each job and the application. -It can be modified at the job level in the **Job Properties** window. See the +You can modify it at the job level in the **Job Properties** window. See the [General Tab](/docs/accessanalyzer/11.6/admin/jobs/job/properties/general.md) -topic for additional information. Options available in the Application log level drop-down menu +topic for additional information. Options available in the Application log level dropdown menu include: - Debug – Records everything that happens during job execution, most verbose level of logging @@ -52,9 +52,9 @@ Set the log level to **Warning**. ::: -The other log levels are designed to assist with troubleshooting job execution issues. The Debug -level is only recommended when experiencing problems. After the problem is fixed or the Application -log has been sent to [Netwrix Support](https://www.netwrix.com/support.html), reduce the logging +The other log levels help with troubleshooting job execution issues. Use the Debug +level only when you're experiencing problems. After you fix the problem or send the Application +log to [Netwrix Support](https://www.netwrix.com/support.html), reduce the logging level to **Warning** or **Info**. **Profile Security** @@ -64,32 +64,32 @@ various credentials stored by the Enterprise Auditor application. ![Profile Security](/images/accessanalyzer/11.6/admin/settings/application/profilesecurity.webp). -There are two options available in the Profiles stored with drop-down menu: +There are two options available in the Profiles stored with dropdown menu: -- Application – Default setting, does not employ the enhanced encryption +- Application – Default setting, doesn't employ the enhanced encryption - Vault – Enables the enhanced encryption of stored credentials. See the [Vault](/docs/accessanalyzer/11.6/admin/settings/application/vault.md) topic for requirements and additional information. **Usage Statistics** -The Usage Statistics section allows you to select whether to send usage statistics data to Netwrix -to help us improve our product. +Use the Usage Statistics section to select whether to send usage statistics data to Netwrix +to help improve the product. ![Usage Statistics](/images/accessanalyzer/11.6/admin/settings/application/usagestatistics.webp) -- If selected, usage statistics are collected and sent to Netwrix +- If you select this option, Enterprise Auditor collects and sends usage statistics to Netwrix - - Upon startup of the Enterprise Auditor console, the system checks if usage statistics have - been sent in the last 7 days. If they have not been, stored procedures run against the + - Upon startup of the Enterprise Auditor console, the system checks whether it has sent usage + statistics in the last 7 days. If it hasn't, stored procedures run against the Enterprise Auditor database and gather data about job runs, access times, and environmental - details like resource counts, users counts, number of exceptions, and so on. This data is then - sent back to Netwrix to help us identify usage trends and common pain points, so that we can - use this information to improve the product. - - Only anonymous statistic-level data is included. No private company or personal data is - collected or sent to Netwrix. + details like resource counts, users counts, number of exceptions, and so on. Enterprise + Auditor then sends this data back to Netwrix to help identify usage trends and common problem + areas, which Netwrix uses to improve the product. + - Enterprise Auditor includes only anonymous statistic-level data and doesn't collect or send + private company or personal data to Netwrix. -- If cleared, no usage statistics are collected or sent to Netwrix +- If you clear this option, Enterprise Auditor doesn't collect or send usage statistics to Netwrix **Host Target Options** @@ -113,7 +113,7 @@ Console. - Automatically rename duplicate columns within a table – Checks for and renames columns with duplicate names - Automatically correct invalid column names – Checks for and corrects column names which contain - characters SQL cannot handle + characters SQL can't handle :::info Leave both options selected. @@ -121,16 +121,16 @@ Console. - Save filters and grouping on data grids – Maintains filters configured for a data grid for the - next viewing. If not selected, filtered data grids reset between viewings. + next viewing. If you don't select this option, filtered data grids reset between viewings. - Maximum row count for interactive grid view – Indicates the number of rows displayed in tables accessible in under a job’s Status and Results nodes - - Maximum row count is set to 1000 by default and has a cap of 99,999 rows. This number does not + - The default maximum row count is 1000, with a cap of 99,999 rows. This number doesn't impact the number of rows within the SQL database. To view the full row count for a table exceeding this size, use the SQL Server Management Studio or another SQL Server interface tool which displays the full table. -Filtered data grids are not lost if persistent filters are not saved. The Filtration Dialog +You keep filtered data grids only if you save persistent filters. The Filtration Dialog available for every data grid maintains a list of recent filters. See the [Data Grid Functionality](/docs/accessanalyzer/11.6/admin/navigate/datagrid.md) topic for additional information. @@ -142,38 +142,39 @@ when the database is configured to use Simple Recovery Model. ![Cleanup Options](/images/accessanalyzer/11.6/admin/settings/application/cleanup.webp) -- Compact Database Transaction Log – If selected, every time the Enterprise Auditor application is - closed, the Database Transaction Log is compacted +- Compact Database Transaction Log – If you select this option, Enterprise Auditor compacts the + Database Transaction Log every time you close the application :::info - In most environments, it is recommended to leave this option selected. If a + In most environments, leave this option selected. If a scheduled task ends while multiple tasks are still running, the process of compacting the database freezes it and causes the running tasks to fail. ::: -- Run Post Processing SQL Script to Set Host Status – If selected, this option ascribes the values - of SUCCESS, WARNING, or ERROR to indicate what happened on that host during job execution +- Run Post Processing SQL Script to Set Host Status – If you select this option, Enterprise Auditor + ascribes the values of SUCCESS, WARNING, or ERROR to indicate what happened on that host during + job execution :::info - It is recommended that this option be left selected. + Leave this option selected. ::: **Application Exit Options** -The Application Exit Options section controls whether or not a confirmation is displayed when the -Enterprise Auditor application is closed. +The Application Exit Options section controls whether Enterprise Auditor displays a confirmation +when you close the application. ![Application Exit Options](/images/accessanalyzer/11.6/admin/settings/application/applicationexitoptions.webp) -If selected, the **Show Confirmation Dialog** option causes a Confirm Exit window to open when the -Enterprise Auditor user attempts to exit the application. If deselected, the Enterprise Auditor -application closes without confirmation. +If you select the **Show Confirmation Dialog** option, a Confirm Exit window opens when the +Enterprise Auditor user attempts to exit the application. If you don't select this option, the +Enterprise Auditor application closes without confirmation. ![Confirm Exit](/images/accessanalyzer/11.6/admin/settings/application/confirmexitwindow.webp) -The Confirm Exit window requires the **Yes** button to be clicked before the Enterprise Auditor +The Confirm Exit window requires you to click **Yes** before the Enterprise Auditor application closes. The **Cancel** and **Save** buttons are in the lower-right corner of the Application view. These diff --git a/docs/accessanalyzer/11.6/admin/settings/application/vault.md b/docs/accessanalyzer/11.6/admin/settings/application/vault.md index 8be77691a5..cc52c7a0f0 100644 --- a/docs/accessanalyzer/11.6/admin/settings/application/vault.md +++ b/docs/accessanalyzer/11.6/admin/settings/application/vault.md @@ -8,25 +8,24 @@ sidebar_position: 10 The Enterprise Auditor vault provides additional security through enhanced encryption to various credentials stored by the Enterprise Auditor application, such as Connection Profile credentials or -Schedule Service Account credentials. In order to enable the vault, the following prerequisites must -be met in the order listed: +Schedule Service Account credentials. To enable the vault, meet the following prerequisites in the order listed: - Enterprise Auditor Vault Service must be running - This service was installed during the Enterprise Auditor installation and is configured for Manual Startup Type - - It needs to be configured to Log On (Service > Properties) with a service account which has + - Configure it to Log On (Service > Properties) with a service account that has Log on as Service rights, as well as Read and Execute rights to the VaultService.exe file located within the Enterprise Auditor installation directory - Role Base Access must be enabled within Enterprise Auditor - - The vault was designed to provide enhanced security when employing the Role Based Access, or - least privilege, option of Enterprise Auditor - - At least one Administrator role must be assigned to enable the vault: + - The vault provides enhanced security when you employ the Role Based Access, or + least-privilege, option of Enterprise Auditor + - Assign at least one Administrator role to enable the vault: - - If full Role Based Access is not desired but enabling the vault is, all of the Enterprise - Auditor users should be given the Administrator role + - If you don't want full Role Based Access but do want to enable the vault, give all + Enterprise Auditor users the Administrator role - No additional Role Based Access prerequisites are required for this option - See the @@ -34,9 +33,9 @@ be met in the order listed: topic for additional information on Role Based Access :::note - Once the vault has been enabled, it is not possible to disable Role Based Access - without first disabling the vault. Please contact - [Netwrix Support](https://www.netwrix.com/support.html) for assistance in disabling Role Based + After you enable the vault, you can't disable Role Based Access + without first disabling the vault. Contact + [Netwrix Support](https://www.netwrix.com/support.html) for help disabling Role Based Access. ::: @@ -45,20 +44,20 @@ be met in the order listed: ![Vault Security](/images/accessanalyzer/11.6/admin/settings/application/vaultrbaerror.webp) - If the previous prerequisites have not been met, then one of the following errors will occur - when attempting to save the Vault Profile Security setting: + If you haven't met the previous prerequisites, one of the following errors occurs + when you try to save the Vault Profile Security setting: - - Role Based Access Error – Role Based Access must be configured in order to use the Enterprise - Auditor Vault. Please configure Role Based Access and try again - - Enterprise Auditor Vault Service Error – Enterprise Auditor is not running + - Role Based Access Error – Configure Role Based Access to use the Enterprise + Auditor Vault, and try again + - Enterprise Auditor Vault Service Error – Enterprise Auditor isn't running - The Netwrix Enterprise Auditor Web Server service must be run with an account that has the Administrator role assigned - - If the Administrator role is not assigned, the vault service does not allow the web server to + - If the Administrator role isn't assigned, the vault service doesn't allow the web server to access the SQL profile and throws an access denied error in the web server log file -The credentials which are encrypted once the vault has been enabled are: +After you enable the vault, Enterprise Auditor encrypts the following credentials: - Storage Profile credentials - Connection Profile credentials @@ -66,12 +65,13 @@ The credentials which are encrypted once the vault has been enabled are: - Role Definitions - Role Assignments -Once encrypted, the files with these stored credentials are moved into a new directory location. +Enterprise Auditor moves the encrypted files with these stored credentials into a new directory +location. -This location is protected by the service account used to run the Enterprise Auditor Vault Service. +The service account used to run the Enterprise Auditor Vault Service protects this location. ## Disabling the Vault To disable the vault, navigate to the **Settings** > **Application** node and change the Profile -Security section setting to **Application**. It is a best practice to also stop the Enterprise +Security section setting to **Application**. As a best practice, also stop the Enterprise Auditor Vault Service. diff --git a/docs/accessanalyzer/11.6/admin/settings/connection/create/activedirectory.md b/docs/accessanalyzer/11.6/admin/settings/connection/create/activedirectory.md index cc3df597c9..8fd402fa55 100644 --- a/docs/accessanalyzer/11.6/admin/settings/connection/create/activedirectory.md +++ b/docs/accessanalyzer/11.6/admin/settings/connection/create/activedirectory.md @@ -11,9 +11,9 @@ following information is required for the credential: ![User Credentials Window - Active Directory](/images/accessanalyzer/11.6/admin/settings/connection/profile/activedirectoryaccount.webp) -- Domain – Drop-down menu with available trusted domains will appear. Either type the short domain +- Domain – dropdown menu with available trusted domains will appear. Either enter the short domain name in the textbox or select a domain from the menu. -- User name – Type the user name +- User name – Enter the user name - Password Storage – Choose the option for credential password storage: - Application – Uses the configured Profile Security setting as selected at the **Settings** > @@ -22,12 +22,12 @@ following information is required for the credential: topic for additional information. - CyberArk – Uses the CyberArk Enterprise Password Vault. See the [CyberArk Integration](/docs/accessanalyzer/11.6/admin/settings/connection/cyberarkintegration.md) - topic for additional information. The password fields do not apply for CyberArk password + topic for additional information. The password fields don't apply for CyberArk password storage. - Managed Service Account – Use previously configured MSA and gMSAs for authentication. The - password fields are not applicable when this option is selected. See the + password fields aren't applicable when this option is selected. See the [Group Managed Service Accounts (gMSA) Configuration](/docs/accessanalyzer/11.6/admin/settings/connection/gmsa.md) topic for additional information. -- Password – Type the password -- Confirm – Re-type the password +- Password – Enter the password +- Confirm – Re-enter the password diff --git a/docs/accessanalyzer/11.6/admin/settings/connection/create/aws.md b/docs/accessanalyzer/11.6/admin/settings/connection/create/aws.md index c793913491..0d85731f08 100644 --- a/docs/accessanalyzer/11.6/admin/settings/connection/create/aws.md +++ b/docs/accessanalyzer/11.6/admin/settings/connection/create/aws.md @@ -13,17 +13,17 @@ type in the User Credentials window. The required credentials for Amazon Web Services are: -- Access Key ID — Used to sign programmatic requests made to AWS. If access keys are not available, +- Access Key ID — Used to sign programmatic requests made to AWS. If access keys aren't available, create them with the IAM console. - Password Storage: Application – Uses the configured Profile Security setting as selected at the **Settings >** **Application** node -- Secret Key — Used to sign programmatic requests made to AWS. If secret keys are not available, +- Secret Key — Used to sign programmatic requests made to AWS. If secret keys aren't available, create them with the IAM console. - Scan Roles — Role used to scan other organization accounts ## Create a Connection Profile for AWS -A new connection profile will need to be created to be leveraged in the AWS Solution. +Create a new connection profile to use in the AWS Solution. **Step 1 –** Under Settings > Connection, click Add Connection profile. @@ -33,7 +33,7 @@ A new connection profile will need to be created to be leveraged in the AWS Solu Access Token section. :::tip -Remember, these are obtained from AWS when the permissions are configured. See the +Remember, you obtain these from AWS when you configure the permissions. See the [Configure AWS for Scans](/docs/accessanalyzer/11.6/requirements/aws/configurescans.md) topic for additional information. ::: @@ -41,4 +41,4 @@ topic for additional information. **Step 4 –** Click OK in the User Credentials modal, name the Connection Profile, and click Save. -This connection profile can now be assigned to the AWS Solution. +You can now assign this connection profile to the AWS Solution. diff --git a/docs/accessanalyzer/11.6/admin/settings/connection/create/create.md b/docs/accessanalyzer/11.6/admin/settings/connection/create/create.md index 8808545310..8ca661940c 100644 --- a/docs/accessanalyzer/11.6/admin/settings/connection/create/create.md +++ b/docs/accessanalyzer/11.6/admin/settings/connection/create/create.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Create a Connection Profile -Follow the steps to create a Connection Profile. +To create a Connection Profile: ![Add Connection Profile](/images/accessanalyzer/11.6/admin/settings/connection/profile/addconnectionprofile.webp) @@ -18,16 +18,16 @@ Follow the steps to create a Connection Profile. name in the Connection profile name textbox. :::note -A good profile name should be chosen so that it does not need to be changed at a later -time. If the profile name is changed after being applied to job groups or jobs, it requires the user -to go back through all of those job groups or jobs and re-apply the Connection Profile. +Choose a good profile name so that you don't need to change it later. If you change the +profile name after applying it to job groups or jobs, you must go back through those job groups or +jobs and reapply the Connection Profile. ::: ![Add User Credential](/images/accessanalyzer/11.6/admin/settings/connection/profile/addusercredential.webp) -**Step 3 –** Now it is time to add credentials to this profile. Click Add User credential and the -User Credentials window opens. +**Step 3 –** Click Add User credential to add credentials to this profile. The User Credentials +window opens. ![User Credentials](/images/accessanalyzer/11.6/admin/settings/connection/profile/activedirectoryaccount.webp) @@ -51,8 +51,8 @@ See the individual account type sections for information on the fields. Then cli ![Error Message for Password](/images/accessanalyzer/11.6/admin/settings/connection/profile/passworddifferserror.webp) :::note -If the entered passwords are not the same, an error message will pop-up after clicking OK -on the User Credentials window. Click OK on the error message and re-type the passwords. +If the entered passwords aren't the same, an error message will pop-up after clicking OK +on the User Credentials window. Click OK on the error message and re-enter the passwords. ::: @@ -68,9 +68,8 @@ domain, and then proceed through all other credentials until authentication is s are no more credentials to try. :::info -Limit the User Credentials list to a minimal number per profile, especially when -considering that a successful authentication does not automatically mean that particular credential -has the appropriate level of permissions in order for the data collection to occur. +Limit the User Credentials list to a minimal number per profile. A successful authentication +doesn't automatically mean that credential has the permissions required for data collection. ::: @@ -82,52 +81,52 @@ There are Move Up and Move Down buttons for arranging priority within the User C **Step 6 –** (Optional): At the bottom of the Connection view, is the Use the Windows account that Enterprise Auditor runs with before trying the user credentials above option. This option is per -Connection Profile. If checked, Enterprise Auditor applies the local login credentials prior to any +Connection Profile. If checked, Enterprise Auditor applies the local login credentials before any of the credentials saved to the Connection Profile. :::note -If a data collector utilizes an applet, this option must be unchecked. +If a data collector uses an applet, uncheck this option. ::: -**Step 7 –** When the user credentials have been added and ordered, click Save and then OK to -confirm the changes to the Connection Profile. +**Step 7 –** After you add and order the user credentials, click Save and then OK to confirm the +changes to the Connection Profile. The new Connection Profile is now visible in the Profile list and available for use at the job group or job level. ## Edit User Credentials within a Connection Profile -Follow the steps to edit user credentials within a Connection Profile. +To edit user credentials within a Connection Profile: ![Edit Connection Profile](/images/accessanalyzer/11.6/admin/settings/connection/profile/editusercredentials.webp) -**Step 1 –** Select the Connection Profile to be modified from the Profile list. Remember, changing -the Connection Profile name results in breaking job groups or jobs that are assigned this profile. +**Step 1 –** Select the Connection Profile you want to modify from the Profile list. Remember, +changing the Connection Profile name breaks job groups or jobs that are assigned this profile. -**Step 2 –** Select the user credential to be edited from the User Credentials list. Click Edit. +**Step 2 –** Select the user credential you want to edit from the User Credentials list. Click Edit. ![User Credentials](/images/accessanalyzer/11.6/admin/settings/connection/profile/selectaccounttype.webp) **Step 3 –** Modify the information in the User Credentials window. For the password, choose between the Use the existing password option or the Specify a new password below option. Click OK. -**Step 4 –** When the Connection Profile’s user credentials have been edited as desired, click Save -and then OK to confirm the changes to the Connection Profile. +**Step 4 –** After you edit the Connection Profile's user credentials as desired, click Save and then +OK to confirm the changes to the Connection Profile. -The edited user credentials are now used for authentication to target hosts for this Connection -Profile. +Enterprise Auditor now uses the edited user credentials for authentication to target hosts for this +Connection Profile. ## Delete a User Credential from a Connection Profile -Follow the steps to delete a user credential from a Connection Profile. +To delete a user credential from a Connection Profile: ![Delete User Credentials](/images/accessanalyzer/11.6/admin/settings/connection/profile/deleteusercredentials.webp) -**Step 1 –** Select the Connection Profile to be modified from the Profile list. Remember, changing -the Connection Profile name results in breaking job groups or jobs that are assigned this profile. +**Step 1 –** Select the Connection Profile you want to modify from the Profile list. Remember, +changing the Connection Profile name breaks job groups or jobs that are assigned this profile. -**Step 2 –** Select the user credential to be edited from the User Credentials list. Click Delete. +**Step 2 –** Select the user credential you want to edit from the User Credentials list. Click Delete. ![Confirmation message for deletion](/images/accessanalyzer/11.6/admin/settings/connection/profile/deleteusercredentialsconfirm.webp) @@ -145,19 +144,19 @@ The default profile is marked with the green checkmark. ![defaultconnectionprofile](/images/accessanalyzer/11.6/admin/settings/connection/profile/defaultconnectionprofile.webp) -Follow the steps to set a new default Connection Profile. +To set a new default Connection Profile: ![Set a Default Connection Profile](/images/accessanalyzer/11.6/admin/settings/connection/profile/setasdefaultconnectionprofile.webp) -**Step 1 –** Select the desired profile in the Connection Profile list and click Set as default. +**Step 1 –** Select the profile you want in the Connection Profile list and click Set as default. **Step 2 –** The green checkmark moves. Click Save and then OK to confirm the changes. -This Connection Profile is now used as the default Connection Profile. +This Connection Profile now serves as the default Connection Profile. ## Delete a Connection Profile -Follow the steps to delete a Connection Profile. +To delete a Connection Profile: ![Delete a Connection Profile](/images/accessanalyzer/11.6/admin/settings/connection/profile/deleteconnectionprofile.webp) diff --git a/docs/accessanalyzer/11.6/admin/settings/connection/create/exchangemodernauth.md b/docs/accessanalyzer/11.6/admin/settings/connection/create/exchangemodernauth.md index 7e19692f56..6ec94a5220 100644 --- a/docs/accessanalyzer/11.6/admin/settings/connection/create/exchangemodernauth.md +++ b/docs/accessanalyzer/11.6/admin/settings/connection/create/exchangemodernauth.md @@ -17,11 +17,11 @@ The values for the required credentials for the Exchange Modern Authentication a **Settings** > **Application** node. See the [Application](/docs/accessanalyzer/11.6/admin/settings/application/overview.md) topic for additional information.) -- Organization – The primary domain name of the Microsoft Entra tenant being leveraged to make the +- Organization – The primary domain name of the Microsoft Entra tenant used to make the connection. See the [Identify the Tenant's Name](/docs/accessanalyzer/11.6/requirements/exchange/exchangeonline/access.md#identify-the-tenants-name) topic for additional information. -- Email Address – The email address for the mailbox to be leveraged in Exchange Online environment +- Email Address – The email address for the mailbox used in Exchange Online environment scans. The mailbox must belong to the primary domain used in the Organization field. - AppID – Application (client) ID of the Enterprise Auditor application registered with Microsoft Entra ID. See the diff --git a/docs/accessanalyzer/11.6/admin/settings/connection/create/localwindows.md b/docs/accessanalyzer/11.6/admin/settings/connection/create/localwindows.md index 1f1a290ec6..0726355664 100644 --- a/docs/accessanalyzer/11.6/admin/settings/connection/create/localwindows.md +++ b/docs/accessanalyzer/11.6/admin/settings/connection/create/localwindows.md @@ -13,7 +13,7 @@ User Credentials window. The required credentials for the Local Windows Account are: -- User name – Type the user name +- User name – Enter the user name - Password Storage – Choose the option for credential password storage: - Application – Uses the configured Profile Security setting as selected at the **Settings** > @@ -22,15 +22,15 @@ The required credentials for the Local Windows Account are: topic for additional information. - CyberArk – Uses the CyberArk Enterprise Password Vault. See the [CyberArk Integration](/docs/accessanalyzer/11.6/admin/settings/connection/cyberarkintegration.md) - topic for additional information. The password fields do not apply for CyberArk password + topic for additional information. The password fields don't apply for CyberArk password storage. :::note If using the CyberArk option, then the associated Connection Profile can only have - one user credential in it. Multiple user credentials are not supported with the CyberArk + one user credential in it. Multiple user credentials aren't supported with the CyberArk integration when using local Windows accounts. ::: -- Password – Type the password -- Confirm – Re-type the password +- Password – Enter the password +- Confirm – Re-enter the password diff --git a/docs/accessanalyzer/11.6/admin/settings/connection/create/oracle.md b/docs/accessanalyzer/11.6/admin/settings/connection/create/oracle.md index 8e4a253602..593fa1f861 100644 --- a/docs/accessanalyzer/11.6/admin/settings/connection/create/oracle.md +++ b/docs/accessanalyzer/11.6/admin/settings/connection/create/oracle.md @@ -14,24 +14,24 @@ window. The required credentials for Oracle are: - Domain – Field options are dependent upon the additional account type option selected: - - Oracle Account – Domain is not a field for this type of credential - - Windows account that Enterprise Auditor is run with – (Domain is not a field for this type of + - Oracle Account – Domain isn't a field for this type of credential + - Windows account that Enterprise Auditor is run with – (Domain isn't a field for this type of credential) - - Active Directory – Drop-down menu with available trusted domains displays. Either type the + - Active Directory – dropdown menu with available trusted domains displays. Either enter the short domain name in the textbox or select a domain from the menu. -- User name – Type the user name - - This is not a field for the additional account type of Windows account that Enterprise Auditor +- User name – Enter the user name + - This isn't a field for the additional account type of Windows account that Enterprise Auditor is run with is selected - Password Storage: Application – Uses the configured Profile Security setting as selected at the **Settings >** **Application** node -- Password – Type the password - - This is not a field for the additional account type of Windows account that Enterprise Auditor +- Password – Enter the password + - This isn't a field for the additional account type of Windows account that Enterprise Auditor is run with -- Confirm – Re-type the password - - This is not a field for the additional account type of Windows account that Enterprise Auditor +- Confirm – Re-enter the password + - This isn't a field for the additional account type of Windows account that Enterprise Auditor is run with -- Role – Specify an Oracle role, if desired. The drop-down menu provides a list of roles. Either - type the role name in the textbox or select a role from the menu. +- Role – Specify an Oracle role, if desired. The dropdown menu provides a list of roles. Either + enter the role name in the textbox or select a role from the menu. - **NOTE:** When using a least privileged model for Oracle, **SYSDBA** must be selected for the Role. - Additional Account type – Select radio button of the secondary account type from the list at the diff --git a/docs/accessanalyzer/11.6/admin/settings/connection/create/sql.md b/docs/accessanalyzer/11.6/admin/settings/connection/create/sql.md index eea52d5037..fe3524bfc2 100644 --- a/docs/accessanalyzer/11.6/admin/settings/connection/create/sql.md +++ b/docs/accessanalyzer/11.6/admin/settings/connection/create/sql.md @@ -24,5 +24,5 @@ The required credentials for SQL Authentication are: **Settings** > **Application** node. See the [Application](/docs/accessanalyzer/11.6/admin/settings/application/overview.md) topic for additional information.) -- Password – Type the password -- Confirm – Re-type the password +- Password – Enter the password +- Confirm – Re-enter the password diff --git a/docs/accessanalyzer/11.6/admin/settings/connection/create/task.md b/docs/accessanalyzer/11.6/admin/settings/connection/create/task.md index 6b8207e42c..db432018d2 100644 --- a/docs/accessanalyzer/11.6/admin/settings/connection/create/task.md +++ b/docs/accessanalyzer/11.6/admin/settings/connection/create/task.md @@ -17,10 +17,10 @@ The required credentials for Task (Local) and Task (Domain) are: - Domain - Local – Not a field for this type of credential, defaults to `` - - Domain – Drop-down menu with available trusted domains displays. Either type the short domain + - Domain – dropdown menu with available trusted domains displays. Either enter the short domain name in the textbox or select a domain from the menu. -- User name – Type the user name +- User name – Enter the user name - Password Storage: Application – Uses the configured Profile Security setting as selected at the **Settings > Application** node -- Password – Type the password -- Confirm – Re-type the password +- Password – Enter the password +- Confirm – Re-enter the password diff --git a/docs/accessanalyzer/11.6/admin/settings/connection/create/unix.md b/docs/accessanalyzer/11.6/admin/settings/connection/create/unix.md index fe6faf5cca..ff1bf085d0 100644 --- a/docs/accessanalyzer/11.6/admin/settings/connection/create/unix.md +++ b/docs/accessanalyzer/11.6/admin/settings/connection/create/unix.md @@ -21,12 +21,12 @@ The required credentials for the Unix Account are: - Password/Confirm - If not using a private key, enter the **Password** and re-type in the **Confirm** field - - If using a private key, then the password is not needed. Provide the private key information + - If using a private key, then the password isn't needed. Provide the private key information in the **Use the following private key when connecting** field. - Use the following port/ports (CSV) for SSH - - The SSH port needs to be opened in software and hardware firewalls + - You must open the SSH port in software and hardware firewalls - If desired, select this option and provide the port value - Use the following private key when connecting diff --git a/docs/accessanalyzer/11.6/admin/settings/connection/cyberarkintegration.md b/docs/accessanalyzer/11.6/admin/settings/connection/cyberarkintegration.md index 2efe12ae2c..8f9de377cf 100644 --- a/docs/accessanalyzer/11.6/admin/settings/connection/cyberarkintegration.md +++ b/docs/accessanalyzer/11.6/admin/settings/connection/cyberarkintegration.md @@ -6,20 +6,20 @@ sidebar_position: 20 # CyberArk Integration -In order for Enterprise Auditor to be able to retrieve service account passwords from the CyberArk -Password Vault, the following prerequisites must be completed: +For Enterprise Auditor to retrieve service account passwords from the CyberArk Password Vault, +complete the following prerequisites: -- The Secrets Manager must be installed on the Enterprise Auditor Console server. The organization’s +- Install the Secrets Manager on the Enterprise Auditor Console server. The organization’s Vault administrator can provide the Secrets Manager installation package and most likely needs to - be present during the installation to provide credentials in order for the Secrets Manager + be present during the installation to provide credentials for the Secrets Manager installation to complete. See the CyberArk [Credential Provider (CP)](https://docs.cyberark.com/credential-providers/Latest/en/Content/CP%20and%20ASCP/Installing-CP.htm) article for additional information. -- An application must be added to CyberArk for the integration with Enterprise Auditor. The - Application Id of this application must then be added to the `GlobalOptions.xml` file for +- Add an application to CyberArk for the integration with Enterprise Auditor. Then add the + Application Id of this application to the `GlobalOptions.xml` file for Enterprise Auditor. See the [Customize CyberArk Application Id](#customize-cyberark-application-id) topic for additional - information. The application can be locked down by providing an OS User, a Path, or a Hash. See + information. You can lock down the application by providing an OS User, a Path, or a Hash. See the CyberArk [Add applications](https://docs.cyberark.com/credential-providers/14.0/en/Content/Common/Adding-Applications.htm) article for additional information. @@ -29,9 +29,9 @@ Password Vault, the following prerequisites must be completed: Account within Enterprise Auditor. More than one OS User can be added. - The Path should be a local path to the `StealthAUDIT.exe` file. The path should end with the file name: `…\StealthAUDIT.exe`. - - The Hash should be generated using the **AimGetAppInfo** tool in the + - Generate the Hash using the **AimGetAppInfo** tool in the `…\CyberArk\ApplicationPasswordProvider\Utils` folder on the server where Secrets Manager is - installed. AimGetAppInfo should be run in an Administrator Command Prompt. Run the following + installed. Run AimGetAppInfo in an Administrator Command Prompt using the following command: ``` @@ -55,32 +55,32 @@ Password Vault, the following prerequisites must be completed: ![Allowed Machines list for the CyberArk application](/images/accessanalyzer/11.6/admin/settings/connection/allowedmachines.webp) - - The machine name for the Enterprise Auditor console needs to be added on the Allowed Machines + - Add the machine name for the Enterprise Auditor console to the Allowed Machines list for the CyberArk application -- Once the Secrets Manager installation has completed and the Enterprise Auditor application has - been created, the necessary CyberArk accounts must be given access to the Safes in which the - Enterprise Auditor service accounts are stored. This includes the account which was created - automatically during the Secrets Manager installation, as well as the account created - automatically as a result of the application creation. +- After the Secrets Manager installation completes and you create the Enterprise Auditor + application, give the necessary CyberArk accounts access to the Safes that store the + Enterprise Auditor service accounts. This includes the account automatically created + during the Secrets Manager installation, as well as the account automatically created + when you create the application. ![Owners window for the Safe containing the credentials](/images/accessanalyzer/11.6/admin/settings/connection/vaultownerswindow.webp) - The account created during the AIM installation is under the naming convention `Prov_[COMPUTERNAME]`, where `COMPUTERNAME` is the name of the computer on which AIM is - installed. This account should be given **Retrieve accounts**, **List accounts**, and **View - Safe Members** rights on the desired Safes. + installed. Give this account **Retrieve accounts**, **List accounts**, and **View + Safe Members** rights on the Safes you want. - The account created during the application creation has the same name as the application - itself and should be given **Retrieve accounts** rights on the desired Safes + itself; give it **Retrieve accounts** rights on the Safes you want ## Customize CyberArk Application Id -The Application id value of the application created within CyberArk for the integration with -Enterprise Auditor must be configured within Enterprise Auditor. This is done in the +Configure Enterprise Auditor with the Application id value of the application you created within +CyberArk for the integration. You do this in the `GlobalOptions.xml` file within the Enterprise Auditor installation directory. The default location is `…\STEALTHbits\StealthAUDIT\`. -Follow the steps to customize the CyberArk Application Id within Enterprise Auditor. +To customize the CyberArk Application Id within Enterprise Auditor: **Step 1 –** Navigate to the `GlobalOptions.xml` file. Open it with a text editor, for example Notepad. @@ -126,8 +126,8 @@ window when configuring an **Active Directory Account** or **Local Windows Accou The credential information supplied in the User Credentials window must be an exact match to what is in CyberArk as the privileged account for which it is linked. It is case-sensitive. -If the Connection Profile with a Local Windows Account credential using CyberArk password storage is -used to target multiple hosts, then the local credential on each host needs to have the exact same +If you use a Connection Profile with a Local Windows Account credential using CyberArk password +storage to target multiple hosts, the local credential on each host needs to have the exact same username and password combination. ![Connection view with CyberArk credentials](/images/accessanalyzer/11.6/admin/settings/connection/usercredentials.webp) @@ -142,8 +142,8 @@ properties in CyberArk. These values are case-sensitive, and must be an exact ma ![User Credentials window for Active Directory Account](/images/accessanalyzer/11.6/admin/settings/connection/usercredentialsad.webp) -The table below shows the values from your CyberArk configuration that the User Credentials window -should be populated with: +The following table shows the values from your CyberArk configuration to populate in the User +Credentials window: | Enterprise Auditor | CyberArk Property | CyberArk Description | Example Value | | ------------------ | ----------------- | -------------------------------------- | ----------------- | @@ -160,8 +160,8 @@ Auditor Domain value is `` and the CyberArk Address property value is the ![User Credentials window for Local Windows Account](/images/accessanalyzer/11.6/admin/settings/connection/usercredentialslocal.webp) -The table below shows the values from your CyberArk configuration that the User Credentials window -should be populated with: +The following table shows the values from your CyberArk configuration to populate in the User +Credentials window: | Enterprise Auditor | CyberArk Property | CyberArk Description | Example Value | | ------------------ | ----------------- | -------------------------------------- | ------------- | @@ -172,7 +172,8 @@ should be populated with: :::info Only use one Local Windows Account credential with CyberArk password storage in a Connection Profile. As part of the Enterprise Auditor to CyberArk integration, the Enterprise -Auditor job is stopped immediately if the query from Enterprise Auditor to CyberArk for the -credential fails. Therefore, a second credential within the Connection Profile would not be queried. +Auditor stops the job immediately if the query from Enterprise Auditor to CyberArk for the +credential fails. Therefore, Enterprise Auditor wouldn't query a second credential within the +Connection Profile. ::: diff --git a/docs/accessanalyzer/11.6/admin/settings/connection/gmsa.md b/docs/accessanalyzer/11.6/admin/settings/connection/gmsa.md index f0f3fec9ad..8bcc67004c 100644 --- a/docs/accessanalyzer/11.6/admin/settings/connection/gmsa.md +++ b/docs/accessanalyzer/11.6/admin/settings/connection/gmsa.md @@ -7,7 +7,7 @@ sidebar_position: 30 # Group Managed Service Accounts (gMSA) Configuration Enterprise Auditor can use a previously-configured Group Managed Service Accounts (gMSA/MSA) -account. Make sure that Managed Service Account is selected in the User Credentials window. See the +account. ensure that Managed Service Account is selected in the User Credentials window. See the [Create a Connection Profile](/docs/accessanalyzer/11.6/admin/settings/connection/create/create.md) or [Create a Schedule Service Account](/docs/accessanalyzer/11.6/admin/settings/schedule.md#create-a-schedule-service-account) @@ -18,7 +18,7 @@ To run a job or scheduled task with a gMSA/MSA account, the following prerequisi - The account that Enterprise Auditor is run with must have permissions to retrieve the gMSA account password - The gMSA account must be a Local Admin in the target hosts -- The gMSA account does not have to be a local admin in the Enterprise Auditor Console +- The gMSA account doesn't have to be a local admin in the Enterprise Auditor Console - The Data Collector used must support unicode characters in the Connection Profile's credential password to retrieve the gMSA account password diff --git a/docs/accessanalyzer/11.6/admin/settings/connection/overview.md b/docs/accessanalyzer/11.6/admin/settings/connection/overview.md index b558c3781f..ef2f6e3899 100644 --- a/docs/accessanalyzer/11.6/admin/settings/connection/overview.md +++ b/docs/accessanalyzer/11.6/admin/settings/connection/overview.md @@ -32,7 +32,7 @@ inventory or job execution with the Windows account used to launch Enterprise Au ## Use a Connection Profile -This method allows you to define a Connection Profile which houses one or several sets of +Use this method to define a Connection Profile that houses one or several sets of credentials to be used for authentication on the target hosts during host inventory or job execution. The credentials specified in a Connection Profile could be any of the following: @@ -51,8 +51,8 @@ collector being used. ### Password Storage Options -The password for the credential provided can be stored in Enterprise Auditor application or -Enterprise Auditor Vault. Certain types of credentials can be stored in CyberArk®. +You can store the password for the credential provided in the Enterprise Auditor application or +Enterprise Auditor Vault. You can store certain types of credentials in CyberArk®. Choosing to store passwords in either the Enterprise Auditor application or the Enterprise Auditor Vault is a global setting configured in the **Settings** > **Application** node. See the @@ -74,9 +74,9 @@ topic for additional information. ![Cancel and Save options](/images/accessanalyzer/11.6/admin/settings/connection/cancelsavebuttons.webp) The **Cancel** and **Save** buttons are in the lower-right corner of the Connection view. These -buttons become enabled when modifications are made to the Connection global setting. +buttons become enabled when you make modifications to the Connection global setting. ![Information update message box](/images/accessanalyzer/11.6/admin/settings/connection/settingssavedmessage.webp) -Whenever changes are made at the global level, click **Save** and then **OK** to confirm the -changes. Otherwise, click **Cancel** if no changes were intended. +Whenever you make changes at the global level, click **Save** and then **OK** to confirm the +changes. Otherwise, click **Cancel** if you don't want to save the changes. diff --git a/docs/accessanalyzer/11.6/admin/settings/exchange.md b/docs/accessanalyzer/11.6/admin/settings/exchange.md index 9a511f3c7a..f2163aca44 100644 --- a/docs/accessanalyzer/11.6/admin/settings/exchange.md +++ b/docs/accessanalyzer/11.6/admin/settings/exchange.md @@ -11,18 +11,17 @@ These settings are exclusive to the Enterprise Auditor for Exchange Solution. ![Exchange - Set up the connection](/images/accessanalyzer/11.6/admin/settings/exchange_1.webp) -The Exchange node is grayed-out by default. In order for these settings to be enabled, it is -necessary to install both Enterprise Auditor MAPI CDO and Microsoft Exchange MAPI CDO on the -Enterprise Auditor Console server. See the +The Exchange node is grayed out by default. To enable these settings, install both Enterprise +Auditor MAPI CDO and Microsoft Exchange MAPI CDO on the Enterprise Auditor Console server. See the [StealthAUDIT MAPI CDO Installation](/docs/accessanalyzer/11.6/install/stealthauditmapicdoinstallation/stealthaudit_mapi_cdo_installation.md) topic for additional information. ![exchange_2](/images/accessanalyzer/11.6/admin/settings/exchange_2.webp) -Once the requirements have been met, the Exchange node is enabled for configuration. These settings -are utilized to make MAPI connections to the Exchange Server for the Mailbox, PublicFolder, -Exchange2K, and ExchangePS Data Collectors. The Client Access Server field, or CAS, is also utilized -by the ExchangePS Data Collector in order to make Remote PowerShell connections for Exchange 2010 or +After you meet the requirements, the Exchange node is enabled for configuration. These settings +are used to make MAPI connections to the Exchange Server for the Mailbox, PublicFolder, +Exchange2K, and ExchangePS Data Collectors. The Client Access Server field, or CAS, is also used +by the ExchangePS Data Collector to make Remote PowerShell connections for Exchange 2010 or newer. The data collectors apply these settings unless modified inside the job query. ![Set up the connection](/images/accessanalyzer/11.6/admin/settings/exchange_3.webp) @@ -45,34 +44,34 @@ on which version of Exchange is audited. specified for MAPI connections. - Enter the Alias name in the textbox. The Alias needs to be an Exchange 2010 or newer - mailbox, not a mail-enabled service account. However, this mailbox does not need + mailbox, not a mail-enabled service account. However, this mailbox doesn't need rights on the Exchange Organization; it only needs to reside within it. - Enter the name of the physical CAS in the Client Access Server textbox. This server can be - part of an array, but do not enter the name of a CAS Array. This should also be the - Exchange CAS where both Remote PowerShell and Windows Authentication on the PowerShell - Virtual Directory have been enabled. + part of an array, but don't enter the name of a CAS Array. This should also be the + Exchange CAS where you have enabled both Remote PowerShell and Windows Authentication on + the PowerShell Virtual Directory. :::info -Once the Exchange Connection Settings have been properly configured for the -version of Exchange to be audited, it is strongly recommended that the settings be tested. +After you properly configure the Exchange Connection Settings for the +version of Exchange you want to audit, test the settings. ::: In the Test Exchange Connection Settings section: -- Enter a Mailbox Server with mailboxes to be audited in the Exchange Server textbox. +- Enter a Mailbox Server with the mailboxes you want to audit in the Exchange Server textbox. - Click the Test Exchange settings link. ![Test Exchange Connection Setting](/images/accessanalyzer/11.6/admin/settings/exchange_4.webp) If the Exchange Connection Settings are correct, an output field opens. At the bottom of the output -field, a mailbox count is stated and a message appears which says, “You have successfully connected -to this Exchange Server.” Click OK. +field, the output states a mailbox count and shows a message that reads, “You have successfully +connected to this Exchange Server.” Click OK. ![exchange_6](/images/accessanalyzer/11.6/admin/settings/exchange_6.webp) The Cancel and Save buttons are in the lower-right corner of the Exchange view. These buttons become -enabled when modifications are made to the Exchange global setting. Whenever changes are made at the -global level, click Save and then OK to confirm the changes. Otherwise, click Cancel if no changes -were intended. +enabled when you make modifications to the Exchange global setting. Whenever you make changes at the +global level, click Save and then OK to confirm the changes. Otherwise, click Cancel if you don't +want to save the changes. diff --git a/docs/accessanalyzer/11.6/admin/settings/history.md b/docs/accessanalyzer/11.6/admin/settings/history.md index 21cf3e8d05..f121ed1ef7 100644 --- a/docs/accessanalyzer/11.6/admin/settings/history.md +++ b/docs/accessanalyzer/11.6/admin/settings/history.md @@ -6,7 +6,7 @@ sidebar_position: 50 # History -The History node is where the history retention of job data and job logs are configured. The setting +The History node is where you configure the history retention of job data and job logs. The setting specified here at the global level applies to all jobs in the Jobs tree unless specifically changed at the job group or job level. See the [History Node](/docs/accessanalyzer/11.6/admin/jobs/group/settings/history.md) @@ -28,15 +28,15 @@ for more control over the quantity of data by applying history retention at the level. All jobs run with this default setting only keep the most current record set. :::warning -It is important to understand that some pre-configured jobs require history retention -while others do not support it. Changing the history retention settings at the global level can +Some pre-configured jobs require history retention +while others don't support it. Changing the history retention settings at the global level can cause issues with data analysis and reporting on jobs that don't support it. See the relevant job group and job descriptions for additional information. ::: -The Diagnostics Retention Period settings determine how long this data is retained for all jobs that -do not have an explicit setting. Setting the retention period for a specific job overrides the +The Diagnostics Retention Period settings determine how long Enterprise Auditor retains this data +for all jobs that don't have an explicit setting. Setting the retention period for a specific job overrides the default setting. There are two settings: - Logs and Messages @@ -61,19 +61,19 @@ default setting. There are two settings: [Status Node](/docs/accessanalyzer/11.6/admin/jobs/job/status.md) topic for additional information. -For both the **Logs and Messages** and **Job Statistics** options above: +For both the **Logs and Messages** and **Job Statistics** options: -- Enter a number in the first textbox and select the desired time period from the drop-down menu in +- Enter a number in the first textbox and select the time period you want from the dropdown menu in the second box. Retention can be set to a specific number of **Days**, **Weeks**, **Months**, or **Times** for both. - All jobs run with this setting add the newly collected data set or job logs on top of the - previously collected record sets or logs. Any record sets or logs outside the specified historical - retention limit are dropped. + previously collected record sets or logs. Enterprise Auditor drops any record sets or logs outside + the specified historical retention limit. The **Cancel** and **Save** buttons are in the lower-right corner of the History view. These buttons -become enabled when modifications are made to the History global settings. Whenever changes are made +become enabled when you make modifications to the History global settings. Whenever you make changes at the global level, click **Save** and then **OK** to confirm the changes. Otherwise, click -**Cancel** if no changes were intended. +**Cancel** if you don't want to save the changes. ## Job Data History Retention & Database Size Concerns @@ -85,19 +85,19 @@ following scenario explains a common concern. - To reduce data retention periods, navigate to the **Settings** > **History** node. Change the time period to a smaller interval, for example 90 days. Click **Save** and rerun the jobs. - - All of the record sets outside the new retention limit are dropped, and the database size is - back down where it belongs + - Enterprise Auditor drops all record sets outside the new retention limit, reducing the + database to a more manageable size ## Job Logs -The job logs are stored within the output folder of each job. They can be read in the Enterprise -Auditor Console within the job’s **Status** > **Messages** table. To access the logs within the -job’s directory, right-click on the job’s node in the Navigation pane and select **Explore Folder**. +Enterprise Auditor stores the job logs within the output folder of each job. You can read them in +the Enterprise Auditor Console within the job’s **Status** > **Messages** table. To access the logs within the +job’s directory, right-click the job’s node in the Navigation pane and select **Explore Folder**. ![Job Logs in the job's Output folder in File Explorer](/images/accessanalyzer/11.6/admin/settings/historyjoblogs.webp) -The most recent log is open. Older jobs are stored as zip files, according to the Log Retention -Period setting. Each log is named in the following format: +The most recent log is open. Enterprise Auditor stores older jobs as zip files, according to the Log +Retention Period setting. Each log is named in the following format: - Open/Latest Log Name – `[Jobname]_Log.tsv` - Older/Zipped Log Name – `[Jobname]_Log_[Date]_[Time].zip` diff --git a/docs/accessanalyzer/11.6/admin/settings/hostdiscovery.md b/docs/accessanalyzer/11.6/admin/settings/hostdiscovery.md index 70bcdf9f15..1cc7b1e459 100644 --- a/docs/accessanalyzer/11.6/admin/settings/hostdiscovery.md +++ b/docs/accessanalyzer/11.6/admin/settings/hostdiscovery.md @@ -33,8 +33,8 @@ The log levels are: logging - Records all Info level information - - If files are referenced or updated during the process of running the query then the path to - the affected file is shown + - If the query references or updates files while running, the log shows the path to the + affected file - Helps [Netwrix Support](https://www.netwrix.com/support.html) to assist in diagnosing issues which may be causing host inventories to fail - Creates the largest file @@ -56,16 +56,16 @@ The log levels are: - Error – Records all errors which occur during the host discovery process :::info - Set the Log Level to Error. The default setting is Info, but it is - recommended that the setting for daily use be set to Error. The other log levels are designed to + Set the Log Level to Error. The default setting is Info, but Netwrix recommends setting it + to Error for daily use. The other log levels are designed to assist with troubleshooting host discovery and host inventory issues. ::: The **Cancel** and **Save** buttons are in the lower-right corner of the Host Discovery view. These -buttons become enabled when modifications are made to the Host Discovery global settings. Whenever -changes are made at the global level, click **Save** and then **OK** to confirm the changes. -Otherwise, click **Cancel** if no changes were intended. +buttons become enabled when you make modifications to the Host Discovery global settings. Whenever +you make changes at the global level, click **Save** and then **OK** to confirm the changes. +Otherwise, click **Cancel** if you don't want to save the changes. ![Host Discovery Log under Host Discovery node](/images/accessanalyzer/11.6/admin/settings/hostdiscoverylog.webp) diff --git a/docs/accessanalyzer/11.6/admin/settings/hostinventory.md b/docs/accessanalyzer/11.6/admin/settings/hostinventory.md index 213e427baf..91b5284c99 100644 --- a/docs/accessanalyzer/11.6/admin/settings/hostinventory.md +++ b/docs/accessanalyzer/11.6/admin/settings/hostinventory.md @@ -21,7 +21,7 @@ In the Inventory Items section, there are four program property groups: Each of these groups brings back the properties enumerated in the list below the group title. These collected properties correspond to the columns in the Host Management tables. Deselecting a checkbox -prevents that information from being collected for target hosts. However, some solutions require +stops Enterprise Auditor from collecting that information for target hosts. However, some solutions require this information. :::info @@ -37,9 +37,8 @@ host inventory process: - Threads – Indicates the number of job threads that are employed during the host inventory process - The default setting is 20 Threads - - Maximum thread count is 100. Thread count will revert back to 100 if values over 100 are - entered. - - Restart Enterprise Auditor if thread count is changed for changes to take place + - Maximum thread count is 100. Thread count reverts to 100 if you enter values over 100. + - Restart Enterprise Auditor if you change the thread count, for the changes to take place - Thread timeout [in seconds] – Indicates the time a thread will spend in retrieving information from a host @@ -48,13 +47,13 @@ host inventory process: - If thread can't receive an active response from target host, the thread will move on to the next host in the queue -- Stop on Failed Ping – If the Stop on Failed Ping checkbox is selected, hosts that don't respond - to pings aren't queried. Otherwise, hosts will be queried regardless. +- Stop on Failed Ping – If you select the Stop on Failed Ping checkbox, Enterprise Auditor doesn't + query hosts that don't respond to pings. Otherwise, Enterprise Auditor queries hosts regardless. - PING timeout [in seconds] – Indicates the time a thread will spend pinging a host - Default setting is 4 seconds - - If thread can't connect with a host, the host will be designated as being offline and the - thread will move on to the next host in the queue + - If the thread can't connect with a host, Enterprise Auditor designates the host as offline + and the thread moves on to the next host in the queue - Only refresh inventory items older than [time selected] – Indicates the time that needs to pass before the host inventory process is automatically refreshed @@ -74,24 +73,24 @@ host inventory process: The Desired Host List Views section at the bottom contains all available host lists, both built-in lists and custom-created lists. There are seven Default Hosts Lists which correspond -to the solutions that target them. During the host inventory process, hosts which meet the filter -criteria for these default lists are automatically populated into that host list. A checkmark in +to the solutions that target them. During the host inventory process, Enterprise Auditor automatically populates hosts that meet the +filter criteria for these default lists into that host list. A checkmark in front of the host list indicates that the list is visible in the **Host Management** > **All Hosts** node. The **Cancel** and **Save** buttons are in the lower-right corner of the Host Inventory view. These -buttons become enabled when modifications are made to the Host Inventory global settings. Whenever -changes are made at the global level, click **Save** and then **OK** to confirm the changes. -Otherwise, click **Cancel** if no changes were intended. +buttons become enabled when you make modifications to the Host Inventory global settings. Whenever +you make changes at the global level, click **Save** and then **OK** to confirm the changes. +Otherwise, click **Cancel** if you don't want to save the changes. ## Default Host Lists -The seven default lists are auto-populated during the host inventory process based on specific -filter criteria. These lists correspond to the pre-configured solution jobs which target them. +Enterprise Auditor auto-populates the seven default lists during the host inventory process based +on specific filter criteria. These lists correspond to the pre-configured solution jobs which target them. ### AD Host List -The **AD** Host List can be expanded and contains five sub-groups used by the Active Directory +You can expand the **AD** Host List. It contains five sub-groups used by the Active Directory Solution and the Active Directory Inventory Solution: ![AD Host List](/images/accessanalyzer/11.6/admin/settings/ad.webp) @@ -106,7 +105,7 @@ The sub-groups are: ### ALL WINDOWS HOSTS Host List -The **ALL WINDOWS HOSTS** Host List is used primarily by the Windows Solution. +The Windows Solution primarily uses the **ALL WINDOWS HOSTS** Host List. ![ALL WINDOWS HOSTS Host List](/images/accessanalyzer/11.6/admin/settings/allwindowshosts.webp) @@ -114,7 +113,7 @@ There are no sub-groups for ALL WINDOWS HOSTS. ### DG Host List -The **DG** Host List can be expanded and contains three sub-groups used by the Data Access +You can expand the **DG** Host List. It contains three sub-groups used by the Data Access Governance for File System Solution. ![DG Host List](/images/accessanalyzer/11.6/admin/settings/dg.webp) @@ -127,8 +126,8 @@ The sub-groups are: ### EXCHANGE Host List -The **EXCHANGE** Host List can be expanded and contains six sub-groups used by the Exchange -Solution. Four of these sub-groups can also be expand. +You can expand the **EXCHANGE** Host List. It contains six sub-groups used by the Exchange +Solution, and you can also expand four of these sub-groups. ![EXCHANGE Host List](/images/accessanalyzer/11.6/admin/settings/exchange.webp) @@ -146,7 +145,7 @@ The sub-groups are: ### SQL Servers Host List -The **SQL SERVERS** Host List is used primarily by the SQL Solution. +The SQL Solution primarily uses the **SQL SERVERS** Host List. ![SQL Servers Host List](/images/accessanalyzer/11.6/admin/settings/sqlservers.webp) @@ -154,7 +153,7 @@ There are no sub-groups for SQL SERVERS. ### Windows Server Host List -The **Windows Server** Host List can be expanded and contains three sub-groups used by the +You can expand the **Windows Server** Host List. It contains three sub-groups used by the Windows Solution. ![Windows Server Host List](/images/accessanalyzer/11.6/admin/settings/windowsserver.webp) @@ -167,7 +166,7 @@ The sub-groups are: ### Work Station Host List -The **Work Station** Host List can be expanded and contains one sub-group used by the Windows +You can expand the **Work Station** Host List. It contains one sub-group used by the Windows Solution. ![Work Station Host List](/images/accessanalyzer/11.6/admin/settings/workstation.webp) diff --git a/docs/accessanalyzer/11.6/admin/settings/notification.md b/docs/accessanalyzer/11.6/admin/settings/notification.md index 1e9c6724ba..62c1535e07 100644 --- a/docs/accessanalyzer/11.6/admin/settings/notification.md +++ b/docs/accessanalyzer/11.6/admin/settings/notification.md @@ -12,25 +12,25 @@ alerts, conformance analysis notification, and more. ![Global Settings Notification page](/images/accessanalyzer/11.6/admin/settings/notification.webp) -To enable notifications from the Enterprise Auditor Console, a mail server must be configured for -Enterprise Auditor to employ for sending emails. +To enable notifications from the Enterprise Auditor Console, configure a mail server for +Enterprise Auditor to use for sending emails. -Enterprise Auditor supports authentication and encryption when sending email notifications. -Notifications can be configured based on the requirements of an organizations mail environment. +Enterprise Auditor supports authentication and encryption when sending email notifications. You can +configure notifications based on the requirements of an organization's mail environment. -Enable Enterprise Auditor notifications by configuring the Mail Server and Sender Information. It is -recommended to send a test email to yourself after initial configuration to ensure proper settings. +Enable Enterprise Auditor notifications by configuring the Mail Server and Sender Information. Send +a test email to yourself after initial configuration to ensure proper settings. See the [Test Notification Settings](#test-notification-settings) topic for additional information. The **Cancel** and **Save** buttons are in the lower-right corner of the Notification view. These -buttons become enabled when modifications are made to the Notification global setting. Whenever -changes are made at the global level, click **Save** and then **OK** to confirm the changes. -Otherwise, click **Cancel** if no changes were intended. +buttons become enabled when you make modifications to the Notification global setting. Whenever +you make changes at the global level, click **Save** and then **OK** to confirm the changes. +Otherwise, click **Cancel** if you don't want to save the changes. ## Configure SMTP Server Information -The Mail Server section at the top of the page is where an organization’s SMTP Server information is -provided. +The Mail Server section at the top of the page is where you provide an organization’s SMTP Server +information. ![Mail Server settings on Notification page](/images/accessanalyzer/11.6/admin/settings/server.webp) @@ -67,12 +67,12 @@ account. **Step 2 –** Click **Save**. -The credentials for Mail Server authentication account have been updated and committed to the -Console. +Enterprise Auditor updates and commits the credentials for the Mail Server authentication account +to the Console. ## Sender Information -The Sender Information section is where the sender information is provided. +The Sender Information section is where you provide the sender information. ![Sender Information section on Notification page](/images/accessanalyzer/11.6/admin/settings/senderinformation.webp) @@ -82,7 +82,7 @@ Auditor, and are sent to this recipient list unless inheritance is broken at the level. - Sender Name – Name displayed in the sent from field of the email -- Sender Address – Sender’s email address. This does not have to be a real email address, unless +- Sender Address – Sender’s email address. This doesn't have to be a real email address, unless required by the organization. It can be something as simple as `accessanalyzer@yourdomain.com`. ## Email Content @@ -98,14 +98,14 @@ The Email Content section is where the recipient information is provided. ## Test Notification Settings -Once the global **Notification** settings have been configured, it is recommended to send a test -email to ensure proper configuration. This verifies all settings are correct and email is received -as expected. +After you configure the global **Notification** settings, send a test +email to ensure proper configuration. This verifies that all settings are correct and that email +arrives as expected. ![Test Email Settings button](/images/accessanalyzer/11.6/admin/settings/test.webp) -The Test Email Settings button sends a test email to the recipient list. It is recommended that you -test by sending an email to yourself. Once all Notification settings are configured, click the +The Test Email Settings button sends a test email to the recipient list. Test by sending an email +to yourself. Once you configure all Notification settings, click the **Test Email Settings** button. ![Test email sent successfully message](/images/accessanalyzer/11.6/admin/settings/testsuccess.webp) @@ -123,5 +123,6 @@ successfully. ![Netwrix Enterprise Auditor test e-mail](/images/accessanalyzer/11.6/admin/settings/testemail.webp) -This email is sent to all recipients when the **Test Email settings** link is clicked. When the -Notification settings are configured, click **Save** and then **Ok** to complete the configuration. +Enterprise Auditor sends this email to all recipients when you click the **Test Email settings** +link. After you configure the Notification settings, click **Save** and then **Ok** to complete the +configuration. diff --git a/docs/accessanalyzer/11.6/admin/settings/overview.md b/docs/accessanalyzer/11.6/admin/settings/overview.md index 012f5cd255..dc5138983c 100644 --- a/docs/accessanalyzer/11.6/admin/settings/overview.md +++ b/docs/accessanalyzer/11.6/admin/settings/overview.md @@ -6,15 +6,15 @@ sidebar_position: 20 # Global Settings -The global settings have an overall impact on the running ofEnterprise Auditor jobs. Settings are -inherited through a parent-child structure from the Settings node through the Jobs tree to the -individual jobs unless inheritance is broken by direct assignment at either the job group or the -individual job level. +The global settings have an overall impact on the running ofEnterprise Auditor jobs. Settings inherit +through a parent-child structure from the Settings node through the Jobs tree to the +individual jobs, unless you break inheritance by directly assigning settings at either the job +group or the individual job level. ![Configuration Settings](/images/accessanalyzer/11.6/admin/settings/globalsettings.webp) -Some of these settings are configured during the initial launching of theEnterprise Auditor Console. -Others are configured as desired by the end-user. Expand the Settings node in the Navigation pane to +You configure some of these settings during the initial launch of the Enterprise Auditor Console. +The end-user configures others as desired. Expand the Settings node in the Navigation pane to select a global setting to configure: - [Access](/docs/accessanalyzer/11.6/admin/settings/access/overview.md) @@ -37,11 +37,11 @@ select a global setting to configure: according to the data collector being used - [Exchange](/docs/accessanalyzer/11.6/admin/settings/exchange.md) - Required for auditing an organization’s Exchange environment - - Only enabled for configuration once the Enterprise Auditor for Exchange Solution prerequisites + - Only enabled for configuration after the Enterprise Auditor for Exchange Solution prerequisites are installed - Configure Microsoft Exchange server connections and requires Exchange server versions and names - - The ExchangeMailbox, Exchange2K, ExchangePS, and ExchangePublicFolder Data Collectors utilize + - The ExchangeMailbox, Exchange2K, ExchangePS, and ExchangePublicFolder Data Collectors use these global settings - [History](/docs/accessanalyzer/11.6/admin/settings/history.md) - Configure job data retention period settings @@ -65,7 +65,7 @@ select a global setting to configure: - [Schedule](/docs/accessanalyzer/11.6/admin/settings/schedule.md) - Optional configuration during the initial launch if Windows authentication is used with the Storage Profile - - Required in order to schedule host inventory, job, analysis task, and action task execution + - Required to schedule host inventory, job, analysis task, and action task execution - Provide credentials used against the Enterprise Auditor Console server to execute scheduled jobs with the Windows Task Scheduler - Creating a Schedule Service Account requires credentials on the Enterprise Auditor Console diff --git a/docs/accessanalyzer/11.6/admin/settings/reporting.md b/docs/accessanalyzer/11.6/admin/settings/reporting.md index 2851fec3bd..32fbd1da44 100644 --- a/docs/accessanalyzer/11.6/admin/settings/reporting.md +++ b/docs/accessanalyzer/11.6/admin/settings/reporting.md @@ -7,22 +7,22 @@ sidebar_position: 90 # Reporting The Reporting node is for configuring the global settings for publishing Enterprise Auditor reports. -The Web Console is where any reports which have been published can be viewed outside of the +The Web Console is where you can view any published reports outside of the Enterprise Auditor Console. The Web Console provides a consolidated logon housing both the published reports and the AIC (when applicable). ![Global Settings Reporting page](/images/accessanalyzer/11.6/admin/settings/reporting.webp) -The publishing of reports can be disabled at the global level by selecting **Do not publish -reports** from the Publish Option drop-down menu. It can also be disabled at the job group, job, or +You can disable the publishing of reports at the global level by selecting **Don't publish +reports** from the Publish Option dropdown menu. You can also disable it at the job group, job, or report configuration level. See the [Jobs Tree](/docs/accessanalyzer/11.6/admin/jobs/overview.md) topic for additional information. The **Cancel** and **Save** buttons are in the lower-right corner of the Reporting view. These -buttons become enabled when modifications are made to the Reporting global settings. Whenever -changes are made at the global level, click **Save** and then **OK** to confirm the changes. -Otherwise, click **Cancel** if no changes were intended. +buttons become enabled when you make modifications to the Reporting global settings. Whenever +you make changes at the global level, click **Save** and then **OK** to confirm the changes. +Otherwise, click **Cancel** if you don't want to save the changes. ## Website URL @@ -35,10 +35,10 @@ The default address is: http://[Fully Qualified Domain Name of the Enterprise Auditor Console server]:8082 -This link is used to access the Web Console, and it is used for the web link in an emailed report. -The protocol and port number may need to be modified to align with the organization’s environment, -but it must match the information in the website’s configuration file. If the Web Console has been -secured, this address must be manually updated: +Enterprise Auditor uses this link to access the Web Console and for the web link in an emailed +report. You may need to modify the protocol and port number to align with the organization’s +environment, but they must match the information in the website’s configuration file. If you have +secured the Web Console, manually update this address: https://[Fully Qualified Domain Name of the StealthAUDIT Console server]:[Port Number] @@ -52,11 +52,11 @@ topic for additional information. ## Publish Option -The Publish Option allows you to enable or disable the publishing of reports at the global level. +Use the Publish Option to enable or disable the publishing of reports at the global level. ![Publish Option on Global Settings Reporting page](/images/accessanalyzer/11.6/admin/settings/publish.webp) -Select the **Publish reports** option to publish all Enterprise Auditor reports or select **Do not +Select the **Publish reports** option to publish all Enterprise Auditor reports or select **Don't publish reports** to disable the publishing. The inheritance of this setting can be broken at the job group, job, or report levels. @@ -68,8 +68,8 @@ Configure email reports sent out by Enterprise Auditor using the Email Report op The **E-mail reports** checkbox enables recipients to receive all published reports, unless inheritance is broken at the job group, job, or report level. Separate multiple recipients with a -semicolon. If commas are used as delimiters for email addresses, they will be converted into -semicolons when the settings are saved. +semicolon. If you use commas as delimiters for email addresses, Enterprise Auditor converts them +into semicolons when you save the settings. :::info Configure email reporting at a specific level to ensure recipients only receive @@ -78,24 +78,24 @@ reports which apply to them. :::note -Email reports does not work unless Enterprise Auditor has been configured to send email +Email reports doesn't work unless you configure Enterprise Auditor to send email notifications through the **Notification** node. See the [Notification](/docs/accessanalyzer/11.6/admin/settings/notification.md) topic for additional information. ::: -The **Do Not Email Report If Blank** checkbox prevents reports from being sent via email if all -elements are blank when generated. A blank report can occur if there is an error in data collection +The **Don't Email Report If Blank** checkbox prevents Enterprise Auditor from sending reports via +email if all elements are blank when generated. A blank report can occur if there is an error in data collection or if the report is configured for data which might not always be present (for example, new computer objects created since last scan). :::info -Enable the **Do Not Email Report If Blank** option. +Enable the **Don't Email Report If Blank** option. ::: -The report can be sent using the desired **Email Content** option: +You can send the report using the **Email Content** option you want: - Web Link – Sends an email notice that the report has been published and provides the recipient with a link to it in the Web console @@ -112,7 +112,7 @@ the email subject line. ## Configure JavaScript Settings for the Web Console Any browser used to access the Web Console must have JavaScript allowed for all features of the Web -Console to function correctly. If the JavaScript permission is not set as allowed for the entire +Console to function correctly. If the JavaScript permission isn't set as allowed for the entire browser, you must add the Web Console as an allowed site. Follow the steps to allow JavaScript on the Web Console in Microsoft Edge. @@ -130,9 +130,10 @@ under All permissions. Console and click **Add**. :::note -If the global Allowed option is selected, you do not need to specifically add the Web +If the global Allowed option is selected, you don't need to specifically add the Web Console as an allowed site. ::: -The Web Console's URL is added to the Allow list and JavaScript is enabled for the Web Console. +Microsoft Edge adds the Web Console's URL to the Allow list and enables JavaScript for the Web +Console. diff --git a/docs/accessanalyzer/11.6/admin/settings/schedule.md b/docs/accessanalyzer/11.6/admin/settings/schedule.md index 5616812592..72c3e6626a 100644 --- a/docs/accessanalyzer/11.6/admin/settings/schedule.md +++ b/docs/accessanalyzer/11.6/admin/settings/schedule.md @@ -11,24 +11,24 @@ Account is used to run scheduled tasks on the Enterprise Auditor Console server. ![Schedule node](/images/accessanalyzer/11.6/admin/settings/schedule.webp) -Jobs can be executed manually as desired or scheduled to execute at designated times. For example, +You can execute jobs manually as desired or schedule them to execute at designated times. For example, you could schedule a job to run during hours when the office is closed and network traffic is low. Windows uses the Schedule Service Account to access the task folders when launching scheduled tasks. -Schedule Service Accounts are configured at the global level, and this account can be used to +Schedule Service Accounts are configured at the global level, and you can use this account to schedule jobs in the Schedule Wizard. See the [Schedules](/docs/accessanalyzer/11.6/admin/schedule/overview.md) topic for additional information. :::warning -On Windows 2016 servers, the Schedule Service Account cannot be signed into an active -session when the time comes for a scheduled task to start. Windows blocks the starting or running of +On Windows 2016 servers, the Schedule Service Account can't be signed into an active +session when a scheduled task is set to start. Windows blocks the starting or running of scheduled tasks using an account that is logged into the server. ::: **Password Storage Options** -The password for the credential provided can be stored in the Enterprise Auditor application or the +You can store the password for the credential provided in the Enterprise Auditor application or the Enterprise Auditor Vault. Choosing between the Enterprise Auditor application and Enterprise Auditor Vault is a global setting @@ -69,9 +69,9 @@ least the following to meet Least Privileged specifications: topic for additional information. The **Cancel** and **Save** buttons are in the lower-right corner of the Schedule view. These -buttons become enabled when modifications are made to the Schedule global settings. Whenever changes -are made at the global level, click **Save** and then **OK** to confirm the changes. Otherwise, -click **Cancel** if no changes were intended. +buttons become enabled when you make modifications to the Schedule global settings. Whenever you +make changes at the global level, click **Save** and then **OK** to confirm the changes. Otherwise, +click **Cancel** if you don't want to save the changes. The Enterprise Auditor vault provides enhanced security through enhanced encryption to various credentials stored by the Enterprise Auditor application. See the @@ -80,7 +80,7 @@ topic for additional information. ## Schedule Service Account Types -There are two types of accounts that can be used to configure the Schedule Service Account. +Use one of two types of accounts to configure the Schedule Service Account. ![serviceaccounttypes](/images/accessanalyzer/11.6/admin/settings/serviceaccounttypes.webp) @@ -91,7 +91,7 @@ Use one of the following options for the Schedule Service Account: - Credentials must have privileges sufficient for scheduling tasks on the Enterprise Auditor Console server. If not, scheduled tasks fail to start. - - This option cannot be edited or deleted + - You can't edit or delete this option - User-supplied credentials – Provide credentials for a specific account with sufficient rights to schedule tasks on the Enterprise Auditor Console server @@ -100,19 +100,19 @@ Use one of the following options for the Schedule Service Account: - A local Windows account is a specific account and not the default local system account :::tip -Remember, the Schedule Service Account cannot be signed into an active session on the Enterprise -Auditor Console server when the time comes for a scheduled task to start when it has a Windows 2016 +Remember, the Schedule Service Account can't be signed into an active session on the Enterprise +Auditor Console server when a scheduled task is set to start, if the server has a Windows 2016 operating system. ::: ## Create a Schedule Service Account -Follow the steps to create a Schedule Service Account. +To create a Schedule Service Account: :::tip -Remember, the Schedule Service Account cannot be signed into an active session on the Enterprise -Auditor Console server when the time comes for a scheduled task to start when it has a Windows 2016 +Remember, the Schedule Service Account can't be signed into an active session on the Enterprise +Auditor Console server when a scheduled task is set to start, if the server has a Windows 2016 operating system. ::: @@ -138,12 +138,12 @@ types are: - Application – Uses Enterprise Auditor’s configured Profile Security setting as selected at the **Settings** > **Application** node - Managed Service Account – Use previously configured MSA and gMSAs for authentication. The - password fields are not applicable when this option is selected. See the + password fields aren't applicable when this option is selected. See the [Group Managed Service Accounts (gMSA) Configuration](/docs/accessanalyzer/11.6/admin/settings/connection/gmsa.md) topic for additional information. - - Password – Type the password - - Confirm – Re-type the password + - Password – Enter the password + - Confirm – Re-enter the password - Local Account – Use this option to specify a local account for the Enterprise Auditor Console server @@ -154,32 +154,32 @@ types are: - Application – Uses Enterprise Auditor’s configured Profile Security setting as selected at the **Settings** > **Application** node - - Password – Type the password - - Confirm – Re-type the password + - Password – Enter the password + - Confirm – Re-enter the password -**Step 3 –** Click **OK** and the credentials are verified. If there are no problems with the -provided credentials, the User Credentials window closes. Otherwise, one of the following error +**Step 3 –** Click **OK**; Enterprise Auditor verifies the credentials. If there are no problems with +the provided credentials, the User Credentials window closes. Otherwise, one of the following error messages might appear: -- Passwords Do Not Match Error +- Passwords Don't Match Error - ![Passwords Do Not Match Error](/images/accessanalyzer/11.6/admin/settings/passwordsdontmatch.webp) + ![Passwords Don't Match Error](/images/accessanalyzer/11.6/admin/settings/passwordsdontmatch.webp) - - This error indicates the two password entries do not match. Click **OK** and reenter the + - This error indicates the two password entries don't match. Click **OK** and reenter the passwords. - Bad User Name or Password Error ![Bad User Name or Password Error](/images/accessanalyzer/11.6/admin/settings/incorrectlogondetails.webp) - - This error indicates either the user account does not exist or the username and password do + - This error indicates either the user account doesn't exist or the username and password do not match. Click **OK** and reenter the information. - Insufficient Rights Error ![Insufficient Rights Error](/images/accessanalyzer/11.6/admin/settings/insufficientrights.webp) - - This error indicates the account supplied does not have sufficient rights to create and run + - This error indicates the account supplied doesn't have sufficient rights to create and run scheduled tasks. Click **OK** and provide credentials with sufficient rights. - GPO Network Security Error @@ -201,32 +201,32 @@ Enterprise Auditor can now schedule tasks with this Scheduled Service Account. ## Edit a Schedule Service Account -Follow the steps to edit a Schedule Service Account credentials. +To edit a Schedule Service Account's credentials: :::tip -Remember, the Schedule Service Account cannot be signed into an active session on the Enterprise -Auditor Console server when the time comes for a scheduled task to start when it has a Windows 2016 +Remember, the Schedule Service Account can't be signed into an active session on the Enterprise +Auditor Console server when a scheduled task is set to start, if the server has a Windows 2016 operating system. ::: ![Edit option in the Schedule view](/images/accessanalyzer/11.6/admin/settings/edit.webp) -**Step 1 –** Select a credential from the User Credentials list and click on **Edit**. The User +**Step 1 –** Select a credential from the User Credentials list and click **Edit**. The User Credentials window opens. **Step 2 –** Modify the credential information as needed. See Step 2 of the [Create a Schedule Service Account](#create-a-schedule-service-account) topic for additional information. -**Step 3 –** Click **OK** and the credentials will be verified. If there are no problems with the -provided credentials, the User Credentials window closes. +**Step 3 –** Click **OK**; Enterprise Auditor verifies the credentials. If there are no problems with +the provided credentials, the User Credentials window closes. Enterprise Auditor can now schedule tasks with this Scheduled Service Account. ## Delete a Schedule Service Account -Follow the steps to delete a Schedule Service Account. +To delete a Schedule Service Account: ![Delete option in the Schedule view](/images/accessanalyzer/11.6/admin/settings/delete.webp) @@ -241,6 +241,6 @@ Credentials confirmation window appears. Account. Click **Save** and then **OK** to confirm the changes. To ensure these changes take effect, exit and restart the Enterprise Auditor application. -If all Schedule Service Accounts are removed and only the local System account remains, Enterprise -Auditor cannot create or run scheduled tasks unless the local system account has adequate +If you remove all Schedule Service Accounts and only the local System account remains, Enterprise +Auditor can't create or run scheduled tasks unless the local system account has adequate permissions. diff --git a/docs/accessanalyzer/11.6/admin/settings/sensitivedata/criteria.md b/docs/accessanalyzer/11.6/admin/settings/sensitivedata/criteria.md index 2ce410ed91..5ff75acfde 100644 --- a/docs/accessanalyzer/11.6/admin/settings/sensitivedata/criteria.md +++ b/docs/accessanalyzer/11.6/admin/settings/sensitivedata/criteria.md @@ -23,13 +23,13 @@ The options on the Criteria Tab are: - Search selected criteria – Filter the criteria listed in the Criteria tab The **Cancel** and **Save** buttons are in the lower-right corner of the Sensitive Data view. These -buttons become enabled when modifications are made to the Sensitive Data global settings. Whenever -changes are made at the global level, click **Save** and then **OK** to confirm the changes. -Otherwise, click **Cancel** if no changes were intended. +buttons become enabled when you make modifications to the Sensitive Data global settings. Whenever +you make changes at the global level, click **Save** and then **OK** to confirm the changes. +Otherwise, click **Cancel** if you don't want to save the changes. ## Select Criteria Window -Follow the steps to add Search Criteria for Sensitive Data scan jobs. +To add Search Criteria for Sensitive Data scan jobs: ![Add criteria](/images/accessanalyzer/11.6/admin/settings/sensitivedata/addcriteria.webp) @@ -45,5 +45,5 @@ search criteria. **Step 4 –** Click **Save** on the Sensitive Data view to save changes. -The selected Search Criteria are now inherited by Sensitive Data scan jobs that are set to use -global sensitive data criteria settings. +Sensitive Data scan jobs that are set to use global sensitive data criteria settings now inherit +the selected Search Criteria. diff --git a/docs/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/add.md b/docs/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/add.md index 01df6eaf03..7d68d17a74 100644 --- a/docs/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/add.md +++ b/docs/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/add.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Adding False Positive Exclusion Filters -Follow the steps to add a False Positive Exclusion Filter. +To add a False Positive Exclusion Filter: ![Add Filter on False Positives tab](/images/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/addfilter.webp) @@ -17,7 +17,7 @@ Follow the steps to add a False Positive Exclusion Filter. **Step 2 –** Enter the **File Path** according to the type of format for the repository. **Step 3 –** Indicate the type of repository by selecting either **File System** or **SharePoint** -from the **Source** drop-down menu. +from the **Source** dropdown menu. **Step 4 –** Select the required criteria from the list by selecting the relevant checkboxes. You can use the **Search Criteria** textbox to filter the list by keywords. @@ -27,4 +27,4 @@ Exclusion Filter window closes. **Step 6 –** Click **Save** on the Sensitive Data view to save changes. -The false positive exclusion filter is now applied to Sensitive Data reports. +Enterprise Auditor now applies the false positive exclusion filter to Sensitive Data reports. diff --git a/docs/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/delete.md b/docs/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/delete.md index 1df666d811..940f2daa50 100644 --- a/docs/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/delete.md +++ b/docs/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/delete.md @@ -6,7 +6,7 @@ sidebar_position: 30 # Deleting False Positive Exclusion Filters -Follow the steps to delete a False Positive Exclusion Filter. +To delete a False Positive Exclusion Filter: ![Delete Filter on False Positives tab](/images/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/deletefilter.webp) @@ -14,4 +14,4 @@ Follow the steps to delete a False Positive Exclusion Filter. **Step 2 –** Click **Save** on the Sensitive Data view to save changes. -The false positive exclusion filter has been successfully deleted. +Enterprise Auditor successfully deletes the false positive exclusion filter. diff --git a/docs/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/edit.md b/docs/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/edit.md index 5b2762af41..aaa2e558e5 100644 --- a/docs/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/edit.md +++ b/docs/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/edit.md @@ -6,7 +6,7 @@ sidebar_position: 20 # Editing False Positive Exclusion Filters -Follow the steps to edit a False Positive Exclusion Filter. +To edit a False Positive Exclusion Filter: ![Edit Filter on False Positives tab](/images/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/editfilter.webp) @@ -21,4 +21,4 @@ closes. **Step 4 –** Click **Save** on the Sensitive Data view to save changes. -The false positive exclusion filter has been successfully edited. +Enterprise Auditor successfully saves your edits to the false positive exclusion filter. diff --git a/docs/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/export.md b/docs/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/export.md index 3bcd7ba6e8..3962755d4c 100644 --- a/docs/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/export.md +++ b/docs/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/export.md @@ -6,7 +6,7 @@ sidebar_position: 50 # Exporting False Positive Exclusion Filters -Follow the steps to export selected False Positive Exclusion Filters into a TXT file. +To export selected False Positive Exclusion Filters into a TXT file: ![Export on False Positives tab](/images/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/exportfilter.webp) @@ -15,7 +15,7 @@ Explorer opens. ![Select False Positive Exclusion filter file to export File Explorer window](/images/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/exportfileexplorer.webp) -**Step 2 –** Enter a File name for the TXT file that the exported false positive exclusion filters -will be contained in. Click **Save**. +**Step 2 –** Enter a File name for the TXT file that will contain the exported false positive +exclusion filters. Click **Save**. -The False Positive Exclusion Filters are now exported. +Enterprise Auditor now exports the False Positive Exclusion Filters. diff --git a/docs/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/import.md b/docs/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/import.md index 71f7506f53..79ff7fcf7e 100644 --- a/docs/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/import.md +++ b/docs/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/import.md @@ -7,10 +7,10 @@ sidebar_position: 40 # Importing False Positive Exclusion Filters Create an import (TXT) file containing a list of file paths for the files to be excluded from -Sensitive Data reports. The text file should have one file path per row. The import file needs to be -scoped to a single solution and a criteria set. +Sensitive Data reports. The text file should have one file path per row. You must scope the import +file to a single solution and a criteria set. -Follow the steps to import a list of False Positive Exclusion Filter. +To import a list of False Positive Exclusion Filters: ![Import on False Positives tab](/images/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/importfilter.webp) @@ -19,12 +19,12 @@ window. ![Select False Positive Exclusion Filter file to import window](/images/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/importfileexplorer.webp) -**Step 2 –** Navigate to the file that will be imported. Select the file and click **Open**. The +**Step 2 –** Navigate to the file you want to import. Select the file and click **Open**. The Configure Imported False Positive Exclusion Filters window opens. ![Configure Imported False Positive Exclusion Filters window](/images/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/configureexclusionfilterwindow.webp) -**Step 3 –** Select the repository type from the **Source** drop-down menu. +**Step 3 –** Select the repository type from the **Source** dropdown menu. **Step 4 –** Select the required criteria from the list. You can use the **Search Criteria** textbox to filter the list by keywords. @@ -34,7 +34,8 @@ Filters window closes. **Step 6 –** Click **Save** on the Sensitive Data view to save changes. -The imported list of False Positive Exclusion Filters are now applied to Sensitive Data reports. If -all of the files in the import were not meant to have the same Source and Criteria set, see the +Enterprise Auditor now applies the imported list of False Positive Exclusion Filters to Sensitive +Data reports. If all of the files in the import weren't meant to have the same Source and Criteria +set, see the [Editing False Positive Exclusion Filters](/docs/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/edit.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/overview.md b/docs/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/overview.md index 84c62bb847..9bdfa7bdf7 100644 --- a/docs/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/overview.md +++ b/docs/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/overview.md @@ -6,9 +6,9 @@ sidebar_position: 20 # False Positives Tab -Configure False Positive exclusion filters using the options in the False Positives tab. False -Positives Filters listed here as False Positives results in the corresponding matches being removed -from Enterprise Auditor and Access Information Center reports. +Configure False Positive exclusion filters using the options in the False Positives tab. When you +list filters here as False Positives, Enterprise Auditor removes the corresponding matches from +Enterprise Auditor and Access Information Center reports. ![False Positives tab](/images/accessanalyzer/11.6/admin/settings/sensitivedata/exclusions/falsepositivestab.webp) @@ -45,6 +45,6 @@ Filters: - Criteria – Sensitive Data criteria where the exclusion filter is applied The **Cancel** and **Save** buttons are in the lower-right corner of the Sensitive Data view. These -buttons become enabled when modifications are made to the Sensitive Data global settings. Whenever -changes are made at the global level, click **Save** and then **OK** to confirm the changes. -Otherwise, click **Cancel** if no changes were intended. +buttons become enabled when you make modifications to the Sensitive Data global settings. Whenever +you make changes at the global level, click **Save** and then **OK** to confirm the changes. +Otherwise, click **Cancel** if you don't want to save the changes. diff --git a/docs/accessanalyzer/11.6/admin/settings/sensitivedata/overview.md b/docs/accessanalyzer/11.6/admin/settings/sensitivedata/overview.md index 80fe653470..7c1160c579 100644 --- a/docs/accessanalyzer/11.6/admin/settings/sensitivedata/overview.md +++ b/docs/accessanalyzer/11.6/admin/settings/sensitivedata/overview.md @@ -12,7 +12,7 @@ positive exclusion filters. These settings require the Sensitive Data Discovery topic for additional information. :::note -Sensitive data exclusion filters can only be applied to the +You can only apply sensitive data exclusion filters to the [File System Solution](/docs/accessanalyzer/11.6/solutions/filesystem/overview.md) and the [SharePoint Solution](/docs/accessanalyzer/11.6/solutions/sharepoint/overview.md). diff --git a/docs/accessanalyzer/11.6/admin/settings/servicenow.md b/docs/accessanalyzer/11.6/admin/settings/servicenow.md index 460a40d20e..c894dfc2bf 100644 --- a/docs/accessanalyzer/11.6/admin/settings/servicenow.md +++ b/docs/accessanalyzer/11.6/admin/settings/servicenow.md @@ -7,8 +7,8 @@ sidebar_position: 120 # ServiceNow The ServiceNow® node is for configuring the settings needed to integrate with ServiceNow. These -settings are exclusive to the Enterprise Auditor integration with ServiceNow and are used by the -ServiceNow Action Module. See the +settings are exclusive to the Enterprise Auditor integration with ServiceNow, and the ServiceNow +Action Module uses them. See the [ServiceNow Action Module](/docs/accessanalyzer/11.6/admin/action/servicenow/overview.md) topic for additional information. @@ -22,17 +22,17 @@ Provide ServiceNow authentication information to your ServiceNow instance. field, and any other ServiceNow incident field that references the **sys_user** table. The **Cancel** and **Save** buttons are in the lower-right corner of the ServiceNow view. These -buttons become enabled when modifications are made to the ServiceNow global settings. Whenever -changes are made at the global level, click **Save** and then **OK** to confirm the changes. -Otherwise, click **Cancel** if no changes were intended. +buttons become enabled when you make modifications to the ServiceNow global settings. Whenever +you make changes at the global level, click **Save** and then **OK** to confirm the changes. +Otherwise, click **Cancel** if you don't want to save the changes. ## Update ServiceNow Authentication Credentials -Follow the steps to update the ServiceNow authentication credentials. +To update the ServiceNow authentication credentials: **Step 1 –** In the ServiceNow Authentication section, enter a new **Password** for the user account. **Step 2 –** Click **Save**. -The credentials have been updated for ServiceNow authentication. +Enterprise Auditor updates the credentials for ServiceNow authentication. diff --git a/docs/accessanalyzer/11.6/admin/settings/storage/add.md b/docs/accessanalyzer/11.6/admin/settings/storage/add.md index cf33b821dc..9a0e61674f 100644 --- a/docs/accessanalyzer/11.6/admin/settings/storage/add.md +++ b/docs/accessanalyzer/11.6/admin/settings/storage/add.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Add a Storage Profile -Follow the steps to create a Storage Profile. +To create a Storage Profile: ![Add Storage profile option](/images/accessanalyzer/11.6/admin/settings/storage/addprofile.webp) @@ -19,7 +19,7 @@ Profile name to a unique and descriptive name. ![Server Name field](/images/accessanalyzer/11.6/admin/settings/storage/addprofileservername.webp) -**Step 3 –** Type the SQL **Server name** in the textbox provided. This can be a NetBIOS name, a +**Step 3 –** Enter the SQL **Server name** in the textbox provided. This can be a NetBIOS name, a fully qualified domain name, or an IP Address. If the SQL Server specified is configured to use a named instance, provide the **Instance name** in the next textbox. @@ -45,17 +45,17 @@ for additional information. | ----------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | | Good Connection Test | Bad Connection Test | -**Step 6 –** It is recommended to test the credentials provided at this point. The radio button for -**Use existing database** should be selected by default. Test the SQL Server connection by clicking -the drop-down arrow for an existing database. If the connection is established, a listing of -databases appears. If the connection cannot be established, an error warning displays. +**Step 6 –** Consider testing the credentials provided at this point. By default, Enterprise Auditor +selects the radio button for **Use existing database**. Test the SQL Server connection by clicking +the dropdown arrow for an existing database. If the connection succeeds, a listing of +databases appears. If the connection fails, an error warning displays. ![Database options](/images/accessanalyzer/11.6/admin/settings/storage/addprofiledatabase.webp) **Step 7 –** Set the database through one of the following options: - Use existing database – Click this radio button and select a database from this list provided in - the drop-down menu + the dropdown menu - Create new database – Click this radio button and provide a unique, descriptive name in the textbox @@ -66,8 +66,8 @@ the appropriate permissions and lists any that are missing. If no permissions ar message appears in the Connection report window. When there is a `Successful connection test`, click **Close**. -**Step 9 –** If **Create new database** was selected, the new database now exists. If **Use existing -database** was selected, the Storage Profile is now linked to the database. Click **Save** and then +**Step 9 –** If you selected **Create new database**, the new database now exists. If you selected +**Use existing database**, the Storage Profile is now linked to the database. Click **Save** and then **OK** to complete the creation of the new Storage Profile. -The new Storage Profile is available to be used by Enterprise Auditor. +Enterprise Auditor can now use the new Storage Profile. diff --git a/docs/accessanalyzer/11.6/admin/settings/storage/default.md b/docs/accessanalyzer/11.6/admin/settings/storage/default.md index 2df7ac4f12..f965b51b89 100644 --- a/docs/accessanalyzer/11.6/admin/settings/storage/default.md +++ b/docs/accessanalyzer/11.6/admin/settings/storage/default.md @@ -6,9 +6,9 @@ sidebar_position: 30 # Set a Default Storage Profile -While multiple Storage Profiles can exist, only one profile can be set as the default. A green -checkmark next to the profile name indicates the default Storage Profile. Follow the steps to change -the default Storage Profile at the global level. +You can create multiple Storage Profiles, but you can set only one as the default. A green +checkmark next to the profile name indicates the default Storage Profile. To change +the default Storage Profile at the global level: ![Set as Default option on Storage page](/images/accessanalyzer/11.6/admin/settings/storage/default.webp) @@ -17,8 +17,8 @@ storage profile window opens. ![Change storage profile window](/images/accessanalyzer/11.6/admin/settings/storage/changestorageprofile.webp) -**Step 2 –** There are three options for host management data migration. Select the desired option, -choose whether or not to apply the secondary option, and click **OK**. +**Step 2 –** There are three options for host management data migration. Select the option you want, +choose whether to apply the secondary option, and click **OK**. - Merge your host management data with data in the destination table (Recommended) – This option keeps existing hosts and host discovery tasks in the destination and updates the tasks based on @@ -33,7 +33,7 @@ choose whether or not to apply the secondary option, and click **OK**. - Also overwrite shared host inventory data – If selected, host inventory data is also replaced with data found in the source database -- Don’t copy your host management data to destination table – This option does not copy, update, or +- Don’t copy your host management data to destination table – This option doesn't copy, update, or overwrite information between databases - Clear data in destination table – If selected, all host management data in the destination @@ -45,12 +45,12 @@ choose whether or not to apply the secondary option, and click **OK**. ![Storage page with new default storage profile](/images/accessanalyzer/11.6/admin/settings/storage/defaultsave.webp) -**Step 4 –** A blue arrow now points to the new default Storage Profile. However, the arrow is also -an indication that the new default is not fully recognized by Enterprise Auditor. Click **Save** and +**Step 4 –** A blue arrow now points to the new default Storage Profile. However, the arrow also +indicates that Enterprise Auditor hasn't fully recognized the new default. Click **Save** and then **OK** to confirm the changes. **Step 5 –** Finally, to ensure these changes take effect, exit the Enterprise Auditor application and relaunch it. -The blue arrow is replaced by the green checkmark, indicating the new default Storage Profile is -recognized. +The green checkmark replaces the blue arrow, indicating that Enterprise Auditor now recognizes the +new default Storage Profile. diff --git a/docs/accessanalyzer/11.6/admin/settings/storage/delete.md b/docs/accessanalyzer/11.6/admin/settings/storage/delete.md index 9329874276..c19703b5bc 100644 --- a/docs/accessanalyzer/11.6/admin/settings/storage/delete.md +++ b/docs/accessanalyzer/11.6/admin/settings/storage/delete.md @@ -6,17 +6,17 @@ sidebar_position: 40 # Delete a Storage Profile -Follow the steps to delete a Storage Profile. +To delete a Storage Profile: :::note -This procedure does not delete databases from the SQL Server. It only removes the selected +This procedure doesn't delete databases from the SQL Server. It only removes the selected Storage Profile from this Enterprise Auditor Console. ::: ![Delete Storage Profile option](/images/accessanalyzer/11.6/admin/settings/storage/delete.webp) -**Step 1 –** Select the Storage Profile to be removed, and click **Delete**. +**Step 1 –** Select the Storage Profile to remove, and click **Delete**. ![Confirm delete selected profile dialog](/images/accessanalyzer/11.6/admin/settings/storage/deleteconfirm.webp) @@ -25,4 +25,4 @@ Storage Profile from this Enterprise Auditor Console. **Step 3 –** The profile disappears from the Storage Profiles list. Click **Save** and then **OK** to confirm the changes. -The Storage Profile has now been deleted. +You have now deleted the Storage Profile. diff --git a/docs/accessanalyzer/11.6/admin/settings/storage/overview.md b/docs/accessanalyzer/11.6/admin/settings/storage/overview.md index 5c0da1a117..4ce9f85f76 100644 --- a/docs/accessanalyzer/11.6/admin/settings/storage/overview.md +++ b/docs/accessanalyzer/11.6/admin/settings/storage/overview.md @@ -28,9 +28,8 @@ Each Storage Profile consists of the following parts: - Command Timeout – Number of minutes before Enterprise Auditor halts any SQL queries running for that amount of time. This prevents SQL queries from running excessively long. The default is 1440 minutes. -- Authentication – Mode of authentication to the SQL Server. In general, it is recommended to - connect with an account configured with the DBO role (database owner rights) and provisioned to - use DBO Schema. +- Authentication – Mode of authentication to the SQL Server. In general, use an account configured + with the DBO role (database owner rights) and provisioned to use DBO Schema. :::info When possible, use Windows Authentication. Windows Authentication is more @@ -40,7 +39,7 @@ Each Storage Profile consists of the following parts: ::: - - Windows authentication – Leverages the account used to run the Enterprise Auditor Console + - Windows authentication – Uses the account used to run the Enterprise Auditor Console :::note This option affects the credentials used for Schedule Service Accounts. See the @@ -49,16 +48,16 @@ Each Storage Profile consists of the following parts: ::: - - SQL Server authentication – Leverages the account provided in the **User name** and + - SQL Server authentication – Uses the account provided in the **User name** and **Password** textboxes - Use existing password – Use the password configured for the Storage Profile account - Specify a new password below – Enter a new password for the selected Storage Profile account - Database name – Name of the Enterprise Auditor database to use in this storage profile - - Use existing database – Drop-down menu provides a list of databases on the named SQL Server, + - Use existing database – dropdown menu provides a list of databases on the named SQL Server, provided the connection information supplied is correct. If the menu is empty, then a - connection to the SQL Server was not established. + connection to the SQL Server wasn't established. - Create new database – Enterprise Auditor automatically creates a new database using the name provided in the textbox. This value should be a unique, descriptive name. @@ -82,11 +81,11 @@ A green checkmark in the Storage Profiles list indicates the default Storage Pro The **Cancel** and **Save** buttons are in the lower-right corner of the Storage view. These buttons -become enabled when modifications are made to the Storage global setting. Whenever changes are made +become enabled when you make changes to the Storage global setting. Whenever you make changes at the global level, click **Save** and then **OK** to confirm the changes. Otherwise, click -**Cancel** if no changes were intended. +**Cancel** if you don't want to save the changes. -The vault provides enhanced security through enhanced encryption to various credentials stored by +The vault provides enhanced security through encryption for various credentials stored by the Enterprise Auditor application. See the [Vault](/docs/accessanalyzer/11.6/admin/settings/application/vault.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/admin/settings/storage/updateauth.md b/docs/accessanalyzer/11.6/admin/settings/storage/updateauth.md index 2515680d1d..b542c5cd40 100644 --- a/docs/accessanalyzer/11.6/admin/settings/storage/updateauth.md +++ b/docs/accessanalyzer/11.6/admin/settings/storage/updateauth.md @@ -6,8 +6,8 @@ sidebar_position: 20 # Update Authentication Credentials in a Storage Profile -Follow the steps to update authentication credentials for a Storage Profile in the Enterprise -Auditor Console. +To update authentication credentials for a Storage Profile in the Enterprise +Auditor Console: **Step 1 –** Navigate to the **Settings** > **Storage** page. @@ -21,4 +21,4 @@ Auditor Console. **Step 5 –** Click **Apply**. -A new password has been added to a Storage profile. +You have added a new password to the Storage profile. diff --git a/docs/accessanalyzer/11.6/cdsa/job.md b/docs/accessanalyzer/11.6/cdsa/job.md index ac0977cae4..8be1d1f50c 100644 --- a/docs/accessanalyzer/11.6/cdsa/job.md +++ b/docs/accessanalyzer/11.6/cdsa/job.md @@ -8,10 +8,10 @@ sidebar_position: 10 The CDSA Job is available through the Instant Job Library under the CDSA library. See the [Instant Job Wizard](/docs/accessanalyzer/11.6/admin/jobs/instantjobs/overview.md) -topic for instructions of how to add this instant job to the Jobs tree. When installing the job, +topic for instructions on adding this instant job to the Jobs tree. When installing the job, select **Local host** on the Host pages of the Instant Job Wizard. -Ensure the supporting solutions have successfully collected and analyzed data prior to running this +Ensure the supporting solutions have successfully collected and analyzed data before running this job. See the [Presentation Dependencies](/docs/accessanalyzer/11.6/cdsa/presentation.md) topic for alignment between presentation slides and jobs that supply the data points. @@ -30,7 +30,7 @@ The CDSA job generates three PowerPoint files: self-review as a PDF file :::warning -Do not send any these presentations to a customer in PowerPoint format. +Don't send any these presentations to a customer in PowerPoint format. ::: @@ -54,7 +54,7 @@ are two presentation options for the live slide show: - The **ePHI Security Assessment** slide show contains the ending slides with select summary slides from the Classic slide show and is applicable to the healthcare industry -Use the Custom Slide Show drop-down menu on the Slide Show ribbon in PowerPoint to select the +Use the Custom Slide Show dropdown menu on the Slide Show ribbon in PowerPoint to select the appropriate presentation. :::note @@ -63,7 +63,7 @@ Slide 17 is hidden by default as same information is available on Slides 18-20. Netwrix University includes a training module with details on the key talking points for a live -delivery of the slide shows. Check out the **315 – Getting Started with Credential & Data Security +delivery of the slide shows. Refer to the **315 – Getting Started with Credential & Data Security Assessment** training course. ## Choosing a PDF Version @@ -74,7 +74,7 @@ Both of the printable assets have two customized options for converting to a PDF - ePHI Security Assessment – Contains the ending slides with select summary slides from the Classic slide show and is applicable to the healthcare industry -Follow the steps to create the appropriate custom PDF. +To create the appropriate custom PDF: **Step 1 –** Use the **Save As** option. @@ -87,7 +87,7 @@ Follow the steps to create the appropriate custom PDF. **Step 5 –** Click **OK** to confirm the option, and then click **Save** to generate the PDF. -The presentation is converted to a PDF with only the applicable slides included. +You have now converted the presentation to a PDF with only the applicable slides included. :::note Slide 16 is hidden by default as same information is available on Slides 17-19. diff --git a/docs/accessanalyzer/11.6/cdsa/overview.md b/docs/accessanalyzer/11.6/cdsa/overview.md index 50f531df39..bd28e2d3f9 100644 --- a/docs/accessanalyzer/11.6/cdsa/overview.md +++ b/docs/accessanalyzer/11.6/cdsa/overview.md @@ -7,7 +7,7 @@ sidebar_position: 70 # Credential & Data Security Assessment Overview Proper data security begins with a strong foundation. The Credential & Data Security Assessment -(CDSA) provides a deep-dive into the security of your structured and unstructured data, Active +(CDSA) provides an in-depth analysis of the security of your structured and unstructured data, Active Directory, and Windows infrastructure. The CDSA job depends upon several Enterprise Auditor solutions for data collection. See the @@ -16,7 +16,7 @@ topic for installation and database requirements. ## Supporting Solutions -At a minimum the following solutions need to run prior to the CDSA job to provide the data used to +At a minimum the following solutions need to run before the CDSA job to provide the data used to generate the CDSA presentations: - .Active Directory Inventory Solution diff --git a/docs/accessanalyzer/11.6/cdsa/presentation.md b/docs/accessanalyzer/11.6/cdsa/presentation.md index 795a74482e..8db4c89934 100644 --- a/docs/accessanalyzer/11.6/cdsa/presentation.md +++ b/docs/accessanalyzer/11.6/cdsa/presentation.md @@ -9,7 +9,7 @@ sidebar_position: 20 In the following subsections, each slide is aligned to the jobs that supply its data. The slide number is specific to the **Netwrix_CDSA_Presentation.pptx** file, as there are slight various in page numbering with the files designed to be saved as PDFs. Many jobs contribute to multiple slides, -so jobs are highlighted in bold text the first time they are listed. +so this topic highlights each job in bold text the first time it's listed. ## Executive Summary Slide diff --git a/docs/accessanalyzer/11.6/gettingstarted.md b/docs/accessanalyzer/11.6/gettingstarted.md index 84dfec2e1c..5795894e5d 100644 --- a/docs/accessanalyzer/11.6/gettingstarted.md +++ b/docs/accessanalyzer/11.6/gettingstarted.md @@ -6,14 +6,14 @@ sidebar_position: 2 # Getting Started -Once Enterprise Auditor is installed, the following workflow will quickly enable users to begin -auditing the organization’s IT infrastructure. See the +After you install Enterprise Auditor, use the following workflow to quickly begin +auditing the organization's IT infrastructure. See the [Navigating the Console](/docs/accessanalyzer/11.6/admin/navigate/overview.md) topic for additional information and data grid functionality. ## Initial Configuration During First Launch -During the initial Enterprise Auditor Configuration Wizard, users are walked through configuring +The initial Enterprise Auditor Configuration Wizard walks you through configuring several key global settings: - Storage @@ -45,8 +45,8 @@ several key global settings: ## Global Settings Configured -The global Settings have an overall impact on the running of Enterprise Auditor jobs. They are -managed through the Settings node at the top of the Navigation pane. The following global Settings +The global Settings affect how Enterprise Auditor runs jobs. You manage them +through the Settings node at the top of the Navigation pane. The following global Settings require configuration from the start: - [Connection](/docs/accessanalyzer/11.6/admin/settings/connection/overview.md) @@ -58,15 +58,15 @@ require configuration from the start: - [Notification](/docs/accessanalyzer/11.6/admin/settings/notification.md) – Configure an SMTP server for Enterprise Auditor to use for sending email notifications -The other global Settings provide additional options for impacting how Enterprise Auditor functions: +The other global Settings provide additional options for how Enterprise Auditor functions: - [Access](/docs/accessanalyzer/11.6/admin/settings/access/overview.md) – Enable and configure Role Based Access for a least privileged application of Enterprise Auditor and report viewing or the enable the REST API :::note - If Role Based Access is enabled by accident, contact - [Netwrix Support](https://www.netwrix.com/support.html) for assistance in disabling it. + If you enable Role Based Access by accident, contact + [Netwrix Support](https://www.netwrix.com/support.html) for assistance disabling it. ::: @@ -76,8 +76,8 @@ The other global Settings provide additional options for impacting how Enterpris Configure Microsoft® Exchange Server connections :::warning -Do not configure data retention at the global level without ensuring History is -supported by ALL solutions to be run. +Don't configure data retention at the global level unless History supports all +the solutions you plan to run. ::: @@ -102,27 +102,27 @@ topic for additional information. ## Discover Hosts for Enterprise Auditor -Within the terminology of Enterprise Auditor, hosts are the machines being targeted during data -collection. Hosts can be discovered or manually introduced to Enterprise Auditor. Known hosts are -then inventoried to populate dynamic host lists. Host discovery is done at the Host Discovery  node. -Hosts are manually introduced at the Host Management node. +Within the terminology of Enterprise Auditor, hosts are the machines that Enterprise Auditor targets +during data collection. You can discover hosts or manually introduce them to Enterprise Auditor. +Enterprise Auditor then inventories known hosts to populate dynamic host lists. You perform host +discovery at the Host Discovery node. You manually introduce hosts at the Host Management node. -Host management consists of maintaining up-to-date host inventories and host lists which can be -assigned to job groups or jobs as targeted hosts. See the +Host management consists of maintaining up-to-date host inventories and host lists that you can +assign to job groups or jobs as targeted hosts. See the [Host Management](/docs/accessanalyzer/11.6/admin/hostmanagement/overview.md) topic for additional information. ## Enterprise Auditor Job Workflow -Once the global Settings are configured and hosts have been introduced to Enterprise Auditor, it is +After you configure the global Settings and introduce hosts to Enterprise Auditor, it's time to begin auditing. This requires an understanding of the relationship between solutions, job groups, jobs, queries, analysis, actions, and reports. The Enterprise Auditor job is the fundamental unit. Jobs are responsible for all data collection queries, analysis tasks, notification tasks, action tasks, and report generation. When Jobs are designed to work together, they are housed within job groups to control the order of job execution. -Solutions are pre-configured job groups which have been designed to target specific types of -environments to audit for specific data sets, typically the most common types of information +Solutions are pre-configured job groups that Netwrix designed to target specific types of +environments and audit specific data sets, typically the most common types of information desired. See the [Jobs Tree](/docs/accessanalyzer/11.6/admin/jobs/overview.md) diff --git a/docs/accessanalyzer/11.6/index.md b/docs/accessanalyzer/11.6/index.md index d27a560bab..d786835a82 100644 --- a/docs/accessanalyzer/11.6/index.md +++ b/docs/accessanalyzer/11.6/index.md @@ -18,8 +18,8 @@ The platform framework contains the following key components: - Reporting through Published Reports and the Web Console Enterprise Auditor contains over 40 built-in data collection modules covering both on-premises and -cloud-based platforms from Operating Systems to Office 365. Leveraging an agentless architectural -approach, our proprietary AnyData collector provides an easy, wizard-driven interface for +cloud-based platforms from Operating Systems to Office 365. Using an agentless architectural +approach, the proprietary AnyData collector provides a wizard-driven interface for configuring the application to collect exactly the data needed, enabling fast, flawless, lightest-weight possible data collection from dozens of data sources. @@ -84,8 +84,8 @@ topic for additional information. ### Active Directory Permissions Analyzer Solution -The Active Directory Permissions Analyzer Solution is designed to easily and automatically determine -effective permissions applied to any and all Active Directory objects, at any scope, allowing for +The Active Directory Permissions Analyzer Solution is designed to automatically determine +effective permissions applied to any and all Active Directory objects, at any scope, providing the most authoritative view available of who has access to what in Active Directory. See the @@ -117,7 +117,7 @@ topic for additional information. ### Box Solution The Box solution set contains jobs to provide visibility into Box access rights, policies, -configurations, activities, and more, ensuring you never lose sight or control of your critical +configurations, activities, and more, ensuring you maintain visibility and control over your critical assets residing in Box. See the @@ -138,18 +138,18 @@ reports that provide visibility into various aspects of supported databases. - Instance Discovery – The Instance Discovery Solution discovers instances on supported database servers. - MongoDB Solution – The MongoDB Solution automates the process of understanding where MongDB - databases exist and provides an overview of the MongoDB environment in order to answer questions - around data access. With visibility into every corner of MongoDB and the operating system it + databases exist and provides an overview of the MongoDB environment to answer questions + around data access. With visibility into all aspects of MongoDB and the operating system it relies upon, organizations can proactively highlight and prioritize risks to sensitive data. Additionally, organizations can automate manual, time-consuming, and expensive processes - associated with compliance, security, and operations to easily adhere to best practices that keep + associated with compliance, security, and operations to adhere to best practices that keep MongoDB Server safe and operational. - MySQL Solution – The MySQL Solution automates the process of understanding where SQL databases - exist and provides an overview of the MySQL environment in order to answer questions around data - access. With visibility into every corner of Microsoft SQL Server and the Windows operating system + exist and provides an overview of the MySQL environment to answer questions around data + access. With visibility into all aspects of Microsoft SQL Server and the Windows operating system it relies upon, organizations can proactively highlight and prioritize risks to sensitive data. Additionally, organizations can automate manual, time-consuming, and expensive processes - associated with compliance, security, and operations to easily adhere to best practices that keep + associated with compliance, security, and operations to adhere to best practices that keep SQL Server safe and operational. - Oracle Solution – The Oracle Solution delivers comprehensive permissions, activity, and sensitive data auditing and reporting for Oracle databases. Through the power of Enterprise Auditor, users diff --git a/docs/accessanalyzer/11.6/install/application/database/database.md b/docs/accessanalyzer/11.6/install/application/database/database.md index b406917e67..4b4453818d 100644 --- a/docs/accessanalyzer/11.6/install/application/database/database.md +++ b/docs/accessanalyzer/11.6/install/application/database/database.md @@ -7,19 +7,19 @@ sidebar_position: 10 # Enterprise Auditor Database The Enterprise Auditor database is dynamic in nature. There are a handful of required system tables -which are created at installation time or when individual features are used the first time. All -other data tables in the Enterprise Auditor database are created and bound to individual jobs which -are added to the Enterprise Auditor Console. As jobs are created and modified, corresponding tables -are created and modified in the database. A job can generate one or more tables. +that Enterprise Auditor creates at installation time or when you use individual features for the +first time. Enterprise Auditor creates and binds all other data tables in the database to individual +jobs that you add to the Enterprise Auditor Console. As you create and modify jobs, Enterprise +Auditor creates and modifies corresponding tables in the database. A job can generate one or more tables. -The structure and schema of each data table is controlled by the Enterprise Auditor data collector -used to collect data and write results to the table. There is a one-to-one relationship between a +The Enterprise Auditor data collector that collects data and writes results to the table controls +the structure and schema of each data table. There is a one-to-one relationship between a task created within a Enterprise Auditor job and the table to which the task writes results. Creating tasks or adding and removing properties within a task modifies the schema of the table on subsequent execution of the job. Enterprise Auditor offers users the ability to modify its preconfigured jobs or create custom jobs -and tasks as needed. Therefore, precise schema information for data tables cannot be predicted, +and tasks as needed. Therefore, precise schema information for data tables can't be predicted, restricted, or locked down. ## Database Permissions @@ -34,8 +34,8 @@ access to the database. ::: -If database owner rights cannot be obtained, the following SQL script can be executed by a database -administrator (DBA) against the Enterprise Auditor database to grant the necessary permissions to +If you can't obtain database owner rights, a database administrator (DBA) can execute the following +SQL script against the Enterprise Auditor database to grant the necessary permissions to the appropriate users (replacing `` and `` with the appropriate values): ``` @@ -85,17 +85,17 @@ Enterprise Auditor. user-configured time frame - Reporting Needs – Anticipated data needed to generate reports -Recommended SQL Server database sizes are provided for specific solutions in the +The [Requirements](/docs/accessanalyzer/11.6/requirements/overview.md) -topics. These recommendations are based on environmental factors, the number of target objects -within an environment (users, hosts, mailboxes, etc.), and the applicable factors listed above for -the specific solution. +topics provide recommended SQL Server database sizes for specific solutions. These recommendations +are based on environmental factors, the number of target objects within an environment (users, +hosts, mailboxes, etc.), and the applicable factors described earlier for the specific solution. ### Customer Examples of Database Sizing -The overall database size is ultimately governed by an organization’s auditing objectives. The -examples below provide a glimpse into how these objectives combine with the applicable factors above -to impact the Enterprise Auditor database resource consumption. +An organization's auditing objectives ultimately govern the overall database size. The +following examples provide a glimpse into how these objectives combine with the applicable factors +described earlier to impact the Enterprise Auditor database resource consumption. - Example from an Active Directory Solution Customer - An Active Directory (AD) customer intends to collect AD User/Group/Membership information and @@ -115,8 +115,8 @@ to impact the Enterprise Auditor database resource consumption. information on file permissions and ages (and possibly, ad hoc, information on file system activity) with an overall plan to identify stale data, consolidate active data on a subset of the organization’s file system infrastructure, and to move that active data to a cloud-based - platform like SharePoint Online. Activity monitoring (FSAC) is to be used ad hoc against open - shares to profile resource ownership and also to validate the “staleness” of certain + platform like SharePoint Online. The customer plans to use Activity monitoring (FSAC) ad hoc against open + shares to profile resource ownership and validate the “staleness” of certain resources. The database sizing for a project of this scope could be up to 750 GB for the database, 240 GB for the transaction log, and 380 GB of TEMPDB space. - Example from an Exchange Solution Customer @@ -131,12 +131,12 @@ to impact the Enterprise Auditor database resource consumption. ## Securing the Enterprise Auditor Database -The typical database configuration is to have **sysadmin Server Role** assigned to the ID used to -connect to the SQL instance. It will allow full control over the instance where the Enterprise -Auditor database resides. This configuration is chosen because Enterprise Auditor requires some -interaction with the master database in order to install and configure the initial Enterprise -Auditor database. When it is necessary to secure the Enterprise Auditor database, the following -steps should be followed to achieve the minimum SQL security levels without breaking core Enterprise +The typical database configuration assigns the **sysadmin Server Role** to the ID used to +connect to the SQL instance, which allows full control over the instance where the Enterprise +Auditor database resides. Administrators typically choose this configuration because Enterprise +Auditor requires some interaction with the master database to install and configure the initial +Enterprise Auditor database. To secure the Enterprise Auditor database, follow these +steps to achieve the minimum SQL security levels without breaking core Enterprise Auditor functionality. ### Database Creation & First Level of Security @@ -146,7 +146,7 @@ settings for the server roles and user mappings. ![SQL Server Management Studio create New Database](/images/accessanalyzer/11.6/install/application/createnewdatabase.webp) -**Step 1 –** Create a new database for use with Enterprise Auditor. Right-click on the **Databases** +**Step 1 –** Create a new database for use with Enterprise Auditor. Right-click the **Databases** node and choose **New Database**. ![SQL Server Management Studio New Database window](/images/accessanalyzer/11.6/install/application/newdatabase.webp) @@ -170,17 +170,17 @@ authentication. ![SQL Server Management Studio new login with Windows authentication](/images/accessanalyzer/11.6/install/application/loginwindows.webp) -- If **Windows authentication** is desired, then click **Search** and select the desired Windows - account, which has been set up for use with Enterprise Auditor. +- If you want **Windows authentication**, click **Search** and select the Windows + account you want, which is set up for use with Enterprise Auditor. ![SQL Server Management Studio new login with SQL Server authentication](/images/accessanalyzer/11.6/install/application/loginsql.webp) -- **_RECOMMENDED:_** If **SQL Server authentication** is desired, use a login name called Enterprise +- **_RECOMMENDED:_** If you want **SQL Server authentication**, use a login name called Enterprise Auditor. :::note -Set the **Default Database** as Enterprise Auditor (or the desired Enterprise Auditor -database) and choose English as the **Default Language**. +Set the **Default Database** as Enterprise Auditor (or the Enterprise Auditor +database you want) and choose English as the **Default Language**. ::: @@ -216,24 +216,24 @@ topic for instructions. ![Connection report window](/images/accessanalyzer/11.6/install/application/connectionreport.webp) -- Click **Apply** and a Connection report window will open. Verify that the connection and test - table drop were performed successfully. +- Click **Apply** and a Connection report window will open. Verify that Enterprise Auditor + performed the connection and test table drop successfully. - Click **Close** on the Connection report window and then **Save** the new Storage Profile. ![Change storage profile dialog](/images/accessanalyzer/11.6/install/application/changestorageprofile.webp) :::note -If previously connected to another database which already had the Enterprise Auditor DB -schema applied, then a prompt should appear to merge the host management data. Choose the +If you previously connected to another database that already had the Enterprise Auditor DB +schema applied, a prompt should appear to merge the host management data. Choose the appropriate options and then click **OK** to migrate data. ::: -**Step 9 –** Make sure to close and re-open the Enterprise Auditor Console before continuing to -configure or use Enterprise Auditor if a new database Storage Profile was chosen as the default. +**Step 9 –** Close and reopen the Enterprise Auditor Console before continuing to +configure or use Enterprise Auditor if you chose a new database Storage Profile as the default. -The **blue arrow** signifies the default profile was changed but does not take effect until the -required restart of the Enterprise Auditor Console. +The **blue arrow** signifies that you changed the default profile, but the change doesn't take +effect until you restart the Enterprise Auditor Console. See the [Enterprise Auditor Initial Configuration](/docs/accessanalyzer/11.6/install/application/firstlaunch.md) diff --git a/docs/accessanalyzer/11.6/install/application/database/otherlanguages.md b/docs/accessanalyzer/11.6/install/application/database/otherlanguages.md index 24b43343f4..934a10a05c 100644 --- a/docs/accessanalyzer/11.6/install/application/database/otherlanguages.md +++ b/docs/accessanalyzer/11.6/install/application/database/otherlanguages.md @@ -11,7 +11,7 @@ Language environment, specifically when the environment uses a non-Latin alphabe ## Requirements -The following collation requirements need to be met prior to the Enterprise Auditor installation. +You must meet the following collation requirements before installing Enterprise Auditor. ### Database & Server Collation Settings @@ -21,11 +21,11 @@ The collation settings at the database level must match what is set at the serve Common errors that occur are: -- Implicit conversion of VARCHAR value to VARCHAR cannot be performed because the collation of the +- Implicit conversion of VARCHAR value to VARCHAR can't be performed because the collation of the value is unresolved due to a collation conflict. - - Could not find stored procedure `#SA_ImportObject` - - Cannot drop the procedure `#SA_ImportObject`, because it does not exist or lack of permission -- Cannot resolve the collation conflict between **SQL_Latin1_General_CP1_CI_AS** and + - Couldn't find stored procedure `#SA_ImportObject` + - Can't drop the procedure `#SA_ImportObject`, because it doesn't exist or lack of permission +- Can't resolve the collation conflict between **SQL_Latin1_General_CP1_CI_AS** and **French_CI_AS** in the equal to operation. **Cause** @@ -33,20 +33,20 @@ Common errors that occur are: These errors occur because the Enterprise Auditor solutions use many temporary functions and procedures which in turn use the collation at the server level. Temporary tables created within a stored procedure use the TEMPDB database’s collation instead of the current user database’s -collation. Therefore, there will be issues in analysis due to the mismatch. +collation. Therefore, the mismatch causes issues in analysis. **Resolution** -The following is a work-around which we use to avoid collation errors. However, when making changes +The following is a work-around used to avoid collation errors. However, when making changes at the SQL Server level, use caution as it actually rebuilds all user/system database objects. If -there are schema bound objects (i.e. Constraints), the whole operation will fail. Make sure to have +there are schema bound objects (i.e. Constraints), the whole operation will fail. ensure to have all of the information or scripts needed to recreate the Enterprise Auditor user’s databases and all of the objects in them. Customers should use a localized version of the SQL Server, and this should not be done in production environments. #### Change Collation at the Database Level -Follow the steps to change the collation at the database level. +To change the collation at the database level: **Step 1 –** Access the Database Properties in SQL Server Management Studio. @@ -58,7 +58,7 @@ Now that the collations match, proceed with Enterprise Auditor installation. #### Change Collation at the SQL Server Level -Follow the steps to change the collation at the SQL Server level. +To change the collation at the SQL Server level: ![SQL Server Configuration Manager](/images/accessanalyzer/11.6/install/application/sqlserverconfigurationmanager.webp) @@ -87,13 +87,13 @@ Now that the collations match, proceed with Enterprise Auditor installation. ### Case Sensitive Collation -Enterprise Auditor does not support case sensitive collation settings. Case insensitive collations +Enterprise Auditor doesn't support case sensitive collation settings. Case insensitive collations are notated by having **CI** in the collation, for example **Latin1_General_CI_AS**. **Cause** -For example, `SYS.INDEXES` will be unable to be found if there was an English install of SQL Server -but a Turkish collation which is case sensitive. So `'SYS.INDEXES != 'sys.indexes' `in the +For example, if there was an English install of SQL Server but a case-sensitive Turkish +collation, the system won't find `SYS.INDEXES`. So `'SYS.INDEXES != 'sys.indexes' `in the environment. **Resolution** @@ -104,10 +104,10 @@ All collation settings must be case insensitive. The following are possible problems for future consideration. -During comparison or joining of columns, collation conflict error occurs in two cases if collation -of one column does not match with collation of another column: +During comparison or joining of columns, a collation conflict error occurs in two cases if one +column's collation doesn't match another column's: -This can be generated by the following script: +The following script generates this: ``` CREATE TABLE TestTab @@ -119,18 +119,18 @@ INSERT INTO TestTab VALUES (1, 'abc', 'abc')  SELECT * FROM TestTab WHERE CharCol = CharCol2 ``` -- Error Returned – Cannot resolve the collation conflict between **Greek_CI_AS** and +- Error Returned – Can't resolve the collation conflict between **Greek_CI_AS** and **French_CI_AS** in the equal to operation. -- Resolution – If the select statement is changed as below, then it would run successfully. +- Resolution – If you change the select statement as follows, it runs successfully. ``` SELECT * FROM TestTab WHERE CharCol = CharCol2 COLLATE Albanian_CI_AI ``` :::note -Explicit collation (Albanian_CI_AI) is not one of any column, but after that it will -complete successfully. The collation of two columns have not been matched, instead the third rule of -collation precedence was implemented. See the Microsoft +Explicit collation (Albanian_CI_AI) isn't one of any column, but the query still +completes successfully. The two columns' collations don't match; instead, SQL Server applies the +third rule of collation precedence. See the Microsoft [Collation Precedence](https://learn.microsoft.com/en-us/sql/t-sql/statements/collation-precedence-transact-sql) article for additional information. ::: diff --git a/docs/accessanalyzer/11.6/install/application/firstlaunch.md b/docs/accessanalyzer/11.6/install/application/firstlaunch.md index 79eb01a463..fb34dd781e 100644 --- a/docs/accessanalyzer/11.6/install/application/firstlaunch.md +++ b/docs/accessanalyzer/11.6/install/application/firstlaunch.md @@ -6,8 +6,8 @@ sidebar_position: 30 # Enterprise Auditor Initial Configuration -Once the Enterprise Auditor installation process is complete, and before performing actions within -Enterprise Auditor, the initial settings for the Enterprise Auditor Console must be configured. +After the Enterprise Auditor installation process finishes, and before performing actions within +Enterprise Auditor, configure the initial settings for the Enterprise Auditor Console. ![Newrix Access Governance shortcut](/images/accessanalyzer/11.6/install/application/shortcut.webp) @@ -47,22 +47,22 @@ topic for additional information. - Command timeout [number] minutes – Number of minutes before Enterprise Auditor halts any SQL queries running for that amount of time. This prevents SQL queries from running excessively long. The default is 1440 minutes. -- Windows authentication – Leverages the account used to open the Enterprise Auditor Console. This +- Windows authentication – Uses the account used to open the Enterprise Auditor Console. This option will use Windows NT Authentication to authenticate to the SQL Server. It also requires the Schedule Service Account to have proper permissions on the SQL database. -- SQL Server authentication – Leverages an account created within the SQL Server. +- SQL Server authentication – Uses an account created within the SQL Server. - User name and password – If SQL Server authentication is selected, provide the **User name** and **Password** for the SQL account. - Specify a new password below – Specify a new password for the SQL server. -- Use existing database – Confirm the SQL Server connection has been established by selecting the - radio button for **Use existing database** and clicking the drop-down arrow. If a listing of - databases appears, then the connection has been established. Select this option to use a - pre-existing database. Then select a database from the drop-down menu of available databases. +- Use existing database – Confirm that the SQL Server connection succeeded by selecting the + radio button for **Use existing database** and clicking the dropdown arrow. If a listing of + databases appears, the connection succeeded. Select this option to use a + pre-existing database. Then select a database from the dropdown menu of available databases. - Create new database – Select this option to create a new database during the configuration of the storage profile. Enter a unique, descriptive name for the new database. If multiple databases - might exist for Enterprise Auditor, then the default name of Enterprise Auditor is not + might exist for Enterprise Auditor, then the default name of Enterprise Auditor isn't recommended. See the @@ -71,9 +71,10 @@ topic for additional information on creating a SQL Server database for Enterpris **Step 5 –** Click **Next**. -- If SQL Server authentication is used, the Options page is displayed next. Skip to Step 7. -- If Windows Server authentication is used, the **Schedule Account** page is enabled for - configuration. Continue to Step 6. +- If you use SQL Server authentication, Enterprise Auditor displays the Options page next. Skip to + Step 7. +- If you use Windows Server authentication, Enterprise Auditor enables the **Schedule Account** + page for configuration. Continue to Step 6. ![Schedule Account Configuration page](/images/accessanalyzer/11.6/install/application/scheduleaccount.webp) @@ -82,7 +83,7 @@ page. The account configured here must be an Active Directory account and must h Enterprise Auditor Console server’s local Task folders as well as sufficient rights to the Enterprise Auditor database. -There are two options that can be selected: +You can select one of two options: - Skip this step, I will configure a schedule service account later – Select this radio button to skip this step and configure the schedule service account later @@ -96,20 +97,20 @@ There are two options that can be selected: ![Configuration wizard Options page](/images/accessanalyzer/11.6/install/application/options.webp) -**Step 7 –** On the Options page, select whether to send usage statistics to Netwrix to help us -improve our product. After the Usage Statistics option is set as desired, click **Next** to +**Step 7 –** On the Options page, select whether to send usage statistics to Netwrix to help +improve the product. After you set the Usage Statistics option as desired, click **Next** to continue. - If selected, usage statistics are collected and sent to Netwrix - - Upon startup of the Enterprise Auditor console, the system checks if usage statistics have - been sent in the last 7 days. If they have not been, stored procedures run against the + - Upon startup of the Enterprise Auditor console, the system checks whether it sent usage + statistics in the last 7 days. If not, stored procedures run against the Enterprise Auditor database and gather data about job runs, access times, and environmental - details like resource counts, users counts, number of exceptions, and so on. This data is then - sent back to Netwrix to help us identify usage trends and common pain points, so that we can - use this information to improve the product. - - Only anonymous statistic-level data is included. No private company or personal data is - collected or sent to Netwrix. + details like resource counts, user counts, number of exceptions, and so on. Enterprise Auditor + then sends this data back to Netwrix to help identify usage trends and common problem areas, + which Netwrix uses to improve the product. + - Enterprise Auditor includes only anonymous statistic-level data. It doesn't collect or send + private company or personal data to Netwrix. - If cleared, no usage statistics are collected or sent to Netwrix @@ -130,7 +131,7 @@ topic for more information about logs. ![Netwrix Acces Governance Settings Node](/images/accessanalyzer/11.6/install/application/settingsnode.webp) The Enterprise Auditor Console is now ready for custom configuration and use. There are a few -additional steps to complete in order to begin collecting data, such as configuring a Connection +additional steps to complete to begin collecting data, such as configuring a Connection Profile and a Schedule Service account as well as discovering hosts and setting up host lists. See the [Getting Started](/docs/accessanalyzer/11.6/gettingstarted.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/install/application/overview.md b/docs/accessanalyzer/11.6/install/application/overview.md index 7145cb1cf8..1583ab308d 100644 --- a/docs/accessanalyzer/11.6/install/application/overview.md +++ b/docs/accessanalyzer/11.6/install/application/overview.md @@ -11,7 +11,7 @@ required when first launching the Enterprise Auditor Console. It also includes a information, such as how to secure the Enterprise Auditor Database, and configuring the Web Console for viewing reports outside of the Enterprise Auditor Console. -Prior to installing Enterprise Auditor, please ensure that all of the prerequisites have been met. +Before installing Enterprise Auditor, ensure that you've met all the prerequisites. See the [Requirements](/docs/accessanalyzer/11.6/requirements/overview.md) topic for more information. @@ -24,8 +24,8 @@ Your Netwrix Representative will provide the appropriate binaries. - Enterprise Auditor binary – Core installation package - Includes data collectors, analysis modules, and action modules - - An organization’s license key, needed during installation, controls which components are laid - down during installation + - An organization’s license key, needed during installation, controls which components the + installer includes - Installs the Web Console - File System Proxy binary – Installation package for the File System Proxy Scanning option diff --git a/docs/accessanalyzer/11.6/install/application/reports/adfs.md b/docs/accessanalyzer/11.6/install/application/reports/adfs.md index e29140093d..e52f7ea55e 100644 --- a/docs/accessanalyzer/11.6/install/application/reports/adfs.md +++ b/docs/accessanalyzer/11.6/install/application/reports/adfs.md @@ -6,11 +6,11 @@ sidebar_position: 80 # Configuring the Web Console to use ADFS -The Enterprise Auditor Webserver and Access Information Center are able to support Single-Sign-On +The Enterprise Auditor Webserver and Access Information Center can support Single-Sign-On (SSO) leveraging WSFederation with SAML tokens. This guide contains steps for implementing SSO using Active Directory Federation Services (ADFS). -Follow the steps to configure the Web Console to use ADFS authentication: +To configure the Web Console to use ADFS authentication: :::note A certificate from the ADFS server is required. Confer with a PKI administrator to @@ -21,7 +21,7 @@ determine which certificate method will conform to the organization's security p **Step 1 –** Import the certificate for the ADFS server onto the hosting server using the Certificate Management MMC snap-in. -- If used, self-signed certificates will also need to be imported +- If you use self-signed certificates, you'll also need to import them **Step 2 –** On the ADFS server, open **AD FS Management**. @@ -33,7 +33,7 @@ Add Relying Party Trust Wizard to configure the relying party trust: **Next**. - On the Specify Display Name page, enter a display name for the relying party trust. Click **Next**. -- On the Configure URL page, do not select any options and click **Next**. +- On the Configure URL page, don't select any options and click **Next**. ![Identifier added on the Configure Identifiers page](/images/accessanalyzer/11.6/install/application/reports/relyingpartytrustwizardidentifier.webp) @@ -46,7 +46,7 @@ Add Relying Party Trust Wizard to configure the relying party trust: ![Add an Endpoint window](/images/accessanalyzer/11.6/install/application/reports/addanendpointwindow.webp) -**Step 4 –** Double-click on the newly added relying party trust to open it's Properties window. +**Step 4 –** Double-click the newly added relying party trust to open it's Properties window. Navigate to the Endpoints tab and click **Add WS-Federation**. On the Add an Endpoint window, add `https://:/federation` as the Trusted URL, then click **OK**. @@ -65,7 +65,7 @@ right-hand panel. - On the Configure Claim Rule page, enter a name in the **Claim rule name** field. -If the SID claim is not configured by default, add it to the Claim Description as follows: +If the SID claim isn't configured by default, add it to the Claim Description as follows: ![Configure Claim Rule SID Properties](/images/accessanalyzer/11.6/install/application/reports/claimrulenamesidproperties.webp) @@ -120,13 +120,13 @@ The following is an example of how the parameters should look when configured in **Step 9 –** Navigate to Services (`services.msc`). Restart the **Enterprise Auditor Web Server** service. -ADFS authentication is now enabled for Enterprise Auditor. +You have now enabled ADFS authentication for Enterprise Auditor. ## Update the Published Reports URL for ADFS -If ADFS does not accept `http://localhost:8082/` as an acceptable path, the path will need to be -updated in the Published Reports properties window. Follow the steps to configure the Published -Reports URL for ADFS: +If ADFS doesn't accept `http://localhost:8082/` as an acceptable path, you'll need to update the +path in the Published Reports properties window. To configure the Published +Reports URL for ADFS: **Step 1 –** Right-click the Published Reports shortcut on the desktop and select **Properties**. @@ -136,4 +136,4 @@ Reports URL for ADFS: **Step 3 –** Click **Apply**. Exit the window. -The Published Reports URL is now configured for ADFS. +You have now configured the Published Reports URL for ADFS. diff --git a/docs/accessanalyzer/11.6/install/application/reports/disclaimer.md b/docs/accessanalyzer/11.6/install/application/reports/disclaimer.md index d7832496dc..5b2d360a07 100644 --- a/docs/accessanalyzer/11.6/install/application/reports/disclaimer.md +++ b/docs/accessanalyzer/11.6/install/application/reports/disclaimer.md @@ -8,7 +8,7 @@ sidebar_position: 70 Users can add a disclaimer message to the logon screen by adding a custom `Disclaimer.txt` file in the Web folder in the Enterprise Auditor directory and configuring the `WebServer.exe.config` file. -Follow the steps to configure the optional disclaimer message: +To configure the optional disclaimer message: **Step 1 –** Navigate to the Web folder of the installation directory: ` …\STEALTHbits\StealthAUDIT\Web`. @@ -18,8 +18,8 @@ Follow the steps to configure the optional disclaimer message: **Step 2 –** Create a `Disclaimer.txt` file in the Web folder. Write a custom disclaimer that displays on the login page for the Web Console. -- The text file must be named `Disclaimer.txt`. The disclaimer message option is not configured - properly if using a text file with a different name. +- You must name the text file `Disclaimer.txt`. The disclaimer message option isn't configured + properly if you use a text file with a different name. ![File Explorer WebServer.exe.config](/images/accessanalyzer/11.6/install/application/reports/webserverexeconfigfile.webp) @@ -43,10 +43,10 @@ displays on the login page for the Web Console. ![Web Console login page with disclaimer message](/images/accessanalyzer/11.6/install/application/reports/webconsolelogindisclaimer.webp) -**Step 7 –** To check if the disclaimer message was configured correctly, open the Web Console to +**Step 7 –** To check whether you configured the disclaimer message correctly, open the Web Console to access the login page. -- If the disclaimer is configured correctly, the custom disclaimer message displays at the bottom of +- If you configured the disclaimer correctly, the custom disclaimer message displays at the bottom of the login page. The disclaimer message displays on the Web Console login page. diff --git a/docs/accessanalyzer/11.6/install/application/reports/domains.md b/docs/accessanalyzer/11.6/install/application/reports/domains.md index 099995bc1c..caa1a5942e 100644 --- a/docs/accessanalyzer/11.6/install/application/reports/domains.md +++ b/docs/accessanalyzer/11.6/install/application/reports/domains.md @@ -8,23 +8,23 @@ sidebar_position: 30 When the `AuthenticationDomains` parameter in the **WebServer.exe.config** file is blank, only domain users from the domain where the Enterprise Auditor Console resides can access the Web -Console. Access can be granted from other domains when specified within this parameter. +Console. You can grant access from other domains by specifying them within this parameter. :::note -Once another domain is added, then it is necessary to also add the domain where the +After adding another domain, also add the domain where the Enterprise Auditor Console resides. ::: All domains provided or enumerated must have a trust relationship with the domain where Enterprise -Auditor resides. Follow the steps to allow access to the Web Console from other domains. +Auditor resides. To allow access to the Web Console from other domains: **Step 1 –** Open the **WebServer.exe.config** file with a text editor, for example Notepad. It is located within the Web folder of the Enterprise Auditor installation directory. ![WebServer.exe.config file in Notepad](/images/accessanalyzer/11.6/install/application/reports/webserverexeconfigmultipledomains.webp) -**Step 2 –** Add the desired domains to the value for the `AuthenticationDomains` parameter: +**Step 2 –** Add the domains you want to the value for the `AuthenticationDomains` parameter: ``` @@ -41,10 +41,10 @@ Use domain name in a comma-separated list. For example: **Step 4 –** Navigate to Services (`services.msc`). Restart the Enterprise Auditor Web Server service. -The Web Console can now be accessed from multiple domains. +You can now access the Web Console from multiple domains. :::note -In order for the AIC to be accessed from these domains, this must also be configured for +To allow access to the AIC from these domains, you must also configure this for the AIC. See the Multiple Domains topic in the [Netwrix Access Information Center Documentation](https://helpcenter.netwrix.com/category/accessinformationcenter) for additional information. diff --git a/docs/accessanalyzer/11.6/install/application/reports/entraidsso.md b/docs/accessanalyzer/11.6/install/application/reports/entraidsso.md index 6c0ee7bebd..cba202c184 100644 --- a/docs/accessanalyzer/11.6/install/application/reports/entraidsso.md +++ b/docs/accessanalyzer/11.6/install/application/reports/entraidsso.md @@ -6,9 +6,9 @@ sidebar_position: 50 # Microsoft Entra ID Single Sign-On -Microsoft Entra ID Single Sign-On (SSO) can be configured for logging in to the Web Console to view -reports. When configured, users accessing the Web Console are directed to the Microsoft Entra -ID login page, and can log in using their existing Entra credentials. +You can configure Microsoft Entra ID Single Sign-On (SSO) for logging in to the Web Console to view +reports. When configured, the Web Console directs users to the Microsoft Entra +ID login page, where they can log in using their existing Entra credentials. The following is required to use Microsoft Entra ID SSO: @@ -20,9 +20,9 @@ ID, and then configure the Web Console to use it. ## Configure an Application in Microsoft Entra ID -An application must be registered for the Web Console with your Microsoft Entra ID tenant and be -configured with the necessary single sign-on settings. Follow the steps to create and configure the -application. +You must register an application for the Web Console with your Microsoft Entra ID tenant and +configure it with the necessary single sign-on settings. To create and configure the +application: **Step 1 –** Sign into the [Microsoft Entra admin center](https://entra.microsoft.com/). @@ -52,8 +52,8 @@ Configuration section. Add your Identifier and Reply URL, and then click **Save* https://app0190.train90.local:8082/federation ``` -**Step 6 –** Next, click **Edit** on the Attributes & Claims section. The four claims in the table -below are required. For each of these, click **Add new claim**, enter the information from the +**Step 6 –** Next, click **Edit** on the Attributes & Claims section. The four claims in the +following table are required. For each of these, click **Add new claim**, enter the information from the table, and then click **Save**. | Name | Namespace | Source attribute | @@ -63,23 +63,23 @@ table, and then click **Save**. | sid | http://schemas.xmlsoap.org/ws/2005/05/identity/claims | user.onpremisessecurityidentifier | | upn | http://schemas.xmlsoap.org/ws/2005/05/identity/claims | user.onpremisesuserprincipalname | -Once configured they should show under Additional claims as below: +Once configured, they should show under Additional claims as follows: ![Claims configured](/images/accessanalyzer/11.6/install/application/reports/entraidssoclaims.webp) **Step 7 –** In the **Manage** > **Users and groups** section for your application, add any required users or groups to give permission to access the application. -The application is now configured with the necessary settings. The next step is to enable the use of -Microsoft Entra ID SSO in the web server config file. +You have now configured the application with the necessary settings. The next step is to enable the +use of Microsoft Entra ID SSO in the web server config file. ## Enable in the Web Server Config File -To enable Microsoft Entra ID SSO for the Web Console, the web server config file needs to be updated -with values from Microsoft Entra ID. Follow the steps to enable the SSO. +To enable Microsoft Entra ID SSO for the Web Console, you need to update the web server config file +with values from Microsoft Entra ID. To enable the SSO: :::tip -Remember, Enabling Entra ID SSO requires SSL to already have been enabled for the web server. See +Before enabling Entra ID SSO, make sure you've already enabled SSL for the web server. See the [Securing the Web Console](/docs/accessanalyzer/11.6/install/application/reports/secure.md) topic for additional information. @@ -122,4 +122,4 @@ For example: **Step 4 –** Navigate to Services (`services.msc`). Restart the Netwrix Enterprise Auditor Web Server service. -The Web Console has been enabled for Microsoft Entra ID single sign-on. +You have now enabled the Web Console for Microsoft Entra ID single sign-on. diff --git a/docs/accessanalyzer/11.6/install/application/reports/kerberosencryption.md b/docs/accessanalyzer/11.6/install/application/reports/kerberosencryption.md index 17a8d67c76..3e811ebec4 100644 --- a/docs/accessanalyzer/11.6/install/application/reports/kerberosencryption.md +++ b/docs/accessanalyzer/11.6/install/application/reports/kerberosencryption.md @@ -10,28 +10,28 @@ If a computer's Local Security Policy, or applicable Group Policy, enforces cert methods for Kerberos authentication, then the service account running the Enterprise Auditor Web Server must support the same encryption methods. -If encryption methods have been configured for Kerberos on the Enterprise Auditor server but not on -the service account running the Enterprise Auditor Web Server service, then users will not be able -to log-in to the Web Console and will receive the below error message. +If you configured encryption methods for Kerberos on the Enterprise Auditor server but not on +the service account running the Enterprise Auditor Web Server service, users won't be able +to log in to the Web Console and will receive the following error message. ![Kerberos Error Message](/images/accessanalyzer/11.6/install/application/reports/kerberoserrormessage.webp) -When this occurs, the following error will be logged: +When this occurs, Enterprise Auditor logs the following error: _ERROR - Unhandled server error: Nancy.RequestExecutionException: Oh noes! ---> -System.Security.SecurityException: The encryption type requested is not supported by the KDC_. +System.Security.SecurityException: The encryption type requested isn't supported by the KDC_. -This error will be logged in the following location: +Enterprise Auditor logs this error in the following location: **%SAINSTALLDIR%\SADatabase\Logs\Web\service.log** -While it is not required to configure these settings, this section provides the locations and steps +While you don't need to configure these settings, this section provides the locations and steps necessary to configure encryption methods in Local and Group policies to allow Kerberos for the -Report Index if an error does occur. +Report Index if an error occurs. ## Local Security Policies -Follow the steps to configure a Local Security Policy to allow Kerberos. +To configure a Local Security Policy to allow Kerberos: **Step 1 –** Open the Local Security Policy window. @@ -48,14 +48,14 @@ policy > click **Properties**. **Step 5 –** Click **Apply**, then click **OK**. -A Local Security Policy has been configured to allow encryption methods for Kerberos. Proceed to the +You have now configured a Local Security Policy to allow encryption methods for Kerberos. Proceed to the [Configure Active Directory Users and Computers Settings to allow Kerberos](#configure-active-directory-users-and-computers-settings-to-allow-kerberos) section of this topic to ensure Active Directory Users and Computer settings are configured to allow the encryption methods for Kerberos. ## Group Security Policy -Follow the steps to configure a Local Group Security Policy to allow Kerberos. +To configure a Local Group Security Policy to allow Kerberos: **Step 1 –** Open the Local Group Policy Editor window. @@ -73,7 +73,7 @@ policy, then click **Properties**. **Step 5 –** Click **Apply**, then click **OK**. -A Local Group Security Policy has been configured to allow encryption methods for Kerberos. Proceed +You have now configured a Local Group Security Policy to allow encryption methods for Kerberos. Proceed to the [Configure Active Directory Users and Computers Settings to allow Kerberos](#configure-active-directory-users-and-computers-settings-to-allow-kerberos) section of this topic to ensure Active Directory Users and Computer settings are configured to allow @@ -81,9 +81,9 @@ the encryption methods for Kerberos. ## Configure Active Directory Users and Computers Settings to allow Kerberos -Follow the steps to ensure the settings for Active Directory Users and Computers are configured to -allow the encryption methods to allow Kerberos. Configurations selected in this section should -reflect the configuration options selected in the two sections above. See the +To ensure that the settings for Active Directory Users and Computers allow the encryption methods +for Kerberos, match the configuration options you select in this section to those you selected in +the two preceding sections. See the [Local Security Policies](#local-security-policies) and [Group Security Policy](#group-security-policy) topics for additional information. @@ -103,6 +103,6 @@ reflect the configuration options selected in the two sections above. See the **Step 6 –** Click **Apply**, then click **OK**. -Active Directory Users and Computer settings have been configured to allow the encryption methods -for Kerberos. These settings should match the configuration options for Local Security Policies and -Local Group Policies. +You have now configured Active Directory Users and Computer settings to allow the encryption +methods for Kerberos. These settings should match the configuration options for Local Security +Policies and Local Group Policies. diff --git a/docs/accessanalyzer/11.6/install/application/reports/okta.md b/docs/accessanalyzer/11.6/install/application/reports/okta.md index 8f4bffc8cb..027097a99d 100644 --- a/docs/accessanalyzer/11.6/install/application/reports/okta.md +++ b/docs/accessanalyzer/11.6/install/application/reports/okta.md @@ -8,7 +8,7 @@ sidebar_position: 90 Create an Enterprise Auditor Application in Okta Using the WS-Fed Template -Follow the steps to create an Enterprise Auditor Application in Okta Using the WS-Fed Template: +To create an Enterprise Auditor Application in Okta using the WS-Fed template: **Step 1 –** Log in to Okta. @@ -28,12 +28,12 @@ Retrieve the Values to Paste into the Enterprise Auditor WebServer.exe.config Fi **Step 1 –** In the Enterprise Auditor application, click the **Sign On** tab. -**Step 2 –** Right click on the **Identity Provider metadata** link and select **Copy Link Address** +**Step 2 –** Right click the **Identity Provider metadata** link and select **Copy Link Address** to get the value for the WSFederationMetadata URL. **** -**Step 3 –** Click on the General tab to copy the value for the **Realm**. This value will be unique +**Step 3 –** Click the General tab to copy the value for the **Realm**. This value will be unique per tenant. `https://www.okta.com/` @@ -44,7 +44,7 @@ per tenant. Edit the WebServer.exe.config File -Follow the steps to edit the **WebServer.exe.config** file: +To edit the **WebServer.exe.config** file: **Step 1 –** Open the **WebServer.exe.config** file with a text editor, such as Notepad++. It is located in the Web folder within the Enterprise Auditor installation. @@ -110,7 +110,7 @@ to populate the following fields. ![oktaprofileeditor](/images/accessanalyzer/11.6/install/application/reports/oktaprofileeditor.webp) -**Step 2 –** Navigate to the Directory menu and select **Profile Editor** from the drop-down menu. +**Step 2 –** Navigate to the Directory menu and select **Profile Editor** from the dropdown menu. Click the **Edit Profile** button for the Enterprise Auditor application. ![Okta Add Attribute button](/images/accessanalyzer/11.6/install/application/reports/oktaaddattribute.webp) @@ -137,12 +137,12 @@ attribute, click **Save and Add Another**. ![To Okta option under the Directory Provisioning Tab](/images/accessanalyzer/11.6/install/application/reports/oktadirectoryprovisioningtookta.webp) -**Step 5 –** Navigate to the **Directory** menu and click on the **Provisioning** tab. Click **To +**Step 5 –** Navigate to the **Directory** menu and click the **Provisioning** tab. Click **To Okta**. ![Okta Show Unmapped Attributes](/images/accessanalyzer/11.6/install/application/reports/oktashowunmappedattributes.webp) -**Step 6 –** Locate and map the attributes that were added for the profile by clicking the +**Step 6 –** Locate and map the attributes that you added for the profile by clicking the **Pencil** icon to edit attributes. To locate the attributes, scroll down and select **Show Unmapped Attributes**. @@ -164,7 +164,7 @@ additional information. ## Setting Up Multi-Factor Authentication -Follow the steps to configure multi-factor-authentication for Enterprise Auditor: +To configure multi-factor authentication for Enterprise Auditor: ![Okta MFA App Sign on Rule window](/images/accessanalyzer/11.6/install/application/reports/oktamfaappsignonrule.webp) @@ -180,4 +180,4 @@ opens. Configure the following options: **Step 2 –** Scroll down to the Access section. Check the **Prompt for factor** box and select **Every Sign On**. Click **Save**. -Multi-Factor Authentication is now configured for Enterprise Auditor. +You have now configured Multi-Factor Authentication for Enterprise Auditor. diff --git a/docs/accessanalyzer/11.6/install/application/reports/overview.md b/docs/accessanalyzer/11.6/install/application/reports/overview.md index d416e16a26..409ef77a72 100644 --- a/docs/accessanalyzer/11.6/install/application/reports/overview.md +++ b/docs/accessanalyzer/11.6/install/application/reports/overview.md @@ -6,8 +6,8 @@ sidebar_position: 40 # Reports via the Web Console -The Web Console is where any reports which have been published can be viewed outside of the -Enterprise Auditor Console. +The Web Console is where you can view any reports that Enterprise Auditor has published, outside +of the Enterprise Auditor Console. - Web Console – This console uses an embedded website for published reports. It provides a consolidated logon feature for viewing published reports, and accessing the Netwrix Access @@ -41,25 +41,25 @@ topic for additional information on configuring security polices to allow Kerber ## Log into the Web Console -In order for a user to log into the Web Console, the user’s account must have the User Principal +To log into the Web Console, a user's account must have the User Principal Name (UPN) attribute populated within Active Directory. Then the user can login using domain -credentials. If multiple domains are being managed by the Netwrix Access Information Center, then +credentials. If the Netwrix Access Information Center manages multiple domains, the username needs to be in the `domain\username` format. -Access to reports in the Web Console can be managed through the Role Based Access feature of +You can manage access to reports in the Web Console through the Role Based Access feature of Enterprise Auditor (**Settings** > **Access**). The Web Administrator role and the Report Viewer role grant access to the published reports. See the [Role Based Access](/docs/accessanalyzer/11.6/admin/settings/access/rolebased/overview.md) topic for addition information. :::note -Access to the AIC and other Netwrix products is controlled from within those products. +You control access to the AIC and other Netwrix products from within those products. ::: -The address to the Web Console can be configured within the Enterprise Auditor Console +You can configure the address to the Web Console within the Enterprise Auditor Console (**Settings** > **Reporting**). The default address is `http://[hostname.domain.com]:8082`. From the -Enterprise Auditor Console server, it can be accessed at `http://localhost/` with any standard +Enterprise Auditor Console server, you can access it at `http://localhost/` with any standard browser. To access the Web Console from another machine in or connected to the environment, replace localhost with the name of the Enterprise Auditor Console. See the [Update Website URLs](/docs/accessanalyzer/11.6/install/application/reports/secure.md#update-website-urls) @@ -73,7 +73,7 @@ topic for additional information. ::: -Follow the steps to login to the Web Console. +To log in to the Web Console: **Step 1 –** To open the Web Console page, use one of the following methods: @@ -84,7 +84,7 @@ Follow the steps to login to the Web Console. - `https://[machinename]:8082` :::note -The URL that is used may need to be added to the browser’s list of trusted sites. +You may need to add the URL you use to the browser’s list of trusted sites. ::: diff --git a/docs/accessanalyzer/11.6/install/application/reports/secure.md b/docs/accessanalyzer/11.6/install/application/reports/secure.md index 8b90dedecb..c63f385973 100644 --- a/docs/accessanalyzer/11.6/install/application/reports/secure.md +++ b/docs/accessanalyzer/11.6/install/application/reports/secure.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Securing the Web Console -Published reports can be accessed in the Web Console. There are several options for enhancing +You can access published reports in the Web Console. There are several options for enhancing security. Additional configuration options for enhanced security include: @@ -29,13 +29,13 @@ Additional configuration options for enhanced security include: ::: -These parameters can be configured within the **WebServer.exe.config** file in the Web folder of the -Enterprise Auditor installation directory `…\STEALTHbits\StealthAUDIT\Web`. +You can configure these parameters within the **WebServer.exe.config** file in the Web folder of +the Enterprise Auditor installation directory `…\STEALTHbits\StealthAUDIT\Web`. ## Enable SSL for the Web Console -To enable Secure Sockets Layer (SSL) for secure, remote connections to the Web Console it is -necessary to bind a certificate to the port. See the +To enable Secure Sockets Layer (SSL) for secure, remote connections to the Web Console, bind a +certificate to the port. See the [Use a Self-Signed Certificate for SSL](#use-a-self-signed-certificate-for-ssl) topic for more information. Follow the steps on the server where Enterprise Auditor is installed to enable SSL for the Web Console. @@ -43,7 +43,7 @@ the Web Console. :::note The following steps require a certificate to be available. Organizations typically have one or more system administrators responsible for Public Key Infrastructure (PKI) and certificates. -To continue with this configuration it will first be necessary to confer with the PKI administrator +Before continuing with this configuration, confer with the PKI administrator to determine which certificate method will conform to the organization’s security policies. Optionally, see [Use a Self-Signed Certificate for SSL](#use-a-self-signed-certificate-for-ssl) for an Administrator PowerShell command which will both create and import a self-signed certificate. @@ -54,16 +54,16 @@ an Administrator PowerShell command which will both create and import a self-sig snap-in. :::note -If using a self-signed certificate, it will also need to be imported. +If you use a self-signed certificate, you'll also need to import it. ::: -**Step 2 –** Create an SSL binding. It is necessary to use the certificate’s **Hash** value for the +**Step 2 –** Create an SSL binding. Use the certificate's **Hash** value for the `$certHash` value: :::note -The following Administrator PowerShell dir command can be run on the certificate's “drive” -to find the **Hash** value of a certificate which was already created and the output will include +You can run the following Administrator PowerShell dir command on the certificate's “drive” +to find the **Hash** value of a certificate that you already created; the output includes the Thumbprint (**Hash**) value and the certificate name: ::: @@ -94,8 +94,8 @@ located within the Web folder of the Enterprise Auditor installation directory. ``` -- After changing the `BindingUrl` value in the **WebServer.exe.config** file, the Website URL must - be updated to match the new value in the following places: +- After changing the `BindingUrl` value in the **WebServer.exe.config** file, you must update the + Website URL to match the new value in the following places: - Enterprise Auditor's **Settings** > **Reporting** node - Enterprise Auditor's Published Reports Desktop icon properties - See the [Update Website URLs](#update-website-urls) topic for additional information. @@ -106,30 +106,30 @@ located within the Web folder of the Enterprise Auditor installation directory. Server service. :::note -If also using the AIC, then SSL needs to be enabled for the AIC using this certificate. +If you also use the AIC, you need to enable SSL for the AIC using this certificate. See the Securing the AIC section of the [Netwrix Access Information Center Documentation](https://helpcenter.netwrix.com/category/accessinformationcenter) for additional information. ::: -The Web Console has been enabled for SSL communication. Access it using the server’s fully qualified -domain name and the HTTPS port (`https://[hostname.domain.com]:8082`). If a self-signed certificate -was used, then the client-side access to the Web Console will generate a Certificate error. See the +You have now enabled the Web Console for SSL communication. Access it using the server’s fully +qualified domain name and the HTTPS port (`https://[hostname.domain.com]:8082`). If you used a +self-signed certificate, client-side access to the Web Console will generate a Certificate error. See the [Add the Certificate for Client-Side Access](#add-the-certificate-for-client-side-access) topic for additional information. ### Update Website URLs -If the Binding URL value is updated in Enterprise Auditor's **WebServer.exe.config** file, the -Website URL must be updated to match the new value in the following places: +If you update the Binding URL value in Enterprise Auditor's **WebServer.exe.config** file, you must +update the Website URL to match the new value in the following places: - Enterprise Auditor's Reporting node (**Settings** > **Reporting**) - Enterprise Auditor's Published Reports Desktop icon properties **Update the Website URL in the Reporting Node** -Follow the steps to update the Website URL in the **Settings** > **Reporting** node. +To update the Website URL in the **Settings** > **Reporting** node: **Step 1 –** Expand **Settings** and select the **Reporting** node. @@ -139,14 +139,14 @@ Follow the steps to update the Website URL in the **Settings** > **Reporting** n **Step 3 –** Click **Save**. -The Website URL is now updated. +You have now updated the Website URL. Update the URL in the Published Reports Desktop Icon Properties -Follow the steps to update the URL in the Published Reports desktop icon's Published Report's -Properties window. +To update the URL in the Published Reports desktop icon's Published Report's +Properties window: -**Step 1 –** Right click on the **Published Reports** desktop shortcut and click **Properties**. +**Step 1 –** Right click the **Published Reports** desktop shortcut and click **Properties**. ![Published Reports desktop icon properties](/images/accessanalyzer/11.6/install/application/reports/publishedreportsproperties.webp) @@ -155,7 +155,7 @@ Properties window. **Step 3 –** Click **Apply** and then **OK** to exit. -The URL is now updated. +You have now updated the URL. ### Remove Certificate from the Port @@ -196,8 +196,8 @@ The Thumbprint value is the certificate **Hash** value to be used when binding t can be the same as in HTTP (8082). Use this **Hash** value for Step 2 of the [Enable SSL for the Web Console](#enable-ssl-for-the-web-console) instructions. -Creation and import of the self-signed certificate can be validated in Microsoft Management Console. -Follow these steps to confirm the certificate is in Microsoft Management Console. +You can validate creation and import of the self-signed certificate in Microsoft Management Console. +To confirm the certificate is in Microsoft Management Console: **Step 1 –** Open Microsoft Management Console (`mmc.exe`). @@ -219,14 +219,14 @@ window. Click **OK** to close the window. **Step 5 –** Navigate to **Certificates** > **Personal** > **Certificates**. The certificate should show in the pane on the right. -The self-signed certificate was created and imported. Repeat these steps for each client-side host. +You created and imported the self-signed certificate. Repeat these steps for each client-side host. ### Add the Certificate for Client-Side Access When you open the Web Console with SSL enabled, the web browser shows a Your connection isn't -private warning message. This can be removed by importing the certificate onto the client server. +private warning message. You can remove this by importing the certificate onto the client server. -Follow the steps to remove the certificate error. +To remove the certificate error: **Step 1 –** Open the Web Console in your browser. @@ -242,7 +242,7 @@ Viewer from the warning details. - In Microsoft Edge, click the **Your Connection to this site isn't secure** section, and then click the certificate icon. -- In Google Chrome, click **Certificate is not valid**. +- In Google Chrome, click **Certificate isn't valid**. ![Web browser Certificate Viewer window](/images/accessanalyzer/11.6/install/application/reports/certificateviewer.webp) diff --git a/docs/accessanalyzer/11.6/install/application/reports/sso.md b/docs/accessanalyzer/11.6/install/application/reports/sso.md index 60a9d1acbb..2ea71837a0 100644 --- a/docs/accessanalyzer/11.6/install/application/reports/sso.md +++ b/docs/accessanalyzer/11.6/install/application/reports/sso.md @@ -6,10 +6,10 @@ sidebar_position: 40 # Enable Single Sign-On -Single sign-on using Windows authentication allows users to be automatically log into the Web -Console according to the user’s current login session. When opening a session from a different -domain, the user will be prompted for credentials from a pop-up windows. After authenticating, the -user will be automatically logged in the Web Console. +With single sign-on using Windows authentication, the Web Console automatically logs users in +according to the user's current login session. When a user opens a session from a different +domain, a pop-up window prompts the user for credentials. After the user authenticates, the Web +Console automatically logs the user in. :::note The Web Console also supports using Microsoft Entra ID single sign-on. See the @@ -18,7 +18,7 @@ topic for additional information. ::: -Follow the steps to enable single sign-on for the Web Console. +To enable single sign-on for the Web Console: **Step 1 –** Open the **WebServer.exe.config** file with a text editor, for example Notepad. It is located within the Web folder of the Enterprise Auditor installation directory. @@ -36,15 +36,15 @@ located within the Web folder of the Enterprise Auditor installation directory. **Step 4 –** Navigate to Services (`services.msc`). Restart the Netwrix Enterprise Auditor Web Server service. -The Web Console has been enabled for single sign-on. +You have now enabled the Web Console for single sign-on. ## Local Intranet Settings -Next, configure local intranet settings to enable SSO. This enables users to have authentication -pass through Windows Authentication and bypass SSO configuration Prompts for credentials via Browser -pop-up. +Next, configure local intranet settings to enable SSO. This lets authentication +pass through Windows Authentication and bypass SSO configuration prompts for credentials through a +browser pop-up. -Follow the steps to configure local intranet settings. +To configure local intranet settings: **Step 1 –** Open Windows Internet Properties (**Control Panel** > **Network and Internet** > **Internet Options**). @@ -71,7 +71,7 @@ Authentication will now pass through Windows Authentication and bypass SSO confi credentials via Browser pop-up :::note -A list of allowed authentication servers can also be configured using the +You can also configure a list of allowed authentication servers using the AuthServerAllowList policy. ::: diff --git a/docs/accessanalyzer/11.6/install/application/reports/timeout.md b/docs/accessanalyzer/11.6/install/application/reports/timeout.md index 81686320ae..0e0eb05a31 100644 --- a/docs/accessanalyzer/11.6/install/application/reports/timeout.md +++ b/docs/accessanalyzer/11.6/install/application/reports/timeout.md @@ -6,19 +6,19 @@ sidebar_position: 60 # Timeout Parameter for the Web Console -The Web Console is configured with a default timeout parameter of 15 minutes. This can be configured -within the **WebServer.exe.config** file in the Web folder of the Enterprise Auditor installation -directory: +By default, Enterprise Auditor configures the Web Console with a timeout parameter of 15 minutes. +You can configure this within the **WebServer.exe.config** file in the Web folder of the Enterprise +Auditor installation directory: **…\STEALTHbits\StealthAUDIT\Web** -Follow the steps to modify the timeout parameter for the Web Console. +To modify the timeout parameter for the Web Console: **Step 1 –** Open the **WebServer.exe.config** file with a text editor, for example Notepad. ![WebServer.exe.config file in Notepad](/images/accessanalyzer/11.6/install/application/reports/webserverexeconfigtimeout.webp) -**Step 2 –** Change the value for the `SessionTimeout` parameter to the desired number of minutes: +**Step 2 –** Change the value for the `SessionTimeout` parameter to the number of minutes you want: ``` diff --git a/docs/accessanalyzer/11.6/install/application/updatelicense.md b/docs/accessanalyzer/11.6/install/application/updatelicense.md index 930904074c..5fb4bc7db2 100644 --- a/docs/accessanalyzer/11.6/install/application/updatelicense.md +++ b/docs/accessanalyzer/11.6/install/application/updatelicense.md @@ -6,22 +6,23 @@ sidebar_position: 60 # Update License Key -It is necessary to install a new license key for an existing Enterprise Auditor installation due to +Install a new license key for an existing Enterprise Auditor installation due to the following: - To renew a Enterprise Auditor license that is due to expire - To grant access to additional Solutions -In these situations it is possible to update the license file without going through the full +In these situations, you can update the license file without going through the full installation process. ## Install a New License File -Follow the steps to update the Enterprise Auditor license key without installing a new version of -the Enterprise Auditor Console. +To update the Enterprise Auditor license key without installing a new version of +the Enterprise Auditor Console: -**Step 1 –** Ensure the new `StealthAUDIT.lic` license file is stored locally on the Enterprise -Auditor Console server in order to be referenced during the installation process. +**Step 1 –** Ensure that you store the new `StealthAUDIT.lic` license file locally on the +Enterprise Auditor Console server so that the installer can reference it during the installation +process. ![Windows Control Panel Uninstall or change a program window](/images/accessanalyzer/11.6/install/application/controlpaneluninstall.webp) @@ -42,14 +43,15 @@ Features**), select the Enterprise Auditor application and click **Change**. | Default License File Page | | Mapped License File | **Step 5 –** On the License File page, click **Browse** and navigate to the **StealthAUDIT.lic** -file. It must be stored on the Enterprise Auditor Console server before the installation begins. -When the path to the file is visible in the text box, click **Next**. The license will be imported. +file. You must store it on the Enterprise Auditor Console server before the installation begins. +When the path to the file is visible in the text box, click **Next**. Enterprise Auditor imports +the license. ![License Features page](/images/accessanalyzer/11.6/install/application/licensefeatures.webp) **Step 6 –** The License Features page displays a list of all features covered by the imported license. It also displays the name of the organization which owns the license, the expiration date, -and the host limit. These are the features that will be installed. Click **Next**. +and the host limit. These are the features that Enterprise Auditor will install. Click **Next**. ![Setup Wizard Ready to change page](/images/accessanalyzer/11.6/install/application/ready_1.webp) @@ -59,5 +61,5 @@ and the host limit. These are the features that will be installed. Click **Next* **Step 8 –** When the installation has completed, click **Finish** to exit the wizard. -The new license file has been imported. If the license granted access to any additional solutions, -they will now be accessible from within the Enterprise Auditor Console. +You have now imported the new license file. If the license granted access to any additional +solutions, you can now access them from within the Enterprise Auditor Console. diff --git a/docs/accessanalyzer/11.6/install/application/upgrade/overview.md b/docs/accessanalyzer/11.6/install/application/upgrade/overview.md index ae67dee744..63bfc607b0 100644 --- a/docs/accessanalyzer/11.6/install/application/upgrade/overview.md +++ b/docs/accessanalyzer/11.6/install/application/upgrade/overview.md @@ -11,15 +11,14 @@ that are no longer supported, contact [Netwrix Support](https://www.netwrix.com/ assistance. :::note -If any customizations have been done by a Netwrix Engineer, please ensure custom work is -not lost during the upgrade process. While using the Upgrade Wizard, customizations are archived -prior to solution upgrades. These archives are available after the solution upgrades have been -completed. Contact [Netwrix Support](https://www.netwrix.com/support.html) for additional +If a Netwrix Engineer has made any customizations, ensure custom work isn't lost during the +upgrade process. The Upgrade Wizard archives customizations before solution upgrades. These +archives are available after the solution upgrades finish. Contact [Netwrix Support](https://www.netwrix.com/support.html) for additional information. ::: -The purpose of this document is to provide the basic steps needed for upgrading Enterprise Auditor +This document provides the basic steps needed for upgrading Enterprise Auditor and the stock solutions. Contact [Netwrix Support](https://www.netwrix.com/support.html) for additional information. @@ -28,11 +27,11 @@ additional information. **Multiple Enterprise Auditor Consoles Connecting to the Same Database** -In environments where multiple Enterprise Auditor Consoles are using the same SQL Server database, -every console using the database must also be updated. The act of connecting a Enterprise Auditor -Console with a newer version to a database updates the database’s schema pursuant to the new -definition. If a Enterprise Auditor Console with an older version connects to the same database -after the schema has been updated, corruption to Enterprise Auditor’s system tables can result. +In environments where multiple Enterprise Auditor Consoles use the same SQL Server database, you +must also update every console using the database. Connecting an Enterprise Auditor Console with a +newer version to a database updates the database’s schema according to the new definition. If an +Enterprise Auditor Console with an older version connects to the same database after you update the +schema, corruption to Enterprise Auditor’s system tables can result. **SQL Server Supported Version Change for the Enterprise Auditor Database** diff --git a/docs/accessanalyzer/11.6/install/application/upgrade/solutionconsiderations.md b/docs/accessanalyzer/11.6/install/application/upgrade/solutionconsiderations.md index 2d697a8e09..0afed2dd70 100644 --- a/docs/accessanalyzer/11.6/install/application/upgrade/solutionconsiderations.md +++ b/docs/accessanalyzer/11.6/install/application/upgrade/solutionconsiderations.md @@ -6,14 +6,14 @@ sidebar_position: 10 # Solution Upgrade Considerations -The following items must be taken into consideration for upgrades: +Consider the following items for upgrades: **Access Information Center** -- Should be upgraded at the same time as Enterprise Auditor. +- Upgrade it at the same time as Enterprise Auditor. :::note - The Enterprise Auditor upgrade should be completed first. + Complete the Enterprise Auditor upgrade first. ::: @@ -23,15 +23,18 @@ instructions. **Sensitive Data Discovery Add-on** -- Needs to be updated on all servers where it was installed. See the +- Update it on all servers where you installed it. See the [Upgrade Sensitive Data Discovery Add-on](/docs/accessanalyzer/11.6/install/sensitivedatadiscovery/upgrade.md) topic for instructions. -- **CAUTION:** The new global Settings will overwrite any previously configured criteria. Make a - note of any configured Sensitive Data Criteria before upgrading Enterprise Auditor. Sensitive Data - Criteria must be reconfigured after an upgrade. -With the new global experience, sensitive data criteria selection is configured globally and used by -default in all solution sets. See the + :::warning + The new global Settings will overwrite any previously configured criteria. Make a + note of any configured Sensitive Data Criteria before upgrading Enterprise Auditor. You must + reconfigure Sensitive Data Criteria after an upgrade. + ::: + +With the new global experience, you configure sensitive data criteria selection globally, and +Enterprise Auditor uses it by default in all solution sets. See the [Configure Global Sensitive Data Settings](#configure-global-sensitive-data-settings) for additional information. @@ -44,7 +47,7 @@ information. **File System Solution Considerations** -- For Proxy Mode as a Service – File System Proxy Service needs to be updated on the proxy servers. +- For Proxy Mode as a Service – Update the File System Proxy Service on the proxy servers. See the [Upgrade Proxy Service Procedure](/docs/accessanalyzer/11.6/install/filesystemproxy/upgrade.md) topic for instructions. @@ -55,8 +58,8 @@ information. **SharePoint Solution Considerations** -- For SharePoint Agent – Enterprise Auditor SharePoint Agent needs to be updated on the SharePoint - server where it was installed. See the +- For SharePoint Agent – Update the Enterprise Auditor SharePoint Agent on the SharePoint + server where you installed it. See the [Upgrade SharePoint Agent](/docs/accessanalyzer/11.6/install/sharepointagent/upgrade.md) section for instructions. - For Activity – Ensure the Stealthbits Activity Monitor is a compatible version. See the Upgrade @@ -80,7 +83,7 @@ After upgrading to Enterprise Auditor 11.6, run the latest version of the **File **0.Collection** > **0-Create Schema** job to migrate the File System Solution to the latest database schema. -This database schema migration should be performed before running other jobs in the File System +Perform this database schema migration before running other jobs in the File System Solution after upgrading to Enterprise Auditor 11.6. See the @@ -91,23 +94,23 @@ topic for additional information. :::warning The new global Settings will overwrite any previously configured criteria. Make a note -of any configured Sensitive Data Criteria before commencing the upgrade Enterprise Auditor. -Sensitive Data Criteria must be reconfigured after an upgrade. +of any configured Sensitive Data Criteria before upgrading Enterprise Auditor. +You must reconfigure Sensitive Data Criteria after an upgrade. ::: -If Sensitive Data Criteria are configured differently for each solution, re-configure the criteria +If you configured Sensitive Data Criteria differently for each solution, re-configure the criteria selection at the solution level. See the [Sensitive Data Discovery Add-On](/docs/accessanalyzer/11.6/sensitivedatadiscovery/overview.md) topic and the topic for the applicable solution for additional information. -If the same Sensitive Data Criteria are used for all solutions, configure the criteria selection at -the global **Settings** > **Sensitive Data** node, which will then be used by default in all +If you use the same Sensitive Data Criteria for all solutions, configure the criteria selection at +the global **Settings** > **Sensitive Data** node; Enterprise Auditor then uses it by default in all solutions. See the [Sensitive Data Discovery Add-On](/docs/accessanalyzer/11.6/sensitivedatadiscovery/overview.md) topic for additional information. -Follow the steps to configure Sensitive Data Criteria at the global level. +To configure Sensitive Data Criteria at the global level: **Step 1 –** The Sensitive Data node provides configuration options to manage sensitive data criteria and false positive exclusion filters. These settings require the Sensitive Data Discovery @@ -117,16 +120,17 @@ topic for additional information. ![Global Settings Sensitive Data node](/images/accessanalyzer/11.6/install/application/upgrade/sensitivedata.webp) -**Step 2 –** If the same Sensitive Data Criteria are used for all solutions, configure the criteria -selection at the global Settings level, which will then be used by default in all solution sets. +**Step 2 –** If you use the same Sensitive Data Criteria for all solutions, configure the criteria +selection at the global Settings level; Enterprise Auditor then uses it by default in all solution +sets. Navigate to the **Settings** > **Sensitive Data** node and click **Add** to open the Select Criteria window. ![Sensitive Data Select Criteria window](/images/accessanalyzer/11.6/install/application/upgrade/selectcriteria.webp) -**Step 3 –** Select the desired criteria. Use the **Search Criteria** text field to filter the list +**Step 3 –** Select the criteria you want. Use the **Search Criteria** text field to filter the list using keywords or expand each category to view and select individual Sensitive Data search criteria, then click **OK**. -By default, Sensitive Data Criteria configured at the global Settings level is inherited down to the -applicable solutions. +By default, Enterprise Auditor applies Sensitive Data Criteria configured at the global Settings +level to the applicable solutions. diff --git a/docs/accessanalyzer/11.6/install/application/upgrade/wizard.md b/docs/accessanalyzer/11.6/install/application/upgrade/wizard.md index 21571813a9..4cf94b55d9 100644 --- a/docs/accessanalyzer/11.6/install/application/upgrade/wizard.md +++ b/docs/accessanalyzer/11.6/install/application/upgrade/wizard.md @@ -7,19 +7,18 @@ sidebar_position: 20 # Enterprise Auditor Core Upgrade Instructions :::warning -If Role Based Access has been enabled, a user with the Administrator role must perform -the upgrade. Other user roles do not have the necessary permissions to perform upgrades. +If you enabled Role Based Access, a user with the Administrator role must perform +the upgrade. Other user roles don't have the necessary permissions to perform upgrades. ::: -Follow the steps to upgrade to Enterprise Auditor 11.6 on the same server where an older version of -Enterprise Auditor is installed. +To upgrade to Enterprise Auditor 11.6 on the same server where an older version of +Enterprise Auditor is installed: :::note -If any customizations have been done by a Netwrix Engineer, please ensure the custom work -is not lost during the upgrade process. While using the Upgrade Wizard, customizations are archived -prior to solution upgrades. These archives are available after the solution upgrades have been -completed. Contact [Netwrix Support](https://www.netwrix.com/support.html) for additional +If a Netwrix Engineer has made any customizations, ensure the custom work isn't lost during the +upgrade process. The Upgrade Wizard archives customizations before solution upgrades. These +archives are available after the solution upgrades finish. Contact [Netwrix Support](https://www.netwrix.com/support.html) for additional information. ::: @@ -27,7 +26,7 @@ information. :::warning The new global Settings will overwrite any previously configured Sensitive Data criteria. Make a note of any configured Sensitive Data Criteria before upgrading Enterprise Auditor. -Sensitive Data Criteria must be reconfigured after an upgrade. See the +You must reconfigure Sensitive Data Criteria after an upgrade. See the [Configure Global Sensitive Data Settings](/docs/accessanalyzer/11.6/install/application/upgrade/solutionconsiderations.md#configure-global-sensitive-data-settings) topic for additional information. ::: @@ -39,9 +38,9 @@ topic for additional information. Features**), uninstall the previous version of Enterprise Auditor. Jobs, application configuration files, and reports remain in the installation directory after the uninstall process. -- The `WebServer.exe.config` file is automatically retained in a Backup folder created under the Web - folder of the installation directory. Any custom application settings contained in this file are - kept as part of this upgrade process. +- Enterprise Auditor automatically retains the `WebServer.exe.config` file in a Backup folder created + under the Web folder of the installation directory. It keeps any custom application settings + contained in this file as part of this upgrade process. ![Setup Wizard Welcome page](/images/accessanalyzer/11.6/install/application/welcome.webp) @@ -49,31 +48,31 @@ files, and reports remain in the installation directory after the uninstall proc [Enterprise Auditor Core Installation](/docs/accessanalyzer/11.6/install/application/wizard.md) topic for detailed instructions. -- Before installation, ensure the new `StealthAUDIT.lic` license file is stored locally on the - Enterprise Auditor Console in order to be referenced during the installation process -- Enterprise Auditor is installed to the following directory by default: +- Before installation, ensure that you store the new `StealthAUDIT.lic` license file locally on the + Enterprise Auditor Console so that the installer can reference it during the installation process +- By default, the installer places Enterprise Auditor in the following directory: `…\STEALTHbits\StealthAUDIT` - If another installation path is designated, please be sure to leave `STEALTHbits\StealthAUDIT` + If you designate another installation path, be sure to leave `STEALTHbits\StealthAUDIT` as the path suffix in the installation wizard. -- During the installation, any customizations to the settings in the `WebServer.exe.config` file are - automatically restored from the backup file retained when installing the previous version. The - `../Web/Backup` folder is deleted after the settings have been restored. +- During the installation, Enterprise Auditor automatically restores any customizations to the + settings in the `WebServer.exe.config` file from the backup file retained when installing the + previous version. It deletes the `../Web/Backup` folder after restoring the settings. -After the installation is completed, the upgrade wizard launches from the Enterprise Auditor desktop +After the installation finishes, the upgrade wizard launches from the Enterprise Auditor desktop icon. ## Upgrade Wizard -Once the Enterprise Auditor installation process is complete, it is necessary to go through the +After the Enterprise Auditor installation process finishes, go through the Upgrade Wizard. There are three Upgrade options for a solution: - Full Upgrade – Performs a full synchronization of the directory and file structure of the solution to mirror the Instant Solution - Upgrade in place – Performs file content updates of jobs matching the Instant Solutions but does not change the Jobs tree structure -- Do not upgrade – No upgrade is performed, leaving the previous version of the solution +- Don't upgrade – Performs no upgrade, leaving the previous version of the solution The default settings configured within the Advanced Upgrade Options window align with the best practices of the Netwrix Professional Services and Support teams. @@ -85,25 +84,25 @@ Upgrade action is set to **Full Upgrade** or **Upgrade in place**: | -------- | ----------------------------------------------------------------------------------- | -------------------- | ------------------------ | | Normal | Job exists in Locked state and has matching ID in Instant Solutions | Upgrade | Upgrade | | New | Job exists in Instant Solutions but not in the Jobs tree for an existing solution | Install | Install | -| Removed | Job exists in Locked state in the Jobs tree but does not exist in Instant Solutions | Delete | Nothing | +| Removed | Job exists in Locked state in the Jobs tree but doesn't exist in Instant Solutions | Delete | Nothing | | Copied | Original job exists in original location, but multiple instances of the job exists | Delete | Upgrade | | Moved | Original job exists but in a different location than in the Instant Solutions | Move & Upgrade | Upgrade | | Renamed | Job found via ID match but was renamed | Rename & Upgrade | Upgrade | | Conflict | Changes have been made to the job | Overwrite | Overwrite | -Conflicts are identified when customizations have been made by either a user or a Netwrix engineer. -Conflicts need to be either resolved prior to the upgrade action or manually applied after the -upgrade is complete. Conflict resolution can be done on the Changes window by undoing a -customization. However, if the conflict is undone prior to a solution upgrade, then the -customization will not be archived. +The Upgrade Wizard identifies conflicts when a user or a Netwrix engineer has made customizations +to the job. You need to either resolve conflicts before the upgrade action or manually apply them +after the upgrade finishes. You can resolve a conflict on the Changes window by undoing a +customization. However, if you undo the conflict before a solution upgrade, the +customization won't be archived. :::warning -If Role Based Access has been enabled, a user with the Administrator role must perform -the upgrade. Other user roles do not have the necessary permissions to perform upgrades. +If you enabled Role Based Access, a user with the Administrator role must perform +the upgrade. Other user roles don't have the necessary permissions to perform upgrades. ::: -Follow the steps to use the Upgrade Wizard. +To use the Upgrade Wizard: **Step 1 –** Launch the Enterprise Auditor application. The installation wizard placed the Enterprise Auditor icon on the desktop. @@ -113,18 +112,18 @@ Enterprise Auditor icon on the desktop. **Step 2 –** The Enterprise Auditor Configuration Wizard opens. Click **Next** to continue. :::note -When Enterprise Auditor11.6 is installed on a server where a previous version of -Enterprise Auditor had been installed, the Version Selection page of the Configuration Wizard will -not appear. +When you install Enterprise Auditor 11.6 on a server where a previous version of +Enterprise Auditor was installed, the Version Selection page of the Configuration Wizard doesn't +appear. ::: ![Configuration Wizard Solution Set Files page with conflicts](/images/accessanalyzer/11.6/install/application/upgrade/solutionsetfiles.webp) -**Step 3 –** On the Solution Set Files page, only upgrade conflicts are displayed by default. +**Step 3 –** On the Solution Set Files page, the wizard displays only upgrade conflicts by default. :::info -Investigate the changes where conflicts have been identified before proceeding. +Investigate the changes where the wizard identified conflicts before proceeding. ::: @@ -139,29 +138,29 @@ Additional options include: ![View conflicts in the Changes window](/images/accessanalyzer/11.6/install/application/upgrade/changes.webp) -**Step 5 –** (Optional) Conflicts can be resolved on the Changes window, which is opened by the -**View conflicts** button. Remember, if the conflict is resolved prior to a solution upgrade, then -the customization will not be archived. To resolve a conflict, select it from the list and click +**Step 5 –** (Optional) You can resolve conflicts on the Changes window, which the **View conflicts** +button opens. If you resolve the conflict before a solution upgrade, +the customization won't be archived. To resolve a conflict, select it from the list and click **Undo**. -**Step 6 –** When the Upgrade options have been set as desired. Click **Next**. +**Step 6 –** After you set the Upgrade options as desired, click **Next**. ![Configuration wizard Options page](/images/accessanalyzer/11.6/install/application/upgrade/options.webp) -**Step 7 –** On the Options page, select whether to send usage statistics to Netwrix to help us -improve our product. After the Usage Statistics option is set as desired, click **Next** to +**Step 7 –** On the Options page, select whether to send usage statistics to Netwrix to help +improve the product. After you set the Usage Statistics option as desired, click **Next** to continue. - If selected, usage statistics are collected and sent to Netwrix - - Upon startup of the Enterprise Auditor console, the system checks if usage statistics have - been sent in the last 7 days. If they have not been, stored procedures run against the + - Upon startup of the Enterprise Auditor console, the system checks whether it sent usage + statistics in the last 7 days. If not, stored procedures run against the Enterprise Auditor database and gather data about job runs, access times, and environmental - details like resource counts, users counts, number of exceptions, and so on. This data is then - sent back to Netwrix to help us identify usage trends and common pain points, so that we can - use this information to improve the product. - - Only anonymous statistic-level data is included. No private company or personal data is - collected or sent to Netwrix. + details like resource counts, user counts, number of exceptions, and so on. Enterprise Auditor + then sends this data back to Netwrix to help identify usage trends and common problem areas, + which Netwrix uses to improve the product. + - Enterprise Auditor includes only anonymous statistic-level data. It doesn't collect or send + private company or personal data to Netwrix. - If cleared, no usage statistics are collected or sent to Netwrix diff --git a/docs/accessanalyzer/11.6/install/application/wizard.md b/docs/accessanalyzer/11.6/install/application/wizard.md index 50e5f015e5..091a942a61 100644 --- a/docs/accessanalyzer/11.6/install/application/wizard.md +++ b/docs/accessanalyzer/11.6/install/application/wizard.md @@ -7,8 +7,8 @@ sidebar_position: 20 # Enterprise Auditor Core Installation Save the organization’s Enterprise Auditor license key, received from your Netwrix Sales -Representative, to the server where Enterprise Auditor is to be installed. Then follow the steps to -install Enterprise Auditor. +Representative, to the server where you'll install Enterprise Auditor. Then, to +install Enterprise Auditor: :::note The process explained in this topic assumes that both the downloaded binary and the @@ -17,8 +17,8 @@ license (.lic) file are located on the server which will become the Enterprise A :::warning -If User Account Control (UAC) is enabled on the server, ensure the installation package -is run in Administrative/privilege mode. +If User Account Control (UAC) is enabled on the server, ensure that you run the installation +package in Administrative/privilege mode. ::: @@ -49,7 +49,7 @@ install Enterprise Auditor. The default destination folder is file. When the path to the file is visible in the textbox, click **Next**. :::note -The license file must be stored on the Enterprise Auditor Console server before the +You must store the license file on the Enterprise Auditor Console server before the installation begins. ::: @@ -58,7 +58,7 @@ installation begins. **Step 6 –** The License Features page displays a list of all features covered by the imported license. It also displays the name of the organization which owns the license, the expiration date, -and the host limit. These are the features that will be installed. Click **Next**. +and the host limit. These are the features that Enterprise Auditor will install. Click **Next**. ![Ready to install Netwrix Access Governance page](/images/accessanalyzer/11.6/install/application/ready.webp) @@ -69,6 +69,6 @@ installation. **Step 8 –** When the installation has completed, click **Finish** to exit the wizard. -The Enterprise Auditor Console has been installed, and two desktop icons have been created: -Enterprise Auditor and Published Reports. Launch the Enterprise Auditor application to complete the +You have now installed the Enterprise Auditor Console, and the installer has created two desktop +icons: Enterprise Auditor and Published Reports. Launch the Enterprise Auditor application to complete the initial configuration. diff --git a/docs/accessanalyzer/11.6/install/filesystemproxy/configuredatacollector.md b/docs/accessanalyzer/11.6/install/filesystemproxy/configuredatacollector.md index 2a0f9c1358..119b2fc503 100644 --- a/docs/accessanalyzer/11.6/install/filesystemproxy/configuredatacollector.md +++ b/docs/accessanalyzer/11.6/install/filesystemproxy/configuredatacollector.md @@ -12,7 +12,7 @@ Access Auditor Data Collector Wizard from the job’s query. On the Applet Settings wizard page, select the following option: -- Require applet to be running as service on target – Must be selected in the Applet Launch +- Require applet to be running as service on target – Select this option in the Applet Launch Mechanism section to prevent the deployment of the applet or the ad hoc installation of the service during the scan diff --git a/docs/accessanalyzer/11.6/install/filesystemproxy/overview.md b/docs/accessanalyzer/11.6/install/filesystemproxy/overview.md index a2a34dfd74..901fcdbf8d 100644 --- a/docs/accessanalyzer/11.6/install/filesystemproxy/overview.md +++ b/docs/accessanalyzer/11.6/install/filesystemproxy/overview.md @@ -6,20 +6,20 @@ sidebar_position: 20 # File System Proxy as a Service Overview -The File System Solution can be enabled to use proxy servers for scanning targeted file systems in +You can enable the File System Solution to use proxy servers for scanning targeted file systems in very large or widely dispersed environments. -When File System scans are run in proxy mode as a service, there are two methods available for +When you run File System scans in proxy mode as a service, two methods are available for deploying the service: -- Pre-Installed File System Proxy Service – File System Proxy Service installation package must be - installed on the Windows proxy servers prior to executing the scans. This is the recommended +- Pre-Installed File System Proxy Service – Install the File System Proxy Service installation + package on the Windows proxy servers before executing the scans. This is the recommended method. -- Ad Hoc File System Proxy Service Deployment – File System Proxy Service is installed on the - Windows proxy server when the job is executed +- Ad Hoc File System Proxy Service Deployment – Enterprise Auditor installs the File System Proxy + Service on the Windows proxy server when the job runs -The data collection processing is conducted by the proxy server where the service is running and -leverages a local mode-type scan to each of the target hosts. The final step in data collection is +The proxy server where the service is running conducts the data collection processing and uses a +local mode-type scan to each of the target hosts. The final step in data collection is to compress and transfer the data collected in the SQLite databases, or Tier 2 databases, back to the Enterprise Auditor Console server. @@ -34,7 +34,7 @@ topic for information on the required prerequisites. ## Supported Platforms -The File System Proxy Service for the Enterprise Auditor File System Solution can be installed on +You can install the File System Proxy Service for the Enterprise Auditor File System Solution on the following Windows operating systems: - Windows Server 2022 @@ -43,15 +43,15 @@ the following Windows operating systems: ## Proxy Scanning Architecture -Enterprise Auditor is configured by default to process data collection against ten target hosts -simultaneously. When File System scans are run in local mode ten hosts process simultaneously, and -processing against the eleventh host begins after the processing against the first host is -completed. Proxy scanning architecture supports large deployments or widely dispersed environments. +By default, Enterprise Auditor processes data collection against ten target hosts +simultaneously. When you run File System scans in local mode, ten hosts process simultaneously, and +processing against the eleventh host begins after processing against the first host completes. +Proxy scanning architecture supports large deployments or widely dispersed environments. -A proxy server is any server that can be leveraged to process data collection against target hosts. +A proxy server is any server that processes data collection against target hosts. :::warning -The File System Proxy Service cannot be installed on the same server as Enterprise +You can't install the File System Proxy Service on the same server as Enterprise Auditor. ::: @@ -63,9 +63,9 @@ Two options are available for implementing the proxy scanning architecture: ### Proxy Mode with Applet -When File System scans are run in proxy mode with applet, it means the File System applet is -deployed to the Windows proxy server when the job is executed to conduct data collection. The data -collection processing is initiated by the proxy server where the applet is deployed and leverages a +When you run File System scans in proxy mode with applet, Enterprise Auditor deploys the File +System applet to the Windows proxy server when the job runs to conduct data collection. The proxy +server where the applet is deployed initiates the data collection processing and uses a local mode-type scan to each of the target hosts. The final step in data collection is to compress and transfer the data collected in the SQLite databases, or Tier 2 databases, back to the Enterprise Auditor Console server. @@ -77,25 +77,25 @@ which runs the scan against a file server, and then returns data to the Enterpri ### Proxy Mode as a Service -When File System scans are run in proxy mode as a service, there are two methods available for +When you run File System scans in proxy mode as a service, two methods are available for deploying the service: -- Pre-Installed File System Proxy Service – File System Proxy Service installation package must be - installed on the Windows proxy servers prior to executing the scans. This is the recommended +- Pre-Installed File System Proxy Service – Install the File System Proxy Service installation + package on the Windows proxy servers before executing the scans. This is the recommended method. -- Ad Hoc File System Proxy Service Deployment – File System Proxy Service is installed on the - Windows proxy server when the job is executed +- Ad Hoc File System Proxy Service Deployment – Enterprise Auditor installs the File System Proxy + Service on the Windows proxy server when the job runs -The data collection processing is conducted by the proxy server where the service is running and -leverages a local mode-type scan to each of the target hosts. The final step in data collection is +The proxy server where the service is running conducts the data collection processing and uses a +local mode-type scan to each of the target hosts. The final step in data collection is to compress and transfer the data collected in the SQLite databases, or Tier 2 databases, back to the Enterprise Auditor Console server. -The proxy communication is configured during the installation of the service on the proxy server and -certificate exchange options are configured via the Applet Settings page of the File System Access -Auditing Data Collector Wizard. The credential provided for the secure communications in the -installation wizard is also added to the Enterprise Auditor Connection Profile assigned to the File -System Solution. +You configure the proxy communication during installation of the service on the proxy server, and +you configure certificate exchange options via the Applet Settings page of the File System Access +Auditing Data Collector Wizard. The installation wizard also adds the credential you provide for +secure communications to the Enterprise Auditor Connection Profile assigned to the File System +Solution. See the [File System Proxy Service Installation](/docs/accessanalyzer/11.6/install/filesystemproxy/wizard.md) @@ -107,25 +107,25 @@ The diagram illustrates the Enterprise Auditor server communicating securely wit on a proxy server, which runs the scan against a file server, collecting the data locally and securely. Then the proxy service returns data securely to the Enterprise Auditor server. -When a proxy mode scan is initiated from the Enterprise Auditor Console, it will distribute hosts to +When you initiate a proxy mode scan from the Enterprise Auditor Console, it distributes hosts to be scanned across all proxy hosts. Enterprise Auditor monitors the scans from the central console. -Once all proxy hosts have completed scanning, all results and SQLite databases are returned to the +Once all proxy hosts complete scanning, they return all results and SQLite databases to the Enterprise Auditor Console server. ![Diagram of difference between an implementation with and without proxy servers](/images/accessanalyzer/11.6/install/filesystemproxy/fsaaproxyarchitecture.webp) The diagram shows the difference between an implementation of Enterprise Auditor without proxy -servers (on the left) and with proxy servers (on the right). On the right side of the diagram, the -scans have been configured to use the local host and two additional proxy servers to perform the +servers (on the left) and with proxy servers (on the right). On the right side of the diagram, you configured the +scans to use the local host and two additional proxy servers to perform the FSAA Data Collector scans. This allows it to execute three times as many concurrent hosts than would be possible without proxy servers. This provides a clear benefit in scalability and scan times. The proxy functionality for the FSAA Data Collector provides security and reliability. :::tip -Remember, It is recommended that the File System Proxy Service is installed on the proxy server -before running File System scans in proxy mode as a service. Once installed, the FileSystemAccess -(FSAA) Data Collector must be configured to use the service. See the +Install the File System Proxy Service on the proxy server +before running File System scans in proxy mode as a service. After installation, you must configure +the FileSystemAccess (FSAA) Data Collector to use the service. See the [File System Data Collection Configuration for Proxy as a Service](/docs/accessanalyzer/11.6/install/filesystemproxy/configuredatacollector.md) topic for additional information. ::: @@ -133,18 +133,18 @@ topic for additional information. ## Sensitive Data Discovery Auditing Consideration -Sensitive Data Discovery Auditing scans also require the Sensitive Data Add-on – FSAA & SPAA -Agentless (or x86) version of the Sensitive Data Discovery Add-On be installed on the proxy server. +Sensitive Data Discovery Auditing scans also require you to install the Sensitive Data Add-on – +FSAA & SPAA Agentless (or x86) version of the Sensitive Data Discovery Add-On on the proxy server. This requirement is in addition to having the Sensitive Data Discovery Add-on installed on the Enterprise Auditor Console server. See the [Sensitive Data Discovery Add-On Installation](/docs/accessanalyzer/11.6/install/sensitivedatadiscovery/overview.md) topic for additional information. :::note -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the +If you run Sensitive Data Discovery (SDD) scans, you'll need to increase the minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. By -default, SDD scans are configured to run two concurrent threads. For example, if the job is -configured to scan 8 hosts at a time with two concurrent SDD threads, then an extra 32 GB of RAM are -required (8x2x2=32). +default, Enterprise Auditor configures SDD scans to run two concurrent threads. For example, if you +configure the job to scan 8 hosts at a time with two concurrent SDD threads, you need an extra 32 GB +of RAM (8x2x2=32). ::: diff --git a/docs/accessanalyzer/11.6/install/filesystemproxy/silentinstall.md b/docs/accessanalyzer/11.6/install/filesystemproxy/silentinstall.md index 55b9bd0a51..db8b45613e 100644 --- a/docs/accessanalyzer/11.6/install/filesystemproxy/silentinstall.md +++ b/docs/accessanalyzer/11.6/install/filesystemproxy/silentinstall.md @@ -6,12 +6,12 @@ sidebar_position: 30 # Silent Installer Option for Proxy -It is possible to use one of the following methods to complete a silent installation of the File +Use one of the following methods to complete a silent installation of the File System Proxy Service. :::warning For all Active Directory versions, aside from Windows 2012 R2, the silent installer -does not prompt an error message if a duplicate SPN value exists in the targeted domain for +doesn't prompt an error message if a duplicate SPN value exists in the targeted domain for [Option 1: Run as LocalSystem](#option-1-run-as-localsystem). Having duplicate SPN’s in the targeted Active Directory environment prohibits connection to the proxy service, resulting in a failed scan. ::: @@ -21,16 +21,16 @@ If a desired SPN already exists in a Windows 2012 R2 domain, the silent installe following message: > _There is a problem with this Windows Installer package. A script required for this install to -> complete could not be run. Contact your support personnel or package vendor_. +> complete couldn't be run. Contact your support personnel or package vendor_. To resolve the problem, remove the duplicate SPN value and rerun the installer to complete -installation. For any additional issues, verbose logging is included in the silent installer and +installation. For any additional issues, the silent installer includes verbose logging and creates an `install.txt` file on the desktop. ## Option 1: Run as LocalSystem -Follow the steps to install the File System Proxy Service on the targeted proxy servers with a -silent installer. +To install the File System Proxy Service on the targeted proxy servers with a +silent installer: **Step 1 –** Copy the `FileSystemProxy.msi` executable to the desktop of the server designated as the proxy server. @@ -43,7 +43,7 @@ msiexec /i FileSystemProxy.msi /qb /l*v install.log SVC_ACCOUNT_TYPE=SYSTEM - To add a non-default install directory, append `PRODUCTDIR="[path]"` to the command. - - `path` – The path to the desired installation directory and must include + - `path` – The path to the installation directory you want and must include `...\STEALTHbits\StealthAUDIT\FSAA\...` For example: @@ -52,12 +52,12 @@ msiexec /i FileSystemProxy.msi /qb /l*v install.log SVC_ACCOUNT_TYPE=SYSTEM msiexec /i FileSystemProxy.msi /qb /l*v install.log SVC_ACCOUNT_TYPE=SYSTEM PRODUCTDIR="E:\STEALTHbits\StealthAUDIT\FSAA" ``` -The SPN value is automatically added to the computer object in Active Directory with this option. +This option automatically adds the SPN value to the computer object in Active Directory. ## Option 2: Run as a Service Account -Follow the steps to install the File System Proxy Service on the targeted proxy servers with a -silent installer. +To install the File System Proxy Service on the targeted proxy servers with a +silent installer: **Step 1 –** Copy the `FileSystemProxy.exe` executable to the desktop of the server designated as the proxy server. @@ -71,11 +71,11 @@ msiexec /i FileSystemProxy.msi /qb /l*v install.log SVC_ACCOUNT_TYPE=DOMAIN SVC_ - `DOMAIN\USERNAME` – The service account credentials, which need to be a member the Local Administrators group and have the**Log on as a service** local policy  (**Local Policies** > **User Rights Assignment**) -- `secret` – The password for the credentials provided above (within quotes) +- `secret` – The password for the credentials provided earlier (within quotes) - To add a non-default install directory, append `PRODUCTDIR="[path]"` to the command. - - `path` – The path to the desired installation directory and must include + - `path` – The path to the installation directory you want and must include `...\STEALTHbits\StealthAUDIT\FSAA\...` For example: diff --git a/docs/accessanalyzer/11.6/install/filesystemproxy/troubleshooting.md b/docs/accessanalyzer/11.6/install/filesystemproxy/troubleshooting.md index d2bd218720..e6ecc43b90 100644 --- a/docs/accessanalyzer/11.6/install/filesystemproxy/troubleshooting.md +++ b/docs/accessanalyzer/11.6/install/filesystemproxy/troubleshooting.md @@ -10,20 +10,20 @@ The following are potential errors that may occur during installation and how to | Error Message | Resolution | | -------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Service ‘Enterprise Auditor FSAA Proxy Scanner’ (StealthAUDITFSAA) failed to start. Verify that you have sufficient privileges to start system services. | The domain account used during setup does not have sufficient privileges to start the service. Open Local Security Policies on the proxy server. In User Rights Assignment under Local policies, add the desired user to the Log on as a service policy. Once the user has this privilege, retry the installation. | +| Service ‘Enterprise Auditor FSAA Proxy Scanner’ (StealthAUDITFSAA) failed to start. Verify that you have sufficient privileges to start system services. | The domain account used during setup doesn't have sufficient privileges to start the service. Open Local Security Policies on the proxy server. In User Rights Assignment under Local policies, add the user you want to the Log on as a service policy. After the user has this privilege, retry the installation. | The following are potential errors that may occur during File System scans and how to resolve each. | Error Message | Resolution | | --------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Failed to launch SDD client (2): The system cannot find the file specified. | This indicates the Sensitive Data Discovery Add-On is not installed on the proxy server. | -| Error creating DLP components. Error:Error initializing DLP communications, received invalid pipe handle. | This indicates the Sensitive Data Discovery Add-On is not installed on the proxy server. | -| Unable to start scan: Could not initialize scan session with any proxy host supplied | This can indicate a few things and is a broad error:
  • The Enterprise Auditor Console cannot reach the proxy server via the network.
  • Network communications are blocked for TCP on port 8766 – possibly by the Windows Firewall on the Enterprise Auditor Console server or proxy server, or by another firewall in the network (it is possible for this port to be customized through the FSAA Data Collector query configuration).
  • The Netwrix Enterprise Auditor FSAA Proxy Scanner service is not running or is not installed on the target proxy server.
| +| Failed to launch SDD client (2): The system can't find the file specified. | This indicates the Sensitive Data Discovery Add-On isn't installed on the proxy server. | +| Error creating DLP components. Error:Error initializing DLP communications, received invalid pipe handle. | This indicates the Sensitive Data Discovery Add-On isn't installed on the proxy server. | +| Unable to start scan: Couldn't initialize scan session with any proxy host supplied | This can indicate a few things and is a broad error:
  • The Enterprise Auditor Console can't reach the proxy server via the network.
  • The Windows Firewall on the Enterprise Auditor Console server or proxy server, or another firewall in the network, might block network communications for TCP on port 8766 (you can customize this port through the FSAA Data Collector query configuration).
  • The Netwrix Enterprise Auditor FSAA Proxy Scanner service isn't running or isn't installed on the target proxy server.
| ## Verbose Logging -Sometimes it is necessary to enable verbose logging in order to troubleshoot a problem with the +Sometimes you need to enable verbose logging to troubleshoot a problem with the proxy server. Run the following command in the directory where the installer lives (to prompt the install): diff --git a/docs/accessanalyzer/11.6/install/filesystemproxy/uninstall.md b/docs/accessanalyzer/11.6/install/filesystemproxy/uninstall.md index d2c3694cd9..5868728ced 100644 --- a/docs/accessanalyzer/11.6/install/filesystemproxy/uninstall.md +++ b/docs/accessanalyzer/11.6/install/filesystemproxy/uninstall.md @@ -6,8 +6,8 @@ sidebar_position: 50 # Uninstall Proxy Service Process -The process to properly uninstall the File System Proxy Service is completed through the -uninstalling of the Enterprise Auditor File System Scanning Proxy program. +To properly uninstall the File System Proxy Service, uninstall the Enterprise Auditor File System +Scanning Proxy program. **Step 1 –** Open Control Panel and select **Programs** > **Uninstall a program**. @@ -16,12 +16,12 @@ uninstalling of the Enterprise Auditor File System Scanning Proxy program. **Step 2 –** Select Netwrix Enterprise Auditor File System Scanning Proxy and click **Uninstall**. :::note -If the installation was configured to use the LocalSystem account to run the RPC service -the two SPN values are removed for that machine in Active Directory. If the service is running with -a supplied account, the SPN values would need to be manually removed for that machine in Active -Directory (unless the uninstall was completed as part of the +If the installation was configured to use the LocalSystem account to run the RPC service, the +uninstall process removes the two SPN values for that machine in Active Directory. If the service is +running with a supplied account, you must manually remove the SPN values for that machine in Active +Directory (unless you completed the uninstall as part of the [Upgrade Proxy Service Procedure](/docs/accessanalyzer/11.6/install/filesystemproxy/upgrade.md)). ::: -When the uninstall process is complete, this program is removed from the list. +When the uninstall process completes, the program no longer appears in the list. diff --git a/docs/accessanalyzer/11.6/install/filesystemproxy/upgrade.md b/docs/accessanalyzer/11.6/install/filesystemproxy/upgrade.md index 5a6351873e..ebcbdcaeb3 100644 --- a/docs/accessanalyzer/11.6/install/filesystemproxy/upgrade.md +++ b/docs/accessanalyzer/11.6/install/filesystemproxy/upgrade.md @@ -6,7 +6,7 @@ sidebar_position: 40 # Upgrade Proxy Service Procedure -When the Enterprise Auditor Console and File System Solution are upgraded, it is necessary to also +When you upgrade the Enterprise Auditor Console and File System Solution, also upgrade the File System Proxy Service when running Enterprise Auditor in Proxy Mode as a Service. This upgrade can be done in two ways: @@ -16,15 +16,15 @@ This upgrade can be done in two ways: :::warning When upgrading the Proxy Service to 11.6 from a previous version for the first time, you must manually uninstall the previous version and follow the [Manual Upgrade](#manual-upgrade) -steps below. Subsequent 11.6 upgrades can be done using the automatic upgrade option. +steps. You can use the automatic upgrade option for subsequent 11.6 upgrades. ::: ## Automatic Upgrade The **FS_UpdateProxy** Job is available through the Instant Job Wizard. This job updates the File -System Proxy Service on all servers in the assigned host list. Follow the steps to instantiate this -job. +System Proxy Service on all servers in the assigned host list. To instantiate this +job: **Step 1 –** Within the **Jobs** tree, right-click and select **Add Instant Job**. The Instant Job Wizard window opens. @@ -39,15 +39,15 @@ Expand the category and select the **FS_UpgradeProxy** Job. Click **Next**. **Step 4 –** On the Host Assignment page, select the **Specify individual hosts or host lists** option and click **Next**. -**Step 5 –** On the Host Lists page, assign the host lists containing the proxy servers to be -updated . Multiple host lists can be added. Click Next. +**Step 5 –** On the Host Lists page, assign the host lists containing the proxy servers to update. +You can add multiple host lists. Click Next. **Step 6 –** On the Individual Hosts page, click **Next**. **Step 7 –** Review the Summary and click either **Save & Exit** or **Save & Run Jobs Now**. -The proxy does not update until the job is run. Once successfully ran, the servers in the assigned -host lists have been updated. +The proxy doesn't update until you run the job. After the job runs successfully, the servers in the +assigned host lists are updated. ## Manual Upgrade diff --git a/docs/accessanalyzer/11.6/install/filesystemproxy/wizard.md b/docs/accessanalyzer/11.6/install/filesystemproxy/wizard.md index f7281c00c7..92a504e05c 100644 --- a/docs/accessanalyzer/11.6/install/filesystemproxy/wizard.md +++ b/docs/accessanalyzer/11.6/install/filesystemproxy/wizard.md @@ -6,7 +6,7 @@ sidebar_position: 10 # File System Proxy Service Installation -The File System Proxy installer is designed to simplify the process of setting up File System +The File System Proxy installer simplifies the process of setting up File System Scanning Proxy as a service on the designated proxy server. It is a best practice to use a specifically provisioned domain account as the File System Proxy service account. Follow the steps to install the FSAA service on the targeted proxy servers. @@ -34,8 +34,8 @@ folder page. On the Change destination folder page, choose a different destination folder for the installation. - Look in – Select which folder or sub-folder to complete installation in using the Look in - drop-down -- Up one level – Click the Up one level button to select the folder one level above the currently + dropdown +- Up one level – Click the Up one level button to select the folder one level above the selected one - Create a new folder – Click to create a new folder for the destination of the installation @@ -62,25 +62,25 @@ radio buttons. Then, click **Next**. **Step 7 –** When the installation completes, click **Finish** to exit the wizard. :::note -If the File System Proxy Service is installed on multiple servers, then a custom host list -of proxy servers should also be created in Netwrix Enterprise Auditor. +If you install the File System Proxy Service on multiple servers, also create a custom host list +of proxy servers in Netwrix Enterprise Auditor. ::: -Once the File System Proxy Service has been installed on any proxy server, it is necessary to +After you install the File System Proxy Service on any proxy server, configure the File System Solution certificate exchange method for Proxy Mode as a Service. See the [FSAA Applet Certificate Management Overview](/docs/accessanalyzer/11.6/admin/datacollector/fsaa/certificatemanagement/certificatemanagement.md) topic for additional information. ## Custom Parameters for File System Proxy Service -The port and priority parameters can be modified for the File System Proxy Service on the registry +You can modify the port and priority parameters for the File System Proxy Service on the registry key: **HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\StealthAUDITFSAA\ImagePath** - Port parameter – Only needs to be added to the registry key value if a custom port is used. The - default port of 8766 does not need to be set as a parameter + default port of 8766 doesn't need to be set as a parameter - Append `-e [PORT NUMBER]` to the ImagePath key value - Priority parameter – Can be modified so that the service runs as a background priority, which may be desired if the service has been installed directly on a file server @@ -98,12 +98,12 @@ key: ::: -Follow the steps to configure these service parameters. +To configure these service parameters: ![Netwrix Enterprise Auditor FSAA Proxy Scanner service in the Services Management Console](/images/accessanalyzer/11.6/install/filesystemproxy/service.webp) **Step 1 –** After installing the File System Proxy Service, open Services Management Console -(`services.msc`). To stop the service, right-click on the Netwrix Enterprise Auditor FSAA Proxy +(`services.msc`). To stop the service, right-click the Netwrix Enterprise Auditor FSAA Proxy Scanner service and select **Stop**. ![File System Proxy ImagePath registry key in the Registry Editor](/images/accessanalyzer/11.6/install/filesystemproxy/regedit.webp) @@ -112,8 +112,8 @@ Scanner service and select **Stop**. **HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\StealthAUDITFSAA\ImagePath** -**Step 3 –** Right-click on the **ImagePath** key and select **Modify**. The Value data was set -during installation according to the installation directory location selected. +**Step 3 –** Right-click the **ImagePath** key and select **Modify**. The installer set the Value +data during installation according to the installation directory location you selected. - Priority set to background priority: - Add `-r 0` to the end of the path value @@ -151,5 +151,5 @@ section for additional configurations required to run scans in proxy mode as a s **Step 7 –** Repeat the previous step for each of the **FileSystem** > **0.Collection** jobs to employ this proxy service. -The custom port identified is now used for communication between the File System Proxy Service and -Enterprise Auditor. +Enterprise Auditor and the File System Proxy Service now use the custom port you identified for +communication. diff --git a/docs/accessanalyzer/11.6/install/overview.md b/docs/accessanalyzer/11.6/install/overview.md index 7e6205d6f1..b302f2a678 100644 --- a/docs/accessanalyzer/11.6/install/overview.md +++ b/docs/accessanalyzer/11.6/install/overview.md @@ -23,7 +23,7 @@ topic for additional information. ## Sensitive Data Discovery Add-on The Sensitive Data Discovery Add-On enables Enterprise Auditor to scan files for criteria matches -which indicate the existence of sensitive data. Sensitive Data Discovery scans can be run against +which indicate the existence of sensitive data. You can run Sensitive Data Discovery scans against Windows file system servers, Network Attached Storage (NAS) devices, SharePoint on-premises, SharePoint Online, OneDrive for Business, DropBox for Business, SQL Server databases, and Exchange mailboxes. @@ -34,7 +34,7 @@ topic for additional information. ## File System Proxy Service -The File System Solution can be enabled to use proxy servers for scanning targeted file systems in +You can enable the File System Solution to use proxy servers for scanning targeted file systems in very large or widely dispersed environments. The File System Proxy installer is designed to simplify the process of setting up File System Scanning Proxy as a service on the designated proxy server. diff --git a/docs/accessanalyzer/11.6/install/sensitivedatadiscovery/overview.md b/docs/accessanalyzer/11.6/install/sensitivedatadiscovery/overview.md index c8dd0a6cc0..d8f17aab83 100644 --- a/docs/accessanalyzer/11.6/install/sensitivedatadiscovery/overview.md +++ b/docs/accessanalyzer/11.6/install/sensitivedatadiscovery/overview.md @@ -7,7 +7,7 @@ sidebar_position: 40 # Sensitive Data Discovery Add-On Installation The Sensitive Data Discovery Add-On enables Enterprise Auditor to scan files for criteria matches -which indicate the existence of sensitive data. Sensitive Data Discovery scans can be run against +which indicate the existence of sensitive data. You can run Sensitive Data Discovery scans against Windows file system servers, Network Attached Storage (NAS) devices, SharePoint on-premises, SharePoint Online, OneDrive for Business, DropBox for Business, SQL Server databases, and Exchange mailboxes. @@ -19,7 +19,7 @@ The version of the SharePoint Agent must also match the major version of Enterpr ## Supported Platforms -The Sensitive Data Discovery Add-On can be installed on the following servers: +You can install the Sensitive Data Discovery Add-On on the following servers: - Windows Server 2016 through Windows Server 2022 - On the Enterprise Auditor Console Server diff --git a/docs/accessanalyzer/11.6/install/sensitivedatadiscovery/upgrade.md b/docs/accessanalyzer/11.6/install/sensitivedatadiscovery/upgrade.md index 9cc92f7cc8..d44c3bbc64 100644 --- a/docs/accessanalyzer/11.6/install/sensitivedatadiscovery/upgrade.md +++ b/docs/accessanalyzer/11.6/install/sensitivedatadiscovery/upgrade.md @@ -6,7 +6,7 @@ sidebar_position: 20 # Upgrade Sensitive Data Discovery Add-on -When the Enterprise Auditor Console and applicable solutions are upgraded, it is necessary to also +When you upgrade the Enterprise Auditor Console and applicable solutions, also upgrade the Sensitive Data Discovery Add-On. ![Windows Control Panel Uninstall or change a program window](/images/accessanalyzer/11.6/install/sensitivedatadiscovery/uninstall.webp) diff --git a/docs/accessanalyzer/11.6/install/sensitivedatadiscovery/wizard.md b/docs/accessanalyzer/11.6/install/sensitivedatadiscovery/wizard.md index fddbbd0c8c..d19a5eda68 100644 --- a/docs/accessanalyzer/11.6/install/sensitivedatadiscovery/wizard.md +++ b/docs/accessanalyzer/11.6/install/sensitivedatadiscovery/wizard.md @@ -9,32 +9,32 @@ sidebar_position: 10 Remember, the following additional considerations: - File System Considerations: - - To run the **FileSystem** Job Group in Applet Mode or Proxy Mode with Applet, the targeted - file servers also need .NET Framework 4.7.2 or later to be installed in order for Sensitive - Data Discovery collections to successfully occur. - - To run the **FileSystem** Job Group in File System Proxy Mode as a Service, the Sensitive Data - Discovery Add-On (32-bit `SensitiveDataAddon.msi`) also needs to be installed on the proxy + - To run the **FileSystem** Job Group in Applet Mode or Proxy Mode with Applet, install .NET + Framework 4.7.2 or later on the targeted file servers so Sensitive Data Discovery collections + can occur successfully. + - To run the **FileSystem** Job Group in File System Proxy Mode as a Service, also install the + Sensitive Data Discovery Add-On (32-bit `SensitiveDataAddon.msi`) on the proxy server. The proxy server also requires the .NET Framework 4.7.2 or later. The Enterprise Auditor license file will need to be accessible locally for this installation. See the [File System Proxy as a Service Overview](/docs/accessanalyzer/11.6/install/filesystemproxy/overview.md) topic for additional information. -- SharePoint Consideration – To use the SharePoint Agent to scan for sensitive data, the Sensitive - Data Discovery Add-On (64-bit `SensitiveDataAddon.msi`) will also need to be installed on the +- SharePoint Consideration – To use the SharePoint Agent to scan for sensitive data, also install + the Sensitive Data Discovery Add-On (64-bit `SensitiveDataAddon.msi`) on the application server which hosts the Central Administration component of the targeted SharePoint - farms after the Enterprise Auditor SharePoint Agent has been installed on that server. The + farms, after you install the Enterprise Auditor SharePoint Agent on that server. The SharePoint server also requires .NET Framework 4.7.2 or later. The Enterprise Auditor license file will need to be accessible locally for this installation. See the [SharePoint Agent Installation](/docs/accessanalyzer/11.6/install/sharepointagent/overview.md) topic for additional information. :::note -Before running the installation package, please close the Enterprise Auditor application. +Before running the installation package, close the Enterprise Auditor application. ::: -The Enterprise Auditor license file is needed during installation. It can be imported from the -Enterprise Auditor installation directory when the add-on is installed on the Enterprise Auditor -Console server. Follow the steps to install the Sensitive Data Discovery Add-On. +You need the Enterprise Auditor license file during installation. You can import it from the +Enterprise Auditor installation directory when you install the add-on on the Enterprise Auditor +Console server. To install the Sensitive Data Discovery Add-On: **Step 1 –** Run the `SensitiveDataAddon.exe` executable. @@ -95,7 +95,7 @@ solutions, according to the organization’s license: - SharePoint - SQL -Prior to job execution, ensure the desired criteria have been properly configured for each job. See +Before job execution, ensure you have properly configured the criteria you want for each job. See the [Sensitive Data Discovery Add-On Installation](/docs/accessanalyzer/11.6/install/sensitivedatadiscovery/overview.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/install/sharepointagent/overview.md b/docs/accessanalyzer/11.6/install/sharepointagent/overview.md index 2f606f00fc..422f54a968 100644 --- a/docs/accessanalyzer/11.6/install/sharepointagent/overview.md +++ b/docs/accessanalyzer/11.6/install/sharepointagent/overview.md @@ -22,8 +22,8 @@ The version of the SharePoint Agent must also match the major version of Enterpr ## Supported Platforms -The SharePoint Agent for the Enterprise Auditor SharePoint & SharePoint Online Solution can be -installed on the following SharePoint versions as targeted environments: +You can install the SharePoint Agent for the Enterprise Auditor SharePoint & SharePoint Online +Solution on the following SharePoint versions as targeted environments: - SharePoint® 2019 - SharePoint® 2016 @@ -31,17 +31,17 @@ installed on the following SharePoint versions as targeted environments: ## Sensitive Data Discovery Auditing Consideration -If utilizing the SharePoint Agent to scan for Sensitive Data, install the Sensitive Data Add-on – -SPAA Agent (or x64) version of the Sensitive Data Discovery Add-On after the SharePoint Agent has -been installed on the SharePoint server. This requirement is in addition to having the Sensitive +If using the SharePoint Agent to scan for Sensitive Data, install the Sensitive Data Add-on – +SPAA Agent (or x64) version of the Sensitive Data Discovery Add-On after you install the SharePoint +Agent on the SharePoint server. This requirement is in addition to having the Sensitive Data Discovery Add-on installed on the Enterprise Auditor Console server. Sensitive Data Discovery Auditing scans also require .NET Framework 4.7.2 or later. :::note -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the +If running Sensitive Data Discovery (SDD) scans, you must increase the minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For -example, if the job is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are -required (8x2=16). +example, if you configure the job to scan 8 hosts at a time, the job requires an extra 16 GB of RAM +(8x2=16). ::: diff --git a/docs/accessanalyzer/11.6/install/sharepointagent/upgrade.md b/docs/accessanalyzer/11.6/install/sharepointagent/upgrade.md index cd050de11c..a1996d3418 100644 --- a/docs/accessanalyzer/11.6/install/sharepointagent/upgrade.md +++ b/docs/accessanalyzer/11.6/install/sharepointagent/upgrade.md @@ -6,7 +6,7 @@ sidebar_position: 20 # Upgrade SharePoint Agent -Follow the steps to upgrade the SharePoint Agent. +To upgrade the SharePoint Agent: ![Windows Control Panel Uninstall or change a program window](/images/accessanalyzer/11.6/install/sharepointagent/uninstall.webp) @@ -17,11 +17,11 @@ Features**), uninstall the previous version of SharePoint Agent. [Installing the SharePoint Agent](/docs/accessanalyzer/11.6/install/sharepointagent/wizard.md) topic for instructions. -**Step 3 –** If also conducting Sensitive Data Discovery Auditing, after the installation is -completed upgrade the Sensitive Data Discovery Add-on on the SharePoint server. See the +**Step 3 –** If also conducting Sensitive Data Discovery Auditing, after the installation completes, +upgrade the Sensitive Data Discovery Add-on on the SharePoint server. See the [Sensitive Data Discovery Add-On Installation](/docs/accessanalyzer/11.6/install/sensitivedatadiscovery/overview.md) topic for additional information. -Now that the SharePoint Agent has been upgraded, it can be used by the SharePoint Solution. See the +Now that you have upgraded the SharePoint Agent, the SharePoint Solution can use it. See the [SharePoint Solution](/docs/accessanalyzer/11.6/solutions/sharepoint/overview.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/install/sharepointagent/wizard.md b/docs/accessanalyzer/11.6/install/sharepointagent/wizard.md index b329afc712..71db1055f0 100644 --- a/docs/accessanalyzer/11.6/install/sharepointagent/wizard.md +++ b/docs/accessanalyzer/11.6/install/sharepointagent/wizard.md @@ -16,7 +16,7 @@ the Enterprise Auditor Console. See the topic for detailed permission information. :::note -If utilizing the SharePoint Agent to scan for Sensitive Data, the 64-bit +If using the SharePoint Agent to scan for Sensitive Data, the 64-bit `SensitiveDataAddon.msi` needs to be installed after the SharePoint Agent has been installed on the SharePoint server. See the [Sensitive Data Discovery Add-On Installation](/docs/accessanalyzer/11.6/install/sensitivedatadiscovery/overview.md) @@ -24,8 +24,8 @@ topic for additional information. ::: -Follow the steps to install the SharePoint Agent on the application server which hosts the Central -Administration component of the targeted SharePoint farms. +To install the SharePoint Agent on the application server which hosts the Central +Administration component of the targeted SharePoint farms: **Step 1 –** Run the `SharePointAgent.exe` executable to open the Netwrix Enterprise Auditor SharePoint Agent Setup Wizard. diff --git a/docs/accessanalyzer/11.6/install/stealthauditmapicdoinstallation/appendix.md b/docs/accessanalyzer/11.6/install/stealthauditmapicdoinstallation/appendix.md index 2740c9d681..183ff4ab75 100644 --- a/docs/accessanalyzer/11.6/install/stealthauditmapicdoinstallation/appendix.md +++ b/docs/accessanalyzer/11.6/install/stealthauditmapicdoinstallation/appendix.md @@ -7,22 +7,22 @@ sidebar_position: 10 # Appendix for the StealthAUDIT MAPI CDO Installation Guide :::warning -The Enterprise Auditor MAPI CDO must be installed first before installing the Microsoft +You must install the Enterprise Auditor MAPI CDO first before installing the Microsoft Exchange MAPI CDO. ::: -Before installing either binary, close the Enterprise Auditor application and ensure the following -requirements have been met: +Before installing either binary, close the Enterprise Auditor application and ensure you meet the +following requirements: -- Exchange System Manager for Exchange 2003 is not installed on the Enterprise Auditor Console +- Exchange System Manager for Exchange 2003 isn't installed on the Enterprise Auditor Console server. -- Microsoft Outlook is not installed on the Enterprise Auditor Console server. +- Microsoft Outlook isn't installed on the Enterprise Auditor Console server. These programs will interfere with the Microsoft Exchange MAPI CDO installation and with MAPI -connections if they are installed on the Enterprise Auditor Console server. +connections if you install them on the Enterprise Auditor Console server. -Follow these steps to install the Microsoft Exchange MAPI CDO. +To install the Microsoft Exchange MAPI CDO: **Step 1 –** Download and run the ExchangeMapiCDO application from Microsoft. @@ -55,5 +55,4 @@ agreement and click Next. **Step 6 –** When the installation is complete, click Finish. -Reopen the Enterprise Auditor application, and the Settings > Exchange node is enabled for -configuration. +Reopen the Enterprise Auditor application. You can now configure the Settings > Exchange node. diff --git a/docs/accessanalyzer/11.6/install/stealthauditmapicdoinstallation/stealthaudit_mapi_cdo_installation.md b/docs/accessanalyzer/11.6/install/stealthauditmapicdoinstallation/stealthaudit_mapi_cdo_installation.md index 2723c66504..3814db4e12 100644 --- a/docs/accessanalyzer/11.6/install/stealthauditmapicdoinstallation/stealthaudit_mapi_cdo_installation.md +++ b/docs/accessanalyzer/11.6/install/stealthauditmapicdoinstallation/stealthaudit_mapi_cdo_installation.md @@ -6,8 +6,8 @@ sidebar_position: 50 # StealthAUDIT MAPI CDO Installation -Both the Enterprise Auditor MAPI CDO and the Microsoft® Exchange MAPI CDO must to be installed in -order to enable the Settings > Exchange node. +You must install both the Enterprise Auditor MAPI CDO and the Microsoft® Exchange MAPI CDO to +enable the Settings > Exchange node. ![exchangenode](/images/accessanalyzer/11.6/stealthaudit/install_guides/mapi_cdo_install/exchangenode.webp) @@ -15,29 +15,29 @@ The Microsoft Exchange MAPI CDO is only required to run the MAPI-based data coll [Exchange Solution](/docs/accessanalyzer/11.6/solutions/exchange/overview.md) topic for additional information. -The Enterprise Auditor MAPI CDO can be downloaded from the -[Product Downloads](https://www.stealthbits.com/product-downloads) page of the Netwrix website. The -Microsoft Exchange MAPI CDO can be downloaded directly from Microsoft. See the +You can download the Enterprise Auditor MAPI CDO from the +[Product Downloads](https://www.stealthbits.com/product-downloads) page of the Netwrix website. You +can download the Microsoft Exchange MAPI CDO directly from Microsoft. See the [Appendix for the StealthAUDIT MAPI CDO Installation Guide](/docs/accessanalyzer/11.6/install/stealthauditmapicdoinstallation/appendix.md) for requirements and installation steps to install the Microsoft Exchange MAPI CDO. :::warning -The Enterprise Auditor MAPI CDO must be installed first before installing the Microsoft +You must install the Enterprise Auditor MAPI CDO first before installing the Microsoft Exchange MAPI CDO. ::: -Before installing either binary, close the Enterprise Auditor application and ensure the following -requirements have been met: +Before installing either binary, close the Enterprise Auditor application and ensure you meet the +following requirements: -- Exchange System Manager for Exchange 2003 is not installed on the Enterprise Auditor Console +- Exchange System Manager for Exchange 2003 isn't installed on the Enterprise Auditor Console server. -- Microsoft Outlook is not installed on the Enterprise Auditor Console server. +- Microsoft Outlook isn't installed on the Enterprise Auditor Console server. -These programs interfere with MAPI connections if they are installed on the Enterprise Auditor +These programs interfere with MAPI connections if you install them on the Enterprise Auditor Console server. -Follow the steps to install the Enterprise Auditor MAPI CDO. +To install the Enterprise Auditor MAPI CDO: **Step 1 –** Run the StealthAuditMapiCDO executable. diff --git a/docs/accessanalyzer/11.6/requirements/activedirectory/activedirectory.md b/docs/accessanalyzer/11.6/requirements/activedirectory/activedirectory.md index 960b926772..85a67e7734 100644 --- a/docs/accessanalyzer/11.6/requirements/activedirectory/activedirectory.md +++ b/docs/accessanalyzer/11.6/requirements/activedirectory/activedirectory.md @@ -11,8 +11,8 @@ Server, and Access Information Center. See the [Requirements](/docs/accessanalyzer/11.6/requirements/overview.md) topic for the core requirements. -In addition to these, integration with either the Netwrix Activity Monitor or the Netwrix Threat -Prevention is required for event activity data to be scanned. See the +In addition to these, you need integration with either the Netwrix Activity Monitor or the Netwrix +Threat Prevention to scan event activity data. See the [Netwrix Activity Monitor Documentation](https://helpcenter.netwrix.com/category/activitymonitor) or the [Netwrix Threat Prevention Documentation](https://helpcenter.netwrix.com/category/threatprevention) diff --git a/docs/accessanalyzer/11.6/requirements/activedirectory/activedirectory/access.md b/docs/accessanalyzer/11.6/requirements/activedirectory/activedirectory/access.md index 1666cfd408..02fb9ab674 100644 --- a/docs/accessanalyzer/11.6/requirements/activedirectory/activedirectory/access.md +++ b/docs/accessanalyzer/11.6/requirements/activedirectory/activedirectory/access.md @@ -47,7 +47,7 @@ passwords, permissions, group policies, and domain information: - Member of the Domain Administrators group The majority of jobs in the Active Directory solutions rely on tables with queried data from the -data collectors mentioned above to perform analysis and generate reports. The remaining jobs utilize +data collectors mentioned above to perform analysis and generate reports. The remaining jobs use data collectors to scan environments, and require additional permissions on the target host. :::info @@ -104,14 +104,14 @@ The following firewall ports are needed: ## Least Privilege Model -A least privilege model can be configured based on your auditing needs and the data collection jobs -you will be using. The following jobs and their corresponding data collectors can be run with a +You can configure a least privilege model based on your auditing needs and the data collection jobs +you will be using. You can run the following jobs and their corresponding data collectors with a least privilege permissions model. **1-AD_Scan Job Permissions** The ADInventory Data Collector in the .Active Directory Inventory > 1-AD_Scan Job has the following -minimum requirements, which must be configured at the Domain level in Active Directory: +minimum requirements, which you must configure at the Domain level in Active Directory: - Read access to directory tree - List Contents & Read Property on the Deleted Objects Container @@ -141,15 +141,15 @@ requirements: **AD_CPassword Job Permissions** While the PowerShell Data Collector typically requires Domain Administrator permissions when -targeting a domain controller, that level of access is not required to run the 4.Group Policy > +targeting a domain controller, that level of access isn't required to run the 4.Group Policy > AD_CPasswords job. The minimum requirements for running this job are: -- Read access to SYSVOL on the targeted Domain Controller(s) and all of its children +- Read access to SYSVOL on the targeted Domain Controllers and all of its children **AD_GroupPolicy Job Permissions** While the GroupPolicy Data Collector typically requires Domain Administrator permissions when -targeting a domain controller, that level of access is not required to run the 4.Group Policy > +targeting a domain controller, that level of access isn't required to run the 4.Group Policy > AD_GroupPolicy Job. The minimum requirements for running this job are: - Requires Read permissions on Group Policy Objects @@ -157,7 +157,7 @@ AD_GroupPolicy Job. The minimum requirements for running this job are: **AD_PasswordPolicies Job Permissions** While the LDAP Data Collector typically requires Domain Administrator permissions when targeting a -domain controller, that level of access is not required to run the 4.Group Policy > +domain controller, that level of access isn't required to run the 4.Group Policy > AD_PasswordPolicies Job. The minimum requirements for running this job are: - Requires Read permissions on the Password Settings Container @@ -165,7 +165,7 @@ AD_PasswordPolicies Job. The minimum requirements for running this job are: **AD_DomainControllers Job Permissions** While the LDAP Data Collector and Active Directory Data Collector typically requires Domain -Administrator permissions when targeting a domain controller, that level of access is not required +Administrator permissions when targeting a domain controller, that level of access isn't required to run the 5.Domains > 0.Collection > AD_DomainControllers Job. The minimum requirements for running this job are: @@ -179,7 +179,7 @@ See the [Variable Definitions](#variable-definitions) for variable definitions. **AD_DSRM Job Permissions** While the Registry Data Collector typically requires Domain Administrator permissions when targeting -a domain controller, that level of access is not required to run the 5.Domains > 0.Collection > +a domain controller, that level of access isn't required to run the 5.Domains > 0.Collection > AD_DSRM Job. The minimum requirements for running this job are: - Requires read access to the following Registry key and its children: @@ -192,7 +192,7 @@ Alternatively, granting access to the Server Operators group also allows read-on **AD_TimeSync Job Permissions** While the Registry Data Collector typically requires Domain Administrator permissions when targeting -a domain controller, that level of access is not required to run the 5.Domains > 0.Collection > +a domain controller, that level of access isn't required to run the 5.Domains > 0.Collection > AD_TimeSync Job. The minimum requirements for running this job are: - Requires Read access to the following Registry keys and its children: @@ -205,9 +205,9 @@ Alternatively, granting access to the Network Configuration Operators group also **AD_DomainInfo Job Permissions** While the LDAP Data Collector and Active Directory Data Collector typically requires Domain -Administrator permissions when targeting a domain controller, that level of access is not required -to run the 5.Domains > AD_DomainInfo Job. The minimum requirements for running this job, which must -be configured at the Domain level in Active Directory, are: +Administrator permissions when targeting a domain controller, that level of access isn't required +to run the 5.Domains > AD_DomainInfo Job. The minimum requirements for running this job, which you +must configure at the Domain level in Active Directory, are: - Read access to: %DOMAINDN% and its children - Read access to: CN=System,%DOMAINDN% and its children diff --git a/docs/accessanalyzer/11.6/requirements/activedirectory/activedirectory/activity/activity.md b/docs/accessanalyzer/11.6/requirements/activedirectory/activedirectory/activity/activity.md index 7af3705508..462f5d6be4 100644 --- a/docs/accessanalyzer/11.6/requirements/activedirectory/activedirectory/activity/activity.md +++ b/docs/accessanalyzer/11.6/requirements/activedirectory/activedirectory/activity/activity.md @@ -31,8 +31,8 @@ In this method, you will be deploying two agents: - Next, deploy the AD Agent to all domain controllers in the target domain. -Follow the steps to setup integration between Activity Monitor and Enterprise Auditor through an API -server. +To set up integration between Activity Monitor and Enterprise Auditor through an API +server: **Step 1 –** Deploy the Activity Agent to the API server. @@ -42,7 +42,7 @@ The next step is to configure the agent deployed to the API server. ## Configure API Server Agent -Follow the steps to configure the agent deployed to the API server. +To configure the agent deployed to the API server: **Step 1 –** On the Agents tab of the Activity Monitor Console, select the agent deployed to the API server. @@ -52,8 +52,8 @@ API server. **Step 3 –** Select the **API Server** tab and configure the following: - Select the **Enable API access on this agent** checkbox. -- The default **API server port (TCP)** is 4494, but it can be modified if desired. Ensure the - modified port is also used by Enterprise Auditor. +- The default **API server port (TCP)** is 4494, but you can modify it if desired. Ensure + Enterprise Auditor also uses the modified port. - Click **Add Application**. The Add or edit API client window opens. - Configure the following: @@ -64,19 +64,19 @@ API server. - Click **Copy** and save the Client Secret value to a text file. :::warning - It is not possible to retrieve the value after closing the Add or edit - API client window. It must be copied first. + You can't retrieve the value after closing the Add or edit + API client window. Copy it first. ::: - - By default, the **Secret Expires** in 3 days. That means it must be used in the Enterprise - Auditor Connection Profile within 72 hours or a new secret will need to be generated. Modify + - By default, the **Secret Expires** in 3 days. That means you must use it in the Enterprise + Auditor Connection Profile within 72 hours, or you'll need to generate a new secret. Modify if desired. - Click **OK** to save the configuration and close the Add or edit API client window. -- If the Activity Monitor Console server is not the API Server, then click **Use this console** to +- If the Activity Monitor Console server isn't the API Server, then click **Use this console** to grant the Activity Monitor the ability to manage the API server. -- The IPv4 or IPv6 allowlist allows you to limit access to the API server data to specific hosts. +- Use the IPv4 or IPv6 allowlist to limit access to the API server data to specific hosts. **Step 4 –** Click **OK** to save the configuration and close the Agent properties window. @@ -84,7 +84,7 @@ The next step is to configure the agents deployed to the domain controllers. ## Configure Domain Controller Agent -Follow the steps to configure the agent deployed to the domain controller. +To configure the agent deployed to the domain controller: **Step 1 –** On the Agents tab of the Activity Monitor Console, select an agent deployed to domain controller. @@ -95,9 +95,9 @@ controller. - Select the **Enable Archiving for this agent** checkbox. - Select the **Archive log files on a UNC path** option. Click the **...** button and navigate to - the desired network share on the API server. -- The **User name** and **User password** fields only need to be filled in if the account used to - install the agent does not have access to this share. + the network share you want on the API server. +- Fill in the **User name** and **User password** fields only if the account used to + install the agent doesn't have access to this share. :::tip Remember, The account used to install the agent on a domain controller is a Domain @@ -111,21 +111,21 @@ controller. **Step 5 –** Repeat Steps 1-4 for each agent deployed to domain controller. -These agent are configured to save the Archive logs to the selected share. +These agents now save the Archive logs to the selected share. ## Configure Monitored Domain Output -Follow the steps configure the monitored domain output for Netwrix Enterprise Auditor. +To configure the monitored domain output for Netwrix Enterprise Auditor: **Step 1 –** Select the **Monitored Domains** tab. -**Step 2 –** Select the desired domain and click **Add Output**. The Add New Ouptut window opens. +**Step 2 –** Select the domain you want and click **Add Output**. The Add New Ouptut window opens. **Step 3 –** Configure the following: -- Configure the desired number of days for the **Period to keep Log files**. This is the number of - days the log files are kept on the API server configured in the sections above. This needs to be - set to a greater value than the days between Enterprise Auditor scans. +- Configure the number of days you want for the **Period to keep Log files**. This is the number of + days the log files are kept on the API server configured in the sections above. Set this to a + greater value than the days between Enterprise Auditor scans. - For example, if Enterprise Auditor runs the **AD_ActivityCollection** Job once a week (every 7 days), then the Activity Monitor output should be configured to retain at least 10 days of log @@ -142,12 +142,12 @@ Enterprise Auditor now has access to the agent log files for this domain. ## Configure Enterprise Auditor Connection Profile -Follow the steps to configure the Connection Profile in Enterprise Auditor. +To configure the Connection Profile in Enterprise Auditor: :::tip -Remember, the Client ID and Client Secret were generated by the API server and copied to a text -file. If the secret expired before the Connection Profile is configured, it will need to be -re-generated. +Remember, the API server generated the Client ID and Client Secret, which you copied to a text +file. If the secret expires before you configure the Connection Profile, you'll need to +regenerate it. ::: @@ -172,19 +172,19 @@ name. Group. Select the **Settings > Connection** node. **Step 7 –** Select the **Select one of the following user defined profiles** option. Expand the -drop-down menu and select the Connection Profile with this credential. +dropdown menu and select the Connection Profile with this credential. **Step 8 –** Click **Save** and then **OK** to confirm the changes to the job group settings. -The Connection Profile will now be used for AD Activity collection. +Enterprise Auditor will now use the Connection Profile for AD Activity collection. ## Configure the AD_ActivityCollection Job -The Enterprise Auditor requires additional configurations in order to collect domain activity data. -Follow the steps to configure the **AD_ActivityCollection** Job. +The Enterprise Auditor requires additional configurations to collect domain activity data. +To configure the **AD_ActivityCollection** Job: :::note -Ensure that the **.Active Directory Inventory** Job Group has been successfully run +Ensure that you have successfully run the **.Active Directory Inventory** Job Group against the target domain. ::: @@ -223,10 +223,10 @@ last step. - Absolute Timespan – Set the date range for activity logs to collect when the scan is run :::info -The threshold should be set to ensure the logs are collected before the Activity +Set the threshold to ensure you collect the logs before the Activity Monitor domain output log retention expires. For example, if Enterprise Auditor runs the -**AD_ActivityCollection** Job once a week (every 7 days), then the Activity Monitor output should be -configured to retain at least 10 days of log files. +**AD_ActivityCollection** Job once a week (every 7 days), then configure the Activity Monitor +output to retain at least 10 days of log files. ::: @@ -246,30 +246,29 @@ Credential with the Refresh token: - Click **OK** to save and close the User Credentials window. - Click **Save** and then **OK** to confirm the changes to the Connection Profile. -The query is now configured to target the Activity Monitor API Server to collect domain activity -logs. +The query now targets the Activity Monitor API Server to collect domain activity logs. ### (Optional) Configure Import of AD Activity into Netwrix Access Information Center -AD Activity data can be imported into Netwrix Access Information Center by the -**AD_ActivityCollection** Job. However, this is disabled by default. Follow the steps to enable the -importing of AD activity data into the Access Information Center. +The **AD_ActivityCollection** Job can import AD Activity data into Netwrix Access Information +Center. However, this feature is disabled by default. To enable the import of AD activity data +into the Access Information Center: **Step 1 –** Navigate to the **Jobs** > **Active Directory** > **6.Activity** > **0.Collection** > **AD_ActivityCollection** Job. **Step 2 –** On the job's Overview page, enable the import of AD Events. -- Click on the **Enable to import AD events into the AIC** parameter. +- Click the **Enable to import AD events into the AIC** parameter. - On the Parameter Configuration window, select the **Enabled** checkbox and click **Save**. **Step 3 –** On the job's Overview page, enable the import of authentication Events. -- Click on the **Enable to import authentication events into the AIC** parameter. +- Click the **Enable to import authentication events into the AIC** parameter. - On the Parameter Configuration window, select the **Enabled** checkbox and click **Save**. **Step 4 –** Optionally, modify the **List of attributes to track for Object Modified changes** and **Number of days to retain activity data in the AIC** parameters. -The **AD_ActivityCollection** Job is now configured to import both AD events and authentication +The **AD_ActivityCollection** Job now imports both AD events and authentication events into the Netwrix Access Information Center. diff --git a/docs/accessanalyzer/11.6/requirements/activedirectory/activedirectory/activity/filearchive.md b/docs/accessanalyzer/11.6/requirements/activedirectory/activedirectory/activity/filearchive.md index 077a809fb8..690a4f4641 100644 --- a/docs/accessanalyzer/11.6/requirements/activedirectory/activedirectory/activity/filearchive.md +++ b/docs/accessanalyzer/11.6/requirements/activedirectory/activedirectory/activity/filearchive.md @@ -16,7 +16,7 @@ Deploy the AD Agent to each domain controller in the target domain. ## Configure Domain Controller Agent -Follow the steps to configure the agent deployed to the domain controller. +Configure the agent deployed to the domain controller. :::note These steps assume the network share where the activity log files will be archived already @@ -35,7 +35,7 @@ controller. - Select the **Archive log files on a UNC path** option. Click the ... button and navigate to the desired network share. - The **User name** and **User password** fields only need to be filled in if the account used to - install the agent does not have access to this share. + install the agent doesn't have access to this share. :::tip Remember, The account used to install the agent on a domain controller is a Domain @@ -52,7 +52,7 @@ controller. **Step 5 –** Repeat Steps 1-4 for each agent deployed to domain controller pointing to the same network share in Step 3 for each agent. -These agent are configured to save the Archive logs to the selected share. +These agents now save the Archive logs to the selected share. ## Configure Monitored Domain Output @@ -60,13 +60,13 @@ Follow the steps configure the monitored domain output for Netwrix Enterprise Au **Step 1 –** Select the **Monitored Domains** tab. -**Step 2 –** Select the desired domain and click **Add Output**. The Add New Ouptut window opens. +**Step 2 –** Select the domain you want and click **Add Output**. The Add New Ouptut window opens. **Step 3 –** Configure the following: -- Configure the desired number of days for the **Period to keep Log files**. This is the number of - days the log files are kept on the API server configured in the sections above. This needs to be - set to a greater value than the days between Enterprise Auditor scans. +- Configure the number of days you want for the **Period to keep Log files**. This is the number of + days the log files are kept on the API server configured in the sections above. Set this to a + greater value than the days between Enterprise Auditor scans. - For example, if Enterprise Auditor runs the **AD_ActivityCollection** Job once a week (every 7 days), then the Activity Monitor output should be configured to retain at least 10 days of log @@ -83,7 +83,7 @@ Enterprise Auditor now has access to the agent log files for this domain. ## Configure Enterprise Auditor Connection Profile -Follow the steps to configure the Connection Profile in Enterprise Auditor. +Configure the Connection Profile in Enterprise Auditor. **Step 1 –** On the Settings > Connection node of the Enterprise Auditor Console, select the Connection Profile for the Active Directory solution. If you haven't yet created a Connection @@ -111,19 +111,19 @@ name. the **Settings > Connection** node. **Step 7 –** Select the **Select one of the following user defined profiles** option. Expand the -drop-down menu and select the Connection Profile with this credential. +dropdown menu and select the Connection Profile with this credential. **Step 8 –** Click **Save** and then **OK** to confirm the changes to the job group settings. -The Connection Profile will now be used for AD Activity collection. +Enterprise Auditor will now use the Connection Profile for AD Activity collection. ## Configure the AD_ActivityCollection Job -The Enterprise Auditor requires additional configurations in order to collect domain activity data. -Follow the steps to configure the **AD_ActivityCollection** Job. +The Enterprise Auditor requires additional configurations to collect domain activity data. +Configure the **AD_ActivityCollection** Job. :::note -Ensure that the .Active Directory Inventory Job Group has been successfully run against +Ensure that you have successfully run the .Active Directory Inventory Job Group against the target domain. ::: @@ -154,10 +154,10 @@ Click **Next**. - Absolute Timespan – Set the date range for activity logs to collect when the scan is run :::info -The threshold should be set to ensure the logs are collected before the Activity +Set the threshold to ensure you collect the logs before the Activity Monitor domain output log retention expires. For example, if Enterprise Auditor runs the -**AD_ActivityCollection** Job once a week (every 7 days), then the Activity Monitor output should be -configured to retain at least 10 days of log files. +**AD_ActivityCollection** Job once a week (every 7 days), then configure the Activity Monitor +output to retain at least 10 days of log files. ::: @@ -168,5 +168,5 @@ keeps the collected data in the SQL Server database. **Step 9 –** Click **OK** to save the changes and close the Query Properties page. -The query is now configured to target the network share where the Activity Monitor domain activity -logs are archived. +The query now targets the network share where the Activity Monitor archives domain activity +logs. diff --git a/docs/accessanalyzer/11.6/requirements/activedirectory/activedirectory/activity/threatprevention.md b/docs/accessanalyzer/11.6/requirements/activedirectory/activedirectory/activity/threatprevention.md index 9bf711d9c7..ae37df26f7 100644 --- a/docs/accessanalyzer/11.6/requirements/activedirectory/activedirectory/activity/threatprevention.md +++ b/docs/accessanalyzer/11.6/requirements/activedirectory/activedirectory/activity/threatprevention.md @@ -6,19 +6,19 @@ sidebar_position: 20 # Getting Data from NTP for AD Activity Reporting -When Netwrix Threat Prevention is configured to monitor a domain, the event data collected by the -policies can be provided to Netwrix Enterprise Auditor for Active Directory Activity reporting. This -is accomplished by configuring Threat Prevention to send data to Netwrix Activity Monitor, which in -turn creates the activity log files that Enterprise Auditor collects. +When you configure Netwrix Threat Prevention to monitor a domain, you can provide the event data +collected by the policies to Netwrix Enterprise Auditor for Active Directory Activity reporting. To +do this, configure Threat Prevention to send data to Netwrix Activity Monitor, which in turn creates +the activity log files that Enterprise Auditor collects. :::note -Threat Prevention can only be configured to send event data to one Netwrix application, -either Netwrix Activity Monitor or Netwrix Threat Manager but not both. However, the Activity -Monitor can be configured with outputs for Enterprise Auditor and Threat Manager +You can only configure Threat Prevention to send event data to one Netwrix application, +either Netwrix Activity Monitor or Netwrix Threat Manager but not both. However, you can configure +the Activity Monitor with outputs for Enterprise Auditor and Threat Manager. ::: -Follow these steps to configure this integration. +Configure this integration. :::info It is a best practice to use the API Server option of the Activity Monitor for @@ -36,17 +36,16 @@ Threat Manager Configuration** on the menu. The Netwrix Threat Manager Configura `amqp://localhost:4499` - You must use localhost, even if Activity Monitor and Threat Prevention are installed on + You must use localhost, even if you install Activity Monitor and Threat Prevention on different servers. - App Token – Leave this field blank for integration with Activity Monitor - Policies – The table displays all policies created in Threat Prevention along with a State icon - indicating if the policy is active. Check the **Send** box for the desired policies monitoring the - target domain activity. + indicating if the policy is active. Check the **Send** box for the policies you want to send that + monitor the target domain activity. **Step 3 –** Click **Save**. -All real-time event data from the selected policies are now being sent to Activity Monitor. -Additional policies can be added to this data stream through the Netwrix Threat Manager -Configuration window or by selecting the **Send to Netwrix Threat Manager** option on the Actions -tab of the policy. +Activity Monitor now receives all real-time event data from the selected policies. You can add +additional policies to this data stream through the Netwrix Threat Manager Configuration window or +by selecting the **Send to Netwrix Threat Manager** option on the Actions tab of the policy. diff --git a/docs/accessanalyzer/11.6/requirements/activedirectory/activedirectory/overview.md b/docs/accessanalyzer/11.6/requirements/activedirectory/activedirectory/overview.md index 8c17dbdcdf..5d6efdac10 100644 --- a/docs/accessanalyzer/11.6/requirements/activedirectory/activedirectory/overview.md +++ b/docs/accessanalyzer/11.6/requirements/activedirectory/activedirectory/overview.md @@ -6,8 +6,8 @@ sidebar_position: 10 # Active Directory Domain Target Requirements -Netwrix Enterprise Auditor can execute scans on Active Directory domains. The Netwrix Activity -Monitor can be configured to monitor activity on Active Directory domains and make the event data +Netwrix Enterprise Auditor can execute scans on Active Directory domains. You can configure the +Netwrix Activity Monitor to monitor activity on Active Directory domains and make the event data available for Enterprise Auditor Active Directory Activity scans. ## Auditing Permissions @@ -29,7 +29,7 @@ topic for additional information. ## Activity Auditing Permissions :::note -Active Directory domain activity events can also be monitored through Netwrix Threat +You can also monitor Active Directory domain activity events through Netwrix Threat Prevention. This requires integration between it and Netwrix Activity Monitor to enable access to the data for Enterprise Auditor Active Directory Activity scans. See the [Getting Data from NTP for AD Activity Reporting](/docs/accessanalyzer/11.6/requirements/activedirectory/activedirectory/activity/threatprevention.md) @@ -39,8 +39,8 @@ topic for additional information. Requirements to Deploy the AD Agent on the Domain Controller -The Netwrix Activity Monitor must have an AD Agent deployed on the domain controller to be -monitored. While actively monitoring, the AD Agent generates activity log files stored on the +The Netwrix Activity Monitor must have an AD Agent deployed on the domain controller you want to +monitor. While actively monitoring, the AD Agent generates activity log files stored on the server. The credential used to deploy the AD Agent must have the following permissions on the server: @@ -48,8 +48,8 @@ server: - READ and WRITE access to the archive location for Archiving feature only :::note -For monitoring an Active Directory domain, the AD Agent must be installed on all domain -controllers within the domain to be monitored. +To monitor an Active Directory domain, install the AD Agent on all domain +controllers within the domain you want to monitor. ::: @@ -58,8 +58,8 @@ Enterprise Auditor to read the activity log files must have also have this permi **Activity Monitor Archive Location** -If the activity log files are being archived, configurable within the Netwrix Activity Monitor -Console, then the credential used by Enterprise Auditor to read the activity log files must also +If you archive the activity log files, configurable within the Netwrix Activity Monitor +Console, then the credential Enterprise Auditor uses to read the activity log files must also have READ and WRITE permissions on the archive location. **Integration with Enterprise Auditor** @@ -77,9 +77,9 @@ are required for communication between the Agent server and the Netwrix Activity | -------------------------------- | -------- | ----- | ------------------- | | Activity Monitor to Agent Server | TCP | 4498 | Agent Communication | -The Windows firewall rules need to be configured on the Windows server, which require certain -inbound rules be created if the scans are running in applet mode. These scans operate over a default -port range, which cannot be specified via an inbound rule. For more information, see the Microsoft +You need to configure the Windows firewall rules on the Windows server, which require certain +inbound rules if the scans run in applet mode. These scans operate over a default +port range that you can't specify via an inbound rule. For more information, see the Microsoft [Connecting to WMI on a Remote Computer](https://msdn.microsoft.com/en-us/library/windows/desktop/aa389290(v=vs.85).aspx) article. diff --git a/docs/accessanalyzer/11.6/requirements/aws/aws.md b/docs/accessanalyzer/11.6/requirements/aws/aws.md index a0abe6e7a6..2c6fa5b5d8 100644 --- a/docs/accessanalyzer/11.6/requirements/aws/aws.md +++ b/docs/accessanalyzer/11.6/requirements/aws/aws.md @@ -32,10 +32,10 @@ These are dependent upon the size of the target environment: | Disk Space | 30 GB | 30 GB | :::note -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the +If running Sensitive Data Discovery (SDD) scans, you must increase the minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For -example, if the job is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are -required (8x2=16). +example, if you configure the job to scan 8 hosts at a time, the job requires an extra 16 GB of RAM +(8x2=16). ::: @@ -47,10 +47,9 @@ The following is required to run Sensitive Data Discovery scans: :::note The Sensitive Data Discovery Add-on installation package installs the appropriate JDK -(Java) version on the server. The JDK deployed is prepackaged and does not require any -configuration; it has been preconfigured to work with Enterprise Auditor and should never be -customized through Java. It will not conflict with other JDKs or Java Runtimes in the same -environment. +(Java) version on the server. The deployed JDK is prepackaged, requires no configuration, comes +preconfigured to work with Enterprise Auditor, and should never be customized through Java. It +doesn't conflict with other JDKs or Java Runtimes in the same environment. ::: diff --git a/docs/accessanalyzer/11.6/requirements/aws/configurescans.md b/docs/accessanalyzer/11.6/requirements/aws/configurescans.md index 83ebe03894..27531bd5a0 100644 --- a/docs/accessanalyzer/11.6/requirements/aws/configurescans.md +++ b/docs/accessanalyzer/11.6/requirements/aws/configurescans.md @@ -6,31 +6,31 @@ sidebar_position: 20 # Configure AWS for Scans -In order to scan multiple AWS accounts using one account you need to create a role in each target -account, so that It can provide the designated scanning account permissions to scan resources it -controls. This is achieved through the following steps which will need to be completed leveraging a -user with administrative access to each target account: +To scan multiple AWS accounts using one account, create a role in each target +account so it can grant the designated scanning account permission to scan the resources it +controls. Complete the following steps using a user with administrative access to each target +account: -**Step 1 –** Create a Managed Policy in each target account that will be used to allow access to -account (S3, Org and IAM). +**Step 1 –** Create a Managed Policy in each target account to allow access to +account (S3, Org, and IAM). -**Step 2 –** Create a Role in each target account that will be used to allow access to listing IAM +**Step 2 –** Create a Role in each target account to allow access to listing IAM users. -**Step 3 –** Create a Managed Policy in the designated scanning account that will be used to allow +**Step 3 –** Create a Managed Policy in the designated scanning account to allow the service account to assume the configured role in each target account. -**Step 4 –** Add Role to Enterprise Auditor. The Role created in the scanning account will need to -be added to the **1-AWS_OrgScan**, **2-AWS_S3Scan**, and **3-AWS_IAMScan** job query configurations. +**Step 4 –** Add Role to Enterprise Auditor. Add the Role created in the scanning account +to the **1-AWS_OrgScan**, **2-AWS_S3Scan**, and **3-AWS_IAMScan** job query configurations. See the [AWS: Login Roles](/docs/accessanalyzer/11.6/admin/datacollector/aws/loginroles.md) topic for additional information. -Once these steps are completed, the role must be added to the AWS queries within Enterprise Auditor. +After you complete these steps, add the role to the AWS queries within Enterprise Auditor. ## Create a Managed Policy in Each Target Account -The following steps will need to be completed in each target account. +Complete the following steps in each target account. **Step 1 –** Sign into the Identity and Access Management Console (IAM) as an administrator of the Trusting account. @@ -87,7 +87,7 @@ and click **Create policy**. **Step 7 –** Click **Create Policy**. :::note -If the designated scanning account is not in Root (Master Account), create a second policy +If the designated scanning account isn't in Root (Master Account), create a second policy in the Master Account with the following JSON definition: ::: @@ -110,12 +110,11 @@ in the Master Account with the following JSON definition: } ``` -The next step is to create a role in each target account that will be used to allow access to -listing IAM users. +Next, create a role in each target account to allow access to listing IAM users. ## Create a Role in Each Target Account -The following steps will need to be completed in each target account. For this, you will need the +Complete the following steps in each target account. For this, you will need the Account ID of the designating scanning account. :::note @@ -134,7 +133,7 @@ target account. ![Create role page Another AWS account option](/images/accessanalyzer/11.6/requirements/target/config/createrole.webp) **Step 3 –** Select the **Another AWS Account** option and add the Account ID of the scanning -account that will be leveraged within Enterprise Auditor. +account that Enterprise Auditor will use. **Step 4 –** Click **Next: Permissions**. @@ -152,12 +151,12 @@ account that will be leveraged within Enterprise Auditor. **Step 9 –** Click **Create Role**. -The next step is to create a Managed Policy in the designated scanning account that will be used to -allow the service account to assume the configured role in each target account. +Next, create a Managed Policy in the designated scanning account to allow the service account to +assume the configured role in each target account. ## Configure the Scanning Account -Create a Managed Policy in the scanning account that will be used to allow the user to assume the +Create a Managed Policy in the scanning account to allow the user to assume the roles configured in each target account. **Step 1 –** Sign into the Identity and Access Management Console (IAM) as an administrator of the @@ -199,7 +198,7 @@ scanning account. :::note Replace `ROLENAME` with the name of the role that was created. If the `ROLENAME` is -different in each account, then a policy will need to be created for each distinct role name. +different in each account, then create a policy for each distinct role name. ::: @@ -217,8 +216,8 @@ different in each account, then a policy will need to be created for each distin ![Security credentials tab](/images/accessanalyzer/11.6/requirements/target/config/securitycredentials.webp) -**Step 10 –** In the Security credentials tab, click **Create access key**. Make sure to note the -Access key ID and Secret access key which need to be input into Enterprise Auditor. +**Step 10 –** In the Security credentials tab, click **Create access key**, and note the +Access key ID and Secret access key. You'll need to enter them into Enterprise Auditor. You can now create the Connection Profile for the AWS Solution. See the [Amazon Web Services for User Credentials](/docs/accessanalyzer/11.6/admin/settings/connection/create/aws.md) diff --git a/docs/accessanalyzer/11.6/requirements/aws/target.md b/docs/accessanalyzer/11.6/requirements/aws/target.md index d4b6da5a76..0baba4f98a 100644 --- a/docs/accessanalyzer/11.6/requirements/aws/target.md +++ b/docs/accessanalyzer/11.6/requirements/aws/target.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Target Amazon Web Service Requirements, Permissions, and Ports -The Enterprise Auditor for AWS Solution provides the ability to audit Amazon Web Services (AWS) to +The Enterprise Auditor for AWS Solution lets you audit Amazon Web Services (AWS) to collect IAM users, groups, roles, and policies, as well as S3 permissions, content, and sensitive data from target AWS accounts. It scans: @@ -24,11 +24,11 @@ This solution employs the following data collector to scan the target environmen The permissions required to scan an AWS account are based on the type of information being collected: -- To collect details about the AWS Organization, the following permission is required: +- To collect details about the AWS Organization, you need the following permission: - organizations:DescribeOrganization -- To collect details regarding IAM, the following permissions are required: +- To collect details regarding IAM, you need the following permissions: - iam:GenerateCredentialReport - iam:GenerateServiceLastAccessedDetails @@ -37,7 +37,7 @@ collected: - iam:Simulate\* - sts:GetAccessKeyInfo -- To collect details related to S3 buckets and objects, the following permissions are required: +- To collect details related to S3 buckets and objects, you need the following permissions: - s3:Describe\* - s3:Get\* diff --git a/docs/accessanalyzer/11.6/requirements/box/target.md b/docs/accessanalyzer/11.6/requirements/box/target.md index a336f4071b..04bc1f486f 100644 --- a/docs/accessanalyzer/11.6/requirements/box/target.md +++ b/docs/accessanalyzer/11.6/requirements/box/target.md @@ -42,7 +42,7 @@ This solution employs the following data collector to scan the target environmen **For Box Data Collection** Box scans require the Enterprise Admin or Co-Admin account credentials to generate an authorization -code. The following can be used as a least privilege model: +code. You can use the following as a least privilege model: - Enterprise Admin account - Co-Admin account with the permission to **Run new reports and access existing reports** enabled diff --git a/docs/accessanalyzer/11.6/requirements/databases/databases.md b/docs/accessanalyzer/11.6/requirements/databases/databases.md index cb9290680d..aa654780ea 100644 --- a/docs/accessanalyzer/11.6/requirements/databases/databases.md +++ b/docs/accessanalyzer/11.6/requirements/databases/databases.md @@ -11,8 +11,8 @@ Server, and Access Information Center. See the [Requirements](/docs/accessanalyzer/11.6/requirements/overview.md) topic for the core requirements. -In addition to these, integration with either the Netwrix Activity Monitor is required for event -activity data to be scanned. See the +In addition to these, you need integration with the Netwrix Activity Monitor to scan event +activity data. See the [Netwrix Activity Monitor Documentation](https://helpcenter.netwrix.com/category/activitymonitor) for installation requirements and information on collecting activity data. @@ -43,10 +43,10 @@ These are dependent upon the size of the target environment: | Disk Space | 460 GB | 280 GB | 160 GB | 80 GB | :::note -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the -minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host.For -example, if the job is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are -required (8x2=16). +If running Sensitive Data Discovery (SDD) scans, you must increase the +minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For +example, if you configure the job to scan 8 hosts at a time, the job requires an extra 16 GB of RAM +(8x2=16). ::: @@ -74,10 +74,9 @@ The following is required to run Sensitive Data Discovery scans: :::note The Sensitive Data Discovery Add-on installation package installs the appropriate JDK -(Java) version on the server. The JDK deployed is prepackaged and does not require any -configuration; it has been preconfigured to work with Enterprise Auditor and should never be -customized through Java. It will not conflict with other JDKs or Java Runtimes in the same -environment. +(Java) version on the server. The deployed JDK is prepackaged, requires no configuration, comes +preconfigured to work with Enterprise Auditor, and should never be customized through Java. It +doesn't conflict with other JDKs or Java Runtimes in the same environment. ::: diff --git a/docs/accessanalyzer/11.6/requirements/databases/db2.md b/docs/accessanalyzer/11.6/requirements/databases/db2.md index 4451fd6807..a40216996b 100644 --- a/docs/accessanalyzer/11.6/requirements/databases/db2.md +++ b/docs/accessanalyzer/11.6/requirements/databases/db2.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Target Db2 Requirements, Permissions, and Ports -The Enterprise Auditor for Databases Solution provides the ability to audit and monitor Db2 database +The Enterprise Auditor for Databases Solution lets you audit and monitor Db2 database environments to collect permissions and sensitive data. It scans: - DB2LUW 11+ @@ -25,7 +25,7 @@ addition, the following clients and drivers must be installed: - IBM .NET Driver NuGet :::note -All necessary clients and drivers can be found on IBM Support's +You can find all necessary clients and drivers on IBM Support's [Download initial version 11.5 clients and drivers](https://www.ibm.com/support/pages/download-initial-version-115-clients-and-drivers) page. From the list of available packages, select the IBM Data Server Client, which is the all-in-one client package. This package includes all of the client tools and available libraries, as diff --git a/docs/accessanalyzer/11.6/requirements/databases/mongodb.md b/docs/accessanalyzer/11.6/requirements/databases/mongodb.md index 4bb081559e..a3393de7d5 100644 --- a/docs/accessanalyzer/11.6/requirements/databases/mongodb.md +++ b/docs/accessanalyzer/11.6/requirements/databases/mongodb.md @@ -6,7 +6,7 @@ sidebar_position: 20 # Target MongoDB Requirements, Permissions, and Ports -The Enterprise Auditor for Databases Solution provides the ability to audit and monitor MongoDB +The Enterprise Auditor for Databases Solution lets you audit and monitor MongoDB database environments to collect permissions and sensitive data. It scans: - MongoDB 5.0 diff --git a/docs/accessanalyzer/11.6/requirements/databases/mysql.md b/docs/accessanalyzer/11.6/requirements/databases/mysql.md index 6756c54a8d..dbd4dbb1b0 100644 --- a/docs/accessanalyzer/11.6/requirements/databases/mysql.md +++ b/docs/accessanalyzer/11.6/requirements/databases/mysql.md @@ -6,7 +6,7 @@ sidebar_position: 30 # Target MySQL Requirements, Permissions, and Ports -The Enterprise Auditor for Databases Solution provides the ability to audit and monitor MySQL +The Enterprise Auditor for Databases Solution lets you audit and monitor MySQL database environments to collect permissions and sensitive data. It scans: - MySQL 5.x diff --git a/docs/accessanalyzer/11.6/requirements/databases/oracle/leastprivilege.md b/docs/accessanalyzer/11.6/requirements/databases/oracle/leastprivilege.md index 6d5e6c0e0d..be6686aafc 100644 --- a/docs/accessanalyzer/11.6/requirements/databases/oracle/leastprivilege.md +++ b/docs/accessanalyzer/11.6/requirements/databases/oracle/leastprivilege.md @@ -6,9 +6,9 @@ sidebar_position: 10 # Oracle Target Least Privilege Model -We recommend using an account DBA privilege to run Enterprise Auditor against an Oracle database. -However, if that is not acceptable all the privileges that are required to configure and run the -solution are below and can be used to implement the least privileges necessary. +Netwrix recommends using an account with DBA privilege to run Enterprise Auditor against an Oracle +database. However, if that isn't acceptable, the following privileges are required to configure and +run the solution and implement the least privileges necessary. ## Create Session Privilege @@ -21,7 +21,7 @@ GRANT CREATE SESSION TO %USERNAME%;          ``` :::note -The above command will grant the privilege only in the current container. To follow the +This command grants the privilege only in the current container. To follow the least privilege model, only grant the privilege on the containers (or pluggable databases) that you will be scanning with Enterprise Auditor. ::: @@ -45,8 +45,8 @@ topic for additional information. This Job uses Nmap to locate listening Oracle ports on servers by scanning for ports using the service Oracle TNS Listener or optionally using specified ports, such as 1521. The Nmap utility can -be downloaded from [nmap.org](http://www.nmap.org/). To run this job, the user needs to have a -permission to execute any PowerShell script on the local host if the host is running the Microsoft +be downloaded from [nmap.org](http://www.nmap.org/). To run this job, the user needs permission to +execute any PowerShell script on the local host if the host is running the Microsoft Windows operating system. In addition, on the Windows host, PowerShell execution policy needs to be sent as well. For example, to set the execution policy to `Unrestricted`, run the following command on the PowerShell command line: @@ -55,12 +55,12 @@ on the PowerShell command line: Set-ExecutionPolicy -ExecutionPolicy Unrestricted           ``` -In case of Linux and UNIX hosts, the `plink` command needs to be executed on the Enterprise Auditor +In case of Linux and UNIX hosts, you must execute the `plink` command on the Enterprise Auditor Console server to update the local file with the SSH keys. :::note -The plink utility in the Enterprise Auditor installation directory has to be used. A -version of plink gets installed with the Nmap utility. +You must use the plink utility in the Enterprise Auditor installation directory. The +Nmap utility installs a version of plink. ::: @@ -77,11 +77,11 @@ C:\Program Files (x86)\Stealthbits\StealthAUDIT\plink   -store_new_k ## Oracle SID Discovery This Job collects the Oracle SID from discovered Oracle servers and uses WMI or SSH to collect -running Oracle processes from the Oracle servers. The process is used to determine the name of the +running Oracle processes from the Oracle servers. It uses this process to determine the name of the Oracle SID. When multiple Oracle instances are running on a server, each SID will have its own entry in this table. -This Job requires local administrator rights on the target hosts in order to read the running +This Job requires local administrator rights on the target hosts to read the running processes using either WMI or SSH. ## Oracle Instance Discovery @@ -117,12 +117,12 @@ ALTER USER %USERNAME% SET CONTAINER_DATA=ALL CONTAINER = CURRENT; ## Oracle Permission Auditing -The Oracle Permissions Scan job is responsible for collecting all permissions from all licensed +The Oracle Permissions Scan job collects all permissions from all licensed database types for all target instances. ### Oracle Database 19c Series Permissions -In order to collect permissions from Oracle Database 19c series, the user credential requires at +to collect permissions from Oracle Database 19c series, the user credential requires at least the following `SELECT` privilege on the targeted database for the following views and tables: - CDB_COL_PRIVS view @@ -189,7 +189,7 @@ GRANT SELECT ON DBA_TAB_PRIVS TO %USERNAME%; ### Oracle Database 12c Series Permissions -In order to collect permissions from Oracle Database 12c series, the user credential requires at +to collect permissions from Oracle Database 12c series, the user credential requires at least the following `SELECT` privilege on the targeted database for the following views and tables: - CDB_COL_PRIVS view @@ -233,7 +233,7 @@ GRANT SELECT ON SYS.USER$ TO %USERNAME%; ### Oracle Database 11g Series Permissions -In order to collect permissions from Oracle Database 11g series, the user credential requires at +to collect permissions from Oracle Database 11g series, the user credential requires at least the following `SELECT` privileges on the targeted database for the following views and tables: - DBA_COL_PRIVS view @@ -273,7 +273,7 @@ GRANT SELECT ON SYS.USER$ TO %USERNAME%; ## Oracle Sensitive Data Auditing -This job is responsible for identifying sensitive data that has been stored within target database +This job identifies sensitive data stored within target database instances. Before running this scan, ensure that Oracle database statistics are up to date at least for the @@ -286,7 +286,7 @@ EXEC DBMS_STATS.GATHER_TABLE_STATS('%SCHEMA_NAME%', ‘%TABLE_NAME%’); ### Oracle Database 12c Series Sensitive Data -In order to perform a sensitive data scan on Oracle database 12c series, the user credential +to perform a sensitive data scan on Oracle database 12c series, the user credential requires at least the following `SELECT` privileges on the targeted database for the following views: @@ -307,7 +307,7 @@ GRANT SELECT ON CDB_OBJECTS TO %USERNAME%; ### Oracle Database 11g Series Sensitive Data -In order to perform a sensitive data scan on Oracle database 11g series, the user credential +to perform a sensitive data scan on Oracle database 11g series, the user credential requires at least the following `SELECT` privileges on the targeted database for the following views: @@ -324,9 +324,12 @@ GRANT SELECT ON DBA_TAB_COLS TO %USERNAME%; GRANT SELECT ON DBA_OBJECTS TO %USERNAME%; ``` -Please note that the `SELECT` privilege needs to be granted individually on all sensitive data -tables to be targeted (more secure). To accomplish it, run the following command for each targeted -sensitive data table: +:::note +The `SELECT` privilege needs to be granted individually on all sensitive data tables to be +targeted (more secure). +::: + +To accomplish it, run the following command for each targeted sensitive data table: ``` GRANT SELECT ON %YOUR_SENSITIVE_DATA_TABLE% TO %USERNAME%; @@ -341,12 +344,12 @@ GRANT SELECT ANY TABLE TO %USERNAME%; ## Oracle Activity Auditing -This job is responsible for collecting audit data from configured database server audits on target +This job collects audit data from configured database server audits on target endpoints. ### Oracle Database 12c Series Activity Data -In order to perform an activity data scan on Oracle database 12c series, the user credential +to perform an activity data scan on Oracle database 12c series, the user credential requires at least the following `SELECT` privileges on the targeted database for the following views: @@ -363,7 +366,7 @@ GRANT SELECT ON CDB_COMMON_AUDIT_TRAIL TO %USERNAME%; GRANT SELECT ON UNIFIED_AUDIT_TRAIL TO %USERNAME%; ``` -If the audit trail mode is `QUEUED`, then audit records are not written to disk until the in-memory +If the audit trail mode is `QUEUED`, then audit records aren't written to disk until the in-memory queues are full. The following procedure explicitly flushes the queues to disk, so that the audit trail records are viewable in the `UNIFIED_AUDIT_TRAIL` view: @@ -373,7 +376,7 @@ EXEC SYS.DBMS_AUDIT_MGMT.FLUSH_UNIFIED_AUDIT_TRAIL; ### Oracle Database 11g Series Activity Data -In order to perform an activity data scan on Oracle database 11g series, the user credential +to perform an activity data scan on Oracle database 11g series, the user credential required at least the following `SELECT` privileges on the targeted database for the following views: @@ -390,7 +393,7 @@ GRANT SELECT ON DBA_COMMON_AUDIT_TRAIL TO %USERNAME%; ## Oracle Users with Default Passwords Job -The 4-Oracle_DefaultPasswordUsers job is responsible for collecting usernames of users whose +The 4-Oracle_DefaultPasswordUsers job collects usernames of users whose passwords have not been updated since the database creation. The user needs to have a `SELECT` privilege on `CDB_USERS_WITH_DEFPWD` table for Oracle container diff --git a/docs/accessanalyzer/11.6/requirements/databases/oracle/oracle.md b/docs/accessanalyzer/11.6/requirements/databases/oracle/oracle.md index 8edd619d92..0163215e87 100644 --- a/docs/accessanalyzer/11.6/requirements/databases/oracle/oracle.md +++ b/docs/accessanalyzer/11.6/requirements/databases/oracle/oracle.md @@ -6,7 +6,7 @@ sidebar_position: 40 # Target Oracle Requirements, Permissions, and Ports -The Enterprise Auditor for Databases Solution provides the ability to audit and monitor Oracle +The Enterprise Auditor for Databases Solution lets you audit and monitor Oracle database environments to collect permissions, sensitive data, and activity events. It scans: - Oracle Database 12c diff --git a/docs/accessanalyzer/11.6/requirements/databases/postgresql.md b/docs/accessanalyzer/11.6/requirements/databases/postgresql.md index eb0efa22a0..37854a4d62 100644 --- a/docs/accessanalyzer/11.6/requirements/databases/postgresql.md +++ b/docs/accessanalyzer/11.6/requirements/databases/postgresql.md @@ -6,7 +6,7 @@ sidebar_position: 50 # Target PostgreSQL Requirements, Permissions, and Ports -The Enterprise Auditor for Databases Solution provides the ability to audit and monitor PostgreSQL +The Enterprise Auditor for Databases Solution lets you audit and monitor PostgreSQL database environments to collect permissions and sensitive data. It scans: - Open Source PostgreSQL 9x through 12x diff --git a/docs/accessanalyzer/11.6/requirements/databases/redshift.md b/docs/accessanalyzer/11.6/requirements/databases/redshift.md index 7695bb3084..6dd930709d 100644 --- a/docs/accessanalyzer/11.6/requirements/databases/redshift.md +++ b/docs/accessanalyzer/11.6/requirements/databases/redshift.md @@ -6,7 +6,7 @@ sidebar_position: 60 # Target Redshift Requirements, Permissions, and Ports -The Enterprise Auditor for Databases Solution provides the ability to audit and monitor Redshift +The Enterprise Auditor for Databases Solution lets you audit and monitor Redshift database environments to collect permissions and sensitive data. It scans: - Amazon AWS Redshift diff --git a/docs/accessanalyzer/11.6/requirements/databases/sql/azuresql.md b/docs/accessanalyzer/11.6/requirements/databases/sql/azuresql.md index 802afb4d1e..04fb7d223a 100644 --- a/docs/accessanalyzer/11.6/requirements/databases/sql/azuresql.md +++ b/docs/accessanalyzer/11.6/requirements/databases/sql/azuresql.md @@ -7,15 +7,15 @@ sidebar_position: 10 # AzureSQL Target Least Privilege Model To access the AzureSQL database, users require the Control permission for the target database. Users -with the Control Database permission have access to perform activity scans due to the function -leveraged by AzureSQL to return the required audit logs. See the +with the Control Database permission can perform activity scans due to the function +AzureSQL uses to return the required audit logs. See the [Auditing for Azure SQL Database and Azure Synapse Analytics](https://docs.microsoft.com/en-us/azure/azure-sql/database/auditing-overview?view=azuresql) Microsoft Knowledge Base article for additional information. :::info -It is recommended to create a new user when leveraging a least privilege access -model to access the AzureSQL database because the user must exist in the master database and all -target database(s). A least privilege access model is one that uses the bare minimum privileges +Netwrix recommends creating a new user when using a least privilege access +model to access the AzureSQL database, because the user must exist in the master database and all +target databases. A least privilege access model uses the bare minimum privileges required to carry out collections for the AzureSQL data collector. ::: @@ -24,14 +24,14 @@ The following role and permission are required for the Least Privilege Model: - db_datareader role - View Database Performance State permission -- Control permission on target database(s) +- Control permission on target databases :::note - Control permission must be granted on any database you wish to collect data for. + You must grant Control permission on any database you want to collect data for. ::: -Follow the steps to configure the least privilege access model for AzureSQL collections. +Configure the least privilege access model for AzureSQL collections. **Step 1 –** To login with the user, run the following script against the master database: @@ -59,4 +59,4 @@ script: `GRANT CONTROL ON DATABASE` -The user is granted Control permission based on the least privilege access model. +These steps grant the user Control permission based on the least privilege access model. diff --git a/docs/accessanalyzer/11.6/requirements/databases/sql/azuresqlaccess.md b/docs/accessanalyzer/11.6/requirements/databases/sql/azuresqlaccess.md index ae5a6b8c82..938d94a34c 100644 --- a/docs/accessanalyzer/11.6/requirements/databases/sql/azuresqlaccess.md +++ b/docs/accessanalyzer/11.6/requirements/databases/sql/azuresqlaccess.md @@ -12,7 +12,7 @@ Azure SQL Auditing supports three different audit log destinations. At present E only supports storage as the audit log destination. This document describes the necessary permissions required to configure the Enterprise Auditor Azure SQL Job Group. -Enterprise Auditorfor Azure SQL enables users to create custom roles which allow for differential +With Enterprise Auditor for Azure SQL, you can create custom roles that allow for differential access to Enterprise Auditor. Within Enterprise Auditor for Azure SQL, roles are created specifically to target Azure SQL @@ -32,7 +32,7 @@ This will enable Enterprise Auditor to discover all the SQL databases present in ## Create a StealthAUDIT Custom Role -Follow the steps below to create an Azure SQL custom role at the subscription level. +Follow these steps to create an Azure SQL custom role at the subscription level. ![Azure Portal - Azure Services](/images/accessanalyzer/11.6/requirements/target/config/azuresqlperm_customrolecreation_1.webp) @@ -47,7 +47,7 @@ subscriptions in the left-hand menu. **Step 3 –** Click **Add** > Add **Custom Role**. **Step 4 –** Create a JSON file using the subscription ID provided by Microsoft Azure (see the -example below) and save it to a local directory. +following example) and save it to a local directory. ```json { @@ -167,17 +167,16 @@ example below) and save it to a local directory. Once that file is chosen, the Review + Create button should be enabled. Click **Review + Create** to create the role or click **Next** to review and edit the permissions. -Once the JSON file is opened, the Custom Role Name and Description boxes will be populated -automatically. The name and description of the custom role can be customized if required in this -step. +After the JSON file is opened, Azure automatically populates the Custom Role Name and Description +boxes. You can customize the name and description of the custom role in this step, if required. ![Azure SQL Configuration - Create a Cusotm Role window](/images/accessanalyzer/11.6/requirements/target/config/azuresqlperm_customrolecreation_4.webp) **Step 6 –** Click Create. This action will save and finalize a custom role entitled Enterprise Auditor Azure SQL Role. -**Step 7 –** Click OK on the final screen to complete the custom role creation process. The custom -role can now be used to register the Enterprise Auditor application within the Azure portal. +**Step 7 –** Click OK on the final screen to complete the custom role creation process. You can now +use the custom role to register the Enterprise Auditor application within the Azure portal. :::note Depending upon the number of resources in the Azure tenancy, it might take some time for @@ -187,7 +186,7 @@ the role to be made available to the resources. ## Register an Azure SQL Application -Follow the steps below to create an Azure SQL Application Registration in the Azure portal. +Follow these steps to create an Azure SQL Application Registration in the Azure portal. **Step 1 –** In the Azure portal under Azure Services, click the **App Registration** icon. @@ -200,8 +199,8 @@ Follow the steps below to create an Azure SQL Application Registration in the A **Step 3 –** Enter a **Name** for the application and select an appropriate option from the Supported account types options. -**Step 4 –** Click **Register** at the bottom of the page when finished. Once the application has -been registered, the App registration overview blade will appear. Take note of the _Application +**Step 4 –** Click **Register** at the bottom of the page when finished. After you register the +application, the App registration overview blade appears. Take note of the _Application (client) ID_ on this page. :::note @@ -216,10 +215,10 @@ Enterprise Auditor. secret**. **Step 6 –** Enter a unique identifier in the Description field of the Add a client secret window. -Select a Expiration time frame from the drop down. Click **Add** when finished. +Select a Expiration time frame from the dropdown. Click **Add** when finished. :::tip -Remember, you will have to update the Enterprise Auditor Connection Profile once the expiration +Remember, you will have to update the Enterprise Auditor Connection Profile when the expiration time frame is reached (within 24 months, for example). ::: @@ -236,29 +235,29 @@ profile. ## Add a Role Assignment -Follow the steps below to add a role assignment to the custom role and newly registered Enterprise -Auditor Azure SQL application. +Follow these steps to add a role assignment to the custom role and newly registered Enterprise +Auditor Azure SQL application. **Step 1 –** Navigate to the Subscriptions blade and click the **Access Control (IAM)** option. -Click the **Add** drop down > Click **Add role assignment**. +Click the **Add** dropdown > Click **Add role assignment**. ![Azure SQL - Add a Role Assignment](/images/accessanalyzer/11.6/requirements/target/config/azuresqlperm_customrolecreation_13z.webp) -**Step 2 –** Search for and click the recently created custom role from the Role drop down. See +**Step 2 –** Search for and click the recently created custom role from the Role dropdown. See [Create a StealthAUDIT Custom Role](#create-a-stealthaudit-custom-role) for steps required to create a custom role in the Azure portal. **Step 3 –** Search for and select the recently registered Azure SQL application from the Select -drop down. See [Register an Azure SQL Application](#register-an-azure-sqlapplication) for steps +dropdown. See [Register an Azure SQL Application](#register-an-azure-sqlapplication) for steps required to register an Azure SQL application in the Azure portal. The registered application will be visible in the Selected members window. Click **Save** when finished. ![Azure SQL - Add a role assignment window](/images/accessanalyzer/11.6/requirements/target/config/azuresqlperm_customrolecreation_14z.webp) -**Step 4 –** Search for and select the SQL Server Contributor role in the Role drop down. +**Step 4 –** Search for and select the SQL Server Contributor role in the Role dropdown. **Step 5 –** Search for and select the recently registered Azure SQL application from the Select -drop down. See [Register an Azure SQL Application](#register-an-azure-sqlapplication) for steps +dropdown. See [Register an Azure SQL Application](#register-an-azure-sqlapplication) for steps required to register an Azure SQL application in the Azure portal. The registered application will be visible in the Selected members window. Click **Save** when finished. @@ -267,7 +266,7 @@ be visible in the Selected members window. Click **Save** when finished. **Step 6 –** Navigate to the **Subscriptions** blade. Click **Access Control (IAM)**. **Step 7 –** Click the **Check access** menu tab Search for and select the recently registered Azure -SQL application from the drop down. See +SQL application from the dropdown. See [Register an Azure SQL Application](#register-an-azure-sqlapplication) for steps required to register an Azure SQL application in the Azure portal. A preview window will appear on the right-hand side of the window. diff --git a/docs/accessanalyzer/11.6/requirements/databases/sql/sql.md b/docs/accessanalyzer/11.6/requirements/databases/sql/sql.md index cef509e708..1092a69d52 100644 --- a/docs/accessanalyzer/11.6/requirements/databases/sql/sql.md +++ b/docs/accessanalyzer/11.6/requirements/databases/sql/sql.md @@ -6,7 +6,7 @@ sidebar_position: 70 # Target SQL Server Requirements, Permissions, and Ports -The Enterprise Auditor for Databases Solution provides the ability to audit and monitor SQL Server +The Enterprise Auditor for Databases Solution lets you audit and monitor SQL Server database environments to collect permissions, sensitive data, and activity events. It scans: - Azure SQL @@ -80,7 +80,7 @@ This solution employs the following data collector to scan the target environmen - Read access to SQL instance - Requires SQL Full-Text and Semantic Extractions for Search feature to be installed on the - target SQL instance(s) when using the **Scan full rows for sensitive data** option on the + target SQL instances when using the **Scan full rows for sensitive data** option on the Options wizard page - Grant Authenticate Server to [DOMAIN\USER] - Grant Connect SQL to [DOMAIN\USER] diff --git a/docs/accessanalyzer/11.6/requirements/dropbox/dropbox.md b/docs/accessanalyzer/11.6/requirements/dropbox/dropbox.md index d384f3117f..6465392b82 100644 --- a/docs/accessanalyzer/11.6/requirements/dropbox/dropbox.md +++ b/docs/accessanalyzer/11.6/requirements/dropbox/dropbox.md @@ -39,7 +39,7 @@ These are dependent upon the size of the target environment: | Disk Space | 30 GB | 30 GB | :::note -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the +If running Sensitive Data Discovery (SDD) scans, you must increase the minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host.For example, if the job is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are required (8x2=16). @@ -54,7 +54,7 @@ The following is required to run Sensitive Data Discovery scans: :::note The Sensitive Data Discovery Add-on installation package installs the appropriate JDK -(Java) version on the server. The JDK deployed is prepackaged and does not require any +(Java) version on the server. The JDK deployed is prepackaged and doesn't require any configuration; it has been preconfigured to work with Enterprise Auditor and should never be customized through Java. It will not conflict with other JDKs or Java Runtimes in the same environment. diff --git a/docs/accessanalyzer/11.6/requirements/dropbox/target.md b/docs/accessanalyzer/11.6/requirements/dropbox/target.md index f6b2f10fe2..7ba362bae3 100644 --- a/docs/accessanalyzer/11.6/requirements/dropbox/target.md +++ b/docs/accessanalyzer/11.6/requirements/dropbox/target.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Target Dropbox Requirements, Permissions, and Ports -The Enterprise Auditor for AWS Solution provides the ability to audit Dropbox. It scans: +The Enterprise Auditor for AWS Solution lets you audit Dropbox. It scans: - Dropbox @@ -20,10 +20,10 @@ This solution employs the following data collector to scan the target environmen - Dropbox Team Administrator -The DropboxAccess Data Collector requires the generation of an access token that is used to -configure the Connection Profile for Dropbox. The access token is generated from within the Dropbox -Access Auditor Data Collector Wizard on the Scan Options page. Once the access token is copied into -a Connection Profile for Dropbox, it will be saved and does not need to be generated again. See the +The DropboxAccess Data Collector requires an access token to configure the Connection Profile for +Dropbox. Generate the access token from within the Dropbox Access Auditor Data Collector Wizard on +the Scan Options page. After you copy the access token into a Connection Profile for Dropbox, it's +saved and you don't need to generate it again. See the [DropboxAccess: Scan Options](/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/scanoptions.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/requirements/entraid/entraid/access.md b/docs/accessanalyzer/11.6/requirements/entraid/entraid/access.md index 0f6d234b09..7e24686647 100644 --- a/docs/accessanalyzer/11.6/requirements/entraid/entraid/access.md +++ b/docs/accessanalyzer/11.6/requirements/entraid/entraid/access.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Microsoft Entra ID Auditing Configuration -The Enterprise Auditor for Entra ID Solution provides the ability to audit Microsoft Entra ID, +The Enterprise Auditor for Entra ID Solution lets you audit Microsoft Entra ID, formerly Azure Active Directory. It scans: - Microsoft Entra ID (formerly Azure AD) @@ -23,19 +23,19 @@ Microsoft Entra ID. **Configuration Settings from the Registered Application** -The following settings are needed from your tenant once you have registered the application: +The following settings are needed from your tenant after you register the application: - Client ID – This is the Application (client) ID for the registered application - Key – This is the Client Secret Value generated when a new secret is created :::warning - It is not possible to retrieve the value after saving the new key. It must be - copied first. + You can't retrieve the value after saving the new key. Copy it + first. ::: :::note -In order to add custom attributes, you will also need to know the Tenant name of the Entra +to add custom attributes, you will also need to know the Tenant name of the Entra ID environment. ::: @@ -67,10 +67,10 @@ The following permissions are required: ## Register a Microsoft Entra ID Application -Follow the steps to register Enterprise Auditor with Microsoft Entra ID. +Register Enterprise Auditor with Microsoft Entra ID. :::note -The steps below are for the Microsoft Entra Admin Center. These steps might vary slightly +The following steps are for the Microsoft Entra Admin Center. These steps might vary slightly if you start from a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: @@ -92,14 +92,14 @@ registrations. **Step 5 –** Click **Register**. The Overview page for the newly registered app opens. Review the newly created registered -application. Now that the application has been registered, permissions need to be granted to it. +application. Now that you've registered the application, you need to grant it permissions. ## Grant Permissions to the Registered Application -Follow the steps to grant permissions to the registered application. +Grant permissions to the registered application. :::note -The steps below are for the Microsoft Entra Admin Center. These steps might vary slightly +The following steps are for the Microsoft Entra Admin Center. These steps might vary slightly if you start from a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: @@ -131,15 +131,15 @@ tab. Select the following permissions: **Step 6 –** Click **Grant Admin Consent for [tenant]**. Then click **Yes** in the confirmation window. -Now that the permissions have been granted to it, the Connection Profile and host settings for -Enterprise Auditor need to be collected. +Now that you've granted the permissions, you need to collect the Connection Profile and host +settings for Enterprise Auditor. ## Identify the Client ID -Follow the steps to find the registered application's Client ID. +Find the registered application's Client ID. :::note -The steps below are for the Microsoft Entra Admin Center. These steps might vary slightly +The following steps are for the Microsoft Entra Admin Center. These steps might vary slightly if you start from a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: @@ -162,18 +162,18 @@ topic for additional information. Next generate the application’s Client Secre ## Generate the Client Secret Key -Follow the steps to find the registered application's Client Secret, create a new key, and save its +Find the registered application's Client Secret, create a new key, and save its value when saving the new key. :::note -The steps below are for the Microsoft Entra Admin Center. These steps might vary slightly +The following steps are for the Microsoft Entra Admin Center. These steps might vary slightly if you start from a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: :::warning -It is not possible to retrieve the value after saving the new key. It must be copied +It isn't possible to retrieve the value after saving the new key. It must be copied first. ::: @@ -200,12 +200,12 @@ list. **Step 5 –** Click **Add** to generate the key. :::warning -If this page is left before the key is copied, then the key is not retrievable, and -this process will have to be repeated. +If you leave this page before copying the key, the key isn't retrievable, and +you'll have to repeat this process. ::: -**Step 6 –** The Client Secret will be displayed in the Value column of the table. You can use the +**Step 6 –** The Value column of the table displays the Client Secret. You can use the Copy to clipboard button to copy the Client Secret. **Step 7 –** Save this value in a text file. @@ -219,10 +219,10 @@ topic for additional information. ## Identify the Tenant Name -Follow the steps to find the Tenant Name where the registered application resides. +Find the Tenant Name where the registered application resides. :::note -The steps below are for the Microsoft Entra Admin Center. These steps might vary slightly +The following steps are for the Microsoft Entra Admin Center. These steps might vary slightly if you start from a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: diff --git a/docs/accessanalyzer/11.6/requirements/entraid/entraid/overview.md b/docs/accessanalyzer/11.6/requirements/entraid/entraid/overview.md index b511d87de8..00dae46617 100644 --- a/docs/accessanalyzer/11.6/requirements/entraid/entraid/overview.md +++ b/docs/accessanalyzer/11.6/requirements/entraid/entraid/overview.md @@ -10,8 +10,8 @@ Netwrix Enterprise Auditor can execute scans on Microsoft Entra ID, formerly Azu ## Auditing Permissions -It is necessary to register Enterprise Auditor as a web application to the targeted Microsoft Entra -ID in order for Enterprise Auditor to scan the environment. This generates the Client ID (App ID) +Register Enterprise Auditor as a web application with the targeted Microsoft Entra +ID so Enterprise Auditor can scan the environment. This generates the Client ID (App ID) and Key (App Key) needed for the Connection Profile credentials and the Custom Attributes Import Wizard page. diff --git a/docs/accessanalyzer/11.6/requirements/exchange/exchange.md b/docs/accessanalyzer/11.6/requirements/exchange/exchange.md index 8e2dce4af6..abbc9ee63a 100644 --- a/docs/accessanalyzer/11.6/requirements/exchange/exchange.md +++ b/docs/accessanalyzer/11.6/requirements/exchange/exchange.md @@ -40,7 +40,7 @@ These are dependent upon the size of the target environment: | Disk Space | 120 GB | 120 GB | :::note -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the +If running Sensitive Data Discovery (SDD) scans, you must increase the minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host.For example, if the job is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are required (8x2=16). @@ -55,7 +55,7 @@ The following is required to run Sensitive Data Discovery scans: :::note The Sensitive Data Discovery Add-on installation package installs the appropriate JDK -(Java) version on the server. The JDK deployed is prepackaged and does not require any +(Java) version on the server. The JDK deployed is prepackaged and doesn't require any configuration; it has been preconfigured to work with Enterprise Auditor and should never be customized through Java. It will not conflict with other JDKs or Java Runtimes in the same environment. @@ -67,7 +67,7 @@ environment. The following are additional requirements for the Enterprise Auditor Console server specific to running the Exchange Solution: -- Outlook should not be installed +- Outlook shouldn't be installed - StealthAUDIT MAPI CDO installed (for MAPI- based data collectors). See the [StealthAUDIT MAPI CDO Installation](/docs/accessanalyzer/11.6/install/stealthauditmapicdoinstallation/stealthaudit_mapi_cdo_installation.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/requirements/exchange/exchangeonline/access.md b/docs/accessanalyzer/11.6/requirements/exchange/exchangeonline/access.md index 568500de4d..bf1348c07d 100644 --- a/docs/accessanalyzer/11.6/requirements/exchange/exchangeonline/access.md +++ b/docs/accessanalyzer/11.6/requirements/exchange/exchangeonline/access.md @@ -6,8 +6,8 @@ sidebar_position: 10 # Exchange Online Auditing Configuration -It is necessary to register Enterprise Auditor as a web application to the targeted Microsoft Entra -ID, formerly Azure Active Directory, in order for Enterprise Auditor to scan the environment. This +Register Enterprise Auditor as a web application with the targeted Microsoft Entra +ID, formerly Azure Active Directory, so Enterprise Auditor can scan the environment. This generates the Client ID (App ID) and self-signed certificate (Certificate Thumbprint) needed for the Connection Profile credentials and/or the Custom Attributes Import Wizard page. See [Microsoft Support](https://docs.microsoft.com/en-us/azure/active-directory/active-directory-reporting-api-prerequisites-azure-portal) @@ -21,7 +21,7 @@ Microsoft Entra ID. **Configuration Settings from the Registered Application** -The following settings are needed from your tenant once you have registered the application: +The following settings are needed from your tenant after you register the application: - Client ID – This is the Application (client) ID for the registered application - Tenant name – This is the primary domain name of the Microsoft Entra tenant @@ -30,9 +30,9 @@ The following settings are needed from your tenant once you have registered the Configure Modern Authentication for Exchange Online using EX_RegisterAzureAppAuth Instant Job -Registering a Microsoft Entra ID application and provisioning it to grant permissions to Exchange -Online can be automated using the EX_RegisterAzureAppAuth job from the Enterprise Auditor Instant -Job Library. The EX_RegisterAzureAppAuth job uses the PowerShell Data Collector to automatically +The EX_RegisterAzureAppAuth job from the Enterprise Auditor Instant Job Library can automate +registering a Microsoft Entra ID application and provisioning it to grant permissions to Exchange +Online. The EX_RegisterAzureAppAuth job uses the PowerShell Data Collector to automatically configure modern authentication for Exchange Online. It requires: - A Connection Profile containing a Microsoft Entra ID Global Admin credential with an Account Type @@ -48,7 +48,7 @@ configure modern authentication for Exchange Online. It requires: - Azure AD PowerShell module installed on targeted hosts :::note - If the module is not already installed, the job will attempt to install it. + If the module isn't already installed, the job will attempt to install it. ::: @@ -107,12 +107,12 @@ The following permissions are required: ## Create Self–Signed Certificate -A self signed certificate needs to be created on the Enterprise Auditor console server. This is used -by Enterprise Auditor to connect to the Microsoft Entra tenant. +You need to create a self-signed certificate on the Enterprise Auditor console server. Enterprise +Auditor uses this certificate to connect to the Microsoft Entra tenant. Follow the steps create the self-signed certificate. -**Step 1 –** To generate a certificate, use the sample PowerShell command below: +**Step 1 –** To generate a certificate, use the following sample PowerShell command: - Change the following parameters in the sample PowerShell command. See the Microsoft [New-SelfSignedCertificate](https://docs.microsoft.com/en-us/powershell/module/pki/new-selfsignedcertificate) @@ -122,9 +122,9 @@ Follow the steps create the self-signed certificate. certificate - Subject – A unique name for the new App (always starts with CN=, to denote a canonical name) - FriendlyName – Same as Subject name minus the canonical name prefix - - NotAfter – A datetime string denoting the certificate's expiration date - in the above sample, - Get-Date.AddYears(11) specifies that the certificate will expire 11 years from the current - datetime + - NotAfter – A datetime string denoting the certificate's expiration date - in the following + sample, Get-Date.AddYears(11) specifies that the certificate will expire 11 years from the + current datetime Example PowerShell: @@ -138,7 +138,7 @@ $certPath variable (see Step 1). :::note The environment variable `SAINSTALLDIR` always points to the base Enterprise Auditor -install directory; simply append the PrivateAssemblies to point to that folder with the following +install directory; append the PrivateAssemblies to point to that folder with the following cmdlet: ::: @@ -168,15 +168,15 @@ Export-PfxCertificate -Cert $cert -FilePath "$($env:SAINSTALLDIR)PrivateAssembli [Export-PfxCertificate](https://docs.microsoft.com/en-us/powershell/module/pki/export-pfxcertificate) article for additional information. -The self signed certificate has been created. The next steps are to create a Microsoft Entra ID +You've created the self-signed certificate. Next, create a Microsoft Entra ID application and then upload this certificate to it. ## Register a Microsoft Entra ID Application -Follow the steps to register Enterprise Auditor with Microsoft Entra ID. +Register Enterprise Auditor with Microsoft Entra ID. :::note -The steps below are for the Microsoft Entra Admin Center. These steps might vary slightly +The following steps are for the Microsoft Entra Admin Center. These steps might vary slightly if you start from a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: @@ -198,14 +198,14 @@ registrations. **Step 5 –** Click **Register**. The Overview page for the newly registered app opens. Review the newly created registered -application. Now that the application has been registered, permissions need to be granted to it. +application. Now that you've registered the application, you need to grant it permissions. ## Upload Self-Signed Certificate Follow the steps upload your self-signed certificate. :::note -The steps below are for the Microsoft Entra Admin Center. These steps might vary slightly +The following steps are for the Microsoft Entra Admin Center. These steps might vary slightly if you start from a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: @@ -233,10 +233,10 @@ topic for additional information. ## Grant Permissions to the Registered Application -Follow the steps to grant permissions to the registered application. +Grant permissions to the registered application. :::note -The steps below are for the Microsoft Entra Admin Center. These steps might vary slightly +The following steps are for the Microsoft Entra Admin Center. These steps might vary slightly if you start from a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: @@ -265,15 +265,15 @@ uses tab to find and select Office 365 Exchange Online. Select the following per **Step 6 –** Click **Grant Admin Consent for [tenant]**. Then click **Yes** in the confirmation window. -Now that the permissions have been granted to it, the Connection Profile and host settings for -Enterprise Auditor need to be collected. +Now that you've granted the permissions, you need to collect the Connection Profile and host +settings for Enterprise Auditor. ## Identify the Tenant's Name -Follow the steps to find the Tenant Name where the registered application resides. +Find the Tenant Name where the registered application resides. :::note -The steps below are for the Microsoft Entra Admin Center. These steps might vary slightly +The following steps are for the Microsoft Entra Admin Center. These steps might vary slightly if you start from a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: @@ -294,10 +294,10 @@ topic for additional information. Next identify the application’s Client ID. ## Identify the Client ID -Follow the steps to find the registered application's Client ID. +Find the registered application's Client ID. :::note -The steps below are for the Microsoft Entra Admin Center. These steps might vary slightly +The following steps are for the Microsoft Entra Admin Center. These steps might vary slightly if you start from a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: diff --git a/docs/accessanalyzer/11.6/requirements/exchange/exchangeonline/exchangeonline.md b/docs/accessanalyzer/11.6/requirements/exchange/exchangeonline/exchangeonline.md index d3debcdc99..40537e5391 100644 --- a/docs/accessanalyzer/11.6/requirements/exchange/exchangeonline/exchangeonline.md +++ b/docs/accessanalyzer/11.6/requirements/exchange/exchangeonline/exchangeonline.md @@ -6,7 +6,7 @@ sidebar_position: 30 # Target Exchange Online Requirements, Permissions, and Ports -The Enterprise Auditor for Exchange Solution provides the ability to audit Exchange Online. It +The Enterprise Auditor for Exchange Solution lets you audit Exchange Online. It scans: - Exchange Online (Limited) diff --git a/docs/accessanalyzer/11.6/requirements/exchange/support/mailflow.md b/docs/accessanalyzer/11.6/requirements/exchange/support/mailflow.md index a0a46ca194..2dcc1154a6 100644 --- a/docs/accessanalyzer/11.6/requirements/exchange/support/mailflow.md +++ b/docs/accessanalyzer/11.6/requirements/exchange/support/mailflow.md @@ -8,7 +8,7 @@ sidebar_position: 10 The ExchangeMetrics Data Collector collects Mail-Flow metrics from the Exchange Message Tracking Logs on the Exchange servers. Some examples of this include server volume and message size -statistics. This data collector utilizes an applet to process and collect summarized metrics from +statistics. This data collector uses an applet to process and collect summarized metrics from the Message Tracking Log. 1. HUB Metrics Job Group Requirement @@ -17,7 +17,7 @@ In addition to the permissions required by the ExchangeMetrics Data Collector, t Profile assigned to the 1. HUB Metrics Job Group requires the following permission and User Rights (based on default settings): -- Member of the local Administrator group on the targeted Exchange server(s) where the Hub Transport +- Member of the local Administrator group on the targeted Exchange servers where the Hub Transport service is running - Log on as a Service Group Policy: @@ -30,7 +30,7 @@ Profile assigned to the 1. HUB Metrics Job Group requires the following permissi This is required because the ExchangeMetrics Data Collector is an applet-based data collector. It requires -- Member of the local Administrator group on the targeted Exchange server(s) +- Member of the local Administrator group on the targeted Exchange servers This grants access to the Message Tracking Logs and the ability to create the `SA_ExchangeMetricsData` folder, which will contain the applet files and the processed message @@ -39,7 +39,7 @@ tracking log files stored inside a SQLite database for each day. For example: \\ExchangeServerName\c$\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\MessageTracking -If there have been additional security or permission modifications on the server(s), the following +If there have been additional security or permission modifications on the servers, the following rights and policies may need to be enabled on the targeted host: - Ensure the Administrator group has been granted Full Control over Message Tracking Log Directories diff --git a/docs/accessanalyzer/11.6/requirements/exchange/support/mapi.md b/docs/accessanalyzer/11.6/requirements/exchange/support/mapi.md index cfef76637d..c367cb88b9 100644 --- a/docs/accessanalyzer/11.6/requirements/exchange/support/mapi.md +++ b/docs/accessanalyzer/11.6/requirements/exchange/support/mapi.md @@ -10,7 +10,7 @@ The Exchange2K, ExchangeMailbox, and ExchangePublicFolder data collectors have o requirements. These data collectors supports Exchange 2010 through Exchange 2013. Since this data collectors are -MAPI-based, they do not support Exchange Online, Exchange 2019, nor Exchange 2016. +MAPI-based, they don't support Exchange Online, Exchange 2019, nor Exchange 2016. All MAPI-based data collectors have the following prerequisites: diff --git a/docs/accessanalyzer/11.6/requirements/exchange/support/powershell.md b/docs/accessanalyzer/11.6/requirements/exchange/support/powershell.md index b4f194b3fb..6717e95a7c 100644 --- a/docs/accessanalyzer/11.6/requirements/exchange/support/powershell.md +++ b/docs/accessanalyzer/11.6/requirements/exchange/support/powershell.md @@ -6,8 +6,8 @@ sidebar_position: 30 # Exchange PowerShell Permissions -The ExchangePS Data Collector utilizes PowerShell to collect various information from the Exchange -environment. This data collector utilizes Remote PowerShell to collect information about Exchange +The ExchangePS Data Collector uses PowerShell to collect various information from the Exchange +environment. This data collector uses Remote PowerShell to collect information about Exchange Users Configuration, Mailboxes, Public Folders, and Exchange Online Mail-Flow. **Job Group Requirements in Addition to ExchangePS** @@ -48,13 +48,13 @@ assigned to these job groups requires the following permissions: **Remote PowerShell and Windows Authentication Enabled** -The Remote PowerShell and Windows Authentication configurations for Exchanges servers are required -to be enabled on at least one Exchange server running the Client Access Service so that the +You must enable the Remote PowerShell and Windows Authentication configurations for Exchange +servers on at least one Exchange server running the Client Access Service so that the ExchangePS Data Collector can make a remote PowerShell connection and authenticate through Enterprise Auditor. Enterprise Auditor passes credentials saved in the Connection Profile to the data collector so that -it is able to connect to the targeted host. This requires the Exchange server to allow for Windows +it can connect to the targeted host. This requires the Exchange server to allow for Windows Authentication. See the [Enable Remote PowerShell for ExchangePS Data Collector](#enable-remote-powershell-for-exchangeps-data-collector) topic and the @@ -63,19 +63,19 @@ topic for additional information. **View-Only Organization Management Role Group** -This is required so the ExchangePS Data Collector is able to run the various Exchange PowerShell +This is required so the ExchangePS Data Collector can run the various Exchange PowerShell cmdlets. **Public Folder Management** -This permission is only required if utilizing the ExchangePublicFolder Data Collector or +This permission is only required if using the ExchangePublicFolder Data Collector or ExchangeMailbox Data Collector, as well as the PublicFolder or Mailbox Action Modules. This is -required in order to make a connection through the MAPI protocol. The following job group requires +required to make a connection through the MAPI protocol. The following job group requires the Public Folder Management Role Group: - **5. Public Folders > Ownership** -If not running this collection, then this permission is not required. +If not running this collection, then this permission isn't required. **Mailbox Search Role** @@ -94,14 +94,14 @@ topic for additional information. There are five different scoping options within this data collector. Since not all query categories support all scoping options, No Scoping is an option. If there are no scoping options available, -then the data collector should be run against the host specified in the Summary page of the data +run the data collector against the host specified in the Summary page of the data collector wizard. **No Scoping** This option will gather information about the entire Exchange Organization. When using the applet, the data collector will gather information about the Exchange Forest in which the Enterprise Auditor -Console currently resides. For Remote PowerShell, the data collector will gather information about +Console resides. For Remote PowerShell, the data collector will gather information about the Exchange Organization to which the Remote PowerShell connection was made. This refers to the server entered in the Client Access Server (CAS) field of the global configuration from the **Settings** > **Exchange** node or on the Scope Page of the data collector wizard. See the @@ -110,9 +110,9 @@ topic for additional information. **Scope by Database** -This option will gather information about any databases which are chosen. When using the applet, the +This option will gather information about any databases you choose. When using the applet, the data collector will return databases in the Scope by DB page of the data collector wizard for the -Exchange Organization in which the Enterprise Auditor Console currently resides, as well as, only +Exchange Organization in which the Enterprise Auditor Console resides, as well as, only return information about those databases. For Remote PowerShell, the data collector will return databases in the Scope by DB page of the data collector wizard for the Exchange Forest, as well as, only return information about those databases. See the @@ -121,9 +121,9 @@ topic for additional information. **Scope by Mailbox** -This option will gather information about any mailboxes which are chosen. When using the applet, the +This option will gather information about any mailboxes you choose. When using the applet, the data collector will return mailboxes in the Scope by Mailboxes page of the data collector wizard for -the Exchange Forest in which the Enterprise Auditor Console currently resides, as well as, only +the Exchange Forest in which the Enterprise Auditor Console resides, as well as, only return information about those mailboxes. For Remote PowerShell, the data collector will return mailboxes in the Scope by Mailboxes page of the data collector wizard for the Exchange Forest, as well as, only return information about those mailboxes. See the @@ -136,14 +136,14 @@ This option will gather information about objects which reside on the chosen ser this option, the data collector will then use the Host List applied to the job’s **Configure** > **Hosts** node as the servers scoping list. When using the applet, the data collector will deploy a process to the targeted host to run the PowerShell on that server. For Remote PowerShell, the data -collector will deploy no applet and utilize the WinRM protocol to gather information about the +collector will deploy no applet and use the WinRM protocol to gather information about the objects on that server. **Scope by Public Folder** -This option will gather information about any public folders which are chosen. When using the +This option will gather information about any public folders you choose. When using the applet, the data collector will return public folders in the Scope by Public Folders page of the -data collector wizard for the Exchange Forest in which the Enterprise Auditor Console currently +data collector wizard for the Exchange Forest in which the Enterprise Auditor Console resides, as well as, only return information about those public folders. For Remote PowerShell, the data collector will return public folders in the Scope by Public Folders page of the data collector wizard for the Exchange Forest, as well as, only return information about those public folders. See @@ -153,7 +153,7 @@ topic for additional information. ## Enable Remote PowerShell for ExchangePS Data Collector -Follow these steps to enable Remote PowerShell. +Enable Remote PowerShell. **Step 1 –** On the server that Enterprise Auditor will connect with Remote PowerShell, open PowerShell. @@ -166,7 +166,7 @@ Enable-PSRemoting **Step 3 –** When prompted, type `A` and `A` again to enable the appropriate services and protocols. -Remote PowerShell has been enabled. See the Microsoft +You've enabled Remote PowerShell. See the Microsoft [Tip: Enable and Use Remote Commands in Windows PowerShell](https://technet.microsoft.com/en-us/library/ff700227.aspx) article for additional information. @@ -174,9 +174,8 @@ Next, enable Windows Authentication for PowerShell Virtual Directory on the same ## Enable Windows Authentication for PowerShell Virtual Directory -Once Remote PowerShell has been enabled on an Exchange Server in the environment, it is necessary to -also enable Windows Authentication for the PowerShell Virtual Directory on the same Exchange server. -Follow these steps to enable Windows Authentication. +Once you've enabled Remote PowerShell on an Exchange Server in the environment, also enable +Windows Authentication for the PowerShell Virtual Directory on the same Exchange server. **Step 1 –** On the server where Remote PowerShell was enabled, open the Internet Information Services (IIS) Manager. @@ -188,13 +187,13 @@ Services (IIS) Manager. ![IIS Enable Windows Authentication](/images/accessanalyzer/11.6/requirements/solutions/exchange/iismanagerauth.webp) -**Step 3 –** Right-click on **Windows Authentication** and select **Enable**. +**Step 3 –** Right-click **Windows Authentication** and select **Enable**. -Windows Authentication has been enabled for the PowerShell Virtual Directory. +You've enabled Windows Authentication for the PowerShell Virtual Directory. ## Create Custom Application Impersonation Role in Exchange -Follow the steps to create the custom Application Impersonation role. The process is the same for +Create the custom Application Impersonation role. The process is the same for Exchange 2010 Service Pack 1 through Exchange 2019 and Exchange Online. **Step 1 –** Within the Exchange Admin Center, navigate to the permissions section and select admin @@ -214,7 +213,7 @@ roles. **ApplicationImpersonation** role from the available list and click **Add**. Then click **OK** to close the Select a Role window. - Members – Click the + button to open the Select Members window. Select the account from the - available list and click **Add**. Remember, the account needs to be assigned the other permissions + available list and click **Add**. Remember, you need to assign the account the other permissions required for the **EWSMailbox** and/or **EWSPublicFolder** data collectors. Then click **OK** to close the Select Members window. @@ -224,8 +223,8 @@ The new role group appears in the list. ## Enable Exchange Mailbox Access Auditing -The 4. Mailboxes Job Group requires the Exchange Mailbox Access Auditing to be enabled. In order to -collect Mailbox Access Auditing events, it is necessary to enable Exchange Mailbox Access Auditing +The 4. Mailboxes Job Group requires the Exchange Mailbox Access Auditing to be enabled. To +collect Mailbox Access Auditing events, enable Exchange Mailbox Access Auditing for Exchange. See the following Microsoft articles: - Exchange Online – diff --git a/docs/accessanalyzer/11.6/requirements/exchange/support/remoteconnections.md b/docs/accessanalyzer/11.6/requirements/exchange/support/remoteconnections.md index 6d151cf7ee..f603712200 100644 --- a/docs/accessanalyzer/11.6/requirements/exchange/support/remoteconnections.md +++ b/docs/accessanalyzer/11.6/requirements/exchange/support/remoteconnections.md @@ -16,7 +16,7 @@ In addition to the permissions required by the SMARTLog Data Collector, the Conn assigned to the 2. CAS Metrics Job Group requires the following permissions and User Rights (based on default settings): -- Member of the local Administrator group on the targeted Exchange server(s) where the Client Access +- Member of the local Administrator group on the targeted Exchange servers where the Client Access Service is running - Log on as a Service Group Policy: @@ -40,7 +40,7 @@ example: **\\ExchangeServerName\c$\Program Files (x86)\STEALTHbits\StealthAUDIT\LogProcessor** -If there have been additional security or permission modifications on the server(s), the following +If there have been additional security or permission modifications on the servers, the following rights and policies may need to be enabled on the targeted host: - Ensure the Administrator group has been granted Full Control over IIS Log Directories diff --git a/docs/accessanalyzer/11.6/requirements/exchange/support/webservicesapi.md b/docs/accessanalyzer/11.6/requirements/exchange/support/webservicesapi.md index e7d63767fd..e40ef43db1 100644 --- a/docs/accessanalyzer/11.6/requirements/exchange/support/webservicesapi.md +++ b/docs/accessanalyzer/11.6/requirements/exchange/support/webservicesapi.md @@ -6,7 +6,7 @@ sidebar_position: 40 # Exchange Web Services API Permissions -The EWSMailbox and EWSPublicFolder data collectors utilizes Exchange Web Services API to access and +The EWSMailbox and EWSPublicFolder data collectors uses Exchange Web Services API to access and communicate with Exchange. These data collectors collect statistical, content, permission, and sensitive data information from mailboxes and public folders. diff --git a/docs/accessanalyzer/11.6/requirements/exchange/target.md b/docs/accessanalyzer/11.6/requirements/exchange/target.md index 9429da26b4..ff2f75b59b 100644 --- a/docs/accessanalyzer/11.6/requirements/exchange/target.md +++ b/docs/accessanalyzer/11.6/requirements/exchange/target.md @@ -25,16 +25,16 @@ The following are requirements for the Exchange servers to be scanned: - Enable Remote PowerShell on one Client Access Server (CAS) - Enable Windows Authentication for the PowerShell Virtual Directory on the same CAS - .NET Framework 4.5+ installed on all Exchange servers to be targeted -- WINRM Service installed on all Exchange servers to be targeted as a back up in the event of a +- WINRM Service installed on all Exchange servers to be targeted as a backup if there is a remote PowerShell failure - Within the Enterprise Auditor Console, the global **Settings > Exchange** node must be configured :::note For Exchange 2013, 2016, and 2019 – If the global Settings have been configured for - "MAPI over HTTP," then an actual CAS server name was supplied and will be used by the ExchangePS - Data Collector. If the global Settings have been configured for "MAPI over HTTPS," then the - global Settings will have a web address instead of an actual server. Therefore, each ExchangePS - query requires the CAS server to be set as the specific server on the Category page. See the + "MAPI over HTTP," then an actual CAS server name was supplied, and the ExchangePS + Data Collector uses it. If the global Settings have been configured for "MAPI over HTTPS," then the + global Settings will have a web address instead of an actual server. Therefore, for each ExchangePS + query, you must set the CAS server as the specific server on the Category page. See the [ExchangePS Data Collector & Client Access Server](/docs/accessanalyzer/11.6/solutions/exchange/recommended.md) topic for a list of queries for which this would apply. ::: @@ -106,7 +106,7 @@ topic for additional information. **For Exchange Mail Flow with ExchangeMetrics Data Collector** -- Member of the local Administrator group on the targeted Exchange server(s) +- Member of the local Administrator group on the targeted Exchange servers See the [Exchange Mail-Flow Permissions](/docs/accessanalyzer/11.6/requirements/exchange/support/mailflow.md) diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystem.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystem.md index 8669690e0b..096a4b9c86 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystem.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystem.md @@ -27,8 +27,8 @@ The Sensitive Data Discovery Add-On must be installed on the Enterprise Auditor which enables Sensitive Data criteria for scans. :::note -If proxy server scan options are used, it may also be necessary for the Sensitive Data -Discovery Add-On to be installed on those servers as well. +If you use proxy server scan options, you may also need to install the Sensitive Data +Discovery Add-On on those servers as well. ::: @@ -50,26 +50,26 @@ These are dependent upon the size of the target environment: | Cores | 8 CPU | 8 CPU | 8 CPU | 4 CPU | 2 CPU | | Disk Space | 1.5 TB | 770 GB | 470 GB | 270 GB | 130 GB | -The above recommended disk space sizing information is based on the needs of Enterprise Auditor as +This recommended disk space sizing information is based on the needs of Enterprise Auditor as well as the File System solution for running Permission scans with default configuration (500 MB per million files and folders), that means no tag collection, file-level scanning, activity, or sensitive data. -- For tag collection, add 125 MB per million documents to the totals above +- For tag collection, add 125 MB per million documents to those totals - For activity collection, add 250 MB per million files and folders and another 125 MB per million - activity events to the totals above + activity events to those totals - For sensitive data collection, add 500 MB per million files and folders and another 1%-10% of the total size of the documents scanned for sensitive data (depending on targeted document types and - selected criteria) to the totals above + selected criteria) to those totals -For example, in order to scan 200 million files and folders, of which 10 million files will be +For example, to scan 200 million files and folders, of which 10 million files will be scanned for tag collection and sensitive data with a total size of 6 TB, you would need: 160 GB for permission collection + 1.25 GB for tag collection (10x125 MB) + 100 GB for sensitive data collection (200x500 MB) + 600 GB additional for sensitive data collection (10% of 6 TB) = 861.25 GB total disk space. :::note -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the +If running Sensitive Data Discovery (SDD) scans, you must increase the minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. By default, SDD scans are configured to run two concurrent threads. For example, if the job is configured to scan 8 hosts at a time with two concurrent SDD threads, then an extra 32 GB of RAM are @@ -81,7 +81,7 @@ required (8x2x2=32). If Data Activity Tracking for NAS is required or if NetApp Filers running Clustered Data ONTAP are in scope, reducing latency between the scanning server and the target device is highly recommended. -Additional hardware may be required, especially if the target NAS devices are not collocated with +Additional hardware may be required, especially if the target NAS devices aren't collocated with the Enterprise Auditor Console server. **Sensitive Data Discovery Auditing Requirement** @@ -92,7 +92,7 @@ The following is required to run Sensitive Data Discovery scans: :::note The Sensitive Data Discovery Add-on installation package installs the appropriate JDK -(Java) version on the server. The JDK deployed is prepackaged and does not require any +(Java) version on the server. The JDK deployed is prepackaged and doesn't require any configuration; it has been preconfigured to work with Enterprise Auditor and should never be customized through Java. It will not conflict with other JDKs or Java Runtimes in the same environment. @@ -113,7 +113,7 @@ mode, applet mode, or proxy mode with applet: - Administrators These permissions grant the credential the ability to create a high integrity token capable of -leveraging the “Back up files and directories” from where the Enterprise Auditor executable is run. +using the “Back up files and directories” right from where the Enterprise Auditor executable is run. Additionally, the credential must have `WRITE` access to the `…\StealthAUDIT\FSAA` folder in the installation directory. This is required by either the user account running the Enterprise Auditor diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/azureinformationprotection.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/azureinformationprotection.md index 3548687f18..b6ef35c5de 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/azureinformationprotection.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/azureinformationprotection.md @@ -6,7 +6,7 @@ sidebar_position: 10 # **Azure Information Protection Target Requirements** -Microsoft® Azure is a cloud-based computing platform that provides a range of services, such as file storage. Azure uses Azure Information Protection (AIP) labels, a Microsoft tool used to classify and protect stored files. Access Analyzer employs the File System Solution to execute Access Auditing (FSAA) and/or Sensitive Data Discovery Auditing scans in order to find AIP Protection labels and scan protected (i.e. encrypted) files for sensitive data. +Microsoft® Azure is a cloud-based computing platform that provides a range of services, such as file storage. Azure uses Azure Information Protection (AIP) labels, a Microsoft tool used to classify and protect stored files. Access Analyzer employs the File System Solution to execute Access Auditing (FSAA) and/or Sensitive Data Discovery Auditing scans to find AIP Protection labels and scan protected (i.e. encrypted) files for sensitive data. This document provides information needed to properly configure access required by Access Analyzer to successfully scan for Azure Information Protection labels in a targeted environment. @@ -14,7 +14,7 @@ This document provides information needed to properly configure access required :::info **NOTE** -Access Analyzer does not scan for AIP Marking labels, only Protection labels. +Access Analyzer doesn't scan for AIP Marking labels, only Protection labels. ::: @@ -43,7 +43,7 @@ Ensure the following prerequisites are met before configuring AIP scanning: ### Rights Management Service Client Installation -The Rights Management Service Client must be installed on the applet servers where FSAA is running. This may be the local Access Analyzer server, a Proxy server, or a File Server running in applet mode. +You must install the Rights Management Service Client on the applet servers where FSAA is running. This may be the local Access Analyzer server, a Proxy server, or a File Server running in applet mode. * To install the Rights Management Service Client 2.1 on the server where the scan is taking place, go to the [Microsoft Download Center](https://www.microsoft.com/en-us/download/details.aspx?id=38396): @@ -74,7 +74,7 @@ Read the System Requirements and Install Instructions provided by Microsoft to c :::warning - This will disappear once you leave the page! + This will disappear when you leave the page. ::: 4. Add API permissions @@ -92,13 +92,13 @@ Read the System Requirements and Install Instructions provided by Microsoft to c ## **Enable the Account as an AIP Super User using PowerShell** -Follow the steps to enable the Service Principal Account in AIP as a Super User: +Enable the Service Principal Account in AIP as a Super User: :::info **NOTE** -All PowerShell commands should be run in order through PowerShell as an Admin. +Run all PowerShell commands in order through PowerShell as an Admin. ::: @@ -119,7 +119,7 @@ All PowerShell commands should be run in order through PowerShell as an Admin. `Enable-AIPServiceSuperUserFeature` -The Service Principal Account is now added to the Rights Management service as a Super User, and the Super User feature is enabled. +You've added the Service Principal Account to the Rights Management service as a Super User, and enabled the Super User feature. ## Add App Registration to the AIP Role in Microsoft® Azure @@ -130,33 +130,33 @@ In Microsoft Azure, add the Account to the Azure Information Protection Administ 2. Navigate to **Roles and Administrators**. On the Administrative Roles page, select the **Azure Information Protection Administrator** role. 3. Use the **Add Assignment** button to display the Add assignments pane. Search for the name of the new service principal account (the **DisplayName** entered in PowerShell) and add it to the list of assignments. -The Service Principal Account is now successfully added to the Azure Information Protection Administrator role. +You've now successfully added the Service Principal Account to the Azure Information Protection Administrator role. ## **Access Analyzer Configurations** -Before Access Analyzer can scan for AIP labels, two configurations must be done prior to the initial scan. +Complete two configurations before the initial scan so Access Analyzer can scan for AIP labels. * [Azure Connection Profile](https://docs.netwrix.com/docs/accessanalyzer/12_0/requirements/filesystem/filesystems/azureinformationprotection#azure-connection-profile) * [Configure FSAA Data Collector](https://docs.netwrix.com/docs/accessanalyzer/12_0/requirements/filesystem/filesystems/azureinformationprotection#configure-fsaa-data-collector) ### **Azure Connection Profile** -To collect tags for files protected with Azure Information Protection, an Azure connection profile must be configured in Access Analyzer before an FSAA scan runs. See the [Global Settings](https://docs.netwrix.com/docs/accessanalyzer/12_0/admin/settings/overview) topic for additional information on how to set up a connection profile at the global level. +To collect tags for files protected with Azure Information Protection, you must configure an Azure connection profile in Access Analyzer before an FSAA scan runs. See the [Global Settings](https://docs.netwrix.com/docs/accessanalyzer/12_0/admin/settings/overview) topic for additional information on how to set up a connection profile at the global level. 1. In Access Analyzer, add a credential for an Azure Active Directory account type to the existing Connection Profile used for File System scanning. Supply the Client ID field with the **AppID** and the Key field with the **Secret Value** created upon creation of the new service principal. 2. At the job level, apply the connection profile that contains both the Microsoft Entra ID credential and credentials required for File System scanning under the **Jobs** > \[**Job**\] > **Settings** > **Connection** node. 3. Ensure that the job is configured correctly before running a scan. See the [Configure FSAA Data Collector](https://docs.netwrix.com/docs/accessanalyzer/12_0/requirements/filesystem/filesystems/azureinformationprotection#configure-fsaa-data-collector) topic for additional information. -An Azure Connection Profile has now been successfully created for an FSAA scan. +You've now successfully created an Azure Connection Profile for an FSAA scan. ### **Configure FSAA Data Collector** -In Access Analyzer, configure the FSAA Data Collector wizard pages to scan files protected by Azure Information Protection. This can be done for both FSAA System Scans and SEEK System Scans. In the FSAA Data Collector Wizard, configure the following menus to scan for AIP protection labels: +In Access Analyzer, configure the FSAA Data Collector wizard pages to scan files protected by Azure Information Protection. You can do this for both FSAA System Scans and SEEK System Scans. In the FSAA Data Collector Wizard, configure the following menus to scan for AIP protection labels: For FSAA System Scans: -* Scan Server Selection – Choose the server that scanning is executed on. Target the server that has the Rights Management Service Client 2.1 installed where the applet is running. +* Scan Server Selection – Choose the server where scanning runs. Target the server that has the Rights Management Service Client 2.1 installed where the applet is running. * This may be a proxy server, file server (applet mode), or the local Access Analyzer console depending on scan configuration * Scan Settings – Select the **Enable scanning of files protected by Azure Information Protection** checkbox to add AIP files to the scan criteria * Azure Tenant Mapping page – Add the **AppID** and the **Domain Name** or **Tenant ID** @@ -175,7 +175,7 @@ For FSAA System Scans: For SEEK System Scans: -* Scan Server Selection – Choose the server that scanning is executed on. Target the server that has the Rights Management Service Client 2.1 installed where the applet is running. +* Scan Server Selection – Choose the server where scanning runs. Target the server that has the Rights Management Service Client 2.1 installed where the applet is running. * This may be a proxy server, file server (applet mode), or the local Access Analyzer console depending on scan configuration * Scan Settings – Select the **Enable scanning of files protected by Azure Information Protection** checkbox to add AIP files to the scan criteria * Azure Tenant Mapping page – Add the **AppID** and the **Domain Name** or **Tenant ID** diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellcelerravnx/access.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellcelerravnx/access.md index 2b7f11c235..e84f160895 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellcelerravnx/access.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellcelerravnx/access.md @@ -14,7 +14,7 @@ Follow the steps assign group membership through Computer Management. **Step 1 –** Open Computer Management (`compmgmt.msc`). -**Step 2 –** Right-click on the Computer Management (local) node and select Connect to another +**Step 2 –** Right-click the Computer Management (local) node and select Connect to another computer. **Step 3 –** Enter the name of the Dell device in the textbox and click OK. @@ -25,4 +25,4 @@ computer. **Step 6 –** Select the Power Users group and add the account being provisioned. -The account has been provisioned for Access Auditing and Sensitive Data Discovery Auditing. +You've provisioned the account for Access Auditing and Sensitive Data Discovery Auditing. diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellcelerravnx/activity/activity.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellcelerravnx/activity/activity.md index 907fe1610b..da6be779a2 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellcelerravnx/activity/activity.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellcelerravnx/activity/activity.md @@ -6,20 +6,20 @@ sidebar_position: 20 # Dell Celerra & Dell VNX Activity Auditing Configuration -An Dell Celerra or VNX device can be configured to audit Server Message Block (SMB) protocol access -events. All audit data can be forwarded to the Dell Common Event Enabler (CEE). The Activity Monitor +You can configure a Dell Celerra or VNX device to audit Server Message Block (SMB) protocol access +events. The device can forward all audit data to the Dell Common Event Enabler (CEE). The Activity Monitor listens for all events coming through the Dell CEE and translates all relevant information into entries in the Log files or syslog messages. -Complete the following checklist prior to configuring the Activity Monitor to monitor the host. +Complete the following checklist before configuring the Activity Monitor to monitor the host. Instructions for each item of the checklist are detailed within the following sections. **Checklist Item 1: Plan Deployment** -- Prior to beginning the deployment, gather the following: +- Before beginning the deployment, gather the following: - - DNS name of Celerra or VNX CIFS share(s) to be monitored - - Data Mover or Virtual Data Mover hosting the share(s) to be monitored + - DNS name of Celerra or VNX CIFS shares to be monitored + - Data Mover or Virtual Data Mover hosting the shares to be monitored - Account with access to the CLI - Download the Dell CEE from: @@ -27,20 +27,20 @@ Instructions for each item of the checklist are detailed within the following se **Checklist Item 2: Install Dell CEE** -- Dell CEE can be installed on the same Windows server as the Activity Agent, or on a different - server. If it is installed on the same host, the activity agent can configure it automatically. +- You can install Dell CEE on the same Windows server as the Activity Agent, or on a different + server. If you install it on the same host, the activity agent can configure it automatically. :::info - The latest version of Dell CEE is the recommended version to use with the + Netwrix recommends using the latest version of Dell CEE with the asynchronous bulk delivery (VCAPS) feature. ::: - Important: - - Open MS-RPC ports between the Dell device and the Windows proxy server(s) where the Dell CEE + - Open MS-RPC ports between the Dell device and the Windows proxy servers where the Dell CEE is installed - - Dell CEE 8.4.2 through Dell CEE 8.6.1 are not supported for use with the VCAPS feature + - Dell CEE 8.4.2 through Dell CEE 8.6.1 aren't supported for use with the VCAPS feature - Dell CEE requires .NET Framework 3.5 to be installed on the Windows proxy server - See the diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellcelerravnx/activity/installcee.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellcelerravnx/activity/installcee.md index e864633b2a..311c022bf2 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellcelerravnx/activity/installcee.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellcelerravnx/activity/installcee.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Install & Configure Dell CEE -Dell CEE should be installed on a Windows or a Linux server. The Dell CEE software is not a Netwrix +You should install Dell CEE on a Windows or a Linux server. The Dell CEE software isn't a Netwrix product. Dell customers have a support account with Dell to access the download. :::tip @@ -15,15 +15,15 @@ Remember, the latest version is the recommended version of Dell CEE. :::info -The Dell CEE package can be installed on the Windows server where the Activity +You can install the Dell CEE package on the Windows server where the Activity Monitor agent will be deployed (recommended) or on any other Windows or Linux server. ::: -Follow the steps to install the Dell CEE. +Install the Dell CEE. **Step 1 –** Obtain the latest CEE install package from Dell and any additional license required for -this component. It is recommended to use the most current version. +this component. Netwrix recommends using the most current version. **Step 2 –** Follow the instructions in the Dell [Using the Common Event Enabler on Windows Platforms](https://www.dell.com/support/home/en-us/product-support/product/common-event-enabler/docs) @@ -33,7 +33,7 @@ guide to install and configure the CEE. The installation will add two services t - EMC CEE Monitor (Display Name: EMC CEE Monitor) :::info -The latest version of .NET Framework and Dell CEE is recommended to use with the +Netwrix recommends using the latest version of .NET Framework and Dell CEE with the asynchronous bulk delivery (VCAPS) feature. ::: @@ -42,14 +42,14 @@ See the [CEE Debug Logs](/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellunity/activity/validate.md#cee-debug-logs) section for information on troubleshooting issues related to Dell CEE. -After Dell CEE installation is complete, it is necessary to +After Dell CEE installation is complete, proceed to [Connect Data Movers to the Dell CEE Server](#connect-data-movers-to-the-dell-cee-server). ## Configure Dell Registry Key Settings -There may be situations when Dell CEE needs to be installed on a different Windows server than the -one where the Activity Monitor activity agent is deployed. In those cases it is necessary to -manually set the Dell CEE registry key to forward events. +There may be situations when you need to install Dell CEE on a different Windows server than the +one where the Activity Monitor activity agent is deployed. In those cases, manually set the Dell +CEE registry key to forward events. **Step 1 –** Open the Registry Editor (run regedit). @@ -59,12 +59,12 @@ manually set the Dell CEE registry key to forward events. **HKEY_LOCAL_MACHINE\SOFTWARE\EMC\CEE\CEPP\AUDIT\Configuration** -**Step 3 –** Right-click on **Enabled** and select Modify. The Edit DWORD Value window opens. +**Step 3 –** Right-click **Enabled** and select Modify. The Edit DWORD Value window opens. **Step 4 –** In the Value data field, enter the value of 1. Click OK, and the Edit DWORD Value window closes. -**Step 5 –** Right-click on **EndPoint** and select Modify. The Edit String window opens. +**Step 5 –** Right-click **EndPoint** and select Modify. The Edit String window opens. **Step 6 –** In the Value data field, enter the StealthAUDIT value with the IP Address for the Windows proxy server hosting the Activity Monitor activity agent. Use the following format: @@ -75,13 +75,13 @@ Examples: **StealthAUDIT@192.168.30.15** -**Step 7 –** Click OK. The Edit String window closes. Registry Editor can be closed. +**Step 7 –** Click OK. The Edit String window closes. You can close Registry Editor. ![services](/images/activitymonitor/7.1/config/dellpowerstore/services.webp) **Step 8 –** Open Services (run `services.msc`). Start or Restart the EMC CEE Monitor service. -The Dell CEE registry key is now properly configured to forward event to the Activity Monitor +You've now properly configured the Dell CEE registry key to forward events to the Activity Monitor activity agent. ## Connect Data Movers to the Dell CEE Server @@ -95,19 +95,19 @@ Mover. administrative account should have a $ character in the terminal. :::note -Do not use a # charter. +Don't use a # charter. ::: **Step 2 –** Create or retrieve the `cepp.conf` file. -If there is not a `cepp.conf` file on the Data Mover(s), use a text editor to create a new blank +If there isn't a `cepp.conf` file on the Data Movers, use a text editor to create a new blank file in the home directory named `cepp.conf`. The following is an example command if using the text editor ‘vi’ to create a new blank file: **$ vi cepp.conf** -If a `cepp.conf` file already exists, it can be retrieved from the Data Movers for modification +If a `cepp.conf` file already exists, you can retrieve it from the Data Movers for modification with the following command: `$ server_file [DATA_MOVER_NAME] -get cepp.conf cepp.conf` @@ -117,17 +117,17 @@ with the following command: guide instructions on how to add parameters or edit the values or existing parameters. :::note -The information can be added to the file on one line or separate lines by using a space +You can add the information to the file on one line or separate lines by using a space and a ”\” at the end of each line, except for the last line and the lines that contain global options: `cifsserver`, `surveytime`, `ft`, and `msrpcuser`. ::: -The Activity Monitor requires the following parameters to be set in the `cepp.conf` file: +You must set the following parameters for the Activity Monitor in the `cepp.conf` file: - `pool name= ` - This should equal the name assigned to the configuration container. This container is composed - of the server(s) IP Address or FQDN where the Dell CEE is installed and where the list of + of the servers IP Address or FQDN where the Dell CEE is installed and where the list of events to be monitored is located. It can be named as desired but must be a pool name. - `servers= ` - This should equal the IP Address or FQDN of the Windows server where the Dell CEE is @@ -173,7 +173,7 @@ The Activity Monitor requires the following parameters to be set in the `cepp.co postevents=CloseModified|CloseUnmodified|CreateDir|CreateFile|DeleteDir|DeleteFile|RenameDir|RenameFile|SetAclDir|SetAclFile ``` -**Step 4 –** Move the `cepp.conf` file to the Data Mover(s) root file system. Run the following +**Step 4 –** Move the `cepp.conf` file to the Data Movers root file system. Run the following command: `$ server_file [DATA_MOVER_NAME]‑put cepp.conf cepp.conf` @@ -199,7 +199,7 @@ Then verify the CEPA status using the following command: `server_cepp [DATA_MOVER_NAME] -service –status` -Once the `cepp.config` file has been configured, it is time to configure and enable monitoring with +After you've configured the `cepp.config` file, configure and enable monitoring with the Activity Monitor. See the [Netwrix Activity Monitor Documentation](https://helpcenter.netwrix.com/category/activitymonitor) for additional information. diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellcelerravnx/activity/validate.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellcelerravnx/activity/validate.md index bf31934f05..92c4443daa 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellcelerravnx/activity/validate.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellcelerravnx/activity/validate.md @@ -6,7 +6,7 @@ sidebar_position: 20 # Validate Setup -Once the Activity Monitor agent is configured to monitor the Dell device, the automated +After the Activity Monitor agent is configured to monitor the Dell device, the automated configuration must be validated to ensure events are being monitored. ## Validate Dell CEE Registry Key Settings @@ -19,12 +19,13 @@ topic for information on manually setting the registry key. After the Activity Monitor activity agent has been configured to monitor the Dell device, it will -configure the Dell CEE automatically if it is installed on the same server as the agent. This needs +configure the Dell Common Event Enabler (CEE) automatically if it is installed on the same server as +the agent. This needs to be set manually in the rare situations where it is necessary for the Dell CEE to be installed on -a different server than the Windows proxy server(s) where the Activity Monitor activity agent is +a different server than the Windows proxy servers where the Activity Monitor activity agent is deployed. -If the monitoring agent is not registering events, validate that the EndPoint is accurately set. +If the monitoring agent isn't registering events, validate that the EndPoint is accurately set. Open the Registry Editor (run regedit). For the synchronous real-time delivery mode (AUDIT), use the following steps. @@ -91,7 +92,7 @@ additional information. ## Validate Dell CEE Services are Running After the Activity Monitor Activity Agent has been configured to monitor the Dell device, the Dell -CEE services should be running. If the Activity Agent is not registering events and the EndPoint is +CEE services should be running. If the Activity Agent isn't registering events and the EndPoint is set accurately, validate that the Dell CEE services are running. Open the Services (run `services.msc`). @@ -121,19 +122,19 @@ and Disable monitoring. **HKEY_LOCAL_MACHINE\SOFTWARE\EMC\CEE\Configuration** -**Step 10 –** Right-click on **Debug** and select Modify. The Edit DWORD Value window opens. In the +**Step 10 –** Right-click **Debug** and select Modify. The Edit DWORD Value window opens. In the Value data field, enter the value of 3F. Click OK, and the Edit DWORD Value window closes. :::note -If the Debug DWORD Value does not exist, it needs to be added. +If the Debug DWORD Value doesn't exist, it needs to be added. ::: -**Step 11 –** Right-click on **Verbose** and select Modify. The Edit DWORD Value window opens. In +**Step 11 –** Right-click **Verbose** and select Modify. The Edit DWORD Value window opens. In the Value data field, enter the value of 3F. Click OK, and the Edit DWORD Value window closes. :::note -If the Verbose DWORD Value does not exist, it needs to be added. +If the Verbose DWORD Value doesn't exist, it needs to be added. ::: diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellcelerravnx/overview.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellcelerravnx/overview.md index 9285ad28d2..0cfe451ea0 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellcelerravnx/overview.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellcelerravnx/overview.md @@ -39,7 +39,7 @@ topic for additional information. Troubleshooting Dell Celerra & Dell VNX Denied Access Errors If there are folders to which the credential is denied access, it is likely that the Backup -Operators group does not have the “Back up files and directories” right. In that case, it is +Operators group doesn't have the “Back up files and directories” right. In that case, it is necessary to assign additional the “Back up files and directories” right to those groups or to create a new local group, using Computer Management from a Windows server. Then assign rights to it using the CelerraManagementTool.msc plugin, which is available to Dell customers. For further @@ -104,7 +104,7 @@ are required for communication between the Agent server and the Netwrix Activity The Windows firewall rules need to be configured on the Windows server, which require certain inbound rules be created if the scans are running in applet mode. These scans operate over a default -port range, which cannot be specified via an inbound rule. For more information, see the Microsoft +port range, which can't be specified via an inbound rule. For more information, see the Microsoft [Connecting to WMI on a Remote Computer](https://msdn.microsoft.com/en-us/library/windows/desktop/aa389290(v=vs.85).aspx) article. diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellpowerscale/activity/activity.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellpowerscale/activity/activity.md index 0d614adcd1..8264a8cb31 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellpowerscale/activity/activity.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellpowerscale/activity/activity.md @@ -20,15 +20,15 @@ initiated the activity. The stored events are then forwarded by the node to the concurrently to several instances. At this point, Dell CEE forwards the audit event to a defined endpoint, such as Activity Monitor agent. -Complete the following checklist prior to configuring Activity Monitor to monitor the host. +Complete the following checklist before configuring Activity Monitor to monitor the host. Instructions for each item of the checklist are detailed within the following sections. **Checklist Item 1: Plan Deployment** -- Prior to beginning the deployment, gather the following: +- Before beginning the deployment, gather the following: - - DNS name of Isilon/PowerScale CIFS share(s) to be monitored - - Access Zone(s) containing the CIFS shares to be monitored + - DNS name of Isilon/PowerScale CIFS shares to be monitored + - Access Zones containing the CIFS shares to be monitored - Account with access to the OneFS UI or CLI - Download the Dell CEE from: @@ -36,8 +36,8 @@ Instructions for each item of the checklist are detailed within the following se :::info You can achieve higher throughput and fault tolerance by monitoring the -Isilon/PowerScale cluster with more than one pair of Dell CEE and Activity Monitor Agent. The -activity will be evenly distributed between the pairs. +Isilon/PowerScale cluster with more than one pair of Dell CEE and Activity Monitor Agent. Activity +Monitor distributes the activity evenly between the pairs. ::: @@ -80,20 +80,20 @@ Checklist Item 3: Configure Auditing on the Dell Isilon/PowerScale Cluster - Important: - Value of the **Storage Cluster Name** field must exactly match the name entered for the - monitored host in the Activity Monitor Console. If the Storage Cluster Name cannot be modified + monitored host in the Activity Monitor Console. If the Storage Cluster Name can't be modified (for example, another 3rd party depends on it), you need to set the Host Aliases parameter in the Activity Monitor Console. Otherwise, if for some reason the Storage Cluster Name must be - left empty, one can list OneFS cluster node names in the Host Aliases. + left empty, list the OneFS cluster node names in the Host Aliases instead. - - If the Storage Cluster Name is not empty, set the Host Aliases parameter to its value + - If the Storage Cluster Name isn't empty, set the Host Aliases parameter to its value - If the Storage Cluster Name is empty, set the Host Aliases to a semicolon-separated list of OneFS node names - Include all Access Zones to be monitored in the auditing configuration - As soon as the first CEE is installed, Isilon/PowerScale will start to send all activity, - including all previous audit events, to the agent. The start time can be modified to exclude - previously recorded audit events to prevent the agent from becoming overloaded with data. It - can be done using OneFS CLI only with isi audit modify command to edit the start time. + including all previous audit events, to the agent. You can modify the start time to exclude + previously recorded audit events and prevent the agent from becoming overloaded with data. You + can edit the start time only through the OneFS CLI, using the `isi audit modify` command. - Start time command: diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellpowerscale/activity/installcee.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellpowerscale/activity/installcee.md index ba11066859..0c0da683a9 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellpowerscale/activity/installcee.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellpowerscale/activity/installcee.md @@ -6,8 +6,8 @@ sidebar_position: 10 # Install Dell CEE -Dell CEE should be installed on a Windows or a Linux server. The Dell CEE software is not a Netwrix -product. Dell customers have a support account with Dell to access the download. +The Dell Common Event Enabler (CEE) should be installed on a Windows or a Linux server. The Dell CEE +software isn't a Netwrix product. Dell customers have a support account with Dell to access the download. :::tip Remember, the latest version is the recommended version of Dell CEE. @@ -20,7 +20,7 @@ Monitor agent will be deployed (recommended) or on any other Windows or Linux se ::: -Follow the steps to install the Dell CEE. +Install the Dell CEE. **Step 1 –** Obtain the latest CEE install package from Dell and any additional license required for this component. It is recommended to use the most current version. @@ -45,8 +45,8 @@ section for information on troubleshooting issues related to Dell CEE. ## Configure Dell Registry Key Settings There may be situations when Dell CEE needs to be installed on a different Windows server than the -one where the Activity Monitor activity agent is deployed. In those cases it is necessary to -manually set the Dell CEE registry key to forward events. +one where the Activity Monitor activity agent is deployed. In those cases, manually set the Dell +CEE registry key to forward events. **Step 1 –** Open the Registry Editor (run regedit). @@ -56,12 +56,12 @@ manually set the Dell CEE registry key to forward events. **HKEY_LOCAL_MACHINE\SOFTWARE\EMC\CEE\CEPP\AUDIT\Configuration** -**Step 3 –** Right-click on **Enabled** and select Modify. The Edit DWORD Value window opens. +**Step 3 –** Right-click **Enabled** and select Modify. The Edit DWORD Value window opens. **Step 4 –** In the Value data field, enter the value of 1. Click OK, and the Edit DWORD Value window closes. -**Step 5 –** Right-click on **EndPoint** and select Modify. The Edit String window opens. +**Step 5 –** Right-click **EndPoint** and select Modify. The Edit String window opens. **Step 6 –** In the Value data field, enter the StealthAUDIT value with the IP Address for the Windows proxy server hosting the Activity Monitor activity agent. Use the following format: diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellpowerscale/activity/manualconfiguration.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellpowerscale/activity/manualconfiguration.md index 4a7eb156ef..1f8fc2a084 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellpowerscale/activity/manualconfiguration.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellpowerscale/activity/manualconfiguration.md @@ -20,11 +20,11 @@ Administration Console. is typically used. If the CIFS or NFS shares are accessible through different zones on the OneFS cluster, include all relevant zones. -Ensure that OneFS collects only events you are interested in. By default, OneFS may monitor things -like directory reads, which can take up a large amount of space. Configuring the OneFS events that -need monitoring is not done through the Activity Monitor console. Configure OneFS event monitoring -using OneFS CLI with the isi audit modify command for each access zone. Enabling monitoring for only -what is needed for the environment will reduce the data load to the agent. +Ensure that OneFS collects only events you are interested in. By default, OneFS may monitor items +such as directory reads, which can use significant space. You can't configure which OneFS events +need monitoring through the Activity Monitor console. Configure OneFS event monitoring using the +OneFS CLI with the isi audit modify command for each access zone. Enabling monitoring only for what +your environment needs reduces the data load on the agent. Activity Monitor monitors the following events: `close_file_modified`, `close_file_unmodified`, `create_file`, `create_directory`, `delete_file`, `delete_directory`, `rename_file`, @@ -53,10 +53,10 @@ server hosting CEE. Use either of the following format: http://[SERVER Name]:[PORT]/cee :::info -When deploying multiple Dell CEE instances at scale, it is recommended that an -accommodating agent must be configured with each CEE instance. If multiple CEE instances send events -to just one agent, it may create an overflow of data and overload the agent. Distributing the -activity stream into pairs will be the most efficient way of monitoring large data sets at scale. +When deploying multiple Dell CEE instances at scale, configure an accommodating agent +for each CEE instance. If multiple CEE instances send events +to just one agent, it may create an overflow of data and overload the agent. Distribute the +activity stream into pairs to monitor large data sets most efficiently at scale. ::: @@ -65,7 +65,7 @@ be an exact match to the name which is entered in the Activity Monitor for the * list. This name is used as a ‘tag’ on all events coming through the CEE. This name must exactly match what -is in the Activity Monitor or it does not recognize the events. +is in the Activity Monitor or it doesn't recognize the events. :::info Use the CIFS DNS name for Dell OneFS. @@ -78,10 +78,10 @@ the name entered here must exactly match what is used for Enterprise Auditor as ::: -If the Storage Cluster Name cannot be modified (for example, another third-party depends on it), you +If the Storage Cluster Name can't be modified (for example, another third-party depends on it), you need to set the Host Aliases parameter in the Activity Monitor Console: -- If the Storage Cluster Name is not empty, set the Host Aliases parameter to its value +- If the Storage Cluster Name isn't empty, set the Host Aliases parameter to its value - If the Storage Cluster Name is empty, set the Host Aliases to a semicolon-separated list of OneFS node names diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellpowerscale/activity/validate.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellpowerscale/activity/validate.md index c4a2e2af40..cf58786278 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellpowerscale/activity/validate.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellpowerscale/activity/validate.md @@ -6,18 +6,19 @@ sidebar_position: 30 # Validate Setup -Once the Activity Monitor agent is configured to monitor the Dell device, the automated +After the Activity Monitor agent is configured to monitor the Dell device, the automated configuration must be validated to ensure events are being monitored. ## Validate Dell CEE Registry Key Settings After the Activity Monitor activity agent has been configured to monitor the Dell device, it will -configure the Dell CEE automatically if it is installed on the same server as the agent. This needs +configure the Dell Common Event Enabler (CEE) automatically if it is installed on the same server as +the agent. This needs to be set manually in the rare situations where it is necessary for the Dell CEE to be installed on -a different server than the Windows proxy server(s) where the Activity Monitor activity agent is +a different server than the Windows proxy servers where the Activity Monitor activity agent is deployed. -If the monitoring agent is not registering events, validate that the EndPoint is accurately set. +If the monitoring agent isn't registering events, validate that the EndPoint is accurately set. Open the Registry Editor (run regedit). For the synchronous real-time delivery mode (AUDIT), use the following steps. @@ -84,7 +85,7 @@ additional information. ## Validate Dell CEE Services are Running After the Activity Monitor Activity Agent has been configured to monitor the Dell device, the Dell -CEE services should be running. If the Activity Agent is not registering events and the EndPoint is +CEE services should be running. If the Activity Agent isn't registering events and the EndPoint is set accurately, validate that the Dell CEE services are running. Open the Services (run `services.msc`). @@ -114,19 +115,19 @@ and Disable monitoring. **HKEY_LOCAL_MACHINE\SOFTWARE\EMC\CEE\Configuration** -**Step 10 –** Right-click on **Debug** and select Modify. The Edit DWORD Value window opens. In the +**Step 10 –** Right-click **Debug** and select Modify. The Edit DWORD Value window opens. In the Value data field, enter the value of 3F. Click OK, and the Edit DWORD Value window closes. :::note -If the Debug DWORD Value does not exist, it needs to be added. +If the Debug DWORD Value doesn't exist, it needs to be added. ::: -**Step 11 –** Right-click on **Verbose** and select Modify. The Edit DWORD Value window opens. In +**Step 11 –** Right-click **Verbose** and select Modify. The Edit DWORD Value window opens. In the Value data field, enter the value of 3F. Click OK, and the Edit DWORD Value window closes. :::note -If the Verbose DWORD Value does not exist, it needs to be added. +If the Verbose DWORD Value doesn't exist, it needs to be added. ::: @@ -158,8 +159,7 @@ The debug log is stored in `/opt/CEEPack/emc_cee_svc.log` file. To enable verbos and Verbose parameters under **Configuration** to 255 and restart the CEE. :::note -Debug logs should only be used for troubleshooting purposes. It's recommended to have -Debug Logs disabled by default. +Use debug logs only for troubleshooting. Disable them by default. ::: diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellpowerscale/overview.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellpowerscale/overview.md index 15c8a019fb..b7f519bc69 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellpowerscale/overview.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellpowerscale/overview.md @@ -38,7 +38,7 @@ topic for additional information. **Additional Sensitive Data Discovery Auditing Permission** -In order to execute scoped Sensitive Data Discovery Auditing scans, the credential must also have +to execute scoped Sensitive Data Discovery Auditing scans, the credential must also have the LOCAL:System provider selected in each access zone in which the shares to be scanned reside. The credential must have an Authentication Provider configured for the Isilon/PowerScale device. For @@ -71,8 +71,8 @@ Share permissions can now be granted to this credential. ## BackupAdmin Role Assignment for OneFS -Follow the steps to assign the credential to the **BackupAdmin** role through OneFS Storage -Administration Console. +Assign the credential to the **BackupAdmin** role through the OneFS Storage +Administration Console using the following steps. **Step 1 –** Navigate to the **Access** tab > **Membership & Roles** for the System Access Zone. @@ -125,8 +125,8 @@ scan. ### Troubleshooting NFSv3 Export Access -If Enterprise Auditor is not discovering the expected NFS export, it is possible that the export -policy is not properly configured to allow the Enterprise Auditor server or proxy server IP Address +If Enterprise Auditor isn't discovering the expected NFS export, it is possible that the export +policy isn't properly configured to allow the Enterprise Auditor server or proxy server IP Address to mount the NFS export. One step in troubleshooting this issue is to confirm a Unix client (or WSL for Windows) in the same IP range as the Enterprise Auditor server or proxy server can mount the NFS export. @@ -198,7 +198,7 @@ are required for communication between the Agent server and the Netwrix Activity The Windows firewall rules need to be configured on the Windows server, which require certain inbound rules be created if the scans are running in applet mode. These scans operate over a default -port range, which cannot be specified via an inbound rule. For more information, see the Microsoft +port range, which can't be specified via an inbound rule. For more information, see the Microsoft [Connecting to WMI on a Remote Computer](https://msdn.microsoft.com/en-us/library/windows/desktop/aa389290(v=vs.85).aspx) article. diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellunity/access.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellunity/access.md index 8434e7f0bb..f4e1623f62 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellunity/access.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellunity/access.md @@ -14,7 +14,7 @@ Follow the steps assign group membership through Computer Management. **Step 1 –** Open Computer Management (`compmgmt.msc`). -**Step 2 –** Right-click on the Computer Management (local) node and select Connect to another +**Step 2 –** Right-click the Computer Management (local) node and select Connect to another computer. **Step 3 –** Enter the name of the Dell device in the textbox and click OK. diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellunity/activity/activity.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellunity/activity/activity.md index d1bb999b41..9f0eaada21 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellunity/activity/activity.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellunity/activity/activity.md @@ -20,14 +20,14 @@ activity log file is created if there is no activity for the day. **Configuration Checklist** -Complete the following checklist prior to configuring activity monitoring of Dell Unity devices. +Complete the following checklist before configuring activity monitoring of Dell Unity devices. Instructions for each item of the checklist are detailed within the following topics. **Checklist Item 1: Plan Deployment** -- Prior to beginning the deployment, gather the following: +- Before beginning the deployment, gather the following: - - Data Mover or Virtual Data Mover hosting the share(s) to be monitored + - Data Mover or Virtual Data Mover hosting the shares to be monitored - Account with access to the CLI - Download the Dell CEE from: @@ -36,7 +36,7 @@ Instructions for each item of the checklist are detailed within the following to Checklist Item 2: [Install Dell CEE](/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellunity/activity/installcee.md) -- Dell CEE should be installed on the Windows proxy server(s) where the Activity Monitor activity +- Dell CEE should be installed on the Windows proxy servers where the Activity Monitor activity agent will be deployed :::info @@ -47,9 +47,9 @@ Checklist Item 2: - Important: - - Open MS-RPC ports between the Dell device and the Windows proxy server(s) where the Dell CEE + - Open MS-RPC ports between the Dell device and the Windows proxy servers where the Dell CEE is installed - - Dell CEE 8.4.2 through Dell CEE 8.6.1 are not supported for use with the VCAPS feature + - Dell CEE 8.4.2 through Dell CEE 8.6.1 aren't supported for use with the VCAPS feature - Dell CEE requires .NET Framework 3.5 to be installed on the Windows proxy server **Checklist Item 3: Dell Unity Device Configuration** @@ -70,8 +70,8 @@ Checklist Item 2: Checklist Item 5: Configure Dell CEE to Forward Events to the Activity Agent :::note -When Dell CEE is installed on Windows proxy server(s) where the Activity Monitor activity -agent will be deployed, the following steps are not needed. +When Dell CEE is installed on Windows proxy servers where the Activity Monitor activity +agent will be deployed, the following steps aren't needed. ::: diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellunity/activity/installcee.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellunity/activity/installcee.md index 358642e989..9fdcf4ae2d 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellunity/activity/installcee.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellunity/activity/installcee.md @@ -6,8 +6,8 @@ sidebar_position: 10 # Install Dell CEE -Dell CEE should be installed on a Windows or a Linux server. The Dell CEE software is not a Netwrix -product. Dell customers have a support account with Dell to access the download. +The Dell Common Event Enabler (CEE) should be installed on a Windows or a Linux server. The Dell CEE +software isn't a Netwrix product. Dell customers have a support account with Dell to access the download. :::tip Remember, the latest version is the recommended version of Dell CEE. @@ -20,7 +20,7 @@ Monitor agent will be deployed (recommended) or on any other Windows or Linux se ::: -Follow the steps to install the Dell CEE. +Install the Dell CEE using the following steps. **Step 1 –** Obtain the latest CEE install package from Dell and any additional license required for this component. It is recommended to use the most current version. @@ -38,14 +38,14 @@ asynchronous bulk delivery (VCAPS) feature. ::: -After Dell CEE installation is complete, it is necessary to complete the +After you install Dell CEE, complete the [Unity Initial Setup with Unisphere](/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellunity/activity/setupunisphere.md). ## Configure Dell Registry Key Settings There may be situations when Dell CEE needs to be installed on a different Windows server than the -one where the Activity Monitor activity agent is deployed. In those cases it is necessary to -manually set the Dell CEE registry key to forward events. +one where the Activity Monitor activity agent is deployed. In those cases, manually set the +Dell CEE registry key to forward events. **Step 1 –** Open the Registry Editor (run regedit). @@ -55,12 +55,12 @@ manually set the Dell CEE registry key to forward events. **HKEY_LOCAL_MACHINE\SOFTWARE\EMC\CEE\CEPP\AUDIT\Configuration** -**Step 3 –** Right-click on **Enabled** and select Modify. The Edit DWORD Value window opens. +**Step 3 –** Right-click **Enabled** and select Modify. The Edit DWORD Value window opens. **Step 4 –** In the Value data field, enter the value of 1. Click OK, and the Edit DWORD Value window closes. -**Step 5 –** Right-click on **EndPoint** and select Modify. The Edit String window opens. +**Step 5 –** Right-click **EndPoint** and select Modify. The Edit String window opens. **Step 6 –** In the Value data field, enter the StealthAUDIT value with the IP Address for the Windows proxy server hosting the Activity Monitor activity agent. Use the following format: diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellunity/activity/setupunisphere.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellunity/activity/setupunisphere.md index a8be8dce3d..64c540cc24 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellunity/activity/setupunisphere.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellunity/activity/setupunisphere.md @@ -6,12 +6,12 @@ sidebar_position: 20 # Unity Initial Setup with Unisphere -Follow the steps to configure the initial setup for a Unity device with Unisphere. +Configure the initial setup for a Unity device with Unisphere using the following steps. **Step 1 –** Edit the NAS Server > Protection and Events > Events Publishing > Select Pool settings: -- Add CEPA server – This is the server where CEE is installed. It is recommended that this is also - the server were the Activity Monitor activity agent is deployed. +- Add CEPA server – This is the server where the Dell Common Event Enabler (CEE) is installed. This + should also be the server where the Activity Monitor activity agent is deployed. - Enable the following events for Post Events. Required Unity events needed for CIFS Activity: diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellunity/activity/validate.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellunity/activity/validate.md index 54b1932f77..c563bd3df2 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellunity/activity/validate.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellunity/activity/validate.md @@ -6,7 +6,7 @@ sidebar_position: 30 # Validate Setup -Once the Activity Monitor agent is configured to monitor the Dell device, the automated +After the Activity Monitor agent is configured to monitor the Dell device, the automated configuration must be validated to ensure events are being monitored. ## Validate CEE Registry Key Settings @@ -19,12 +19,13 @@ topic for information on manually setting the registry key. After the Activity Monitor activity agent has been configured to monitor the Dell device, it will -configure the Dell CEE automatically if it is installed on the same server as the agent. This needs +configure the Dell Common Event Enabler (CEE) automatically if it is installed on the same server as +the agent. This needs to be set manually in the rare situations where it is necessary for the Dell CEE to be installed on -a different server than the Windows proxy server(s) where the Activity Monitor activity agent is +a different server than the Windows proxy servers where the Activity Monitor activity agent is deployed. -If the monitoring agent is not registering events, validate that the EndPoint is accurately set. +If the monitoring agent isn't registering events, validate that the EndPoint is accurately set. Open the Registry Editor (run regedit). For the synchronous real-time delivery mode (AUDIT), use the following steps. @@ -91,7 +92,7 @@ additional information. ## Validate Dell CEE Services are Running After the Activity Monitor Activity Agent has been configured to monitor the Dell device, the Dell -CEE services should be running. If the Activity Agent is not registering events and the EndPoint is +CEE services should be running. If the Activity Agent isn't registering events and the EndPoint is set accurately, validate that the Dell CEE services are running. Open the Services (run `services.msc`). @@ -121,19 +122,19 @@ and Disable monitoring. **HKEY_LOCAL_MACHINE\SOFTWARE\EMC\CEE\Configuration** -**Step 10 –** Right-click on **Debug** and select Modify. The Edit DWORD Value window opens. In the +**Step 10 –** Right-click **Debug** and select Modify. The Edit DWORD Value window opens. In the Value data field, enter the value of 3F. Click OK, and the Edit DWORD Value window closes. :::note -If the Debug DWORD Value does not exist, it needs to be added. +If the Debug DWORD Value doesn't exist, it needs to be added. ::: -**Step 11 –** Right-click on **Verbose** and select Modify. The Edit DWORD Value window opens. In +**Step 11 –** Right-click **Verbose** and select Modify. The Edit DWORD Value window opens. In the Value data field, enter the value of 3F. Click OK, and the Edit DWORD Value window closes. :::note -If the Verbose DWORD Value does not exist, it needs to be added. +If the Verbose DWORD Value doesn't exist, it needs to be added. ::: diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellunity/overview.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellunity/overview.md index 114d4a906f..95e373598b 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellunity/overview.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/dellunity/overview.md @@ -39,7 +39,7 @@ topic for additional information. **Troubleshooting Dell Unity Denied Access Errors** If there are folders to which the credential is denied access, it is likely that the Backup -Operators group does not have the “Back up files and directories” right. In that case, it is +Operators group doesn't have the “Back up files and directories” right. In that case, it is necessary to assign additional the “Back up files and directories” right to those groups or to create a new local group, using Computer Management from a Windows server. Then assign rights to it using the CelerraManagementTool.msc plugin, which is available to Dell customers. For further @@ -104,7 +104,7 @@ are required for communication between the Agent server and the Netwrix Activity The Windows firewall rules need to be configured on the Windows server, which require certain inbound rules be created if the scans are running in applet mode. These scans operate over a default -port range, which cannot be specified via an inbound rule. For more information, see the Microsoft +port range, which can't be specified via an inbound rule. For more information, see the Microsoft [Connecting to WMI on a Remote Computer](https://msdn.microsoft.com/en-us/library/windows/desktop/aa389290(v=vs.85).aspx) article. diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/filesystems.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/filesystems.md index 129aa2f50f..9ba731e576 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/filesystems.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/filesystems.md @@ -111,7 +111,7 @@ See the [Hitachi Target Requirements](/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/hitachi/overview.md) topic for target environment requirements. -**Nasuni Nasuni Edge Appliances** +**Nasuni Edge Appliances** - 8.0+ @@ -125,7 +125,7 @@ for target environment requirements. - Cluster-Mode 8.2+ :::note - The Resiliency feature introduced in ONTAP 9.0 is not supported. + The Resiliency feature introduced in ONTAP 9.0 isn't supported. ::: diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/hitachi/activity/activity.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/hitachi/activity/activity.md index 0851cb0914..f0aab74c80 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/hitachi/activity/activity.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/hitachi/activity/activity.md @@ -11,7 +11,7 @@ multiple file systems. Auditing is enabled and configured per file system. This to enable auditing on an HNAS and to configure the Activity Monitor to monitor activity coming from the Hitachi device auditing. -The Activity Monitor does not use the EVS or file system name to connect to HNAS. Therefore, all +The Activity Monitor doesn't use the EVS or file system name to connect to HNAS. Therefore, all that is required of the user for HNAS activity collection is the following: - Logs path (UNC) @@ -39,11 +39,11 @@ clients using other protocols would be costly in terms of system performance, be operation would have to be audited as an open operation. **Therefore, when file system auditing is enabled, by default, only clients connecting through the CIFS protocol are allowed access to the file system.** Access by clients using other protocols, like NFS, can, however, be allowed. When -such access is allowed, access to file system objects through these protocols is not audited.” +such access is allowed, access to file system objects through these protocols isn't audited.” :::note File system auditing can be configured to deny access to clients connecting with protocols -that cannot be audited (NFS). Please see the Hitachi +that can't be audited (NFS). see the Hitachi [Server and Cluster Administration Guide](https://support.hds.com/download/epcra/hnas0106.pdf) for additional information. ::: @@ -51,7 +51,7 @@ additional information. **Configuration Checklist** -Complete the following checklist prior to configuring activity monitoring of Hitachi devices. +Complete the following checklist before configuring activity monitoring of Hitachi devices. Instructions for each item of the checklist are detailed within the following topics. Checklist Item 1: diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/hitachi/activity/configureaccesstologs.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/hitachi/activity/configureaccesstologs.md index deade0c148..5a1ece6217 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/hitachi/activity/configureaccesstologs.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/hitachi/activity/configureaccesstologs.md @@ -6,8 +6,8 @@ sidebar_position: 20 # Configure Access to HNAS Audit Logs on Activity Agent Server -Follow the steps to configure access to the HNAS audit logs on the Windows server hosting the -Activity Monitor activity agent. +Configure access to the HNAS audit logs on the Windows server hosting the +Activity Monitor activity agent using the following steps. **Step 1 –** On the Windows computer, go to Run and type `compmgmt.msc`. @@ -22,7 +22,7 @@ Folders > Shares. **Step 5 –** Select the Security tab and click Advanced. **Step 6 –** In the Advanced Security Settings dialog box, select the Audit tab. Click Add or Edit -to select the users and groups to be audited and add the desired user or group. +to select the users and groups to be audited and add the user or group you want. **Step 7 –** Select All for Type, and Full Control for Basic permissions. diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/hitachi/activity/configurelogs.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/hitachi/activity/configurelogs.md index 1b4ca664f9..b9d4262eca 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/hitachi/activity/configurelogs.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/hitachi/activity/configurelogs.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Configure Audit Logs on HNAS -Follow the steps to configure access to the HNAS audit logs on the Hitachi device. +Configure access to the HNAS audit logs on the Hitachi device using the following steps. **Step 1 –** Open a browser and enter the IP Address for HNAS in the address bar to launch the Hitachi Storage Navigator (SN). Enter the username and password. @@ -33,7 +33,7 @@ auditing). In the Audit Log section, set the maximum log file size to a value of is recommended to set it to 16 MB. In the Log roll over policy section, select New. The product does not support the Wrap policy. Click OK to close. -Once access has been configured on the Hitachi device, it is necessary to configure access to the +Once access has been configured on the Hitachi device, configure access to the HNAS audit logs on the Windows server. See the [Configure Access to HNAS Audit Logs on Activity Agent Server](/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/hitachi/activity/configureaccesstologs.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/hitachi/overview.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/hitachi/overview.md index 75ae42426d..17cd25e5f0 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/hitachi/overview.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/hitachi/overview.md @@ -88,7 +88,7 @@ are required for communication between the Agent server and the Netwrix Activity The Windows firewall rules need to be configured on the Windows server, which require certain inbound rules be created if the scans are running in applet mode. These scans operate over a default -port range, which cannot be specified via an inbound rule. For more information, see the Microsoft +port range, which can't be specified via an inbound rule. For more information, see the Microsoft [Connecting to WMI on a Remote Computer](https://msdn.microsoft.com/en-us/library/windows/desktop/aa389290(v=vs.85).aspx) article. diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/nasuni/access.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/nasuni/access.md index d39752986a..8c0d490a98 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/nasuni/access.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/nasuni/access.md @@ -6,12 +6,12 @@ sidebar_position: 10 # Nasuni Edge Appliance Access & Sensitive Data Auditing Configuration -It is necessary to generate an API Key Name and Passcode for each on-premise Nasuni Edge Appliance +Generate an API Key Name and Passcode for each on-premise Nasuni Edge Appliance and cloud filer. ## Nasuni Filer Management Interface -Follow the steps to generate a Nasuni API Access Key in the Nasuni Filer Management Interface. +Generate a Nasuni API Access Key in the Nasuni Filer Management Interface using the following steps. **Step 1 –** Within the **Configuration** menu, under **USERS & SECURITY**, select API Access Keys. The API Access Keys page opens. @@ -39,14 +39,14 @@ documentation for additional information. ## Nasuni Management Console -Follow the steps to generate a Nasuni API Access Key in the Nasuni Management Console. +Generate a Nasuni API Access Key in the Nasuni Management Console using the following steps. **Step 1 –** Click Filers and select API Keys from the menu on the left. The Filer API Access Key Settings page opens. **Step 2 –** Click New API Key button. The Add API Access Key window opens. -**Step 3 –** From the Filer drop-down menu, select the desired Nasuni Edge Appliance. Then enter a +**Step 3 –** From the Filer dropdown menu, select the Nasuni Edge Appliance you want. Then enter a Name for the key; for example, the name of the application. **Step 4 –** Click Add API Key. @@ -68,13 +68,12 @@ documentation for additional information. ## Nasuni Best Practices for Access Auditing -Nasuni is a hybrid NAS where actively-used data is stored on a Nasuni Edge appliance while the -authoritative copy of all files and meta data is stored in private or public cloud object storage -platforms by the UniFS® global file system, and there are egress fees associated with transferring -data between the two. In order to minimize these egress fees and optimize scan performance, it is -recommended to deploy a dedicated Nasuni Edge Appliance with all shares to be scanned by Enterprise -Auditor mounted, and the Enterprise Auditor console server, in the same region where the -authoritative copy resides. +Nasuni is a hybrid NAS: a Nasuni Edge Appliance stores actively used data locally, while the UniFS® +global file system stores the authoritative copy of all files and metadata in private or public +cloud object storage platforms. Transferring data between the two incurs egress fees. To minimize +these fees and optimize scan performance, deploy a dedicated Nasuni Edge Appliance with all shares +that Enterprise Auditor scans mounted, and place the Enterprise Auditor console server in the same +region as the authoritative copy. See the [External Auditing and Nasuni Best Practices](https://nasuni.my.salesforce.com/sfc/p/#external-auditing-and-nasuni-best-practices) diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/nasuni/activity.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/nasuni/activity.md index b4a1c231fb..df486b6ca1 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/nasuni/activity.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/nasuni/activity.md @@ -6,14 +6,14 @@ sidebar_position: 20 # Nasuni Edge Appliance Activity Auditing Configuration -Generation of an API Access Key is required for Nasuni activity monitoring. The Nasuni Edge -Appliance generates its own audit trail. An API Access Key is used by the Activity Monitor to form a -network connection to the appliance. Nasuni will then stream event data to the activity agent. See +Nasuni activity monitoring requires an API Access Key. The Nasuni Edge Appliance generates its own +audit trail. The Activity Monitor uses an API Access Key to form a network connection to the +appliance. Nasuni then streams event data to the activity agent. See [Nasuni Support Documentation](https://www.nasuni.com/support/) for additional information. **Configuration Checklist** -Complete the following checklist prior to configuring activity monitoring of Nasuni Edge Appliances. +Complete the following checklist before configuring activity monitoring of Nasuni Edge Appliances. Instructions for each item of the checklist are detailed within the following topics. **Checklist Item 1: Generate Nasuni API Access Key** @@ -30,7 +30,7 @@ Instructions for each item of the checklist are detailed within the following to ## Nasuni Filer Management Interface -Follow the steps to generate a Nasuni API Access Key in the Nasuni Filer Management Interface. +Generate a Nasuni API Access Key in the Nasuni Filer Management Interface using the following steps. **Step 1 –** Within the **Configuration** menu, under **USERS & SECURITY**, select API Access Keys. The API Access Keys page opens. @@ -43,9 +43,9 @@ The API Access Keys page opens. **Step 5 –** In the Successfully Generated API Key window, copy the Key Passcode. -Both the Key Name and the Key Passcode are required by the Activity Monitor in order to connect to -the Nasuni Edge Appliance. Once the API Key has been generated, it is time to configure and enable -monitoring with the Activity Monitor console. +The Activity Monitor requires both the Key Name and the Key Passcode to connect to the Nasuni Edge +Appliance. After you generate the API Key, configure and enable monitoring with the Activity Monitor +console. :::note Nasuni API key names are case sensitive. When providing them, ensure they are entered in @@ -55,23 +55,23 @@ the exact same case as generated. ## Nasuni Management Console -Follow the steps to generate a Nasuni API Access Key in the Nasuni Management Console. +Generate a Nasuni API Access Key in the Nasuni Management Console using the following steps. **Step 1 –** Click Filers and select API Keys from the menu on the left. The Filer API Access Key Settings page opens. **Step 2 –** Click New API Key button. The Add API Access Key window opens. -**Step 3 –** From the Filer drop-down menu, select the desired Nasuni Edge Appliance. Then enter a +**Step 3 –** From the Filer dropdown menu, select the Nasuni Edge Appliance you want. Then enter a Name for the key; for example, the name of the application. **Step 4 –** Click Add API Key. **Step 5 –** A message appears which includes the Key Passcode; copy the Key Passcode. -Both the Key Name and the Key Passcode are required by the Activity Monitor in order to connect to -the Nasuni Edge Appliance. Once the API Key has been generated, it is time to configure and enable -monitoring with the Activity Monitor console. +The Activity Monitor requires both the Key Name and the Key Passcode to connect to the Nasuni Edge +Appliance. After you generate the API Key, configure and enable monitoring with the Activity Monitor +console. :::note Nasuni API key names are case sensitive. When providing them, ensure they are entered in diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/nasuni/overview.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/nasuni/overview.md index 2ddd4251f7..c7dc39dd6c 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/nasuni/overview.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/nasuni/overview.md @@ -59,7 +59,7 @@ Enterprise Auditor to read the activity log files must have also have this permi **Nasuni Edge Appliance Requirements** -Additionally, it is necessary to generate an API Access Key for Nasuni activity monitoring. See the +Additionally, generate an API Access Key for Nasuni activity monitoring. See the [Nasuni Edge Appliance Activity Auditing Configuration](/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/nasuni/activity.md) topic for instructions. @@ -80,7 +80,7 @@ are required for communication between the Agent server and the Netwrix Activity The Windows firewall rules need to be configured on the Windows server, which require certain inbound rules be created if the scans are running in applet mode. These scans operate over a default -port range, which cannot be specified via an inbound rule. For more information, see the Microsoft +port range, which can't be specified via an inbound rule. For more information, see the Microsoft [Connecting to WMI on a Remote Computer](https://msdn.microsoft.com/en-us/library/windows/desktop/aa389290(v=vs.85).aspx) article. diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/access/access.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/access/access.md index 745d396054..aeaaca57be 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/access/access.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/access/access.md @@ -30,7 +30,7 @@ api-volume-list-info-iter-* ## Bypass NTFS Security for 7-Mode -In order to bypass NTFS, the credential needs to at least have the following permissions on the +to bypass NTFS, the credential needs to at least have the following permissions on the NetApp device: - Group membership in both of the following groups: diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/access/provisionaccess.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/access/provisionaccess.md index 87eaed619c..108bd0d8c7 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/access/provisionaccess.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/access/provisionaccess.md @@ -8,13 +8,13 @@ sidebar_position: 10 This section describes the steps needed to create a user account with the privileges required to execute Access Auditing (FSAA) and/or Sensitive Data Discovery Auditing scans from Enterprise -Auditor. It is necessary to: +Auditor. This requires the following tasks: - Create Role - Create a Group & Assign Role - Add User to Group -Relevant NetApp Documentation: To learn more about node access controls, please visit the NetApp +Relevant NetApp Documentation: To learn more about node access controls, visit the NetApp website and read the [na_useradmin – Administers node access controls](https://library.netapp.com/ecmdocs/ECMP1511537/html/man1/na_useradmin.1.html) article. @@ -47,7 +47,7 @@ After the role is created, Create a Group & Assign Role. ## Create a Group & Assign Role -Once the role has been created, it must be attached to a group. The following command needs to be +After the role is created, it must be attached to a group. The following command needs to be run to create a group and assign the role to it. ``` diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/activity/activity.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/activity/activity.md index afeb718bc4..1e4f488b1b 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/activity/activity.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/activity/activity.md @@ -6,9 +6,9 @@ sidebar_position: 20 # NetApp Data ONTAP 7-Mode Activity Auditing Configuration -The Activity Monitor agent employed to monitor NetApp leverages 128-bit encrypted Remote Procedure +The Activity Monitor agent employed to monitor NetApp uses 128-bit encrypted Remote Procedure Calls (RPC), NetApp ONTAP-API, and NetApp FPolicy to monitor file system events. This includes both -NetApp 7-Mode and Cluster-Mode configurations. To learn more about FPolicy please visit the NetApp +NetApp 7-Mode and Cluster-Mode configurations. To learn more about FPolicy visit the NetApp website and read the [What FPolicy is](https://library.netapp.com/ecmdocs/ECMP1401220/html/GUID-54FE1A84-6CF0-447E-9AAE-F43B61CA2138.html) article. @@ -17,7 +17,7 @@ If the activity agent is stopped, a notification will be sent to the NetApp devi disable the associated FPolicy policy, but it will not be removed. If the network connection is lost between the activity agent and the NetApp device, the NetApp -device is configured with a default timeout to wait for a response. If a response is not received +device is configured with a default timeout to wait for a response. If a response isn't received from the Activity Agent within the timeout, then the NetApp device will disconnect and disable the FPolicy policy. The Activity Agent will check every minute by default to see if the FPolicy policy has been disabled and will enable it (if the auto-enable functionality is enabled for the agent). @@ -29,7 +29,7 @@ No activity log file will be created if there is no activity for the day. **Configuration Checklist** -Complete the following checklist prior to configuring activity monitoring of NetApp Data ONTAP +Complete the following checklist before configuring activity monitoring of NetApp Data ONTAP 7-Mode devices. Instructions for each item of the checklist are detailed within the following topics. @@ -37,7 +37,7 @@ topics. - Gather the following information: - Names of the vFiler™(s) to be monitored - - DNS name of the CIFS shares(s) to be monitored + - DNS name of the CIFS sharess to be monitored Checklist Item 2: [Provision FPolicy Account](/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/activity/provisionactivity.md) diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/activity/configurefpolicy.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/activity/configurefpolicy.md index 09fa54419c..44ae67b5cf 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/activity/configurefpolicy.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/activity/configurefpolicy.md @@ -8,7 +8,7 @@ sidebar_position: 30 Select a method to configure the FPolicy for NetApp Data ONTAP 7-Mode devices: -**:::info** +:::info [Manually Configure FPolicy (Recommended Option)](#manually-configure-fpolicy-recommended-option) – A tailored FPolicy @@ -30,7 +30,7 @@ A tailored FPolicy ## Manually Configure FPolicy (Recommended Option) This section describes how to manually configure FPolicy. Manual configuration of the FPolicy is -recommended so that the policy can be scoped. It is necessary to create six FPolicy components and +recommended so that the policy can be scoped. Create six FPolicy components and then enable the FPolicy. See the sections corresponding to each part of this list: - [Part 1: Create FPolicy](#part-1-create-fpolicy) @@ -46,7 +46,7 @@ vFiler. This is because FPolicy operates on the affected vFiler. Therefore, when commands on a vFiler, the commands must be run from a vFiler context (e.g. via the vFiler run command). -Relevant NetApp Documentation: To learn more about configuring file policies, please visit the +Relevant NetApp Documentation: To learn more about configuring file policies, visit the NetApp website and read [na_fpolicy – configure file policies](https://library.netapp.com/ecmdocs/ECMP1196890/html/man1/na_fpolicy.1.html) article. @@ -68,8 +68,8 @@ fpolicy create StealthAUDIT screen ### Part 2: Set FPolicy Required to Off -If the `FPolicy Required` value is set to on, user requests are denied if an FPolicy server is not -available to implement the policy. If it is set to off, user requests are allowed when it is not +If the `FPolicy Required` value is set to on, user requests are denied if an FPolicy server isn't +available to implement the policy. If it is set to off, user requests are allowed when it isn't possible to apply the policy to the file because no FPolicy server is available. IMPORTANT: @@ -175,6 +175,6 @@ fpolicy enable StealthAUDIT ## Automatic Configuration of FPolicy The Activity Monitor can automatically configure FPolicy on the targeted NetApp Data ONTAP 7-Mode -device. The FPolicy created monitors all file system activity. This is done when the NetApp device -is assigned to the agent for monitoring. This option is enabled on the NetApp FPolicy Configuration -page of the Add New Host window. +device. The FPolicy it creates monitors all file system activity. The Activity Monitor configures +FPolicy automatically when you assign the NetApp device to the agent for monitoring. You enable this +option on the NetApp FPolicy Configuration page of the Add New Host window. diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/activity/customizefpolicy.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/activity/customizefpolicy.md index 77843dad69..4d90aecbe9 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/activity/customizefpolicy.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/activity/customizefpolicy.md @@ -7,7 +7,7 @@ sidebar_position: 40 # Customize FPolicy Policy Name There may be situations when FPolicy needs to be named something other than StealthAUDIT. In those -cases it is necessary to manually add a parameter to the Activity Monitor agent’s `sbtfilemon.ini` +cases, manually add a parameter to the Activity Monitor agent’s `sbtfilemon.ini` file. After the monitoring agent has been deployed, follow the steps. **Step 1 –** Open to the `sbtfilemon.ini` file on the agent server in a text editor: diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/activity/enablehttp.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/activity/enablehttp.md index 2cdbc8a4ce..68937894ee 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/activity/enablehttp.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/activity/enablehttp.md @@ -6,9 +6,9 @@ sidebar_position: 20 # Enable HTTP or HTTPS -The Activity Monitor Activity Agent must be able to send ONTAPI calls to the vFiler’s data LIF over -HTTP or HTTPS. The following commands will enable the HTTP or HTTPS communication between the vFiler -and the Activity Monitor. +The Activity Monitor Activity Agent must be able to send ONTAP API (ONTAPI) calls to the vFiler’s +data Logical Interface (LIF) over HTTP or HTTPS. The following commands will enable the HTTP or +HTTPS communication between the vFiler and the Activity Monitor. Use the following command to enable HTTP: diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/activity/provisionactivity.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/activity/provisionactivity.md index 690a741a7c..4f6ce9549d 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/activity/provisionactivity.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/activity/provisionactivity.md @@ -16,10 +16,9 @@ Provisioning this account is a three part process: - Part 2: Create a Group & Assign Role - Part 3: Add User to Group -Relevant NetApp Documentation: To learn more about node access controls, please visit the NetApp -website and read the +Relevant NetApp Documentation: For information about node access controls, see the [na_useradmin – Administers node access controls](https://library.netapp.com/ecmdocs/ECMP1511537/html/man1/na_useradmin.1.html) -article. +article on the NetApp website. ## Part 1: Create Role with API/CLI Access @@ -74,7 +73,7 @@ After the role is created, complete Part 2: Create a Group & Assign Role. ## Part 2: Create a Group & Assign Role -Once the role has been created, it must be attached to a group. The following command needs to be +After the role is created, attach it to a group. The following command needs to be run to create a group and assign the role to it. ``` diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/overview.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/overview.md index a4d1cafe78..b98f737800 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/overview.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netapp7mode/overview.md @@ -116,7 +116,7 @@ are required for communication between the Agent server and the Netwrix Activity The Windows firewall rules need to be configured on the Windows server, which require certain inbound rules be created if the scans are running in applet mode. These scans operate over a default -port range, which cannot be specified via an inbound rule. For more information, see the Microsoft +port range, which can't be specified via an inbound rule. For more information, see the Microsoft [Connecting to WMI on a Remote Computer](https://msdn.microsoft.com/en-us/library/windows/desktop/aa389290(v=vs.85).aspx) article. @@ -140,7 +140,7 @@ Agent server and the target NetApp Data ONTAP 7-Mode device: Activity Monitor. :::note -If either HTTP or HTTPS are not enabled, the FPolicy on the NetApp Data ONTAP 7-Mode +If either HTTP or HTTPS aren't enabled, the FPolicy on the NetApp Data ONTAP 7-Mode device must be configured manually. Also, the External Engine will not reconnect automatically in the case of a server reboot or service restart. ::: diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/access/access.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/access/access.md index 435d7d4fc2..8f4e4b2624 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/access/access.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/access/access.md @@ -21,8 +21,8 @@ an alternative method. ### Configure Data LIF to Allow HTTPS Traffic -As of NetApp Clustered ONTAP 9.6, users can assign service policies (instead of LIF roles) to LIFs -that determine the kind of traffic that is supported for the LIFs. +As of NetApp Clustered ONTAP 9.6, users can assign service policies (instead of Logical Interface +(LIF) roles) to LIFs that determine the kind of traffic that is supported for the LIFs. - Starting with ONTAP 9.5, ONTAP supports service policies - Starting with ONTAP 9.6, LIF roles are deprecated and service policies are supported for all types @@ -72,8 +72,8 @@ Example: network interface modify -vserver testserver -lif lif_1 -service-policy new_service_policy ``` -A service policy can only be used by LIFs in the same SVM that is specified when creating the -service policy. +A service policy can only be used by LIFs in the same Storage Virtual Machine (SVM) that is +specified when creating the service policy. ## CIFS Method 2 Credential Configuration @@ -104,8 +104,8 @@ The following permissions are required: cifs users-and-groups local-group add-members ‑group-name "BUILTIN\Backup Operators" ‑member-names [DOMAIN_USER] ‑vserver [SVM_NAME] ``` -If an ACE does not already exist for a specific user/group on an SVM's c$ share, then it needs to be -added with the desired rights (No_access, Read, Change, or Full_Control). To check the current ACE +If an ACE doesn't already exist for a specific user/group on an SVM's c$ share, add one with the +rights you want (No_access, Read, Change, or Full_Control). To check the current ACE for a user or group on each SVM's c$ share, the following ONTAP CLI command should be used at the cluster management level. @@ -117,18 +117,17 @@ The output will list each SVM's ACL for its c$ share. For example: ![ONTAP CLI Command Output Example](/images/accessanalyzer/11.6/config/netappcmode/accesscifsmethod2.webp) -If the desired ACE does not exist on an SVM's c$ share, then one can be created with the following -command: +If the ACE you want doesn't exist on an SVM's c$ share, create one with the following command: ``` vserver cifs share access-control create -share c$ -user-or-group [USER_OR_GROUP_NAME] -permission Read -vserver [SVM_NAME] ``` -If an existing ACE needs to be modified, the following command should be used: +To modify an existing ACE, use the following command: :::warning -The following command will overwrite an existing ACE. For example, it is possible to -downgrade a user with Full_Control to Read, or vice versa. +The following command will overwrite an existing ACE. For example, you can +downgrade a user from Full_Control to Read, or the reverse. ::: @@ -137,19 +136,19 @@ vserver cifs share access-control modify -share c$ -user-or-group [USER_OR_GROUP ``` :::note -If users would prefer to avoid permissioning C$, then there is an alternative. Users can -instead give the SVM's Backup Operators group read-only access to each share to be scanned. +If you want to avoid permissioning C$, give the SVM's Backup Operators group read-only access to +each share you want to scan instead. ::: -In order to utilize Enterprise Auditor’s LAT Preservation (Last Access Time) feature during -sensitive data scans and metadata tag collection, applying ONTAP’s SeRestorePrivilege to the service -account is also required. +To use Enterprise Auditor’s LAT Preservation (Last Access Time) feature during +sensitive data scans and metadata tag collection, also apply ONTAP’s SeRestorePrivilege to the +service account. -As an alternative to membership in BUILTIN\Backup Operators, SeBackupPrivilege can be directly -applied to a user via the NetApp command line. +As an alternative to BUILTIN\Backup Operators membership, apply SeBackupPrivilege directly to a +user via the NetApp command line. -The following commands can be used to grant these permissions to the service account to be used for +Use the following commands to grant these permissions to the service account used for scanning by Enterprise Auditor. Use the following commands to add SeBackupPrivilege to the Service Account (or a BUILTIN Group): @@ -196,13 +195,13 @@ cifs share access-control show ‑vserver [SVM_NAME] ‑share c$ ## NFSv3 Credential Configuration -The following is a list of example commands that can be used to configure a NetApp export policy to +Use the following example commands to configure a NetApp export policy to scan a volume via NFSv3 using the Enterprise Auditor File System Solution. :::warning The export policy for a volume's parent (ex. the SVM's root volume), or the export policy for a qtree's parent, must have access rights that are equal or wider in scope to the export -policy for the target volume/qtree. If Enterprise Auditor cannot access all segments of a target +policy for the target volume/qtree. If Enterprise Auditor can't access all segments of a target volume/qtree's junction path, then NFS access will be denied. ::: @@ -259,7 +258,7 @@ volume modify ‑vserver testserver ‑volume testVolume ‑policy testNFS ### Troubleshooting NFSv3 Export Access If Enterprise Auditoris not discovering the expected NFS export, it is possible that the export -policy is not properly configured to allow the Enterprise Auditor server or proxy server IP Address +policy isn't properly configured to allow the Enterprise Auditor server or proxy server IP Address to mount the NFS export. One step in troubleshooting this issue is to confirm a Unix client (or WSL for Windows) in the same IP range as the Enterprise Auditor server or proxy server can mount the NFS export. diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/access/configureemptyfpolicy.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/access/configureemptyfpolicy.md index 372b98e3aa..2f75613fb7 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/access/configureemptyfpolicy.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/access/configureemptyfpolicy.md @@ -6,8 +6,8 @@ sidebar_position: 10 # Configure Empty FPolicy -The credential used to just run Access Auditing (FSAA) and/or Sensitive Data Discovery Auditing -scans requires access to the specified API calls as well as association to an FPolicy. Therefore, it +The credential used to run Access Auditing (FSAA) and/or Sensitive Data Discovery Auditing +scans requires access to the specified API calls and association with an FPolicy. Therefore, it is necessary to: - [Create Security Role for FSAA Scans](#create-security-role-for-fsaa-scans) @@ -95,14 +95,13 @@ Example: security login role show enterpriseauditor ``` -Relevant NetApp Documentation: To learn more about creating security login roles, please visit the -NetApp website and read the +Relevant NetApp Documentation: For information about creating security login roles, see the [security login role create](https://library.netapp.com/ecmdocs/ECMP1196817/html/security/login/role/create.html) -article. +article on the NetApp website. ## Create Security Login for FSAA Scans -Once the access control role has been created, apply it to a domain account. +After you create the access control role, apply it to a domain account. - The SVM used in the following command must be the same SVM used when creating the role. See the [Create Security Role for FSAA Scans](#create-security-role-for-fsaa-scans) topic for additional @@ -149,10 +148,9 @@ Verify that the output is displayed as follows: ![validatesecuritylogincreation](/images/activitymonitor/7.1/config/netappcmode/validatesecuritylogincreation.webp) -Relevant NetApp Documentation: To learn more about creating security logins, please visit the NetApp -website and read the +Relevant NetApp Documentation: For information about creating security logins, see the [security login create](https://library.netapp.com/ecmdocs/ECMP12452955/html/security/login/create.html) -article. +article on the NetApp website. ## Create External Engine for Empty FPolicy @@ -206,10 +204,9 @@ Verify that the output is displayed as follows: ![validateexternalenginecreation](/images/activitymonitor/7.1/config/netappcmode/validateexternalenginecreation.webp) -Relevant NetApp Documentation: To learn more about creating an external engine, please visit the -NetApp website and read the +Relevant NetApp Documentation: For information about creating an external engine, see the [vserver fpolicy policy external-engine create](https://library.netapp.com/ecmdocs/ECMP1366832/html/vserver/fpolicy/policy/external-engine/create.html) -article. +article on the NetApp website. ## Create FPolicy Event for Empty FPolicy @@ -254,14 +251,13 @@ Verify that the output is displayed as follows: ![validatefpolciyeventcreation](/images/accessanalyzer/11.6/config/netappcmode/validatefpolciyeventcreation.webp) -Relevant NetApp Documentation: To learn more about creating an event, please visit the NetApp -website and read the +Relevant NetApp Documentation: For information about creating an event, see the [vserver fpolicy policy event create](https://library.netapp.com/ecmdocs/ECMP1196817/html/vserver/fpolicy/policy/event/create.html) -article. +article on the NetApp website. ## Create Empty FPolicy Policy -The FPolicy policy associates the other three FPolicy components and allows for the designation of a +The FPolicy policy associates the other three FPolicy components and designates a privileged FPolicy user, or the account granted Security Login. IMPORTANT: @@ -308,10 +304,9 @@ fpolicy policy show ‑instance ![validatefpolicypolicycreation](/images/activitymonitor/7.1/config/netappcmode/validatefpolicypolicycreation.webp) -Relevant NetApp Documentation: To learn more about creating a policy, please visit the NetApp -website and read the +Relevant NetApp Documentation: For information about creating a policy, see the [vserver fpolicy policy create](https://library.netapp.com/ecmdocs/ECMP1366832/html/vserver/fpolicy/policy/create.html) -article. +article on the NetApp website. ## Create Empty FPolicy Scope @@ -320,9 +315,9 @@ The FPolicy scope creates the filters necessary to perform scans on specific sha IMPORTANT: - The SVM used must be the SVM hosting the CIFS shares. -- It is not necessary to specify both volumes and shares. One or the other is sufficient. +- It isn't necessary to specify both volumes and shares. One or the other is sufficient. -Use the following command to create the FPolicy scope by volume(s): +Use the following command to create the FPolicy scope by volumes: ``` vserver fpolicy policy scope create ‑vserver [SVM_NAME] ‑policy-name StealthAUDIT ‑volumes-to-include @@ -334,7 +329,7 @@ Example: vserver fpolicy policy scope create ‑vserver testserver ‑policy-name StealthAUDIT ‑volumes-to-include ``` -Use the following command to create the FPolicy scope by share(s): +Use the following command to create the FPolicy scope by shares: ``` vserver fpolicy policy scope create ‑vserver [SVM_NAME] ‑policy-name StealthAUDIT ‑shares-to-include @@ -358,14 +353,13 @@ fpolicy policy scope show ‑instance ![validatefpolicyscopecreation](/images/activitymonitor/7.1/config/netappcmode/validatefpolicyscopecreation.webp) -Relevant NetApp Documentation: To learn more about creating scope, please visit the NetApp website -and read the +Relevant NetApp Documentation: For information about creating scope, see the [vserver fpolicy policy scope create](https://library.netapp.com/ecmdocs/ECMP1196817/html/vserver/fpolicy/policy/scope/create.html) -article. +article on the NetApp website. ## Enable the Empty FPolicy -Once the empty FPolicy has been created, it must be enabled. +After you create the empty FPolicy, enable it. IMPORTANT: @@ -395,7 +389,6 @@ vserver fpolicy show ![validatefpolicyenabled](/images/activitymonitor/7.1/config/netappcmode/validatefpolicyenabled.webp) -Relevant NetApp Documentation: To learn more about enabling a policy, please visit the NetApp -website and read the +Relevant NetApp Documentation: For information about enabling a policy, see the [vserver fpolicy enable](https://library.netapp.com/ecmdocs/ECMP1196817/html/vserver/fpolicy/enable.html) -article. +article on the NetApp website. diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/activity/activity.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/activity/activity.md index 14c513620b..8eda5fe192 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/activity/activity.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/activity/activity.md @@ -6,7 +6,7 @@ sidebar_position: 20 # NetApp Data ONTAP Cluster-Mode Activity Auditing Configuration -The Activity Monitor agent employed to monitor NetApp leverages NetApp ONTAP API, and the NetApp +The Activity Monitor agent employed to monitor NetApp uses the NetApp ONTAP API and the NetApp FPolicy framework to monitor file system events. This includes both NetApp 7-Mode and Cluster-Mode configurations. For more information about FPolicy read the [What are the two parts of the FPolicy solution ](https://library.netapp.com/ecmdocs/ECMP1401220/html/GUID-54FE1A84-6CF0-447E-9AAE-F43B61CA2138.html) @@ -25,17 +25,17 @@ list of volumes, list of LIFs. Depending on the configuration, the agent can als of FPolicy to ensure it is enabled; configure FPolicy and register or unregister itself. The FPolicy framework enables the collection of audit events on the ONTAP side and their transfer to -the agent(s) via the designated Data LIFs. Each LIF establishes its own connection with one or +the agents via the designated Data LIFs. Each LIF establishes its own connection with one or several agents and sends notifications as soon as the file transaction occurs. The FPolicy connection is asynchronous and buffered; both ONTAP and Activity Monitor have techniques in place to -make sure that connections are alive and working. The connection can be secured using TLS with +ensure that connections are alive and working. The connection can be secured using TLS with server or mutual authentication. FPolicy may have a significant impact on file system throughput, and it is always a best practice to monitor performance when enabling FPolicy. :::info -Create a tailored FPolicy which only collects the desired activity from the +Create a tailored FPolicy which only collects the activity you want from the environment to limit the scope and impact. ::: @@ -43,12 +43,12 @@ environment to limit the scope and impact. For scale-out and fault tolerance purposes, the product supports a range of deployment options. A single agent can receive events from multiple SVMs. Or events from a single SVM can be distributed among multiple agents. Or a set of SVMs can distribute events among a set of agents. The choice -depends on the fault tolerance requirements and the expected event flow. As a rule of thumb, the -_average_ load on a single agent should not exceed 5000 events per second. +depends on the fault tolerance requirements and the expected event flow. In general, the +_average_ load on a single agent shouldn't exceed 5000 events per second. **Configuration Checklist** -Complete the following checklist prior to configuring the activity monitoring of NetApp Data ONTAP +Complete the following checklist before configuring the activity monitoring of NetApp Data ONTAP Cluster-Mode devices. Instructions for each item of the checklist are detailed within the following sections. @@ -56,10 +56,10 @@ sections. - Gather the following information: - - Names of the SVM(s) to be monitored + - Names of the SVMs to be monitored - FPolicy is configured for each SVM separately - - This should be the SVM(s) hosting the CIFS or NFS shares(s) to be monitored + - This should be the SVMs hosting the CIFS or NFS sharess to be monitored - Credentials to access ONTAP to provision a role and account. - Desired functionality level: @@ -80,7 +80,7 @@ sections. - Limiting the FPolicy to specific file operations is an effective way to limit the performance impact of FPolicy - - IP Address of the server(s) where the Activity Monitor Agent is deployed + - IP Address of the servers where the Activity Monitor Agent is deployed - API enabled in ONTAP: the classic ONTAPI/ZAPI or the new REST API - The product supports the REST API for ONTAP 9.13.1 and above. diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/activity/configurefirewall.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/activity/configurefirewall.md index 50b58da056..56c4003976 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/activity/configurefirewall.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/activity/configurefirewall.md @@ -30,11 +30,11 @@ Monitor. Both classic ONTAPI/ZAPI and the new REST API are supported. Starting with ONTAP 9.13.1, the product uses REST API by default if it is available. HTTP and HTTPS protocols are supported. For HTTPS, two -modes are supported: strict and ignore errors. For the strict mode, the product allows you to -disable the host name validation in case the agent cannot resolve the FQDN of the LIF. +modes are supported: strict and ignore errors. With strict mode, you can +disable the host name validation in case the agent can't resolve the FQDN of the LIF. Enabling the API access varies depending on ONTAP version. The following sections list common steps -on enabling the API access. Please refer to the NetApp documentation for more details. +on enabling the API access. refer to the NetApp documentation for more details. ### Management-http Service @@ -74,7 +74,7 @@ network interface service-policy add-service -service management-https -policy d ### Firewall Policy -For ONTAP 9.5 and older, the following commands can be used to either create a new firewall policy +For ONTAP 9.5 and older, use the following commands to either create a new firewall policy or modify an existing policy if ONTAPI is blocked. #### Create New Firewall HTTP Policy @@ -148,15 +148,15 @@ Verify that the output is displayed as follows: ## FPolicy The FPolicy framework enables the collection of audit events on the ONTAP side and their transfer to -the agent(s) via the designated Data LIFs. Each LIF establishes its own connection with one or +the agents via the designated Data LIFs. Each LIF establishes its own connection with one or several agents and sends notifications as soon as the file transaction occurs. The FPolicy connection is asynchronous and buffered; both ONTAP and Activity Monitor have techniques in place to -make sure that connections are alive and working. The connection can be secured using TLS with +ensure that connections are alive and working. The connection can be secured using TLS with server or mutual authentication. ONTAP cluster nodes connect to the agent on port 9999 by default. The port can be changed in the -agent's settings. The agent adds this port to Windows Firewall exclusions automatically. Please -ensure the port is not blocked by other firewalls between ONTAP and the agent. +agent's settings. The agent adds this port to Windows Firewall exclusions automatically. Ensure +the port isn't blocked by other firewalls between ONTAP and the agent. ### Data-fpolicy-client Service diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/activity/configurefpolicy.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/activity/configurefpolicy.md index 853640604c..e10e9bc001 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/activity/configurefpolicy.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/activity/configurefpolicy.md @@ -13,11 +13,11 @@ There are two ways to configure FPolicy: - Activity Monitor agent can facilitate the [Automatic Configuration of FPolicy](#automatic-configuration-of-fpolicy) for the monitored SVM - using the ONTAP API. This mode is simple, but does not allow you to exclude certain volumes or + using the ONTAP API. This mode is simple, but it doesn't let you exclude certain volumes or shares of the SVM from being monitored. It also requires additional permissions to create and modify FPolicy. -- Another option is to [Manually Configure FPolicy](#manually-configure-fpolicy) for each SVM. This - mode allows you to fine tune FPolicy by excluding certain volumes or shares from being monitored. +- Another option is to [Manually Configure FPolicy](#manually-configure-fpolicy) for each SVM. With + this mode, you can fine-tune FPolicy by excluding certain volumes or shares from being monitored. It also reduces product permissions. Regardless of the chosen approach for FPolicy configuration, one also needs to perform extra steps @@ -55,8 +55,8 @@ A certificate (Server Certificate) for the Agent server needs to be generated an file. This is required for both of the TLS authentication options. The PEM file must contain both Public Key and Private Key parts. A certificate may be self-signed or -issued by a certification authority. Below are the steps for generation of a self-signed certificate -using OpenSSL toolkit. +issued by a certification authority. The following steps generate a self-signed certificate +using the OpenSSL toolkit. Use the following command on the agent server to create the Server Certificate and copy it to a .pem file: @@ -88,8 +88,8 @@ locally on the Activity Monitor Console server. ### Create PEM File for Client Certificate A certificate (Client Certificate) for the SVM needs to be copied to a PEM file. This is required -for the TLS, mutual authentication option. Follow the steps to create the PEM file for the Client -Certificate. +for the TLS, mutual authentication option. Complete the following steps to create the PEM file for +the Client Certificate. **Step 1 –** On the SVM , use the following command to show the security certificate details: @@ -105,7 +105,7 @@ security certificate show -vserver testserver -type server instance **Step 2 –** Copy the security certificate details into a text file and copy the public key to a PEM file. The following variables from security details will be needed to set mutual-authentication -during Part 6 of manual configuration and prior to automatic configuration: +during Part 6 of manual configuration and before automatic configuration: - SVM - Common Name @@ -120,8 +120,8 @@ The Client Certificate PEM file has been created. ## Manually Configure FPolicy This section describes how to manually configure FPolicy. Manual configuration of the FPolicy is -recommended if the policy needs to be scoped to monitor select volumes or shares. It is necessary to -create several FPolicy components and then enable the FPolicy. See the sections corresponding to +recommended if the policy needs to be scoped to monitor select volumes or shares. Create several +FPolicy components and then enable the FPolicy. See the sections corresponding to each part of this list: - Part 1: Install Server Certificate on the SVM (only if using TLS authentication) @@ -135,12 +135,12 @@ each part of this list: - Part 3: Create FPolicy Events - - An FPolicy event defines which protocol(s) to monitor and which file access events to monitor. + - An FPolicy event defines which protocols to monitor and which file access events to monitor. - Part 4: Create FPolicy Policy - - The FPolicy policy associates the other three FPolicy components and allows for the - designation of a privileged FPolicy user + - The FPolicy policy associates the other three FPolicy components and designates a + privileged FPolicy user - If running the Access Auditing (FSAA), Activity Auditing (FSAC), and/or Sensitive Data Discovery Auditing scans, then this is the user account credential to be added to the Enterprise Auditor Connection Profile. @@ -156,7 +156,7 @@ each part of this list: - Part 7: Enable the FPolicy - - Once the FPolicy is enabled, the Activity Monitor Agent can be configured to monitor the SVM. + - After the FPolicy is enabled, the Activity Monitor Agent can be configured to monitor the SVM. - Part 8: Connect FPolicy Server / Agent to Cluster Node (optional) @@ -165,7 +165,7 @@ each part of this list: ### Part 1: Install Server Certificate on the SVM -If using the TLS authentication options, it is necessary to install the Server Certificate on the +If using the TLS authentication options, install the Server Certificate on the SVM. Use the following command to install the Server Certificate: @@ -212,7 +212,7 @@ IMPORTANT: - The following values are required: - `engine-name StealthAUDITEngine`, the names of the external engine object can be customized - (see below). + (see [Customization of FPolicy Object Names](#customization-of-fpolicy-object-names)). - `port 9999`, Port number can be customized, but it is recommended to use 9999. - `extern-engine-type asynchronous` - `ssl-option no-auth` @@ -249,10 +249,9 @@ Verify that the output is displayed as follows: ![Output Displayed](/images/activitymonitor/7.1/config/netappcmode/validateexternalenginecreation.webp) -Relevant NetApp Documentation: To learn more about creating an external engine, please visit the -NetApp website and read the +Relevant NetApp Documentation: For information about creating an external engine, see the [vserver fpolicy policy external-engine create](https://docs.netapp.com/us-en/ontap-cli-9141/vserver-fpolicy-policy-external-engine-create.html) -article. +article on the NetApp website. ### Part 3: Create FPolicy Event @@ -262,7 +261,7 @@ IMPORTANT: - The SVM used must be the SVM hosting the CIFS or NFS shares to be monitored. - Enterprise Auditor and the Activity Monitor are capable of monitoring both NFS and CIFS. However, - it is necessary to create separate events for each protocol. + you must create separate events for each protocol. - The following values are required: - `event-name` @@ -281,8 +280,8 @@ IMPORTANT: reported. - Limiting the file operations to be monitored is an excellent way to limit the performance impact - the FPolicy will have on the NetApp device. The file operations from which to choose are below - with additional filter options: + the FPolicy will have on the NetApp device. Choose from the following file operations, with + additional filter options: - `create` – File create operations - `create_dir` – Directory create operations @@ -308,7 +307,7 @@ IMPORTANT: - `read` – File read operations - `first-read` – Limits notification to only first read operations for CIFS protocol. For - ONTAP 9.2+, this filter can be used for both CIFS and NFS protocols. + ONTAP 9.2+, you can use this filter for both CIFS and NFS protocols. - `rename`– File rename operations - `rename_dir`– Directory rename operations @@ -340,7 +339,7 @@ IMPORTANT: - `write` – File write operations - `first-write` – Limits notification to only first write operations for CIFS protocol. For - ONTAP 9.2+, this filter can be used for both CIFS and NFS protocols. + ONTAP 9.2+, you can use this filter for both CIFS and NFS protocols. - For failed/denied events, the list of supported file operations is limited to the following values: @@ -410,14 +409,13 @@ Verify that the output is displayed as follows: ![Output Displayed](/images/activitymonitor/7.1/config/netappcmode/fpolicyeventcreation.webp) -Relevant NetApp Documentation: To learn more about creating an event, please visit the NetApp -website and read the +Relevant NetApp Documentation: For information about creating an event, see the [vserver fpolicy policy event create](https://docs.netapp.com/us-en/ontap-cli-9141/vserver-fpolicy-policy-event-create.html) -article. +article on the NetApp website. ### Part 4: Create FPolicy Policy -The FPolicy policy associates the other three FPolicy components and allows for the designation of a +The FPolicy policy associates the other three FPolicy components and designates a privileged FPolicy user, or the provisioned FPolicy account. If running the Access Auditing (FSAA), Activity Auditing (FSAC), and/or Sensitive Data Discovery Auditing scans in Enterprise Auditor, then this is also the user account credential to be added to the Enterprise Auditor Connection Profile. @@ -490,10 +488,9 @@ fpolicy policy show -instance ![Output Displayed](/images/activitymonitor/7.1/config/netappcmode/validatefpolicypolicycreation.webp) -Relevant NetApp Documentation: To learn more about creating a policy, please visit the NetApp -website and read the +Relevant NetApp Documentation: For information about creating a policy, see the [vserver fpolicy policy create](https://docs.netapp.com/us-en/ontap-cli-9141/vserver-fpolicy-policy-create.html) -article. +article on the NetApp website. ### Part 5: Create FPolicy Scope @@ -504,10 +501,10 @@ variable [SVM_NAME] in the command with an asterisk (\*). IMPORTANT: - The SVM used must be the SVM hosting the CIFS or NFS shares to be monitored. -- It is not necessary to specify both volumes and shares. One or the other is sufficient. +- It isn't necessary to specify both volumes and shares. One or the other is sufficient. - If you want to monitor everything, set the "`volumes-to-include`" value to "`*`". -Use the following command to create the FPolicy scope by specifying volume(s): +Use the following command to create the FPolicy scope by specifying volumes: ``` vserver fpolicy policy scope create -vserver [SVM_NAME] -policy-name StealthAUDIT -volumes-to-include [VOLUME_NAME],[VOLUME_NAME] @@ -519,7 +516,7 @@ Example: vserver fpolicy policy scope create -vserver testserver -policy-name StealthAUDIT -volumes-to-include samplevolume1,samplevolume2 ``` -Use the following command to create the FPolicy scope by specifying share(s): +Use the following command to create the FPolicy scope by specifying shares: ``` vserver fpolicy policy scope create -vserver [SVM_NAME] -policy-name StealthAUDIT -shares-to-include [SHARE_NAME],[SHARE_NAME] @@ -541,14 +538,13 @@ fpolicy policy scope show -instance ![Output Displayed](/images/activitymonitor/7.1/config/netappcmode/validatefpolicyscopecreation.webp) -Relevant NetApp Documentation: To learn more about creating scope, please visit the NetApp website -and read the +Relevant NetApp Documentation: For information about creating scope, see the [vserver fpolicy policy scope create](https://docs.netapp.com/us-en/ontap-cli-9141/vserver-fpolicy-policy-scope-create.html) -article. +article on the NetApp website. ### Part 6: Set TLS Authentication -If using the TLS authentication options, it is necessary to set authentication for the type of +If using the TLS authentication options, set authentication for the type of authentication. #### Set Server-Authentication @@ -617,10 +613,9 @@ vserver fpolicy show ![Output Displayed](/images/activitymonitor/7.1/config/netappcmode/validatefpolicyenabled.webp) -Relevant NetApp Documentation: To learn more about enabling a policy, please visit the NetApp -website and read the +Relevant NetApp Documentation: For information about enabling a policy, see the [vserver fpolicy enable](https://docs.netapp.com/us-en/ontap-cli-9121//vserver-fpolicy-enable.html) -article. +article on the NetApp website. ### Part 8: Connect FPolicy Server / Agent to Cluster Node @@ -663,7 +658,7 @@ will also be necessary to set mutual authentication on the SVM. ### Set TLS Mutual-Authentication -If using the TLS, mutual authentication options, it is necessary to set authentication. +If using the TLS, mutual authentication options, set authentication. Use the following command to set mutual-authentication: @@ -702,6 +697,6 @@ These names can be customized in the monitored host's settings in the Activity M useful in two scenarios: - You want the names to match the company policies; -- You want to configure FPolicy manually using your custom names, but also want to leverage the +- You want to configure FPolicy manually using your custom names, but also want to use the "Enable and Connect FPolicy" feature of the Activity Monitor, so that the product ensures that FPolicy stays enabled and connected at all times. diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/activity/provisionactivity.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/activity/provisionactivity.md index 1246f12520..da5f1db4d5 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/activity/provisionactivity.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/activity/provisionactivity.md @@ -26,13 +26,13 @@ The permissions needed depends on the functionality level: - Least Privileged: ONLY Collect Events – This is the minimal functionality level. A user manually configures FPolicy and ensures that it stays enabled and connected. The product only collects - events. This functionality level is not recommended as it requires an additional solution that + events. This functionality level isn't recommended as it requires an additional solution that tracks the state of FPolicy and fixes the problem should ONTAP disconnect or should the policy become disabled. - **_RECOMMENDED:_** Less Privileged: Enable/Connect Policy & Collect Events – With this level, the user still performs the initial FPolicy configuration manually. The product tracks the state of FPolicy with periodic checks to ensure it stays enabled and connected all the time. -- **_RECOMMENDED:_** Automatically Configure the FPolicy – With this full-blown level, no manual +- **_RECOMMENDED:_** Automatically Configure the FPolicy – With this comprehensive level, no manual configuration is needed. The product performs the initial FPolicy configuration; updates FPolicy to reflect configuration changes; ensures that FPolicy stays enabled and connected all the time. @@ -105,7 +105,7 @@ security login rest-role create -role enterpriseauditorrest -api "/api/svm/svms" ``` :::note -If the FPolicy account is configured with these permissions, it is necessary to manually +If the FPolicy account is configured with these permissions, you must manually configure the FPolicy. See the [Configure FPolicy](/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/activity/configurefpolicy.md) topic for additional information. @@ -130,7 +130,7 @@ permissions to collect events: :::tip Remember, this permission permits the Activity Monitor to enable the FPolicy. If the “Enable - and connect FPolicy” option is employed but the permission is not provided, the agent will + and connect FPolicy” option is employed but the permission isn't provided, the agent will encounter “Failed to enable policy” errors, but it will still be able to connect to the FPolicy. Since this permission model requires a manual configuration of the FPolicy, then the need to manually enable the FPolicy will be met. @@ -195,7 +195,7 @@ security login rest-role create -role enterpriseauditorrest -api "/api/protocols ``` :::note -If the FPolicy account is configured with these permissions, it is necessary to manually +If the FPolicy account is configured with these permissions, you must manually configure the FPolicy. See the [Configure FPolicy](/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/activity/configurefpolicy.md) topic for additional information. @@ -345,7 +345,7 @@ article. ## Part 2: Create Security Login -Once the access control role has been created, apply it to a domain account. Ensure the following +After the access control role is created, apply it to a domain account. Ensure the following requirements are met: - The SVM used in the following command must be the same SVM used when creating the access control diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/overview.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/overview.md index 3812c4f488..947df26c89 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/overview.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/netappcmode/overview.md @@ -133,7 +133,7 @@ are required for communication between the Agent server and the Netwrix Activity The Windows firewall rules need to be configured on the Windows server, which require certain inbound rules be created if the scans are running in applet mode. These scans operate over a default -port range, which cannot be specified via an inbound rule. For more information, see the Microsoft +port range, which can't be specified via an inbound rule. For more information, see the Microsoft [Connecting to WMI on a Remote Computer](https://msdn.microsoft.com/en-us/library/windows/desktop/aa389290(v=vs.85).aspx) article. @@ -152,7 +152,7 @@ Agent server and the target NetApp Data ONTAP Cluster-Mode device: Activity Monitor. :::note -If either HTTP or HTTPS are not enabled, the FPolicy on the NetApp Data ONTAP 7-Mode +If either HTTP or HTTPS aren't enabled, the FPolicy on the NetApp Data ONTAP 7-Mode device must be configured manually. Also, the External Engine will not reconnect automatically in the case of a server reboot or service restart. ::: diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/nutanix/access.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/nutanix/access.md index 5d9cdcdf81..a616baf183 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/nutanix/access.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/nutanix/access.md @@ -11,7 +11,7 @@ Admin: Backup Access only** role assigned. ## Nutanix Prism Central Interface -Follow the steps to configure the required account in the Nutanix Prism Central Interface. +Complete the following steps to configure the required account in the Nutanix Prism Central Interface. **Step 1 –** Select the **Home** dropdown and select **File Server**. diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/nutanix/overview.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/nutanix/overview.md index 1445c90d3c..ff57e89047 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/nutanix/overview.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/nutanix/overview.md @@ -55,7 +55,7 @@ are required for communication between the Agent server and the Netwrix Activity The Windows firewall rules need to be configured on the Windows server, which require certain inbound rules be created if the scans are running in applet mode. These scans operate over a default -port range, which cannot be specified via an inbound rule. For more information, see the Microsoft +port range, which can't be specified via an inbound rule. For more information, see the Microsoft [Connecting to WMI on a Remote Computer](https://msdn.microsoft.com/en-us/library/windows/desktop/aa389290(v=vs.85).aspx) article. diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/qumulo/activity.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/qumulo/activity.md index 9dedbfce85..d2463930ff 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/qumulo/activity.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/qumulo/activity.md @@ -32,7 +32,7 @@ advanced filtering of Microsoft Office activity also requires the JSON format. The JSON format for audit events was introduced in Qumulo Core 6.0.1. The new format can be enabled via an SSH session to the Qumulo cluster. -Follow the steps to verify that audit event format and change the format, if needed. +Complete the following steps to verify the audit event format and change it, if needed. **Step 1 –** Connect to the Qumulo cluster with SSH. diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/qumulo/overview.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/qumulo/overview.md index 909948f96b..f1b192625e 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/qumulo/overview.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/qumulo/overview.md @@ -52,7 +52,7 @@ are required for communication between the Agent server and the Netwrix Activity The Windows firewall rules need to be configured on the Windows server, which require certain inbound rules be created if the scans are running in applet mode. These scans operate over a default -port range, which cannot be specified via an inbound rule. For more information, see the Microsoft +port range, which can't be specified via an inbound rule. For more information, see the Microsoft [Connecting to WMI on a Remote Computer](https://msdn.microsoft.com/en-us/library/windows/desktop/aa389290(v=vs.85).aspx) article. diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/windowsfile/access.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/windowsfile/access.md index 64f9611994..a9c8f3c3a3 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/windowsfile/access.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/windowsfile/access.md @@ -17,7 +17,7 @@ Namespaces. ## Windows File System (Standard) -Configure the credential(s) with the following rights on the Windows host(s): +Configure the credentials with the following rights on the Windows hosts: - Granted the "Network access: Restrict clients allowed to make remote calls to SAM" Local Policies > Security Options privilege - Granted the “Backup files and directories” local policy privilege @@ -30,11 +30,11 @@ Configure the credential(s) with the following rights on the Windows host(s): - Local Administrators - Granted the “Log on as a batch” privilege - Remote Registry service must be enabled on the host where the applet is deployed (Applet or Proxy w/ Applet scans) to determine the system platform and where to deploy the applet. - - The local policy, “Network access: Do not allow storage of passwords and credentials for network authentication” must be disabled in order for the applet to start. - - Sensitive Data Discovery Auditing scans require .NET Framework 4.7.2 or later to be installed on the server where the applet is to be deployed in order for Sensitive Data Discovery collections to successfully occur. + - The local policy, “Network access: Don't allow storage of passwords and credentials for network authentication” must be disabled for the applet to start. + - Sensitive Data Discovery Auditing scans require .NET Framework 4.7.2 or later on the server where the applet is deployed, for Sensitive Data Discovery collections to succeed. :::note -In order to collect data on administrative shares and local policies (logon policies) for a Windows target, the credential must have group membership in the local Administrators group. +to collect data on administrative shares and local policies (logon policies) for a Windows target, the credential must have group membership in the local Administrators group. ::: ## Windows File System Clusters @@ -43,7 +43,7 @@ The permissions necessary to collect file system data from a Windows File System for all nodes that comprise the cluster. :::note -It is necessary to target the Windows Cluster File Server Role Server (name clients connect to) of interest when running a File System scan against a Windows File System Cluster. +Target the Windows Cluster File Server Role Server (name clients connect to) of interest when running a File System scan against a Windows File System Cluster. ::: Configure credentials on all cluster nodes according to the Windows File System (Standard) permissions, with the following additional requirements: @@ -54,7 +54,7 @@ Configure credentials on all cluster nodes according to the Windows File System ### Host List Considerations -It is necessary to target the Windows File Server Cluster (name of the cluster) of interest when running a File System scan against a Windows File System Cluster. Within the Master Host Table, there should be a host entry for the cluster as well as for each node. Additionally, each of these host entries must have the name of the cluster in the `WinCluster` column in the host inventory data. This may need to be updated manually. +Target the Windows File Server Cluster (name of the cluster) of interest when running a File System scan against a Windows File System Cluster. Within the Master Host Table, there should be a host entry for the cluster as well as for each node. Additionally, each of these host entries must have the name of the cluster in the `WinCluster` column in the host inventory data. This may need to be updated manually. See the View/Edit section of the [Host Management Activities](https://docs.netwrix.com/docs/accessanalyzer/11_6/admin/hostmanagement/actions/overview) topic for additional information on host inventory. @@ -62,7 +62,7 @@ See the View/Edit section of the [Host Management Activities](https://docs.netwr The host targeted by the File System scans is only the host entry for the cluster. For example: -The environment has a Windows File System Cluster named `ExampleCluster1` with three nodes named `ExampleNodeA`, `ExampleNodeB`, and `ExampleNodeC`. There would be four host entries in the Access Analyzer Master Host Table: `ExampleCluster1`, `ExampleNodeA`, `ExampleNodeB`, and `ExampleNodeC`. Each of these four entries would have the same value of the cluster name in the `WinCluster` column: `ExampleCluster1`. An additional entry containing the File Server Role Server name(s) should also be added, including the WinCluster name of the nodes. **This File Server Role Server name will be our target host.** +The environment has a Windows File System Cluster named `ExampleCluster1` with three nodes named `ExampleNodeA`, `ExampleNodeB`, and `ExampleNodeC`. There would be four host entries in the Access Analyzer Master Host Table: `ExampleCluster1`, `ExampleNodeA`, `ExampleNodeB`, and `ExampleNodeC`. Each of these four entries would have the same value of the cluster name in the `WinCluster` column: `ExampleCluster1`. An additional entry containing the File Server Role Server names should also be added, including the WinCluster name of the nodes. **This File Server Role Server name is the target host.** ### Least Privilege Permission Model for Windows Clusters @@ -84,7 +84,7 @@ comprise the cluster: The FileSystem > 0.Collection > 0-FSDFS System Scans Job is configured by default to target the default domain controller for the domain in which Access Analyzer resides. This is the appropriate target host for this job when targeting a domain-based namespace. To target a standalone namespace -or multiple namespaces, create a custom host list of the server(s) hosting the namespace(s). Then +or multiple namespaces, create a custom host list of the servers hosting the namespaces. Then assign the custom host list to the 0-FSDFS System Scans Job. No additional host list is require for the FileSystem > 0.Collection Job Group unless additional file servers are also being targeted. diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/windowsfile/activity.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/windowsfile/activity.md index fedf4acdee..6bb24d0c01 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/windowsfile/activity.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/windowsfile/activity.md @@ -6,11 +6,11 @@ sidebar_position: 20 # Windows File Server Activity Auditing Configuration -In order for Netwrix Access Analyzer to collect and store Windows file server activity, an activity monitor agent for Netwrix Activity Monitor must be deployed to the server and monitoring. See the [Single Activity Agent Deployment](https://docs.netwrix.com/docs/activitymonitor/9_0/admin/agents/overview) topic for additional information. +For Netwrix Access Analyzer to collect and store Windows file server activity, an activity monitor agent for Netwrix Activity Monitor must be deployed to the server and monitoring. See the [Single Activity Agent Deployment](https://docs.netwrix.com/docs/activitymonitor/9_0/admin/agents/overview) topic for additional information. ## Windows File System (Standard) -Configure the credential(s) with the following rights on the Windows host(s): +Configure the credentials with the following rights on the Windows hosts: - For **Local** or **Proxy as a Service Mode** Scans: - Group membership in both of the following local groups: @@ -21,7 +21,7 @@ Configure the credential(s) with the following rights on the Windows host(s): - Local Administrators - Granted the “Log on as a batch” privilege - Remote Registry service must be enabled on the host where the applet is deployed (Applet or Proxy w/ Applet scans) to determine the system platform and where to deploy the applet. - - The local policy, “Network access: Do not allow storage of passwords and credentials for network authentication” must be disabled in order for the applet to start. + - The local policy, “Network access: Don't allow storage of passwords and credentials for network authentication” must be disabled for the applet to start. - Granted the "Network access: Restrict clients allowed to make remote calls to SAM" Local Policies > Security Options privilege - Granted the “Backup files and directories” local policy privilege - The service account in the credential profile requires access to the admin share (e.g. `C$`) where the `sbtfilemon.ini` file exists @@ -29,10 +29,10 @@ Configure the credential(s) with the following rights on the Windows host(s): ## Windows File System Clusters -In order to monitor a Windows File System Cluster, an Activity Agent needs to be deployed on all nodes that comprise the Windows File System Cluster. +to monitor a Windows File System Cluster, an Activity Agent needs to be deployed on all nodes that comprise the Windows File System Cluster. :::note -It is necessary to target the Windows Cluster File Server Role Server (name clients connect to) when running a File System scan against a Windows File System Cluster. +Target the Windows Cluster File Server Role Server (name clients connect to) when running a File System scan against a Windows File System Cluster. ::: Configure credentials according to the Windows File System (Standard) permissions on all cluster nodes that comprise the cluster, with the following additional requirements: @@ -43,7 +43,7 @@ Configure credentials according to the Windows File System (Standard) permission ### Host List Considerations -It is necessary to target the Windows File Server Cluster (name of the cluster) of interest when running a File System scan against a Windows File System Cluster. Within the Master Host Table, there should be a host entry for the cluster as well as for each node. Additionally, each of these host entries must have the name of the cluster in the `WinCluster` column in the host inventory data. This may need to be updated manually. +Target the Windows File Server Cluster (name of the cluster) of interest when running a File System scan against a Windows File System Cluster. Within the Master Host Table, there should be a host entry for the cluster as well as for each node. Additionally, each of these host entries must have the name of the cluster in the `WinCluster` column in the host inventory data. This may need to be updated manually. See the View/Edit section of the [Host Management Activities](https://docs.netwrix.com/docs/accessanalyzer/11_6/admin/hostmanagement/actions/overview) topic for additional information on host inventory. @@ -53,7 +53,7 @@ The host targeted by the File System scans is only the host entry for the cluste :::note Example: -The environment has a Windows File System Cluster named `ExampleCluster1` with three nodes named `ExampleNodeA`, `ExampleNodeB`, and `ExampleNodeC`. There would be four host entries in the Access Analyzer Master Host Table: `ExampleCluster1`, `ExampleNodeA`, `ExampleNodeB`, and `ExampleNodeC`. Each of these four entries would have the same value of the cluster name in the `WinCluster` column: `ExampleCluster1`. An additional entry containing the File Server Role Server name(s) should also be added, including the WinCluster name of the nodes. This File Server Role Server name will be our target host. +The environment has a Windows File System Cluster named `ExampleCluster1` with three nodes named `ExampleNodeA`, `ExampleNodeB`, and `ExampleNodeC`. There would be four host entries in the Access Analyzer Master Host Table: `ExampleCluster1`, `ExampleNodeA`, `ExampleNodeB`, and `ExampleNodeC`. Each of these four entries would have the same value of the cluster name in the `WinCluster` column: `ExampleCluster1`. An additional entry containing the File Server Role Server names should also be added, including the WinCluster name of the nodes. This File Server Role Server name is the target host. ::: ### Host Mapping diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/windowsfile/overview.md b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/windowsfile/overview.md index 213e9d4458..4253a9658f 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/windowsfile/overview.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/windowsfile/overview.md @@ -61,7 +61,7 @@ are required for communication between the Agent server and the Netwrix Activity The Windows firewall rules need to be configured on the Windows server, which require certain inbound rules be created if the scans are running in applet mode. These scans operate over a default -port range, which cannot be specified via an inbound rule. For more information, see the Microsoft +port range, which can't be specified via an inbound rule. For more information, see the Microsoft [Connecting to WMI on a Remote Computer](https://msdn.microsoft.com/en-us/library/windows/desktop/aa389290(v=vs.85).aspx) article. diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/appletmodescans/appletmodepermissions.md b/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/appletmodescans/appletmodepermissions.md index 3d85f230e9..7a19571262 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/appletmodescans/appletmodepermissions.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/appletmodescans/appletmodepermissions.md @@ -6,13 +6,13 @@ sidebar_position: 10 # Applet Mode Permissions -When File System scans are run in applet mode, it means the File System applet is deployed to the target host when the job is executed to conduct data collection. However, the applet can only be deployed to a server with a Windows operating system. The data is collected on the Windows target host where the applet is deployed. The final step in data collection is to compress and transfer the data collected in the SQLite database(s), or Tier 2 database(s), back to the Access Analyzer Console server. If the target host is a NAS device, the File System scans will default to local mode for that host. +When File System scans are run in applet mode, it means the File System applet is deployed to the target host when the job is executed to conduct data collection. However, the applet can only be deployed to a server with a Windows operating system. The data is collected on the Windows target host where the applet is deployed. The final step in data collection is to compress and transfer the data collected in the SQLite databases, or Tier 2 databases, back to the Access Analyzer Console server. If the target host is a NAS device, the File System scans will default to local mode for that host. Additionally, the credential must have `WRITE` access to the `…\StealthAUDIT\FSAA` folder in the installation directory on the target host/proxy server as well as on the Access Analyzer Console server. This is required by either the user account running the Access Analyzer application, when manually executing jobs within the console, or the Schedule Service Account assigned within Access Analyzer, when running jobs as a scheduled tasks. -Sensitive Data Discovery Auditing scans require .NET Framework 4.7.2 or later to be installed on the server where the applet is to be deployed in order for Sensitive Data Discovery collections to successfully occur. +Sensitive Data Discovery Auditing scans require .NET Framework 4.7.2 or later on the server where the applet is deployed, for Sensitive Data Discovery collections to succeed. :::tip Remember, Remote Registry Service must be enabled on the host where the applet is deployed (for @@ -21,8 +21,8 @@ the applet. ::: :::warning -The local policy, “Network access: Do not allow storage of passwords and credentials -for network authentication” must be disabled in order for the applet to start. +The local policy, “Network access: Don't allow storage of passwords and credentials +for network authentication” must be disabled for the applet to start. ::: See the [Applet Mode Port Requirements](https://docs.netwrix.com/docs/accessanalyzer/12_0/requirements/filesystem/scanoptions/applet-mode-scans/appletmodeports) topic for firewall rule information. @@ -37,7 +37,7 @@ By default, the Applet will run as the connection profile account unless an addi The account used in the connection profile associated with the File System scan jobs, should have the appropriate permissions required to access the target host. See the [File System Supported Platforms](https://docs.netwrix.com/docs/accessanalyzer/11_6/requirements/filesystem/filesystems/) page for specific requirements per target file system. -## How do I determine if I’m using Applet Mode scanning? +## Determine whether you're using Applet Mode scanning The best way to verify if you’re using Applet Mode scanning is via the FSAA Data Collector Query Settings > [Scan Server Selection](https://docs.netwrix.com/docs/accessanalyzer/11_6/admin/datacollector/fsaa/scanserverselection) page: diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/appletmodescans/appletmodeports.md b/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/appletmodescans/appletmodeports.md index d2d362b931..62656bed67 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/appletmodescans/appletmodeports.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/appletmodescans/appletmodeports.md @@ -6,7 +6,7 @@ sidebar_position: 20 # Applet Mode Port Requirements -The following are the firewall settings are required when executing the Access Auditing (FSAA) +The following firewall settings are required when executing the Access Auditing (FSAA) and/or Sensitive Data Discovery Auditing scans in applet mode for communication between Enterprise Auditor and the host: diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/localmodescans/localmodepermissions.md b/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/localmodescans/localmodepermissions.md index 4c6bcba5b4..3bac7da5f8 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/localmodescans/localmodepermissions.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/localmodescans/localmodepermissions.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Local Mode Permissions -When File System scans are run in local mode, it means all of the data collection processing is conducted by the Access Analyzer Console server across the network. The data is collected in the SQLite database(s), or Tier 2 database(s), on the Access Analyzer Console server, and then imported into the Access Analyzer database, or Tier 1 database, on the SQL Server. +When File System scans are run in local mode, it means all of the data collection processing is conducted by the Access Analyzer Console server across the network. The data is collected in the SQLite databases, or Tier 2 databases, on the Access Analyzer Console server, and then imported into the Access Analyzer database, or Tier 1 database, on the SQL Server. The account used to run either a manual execution or a scheduled execution of the File System scans, must have the following permissions on the Access Analyzer Console server: @@ -19,7 +19,7 @@ The account used to run either a manual execution or a scheduled execution of th Additionally, the credential must have `WRITE` access to the `…\StealthAUDIT\FSAA` folder in the installation directory on the Access Analyzer Console server. This is required by either the user account running the Access Analyzer application, when manually executing jobs within the console, or the Schedule Service Account assigned within Access Analyzer, when running jobs as a scheduled tasks. -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host.  By default, SDD scans are configured to run two concurrent threads. For example, if the job is configured to scan 8 hosts at a time with two concurrent SDD threads, then an extra 32 GB of RAM are required (8x2x2=32). +If running Sensitive Data Discovery (SDD) scans, you must increase the minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. By default, SDD scans are configured to run two concurrent threads. For example, if the job is configured to scan 8 hosts at a time with two concurrent SDD threads, then an extra 32 GB of RAM are required (8x2x2=32). Firewall rules must be configured to allow for communication between the applicable servers. See the [Local Mode Port Requirements](https://docs.netwrix.com/docs/accessanalyzer/11_6/requirements/filesystem/scanoptions/local-mode-scans/localmodeports) topic for firewall rule information. @@ -30,9 +30,9 @@ Firewall rules must be configured to allow for communication between the applica The account used in the connection profile associated with the File System scan jobs, should have the appropriate permissions required to access the target host. See the [File System Supported Platforms](https://docs.netwrix.com/docs/accessanalyzer/11_6/requirements/filesystem/filesystems/) page for specific requirements per target file system. -## How do I determine if I’m using Local Mode scanning? +## Determine whether you're using Local Mode scanning The best way to verify if you’re using Local Mode scanning is via the FSAA Data Collector Query Settings > [Scan Server Selection](https://docs.netwrix.com/docs/accessanalyzer/11_6/admin/datacollector/fsaa/scanserverselection) page: -- **Automatic** — If the target host being scanned is a NAS/Non-Windows host, a Local Mode scan will be utilized. -- **Local Server** — This will utilize a Local Mode scan, regardless of the OSType of the target host. +- **Automatic** — If the target host being scanned is a NAS/Non-Windows host, a Local Mode scan will be used. +- **Local Server** — This will use a Local Mode scan, regardless of the OSType of the target host. diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/localmodescans/localmodeports.md b/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/localmodescans/localmodeports.md index 8af86641b8..72f5d83a92 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/localmodescans/localmodeports.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/localmodescans/localmodeports.md @@ -6,7 +6,7 @@ sidebar_position: 20 # Local Mode Port Requirements -The following are the firewall settings are required when executing the Access Auditing (FSAA) +The following firewall settings are required when executing the Access Auditing (FSAA) and/or Sensitive Data Discovery Auditing scans in local mode for communication between Enterprise Auditor and the target host: diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/proxymodescans/asaservice/proxymodeserviceports.md b/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/proxymodescans/asaservice/proxymodeserviceports.md index 4c1658ad19..683898fe4b 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/proxymodescans/asaservice/proxymodeserviceports.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/proxymodescans/asaservice/proxymodeserviceports.md @@ -6,7 +6,7 @@ sidebar_position: 20 # Proxy Mode as a Service Port Requirements -The following are the firewall settings are required when executing the Access Auditing (FSAA) +The following firewall settings are required when executing the Access Auditing (FSAA) and/or Sensitive Data Discovery Auditing scans in proxy mode as a service for communication between Enterprise Auditor and the proxy server: @@ -22,7 +22,7 @@ Data Collector Wizard. ::: -The following are the firewall settings are required when executing the Access Auditing (FSAA) +The following firewall settings are required when executing the Access Auditing (FSAA) and/or Sensitive Data Discovery Auditing scans in proxy mode as a service for communication between the proxy server and the target host: diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/proxymodescans/proxymodeserver.md b/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/proxymodescans/proxymodeserver.md index 995ae52b86..a24b18c97a 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/proxymodescans/proxymodeserver.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/proxymodescans/proxymodeserver.md @@ -27,7 +27,7 @@ The server can be physical or virtual. The requirements for Enterprise Auditor a RAM, CPU, and Disk Space are dependent upon the size of the target environment: :::warning -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the +If running Sensitive Data Discovery (SDD) scans, you must increase the minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. By default, SDD scans are configured to run two concurrent threads. For example, if the job is configured to scan 8 hosts at a time with two concurrent SDD threads, then an extra 32 GB of RAM are @@ -65,19 +65,19 @@ required (8x2x2=32). - 2 CPU Cores - 130 GB Disk Space -The above recommended disk space sizing information is based on the needs of Enterprise Auditor as -well as the File System solution for running Permission scans with out of the box configuration (500 +This recommended disk space sizing information is based on the needs of Enterprise Auditor as +well as the File System solution for running Permission scans with the default configuration (500 MB per million files and folders), that means no tag collection, file-level scanning, activity, or sensitive data. -- For tag collection, add 125 MB per million documents to the totals above +- For tag collection, add 125 MB per million documents to these totals - For activity collection, add 250 MB per million files and folders and another 125 MB per million - activity events to the totals above + activity events to these totals - For sensitive data collection, add 500 MB per million files and folders and another 1%-10% of the total size of the documents scanned for sensitive data (depending on targeted document types and - selected criteria) to the totals above + selected criteria) to these totals -For example, in order to scan 200 million files and folders, of which 10 million files will be +For example, to scan 200 million files and folders, of which 10 million files will be scanned for tag collection and sensitive data with a total size of 6 TB, you would need: 160 GB for permission collection + 1.25 GB for tag collection (10x125 MB) + 100 GB for sensitive data collection (200x500 MB) + 600 GB additional for sensitive data collection (10% of 6 TB) = 861.25 GB @@ -112,7 +112,7 @@ The following is required to run Sensitive Data Discovery scans: :::note The Sensitive Data Discovery Add-on installation package installs the appropriate JDK -(Java) version on the server. The JDK deployed is prepackaged and does not require any +(Java) version on the server. The JDK deployed is prepackaged and doesn't require any configuration. It will not conflict with other JDKs or Java Runtimes in the same environment. ::: diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/proxymodescans/withapplet/proxymodeappletpermissions.md b/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/proxymodescans/withapplet/proxymodeappletpermissions.md index b0ecccea55..07009548c5 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/proxymodescans/withapplet/proxymodeappletpermissions.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/proxymodescans/withapplet/proxymodeappletpermissions.md @@ -29,9 +29,9 @@ for network authentication” must be disabled for the applet to start. ::: -Sensitive Data Discovery Auditing scans require .NET Framework 4.7.2 or later to be installed on the -server where the applet is to be deployed in order for Sensitive Data Discovery collections to -successfully occur. +Sensitive Data Discovery Auditing scans require .NET Framework 4.7.2 or later on the +server where the applet is deployed, for Sensitive Data Discovery collections to +succeed. See the [Proxy Mode with Applet Port Requirements](https://docs.netwrix.com/docs/accessanalyzer/11_6/requirements/filesystem/scanoptions/proxy-mode-scans/with-applet/proxymodeappletports) topic for firewall rule diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/proxymodescans/withapplet/proxymodeappletports.md b/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/proxymodescans/withapplet/proxymodeappletports.md index 5ca6e91edc..7c73e9a95d 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/proxymodescans/withapplet/proxymodeappletports.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/proxymodescans/withapplet/proxymodeappletports.md @@ -6,7 +6,7 @@ sidebar_position: 20 # Proxy Mode with Applet Port Requirements -The following are the firewall settings are required when executing the Access Auditing (FSAA) +The following firewall settings are required when executing the Access Auditing (FSAA) and/or Sensitive Data Discovery Auditing scans in proxy mode with applet for communication between Enterprise Auditor and the proxy server: @@ -23,7 +23,7 @@ Data Collector Wizard. ::: -The following are the firewall settings are required when executing the Access Auditing (FSAA) +The following firewall settings are required when executing the Access Auditing (FSAA) and/or Sensitive Data Discovery Auditing scans in proxy mode with applet for communication between the proxy server and the target host: diff --git a/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/scanoptions.md b/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/scanoptions.md index 236d0c4aa4..047cf8f2d8 100644 --- a/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/scanoptions.md +++ b/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/scanoptions.md @@ -11,16 +11,16 @@ targeted but also the mode in which the data collection scan is executed. There types of scan modes: local, applet, or proxy. The proxy mode can be conducted via applet deployment, or via running as a service (installed in advance). -For the purpose of this document, “applet” refers to the runtime deployment of the +In this document, “applet” refers to the runtime deployment of the `FSAAAppletServer.exe` to either the target host (applet mode scans) or the proxy host (proxy mode -with applet scans) via Microsoft Task Scheduler. A “proxy” host is any host which can be leveraged +with applet scans) via Microsoft Task Scheduler. A “proxy” host is any host that can be used for running File System scans against target hosts. ## Local Mode When File System scans are run in local mode, it means all of the data collection processing is conducted by the Enterprise Auditor Console server across the network. The data is collected in the -SQLite database(s), or Tier 2 database(s), on the Enterprise Auditor Console server, and then +SQLite databases, or Tier 2 databases, on the Enterprise Auditor Console server, and then imported into theEnterprise Auditor database, or Tier 1 database, on the SQL Server. ![Illustrates the Enterprise Auditor server running the scan against a file server](/images/accessanalyzer/11.6/requirements/solutions/filesystem/localmode.webp) @@ -35,8 +35,8 @@ See the following topics for additional information: ## Applet Mode :::warning -The local policy, “Network access: Do not allow storage of passwords and credentials -for network authentication” must be disabled in order for the applet to start. +The local policy, “Network access: Don't allow storage of passwords and credentials +for network authentication” must be disabled for the applet to start. ::: @@ -44,7 +44,7 @@ When File System scans are run in applet mode, it means the File System applet i target host when the job is executed to conduct data collection. However, the applet can only be deployed to a server with a Windows operating system. The data is collected on the Windows target host where the applet is deployed. The final step in data collection is to compress and transfer the -data collected in the SQLite database(s), or Tier 2 database(s), back to the Enterprise Auditor +data collected in the SQLite databases, or Tier 2 databases, back to the Enterprise Auditor Console server. If the target host is a NAS device, the File System scans will default to local mode for that host. @@ -62,14 +62,14 @@ See the following topics for additional information: ## Proxy Mode with Applet :::warning -The local policy, “Network access: Do not allow storage of passwords and credentials -for network authentication” must be disabled in order for the applet to start. +The local policy, “Network access: Don't allow storage of passwords and credentials +for network authentication” must be disabled for the applet to start. ::: When File System scans are run in proxy mode with applet, it means the File System applet is deployed to the Windows proxy server when the job is executed to conduct data collection. The data -collection processing is initiated by the proxy server where the applet is deployed and leverages a +collection processing is initiated by the proxy server where the applet is deployed and uses a local mode-type scan to each of the target hosts. The final step in data collection is to compress and transfer the data collected in the SQLite databases, or Tier 2 databases, back to the Enterprise Auditor Console server. @@ -91,13 +91,13 @@ When File System scans are run in proxy mode as a service, there are two methods deploying the service: - Pre-Installed File System Proxy Service – File System Proxy Service installation package must be - installed on the Windows proxy servers prior to executing the scans. This is the recommended + installed on the Windows proxy servers before executing the scans. This is the recommended method. - Ad Hoc File System Proxy Service Deployment – File System Proxy Service is installed on the Windows proxy server when the job is executed The data collection processing is conducted by the proxy server where the service is running and -leverages a local mode-type scan to each of the target hosts. The final step in data collection is +uses a local mode-type scan to each of the target hosts. The final step in data collection is to compress and transfer the data collected in the SQLite databases, or Tier 2 databases, back to the Enterprise Auditor Console server. diff --git a/docs/accessanalyzer/11.6/requirements/overview.md b/docs/accessanalyzer/11.6/requirements/overview.md index e8863beb45..9aec52fcac 100644 --- a/docs/accessanalyzer/11.6/requirements/overview.md +++ b/docs/accessanalyzer/11.6/requirements/overview.md @@ -8,7 +8,7 @@ sidebar_position: 20 This topic describes the recommended configuration of the servers needed to install the application in a production environment. Depending on the size of the organization, it is recommended to review -your environment and requirements with a Netwrix engineer prior to deployment to ensure all +your environment and requirements with a Netwrix engineer before deployment to ensure all exceptions are covered. ## Architecture Overview @@ -46,9 +46,9 @@ The following servers and applications are required for installation of the appl **File System Solution-Specific Components** - Enterprise Auditor File System Proxy Server – In certain environments, a proxy server may be - utilized to scan hosts in remote or firewalled sites to increase scan capacity in large + used to scan hosts in remote or firewalled sites to increase scan capacity in large environments. This feature can be implemented through either an applet or a service. The applet - would be deployed as part of the data collection process. The service should be installed prior to + would be deployed as part of the data collection process. The service should be installed before data collection. See the [Proxy Mode as a Service](/docs/accessanalyzer/11.6/requirements/filesystem/scanoptions/scanoptions.md#proxy-mode-as-a-service) topic for server requirements. @@ -60,7 +60,7 @@ The following servers and applications are required for installation of the appl - Enterprise Auditor SharePoint Agent Server – For agent-based scans, this application can be installed on the SharePoint application server that hosts the “Central Administration” component - of the targeted farm(s) to auditing permissions, content, and sensitive data for SharePoint + of the targeted farms to auditing permissions, content, and sensitive data for SharePoint On-Premise. See the [SharePoint Scan Options](/docs/accessanalyzer/11.6/requirements/sharepoint/scanoptions/scanoptions.md) topic for server requirements. @@ -76,7 +76,7 @@ The following servers and applications are required for installation of the appl for installation requirements and information on collecting activity data. - Netwrix Threat Prevention – Enterprise Auditor can integrate with Threat Prevention for Active Directory and Windows File System event data. This integration works in conjunction with Netwrix - Activity Monitor. See the the + Activity Monitor. See the [Netwrix Threat Prevention Documentation](https://helpcenter.netwrix.com/category/threatprevention) for installation requirements and information on collecting activity data. @@ -192,7 +192,7 @@ The following additional considerations are recommended for the SQL Server: - The standard Autogrowth setting can cause Enterprise Auditor job delays. Database growth is computationally intensive. While SQL Server is growing the database, no other activity can occur. - If this option is employed, please speak with a Netwrix engineer to determine an appropriate + If this option is employed, speak with a Netwrix engineer to determine an appropriate setting for best performance. - Microsoft SQL Server supports TLS 1.2, which requires the Enterprise Auditor Console server to have either SQL Server Native Client 11 or Microsoft OleDB 18 installed. @@ -207,8 +207,8 @@ The following permissions are required on the databases: ## Virtual Environment Recommendations -While physical machines are always preferred, we fully support the use of virtual machines. This -section contains special considerations when leveraging virtualization. +While physical machines are always preferred, virtual machines are fully supported. This +section contains special considerations when using virtualization. - VMWare® ESX® – If using ESX, the following specifications are recommended: diff --git a/docs/accessanalyzer/11.6/requirements/sharepoint/scanoptions/agentbasedscans/agentpermissions.md b/docs/accessanalyzer/11.6/requirements/sharepoint/scanoptions/agentbasedscans/agentpermissions.md index 437cdd76c1..a241598c76 100644 --- a/docs/accessanalyzer/11.6/requirements/sharepoint/scanoptions/agentbasedscans/agentpermissions.md +++ b/docs/accessanalyzer/11.6/requirements/sharepoint/scanoptions/agentbasedscans/agentpermissions.md @@ -8,7 +8,7 @@ sidebar_position: 10 When Enterprise Auditor SharePoint scans are run in agent-based mode, the Enterprise Auditor SharePoint Agent must be installed on the SharePoint Application server which hosts the Central -Administration component prior to executing the scans. This is typically the first server stood up +Administration component before executing the scans. This is typically the first server deployed during the SharePoint farm installation process in this mode. The data collection processing is conducted by the SharePoint Agent for the target environment. The final step in data collection is to transfer the data collected in the SQLite databases, or Tier 2 databases, on the Enterprise @@ -30,7 +30,7 @@ The following are additional requirements for the Enterprise Auditor SharePoint **Sensitive Data Discovery Auditing Requirement** -In addition to having the Sensitive Data Discovery Add-on be installed on the Enterprise Auditor +In addition to having the Sensitive Data Discovery Add-on installed on the Enterprise Auditor Console server, The following is required to run Sensitive Data Discovery scans: - Sensitive Data Discovery Add-On, 64-bit version, installed on the Enterprise Auditor SharePoint @@ -39,20 +39,20 @@ Console server, The following is required to run Sensitive Data Discovery scans: :::note The Sensitive Data Discovery Add-on installation package installs the appropriate JDK -(Java) version on the server. The JDK deployed is prepackaged and does not require any +(Java) version on the server. The JDK deployed is prepackaged and doesn't require any configuration; it has been preconfigured to work with Enterprise Auditor and should never be customized through Java. It will not conflict with other JDKs or Java Runtimes in the same environment. ::: -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the minimum amount +If running Sensitive Data Discovery (SDD) scans, you must increase the minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For example, if the job is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are required (8x2=16). ## Permissions Explained -If limited provisioning of the service account is not required by the organization, then the +If limited provisioning of the service account isn't required by the organization, then the following permissions are sufficient for successful agent-based scans: - Membership in the local Administrator group on the on server where the Enterprise Auditor @@ -85,10 +85,10 @@ following permissions are sufficient for successful agent-based scans: - This is required so the Enterprise Auditor auditing account can make calls against the SharePoint web services to remotely gather information around permissions, site hierarchy, content and more - - If the group does not exist already, then you need to create a new group at that level and + - If the group doesn't exist already, then you need to create a new group at that level and grant it Read access. Specifically, it is a group that exists within Central Administration at the farm administrator level. This group only requires Read access and - is not giving farm admin access. Once the group is created, add the service account that + isn't giving farm admin access. After the group is created, add the service account that Enterprise Auditor will be leveraging to scan SharePoint. - Web Application permissions: @@ -103,7 +103,7 @@ following permissions are sufficient for successful agent-based scans: - SPDataAccess on the SharePoint Content database and all Configuration databases - - This permission should be applied on the desired Configuration database and all Content + - This permission should be applied on the Configuration database and all Content databases for the SharePoint version - This version-specific permission is required for Enterprise Auditor to execute read operations directly against the SharePoint databases, gather information from the @@ -127,7 +127,7 @@ Additional permission models are explained for a less and least permission model If restricted permissions are desired by the organization, then the following permissions are needed for the service account to successfully run SharePoint Agent-based scans. -Prior to installation of the SharePoint Agent, the service account to be supplied during +Before installation of the SharePoint Agent, the service account to be supplied during installation and later used to run the Access Auditing (SPAA) and Sensitive Data Discovery Auditing scans against the targeted SharePoint environment needs the following permissions: @@ -156,8 +156,8 @@ following permissions: `C:\Program Files\STEALTHbits\StealthAUDIT\SPAA` -The Enterprise Auditor SharePoint Agent utilizes Microsoft APIs. The Microsoft APIs require an -account with the following permissions in order to collect all of the data: +The Enterprise Auditor SharePoint Agent uses Microsoft APIs. The Microsoft APIs require an +account with the following permissions to collect all of the data: - WSS_CONTENT_APPLICATION_POOLS on the SharePoint Content databases - WSS_CONTENT_APPLICATION_POOLS on the SharePoint Configuration database @@ -172,7 +172,7 @@ If scans include Web Application scoping, this last permission requirement is al If a least privilege model is required by the organization, then the following permissions are needed for the service account to successfully run SharePoint Agent-based scans. -Prior to installation of the SharePoint Agent, the service account to be supplied during +Before installation of the SharePoint Agent, the service account to be supplied during installation and later used to run the Access Auditing (SPAA) and Sensitive Data Discovery Auditing scans the targeted SharePoint environment needs the following permissions: @@ -217,8 +217,8 @@ following permissions: `C:\Program Files\STEALTHbits\StealthAUDIT\SPAA` -The Enterprise Auditor SharePoint Agent utilizes Microsoft APIs. The Microsoft APIs require an -account with the following permissions in order to collect all of the data: +The Enterprise Auditor SharePoint Agent uses Microsoft APIs. The Microsoft APIs require an +account with the following permissions to collect all of the data: - `'GRANT EXECUTE'` permissions on the following stored procedures in the SharePoint Configuration database: @@ -230,7 +230,7 @@ account with the following permissions in order to collect all of the data: - `proc_ReturnWebFeatures` :::note - The above four stored procedures would already have the correct permissions if Web + These four stored procedures would already have the correct permissions if Web Application scoping is desired. ::: diff --git a/docs/accessanalyzer/11.6/requirements/sharepoint/scanoptions/agentbasedscans/agentports.md b/docs/accessanalyzer/11.6/requirements/sharepoint/scanoptions/agentbasedscans/agentports.md index 41676bcdfc..faa5610b72 100644 --- a/docs/accessanalyzer/11.6/requirements/sharepoint/scanoptions/agentbasedscans/agentports.md +++ b/docs/accessanalyzer/11.6/requirements/sharepoint/scanoptions/agentbasedscans/agentports.md @@ -6,7 +6,7 @@ sidebar_position: 20 # SharePoint Agent Ports -The following are the firewall settings are required when executing the Access Auditing (FSAA) +The following firewall settings are required when executing the Access Auditing (FSAA) and/or Sensitive Data Discovery Auditing scans in Agent-based mode for communication between Enterprise Auditor and the target host: diff --git a/docs/accessanalyzer/11.6/requirements/sharepoint/scanoptions/scanoptions.md b/docs/accessanalyzer/11.6/requirements/sharepoint/scanoptions/scanoptions.md index 255995711d..9402719fda 100644 --- a/docs/accessanalyzer/11.6/requirements/sharepoint/scanoptions/scanoptions.md +++ b/docs/accessanalyzer/11.6/requirements/sharepoint/scanoptions/scanoptions.md @@ -6,22 +6,21 @@ sidebar_position: 10 # SharePoint Scan Options -Required permissions on the targeted SharePoint environment are dependent upon not only the type of -environment targeted but also the type of data collection scan being executed. There are two types -of Access Auditing (SPAA) and/or Sensitive Data Discovery Auditing scans: agent-based and -agent-less. The Activity Auditing (SPAC) scans run as agent-less scans from Enterprise Auditor, but -they require the Netwrix Activity Monitor to have an activity agent deployed in the target -environment. +Required permissions on the targeted SharePoint environment depend on both the type of environment +you target and the type of data collection scan you run. There are two types of Access Auditing +(SPAA) and/or Sensitive Data Discovery Auditing scans: agent-based and agent-less. The Activity +Auditing (SPAC) scans run as agent-less scans from Enterprise Auditor, but they require the Netwrix +Activity Monitor to have an activity agent deployed in the target environment. ## Agent-Based Type -When Enterprise Auditor SharePoint scans are run in agent-based mode, the Enterprise Auditor -SharePoint Agent must be installed on the SharePoint Application server which hosts the Central -Administration component prior to executing the scans. This is typically the first server stood up -during the SharePoint farm installation process in this mode. The data collection processing is -conducted by the SharePoint Agent for the target environment. The final step in data collection is -to transfer the data collected in the SQLite databases, or Tier 2 databases, on the Enterprise -Auditor SharePoint Agent server back to the Enterprise Auditor Console server. +Before you run Enterprise Auditor SharePoint scans in agent-based mode, install the Enterprise +Auditor SharePoint Agent on the SharePoint Application server that hosts the Central Administration +component. This is typically the first server set up during the SharePoint farm installation +process in this mode. The SharePoint Agent conducts data collection processing for the target +environment. The final step in data collection is to transfer the data collected in the SQLite +databases, or Tier 2 databases, on the Enterprise Auditor SharePoint Agent server back to the +Enterprise Auditor Console server. :::note Agent-based scans can only target on-premise environments. @@ -35,8 +34,8 @@ See the following topics for additional information: ## Agent-Less Type -When SharePoint agent-less scans are run, it means all of the data collection processing is -conducted by the Enterprise Auditor Console server across the network. +When you run SharePoint agent-less scans, the Enterprise Auditor Console server conducts all data +collection processing across the network. :::note Agent-less scans can target both on-premise and online environments. This is the only scan diff --git a/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint.md b/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint.md index 7e59dc0d48..8ae2b4c3f4 100644 --- a/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint.md +++ b/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint.md @@ -11,19 +11,19 @@ Server, and Access Information Center. See the [Requirements](/docs/accessanalyzer/11.6/requirements/overview.md) topic for the core requirements. -The SharePoint solution can be configure to run without an agent or to use the Enterprise Auditor +You can configure the SharePoint solution to run without an agent or to use the Enterprise Auditor SharePoint Agent. See the [SharePoint Agent Installation](/docs/accessanalyzer/11.6/install/sharepointagent/overview.md) topic for additional information. -In addition to these, integration with either the Netwrix Activity Monitor is required for event -activity data to be scanned. See the +In addition, scanning event activity data requires integration with the Netwrix Activity Monitor. +See the [Netwrix Activity Monitor Documentation](https://helpcenter.netwrix.com/category/activitymonitor) for installation requirements and information on collecting activity data. :::note -For Activity Auditing (SPAC) scans, the audit logs generated by SharePoint must be -retained for more days than the number of days between the Enterprise Auditor scans. +For Activity Auditing (SPAC) scans, retain the audit logs generated by SharePoint for more days +than the number of days between the Enterprise Auditor scans. ::: @@ -33,12 +33,12 @@ in both the Documents and Items section and the List, Libraries, and Site sectio ::: -The Sensitive Data Discovery Add-On must be installed on the Enterprise Auditor Console server, -which enables Sensitive Data criteria for scans. +Install the Sensitive Data Discovery Add-On on the Enterprise Auditor Console server to enable +Sensitive Data criteria for scans. :::note -If the Enterprise Auditor SharePoint Agent scan option is used, it is also be necessary -for the Sensitive Data Discovery Add-On to be installed on the servers as well. +If you use the Enterprise Auditor SharePoint Agent scan option, also install the Sensitive Data +Discovery Add-On on the servers. ::: @@ -60,7 +60,7 @@ topic for additional information. **RAM, CPU, and Disk Space** -These are dependent upon the size of the target environment: +These depend on the size of the target environment: | Environment | Extra-Large | Large | Medium | Small | | ----------- | ------------------------------------------------ | ------------------------------------------------- | ------------------------------------------------- | ----------------------------------------------- | @@ -70,10 +70,9 @@ These are dependent upon the size of the target environment: | Disk Space | 460 GB | 280 GB | 160 GB | 80 GB | :::note -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the -minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host.For -example, if the job is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are -required (8x2=16). +If you run Sensitive Data Discovery (SDD) scans, increase the minimum amount of RAM. Each thread +requires a minimum of 2 additional GB of RAM per host. For example, if you configure the job to +scan 8 hosts at a time, it requires an extra 16 GB of RAM (8 x 2 = 16). ::: @@ -85,10 +84,9 @@ The following is required to run Sensitive Data Discovery scans: :::note The Sensitive Data Discovery Add-on installation package installs the appropriate JDK -(Java) version on the server. The JDK deployed is prepackaged and does not require any -configuration; it has been preconfigured to work with Enterprise Auditor and should never be -customized through Java. It will not conflict with other JDKs or Java Runtimes in the same -environment. +(Java) version on the server. The JDK deployed is prepackaged and doesn't require any +configuration. The package preconfigures it to work with Enterprise Auditor, so never customize it +through Java. It doesn't conflict with other JDKs or Java Runtimes in the same environment. ::: @@ -96,7 +94,7 @@ environment. **RAM, CPU, and Disk Space** -These are dependent upon the size of the target environment. +These depend on the size of the target environment. | Environment | Extra-Large | Large | Medium | Small | | ------------------------ | ------------------------------------------------ | ------------------------------------------------- | ------------------------------------------------- | ----------------------------------------------- | diff --git a/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepoint.md b/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepoint.md index e1451663de..662c889d20 100644 --- a/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepoint.md +++ b/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepoint.md @@ -10,7 +10,7 @@ Netwrix products audit and monitor Microsoft® SharePoint® environments. Enterp the SharePoint solution to execute Access Auditing (SPAA) and Sensitive Data Discovery Auditing scans against SharePoint on-premise and SharePoint Online. Through integration with Activity Monitor, Enterprise Auditor can also execute Activity Auditing (SPAC) scans against SharePoint -on-premise and SharePoint online environments. Additionally, Activity Monitor can be configured to +on-premise and SharePoint online environments. Additionally, you can configure Activity Monitor to provide activity data to various SIEM products. Ports and permissions vary based on the scan mode option selected as well as the target environment. diff --git a/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepoint/access.md b/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepoint/access.md index 1aa2e80922..904f0616a4 100644 --- a/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepoint/access.md +++ b/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepoint/access.md @@ -30,14 +30,14 @@ The service account must be a member of the `Farm Read` group at the farm level. Enterprise Auditor to call the SharePoint web services to gather permissions, site hierarchy, and content information remotely. -Follow these steps to configure farm-level permissions on SharePoint 2013 through SharePoint 2019: +### Configure farm-level permissions on SharePoint 2013 through SharePoint 2019 1. In the SharePoint **Central Administration Center**, navigate to the **Security** section. 2. Select **Manage the farm administrators group** under **Users**. 3. If the `Farm Read` group exists, add the service account to that group. If the group has been deleted, create a new group: - Select **More** under the **Groups** section. - - Select **New Group** from the **New** drop-down menu. + - Select **New Group** from the **New** dropdown menu. - Ensure the group has the `Read – Can view pages and list items and download documents` permission. - Add the service account to the new group. @@ -50,8 +50,7 @@ The service account requires a custom policy role with `Site Collection Auditor` permissions at the web application level. This allows Enterprise Auditor to execute web service calls against **Central Administration**. -Follow these steps to configure web application-level permissions on SharePoint 2013 through -SharePoint 2019: +### Configure web application-level permissions on SharePoint 2013 through SharePoint 2019 1. In the **Central Administration Center**, navigate to the **Application Management** section. 2. Select **Manage web applications** under **Web Applications**. @@ -72,8 +71,8 @@ SharePoint 2019: then click **Finish**. 6. Repeat step 5 for each web application in scope. -The service account is provisioned as `Site Collection Auditor` on all web applications to be -audited. +The service account now has `Site Collection Auditor` access on all web applications you want to +audit. ## SharePoint database server permissions @@ -82,7 +81,7 @@ configuration database and all content databases. This allows Enterprise Auditor operations directly against the SharePoint databases and gather information about web application and content database locations. -Follow these steps to configure database server permissions: +### Configure database server permissions 1. Open the SharePoint database server user configuration in SQL Server Management Studio. 2. Grant the service account the `SPDataAccess` database role membership on the following @@ -91,7 +90,7 @@ Follow these steps to configure database server permissions: - All SharePoint Content databases that house web application data (by default, content databases begin with `WSS_Content`, but they can be customized) -The service account is provisioned with the required SharePoint database permissions. +The service account now has the required SharePoint database permissions. ## MySites and OneDrive permissions @@ -102,5 +101,5 @@ MySites and OneDrive permissions depend on the SharePoint Access Data Collector requires the SharePoint Farm Administrator role or `Site Collection Auditor` at the web application that hosts MySites. - **Skip inaccessible personal sites**: This option scans only sites where the service account - already has administrative access. You must provision the service account before the scan to - scan OneDrives and personal sites. + already has administrative access. To scan OneDrives and personal sites, provision the service + account with access before running the scan. diff --git a/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepoint/activity.md b/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepoint/activity.md index 6654e8582a..da4c8d22e2 100644 --- a/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepoint/activity.md +++ b/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepoint/activity.md @@ -6,8 +6,8 @@ sidebar_position: 20 # SharePoint On-Premise Activity Auditing Configuration -SharePoint Event Auditing must be enabled for each site collection to be monitored by the Netwrix -Activity Monitor and/or audited by Netwrix Enterprise Auditor. +Enable SharePoint Event Auditing for each site collection that the Netwrix Activity Monitor +monitors or Netwrix Enterprise Auditor audits. ## User Requirements diff --git a/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepoint/overview.md b/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepoint/overview.md index eb214eae7b..21f64e930c 100644 --- a/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepoint/overview.md +++ b/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepoint/overview.md @@ -7,7 +7,7 @@ sidebar_position: 10 # SharePoint Target Requirements Netwrix Enterprise Auditor can execute Access Auditing (SPAA) and/or Sensitive Data Discovery -Auditing scans on SharePoint farms. The Netwrix Activity Monitor can be configured to monitor +Auditing scans on SharePoint farms. You can configure the Netwrix Activity Monitor to monitor activity on SharePoint farms and make the event data available for Enterprise Auditor Activity Auditing (SPAC) scans. @@ -39,7 +39,7 @@ Activity Agent must have the following permissions on the proxy server: - Membership in the local Administrators group - READ and WRITE access to the archive location for Archiving feature only -It is also necessary to enable the Remote Registry Service on the Activity Agent server. +Also enable the Remote Registry Service on the Activity Agent server. For integration between the Activity Monitor and Enterprise Auditor, the credential used by Enterprise Auditor to read the activity log files must have also have this permission. @@ -65,15 +65,15 @@ are required for communication between the Agent server and the Netwrix Activity | -------------------------------- | -------- | ----- | ------------------- | | Activity Monitor to Agent Server | TCP | 4498 | Agent Communication | -The Windows firewall rules need to be configured on the Windows server, which require certain -inbound rules be created if the scans are running in applet mode. These scans operate over a default -port range, which cannot be specified via an inbound rule. For more information, see the Microsoft +Configure the Windows firewall rules on the Windows server. If the scans run in applet mode, you +must create certain inbound rules. These scans operate over a default +port range, which can't be specified via an inbound rule. For more information, see the Microsoft [Connecting to WMI on a Remote Computer](https://msdn.microsoft.com/en-us/library/windows/desktop/aa389290(v=vs.85).aspx) article. Additional Firewall Rules for Integration between Enterprise Auditor and Activity Monitor -Firewall settings are dependent upon the type of environment being targeted. The following firewall +Firewall settings depend on the type of environment you target. The following firewall settings are required for communication between the agent server and the Enterprise Auditor Console: | Communication Direction | Protocol | Ports | Description | diff --git a/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepointonline/access.md b/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepointonline/access.md index 92db88805d..5d56eea176 100644 --- a/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepointonline/access.md +++ b/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepointonline/access.md @@ -19,7 +19,7 @@ Microsoft Entra ID. **Configuration Settings from the Registered Application** -The following settings are needed from your tenant once you have registered the application: +The following settings are needed from your tenant after you register the application: - Client ID – This is the Application (client) ID for the registered application - Key – The comma delimited string containing the path to the certificate PFX file, certificate @@ -28,9 +28,9 @@ The following settings are needed from your tenant once you have registered the Configure Modern Authentication for SharePoint Online using SP_RegisterAzureAppAuth Instant Job -Registering a Microsoft Entra ID application and provisioning it to grant permissions to SharePoint -Online can be automated using the SP_RegisterAzureAppAuth job from the Enterprise Auditor Instant -Job Library. The SP_RegisterAzureAppAuth job uses the PowerShell Data Collector to automatically +The SP_RegisterAzureAppAuth job from the Enterprise Auditor Instant Job Library can automate +registering a Microsoft Entra ID application and provisioning it to grant permissions to SharePoint +Online. The SP_RegisterAzureAppAuth job uses the PowerShell Data Collector to automatically configure modern authentication for SharePoint Online. It requires: - A Connection Profile containing the following two user credentials, both with an Account Type of @@ -103,9 +103,7 @@ against Entra ID while requesting the App Only access token. See the Microsoft [Granting access via Azure AD App-Only](https://learn.microsoft.com/en-us/sharepoint/dev/solution-guidance/security-apponly-azuread) article for additional information. -Follow the steps create the self-signed X.509 certificate. - -**Step 1 –** To generate a certificate, use the sample PowerShell command below: +**Step 1 –** To generate a certificate, use the following sample PowerShell command: - Change the following parameters in the sample PowerShell command. See the Microsoft [New-SelfSignedCertificate](https://docs.microsoft.com/en-us/powershell/module/pki/new-selfsignedcertificate) @@ -115,9 +113,9 @@ Follow the steps create the self-signed X.509 certificate. certificate - Subject – A unique name for the new App (always starts with CN=, to denote a canonical name) - FriendlyName – Same as Subject name minus the canonical name prefix - - NotAfter – A datetime string denoting the certificate's expiration date - in the above sample, - Get-Date.AddYears(11) specifies that the certificate will expire 11 years from the current - datetime + - NotAfter – A datetime string denoting the certificate's expiration date - in the following + sample, Get-Date.AddYears(11) specifies that the certificate will expire 11 years from the + current datetime Example PowerShell: @@ -131,7 +129,7 @@ $certPath variable (see Step 1). :::note The environment variable `SAINSTALLDIR` always points to the base Enterprise Auditor -install directory; simply append the PrivateAssemblies to point to that folder with the following +install directory; append PrivateAssemblies to point to that folder with the following cmdlet: ::: @@ -163,10 +161,8 @@ more secure before running this cmdlet. ## Register a Microsoft Entra ID Application -Follow the steps to register Enterprise Auditor with Microsoft Entra ID. - :::note -The steps below are for the Microsoft Entra Admin Center. These steps might vary slightly +The following steps are for the Microsoft Entra Admin Center. These steps might vary slightly if you start from a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: @@ -188,14 +184,12 @@ registrations. **Step 5 –** Click **Register**. The Overview page for the newly registered app opens. Review the newly created registered -application. Now that the application has been registered, permissions need to be granted to it. +application, then grant it permissions. ## Upload Self-Signed Certificate -Follow the steps to provision the upload your self-signed certificate. - :::note -The steps below are for the Microsoft Entra Admin Center. These steps might vary slightly +The following steps are for the Microsoft Entra Admin Center. These steps might vary slightly if you start from a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: @@ -220,10 +214,8 @@ The upload certificate public key .cer file is an application key credential. ## Grant Permissions to the Registered Application -Follow the steps to grant permissions to the registered application. - :::note -The steps below are for the Microsoft Entra Admin Center. These steps might vary slightly +The following steps are for the Microsoft Entra Admin Center. These steps might vary slightly if you start from a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: @@ -299,15 +291,13 @@ Select the following permissions: **Step 12 –** Click **Grant Admin Consent for [tenant]**. Then click **Yes** in the confirmation window. -Now that the permissions have been granted to it, the Connection Profile and host settings for -Enterprise Auditor need to be collected. +Now that you've granted the permissions, collect the Connection Profile and host settings for +Enterprise Auditor. ## Identify the Client ID -Follow the steps to find the registered application's Client ID. - :::note -The steps below are for the Microsoft Entra Admin Center. These steps might vary slightly +The following steps are for the Microsoft Entra Admin Center. These steps might vary slightly if you start from a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: diff --git a/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepointonline/activity.md b/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepointonline/activity.md index a6c6df8664..1217544c01 100644 --- a/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepointonline/activity.md +++ b/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepointonline/activity.md @@ -6,8 +6,8 @@ sidebar_position: 20 # SharePoint Online Activity Auditing Configuration -In order to collect logs and monitor SharePoint Online activity using the Netwrix Activity Monitor, -it needs to be registered with Microsoft® Entra ID® (formerly Azure AD). +To collect logs and monitor SharePoint Online activity, the Netwrix Activity Monitor requires an +application registered with Microsoft® Entra ID® (formerly Azure AD). :::note A user account with the Global Administrator role is required to register an app with @@ -26,14 +26,14 @@ additional information. **Configuration Settings from the Registered Application** -The following settings are needed from your tenant once you have registered the application: +The following settings are needed from your tenant after you register the application: - Tenant ID – This is the Tenant ID for Microsoft Entra ID - Client ID – This is the Application (client) ID for the registered application - Client Secret – This is the Client Secret Value generated when a new secret is created :::warning - It is not possible to retrieve the value after saving the new key. It must be + It isn't possible to retrieve the value after saving the new key. It must be copied first. ::: @@ -55,10 +55,8 @@ The following settings are needed from your tenant once you have registered the ## Register a Microsoft Entra ID Application -Follow the steps to register Activity Monitor with Microsoft Entra ID. - :::note -The steps below are for the Microsoft Entra Admin Center. These steps might vary slightly +The following steps are for the Microsoft Entra Admin Center. These steps might vary slightly if you start from a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: @@ -84,14 +82,12 @@ registrations. **Step 5 –** Click **Register**. The Overview page for the newly registered app opens. Review the newly created registered -application. Now that the application has been registered, permissions need to be granted to it. +application, then grant it permissions. ## Grant Permissions to the Registered Application -Follow the steps to grant permissions to the registered application. - :::note -The steps below are for the Microsoft Entra Admin Center. These steps might vary slightly +The following steps are for the Microsoft Entra Admin Center. These steps might vary slightly if you start from a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: @@ -131,15 +127,12 @@ Microsoft APIs tab. Select the following permissions: **Step 9 –** Click **Grant Admin Consent for [tenant]**. Then click **Yes** in the confirmation window. -Now that the permissions have been granted to it, the settings required for Activity Monitor need to -be collected. +Now that you've granted the permissions, collect the settings required for Activity Monitor. ## Identify the Client ID -Follow the steps to find the registered application's Client ID. - :::note -The steps below are for the Microsoft Entra Admin Center. These steps might vary slightly +The following steps are for the Microsoft Entra Admin Center. These steps might vary slightly if you start from a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: @@ -174,10 +167,8 @@ application’s Client Secret Key. **Overview Page** -Follow the steps to find the tenant name where the registered application resides. - :::note -The steps below are for the Microsoft Entra Admin Center. These steps might vary slightly +The following steps are for the Microsoft Entra Admin Center. These steps might vary slightly if you start from a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: @@ -194,18 +185,15 @@ application’s Client Secret Key. ## Generate the Client Secret Key -Follow the steps to find the registered application's Client Secret, create a new key, and save its -value when saving the new key. - :::note -The steps below are for the Microsoft Entra Admin Center. These steps might vary slightly +The following steps are for the Microsoft Entra Admin Center. These steps might vary slightly if you start from a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: :::warning -It is not possible to retrieve the value after saving the new key. It must be copied +It isn't possible to retrieve the value after saving the new key. It must be copied first. ::: @@ -232,13 +220,13 @@ list. **Step 5 –** Click **Add** to generate the key. :::warning -If this page is left before the key is copied, then the key is not retrievable, and -this process will have to be repeated. +If you leave this page before copying the key, the key isn't retrievable and you'll have to repeat +this process. ::: -**Step 6 –** The Client Secret will be displayed in the Value column of the table. You can use the -Copy to clipboard button to copy the Client Secret. +**Step 6 –** The Value column of the table displays the Client Secret. You can use the Copy to +clipboard button to copy the Client Secret. **Step 7 –** Save this value in a text file. @@ -246,15 +234,14 @@ This is needed for adding a SharePoint Online host in the Activity Monitor. ## Enable Auditing for SharePoint Online -Follow the steps to enable auditing for SharePoint Online so the Activity Monitor can receive -events. +Enable auditing for SharePoint Online so the Activity Monitor can receive events. **Step 1 –** In the Microsoft Purview compliance portal at [https://compliance.microsoft.com](https://compliance.microsoft.com/), go to **Solutions** > **Audit**. Or, to go directly to the Audit page at [https://compliance.microsoft.com/auditlogsearch](https://compliance.microsoft.com/auditlogsearch). -**Step 2 –** If auditing is not turned on for your organization, a banner is displayed prompting you +**Step 2 –** If auditing isn't turned on for your organization, a banner is displayed prompting you start recording user and admin activity. **Step 3 –** Select the **Start recording** user and **admin activity** banner. diff --git a/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepointonline/overview.md b/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepointonline/overview.md index ac66bb3cd9..c2f746f589 100644 --- a/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepointonline/overview.md +++ b/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepointonline/overview.md @@ -7,7 +7,7 @@ sidebar_position: 20 # SharePoint Online Target Requirements Netwrix Enterprise Auditor can execute Access Auditing (SPAA) and Sensitive Data Discovery Auditing -scans on SharePoint Online. The Netwrix Activity Monitor can be configured to monitor activity on +scans on SharePoint Online. You can configure the Netwrix Activity Monitor to monitor activity on SharePoint Online and make the event data available for Enterprise Auditor Activity Auditing (SPAC) scans. @@ -48,7 +48,7 @@ server: - Membership in the local Administrators group - READ and WRITE access to the archive location for Archiving feature only -It is also necessary to enable the Remote Registry Service on the Activity Agent server. +Also enable the Remote Registry Service on the Activity Agent server. For integration between the Activity Monitor and Enterprise Auditor, the credential used by Enterprise Auditor to read the activity log files must have also have this permission. @@ -74,15 +74,15 @@ are required for communication between the Agent server and the Netwrix Activity | -------------------------------- | -------- | ----- | ------------------- | | Activity Monitor to Agent Server | TCP | 4498 | Agent Communication | -The Windows firewall rules need to be configured on the Windows server, which require certain -inbound rules be created if the scans are running in applet mode. These scans operate over a default -port range, which cannot be specified via an inbound rule. For more information, see the Microsoft +Configure the Windows firewall rules on the Windows server. If the scans run in applet mode, you +must create certain inbound rules. These scans operate over a default +port range, which can't be specified via an inbound rule. For more information, see the Microsoft [Connecting to WMI on a Remote Computer](https://msdn.microsoft.com/en-us/library/windows/desktop/aa389290(v=vs.85).aspx) article. Additional Firewall Rules for Integration between Enterprise Auditor and Activity Monitor -Firewall settings are dependent upon the type of environment being targeted. The following firewall +Firewall settings depend on the type of environment you target. The following firewall settings are required for communication between the agent server and the Enterprise Auditor Console: | Communication Direction | Protocol | Ports | Description | diff --git a/docs/accessanalyzer/11.6/requirements/unix/target.md b/docs/accessanalyzer/11.6/requirements/unix/target.md index 52af30d3f0..8fe7b9cbdd 100644 --- a/docs/accessanalyzer/11.6/requirements/unix/target.md +++ b/docs/accessanalyzer/11.6/requirements/unix/target.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Target Unix Requirements, Permissions, and Ports -The Enterprise Auditor for Unix Solution provides the ability to audit Unix servers. It scans: +The Enterprise Auditor for Unix Solution lets you audit Unix servers. It scans: - AIX® 4+ - Solaris™ 8+ @@ -33,8 +33,8 @@ This solution employs the following data collectors to scan the target environme - Root permissions in Unix/Linux -If the Root permission is unavailable, a least privileged model can be used. See the -[Least Privilege Model](#least-privilege-model) topic additional information. +If the Root permission is unavailable, you can use a least privileged model. See the +[Least Privilege Model](#least-privilege-model) topic for additional information. ## Ports @@ -53,17 +53,17 @@ The following firewall ports are needed: ## Least Privilege Model Enterprise Auditor for Unix collects information from Unix devices by running commands or executing -scripts on your Unix hosts (if configured properly our tool can SCP scripts to your hosts before -execution). Therefore, the domain or local user credentials entered in the Connection Profile within -the Enterprise Auditor must be capable of running the necessary commands, executing the necessary -scripts or, in some cases, have rights to SCP scripts to the host. +scripts on your Unix hosts (if configured properly, Enterprise Auditor can SCP scripts to your hosts +before execution). Therefore, the domain or local user credentials entered in the Connection Profile within +the Enterprise Auditor must be able to run the necessary commands, execute the necessary +scripts, or, in some cases, have rights to SCP scripts to the host. ### Connecting to Unix Hosts Enterprise Auditor for Unix connects to your host in two ways: -- Plink – This mechanism is leveraged during our tools Host Inventory to test connectivity to a host - and to collect basic details about a host (Host Name, OS Type, etc.) +- Plink – Enterprise Auditor uses this mechanism during Host Inventory to test connectivity to a + host and to collect basic details about a host (Host Name, OS Type, etc.) - Implementation of the SSH2 protocol built into Enterprise Auditor – This is how the Unix Data Collector interacts with and pulls information from your environment @@ -81,13 +81,13 @@ Enterprise Auditor for Unix connects to your host in two ways: - SSH port opened in software and hardware firewalls. Default is 22. - - If you do not use Port 22, you can specify your SSH port in the Connection Profile + - If you don't use Port 22, you can specify your SSH port in the Connection Profile ### Commands for Non-Root Accounts -We recommend using the root account to run Enterprise Auditor against a Unix system. However, if -that is not acceptable all the commands we leverage in the solution set are below and can be used to -implement least privilege: +Netwrix recommends using the root account to run Enterprise Auditor against a Unix system. However, +if that isn't acceptable, the following commands used in the solution set implement least +privilege: All Perl scripts require the account to be able to execute the following commands: @@ -118,7 +118,7 @@ environment to run the following commands: - `cat /etc/security/user` (read access) - `cat /etc/shadow` - - Requires root or customization to job to utilize sudo without password prompt (:NOPASSWD) + - Requires root or customization to job to use sudo without password prompt (:NOPASSWD) - `egrep /etc/security/user` (read access) - `egrep /etc/login.defs` (read access) @@ -150,8 +150,8 @@ The 2.PrivilegedAccess > Sudoers > 0.Collection > UX_ParseSudoers Job requires p Unix environment to run the following commands: :::note -To parse sudoers we either need root or an account that has access to use sudo without -password prompt (:NOPASSWD) +To parse sudoers, the account needs root access or access to use sudo without a +password prompt (:NOPASSWD). ::: diff --git a/docs/accessanalyzer/11.6/requirements/unix/unix.md b/docs/accessanalyzer/11.6/requirements/unix/unix.md index 3012e2b3db..3a728755a5 100644 --- a/docs/accessanalyzer/11.6/requirements/unix/unix.md +++ b/docs/accessanalyzer/11.6/requirements/unix/unix.md @@ -19,7 +19,7 @@ topic for target environment requirements. **RAM, CPU, and Disk Space** -These are dependent upon the size of the target environment: +These depend on the size of the target environment: | Environment | Large | Medium – Small | | ----------- | ------ | -------------- | @@ -31,7 +31,7 @@ These are dependent upon the size of the target environment: **RAM, CPU, and Disk Space** -These are dependent upon the size of the target environment. +These depend on the size of the target environment. | Environment | Large | Medium – Small | | ------------------------ | ------ | -------------- | diff --git a/docs/accessanalyzer/11.6/requirements/windows/windows.md b/docs/accessanalyzer/11.6/requirements/windows/windows.md index d7b2c400a4..45c0b16b47 100644 --- a/docs/accessanalyzer/11.6/requirements/windows/windows.md +++ b/docs/accessanalyzer/11.6/requirements/windows/windows.md @@ -19,7 +19,7 @@ topic for target environment requirements. **RAM, CPU, and Disk Space** -These are dependent upon the size of the target environment: +These depend on the size of the target environment: | Environment | Large | Medium – Small | | ----------- | ------ | -------------- | @@ -31,7 +31,7 @@ These are dependent upon the size of the target environment: **RAM, CPU, and Disk Space** -These are dependent upon the size of the target environment. +These depend on the size of the target environment. | Environment | Large | Medium – Small | | ------------------------ | ------ | -------------- | diff --git a/docs/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/configuration.md b/docs/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/configuration.md index b9848b1bf1..633226a714 100644 --- a/docs/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/configuration.md +++ b/docs/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/configuration.md @@ -11,7 +11,7 @@ edit, and remove sub-criteria information for User Criteria. ![Configuration Pane](/images/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/configurationpanesystemcriteria.webp) -The information in the configuration pane changes based on the criteria currently selected in the +The information in the configuration pane changes based on the criteria selected in the navigation pane. ![Options at the top of the configuration pane](/images/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/configurationpanetop.webp) @@ -19,7 +19,7 @@ navigation pane. The options at the top of the Configuration Pane are: :::note -Configuration settings for System Criteria cannot be modified. +Configuration settings for System Criteria can't be modified. ::: @@ -40,7 +40,7 @@ Configuration settings for System Criteria cannot be modified. - The risk score can be set to **Low**, **Medium**, or **High** - Click the **Risk Score** button to change the risk score for user-configured criteria -- Required matched criteria list – Lists the sub-criteria configured for the currently selected +- Required matched criteria list – Lists the sub-criteria configured for the selected top-level criteria in the navigation pane. The columns in the table are: - Name – Name of the sub-criteria @@ -54,7 +54,7 @@ Configuration settings for System Criteria cannot be modified. The options at the bottom of the configuration pane are: :::note -Configuration settings for System Criteria cannot be modified. +Configuration settings for System Criteria can't be modified. ::: @@ -67,7 +67,7 @@ Configuration settings for System Criteria cannot be modified. - [Summary Criteria](/docs/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/summary.md) - Remove – Remove sub-criteria from the Required matched sub-criteria list -- Edit – Edit the currently selected sub-criteria +- Edit – Edit the selected sub-criteria - Must match at least this many criteria – Adjust the slider to configure how many sub-criteria must be matched for the sensitive data criteria to be reported @@ -76,13 +76,13 @@ Configuration settings for System Criteria cannot be modified. required matched criteria list :::warning - The character distance feature does not account for summaries that are nested + The character distance feature doesn't account for summaries that are nested within other summaries. ::: - Matches should be within this proximity of characters – Match hits for this criteria should be - within this many characters of one another in order for there to be a match. Adjust the slider to + within this many characters of one another for a match to occur. Adjust the slider to set the default character distance required for match hits. - The minimum value is 0 @@ -90,15 +90,15 @@ Configuration settings for System Criteria cannot be modified. - Using this feature requires any combination of two or more Regular Expression (Pattern) and Keyword sub-criteria -- Include keywords as part of match hits – Select this option to enable the inclusion of keywords as +- Include keywords as part of match hits – Select this option to include keywords as part of match hits. This option determines whether a match found based on a Keyword Criteria is reported as a match hit. When this option is selected, any matches found for a word in the Keyword - list is reported as match hit. If this option is not selected, then only matches found based on + list is reported as match hit. If this option isn't selected, then only matches found based on Pattern or child Summary Criteria are reported as a match hit. - Metadata for this criteria – Click the green plus (**+**) button to add a new metadata type for the criteria. Delete a metadata type by clicking the **X** button in the gray metadata tag. - - For a list of available out-of-the-box metadata tags, see the + - For a list of available default metadata tags, see the [Default Metadata Tag Values](/docs/accessanalyzer/11.6/sensitivedatadiscovery/metadatatags.md) topic for additional information @@ -116,8 +116,8 @@ The options in the Criteria Tester are: - Use the following sample text – Enter sample text to test against current configured criteria in the **Use the following sample text** textbox - Use the following file – Click **Browse** to import a file as sample text to test against - currently configured criteria -- Test Data – Click **Test Data** to test the sample text against currently configured criteria. + configured criteria +- Test Data – Click **Test Data** to test the sample text against configured criteria. Match hits show in the **Test Results** section. - Test Results – Displays match hits for the sample text typed into the text box. The two tabs under Test Results are: diff --git a/docs/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/keyword.md b/docs/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/keyword.md index 2f5bb7c9ef..addcc80468 100644 --- a/docs/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/keyword.md +++ b/docs/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/keyword.md @@ -21,8 +21,8 @@ The options on the Keywords window are: - Match Type – Choose whether keyword matches for the Keyword criteria **Must match** or **Must not match** - Case Sensitive Keywords – If enabled, checks letter case when matching keywords -- Count only distinct occurrences – Select the checkbox to enable only distinct occurrences to be - counted during scan jobs +- Count only distinct occurrences – Select the checkbox to count only distinct occurrences during + scan jobs - Apply these keywords to these file components – Select which file components the keywords apply to: diff --git a/docs/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/overview.md b/docs/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/overview.md index 8194843a3d..96c11db28f 100644 --- a/docs/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/overview.md +++ b/docs/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/overview.md @@ -6,10 +6,10 @@ sidebar_position: 50 # Sensitive Data Criteria Editor -The Sensitive Data Criteria Editor is accessed from the Criteria Tab in the -**Settings** > **Sensitive Data** node. Use the Sensitive Data Criteria Editor to view pre-defined -criteria and to customize or create user-defined criteria. Sensitive Data Criteria can be configured -in individual data collectors that use the Sensitive Data Discovery Add-On or can be configured to +Access the Sensitive Data Criteria Editor from the Criteria tab in the +**Settings** > **Sensitive Data** node. Use it to view pre-defined +criteria and to customize or create user-defined criteria. You can configure Sensitive Data Criteria +in individual data collectors that use the Sensitive Data Discovery Add-On, or configure them to inherit Sensitive Data Criteria settings from the **Settings** > **Sensitive Data** node. See the [Sensitive Data](/docs/accessanalyzer/11.6/admin/settings/sensitivedata/overview.md) topic for additional information. @@ -18,10 +18,9 @@ topic for additional information. The Sensitive Data Criteria Editor contains two sections: -- Navigation pane – User-configured criteria can be added and removed in the navigation pane using - the Add or Remove options. See the [Navigation Pane](#navigation-pane) topic for additional - information. -- Configuration pane – Displays configured settings for the currently selected criteria in the +- Navigation pane – Add or remove user-configured criteria using the Add or Remove options. See the + [Navigation Pane](#navigation-pane) topic for additional information. +- Configuration pane – Displays configured settings for the selected criteria in the navigation pane. See the [Configuration Pane](/docs/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/configuration.md) topic for additional information. @@ -42,6 +41,6 @@ The options in the Navigation Pane are: [Sensitive Data System Criteria](/docs/accessanalyzer/11.6/sensitivedatadiscovery/systemcriteria.md) topic for additional information. - - System Criteria cannot be modified or removed. To use existing System Criteria configurations - in a User Criteria, right-click on a System Criteria and select **Duplicate** from the + - System Criteria can't be modified or removed. To use existing System Criteria configurations + in a User Criteria, right-click a System Criteria and select **Duplicate** from the right-click menu. A configurable copy of the System Criteria appears under User Criteria. diff --git a/docs/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/regularexpression.md b/docs/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/regularexpression.md index 2d04bbc35a..15e7d8403e 100644 --- a/docs/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/regularexpression.md +++ b/docs/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/regularexpression.md @@ -7,7 +7,7 @@ sidebar_position: 20 # Regular Expression (Pattern) Criteria Regular Expression criteria are a set of pattern matching rules that provide a concise and flexible -means for matching strings of text. This criteria type can be used to verify a series of numbers as +means for matching strings of text. Use this criteria type to verify a series of numbers as potentially valid, for example credit card numbers. ![Regular Expression window](/images/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/criteriatype/regularexpression.webp) @@ -18,7 +18,7 @@ The options on the Regular Expression window are: - Expression – Enter the Regular Expression in the Expression text box - Case Sensitive Expression – Select the checkbox for case sensitive Regular Expression pattern matching -- Validation – Select a validation method from the Validation drop-down. The default value is **No +- Validation – Select a validation method from the Validation dropdown. The default value is **No validation required**. :::note @@ -35,9 +35,9 @@ The options on the Regular Expression window are: - Match Type – Choose whether pattern matches for the Regular Expression criteria **Must match** or **Must not match** - - Must match – The Regular Expression must be matched for there to be a match - - Must not match – If the Regular Expression is matched and is designated **Must not match**, - then the potential match is invalidated + - Must match – The criteria counts as a match only if the Regular Expression matches + - Must not match – If the Regular Expression matches while set to **Must not match**, the + potential match is invalid - Apply this expression to these file components – Select which file components the expression applies to: diff --git a/docs/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/summary.md b/docs/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/summary.md index 19eab66527..e0ed6152c1 100644 --- a/docs/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/summary.md +++ b/docs/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/summary.md @@ -6,8 +6,7 @@ sidebar_position: 40 # Summary Criteria -Summary criteria are designed as a way of combining Regular Expression (Pattern) criteria and -Keyword criteria. +Summary criteria combine Regular Expression (Pattern) criteria and Keyword criteria. ![Edit new Summary criteria](/images/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/criteriatype/newsummarycriteria.webp) @@ -23,7 +22,7 @@ The options on the Summary criteria configuration page are: See the [Criteria Tester Window](/docs/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/configuration.md#criteria-tester-window) topic for additional information. -- Required matched criteria – Lists sub-criteria configured for currently selected criteria in the +- Required matched criteria – Lists sub-criteria configured for selected criteria in the navigation pane. The columns in the table are: - Name – Name of the sub-criteria @@ -35,7 +34,7 @@ The options on the Summary criteria configuration page are: - Add – Add a sub-criteria to the required matched criteria list. The three types of sub-criteria that can be added are **Keyword**, **Pattern**, and **Summary**. - Remove – Remove the selected sub-criteria from the Required matched criteria list -- Edit – Edit the currently selected sub-criteria +- Edit – Edit the selected sub-criteria - Match Type – Choose whether match hits for the Summary criteria **Must match** or **Must not match** - Must match at least this many criteria – Adjust the slider to configure how many sub-criteria must @@ -46,7 +45,7 @@ The options on the Summary criteria configuration page are: Required matched criteria list :::warning -The character distance feature does not account for summaries that are nested within +The character distance feature doesn't account for summaries that are nested within other summaries. ::: @@ -62,4 +61,4 @@ other summaries. - Include keywords as part of match hits – Select this checkbox to enable the inclusion of keywords as part of match hits - Cancel – Exit the Sensitive Data Criteria Editor without saving changes -- Save – Save changes made to the currently selected criteria +- Save – Save changes made to the selected criteria diff --git a/docs/accessanalyzer/11.6/sensitivedatadiscovery/overview.md b/docs/accessanalyzer/11.6/sensitivedatadiscovery/overview.md index 16bac42cf7..4a60dc34e3 100644 --- a/docs/accessanalyzer/11.6/sensitivedatadiscovery/overview.md +++ b/docs/accessanalyzer/11.6/sensitivedatadiscovery/overview.md @@ -10,7 +10,7 @@ The Sensitive Data Discovery Add-On allows Enterprise Auditor to scan file conte the sensitive data criteria. There are several pre-defined criteria, but you can also customize existing criteria or create new criteria. -The Sensitive Data Discovery Add-on can be used with any of the following Enterprise Auditor +You can use the Sensitive Data Discovery Add-on with any of the following Enterprise Auditor solutions: - AWS Solution @@ -44,10 +44,9 @@ Sensitive Data Discovery Add-on. :::note The Sensitive Data Discovery Add-on installation package installs the appropriate JDK -(Java) version on the server. The JDK deployed is prepackaged and does not require any -configuration; it has been preconfigured to work with Enterprise Auditor and should never be -customized through Java. It will not conflict with other JDKs or Java Runtimes in the same -environment. +(Java) version on the server. The JDK deployed is prepackaged and doesn't require any +configuration. The package preconfigures it to work with Enterprise Auditor, so never customize it +through Java. It doesn't conflict with other JDKs or Java Runtimes in the same environment. ::: diff --git a/docs/accessanalyzer/11.6/sensitivedatadiscovery/supportedformats.md b/docs/accessanalyzer/11.6/sensitivedatadiscovery/supportedformats.md index 77a2e4fdbe..0c2a7fbd7e 100644 --- a/docs/accessanalyzer/11.6/sensitivedatadiscovery/supportedformats.md +++ b/docs/accessanalyzer/11.6/sensitivedatadiscovery/supportedformats.md @@ -166,15 +166,15 @@ multimedia. The following file formats are supported as metadata only formats. ## Scans Against Files with no Extensions -Files with no extensions can be scanned by modifying the XML file for each job where this type of -scan is desired. Add the following line to the `PerScanExtraScanOptions` section of a job's XML +You can scan files with no extensions by modifying the XML file for each job where you want this +type of scan. Add the following line to the `PerScanExtraScanOptions` section of a job's XML script: ``` true ``` -This line must be added to a specific location within the XML script. See below: +Add this line to the specific location shown in the following XML script: ``` @@ -193,5 +193,5 @@ This line must be added to a specific location within the XML script. See below: ``` -Once this line has been added to the job's XML script and the XML file is saved, files with no +After you add this line to the job's XML script and save the XML file, files with no extensions are included in scans for the job. diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/ad_activitycollection.md b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/ad_activitycollection.md index a2b10a9d7c..4818f46fcc 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/ad_activitycollection.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/ad_activitycollection.md @@ -7,23 +7,23 @@ sidebar_position: 20 # 0.Collection > AD_ActivityCollection Job The AD_ActivityCollection Job located in the 0.Collection Job Group, imports data from the Netwrix -Activity Monitor logs into the Enterprise Auditor Database. Retention can be modified in the query +Activity Monitor logs into the Enterprise Auditor Database. You can modify retention in the query (120 days default). ![AD_ActivityCollection Job in the Jobs Tree](/images/accessanalyzer/11.6/solutions/activedirectory/activity/jobstree_1.webp) -There are two ways AD Activity data can be retrieved by Enterprise Auditor: +Enterprise Auditor can retrieve AD Activity data in two ways: - Network share containing the archive logs - API Server connected to the archive logs -This is configured in the query. See the -[Queries for the AD_ActivityCollection Job](#queries-for-the-ad_activitycollection-job) topic for +You configure this in the query. See the +[Queries for the AD_ActivityCollection Job](#queries-for-the-adactivitycollection-job) topic for additional information. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +With the Configuration section on a job's overview page, you can modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/11.6/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -48,7 +48,7 @@ The AD_ActivityCollection page has the following configurable parameters: - Number of days to retain activity data in the AIC See the -[Customize Analysis Parameters for the AD_ActivityCollection Job](#customize-analysis-parameters-for-the-ad_activitycollection-job) +[Customize Analysis Parameters for the AD_ActivityCollection Job](#customize-analysis-parameters-for-the-adactivitycollection-job) topic for additional information. ## Queries for the AD_ActivityCollection Job @@ -57,8 +57,8 @@ The AD Activity Collection query uses the ADActivity Data Collector to target th archive logs for AD Activity. :::note -The query can be configured to connect directly to the network share where the archive -logs are stored or the API Server. +You can configure the query to connect directly to the network share where the archive +logs are stored, or to the API Server. ::: @@ -70,9 +70,8 @@ The AD_ActivityCollection Job uses the ADActivity Data Collector for the followi ### Configure the Query to Import from the Activity Monitor -The AD_ActivityCollection Job requires configuration to collect data. Follow the steps to modify the -query configuration when Netwrix Activity Monitor is configured to host domain activity logs on an -API server. +The AD_ActivityCollection Job requires configuration to collect data. Modify the query configuration +when Netwrix Activity Monitor is configured to host domain activity logs on an API server. :::note Ensure the Activity Monitor API Server and the required Connection Profile are @@ -116,10 +115,10 @@ last step. - Absolute Timespan – Set the date range for activity logs to collect when the scan is run :::info -The threshold should be set to ensure the logs are collected before the Activity +Set the threshold to ensure the logs are collected before the Activity Monitor domain output log retention expires. For example, if Enterprise Auditor runs the -**AD_ActivityCollection** Job once a week (every 7 days), then the Activity Monitor output should be -configured to retain at least 10 days of log files. +**AD_ActivityCollection** Job once a week (every 7 days), configure the Activity Monitor output to +retain at least 10 days of log files. ::: @@ -139,14 +138,12 @@ Credential with the Refresh token: - Click **OK** to save and close the User Credentials window. - Click **Save** and then **OK** to confirm the changes to the Connection Profile. -The query is now configured to target the Activity Monitor API Server to collect domain activity -logs. +The query now targets the Activity Monitor API Server to collect domain activity logs. ### Configure the Query to Import from a Share -The AD_ActivityCollection Job requires configuration to collect data. Follow the steps to modify the -query configuration when Netwrix Activity Monitor is configured to store activity logs on a network -share. +The AD_ActivityCollection Job requires configuration to collect data. Modify the query configuration +when Netwrix Activity Monitor is configured to store activity logs on a network share. :::note Ensure the Activity Monitor domain output and the required Connection Profile are @@ -182,10 +179,10 @@ Click **Next**. - Absolute Timespan – Set the date range for activity logs to collect when the scan is run :::info -The threshold should be set to ensure the logs are collected before the Activity +Set the threshold to ensure the logs are collected before the Activity Monitor domain output log retention expires. For example, if Enterprise Auditor runs the -**AD_ActivityCollection** Job once a week (every 7 days), then the Activity Monitor output should be -configured to retain at least 10 days of log files. +**AD_ActivityCollection** Job once a week (every 7 days), configure the Activity Monitor output to +retain at least 10 days of log files. ::: @@ -196,8 +193,8 @@ keeps the collected data in the SQL Server database. **Step 9 –** Click **OK** to save the changes and close the Query Properties page. -The query is now configured to target the network share where the Activity Monitor domain activity -logs are archived. +The query now targets the network share where the Activity Monitor domain activity logs are +archived. ## Analysis Tasks for the AD_ActivityCollection Job @@ -205,7 +202,7 @@ Navigate to the **Jobs** > **Active Directory** > **6.Activity** > **0.Collecti **AD_ActivityCollection** Job. Select the **Configure** > **Analysis** node. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -218,9 +215,9 @@ The following analysis tasks are selected by default: - AIC Import - AD Activity Events – Imports AD events to the Access Information Center for domain objects - - The `@ADEvents` and `@AuthEvents` parameters must be enabled for AD events and authentication - events to be imported into the Access Information Center - - The list of attributes to track for Object Modified changes can be customized by the + - You must enable the `@ADEvents` and `@AuthEvents` parameters to import AD events and + authentication events into the Access Information Center + - You can customize the list of attributes to track for Object Modified changes using the `#modifiedAttributeList` parameter - AIC Import - Activity Retention – Deletes older activity data from the Access Information Center @@ -229,7 +226,7 @@ The following analysis tasks are selected by default: ### Customize Analysis Parameters for the AD_ActivityCollection Job -The customizable parameters for this job allow you to configure importing of AD activity data into +Use the customizable parameters for this job to configure how the job imports AD activity data into the Netwrix Access Information Center. | Analysis Task | Customizable Parameter Name | Default Value | Value Indicates | diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/ad_ldapqueries.md b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/ad_ldapqueries.md index 40792972f0..af765ff756 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/ad_ldapqueries.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/ad_ldapqueries.md @@ -7,8 +7,8 @@ sidebar_position: 50 # LDAP > AD_LDAPQueries Job The **LDAP** > **AD_LDAPQueries** Job analyzes LDAP traffic to determine trends such as most -expensive queries, most active servers and users, successful/failed and signing status. This data -can be used to troubleshoot performance issues, load balancing, and poorly configured services. +expensive queries, most active servers and users, successful/failed and signing status. Use this +data to troubleshoot performance issues, load balancing, and poorly configured services. ![AD_LDAPQueries Job in the Jobs Tree](/images/accessanalyzer/11.6/solutions/activedirectory/activity/ldapjobstree.webp) @@ -23,7 +23,7 @@ Navigate to the **Active Directory** > **6.Activity** > **LDAP** > **AD_LDAPQuer **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Except for the **Largest Queries** task, do not modify or deselect the remaining +Except for the **Largest Queries** task, don't modify or deselect the remaining selected analysis tasks. The remaining analysis tasks are preconfigured for this job. ::: @@ -38,7 +38,7 @@ The following non-configurable analysis tasks are selected by default: - User Summary – Creates the SA_AD_LDAPQueries_UserSummary table accessible under the job’s Results node -The following configurable analysis task can be optionally enabled: +You can enable the following configurable analysis task: - Largest Queries – Creates the SA_AD_LDAPQueries_ExpensiveQueries table accessible under the job’s Results node @@ -54,10 +54,9 @@ pre-configured reports: ### Configure the Largest Queries Analysis Task -Customizable parameters enable you to set the values used to control the minimum objects returned -and the days of traffic to analyze during this job’s analysis. The parameters can be customized and -are listed in a section at the bottom of the SQL Script Editor. Follow the steps to customize an -analysis task’s parameters. +Use customizable parameters to set the values used to control the minimum objects returned +and the days of traffic to analyze during this job’s analysis. You can customize the parameters; +they're listed in a section at the bottom of the SQL Script Editor. **Step 1 –** Navigate to the **Active Directory** > **6.Activity** > **LDAP** > **AD_LDAPQueries** > **Configure** node and select **Analysis**. @@ -68,14 +67,14 @@ analysis task’s parameters. **Analysis Configuration**. The SQL Script Editor opens. :::warning -Do not change any parameters where the Value states `Created during execution`. +Don't change any parameters where the Value states `Created during execution`. ::: ![Largest Queries analysis task in the SQL Script Editor](/images/accessanalyzer/11.6/solutions/activedirectory/activity/ldapsqlscripteditor.webp) **Step 3 –** In the parameters section at the bottom of the editor, find the Value column. There are -two integer variables that can be modified. Double-click on the current **value** and change as +two integer variables you can modify. Double-click the current **value** and change as desired: - @objects_returned – Controls the minimum number of objects returned for the queries to be diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/ad_lockouts.md b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/ad_lockouts.md index 7c70020cb6..3948f46b80 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/ad_lockouts.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/ad_lockouts.md @@ -7,7 +7,7 @@ sidebar_position: 60 # Lockouts > AD_Lockouts Job The **Lockouts** > **AD_Lockouts** Job provides a listing of all account lockouts. For any lockout -occurring in the past 30 days, failed authentications and host information is provided to aid +occurring in the past 30 days, it also provides failed authentications and host information to aid troubleshooting. ![AD_Lockouts Job in the Jobs Tree](/images/accessanalyzer/11.6/solutions/activedirectory/activity/lockoutsjobstree.webp) @@ -23,7 +23,7 @@ Navigate to the **Active Directory** > **6.Activity** > **Lockouts** > **AD_Lock **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -42,4 +42,4 @@ pre-configured reports: | Report | Description | Default Tags | Report Elements | | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Lockouts | This report tracks all lockouts for user accounts. For any lockout occurring in the past 30 days, failed authentications and host information are provided to aid troubleshooting. | CCPA GDPR SOX HIPPA PCI-DSS GLBA ITAR FERPA FISMA ISO27001 | This report is comprised of two elements:
  • Table – Displays account lockouts details
  • Table –  Displays failed authentications in the past 30 days
| +| Lockouts | This report tracks all lockouts for user accounts. For any lockout occurring in the past 30 days, it also lists failed authentications and host information to aid troubleshooting. | CCPA GDPR SOX HIPPA PCI-DSS GLBA ITAR FERPA FISMA ISO27001 | This report is comprised of two elements:
  • Table – Displays account lockouts details
  • Table –  Displays failed authentications in the past 30 days
| diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/changes/ad_computermodifications.md b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/changes/ad_computermodifications.md index 742de2d4cf..3f2b42b6a5 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/changes/ad_computermodifications.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/changes/ad_computermodifications.md @@ -14,7 +14,7 @@ Navigate to the **Active Directory** > **6.Activity** > **Changes** > **AD_Compu **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/changes/ad_groupmodifications.md b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/changes/ad_groupmodifications.md index 8d5e1c2864..20945a87ea 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/changes/ad_groupmodifications.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/changes/ad_groupmodifications.md @@ -6,9 +6,9 @@ sidebar_position: 20 # AD_GroupModifications Job -The AD_GroupModifications Job provides a report of all changes to group objects. A separate report -is provided to highlight group membership changes. The list of top perpetrators can be used to -identify out of band changes. +The AD_GroupModifications Job provides a report of all changes to group objects, and a separate +report to highlight group membership changes. Use the list of top perpetrators to identify +out of band changes. ## Analysis Tasks for the AD_GroupModifications Job @@ -16,7 +16,7 @@ Navigate to the **Jobs** > **Active Directory** > **6.Activity** > **Changes** > **AD_GroupModifications** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/changes/ad_usermodifications.md b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/changes/ad_usermodifications.md index 6d9d04f211..8632665f30 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/changes/ad_usermodifications.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/changes/ad_usermodifications.md @@ -14,7 +14,7 @@ Navigate to the **Jobs** > **Active Directory** > **6.Activity** > **Changes** > **AD_UserModifications** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/changes/overview.md b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/changes/overview.md index 128f6eaa2f..398724398d 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/changes/overview.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/changes/overview.md @@ -6,7 +6,7 @@ sidebar_position: 30 # Changes Job Group -The Changes Job Group provides an audit trail for changes made to Computer, Group and User objects +The Changes Job Group provides an audit trail for changes made to Computer, Group, and User objects within the environment. ![Changes Job Group in the Jobs Tree](/images/accessanalyzer/11.6/solutions/activedirectory/activity/changes/jobstree.webp) diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/groupusage/ad_accesschanges.md b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/groupusage/ad_accesschanges.md index 2aa638f403..4ec081892d 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/groupusage/ad_accesschanges.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/groupusage/ad_accesschanges.md @@ -16,7 +16,7 @@ Navigate to the **Jobs** > **Active Directory** > **6.Activity** > **Group Usage **AD_AccessChanges** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/groupusage/ad_grouphosts.md b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/groupusage/ad_grouphosts.md index 61d83689b8..1487813e1a 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/groupusage/ad_grouphosts.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/groupusage/ad_grouphosts.md @@ -14,7 +14,7 @@ Navigate to the **Jobs** > **Active Directory** > **6.Activity** > **GroupUsage* **AD_GroupHosts** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -35,4 +35,4 @@ following pre-configured reports: | Report | Description | Default Tags | Report Elements | | ---------------- | ------------------------------------------------------------------- | ---------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Group Host Usage | Understand what groups are utilizing what hosts in the environment. | CCPA GDPR SOX HIPPA PCI-DSS GLBA ITAR FERPA FISMA ISO27001 | This report is comprised of three elements:
  • Table – Displays security groups by target hosts
  • Table – Displays hosts by associated groups
  • Table – Displays authentication details
| +| Group Host Usage | Understand what groups are using what hosts in the environment. | CCPA GDPR SOX HIPPA PCI-DSS GLBA ITAR FERPA FISMA ISO27001 | This report is comprised of three elements:
  • Table – Displays security groups by target hosts
  • Table – Displays hosts by associated groups
  • Table – Displays authentication details
| diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/groupusage/ad_groupmemberactivity.md b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/groupusage/ad_groupmemberactivity.md index 35c0b9ae78..be3415fcd5 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/groupusage/ad_groupmemberactivity.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/groupusage/ad_groupmemberactivity.md @@ -32,9 +32,9 @@ follow pre-configured report: ### Configure the Group Member Activity Analysis Task -Customizable parameters enable you to set the values used to include the SIDs for admin groups +Use customizable parameters to set the values used to include the SIDs for admin groups during this job’s analysis. The parameters can be customized and are listed in a section at the -bottom of the SQL Script Editor. Follow the steps to customize an analysis task’s parameters. +bottom of the SQL Script Editor. **Step 1 –** Navigate to the **Active Directory** > **6.Activity** > **Group Usage** > **AD_GroupMemberActivity** > **Configure** node and select **Analysis**. @@ -42,10 +42,10 @@ bottom of the SQL Script Editor. Follow the steps to customize an analysis task ![Group Member Activity analysis task configuration](/images/accessanalyzer/11.6/solutions/activedirectory/activity/groupusage/groupmemberactivityanalysisconfiguration.webp) **Step 2 –** In the Analysis Selection view, select the Group Member Activity analysis task and -click on **Analysis Configuration**. The SQL Script Editor opens. +click **Analysis Configuration**. The SQL Script Editor opens. :::warning -Do not change any parameters where the Value states `Created during execution`. +Don't change any parameters where the Value states `Created during execution`. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/ad_authenticationprotocol.md b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/ad_authenticationprotocol.md index 89590158e7..c367db4904 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/ad_authenticationprotocol.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/ad_authenticationprotocol.md @@ -16,7 +16,7 @@ Navigate to the **Active Directory** > **6.Activity** > **Operations** > tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/ad_domaincontrollertraffic.md b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/ad_domaincontrollertraffic.md index 4b5d53057b..bfc5e61a85 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/ad_domaincontrollertraffic.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/ad_domaincontrollertraffic.md @@ -7,7 +7,7 @@ sidebar_position: 20 # AD_DomainControllerTraffic Job The AD_DomainControllerTraffic Job provides a summary of the amount of traffic for Changes, -Authentication, Replication, and LDAP Queries for each domain controller which can be used to +Authentication, Replication, and LDAP Queries for each domain controller. Use this information to identify issues with load balancing. If the AD_DCSummary job has been run, the roles for each domain controller will be provided. @@ -18,7 +18,7 @@ Navigate to the **Active Directory** > **6.Activity** > **Operations** > tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/ad_hardcodeddcs.md b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/ad_hardcodeddcs.md index d0e5808b23..1cc5921c92 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/ad_hardcodeddcs.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/ad_hardcodeddcs.md @@ -14,7 +14,7 @@ Navigate to the **Active Directory** > **6.Activity** > **Operations** > **AD_Ha **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/ad_loadbalancing.md b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/ad_loadbalancing.md index 69f4347964..e113298039 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/ad_loadbalancing.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/ad_loadbalancing.md @@ -7,8 +7,8 @@ sidebar_position: 40 # AD_LoadBalancing Job The AD_LoadBalancing Job analyzes each domain controller's traffic to show what percent of all LDAP, -Replication, Authentication and Changes are being handled by that particular machine. This helps to -highlight domain controllers which are over utilized relative to others within the domain, or unused +Replication, Authentication, and Changes are being handled by that particular machine. This helps to +highlight domain controllers which are over used relative to others within the domain, or unused domain controllers which may be decommissioned. ## Analysis Task for the AD_LoadBalancing Job @@ -17,7 +17,7 @@ Navigate to the **Active Directory** > **6.Activity** > **Operations** > **AD_Lo **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/ad_machineowners.md b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/ad_machineowners.md index 1efa29f971..2782adcabf 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/ad_machineowners.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/ad_machineowners.md @@ -14,7 +14,7 @@ Navigate to the **Active Directory** > **6.Activity** > **Operations** > **AD_Ma **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/overview.md b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/overview.md index 1c8be7b00a..b1987b917c 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/overview.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/overview.md @@ -24,14 +24,14 @@ Schedule these jobs to run with the 0.Collection job group. identify what services and computers may be affected when disabling NTLM - [AD_DomainControllerTraffic Job](/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/ad_domaincontrollertraffic.md) – Provides a summary of the amount of traffic for Changes, Authentication, Replication, and LDAP - Queries for each domain controller which can be used to identify issues with load balancing. If + Queries for each domain controller. Use this summary to identify issues with load balancing. If the AD_DCSummary job has been run, the roles for each DC will be provided. - [AD_HardcodedDCs Job](/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/ad_hardcodeddcs.md) – Highlight machines that have communicated with only one DC - [AD_LoadBalancing Job](/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/ad_loadbalancing.md) – Analyzes each domain controller's traffic to show what percent of all LDAP, Replication, Authentication and Changes are being handled by that particular machine. This helps to highlight - domain controllers which are over utilized relative to others within the domain, or unused domain + domain controllers which are over used relative to others within the domain, or unused domain controllers which may be decommissioned. - [AD_MachineOwners Job](/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/ad_machineowners.md) – Helps to identify the owner of a particular host diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/overview.md b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/overview.md index f0ed2e14fc..ede2f08060 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/overview.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/overview.md @@ -27,7 +27,7 @@ The 6.Activity Job Group is comprised of the following jobs: – Imports data from the Netwrix Activity Monitor logs into the Enterprise Auditor Database. Retention can be modified in the query (120 days default). - [Changes Job Group](/docs/accessanalyzer/11.6/solutions/activedirectory/activity/changes/overview.md) - – Provides an audit trail for changes made to Computer, Group and User objects within the + – Provides an audit trail for changes made to Computer, Group, and User objects within the environment - [Group Usage Job Group](/docs/accessanalyzer/11.6/solutions/activedirectory/activity/groupusage/overview.md) – Shows how group membership changes have affected access across the entire environment, the @@ -35,10 +35,10 @@ The 6.Activity Job Group is comprised of the following jobs: in applications - [LDAP > AD_LDAPQueries Job](/docs/accessanalyzer/11.6/solutions/activedirectory/activity/ad_ldapqueries.md) – Analyzes LDAP traffic to determine trends such as most expensive queries, most active servers - and users, successful/failed and signing status. This data can be used to troubleshoot performance + and users, successful/failed and signing status. Use this data to troubleshoot performance issues, load balancing, and poorly configured services. - [Lockouts > AD_Lockouts Job](/docs/accessanalyzer/11.6/solutions/activedirectory/activity/ad_lockouts.md)– - Provides a listing of all account lockouts with relevant details which can be used to aid + Provides a listing of all account lockouts with relevant details to aid troubleshooting - [Operations Job Group](/docs/accessanalyzer/11.6/solutions/activedirectory/activity/operations/overview.md) – Reports on Active Directory activity events related to operational activity. This group can help diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/privilegedaccounts/ad_adminaccounts.md b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/privilegedaccounts/ad_adminaccounts.md index 828f547779..a30725e2ff 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/privilegedaccounts/ad_adminaccounts.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/privilegedaccounts/ad_adminaccounts.md @@ -14,7 +14,7 @@ Navigate to the **Jobs** > **Active Directory** > **6.Activity** > **Privileged **AD_AdminAccounts** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -41,9 +41,9 @@ follow pre-configured reports: ### Configure the Summarize Administrative Account Activity Analysis Task -Customizable parameters enable you to set the values used to include the NT Account name for admin -groups during this job’s analysis. The parameters can be customized and are listed in a section at -the bottom of the SQL Script Editor. Follow the steps to customize an analysis task’s parameters. +With the customizable parameters, you can set the values used to include the NT Account name for admin +groups during this job’s analysis. The parameters are listed in a section at +the bottom of the SQL Script Editor. Complete the following steps to customize an analysis task’s parameters. **Step 1 –** Navigate to the **Active Directory** > **6.Activity** > **Privileged Accounts** > **AD_AdminAccounts** > **Configure** node and select **Analysis**. @@ -54,7 +54,7 @@ the bottom of the SQL Script Editor. Follow the steps to customize an analysis t Activity** analysis task and click **Analysis Configuration**. The SQL Script Editor opens. :::warning -Do not change any parameters where the Value states `Created during execution`. +Don't change any parameters where the Value states `Created during execution`. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/privilegedaccounts/ad_serviceaccountauth.md b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/privilegedaccounts/ad_serviceaccountauth.md index 1ec147ee6f..1567a9d1bb 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/privilegedaccounts/ad_serviceaccountauth.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/privilegedaccounts/ad_serviceaccountauth.md @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **Active Directory** > **6.Activity** > **Operations* **AD_ServiceAccountAuth** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/recommended.md b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/recommended.md index d5f02c1d54..a53bcd163c 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/recommended.md @@ -7,19 +7,19 @@ sidebar_position: 10 # Recommended Configurations for the 6.Activity Job Group The **Active Directory** > **6.Activity** Job Group has been configured by default to run with the -out-of-the-box settings. It can be run directly or scheduled. +default settings. It can be run directly or scheduled. **Dependencies** - Successfully execute the **.Active Directory Inventory** Job Group - Netwrix Activity Monitor 4.1+ is archiving AD Activity Logs -- Successfully execute the **Active Directory** > **5.Domains Job Group** prior to running the +- Successfully execute the **Active Directory** > **5.Domains Job Group** before running the Operations Job Group - (Optional) Successfully execute the **Active Directory Permissions Analyzer** > **0.Collection** Job Group - (Optional) Successfully execute the **FileSystem** > **0.Collection** Job Group -**Targeted Host(s)** +**Targeted Hosts** Netwrix Activity Monitor API Server or the host with the network share housing archived log files. @@ -27,7 +27,7 @@ Netwrix Activity Monitor API Server or the host with the network share housing a Connection Profiles must be set directly on the [0.Collection > AD_ActivityCollection Job](/docs/accessanalyzer/11.6/solutions/activedirectory/activity/ad_activitycollection.md) -in order to connect to either the SAM API Server or the host with the network share housing the +to connect to either the SAM API Server or the host with the network share housing the archived log files. **Access Token** @@ -40,18 +40,18 @@ Required for SAM API Server integration for the This group can be scheduled to run as desired. :::info -Run from the 6.Activity Job Group level in order to correlate 0.Collection job +Run from the 6.Activity Job Group level to correlate 0.Collection job group data with other jobs. ::: **History Retention** -History is not supported. Turning on history will cause issues with data analysis and reporting. +History isn't supported. Turning on history will cause issues with data analysis and reporting. **Multi-Console Support** -Multiple Enterprise Auditor Consoles are not supported. This group should be run from a single +Multiple Enterprise Auditor Consoles aren't supported. This group should be run from a single Enterprise Auditor Console. **Workflow** @@ -70,7 +70,7 @@ Monitor API Server or the host with the network share housing the archived log f **Step 6 –** Run the jobs as desired. -**Step 7 –** Run from the **6.Activity** Job Group level in order to correlate 0.Collection job +**Step 7 –** Run from the **6.Activity** Job Group level to correlate 0.Collection job group data with other jobs. **Step 8 –** Review the reports generated by the jobs. diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/ad_securityassessment.md b/docs/accessanalyzer/11.6/solutions/activedirectory/ad_securityassessment.md index c26f6f04b8..74d976252b 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/ad_securityassessment.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/ad_securityassessment.md @@ -9,7 +9,7 @@ sidebar_position: 80 The AD_SecurityAssessment Job performs checks against Active Directory security best practices in order to proactively identify critical security configurations that leave Active Directory vulnerable to attack. The result are reports that provide a listing of findings by severity and -category with corresponding details that can be used to prioritize and remediate security issues. +category with corresponding details. Use these details to prioritize and remediate security issues. ![AD Security Assessment Job](/images/accessanalyzer/11.6/solutions/activedirectory/securityassessmentjobstree.webp) @@ -51,14 +51,14 @@ One or more of the following job groups or jobs must be run to produce results: - Windows > Privileged Accounts > Service Accounts > SG_ServiceAccounts :::note -If any of the above jobs are not completed, the AD_SecurityAssessment job will run but all +If any of the above jobs aren't completed, the AD_SecurityAssessment job will run but all checks will not be assessed. ::: **Target Host** -This job group does not collect data. No target host is required. +This job group doesn't collect data. No target host is required. **Connection Profile** @@ -70,11 +70,11 @@ Scheduled to run as desired **History Retention** -History is not supported. Turning on history will cause issues with data analysis and reporting. +History isn't supported. Turning on history will cause issues with data analysis and reporting. **Multi-console Support** -Multiple StealthAUDIT consoles are not supported. This job should be run from a single StealthAUDIT +Multiple StealthAUDIT consoles aren't supported. This job should be run from a single StealthAUDIT console. ## Analysis Task for the AD_SecurityAssessment Job @@ -83,7 +83,7 @@ Navigate to the **Jobs** > Active Directory > AD_SecurityAssessment > Configure **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/ad_cleanupprogress.md b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/ad_cleanupprogress.md index 516df64a9d..83938d4438 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/ad_cleanupprogress.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/ad_cleanupprogress.md @@ -9,7 +9,7 @@ sidebar_position: 50 The AD_CleanupProgress Job performs checks against Active Directory security best practices in order to proactively identify critical security configurations that leave Active Directory vulnerable to attack. The result is a report which provides a listing of findings by severity and category with -corresponding details that can be used to prioritize and remediate security issues. +corresponding details. Use these details to prioritize and remediate security issues. ![AD_CleanupProgress Job in the Jobs Tree](/images/accessanalyzer/11.6/solutions/activedirectory/cleanup/cleanupprogressjobstree.webp) @@ -17,8 +17,8 @@ corresponding details that can be used to prioritize and remediate security issu **Step 1 –** Ensure the following prerequisites are met: -- The .Active Directory Inventory Job Group needs to be successfully run prior to running this job -- The following jobs from the Active Directory Solution must be run prior to running this job: +- The .Active Directory Inventory Job Group needs to be successfully run before running this job +- The following jobs from the Active Directory Solution must be run before running this job: - **Active Directory** > **1.Groups** > **AD_DuplicateGroups** - **Active Directory** > **2.Users** > **AD_DirectMembership** @@ -35,7 +35,7 @@ Navigate to the **Active Directory** > **Cleanup** > **AD_CleanupProgress** > ** select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/computers/ad_deprovisioncomputers.md b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/computers/ad_deprovisioncomputers.md index 22251880b9..8a8bede5b2 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/computers/ad_deprovisioncomputers.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/computers/ad_deprovisioncomputers.md @@ -19,7 +19,7 @@ staging OU. The default is 365 days. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to easily modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/11.6/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -29,7 +29,7 @@ The AD_DeprovisionComputers page has the following configurable parameters: - Days in the Staging OU before Deleting Account See the -[Customizable Analysis Parameters for the AD_DeprovisionComputers Job](#customizable-analysis-parameters-for-the-ad_deprovisioncomputers-job) +[Customizable Analysis Parameters for the AD_DeprovisionComputers Job](#customizable-analysis-parameters-for-the-addeprovisioncomputers-job) topic for additional information. ## Analysis Tasks for the AD_DeprovisionComputers Job @@ -47,12 +47,12 @@ The default analysis tasks are: under the job’s Results node - This analysis task contains a configurable parameter: `@days_before_deleting`. See the - [Customizable Analysis Parameters for the AD_DeprovisionComputers Job](#customizable-analysis-parameters-for-the-ad_deprovisioncomputers-job) + [Customizable Analysis Parameters for the AD_DeprovisionComputers Job](#customizable-analysis-parameters-for-the-addeprovisioncomputers-job) topic for additional information. ### Customizable Analysis Parameters for the AD_DeprovisionComputers Job -Customizable parameters enable you to set the values used to classify user and group objects during +With the customizable parameters, you can set the values used to classify user and group objects during this job’s analysis. | Analysis Task | Customizable Parameter Name | Default Value | Value Indicates | @@ -69,7 +69,7 @@ Navigate to the **Active Directory** > **Cleanup** > **3.Computers** > **AD_Depr **Configure** node and select **Actions** to view the actions. :::warning -Do not enable the actions unless it is required. Disable the actions after execution to +Don't enable the actions unless it is required. Disable the actions after execution to prevent making unintended and potentially harmful changes to Active Directory. ::: @@ -85,7 +85,7 @@ The action tasks must be executed together and in order. - Move Computers – Move computers to staging OU for deletion - - The target staging OU must be set in the Move Computers Action Task prior to executing the + - The target staging OU must be set in the Move Computers Action Task before executing the action tasks. See the [Configure the Target OU](/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/configuretargetou.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/computers/ad_deprovisioncomputers_status.md b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/computers/ad_deprovisioncomputers_status.md index f0577c0c78..00b51f10f3 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/computers/ad_deprovisioncomputers_status.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/computers/ad_deprovisioncomputers_status.md @@ -16,7 +16,7 @@ Navigate to the **Active Directory** > **Cleanup** > **3.Computers** > tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/computers/overview.md b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/computers/overview.md index c62debf1a9..df604845b2 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/computers/overview.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/computers/overview.md @@ -24,10 +24,10 @@ The jobs in the 3.Computers Job Group are: - The .Active Directory Inventory Job Group needs to be successfully run - For the AD_DeprovisionComputers Job, the target OU needs to be manually set in the Move Computers - Action Task prior to executing the actions. See the - [Action Tasks for the AD_DeprovisionComputers Job](/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/computers/ad_deprovisioncomputers.md#action-tasks-for-the-ad_deprovisioncomputers-job) + Action Task before executing the actions. See the + [Action Tasks for the AD_DeprovisionComputers Job](/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/computers/ad_deprovisioncomputers.md#action-tasks-for-the-addeprovisioncomputers-job) topic for additional information. -- The AD_DeprovisionComputers Job needs to be run prior to running the +- The AD_DeprovisionComputers Job needs to be run before running the AD_DeprovisionComputers_Status Job **Step 2 –** Schedule the 3.Computers Job Group to run as desired after the prerequisites have been diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/configuretargetou.md b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/configuretargetou.md index a12d8a71f9..14055b233d 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/configuretargetou.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/configuretargetou.md @@ -6,13 +6,13 @@ sidebar_position: 60 # Configure the Target OU -Follow the steps to configure the target staging OU. +Complete the following steps to configure the target staging OU. **Step 1 –** Navigate to the **[Job]** > **Configure** > **Actions** node. ![Action Properties button on Action Selection page](/images/accessanalyzer/11.6/solutions/activedirectory/cleanup/configuretargetouactionproperties.webp) -**Step 2 –** On the Action Selection page, select the desired action task and click **Action +**Step 2 –** On the Action Selection page, select the action task you want and click **Action Properties**. **Step 3 –** In the Action Properties window, select **Configure Action**. The Active Directory @@ -21,8 +21,8 @@ Action Module Wizard opens. ![Move Objects page of the Active Directory Action Module Wizard](/images/accessanalyzer/11.6/solutions/activedirectory/cleanup/configuretargetouactionmodulewizard.webp) **Step 4 –** Navigate to the Move Objects page of the Active Directory Action Module Wizard. In the -OU field, enter or browse to the desired target OU. To create the target OU location, select the -**Create target OU location if it does not already exist** checkbox. +OU field, enter or browse to the target OU. To create the target OU location, select the +**Create target OU location if it doesn't already exist** checkbox. **Step 5 –** Navigate to the Summary page and click **Finish**. diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/deprovision/ad_deprovisiongroups.md b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/deprovision/ad_deprovisiongroups.md index 5c42d0c038..41cbf32a9d 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/deprovision/ad_deprovisiongroups.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/deprovision/ad_deprovisiongroups.md @@ -22,7 +22,7 @@ staging OU. The default is 365 days. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to easily modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/11.6/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -32,7 +32,7 @@ The AD_DeprovisionGroups page has the following configurable parameters: - Days in the Staging OU before deletion See the -[Customizable Analysis Parameters for the AD_DeprovisionGroups Job](#customizable-analysis-parameters-for-the-ad_deprovisiongroups-job) +[Customizable Analysis Parameters for the AD_DeprovisionGroups Job](#customizable-analysis-parameters-for-the-addeprovisiongroups-job) topic for additional information. ## Analysis Tasks for the AD_DeprovisionGroups Job @@ -49,12 +49,12 @@ The default analysis tasks are: - Groups to Delete – Identifies groups in the Stale Groups OU that are ready to be deleted - This analysis task contains a configurable parameter: `@days_before_deleting`. See the - [Customizable Analysis Parameters for the AD_DeprovisionGroups Job](#customizable-analysis-parameters-for-the-ad_deprovisiongroups-job) + [Customizable Analysis Parameters for the AD_DeprovisionGroups Job](#customizable-analysis-parameters-for-the-addeprovisiongroups-job) topic for additional information. ### Customizable Analysis Parameters for the AD_DeprovisionGroups Job -Customizable parameters enable you to set the values used to classify user and group objects during +With the customizable parameters, you can set the values used to classify user and group objects during this job’s analysis. | Analysis Task | Customizable Parameter Name | Default Value | Value Indicates | @@ -71,7 +71,7 @@ Navigate to the **Active Directory** > **Cleanup** > **1.Groups** > **1. Deprovi **AD_DeprovisonGroups** > **Configure** node and select **Actions** to view the action tasks. :::warning -Do not enable the actions unless it is required. Disable the actions after execution to +Don't enable the actions unless it is required. Disable the actions after execution to prevent making unintended and potentially harmful changes to Active Directory. ::: @@ -87,7 +87,7 @@ The action tasks must be executed together and in order. - Move Groups – Move groups to staging OU - - The target staging OU must be set in the Move Groups Action Task prior to executing the action + - The target staging OU must be set in the Move Groups Action Task before executing the action tasks. See the [Configure the Target OU](/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/configuretargetou.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/deprovision/ad_deprovisiongroups_status.md b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/deprovision/ad_deprovisiongroups_status.md index 9613603754..6ed94e556d 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/deprovision/ad_deprovisiongroups_status.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/deprovision/ad_deprovisiongroups_status.md @@ -15,7 +15,7 @@ Navigate to the **Active Directory** > **Cleanup** > **1.Groups** > **1. Deprovi tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis tasks is +Don't modify or deselect the selected analysis task. The analysis tasks is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/overview.md b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/overview.md index f39083e8ad..2c9753cc28 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/overview.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/overview.md @@ -39,10 +39,10 @@ The jobs in the 1.Groups Job Group are: - The .Active Directory Inventory Job Group needs to be successfully run - For the AD_DeprovisionGroups Job, the target OU needs to be manually set in the Move Groups Action - Task prior to executing the actions. See the - [Action Tasks for the AD_DepvisionGroups Job](/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/deprovision/ad_deprovisiongroups.md#action-tasks-for-the-ad_depvisiongroups-job) + Task before executing the actions. See the + [Action Tasks for the AD_DepvisionGroups Job](/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/deprovision/ad_deprovisiongroups.md#action-tasks-for-the-addepvisiongroups-job) topic for additional information. -- The AD_DeprovisionGroups Job needs to be run prior to running the AD_DeprovisionGroups_Status Job +- The AD_DeprovisionGroups Job needs to be run before running the AD_DeprovisionGroups_Status Job **Step 2 –** Schedule the 1.Groups Job Group to run as desired after the prerequisites have been satisfied. diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/stamping/ad_groupcleanup_permissions.md b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/stamping/ad_groupcleanup_permissions.md index eb71ac9160..5138ee2696 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/stamping/ad_groupcleanup_permissions.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/stamping/ad_groupcleanup_permissions.md @@ -7,7 +7,7 @@ sidebar_position: 10 # AD_GroupCleanup_Permissions Job The AD_GroupCleanup_Permissions Job reports on where security groups are being used to assign -permissions. This can be used to prioritize remediation for groups that are rarely used. +permissions. Use these results to prioritize remediation for groups that are rarely used. ## Analysis Tasks for the AD_GroupCleanup_Permissions Job @@ -16,7 +16,7 @@ Navigate to the **Active Directory** > **Cleanup** > **1.Groups** > **2. Group S tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/stamping/ad_groupstamping.md b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/stamping/ad_groupstamping.md index 0ed8a51880..4bbc60be9d 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/stamping/ad_groupstamping.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/stamping/ad_groupstamping.md @@ -16,7 +16,7 @@ Navigate to the **Active Directory** > **Cleanup** > **1.Groups** > **2. Group S AD_GroupStamping** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/recommended.md b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/recommended.md index 4ae21882f5..9238cbd6b6 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/recommended.md @@ -14,7 +14,7 @@ The Cleanup job group has the following prerequisites: - The Active Directory Actions license feature is required - The Active Directory Actions Module must be installed -- The .Active Directory Inventory Job Group needs to be successfully run prior to running this job +- The .Active Directory Inventory Job Group needs to be successfully run before running this job group - The following job groups from the Activity Directory job group need to be successfully run prior to running this job group: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/users/ad_deprovisionusers.md b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/users/ad_deprovisionusers.md index 7013cad81d..a3b6ae7d22 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/users/ad_deprovisionusers.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/users/ad_deprovisionusers.md @@ -11,11 +11,11 @@ accounts. **Step 1 –** Move stale users to a staging OU for deletion. -**Step 2 –** The assigned manager is alerted by email of the impending deletion. +**Step 2 –** Notify the assigned manager by email of the impending deletion. -**Step 3 –** User accounts are disabled. +**Step 3 –** Disable the user accounts. -**Step 4 –** Users are flagged as **To Be Deleted**. +**Step 4 –** Flag users as **To Be Deleted**. **Step 5 –** Delete users from the staging OU. @@ -23,7 +23,7 @@ accounts. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to easily modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/11.6/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -33,7 +33,7 @@ The AD_DeprovisionUsers page has the following configurable parameters: - Days in the Stale Users OU before being deleted See the -[Customizable Analysis Parameters for the AD_DeprovisionUsers Job](#customizable-analysis-parameters-for-the-ad_deprovisionusers-job) +[Customizable Analysis Parameters for the AD_DeprovisionUsers Job](#customizable-analysis-parameters-for-the-addeprovisionusers-job) topic for additional information. ## Analysis Tasks for the AD_DeprovisionUsers Job @@ -50,14 +50,14 @@ The default analysis tasks are: deleted - This analysis task contains a configurable parameter: `@days_before_deleting`. See the - [Customizable Analysis Parameters for the AD_DeprovisionUsers Job](#customizable-analysis-parameters-for-the-ad_deprovisionusers-job) + [Customizable Analysis Parameters for the AD_DeprovisionUsers Job](#customizable-analysis-parameters-for-the-addeprovisionusers-job) topic for additional information. - Identify Group Membership – Identifies stale user membership to remove ### Customizable Analysis Parameters for the AD_DeprovisionUsers Job -Customizable parameters enable you to set the values used to classify user and group objects during +With the customizable parameters, you can set the values used to classify user and group objects during this job’s analysis. | Analysis Task | Customizable Parameter Name | Default Value | Value Indicates | @@ -74,7 +74,7 @@ Navigate to the **Active Directory** > **Cleanup** > **2.Users** > **AD_Deprovis **Configure** node and select **Actions** to view the actions. :::warning -Do not enable the actions unless it is required. Disable the actions after execution to +Don't enable the actions unless it is required. Disable the actions after execution to prevent making unintended and potentially harmful changes to Active Directory. ::: @@ -90,7 +90,7 @@ The action tasks must be executed together and in order. - Move Users – Move users to staging OU for deletion - - The target OU must be set in the Move Users Action Task prior to executing the action tasks. + - The target OU must be set in the Move Users Action Task before executing the action tasks. See the [Configure the Target OU](/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/configuretargetou.md) topic for additional information. @@ -101,6 +101,6 @@ The action tasks must be executed together and in order. - Delete Users – Delete users from staging OU - Remove Membership – Remove stale users from all groups -After the `@days_before_deleting` analysis parameter has been configured and the target OU has been -set in the Move Users Action Task, select the checkboxes next to all of the action tasks and click +After you configure the `@days_before_deleting` analysis parameter and set the target OU in the Move +Users Action Task, select the checkboxes next to all of the action tasks and click **Execute Action** to execute the action tasks. diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/users/ad_deprovisionusers_status.md b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/users/ad_deprovisionusers_status.md index 702ebf0972..eb86ccec95 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/users/ad_deprovisionusers_status.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/users/ad_deprovisionusers_status.md @@ -14,7 +14,7 @@ Navigate to the **Active Directory** > **Cleanup** > **2.Users** > **AD_Deprovis **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/users/overview.md b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/users/overview.md index 914dfd7d34..3a4e314d16 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/users/overview.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/users/overview.md @@ -23,10 +23,10 @@ The jobs in the 2.Users Job Group are: - The .Active Directory Inventory Job Group needs to be successfully run - For the AD_DeprovisionUsers Job, the target OU needs to be manually set in the Move Users Action - Task prior to executing the actions. See the - [Action Tasks for the AD_DeprovisionUsers Job](/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/users/ad_deprovisionusers.md#action-tasks-for-the-ad_deprovisionusers-job) + Task before executing the actions. See the + [Action Tasks for the AD_DeprovisionUsers Job](/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/users/ad_deprovisionusers.md#action-tasks-for-the-addeprovisionusers-job) topic for additional information. -- The AD_DeprovisionUsers Job needs to be run prior to running the AD_DeprovisionUsers_Status Job +- The AD_DeprovisionUsers Job needs to be run before running the AD_DeprovisionUsers_Status Job **Step 2 –** Schedule the 2.Users Job Group to run as desired after the prerequisites have been satisfied. diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/computers/ad_computerdelegation.md b/docs/accessanalyzer/11.6/solutions/activedirectory/computers/ad_computerdelegation.md index 1b6cec31ac..46b85c6de0 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/computers/ad_computerdelegation.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/computers/ad_computerdelegation.md @@ -7,10 +7,10 @@ sidebar_position: 20 # AD_ComputerDelegation Job The AD_ComputerDelegation Job provides details on computer accounts that have been enabled for -unconstrained delegation. Once this configuration is enabled for a computer, any time an account +unconstrained delegation. After this configuration is enabled for a computer, any time an account connects to the computer for any reason, their ticket-granting ticket (TGT) is stored in memory so it can be used later by the computer for impersonation, which exposes a significant security risk in -cases where privileged accounts access the computer.  See the +cases where privileged accounts access the computer. See the [What Is Kerberos Delegation?](https://blog.netwrix.com/2021/11/30/what-is-kerberos-delegation-an-overview-of-kerberos-delegation/) Netwrix blog article for more information about this configuration and the related security risks. @@ -20,7 +20,7 @@ Navigate to the **Active Directory** > **3.Computers** > **AD_ComputerDelegation and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the analysis task. The analysis task is preconfigured for +Don't modify or deselect the analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/computers/ad_stalecomputers.md b/docs/accessanalyzer/11.6/solutions/activedirectory/computers/ad_stalecomputers.md index c594efb1b0..ddd1d00672 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/computers/ad_stalecomputers.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/computers/ad_stalecomputers.md @@ -10,7 +10,7 @@ The AD_StaleComputers Job provides details on stale computers that may be candid ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to easily modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/11.6/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -21,7 +21,7 @@ The AD_StaleComputers Job has the following configurable parameters: - Consider disabled accounts as stale See the -[Customizable Analysis Parameters for the AD_StaleComputers Job](#customizable-analysis-parameters-for-the-ad_stalecomputers-job) +[Customizable Analysis Parameters for the AD_StaleComputers Job](#customizable-analysis-parameters-for-the-adstalecomputers-job) topic for additional information. ## Analysis Tasks for the AD_StaleComputers Job @@ -30,7 +30,7 @@ Navigate to the **Active Directory** > **3.Computers** > **AD_StaleComputers** > and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the **2. Summarize by Domain** analysis task. This analysis +Don't modify or deselect the **2. Summarize by Domain** analysis task. This analysis task is preconfigured for this job. ::: @@ -64,7 +64,7 @@ Analysis parameters that can be customized have the following default values: | Analysis Task | Customizable Parameter Name | Default Value | Value Indicates | | --------------------------- | --------------------------- | ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 1. Identify Stale Computers | @days_since_last_logon | 90 | A computer object that has been inactive for 90 days or more | -| 1. Identify Stale Computers | @consider_disable | 1 | A computer object that has been disabled:
  • Value 1 = Disabled computers are included as stale
  • Value 0 = Disabled computers are not included as stale
| +| 1. Identify Stale Computers | @consider_disable | 1 | A computer object that has been disabled:
  • Value 1 = Disabled computers are included as stale
  • Value 0 = Disabled computers aren't included as stale
| See the diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/computers/overview.md b/docs/accessanalyzer/11.6/solutions/activedirectory/computers/overview.md index 5e6a6164cc..48ba09cf56 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/computers/overview.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/computers/overview.md @@ -14,11 +14,11 @@ computer accounts, including stale computers and computers that have been truste The following jobs comprise the 3.Computers Job Group: - [AD_ComputerDelegation Job](/docs/accessanalyzer/11.6/solutions/activedirectory/computers/ad_computerdelegation.md) - – Provides details on computer accounts that have been trusted for delegation. Once this + – Provides details on computer accounts that have been trusted for delegation. After this configuration is enabled for a computer, any time an account connects to the computer for any reason, their ticket-granting ticket (TGT) is stored in memory so it can be used later by the computer for impersonation, which exposes a significant security risk in cases where privileged - accounts access the computer.  See the + accounts access the computer. See the [What Is Kerberos Delegation?](https://blog.netwrix.com/2021/11/30/what-is-kerberos-delegation-an-overview-of-kerberos-delegation/) Netwrix blog article for more information about this configuration and the related security risks. - [AD_StaleComputers Job](/docs/accessanalyzer/11.6/solutions/activedirectory/computers/ad_stalecomputers.md) diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/computers/recommended.md b/docs/accessanalyzer/11.6/solutions/activedirectory/computers/recommended.md index 521cf0da01..8987a72571 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/computers/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/computers/recommended.md @@ -11,22 +11,22 @@ default settings. It can be run directly or scheduled. **Dependencies** -The **.Active Directory Inventory** Job Group needs to be successfully executed prior to running +The **.Active Directory Inventory** Job Group needs to be successfully executed before running this job group. **Target Host** -This job group does not collect data. No target host is required. +This job group doesn't collect data. No target host is required. **Connection Profile** -This job group does not collect data. No specific Connection Profile is required. +This job group doesn't collect data. No specific Connection Profile is required. **Schedule Frequency** -The data analyzed by the 3.Computers Job Group jobs is collected by the .Active Directory Inventory -Job Group. Therefore, it is recommended to schedule these jobs to run after the .Active Directory -Inventory job group collection has completed. These jobs can be scheduled to run as desired. +The .Active Directory Inventory Job Group collects the data that the 3.Computers Job Group jobs +analyze. Schedule the 3.Computers Job Group jobs to run after the .Active Directory Inventory job +group collection completes. You can schedule these jobs to run as desired. **Run at the Job Group Level** diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/domains/ad_dcsummary.md b/docs/accessanalyzer/11.6/solutions/activedirectory/domains/ad_dcsummary.md index 7572950163..3d7330e5b0 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/domains/ad_dcsummary.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/domains/ad_dcsummary.md @@ -16,7 +16,7 @@ Navigate to the **Active Directory > 5.Domains > AD_DCSummary > Configure** node **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/domains/ad_domaininfo.md b/docs/accessanalyzer/11.6/solutions/activedirectory/domains/ad_domaininfo.md index eb7242a3bc..ff9ea4d9b6 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/domains/ad_domaininfo.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/domains/ad_domaininfo.md @@ -16,7 +16,7 @@ The AD_DomainInfo Job uses the ActiveDirectory Data Collector and the LDAP Data following queries: :::warning -Do not modify the queries. The queries are preconfigured for this job. +Don't modify the queries. The queries are preconfigured for this job. ::: @@ -42,7 +42,7 @@ Navigate to the **Active Directory > 5.Domains > AD_DomainInfo > Configure** nod **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/domains/ad_dsrmsettings.md b/docs/accessanalyzer/11.6/solutions/activedirectory/domains/ad_dsrmsettings.md index 81772ef3bc..49bfd078eb 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/domains/ad_dsrmsettings.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/domains/ad_dsrmsettings.md @@ -6,10 +6,11 @@ sidebar_position: 50 # AD_DSRMSettings Job -The AD_DRSMSettings Job provides details on domain controller registry settings for the -DSRMAdminLogonBehavior key. If this key is set to 1 or 2, the DSRM Admin Account can be used to log -in to the domain controller even if it has not been started in DSRM which can present a potential -security vulnerability. Additional information on this registry key is available in this +The AD_DSRMSettings Job provides details on domain controller registry settings for the +DSRMAdminLogonBehavior key. If this key is set to 1 or 2, you can use the Directory Services Restore +Mode (DSRM) Admin Account to log in to the domain controller even if it has not been started in +DSRM, which can present a potential security vulnerability. Additional information on this +registry key is available in this [Microsoft Document](https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc732714(v=ws.10)?redirectedfrom=MSDN). ## Analysis Tasks for the AD_DSRMSettings Job @@ -18,7 +19,7 @@ Navigate to the **Active Directory > 5.Domains > AD_DSRMSettings > Configure** n **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -37,4 +38,4 @@ the following pre-configured report: | Report | Description | Default Tags | Report Elements | | ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| DSRM Admin Security | This report highlights domain controller registry settings for the DSRMAdminLogonBehavior key. If this key is set to 1 or 2, the DSRM Admin account can be used to log in to the domain controller even if it has not been started in DSRM. This is a potential vulnerability. See the Microsoft [Restartable AD DS Step-by-Step Guide](https://technet.microsoft.com/en-us/library/cc732714(v=ws.10).aspx) for additional information. | None | This report is comprised of two elements:
  • Pie Chart – Displays DSRM admin logon  by domain controller
  • Table – Provides details on domain controllers
| +| DSRM Admin Security | This report highlights domain controller registry settings for the DSRMAdminLogonBehavior key. If this key is set to 1 or 2, you can use the DSRM Admin account to log in to the domain controller even if it has not been started in DSRM. This is a potential vulnerability. See the Microsoft [Restartable AD DS Step-by-Step Guide](https://technet.microsoft.com/en-us/library/cc732714(v=ws.10).aspx) for additional information. | None | This report is comprised of two elements:
  • Pie Chart – Displays DSRM admin logon  by domain controller
  • Table – Provides details on domain controllers
| diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/domains/collection/ad_domaincontrollers.md b/docs/accessanalyzer/11.6/solutions/activedirectory/domains/collection/ad_domaincontrollers.md index b2f7266516..7e8115a42c 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/domains/collection/ad_domaincontrollers.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/domains/collection/ad_domaincontrollers.md @@ -7,7 +7,7 @@ sidebar_position: 10 # AD_DomainControllers Job The 0.Collection > AD_DomainControllers Job collects domain controller details which will be further -analyzed in order to provide information on domains, sites, and trusts. +analyzed to provide information on domains, sites, and trusts. ## Queries for the AD_DomainControllers Job @@ -15,7 +15,7 @@ The AD_DomainControllers Job uses the LDAP Data Collector and the ActiveDirector the following queries: :::warning -Except the first query, do not modify the remaining queries. The remaining queries are +Except the first query, don't modify the remaining queries. The remaining queries are preconfigured for this job. ::: @@ -50,7 +50,7 @@ The Domain Controller Listing Query in the AD_DomainControllers Job is configure Data Collector. This query can be optionally configured to connect securely with TLS/SSL. :::warning -Do not modify any other settings in this query. +Don't modify any other settings in this query. ::: @@ -72,6 +72,6 @@ opens. **Ignore Certificate Errors** to connect even if certificate errors occur. Use **Server Port** 686 for a secure connection. Click **OK** to close the Options page. -**Step 6 –** Step 13 – Then click **OK** to close the LDAP template form wizard. +**Step 6 –** Click **OK** to close the LDAP template form wizard. The job now connects securely with TLS/SSL. diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/domains/collection/ad_dsrm.md b/docs/accessanalyzer/11.6/solutions/activedirectory/domains/collection/ad_dsrm.md index 3c4316714f..cb3c8312d7 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/domains/collection/ad_dsrm.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/domains/collection/ad_dsrm.md @@ -7,17 +7,18 @@ sidebar_position: 20 # AD_DSRM Job The **0.Collection > AD_DSRM** Job collects data related to domain controller registry settings for -the DSRMAdminLogonBehavior key. If this key is set to 1 or 2, the DSRM Admin Account can be used to -log in to the domain controller even if it has not been started in DSRM which can present a -potential security vulnerability. Additional information on this registry key is available in this +the DSRMAdminLogonBehavior key. If this key is set to 1 or 2, the Directory Services Restore Mode +(DSRM) Admin Account can log in to the domain controller even if it has not been started in DSRM, +which can present a potential security vulnerability. Additional information on this registry key +is available in this [Microsoft Document](https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc732714(v=ws.10)?redirectedfrom=MSDN). ## Query for the AD_DSRM Job -The AD_TimeSync Job uses the Registry Data Collector for the following query: +The AD_DSRM Job uses the Registry Data Collector for the following query: :::warning -Do not modify this query. The query is preconfigured for this job. +Don't modify this query. The query is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/domains/collection/ad_timesync.md b/docs/accessanalyzer/11.6/solutions/activedirectory/domains/collection/ad_timesync.md index 5cf2a98f22..a5f90b0f80 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/domains/collection/ad_timesync.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/domains/collection/ad_timesync.md @@ -14,7 +14,7 @@ domain controller within the domain. The AD_TimeSync Job uses the Registry Data Collector for the following query: :::warning -Do not modify this query. The query is preconfigured for this job. +Don't modify this query. The query is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/domains/collection/overview.md b/docs/accessanalyzer/11.6/solutions/activedirectory/domains/collection/overview.md index 343313ee71..fc5ffabe66 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/domains/collection/overview.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/domains/collection/overview.md @@ -14,13 +14,13 @@ to provide details on domains, sites, and trusts. The 0.Collection Job Group is comprised of: - [AD_DomainControllers Job](/docs/accessanalyzer/11.6/solutions/activedirectory/domains/collection/ad_domaincontrollers.md) - – Collects domain controller details which will be further analyzed in order to provide + – Collects domain controller details which will be further analyzed to provide information on domains, sites, and trusts. - [AD_DSRM Job](/docs/accessanalyzer/11.6/solutions/activedirectory/domains/collection/ad_dsrm.md) – Collects data related to domain controller registry settings for the DSRMAdminLogonBehavior key. - If this key is set to 1 or 2, the DSRM Admin Account can be used to log in to the domain - controller even if it has not been started in DSRM which can present a potential security - vulnerability. Additional information on this registry key is available in this + If this key is set to 1 or 2, the Directory Services Restore Mode (DSRM) Admin Account can log in + to the domain controller even if it has not been started in DSRM, which can present a potential + security vulnerability. Additional information on this registry key is available in this [Microsoft Document](https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc732714(v=ws.10)?redirectedfrom=MSDN). - [AD_TimeSync Job](/docs/accessanalyzer/11.6/solutions/activedirectory/domains/collection/ad_timesync.md) – Collects TimeSync information from the registry for each domain controller within the domain diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/domains/overview.md b/docs/accessanalyzer/11.6/solutions/activedirectory/domains/overview.md index 9dfc4caf04..70dbeff862 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/domains/overview.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/domains/overview.md @@ -14,7 +14,7 @@ configurations that may leave your environment at risk. The following components comprises the 5.Domains Job Group: - [0.Collection Job Group](/docs/accessanalyzer/11.6/solutions/activedirectory/domains/collection/overview.md) - – Collects the data which will be further analyzed in order to provide details on domains, sites, + – Collects the data which will be further analyzed to provide details on domains, sites, and trusts. - [AD_DCSummary Job](/docs/accessanalyzer/11.6/solutions/activedirectory/domains/ad_dcsummary.md) – Provides operational reporting related to the details collected for each domain controller. For @@ -26,7 +26,8 @@ The following components comprises the 5.Domains Job Group: and types and directions of trusts - [AD_DSRMSettings Job](/docs/accessanalyzer/11.6/solutions/activedirectory/domains/ad_dsrmsettings.md) – Provides details on domain controller registry settings for the DSRMAdminLogonBehavior key. If - this key is set to 1 or 2, the DSRM Admin Account can be used to log in to the domain controller - even if it has not been started in DSRM which can present a potential security vulnerability. + this key is set to 1 or 2, the Directory Services Restore Mode (DSRM) Admin Account can log in to + the domain controller even if it has not been started in DSRM, which can present a potential + security vulnerability. Additional information on this registry key is available in this [Microsoft Document](https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc732714(v=ws.10)?redirectedfrom=MSDN). diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/domains/recommended.md b/docs/accessanalyzer/11.6/solutions/activedirectory/domains/recommended.md index c4d52f12aa..b21b98eff9 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/domains/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/domains/recommended.md @@ -11,7 +11,7 @@ default settings. It can be run directly or scheduled. **Dependencies** -This job group does not have dependencies. +This job group doesn't have dependencies. **Targeted Hosts** @@ -50,7 +50,7 @@ entire job group, instead of the individual jobs. **Query Configuration** The 5.Domains > 0.Collection > AD_DomainControllers job should be run with the default query -configurations. Most of these queries are preconfigured for this Job Group and should not be +configurations. Most of these queries are preconfigured for this Job Group and shouldn't be modified. The following query can be modified to use a secure connection with TLS/SSL: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/grouppolicy/ad_cpassword.md b/docs/accessanalyzer/11.6/solutions/activedirectory/grouppolicy/ad_cpassword.md index 87e7173e69..d953cc0aca 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/grouppolicy/ad_cpassword.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/grouppolicy/ad_cpassword.md @@ -8,20 +8,20 @@ sidebar_position: 20 The AD_CPassword Job identifies passwords that are stored in Group Policy Preferences which present a security risk allowing attackers access to these passwords. Microsoft published the AES private -key, which can be used to decrypt passwords stored in Group Policy Preferences. See the Microsoft +key, which attackers can use to decrypt passwords stored in Group Policy Preferences. See the Microsoft [2.2.1.1.4 Password Encryption](https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-gppref/2c15cbf0-f086-4c74-8b70-1f2fa45dd4be) article for additional information. Since Authenticated Users have read access to SYSVOL, any malicious insider or attacker can search for the cPassword file inside XML files shared through SYSVOL to decrypt them. GPOs can be stored in the `%ProgramData%\Microsoft\Group Policy\History` folder on each machine, meaning any results found by this job should be deleted off every computer -once this policy has been removed. +after this policy has been removed. ## Query for the AD_CPassword Job The AD_CPassword Job uses the PowerShell Data Collector for the following query: :::warning -Do not modify the query. The query is preconfigured for this job +Don't modify the query. The query is preconfigured for this job ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/grouppolicy/ad_grouppolicy.md b/docs/accessanalyzer/11.6/solutions/activedirectory/grouppolicy/ad_grouppolicy.md index bf968755ff..d06b6d59ca 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/grouppolicy/ad_grouppolicy.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/grouppolicy/ad_grouppolicy.md @@ -14,7 +14,7 @@ provides details on the containers they are linked to, and the settings that are The AD_GroupPolicy Job uses the GroupPolicy Data Collector for the following query: :::warning -Do not modify the queries. The queries are preconfigured for this job. +Don't modify the queries. The queries are preconfigured for this job. ::: @@ -35,7 +35,7 @@ Navigate to the **Active Directory** > **4.GroupPolicy** > **AD_GroupPolicy** > and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/grouppolicy/ad_overlappinggpos.md b/docs/accessanalyzer/11.6/solutions/activedirectory/grouppolicy/ad_overlappinggpos.md index a4231ed91a..e668c4bad2 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/grouppolicy/ad_overlappinggpos.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/grouppolicy/ad_overlappinggpos.md @@ -15,7 +15,7 @@ Navigate to the **Active Directory** > **4. Group Policy** > **AD_OverlappingGPO node and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected first analysis task. The first analysis task is +Don't modify or deselect the selected first analysis task. The first analysis task is preconfigured for this job. ::: @@ -30,7 +30,7 @@ The default analysis tasks are: The following analysis tasks are deselected by default: :::note -Deselect the **Conflicting** analysis task before selecting the analysis tasks below. +Deselect the **Conflicting** analysis task before selecting the following analysis tasks. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/grouppolicy/ad_passwordpolicies.md b/docs/accessanalyzer/11.6/solutions/activedirectory/grouppolicy/ad_passwordpolicies.md index 574ee6dcec..d9b0782813 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/grouppolicy/ad_passwordpolicies.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/grouppolicy/ad_passwordpolicies.md @@ -15,7 +15,7 @@ different password policies within a single domain. The AD_PasswordPolicies Job uses the LDAP Data Collector for the following query: :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -36,7 +36,7 @@ Navigate to the **Active Directory** > **4.GroupPolicy** > **AD_PasswordPolicies node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -48,7 +48,7 @@ The default analysis tasks are: - Determine fine-grained password policy details – Creates the SA_AD_PasswordPolicies_Details table accessible under the job’s Results node -In addition to the tables and views created by the analysis task, the AD_UserDelegation Job produces +In addition to the tables and views created by the analysis task, the AD_PasswordPolicies Job produces the following pre-configured report: | Report | Description | Default Tags | Report Elements | diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/grouppolicy/overview.md b/docs/accessanalyzer/11.6/solutions/activedirectory/grouppolicy/overview.md index 7a57f1ccfe..832a4c66b0 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/grouppolicy/overview.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/grouppolicy/overview.md @@ -23,7 +23,7 @@ The following components comprise the 4.Group Policy Job Group: malicious insider or attacker can search for the cPassword file inside XML files shared through SYSVOL to decrypt them. GPOs can be stored in the `%ProgramData%\Microsoft\Group Policy\History` folder on each machine, meaning any results found by this job should be deleted off every computer - once this policy has been removed. + after this policy has been removed. - [AD_GroupPolicy Job](/docs/accessanalyzer/11.6/solutions/activedirectory/grouppolicy/ad_grouppolicy.md) – Audits all Group Policies that are present on the Domain Controller, and provides details on the containers they are linked to and the settings that are configured diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/grouppolicy/recommended.md b/docs/accessanalyzer/11.6/solutions/activedirectory/grouppolicy/recommended.md index 4db5174f78..e1b535ee27 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/grouppolicy/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/grouppolicy/recommended.md @@ -11,7 +11,7 @@ settings. It can be run directly or scheduled. **Dependencies** -This job group does not have dependencies. +This job group doesn't have dependencies. **Targeted Hosts** diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_circularnesting.md b/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_circularnesting.md index aaceeef214..3627415c57 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_circularnesting.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_circularnesting.md @@ -15,7 +15,7 @@ Navigate to the **Active Directory** > **1.Groups** > **AD_CircularNesting** > * and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_dclogongroups.md b/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_dclogongroups.md index c5fce3cba2..e1a61a5a4f 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_dclogongroups.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_dclogongroups.md @@ -6,7 +6,7 @@ sidebar_position: 30 # AD_DCLogonGroups Job -The AD_DCLogonGroups Job identifies users who are able to log on to Domain Controllers through +The AD_DCLogonGroups Job identifies users who can log on to Domain Controllers through effective membership to the Enterprise Admins, Domain Admins, Administrators, Backup Operators, Account Operators, Print Operators, or Remote Desktop Users groups. This type of access should be limited to only those individuals who require this level of administrative privileges. @@ -17,7 +17,7 @@ Navigate to the **Active Directory** > **1.Groups** > **AD_DCLogonGroups** > **C select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_duplicategroups.md b/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_duplicategroups.md index be31dcd508..7bd8727f67 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_duplicategroups.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_duplicategroups.md @@ -15,7 +15,7 @@ Navigate to the **Active Directory** > **1.Groups** > **AD_DuplicateGroups** > * and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_emptygroups.md b/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_emptygroups.md index d8938ebc0d..411c56a839 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_emptygroups.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_emptygroups.md @@ -15,7 +15,7 @@ Navigate to the **Active Directory** > **1.Groups** > **AD_EmptyGroups** > **Con select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_groupprobableowners.md b/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_groupprobableowners.md index d51f220024..0438338636 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_groupprobableowners.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_groupprobableowners.md @@ -16,7 +16,7 @@ Navigate to the **Active Directory** > **1.Groups** > **AD_GroupProbableOwners** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_largestgroups.md b/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_largestgroups.md index fb5fce2a30..33db331cec 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_largestgroups.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_largestgroups.md @@ -6,9 +6,8 @@ sidebar_position: 70 # AD_LargestGroups Job -The AD_LargestGroups Job identifies groups with large effective member counts. These types of groups -may cause administrative overhead and burden in being able to easily understand who is getting -access to resources, or how much access is being granted to resources through these groups. +The AD_LargestGroups Job identifies groups with large effective member counts. These groups can +make it hard to determine who has access to resources or how much access these groups grant. ## Analysis Task for the AD_LargestGroups Job @@ -16,7 +15,7 @@ Navigate to the **Active Directory** > **1.Groups** > **AD_LargestGroups** > **C select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_mailsecuritygroups.md b/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_mailsecuritygroups.md index 8b219c0fdd..efde1b98d8 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_mailsecuritygroups.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_mailsecuritygroups.md @@ -14,7 +14,7 @@ Navigate to the **Active Directory** > **1.Groups** > **AD_MailSecurityGroups** and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_nestedgroups.md b/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_nestedgroups.md index df817e8379..735580dbe1 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_nestedgroups.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_nestedgroups.md @@ -7,8 +7,8 @@ sidebar_position: 90 # AD_NestedGroups Job The AD_NestedGroups Job identifies nested groups within Active Directory and provides details such -as the levels of nesting. While Active Directory provides the ability to nest certain types of -groups within other groups, Microsoft recommends nesting does not go beyond two levels in order to +as the levels of nesting. While Active Directory lets you nest certain types of +groups within other groups, Microsoft recommends nesting doesn't go beyond two levels to avoid difficulties in understanding effective membership and access. ## Analysis Tasks for the AD_NestedGroups Job @@ -17,7 +17,7 @@ Navigate to the **Active Directory** > **1.Groups** > **AD_NestedGroups** > **Co select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_sensitivesecuritygroups.md b/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_sensitivesecuritygroups.md index 5edd9f1ce5..620ed2382b 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_sensitivesecuritygroups.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_sensitivesecuritygroups.md @@ -17,7 +17,7 @@ Navigate to the **Active Directory** > **1.Groups** > **AD_SensitiveSecurityGrou node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_stalegroups.md b/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_stalegroups.md index 3816f6e6bb..67e3e39ee2 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_stalegroups.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_stalegroups.md @@ -16,7 +16,7 @@ Navigate to the **Active Directory** > **1.Groups** > **AD_StaleGroups** > **Con select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -37,4 +37,4 @@ the following pre-configured report: | Report | Description | Default Tags | Report Elements | | ------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Stale Effective Membership (A.K.A. Stale Groups) | This report identifies groups with stale effective membership. A stale user is defined as someone who has not logged into the domain in over 60 days, is expired, or currently disabled. | None | This report is comprised of three elements:
  • Bar Chart – Displays group membership
  • Table – Provides details on membership
  • Table – Provides details on group membership
| +| Stale Effective Membership (A.K.A. Stale Groups) | This report identifies groups with stale effective membership. A stale user is defined as someone who has not logged into the domain in over 60 days, is expired, or disabled. | None | This report is comprised of three elements:
  • Bar Chart – Displays group membership
  • Table – Provides details on membership
  • Table – Provides details on group membership
| diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/groups/overview.md b/docs/accessanalyzer/11.6/solutions/activedirectory/groups/overview.md index 2770f2655f..9577b397dd 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/groups/overview.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/groups/overview.md @@ -17,7 +17,7 @@ The following jobs comprise the 1.Groups Job Group: – Identifies circularly nested groups within Active Directory which can pose administrative and operational challenges with identifying effective access to resources - [AD_DCLogonGroups Job](/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_dclogongroups.md) - – Identifies users who are able to log on to Domain Controllers through effective membership to + – Identifies users who can log on to Domain Controllers through effective membership to the Enterprise Admins, Domain Admins, Administrators, Backup Operators, Account Operators, Print Operators, or Remote Desktop Users groups. This type of access should be limited to only those individuals who require this level of administrative privileges. @@ -28,7 +28,7 @@ The following jobs comprise the 1.Groups Job Group: – Identifies empty and single member groups which are suitable candidates for consolidation or cleanup - [AD_GroupProbableOwners Job](/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_groupprobableowners.md) - – Determines potential owners for Active Directory Groups which can be used to perform automated + – Determines potential owners for Active Directory Groups, which you can use to perform automated membership reviews and enable self-service group management and membership requests - [AD_LargestGroups Job](/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_largestgroups.md) – Identifies groups with large effective member counts. These types of groups may cause @@ -44,8 +44,8 @@ The following jobs comprise the 1.Groups Job Group: – Identifies mail-enabled security groups within Active Directory - [AD_NestedGroups Job](/docs/accessanalyzer/11.6/solutions/activedirectory/groups/ad_nestedgroups.md) – Identifies nested groups within Active Directory and provides details such as the levels of - nesting. While Active Directory provides the ability to nest certain types of groups within other - groups, Microsoft recommends nesting does not go beyond two levels in order to avoid difficulties + nesting. While Active Directory lets you nest certain types of groups within other + groups, Microsoft recommends nesting doesn't go beyond two levels to avoid difficulties in understanding effective membership and access. - The definition of a deeply nested group is set by the **.Active Directory Inventory** > diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/groups/recommended.md b/docs/accessanalyzer/11.6/solutions/activedirectory/groups/recommended.md index 63a9a82ec0..5fe1445160 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/groups/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/groups/recommended.md @@ -11,16 +11,16 @@ settings. It can be run directly or scheduled. **Dependencies** -The **.Active Directory Inventory** Job Group needs to be successfully executed prior to running +The **.Active Directory Inventory** Job Group needs to be successfully executed before running this job group. **Target Host** -This job group does not collect data. No target host is required. +This job group doesn't collect data. No target host is required. **Connection Profile** -This job group does not collect data. No specific Connection Profile is required. +This job group doesn't collect data. No specific Connection Profile is required. **Schedule Frequency** diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_directmembership.md b/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_directmembership.md index bca6f50668..24e6c94754 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_directmembership.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_directmembership.md @@ -6,7 +6,7 @@ sidebar_position: 20 # AD_DirectMembership Job -The AD_DirectMembership Job identifies users who do not have any group membership. This condition +The AD_DirectMembership Job identifies users who don't have any group membership. This condition may indicate unnecessary user accounts that are suitable candidates for review and cleanup. ## Analysis Tasks for the AD_DirectMembership Job @@ -15,7 +15,7 @@ Navigate to the **Active Directory** > **2.Users** > **AD_DirectMembership** > * and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_duplicateusers.md b/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_duplicateusers.md index 34069e96c9..205608974d 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_duplicateusers.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_duplicateusers.md @@ -6,9 +6,9 @@ sidebar_position: 30 # AD_DuplicateUsers Job -The AD_DuplicateUsers Job helps to identify multiple user accounts which may be owned by a single -employee. A user may have accounts in multiple domains or administrative accounts with greater -access than their normal account. +The AD_DuplicateUsers Job identifies multiple user accounts that a single employee may own. A user +may have accounts in multiple domains or administrative accounts with greater access than their +normal account. ## Analysis Tasks for the AD_DuplicateUsers Job @@ -16,7 +16,7 @@ Navigate to the **Active Directory** > **2.Users** > **AD_DuplicateUsers** > **C select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_orphanedusers.md b/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_orphanedusers.md index 9941572cf1..bc032fed2d 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_orphanedusers.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_orphanedusers.md @@ -15,7 +15,7 @@ Navigate to the **Active Directory** > **2.Users** > **AD_OrphanedUsers** > **Co select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_passwordstatus.md b/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_passwordstatus.md index 25507822b2..bb61792edc 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_passwordstatus.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_passwordstatus.md @@ -15,7 +15,7 @@ Navigate to the **Active Directory** > **2.Users** > **AD_PasswordStatus** > **C select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigure for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_serviceaccounts.md b/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_serviceaccounts.md index 276cf326e6..7e4ff8252a 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_serviceaccounts.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_serviceaccounts.md @@ -11,7 +11,7 @@ Kerberoasting. An account is deemed vulnerable to a Kerberoasting attack if the msDS-SupportedEncryptionTypes value supports RC4 as the highest encryption type. :::tip -Remember, the 1-AD_Scan Job needs to be configured to collect these Custom Attributes: +Configure the 1-AD_Scan Job to collect these custom attributes: ::: @@ -26,7 +26,7 @@ Navigate to the **Active Directory** > **2.Users** > **AD_ServiceAccounts** > ** select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_sidhistory.md b/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_sidhistory.md index 75dd4546ff..35bb9c97cd 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_sidhistory.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_sidhistory.md @@ -17,7 +17,7 @@ Navigate to the **Active Directory** > **2.Users** > **AD_SIDHistory** > **Confi select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -36,4 +36,4 @@ produces the following pre-configured report: | Report | Description | Default Tags | Report Elements | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| SID History | This report lists historical SIDs in the audited environment. Additionally, it highlights exceptions involving the SIDHistory attribute on AD user objects. Considered in particular are when a user has a historical SID from their current domain, or when a non-admin user has a historical SID with administrative rights. | None | This report is comprised of three elements:
  • Bar Chart – Displays historical SIDs by domain
  • Table – Provides details on SID history
  • Table – Provides details on historical SIDs by domain
| +| SID History | This report lists historical SIDs in the audited environment. Additionally, it highlights exceptions involving the SIDHistory attribute on AD user objects. It pays particular attention to cases where a user has a historical SID from their current domain, or where a non-admin user has a historical SID with administrative rights. | None | This report is comprised of three elements:
  • Bar Chart – Displays historical SIDs by domain
  • Table – Provides details on SID history
  • Table – Provides details on historical SIDs by domain
| diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_staleusers.md b/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_staleusers.md index cbc848c1a5..3053399388 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_staleusers.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_staleusers.md @@ -7,12 +7,12 @@ sidebar_position: 80 # AD_StaleUsers Job The AD_StaleUsers job identifies potentially stale users based on the amount of time since their -last login to the domain, or if the account has been disabled. These accounts should be reviewed and -cleaned up in order to increase security and reduce complexity. +last log in to the domain, or if the account has been disabled. These accounts should be reviewed and +cleaned up to increase security and reduce complexity. :::note The definition of a stale user is set by the .Active Directory Inventory solution. These -parameters, including the number of days since last login to be considered stale (by default 60 +parameters, including the number of days since last log in to be considered stale (by default 60 days), can be customized within the **.Active Directory Inventory** > **3-AD_Exceptions** job's **Stale Users** analysis task. See the [3-AD_Exceptions Job](/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/3-ad_exceptions.md) @@ -26,7 +26,7 @@ Navigate to the **Active Directory** > **2.Users** > **AD_StaleUsers** > **Confi select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -44,4 +44,4 @@ the following pre-configured report: | Report | Description | Default Tags | Report Elements | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Stale Users | This report identifies user accounts which have not logged into the domain for an extended amount of time or are currently disabled. A user account is considered stale if the last logon is over 60 days ago, is currently disabled, or expired. | None | This report is comprised of three elements:
  • Stacked Bar Chart – Displays users by domain
  • Table – Provides details on users
  • Table – Provides details on users by domain
| +| Stale Users | This report identifies user accounts which have not logged into the domain for an extended amount of time or are disabled. A user account is considered stale if the last logon is over 60 days ago, is disabled, or expired. | None | This report is comprised of three elements:
  • Stacked Bar Chart – Displays users by domain
  • Table – Provides details on users
  • Table – Provides details on users by domain
| diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_userattributecompletion.md b/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_userattributecompletion.md index d385030328..3650521e96 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_userattributecompletion.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_userattributecompletion.md @@ -16,7 +16,7 @@ Navigate to the **Active Directory** > **2.Users** > **AD_UserAttributeCompletio node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_userdelegation.md b/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_userdelegation.md index 587a51831b..ce9717ff1c 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_userdelegation.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_userdelegation.md @@ -8,7 +8,7 @@ sidebar_position: 100 The AD_Delegation Job highlights user accounts which are trusted for delegation. Kerberos delegation enables an application to access resources hosted on a different server, and opens up several -avenues to compromise based on the type of delegation enabled.  See the +avenues to compromise based on the type of delegation enabled. See the [What Is Kerberos Delegation?](https://blog.netwrix.com/2021/11/30/what-is-kerberos-delegation-an-overview-of-kerberos-delegation/) Netwrix blog article for more information about this configuration and the related security risks. @@ -18,7 +18,7 @@ Navigate to the **Active Directory** > **2.Users** > **AD_UserDelegation** > **C select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_usertoken.md b/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_usertoken.md index 50bc54ecd9..15d3b8a47b 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_usertoken.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_usertoken.md @@ -18,7 +18,7 @@ Navigate to the **Active Directory** > **2.Users** > **AD_UserToken** > **Config select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_weakpasswords.md b/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_weakpasswords.md index 82827a6f99..ef525d59c9 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_weakpasswords.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_weakpasswords.md @@ -19,20 +19,20 @@ dictionaries and other exceptions. Exceptions include: - Delegable Admins – Administrator account is allowed to be delegated to a service - DES Encryption Only – Account is using Kerberos DES encryption. DES encryption is considered weak as the 56-bit key is prone to brute force attacks. See the Microsoft - [AD DS: User accounts and trusts in this domain should not be configured for DES only](https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ff646918(v=ws.10)) + [AD DS: User accounts and trusts in this domain shouldn't be configured for DES only](https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ff646918(v=ws.10)) article for additional information. - Empty Password – Account has an empty password -- Kerberos Pre-authentication is not required – Account does not require Kerberos +- Kerberos Pre-authentication isn't required – Account doesn't require Kerberos pre-authentication. Kerberos pre-authentication can mitigate against brute force attacks. See the Microsoft - [Kerberos Pre-Authentication: Why It Should Not Be Disabled](https://learn.microsoft.com/en-us/archive/technet-wiki/23559.kerberos-pre-authentication-why-it-should-not-be-disabled) + [Kerberos Pre-Authentication: Why It Shouldn't Be Disabled](https://learn.microsoft.com/en-us/archive/technet-wiki/23559.kerberos-pre-authentication-why-it-should-not-be-disabled) article for additional information. - LM Hash – Account has stored LM hashes. The LM hash is a relatively weak hash that is prone to brute force attacks. See the Microsoft [How to prevent Windows from storing a LAN manager hash of your password in Active Directory and local SAM databases](https://learn.microsoft.com/en-US/troubleshoot/windows-server/windows-security/prevent-windows-store-lm-hash-password) article for additional information. - Password Never Expires – Account has a password that never expires -- Password Not Required – Account does not require a password +- Password Not Required – Account doesn't require a password - Weak Historical Password – Account has a historical password that was found in the dictionary - Weak Password – Account has a password that was found in the dictionary - Shares Common Password – Account shares a password with another account @@ -53,8 +53,7 @@ The query for this job are: ### Configure the Weak Passwords Query -The PasswordSecurity Data Collector can be scoped if desired. Follow the steps to modify the query -configuration. +The PasswordSecurity Data Collector can be scoped if desired. To modify the query configuration: **Step 1 –** Navigate to the job’s Configure node and select Queries. @@ -67,7 +66,7 @@ Collector Wizard opens. ![Password Security Data Collection Wizard Scan options page](/images/accessanalyzer/11.6/solutions/activedirectory/users/optionsweakpassword.webp) :::warning -Read the warning prior to enabling the cleartext password feature. +Read the warning before enabling the cleartext password feature. ::: @@ -95,7 +94,7 @@ Navigate to the **Active Directory** > **2.Users** > **AD_WeakPasswords** > **Co select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/users/overview.md b/docs/accessanalyzer/11.6/solutions/activedirectory/users/overview.md index 9fc3cf6f22..668732776d 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/users/overview.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/users/overview.md @@ -14,7 +14,7 @@ concern such as weak passwords, user token size, or stale users. The following components comprise the 2.Users Job Group: - [AD_DirectMembership Job](/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_directmembership.md) - – Identifies users who do not have any group membership. This condition may indicate unnecessary + – Identifies users who don't have any group membership. This condition may indicate unnecessary user accounts that are suitable candidates for review and cleanup. - [AD_DuplicateUsers Job](/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_duplicateusers.md) – Identifies multiple user accounts which may be owned by a single employee. A user may have @@ -36,7 +36,7 @@ The following components comprise the 2.Users Job Group: SID from their current domain, or when a non-admin user has a historical SID with administrative rights, both of which may be indicators of compromise. - [AD_StaleUsers Job](/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_staleusers.md) - – Identifies potentially stale users based on the amount of time since their last login to the + – Identifies potentially stale users based on the amount of time since their last log in to the domain, or if the account has been disabled. These accounts should be reviewed and cleaned up in order to increase security and reduce complexity. - [AD_UserAttributeCompletion Job](/docs/accessanalyzer/11.6/solutions/activedirectory/users/ad_userattributecompletion.md) diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/users/recommended.md b/docs/accessanalyzer/11.6/solutions/activedirectory/users/recommended.md index d45aae4a32..8389e016a9 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/users/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/users/recommended.md @@ -6,16 +6,16 @@ sidebar_position: 10 # Recommended Configurations for the 2.Users Job Group -The **Active Directory** > **2.Users** Job Group has been configured by default to run with the -out-of-the-box settings. It can be run directly or scheduled. +The **Active Directory** > **2.Users** Job Group is configured to run with the default settings. +It can be run directly or scheduled. **Dependencies** -- The **.Active Directory Inventory** Job Group needs to be successfully executed prior to running +- The **.Active Directory Inventory** Job Group needs to be successfully executed before running this job group - - For the **AD_ServiceAccounts** Job, the **.Active Directory Inventory** > **1-AD_Scan** Job - needs to be configured to collect **servicePrincipalName** as a Custom Attribute + - For the **AD_ServiceAccounts** Job, configure the **.Active Directory Inventory** > + **1-AD_Scan** Job to collect **servicePrincipalName** as a Custom Attribute - For the **AD_WeakPassword** Job: @@ -27,12 +27,12 @@ out-of-the-box settings. It can be run directly or scheduled. topic for additional information. :::info - If this job is not to be used, disable the job to prevent execution when the - job group is executed. + If you don't need this job, disable it to prevent it from running with the job + group. ::: -**Targeted Host(s)** +**Targeted Hosts** Only the **AD_WeakPasswords** Job requires a host list. The host list assignment has been configured under the **2. Users** > **AD_WeakPasswords** > **Configure** > **Hosts** node. It is set to target @@ -41,8 +41,8 @@ the host inventory value in the **isDomainController** field in the Host Master **Connection Profile** -Only the **AD_WeakPasswords** Job requires a Connection Profile. It must be set directly on the -**AD_WeakPasswords** Job (through the Job Properties window) with Domain Administrator privileges. +Only the **AD_WeakPasswords** Job requires a Connection Profile. Set it directly on the +**AD_WeakPasswords** Job (through the Job Properties window) using Domain Administrator privileges. :::note The **AD_WeakPassword** Job can be executed with a least privilege credential. See the @@ -64,7 +64,7 @@ Run the jobs in the **2.Users** Job Group together and in order by running the e instead of the individual jobs. :::tip -Remember, if the **AD_WeakPassword** Job is not to be executed, it can be disabled. +If you don't need to run the **AD_WeakPassword** Job, disable it. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/1-ad_scan.md b/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/1-ad_scan.md index 1fad4a84ef..8da8be1a55 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/1-ad_scan.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/1-ad_scan.md @@ -8,7 +8,7 @@ sidebar_position: 20 The 1-AD_Scan Job collects data from Active Directory. In most environments, this job requires no additional customizations before running it. Optionally, the job can be configured to scope scan -options and to collect custom attributes. For enable SSL encryption for communication with Active +options and to collect custom attributes. To enable SSL encryption for communication with Active Directory, see the [Enable SSL Option](#enable-ssloption) topic for additional information. ## Queries for the 1-AD Scan Job @@ -21,14 +21,14 @@ The 1-AD_Scan Job uses the ADInventory Data Collector for the following query: objects - This query can be modified. See the - [Customize the 1-AD_Scan Query](#customize-the-1-ad_scan-query) topic for additional + [Customize the 1-AD_Scan Query](#customize-the-1-adscan-query) topic for additional information. ### Customize the 1-AD_Scan Query The 1-AD_Scan Job has been preconfigured to run with the default settings with the category of Scan -Active Directory. Follow the steps to set any desired customizations to scan options or to collect -custom attributes. +Active Directory. To set any desired customizations to scan options or to collect +custom attributes: **Step 1 –** Navigate to the **.Active Directory Inventory** > **1-AD_Scan** > **Configure** node and select **Queries**. @@ -40,7 +40,7 @@ opens. DC Wizard opens. :::warning -Do not make changes to other wizard pages as they have been pre-configured for the +Don't make changes to other wizard pages as they have been pre-configured for the purpose of this job. ::: @@ -68,16 +68,16 @@ topic for additional information. click **Cancel** if no changes were made. Then click **OK** to close the Query Properties window. :::note -In order for the Access Information Center to populate NFS permissions within File System -reports, the .Active Directory Inventory Job Group must be configured to collect the **uid** and -**uidNumber** attributes for Users. See the +To let the Access Information Center populate NFS permissions within File System reports, +configure the .Active Directory Inventory Job Group to collect the **uid** and **uidNumber** +attributes for Users. See the [NFS Permissions for the AIC ](#nfs-permissions-for-the-aic) topic for additional information. ::: The 1-AD_Scan Job is now ready to run with the customized settings. If any custom attributes are added to the data collection, the **Create Extended Attributes View** analysis task can be enabled -in order to have visibility into the collected data. +to have visibility into the collected data. ## Analysis Tasks for the 1-AD_Scan Job @@ -85,7 +85,7 @@ View the analysis tasks by navigating to the **.Active Directory Inventory** > * **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -124,14 +124,14 @@ topic, the 1-AD_Scan Job produces the following pre-configured report: ## NFS Permissions for the AIC -In order for the Access Information Center to populate NFS resources within all File System -permissions and resource audit reports, the .Active Directory Inventory Job Group must be configured -to collect the following custom attributes for Users: +To let the Access Information Center populate NFS resources within all File System permissions and +resource audit reports, configure the .Active Directory Inventory Job Group to collect the following +custom attributes for Users: - uid - uidNumber -Follow the steps to add the custom attributes. +To add the custom attributes: **Step 1 –** Navigate to the Active Directory Inventory DC Wizard for the AD Inventory Query within the 1-AD_Scan Job. @@ -142,7 +142,7 @@ the 1-AD_Scan Job. option is deselected. :::note -Whenever query configurations are modified, it is necessary to do a full scan. After the +Whenever query configurations are modified, run a full scan. After the first full scan, differential scanning can be re-enabled. ::: @@ -176,7 +176,7 @@ The .Active Directory Inventory Job Group is now collecting attributes required visible within the Access Information Center. :::tip -Remember, it is necessary to re-enable differential scanning after Step 5 if desired. +Remember to re-enable differential scanning after Step 5 if desired. ::: @@ -186,7 +186,7 @@ for additional information. ## Enable SSL Option -Follow the steps to enable SSL encryption for communications with Active Directory: +To enable SSL encryption for communications with Active Directory: **Step 1 –** Navigate to the **1-AD_Scan > Configure** node and select **Queries**. diff --git a/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/2-ad_changes.md b/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/2-ad_changes.md index b92a1d099b..1972be10ca 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/2-ad_changes.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/2-ad_changes.md @@ -11,9 +11,9 @@ Directory changes which have occurred since the last time the .Active Directory was run. It is dependent on the running of the 1-AD_Scan Job, also located in the .Active Directory Inventory Job Group. -The 1-AD_Scan Job must have the Query Option to **Track changes into Change tracking tables** -selected in order for the Analysis Tasks in the 2-AD_Changes Job to work. See Step 4 of the -[Customize the 1-AD_Scan Query](/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/1-ad_scan.md#customize-the-1-ad_scan-query) +Select the Query Option to **Track changes into Change tracking tables** in the 1-AD_Scan Job so the +Analysis Tasks in the 2-AD_Changes Job work. See Step 4 of the +[Customize the 1-AD_Scan Query](/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/1-ad_scan.md#customize-the-1-adscan-query) topic for additional information. ## Analysis Tasks for the 2-AD_Changes Job @@ -22,7 +22,7 @@ View the analysis tasks by navigating to the **.Active Directory Inventory** > * **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -113,7 +113,7 @@ following analysis tasks are deselected by default: Notification must have recipients configured for the analysis task. Optionally, the email subject and body can be modified. See the -[Notification Analysis Tasks for the 2-AD_Changes Job](#notification-analysis-tasks-for-the-2-ad_changes-job) +[Notification Analysis Tasks for the 2-AD_Changes Job](#notification-analysis-tasks-for-the-2-adchanges-job) topic for additional information. In addition to the tables and views created by the analysis tasks, the 2-AD_Changes Job produces the @@ -125,32 +125,31 @@ following pre-configured reports: | Group Membership Changes (A.K.A. Most Active Groups) | This report tracks group membership changes in Active Directory. | None | This report is comprised of three elements:
  • Bar graph – Displays Most Active Groups (Past 24 Hours)
  • Table – Provides details on the most active groups (Past 24 Hours)
  • Table – Provides details on the most active groups
| | New Principals | This report identifies when principals have been created on the targeted domains. | None | This report is comprised of two elements:
  • Bar graph – Displays New Principals by Domain (Past 24 Hours)
  • Table – Provides details on the new principals by domain
| | Object Moves | This report tracks object moves in Active Directory. | None | This report is comprised of two elements:
  • Table – Displays Most Active OUs (Past 24 Hours)
  • Table – Provides details on the most active OUs
| -| Org Changes (A.K.A. Organizational Changes) | This report tracks organizational moves such as manager, title or department changes. | None | This report is comprised of three elements:
  • Bar graph – Displays Organizational Changes (Past 24 Hours)
  • Table – Provides details on organizational changes (Past 24 Hours)
  • Table – Provides details on the organizational changes
| +| Org Changes (A.K.A. Organizational Changes) | This report tracks organizational moves such as manager, title, or department changes. | None | This report is comprised of three elements:
  • Bar graph – Displays Organizational Changes (Past 24 Hours)
  • Table – Provides details on organizational changes (Past 24 Hours)
  • Table – Provides details on the organizational changes
| | Principal Deletions (A.K.A. Past 24 Hours) | This report identifies when principals have been deleted from the targeted domains. | None | This report is comprised of three elements:
  • Bar graph – Displays Deleted Principals by Domain (Past 24 Hours)
  • Table – Provides details on deleted principals by domain (Past 24 Hours)
  • Table – Provides details on the principals by domain
| | User Account Status Changes | This report tracks user account status changes. | None | This report is comprised of three elements:
  • Bar graph – Displays User Account Control Changes (Past 24 Hours)
  • Table – Provides details on user account control changes (Past 24 Hours)
  • Table – Provides details on the user account control changes
| ### Notification Analysis Tasks for the 2-AD_Changes Job -In order for Enterprise Auditor to send email notifications, it is necessary for the **Settings** > -**Notification** node to be properly configured. See the +To send email notifications, configure the **Settings** > **Notification** node properly. See the [Notification](/docs/accessanalyzer/11.6/admin/settings/notification.md) topic for instructions on enabling the Enterprise Auditor Console to send email notifications. Once email notifications have been enabled, the individual notification analysis tasks can be configured -and enabled. Follow the steps to configure a notification analysis task. +and enabled. To configure a notification analysis task: **Step 1 –** Navigate to the **.Active Directory Inventory** > **2-AD_Changes** > **Configure** node and select **Analysis**. ![Notification Analysis Tasks for the 2-AD_Changes Job](/images/accessanalyzer/11.6/solutions/activedirectoryinventory/changesanalysisnotification.webp) -**Step 2 –** In the Analysis Selection view, select the desired notification analysis task and click +**Step 2 –** In the Analysis Selection view, select the notification analysis task you want and click **Analysis Configuration**. The Notification Data Analysis Module opens. ![Notification Data Analysis Module SMTP properties page](/images/accessanalyzer/11.6/solutions/activedirectoryinventory/notificationanalysissmtp.webp) :::warning -Do not make changes to the pages preceding the SMTP page. +Don't make changes to the pages preceding the SMTP page. ::: @@ -169,9 +168,9 @@ provided. You can use the following options: ![Message section of SMTP properties page](/images/accessanalyzer/11.6/solutions/activedirectoryinventory/notificationanalysissmtpmessage.webp) -**Step 5 –** In the Message section, edit the **Subject**. It is not recommended to remove any -parameters. Then, customize the email content in the textbox to provide an explanation of the -notification to the recipients. +**Step 5 –** In the Message section, edit the **Subject**. Don't remove any parameters. Then, +customize the email content in the textbox to provide an explanation of the notification to the +recipients. **Step 6 –** Click **Next** to save these configuration changes and navigate to the Summary page. Do not make changes to any other pages. Click **Finish**. The Notification Data Analysis Module window diff --git a/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/3-ad_exceptions.md b/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/3-ad_exceptions.md index cb03286eae..c2c5307fbb 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/3-ad_exceptions.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/3-ad_exceptions.md @@ -12,7 +12,7 @@ running the 1-AD_Scan Job, also located in the .Active Directory Inventory Job G ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +The Configuration section on a Job's overview page lets you easily modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/11.6/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -28,17 +28,17 @@ The 3-AD_Exceptions Job has the following configurable parameters: - List of administrative groups See the -[Customize Analysis Parameters for the 3-AD_Exceptions Job](#customize-analysis-parameters-for-the-3-ad_exceptions-job) +[Customize Analysis Parameters for the 3-AD_Exceptions Job](#customize-analysis-parameters-for-the-3-adexceptions-job) topic for additional information. ## Analysis Tasks for the 3-AD_Exceptions Job View the analysis tasks by navigating to the **.Active Directory Inventory** > **3-AD_Exceptions** > -**Configure** node and select **Analysis**. Analysis tasks with configuration parameters that define -the security concerns within them can be modified. +**Configure** node and select **Analysis**. You can modify analysis tasks whose configuration +parameters define their security concerns. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/overview.md b/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/overview.md index 1276f491e6..f32050da62 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/overview.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/overview.md @@ -50,7 +50,7 @@ Inventory Job Group. The .Active Directory Inventory Solution is a core component of all Enterprise Auditor installations. Typically this solution is instantiated during installation, but it can be installed -from the Instant Job Wizard. Once it has been installed into the Jobs tree, navigate to the +from the Instant Job Wizard. After it has been installed into the Jobs tree, navigate to the solution: **Jobs** > **.Active Directory Inventory**. This group has been named in such a way to keep it at the top of the Jobs tree. diff --git a/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/recommended.md b/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/recommended.md index 4078b5bedc..a2fa1d4633 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/recommended.md @@ -6,13 +6,13 @@ sidebar_position: 10 # Recommended Configurations for the .Active Directory Inventory Solution -The .Active Directory Inventory Solution has been configured by default to run with the -out-of-the-box settings, but some settings are optional for configuration. It can be run directly or +The .Active Directory Inventory Solution is configured to run with the +default settings, but some settings are optional for configuration. It can be run directly or scheduled. **Dependencies** -This job group does not have dependencies. +This job group doesn't have dependencies. **Targeted Hosts** @@ -57,8 +57,8 @@ It is best to rerun it anytime AD changes might have occurred. **Run at the Solution Level** -The jobs in the .Active Directory Inventory Job Group should be run together and in order by running -the entire solution, instead of the individual jobs. +Run the jobs in the .Active Directory Inventory Job Group together and in order by running the +entire solution, instead of the individual jobs. **Query Configuration** @@ -92,6 +92,6 @@ when targeting multiple domains. **Step 2 –** Set a Connection Profile. -**Step 3 –** chedule the .Active Directory Inventory Job Group to run as desired. +**Step 3 –** Schedule the .Active Directory Inventory Job Group to run as desired. **Step 4 –** Review the reports generated by the .Active Directory Inventory Job Group. diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/ad_brokeninheritance.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/ad_brokeninheritance.md index c50ed8f3de..f3573ca9ac 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/ad_brokeninheritance.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/ad_brokeninheritance.md @@ -19,7 +19,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **6.BrokenInheritanc **AD_BrokenInheritance** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/ad_openaccess.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/ad_openaccess.md index 5e1be00912..6796b3dc4e 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/ad_openaccess.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/ad_openaccess.md @@ -20,7 +20,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **5.Open Access** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/ad_oupermissions.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/ad_oupermissions.md index 08df3b0389..9dc3c1c3b7 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/ad_oupermissions.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/ad_oupermissions.md @@ -19,7 +19,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **3.OUs** > **AD_OUP **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/ad_shadowaccess.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/ad_shadowaccess.md index 64d289ae2f..6ace5fe224 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/ad_shadowaccess.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/ad_shadowaccess.md @@ -33,7 +33,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **AD_ShadowAccess** and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks, with the exception of the +Don't modify or deselect the selected analysis tasks, with the exception of the **Calculate Shadow Access** analysis tasks. The analysis tasks are preconfigured for this job. The **Calculate Shadow Access** analysis task is the only analysis task that has customizable parameters. @@ -55,7 +55,7 @@ The default analysis tasks are: Results node - This Analysis Task has configurable parameters. See the - [Configure the Analysis Tasks for the AD_ShadowAccess Job](#configure-the-analysis-tasks-for-the-ad_shadowaccess-job) + [Configure the Analysis Tasks for the AD_ShadowAccess Job](#configure-the-analysis-tasks-for-the-adshadowaccess-job) topic for additional information. - Shadow Access Paths Cleanup – Removes calculated rows that are no longer used @@ -70,7 +70,7 @@ the following pre-configured reports. See the -[Report Functions for the AD_ShadowAccess Job](#report-functions-for-the-ad_shadowaccess-job) topic +[Report Functions for the AD_ShadowAccess Job](#report-functions-for-the-adshadowaccess-job) topic for additional information. ### Customizable Analysis Tasks for the AD_ShadowAccess Job @@ -88,15 +88,15 @@ The default values for customizable parameters are: | @disabled | 0 | Set to 0 to ignore disabled users | | See the -[Configure the Analysis Tasks for the AD_ShadowAccess Job](#configure-the-analysis-tasks-for-the-ad_shadowaccess-job) +[Configure the Analysis Tasks for the AD_ShadowAccess Job](#configure-the-analysis-tasks-for-the-adshadowaccess-job) topic for additional information. ### Configure the Analysis Tasks for the AD_ShadowAccess Job Customizable parameters enable Enterprise Auditor users to set the values used to classify user and group objects during this job’s analysis. The parameters can be customized and are listed in a -section at the bottom of the SQL Script Editor. Follow the steps to customize an analysis task’s -parameters. +section at the bottom of the SQL Script Editor. To customize an analysis task’s +parameters: **Step 1 –** Navigate to the **Active Directory Permissions Analyzer** > **AD_ShadowAccess** > **Configure** node and select **Analysis** to view analysis tasks. @@ -109,12 +109,12 @@ then click **Analysis Configuration**. The SQL Script Editor opens. ![SQL Script Editor](/images/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/shadowaccesssqlscripteditor.webp) **Step 3 –** In the parameters section at the bottom of the editor, find the Value column. -Double-click on the current value and change as desired. +Double-click the current value and change as desired. - If the variable type is a table, select the cell and click **Edit Table** to modify the value. :::warning -Do not change any parameters where the Value states `Created during execution`. +Don't change any parameters where the Value states `Created during execution`. ::: @@ -154,9 +154,9 @@ domain and sensitive data. ![Report element displaying information on potential attack paths for users found in the targeted domain](/images/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/shadowaccessreport2.webp) The last report element displays information on potential attack paths for users found in the -targeted domain. Clicking on the green plus sign next to an attack path will open an Attack Path -window that displays a step-by-step process of how a user object, if compromised, can be used to -conduct a shadow attack. +targeted domain. Click the green plus sign next to an attack path to open an Attack Path window that +displays a step-by-step process of how an attacker can use a compromised user object to conduct a +shadow attack. ![Attack Path window example](/images/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/shadowaccessreport3.webp) diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/collection/ad_computerrights.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/collection/ad_computerrights.md index 196ea8441d..3dcb8656e7 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/collection/ad_computerrights.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/collection/ad_computerrights.md @@ -14,7 +14,7 @@ Active Directory. The AD_ComputerRights Job uses the ADPermissions Data Collector for the following query: :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -32,7 +32,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **0.Collection** > **AD_ComputerRights** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/collection/ad_containerrights.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/collection/ad_containerrights.md index 617e21d516..725578fe32 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/collection/ad_containerrights.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/collection/ad_containerrights.md @@ -14,7 +14,7 @@ Active Directory. The AD_ContainerRights Job uses the ADPermissions Data Collector for the following query: :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -32,7 +32,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **0.Collection** > **AD_ContainerRights** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/collection/ad_domainrights.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/collection/ad_domainrights.md index d9e103d04c..e4a865273a 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/collection/ad_domainrights.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/collection/ad_domainrights.md @@ -14,7 +14,7 @@ Active Directory. The AD_DomainRights Job uses the ADPermissions Data Collector for the following query: :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -32,7 +32,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **0.Collection** > * **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/collection/ad_grouprights.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/collection/ad_grouprights.md index 8adb3aeb02..268cd8bb03 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/collection/ad_grouprights.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/collection/ad_grouprights.md @@ -14,7 +14,7 @@ Directory. The AD_GroupRights Job uses the ADPermissions Data Collector for the following query: :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -32,7 +32,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **0.Collection** > * **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/collection/ad_ourights.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/collection/ad_ourights.md index 0d3a884ecb..16514300da 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/collection/ad_ourights.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/collection/ad_ourights.md @@ -14,7 +14,7 @@ in Active Directory. The AD_OURights Job uses the ADPermissions Data Collector for the following query: :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -32,7 +32,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **0.Collection** > * **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/collection/ad_siterights.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/collection/ad_siterights.md index 5b52b0a0ba..2fe5159113 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/collection/ad_siterights.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/collection/ad_siterights.md @@ -14,7 +14,7 @@ Directory. The AD_SiteRights Job uses the ADPermissions Data Collector for the following query: :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -32,7 +32,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **0.Collection** > * **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/collection/ad_userrights.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/collection/ad_userrights.md index 9f6684cdae..9ab47c4a3c 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/collection/ad_userrights.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/collection/ad_userrights.md @@ -14,7 +14,7 @@ Directory. The AD_UserRights Job uses the ADPermissions Data Collector for the following query: :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -32,7 +32,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **0.Collection** > * **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/computers/ad_computerpermissions.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/computers/ad_computerpermissions.md index ad8dd9826a..eaabf66ca0 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/computers/ad_computerpermissions.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/computers/ad_computerpermissions.md @@ -15,7 +15,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **4.Computers** > **AD_ComputerPermissions** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/computers/ad_lapspermissions.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/computers/ad_lapspermissions.md index 776c5d7037..126fc8aa7c 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/computers/ad_lapspermissions.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/computers/ad_lapspermissions.md @@ -15,7 +15,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **4.Computers** > **AD_LAPSPermissions** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/containers/ad_adminsdholder.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/containers/ad_adminsdholder.md index fa4a2ee7f2..420a7fb92a 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/containers/ad_adminsdholder.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/containers/ad_adminsdholder.md @@ -15,7 +15,7 @@ Container in Active Directory. The AD_AdminSDHolder Job uses the PowerShell Data Collector for the following query: :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -33,7 +33,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **7.Containers** > **AD_AdminSDHolder** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/containers/ad_containerpermissions.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/containers/ad_containerpermissions.md index 814b60bb81..d8f729ea39 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/containers/ad_containerpermissions.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/containers/ad_containerpermissions.md @@ -6,7 +6,7 @@ sidebar_position: 20 # AD_ContainerPermissions Job -The AD_ContainerPermissions Job is responsible for reporting on all Active Directory permissions +The AD_ContainerPermissions Job reports on all Active Directory permissions applied to container objects within the targeted domains. ## Analysis Tasks for the AD_ContainerPermissions Job @@ -15,7 +15,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **7.Containers** > **AD_ContainerPermissions** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/containers/overview.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/containers/overview.md index c751c853a8..34e52faf9a 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/containers/overview.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/containers/overview.md @@ -15,7 +15,7 @@ The jobs in the 7.Containers Job Group are: - [AD_AdminSDHolder Job](/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/containers/ad_adminsdholder.md) – Reports on all non-default Active Directory permissions applied to the AdminSDHolder container - within the targeted domains. The AdminSDHolder container can be leveraged by an attacker to create + within the targeted domains. An attacker can use the AdminSDHolder container to create persistence within the environment. See the Microsoft [AdminSDHolder, Protected Groups and SDPROP](https://technet.microsoft.com/en-us/library/2009.09.sdadminholder.aspx) article for additional information. diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/domains/ad_domainpermissions.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/domains/ad_domainpermissions.md index 8672ae1ec9..7053a6a59a 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/domains/ad_domainpermissions.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/domains/ad_domainpermissions.md @@ -15,7 +15,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **8.Domains** > **AD_DomainPermissions** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/domains/ad_domainreplication.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/domains/ad_domainreplication.md index 25753e3d5c..9abb71a50c 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/domains/ad_domainreplication.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/domains/ad_domainreplication.md @@ -15,7 +15,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **8.Domains** > **AD_DomainReplication** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/groups/ad_groupmembershippermissions.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/groups/ad_groupmembershippermissions.md index 7e9ec9ad88..799ac62e02 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/groups/ad_groupmembershippermissions.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/groups/ad_groupmembershippermissions.md @@ -6,8 +6,8 @@ sidebar_position: 10 # AD_GroupMembershipPermissions Job -The AD_GroupMembershipPermissions Job highlights all Active Directory users that are capable of -modifying group membership within the targeted domains. +The AD_GroupMembershipPermissions Job highlights all Active Directory users that can modify group +membership within the targeted domains. ## Analysis Tasks for the AD_GroupMembershipPermissions Job @@ -16,7 +16,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **2.Groups** > tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/groups/ad_grouppermissions.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/groups/ad_grouppermissions.md index ec46d0fa16..e853130048 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/groups/ad_grouppermissions.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/groups/ad_grouppermissions.md @@ -15,7 +15,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **2.Groups** > **AD_ **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/groups/overview.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/groups/overview.md index d52b451ee3..3bfbbf9352 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/groups/overview.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/groups/overview.md @@ -14,7 +14,7 @@ the targeted domains. The jobs in the 2.Groups Job Group are: - [AD_GroupMembershipPermissions Job](/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/groups/ad_groupmembershippermissions.md) - – Highlights all Active Directory users that are capable of modifying group membership within the + – Highlights all Active Directory users that can modify group membership within the targeted domains - [AD_GroupPermissions Job](/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/groups/ad_grouppermissions.md) – Reports on all Active Directory permissions applied to group objects within the targeted domains diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/overview.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/overview.md index 0d51dd6de1..76499465cf 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/overview.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/overview.md @@ -7,8 +7,8 @@ sidebar_position: 50 # Active Directory Permissions Analyzer Solution The Enterprise Auditor Active Directory Permissions Analyzer Solution enables organizations to -easily and automatically determine effective permissions applied to any and all Active Directory -(AD) objects. AD, Security, and Network Administrators can easily browse and compare information +automatically determine effective permissions applied to all Active Directory +(AD) objects. AD, Security, and Network Administrators can browse and compare information from individual or multiple domains using comprehensive, preconfigured analyses and reports focused on permissions associated with AD domains, organizational units, groups, users, and computers. These capabilities enable them to obtain the most authoritative view of who has access to what in AD. diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/recommended.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/recommended.md index 4bbecb3511..2d1890f089 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/recommended.md @@ -12,7 +12,7 @@ The following Enterprise Auditor job groups need to be successfully run: - .Active Directory Inventory Job Group -The following jobs need to be run prior to running the +The following jobs need to be run before running the [AD_ShadowAccess Job](/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/ad_shadowaccess.md): - .Active Directory Inventory >1-AD_Scan > ADInventory diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/sites/ad_dcshadowpermissions.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/sites/ad_dcshadowpermissions.md index 97aa4c2c52..baee6076eb 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/sites/ad_dcshadowpermissions.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/sites/ad_dcshadowpermissions.md @@ -6,8 +6,8 @@ sidebar_position: 10 # AD_DCShadowPermissions Job -The AD_DCShadowPermissions Job highlights all Active Directory users that are capable of potentially -performing a DCShadow attack within the targeted domains. +The AD_DCShadowPermissions Job highlights all Active Directory users that can perform a DCShadow +attack within the targeted domains. ## Analysis Tasks for the AD_DCShadowPermissions Job @@ -15,7 +15,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **9.Sites** > **AD_DCShadowPermissions** > **Configure** node and select **Analysis** to view analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/sites/ad_sitepermissions.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/sites/ad_sitepermissions.md index 70bda7b571..77c3224bb3 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/sites/ad_sitepermissions.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/sites/ad_sitepermissions.md @@ -15,7 +15,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **9.Sites** > **AD_S **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/sites/overview.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/sites/overview.md index c7613b3c83..19d81a71c3 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/sites/overview.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/sites/overview.md @@ -14,7 +14,7 @@ targeted domains. The jobs in the 9.Sites Job Group are: - [AD_DCShadowPermissions Job](/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/sites/ad_dcshadowpermissions.md) - – Highlights all Active Directory users that are capable of potentially performing a DCShadow + – Highlights all Active Directory users that can perform a DCShadow attack within the targeted domains - [AD_SitePermissions Job](/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/sites/ad_sitepermissions.md) – Reports on all Active Directory permissions applied to site objects within the targeted domains diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/users/ad_resetpasswordpermissions.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/users/ad_resetpasswordpermissions.md index 8fc8f721bf..925e29a79f 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/users/ad_resetpasswordpermissions.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/users/ad_resetpasswordpermissions.md @@ -6,8 +6,8 @@ sidebar_position: 10 # AD_ResetPasswordPermissions Job -The AD_ResetPasswordPermissions Job highlights all Active Directory users that are capable of -resetting another user's password within the targeted domains. It uses the data collected by the +The AD_ResetPasswordPermissions Job highlights all Active Directory users that can reset another +user's password within the targeted domains. It uses the data collected by the 0.Collection Job Group to provide information on permissions applied to user objects in Active Directory. @@ -18,7 +18,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **1.Users** > tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/users/ad_userpermissions.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/users/ad_userpermissions.md index cafe946361..921fb71fbe 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/users/ad_userpermissions.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/users/ad_userpermissions.md @@ -16,7 +16,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **1.Users** > **AD_U **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/users/overview.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/users/overview.md index 852e647802..03dcb277c8 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/users/overview.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/users/overview.md @@ -14,7 +14,7 @@ targeted domains The following jobs comprise the 1.Users Job Group: - [AD_ResetPasswordPermissions Job](/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/users/ad_resetpasswordpermissions.md) - – Highlights all Active Directory users that are capable of resetting another user’s password + – Highlights all Active Directory users that can reset another user’s password within the targeted domains - [AD_UserPermissions Job](/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/users/ad_userpermissions.md) – Reports on all Active Directory permissions applied to user objects within the targeted domains diff --git a/docs/accessanalyzer/11.6/solutions/anyid/anyid_csv.md b/docs/accessanalyzer/11.6/solutions/anyid/anyid_csv.md index 840b6dfb09..6cdf2cce94 100644 --- a/docs/accessanalyzer/11.6/solutions/anyid/anyid_csv.md +++ b/docs/accessanalyzer/11.6/solutions/anyid/anyid_csv.md @@ -33,7 +33,7 @@ Local Host **Connection Profile** -The AnyID_CSV job does not require a connection profile. +The AnyID_CSV job doesn't require a connection profile. **History Retention** @@ -52,11 +52,11 @@ Schedule the job as required. **Query Configuration** This job contains configurable queries. See the -[Configure the AnyID_CSV Query](#configure-the-anyid_csvquery) topic for additional information. +[Configure the AnyID_CSV Query](#configure-the-anyidcsvquery) topic for additional information. **Analysis Configuration** -See the [Analysis Tasks for the AnyID_CSV Job](#analysis-tasks-for-the-anyid_csvjob) topic for +See the [Analysis Tasks for the AnyID_CSV Job](#analysis-tasks-for-the-anyidcsvjob) topic for additional information. **Workflow** @@ -78,11 +78,11 @@ The AnyID_CSV query uses the PowerShell Data Collector. The query is: - CSV Import – Imports identities and attributes from a CSV file. See the - [Configure the AnyID_CSV Query](#configure-the-anyid_csvquery) topic for additional information. + [Configure the AnyID_CSV Query](#configure-the-anyidcsvquery) topic for additional information. ### Configure the AnyID_CSV Query -Follow the steps to configure the AnyID_CSV query. +To configure the AnyID_CSV query: ![ The name of the source repository parameter on the job Overview page](/images/accessanalyzer/11.6/solutions/anyid/csvoverviewpage.webp) @@ -111,7 +111,7 @@ The following attributes must be configured in order for the job to execute prop - $inputfile – File path to the CSV file which contains the identity and attribute information -- $RequiredAttributes – The list of attributes that need to be found in the document in order to +- $RequiredAttributes – The list of attributes that need to be found in the document to trigger a match - An attribute in the Attributes list will not be considered a match (in reporting and AIC) @@ -141,7 +141,7 @@ Navigate to the **Jobs** > **AnyID Connectors** > **AnyID_CSV** > **Configure** **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/anyid/anyid_epicclarity.md b/docs/accessanalyzer/11.6/solutions/anyid/anyid_epicclarity.md index 6607ab58e6..08b9915b75 100644 --- a/docs/accessanalyzer/11.6/solutions/anyid/anyid_epicclarity.md +++ b/docs/accessanalyzer/11.6/solutions/anyid/anyid_epicclarity.md @@ -8,7 +8,7 @@ sidebar_position: 20 The AnyID_EpicClarity job collects patient information from Epic including MRNs, SSNs, Subscriber IDs, and Account IDs. An account with read access to the underlying Clarity Oracle database is -required in order to run queries. +required to run queries. ![AnyID_EpicClarity Job in the Jobs Tree](/images/accessanalyzer/11.6/solutions/anyid/epicclarityjoblocation.webp) @@ -22,7 +22,7 @@ The following are recommended configurations for the AnyID_EpicClarity job: The AnyID_EpicClarity job requires a CSV file with a filepath configured in the job's query to collect data. See the -[Configure the AnyID_EpicClarity Queries](#configure-the-anyid_epicclarity-queries) topic for +[Configure the AnyID_EpicClarity Queries](#configure-the-anyidepicclarity-queries) topic for additional information. **Targeted Host** @@ -45,12 +45,12 @@ Not supported **Schedule Frequency** -This job should be run based on the desired frequency of Sensitive Data Scans. +This job should be run based on the frequency you want for Sensitive Data Scans. **Query Configuration** This job contains configurable queries. See the Configure the -[Configure the AnyID_EpicClarity Queries](#configure-the-anyid_epicclarity-queries) topic for +[Configure the AnyID_EpicClarity Queries](#configure-the-anyidepicclarity-queries) topic for additional information. **Analysis Configuration** @@ -79,12 +79,12 @@ The queries are: - Epic Clarity Identity IDs – Imports Epic Clarity subject profile information on identity IDs The above queries have configurable parameters. See the -[Configure the AnyID_EpicClarity Queries](#configure-the-anyid_epicclarity-queries) topic for +[Configure the AnyID_EpicClarity Queries](#configure-the-anyidepicclarity-queries) topic for additional information. ### Configure the AnyID_EpicClarity Queries -Follow the steps to configure the AnyID_EpicClarity queries. +To configure the AnyID_EpicClarity queries: **Step 1 –** Navigate to the **AnyID Connectors** > **AnyID_EpicClarity** > **Configure** node and select **Queries**. @@ -111,7 +111,7 @@ topic for additional information. Configure the following attributes as needed: - An attribute in the Attributes list will not be considered a match (in reporting and AIC) unless an attribute in the RequiredAttributes list is also found in the same file -- $RequiredAttributes – The list of attributes that need to be found in the document in order to +- $RequiredAttributes – The list of attributes that need to be found in the document to trigger a match. The default values are SSN, MRN, and IdentityID. - An attribute in the Attributes list will not be considered a match (in reporting and AIC) @@ -131,7 +131,7 @@ Navigate to the **Jobs** > **AnyID Connectors** > **AnyID_EpicClarity** > **Con select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/anyid/anyid_paycom.md b/docs/accessanalyzer/11.6/solutions/anyid/anyid_paycom.md index ff83b472e2..7aea46735b 100644 --- a/docs/accessanalyzer/11.6/solutions/anyid/anyid_paycom.md +++ b/docs/accessanalyzer/11.6/solutions/anyid/anyid_paycom.md @@ -7,7 +7,7 @@ sidebar_position: 30 # AnyID_Paycom Job The AnyID_Paycom job pulls employee information from Paycom including name, address, date of Birth, -and SSN. Contact the organization's Paycom administrator in order to generate the CSV export +and SSN. Contact the organization's Paycom administrator to generate the CSV export required for this job. The recommended approach is to copy the CSV file to the Enterprise Auditor Console for best import performance. @@ -29,7 +29,7 @@ Local Host **Connection Profile** -The AnyID_Paycom job does not require a connection profile. +The AnyID_Paycom job doesn't require a connection profile. **History Retention** @@ -43,12 +43,12 @@ Not supported **Schedule Frequency** -This job should be run based on the desired frequency of Sensitive Data Scans. +This job should be run based on the frequency you want for Sensitive Data Scans. **Query Configuration** This job contains configurable queries. See the -[Configure the AnyID_Paycom Job](#configure-the-anyid_paycom-job) topic for additional information. +[Configure the AnyID_Paycom Job](#configure-the-anyidpaycom-job) topic for additional information. **Analysis Configuration** @@ -73,12 +73,12 @@ The AnyID_Paycom job uses the PowerShell Data Collector for the query. The queries are: - Paycom CSV Import – Imports a CSV file with information from Paycom. This query has configurable - parameters. See the [Configure the AnyID_Paycom Job](#configure-the-anyid_paycom-job) topic for + parameters. See the [Configure the AnyID_Paycom Job](#configure-the-anyidpaycom-job) topic for additional information. ### Configure the AnyID_Paycom Job -Follow the steps to configure the AnyID_Paycom query. +To configure the AnyID_Paycom query: **Step 1 –** Navigate to the **AnyID Connectors** > **AnyID_Paycom** > **Configure** node and select **Queries**. @@ -96,16 +96,16 @@ the page to expand the Parameters window. See the [PowerShell: Edit Query](/docs/accessanalyzer/11.6/admin/datacollector/powershell/editquery.md) topic for additional information. Configure the following attributes as needed: -- $SAHOSTNAME – Created during execution. This parameter cannot be modified. -- $JobCredential – Created during execution. This parameter cannot be modified. -- $JobCredentials – Created during execution. This parameter cannot be modified. +- $SAHOSTNAME – Created during execution. This parameter can't be modified. +- $JobCredential – Created during execution. This parameter can't be modified. +- $JobCredentials – Created during execution. This parameter can't be modified. - $inputfile – File path to the CSV file which contains the identity and attribute information - $Attributes – The list of attributes that will be scanned for during sensitive data scanning - An attribute in the Attributes list will not be considered a match (in reporting and AIC) unless an attribute in the RequiredAttributes list is also found in the same file -- $RequiredAttributes – The list of attributes that need to be found in the document in order to +- $RequiredAttributes – The list of attributes that need to be found in the document to trigger a match - An attribute in the Attributes list will not be considered a match (in reporting and AIC) @@ -130,7 +130,7 @@ Navigate to the **Jobs** > **AnyID Connectors** > **AnyID_Paycom** > **Configur **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/anyid/anyid_salesforce.md b/docs/accessanalyzer/11.6/solutions/anyid/anyid_salesforce.md index b6e55e8e32..17dd0cdc8b 100644 --- a/docs/accessanalyzer/11.6/solutions/anyid/anyid_salesforce.md +++ b/docs/accessanalyzer/11.6/solutions/anyid/anyid_salesforce.md @@ -7,7 +7,7 @@ sidebar_position: 40 # AnyID_Salesforce Job The AnyID_Salesforce job collects Salesforce contact details including phone, address, email, and -date of birth. This job requires API access to Salesforce in order to collect this information. The +date of birth. This job requires API access to Salesforce to collect this information. The list of collected attributes can be adjusted as necessary. ![AnyID_Salesforce Job in the Jobs Tree](/images/accessanalyzer/11.6/solutions/anyid/salesforcejoblocation.webp) @@ -57,7 +57,7 @@ Schedule the job as required. **Query Configuration** This job contains configurable queries. See the -[Configure the AnyID_Salesforce Query](#configure-the-anyid_salesforce-query) topic for additional +[Configure the AnyID_Salesforce Query](#configure-the-anyidsalesforce-query) topic for additional information. **Analysis Configuration** @@ -83,12 +83,12 @@ The AnyID_Salesforce job uses the PowerShell Data Collector for the query. The query is: - PS Salesforce Import – Imports Salesforce information for analysis. This query has configurable - parameters. See the [Configure the AnyID_Salesforce Query](#configure-the-anyid_salesforce-query) + parameters. See the [Configure the AnyID_Salesforce Query](#configure-the-anyidsalesforce-query) topic for additional information. ### Configure the AnyID_Salesforce Query -Follow the steps to configure the AnyID_Salesforce query. +To configure the AnyID_Salesforce query: **Step 1 –** Navigate to the **AnyID Connectors** > **AnyID_Salesforce** > **Configure** node and select **Queries**. @@ -106,15 +106,15 @@ the page to expand the Parameters window. See the [PowerShell: Edit Query](/docs/accessanalyzer/11.6/admin/datacollector/powershell/editquery.md) topic for additional information. Configure the following attributes as needed: -- $SAHOSTNAME – Created during execution. This parameter cannot be modified. -- $JobCredential – Created during execution. This parameter cannot be modified. -- $JobCredentials – Created during execution. This parameter cannot be modified. +- $SAHOSTNAME – Created during execution. This parameter can't be modified. +- $JobCredential – Created during execution. This parameter can't be modified. +- $JobCredentials – Created during execution. This parameter can't be modified. - $Attributes – The list of attributes that will be scanned for during sensitive data scanning - An attribute in the Attributes list will not be considered a match (in reporting and AIC) unless an attribute in the RequiredAttributes list is also found in the same file -- $RequiredAttributes – The list of attributes that need to be found in the document in order to +- $RequiredAttributes – The list of attributes that need to be found in the document to trigger a match - An attribute in the Attributes list will not be considered a match (in reporting and AIC) @@ -136,7 +136,7 @@ Navigate to the **Jobs** > **AnyID Connectors** > **AnyID_Salesforce** > **Conf select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/anyid/overview.md b/docs/accessanalyzer/11.6/solutions/anyid/overview.md index 2b31c0337f..293ea877f9 100644 --- a/docs/accessanalyzer/11.6/solutions/anyid/overview.md +++ b/docs/accessanalyzer/11.6/solutions/anyid/overview.md @@ -6,23 +6,23 @@ sidebar_position: 60 # AnyID Connectors Solution -The AnyID Connectors Solution allows you to quickly find where data for identities are stored, +The AnyID Connectors Solution lets you quickly find where data for identities are stored, reducing the response time to Data Subject Access Requests (DSARs). Integration with third party -repositories allows you to perform exact data matching for profiles such as employees, customers, +repositories lets you perform exact data matching for profiles such as employees, customers, students, or patients across any data repository. Data Privacy Engine works in conjunction with Enterprise Auditor Sensitive Data Discovery scans to create an efficient, secure IdentityIndex™ that privacy, security, and legal professionals can -leverage to quickly and easily map the location of subject information. Through a series of -preconfigured Identity Connectors,you can easily extract identity-related attributes about customers +use to map the location of subject information. Through a series of +preconfigured Identity Connectors, you can extract identity-related attributes about customers and other potential subjects from verified systems of record like Salesforce, Epic, Peoplesoft, and Paycom, as well as homegrown or alternative platforms. Through the creation of a Subject Profile for each individual, Enterprise Auditor’s broad-reaching Sensitive Data Discovery engine accurately identifies the specific location of a subject’s data -across virtually any cloud or on-premises data repository. With this context in tow, organizations -can now easily perform Data Subject Access Requests (DSARs), zero-in on where the implementation of -Privacy by Design principles are needed most urgently, and know for certain when breach attempts and +across virtually any cloud or on-premises data repository. With this context, organizations +can perform Data Subject Access Requests (DSARs), prioritize where Privacy by Design +principles are needed most, and confirm when breach attempts and activities involve consumer, patient, resident, and other subject data. ## Supported Platforms @@ -50,10 +50,10 @@ integrate with third-party systems of record such as Paycom or Salesforce, to ex potential data subjects along with relevant bits of PII such as Social Security Number, Address, or Phone Number. -The jobs within this group create and add to the secure IdentityIndex™ containing identity-related -attributes about potential subjects which are then used by Enterprise Auditor’s Sensitive Data -Discovery engine to perform exact data matching against virtually any cloud or on-premises data -repository. +The jobs within this group create and add to the secure IdentityIndex™, which contains +identity-related attributes about potential subjects. Enterprise Auditor’s Sensitive Data +Discovery engine then uses this index to perform exact data matching against virtually any +cloud or on-premises data repository. ![AnyID Connectors Solution Overview page](/images/accessanalyzer/11.6/solutions/anyid/overviewpage.webp) @@ -64,14 +64,14 @@ The jobs in the AnyID Connectors Solution are: may not be available, or an export is the best option. - [AnyID_EpicClarity Job](/docs/accessanalyzer/11.6/solutions/anyid/anyid_epicclarity.md) – Collects patient information from Epic including MRNs, SSNs, Subscriber IDs, and Account IDs. An - account with read access to the underlying Clarity Oracle database is required in order to run + account with read access to the underlying Clarity Oracle database is required to run queries. - [AnyID_Paycom Job](/docs/accessanalyzer/11.6/solutions/anyid/anyid_paycom.md) – Pulls employee information from Paycom including Name, Address, Date of Birth, and SSN. Contact - your Paycom administrator in order to generate the CSV export required for this job. + your Paycom administrator to generate the CSV export required for this job. - [AnyID_Salesforce Job](/docs/accessanalyzer/11.6/solutions/anyid/anyid_salesforce.md) – Collects Salesforce Contact details including Phone, Address, Email, and Date of birth. This job - requires API access to Salesforce in order to collect this information. + requires API access to Salesforce to collect this information. :::note See the individual job topics for information on recommended configurations. diff --git a/docs/accessanalyzer/11.6/solutions/aws/collection/1.aws_orgscan.md b/docs/accessanalyzer/11.6/solutions/aws/collection/1.aws_orgscan.md index 76f57bd4c8..54a959bd3f 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/collection/1.aws_orgscan.md +++ b/docs/accessanalyzer/11.6/solutions/aws/collection/1.aws_orgscan.md @@ -23,7 +23,7 @@ The 1.AWS_OrgScan job has the following configurable query: ### Configure the Org Scan Query The Org Scan query in the 1.AWS_OrgScan job has been preconfigured to run with the default settings -with the category of Collect Org Data. Follow the steps to set any desired customizations. +with the category of Collect Org Data. To set any desired customizations: **Step 1 –** Navigate to the **AWS** > **0.Collection** > **1.AWS_OrgScan** > **Configure** node and select the **Queries** node. diff --git a/docs/accessanalyzer/11.6/solutions/aws/collection/2.aws_s3scan.md b/docs/accessanalyzer/11.6/solutions/aws/collection/2.aws_s3scan.md index a12c4fbcb9..5de25860bc 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/collection/2.aws_s3scan.md +++ b/docs/accessanalyzer/11.6/solutions/aws/collection/2.aws_s3scan.md @@ -23,7 +23,7 @@ The 2.AWS_S3Scan job has the following configurable query: ### Configure the S3 Scan Query The S3 Scan query in the 2.AWS_S3 Scan job has been preconfigured to run with the default settings -with the category of Collect S3. Follow the steps to set any desired customizations. +with the category of Collect S3. To set any desired customizations: **Step 1 –** Navigate to the **AWS** > **0.Collection** > **2.AWS_S3Scan** > **Configure** node and select the **Queries** node. @@ -65,7 +65,7 @@ Navigate to the **AWS** > **0.Collection** > **2.AWS_S3Scan** > **Configure** no **Analysis** to view analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/aws/collection/3.aws_iamscan.md b/docs/accessanalyzer/11.6/solutions/aws/collection/3.aws_iamscan.md index 5ae6ab2180..65f291b452 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/collection/3.aws_iamscan.md +++ b/docs/accessanalyzer/11.6/solutions/aws/collection/3.aws_iamscan.md @@ -23,7 +23,7 @@ The 3.AWS_IAMScan job has the following configurable query: ### Configure the IAM Scan Query The IAM Scan query in the 3.AWS_IAMScan job has been preconfigured to run with the default settings -with the category of Collect IAM Data. Follow the steps to set any desired customizations. +with the category of Collect IAM Data. To set any desired customizations: **Step 1 –** Navigate to the **AWS** > **0.Collection** > **3.AWS_IAMScan** > **Configure** node and select the **Queries** node. @@ -55,7 +55,7 @@ View the analysis tasks by navigating to the **AWS** > **0.Collection** > **3.AW **Configure** node and selecting **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/aws/collection/4.aws_s3sddscan.md b/docs/accessanalyzer/11.6/solutions/aws/collection/4.aws_s3sddscan.md index 6ccd9bcc25..15e9750c77 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/collection/4.aws_s3sddscan.md +++ b/docs/accessanalyzer/11.6/solutions/aws/collection/4.aws_s3sddscan.md @@ -22,8 +22,8 @@ The 4.AWS_S3SDDScan job has the following configurable query: ### Configure the AWS S3 Sensitive Data Scan Query The AWS S3 Sensitive Data Scan query in the 4.AWS_S3SDDScan job has been preconfigured to run with -the default settings with the category of Collect SDD Data. Follow the steps to set any desired -customizations. +the default settings with the category of Collect SDD Data. To set any desired +customizations: **Step 1 –** Navigate to the **AWS** > **0.Collection** > **4.AWS_S3SDD Scan** > **Configure** node and select the **Queries** node. @@ -96,7 +96,7 @@ View the analysis tasks by navigating to the **AWS** > **0.Collection** > **4.AW **Configure** node and selecting **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/aws/collection/overview.md b/docs/accessanalyzer/11.6/solutions/aws/collection/overview.md index 7618ed66fa..e763389ea0 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/collection/overview.md +++ b/docs/accessanalyzer/11.6/solutions/aws/collection/overview.md @@ -19,6 +19,6 @@ The 0.Collection Job Group is comprised of: - [2.AWS_S3Scan Job](/docs/accessanalyzer/11.6/solutions/aws/collection/2.aws_s3scan.md) – Collects details about the AWS S3 buckets including details about the objects in those buckets - [3.AWS_IAMScan Job](/docs/accessanalyzer/11.6/solutions/aws/collection/3.aws_iamscan.md) - – Collects details about users, groups, policies, roles and other IAM related identities + – Collects details about users, groups, policies, roles, and other IAM related identities - [4.AWS_S3SDDScan Job](/docs/accessanalyzer/11.6/solutions/aws/collection/4.aws_s3sddscan.md) – Collects details about S3 objects containing sensitive data diff --git a/docs/accessanalyzer/11.6/solutions/aws/groups/aws_groupmembers.md b/docs/accessanalyzer/11.6/solutions/aws/groups/aws_groupmembers.md index 8d2ecefc24..ffce0c7067 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/groups/aws_groupmembers.md +++ b/docs/accessanalyzer/11.6/solutions/aws/groups/aws_groupmembers.md @@ -15,7 +15,7 @@ Navigate to the **AWS** > **3.Groups** > **AWS_GroupMembers** > **Configure** no **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/aws/groups/aws_nopolicygroups.md b/docs/accessanalyzer/11.6/solutions/aws/groups/aws_nopolicygroups.md index 9863da016e..3ec1b9195a 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/groups/aws_nopolicygroups.md +++ b/docs/accessanalyzer/11.6/solutions/aws/groups/aws_nopolicygroups.md @@ -14,7 +14,7 @@ Navigate to the **AWS** > **3.Groups** > **AWS_NoPolicyGroups** > **Configure** **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -35,4 +35,4 @@ produces the following preconfigured report: | Report | Description | Default Tags | Report Element | | ----------------------- | ----------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Groups With No Policies | This report identifies groups that do not have a policy assigned. | None | This report is comprised of the following elements:
  • Stacked Bar Chart – Displays top accounts by no policy group counts
  • Table – Shows no policy groups by accounts
  • Table – Provides details on no policy groups
| +| Groups With No Policies | This report identifies groups that don't have a policy assigned. | None | This report is comprised of the following elements:
  • Stacked Bar Chart – Displays top accounts by no policy group counts
  • Table – Shows no policy groups by accounts
  • Table – Provides details on no policy groups
| diff --git a/docs/accessanalyzer/11.6/solutions/aws/groups/aws_stalegroups.md b/docs/accessanalyzer/11.6/solutions/aws/groups/aws_stalegroups.md index d1f3d123fa..d5c7137089 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/groups/aws_stalegroups.md +++ b/docs/accessanalyzer/11.6/solutions/aws/groups/aws_stalegroups.md @@ -11,17 +11,17 @@ definition for staleness is set by default to 60 days. This can be configured. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +The Configuration section on a Job's overview page lets you easily modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/11.6/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. The AWS_StaleGroups job has the following configurable parameter: -- Days without login to consider an account stale +- Days without log in to consider an account stale See the -[Customizable Analysis Tasks for the AWS_StaleGroups Job](#customizable-analysis-tasks-for-the-aws_stalegroups-job) +[Customizable Analysis Tasks for the AWS_StaleGroups Job](#customizable-analysis-tasks-for-the-awsstalegroups-job) topic for additional information. ## Analysis Tasks for the AWS_StaleGroups Job @@ -30,7 +30,7 @@ Navigate to the **AWS** > **3.Groups** > **AWS_StaleGroups** > **Configure** nod **Analysis** to view the analysis tasks. :::warning -Do not deselect the selected analysis tasks. The analysis tasks are preconfigured for +Don't deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. Only modify the analysis tasks listed in the customizable analysis tasks section. ::: @@ -42,9 +42,9 @@ The following analysis tasks are selected by default: - Stale Group Details – Highlights the staleness of users in AWS groups. Creates the AWS_StaleGroup_Details table accessible under the job’s Results node. - - The number of days without login to consider an account stale can be customized. By default it + - The number of days without log in to consider an account stale can be customized. By default it is set to 60. See the - [Customizable Analysis Tasks for the AWS_StaleGroups Job](#customizable-analysis-tasks-for-the-aws_stalegroups-job) + [Customizable Analysis Tasks for the AWS_StaleGroups Job](#customizable-analysis-tasks-for-the-awsstalegroups-job) topic for additional information. - Stale Group Summary – Summarizes statistics for stale groups. Creates the AWS_StaleGroup_Summary @@ -57,7 +57,7 @@ The default values for parameters that can be customized are: | Analysis Task | Customizable Parameter Name | Default Value | Value Indicates | | ------------------- | --------------------------- | ------------- | ----------------------------------------------- | -| Stale Group Details | @StaleThreshold | 60 | Days without login to consider an account stale | +| Stale Group Details | @StaleThreshold | 60 | Days without log in to consider an account stale | See the [Configure the Customizable Parameters in an Analysis Task](/docs/accessanalyzer/11.6/admin/jobs/job/configure/analysis/analysiscustomizableparameters.md) diff --git a/docs/accessanalyzer/11.6/solutions/aws/organizations/aws_accounts.md b/docs/accessanalyzer/11.6/solutions/aws/organizations/aws_accounts.md index 1cb32163ad..183afb6aa7 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/organizations/aws_accounts.md +++ b/docs/accessanalyzer/11.6/solutions/aws/organizations/aws_accounts.md @@ -17,7 +17,7 @@ Navigate to the **AWS** > **1.Organizations** > **AWS_Accounts** > **Configure** **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/aws/organizations/aws_memberaccountusers.md b/docs/accessanalyzer/11.6/solutions/aws/organizations/aws_memberaccountusers.md index da09d1e711..36b26ac95c 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/organizations/aws_memberaccountusers.md +++ b/docs/accessanalyzer/11.6/solutions/aws/organizations/aws_memberaccountusers.md @@ -6,7 +6,7 @@ sidebar_position: 20 # AWS_MemberAccountUsers Job -The AWS_MemberAccountUsers job highlights users that are not located in the primary AWS Identity +The AWS_MemberAccountUsers job highlights users that aren't located in the primary AWS Identity Source, which is generally the Master AWS Account for the Organization. ## Analysis Tasks for the AWS_MemberAccountUsers Job @@ -15,7 +15,7 @@ Navigate to the **AWS** > **1.Organizations** > **AWS_MemberAccountUsers** > **C select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -36,4 +36,4 @@ produces the following preconfigured report: | Report | Description | Default Tags | Report Element | | -------------------- | -------------------------------------------------------------------------------------- | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Member Account Users | This report highlights user accounts that are not contained in the AWS Master Account. | None | This report is comprised of the following elements:
  • Stacked Bar Chart – Displays top member account users by org
  • Table – Shows member account users by Org
  • Table – Provides details on member account users
| +| Member Account Users | This report highlights user accounts that aren't contained in the AWS Master Account. | None | This report is comprised of the following elements:
  • Stacked Bar Chart – Displays top member account users by org
  • Table – Shows member account users by Org
  • Table – Provides details on member account users
| diff --git a/docs/accessanalyzer/11.6/solutions/aws/organizations/overview.md b/docs/accessanalyzer/11.6/solutions/aws/organizations/overview.md index f2dcf21188..197e1ce4b5 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/organizations/overview.md +++ b/docs/accessanalyzer/11.6/solutions/aws/organizations/overview.md @@ -19,5 +19,5 @@ The 1.Organizations job jroup is comprised of: manually by adding a line for each Organization in the temporary table #IdentitySourceAccount in the analysis task parameters for this job. - [AWS_MemberAccountUsers Job](/docs/accessanalyzer/11.6/solutions/aws/organizations/aws_memberaccountusers.md) - – Highlights users that are not located in the primary AWS Identity Source, which is generally the + – Highlights users that aren't located in the primary AWS Identity Source, which is generally the Master AWS Account for the Organization diff --git a/docs/accessanalyzer/11.6/solutions/aws/overview.md b/docs/accessanalyzer/11.6/solutions/aws/overview.md index 51f1a65efe..b2c4c0248f 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/overview.md +++ b/docs/accessanalyzer/11.6/solutions/aws/overview.md @@ -6,9 +6,9 @@ sidebar_position: 70 # AWS Solution -Enterprise Auditor for AWS allows organizations to secure their data residing in Amazon Web Services -(AWS) S3 platform, reducing their risk exposure through proactive, automated auditing and reporting -of S3 permissions, sensitive data, and ultimately a consolidated view of user access rights across +Enterprise Auditor for AWS helps organizations secure data stored in the Amazon Web Services +(AWS) S3 platform. It reduces risk exposure through proactive, automated auditing and reporting +of S3 permissions and sensitive data, giving you a consolidated view of user access rights across dozens of structured and unstructured data resources both on-premises and in the cloud. The AWS Solution is designed to provide information about data access such as: @@ -17,10 +17,10 @@ The AWS Solution is designed to provide information about data access such as: - Who is accessing your data - What sensitive data is being stored and accessed -The AWS Solution provides the ability to audit AWS IAM and S3. Enterprise Auditor uses the AWS +The AWS Solution lets you audit AWS IAM and S3. Enterprise Auditor uses the AWS solution to collect IAM users, groups, roles, and policies, as well as S3 permissions, content, and sensitive data from target AWS accounts. The solution requires a special Enterprise Auditor license. -It can be focused to only conduct auditing of AWS IAM. Additionally, the Sensitive Data Discovery +You can focus it to audit only AWS IAM. Additionally, the Sensitive Data Discovery Add-On enables the solution to search AWS S3 content for sensitive data. **Supported Platforms** @@ -37,16 +37,16 @@ topic for additional information. **Sensitive Data Discovery Considerations** The Sensitive Data Discovery Add-On must be installed on the Enterprise Auditor Console server, -which enables Sensitive Data criteria for scans. If running Sensitive Data Discovery (SDD) scans, it -will be necessary to increase the minimum amount of RAM. Each thread requires a minimum of 2 -additional GB of RAM per host. For example, if the job is configured to scan 8 hosts at a time , -then an extra 16 GB of RAM are required (8x2=16). +which enables Sensitive Data criteria for scans. If you run Sensitive Data Discovery (SDD) scans, +increase the minimum amount of RAM. Each thread requires a minimum of 2 +additional GB of RAM per host. For example, if you configure the job to scan 8 hosts at a time, +it requires an extra 16 GB of RAM (8 x 2 = 16). :::note -The Sensitive Data Discovery Add-on installation package installs the appropriate JDK -(Java) version on the server. The JDK deployed is prepackaged and does not require any -configuration; it has been preconfigured to work with Enterprise Auditor and should never be -customized through Java. It will not conflict with other JDKs or Java Runtimes in the same +The Sensitive Data Discovery Add-on installation package installs the appropriate Java +Development Kit (JDK) version on the server. The deployed JDK is prepackaged and doesn't require +any configuration; it comes preconfigured to work with Enterprise Auditor. Don't customize it +through Java. It won't conflict with other JDKs or Java Runtimes in the same environment. ::: @@ -58,7 +58,7 @@ Enterprise Auditor Instant Job Wizard. See the [Instant Job Wizard](/docs/accessanalyzer/11.6/admin/jobs/instantjobs/overview.md) topic for information on installing instant solutions from the Enterprise Auditor Library. -Once it has been installed into the Jobs tree, navigate to the solution: **Jobs** > **AWS**. +After it has been installed into the Jobs tree, navigate to the solution: **Jobs** > **AWS**. ## Job Groups diff --git a/docs/accessanalyzer/11.6/solutions/aws/policies/aws_custommanagedpolicies.md b/docs/accessanalyzer/11.6/solutions/aws/policies/aws_custommanagedpolicies.md index c572cbdcd5..eba8e250fd 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/policies/aws_custommanagedpolicies.md +++ b/docs/accessanalyzer/11.6/solutions/aws/policies/aws_custommanagedpolicies.md @@ -15,7 +15,7 @@ Navigate to the **AWS** > **5.Policies** > **AWS_CustomManagedPolicies** > **Con select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/aws/policies/aws_inlinepolicies.md b/docs/accessanalyzer/11.6/solutions/aws/policies/aws_inlinepolicies.md index f77fe04a05..92673ceb2d 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/policies/aws_inlinepolicies.md +++ b/docs/accessanalyzer/11.6/solutions/aws/policies/aws_inlinepolicies.md @@ -15,7 +15,7 @@ Navigate to the **AWS** > **5.Policies** > **AWS_InlinePolicies** > **Configure* **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/aws/policies/aws_managedpolicies.md b/docs/accessanalyzer/11.6/solutions/aws/policies/aws_managedpolicies.md index 73aa0a4c6d..247bb3852c 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/policies/aws_managedpolicies.md +++ b/docs/accessanalyzer/11.6/solutions/aws/policies/aws_managedpolicies.md @@ -14,7 +14,7 @@ Navigate to the **AWS** > **5.Policies** > **AWS_ManagedPolicies** > **Configure **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/aws/policies/aws_sensitivepolicies.md b/docs/accessanalyzer/11.6/solutions/aws/policies/aws_sensitivepolicies.md index 80bbaa301a..c012ae1dba 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/policies/aws_sensitivepolicies.md +++ b/docs/accessanalyzer/11.6/solutions/aws/policies/aws_sensitivepolicies.md @@ -15,7 +15,7 @@ Navigate to the **AWS** > **5.Policies** > **AWS_SensitivePolicies** > **Configu **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/aws/policies/aws_unusedmanagedpolicies.md b/docs/accessanalyzer/11.6/solutions/aws/policies/aws_unusedmanagedpolicies.md index 30e1bb42fb..335d036dab 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/policies/aws_unusedmanagedpolicies.md +++ b/docs/accessanalyzer/11.6/solutions/aws/policies/aws_unusedmanagedpolicies.md @@ -12,7 +12,7 @@ analysis task. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +The Configuration section on a Job's overview page lets you easily modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/11.6/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -22,7 +22,7 @@ The AWS_UnusedManagedPolicies job has the following configurable parameter: - True or False value to include policies managed by AWS See the -[Customizable Analysis Tasks for the AWS_UnusedManagedPolicies Job](#customizable-analysis-tasks-for-the-aws_unusedmanagedpolicies-job) +[Customizable Analysis Tasks for the AWS_UnusedManagedPolicies Job](#customizable-analysis-tasks-for-the-awsunusedmanagedpolicies-job) topic for additional information. ## Analysis Tasks for the AWS_UnusedManagedPolicies Job @@ -31,7 +31,7 @@ Navigate to the **AWS** > **5.Policies** > **AWS_UnusedManagedPolicies** > **Con select **Analysis** to view the analysis tasks. :::warning -Do not deselect the selected analysis tasks. The analysis tasks are preconfigured for +Don't deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. Only modify the analysis tasks listed in the customizable analysis tasks section. ::: @@ -44,7 +44,7 @@ The following analysis tasks are selected by default: AWS_UnusedPolicies_Details table accessible under the job’s Results node. - Optionally, AWS managed policies can be included by setting the parameter to True. See the - [Customizable Analysis Tasks for the AWS_UnusedManagedPolicies Job](#customizable-analysis-tasks-for-the-aws_unusedmanagedpolicies-job) + [Customizable Analysis Tasks for the AWS_UnusedManagedPolicies Job](#customizable-analysis-tasks-for-the-awsunusedmanagedpolicies-job) topic for additional information. - Unused Managed Policy Summary – Summary by AWS Organization of unused managed policies. Creates @@ -69,4 +69,4 @@ produces the following preconfigured report: | Report | Description | Default Tags | Report Element | | ----------------------- | --------------------------------------------------------------------------- | ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Unused Managed Policies | This report identifies policies that are not assigned to any group or user. | None | This report is comprised of the following elements:
  • Stacked Bar Chart – Displays unused managed policies by account
  • Table – Shows unused managed policies by account
  • Table – Provides details on unused managed policies
| +| Unused Managed Policies | This report identifies policies that aren't assigned to any group or user. | None | This report is comprised of the following elements:
  • Stacked Bar Chart – Displays unused managed policies by account
  • Table – Shows unused managed policies by account
  • Table – Provides details on unused managed policies
| diff --git a/docs/accessanalyzer/11.6/solutions/aws/policies/aws_userpolicies.md b/docs/accessanalyzer/11.6/solutions/aws/policies/aws_userpolicies.md index fb6674f5b0..e3b502dd5e 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/policies/aws_userpolicies.md +++ b/docs/accessanalyzer/11.6/solutions/aws/policies/aws_userpolicies.md @@ -15,7 +15,7 @@ Navigate to the **AWS** > **5.Policies** > **AWS_UserPolicies** > **Configure** **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/aws/recommended.md b/docs/accessanalyzer/11.6/solutions/aws/recommended.md index 1ac9319ac8..53f4de1ec5 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/aws/recommended.md @@ -7,7 +7,7 @@ sidebar_position: 10 # Recommended Configuration for the AWS Solution The AWS Solution is configured to inherit settings from the global Settings node. The Connection -Profile must be assigned before job execution. Once it is assigned to the job group, it can be run +Profile must be assigned before job execution. After it is assigned to the job group, it can be run directly or scheduled. **Dependencies** @@ -31,25 +31,25 @@ For AWS S3 Sensitive Data Discovery Auditing: [Sensitive Data Discovery Add-On Installation](/docs/accessanalyzer/11.6/install/sensitivedatadiscovery/overview.md) topic for additional information -Some of the 0.Collection job group queries can be scoped to target specific S3 Objects. However, it -is necessary for the SA_AWS_Instances table to be populated before attempting to scope the queries. -Therefore, the AWS_S3Scan job must be manually executed before attempting to scope the S3 queries. +Some of the 0.Collection job group queries can be scoped to target specific S3 Objects. However, the +SA_AWS_Instances table must be populated before you scope the queries. Therefore, run the +AWS_S3Scan job manually before you scope the S3 queries. **Target Host** -The AWS Data Collector identifies AWS instances via the created Roles and therefore does not require +The AWS Data Collector identifies AWS instances via the created Roles and therefore doesn't require a host list to be assigned. No target host is required (assign Local Host). **Connection Profile** The AWS Data Collector requires a specific set of permissions. The account used can be either a Web -Services (JWT) account or an Amazon Web Services account. Once the account has been provisioned, +Services (JWT) account or an Amazon Web Services account. After the account has been provisioned, create a custom Connection Profile containing the credentials for the targeted environment. See the [Amazon Web Services for User Credentials](/docs/accessanalyzer/11.6/admin/settings/connection/create/aws.md) topic for additional information. The Connection Profile is assigned under the **AWS** > **Settings** > **Connection** node. It is set -to **Use Default Profile**, as configured at the global Settings level. However, if this is not the +to **Use Default Profile**, as configured at the global Settings level. However, if this isn't the Connection Profile with the necessary permissions for targeting the AWS instances, click the **Select one of the following user defined profiles** option and select the appropriate Connection Profile. @@ -60,16 +60,16 @@ topic for additional information on creating a Connection Profile. **Access Token** -Creating the Connection Profile requires having the **Access Key ID** and the **Secret Access Key** -that was generated by the Amazon Web Services application. See the +To create the Connection Profile, you need the **Access Key ID** and the **Secret Access Key** +that the Amazon Web Services application generated. See the [Configure AWS for Scans](/docs/accessanalyzer/11.6/requirements/aws/configurescans.md) topic for additional information. **Schedule Frequency** Schedule the AWS job group to run weekly or daily, depending on the amount of data in the -environment. If there are frequent AWS changes within the target environment, then it can be -executed more often. It is best to rerun it anytime AWS changes might have occurred. +environment. If there are frequent AWS changes within the target environment, you can run it +more often. It is best to rerun it anytime AWS changes might have occurred. **History Retention** diff --git a/docs/accessanalyzer/11.6/solutions/aws/roles/aws_roles.md b/docs/accessanalyzer/11.6/solutions/aws/roles/aws_roles.md index 5bf92f8b2a..7e0971842f 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/roles/aws_roles.md +++ b/docs/accessanalyzer/11.6/solutions/aws/roles/aws_roles.md @@ -14,7 +14,7 @@ Navigate to the **AWS** > **4.Roles** > **AWS_Roles** > **Configure** node and s to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/aws/roles/aws_staleroles.md b/docs/accessanalyzer/11.6/solutions/aws/roles/aws_staleroles.md index 004ed1a065..41ca15a779 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/roles/aws_staleroles.md +++ b/docs/accessanalyzer/11.6/solutions/aws/roles/aws_staleroles.md @@ -6,23 +6,23 @@ sidebar_position: 20 # AWS_StaleRoles Job -The AWS_StaleRoles job provides details on roles that are considered stale. Highlighting roles that -have not been used in more than 60 days and those that have never been used. The 60 day parameter is +The AWS_StaleRoles job provides details on roles that are considered stale, highlighting roles that +haven't been used in more than 60 days and those that have never been used. The 60 day parameter is configurable. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +The Configuration section on a Job's overview page lets you easily modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/11.6/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. The AWS_StaleRoles job has the following configurable parameter: -- Days without login to consider an account stale +- Days without log in to consider an account stale See the -[Customizable Analysis Tasks for the AWS_StaleRoles Job](#customizable-analysis-tasks-for-the-aws_staleroles-job) +[Customizable Analysis Tasks for the AWS_StaleRoles Job](#customizable-analysis-tasks-for-the-awsstaleroles-job) topic for additional information. ## Analysis Tasks for the AWS_StaleRoles Job @@ -31,7 +31,7 @@ Navigate to the **AWS** > **4.Roles** > **AWS_StaleRoles** > **Configure** node **Analysis** to view the analysis tasks. :::warning -Do not deselect the selected analysis tasks. The analysis tasks are preconfigured for +Don't deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. Only modify the analysis tasks listed in the customizable analysis tasks section. ::: @@ -43,9 +43,9 @@ The following analysis tasks are selected by default: - Stale Role Details – Highlights the roles in AWS that are considered stale. Creates the AWS_StaleRole_Details table accessible under the job’s Results node. - - The number of days without login to consider an account stale can be customized. By default it + - The number of days without log in to consider an account stale can be customized. By default it is set to 60. See the - [Customizable Analysis Tasks for the AWS_StaleRoles Job](#customizable-analysis-tasks-for-the-aws_staleroles-job) + [Customizable Analysis Tasks for the AWS_StaleRoles Job](#customizable-analysis-tasks-for-the-awsstaleroles-job) topic for additional information. - Stale Role Summary – Summarizes stale roles by AWS Account. Creates the AWS_StaleRole_Summary @@ -57,7 +57,7 @@ The default values for parameters that can be customized are: | Analysis Task | Customizable Parameter Name | Default Value | Value Indicates | | ------------------ | --------------------------- | ------------- | ------------------------------------------------ | -| Stale Role Details | @StaleThreshold | 60 | Days without login to consider an account stale. | +| Stale Role Details | @StaleThreshold | 60 | Days without log in to consider an account stale. | See the [Configure the Customizable Parameters in an Analysis Task](/docs/accessanalyzer/11.6/admin/jobs/job/configure/analysis/analysiscustomizableparameters.md) diff --git a/docs/accessanalyzer/11.6/solutions/aws/roles/overview.md b/docs/accessanalyzer/11.6/solutions/aws/roles/overview.md index 79d33702fd..5c833d6853 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/roles/overview.md +++ b/docs/accessanalyzer/11.6/solutions/aws/roles/overview.md @@ -15,5 +15,5 @@ The 4.Roles job group is comprised of: - [AWS_Roles Job](/docs/accessanalyzer/11.6/solutions/aws/roles/aws_roles.md) – Provides details on roles in the AWS IAM environment - [AWS_StaleRoles Job](/docs/accessanalyzer/11.6/solutions/aws/roles/aws_staleroles.md) - – Provides details on roles that are considered stale. Highlighting roles that have not been used + – Provides details on roles that are considered stale, highlighting roles that haven't been used in more than 60 days and those that have never been used. diff --git a/docs/accessanalyzer/11.6/solutions/aws/s3content/aws_s3buckets.md b/docs/accessanalyzer/11.6/solutions/aws/s3content/aws_s3buckets.md index 2321c25df7..54cd40d914 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/s3content/aws_s3buckets.md +++ b/docs/accessanalyzer/11.6/solutions/aws/s3content/aws_s3buckets.md @@ -14,7 +14,7 @@ Navigate to the **AWS** > **7.S3 Content** > **AWS_S3Buckets** > **Configure** n **Analysis** to view the analysis task. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/aws/s3content/aws_s3buckettags.md b/docs/accessanalyzer/11.6/solutions/aws/s3content/aws_s3buckettags.md index 9a5a9c8488..6375ecf74d 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/s3content/aws_s3buckettags.md +++ b/docs/accessanalyzer/11.6/solutions/aws/s3content/aws_s3buckettags.md @@ -15,7 +15,7 @@ Navigate to the **AWS** > **7.S3 Content** > **AWS_S3BucketTags** > **Configure* **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/aws/s3permissions/aws_brokeninheritance.md b/docs/accessanalyzer/11.6/solutions/aws/s3permissions/aws_brokeninheritance.md index 6e1ddedc0f..4f8665efe9 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/s3permissions/aws_brokeninheritance.md +++ b/docs/accessanalyzer/11.6/solutions/aws/s3permissions/aws_brokeninheritance.md @@ -15,7 +15,7 @@ Navigate to the **AWS** > **6.S3 Permissions** > **AWS_BrokenInheritance** > **C select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/aws/s3permissions/aws_effectivepermissions.md b/docs/accessanalyzer/11.6/solutions/aws/s3permissions/aws_effectivepermissions.md index b8f5fa5160..e1f93554d6 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/s3permissions/aws_effectivepermissions.md +++ b/docs/accessanalyzer/11.6/solutions/aws/s3permissions/aws_effectivepermissions.md @@ -15,7 +15,7 @@ Navigate to the **AWS** > **6.S3 Permissions** > **AWS_EffectivePermissions** > and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/aws/s3permissions/aws_openbuckets.md b/docs/accessanalyzer/11.6/solutions/aws/s3permissions/aws_openbuckets.md index 95196c3989..f7a3e9f687 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/s3permissions/aws_openbuckets.md +++ b/docs/accessanalyzer/11.6/solutions/aws/s3permissions/aws_openbuckets.md @@ -15,7 +15,7 @@ Navigate to the **AWS** > **6.S3 Permissions** > **AWS_OpenBuckets** > **Configu **Analysis** to view the analysis task. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/aws/sensitivedata/aws_sensitivedata.md b/docs/accessanalyzer/11.6/solutions/aws/sensitivedata/aws_sensitivedata.md index 62af019e74..f39192555e 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/sensitivedata/aws_sensitivedata.md +++ b/docs/accessanalyzer/11.6/solutions/aws/sensitivedata/aws_sensitivedata.md @@ -15,7 +15,7 @@ Navigate to the **AWS** > **8.S3 Sensitive Data** > **AWS_SensitiveData** > **Co select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/aws/sensitivedata/aws_sensitivedata_permissions.md b/docs/accessanalyzer/11.6/solutions/aws/sensitivedata/aws_sensitivedata_permissions.md index e6f4bef4e7..9c21d5b586 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/sensitivedata/aws_sensitivedata_permissions.md +++ b/docs/accessanalyzer/11.6/solutions/aws/sensitivedata/aws_sensitivedata_permissions.md @@ -15,7 +15,7 @@ Navigate to the **AWS** > **8.S3 Sensitive Data** > **AWS_SensitiveData_Permissi **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/aws/users/aws_accesskeys.md b/docs/accessanalyzer/11.6/solutions/aws/users/aws_accesskeys.md index d5c6af5a1d..c5bfc1f9f0 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/users/aws_accesskeys.md +++ b/docs/accessanalyzer/11.6/solutions/aws/users/aws_accesskeys.md @@ -15,7 +15,7 @@ Navigate to the **AWS** > **2.Users** > **AWS_AccessKeys** > **Configure** node **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/aws/users/aws_mfastatus.md b/docs/accessanalyzer/11.6/solutions/aws/users/aws_mfastatus.md index 0a152a3939..392d4efad6 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/users/aws_mfastatus.md +++ b/docs/accessanalyzer/11.6/solutions/aws/users/aws_mfastatus.md @@ -15,7 +15,7 @@ Navigate to the **AWS** > **2.Users** > **AWS_MFAStatus** > **Configure** node a **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/aws/users/aws_rootaccounts.md b/docs/accessanalyzer/11.6/solutions/aws/users/aws_rootaccounts.md index 4dc182a0f8..7ac67b26ea 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/users/aws_rootaccounts.md +++ b/docs/accessanalyzer/11.6/solutions/aws/users/aws_rootaccounts.md @@ -15,7 +15,7 @@ Navigate to the **AWS** > **2.Users** > **AWS_RootAccounts** > **Configure** nod **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/aws/users/aws_staleusers.md b/docs/accessanalyzer/11.6/solutions/aws/users/aws_staleusers.md index f3ffd13f26..e7bf2514f4 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/users/aws_staleusers.md +++ b/docs/accessanalyzer/11.6/solutions/aws/users/aws_staleusers.md @@ -11,7 +11,7 @@ used, highlighting those over specified number of days (default 60) or that have ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +The Configuration section on a Job's overview page lets you modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/11.6/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -21,7 +21,7 @@ The AWS_StaleUsers job has the following configurable parameter: - Number of days before considering a user stale See the -[Customizable Analysis Tasks for the AWS_StaleUsers Job](#customizable-analysis-tasks-for-the-aws_staleusers-job) +[Customizable Analysis Tasks for the AWS_StaleUsers Job](#customizable-analysis-tasks-for-the-awsstaleusers-job) topic for additional information. ## Analysis Tasks for the AWS_StaleUsers Job @@ -30,7 +30,7 @@ Navigate to the **AWS** > **2.Users** > **AWS_StaleUsers** > **Configure** node **Analysis** to view the analysis tasks. :::warning -Do not deselect the selected analysis tasks. The analysis tasks are preconfigured for +Don't deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. Only modify the analysis tasks listed in the customizable analysis tasks section. ::: @@ -39,11 +39,11 @@ this job. Only modify the analysis tasks listed in the customizable analysis tas The following analysis tasks are selected by default: -- Stale Users – Identifies user accounts that have not been logged in to in the last 60 days. +- Stale Users – Identifies user accounts that have not logged in during the last 60 days. Creates the AWS_StaleUser_Details table accessible under the job’s Results node. - The number of days can be customized from the default value of 60. See the - [Customizable Analysis Tasks for the AWS_StaleUsers Job](#customizable-analysis-tasks-for-the-aws_staleusers-job) + [Customizable Analysis Tasks for the AWS_StaleUsers Job](#customizable-analysis-tasks-for-the-awsstaleusers-job) topic for additional information. - Stale User Summary – Summarizes stale users in AWS. Creates the AWS_StaleUser_Summary table diff --git a/docs/accessanalyzer/11.6/solutions/box/activity/forensics/box_deletions.md b/docs/accessanalyzer/11.6/solutions/box/activity/forensics/box_deletions.md index 7f02069345..63e945e5ae 100644 --- a/docs/accessanalyzer/11.6/solutions/box/activity/forensics/box_deletions.md +++ b/docs/accessanalyzer/11.6/solutions/box/activity/forensics/box_deletions.md @@ -16,7 +16,7 @@ Navigate to **Box** > **1.Activity** > **Forensics** > **Box_Deletions** > **Con select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/box/activity/forensics/box_downloads.md b/docs/accessanalyzer/11.6/solutions/box/activity/forensics/box_downloads.md index a761c01b0d..7852e55b4e 100644 --- a/docs/accessanalyzer/11.6/solutions/box/activity/forensics/box_downloads.md +++ b/docs/accessanalyzer/11.6/solutions/box/activity/forensics/box_downloads.md @@ -15,7 +15,7 @@ Navigate to **Box** > **1.Activity** > **Forensics** > **Box_Downloads** > **Con select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/box/activity/forensics/box_externaluseractivity.md b/docs/accessanalyzer/11.6/solutions/box/activity/forensics/box_externaluseractivity.md index 53363675c7..a750a1d7fc 100644 --- a/docs/accessanalyzer/11.6/solutions/box/activity/forensics/box_externaluseractivity.md +++ b/docs/accessanalyzer/11.6/solutions/box/activity/forensics/box_externaluseractivity.md @@ -17,7 +17,7 @@ Navigate to **Box** > **1.Activity** > **Forensics** > **Box_ExternalUserActivit node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/box/activity/forensics/box_externalusercollaborations.md b/docs/accessanalyzer/11.6/solutions/box/activity/forensics/box_externalusercollaborations.md index 78a5fff721..fa96b398aa 100644 --- a/docs/accessanalyzer/11.6/solutions/box/activity/forensics/box_externalusercollaborations.md +++ b/docs/accessanalyzer/11.6/solutions/box/activity/forensics/box_externalusercollaborations.md @@ -16,7 +16,7 @@ Navigate to **Box** > **1.Activity** > **Forensics** > **Box_ExternalUserCollabo **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/box/activity/forensics/box_permissionchanges.md b/docs/accessanalyzer/11.6/solutions/box/activity/forensics/box_permissionchanges.md index a8d7053430..82251dfd5a 100644 --- a/docs/accessanalyzer/11.6/solutions/box/activity/forensics/box_permissionchanges.md +++ b/docs/accessanalyzer/11.6/solutions/box/activity/forensics/box_permissionchanges.md @@ -15,7 +15,7 @@ Navigate to **Box** > **1.Activity** > **Forensics** > **Box_PermissionChanges** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/box/activity/forensics/box_sharing.md b/docs/accessanalyzer/11.6/solutions/box/activity/forensics/box_sharing.md index 6efc486ab4..d4a87de329 100644 --- a/docs/accessanalyzer/11.6/solutions/box/activity/forensics/box_sharing.md +++ b/docs/accessanalyzer/11.6/solutions/box/activity/forensics/box_sharing.md @@ -14,7 +14,7 @@ Navigate to **Box** > **1.Activity** > **Forensics** > **Box_Sharing** > **Confi select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/box/activity/forensics/overview.md b/docs/accessanalyzer/11.6/solutions/box/activity/forensics/overview.md index 61f097bcd6..d9ebc48e58 100644 --- a/docs/accessanalyzer/11.6/solutions/box/activity/forensics/overview.md +++ b/docs/accessanalyzer/11.6/solutions/box/activity/forensics/overview.md @@ -8,7 +8,7 @@ sidebar_position: 10 The Forensics Job Group highlights deletions, file downloads, permissions changes, external user activity, collaboration activity and high-risk collaborations within the targeted Box environment. -It is dependent on data collected by the 0.Collection Job Group, also housed in the Box Job Group. +It depends on data collected by the 0.Collection Job Group, also housed in the Box Job Group. The jobs that comprise the 1.Activity Job Group process analysis tasks and generate a report. ![Forensics Job Group in the Jobs Tree](/images/accessanalyzer/11.6/solutions/box/activity/forensics/jobstree.webp) @@ -23,7 +23,7 @@ The Forensics Job Group is comprised of: – Identifies and analyzes external user activity which has occurred over the past 30 days - [Box_ExternalUserCollaborations Job](/docs/accessanalyzer/11.6/solutions/box/activity/forensics/box_externalusercollaborations.md) – Identifies collaboration invites sent to external users. These collaborations should be reviewed - to ensure sensitive data is not being shared outside of your organization. + to ensure sensitive data isn't being shared outside of your organization. - [Box_PermissionChanges Job](/docs/accessanalyzer/11.6/solutions/box/activity/forensics/box_permissionchanges.md) – Provides details on permission changes that have occurred over the past 30 days - [Box_Sharing Job](/docs/accessanalyzer/11.6/solutions/box/activity/forensics/box_sharing.md) diff --git a/docs/accessanalyzer/11.6/solutions/box/activity/suspiciousactivity/box_failedlogins.md b/docs/accessanalyzer/11.6/solutions/box/activity/suspiciousactivity/box_failedlogins.md index bc98ff2534..bab6450c17 100644 --- a/docs/accessanalyzer/11.6/solutions/box/activity/suspiciousactivity/box_failedlogins.md +++ b/docs/accessanalyzer/11.6/solutions/box/activity/suspiciousactivity/box_failedlogins.md @@ -16,7 +16,7 @@ Navigate to **Box** > **1.Activity** > **Suspicious Activity** > **Box_FailedLog **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/box/activity/suspiciousactivity/box_firsttimefolderaccess.md b/docs/accessanalyzer/11.6/solutions/box/activity/suspiciousactivity/box_firsttimefolderaccess.md index 2db8168705..6227531eaa 100644 --- a/docs/accessanalyzer/11.6/solutions/box/activity/suspiciousactivity/box_firsttimefolderaccess.md +++ b/docs/accessanalyzer/11.6/solutions/box/activity/suspiciousactivity/box_firsttimefolderaccess.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **Box** > **1.Activity** > **Suspic **Box_FirstTimeFolderAccess** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/box/activity/suspiciousactivity/box_unusualdownloadactivity.md b/docs/accessanalyzer/11.6/solutions/box/activity/suspiciousactivity/box_unusualdownloadactivity.md index 05cb379a03..fd0d2d32cc 100644 --- a/docs/accessanalyzer/11.6/solutions/box/activity/suspiciousactivity/box_unusualdownloadactivity.md +++ b/docs/accessanalyzer/11.6/solutions/box/activity/suspiciousactivity/box_unusualdownloadactivity.md @@ -16,7 +16,7 @@ Navigate to **Box** > **1.Activity** > **Suspicious Activity** > **Box_UnusualDo **Configure** node and select **Analysis** to view analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -33,4 +33,4 @@ produces the following pre-configured report: | Report | Description | Default Tags | Report Elements | | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Unusual Download Activity | This report provides insight into download activity that deviates from the normal range of expected downloads.  This is determined by using historical data for each file. | None | This report is comprised of two elements:
  • Bar Chart – Displays top 5 most recent unusual download activity
  • Table – Provides details on unusual download activity
| +| Unusual Download Activity | This report provides insight into download activity that deviates from the normal range of expected downloads. This is determined by using historical data for each file. | None | This report is comprised of two elements:
  • Bar Chart – Displays top 5 most recent unusual download activity
  • Table – Provides details on unusual download activity
| diff --git a/docs/accessanalyzer/11.6/solutions/box/activity/suspiciousactivity/box_unusualuseractivity.md b/docs/accessanalyzer/11.6/solutions/box/activity/suspiciousactivity/box_unusualuseractivity.md index 1774bb9acc..19cb96bc30 100644 --- a/docs/accessanalyzer/11.6/solutions/box/activity/suspiciousactivity/box_unusualuseractivity.md +++ b/docs/accessanalyzer/11.6/solutions/box/activity/suspiciousactivity/box_unusualuseractivity.md @@ -16,7 +16,7 @@ Navigate to **Box** > **1.Activity** > **Suspicious Activity** > **Box_UnusualUs **Configure** node and select **Analysis** to view analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -33,4 +33,4 @@ pre-configured report: | Report | Description | Default Tags | Report Elements | | --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Unusual User Activity | This report provides insight into user activity that deviates from the normal range of expected activity.  This is determined by using historical data for each user. | None | This report is comprised of two elements:
  • Bar Chart – Displays top 5 most recent unusual user activity
  • Table – Provides details on unusual user activity
| +| Unusual User Activity | This report provides insight into user activity that deviates from the normal range of expected activity. This is determined by using historical data for each user. | None | This report is comprised of two elements:
  • Bar Chart – Displays top 5 most recent unusual user activity
  • Table – Provides details on unusual user activity
| diff --git a/docs/accessanalyzer/11.6/solutions/box/activity/suspiciousactivity/box_weekendactivity.md b/docs/accessanalyzer/11.6/solutions/box/activity/suspiciousactivity/box_weekendactivity.md index c7924e7ab7..bb2e5e16f1 100644 --- a/docs/accessanalyzer/11.6/solutions/box/activity/suspiciousactivity/box_weekendactivity.md +++ b/docs/accessanalyzer/11.6/solutions/box/activity/suspiciousactivity/box_weekendactivity.md @@ -16,7 +16,7 @@ Navigate to **Box** > **1.Activity** > **Suspicious Activity** > **Box_WeekendAc **Configure** node and select **Analysis** to view analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/box/activity/usagestatistics/box_folders_mostactive.md b/docs/accessanalyzer/11.6/solutions/box/activity/usagestatistics/box_folders_mostactive.md index 06eec4748d..0291f6b7b9 100644 --- a/docs/accessanalyzer/11.6/solutions/box/activity/usagestatistics/box_folders_mostactive.md +++ b/docs/accessanalyzer/11.6/solutions/box/activity/usagestatistics/box_folders_mostactive.md @@ -15,7 +15,7 @@ Navigate to **Box** > **1.Activity** > **Usage Statistics** > **Box_Folders_Most **Configure** node and select **Analysis** to view analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/box/activity/usagestatistics/box_folders_stale.md b/docs/accessanalyzer/11.6/solutions/box/activity/usagestatistics/box_folders_stale.md index 21185f5f7c..c9cccf481b 100644 --- a/docs/accessanalyzer/11.6/solutions/box/activity/usagestatistics/box_folders_stale.md +++ b/docs/accessanalyzer/11.6/solutions/box/activity/usagestatistics/box_folders_stale.md @@ -16,7 +16,7 @@ Navigate to **Box** > **1.Activity** > **Usage Statistics** > **Box_Folders_Stal node and select **Analysis** to view analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/box/activity/usagestatistics/box_users_mostactive.md b/docs/accessanalyzer/11.6/solutions/box/activity/usagestatistics/box_users_mostactive.md index d5a9eaa41b..050a6f00ab 100644 --- a/docs/accessanalyzer/11.6/solutions/box/activity/usagestatistics/box_users_mostactive.md +++ b/docs/accessanalyzer/11.6/solutions/box/activity/usagestatistics/box_users_mostactive.md @@ -15,7 +15,7 @@ Navigate to **Box** > **1.Activity** > **Usage Statistics** > **Box_Users_MostAc **Configure** node and select **Analysis** to view analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/box/box_access.md b/docs/accessanalyzer/11.6/solutions/box/box_access.md index 517c7610cf..ec234621b3 100644 --- a/docs/accessanalyzer/11.6/solutions/box/box_access.md +++ b/docs/accessanalyzer/11.6/solutions/box/box_access.md @@ -7,7 +7,7 @@ sidebar_position: 50 # Box_Access Job The Box_Access Job analyzes access granted to users and groups in an organization's Box environment -in order to report on effective access rights, file-level permissions, and inactive access rights +to report on effective access rights, file-level permissions, and inactive access rights that can be revoked. ## Analysis Tasks for the Box_Access Job @@ -16,7 +16,7 @@ Navigate to **Box** > **Box_Access** > **Configure** node and select **Analysis* tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/box/box_groupmembership.md b/docs/accessanalyzer/11.6/solutions/box/box_groupmembership.md index c6e3efd09c..edb8018763 100644 --- a/docs/accessanalyzer/11.6/solutions/box/box_groupmembership.md +++ b/docs/accessanalyzer/11.6/solutions/box/box_groupmembership.md @@ -15,7 +15,7 @@ Navigate to **Box** > **Box_GroupMembership** > **Configure** node and select ** analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/box/collection/1-box_access_scans.md b/docs/accessanalyzer/11.6/solutions/box/collection/1-box_access_scans.md index a4e1f9477e..413bf3179e 100644 --- a/docs/accessanalyzer/11.6/solutions/box/collection/1-box_access_scans.md +++ b/docs/accessanalyzer/11.6/solutions/box/collection/1-box_access_scans.md @@ -6,24 +6,24 @@ sidebar_position: 10 # 1-Box_Access Scans Job -The 1-Box_Access Scans Job collects the data which will be further analyzed in order to provide +The 1-Box_Access Scans Job collects the data which will be further analyzed to provide details on Box access rights, policies, configurations, and content. ## Queries for the 1-Box_Access Scans Job The Scan Query uses the Box Data Collector to target all Box hosts and has been preconfigured to use -the Scan Box Permissions Category. If this query is not configured but has the access token, a full -scan of all folders at full depth is performed. Optionally, configure the query to limit the depth +the Scan Box Permissions Category. If this query isn't configured but has the access token, the query +performs a full scan of all folders at full depth. Optionally, configure the query to limit the depth of the scan. ![Queries for the 1-Box_Access Scans Job](/images/accessanalyzer/11.6/solutions/box/collection/accessqueries.webp) The 1-Box_Access Scans Job has the following queries: -- Scan Query – Collects access data which will be further analyzed in order to provide details on +- Scan Query – Collects access data which will be further analyzed to provide details on Box access rights, policies, configurations, and content -Prior to the first execution, it is necessary to authenticate to the targeted Box environment. This +Before the first execution, authenticate to the targeted Box environment. This is done on the Authenticate page of the Scan query. Additionally, the following default configurations are commonly customized: @@ -35,54 +35,54 @@ configurations are commonly customized: - Not scoped -See the [Configure the 1-Box_Access Scans Job](#configure-the-1-box_access-scans-job) section for +See the [Configure the 1-Box_Access Scans Job](#configure-the-1-boxaccess-scans-job) section for instructions. ### Configure the 1-Box_Access Scans Job -The 1-Box_Access Scans Job contains the Scan Query. Follow the steps to configure the query. +The 1-Box_Access Scans Job contains the Scan Query. To configure the query: **Step 1 –** Navigate to the **Box** > **0.Collection** > **1-Box_Access Scans** > **Configure** node and select **Queries**. -**Step 1 –** In the Query Selection view, select the Scan Query and click **Query Properties**. The +**Step 2 –** In the Query Selection view, select the Scan Query and click **Query Properties**. The Query Properties window opens. -**Step 2 –** Select the **Data Source** tab, and click **Configure**. The Box Data Collector Wizard +**Step 3 –** Select the **Data Source** tab, and click **Configure**. The Box Data Collector Wizard opens. ![Box Data Collector Wizard Exclusions page](/images/accessanalyzer/11.6/solutions/box/collection/accessexclusions.webp) -**Step 3 –** On the Exclusions Page: +**Step 4 –** On the Exclusions Page: - Add folders to be excluded - Add folders to be included (scope scan to only these folders) ![Box Data Collector Wizard Additional Scoping page](/images/accessanalyzer/11.6/solutions/box/collection/accessadditionalscoping.webp) -**Step 4 –** On the Additional Scoping page: +**Step 5 –** On the Additional Scoping page: - Optionally, select this option to limit the depth of the scan across the targeted Box account ![Box Data Collector Wizard Scope by User page](/images/accessanalyzer/11.6/solutions/box/collection/accessuserscope.webp) -**Step 5 –** On the Scope By User Page: +**Step 6 –** On the Scope By User Page: - Optionally, limit the scope of the scan to specified users by providing a CSV file ![Box Data Collector Wizard Authenticate page](/images/accessanalyzer/11.6/solutions/box/collection/accessauthenticate.webp) -**Step 6 –** The Authenticate page is where the connection to the target Box environment is +**Step 7 –** The Authenticate page is where the connection to the target Box environment is configured. Click **Authorize** to launch the BoxLogin window and generate an authorization code. This code allows Enterprise Auditor to report on the Box Enterprise. :::note -Authentication to the target Box environment only needs to be completed once, prior to the +Authentication to the target Box environment only needs to be completed once, before the first scan and only in one of the scan jobs. ::: -**Step 7 –** Navigate to the Summary page, click **Finish** to save any setting modifications or +**Step 8 –** Navigate to the Summary page, click **Finish** to save any setting modifications or click **Cancel** if no changes were made. Then click **OK** to close the Query Properties window. The 1-Box_Access Scans Job will execute according to the connection settings configuration. diff --git a/docs/accessanalyzer/11.6/solutions/box/collection/1-box_activity_scans.md b/docs/accessanalyzer/11.6/solutions/box/collection/1-box_activity_scans.md index 75e5edee31..a248622939 100644 --- a/docs/accessanalyzer/11.6/solutions/box/collection/1-box_activity_scans.md +++ b/docs/accessanalyzer/11.6/solutions/box/collection/1-box_activity_scans.md @@ -6,7 +6,7 @@ sidebar_position: 20 # 1-Box_Activity Scans Job -The 1-Box_Activity Scans Job collects the data which will be further analyzed in order to provide +The 1-Box_Activity Scans Job collects the data which will be further analyzed to provide visibility into user activity events within Box. ## Queries for the 1-Box_Activity Scans Job @@ -18,12 +18,12 @@ the Scan Box Permissions Category. The 1-Box_Activity Scans Job has the following queries: -- Activity Scan – Collects activity data which will be further analyzed in order to provide +- Activity Scan – Collects activity data which will be further analyzed to provide visibility into user activity events within Box. -Prior to the first execution, it is necessary to authenticate to the targeted Box environment if -this has not already been done when configuring the 1-Box_Access Scans Job. This is done on the -Authenticate page of the Activity Scan query. Additionally, the following default configurations are +Before the first execution, authenticate to the targeted Box environment if you haven't already done +so while configuring the 1-Box_Access Scans Job. This is done on the Authenticate page of the +Activity Scan query. Additionally, the following default configurations are commonly customized: - Exclusions page: @@ -34,13 +34,13 @@ commonly customized: - Not scoped -See the [Configure the 1-Box_Activity Scans Job](#configure-the-1-box_activity-scans-job) section +See the [Configure the 1-Box_Activity Scans Job](#configure-the-1-boxactivity-scans-job) section for instructions. ### Configure the 1-Box_Activity Scans Job -The 1-Box_Activity Scans Job contains the Activity Scan Query. Follow the steps to configure the -query. +The 1-Box_Activity Scans Job contains the Activity Scan Query. To configure the +query: **Step 1 –** Navigate to the **Box** > **0.Collection** > **1-Box_Activity Scans** > **Configure** node and select **Queries**. @@ -90,7 +90,7 @@ configured. Click **Authorize** to launch the BoxLogin window and generate an au This code allows Enterprise Auditor to report on the Box Enterprise. :::note -Authentication to the target Box environment only needs to be completed once, prior to the +Authentication to the target Box environment only needs to be completed once, before the first scan and only in one of the scan jobs. ::: diff --git a/docs/accessanalyzer/11.6/solutions/box/collection/2-box_import.md b/docs/accessanalyzer/11.6/solutions/box/collection/2-box_import.md index fe89ebe8c3..a2832f43f5 100644 --- a/docs/accessanalyzer/11.6/solutions/box/collection/2-box_import.md +++ b/docs/accessanalyzer/11.6/solutions/box/collection/2-box_import.md @@ -7,8 +7,8 @@ sidebar_position: 30 # 2-Box_Import Job The 2-Box_Import Job takes the data that has been collected from the 1-Box_Access Scans Job and the -1-Box_Activity Scans Job and imports it to the Enterprise Auditor database to be analyzed in order -to provide detailed reports on Box access rights, policies, configurations, activities, and content. +1-Box_Activity Scans Job and imports it to the Enterprise Auditor database to be analyzed to provide +detailed reports on Box access rights, policies, configurations, activities, and content. ## Queries for the 2-Box_Import Job @@ -20,5 +20,5 @@ Permissions Category. The 2-Box_Import Job has the following query: - Import - Takes the data that has been collected from Box and imports it to the Enterprise Auditor - database to be analyzed in order to provide detailed reports on Box access rights, policies, + database to be analyzed to provide detailed reports on Box access rights, policies, configurations, activities, and content. diff --git a/docs/accessanalyzer/11.6/solutions/box/collection/overview.md b/docs/accessanalyzer/11.6/solutions/box/collection/overview.md index 735ebba523..c6e3b63b7a 100644 --- a/docs/accessanalyzer/11.6/solutions/box/collection/overview.md +++ b/docs/accessanalyzer/11.6/solutions/box/collection/overview.md @@ -6,7 +6,7 @@ sidebar_position: 20 # 0.Collection Job Group -The 0.Collection Job Group collects data which will be further analyzed in order to provide details +The 0.Collection Job Group collects data which will be further analyzed to provide details on Box access rights, policies, configurations, activities, and content. ![Box > Collection Job Group in the Jobs Tree](/images/accessanalyzer/11.6/solutions/box/collection/jobstree.webp) @@ -14,12 +14,12 @@ on Box access rights, policies, configurations, activities, and content. The 0.Collection Job Group is comprised of: - [1-Box_Access Scans Job](/docs/accessanalyzer/11.6/solutions/box/collection/1-box_access_scans.md) - – Collects the data which will be further analyzed in order to provide details on Box access + – Collects the data which will be further analyzed to provide details on Box access rights, policies, configurations, and content - [1-Box_Activity Scans Job](/docs/accessanalyzer/11.6/solutions/box/collection/1-box_activity_scans.md) - – Collects the data which will be further analyzed in order to provide visibility into user + – Collects the data which will be further analyzed to provide visibility into user activity events within Box - [2-Box_Import Job](/docs/accessanalyzer/11.6/solutions/box/collection/2-box_import.md) – Takes the data that has been collected from Box and imports it to the Enterprise Auditor - database to be analyzed in order to provide detailed reports on Box access rights, policies, + database to be analyzed to provide detailed reports on Box access rights, policies, configurations, activities, and content diff --git a/docs/accessanalyzer/11.6/solutions/box/content/box_filemetrics.md b/docs/accessanalyzer/11.6/solutions/box/content/box_filemetrics.md index d40b9eac91..06f38ab9b9 100644 --- a/docs/accessanalyzer/11.6/solutions/box/content/box_filemetrics.md +++ b/docs/accessanalyzer/11.6/solutions/box/content/box_filemetrics.md @@ -20,7 +20,7 @@ Navigate to **Box** > **2.Content** > **Box_FileMetrics** > **Configure** node a **Analysis** to view analysis tasks. :::warning -Most of these analysis tasks should never be modified and never be deselected. +Don't modify or deselect most of these analysis tasks. ::: @@ -32,7 +32,7 @@ The following analysis tasks are selected by default: Results node - Set to consider content stale after 30 days which is the @STALETHRESHOLD parameter value - See the - [Customize Analysis Tasks for the Box_FileMetrics Job](#customize-analysis-tasks-for-the-box_filemetrics-job) + [Customize Analysis Tasks for the Box_FileMetrics Job](#customize-analysis-tasks-for-the-boxfilemetrics-job) topic for additional information. - File Count by User – Creates the Box_FileMetrics_UserFileCount table accessible under the job’s Results node diff --git a/docs/accessanalyzer/11.6/solutions/box/content/box_foldermetrics.md b/docs/accessanalyzer/11.6/solutions/box/content/box_foldermetrics.md index 64d01c8a3a..79fec47730 100644 --- a/docs/accessanalyzer/11.6/solutions/box/content/box_foldermetrics.md +++ b/docs/accessanalyzer/11.6/solutions/box/content/box_foldermetrics.md @@ -22,7 +22,7 @@ Navigate to **Box** > **2.Content** > **Box_FolderMetrics** > **Configure** node **Analysis** to view analysis tasks. :::warning -Most of these analysis tasks should never be modified and never be deselected. +Don't modify or deselect most of these analysis tasks. ::: @@ -34,7 +34,7 @@ The following analysis tasks are selected by default: Results node - Set to consider content stale after 30 days which is the @STALETHRESHOLD parameter value - See the - [Customizable Analysis Tasks for the Box_FolderMetrics Job](#customizable-analysis-tasks-for-the-box_foldermetrics-job) + [Customizable Analysis Tasks for the Box_FolderMetrics Job](#customizable-analysis-tasks-for-the-boxfoldermetrics-job) topic for additional information. - Largest Folders – Creates the Box_FolderMetrics_Largest table accessible under the job’s Results node diff --git a/docs/accessanalyzer/11.6/solutions/box/overview.md b/docs/accessanalyzer/11.6/solutions/box/overview.md index c5427e87dc..c5b7248bf7 100644 --- a/docs/accessanalyzer/11.6/solutions/box/overview.md +++ b/docs/accessanalyzer/11.6/solutions/box/overview.md @@ -7,8 +7,8 @@ sidebar_position: 80 # Box Solution The Box solution set contains jobs to provide visibility into Box access rights, policies, -configurations, activities, and more, ensuring you never lose sight or control of your critical -assets residing in Box. +configurations, activities, and more, so you can monitor and control your critical assets residing in +Box. **Supported Platforms** @@ -23,7 +23,7 @@ topic for additional information. **Location** The Box Solution requires a special Enterprise Auditor license. It can be installed from the Instant -Job Wizard. Once it has been installed into the Jobs tree, navigate to the solution: **Jobs** > +Job Wizard. After it has been installed into the Jobs tree, navigate to the solution: **Jobs** > **Box**. ![Box Solution in the Jobs Tree](/images/accessanalyzer/11.6/solutions/box/jobstree.webp) @@ -41,7 +41,7 @@ an organization's Box environment. The Box Solution has the following job groups and jobs: - [0.Collection Job Group](/docs/accessanalyzer/11.6/solutions/box/collection/overview.md) - – Collects the data which will be further analyzed in order to provide details on Box access + – Collects the data which will be further analyzed to provide details on Box access rights, policies, configurations, activities, and content - [1.Activity Job Group](/docs/accessanalyzer/11.6/solutions/box/activity/overview.md) – Identifies long term trends of activity providing insight into user activity, usage statistics, @@ -50,7 +50,7 @@ The Box Solution has the following job groups and jobs: – Analyzes and summarizes the content of the Box environment, highlighting users with the most content as well as what type of content exists - [Box_Access Job](/docs/accessanalyzer/11.6/solutions/box/box_access.md) - – Analyzes access granted to users and groups in an organization's Box environment in order to + – Analyzes access granted to users and groups in an organization's Box environment to report on effective access rights, file-level permissions, and inactive access rights that can be revoked - [Box_GroupMembership Job](/docs/accessanalyzer/11.6/solutions/box/box_groupmembership.md) diff --git a/docs/accessanalyzer/11.6/solutions/box/recommended.md b/docs/accessanalyzer/11.6/solutions/box/recommended.md index 1de3044c39..72e0c207b5 100644 --- a/docs/accessanalyzer/11.6/solutions/box/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/box/recommended.md @@ -6,11 +6,11 @@ sidebar_position: 10 # Recommended Configurations for the Box Solution -The jobs that run analysis tasks in the Box Solution requires the host list to be assigned. +The jobs that run analysis tasks in the Box Solution require you to assign the host list. **Dependencies** -- The .Active Directory Inventory Job Group must be successfully run prior to running this Job Group +- The .Active Directory Inventory Job Group must be successfully run before running this Job Group - 2-Box_Import Job – Imports data collected by the 1-Box_Access Scans Job and 1-Box_Activity Scans Job @@ -20,20 +20,20 @@ The jobs that run analysis tasks in the Box Solution requires the host list to b Within host inventory, the Box hosts will return a HostStatus of **Offline**. -If multiple Enterprise_IDs are to be scanned, it is necessary to duplicate the jobs within the -0.Collection Job Group for each target host. Since the 2-Box_Import Job must always be run after the -1-Box_Access Scans Job and 1-Box_Activity Scans Job, it is a best practice to set up sub-job groups -for each target named to identify the target, for example EMEA Box. Copying the jobs will append a -number to the job’s name. Once authorization codes have been generated for each 1-Box_Access Scans -Job and 1-Box_Activity Scans Job, then the solution can be scheduled to run as desired. +To scan multiple Enterprise_IDs, duplicate the jobs within the 0.Collection Job Group for each target +host. Since the 2-Box_Import Job must always run after the 1-Box_Access Scans Job and +1-Box_Activity Scans Job, set up sub-job groups for each target, named to identify the target, for +example EMEA Box. Copying the jobs will append a number to the job’s name. After you generate +authorization codes for each 1-Box_Access Scans Job and 1-Box_Activity Scans Job, you can schedule +the solution to run as desired. **Connection Profile** The Box Solution requires a specific credential for the Connection Profile which has access to the -SA Installer location. It is also necessary to authenticate to the target Box environment, which is -done through the Box Data Collector query configuration. An Enterprise Admin account (or Co-Admin -account with permission to **Run new reports and access existing reports** enabled) credential is -needed to generate an authorization code in the form of an Access Token. This can be done through +SA Installer location. You must also authenticate to the target Box environment through the Box Data +Collector query configuration. You need an Enterprise Admin account (or Co-Admin account with +permission to **Run new reports and access existing reports** enabled) to generate an authorization +code in the form of an Access Token. This can be done through the query configuration either in the 1-Box_Access Scans Job’ Authentication wizard page or the 1-Box_Activity Scans Job’s Authentication wizard page of the Box Data Collector Wizard. See the [Box Data Collector](/docs/accessanalyzer/11.6/admin/datacollector/box/overview.md) @@ -43,7 +43,7 @@ topic for additional information. The Access Token is valid for 60 days. If Box scans are running on a regular schedule, then the Access Token automatically refreshes once an hour. However, if it has been more than 60 days since -the last scan, it is necessary to regenerate the Access Token. +the last scan, regenerate the Access Token. **Schedule Frequency** @@ -57,15 +57,15 @@ This solution can be run with the default query configuration. However, the foll - 1-Box_Access Scans Scan query - 1-Box_Activity Scans Activity Scan query -The Box_Import Job's Import query is preconfigured to run a full import and should not be modified. +The Box_Import Job's Import query is preconfigured to run a full import and shouldn't be modified. **Analysis Configuration** This solution can be run with the default analysis configuration. However, the following parameters can be modified: -- The @STALETHRESHOLD parameter determines the number of days after which content is considered - stale. It is set to default of 30 days. The @STALETHRESHOLD parameter can be customized in the +- The @STALETHRESHOLD parameter determines the number of days after which the job considers content + stale. It defaults to 30 days. The @STALETHRESHOLD parameter can be customized in the following analysis tasks: - 2.Content > Box_FileMetrics in the File Metrics Details analysis task - 2.Content > Box_FolderMetrics Folder in the Metrics Details analysis task @@ -78,8 +78,7 @@ can be modified: depth. **Step 3 –** In the 1-Box_Access Scans Job, configure the Scan query to generate an authentication -code to authenticate to the targeted Box environment. This step only needs to be run prior to the -first scan. +code to authenticate to the targeted Box environment. Run this step only before the first scan. **Step 4 –** (Optional) Modify analysis task parameters for the reporting jobs. diff --git a/docs/accessanalyzer/11.6/solutions/databases/db2/collection/db2_configuration.md b/docs/accessanalyzer/11.6/solutions/databases/db2/collection/db2_configuration.md index a673a52350..513d58dd63 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/db2/collection/db2_configuration.md +++ b/docs/accessanalyzer/11.6/solutions/databases/db2/collection/db2_configuration.md @@ -21,12 +21,12 @@ The query is: ## Recommended Configuration for the Configuration Query -Prior to running an Db2 0.Collection query, you must establish a connection to the appropriate IBM -Db2 server. As long as that connection is set up first, it is recommended that no configuration -changes be made to the 0.Collection jobs before they run. +Before running an Db2 0.Collection query, you must establish a connection to the appropriate IBM +Db2 server. As long as that connection is set up first, don't make configuration +changes to the 0.Collection jobs before they run. It is also recommended that the connection only be established for the 1-Db2 SensitiveDataScan Job. -Once the connection is established, it applies to all jobs in the 0.Collection job group. It does +After the connection is established, it applies to all jobs in the 0.Collection job group. It does not apply to any other job groups. For additional information on establishing a database connection, see [1-Db2_SensitiveDataScan](/docs/accessanalyzer/11.6/solutions/databases/db2/collection/db2_sensitivedatascan.md). diff --git a/docs/accessanalyzer/11.6/solutions/databases/db2/collection/db2_permissionscan.md b/docs/accessanalyzer/11.6/solutions/databases/db2/collection/db2_permissionscan.md index 7826540635..919bd54af6 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/db2/collection/db2_permissionscan.md +++ b/docs/accessanalyzer/11.6/solutions/databases/db2/collection/db2_permissionscan.md @@ -13,7 +13,7 @@ This job collects Db2 database level permissions from all the targeted Db2 datab The 2-Db2_PermissionScan Job uses the SQL Data Collector for queries. :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -25,12 +25,12 @@ The query is: ## Recommended Configuration for the Db2 Permission Query -Prior to running an Db2 0.Collection query, you must establish a connection to the appropriate IBM -Db2 server. As long as that connection is set up first, it is recommended that no configuration -changes be made to the 0.Collection jobs before they run. +Before running an Db2 0.Collection query, you must establish a connection to the appropriate IBM +Db2 server. As long as that connection is set up first, don't make configuration +changes to the 0.Collection jobs before they run. It is also recommended that the connection only be established for the 1-Db2 SensitiveDataScan Job. -Once the connection is established, it applies to all jobs in the 0.Collection job group. It does +After the connection is established, it applies to all jobs in the 0.Collection job group. It does not apply to any other job groups. For additional information on establishing a database connection, see [1-Db2_SensitiveDataScan](/docs/accessanalyzer/11.6/solutions/databases/db2/collection/db2_sensitivedatascan.md). @@ -41,7 +41,7 @@ Navigate to the **Databases** > **0.Collection** > **Db2** > **2-Db2_PermissionS **Configure** node and select Analysis to view the Analysis Tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -52,5 +52,5 @@ The default analysis tasks are: - Update Instance Name — Updates the instance name with a port if there are multiple instances in a single host -- AIC Permissions Import — Imports Db2 permissions to the AIC +- AIC Permissions Import — Imports Db2 permissions to the Access Information Center (AIC) - AIC Roles Import — Imports roles to the AIC for Db2 diff --git a/docs/accessanalyzer/11.6/solutions/databases/db2/collection/db2_sensitivedatascan.md b/docs/accessanalyzer/11.6/solutions/databases/db2/collection/db2_sensitivedatascan.md index 5cf531ef35..df98278ac4 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/db2/collection/db2_sensitivedatascan.md +++ b/docs/accessanalyzer/11.6/solutions/databases/db2/collection/db2_sensitivedatascan.md @@ -21,14 +21,14 @@ The query is: ## Recommended Configuration for the SensitiveDataScan Query -It is only necessary to set up the connection for the 1-Db2 SensitiveDataScan Job. Once the -connection is established, custom configurations apply to all other job queries within the -0.Collection job group. Follow the steps to customize configurations. +You only need to set up the connection for the 1-Db2 SensitiveDataScan Job. After you establish the +connection, custom configurations apply to all other job queries within the 0.Collection job group. +To customize configurations: **Step 1 –** Navigate to the Databases > 0.Collection > Db2 > 1-Db2_SensitiveDataScan > Configure node and select Queries. -**Step 2 –** In the Query Selection view, select the SensitiveDataScan query click on Query +**Step 2 –** In the Query Selection view, select the SensitiveDataScan query click Query Properties. The Query Properties window appears. **Step 3 –** Select the Data Source tab, and click Configure. The SQL Data Collector Wizard opens @@ -40,7 +40,7 @@ with Sensitive Data Collection category selected. ![Sensitive Data Scan Settings](/images/accessanalyzer/11.6/solutions/databases/db2/collection/sensitivedatajoboptions.webp) -**Step 5 –** To modify sensitive data scan options, select the desired scan options. See the +**Step 5 –** To modify sensitive data scan options, select the scan options you want. See the [SQL: Options](/docs/accessanalyzer/11.6/admin/datacollector/sql/options.md) page for additional information. @@ -55,7 +55,7 @@ may significantly increase scan time. ![Select Criteria](/images/accessanalyzer/11.6/solutions/databases/db2/collection/sensitivedatacriteria.webp) -**Step 7 –** To modify criteria, click on **Use the following selected criteria:** and select your +**Step 7 –** To modify criteria, click **Use the following selected criteria:** and select your choices. By default, the Sensitive Data Scan job is set to **Use Global Criteria**. :::note @@ -84,14 +84,14 @@ query, you must establish a connection to the database. **Step 10 –** In the Manage Connections window, enter the following information: - Instance Label — Custom name of the instance -- Database System — A drop down containing all available database servers. Select the Db2LUW server +- Database System — A dropdown containing all available database servers. Select the Db2LUW server to configure Db2 queries. - Service Name — Custom name of the service - Host — Name or IP address of the host where the database is located. Host list is IBM DB2 - Port Number — Port number for the selected database - Default Database — Default Database -**Step 11 –** After completing the above information fields, click **Test Connection** to validate +**Step 11 –** After completing these information fields, click **Test Connection** to validate the new connection. Once validated, click **Create New Connection** to finalize the connection. **Step 12 –** Navigate to the Filter page. Select Only select database objects or **All database @@ -106,14 +106,14 @@ page. **Step 13 –** Click Retrieve. The Available database objects box will populate. -**Step 14 –** Add the Databases and instances to be audited. Databases and instances can be added in +**Step 14 –** Add the databases and instances that you want to audit. Add them in the following ways: -- Select the desired database objects and click Add. +- Select the database objects you want and click Add. - Use the Import CSV button to import a list from a CSV file, if desired. - Optionally use the Add Custom Filter button to create and apply a custom filter. -Selected database objects to be audited will display. +Selected database objects will display. **Step 15 –** Click **Next** and navigate to the Summary page, click Finish to save any setting modifications or click Cancel if no changes were made. Then click OK to close the Query Properties @@ -127,7 +127,7 @@ Navigate to the **Databases** > **0.Collection** > **Db2** > **1-Db2_SensitiveDa **Configure** node and select **Analysis** to view the Analysis Tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -140,4 +140,5 @@ The default analysis tasks are: single host - Db2 Matches — Brings the Db2 SDD Matches View to the Enterprise Auditor console - Db2 Match Hits — Brings the Db2 Match Hits View to the Enterprise Auditor console -- AIC Sensitive Data Import — Db2 Match Imports discovered Db2 sensitive data to the AIC +- AIC Sensitive Data Import — Db2 Match Imports discovered Db2 sensitive data to the Access + Information Center (AIC) diff --git a/docs/accessanalyzer/11.6/solutions/databases/db2/db2_databasesizing.md b/docs/accessanalyzer/11.6/solutions/databases/db2/db2_databasesizing.md index 4b1b4c2212..37a5ba4356 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/db2/db2_databasesizing.md +++ b/docs/accessanalyzer/11.6/solutions/databases/db2/db2_databasesizing.md @@ -18,7 +18,7 @@ Navigate to the **Jobs** > **Databases** > **Db2** > **Configuration** > **Db2_ **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/db2/overview.md b/docs/accessanalyzer/11.6/solutions/databases/db2/overview.md index f3a20ec617..0c68bf283f 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/db2/overview.md +++ b/docs/accessanalyzer/11.6/solutions/databases/db2/overview.md @@ -30,7 +30,7 @@ then an extra 16 GB of RAM are required (8x2=16). :::note The Sensitive Data Discovery Add-on installation package installs the appropriate JDK -(Java) version on the server. The JDK deployed is prepackaged and does not require any +(Java) version on the server. The JDK deployed is prepackaged and doesn't require any configuration; it has been preconfigured to work with Enterprise Auditor and should never be customized through Java. It will not conflict with other JDKs or Java Runtimes in the same environment. @@ -40,7 +40,7 @@ environment. **Location** The Db2 Solution requires a special Enterprise Auditor license. It can be installed from the -Enterprise Auditor Instant Job Wizard. Once it has been installed in the Jobs tree, navigate to the +Enterprise Auditor Instant Job Wizard. After it has been installed in the Jobs tree, navigate to the solution: Jobs > **Databases** > **Db2**. The 0.Collection Job Group collects the data. The Db2 Solution Set Collection group is designed to diff --git a/docs/accessanalyzer/11.6/solutions/databases/db2/permissions/db2_directpermissions.md b/docs/accessanalyzer/11.6/solutions/databases/db2/permissions/db2_directpermissions.md index c39fdf4969..99efcabec8 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/db2/permissions/db2_directpermissions.md +++ b/docs/accessanalyzer/11.6/solutions/databases/db2/permissions/db2_directpermissions.md @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **Databases** > **Db2** > **Permissions** > **Db2_Dir **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/db2/permissions/db2_effectivepermissions.md b/docs/accessanalyzer/11.6/solutions/databases/db2/permissions/db2_effectivepermissions.md index 32a88aea72..7e848cb622 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/db2/permissions/db2_effectivepermissions.md +++ b/docs/accessanalyzer/11.6/solutions/databases/db2/permissions/db2_effectivepermissions.md @@ -16,7 +16,7 @@ Navigate to the **Jobs** > **Databases** > **Db2** > **Permissions** > Tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/db2/recommended.md b/docs/accessanalyzer/11.6/solutions/databases/db2/recommended.md index 04fa896d49..1472017063 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/db2/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/databases/db2/recommended.md @@ -33,7 +33,7 @@ scheduled. - .Instance Discovery Job Group run successfully -**Targeted Host(s)** +**Targeted Hosts** The Db2 Job Group has been configured to inherit the host list assignment from the collection group level. @@ -45,7 +45,7 @@ The host list assignment should be assigned under the **Databases** > **0.Collec The SQL Data Collector requires a specific set of permissions. See the Permissions section for necessary permissions. The account used can be either an Active Directory account or a SQL account. -Once the account has been provisioned, create a custom Connection Profile containing the credentials +After the account has been provisioned, create a custom Connection Profile containing the credentials for the targeted environment. See the [SQL Custom Connection Profile & Default Dynamic Host List](/docs/accessanalyzer/11.6/admin/datacollector/sql/configurejob.md) topic for additional information. @@ -54,7 +54,7 @@ The Connection Profile should be assigned under the Databases > 0.Collection > D Connection node. It is set to Use the Default Profile, as configured at the global settings level. However, since this may not be the Connection Profile with the necessary permissions for the assigned hosts, click the radio button for the Select one of the following user defined profiles -option and select the appropriate Connection Profile drop-down menu. +option and select the appropriate Connection Profile dropdown menu. See the [Connection](/docs/accessanalyzer/11.6/admin/settings/connection/overview.md) @@ -77,7 +77,7 @@ Run the solution at the top level. **Workflow** 1. Install IBM Db2 Server Client and required clients and drivers -2. Configure and assign host list and connection profile(s) +2. Configure and assign host list and connection profiles 3. Define the connection information 4. Schedule the .Instance Discovery job group and 0.Collection job group to run as desired 5. Review the reports generated by the 0.Collection job group diff --git a/docs/accessanalyzer/11.6/solutions/databases/db2/sensitivedata/db2_sensitivedata.md b/docs/accessanalyzer/11.6/solutions/databases/db2/sensitivedata/db2_sensitivedata.md index 54075bc468..15cc92d08a 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/db2/sensitivedata/db2_sensitivedata.md +++ b/docs/accessanalyzer/11.6/solutions/databases/db2/sensitivedata/db2_sensitivedata.md @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **Databases** > **Db2** > **Sensitive Data** > **Db2_ **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/db2/sensitivedata/db2_sensitivedatapermissions.md b/docs/accessanalyzer/11.6/solutions/databases/db2/sensitivedata/db2_sensitivedatapermissions.md index 825bc13d59..ee34866614 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/db2/sensitivedata/db2_sensitivedatapermissions.md +++ b/docs/accessanalyzer/11.6/solutions/databases/db2/sensitivedata/db2_sensitivedatapermissions.md @@ -16,7 +16,7 @@ Navigate to the **Jobs** > **Databases** > **Db2** > **Sensitive Data** > tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/mongodb/collection/mongodb_configuration.md b/docs/accessanalyzer/11.6/solutions/databases/mongodb/collection/mongodb_configuration.md index e2b646d5f3..85e12a386e 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/mongodb/collection/mongodb_configuration.md +++ b/docs/accessanalyzer/11.6/solutions/databases/mongodb/collection/mongodb_configuration.md @@ -14,7 +14,7 @@ configuration settings for use in the following analysis jobs and respective rep The MongoDB_Configuration Job uses the NoSQL Data Collector for queries. :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/mongodb/collection/mongodb_sensitivedatascan.md b/docs/accessanalyzer/11.6/solutions/databases/mongodb/collection/mongodb_sensitivedatascan.md index 887beddcfe..9e0bcea2f3 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/mongodb/collection/mongodb_sensitivedatascan.md +++ b/docs/accessanalyzer/11.6/solutions/databases/mongodb/collection/mongodb_sensitivedatascan.md @@ -26,7 +26,7 @@ The query is: ## Configure the MongoDB SDD Query The MongoDB SDD Query is preconfigured to run using the default settings for the Sensitive Data -Collection category. Follow the steps to customize configurations. +Collection category. To customize configurations: **Step 1 –** Navigate to the **Databases** > **0.Collection** > **MongoDB** > **MongoDB_SensitiveDataScan** > **Configure** node and select Queries. @@ -37,7 +37,7 @@ The Query Properties window opens. **Step 3 –** Select the Data Source tab, and click Configure. The NoSQL Data Collector Wizard opens. :::warning -Do not make changes to wizard pages not listed in these steps. They have been +Don't make changes to wizard pages not listed in these steps. They have been pre-configured for this job. ::: @@ -47,7 +47,7 @@ pre-configured for this job. ![Sensitive Data Scan Settings](/images/accessanalyzer/11.6/install/application/options.webp) -**Step 5 –** Select the desired scan options. +**Step 5 –** Select the scan options you want. **Step 6 –** Navigate to the [NoSQL: Criteria](/docs/accessanalyzer/11.6/admin/datacollector/nosql/criteria.md) @@ -103,7 +103,7 @@ Connections window. **Step 13 –** On the Filter page, click Retrieveto populate the Servers pane with the databases and collections. -**Step 14 –** (Optional) Right click on an object in the list to include or exclude it from the +**Step 14 –** (Optional) Right click an object in the list to include or exclude it from the sensitive data scan, or build /edit a pattern to create a custom filter. See the [NoSQL: Filter](/docs/accessanalyzer/11.6/admin/datacollector/nosql/filter.md) topic for additional information. @@ -122,7 +122,7 @@ Navigate to the Databases > > 0.Collection > MongoDB > MongoDB_SensitiveDataScan and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -134,4 +134,4 @@ The default analysis tasks are: - NoSQL Instances — Brings the SA_NoSQL_Instances to view in SA - Matches View — Brings the MongoDB matches view to the Enterprise Auditor console - Match Hits View — Brings the MongoDB match hits view to the Enterprise Auditor console -- MongoDB SDD AIC Import — Imports MongoDB SDD into the AIC +- MongoDB SDD AIC Import — Imports MongoDB SDD into the Access Information Center (AIC) diff --git a/docs/accessanalyzer/11.6/solutions/databases/mongodb/collection/overview.md b/docs/accessanalyzer/11.6/solutions/databases/mongodb/collection/overview.md index db106a3e21..4e8477cbd6 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/mongodb/collection/overview.md +++ b/docs/accessanalyzer/11.6/solutions/databases/mongodb/collection/overview.md @@ -7,7 +7,7 @@ sidebar_position: 20 # 0.Collection Job Group The MongoDB Solution Collection group is designed to collect high level summary information from -targeted MongoDB Servers.  This information is used by other jobs in the MongoDB Solution Set for +targeted MongoDB Servers. This information is used by other jobs in the MongoDB Solution Set for further analysis and producing respective reports. ![0](/images/accessanalyzer/11.6/solutions/databases/mongodb/collection/0.collecitonjobgroup.webp) diff --git a/docs/accessanalyzer/11.6/solutions/databases/mongodb/mongodb_databasesizing.md b/docs/accessanalyzer/11.6/solutions/databases/mongodb/mongodb_databasesizing.md index 45af4c7cc8..d24e6540e6 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/mongodb/mongodb_databasesizing.md +++ b/docs/accessanalyzer/11.6/solutions/databases/mongodb/mongodb_databasesizing.md @@ -12,7 +12,7 @@ Navigate to the **Jobs > Databases > MongoDB > Configuration > MongoDB_Databa node and select Analysis to view the Analysis Tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/mongodb/mongodb_sensitivedata.md b/docs/accessanalyzer/11.6/solutions/databases/mongodb/mongodb_sensitivedata.md index c1ce414157..707ecc1af1 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/mongodb/mongodb_sensitivedata.md +++ b/docs/accessanalyzer/11.6/solutions/databases/mongodb/mongodb_sensitivedata.md @@ -22,7 +22,7 @@ Navigate to the MongoDB > **Databases** > **Sensitive Data**> MongoDB_SensitiveD and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/mongodb/overview.md b/docs/accessanalyzer/11.6/solutions/databases/mongodb/overview.md index 2039fb8c46..ec89f9429d 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/mongodb/overview.md +++ b/docs/accessanalyzer/11.6/solutions/databases/mongodb/overview.md @@ -15,16 +15,16 @@ access the data, and how each database has been configured. As part of Stealthbits comprehensive Data Access Governance suite for structured and unstructured data, Enterprise Auditor for MongoDB automates the process of understanding where MongoDB databases -exist and provides an overview of the MongoDB environment in order to answer questions around data +exist and provides an overview of the MongoDB environment to answer questions around data access: - Who has access to your data? - Where is sensitive data being stored? -With visibility into every corner of MongoDB, organizations can proactively highlight and prioritize -risks to sensitive data. Additionally, organizations can automate manual, time-consuming, and -expensive processes associated with compliance, security, and operations to easily adhere to best -practices that keep MongoDB Server safe and operational. +With complete visibility into MongoDB, organizations can proactively highlight and prioritize risks +to sensitive data. Additionally, organizations can automate manual, time-consuming, and expensive +processes associated with compliance, security, and operations to adhere to best practices that keep +MongoDB Server safe and operational. **Supported Platforms** @@ -52,7 +52,7 @@ resources on the Enterprise Auditor server. :::note The Sensitive Data Discovery Add-on installation package installs the appropriate JDK -(Java) version on the server. The JDK deployed is prepackaged and does not require any +(Java) version on the server. The JDK deployed is prepackaged and doesn't require any configuration; it has been preconfigured to work with Enterprise Auditor and should never be customized through Java. It will not conflict with other JDKs or Java Runtimes in the same environment. @@ -62,7 +62,7 @@ environment. **Location** The Structured Sensitive Data Discovery License is required to run the MongoDB Solution. The MongoDB -Solution can be installed from the Enterprise Auditor Instant Job Wizard. Once it has been installed +Solution can be installed from the Enterprise Auditor Instant Job Wizard. After it has been installed into the Jobs tree, navigate to the solution: Jobs > **Databases** > MongoDB. The 0.Collection Job Group scans MongoDB instances on the target hosts, and collects diff --git a/docs/accessanalyzer/11.6/solutions/databases/mongodb/recommended.md b/docs/accessanalyzer/11.6/solutions/databases/mongodb/recommended.md index b17ed9c6ee..53896b14f3 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/mongodb/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/databases/mongodb/recommended.md @@ -18,9 +18,9 @@ scheduled. StealthAUDIT Console server Some of the 0.Collection Job Group queries can be scoped to target specific databases/instances. -However, it is necessary to add the databases to the query first. +However, add the databases to the query first. -**Targeted Host(s)** +**Targeted Hosts** The 0.Collection Job Group must be set to run against a custom host list containing the MongoDB database instances / clusters. @@ -29,7 +29,7 @@ database instances / clusters. The NoSQL Data Collector requires a specific set of permission. See the Permissions section for necessary permissions. The account used can be either an Active Directory account or a SQL account. -Once the account has been provisioned, create a custom Connection Profile containing the credentials +After the account has been provisioned, create a custom Connection Profile containing the credentials for the targeted environment. See the [NoSQL Custom Connection Profile & Host List](/docs/accessanalyzer/11.6/admin/datacollector/nosql/configurejob.md) topic for additional information. @@ -38,7 +38,7 @@ The Connection Profile should be assigned under the MongoDB > 0.Collection > Set node. It is set to Use the Default Profile, as configured at the global settings level. However, since this may not be the Connection Profile with the necessary permissions for the assigned hosts, click the radio button for the Select one of the following user defined profiles option and select -the appropriate Connection Profile drop-down menu. +the appropriate Connection Profile dropdown menu. See the [Connection](/docs/accessanalyzer/11.6/admin/settings/connection/overview.md) @@ -48,8 +48,7 @@ topic for additional information. One of the most important decisions to make is how frequently to collect this data. The MongoDB Job Group can be scheduled to run as desired depending on the types of auditing being conducted and the -scope of the target environment. The general recommendation is to schedule the solution to run -daily. +scope of the target environment. Schedule the solution to run daily. **Run Order** diff --git a/docs/accessanalyzer/11.6/solutions/databases/mysql/collection/mysql_configuration.md b/docs/accessanalyzer/11.6/solutions/databases/mysql/collection/mysql_configuration.md index f89ec97af2..20f13c79ff 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/mysql/collection/mysql_configuration.md +++ b/docs/accessanalyzer/11.6/solutions/databases/mysql/collection/mysql_configuration.md @@ -14,7 +14,7 @@ settings for use in the following analysis jobs and respective reports. The MySQL_Configuration Job uses the SQL Data Collector for queries. :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/mysql/collection/mysql_sensitivedatascan.md b/docs/accessanalyzer/11.6/solutions/databases/mysql/collection/mysql_sensitivedatascan.md index d9fb59b921..c89c1ed8b7 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/mysql/collection/mysql_sensitivedatascan.md +++ b/docs/accessanalyzer/11.6/solutions/databases/mysql/collection/mysql_sensitivedatascan.md @@ -24,25 +24,25 @@ The query is: ### Configure the SensitiveDataScan Query The MySQL_SensitiveDataScan Job is preconfigured to run using the default settings for the Sensitive -Data Collection category. Follow the steps to customize configurations. +Data Collection category. To customize configurations: **Step 1 –** Navigate to the Databases > 0.Collection > MySQL > MySQL_SensitiveDataScan > Configure node and select Queries. -**Step 2 –** In the Query Selection view, select the Sensitive Data Scan query click on Query +**Step 2 –** In the Query Selection view, select the Sensitive Data Scan query click Query Properties. The Query Properties window appears. **Step 3 –** Select the Data Source tab, and click Configure. The SQL Data Collector Wizard opens. :::warning -Do not make changes to other wizard pages as they have been pre-configured for this +Don't make changes to other wizard pages as they have been pre-configured for this job. ::: ![Sensitive Data Scan Settings](/images/accessanalyzer/11.6/solutions/databases/mysql/collection/sensitivedatscan_optionspage.webp) -**Step 4 –** To modify sensitive data scan options, select the desired scan options. See the +**Step 4 –** To modify sensitive data scan options, select the scan options you want. See the [SQL: Options](/docs/accessanalyzer/11.6/admin/datacollector/sql/options.md) page for additional information. @@ -84,7 +84,7 @@ objects. Click Retrieve. The Available database objects box will populate. The d scan all MySQL Databases returned, excluding the listed system schemas and tables in red. Databases and instances can be added in the following ways: -- Select the desired database objects and click Add. +- Select the database objects you want and click Add. - Use the Import CSV button to import a list from a CSV file, if desired. - Use the Add Custom Filter button to create and apply a custom filter. @@ -99,7 +99,7 @@ Navigate to the **Databases** > **0.Collection** > **MySQL** > **MySQL_Sensitive **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/mysql/collection/mysql_tableprivileges.md b/docs/accessanalyzer/11.6/solutions/databases/mysql/collection/mysql_tableprivileges.md index 578d06883e..e4f69cac31 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/mysql/collection/mysql_tableprivileges.md +++ b/docs/accessanalyzer/11.6/solutions/databases/mysql/collection/mysql_tableprivileges.md @@ -14,7 +14,7 @@ servers. The MySQL_TablePrivileges Job uses the SQL Data Collector for queries. :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -30,7 +30,7 @@ Navigate to the **Databases** > **0.Collection** > **MySQL** > **MySQL_TablePriv **Configure** node and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/mysql/mysql_databasesizing.md b/docs/accessanalyzer/11.6/solutions/databases/mysql/mysql_databasesizing.md index 3b2a68d119..2bcb36ee5f 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/mysql/mysql_databasesizing.md +++ b/docs/accessanalyzer/11.6/solutions/databases/mysql/mysql_databasesizing.md @@ -20,7 +20,7 @@ Navigate to the **Jobs > Databases > MySQL > Configuration > MySQL_DatabaseSi and select Analysis to view the Analysis Tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/mysql/overview.md b/docs/accessanalyzer/11.6/solutions/databases/mysql/overview.md index 656291266c..b5b7fd623a 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/mysql/overview.md +++ b/docs/accessanalyzer/11.6/solutions/databases/mysql/overview.md @@ -6,8 +6,8 @@ sidebar_position: 30 # MySQL Solution -Data privacy and security is quickly evolving to be on equal footing with traditional security -measures focused on the network, hardware, or software the data is contained within. Organizations +Data privacy and security is quickly becoming as important as traditional security +measures focused on the network, hardware, or software that stores the data. Organizations aligning to concepts like Data-Centric Audit and Protection (DCAP) as defined by Gartner, or the requirements of strict compliance regulations like EU GDPR, are looking to implement processes that help them understand where sensitive data is stored, who or what is leveraging their privileges to @@ -15,19 +15,19 @@ access the data, and how each database has been configured. As part of Stealthbits comprehensive Data Access Governance suite for structured and unstructured data, Enterprise Auditor for MySQL automates the process of understanding where MySQL databases -exist and provides an overview of the MySQL environment in order to answer questions around data +exist and provides an overview of the MySQL environment to answer questions around data access: - Who has access to your data? - Where is sensitive data being stored? -With visibility into every corner of MySQL, organizations can proactively highlight and prioritize +With visibility into every part of the MySQL environment, organizations can proactively highlight and prioritize risks to sensitive data. Additionally, organizations can automate manual, time-consuming, and -expensive processes associated with compliance, security, and operations to easily adhere to best +expensive processes associated with compliance, security, and operations to adhere to best practices that keep MySQL Server safe and operational. The MySQL Solution requires a special Enterprise Auditor license. The Database Solution license -includes all supported database platforms supported by Enterprise Auditor. Additionally, the +includes all database platforms that Enterprise Auditor supports. Additionally, the Sensitive Data Discovery Add-On enables the solution to search database content for sensitive data. By default, the job is configured to use 10 threads, which can be adjusted based on available @@ -57,7 +57,7 @@ an extra 16 GB of RAM are required (8x2=16). :::note The Sensitive Data Discovery Add-on installation package installs the appropriate JDK -(Java) version on the server. The JDK deployed is prepackaged and does not require any +(Java) version on the server. The JDK deployed is prepackaged and doesn't require any configuration; it has been preconfigured to work with Enterprise Auditor and should never be customized through Java. It will not conflict with other JDKs or Java Runtimes in the same environment. @@ -67,15 +67,15 @@ environment. **Location** The Structured Sensitive Data Discovery License is required to run the MySQL Solution. It can be -installed from the Enterprise Auditor Instant Job Wizard. Once it has been installed into the Jobs +installed from the Enterprise Auditor Instant Job Wizard. After it has been installed into the Jobs tree, navigate to the solution: Jobs > **Databases** > MySQL. The 0.Collection Job Group discovers configuration settings and Sensitive Data in MySQL Instances on the target hosts. The other job groups analyze and report on the data collected by the 0.Collection Job Group. -The Database Solution license includes all supported database platforms supported by Enterprise -Auditor. Additionally, the Sensitive Data Discovery Add-On enables the solution to search database +The Database Solution license includes all database platforms that Enterprise +Auditor supports. Additionally, the Sensitive Data Discovery Add-On enables the solution to search database content for sensitive data. ## Job Groups diff --git a/docs/accessanalyzer/11.6/solutions/databases/mysql/recommended.md b/docs/accessanalyzer/11.6/solutions/databases/mysql/recommended.md index 0db5d8d93b..b851dc9956 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/mysql/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/databases/mysql/recommended.md @@ -8,8 +8,8 @@ sidebar_position: 10 The MySQL Solution has been configured to inherit down from the MySQL > Settings node. However, it is best practice to assign the host list and the Connection Profile at the data collection level, -0.Collection Job Group. Once these are assigned to the job group, it can be run directly or -scheduled. +0.Collection Job Group. After you assign these to the job group, you can run it directly or +schedule it. **Dependencies** @@ -17,9 +17,9 @@ scheduled. Enterprise Auditor Console server - For AWS RDS and Aurora instances, right-click a job in the **MySQL** > **0.Collection** folder and open the properties window. Select the **Performance** tab and ensure that the **Skip Hosts that - do not respond to PING**checkbox is not selected. + don't respond to PING**checkbox isn't selected. -**Targeted Host(s)** +**Targeted Hosts** - The 0.Collection Job Group must be set to run against a custom host list containing the MySQL database instances / clusters. @@ -36,7 +36,7 @@ topic for additional information on permissions and creating a SQL custom connec The Connection Profile is set to Use the Default Profile, as configured at the global settings level. However, since this may not be the Connection Profile with the necessary permissions for the assigned hosts, click the radio button for the Select one of the following user defined profiles -option and select the appropriate Connection Profile drop-down menu. +option and select the appropriate Connection Profile dropdown menu. **Schedule Frequency** @@ -61,12 +61,12 @@ topic for additional information. **Analysis Configuration** This solution should be run with the default analysis configurations. These analysis tasks are -preconfigured and should not be modified or deselected. +preconfigured and shouldn't be modified or deselected. Disabling obsolete or run-desired jobs allows the solution to run more efficiently. To disable a job -or job group, right-click on the item and select Disable Job. +or job group, right-click the item and select Disable Job. :::info -Do not delete any jobs. Instead, jobs should be disabled. +Don't delete any jobs. Disable them instead. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/mysql/sensitivedata/mysql_sensitivedata.md b/docs/accessanalyzer/11.6/solutions/databases/mysql/sensitivedata/mysql_sensitivedata.md index ec1df04cc5..d4cd8c9990 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/mysql/sensitivedata/mysql_sensitivedata.md +++ b/docs/accessanalyzer/11.6/solutions/databases/mysql/sensitivedata/mysql_sensitivedata.md @@ -15,7 +15,7 @@ Navigate to the **Jobs > MySQL > Sensitive Data > MySQL_SensitiveData > Conf Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/mysql/sensitivedata/mysql_sensitivedatapermissions.md b/docs/accessanalyzer/11.6/solutions/databases/mysql/sensitivedata/mysql_sensitivedatapermissions.md index 58c9c94e52..e7e7006fd7 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/mysql/sensitivedata/mysql_sensitivedatapermissions.md +++ b/docs/accessanalyzer/11.6/solutions/databases/mysql/sensitivedata/mysql_sensitivedatapermissions.md @@ -16,7 +16,7 @@ Navigate to the **Jobs > MySQL > Sensitive Data > MySQL_SensitiveDataPermissi and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_activity.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_activity.md index c8207faaf6..db51f65a41 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_activity.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_activity.md @@ -15,7 +15,7 @@ Navigate to the **Oracle** > **2.Activity** > **Oracle_Activity** > **Configure* **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_logons.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_logons.md index c2404162b8..05962e91aa 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_logons.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_logons.md @@ -15,7 +15,7 @@ Navigate to the **Oracle** > **2.Activity** > **Oracle_Logons** > **Configure** **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_permissionchanges.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_permissionchanges.md index 8f89ccb815..675ff2ce9b 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_permissionchanges.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_permissionchanges.md @@ -16,7 +16,7 @@ Navigate to the **Oracle** > **2.Activity** > **Oracle_PermissionChanges** > **C select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_schemachanges.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_schemachanges.md index 8fb56c421e..1ccbf615bb 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_schemachanges.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_schemachanges.md @@ -15,7 +15,7 @@ Navigate to the **Oracle** > **2.Activity** > **Oracle_SchemaChanges** > **Confi select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_sensitivedataactivity.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_sensitivedataactivity.md index 1010e06d3b..f0b976eedf 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_sensitivedataactivity.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_sensitivedataactivity.md @@ -15,7 +15,7 @@ Navigate to the **Oracle** > **2.Activity** > **Oracle_SensitiveDataActivity** > and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_suspiciousactivity.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_suspiciousactivity.md index aae76fc305..8b06367f0a 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_suspiciousactivity.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_suspiciousactivity.md @@ -7,7 +7,7 @@ sidebar_position: 60 # Oracle_SuspiciousActivity Job The Oracle_SuspiciousActivity job is designed to provide insight into suspicious behavior based on -user activity that does not conform to normal database activity. +user activity that doesn't conform to normal database activity. ## Analysis Tasks for the Oracle_SuspiciousActivity Job @@ -15,7 +15,7 @@ Navigate to the **Oracle** > **2.Activity** > **Oracle_SuspiciousActivity** > ** select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_unusualactivity.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_unusualactivity.md index 042b171e5c..e407dfcdbb 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_unusualactivity.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_unusualactivity.md @@ -16,7 +16,7 @@ Navigate to the **Oracle** > **2.Activity** > **Oracle_UnusualActivity** > **Con select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/overview.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/overview.md index 171be621f5..49d22fc269 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/overview.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/overview.md @@ -33,7 +33,7 @@ The jobs in the 2.Activity Job Group are: TRUNCATE) against objects containing sensitive data - [Oracle_SuspiciousActivity Job](/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_suspiciousactivity.md) – This job is designed to provide insight into suspicious behavior based on user activity that - does not conform to normal database activity + doesn't conform to normal database activity - [Oracle_UnusualActivity Job](/docs/accessanalyzer/11.6/solutions/databases/oracle/activity/oracle_unusualactivity.md) – This job is designed to analyze user activity based on the audited actions and identify any outliers based on a modified z-score. Modified z-scores of 3.5 or higher are considered to be diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/collection/0-oracle_servers.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/collection/0-oracle_servers.md index 5d79970168..32c47305d0 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/collection/0-oracle_servers.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/collection/0-oracle_servers.md @@ -14,7 +14,7 @@ running on the targeted servers. The Server Discovery query uses the PowerShell Data Collector for the following query: :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -22,7 +22,7 @@ Do not modify the query. The query is preconfigured for this job. - Oracle Servers – Returns a list of Oracle servers from the specified host list -Regarding Oracle instance discovery, there may be errors running the query that are not reported. An +Errors running the query during Oracle instance discovery might not be reported. An additional log to store the issues has been added for instance discoveries named `Oracle_Server_log_[target_hostname]`. This file can be found in `%sainstalldir%\Jobs\GROUP_ORACLE_0.Collection\GROUP_1.Discovery\JOB_Oracle_Servers\OUTPUT`. See the @@ -35,7 +35,7 @@ Navigate to the **Databases** > **0.Collection** > **Oracle** > **0-Oracle_Serve node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/collection/1-oracle_permissionsscan.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/collection/1-oracle_permissionsscan.md index 2b9e53dcf1..3af54a77bd 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/collection/1-oracle_permissionsscan.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/collection/1-oracle_permissionsscan.md @@ -20,19 +20,19 @@ The PermissionsScan query uses the SQL Data Collector for the following query: ### Configure the 1-Oracle_PermissionsScan Query The 1-Oracle_PermissionsScan Job is preconfigured to run using the default settings for the -Permissions Collection category in the SQL Data Collector. Follow the steps to customize +Permissions Collection category in the SQL Data Collector. To customize configurations: **Step 1 –** Navigate to the **Databases** > **0.Collection** > **Oracle** > **1-Oracle_PermissionsScan** > **Configure** node and select Queries. -**Step 2 –** In the Query Selection view, select the PermissionScan query and click on Query +**Step 2 –** In the Query Selection view, select the PermissionScan query and click Query Properties. The Query Properties window opens. **Step 3 –** Select the Data Source tab and click Configure. The SQL Data Collector wizard opens. :::warning -Do not make changes to wizard pages not listed in these steps. They have been +Don't make changes to wizard pages not listed in these steps. They have been pre-configured for this job. ::: @@ -44,7 +44,7 @@ query target is All Databases. The default query scope is Only select database o Retrieve. The Available database objects section will be populated. Databases and instances can be added in the following ways: -- Select the desired database objects and click Add +- Select the database objects you want and click Add - Use the Import CSV button to import a list from a CSV file, if desired - Optionally, use the Add Custom Filter button to create and apply a custom filter @@ -59,7 +59,7 @@ Navigate to the **Databases** > **0.Collection** > **Oracle** > **1-Oracle_Permi **Configure** node and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/collection/2-oracle_sensitivedatascan.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/collection/2-oracle_sensitivedatascan.md index bcdb36f682..fbf0d99301 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/collection/2-oracle_sensitivedatascan.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/collection/2-oracle_sensitivedatascan.md @@ -36,19 +36,19 @@ The SensitiveDataScan Query uses the SQL Data Collector for the following query: ### Configure the 2-Oracle_SensitiveDataScan Query The 2-Oracle_SensitiveDataScan Job is preconfigured to run using the default settings for the -Sensitive Data Collection category in the SQL Data Collector. Follow the steps to customize +Sensitive Data Collection category in the SQL Data Collector. To customize configurations: **Step 1 –** Navigate to the **Databases > 0.Collection >** Oracle > > 2-Oracle_SensitiveDataScan > Configure node and select Queries. -**Step 2 –** In the Query Selection view, select the SensitiveDataScan query and click on Query +**Step 2 –** In the Query Selection view, select the SensitiveDataScan query and click Query Properties. The Query Properties window opens. **Step 3 –** Select the Data Source tab and click Configure. The SQL Data Collector wizard opens. :::warning -Do not make changes to wizard pages not listed in these steps. They have been +Don't make changes to wizard pages not listed in these steps. They have been pre-configured for this job. ::: @@ -70,7 +70,7 @@ query target is All Databases. The default query scope is Only select database o Retrieve. The Available database objects section will be populated. Databases and instances can be added in the following ways: -- Select the desired database objects and click Add +- Select the database objects you want and click Add - Use the Import CSV button to import a list from a CSV file, if desired - Optionally, use the Add Custom Filter button to create and apply a custom filter @@ -85,7 +85,7 @@ Navigate to the **Databases** > **0.Collection** > **Oracle** > **2-Oracle_Sensi **Configure** node and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/collection/3-oracle_activityscan.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/collection/3-oracle_activityscan.md index 4ec990442c..baae8f05be 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/collection/3-oracle_activityscan.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/collection/3-oracle_activityscan.md @@ -27,19 +27,19 @@ The ActivityScan Query uses the SQL Data Collector for the following query: ### Configure the 3-Oracle_ActivityScan Query The 3-Oracle_ActivityScan Job is preconfigured to run using the default settings for the Server -Audit Events Collection category in the SQL Data Collector. Follow the steps to customize +Audit Events Collection category in the SQL Data Collector. To customize configurations: **Step 1 –** Navigate to the **Databases** > **0.Collection** > **Oracle** > **3-Oracle_ActivityScan** > **Configure** node and select Queries. -**Step 2 –** In the Query Selection view, select the ActivityScan query and click on Query +**Step 2 –** In the Query Selection view, select the ActivityScan query and click Query Properties. The Query Properties window opens. **Step 3 –** Select the Data Source tab and click Configure. The SQL Data Collector wizard opens. :::warning -Do not make changes to wizard pages not listed in these steps. They have been +Don't make changes to wizard pages not listed in these steps. They have been pre-configured for this job. ::: @@ -56,7 +56,7 @@ query target is All Databases. The default query scope is Only select database o Retrieve. The Available database objects section will be populated. Databases and instances can be added in the following ways: -- Select the desired database objects and click Add +- Select the database objects you want and click Add - Use the Import CSV button to import a list from a CSV file, if desired - Optionally, use the Add Custom Filter button to create and apply a custom filter @@ -71,7 +71,7 @@ Navigate to the **Databases** > **0.Collection** > **Oracle** > **3-Oracle_Activ **Configure** node and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/collection/4-oracle_defaultpasswordusers.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/collection/4-oracle_defaultpasswordusers.md index 191bdf71bc..c85fb09489 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/collection/4-oracle_defaultpasswordusers.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/collection/4-oracle_defaultpasswordusers.md @@ -21,19 +21,19 @@ The 4-Oracle_DefaultPasswordUsers Job uses the SQL Data Collector for the follow ### Configure the 4-Oracle_DefaultPasswordUsers Query The 4-Oracle_DefaultPasswordUsers Job is preconfigured to run using the default settings for the -Permissions Collection category in the SQL Data Collector. Follow the steps to customize +Permissions Collection category in the SQL Data Collector. To customize configurations: **Step 1 –** Navigate to the **Databases** > **0.Collection** > **Oracle** > **4-Oracle_DefaultPasswordUsers** > **Configure** node and select Queries. -**Step 2 –** In the Query Selection view, select the Users with Default Passwords query and click on +**Step 2 –** In the Query Selection view, select the Users with Default Passwords query and click Query Properties. The Query Properties window opens. **Step 3 –** Select the Data Source tab and click Configure. The SQL Data Collector wizard opens. :::warning -Do not make changes to wizard pages not listed in these steps. They have been +Don't make changes to wizard pages not listed in these steps. They have been pre-configured for this job. ::: @@ -45,7 +45,7 @@ query target is All Databases. The default query scope is Only select database o Retrieve. The Available database objects section will be populated. Databases and instances can be added in the following ways: -- Select the desired database objects and click Add +- Select the database objects you want and click Add - Use the Import CSV button to import a list from a CSV file, if desired - Optionally, use the Add Custom Filter button to create and apply a custom filter diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/collection/5-oracle_configuration.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/collection/5-oracle_configuration.md index 44368c2f0e..18860f699e 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/collection/5-oracle_configuration.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/collection/5-oracle_configuration.md @@ -23,18 +23,18 @@ The queries are: ### Configure the 5-Oracle_Configuration Queries The 5-Oracle_Configuration Job is preconfigured to run using the default settings for the Custom -Oracle Query category in the SQL Data Collector. Follow the steps to customize configurations: +Oracle Query category in the SQL Data Collector. To customize configurations: **Step 1 –** Navigate to the **Databases** > **0.Collection** > **Oracle** > **5-Oracle_Configuration Job** > **Configure** node and select Queries. -**Step 2 –** In the Query Selection view, select one of the queries and click on Query Properties. +**Step 2 –** In the Query Selection view, select one of the queries and click Query Properties. The Query Properties window opens. **Step 3 –** Select the Data Source tab and click Configure. The SQL Data Collector wizard opens. :::warning -Do not make changes to wizard pages not listed in these steps. They have been +Don't make changes to wizard pages not listed in these steps. They have been pre-configured for this job. ::: @@ -46,7 +46,7 @@ query target is All Databases. The default query scope is Only select database o Retrieve. The Available database objects section will be populated. Databases and instances can be added in the following ways: -- Select the desired database objects and click Add +- Select the database objects you want and click Add - Use the Import CSV button to import a list from a CSV file, if desired - Optionally, use the Add Custom Filter button to create and apply a custom filter diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/oracle_databaselinks.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/oracle_databaselinks.md index 9e3173b825..298f7ba5a1 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/oracle_databaselinks.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/oracle_databaselinks.md @@ -7,7 +7,7 @@ sidebar_position: 10 # Oracle_DatabaseLinks Job The Oracle_DatabaseLinks Job contains a report that provides information on Database Links where the -listed Oracle Server is able to execute remote commands. +listed Oracle Server can execute remote commands. ## Analysis Tasks for the Oracle_DatabaseLinks Job @@ -15,7 +15,7 @@ Navigate to the **Jobs >  Databases > Oracle > 4.Configuration > Oracle_Databas Job >Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -32,4 +32,4 @@ the following preconfigured report: | Report | Description | Default Tags | Report Elements | | -------------- | -------------------------------------------------------------------------------------------------------- | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Database Links | This report highlights Database Links where the listed Oracle Server is able to execute remote commands. | None | This report is comprised of three elements:
  • Bar Chart – Provides information on top five database links by instance
  • Bar Chart – Provides information on database links by instance (GB)
  • Table – Provides details on database links
| +| Database Links | This report highlights Database Links where the listed Oracle Server can execute remote commands. | None | This report is comprised of three elements:
  • Bar Chart – Provides information on top five database links by instance
  • Bar Chart – Provides information on database links by instance (GB)
  • Table – Provides details on database links
| diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/oracle_databasesizing.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/oracle_databasesizing.md index a3c4df6307..8765d526d1 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/oracle_databasesizing.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/oracle_databasesizing.md @@ -15,7 +15,7 @@ Navigate to the **Jobs >  Databases > Oracle > 4.Configuration > Oracle_Databas Job >Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/oracle_datadictionaryprotection.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/oracle_datadictionaryprotection.md index 9790c78d38..de03f42eea 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/oracle_datadictionaryprotection.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/oracle_datadictionaryprotection.md @@ -17,7 +17,7 @@ Navigate to the **Jobs >  Databases > Oracle > 4.Configuration > Oracle_DataDic Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/oracle_instancenameissues.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/oracle_instancenameissues.md index 630506ba27..62d9a8a5ef 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/oracle_instancenameissues.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/oracle_instancenameissues.md @@ -8,7 +8,7 @@ sidebar_position: 40 The Oracle_InstanceNameIssues Job discovers if names used for Oracle database instances conform to Oracle recommended best practices. The job also checks to see if Oracle SIDs conform to DISA STIG -V-61413 – Oracle instance name or SID should not contain Oracle version numbers. +V-61413 – Oracle instance name or SID shouldn't contain Oracle version numbers. ## Analysis Tasks for the Oracle_InstanceNameIssues Job @@ -16,7 +16,7 @@ Navigate to the **Jobs > Databases > Oracle > 4.Configuration > Oracle_InstanceN Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/oracle_remoteosauthentication.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/oracle_remoteosauthentication.md index f3426cd1c6..2db7c5f61b 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/oracle_remoteosauthentication.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/oracle_remoteosauthentication.md @@ -15,7 +15,7 @@ Navigate to the **Jobs > Databases > Oracle > 4.Configuration > Oracle_RemoteOSA Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/overview.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/overview.md index ed5fb2e7cb..57290f0a97 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/overview.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/overview.md @@ -14,8 +14,8 @@ related to Oracle Database Instance configuration settings. The jobs in the 4.Configuration Job Group are: - [Oracle_DatabaseLinks Job](/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/oracle_databaselinks.md) - – Contains a report that provides information on Database Links where the listed Oracle Server is - able to execute remote commands + – Contains a report that provides information on Database Links where the listed Oracle Server + can execute remote commands - [Oracle_DatabaseSizing Job](/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/oracle_databasesizing.md) – Provides details on tablespace file sizes and overall tablespace sizes - [Oracle_DataDictionaryProtection Job](/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/oracle_datadictionaryprotection.md) @@ -25,7 +25,7 @@ The jobs in the 4.Configuration Job Group are: - [Oracle_InstanceNameIssues Job](/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/oracle_instancenameissues.md) – This job is designed to find out if the names used for the Oracle database instances conform to Oracle recommended best practices. The job also checks to see if the Oracle SID conforms to DISA - STIG V-61413 – Oracle instance name or SID should not contain Oracle version numbers. + STIG V-61413 – Oracle instance name or SID shouldn't contain Oracle version numbers. - [Oracle_RemoteOSAuthentication Job](/docs/accessanalyzer/11.6/solutions/databases/oracle/configuration/oracle_remoteosauthentication.md) – This job is designed to find out if remote OS authentication is enabled for the targeted Oracle database servers diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/overview.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/overview.md index 16d59208ba..b8070f5f6a 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/overview.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/overview.md @@ -6,8 +6,8 @@ sidebar_position: 40 # Oracle Solution -Data privacy and security is quickly evolving to be on equal footing with traditional security -measures focused on the network, hardware, or software the data is contained within. Organizations +Data privacy and security is becoming as important as traditional security measures that focus on +the network, hardware, or software where the data resides. Organizations aligning to concepts like Data-Centric Audit and Protection (DCAP) as defined by Gartner, or the requirements of strict compliance regulations like EU GDPR, are looking to implement processes that help them understand where sensitive data is stored, who or what is leveraging their privileges to @@ -15,7 +15,7 @@ access the data, and how each database has been configured. This solution is a comprehensive part of the Data Access Governance suite for structured and unstructured data. Enterprise Auditor for Oracle automates the process of understanding where Oracle -databases exist and provides an overview of the Oracle environment in order to answer questions +databases exist and provides an overview of the Oracle environment to answer questions around data access: - Who HAS access to your data? @@ -25,11 +25,11 @@ around data access: With visibility into every corner of Oracle® server and the Windows® operating system it relies upon, organizations can proactively highlight and prioritize risks to sensitive data. Additionally, organizations can automate manual, time-consuming, and expensive processes associated with -compliance, security, and operations to easily adhere to best practices that keep Oracle Server safe +compliance, security, and operations to adhere to best practices that keep Oracle Server safe and operational. The Oracle Solution requires a special Enterprise Auditor license. The Database Solution license -includes all supported database platforms supported by Enterprise Auditor. Additionally, the +includes all database platforms supported by Enterprise Auditor. Additionally, the Sensitive Data Discovery Add-On enables the solution to search database content for sensitive data. **Supported Platforms** @@ -46,15 +46,15 @@ topic for additional information. **Sensitive Data Discovery Considerations** -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the minimum amount +If you run Sensitive Data Discovery (SDD) scans, increase the minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host.For example, if the job is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are required (8x2=16). :::note The Sensitive Data Discovery Add-on installation package installs the appropriate JDK -(Java) version on the server. The JDK deployed is prepackaged and does not require any -configuration; it has been preconfigured to work with Enterprise Auditor and should never be -customized through Java. It will not conflict with other JDKs or Java Runtimes in the same +(Java) version on the server. The JDK deployed is prepackaged and doesn't require any +configuration; it has been preconfigured to work with Enterprise Auditor. Never customize it through +Java. It will not conflict with other JDKs or Java Runtimes in the same environment. ::: @@ -62,7 +62,7 @@ environment. **Location** The Oracle Solution requires a special Enterprise Auditor license. It can be installed from the -Enterprise Auditor Instant Job Wizard. Once it has been installed into the Jobs tree, navigate to +Enterprise Auditor Instant Job Wizard. After it has been installed into the Jobs tree, navigate to the solution: **Jobs** > **Databases** > **0.Collection** > **Oracle** for the 0.Collection job group for Oracle. @@ -70,7 +70,7 @@ The 0.Collection Job Group discovers Oracle Instances on the target hosts. The o **Jobs** > **Databases** > **Oracle** analyze and report on the data collected by the 0.Collection Job Group. -The Database Solution license includes all supported database platforms supported by Enterprise +The Database Solution license includes all database platforms supported by Enterprise Auditor. Additionally, the Sensitive Data Discovery Add-On enables the solution to search database content for sensitive data. diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/permissions/oracle_domainuserpermissions.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/permissions/oracle_domainuserpermissions.md index e280617f9d..cae79442bc 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/permissions/oracle_domainuserpermissions.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/permissions/oracle_domainuserpermissions.md @@ -15,7 +15,7 @@ Navigate to the **Oracle** > **3.Permissions** > **Oracle_DomainUserPermissions* node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/permissions/oracle_objectpermissions.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/permissions/oracle_objectpermissions.md index 6a6545bfd5..7306a140ed 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/permissions/oracle_objectpermissions.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/permissions/oracle_objectpermissions.md @@ -15,7 +15,7 @@ Navigate to the **Oracle** > **3.Permissions** > **Oracle_ObjectPermissions** > and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/permissions/oracle_publicpermissions.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/permissions/oracle_publicpermissions.md index 11bb53c4fa..d84ad993b1 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/permissions/oracle_publicpermissions.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/permissions/oracle_publicpermissions.md @@ -15,7 +15,7 @@ Navigate to the **Oracle** > **3.Permissions** > **Oracle_PublicPermissions** > and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/permissions/oracle_serverpermissions.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/permissions/oracle_serverpermissions.md index 316ed05de0..cbbadb2fd3 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/permissions/oracle_serverpermissions.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/permissions/oracle_serverpermissions.md @@ -15,7 +15,7 @@ Navigate to the **Oracle** > **3.Permissions** > **Oracle_ServerPermissions** > and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/permissions/oracle_sysschemapermissions.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/permissions/oracle_sysschemapermissions.md index f6225102f9..7a90ec58ec 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/permissions/oracle_sysschemapermissions.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/permissions/oracle_sysschemapermissions.md @@ -15,7 +15,7 @@ Navigate to the **Oracle** > **3.Permissions** > **Oracle_SysSchemaPermissions** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/recommended.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/recommended.md index 5a2f716055..0e0a3cc549 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/recommended.md @@ -8,8 +8,8 @@ sidebar_position: 10 The Oracle Solution has been configured to inherit down from the Oracle > Settings node. However, it is best practice to assign the host list and the Connection Profile at the data collection level, -0.Collection Job Group. Once these are assigned to the job group, it can be run directly or -scheduled. +0.Collection Job Group. After you assign the host list and Connection Profile to the job group, you +can run it directly or schedule it. **Dependencies** @@ -20,19 +20,18 @@ scheduled. Enterprise Auditor Console server Some of the queries in the **Jobs** > **Databases** > **0.Collection** > **Oracle Job Group** can be -scoped to target specific databases and/or instances. However, it is necessary for the -SA_SQL_Instances table to be populated before attempting to scope the queries. Therefore, the -0-Oracle_Servers job must be executed before attempting to scope the rest of the 0.Collection Job -Group queries. +scoped to target specific databases and/or instances. However, the SA_SQL_Instances table must be +populated before you scope the queries. Therefore, you must run the 0-Oracle_Servers job before +scoping the rest of the 0.Collection Job Group queries. -**Targeted Host(s)** +**Targeted Hosts** The 0.Collection Job Group must be set to run against the following dynamic host list: - Oracle Servers Default dynamic host lists are populated from hosts in the Host Master Table which meet the host -inventory criteria for the list. Ensure the appropriate host list(s) have been populated through +inventory criteria for the list. Ensure the appropriate host lists have been populated through host inventory results. **Connection Profile** @@ -40,11 +39,11 @@ host inventory results. The SQL Data Collector requires a specific set of permissions. The account used can be either an Active Directory account or an Oracle account. -For a Windows-integrated Oracle instance it is possible to use one Active Directory credential that +For a Windows-integrated Oracle instance, you can use one Active Directory credential that has permissions on both the Oracle database and the server. This will not generally be the case in most customer environments, but it is possible. -If the required permissions are assigned to one Active Directory credential, once the account has +If the required permissions are assigned to one Active Directory credential, after the account has been provisioned, create a custom Connection Profile containing the credentials for the targeted environment. See the [SQL Data Collector](/docs/accessanalyzer/11.6/admin/datacollector/sql/overview.md) @@ -66,10 +65,10 @@ node as follows: - 4-Oracle_DefaultPasswordUsers Job - 5-Oracle_Configuration Job -The Connection Profile is set to Use the Default Profile, as configured at the global settings -level. However, since this may not be the Connection Profile with the necessary permissions for the -assigned hosts, click the radio button for the Select one of the following user defined profiles -option and select the appropriate Connection Profile drop-down menu. +The Connection Profile defaults to the profile configured at the global settings level. If that +profile doesn't have the permissions the assigned hosts need, select the radio button for the Select +one of the following user defined profiles option, then choose the correct profile from the +Connection Profile dropdown menu. See the [Connection](/docs/accessanalyzer/11.6/admin/settings/connection/overview.md) @@ -84,7 +83,7 @@ daily. **Run Order** -The 0-Oracle_Servers Job within the Oracle 0.Collection Job Group must be run first, before running +Run the 0-Oracle_Servers Job within the Oracle 0.Collection Job Group first, before running the rest of the jobs. :::info @@ -107,9 +106,9 @@ SQL Data Collector configurations can be modified if desired: - 2-Oracle_SensitiveDataScan Job - Filter page – Scope the query to target specific databases/instances in the following jobs: - Remember, it is necessary for the + Remember, the [0-Oracle_Servers Job](/docs/accessanalyzer/11.6/solutions/databases/oracle/collection/0-oracle_servers.md) - to run at least once before attempting to scope any of the following queries: + must run at least once before you scope any of the following queries: - 1-Oracle_PermissionsScan Job - 2-Oracle_SensitiveDataScan Job @@ -126,13 +125,13 @@ SQL Data Collector configurations can be modified if desired: **Analysis Configuration** This solution should be run with the default analysis configurations. These analysis tasks are -preconfigured and should not be modified or deselected! +preconfigured and shouldn't be modified or deselected. Remember, disabling obsolete or un-desired jobs allows the solution to run more efficiently. To -disable a job or job group, right-click on the item and select Disable Job. +disable a job or job group, right-click the item and select Disable Job. :::info -Do not delete any jobs. Instead, jobs should be disabled. +Don't delete any jobs. Disable them instead. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/sensitivedata/oracle_sensitivedata.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/sensitivedata/oracle_sensitivedata.md index dc312139f7..6773f7a616 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/sensitivedata/oracle_sensitivedata.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/sensitivedata/oracle_sensitivedata.md @@ -15,7 +15,7 @@ Navigate to the **Oracle > 5.Sensitve Data > Oracle_SensitveData > Configure** n **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/sensitivedata/oracle_sensitivedatapermissions.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/sensitivedata/oracle_sensitivedatapermissions.md index 8bc06f0e70..b89fdaadee 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/sensitivedata/oracle_sensitivedatapermissions.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/sensitivedata/oracle_sensitivedatapermissions.md @@ -15,7 +15,7 @@ Navigate to the **Oracle > 5.Sensitive Data > Oracle_SensitiveDataPermissions > select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/usersroles/oracle_passwordissues.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/usersroles/oracle_passwordissues.md index b80c2a0f75..12c62388d7 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/usersroles/oracle_passwordissues.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/usersroles/oracle_passwordissues.md @@ -15,7 +15,7 @@ passwords. The Oracle_PasswordIssues Job uses the PowerShell Data Collector for the following query: :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -34,7 +34,7 @@ Navigate to the **Jobs** > **Oracle** > **1.Users and Roles** > **Oracle_Passwor **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/usersroles/oracle_rolemembers.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/usersroles/oracle_rolemembers.md index 9d28525729..3b9c4c794e 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/usersroles/oracle_rolemembers.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/usersroles/oracle_rolemembers.md @@ -15,7 +15,7 @@ Navigate to the **Oracle** > **1.Users and Roles** > **Oracle_RoleMembers** > Co select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/usersroles/oracle_systemadministrators.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/usersroles/oracle_systemadministrators.md index a8a6450f51..30d8ede62d 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/usersroles/oracle_systemadministrators.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/usersroles/oracle_systemadministrators.md @@ -15,7 +15,7 @@ Navigate to the **Oracle** > **1.Users and Roles** > **Oracle_SystemAdministrato node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/oracle/usersroles/oracle_users.md b/docs/accessanalyzer/11.6/solutions/databases/oracle/usersroles/oracle_users.md index 405d8d476c..e26ad4d1ff 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/oracle/usersroles/oracle_users.md +++ b/docs/accessanalyzer/11.6/solutions/databases/oracle/usersroles/oracle_users.md @@ -15,7 +15,7 @@ Navigate to the **Oracle** > **1.Users and Roles** > **Oracle_Users** > **Config select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/overview.md b/docs/accessanalyzer/11.6/solutions/databases/overview.md index 90e49df74c..fe9b3023ff 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/overview.md +++ b/docs/accessanalyzer/11.6/solutions/databases/overview.md @@ -15,18 +15,18 @@ reports that provide visibility into various aspects of supported databases: and Sensitive Data. - [MongoDB Solution](/docs/accessanalyzer/11.6/solutions/databases/mongodb/overview.md) – Enterprise Auditorfor MongoDB automates the process of understanding where MongoDB databases - exist and provides an overview of the MongoDB environment in order to answer questions around data + exist and provides an overview of the MongoDB environment to answer questions around data access. - [MySQL Solution](/docs/accessanalyzer/11.6/solutions/databases/mysql/overview.md) – Enterprise Auditor for MySQL automates the process of understanding where MySQL databases exist - and provides an overview of the MySQL environment in order to answer questions around data access. + and provides an overview of the MySQL environment to answer questions around data access. - [Oracle Solution](/docs/accessanalyzer/11.6/solutions/databases/oracle/overview.md) – Enterprise Auditor for Oracle automates the process of understanding where Oracle databases - exist and provides an overview of the Oracle environment in order to answer questions around data + exist and provides an overview of the Oracle environment to answer questions around data access. - [PostgreSQL Solution](/docs/accessanalyzer/11.6/solutions/databases/postgresql/overview.md) – Enterprise Auditor for PostgreSQL automates the process of understanding where - PostgreSQL databases exist and provides an overview of the PostgreSQL environment in order to + PostgreSQL databases exist and provides an overview of the PostgreSQL environment to answer questions around data access. - [Redshift Solution](/docs/accessanalyzer/11.6/solutions/databases/redshift/overview.md) – Redshift Solution Set is a comprehensive set of pre-configured audit jobs and reports that @@ -37,7 +37,7 @@ reports that provide visibility into various aspects of supported databases: information on users and roles, activity, permissions, configuration, sensitive data, and overall security assessment for both the SQL 0.Collection Job Group and Azure SQL 0.Collection Job Group. -The Database Solution license includes all supported database platforms supported by Enterprise +The Database Solution license includes all database platforms supported by Enterprise Auditor. Additionally, the Sensitive Data Discovery Add-On enables the solution to search database content for sensitive data. @@ -53,7 +53,7 @@ The following table identifies the type of audit functionality for each supporte | PostgreSQL | | \*Partially Supported | | Fully Supported | \*\*Partially Supported | | Redshift | | \*Partially Supported | | Fully Supported | \*\*Partially Supported | -In the above table: +The following notes apply to the table: - \*Partially Supported, "Permission Audit" means the permissions as solely collected at the table level. diff --git a/docs/accessanalyzer/11.6/solutions/databases/postgresql/collection/pgsql_configuration.md b/docs/accessanalyzer/11.6/solutions/databases/postgresql/collection/pgsql_configuration.md index aeccb79e94..8a061586fc 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/postgresql/collection/pgsql_configuration.md +++ b/docs/accessanalyzer/11.6/solutions/databases/postgresql/collection/pgsql_configuration.md @@ -14,7 +14,7 @@ PostgreSQL servers. The PgSQL_Configuration Job uses the SQL Data Collector. :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/postgresql/collection/pgsql_sensitivedatascan.md b/docs/accessanalyzer/11.6/solutions/databases/postgresql/collection/pgsql_sensitivedatascan.md index 55b15a912f..0e39f2c910 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/postgresql/collection/pgsql_sensitivedatascan.md +++ b/docs/accessanalyzer/11.6/solutions/databases/postgresql/collection/pgsql_sensitivedatascan.md @@ -24,18 +24,18 @@ The query is: ### Configure the SensitiveDataScan Query The PgSQL_SensitiveDataScan Job is preconfigured to run using the default settings for the Sensitive -Data Collection category. Follow the steps to customize configurations. +Data Collection category. To customize configurations: **Step 1 –** Navigate to the **Databases** > **0.Collection** > **PostgreSQL** > **PgSQL_SensitiveDataScan** > **Configure** node and select Queries. -**Step 2 –** In the Query Selection view, select the **PostgreSQL** query click on Query Properties. +**Step 2 –** In the Query Selection view, select the **PostgreSQL** query click Query Properties. The Query Properties window appears. **Step 3 –** Select the Data Source tab, and click Configure. The SQL Data Collector Wizard opens. :::warning -Do not make changes to other wizard pages as they have been pre-configured for this +Don't make changes to other wizard pages as they have been pre-configured for this job. ::: @@ -44,7 +44,7 @@ job. **Step 4 –** To modify sensitive data scan options, navigate to the [SQL Data Collector](/docs/accessanalyzer/11.6/admin/datacollector/sql/overview.md) -page. Select the desired scan options. +page. Select the scan options that you want. :::note The Sensitive Data Scan Settings are pre-configured for optimal performance for a @@ -64,7 +64,7 @@ topic for additional information. ![Filters page](/images/accessanalyzer/11.6/solutions/databases/postgresql/collection/sensitivedatascanfilter.webp) -**Step 6 –** PostgreSQL databases must be added to the query before they can be scanned. Navigate to +**Step 6 –** Add PostgreSQL databases to the query before you scan them. Navigate to the **Filter** page and click **Connections** to open the Manage Connections window. ![Manage Connections](/images/accessanalyzer/11.6/solutions/databases/postgresql/collection/manageconnectionspgsql.webp) @@ -85,7 +85,7 @@ objects. Click Retrieve. The Available database objects box will populate. The d scan all PostgreSQL databases returned, excluding the listed system or default schemas and tables in red. Databases and instances can be added in the following ways: -- Select the desired database objects and click Add. +- Select the database objects you want and click Add. - Use the Import CSV button to import a list from a CSV file, if desired. - Use the Add Custom Filter button to create and apply a custom filter. @@ -100,7 +100,7 @@ Navigate to the **Databases** > **0.Collection** > **PostgreSQL** > **PgSQL_Sen **Configure** node and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -112,4 +112,4 @@ The default analysis tasks are: - Bring SA_SQL_Instances to View — Displays the SA_SQL_Instances table - PostgreSQL SDD Matches View — Bring the PostgreSQL SDD Matches View to the SA console - PostgreSQL SDD Match Hits View — Bring the PostgreSQL SDD Match Hits View to the SA console -- PostgreSQL SDD AIC Import — Imports PostgreSQL SDD into the AIC +- PostgreSQL SDD AIC Import — Imports PostgreSQL SDD into the Access Information Center (AIC) diff --git a/docs/accessanalyzer/11.6/solutions/databases/postgresql/collection/pgsql_tableprivileges.md b/docs/accessanalyzer/11.6/solutions/databases/postgresql/collection/pgsql_tableprivileges.md index 98ace0c5c9..5c2cfba0d2 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/postgresql/collection/pgsql_tableprivileges.md +++ b/docs/accessanalyzer/11.6/solutions/databases/postgresql/collection/pgsql_tableprivileges.md @@ -14,7 +14,7 @@ targeted servers. The PgSQL_TablePrivileges Job uses the SQL Data Collector for queries. :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -30,7 +30,7 @@ Navigate to the **Databases** > **0.Collection** > **PostgreSQL** > **PgSQL_Tabl **Configure** node and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: @@ -39,5 +39,6 @@ preconfigured for this job. The default analysis task is: -- AIC Import - PostgreSQL Permissions – Imports PostgreSQL permissions to the AIC. +- AIC Import - PostgreSQL Permissions – Imports PostgreSQL permissions to the Access Information + Center (AIC). - AIC Import - Databases – Imports PostgreSQL database and schema nodes to the AIC. diff --git a/docs/accessanalyzer/11.6/solutions/databases/postgresql/overview.md b/docs/accessanalyzer/11.6/solutions/databases/postgresql/overview.md index cc736a3f22..16629c085f 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/postgresql/overview.md +++ b/docs/accessanalyzer/11.6/solutions/databases/postgresql/overview.md @@ -6,8 +6,8 @@ sidebar_position: 50 # PostgreSQL Solution -Data privacy and security is quickly evolving to be on equal footing with traditional security -measures focused on the network, hardware, or software the data is contained within. Organizations +Data privacy and security is becoming as important as traditional security measures that focus on +the network, hardware, or software where the data resides. Organizations aligning to concepts like Data-Centric Audit and Protection (DCAP) as defined by Gartner, or the requirements of strict compliance regulations like EU GDPR, are looking to implement processes that help them understand where sensitive data is stored, who or what is leveraging their privileges to @@ -15,7 +15,7 @@ access the data, and how each database has been configured. As part of Netwrix comprehensive Data Access Governance suite for structured and unstructured data, Enterprise Auditor for PostgreSQL automates the process of understanding where PostgreSQL databases -exist and provides an overview of the PostgreSQL environment in order to answer questions around +exist and provides an overview of the PostgreSQL environment to answer questions around data access: - Who has access to your data? @@ -23,7 +23,7 @@ data access: With visibility into every corner of PostgreSQL, organizations can proactively highlight and prioritize risks to sensitive data. Additionally, organizations can automate manual, time-consuming, -and expensive processes associated with compliance, security, and operations to easily adhere to +and expensive processes associated with compliance, security, and operations to adhere to best practices that keep PostgreSQL Server safe and operational. **Supported Platforms** @@ -42,8 +42,8 @@ topic for additional information. **Sensitive Data Discovery Considerations** The Sensitive Data Discovery Add-On must be installed on the Enterprise Auditor Console server, -which enables Sensitive Data criteria for scans. If running Sensitive Data Discovery (SDD) scans, it -will be necessary to increase the minimum amount of RAM. Each thread requires a minimum of 2 +which enables Sensitive Data criteria for scans. If you run Sensitive Data Discovery (SDD) scans, +increase the minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For example, if the job is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are required (8x2=16). @@ -52,9 +52,9 @@ resources on the Enterprise Auditor server. :::note The Sensitive Data Discovery Add-on installation package installs the appropriate JDK -(Java) version on the server. The JDK deployed is prepackaged and does not require any -configuration; it has been preconfigured to work with Enterprise Auditor and should never be -customized through Java. It will not conflict with other JDKs or Java Runtimes in the same +(Java) version on the server. The JDK deployed is prepackaged and doesn't require any +configuration; it has been preconfigured to work with Enterprise Auditor. Never customize it through +Java. It will not conflict with other JDKs or Java Runtimes in the same environment. ::: @@ -62,14 +62,14 @@ environment. **Location** The Structured Sensitive Data Discovery License is required to run the PostgreSQL Solution. It can -be installed from theEnterprise Auditor Instant Job Wizard. Once it has been installed into the Jobs +be installed from theEnterprise Auditor Instant Job Wizard. After it has been installed into the Jobs tree, navigate to the solution: Jobs > **Databases** > PostgreSQL. The 0.Collection Job Group performs sensitive data discovery and collects information on database configurations on the target hosts. The other job groups analyze and report on the data collected by the 0.Collection Job Group. -The Database Solution license includes all supported database platforms supported by Enterprise +The Database Solution license includes all database platforms supported by Enterprise Auditor. Additionally, the Sensitive Data Discovery Add-On enables the solution to search database content for sensitive data. diff --git a/docs/accessanalyzer/11.6/solutions/databases/postgresql/pgsql_databasesizing.md b/docs/accessanalyzer/11.6/solutions/databases/postgresql/pgsql_databasesizing.md index 5a2980c0e6..9d560ece47 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/postgresql/pgsql_databasesizing.md +++ b/docs/accessanalyzer/11.6/solutions/databases/postgresql/pgsql_databasesizing.md @@ -21,7 +21,7 @@ Navigate to the **Jobs > Databases > PostgreSQL > Configuration > PgSQL_Databa node and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/postgresql/recommended.md b/docs/accessanalyzer/11.6/solutions/databases/postgresql/recommended.md index acd80433d3..41341e1e46 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/postgresql/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/databases/postgresql/recommended.md @@ -8,8 +8,8 @@ sidebar_position: 10 The jobs in the PostgreSQL Solution has been configured to inherit down from the **PostgreSQL** > **Settings** node. However, it is best practice to assign the host list and the Connection Profile -at the data collection level, 0.Collection Job Group. Once these are assigned to the job group, it -can be run directly or scheduled. +at the data collection level, 0.Collection Job Group. After you assign the host list and Connection +Profile to the job group, you can run it directly or schedule it. **Dependencies** @@ -18,9 +18,9 @@ can be run directly or scheduled. Enterprise Auditor Console server - For AWS RDS and Aurora instances, right-click a job in the **PostgreSQL** > **0.Collection** folder and open the properties window. Select the **Performance** tab and ensure that the **Skip - Hosts that do not respond to PING**checkbox is not selected. + Hosts that don't respond to PING**checkbox isn't selected. -**Targeted Host(s)** +**Targeted Hosts** - The 0.Collection Job Group must be set to run against a custom host list containing the PostgreSQL database instances / clusters. @@ -35,10 +35,10 @@ the [Connection](/docs/accessanalyzer/11.6/admin/settings/connection/overview.md) topic for additional information on permissions and creating a SQL custom connection profile. -The Connection Profile is set to **Use the Default Profile**, as configured at the global settings -level. However, since this may not be the Connection Profile with the necessary permissions for the -assigned hosts, click the radio button for the **Select one of the following user defined profiles** -option and select the appropriate Connection Profile drop-down menu. +The Connection Profile defaults to the **Use the Default Profile** setting, configured at the global +settings level. If that profile doesn't have the permissions the assigned hosts need, select the +radio button for the **Select one of the following user defined profiles** option, then choose the +correct profile from the Connection Profile dropdown menu. **Schedule Frequency** @@ -46,7 +46,7 @@ Daily **Run Order** -The 0.Collection Job Group must be run first before running the other jobs and job groups. +Run the 0.Collection Job Group first, before running the other jobs and job groups. :::info Run the solution at the top level: PostgreSQL Job Group @@ -63,12 +63,12 @@ topic for additional information. **Analysis Configuration** This solution should be run with the default analysis configurations. These analysis tasks are -preconfigured and should not be modified or deselected! +preconfigured and shouldn't be modified or deselected. Disabling obsolete or run-desired jobs allows the solution to run more efficiently. To disable a job -or job group, right-click on the item and select **Disable Job**. +or job group, right-click the item and select **Disable Job**. :::info -Do not delete any jobs. Instead, jobs should be disabled. +Don't delete any jobs. Disable them instead. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/postgresql/sensitivedata/pgsql_sensitivedata.md b/docs/accessanalyzer/11.6/solutions/databases/postgresql/sensitivedata/pgsql_sensitivedata.md index 1df3808ffa..f94d75faf3 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/postgresql/sensitivedata/pgsql_sensitivedata.md +++ b/docs/accessanalyzer/11.6/solutions/databases/postgresql/sensitivedata/pgsql_sensitivedata.md @@ -15,7 +15,7 @@ Navigate to the **Jobs > Databases > PostgreSQL > Sensitive Data > PgSQL_Sens node and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/postgresql/sensitivedata/pgsql_sensitivedatapermissions.md b/docs/accessanalyzer/11.6/solutions/databases/postgresql/sensitivedata/pgsql_sensitivedatapermissions.md index 7d6e30433a..036662ed2c 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/postgresql/sensitivedata/pgsql_sensitivedatapermissions.md +++ b/docs/accessanalyzer/11.6/solutions/databases/postgresql/sensitivedata/pgsql_sensitivedatapermissions.md @@ -17,7 +17,7 @@ Data > PgSQL_SensitiveDataPermissions > Configure** node and select Analysis t tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/redshift/collection/overview.md b/docs/accessanalyzer/11.6/solutions/databases/redshift/collection/overview.md index af71412166..2101ba3187 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/redshift/collection/overview.md +++ b/docs/accessanalyzer/11.6/solutions/databases/redshift/collection/overview.md @@ -7,7 +7,7 @@ sidebar_position: 20 # 0.Collection Job Group The Redshift Solution Collection group collects high level summary information from targeted -Redshift Servers.  Other jobs in the Redshift Solution Set use this information for further analysis +Redshift Servers. Other jobs in the Redshift Solution Set use this information for further analysis and for producing respective reports. ![0](/images/accessanalyzer/11.6/solutions/databases/redshift/collection/0.collection.webp) diff --git a/docs/accessanalyzer/11.6/solutions/databases/redshift/collection/redshift_configuration.md b/docs/accessanalyzer/11.6/solutions/databases/redshift/collection/redshift_configuration.md index efaa04d3e1..33e0f0433f 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/redshift/collection/redshift_configuration.md +++ b/docs/accessanalyzer/11.6/solutions/databases/redshift/collection/redshift_configuration.md @@ -13,7 +13,7 @@ The Redshift_Configuration job returns additional configuration settings from Re The Redshift_Configuration Job uses the SQL Data Collector for queries. :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/redshift/collection/redshift_sensitivedatascan.md b/docs/accessanalyzer/11.6/solutions/databases/redshift/collection/redshift_sensitivedatascan.md index fea66473ba..cfab61e4b3 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/redshift/collection/redshift_sensitivedatascan.md +++ b/docs/accessanalyzer/11.6/solutions/databases/redshift/collection/redshift_sensitivedatascan.md @@ -22,14 +22,13 @@ The query is: ## Recommended Configuration for the SensitiveDataScan Query The Redshift_SensitiveDataScan Job is preconfigured to run using the default settings for the -Sensitive Data Collection category. It is necessary only to set up the connection for the Redshift- -SensitiveDataScan Job. Once the connection is established, it applies to any other 0.Collection job -query. Follow the steps to customize configurations. +Sensitive Data Collection category. You only need to set up the connection for the Redshift_SensitiveDataScan Job. After you establish +the connection, it applies to any other 0.Collection job query. To customize configurations: **Step 1 –** Navigate to the **Databases** > **0.Collection** > **Redshift** > **Redshift_SensitiveDataScan** > **Configure** node and select Queries. -**Step 2 –** In the Query Selection view, select the Redshift Sensitive Data Scan query click on +**Step 2 –** In the Query Selection view, select the Redshift Sensitive Data Scan query click Query Properties. The Query Properties window appears. **Step 3 –** Select the Data Source tab, and click Configure. The SQL Data Collector Wizard opens @@ -41,7 +40,7 @@ with Sensitive Data Collection category selected. ![Sensitive Data Scan Settings](/images/accessanalyzer/11.6/solutions/databases/redshift/collection/collectionsensitivedatajoboptions.webp) -**Step 5 –** To modify sensitive data scan options, select the desired scan options. See the +**Step 5 –** To modify sensitive data scan options, select the scan options you want. See the [SQL: Options](/docs/accessanalyzer/11.6/admin/datacollector/sql/options.md) page for additional information. @@ -56,7 +55,7 @@ may significantly increase scan time. ![Select DLP Criteria for Scan](/images/accessanalyzer/11.6/solutions/databases/redshift/collection/collectionsensitivedatacriteria.webp) -**Step 7 –** To modify criteria, click on **Use the following selected criteria:** and select your +**Step 7 –** To modify criteria, click **Use the following selected criteria:** and select your choices. By default, the Sensitive Data Scan job is set to **Use Global Criteria**. Also by default, the following System Criteria have been selected: @@ -117,7 +116,7 @@ page. **Step 14 –** Add the Databases and instances to be audited. Databases and instances can be added in the following ways: -- Select the desired database objects and click Add. +- Select the database objects you want and click Add. - Use the Import CSV button to import a list from a CSV file, if desired. - Optionally use the Add Custom Filter button to create and apply a custom filter. @@ -131,13 +130,13 @@ The 1-Db2_SensitsveDataScan Job is now ready to run with the customized settings ## Analysis Tasks for the Redshift_SensitiveDataScan -Navigate to the _**_Databases > 0.Collection >**Redshift >__ **Redshift_SensitiveDataScan** > -**Configure** node and select **Analysis** to view the Analysis Tasks. The Analysis tasks do not +Navigate to the **Databases** > **0.Collection** > **Redshift** > **Redshift_SensitiveDataScan** > +**Configure** node and select **Analysis** to view the Analysis Tasks. The Analysis tasks don't require any configuration as they just populate the reports with the collected information and do not collect data themselves. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/redshift/collection/redshift_tableprivileges.md b/docs/accessanalyzer/11.6/solutions/databases/redshift/collection/redshift_tableprivileges.md index e3e5791d24..15ba204ac6 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/redshift/collection/redshift_tableprivileges.md +++ b/docs/accessanalyzer/11.6/solutions/databases/redshift/collection/redshift_tableprivileges.md @@ -14,7 +14,7 @@ targeted servers. The Redshift_TablePrivileges Job uses the SQL Data Collector for queries. :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -30,7 +30,7 @@ Navigate to the **Databases** > **0.Collection** > **Redshift** > **Redshift_Tab **Configure** node and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/redshift/overview.md b/docs/accessanalyzer/11.6/solutions/databases/redshift/overview.md index 01301ddf1f..0900226650 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/redshift/overview.md +++ b/docs/accessanalyzer/11.6/solutions/databases/redshift/overview.md @@ -15,8 +15,8 @@ Data Discovery Add-On enables the solution to search Redshift and AWS content fo **Supported Platforms** -- Amazon AWS Redshift -- AWS Redshift Cluster +- Amazon AWS Redshift +- AWS Redshift Cluster **Requirements, Permissions, and Ports** @@ -26,18 +26,18 @@ topic for additional information. **Sensitive Data Discovery Considerations** -The Sensitive Data Discovery Add-On must be installed on the Enterprise Auditor Console server, -which enables Sensitive Data criteria for scans. If running Sensitive Data Discovery (SDD) scans, it -will be necessary to increase the minimum amount of RAM. Each thread requires a minimum of 2 -additional GB of RAM per host. For example, if the job is configured to scan 8 hosts at a time , -then an extra 16 GB of RAM are required (8x2=16). +Install the Sensitive Data Discovery Add-On on the Enterprise Auditor Console server to enable +Sensitive Data criteria for scans. If you run Sensitive Data Discovery (SDD) scans, increase the +minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For +example, if the job is configured to scan 8 hosts at a time, it requires an extra 16 GB of RAM +(8x2=16). By default, the job is configured to use 10 threads, which can be adjusted based on available resources on the Enterprise Auditor server. :::note The Sensitive Data Discovery Add-on installation package installs the appropriate JDK -(Java) version on the server. The JDK deployed is prepackaged and does not require any +(Java) version on the server. The JDK deployed is prepackaged and doesn't require any configuration; it has been preconfigured to work with Enterprise Auditor and should never be customized through Java. It will not conflict with other JDKs or Java Runtimes in the same environment. @@ -47,20 +47,19 @@ environment. **Location** The Redshift Solution requires a special Enterprise Auditor license. It can be installed from the -Enterprise Auditor Instant Job Wizard. Once it has been installed in the **Jobs** tree, navigate to +Enterprise Auditor Instant Job Wizard. After it has been installed in the **Jobs** tree, navigate to the solution: **Jobs** > **Databases** > **Redshift Solution**. The 0.Collection Job Group discovers SQL instances on the target hosts, and collects the data. The other job groups analyze the collected data and generate reports. -The Database Solution license includes all supported database platforms supported by Enterprise -Auditor. Additionally, the Sensitive Data Discovery Add-On enables the solution to search database +The Database Solution license includes all database platforms supported by Enterprise Auditor. Additionally, the Sensitive Data Discovery Add-On enables the solution to search database content for sensitive data. ## Redshift Job Group -The Enterprise Auditor Redshift  Solution Set is a set of preconfigured audit jobs and reports that -provides visibility into Redshift Sensitive Data. +The Enterprise Auditor Redshift Solution Set is a set of preconfigured audit jobs and reports that +provides visibility into Redshift Sensitive Data. ![redshiftjobgrpoverview](/images/accessanalyzer/11.6/solutions/databases/redshift/redshiftjobgrpoverview.webp) @@ -69,7 +68,7 @@ The following job groups comprise the Redshift Job Group: - [0.Collection Job Group](/docs/accessanalyzer/11.6/solutions/databases/redshift/collection/overview.md) — Collects high level summary information from targeted Redshift Servers. Other jobs in the Redshift Solution Set use this information for further analysis and producing respective report. - This Job Group is comprised of the following jobs(s) + This Job Group is comprised of the following jobs - [Redshift_Configuration Job](/docs/accessanalyzer/11.6/solutions/databases/redshift/collection/redshift_configuration.md) - [Redshift_SensitiveDataScan Job](/docs/accessanalyzer/11.6/solutions/databases/redshift/collection/redshift_sensitivedatascan.md) @@ -81,7 +80,7 @@ The following job groups comprise the Redshift Job Group: - [Sensitive Data Job Group](/docs/accessanalyzer/11.6/solutions/databases/redshift/sensitivedata/overview.md) — Provides insight into where sensitive data exists and who has access to it across all the - targeted Redshift databases.This Job Group is comprised of the following job(s): + targeted Redshift databases. This Job Group is comprised of the following jobs: - [Redshift_SensitiveData Job](/docs/accessanalyzer/11.6/solutions/databases/redshift/sensitivedata/redshift_sensitivedata.md) - [Redshift_SensitiveDataPermissions Job](/docs/accessanalyzer/11.6/solutions/databases/redshift/sensitivedata/redshift_sensitivedatapermissions.md) diff --git a/docs/accessanalyzer/11.6/solutions/databases/redshift/recommended.md b/docs/accessanalyzer/11.6/solutions/databases/redshift/recommended.md index 356fbdfe57..e4104a114e 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/redshift/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/databases/redshift/recommended.md @@ -8,7 +8,7 @@ sidebar_position: 10 The Redshift Solution is configured to inherit settings from the global Settings node. However, it is best practice to assign the host list and the Connection Profile at the data collection level, -the 0.Collection Job Group. Once these are assigned to the job group, it can be run directly or +the 0.Collection Job Group. After these are assigned to the job group, it can be run directly or scheduled. **Dependencies** @@ -16,7 +16,7 @@ scheduled. - For Sensitive Data Discovery Auditing – Sensitive Data Discovery Add-On installed on the Enterprise Auditor Console server -**Targeted Host(s)** +**Targeted Hosts** The Redshift Job Group has been configured to inherit the host list assignment from the collection group level. @@ -28,7 +28,7 @@ The host list assignment should be assigned under the **Redshift** > **0.Collect The SQL Data Collector requires a specific set of permissions. See the Permissions section for necessary permissions. The account used can be either an Active Directory account or a SQL account. -Once the account has been provisioned, create a custom Connection Profile containing the credentials +After the account has been provisioned, create a custom Connection Profile containing the credentials for the targeted environment. See the [SQL Custom Connection Profile & Default Dynamic Host List](/docs/accessanalyzer/11.6/admin/datacollector/sql/configurejob.md) topic for additional information. @@ -37,7 +37,7 @@ The Connection Profile should be assigned under the **Redshift** > **0.Collectio **Connection** node. It is set to **Use the Default Profile**, as configured at the global settings level. However, since this may not be the Connection Profile with the necessary permissions for the assigned hosts, click the radio button for the **Select one of the following user defined profiles** -option and select the appropriate Connection Profile drop-down menu. +option and select the appropriate Connection Profile dropdown menu. See the [Connection](/docs/accessanalyzer/11.6/admin/settings/connection/overview.md) diff --git a/docs/accessanalyzer/11.6/solutions/databases/redshift/redshift_databasesizing.md b/docs/accessanalyzer/11.6/solutions/databases/redshift/redshift_databasesizing.md index ed25a6b867..fc47afe84b 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/redshift/redshift_databasesizing.md +++ b/docs/accessanalyzer/11.6/solutions/databases/redshift/redshift_databasesizing.md @@ -11,7 +11,7 @@ vulnerabilities related to instance configuration settings. ![configurationjobgroup](/images/accessanalyzer/11.6/solutions/databases/redshift/configurationjobgroup.webp) -The job(s) in the Configuration Job Group are: +The jobs in the Configuration Job Group are: - Redshift_DatabaseSizing Job — Provides details about Redshift databases and overall database size. @@ -21,7 +21,7 @@ Navigate to the **Jobs** > **Databases**> **Redshift** > **Configuration** > **Redshift_DatabaseSizing** > **Configure** node and select **Analysis** to view the Analysis Tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/redshift/sensitivedata/overview.md b/docs/accessanalyzer/11.6/solutions/databases/redshift/sensitivedata/overview.md index 3c5a302d3e..61eda88a86 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/redshift/sensitivedata/overview.md +++ b/docs/accessanalyzer/11.6/solutions/databases/redshift/sensitivedata/overview.md @@ -11,7 +11,7 @@ targeted Redshift databases. ![sensitivedatajobgroup](/images/accessanalyzer/11.6/solutions/databases/redshift/sensitive_data/sensitivedatajobgroup.webp) -The job(s) in the Sensitive Data Job Group are: +The jobs in the Sensitive Data Job Group are: - [Redshift_SensitiveData Job](/docs/accessanalyzer/11.6/solutions/databases/redshift/sensitivedata/redshift_sensitivedata.md) - Provides information on all the data that was discovered in the targeted Redshift database servers diff --git a/docs/accessanalyzer/11.6/solutions/databases/redshift/sensitivedata/redshift_sensitivedata.md b/docs/accessanalyzer/11.6/solutions/databases/redshift/sensitivedata/redshift_sensitivedata.md index 2418374e0c..ea103abb8e 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/redshift/sensitivedata/redshift_sensitivedata.md +++ b/docs/accessanalyzer/11.6/solutions/databases/redshift/sensitivedata/redshift_sensitivedata.md @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **Databases** > **Redshift** >  **Sensitive Data** > **Redshift_SensitiveData** > **Configure** node and select **Analysis** to view the Analysis Tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/redshift/sensitivedata/redshift_sensitivedatapermissions.md b/docs/accessanalyzer/11.6/solutions/databases/redshift/sensitivedata/redshift_sensitivedatapermissions.md index 0042bef71d..213c3b0bb6 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/redshift/sensitivedata/redshift_sensitivedatapermissions.md +++ b/docs/accessanalyzer/11.6/solutions/databases/redshift/sensitivedata/redshift_sensitivedatapermissions.md @@ -17,7 +17,7 @@ Data > Redshift_SensitiveDataPermissions > Configure** node and select Analysi tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/activity/sql_activity.md b/docs/accessanalyzer/11.6/solutions/databases/sql/activity/sql_activity.md index 62c0302942..39a701f5eb 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/activity/sql_activity.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/activity/sql_activity.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 2.Activity > SQL_Activity > Configure node to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/activity/sql_logons.md b/docs/accessanalyzer/11.6/solutions/databases/sql/activity/sql_logons.md index 5db2f078c9..3a470b4277 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/activity/sql_logons.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/activity/sql_logons.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 2.Activity > SQL_Logons > Configure node to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/activity/sql_permissionchanges.md b/docs/accessanalyzer/11.6/solutions/databases/sql/activity/sql_permissionchanges.md index 3ae0d356e3..2b22089357 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/activity/sql_permissionchanges.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/activity/sql_permissionchanges.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 2.Activity > SQL_PermissionChanges > Conf Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/activity/sql_sensitivedataactivity.md b/docs/accessanalyzer/11.6/solutions/databases/sql/activity/sql_sensitivedataactivity.md index baf074ecf3..ec487f4621 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/activity/sql_sensitivedataactivity.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/activity/sql_sensitivedataactivity.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 2.Activity > SQL_SensitiveDataActivity > C select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/activity/sql_unusualactivity.md b/docs/accessanalyzer/11.6/solutions/databases/sql/activity/sql_unusualactivity.md index 0d16e0a701..3f52cd8b98 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/activity/sql_unusualactivity.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/activity/sql_unusualactivity.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 2.Activity > SQL_UnusualActivity > Config Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/collection-azuresql/0-azuresql_instancediscovery.md b/docs/accessanalyzer/11.6/solutions/databases/sql/collection-azuresql/0-azuresql_instancediscovery.md index 9cc2d3f36c..6cdf5ee53c 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/collection-azuresql/0-azuresql_instancediscovery.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/collection-azuresql/0-azuresql_instancediscovery.md @@ -25,7 +25,7 @@ Navigate to the **Databases** > **0.Collection** > **AzureSQL** > **0-AzureSQL_I **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/collection-azuresql/1-azuresql_permissionscan.md b/docs/accessanalyzer/11.6/solutions/databases/sql/collection-azuresql/1-azuresql_permissionscan.md index 9f5315601f..5dbfb74734 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/collection-azuresql/1-azuresql_permissionscan.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/collection-azuresql/1-azuresql_permissionscan.md @@ -20,18 +20,18 @@ The 1–AzureSQL_PermissionsScan Job uses the SQL Data Collector for the followi ### Configure the PermissionsScan Query The 1-AzureSQL_PermissionScan Job is preconfigured to run using the default settings within the -Permissions Collection category. Follow the steps to customize configurations. +Permissions Collection category. To customize configurations: **Step 1 –** Navigate to the **Databases** > 0.Collection > AzureSQL > 1-AzureSQL_PermissionsScan > Configure node and select **Queries**. -**Step 2 –** In the Query Selection view, select the PermissionsScan query and click on Query +**Step 2 –** In the Query Selection view, select the PermissionsScan query and click Query Properties. The Query Properties window appears. **Step 3 –** Select the Data Source tab and click Configure. The SQL Data Collector Wizard opens. :::warning -Do not make changes to other wizard pages as they have been pre-configured for this +Don't make changes to other wizard pages as they have been pre-configured for this job. ::: @@ -44,7 +44,7 @@ page. The default query target is All databases. The default query scope is Only objects and click Retrieve. The Available database objects will be populated. Databases and instances can be added in the following ways: -- Select the desired database objects and click Add. +- Select the database objects you want and click Add. - Use the Import CSV button to import a list from a CSV file, if desired. - Optionally, use the Add Custom Filter button to create and apply a custom filter. @@ -71,7 +71,7 @@ Navigate to the Databases > 0.Collection > **AzureSQL** > 1-AzureSQL_Permissions node and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/collection-azuresql/2-azuresql_sensitivedatascan.md b/docs/accessanalyzer/11.6/solutions/databases/sql/collection-azuresql/2-azuresql_sensitivedatascan.md index 1620360dcd..2b565c0946 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/collection-azuresql/2-azuresql_sensitivedatascan.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/collection-azuresql/2-azuresql_sensitivedatascan.md @@ -23,7 +23,7 @@ Navigate to the **Databases** > **0.Collection** > **AzureSQL** > **2–AzureSQL **Configure** node and select Analysis to view the analysis task. :::warning -Do not modify or deselect the selected analysis task(s). The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/collection-azuresql/3-azuresql_activityscan.md b/docs/accessanalyzer/11.6/solutions/databases/sql/collection-azuresql/3-azuresql_activityscan.md index 4265140207..a39058fa10 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/collection-azuresql/3-azuresql_activityscan.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/collection-azuresql/3-azuresql_activityscan.md @@ -23,7 +23,7 @@ Navigate to the **Databases** > **0.Collection** > **Azure SQL** > **3–AzureSQL_ActivityScan** > **Configure** node and select **Analysis** to view the analysis task. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/collection-azuresql/4-azuresql_serversettings.md b/docs/accessanalyzer/11.6/solutions/databases/sql/collection-azuresql/4-azuresql_serversettings.md index 261db9ba83..263ff6c87c 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/collection-azuresql/4-azuresql_serversettings.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/collection-azuresql/4-azuresql_serversettings.md @@ -29,7 +29,7 @@ Navigate to the **Databases** > **0.Collection** > **Azure SQL** > task. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/collection/0-sql_instancediscovery.md b/docs/accessanalyzer/11.6/solutions/databases/sql/collection/0-sql_instancediscovery.md index 839d1e5b40..72db443e22 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/collection/0-sql_instancediscovery.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/collection/0-sql_instancediscovery.md @@ -24,7 +24,7 @@ Navigate to the **Databases** > **0.Collection** > **SQL** > **0-SQL_InstanceDis **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/collection/1-sql_permissionsscan.md b/docs/accessanalyzer/11.6/solutions/databases/sql/collection/1-sql_permissionsscan.md index a6e1cfc613..a1b8009e8e 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/collection/1-sql_permissionsscan.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/collection/1-sql_permissionsscan.md @@ -23,18 +23,18 @@ The 1-SQL_PermissionsScan Job uses the SQL Data Collector for the following quer ### Configure the PermissionsScan Query The 1-SQL_PermissionScan Job is preconfigured to run using the default settings within the -Permissions Collection category. Follow the steps to customize configurations. +Permissions Collection category. To customize configurations: **Step 1 –** Navigate to the **Databases** > 0.Collection > SQL > 1-SQL_PermissionsScan > Configure node and select Queries. -**Step 2 –** In the Query Selection view, select the PermissionsScan query and click on Query +**Step 2 –** In the Query Selection view, select the PermissionsScan query and click Query Properties. The Query Properties window appears. **Step 3 –** Select the Data Source tab and click Configure. The SQL Data Collector Wizard opens. :::warning -Do not make changes to other wizard pages as they have been pre-configured for this +Don't make changes to other wizard pages as they have been pre-configured for this job. ::: @@ -47,7 +47,7 @@ page. The default query target is All databases. The default query scope is Only objects and click Retrieve. The Available database objects will be populated. Databases and instances can be added in the following ways: -- Select the desired database objects and click Add. +- Select the database objects you want and click Add. - Use the Import CSV button to import a list from a CSV file, if desired. - Optionally, use the Add Custom Filter button to create and apply a custom filter. @@ -62,7 +62,7 @@ Navigate to the **Databases** > 0.Collection > SQL > 1-SQL_PermissionsScan > Con select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -71,7 +71,7 @@ preconfigured for this job. The default analysis tasks are: -- Remove Old AIC Resources — Removes AIC resources using the old path that did not include the +- Remove Old AIC Resources — Removes AIC resources using the old path that didn't include the schema - AIC Import – Hosts — Imports SQL hosts to the AIC - AIC Import – Instance Permissions Node — Imports a node for instance permissions for each instance diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/collection/2-sql_sensitivedatascan.md b/docs/accessanalyzer/11.6/solutions/databases/sql/collection/2-sql_sensitivedatascan.md index f6b65f89c7..10a9ba344e 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/collection/2-sql_sensitivedatascan.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/collection/2-sql_sensitivedatascan.md @@ -36,25 +36,25 @@ The SensitiveDataScan Job uses the SQL Data Collector for the following query: ### Configure the SensitiveDataScan Query The 2-SQL_SensitiveDataScan Job is preconfigured to run using the default settings for the Sensitive -Data Collection category. Follow the steps to customize configurations. +Data Collection category. To customize configurations: **Step 1 –** Navigate to the **Databases** > 0.Collection > SQL > 2-SQL_SensitiveDataScan > Configure node and select Queries. -**Step 2 –** In the Query Selection view, select the SensitiveDataScan query click on Query +**Step 2 –** In the Query Selection view, select the SensitiveDataScan query click Query Properties. The Query Properties window appears. **Step 3 –** Select the Data Source tab, and click Configure. The SQL Data Collector Wizard opens. :::warning -Do not make changes to other wizard pages as they have been pre-configured for this +Don't make changes to other wizard pages as they have been pre-configured for this job. ::: ![2sqlsensitivedatascanoptionspage](/images/accessanalyzer/11.6/solutions/databases/sql/collection/2sqlsensitivedatascanoptionspage.webp) -**Step 4 –** Select the desired scan options. Navigate to the +**Step 4 –** Select the scan options you want. Navigate to the [SQL: Options](/docs/accessanalyzer/11.6/admin/datacollector/sql/options.md) page for additional information. @@ -89,7 +89,7 @@ page. The query is configured by default to target Only select database objects. Available database objects box will populate. Databases and instances can be added in the following ways: -- Select the desired database objects and click Add. +- Select the database objects you want and click Add. - Use the Import CSV button to import a list from a CSV file, if desired. - Optionally use the Add Custom Filter button to create and apply a custom filter. @@ -104,7 +104,7 @@ Navigate to the **Databases** > 0.Collection > SQL > 2-SQL_SensitiveDataScan > select Analysis to view the analysis task. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/collection/3-sql_activityscan.md b/docs/accessanalyzer/11.6/solutions/databases/sql/collection/3-sql_activityscan.md index 8bdc9de65d..8e0c599c19 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/collection/3-sql_activityscan.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/collection/3-sql_activityscan.md @@ -30,18 +30,18 @@ The ActivityScan Job uses the SQL Data Collector for the following query: ### Configure the ActivityScan Query The 3-SQL_ActivityScan Job is preconfigured to run using the default settings within the Server -Audits Events Collection category. Follow the steps to customize configurations. +Audits Events Collection category. To customize configurations: **Step 1 –** Navigate to the **Databases** > 0.Collection > SQL > 3-SQL_ActivityScan > Configure node and select Queries. -**Step 2 –** In the Query Selection view, click on Query Properties. The Query Properties window +**Step 2 –** In the Query Selection view, click Query Properties. The Query Properties window appears. **Step 3 –** Select the Data Source tab, and click Configure. The SQL Data Collector Wizard opens. :::warning -Do not make changes to other wizard pages as they have been pre-configured for the +Don't make changes to other wizard pages as they have been pre-configured for the purpose of this job. ::: @@ -50,7 +50,7 @@ purpose of this job. **Step 4 –** To modify scan options, navigate to the [SQL Data Collector](/docs/accessanalyzer/11.6/admin/datacollector/sql/overview.md) -page. Select the desired scan options. The query is preconfigured with the following default +page. Select the scan options you want. The query is preconfigured with the following default settings: - Collect only events since last scan – Collects activity recorded since the previous scan @@ -66,7 +66,7 @@ page. The query is configured by default to target Only select database objects. Available database objects will be populated. Databases and instances can be added in the following ways: -Select the desired database objects and click Add. +Select the database objects you want and click Add. Use the Import CSV button to import a list from a CSV file. @@ -83,7 +83,7 @@ Navigate to the **Databases** > 0.Collection > SQL > 3-SQL_ActivityScan > Config Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/collection/4-sql_serverlogons.md b/docs/accessanalyzer/11.6/solutions/databases/sql/collection/4-sql_serverlogons.md index 371447770e..cc50b2fc80 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/collection/4-sql_serverlogons.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/collection/4-sql_serverlogons.md @@ -15,7 +15,7 @@ The AppnLogSQL Query uses the SMARTLog Data Collector and has been preconfigured Windows Event Log Type. :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/collection/5-sql_serversettings.md b/docs/accessanalyzer/11.6/solutions/databases/sql/collection/5-sql_serversettings.md index 47238b4103..cf32d36c64 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/collection/5-sql_serversettings.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/collection/5-sql_serversettings.md @@ -35,19 +35,19 @@ The 5-SQL_ServerSettings Job uses the SQL Data Collector for the following queri ### Configure the Configuration Query The 5-SQL_ServerSettings Job’s Configuration Query is configured to run with the default settings -with the Configuration Properties category. Follow the steps to customize configurations. +with the Configuration Properties category. To customize configurations: **Step 1 –** Navigate to the **Databases** > 0.Collection > SQL > 5-SQL_ServerSettings > Configure node and select Queries. -**Step 2 –** In the Query Selection view, select the Configuration Query and click on Query +**Step 2 –** In the Query Selection view, select the Configuration Query and click Query Properties. The Query Properties window will appear. **Step 3 –** Select the Data Source tab, and click Configure. The SQL Data Collector Wizard will open. :::warning -Do not make changes to other wizard pages as they have been pre-configured for the +Don't make changes to other wizard pages as they have been pre-configured for the purpose of this job. ::: @@ -60,7 +60,7 @@ page. The query is configured by default to target All instances. Change the que select instances, and click Retrieve. The Available server audits will be populated. Databases and instances can be added in the following ways: -- Select the desired instances and click Add. +- Select the instances you want and click Add. - Use the Import CSV button to import a list from a CSV file. - (Optional) Use the Add Custom Filter button to create and apply a custom filter. @@ -73,20 +73,20 @@ The 5-SQL_ServerSettings Job is now ready to run with the customized settings. The 5-SQL_ServerSettingsJob > Server Query has been preconfigured to run with the default settings with the category of Server Properties. However, the query can be scoped to target specific -databases/instances on the Filters page of the SQL Data Collector Wizard. Follow these steps to -modify the query configuration. +databases/instances on the Filters page of the SQL Data Collector Wizard. To +modify the query configuration: **Step 1 –** Navigate to the **Databases** > 0.Collection > SQL > 5-SQL_ServerSettings > Configure node and select Queries. -**Step 2 –** In the Query Selection view, select the Server query click on Query Properties. The +**Step 2 –** In the Query Selection view, select the Server query click Query Properties. The Query Properties window will appear. **Step 3 –** Select the Data Source tab, and click Configure. The SQL Data Collector Wizard will open. :::warning -Do not make changes to other wizard pages as they have been pre-configured for the +Don't make changes to other wizard pages as they have been pre-configured for the purpose of this job. ::: @@ -99,7 +99,7 @@ page. The query is configured by default to target All instances. Change the que select instances, and click Retrieve. The Available server audits will be populated. Databases and instances can be added in the following ways: -- Select the desired instances and click Add. +- Select the instances you want and click Add. - Use the Import CSV button to import a list from a CSV file. - Optionally use the Add Custom Filter button to create and apply a custom filter. diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/overview.md b/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/overview.md index 0bbc16ddf2..492e7181f1 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/overview.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/overview.md @@ -16,7 +16,7 @@ The jobs in the 4.Configuration Job Group are: - [SQL_Authentication Job](/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/sql_authentication.md) – This job identifies authentication settings on targeted SQL and Azure SQL servers that allow SQL server authentication in addition to Windows authentication. Microsoft recommends that the SQL and - Azure SQL servers should be generally configured to utilize Windows authentication versus SQL + Azure SQL servers should be generally configured to use Windows authentication versus SQL authentication. - [SQL_BestPractices Job](/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/sql_bestpractices.md) – This job is designed to analyze SQL and Azure SQL server configuration settings and report on @@ -25,12 +25,12 @@ The jobs in the 4.Configuration Job Group are: - [SQL_CMDShell Job](/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/sql_cmdshell.md) – This job is designed to report if the `xp_cmdshell `stored procedure is enabled or disabled. Since `xp_cmdshell` allows a user to execute operating system commands when connected to the SQL - or Azure SQL server, it can be used to launch malicious attacks. Microsoft recommends that the + or Azure SQL server, attackers can use it to launch malicious attacks. Microsoft recommends that the `xp_cmdshell` stored procedure be disabled. - [SQL_DatabaseSizing Job](/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/sql_databasesizing.md) – Provides details on database file sizes and overall database sizes - [SQL_LinkedServers Job](/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/sql_linkedservers.md) – Identifies Linked Servers or remote database servers on which the identified SQL and Azure SQL server can execute commands. Some of the common remote OLE DB providers include IBM DB2, - Oracle, Access and Excel. Typically, linked servers are used to handle distributed queries in SQL + Oracle, Access, and Excel. Typically, linked servers are used to handle distributed queries in SQL and Azure SQL server. diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/sql_authentication.md b/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/sql_authentication.md index 113794dbd4..aa04c331b3 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/sql_authentication.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/sql_authentication.md @@ -8,7 +8,7 @@ sidebar_position: 10 The SQL_Authentication Job identifies authentication settings on targeted SQL and Azure SQL servers that allow SQL server authentication in addition to Windows authentication. Microsoft recommends -that SQL and Azure SQL servers should be generally configured to utilize Windows authentication +that SQL and Azure SQL servers should be generally configured to use Windows authentication versus SQL server authentication. ## Analysis Tasks for the SQL_Authentication Job @@ -17,7 +17,7 @@ Navigate to the **Databases** > SQL > 4.Configuration > SQL_Authentication > Con select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -36,4 +36,4 @@ produces the following pre-configured report. | Report | Description | Default Tags | Report Elements | | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| SQL  Authentication | This report identifies authentication settings on the targeted servers, and highlights those with SQL Authentication enabled. Additionally, the number of SQL logins on a given instance, and whether or not the 'sa' login exists, are indicated. Best practices recommend that SQL instances be integrated login only, and that the 'sa' principal be renamed or removed. | None | This report is comprised of two elements:
  • Pie Chart – Displays instances with integrated security only
  • Table – Displays integrated security details by instance
| +| SQL  Authentication | This report identifies authentication settings on the targeted servers, and highlights those with SQL Authentication enabled. Additionally, the number of SQL logins on a given instance, and whether the 'sa' login exists, are indicated. Best practices recommend that SQL instances be integrated login only, and that the 'sa' principal be renamed or removed. | None | This report is comprised of two elements:
  • Pie Chart – Displays instances with integrated security only
  • Table – Displays integrated security details by instance
| diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/sql_bestpractices.md b/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/sql_bestpractices.md index d6c08ab147..36e78ddbd9 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/sql_bestpractices.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/sql_bestpractices.md @@ -16,7 +16,7 @@ Navigate to the **Databases** > SQL > 4.Configuration > SQL_BestPractices > Con select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/sql_cmdshell.md b/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/sql_cmdshell.md index 7cef870ba5..80a725834a 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/sql_cmdshell.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/sql_cmdshell.md @@ -7,8 +7,8 @@ sidebar_position: 30 # SQL_CMDShell Job The SQL_CMDShell Job reports on whether the `xp_cmdshell` stored procedure is enabled or disabled. -Since `xp_cmdshell` allows users to execute operating system commands when connected to the SQL or -the Azure SQL server, it can be used to launch malicious attacks. Microsoft recommends that the +Since `xp_cmdshell` lets users execute operating system commands when connected to the SQL or +the Azure SQL server, attackers can use it to launch malicious attacks. Microsoft recommends that the `xp_cmdshell` stored procedure be disabled. ## Analysis Tasks for the SQL_CMDShell Job @@ -17,7 +17,7 @@ Navigate to the **Databases** > SQL > 4.Configuration > SQL_CMDShell > Configure Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/sql_databasesizing.md b/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/sql_databasesizing.md index 86f0bf4aab..9f3a063ee9 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/sql_databasesizing.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/sql_databasesizing.md @@ -14,7 +14,7 @@ Navigate to the **Databases** > Jobs > SQL > 4.Configuration > SQL_DatabaseSizi node and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/sql_linkedservers.md b/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/sql_linkedservers.md index fa96ccd638..0cfbde1ecd 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/sql_linkedservers.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/configuration/sql_linkedservers.md @@ -8,7 +8,7 @@ sidebar_position: 50 The SQL_LinkedServers Job identifies Linked Servers or remote database servers on which the identified SQL and Azure SQL servers can execute commands. Some of the common remote -OLE DB providers include IBM DB2, Oracle, Access and Excel. Typically, linked servers are used to +OLE DB providers include IBM DB2, Oracle, Access, and Excel. Typically, linked servers are used to handle distributed queries in SQL and Azure SQL server . ## Analysis Tasks for the SQL_LinkedServers Job @@ -17,7 +17,7 @@ Navigate to the **Databases** > Jobs > SQL > 4.Configuration > SQL_LinkedServers and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are pre-configured for this job. ::: @@ -34,4 +34,4 @@ following preconfigured report: | Report | Description | Default Tags | Report Elements | | -------------- | ----------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Linked Servers | This report highlights Linked Servers where the listed SQL Server is able to execute remote commands. | None | This report is comprised of three elements:
  • Bar Chart – Provides information on top five linked servers by instance
  • Table – Provides details on linked servers by instance
  • Table – Provides details on linked servers
| +| Linked Servers | This report highlights Linked Servers where the listed SQL Server can execute remote commands. | None | This report is comprised of three elements:
  • Bar Chart – Provides information on top five linked servers by instance
  • Table – Provides details on linked servers by instance
  • Table – Provides details on linked servers
| diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/overview.md b/docs/accessanalyzer/11.6/solutions/databases/sql/overview.md index 211a22e835..2ad8fe090b 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/overview.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/overview.md @@ -29,14 +29,14 @@ topic for additional information. **Sensitive Data Discovery Considerations** The Sensitive Data Discovery Add-On must be installed on the Enterprise Auditor Console server, -which enables Sensitive Data criteria for scans.If running Sensitive Data Discovery (SDD) scans, it -will be necessary to increase the minimum amount of RAM. Each thread requires a minimum of 2 -additional GB of RAM per host.For example, if the job is configured to scan 8 hosts at a time , then -an extra 16 GB of RAM are required (8x2=16). +which enables Sensitive Data criteria for scans. If running Sensitive Data Discovery (SDD) scans, you +must increase the minimum amount of RAM. Each thread requires a minimum of 2 +additional GB of RAM per host. For example, if the job is configured to scan 8 hosts at a time, you +need an extra 16 GB of RAM (8 x 2 = 16). :::note The Sensitive Data Discovery Add-on installation package installs the appropriate JDK -(Java) version on the server. The JDK deployed is prepackaged and does not require any +(Java) version on the server. The JDK deployed is prepackaged and doesn't require any configuration; it has been preconfigured to work with Enterprise Auditor and should never be customized through Java. It will not conflict with other JDKs or Java Runtimes in the same environment. diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/permissions/overview.md b/docs/accessanalyzer/11.6/solutions/databases/sql/permissions/overview.md index 0c5fa1d070..a8ddb2d9c6 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/permissions/overview.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/permissions/overview.md @@ -15,7 +15,7 @@ The jobs in the 3.Permissions Job Group are: - [SQL_ControlServer Job](/docs/accessanalyzer/11.6/solutions/databases/sql/permissions/sql_controlserver.md) – This job will provide information on control server permissions. Users with control server - permissions allow users to command full control of a SQL and Azure SQL server instances + permissions can command full control of a SQL and Azure SQL server instances - [SQL_DirectPermissions Job](/docs/accessanalyzer/11.6/solutions/databases/sql/permissions/sql_directpermissions.md) – This job will provide information about the permissions granted to users at the schema, database, and server levels diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/permissions/sql_controlserver.md b/docs/accessanalyzer/11.6/solutions/databases/sql/permissions/sql_controlserver.md index b8fb6ba3c7..64aa997e73 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/permissions/sql_controlserver.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/permissions/sql_controlserver.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 3.Permissions > SQL_ControlServer > Confi Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/permissions/sql_directpermissions.md b/docs/accessanalyzer/11.6/solutions/databases/sql/permissions/sql_directpermissions.md index 28f344c825..42f1601132 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/permissions/sql_directpermissions.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/permissions/sql_directpermissions.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 3.Permissions > SQL_DirectPermissions > Co select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/permissions/sql_domainuserpermissions.md b/docs/accessanalyzer/11.6/solutions/databases/sql/permissions/sql_domainuserpermissions.md index 7d50e25482..6146a2b921 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/permissions/sql_domainuserpermissions.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/permissions/sql_domainuserpermissions.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 3.Permissions > SQL_DomainUserPermissions select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/permissions/sql_publicpermissions.md b/docs/accessanalyzer/11.6/solutions/databases/sql/permissions/sql_publicpermissions.md index 4705686043..24a4ab2aaf 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/permissions/sql_publicpermissions.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/permissions/sql_publicpermissions.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 5.Permissions > SQL_PublicPermissions > C select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -29,7 +29,7 @@ The default analysis tasks are: - Public Permissions Summary – Creates the SA_SQLServer_PublicPermissions_DatabaseSummary table accessible under the job’s Results node - Public Permissions Summary – Highlights permissions that have been granted to the public role on - objects that are not-default SQL or Azure SQL server objects + non-default SQL or Azure SQL server objects - Public Permissions Instance Summary (Non-Default) – Summarizes non-default SQL and Azure SQL server public permissions by instance @@ -38,4 +38,4 @@ produces the following pre-configured report. | Report | Description | Default Tags | Report Elements | | ------------------ | -------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Public Permissions | This report determines highlights objects with public permissions applied. | None | This report is comprised of three elements:
  • Bar Chart – Displays top databases by public permission count
  • Table – Provides details on databases by public permission count
  • Table – Provides details on public permission details
| +| Public Permissions | This report highlights objects with public permissions applied. | None | This report is comprised of three elements:
  • Bar Chart – Displays top databases by public permission count
  • Table – Provides details on databases by public permission count
  • Table – Provides details on public permission details
| diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/permissions/sql_serverpermissions.md b/docs/accessanalyzer/11.6/solutions/databases/sql/permissions/sql_serverpermissions.md index 36dc355de6..b7e291dd62 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/permissions/sql_serverpermissions.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/permissions/sql_serverpermissions.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 3.Permissions > SQL_ServerPermissions > C select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/recommended.md b/docs/accessanalyzer/11.6/solutions/databases/sql/recommended.md index 4e894a7d4d..ed0dcfe4c2 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/recommended.md @@ -18,8 +18,8 @@ The SQL Solution Jobs report on both the SQL and Azure SQL Collection Jobs. The SQL Solution has been configured to inherit down from the SQL > Settings node. However, it is best practice to assign the host list and the Connection Profile at the data collection level, the -0.Collection Job Group. Once these are assigned to the job group, it can be run directly or -scheduled. +0.Collection Job Group. After you assign these to the job group, you can run it directly or +schedule it. **Dependencies** @@ -40,13 +40,13 @@ scheduled. - [Privileged Accounts Job Group](/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/overview.md) - [Privileged Accounts Job Group](/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/overview.md) -Some of the 0.Collection Job Group queries can be scoped to target specific databases/instances. -However, it is necessary for the SA_SQL_Instances table to be populated before attempting to scope -the queries. Therefore, the +You can scope some of the 0.Collection Job Group queries to target specific databases/instances. +However, you must populate the SA_SQL_Instances table before scoping the queries. Therefore, +manually run the [0-SQL_InstanceDiscovery Job](/docs/accessanalyzer/11.6/solutions/databases/sql/collection/0-sql_instancediscovery.md) -must be manually executed before attempting to scope the 0.Collection Job Group queries. +before scoping the 0.Collection Job Group queries. -**Targeted Host(s)** +**Targeted Hosts** The 0.Collection Job Group has been set to run against the following default dynamic host list: @@ -54,7 +54,7 @@ The 0.Collection Job Group has been set to run against the following default dyn :::note Default dynamic host lists are populated from hosts in the Host Master Table which - meet the host inventory criteria for the list. Ensure the appropriate host list(s) have been + meet the host inventory criteria for the list. Ensure the appropriate host lists have been populated through host inventory results. ::: @@ -63,16 +63,16 @@ The 0.Collection Job Group has been set to run against the following default dyn The SQL Data Collector requires a specific set of permissions. See the Permissions section for necessary permissions. The account used can be either an Active Directory account or a SQL account. -Once the account has been provisioned, create a custom Connection Profile containing the credentials +After the account has been provisioned, create a custom Connection Profile containing the credentials for the targeted environment. See the [SQL Custom Connection Profile & Default Dynamic Host List](/docs/accessanalyzer/11.6/admin/datacollector/sql/configurejob.md) topic for additional information. -The Connection Profile should be assigned under the SQL > 0.Collection > Settings > Connection node. +Assign the Connection Profile under the SQL > 0.Collection > Settings > Connection node. It is set to Use the Default Profile, as configured at the global settings level. However, since this may not be the Connection Profile with the necessary permissions for the assigned hosts, click the radio button for the Select one of the following user defined profiles option and select the -appropriate Connection Profile drop-down menu. +appropriate Connection Profile dropdown menu. See the [Connection](/docs/accessanalyzer/11.6/admin/settings/connection/overview.md) @@ -80,15 +80,15 @@ topic for additional information. **Schedule Frequency** -One of the most important decisions to make is how frequently to collect this data. The SQL Job -Group can be scheduled to run as desired depending on the types of auditing being conducted and the -scope of the target environment. The general recommendation is to schedule the solution to run +One of the most important decisions to make is how frequently to collect this data. You can +schedule the SQL Job Group to run as desired depending on the types of auditing being conducted and +the scope of the target environment. Schedule the solution to run daily. **Run Order** -The 0.Collection Jobs must be run first and in order. The other SQL Solution sub-job groups can be -run in any order, together or individually, after running the 0.Collection Job Group. +Run the 0.Collection Jobs first and in order. You can run the other SQL Solution sub-job groups in +any order, together or individually, after running the 0.Collection Job Group. :::info Run the solution at the top level. @@ -124,20 +124,20 @@ Prerequisites: The Azure SQL Solution has been configured to inherit down from the Azure SQL > Settings node. However, it is best practice to assign the host list and the Connection Profile at the data -collection level, the 0.Collection Job Group. Once these are assigned to the job group, it can be -run directly or scheduled. +collection level, the 0.Collection Job Group. After you assign these to the job group, you can +run it directly or schedule it. **Dependencies** - Full registration within Microsoft's Azure portal: - - Creation of a Enterprise Auditor Azure SQL Role in the Access control (IAM) section + - Creation of an Enterprise Auditor Azure SQL Role in the Access control (IAM) section - Successful registration of the Enterprise Auditor app - Successful creation of an Application (client) ID - Successful configuration of an AzureSQL-specific connection profile - Creation of an Azure Tenancy host list (ex. COMPANY.onmicrosoft.com) and Azure Active Directory - user credential(s) + user credentials :::info To avoid functional issues with Enterprise Auditor, create multiple @@ -149,7 +149,7 @@ run directly or scheduled. - [0-AzureSQL_InstanceDiscovery Job](/docs/accessanalyzer/11.6/solutions/databases/sql/collection-azuresql/0-azuresql_instancediscovery.md) run successfully -**Targeted Host(s)** +**Targeted Hosts** The 0.Collection Job Group has been set to run against the following default dynamic host list: @@ -159,16 +159,16 @@ The 0.Collection Job Group has been set to run against the following default dyn The SQL Data Collector requires a specific set of permissions. See the Permissions section for necessary permissions. The account used can be either an Active Directory account with database -login enabled or a SQL account. Once the account has been provisioned, create a custom Connection +login enabled or a SQL account. After the account has been provisioned, create a custom Connection Profile containing the credentials for the targeted environment. See the [SQL Custom Connection Profile & Default Dynamic Host List](/docs/accessanalyzer/11.6/admin/datacollector/sql/configurejob.md) topic for additional information. -The Connection Profile should be assigned under the **Databases** > 0.Collection > Azure SQL > +Assign the Connection Profile under the **Databases** > 0.Collection > Azure SQL > Settings > Connection node. It is set to Use the Default Profile, as configured at the global settings level. However, since this may not be the Connection Profile with the necessary permissions for the assigned hosts, click the radio button for the Select one of the following user defined -profiles option and select the appropriate Connection Profile drop-down menu. +profiles option and select the appropriate Connection Profile dropdown menu. See the [Connection](/docs/accessanalyzer/11.6/admin/settings/connection/overview.md) @@ -176,15 +176,15 @@ topic for additional information. **Schedule Frequency** -One of the most important decisions to make is how frequently to collect this data. The Azure SQL -Job Group can be scheduled to run as desired depending on the types of auditing being conducted and -the scope of the target environment. The general recommendation is to schedule the solution to run +One of the most important decisions to make is how frequently to collect this data. You can +schedule the Azure SQL Job Group to run as desired depending on the types of auditing being conducted +and the scope of the target environment. Schedule the solution to run daily. **Run Order** -The 0.Collection Jobs must be run first and in order. The other Azure SQL Solution sub-job groups -can be run in any order, together or individually, after running the 0.Collection Job Group. +Run the 0.Collection Jobs first and in order. You can run the other Azure SQL Solution sub-job groups +in any order, together or individually, after running the 0.Collection Job Group. :::info Run the solution at the top level. diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/sensitivedata/sql_sensitivedata.md b/docs/accessanalyzer/11.6/solutions/databases/sql/sensitivedata/sql_sensitivedata.md index 715292d5f4..0bf7f629a2 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/sensitivedata/sql_sensitivedata.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/sensitivedata/sql_sensitivedata.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 5.Sensitve Data > SQL_SensitiveData > Con select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/sensitivedata/sql_sensitivedatapermissions.md b/docs/accessanalyzer/11.6/solutions/databases/sql/sensitivedata/sql_sensitivedatapermissions.md index 5f83d9be8d..81b8c37c95 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/sensitivedata/sql_sensitivedatapermissions.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/sensitivedata/sql_sensitivedatapermissions.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 5.Sensitve Data > SQL_SensitiveDataPermi node and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/overview.md b/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/overview.md index 74703f2864..230dcd6723 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/overview.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/overview.md @@ -20,7 +20,7 @@ The jobs in the 1.Users and Roles Job Group are: – This job group is designed to analyze the SQL or Azure SQL login passwords and evaluate if they comply with the prescribed password policies. In addition, it checks for weak passwords. - [SQL_RoleMembers Job](/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/sql_rolemembers.md) - – This job is designed to analyze and provide information about all the role members in each o the + – This job is designed to analyze and provide information about all the role members in each of the SQL or Azure SQL server role groups, both at the instance and database level, across all the targeted SQL or Azure SQL servers - [SQL_ServerPrincipals Job](/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/sql_serverprincipals.md) diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/sql_databaseprinciples.md b/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/sql_databaseprinciples.md index 5eb38651eb..54483444cb 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/sql_databaseprinciples.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/sql_databaseprinciples.md @@ -6,7 +6,7 @@ sidebar_position: 10 # SQL_DatabasePrinciples Job -The SQL_DatabasePrinciplesJob provides detailed information on database principals across all +The SQL_DatabasePrinciples Job provides detailed information on database principals across all targeted SQL or Azure SQL server instances. ## Analysis Tasks for the SQL_DatabasePrinciples Job @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 3.Users and Roles > SQL_DatabasePrinciple and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -29,7 +29,7 @@ The default analysis tasks are: - Summarize by instance – Creates the SA_SQLServer_DatabasePrincipals_InstanceSummary table accessible under the job’s Results node -In addition to the tables and views created by the analysis tasks, the SQL_DataPrinciples Job +In addition to the tables and views created by the analysis tasks, the SQL_DatabasePrinciples Job produces the following pre-configured report. | Report | Description | Default Tags | Report Elements | diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/sql_passwordissues.md b/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/sql_passwordissues.md index 0e88d570c7..5d0d126b73 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/sql_passwordissues.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/sql_passwordissues.md @@ -15,7 +15,7 @@ weak passwords. The Collect Weak Passwords Job uses the PowerShell Data Collector for the following query: :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -33,7 +33,7 @@ Navigate to the Jobs > **Databases** > SQL > 3.Users and Roles > SQL_PasswordIs and select Analysis to view the analysis tasks. :::warning -Most of these analysis tasks are preconfigured and should not be modified and or +Most of these analysis tasks are preconfigured and shouldn't be modified and or deselected unless otherwise specified. ::: @@ -50,7 +50,7 @@ The default analysis tasks are: [Configure the Customizable Parameters in an Analysis Task](/docs/accessanalyzer/11.6/admin/jobs/job/configure/analysis/analysiscustomizableparameters.md) topic for additional information on modifying analysis parameters. - Shared Passwords – Highlights SQL Server Logins with shared password hashes -- No Password – Inserts users that do not have a password set into the details table +- No Password – Inserts users that don't have a password set into the details table - Summarize the Weak Password Results – Summarizes the data that has been collected by the weak passwords job diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/sql_rolemembers.md b/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/sql_rolemembers.md index 2de1a8e0b9..225049ce78 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/sql_rolemembers.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/sql_rolemembers.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 3.Users and Roles > SQL_RoleMembers > Conf select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/sql_serverprincipals.md b/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/sql_serverprincipals.md index e141eff5b0..394c04cfa1 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/sql_serverprincipals.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/sql_serverprincipals.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 3.Users and Roles > SQL_ServerPrincipals select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/sql_sqllogins.md b/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/sql_sqllogins.md index a441127dab..173d3d733e 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/sql_sqllogins.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/sql_sqllogins.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 3.Users and Roles > SQL_SQLLogins > Config Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/sql_sysadmins.md b/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/sql_sysadmins.md index 07f7a6ad4e..66f38b166c 100644 --- a/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/sql_sysadmins.md +++ b/docs/accessanalyzer/11.6/solutions/databases/sql/usersroles/sql_sysadmins.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 3.Users and Roles > SQL_SysAdmins > Config Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/dropbox/collection/1-dropbox_permissions_scan.md b/docs/accessanalyzer/11.6/solutions/dropbox/collection/1-dropbox_permissions_scan.md index 954f9357d3..5d4e8a18c8 100644 --- a/docs/accessanalyzer/11.6/solutions/dropbox/collection/1-dropbox_permissions_scan.md +++ b/docs/accessanalyzer/11.6/solutions/dropbox/collection/1-dropbox_permissions_scan.md @@ -10,7 +10,7 @@ The 1-Dropbox_Permissions Scan job collects data from the Dropbox environment on sharing policies, configurations, and content. :::warning -This job should not be run if running sensitive data scans against the Dropbox Business +This job shouldn't be run if running sensitive data scans against the Dropbox Business environment. ::: @@ -28,8 +28,8 @@ The query for the 1-Dropbox_Permissions Scan job is: ### Configure the Dropbox Access Query -Follow the steps to either generate the access token needed for the Connection Profile (only done -prior to first execution) or to set any desired customizations. +To either generate the access token needed for the Connection Profile (only done +before first execution) or set any desired customizations: **Step 1 –** Navigate to the **Jobs** > **Dropbox** > **0.Collection** > **1-Dropbox_Permissions Scan** > **Configure** node and select **Queries**. @@ -42,12 +42,12 @@ Data Collector Wizard opens. ![Dropbox Access Auditor Data Collector Wizard Scan Options page](/images/accessanalyzer/11.6/solutions/dropbox/collection/permissionsscanoptionspage.webp) -**Step 4 –** T Use the Scan Options page ito generate the access token prior to the first execution +**Step 4 –** Use the Scan Options page to generate the access token before the first execution of the job group. - Remember to copy the access token, either from the textbox or using the **Copy to Clipboard** - button, and use it in the Connection Profile assigned to the Dropbox Solution. Once the access - token has been generated and copied, if no customizations are to be made, click **Cancel** to + button, and use it in the Connection Profile assigned to the Dropbox Solution. After the access + token has been generated and copied, if you don't need to make customizations, click **Cancel** to close the Dropbox Access Auditor Data Collector wizard. - See the [DropboxAccess: Scan Options](/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/scanoptions.md) @@ -65,4 +65,4 @@ collect permissions at the file level. When finished with this page, click **Nex **Step 7 –** On the Summary page, click **Finish** to save any setting modifications or click **Cancel** if no changes were made. Then click **OK** to close the Query Properties window. -If changes were made, the 1-Dropbox_Permissions Scan job has now been customized. +If you made changes, the 1-Dropbox_Permissions Scan job is now customized. diff --git a/docs/accessanalyzer/11.6/solutions/dropbox/collection/1-dropbox_sdd_scan.md b/docs/accessanalyzer/11.6/solutions/dropbox/collection/1-dropbox_sdd_scan.md index 4c7d34a312..a4c5e8ad24 100644 --- a/docs/accessanalyzer/11.6/solutions/dropbox/collection/1-dropbox_sdd_scan.md +++ b/docs/accessanalyzer/11.6/solutions/dropbox/collection/1-dropbox_sdd_scan.md @@ -7,7 +7,7 @@ sidebar_position: 20 # 1-Dropbox_SDD Scan Job The 1-Dropbox_SDD Scan job collects data from the Dropbox environment on access rights, sharing -policies, configurations, content and sensitive data. +policies, configurations, content, and sensitive data. ## Queries for the 1-Dropbox_SDD Scan Job @@ -22,8 +22,8 @@ The query for the 1-Dropbox_SDD Scan job is: ### Configure the Sensitive Data Scan Query -Follow the steps to either generate the access token needed for the Connection Profile (only done -prior to first execution) or to set any desired customizations. +To either generate the access token needed for the Connection Profile (only done +before first execution) or set any desired customizations: **Step 1 –** Navigate to the **Jobs** > **Dropbox** > **0.Collection** > **1-Dropbox_SDD Scan** > **Configure** node and select **Queries**. @@ -45,7 +45,7 @@ for additional information. ![Dropbox Access Auditor Data Collector Wizard DLP Audit Settings page](/images/accessanalyzer/11.6/solutions/dropbox/collection/sdddlpsettings.webp) -**Step 5 –** On theDLP Audit Settings page: +**Step 5 –** On the DLP Audit Settings page: - Modify the maximum file size to be scanned - Modify file types to be scanned @@ -58,7 +58,7 @@ topic for additional information. ![Dropbox Access Auditor Data Collector Wizard Select DLP criteria page](/images/accessanalyzer/11.6/solutions/dropbox/collection/sddselectdlpcriteria.webp) -**Step 6 –** On the Select DLP Criteria for This Scan page , add or remove criteria as desired. +**Step 6 –** On the Select DLP Criteria for This Scan page, add or remove criteria as desired. - (Optional) Create custom criteria with the **Edit** option. See the [Sensitive Data Criteria Editor](/docs/accessanalyzer/11.6/sensitivedatadiscovery/criteriaeditor/overview.md) @@ -71,4 +71,4 @@ topic for additional information. **Step 7 –** On the Completion Page, click **Finish** to save any setting modifications or click **Cancel** if no changes were made. Then click **OK** to close the Query Properties window. -If changes were made, the 1-Dropbox_SDD Scan job has now been customized. +If you made changes, the 1-Dropbox_SDD Scan job is now customized. diff --git a/docs/accessanalyzer/11.6/solutions/dropbox/collection/2-dropbox_permissions_bulk_import.md b/docs/accessanalyzer/11.6/solutions/dropbox/collection/2-dropbox_permissions_bulk_import.md index 08740d4b40..bd60cbc1e8 100644 --- a/docs/accessanalyzer/11.6/solutions/dropbox/collection/2-dropbox_permissions_bulk_import.md +++ b/docs/accessanalyzer/11.6/solutions/dropbox/collection/2-dropbox_permissions_bulk_import.md @@ -6,11 +6,11 @@ sidebar_position: 30 # 2-Dropbox_Permissions Bulk Import Job -The 2-Dropbox_Permissions Bulk Import job imports the data collected by the 1-Dropbox _Permissions +The 2-Dropbox_Permissions Bulk Import job imports the data collected by the 1-Dropbox_Permissions Scan job to the Enterprise Auditor database for use by the analysis tasks. :::warning -This job should not be run if running sensitive data scans against the Dropbox Business +This job shouldn't be run if running sensitive data scans against the Dropbox Business environment. ::: @@ -27,6 +27,6 @@ The query for the 2-Dropbox_Permissions Bulk Import job is: - Dropbox Bulk Import – Imports data collected by the 1-Dropbox_Permissions Scan job to the Enterprise Auditor database -There are no customization options available for this job. The Summary page of the Dropbox Access -Auditor Data Collector wizard can be viewed at the **Jobs** > **Dropbox** > **0.Collection** > +There are no customization options available for this job. You can view the Summary page of the +Dropbox Access Auditor Data Collector wizard at the **Jobs** > **Dropbox** > **0.Collection** > **2-Dropbox_Permissions Bulk Import** > **Configure** > **Queries** node. diff --git a/docs/accessanalyzer/11.6/solutions/dropbox/collection/2-dropbox_sdd_bulk_import.md b/docs/accessanalyzer/11.6/solutions/dropbox/collection/2-dropbox_sdd_bulk_import.md index 985f147bd6..2cd11194a6 100644 --- a/docs/accessanalyzer/11.6/solutions/dropbox/collection/2-dropbox_sdd_bulk_import.md +++ b/docs/accessanalyzer/11.6/solutions/dropbox/collection/2-dropbox_sdd_bulk_import.md @@ -18,9 +18,9 @@ category of Bulk Import Sensitive Content Scan. The query for the 2-Dropbox_SDD Bulk Import job is: -- DropboxSDD Bulk Import – Imports data collected by the Dropbox 1-SDD Scan Job into the Enterprise +- DropboxSDD Bulk Import – Imports data collected by the 1-Dropbox_SDD Scan Job into the Enterprise Auditor database -There are no customization options available for this job. The Summary page of the Dropbox Access -Auditor Data Collector wizard can be viewed at the **Jobs** > **Dropbox** > **0.Collection** > +There are no customization options available for this job. You can view the Summary page of the +Dropbox Access Auditor Data Collector wizard at the **Jobs** > **Dropbox** > **0.Collection** > **2-Dropbox_SDD Bulk Import** > **Configure** > **Queries** node. diff --git a/docs/accessanalyzer/11.6/solutions/dropbox/collection/overview.md b/docs/accessanalyzer/11.6/solutions/dropbox/collection/overview.md index 3d754f5dce..32ed11507e 100644 --- a/docs/accessanalyzer/11.6/solutions/dropbox/collection/overview.md +++ b/docs/accessanalyzer/11.6/solutions/dropbox/collection/overview.md @@ -15,31 +15,31 @@ the Access Information Center for analysis. The 0.Collection job group is comprised of: - [1-Dropbox_Permissions Scan Job](/docs/accessanalyzer/11.6/solutions/dropbox/collection/1-dropbox_permissions_scan.md) - – This job is responsible for scanning the target Dropbox site + – This job scans the target Dropbox site - [1-Dropbox_SDD Scan Job](/docs/accessanalyzer/11.6/solutions/dropbox/collection/1-dropbox_sdd_scan.md) - – This job is responsible for scanning sensitive data in the target Dropbox site. The Sensitive - Data Discovery Add-On is required to run this job. The Dropbox sensitive data Discovery Reports in - the Access Information Center are also populated by this data. See the Resource Audits Overview + – This job scans sensitive data in the target Dropbox site. The Sensitive + Data Discovery Add-On is required to run this job. This data also populates the Dropbox sensitive + data Discovery Reports in the Access Information Center. See the Resource Audits Overview topic in the [Netwrix Access Information Center Documentation](https://helpcenter.netwrix.com/category/accessinformationcenter) for additional information. - [2-Dropbox_Permissions Bulk Import Job](/docs/accessanalyzer/11.6/solutions/dropbox/collection/2-dropbox_permissions_bulk_import.md) - – This job is responsible for importing the collected data into the Enterprise Auditor database + – This job imports the collected data into the Enterprise Auditor database - [2-Dropbox_SDD Bulk Import Job](/docs/accessanalyzer/11.6/solutions/dropbox/collection/2-dropbox_sdd_bulk_import.md) - – This job is responsible for importing the collected sensitive data into the Enterprise Auditor - database. The Sensitive Data Discovery Add-On is required to run this job. The Dropbox sensitive - data Discovery Reports in the Access Information Center are also populated by this data. See the + – This job imports the collected sensitive data into the Enterprise Auditor + database. The Sensitive Data Discovery Add-On is required to run this job. This data also populates + the Dropbox sensitive data Discovery Reports in the Access Information Center. See the Resource Audits Overview topic in the [Netwrix Access Information Center Documentation](https://helpcenter.netwrix.com/category/accessinformationcenter) for additional information. The relationship between the scan and bulk import jobs requires the following considerations: -- A scan job executed from an Enterprise Auditor Console must be followed by the corresponding bulk +- You must follow a scan job run from an Enterprise Auditor Console with the corresponding bulk import job from the same Enterprise Auditor Console version -- Two scan jobs processing the same information, for example two 1-Dropbox_Permissions Scan jobs, - cannot be executed consecutively against the same target host. The corresponding bulk import job, - for example 2-Dropbox_Permissions Bulk Import job, must be executed in between. +- You can't run two scan jobs processing the same information, for example two 1-Dropbox_Permissions + Scan jobs, consecutively against the same target host. You must run the corresponding bulk import + job, for example the 2-Dropbox_Permissions Bulk Import job, in between. - For the Dropbox Solution, the bulk import jobs require the same connection profile as used in the corresponding scan jobs @@ -50,8 +50,8 @@ versa. :::tip -Remember, prior to running the Dropbox Solution for the first time, it is necessary to generate an -access token to be used in the Connection Profile. This only needs to be done once. See the +Remember, before running the Dropbox Solution for the first time, generate an +access token to be used in the Connection Profile. You only need to do this once. See the [Configure the Dropbox Access Query](/docs/accessanalyzer/11.6/solutions/dropbox/collection/1-dropbox_permissions_scan.md#configure-the-dropbox-access-query) topic for additional information. ::: diff --git a/docs/accessanalyzer/11.6/solutions/dropbox/dropbox_access.md b/docs/accessanalyzer/11.6/solutions/dropbox/dropbox_access.md index 1dfc2ac380..6006d034c3 100644 --- a/docs/accessanalyzer/11.6/solutions/dropbox/dropbox_access.md +++ b/docs/accessanalyzer/11.6/solutions/dropbox/dropbox_access.md @@ -17,11 +17,11 @@ The Dropbox_Access job is located in the 1.Access job group. ## Analysis Tasks for the Dropbox_Access Job -View the analysis tasks by navigating to the **Jobs** > **Dropbox** > **1.Access** > **Dro -pbox_Access** > **Configure** node and select **Analysis**. +View the analysis tasks by navigating to the **Jobs** > **Dropbox** > **1.Access** > +**Dropbox_Access** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/dropbox/dropbox_content.md b/docs/accessanalyzer/11.6/solutions/dropbox/dropbox_content.md index 8e28eea15c..dfe1c37854 100644 --- a/docs/accessanalyzer/11.6/solutions/dropbox/dropbox_content.md +++ b/docs/accessanalyzer/11.6/solutions/dropbox/dropbox_content.md @@ -16,7 +16,7 @@ The Dropbox_Content job is located in the 4.Content job group. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +The Configuration section on a Job's overview page lets you modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/11.6/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -26,7 +26,7 @@ The Dropbox_Content job has the following customizable parameter: - Days since File Modification before a file is considered stale See the -[Customizable Analysis Tasks for the Dropbox_Content Job](#customizable-analysis-tasks-for-the-dropbox_content-job) +[Customizable Analysis Tasks for the Dropbox_Content Job](#customizable-analysis-tasks-for-the-dropboxcontent-job) topic for additional information. ## Analysis Tasks for the Dropbox_Content Job @@ -35,7 +35,7 @@ View the analysis tasks by navigating to the **Jobs** > **Dropbox** > **4.Conten **Dropbox_Content** > **Configure** node and select **Analysis**. :::warning -Most of the analysis tasks should not be modified or deselected. The analysis tasks are +Most of the analysis tasks shouldn't be modified or deselected. The analysis tasks are preconfigured for this job. ::: @@ -48,7 +48,7 @@ preconfigured for this job. - By default, a stale file has not been modified in the past 365 days. You can modify this analysis task to edit this number of days. See the - [Customizable Analysis Tasks for the Dropbox_Content Job](#customizable-analysis-tasks-for-the-dropbox_content-job) + [Customizable Analysis Tasks for the Dropbox_Content Job](#customizable-analysis-tasks-for-the-dropboxcontent-job) topic for additional information. - Creates an interim processing table in the database for use by downstream analysis and report generation @@ -65,15 +65,15 @@ Dropbox_Content job produces the following pre-configured reports. ### Customizable Analysis Tasks for the Dropbox_Content Job -The time frame used to define stale content is set by default to 365 days. This can be modified +The time frame used to define stale content is set by default to 365 days. You can modify this within the **Determines stale data by owner** analysis task. The customizable parameter feature -enables you to easily set this value. +lets you set this value. | Customizable Parameter Name | Default Value | Value Indicates | | --------------------------- | ------------- | --------------------------------------------------------------------------------------------- | | @days_since_modified | 365 | How many days since the last modified day in order for a file to be considered stale content. | -The parameter can be customized and is listed in a section at the bottom of the SQL Script Editor. +You can customize the parameter. It's listed in a section at the bottom of the SQL Script Editor. See the [Configure the Customizable Parameters in an Analysis Task](/docs/accessanalyzer/11.6/admin/jobs/job/configure/analysis/analysiscustomizableparameters.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/solutions/dropbox/dropbox_groupmembership.md b/docs/accessanalyzer/11.6/solutions/dropbox/dropbox_groupmembership.md index d42aa811e0..5c6e1681c3 100644 --- a/docs/accessanalyzer/11.6/solutions/dropbox/dropbox_groupmembership.md +++ b/docs/accessanalyzer/11.6/solutions/dropbox/dropbox_groupmembership.md @@ -20,7 +20,7 @@ View the analysis tasks by navigating to the **Jobs** > **Dropbox** > **3.Group **Dropbox_GroupMembership** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/dropbox/dropbox_sensitivedata.md b/docs/accessanalyzer/11.6/solutions/dropbox/dropbox_sensitivedata.md index 14a1803ece..66a8f8a8ce 100644 --- a/docs/accessanalyzer/11.6/solutions/dropbox/dropbox_sensitivedata.md +++ b/docs/accessanalyzer/11.6/solutions/dropbox/dropbox_sensitivedata.md @@ -22,7 +22,7 @@ View the analysis tasks by navigating to the **Jobs** > **Dropbox** > **5.Sensit **Dropbox_SensitiveData** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -31,13 +31,13 @@ preconfigured for this job. - **1. Enterprise Summary** – Creates the SA_Dropbox_SensitiveData_EnterpriseSummary table accessible under the job’s Results node -- **2. Folder Details** – Creates the SA*Dropbox* SensitiveData_FolderDetails table accessible under +- **2. Folder Details** – Creates the SA_Dropbox_SensitiveData_FolderDetails table accessible under the job’s Results node -- **3. Folder Summary** – Creates the SA*Dropbox* SensitiveData_FolderSummary table accessible under +- **3. Folder Summary** – Creates the SA_Dropbox_SensitiveData_FolderSummary table accessible under the job’s Results node -- **4. Permission Details** – Creates the SA*Dropbox* SensitiveData_PermissionDetails table accessible +- **4. Permission Details** – Creates the SA_Dropbox_SensitiveData_PermissionDetails table accessible under the job’s Results node -- **5. Permission Summary** – Creates the SA*Dropbox* SensitiveData_PermissionSummary table accessible +- **5. Permission Summary** – Creates the SA_Dropbox_SensitiveData_PermissionSummary table accessible under the job’s Results node In addition to the tables created by the analysis tasks which display effective access to resources, @@ -46,5 +46,5 @@ the Dropbox_SensitiveData job produces the following pre-configured reports. | Report | Description | Default Tags | Report Elements | | -------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Enterprise Summary | This report identifies the type and amount of sensitive content found on Dropbox. | None | This report is comprised of two elements:
  • Pie Chart – Displays criteria summary by match count
  • Table – Provides criteria summary by match count
| -| Folder Details | This report identifies the location of sensitive data, and flags whether or not this data is accessible through open access. | None | This report is comprised of three elements:
  • Bar Chart – Displays top sensitive folders by file count
  • Table – Provides top sensitive folders by file count
  • Table – Provides top sensitive folder details by match count
| +| Folder Details | This report identifies the location of sensitive data, and flags whether this data is accessible through open access. | None | This report is comprised of three elements:
  • Bar Chart – Displays top sensitive folders by file count
  • Table – Provides top sensitive folders by file count
  • Table – Provides top sensitive folder details by match count
| | Sensitive Data Permissions | This report identifies the sensitive data locations and associated permissions. | None | This report is comprised of three elements:
  • Bar Chart – Displays sensitive data permission summary by file count
  • Table – Provides sensitive data permission summary by file count
  • Table – Provides sensitive data permissions by match count
| diff --git a/docs/accessanalyzer/11.6/solutions/dropbox/dropbox_sharing.md b/docs/accessanalyzer/11.6/solutions/dropbox/dropbox_sharing.md index 43ac5a6cf6..f0420a553d 100644 --- a/docs/accessanalyzer/11.6/solutions/dropbox/dropbox_sharing.md +++ b/docs/accessanalyzer/11.6/solutions/dropbox/dropbox_sharing.md @@ -9,9 +9,9 @@ sidebar_position: 40 The Dropbox_Sharing job provides insight into the sharing of resources within the targeted Dropbox environment. It is dependent on data collected by the 0.Collection job group. This job processes analysis tasks and generates a report on which resources are being shared and under which policy the -sharing occurs. Best practices often dictate that these resources should be carefully monitored due -to the amount of access to the data. If these resources contain privileged data, the access should -be reevaluated or the sensitive resources relocated. +sharing occurs. Best practices recommend monitoring these resources carefully due +to the amount of access to the data. If these resources contain privileged data, reevaluate the +access or relocate the sensitive resources. ![2.Sharing > Dropbox_Sharing Job in the Jobs Tree](/images/accessanalyzer/11.6/solutions/dropbox/sharingjobstree.webp) @@ -23,7 +23,7 @@ View the analysis tasks by navigating to the **Jobs** > **Dropbox** > **2.Sharin **Dropbox_Sharing** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/dropbox/overview.md b/docs/accessanalyzer/11.6/solutions/dropbox/overview.md index fd2c8bb654..e75bbd74c6 100644 --- a/docs/accessanalyzer/11.6/solutions/dropbox/overview.md +++ b/docs/accessanalyzer/11.6/solutions/dropbox/overview.md @@ -19,8 +19,8 @@ scanning the targeted Dropbox site. Key information includes: - Detailed Dropbox group membership - Breakdown of Dropbox content by size, type, and owner -Dropbox can scan the contents of over 400 file types to discover which files contain sensitive data -using the Sensitive Data Discovery Add-on. +Using the Sensitive Data Discovery Add-on, Dropbox can scan the contents of over 400 file types to +discover which files contain sensitive data. **Supported Platforms** @@ -34,17 +34,17 @@ topic for additional information. **Sensitive Data Discovery Considerations** -The Sensitive Data Discovery Add-On must be installed on the Enterprise Auditor Console server, -which enables Sensitive Data criteria for scans. If running Sensitive Data Discovery (SDD) scans, it -will be necessary to increase the minimum amount of RAM. Each thread requires a minimum of 2 -additional GB of RAM per host. For example, if the job is configured to scan 8 hosts at a time , -then an extra 16 GB of RAM are required (8x2=16). +You must install the Sensitive Data Discovery Add-On on the Enterprise Auditor Console server to +enable Sensitive Data criteria for scans. If you run Sensitive Data Discovery (SDD) scans, you must +increase the minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per +host. For example, if you configure the job to scan 8 hosts at a time, you need an extra 16 GB of +RAM (8 x 2 = 16). :::note The Sensitive Data Discovery Add-on installation package installs the appropriate JDK -(Java) version on the server. The JDK deployed is prepackaged and does not require any -configuration; it has been preconfigured to work with Enterprise Auditor and should never be -customized through Java. It will not conflict with other JDKs or Java Runtimes in the same +(Java) version on the server. The JDK deployed is prepackaged and doesn't require any +configuration; it has been preconfigured to work with Enterprise Auditor. Don't customize it +through Java. It will not conflict with other JDKs or Java Runtimes in the same environment. ::: @@ -52,7 +52,7 @@ environment. **Location** The Dropbox Solution requires a special Enterprise Auditor license. It can be installed from the -Instant Job Wizard. Once it has been installed into the Jobs tree, navigate to the solution: +Instant Job Wizard. After it has been installed into the Jobs tree, navigate to the solution: **Jobs** > **Dropbox**. The 0.Collection job group collects the data. The other job groups run analyses on the collected diff --git a/docs/accessanalyzer/11.6/solutions/dropbox/recommended.md b/docs/accessanalyzer/11.6/solutions/dropbox/recommended.md index d1dd985914..b13f3ee7d4 100644 --- a/docs/accessanalyzer/11.6/solutions/dropbox/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/dropbox/recommended.md @@ -7,14 +7,14 @@ sidebar_position: 10 # Recommended Configurations for the Dropbox Solution The Dropbox Solution requires the host list to be assigned and the Connection Profile configured -before job execution. Once these are assigned to the job group, it can be run directly or scheduled. +before job execution. After these are assigned to the job group, it can be run directly or scheduled. **Targeted Hosts** The Dropbox solution has been configured to inherit the host list assignment from the collection job group level. -The host list assignment should be assigned under the **Dropbox** > **0.Collection** > +Assign the host list under the **Dropbox** > **0.Collection** > **Settings** > **Host List Assignment** node. Select the **Local host** option. **Connection Profile** @@ -23,20 +23,20 @@ The DropboxAccess Data Collector requires a specific set of permissions to gener which is used to configure the Connection Profile for Dropbox. The access token is generated in the Dropbox Access Auditor Data Collector Wizard on the Scan Options page (accessed through the **1-Dropbox_Permissions Scan** job’s **Queries** node). The access token only needs to be generated -once, prior to running the job group for the first time. Then it is used as the credential in the +once, before running the job group for the first time. Then it is used as the credential in the Connection Profile. See the [DropboxAccess: Scan Options](/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/scanoptions.md) topic for additional information. The Dropbox solution has been configured to inherit the Connection Profile from the collection job -group level. The Connection Profile should be assigned under the **Dropbox** > **0.Collection** > +group level. Assign the Connection Profile under the **Dropbox** > **0.Collection** > **Settings** > **Connection** node. It is set to **Use the Default Profile**, as configured at the global settings level. However, since this may not be the Connection Profile with the necessary permissions for Dropbox, select the **Select one of the following user defined profiles** option and -select the appropriate Connection Profile from the drop-down menu. See the +select the appropriate Connection Profile from the dropdown menu. See the [Custom Dropbox Connection Profile & Host List](/docs/accessanalyzer/11.6/admin/datacollector/dropboxaccess/configurejob.md) topic for additional information on configuring the Dropbox credential. The Dropbox bulk import jobs -requires the same connection profile as used in the corresponding Dropbox scan jobs +require the same connection profile as used in the corresponding Dropbox scan jobs. See the [Connection](/docs/accessanalyzer/11.6/admin/settings/connection/overview.md) @@ -66,7 +66,7 @@ versa. ::: -After running the 0.Collection jobs, the other Dropbox solution job groups can be run in any order. +After you run the 0.Collection jobs, you can run the other Dropbox solution job groups in any order. Best practice is to run at the solution level. **Query Configuration** @@ -81,12 +81,12 @@ topic for additional information. This solution should be run with the default analysis configuration. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this solution. ::: -Though the analysis tasks should not be deselected the time frame used to define staleness can be +Though the analysis tasks shouldn't be deselected, the time frame used to define staleness can be modified: - Stale content set to default of 365 days @@ -113,10 +113,10 @@ Scan** job). **Step 2 –** Run the **2-Dropbox_Permissions Bulk Import** job (for sensitive data, run the **2-Dropbox_SDD Bulk Import** job). -**Step 3 –** Run the desired corresponding analysis and reporting sub-job groups. +**Step 3 –** Run the corresponding analysis and reporting sub-job groups you want. :::tip -Remember, prior to running the Dropbox solution for the first time, it is necessary to generate an +Remember, before running the Dropbox solution for the first time, generate an access token to be used in the Connection Profile. This only needs to be done once. See the [Configure the Dropbox Access Query](/docs/accessanalyzer/11.6/solutions/dropbox/collection/1-dropbox_permissions_scan.md#configure-the-dropbox-access-query) topic for additional information. diff --git a/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_circularnesting.md b/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_circularnesting.md index 954e4c0ef9..61ec11716d 100644 --- a/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_circularnesting.md +++ b/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_circularnesting.md @@ -6,8 +6,8 @@ sidebar_position: 10 # AAD_CircularNesting Job -The AAD_CircularNesting Job identifies circularly nested groups within Microsoft Entra ID which can -pose administrative and operational challenges with identifying effective access to resources. +The AAD_CircularNesting Job identifies circularly nested groups within Microsoft Entra ID. Circular +nesting can complicate determining effective access to resources. ## Analysis Tasks for the AAD_CircularNesting Job @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **Entra ID** > **1.Groups** > **AAD_CircularNesting** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_duplicategroups.md b/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_duplicategroups.md index d2a75fb3d4..06a946855a 100644 --- a/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_duplicategroups.md +++ b/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_duplicategroups.md @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **Entra ID** > **1.Groups** > **AAD_DuplicateGroups** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -32,4 +32,4 @@ following pre-configured report. | Report | Description | Default Tags | Report Elements | | ---------------- | ------------------------------------------------------------------- | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Duplicate Groups | This report identifies duplicate groups within the audited domains. | None | This report is comprised of one elements:
  • Bar Chart – Displays domains by number of groups with duplicates
  • Table – Provides duplicate groups details
  • Table – Provides details on domains by number of groups with duplicates
| +| Duplicate Groups | This report identifies duplicate groups within the audited domains. | None | This report is comprised of one element:
  • Bar Chart – Displays domains by number of groups with duplicates
  • Table – Provides duplicate groups details
  • Table – Provides details on domains by number of groups with duplicates
| diff --git a/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_emptygroups.md b/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_emptygroups.md index 746a78d05a..3306af4174 100644 --- a/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_emptygroups.md +++ b/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_emptygroups.md @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **Entra ID** > **1.Groups** > **AAD_EmptyGroups** > * and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_groupdirsync.md b/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_groupdirsync.md index 206d9ab249..e4bf22e29b 100644 --- a/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_groupdirsync.md +++ b/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_groupdirsync.md @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **Entra ID** > **1.Groups** > **AAD_GroupDirSync** > and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_largestgroups.md b/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_largestgroups.md index 9871870c10..db73a9ed54 100644 --- a/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_largestgroups.md +++ b/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_largestgroups.md @@ -6,9 +6,9 @@ sidebar_position: 50 # AAD_LargestGroups Job -The AAD_LargestGroups Job identifies groups with large effective member counts. These groups may -cause administrative overhead and burden in being able to easily understand who is getting access to -resources, or how much access is being granted to resources through these groups. +The AAD_LargestGroups Job identifies groups with large effective member counts. These groups can +make it difficult to determine who has access to resources through them, or how much access they +grant. ## Analysis Tasks for the AAD_LargestGroups Job @@ -16,7 +16,7 @@ Navigate to the **Jobs** > **Entra ID** > **1.Groups** > **AAD_LargestGroups** > and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -33,4 +33,4 @@ following pre-configured report. | Report | Description | Default Tags | Report Elements | | -------------- | ------------------------------------------------------------------------ | ------------ | -------------------------------------------------------------------------------------------------------------------------------------- | -| Largest Groups | This report identifies the largest groups within the audited environment | None | This report is comprised of two elements:
  • Bar Chart – Displays largest groups
  • Table – Provides group details
| +| Largest Groups | This report identifies the largest groups within the audited environment. | None | This report is comprised of two elements:
  • Bar Chart – Displays largest groups
  • Table – Provides group details
| diff --git a/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_nestedgroups.md b/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_nestedgroups.md index 18651be9c1..68a669b3fc 100644 --- a/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_nestedgroups.md +++ b/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_nestedgroups.md @@ -7,8 +7,8 @@ sidebar_position: 60 # AAD_NestedGroups Job The AAD_NestedGroups Job identifies nested groups within Microsoft Entra ID and provides details -such as the levels of nesting. While Microsoft Entra ID provides the ability to nest certain types -of groups within other groups, Microsoft recommends nesting does not go beyond two levels in order +such as the levels of nesting. While Microsoft Entra ID lets you nest certain types +of groups within other groups, Microsoft recommends nesting doesn't go beyond two levels to avoid difficulties in understanding effective membership and access. ## Analysis Tasks for the AAD_NestedGroups Job @@ -17,7 +17,7 @@ Navigate to the **Jobs** > **Entra ID** > **1.Groups** > **AAD_NestedGroups** > and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_probableowners.md b/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_probableowners.md index 0ee073217e..73a874bef5 100644 --- a/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_probableowners.md +++ b/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_probableowners.md @@ -6,8 +6,8 @@ sidebar_position: 70 # AAD_ProbableOwners Job -The AAD_ProbableOwners Job determines potential owners for Microsoft Entra ID Groups which can be -used to perform automated membership reviews and enable self-service group management and membership +The AAD_ProbableOwners Job determines potential owners for Microsoft Entra ID Groups, which you can +use to perform automated membership reviews and enable self-service group management and membership requests. ## Analysis Tasks for the AAD_ProbableOwners Job @@ -16,7 +16,7 @@ Navigate to the **Jobs** > **Entra ID** > **1.Groups** > **AAD_ProbableOwners** and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_stalegroups.md b/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_stalegroups.md index e79071f708..942d0b04a1 100644 --- a/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_stalegroups.md +++ b/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_stalegroups.md @@ -17,7 +17,7 @@ Navigate to the **Jobs** > **Entra ID** > **1.Groups** > **AAD_StaleGroups** > * and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -38,4 +38,4 @@ following pre-configured report. | Report | Description | Default Tags | Report Elements | | ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Stale Effective Membership (Stale Groups) | This report identifies groups with stale effective membership. A stale user is defined as someone who has not logged into the domain in over 30 days or is currently disabled. | None | This report is comprised of three elements:
  • Chart – Displays group membership
  • Table – Provides group membership details
  • Tables – Provides stale groups organization summary
| +| Stale Effective Membership (Stale Groups) | This report identifies groups with stale effective membership. A stale user is defined as someone who has not logged into the domain in over 30 days or is disabled. | None | This report is comprised of three elements:
  • Chart – Displays group membership
  • Table – Provides group membership details
  • Tables – Provides stale groups organization summary
| diff --git a/docs/accessanalyzer/11.6/solutions/entraid/groups/overview.md b/docs/accessanalyzer/11.6/solutions/entraid/groups/overview.md index 749bbe1ed9..d407b7dc15 100644 --- a/docs/accessanalyzer/11.6/solutions/entraid/groups/overview.md +++ b/docs/accessanalyzer/11.6/solutions/entraid/groups/overview.md @@ -14,8 +14,8 @@ Microsoft Entra ID, such as toxic group conditions or synchronization issues. The jobs in the 1.Groups Job Group are: - [AAD_CircularNesting Job](/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_circularnesting.md) - – Identifies circularly-nested groups within Microsoft Entra ID which can pose administrative and - operational challenges with identifying effective access to resources + – Identifies circularly-nested groups within Microsoft Entra ID. Circular nesting can complicate + determining effective access to resources - [AAD_DuplicateGroups Job](/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_duplicategroups.md) – Identifies duplicate groups within Microsoft Entra ID. Duplicate groups contain the same group membership as one another and are suitable candidates for cleanup @@ -25,18 +25,17 @@ The jobs in the 1.Groups Job Group are: - [AAD_GroupDirSync Job](/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_groupdirsync.md) – Summarizes on-premises Active Directory syncing in the audited Microsoft Entra ID environment - [AAD_LargestGroups Job](/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_largestgroups.md) - – Identifies groups with large effective member counts. These types of groups may cause - administrative overhead and burden in being able to easily understand who is getting access to - resources, or how much access is being granted to resources through these groups. + – Identifies groups with large effective member counts. These types of groups can make it + difficult to determine who has access to resources through them, or how much access they grant - [AAD_NestedGroups Job](/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_nestedgroups.md) – Identifies nested groups within Microsoft Entra ID and provides details such as the levels of - nesting. While Microsoft Entra ID provides the ability to nest certain types of groups within - other groups, Microsoft recommends nesting does not go beyond two levels in order to avoid + nesting. While Microsoft Entra ID lets you nest certain types of groups within + other groups, Microsoft recommends nesting doesn't go beyond two levels to avoid difficulties in understanding effective membership and access. - [AAD_ProbableOwners Job](/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_probableowners.md) - – Determines potential owners for Microsoft Entra ID Groups which can be used to perform automated + – Determines potential owners for Microsoft Entra ID Groups, which you can use to perform automated membership reviews and enable self-service group management and membership requests -- [AAD_StaleGroups Job](/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_stalegroups.md)– +- [AAD_StaleGroups Job](/docs/accessanalyzer/11.6/solutions/entraid/groups/aad_stalegroups.md) – Identifies Microsoft Entra ID groups that contain potentially stale users. Users are considered stale if they have never logged onto the domain, have not logged onto the domain in the past 30 days, or are disabled. These group memberships should be reviewed and possibly removed. diff --git a/docs/accessanalyzer/11.6/solutions/entraid/overview.md b/docs/accessanalyzer/11.6/solutions/entraid/overview.md index f43dd05d9c..e7d8764833 100644 --- a/docs/accessanalyzer/11.6/solutions/entraid/overview.md +++ b/docs/accessanalyzer/11.6/solutions/entraid/overview.md @@ -24,9 +24,9 @@ topic for additional information. **Location** The Entra ID Solution requires a special Enterprise Auditor license. It can be installed from the -Instant Job Wizard, see the +Instant Job Wizard. See the [Instant Job Wizard](/docs/accessanalyzer/11.6/admin/jobs/instantjobs/overview.md) -topic for additional information. Once it has been installed into the Jobs tree, navigate to the +topic for additional information. After it has been installed into the Jobs tree, navigate to the solution: **Jobs** > **Entra ID**. The .Entra ID Inventory Job Group collects the data. The Entra ID Job Groups run analysis and diff --git a/docs/accessanalyzer/11.6/solutions/entraid/recommended.md b/docs/accessanalyzer/11.6/solutions/entraid/recommended.md index 20353edf52..e9d302289b 100644 --- a/docs/accessanalyzer/11.6/solutions/entraid/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/entraid/recommended.md @@ -7,7 +7,7 @@ sidebar_position: 10 # Recommended Configurations for Entra ID Job Group The Entra ID Solution has been configured to inherit down from the job group **Settings** node. The -host list must be assigned and the Connection Profile configured before job execution. Once these +host list must be assigned and the Connection Profile configured before job execution. After these are assigned to the job group, it can be run directly or scheduled. **Dependencies** @@ -21,15 +21,15 @@ topic for additional information. **Targeted Hosts** -The Entra ID Solution does not require a target host because the jobs use data collected from the +The Entra ID Solution doesn't require a target host because the jobs use data collected from the .Entra ID Inventory Job Group and the .Active Directory Inventory Job Group. However, Enterprise -Auditor jobs do not execute successfully without a host list assigned. Assign the host list under +Auditor jobs don't execute successfully without a host list assigned. Assign the host list under the **Entra ID** > **Settings** > **Host Lists Assignment** node. Check the **Local host** box and click **Save**. **Connection Profile** -Since the Entra ID Solution is not collecting any data, a specific connection profile is not +Since the Entra ID Solution isn't collecting any data, a specific connection profile isn't necessary. Therefore, the default setting **Use the Default Profile** is sufficient for this solution. @@ -52,7 +52,7 @@ topic for additional information. The following is the recommended workflow: -**Step 1 –** Assign the Local host at the solution level as described above. +**Step 1 –** Assign the Local host at the solution level, as described in Targeted Hosts. **Step 2 –** Run the .Entra ID Inventory Job Group. If on-premises directory syncing information is desired, run the .Active Directory Inventory Job Group. diff --git a/docs/accessanalyzer/11.6/solutions/entraid/users/aad_directmembership.md b/docs/accessanalyzer/11.6/solutions/entraid/users/aad_directmembership.md index 8b8cb38e43..f363306468 100644 --- a/docs/accessanalyzer/11.6/solutions/entraid/users/aad_directmembership.md +++ b/docs/accessanalyzer/11.6/solutions/entraid/users/aad_directmembership.md @@ -6,7 +6,7 @@ sidebar_position: 10 # AAD_DirectMembership Job -The AAD_DirectMembership Job identifies Microsoft Entra ID users who do not have any group +The AAD_DirectMembership Job identifies Microsoft Entra ID users who don't have any group membership. This condition may indicate unnecessary user accounts that are suitable candidates for review and cleanup. @@ -16,7 +16,7 @@ Navigate to the **Jobs** > **Entra ID** > **2.Users** > **AAD_DirectMembership** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/entraid/users/aad_disabledusers.md b/docs/accessanalyzer/11.6/solutions/entraid/users/aad_disabledusers.md index 3da8d26813..7becbd24d6 100644 --- a/docs/accessanalyzer/11.6/solutions/entraid/users/aad_disabledusers.md +++ b/docs/accessanalyzer/11.6/solutions/entraid/users/aad_disabledusers.md @@ -7,7 +7,7 @@ sidebar_position: 20 # AAD_DisabledUsers Job The AAD_DisabledUsers Job identifies disabled user accounts within Microsoft Entra ID. These -accounts should be reviewed and cleaned up in order to increase security and reduce complexity. +accounts should be reviewed and cleaned up to increase security and reduce complexity. ## Analysis Tasks for the AAD_DisabledUsers Job @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **Entra ID** > **2.Users** > **AAD_DisabledUsers** > and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/entraid/users/aad_staleusers.md b/docs/accessanalyzer/11.6/solutions/entraid/users/aad_staleusers.md index 5b2fd6179d..68f8f3e954 100644 --- a/docs/accessanalyzer/11.6/solutions/entraid/users/aad_staleusers.md +++ b/docs/accessanalyzer/11.6/solutions/entraid/users/aad_staleusers.md @@ -7,7 +7,7 @@ sidebar_position: 30 # AAD_StaleUsers Job The AAD_StaleUsers Job identifies potentially stale users based on a variety of factors. These -accounts should be reviewed and cleaned up in order to increase security and reduce complexity. +accounts should be reviewed and cleaned up to increase security and reduce complexity. ## Analysis Tasks for the AAD_StaleUsers Job @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **Entra ID** > **2.Users** > **AAD_StaleUsers** > **C select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -34,4 +34,4 @@ following pre-configured report. | Report | Description | Default Tags | Report Elements | | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Stale Users | This report identifies user accounts which have not logged into the domain for an extended amount of time or are currently disabled. A user account is considered stale if the last logon is over 30 days ago or is currently disabled. | None | This report is comprised of three elements:
  • Stacked Bar Chart – Displays users by domain
  • Table – Provides details on users
  • Tables – Provides details on users by domain
| +| Stale Users | This report identifies user accounts which have not logged into the domain for an extended amount of time or are disabled. A user account is considered stale if the last logon is over 30 days ago or is disabled. | None | This report is comprised of three elements:
  • Stacked Bar Chart – Displays users by domain
  • Table – Provides details on users
  • Tables – Provides details on users by domain
| diff --git a/docs/accessanalyzer/11.6/solutions/entraid/users/aad_userattributecompletion.md b/docs/accessanalyzer/11.6/solutions/entraid/users/aad_userattributecompletion.md index 444750d458..fd2ea103da 100644 --- a/docs/accessanalyzer/11.6/solutions/entraid/users/aad_userattributecompletion.md +++ b/docs/accessanalyzer/11.6/solutions/entraid/users/aad_userattributecompletion.md @@ -16,7 +16,7 @@ Navigate to the **Jobs** > **Entra ID** > **2.Users** > **AAD_UserAttributeCompl **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -35,4 +35,4 @@ produces the following pre-configured report. | Report | Description | Default Tags | Report Elements | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| User Attribute Completion | This report identifies which attributes are present within User fields in Microsoft Entra ID, and which ones are blank for a majority of User objects. | None | This report is comprised of three elements:
  • Stacked Bar Chart – Displays completeness by attribute
  • Table – Provides details on users with blank attributes
  • Tables – Provides details om completeness by attribute
| +| User Attribute Completion | This report identifies which attributes are present within User fields in Microsoft Entra ID, and which ones are blank for a majority of User objects. | None | This report is comprised of three elements:
  • Stacked Bar Chart – Displays completeness by attribute
  • Table – Provides details on users with blank attributes
  • Tables – Provides details on completeness by attribute
| diff --git a/docs/accessanalyzer/11.6/solutions/entraid/users/aad_userdirsync.md b/docs/accessanalyzer/11.6/solutions/entraid/users/aad_userdirsync.md index cc2eccee6e..fc038d4c2e 100644 --- a/docs/accessanalyzer/11.6/solutions/entraid/users/aad_userdirsync.md +++ b/docs/accessanalyzer/11.6/solutions/entraid/users/aad_userdirsync.md @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **Entra ID** > **2.Users** > **AAD_UserDirSync** > ** select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/entraid/users/overview.md b/docs/accessanalyzer/11.6/solutions/entraid/users/overview.md index 29a98f8af4..850c5e026e 100644 --- a/docs/accessanalyzer/11.6/solutions/entraid/users/overview.md +++ b/docs/accessanalyzer/11.6/solutions/entraid/users/overview.md @@ -14,15 +14,15 @@ administrative concerns within Microsoft Entra ID such as disabled or stale user The jobs in the 2.Users Job Group are: - [AAD_DirectMembership Job](/docs/accessanalyzer/11.6/solutions/entraid/users/aad_directmembership.md) - – Identifies Microsoft Entra ID users who do not have any group membership. This condition may + – Identifies Microsoft Entra ID users who don't have any group membership. This condition may indicate unnecessary user accounts that are suitable candidates for review and cleanup. - [AAD_DisabledUsers Job](/docs/accessanalyzer/11.6/solutions/entraid/users/aad_disabledusers.md) – Identifies disabled user accounts within Microsoft Entra ID. These accounts should be reviewed - and cleaned up in order to increase security and reduce complexity. -- [AAD_StaleUsers Job](/docs/accessanalyzer/11.6/solutions/entraid/users/aad_staleusers.md)– + and cleaned up to increase security and reduce complexity. +- [AAD_StaleUsers Job](/docs/accessanalyzer/11.6/solutions/entraid/users/aad_staleusers.md) – Identifies potentially stale users based on a variety of factors. These accounts should be - reviewed and cleaned up in order to increase security and reduce complexity. -- [AAD_UserAttributeCompletion Job](/docs/accessanalyzer/11.6/solutions/entraid/users/aad_userattributecompletion.md)– + reviewed and cleaned up to increase security and reduce complexity. +- [AAD_UserAttributeCompletion Job](/docs/accessanalyzer/11.6/solutions/entraid/users/aad_userattributecompletion.md) – Identifies which attributes are present within User fields in Microsoft Entra ID, and which ones are blank for a majority of objects. This may indicate accounts within Microsoft Entra ID which are lacking appropriate information. diff --git a/docs/accessanalyzer/11.6/solutions/entraidinventory/1-aad_scan.md b/docs/accessanalyzer/11.6/solutions/entraidinventory/1-aad_scan.md index ddc228ebbe..7327ea3d1f 100644 --- a/docs/accessanalyzer/11.6/solutions/entraidinventory/1-aad_scan.md +++ b/docs/accessanalyzer/11.6/solutions/entraidinventory/1-aad_scan.md @@ -6,9 +6,9 @@ sidebar_position: 20 # 1-AAD_Scan Job -The **1-AAD_Scan** Job is responsible for collecting data from Microsoft Entra ID. This job requires -no additional customizations before being used, but can be scoped to disable collecting sign-in -activity with the scan. +The **1-AAD_Scan** Job collects data from Microsoft Entra ID. It requires no additional +customization before use, but you can scope it to disable collecting sign-in activity with the +scan. ## Queries for the 1-AAD_Scan Job @@ -18,20 +18,20 @@ The 1-AAD_Scan job uses the AzureADInventory Data Collector for the following qu - AAD Inventory – Targets Microsoft Entra tenants to collect inventory data for user group objects - _(Optional)_ This query can be modified to specify scan options and to collect custom - attributes. See the [Configure the 1-AAD_Scan Query](#configure-the-1-aad_scan-query) topic + attributes. See the [Configure the 1-AAD_Scan Query](#configure-the-1-aadscan-query) topic for additional information. ### Configure the 1-AAD_Scan Query The 1-AAD_Scan Job is configured to run with the default settings with the category of Scan Entra -ID. Follow the steps to customize configurations. +ID. To customize configurations: **Step 1 –** Navigate to the **.Entra ID Inventory** > **1-AAD_Scan** > **Configure** node and select **Queries**. ![Query Properties button on Query Selection page](/images/accessanalyzer/11.6/solutions/entraidinventory/scanqueryselectionproperties.webp) -**Step 2 –** In the Query Selection view, click on **Query Properties** to open the Query Properties +**Step 2 –** In the Query Selection view, click **Query Properties** to open the Query Properties window. ![Query Properties window](/images/accessanalyzer/11.6/solutions/entraidinventory/scanqueryproperties.webp) @@ -84,7 +84,7 @@ Navigate to the **.Entra ID Inventory** > **1-AAD_Scan** > **Configure** node an **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/entraidinventory/2-aad_exceptions.md b/docs/accessanalyzer/11.6/solutions/entraidinventory/2-aad_exceptions.md index f0815577ae..176f3708b8 100644 --- a/docs/accessanalyzer/11.6/solutions/entraidinventory/2-aad_exceptions.md +++ b/docs/accessanalyzer/11.6/solutions/entraidinventory/2-aad_exceptions.md @@ -12,13 +12,12 @@ leave environments at risk or add unnecessary administrative overhead. ## Analysis Tasks for the 2-AAD_Exceptions Job Navigate to the **.Entra ID Inventory** > **2-AAD_Exceptions** > **Configure** node and select -**Analysis**. Analysis tasks with configuration parameters that define security concerns can be -modified. +**Analysis**. You can modify analysis tasks with configuration parameters that define security +concerns. :::warning -Most of these analysis tasks are preconfigured and should not be modified and not be -deselected. There are a few which are deselected by default, as they are for troubleshooting -purposes. +Most of these analysis tasks are preconfigured. Don't modify or deselect them. A few +are deselected by default because they're for troubleshooting. ::: @@ -80,7 +79,7 @@ The default values for parameters that can be customized are: | Stale Membership | @STALE_THRESHOLD | 10 | A group where 10% of its effective members are stale users | See the -[Configure the Analysis Tasks for the 2-AAD_Exceptions Job](#configure-the-analysis-tasks-for-the-2-aad_exceptions-job) +[Configure the Analysis Tasks for the 2-AAD_Exceptions Job](#configure-the-analysis-tasks-for-the-2-aadexceptions-job) section for instructions to modify parameters. See the [AzureADInventory Exception Types Translated](/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/standardtables.md#azureadinventory-exception-types-translated) topic for an explanation of Exception Types. @@ -88,9 +87,9 @@ topic for an explanation of Exception Types. ### Configure the Analysis Tasks for the 2-AAD_Exceptions Job Customizable parameters enable Enterprise Auditor users to set the values used to classify user and -group objects during this job’s analysis. The parameters can be customized and are listed in a -section at the bottom of the SQL Script Editor. Follow the steps to customize an analysis task’s -parameters. +group objects during this job’s analysis. You can customize the parameters, which are listed in a +section at the bottom of the SQL Script Editor. To customize an analysis task’s +parameters: :::warning Modifying these parameters affects solutions with .Entra ID Inventory Job Group @@ -113,7 +112,7 @@ Configuration**. The SQL Script Editor opens. **Step 4 –** Double-click in a field in the Value column and enter a custom value. :::warning -Do not change any parameters where the Value states **Created during execution**. +Don't change any parameters where the Value states **Created during execution**. ::: diff --git a/docs/accessanalyzer/11.6/solutions/entraidinventory/overview.md b/docs/accessanalyzer/11.6/solutions/entraidinventory/overview.md index 0dd2413983..d39d3efda1 100644 --- a/docs/accessanalyzer/11.6/solutions/entraidinventory/overview.md +++ b/docs/accessanalyzer/11.6/solutions/entraidinventory/overview.md @@ -30,7 +30,7 @@ The .Entra ID Inventory Solution is a core component of all Enterprise Auditor be installed from the Enterprise Auditor Instant Job Wizard. See the [Instant Job Wizard](/docs/accessanalyzer/11.6/admin/jobs/instantjobs/overview.md) topic for additional information. Navigate to the solution by expanding the Jobs tree and selecting -the **.Entra ID Inventory** Job Group. This group has been named in such a way to keep it at the top +the **.Entra ID Inventory** Job Group. This group's name keeps it at the top of the Jobs tree. ## Jobs diff --git a/docs/accessanalyzer/11.6/solutions/entraidinventory/recommended.md b/docs/accessanalyzer/11.6/solutions/entraidinventory/recommended.md index 5d5ad062d9..9f32d4998e 100644 --- a/docs/accessanalyzer/11.6/solutions/entraidinventory/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/entraidinventory/recommended.md @@ -7,12 +7,12 @@ sidebar_position: 10 # Recommended Configurations for the .Entra ID Inventory Job Group The .Entra ID Inventory Solution is configured to inherit settings from the Global Settings node. -The host list and connection profile must be assigned before job execution. Once these are assigned +The host list and connection profile must be assigned before job execution. After these are assigned to the job group, it can be run directly or scheduled. **Dependencies** -This job group does not have dependencies. +This job group doesn't have dependencies. **Targeted Hosts** @@ -22,7 +22,7 @@ All Microsoft Entra Tenants. The Connection Profile is assigned under **.Entra ID Inventory** > **Settings** > **Connection**. It is set to **Use the Default Profile**, as configured at the global **Settings** level. However, if -this is not the Connection Profile with the necessary permissions for targeting the Microsoft Entra +this isn't the Connection Profile with the necessary permissions for targeting the Microsoft Entra tenants, select the **Select one of the following user defined profiles** option and select the appropriate Connection Profile. See the [Microsoft Entra ID Connection Profile & Host List](/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/configurejob.md) @@ -40,27 +40,27 @@ Not supported. :::info Schedule the .Entra ID Inventory job group to run once a day. If there are -frequent Microsoft Entra ID changes within the target environment, then it can be executed more +frequent Microsoft Entra ID changes within the target environment, run it more often. It is best to rerun it anytime Entra ID changes might have occurred. ::: **Run at the Solution Level** -The jobs in the .Entra ID Inventory Job Group should be run together and in order by running the -entire solution, instead of the individual jobs. +Run the jobs in the .Entra ID Inventory Job Group together and in order by running the +entire solution, instead of running the individual jobs. **Query Configuration** -Run the solution with the default query configuration for best results. While it is recommended to -make no changes to the +Run the solution with the default query configuration for best results. Although you typically +don't need to change the [1-AAD_Scan Job](/docs/accessanalyzer/11.6/solutions/entraidinventory/1-aad_scan.md), -a possible modification might be to scope the query to not collect login activity. +you can scope the query to skip collecting login activity. **Analysis Configuration** -Run the solution with the default analysis configuration for best results. However, a possible -modification might be to customize exception analysis parameters within the +Run the solution with the default analysis configuration for best results. However, you can +customize exception analysis parameters in the [2-AAD_Exceptions Job](/docs/accessanalyzer/11.6/solutions/entraidinventory/2-aad_exceptions.md). **Workflow** diff --git a/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/ex_activesync.md b/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/ex_activesync.md index 6fb38e6301..05fd7e53bf 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/ex_activesync.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/ex_activesync.md @@ -18,7 +18,7 @@ View the analysis tasks by navigating to the **Exchange** > **2. CAS Metrics** > **EX_ActiveSync** > **Configure** node and select **Analysis**. :::warning -Most of these analysis tasks are preconfigured and should not be modified or +Most of these analysis tasks are preconfigured and shouldn't be modified or deselected. There are some that are deselected by default, as they are for troubleshooting purposes. ::: @@ -50,7 +50,7 @@ The following analysis task deletes table data from the analysis jobs. This anal remain cleared unless specifically needed: :::warning -Do not select the **00. Deletes all History** option. This analysis task is for +Don't select the **00. Deletes all History** option. This analysis task is for troubleshooting and cleanup only. Data will be deleted from the database. ::: @@ -61,8 +61,8 @@ troubleshooting and cleanup only. Data will be deleted from the database. [Troubleshooting Data Collection](/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/collection/ex_metricscollection.md#troubleshooting-data-collection) topic for additional information -The following analysis task updates the table to clean the data so that any UserAgent information -that is returned as NULL is updated based on existing data in the table: +The following analysis task cleans the table by updating any UserAgent information returned as +NULL, based on existing data in the table: - 01a. Clean NULL UserAgent – Updates UserAgent information which was returned as NULL based on existing data @@ -72,7 +72,7 @@ the following pre-configured reports: | Report | Description | Default Tags | Report Elements | | ----------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Device Types (Device Population) | This report identifies what device models are currently being used with ActiveSync, and the average load they put on the environment each day. | None | This report is comprised of two elements:
  • Bar Chart – Displays most popular devices
  • Table – Provides details on most popular devices
| +| Device Types (Device Population) | This report identifies what device models are being used with ActiveSync, and the average load they put on the environment each day. | None | This report is comprised of two elements:
  • Bar Chart – Displays most popular devices
  • Table – Provides details on most popular devices
| | Server Traffic (Top Servers by Average Daily Traffic) | This report ranks CAS servers by volume of ActiveSync traffic. | None | This report is comprised of two elements:
  • Bar Chart – Displays top users by average daily traffic
  • Table – Provides details on top users by average daily traffic
| | Top Users (Top Users by Average Daily Traffic) | This report shows the top users of ActiveSync. | None | This report is comprised of two elements:
  • Bar Chart – Displays top users by average daily traffic
  • Table – Provides details on top users by average daily traffic
| | User Devices (User Phones) | This report identifies all devices which have been associated with a User, and the time frames when they were used. | None | This report is comprised of one element:
  • Table – Provides details on user devices
| diff --git a/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/ex_aspolicies.md b/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/ex_aspolicies.md index d4446fb747..20513ae62a 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/ex_aspolicies.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/ex_aspolicies.md @@ -26,7 +26,7 @@ The following query is included in the EX_ASPolicies Job. The ExchangePS Data Collector can be scoped if desired. -Follow the steps to scope the ExchangePS Data Collector: +To scope the ExchangePS Data Collector: **Step 1 –** Navigate to job’s **Configure** node and select **Queries**. @@ -37,29 +37,29 @@ Properties**. The Query Properties window opens. Wizard opens. :::warning -Do not modify other wizard pages. The wizard pages are pre-configured for this job. +Don't modify other wizard pages. The wizard pages are pre-configured for this job. ::: ![ExchangePS Data Collector Wizard Scope page](/images/activitymonitor/7.1/config/activedirectory/scope.webp) -**Step 4 –** Navigate to the Scope page, and select the desired scoping method from those available. +**Step 4 –** Navigate to the Scope page, and select the scoping method you want from those available. See the [ExchangePS: Scope](/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scope.md) topic for additional information. - Scope by Database – Select the **Scope by Database Target Host: Local Host** option. Then, click - **Next** and identify the desired databases on the Scope by Databases page. See the + **Next** and identify the databases you want on the Scope by Databases page. See the [ExchangePS: Scope by DB](/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scopedatabases.md) topic for additional information. - Scope by Mailbox – Select the **Scope by Mailbox Target Host: Local Host** option. Then, click - **Next** and identify the desired mailboxes on the Scope by Mailboxes page. See the + **Next** and identify the mailboxes you want on the Scope by Mailboxes page. See the [ExchangePS: Scope by Mailboxes](/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scopemailboxes.md) topic for additional information. - Scope by Server – Select the **Scope by Server Target Host: Exchange MB Server** option. The job returns results for specific servers selected in job’s **Configure** > **Hosts** node. - Scope by Public Folder – Select the **Scope by Public Folder** option. Then, click **Next** and - identify the desired mailboxes on the Scope by Public Folders page. See the + identify the mailboxes you want on the Scope by Public Folders page. See the [ExchangePS: Scope by Public Folders](/docs/accessanalyzer/11.6/admin/datacollector/exchangeps/scopepublicfolders.md) topic for additional information. - _Remember,_ the scoping options available vary based on the pre-defined query configurations. @@ -74,7 +74,7 @@ View the analysis tasks by navigating to the **Exchange** > **2. CAS Metrics** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: @@ -90,4 +90,4 @@ following pre-configured report: | Report | Description | Default Tags | Report Elements | | ---------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- | -| User ActiveSync Policies (ActiveSync Settings) | Exchange introduced many ActiveSync policies and settings which can be applied to users. This report identifies which users have these settings enabled. | None | This report is comprised of two elements:
  • Pie Chart – Displays ActiveSync Policies
  • Table – Provides details ActiveSync Policies
| +| User ActiveSync Policies (ActiveSync Settings) | Exchange introduced many ActiveSync policies and settings which can be applied to users. This report identifies which users have these settings enabled. | None | This report is comprised of two elements:
  • Pie Chart – Displays ActiveSync Policies
  • Table – Provides details on ActiveSync Policies
| diff --git a/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/ex_iislogs.md b/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/ex_iislogs.md index 16b4215f88..f0bac44d34 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/ex_iislogs.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/ex_iislogs.md @@ -6,9 +6,9 @@ sidebar_position: 20 # 0.Collection > EX_IISLogs Job -The 0.Collection > EX_IISLogs Job provides data collection to be utilized in the ActiveSync, Outlook -Web Access, and Outlook Anywhere Reports. This job goes out to each server that contains the -IIS Logs and parses the log to return the data to the Enterprise Auditor database. +The 0.Collection > EX_IISLogs Job collects data for the ActiveSync, Outlook Web Access, and +Outlook Anywhere reports. This job connects to each server that contains the IIS logs and parses +the log to return the data to the Enterprise Auditor database. ![0.Collection > EX_IISLogs Job in the Jobs Tree](/images/accessanalyzer/11.6/solutions/exchange/casmetrics/collectionjobstree.webp) @@ -36,7 +36,7 @@ modified on the Target Log page of the SMART Log DC Wizard. See the [SMARTLog Data Collector](/docs/accessanalyzer/11.6/admin/datacollector/smartlog/overview.md) topic for additional information. -Follow the steps to modify the query configuration. +To modify the query configuration: **Step 1 –** Navigate to the **Exchange** > **2. CAS Metrics** > **0. Collection** > **EX_IISLogs** > **Configure** node and select **Queries**. @@ -47,7 +47,7 @@ opens. **Step 3 –** Select the **Data Source** tab, and click **Configure**. The SMART Log DC Wizard opens. :::warning -Do not modify other wizard pages. The other wizard pages are pre-configured for this +Don't modify other wizard pages. The other wizard pages are pre-configured for this job. ::: @@ -59,8 +59,8 @@ job. topic for additional information. :::tip -Remember, if the date range configuration includes data older than the last scan, the **Persist -Log State** checkbox on the Log State page must be disabled. +Remember, if the date range configuration includes data older than the last scan, disable the +**Persist Log State** checkbox on the Log State page. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/ex_owatraffic.md b/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/ex_owatraffic.md index 3a922aa2ed..d50cc61870 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/ex_owatraffic.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/ex_owatraffic.md @@ -18,7 +18,7 @@ View the analysis tasks by navigating to the **Exchange** > **2. CAS Metrics** > Access** > **EX_OWATraffic** > **Configure** node and select **Analysis**. :::warning -Most of these analysis tasks are preconfigured and should not be modified ordeselected. +Most of these analysis tasks are preconfigured and shouldn't be modified or deselected. There is one that is deselected by default, as it is for troubleshooting purposes. ::: @@ -46,7 +46,7 @@ The following analysis task deletes table data from data collection and analysis task should remain cleared unless specifically needed: :::warning -Do not select the **00. Delete all History** option. This analysis task is for +Don't select the **00. Delete all History** option. This analysis task is for troubleshooting and cleanup only. Data will be deleted from the database. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/ex_rpctraffic.md b/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/ex_rpctraffic.md index 945b879f15..541f30f009 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/ex_rpctraffic.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/ex_rpctraffic.md @@ -19,7 +19,7 @@ View the analysis tasks by navigating to the **Exchange** > **2. CAS Metrics** > Anywhere** > **EX_RPCTraffic** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -43,11 +43,11 @@ The following analysis tasks are selected by default: [Exchange History Retention](/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/collection/ex_metricscollection.md#exchange-history-retention) topic for additional information -The following analysis tasks deletes table data from data collection and analysis jobs. These +The following analysis tasks delete table data from data collection and analysis jobs. These analysis tasks should remain cleared unless specifically needed: :::warning -Do not select the **00. Delete all History** option. This analysis task is for +Don't select the **00. Delete all History** option. This analysis task is for troubleshooting and cleanup only. Data will be deleted from the database. ::: @@ -63,5 +63,5 @@ the following pre-configured reports: | Report | Description | Default Tags | Report Elements | | ---------------------------------------------------------------------- | -------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Top Servers by Average Load ( Top Servers by Average Daily User Count) | This report shows servers with the highest average load. | None | This report is comprised of two elements:
  • Stacked Bar Chart – Displays top servers by average daily user count
  • Table – Provides details on top servers by average daily user count
| +| Top Servers by Average Load (Top Servers by Average Daily User Count) | This report shows servers with the highest average load. | None | This report is comprised of two elements:
  • Stacked Bar Chart – Displays top servers by average daily user count
  • Table – Provides details on top servers by average daily user count
| | Top Users (Outlook Anywhere Traffic) | This report identifies top users of Outlook Anywhere. | None | This report is comprised of two elements:
  • Bar Chart – Displays top users
  • Table – Provides details on top users
| diff --git a/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/overview.md b/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/overview.md index 91bb043de5..9abcef75a3 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/overview.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/overview.md @@ -6,7 +6,7 @@ sidebar_position: 30 # 2.CAS Metrics Job Group -The 2. CAS Metrics Job Group is comprised of data collection, analysis and reports that focus on +The 2. CAS Metrics Job Group is comprised of data collection, analysis, and reports that focus on remote connections (Outlook Web Access, ActiveSync, and Outlook Anywhere Access) occurring within your organization. This job group goes out to each server that contains the IIS Logs and parses the logs to return the data to the Enterprise Auditor database. @@ -16,7 +16,7 @@ logs to return the data to the Enterprise Auditor database. The jobs in the 2.CAS Metrics Job Group are: - [0.Collection > EX_IISLogs Job](/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/ex_iislogs.md) - – Provides data collection to be utilized in the ActiveSync, Outlook Web Access, and Outlook + – Provides data collection to be used in the ActiveSync, Outlook Web Access, and Outlook Anywhere Reports. This job group goes out to each server that contains the IIS Logs and parses the logs to return the data to the Enterprise Auditor database. - [ActiveSync > EX_ActiveSync Job](/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/ex_activesync.md) @@ -31,7 +31,7 @@ The jobs in the 2.CAS Metrics Job Group are: :::note An actual CAS name is required for the data collection. When targeting Exchange 2013 - or 2016, it is possible for the **Settings** > **Exchange** node to have been configured with a + or 2016, the **Settings** > **Exchange** node might be configured with a web address instead of an actual server. See the [ExchangePS Data Collector & Client Access Server](/docs/accessanalyzer/11.6/solutions/exchange/recommended.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/recommended.md b/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/recommended.md index 2ee3077ce0..5767bf70f6 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/recommended.md @@ -61,7 +61,7 @@ Run this Job Group at 2:00 AM. **History Retention** -History retention should not be enabled on this job group. History is kept through analysis tasks. +History retention shouldn't be enabled on this job group. History is kept through analysis tasks. Modify the following analysis tasks to customize the amount of history which is kept. | Job Name | Analysis Task Name | Default History | @@ -85,12 +85,12 @@ No other queries should be modified. The 2. CAS Metrics Job Group should be run with the default analysis configurations. :::warning -Most of these analysis tasks are preconfigured and should not be modified or +Most of these analysis tasks are preconfigured and shouldn't be modified or deselected. There are some that are deselected by default, as they are for troubleshooting purposes. ::: -The following analysis tasks should not be deselected, but their parameters can be modified: +The following analysis tasks shouldn't be deselected, but their parameters can be modified: - **ActiveSync** > **EX_ActiveSync** Job – **07. SET HISTORY RETENTION** Analysis Task - **Outlook Anywhere** > **EX_RPCTraffic** Job – **05. SET HISTORY RETENTION** Analysis Task diff --git a/docs/accessanalyzer/11.6/solutions/exchange/databases/collection/ex_dbinfo.md b/docs/accessanalyzer/11.6/solutions/exchange/databases/collection/ex_dbinfo.md index 1ff643548a..8cf2746a44 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/databases/collection/ex_dbinfo.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/databases/collection/ex_dbinfo.md @@ -6,7 +6,7 @@ sidebar_position: 10 # 1.Local > EX_DBInfo Job -The EX_DBInfo job utilizes Exchange PowerShell to gather 2010/2013 Mailbox Size information. +The EX_DBInfo job uses Exchange PowerShell to gather 2010/2013 Mailbox Size information. ![1.Local > EX_DBInfo Job in the Jobs Tree](/images/accessanalyzer/11.6/solutions/exchange/databases/collection/localjobstree.webp) @@ -14,7 +14,7 @@ The EX_DBInfo job is located in the 1.Local job group. :::note An actual CAS name is required for the data collection. When targeting Exchange 2013 or -2016, it is possible for the **Settings** > **Exchange** node to have been configured with a web +2016, the **Settings** > **Exchange** node might be configured with a web address instead of an actual server. See the [ExchangePS Data Collector & Client Access Server](/docs/accessanalyzer/11.6/solutions/exchange/recommended.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/solutions/exchange/databases/collection/ex_pfinfo.md b/docs/accessanalyzer/11.6/solutions/exchange/databases/collection/ex_pfinfo.md index cfca53b3ef..025321f022 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/databases/collection/ex_pfinfo.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/databases/collection/ex_pfinfo.md @@ -6,7 +6,7 @@ sidebar_position: 20 # 2.PF > EX_PFInfo Job -The EX_PFInfo job utilizes MAPI to gather Public Folder Database Information focusing on database +The EX_PFInfo job uses MAPI to gather Public Folder Database Information focusing on database sizing, growth, and trends. ![2.PF > EX_PFInfo Job in the Jobs Tree](/images/accessanalyzer/11.6/solutions/exchange/databases/collection/pfjobstree.webp) @@ -18,7 +18,7 @@ The EX_PFInfo job is located in the 2.PF job group. The EX_PFInfo Job uses the Exchange2K Data Collector for the query. :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/databases/collection/overview.md b/docs/accessanalyzer/11.6/solutions/exchange/databases/collection/overview.md index 66517886a3..9ea41d4140 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/databases/collection/overview.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/databases/collection/overview.md @@ -14,7 +14,7 @@ database sizing, growth, and trends. The jobs in the 0.Collection Job Group are: - [1.Local > EX_DBInfo Job](/docs/accessanalyzer/11.6/solutions/exchange/databases/collection/ex_dbinfo.md) - – Utilizes Exchange PowerShell to gather 2010/2013 Mailbox Size Information + – uses Exchange PowerShell to gather 2010/2013 Mailbox Size Information - [2.PF > EX_PFInfo Job](/docs/accessanalyzer/11.6/solutions/exchange/databases/collection/ex_pfinfo.md) - – Utilizes MAPI to gather Public Folder Database Information focusing on database sizing, growth, + – uses MAPI to gather Public Folder Database Information focusing on database sizing, growth, and trends diff --git a/docs/accessanalyzer/11.6/solutions/exchange/databases/ex_dbsizing.md b/docs/accessanalyzer/11.6/solutions/exchange/databases/ex_dbsizing.md index bc1f4d95d3..1d878ff9c4 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/databases/ex_dbsizing.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/databases/ex_dbsizing.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **Exchange** > **3. Databases** > * **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -44,7 +44,7 @@ The following analysis task deletes table data from data collection and analysis task should remain cleared unless specifically needed: :::warning -Do not select the **00. Deletes all Stored Data** option. This analysis task is for +Don't select the **00. Deletes all Stored Data** option. This analysis task is for troubleshooting and cleanup only. Data will be deleted from the database. ::: @@ -60,7 +60,7 @@ following pre-configured reports: | Report | Description | Default Tags | Report Elements | | ---------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Database Details (Storage Group Details) | This report provides the details of Mailbox Stores grouped by Server, then Storage Group. This report helps administrators locate Storage Groups that may be growing out of control. If a storage group with very few users is extremely large, further investigation may be required. | None | This report is comprised of two elements:
  • Bar Chart – Displays database sizes
  • Table – Provides details on database sizes
| +| Database Details (Storage Group Details) | This report provides the details of Mailbox Stores grouped by Server, then Storage Group. This report helps administrators locate Storage Groups that may be growing out of control. If a storage group with very few users is extremely large, investigate further. | None | This report is comprised of two elements:
  • Bar Chart – Displays database sizes
  • Table – Provides details on database sizes
| | Database Growth Statistics | This report displays the top 10 Databases that grew over the last 30 days in pure MB. This report is filtered on the Rank Column for Top 10 and may be modified to fit any desired Top outcome. | None | This report is comprised of four elements:
  • Stacked Bar Chart – Displays store size growth
  • Stacked Bar Chart – Displays WhiteSpace growth
  • Table – Provides details on store size growth
  • Table – Provides details on WhiteSpace growth
| | Historical Database Information | This report shows the history of the store size, white space, mailbox count, and hard drive space on all targeted servers. | None | This report is comprised of one element:
  • Table – Displays details on historical store information
| -| Mailbox Counts by Database | This report graphically displays the number of Mailboxes by Database.  It provides an overall picture of the Exchange Mailbox Environment. Having a clear break down of the number of mailboxes per database allows for better planning of architecture in the future. | None | This report is comprised of two elements:
  • Bar Chart – Displays mailbox counts by database
  • Table – Provides details on mailbox counts by database
| +| Mailbox Counts by Database | This report graphically displays the number of Mailboxes by Database. It provides an overall picture of the Exchange Mailbox Environment. A clear breakdown of the number of mailboxes per database helps you plan future architecture. | None | This report is comprised of two elements:
  • Bar Chart – Displays mailbox counts by database
  • Table – Provides details on mailbox counts by database
| diff --git a/docs/accessanalyzer/11.6/solutions/exchange/databases/ex_dbtrending.md b/docs/accessanalyzer/11.6/solutions/exchange/databases/ex_dbtrending.md index 6b10a4cb67..daf3a01e77 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/databases/ex_dbtrending.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/databases/ex_dbtrending.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **Exchange** > **3. Databases** > * **Configure** node and selecting **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -39,4 +39,4 @@ the following pre-configured report: | Report | Description | Default Tags | Report Elements | | --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Capacity Planning
  • Databases
| This report displays the growth rate trend of your private stores and the growth rate trend of your public stores.  The trend is projected for two months. These reports help identify bad trends in growth on Exchange servers for hard drive space usage is key in avoiding running out of space. | None | This report is comprised of two elements:
  • Line Chart – Displays private store trend
  • Line Chart – Displays public store trend
| +| Capacity Planning
  • Databases
| This report displays the growth rate trend of your private stores and the growth rate trend of your public stores. The trend is projected for two months. These reports help identify bad trends in growth on Exchange servers for hard drive space usage is key in avoiding running out of space. | None | This report is comprised of two elements:
  • Line Chart – Displays private store trend
  • Line Chart – Displays public store trend
| diff --git a/docs/accessanalyzer/11.6/solutions/exchange/databases/recommended.md b/docs/accessanalyzer/11.6/solutions/exchange/databases/recommended.md index acfc42255c..5c76dc98f2 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/databases/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/databases/recommended.md @@ -57,7 +57,7 @@ Run this Job Group at 3:00 AM. **History Retention** -History retention should not be enabled on this job group. History is kept through analysis tasks. +History retention shouldn't be enabled on this job group. History is kept through analysis tasks. Modify the following analysis tasks to customize the amount of history which is kept: | Job Name | Analysis Task Name | Default History | @@ -83,7 +83,7 @@ deselected. There are some that are deselected by default, as they are for troub ::: -The following analysis task should not be deselected, but the parameters can be modified: +The following analysis task shouldn't be deselected, but the parameters can be modified: - **EX_DBSizing** Job – **SET HISTORY RETENTION** Analysis Task diff --git a/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/ex_dlcleanup.md b/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/ex_dlcleanup.md index b8edc85f6f..c08287b872 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/ex_dlcleanup.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/ex_dlcleanup.md @@ -16,7 +16,7 @@ View the analysis task by navigating to the **Exchange** > **6. Distribution Lis **EX_DLCleanup** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/ex_groupexpansion.md b/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/ex_groupexpansion.md index cf3e7bc3bd..52bd5e617f 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/ex_groupexpansion.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/ex_groupexpansion.md @@ -18,7 +18,7 @@ View the analysis tasks by navigating to the **Exchange** > **6. Distribution Li Membership** > **EX_GroupExpansion** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/membershipanalysis/ex_circularnesting.md b/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/membershipanalysis/ex_circularnesting.md index 4fb40fc459..38da3c242c 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/membershipanalysis/ex_circularnesting.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/membershipanalysis/ex_circularnesting.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **Exchange** > **6. Distribution Li Analysis** > **EX_CircularNesting** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/membershipanalysis/ex_emptygroups.md b/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/membershipanalysis/ex_emptygroups.md index 49f15d7dab..eb4379fa8a 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/membershipanalysis/ex_emptygroups.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/membershipanalysis/ex_emptygroups.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **Exchange** > **6. Distribution Li Analysis** > **EX_EmptyGroups** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/membershipanalysis/ex_largestgroups.md b/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/membershipanalysis/ex_largestgroups.md index 547a38c9fa..5b6f682aff 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/membershipanalysis/ex_largestgroups.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/membershipanalysis/ex_largestgroups.md @@ -14,7 +14,7 @@ View the analysis task by navigating to the **Exchange** > **6. Distribution Lis Analysis** > **EX_LargestGroups** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/membershipanalysis/ex_nestedgroups.md b/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/membershipanalysis/ex_nestedgroups.md index c33b3207b3..30488a7250 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/membershipanalysis/ex_nestedgroups.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/membershipanalysis/ex_nestedgroups.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **Exchange** > **6. Distribution Li Analysis** > **EX_NestedGroups** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/membershipanalysis/ex_stalegroups.md b/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/membershipanalysis/ex_stalegroups.md index 6f46c6584b..e44b79c110 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/membershipanalysis/ex_stalegroups.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/membershipanalysis/ex_stalegroups.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **Exchange** > **6. Distribution Li Analysis** > **EX_StaleGroups** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/membershipanalysis/overview.md b/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/membershipanalysis/overview.md index 0883d22948..25da9506e3 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/membershipanalysis/overview.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/membershipanalysis/overview.md @@ -6,7 +6,7 @@ sidebar_position: 30 # Membership Analysis Job Group -The Membership Analysis job group provides visibility into toxic conditions contained with the +The Membership Analysis job group provides visibility into toxic conditions within the environment, such as circular nesting, large groups, empty groups, nesting, and potentially stale groups. diff --git a/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/overview.md b/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/overview.md index 6844dd22ad..64aa5c899e 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/overview.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/overview.md @@ -21,7 +21,7 @@ These jobs are compatible with the Office 365 environment. - [Effective Membership > EX_GroupExpansion Job](/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/ex_groupexpansion.md) – Expands the direct membership of distribution groups in the environment - [Membership Analysis Job Group](/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/membershipanalysis/overview.md) - – Provides visibility into toxic conditions contained with the environment, such as circular + – Provides visibility into toxic conditions within the environment, such as circular nesting, large groups, empty groups, nesting, and potentially stale groups - [EX_DLCleanup Job](/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/ex_dlcleanup.md) – Identifies potentially stale distribution groups based on the last domain logon of the members, diff --git a/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/recommended.md b/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/recommended.md index 899adaf8bf..3602c9cb54 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/distributionlists/recommended.md @@ -25,7 +25,7 @@ The following job groups need to be successfully run: **Schedule Frequency** This job group has been designed to run daily after the .Active Directory Inventory Job Group has -been run, to analyze distribution list membership. This job group does not collect data. It uses the +been run, to analyze distribution list membership. This job group doesn't collect data. It uses the data collection from the .Active Directory Inventory Job Group. :::info diff --git a/docs/accessanalyzer/11.6/solutions/exchange/ex_useroverview.md b/docs/accessanalyzer/11.6/solutions/exchange/ex_useroverview.md index 1af05c8429..3060516d33 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/ex_useroverview.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/ex_useroverview.md @@ -15,7 +15,7 @@ environment. **Dependencies** -The following job groups need to be successfully run prior to this job: +The following job groups need to be successfully run before this job: - **.Active Directory Inventory** Job Group - **.Entra ID Inventory** Job Group @@ -27,8 +27,7 @@ The following job groups need to be successfully run prior to this job: **Schedule Frequency** -It is recommended to run this job daily after running its dependencies, but it can be scheduled to -run as desired. +Run this job daily after running its dependencies, or schedule it to run as needed. ## Analysis Tasks for the EX_Mailflow_UserOverview Job @@ -36,7 +35,7 @@ View the analysis task by navigating to the **Exchange** > **EX_UserOverview** > and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/collection/appletstatuscheck.md b/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/collection/appletstatuscheck.md index 113f897050..050f8ebf71 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/collection/appletstatuscheck.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/collection/appletstatuscheck.md @@ -14,7 +14,7 @@ Exchange servers. The .AppletStatusCheck Job uses the Script Data Collector. :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/collection/ex_metricscollection.md b/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/collection/ex_metricscollection.md index e9c01667fe..dc2ad0de66 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/collection/ex_metricscollection.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/collection/ex_metricscollection.md @@ -6,11 +6,11 @@ sidebar_position: 20 # EX_MetricsCollection Job -The EX_MetricsCollection Job is comprised of multiple queries that utilize the ExchangeMetrics Data +The EX_MetricsCollection Job is comprised of multiple queries that use the ExchangeMetrics Data Collector to process and collect the message tracking logs on the Exchange servers in the environment. These queries collect server, domain, user, and distribution list traffic including but -not limited to: sent, received, journal, NDRs, and transports messages. These queries are configured -to process and collect that previous 7 days of Message Tracking Logs the first time this job is run, +not limited to: sent, received, journal, NDRs, and transport messages. These queries are configured +to process and collect the previous 7 days of Message Tracking Logs the first time this job is run, after that it only collects the previous day unless the **Enable Persistent Log State** option has been enabled in the query. @@ -45,7 +45,7 @@ View the analysis tasks by navigating to the **Exchange** > **1. HUB Metrics** > **EX_MetricsCollection** > **Configure** node and selecting **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -56,7 +56,7 @@ The following analysis tasks are selected by default: - **1. Delivery Times History** – Creates the SA_ExhangeMetrics_DeliveryTimes table, accessible under the job’s Results node -- **2. DL History** – Creates the SA*EX* ExhangeMetrics_DistributionLists table, accessible under the +- **2. DL History** – Creates the SA_EX_ExhangeMetrics_DistributionLists table, accessible under the job’s Results node - **3. Internet Traffic History** – Creates the SA_EX_ExhangeMetrics_InternetTraffic table, accessible under the job’s Results node @@ -78,7 +78,7 @@ The following analysis task deletes table data from data collection and analysis task should remain deselected unless specifically needed: :::warning -Do not select the **00. Deletes all Stored Data** option. This analysis task is for +Don't select the **00. Deletes all Stored Data** option. This analysis task is for troubleshooting and cleanup only. Data will be deleted from the database. ::: @@ -92,8 +92,8 @@ troubleshooting and cleanup only. Data will be deleted from the database. The **08. SET HISTORY RETENTION** analysis task controls the retention period for the job’s data. This is why the Data Retention Period options at the global, job group, or job Properties settings -are not supported for the job group. The number of months can be modified. If desired, the parameter -can be set to a specified number of days. Follow these steps to modify the history retention period. +aren't supported for the job group. The number of months can be modified. If desired, the parameter +can be set to a specified number of days. To modify the history retention period: **Step 1 –** Navigate to the job’s **Configure** node and select **Analysis**. @@ -132,17 +132,17 @@ The modified history retention period is now applied during future job execution ## Troubleshooting Data Collection -There might be times when it is necessary to purge the data either through dropping the tables from -the database or truncating the data within the tables. This option is provided through ananalysis -task that is not selected by default. Only one analysis task within a job should be enabled when the -desire is to purge that database. +There might be times when you need to purge the data either by dropping the tables from +the database or by truncating the data within the tables. This option is provided through an analysis +task that isn't selected by default. Enable only one analysis task within a job when you want to +purge that database. :::warning This analysis task deletes information collected or produced by jobs in this solution. ::: -Follow these steps to troubleshoot data collection: +To troubleshoot data collection: **Step 1 –** Navigate to the job’s **Configure** node and select **Analysis**. @@ -159,9 +159,9 @@ Remember, only one task should be selected. **Step 3 –** In the Navigation pane, right-click the **Analysis** node and select **Execute Analyses**. -**Step 4 –** After the analysis task has been executed, return to the Analysis Selection view. -Deselect the analysis task which was executed and reselect the default analysis tasks (if any had -been cleared in Step 2). +**Step 4 –** After you run the analysis task, return to the Analysis Selection view. +Deselect the analysis task you ran and reselect the default analysis tasks (if any were +cleared in Step 2). -The selected purge of data and tables has taken place, and the analysis tasks have been reset to the +The selected purge of data and tables is complete, and the analysis tasks are reset to the default state. diff --git a/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/collection/ex_metricsdetails.md b/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/collection/ex_metricsdetails.md index 670338892c..ed01e6b115 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/collection/ex_metricsdetails.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/collection/ex_metricsdetails.md @@ -6,11 +6,11 @@ sidebar_position: 30 # EX_MetricsDetails Job -The EX_MetricsDetails Job collects daily user-to-user Traffic. Walk through this jobs query to +The EX_MetricsDetails Job collects daily user-to-user Traffic. Walk through this job's query to configure the internal domains to collect the sender to recipient traffic from. By default, the query is configured to collect the previous 1 day of Message Tracking Logs and has @netwrix.com -configured as the domain. If the domains are not configured in the query, then most likely data -collection does not return. +configured as the domain. If the domains aren't configured in the query, then most likely data +collection doesn't return. ## Queries for the EX_MetricsDetails Job @@ -31,7 +31,7 @@ The following query is included in the EX_MetricsDetails Job: The Activity Metrics Query has been preconfigured to run with the ExchangeMetrics Data Collector to collect user traffic per day. The domains must be configured for data collection to return data. -Follow the steps to configure the Activity Metrics Query. +To configure the Activity Metrics Query: **Step 1 –** Navigate to the **Exchange** > **1. HUB Metrics** > **0. Collection** > **EX_MetricsDetails** > **Configure** node and select **Queries**. @@ -43,7 +43,7 @@ Properties**. The Query Properties window opens. Collector Wizard opens. :::warning -Do not modify other wizard pages. The wizard pages are pre-configured for this job. +Don't modify other wizard pages. The wizard pages are pre-configured for this job. ::: @@ -65,7 +65,7 @@ View the analysis tasks by navigating to the **Exchange** > **1. HUB Metrics** > **EX_MetricsDetails** > **Configure** node and selecting **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -87,7 +87,7 @@ The following analysis task clears table data from data collection and analysis task should remain deselected unless specifically needed: :::warning -Do not select the **00. DROP HISTORY** option. This analysis task is for +Don't select the **00. DROP HISTORY** option. This analysis task is for troubleshooting and cleanup only. Data will be deleted from the database. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/collection/overview.md b/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/collection/overview.md index ca457492e5..dde56b6b00 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/collection/overview.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/collection/overview.md @@ -16,12 +16,12 @@ The jobs in the 0.Collection Job Group are: - [AppletStatusCheck Job](/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/collection/appletstatuscheck.md) – Checks the health and status of the applet deployed to the target Exchange servers - [EX_MetricsCollection Job](/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/collection/ex_metricscollection.md) - – Comprised of multiple queries that utilize the Exchange Metrics Data Collect to process and + – Comprised of multiple queries that use the Exchange Metrics Data Collect to process and collect the message tracking logs on the Exchange servers in the environment. These queries collect server, domain, user, and distribution list traffic including but not limited to sent, - received, journal, NDRs, and transports message. These queries are configured to process and - collect that previous 7 days of Message Tracking Logs the first time this job is run, after that - it only collects the previous day assuming persistence has not been disabled inside the query. + received, journal, NDRs, and transport messages. These queries are configured to process and + collect the previous 7 days of Message Tracking Logs the first time this job is run, after that + it only collects the previous day if persistence is enabled in the query. - [EX_MetricsDetails Job](/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/collection/ex_metricsdetails.md) – Collects user to user traffic per day @@ -29,6 +29,6 @@ The jobs in the 0.Collection Job Group are: This job's query needs to be configured to the internal domains from which to collect the sender to recipient traffic. By default, the query is configured to collect the previous 1 day of Message Tracking Logs and has @netwrix.com configured as the domain. If the domains are - not configured in the query, then most likely data collection does not return. + not configured in the query, then most likely data collection doesn't return. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_deliverytimes.md b/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_deliverytimes.md index 9caccbecb7..cccfcf5b53 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_deliverytimes.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_deliverytimes.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **Exchange** > **1. HUB Metrics** > **EX_DeliveryTimes** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_dlmetrics.md b/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_dlmetrics.md index 0f72cbebd9..f6ffcad9c4 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_dlmetrics.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_dlmetrics.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **Exchange** > **1. HUB Metrics** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_domainmetrics.md b/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_domainmetrics.md index 104439f532..b2757f4910 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_domainmetrics.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_domainmetrics.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **Exchange** > **1. HUB Metrics** > **EX_DomainMetrics** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -29,7 +29,7 @@ The following analysis tasks are selected by default: - **2. External Domain Traffic - Volume** – Creates the SA_EX_DomainMetrics_Volume table, accessible under the job’s Results node -In addition to the tables and views by the analysis tasks, the EX_DomainMetrics Job produces the +In addition to the tables and views created by the analysis tasks, the EX_DomainMetrics Job produces the following pre-configured reports: | Report | Description | Default Tags | Report Elements | diff --git a/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_hourlymetrics.md b/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_hourlymetrics.md index 513ac33995..f5f3cb07fe 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_hourlymetrics.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_hourlymetrics.md @@ -15,13 +15,7 @@ View the analysis tasks by navigating to the **Exchange** > **1. HUB Metrics** > **EX_HourlyMetrics** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are -preconfigured for this job. -::: - - -:::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_messagesize.md b/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_messagesize.md index 41c4ee5a2a..3b6c86724c 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_messagesize.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_messagesize.md @@ -14,7 +14,7 @@ View the analysis task by navigating to the **Exchange** > **1. HUB Metrics** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_servermetrics.md b/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_servermetrics.md index f8a8d46351..2cdcbc2bf8 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_servermetrics.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_servermetrics.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **Exchange** > **1. HUB Metrics** > **EX_ServerMetrics** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_usermetrics.md b/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_usermetrics.md index 0df99307df..231a11cc35 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_usermetrics.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_usermetrics.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **Exchange** > **1. HUB Metrics** > **EX_UserMetrics** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/overview.md b/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/overview.md index dad39da21b..8e79095bb0 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/overview.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/overview.md @@ -6,9 +6,9 @@ sidebar_position: 20 # 1.HUB Metrics Job Group -The 1. HUB Metrics Job Group is comprised of data collection, analysis and reports that focus on +The 1. HUB Metrics Job Group is comprised of data collection, analysis, and reports that focus on mail-flow activity occurring within your organization. This job group goes out to each server that -contains the Message Tracking Logs and parse the log to return the data to the Enterprise Auditor +contains the Message Tracking Logs and parses the log to return the data to the Enterprise Auditor database. ![1.HUB Metrics Job Group in the Jobs Tree](/images/accessanalyzer/11.6/solutions/exchange/hubmetrics/jobstree.webp) @@ -30,6 +30,6 @@ The following job groups and jobs comprise the 1. HUB Metrics Job Group: – Provides information around size of messages sent and received - [EX_ServerMetrics Job](/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_servermetrics.md) – Provides visibility into server mail-flow statistics, such as, sent, received, journaling, - transport and NDR counts and sizes + transport and non-delivery report (NDR) counts and sizes - [EX_UserMetrics Job](/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/ex_usermetrics.md) – Provides information around each user’s mail-flow in the organization diff --git a/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/recommended.md b/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/recommended.md index e67dbdfb35..703a2239ec 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/recommended.md @@ -56,7 +56,7 @@ Run this job group at 1:00 AM. **History Retention** -History retention should not be enabled on this job group. History is kept through analysis tasks. +History retention shouldn't be enabled on this job group. History is kept through analysis tasks. Modify the following analysis tasks to customize the amount of history which is kept: | Job Name | Analysis Task Name | Default History | @@ -86,13 +86,13 @@ following exceptions: The 1. HUB Metrics Job Group should be run with the default analysis configurations. :::warning -Most of these analysis tasks are preconfigured and should not be modified or +Most of these analysis tasks are preconfigured and shouldn't be modified or deselected. There are a few which are deselected by default, as they are for troubleshooting purposes. ::: -The following analysis tasks should not be deselected, but their parameters can be modified: +The following analysis tasks shouldn't be deselected, but their parameters can be modified: - **0. Collection** > **EX_MetricsCollection** Job – **08. SET HISTORY RETENTION** Analysis Task - **0. Collection** > **EX_MetricsDetails** Job – **02. SET HISTORY RETENTION** Analysis Task diff --git a/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/ex_features.md b/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/ex_features.md index 2dd0de6ec0..41bd503cf2 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/ex_features.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/ex_features.md @@ -7,7 +7,7 @@ sidebar_position: 20 # Features > EX_Features Job The EX_Features job is comprised of data collection and a report that provides information around -which features have been enabled or disabled on Mailboxes, such as ActiveSync, IMAP, POP and more. +which features have been enabled or disabled on Mailboxes, such as ActiveSync, IMAP, POP, and more. :::info Schedule the Features Job Group to run weekly on any desired recurrence. diff --git a/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/logons/ex_mailboxlogons.md b/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/logons/ex_mailboxlogons.md index 060cd0dab2..3c24369244 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/logons/ex_mailboxlogons.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/logons/ex_mailboxlogons.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **Exchange** > **4. Mailboxes** > * **EX_MailboxLogons** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -45,7 +45,7 @@ The following analysis task deletes table data from data collection and analysis task should remain cleared unless specifically needed: :::warning -Do not select the **00. Delete All Historical Data** option. This analysis task is for +Don't select the **00. Delete All Historical Data** option. This analysis task is for troubleshooting and cleanup only. Data will be deleted from the database. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/overview.md b/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/overview.md index 5375602ec9..132ebc3bf4 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/overview.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/overview.md @@ -20,12 +20,12 @@ These jobs are compatible with the Office 365 environment. - [Features > EX_Features Job](/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/ex_features.md) – Comprised of data collection and a report that provides information around which features have - been enabled or disabled on mailboxes, such as ActiveSync, IMAP, POP and more + been enabled or disabled on mailboxes, such as ActiveSync, IMAP, POP, and more - [Logons Job Group](/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/logons/overview.md) – Provides collection of Native Mailbox Access Auditing logs from Exchange to provide reporting around mailbox logon activity - [Permissions Job Group](/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/permissions/overview.md) - – Comprised of data collection, analysis and reports that focus on access granted to each mailbox + – Comprised of data collection, analysis, and reports that focus on access granted to each mailbox in the environment including, Mailbox Rights, Active Directory Permissions, Delegation, and Folder Permissions - [Sizing Job Group](/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/sizing/overview.md) diff --git a/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/permissions/collection/ex_sendas.md b/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/permissions/collection/ex_sendas.md index f2b25df74c..cd7227da5c 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/permissions/collection/ex_sendas.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/permissions/collection/ex_sendas.md @@ -38,7 +38,7 @@ View the analysis task by navigating to the **Exchange** > **4. Mailboxes** > ** **0.Collection** > **EX_SendAs** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/permissions/ex_admingroups.md b/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/permissions/ex_admingroups.md index bd4d13b80b..5f4fe15901 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/permissions/ex_admingroups.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/permissions/ex_admingroups.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **Exchange** > **4. Mailboxes** > * **EX_AdminGroups** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/permissions/ex_mailboxaccess.md b/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/permissions/ex_mailboxaccess.md index 2b821227ac..54fb34c074 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/permissions/ex_mailboxaccess.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/permissions/ex_mailboxaccess.md @@ -10,18 +10,18 @@ The EX_MailboxAccess job provides visibility into access granted to each mailbox taking into consideration Mailbox Rights, Active Directory Permissions, Delegation, and Folder Permissions. -## Analysis Tasks for the EX_Mailbox Access Job +## Analysis Tasks for the EX_MailboxAccess Job View the analysis tasks by navigating to the **Exchange** > **4. Mailboxes** > **Permissions** > **EX_MailboxAccess** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: -![Analysis Tasks for the EX_Mailbox Access Job](/images/accessanalyzer/11.6/solutions/exchange/mailboxes/permissions/mailboxaccessanalysis.webp) +![Analysis Tasks for the EX_MailboxAccess Job](/images/accessanalyzer/11.6/solutions/exchange/mailboxes/permissions/mailboxaccessanalysis.webp) The following analysis tasks are selected by default: @@ -52,7 +52,7 @@ The following analysis tasks are selected by default: - 12.Send As Summary – Creates the SA_EX_MailboxAccess_SendAsSummary table accessible under the job’s Results node -The following analysis tasks is selected to export data to the AIC: +The following analysis task is selected to export data to the AIC: - 13.AIC Import - Export Exchange Permissions – Exports delegates, Send AS rights, mailbox permissions, and Active Directory rights to the Access Information Center @@ -73,5 +73,5 @@ the following pre-configured reports: | Delegation (Delegates) | This report identifies users where Delegate/Send on Behalf Of rights have been assigned and which objects the users have been given rights to. | None | This report is comprised of two elements:
  • Bar Chart – Displays top users by number of delegates
  • Table – Provides details on top users by number of delegates
| | Full Control Access (Mailboxes with Full Control) | This report identifies users with the largest amount of Full Control rights assigned to other individuals. | None | This report is comprised of two elements:
  • Bar Chart – Displays top users with full control granted
  • Table – Provides details on top users with full control granted
| | Incorrect Default And Anon Permissions | This report identifies where Default or Anonymous have any role assignment other than **None** or **Free/Busy time**. | None | This report is comprised of three elements:
  • Bar Chart – Displays top users with incorrect default/anon permissions
  • Table – Provides details on top users with incorrect default/anon permissions
  • Table – Provides role details
| -| Missing Anonymous Permissions | This report identifies folders where Anonymous permissions are not assigned. | None | This report is comprised of one element:
  • Table – Provides details on missing anonymous permissions
| +| Missing Anonymous Permissions | This report identifies folders where Anonymous permissions aren't assigned. | None | This report is comprised of one element:
  • Table – Provides details on missing anonymous permissions
| | Send As (Send-As Rights) | This report identifies which users have the highest number of users with Send-As rights to their mailbox. | None | This report is comprised of three elements:
  • Stacked Bar Chart – Displays top users by send as rights granted
  • Table – Provides details on top users by send as right granted
  • Table – Provides additional details
| diff --git a/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/permissions/overview.md b/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/permissions/overview.md index 161ed37e3b..98e0199177 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/permissions/overview.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/permissions/overview.md @@ -6,7 +6,7 @@ sidebar_position: 40 # Permissions Job Group -The Permissions job group is comprised of data collection, analysis and reports that focus on access +The Permissions job group is comprised of data collection, analysis, and reports that focus on access granted to each mailbox in the environment including, Mailbox Rights, Active Directory Permissions, Delegation, and Folder Permissions. diff --git a/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/recommended.md b/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/recommended.md index f7276f9a08..472e94ceac 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/recommended.md @@ -38,7 +38,7 @@ on-premises to run against: - Local host This Job Group can target a custom host list for Exchange Online instead of targeting Exchange -on-premises. However, do not try to target both types of environments. +on-premises. However, don't try to target both types of environments. **Connection Profile** @@ -63,7 +63,7 @@ topic for additional information. **Schedule Frequency** -It is not recommended to run these jobs at the 4. Mailboxes job group level. The Logons sub-job +Don't run these jobs at the 4. Mailboxes job group level. The Logons sub-job group and Sizing job group have been designed to run daily. The Features sub-job group and Permissions job group have been designed to run weekly. See the table for recommended times: @@ -76,7 +76,7 @@ Permissions job group have been designed to run weekly. See the table for recomm **History Retention** -History retention should not be enabled on this job group. History is kept through analysis tasks. +History retention shouldn't be enabled on this job group. History is kept through analysis tasks. Modify the following analysis tasks to customize the amount of history which is kept: | Job Name | Analysis Task Name | Default History | @@ -104,18 +104,18 @@ No other queries should be modified. The 4. Mailboxes job group should be run with the default analysis configurations. :::warning -Most of these analysis tasks are preconfigured and should not be modified or +Most of these analysis tasks are preconfigured and shouldn't be modified or deselected. There are some tasks that are deselected by default, as they are for troubleshooting purposes. ::: -The following analysis tasks should not be deselected, but their parameters can be modified: +The following analysis tasks shouldn't be deselected, but their parameters can be modified: - **Logons** > **EX_MailboxLogons** Job – **03.SET HISTORY RETENTION** Analysis Task - **Sizing** > **EX_MailboxSizes** Job – **02.SET HISTORY RETENTION** Analysis Task -The following analysis tasks is enabled to send Exchange mailbox permission data to the +The following analysis task is enabled to send Exchange mailbox permission data to the Netwrix Access Information Center: - **Permissions** > **EX_MailboxAccess** Job – **13.AIC Import - Export Exchange Permissions** diff --git a/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/sizing/ex_mailboxsizes.md b/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/sizing/ex_mailboxsizes.md index d6b2c94ef8..8f99ed2cc8 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/sizing/ex_mailboxsizes.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/sizing/ex_mailboxsizes.md @@ -8,18 +8,18 @@ sidebar_position: 20 The EX_MailboxSizes job provides analysis and reporting around mailbox sizing and growth. -#### Analysis Tasks for the EX_Mailbox Sizes Job +#### Analysis Tasks for the EX_MailboxSizes Job View the analysis tasks by navigating to the **Exchange** > **4. Mailboxes** > **Sizing** > **EX_MailboxSizes** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: -![Analysis Tasks for the EX_Mailbox Sizes Job](/images/accessanalyzer/11.6/solutions/exchange/mailboxes/sizing/mailboxsizesanalysis.webp) +![Analysis Tasks for the EX_MailboxSizes Job](/images/accessanalyzer/11.6/solutions/exchange/mailboxes/sizing/mailboxsizesanalysis.webp) The following analysis tasks are selected by default: @@ -47,7 +47,7 @@ The following analysis task deletes table data from data collection and analysis task should remain cleared unless specifically needed: :::warning -Do not select the **00.Delete All Data** option. This analysis task is for +Don't select the **00.Delete All Data** option. This analysis task is for troubleshooting and cleanup only. Data will be deleted from the database: ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/sizing/ex_stalemailboxes.md b/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/sizing/ex_stalemailboxes.md index 069ce34c20..f0d3e1f886 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/sizing/ex_stalemailboxes.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/sizing/ex_stalemailboxes.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **Exchange** > **4. Mailboxes** > * **EX_StaleMailboxes** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -35,5 +35,5 @@ produces the following pre-configured reports: | Report | Description | Default Tags | Report Elements | | --------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Orphaned Mailboxes | Orphaned Mailboxes do not have an Active Directory account associated with them, and generally can be safely deleted. | None | This report is comprised of three elements:
  • Bar Chart – Displays orphan mailbox storage
  • Table – Provides details on all orphaned mailboxes
  • Table – Provides details on orphan mailbox storage
| +| Orphaned Mailboxes | Orphaned Mailboxes don't have an Active Directory account associated with them, and generally can be safely deleted. | None | This report is comprised of three elements:
  • Bar Chart – Displays orphan mailbox storage
  • Table – Provides details on all orphaned mailboxes
  • Table – Provides details on orphan mailbox storage
| | Stale Users (Mailboxes associated with Stale AD Accounts) | This report shows mailboxes which are tied to stale user accounts. | None | This report is comprised of three elements:
  • Bar Chart – Displays stale user mailboxes
  • Table – Provides details stale user mailboxes
  • Table – Provides additional details on stale user mailboxes
| diff --git a/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/sizing/ex_storesizes.md b/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/sizing/ex_storesizes.md index 4fef0add56..72fe842f7a 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/sizing/ex_storesizes.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/sizing/ex_storesizes.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **Exchange** > **4. Mailboxes** > **Sizing** > **EX_StoreSizes** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow.md b/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow.md index 98ad94e511..da3218e799 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow.md @@ -14,7 +14,7 @@ The EX_Mailflow job is located in the **Mailflow** > **0. Collection** job group ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/11.6/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -23,7 +23,7 @@ The EX_Mailflow job has the following configurable parameter: - Number of months to keep -See the [Analysis Tasks for the EX_Mailflow Job](#analysis-tasks-for-the-ex_mailflow-job) topic for +See the [Analysis Tasks for the EX_Mailflow Job](#analysis-tasks-for-the-exmailflow-job) topic for additional information. ## Queries for the EX_Mailflow Job @@ -44,7 +44,7 @@ The following queries are included in the EX_Mailflow job: - LocalDomains – Collects domains local to the Office 365 environment :::warning - Do not modify this query. The query is preconfigured for this job. + Don't modify this query. The query is preconfigured for this job. ::: @@ -57,7 +57,7 @@ The following queries are included in the EX_Mailflow job: The ExchangePS Data Collector configured with the Mail Flow Metrics category can be scoped to specific report dates. By default, the MailFlow Query is set to report on the Last 7 Days. -Follow the steps to modify the query configuration: +To modify the query configuration: **Step 1 –** Navigate to the **Exchange** > **8. Exchange Online** > **0. Collection** > **EX_Mailflow** > **Configure** node and select **Queries**. @@ -69,7 +69,7 @@ Properties window opens. Wizard opens. :::warning -Do not modify other wizard pages. The wizard pages are pre-configured for this job. +Don't modify other wizard pages. The wizard pages are pre-configured for this job. ::: @@ -95,7 +95,7 @@ View the analysis tasks by navigating to the **Exchange** > **8. Exchange Online Collection** > **EX_Mailflow** > **Configure** node and selecting **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -121,7 +121,7 @@ The following analysis task deletes table data from data collection and analysis task should remain cleared unless specifically needed: :::warning -Do not select the **00. Deletes all Stored Data** option. This analysis task is for +Don't select the **00. Deletes all Stored Data** option. This analysis task is for troubleshooting and cleanup only. Data will be deleted from the database. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow_dl.md b/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow_dl.md index b806b6e906..49b85d36f7 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow_dl.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow_dl.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **Exchange** > **8. Exchange Online **EX_Mailflow_DL** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -23,13 +23,13 @@ preconfigured for this job. The following analysis tasks are selected by default: -- Azure Groups Direct Member Count – Creates the EX_ MailFlow_DL_AzureMemberCount table, accessible +- Azure Groups Direct Member Count – Creates the EX_MailFlow_DL_AzureMemberCount table, accessible under the job’s Results node. Provides a direct member count for distribution lists from Azure groups. -- DLs by Count – Creates the EX_ Mailflow_DLsByCount table, accessible under the job’s Results +- DLs by Count – Creates the EX_Mailflow_DLsByCount table, accessible under the job’s Results node. Lists of all distribution lists and how much mail-flow they have received. -In addition to the tables and views created by the analysis tasks, the EX_Mailflow_DL Jjb produces +In addition to the tables and views created by the analysis tasks, the EX_Mailflow_DL Job produces the following pre-configured report: | Report | Description | Default Tags | Report Elements | diff --git a/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow_domain.md b/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow_domain.md index 75e9dc975c..a5efe5bfcf 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow_domain.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow_domain.md @@ -11,7 +11,7 @@ coming from. This job is set to analyze the last 30 days. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/11.6/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -21,7 +21,7 @@ The EX_Mailflow_Domain job has the following configurable parameter: - Number of days to show in tables and reports See the -[Analysis Tasks for the EX_Mailflow_Domain Job](#analysis-tasks-for-the-ex_mailflow_domain-job) +[Analysis Tasks for the EX_Mailflow_Domain Job](#analysis-tasks-for-the-exmailflowdomain-job) topic for additional information. ## Analysis Tasks for the EX_Mailflow_Domain Job @@ -30,7 +30,7 @@ View the analysis task by navigating to the **Exchange** > **8. Exchange Online* **EX_Mailflow_Domain** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow_mailbox.md b/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow_mailbox.md index a06dffcff2..b306847eb1 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow_mailbox.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow_mailbox.md @@ -11,7 +11,7 @@ This job is set to analyze the last 30 days. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/11.6/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -22,7 +22,7 @@ The EX_Mailflow_Mailbox job has the following configurable parameter: Count** and **User Mailboxes by Message Size** analysis tasks. The default is **30** days. See the -[Analysis Tasks for the EX_Mailflow_Mailbox Job](#analysis-tasks-for-the-ex_mailflow_mailbox-job) +[Analysis Tasks for the EX_Mailflow_Mailbox Job](#analysis-tasks-for-the-exmailflowmailbox-job) topic for additional information. ## Analysis Tasks for the EX_Mailflow_Mailbox Job @@ -31,7 +31,7 @@ View the analysis tasks by navigating to the **Exchange** > **8. Exchange Online **EX_Mailflow_Mailbox** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow_orgoverview.md b/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow_orgoverview.md index 9116db8e88..d123253e6b 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow_orgoverview.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow_orgoverview.md @@ -11,7 +11,7 @@ This job is set to analyze the last 30 days. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/11.6/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -21,7 +21,7 @@ The EX_Mailflow_OrgOverview job has the following configurable parameter: - Number of days of data to display See the -[Analysis Tasks for the EX_Mailflow_OrgOverview Job](#analysis-tasks-for-the-ex_mailflow_orgoverview-job) +[Analysis Tasks for the EX_Mailflow_OrgOverview Job](#analysis-tasks-for-the-exmailfloworgoverview-job) topic for additional information. ## Analysis Tasks for the EX_Mailflow_OrgOverview Job diff --git a/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/overview.md b/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/overview.md index 30bbb84c67..8a4614ebe8 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/overview.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/overview.md @@ -6,7 +6,7 @@ sidebar_position: 20 # Mailflow Job Group -The Mailbox job group is comprised of jobs that process and analyze the Message Tracking Logs in the +The Mailflow job group is comprised of jobs that process and analyze the Message Tracking Logs in the Office 365 environment. This job group parses message tracking and stores the data for analysis and reporting in the Enterprise Auditor database. diff --git a/docs/accessanalyzer/11.6/solutions/exchange/online/recommended.md b/docs/accessanalyzer/11.6/solutions/exchange/online/recommended.md index fabaa8dfc1..aaa08bd028 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/online/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/online/recommended.md @@ -68,7 +68,7 @@ The 8. Exchange Online job group should be run with the default analysis configu these analysis tasks are preconfigured and should never be modified or deselected. There are some that are deselected by default, as they are for troubleshooting purposes. -The following analysis tasks should not be deselected, but their parameters can be modified: +The following analysis tasks shouldn't be deselected, but their parameters can be modified: - **Mailflow** > **0. Collection** > **EX_Mailflow** Job – **03. SET HISTORY RETENTION** Analysis Task diff --git a/docs/accessanalyzer/11.6/solutions/exchange/overview.md b/docs/accessanalyzer/11.6/solutions/exchange/overview.md index 24c289ad5b..9c02c043a0 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/overview.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/overview.md @@ -37,24 +37,23 @@ topics for additional information. **Sensitive Data Discovery Considerations** The Sensitive Data Discovery Add-On must be installed on the Enterprise Auditor Console server, -which enables Sensitive Data criteria for scans.If running Sensitive Data Discovery (SDD) scans, it -will be necessary to increase the minimum amount of RAM. Each thread requires a minimum of 2 -additional GB of RAM per host.For example, if the job is configured to scan 8 hosts at a time , then -an extra 16 GB of RAM are required (8x2=16). +which enables Sensitive Data criteria for scans. If you run Sensitive Data Discovery (SDD) scans, +increase the minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per +host. For example, if the job is configured to scan 8 hosts at a time, the job needs an extra 16 GB +of RAM (8x2=16). :::note The Sensitive Data Discovery Add-on installation package installs the appropriate JDK -(Java) version on the server. The JDK deployed is prepackaged and does not require any -configuration; it has been preconfigured to work with Enterprise Auditor and should never be -customized through Java. It will not conflict with other JDKs or Java Runtimes in the same -environment. +(Java) version on the server. This JDK requires no configuration, works with Enterprise Auditor +by default, and doesn't conflict with other JDKs or Java Runtimes in the same environment. Don't +customize it through Java. ::: **Location** The Exchange Solution requires a special Enterprise Auditor license. It can be installed from the -Enterprise Auditor Instant Job Wizard. Once it has been installed into the Jobs tree, navigate to +Enterprise Auditor Instant Job Wizard. After it has been installed into the Jobs tree, navigate to the solution: **Jobs** > **Exchange**. Each job group within the solution collects data, analyzes the data, and reports on the target @@ -71,23 +70,23 @@ The Exchange Solution is divided into categories based upon what is being audite The following job groups comprise the Exchange Solution: - [1.HUB Metrics Job Group](/docs/accessanalyzer/11.6/solutions/exchange/hubmetrics/overview.md) - – Comprised of data collection, analysis and reports that focus on mail-flow activity occurring + – Comprised of data collection, analysis, and reports that focus on mail-flow activity occurring within your organization. This job group goes out to each server that contains the Message Tracking Logs and parses the log to return the data to the Enterprise Auditor database. - [2.CAS Metrics Job Group](/docs/accessanalyzer/11.6/solutions/exchange/casmetrics/overview.md) - – Comprised of data collection, analysis and reports that focus on remote connections (Outlook Web + – Comprised of data collection, analysis, and reports that focus on remote connections (Outlook Web Access, ActiveSync, and Outlook Anywhere Access) occurring within your organization. This job group goes out to each server that contains the IIS Logs and parses the log to return the data to the Enterprise Auditor database. - [3.Databases Job Group](/docs/accessanalyzer/11.6/solutions/exchange/databases/overview.md) - – Comprised of data collection, analysis and reports that focus on database sizing, growth, and + – Comprised of data collection, analysis, and reports that focus on database sizing, growth, and trends - [4.Mailboxes Job Group](/docs/accessanalyzer/11.6/solutions/exchange/mailboxes/overview.md) – Comprised of data collection, analyses, and reports around mailbox features, logons, permissions, and sizing :::warning - It is not recommended to run this job group at this job group level. + It isn't recommended to run this job group at this job group level. ::: @@ -97,7 +96,7 @@ The following job groups comprise the Exchange Solution: environment. - [5. Public Folders Job Group](/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/overview.md) - – Comprised of data collection, analysis and reports that focus on public folder sizing, content + – Comprised of data collection, analysis, and reports that focus on public folder sizing, content aging, entitlement, ownership, and the identification of each public folder’s Most Probable Owner. The Most Probable Owner is a unique algorithm built into the public folder data collector that is determined based on folder ownership, content posted, and size of content posted. @@ -117,7 +116,7 @@ The following job groups comprise the Exchange Solution: depends upon multiple job groups. The MAPI-based data collectors require both Enterprise Auditor MAPI CDO and Microsoft Exchange MAPI -CDO to be installed on the Enterprise Auditor Console server. Once these have been installed, +CDO to be installed on the Enterprise Auditor Console server. After these are installed, configure the **Settings** > **Exchange** node for proper connection to the Exchange server. See the [Exchange](/docs/accessanalyzer/11.6/admin/settings/exchange.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/content/pf_content.md b/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/content/pf_content.md index d3930cc102..7ded08b17f 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/content/pf_content.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/content/pf_content.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **Exchange** > **5. Public Folders* **PF_Content** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/content/pf_contentscans.md b/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/content/pf_contentscans.md index 87777856f2..c86c45a6ea 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/content/pf_contentscans.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/content/pf_contentscans.md @@ -34,7 +34,7 @@ View the analysis task by navigating to the **Exchange** > **5. Public Folders** **Collection** > **PF_ContentScans** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/growthsize/pf_folderscans.md b/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/growthsize/pf_folderscans.md index d32f37e594..197ef28ed3 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/growthsize/pf_folderscans.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/growthsize/pf_folderscans.md @@ -34,7 +34,7 @@ View the analysis task by navigating to the **Exchange** > **5. Public Folders** Size** > **Collection** > **PF_FolderScans** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/growthsize/pf_foldersize.md b/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/growthsize/pf_foldersize.md index deb289007f..9e3f910580 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/growthsize/pf_foldersize.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/growthsize/pf_foldersize.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **Exchange** > **5. Public Folders* Size** > **PF_FolderSize** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -41,7 +41,7 @@ The following analysis task clears table data from data collection and analysis task should remain cleared unless specifically needed: :::warning -Do not select the **00. Delete all Historical Data** option. This analysis task is for +Don't select the **00. Delete all Historical Data** option. This analysis task is for troubleshooting and cleanup only. Data will be deleted from the database. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/overview.md b/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/overview.md index 47250e81e5..6a359cfcbb 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/overview.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/overview.md @@ -33,8 +33,8 @@ The following comprise the 5. Public Folders job group: The **5. Public Folders** > **Ownership** job group uses the ExchangePublicFolder, a MAPI-based data collector. Therefore, it requires both Enterprise Auditor MAPI CDO and Microsoft Exchange MAPI CDO -to be installed on the Enterprise Auditor Console server. Once these have been installed, the -**Settings** > **Exchange** node must be configured for proper connection to the Exchange server. +to be installed on the Enterprise Auditor Console server. After these are installed, configure the +**Settings** > **Exchange** node for proper connection to the Exchange server. See the [Exchange](/docs/accessanalyzer/11.6/admin/settings/exchange.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/ownership/overview.md b/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/ownership/overview.md index e95b507022..93cceb7b7f 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/ownership/overview.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/ownership/overview.md @@ -13,7 +13,7 @@ based on folder ownership, content posted, and size of content posted. ![Ownership Job Group](/images/accessanalyzer/11.6/solutions/exchange/publicfolders/ownership/jobstree.webp) -The obs in the Ownership job group are: +The jobs in the Ownership job group are: - [Collection > PF_FolderOwnership Job](/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/ownership/pf_folderownership.md) – Focuses on public folder sizing, content aging, entitlement, ownership, and most importantly the diff --git a/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/ownership/pf_folderownership.md b/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/ownership/pf_folderownership.md index 8c9cb1a32d..72e7e4e6b7 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/ownership/pf_folderownership.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/ownership/pf_folderownership.md @@ -28,7 +28,7 @@ The following queries are included in the PF_FolderOwnership job: - By default set to search all public folders. It can be scoped. - See the - [Scope the ExchangePublicFolder Data Collector for the PF_FolderOwnership Job](#scope-the-exchangepublicfolder-data-collector-for-the-pf_folderownership-job) + [Scope the ExchangePublicFolder Data Collector for the PF_FolderOwnership Job](#scope-the-exchangepublicfolder-data-collector-for-the-pffolderownership-job) topic for additional information - Assigned Ownership – Collects assigned owners @@ -36,13 +36,13 @@ The following queries are included in the PF_FolderOwnership job: - By default set to search all public folders. It can be scoped. - Probable Owner Calculation can be modified - See the - [Scope the ExchangePublicFolder Data Collector for the PF_FolderOwnership Job](#scope-the-exchangepublicfolder-data-collector-for-the-pf_folderownership-job) + [Scope the ExchangePublicFolder Data Collector for the PF_FolderOwnership Job](#scope-the-exchangepublicfolder-data-collector-for-the-pffolderownership-job) topic for additional information ### Scope the ExchangePublicFolder Data Collector for the PF_FolderOwnership Job -The ExchangePublicFolder Data Collector can be scoped if desired. Follow the steps to modify the -query configuration. +The ExchangePublicFolder Data Collector can be scoped if desired. To modify the +query configuration: :::note These instructions include information on modifying the calculation used to determine @@ -60,7 +60,7 @@ Properties window opens. Data Collector Wizard opens. :::warning -Do not modify other wizard pages. The wizard pages are pre-configured for this job. +Don't modify other wizard pages. The wizard pages are pre-configured for this job. ::: @@ -74,7 +74,7 @@ using the following settings: - Default Public Folders – Select this option to access folders directly with client applications such as Microsoft Outlook. In its default configuration, Exchange System Manager displays these folders when a public folder tree is expanded. - - System Public Folders – Select this option to access folders that cannot be directly accessed. + - System Public Folders – Select this option to access folders that can't be directly accessed. Client applications, such as Microsoft Outlook, use these folders to store information such as free and busy data, offline address lists, and organizational forms. Other folders hold configuration information that is used by custom applications or by Exchange itself. The @@ -123,7 +123,7 @@ View the analysis task by navigating to the **Exchange** > **5. Public Folders** **Collection** > **PF_FolderOwnership** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/ownership/pf_owners.md b/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/ownership/pf_owners.md index 580506eff9..7bea2430e1 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/ownership/pf_owners.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/ownership/pf_owners.md @@ -17,7 +17,7 @@ View the analysis tasks by navigating to the **Exchange** > **5. Public Folders* **PF_Owners** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/permissions/pf_entitlements.md b/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/permissions/pf_entitlements.md index 85231f9306..33f60c4a22 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/permissions/pf_entitlements.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/permissions/pf_entitlements.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **Exchange** > **5. Public Folders* **Permissions** > **PF_Entitlements** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/permissions/pf_entitlementscans.md b/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/permissions/pf_entitlementscans.md index b392d36055..be9ee757f8 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/permissions/pf_entitlementscans.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/permissions/pf_entitlementscans.md @@ -35,7 +35,7 @@ View the analysis tasks by navigating to the **Exchange** > **5. Public Folders* **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/pf_overview.md b/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/pf_overview.md index 3fe1121c81..e1718e79ad 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/pf_overview.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/pf_overview.md @@ -16,7 +16,7 @@ View the analysis tasks by navigating to the **Exchange** > **5. Public Folders* **PF_Overview** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/recommended.md b/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/recommended.md index 84d3b71fc2..19ee6f3040 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/recommended.md @@ -42,8 +42,8 @@ list: individual host at the **Configure** > **Hosts** node :::note - The target host should be set to an on-premises Exchange server. Exchange Online is - not support. + The target host should be set to an on-premises Exchange server. Exchange Online + isn't supported. ::: @@ -80,7 +80,7 @@ Run this job group on Fridays at 8:00 PM. **History Retention** -History retention should not be enabled on this job group. History is kept through analysis tasks. +History retention shouldn't be enabled on this job group. Analysis tasks keep the history. Modify the following analysis task to customize the amount of history which is kept: | Job Name | Analysis Task Name | Default History | @@ -111,7 +111,7 @@ deselected. There are some that are deselected by default, as they are for troub ::: -The following analysis tasks should not be deselected, but their parameters can be modified: +The following analysis tasks shouldn't be deselected, but their parameters can be modified: - **Growth and Size** > **PF_FolderSize** Job – **02.SET HISTORY RETENTION** Analysis Task diff --git a/docs/accessanalyzer/11.6/solutions/exchange/recommended.md b/docs/accessanalyzer/11.6/solutions/exchange/recommended.md index d68f4e8402..8b4f8817ac 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/recommended.md @@ -20,9 +20,9 @@ relevant topic for specific information on job group settings and recommended sc ## ExchangePS Data Collector & Client Access Server -A Client Access Server (CAS) name is required for the ExchangePS Data Collector. When targeting -Exchange 2013 or 2016, it is possible for the **Settings** > **Exchange** node to have been -configured with a web address instead of a CAS. +A Client Access Server (CAS) name is required for the ExchangePS Data Collector. When you target +Exchange 2013 or 2016, the **Settings** > **Exchange** node might be configured with a web address +instead of a CAS. - Exchange 2010 Servers – Uses the CAS server set in the global configuration (**Settings** > **Exchange** node) @@ -34,7 +34,7 @@ configured with a web address instead of a CAS. global configuration has a web address instead of an actual server. Therefore, each query requires the CAS server to be set as the specific server on the Category page. -Follow the steps to supply a CAS name for data collection. +To supply a CAS name for data collection: **Step 1 –** Navigate to the job’s **Configure** node and select **Queries**. @@ -45,8 +45,8 @@ opens. Wizard opens. :::warning -Unless otherwise indicated within the job group section, do not make changes to other -wizard pages as they have been pre-configured for the purpose of the job. +Unless otherwise indicated within the job group section, don't make changes to other +wizard pages as they have been pre-configured to support the job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/sensitivedata/collection/ex_mailbox_sdd.md b/docs/accessanalyzer/11.6/solutions/exchange/sensitivedata/collection/ex_mailbox_sdd.md index 1648923071..9bc0d496bf 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/sensitivedata/collection/ex_mailbox_sdd.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/sensitivedata/collection/ex_mailbox_sdd.md @@ -42,7 +42,7 @@ The following query is included in the EX_Mailbox_SDD job: - US SSN - See the - [Configure the EWSMailbox Data Collector for the EX_Mailbox_SDD Job](#configure-the-ewsmailbox-data-collector-for-the-ex_mailbox_sdd-job) + [Configure the EWSMailbox Data Collector for the EX_Mailbox_SDD Job](#configure-the-ewsmailbox-data-collector-for-the-exmailboxsdd-job) topic for additional information ### Configure the EWSMailbox Data Collector for the EX_Mailbox_SDD Job @@ -50,19 +50,19 @@ The following query is included in the EX_Mailbox_SDD job: The Exchange Sensitive Data Discovery query has been preconfigured to run with the EWSMailbox Data Collector to scan for sensitive data. -Follow the steps to configure the scope of the EWSMailbox Data Collector: +To configure the scope of the EWSMailbox Data Collector: **Step 1 –** Navigate to the **Exchange** > **7. Sensitive Data** > **0. Collection** > **EX_Mailbox_SDD** > **Configure** node and select **Queries**. **Step 2 –** In the Query Selection view, select the **Exchange Sensitive Data Discovery** query and -click**Query Properties**. The Query Properties window opens. +click **Query Properties**. The Query Properties window opens. **Step 3 –** Select the **Data Source** tab, and click **Configure**. The EWS Mailbox Data Collector Wizard opens. :::warning -Do not make changes to other wizard pages as they have been pre-configured for the +Don't make changes to other wizard pages as they have been pre-configured for the purpose of this job. ::: @@ -78,7 +78,7 @@ topic for additional information. ![EWS Mailbox Data Collector Wizard Scope select page](/images/accessanalyzer/11.6/solutions/exchange/sensitivedata/collection/mailboxscopeselect.webp) **Step 5 –** To retrieve available mailboxes, click **Retrieve** on the Scope Select page. Select -the desired mailboxes and click **Add**. See the +the mailboxes you want and click **Add**. See the [EWSMailbox: Scope Select](/docs/accessanalyzer/11.6/admin/datacollector/ewsmailbox/scopeselect.md) topic for additional information. @@ -90,7 +90,7 @@ Sensitive data matches can be limited to reduce storage space. See the topic for additional information. :::note -By default, discovered sensitive data strings are not stored in the Enterprise Auditor +By default, discovered sensitive data strings aren't stored in the Enterprise Auditor database. ::: @@ -131,7 +131,7 @@ By default, all categories are selected under sensitive data. **Step 10 –** Navigate to the Summary page, click **Finish** to save any setting modifications or -click **Cancel** if no changes were made. Then click **OK** to close the Query Properties window +click **Cancel** if no changes were made. Then click **OK** to close the Query Properties window. The job now applies the modification to future job executions. @@ -141,7 +141,7 @@ View the analysis task by navigating to the **Exchange** > **7.Sensitive Data** **EX_Mailbox_SDD** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/sensitivedata/collection/ex_publicfolder_sdd.md b/docs/accessanalyzer/11.6/solutions/exchange/sensitivedata/collection/ex_publicfolder_sdd.md index 1b02265780..9d62854618 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/sensitivedata/collection/ex_publicfolder_sdd.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/sensitivedata/collection/ex_publicfolder_sdd.md @@ -42,7 +42,7 @@ The following query is included in the EX_PublicFolder_SDD job: - Tax Forms - US SSN - - See the [Configure the EX_PublicFolder_SDD Query](#configure-the-ex_publicfolder_sdd-query) + - See the [Configure the EX_PublicFolder_SDD Query](#configure-the-expublicfoldersdd-query) topic for additional information ### Configure the EX_PublicFolder_SDD Query @@ -51,7 +51,7 @@ The Exchange Sensitive Data Discovery query has been preconfigured to run with t Data Collector to scan for sensitive data. **Step 1 –** Navigate to the **Exchange** > **7. Sensitive Data** > **0. Collection** > -**EX_EWSPublicFolder_SDD** > **Configure** node and select **Queries**. +**EX_PublicFolder_SDD** > **Configure** node and select **Queries**. **Step 2 –** In the Query Selection view, select **Exchange Sensitive Data Discovery** and click **Query Properties**. The Query Properties window opens. @@ -60,7 +60,7 @@ Data Collector to scan for sensitive data. Collector Wizard opens. :::warning -Do not modify other wizard pages. The wizard pages are pre-configured for this job. +Don't modify other wizard pages. The wizard pages are pre-configured for this job. ::: @@ -72,7 +72,7 @@ Sensitive data matches can be limited to reduce storage space. See the for additional information. :::note -By default, discovered sensitive data strings are not stored in the Enterprise Auditor +By default, discovered sensitive data strings aren't stored in the Enterprise Auditor database. ::: @@ -103,7 +103,7 @@ for additional information. ![EWS Public Folder Data Collector Wizard Results page](/images/accessanalyzer/11.6/solutions/exchange/sensitivedata/collection/publicfolderresults.webp) **Step 7 –** To select which properties are gathered based on category, navigate to the Results -page.  See the +page. See the [EWSPublicFolder: Results](/docs/accessanalyzer/11.6/admin/datacollector/ewspublicfolder/results.md) topic for additional information. @@ -113,6 +113,6 @@ By default, all categories are selected under sensitive data. **Step 8 –** Navigate to the Summary page, click **Finish** to save any setting modifications or -click **Cancel** if no changes were made. Then click **OK** to close the Query Properties window +click **Cancel** if no changes were made. Then click **OK** to close the Query Properties window. The job applies the modification to future job executions. diff --git a/docs/accessanalyzer/11.6/solutions/exchange/sensitivedata/ex_sddresults.md b/docs/accessanalyzer/11.6/solutions/exchange/sensitivedata/ex_sddresults.md index be4ce48778..83c1c1a45b 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/sensitivedata/ex_sddresults.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/sensitivedata/ex_sddresults.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **Exchange** > **7. Sensitive Data* **EX_SDDResults** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -25,12 +25,12 @@ preconfigured for this job. The following analysis tasks are selected by default: - Mailbox Details – Creates the EX_SDDResults_MailboxDetails table, accessible under the job’s - Results node. Provides details regarding the number of matches that are found per item in each + Results node. Provides details regarding the number of matches found per item in each mailbox. - Mailbox Summary – Creates the EX_SDDResults_MailboxSummary table, accessible under the job’s Results node. Summarizes the items found with matches. - Public Folder Details – Creates the EX_SDDResults_PublicFolderDetails table, accessible under the - job’s Result node. Provides details regarding the number of matches that are found per item in + job’s Result node. Provides details regarding the number of matches found per item in each public folder. - Public Folder Mailstore Summary – Creates the EX_SDDResults_PublicFolderSummary table, accessible under the job’s Results node. Summarizes the items found with matches. @@ -41,7 +41,7 @@ The following analysis task deletes table data from data collection and analysis task should remain cleared unless specifically needed: :::warning -Do not select the **Deletes all Stored Data** option. This analysis task is for +Don't select the **Deletes all Stored Data** option. This analysis task is for troubleshooting and cleanup only. Data will be deleted from the database. ::: diff --git a/docs/accessanalyzer/11.6/solutions/exchange/sensitivedata/overview.md b/docs/accessanalyzer/11.6/solutions/exchange/sensitivedata/overview.md index 9aa7434664..f323758c5a 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/sensitivedata/overview.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/sensitivedata/overview.md @@ -24,7 +24,7 @@ These jobs are compatible with the Office 365 environment. – Contains analyses and reports to provide insight into the types of sensitive data that was located within Exchange mailboxes and public folders within the environment -The 7. Sensitive Data job group is comprised of jobs that utilize the EWSMailbox and EWSPublicFolder +The 7. Sensitive Data job group is comprised of jobs that use the EWSMailbox and EWSPublicFolder Data Collectors to locate sensitive data found in mailboxes and public folders in the Exchange environment. It also contains analysis and reporting jobs to order and analyze the data returned by the queries. See the diff --git a/docs/accessanalyzer/11.6/solutions/exchange/sensitivedata/recommended.md b/docs/accessanalyzer/11.6/solutions/exchange/sensitivedata/recommended.md index aac5d5af2d..9093a6bfca 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/sensitivedata/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/sensitivedata/recommended.md @@ -32,8 +32,8 @@ to be set to run against the version-appropriate default dynamic host list: - Exchange 2019 MB Servers :::note -Default dynamic host lists are populated from hosts in the Host Master Table which meet -the host inventory criteria for the list. Ensure the appropriate host lists have been populated +Access Analyzer populates default dynamic host lists from hosts in the Host Master Table +which meet the host inventory criteria for the list. Ensure the appropriate host lists have been populated through host inventory results. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/activity/forensics/fs_deletions.md b/docs/accessanalyzer/11.6/solutions/filesystem/activity/forensics/fs_deletions.md index c153f384a5..a5a6fdb014 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/activity/forensics/fs_deletions.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/activity/forensics/fs_deletions.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * **FS_Deletions** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -57,15 +57,14 @@ following pre-configured report: A Notification analysis task sends email notification to recipients when the job is executed. It requires the global **Notification** settings to be configured (**Settings** > **Notifications**) for SMTP server information, but it uses the recipient list provided through the analysis task. -Follow the steps to configure a notification analysis task. **Step 1 –** Navigate to the job’s **Configure** node and select **Analysis**. **Step 2 –** In the Analysis Selection view, select the Notification analysis task and click -**Analysis Configuration** . The Notification Data Analysis Module wizard opens. +**Analysis Configuration**. The Notification Data Analysis Module wizard opens. :::warning -Do not make changes to other wizard pages as they have been pre-configured for the +Don't make changes to other wizard pages as they have been pre-configured for the purpose of this job. ::: @@ -92,7 +91,7 @@ provided. You can use the following options: ![Message section](/images/accessanalyzer/11.6/solutions/filesystem/activity/forensics/notificationsmtpmessage.webp) -**Step 5 –** In the Message section, edit the **Subject**. It is not recommended to remove any +**Step 5 –** In the Message section, edit the **Subject**. It isn't recommended to remove any parameters. Then, customize the email content in the textbox to provide an explanation of the notification to the recipients. @@ -105,9 +104,9 @@ automatically during the execution of the job. :::tip Remember, all of the analysis tasks should remain in the default order indicated by the numbering. -Do not deselect any of the SQLscripting analysis tasks. +Don't deselect any of the SQL scripting analysis tasks. ::: -Once the Notification analysis task is configured and enabled alerts are sent when the trigger has -been identified by this job. +After you configure and enable the Notification analysis task, the job sends alerts when it +identifies the trigger. diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/activity/forensics/fs_permissionchanges.md b/docs/accessanalyzer/11.6/solutions/filesystem/activity/forensics/fs_permissionchanges.md index 8c8ffd3d89..6fa492abbd 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/activity/forensics/fs_permissionchanges.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/activity/forensics/fs_permissionchanges.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * **FS_PermissionChanges** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/activity/fs_leastprivilegedaccess.md b/docs/accessanalyzer/11.6/solutions/filesystem/activity/fs_leastprivilegedaccess.md index c48da84df8..c3d0a25197 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/activity/fs_leastprivilegedaccess.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/activity/fs_leastprivilegedaccess.md @@ -7,7 +7,7 @@ sidebar_position: 20 # Least Privileged Access > FS_LeastPrivilegedAccess Job The FS_LeastPrivilegedAccess job is designed to report on activity event information that can assist -in identifying least privilege from targeted file servers. It identifies where trustees are not +in identifying least privilege from targeted file servers. It identifies where trustees aren't leveraging their permissions to resources from targeted file servers. Requires **Access Auditing** component data collection. @@ -21,7 +21,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Access** > **FS_LeastPrivilegedAccess** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -55,4 +55,4 @@ produces the following pre-configured reports: | ------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Overprovisioning Risk by Share | This report identifies shares with the largest amount of unutilized entitlements and assigns a risk rating to each one. | GDPR SOX HIPAA PCI-DSS GLBA ITAR FERPA FISMA ISO27001 | This report is comprised of two elements:
  • Pie Chart – Displays shares by overprovisioning risk
  • Table – Provides details on shares by overprovisioning risk
| | Overprovisioning Summary | This report shows the percentage of all entitlements which are being used. An entitlement refers to one user's access to one folder. | GDPR SOX HIPAA PCI-DSS GLBA ITAR FERPA FISMA ISO27001 | This report is comprised of two elements:
  • Pie Chart – entitlements by level of usage
  • Table – Provides details on entitlements
| -| Remediation | If all members of a group are not using their full access, then modification to group permissions on the share will be suggested here. | None | This report is comprised of one element:
  • Table – Provides details on recommended changes to permissions
| +| Remediation | If all members of a group aren't using their full access, this report suggests changes to the group's permissions on the share. | None | This report is comprised of one element:
  • Table – Provides details on recommended changes to permissions
| diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/activity/security/fs_adminactvity.md b/docs/accessanalyzer/11.6/solutions/filesystem/activity/security/fs_adminactvity.md index 7e43687cc6..c180f8d247 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/activity/security/fs_adminactvity.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/activity/security/fs_adminactvity.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * **FS_AdminActivity** > **Configure** node and select Analysis. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -45,4 +45,4 @@ the following pre-configured reports: | Administrator Activity Details | This report shows the details of administrator activity on file shares. | None | This report is comprised of one element:
  • Table – Provides details on last 30 days of administrator activity
| | Administrator Activity Overview | This report identifies the types of actions administrators are performing across your network. | None | This report is comprised of two elements:
  • Pie Chart – Displays last 30 days of administrator activity
  • Table – Provides details on types of actions
| | Most Active Administrators | This report ranks administrators by number of shares they have activity in. | None | This report is comprised of two elements:
  • Bar Chart – Displays last 30 days of administrator activity
  • Table – Provides details on administrator activity
| -| Suspicious Admin Activity | This report highlights all administrator reads in shares where they do not have access. | GDPR SOX HIPAA PCI-DSS GLBA ITAR FERPA FISMA ISO27001 | This report is comprised of one element:
  • Table – Provides details on last 30 days of administrator activity
| +| Suspicious Admin Activity | This report highlights all administrator reads in shares where they don't have access. | GDPR SOX HIPAA PCI-DSS GLBA ITAR FERPA FISMA ISO27001 | This report is comprised of one element:
  • Table – Provides details on last 30 days of administrator activity
| diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/activity/security/fs_highriskactivity.md b/docs/accessanalyzer/11.6/solutions/filesystem/activity/security/fs_highriskactivity.md index bf1af5aca1..339d489bbd 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/activity/security/fs_highriskactivity.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/activity/security/fs_highriskactivity.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * **FS_HighRiskActivity** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -37,4 +37,4 @@ produces the following pre-configured report: | Report | Description | Default Tags | Report Elements | | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| High Risk Activity | High Risk Activity is any action performed by a user who has access to a particular resource only through a High Risk Trustee (for example, Everyone, Authenticated Users, or Domain Users). Unless action is taken, these users will lose access once the open access is remediated. | GDPR SOX HIPAA PCI-DSS GLBA ITAR FERPA FISMA ISO27001 | This report is comprised of three elements:
  • Pie Chart – Displays last 30 days of activity
  • Table – Provides details on activity by user
  • Table – Provides details on activity by share
| +| High Risk Activity | High Risk Activity is any action performed by a user who has access to a particular resource only through a High Risk Trustee (for example, Everyone, Authenticated Users, or Domain Users). Unless you take action, these users lose access after you remediate the open access. | GDPR SOX HIPAA PCI-DSS GLBA ITAR FERPA FISMA ISO27001 | This report is comprised of three elements:
  • Pie Chart – Displays last 30 days of activity
  • Table – Provides details on activity by user
  • Table – Provides details on activity by share
| diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/activity/security/fs_localuseractivity.md b/docs/accessanalyzer/11.6/solutions/filesystem/activity/security/fs_localuseractivity.md index 1124490e92..c83de26135 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/activity/security/fs_localuseractivity.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/activity/security/fs_localuseractivity.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * **FS_LocalUserActivity** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_deniedactivity.md b/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_deniedactivity.md index f02f62f7ed..a1b3db1ebf 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_deniedactivity.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_deniedactivity.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Activity** > **FS_DeniedActivity** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_highesthourlyactivity.md b/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_highesthourlyactivity.md index 0cf1b4b4fb..fa48cd833f 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_highesthourlyactivity.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_highesthourlyactivity.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Activity** > **FS_HighestHourlyActivity** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_hourlyshareactivity.md b/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_hourlyshareactivity.md index 75963d2589..78668d6bb6 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_hourlyshareactivity.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_hourlyshareactivity.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Activity** > **FS_HourlyShareActivity** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_modifiedbinaries.md b/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_modifiedbinaries.md index d2470d0913..59ef1304e3 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_modifiedbinaries.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_modifiedbinaries.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Activity** > **FS_ModifiedBinaries** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_peergroupactivity.md b/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_peergroupactivity.md index 859714216a..b1a6f2468c 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_peergroupactivity.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_peergroupactivity.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Activity** > **FS_PeerGroupActivity** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_ransomware.md b/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_ransomware.md index e67e79b0c9..a81268bce3 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_ransomware.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_ransomware.md @@ -8,8 +8,8 @@ sidebar_position: 60 The FS_Ransomware job is comprised of analysis and reports which use the data collected by the **0.Collection** job group to provide information on periods of time in which users are responsible -for an abnormally high number of updates. This can be indicative of ransomware. Additionally, -activity involving files which are known as ransomware artifacts is highlighted. +for an abnormally high number of updates. This can indicate ransomware. Additionally, the job +highlights activity involving files known as ransomware artifacts. ## Analysis Tasks for the FS_Ransomeware Job @@ -17,7 +17,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Activity** > **FS_Ransomware** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -40,4 +40,4 @@ the following pre-configured reports: | Report | Description | Default Tags | Report Elements | | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Ransomware Activity | This report summarizes Add or Rename activity involving known ransomware artifacts. | None | This report is comprised of three elements:
  • Bar Chart – Displays top ransomware patterns
  • Table – Provides details on ransomware activity
  • Table – Provides summary of ransomware by pattern
| -| Unusual Write Activity (Ransomware) | This report highlights periods of abnormally high update activity involving shared resources. This can be indicative of ransomware attacks. | None | This report is comprised of two elements:
  • Bar Chart – Displays abnormal update activity
  • Table – Provides details on abnormal update activity
| +| Unusual Write Activity (Ransomware) | This report highlights periods of abnormally high update activity involving shared resources. This can indicate ransomware attacks. | None | This report is comprised of two elements:
  • Bar Chart – Displays abnormal update activity
  • Table – Provides details on abnormal update activity
| diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_sensitivedataactivity.md b/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_sensitivedataactivity.md index 454b2ac227..d1786696ed 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_sensitivedataactivity.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_sensitivedataactivity.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Activity** > **FS_SensitiveDataActivity** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_stalefileactivity.md b/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_stalefileactivity.md index e223501c46..08ef3c2b7d 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_stalefileactivity.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_stalefileactivity.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Activity** > **FS_StaleFileActivity** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_usershareactivity.md b/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_usershareactivity.md index 248d566c7c..7dd54a3a1c 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_usershareactivity.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_usershareactivity.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Activity** > **FS_UserShareActivity** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_weekendactivity.md b/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_weekendactivity.md index 81b1f2ddea..f3414bb923 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_weekendactivity.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_weekendactivity.md @@ -17,7 +17,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Activity** > **FS_WeekendActivity** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/overview.md b/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/overview.md index e80d6702a6..9ce27e07a8 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/overview.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/overview.md @@ -18,9 +18,9 @@ The Suspicious Activity job group is comprised of: - Requires **Access Auditing** component data collection - [FS_HighestHourlyActivity Job](/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_highesthourlyactivity.md) - – Designed to report on the highest hourly activity event information from targeted file servers - broken down by user +- [FS_HighestHourlyActivity Job](/docs/accessanalyzer/11.6/solutions/filesystem/activity/suspiciousactivity/fs_highesthourlyactivity.md) + – Designed to report on the highest hourly activity event information from targeted file servers + broken down by user - Includes a Notification analysis task option - Requires **Access Auditing** component data collection diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/activity/usagestatistics/fs_groupusage.md b/docs/accessanalyzer/11.6/solutions/filesystem/activity/usagestatistics/fs_groupusage.md index 7393f5073d..ff21d7364a 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/activity/usagestatistics/fs_groupusage.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/activity/usagestatistics/fs_groupusage.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Statistics** > **FS_GroupUsage** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/activity/usagestatistics/fs_mostactiveservers.md b/docs/accessanalyzer/11.6/solutions/filesystem/activity/usagestatistics/fs_mostactiveservers.md index 5009e0754a..b4e56b7bb3 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/activity/usagestatistics/fs_mostactiveservers.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/activity/usagestatistics/fs_mostactiveservers.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Statistics** > **FS_MostActiveServers** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/activity/usagestatistics/fs_mostactiveusers.md b/docs/accessanalyzer/11.6/solutions/filesystem/activity/usagestatistics/fs_mostactiveusers.md index a9178b28f9..f975661f3a 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/activity/usagestatistics/fs_mostactiveusers.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/activity/usagestatistics/fs_mostactiveusers.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Statistics** > **FS_MostActiveUsers** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/activity/usagestatistics/fs_staleshares.md b/docs/accessanalyzer/11.6/solutions/filesystem/activity/usagestatistics/fs_staleshares.md index d374eb8283..abbe860392 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/activity/usagestatistics/fs_staleshares.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/activity/usagestatistics/fs_staleshares.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Statistics** > **FS_StaleShares** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/adhocaudits/fs_shareaudit.md b/docs/accessanalyzer/11.6/solutions/filesystem/adhocaudits/fs_shareaudit.md index 14d65b561f..6120cc48b8 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/adhocaudits/fs_shareaudit.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/adhocaudits/fs_shareaudit.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the FileSystem > Ad Hoc Audits > FS_Sha node and select Analysis. :::warning -Do not modify or deselect the last three selected analysis tasks. The analysis tasks +Don't modify or deselect the last three selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/adhocaudits/fs_trusteepermissions.md b/docs/accessanalyzer/11.6/solutions/filesystem/adhocaudits/fs_trusteepermissions.md index dfc918d351..82646514de 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/adhocaudits/fs_trusteepermissions.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/adhocaudits/fs_trusteepermissions.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the FileSystem > Ad Hoc Audits > FS_Tru Configure node and select Analysis. :::warning -Do not modify or deselect the second selected analysis task. The analysis task is +Don't modify or deselect the second selected analysis task. The analysis task is preconfigured for this job. ::: @@ -38,4 +38,4 @@ produces the following pre-configured report: | Report | Description | Default Tags | Report Elements | | ------------------------- | ------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Trustee Permissions Audit | This report provides an overview of the access sprawl across the environment for the select trustee(s). | None | This report is comprised of two elements:
  • Bar Chart – Displays summary of trustees
  • Table – Provides details on trustee permissions
| +| Trustee Permissions Audit | This report provides an overview of the access sprawl across the environment for the selected trustees. | None | This report is comprised of two elements:
  • Bar Chart – Displays summary of trustees
  • Table – Provides details on trustee permissions
| diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/adhocaudits/overview.md b/docs/accessanalyzer/11.6/solutions/filesystem/adhocaudits/overview.md index c7b5c12191..93214beb92 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/adhocaudits/overview.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/adhocaudits/overview.md @@ -9,7 +9,7 @@ sidebar_position: 100 The Ad Hoc Audits Job Group is designed to report on resources and trustees that have been provided by the user from targeted file servers. -The Ad Hoc Audits Job Group tables and reports are blank if the CSV file is not modified to contain +The Ad Hoc Audits Job Group tables and reports are blank if the CSV file isn't modified to contain the required information before job execution. :::info diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/delete/fs_deletefiles.md b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/delete/fs_deletefiles.md index 41461ddc7b..62cd3008a0 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/delete/fs_deletefiles.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/delete/fs_deletefiles.md @@ -11,7 +11,7 @@ previously quarantined and can be deleted. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/11.6/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -21,7 +21,7 @@ The FS_DeleteFiles job has the following configurable parameter: - Number of days without access after which a file is a deletion candidate See the -[Customizable Analysis Tasks for the FS_DeleteFiles Job](#customizable-analysis-tasks-for-the-fs_deletefiles-job) +[Customizable Analysis Tasks for the FS_DeleteFiles Job](#customizable-analysis-tasks-for-the-fsdeletefiles-job) topic for additional information. ## Analysis Tasks for the FS_DeleteFiles Job @@ -30,7 +30,7 @@ Navigate to the **FileSystem** > **Cleanup** > **4. Delete** > **FS_DeleteFiles* node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -64,7 +64,7 @@ Navigate to the **FileSystem** > **Cleanup** > **4. Delete** > **FS_DeleteFiles* node and select **Actions** to view the action tasks. :::warning -Do not enable the action unless it is required. Disable the action after execution to +Don't enable the action unless it is required. Disable the action after execution to prevent making unintended and potentially harmful changes to Active Directory. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/delete/fs_deletefiles_status.md b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/delete/fs_deletefiles_status.md index e73938dce4..3f9ba35104 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/delete/fs_deletefiles_status.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/delete/fs_deletefiles_status.md @@ -17,7 +17,7 @@ Navigate to the **FileSystem** > **Cleanup** > **4. Delete** > **FS_DeleteFiles_ **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/fs_cleanupassessment.md b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/fs_cleanupassessment.md index 8baf27bf45..936f1fd7f3 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/fs_cleanupassessment.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/fs_cleanupassessment.md @@ -35,7 +35,7 @@ have completed. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/11.6/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -49,7 +49,7 @@ The FS_CleanupAssessment job has the following configurable parameters: - Upper bound for files to be included in the FileDetails table (by LastModfied, in days) See the -[Customizable Analysis Tasks for the FS_CleanupAssessment Job](#customizable-analysis-tasks-for-the-fs_cleanupassessment-job) +[Customizable Analysis Tasks for the FS_CleanupAssessment Job](#customizable-analysis-tasks-for-the-fscleanupassessment-job) topic for additional information. ## Analysis Tasks for the FS_CleanupAssessment Job @@ -58,7 +58,7 @@ Navigate to the **FileSystem** > **Cleanup** > **1. Cleanup Assessment** > **FS_CleanupAssessment** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -73,14 +73,14 @@ The following analysis tasks are selected by default: - See the [Include Metadata Tag Information](#include-metadata-tag-information) topic for instructions on how to include metadata tag information in this table - Has 3 configurable parameters. See the - [Customizable Analysis Tasks for the FS_CleanupAssessment Job](#customizable-analysis-tasks-for-the-fs_cleanupassessment-job) + [Customizable Analysis Tasks for the FS_CleanupAssessment Job](#customizable-analysis-tasks-for-the-fscleanupassessment-job) topic for additional information. - Create file-level details table – Creates the SA_FS_CleanupAssessment_FileDetails table accessible under the job’s Results node - Has 2 configurable parameters. See the - [Customizable Analysis Tasks for the FS_CleanupAssessment Job](#customizable-analysis-tasks-for-the-fs_cleanupassessment-job) + [Customizable Analysis Tasks for the FS_CleanupAssessment Job](#customizable-analysis-tasks-for-the-fscleanupassessment-job) topic for additional information. - Summarize share-level information – Creates the SA_FS_CleanupAssessment_ShareDetails table @@ -139,7 +139,7 @@ Data Collector Wizard opens. the **Collect tags/keywords from file metadata properties** option. :::warning -Do not make changes to other wizard pages as they have been pre-configured for the +Don't make changes to other wizard pages as they have been pre-configured for the purpose of this job. ::: @@ -147,5 +147,5 @@ purpose of this job. **Step 6 –** Navigate to the **Scoping Queries** page of the File System Access Auditor Data Collector Wizard and click Finish to save the changes and close the wizard. -Metadata Tag Information will now be included in the SA_FS_CleanupView table the next time the -FS_CleanupAssessment job is run. +The SA_FS_CleanupView table now includes metadata tag information the next time you run the +FS_CleanupAssessment job. diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/fs_cleanupprogress.md b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/fs_cleanupprogress.md index bedabf0ee3..da237b7629 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/fs_cleanupprogress.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/fs_cleanupprogress.md @@ -15,7 +15,7 @@ Navigate to the **FileSystem** > **Cleanup** > **FS_CleanupProgress** > **Config select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/notify/fs_notifyowners.md b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/notify/fs_notifyowners.md index 5f73ddca06..3c6782b449 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/notify/fs_notifyowners.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/notify/fs_notifyowners.md @@ -16,7 +16,7 @@ Navigate to the **FileSystem** > **Cleanup** > **2. Notify** > **FS_NotifyOwners node and select **Actions** to view the action tasks. :::warning -Do not enable the action unless it is required. Disable the action after execution to +Don't enable the action unless it is required. Disable the action after execution to prevent making unintended and potentially harmful changes to Active Directory. ::: @@ -27,29 +27,28 @@ The following action task is deselected by default. - Notify Owners – Notifies share owners using SendMail module -Prior to running the FS_NotifyOwners job, it is necessary to select the **Notify Owners** task and +Before running the FS_NotifyOwners job, select the **Notify Owners** task and configure the properties for the SendMail action module. See the -[Configure the FS_NotifyOwners Action](#configure-the-fs_notifyowners-action) topic for additional +[Configure the FS_NotifyOwners Action](#configure-the-fsnotifyowners-action) topic for additional information. ### Configure the FS_NotifyOwners Action The recipients and the text of the email can be customized on the Properties page within the Send -Mail Action Module Wizard. The +Mail Action Module Wizard. You must run the [1. Cleanup Assessment > FS_CleanupAssessment Job](/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/fs_cleanupassessment.md) -must be run before the Send Mail Action Module Wizard can be opened. Follow these steps to customize -the Notify Owners action task. +before you can open the Send Mail Action Module Wizard. **Step 1 –** Navigate to the job’s **Configure** node and select **Actions**. -**Step 2 –** In the Action Selection view, select the desired action task and click **Action +**Step 2 –** In the Action Selection view, select the action task and click **Action Properties** to view the Action Properties page. **Step 3 –** Click **Configure Action** to open the Send Mail Action Module Wizard. :::tip -Remember, the FS_CleanupAssessment job must be run before the Send Mail Action Module Wizard can -be opened. +Remember, you must run the FS_CleanupAssessment job before you can open the Send Mail Action +Module Wizard. ::: @@ -76,5 +75,5 @@ be opened. click **Cancel** if no changes were made. Then click **OK** to close the Send Mail Action Module Wizard. -The action task has been customized. It can now be selected and run as part of the FS_NotifyOwners +You've now customized the action task. You can select and run it as part of the FS_NotifyOwners job. diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/notify/fs_notifyowners_status.md b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/notify/fs_notifyowners_status.md index 4fc0ff3f40..c0e69e669f 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/notify/fs_notifyowners_status.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/notify/fs_notifyowners_status.md @@ -17,7 +17,7 @@ Navigate to the **FileSystem** > **Cleanup** > **2. Notify** > **FS_NotifyOwners **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/overview.md b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/overview.md index f39b6ca573..a1a5025871 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/overview.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/overview.md @@ -38,8 +38,8 @@ The Cleanup job group includes the following job groups and jobs: Many jobs in this group include one or more pre-built actions designed to apply operations to the data tables generated by the job’s analysis tasks. These actions perform the cleanup operations. By -default, the actions do not execute as part of the job group. You must select the actions you want -to run prior to execution. See the +default, the actions don't execute as part of the job group. You must select the actions you want +to run before execution. See the [Action Modules](/docs/accessanalyzer/11.6/admin/action/overview.md) topic for additional information. @@ -51,7 +51,7 @@ The Cleanup job group has the following recommended configuration settings. The Cleanup job group has the following prerequisites: -- Successfully execute the **.Active Directory Inventory** job group prior to running this job group +- Successfully execute the **.Active Directory Inventory** job group before running this job group - The **File System Actions** license must be installed - Successfully execute the **FileSystem** > **0.Collection** job group with the following options enabled: @@ -68,7 +68,7 @@ dependencies. See the relevant topic for the job or job group for information ab **Target Host** -This job group does not collect data. No target host is required. +This job group doesn't collect data. No target host is required. **Schedule Frequency** diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/quarantine/fs_quarantinedata.md b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/quarantine/fs_quarantinedata.md index f82984cfdc..c02c99b014 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/quarantine/fs_quarantinedata.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/quarantine/fs_quarantinedata.md @@ -6,7 +6,7 @@ sidebar_position: 10 # FS_QuarantineData Job -The FS_QuarantineData job is designed to quarantine files subject to be cleaned up. +The FS_QuarantineData job is designed to quarantine files that are pending cleanup. ## Action Tasks for the FS_QuarantineData Job @@ -14,13 +14,13 @@ Navigate to the **FileSystem** > **Cleanup** > **3. Quarantine** > **FS_Quaranti **Configure** node and select **Actions** to view the action tasks. :::warning -Do not enable the actions unless they are required. Disable the actions after execution +Don't enable the actions unless they are required. Disable the actions after execution to prevent making unintended and potentially harmful changes to Active Directory. ::: :::warning -Do not modify the action tasks. The action tasks are preconfigured for this job. +Don't modify the action tasks. The action tasks are preconfigured for this job. ::: @@ -31,5 +31,5 @@ The following action tasks are deselected by default: - Give domain user full control – Gives a specified domain user full control over stale files - Break inherited permissions – Breaks inherited permissions -Prior to running the FS_QuarantineData job, it is necessary to select the **Give domain user full +Before running the FS_QuarantineData job, select the **Give domain user full control** or **Break inherited permissions** task to perform an action. diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/quarantine/fs_quarantinedata_status.md b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/quarantine/fs_quarantinedata_status.md index ba9e722f80..823e41b27e 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/quarantine/fs_quarantinedata_status.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/quarantine/fs_quarantinedata_status.md @@ -16,7 +16,7 @@ Navigate to the **FileSystem** > **Cleanup** > **3. Quarantine** > **FS_Quaranti **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/quarantine/fs_restoreinheritance.md b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/quarantine/fs_restoreinheritance.md index 43838f93de..8e10681951 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/quarantine/fs_restoreinheritance.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/quarantine/fs_restoreinheritance.md @@ -14,7 +14,7 @@ Navigate to the **FileSystem** > **Cleanup** > **3. Quarantine** > **FS_RestoreI **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: @@ -32,13 +32,13 @@ Navigate to the **FileSystem** > **Cleanup** > **3. Quarantine** > **FS_RestoreI **Configure** node and select **Actions** to view the action tasks. :::warning -Do not enable the action unless it is required. Disable the action after execution to +Don't enable the action unless it is required. Disable the action after execution to prevent making unintended and potentially harmful changes to Active Directory. ::: :::warning -Do not modify the action task. The action task is preconfigured for this job. +Don't modify the action task. The action task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/quarantine/fs_restoreinheritance_status.md b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/quarantine/fs_restoreinheritance_status.md index 471d1e4387..0b7d2ac3ad 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/quarantine/fs_restoreinheritance_status.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/quarantine/fs_restoreinheritance_status.md @@ -12,11 +12,11 @@ previously quarantined files. ## Analysis Tasks for the FS_RestoreInheritance_Status Job Navigate to the **FileSystem** > **Cleanup** > **3. Quarantine** > -**FS_RestoredInheritance_Status** > **Configure** node and select **Analysis** to view the analysis +**FS_RestoreInheritance_Status** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/quarantine/overview.md b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/quarantine/overview.md index 52da5e2ee4..9037f7ae09 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/quarantine/overview.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/quarantine/overview.md @@ -13,7 +13,7 @@ The 3. Quarantine job group is designed to report on and quarantine files that a This job group includes the following jobs: - [FS_QuarantineData Job](/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/quarantine/fs_quarantinedata.md) - – Designed to quarantine files subject to be cleaned up + – Designed to quarantine files that are pending cleanup - [FS_QuarantineData_Status Job](/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/quarantine/fs_quarantinedata_status.md) – Designed to report on the FS_QuarantineData job - [FS_RestoreInheritance Job](/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/quarantine/fs_restoreinheritance.md) diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/collection/0-create_schema.md b/docs/accessanalyzer/11.6/solutions/filesystem/collection/0-create_schema.md index c0ed287ddb..1d64e834d9 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/collection/0-create_schema.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/collection/0-create_schema.md @@ -8,11 +8,11 @@ sidebar_position: 10 The 0-Create Schema job within the 0.Collection job group creates and updates the schema for the tables, views, and functions used by the rest of the File System Solution. This job needs to run -prior to the other jobs in the 0.Collection job group for both new installations and upgrades. The -job can be scheduled with any of the collections. Do not delete the job from the job tree. +before the other jobs in the 0.Collection job group for both new installations and upgrades. The +job can be scheduled with any of the collections. Don't delete the job from the job tree. :::info -This job does not need to be moved. Leave it to run as part of the 0.Collection +This job doesn't need to be moved. Leave it to run as part of the 0.Collection job group. ::: @@ -23,7 +23,7 @@ View the analysis task by navigating to the **FileSystem** > **0.Collection** > Schema** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/collection/0-fs_nasuni.md b/docs/accessanalyzer/11.6/solutions/filesystem/collection/0-fs_nasuni.md index e8f29fec21..6bb11fdff1 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/collection/0-fs_nasuni.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/collection/0-fs_nasuni.md @@ -6,23 +6,22 @@ sidebar_position: 30 # 0-FS_Nasuni Job -The 0-FS_Nasuni job is required in order to target Nasuni Edge Appliances. The job can be added from +You need the 0-FS_Nasuni job to target Nasuni Edge Appliances. The job can be added from the Enterprise Auditor Instant Job Library. See the [Instant Job Wizard](/docs/accessanalyzer/11.6/admin/jobs/instantjobs/overview.md) topic to add this instant job to the 0.Collection job group. :::warning -It is necessary to rename the job after it has been added to the 0.Collection job group -from **FS_Nasuni** to **0-FS_Nasuni**, so that it runs immediately after the 0-Create Schema job. +After you add the job to the 0.Collection job group, rename it from **FS_Nasuni** to +**0-FS_Nasuni** so it runs immediately after the 0-Create Schema job. ::: :::tip -Remember, the 0-FS_Nasuni job must be assigned a custom host list containing all on-premise Nasuni -Edge Appliances and cloud filers, and a custom Connection Profile containing the API Access Key and -Passcode for each on-premise Nasuni Edge Appliance and cloud filer in the target environment. Nasuni -API key names are case sensitive. When providing them, ensure they are entered in the exact same -case as generated. +Assign the 0-FS_Nasuni job a custom host list containing all on-premise Nasuni Edge Appliances and +cloud filers, and a custom Connection Profile containing the API Access Key and Passcode for each +on-premise Nasuni Edge Appliance and cloud filer in the target environment. Nasuni API key names are +case sensitive. When providing them, ensure they are entered in the exact same case as generated. ::: @@ -32,7 +31,7 @@ The queries for the 0-FS_Nasuni job use the PowerShell Data collector to gather volume data, and share data from the Nasuni environment. :::warning -Do not modify the queries. The queries are preconfigured for this job. +Don't modify the queries. The queries are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/collection/0-fsdfs_system_scans.md b/docs/accessanalyzer/11.6/solutions/filesystem/collection/0-fsdfs_system_scans.md index 47200ae627..845e016149 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/collection/0-fsdfs_system_scans.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/collection/0-fsdfs_system_scans.md @@ -7,7 +7,7 @@ sidebar_position: 20 # 0-FSDFS System Scans Job The 0-FSDFS System Scans job enumerates a list of all root and link targets in the distributed file -system and creating a dynamic host list that will be used by the components. +system and creates a dynamic host list used by the components. ## Query for the 0-FSDFS System Scans Job @@ -15,7 +15,7 @@ The DFS System Scan Query uses the FSAA Data Collector and has been preconfigure Scan Category. :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -29,7 +29,7 @@ View the analysis tasks by navigating to the **FileSystem** > **0.Collection** > Scans** > **Configure** node and selecting **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/collection/1-fsaa_system_scans.md b/docs/accessanalyzer/11.6/solutions/filesystem/collection/1-fsaa_system_scans.md index 411ac5c5b1..d0fea6de76 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/collection/1-fsaa_system_scans.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/collection/1-fsaa_system_scans.md @@ -93,7 +93,7 @@ topic for additional information. ![Default Scoping Options](/images/accessanalyzer/11.6/solutions/filesystem/collection/fsaadefaultscopingoptions.webp) -**Step 8 –** On the Default Scoping Options page, configure the following on the Scan Setting tab: +**Step 8 –** On the Default Scoping Options page, configure the following on the Scan Settings tab: - Limit subfolder scan depth to – Select this checkbox and use the arrow buttons to modify the subfolder scan depth @@ -105,15 +105,15 @@ topic for additional information. - Action on failure to enable LAT Preservation – Before scanning each file, FSAA attempts to enable an operating system feature to preserve the LAT when accessing the file. This operation - may fail for a variety of reasons, which include but aren't limited to: the operating system - or file system where the file is located doesn't support LAT preservation, or insufficient - permissions from the service account trying to access the file. The following configuration - addresses a failure to enable the LAT preservation mode: - - - Continue to scan file silently – FSAA scans the file with the possibility that LAT - preservation isn't possible. No warning appears. - - Continue to scan file with warning – FSAA scans the file with the possibility that LAT - will not be preserved. A warning appears for this file. + may fail for a variety of reasons, including: the operating system or file system where the + file is located doesn't support LAT preservation, or insufficient permissions from the + service account trying to access the file. The following configuration addresses a failure + to enable the LAT preservation mode: + + - Continue to scan file silently – FSAA scans the file even if LAT preservation isn't + possible. No warning appears. + - Continue to scan file with warning – FSAA scans the file even if LAT isn't preserved. A + warning appears for this file. - Skip file silently – FSAA will not scan the file. No warning appears. - Skip file with warning – FSAA will not scan the file. A warning appears indicating the file was skipped. @@ -131,7 +131,7 @@ topic for additional information. updated for the processed file. A warning appears. - Force-reset file LAT silently – The scan will reset the file's LAT to its original state before processing. No warning appears. The scan will proceed to the next file. - - Force-reset file LAT with warning – The scan will Reset the file's LAT to its original + - Force-reset file LAT with warning – The scan will reset the file's LAT to its original state before processing. A warning appears. The scan will proceed to the next file. - Abort the scan – FSAA will abort the scan. LAT will be updated for the processed file. No other files will be processed @@ -145,6 +145,7 @@ topic for additional information. **Step 9 –** On the File Details tab of the Default Scoping Options page, you can enable file-level scans. See the [File Details Tab](/docs/accessanalyzer/11.6/admin/datacollector/fsaa/defaultscopingoptions/filedetails.md) +topic for additional information. :::info Carefully consider configuring the following settings. Applying filters after you enable diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/collection/1-fsac_system_scans.md b/docs/accessanalyzer/11.6/solutions/filesystem/collection/1-fsac_system_scans.md index 27ce8c81e5..975422a667 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/collection/1-fsac_system_scans.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/collection/1-fsac_system_scans.md @@ -57,7 +57,7 @@ purpose of this job. ![Applet Settings](/images/accessanalyzer/11.6/solutions/filesystem/collection/fsacappletsettings.webp) **Step 4 –** The Applet Settings page applies to the applet and proxy mode scans which you select -on the Scan Server Level Page. If employing proxy servers, see the +on the Scan Server Selection page. If employing proxy servers, see the [FSAA: Applet Settings](/docs/accessanalyzer/11.6/admin/datacollector/fsaa/appletsettings/appletsettings.md) topic for configuration instructions. diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/collection/1-seek_system_scans.md b/docs/accessanalyzer/11.6/solutions/filesystem/collection/1-seek_system_scans.md index e866fb5f9c..360928d132 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/collection/1-seek_system_scans.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/collection/1-seek_system_scans.md @@ -77,7 +77,7 @@ purpose of this job. ![Applet Settings](/images/accessanalyzer/11.6/solutions/filesystem/collection/fsaaseekappletsettings.webp) **Step 4 –** The Applet Settings page applies to the applet and proxy mode scans which you select -on the Scan Server Level page. If employing proxy servers, see the +on the Scan Server Selection page. If employing proxy servers, see the [FSAA: Applet Settings](/docs/accessanalyzer/11.6/admin/datacollector/fsaa/appletsettings/appletsettings.md) topic for configuration instructions. @@ -109,7 +109,7 @@ topic for additional information. ![Default Scoping Options](/images/accessanalyzer/11.6/solutions/filesystem/collection/seekdefaultscopingoptions.webp) -**Step 8 –** On the Default Scoping Options page, configure the following on the Scan Setting tab: +**Step 8 –** On the Default Scoping Options page, configure the following on the Scan Settings tab: - Limit subfolder scan depth to – Select this checkbox and use the arrow buttons to modify the subfolder scan depth @@ -122,15 +122,15 @@ topic for additional information. - Action on failure to enable LAT Preservation – Before scanning each file, FSAA attempts to enable an operating system feature to preserve the LAT when accessing the file. This operation - may fail for a variety of reasons, which include but aren't limited to: the operating system - or file system where the file is located doesn't support LAT preservation, or insufficient - permissions from the service account trying to access the file. The following configuration - addresses a failure to enable the LAT preservation mode: - - - Continue to scan file silently – FSAA scans the file with the possibility that LAT - preservation isn't possible. No warning appears. - - Continue to scan file with warning – FSAA scans the file with the possibility that LAT - will not be preserved. A warning appears for this file. + may fail for a variety of reasons, including: the operating system or file system where the + file is located doesn't support LAT preservation, or insufficient permissions from the + service account trying to access the file. The following configuration addresses a failure + to enable the LAT preservation mode: + + - Continue to scan file silently – FSAA scans the file even if LAT preservation isn't + possible. No warning appears. + - Continue to scan file with warning – FSAA scans the file even if LAT isn't preserved. A + warning appears for this file. - Skip file silently – FSAA will not scan the file. No warning appears. - Skip file with warning – FSAA will not scan the file. A warning appears indicating the file was skipped. @@ -148,7 +148,7 @@ topic for additional information. updated for the processed file. A warning appears. - Force-reset file LAT silently – The scan will reset the file's LAT to its original state before processing. No warning appears. The scan will proceed to the next file. - - Force-reset file LAT with warning – The scan will Reset the file's LAT to its original + - Force-reset file LAT with warning – The scan will reset the file's LAT to its original state before processing. A warning appears. The scan will proceed to the next file. - Abort the scan – FSAA will abort the scan. LAT will be updated for the processed file. No other files will be processed diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/collection/2-fsaa_bulk_import.md b/docs/accessanalyzer/11.6/solutions/filesystem/collection/2-fsaa_bulk_import.md index e8192a15c2..45fde280b4 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/collection/2-fsaa_bulk_import.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/collection/2-fsaa_bulk_import.md @@ -18,7 +18,7 @@ access/permission auditing Bulk import category. - Bulk import – Imports scan data into SQL Server - - Typically, this query is not modified. See the + - Typically, this query isn't modified. See the [FileSystemAccess Data Collector](/docs/accessanalyzer/11.6/admin/datacollector/fsaa/overview.md) topic for information on when this query should be modified. @@ -28,7 +28,7 @@ View the analysis tasks by navigating to the **FileSystem** > **0.Collection** > Import** > **Configure** node and selecting **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/collection/2-fsac_bulk_import.md b/docs/accessanalyzer/11.6/solutions/filesystem/collection/2-fsac_bulk_import.md index db660acdd9..3aa66ced7b 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/collection/2-fsac_bulk_import.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/collection/2-fsac_bulk_import.md @@ -18,6 +18,6 @@ activity Bulk import category. - Bulk Import – Imports data into SQL Server - - Typically this query is not modified. See the + - Typically this query isn't modified. See the [FileSystemAccess Data Collector](/docs/accessanalyzer/11.6/admin/datacollector/fsaa/overview.md) topic for information on when this query should be modified. diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/collection/2-seek_bulk_import.md b/docs/accessanalyzer/11.6/solutions/filesystem/collection/2-seek_bulk_import.md index 7ad0e8df14..b37913cfe6 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/collection/2-seek_bulk_import.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/collection/2-seek_bulk_import.md @@ -18,6 +18,6 @@ data Bulk import category. - Bulk Import – Imports data into SQL server - - Typically this query is not modified. See the + - Typically this query isn't modified. See the [FileSystemAccess Data Collector](/docs/accessanalyzer/11.6/admin/datacollector/fsaa/overview.md) topic for information on when this query should be modified. diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/collection/3-fsaa_exceptions.md b/docs/accessanalyzer/11.6/solutions/filesystem/collection/3-fsaa_exceptions.md index df8b9dd8ef..7a97fe9cd6 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/collection/3-fsaa_exceptions.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/collection/3-fsaa_exceptions.md @@ -6,19 +6,19 @@ sidebar_position: 100 # 3-FSAA Exceptions Job -The 3-FSAA Exceptions job does not use the FSAA Data Collector. Instead it runs analysis on the data +The 3-FSAA Exceptions job doesn't use the FSAA Data Collector. Instead it runs analysis on the data returned by the Access Auditing collection jobs to identify potential security concerns. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/11.6/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. The 3-FSAA Exceptions job has the following customizable parameter: -- Well Known high risk SIDS – Add any additional custom SIDS, but do not remove the default SIDS. +- Well Known high risk SIDS – Add any additional custom SIDS, but don't remove the default SIDS. See the [Analysis Tasks for the 3-FSAA Exceptions Job](#analysis-tasks-for-the-3-fsaa-exceptions-job) topic @@ -30,8 +30,8 @@ View the analysis tasks by navigating to the **FileSystem** > **0.Collection** > Exceptions** > **Configure** node and select **Analysis**. :::warning -Most of these analysis tasks are preconfigured and should not be modified and or -deselected. While it is possible to deselect particular tasks as specified, it is not recommended. +Most of these analysis tasks are preconfigured and shouldn't be modified and/or +deselected. You can deselect particular tasks as specified, but doing so isn't recommended. ::: @@ -39,22 +39,22 @@ deselected. While it is possible to deselect particular tasks as specified, it i The following analysis tasks are selected by default: -- Open resources – Any folders that are openly accessible through file shares. Can be deselected if - open resource information is not desired. +- Open resources – Any folders that are openly accessible through file shares. Deselect this task + if you don't need open resource information. - - Well known high risk SIDS have been set in the `#SIDS` parameter. Do not remove these, but - additional custom SIDS can be added. See the + - The `#SIDS` parameter includes well-known, high-risk SIDS by default. Don't remove these, + but you can add custom SIDS. See the [Configure the Customizable Parameters in an Analysis Task](/docs/accessanalyzer/11.6/admin/jobs/job/configure/analysis/analysiscustomizableparameters.md) topic for additional information. -- Disabled users – Any folders where disabled users have been granted access +- Disabled users – Any folders where disabled users have access - - Can be deselected if disabled user information is not desired + - Deselect this task if you don't need disabled user information -- Stale users – Any folders where stale users have been granted access. Stale users are user who - have not logged in for more than 120 days. +- Stale users – Any folders where stale users have access. Stale users are users who haven't + logged in for more than 120 days. - - Can be deselected if stale user information is not desired + - Deselect this task if you don't need stale user information - Reindex Exception IDs – Displays views within the **Results** node of the Enterprise Auditor Console diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/collection/3-fsac_exceptions.md b/docs/accessanalyzer/11.6/solutions/filesystem/collection/3-fsac_exceptions.md index 58e7e58927..5f77a12552 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/collection/3-fsac_exceptions.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/collection/3-fsac_exceptions.md @@ -10,7 +10,7 @@ The 3-FSAC Exceptions job is designed to analyze collected access information fo ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/11.6/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -25,7 +25,7 @@ View the analysis tasks by navigating to the **FileSystem** > **0.Collection** > Exceptions** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -44,7 +44,7 @@ The following analysis tasks are selected by default: - Ransomware – Spikes in updates by user - Unusual user stale data activity – Spikes in stale data activity by user -While it is possible to deselect particular tasks as specified, it is not recommended. The following +You can deselect particular tasks as specified, but doing so isn't recommended. The following analysis tasks are deselected by default: - Show view – Displays the SA_FSAC_ExceptionsView within the Results node of the Enterprise Auditor @@ -54,7 +54,7 @@ analysis tasks are deselected by default: ### Customizable Analysis Tasks for the 3-FSAC Exceptions Job -Customizable parameters enable users to set the values used for classification during the job’s +Customizable parameters let you set the values used for classification during the job’s analysis. The 3-FSAC Exceptions job contains the following customizable parameters: | Analysis Task | Customizable Parameter Name | Default Value | Value Indicates | diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/collection/overview.md b/docs/accessanalyzer/11.6/solutions/filesystem/collection/overview.md index 407a3718e4..000a7dfd00 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/collection/overview.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/collection/overview.md @@ -24,7 +24,7 @@ The 0.Collection job group has the following collection components: [File System DFS Auditing](#file-system-dfs-auditing) topic for additional information. - File System Activity Auditing (FSAC) component – Collects event information logged by the Activity Monitor. This component requires an additional installer package before data collection will - occur. It should be run in conjunction with the FSAA component and employs the **1-FSAC System + occur. It should run in conjunction with the FSAA component and employs the **1-FSAC System Scans** job, the **2-FSAC Bulk Import** job, and the **3-FSAC Exceptions** job. See the [File System Activity Auditing](#file-system-activity-auditing) topic for additional information. - File System Sensitive Data Discovery Auditing (SEEK) component – Searches file content for @@ -34,7 +34,7 @@ The 0.Collection job group has the following collection components: [File System Sensitive Data Discovery Auditing (SEEK)](#file-system-sensitive-data-discovery-auditing-seek) topic for additional information. -These jobs are numbered to keep them in the necessary run order. Not all jobs need be run. See the +Job numbers indicate the required run order. You don't need to run every job. See the appropriate auditing topic for specific job relationships and recommended workflows. The 0-Create Schema job ensures the database schema is properly configured for the current version of the data collector. See the @@ -47,18 +47,18 @@ considerations: ::: -- A system scans job executed from a Enterprise Auditor Console must be followed by the - corresponding bulk import job from the same Enterprise Auditor Console with the same version of - Enterprise Auditor -- Two system scans processing the same information, for example two 1-FSAA System Scans jobs, cannot - be executed consecutively against the same target host. The corresponding bulk import job, for - example 2-FSAA Bulk Import job, must be executed in between. +- You must follow a system scans job executed from an Enterprise Auditor Console with the + corresponding bulk import job from the same Enterprise Auditor Console and version of Enterprise + Auditor +- Don't execute two system scans jobs that process the same information, for example two 1-FSAA + System Scans jobs, consecutively against the same target host. Execute the corresponding bulk + import job, for example the 2-FSAA Bulk Import job, in between. The system scans job collects the data and creates a Tier-2 database, or SQLite database, on the local host, target host, or proxy host (according to the Applet Gathering Settings configured). The corresponding bulk import job gathers the information from the Tier-2 database, and pulls it into the Tier-1 database, or Enterprise Auditor SQL backend database, thus completing the collection -process. The collection does not include a bulk import job, as it streams the collected data +process. The collection doesn't include a bulk import job, as it streams the collected data directly into the Tier-1 database. ## File System Access Auditing @@ -76,7 +76,7 @@ The 0.Collection jobs that comprise this auditing component are: - [2-FSAA Bulk Import Job](/docs/accessanalyzer/11.6/solutions/filesystem/collection/2-fsaa_bulk_import.md) – Imports collected access information from the targeted file servers - - The 2-FSAA Bulk Import job does not need to be run when streaming is enabled + - The 2-FSAA Bulk Import job doesn't need to be run when streaming is enabled - [3-FSAA Exceptions Job](/docs/accessanalyzer/11.6/solutions/filesystem/collection/3-fsaa_exceptions.md) – Analyzes collected access information for exceptions @@ -106,7 +106,7 @@ for additional information. It is more efficient to streamline the collection jobs to those desired. Remember, it is a best practice to scope the 0.Collection job group to only include the collection components desired by disabling the undesired collection jobs. Disabling them allows the solution to run more efficiently. -It is not recommended to delete any jobs. The required collection jobs are listed for the following +It isn't recommended to delete any jobs. The required collection jobs are listed for the following workflow. **Workflow (for Access Auditing only)** @@ -117,9 +117,9 @@ The recommended workflow for Access Auditing only is as follows: **Step 2 –** If necessary, run the **2-FSAA Bulk Import** job: -- If streaming is not enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** +- If streaming isn't enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** job. -- If streaming is enabled in the **1-FSAA System Scans** job, do not run **2-FSAA Bulk Import** job. +- If streaming is enabled in the **1-FSAA System Scans** job, don't run **2-FSAA Bulk Import** job. :::info It is best practice to disable undesired Bulk Import jobs. @@ -128,10 +128,10 @@ The recommended workflow for Access Auditing only is as follows: **Step 3 –** Run the **3-FSAA Exceptions** job. -**Step 4 –** Run the desired corresponding analysis and reporting sub-job groups. +**Step 4 –** Run the applicable analysis and reporting sub-job groups. :::note -Please see the +See the [Recommended Configuration for the File System Solution](/docs/accessanalyzer/11.6/solutions/filesystem/recommended.md) topic before continuing with this workflow. ::: @@ -168,8 +168,9 @@ The 0.Collection jobs that comprise the DFS auditing component are: namespaces - When run successfully, the 0-FSDFS System Scans job automatically creates a dynamic host list - called **DFS HOST LIST**. This is added to the Host Management node. You should assign this - **DFS HOST LIST** to other 0.Collection jobs as outlined in the recommended workflows below. + called **DFS HOST LIST** and adds it to the Host Management node. You should assign this + **DFS HOST LIST** to other 0.Collection jobs as outlined in the recommended workflows that + follow. The components depend on data collected by these jobs to collect within a file system using DFS mappings. @@ -177,17 +178,16 @@ mappings. It is more efficient to streamline the collection jobs to those desired. Remember, it is a best practice to scope the 0.Collection job group to only include the collection components desired by disabling the undesired collection jobs. Disabling them allows the solution to run more efficiently. -It is not recommended to delete any jobs. The required collection jobs are listed for each of the +It isn't recommended to delete any jobs. The required collection jobs are listed for each of the following optional workflows. :::warning -The DFS Auditing component must always be run in conjunction with the Access Auditing -component. Access audits are necessary to resolve the target shares and folders of DFS link -destinations. +Always run the DFS Auditing component in conjunction with the Access Auditing component. Access +audits resolve the target shares and folders of DFS link destinations. ::: -**Recommended Workflow 1 (for AccessAuditing with DFS Auditing)** +**Recommended Workflow 1 (for Access Auditing with DFS Auditing)** **Step 1 –** Run the **0-FSDFS System Scans** job. @@ -195,9 +195,9 @@ destinations. **Step 3 –** If necessary, run the **2-FSAA Bulk Import** job (with the **DFS HOST LIST** assigned): -- If streaming is not enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** +- If streaming isn't enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** job. -- If streaming is enabled in the **1-FSAA System Scans** job, do not run **2-FSAA Bulk Import** job. +- If streaming is enabled in the **1-FSAA System Scans** job, don't run **2-FSAA Bulk Import** job. :::info It is best practice to disable undesired Bulk Import jobs. @@ -207,9 +207,9 @@ destinations. **Step 4 –** Run the **3-FSAA Exceptions** job (not specifically needed for DFS Auditing, but recommended for **0.Collection** job group). -**Step 5 –** Run the desired corresponding analysis and reporting sub-job groups. +**Step 5 –** Run the applicable analysis and reporting sub-job groups. -Recommended Workflow 2 (for AccessAuditing with DFS Auditing and Activity Auditing) +Recommended Workflow 2 (for Access Auditing with DFS Auditing and Activity Auditing) **Step 1 –** Install and configure monitoring with the Activity Monitor for targeted hosts (once only). @@ -222,9 +222,9 @@ only). **Step 5 –** If necessary, run the **2-FSAA Bulk Import** job (with the **DFS HOST LIST** assigned): -- If streaming is not enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** +- If streaming isn't enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** job. -- If streaming is enabled in the **1-FSAA System Scans** job, do not run **2-FSAA Bulk Import** job. +- If streaming is enabled in the **1-FSAA System Scans** job, don't run **2-FSAA Bulk Import** job. :::info It is best practice to disable undesired Bulk Import jobs. @@ -237,10 +237,10 @@ only). **Step 8 –** Run the **3-FSAC Exceptions** job. -**Step 9 –** Run the desired corresponding analysis and reporting sub-job groups. +**Step 9 –** Run the applicable analysis and reporting sub-job groups. -Recommended Workflow 3 (for AccessAuditing with DFS Auditing, Activity, and Sensitive Data Discovery -Auditing) +Recommended Workflow 3 (for Access Auditing with DFS Auditing, Activity, and Sensitive Data +Discovery Auditing) **Step 1 –** Install the Sensitive Data Discovery Add-On on the Enterprise Auditor Console (once only). @@ -258,9 +258,9 @@ only). **Step 7 –** If necessary, run the **2-FSAA Bulk Import** job (with the **DFS HOST LIST** assigned): -- If streaming is not enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** +- If streaming isn't enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** job. -- If streaming is enabled in the **1-FSAA System Scans** job, do not run **2-FSAA Bulk Import** job. +- If streaming is enabled in the **1-FSAA System Scans** job, don't run **2-FSAA Bulk Import** job. :::info It is best practice to disable undesired Bulk Import jobs. @@ -271,9 +271,9 @@ only). **Step 9 –** If necessary, run the **2-SEEK Bulk Import** job (with the **DFS HOST LIST** assigned): -- If streaming is not enabled in the **1-SEEK System Scans** job, run the **2-SEEK Bulk Import** +- If streaming isn't enabled in the **1-SEEK System Scans** job, run the **2-SEEK Bulk Import** job. -- If streaming is enabled in the **1-SEEK System Scans** job, do not run the **2-SEEK Bulk Import** +- If streaming is enabled in the **1-SEEK System Scans** job, don't run the **2-SEEK Bulk Import** job. :::info @@ -285,10 +285,10 @@ only). **Step 11 –** Run the **3-FSAC Exceptions** job. -**Step 12 –** Run the desired corresponding analysis and reporting sub-job groups. +**Step 12 –** Run the applicable analysis and reporting sub-job groups. :::note -Please see the +See the [Recommended Configuration for the File System Solution](/docs/accessanalyzer/11.6/solutions/filesystem/recommended.md) topic before continuing with these workflows. ::: @@ -308,23 +308,23 @@ specifically incorporated into this component are prefixed with `FSAC`. See the topic for additional information on the data collected. :::note -The Activity Auditing component requires the Activity Monitor be deployed, configured, and -have services running on the target hosts. See the +The Activity Auditing component requires the Activity Monitor to be deployed and configured, with +services running on the target hosts. See the [Netwrix Activity Monitor Documentation](https://helpcenter.netwrix.com/category/activitymonitor) for additional information. ::: -Once the Activity Monitor is installed, the monitored host configuration tells it what to monitor +After the Activity Monitor is installed, the monitored host configuration tells it what to monitor and how long to retain the activity log files. The monitoring agent writes one log per day of activity for the host. Then, the FSAA Data Collector gathers the log files to report on file system activity for the targeted host. While the Activity Monitor can be configured to create multiple outputs, Enterprise Auditor can only collect one log file per host. Therefore, after the monitored -host has been configured, it is necessary to identify the log file for Enterprise Auditor. See the +host has been configured, identify the log file for Enterprise Auditor. See the [Identify a Log File](#identify-a-log-file) topic for additional information. -The data retention period needs to be coordinated between the Activity Monitor and Enterprise -Auditor. The number of days theActivity Monitor is configured to retain log files must be higher +You need to coordinate the data retention period between the Activity Monitor and Enterprise +Auditor. The number of days the Activity Monitor is configured to retain log files must be higher than the number of days between Activity Auditing scans. The FSAA Data Collector can be customized on the Activity Settings page of the File System Access Auditor Data Collector Wizard. See the [Configure the Activity Scan Query](/docs/accessanalyzer/11.6/solutions/filesystem/collection/1-fsac_system_scans.md#configure-the-activity-scan-query) @@ -367,7 +367,7 @@ for additional information. It is more efficient to streamline the collection jobs to those desired. Remember, it is a best practice to scope the 0.Collection job group to only include the collection components desired by disabling the undesired collection jobs. Disabling them allows the solution to run more efficiently. -It is not recommended to delete any jobs. The required collection jobs are listed for each of the +It isn't recommended to delete any jobs. The required collection jobs are listed for each of the following optional workflows. **Recommended Workflow 1 (for Access and Activity Auditing)** @@ -381,9 +381,9 @@ only). **Step 4 –** If necessary, run the **2-FSAA Bulk Import** job: -- If streaming is not enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** +- If streaming isn't enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** job. -- If streaming is enabled in the **1-FSAA System Scans** job, do not run **2-FSAA Bulk Import** job. +- If streaming is enabled in the **1-FSAA System Scans** job, don't run **2-FSAA Bulk Import** job. :::info It is best practice to disable undesired Bulk Import jobs. @@ -396,7 +396,7 @@ only). **Step 7 –** Run the **3-FSAC Exceptions** job. -**Step 8 –** Run the desired corresponding analysis and reporting sub-job groups. +**Step 8 –** Run the applicable analysis and reporting sub-job groups. Recommended Workflow 2 (for Access, Activity, and Sensitive Data Discovery Auditing) @@ -414,9 +414,9 @@ only). **Step 6 –** If necessary, run the **2-FSAA Bulk Import** job: -- If streaming is not enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** +- If streaming isn't enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** job. -- If streaming is enabled in the **1-FSAA System Scans** job, do not run **2-FSAA Bulk Import** job. +- If streaming is enabled in the **1-FSAA System Scans** job, don't run **2-FSAA Bulk Import** job. :::info It is best practice to disable undesired Bulk Import jobs. @@ -427,9 +427,9 @@ only). **Step 8 –** If necessary, run the **2-SEEK Bulk Import** job: -- If streaming is not enabled in the **1-SEEK System Scans** job, run the **2-SEEK Bulk Import** +- If streaming isn't enabled in the **1-SEEK System Scans** job, run the **2-SEEK Bulk Import** job. -- If streaming is enabled in the **1-SEEK System Scans** job, do not run the **2-SEEK Bulk Import** +- If streaming is enabled in the **1-SEEK System Scans** job, don't run the **2-SEEK Bulk Import** job. :::info @@ -441,7 +441,7 @@ only). **Step 10 –** Run the **3-FSAC Exceptions** job. -**Step 11 –** Run the desired corresponding analysis and reporting sub-job groups. +**Step 11 –** Run the applicable analysis and reporting sub-job groups. Recommended Workflow 3 (for Access, Activity, DFS, and Sensitive Data Discovery Auditing) @@ -461,9 +461,9 @@ only). **Step 7 –** If necessary, run the **2-FSAA Bulk Import** job: -- If streaming is not enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** +- If streaming isn't enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** job. -- If streaming is enabled in the **1-FSAA System Scans** job, do not run **2-FSAA Bulk Import** job. +- If streaming is enabled in the **1-FSAA System Scans** job, don't run **2-FSAA Bulk Import** job. :::info It is best practice to disable undesired Bulk Import jobs. @@ -474,9 +474,9 @@ only). **Step 9 –** If necessary, run the **2-SEEK Bulk Import** job: -- If streaming is not enabled in the **1-SEEK System Scans** job, run the **2-SEEK Bulk Import** +- If streaming isn't enabled in the **1-SEEK System Scans** job, run the **2-SEEK Bulk Import** job. -- If streaming is enabled in the **1-SEEK System Scans** job, do not run the **2-SEEK Bulk Import** +- If streaming is enabled in the **1-SEEK System Scans** job, don't run the **2-SEEK Bulk Import** job. :::info @@ -488,7 +488,7 @@ only). **Step 11 –** Run the **3-FSAC Exceptions** job. -**Step 12 –** Run the desired corresponding analysis and reporting sub-job groups. +**Step 12 –** Run the applicable analysis and reporting sub-job groups. Optional Workflow (for Activity Auditing data collection only ) @@ -504,10 +504,10 @@ only). **Step 4 –** Run the **3-FSAC Exceptions** job. -**Step 5 –** Run the desired corresponding analysis and reporting sub-job groups. +**Step 5 –** Run the applicable analysis and reporting sub-job groups. :::note -Please see the +See the [Recommended Configuration for the File System Solution](/docs/accessanalyzer/11.6/solutions/filesystem/recommended.md) topic before continuing with these workflows. ::: @@ -517,8 +517,7 @@ topic before continuing with these workflows. While the Activity Monitor can have multiple configurations per host, Enterprise Auditor can only read one of them. Therefore, after the Activity Monitor has been configured to monitor a host, it is -necessary to indicate when that configuration is for Enterprise Auditor. Follow these steps to -identify the Log file to be read by Enterprise Auditor. +necessary to indicate when that configuration is for Enterprise Auditor. **Step 1 –** Within the Activity Monitor Console on the **Monitored Hosts** tab, select the desired configuration and click **Edit**. @@ -554,7 +553,7 @@ topic for additional information. ::: -Customized search criteria can be created with the Criteria Editor accessible through the SDD +You can create customized search criteria with the Criteria Editor accessible through the SDD Criteria Settings page of the File System Access Auditor Data Collector Wizard. See the [Configure the (SEEK) File System Scan Query](/docs/accessanalyzer/11.6/solutions/filesystem/collection/1-seek_system_scans.md#configure-the-seek-file-system-scan-query) topic for additional information. @@ -569,14 +568,14 @@ topic for additional information. **Option to Enable Last Access Timestamp** -The Last Access Timestamp (LAT) is disabled by default in Windows. This means the LAT does not get -updated by any applications reading the file. As soon as the LAT feature is enabled in Windows, any +The Last Access Timestamp (LAT) is disabled by default in Windows. This means applications that +read the file don't update the LAT. As soon as the LAT feature is enabled in Windows, any attempt to read file contents updates the LAT. It stores the time of the last read operation. -Since files are read during the Sensitive Data Discovery Auditing scan,when the feature is enabled -in Windows the scan causes each file's LAT to update each time the file is scanned. Therefore, there -is a feature within the job XML file which enables the scan to call a special API in order to keep -each file's LAT from updating when it's scanned. This feature can be enabled by adding +Since files are read during the Sensitive Data Discovery Auditing scan, when the feature is enabled +in Windows the scan causes each file's LAT to update each time the file is scanned. Therefore, the +job XML file includes a feature that lets the scan call a special API to prevent each file's LAT +from updating when it's scanned. You can enable this feature by adding the `` tag to the XML. See the [1-SEEK System Scans Job](/docs/accessanalyzer/11.6/solutions/filesystem/collection/1-seek_system_scans.md) topic for additional information and instructions. @@ -597,7 +596,7 @@ The 0.Collection jobs that comprise this auditing component are: - [2-SEEK Bulk Import Job](/docs/accessanalyzer/11.6/solutions/filesystem/collection/2-seek_bulk_import.md) – Imports collected sensitive data information from the targeted file servers - - The 2-SEEK Bulk Import job does not need to be run when streaming is enabled + - The 2-SEEK Bulk Import job doesn't need to be run when streaming is enabled The following job group and jobs in the File System solution depend on data collected by these jobs to generate reports: @@ -615,7 +614,7 @@ for additional information. It is more efficient to streamline the collection jobs to those desired. Remember, it is a best practice to scope the 0.Collection job group to only include the collection components desired by disabling the undesired collection jobs. Disabling them allows the solution to run more efficiently. -It is not recommended to delete any jobs. The required collection jobs are listed for the following +It isn't recommended to delete any jobs. The required collection jobs are listed for the following workflows. Recommended Workflow 1 (for Access and Sensitive Data Discovery Auditing data collection) @@ -635,9 +634,9 @@ only). **Step 4 –** If necessary, run the **2-FSAA Bulk Import** job: -- If streaming is not enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** +- If streaming isn't enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** job. -- If streaming is enabled in the **1-FSAA System Scans** job, do not run **2-FSAA Bulk Import** job. +- If streaming is enabled in the **1-FSAA System Scans** job, don't run **2-FSAA Bulk Import** job. :::info It is best practice to disable undesired Bulk Import jobs. @@ -646,9 +645,9 @@ only). **Step 5 –** If necessary, run the **2-SEEK Bulk Import** job: -- If streaming is not enabled in the **1-SEEK System Scans** job, run the **2-SEEK Bulk Import** +- If streaming isn't enabled in the **1-SEEK System Scans** job, run the **2-SEEK Bulk Import** job. -- If streaming is enabled in the **1-SEEK System Scans** job, do not run the **2-SEEK Bulk Import** +- If streaming is enabled in the **1-SEEK System Scans** job, don't run the **2-SEEK Bulk Import** job. :::info @@ -658,7 +657,7 @@ only). **Step 6 –** Run the **3-FSAA Exceptions** job. -**Step 7 –** Run the desired corresponding analysis and reporting sub-job groups. +**Step 7 –** Run the applicable analysis and reporting sub-job groups. Recommended Workflow 2 (for Access, Activity, and Sensitive Data Discovery Auditing) @@ -676,9 +675,9 @@ only). **Step 6 –** If necessary, run the **2-FSAA Bulk Import** job: -- If streaming is not enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** +- If streaming isn't enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** job. -- If streaming is enabled in the **1-FSAA System Scans** job, do not run **2-FSAA Bulk Import** job. +- If streaming is enabled in the **1-FSAA System Scans** job, don't run **2-FSAA Bulk Import** job. :::info It is best practice to disable undesired Bulk Import jobs. @@ -689,9 +688,9 @@ only). **Step 8 –** If necessary, run the **2-SEEK Bulk Import** job: -- If streaming is not enabled in the **1-SEEK System Scans** job, run the **2-SEEK Bulk Import** +- If streaming isn't enabled in the **1-SEEK System Scans** job, run the **2-SEEK Bulk Import** job. -- If streaming is enabled in the **1-SEEK System Scans** job, do not run the **2-SEEK Bulk Import** +- If streaming is enabled in the **1-SEEK System Scans** job, don't run the **2-SEEK Bulk Import** job. :::info @@ -703,7 +702,7 @@ only). **Step 10 –** Run the **3-FSAC Exceptions** job. -**Step 11 –** Run the desired corresponding analysis and reporting sub-job groups. +**Step 11 –** Run the applicable analysis and reporting sub-job groups. Recommended Workflow 3 (for Access, Activity, DFS, and Sensitive Data Discovery Auditing) @@ -723,9 +722,9 @@ only). **Step 7 –** If necessary, run the **2-FSAA Bulk Import** job: -- If streaming is not enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** +- If streaming isn't enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** job. -- If streaming is enabled in the **1-FSAA System Scans** job, do not run **2-FSAA Bulk Import** job. +- If streaming is enabled in the **1-FSAA System Scans** job, don't run **2-FSAA Bulk Import** job. :::info It is best practice to disable undesired Bulk Import jobs. @@ -736,9 +735,9 @@ only). **Step 9 –** If necessary, run the **2-SEEK Bulk Import** job: -- If streaming is not enabled in the **1-SEEK System Scans** job, run the **2-SEEK Bulk Import** +- If streaming isn't enabled in the **1-SEEK System Scans** job, run the **2-SEEK Bulk Import** job. -- If streaming is enabled in the **1-SEEK System Scans** job, do not run the **2-SEEK Bulk Import** +- If streaming is enabled in the **1-SEEK System Scans** job, don't run the **2-SEEK Bulk Import** job. :::info @@ -750,7 +749,7 @@ only). **Step 11 –** Run the **3-FSAC Exceptions** job. -**Step 12 –** Run the desired corresponding analysis and reporting sub-job groups. +**Step 12 –** Run the applicable analysis and reporting sub-job groups. Optional Workflow (for Sensitive Data Discovery Auditing data collection only) @@ -761,9 +760,9 @@ Activity Auditing components. **Step 2 –** If necessary, run the **2-SEEK Bulk Import** job. -- If streaming is not enabled in the **1-SEEK System Scans** job, run the **2-SEEK Bulk Import** +- If streaming isn't enabled in the **1-SEEK System Scans** job, run the **2-SEEK Bulk Import** job. -- If streaming is enabled in the **1-SEEK System Scans** job, do not run the **2-SEEK Bulk Import** +- If streaming is enabled in the **1-SEEK System Scans** job, don't run the **2-SEEK Bulk Import** job. :::info @@ -771,10 +770,10 @@ Activity Auditing components. ::: -**Step 3 –** Run the desired corresponding analysis and reporting sub-job groups. +**Step 3 –** Run the applicable analysis and reporting sub-job groups. :::note -Please see the +See the [Recommended Configuration for the File System Solution](/docs/accessanalyzer/11.6/solutions/filesystem/recommended.md) topic before continuing with these workflows. diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/content/fs_filetypes.md b/docs/accessanalyzer/11.6/solutions/filesystem/content/fs_filetypes.md index 426993ce0e..1085e10f94 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/content/fs_filetypes.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/content/fs_filetypes.md @@ -18,7 +18,7 @@ View the analysis tasks by navigating to the **FileSystem** > **4.Content** > ** **FS_FileTypes** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/content/fs_stalecontent.md b/docs/accessanalyzer/11.6/solutions/filesystem/content/fs_stalecontent.md index 8c406a9cdb..f60c04298f 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/content/fs_stalecontent.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/content/fs_stalecontent.md @@ -19,7 +19,7 @@ View the analysis tasks by navigating to the **FileSystem** > **4.Content** > ** **FS_StaleContent** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/content/sizing/fs_emptyresources.md b/docs/accessanalyzer/11.6/solutions/filesystem/content/sizing/fs_emptyresources.md index efae10c40c..54fa9b44e1 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/content/sizing/fs_emptyresources.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/content/sizing/fs_emptyresources.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **FileSystem** > **4.Content** > ** **FS_EmptyResources** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/content/sizing/fs_largestresources.md b/docs/accessanalyzer/11.6/solutions/filesystem/content/sizing/fs_largestresources.md index e8b35ffb07..57cdd27594 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/content/sizing/fs_largestresources.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/content/sizing/fs_largestresources.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **4.Content** > ** **FS_LargestResources** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/content/sizing/fs_smallestresources.md b/docs/accessanalyzer/11.6/solutions/filesystem/content/sizing/fs_smallestresources.md index 3f4a457961..5cfd7f0345 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/content/sizing/fs_smallestresources.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/content/sizing/fs_smallestresources.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **4.Content** > ** **FS_SmallestResources** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/content/tags/fs_aiplabels.md b/docs/accessanalyzer/11.6/solutions/filesystem/content/tags/fs_aiplabels.md index 6bdaaa1443..7b3a3eaaae 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/content/tags/fs_aiplabels.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/content/tags/fs_aiplabels.md @@ -6,8 +6,8 @@ sidebar_position: 10 # FS_AIPLabels Job -The FS_AIPLabels job is designed to report on resources classified by AIP labels from targeted file -servers. +The FS_AIPLabels job is designed to report on resources classified by Azure Information Protection +(AIP) labels from targeted file servers. ## Analysis Tasks for the FS_AIPLabels Job @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **4.Content** > ** **FS_AIPLabels** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/content/tags/fs_filetags.md b/docs/accessanalyzer/11.6/solutions/filesystem/content/tags/fs_filetags.md index 79365610be..88a3762c8b 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/content/tags/fs_filetags.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/content/tags/fs_filetags.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **4.Content** > ** **FS_FileTags** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/content/tags/overview.md b/docs/accessanalyzer/11.6/solutions/filesystem/content/tags/overview.md index 31890c0624..d9317bbc8d 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/content/tags/overview.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/content/tags/overview.md @@ -14,6 +14,7 @@ servers. The Tags job group is comprised of: - [FS_AIPLabels Job](/docs/accessanalyzer/11.6/solutions/filesystem/content/tags/fs_aiplabels.md) - – Designed to report on resources classified by AIP labels from targeted file servers + – Designed to report on resources classified by Azure Information Protection (AIP) labels from + targeted file servers - [FS_FileTags Job](/docs/accessanalyzer/11.6/solutions/filesystem/content/tags/fs_filetags.md) – Designed to report on resources classified with metadata file tags from targeted file servers diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/directpermissions/fs_domainuseracls.md b/docs/accessanalyzer/11.6/solutions/filesystem/directpermissions/fs_domainuseracls.md index 02bda80bc8..f53b595580 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/directpermissions/fs_domainuseracls.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/directpermissions/fs_domainuseracls.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **2.Direct Permiss **FS_DomainUserACLs** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -34,7 +34,7 @@ The following analysis tasks are selected by default: - **4. Direct Resources** – Creates an interim processing table in the database for use by downstream analysis and report generation -In addition to the tables and views created by the analysis tasks which displays all direct user +In addition to the tables and views created by the analysis tasks which display all direct user permissions, the FS_DomainUserACLs job produces the following pre-configured report: | Report | Description | Default Tags | Report Elements | diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/directpermissions/fs_highriskacls.md b/docs/accessanalyzer/11.6/solutions/filesystem/directpermissions/fs_highriskacls.md index 21cdc34e65..c9a6f1912a 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/directpermissions/fs_highriskacls.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/directpermissions/fs_highriskacls.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **2.Direct Permiss **FS_HighRiskACLs** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/directpermissions/fs_localusersandgroups.md b/docs/accessanalyzer/11.6/solutions/filesystem/directpermissions/fs_localusersandgroups.md index cee705aeac..624e85b654 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/directpermissions/fs_localusersandgroups.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/directpermissions/fs_localusersandgroups.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **2.Direct Permiss **FS_LocalUsersAndGroups** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/directpermissions/fs_missingfullcontrol.md b/docs/accessanalyzer/11.6/solutions/filesystem/directpermissions/fs_missingfullcontrol.md index c9fb31d255..20a7191ced 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/directpermissions/fs_missingfullcontrol.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/directpermissions/fs_missingfullcontrol.md @@ -7,7 +7,7 @@ sidebar_position: 40 # FS_MissingFullControl Job The FS_MissingFullControl job is designed to report on resources from targeted file servers that -have no Full Control rights granted to it. +have no Full Control rights granted to them. ## Analysis Tasks for the FS_MissingFullControl Job @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **2.Direct Permiss **FS_MissingFullControl** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -34,4 +34,4 @@ produces the following pre-configured report: | Report | Description | Default Tags | Report Elements | | --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Missing Full Control Rights | This report identifies folders within the environment which currently do not have any trustee with Full Control rights, adding to administrative burden. | None | This report is comprised of three elements:
  • Bar Chart – Displays shares with missing full control rights
  • Table – Provides details on folder
  • Table – Provides details on shares with missing full control rights
| +| Missing Full Control Rights | This report identifies folders within the environment which don't have any trustee with Full Control rights, adding to administrative burden. | None | This report is comprised of three elements:
  • Bar Chart – Displays shares with missing full control rights
  • Table – Provides details on folder
  • Table – Provides details on shares with missing full control rights
| diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/directpermissions/fs_nestedshares.md b/docs/accessanalyzer/11.6/solutions/filesystem/directpermissions/fs_nestedshares.md index 0b07b59192..7aa7b6a50d 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/directpermissions/fs_nestedshares.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/directpermissions/fs_nestedshares.md @@ -6,7 +6,7 @@ sidebar_position: 50 # FS_NestedShares Job -The FS_NestedShares job is is designed to report on nested shares that have been granted direct +The FS_NestedShares job is designed to report on nested shares that have been granted direct permissions from targeted file servers. ## Analysis Tasks for the FS_NestedShares Job @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **2.Direct Permiss **FS_NestedShares** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/directpermissions/fs_sidhistory.md b/docs/accessanalyzer/11.6/solutions/filesystem/directpermissions/fs_sidhistory.md index f5135bcc5a..74e90e5673 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/directpermissions/fs_sidhistory.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/directpermissions/fs_sidhistory.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **2.Direct Permiss **FS_SIDHistory** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -39,4 +39,4 @@ the following pre-configured report: | Report | Description | Default Tags | Report Elements | | -------------------- | ------------------------------------------------------------------------------ | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| SID History Overview | This report identifies any applied ACE which utilizes a trustee's SID history. | None | This report is comprised of three elements:
  • Bar Chart – Displays the top 5 hosts by affected folders
  • Table – Provides details on permissions
  • Table – Provides details on trustees
| +| SID History Overview | This report identifies any applied ACE which uses a trustee's SID history. | None | This report is comprised of three elements:
  • Bar Chart – Displays the top 5 hosts by affected folders
  • Table – Provides details on permissions
  • Table – Provides details on trustees
| diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/directpermissions/fs_unresolvedsids.md b/docs/accessanalyzer/11.6/solutions/filesystem/directpermissions/fs_unresolvedsids.md index ccbf165bff..8e56c470f2 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/directpermissions/fs_unresolvedsids.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/directpermissions/fs_unresolvedsids.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **2.Direct Permiss **FS_UnresolvedSIDs** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/filesystemoverview.md b/docs/accessanalyzer/11.6/solutions/filesystem/filesystemoverview.md index 1b736d789a..422fb950fc 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/filesystemoverview.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/filesystemoverview.md @@ -11,8 +11,8 @@ collected by the [File System Access Auditing](/docs/accessanalyzer/11.6/solutions/filesystem/collection/overview.md#file-system-access-auditing) components and the components of the [0.Collection Job Group](/docs/accessanalyzer/11.6/solutions/filesystem/collection/overview.md). -It also depends on the running of the sub-job groups within the solution. If only select sub-job -groups have been run, there will be blank sections in the overview report. +It also depends on running the sub-job groups within the solution. If you run only select sub-job +groups, the overview report has blank sections. ![FileSystemOverview Job in the Jobs Tree](/images/accessanalyzer/11.6/solutions/filesystem/filesystemoverviewjobstree.webp) @@ -25,7 +25,7 @@ View the analysis tasks by navigating to the **FileSystem** > **FileSystemOvervi node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/fs_brokeninheritance.md b/docs/accessanalyzer/11.6/solutions/filesystem/fs_brokeninheritance.md index e58445d1a3..3f26ea1d1a 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/fs_brokeninheritance.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/fs_brokeninheritance.md @@ -15,21 +15,21 @@ The FS_BrokenInheritance job is located in the 3.Broken Inheritance job group. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/11.6/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. The FS_BrokenInheritance job has the following configurable parameter: -- Only analyze folders with changed permissions – Set a value of `1` or `2` to select if only - folders with modified permissions are analyzed: +- Only analyze folders with changed permissions – Set a value of `1` or `2` to select if the job + analyzes only folders with modified permissions: - 1 – Only analyze resources with changed permissions from parent - 2 – Analyze all resources regardless of permission changes between parent and child See the -[Analysis Tasks for the FS_BrokenInheritance Job](#analysis-tasks-for-the-fs_brokeninheritance-job) +[Analysis Tasks for the FS_BrokenInheritance Job](#analysis-tasks-for-the-fsbrokeninheritance-job) topic for additional information. ## Analysis Tasks for the FS_BrokenInheritance Job @@ -38,7 +38,7 @@ View the analysis tasks by navigating to the **FileSystem** > **3.Broken Inherit **FS_BrokenInheritance** > **Configure** node and select **Analysis**. :::warning -Most of these analysis tasks are preconfigured and should not be modified and or +Most of these analysis tasks are preconfigured and shouldn't be modified and/or deselected. There are some that are deselected by default, as they are for troubleshooting purposes. ::: @@ -63,7 +63,7 @@ The following analysis tasks are selected by default: - Can be modified to analyze all resources regardless of permission changes between parent and child. See the [Parameter Configuration](#parameter-configuration) topic for additional information. - - Alternatively, this can be set by modifying the `@FILTER_TO_CHANGED_RESOURCES` parameter. See + - Alternatively, you can set this by modifying the `@FILTER_TO_CHANGED_RESOURCES` parameter. See the [Configure the Customizable Parameters in an Analysis Task](/docs/accessanalyzer/11.6/admin/jobs/job/configure/analysis/analysiscustomizableparameters.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/fs_dlpresults.md b/docs/accessanalyzer/11.6/solutions/filesystem/fs_dlpresults.md index b0e25a98cb..0378f1015d 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/fs_dlpresults.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/fs_dlpresults.md @@ -21,7 +21,7 @@ View the analysis tasks by navigating to the **FileSystem** > **7.Sensitive Data **FS_DLPResults** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -54,4 +54,4 @@ the following pre-configured reports: | File Ownership (Sensitive Data Ownership) | This report identifies the top 3 potential owners of files which have been found to contain sensitive content. | None | This report is comprised of one element:
  • Table – Provides details on top owners per file
| | Sensitive Data Access | This report shows who is accessing sensitive data. Emphasis is placed on activity within the last 30 days. | GDPR SOX HIPAA PCI-DSS GLBA ITAR FERPA FISMA ISO27001 | This report is comprised of two elements:
  • Bar Chart – Displays sensitive data access by top users
  • last 30 days
  • Table – Provides details on sensitive data access
| | Sensitive Security Groups | This report identifies groups which are used to provide access to sensitive data. Changes to membership should be closely monitored. | GDPR SOX HIPAA PCI-DSS GLBA ITAR FERPA FISMA ISO27001 | This report is comprised of two elements:
  • Bar Chart – Top groups by access to sensitive files
  • Table – Provides details on group access to sensitive files
| -| Share Details (Shares with Sensitive Content) | This report identifies the location of sensitive data, and flags whether or not this data is accessible through open access. | GDPR SOX HIPAA PCI-DSS GLBA ITAR FERPA FISMA ISO27001 | This report is comprised of three elements:
  • Bar chart – Displays top shares by sensitive file count
  • Table – Provides details on files
  • Table – Provides details on top shares by sensitive file count
| +| Share Details (Shares with Sensitive Content) | This report identifies the location of sensitive data, and flags whether this data is accessible through open access. | GDPR SOX HIPAA PCI-DSS GLBA ITAR FERPA FISMA ISO27001 | This report is comprised of three elements:
  • Bar chart – Displays top shares by sensitive file count
  • Table – Provides details on files
  • Table – Provides details on top shares by sensitive file count
| diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/fs_openaccess.md b/docs/accessanalyzer/11.6/solutions/filesystem/fs_openaccess.md index 224f6d0e8a..c6822d32ed 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/fs_openaccess.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/fs_openaccess.md @@ -7,8 +7,8 @@ sidebar_position: 30 # 1.Open Access > FS_OpenAccess Job The FS_OpenAccess job is designed to report on Open Access information from targeted file servers. -The definition of Open Access is when a security principal, such as Everyone, Authenticated Users, -or Domain Users, have permissions on a resource. +Open Access means a security principal, such as Everyone, Authenticated Users, or Domain Users, has +permissions on a resource. ![1.Open Access > FS_OpenAccess Job in the Jobs Tree](/images/accessanalyzer/11.6/solutions/filesystem/openaccessjobstree.webp) @@ -20,7 +20,7 @@ View the analysis tasks by navigating to the **FileSystem** > **1.Open Access** **FS_OpenAccess** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/fs_probableowner.md b/docs/accessanalyzer/11.6/solutions/filesystem/fs_probableowner.md index b78e5f31e5..a7b95b2791 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/fs_probableowner.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/fs_probableowner.md @@ -22,7 +22,7 @@ View the analysis tasks by navigating to the FileSystem > 6.Probable Owner > FS_ Configure node and select Analysis. :::warning -Do not modify or deselect the first and third selected analysis tasks. The analysis +Don't modify or deselect the first and third selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -35,9 +35,9 @@ The following analysis tasks are selected by default: Probable Owners - Identify Probable Owners – Creates the SA_FS_ProbableOwner_Details table accessible under the job’s Results node - - Set to “Start listing ownership at the root share” which is `@minlevel` parameter set to + - Set to “Start listing ownership at the root share” which is the `@minlevel` parameter set to Value0. - - Set to “List ownership as deep into the folder hierarchy as the root share” which is + - Set to “List ownership as deep into the folder hierarchy as the root share” which is the `@maxlevel` parameter set to Value0. - Value0 = root share, Value1 = 1 folder deep, Value2 = 2 folders deep, etc. - Set the variable #FILTERED_TRUSTEES to a CSV file that contains one row for each SID to be diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/fs_securityassessment.md b/docs/accessanalyzer/11.6/solutions/filesystem/fs_securityassessment.md index 86007f39d9..410582bf76 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/fs_securityassessment.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/fs_securityassessment.md @@ -26,7 +26,7 @@ information from targeted file servers. It is dependent upon the following jobs: - [7.Sensitive Data > FS_DLPResults Job](/docs/accessanalyzer/11.6/solutions/filesystem/fs_dlpresults.md) -If only select sub-job groups have been run, there are blank sections in the overview report. +If you run only select sub-job groups, the overview report has blank sections. ![FS_SecurityAssessment Job in the Jobs Tree](/images/accessanalyzer/11.6/solutions/filesystem/securityassessmentjobstree.webp) @@ -39,7 +39,7 @@ View the analysis tasks by navigating to the **FileSystem** > **FS_SecurityAsses **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/overview.md b/docs/accessanalyzer/11.6/solutions/filesystem/overview.md index 7ffce8de05..0da0f34153 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/overview.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/overview.md @@ -13,9 +13,9 @@ sensitive data discovery and classification, open access remediation, least-priv transformation, and file activity monitoring. File systems and NAS devices contain the vast majority of an organization’s data. Each day, more -data is created and stored in the nooks and crannies of the environment, beyond the sight of the -people charged with managing it and keeping it safe. The File System Solution is designed to gather -information from file systems and shared folders in order to answer questions around data access: +data is created and stored throughout the environment, often unnoticed by the people responsible +for managing it and keeping it safe. The File System Solution is designed to gather +information from file systems and shared folders to answer questions around data access: - Who has access to your data? - Who is accessing your data? @@ -50,14 +50,13 @@ There is a limit of 100 file system hosts that can be scanned simultaneously. **Sensitive Data Discovery Considerations** The Sensitive Data Discovery Add-On must be installed on the Enterprise Auditor Console server, -which enables Sensitive Data criteria for scans. If running Sensitive Data Discovery (SDD) scans, it -will be necessary to increase the minimum amount of RAM. Each thread requires a minimum of 2 -additional GB of RAM per host. For example, if the job is configured to scan 8 hosts at a time , -then an extra 16 GB of RAM are required (8x2=16). +which enables Sensitive Data criteria for scans. If you run Sensitive Data Discovery (SDD) scans, increase the minimum amount of +RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For example, if the job is +configured to scan 8 hosts at a time, then an extra 16 GB of RAM is required (8x2=16). :::note The Sensitive Data Discovery Add-on installation package installs the appropriate JDK -(Java) version on the server. The JDK deployed is prepackaged and does not require any +(Java) version on the server. The JDK deployed is prepackaged and doesn't require any configuration; it has been preconfigured to work with Enterprise Auditor and should never be customized through Java. It will not conflict with other JDKs or Java Runtimes in the same environment. @@ -65,16 +64,15 @@ environment. :::tip -Remember, if employing either of the File System Proxy Mode as a Service scan mode options, it is -also necessary for the Sensitive Data Discovery Add-on to be installed on the server where the proxy -service is installed. +Remember, if you use either File System Proxy Mode as a Service scan mode option, you must also +install the Sensitive Data Discovery Add-on on the server where the proxy service runs. ::: **Location** The File System Solution requires a special Enterprise Auditor license. It can be installed from the -Instant Job Wizard. Once it has been installed into the Jobs tree, navigate to the solution: +Instant Job Wizard. After it has been installed into the Jobs tree, navigate to the solution: **Jobs** > **FileSystem**. The @@ -97,8 +95,8 @@ information. The File System Solution offers information on multiple aspects of an organization’s file system infrastructure. This solution is comprised of eleven job groups and an overview job which collect, -analyze, and report on data as well as run action tasks for environmental remediation. The data -collection is conducted by the FileSystemAccess (FSAA) Data Collector. See the +analyze, and report on data as well as run action tasks for environmental remediation. The +FileSystemAccess (FSAA) Data Collector collects this data. See the [Standard Reference Tables & Views for the FSAA Data Collector](/docs/accessanalyzer/11.6/admin/datacollector/fsaa/standardtables.md) section for database table information. @@ -111,10 +109,10 @@ exception of the Sensitive Data Discovery Auditing component which can be run in data collection query options for each type are explained within the 0.Collection Job Group section. Additionally, the corresponding analysis and reporting job groups are listed for each auditing type. -If intending to run three or all auditing types, see each auditing type section within the -0.Collection Job Group section for information on query options and requirements. It is recommended -to first run the 0.Collection Job Group components in the default order for the desired auditing -types to ensure successful data collection, and then to run the desired sub-groups for reports. +If you intend to run three or all auditing types, see each auditing type section within the +0.Collection Job Group section for information on query options and requirements. First run the +0.Collection Job Group components in the default order for the auditing types you want to run, to +ensure successful data collection, and then run the sub-groups you need for reports. See the [Recommended Configuration for the File System Solution](/docs/accessanalyzer/11.6/solutions/filesystem/recommended.md) @@ -164,9 +162,9 @@ of the following jobs: - [FS_SecurityAssessment Job](/docs/accessanalyzer/11.6/solutions/filesystem/fs_securityassessment.md) – Designed to provide a security assessment of all relevant information from targeted file servers -When targeting Nasuni Edge Appliances, it is necessary to add a job from the Instant Job Library +When targeting Nasuni Edge Appliances, add a job from the Instant Job Library (FS_Nasuni Job) which uses the PowerShell Data collector to gather system information, volume data, -and share data from the Nasuni environment. This job should be added to the 0.Collection Job Group -and should be renamed (0-FS_Nasuni) to run immediately after the 0-Create Schema Job. See the +and share data from the Nasuni environment. Add this job to the 0.Collection Job Group +and rename it (0-FS_Nasuni) to run immediately after the 0-Create Schema Job. See the [0-FS_Nasuni Job](/docs/accessanalyzer/11.6/solutions/filesystem/collection/0-fs_nasuni.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/recommended.md b/docs/accessanalyzer/11.6/solutions/filesystem/recommended.md index 2b3b1f68f3..1a012b2c0e 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/recommended.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Recommended Configuration for the File System Solution -The File System Solution has been configured to inherit down from the **FileSystem** > **Settings** +By default, the File System Solution inherits settings from the **FileSystem** > **Settings** node for most jobs. However, as a best practice, assign the host list and the Connection Profile at the data collection level. After you assign these to the job, you can run it manually or schedule it. @@ -32,8 +32,8 @@ topic for additional information. **Targeted Hosts** Assign the host list under the **FileSystem** > **0.Collection** > -**[job]** > **Host** node. The list should be a custom created list for the file system environments -to be targeted. Check the box for the custom-created host list. The **…System +**[job]** > **Host** node. Use a custom list of the file system environments you want to target. +Check the box for the custom-created host list. The **…System Scans** jobs and the corresponding **…Bulk Import** jobs must use the same host lists. The 0-FSDFS System Scans Job is an exception and is set to the Default domain controller. For @@ -43,7 +43,7 @@ want to scan. If you target Nasuni Edge Appliances, assign the 0-FS_Nasuni Job a custom host list containing all on-premise Nasuni Edge Appliances and cloud filers. -If using multiple proxy servers, these should also be configured within a different custom-created +If you use multiple proxy servers, configure them within a different custom-created host list. Then assign the proxy servers host list on the [FSAA: Applet Settings](/docs/accessanalyzer/11.6/admin/datacollector/fsaa/appletsettings/appletsettings.md) page of the File System Access Auditor Data Collector Wizard within the following jobs in the @@ -55,8 +55,8 @@ page of the File System Access Auditor Data Collector Wizard within the followin Windows clusters have special needs for the host list and host inventory data. You must target the Windows File Server Cluster (name of the cluster) of interest when running a scan against a Windows -File System Cluster. Within the Enterprise Auditor Master Host Table, there -should be a host entry for the cluster as well as for each node. Additionally, each of these host +File System Cluster. The Enterprise Auditor Master Host Table must include a +host entry for the cluster as well as for each node. Additionally, each of these host entries must have the name of the cluster in the WinCluster column in the host inventory data. You may need to update this manually. See the [Host Inventory](/docs/accessanalyzer/11.6/admin/settings/hostinventory.md) @@ -105,10 +105,10 @@ permissions for the assigned hosts, click the radio button for the **Select one user defined profiles** option and select the appropriate Connection Profile dropdown menu. :::tip -Remember, if targeting Nasuni Edge Appliances, the 0-FS_Nasuni Job needs to be assigned a custom +Remember, if you target Nasuni Edge Appliances, assign the 0-FS_Nasuni Job a custom Connection Profile containing the **API Access Key** and **Passcode** for each on-premise Nasuni Edge Appliance and cloud filer in the target environment. Nasuni API key names are case sensitive. -When providing them, enter them in the exact same case as generated. +Enter them in the exact case in which they were generated. ::: @@ -123,26 +123,26 @@ dependent on the size of the target environment. The FileSystem Solution can be weekly or as desired depending on the types of auditing being conducted and the scope of the target environment. -For example, it may be desired in large environments to run Activity Auditing collection jobs on a -daily basis, but to only run Access Auditing and Sensitive Data Discovery Auditing collection jobs -on a weekly basis followed by the analysis and reporting job groups. +For example, in large environments, you might run Activity Auditing collection jobs daily, but run +Access Auditing and Sensitive Data Discovery Auditing collection jobs only weekly, followed by the +analysis and reporting job groups. **Run Order** -Whatever schedule frequency may be configured, it is also recommended to streamline the collection -jobs to those desired. The jobs in the 0.Collection Job Group must be run in order for the auditing +Regardless of the schedule frequency you configure, streamline the collection +jobs to only those you need. Run the jobs in the 0.Collection Job Group in order for the auditing type. Run …System Scans jobs and then the corresponding …Bulk Import jobs according to the desired workflow. The other File System Solution sub-job groups can be run together or individually in any order, after running the 0.Collection Job Group. The FileSystemOverview Job pulls information from both the 0.Collection Job Group and the other sub-job groups, and the report may contain blank sections if -only select sub-job groups are run. +you run only select sub-job groups. :::info -If only conducting one or two types of auditing, scope the solution by disabling -the undesired collection jobs. Disabling them allows the solution to run more efficiently. It isn't -recommended to delete any jobs. See the +If you conduct only one or two types of auditing, scope the solution by disabling +the undesired collection jobs. Disabling them allows the solution to run more efficiently. Don't +delete any jobs. See the [Disable or Enable a Job](/docs/accessanalyzer/11.6/admin/jobs/job/disableenable.md) topic for additional information. ::: @@ -178,7 +178,7 @@ customizations include: - Default Scoping Options page > File Details tab, configure the file detail collection - By default, file detail scans are disabled - - Select the type of file data to be collected and optionally add filters + - Select the type of file data to collect and optionally add filters - Set on the following **0.Collection** Job Group jobs: - **1-FSAA System Scans** Job for Access Auditing @@ -207,26 +207,24 @@ customizations include: topic and the [File System Supported Platforms](/docs/accessanalyzer/11.6/requirements/filesystem/filesystems/filesystems.md) topic for additional information. - - Local Mode – All of the data collection processing is conducted by the Enterprise Auditor - Console server across the network - - Applet Mode – The File System applet is deployed to the target host when the job is executed - to conduct data collection. The data is collected on the Windows target host where the applet - is deployed. The final step in data collection is to compress and transfer the data collected - in the SQLite databases, or Tier 2 databases, back to the Enterprise Auditor Console server. - If the target host is a NAS device, the File System scans default to local mode for that host. - - Proxy Mode with Applet – The File System applet is deployed to the Windows proxy server when - the job is executed to conduct data collection. The data collection processing is initiated by - the proxy server where the applet is deployed and uses a local mode-type scan to each of - the target hosts. The final step in data collection is to compress and transfer the data - collected in the SQLite databases, or Tier 2 databases, back to the Enterprise Auditor Console - server. - - Proxy Mode as a Service – The File System Proxy Service must be installed on the Windows proxy - servers before executing the scans. The data collection processing is conducted by the proxy - server where the service is running and uses a local mode-type scan to each of the target - hosts. The final step in data collection is to compress and transfer the data collected in the - SQLite databases, or Tier 2 databases, back to the Enterprise Auditor Console server. The - credential granted rights to interact with the service must be included in the assigned - Connection Profile. + - Local Mode – The Enterprise Auditor Console server conducts all data collection processing + across the network + - Applet Mode – When the job runs, it deploys the File System applet to the target host to + collect data. The applet collects data on the Windows target host where it's deployed. The + final step compresses and transfers the collected data in the SQLite databases, or Tier 2 + databases, back to the Enterprise Auditor Console server. If the target host is a NAS device, + the File System scans default to local mode for that host. + - Proxy Mode with Applet – When the job runs, it deploys the File System applet to the Windows + proxy server to collect data. The proxy server where the applet is deployed initiates data + collection processing and uses a local mode-type scan against each target host. The final step + compresses and transfers the collected data in the SQLite databases, or Tier 2 databases, back + to the Enterprise Auditor Console server. + - Proxy Mode as a Service – You must install the File System Proxy Service on the Windows proxy + servers before running the scans. The proxy server where the service runs conducts data + collection processing and uses a local mode-type scan against each target host. The final step + compresses and transfers the collected data in the SQLite databases, or Tier 2 databases, back + to the Enterprise Auditor Console server. The assigned Connection Profile must include the + credential granted rights to interact with the service. - Set on the following **0.Collection** Job Group jobs: - **1-FSAA System Scans** Job for Access Auditing @@ -266,7 +264,7 @@ Though the analysis tasks shouldn't be deselected, the following parameters can - The .Active Directory Inventory Solution defines large groups, deeply nested groups, stale users, and users with large tokens. These parameters can be customized and are applicable to any - solution, including File System, which incorporate this analyzed data into further analysis. + solution, including File System, which incorporates this analyzed data into further analysis. - Customize within **.Active Directory Inventory** > **3-AD_Exceptions** Job analysis tasks @@ -306,10 +304,10 @@ within an analysis task. The jobs contained in the group use custom SQL scripts to render views on collected data. SQL views populate report element tables and graphs. Changing or modifying the group, job, or -table names result in no data displayed within the reports or the AIC. +table names results in no data displayed within the reports or the AIC. :::tip -Remember, it is recommended to scope the 0.Collection Job Group to only include the collection -components desired by disabling the undesired collection jobs. Disabling them allows the solution to -run more efficiently. It isn't recommended to delete any jobs. +Remember, scope the 0.Collection Job Group to include only the collection +components you want by disabling the undesired collection jobs. Disabling them allows the solution to +run more efficiently. Don't delete any jobs. ::: diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroupaicimport.md b/docs/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroupaicimport.md index d338666a41..123385b297 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroupaicimport.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroupaicimport.md @@ -6,21 +6,20 @@ sidebar_position: 20 # FS_ResourceBasedGroupAICImport Job -The FS_ResorceBasedGroupsAICImport Job imports resources and access groups from the -FS_ResoureBasedGroup Job into the Netwrix Access Information Center. This job assigns ownership in -the Access Information Center and then assigns resource groups. This step is required if it is -desired to change access through entitlement reviews, self-service, or for publishing resources to -IAM. +The FS_ResourceBasedGroupsAICImport Job imports resources and access groups from the +FS_ResourceBasedGroups Job into the Netwrix Access Information Center. This job assigns ownership in +the Access Information Center and then assigns resource groups. This step is required if you want to +change access through entitlement reviews, self-service, or publishing resources to IAM. ## Recommended Configurations for the FS_ResourceBasedGroupsAICImport Job **Dependencies** -- The **FS_ResourceBasedGroups** job must be successfully run prior to running this job -- The **.Active Directory Inventory** > **1-AD_Scan** job must be successfully run prior to running +- The **FS_ResourceBasedGroups** job must be successfully run before running this job +- The **.Active Directory Inventory** > **1-AD_Scan** job must be successfully run before running this job - The **File System** > **0.Collection** > **1-FSAA System Scans** job must be successfully run - prior to running this job + before running this job - The **File System** > **0.Collection** > **2-FSAA Bulk Import** job must be successfully run prior to running this job @@ -30,8 +29,8 @@ None **Schedule Frequency** -This job group can be scheduled to run as desired. Throughout this document reference to executing a -job refers to either manual execution or scheduled execution, according to the needs of the +This job group can be scheduled to run as desired. Throughout this document, executing a +job refers to either manual execution or scheduled execution, based on the needs of the organization. See the [Scheduling the Resource Based Groups Job Group](/docs/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/overview.md#scheduling-the-resource-based-groups-job-group) topic for additional information. @@ -51,7 +50,7 @@ Not supported **Step 2 –** Run the FS_ResourceBasedGroupsAICImport job. -- See the [Run the FS_ResourceBasedGroupsAICImportJob](#run-the-fs_resourcebasedgroupsaicimportjob) +- See the [Run the FS_ResourceBasedGroupsAICImportJob](#run-the-fsresourcebasedgroupsaicimportjob) topic for additional information **Step 3 –** Review the newly-created resource based groups in the AIC. @@ -63,13 +62,12 @@ Not supported ## Run the FS_ResourceBasedGroupsAICImportJob Now that the target environment follows a Resource Based Groups model, the new resources can be -imported into the Access Information Center. Follow the steps to import the new resources into the -AIC Ownership Workflow. +imported into the Access Information Center. :::warning -It is important to run the .Active Directory Inventory Job Group and **File System** > -**0. Collection** Job Group again so that the AD and permissions changes are captured by Enterprise -Auditor. +Run the .Active Directory Inventory Job Group and **File System** > +**0. Collection** Job Group again so that Enterprise Auditor captures the AD and permissions +changes. ::: @@ -78,8 +76,8 @@ Job Group again. **Step 2 –** Right click the **FS_ResourceBasedGroupsAICImport** job and select **Run Job**. -The newly created resource based groups are imported to the AIC. The Owner and Access Groups have -been assigned to the resources by the import process. The AIC can now be used to manage these +The import process imports the newly created resource based groups to the AIC and assigns the Owner +and Access Groups to the resources. The AIC can now be used to manage these resources through Entitlement Reviews, Ad hoc owner changes, and the Self Service access portal. ## Review the New Resource Based Groups in the AIC diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroups.md b/docs/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroups.md index 5b161cb094..3abe5e8dc7 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroups.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroups.md @@ -19,7 +19,7 @@ group implementation. **Step 3 –** (Optional) Configure a Host List for the job at the job level. :::note -If a host list is not configured, this job will analyze and commit actions on every File +If you don't configure a host list, this job analyzes and commits actions on every File System server known to Enterprise Auditor. To scope the actions to target specific servers, configure a host list at the job level to target only those servers. ::: @@ -31,7 +31,7 @@ configure a host list at the job level to target only those servers. - Verify that all actions are disabled :::warning - Do not make configuration changes to the analysis tasks after reviewing and + Don't make configuration changes to the analysis tasks after reviewing and approving the Change Modeling report ::: @@ -48,7 +48,7 @@ configure a host list at the job level to target only those servers. **Step 6 –** Execute File System actions: -- Allow an appropriate grace period for token refresh prior to executing File System action tasks, +- Allow an appropriate grace period for token refresh before executing File System action tasks, for example one week - Disable the Active Directory action tasks - Enable the File System action tasks @@ -70,14 +70,14 @@ based groups. See the [FS_TraverseGroups Job](/docs/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/fs_traversegroups.md) topic for additional information. -**Step 9 –** (Optional) Import resources and access groups from the FS_ResoureBasedGroup Job into +**Step 9 –** (Optional) Import resources and access groups from the FS_ResourceBasedGroups Job into the Netwrix Access Information Center. See the [FS_ResourceBasedGroupAICImport Job](/docs/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroupaicimport.md) topic for additional information. ## Model Intended Changes -Prior to executing the actions to apply changes, the proposed changes can be modeled and reviewed to +Before executing the actions to apply changes, model and review the proposed changes to determine if the parameters are configured as desired. ### Configure the Analyze Group Permissions Analysis Task @@ -107,12 +107,12 @@ topic for additional information. | Analyze Group Permissions | @add_admin_groups | 1 | Add full control admin groups. 1=true. 0=false. | | Analyze Group Permissions | @admin_groups | | ObjectSIDs of admin groups to add to every share if @add_admin_groups = 1 | | Analyze Group Permissions | #folders | | List of folders to assign RBG to. Overrides @levels_down. | -| Analyze Group Permissions | @activity_filter | 1000 | Filter out users with last activity older than X days ago. Will filter out users who have not accessed the folder within the specified threshold. If activity records show the user has never accessed the folder, users will still be included in resource based groups. | +| Analyze Group Permissions | @activity_filter | 1000 | Filter out users with last activity older than X days ago. This filters out users who have not accessed the folder within the specified threshold. If activity records show the user has never accessed the folder, the user is still included in resource based groups. | ### Execute the Analysis Tasks Execute the analysis tasks to generate the Change Modeling report and review the proposed changed -prior to executing the actions to apply the changes. +before executing the actions to apply the changes. | Report | Description | Default Tags | Report Elements | | --------------- | ---------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -127,47 +127,45 @@ implementing the changes: Access changes occur in the following cases: -- The user is granted full access, but is not a member of the administrator group specified in the +- The user is granted full access, but isn't a member of the administrator group specified in the analysis parameters - The user is granted less access, but is a member of the administrator group specified in the analysis parameters - The user has not used access within the timeframe configured in the analysis parameters -Follow the steps to model the proposed changes. - -**Step 1 –** Make sure all of the analysis tasks are enabled. +**Step 1 –** Ensure all of the analysis tasks are enabled. :::warning -Prior to executing the analysis tasks, make sure that all action tasks are disabled. +Before executing the analysis tasks, ensure that all action tasks are disabled. The purpose at this point is only to model the intended changes. ::: -**Step 2 –** In the Configure node, select **Actions** and make sure that all of the action tasks +**Step 2 –** In the Configure node, select **Actions** and ensure that all of the action tasks are disabled. -**Step 3 –** Right click on the **Resource Based Groups** folder and select **Run Group**. This will +**Step 3 –** Right click the **Resource Based Groups** folder and select **Run Group**. This will generate the Change Modeling report. - Wait for the queued jobs to execute. **Step 4 –** In the **FS_ResourceBasedGroups** node, navigate to **Results** > **Change Modeling** -to review the proposed changes prior to executing the actions to apply the changes. +to review the proposed changes before executing the actions to apply the changes. -The Change Modeling report has been created for review. Ensure the modeled changes are approved -before continuing with implementing them. +The Change Modeling report is now available for review. Ensure the modeled changes are approved +before you implement them. ## Configure & Execute Active Directory Action Tasks :::warning -Do not modify the analysis tasks after the Change Modeling report has been reviewed and +Don't modify the analysis tasks after the Change Modeling report has been reviewed and approved. The approved modeled changes are implemented through the execution of the action tasks. ::: -The Active Directory action tasks create and populate resource based groups. The Create Groups and -Update Members action tasks must be updated to specify a Target OU for group creation prior to -enabling and executing the actions. It should also be verified that these action tasks are targeting +The Active Directory action tasks create and populate resource based groups. You must update the +Create Groups and Update Members action tasks to specify a Target OU for group creation before you +enable and execute the actions. Also verify that these action tasks target the same domain controller. View the action tasks by navigating to the **Jobs** > **FileSystem** > **Resourced Based Groups** > @@ -175,12 +173,12 @@ View the action tasks by navigating to the **Jobs** > **FileSystem** > **Resourc ![Active Directory Action Tasks](/images/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/rbgactivedirectoryactions.webp) -There are the following two Active Directory action tasks: +Two Active Directory action tasks are available: - Create Groups – Creates resource based groups - Update Members – Adds members to the resource based groups based on permissions -It is recommended to review the tables used by the actions prior to executing the actions. The +Review the tables used by the actions before you execute the actions. The actions act upon the data within the following tables: - FS_ResourceBasedGroups_GroupsToCreate @@ -191,8 +189,6 @@ job’s Results node. The FS_ResourceBasedGroups Job will run analysis tasks aga ### Configure & Enable the Create Groups Action Task -Follow the steps to configure the Create Groups action task. - **Step 1 –** Select the action and click **Action Properties**. **Step 2 –** On the Action Properties page, click **Configure Action**. @@ -215,8 +211,6 @@ The Create Groups action is configured. ### Configure & Enable the Update Members Action Task -Follow the steps to configure the Create Groups action task. - **Step 1 –** Select the action task and click **Action Properties**. **Step 2 –** On the Action Properties page, click **Configure Action**. @@ -240,30 +234,28 @@ The Update Members action is configured. ### Execute Active Directory Action Tasks -Make sure that the File System actions are deselected and execute the Active Directory action tasks. +Ensure that the File System actions are deselected, and execute the Active Directory action tasks. The Create Groups action creates the resource based groups. The Update Members action populates those groups. Enabled action tasks can be manually executed at the Actions node. Action tasks can be scheduled only at the job level. -Follow the steps to execute the AD actions. - :::warning -Do not modify the analysis tasks after the Change Modeling report has been reviewed and +Don't modify the analysis tasks after the Change Modeling report has been reviewed and approved. The approved modeled changes are implemented through the execution of the action tasks. ::: :::info -Disable the analysis tasks. It is not necessary to collect the data again. +Disable the analysis tasks. You don't need to collect the data again. ::: **Step 1 –** On the Action Selection page, enable the **Create Groups** and **Update Members** actions. -**Step 2 –** Right-click on the **Resource Based Groups** folder and select **Run Group**. +**Step 2 –** Right-click the **Resource Based Groups** folder and select **Run Group**. - Wait for the queued jobs to execute. @@ -272,25 +264,25 @@ The resource based groups are created and populated. ## Execute File System Action Tasks :::warning -Prior to executing the File System action tasks, allow a grace period, for example one +Before executing the File System action tasks, allow a grace period, for example one week. This is important for token refresh to occur as users log off and log on again. ::: The File System actions modify folder permissions and break inheritance. The Modify Permissions and -Break Inheritance actions modules do not require any configuration. +Break Inheritance actions modules don't require any configuration. View the action tasks by navigating to the **Jobs** > **FileSystem** > **Resourced Based Groups** > **FS_ResourceBasedGroups** > **Configure** node and select **Actions**. ![File System action tasks](/images/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/rbgfilesystemactions.webp) -There are the following two File System action tasks: +Two File System action tasks are available: - Modify Permissions – Modifies folder permissions - Break Inheritance – Breaks inheritance and remove all previous permissions -It is recommended to review the tables used by the actions prior to executing the actions. The +Review the tables used by the actions before you execute the actions. The actions act upon the data within the following table: - FS_ResourceBasedGroups_GroupsToCreate @@ -298,10 +290,8 @@ actions act upon the data within the following table: The actions populate the Modify Permissions and Break Inheritance tables, which can viewed under the job’s Results node. The FS_ResourceBasedGroups Job will run analysis tasks against these tables. -Follow the steps to execute the FS actions. - :::warning -Do not modify the analysis tasks after the Change Modeling report has been reviewed and +Don't modify the analysis tasks after the Change Modeling report has been reviewed and approved. The approved modeled changes are implemented through the execution of the action tasks. ::: @@ -311,7 +301,7 @@ actions. **Step 2 –** Enable the **Modify Permissions** and **Break Inheritance** actions. -**Step 3 –** Right-click on the **Resource Based Groups** folder and select **Run Group**. +**Step 3 –** Right-click the **Resource Based Groups** folder and select **Run Group**. - Wait for the queued jobs to execute. @@ -328,15 +318,13 @@ purposes. | Action History | This report shows all actions taken on each share for audit trail purposes. | None | This report is comprised of one element:
  • Table – This table provides details on the actions taken on each share
| -Follow the steps to analyze and report on action history. - :::warning -Disable all of the action tasks prior to generating the Action History report. +Disable all of the action tasks before generating the Action History report. ::: **Step 1 –** On the Action Selection page, disable the **Modify Permissions** and **Break -Inheritance** actions. Make sure all of the action tasks are disabled. +Inheritance** actions. Ensure all of the action tasks are disabled. **Step 2 –** On the Analysis Selection page, enable the **Create view for action status** and **Summarize Access Changes** analysis tasks. diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/fs_traversegroups.md b/docs/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/fs_traversegroups.md index 0566ae4cc6..42dd6e9521 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/fs_traversegroups.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/fs_traversegroups.md @@ -6,9 +6,9 @@ sidebar_position: 30 # FS_TraverseGroups Job -The **FS_TraverseGroups** Job can be used to create and apply permissions for traverse groups based +Use the **FS_TraverseGroups** Job to create and apply permissions for traverse groups based on previous resource based groups. This job would be used in the case where the folder to which -resource based groups permissions are applied is not the root share folder, or at the root of the +resource based groups permissions are applied isn't the root share folder, or at the root of the share. This job prevents users from losing the ability to navigate through the directory structure if the folder is nested. The FS_TraverseGroups Job must be installed from the Instant Job library. See the @@ -19,7 +19,7 @@ topic for additional information. **Dependencies** -- The **FS_ResourceBasedGroups** job must be successfully run prior to running this job +- The **FS_ResourceBasedGroups** job must be successfully run before running this job **Targeted Hosts** @@ -28,8 +28,8 @@ topic for additional information. **Schedule Frequency** -This job can be scheduled to run as desired. Throughout this document reference to executing a job -refers to either manual execution or scheduled execution, according to the needs of the +This job can be scheduled to run as desired. Throughout this document, executing a job +refers to either manual execution or scheduled execution, based on the needs of the organization. See the [Scheduling the Resource Based Groups Job Group](/docs/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/overview.md#scheduling-the-resource-based-groups-job-group) topic for additional information. @@ -45,7 +45,7 @@ Not supported **Step 2 –** Configure a Host List for the job at the job level. :::note -If a host list is not configured, this job will analyze and commit actions on every File +If a host list isn't configured, this job will analyze and commit actions on every File System server known to Enterprise Auditor. To scope the actions to target specific servers, configure a host list at the job level to target only those servers. ::: @@ -65,7 +65,7 @@ configure a host list at the job level to target only those servers. **Step 5 –** Execute File System action task. -- Allow an appropriate grace period for token refresh prior to executing File System action task, +- Allow an appropriate grace period for token refresh before executing File System action task, for example one week - Disable the Active Directory action task - Enable the Modify Permissions action task @@ -81,7 +81,7 @@ configure a host list at the job level to target only those servers. ## Configure & Execute Analysis Tasks -Prior to executing the action tasks, configure and execute the analysis tasks. +Before executing the action tasks, configure and execute the analysis tasks. ### Configure the Create Groups Analysis Task @@ -114,21 +114,21 @@ topic. ### Execute Analysis Tasks -Once the Create Groups analysis task has been configured, execute the analysis tasks. The analysis -tasks are selected by default. Follow the steps to execute the analysis tasks. +After the Create Groups analysis task has been configured, execute the analysis tasks. The analysis +tasks are selected by default. -**Step 1 –** Make sure all of the analysis tasks are enabled. +**Step 1 –** Ensure all of the analysis tasks are enabled. :::warning -Prior to executing the analysis tasks, make sure that all action tasks are disabled. +Before executing the analysis tasks, ensure that all action tasks are disabled. The purpose at this point is only to create the required traversal tables. ::: -**Step 2 –** In the Configure node, select **Actions** and make sure that all of the action tasks +**Step 2 –** In the Configure node, select **Actions** and ensure that all of the action tasks are disabled. -**Step 3 –** Right click on the **FS_TraverseGroups** job and select **Run Job**. This will generate +**Step 3 –** Right click the **FS_TraverseGroups** job and select **Run Job**. This will generate the Change Modeling report. - Wait for the queued jobs to execute. @@ -138,7 +138,7 @@ The analysis tasks create the required traversal tables accessible under the job ## Configure & Execute Active Directory Action Task The Active Directory action tasks create and populate resource based groups. The Create Groups -action tasks must be updated to specify a Target OU for group creation prior to enabling and +action tasks must be updated to specify a Target OU for group creation before enabling and executing the actions. It should also be verified that the action tasks are targeting the same domain controller. View the actions by navigating to the place in the Jobs tree where the Traverse Groups job was installed from the Instant Jobs library. Then go to the **FS_TraverseGroups** > @@ -146,19 +146,19 @@ Groups job was installed from the Instant Jobs library. Then go to the **FS_Trav specify the OU for group creation. :::info -It is recommended to execute the actions one at a time and in order as opposed to +Execute the actions one at a time and in order instead of running the entire job group with the actions enabled. ::: ![FS_TraverseGroups action tasks](/images/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/traverseactions.webp) -There are the following action tasks: +The following action tasks are available: - Create Groups – Create groups and add resource based groups - Modify Permissions – Add list groups -It is recommended to review the tables used by the actions prior to executing the actions. For +Review the tables used by the actions before you execute the actions. For instructions on configuring action tables, see the Configure & Enable the Create Groups Action Task topic. The actions act upon the data within the following tables: @@ -170,8 +170,6 @@ tasks against these tables. ### Configure & Enable the Create Groups Action Task -Follow the steps to configure the Create Groups action task. - **Step 1 –** Select the action and click **Action Properties**. **Step 2 –** On the Action Properties page, click **Configure Action**. @@ -190,12 +188,11 @@ groups is the same domain controller used in the Update Members action task. ### Execute Active Directory Action Task The Create Groups action creates the resource based groups. Enabled action tasks can be manually -executed at the Actions node. Action tasks can be scheduled only at the job level. Follow the steps -to create the resource based groups. +executed at the Actions node. Action tasks can be scheduled only at the job level. **Step 1 –** On the Action Selection page, enable the **Create Groups** action task. -**Step 2 –** Right-click on the **FS_TraverseGroups** job and select **Run Job**. +**Step 2 –** Right-click the **FS_TraverseGroups** job and select **Run Job**. - Wait for the queued job to execute @@ -203,11 +200,10 @@ The resource based groups are created and populated. ## Execute File System Action Task -Once the Create Groups action has been executed, the Modify Permissions action can be executed. -Follow the steps to execute the action. +After the Create Groups action has been executed, the Modify Permissions action can be executed. :::warning -Prior to executing the File System action tasks, allow a grace period, for example one +Before executing the File System action tasks, allow a grace period, for example one week. This is important for token refresh to occur as users log off and log on again. ::: @@ -216,7 +212,7 @@ week. This is important for token refresh to occur as users log off and log on a **Step 2 –** Enable the **Modify Permissions** action task. -**Step 3 –** Right-click on the **FS_TraverseGroups** job and select Run Job. +**Step 3 –** Right-click the **FS_TraverseGroups** job and select Run Job. - Wait for the queued job to execute. @@ -233,15 +229,13 @@ environment by the action modules. | List Traverse Group Changes | This report shows a list of changes made in the environment by the action modules. | None | This report is comprised of one elements:
  • Table – This table provides details on the changes made to the environment by the action modules
| - Follow the steps to analyze and report on action history. - :::warning -Disable all of the action tasks prior to generating the List Traverse Group Changes +Disable all of the action tasks before generating the List Traverse Group Changes report. ::: -**Step 1 –** On the Action Selection page, disable the **Modify Permissions** action task. Make sure +**Step 1 –** On the Action Selection page, disable the **Modify Permissions** action task. Ensure all of the action tasks are disabled. **Step 2 –** On the Analysis Selection page, enable the **Create Groups** and both **Show Table** diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/overview.md b/docs/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/overview.md index 5d890f4df9..b4497ffd98 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/overview.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/overview.md @@ -14,7 +14,7 @@ inheritance. ## Prerequisites -Action modules are available with a special Enterprise Auditor license. In order to use the Resource +Action modules are available with a special Enterprise Auditor license. To use the Resource Based Groups workflow, the following Enterprise Auditor licensing components are required: - File System Feature @@ -22,7 +22,7 @@ Based Groups workflow, the following Enterprise Auditor licensing components are - File System Actions Add-on - Active Directory Actions Add-on -The following job groups must be successfully run prior to using this workflow: +The following job groups must be successfully run before using this workflow: - .Active Directory Inventory Job Group - FileSystem > 0.Collection Job Group @@ -35,7 +35,7 @@ but it can be installed from the Instant Job Wizard. ![Resource Based Groups Job Group in the Jobs Tree](/images/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/jobstree.webp) -Once it has been installed into the Jobs tree, navigate to the solution: **Jobs** > **FileSystem** > +After it has been installed into the Jobs tree, navigate to the solution: **Jobs** > **FileSystem** > **Resource Based Groups**. The FS_TraverseGroups Job and the FS_ResourceBasedGroupsAICImport Job must be installed from the @@ -53,13 +53,13 @@ based groups model. The following jobs comprise the Resource Based Groups Job Group: - [FS_ResourceBasedGroups Job](/docs/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroups.md) - – This job will transform permission on specified folders to a resource based groups model + – This job will transform permissions on specified folders to a resource based groups model - [FS_TraverseGroups Job](/docs/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/fs_traversegroups.md) - – (Optional) This job can be used to create and apply permissions for traverse groups based on - previous resource based groups. The FS_TraverseGroupsJob must be added from the Instant Job - Library in order to be used. + – (Optional) Use this job to create and apply permissions for traverse groups based on + previous resource based groups. The FS_TraverseGroups Job must be added from the Instant Job + Library to be used. - [FS_ResourceBasedGroupAICImport Job](/docs/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroupaicimport.md) - – (Optional) This job imports resources and access groups from the FS_ResoureBasedGroup Job into + – (Optional) This job imports resources and access groups from the FS_ResourceBasedGroups Job into the Netwrix Access Information Center. The FS_ResourceBasedGroupsAICImport Job must be added from the Instant Job Library to be used. @@ -67,8 +67,8 @@ The following jobs comprise the Resource Based Groups Job Group: **Dependencies** -- The **.Active Directory Inventory** Job Group must be successfully run prior to running this job -- The **FileSystem** > **0.Collection** Job Group must be successfully run prior to running this job +- The **.Active Directory Inventory** Job Group must be successfully run before running this job +- The **FileSystem** > **0.Collection** Job Group must be successfully run before running this job **Targeted Hosts** @@ -77,8 +77,8 @@ The following jobs comprise the Resource Based Groups Job Group: **Schedule Frequency** -This job group can be scheduled to run as desired. Throughout this document reference to executing a -job refers to either manual execution or scheduled execution, according to the needs of the +This job group can be scheduled to run as desired. Throughout this document, executing a +job refers to either manual execution or scheduled execution, based on the needs of the organization. See the [Scheduling the Resource Based Groups Job Group](#scheduling-the-resource-based-groups-job-group) topic for additional information. @@ -96,5 +96,5 @@ scheduled for discrete one-time runs so that results may be reviewed after each [Schedule Jobs](/docs/accessanalyzer/11.6/admin/schedule/overview.md#schedule-jobs) topic for additional information. -Throughout this document reference to executing a job refers to either manual execution or scheduled -execution, according to the needs of the organization. +Throughout this document, executing a job refers to either manual execution or scheduled +execution, based on the needs of the organization. diff --git a/docs/accessanalyzer/11.6/solutions/nisinventory/nis_scan.md b/docs/accessanalyzer/11.6/solutions/nisinventory/nis_scan.md index ede2fadd82..a1ca86981c 100644 --- a/docs/accessanalyzer/11.6/solutions/nisinventory/nis_scan.md +++ b/docs/accessanalyzer/11.6/solutions/nisinventory/nis_scan.md @@ -27,7 +27,7 @@ This query must be modified. See the ### Configure the NIS Scan Query The NIS Scan job has been preconfigured to run with the default settings with the category of **Scan -NIS Users and Groups**. However, it is necessary to configure the targeted NIS domain. Follow the +NIS Users and Groups**. However, you must configure the targeted NIS domain. Follow the steps to set the target NIS domain and any desired customizations. **Step 1 –** Navigate to the **.NIS Inventory** > **NIS Scan** > **Configure** node and select @@ -40,7 +40,7 @@ opens. opens. :::warning -Do not make changes to other wizard pages as they have been pre-configured for the +Don't make changes to other wizard pages as they have been pre-configured for the purpose of this job. ::: @@ -48,7 +48,7 @@ purpose of this job. ![NIS Settings page](/images/accessanalyzer/11.6/admin/datacollector/nis/settings.webp) **Step 4 –** On the NIS Settings page, enter the **NIS Domain Name** for the targeted NIS domain. -This step is required prior to running this query. See the +This step is required before running this query. See the [NIS: NIS Settings](/docs/accessanalyzer/11.6/admin/datacollector/nis/settings.md) topic for additional information. @@ -71,7 +71,7 @@ View the analysis tasks by navigating to the **.NIS Inventory** > **NIS Scan** > and select **Analysis**. :::warning -Most of these analysis tasks are preconfigured and should not be modified or +Most of these analysis tasks are preconfigured and shouldn't be modified or deselected. There is one that is deselected by default, as it is for troubleshooting purposes. ::: @@ -84,13 +84,13 @@ The following analysis tasks are selected by default: - Groups – Enables the SA_NIS_Groups table to be accessible under the job’s Results node - Members – Enables the SA_NIS_GroupMembersView to be accessible under the job’s Results node -The following analysis task only needs to be selected when there is a need to remove the tables from +Select the following analysis task only when you need to remove the tables from the database: :::warning -This analysis task is for troubleshooting and cleanup only. Data will be deleted from -the database. Do not execute this task with the other analysis tasks, as that results in the -deletion of data that was just collected. +This analysis task is for troubleshooting and cleanup only. It deletes data from +the database. Don't execute this task with the other analysis tasks, as doing so deletes +data you just collected. ::: @@ -100,7 +100,7 @@ deletion of data that was just collected. ### Remove NIS Tables -Sometimes when troubleshooting a NIS Data Collector issue, it becomes necessary to clear the +When troubleshooting a NIS Data Collector issue, you might need to clear the standard reference tables. Follow these steps. **Step 1 –** Navigate to the **.NIS Inventory** > **NIS Scan** > **Configure** node and select @@ -111,13 +111,13 @@ task. **Step 3 –** Use the right-click menu on the analysis data grid to **Execute Analyses**. -**Step 4 –** After the analysis task has completed execution, the tables have been cleared from the +**Step 4 –** After the analysis task finishes running, the job clears the tables from the SQL database. :::warning -Do not forget to clear the Drop NIS Tables analysis task and reselect all of the other +Don't forget to clear the Drop NIS Tables analysis task and reselect all of the other analysis tasks. ::: -The next time the job is run, the standard reference tables are recreated in the database. +The next time you run the job, it recreates the standard reference tables in the database. diff --git a/docs/accessanalyzer/11.6/solutions/nisinventory/overview.md b/docs/accessanalyzer/11.6/solutions/nisinventory/overview.md index 7dff9d541a..cfabe9e173 100644 --- a/docs/accessanalyzer/11.6/solutions/nisinventory/overview.md +++ b/docs/accessanalyzer/11.6/solutions/nisinventory/overview.md @@ -28,12 +28,12 @@ when auditing NFS shares. This information can also be used in the Unix Solution **Location** The .NIS Inventory Solution is a core component of all Enterprise Auditor installations. It can be -installed from the Enterprise Auditor Instant Job Wizard.. +installed from the Enterprise Auditor Instant Job Wizard. ![.NIS Inventory Solution in the Jobs Tree](/images/accessanalyzer/11.6/solutions/nisinventory/jobstree.webp) -Once it has been installed into the Jobs tree, navigate to the solution: **Jobs** > **.NIS -Inventory**. This group has been named in such a way to keep it at the top of the Jobs tree. +After it has been installed into the Jobs tree, navigate to the solution: **Jobs** > **.NIS +Inventory**. This group's name keeps it at the top of the Jobs tree. ## NIS Scan Job diff --git a/docs/accessanalyzer/11.6/solutions/nisinventory/recommended.md b/docs/accessanalyzer/11.6/solutions/nisinventory/recommended.md index 11407fa417..8cbe7bbf35 100644 --- a/docs/accessanalyzer/11.6/solutions/nisinventory/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/nisinventory/recommended.md @@ -11,11 +11,11 @@ directly or scheduled. **Dependencies** -This job group does not have dependencies. +This job group doesn't have dependencies. **Targeted Hosts** -The host list assignment should be assigned under the **.NIS Inventory** > **NIS Scan** > **Hosts** +Assign the host list under the **.NIS Inventory** > **NIS Scan** > **Hosts** node. Select the custom host list containing the NIS servers or manually add the host in the **Individual hosts** section. See the [Unix Connection Profile & Host List](/docs/accessanalyzer/11.6/admin/datacollector/nis/configurejob.md) @@ -25,7 +25,7 @@ topic for additional information. The Connection Profile should be assigned in the **.NIS Inventory** > **NIS Scan** > **Job Properties** window on the **Connection** tab. It is set to **Use the Default Profile**, as -configured at the global settings level. However, if this is not the Connection Profile with the +configured at the global settings level. However, if this isn't the Connection Profile with the necessary permissions for targeting the NIS servers, select the **Select one of the following user defined profiles** option and select the appropriate Connection Profile. See the [Unix Connection Profile & Host List](/docs/accessanalyzer/11.6/admin/datacollector/nis/configurejob.md) @@ -33,8 +33,8 @@ topic for additional information. **Schedule Frequency** -It is recommended to schedule the .NIS Inventory job group to run once a day. If there are frequent -changes within the target environment, then it can be executed more often. It is best to rerun it +Schedule the .NIS Inventory job group to run once a day. If the target environment changes +frequently, you can run it more often. It is best to rerun it anytime changes might have occurred. **Run at the Solution Level** @@ -43,9 +43,9 @@ The job in the .NIS Inventory job group can be run at either the job or job grou **Query Configuration** -The solution requires the NIS domain to be configured in the **Inventory Scan** query. Navigate to -the **NIS Settings** page of the NIS Data Collector Wizard. Optionally, modifications can be made -for SID mappings within the **NIS Scan** job. See the +The solution requires you to configure the NIS domain in the **Inventory Scan** query. Navigate to +the **NIS Settings** page of the NIS Data Collector Wizard. Optionally, modify SID mappings within +the **NIS Scan** job. See the [NIS Scan Job](/docs/accessanalyzer/11.6/solutions/nisinventory/nis_scan.md) topic for additional information. @@ -56,11 +56,11 @@ analysis task is deselected by default, as it is for troubleshooting purposes on **History Retention** -History retention is not supported and should be turned off. +History retention isn't supported. Turn it off. **Multi-console Support** -Multi-console is not supported. +Multi-console isn't supported. **Workflow** diff --git a/docs/accessanalyzer/11.6/solutions/overview.md b/docs/accessanalyzer/11.6/solutions/overview.md index 41a5e74183..a8cf1fb7ff 100644 --- a/docs/accessanalyzer/11.6/solutions/overview.md +++ b/docs/accessanalyzer/11.6/solutions/overview.md @@ -19,16 +19,16 @@ These solutions are broken down by the top-level job group that comprises the so | .Entra ID Inventory | The .Entra ID Inventory Solution is designed to inventory, analyze, and report on Microsoft Entra ID. It provides essential user and group membership details to the Entra ID Solution. Key information includes managers, email addresses, and direct memberships. Collected data helps an organization identify toxic conditions like nested groups, circular nesting, disabled users, and duplicate groups. The user and group information assists with understanding probable group ownership, group memberships, largest groups, user status, attribute completion, and synchronization status between on-premises Active Directory and Microsoft Entra ID.
**Core Solution** | | .NIS Inventory | The .NIS Inventory Solution is designed to provide essential user and group membership information from a NIS domain, mapping these principals to Windows-style SIDs. This provides valuable information to the File Systems Solution when auditing NFS shares.
**Core Solution** | | Active Directory | The Active Directory Solution is designed to provide the information every administrator needs regarding Active Directory configuration, operational management, troubleshooting, analyzing effective permissions, and tracking who is making what changes within your organization.
**Requires Active Directory Licensed Feature** | -| Active Directory Permissions Analyzer | The Active Directory Permissions Analyzer Solution is designed to easily and automatically determine effective permissions applied to any and all Active Directory objects, at any scope, allowing for the most authoritative view available of who has access to what in Active Directory.
**Requires Active Directory Permissions Analyzer Licensed Feature** | -| AnyID Connectors | The AnyID Connectors Solution allows you to quickly find where data for identities are stored, reducing the response time to Data Subject Access Requests (DSARs). Integration with third party repositories allows you to perform exact data matching for profiles such as employees, customers, students, or patients across any data repository. | +| Active Directory Permissions Analyzer | The Active Directory Permissions Analyzer Solution is designed to automatically determine effective permissions applied to any and all Active Directory objects, at any scope, allowing for the most authoritative view available of who has access to what in Active Directory.
**Requires Active Directory Permissions Analyzer Licensed Feature** | +| AnyID Connectors | Use the AnyID Connectors Solution to quickly find where data for identities is stored, reducing the response time to Data Subject Access Requests (DSARs). Integration with third-party repositories enables exact data matching for profiles such as employees, customers, students, or patients across any data repository. | | Amazon Web Services | Enterprise Auditor for AWS allows organizations to secure their data residing in Amazon Web Services (AWS) S3 platform, reducing their risk exposure through proactive, automated auditing and reporting of S3 permissions, sensitive data, and ultimately a consolidated view of user access rights across dozens of structured and unstructured data resources both on-premises and in the cloud. | -| Box | The Box solution set contains jobs to provide visibility into Box access rights, policies, configurations, activities, and more, ensuring you never lose sight or control of your critical assets residing in Box.
**Requires Box Collection Licensed Feature** | -| Databases | Enterprise Auditor Databases Solution Set is a comprehensive set of pre-configured audit jobs and reports that provide visibility into various aspects of supported databases.
  • Azure SQL – The Azure SQL Solution Set is a comprehensive set of pre-configured audit jobs and reports that provide visibility into various aspects of Azure SQL : Users and Roles, Sensitive Data Discovery, Object Permissions, Configuration, and User Activity.
  • Db2 – The Db2 Solution Set is a comprehensive set of pre-configured audit jobs and reports that provides visibility into various aspects of a Db2 Databases: Sensitive Data Discovery and Object Permissions.
  • Instance Discovery – The Instance Discovery Solution discovers instances on supported database servers.
  • MongoDB Solution – The MongoDB Solution automates the process of understanding where MongDB databases exist and provides an overview of the MongoDB environment in order to answer questions around data access. With visibility into every corner of MongoDB and the operating system it relies upon, organizations can proactively highlight and prioritize risks to sensitive data. Additionally, organizations can automate manual, time-consuming, and expensive processes associated with compliance, security, and operations to easily adhere to best practices that keep MongoDB Server safe and operational.
  • MySQL Solution – The MySQL Solution automates the process of understanding where SQL databases exist and provides an overview of the MySQL environment in order to answer questions around data access. With visibility into every corner of Microsoft SQL Server and the Windows operating system it relies upon, organizations can proactively highlight and prioritize risks to sensitive data. Additionally, organizations can automate manual, time-consuming, and expensive processes associated with compliance, security, and operations to easily adhere to best practices that keep SQL Server safe and operational.
  • Oracle Solution – The Oracle Solution delivers comprehensive permissions, activity, and sensitive data auditing and reporting for Oracle databases. Through the power of Enterprise Auditor, users can automate Oracle instance discovery, understand who has access to their Oracle databases, the level of permission they have, and who is leveraging their access privileges, identify the location of sensitive information, measure adherence to best practices, and generate workflows and reports to satisfy security, compliance, and operational requirements.
  • PostgreSQL Solution – Enterprise Auditor PostgreSQL Solution Set is a set of pre-configured audit jobs and reports that provides visibility into PostgreSQL Sensitive Data.
  • Redshift – Enterprise Auditor Redshift Solution Set is a set of pre-configured audit jobs and reports that provides visibility into Redshift Sensitive Data.
  • SQL Solution – The SQL Solution is an auditing, compliance, and governance solution for Microsoft SQL Server database. Key capabilities include effective access calculation, sensitive data discovery, security configuration assessment, and database activity monitoring.

**Requires SQL Licensed Feature** | +| Box | The Box solution set contains jobs to provide visibility into Box access rights, policies, configurations, activities, and more, so you always have visibility and control over your critical assets in Box.
**Requires Box Collection Licensed Feature** | +| Databases | Enterprise Auditor Databases Solution Set is a comprehensive set of pre-configured audit jobs and reports that provide visibility into various aspects of supported databases.
  • Azure SQL – The Azure SQL Solution Set is a comprehensive set of pre-configured audit jobs and reports that provide visibility into various aspects of Azure SQL : Users and Roles, Sensitive Data Discovery, Object Permissions, Configuration, and User Activity.
  • Db2 – The Db2 Solution Set is a comprehensive set of pre-configured audit jobs and reports that provides visibility into various aspects of a Db2 Databases: Sensitive Data Discovery and Object Permissions.
  • Instance Discovery – The Instance Discovery Solution discovers instances on supported database servers.
  • MongoDB Solution – The MongoDB Solution automates the process of understanding where MongDB databases exist and provides an overview of the MongoDB environment to answer questions around data access. With full visibility into MongoDB and the operating system it relies upon, organizations can proactively highlight and prioritize risks to sensitive data. Additionally, organizations can automate manual, time-consuming, and expensive processes associated with compliance, security, and operations to easily adhere to best practices that keep MongoDB Server safe and operational.
  • MySQL Solution – The MySQL Solution automates the process of understanding where MySQL databases exist and provides an overview of the MySQL environment to answer questions around data access. With full visibility into MySQL and the operating system it relies upon, organizations can proactively highlight and prioritize risks to sensitive data. Additionally, organizations can automate manual, time-consuming, and expensive processes associated with compliance, security, and operations to easily adhere to best practices that keep MySQL safe and operational.
  • Oracle Solution – The Oracle Solution delivers comprehensive permissions, activity, and sensitive data auditing and reporting for Oracle databases. Through the power of Enterprise Auditor, users can automate Oracle instance discovery, understand who has access to their Oracle databases, the level of permission they have, and who is leveraging their access privileges, identify the location of sensitive information, measure adherence to best practices, and generate workflows and reports to satisfy security, compliance, and operational requirements.
  • PostgreSQL Solution – Enterprise Auditor PostgreSQL Solution Set is a set of pre-configured audit jobs and reports that provides visibility into PostgreSQL Sensitive Data.
  • Redshift – Enterprise Auditor Redshift Solution Set is a set of pre-configured audit jobs and reports that provides visibility into Redshift Sensitive Data.
  • SQL Solution – The SQL Solution is an auditing, compliance, and governance solution for Microsoft SQL Server database. Key capabilities include effective access calculation, sensitive data discovery, security configuration assessment, and database activity monitoring.

**Requires SQL Licensed Feature** | | Dropbox | The Dropbox Solution is an auditing, compliance, and governance solution for Dropbox for Business. Key capabilities include effective access calculation, sensitive data discovery, file content inspection, inactive access and stale data identification, and entitlement collection for integration with Identity & Access Management (IAM) processes. \*Requires Dropbox Collection Licensed Feature | | Entra ID | The Entra ID Solution is a comprehensive set of audit jobs and reports that provide the information regarding Microsoft Entra ID configuration, operational management, and troubleshooting. The jobs within this group help pinpoint potential areas of administrative and security concerns related to Microsoft Entra ID users and groups, including syncing with on-premises Active Directory.
**Requires Entra ID Licensed Feature** | | Exchange | The Exchange Solution provides auditing and reporting on multiple aspects of the Exchange environment to assist with identifying risk, understanding usage, and decreasing bloat. Areas of focus include Audit and Compliance, Maintenance and Cleanup, Metrics and Capacity, Operations and Health, Public Folders and Configuration Baseline.
**Requires Exchange Licensed Feature** | | FileSystem | The File Systems Solution is an auditing, compliance, and governance solution for Windows, NAS, Unix, and Linux file systems. Key capabilities include effective access calculation, data owner identification, governance workflows including entitlement reviews and self-service access requests, sensitive data discovery and classification, open access remediation, least-privilege access transformation, and file activity monitoring.
**Requires File System Reports Licensed Feature** | | SharePoint | The SharePoint Solution is a comprehensive set of audit jobs and reports which provide the information every administrator needs regarding SharePoint on-premises and SharePoint Online infrastructure, configuration, performance, permissions, required ports, and effective rights.
**Requires SharePoint Reports Licensed Feature** | -| Unix | The Unix Solution reports on areas of administrative concern for Unix and Linux systems. Attention is given to users and group details, privileged access rights, and NFS and Samba sharing configurations.
**Requires Unix Licensed Feature** | +| Unix | The Unix Solution reports on areas of administrative concern for Unix and Linux systems. The solution focuses on user and group details, privileged access rights, and NFS and Samba sharing configurations.
**Requires Unix Licensed Feature** | | Windows | The Windows Solution allows organizations to quickly inventory, assess, and secure their Windows desktop and server infrastructure from a central location. Key capabilities include privileged account discovery, security configuration and vulnerability assessment, compliance reporting, and asset inventory. | diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/activity/forensics/overview.md b/docs/accessanalyzer/11.6/solutions/sharepoint/activity/forensics/overview.md index a2b497d6f3..da7713583b 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/activity/forensics/overview.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/activity/forensics/overview.md @@ -20,4 +20,4 @@ The jobs in the Forensics Job Group are: the past 30 days - [SP_SensitiveDataActivity Job](/docs/accessanalyzer/11.6/solutions/sharepoint/activity/forensics/sp_sensitivedataactivity.md) – Highlights user activity involving sensitive data and provides details on who is interacting - with your environments sensitive content + with your environment's sensitive content diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/activity/forensics/sp_deletions.md b/docs/accessanalyzer/11.6/solutions/sharepoint/activity/forensics/sp_deletions.md index 6b0c1bc857..d46cdcff58 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/activity/forensics/sp_deletions.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/activity/forensics/sp_deletions.md @@ -14,7 +14,7 @@ Navigate to the **Jobs** > **SharePoint** > **7.Activity** > **Forensics** > **S **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: @@ -26,7 +26,7 @@ The default analysis task is: - Analyze SPAC Deletion Events – Creates the SA_SPAC_Deletions_Last30Days table accessible under the job’s Results node -In addition to the tables and views created by the analysis tasks, the SQL_Deletions Job produces +In addition to the tables and views created by the analysis tasks, the SP_Deletions Job produces the following pre-configured report: | Report | Description | Default Tags | Report Elements | diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/activity/forensics/sp_permissionchanges.md b/docs/accessanalyzer/11.6/solutions/sharepoint/activity/forensics/sp_permissionchanges.md index d5b4d88ac4..7f00b378df 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/activity/forensics/sp_permissionchanges.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/activity/forensics/sp_permissionchanges.md @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **SharePoint** > **7.Activity** > **Forensics** > **SP_PermissionChanges** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -29,9 +29,9 @@ The default analysis tasks are: - Permission Changes Counts – Creates the SA_SP_PermissionChanges_Counts table accessible under the job’s Results node -In addition to the tables and views created by the analysis tasks, the SQL_PermissionChanges Job +In addition to the tables and views created by the analysis tasks, the SP_PermissionChanges Job produces the following pre-configured report: | Report | Description | Default Tags | Report Elements | | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Permission Changes | This report identifies SharePoint permission changes based on activity events and determines whether or not that permission change is considered a high security risk. | None | This report is comprised of two elements:
  • Bar Chart – Displays permission change activity in the past seven days
  • Table – Provides permission change details
| +| Permission Changes | This report identifies SharePoint permission changes based on activity events and determines whether that permission change is considered a high security risk. | None | This report is comprised of two elements:
  • Bar Chart – Displays permission change activity in the past seven days
  • Table – Provides permission change details
| diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/activity/forensics/sp_sensitivedataactivity.md b/docs/accessanalyzer/11.6/solutions/sharepoint/activity/forensics/sp_sensitivedataactivity.md index 8f38c9e434..a89f146d95 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/activity/forensics/sp_sensitivedataactivity.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/activity/forensics/sp_sensitivedataactivity.md @@ -7,7 +7,7 @@ sidebar_position: 30 # SP_SensitiveDataActivity Job This job highlights user activity involving sensitive data and provides details on who is -interacting with your environments sensitive content. +interacting with your environment's sensitive content. ## Analysis Tasks for the SP_SensitiveDataActivity Job @@ -16,7 +16,7 @@ Navigate to the **Jobs** > **SharePoint** > **7.Activity** > **Forensics** > tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -30,9 +30,9 @@ The default analysis tasks are: - Sensitive Data Activity User Count – Creates an interim processing table in the database for use by downstream analysis and report generation -In addition to the tables and views created by the analysis tasks, the SQL_SensitiveDataActivity Job +In addition to the tables and views created by the analysis tasks, the SP_SensitiveDataActivity Job produces the following pre-configured report: | Report | Description | Default Tags | Report Elements | | ----------------------- | -------------------------------------------------- | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Sensitive Data Activity | This Report shows user activity on sensitive data. | None | This report is comprised of two elements:
  • Bar Chart – Displays sensitive data activity
  • Table – Provides details on sensitive data activity
| +| Sensitive Data Activity | This report shows user activity on sensitive data. | None | This report is comprised of two elements:
  • Bar Chart – Displays sensitive data activity
  • Table – Provides details on sensitive data activity
| diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/activity/overview.md b/docs/accessanalyzer/11.6/solutions/sharepoint/activity/overview.md index 4d65404b7f..1ce203bc7b 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/activity/overview.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/activity/overview.md @@ -7,7 +7,7 @@ sidebar_position: 90 # 7.Activity Job Group The 7.Activity job group generates summary and detail reports of SharePoint activity on the -specified sites. These reports can be used for identifying file, folder, and user related activity +specified sites. Use these reports to identify file, folder, and user related activity across your SharePoint environment. ![7.Activity Job Group in the Jobs Tree](/images/accessanalyzer/11.6/solutions/sharepoint/activity/jobstree.webp) @@ -17,6 +17,6 @@ The job groups in the 7.Activity Job Group are: - [Forensics Job Group](/docs/accessanalyzer/11.6/solutions/sharepoint/activity/forensics/overview.md) – Highlights deletions, group membership changes, permission changes, and activity around sensitive data -- [Usage Statistics Job Group](/docs/accessanalyzer/11.6/solutions/sharepoint/activity/usagestatistics/overview.md)– - Identifies long term trends of activity across your SharePoint environment highlighting most +- [Usage Statistics Job Group](/docs/accessanalyzer/11.6/solutions/sharepoint/activity/usagestatistics/overview.md) + – Identifies long term trends of activity across your SharePoint environment highlighting most active sites and users as well as stale users diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/activity/usagestatistics/overview.md b/docs/accessanalyzer/11.6/solutions/sharepoint/activity/usagestatistics/overview.md index d659d0f40c..0e6c140664 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/activity/usagestatistics/overview.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/activity/usagestatistics/overview.md @@ -14,7 +14,7 @@ environment highlighting most active sites and users as well as stale sites. The jobs in the Usage Statistics Job Group are: - [SP_InactiveSites Job](/docs/accessanalyzer/11.6/solutions/sharepoint/activity/usagestatistics/sp_inactivesites.md) - – Highlights your environments least active Sites or Site Collections + – Highlights your environment's least active Sites or Site Collections - [SP_MostActiveSites Job](/docs/accessanalyzer/11.6/solutions/sharepoint/activity/usagestatistics/sp_mostactivesites.md) – Identifies the top five most active sites monitored by Enterprise Auditor - [SP_MostActiveUsers Job](/docs/accessanalyzer/11.6/solutions/sharepoint/activity/usagestatistics/sp_mostactiveusers.md) diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/activity/usagestatistics/sp_inactivesites.md b/docs/accessanalyzer/11.6/solutions/sharepoint/activity/usagestatistics/sp_inactivesites.md index 0ea8a3d1ed..2c0cd77010 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/activity/usagestatistics/sp_inactivesites.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/activity/usagestatistics/sp_inactivesites.md @@ -6,7 +6,7 @@ sidebar_position: 10 # SP_InactiveSites Job -This job highlights your environments least active Sites or Site Collections. +This job highlights your environment's least active Sites or Site Collections. ## Analysis Tasks for the SP_InactiveSites Job @@ -14,7 +14,7 @@ Navigate to the **Jobs** > **SharePoint** > **7.Activity** > **Usage Statistics* **SP_InactiveSites** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/activity/usagestatistics/sp_mostactivesites.md b/docs/accessanalyzer/11.6/solutions/sharepoint/activity/usagestatistics/sp_mostactivesites.md index 9242f51d6e..66767c63ce 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/activity/usagestatistics/sp_mostactivesites.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/activity/usagestatistics/sp_mostactivesites.md @@ -14,7 +14,7 @@ Navigate to the **Jobs** > **SharePoint** > **7.Activity** > **Usage Statistics* **SP_MostActiveSites** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: @@ -31,4 +31,4 @@ produces the following pre-configured report: | Report | Description | Default Tags | Report Elements | | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Most Active Sites – Last 30 Days | This report identifies the top five most active sites for the past 30 days. [Reads], [Updates], [Deletes], [Permission Changes] fields reflect the number of unique operations of each type that was performed on the site for this time frame. Unique Resources Accessed, number of active user performing operations on the site, as well as whether or not the active site contains sensitive information. | None | This report is comprised of two elements:
  • Bar Chart – Displays information on most active sites by event count
  • Table – Provides details on most active sites by event count
| +| Most Active Sites – Last 30 Days | This report identifies the top five most active sites for the past 30 days. [Reads], [Updates], [Deletes], [Permission Changes] fields reflect the number of unique operations of each type that was performed on the site for this time frame. Unique Resources Accessed, number of active user performing operations on the site, as well as whether the active site contains sensitive information. | None | This report is comprised of two elements:
  • Bar Chart – Displays information on most active sites by event count
  • Table – Provides details on most active sites by event count
| diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/activity/usagestatistics/sp_mostactiveusers.md b/docs/accessanalyzer/11.6/solutions/sharepoint/activity/usagestatistics/sp_mostactiveusers.md index 7bfaba8334..36047303e1 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/activity/usagestatistics/sp_mostactiveusers.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/activity/usagestatistics/sp_mostactiveusers.md @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **SharePoint** > **7.Activity** > **Usage Statistics* **SP_MostActiveUsers** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: @@ -24,8 +24,8 @@ preconfigured for this job. The default analysis task is: -- Most Active Users Last 30 Days – SA_SPAC_MostActiveUsers_Last30Days table accessible under the - job’s Results node +- Most Active Users Last 30 Days – Creates the SA_SPAC_MostActiveUsers_Last30Days table accessible + under the job’s Results node In addition to the tables and views created by the analysis tasks, the SQL_MostActiveUsers Job produces the following pre-configured report: diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/collection/1-spseek_systemscans.md b/docs/accessanalyzer/11.6/solutions/sharepoint/collection/1-spseek_systemscans.md index 23a635a9c4..830cdac3e8 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/collection/1-spseek_systemscans.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/collection/1-spseek_systemscans.md @@ -6,8 +6,8 @@ sidebar_position: 10 # 1-SPSEEK_SystemScans Job -This job is responsible for building the Tier2 SPDLP database repositories, which contain -information regarding sensitive content that exists within SharePoint. +This job builds the Tier2 SPDLP database repositories, which contain information about sensitive +content in SharePoint. ## Queries for the 1-SPSEEK_SystemScans Job @@ -22,18 +22,18 @@ The query for the 1-SPSEEK SystemScans Job is: ### Configure the Query for the 1-SPSEEK_SystemScans Job The 1-SPSEEK_SystemScans Job has been preconfigured to run with the default settings using the SPAA -Data Collector category of Scan for Sensitive Content, which is not visible within the SharePoint +Data Collector category of Scan for Sensitive Content, which isn't visible within the SharePoint Access Auditor Data Collector Wizard when opened from within this job. :::warning -Users should not change scans in a way that would result in less data being returned on +Users shouldn't change scans in a way that would result in less data being returned on a subsequent scan (i.e. scanning fewer web applications, scanning fewer site collections, or a shallower depth scan). Those resources not included in a subsequent scan are marked as deleted in the Tier 2 database and subsequently removed from the Tier 1 database. ::: -Follow the steps to set any desired customizations. +To set any desired customizations: **Step 1 –** Navigate to the **Jobs** > **SharePoint** > **0.Collection** > **1-SPSEEK_SystemScans** > **Configure** node and select **Queries**. @@ -95,7 +95,7 @@ All** and **Clear All** buttons. Click **Next**. _(Optional)_ To create custom c topic for additional information. :::warning -Do not configure the options on the Results page. +Don't configure the options on the Results page. ::: diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/collection/2-spaa_systemscans.md b/docs/accessanalyzer/11.6/solutions/sharepoint/collection/2-spaa_systemscans.md index 28ffcd3dc4..e443ae1f1d 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/collection/2-spaa_systemscans.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/collection/2-spaa_systemscans.md @@ -22,20 +22,20 @@ The query for the 2-SPAA_SystemScans Job is: ### Configure 2-SPAA_SystemScans Job The 2-SPAA_SystemScans Job has been preconfigured to run with the default settings using the SPAA -Data Collector category of Scan SharePoint Access, which is not visible within the SharePoint Access +Data Collector category of Scan SharePoint Access, which isn't visible within the SharePoint Access Auditor Data Collector Wizard when opened from within this job. :::warning -Users should not change scans in a way that would result in less data being returned on +Users shouldn't change scans in a way that would result in less data being returned on a subsequent scan (i.e. scanning fewer web applications, scanning fewer site collections, or a shallower depth scan). Those resources not included in a subsequent scan are marked as deleted in the Tier 2 database and subsequently removed from the Tier 1 database. ::: -Follow the steps to set any desired customizations. +To set any desired customizations: -**Step 1 –** Navigate to the **Jobs** > **SharePoint** > **0.Collection** > **1-SPAA_SystemScans** > +**Step 1 –** Navigate to the **Jobs** > **SharePoint** > **0.Collection** > **2-SPAA_SystemScans** > **Configure** node and select the **Queries** node. **Step 2 –** In the Query Selection view, click **Query Properties**. The Query Properties window @@ -70,7 +70,7 @@ setting as desired and click **Next**. page, use the default settings unless an agent scan mode is desired. Click **Next**. :::warning -Do not configure the options on the Results page. +Don't configure the options on the Results page. ::: @@ -79,4 +79,4 @@ Do not configure the options on the Results page. **Step 9 –** On the Summary page, click **Finish** to save any setting modifications or click **Cancel** if no changes were made. Then click **OK** to close the Query Properties window. -If changes were made, the 1-SPAA_SystemScans Job has now been customized. +If changes were made, the 2-SPAA_SystemScans Job has now been customized. diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/collection/3-spac_systemscans.md b/docs/accessanalyzer/11.6/solutions/sharepoint/collection/3-spac_systemscans.md index 03a34ecde5..d159159cbf 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/collection/3-spac_systemscans.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/collection/3-spac_systemscans.md @@ -12,11 +12,11 @@ in each structural level in the SharePoint farm. ## Queries for the 3-SPAC_SystemScans Job The 3-SPAC_SystemScans Job has been preconfigured to run with the default settings using the SPAA -Data Collector category of Scan SharePoint Activity, which is not visible within the SharePoint +Data Collector category of Scan SharePoint Activity, which isn't visible within the SharePoint Access Auditor Data Collector Wizard when opened from within this job. :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/collection/4-spseek_bulkimport.md b/docs/accessanalyzer/11.6/solutions/sharepoint/collection/4-spseek_bulkimport.md index 2eab5bb280..5071d87746 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/collection/4-spseek_bulkimport.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/collection/4-spseek_bulkimport.md @@ -6,8 +6,8 @@ sidebar_position: 40 # 4-SPSEEK_BulkImport Job -This job is responsible for retrieving the Tier 2 SPDLP database information and importing it to the -SQL Server where Enterprise Auditor stores data. +This job retrieves the Tier 2 SPDLP database information and imports it to the SQL Server where +Enterprise Auditor stores data. ## Queries for the 4-SPSEEK_BulkImport Job @@ -22,7 +22,7 @@ The query for the 4-SPSEEK Bulk Import Job is: ### Configure 4-SPSEEK_BulkImport Job The 4-SPSEEK_BulkImport Job has been preconfigured to run with the default settings with the SPAA -Data Collector category of **Bulk Import Sensitive Content Scan Results**, which is not visible +Data Collector category of **Bulk Import Sensitive Content Scan Results**, which isn't visible within the SharePoint Access Auditor Data Collector Wizard when opened from within this job. Follow the steps to set any desired customizations. @@ -38,16 +38,16 @@ displays. **Step 4 –** On the [SPAA: Bulk Import Settings](/docs/accessanalyzer/11.6/admin/datacollector/spaa/bulkimportsettings.md) -page, the **Set Host Identifier** is not configured by default. Click **Next**. +page, the **Set Host Identifier** isn't configured by default. Click **Next**. :::note -Unless SQL Server Replication is used, it should not be necessary to adjust the **Host +Unless SQL Server Replication is used, it shouldn't be necessary to adjust the **Host Identifier** seed. ::: :::warning -Do not configure the options on the Results page. +Don't configure the options on the Results page. ::: @@ -81,6 +81,6 @@ The default analysis tasks are: - **5. Create DLP views** – Creates the SA_SPDLP_MatchesView - **6. Create exceptions view** – Creates the SA_SPAA_ExceptionsView -The following analysis task is not selected by default, but can be enabled: +The following analysis task isn't selected by default, but can be enabled: - Display Match Hits – Displays the SA_SPDLP_MatchesHitsView within Enterprise Auditor. diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/collection/5-spaa_bulkimport.md b/docs/accessanalyzer/11.6/solutions/sharepoint/collection/5-spaa_bulkimport.md index d387d5c3a9..9aee08dcb6 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/collection/5-spaa_bulkimport.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/collection/5-spaa_bulkimport.md @@ -6,8 +6,8 @@ sidebar_position: 50 # 5-SPAA_BulkImport Job -This job is responsible for retrieving the SPAA Tier 2 database information and import it to the -Enterprise Auditor SQL database. +This job retrieves the SPAA Tier 2 database information and imports it to the Enterprise Auditor SQL +database. ## Queries for the 5-SPAA_BulkImport Job @@ -22,11 +22,11 @@ The query for the 5-SPAA_BulkImport Job is: ### Configure 5-SPAA_BulkImport Job The 5-SPAA_BulkImport Job has been preconfigured to run with the default settings with the SPAA Data -Collector category of Bulk Import Access Scan Results, which is not visible within the SharePoint -Access Auditor Data Collector Wizard when opened from within this job. Follow the steps to set any -desired customizations. +Collector category of Bulk Import Access Scan Results, which isn't visible within the SharePoint +Access Auditor Data Collector Wizard when opened from within this job. To set any +desired customizations: -**Step 1 –** Navigate to the **Jobs** > **SharePoint** > **0.Collection** > **2-SPAA_BulkImport** > +**Step 1 –** Navigate to the **Jobs** > **SharePoint** > **0.Collection** > **5-SPAA_BulkImport** > **Configure** node and select the **Queries** node. **Step 2 –** In the Query Selection view, click **Query Properties**. The Query Properties window @@ -38,16 +38,16 @@ displays. **Step 4 –** On the [SPAA: Bulk Import Settings](/docs/accessanalyzer/11.6/admin/datacollector/spaa/bulkimportsettings.md) -page, the **Set Host Identifier** is not configured by default. Click **Next**. +page, the **Set Host Identifier** isn't configured by default. Click **Next**. :::note -Unless SQL Server Replication is used, it should not be necessary to adjust the **Host +Unless SQL Server Replication is used, it shouldn't be necessary to adjust the **Host Identifier** seed. ::: :::warning -Do not configure the options on the Results page. +Don't configure the options on the Results page. ::: @@ -60,7 +60,7 @@ If changes were made, the 5-SPAA_BulkImport Job has now been customized. ## Analysis Tasks for 5-SPAA_BulkImport Job -Navigate to the **Jobs** > **SharePoint** > **0.Collection** > **2-SPAA_BulkImport** > **Configure** +Navigate to the **Jobs** > **SharePoint** > **0.Collection** > **5-SPAA_BulkImport** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/collection/6-spac_bulkimport.md b/docs/accessanalyzer/11.6/solutions/sharepoint/collection/6-spac_bulkimport.md index 0dc0420578..a9c3d91fe6 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/collection/6-spac_bulkimport.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/collection/6-spac_bulkimport.md @@ -6,8 +6,8 @@ sidebar_position: 60 # 6-SPAC_BulkImport Job -This job is responsible for retrieving the SPAC Tier 2 database information and import it to the -Enterprise Auditor SQL database. +This job retrieves the SPAC Tier 2 database information and imports it to the Enterprise Auditor SQL +database. ## Queries for the 6-SPAC_BulkImport Job @@ -22,11 +22,11 @@ The query for the 6-SPAC_BulkImport Job is: ### Configure the Query for the 6-SPAC_BulkImport Job The 6-SPAC_BulkImport Job has been preconfigured to run with the default settings with the category -of Bulk Import SharePoint Activity Scan Results, which is not visible within the SharePoint Access -Auditor Data Collector Wizard when opened from within this job. Follow the steps to set any desired -customizations. +of Bulk Import SharePoint Activity Scan Results, which isn't visible within the SharePoint Access +Auditor Data Collector Wizard when opened from within this job. To set any desired +customizations: -**Step 1 –** Navigate to the **Jobs** > **SharePoint** > **0.Collection** > **2-SPAC_BulkImport** > +**Step 1 –** Navigate to the **Jobs** > **SharePoint** > **0.Collection** > **6-SPAC_BulkImport** > **Configure** node and select **Queries**. **Step 2 –** In the Query Selection view, click **Query Properties**. The Query Properties window @@ -38,16 +38,16 @@ displays. **Step 4 –** On the [SPAA: Bulk Import Settings](/docs/accessanalyzer/11.6/admin/datacollector/spaa/bulkimportsettings.md) -page, the **Set Host Identifier** is not configured by default. Click **Next**. +page, the **Set Host Identifier** isn't configured by default. Click **Next**. :::note -Unless SQL Server Replication is used, it should not be necessary to adjust the **Host +Unless SQL Server Replication is used, it shouldn't be necessary to adjust the **Host Identifier** seed. ::: :::warning -Do not configure the options on the Results page. +Don't configure the options on the Results page. ::: @@ -58,7 +58,7 @@ Do not configure the options on the Results page. If changes were made, the 6-SPAC_BulkImport Job has now been customized. -## Analysis Tasks for 2-SPAC_BulkImport Job +## Analysis Tasks for 6-SPAC_BulkImport Job Navigate to the **Jobs** > **SharePoint** > **0.Collection** > **6-SPAC_BulkImport** > **Configure** node and select **Analysis** to view the analysis tasks. diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/collection/7-spaa_exceptions.md b/docs/accessanalyzer/11.6/solutions/sharepoint/collection/7-spaa_exceptions.md index fc9302fa9e..9730d520b1 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/collection/7-spaa_exceptions.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/collection/7-spaa_exceptions.md @@ -6,12 +6,12 @@ sidebar_position: 70 # 7-SPAA_Exceptions Job -This job searches scanned data for resources that match high risk conditions and retrieving a +This job searches scanned data for resources that match high risk conditions and retrieves a summary of SharePoint exceptions per host. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/11.6/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -27,14 +27,14 @@ The 7-SPAA_Exceptions page has the following configurable parameters: See the -[Customizable Analysis Tasks for the 7-SPAA_Exceptions Job](#customizable-analysis-tasks-for-the-7-spaa_exceptions-job) +[Customizable Analysis Tasks for the 7-SPAA_Exceptions Job](#customizable-analysis-tasks-for-the-7-spaaexceptions-job) for additional information. ## Analysis Tasks 7-SPAA_Exceptions Job -The 3-SPAA_Exceptions Job does not use the SPAA Data Collector. Instead it runs analysis on the data -returned by the 2-SPAA_BulkImport Job. View the analysis tasks by navigating to the **Jobs** > -**SharePoint** > **0.Collection** > **3-SPAA_Exceptions** > **Configure** node and select +The 7-SPAA_Exceptions Job doesn't use the SPAA Data Collector. Instead it runs analysis on the data +returned by the 5-SPAA_BulkImport Job. View the analysis tasks by navigating to the **Jobs** > +**SharePoint** > **0.Collection** > **7-SPAA_Exceptions** > **Configure** node and select **Analysis**. :::warning @@ -48,17 +48,17 @@ selected analysis tasks. The default analysis tasks are: - Open resources – Any site collections, sites, libraries, lists, or folders that are openly - accessible. Can be deselected if open resource information is not desired. + accessible. Can be deselected if open resource information isn't desired. - This analysis task contains a configurable parameter: `#opengroups` - Disabled users – Any site collections, sites, libraries, lists, or folders where disabled users - have been granted access. Can be deselected if disabled user information is not desired. + have been granted access. Can be deselected if disabled user information isn't desired. - Stale users – Any site collections, sites, libraries, lists, or folders where stale users have - been granted access. Stale users are user who have not logged in for more than 120 days. Can be - deselected if stale user information is not desired. -- Unresolved SID – Matches SIDs to .Active Directory Inventory Job Group data to resolve for those - users using legacy SIDS or deleted users. + been granted access. Stale users are users who have not logged in for more than 120 days. Can be + deselected if stale user information isn't desired. +- Unresolved SID – Matches SIDs to the Active Directory Inventory Job Group data to resolve for + those users using legacy SIDS or deleted users. - Show view – Displays views within the Results node of the Enterprise Auditor Console. ### Customizable Analysis Tasks for the 7-SPAA_Exceptions Job diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/collection/overview.md b/docs/accessanalyzer/11.6/solutions/sharepoint/collection/overview.md index 484efcba3a..48bcda562c 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/collection/overview.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/collection/overview.md @@ -6,8 +6,8 @@ sidebar_position: 20 # 0.Collection Job Group -The **SharePoint** > **0.Collection** Job Group is designed to collect information from SharePoint -farms using the SPAA Data Collector. The collected data is then available to other SharePoint +The **SharePoint** > **0.Collection** Job Group collects information from SharePoint farms using the +SPAA Data Collector. The collected data is then available to other SharePoint Solution sub-job groups and the Access Information Center for analysis. ![0.Collection Job Group](/images/accessanalyzer/11.6/solutions/sharepoint/collection/jobstree.webp) @@ -52,24 +52,24 @@ components: [SharePoint Activity Auditing](#sharepoint-activity-auditing) topic for additional information. - SharePoint Sensitive Data Discovery Auditing (SEEK) – The SharePoint Sensitive Data Discovery Auditing (SEEK) component searches file content for sensitive data. It also collects permission - information; therefore, it does not need to be run with the SPAA component. This component employs + information; therefore, it doesn't need to be run with the SPAA component. This component employs the 1-SPSEEK_SystemScans Job, the 5-SPAA_BulkImport Job, the 4-SPSEEK_BulkImport Job, and the 7-SPAA_Exceptions Job. This component requires an additional installer package before data collection will occur. See the [SharePoint Sensitive Data Discovery Auditing (SEEK)](#sharepoint-sensitive-data-discovery-auditing-seek) topic for additional information. -These jobs are numbered to keep them in the necessary run order. Not all jobs need be run. See the +These jobs are numbered to keep them in the necessary run order. Not all jobs need to run. See the appropriate auditing section for specific job relationships and recommended workflows. The relationship between system scans and bulk import jobs requires the following considerations: -- A system scans job executed from a Enterprise Auditor Console must be followed by the +- A system scans job executed from an Enterprise Auditor Console must be followed by the corresponding bulk import job from the same Enterprise Auditor Console with the same version of Enterprise Auditor - Two system scans processing the same information, for example two **2-SPAA_SystemScans** jobs, - cannot be executed consecutively against the same target host. The corresponding bulk import job, - for example. **5-SPAA_BulkImport**, must be executed in between. + can't be executed consecutively against the same target host. The corresponding bulk import job, + for example, **5-SPAA_BulkImport**, must be executed in between. The system scans job collects the data and creates a Tier-2 database, or SQLite database, on the local host or the host where the SharePoint Agent was installed (according to the scan method @@ -132,14 +132,14 @@ topic for other Runtime Details. **Step 4 –** Run desired corresponding analysis and reporting sub-job groups. -Please see the +see the [Recommended Configuration for the SharePoint Solution](/docs/accessanalyzer/11.6/solutions/sharepoint/recommended.md) topic before continuing with this workflow. :::info Scope the 0.Collection Job Group to only include the collection components desired by disabling the undesired collection jobs. Disabling them allows the solution to run more -efficiently. It is not recommended to delete any jobs. See the +efficiently. It isn't recommended to delete any jobs. See the [Disable or Enable a Job](/docs/accessanalyzer/11.6/admin/jobs/job/disableenable.md) topic for additional information. ::: @@ -154,9 +154,9 @@ and tables specifically incorporated into this component are prefaced with SPAC. [Standard Reference Tables & Views for the SPAA Data Collector](/docs/accessanalyzer/11.6/admin/datacollector/spaa/standardtables.md) topic for additional information on the data collected. -The Access Auditing components must be run in order to create the tables in the database for the -SPAC component to use. Either the SPAA or SEEK Scan job, run to at least a 0-level scan depth (and -the corresponding Bulk Import job) can be used to create these tables. Once an initial 0-level SPAA +The Access Auditing components must be run to create the tables in the database for the +SPAC component to use. Use either the SPAA or SEEK Scan job, run to at least a 0-level scan depth, along +with the corresponding Bulk Import job, to create these tables. After an initial 0-level SPAA or SPSEEK scan job and corresponding Bulk Import have been run against a particular SharePoint On Prem farm or SharePoint Online tenant, SPAA or SPSEEK Scan jobs can be run concurrently with SPAC Scan and Bulk Import jobs as needed. @@ -201,8 +201,8 @@ for additional information. **Step 6 –** Run desired corresponding analysis and reporting sub-job groups. :::note -Once an initial 2-SPAA SystemScans job (scoped to at least 0-level depth) and the -corresponding 5-SPAA Bulk Import job have been run, then the SPAA Scans can be run concurrently with +After an initial 2-SPAA SystemScans job (scoped to at least 0-level depth) and the +corresponding 5-SPAA Bulk Import job have been run, the SPAA Scans can be run concurrently with SPAC Scans and Bulk Import jobs as desired. ::: @@ -210,9 +210,9 @@ SPAC Scans and Bulk Import jobs as desired. Recommended Workflow 2 (for Access, Sensitive Data Discovery & Activity Auditing) :::warning -The jobs must be run in the order shown. It is not possible to disable the +The jobs must be run in the order shown. It isn't possible to disable the 1-SPAA_SystemScan and 2-SPAA_BulkImport jobs and run the 0.Collection Job Group because the -remaining jobs are in the wrong order. Renaming the jobs is not an option. +remaining jobs are in the wrong order. Renaming the jobs isn't an option. ::: @@ -237,8 +237,8 @@ only). **Step 7 –** Run desired corresponding analysis and reporting sub-job groups. :::note -Once an initial 1-SPSEEK SystemScans job (scoped to at least 0-level depth) and the -corresponding 4-SPSEEK Bulk Import job have been run, then the SPSEEK Scans jobs can be run +After an initial 1-SPSEEK SystemScans job (scoped to at least 0-level depth) and the +corresponding 4-SPSEEK Bulk Import job have been run, the SPSEEK Scans jobs can be run concurrently with the SPAC Scans and the Bulk Import jobs as desired. ::: @@ -254,7 +254,7 @@ concurrently with the SPAC Scans and the Bulk Import jobs as desired. **Step 3 –** Run desired corresponding analysis and reporting sub-job groups. :::note -Please see the +see the [Recommended Configuration for the SharePoint Solution](/docs/accessanalyzer/11.6/solutions/sharepoint/recommended.md) topic before continuing with this workflow. ::: @@ -263,7 +263,7 @@ topic before continuing with this workflow. :::info Scope the 0.Collection Job Group to only include the collection components desired by disabling the undesired collection jobs. Disabling them allows the solution to run more -efficiently. It is not recommended to delete any jobs. See the +efficiently. It isn't recommended to delete any jobs. See the [Disable or Enable a Job](/docs/accessanalyzer/11.6/admin/jobs/job/disableenable.md) topic for additional information. ::: @@ -343,9 +343,9 @@ the SharePoint application server when applicable (once only). Recommended Workflow 2 (for Access, Sensitive Data Discovery & Activity Auditing) :::warning -The jobs must be run in the order shown. It is not possible to disable the -2-SPAA_SystemScan and 5-SPAA_BulkImport jobs and run the 0.Collection Job Group because the -remaining jobs are in the wrong order. Renaming the jobs is not an option. +The jobs must be run in the order shown. It isn't possible to disable the +2-SPAA_SystemScans and 5-SPAA_BulkImport jobs and run the 0.Collection Job Group because the +remaining jobs are in the wrong order. Renaming the jobs isn't an option. ::: @@ -369,14 +369,14 @@ remaining jobs are in the wrong order. Renaming the jobs is not an option. **Step 7 –** Run desired corresponding analysis and reporting sub-job groups. :::note -Once an initial 1-SPSEEK SystemScans job (scoped to at least 0-level depth) and the -corresponding 4-SPSEEK Bulk Import job have been run, then the SPSEEK Scans can be run concurrently +After an initial 1-SPSEEK SystemScans job (scoped to at least 0-level depth) and the +corresponding 4-SPSEEK Bulk Import job have been run, the SPSEEK Scans can be run concurrently with the SPAC Scans and the Bulk Import jobs as desired. ::: :::note -Please see the +see the [Recommended Configuration for the SharePoint Solution](/docs/accessanalyzer/11.6/solutions/sharepoint/recommended.md) topic before continuing with this workflow. ::: @@ -385,7 +385,7 @@ topic before continuing with this workflow. :::info Scope the 0.Collection Job Group to only include the collection components desired by disabling the undesired collection jobs. Disabling them allows the solution to run more -efficiently. It is not recommended to delete any jobs. See the +efficiently. It isn't recommended to delete any jobs. See the [Disable or Enable a Job](/docs/accessanalyzer/11.6/admin/jobs/job/disableenable.md) topic for additional information. diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/content/overview.md b/docs/accessanalyzer/11.6/solutions/sharepoint/content/overview.md index 51f08080dc..f685c832af 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/content/overview.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/content/overview.md @@ -6,9 +6,9 @@ sidebar_position: 60 # 4.Content Job Group -This group provides insight into content stored across SharePoint farms in order to help more +This group provides insight into content stored across SharePoint farms to help more efficiently manage that content. It will provide information on the content taking up the most -space, the content that has not been accessed for extended periods of time, and additional data +space, the content that hasn't been accessed in a long time, and additional data describing SharePoint content and the configuration of the repositories such as lists and libraries which store that content. @@ -25,4 +25,4 @@ The 4.Content Job Group is comprised of: – Identifies files that have been modified in at least a year across SharePoint farms. This aids administrators and users in cleaning up or archiving old and unchanged files to help maintain a clean and healthy SharePoint environment. Report includes files, their last modified time, total - file size, versions and version size, along with file owner and file editor information. + file size, versions, and version size, along with file owner and file editor information. diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/content/sp_largestfiles.md b/docs/accessanalyzer/11.6/solutions/sharepoint/content/sp_largestfiles.md index 331bb9f4b2..830be2f144 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/content/sp_largestfiles.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/content/sp_largestfiles.md @@ -17,7 +17,7 @@ Navigate to the **Jobs** > **SharePoint** > **4.Content** > **SP_LargestFiles** and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/content/sp_stalefiles.md b/docs/accessanalyzer/11.6/solutions/sharepoint/content/sp_stalefiles.md index 83ab91209a..71a2573588 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/content/sp_stalefiles.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/content/sp_stalefiles.md @@ -9,12 +9,12 @@ sidebar_position: 20 The SP_StaleFiles Job identifies files that have not been modified in at least a year across SharePoint farms. This aids administrators and users in cleaning up or archiving old and unchanged files to help maintain a clean and healthy SharePoint environment. Report includes files, their last -modified time, total file size, versions and version size, along with file owner and file editor +modified time, total file size, versions, and version size, along with file owner and file editor information. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/11.6/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -24,7 +24,7 @@ The SP_StaleFiles page has the following configurable parameters: - Days since last modification to be considered stale See the -[Customizable Analysis Tasks for the SP_StaleFiles Job](#customizable-analysis-tasks-for-the-sp_stalefiles-job) +[Customizable Analysis Tasks for the SP_StaleFiles Job](#customizable-analysis-tasks-for-the-spstalefiles-job) for additional information. ## Analysis Tasks for the SP_StaleFiles Job @@ -33,7 +33,7 @@ Navigate to the **Jobs** > **SharePoint** > **4.Content** > **SP_StaleFiles** > and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. Only the `@stale` parameter can be configured for the analysis task. ::: @@ -46,7 +46,7 @@ The default analysis task is: node - This analysis task contains a configurable parameter: `@stale`. See the - [Customizable Analysis Tasks for the SP_StaleFiles Job](#customizable-analysis-tasks-for-the-sp_stalefiles-job) + [Customizable Analysis Tasks for the SP_StaleFiles Job](#customizable-analysis-tasks-for-the-spstalefiles-job) topic for additional information. In addition to the table created by the analysis task which displays the stale file resources, the diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/directpermissions/sp_domainusers.md b/docs/accessanalyzer/11.6/solutions/sharepoint/directpermissions/sp_domainusers.md index b4352f6dc2..af86c1c794 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/directpermissions/sp_domainusers.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/directpermissions/sp_domainusers.md @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **SharePoint** > **1.Direct Permissions** > **SP_Doma **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/directpermissions/sp_emptydomaingroupperms.md b/docs/accessanalyzer/11.6/solutions/sharepoint/directpermissions/sp_emptydomaingroupperms.md index 6ce20a5b48..b729f1248f 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/directpermissions/sp_emptydomaingroupperms.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/directpermissions/sp_emptydomaingroupperms.md @@ -17,7 +17,7 @@ Navigate to the **Jobs** > **SharePoint** > **1.Direct Permissions** > tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/directpermissions/sp_highriskpermissions.md b/docs/accessanalyzer/11.6/solutions/sharepoint/directpermissions/sp_highriskpermissions.md index 1d828643fc..12aaa2c878 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/directpermissions/sp_highriskpermissions.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/directpermissions/sp_highriskpermissions.md @@ -7,7 +7,7 @@ sidebar_position: 30 # SP_HighRiskPermissions Job The SP_HighRiskPermissions Job identifies where Authenticated Users, Everyone Except External Users, -Anonymous Logon, or Domain users have been directly assigned permissions +Anonymous Logon, or Domain users have been directly assigned permissions. ## Analysis Tasks for the SP_HighRiskPermissions Job @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **SharePoint** > **1.Direct Permissions** > **SP_High **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/directpermissions/sp_sitecollectionperms.md b/docs/accessanalyzer/11.6/solutions/sharepoint/directpermissions/sp_sitecollectionperms.md index 1934277643..e5521c4dd8 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/directpermissions/sp_sitecollectionperms.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/directpermissions/sp_sitecollectionperms.md @@ -6,8 +6,8 @@ sidebar_position: 40 # SP_SiteCollectionPerms Job -Most content will inherit the permissions configured at the root of the site collection. Having an -understanding of how those permissions are assigned is useful for gaining perspective on the overall +Most content will inherit the permissions configured at the root of the site collection. +Understanding how those permissions are assigned gives useful perspective on the overall SharePoint permission configuration. ## Analysis Tasks for the SP_SiteCollectionPerms Job @@ -16,7 +16,7 @@ Navigate to the **Jobs** > **SharePoint** > **1.Direct Permissions** > **SP_Site **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -41,4 +41,4 @@ report: | Report | Description | Default Tags | Report Elements | | ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Direct Site Collection Permissions | Most content will inherit the permissions configured at the root of the site collection. Having an understanding of how those permissions are assigned is useful for gaining perspective on the overall SharePoint permission configuration. | None | This report is comprised of two elements:
  • Bar Chart – Displays top 5 site collections by direct permissions
  • Table – Provides details on site collections by direct permissions breakdown
| +| Direct Site Collection Permissions | Most content will inherit the permissions configured at the root of the site collection. Understanding how those permissions are assigned gives useful perspective on the overall SharePoint permission configuration. | None | This report is comprised of two elements:
  • Bar Chart – Displays top 5 site collections by direct permissions
  • Table – Provides details on site collections by direct permissions breakdown
| diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/directpermissions/sp_staleusers.md b/docs/accessanalyzer/11.6/solutions/sharepoint/directpermissions/sp_staleusers.md index 083981b849..1fb252c13f 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/directpermissions/sp_staleusers.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/directpermissions/sp_staleusers.md @@ -6,9 +6,8 @@ sidebar_position: 50 # SP_StaleUsers Job -A stale user is defined as either currently disabled within Active Directory, or has not logged onto -the domain for over 90 days. This job will identify locations where there are stale users directly -applied on SharePoint resources. These permissions can be safely removed. +A stale user is disabled in Active Directory or hasn't logged on to the domain in over 90 days. This +job will identify locations where there are stale users directly applied on SharePoint resources. These permissions can be safely removed. ## Analysis Tasks for the SP_StaleUsers Job @@ -16,7 +15,7 @@ Navigate to the **Jobs** > **SharePoint** > **1.Direct Permissions** > **SP_Stal **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -37,4 +36,4 @@ users, the SP_StaleUsers Job produces the following pre-configured report: | Report | Description | Default Tags | Report Elements | | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Stale User Permissions | A stale user is defined as either currently disabled within Active Directory, or has not logged onto the domain for over 90 days. | None | This report is comprised of three elements:
  • Bar Chart – Displays top 5 users by affected resources
  • Table – Provides details on top resource by stale user permissions
  • Table – Provides details on top stale users by affected resources
| +| Stale User Permissions | A stale user is disabled in Active Directory or hasn't logged on to the domain in over 90 days. | None | This report is comprised of three elements:
  • Bar Chart – Displays top 5 users by affected resources
  • Table – Provides details on top resource by stale user permissions
  • Table – Provides details on top stale users by affected resources
| diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/directpermissions/sp_unresolvedsids.md b/docs/accessanalyzer/11.6/solutions/sharepoint/directpermissions/sp_unresolvedsids.md index 2a91fa22d8..6f43005a44 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/directpermissions/sp_unresolvedsids.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/directpermissions/sp_unresolvedsids.md @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **SharePoint** > **1.Direct Permissions** > **SP_Unre **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/effectiveaccessaudits/overview.md b/docs/accessanalyzer/11.6/solutions/sharepoint/effectiveaccessaudits/overview.md index e737c7b0b3..67264f4249 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/effectiveaccessaudits/overview.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/effectiveaccessaudits/overview.md @@ -14,10 +14,9 @@ SharePoint environment. The Effective Access Audits Job Group is comprised of: - [Scoping > SP_TrusteeAccess Job](/docs/accessanalyzer/11.6/solutions/sharepoint/effectiveaccessaudits/sp_trusteeaccess.md) - – Scopes a list of users to audit their access across the SharePoint environment. This can also be - accomplished by looking users up in the Access Information Center. However, it is recommended to - use this job in scenarios where a report on multiple users’ effective access at once needs to be - generated. + – Scopes a list of users to audit their access across the SharePoint environment. You can also + accomplish this by looking users up in the Access Information Center. However, use this job when + you want to generate a report on multiple users’ effective access at once. - [SP_TrusteeAudit Job](/docs/accessanalyzer/11.6/solutions/sharepoint/effectiveaccessaudits/sp_trusteeaudit.md) – Provides functionality similar to the Access Information Center by allowing scoped audits of users’ access across the environment diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/effectiveaccessaudits/sp_trusteeaccess.md b/docs/accessanalyzer/11.6/solutions/sharepoint/effectiveaccessaudits/sp_trusteeaccess.md index 338593690f..2fc92d5cea 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/effectiveaccessaudits/sp_trusteeaccess.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/effectiveaccessaudits/sp_trusteeaccess.md @@ -6,15 +6,15 @@ sidebar_position: 10 # Scoping > SP_TrusteeAccess Job -The SP_TrusteeAccess job allows you to scope a list of users to audit their access across the +Use the SP_TrusteeAccess job to scope a list of users and audit their access across the SharePoint environment. You can also accomplish this by looking users up in the Access Information -Center, however you want to utilize this job in scenarios where you want to generate a report on -multiple users’ effective access at once. +Center. However, use this job when you want to generate a report on multiple users’ effective access +at once. :::note Trustees can be specified in the `UserScoping.csv` file for the SP_TrusteeAccess Job. See the -[Configure CSV File for the Query for the SP_TrusteeAccess Job](#configure-csv-file-for-the-query-for-the-sp_trusteeaccess-job) +[Configure CSV File for the Query for the SP_TrusteeAccess Job](#configure-csv-file-for-the-query-for-the-sptrusteeaccess-job) topic for additional information. ::: @@ -32,15 +32,15 @@ The SP_TrusteeAccess Job uses the TextSearch Data Collector for the following qu The default query is: - Scoping – Modifies the CSV in the Job Directory. See the - [Configure CSV File for the Query for the SP_TrusteeAccess Job](#configure-csv-file-for-the-query-for-the-sp_trusteeaccess-job) + [Configure CSV File for the Query for the SP_TrusteeAccess Job](#configure-csv-file-for-the-query-for-the-sptrusteeaccess-job) topic for additional information. ### Configure CSV File for the Query for the SP_TrusteeAccess Job -Follow the steps to specify trustees in the `UserScoping.csv` file. +To specify trustees in the `UserScoping.csv` file: **Step 1 –** Navigate to the **Jobs** > **SharePoint** > **Effective Access Audits** > **Scoping** > -**SP_TrusteeAccess** Job and right-click on the job. Select **Explore Folder** and the job’s +**SP_TrusteeAccess** Job and right-click the job. Select **Explore Folder** and the job’s directory opens. ![UserScoping.csv in the SP_TrusteeAccess Job folder in File Explorer](/images/accessanalyzer/11.6/solutions/sharepoint/effectiveaccessaudits/userscopingfileexplorer.webp) diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/effectiveaccessaudits/sp_trusteeaudit.md b/docs/accessanalyzer/11.6/solutions/sharepoint/effectiveaccessaudits/sp_trusteeaudit.md index 7a9afecb26..391a452be7 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/effectiveaccessaudits/sp_trusteeaudit.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/effectiveaccessaudits/sp_trusteeaudit.md @@ -16,7 +16,7 @@ Navigate to the **Jobs** > **SharePoint** > **Effective Access Audits** > **SP_T **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/m365/overview.md b/docs/accessanalyzer/11.6/solutions/sharepoint/m365/overview.md index f1fc7f1098..3b00934016 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/m365/overview.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/m365/overview.md @@ -7,7 +7,7 @@ sidebar_position: 100 # 8.M365 Job Group The 8.M365 Job Group generates summary and detail reports of SharePoint Activity on the specified -Teams sites. These reports can be used for identifying file, folder, and user related activity +Teams sites. Use these reports to identify file, folder, and user related activity across your SharePoint environment. ![8.M365 Job Group in the Jobs Tree](/images/accessanalyzer/11.6/solutions/sharepoint/m365/jobstree.webp) diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_externalusers.md b/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_externalusers.md index 1912e770e8..8d8e684cae 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_externalusers.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_externalusers.md @@ -15,14 +15,14 @@ Navigate to the **Jobs** > **SharePoint** > **8.M365** > **SP_OneDrives** > **Co select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: ![Analysis Tasks for the SP_ExternalUsers Job](/images/accessanalyzer/11.6/solutions/sharepoint/m365/externalusersanalysis.webp) -The default analysis task is: +The default analysis tasks are: - Analyze External User Activity – Creates the SA_SPAC_SharePointOnlineMostActiveExternalUsersSummary table accessible under the job's Results diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_onedrives.md b/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_onedrives.md index 2764d4ef80..2ed7f169bc 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_onedrives.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_onedrives.md @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **SharePoint** > **8.M365** > **SP_OneDrives** > **Co select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_sharedlinks.md b/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_sharedlinks.md index 2c63641c51..351f09dfea 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_sharedlinks.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_sharedlinks.md @@ -16,7 +16,7 @@ Navigate to the **Jobs** > **SharePoint** > **8.M365** > **SP_SharedLinks** > ** select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_staleteamsites.md b/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_staleteamsites.md index df7c9382ef..2d4d064c62 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_staleteamsites.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_staleteamsites.md @@ -7,11 +7,11 @@ sidebar_position: 40 # SP_StaleTeamSites Job The SP_StaleTeamSites Job identifies Teams that have not had activity for a number of days that can -be set in the analysis (Set as 30 Days by Default). +be set in the analysis (Set at 30 Days by Default). ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/11.6/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -21,12 +21,12 @@ The SP_StaleTeamSites page has the following configurable parameters: - Desired Number of Days Since Last Activity To Determine Staleness See the -[Customizable Analysis Tasks for the SP_StaleTeamSites Job](#customizable-analysis-tasks-for-the-sp_staleteamsites-job) +[Customizable Analysis Tasks for the SP_StaleTeamSites Job](#customizable-analysis-tasks-for-the-spstaleteamsites-job) for additional information. ## Analysis Tasks for the SP_StaleTeamSites Job -Navigate to the **Jobs** > **SharePoint** > **8.M365** > **SP_StaleTeamSites** >**Configure** node +Navigate to the **Jobs** > **SharePoint** > **8.M365** > **SP_StaleTeamSites** > **Configure** node and select **Analysis** to view the analysis tasks. ![Analysis Tasks for the SP_StaleTeamSites Job](/images/accessanalyzer/11.6/solutions/sharepoint/m365/staleteamsitesanalysis.webp) @@ -37,7 +37,7 @@ The default analysis task is: - This task contains a configurable parameter to set the number of days a Team has not had activity for before it's considered stale. See the - [Customizable Analysis Tasks for the SP_StaleTeamSites Job](#customizable-analysis-tasks-for-the-sp_staleteamsites-job) + [Customizable Analysis Tasks for the SP_StaleTeamSites Job](#customizable-analysis-tasks-for-the-spstaleteamsites-job) topic for additional information. In addition to the table created by the analysis task, the SP_StaleTeamSites Job produces the diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_teams.md b/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_teams.md index ab4112eece..9b34c8719b 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_teams.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_teams.md @@ -15,14 +15,14 @@ Navigate to the **Jobs** > **SharePoint** > **8.M365** > **SP_Teams** > **Config select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: ![Analysis Tasks for the SP_Teams Job](/images/accessanalyzer/11.6/solutions/sharepoint/m365/teamsanalysis.webp) -The default analysis task is: +The default analysis tasks are: - Teams Details and Summary – Creates the SA_SP_TeamsSummary table to populate the Teams Activity and Teams Summary reports diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_teamsexternaluseractivity.md b/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_teamsexternaluseractivity.md index a7797cfac5..209d33b729 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_teamsexternaluseractivity.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_teamsexternaluseractivity.md @@ -12,11 +12,11 @@ Teams, including details on the date/time, resource, and operation. ## Analysis Tasks for the SP_TeamsExternalUserActivity Job Navigate to the **Jobs** > **SharePoint** > **8.M365** > -**SP_TeamsExternalUserActivity** >**Configure** node and select **Analysis** to view the analysis +**SP_TeamsExternalUserActivity** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_teamssensitivedata.md b/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_teamssensitivedata.md index 8a0f2a250f..4f9610e890 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_teamssensitivedata.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_teamssensitivedata.md @@ -10,11 +10,11 @@ The SP_TeamsSensitiveData Job analyzes sensitive data activity within Teams Site ## Analysis Tasks for the SP_TeamsSensitiveData Job -Navigate to the **Jobs** > **SharePoint** > **8.M365** > **SP_TeamsSensitiveData** >**Configure** +Navigate to the **Jobs** > **SharePoint** > **8.M365** > **SP_TeamsSensitiveData** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/overview.md b/docs/accessanalyzer/11.6/solutions/sharepoint/overview.md index 410b9486b4..7803cbc06d 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/overview.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/overview.md @@ -46,14 +46,14 @@ topic for additional information. **Sensitive Data Discovery Considerations** The Sensitive Data Discovery Add-On must be installed on the Enterprise Auditor Console server, -which enables Sensitive Data criteria for scans. If running Sensitive Data Discovery (SDD) scans, it -will be necessary to increase the minimum amount of RAM. Each thread requires a minimum of 2 -additional GB of RAM per host. For example, if the job is configured to scan 8 hosts at a time , -then an extra 16 GB of RAM are required (8x2=16). +which enables Sensitive Data criteria for scans. If you run Sensitive Data Discovery (SDD) scans, +increase the minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per +host. For example, if the job is configured to scan 8 hosts at a time, then an extra 16 GB of RAM +are required (8x2=16). :::note The Sensitive Data Discovery Add-on installation package installs the appropriate JDK -(Java) version on the server. The JDK deployed is prepackaged and does not require any +(Java) version on the server. The JDK deployed is prepackaged and doesn't require any configuration; it has been preconfigured to work with Enterprise Auditor and should never be customized through Java. It will not conflict with other JDKs or Java Runtimes in the same environment. @@ -61,15 +61,15 @@ environment. :::tip -Remember, if employing the Enterprise Auditor SharePoint Agent, it is also necessary for the -Sensitive Data Discovery Add-on to be installed on the server where the agent is installed. +If you use the Enterprise Auditor SharePoint Agent, also install the Sensitive Data Discovery +Add-on on the server where the agent is installed. ::: **Location** The SharePoint Solution requires a special Enterprise Auditor license. It can be installed from the -Enterprise Auditor Instant Job Wizard. Once it has been installed into the Jobs tree, navigate to +Enterprise Auditor Instant Job Wizard. After it has been installed into the Jobs tree, navigate to the solution: **Jobs** > **SharePoint**. The 0.Collection Job Group collects the data. The other job groups and the SP_Overview Job run @@ -95,15 +95,15 @@ The following types of auditing can be conducted with the SharePoint Solution: Each type of auditing depends on specific jobs within the 0.Collection Job Group to collect the data and its corresponding analysis/reporting job groups. The Access Auditing components represent the core of the SharePoint Solution. However, the Sensitive Data Discovery Auditing components also -collect the Access Auditing data; therefore it is not necessary to run both sets of collection jobs. +collect the Access Auditing data; therefore it isn't necessary to run both sets of collection jobs. The data collection query options for each type are explained within the 0.Collection Job Group section. Additionally, the corresponding analysis/reporting job groups are listed for each auditing type. -If intending to run two or all auditing types, see each auditing type section within the +If you intend to run two or all auditing types, see each auditing type section within the 0.Collection Job Group section for information on query options and requirements. It is recommended -to first run the 0.Collection Job Group components in the default order for the desired auditing -types to ensure successful data collection, and then to run the desired sub-groups for reports. +to first run the 0.Collection Job Group components in the default order for the auditing types you want +to ensure successful data collection, and then to run the sub-groups you want for reports. See the [Recommended Configuration for the SharePoint Solution](/docs/accessanalyzer/11.6/solutions/sharepoint/recommended.md) @@ -113,7 +113,7 @@ The SharePoint Solution is available with the SharePoint Reports license feature the following job groups and jobs: - [0.Collection Job Group](/docs/accessanalyzer/11.6/solutions/sharepoint/collection/overview.md) - – Designed to collect high level summary information from SharePoint servers. This information is + – Collects high level summary information from SharePoint servers. This information is used to populate the SMP Reports based around the SharePoint and is a requirement for the Access Information Center – SharePoint reports. @@ -130,15 +130,14 @@ the following job groups and jobs: principles such as NT AUTHORITY\Authenticated Users, Everyone, and Everyone Except External Users. This data must be monitored closely because of its exposure. - [3.Broken Inheritance > SP_BrokenInheritance Job](/docs/accessanalyzer/11.6/solutions/sharepoint/sp_brokeninheritance.md) - – Keeping track of directly applied permissions at mass is not realistic, this job is responsible - for performing data analysis and generating SharePoint broken inheritance reports at the site - level. This includes looking at site broken inheritance and the trustees who are assigned to those - sites where inheritance is broken so that you can remove that access in favor of providing access - via group membership. + – Keeping track of directly applied permissions at scale isn't realistic. This job performs data + analysis and generates SharePoint broken inheritance reports at the site level. This includes + looking at site broken inheritance and the trustees assigned to those sites where inheritance is + broken so that you can remove that access in favor of providing access via group membership. - [4.Content Job Group](/docs/accessanalyzer/11.6/solutions/sharepoint/content/overview.md) - – Provides insight into content stored across SharePoint farms in order to help more efficiently + – Provides insight into content stored across SharePoint farms to help more efficiently manage that content. It will provide information on the content taking up the most space, the - content that has not been accessed for extended periods of time, and additional data describing + content that hasn't been accessed in a long time, and additional data describing SharePoint content and the configuration of the repositories such as lists and libraries which store that content. - [5.Probable Owner > SP_ProbableOwner Job](/docs/accessanalyzer/11.6/solutions/sharepoint/sp_probableowner.md) @@ -151,12 +150,12 @@ the following job groups and jobs: - Requires the Data Governance Sensitive Data Discovery Add-on - [7.Activity Job Group](/docs/accessanalyzer/11.6/solutions/sharepoint/activity/overview.md)– - Generates summary and detail reports of SharePoint activity on the specified sites. These reports - can be used for identifying file, folder, and user related activity across your SharePoint + Generates summary and detail reports of SharePoint activity on the specified sites. Use these + reports to identify file, folder, and user related activity across your SharePoint environment. - [8.M365 Job Group](/docs/accessanalyzer/11.6/solutions/sharepoint/m365/overview.md) - – Generates summary and detail reports of SharePoint Activity on the specified Teams sites. These - reports can be used for identifying file, folder, and user related activity across your SharePoint + – Generates summary and detail reports of SharePoint Activity on the specified Teams sites. Use + these reports to identify file, folder, and user related activity across your SharePoint environment. - [Effective Access Audits Job Group](/docs/accessanalyzer/11.6/solutions/sharepoint/effectiveaccessaudits/overview.md) – Returns reports identifying specific trustees’ effective access across the entire SharePoint diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/recommended.md b/docs/accessanalyzer/11.6/solutions/sharepoint/recommended.md index 61e49cebe4..caeadaf80d 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/recommended.md @@ -13,9 +13,9 @@ directly or scheduled. **Dependencies** -- The **.Active Directory Inventory** Job Group needs to be executed prior to running the SharePoint +- The **.Active Directory Inventory** Job Group needs to be executed before running the SharePoint Solution against a SharePoint on-premises environment -- The **.Entra ID Inventory** Job Group needs to be executed prior to running the SharePoint +- The **.Entra ID Inventory** Job Group needs to be executed before running the SharePoint Solution against a SharePoint Online environment - For Agent-based scans, the SharePoint Agent must be installed on the application server (for Access Auditing & Sensitive Data Discovery Auditing only) @@ -24,7 +24,7 @@ directly or scheduled. - The Sensitive Data Discovery Add-on must be installed on the SharePoint application server (for Sensitive Data Discovery Auditing with agent-based scans only) -**Targeted Host(s)** +**Targeted Hosts** For the 0.Collection Job Group: @@ -43,24 +43,24 @@ topic for additional information. **Connection Profile** -The SPAA Data Collector requires a specific set of permissions. See the +The SharePoint Access Auditor (SPAA) Data Collector requires a specific set of permissions. See the [SharePoint Scan Options](/docs/accessanalyzer/11.6/requirements/sharepoint/scanoptions/scanoptions.md) and [SharePoint Support](/docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepoint.md) topics for the necessary permissions for both on-premises and online target environments. Then create a custom Connection Profile containing the appropriate credentials for the targeted -environment. If a single Connection Profile contains both on-premises and online credentials, it is -necessary for the online credentials to be above the on-premises credentialss in the Connection -Profile credentials list. +environment. If a single Connection Profile contains both on-premises and online credentials, the +online credentials must appear above the on-premises credentials in the Connection Profile +credentials list. The Connection Profile should be assigned under the **SharePoint** > **0.Collection** > **Settings** > **Connection** node. It is set to **Use the Default Profile**, as configured at the global settings level. However, since this may not be the Connection Profile with the necessary -permissions for the assigned hosts, select the the **Select one of the following user defined -profiles** option and select the appropriate Connection Profile from the drop-down menu. +permissions for the assigned hosts, select the **Select one of the following user defined +profiles** option and select the appropriate Connection Profile from the dropdown menu. The jobs within the 5.Effective Access Audits Job Group import CSV files from the jobs’ directories -using the TextSearch Data Collector. Therefore, it is necessary to assign a Connection Profile with +using the TextSearch Data Collector. Therefore, assign a Connection Profile with rights on the Enterprise Auditor Console server to access the CSV file saved in the job’s directory. The Connection Profile can be set at either the **Effective Access Audits** > **Settings** > **Connection** node (applies to both jobs) or in the job’s Properties window on the Connection tab. @@ -75,21 +75,21 @@ The jobs in this job group can be scheduled to run as desired. **Run Order** -The 0.Collection Jobs must be run first and in order. RunSystem Scans jobs and then the Bulk Import -jobs according to the desired workflow. The other SharePoint Solution sub-job groups can be run in +The 0.Collection Jobs must be run first and in order. Run System Scans jobs and then the Bulk Import +jobs according to your workflow. The other SharePoint Solution sub-job groups can be run in any order, together or individually, after running the 0.Collection Job Group. It is recommended to run at the sub-job group level. The SP_Overview Job pulls information from both the 0.Collection Job Group and the other sub-job groups, and the report may contain blank sections if only select sub-job groups are run. -The Access Information Center requires the execution of the 2-SPAA_BulkImport Job default analysis -tasks in order for permission/access reports to be accessible. For activity reports, the Access -Information Center requires the execution of both the 2-SPAA Bulk Import Job default analysis tasks -and the 2-SPAC Bulk Import Job default analysis tasks. +The Access Information Center requires the 2-SPAA_BulkImport Job default analysis tasks to run +before permission and access reports become accessible. For activity reports, the Access +Information Center requires both the 2-SPAA Bulk Import Job default analysis tasks and the 2-SPAC +Bulk Import Job default analysis tasks to run. :::info If only conducting one or two types of auditing, scope the solution by disabling -the undesired collection jobs. Disabling them allows the solution to run more efficiently. It is not +the undesired collection jobs. Disabling them allows the solution to run more efficiently. It isn't recommended to delete any jobs. See the [Disable or Enable a Job](/docs/accessanalyzer/11.6/admin/jobs/job/disableenable.md) topic for additional information. @@ -101,7 +101,7 @@ topic for additional information. This solution can be run with the default query configuration. However, the most common customizations include: -- If using agent-based scanning, it is necessary to enable the agent services on the SharePoint +- If using agent-based scanning, enable the agent services on the SharePoint Access Auditor Data Collector Wizard pages: - Agent Settings page, enable agent service scans: @@ -163,7 +163,7 @@ This solution should be run with the default analysis configuration. Most of the are preconfigured. There are a few which are deselected by default, as they are for troubleshooting purposes. -Though the analysis tasks should not be deselected, the following parameters can be modified: +Though the analysis tasks shouldn't be deselected, the following parameters can be modified: - Stale File is defined by default to 365 days diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/sp_brokeninheritance.md b/docs/accessanalyzer/11.6/solutions/sharepoint/sp_brokeninheritance.md index 181eeb637b..7537e7ae5d 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/sp_brokeninheritance.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/sp_brokeninheritance.md @@ -6,11 +6,10 @@ sidebar_position: 50 # 3.Broken Inheritance > SP_BrokenInheritance Job -Keeping track of directly applied permissions at mass is not realistic, the SP_BrokenInheritance job -is responsible for performing data analysis and generating SharePoint broken inheritance reports at -the site level. This includes looking at site broken inheritance and the trustees who are assigned -to those sites where inheritance is broken so that you can remove that access in favor of providing -access via group membership. +Tracking directly applied permissions at scale isn't realistic. The SP_BrokenInheritance job +analyzes data and generates SharePoint broken inheritance reports at the site level, showing site +broken inheritance and the trustees assigned to those sites where inheritance is broken. Use this +report to remove that access and grant access through group membership instead. ![3.Broken Inheritance > SP_BrokenInheritance Job in the Jobs Tree](/images/accessanalyzer/11.6/solutions/sharepoint/brokeninheritancejobstree.webp) @@ -22,7 +21,7 @@ Navigate to the **Jobs** > **SharePoint** > **3.Broken Inheritance** > **SP_Brok **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -45,4 +44,4 @@ inheritance, the SP_BrokenInheritance Job produces the following pre-configured | Report | Description | Default Tags | Report Elements | | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Broken Inheritance | This job is responsible for performing data analysis and generating SharePoint direct permission reports at the site level. This includes looking at site broken inheritance and the trustees who are assigned to those sites where inheritance is broken. | None | This report is comprised of two elements:
  • Bar Chart – Displays top 5 site collections by resources with permission changes
  • Table – Provides a site collection summary
  • Table – Provides broken inheritance details
| +| Broken Inheritance | This job analyzes data and generates SharePoint direct permission reports at the site level. It shows site broken inheritance and the trustees assigned to those sites where inheritance is broken. | None | This report is comprised of two elements:
  • Bar Chart – Displays top 5 site collections by resources with permission changes
  • Table – Provides a site collection summary
  • Table – Provides broken inheritance details
| diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/sp_openaccess.md b/docs/accessanalyzer/11.6/solutions/sharepoint/sp_openaccess.md index dd39f7bc77..b7cc2b8f30 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/sp_openaccess.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/sp_openaccess.md @@ -7,17 +7,16 @@ sidebar_position: 40 # 2.High Risk Sites > SP_OpenAccess Job The 2.High Risk Sites Job Group provides insight into any high risk repositories and high risk data -that may exist within the targeted SharePoint environment. High risk data is effectively open to the -entire organization through modification of SharePoint permissions to apply well known security -principals such as NT AUTHORITY\Authenticated Users. The data must be monitored closely because of -its exposure. +that may exist within the targeted SharePoint environment. Modifying SharePoint permissions to apply +broad security principals, such as NT AUTHORITY\Authenticated Users, can leave high risk data +effectively open to the entire organization. Monitor this data closely because of its exposure. ![2.High Risk Sites > SP_OpenAccess Job in the Jobs Tree](/images/accessanalyzer/11.6/solutions/sharepoint/openaccessjobstree.webp) The job group is comprised of the SP_OpenAccess Job. Minimizing your attack surface is the goal. Open site collections can potentially provide access to privileged data, greatly increasing your -vulnerability. The SP_OpenAccess Job will identify places in the environment where data is able to -be accessed by a very large amount of employees. +vulnerability. The SP_OpenAccess Job identifies places in the environment where a large number of +employees can access data. It is dependent on data collected by the [SharePoint Access Auditing](/docs/accessanalyzer/11.6/solutions/sharepoint/collection/overview.md#sharepoint-access-auditing) @@ -32,7 +31,7 @@ Navigate to the **Jobs** > **SharePoint** > **2.High Risk Sites** > **SP_OpenAcc **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/sp_overview.md b/docs/accessanalyzer/11.6/solutions/sharepoint/sp_overview.md index 10a3f0f314..367d69a612 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/sp_overview.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/sp_overview.md @@ -6,9 +6,8 @@ sidebar_position: 120 # SP_Overview Job -The SP_Overview job provides an overview of the SharePoint Environment, providing a high level view -into what makes up a SharePoint Environment and the types of security risks and toxic permissions -found during scans. +The SP_Overview job provides a high-level view of the SharePoint environment, including the types +of security risks and toxic permissions found during scans. ![SP_Overview Job in the Jobs Tree](/images/accessanalyzer/11.6/solutions/sharepoint/overviewjobstree.webp) @@ -19,7 +18,7 @@ and [SharePoint Activity Auditing](/docs/accessanalyzer/11.6/solutions/sharepoint/collection/overview.md#sharepoint-activity-auditing) components of the [0.Collection Job Group](/docs/accessanalyzer/11.6/solutions/sharepoint/collection/overview.md). -It also depends on the running of the sub-job groups within the solution. If only select sub-job +It also depends on running the sub-job groups within the solution. If only select sub-job groups have been run, there will be blank sections of this overview report. ## Analysis Tasks for the SP_Overview Job @@ -28,14 +27,14 @@ Navigate to the **Jobs** > **SharePoint** > **SP_Overview** > **Configure** node **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: ![Analysis Tasks for the SP_Overview Job](/images/accessanalyzer/11.6/solutions/sharepoint/overviewanalysis.webp) -The default analysis tasks is: +The default analysis task is: - Generate Overview – Creates an interim processing table in the database for use by downstream analysis and report generation diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/sp_probableowner.md b/docs/accessanalyzer/11.6/solutions/sharepoint/sp_probableowner.md index a1c84e45f1..bd948cb886 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/sp_probableowner.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/sp_probableowner.md @@ -6,10 +6,10 @@ sidebar_position: 70 # 5.Probable Owner > SP_ProbableOwner Job -The SP_ProbableOwner Job aids in the identification of probable owners for Site Collections and -Sites, which can be used for entitlement reviews. Probably Owner calculation is based on file -ownership, management structure, and file activity. The goal of this report is to help you identify -who most likely owns the SharePoint resource or at least someone who can tell you who does. +The SP_ProbableOwner Job identifies probable owners for Site Collections and Sites, which you can +use for entitlement reviews. Probable Owner calculation is based on file ownership, management +structure, and file activity. The goal of this report is to help you identify who most likely owns +the SharePoint resource or at least someone who can tell you who does. ![5.Probable Owner > SP_ProbableOwner Job in the Jobs Tree](/images/accessanalyzer/11.6/solutions/sharepoint/probableownerjobstree.webp) @@ -21,7 +21,7 @@ Navigate to the **Jobs** > **SharePoint** > **5.Probable Owner** > **SP_ProbableOwner** >**Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/sp_sensitivedata.md b/docs/accessanalyzer/11.6/solutions/sharepoint/sp_sensitivedata.md index 4dfbfc5cba..576b276474 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/sp_sensitivedata.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/sp_sensitivedata.md @@ -6,8 +6,8 @@ sidebar_position: 80 # 6.Sensitive Data > SP_SensitiveData Job -The SP_SensitiveData Job identifies where sensitive data is located inside SharePoint farms. Special -care is paid to access and user activity in these locations. +The SP_SensitiveData Job identifies where sensitive data is located inside SharePoint farms. Monitor +access and user activity in these locations closely. ![6.Sensitve Data > SP_SensitiveData Job in the Jobs Tree](/images/accessanalyzer/11.6/solutions/sharepoint/sensitivedatajobstree.webp) @@ -19,7 +19,7 @@ Navigate to the **Jobs** > **SharePoint** > **6.Sensitive Data** > **SP_Sensitiv **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/unix/overview.md b/docs/accessanalyzer/11.6/solutions/unix/overview.md index 69cb7c0229..c3cdf4411c 100644 --- a/docs/accessanalyzer/11.6/solutions/unix/overview.md +++ b/docs/accessanalyzer/11.6/solutions/unix/overview.md @@ -29,7 +29,7 @@ topic for additional information. **Location** The Unix Solution requires a special Enterprise Auditor license. It can be installed from the -Enterprise Auditor Instant Job Wizard. Once it has been installed into the Jobs tree, navigate to +Enterprise Auditor Instant Job Wizard. After it has been installed into the Jobs tree, navigate to the solution: **Jobs** > **Unix**. ## Job Groups diff --git a/docs/accessanalyzer/11.6/solutions/unix/privilegedaccess/sudoers/ux_sudoers.md b/docs/accessanalyzer/11.6/solutions/unix/privilegedaccess/sudoers/ux_sudoers.md index 56db0346c3..e4a1a15983 100644 --- a/docs/accessanalyzer/11.6/solutions/unix/privilegedaccess/sudoers/ux_sudoers.md +++ b/docs/accessanalyzer/11.6/solutions/unix/privilegedaccess/sudoers/ux_sudoers.md @@ -15,7 +15,7 @@ Navigate to the **Unix** > **2.Privileged Access** > **Sudoers** > **UX_Sudoers* node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/unix/privilegedaccess/ux_criticalfiles.md b/docs/accessanalyzer/11.6/solutions/unix/privilegedaccess/ux_criticalfiles.md index 3ebc2a15eb..493f38d9ca 100644 --- a/docs/accessanalyzer/11.6/solutions/unix/privilegedaccess/ux_criticalfiles.md +++ b/docs/accessanalyzer/11.6/solutions/unix/privilegedaccess/ux_criticalfiles.md @@ -11,7 +11,7 @@ Linux environments such as passwd, shadow, sudoers, hosts.deny, and more. ## Queries for the UX_CriticalFiles Job -The UX_CriticalFIles job uses the Unix Data Collector for the following query: +The UX_CriticalFiles job uses the Unix Data Collector for the following query: :::warning The query is preconfigured for this job. Never modify the query. @@ -30,7 +30,7 @@ Navigate to the **Unix** > **2.Privileged Access** > **UX_CriticalFiles** > **Co select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/unix/recommended.md b/docs/accessanalyzer/11.6/solutions/unix/recommended.md index 165943d1c0..3d76ecafba 100644 --- a/docs/accessanalyzer/11.6/solutions/unix/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/unix/recommended.md @@ -6,15 +6,15 @@ sidebar_position: 10 # Recommended Configurations for the Unix Job Group -The Unix job group has been configured by default to run with the default settings. It can be run -directly or scheduled. +The Unix job group is configured to run with the default settings. It can be run directly or +scheduled. **Dependencies** If applicable, the **.NIS Inventory** job group can be run to enable reporting on users and groups from NIS environments. -**Target Host(s)** +**Target Hosts** All Unix Servers. Create a custom host list in Host Management that contains all Unix servers that are in scope to be auditing with the Unix solution. @@ -37,12 +37,12 @@ Schedule the Unix Solution or individual job groups to run as desired. **History Retention** -This is not supported in this job group and should be turned off. +This isn't supported in this job group and should be turned off. **Run at the Job Group Level** -It is a common practice to run the job in the **1.Users and Groups** job group by running the entire -job group, instead of the individual jobs. +It's common practice to run the entire **1.Users and Groups** job group instead of running the +individual jobs. **Query Configuration** diff --git a/docs/accessanalyzer/11.6/solutions/unix/sharing/collection/overview.md b/docs/accessanalyzer/11.6/solutions/unix/sharing/collection/overview.md index 895491928e..176a67e0a1 100644 --- a/docs/accessanalyzer/11.6/solutions/unix/sharing/collection/overview.md +++ b/docs/accessanalyzer/11.6/solutions/unix/sharing/collection/overview.md @@ -16,6 +16,6 @@ The jobs in the 0.Collection job group are: - [UX_NFSConfiguration Job](/docs/accessanalyzer/11.6/solutions/unix/sharing/collection/ux_nfsconfiguration.md) – Collects NFS configuration information which will be further analyzed to identify and categorize risk within audited Unix and Linux environments -- [UX_NFSConfiguration Job](/docs/accessanalyzer/11.6/solutions/unix/sharing/collection/ux_nfsconfiguration.md) +- [UX_SambaConfiguration Job](/docs/accessanalyzer/11.6/solutions/unix/sharing/collection/ux_sambaconfiguration.md) – Collects Samba configuration information which will be further analyzed to identify and categorize risk within audited Unix and Linux environments diff --git a/docs/accessanalyzer/11.6/solutions/unix/sharing/collection/ux_nfsconfiguration.md b/docs/accessanalyzer/11.6/solutions/unix/sharing/collection/ux_nfsconfiguration.md index 41c79f1ca8..b0914e55b7 100644 --- a/docs/accessanalyzer/11.6/solutions/unix/sharing/collection/ux_nfsconfiguration.md +++ b/docs/accessanalyzer/11.6/solutions/unix/sharing/collection/ux_nfsconfiguration.md @@ -31,7 +31,7 @@ Navigate to the **Unix** > **3.Sharing** > **0.Collection** > **UX_NFSConfigurat **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/unix/sharing/collection/ux_sambaconfiguration.md b/docs/accessanalyzer/11.6/solutions/unix/sharing/collection/ux_sambaconfiguration.md index ef8394a572..53b6aa40cd 100644 --- a/docs/accessanalyzer/11.6/solutions/unix/sharing/collection/ux_sambaconfiguration.md +++ b/docs/accessanalyzer/11.6/solutions/unix/sharing/collection/ux_sambaconfiguration.md @@ -31,7 +31,7 @@ Navigate to the **Unix** > **3.Sharing** > **0.Collection** > **UX_SambaConfigur **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/unix/sharing/ux_nfs.md b/docs/accessanalyzer/11.6/solutions/unix/sharing/ux_nfs.md index f26f1b02fe..1ee345894b 100644 --- a/docs/accessanalyzer/11.6/solutions/unix/sharing/ux_nfs.md +++ b/docs/accessanalyzer/11.6/solutions/unix/sharing/ux_nfs.md @@ -15,7 +15,7 @@ Navigate to the **Unix** > **3.Sharing** > **UX_NFS** > **Configure** node and s to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/unix/sharing/ux_samba.md b/docs/accessanalyzer/11.6/solutions/unix/sharing/ux_samba.md index bfb1e25de0..ef0ccd1f0d 100644 --- a/docs/accessanalyzer/11.6/solutions/unix/sharing/ux_samba.md +++ b/docs/accessanalyzer/11.6/solutions/unix/sharing/ux_samba.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **Unix** > **3.Sharing** > **UX_Sam node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -29,7 +29,7 @@ The default analysis tasks are: - Highlights hosts with a large number of risky shares – Creates an interim processing table in the database for use by downstream analysis and report generation -In addition to the tables and views created by the analysis task, the UX_NFS job produces the +In addition to the tables and views created by the analysis task, the UX_Samba job produces the following pre-configured report: | Report | Description | Default Tags | Report Elements | diff --git a/docs/accessanalyzer/11.6/solutions/unix/usersgroups/overview.md b/docs/accessanalyzer/11.6/solutions/unix/usersgroups/overview.md index 7a86f35964..cbefca252c 100644 --- a/docs/accessanalyzer/11.6/solutions/unix/usersgroups/overview.md +++ b/docs/accessanalyzer/11.6/solutions/unix/usersgroups/overview.md @@ -14,7 +14,7 @@ to pinpoint potential areas of administrative concern. The jobs in the 1.Users and Groups job group are: - [0.Collection > UX_UsersAndGroups Job](/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_usersandgroups.md) - – Collects user and group related information from /etc/shadow and their equivalents in order to + – Collects user and group related information from /etc/shadow and their equivalents to provide details on user and group conditions to help pinpoint areas of administrative concerns - [UX_DuplicateGroups Job](/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_duplicategroups.md) – This job identifies duplicate groups within the audited Unix or Linux environment. Duplicate @@ -23,9 +23,9 @@ The jobs in the 1.Users and Groups job group are: – This job identifies empty groups found within the audited Unix or Linux environment. These are suitable candidates for consolidation or cleanup. - [UX_LargeGroups Job](/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_largegroups.md) - – This job identifies groups with large member counts. These types of groups may cause - administrative overhead and burden in being able to easily understand who is getting access to - resources, or how much access is being granted to resources through these groups. + – This job identifies groups with large member counts. Large groups can create administrative + overhead, making it difficult to see who has access to resources or how much access these groups + grant. - [UX_LocalGroups Job](/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_localgroups.md) – This job provides an overview of all local groups within the audited Unix and Linux environments - [UX_LocalUsers Job](/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_localusers.md) diff --git a/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_duplicategroups.md b/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_duplicategroups.md index 66c97b876a..c79adb7e0b 100644 --- a/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_duplicategroups.md +++ b/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_duplicategroups.md @@ -16,7 +16,7 @@ Navigate to the **Unix** > **1.Users and Groups** > **UX_DuplicateGroups** > **C select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_emptygroups.md b/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_emptygroups.md index 0ce1355412..739aadebdb 100644 --- a/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_emptygroups.md +++ b/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_emptygroups.md @@ -15,7 +15,7 @@ Navigate to the **Unix** > **1.Users and Groups** > **UX_EmptyGroups** > **Confi select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_largegroups.md b/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_largegroups.md index 8202f1efd5..ff32e6a4bc 100644 --- a/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_largegroups.md +++ b/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_largegroups.md @@ -6,13 +6,13 @@ sidebar_position: 40 # UX_LargeGroups Job -The UX_LargeGroups job identifies groups with large member counts. These types of groups may cause -administrative overhead and burden in being able to easily understand who is getting access to -resources, or how much access is being granted to resources through these groups. +The UX_LargeGroups job identifies groups with large member counts. Large groups can create +administrative overhead, making it difficult to see who has access to resources or how much access +these groups grant. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/11.6/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -28,7 +28,7 @@ Navigate to the **Unix** > **1.Users and Groups** > **UX_LargeGroups** > **Confi select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_localgroups.md b/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_localgroups.md index 0ece7d31e2..043d721805 100644 --- a/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_localgroups.md +++ b/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_localgroups.md @@ -15,7 +15,7 @@ Navigate to the **Unix** > **1.Users and Groups** > **UX_LocalGroups** > **Confi select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_localusers.md b/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_localusers.md index 94fce9e69e..f88e1a1ba8 100644 --- a/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_localusers.md +++ b/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_localusers.md @@ -15,7 +15,7 @@ Navigate to the **Unix** > **1.Users and Groups** > **UX_LocalUsers** > **Config select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_passwordsettings.md b/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_passwordsettings.md index 6b45a0bd2b..f8919b601c 100644 --- a/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_passwordsettings.md +++ b/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_passwordsettings.md @@ -15,7 +15,7 @@ Navigate to the **Unix** > **1.Users and Groups** > **UX_PasswordSettings** > ** select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_usersandgroups.md b/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_usersandgroups.md index ca174a61e5..3dd926987b 100644 --- a/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_usersandgroups.md +++ b/docs/accessanalyzer/11.6/solutions/unix/usersgroups/ux_usersandgroups.md @@ -7,7 +7,7 @@ sidebar_position: 10 # 0.Collection > UX_UsersAndGroups Job The UX_UsersAndGroups job collects user and group information from /etc/passwd, /etc/shadow, and -their equivalents in order to provide details on user and group conditions to help pinpoint +their equivalents to provide details on user and group conditions to help pinpoint potential areas of administrative concern. ![0.Collection > UX_UsersAndGroups Job in the Jobs Tree](/images/accessanalyzer/11.6/solutions/unix/usersgroups/collectionjobstree.webp) @@ -16,7 +16,7 @@ The UX_UsersAndGroups job is located in the 0.Collection job group. ## Queries for the UX_UsersAndGroups Job -The UX_UsersandGroups job uses the Unix Data Collector for the following queries: +The UX_UsersAndGroups job uses the Unix Data Collector for the following queries: :::warning The queries are preconfigured for this job. Never modify the queries. @@ -44,7 +44,7 @@ Navigate to the **Unix** > **1.Users and Groups** > **0.Collection** > **UX_User **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/windows/applications/sg_installedapplications.md b/docs/accessanalyzer/11.6/solutions/windows/applications/sg_installedapplications.md index 09d816de26..fef61736f8 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/applications/sg_installedapplications.md +++ b/docs/accessanalyzer/11.6/solutions/windows/applications/sg_installedapplications.md @@ -19,7 +19,7 @@ The query is preconfigured for this job. Never modify the query. ![Queries for the SG_InstalledApplications Job](/images/accessanalyzer/11.6/solutions/windows/applications/installedapplicationsquery.webp) -The query for the SG_InstalledApplications job are: +The query for the SG_InstalledApplications job is: - Installed Applications – Targets all Windows servers known to Enterprise Auditor to determine installed applications @@ -30,7 +30,7 @@ Navigate to the **Windows** > **Applications** > **SG_InstalledApplications** > and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/windows/applications/sg_runatboot.md b/docs/accessanalyzer/11.6/solutions/windows/applications/sg_runatboot.md index c851f854f5..24a31e3b77 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/applications/sg_runatboot.md +++ b/docs/accessanalyzer/11.6/solutions/windows/applications/sg_runatboot.md @@ -32,7 +32,7 @@ Navigate to the **Windows** > **Applications** > **SG_RunAtBoot** > **Configure* **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/windows/applications/sg_scheduledtasks.md b/docs/accessanalyzer/11.6/solutions/windows/applications/sg_scheduledtasks.md index 2ceee29617..874aed6a7e 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/applications/sg_scheduledtasks.md +++ b/docs/accessanalyzer/11.6/solutions/windows/applications/sg_scheduledtasks.md @@ -30,7 +30,7 @@ Navigate to the **Windows** > **Applications** > **SG_ScheduledTasks** > **Confi select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/windows/authentication/overview.md b/docs/accessanalyzer/11.6/solutions/windows/authentication/overview.md index edf9e461f9..883657c646 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/authentication/overview.md +++ b/docs/accessanalyzer/11.6/solutions/windows/authentication/overview.md @@ -14,17 +14,17 @@ to help identify potential security vulnerabilities and reduce risk within the e The jobs in the Authentication job group are: - [SG_LSASettings Job](/docs/accessanalyzer/11.6/solutions/windows/authentication/sg_lsasettings.md) - – This job lists LSA settings on all targeted hosts. In particular, the RunAsPPL, - RestrictAnonymous, and ValidateKdcPacSignature keys are examined. If these keys are not set to 1, + – This job lists LSA settings on all targeted hosts. In particular, the job examines the + RunAsPPL, RestrictAnonymous, and ValidateKdcPacSignature keys. If these keys aren't set to 1, a host is vulnerable to mimikatz and other exploitation tools. See the Microsoft [Configuring Additional LSA Protection](https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn408187(v=ws.11)) - article for additional ininformation. + article for additional information. - [SG_SecuritySupportProviders Job](/docs/accessanalyzer/11.6/solutions/windows/authentication/sg_securitysupportproviders.md) - – This job identifies security support providers on all targeted hosts, highlighting potentially - malicious SSPs + – This job identifies security support providers (SSPs) on all targeted hosts, highlighting + potentially malicious SSPs - [SG_WDigestSettings Job](/docs/accessanalyzer/11.6/solutions/windows/authentication/sg_wdigestsettings.md) – This job lists WDigest settings on all targeted hosts. In particular, the UseLogonCredentials - key is examined. If the KB is not installed, and this key is not set properly for a given host, + key is examined. If the KB isn't installed, and this key isn't set properly for a given host, cleartext passwords will be stored in memory. See the [Microsoft Security Advisory](https://support.microsoft.com/en-us/help/2871997/microsoft-security-advisory-update-to-improve-credentials-protection-a) article for more information. diff --git a/docs/accessanalyzer/11.6/solutions/windows/authentication/sg_lsasettings.md b/docs/accessanalyzer/11.6/solutions/windows/authentication/sg_lsasettings.md index eef0717ac7..a87eeb8a69 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/authentication/sg_lsasettings.md +++ b/docs/accessanalyzer/11.6/solutions/windows/authentication/sg_lsasettings.md @@ -6,8 +6,8 @@ sidebar_position: 20 # SG_LSASettings Job -The SG_LASettings job lists settings on all targeted hosts. In particular, the RunAsPPL, -RestrictAnonymous, and ValidateKdcPacSignature keys are examined. If these keys are not set to 1, a +The SG_LSASettings job lists LSA settings on all targeted hosts. In particular, the job examines +the RunAsPPL, RestrictAnonymous, and ValidateKdcPacSignature keys. If these keys aren't set to 1, a host is vulnerable to mimikatz and other exploitation tools. See the Microsoft [Configuring Additional LSA Protection](https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn408187(v=ws.11)) article for additional information. @@ -34,7 +34,7 @@ Navigate to the **Windows** > **Authentication** > **SG_LSASettings** > **Config select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -62,6 +62,6 @@ following pre-configured reports. | Report | Description | Default Tags | Report Elements | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Additional LSA Protection | This report summarizes RunAsPPL registry settings on targeted hosts. This key governs whether or not additional LSA protection is enabled. See the Microsoft [Configuring Additional LSA Protection](https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn408187(v=ws.11)) article for additional information. | None | This report is comprised of two elements:
  • Pie Chart – Displays additional LSA protection by host
  • Table – Provides additional LSA Protection Details
| -| PAC Validation | This report indicates whether or not PAC Validation is enabled on all targeted hosts. This is governed by the ValidateKdcPacSignature key. Default behavior in the event of this key's absence depends on the Windows version installed. See the Microsoft [Understanding Microsoft Kerberos PAC Validation](https://learn.microsoft.com/en-gb/archive/blogs/openspecification/understanding-microsoft-kerberos-pac-validation) article for additional information. | None | This report is comprised of two elements:
  • Pie Chart – Displays PAC validation status
  • Table – Provides PAC validation details
| -| Restrict Anonymous Access | This report summarizes RestrictAnonymous registry settings on targeted hosts. This key governs whether or not access over anonymous connections is enabled. See the Microsoft [Restrict Anonymous check](https://learn.microsoft.com/en-us/previous-versions/tn-archive/bb418944(v=technet.10)) article for additional information. | None | This report is comprised of two elements:
  • Pie Chart – Displays anonymous access by host
  • Table – Provides anonymous access details
| +| Additional LSA Protection | This report summarizes RunAsPPL registry settings on targeted hosts. This key governs whether additional LSA protection is enabled. See the Microsoft [Configuring Additional LSA Protection](https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn408187(v=ws.11)) article for additional information. | None | This report is comprised of two elements:
  • Pie Chart – Displays additional LSA protection by host
  • Table – Provides additional LSA Protection Details
| +| PAC Validation | This report indicates whether PAC Validation is enabled on all targeted hosts. This is governed by the ValidateKdcPacSignature key. Default behavior if this key is absent depends on the Windows version installed. See the Microsoft [Understanding Microsoft Kerberos PAC Validation](https://learn.microsoft.com/en-gb/archive/blogs/openspecification/understanding-microsoft-kerberos-pac-validation) article for additional information. | None | This report is comprised of two elements:
  • Pie Chart – Displays PAC validation status
  • Table – Provides PAC validation details
| +| Restrict Anonymous Access | This report summarizes RestrictAnonymous registry settings on targeted hosts. This key governs whether access over anonymous connections is enabled. See the Microsoft [Restrict Anonymous check](https://learn.microsoft.com/en-us/previous-versions/tn-archive/bb418944(v=technet.10)) article for additional information. | None | This report is comprised of two elements:
  • Pie Chart – Displays anonymous access by host
  • Table – Provides anonymous access details
| diff --git a/docs/accessanalyzer/11.6/solutions/windows/authentication/sg_securitysupportproviders.md b/docs/accessanalyzer/11.6/solutions/windows/authentication/sg_securitysupportproviders.md index 1c478940c9..827c23e3d9 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/authentication/sg_securitysupportproviders.md +++ b/docs/accessanalyzer/11.6/solutions/windows/authentication/sg_securitysupportproviders.md @@ -6,8 +6,8 @@ sidebar_position: 40 # SG_SecuritySupportProviders Job -The SG_SecuritySupportProviders job identifies security support providers on all targeted hosts, -highlighting potentially malicious SSPs. +The SG_SecuritySupportProviders job identifies security support providers (SSPs) on all targeted +hosts, highlighting potentially malicious SSPs. ## Queries for the SG_SecuritySupportProviders Job @@ -31,7 +31,7 @@ Navigate to the **Windows** > **Authentication** > **SG_SecuritySupportProviders node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/windows/authentication/sg_wdigestsettings.md b/docs/accessanalyzer/11.6/solutions/windows/authentication/sg_wdigestsettings.md index 05df3e6b5a..2bb679de04 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/authentication/sg_wdigestsettings.md +++ b/docs/accessanalyzer/11.6/solutions/windows/authentication/sg_wdigestsettings.md @@ -7,7 +7,7 @@ sidebar_position: 30 # SG_WDigestSettings Job The SG_WDigestSettings job lists WDigest settings on all targeted hosts. In particular, the -UseLogonCredentials key is examined. If this key is not set properly for a given host, cleartext +UseLogonCredentials key is examined. If this key isn't set properly for a given host, cleartext passwords will be stored in memory. See the [Microsoft Security Advisory](https://support.microsoft.com/en-us/help/2871997/microsoft-security-advisory-update-to-improve-credentials-protection-a) article for more information. @@ -36,7 +36,7 @@ Navigate to the **Windows** > **Authentication** > **SG_WDigestSettings** > **Co select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/windows/openaccess/recommended.md b/docs/accessanalyzer/11.6/solutions/windows/openaccess/recommended.md index 43a1433e24..17e17c635e 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/openaccess/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/windows/openaccess/recommended.md @@ -16,8 +16,8 @@ All Windows Servers **Connection Profile** -Configure a Connection Profile that is not part of the Domain Admin group. The report should be run -with a non-privileged user account. +Configure a Connection Profile that isn't part of the Domain Admin group. Run the report with a +non-privileged user account. **Schedule Frequency** @@ -25,7 +25,7 @@ This job in this job group should be scheduled to run daily. **Workflow** -**Step 1 –** Configure a Connection Profile that is not part of the Domain Admin group. +**Step 1 –** Configure a Connection Profile that isn't part of the Domain Admin group. **Step 2 –** Assign All Windows Servers under Hosts List Assignment. diff --git a/docs/accessanalyzer/11.6/solutions/windows/openaccess/sg_openfolders.md b/docs/accessanalyzer/11.6/solutions/windows/openaccess/sg_openfolders.md index 86b71032d7..5c260f851f 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/openaccess/sg_openfolders.md +++ b/docs/accessanalyzer/11.6/solutions/windows/openaccess/sg_openfolders.md @@ -27,9 +27,9 @@ The query for the SG_OpenFolders job is: The OpenAccess query has been preconfigured to run with the default settings. However, the subfolder depth can optionally be increased on the Options page in the System Info Data Collector Wizard. -Follow the steps to customize the query. See the +See the [SystemInfo Data Collector](/docs/accessanalyzer/11.6/admin/datacollector/systeminfo/overview.md) -topic for additional information. +topic for additional information. To customize the query: **Step 1 –** Navigate to the **Jobs** > **Windows** > **Open Access** > **SG_OpenFolders** > **Configure** node and select **Queries**. @@ -45,11 +45,11 @@ Wizard opens. **Step 4 –** Navigate to the Options page and select the **Enumerate subfolders within shared folder** checkbox and then the **Limit returned subfolders depth to** checkbox. -**Step 5 –** Select the desired subfolders depth level using the arrows. Click **Next**. +**Step 5 –** Select the subfolder depth level you want using the arrows. Click **Next**. **Step 6 –** On the Summary page, click **Finish** to save the changes. -The subfolders depth is now saved to the configured level. +The subfolder depth is now saved to the configured level. ## Analysis Tasks for the SG_OpenFolders Job @@ -57,7 +57,7 @@ Navigate to the **Windows** > **OpenAccess** > **SG_OpenFolders** > **Configure* **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/windows/overview.md b/docs/accessanalyzer/11.6/solutions/windows/overview.md index 7c2583a8e3..c0feb3e4ea 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/overview.md +++ b/docs/accessanalyzer/11.6/solutions/windows/overview.md @@ -7,8 +7,8 @@ sidebar_position: 160 # Windows Solution The Windows Solution is designed to provide both high-level and granular views into any sized -organization's infrastructure. Systems are a critical business asset. In order to optimally support -and benefit the business, these systems must be running optimally and be fully secured. The Windows +organization's infrastructure. Systems are a critical business asset. To optimally support +and benefit the business, these systems must run optimally and remain fully secured. The Windows Solution allows organizations to quickly inventory, assess, and secure their Windows desktop and server infrastructure from a central location. Key capabilities include privileged account discovery, security configuration and vulnerability assessment, compliance reporting, and asset @@ -30,13 +30,13 @@ topic for additional information. The Windows Solution requires a special Enterprise Auditor license. It can be installed from the Instant Job Wizard. See the [Instant Job Wizard](/docs/accessanalyzer/11.6/admin/jobs/instantjobs/overview.md) -topic for additional information. Once it has been installed in the Jobs tree, navigate to the +topic for additional information. After it has been installed in the Jobs tree, navigate to the solution: **Jobs** > **Windows**. ![Windows Solution in the Jobs Tree](/images/accessanalyzer/11.6/solutions/windows/jobstree.webp) Each job group works independently from the other job groups. All of the job groups have their own -collections that are used to analyze and report on data specific to the groups function. The +collections that are used to analyze and report on data specific to the group's function. The SG_SecurityAssessment job summarizes security related results from the Windows solution. ## Job Groups @@ -64,7 +64,7 @@ The jobs and job groups in the Windows Solution are: - [Security Utilities Job Group](/docs/accessanalyzer/11.6/solutions/windows/securityutilities/overview.md) – This group provides a series of security element checks across the audited environment - [SG_SecurityAssessment Job](/docs/accessanalyzer/11.6/solutions/windows/sg_securityassessment.md) - – This job performs checks against Windows security best practices in order to proactively + – This job performs checks against Windows security best practices to proactively identify critical security configurations that leave the environment vulnerable to attack. The result is a report which provides a listing of findings by severity and category with - corresponding details that can be used to prioritize and remediate security issues. + corresponding details you can use to prioritize and remediate security issues. diff --git a/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/localadministrators/overview.md b/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/localadministrators/overview.md index 07e3f6ab1a..22f3e8f48d 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/localadministrators/overview.md +++ b/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/localadministrators/overview.md @@ -23,5 +23,5 @@ The jobs in the Local Administrators group are: article for additional information. - [SG_Sessions Job](/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/localadministrators/sg_sessions.md) – This job lists sessions and logged on users from all targeted hosts. These active sessions and - logged on users may have their hashes stored in memory on the target machine, which could be - leveraged in a Pass the Hash attack. + logged on users may have their hashes stored in memory on the target machine, which an attacker + could use in a Pass the Hash attack. diff --git a/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/localadministrators/sg_localadmins.md b/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/localadministrators/sg_localadmins.md index 0709d01d66..68dce05a4a 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/localadministrators/sg_localadmins.md +++ b/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/localadministrators/sg_localadmins.md @@ -31,7 +31,7 @@ Navigate to the **Windows** > **Privileged Accounts** > **Local Administrators** **SG_LocalAdmins** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/localadministrators/sg_microsoftlaps.md b/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/localadministrators/sg_microsoftlaps.md index 81738cbbca..c78cad3410 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/localadministrators/sg_microsoftlaps.md +++ b/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/localadministrators/sg_microsoftlaps.md @@ -34,7 +34,7 @@ Navigate to the **Windows** > **Privileged Accounts** > **Local Administrators** **SG_MicrosoftLAPS** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/localadministrators/sg_sessions.md b/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/localadministrators/sg_sessions.md index 0b0706402e..ed563b9b85 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/localadministrators/sg_sessions.md +++ b/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/localadministrators/sg_sessions.md @@ -8,14 +8,14 @@ sidebar_position: 30 The SG_Sessions job lists sessions and logged on users from all targeted hosts. These active sessions and logged on users may have their hashes stored in memory on the target machine, which -could be leveraged in a Pass the Hash attack. +an attacker could use in a Pass the Hash attack. ## Queries for the SG_Sessions Job The SG_Sessions job uses the SystemInfo Data Collector for the following queries: :::warning -The queries) are preconfigured for this job. Never modify the queries. +The queries are preconfigured for this job. Never modify the queries. ::: diff --git a/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/collection/overview.md b/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/collection/overview.md index f0894dc66d..b3cb44c82f 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/collection/overview.md +++ b/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/collection/overview.md @@ -7,17 +7,17 @@ sidebar_position: 10 # Collection Job Group The Collection job group collects group policy settings, local users, and local group membership -information from Windows servers which will be further analyzed to provide insight into privileged -users within the environment. +information from Windows servers, then analyzes this information to provide insight into +privileged users within the environment. ![Collection Job Group in the Jobs Tree](/images/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/collection/collectionjobstree.webp) The jobs in the Collection job group are: - [SG_GroupPolicy Job](/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/collection/sg_grouppolicy.md) - – This job collects policy assignments from all targeted servers. In particular, **Allow log on - locally**, **Log on as a batch job**, **Allow log on through Remote Desktop Services**, and **Log - on as a service** are audited. + – This job collects policy assignments from all targeted servers. In particular, the job audits + **Allow log on locally**, **Log on as a batch job**, **Allow log on through Remote Desktop + Services**, and **Log on as a service**. - [SG_LocalMembership Job](/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/collection/sg_localmembership.md) – This job collects local group membership details from all targeted servers - [SG_LocalUsers Job](/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/collection/sg_localusers.md) diff --git a/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/collection/sg_grouppolicy.md b/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/collection/sg_grouppolicy.md index 741ccad71d..204a4af453 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/collection/sg_grouppolicy.md +++ b/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/collection/sg_grouppolicy.md @@ -6,8 +6,8 @@ sidebar_position: 10 # SG_GroupPolicy Job -The SG_GroupPolicy job collects policy assignments from all targeted servers. The following policy -assignments are audited: +The SG_GroupPolicy job collects policy assignments from all targeted servers. The job audits the +following policy assignments: - Allow log on locally - Log on as a batch job diff --git a/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/collection/sg_localmembership.md b/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/collection/sg_localmembership.md index db86a0f64d..654b92108c 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/collection/sg_localmembership.md +++ b/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/collection/sg_localmembership.md @@ -29,7 +29,7 @@ Navigate to the **Windows** > **Privileged Accounts** > **Logon Rights** > **Col **SG_LocalMembership** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/collection/sg_localusers.md b/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/collection/sg_localusers.md index a8e93e159a..bbfe3ae949 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/collection/sg_localusers.md +++ b/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/collection/sg_localusers.md @@ -29,14 +29,14 @@ Navigate to the **Windows** > **Privileged Accounts** > **Logon Rights** > **Col **SG_LocalUsers** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: ![Analysis Tasks for the SG_LocalUsers Job](/images/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/collection/localusersanalysis.webp) -The default analysis tasks is: +The default analysis task is: - Update LocalUsers – Creates an interim processing table in the database for use by downstream analysis and report generation diff --git a/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/overview.md b/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/overview.md index ea206adbcf..53ecedcfaf 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/overview.md +++ b/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/overview.md @@ -14,8 +14,8 @@ The jobs and job groups in the Logon Rights job group are: - [Collection Job Group](/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/collection/overview.md) – The jobs within this group collect group policy settings, local users, and local group - membership from Windows servers which will be further analyzed to provide insight into privileged - users within the environment + membership from Windows servers, then analyze this information to provide insight into + privileged users within the environment - [SG_AccountPrivileges Job](/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/sg_accountprivileges.md) – This job highlights account privileges across the audited environment, filtering out default privileges present on Windows servers diff --git a/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/sg_accountprivileges.md b/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/sg_accountprivileges.md index b986243c9b..d26b2161b1 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/sg_accountprivileges.md +++ b/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/sg_accountprivileges.md @@ -6,7 +6,7 @@ sidebar_position: 20 # SG_AccountPrivileges Job -The SG_AccountPrivileges job identifies accounts privileges on hosts in the targeted environment. +The SG_AccountPrivileges job identifies account privileges on hosts in the targeted environment. **Targeted Hosts** @@ -33,7 +33,7 @@ Navigate to the **Windows** > **Privileged Accounts** > **Logon Rights** > **SG_AccountPrivileges** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/sg_localpolicies.md b/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/sg_localpolicies.md index b011375432..499015efaf 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/sg_localpolicies.md +++ b/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/logonrights/sg_localpolicies.md @@ -14,7 +14,7 @@ Navigate to the **Windows** > **Privileged Accounts** > **Logon Rights** > **SG_ **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -39,6 +39,6 @@ following pre-configured reports. | Report | Description | Default Tags | Report Elements | | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Local Account Network Access | This report highlights whether or not the **Local accounts** and **Local account and member of Administrators group** principals can be used to access a given host across the network. | None | This report is comprised of two elements:
  • Stacked Bar Chart – Displays a local accounts access enterprise summary
  • Table – Provides local account network access details
| -| Local Security Policies | This report identifies effective local security policy assignments. In particular, **Allow log on locally**, **Log on as a batch job**, **Allow log on through Remote Desktop Services**, and **Log on as a service** are considered. Special attention is paid to policies with a large number of trustee assignments. It displays Largest Policies by Number of Domain User Accounts in a graph format, and Trustee Details in a table format. | GDPR, SOX, HIPAA, PCI-DSS, GLBA, ITAR, FERPA, FISMA, ISO27001 | This report is comprised of three elements:
  • Stacked Bar Chart – Displays largest policies by number of domain user accounts
  • Table – Provides details largest policies by number of domain user accounts
  • Table – Provides trustee details
| +| Local Account Network Access | This report highlights whether the **Local accounts** and **Local account and member of Administrators group** principals can access a given host across the network. | None | This report is comprised of two elements:
  • Stacked Bar Chart – Displays a local accounts access enterprise summary
  • Table – Provides local account network access details
| +| Local Security Policies | This report identifies effective local security policy assignments. In particular, the report considers **Allow log on locally**, **Log on as a batch job**, **Allow log on through Remote Desktop Services**, and **Log on as a service**. Special attention is paid to policies with a large number of trustee assignments. It displays Largest Policies by Number of Domain User Accounts in a graph format, and Trustee Details in a table format. | GDPR, SOX, HIPAA, PCI-DSS, GLBA, ITAR, FERPA, FISMA, ISO27001 | This report is comprised of three elements:
  • Stacked Bar Chart – Displays largest policies by number of domain user accounts
  • Table – Provides details largest policies by number of domain user accounts
  • Table – Provides trustee details
| | Privileged Accounts | This report highlights user accounts with a large number of rights. | None | This report is comprised of two elements:
  • Stacked Bar Chart – Displays top trustees by logon rights
  • Table – Provides details on all trustees
| diff --git a/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/recommended.md b/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/recommended.md index ff4d781aa5..2116421198 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/recommended.md @@ -9,8 +9,8 @@ sidebar_position: 10 **Dependencies** - SG_AccountPrivileges – To populate the Local Administrator column, which is hidden by default, the - SG_LocalAdmins job must be run prior to running this job -- The **Logon Rights** > **Collection** job group must be run prior to running the SG_LocalPolicies + SG_LocalAdmins job must be run before running this job +- The **Logon Rights** > **Collection** job group must be run before running the SG_LocalPolicies job **Targeted Hosts** @@ -20,7 +20,7 @@ All Windows Servers (No DCs) for: - Local Administrator job group - Logon Rights job group -All Window Hosts for: +All Windows Hosts for: - Service Accounts job group @@ -35,11 +35,11 @@ Domain Admin privileges if targeting domain controllers. - Assign the appropriate target host list under Hosts List Assignment for each job group -**Step 2 –** Prerequisite: Ensure that the .Active Directory Inventory job group has successfully -run prior to running this job group. +**Step 2 –** Prerequisite: Ensure that the Active Directory Inventory job group has successfully +run before running this job group. **Step 3 –** Schedule the Privileged Accounts job group or the individual job groups within the -Privleged Accounts job group to run as desired. +Privileged Accounts job group to run as desired. **Step 4 –** Review the reports generated by the jobs. diff --git a/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/sg_serviceaccounts.md b/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/sg_serviceaccounts.md index 5e82f74756..e8479fd6ef 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/sg_serviceaccounts.md +++ b/docs/accessanalyzer/11.6/solutions/windows/privilegedaccounts/sg_serviceaccounts.md @@ -11,7 +11,7 @@ servers, identifying password age and settings. ![Service Accounts > SG_ServiceAccounts Job in the Jobs Tree](/images/accessanalyzer/11.6/solutions/windows/privilegedaccounts/serviceaccountsjobstree.webp) -The SG_ServiceAccounts job is located in the Service Account job group. +The SG_ServiceAccounts job is located in the Service Accounts job group. ## Queries for the SG_ServiceAccounts Job @@ -38,7 +38,7 @@ Navigate to the **Jobs** > **Windows** > **Privileged Accounts** > **Service Acc **SG_ServiceAccounts** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/windows/recommended.md b/docs/accessanalyzer/11.6/solutions/windows/recommended.md index ce0faf0913..286a12c792 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/windows/recommended.md @@ -8,7 +8,7 @@ sidebar_position: 10 **Dependencies** -The .Active Directory Inventory job group needs to be executed prior to running the Windows +The Active Directory Inventory job group needs to be executed before running the Windows Solution. See individual sub-groups and jobs for the dependencies. @@ -33,8 +33,8 @@ otherwise. **Additional Notes** Some jobs in the Windows Job Group use custom SQL scripts to render views on collected data. SQL -views are used to populate report element tables and graphs. Changing or modifying the group, job, -or tables names will result in no data displayed within the reports. +views are used to populate report element tables and graphs. Changing the group, job, +or table names will result in no data displayed within the reports. See the Recommended Configurations topic for each job group for additional information on frequency and job group settings. diff --git a/docs/accessanalyzer/11.6/solutions/windows/securityutilities/openportscan/overview.md b/docs/accessanalyzer/11.6/solutions/windows/securityutilities/openportscan/overview.md index b44fab30e6..31cb549319 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/securityutilities/openportscan/overview.md +++ b/docs/accessanalyzer/11.6/solutions/windows/securityutilities/openportscan/overview.md @@ -6,9 +6,9 @@ sidebar_position: 20 # OpenPortScan Job Group -The OpenPortScan job group reveals all open ports along with the associated executable on the -targeted systems leveraging the jobs within this group. This is accomplished through remotely -executing a netstat command on the target hosts and collecting the results for reporting. +The OpenPortScan job group reveals all open ports and the associated executable on the targeted +systems by remotely executing a netstat command on the target hosts and collecting the results for +reporting. ![OpenPortScan Job Group in the Jobs Tree](/images/accessanalyzer/11.6/solutions/windows/securityutilities/openportscan/openportscanjobstree.webp) @@ -22,6 +22,6 @@ The jobs in the OpenPortScan job group are: - [RemoteOpenPort Job](/docs/accessanalyzer/11.6/solutions/windows/securityutilities/openportscan/remoteopenport.md) – This job remotely executes `netstat -a -b -n` command to gather information about the available - port on the targeted hosts + ports on the targeted hosts - [RetrieveNetstat Job](/docs/accessanalyzer/11.6/solutions/windows/securityutilities/openportscan/retrievenetstat.md) - – This job reveals all open ports along with the associated executable on  targeted systems + – This job reveals all open ports along with the associated executable on targeted systems diff --git a/docs/accessanalyzer/11.6/solutions/windows/securityutilities/openportscan/remoteopenport.md b/docs/accessanalyzer/11.6/solutions/windows/securityutilities/openportscan/remoteopenport.md index 76bf2a87fa..e81a6996fc 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/securityutilities/openportscan/remoteopenport.md +++ b/docs/accessanalyzer/11.6/solutions/windows/securityutilities/openportscan/remoteopenport.md @@ -31,7 +31,7 @@ Navigate to the **Windows** > **Security Utilities** > **OpenPortScan** > **Remo **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/11.6/solutions/windows/securityutilities/openportscan/retrievenetstat.md b/docs/accessanalyzer/11.6/solutions/windows/securityutilities/openportscan/retrievenetstat.md index 9819b68ce6..2e4484f6cd 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/securityutilities/openportscan/retrievenetstat.md +++ b/docs/accessanalyzer/11.6/solutions/windows/securityutilities/openportscan/retrievenetstat.md @@ -11,7 +11,7 @@ systems. ## Queries for the RetrieveNetstat Job -The RetrieveNetstat job is uses the TextSearch Data Collector for the following query: +The RetrieveNetstat job uses the TextSearch Data Collector for the following query: :::warning The query is preconfigured for this job. Never modify the query. @@ -31,7 +31,7 @@ Navigate to the **Windows** > **Security Utilities** > **OpenPortScan** > **Retr **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: @@ -43,9 +43,9 @@ The default analysis tasks are: - **1. NETSTAT Result** – Creates the SA_RetrieveNetstat_NETSTAT table accessible under the job’s Results node -In addition to the tables and views created by the analysis tasks, the EX_DeliveryTimes job produces +In addition to the tables and views created by the analysis tasks, the RetrieveNetstat job produces the following pre-configured report. | Report | Description | Default Tags | Report Elements | | --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------- | -| Network Ports (Open Ports Report) | This job is designed to report on all available ports on the targeted host. It will bring back the results of a `Netstat -b -a`. | None | This report is comprised of one element:
  • Table – Provides details on open ports
| +| Network Ports (Open Ports Report) | This job reports on all available ports on the targeted host, returning the results of a `Netstat -b -a` command. | None | This report is comprised of one element:
  • Table – Provides details on open ports
| diff --git a/docs/accessanalyzer/11.6/solutions/windows/securityutilities/overview.md b/docs/accessanalyzer/11.6/solutions/windows/securityutilities/overview.md index 9a07985b8d..5674810a48 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/securityutilities/overview.md +++ b/docs/accessanalyzer/11.6/solutions/windows/securityutilities/overview.md @@ -6,7 +6,7 @@ sidebar_position: 60 # Security Utilities Job Group -The Security Utilities job group is designed to reveal all open ports along with the associated +The Security Utilities job group reveals all open ports along with the associated executable on the targeted systems. The job remotely executes a netstat command on the target hosts and collects the results for reporting. @@ -15,9 +15,9 @@ and collects the results for reporting. The jobs and job groups in the Security Utilities job group are: - [OpenPortScan Job Group](/docs/accessanalyzer/11.6/solutions/windows/securityutilities/openportscan/overview.md) - – Reveals all open ports along with the associated executable on the targeted systems leveraging - the jobs within this group. This is accomplished through remotely executing a netstat command on - the target hosts and collecting the results for reporting. + – Reveals all open ports along with the associated executable on the targeted systems using + the jobs within this group. It remotely executes a netstat command on + the target hosts and collects the results for reporting. - [SG_PowerShellCommands Job](/docs/accessanalyzer/11.6/solutions/windows/securityutilities/sg_powershellcommands.md) - – This job highlights instances where suspicious PowerShell commands have been found in a host’s + – This job highlights suspicious PowerShell commands found in a host’s PowerShell log diff --git a/docs/accessanalyzer/11.6/solutions/windows/securityutilities/recommended.md b/docs/accessanalyzer/11.6/solutions/windows/securityutilities/recommended.md index 53cdc89888..7401279cf5 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/securityutilities/recommended.md +++ b/docs/accessanalyzer/11.6/solutions/windows/securityutilities/recommended.md @@ -8,12 +8,12 @@ sidebar_position: 10 **Dependencies** -The RemoteOpenPort job must be must be successfully run prior to running the RetrieveNetstat job. +The RemoteOpenPort job must be successfully run before running the RetrieveNetstat job. **Targeted Hosts** - OpenPortScan Job Group – There is no assigned host list for this job group. Configure a host list - with any desired systems to be audited prior to running this job group. Both jobs in the + with any desired systems to be audited before running this job group. Both jobs in the OpenPortScan job group need to be assigned the same target host list. - SG_PowerShellCommands – All Windows Servers (No DCs) @@ -30,7 +30,7 @@ This job group can be scheduled to run as desired. **Step 1 –** Ensure that the configured Connection Profile has local administrator privileges and Domain Admin privileges if targeting domain controllers. -**Step 2 –** Configure target hosts prior to running this job group. +**Step 2 –** Configure target hosts before running this job group. **Step 3 –** Remotely execute a netstat command on the target hosts. diff --git a/docs/accessanalyzer/11.6/solutions/windows/securityutilities/sg_powershellcommands.md b/docs/accessanalyzer/11.6/solutions/windows/securityutilities/sg_powershellcommands.md index e684ac2fd6..044366a4d7 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/securityutilities/sg_powershellcommands.md +++ b/docs/accessanalyzer/11.6/solutions/windows/securityutilities/sg_powershellcommands.md @@ -33,8 +33,8 @@ The queries for the SG_PowerShellCommands job are: ### Configure the Check PowerShell log Query -The Check PowerShell log query has been preconfigured to run with the default settings. However, the -new criteria can optionally be added on the Criteria page in the Smart Log Data Collector Wizard. +The Check PowerShell log query has been preconfigured to run with the default settings. However, you +can add new criteria on the Criteria page in the Smart Log Data Collector Wizard. **Step 1 –** Navigate to the **Jobs** > **Windows** > **Security Utilities** > **SG_PowerShellCommands** > **Configure** node and select **Queries**. Select the **Check PowerShell @@ -53,7 +53,7 @@ is accessible. **Step 5 –** On the Criteria page, click the **press the button to add a new condition** box. -**Step 6 –** Enter the desired conditions. +**Step 6 –** Enter the conditions you want. **Step 7 –** Click **Next** to navigate to the Summary page and click **Finish**. @@ -65,7 +65,7 @@ View the analysis tasks by navigating to the **Windows** > **Security Utilities* **SG_PowerShellCommands** > **Configure** node and selecting **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -79,7 +79,7 @@ The default analysis tasks are: - Summarize PowerShell commands – Creates the SA_PowerShellCommands_HostSummary table accessible under the job’s Results node -The optional analysis tasks is: +The optional analysis task is: - Notify on suspicious commands – Enable this analysis task and the select Analysis Configuration to open the Notification Data Analysis Module Wizard to configure it to send notifications on @@ -87,17 +87,17 @@ The optional analysis tasks is: [Configure the Notify on Suspicious Commands Analysis Task](#configure-the-notify-on-suspicious-commands-analysis-task) topic for additional information. -In addition to the tables and views created by the analysis tasks, the EX_DeliveryTimes job produces +In addition to the tables and views created by the analysis tasks, the SG_PowerShellCommands job produces the following pre-configured report. | Report | Description | Default Tags | Report Elements | | ------------------------------ | ----------------------------------------------------------------------------------------------------------------- | ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Suspicious PowerShell Commands | This report highlights instances where suspicious PowerShell commands have been found in a host's PowerShell log. | None | This report is comprised of three elements:
  • Bar Chart – Displays suspicious commands by host
  • Table – Provides details on suspicious commands by host
  • Table – Provides command details
| +| Suspicious PowerShell Commands | This report highlights suspicious PowerShell commands found in a host's PowerShell log. | None | This report is comprised of three elements:
  • Bar Chart – Displays suspicious commands by host
  • Table – Provides details on suspicious commands by host
  • Table – Provides command details
| ### Configure the Notify on Suspicious Commands Analysis Task -Follow these steps to configure the notification analysis task. +To configure the notification analysis task: **Step 1 –** Navigate to the **Jobs** > **Windows** > **Security Utilities** > **SG_PowerShellCommands** > **Configure** node and select **Analysis**. @@ -107,14 +107,14 @@ task and click **Analysis Configuration**. The Notification Data Analysis Module ![Notification Data Analysis Module wizard SMTP properties page](/images/accessanalyzer/11.6/solutions/windows/securityutilities/powershellcommandsnotifysmtp.webp) -**Step 3 –** Use the **Next** button to navigate to the SMTP page. Do not make changes to the +**Step 3 –** Use the **Next** button to navigate to the SMTP page. Don't make changes to the preceding pages. ![Recipients section](/images/accessanalyzer/11.6/solutions/windows/securityutilities/powershellcommandsnotifyrecipients.webp) **Step 4 –** In the Recipients section, provide the email addresses or distribution lists (fully -qualified address) for those who are to receive this notification. Multiple addresses can be -provided. You can use the following options: +qualified address) for the people who receive this notification. You can provide multiple +addresses. You can use the following options: - Add – Add an email address to the E-mail field - Remove – Remove an email address from the Recipients list @@ -123,16 +123,16 @@ provided. You can use the following options: ![Message section](/images/accessanalyzer/11.6/solutions/windows/securityutilities/powershellcommandsnotifymessage.webp) -**Step 5 –** In the Message section, edit the **Subject**. It is not recommended to remove any +**Step 5 –** In the Message section, edit the **Subject**. Don't remove any parameters. Then, customize the email content in the textbox to provide an explanation of the notification to the recipients. -**Step 6 –** To save these configuration changes, use the **Next** to navigate to the Summary page. -Do not make changes to any other pages. Click **Finish**. The Notification Data Analysis Module +**Step 6 –** To save these configuration changes, use the **Next** button to navigate to the Summary page. +Don't make changes to any other pages. Click **Finish**. The Notification Data Analysis Module window closes. **Step 7 –** This notification analysis task is now configured to send emails. In the Analysis -Selection view, select this task so that notifications can be sent automatically during the -execution of the SG_PowerShellCommands job. +Selection view, select this task so that the SG_PowerShellCommands job sends notifications +automatically when it runs. The Notify on suspicious commands analysis task is now configured to send notifications. diff --git a/docs/accessanalyzer/11.6/solutions/windows/sg_securityassessment.md b/docs/accessanalyzer/11.6/solutions/windows/sg_securityassessment.md index 9fe42c062e..c8d41d1e5b 100644 --- a/docs/accessanalyzer/11.6/solutions/windows/sg_securityassessment.md +++ b/docs/accessanalyzer/11.6/solutions/windows/sg_securityassessment.md @@ -6,10 +6,10 @@ sidebar_position: 70 # SG_SecurityAssessment Job -The SG_SecurityAssessment job performs checks against Windows security best practices in order to +The SG_SecurityAssessment job performs checks against Windows security best practices to proactively identify critical security configurations that leave the environment vulnerable to attack. The result is a report which provides a listing of findings by severity and category with -corresponding details that can be used to prioritize and remediate security issues. +corresponding details you can use to prioritize and remediate security issues. ![SG_SecurityAssessment Job in the Jobs Tree](/images/accessanalyzer/11.6/solutions/windows/securityassessmentjobstree.webp) @@ -64,7 +64,7 @@ Navigate to the **Windows** > **SG_SecurityAssessment** > **Configure** node and to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: @@ -81,4 +81,4 @@ produces the following pre-configured report. | Report | Description | Default Tags | Report Elements | | --------------------------- | ------------------------------------------------------------------------------ | --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Systems Security Assessment | This report summarizes security related results from the Windows solution set. | GDPR, SOX, PCI, HIPAA | This report is comprised of four elements:
  • Pie Chart – Displays a findings by severity
  • Table – Provides scope of audit details
  • Table – Displays details on security assessment results
  • Table – Provides details on findings by category
| +| Systems Security Assessment | This report summarizes security related results from the Windows solution set. | GDPR, SOX, PCI, HIPAA | This report is comprised of four elements:
  • Pie Chart – Displays findings by severity
  • Table – Provides scope of audit details
  • Table – Displays details on security assessment results
  • Table – Provides details on findings by category
| diff --git a/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/computerdetails.md b/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/computerdetails.md index 2996c81406..1e12ebe199 100644 --- a/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/computerdetails.md +++ b/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/computerdetails.md @@ -12,14 +12,14 @@ Use the Computers Details page to select computer attributes to change. Highlight the attribute to edit: -- Insert field – Use the drop-down list to select a field (column) from the source table. Then click +- Insert field – Use the dropdown list to select a field (column) from the source table. Then click the blue arrow to insert the item into the Value box. The executed action replaces the AD Object property with the specified value from the source table. - Add Attribute – Adds a custom attribute to the Computer Details attribute list - Remove Attribute – Removes a selected attribute Computer Details attribute list - Edit Attribute – Click this icon to change the name of the selected custom attribute -- Import Attribute – Opens the Import Custom Attributes Import Wizard where one or more custom - attributes can be imported. See the +- Import Attribute – Opens the Import Custom Attributes Import Wizard, where you can import one or + more custom attributes. See the [Custom Attribute Import Wizard](#custom-attribute-import-wizard) topic for additional information. - Value – This field contains selections from the Insert field. If the Manager attribute is @@ -39,7 +39,7 @@ to use the Custom Attributes Import Wizard. ![Custom Attributes Import Wizard Credentials page](/images/accessanalyzer/12.0/admin/action/activedirectory/operations/credentials.webp) **Step 2 –** On the Credentials page, identify a domain either by entering one manually or selecting -one from the **Domain Name** drop-down menu which displays a list of domains trusted by the one in +one from the **Domain Name** dropdown menu which displays a list of domains trusted by the one in which the Access Analyzer Console server resides. Then set the credentials for reading the attributes list from the domain: @@ -52,11 +52,11 @@ attributes list from the domain: ![Custom Attributes Import Wizard Attributes page](/images/accessanalyzer/12.0/admin/action/activedirectory/operations/attributescomputer.webp) **Step 4 –** The wizard populates available attributes from the domain specified on the Attributes -page. Expand the desired object class and select the checkboxes for the custom attributes to be +page. Expand the object class you want and select the checkboxes for the custom attributes to be imported. Then click **Next**. ![Custom Attributes Import Wizard Completion page](/images/accessanalyzer/12.0/admin/action/activedirectory/operations/completionpage.webp) **Step 5 –** On the Completion page, click **Finish**. -The selected attributes have been added to the attribute list on the Computer Details page. +The wizard adds the selected attributes to the attribute list on the Computer Details page. diff --git a/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/creategroups.md b/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/creategroups.md index 13ec1b3eee..5712c06327 100644 --- a/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/creategroups.md +++ b/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/creategroups.md @@ -12,12 +12,12 @@ Use the Create Groups page to configure the action to create groups on the selec Use the following options to configure the action: -- Insert field – Use the drop-down list to select a field (column) from the source table. Then, +- Insert field – Use the dropdown list to select a field (column) from the source table. Then, click the blue arrow to insert the item into the OU, Group name, or Group name (pre Windows 2000) boxes. - OU – The organizational unit that contains the group - - Create target OU location if it does not already exist – Select this checkbox to create the + - Create target OU location if it doesn't already exist – Select this checkbox to create the target OU - Group Name – The name of the group that being created. This field is required. @@ -27,10 +27,10 @@ Use the following options to configure the action: - Universal - Global - DomainLocal - - SqlField – Enter a value from the drop-down list + - SqlField – Enter a value from the dropdown list - Group type – The type of group being created. Select from the following: - Security - Distribution - - SqlField – Enter a value from the drop-down list + - SqlField – Enter a value from the dropdown list diff --git a/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/createusers.md b/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/createusers.md index 5a170dfdbb..7ec3ed3806 100644 --- a/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/createusers.md +++ b/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/createusers.md @@ -12,11 +12,11 @@ Use the Create Users page to create users on the selected target. Use the following options to configure the action: -- Insert field – Use the drop-down list to select a field (column) from the source table. Then, +- Insert field – Use the dropdown list to select a field (column) from the source table. Then, click the blue arrow to insert the item into the selected box. - OU – The organizational unit in which to create the user - - Create target OU location if it does not already exist - Select this checkbox to create the + - Create target OU location if it doesn't already exist - Select this checkbox to create the target OU. - First Name – The first name of the user being created @@ -31,6 +31,6 @@ Optionally, select from the following checkboxes: - User must change password at next logon – Require the user to change the password at the next logon -- User cannot change password +- User can't change password - Password never expires - Account is disabled diff --git a/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/disableenablecomputers.md b/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/disableenablecomputers.md index 97f9dfb7f6..1e3504c4eb 100644 --- a/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/disableenablecomputers.md +++ b/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/disableenablecomputers.md @@ -11,7 +11,7 @@ options on target computers. ![Active Directory Action Module Wizard Disable/Enable Computers page](/images/accessanalyzer/12.0/admin/action/activedirectory/operations/disableenablecomputers.webp) -Select the radio button for the desired option: +Select the radio button for the option you want: - Enable – Enables users' operation options - Disable – Disables users' operation options diff --git a/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/disableenableusers.md b/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/disableenableusers.md index a0f4b53c81..eb2cb44a7c 100644 --- a/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/disableenableusers.md +++ b/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/disableenableusers.md @@ -10,7 +10,7 @@ Use the Disable/Enable Users page to enable or disable target users. ![Active Directory Action Module Wizard Disable/Enable Users page](/images/accessanalyzer/12.0/admin/action/activedirectory/operations/disableenableusers.webp) -Select the radio button for the desired option: +Select the radio button for the option you want: - Disable – Select this radio button to disable users' operation options - Enable – Select this radio button to enable users' operation options diff --git a/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/groupdetails.md b/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/groupdetails.md index a1ebd6aff8..4a777f8c92 100644 --- a/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/groupdetails.md +++ b/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/groupdetails.md @@ -18,13 +18,13 @@ The options at the bottom of the page vary based on the highlighted attribute. ::: -- Insert field – Use the drop-down list to select a field (column) from the source table. Then, +- Insert field – Use the dropdown list to select a field (column) from the source table. Then, click the blue arrow to insert the item into the Value box. - Add Attribute – Adds a custom attribute to the Computer Details attribute list - Remove Attribute – Removes a selected attribute from the action - Edit Attribute – Click this icon to change the name of the selected custom attribute -- Import Attribute – Opens the Import Custom Attributes Import Wizard where current attributes for - an object is viewed and can be imported for editing. See the +- Import Attribute – Opens the Import Custom Attributes Import Wizard, where you can view and import + current attributes for an object for editing. See the [Custom Attribute Import Wizard](#custom-attribute-import-wizard) topic for additional information. - Value/Name – This field derives its name from selections made on the page. It can contain @@ -45,7 +45,7 @@ to use the Custom Attributes Import Wizard. ![Custom Attributes Import Wizard Credentials page](/images/accessanalyzer/12.0/admin/action/activedirectory/operations/credentials.webp) **Step 2 –** On the Credentials page, identify a domain either by entering one manually or selecting -one from the **Domain Name** drop-down menu which displays a list of domains trusted by the one in +one from the **Domain Name** dropdown menu which displays a list of domains trusted by the one in which the Access Analyzer Console server resides. Then set the credentials for reading the attributes list from the domain: @@ -58,11 +58,11 @@ attributes list from the domain: ![Custom Attributes Import Wizard Attributes page](/images/accessanalyzer/12.0/admin/action/activedirectory/operations/attributesgroup.webp) **Step 4 –** The wizard populates available attributes from the domain specified on the Attributes -page. Expand the desired object class and select the checkboxes for the custom attributes to be +page. Expand the object class you want and select the checkboxes for the custom attributes to be imported. Then click **Next**. ![Custom Attributes Import Wizard Completion page](/images/accessanalyzer/12.0/admin/action/activedirectory/operations/completionpage.webp) **Step 5 –** On the Completion page, click **Finish**. On the Completion page, click **Finish**. -The selected attributes have been added to the attribute list on the Group Details page. +The wizard adds the selected attributes to the attribute list on the Group Details page. diff --git a/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/groupmembership.md b/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/groupmembership.md index 6751f120cd..c3d38d3cad 100644 --- a/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/groupmembership.md +++ b/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/groupmembership.md @@ -6,14 +6,14 @@ sidebar_position: 80 # Group Membership -Use the Groups Membership page to add or remove group members. Values from the source table can also -be used to specify if the object will be added or removed. +Use the Groups Membership page to add or remove group members. You can also use values from the +source table to specify whether the action adds or removes the object. ![Active Directory Action Module Wizard Group Membership page](/images/accessanalyzer/12.0/admin/action/activedirectory/operations/groupmembership.webp) Use the following options to configure the action: -- Insert field – Use the drop-down list to select a field (column) from the source table. Then, +- Insert field – Use the dropdown list to select a field (column) from the source table. Then, click the blue arrow to insert the item into the selected box. - Select one of the following: @@ -22,18 +22,18 @@ Use the following options to configure the action: - OU – The organizational unit that contains the group. This field is required. - - Create target OU location if it does not already exist – Select this checkbox to create the + - Create target OU location if it doesn't already exist – Select this checkbox to create the target OU. - Group (CN, not a pre-Windows 2000 name) – The group to create. This field is required. - - Create target Group if it does not already exist + - Create target Group if it doesn't already exist - Select one of the following: - Add members - Remove members - - Add/Remove members – Enables the ChangeType Column drop down list + - Add/Remove members – Enables the ChangeType Column dropdown list - ChangeType Column – The value to use from the source table to specify if the object is added or removed. The contents of the ChangeType column should be a 0 for Add or a 1 for Remove. diff --git a/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/moveobjects.md b/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/moveobjects.md index 91bd31f911..edf65ad5b0 100644 --- a/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/moveobjects.md +++ b/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/moveobjects.md @@ -13,8 +13,8 @@ Use the Move Objects page to specify the OU in which to move objects. Use the following options to configure the action: - Insert Field – Contains available values from populated from the source table -- OU – Use the drop-down list to select a field (column) from the source table. Then, click the blue +- OU – Use the dropdown list to select a field (column) from the source table. Then, click the blue arrow to insert the item into the OU box. - - Create target OU location if it does not already exist – Select this checkbox to create the + - Create target OU location if it doesn't already exist – Select this checkbox to create the target OU diff --git a/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/operations.md b/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/operations.md index dbb7a607b6..711fba3f05 100644 --- a/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/operations.md +++ b/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/operations.md @@ -11,7 +11,7 @@ Active Directory objects. Some operations have wizard pages to specify the confi ![Active Directory Action Module Wizard Operations page](/images/accessanalyzer/12.0/admin/action/activedirectory/operations.webp) -The Operations drop-down menu contains the following operations: +The Operations dropdown menu contains the following operations: - [Clear/Set SID History ](/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/sidhistory.md) - [Computer Details](/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/computerdetails.md) @@ -28,7 +28,7 @@ The Operations drop-down menu contains the following operations: - [Unlock Users ](#unlock-users) - [Users Details ](/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/usersdetails.md) -Select an operation from the drop-down list and then click **Add**. The selection appears in the +Select an operation from the dropdown list and then click **Add**. The selection appears in the Selections pane as well as the navigation pane if there is an associated configuration page. If performing multiple operations, the action executes the operations in the order in which they appear here. To change the order, select an operation and use the **Down** and **Up** buttons. @@ -36,20 +36,20 @@ here. To change the order, select an operation and use the **Down** and **Up** b ## Delete Objects :::warning -Once deleted, objects from Active Directory cannot be restored. +Once deleted, objects from Active Directory can't be restored. ::: Select this operation to delete objects from Active Directory, such as users, groups, or computers. The source table determines which objects are deleted from the Active Directory. Therefore, this -operation does not possess its own wizard window. +operation doesn't have its own wizard window. ## Groups Remove All Members -Select this operation to remove all members from groups located in the source table. There is not a +Select this operation to remove all members from groups located in the source table. There isn't a wizard window associated with this operation. No configuration is required. ## Unlock Users -Select this operation to unlock the account of the specified users in the source table. There is not +Select this operation to unlock the account of the specified users in the source table. There isn't a wizard window associated with this operation. No configuration is required. diff --git a/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/setresetpassword.md b/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/setresetpassword.md index d05f404fab..408104ddd9 100644 --- a/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/setresetpassword.md +++ b/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/setresetpassword.md @@ -12,7 +12,7 @@ Use the Set/Reset Users Password page to set or reset user passwords with the sp Use the following options to configure the action: -- Insert field – Use the drop-down list to select a field (column) from the source table. Then, +- Insert field – Use the dropdown list to select a field (column) from the source table. Then, click the blue arrow to insert the item into the Password box. - Password – The field with the passwords to set or reset. This field is required. diff --git a/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/sidhistory.md b/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/sidhistory.md index 32f34e201f..a7e7cceea7 100644 --- a/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/sidhistory.md +++ b/docs/accessanalyzer/12.0/admin/action/activedirectory/operations/sidhistory.md @@ -7,7 +7,7 @@ sidebar_position: 10 # Clear/Set SID History Use the Clear/Set SID History page to overwrite or append to the SID history for targeted objects. -Please review the restrictions for this operation in the Notes box. +review the restrictions for this operation in the Notes box. The source table used for this operation must contain a column with the following information: @@ -20,15 +20,15 @@ Configure the action with the following options: - Overwrite – Overwrites the SID History - Append – Adds to the SID History - Clear – Clears the SID History -- Insert Field – This drop-down list is enabled when the Overwrite or Append radio buttons are - selected. Use the drop-down list to select a field (column) from the source table. Then, click the +- Insert Field – This dropdown list is enabled when the Overwrite or Append radio buttons are + selected. Use the dropdown list to select a field (column) from the source table. Then, click the blue arrow to insert the item into the SID History box. The SID history is overwritten with the selected fields or appended to with the selected fields depending on the selected radio button. - SID History – This box is enabled by selecting the Overwrite or Append radio buttons. The SID history is overwritten or appended to with the inserted fields, depending on the selected radio button. Populate the SID History box using either of the following methods: - - Select one or more fields at the Insert Field drop-down menu + - Select one or more fields at the Insert Field dropdown menu - Click the **ellipsis (…)** to access the Select Users or Groups window to populate this field - Reference link – Accesses a Microsoft web page called Using DsAddSidHistory containing important diff --git a/docs/accessanalyzer/12.0/admin/action/activedirectory/options.md b/docs/accessanalyzer/12.0/admin/action/activedirectory/options.md index 1c4930565c..1a94920a3a 100644 --- a/docs/accessanalyzer/12.0/admin/action/activedirectory/options.md +++ b/docs/accessanalyzer/12.0/admin/action/activedirectory/options.md @@ -6,14 +6,13 @@ sidebar_position: 30 # Active Directory Action Options -The Options page provides the option to select to use the default domain or specific a domain to -use. +Use the Options page to select the default domain or specify a domain to use. ![Active Directory Action Module Wizard Options page](/images/accessanalyzer/12.0/admin/action/activedirectory/options.webp) Use the following options to configure the action: -- Insert field – Use the drop-down list to select a field (column) from the source table. Then, +- Insert field – Use the dropdown list to select a field (column) from the source table. Then, click the blue arrow to insert the item into the **Specify domain (controller) to use** box. - Use default domain (controller) – Use the default domain controller for the action - Specify domain (controller) to use – Click the ellipsis to open the Browse for Domain window and diff --git a/docs/accessanalyzer/12.0/admin/action/activedirectory/overview.md b/docs/accessanalyzer/12.0/admin/action/activedirectory/overview.md index 4dd22c7213..70bccb7d26 100644 --- a/docs/accessanalyzer/12.0/admin/action/activedirectory/overview.md +++ b/docs/accessanalyzer/12.0/admin/action/activedirectory/overview.md @@ -11,9 +11,8 @@ Use the Active Directory Action Module to make bulk changes to objects in Micros Analyzer license. :::warning -Be careful when using this action module. Make sure that only the changes required are -applied and only to those target systems desired. Actions perform their functions on all rows in a -table. +Be careful when using this action module. Apply only the required changes, and only to the target +systems you want to change. Actions perform their functions on all rows in a table. ::: @@ -27,11 +26,10 @@ requirements for the type of data contained in the columns in the source table. Active Directory object, group, user, or computer, the source table columns must contain values that uniquely identify each Active Directory object referenced. Active Directory objects correspond to rows in a Access Analyzer source table. Active Directory object attributes correspond to columns. -Once the source table has been scoped, use the Target page to specify the field that identifies the +After scoping the source table, use the Target page to specify the field that identifies the target objects along with the field type to indicate the type of data contained in the field. -The Operations page lists the operations that may be performed by the Active Directory Action -Module. Each operation may have its own source table column requirements as follows: +The Operations page lists the operations that the Active Directory Action Module can perform. Each operation may have its own source table column requirements as follows: | Operation | Requirements | | ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | @@ -39,7 +37,7 @@ Module. Each operation may have its own source table column requirements as foll | Computer Details | No specific columns required | | Disable/Enable Computers | No specific columns required | | Create Groups | No specific columns required | -| Create Users | Column containing the user logon name

**_RECOMMENDED:_** It is recommended that the source table has columns containing the following information:
  • First Name
  • Last name
  • Initials
  • Full name
  • Password
  • OU in which to create the user (This can also be created on the Create Users page)
| +| Create Users | Column containing the user logon name

**_RECOMMENDED:_** Include columns containing the following information in the source table:
  • First Name
  • Last name
  • Initials
  • Full name
  • Password
  • OU in which to create the user (This can also be created on the Create Users page)
| | Delete Objects (Users, Groups, Computers, etc.) | No specific columns required | | Disable/Enable Users | No specific columns required | | Group Details | No specific columns required | @@ -68,6 +66,9 @@ introductory and caution information about the Active Directory Action Module. ![Active Directory Action Module Wizard Welcome page](/images/accessanalyzer/12.0/admin/action/activedirectory/welcome.webp) -The navigation pane contains links to the pages in the wizard. Note that the operations added on the -Operations page will affect the list of pages in the navigation pane. Several operations have +The navigation pane contains links to the pages in the wizard. Several operations have associated configuration pages. + +:::note +Operations added on the Operations page affect the list of pages in the navigation pane. +::: diff --git a/docs/accessanalyzer/12.0/admin/action/activedirectory/summary.md b/docs/accessanalyzer/12.0/admin/action/activedirectory/summary.md index bd7e5c7dc8..3cd4116946 100644 --- a/docs/accessanalyzer/12.0/admin/action/activedirectory/summary.md +++ b/docs/accessanalyzer/12.0/admin/action/activedirectory/summary.md @@ -10,6 +10,6 @@ The Summary page displays a summary of the configured settings for the action. ![Active Directory Action Module Wizard Summary page](/images/accessanalyzer/12.0/admin/action/activedirectory/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Active Directory Action Module Wizard to ensure that no accidental -clicks are saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** to +close the Active Directory Action Module Wizard instead. This prevents the wizard from saving +accidental clicks. diff --git a/docs/accessanalyzer/12.0/admin/action/activedirectory/target.md b/docs/accessanalyzer/12.0/admin/action/activedirectory/target.md index 112f1fcfc0..80d39e2b46 100644 --- a/docs/accessanalyzer/12.0/admin/action/activedirectory/target.md +++ b/docs/accessanalyzer/12.0/admin/action/activedirectory/target.md @@ -18,12 +18,12 @@ Use the following options to configure the action: - Add – Adds the selected field and field type to the Selections pane - Delete – Removes the highlighted operation from the Selection pane - Field – The name of the column in the Access Analyzer source table. Select the field that uniquely - identifies the target AD objects (represented by rows in the Access Analyzer table). The drop-down + identifies the target AD objects (represented by rows in the Access Analyzer table). The dropdown list displays the fields from the source data table specified on the Action Properties page. The - list excludes any default fields such as HOSTSTATUS, on which actions cannot be performed. + list excludes any default fields such as HOSTSTATUS, on which you can't perform actions. - Field Type – The type of data contained in the specified field. Access Analyzer must know the data - type of the field selected above. Otherwise, errors may appear upon execution of the action and - report results may be incomplete. The drop-down list contains the following field types: + type of the selected field. Otherwise, errors may appear when you run the action, and report + results may be incomplete. The dropdown list contains the following field types: - Distinguished Name or DN - GUID @@ -33,7 +33,7 @@ Use the following options to configure the action: - Employee (employeeID) :::note -While one field is usually sufficient to identify AD objects, if specifying multiple -fields, each field type can only be used once. +While one field is usually sufficient to identify AD objects, if you specify multiple +fields, you can use each field type only once. ::: diff --git a/docs/accessanalyzer/12.0/admin/action/filesystem/action.md b/docs/accessanalyzer/12.0/admin/action/filesystem/action.md index b3d2c82e22..5159321643 100644 --- a/docs/accessanalyzer/12.0/admin/action/filesystem/action.md +++ b/docs/accessanalyzer/12.0/admin/action/filesystem/action.md @@ -6,8 +6,8 @@ sidebar_position: 10 # File System Action: Action -On the Action page, select the type of action to be configured, define a new action, and additional -capabilities. +On the Action page, select the type of action to configure, define a new action, and configure +additional capabilities. ![File System Action Module Wizard Action page](/images/accessanalyzer/12.0/admin/action/filesystem/action.webp) @@ -15,10 +15,10 @@ The following options are available: - Define a new action – Enables the Operation page where operations are selected on which the action is based -- Rollback a previously executed action – Enables the Prior Actions page where lists of previously - executed actions and rollback actions can be selected. Not all operations support rollback. Enable - the Support Rollback option prior to execution for the action in order to perform a rollback. +- Rollback a previously executed action – Enables the Prior Actions page, where you can select from + lists of previously executed actions and rollback actions. Not all operations support rollback. Enable + the Support Rollback option before execution for the action to perform a rollback. - Remove the applet service from a host – If an executed action installs an applet service on a host - from a Access Analyzer Console, it remains installed after the action is completed for other - Access Analyzer consoles to perform actions using the same applet service. This setting removes + from a Access Analyzer Console, it remains installed after the action completes, so other + Access Analyzer consoles can use the same applet service to perform actions. This setting removes the action’s applet service from that host. diff --git a/docs/accessanalyzer/12.0/admin/action/filesystem/appletsettings.md b/docs/accessanalyzer/12.0/admin/action/filesystem/appletsettings.md index 9b5a53128a..4a8b194297 100644 --- a/docs/accessanalyzer/12.0/admin/action/filesystem/appletsettings.md +++ b/docs/accessanalyzer/12.0/admin/action/filesystem/appletsettings.md @@ -16,21 +16,21 @@ Specify how the operations will be executed: - Local Access Analyzer server - Specific remote server: - - Fields – Use the drop-down list to select a field (column) from the source table, then click + - Fields – Use the dropdown list to select a field (column) from the source table, then click the blue arrow to insert the item into the **Remote server** field - - Environment Variables – Select an item from the drop-down list, then click the blue arrow to + - Environment Variables – Select an item from the dropdown list, then click the blue arrow to insert the item into the **Remote Server** field - Remote Server – Enter the path to the server - Click the **ellipsis (…)** to browse for server - Click the **tick** icon to show a preview of the path - Click the **Help** icon for additional information -- Preview – Shows what the compound path specified will be resolved in to. The text here is used to - initialize the path specification selection dialog. +- Preview – Shows what the specified compound path resolves to. The text here initializes the path + specification selection dialog. - Specific remote servers – Click the **ellipsis (…)** to browse for servers - Click **Add** to add the server - Click **Remove** to remove the server -- Fall back to the local Access Analyzer server if an applet cannot start – Check to enable this +- Fall back to the local Access Analyzer server if an applet can't start – Check to enable this option diff --git a/docs/accessanalyzer/12.0/admin/action/filesystem/destination.md b/docs/accessanalyzer/12.0/admin/action/filesystem/destination.md index 3410b7fe1a..6e5ff4f87b 100644 --- a/docs/accessanalyzer/12.0/admin/action/filesystem/destination.md +++ b/docs/accessanalyzer/12.0/admin/action/filesystem/destination.md @@ -12,18 +12,18 @@ The Destination page is available only if the following operations are selected: - Move - Rename -Define the destination location of the files that will be copied, moved, or renamed by building the +Define the destination location for the files you want to copy, move, or rename by building the destination path using the Fields and Environment Variables options as needed. ![File System Action Module Wizard Destination page](/images/accessanalyzer/12.0/admin/action/filesystem/destination.webp) -Use the fields provided to select destination items and hosts from the drop-down lists and populate +Use the fields provided to select destination items and hosts from the dropdown lists and populate the Destination field, or edit the field manually. The Preview field updates based on the contents of the Destination field. -- Fields – Use the drop-down list to select a field (column) from the source table, then click the +- Fields – Use the dropdown list to select a field (column) from the source table, then click the blue arrow to insert the item into the **Destination** field -- Environment Variables – Select an item from the drop-down list, then click the blue arrow to +- Environment Variables – Select an item from the dropdown list, then click the blue arrow to insert the item into the **Destination** field - Target Items – Enter the path to the target file or folder @@ -31,11 +31,11 @@ of the Destination field. - Click the **tick** icon to show a preview of the specified path - Click the **Help** icon for additional information -- Host – Select the field that identifies the systems or manually type the host destination +- Host – Select the field that identifies the systems or manually enter the host destination - Use path type – Choose from the following options: - Local – Uses the local path - UNC – Uses the UNC path -- Preview – Shows what the compound path specified will be resolved in to. The text here is used to - initialize the file specification selection dialog. +- Preview – Shows what the specified compound path resolves to. The text here initializes the file + specification selection dialog. diff --git a/docs/accessanalyzer/12.0/admin/action/filesystem/environment.md b/docs/accessanalyzer/12.0/admin/action/filesystem/environment.md index d77506f094..d6f66c5136 100644 --- a/docs/accessanalyzer/12.0/admin/action/filesystem/environment.md +++ b/docs/accessanalyzer/12.0/admin/action/filesystem/environment.md @@ -7,10 +7,10 @@ sidebar_position: 40 # File System Action: Environment The Environment (Environment Variables) page is available only if the selected operation requires -the selection of a sample host. +selecting a sample host. -Use this page to select and connect to a sample host, via which a set of remote environment -variables for use in scoping the action are loaded. Then, on the Target page, use the environment +Use this page to select and connect to a sample host, which loads a set of remote environment +variables for scoping the action. Then, on the Target page, use the environment variables to build dynamic file path locations for the selected operation. :::note diff --git a/docs/accessanalyzer/12.0/admin/action/filesystem/operation.md b/docs/accessanalyzer/12.0/admin/action/filesystem/operation.md index d4a7935eee..1662a58b6d 100644 --- a/docs/accessanalyzer/12.0/admin/action/filesystem/operation.md +++ b/docs/accessanalyzer/12.0/admin/action/filesystem/operation.md @@ -7,11 +7,11 @@ sidebar_position: 20 # File System Action: Operation The Operation page is available when **Define a new action** is selected on the Action page. On the -Operation page, define the action by selecting an operation from the drop-down list. +Operation page, define the action by selecting an operation from the dropdown list. ![File System Action Module Wizard Operation page](/images/accessanalyzer/12.0/admin/action/filesystem/operation.webp) -At the Available Operations drop-down selection list, choose the operation for the action to +At the Available Operations dropdown selection list, choose the operation for the action to perform. The selection determines which pages are available in the wizard. The following operations are available: diff --git a/docs/accessanalyzer/12.0/admin/action/filesystem/options.md b/docs/accessanalyzer/12.0/admin/action/filesystem/options.md index 0a73471726..8c56301244 100644 --- a/docs/accessanalyzer/12.0/admin/action/filesystem/options.md +++ b/docs/accessanalyzer/12.0/admin/action/filesystem/options.md @@ -14,50 +14,48 @@ available. Select from the following additional operations: -- Delete locked files on reboot – Files that are locked can be queued to be deleted at the next - system start up -- Overwrite existing files – Files in the destination location are overwritten. This action cannot +- Delete locked files on reboot – Queues locked files for deletion at the next system startup +- Overwrite existing files – Overwrites files in the destination location. This action can't be undone. -- Terminate associated process – Files that are locked cannot be actively moved, renamed or deleted - without stopping the associated process. If selected, this may cause an interruption to any users - of that target system and service. -- Create shortcuts to the moved files in the source directory – A shortcut will be created in the +- Terminate associated process – You can't move, rename, or delete locked files without stopping + the associated process. If you select this option, it may interrupt users of the target system + and service. +- Create shortcuts to the moved files in the source directory – Creates a shortcut in the source directory that points to the new location of a moved file - Preserve file access – Copy the file ACL from the source directory to the destination to preserve file access. Child objects, with inherited permissions or broken inheritance, targeted by copy or - move actions retain their permissions. Parent folders with inherited permissions are changed to - explicit. -- Enable SACL modification – Request system security access when opening files in order to make SACL + move actions retain their permissions. Parent folders with inherited permissions change to + explicit permissions. +- Enable SACL modification – Request system security access when opening files to make SACL changes - Retry failed rows – Enter the following information: - Number of times to retry - - Do not retry error codes – Rows of data with error codes listed within this textbox are - excluded from the action performed. Common errors are included for certain actions, and may be - customized to add or remove error codes. See the Microsoft + - Don't retry error codes – Excludes rows of data with error codes listed in this textbox from + the action performed. Certain actions include common errors by default, and you can customize + the list to add or remove error codes. See the Microsoft [System Error Codes](https://docs.microsoft.com/en-us/windows/desktop/Debug/system-error-codes) article for additional information. - Delay between retries - Enable batching – (For big data sets) Enabling batching breaks the data set into batches so the - action does not attempt to execute all lines at once. Actions performed on tables with a large - number of input rows may fail due to network failure, and it is difficult to determine the actions - that were executed before the failure. + action doesn't attempt to execute all lines at once. Actions performed on tables with a large + number of input rows may fail due to a network failure, making it difficult to determine which + actions ran before the failure. - Batch size – Specify the batch size. **Start Process** -Select the desired start process. +Select the process you want to start. :::warning -Due to system security limitations, some applications and programs cannot be restarted -or run remotely using this option. Additionally, starting interactive processes (such as Word, -Excel, and so on) will load them into memory, but may not make them available for interaction by the -end user. +Due to system security limitations, this option can't restart or run some applications and programs +remotely. Additionally, starting interactive processes (such as Word or Excel) loads them into +memory but may not make them available to the end user for interaction. ::: -Use the fields provided to select target items and hosts from the drop-down lists and populate the +Use the fields provided to select target items and hosts from the dropdown lists and populate the Set working directory field, or edit the field manually. The Preview field updates based on the contents of the Set working directory field. diff --git a/docs/accessanalyzer/12.0/admin/action/filesystem/overview.md b/docs/accessanalyzer/12.0/admin/action/filesystem/overview.md index ca208a4974..627fe0e0d3 100644 --- a/docs/accessanalyzer/12.0/admin/action/filesystem/overview.md +++ b/docs/accessanalyzer/12.0/admin/action/filesystem/overview.md @@ -6,15 +6,14 @@ sidebar_position: 30 # File System Action Module -The File System Action Module allows Access Analyzer Administrators to automate the process of -remediating and modifying Windows file system attributes and properties. The File System Action +The File System Action Module lets Access Analyzer administrators automate remediating and +modifying Windows file system attributes and properties. The File System Action Module provides options for changing attributes and permissions, as well as copying, deleting, moving, and renaming file system contents. It is available with a special Access Analyzer license. :::warning -Be careful when using this Action Module. Make sure that only the changes required are -applied and only to those target systems desired. Actions perform their functions on all rows in a -table. +Be careful when using this Action Module. Apply only the required changes, and only to the target +systems you want to change. Actions perform their functions on all rows in a table. ::: @@ -24,7 +23,7 @@ its function on a single object per row from the source table defined in the act ## Permissions The File System Action Module requires a Access Analyzer connection profile and privileged access to -file system devices. The Access Analyzer connection profile may be configured to have a Task account +file system devices. You can configure the Access Analyzer connection profile to use a Task account type. The following are the least privileged access model required for Share Permission Changes: - Windows – User credential must be member of Power Users group @@ -50,21 +49,22 @@ type. The following are the least privileged access model required for Share Per ## Applet Deployment -The File System Action Module deploys an applet the first time an action is executed. Applets are -installed within the Access Analyzer Installation Directory if the `%SAInstallDir%` environment is -present. Otherwise, applets are deployed to `C:\Program Files (x86)\STEALTHbits\StealthAUDIT`. +The File System Action Module deploys an applet the first time you run an action. The module +installs applets within the Access Analyzer Installation Directory if the `%SAInstallDir%` +environment variable is present. Otherwise, it deploys applets to +`C:\Program Files (x86)\STEALTHbits\StealthAUDIT`. ## Source Table Configuration Individual action modules, including File System Action Module, may have their own column requirements. To take action on a file system resource, the source table must contain a column with values to uniquely identify it. File System resources correspond to rows in a Access Analyzer table. -File System attributes correspond to columns. Once the source table has been scoped, use the Target +File System attributes correspond to columns. After scoping the source table, use the Target page to specify the field that identifies the target attribute along with any environmental variables. -These columns are required to use the File System Action Module. Otherwise, errors may occur upon -execution of the action and with analysis and reports downstream. +The File System Action Module requires these columns. Otherwise, errors may occur when you run the +action, affecting analysis and reports downstream. | Required Columns | Description | | ---------------- | ---------------------------------------------------------------------------------------------------------------------------- | @@ -72,12 +72,12 @@ execution of the action and with analysis and reports downstream. | RowKey | Identifies each data row as unique. Sometimes the value is a GUID, but the datatype in the table is a varchar (text string). | :::tip -Remember, the individual File System actions may have their own column requirements in addition to -the above. These columns are made available through the File System Action Module wizard. +Remember, individual File System actions may have their own column requirements in addition to the +columns listed here. The File System Action Module wizard makes these columns available. ::: -The Operations page lists the operations that may be performed by the File System Action Module. +The Operations page lists the operations that the File System Action Module can perform. Each operation has its own source table column requirements as follows: | Operation | Column requirements | diff --git a/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/addtags.md b/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/addtags.md index 9abded38d6..31aa827f3a 100644 --- a/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/addtags.md +++ b/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/addtags.md @@ -10,7 +10,7 @@ Use the Parameters page to specify the file tags the action adds. ![File System Action Module Wizard Add Tags Parameters page](/images/accessanalyzer/12.0/admin/action/filesystem/parameters/addtags.webp) -Use the fields provided to select tags from the drop-down lists and populate the Tag field, or edit +Use the fields provided to select tags from the dropdown lists and populate the Tag field, or edit the field manually. The Preview field updates based on the contents of the Tag field. - Add Mode: @@ -19,18 +19,18 @@ the field manually. The Preview field updates based on the contents of the Tag f - Overwrite existing tags - Removes all existing tags before adding newly configured tags :::note -If choosing the option to overwrite tags, the action module will clear out both normal -tags and Boldon James tags and then proceed to apply the tags configured for overwrite. If choosing -the option to remove all tags, the action module will clear out both normal tags and Boldon James +If you choose the option to overwrite tags, the action module clears out both normal +tags and Boldon James tags, then applies the tags configured for overwrite. If you choose +the option to remove all tags, the action module clears out both normal tags and Boldon James tags. ::: -- Fields – Use the drop-down list to select a field (column) from the source table, then click the +- Fields – Use the dropdown list to select a field (column) from the source table, then click the blue arrow to insert the item into the **Tag** field -- Environment Variables – Select an item from the drop-down list, then click the blue arrow to +- Environment Variables – Select an item from the dropdown list, then click the blue arrow to insert the item into the **Tag** field -- Preview – Shows what the compound path specified will be resolved in to +- Preview – Shows what the specified compound path resolves to - Click **Add** to add the tag field to the list - Click **Remove** to remove the tag field from the list @@ -43,8 +43,8 @@ tags. :::note The Boldon James column indicates whether a file tag is a regular tag or a Boldon - James tag. Regular tags will be identified with **0**. Boldon James tags will be identified - with **1**. + James tag. The system identifies regular tags with **0** and Boldon James tags with + **1**. ::: diff --git a/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/changeowner.md b/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/changeowner.md index 203cc100ab..8a80510dbf 100644 --- a/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/changeowner.md +++ b/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/changeowner.md @@ -12,7 +12,7 @@ Use the Change Owner Parameters page to select a trustee to be the new owner. Use the options to enter the trustees: -- Insert field – Use the drop-down list to select a field (column) from the source table, then click +- Insert field – Use the dropdown list to select a field (column) from the source table, then click the blue arrow - Alternatively click **Select** to select a user or group object - Replace owner on all child objects – Check to enable diff --git a/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/changepermissioninheritance.md b/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/changepermissioninheritance.md index c11c5c2b11..a5145550ed 100644 --- a/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/changepermissioninheritance.md +++ b/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/changepermissioninheritance.md @@ -11,4 +11,4 @@ permissions. ![File System Action Module Wizard Change Permissions Inheritance Parameters page](/images/accessanalyzer/12.0/admin/action/filesystem/parameters/changepermissionsinheritance.webp) -Select the desired options for adding or removing inheritance. +Select the options you want for adding or removing inheritance. diff --git a/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/changepermissionsauditing.md b/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/changepermissionsauditing.md index d3a2b312ce..1bdfd9301a 100644 --- a/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/changepermissionsauditing.md +++ b/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/changepermissionsauditing.md @@ -13,7 +13,7 @@ settings the action changes. Use the following options to enter the Permissions: -- Insert field – Use the drop-down list to select a field (column) from the source table, then click +- Insert field – Use the dropdown list to select a field (column) from the source table, then click the blue arrow - Group or user names: @@ -29,7 +29,7 @@ In the table, select from the following options: - Audit – Report the status of the change to the attribute - Audit Apply To - Select the files or folders to report the status on -Select from the following options (Multiple options can be selected): +Select from the following options (you can select multiple options): - Overwrite existing file explicit permissions (target object only) - Replace permission entries on all child objects diff --git a/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/changesharepermissions.md b/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/changesharepermissions.md index 120be8f12f..5ab8f99e9d 100644 --- a/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/changesharepermissions.md +++ b/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/changesharepermissions.md @@ -6,9 +6,9 @@ sidebar_position: 40 # Change Share Permissions -Use the Change Share Permissions Parameters page to specify the permission status for what group or -users are to be changed. +Use the Change Share Permissions Parameters page to specify the permission status to change for the +selected group or users. ![File System Action Module Wizard Change Share Permissions Parameters page](/images/accessanalyzer/12.0/admin/action/filesystem/parameters/changesharepermissions.webp) -Select the desired options for changing the permissions control of the selected group or users. +Select the options you want for changing the permissions control of the selected group or users. diff --git a/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/parameters.md b/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/parameters.md index 0855814df5..563bd1a575 100644 --- a/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/parameters.md +++ b/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/parameters.md @@ -6,9 +6,9 @@ sidebar_position: 60 # File System Action: Parameters -The Parameters page is available for some of the selections on the Operation page. The list of -operations below provides access to the operation-specific versions of the Parameters page for this -wizard. Click on an operation to view its associated Parameters page. +The Parameters page is available for some of the selections on the Operation page. The following +list of operations provides access to the operation-specific versions of the Parameters page for +this wizard. Click an operation to view its associated Parameters page. - [Change Attributes](/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/changeattributes.md) - [Change Permissions and Auditing](/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/changepermissionsauditing.md) @@ -22,5 +22,5 @@ wizard. Click on an operation to view its associated Parameters page. ![File System Action Module Wizard Change File Attributes Parameters page](/images/accessanalyzer/12.0/admin/action/filesystem/changeattributes.webp) -The Navigation pane will list this as the Parameters page, but the title for each version indicates -the type of parameter to be configured. +The Navigation pane lists this as the Parameters page, but each version's title indicates the type +of parameter to configure. diff --git a/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/removefilepermissions.md b/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/removefilepermissions.md index 565ed4419f..747320ee5a 100644 --- a/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/removefilepermissions.md +++ b/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/removefilepermissions.md @@ -13,7 +13,7 @@ removes. Use the options to enter the Permissions: -- Insert field – Use the drop-down list to select a field (column) from the source table, then click +- Insert field – Use the dropdown list to select a field (column) from the source table, then click the blue arrow - Group or user names: - Click **Add** to select a user or group object diff --git a/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/removesharepermissions.md b/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/removesharepermissions.md index 73a8d7be88..9842e2365d 100644 --- a/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/removesharepermissions.md +++ b/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/removesharepermissions.md @@ -13,7 +13,7 @@ removes. Use the options to enter the Permissions: -- Insert field – Use the drop-down list to select a field (column) from the source table, then click +- Insert field – Use the dropdown list to select a field (column) from the source table, then click the blue arrow - Group or user names: diff --git a/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/removetags.md b/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/removetags.md index 43b54e81fe..e1a96d3e08 100644 --- a/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/removetags.md +++ b/docs/accessanalyzer/12.0/admin/action/filesystem/parameters/removetags.md @@ -10,7 +10,7 @@ Use the Parameter page to specify the file tags the action removes. ![File System Action Module Wizard Remove Tags Parameters page](/images/accessanalyzer/12.0/admin/action/filesystem/parameters/removetags.webp) -Use the fields provided to select tags from the drop-down lists and populate the Tag field, or edit +Use the fields provided to select tags from the dropdown lists and populate the Tag field, or edit the field manually. The Preview field updates based on the contents of the Tag field. - Remove Mode: @@ -19,18 +19,18 @@ the field manually. The Preview field updates based on the contents of the Tag f - Remove all tags - Remove all existing tags :::note -If choosing the option to overwrite tags, the action module will clear out both normal -tags and Boldon James tags and then proceed to apply the tags configured for overwrite. If choosing -the option to remove all tags, the action module will clear out both normal tags and Boldon James +If you choose the option to overwrite tags, the action module clears out both normal +tags and Boldon James tags, then applies the tags configured for overwrite. If you choose +the option to remove all tags, the action module clears out both normal tags and Boldon James tags. ::: -- Fields – Use the drop-down list to select a field (column) from the source table, then click the +- Fields – Use the dropdown list to select a field (column) from the source table, then click the blue arrow to insert the item into the **Tag** field -- Environment Variables – Select an item from the drop-down list, then click the blue arrow to +- Environment Variables – Select an item from the dropdown list, then click the blue arrow to insert the item into the **Tag** field -- Preview – Shows what the compound path specified will be resolved in to +- Preview – Shows what the specified compound path resolves to - Click **Add** to add the tag field to the list for removal - Click **Remove** to remove the tag field from the list for removal @@ -43,8 +43,8 @@ tags. :::note The Boldon James column indicates whether a file tag is a regular tag or a Boldon - James tag. Regular tags will be identified with **0**. Boldon James tags will be identified - with **1**. + James tag. The system identifies regular tags with **0** and Boldon James tags with + **1**. ::: diff --git a/docs/accessanalyzer/12.0/admin/action/filesystem/rollback.md b/docs/accessanalyzer/12.0/admin/action/filesystem/rollback.md index 43a9b4c0d2..f8e8366100 100644 --- a/docs/accessanalyzer/12.0/admin/action/filesystem/rollback.md +++ b/docs/accessanalyzer/12.0/admin/action/filesystem/rollback.md @@ -6,7 +6,7 @@ sidebar_position: 80 # File System Action: Rollback -Use the Rollback page to apply rollback support to the action. This option provides the ability to +Use the Rollback page to apply rollback support to the action. This option lets you undo failed actions and reapply the original action settings when the action continues from where it left off. diff --git a/docs/accessanalyzer/12.0/admin/action/filesystem/summary.md b/docs/accessanalyzer/12.0/admin/action/filesystem/summary.md index 81538d8fbe..53ea5e7b15 100644 --- a/docs/accessanalyzer/12.0/admin/action/filesystem/summary.md +++ b/docs/accessanalyzer/12.0/admin/action/filesystem/summary.md @@ -10,6 +10,6 @@ The Summary page displays a summary of the configured action. ![File System Action Module Wizard Summary page](/images/accessanalyzer/12.0/admin/action/filesystem/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the File System Action Module Wizard to ensure that no accidental clicks -are saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** to +close the File System Action Module Wizard instead. This prevents the wizard from saving accidental +clicks. diff --git a/docs/accessanalyzer/12.0/admin/action/filesystem/target.md b/docs/accessanalyzer/12.0/admin/action/filesystem/target.md index b42ed3e0f0..4dbec1b7c4 100644 --- a/docs/accessanalyzer/12.0/admin/action/filesystem/target.md +++ b/docs/accessanalyzer/12.0/admin/action/filesystem/target.md @@ -7,19 +7,19 @@ sidebar_position: 50 # File System Action: Target Use the Target page to point the action module towards a file path on the specified host. -Environmental variables (for example, Program Files, SystemRoot, SAInstallDir, and so on) can be -used when creating a path as well as fields in the raw table output to populate the **Target items** -field. +You can use environmental variables (for example, Program Files, SystemRoot, SAInstallDir, and so +on) when creating a path, as well as fields in the raw table output, to populate the +**Target items** field. ![File System Action Module Wizard Target page](/images/accessanalyzer/12.0/admin/action/filesystem/target.webp) -Use the fields provided to select target items and hosts from the drop-down lists and populate the +Use the fields provided to select target items and hosts from the dropdown lists and populate the Target items field, or edit the field manually. The Preview field updates based on the contents of the Target items field. -- Fields – Use the drop-down list to select a field (column) from the source table, then click the +- Fields – Use the dropdown list to select a field (column) from the source table, then click the blue arrow to insert the item into the **Target items** field -- Environment Variables – Select an item from the drop-down list, then click the blue arrow to +- Environment Variables – Select an item from the dropdown list, then click the blue arrow to insert the item into the Target items field - Target items – Enter the path to the target file or folder @@ -27,12 +27,12 @@ the Target items field. - Click the **tick** icon to show a preview of the specified path - Click the **Help** icon for additional information -- Host – Select the field that identifies the systems or manually type the host to take action +- Host – Select the field that identifies the systems or manually enter the host to take action against - Use path type – Choose from the following options: - Local – Uses the local path - UNC – Uses the UNC path -- Preview – Shows what the compound path specified will be resolved in to. The text here is used to - initialize the file specification selection dialog. +- Preview – Shows what the specified compound path resolves to. The text here initializes the file + specification selection dialog. diff --git a/docs/accessanalyzer/12.0/admin/action/libraries.md b/docs/accessanalyzer/12.0/admin/action/libraries.md index e86f94958b..34eadf979c 100644 --- a/docs/accessanalyzer/12.0/admin/action/libraries.md +++ b/docs/accessanalyzer/12.0/admin/action/libraries.md @@ -6,10 +6,10 @@ sidebar_position: 10 # Action Libraries -When creating a new action on a job, you have the ability to load action tasks that have been -preconfigured with table input, script body, and parameters. This helps you: +When creating a new action on a job, you can load action tasks preconfigured with table input, +script body, and parameters. This helps you: -- Perform operations that are not available in one of the out of the box action modules +- Perform operations that aren't available in one of the built-in action modules - Build custom action workflows to satisfy common use cases - Build custom remediation workflows, such as: @@ -22,15 +22,15 @@ window with the available Action Libraries and operations: ![Libraries window](/images/accessanalyzer/12.0/admin/action/libraries.webp) -When a specific operation within a library is chosen, the action is added in the disabled state to -the job. The Action Properties page opens, which has a description, action module, and source table +When you choose a specific operation within a library, the action module adds the action to the job +in a disabled state. The Action Properties page opens, which has a description, action module, and source table with relevant filters applied. When you click the **Configure Action** link, the action module's wizard opens. ![PowerShell Action Module Wizard](/images/accessanalyzer/12.0/admin/action/powershellmodulewizard.webp) -The following Action Libraries and Templates leverage the PowerShell Action module for running +The following Action Libraries and Templates use the PowerShell Action module for running actions within the specific environment: - Active Directory @@ -39,14 +39,13 @@ actions within the specific environment: - SharePoint Online - Windows -Prerequisite information for each of the PowerShell scripts is included as part of the script -comments. Typically, a script requires necessary cmdlets available and installed, as well as +Each PowerShell script's comments include prerequisite information for that script. Typically, a script requires necessary cmdlets available and installed, as well as parameter inputs configured. ## Create a Custom Action Library -You can also create and maintain custom libraries of action tasks for easy reference and use. Once -you configure an action task as desired, follow the steps to add it to an Action Library. +You can also create and maintain custom libraries of action tasks for easy reference and use. After +you configure an action task, add it to an Action Library: **Step 1 –** From within the Action Selections view where the custom action tasks exists, right-click and copy the task. diff --git a/docs/accessanalyzer/12.0/admin/action/mailbox/affectedmailboxes.md b/docs/accessanalyzer/12.0/admin/action/mailbox/affectedmailboxes.md index 5287dfcf33..b35420db3d 100644 --- a/docs/accessanalyzer/12.0/admin/action/mailbox/affectedmailboxes.md +++ b/docs/accessanalyzer/12.0/admin/action/mailbox/affectedmailboxes.md @@ -20,7 +20,7 @@ Select mailboxes to process using the following options: - Users found in the following column – Select this option to identify users via a data table column - - Use the drop-down menu to select a data table column containing either the Mailbox display + - Use the dropdown menu to select a data table column containing either the Mailbox display name or email address - Select a data type for the selected field using the following options: diff --git a/docs/accessanalyzer/12.0/admin/action/mailbox/delegaterights.md b/docs/accessanalyzer/12.0/admin/action/mailbox/delegaterights.md index 3e8926f9a0..0febb64318 100644 --- a/docs/accessanalyzer/12.0/admin/action/mailbox/delegaterights.md +++ b/docs/accessanalyzer/12.0/admin/action/mailbox/delegaterights.md @@ -6,15 +6,15 @@ sidebar_position: 120 # Mailbox: Delegate Rights -Use the Delegate Rights page to specify folder permissions for the selected delegates. A permission -level can be specified for each folder on the page. It is a wizard page for the Add Delegates +Use the Delegate Rights page to specify folder permissions for the selected delegates. You can +specify a permission level for each folder on the page. It is a wizard page for the Add Delegates operation. ![New Mailbox Action Wizard Delegate Rights page](/images/accessanalyzer/12.0/admin/action/mailbox/delegaterights.webp) Set delegate rights using the following options: -- The following delegate rights can be chosen to access each mailbox folder: +- Choose from the following delegate rights to access each mailbox folder: - None - Reviewer @@ -26,13 +26,13 @@ Set delegate rights using the following options: - Publishing Editor - Owner -- Select a right from the drop-down menu of any desired mailbox folder, including: +- Select a right from the dropdown menu of any desired mailbox folder, including: - Calendar :::note - If Editor or a higher rights level is selected, the **Delegate receives copies of - meeting-related messages sent to me** option is enabled for selection. + If you select Editor or a higher rights level, the wizard enables the **Delegate receives + copies of meeting-related messages sent to me** option for selection. ::: diff --git a/docs/accessanalyzer/12.0/admin/action/mailbox/folderconditions.md b/docs/accessanalyzer/12.0/admin/action/mailbox/folderconditions.md index 9eaedc1921..3359976f40 100644 --- a/docs/accessanalyzer/12.0/admin/action/mailbox/folderconditions.md +++ b/docs/accessanalyzer/12.0/admin/action/mailbox/folderconditions.md @@ -7,7 +7,7 @@ sidebar_position: 60 # Mailbox: Folder Conditions Use the Folder Conditions page to customize folder search filter conditions. It is a wizard page for -the **No, the query results do not contain a mailbox identification** column option on the Folder +the **No, the query results don't contain a mailbox identification** column option on the Folder Identification page. ![New Mailbox Action Wizard Folder Conditions page](/images/accessanalyzer/12.0/admin/action/mailbox/folderconditions.webp) @@ -19,7 +19,7 @@ Customize folder search conditions using the following options: - With specific folder type - With search terms in the folder name - - With specific folder(s) to include/exclude + - With specific folders to include/exclude - Edit conditions – Any selected conditions populate here. To modify filter conditions, click the underlined portion of the condition, which opens a corresponding window. @@ -27,8 +27,8 @@ Customize folder search conditions using the following options: ## Folder Type Window Use the Folder Type window to select which folder types to run the action against. The Folder Type -window opens if **specific** in **with specific folder type** is selected in the Edit Conditions -box. . +window opens if you select **specific** in **with specific folder type** in the Edit Conditions +box. ![Folder Type Window](/images/accessanalyzer/12.0/admin/action/mailbox/foldertypewindow.webp) @@ -45,14 +45,14 @@ Select the checkbox next to any desired folder type to include it in the search ## Search Terms Window -Use the Search Terms window to select terms contained in folder names to run the action against.The -Search Terms window opens if **search terms** is selected in the Edit Conditions box. +Use the Search Terms window to select terms contained in folder names to run the action against. The +Search Terms window opens if you select **search terms** in the Edit Conditions box. ![Search Terms Window](/images/accessanalyzer/12.0/admin/action/mailbox/searchtermswindow.webp) Edit the search terms using the following options: -- To add a term to the search, enter the desired term into the upper text box and click **Add** +- To add a term to the search, enter the term you want into the upper text box and click **Add** - To remove a term from the search, select a term in the lower text box and click **Remove** - Click **Clear** to clear all terms from the lower box - Select a qualifier option: @@ -67,8 +67,8 @@ Edit the search terms using the following options: ## Folder Inclusion/Exclusion Window Use the Folder Inclusion/Exclusion window to select individual folders to add to or remove from the -action. The Folder Inclusion/Exclusion window opens if **specific** in **with specific folder(s) to -include/exclude** is selected in the Edit Conditions box. +action. The Folder Inclusion/Exclusion window opens if you select **specific** in **with specific +folders to include/exclude** in the Edit Conditions box. ![Folder Inclusion/Exclusion Window](/images/accessanalyzer/12.0/admin/action/mailbox/folderinclusionexclusionwindow.webp) @@ -78,13 +78,13 @@ Include/Exclude folders using the following options: ![New field added on Folder Inclusion/Exclusion window](/images/accessanalyzer/12.0/admin/action/mailbox/folderinclusionexclusionwindownew.webp) -- Click the ellipsis (**…**) or enter the path to the desired folder in the text box -- Scope auto-populates with **This folder**. Click **This folder** to reveal a drop-down menu to +- Click the ellipsis (**…**) or enter the path to the folder you want in the text box +- Scope auto-populates with **This folder**. Click **This folder** to reveal a dropdown menu to select from the following scope options: - This folder - This folder and subfolders - Subfolders only -- The Remove button becomes enabled once a folder is added to either section. To remove a folder +- The Remove button becomes enabled once you add a folder to either section. To remove a folder from the scope, select it and click **Remove**. diff --git a/docs/accessanalyzer/12.0/admin/action/mailbox/folderidentification.md b/docs/accessanalyzer/12.0/admin/action/mailbox/folderidentification.md index 7d7c0d21ef..124562296a 100644 --- a/docs/accessanalyzer/12.0/admin/action/mailbox/folderidentification.md +++ b/docs/accessanalyzer/12.0/admin/action/mailbox/folderidentification.md @@ -16,7 +16,7 @@ options: - Yes, the query results contain a mailbox folder identification column - - Select the mailbox identification column using the drop-down menu + - Select the mailbox identification column using the dropdown menu - Folder Identifier Type – Choose which mailbox identifier the selected column uses: - Folder Path and Name – Select this option if the specified field contains a fully @@ -24,6 +24,6 @@ options: - Entry ID – Select this option if the selected field is an EntryID that is a unique identifier for a folder -- No, the query results do not contain a mailbox folder identification column – Selecting this +- No, the query results don't contain a mailbox folder identification column – Selecting this enables the Folder Conditions page, used to identify specific folders to target. See the [Mailbox: Folder Conditions](/docs/accessanalyzer/12.0/admin/action/mailbox/folderconditions.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/admin/action/mailbox/identification.md b/docs/accessanalyzer/12.0/admin/action/mailbox/identification.md index 8639d8ca7d..ab1a19b05a 100644 --- a/docs/accessanalyzer/12.0/admin/action/mailbox/identification.md +++ b/docs/accessanalyzer/12.0/admin/action/mailbox/identification.md @@ -18,7 +18,7 @@ Select which mailboxes to target using the following options: - Users found in the following column – Select this option to identify users via a data table column - - Use the drop-down menu to select a data table column containing either the Mailbox display + - Use the dropdown menu to select a data table column containing either the Mailbox display name or email address - Select a data type for the selected field using the following options: diff --git a/docs/accessanalyzer/12.0/admin/action/mailbox/messageactions.md b/docs/accessanalyzer/12.0/admin/action/mailbox/messageactions.md index 6096c6c905..5e0cf17cb0 100644 --- a/docs/accessanalyzer/12.0/admin/action/mailbox/messageactions.md +++ b/docs/accessanalyzer/12.0/admin/action/mailbox/messageactions.md @@ -16,8 +16,8 @@ To select a message action, use the following options: - Select an action – Select the checkbox next to a message action to apply it to the search. The selected action displays in the Edit Actions box. Possible actions include: - - Delete – Items can be recovered via the Deleted Contents table (folder dumpster) - - Permanent Delete – Items are not recoverable + - Delete – You can recover deleted items via the Deleted Contents table (folder dumpster) + - Permanent Delete – Items aren't recoverable - Move to Deleted Items folder - Delete Attachment (Append Text Options) – Deletes attachment and adds **Append Text Options** to the Edit Conditions box @@ -31,8 +31,8 @@ To select a message action, use the following options: ## Options Window -Use the Options window to add an appended text. The Options window opens if **Append Text Options** -is selected in the Edit Conditions box. +Use the Options window to add an appended text. The Options window opens if you select +**Append Text Options** in the Edit Conditions box. ![Options Window](/images/accessanalyzer/12.0/admin/action/mailbox/optionswindow.webp) diff --git a/docs/accessanalyzer/12.0/admin/action/mailbox/messageconditions.md b/docs/accessanalyzer/12.0/admin/action/mailbox/messageconditions.md index b98e8fbd7c..c59355c176 100644 --- a/docs/accessanalyzer/12.0/admin/action/mailbox/messageconditions.md +++ b/docs/accessanalyzer/12.0/admin/action/mailbox/messageconditions.md @@ -13,7 +13,7 @@ for the Delete Mailbox Contents operation. Customize the folder search conditions using the following options: -- Message Category – Use the drop-down menu to select a message category +- Message Category – Use the dropdown menu to select a message category :::note Each selection may populate various conditions in the Select Conditions section. @@ -39,14 +39,14 @@ Customize the folder search conditions using the following options: - Edit conditions – Any selected conditions populate here - To edit filter conditions, click the underlined portion of the condition. This opens a - corresponding window to configure the condition, with the exception of **has attachment(s)**. + corresponding window to configure the condition, with the exception of **has attachments**. - - Clicking **has attachment(s)** changes it to **has no attachment(s** and vice versa + - Clicking **has attachments** changes it to **has no attachment(s** and vice versa ## MessageClasses Window Use the MessageClasses window to select a message class to apply to the scope of the action. The -MessageClasses window opens if **specific** in **with specific message classes** is selected in the +MessageClasses window opens if you select **specific** in **with specific message classes** in the Edit Conditions box. ![MessageClasses Window](/images/accessanalyzer/12.0/admin/action/mailbox/messageclasseswindow.webp) @@ -57,8 +57,8 @@ Modify message classes using the following options: ![New class added in MessageClasses Window](/images/accessanalyzer/12.0/admin/action/mailbox/messageclasseswindownew.webp) -- Click the ellipsis (**…**) or enter the path to the desired folder in the text box -- Matching Strategy auto-populates with **Exact Match**. Click **Exact Match** to reveal a drop-down +- Click the ellipsis (**…**) or enter the path to the folder you want in the text box +- Matching Strategy auto-populates with **Exact Match**. Click **Exact Match** to reveal a dropdown menu to select from the following scope options: - Exact Match @@ -71,8 +71,8 @@ Modify message classes using the following options: ## Data Range Selection Window Use the Date Range Selection window to determine a time period to scope. The Date Range Selection -window opens if **in specific date** in either the **that is created in specific date** or **that is -received in specific date** conditions is selected in the Edit condition box. +window opens if you select **in specific date** in either the **that is created in specific date** +or **that is received in specific date** conditions in the Edit condition box. ![Data Range Selection Window](/images/accessanalyzer/12.0/admin/action/mailbox/datarangeselectionwindow.webp) @@ -86,18 +86,18 @@ To specify a date range, use the following options: - After - Between -- Configure the date range using the textbox or drop-down menus for the selected option +- Configure the date range using the textbox or dropdown menus for the selected option ## Search Terms Window Use the Search Terms window to select terms in messages to run the action against. The Search Terms -window opens if **search terms** in any condition is selected in the Edit Conditions box. +window opens if you select **search terms** in any condition in the Edit Conditions box. ![Search Terms Window](/images/accessanalyzer/12.0/admin/action/mailbox/searchtermswindow.webp) Edit the search terms using the following options: -- To add a term to the search, enter the desired term into the upper text box and click **Add** +- To add a term to the search, enter the term you want into the upper text box and click **Add** - To remove a term from the search, select a term in the lower text box and click **Remove** - Click **Clear** to clear all terms from the lower box - Specify a qualifier option: @@ -110,11 +110,11 @@ Edit the search terms using the following options: ## Values Window Use the Values window to add or remove values to or from the search. The Values window opens if -**specific** in **with specific Message ID** is selected in the Edit Conditions box. +you select **specific** in **with specific Message ID** in the Edit Conditions box. ![Values Window](/images/accessanalyzer/12.0/admin/action/mailbox/valueswindow.webp) -- To add a term to the search, enter the desired term into the upper text box and click **Add** +- To add a term to the search, enter the term you want into the upper text box and click **Add** - To remove a term from the search, select a term in the lower text box and click **Remove** - Click **Clear** to clear all terms from the lower box - Click **Import CSV** to open a file explorer and select a CSV file to import diff --git a/docs/accessanalyzer/12.0/admin/action/mailbox/operations.md b/docs/accessanalyzer/12.0/admin/action/mailbox/operations.md index c87043bd76..1bcc7dbc38 100644 --- a/docs/accessanalyzer/12.0/admin/action/mailbox/operations.md +++ b/docs/accessanalyzer/12.0/admin/action/mailbox/operations.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Mailbox: Operations -Use the Operations page to specify the operation to be performed as part of the action. +Use the Operations page to specify the operation to perform as part of the action. ![New Mailbox Action Wizard Operations page](/images/accessanalyzer/12.0/admin/action/mailbox/operations.webp) diff --git a/docs/accessanalyzer/12.0/admin/action/mailbox/overview.md b/docs/accessanalyzer/12.0/admin/action/mailbox/overview.md index 02755f24e6..15d3696975 100644 --- a/docs/accessanalyzer/12.0/admin/action/mailbox/overview.md +++ b/docs/accessanalyzer/12.0/admin/action/mailbox/overview.md @@ -6,18 +6,18 @@ sidebar_position: 40 # Mailbox Action Module -The Mailbox action module allows you to perform bulk operations on Microsoft Exchange mailboxes, for +Use the Mailbox action module to perform bulk operations on Microsoft Exchange mailboxes, for example deleting mailbox content and modifying permissions and delegates. :::warning This action module can add, change, or remove permissions and delegates from an -environment. Always verify the data and target mailboxes prior to executing any action. +environment. Always verify the data and target mailboxes before executing any action. ::: ## Mailbox Action Source Table Configuration -All data tables used in Access Analyzer action modules require the presence of certain data columns. +All data tables used in Access Analyzer action modules require certain data columns. In addition, individual action modules including Mailbox may have their own column requirements. The Mailbox action module requires a column containing mailbox names. diff --git a/docs/accessanalyzer/12.0/admin/action/mailbox/permissions.md b/docs/accessanalyzer/12.0/admin/action/mailbox/permissions.md index dacf092f8c..8f4820bbb2 100644 --- a/docs/accessanalyzer/12.0/admin/action/mailbox/permissions.md +++ b/docs/accessanalyzer/12.0/admin/action/mailbox/permissions.md @@ -11,7 +11,7 @@ Use the Permissions page to determine which permissions to remove. It is a wizar ![New Mailbox Action Wizard Permissions page](/images/accessanalyzer/12.0/admin/action/mailbox/permissions.webp) -Use the following options to add, change or remove Permissions: +Use the following options to add, change, or remove Permissions: - User – Specifies user permissions to add or change. To select different users, click the down-arrow to display the User window. See the [User Window](#user-window) topic for additional @@ -22,13 +22,12 @@ Use the following options to add, change or remove Permissions: window. See the [Permission Window](#permission-window) topic for additional information. - Propagate permissions to child folders – Propagates permissions to the child folders of the selected folders -- Once User, Folder, and Permission are selected, click **Add** to add them to the summary of the - action to be taken +- Once you select User, Folder, and Permission, click **Add** to add them to the action summary - To remove an added Permission, select it in the panel and click **Remove** ## User Window -Use the User window to select a user. The User window opens when the **User** down-arrow is selected +Use the User window to select a user. The User window opens when you select the **User** down-arrow on the Permissions page. ![User Window](/images/accessanalyzer/12.0/admin/action/mailbox/userwindow.webp) @@ -37,7 +36,7 @@ Select a user using the following options: - Users found in the following column – Select this option to identify users via a data table column - - Use the drop-down menu to select a data table column containing either the Mailbox display + - Use the dropdown menu to select a data table column containing either the Mailbox display name or email address - Select a data type for the selected field using the following options: @@ -64,8 +63,8 @@ Select a user using the following options: ## Folder Window -Use the Folder window to select folders. The Folder window opens when the **Folder** down-arrow is -selected on the Permissions page. +Use the Folder window to select folders. The Folder window opens when you select the **Folder** +down-arrow on the Permissions page. ![Folder Window](/images/accessanalyzer/12.0/admin/action/mailbox/folderwindow.webp) @@ -81,20 +80,20 @@ Select a folder using the following options: - The list of folders – Select one of the default folders - - Select a folder from the drop-down menu and click **Add** + - Select a folder from the dropdown menu and click **Add** - To remove a folder, select it and click **Remove** ## Permission Window -Use the Permission window to specify permissions. The Permission window opens when the -**Permission** down-arrow is selected on the Permissions page. +Use the Permission window to specify permissions. The Permission window opens when you select the +**Permission** down-arrow on the Permissions page. ![Permission Window](/images/accessanalyzer/12.0/admin/action/mailbox/permissionwindow.webp) Specify permissions using the following options: -- Permissions Level – Each permission level has a set of default selections. If a setting is - changed, the Permissions Level field changes to **Custom**. Permission levels are associated with +- Permissions Level – Each permission level has a set of default selections. If you change a + setting, the Permissions Level field changes to **Custom**. Permission levels are associated with the different permissions available for assignment through Outlook. Options include: - None @@ -131,7 +130,7 @@ Specify permissions using the following options: - Folder Contact – User receives automated messages about the folder such as replication conflict messages, requests from users for additional permissions, and other changes to folder status - - Folder visible – User can see the folder but cannot read or edit the items within + - Folder visible – User can see the folder but can't read or edit the items within - To add anonymous permissions, choose **None** diff --git a/docs/accessanalyzer/12.0/admin/action/mailbox/samplinghost.md b/docs/accessanalyzer/12.0/admin/action/mailbox/samplinghost.md index 38eada6b59..e424b0d640 100644 --- a/docs/accessanalyzer/12.0/admin/action/mailbox/samplinghost.md +++ b/docs/accessanalyzer/12.0/admin/action/mailbox/samplinghost.md @@ -19,12 +19,12 @@ Select an Exchange server to target using the following options: - Use the mailbox associated with the Windows account that Access Analyzer is run with – Uses either the account logged into the Access Analyzer Console server or the account set to run the Access Analyzer application to access the Exchange mailbox -- Exchange Mailbox (2010 and newer) – Allows Exhange Mailbox Alias to be specified for MAPI +- Exchange Mailbox (2010 and newer) – Lets you specify an Exchange Mailbox Alias for MAPI connections - - When Exchange Mailbox (2010 and newer) is selected, the textbox is enabled. Enter the Alias + - When you select Exchange Mailbox (2010 and newer), the wizard enables the textbox. Enter the Alias name in the textbox. The Alias needs to be an Exchange 2010 or newer mailbox, not a - mail-enabled service account. However, this mailbox does not need rights on the Exchange + mail-enabled service account. However, this mailbox doesn't need rights on the Exchange Organization; it only needs to reside within it. - Client Access Server – Enter the name of the physical CAS in the textbox. This server can be part of an array, but do enter the name of a CAS Array. This should also be the Exchange CAS diff --git a/docs/accessanalyzer/12.0/admin/action/mailbox/trustedusers.md b/docs/accessanalyzer/12.0/admin/action/mailbox/trustedusers.md index b2f260eac0..a3583f0a59 100644 --- a/docs/accessanalyzer/12.0/admin/action/mailbox/trustedusers.md +++ b/docs/accessanalyzer/12.0/admin/action/mailbox/trustedusers.md @@ -6,7 +6,7 @@ sidebar_position: 110 # Mailbox: Trusted Users -Use the Trusted Users page to select delegates to add. Users can be added individually or from a +Use the Trusted Users page to select delegates to add. You can add users individually or from a server with a mailbox environment. It is a wizard page for the following operations: - Add Delegates @@ -18,7 +18,7 @@ Select Trusted User delegates using the following options: - Users found in the following column – Select this option to identify users via a data table column - - Use the drop-down menu to select a data table column containing either the Mailbox display + - Use the dropdown menu to select a data table column containing either the Mailbox display name or email address - Select a data type for the selected field using the following options: @@ -50,7 +50,6 @@ The following additional options are available for the Remove Delegates operatio - Remove Permissions from Child Folders – Removes permissions from child folders :::note - This option is only enabled if the **Remove Permissions for Delegate** option is - selected. + This option is enabled only if you select the **Remove Permissions for Delegate** option. ::: diff --git a/docs/accessanalyzer/12.0/admin/action/overview.md b/docs/accessanalyzer/12.0/admin/action/overview.md index bdc4022731..73e721eea7 100644 --- a/docs/accessanalyzer/12.0/admin/action/overview.md +++ b/docs/accessanalyzer/12.0/admin/action/overview.md @@ -11,7 +11,7 @@ Analyzer. This overview topic describes the basic procedure for creating and exe module as well the initial steps to take when configuring an action. Each action module is described in detail in the relevant topics. -The Access Analyzer actions are capable of changing users, permissions, files, and objects from a +Access Analyzer actions can change users, permissions, files, and objects from a variety of environments. Action modules are assigned to a job at the **Configure** > **Actions** node. See the [Actions Node](/docs/accessanalyzer/12.0/admin/jobs/job/configure/actions.md) topic for additional information on the Action Selection view. @@ -21,7 +21,7 @@ the Action Selection view. Configure the action through the Action Properties page. Navigate to the job’s **Configure** > **Actions** node. Select **Create Action** to add a new action task to a job. Select an existing action and click **Action Properties** to modify its configuration. The Action Properties page opens -for either option. Pre-configured action tasks can be added from the Action Library. See the +for either option. You can add pre-configured action tasks from the Action Library. See the [Action Libraries](/docs/accessanalyzer/12.0/admin/action/libraries.md) topic for additional information. Most action modules are available with a special Access Analyzer License. The following table @@ -62,8 +62,8 @@ Target the selected objects and apply selected operations to the data. ### Executing Actions -Actions with the checkbox next to their name selected in the Action Selection view are executed -automatically as part of the job’s execution. The actions are executed in the order in which they +Actions with the checkbox next to their name selected in the Action Selection view run +automatically when the job runs. The actions run in the order in which they appear in the Selection table. You can also manually execute selected actions without running the job by clicking on the **Action Execute** link on the Action Selection view. @@ -72,14 +72,14 @@ job by clicking on the **Action Execute** link on the Action Selection view. :::warning Access Analyzer action modules apply bulk changes to targeted objects within the target environment. Actions perform operations on selected objects listed in each row of the source table. -Exercise caution to ensure the action applies only the desired changes and only to the desired -target objects. +Exercise caution to ensure the action applies only the changes you want and only to the +objects you want to target. ::: :::info -Prior to configuring the action module, scope the source data table to include -only the desired data. It is also recommended to run the action in a test environment before making +Before configuring the action module, scope the source data table to include +only the data you want. Also run the action in a test environment before making changes to a production environment. ::: @@ -99,7 +99,7 @@ created action tasks. - Name – Action task name. For new actions, an editable default name displays. - Description – Action task description. For new actions, this editable field is blank. -- Action Module – Drop-down menu of available action modules +- Action Module – dropdown menu of available action modules - Configure Action – Opens the configuration wizard for the selected action module @@ -111,14 +111,14 @@ created action tasks. - ID – Unique identifier, or GUID, of the action task generated by the application. With this ID, the database can distinguish actions, even those with identical configurations. - Data Grid – Displays a sample of the selected Source table. This data grid functions the same as - all data grids within Access Analyzer. Data can be filtered, and columns can be regrouped. See the + all data grids within Access Analyzer. You can filter data and regroup columns. See the [Data Grid Functionality](/docs/accessanalyzer/12.0/admin/navigate/datagrid.md) topic for additional information. ### Source Table Configuration All Access Analyzer actions require a source data table. The source table must contain, at a minimum, the following columns. Include these columns in addition to any other columns required by -the action module being used. Otherwise, errors may occur upon execution of the action and with +the action module being used. Otherwise, errors may occur when you run the action, affecting analysis and reports downstream. | Required Columns | Description | @@ -130,20 +130,20 @@ analysis and reports downstream. | RowKey | Identifies each data row as unique. Sometimes the value is a GUID, but the datatype in the table is a varchar (text string). | :::tip -Remember, the individual action modules may have their own column requirements in addition to the -above. +Remember, individual action modules may have their own column requirements in addition to the +columns listed here. ::: #### Data Tables -Access Analyzer native data tables generally contain all of the above columns. However, if all -required columns are not present by default, add them manually. +Access Analyzer native data tables generally contain all the columns listed here. However, if all +required columns aren't present by default, add them manually. :::warning -Do not use native data tables in action modules. Source data tables in actions should +Don't use native data tables in action modules. Source data tables in actions should include only the data desired for the operation. Scope the data tables to include only the required -columns prior to configuring the action. +columns before configuring the action. ::: diff --git a/docs/accessanalyzer/12.0/admin/action/powershell/executionoptions.md b/docs/accessanalyzer/12.0/admin/action/powershell/executionoptions.md index d2db889a68..30fade58a2 100644 --- a/docs/accessanalyzer/12.0/admin/action/powershell/executionoptions.md +++ b/docs/accessanalyzer/12.0/admin/action/powershell/executionoptions.md @@ -21,8 +21,8 @@ The options on the Execution Options page are: - Execute script remotely on a target server – Enable this to execute the PowerShell script on a remote target server - - Use the **Remote host** dropdown to select the database column that will be used as the target - server name or type in a network host name + - Use the **Remote host** dropdown to select the database column to use as the target + server name, or type in a network host name - Select the **Fall back to the local Access Analyzer server if the remote execution fails** option to use the Access Analyzer server if remote execution fails diff --git a/docs/accessanalyzer/12.0/admin/action/powershell/overview.md b/docs/accessanalyzer/12.0/admin/action/powershell/overview.md index 51156d20c0..cb5165b3ba 100644 --- a/docs/accessanalyzer/12.0/admin/action/powershell/overview.md +++ b/docs/accessanalyzer/12.0/admin/action/powershell/overview.md @@ -10,8 +10,7 @@ The PowerShell action module provides methods of running PowerShell scripts on t on remote hosts. Define PowerShell scripting actions using the PowerShell Action Module Wizard. :::warning -Ensure that only the changes required are applied and only to those target systems -desired. +Apply only the required changes, and only to the target systems you want to change. ::: diff --git a/docs/accessanalyzer/12.0/admin/action/powershell/script.md b/docs/accessanalyzer/12.0/admin/action/powershell/script.md index eefa4e7112..3355913373 100644 --- a/docs/accessanalyzer/12.0/admin/action/powershell/script.md +++ b/docs/accessanalyzer/12.0/admin/action/powershell/script.md @@ -6,15 +6,15 @@ sidebar_position: 10 # PowerShell Action: Script -The Script page enables you to input the PowerShell script that will be used to perform the +Use the Script page to input the PowerShell script used to perform the requested action. Built-in variables are available for use in the script. ![PowerShell Action Module Wizard Script page](/images/accessanalyzer/12.0/admin/action/powershell/script.webp) -The PowerShell script can be entered manually into the Script window at the top of the Script page. +You can enter the PowerShell script manually into the Script window at the top of the Script page. To open a pre-existing PowerShell script from a file, click **Open** to select the script file. -At the bottom of the page are three tabs that can be used to configure the PowerShell action module +At the bottom of the page are three tabs to configure the PowerShell action module further. The tabs are: - [Columns](#columns) @@ -27,8 +27,8 @@ Use the Columns tab to select the available columns. ![Columns tab](/images/accessanalyzer/12.0/admin/action/powershell/scriptcolumns.webp) -The table in the Columns tab displays the Columns that can be used for the PowerShell script. To use -a Column, select the checkbox under the **Use** column. +The table in the Columns tab displays the columns available for the PowerShell script. To use +a column, select the checkbox under the **Use** column. ![Right-click menu](/images/accessanalyzer/12.0/admin/action/powershell/scriptrightclickoption.webp) @@ -53,7 +53,7 @@ The options are: - Delete – Delete a selected parameter :::note -The built-in default parameters cannot be edited or deleted. +You can't edit or delete the built-in default parameters. ::: @@ -84,5 +84,5 @@ Preview how the input data will look in the Input Data tab. ![Input Data tab](/images/accessanalyzer/12.0/admin/action/powershell/scriptinputdata.webp) -Information in the Input Data tab varies depending on which source table the PowerShell action -module is configured to pull data from. +Information in the Input Data tab varies depending on which source table you configure the +PowerShell action module to pull data from. diff --git a/docs/accessanalyzer/12.0/admin/action/publicfolder/action.md b/docs/accessanalyzer/12.0/admin/action/publicfolder/action.md index 3580aaebb7..f0d9c1c9fd 100644 --- a/docs/accessanalyzer/12.0/admin/action/publicfolder/action.md +++ b/docs/accessanalyzer/12.0/admin/action/publicfolder/action.md @@ -10,8 +10,8 @@ The Action page specifies the basic action to perform on public folders. The pag selection in the Steps pane adjust based on this selection. :::note -Once an action is selected and saved, and the wizard is closed, this page is no longer -available and the selection cannot be altered. +Once you select and save an action and close the wizard, this page is no longer +available, and you can't alter the selection. ::: @@ -19,9 +19,8 @@ available and the selection cannot be altered. Choose from the following actions: -- Define a new action – Enables the Operation page where the operation on which the action is based - is selected -- Rollback a previously executed action – Enables the Prior Actions page where a list of previously - executed actions is displayed and a selected action may be rolled back. Not all operations support - rollback, and the Support Rollback option must be enabled prior to execution for the action to be - eligible for rollback. +- Define a new action – Enables the Operation page, where you select the operation on which to base + the action +- Rollback a previously executed action – Enables the Prior Actions page, which displays a list of + previously executed actions that you can roll back. Not all operations support rollback. Enable + the Support Rollback option before execution to make the action eligible for rollback. diff --git a/docs/accessanalyzer/12.0/admin/action/publicfolder/folders.md b/docs/accessanalyzer/12.0/admin/action/publicfolder/folders.md index 95714dd88a..520841160e 100644 --- a/docs/accessanalyzer/12.0/admin/action/publicfolder/folders.md +++ b/docs/accessanalyzer/12.0/admin/action/publicfolder/folders.md @@ -6,7 +6,7 @@ sidebar_position: 30 # Public Folder: Folders -The Folders page identifies which public folders are targeted by this action. +The Folders page identifies which public folders this action targets. ![Public Folder Action Module Wizard Folders page](/images/accessanalyzer/12.0/admin/action/publicfolder/folders.webp) @@ -17,8 +17,8 @@ The options on this page are: - Field – Column names :::note - The displayed fields vary depending on the Source Table selected during the - creation of the new action + The displayed fields vary depending on the Source Table you selected when you created + the new action ::: diff --git a/docs/accessanalyzer/12.0/admin/action/publicfolder/mapisettings.md b/docs/accessanalyzer/12.0/admin/action/publicfolder/mapisettings.md index 73d3dbb87d..590d15bfe4 100644 --- a/docs/accessanalyzer/12.0/admin/action/publicfolder/mapisettings.md +++ b/docs/accessanalyzer/12.0/admin/action/publicfolder/mapisettings.md @@ -16,6 +16,6 @@ Use the following options to configure the action: - System Attendant (2003 & 2007) - Use the mailbox associated with the Windows account on which Access Analyzer is run - Exchange Mailbox (2010 and newer) – If targeting a 2010 Exchange Server, specify the CAS server. - This is also where the MAPI setting is selected. + This is also where you select the MAPI setting. - Client Access Server – Enter the Domain Name in this field diff --git a/docs/accessanalyzer/12.0/admin/action/publicfolder/operations.md b/docs/accessanalyzer/12.0/admin/action/publicfolder/operations.md index d42017ba4a..8892f41d58 100644 --- a/docs/accessanalyzer/12.0/admin/action/publicfolder/operations.md +++ b/docs/accessanalyzer/12.0/admin/action/publicfolder/operations.md @@ -10,7 +10,7 @@ Use the Operations page to specify the operations to perform as part of the acti ![Public Folder Action Module Wizard Operations page](/images/accessanalyzer/12.0/admin/action/publicfolder/operations.webp) -The **Add operation** drop-down menu lists the operations that can be performed. Each operation +The **Add operation** dropdown menu lists the operations you can perform. Each operation opens a corresponding window. Operations include: - Rename – See the [Rename Folder Window](#rename-folder-window) topic for additional information @@ -22,9 +22,9 @@ opens a corresponding window. Operations include: - Limits – See the [Limits Window](#limits-window) topic for additional information - Delete – See the [Delete Folder Window](#delete-folder-window) topic for additional information -The buttons to the right of the drop-down control the operations in the field: +The buttons to the right of the dropdown control the operations in the field: -- Edit – Allows you to alter operation settings +- Edit – Alters operation settings - Add – Places selected operation one step above its current position - Down – Places selected operation one step below its current position - Delete – Removes a selected operation @@ -66,7 +66,7 @@ Change permissions using the following options: - Mode – Select whether to change or remove permissions - Permissions – Determine Permission level and assign permissions to the user - - Permission level – Use the drop-down menu to select a permission level from the following: + - Permission level – Use the dropdown menu to select a permission level from the following: - Reviewer - Contributor @@ -84,20 +84,20 @@ Change permissions using the following options: - Read items – User can read items - Create Subfolders – User can create subfolders - Folder owner – User can view and move the public folder, create subfolders, and set - permissions for the folder, but cannot read, edit, delete, or create items + permissions for the folder, but can't read, edit, delete, or create items - Folder contact – Set user as the contact for the specified public folder - - Folder visible – User can view the specified public folder but cannot read or edit the + - Folder visible – User can view the specified public folder but can't read or edit the items within :::note - Different permissions become automatically selected based on which permission - level is selected. To override this default, select the checkbox of the unwanted permission - to deselect it. If a desired checkbox is blocked by a black square, click the square to - unblock the checkbox. The checkbox can then be selected or unselected. + Selecting a permission level automatically selects the corresponding permissions. To + override this default, select the checkbox of the unwanted permission to deselect it. If a + desired checkbox is blocked by a black square, click the square to unblock the checkbox. You + can then select or unselect the checkbox. ::: - - Edit items – Use the drop-down menu to determine user editing permissions from the following: + - Edit items – Use the dropdown menu to determine user editing permissions from the following: - No change - None @@ -106,7 +106,7 @@ Change permissions using the following options: - Own only - All - - Delete items – Use the drop-down menu to determine user deletion permissions from the + - Delete items – Use the dropdown menu to determine user deletion permissions from the following: - No change @@ -132,8 +132,8 @@ Select attributes using the following options: - Select a Field from the dropdown list and click **Add** to add the field to the custom attribute :::note - Multiple fields may be added to a custom attribute. Fields added to a custom attribute - can be modified or deleted manually. + You can add multiple fields to a custom attribute. You can also modify or delete added + fields manually. ::: @@ -145,7 +145,7 @@ Use the Replicas window to replicate servers. It is a wizard page for the Replic Replicate servers using the following options: -- Select a server from the dropdown menu and click **Add**. The servers listed will be replicated. +- Select a server from the dropdown menu and click **Add**. The action replicates the listed servers. - Select a server from the list and click **Delete** to remove it from the list of replicated servers - Select the **Remove last replica** option to delete the replica created when the action was last @@ -182,5 +182,5 @@ Select deletion settings using the following options: - Optionally, select a checkbox to apply any exception - - Do not delete folders with subfolders - - Do not delete folders with content + - Don't delete folders with subfolders + - Don't delete folders with content diff --git a/docs/accessanalyzer/12.0/admin/action/publicfolder/overview.md b/docs/accessanalyzer/12.0/admin/action/publicfolder/overview.md index 3a3c04a227..dd09173ef6 100644 --- a/docs/accessanalyzer/12.0/admin/action/publicfolder/overview.md +++ b/docs/accessanalyzer/12.0/admin/action/publicfolder/overview.md @@ -6,24 +6,22 @@ sidebar_position: 60 # PublicFolder Action Module -The Public Folder action module allows users to make bulk changes to selected Microsoft Exchange +Use the Public Folder action module to make bulk changes to selected Microsoft Exchange public folders by adding, changing, or removing folders and permissions from the environment. Use the Pubic Folder Action Module Wizard to choose the data table column that identifies the folders and to configure the operations performed against the selected folders. -Prior to configuring the Pubic Folder Action Module Wizard, scope the source data table to ensure -the actions apply only to the desired folders. +Before configuring the Pubic Folder Action Module Wizard, scope the source data table to ensure +the actions apply only to the folders you want to change. :::warning -Be careful when using this action module. Make sure that only the changes required are -applied and only to those target folders desired. Always verify the data prior to execution of any -action. +Be careful when using this action module. Apply only the required changes, and only to the target +folders you want to change. Always verify the data before executing any action. ::: :::info -Although rollbacks for some actions are available, having to use one should be -avoided +Although rollbacks for some actions are available, avoid using one when possible ::: diff --git a/docs/accessanalyzer/12.0/admin/action/publicfolder/prioractions.md b/docs/accessanalyzer/12.0/admin/action/publicfolder/prioractions.md index c68eb8618d..2188c9452a 100644 --- a/docs/accessanalyzer/12.0/admin/action/publicfolder/prioractions.md +++ b/docs/accessanalyzer/12.0/admin/action/publicfolder/prioractions.md @@ -10,8 +10,8 @@ The Prior Actions page selects previously executed actions for rollback. It is a **Rollback a previously executed action** is selected on the Action page. :::note -Once an action is selected and saved, and the wizard is closed, this page is no longer -available and the selection cannot be altered. +Once you select and save an action and close the wizard, this page is no longer +available, and you can't alter the selection. ::: diff --git a/docs/accessanalyzer/12.0/admin/action/publicfolder/rollback.md b/docs/accessanalyzer/12.0/admin/action/publicfolder/rollback.md index e7bae823e6..68729b9b25 100644 --- a/docs/accessanalyzer/12.0/admin/action/publicfolder/rollback.md +++ b/docs/accessanalyzer/12.0/admin/action/publicfolder/rollback.md @@ -6,8 +6,8 @@ sidebar_position: 60 # Public Folder: Rollback -Use the Rollback page to enable rollback capabilities for the action. If rollback isn’t selected at -this step, the applied operations cannot be rolled back after execution of the action module. +Use the Rollback page to enable rollback capabilities for the action. If you don't select rollback +at this step, you can't roll back the applied operations after the action module runs. ![Public Folder Action Module Wizard Rollback page](/images/accessanalyzer/12.0/admin/action/publicfolder/rollback.webp) diff --git a/docs/accessanalyzer/12.0/admin/action/publicfolder/summary.md b/docs/accessanalyzer/12.0/admin/action/publicfolder/summary.md index 3cc7cf182c..bb821b7b02 100644 --- a/docs/accessanalyzer/12.0/admin/action/publicfolder/summary.md +++ b/docs/accessanalyzer/12.0/admin/action/publicfolder/summary.md @@ -10,6 +10,6 @@ The Summary page summarizes the configuration of the action. ![Public Folder Action Module Wizard Summary page](/images/accessanalyzer/12.0/admin/action/publicfolder/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Public Folder Action Module Wizard to ensure that no accidental clicks -are saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** to +close the Public Folder Action Module Wizard instead. This prevents the wizard from saving +accidental clicks. diff --git a/docs/accessanalyzer/12.0/admin/action/registry/operations.md b/docs/accessanalyzer/12.0/admin/action/registry/operations.md index 7e819f87c2..2e438a6ce3 100644 --- a/docs/accessanalyzer/12.0/admin/action/registry/operations.md +++ b/docs/accessanalyzer/12.0/admin/action/registry/operations.md @@ -13,11 +13,11 @@ Use the Operations page to select the operations to apply to the target hosts. S Select and configure the operations using the following options: -- Add operation – Use the drop-down menu to select an operation to perform on the target host. This +- Add operation – Use the dropdown menu to select an operation to perform on the target host. This opens a corresponding window for configuration. Operations include: :::note - Window options vary based on the operation selected from the drop-down menu. + Window options vary based on the operation selected from the dropdown menu. ::: @@ -44,12 +44,12 @@ Select a key using the following options: - Computer name – By default, the Registry browser connects to the local machine - - If the desired registry item is on the local machine, browse the registry, and select the item + - If the registry item you want is on the local machine, browse the registry, and select it - To connect to the registry of another machine: - Enter the hostname in the **Computer name** textbox - Click **Connect**, then browse the registry of that machine - - Select the desired registry item + - Select the registry item you want - Connect – Attempts to connect to the registry of the machine specified in the **Computer name** field @@ -64,14 +64,14 @@ Use the Select Users or Groups window to select a user, group, or built-in secur The options are: -- Select this object type – Displays types that are queried against +- Select this object type – Displays the object types you can query - Click **Object Types** to open the Object Types window and select the types to query against. See the [Object Types Window](#object-types-window) topic for additional information. -- From this location – Displays the location the intended objects are found +- From this location – Displays the location to search for the intended objects - - Click **Locations** to open the Locations window and set the location to be queried. See the + - Click **Locations** to open the Locations window and set the location to query. See the [Locations Window](#locations-window) topic for additional information. - Enter the object names to select – Select names of objects to query @@ -126,8 +126,8 @@ following additional options: - Columns – Click **Columns** to open the Choose Columns window. See the [Choose Columns Window](#choose-columns-window) topic for additional information. - Find now – Click **Find Now** to search for objects matching the selected criteria -- Stop – While a search is running , the **Stop** button is available. Click **Stop** to halt the - search before it is completed. +- Stop – While a search is running, the **Stop** button is available. Click **Stop** to halt the + search before it completes. - Search Results – Displays results from a search #### Choose Columns Window diff --git a/docs/accessanalyzer/12.0/admin/action/registry/overview.md b/docs/accessanalyzer/12.0/admin/action/registry/overview.md index 19c2672e0f..6bc8ca8d4b 100644 --- a/docs/accessanalyzer/12.0/admin/action/registry/overview.md +++ b/docs/accessanalyzer/12.0/admin/action/registry/overview.md @@ -6,13 +6,13 @@ sidebar_position: 70 # Registry Action Module -The Registry action module allows users to make bulk changes to the Microsoft Windows Registry. Use +Use the Registry action module to make bulk changes to the Microsoft Windows Registry. Use the Registry Action Module Wizard to choose the data table column that identifies the folders and to configure the operations performed against the selected folders. The Registry action module requires -a column containing the hosts to be targeted. +a column containing the hosts to target. -Prior to configuring the Registry Action Module Wizard, scope the source data table to ensure the -actions apply only to the desired hosts. +Before configuring the Registry Action Module Wizard, scope the source data table to ensure the +actions apply only to the hosts you want to target. :::warning Unexpected values in the registry can cause major system failures when deleting or @@ -28,9 +28,9 @@ module. ## Registry Action Source Table Configuration -All data tables used in Access Analyzer action modules require the presence of certain data columns. +All data tables used in Access Analyzer action modules require certain data columns. In addition, individual action modules including Registry may have their own column requirements. -The Registry action module requires a column containing the hosts that are going to be targeted. +The Registry action module requires a column containing the hosts you want to target. ## Configuration diff --git a/docs/accessanalyzer/12.0/admin/action/registry/summary.md b/docs/accessanalyzer/12.0/admin/action/registry/summary.md index b18106e7cc..b7b7acdb15 100644 --- a/docs/accessanalyzer/12.0/admin/action/registry/summary.md +++ b/docs/accessanalyzer/12.0/admin/action/registry/summary.md @@ -10,6 +10,6 @@ The Summary page summarizes the configuration of the action. ![Registry Action Module Wizard Summary page](/images/accessanalyzer/12.0/admin/action/registry/summary.webp) -When done configuring the action, click **Finish**. If no changes were made, it is a best practice -to click **Cancel** to close the Registry Action Module Wizard to ensure that no accidental clicks -are saved. +When done configuring the action, click **Finish**. If you didn't make any changes, click **Cancel** +to close the Registry Action Module Wizard instead. This prevents the wizard from saving accidental +clicks. diff --git a/docs/accessanalyzer/12.0/admin/action/registry/targethosts.md b/docs/accessanalyzer/12.0/admin/action/registry/targethosts.md index e9ed4cb068..5d2f750df4 100644 --- a/docs/accessanalyzer/12.0/admin/action/registry/targethosts.md +++ b/docs/accessanalyzer/12.0/admin/action/registry/targethosts.md @@ -11,6 +11,6 @@ alters. ![Registry Action Module Wizard Target hosts page](/images/accessanalyzer/12.0/admin/action/registry/targethosts.webp) -Use the drop-down menu to select the field that identifies the systems to be targeted. The list +Use the dropdown menu to select the field that identifies the systems to target. The list displays columns from the specified source table. The action applies the specified operations to all systems in the field. diff --git a/docs/accessanalyzer/12.0/admin/action/sendmail/message.md b/docs/accessanalyzer/12.0/admin/action/sendmail/message.md index d056604729..9d08e364c8 100644 --- a/docs/accessanalyzer/12.0/admin/action/sendmail/message.md +++ b/docs/accessanalyzer/12.0/admin/action/sendmail/message.md @@ -15,8 +15,8 @@ Use the following fields to specify the text of the email: - Subject – Specify a subject for the email. The contents of this field displays as the subject line of the delivered email. Enter text directly and optionally use the Insert field to insert one or more data fields. This is a required field. -- Insert Field – Inserts a data field into the subject or body of the email. The drop-down menu - displays a list of available fields. Once a selection displays in the field, click on the blue Up +- Insert Field – Inserts a data field into the subject or body of the email. The dropdown menu + displays a list of available fields. Once a selection displays in the field, click the blue Up and Down arrows to insert the field into the body or the subject, respectively. This field is optional. - Show sample input source data – To display a table of sample source data, click the icon next to @@ -25,7 +25,7 @@ Use the following fields to specify the text of the email: blue arrows to display the SMTP Options dialog box - Preview – Displays the Message Preview window containing a preview of the current SendMail. Click **Send** to send a single message to the addresses in the Recipient field in the Message Preview - window. The Preview button is active only if the Recipients field is populated on the Properties + window. The Preview button is active only if you populate the Recipients field on the Properties page of the Send Mail Action Module Wizard. See the [Messages Preview Window](#messages-preview-window) topic for additional information. - Clear Template – Clears any content from the Subject and Text Entry box @@ -54,7 +54,7 @@ Use the following fields to specify the text of the email: ## Text Entry Box -The Text Entry box allows you to compose a message. A Microsoft Word-style editor provides +Use the Text Entry box to compose a message. A Microsoft Word-style editor provides formatting options including the ability to insert dynamic text from the specified table (such as a username) through the Insert field option. Use the editor to personalize the content and appearance of each message. @@ -62,13 +62,13 @@ of each message. Example: Assume the source table includes a column containing the names of intended recipients. Place the -cursor in the greeting section of the email. Next, select that field from the Insert field drop-down +cursor in the greeting section of the email. Next, select that field from the Insert field dropdown list and click the down arrow to insert a dynamic field. The column name appears in the Text Entry box, enclosed by brackets: Dear [ProbableOwner]; -You are approaching your Mailbox storage quota. Please clean up any unneeded items. +You are approaching your Mailbox storage quota. clean up any unneeded items. **Thank you,** diff --git a/docs/accessanalyzer/12.0/admin/action/sendmail/overview.md b/docs/accessanalyzer/12.0/admin/action/sendmail/overview.md index ef77f5d01a..4479dd6575 100644 --- a/docs/accessanalyzer/12.0/admin/action/sendmail/overview.md +++ b/docs/accessanalyzer/12.0/admin/action/sendmail/overview.md @@ -16,14 +16,14 @@ The SendMail Action Module has multiple uses, for example: workflow to contact clients and solicit feedback for use in the decision-making process :::warning -This module sends one or more electronic messages to a selected audience. Prior to -executing the action, ensure the audience consists of only the desired members. +This module sends one or more electronic messages to a selected audience. Before +executing the action, ensure the audience consists of only the members you want to include. ::: ## Source Table Configuration -All data tables used in Access Analyzer action modules require the presence of certain data columns. +All data tables used in Access Analyzer action modules require certain data columns. In addition, individual action modules including SendMail may have their own column requirements. The SendMail Action Module requires a column containing well-formatted email addresses (for example, `hfinn@netwrix.com`) for your recipients. diff --git a/docs/accessanalyzer/12.0/admin/action/sendmail/properties.md b/docs/accessanalyzer/12.0/admin/action/sendmail/properties.md index b8c26b0ad1..aa8438aeb0 100644 --- a/docs/accessanalyzer/12.0/admin/action/sendmail/properties.md +++ b/docs/accessanalyzer/12.0/admin/action/sendmail/properties.md @@ -12,16 +12,16 @@ Use the Properties page to specify the recipients of the email. Use the following fields to specify the recipient information: -- Recipient column – Use the drop-down menu to specify the column from the data table containing +- Recipient column – Use the dropdown menu to specify the column from the data table containing intended recipients, for example a column containing email addresses -- Recipient type – Use the drop-down menu to specify the data type of the Recipient column, for +- Recipient type – Use the dropdown menu to specify the data type of the Recipient column, for example SMTP mail address - Carbon copy (CC) – Optionally, specify one or more additional email addresses to receive a carbon-copy of the SendMail message, for example an address not included in the source table. - Use the following email address – Enter one or more additional email addresses. Separate multiple addresses with a semi-colon and a space. - - Use a column from the table – Use the drop-down menu to specify a column from the data table + - Use a column from the table – Use the dropdown menu to specify a column from the data table - Combine multiple messages into a single message when all recipients are the same – Select this checkbox to send only one message to each recipient as a result of this action (even recipients diff --git a/docs/accessanalyzer/12.0/admin/action/sendmail/summary.md b/docs/accessanalyzer/12.0/admin/action/sendmail/summary.md index 5db91af97a..8a855fbed6 100644 --- a/docs/accessanalyzer/12.0/admin/action/sendmail/summary.md +++ b/docs/accessanalyzer/12.0/admin/action/sendmail/summary.md @@ -10,9 +10,9 @@ The Summary page displays the SendMail configuration. ![Send Mail Action Module Wizard Summary page](/images/accessanalyzer/12.0/admin/action/sendmail/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Send Mail Action Module Wizard to ensure that no accidental clicks are -saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** to +close the Send Mail Action Module Wizard instead. This prevents the wizard from saving accidental +clicks. To view the status of executed SendMail actions, see the [Viewing the Status of SendMail Actions](/docs/accessanalyzer/12.0/admin/action/sendmail/viewstatus.md) for additional information. diff --git a/docs/accessanalyzer/12.0/admin/action/sendmail/viewstatus.md b/docs/accessanalyzer/12.0/admin/action/sendmail/viewstatus.md index 69f0431f9d..c6f9d9ccda 100644 --- a/docs/accessanalyzer/12.0/admin/action/sendmail/viewstatus.md +++ b/docs/accessanalyzer/12.0/admin/action/sendmail/viewstatus.md @@ -6,7 +6,7 @@ sidebar_position: 40 # Viewing the Status of SendMail Actions -Follow the steps to view the status of an executed SendMail action: +To view the status of an executed SendMail action, complete the following steps: ![Analysis Properties page for SendMail View Status Analysis task](/images/accessanalyzer/12.0/admin/action/sendmail/viewstatusanalysisproperties.webp) diff --git a/docs/accessanalyzer/12.0/admin/action/servicenow/authentication.md b/docs/accessanalyzer/12.0/admin/action/servicenow/authentication.md index 8de9ff381a..8f2668540d 100644 --- a/docs/accessanalyzer/12.0/admin/action/servicenow/authentication.md +++ b/docs/accessanalyzer/12.0/admin/action/servicenow/authentication.md @@ -8,7 +8,7 @@ sidebar_position: 10 The Authentication page implements signing into a ServiceNow account. -A ServiceNow account must be set up and configured to determine which incidents will be visible on +You must set up and configure a ServiceNow account to determine which incidents appear on the Incident Creation page. ![ServiceNow Action Module wizard Authentication page](/images/accessanalyzer/12.0/admin/action/servicenow/authentication.webp) diff --git a/docs/accessanalyzer/12.0/admin/action/servicenow/description.md b/docs/accessanalyzer/12.0/admin/action/servicenow/description.md index 6ede97877d..5894f801bc 100644 --- a/docs/accessanalyzer/12.0/admin/action/servicenow/description.md +++ b/docs/accessanalyzer/12.0/admin/action/servicenow/description.md @@ -7,15 +7,15 @@ sidebar_position: 30 # ServiceNow Action: Description The Description page provides details on the incidents entered into a field on the Incident Creation -page. A description of the incident and related comments are included with the incident’s report to -provide additional feedback to the system administrator, and may be saved to a template. +page. The incident's report includes a description of the incident and related comments to provide +additional feedback to the system administrator. You can also save these to a template. ![ServiceNow Action Module wizard Description page](/images/accessanalyzer/12.0/admin/action/servicenow/description.webp) Create a report using the following options: - Short Description – Displays entered words or phrases used to summarize the incident -- Insert Field – Use the drop-down menu to select a field (column) from the source table +- Insert Field – Use the dropdown menu to select a field (column) from the source table - Click the **blue down arrow** to insert the item into the Short Description section - Click the **blue up arrow** to insert the item in to the Comments section diff --git a/docs/accessanalyzer/12.0/admin/action/servicenow/incidentcreation.md b/docs/accessanalyzer/12.0/admin/action/servicenow/incidentcreation.md index 4693c95aae..2eddbfae5a 100644 --- a/docs/accessanalyzer/12.0/admin/action/servicenow/incidentcreation.md +++ b/docs/accessanalyzer/12.0/admin/action/servicenow/incidentcreation.md @@ -6,17 +6,17 @@ sidebar_position: 20 # ServiceNow Action: Incident Creation -The Incident Creation page is available once the ServiceNow credentials are approved. Incidents on -this page belong to two fields: Mandatory and Optional. The type of field and its incidents are -chosen within ServiceNow’s configuration page. Selecting a field and entering a value will include +The Incident Creation page is available after ServiceNow approves the credentials. Incidents on +this page belong to two fields: Mandatory and Optional. You configure the type of field and its +incidents within ServiceNow’s configuration page. Selecting a field and entering a value will include the incident within ServiceNow’s incident report. ![ServiceNow Action Module wizard New Incident page](/images/accessanalyzer/12.0/admin/action/servicenow/incidentcreation.webp) At the New Incident field list section, enter the fields for which incident to include on ServiceNow’s incident report. The ServiceNow account entered on the Authentication page determines -which incidents are available within the fields on the Incidents Creation page and are adjusted in -ServiceNow. +which incidents are available within the fields on the Incidents Creation page. You adjust these +incidents in ServiceNow. -Fields with a drop-down menu have a set of preconfigured options to select. Fields with ellipsis +Fields with a dropdown menu have a set of preconfigured options to select. Fields with ellipsis choose members from a preconfigured list. diff --git a/docs/accessanalyzer/12.0/admin/action/servicenow/overview.md b/docs/accessanalyzer/12.0/admin/action/servicenow/overview.md index 9ce3a4a849..9b70768c87 100644 --- a/docs/accessanalyzer/12.0/admin/action/servicenow/overview.md +++ b/docs/accessanalyzer/12.0/admin/action/servicenow/overview.md @@ -6,18 +6,18 @@ sidebar_position: 90 # ServiceNow Action Module -The ServiceNow Action Module is primarily intended to allow for the automated creation of ServiceNow -incidents from data collected by the Netwrix suite of data security tools. By facilitating -communication between tools like Access Analyzer and ServiceNow’s incident management capability, -security risks in an organization’s environment can not only be identified, but presented to admins, -managers, and other stakeholders in a familiar way, with respect to chains of command and approval -as dictated by employee relationships and business workflows implemented in ServiceNow. +The ServiceNow Action Module automates the creation of ServiceNow incidents from data collected by +the Netwrix suite of data security tools. By facilitating communication between tools like Access +Analyzer and ServiceNow’s incident management capability, the module doesn't just identify security +risks in an organization’s environment — it presents them to admins, managers, and other +stakeholders in a familiar way, following the chains of command and approval that employee +relationships and business workflows define in ServiceNow. When account lockouts occur, the Active Directory Inventory Data Collector makes that information available. From the Access Analyzer console, the ServiceNow Action Module transmits customized information regarding the locked out accounts directly to those responsible for account management, -alerting them of the issue and requesting that appropriate action is taken to re-enable user -accounts before effected users are aware of the problem. +alerting them of the issue and requesting that they take appropriate action to re-enable user +accounts before affected users become aware of the problem. This section describes the following pages in the configuration wizard. @@ -32,16 +32,16 @@ The ServiceNow Action Module requires an active ServiceNow account with: ## Permissions -The following permissions are required to utilize Access Analyzer’s ServiceNow Action Module: +The following permissions are required to use Access Analyzer’s ServiceNow Action Module: - ServiceNow admin account – An Administrator Role by an organization’s ServiceNow administrator -- The **Settings** > **ServiceNow** node at the global level can be configured with a credential +- You can configure the **Settings** > **ServiceNow** node at the global level with a credential provisioned to create incidents as Callers in the **Assigned to** field, and any other ServiceNow incident field that references the sys_user table. ## Connecting ServiceNow -The following instructions can only be performed with a ServiceNow admin account and access to the +You can perform the following instructions only with a ServiceNow admin account and access to the ServiceNow Action Module XML file. ![ServiceNow Action Module XML file in Windows file explorer](/images/accessanalyzer/12.0/admin/action/servicenow/actionmodulexmlfile.webp) @@ -50,23 +50,23 @@ ServiceNow Action Module XML file. `STEALTHbits SN Action Module v1.0_merged_rev2.0` file to use on ServiceNow’s website. **Step 2 –** Visit servicenow.com, sign into the administrator account, expand **System Update -Sets**, and click on **Retrieved Update Sets**. +Sets**, and click **Retrieved Update Sets**. -**Step 3 –** Under **Related Links**, click on **Import Update Set from XML**. +**Step 3 –** Under **Related Links**, click **Import Update Set from XML**. **Step 4 –** Attach the `STEALTHbits SN Action Module v1.0_merged_rev2.0` file, and then click **Upload**. -**Step 5 –** After the file is uploaded, click on the **STEALTHbits SN Action Module** within the +**Step 5 –** After you upload the file, click the **STEALTHbits SN Action Module** within the list of updated sets. -**Step 6 –** Click on the **Preview Update Set** button. Wait until the update set preview is -finished and then click **Commit Update Set**. Then, close the Update Set Commit window. +**Step 6 –** Click the **Preview Update Set** button. Wait until the update set preview +completes, then click **Commit Update Set**. Then, close the Update Set Commit window. **Step 7 –** On the navigation page, expand **System Definitions** and click **Plugins**. Then click on the **Insert Multiple Web Service plugin** -**Step 8 –** Under **Related Links**, click on **Activate/Upgrade** and click **Activate** on the +**Step 8 –** Under **Related Links**, click **Activate/Upgrade** and click **Activate** on the Activate Plugin window. When the Activation is complete, click **Close** to close the window. **Step 9 –** Click **Reload** on the System Plugin page and confirm the Status is Active. diff --git a/docs/accessanalyzer/12.0/admin/action/servicenow/summary.md b/docs/accessanalyzer/12.0/admin/action/servicenow/summary.md index 0ff331c99d..332c408023 100644 --- a/docs/accessanalyzer/12.0/admin/action/servicenow/summary.md +++ b/docs/accessanalyzer/12.0/admin/action/servicenow/summary.md @@ -10,6 +10,6 @@ The Summary page displays a summary of the configured query. ![ServiceNow Action Module wizard Summary page](/images/accessanalyzer/12.0/admin/action/servicenow/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the ServiceNow Action Module Wizard to ensure that no accidental clicks -are saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** to +close the ServiceNow Action Module Wizard instead. This prevents the wizard from saving accidental +clicks. diff --git a/docs/accessanalyzer/12.0/admin/action/survey/introduction.md b/docs/accessanalyzer/12.0/admin/action/survey/introduction.md index a42dbea445..5f7ad9f72c 100644 --- a/docs/accessanalyzer/12.0/admin/action/survey/introduction.md +++ b/docs/accessanalyzer/12.0/admin/action/survey/introduction.md @@ -8,7 +8,7 @@ sidebar_position: 20 Use this page to specify web page introductory text (if any) for the web page specified on the Web Server page. See the [Survey: Web Server](/docs/accessanalyzer/12.0/admin/action/survey/webserver.md) topic for additional information. The -introductory text appears on the landing page when recipients click on the survey link in the email. +introductory text appears on the landing page when recipients click the survey link in the email. ![Survey Action Module Wizard Introduction Page](/images/accessanalyzer/12.0/admin/action/survey/introduction.webp) @@ -19,7 +19,7 @@ The configurable options are: are limited to data from the SQL table specified at the Source Table field on the Action Properties page. - Place the cursor in the text where a field should appear. Next, click on the drop-down and + Place the cursor in the text where a field should appear. Next, click the dropdown and select a field from the list. When a selection appears in the field, click the blue down arrow. The field appears in the text. diff --git a/docs/accessanalyzer/12.0/admin/action/survey/mailmessage.md b/docs/accessanalyzer/12.0/admin/action/survey/mailmessage.md index 8f164fc03b..6f60ada0e4 100644 --- a/docs/accessanalyzer/12.0/admin/action/survey/mailmessage.md +++ b/docs/accessanalyzer/12.0/admin/action/survey/mailmessage.md @@ -13,7 +13,7 @@ not using them. ![Survey Action Module Wizard Mail – Message page](/images/accessanalyzer/12.0/admin/action/survey/mailmessage.webp) Placeholder text displays in the Message box. This text includes a hyperlink to the web page hosting -the survey. Placeholder text can be modified but the link cannot be removed. The link does not +the survey. You can modify the placeholder text, but you can't remove the link. The link doesn't activate until the message is sent. Use the following fields to specify the text of the email: @@ -21,8 +21,8 @@ Use the following fields to specify the text of the email: - Subject – Specify subject text for the email. The contents of this field displays as the Subject line of the delivered email. Enter text directly and use the **Insert field** to insert one or more data fields. This is a required field. -- Insert Field – Inserts a data field into the subject or body of the email. The drop-down menu - displays a list of available fields. Once a selection displays in the field, click on the blue +- Insert Field – Inserts a data field into the subject or body of the email. The dropdown menu + displays a list of available fields. Once a selection displays in the field, click the blue Down and Up arrows to insert the field into the body or the subject, respectively. This field is optional. - The following are buttons appearing on a bar below the Subject field: @@ -33,18 +33,18 @@ Use the following fields to specify the text of the email: the blue arrows to display the SMTP Options dialog box - Preview – Displays the Messages Preview window containing a preview of the current email message. Click **Send** to send a single message to the addresses in the Recipient field in - the Message Preview window. The Preview button is active only if the Recipients field is - populated. See the [Messages Preview Window](#messages-preview-window) topic for additional + the Message Preview window. The Preview button is active only if you populate the Recipients + field. See the [Messages Preview Window](#messages-preview-window) topic for additional information. - Clear Template – Clears any content from the Subject and Text Entry box -- Load from template – Survey templates are a legacy feature. It is strongly recommended not use +- Load from template – Survey templates are a legacy feature. Netwrix strongly recommends not using templates when creating surveys. - Save to template – Saves the current email subject and content to a template. If an existing template name appears in the **Load from template** field, clicking this button updates that template. If the **Load from template** field is empty or contains a name other than one of the - existing templates, clicking this button accesses the Save SendMail Template window and changes - can be saved to a new template. Templates reside locally on the host computer as XML files, in the + existing templates, clicking this button accesses the Save SendMail Template window, and you can save changes + to a new template. Templates reside locally on the host computer as XML files, in the `Actions/SM_Templates` folder. ## Messages Preview Window diff --git a/docs/accessanalyzer/12.0/admin/action/survey/mailproperties.md b/docs/accessanalyzer/12.0/admin/action/survey/mailproperties.md index 3f3121f879..21a38a63b9 100644 --- a/docs/accessanalyzer/12.0/admin/action/survey/mailproperties.md +++ b/docs/accessanalyzer/12.0/admin/action/survey/mailproperties.md @@ -14,10 +14,10 @@ Use the following fields to specify the recipient information: - Recipient column – Specify the data table columns containing intended recipient information - - For example, a column containing email addresses. The drop-down menu displays a list of + - For example, a column containing email addresses. The dropdown menu displays a list of possible column types. -- Recipient type – Specify the data type of the Recipient column. The drop-down menu displays a list +- Recipient type – Specify the data type of the Recipient column. The dropdown menu displays a list of recipient types, for example **SMTP email address**. - Carbon copy (CC) – (Optional) Specify one or more additional email addresses to receive a carbon-copy of the SendMail message, for example an address not included in the source table. diff --git a/docs/accessanalyzer/12.0/admin/action/survey/overview.md b/docs/accessanalyzer/12.0/admin/action/survey/overview.md index f05c07b702..ab97c6fe40 100644 --- a/docs/accessanalyzer/12.0/admin/action/survey/overview.md +++ b/docs/accessanalyzer/12.0/admin/action/survey/overview.md @@ -10,20 +10,20 @@ Use this action module to create surveys and make them available to targeted rec For example, a survey can solicit feedback from clients or poll employees on company issues. The Survey Action Module Wizard builds customizable, web-based surveys containing questions created -by the user. Once the survey is defined, a list of recipients can then be specified. When executing +by the user. After you define the survey, specify a list of recipients. When executing the action, the process simultaneously sends an email to the recipients containing a link to the survey and creates a web page to host the survey. :::warning -This module sends one or more electronic messages to a selected audience. Prior to -executing the action, ensure the audience consists of only the desired members. Netwrix recommends +This module sends one or more electronic messages to a selected audience. Before +executing the action, ensure the audience consists of only the members you want to include. Netwrix recommends using this and all other Access Analyzer actions with caution. ::: ## Survey Action Source Table Configuration -All data tables used in Access Analyzer action modules require the presence of certain data columns. +All data tables used in Access Analyzer action modules require certain data columns. In addition, individual action modules including Survey may have their own column requirements. The Survey action module requires a column containing well-formatted email addresses (for example, `hfinn@netwrix.com`) for your recipients. diff --git a/docs/accessanalyzer/12.0/admin/action/survey/questions.md b/docs/accessanalyzer/12.0/admin/action/survey/questions.md index a71e051d66..8baa0c24d5 100644 --- a/docs/accessanalyzer/12.0/admin/action/survey/questions.md +++ b/docs/accessanalyzer/12.0/admin/action/survey/questions.md @@ -39,7 +39,7 @@ The configurable options are: available: - Text – Specify the survey question - - Subjects – Click on the ellipses (**…**) to open the Select subjects window. Specify the + - Subjects – Click the ellipses (**…**) to open the Select subjects window. Specify the object to which a question is directed. The selected subjects show in the Subjects field. See the [Select Subjects Window](#select-subjects-window) topic for additional information. - Answer Column Name – The Survey action module inserts the results of the survey directly into @@ -49,11 +49,11 @@ The configurable options are: - Yes/No - Text - - Multiple Choice – If this option is selected, the **Answers** button activates. Click this + - Multiple Choice – If you select this option, the **Answers** button activates. Click this button to open the Answers window and specify the response options to the multiple choice question via the **Add** button. - - Answers – This button activates if Multiple Choice in the Question Type field is selected. + - Answers – This button activates if you select Multiple Choice in the Question Type field. Click to access the Answers window. - Description – Specify any additional explanation of the survey question. The text appears on the survey below the associated question. diff --git a/docs/accessanalyzer/12.0/admin/action/survey/testsurvey.md b/docs/accessanalyzer/12.0/admin/action/survey/testsurvey.md index cf71673b13..b87d52f52c 100644 --- a/docs/accessanalyzer/12.0/admin/action/survey/testsurvey.md +++ b/docs/accessanalyzer/12.0/admin/action/survey/testsurvey.md @@ -13,6 +13,5 @@ Use this page to test a survey and verify proper configuration. The configurable options are: - Start test – Click to test your survey configuration -- Survey full test – Once the survey configuration test passes inspection, a full survey can be - tested against a single user (for example, your own email account) to verify a survey matches - design criteria +- Survey full test – After the survey configuration test passes inspection, test a full survey + against a single user (for example, your own email account) to verify it matches design criteria diff --git a/docs/accessanalyzer/12.0/admin/action/webrequest/destination.md b/docs/accessanalyzer/12.0/admin/action/webrequest/destination.md index 05a768d563..4d4af99851 100644 --- a/docs/accessanalyzer/12.0/admin/action/webrequest/destination.md +++ b/docs/accessanalyzer/12.0/admin/action/webrequest/destination.md @@ -12,7 +12,7 @@ Use the Destination page to specify all settings for the destination of the web Use the following categories to establish the location of the web request: -- Insert field – Select a field using the drop-down menu +- Insert field – Select a field using the dropdown menu :::note The fields available varies based on the source table columns. @@ -41,12 +41,12 @@ Use the following categories to establish the location of the web request: - Resource – URL destination to send the data via the web request - - Select a field using the drop-down menu, place the cursor in the Resource textbox, and click + - Select a field using the dropdown menu, place the cursor in the Resource textbox, and click the blue down-arrow to add it to the Resource box - Manually enter a resource in the textbox :::note - A red circle with an x indicates that the Resource field cannot be empty. + A red circle with an x indicates that the Resource field can't be empty. ::: @@ -56,17 +56,17 @@ Use the following categories to establish the location of the web request: - Basic – Basic authentication - JWT – JSON Web Token, a URL-safe authentication method - Basic and JWT authentications are pulled from the credential profile set in the job. It inserts - that data into the authentication header of the web request with the proper format expected (for + The wizard pulls Basic and JWT authentication from the credential profile set in the job. It + inserts that data into the authentication header of the web request with the proper format expected (for example, Basic [Base64 encoded credentials] or Bearer [JWT token] for Basic and JWT authentication respectively). **Test Connection** -- Drop-down menu – Select a method to test. Currently locked to GET. +- dropdown menu – Select a method to test. locked to GET. - URI textbox – Input the resource to receive the test message - - Select a field using the drop-down menu, place the cursor in text area, and click the blue + - Select a field using the dropdown menu, place the cursor in text area, and click the blue down-arrow to add it to the URI textbox - Manually enter a resource in the field diff --git a/docs/accessanalyzer/12.0/admin/action/webrequest/header.md b/docs/accessanalyzer/12.0/admin/action/webrequest/header.md index 0f5bea2e15..b998333561 100644 --- a/docs/accessanalyzer/12.0/admin/action/webrequest/header.md +++ b/docs/accessanalyzer/12.0/admin/action/webrequest/header.md @@ -12,7 +12,7 @@ Use the Header page to enter the header values for the request. Use the following options to enter header values: -- Insert field – Select a field to include in the request using the drop-down menu +- Insert field – Select a field to include in the request using the dropdown menu :::note The fields available varies based on the source table columns. @@ -26,6 +26,6 @@ Use the following options to enter header values: - Key / Value fields – The name or value of the attribute - - Select a field using the drop-down menu, place the cursor in the cell of the desired Key or - Value, and click the blue down-arrow to add it to the selected cell + - Select a field using the dropdown menu, place the cursor in the cell of the Key or Value + field you want, and click the blue down-arrow to add it to the selected cell - Manually enter a field in the cell diff --git a/docs/accessanalyzer/12.0/admin/action/webrequest/overview.md b/docs/accessanalyzer/12.0/admin/action/webrequest/overview.md index 5c1b95a8e4..cd35a01ae1 100644 --- a/docs/accessanalyzer/12.0/admin/action/webrequest/overview.md +++ b/docs/accessanalyzer/12.0/admin/action/webrequest/overview.md @@ -7,12 +7,12 @@ sidebar_position: 110 # WebRequest Action Module The Web Request action module provides methods of applying bulk changes to REST endpoints. At this -stage, target endpoints should be identified to invoke web requests against. This wizard allows the -definition of requests to perform. +stage, identify the target endpoints to invoke web requests against. This wizard lets you define +requests to perform. :::warning -Ensure that only the changes required are applied and only those target systems desired -when using this action module. +When using this action module, apply only the required changes, and only to the target +systems you want. ::: diff --git a/docs/accessanalyzer/12.0/admin/action/webrequest/parameters.md b/docs/accessanalyzer/12.0/admin/action/webrequest/parameters.md index 32268af111..12e1828821 100644 --- a/docs/accessanalyzer/12.0/admin/action/webrequest/parameters.md +++ b/docs/accessanalyzer/12.0/admin/action/webrequest/parameters.md @@ -12,7 +12,7 @@ Use the Parameters page to enter the parameter values. Enter parameter values using the following options: -- Insert Field – Select a field to include in the request from the drop-down menu. +- Insert Field – Select a field to include in the request from the dropdown menu. :::note The fields available varies based on the source table. @@ -36,8 +36,8 @@ Enter parameter values using the following options: - Key / Value Fields – The name or value of the attribute - - Select a field using the drop-down menu, place the cursor in the cell of the desired Key or - Value, and click the blue down-arrow to add it to the selected cell + - Select a field using the dropdown menu, place the cursor in the cell of the Key or Value + field you want, and click the blue down-arrow to add it to the selected cell - Select a cell and click the green circle with plus sign to open the Custom Attribute Editor window and add the attribute to the cell - Manually enter a field in the cell @@ -51,16 +51,16 @@ and advanced functions. Create custom attributes using the following options: -- Insert field – Select a field to insert using the drop-down menu -- Unique name – Name of the custom attribute that will be created +- Insert field – Select a field to insert using the dropdown menu +- Unique name – Name for the custom attribute to create - - Select a field using the drop-down menu, place the cursor in the Unique name textbox, and + - Select a field using the dropdown menu, place the cursor in the Unique name textbox, and click the blue down-arrow to add it to the Unique name textbox - Manually enter the name - Data – The actual value of the custom attribute (can be database value or manually specified) - - Select a field using the drop-down menu, place the cursor in the Data textbox, and click the + - Select a field using the dropdown menu, place the cursor in the Data textbox, and click the blue down-arrow to add it to the Data textbox - Manually enter the data diff --git a/docs/accessanalyzer/12.0/admin/action/webrequest/summary.md b/docs/accessanalyzer/12.0/admin/action/webrequest/summary.md index 7a99244f4b..511044faec 100644 --- a/docs/accessanalyzer/12.0/admin/action/webrequest/summary.md +++ b/docs/accessanalyzer/12.0/admin/action/webrequest/summary.md @@ -10,6 +10,6 @@ The Summary page displays a summary of the configured action. ![Web Request Action Module Wizard Summary page](/images/accessanalyzer/12.0/admin/action/webrequest/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Web Request Action Module Wizard to ensure that no accidental clicks -are saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** to +close the Web Request Action Module Wizard instead. This prevents the wizard from saving accidental +clicks. diff --git a/docs/accessanalyzer/12.0/admin/analysis/autoaction.md b/docs/accessanalyzer/12.0/admin/analysis/autoaction.md index d18a7d4ade..e12b3b2484 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/autoaction.md +++ b/docs/accessanalyzer/12.0/admin/analysis/autoaction.md @@ -18,13 +18,13 @@ The Actions node can also automatically execute actions. See the ## Select Action Window -The Select Action window lists the actions that currently exist within the Job that can be selected -to automatically run upon job execution. +The Select Action window lists the actions that exist within the Job and that you can select +to run automatically upon job execution. ![Select Action Window](/images/accessanalyzer/12.0/admin/analysis/autoaction.webp) Select an action from the list. Click **OK** to exit the window, and then click **Save** to preserve -the changes made to the analysis module. The action now executes as part of the analysis task. If no -actions were selected, it is best practice to click **Cancel** to close the Select Action window to -ensure no accidental selections are saved. Actions only display if they exist within the Actions +the changes made to the analysis module. The action now executes as part of the analysis task. If you didn't select any actions, click +**Cancel** to close the Select Action window instead. This prevents the wizard from saving +accidental selections. Actions only display if they exist within the Actions node of the current Job. diff --git a/docs/accessanalyzer/12.0/admin/analysis/businessrules/appliesto.md b/docs/accessanalyzer/12.0/admin/analysis/businessrules/appliesto.md index a8b0e9d897..4629d7785e 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/businessrules/appliesto.md +++ b/docs/accessanalyzer/12.0/admin/analysis/businessrules/appliesto.md @@ -20,14 +20,14 @@ The Applies To tab provides the following options: - All Source Data – Select this option to run the action using all data - Source Data from this Console only – Select this option to run the action specifically using data from only this Access Analyzer console - - Time Window for source table – Use the drop-down menu to specify a time window from the + - Time Window for source table – Use the dropdown menu to specify a time window from the following options: - Most recent data – Use only the most recently collected data - Cumulative data for offline hosts – Use data collected from offline hosts - Most recent data filtering duplicate and offline hosts – Use most recent data excluding duplicate and offline hosts - - Do not filter data – Use unfiltered data + - Don't filter data – Use unfiltered data - Hosts Filtering – Specify source hosts diff --git a/docs/accessanalyzer/12.0/admin/analysis/businessrules/logic.md b/docs/accessanalyzer/12.0/admin/analysis/businessrules/logic.md index 177d8bafa9..5b7868ab21 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/businessrules/logic.md +++ b/docs/accessanalyzer/12.0/admin/analysis/businessrules/logic.md @@ -16,7 +16,7 @@ The Logic tab contains the following sections and options: - Rule Name – The field defaults with the name on the Analysis Properties page and is manually editable - - Table – Select a table from the drop-down menu containing the baseline values to evaluate + - Table – Select a table from the dropdown menu containing the baseline values to evaluate - To view data from a selected table, click the ellipsis (**…**) to open the Sample Data Viewer window, or select a table within the viewer. See the @@ -48,20 +48,20 @@ Use the Sample Data Viewer window to examine data in a selected table. The Sample Data Viewer window provides the following options: -- Use the drop-down menu to select a table to view the table’s data. The field defaults with the +- Use the dropdown menu to select a table to view the table’s data. The field defaults with the table selected in the Logic tab if previously selected. - Show First [Number] rows – Adjusts the presentation of the number of rows of the selected table. The default value is 50. It can be manually adjusted with values between 0 and all. ## EditConditionsForm Window -Use the EditConditionsForm to configure conditions to be applied to the table. +Use the EditConditionsForm to configure conditions to apply to the table. ![EditConditionsForm Window](/images/accessanalyzer/12.0/admin/analysis/businessrules/editconditionsform.webp) The EditConditionsForm contains the following options: -- Column – Use the drop-down menu to select a column from the table selected in the Logic tab +- Column – Use the dropdown menu to select a column from the table selected in the Logic tab - Operator – Use the dropdown to select an operator: - `<` – Search for items in the selected column with values less than a selected value @@ -101,14 +101,14 @@ The Configure Scorecard Options window provides the following options: - Action Name – Enter a name for the action - Description – Enter a description for the action -- Action Classification – This section allows you to group scorecard action results for reporting +- Action Classification – Use this section to group scorecard action results for reporting purposes - Category – Enter a desired category name in the field or use the dropdown to select from previously titled categories - Index – Enter a desired index value for the scorecard action -- Action Score – This section allows you to rank the action’s importance relative to other scorecard +- Action Score – Use this section to rank the action’s importance relative to other scorecard actions - Score – Enter a desired score value for the scorecard action @@ -119,9 +119,9 @@ The Configure Scorecard Options window provides the following options: - Knowledge – Enter information to assist issue resolution, for example a website URL -- Captured Values – This section allows you to select up to five optional properties whose values - will be captured and stored with the scorecard entry. For each property selected, a name column +- Captured Values – Use this section to select up to five optional properties. The system captures + and stores their values with the scorecard entry. For each property selected, a name column and value column appear in the scorecard. - - Property [1-5] – Select a property from the selected table using the drop-down menu to capture + - Property [1-5] – Select a property from the selected table using the dropdown menu to capture and store its values with the scorecard diff --git a/docs/accessanalyzer/12.0/admin/analysis/businessrules/overview.md b/docs/accessanalyzer/12.0/admin/analysis/businessrules/overview.md index 309a0f2204..c9c50776e1 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/businessrules/overview.md +++ b/docs/accessanalyzer/12.0/admin/analysis/businessrules/overview.md @@ -8,19 +8,19 @@ sidebar_position: 20 The Business Rules analysis module measures and evaluates a configured value from an object (the baseline value) and compares it against a stated value (the business rule) to find an exception or -deviation. Any deviations or differences found the execution of a business rule appear in a +deviation. Any deviations or differences found when a business rule runs appear in a resultant table called a scorecard. -Create one or more jobs to collect the data to be analyzed. Then configure one or business rules to +Create one or more jobs to collect the data to analyze. Then configure one or business rules to analyze the data. Examine the scoreboard to determine how an object is performing with regard to its original baseline expectations. ## Scorecard -Business Rules analysis module results are displayed in a table called a scorecard. The scorecard -determines which of the rules are applied, and in what order. A scorecard table contains only +The Business Rules analysis module displays results in a table called a scorecard. The scorecard +determines which rules apply, and in what order. A scorecard table contains only exceptions and deviations from the business rule criteria when compared to a baseline value. The -table does not include matches to the criteria. All scorecard table names are suffixed with +table doesn't include matches to the criteria. All scorecard table names end with `_SCORECARD` for easy identification. ## Edit Rules Window diff --git a/docs/accessanalyzer/12.0/admin/analysis/changedetection/additionalfields.md b/docs/accessanalyzer/12.0/admin/analysis/changedetection/additionalfields.md index fb649b3d70..2d8c7960ad 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/changedetection/additionalfields.md +++ b/docs/accessanalyzer/12.0/admin/analysis/changedetection/additionalfields.md @@ -7,7 +7,7 @@ sidebar_position: 50 # Change Detection: Additional Fields Use the Additional Fields page to choose any additional fields to include with the change analysis. -These fields do not detect change, but may provide additional information to help diagnose and +These fields don't detect change, but may provide additional information to help diagnose and analyze the changes reported. ![Change Detection Data Analysis Module wizard Additional Fields page](/images/accessanalyzer/12.0/admin/analysis/changedetection/additionalfields.webp) diff --git a/docs/accessanalyzer/12.0/admin/analysis/changedetection/input.md b/docs/accessanalyzer/12.0/admin/analysis/changedetection/input.md index 22c9d922f9..1affc57da6 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/changedetection/input.md +++ b/docs/accessanalyzer/12.0/admin/analysis/changedetection/input.md @@ -12,10 +12,10 @@ Use the Input Data Source page to choose a data source to analyze for changes. The configurable option is: -- Please select a data source – Select a data source table from the list +- select a data source – Select a data source table from the list :::note - The selectable data sources change based on which option is selected on the Input + The selectable data sources change based on the option you select on the Input Scope page. ::: diff --git a/docs/accessanalyzer/12.0/admin/analysis/changedetection/inputscope.md b/docs/accessanalyzer/12.0/admin/analysis/changedetection/inputscope.md index b9e5b52290..632d15a5b9 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/changedetection/inputscope.md +++ b/docs/accessanalyzer/12.0/admin/analysis/changedetection/inputscope.md @@ -12,11 +12,11 @@ Use the Input Scope page to specify the input scope of the data source. Identify the scope of the data source from the following options: -- Tables from Current Job – Select tables from only the currently selected job +- Tables from Current Job – Select tables from only the selected job - All Access Analyzer Tables – Select from all Access Analyzer tables within the SQL Server database - All tables in the database – Select all tables within the SQL Server database :::note -This selection affects the tables that are available for selection on the Input page. +This selection affects the tables available to select on the Input page. ::: diff --git a/docs/accessanalyzer/12.0/admin/analysis/changedetection/options.md b/docs/accessanalyzer/12.0/admin/analysis/changedetection/options.md index f55b2216e6..7e6c7c5641 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/changedetection/options.md +++ b/docs/accessanalyzer/12.0/admin/analysis/changedetection/options.md @@ -13,7 +13,7 @@ made within a certain time period, or only changes between the last two runs of Configure the additional options using the following: -- Save change detection results for xx days – Modify the number of days that results for the Change - Detection task are saved for +- Save change detection results for xx days – Modify the number of days the Change + Detection task saves results - Only save most recent change (per unique key) – Select the checkbox to only save changes between the last two runs of the source set diff --git a/docs/accessanalyzer/12.0/admin/analysis/changedetection/overview.md b/docs/accessanalyzer/12.0/admin/analysis/changedetection/overview.md index 48e33398ad..0f834fee8a 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/changedetection/overview.md +++ b/docs/accessanalyzer/12.0/admin/analysis/changedetection/overview.md @@ -13,7 +13,7 @@ most recent collection. This module compares values collected for two different query instances. Therefore, as change detection depends on the existence of a **JobRunTimeKey**, history must be enabled and data -collected at least twice to produce the desired results. Configure History settings under the job’s +collected at least twice to produce comparison results. Configure History settings under the job’s **Settings** > **History** node. See the [History](/docs/accessanalyzer/12.0/admin/settings/history.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/admin/analysis/changedetection/summary.md b/docs/accessanalyzer/12.0/admin/analysis/changedetection/summary.md index 91db12469d..36d426c6f7 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/changedetection/summary.md +++ b/docs/accessanalyzer/12.0/admin/analysis/changedetection/summary.md @@ -10,5 +10,6 @@ The Summary page summarizes the configuration of the action. ![Change Detection Data Analysis Module wizard Summary page](/images/accessanalyzer/12.0/admin/analysis/changedetection/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, click **Cancel** to close -the Change Detection Data Analysis Module wizard to ensure no accidental configurations are saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** to +close the Change Detection Data Analysis Module wizard instead. This prevents the wizard from +saving accidental configurations. diff --git a/docs/accessanalyzer/12.0/admin/analysis/notification/changetype.md b/docs/accessanalyzer/12.0/admin/analysis/notification/changetype.md index 4baad190e1..30bec89d5e 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/notification/changetype.md +++ b/docs/accessanalyzer/12.0/admin/analysis/notification/changetype.md @@ -7,8 +7,8 @@ sidebar_position: 30 # Notification: Change Type Use the Select Change Type page to choose the types of changes for which to trigger a notification. -The selections on this page are optional. This page is only active if Change Detection Table is -selected on the Table Type page. +The selections on this page are optional. This page is only active if you select Change Detection Table +on the Table Type page. ![Notification Data Analysis Module wizard Select Change Type page](/images/accessanalyzer/12.0/admin/analysis/notification/changetype.webp) diff --git a/docs/accessanalyzer/12.0/admin/analysis/notification/commandline.md b/docs/accessanalyzer/12.0/admin/analysis/notification/commandline.md index 83980daada..ead18ae046 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/notification/commandline.md +++ b/docs/accessanalyzer/12.0/admin/analysis/notification/commandline.md @@ -6,8 +6,8 @@ sidebar_position: 80 # Notification: Command Line -The Command Line properties page is available when the Command-line Executable notification type is -selected on the Type page. +The Command Line properties page is available when you select the Command-line Executable +notification type on the Type page. ![Notification Data Analysis Module wizard Command Line properties page](/images/accessanalyzer/12.0/admin/analysis/notification/commandline.webp) @@ -17,7 +17,7 @@ The following options are available: view and select from a list of executable files. - Arguments – If required, specify command line inputs for the application in the text box. If the argument must come from a value in the database (for example, a timeout value), insert it here via - the Fields drop-down menu above. + the Fields dropdown menu above. - - Fields – To pass one or more fields into the command line arguments, click the drop-down menu, + - Fields – To pass one or more fields into the command line arguments, click the dropdown menu, select a field from the lists, and click **Add** diff --git a/docs/accessanalyzer/12.0/admin/analysis/notification/criteria.md b/docs/accessanalyzer/12.0/admin/analysis/notification/criteria.md index c98530d5e5..d3e7a9ea76 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/notification/criteria.md +++ b/docs/accessanalyzer/12.0/admin/analysis/notification/criteria.md @@ -12,8 +12,8 @@ Use the Notification Criteria page to specify criteria to trigger a notification The following options are available: -- No Criteria – Set no criteria to trigger a notification if any property changes. If selected, any - row will trigger the notification. +- No Criteria – Set no criteria to trigger a notification if any property changes. If you select + this option, any row triggers the notification. - Simple Criteria – Select criteria to send a notification based on the value of a specific property or column in the database. The trigger can be if the property or column value is greater than, equal to, or less than the value provided. diff --git a/docs/accessanalyzer/12.0/admin/analysis/notification/eventlog.md b/docs/accessanalyzer/12.0/admin/analysis/notification/eventlog.md index 9163c72b9c..0cd53efc46 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/notification/eventlog.md +++ b/docs/accessanalyzer/12.0/admin/analysis/notification/eventlog.md @@ -6,7 +6,7 @@ sidebar_position: 90 # Notification: Event Log -The Event Log properties page is available when the Event log notification type is selected on the +The Event Log properties page is available when you select the Event log notification type on the Type page. Use this page to specify the type of event, the event ID, and the description for the event. @@ -15,7 +15,7 @@ event. The following options are available: - Log – The event log name is Access Analyzer -- Type – Specify the log type. The drop-down menu displays the following options: +- Type – Specify the log type. The dropdown menu displays the following options: - Information - Warning @@ -26,5 +26,5 @@ The following options are available: - Event ID – Specify the event ID - Description – Enter a description of the event - - Fields – To pass fields into the description, click on the drop-down list, select a field from + - Fields – To pass fields into the description, click the dropdown list, select a field from the list, then click **Add** diff --git a/docs/accessanalyzer/12.0/admin/analysis/notification/hosts.md b/docs/accessanalyzer/12.0/admin/analysis/notification/hosts.md index f06a5c4661..38056cb961 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/notification/hosts.md +++ b/docs/accessanalyzer/12.0/admin/analysis/notification/hosts.md @@ -16,11 +16,11 @@ The following options are available: - I want notifications sent only for the hosts listed below - I want notifications sent for all hosts except the ones listed below -If the first option is selected, the host list selection window is not enabled. If either the second -or third option is selected, the following options are enabled: +If you select the first option, the host list selection window isn't enabled. If you select either +the second or third option, the wizard enables the following options: -- Show me all host lists – Activates the host list selection window, from which individual host - lists can be selected -- Enter hosts manually – Manually enter specific host names. Once the name is entered, click the add - (**+**) button to add it to the selection box. Ensure the checkbox next to the host name is - selected to include it in the list of hosts. +- Show me all host lists – Activates the host list selection window, from which you can select + individual host lists +- Enter hosts manually – Manually enter specific host names. After entering the name, click the add + (**+**) button to add it to the selection box. Ensure you select the checkbox next to the host + name to include it in the list of hosts. diff --git a/docs/accessanalyzer/12.0/admin/analysis/notification/overview.md b/docs/accessanalyzer/12.0/admin/analysis/notification/overview.md index 92b8cf2fd3..d895ff567e 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/notification/overview.md +++ b/docs/accessanalyzer/12.0/admin/analysis/notification/overview.md @@ -6,7 +6,7 @@ sidebar_position: 40 # Notification Analysis Module -The Notification Data analysis module provides the ability to send an email or command-line +The Notification Data analysis module lets you send an email or command-line notification to selected targets based on the values contains in any table. The Notification Data Analysis Module has the following prerequisites: diff --git a/docs/accessanalyzer/12.0/admin/analysis/notification/smtp.md b/docs/accessanalyzer/12.0/admin/analysis/notification/smtp.md index ce1660c5bb..d7cc5595a7 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/notification/smtp.md +++ b/docs/accessanalyzer/12.0/admin/analysis/notification/smtp.md @@ -24,13 +24,13 @@ The following options are available: - Subject – Specify a subject for the email. The subject can include field variables. :::info - If configuring a Notification analysis module for a pre-configured job, it is - recommended not to change the existing field variables. + If you configure a Notification analysis module for a pre-configured job, avoid changing the + existing field variables. ::: - Insert Field – Select a source data column to add to the message body or subject line. Click the - drop-down to see a list of columns. Once the column displays in the field, click an arrow to + dropdown to see a list of columns. After the column displays in the field, click an arrow to insert the field. - Down arrow – Adds the selected source column to the message text @@ -39,9 +39,9 @@ The following options are available: - Embed HTML Report – Embed a HTML report in the notification email. Click the Embed HTML Report button to navigate to the HTML file. - Show sample input source data – Opens the Sample Source Data window, containing sample input - source data as it currently exists in the database -- Show dialog to set SMTP options – Opens the SMTP Options window, where SMTP global settings can be - overwritten through manual configuration + source data as it exists in the database +- Show dialog to set SMTP options – Opens the SMTP Options window, where you can overwrite SMTP + global settings through manual configuration - Preview – Displays a preview of the email. :::note @@ -49,9 +49,9 @@ The following options are available: ::: -- Clear Template – Clears all data from the subject and message boxes. Does not clear e-mail +- Clear Template – Clears all data from the subject and message boxes. Doesn't clear e-mail addresses. - Text Box – Specify the text of the email message. The toolbar above the text box contains various icons providing access to text editing and formatting tools. To insert fields from Access - Analyzer, choose a field from the drop-down menu and click the Down arrow. Block tag formatting is + Analyzer, choose a field from the dropdown menu and click the Down arrow. Block tag formatting is supported. diff --git a/docs/accessanalyzer/12.0/admin/analysis/notification/summary.md b/docs/accessanalyzer/12.0/admin/analysis/notification/summary.md index 0d1daf77db..62cbaa5687 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/notification/summary.md +++ b/docs/accessanalyzer/12.0/admin/analysis/notification/summary.md @@ -11,6 +11,6 @@ previous pages of the wizard. ![Notification Data Analysis Module wizard Summary page](/images/accessanalyzer/12.0/admin/analysis/notification/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is best practice to -click **Cancel** to close the Notification Data Analysis Module wizard to ensure no accidental -clicks are saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** to +close the Notification Data Analysis Module wizard instead. This prevents the wizard from saving +accidental clicks. diff --git a/docs/accessanalyzer/12.0/admin/analysis/notification/tabletype.md b/docs/accessanalyzer/12.0/admin/analysis/notification/tabletype.md index 2bd6cfc6f9..225bb8d67c 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/notification/tabletype.md +++ b/docs/accessanalyzer/12.0/admin/analysis/notification/tabletype.md @@ -13,19 +13,19 @@ notifications. The following options are available: -- Change Detection Table – Sends notifications when changes are detected in the data. When selected, - the option of **Show only tables for this job** becomes the default selection on the Select Table +- Change Detection Table – Sends notifications when the data changes. When you select this option, + **Show only tables for this job** becomes the default selection on the Select Table page. This option targets only change detection tables within the current job. Possible tables (if any) display on the Select Table page. See the [Notification: Select Table](/docs/accessanalyzer/12.0/admin/analysis/notification/selecttable.md) topic for additional information. :::note - Change Detection Table also locks selections to tables on the Select Table page that - are selected through Other. To select tables outside of **Show only tables for this job**, + Change Detection Table also locks selections to tables that you select through Other on + the Select Table page. To select tables outside of **Show only tables for this job**, select Other on the Table Type page, then select either **Show All Tables** or **Show All SA Tables**, then click back to return to the Table Type page. Now selecting Change Detection Table - and proceeding defaults the selection on the Select Table page to whichever was previously - selected through Other. + and proceeding defaults the selection on the Select Table page to whichever option you + previously selected through Other. ::: diff --git a/docs/accessanalyzer/12.0/admin/analysis/notification/timewindow.md b/docs/accessanalyzer/12.0/admin/analysis/notification/timewindow.md index 7c05ec132f..b7b067ae37 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/notification/timewindow.md +++ b/docs/accessanalyzer/12.0/admin/analysis/notification/timewindow.md @@ -16,7 +16,7 @@ The following option is available: to the most recent data :::note - The checkbox is only enabled if the table selected on the Select Table page has a - Access Analyzer **JobRunTimeKey** property. Otherwise, the checkbox is cleared by default. + Access Analyzer only enables the checkbox if the table selected on the Select Table page has an + Access Analyzer **JobRunTimeKey** property. Otherwise, it clears the checkbox by default. ::: diff --git a/docs/accessanalyzer/12.0/admin/analysis/overview.md b/docs/accessanalyzer/12.0/admin/analysis/overview.md index 8bdb6b81be..d55be594a9 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/overview.md +++ b/docs/accessanalyzer/12.0/admin/analysis/overview.md @@ -6,16 +6,16 @@ sidebar_position: 90 # Analysis Modules -The Access Analyzer analysis modules are capable of finding unique data and notifying users of its -location from a variety of environments. Analysis modules are assigned to a job at the +The Access Analyzer analysis modules find unique data and notify users of its +location across a variety of environments. You assign analysis modules to a job at the **Configure** > **Analysis** node. See the [Analysis Node](/docs/accessanalyzer/12.0/admin/jobs/job/configure/analysis/analysis.md) topic for information on the Analysis Selection view. ![Configure an analysis](/images/accessanalyzer/12.0/admin/analysis/configure.webp) -Analysis tasks are configured through the Analysis Properties page. Navigate to the job’s -**Configure** > Analysis node. The Analysis Properties page is opened from the Analysis Selection -page by either of the following options: +Configure analysis tasks through the Analysis Properties page. Navigate to the job’s +**Configure** > Analysis node. Open the Analysis Properties page from the Analysis Selection +page using either of the following options: - Select **Create Analysis** to add a new analysis task to a job - Select an existing analysis and click **Analysis Properties** to modify its configuration @@ -29,7 +29,7 @@ Analyzer. | Analysis Module | Description | | --------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- | | [AutoAction Analysis Module](/docs/accessanalyzer/12.0/admin/analysis/autoaction.md) | Performs a specified action at the conclusion of an analysis task’s execution | -| [Business Rules Analysis Module](/docs/accessanalyzer/12.0/admin/analysis/businessrules/overview.md) | Finds data that does not match user expectations for the target environment | +| [Business Rules Analysis Module](/docs/accessanalyzer/12.0/admin/analysis/businessrules/overview.md) | Finds data that doesn't match user expectations for the target environment | | [Change Detection Analysis Module](/docs/accessanalyzer/12.0/admin/analysis/changedetection/overview.md) | Notifies when a change occurs in the results of a job and identifies the location of the change | | [Notification Analysis Module](/docs/accessanalyzer/12.0/admin/analysis/notification/overview.md) | Sends notifications to specified recipients when a specified event occurs | | [SQLscripting Analysis Module](/docs/accessanalyzer/12.0/admin/analysis/sqlscripting.md) | Executes free-form SQL scripts | @@ -39,17 +39,17 @@ Analyzer. ## Executing Analyses -Analysis tasks execute automatically if enabled through the Analysis Selection page for jobs with -analysis modules configured. Analysis tasks can be enabled or disabled by selecting the checkbox -next to the analysis tasks. Analysis tasks execute in the order shown in the Analysis Selection -window. Tasks can be manually executed without running the job by right-clicking on the task and +Analysis tasks execute automatically if you enable them through the Analysis Selection page for jobs with +analysis modules configured. Enable or disable analysis tasks by selecting the checkbox +next to them. Analysis tasks execute in the order shown in the Analysis Selection +window. Manually execute tasks without running the job by right-clicking on the task and selecting **Execute Analyses** from the dropdown menu. ## Analysis Selection Page -Analysis tasks can be created, deleted, and configured through the Analysis Selection page. For jobs -with existing analysis tasks, the Analysis Selection page is used to change the order in which tasks -are run, as well as enabling or disabling tasks. +Create, delete, and configure analysis tasks through the Analysis Selection page. For jobs +with existing analysis tasks, use the Analysis Selection page to change the order in which tasks +run and to enable or disable them. ![Analysis Selection Page](/images/accessanalyzer/12.0/admin/analysis/analysisselectionpage.webp) @@ -61,8 +61,8 @@ The Analysis Selection page has the following options: - Analysis Configuration – Opens the configuration wizard for the analysis task - Select the checkbox next to an analysis task to enable it, or clear the checkbox to disable it - Move Up/Move Down – Moves the selected analysis tasks up or down the Analysis Selection task list. - Moving tasks up or down the list changes the order in which the task is run when the job is - executed. + Moving tasks up or down the list changes the order in which the task runs when the job + executes. :::note Tasks can be drag-and-dropped to change position in the list. @@ -76,8 +76,8 @@ The Analysis Selection page has the following options: ## Analysis Properties Page -Configure task properties through the Analysis Properties page. The Analysis Properties page is -accessed through the Analysis Selection page. +Configure task properties through the Analysis Properties page. Access the Analysis Properties page +through the Analysis Selection page. ![Analysis Properties Page](/images/accessanalyzer/12.0/admin/analysis/analysispropertiespage.webp) @@ -86,7 +86,7 @@ The Analysis Properties page has the following options: - Name – Name of the analysis task. Default names can be changed. - Description – Description of the analysis task. Analysis tasks for default solutions reference associate data tables. Descriptions for new tasks are blank by default. -- Analysis Module – Click the drop-down to select an analysis module for the task +- Analysis Module – Click the dropdown to select an analysis module for the task - Configure Analysis – Click to access the configuration wizard for the selected analysis module - ID – Unique identifying number of the analysis task. The database uses distinct IDs to distinguish between analysis tasks, even those with identical configurations. diff --git a/docs/accessanalyzer/12.0/admin/analysis/sqlscripting.md b/docs/accessanalyzer/12.0/admin/analysis/sqlscripting.md index 02772992a0..1db46a6067 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/sqlscripting.md +++ b/docs/accessanalyzer/12.0/admin/analysis/sqlscripting.md @@ -12,7 +12,7 @@ Use the SQLscripting analysis module to apply SQL scripting to the selected job. The SQLscripting analysis module evaluates the Access Analyzer user’s permission level to determine whether to allow the connected user to run the scripted command. Since this evaluation is based on -specific SQL database permissions and is not always under Access Analyzer’s control, some scripts +specific SQL database permissions and isn't always under Access Analyzer’s control, some scripts with correct syntax may fail due to insufficient permissions. The SQL Script Editor window has the following options: @@ -25,13 +25,13 @@ The SQL Script Editor window has the following options: - Syntax Check – Checks SQL script syntax - - Syntax Check does not identify logic errors, only instances where syntax is incorrect. Click + - Syntax Check doesn't identify logic errors, only instances where syntax is incorrect. Click **Syntax Check** to open the Script Errors window which identifies syntax errors. - - Syntax Check reports back syntax errors starting from the beginning of the script to the end. - Syntax Check does not return a list of errors. + - Syntax Check reports syntax errors starting from the beginning of the script to the end. + Syntax Check doesn't return a list of errors. -- Load file – Opens a File Explorer which can be used to navigate to a SQL file -- Save to File – Saves the currently configured script into a SQL file +- Load file – Opens a File Explorer to navigate to a SQL file +- Save to File – Saves the configured script into a SQL file - Undo – Undo the previous changes made to script (Ctrl+Z) - Redo – Redo the previous changes made to script (Ctrl+Y) - Cut – Cuts the highlighted script from the SQL script editor (Ctrl+X) @@ -41,9 +41,8 @@ The SQL Script Editor window has the following options: [Transact-SQL Reference](https://learn.microsoft.com/en-us/previous-versions/sql/sql-server-2005/ms189826(v=sql.90)) article -Click **Save and Close** to return to the Analysis Properties page. If no changes were made or -intended, it is best practice to click **Cancel** to close the SQL Script Editor wizard to ensure no -accidental changes are saved. +Click **Save and Close** to return to the Analysis Properties page. If you didn't make or intend any +changes, click **Cancel** to close the SQL Script Editor wizard so you don't save accidental changes. ## Parameters @@ -75,8 +74,8 @@ The parameters have the following properties: - Name – Name of the variable or table - Type – Type of variable or table - - String variables utilize a text string input - - Integers and floats are able to handle invalid inputs + - String variables use a text string input + - Integers and floats can handle invalid inputs - Boolean variables only take True/False input, in SQL they are 1/0 - Percentages only take whole numbers 0-100, converted to 0.0 to 1.0 in SQL - Temporary and Variable Tables @@ -98,9 +97,9 @@ The Edit table window has the following options: - If the name begins with a `#` it is a temporary table - If the name begins with a `@` it is a table variable - - In SQLCommand, these can be passed in as structured table parameters + - In SQLCommand, you can pass these in as structured table parameters - - If neither is specified, Access Analyzer assumes it is a temporary table + - If the name doesn't begin with either character, Access Analyzer assumes it's a temporary table - Description – Use the Parameters window to edit the description - Values – Add, edit, and remove values from the table @@ -110,8 +109,8 @@ The Edit table window has the following options: - Delete – Deletes the selected value - Up/Down – Changes the value position higher or lower -A CSV file is created under the job’s directory when a parameter table is added to the analysis. A -pre-existing CSV file can also be uploaded to populate the table. +Access Analyzer creates a CSV file under the job’s directory when you add a parameter table to the +analysis. You can also upload a pre-existing CSV file to populate the table. -Click **OK** to confirm changes to the table. If no changes were made or intended, click **Cancel** -to close the Edit Table window to ensure no accidental changes are saved. +Click **OK** to confirm changes to the table. If you didn't make or intend any changes, click +**Cancel** to close the Edit Table window so you don't save accidental changes. diff --git a/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/columns.md b/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/columns.md index 2fb10a44e0..7628522e25 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/columns.md +++ b/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/columns.md @@ -11,7 +11,7 @@ The Result Columns page lists the tables selected on the Input Select page. ![View and Table Creation Analysis Module wizard Result Columns page](/images/accessanalyzer/12.0/admin/analysis/sqlviewcreation/columns.webp) Expand the table to show its columns. Then, select the checkbox next to the column to include it in -the resulting table or view. If two data tables are being joined, the resulting table displays at +the resulting table or view. If you join two data tables, the resulting table displays at the bottom of the grid. Use the scroll bar to view any hidden tables or data points. The grid provides the following options for formatting the resulting table or view: @@ -21,14 +21,14 @@ The grid provides the following options for formatting the resulting table or vi - Add Column – Opens the New Trend Column window, where columns can be added to the table - Delete – Deletes a selected column - - Original columns cannot be deleted. Only columns that have been added by users can be deleted. + - You can't delete original columns. You can only delete columns that you added. -- Show All Columns/Hide Unchecked Columns – Hides rows that are not currently selected ,or if - columns are currently hidden, displays all columns in the table +- Show All Columns/Hide Unchecked Columns – Hides rows that aren't selected, or if + columns are hidden, displays all columns in the table - Checked – Selects data columns for inclusion in the resulting table or view - Column Name – Displays the data column name - Group Operation – Accesses the available group operations that can be applied to individual data - points. Click on a cell in this column to display the drop-down arrow. The following operations + points. Click a cell in this column to display the dropdown arrow. The following operations are available: - (none) @@ -43,7 +43,7 @@ The grid provides the following options for formatting the resulting table or vi column name on the materialized table or view. If applying a group operation, a default data label shows. To apply a custom label, click in the cell and enter the label. - Order By Operation – Accesses the available order-by operations that can be applied to individual - data points. Click on a cell in this column to display the drop-down arrow. The following + data points. Click a cell in this column to display the dropdown arrow. The following operations are available: - None @@ -51,7 +51,7 @@ The grid provides the following options for formatting the resulting table or vi - Descending :::note -If at least one columns is sorted by value, the **With ties** option is enabled on the +If you sort at least one column by value, Access Analyzer enables the **With ties** option on the Result Constraints page. See the [SQLViewCreation: Result Constraints](/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/resultconstraints.md) topic for additional information. ::: diff --git a/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/export.md b/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/export.md index afa63fe6a6..abe7142b63 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/export.md +++ b/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/export.md @@ -13,10 +13,10 @@ Use the Export settings page to specify data export settings. Select the **Export results data** checkbox to enable the settings. The following options control the file type and destination of the exported data: -- Format – Use the drop-down menu to select the file format of the exported data +- Format – Use the dropdown menu to select the file format of the exported data - - MS Excel file – Converts file to Microsoft Excel format. If Excel is not installed on the - console, a warning message shows and another export file format needs to be selected. + - MS Excel file – Converts file to Microsoft Excel format. If Excel isn't installed on the + console, a warning message shows, and you need to select another export file format. - CSV file – Converts file to Comma-Separated Values format. Includes the option to compress the file to a zip file. - ML file – Converts file to Extensible Markup Language format. Includes the option to compress @@ -29,4 +29,4 @@ the file type and destination of the exported data: **Location** field. To specify a different location, clear the checkbox and edit the **Location** field. -Once the options are selected, click **Next**. +After selecting the options, click **Next**. diff --git a/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/filter.md b/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/filter.md index 09023bbcf7..05983e09ba 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/filter.md +++ b/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/filter.md @@ -11,7 +11,7 @@ Use this page to add custom filters to the table using the Filter Builder. ![View and Table Creation Analysis Module wizard Filter page](/images/accessanalyzer/12.0/admin/analysis/sqlviewcreation/filter.webp) Filters reduce the amount of data visible in a column imported to the resulting table or view. By -default, when the filter page is blank, all the data within each column is included. Use the +default, when the filter page is blank, Access Analyzer includes all the data within each column. Use the following options to add and remove filters: - Edit – Opens the Filter window diff --git a/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/input.md b/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/input.md index 5e296077a0..d7358e12b4 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/input.md +++ b/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/input.md @@ -11,16 +11,16 @@ aggregate into a resulting table or view. ![View and Table Creation Analysis Module wizard Input Source page](/images/accessanalyzer/12.0/admin/analysis/sqlviewcreation/input.webp) -At the first drop-down, select a table. The drop-down lists on this page are determined by the -selection made on the Input Scope page. To join or aggregate data from two tables, select a second -table at the second drop-down menu. To remove the second table from the field, click the **X** +At the first dropdown, select a table. The selection you make on the Input Scope page determines +the dropdown lists on this page. To join or aggregate data from two tables, select a second +table at the second dropdown menu. To remove the second table from the field, click the **X** button. :::note -It is important to choose tables that are compatible with one another or share similar +Choose tables that are compatible with one another or share similar columns. ::: -When the two sources of data are selected, click **Next** to create a joint column within the +After you select the two sources of data, click **Next** to create a joint column within the resulting table or view. diff --git a/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/inputscope.md b/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/inputscope.md index c7fdc0086e..664b19ff89 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/inputscope.md +++ b/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/inputscope.md @@ -11,7 +11,7 @@ available for selection on the subsequent pages. ![View and Table Creation Analysis Module wizard Input Selection page](/images/accessanalyzer/12.0/admin/analysis/sqlviewcreation/inputscope.webp) -Select the source data to be used from the following options: +Select the source data to use from the following options: - Tables from Current Job – Targets all tables generated by the current job within the SQL Server database diff --git a/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/joincolumns.md b/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/joincolumns.md index d8932af576..b8c387759c 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/joincolumns.md +++ b/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/joincolumns.md @@ -7,8 +7,8 @@ sidebar_position: 30 # SQLViewCreations: Join Columns Use the Join Columns page to select a column from each source table to join together on the -resulting table or view. The options on this page are only enabled if two tables are selected on the -Input Source page. +resulting table or view. Access Analyzer only enables the options on this page if you select two +tables on the Input Source page. :::note The SQLViewCreation analysis module can join two tables, using a simple equi-join @@ -21,17 +21,18 @@ predicates, use the SQLscripting analysis module. See the ![View and Table Creation Analysis Module wizard Join Columns page](/images/accessanalyzer/12.0/admin/analysis/sqlviewcreation/joincolumns.webp) Use the **Table 1 join property** and **Table 2 join property** fields to select join predicates -from both tables. Join predicates are columns containing analogous values that are used to match +from both tables. Join predicates are columns containing analogous values that match records in referenced tables. Next, specify how to join these tables. To automatically select the appropriate join type, select one or more of the checkboxes. The selection in the **Join Type** field updates based on user selections. -To manually select, use the **Join Type** field. The selection here may update the above checkboxes. +To manually select, use the **Join Type** field. The selection here may update the checkboxes you +selected to automatically choose the join type. The following options are available: -- Join Type – Select a join type from the drop-down: +- Join Type – Select a join type from the dropdown: :::note Left is the first table referenced, right is the second table. @@ -48,7 +49,7 @@ The following options are available: :::note The join property is the column found within both tables. The two columns can have different names. However, in the results set, everywhere a value in the first column matches the -value in the second column, rows from the respective tables are joined together. +value in the second column, Access Analyzer joins rows from the respective tables together. ::: diff --git a/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/overview.md b/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/overview.md index 3e65e4c10e..ce101904b3 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/overview.md +++ b/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/overview.md @@ -6,8 +6,9 @@ sidebar_position: 60 # SQLViewCreation Analysis Module -The SQLViewCreation analysis module provides the ability to create new views or tables that are used -in Access Analyzer actions and reports. These views or tables are re-created during job execution. +The SQLViewCreation analysis module lets you create new views or tables for use +in Access Analyzer actions and reports. Access Analyzer re-creates these views or tables during job +execution. :::warning Consider the impact on storage and performance when choosing to create views versus @@ -18,7 +19,7 @@ tables. Tables require more storage space in the database. ## Configuration This analysis module provides the View and Table Creation Analysis Module wizard to assist in -configuring the module. Before the wizard, collect the desired data for manipulation. +configuring the module. Before the wizard, collect the data you want to manipulate. The wizard contains the following pages: diff --git a/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/result.md b/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/result.md index 24fd2c6cf3..51cfd97a6c 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/result.md +++ b/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/result.md @@ -16,9 +16,9 @@ two sourced tables. Select from the following two options: - Create Table – Creates a table output for the resulting dataset - Create View – Creates a view output for the resulting dataset -A default name of `SA_[job name]_Result` is provided in the name field. You can customize this name -for the resulting table or view. +Access Analyzer provides a default name of `SA_[job name]_Result` in the name field. You can +customize this name for the resulting table or view. -The name must start with `SA` to be recognized as a Access Analyzer table or view. +The name must start with `SA` for Access Analyzer to recognize it as a table or view. After selecting the resulting table or view’s visual representation and name, click **Next**. diff --git a/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/resultconstraints.md b/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/resultconstraints.md index 1ea52a92dd..7bcfcb2323 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/resultconstraints.md +++ b/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/resultconstraints.md @@ -10,7 +10,7 @@ Use the Result Constraints page to impose restraints on the dataset. ![View and Table Creation Analysis Module wizard Result constraints page](/images/accessanalyzer/12.0/admin/analysis/sqlviewcreation/resultconstraints.webp) -Select one of the following options to choose if and how much data should be returned: +Select one of the following options to choose whether and how much data to return: - Duplicate rows can appear in the result set - Only unique rows can appear in the result set @@ -18,11 +18,11 @@ Select one of the following options to choose if and how much data should be ret of measurement to return for the rows that appear in the resulting table or view - With ties – Include all instances of identical values in the sorted columns with the results. - To include only one instance of identical values, do not select this option.. See the + To include only one instance of identical values, don't select this option.. See the [With Ties Example](#with-ties-example) topic for additional information. :::note - This field is enabled by sorting at least one column in the table by value (for + You enable this field by sorting at least one column in the table by value (for SQL, only a sorted column can contain ties). To sort columns, use the **Order By Operation** field on the Columns page. See the [SQLViewCreations: Columns](/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/columns.md) topic for additional information. @@ -39,8 +39,8 @@ Consider a table that has ten rows with one repeating entry under the value colu ![cid:image025.webp@01D4CF74.8A56D750](/images/accessanalyzer/12.0/admin/analysis/sqlviewcreation/examplereduced.webp) -If the table is sorted by the value column in ascending order and the **Return only** option is set -to **40 percent**, then there should be four rows visible in the resulting table or view output. +If you sort the table by the value column in ascending order and set the **Return only** option to +**40 percent**, four rows are visible in the resulting table or view output. ![cid:image026.webp@01D4CF74.8A56D750](/images/accessanalyzer/12.0/admin/analysis/sqlviewcreation/examplereducedwithties.webp) @@ -49,7 +49,7 @@ fifth, selecting the **With ties** option returns the first three rows as well a and fifth rows for a total of five rows. :::note -If sorting multiple columns, **With ties** evaluates all sorted columns to determine ties +If you sort multiple columns, **With ties** evaluates all sorted columns to determine ties between columns with the same inputs. ::: diff --git a/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/resultsample.md b/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/resultsample.md index 49afeec34c..7e5ac6fb21 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/resultsample.md +++ b/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/resultsample.md @@ -11,10 +11,10 @@ Use this page to preview a sampling of the completed data manipulation. ![View and Table Creation Analysis Module wizard Result Sample page](/images/accessanalyzer/12.0/admin/analysis/sqlviewcreation/resultsample.webp) Click **Show Preview** to populate the window with the selections from the previous pages. If the -window does not populate, check the configurations for errors and try again. +window doesn't populate, check the configurations for errors and try again. :::note -The **Show Preview** option does not always apply the filter conditions specified within +The **Show Preview** option doesn't always apply the filter conditions specified within the wizard, but the resulting table or view applies all filters. ::: diff --git a/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/summary.md b/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/summary.md index 91fb91144e..77315a1f31 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/summary.md +++ b/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/summary.md @@ -10,6 +10,5 @@ This page provides an overview of all the settings configured in the wizard. ![View and Table Creation Analysis Module wizard Summary page](/images/accessanalyzer/12.0/admin/analysis/sqlviewcreation/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the View and Table Creation Analysis Module wizard to ensure that no -accidental clicks are saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** to +close the View and Table Creation Analysis Module wizard so you don't save accidental changes. diff --git a/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/timewindow.md b/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/timewindow.md index ba464f53aa..44b6c02cfb 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/timewindow.md +++ b/docs/accessanalyzer/12.0/admin/analysis/sqlviewcreation/timewindow.md @@ -18,8 +18,8 @@ data was collected: two separate Access Analyzer Consoles using tables generated by the same job. :::note - This section is enabled after selecting **All Access Analyzer Tables** or **All tables - in the database** on the Input Scope page. + Access Analyzer enables this section after you select **All Access Analyzer Tables** or **All + tables in the database** on the Input Scope page. ::: @@ -28,5 +28,5 @@ data was collected: - Data from this Access Analyzer Console only – Uses only data from the Access Analyzer Console generating the current analysis module -- Time Window – Select a time window for each table in the analysis. The drop-down menu selections +- Time Window – Select a time window for each table in the analysis. The dropdown menu selections vary based on each table's history settings. diff --git a/docs/accessanalyzer/12.0/admin/analysis/vbscripting.md b/docs/accessanalyzer/12.0/admin/analysis/vbscripting.md index ab5326ac60..2359c697f7 100644 --- a/docs/accessanalyzer/12.0/admin/analysis/vbscripting.md +++ b/docs/accessanalyzer/12.0/admin/analysis/vbscripting.md @@ -16,13 +16,13 @@ The VBScript Editor has the following options: - Save and Close – Saves the script and closes the window - Syntax Check – Checks VB script syntax - - Syntax Check does not identify logic errors, only instances where syntax is incorrect. Click + - Syntax Check doesn't identify logic errors, only instances where syntax is incorrect. Click **Syntax Check** to open the Script Errors window which identifies syntax errors. - - Syntax Check reports back syntax errors starting from the beginning of the script to the end. - Syntax Check does not return a list of errors. + - Syntax Check reports syntax errors starting from the beginning of the script to the end. + Syntax Check doesn't return a list of errors. -- Load file – Opens a File Explorer which can be used to navigate to a VBS file -- Save to File – Saves the currently configured script into a VBS file +- Load file – Opens a File Explorer to navigate to a VBS file +- Save to File – Saves the configured script into a VBS file - Undo – Undo the previous changes made to script (Ctrl+Z) - Redo – Redo the previous changes made to script (Ctrl+Y) - Cut – Cuts the highlighted script from the VB script editor (Ctrl+X) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/activedirectory/directoryscope.md b/docs/accessanalyzer/12.0/admin/datacollector/activedirectory/directoryscope.md index e11eb5a4be..01982c2c22 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/activedirectory/directoryscope.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/activedirectory/directoryscope.md @@ -21,5 +21,5 @@ The Directory Scope page has the following options: - Connect – Connects to the target domain to provide a list of directories - Add – Add an OU to the query scope - Remove – Removes an OU from the query scope -- Scope – List of OUs to be scanned +- Scope – List of OUs to scan - Sub tree – Sub-OUs included in the scan if checked diff --git a/docs/accessanalyzer/12.0/admin/datacollector/activedirectory/options.md b/docs/accessanalyzer/12.0/admin/datacollector/activedirectory/options.md index c0fc49e665..0aa47d1a18 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/activedirectory/options.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/activedirectory/options.md @@ -15,11 +15,11 @@ The Options page provides format options for returned data. It is a wizard page - Return data as collected - Return data in a separate row for each property set in the following group - - Select the group from the drop-down menu + - Select the group from the dropdown menu - Return each value of the following property in a separate row - - Select the property from the drop-down menu + - Select the property from the dropdown menu - How to return multi-valued properties in one cell – Select from the following options: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/activedirectory/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/activedirectory/overview.md index 3cd85c6e0e..d4797ab36f 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/activedirectory/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/activedirectory/overview.md @@ -6,9 +6,9 @@ sidebar_position: 20 # ActiveDirectory Data Collector -The ActiveDirectory Data Collector audits objects published in Active Directory. It has been -preconfigured within the Active Directory Solution. Both this data collector and the solution are -available with a special Access Analyzer license. See the +The ActiveDirectory Data Collector audits objects published in Active Directory. The Active +Directory Solution includes this data collector preconfigured. Both this data collector and the +solution are available with a special Access Analyzer license. See the [Active Directory Solution](/docs/accessanalyzer/12.0/solutions/activedirectory/overview.md) topic for additional information. @@ -42,5 +42,5 @@ which contains the following wizard pages: ![Active Directory Data Collector Wizard Welcome page](/images/accessanalyzer/12.0/admin/datacollector/activedirectory/welcome.webp) -The Welcome page can be hidden by selecting the **Do not display this page the next time** checkbox -when the wizard is open and configuration settings are saved. +To hide the Welcome page, select the **Don't display this page the next time** checkbox while the +wizard is open, then save the configuration settings. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/activedirectory/results.md b/docs/accessanalyzer/12.0/admin/datacollector/activedirectory/results.md index 6ed7755745..bae1ea9869 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/activedirectory/results.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/activedirectory/results.md @@ -6,11 +6,11 @@ sidebar_position: 30 # ActiveDirectory: Results -The Results page is where Active Directory object properties to be gathered are selected. It is a -wizard page for all categories. +Use the Results page to select the Active Directory object properties to gather. This wizard page +appears for all categories. ![Active Directory Data Collector Wizard Results page](/images/accessanalyzer/12.0/admin/datacollector/activedirectory/results.webp) -Properties can be selected individually or the **Check all**, **Uncheck all**, and **Reset to -defaults** buttons can be used. All selected properties are gathered. Available properties vary -based on the category selected. +Select properties individually, or use the **Check all**, **Uncheck all**, and **Reset to +defaults** buttons. The data collector gathers all selected properties. Available properties vary +based on the category you select. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/activedirectory/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/activedirectory/summary.md index 1081baeb09..a839161c42 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/activedirectory/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/activedirectory/summary.md @@ -6,10 +6,10 @@ sidebar_position: 50 # ActiveDirectory: Summary -The Summary page displays a summary of the configured query. It wizard page for all categories. +The Summary page displays a summary of the configured query. It is a wizard page for all categories. ![Active Directory Data Collector Wizard Summary page](/images/accessanalyzer/12.0/admin/datacollector/activedirectory/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Active Directory Data Collector Wizard to ensure that no accidental -clicks are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** to close +the Active Directory Data Collector Wizard instead. This ensures the wizard doesn't save any +accidental clicks. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/adactivity/category.md b/docs/accessanalyzer/12.0/admin/datacollector/adactivity/category.md index 19fa9b97c2..a2d9c16f0c 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/adactivity/category.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/adactivity/category.md @@ -6,7 +6,7 @@ sidebar_position: 20 # ADActivity: Category -Use the Category page to identify how activity data is retrieved or removed. +Use the Category page to identify how the data collector retrieves or removes activity data. ![Active Directory Activity DC wizard Category page](/images/accessanalyzer/12.0/admin/datacollector/adactivity/category.webp) @@ -14,6 +14,6 @@ The ADActivity Data Collector Category page contains three query categories: - Import From SAM – Import activity from a Netwrix Activity Monitor archive - Import From Share – Import activity from a network share -- Remove Tables – Removes all tables and views from SQL Server database. This option is designed for - troubleshooting. When this option is selected, the next wizard page is the Summary page. See the +- Remove Tables – Removes all tables and views from SQL Server database. Use this option for + troubleshooting. When you select this option, the next wizard page is the Summary page. See the [Clear ADActivity Tables](/docs/accessanalyzer/12.0/admin/datacollector/adactivity/cleartables.md) topic for more information. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/adactivity/cleartables.md b/docs/accessanalyzer/12.0/admin/datacollector/adactivity/cleartables.md index bb51cd0edb..a2499f883b 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/adactivity/cleartables.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/adactivity/cleartables.md @@ -6,8 +6,8 @@ sidebar_position: 80 # Clear ADActivity Tables -Sometimes when troubleshooting an ADActivity issue, it becomes necessary to clear the standard -reference tables. Follow the steps. +When troubleshooting an ADActivity issue, you sometimes need to clear the standard reference +tables. Follow these steps. **Step 1 –** Create a new job and assign a query using the ADActivity Data Collector. @@ -19,13 +19,13 @@ Tables** category task. ![Active Directory Activity DC wizard Results page for Remove Tables category](/images/accessanalyzer/12.0/admin/datacollector/adactivity/resultsremovetables.webp) **Step 3 –** Click **Next** to go to the Results page. Optionally, select the **Success** checkbox -to display a confirmation of successful removal in the results after the job is run. +to display a confirmation of successful removal in the results after the job runs. **Step 4 –** Click **Next** and then Click **Finish** to close the Active Directory Activity DC Wizard. Click **OK** to close the Query Properties window. :::warning -When the job is run, all of the ADActivity standard reference tables are removed from +When you run the job, it removes all ADActivity standard reference tables from the database. ::: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/adactivity/connection.md b/docs/accessanalyzer/12.0/admin/datacollector/adactivity/connection.md index 1986f5964e..7584abdeba 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/adactivity/connection.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/adactivity/connection.md @@ -6,7 +6,7 @@ sidebar_position: 30 # ADActivity: SAM Connection -The SAM connection page is where the port number is configured to send Active Directory data from +Use the SAM connection page to configure the port number for sending Active Directory data from Netwrix Activity Monitor. It is a wizard page for the category of: - Import from SAM @@ -24,14 +24,13 @@ archive via an API Server: scan to continue - Test SAM host – Enter the Activity Monitor API server name in a qualified domain name format. - Click Connect to test the connection. A successful result populates the section underneath with a - Refresh token. -- Exclude – Select archives to be ignored by the Active Directory Activity DC scan + Click Connect to test the connection. A successful connection displays a Refresh token. +- Exclude – Select archives for the Active Directory Activity DC scan to ignore :::warning Save the Refresh token to a Text Editor for later use. The Refresh token resets - each time the Test SAM host option is connected to. It must be replaced in the Connection - profile if it is regenerated. + each time you use the Test SAM host option to connect. If it regenerates, replace it in the + Connection profile. ::: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/adactivity/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/adactivity/overview.md index decca5386b..55fc6850c8 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/adactivity/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/adactivity/overview.md @@ -7,8 +7,9 @@ sidebar_position: 30 # ADActivity Data Collector The ADActivity Data Collector integrates with the Netwrix Activity Monitor by reading the Active -Directory activity log files. It has been preconfigured within the Active Directory Solution. Both -this data collector and the solution are available with a special Access Analyzer license. See the +Directory activity log files. The Active Directory Solution includes this data collector +preconfigured. Both this data collector and the solution are available with a special Access +Analyzer license. See the [Active Directory Solution](/docs/accessanalyzer/12.0/solutions/activedirectory/overview.md) topic for additional information. @@ -29,8 +30,8 @@ information. ## ADActivity Query Configuration -The ADActivity Data Collector is configured through the Active Directory Activity DC wizard, which -contains the following wizard pages, which change based up on the query category selected: +The ADActivity Data Collector is configured through the Active Directory Activity DC wizard. The +wizard pages it contains change based on the query category you select: - [ADActivity: Category](/docs/accessanalyzer/12.0/admin/datacollector/adactivity/category.md) - [ADActivity: SAM Connection](/docs/accessanalyzer/12.0/admin/datacollector/adactivity/connection.md) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/adactivity/results.md b/docs/accessanalyzer/12.0/admin/datacollector/adactivity/results.md index 88e2f74072..1be6560d5a 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/adactivity/results.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/adactivity/results.md @@ -6,10 +6,11 @@ sidebar_position: 60 # ADActivity: Results -The Results page is where the properties to be gathered are selected. It is a wizard page for all of -the categories. +Use the Results page to select the properties to gather. This wizard page appears for all +categories. ![Active Directory Activity DC wizard Results page](/images/accessanalyzer/12.0/admin/datacollector/adactivity/results.webp) -Properties can be selected individually or the **Select All** and **Clear All** buttons can be used. -All selected properties are gathered. Available properties vary based on the category selected. +Select properties individually, or use the **Select All** and **Clear All** buttons. The data +collector gathers all selected properties. Available properties vary based on the category you +select. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/adactivity/scope.md b/docs/accessanalyzer/12.0/admin/datacollector/adactivity/scope.md index b316f2ffa2..1972a1951f 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/adactivity/scope.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/adactivity/scope.md @@ -14,21 +14,21 @@ the categories of: ![Active Directory Activity DC wizard Scoping and Retention page](/images/activitymonitor/8.0/config/activedirectory/scope.webp) -The Timespan is defined according to the following two elements: +Two elements define the Timespan: -- Relative Timespan – Number of days AD Activity is collected when the scan is run +- Relative Timespan – Number of days the scan collects AD Activity when it runs - Absolute Timespan – Set the date range for the scan to collect AD Activity :::info - The threshold should be set for after the Netwrix Activity Monitor collects - and archives its data but before they are deleted after a set retention period. + Set the threshold to a point after the Netwrix Activity Monitor collects + and archives its data but before the set retention period deletes it. ::: -The Retention section sets what event type is collected and how many days Access Analyzer keeps the +The Retention section sets which event types Access Analyzer collects and how many days it keeps the collected data in its SQL database. The table has the following columns: -- Event Type – The event type that may be enabled for the scan. The event types are: +- Event Type – The event type you can enable for the scan. The event types are: - AD Change - AD Replication @@ -37,4 +37,4 @@ collected data in its SQL database. The table has the following columns: - Process Injection - Days to Store – Specify the number of days to store the collected data for the event type -- Enable Collection – When selected, the corresponding event type is collected +- Enable Collection – When you select this checkbox, the scan collects the corresponding event type diff --git a/docs/accessanalyzer/12.0/admin/datacollector/adactivity/share.md b/docs/accessanalyzer/12.0/admin/datacollector/adactivity/share.md index 239917e88e..325c3c29be 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/adactivity/share.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/adactivity/share.md @@ -13,14 +13,14 @@ of: ![Active Directory Activity DC wizard Share settings page](/images/activitymonitor/8.0/config/activedirectory/share.webp) -The following connection setting can be configured to connect to the AD activity archives that must -be located on a Domain Controller share: +Configure the following connection setting to connect to the AD activity archives, which must +reside on a Domain Controller share: -- UNC Path – Enter the path of the share that stores AD Activity from the AD Agent(s). The ellipsis - (**…**) opens a file explorer where the path can be navigated to and selected. +- UNC Path – Enter the path of the share that stores AD Activity from the AD Agents. The ellipsis + (**…**) opens a file explorer where you can navigate to and select the path. - - _Remember,_ all AD Agent logs must be archived to this location or the AD Activity data is not - queried by Access Analyzer + - _Remember,_ you must archive all AD Agent logs to this location, or Access Analyzer won't + query the AD Activity data - Include Sub-Directories – Select to include sub-directories on the targeted share. Use this option if there are multiple archives in the same location. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/adactivity/standardtables.md b/docs/accessanalyzer/12.0/admin/datacollector/adactivity/standardtables.md index 383c229130..07b9cbcf0c 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/adactivity/standardtables.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/adactivity/standardtables.md @@ -10,7 +10,7 @@ The ADActivity Data Collector gathers essential user and group activity informat reference tables. Unlike other Access Analyzer data collectors, the ADActivity Data Collector writes data to these tables regardless of the job executing the query. -These tables and their associated views are outlined below: +The following table describes these tables and their associated views: | Table | Details | | -------------------------------- | --------------------------------------------------------------------- | @@ -35,10 +35,9 @@ These tables and their associated views are outlined below: | SA_ADActivity_Sources | Contains lists of sources of activity events | | SA_ADActivity_SPNs | Contains a unique identifier for each logon account | -Views are the recommended way for Access Analyzer users to obtain the information gathered by the -ADActivity Data Collector. They contain additional information for building queries easily. The -following is an explanation of the corresponding views created for some of the tables generated by -the ADActivity Data Collector: +Views are the recommended way for Access Analyzer users to obtain the information the ADActivity +Data Collector gathers. They contain additional information for building queries. The following +table explains the views the ADActivity Data Collector creates for some of its tables: | Views | Details | | -------------------------------------------- | ------------------------------------------------------------------------ | diff --git a/docs/accessanalyzer/12.0/admin/datacollector/adactivity/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/adactivity/summary.md index 5b0a36fb1b..bd11c849ff 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/adactivity/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/adactivity/summary.md @@ -6,11 +6,11 @@ sidebar_position: 70 # ADActivity: Summary -The Summary page is where configuration settings are summarized. It is a wizard page for all of the +The Summary page summarizes the configuration settings. This wizard page appears for all categories. ![Active Directory Activity DC wizard Summary page](/images/accessanalyzer/12.0/admin/datacollector/adactivity/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Active Directory Activity DC wizard to ensure that no accidental -clicks are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** to close +the Active Directory Activity DC wizard instead. This ensures the wizard doesn't save any +accidental clicks. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/adinventory/category.md b/docs/accessanalyzer/12.0/admin/datacollector/adinventory/category.md index 0489456a4e..006e6339e6 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/adinventory/category.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/adinventory/category.md @@ -16,15 +16,15 @@ The categories include the following tasks: database, creating the standard reference tables. This task is also responsible for maintaining the schema for tables and views. This is the standard option for this data collector. - Update SQL Indexes – Reorganizes or rebuilds indexes in the Access Analyzer SQL storage database. - When this option is selected, the next wizard page is the Results page. -- Remove Tables – Removes all tables and views from SQL Server database. This option is designed for - troubleshooting. When this option is selected, the next wizard page is the Summary page. See the + When you select this option, the next wizard page is the Results page. +- Remove Tables – Removes all tables and views from SQL Server database. Use this option for + troubleshooting. When you select this option, the next wizard page is the Summary page. See the [Clear ADInventory Tables](/docs/accessanalyzer/12.0/admin/datacollector/adinventory/cleartables.md) topic for more information. - Drop Domain – Remove host domain related data from SQL server :::note The Scan Active Directory category is the pre-configured setting for the .Active Directory Inventory Job Group. Therefore, accessing the Active Directory Inventory DC Wizard from the query -within that job group does not display the Category wizard page. +within that job group doesn't display the Category wizard page. ::: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/adinventory/cleartables.md b/docs/accessanalyzer/12.0/admin/datacollector/adinventory/cleartables.md index 57ce3005e5..7a8a62b49c 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/adinventory/cleartables.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/adinventory/cleartables.md @@ -10,8 +10,7 @@ Sometimes when troubleshooting an ADInventory issue, it becomes necessary to cle reference tables. Follow the steps. :::warning -Be careful when using this query task. It will result in the deletion of collected -data. +Be careful when using this query task. It deletes collected data. ::: @@ -25,7 +24,7 @@ Tables** category task. **Step 3 –** Click **Next** and then **Finish** to close the Active Directory Inventory DC Wizard. Click **OK** to close the Query Properties window. -When the job is run, all of the ADInventory standard reference tables are removed from the database. +When you run the job, it removes all ADInventory standard reference tables from the database. :::warning Never leave the query task selected after job execution. Accidental data loss can @@ -34,6 +33,6 @@ occur. :::tip -Remember, this job deletes data from the Access Analyzer database. Check the job has been -configured correctly prior to job execution. +Remember, this job deletes data from the Access Analyzer database. Check that you configured the +job correctly before running it. ::: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/adinventory/customattributes.md b/docs/accessanalyzer/12.0/admin/datacollector/adinventory/customattributes.md index bab5916b69..df589ff665 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/adinventory/customattributes.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/adinventory/customattributes.md @@ -6,9 +6,9 @@ sidebar_position: 70 # ADInventory: Custom Attributes -The Custom Attributes page provides ability to add Active Directory attributes that are unique to -the environment or not collected by default to be gathered. It is a wizard page for the category of -Scan Active Directory. +Use the Custom Attributes page to add Active Directory attributes that are unique to your +environment or that Access Analyzer doesn't collect by default. This wizard page appears for the +Scan Active Directory category. The [Standard Reference Tables & Views for the ADInventory Data Collector](/docs/accessanalyzer/12.0/admin/datacollector/adinventory/standardtables.md) topic provides information on what is collected by default. Custom attributes added on this page are @@ -23,44 +23,43 @@ The Custom Attribute is defined according to the following three elements: - Attribute Name – As listed within Active Directory Use the **Add**, **Edit**, and **Remove** buttons at the bottom of the window to configure the -custom attributes to be gathered by the scan. See the +custom attributes for the scan to gather. See the [Manually Add Custom Attributes](#manually-add-custom-attributes) topic for additional information. The **Import** button opens the Custom Attributes Import Wizard. See the [Custom Attributes Import Wizard](#custom-attributes-import-wizard) topic for additional information. -Microsoft Active Directory Schema is detailed in the Microsoft +For details on the Microsoft Active Directory Schema, see the Microsoft [Active Directory Schema](https://learn.microsoft.com/en-gb/windows/win32/adschema/active-directory-schema) article. #### Manually Add Custom Attributes The **Add** and **Edit** buttons on the Custom Attributes page open the Custom Attribute window. -Follow the steps to manually add custom attributes. +To manually add custom attributes: **Step 1 –** On the Custom Attributes page of the Active Directory Inventory DC Wizard, click **Add**. The Custom Attribute window opens. ![Custom Attribute window](/images/accessanalyzer/12.0/admin/datacollector/adinventory/customattributesadd.webp) -**Step 2 –** Enter the **Domain Filter**. This can be entered either as the short domain name or the -fully qualified domain name. +**Step 2 –** Enter the **Domain Filter** as either the short domain name or the fully qualified +domain name. -**Step 3 –** Select the checkbox for the desired **Object Class**. +**Step 3 –** Select the checkbox for the **Object Class** you want. **Step 4 –** Enter the **Attribute Name** as it appears in Active Directory. -**Step 5 –** Click **OK**. The Custom Attribute window closes and the specified attribute is added -in the Custom Attributes page. +**Step 5 –** Click **OK**. The Custom Attribute window closes and adds the specified attribute to +the Custom Attributes page. -Repeat this process until all desired Custom Attributes have been included. +Repeat this process until you've added all the custom attributes you want. #### Custom Attributes Import Wizard -The Custom Attributes Import Wizard is used to import a list of custom attributes into the -ADInventory Data Collector configurations. Follow the steps to use the Custom Attributes Import -Wizard. +The Custom Attributes Import Wizard imports a list of custom attributes into the ADInventory Data +Collector configurations. To use the Custom Attributes Import Wizard: **Step 1 –** On the Custom Attributes page of the Active Directory Inventory DC Wizard, click **Import**. The Custom Attribute Import Wizard opens. @@ -68,25 +67,25 @@ Wizard. ![Custom Attributes Import Wizard Credentials page](/images/accessanalyzer/12.0/admin/datacollector/adinventory/customattributesimportcredentials.webp) **Step 2 –** On the Credentials page, identify a domain either by entering one manually or selecting -one from the **Domain Name** drop-down menu which displays a list of domains trusted by the one in -which the Access Analyzer Console server resides. Then set the credentials for reading the +one from the **Domain Name** dropdown menu, which displays a list of domains that the domain +hosting the Access Analyzer Console server trusts. Then set the credentials for reading the attributes list from the domain: - Authenticate as the logged in user – Applies the user account running Access Analyzer -- Use the following credentials to authenticate – Applies the account supplied in the **User Name** - and **Password** fields +- Use the following credentials to authenticate – Applies the account you supply in the **User + Name** and **Password** fields Click **Next** to continue. ![Custom Attributes Import Wizard Attributes page](/images/accessanalyzer/12.0/admin/datacollector/adinventory/customattributesimportattributes.webp) -**Step 3 –** The wizard populates available attributes from the domain specified on the Attributes -page. Expand the desired object class and select the checkboxes for the custom attributes to be -imported. Then click **Next**. +**Step 3 –** The wizard populates available attributes from the domain you specify on the Attributes +page. Expand the object class you want and select the checkboxes for the custom attributes to +import. Then click **Next**. ![Custom Attributes Import Wizard Summary page](/images/accessanalyzer/12.0/admin/datacollector/adinventory/customattributesimportsummary.webp) **Step 4 –** On the Summary page, click **Finish**. -The selected attributes are added on the Custom Attributes page of the Active Directory Inventory DC -Wizard. +The wizard adds the selected attributes to the Custom Attributes page of the Active Directory +Inventory DC Wizard. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/adinventory/domains.md b/docs/accessanalyzer/12.0/admin/datacollector/adinventory/domains.md index f4d4b63004..4d58a73e28 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/adinventory/domains.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/adinventory/domains.md @@ -6,7 +6,7 @@ sidebar_position: 40 # ADInventory: Domains -The Domains page removes host domain-related data from the SQL server for the selected domains. +The Domains page removes host domain-related data from the SQL server for the domains you select. ![Active Directory Inventory DC Wizard Domains page](/images/accessanalyzer/12.0/admin/datacollector/adinventory/domains.webp) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/adinventory/indexupdateoptions.md b/docs/accessanalyzer/12.0/admin/datacollector/adinventory/indexupdateoptions.md index 3f16807f46..e41f0a905e 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/adinventory/indexupdateoptions.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/adinventory/indexupdateoptions.md @@ -6,8 +6,8 @@ sidebar_position: 60 # ADInventory: Index Update Options -Configure options for maintaining SQL Server indexes while running queries using the Index Update -Options page. +Use the Index Update Options page to configure options for maintaining SQL Server indexes +while running queries. ![Active Directory Inventory DC Wizard Index Update Options page](/images/accessanalyzer/12.0/admin/datacollector/adinventory/indexupdateoptions.webp) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/adinventory/options.md b/docs/accessanalyzer/12.0/admin/datacollector/adinventory/options.md index e2b92a053d..24a69c802a 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/adinventory/options.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/adinventory/options.md @@ -19,18 +19,18 @@ The Options page has the following configuration options: - Ignore certificate errors? (For testing only) – Ignores untrusted certificate authority errors and allows the scan to continue. This option is for testing purposes only. -- Collect SID History from domain migrations – During a domain migration, the new infrastructure is - created alongside the old infrastructure. The old account SID is typically added to the SID - history attribute for the new account. The option to collect SID history is made available within - the ADInventory Data Collector to assist resolving SIDs for domain migrations. +- Collect SID History from domain migrations – During a domain migration, administrators create new + infrastructure alongside the old infrastructure. The migration process typically adds the old + account SID to the SID history attribute for the new account. The ADInventory Data Collector + provides an option to collect SID history to help resolve SIDs for domain migrations. - Collect only updates since the last scan (recommended) – Default setting for differential - scanning. The updates collected are any changes to: group membership, attributes on user objects, - attributes on group objects, and so on. + scanning. The updates the scan collects include any changes to: group membership, attributes on + user objects, attributes on group objects, and so on. - Track changes into Change tracking tables – Records all changes since the last scan in separate tables - - Limit Last Logon TimeStamp Changes – When selected, changes to the Last Logon TimeStamp - Attribute are not recorded + - Limit Last Logon TimeStamp Changes – When you select this option, the scan doesn't record + changes to the Last Logon TimeStamp attribute :::info If tracking changes, use the Limit Last Logon TimeStamp Changes option. @@ -40,16 +40,15 @@ The Options page has the following configuration options: - Number of days you want to keep changes in the database – Use the arrow buttons or manually enter a number to set the number of days to keep changes - Target previously scanned domain controller – Collects updated information from the last - domain controller targeted to reduce the scan time. Below are some considerations: + domain controller the scan targeted, to reduce scan time. Consider the following: - If the last domain controller is unavailable, the targeted domain controller is the specified domain controller from the host list. If using the domain name, it attempts to find the last scanned domain controller. - - If that domain controller is determined to be unavailable, then it runs a full scan on the + - If the scan determines that domain controller is unavailable, it runs a full scan on the next domain controller that responds. Then, it will scan the new domain controller for - changes going forward. + changes. Selecting the **Track changes into Change tracking tables** option enables the **Number of days - you want to keep changes in the database** box. This allows for changes in Active Directory to - be tracked. When change tracking is enabled, notification analysis tasks can be used to send - alerts. + you want to keep changes in the database** box. This tracks changes in Active Directory. When + you enable change tracking, use notification analysis tasks to send alerts. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/adinventory/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/adinventory/overview.md index ff79a3ac50..251b5b935a 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/adinventory/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/adinventory/overview.md @@ -8,13 +8,12 @@ sidebar_position: 40 The extraction and correlation of user, group, and computer attributes drastically transforms the meaning of data collected across the many systems and applications that are linked to Active -Directory. The ADInventory Data Collector is designed as a highly scalable and useful data -collection mechanism to catalogue user, group, and computer object information that can be used by -other solutions within Access Analyzer. +Directory. The ADInventory Data Collector is a highly scalable data collection mechanism that catalogues user, +group, and computer object information for other solutions within Access Analyzer to use. -The ADInventory Data Collector is a core component of Access Analyzer and has been preconfigured to -be used within the .Active Directory Inventory Solution. Both this data collector and the solution -are available with all Access Analyzer license options. See the +The ADInventory Data Collector is a core component of Access Analyzer. The .Active Directory +Inventory Solution includes this data collector preconfigured. Both this data collector and the +solution are available with all Access Analyzer license options. See the [.Active Directory Inventory Solution](/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/overview.md) topic for additional information. @@ -44,9 +43,9 @@ topic for additional information. ## Functional Design of the ADInventory Data Collector -The ADInventory Data Collector has been designed to update incrementally. Once it has run against a -domain controller, additional collections gather changes made since the last scan. This enables the -ADInventory Data Collector to function efficiently within large environments. Each time it is run +The ADInventory Data Collector updates incrementally. After it has run against a domain controller, +additional collections gather the changes that occurred since the last scan. This enables the +ADInventory Data Collector to function efficiently within large environments. Each time you run it against different domain controllers, it restarts the cycle. ## ADInventory Query Configuration @@ -64,5 +63,5 @@ contains the following wizard pages: ![Active Directory Inventory DC Wizard Welcome page](/images/accessanalyzer/12.0/admin/datacollector/adinventory/welcome.webp) -The Welcome page can be hidden by selecting the **Do not display this page the next time** checkbox -when the wizard is open and configuration settings are saved. +To hide the Welcome page, select the **Don't display this page the next time** checkbox while the +wizard is open, then save the configuration settings. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/adinventory/results.md b/docs/accessanalyzer/12.0/admin/datacollector/adinventory/results.md index b1a88d0d0e..ac580d297b 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/adinventory/results.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/adinventory/results.md @@ -6,14 +6,13 @@ sidebar_position: 30 # ADInventory: Results -The Results page is where properties from Active Directory to be gathered are selected. It is a -wizard page for the category of Scan Active Directory. +Use the Results page to select which Active Directory properties to gather. It is a wizard page for +the category of Scan Active Directory. ![Active Directory Inventory DC Wizard Results page](/images/accessanalyzer/12.0/admin/datacollector/adinventory/results.webp) -Properties can be selected individually or the **Select All** or **Clear All** buttons can be used. -All selected properties are gathered. +You can select properties individually, or use the **Select All** or **Clear All** buttons. The +wizard gathers all selected properties. -This information is not available within the standard reference tables and views. Instead, this -information can be viewed in the SA_ADInventory_DEFAULT table, which is created when any of these -properties are selected. +The standard reference tables and views don't include this information. Instead, you can view it in +the SA_ADInventory_DEFAULT table, which the wizard creates when you select any of these properties. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/adinventory/standardtables.md b/docs/accessanalyzer/12.0/admin/datacollector/adinventory/standardtables.md index 802665ab5f..485dcb5dc3 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/adinventory/standardtables.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/adinventory/standardtables.md @@ -10,7 +10,7 @@ The ADInventory Data Collector gathers essential user and group inventory inform reference tables. Unlike other Access Analyzer data collectors, the ADInventory Data Collector writes data to these tables regardless of the job executing the query. -These tables and their associated views are outlined below: +The following table lists these tables and their associated views: | Table | Details | AD Object Reference Article | | ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | @@ -52,7 +52,7 @@ by the ADInventory Data Collector: ### AD Exception Types Translated -The following table translates the Type of Exceptions that can found. +The following table translates the types of exceptions the ADInventory Data Collector can identify. | Type | Exception | Description | | ---- | -------------------- | ------------------------------------------------------------------------- | diff --git a/docs/accessanalyzer/12.0/admin/datacollector/adinventory/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/adinventory/summary.md index e53677a5ea..d7275b0f8a 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/adinventory/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/adinventory/summary.md @@ -6,11 +6,11 @@ sidebar_position: 80 # ADInventory: Summary -The Summary page is where configuration settings are summarized. It is a wizard page for all of the +The Summary page summarizes the configuration settings. It is a wizard page for all of the categories. ![Active Directory Inventory DC Wizard Summary page](/images/accessanalyzer/12.0/admin/datacollector/adinventory/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Active Directory Inventory DC Wizard to ensure that no accidental -clicks are saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** to +close the Active Directory Inventory DC Wizard. This best practice ensures the wizard doesn't save +accidental clicks. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/category.md b/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/category.md index 65a648f9e8..6cbb361339 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/category.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/category.md @@ -6,8 +6,8 @@ sidebar_position: 20 # ADPermissions: Category -The ADPermissions Data Collector Category page identifies what kind of information to retrieve using -the Category wizard page. +Use the Category page to identify what kind of information the ADPermissions Data Collector +retrieves. ![ADPermissions Data Collector wizard Category page](/images/accessanalyzer/12.0/admin/datacollector/adpermissions/category.webp) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/customfilter.md b/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/customfilter.md index 0221948302..81ff672e5c 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/customfilter.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/customfilter.md @@ -7,7 +7,7 @@ sidebar_position: 40 # ADPermissions: Custom Filter The Custom Filter page provides options to configure settings for object permission collection. It -is only available if the Custom Filter option is checked on the Scope page. It is a wizard page for +is only available if you check the Custom Filter option on the Scope page. It is a wizard page for the categories of: - Scan Active Directory Permissions @@ -19,16 +19,15 @@ The configurable options are: - Root Path – Enter the AD root path - - Select the distinguished name from the drop-down menu to the right of the Root Path + - Select the distinguished name from the dropdown menu to the right of the Root Path - Click **Preview** to show an example of the complete path - LDAP Filter – Enter a custom filter string -- Scope – Select an option from the drop-down menu: +- Scope – Select an option from the dropdown menu: - Base – Limits the scope to the base object. The maximum number of objects returned is always one. - - One Level – Restricted to the immediate children of a base object, but excludes the base - object itself + - One Level – Includes only the immediate children of a base object, not the base object itself - Sub tree – (or a deep scope) includes all child objects as well as the base object -- Click **Add** to add the filter criteria to the list. Multiple filters can be used. +- Click **Add** to add the filter criteria to the list. You can use multiple filters. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/options.md b/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/options.md index 94a73ef065..104a465b59 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/options.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/options.md @@ -6,7 +6,7 @@ sidebar_position: 50 # ADPermissions: Options -The Options page is provides additional options for collecting the Active Directory information. It +The Options page provides additional options for collecting Active Directory information. It is a wizard page for the categories of: - Scan Active Directory Permissions @@ -25,5 +25,5 @@ The configurable options are: - Target previously scanned domain controller – Select to use the same domain controller as the previous scan - Track changes into change tracking tables – Enable to track changes - - Number of days you want to keep changes in the database – Set the number of days to keep - changes in the database + - Number of days you want to keep changes in the database – Set how many days to keep changes in + the database diff --git a/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/overview.md index 7a4da2b78c..3295d18f92 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/overview.md @@ -6,9 +6,9 @@ sidebar_position: 50 # ADPermissions Data Collector -The ADPermissions Data Collector collects the advanced security permissions of objects in AD. It is -preconfigured within the Active Directory Permissions Analyzer Solution. Both this data collector -and the solution are available with a special Access Analyzer license. See the +The ADPermissions Data Collector collects the advanced security permissions of objects in AD. It +comes preconfigured within the Active Directory Permissions Analyzer Solution. Both this data +collector and the solution are available with a special Access Analyzer license. See the [Active Directory Permissions Analyzer Solution](/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/overview.md) topic for additional information. @@ -32,9 +32,9 @@ topic for additional information. ## ADPermissions Query Configuration -The ADPermissions Data Collector is configured through the Active Directory Permissions Data -Collector Wizard. The wizard contains the following pages, which change based upon the query -category selected: +You configure the ADPermissions Data Collector through the Active Directory Permissions Data +Collector Wizard. The wizard contains the following pages, which change based on the query category +you select: - [ADPermissions: Category](/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/category.md) - [ADPermissions: Scope](/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/scope.md) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/removetables.md b/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/removetables.md index ec4aee94b6..5710a1045a 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/removetables.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/removetables.md @@ -8,11 +8,11 @@ sidebar_position: 80 If it becomes necessary to clear the ADPermissions Data Collector tables and views to resolve an issue, create a new job using it as the query source and select the Remove Tables category. The -Connection Profile applied should be the same as the one used for the associated **Active Directory +Connection Profile should be the same one that you used for the associated **Active Directory Permissions Analyzer** > **0.Collection** Job. Follow the steps. :::warning -Using this query task results in the deletion of collected data. +This query task deletes collected data. ::: @@ -21,23 +21,22 @@ Using this query task results in the deletion of collected data. **Step 2 –** In the Active Directory Permissions Data Collector Wizard, on the Category page select the **Remove Tables** category and click **Next**. -**Step 3 –** On the Results page, make sure all the Available Properties are selected and click -**Next**. +**Step 3 –** On the Results page, select all the Available Properties and click **Next**. **Step 4 –** Click **Finish** to close the Active Directory Permissions Data Collector Wizard. Click **OK** to close the Query Properties window. -When the job is run, all of the ADPermissions standard reference tables are removed from the +Running the job removes all of the ADPermissions standard reference tables from the database. :::tip -Remember, this job deletes data from the Access Analyzer database. Ensure the job has been -configured correctly prior to executing the job. +Remember, this job deletes data from the Access Analyzer database. Ensure you configure the job +correctly before you run it. ::: :::warning -Never leave the query task selected after the job has been executed. Accidental data +Never leave the query task selected after you run the job. Accidental data loss can occur. ::: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/results.md b/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/results.md index 2eb12cdb0e..bd65b22c36 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/results.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/results.md @@ -6,10 +6,10 @@ sidebar_position: 60 # ADPermissions: Results -The Results page is where properties that will be gathered are selected. It is a wizard page for all -of the categories. +Use the Results page to select the properties to gather. It is a wizard page for all of the +categories. ![ADPermissions Data Collector wizard Results page](/images/accessanalyzer/12.0/admin/datacollector/adpermissions/results.webp) -Available properties vary based on the category selected. Properties can be selected individually or -the **Select All** and **Clear All** buttons can be used. All selected properties are gathered. +Available properties vary based on the category selected. You can select properties individually, or +use the **Select All** and **Clear All** buttons. The wizard gathers all selected properties. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/scope.md b/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/scope.md index 716945ea02..072829a934 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/scope.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/scope.md @@ -6,7 +6,7 @@ sidebar_position: 30 # ADPermissions: Scope -The Scope page is where the scope for the Active Directory permissions scan is configured. It is a +Use the Scope page to configure the scope for the Active Directory permissions scan. It is a wizard page for the categories of: - Scan Active Directory Permissions diff --git a/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/standardtables.md b/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/standardtables.md index 8941eb7c6d..526d3f2f6d 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/standardtables.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/standardtables.md @@ -10,7 +10,7 @@ The ADPermissions Data Collector gathers essential user and group inventory info standard reference tables. Unlike other Access Analyzer data collectors, the ADPermissions Data Collector writes data to these tables regardless of the job executing the query. -These tables and their associated views are outlined below: +The following table lists these tables and their associated views: | Table | Details | | -------------------------------------- | ------------------------------------------------- | diff --git a/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/summary.md index f3da8cc348..b6b277fe74 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/adpermissions/summary.md @@ -6,11 +6,11 @@ sidebar_position: 70 # ADPermissions: Summary -The Summary page is where configuration settings are summarized. It is a wizard page for all of the +The Summary page summarizes the configuration settings. It is a wizard page for all of the categories. ![ADPermissions Data Collector wizard Summary page](/images/accessanalyzer/12.0/admin/datacollector/adpermissions/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Active Directory Permissions Data Collector Wizard ensuring that no -accidental clicks are saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** to +close the Active Directory Permissions Data Collector Wizard. This ensures the wizard doesn't save +accidental clicks. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/aws/criteria.md b/docs/accessanalyzer/12.0/admin/datacollector/aws/criteria.md index 22419c2819..3bae8b241b 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/aws/criteria.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/aws/criteria.md @@ -6,24 +6,23 @@ sidebar_position: 50 # AWS: Criteria -The Criteria (Select DLP criteria for this scan) page is where criteria to be used for discovering -sensitive data during a scan is configured. It is a wizard page for the category of Collect SDD -Data. +Use the Criteria (Select DLP criteria for this scan) page to configure the criteria for discovering +sensitive data during a scan. It is a wizard page for the category of Collect SDD Data. ![AWS Query SDD Criteria](/images/accessanalyzer/12.0/admin/datacollector/aws/criteria.webp) -Default criteria is set at the **Global Settings** > **Sensitive Data** node. Choose between the +Configure default criteria at the **Global Settings** > **Sensitive Data** node. Choose between the **Use Global Criteria** Selection and the **Use the Following Selected Criteria** radio buttons. -For custom criteria, select the checkbox for the criteria to be used to search for sensitive data. -There are **Select All** and **Clear All** buttons that can be used. +For custom criteria, select the checkbox for each criterion you want to use to search for sensitive +data. Use the **Select All** and **Clear All** buttons as needed. The table contains the following types of criteria: - System Criteria – Lists pre-defined criteria - User Criteria – Lists user-defined criteria -User-defined criteria is created in the Criteria Editor, accessed through the **Global Settings** > +You create user-defined criteria in the Criteria Editor, accessed through the **Global Settings** > **Sensitive Data** node. See the [Sensitive Data Discovery](/docs/accessanalyzer/12.0/sensitivedatadiscovery/overview.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/aws/droptables.md b/docs/accessanalyzer/12.0/admin/datacollector/aws/droptables.md index 5bb915d5d8..cbf6da594f 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/aws/droptables.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/aws/droptables.md @@ -6,8 +6,8 @@ sidebar_position: 80 # Drop AWS Tables -Sometimes when troubleshooting an AWS issue, it becomes necessary to clear the AWS DC data and -tables from the Access Analyzer database. Follow the steps to configure a job to remove tables. +Sometimes, when you troubleshoot an AWS issue, you need to clear the AWS DC data and +tables from the Access Analyzer database. To configure a job to remove tables: **Step 1 –** Create a new job. @@ -24,13 +24,13 @@ tables from the Access Analyzer database. Follow the steps to configure a job to Collector Wizard. Click **OK** to close the Query Properties window. :::warning -When the job is run, all of the AWS DC data and tables are removed from the database. +Running the job removes all of the AWS DC data and tables from the database. ::: -The job is now configured and ready to run. +You've now configured the job, and it's ready to run. :::note -An AWS connection profile is not required for the Drop AWS DC Tables task. +An AWS connection profile isn't required for the Drop AWS DC Tables task. ::: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/aws/filters3objects.md b/docs/accessanalyzer/12.0/admin/datacollector/aws/filters3objects.md index e36d0e1dec..495c8aabf5 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/aws/filters3objects.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/aws/filters3objects.md @@ -6,8 +6,8 @@ sidebar_position: 30 # AWS: Filter S3 Objects -The Filter S3 Objects page provides the options to filter which objects stored in S3 should be -queried for permissions and sensitive data. It is a wizard page for the categories of: +The Filter S3 Objects page provides options to filter which objects stored in S3 the AWS Data +Collector queries for permissions and sensitive data. It is a wizard page for the categories of: - Collect S3 - Collect SDD Data @@ -32,7 +32,7 @@ Select from the available buckets and click **OK** to add them to the Filter S3 ## Add Custom Filter -The Add Custom Filter window allows a custom filter to be configured. +Use the Add Custom Filter window to configure a custom filter. ![Add Custom Filter window](/images/accessanalyzer/12.0/admin/datacollector/aws/customfilter.webp) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/aws/loginroles.md b/docs/accessanalyzer/12.0/admin/datacollector/aws/loginroles.md index e9167d8870..d332abe4e8 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/aws/loginroles.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/aws/loginroles.md @@ -6,7 +6,7 @@ sidebar_position: 20 # AWS: Login Roles -The Login Roles page is where the previously created AWS Roles are added. It is a wizard page for +Use the Login Roles page to add the AWS roles you previously created. It is a wizard page for the categories of: - Collect Org data @@ -15,7 +15,7 @@ the categories of: ![AWS Query Login Roles](/images/accessanalyzer/12.0/admin/datacollector/aws/loginroles.webp) -Add the login roles that will allow Access Analyzer to scan the AWS accounts. See the +Add the login roles that allow Access Analyzer to scan the AWS accounts. See the [Configure AWS for Scans](/docs/accessanalyzer/12.0/requirements/aws/configurescans.md) topic for additional information. The page has the following options: @@ -24,6 +24,6 @@ information. The page has the following options: - Add – Add the role from the Role Name textbox to the list - Remove – Remove the selected role from the list - Clear – Remove all roles from the list -- Max Session Duration (hours) – Specify the maximum time the account can be logged in for. This - value should not exceed the SessionDuration configured for the role in AWS. The default value is 1 - and the maximum value is 12. +- Max Session Duration (hours) – Specify the maximum number of hours the account can stay logged in. + This value shouldn't exceed the SessionDuration configured for the role in AWS. The default value + is 1 and the maximum value is 12. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/aws/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/aws/overview.md index bc0c50a8ad..8980aa88fb 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/aws/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/aws/overview.md @@ -8,7 +8,7 @@ sidebar_position: 60 The AWS Data Collector collects IAM users, groups, roles, and policies, as well as S3 permissions, content, and sensitive data from the target Amazon Web Services (AWS) accounts. The AWS Data -Collector has been preconfigured for the AWS Solution. Both this data collector and the solution are +Collector comes preconfigured for the AWS Solution. Both this data collector and the solution are available with a special Access Analyzer license. See the [AWS Solution](/docs/accessanalyzer/12.0/solutions/aws/overview.md) topic for additional information. @@ -22,11 +22,11 @@ available with a special Access Analyzer license. See the **Permissions** -- To collect details about the AWS Organization, the following permission is required: +- To collect details about the AWS Organization, grant the following permission: - organizations:DescribeOrganization -- To collect details regarding IAM, the following permissions are required: +- To collect details regarding IAM, grant the following permissions: - iam:GenerateCredentialReport - iam:GenerateServiceLastAccessedDetails @@ -35,7 +35,7 @@ available with a special Access Analyzer license. See the - iam:Simulate\* - sts:GetAccessKeyInfo -- To collect details related to S3 buckets and objects, the following permissions are required: +- To collect details related to S3 buckets and objects, grant the following permissions: - s3:Describe\* - s3:Get\* @@ -44,14 +44,14 @@ available with a special Access Analyzer license. See the **Sensitive Data Discovery Considerations** -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the minimum amount -of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For example, if the job -is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are required (8x2=16). +If you run Sensitive Data Discovery (SDD) scans, increase the minimum amount of RAM. Each thread +requires a minimum of 2 additional GB of RAM per host. For example, if you configure the job to scan +8 hosts at a time, it requires an extra 16 GB of RAM (8 x 2 = 16). ## AWS Query Configuration -The AWS Data Collector is configured through the Amazon Web Services Data Collector Wizard. The -wizard contains the following pages, which change based up on the query category selected: +You configure the AWS Data Collector through the Amazon Web Services Data Collector Wizard. The +wizard contains the following pages, which change based on the query category you select: - [AWS: Category](/docs/accessanalyzer/12.0/admin/datacollector/aws/category.md) - [AWS: Login Roles](/docs/accessanalyzer/12.0/admin/datacollector/aws/loginroles.md) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/aws/results.md b/docs/accessanalyzer/12.0/admin/datacollector/aws/results.md index b686048ca0..d247bb51b9 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/aws/results.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/aws/results.md @@ -6,10 +6,10 @@ sidebar_position: 60 # AWS: Results -The Results page is where properties that will be gathered are selected. It is a wizard page for all -of the categories. +Use the Results page to select the properties to gather. It is a wizard page for all of the +categories. ![Results page](/images/accessanalyzer/12.0/admin/datacollector/aws/results.webp) -Properties can be checked individually or the **Select All** or **Clear All** buttons can be used. -All checked properties are gathered. Available properties vary based on the category selected. +You can check properties individually, or use the **Select All** or **Clear All** buttons. The +wizard gathers all checked properties. Available properties vary based on the category selected. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/aws/sensitivedata.md b/docs/accessanalyzer/12.0/admin/datacollector/aws/sensitivedata.md index 1e138e6849..cc08bec972 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/aws/sensitivedata.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/aws/sensitivedata.md @@ -6,7 +6,7 @@ sidebar_position: 40 # AWS: Sensitive Data Settings -The Sensitive Data Settings page is where sensitive data discovery settings are configured. It is a +Use the Sensitive Data Settings page to configure sensitive data discovery settings. It is a wizard page for the category of Collect SDD Data. ![Sensitive Data Settings page](/images/accessanalyzer/12.0/admin/datacollector/aws/sensitivedata.webp) @@ -18,7 +18,8 @@ Configure the following options: - Include offline files (this may significantly increase scan times) – Includes offline files in the scan - Perform Optical Character Recognition for image files – Enables the data collector to scan for - sensitive data within digital images of physical documents + sensitive data within digital images of physical documents using optical character recognition + (OCR) :::note The OCR option is intended to work for clear scanned physical documents or documents @@ -46,13 +47,13 @@ Configure the following options: - Spreadsheets - Text/Markup files -- Perform differential scan of – Enables you to choose whether to employ incremental scanning: +- Perform differential scan of – Choose whether to employ incremental scanning: - Files modified since last scan – Scans only files modified since the last scan - Files modified since [date] – Only scans files modified after the specified date - Files modified since the last [number] days – Scans files modified within the specified number of days -- Number of SDD scan processes [number] – Increases the number of SDD scanner processes that spawn - as part of a scan, increasing parallel scanning. The value should not exceed 2x the number of CPU - threads available. +- Number of SDD scan processes [number] – Increases the number of Sensitive Data Discovery (SDD) + scanner processes that spawn as part of a scan, increasing parallel scanning. The value shouldn't + exceed 2x the number of CPU threads available. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/aws/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/aws/summary.md index 4e2127d47e..b12167111d 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/aws/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/aws/summary.md @@ -10,6 +10,6 @@ The Summary page displays a summary of the configured query. It is a wizard page ![summary](/images/accessanalyzer/12.0/admin/datacollector/aws/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Amazon Web Services Data Collector Wizard to ensure that no accidental -clicks are saved. +Click **Finish** to save configuration changes. If you made no changes, it is a best practice to +click **Cancel** to close the Amazon Web Services Data Collector Wizard instead. This ensures the +wizard doesn't save any accidental clicks. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/category.md b/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/category.md index a7e1edcd76..eb2344469f 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/category.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/category.md @@ -15,10 +15,10 @@ The two categories are: - Scan Entra ID – Scans Microsoft Entra ID objects and imports the information into the SQL Server database, creating the standard reference tables. This task also maintains the schema for tables and views. This is the standard option for this data collector. -- Remove Tables – Removes all tables and views from SQL Server database. This option is designed for - troubleshooting. When this option is selected, the next wizard page is the Summary page. See the +- Remove Tables – Removes all tables and views from SQL Server database. Use this option for + troubleshooting. When you select this option, the wizard displays the Summary page next. See the [Troubleshooting AzureADInventory Data Collector](/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/troubleshooting.md) topic for more information. The Scan Entra ID category is the pre-configured setting for the .Entra ID Inventory Job Group. -Therefore, accessing the Entra ID Inventory DC Wizard from the query within that job group does not +Therefore, accessing the Entra ID Inventory DC Wizard from the query within that job group doesn't display the Category wizard page. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/configurejob.md b/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/configurejob.md index 045b4a9acf..934820349d 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/configurejob.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/configurejob.md @@ -6,14 +6,14 @@ sidebar_position: 20 # Microsoft Entra ID Connection Profile & Host List -The AzureADInventory Data Collector requires a custom Connection Profile and host list to be created -and assigned to the job or job group conducting the data collection. The host inventory option -during host list creation makes it necessary to configure the Connection Profile first. +The AzureADInventory Data Collector requires you to create a custom Connection Profile and host +list, and assign them to the job or job group conducting the data collection. The host inventory +option during host list creation requires you to configure the Connection Profile first. ## Connection Profile -Creating the Connection Profile requires having the Client ID and Key that was generated when Access -Analyzer was registered as a web application with Microsoft Entra ID. See the +To create the Connection Profile, you need the Client ID and Key generated when you registered +Access Analyzer as a web application with Microsoft Entra ID. See the [Microsoft Entra ID Auditing Configuration](/docs/accessanalyzer/12.0/requirements/entraid/entraid/access.md) for additional information. @@ -32,7 +32,7 @@ Create a Connection Profile and set the following information on the User Creden [Generate the Client Secret Key](/docs/accessanalyzer/12.0/requirements/entraid/entraid/access.md#generate-the-client-secret-key) topic for additional information. -Once the Connection Profile is created, it is time to create the custom host list. See the +After you create the Connection Profile, create the custom host list. See the [Connection](/docs/accessanalyzer/12.0/admin/settings/connection/overview.md) topic for additional information. ## Custom Host List diff --git a/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/customattributes.md b/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/customattributes.md index 212f8a36a8..933d5e924e 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/customattributes.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/customattributes.md @@ -6,8 +6,7 @@ sidebar_position: 50 # AzureADInventory: Custom Attributes -Use the Custom Attributes wizard page to define custom attributes that will be used in the Microsoft -Entra ID scan. +Use the Custom Attributes wizard page to define custom attributes for the Microsoft Entra ID scan. ![Entra ID Inventory Data Collector Wizard Custom Attributes page](/images/accessanalyzer/12.0/admin/datacollector/azureadinventory/customattributes.webp) @@ -16,26 +15,26 @@ Configuration options for Custom Attributes include: - Collect Open Extensions – If enabled, data collector will perform a full scan and collect all extension attributes for Microsoft Entra ID objects - - Enabling this option will increase the time it takes for the data collector to complete the - scan. Disabling this option will configure the data collector run a differential scan, which - will only scan changes since the last scan was performed. + - Enabling this option increases the time it takes for the data collector to complete the + scan. Disabling this option configures the data collector to run a differential scan instead, + which scans only changes since the last scan ran. :::warning - A full scan is required when new attributes are added or removed. + Adding or removing attributes requires a full scan. ::: -- Add – Adds a manually entered attribute that is included in the scan. This option opens the Custom +- Add – Adds a manually entered attribute to the scan. This option opens the Custom Attribute window. - Edit – Make changes to a previously added attribute. This option opens the Custom Attribute window. - Remove – Deletes the attribute from the table and therefore the scan - Import – Use the Azure Connection Profile credentials or manually inputted credentials to import - custom attributes for the scan using a valid tenant name. This option opens up the Custom + custom attributes for the scan using a valid tenant name. This option opens the Custom Attributes Import Wizard. Use the **Add**, **Edit**, and **Remove** buttons at the bottom of the window to configure the -custom attributes to be gathered by the scan. Use the **Add** button to open the +custom attributes the scan gathers. Use the **Add** button to open the [Custom Attribute Window](#custom-attribute-window). The **Import** button opens the [Custom Attributes Import Wizard](#custom-attributes-import-wizard). @@ -48,17 +47,17 @@ window. The options on the Custom Attributes window are: -- Tenant Filter – Use a Tenant Name or wildcard to target the desired environment. Wildcards (\*) - can be used. -- Object Class – One or more object class for the attribute can be selected: +- Tenant Filter – Use a Tenant Name or wildcard to target the environment you want. You can use + wildcards (\*). +- Object Class – Select one or more object classes for the attribute: - User - Group - Contact - Attribute Name – Microsoft Entra ID attribute name -- Collect all sub-attributes – Allows the collection of sub-attributes - - Sub-Attribute Name – Define the sub-attribute name. Wildcards (\*) can be used. +- Collect all sub-attributes – Lets you collect sub-attributes + - Sub-Attribute Name – Define the sub-attribute name. You can use wildcards (\*). -Repeat this process until all desired Custom Attributes have been included. Click **OK** to save the +Repeat this process until you've added all desired custom attributes. Click **OK** to save the attribute. #### Custom Attributes Import Wizard @@ -73,7 +72,7 @@ Custom Attributes Import Wizard opens. ![Custom Attributes Import Wizard](/images/accessanalyzer/12.0/admin/datacollector/azureadinventory/customattributesimportwizard.webp) **Step 2 –** On the Connection page, enter the Tenant Name of the instance of Microsoft Entra ID to -be targeted, and then select the method of supplying credentials for the specified tenant instance: +target, and then select how to supply credentials for the specified tenant instance: - Use the following connection profile entry – Select an Azure Connection Profile from the dropdown list @@ -92,7 +91,7 @@ See the [Microsoft Entra ID Auditing Configuration](/docs/accessanalyzer/12.0/re [Microsoft Entra ID Connection Profile & Host List](/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/configurejob.md) topics for additional information. -**Step 3 –** Click **Test Connection** in order to connect to the tenant with the supplied +**Step 3 –** Click **Test Connection** to connect to the tenant with the supplied credentials. If they are correct, the Schema Attributes and Application Attributes pages become available. Click **Next** to navigate to them. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/overview.md index 3b3c7a79b6..318b75a602 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/overview.md @@ -49,7 +49,7 @@ additional information. ## AzureADInventory Query Configuration -The AzureADInventory Data Collector is configured through the Entra ID Inventory DC Wizard, which +You configure the AzureADInventory Data Collector through the Entra ID Inventory DC Wizard, which contains the following wizard pages: - Welcome @@ -61,5 +61,5 @@ contains the following wizard pages: ![Entra ID Inventory Data Collector Wizard Welcome page](/images/accessanalyzer/12.0/admin/datacollector/azureadinventory/welcome.webp) -Hide the Welcome page the next time this data collected is accessed by selecting the **Do not +To hide the Welcome page the next time you access this data collector, select the **Don't display this page the next time** checkbox. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/results.md b/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/results.md index 2df29a43cf..71e6aeca8e 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/results.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/results.md @@ -6,12 +6,12 @@ sidebar_position: 60 # AzureADInventory: Results -The Results page is where the properties from Microsoft Entra ID to be gathered are selected. It is -a wizard page for the category of Scan Entra ID. +Use the Results page to select the Microsoft Entra ID properties to gather. It is +a wizard page for the Scan Entra ID category. ![Entra ID Inventory DC Wizard Results page](/images/accessanalyzer/12.0/admin/datacollector/azureadinventory/results.webp) -Properties can be checked individually or the **Select All** and **Clear All** buttons can be used. -All checked properties are collected. This information is not available within the standard -reference tables and views. Instead, this information can be viewed in the -**SA_AzureADInventory_DEFAULT** table, which is created when any of these properties are selected. +You can check properties individually, or use the **Select All** and **Clear All** buttons. +The data collector collects all checked properties. This information isn't available within the standard +reference tables and views. Instead, view this information in the +**SA_AzureADInventory_DEFAULT** table, which the data collector creates when you select any of these properties. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/standardtables.md b/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/standardtables.md index bb3f3468c1..84bcce7e72 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/standardtables.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/standardtables.md @@ -10,7 +10,7 @@ The AzureADInventory Data Collector collects essential user and group inventory standard reference tables. Unlike other Access Analyzer data collectors, the AzureADInventory Data Collector writes data to these tables regardless of the job executing the query. -These tables and their associated views are outlined below: +The following table describes these tables and their associated views: | Table | Details | | ----------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -26,10 +26,9 @@ These tables and their associated views are outlined below: | SA_AzureADInventory_Principals | Contains common attributes for users, groups, and computers as well as references to their primary display name and mail addresses | | SA_AzureADInventory_Users | Contains extended information about users, department, title, and so on | -Views are the recommended way for you to obtain the information gathered by the AzureADInventory -Data Collector. They contain additional information for building queries easily. The following is an -explanation of the corresponding views created for some of the tables generated by the -AzureADInventory Data Collector: +Views are the recommended way for you to obtain the information the AzureADInventory +Data Collector gathers. They contain additional information for building queries. The following table +explains the views the AzureADInventory Data Collector creates for some of its tables: | Views | Details | | --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | @@ -43,7 +42,7 @@ AzureADInventory Data Collector: ### AzureADInventory Exception Types Translated -The following table translates the Type of Exceptions that can found. +The following table explains the exception types. | Type | Exception | Description | | ---- | -------------------- | ------------------------------------------------------------------------- | diff --git a/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/summary.md index 80d3c80469..0c0e86ddae 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/summary.md @@ -6,11 +6,10 @@ sidebar_position: 70 # AzureADInventory: Summary -The Summary page is where configuration settings are summarized. It is a wizard page for both of the -categories. +The Summary page summarizes your configuration settings. It is a wizard page for both categories. ![Entra ID Inventory DC Wizard Summary page](/images/accessanalyzer/12.0/admin/datacollector/azureadinventory/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Entra ID Inventory DC Wizard to ensure that no accidental clicks are -saved. +Click **Finish** to save configuration changes. If you made no changes, it is a best practice to +click **Cancel** to close the Entra ID Inventory DC Wizard instead. This ensures the wizard doesn't +save any accidental clicks. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/troubleshooting.md b/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/troubleshooting.md index 3b44d36f88..99c03162bc 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/troubleshooting.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/troubleshooting.md @@ -8,7 +8,7 @@ sidebar_position: 80 ## Clear AzureADInventory Tables -Sometimes when troubleshooting an AzureADInventory issue, it becomes necessary to clear the standard +Sometimes when troubleshooting an AzureADInventory issue, you need to clear the standard reference tables. Follow the steps. **Step 1 –** Create a new job and assign a query using the **AZUREADINVENTORY** Data Collector. @@ -19,7 +19,7 @@ category task. **Step 3 –** Click **Next** and then **Finish** to close the Entra ID Inventory DC Wizard. Click **OK** to close the Query Properties window. -When the job is run, all of the AzureADInventory standard reference tables are removed from the +Running the job removes all AzureADInventory standard reference tables from the database. ## Troubleshooting Error Messages @@ -28,11 +28,11 @@ Change the XML parameters to address the following errors: Error: Microsoft.Graph.ServiceException: Code: timeout Message: The request timed out -Update the `` parameter to update the number of retries to run the query. +Update the `` parameter to change the number of retries for the query. The default is 3. Error: An existing connection was forcible closed by the remote host -Update the `` parameter to update the max delta token age. The default is 6. +Update the `` parameter to change the max delta token age. The default is 6. See the [View Job XML File](/docs/accessanalyzer/12.0/admin/jobs/job/properties/viewxml.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/box/activityoperationscope.md b/docs/accessanalyzer/12.0/admin/datacollector/box/activityoperationscope.md index 1cc19e03fd..f595bc5e71 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/box/activityoperationscope.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/box/activityoperationscope.md @@ -6,13 +6,13 @@ sidebar_position: 70 # Box: Activity Operation Scope -The Activity Operation Scope page (ActivityOperationScope) is where Box Enterprise events can be -selected or unselected for scans. It is a wizard page for the Scan Box Activity category. +Use the Activity Operation Scope page (ActivityOperationScope) to select or unselect Box Enterprise +events for scans. It is a wizard page for the Scan Box Activity category. ![Box DC Wizard Activity Operation Scope page](/images/accessanalyzer/12.0/admin/datacollector/box/activityoperation.webp) -Event filters can be selected by group or the group may be expanded and the filters selected -individually. All selected filters are gathered from the Box environment. +You can select event filters by group, or expand the group and select filters individually. The +data collector gathers all selected filters from the Box environment. Event filters include: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/box/activitytimeframescope.md b/docs/accessanalyzer/12.0/admin/datacollector/box/activitytimeframescope.md index c17987c5cd..a87bd40e25 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/box/activitytimeframescope.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/box/activitytimeframescope.md @@ -6,8 +6,8 @@ sidebar_position: 60 # Box: Activity Timeframe Scope -The Activity Timespan Scope page (ActivityTimeframeScope) is where Box activity data collection is -configured. It is a wizard page for the Scan Box Activity category. +Use the Activity Timespan Scope page (ActivityTimeframeScope) to configure Box activity data +collection. It is a wizard page for the Scan Box Activity category. ![Box DC Wizard Activity Timespan Scope page](/images/accessanalyzer/12.0/admin/datacollector/box/activitytimeframe.webp) @@ -15,14 +15,14 @@ Select one of the following options to configure the timeframe for Box data coll - Relative Timespan – Collects activity from a set number of days relative to the present - - Collect activity from the last [number] Days – Enter the number of days for which activity - data collection is required. The default is 180. The maximum timespan is 365 days. + - Collect activity from the last [number] Days – Enter the number of days to collect activity + data for. The default is 180. The maximum timespan is 365 days. - Data retention settings – Select a preferred retention setting - Within timespan – Deletes all data outside of the selected timespan - Retain all data – Retains all data collected inside or outside of the selected timespan -- Absolute Timespan – Enter the interval of days for which activity data collection is required. The +- Absolute Timespan – Enter the interval of days to collect activity data for. The default End Date is the current day. :::note diff --git a/docs/accessanalyzer/12.0/admin/datacollector/box/additionalscoping.md b/docs/accessanalyzer/12.0/admin/datacollector/box/additionalscoping.md index 842fc10edf..215fbcaee6 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/box/additionalscoping.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/box/additionalscoping.md @@ -6,7 +6,7 @@ sidebar_position: 50 # Box: Additional Scoping -The Additional Scoping page is where the scan can be limited by depth of the scan. It is a wizard +Use the Additional Scoping page to limit the scan by depth. It is a wizard page for the Scan Box Permissions category. ![Box DC Wizard Additional Scoping page](/images/accessanalyzer/12.0/admin/datacollector/box/additionalscoping.webp) @@ -14,7 +14,7 @@ page for the Scan Box Permissions category. Configure the scan depth level: - Limit scanned depth to: [number] level – Select the checkbox and set the scan depth level to the - desired depth. If this checkbox is not selected, then the entire Box environment will be scanned, - according to the [Box: Exclusions Page](/docs/accessanalyzer/12.0/admin/datacollector/box/exclusions.md) settings. If the scoping depth is set to - **0** then only root will be scanned. Each increment will add another level of depth from root + desired depth. If you don't select this checkbox, the data collector scans the entire Box + environment according to the [Box: Exclusions Page](/docs/accessanalyzer/12.0/admin/datacollector/box/exclusions.md) settings. If you set the scoping depth to + **0**, the data collector scans only the root. Each increment will add another level of depth from root level. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/box/authenticate.md b/docs/accessanalyzer/12.0/admin/datacollector/box/authenticate.md index 7cc0096182..75f147fed2 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/box/authenticate.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/box/authenticate.md @@ -6,7 +6,7 @@ sidebar_position: 80 # Box: Authenticate -The Authenticate page is where connection to the Box environment is configured. It is a wizard page +Use the Authenticate page to configure the connection to the Box environment. It is a wizard page for all categories. ![Box DC Wizard Authentication page](/images/accessanalyzer/12.0/admin/datacollector/box/authentication.webp) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/box/exclusions.md b/docs/accessanalyzer/12.0/admin/datacollector/box/exclusions.md index cc41a60e07..8fdae4b735 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/box/exclusions.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/box/exclusions.md @@ -6,21 +6,21 @@ sidebar_position: 30 # Box: Exclusions Page -The Exclude or Include folders page (ExclusionsPage) is where the scan can be limited to include or -to exclude folders within the Box Enterprise. It is a wizard page for of Scan Box Permissions +Use the Exclude or Include folders page (ExclusionsPage) to limit the scan to include or +exclude folders within the Box Enterprise. It is a wizard page for the Scan Box Permissions category. ![Box DC Wizard Exclude or Include folders page](/images/accessanalyzer/12.0/admin/datacollector/box/exclusions.webp) The options on the Exclusions Page are: -- Add as inclusion – Type the path of a folder in the text box to include in the scan. The folder +- Add as inclusion – Enter the path of a folder in the text box to include in the scan. The folder path must not include a slash at the end. - Example format: `/All Files/Folder/SubFolder` - Incorrect format: `/All Files/Folder/SubFolder/` -- Add as exclusion – Type the path of a folder in the text box to exclude from the scan +- Add as exclusion – Enter the path of a folder in the text box to exclude from the scan The **Remove** option will delete a selected folder from the list. The **Clear List** option will remove all folders from the list. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/box/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/box/overview.md index 720392a04b..c6c98fd3f0 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/box/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/box/overview.md @@ -9,9 +9,9 @@ sidebar_position: 80 The Box Data Collector audits access, group membership, and content within a Box enterprise. :::note -If the Box Data Collector is used in a new job, outside of the Box Solution, it is -necessary to deselect the **Skip Hosts that do not respond to PING** option on the job’s -**Properties** > **Performance** tab. +If you use the Box Data Collector in a new job outside of the Box Solution, deselect the +**Skip Hosts that don't respond to PING** option on the job's **Properties** > **Performance** +tab. ::: @@ -35,8 +35,8 @@ the solution are available with a special Access Analyzer license. See the ## Box Query Configuration -The Box Data Collector is configured through the Box Data Collector Wizard. The wizard contains the -following pages, which change based up on the query category selected: +Configure the Box Data Collector through the Box Data Collector Wizard. The wizard contains the +following pages, which change based on the query category selected: - Welcome - [Box: Category](/docs/accessanalyzer/12.0/admin/datacollector/box/category.md) @@ -55,5 +55,5 @@ introductory and caution information about the Box Data Collector before proceed ![Box DC Wizard Welcome page](/images/accessanalyzer/12.0/admin/datacollector/box/welcome.webp) -The Welcome page can be hidden by checking the **Do not display this page the next time** box when -the wizard is open and configuration settings are saved. +To hide the Welcome page, check the **Don't display this page the next time** box while the wizard +is open. This saves your configuration settings. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/box/results.md b/docs/accessanalyzer/12.0/admin/datacollector/box/results.md index ff56500b08..a5d7726961 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/box/results.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/box/results.md @@ -6,10 +6,10 @@ sidebar_position: 90 # Box: Results -The Results page is where properties that will be gathered are selected. It is a wizard page for all +Use the Results page to select the properties to gather. It is a wizard page for all categories. ![Box DC Wizard Results page](/images/accessanalyzer/12.0/admin/datacollector/box/results.webp) -Properties can be selected individually or the **Select All** or **Clear All** buttons can be used. -All selected properties will be gathered. Available properties vary based on the category selected. +You can select properties individually, or use the **Select All** or **Clear All** buttons. +The data collector gathers all selected properties. Available properties vary based on the category selected. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/box/scopebyuser.md b/docs/accessanalyzer/12.0/admin/datacollector/box/scopebyuser.md index 37c92ef7d1..2f69617e8a 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/box/scopebyuser.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/box/scopebyuser.md @@ -6,20 +6,20 @@ sidebar_position: 40 # Box: Scope by User Page -The User Scope Settings page (ScopeByUserPage) is where the scope of the scan can be limited to -specified users and the resulting scan will only scan for the specified users. It is a wizard page +Use the User Scope Settings page (ScopeByUserPage) to limit the scope of the scan to specified +users. The resulting scan only includes the specified users. It is a wizard page for the Scan Box Permissions category. ![Box DC Wizard User Scope Settings page](/images/accessanalyzer/12.0/admin/datacollector/box/scopebyuser.webp) Select whether to scan **All Users** or **Limited Users**. If scanning for **Limited Users**, click -**Browse** and navigate to the path of the CSV file that contains the email addresses of users to be -included in the scan. The CSV file should have one email address per row. +**Browse** and navigate to the path of the CSV file that contains the email addresses of users to +include in the scan. The CSV file should have one email address per row. :::note The query will collect information related to User names and Group membership for all -users in a target environment. However, if the query is scoped to specific users, no additional -information is collected for users outside out of the scope. User names and group membership for the -target environment is necessary to generate the Box Solution reports. +users in a target environment. However, if you scope the query to specific users, the query doesn't +collect additional information for users outside the scope. The Box Solution reports require user +names and group membership for the target environment. ::: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/box/standardtables.md b/docs/accessanalyzer/12.0/admin/datacollector/box/standardtables.md index 0cd058264c..b617928398 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/box/standardtables.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/box/standardtables.md @@ -7,7 +7,7 @@ sidebar_position: 10 # Standard Reference Tables & Views For the Box Data Collector The Box Data Collector gathers essential user and group inventory information into standard -reference tables. These tables and their associated views are outlined below: +reference tables. The following table describes these tables and their associated views: | Table | Details | | -------------------------- | ----------------------------------------------------------------------------------------------------------------------- | @@ -27,10 +27,10 @@ reference tables. These tables and their associated views are outlined below: | SA_Box_UnusualUserActivity | Contains information about suspicious activity on user accounts | | SA_Box_Users | Contains one row per user and displays information on users of any teams present | -Views are the recommended way for Access Analyzer users to obtain the information gathered by the -Box Data Collector. They contain additional information for building queries easily. The following -is an explanation of the corresponding views created for some of the tables generated by the Box -Data Collector: +Views are the recommended way for Access Analyzer users to obtain the information the +Box Data Collector gathers. They contain additional information for building queries. The following +table explains the views the Box Data Collector creates for some of its +tables: | Views | Details | | ------------------------- | ------------------------------------------------------------------------------------------------------------ | diff --git a/docs/accessanalyzer/12.0/admin/datacollector/box/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/box/summary.md index 71a3f19857..3ed0fa5ae6 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/box/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/box/summary.md @@ -6,11 +6,9 @@ sidebar_position: 100 # Box: Summary -The Summary page is where configuration settings are summarized. It is a wizard page for all of the -categories. +The Summary page summarizes the configuration settings. It's a wizard page for all categories. ![Box DC Wizard Summary page](/images/accessanalyzer/12.0/admin/datacollector/box/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Box Data Collector Wizard ensuring that no accidental clicks are -saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** to +close the Box Data Collector Wizard instead, so accidental clicks don't get saved. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/commandlineutility/definefields.md b/docs/accessanalyzer/12.0/admin/datacollector/commandlineutility/definefields.md index 1e6e18ea2c..c81163220a 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/commandlineutility/definefields.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/commandlineutility/definefields.md @@ -12,7 +12,7 @@ output. It is a wizard page for the **Edit Profile** and **Create a New Profile* ![Command Line Utility Data Collector Wizard Define Fields page](/images/accessanalyzer/12.0/admin/datacollector/commandlineutility/definefields.webp) :::warning -Do not modify this page without guidance from Netwrix or the data may not be processed -by Access Analyzer. +Don't modify this page without guidance from Netwrix. Otherwise, Access Analyzer might not process +the data correctly. ::: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/commandlineutility/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/commandlineutility/overview.md index 02a2bae772..d59a4c2618 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/commandlineutility/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/commandlineutility/overview.md @@ -6,8 +6,8 @@ sidebar_position: 90 # CommandLineUtility Data Collector -The CommandLineUtility Data Collector provides the ability to remotely spawn, execute, and extract -data provided by a Microsoft native or third-party command line utility. It allows users to easily +The CommandLineUtility Data Collector lets you remotely spawn, execute, and extract +data provided by a Microsoft native or third-party command line utility. Use it to execute a command line utility and capture its output as Access Analyzer data. This data collector is a core component of Access Analyzer and is available with all Access Analyzer licenses. @@ -27,8 +27,8 @@ is a core component of Access Analyzer and is available with all Access Analyzer ## CommandLineUtility Query Configuration -The CommandLineUtility Data Collector executes a command line utility and captures the output. It is -configured through the Command Line Utility Data Collector Wizard, which contains the following +The CommandLineUtility Data Collector executes a command line utility and captures the output. You +configure it through the Command Line Utility Data Collector Wizard, which contains the following pages: - Welcome @@ -42,5 +42,5 @@ pages: ![Command Line Utility Data Collector Wizard Welcome page](/images/accessanalyzer/12.0/admin/datacollector/commandlineutility/welcome.webp) -The Welcome page can be hidden by selecting the **Do not display this page the next time** checkbox -when the wizard is open and configuration settings are saved. +To hide the Welcome page, select the **Don't display this page the next time** checkbox while the +wizard is open, then save the configuration settings. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/commandlineutility/profileparameters.md b/docs/accessanalyzer/12.0/admin/datacollector/commandlineutility/profileparameters.md index d1ddd5a2aa..75598ebec4 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/commandlineutility/profileparameters.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/commandlineutility/profileparameters.md @@ -14,17 +14,17 @@ page. Profile parameters include: -- Profile Name – Name of the profile. If **Edit Profile** was selected on the Profile Type page, - then this is the name of an existing profile to be edited. If **Create a New Profile** was - selected, then this is the name of a new profile. +- Profile Name – Name of the profile. If you selected **Edit Profile** on the Profile Type page, + this is the name of the existing profile you want to edit. If you selected **Create a New + Profile**, this is the name of the new profile. - Path – Path of the utility (.exe) from the local or remote machine. If stored on the local - machine, give the local path. If the utility is located on multiple paths in the same machine, - each can be entered on a new line in this field. If the .exe file is present in the installed CLU - directory, then enter the utility name rather than the full path. + machine, give the local path. If the utility exists in multiple paths on the same machine, enter + each path on a new line in this field. If the .exe file is present in the installed Command Line + Utility (CLU) directory, then enter the utility name rather than the full path. - Start in path for task (Optional) – Working directory for the command line that executes the program or script. This should be either the path to the program or script file, or the path to - the files that are used by the executable file. -- Command Line – Command that the utility executes. If the utility is self-executable and does not + the files that the executable file uses. +- Command Line – Command that the utility executes. If the utility is self-executable and doesn't need a command, leave this field blank. -- Output File Name – Enter the desired name for the output file. By default, the output file name +- Output File Name – Enter the name you want for the output file. By default, the output file name matches the profile name. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/commandlineutility/profiletype.md b/docs/accessanalyzer/12.0/admin/datacollector/commandlineutility/profiletype.md index e529f60d3d..e65d474fac 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/commandlineutility/profiletype.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/commandlineutility/profiletype.md @@ -12,10 +12,10 @@ The Profile Type page contains options to select a new or existing profile. The options on the Profile Type page are: -- Select Profile – Allows you to change the properties of a profile from the results page -- Edit Profile – Allows you to edit a profile's execution options and properties. Enables the Define +- Select Profile – Change the properties of a profile from the results page +- Edit Profile – Edit a profile's execution options and properties. Enables the Define Fields and Script Editor pages. -- Create a New Profile – Allows you to create a new profile. Enables the Define Fields and Script +- Create a New Profile – Create a new profile. Enables the Define Fields and Script Editor pages. -The profile type selected may alter the availability of the subsequent wizard steps. +The profile type you select may affect the availability of the subsequent wizard steps. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/commandlineutility/results.md b/docs/accessanalyzer/12.0/admin/datacollector/commandlineutility/results.md index 0e03ec015a..2b525e12da 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/commandlineutility/results.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/commandlineutility/results.md @@ -6,11 +6,11 @@ sidebar_position: 60 # CLU: Results -The Results page is where the properties to be returned as columns in the results table are -selected. It is a wizard page for all profile types. +The Results page is where you select the properties to return as columns in the results table. +It's a wizard page for all profile types. ![Command Line Utility Data Collector Wizard Results page](/images/accessanalyzer/12.0/admin/datacollector/commandlineutility/results.webp) -Select one or more properties to be returned as columns in the results table. Click **Select All** -to select all of the properties, or click **Clear All** to clear all the currently selected +Select one or more properties to return as columns in the results table. Click **Select All** +to select all the properties, or click **Clear All** to clear all the selected properties. The available properties vary based on the selections on previous wizard pages. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/commandlineutility/scripteditor.md b/docs/accessanalyzer/12.0/admin/datacollector/commandlineutility/scripteditor.md index 1b7b4c5ec8..5e632d2a4e 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/commandlineutility/scripteditor.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/commandlineutility/scripteditor.md @@ -14,7 +14,7 @@ page is disabled when the **Select Profile** option is selected on the Profile T ![Command Line Utility Data Collector Wizard Script Editor page](/images/accessanalyzer/12.0/admin/datacollector/commandlineutility/scripteditor.webp) :::warning -Do not modify this page without guidance from Netwrix or the data may not be processed -by Access Analyzer. +Don't modify this page without guidance from Netwrix. Otherwise, Access Analyzer might not process +the data correctly. ::: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/commandlineutility/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/commandlineutility/summary.md index 4f4c8c6751..f341d0619c 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/commandlineutility/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/commandlineutility/summary.md @@ -6,11 +6,10 @@ sidebar_position: 70 # CLU: Summary -The Summary page provides a summary of the query that has been created or edited. It is a wizard -page for all profile types. +The Summary page summarizes the query you created or edited. It's a wizard page for all profile +types. ![Command Line Utility Data Collector Wizard Summary page](/images/accessanalyzer/12.0/admin/datacollector/commandlineutility/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Command Line Utility Data Collector Wizard to ensure that no -accidental clicks are saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** to +close the Command Line Utility Data Collector Wizard instead, so accidental clicks don't get saved. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/diskinfo/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/diskinfo/overview.md index 49f4875e42..19b0047875 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/diskinfo/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/diskinfo/overview.md @@ -6,8 +6,8 @@ sidebar_position: 100 # DiskInfo Data Collector -The DiskInfo Data Collector provides enumeration of disks and their associated properties. When -targeting the local host for a DiskInfo query, it is necessary to select the **Systems Default** +The DiskInfo Data Collector enumerates disks and their associated properties. When +targeting the local host for a DiskInfo query, select the **Systems Default** option as the connection profile. This data collector is a core component of Access Analyzer and is available with all Access Analyzer licenses. @@ -27,7 +27,7 @@ available with all Access Analyzer licenses. ## DiskInfo Query Configuration -The DiskInfo Data Collector is configured through the Disk Info wizard, which contains the following +You configure the DiskInfo Data Collector through the Disk Info wizard, which contains the following wizard pages: - Welcome @@ -37,5 +37,5 @@ wizard pages: ![Disk Info wizard Welcome page](/images/accessanalyzer/12.0/admin/datacollector/diskinfo/welcome.webp) -The Welcome page can be hidden by selecting the **Do not display this page the next time** checkbox -when the wizard is open and configuration settings are saved. +To hide the Welcome page, select the **Don't display this page the next time** checkbox while the +wizard is open, then save the configuration settings. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/diskinfo/results.md b/docs/accessanalyzer/12.0/admin/datacollector/diskinfo/results.md index c787516b08..50fb71882e 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/diskinfo/results.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/diskinfo/results.md @@ -6,14 +6,13 @@ sidebar_position: 20 # DiskInfo: Results -The Results page provides a checklist of the data that is available for return by the query. Any -number of options can be selected at once, but at least one must be selected in order to complete -the wizard. +The Results page provides a checklist of the data the query can return. You can select any number +of options at once, but you must select at least one to complete the wizard. ![Disk Info wizard Results page](/images/accessanalyzer/12.0/admin/datacollector/diskinfo/results.webp) -Properties can be selected individually, or you can use the **Select all** and **Clear all** -buttons. The table below describes the available options. +You can select properties individually, or use the **Select all** and **Clear all** +buttons. The following table describes the available options. | Checklist Result | Description | | ----------------------------- | ------------------------------------------------------------------------------------------------------------------- | diff --git a/docs/accessanalyzer/12.0/admin/datacollector/diskinfo/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/diskinfo/summary.md index f90909d017..8783f405b4 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/diskinfo/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/diskinfo/summary.md @@ -6,10 +6,9 @@ sidebar_position: 30 # DiskInfo: Summary -The Summary page displays a summary of the configured query. +The Summary page summarizes the configured query. ![Disk Info wizard Summary page](/images/accessanalyzer/12.0/admin/datacollector/diskinfo/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Disk Info Data Collector Wizard to ensure that no accidental clicks -are saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** to +close the Disk Info Data Collector Wizard instead, so accidental clicks don't get saved. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/diskinfo/targetdisks.md b/docs/accessanalyzer/12.0/admin/datacollector/diskinfo/targetdisks.md index b3937a48a2..b4c3149636 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/diskinfo/targetdisks.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/diskinfo/targetdisks.md @@ -6,27 +6,27 @@ sidebar_position: 10 # DiskInfo: Target Disks -The Target Disks page provides a selection of storage devices from which to return data from the -target host after a query. +The Target Disks page lists the storage devices you can select to return data from the target host +after a query. ![Disk Info wizard Target Disks page](/images/accessanalyzer/12.0/admin/datacollector/diskinfo/targetdisks.webp) -Use the options to select the desired target disk. +Use the options to select the target disk you want. -- The Enumerate all storage devices – Allows all internal drives to be scanned. In order to expand - the scan, two sub-options can be included together, separately, or not at all. +- Enumerate all storage devices – Scans all internal drives. To expand the scan, include either or + both of the following sub-options, or neither. - Include removable storage devices – Scans removable devices that are plugged into the target host - Include network storage devices – Scans mapped drives that exist through a connected network -- Single drive letter – Allows information to be collected from a single drive (`A:` through `Z:`) +- Single drive letter – Collects information from a single drive (`A:` through `Z:`) during a single query. This option includes both operating system drives and removable disks. - Enumerate all mount points (available for Windows 2003+ systems) – Targets any drive letter on the target host that points to a mapped share drive - Registry lookup – Provides the path of connection to gather information from the Access Analyzer - Registry Browser. By default, the local host will be targeted unless modified. The Registry value - are instructions for the data found within the subfolders of the registry. + Registry Browser. By default, Access Analyzer targets the local host unless you change it. The + Registry value are instructions for the data found within the subfolders of the registry. - The browse button **(…)** under the Registry lookup option opens the Access Analyzer Registry Browser window. Use the registry browser to find registry keys and values that are on a target @@ -43,8 +43,8 @@ environment. The configurable options on the Registry Browser are: -- Sample from Host – Host for which the Registry will be browsed. If this box is left blank, the - Registry on the local host is used. +- Sample from Host – Host that Access Analyzer browses for registry information. If you leave this + box blank, Access Analyzer uses the Registry on the local host. - 64-bit view – Default view is 32-bit. Select the 64-bit checkbox to switch to a 64-bit view. - Connect – Click **Connect** to browse the Registry - Table Columns – Select the Registry from the navigation pane to view keys in the table diff --git a/docs/accessanalyzer/12.0/admin/datacollector/dns/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/dns/overview.md index d9eefe5289..61801d383e 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/dns/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/dns/overview.md @@ -6,7 +6,7 @@ sidebar_position: 110 # DNS Data Collector -The DNS Data Collector provides information regarding DNS configuration and records. It is available +The DNS Data Collector provides information about DNS configuration and records. It is available with the Active Directory Solution. Both this data collector and the solution are available with a special Access Analyzer license. @@ -25,7 +25,7 @@ special Access Analyzer license. ## DNS Query Configuration -The DNS Data Collector is configured through the Domain Name System Data Collector Wizard, which +You configure the DNS Data Collector through the Domain Name System Data Collector Wizard, which contains the following wizard pages: - Welcome @@ -35,5 +35,5 @@ contains the following wizard pages: ![Domain Name System Data Collector Wizard Welcome page](/images/accessanalyzer/12.0/admin/datacollector/dns/welcome.webp) -The Welcome page can be hidden by selecting the Do not display this page the next time checkbox when -the wizard is open and configuration settings are saved. +To hide the Welcome page, select the Don't display this page the next time checkbox while the +wizard is open, then save the configuration settings. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/dns/results.md b/docs/accessanalyzer/12.0/admin/datacollector/dns/results.md index 87e3b77b9a..81b84234fa 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/dns/results.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/dns/results.md @@ -6,11 +6,11 @@ sidebar_position: 20 # DNS: Results -The Results page is where DNS properties to be gathered are selected. It is a wizard page for all +The Results page is where you select the DNS properties to gather. It's a wizard page for all categories. ![Domain Name System Data Collector Wizard Results page](/images/accessanalyzer/12.0/admin/datacollector/dns/results.webp) -Available properties can be selected individually, or the **Select All**, **Clear All**, and **Reset -to defaults** buttons can be used. All selected properties are gathered. Available properties vary -based on the category selected. +You can select available properties individually, or use the **Select All**, **Clear All**, and +**Reset to defaults** buttons. Access Analyzer gathers all selected properties. Available properties +vary based on the category selected. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/dns/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/dns/summary.md index 17b7207531..3d6a02d8c4 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/dns/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/dns/summary.md @@ -6,10 +6,9 @@ sidebar_position: 30 # DNS: Summary -The Summary page displays a summary of the configured query. It is a wizard page for all categories. +The Summary page summarizes the configured query. It's a wizard page for all categories. ![Domain Name System Data Collector Wizard Summary page](/images/accessanalyzer/12.0/admin/datacollector/dns/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Domain Name System Data Collector Wizard to ensure that no accidental -clicks are saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** to +close the Domain Name System Data Collector Wizard instead, so accidental clicks don't get saved. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/completion.md b/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/completion.md index 93cd66709f..5a04a6158b 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/completion.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/completion.md @@ -6,17 +6,17 @@ sidebar_position: 80 # DropboxAccess: Summary (Completion) -The Completion page, is where configuration settings are summarized. This page is a wizard page for +The Completion page summarizes the configuration settings. This page is a wizard page for all categories. ![Dropbox Access Auditor Data Collector Wizard Completion page](/images/accessanalyzer/12.0/admin/datacollector/dropboxaccess/completion.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Dropbox Access Auditor Data Collector Wizard ensuring that no -accidental clicks are saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** to +close the Dropbox Access Auditor Data Collector Wizard instead, so accidental clicks don't get +saved. :::tip -Remember, if an Access Token was generated, use it as the credential within the Connection +Remember, if you generated an Access Token, use it as the credential within the Connection Profile. Then assign it to the job group or job which will be scanning the targeted Dropbox environment. See the [Custom Dropbox Connection Profile & Host List](/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/configurejob.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/configurejob.md b/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/configurejob.md index c9968698eb..69a49f04da 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/configurejob.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/configurejob.md @@ -6,21 +6,21 @@ sidebar_position: 20 # Custom Dropbox Connection Profile & Host List -The DropboxAccess Data Collector requires a custom Connection Profile to be created and assigned to -the job or job group conducting the data collection. +The DropboxAccess Data Collector requires a custom Connection Profile that you create and assign to +the job or job group that collects the data. ## Connection Profile -Creating the Connection Profile requires an access token. The access token is generated on the Scan +Creating the Connection Profile requires an access token. You generate the access token on the Scan Options page of the Dropbox Access Auditor Data Collector Wizard. Create a Connection Profile and set the following information on the User Credentials window: - Select Account Type – Dropbox -- Password Storage – Application (Uses the configured Profile Security setting as selected at the +- Password Storage – Application (Uses the configured Profile Security setting as you selected it at the **Settings** > **Application** node. See the [Application](/docs/accessanalyzer/12.0/admin/settings/application/overview.md) topic for additional information.) -- Access Token – Copy and paste the Access Token after it has been generated from the Scan Options +- Access Token – Copy and paste the access token after you generate it on the Scan Options page of the Dropbox Access Auditor Data Collector Wizard. See the [DropboxAccess: Scan Options](/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/scanoptions.md) topic for additional information. @@ -28,6 +28,6 @@ See the [Connection](/docs/accessanalyzer/12.0/admin/settings/connection/overvie ## Host List -The host list should be set to: +Set the host list to: - Local host diff --git a/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/dlpauditsettings.md b/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/dlpauditsettings.md index da7ab3e38c..b331e3323d 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/dlpauditsettings.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/dlpauditsettings.md @@ -15,8 +15,8 @@ Configure the DLP audit settings: - Scan Performance: - - Don’t process files larger than – Limits the files to be scanned for sensitive content to - files smaller than the specified size + - Don’t process files larger than – Limits scanning for sensitive content to files smaller + than the specified size - File types to scan: @@ -27,13 +27,13 @@ Configure the DLP audit settings: the scan: - Store discovered sensitive data – Stores a copy of any potentially sensitive data that matches - the selected criteria in the Access Analyzer database. This copy can be used to check for - false positives, data that matches the selected criteria but is not actually sensitive. + the selected criteria in the Access Analyzer database. Use this copy to check for + false positives, data that matches the selected criteria but isn't actually sensitive. - Limit stored matches per criteria to [number] – Identifies the number of potentially sensitive - data matches that are copied to the database. The default is 5 matches. This option is - available only if the **Store discovered sensitive data** option is selected. + data matches copied to the database. The default is 5 matches. This option is available + only if you select the **Store discovered sensitive data** option. -- Perform differential scan of – Enables users to choose whether to employ incremental scanning: +- Perform differential scan of – Choose whether to employ incremental scanning: - Files modified since last scan – Scans only files modified since the last scan - Files modified since [date] – Only scans files modified after the specified date diff --git a/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/overview.md index 147801ab0b..79165f1f9d 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/overview.md @@ -7,10 +7,10 @@ sidebar_position: 120 # DropboxAccess Data Collector The DropboxAccess Data Collector audits access, group membership, and content within a Dropbox -environment. Dropbox can scan the contents of over 400 file types to discover which files contain -sensitive data using Sensitive Data Discovery. The DropboxAccess Data Collector has been -preconfigured within the Dropbox Solution. Both this data collector and the solution are available -with a special Access Analyzer license. See the +environment. Using Sensitive Data Discovery, Dropbox can scan the contents of over 400 file types +to discover which files contain sensitive data. The Dropbox Solution includes the preconfigured +DropboxAccess Data Collector. Both this data collector and the solution are available with a +special Access Analyzer license. See the [Dropbox Solution](/docs/accessanalyzer/12.0/solutions/dropbox/overview.md) topic for additional information. **Protocols** @@ -29,13 +29,13 @@ with a special Access Analyzer license. See the **Sensitive Data Discovery Considerations** -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the minimum amount -of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For example, if the job -is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are required (8x2=16). +If you run Sensitive Data Discovery (SDD) scans, increase the minimum amount of RAM. Each thread +requires a minimum of 2 additional GB of RAM per host. For example, if you configure the job to +scan 8 hosts at a time, it requires an extra 16 GB of RAM (8 x 2 = 16). ## Query Configuration -The DropboxAccess Data Collector is configured through the Dropbox Access Auditor Data Collector +You configure the DropboxAccess Data Collector through the Dropbox Access Auditor Data Collector Wizard. The wizard contains the following pages, which change based upon the query category selected: @@ -49,5 +49,5 @@ selected: ![Dropbox Access Auditor Data Collector Wizard Welcome page](/images/accessanalyzer/12.0/admin/datacollector/dropboxaccess/welcome.webp) -The Welcome page can be hidden by selecting the **Do not display this page the next time** checkbox -when the wizard is open and configuration settings are saved. +To hide the Welcome page, select the **Don't display this page the next time** checkbox while the +wizard is open, then save the configuration settings. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/scanoptions.md b/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/scanoptions.md index 7f54ec3143..6c80ba2611 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/scanoptions.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/scanoptions.md @@ -7,12 +7,12 @@ sidebar_position: 40 # DropboxAccess: Scan Options Use the Scan Options page to authorize Access Analyzer to generate an Access Token allowing the -DropboxAccess Data Collector to access and scan an organization’s Dropbox environment. The Access -Token is used as the credential in the Connection Profile. +DropboxAccess Data Collector to access and scan an organization’s Dropbox environment. The +Connection Profile uses the Access Token as its credential. :::note -The Access Token needs to be generated only once, prior to the first execution of any job -in which the DropboxAccess Data Collector is used in a query. +You only need to generate the Access Token once, before the first job that uses the DropboxAccess +Data Collector in a query. ::: @@ -21,7 +21,7 @@ The Scan Options page is a wizard page for the following categories: - Scan Dropbox Access - Scan for Sensitive Content -Follow the steps to create the Access Token: +To create the Access Token: ![Dropbox Access Auditor Data Collector Wizard Scan Options page](/images/accessanalyzer/12.0/admin/datacollector/dropboxaccess/scanoptions.webp) @@ -33,7 +33,7 @@ Follow the steps to create the Access Token: ![Copy Access Token](/images/accessanalyzer/12.0/admin/datacollector/dropboxaccess/scanoptionsaccesstoken.webp) -**Step 3 –** Once the Access Token has been generated, click **Copy to Clipboard**. Click **Next** +**Step 3 –** After Dropbox generates the Access Token, click **Copy to Clipboard**. Click **Next** to finish choosing the configuration options or click **Cancel** to close the Dropbox Access Auditor Data Collector Wizard. @@ -42,6 +42,5 @@ Create a Connection Profile using this access token as the credential. See the configuring the Dropbox credential. :::tip -Remember, assign this Connection Profile to the job group or job where the host assignment for the -Dropbox environment to be targeted has been assigned. +Assign this Connection Profile to the job group or job that targets the Dropbox environment. ::: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/selectdlpcriteria.md b/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/selectdlpcriteria.md index 73c8d1e390..99c3a92ee7 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/selectdlpcriteria.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/selectdlpcriteria.md @@ -11,7 +11,7 @@ sensitive data. It is a wizard page for the Scan for Sensitive Content category. ![Dropbox Access Auditor Data Collector Wizard Select DLP criteria page](/images/accessanalyzer/12.0/admin/datacollector/dropboxaccess/selectdlpcriteria.webp) -Select the checkbox next to each criteria to be included in the search for sensitive data. You can +Select the checkbox next to each criteria to include in the search for sensitive data. You can also use the **Select All** and **Clear All** buttons. The table contains the following types of criteria: @@ -19,7 +19,7 @@ The table contains the following types of criteria: - System Criteria – Lists pre-defined criteria - User Criteria – Lists user-defined criteria -Use the **Edit** button to access the Criteria Editor where user-defined criteria can be created or -customized. See the +Use the **Edit** button to access the Criteria Editor, where you can create or customize +user-defined criteria. See the [Sensitive Data Criteria Editor](/docs/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/overview.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/standardtables.md b/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/standardtables.md index 50a7d8d6e7..39e669b717 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/standardtables.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/standardtables.md @@ -12,7 +12,7 @@ DropboxAccess Data Collector writes data to these tables regardless of the job e ## Dropbox Access Auditing Tables & Views -These tables and their associated views are outlined below: +The following table lists these tables and their associated views: | Table | Details | | --------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | @@ -40,11 +40,11 @@ Data Collector: ## Dropbox Sensitive Data Discovery Auditing (SEEK) Tables & Views -These tables and their associated views are outlined below: +The following table lists these tables and their associated views: | Table | Details | | -------------------- | ------------------------------------------------------------------------------------------------------------------------ | -| SA_Dropbox_Criteria | Contains the sensitive data criteria which are selected for collection by the scan engine (data collector configuration) | +| SA_Dropbox_Criteria | Contains the sensitive data criteria the scan engine selects for collection (data collector configuration) | | SA_Dropbox_Matches | Contains rolled up aggregate counts of the sensitive data criteria matches found during the scan | | SA_Dropbox_MatchHits | Contains the actual sensitive data discovered within files which matched selected criteria | diff --git a/docs/accessanalyzer/12.0/admin/datacollector/entra/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/entra/overview.md index bd9a768ef6..2a3ae5eb08 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/entra/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/entra/overview.md @@ -7,7 +7,7 @@ sidebar_position: 130 # Entra Data Collector The Entra data collector collects Microsoft Entra roles information from the target Microsoft Entra -tenant. This data collector is preconfigured in the .Entra ID Inventory solution. +tenant. The .Entra ID Inventory solution includes this preconfigured data collector. Both this data collector and the .Entra Inventory solution are available with all Access Analyzer license options. See the @@ -43,7 +43,7 @@ information. ## Query Configuration -The Entra data collector is configured through the Entra Data Collector Wizard, which contains the +You configure the Entra data collector through the Entra Data Collector Wizard, which contains the following wizard pages: - [Entra: Scan options](/docs/accessanalyzer/12.0/admin/datacollector/entra/options.md) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/entra/results.md b/docs/accessanalyzer/12.0/admin/datacollector/entra/results.md index 6136cd82e3..169a1572f3 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/entra/results.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/entra/results.md @@ -6,9 +6,9 @@ sidebar_position: 20 # Entra: Results -The Results page is where the properties from Microsoft Entra ID to be gathered are selected. +Use the Results page to select the properties to gather from Microsoft Entra ID. ![Results page of the Entra Data Collector Wizard](/images/accessanalyzer/12.0/admin/datacollector/entra/results.webp) -Properties can be selected individually or the **Select All** and **Clear All** buttons can be used. -All selected properties are collected. +Select properties individually, or use the **Select All** and **Clear All** buttons. The Entra data +collector collects all selected properties. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/entra/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/entra/summary.md index 6b1e47622c..3dc52bf830 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/entra/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/entra/summary.md @@ -6,10 +6,9 @@ sidebar_position: 30 # Entra: Summary -The Summary page is where configuration settings are summarized. +The Summary page summarizes your configuration settings. ![Summary page of the Entra Data Collector Wizard](/images/accessanalyzer/12.0/admin/datacollector/entra/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Entra Data Collector Wizard to ensure that no accidental clicks are -saved. +Click **Finish** to save configuration changes. If you didn't make changes, click **Cancel** to +close the Entra Data Collector Wizard instead, so it doesn't save accidental clicks. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/eventlog.md b/docs/accessanalyzer/12.0/admin/datacollector/eventlog.md index d6d0d1796a..b94db281f8 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/eventlog.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/eventlog.md @@ -27,7 +27,7 @@ Analyzer licenses. ## EventLog Query Configuration -The EventLog Data Collector is configured through the Event Log Browser window. +You configure the EventLog Data Collector through the Event Log Browser window. ![Event Log Browser window](/images/accessanalyzer/12.0/admin/datacollector/eventlogbrowser.webp) @@ -39,8 +39,8 @@ In the Sample section, select from the following options: - Host – Enter a sample host that contains a log with the type of events desired for the query. Click **Connect** to generate a list of logs available for extraction. - - Log name – Select a log from the drop-down list. Events from the selected log are populated in - the table. + - Log name – Select a log from the dropdown list. Events from the selected log populate the + table. - From file @@ -51,7 +51,7 @@ In the Sample section, select from the following options: File path box :::note - A preview displays automatically if the folder icons is used to navigate to the log. + A preview displays automatically if you use the folder icon to navigate to the log. ::: @@ -62,11 +62,11 @@ In the Sample section, select from the following options: In the Search Criteria section, add a search filter to the table by configuring the following criteria: -- Event Source – Select the event source from the drop-down list. Typically, select **Any Source**. -- Even Type – Select the event type from the drop-down list. Typically, select **Any Type**. +- Event Source – Select the event source from the dropdown list. Typically, select **Any Source**. +- Even Type – Select the event type from the dropdown list. Typically, select **Any Type**. - Event ID – Enter the event ID for the type of event to search -Once the information above has been entered, click **Add** to add the configured event to the query. +After you enter the preceding information, click **Add** to add the configured event to the query. Add as many events as desired. - Latest event only – Select this checkbox to only search the latest event @@ -74,8 +74,8 @@ Add as many events as desired. Click the **Add** button to add the search filters to the table. Click the **Remove** button to remove search criteria from the filters. -- Event Date/Time – Enter the last number of hours the event time must be in. A value of `0` can be - used to specify any time. +- Event Date/Time – Enter the last number of hours the event time must be in. A value of `0` + specifies any time. - Retrieve oldest event – Select this checkbox to retrieve the oldest event - Retrieve latest event – Select this checkbox to retrieve the latest event @@ -83,24 +83,24 @@ Click **Apply Filter** to filter the list of sample events to the search criteri **Options** -In the Options section, select the desired processing options: +In the Options section, select the processing options you want: - Process offline logs only – Select this checkbox to process only offline logs - Process offline logs if required – Select this checkbox to process offline logs if needed -- Specify explicit path\mask for archives – Enabled if the **Process offline logs only** or - **Process offline logs if required** checkboxes are selected. Specify the path and name of the +- Specify explicit path\mask for archives – Available if you select the **Process offline logs + only** or **Process offline logs if required** checkbox. Specify the path and name of the archive. **Available Properties** -In the Available Properties section, select which properties will be collected by the browser. +In the Available Properties section, select which properties the browser collects. -- Add Icon – Add properties from those available in the list to add the properties to the search +- Add Icon – Add properties from the available list to the search - - The Description properties provide the ability to extract the bracketed pieces of information + - The Description properties let you extract the bracketed pieces of information found within the description and display each bracketed piece of information in its own column - Remove Icon – Use to remove properties from the search -Once all options have been configured, click **OK** to save changes and exit the browser. Click +Once you configure all options, click **OK** to save changes and exit the browser. Click **Cancel** to exit without saving. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/category.md b/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/category.md index 99148d9179..539d0b622c 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/category.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/category.md @@ -6,7 +6,7 @@ sidebar_position: 10 # EWSMailbox: Category -The Category page identifies which type of EWSMailbox information is retrieved during the scan. +The Category page identifies which type of EWSMailbox information the scan retrieves. ![EWS Mailbox Data Collector Wizard Category page](/images/accessanalyzer/12.0/admin/datacollector/ewsmailbox/category.webp) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/criteria.md b/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/criteria.md index 7e2c3e87d7..192ad4378a 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/criteria.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/criteria.md @@ -6,8 +6,8 @@ sidebar_position: 60 # EWSMailbox: Criteria -The Select DLP criteria for this scan page is where to select the criteria to use for the sensitive -data scan are selected. It is a wizard page for the Sensitive Data category. +Use the Select DLP criteria for this scan page to select the criteria for the sensitive data scan. +It is a wizard page for the Sensitive Data category. ![EWS Mailbox Data Collector Wizard Criteria page](/images/accessanalyzer/12.0/admin/datacollector/ewsmailbox/criteria.webp) @@ -20,8 +20,8 @@ The options on the Criteria page are: sensitive data criteria to scan for - Select All - Click **Select All** to enable all sensitive data criteria for scanning - Clear All - Click **Clear All** to remove all selections from the table -- Select the checkboxes next to the sensitive data criteria options to enable it to be scanned for - during job execution +- Select the checkboxes next to the sensitive data criteria options you want to scan during job + execution The table contains the following types of criteria: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/filter.md b/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/filter.md index 426ba14c79..d666852cb5 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/filter.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/filter.md @@ -15,13 +15,13 @@ the categories of: ![EWS Mailbox Data Collector Wizard Filter page](/images/accessanalyzer/12.0/admin/datacollector/ewsmailbox/filter.webp) -All folders and attachments are scanned by default. Scope the scan for specific folders and +By default, the scan includes all folders and attachments. Scope the scan for specific folders and attachments: -- Include Folders – Type the folder paths to filter the scan to specific mailbox folders -- Include Attachments – Type the attachment file names to filter to specific attachments -- Exclude Folders – Type the folder paths to exclude mailbox folders from the scan -- Exclude Attachments – Type the file names for the attachments to exclude attachments from the scan +- Include Folders – Enter the folder paths to filter the scan to specific mailbox folders +- Include Attachments – Enter the attachment file names to filter to specific attachments +- Exclude Folders – Enter the folder paths to exclude mailbox folders from the scan +- Exclude Attachments – Enter the file names for the attachments to exclude attachments from the scan Use `*` and `?` for matching wildcard and single characters. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/options.md b/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/options.md index b62c9147d5..fdd6f9b897 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/options.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/options.md @@ -27,7 +27,7 @@ Select the checkboxes to apply any desired scan options: - Scan archives – Scans for archived mailbox data - Scan recoverable items – Scans for recoverable items -- Authentication – Select an Authentication type from the drop down: +- Authentication – Select an Authentication type from the dropdown: - Negotiate - Basic diff --git a/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/overview.md index 895eb4a482..31b1db01f2 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/overview.md @@ -7,8 +7,8 @@ sidebar_position: 150 # EWSMailbox Data Collector The EWSMailbox Data Collector provides configuration options to scan mailbox contents, permissions, -and sensitive data, and is preconfigured within the Exchange Solution. Both this data collector and -the solution are available with a special Access Analyzer license. See the +and sensitive data. The Exchange Solution includes this preconfigured data collector. Both this +data collector and the solution are available with a special Access Analyzer license. See the [Exchange Solution](/docs/accessanalyzer/12.0/solutions/exchange/overview.md) topic for additional information. **Protocols** @@ -31,13 +31,13 @@ the solution are available with a special Access Analyzer license. See the **Sensitive Data Discovery Considerations** -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the minimum amount -of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For example, if the job -is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are required (8x2=16). +If you run Sensitive Data Discovery (SDD) scans, increase the minimum amount of RAM. Each thread +requires a minimum of 2 additional GB of RAM per host. For example, if you configure the job to +scan 8 hosts at a time, it requires an extra 16 GB of RAM (8 x 2 = 16). ## EWSMailbox Query Configuration -The EWSMailbox Data Collector is configured through the Exchange Mailbox Data Collector Wizard, +You configure the EWSMailbox Data Collector through the Exchange Mailbox Data Collector Wizard, which contains the following wizard pages: :::note diff --git a/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/results.md b/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/results.md index 7323da3876..5a1c12bf66 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/results.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/results.md @@ -6,15 +6,15 @@ sidebar_position: 90 # EWSMailbox: Results -Use the Results page to select which properties are gathered out of those available for the -category. It is a wizard page for all of the categories. +Use the Results page to select which properties to gather from those available for the category. +It is a wizard page for all of the categories. ![EWS Mailbox Data Collector Wizard Results page](/images/accessanalyzer/12.0/admin/datacollector/ewsmailbox/results.webp) Select criteria using the following options: -- Select the checkbox of any property to include it in the summary. All selected properties will be - gathered. +- Select the checkbox of any property to include it in the summary. The data collector gathers all + selected properties. :::note Available properties vary based on the category selected. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/scope.md b/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/scope.md index 7724a84759..a64cd456ca 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/scope.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/scope.md @@ -6,12 +6,12 @@ sidebar_position: 30 # EWSMailbox: Scope -The Mailbox scope settings page is used to select which mailboxes are searched by the scan. It is a -wizard page for all categories. +Use the Mailbox scope settings page to select which mailboxes the scan searches. It is a wizard +page for all categories. ![EWS Mailbox Data Collector Wizard Scope page](/images/accessanalyzer/12.0/admin/datacollector/ewsmailbox/scope.webp) -Select an option to specify which mailboxes are searched: +Select an option to specify which mailboxes to search: - All mailboxes – Search all mailboxes - Select mailboxes from list – Search only specific selected mailboxes. This option enables the diff --git a/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/scopeselect.md b/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/scopeselect.md index 2c2bfa0ec7..66f4d41a6f 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/scopeselect.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/scopeselect.md @@ -6,8 +6,8 @@ sidebar_position: 40 # EWSMailbox: Scope Select -The Scope select page is used to select specific mailboxes to scan. It is a wizard page for all -categories when the **Select mailboxes from list** option is selected on the +Use the Scope select page to select specific mailboxes to scan. This page is part of the wizard +for all categories when you select the **Select mailboxes from list** option on the [EWSMailbox: Scope](/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/scope.md) page. ![EWS Mailbox Data Collector Wizard Scope select page](/images/accessanalyzer/12.0/admin/datacollector/ewsmailbox/scopeselect.webp) @@ -15,8 +15,8 @@ categories when the **Select mailboxes from list** option is selected on the Use the following options to scope the scan to specific mailboxes: - Retrieve – Loads the list of mailboxes available for scanning in the Available box -- Add – Select mailboxes from the Available list and click to add them to the Selected box to be - scanned +- Add – Select mailboxes from the Available list and click to add them to the Selected box for + scanning - Select All – Selects all mailboxes in the list - Deselect All – Deselects all selected mailboxes from the list - Remove – Select mailboxes from the Selected box and click to remove them from the list diff --git a/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/sddoptions.md b/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/sddoptions.md index bcb47b8fa0..a94239d5ca 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/sddoptions.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/sddoptions.md @@ -6,8 +6,8 @@ sidebar_position: 50 # EWSMailbox: SDD Options -The Sensitive data scan options page is where options to be used for discovering sensitive data are -configured. It is a wizard page for the Sensitive Data category. +Use the Sensitive data scan options page to configure options for discovering sensitive data. It +is a wizard page for the Sensitive Data category. ![EWS Mailbox Data Collector Wizard SDD Options page](/images/accessanalyzer/12.0/admin/datacollector/ewsmailbox/sddoptions.webp) @@ -18,6 +18,6 @@ Select the applicable Sensitive data scan options: for discovered sensitive data :::note - This option is only available if **Store discovered sensitive data** is selected. + This option is only available if you select **Store discovered sensitive data**. ::: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/searchfilter/bodyoptions.md b/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/searchfilter/bodyoptions.md index a7bd77fafd..fddac5843e 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/searchfilter/bodyoptions.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/searchfilter/bodyoptions.md @@ -10,7 +10,7 @@ Use the BodyOptions page to select the size unit of messages. ![Filter Wizard BodyOptions page](/images/accessanalyzer/12.0/admin/datacollector/ewsmailbox/filterwizard/bodyoptions.webp) -Select the desired message size unit: +Select the message size unit you want: - KB - MB diff --git a/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/searchfilter/filterwizard.md b/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/searchfilter/filterwizard.md index 0810de8304..83657b512a 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/searchfilter/filterwizard.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/searchfilter/filterwizard.md @@ -22,7 +22,7 @@ Customize folder search conditions using the following options: of the template conditions :::note - The values present depends on the selections made in the Select conditions box. + The available values depend on the selections in the Select conditions box. ::: @@ -31,7 +31,7 @@ Customize folder search conditions using the following options: [MessageClasses Window ](#messageclasses-window) topic for additional information. - Click **over 90 Day ago** to open the Date Range Selection Window. See the [Date Range Selection Window](#date-range-selection-window) topic for additional information. - - Click **has attachment(s)** to convert the condition to **has no attachment(s)** and vice + - Click **has attachments** to convert the condition to **has no attachments** and vice versa ## MessageClasses Window @@ -45,7 +45,7 @@ Filter page. Determine MessageClass-related criteria using the following options: - To add a class, click **Add** -- Enter the desired Message Class in the corresponding textbox +- Enter the Message Class in the corresponding textbox - Click **Exact Match** to reveal a dropdown menu of other search criteria under Matching Strategy and select the preferred option: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/searchfilter/folderconditions.md b/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/searchfilter/folderconditions.md index 871f4c71eb..e86c9ab460 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/searchfilter/folderconditions.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/searchfilter/folderconditions.md @@ -21,7 +21,7 @@ Customize folder search conditions using the following options: of the template conditions :::note - The values present depends on the selections made in the Select conditions box. + The available values depend on the selections in the Select conditions box. ::: @@ -48,11 +48,11 @@ Use the Search Terms window to determine terms for the search. The Search Terms Determine terms for the search using the following options: -- Type the desired term into the upper text box and click **Add** to add the term to the lower text +- Enter the term into the upper text box and click **Add** to add the term to the lower text box, which adds the term to the search - Select a term in the lower text box, and click **Remove** to remove the term from the search - Click **Clear** to clear all terms from the lower box -- Select the desired qualifier option: +- Select the qualifier option you want: - Contains ALL of the following search terms (And) – Search only returns results containing all of the search terms diff --git a/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/searchfilter/messageconditions.md b/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/searchfilter/messageconditions.md index 16d0068b81..2727f39bcb 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/searchfilter/messageconditions.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/searchfilter/messageconditions.md @@ -29,7 +29,7 @@ Customize message search filter conditions using the following options: - Select conditions – To add it to the search, select any of the following conditions: :::note - The conditions that are available in the Select Conditions box depends on the selected + The available conditions in the Select Conditions box depend on the selected **Message category**. ::: @@ -63,7 +63,7 @@ Customize message search filter conditions using the following options: - Click **search terms** to open the Search Terms Window. See the [Search Terms Window (Message Conditions)](#search-terms-window-message-conditions) topic for additional information. - - Click **has attachment(s)** to convert the condition to **has no attachment(s)** and vice + - Click **has attachments** to convert the condition to **has no attachments** and vice versa ## MessageClasses Window (Message Conditions) @@ -76,7 +76,7 @@ opens if **specific** is clicked in the Edit Conditions box on the Message Condi Determine MessageClass-related criteria using the following options: - To add a class, click **Add** -- Enter the desired Message Class in the corresponding textbox +- Enter the Message Class in the corresponding textbox - Click **Exact Match** to reveal a dropdown menu of other search criteria under Matching Strategy and select the preferred option: @@ -113,11 +113,11 @@ Use the Search Terms window to determine terms for the search. The Search Terms Determine terms for the search using the following options: -- Type the desired term into the upper text box and click **Add** to add the term to the lower text +- Enter the term into the upper text box and click **Add** to add the term to the lower text box, which adds the term to the search - Select a term in the lower text box, and click **Remove** to remove the term from the search - Click **Clear** to clear all terms from the lower box -- Select the desired qualifier option: +- Select the qualifier option you want: - Contains ALL of the following search terms (And) – Search only returns results containing all of the search terms diff --git a/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/summary.md index 312154109e..ec551741b4 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/summary.md @@ -10,6 +10,5 @@ The Summary page displays a summary of the configured query. It wizard page for ![EWS Mailbox Data Collector Wizard Summary page](/images/accessanalyzer/12.0/admin/datacollector/ewsmailbox/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the EWS Mailbox Data Collector Wizard to ensure that no accidental clicks -are saved. +Click **Finish** to save configuration changes. If you didn't make changes, click **Cancel** to close +the EWS Mailbox Data Collector Wizard and avoid saving accidental clicks. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/critieria.md b/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/critieria.md index 9d6df7d0d6..be70ad078a 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/critieria.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/critieria.md @@ -20,8 +20,8 @@ The options on the Criteria page are: sensitive data criteria to scan for - Select All - Click **Select All** to enable all sensitive data criteria for scanning - Clear All - Click **Clear All** to remove all selections from the table -- Select the checkboxes next to the sensitive data criteria options to enable it to be scanned for - during job execution +- Select the checkboxes next to the sensitive data criteria options you want to scan for during job + execution The table contains the following types of criteria: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/filter.md b/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/filter.md index 6cb99fbc05..14a7d09f54 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/filter.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/filter.md @@ -15,13 +15,13 @@ the categories of: ![EWS Public Folder Data Collector Wizard Filter page](/images/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/filter.webp) -All folders and attachments are scanned by default. Scope the scan for specific folders and +By default, the scan includes all folders and attachments. Scope the scan for specific folders and attachments: -- Include Folders – Type the folder paths to filter the scan to specific mailbox folders -- Include Attachments – Type the attachment file names to filter to specific attachments -- Exclude Folders – Type the folder paths to exclude mailbox folders from the scan -- Exclude Attachments – Type the file names for the attachments to exclude attachments from the scan +- Include Folders – Enter the folder paths to filter the scan to specific mailbox folders +- Include Attachments – Enter the attachment file names to filter to specific attachments +- Exclude Folders – Enter the folder paths to exclude mailbox folders from the scan +- Exclude Attachments – Enter the file names for the attachments to exclude attachments from the scan Use `*` and `?` for matching wildcard and single characters. @@ -30,19 +30,19 @@ Use `*` and `?` for matching wildcard and single characters. - Limit attachments size to [numerical value] – Select to limit attachment size and define a threshold for maximum size of an attachment returned in the scan. The default value is 20000 KB. -Public folders can also be included or excluded from the scan by retrieving a list of public folders -and selecting the desired folders. +You can also include or exclude public folders from the scan by retrieving a list of public folders +and selecting the folders you want. -Follow the steps to filter the scan by selecting public folders from a list. +To filter the scan by selecting public folders from a list: ![Choose folder to include window on Filter settings page](/images/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/filterpublicfolders.webp) **Step 1 –** Click the **+** button to the right of the Include Folders or Exclude Folders box to open the Choose folders to include or Choose folders to exclude window. -**Step 2 –** Click **Retrieve** to load the list of public folders that can be selected. +**Step 2 –** Click **Retrieve** to load the list of available public folders. -**Step 3 –** Select the desired public folders and click **Add** to add the folders to the Include +**Step 3 –** Select the public folders you want and click **Add** to add the folders to the Include Folders or Exclude Folders list. -After the configuration changes are saved, scans are filtered by the selected public folders. +After you save the configuration changes, the scan uses the selected public folders as filters. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/options.md b/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/options.md index 6528ee4dcf..72666d9f56 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/options.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/options.md @@ -18,11 +18,11 @@ Select any desired scan options: :::info Use this option when scanning multiple Exchange environments with a single - job and the Connection Profile has multiple credentials in it. + job and the Connection Profile has multiple credentials. ::: -- Authentication – Select an Authentication type from the drop down: +- Authentication – Select an Authentication type from the dropdown: - Negotiate - Basic diff --git a/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/overview.md index e84363696b..a89659e016 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/overview.md @@ -31,9 +31,9 @@ collector and the solution are available with a special Access Analyzer license. **Sensitive Data Discovery Considerations** -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the minimum amount -of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For example, if the job -is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are required (8x2=16). +If you run Sensitive Data Discovery (SDD) scans, increase the minimum amount of RAM. Each thread +requires a minimum of 2 additional GB of RAM per host. For example, if you configure the job to scan +8 hosts at a time, the job requires an extra 16 GB of RAM (8x2=16). ## EWSPublicFolder Query Configuration @@ -41,7 +41,7 @@ The EWSPublicFolder Data Collector is configured through the Exchange Public Fol Wizard. The wizard contains the following pages: :::note -The Category selected may alter the subsequent steps displayed by the wizard. +The category you select may alter the steps the wizard displays next. ::: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/results.md b/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/results.md index 1175ee1ce1..12eb41e2ee 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/results.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/results.md @@ -6,15 +6,15 @@ sidebar_position: 70 # EWSPublicFolder: Results -The Results page is used to select which properties will be gathered out of those available for the -category. It is a wizard page for all of the categories. +Use the Results page to select which properties to gather from those available for the category. It +is a wizard page for all of the categories. ![EWS Public Folder Data Collector Wizard Results page](/images/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/results.webp) Select criteria using the following options: -- Select the checkbox of any property to include it in the summary. All selected properties will be - gathered. +- Select the checkbox of any property to include it in the summary. The scan gathers all selected + properties. :::note Available properties vary based on the category selected. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/sddoptions.md b/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/sddoptions.md index b582e8bcfd..397fb95dee 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/sddoptions.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/sddoptions.md @@ -6,8 +6,8 @@ sidebar_position: 30 # EWSPublicFolder: SDD Options -Use the Sensitive data scan options page to configure options to for discovering sensitive data. It -is a wizard page for the Sensitive Data category. +Use the Sensitive data scan options page to configure sensitive data discovery options. It is a +wizard page for the Sensitive Data category. ![EWS Public Folder Data Collector Wizard SDD Options page](/images/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/sddoptions.webp) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/searchfilter/bodyoptions.md b/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/searchfilter/bodyoptions.md index 053f6655d5..1d114d9017 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/searchfilter/bodyoptions.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/searchfilter/bodyoptions.md @@ -6,11 +6,11 @@ sidebar_position: 40 # EWSPublicFolder FW: BodyOptions -The BodyOptions page is where the size of messages is selected. +Use the BodyOptions page to select the message size unit. ![Filter Wizard BodyOptions page](/images/accessanalyzer/12.0/admin/datacollector/ewsmailbox/filterwizard/bodyoptions.webp) -Select the desired message size unit: +Select the message size unit: - KB - MB diff --git a/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/searchfilter/filterwizard.md b/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/searchfilter/filterwizard.md index 894b76e3d2..c44acbd1de 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/searchfilter/filterwizard.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/searchfilter/filterwizard.md @@ -22,7 +22,7 @@ Customize folder search conditions using the following options: of the template conditions :::note - The values present depends on the selections made in the Select conditions box. + The available values depend on the selections in the Select conditions box. ::: @@ -31,7 +31,7 @@ Customize folder search conditions using the following options: [MessageClasses Window](#messageclasses-window) topic for additional information. - Click **over 90 Day ago** to open the Date Range Selection Window. See the [Date Range Selection Window](#date-range-selection-window) - - Click **has attachment(s)** to convert the condition to **has no attachment(s)** and vice + - Click **has attachments** to convert the condition to **has no attachments** and vice versa ## MessageClasses Window @@ -45,7 +45,7 @@ Filter page. Determine MessageClass-related criteria using the following options: - To add a class, click **Add** -- Enter the desired Message Class in the corresponding textbox +- Enter the Message Class in the corresponding textbox - Click **Exact Match** to reveal a dropdown menu of other search criteria under Matching Strategy and select the preferred option: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/searchfilter/folderconditions.md b/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/searchfilter/folderconditions.md index e449849ce0..03ee77d16e 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/searchfilter/folderconditions.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/searchfilter/folderconditions.md @@ -6,7 +6,7 @@ sidebar_position: 20 # EWSPublicFolder FW: Folder Conditions -The Folder Conditions page is where folder-related filter criteria can be applied to the search. +Use the Folder Conditions page to apply folder-related filter criteria to the search. ![Filter Wizard Folder Conditions page](/images/accessanalyzer/12.0/admin/datacollector/ewsmailbox/filterwizard/folderconditions.webp) @@ -21,7 +21,7 @@ Customize folder search conditions using the following options: of the template conditions :::note - The values present depends on the selections made in the Select conditions box. + The available values depend on the selections in the Select conditions box. ::: @@ -48,11 +48,11 @@ Use the Search Terms window to determine terms for the search. The Search Terms Determine terms for the search using the following options: -- Type the desired term into the upper text box and click **Add** to add the term to the lower text +- Enter the term into the upper text box and click **Add** to add the term to the lower text box, which adds the term to the search - Select a term in the lower text box, and click **Remove** to remove the term from the search - Click **Clear** to clear all terms from the lower box -- Select the desired qualifier option: +- Select a qualifier option: - Contains ALL of the following search terms (And) – Search only returns results containing all of the search terms diff --git a/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/searchfilter/messageconditions.md b/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/searchfilter/messageconditions.md index 3311ddb860..b7bb83f926 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/searchfilter/messageconditions.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/searchfilter/messageconditions.md @@ -29,7 +29,7 @@ Customize message search filter conditions using the following options: - Select conditions – To add it to the search, select any of the following conditions: :::note - The conditions that are available in the Select Conditions box depends on the selected + The available conditions in the Select Conditions box depend on the selected **Message category**. ::: @@ -51,7 +51,7 @@ Customize message search filter conditions using the following options: of the template conditions :::note - The values present depends on the selections made in the Select conditions box. + The available values depend on the selections in the Select conditions box. ::: @@ -61,7 +61,7 @@ Customize message search filter conditions using the following options: [Date Range Selection Window](#date-range-selection-window) topic for additional information. - Click **search terms** to open the Search Terms Window. See the [Search Terms Window](#search-terms-window) topic for additional information. - - Click **has attachment(s)** to convert the condition to **has no attachment(s)** and vice + - Click **has attachments** to convert the condition to **has no attachments** and vice versa ## MessageClasses Window @@ -74,7 +74,7 @@ opens if **specific** is clicked in the Edit Conditions box on the Message Condi Determine MessageClass-related criteria using the following options: - To add a class, click **Add** -- Enter the desired Message Class in the corresponding textbox +- Enter the Message Class in the corresponding textbox - Click **Exact Match** to reveal a dropdown menu of other search criteria under Matching Strategy and select the preferred option: @@ -111,11 +111,11 @@ Use the Search Terms window to determine terms for the search. The Search Terms Determine terms for the search using the following options: -- Type the desired term into the upper text box and click **Add** to add the term to the lower text +- Enter the term into the upper text box and click **Add** to add the term to the lower text box, which adds the term to the search - Select a term in the lower text box, and click **Remove** to remove the term from the search - Click **Clear** to clear all terms from the lower box -- Select the desired qualifier option: +- Select a qualifier option: - Contains ALL of the following search terms (And) – Search only returns results containing all of the search terms diff --git a/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/summary.md index cb142c9d42..1bff0b6a9c 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/summary.md @@ -10,6 +10,6 @@ The Summary page displays a summary of the configured query. It wizard page for ![EWS Public Folder Data Collector Wizard Summary page](/images/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the EWS Public Folder Data Collector Wizard to ensure that no accidental -clicks are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** to close +the EWS Public Folder Data Collector Wizard. This is a best practice to avoid saving accidental +clicks. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchange2k/category.md b/docs/accessanalyzer/12.0/admin/datacollector/exchange2k/category.md index 5d34190909..0ecf589928 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchange2k/category.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchange2k/category.md @@ -28,7 +28,7 @@ focus: - Recipient Update Services - Message Delivery – System-wide message settings - Instant Messaging – Instant messaging settings - - Exchange Mailbox Store Logons – The users currently logged on to Microsoft Exchange 2007 and + - Exchange Mailbox Store Logons – The users logged on to Microsoft Exchange 2007 and 2010 - Exchange 2007/2010 Hub Transport Configuration diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchange2k/mapisettings.md b/docs/accessanalyzer/12.0/admin/datacollector/exchange2k/mapisettings.md index 656c38cea8..5f15806097 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchange2k/mapisettings.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchange2k/mapisettings.md @@ -6,11 +6,11 @@ sidebar_position: 40 # Exchange2K: MAPI Settings -The MAPI Settings page is used to enter configurations to connect to target Exchange servers. By -default, Access Analyzer connects to Exchange using System Attendant. For Exchange 2010 and 2013, a -mailbox and a client access server need to be entered in order to make a MAPI connection. These -settings only need to be configured if not configured at the Global Settings level. It is a wizard -page for the categories of: +Use the MAPI Settings page to enter configurations to connect to target Exchange servers. By +default, Access Analyzer connects to Exchange using System Attendant. For Exchange 2010 and 2013, +enter a mailbox and a client access server to make a MAPI connection. Configure these settings only +if you haven't configured them at the Global Settings level. It is a wizard page for the categories +of: - Exchange Organization > Users - Mailbox Stores diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchange2k/options.md b/docs/accessanalyzer/12.0/admin/datacollector/exchange2k/options.md index 7d5826b45b..a46d6101ad 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchange2k/options.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchange2k/options.md @@ -26,7 +26,7 @@ Configure the Options step using the following options: - Concatenated – Return the data in a continuous string without gaps - - Delimiter – Enter the desired delimiter to be used between values + - Delimiter – Enter the delimiter to use between values - First-value only – Only display the first value diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchange2k/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/exchange2k/overview.md index fbedbdf3b1..4c7026620c 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchange2k/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchange2k/overview.md @@ -7,12 +7,12 @@ sidebar_position: 170 # Exchange2K Data Collector The Exchange2K Data Collector extracts configuration details from Exchange organizations for -versions 2003 and later. This is a MAPI-based data collector which requires the **Settings** > -**Exchange** node to be enabled and configured. See the [Exchange](/docs/accessanalyzer/12.0/admin/settings/exchange.md) topic +versions 2003 and later. This is a MAPI-based data collector which requires you to enable and +configure the **Settings** > **Exchange** node. See the [Exchange](/docs/accessanalyzer/12.0/admin/settings/exchange.md) topic for additional information. -The Exchange2K Data Collector has been preconfigured within the Exchange Solution. Both this data -collector and the solution are available with a special Access Analyzer license. See the +Access Analyzer preconfigures the Exchange2K Data Collector within the Exchange Solution. Both this +data collector and the solution are available with a special Access Analyzer license. See the [Exchange Solution](/docs/accessanalyzer/12.0/solutions/exchange/overview.md) topic for additional information. **Protocols** @@ -38,7 +38,7 @@ collector and the solution are available with a special Access Analyzer license. ## Exchange2K Query Configuration -The Exchange2K Data Collector is configured through the Exchange 2K+ Data Collector Wizard, which +Configure the Exchange2K Data Collector through the Exchange 2K+ Data Collector Wizard, which contains the following wizard pages: - Welcome @@ -51,5 +51,5 @@ contains the following wizard pages: ![Exchange 2K+ Data Collector Wizard Welcome page](/images/accessanalyzer/12.0/admin/datacollector/exchange2k/welcome.webp) -The Welcome page can be hidden by selecting the **Do not show this page the next time** checkbox -when the wizard is open and configuration settings are saved. +To hide the Welcome page, select the **Don't show this page the next time** checkbox when the +wizard is open and configuration settings are saved. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchange2k/results.md b/docs/accessanalyzer/12.0/admin/datacollector/exchange2k/results.md index 39dbffcdd4..e39546b265 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchange2k/results.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchange2k/results.md @@ -6,12 +6,12 @@ sidebar_position: 30 # Exchange2K: Results -The Results page is where properties that will be gathered are selected. It is a wizard page for +Use the Results page to select the properties to gather. It is a wizard page for all. ![Exchange 2K+ Data Collector Wizard Results page](/images/accessanalyzer/12.0/admin/datacollector/exchange2k/results.webp) -Properties can be selected individually or the **Check All**, **Uncheck All**, or **Reset Defaults** -buttons can be used. All Selected properties will be gathered. Click **Expand All** to expand all +Select properties individually, or use the **Check All**, **Uncheck All**, or **Reset Defaults** +buttons. Access Analyzer gathers all selected properties. Click **Expand All** to expand all properties, or **Collapse All** to collapse all properties. Available properties vary based on the category selected. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchange2k/scope.md b/docs/accessanalyzer/12.0/admin/datacollector/exchange2k/scope.md index f5b3529185..b9982a96f3 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchange2k/scope.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchange2k/scope.md @@ -6,7 +6,7 @@ sidebar_position: 20 # Exchange2K: Scope -The Scope page is used to define where to search. It is a wizard page for the categories of: +Use the Scope page to define where to search. It is a wizard page for the categories of: - Exchange Organization > Users - Exchange Organization > Groups diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchange2k/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/exchange2k/summary.md index 4f1206c542..260070412a 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchange2k/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchange2k/summary.md @@ -11,6 +11,5 @@ categories. ![Exchange 2K+ Data Collector Wizard Summary page](/images/accessanalyzer/12.0/admin/datacollector/exchange2k/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Exchange 2K+ Data Collector Wizard to ensure that no accidental clicks -are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** to close +the Exchange 2K+ Data Collector Wizard. This is a best practice to avoid saving accidental clicks. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangemailbox/options.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangemailbox/options.md index 1ea28ce66c..6d6b5154d7 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangemailbox/options.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangemailbox/options.md @@ -16,7 +16,7 @@ the following categories: ![Exchange Mailbox Data Collector Wizard Options page](/images/accessanalyzer/12.0/admin/datacollector/exchangemailbox/options.webp) -The following options can be configured: +Configure the following options: :::note Options available vary based upon the category selected. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangemailbox/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangemailbox/overview.md index 6a74d6033a..1c12f8b6f2 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangemailbox/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangemailbox/overview.md @@ -8,7 +8,7 @@ sidebar_position: 180 The ExchangeMailbox Data Collector extracts configuration details from the Exchange Store to provide statistical, content, permission, and sensitive data reporting on mailboxes. This is a MAPI-based -data collector which requires the **Settings** > **Exchange** node to be enabled and configured. See +data collector which requires you to enable and configure the **Settings** > **Exchange** node. See the [Exchange](/docs/accessanalyzer/12.0/admin/settings/exchange.md) topic for additional information. The ExchangeMailbox Data Collector is available with a special Access Analyzer license. See the @@ -32,13 +32,13 @@ The ExchangeMailbox Data Collector is available with a special Access Analyzer l **Sensitive Data Discovery Considerations** -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the minimum amount -of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For example, if the job -is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are required (8x2=16). +If you run Sensitive Data Discovery (SDD) scans, increase the minimum amount of RAM. Each thread +requires a minimum of 2 additional GB of RAM per host. For example, if you configure the job to scan +8 hosts at a time, the job requires an extra 16 GB of RAM (8x2=16). ## ExchangeMailbox Query Configuration -The ExchangeMailbox Data Collector is configured through the Exchange Mailbox Data Collector Wizard, +Configure the ExchangeMailbox Data Collector through the Exchange Mailbox Data Collector Wizard, which contains the following wizard pages: - Welcome @@ -60,12 +60,12 @@ Select one of the following options for the connection setting: - Use Global setting – The configured Global Setting is displayed next to this checkbox. Select the checkbox to use the global setting. -- System Attendant (2003 & 2007) – Enabled when the **Use Global Setting** checkbox is not selected. +- System Attendant (2003 & 2007) – Enabled when the **Use Global Setting** checkbox isn't selected. Select this option to use System Attendant (2003 & 2007) for the connection. - Use the mailbox associated with the Windows account that Access Analyzer is run with – Enabled - when the **Use Global Setting** checkbox is not selected. Select this option to use the mailbox + when the **Use Global Setting** checkbox isn't selected. Select this option to use the mailbox associated with the Windows account that Access Analyzer is run with for the connection. -- Exchange Mailbox (2010 and newer) – Enabled when the **Use Global Setting** checkbox is not +- Exchange Mailbox (2010 and newer) – Enabled when the **Use Global Setting** checkbox isn't selected. Select this option to use an Exchange Mailbox (2010 and newer) for the connection. The Client Access Server must be entered unless specified in the Global Settings. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangemailbox/properties.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangemailbox/properties.md index 8af6c3c019..8c36019d8e 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangemailbox/properties.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangemailbox/properties.md @@ -6,13 +6,13 @@ sidebar_position: 30 # ExchangeMailbox: Properties -The Properties page is where properties that will be gathered are selected. The available properties +Use the Properties page to select the properties to gather. The available properties depend on the category selected. It is a wizard page for all of the categories. ![Exchange Mailbox Data Collector Wizard Properties page](/images/accessanalyzer/12.0/admin/datacollector/exchangemailbox/properties.webp) -Properties can be selected individually or you can use the Select All, Clear All, and Reset All -buttons. All selected properties will be gathered. Click **Message Classes** to open the Message +Select properties individually, or use the **Select All**, **Clear All**, and **Reset All** +buttons. Access Analyzer gathers all selected properties. Click **Message Classes** to open the Message classes filters window. ![Message classes filters window](/images/accessanalyzer/12.0/admin/datacollector/exchangemailbox/messageclassesfilterswindow.webp) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangemailbox/scope.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangemailbox/scope.md index 0c1e9ac973..f3350c3a8c 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangemailbox/scope.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangemailbox/scope.md @@ -6,13 +6,13 @@ sidebar_position: 20 # ExchangeMailbox: Scope -The Scope page is used to define which mailboxes are to be queried. It is a wizard page for all of +Use the Scope page to define which mailboxes to query. It is a wizard page for all of the categories. ![Exchange Mailbox Data Collector Wizard Scope page](/images/accessanalyzer/12.0/admin/datacollector/exchangemailbox/scope.webp) -At the top, configure the mailboxes to be queried. The selected option changes how the mailboxes are -identified for scoping. +At the top, configure which mailboxes to query. The selected option determines how Access Analyzer +identifies mailboxes for scoping. - All mailboxes – Searches all mailboxes - Selected mailboxes from server – Retrieves all mailboxes in the Exchange organization, making them @@ -23,7 +23,7 @@ identified for scoping. - Retrieve – Enter the server and select Retrieve to display the list of mailboxes on that server - - Add – Select the desired mailboxes to add to the query. The added mailboxes display in the + - Add – Select the mailboxes to add to the query. The added mailboxes display in the **Selected mailboxes** list. - Remove – Deletes selected mailboxes from the list - Select All – Click the Select All icon to select all mailboxes in the list diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangemailbox/sddcriteria.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangemailbox/sddcriteria.md index 88607ab0b8..64ab7a2997 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangemailbox/sddcriteria.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangemailbox/sddcriteria.md @@ -6,13 +6,13 @@ sidebar_position: 40 # ExchangeMailbox: SDD Criteria -The SDD Criteria page is where criteria to be used for discovering sensitive data are configured. It +Use the SDD Criteria page to configure the criteria for discovering sensitive data. It is a wizard page for the Mailbox sensitive data discovery category. ![Exchange Mailbox Data Collector Wizard SDD Criteria page](/images/accessanalyzer/12.0/admin/datacollector/exchangemailbox/sddcriteria.webp) -Select the checkbox for the criteria to be used to search for sensitive data. Criteria can also be -selected using the **Select All** and **Select None** buttons. +Select the checkbox for the criteria to use to search for sensitive data. You can also select +criteria using the **Select All** and **Select None** buttons. The table contains the following types of criteria: @@ -24,8 +24,8 @@ The table contains the following types of criteria: for additional information. - Store discovered sensitive data – Stores the potentially sensitive data that matches the selected criteria in the Access Analyzer database. Select this checkbox to store a copy of the criteria - match data. This copy can be used to check for false positives, data that matches the selected - criteria but is not actually sensitive. + match data. Use this copy to check for false positives, data that matches the selected + criteria but isn't actually sensitive. - Limit stored matches per criteria to [number] – Identifies the number of potentially sensitive data matches that are copied to the database. The default is 5 matches. This option is only available if the **Store discovered sensitive data** option is selected. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangemailbox/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangemailbox/summary.md index 7fce091d37..670f438dfd 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangemailbox/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangemailbox/summary.md @@ -10,6 +10,6 @@ The Summary page displays a summary of the configured query. It wizard page for ![Exchange Mailbox Data Collector Wizard Summary page](/images/accessanalyzer/12.0/admin/datacollector/exchangemailbox/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Exchange Mailbox Data Collector Wizard to ensure that no accidental -clicks are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** to close +the Exchange Mailbox Data Collector Wizard. This is a best practice to avoid saving accidental +clicks. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/category.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/category.md index 8ff3538ed8..ab7cb5ce8b 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/category.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/category.md @@ -6,7 +6,7 @@ sidebar_position: 10 # ExchangeMetrics: Category -The Category page is used to identify the type of Exchange Metrics information to retrieve. +Use the Category page to identify the type of Exchange Metrics information to retrieve. ![Exchange Metrics Data Collector Wizard Category page](/images/accessanalyzer/12.0/admin/datacollector/exchangemetrics/category.webp) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/collectmode.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/collectmode.md index 814a053cc3..8bff99cd4a 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/collectmode.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/collectmode.md @@ -6,7 +6,7 @@ sidebar_position: 40 # ExchangeMetrics: Collect Mode -The Collect Mode page is where to set the collection mode. It is a wizard page for the categories +Use the Collect Mode page to set the collection mode. It is a wizard page for the categories of: - Server Volume @@ -24,10 +24,10 @@ of: ![Exchange Metrics Data Collector Wizard Collect Mode page](/images/accessanalyzer/12.0/admin/datacollector/exchangemetrics/collectmode.webp) -There are two types of collection modes: +Two types of collection modes are available: - Query Summary Data Only – In this mode, the applet gathers only existing summary data and returns - it to the Access Analyzer Console. In order to process Exchange tracking log files, another + it to the Access Analyzer Console. to process Exchange tracking log files, another instance of the applet must be configured. - Process Exchange Tracking Logs and Query Summary Data – In this mode, the applet processes missing summary data and returns it to the Access Analyzer Console. This mode includes an additional diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/messageactivityfilter.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/messageactivityfilter.md index 366826697f..ce24f9ee83 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/messageactivityfilter.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/messageactivityfilter.md @@ -7,8 +7,8 @@ sidebar_position: 80 # ExchangeMetrics: Message Activity Filter The Message Activity Filter page configures which domains the data collector should return mail flow -from specific senders and to specific recipients. For example, if `@netwrix.com` is entered in the -Senders list and `@netwrix.com` in the Recipients list, message activity will be returned only for +from specific senders and to specific recipients. For example, if you enter `@netwrix.com` in the +Senders list and `@netwrix.com` in the Recipients list, the filter returns message activity only for mail sent to and received from an `@netwrix.com` address. It is a wizard page for the categories of: - User’s Message Activity @@ -18,9 +18,8 @@ mail sent to and received from an `@netwrix.com` address. It is a wizard page fo Configure the Message Activity Filter using the following options: -- Add – To add a filter to the desired category, click **Add** in the desired category to add an - entry to that category -- Select **Exact Match** in the added filter to reveal a drop-down list with the following condition +- Add – To add a filter to a category, click **Add** in that category to add an entry to it +- Select **Exact Match** in the added filter to reveal a dropdown list with the following condition options: - Exact matches @@ -30,7 +29,7 @@ Configure the Message Activity Filter using the following options: - Kind – Select **(Custom…)** to open the Custom Filter menu. The Custom Filter menu provides options to create and configure other filters. -- Value – Type the filter to be applied +- Value – Enter the filter to apply -The columns in the entry tables can be sorted and or filtered, using the same sorting and filtering -methods of Access Analyzer data grids. The **Remove** option will delete a selected filter. +You can sort and filter the columns in the entry tables using the same methods as Access Analyzer +data grids. The **Remove** option will delete a selected filter. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/messagesizes.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/messagesizes.md index 2b634d0a75..5d0f2c4b40 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/messagesizes.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/messagesizes.md @@ -6,14 +6,14 @@ sidebar_position: 60 # ExchangeMetrics: Message Sizes -The Message Sizes page is used to configure message size frames for which to return summary metrics +Use the Message Sizes page to configure message size frames for which to return summary metrics by server. It is a wizard page for the category of: - Message Size Statistics Custom. ![Exchange Metrics Data Collector Wizard Message Sizes page](/images/accessanalyzer/12.0/admin/datacollector/exchangemetrics/messagesizes.webp) -Configure the desired message size frames using the following options: +Configure the message size frames using the following options: - Frame name – Name the configured message size parameters. Can either be entered manually or a default will populate when query limits are set. @@ -27,6 +27,6 @@ For example, a **Start** value of **1** and an **End** value of **2** returns me value of **5** with the **Infinite** checkbox selected retrieves all messages which are 5 megabytes or larger. -Once the frame is configured, click **Add**. The configured message size frame will appear in the -list. Multiple frames can be configured. Select a frame and click **Replace** to modify an existing +After you configure the frame, click **Add**. The configured message size frame will appear in the +list. You can configure multiple frames. Select a frame and click **Replace** to modify an existing frame. Use **Remove** to delete an existing frame. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/options.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/options.md index aa25e70e56..726f42f26c 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/options.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/options.md @@ -43,7 +43,7 @@ Available options vary depending on Category selected. - Applet Logging - Enable Logging – Enables the applet to log - - Applet log level – Select the desired log level using the dropdown list: + - Applet log level – Select the log level using the dropdown list: - None - Debug diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/overview.md index 50cdf07ec4..8568edf7f3 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/overview.md @@ -29,7 +29,7 @@ data collector and the solution are available with a special Access Analyzer lic **Permissions** -- Member of the local Administrator group on the targeted Exchange server(s) +- Member of the local Administrator group on the targeted Exchange servers See the [Exchange Mail-Flow Permissions](/docs/accessanalyzer/12.0/requirements/exchange/support/mailflow.md) topic for additional information. @@ -57,5 +57,5 @@ which contains the following wizard pages: ![Exchange Metrics Data Collector Wizard Welcome page](/images/accessanalyzer/12.0/admin/datacollector/exchangemetrics/welcome.webp) -The Welcome page can be hidden by checking the **Do not display this page the next time** box when +To hide the Welcome page, check the **Don't display this page the next time** box when the wizard is open and configuration settings are saved. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/results.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/results.md index 96c1759133..5746f2799e 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/results.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/results.md @@ -6,11 +6,10 @@ sidebar_position: 30 # ExchangeMetrics: Results -The Results page is where properties that will be gathered are selected. It is a wizard page for all +The Results page is where you select the properties to gather. It is a wizard page for all of the categories. ![Exchange Metrics Data Collector Wizard Results page](/images/accessanalyzer/12.0/admin/datacollector/exchangemetrics/results.webp) -Properties can be selected individually or the **Check All**, **Uncheck All**, or **Reset Defaults** -buttons can be used. Click **Expand All** to expand all property categories. All selected properties -will be gathered. Available properties vary based on the category selected. +You can select properties individually, or use the **Check All**, **Uncheck All**, or **Reset Defaults** +buttons. Click **Expand All** to expand all property categories. The data collector gathers all selected properties. Available properties vary based on the category selected. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/scope.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/scope.md index 23eefa02f6..ca3312f919 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/scope.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/scope.md @@ -6,7 +6,7 @@ sidebar_position: 20 # ExchangeMetrics: Scope -The Scope page is used to define where to search. It is a wizard page for the categories of: +Use the Scope page to define where to search. It is a wizard page for the categories of: - Server Volume - Internal Traffic Summary @@ -26,8 +26,8 @@ The Scope page is used to define where to search. It is a wizard page for the ca Define the scope of the query using the following options: -- Return data for section – Select the time period for which data will be collected. GMT time is - used by Exchange Metrics to calculate the result. +- Return data for section – Select the time period for which to collect data. Exchange Metrics + uses GMT time to calculate the result. - Today - Yesterday @@ -37,11 +37,11 @@ Define the scope of the query using the following options: - Last Month - Last [number] days - Within time frame: - - From [calendar date] to [calendar date] – Use the drop-down arrows to select calendar dates. + - From [calendar date] to [calendar date] – Use the dropdown arrows to select calendar dates. - Return results section – Select the table design for the collected data - - One row for – Use the drop-down list to select one of the following options: + - One row for – Use the dropdown list to select one of the following options: - All period - Day @@ -49,4 +49,4 @@ Define the scope of the query using the following options: - Month - Add summary values as last row – Select this checkbox to add summary values as the last row. - This option is enabled when **Day**, **Week**, or **Month** are selected. + This option is enabled when you select **Day**, **Week**, or **Month**. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/summary.md index b0d9dd37b2..7da436dd6d 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/summary.md @@ -11,6 +11,5 @@ categories. ![Exchange Metrics Data Collector Wizard Summary page](/images/accessanalyzer/12.0/admin/datacollector/exchangemetrics/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Exchange Metrics Data Collector Wizard to ensure that no accidental -clicks are saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** +to close the Exchange Metrics Data Collector Wizard and avoid saving accidental clicks. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/timeframes.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/timeframes.md index 72a36f6ef4..92943900ba 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/timeframes.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/timeframes.md @@ -6,14 +6,14 @@ sidebar_position: 50 # ExchangeMetrics: Time Frames -The Time Frames page is used to configure message delivery time frames for which to return summary +Use the Time Frames page to configure message delivery time frames for which to return summary metrics by server. It is a wizard page for the category of: - Delivery Time Custom. ![Exchange Metrics Data Collector Wizard Time Frames page](/images/accessanalyzer/12.0/admin/datacollector/exchangemetrics/timeframes.webp) -Configure the desired time frames using the following options: +Configure the time frames using the following options: - Frame name – Name the configured time frame. Can either be entered manually or a default will populate when frame limits are set. @@ -32,6 +32,6 @@ selected returns messages delivered in 1 to 2 minutes. **Start** value of **2** with the **Infinite** checkbox selected retrieves all messages that took 2 seconds/minutes/hours or longer to deliver. -Once the frame is configured, click **Add**. The configured message time frame will appear in the -list. Multiple time frames can be configured. Select a frame and click **Replace** to modify an +After you configure the frame, click **Add**. The configured message time frame will appear in the +list. You can configure multiple time frames. Select a frame and click **Replace** to modify an existing frame. Use **Remove** to delete an existing frame. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/category.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/category.md index 70bb491516..587932996c 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/category.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/category.md @@ -6,8 +6,8 @@ sidebar_position: 20 # ExchangePS: Category -The Category page contains a connection section where connection options are defined. It is also -where the query category is selected. The available query categories are sub-divided by auditing +The Category page contains a connection section where you define connection options. It's also +where you select the query category. The available query categories are sub-divided by auditing focus. ![ExchangePS Data Collector Wizard Category page](/images/accessanalyzer/12.0/admin/datacollector/exchangeps/category.webp) @@ -53,7 +53,7 @@ focus: - Mailbox Databases – Collects information on mailbox databases :::note - This option is not available for Office 365 target environments + This option isn't available for Office 365 target environments ::: @@ -110,7 +110,7 @@ Get-MailboxStatistics Get-MailboxDatabase ``` -When this category is selected, the following ExchangePS Data Collector Wizard pages are available +When you select this category, the following ExchangePS Data Collector Wizard pages are available for configuration: - [ExchangePS: Scope](/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scope.md) @@ -131,7 +131,7 @@ Get-MailboxStatistics Get-MailboxDatabase ``` -When this category is selected, the following ExchangePS Data Collector Wizard pages are available +When you select this category, the following ExchangePS Data Collector Wizard pages are available for configuration: - [ExchangePS: Scope](/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scope.md) @@ -149,7 +149,7 @@ PowerShell query this category runs is as follows: Get-MailboxDatabase ``` -When this category is selected, the following ExchangePS Data Collector Wizard pages are available +When you select this category, the following ExchangePS Data Collector Wizard pages are available for configuration: - [ExchangePS: Scope](/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scope.md) @@ -167,7 +167,7 @@ PowerShell query this category runs is as follows: Get-MailboxDatabase ``` -When this category is selected, the following ExchangePS Data Collector Wizard pages are available +When you select this category, the following ExchangePS Data Collector Wizard pages are available for configuration: - [ExchangePS: Scope](/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scope.md) @@ -185,7 +185,7 @@ PowerShell query this category runs is as follows: Get-MailboxDatabase ``` -When this category is selected, the following ExchangePS Data Collector Wizard pages are available +When you select this category, the following ExchangePS Data Collector Wizard pages are available for configuration: - [ExchangePS: Scope](/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scope.md) @@ -205,7 +205,7 @@ Get-Mailbox Get-MailboxDatabase ``` -When this category is selected, the following ExchangePS Data Collector Wizard pages are available +When you select this category, the following ExchangePS Data Collector Wizard pages are available for configuration: - [ExchangePS: Scope](/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scope.md) @@ -217,8 +217,8 @@ for configuration: **Mailbox Access Logons** -This category returns the Mailbox Access Auditing log details. Mailbox Access Auditing does need to -be enabled on the Mailboxes in order for this job to return any information. The PowerShell queries +This category returns the Mailbox Access Auditing log details. You must enable Mailbox Access +Auditing on the mailboxes for this job to return any information. The PowerShell queries this category runs are as follows: ``` @@ -226,7 +226,7 @@ Search-MailboxAuditLog Get-Mailbox ``` -When this category is selected, the following ExchangePS Data Collector Wizard pages are available +When you select this category, the following ExchangePS Data Collector Wizard pages are available for configuration: - [ExchangePS: Scope](/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scope.md) @@ -252,7 +252,7 @@ Get-Mailbox Get-ThrottlingPolicyAssociation ``` -When this category is selected, the following ExchangePS Data Collector Wizard pages are available +When you select this category, the following ExchangePS Data Collector Wizard pages are available for configuration: - [ExchangePS: Scope](/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scope.md) @@ -275,7 +275,7 @@ Get-ActiveSyncDeviceStatistics Get-Mailbox ``` -When this category is selected, the following ExchangePS Data Collector Wizard pages are available +When you select this category, the following ExchangePS Data Collector Wizard pages are available for configuration: - [ExchangePS: Scope](/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scope.md) @@ -290,8 +290,8 @@ Public Folder Information audit focus contains the following categories: **Public Folder Content** -This category returns general statistics and sizing for the public folder environment. When it is -selected, the following ExchangePS Data Collector Wizard pages are available for configuration: +This category returns general statistics and sizing for the public folder environment. When you +select it, the following ExchangePS Data Collector Wizard pages are available for configuration: - [ExchangePS: Scope](/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scope.md) - [ExchangePS: Results](/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/results.md) @@ -301,8 +301,8 @@ selected, the following ExchangePS Data Collector Wizard pages are available for **Public Folder Permissions** -This category returns permissions information for the public folder environment. When it is -selected, the following ExchangePS Data Collector Wizard pages are available for configuration: +This category returns permissions information for the public folder environment. When you +select it, the following ExchangePS Data Collector Wizard pages are available for configuration: - [ExchangePS: Scope](/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scope.md) - [ExchangePS: Results](/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/results.md) @@ -316,8 +316,8 @@ Office 365 audit focus contains the following category: **Mail Flow Metrics** -This category returns information about mail flow in the target Exchange Online environment. When it -is selected, the following ExchangePS Data Collector Wizard pages are available for configuration: +This category returns information about mail flow in the target Exchange Online environment. When +you select it, the following ExchangePS Data Collector Wizard pages are available for configuration: - [ExchangePS: Scope](/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scope.md) - [ExchangePS: Mail Flow](/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/mailflow.md) @@ -332,7 +332,7 @@ Domain Information audit focus contains the following category: **Domains** -This category returns information about domains in the Exchange environment. When it is selected, +This category returns information about domains in the Exchange environment. When you select it, the following ExchangePS Data Collector Wizard pages are available for configuration: - [ExchangePS: Scope](/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scope.md) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/configurejob.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/configurejob.md index 2dd3c15cd8..d1ab89356c 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/configurejob.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/configurejob.md @@ -6,12 +6,12 @@ sidebar_position: 10 # Exchange Custom Connection Profile & Host List -The ExchangePS Data Collector requires a custom Connection Profile and host list to be created and -assigned to the job conducting the data collection. The host inventory option during host list +The ExchangePS Data Collector requires a custom Connection Profile and host list, which you create +and assign to the job that collects the data. The host inventory option during host list creation makes it necessary to configure the Connection Profile first. :::note -It is not possible to target both Exchange Online and on-premises Exchange environments +You can't target both Exchange Online and on-premises Exchange environments from the same job. Therefore, the Connection Profile should only contain the credentials for one type of environment. ::: @@ -28,17 +28,17 @@ The provisioned credential used should be an Active Directory account. Create a and set the following information on the User Credentials window: - Select Account Type – Active Directory Account -- Domain – Drop-down menu with available trusted domains will appear. Either type the short domain +- Domain – dropdown menu with available trusted domains will appear. Either enter the short domain name in the textbox or select a domain from the menu. -- User name – Type the user name +- User name – Enter the user name - Password Storage – Choose the for credential password storage: - Application – Uses the configured Profile Security setting as selected at the **Settings** > **Application** node - CyberArk – Uses the CyberArk Enterprise Password Vault -- Password – Type the password -- Confirm – Re-type the password +- Password – Enter the password +- Confirm – Re-enter the password ### Exchange On-Premise Host List @@ -53,18 +53,18 @@ Exchange Online. ### Exchange Online Credential for a Connection Profile -The provisioned credential must be created with the Exchange Modern Authentication account type. +Create the provisioned credential with the Exchange Modern Authentication account type. Create a Connection Profile and set the following information on the User Credentials window: - Select Account Type – Exchange Modern Authentication - Password Storage – Application (Uses the configured Profile Security setting as selected at the **Settings** > **Application** node. See the [Application](/docs/accessanalyzer/12.0/admin/settings/application/overview.md) topic for additional information.) -- Organization – The primary domain name of the Microsoft Entra tenant being leveraged to make the +- Organization – The primary domain name of the Microsoft Entra tenant used to make the connection. See the [Identify the Tenant's Name](/docs/accessanalyzer/12.0/requirements/exchange/exchangeonline/access.md#identify-the-tenants-name) topic for additional information. -- Email Address – The email address for the mailbox to be leveraged in Exchange Online environment +- Email Address – The email address for the mailbox used in Exchange Online environment scans. The mailbox must belong to the primary domain used in the Organization field. - AppID – Application (client) ID of the Access Analyzer application registered with Microsoft Entra ID. See the diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/errorlogging.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/errorlogging.md index 327c568e85..b54d37907d 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/errorlogging.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/errorlogging.md @@ -6,7 +6,7 @@ sidebar_position: 120 # ExchangePS: Error Logging -The Error Logging page is used to configure how long to keep the PowerShell logs. It is a wizard +Use the Error Logging page to configure how long to keep the PowerShell logs. It is a wizard page for all of the categories. ![ExchangePS Data Collector Wizard Error Logging page](/images/accessanalyzer/12.0/admin/datacollector/exchangeps/errorlogging.webp) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/filtermessage.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/filtermessage.md index 54f4f28d16..969aa427d8 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/filtermessage.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/filtermessage.md @@ -6,7 +6,7 @@ sidebar_position: 70 # ExchangePS: Filter by Message -The Filter by Message page is used to define the filter conditions of the search. It is a wizard +Use the Filter by Message page to define the filter conditions of the search. It is a wizard page for the category of: - Mailbox Search @@ -36,16 +36,16 @@ Available conditions to select from include: See the [Date Range Selection Window](#date-range-selection-window) and [Words Window](#words-window) topics for additional information. -In the Select Search Mailbox Parameters section, select the desired filter parameters: +In the Select Search Mailbox Parameters section, select the filter parameters: -- Do not Include Archive +- Don't Include Archive - Include Unsearchable Items - Search Dumpster - Search Dumpster Only #### Date Range Selection Window -The Date Range Selection window is opened by the **Specify Date Range...** option for a date related +The **Specify Date Range...** option opens the Date Range Selection window for a date related filter on the Filter by Message page. ![Date Range Selection window](/images/accessanalyzer/12.0/admin/datacollector/exchangeps/daterangeselectionwindow.webp) @@ -56,19 +56,19 @@ Select the range category on the left and configure the range setting in the ena **Years**. - Last – Select the number and time units. The available time units are: **Days**, **Months**, or **Years**. -- Before – Drop-down menu opens a calendar selection view, choose the end date -- After – Drop-down menu opens a calendar selection view, choose the start date -- Between (Date) – Drop-down menus open calendar selection view, choose the start and end dates -- Between – Select the numbers for the lower and upper range boundary, and the desired time units. +- Before – dropdown menu opens a calendar selection view, choose the end date +- After – dropdown menu opens a calendar selection view, choose the start date +- Between (Date) – dropdown menus open calendar selection view, choose the start and end dates +- Between – Select the numbers for the lower and upper range boundary, and the time units. The available time units are: **Days**, **Months**, or **Years**. -When the date range is specified, click **OK**. The selected date range shows as a filter on the +After you specify the date range, click **OK**. The selected date range shows as a filter on the Filter by Message page. Click the filter to open the Date Range Selection window to modify the date range. #### Words Window -The Words window is opened by the **Specify words...** option for a word related filter on the +The **Specify words...** option opens the Words window for a word related filter on the Filter by Message page. ![Words window](/images/accessanalyzer/12.0/admin/datacollector/exchangeps/wordswindow.webp) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/mailboxlogons.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/mailboxlogons.md index 70c75af4f2..b524f9cb80 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/mailboxlogons.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/mailboxlogons.md @@ -6,13 +6,13 @@ sidebar_position: 80 # ExchangePS: Mailbox Logons -The Mailbox Logons page is used to define the type of mailbox logon events to return, as well as the -date range to be returned. It is a wizard page for the category of Mailbox Information > Mailbox +Use the Mailbox Logons page to define the type of mailbox logon events to return, as well as the +date range to return. It is a wizard page for the category of Mailbox Information > Mailbox Access Logons. ![ExchangePS Data Collector Wizard Mailbox Logons page](/images/accessanalyzer/12.0/admin/datacollector/exchangeps/mailboxlogons.webp) -Select the desired checkboxes to indicate which logons to audit: +Select the checkboxes to indicate which logons to audit: - Delegate - Admin @@ -27,4 +27,4 @@ Specify the date range for the logons: ::: -- Between (Date) – Use the drop-down menus to open calendars to select the start and end dates +- Between (Date) – Use the dropdown menus to open calendars to select the start and end dates diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/mailflow.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/mailflow.md index 3c6dfdd82f..13cf877cba 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/mailflow.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/mailflow.md @@ -21,5 +21,5 @@ Date range must be 7 days or less. - Last – Select the number of days -- Between (Date) – Use the drop-down menus to open the calendar selection view to choose the start +- Between (Date) – Use the dropdown menus to open the calendar selection view to choose the start and end dates diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/options.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/options.md index a2202ecf18..c4ee5f3b10 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/options.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/options.md @@ -6,7 +6,7 @@ sidebar_position: 110 # ExchangePS: Options -The Options page is used to configure additional options. It is a wizard page for all of the +Use the Options page to configure additional options. It is a wizard page for all of the categories. ![ExchangePS Data Collector Wizard Options page](/images/accessanalyzer/12.0/admin/datacollector/exchangeps/options.webp) @@ -32,6 +32,6 @@ The following options can be configured: - Concatenated - - Delimiter – Enter the desired delimiter to be used between values + - Delimiter – Enter the delimiter to use between values - First-value only diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/overview.md index 9aa2ff7b16..9fc6975d5d 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/overview.md @@ -6,8 +6,8 @@ sidebar_position: 200 # ExchangePS Data Collector -The ExchangePS Data Collector utilizes the Exchange CMDlets to return information about the Exchange -environment utilizing PowerShell. This data collector has been designed to work with Exchange 2010 +The ExchangePS Data Collector uses the Exchange CMDlets to return information about the Exchange +environment using PowerShell. This data collector has been designed to work with Exchange 2010 and newer. The ExchangePS Data Collector has been preconfigured within the Exchange Solution. Both this data collector and the solution are available with a special Access Analyzer license. See the [Exchange Solution](/docs/accessanalyzer/12.0/solutions/exchange/overview.md) topic for additional information. @@ -39,9 +39,9 @@ topic for additional information. ## Remote PowerShell -The ExchangePS Data Collector will utilize Remote PowerShell when connecting to Exchange 2010 or -newer. This behavior simulates what the Exchange Management Shell does when loading. The below -PowerShell syntax is an example of how the connection is loaded through PowerShell. +The ExchangePS Data Collector will use Remote PowerShell when connecting to Exchange 2010 or +newer. This behavior simulates what the Exchange Management Shell does when loading. The following +PowerShell syntax is an example of how PowerShell loads the connection. ``` $JobUserName = '{insert domain\username}' @@ -58,14 +58,14 @@ topic for instructions on enabling Remote PowerShell. ## The Exchange Applet -The Exchange Applet will run on the Exchange server by the ExchangePS Data Collector in the +The ExchangePS Data Collector runs the Exchange Applet on the Exchange server in the following circumstances: -- An actual Client Access Server (CAS) server is not specified either in the global configuration +- An actual Client Access Server (CAS) server isn't specified either in the global configuration (**Settings** > **Exchange** node) or on the Category page of the ExchangePS Data Collector Wizard - Remote PowerShell has not been enabled for targeting Exchange 2010 -The following Exchange Snap-in is used when the applet is utilized: +The following Exchange Snap-in is used when the applet is used: - Add-pssnapin Microsoft.Exchange.Management.Powershell.E2010 diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/results.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/results.md index c0560e386a..a2dab4e5b0 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/results.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/results.md @@ -6,10 +6,10 @@ sidebar_position: 100 # ExchangePS: Results -The Results page is where properties that will be gathered are selected. It is a wizard page for all +The Results page is where you select the properties to gather. It is a wizard page for all of the categories. ![ExchangePS Data Collector Wizard Results page](/images/accessanalyzer/12.0/admin/datacollector/exchangeps/results.webp) -Properties can be selected individually or the **Select All** and **Clear All** buttons can be used. -All selected properties will be gathered. Available properties vary based on the category selected. +You can select properties individually, or use the **Select All** and **Clear All** buttons. +The data collector gathers all selected properties. Available properties vary based on the category selected. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scope.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scope.md index 6c798250f5..c4a6479391 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scope.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scope.md @@ -19,7 +19,7 @@ Available scoping options vary based on the category selected. Scoping options i on the Summary page. See the [ExchangePS: Summary](/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/summary.md) topic for additional information. - When using the applet, the data collector gathers information about the Exchange Forest in - which the Access Analyzer Console currently resides + which the Access Analyzer Console resides - For Remote PowerShell, the data collector gathers information about the Exchange Organization to which the Remote PowerShell connection was made. This refers to the server entered in the Client Access Server (CAS) field of the global configuration from the **Settings** > @@ -36,7 +36,7 @@ Available scoping options vary based on the category selected. Scoping options i - When using the applet, the data collector deploys a process to the targeted host to run the PowerShell on that server - - For Remote PowerShell, the data collector does not deploy anapplet and utilizes the WinRM + - For Remote PowerShell, the data collector doesn't deploy anapplet and uses the WinRM protocol to gather information about the objects on that server. See the [Remote PowerShell](/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/overview.md#remote-powershell) and [The Exchange Applet](/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/overview.md#the-exchange-applet) topics for additional information. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scopedatabases.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scopedatabases.md index e69568302c..636bb3f50e 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scopedatabases.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scopedatabases.md @@ -6,19 +6,19 @@ sidebar_position: 40 # ExchangePS: Scope by DB -The Scope by Databases page is used to define specific databases to search. This page is enabled -when **Scope by Database Target Host: Local Host** option is selected on the Scope page. See the +Use the Scope by Databases page to define specific databases to search. This page is enabled +when you select the **Scope by Database Target Host: Local Host** option on the Scope page. See the [ExchangePS: Scope](/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scope.md) topic for additional information. When using the applet, the data collector returns databases for the Exchange Organization in which -the Access Analyzer Console currently resides, and only returns information about those databases. +the Access Analyzer Console resides, and only returns information about those databases. For Remote PowerShell, the data collector returns databases for the Exchange Forest and only returns information about those databases. ![ExchangePS Data Collector Wizard Scope by Databases page](/images/accessanalyzer/12.0/admin/datacollector/exchangeps/scopedatabases.webp) Click **Retrieve** to return all databases in the Exchange Organization and populate them in the -Available Databases list. Select the desired databases from Available Databases and click **Add**. -The selected databases are added in the Selected Databases list. To remove undesired databases from -Selected Databases, select them and click **Remove**. The Select All and Clear All buttons can be -used for quick selection. +Available Databases list. Select the databases from Available Databases and click **Add** to add +them to the Selected Databases list. To remove undesired databases from +Selected Databases, select them and click **Remove**. Use the Select All and Clear All buttons for +quick selection. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scopemailboxes.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scopemailboxes.md index 812956a4a6..c7cbdccfbe 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scopemailboxes.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scopemailboxes.md @@ -6,12 +6,12 @@ sidebar_position: 50 # ExchangePS: Scope by Mailboxes -The Scope by Mailboxes page is used to define specific mailboxes to search. This page is enabled -when the **Scope by Mailbox Target Host: Local Host** option is selected on the Scope page. See the +Use the Scope by Mailboxes page to define specific mailboxes to search. This page is enabled +when you select the **Scope by Mailbox Target Host: Local Host** option on the Scope page. See the [ExchangePS: Scope](/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scope.md) topic for additional information. When using the applet, the data collector will return mailboxes for the Exchange Forest in which the -Access Analyzer Console currently resides, and only return information about those mailboxes. For +Access Analyzer Console resides, and only return information about those mailboxes. For Remote PowerShell, the data collector will return mailboxes for the Exchange Forest as well as return information about those mailboxes. @@ -19,6 +19,6 @@ return information about those mailboxes. Click **Retrieve** to return all mailboxes in the Exchange Organization and populate them in the Available Mailboxes list. Select desired mailboxes from the Available Mailboxes list and click -**Add**. The selected mailboxes are added in the Selected Mailboxes list. To remove undesired -mailboxes from Selected Mailboxes, select them and click **Remove**. The Select All and Clear All -buttons can be used for quick selection. +**Add** to add them to the Selected Mailboxes list. To remove undesired +mailboxes from Selected Mailboxes, select them and click **Remove**. Use the Select All and Clear All +buttons for quick selection. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scopepublicfolders.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scopepublicfolders.md index 09c47e1874..8ac6e30ab0 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scopepublicfolders.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scopepublicfolders.md @@ -6,11 +6,11 @@ sidebar_position: 60 # ExchangePS: Scope by Public Folders -The Scope by Public Folders page is used to define specific public folders to search. This page is -enabled when the **Scope by Public Folder** option is selected on the Scope page. See the +Use the Scope by Public Folders page to define specific public folders to search. This page is +enabled when you select the **Scope by Public Folder** option on the Scope page. See the [ExchangePS: Scope](/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scope.md) topic for additional information. -Configure the **Scope** option using the drop-down. The available options are: +Configure the **Scope** option using the dropdown. The available options are: - Selected Public Folder - Selected Table @@ -24,9 +24,9 @@ organization, populating them in the Available list. ![ExchangePS Data Collector Wizard Scope by Public Folders page with Selected Public Folders option](/images/accessanalyzer/12.0/admin/datacollector/exchangeps/scopepublicfolders.webp) -The **Search** feature filters this list. Select the desired public folders and click **Add**. The -selected public folders are added to the Selected list. Use the **Remove** option to delete selected -public folders from the list. The Select All or Deselect All buttons can be used for quick +The **Search** feature filters this list. Select the public folders and click **Add** to add +them to the Selected list. Use the **Remove** option to delete selected +public folders from the list. Use the Select All or Deselect All buttons for quick selection. Additional scoping options include: - Return only these folders – Audits only the selected public folders diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/summary.md index 6ad06d6b75..d66fd5dea6 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/summary.md @@ -6,11 +6,10 @@ sidebar_position: 130 # ExchangePS: Summary -The Summary page is where configuration settings are summarized. It is a wizard page for all of the +The Summary page summarizes the configuration settings. It is a wizard page for all of the categories. ![ExchangePS Data Collector Wizard Summary page](/images/accessanalyzer/12.0/admin/datacollector/exchangeps/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the ExchangePS Data Collector Wizard to ensure that no accidental clicks -are saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** +to close the ExchangePS Data Collector Wizard and avoid saving accidental clicks. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/category.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/category.md index 9248547412..e9d57a71fe 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/category.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/category.md @@ -6,7 +6,7 @@ sidebar_position: 10 # ExchangePublicFolder: Category -The Category page is used to select the objects to search. +Use the Category page to select the objects to search. ![Exchange Public Folder Data Collector Wizard Category page](/images/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/category.webp) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/options.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/options.md index 71e99fe77a..644dca50cb 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/options.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/options.md @@ -13,11 +13,11 @@ all of the categories. Available options vary based on the category selected. The Options page contains the following options: -- Process folders that physically reside on the target server only – This option will limit - extraction to only the subset of public folders which reside on this server when selected. Clear - this option if targeting the Exchange 2010 Public Folder Server. The ability to scope to the - targeted server is not available for Exchange 2010. The entire public folder hierarchy is - returned. +- Process folders that physically reside on the target server only – When selected, this option + limits extraction to only the subset of public folders that reside on this server. Clear this + option if targeting the Exchange 2010 Public Folder Server. The ability to scope to the targeted + server isn't available for Exchange 2010, so the query returns the entire public folder + hierarchy. - Message size units: - KB @@ -27,7 +27,7 @@ The Options page contains the following options: When this option is selected, it will include subfolders in message counters, according to the Scope page settings. See the [ExchangeMetrics: Scope](/docs/accessanalyzer/12.0/admin/datacollector/exchangemetrics/scope.md) topic for additional information. -- Large attachment threshold (Kb) – Configure the desired size limit for attachments. The default +- Large attachment threshold (Kb) – Configure the size limit for attachments. The default value is 500. In the Attachment types section, configure attachment count types. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/overview.md index 749da4bfbc..057d3fed72 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/overview.md @@ -8,11 +8,11 @@ sidebar_position: 210 The ExchangePublicFolder Data Collector audits an Exchange Public Folder, including contents, permissions, ownership, and replicas. This is a MAPI-based data collector which requires the -**Settings > Exchange** node to be enabled and configured. See the +**Settings > Exchange** node, which you must enable and configure. See the [Exchange](/docs/accessanalyzer/12.0/admin/settings/exchange.md) topic for additional information. -The ExchangePublicFolder Data Collector has been preconfigured within the Exchange Solution. Both -this data collector and the solution are available with a special Access Analyzer license. See the +The Exchange Solution preconfigures the ExchangePublicFolder Data Collector. Both this data +collector and the solution are available with a special Access Analyzer license. See the [Exchange Solution](/docs/accessanalyzer/12.0/solutions/exchange/overview.md) topic for additional information. **Protocols** @@ -32,13 +32,13 @@ this data collector and the solution are available with a special Access Analyze **Sensitive Data Discovery Considerations** -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the minimum amount -of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For example, if the job -is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are required (8x2=16). +If you run Sensitive Data Discovery (SDD) scans, you must increase the minimum amount of RAM. Each +thread requires a minimum of 2 additional GB of RAM per host. For example, a job configured to scan +8 hosts at a time requires an extra 16 GB of RAM (8x2=16). ## ExchangePublicFolder Query Configuration -The ExchangePublicFolder Data Collector is configured through the Exchange Public Folder Data +You configure the ExchangePublicFolder Data Collector through the Exchange Public Folder Data Collector Wizard, which contains the following wizard pages: - Welcome @@ -57,7 +57,7 @@ permissions on the Welcome page. In the Connection Setting section, choose to either maintain the global inheritance, or configure query specific settings. -The **Use Global setting** option specifies what setting is being inherited. Clear this option to +The **Use Global setting** option specifies which setting the query inherits. Clear this option to break inheritance, and then select one of the following options: - System Attendant (2003 & 2007) @@ -67,6 +67,6 @@ break inheritance, and then select one of the following options: See the [Exchange](/docs/accessanalyzer/12.0/admin/settings/exchange.md) topic for additional information. -In the Sampling server section, enter the Exchange server in the textbox to be used to test the +In the Sampling server section, enter the Exchange server that Access Analyzer will use to test the connection settings. Click **Test sampling server** to ensure there is access to the server. The box at the bottom of the page displays information regarding the test connection in progress. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/probableowner.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/probableowner.md index ab15b6665b..638c6e553a 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/probableowner.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/probableowner.md @@ -6,13 +6,13 @@ sidebar_position: 50 # ExchangePublicFolder: Probable Owner -The Probable Owner Settings page provides configuration options to determine an owner. It is enabled -when the Probable Owner property is selected on the Properties page. See the +The Probable Owner Settings page provides configuration options to determine an owner. Selecting +the Probable Owner property on the Properties page enables it. See the [ExchangePublicFolder: Properties](/docs/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/properties.md) topic for additional information. ![Exchange Public Folder Data Collector Wizard Probable Owner page](/images/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/probableowner.webp) -In the Determine owner section, select the desired option to specify what setting to use to +In the Determine owner section, select an option to specify what setting to use to determine an owner: - Determine owner from folder hierarchy – Select to determine the probable owner with a weight of @@ -47,15 +47,15 @@ In the Exclusions section, select one or more of the following checkboxes to spe - Remove selected – Select a user or users to remove from the Exclude users list and click **Remove selected** to remove the users -In the Output Options section, select the desired output option: +In the Output Options section, select an output option: - Get one most probable owner – Return one probable owner - Get probable owners with relative deviation to the most probable owner – Return probable owners based on the deviation from percentage from the most probable owner - - Maximum deviation [number] percents – Use the arrow buttonss to enter the desired percent of + - Maximum deviation [number] percents – Use the arrow buttons to enter the percent of deviation from the most probable owner from which to return probable owners - Get multiple probable owners – Return multiple probable owners - - Count – Use the arrow buttons to enter the desired number of probable owners to return + - Count – Use the arrow buttons to enter the number of probable owners to return diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/properties.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/properties.md index 57d32739e6..0c4e888b91 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/properties.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/properties.md @@ -6,13 +6,13 @@ sidebar_position: 30 # ExchangePublicFolder: Properties -The Properties page is where properties that will be gathered are selected. It is a wizard page for -all of the categories. +Use the Properties page to select the properties to gather. It is a wizard page for all of the +categories. ![Exchange Public Folder Data Collector Wizard Properties page](/images/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/properties.webp) -Properties can be selected individually or you can use the **Select All**, **Clear All**, or **Reset -All** buttons. All selected properties will be gathered. The **Message Classes** button opens the +You can select properties individually or use the **Select All**, **Clear All**, or **Reset +All** buttons. Access Analyzer gathers all selected properties. The **Message Classes** button opens the Message classes filters window. ![Message classes filters window](/images/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/messageclassesfilterswindow.webp) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/scope.md b/docs/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/scope.md index bf4e076e4e..ca7e1a68f8 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/scope.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/scope.md @@ -6,8 +6,8 @@ sidebar_position: 20 # ExchangePublicFolder: Scope -The Scope page is used to define which folders will be included will be searched by this query. It -is a wizard page for all of the categories. +Use the Scope page to define which folders this query searches. It is a wizard page for all of the +categories. ![Exchange Public Folder Data Collector Wizard Scope page](/images/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/scope.webp) @@ -16,11 +16,11 @@ In the Choose Type of Public Folders to be queried section, select either: - Default Public Folders – User can access these folders directly with client applications such as Microsoft Outlook. In its default configuration, Exchange System Manager displays these folders when a public folder tree is expanded. -- System Public Folders – Users cannot access these folders directly. Client applications, such as +- System Public Folders – Users can't access these folders directly. Client applications, such as Microsoft Outlook, use these folders to store information such as free and busy data, offline address lists, and organizational forms. Other folders hold configuration information that is used by custom applications or by Exchange itself. The Public Folders tree contains extra system - folders, such as the EFORMS REGISTRY folder, that do not exist in general-purpose public folder + folders, such as the EFORMS REGISTRY folder, that don't exist in general-purpose public folder trees. In the Choose Scope of Public Folders to be queried section, select one of the following options: @@ -39,14 +39,14 @@ In the Choose Scope of Public Folders to be queried section, select one of the f ## Scope to the Selected Public Folders -When Scope to **Selected Public Folders** is selected on the Scope page, the options to specify the -desired folders are enabled. +Selecting **Selected Public Folders** on the Scope page enables the options to specify the desired +folders. ![Scope page with Selected Public Folders option selected](/images/accessanalyzer/12.0/admin/datacollector/exchangepublicfolder/scopeselectedpublicfolders.webp) Configure the scope of the selected public folders to be queried: -- Select public folders from – Enter the name of the server hosting the desired public folders and +- Select public folders from – Enter the name of the server hosting the public folders and click **Retrieve**. The box will populate with available public folders. - Add – Adds the selected folders - Add Recursive – Adds the selected folders and all child folders. Not adding recursive folders will @@ -55,7 +55,7 @@ Configure the scope of the selected public folders to be queried: selected host. If enabled, physically housed folders show in bold text in the list that is returned after clicking **Retrieve**. -The selected public folders are added in the table at the bottom. Click **Remove** to delete a +The table at the bottom lists the selected public folders. Click **Remove** to delete a selected word from the filter list. ## Scope to Selected Table @@ -70,7 +70,7 @@ Configure the selected tables to be queried: - Table Name – retrieves the list of selected public folders from a Access Analyzer database table. Click **Retrieve** to populate the Table name box with all available tables within the database. - - The Table name box can be filtered by entering a name in the textbox and clicking **Retrieve** + - Filter the Table name box by entering a name in the textbox and clicking **Retrieve** -- Field name – Select the desired table and the available fields will populate the Field names box. +- Field name – Select the table and the available fields will populate the Field names box. Select the field containing the public folder names. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/file/category.md b/docs/accessanalyzer/12.0/admin/datacollector/file/category.md index 0e456c3042..f8d9df685f 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/file/category.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/file/category.md @@ -14,7 +14,7 @@ The categories are: - Calculate Group Size (Files Only) – Scans of disk space for the amount used by files in each folder location. This option scopes the query to files so that any information involving the - folders that hold the files is not retrieved. + folders that hold the files isn't retrieved. - File or Folder Properties – Scans the target host for specific attributes and properties associated with certain files and folders in the environment. This option is selected by default. - File or Folder Permissions – Scans files or folders for permission settings and effective diff --git a/docs/accessanalyzer/12.0/admin/datacollector/file/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/file/overview.md index ea4d1d8dcc..a7f335ca17 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/file/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/file/overview.md @@ -6,8 +6,8 @@ sidebar_position: 220 # File Data Collector -The File Data Collector provides file and folder enumeration, properties, and permissions. It is -used to find files and folders on a target host. The File Data Collector finds one or more files on +The File Data Collector provides file and folder enumeration, properties, and permissions. Use it to +find files and folders on a target host. The File Data Collector finds one or more files on the target hosts. It can target any file extension. This data collector is a core component of Access Analyzer and is available with all Access Analyzer licenses. @@ -40,7 +40,7 @@ full list of supported platforms. ## File Query Configuration -The **File** Data Collector is configured through the File Search Wizard, which contains the +You configure the **File** Data Collector through the File Search Wizard, which contains the following wizard pages: - Welcome @@ -51,5 +51,5 @@ following wizard pages: ![File Search Wizard Welcome page](/images/accessanalyzer/12.0/admin/datacollector/file/welcome.webp) -The Welcome page can be hidden by selecting the **Do not display this page the next time** checkbox -when the wizard is open and configuration settings are saved. +Select the **Don't display this page the next time** checkbox to hide the Welcome page when the +wizard is open and configuration settings are saved. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/file/results.md b/docs/accessanalyzer/12.0/admin/datacollector/file/results.md index 47d4b6a3f5..169122395d 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/file/results.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/file/results.md @@ -6,18 +6,18 @@ sidebar_position: 30 # File: Results -The Results page provides a list of available properties to be searched for and returned by the job -execution. The properties selected display as table columns in the results of the query. It is a +The Results page provides a list of available properties that the job execution searches for and +returns. The properties selected display as table columns in the results of the query. It is a wizard page for all of the categories. ![File Search Wizard Results page](/images/accessanalyzer/12.0/admin/datacollector/file/results.webp) -Properties can be selected individually or in groups with the **Select All** or **Clear All** +You can select properties individually or in groups with the **Select All** or **Clear All** buttons. The properties available vary based on the category selected. :::note -When the **Calculate Group Size (Files Only)** category is selected, the properties and -options on the Results page are grayed out. +Selecting the **Calculate Group Size (Files Only)** category grays out the properties and +options on the Results page. ::: @@ -26,12 +26,12 @@ options on the Results page are grayed out. - This option is available for the **File or Folder Properties** category -- Only return permissions for the following user(s) – Defines users for the query. Enter the desired +- Only return permissions for the following users – Defines users for the query. Enter the desired users in the textbox. - This option is available for the **File or Folder Permissions** category -- Only return permissions for the following group(s) – Defines groups for the query. Enter the +- Only return permissions for the following groups – Defines groups for the query. Enter the desired users in the textbox. - This option is available for the **File or Folder Permissions** category diff --git a/docs/accessanalyzer/12.0/admin/datacollector/file/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/file/summary.md index 4413ff4300..94ecb43d5c 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/file/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/file/summary.md @@ -6,11 +6,11 @@ sidebar_position: 40 # File: Summary -The Summary page is where configuration settings are summarized. It is a wizard page for all of the +The Summary page summarizes the configuration settings. It is a wizard page for all of the categories. ![File Search Wizard Summary page](/images/accessanalyzer/12.0/admin/datacollector/file/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the File Data Collector Wizard ensuring that no accidental clicks are -saved. +Click **Finish** to save configuration changes. If you didn't make any changes, click **Cancel** to +close the File Data Collector Wizard. This ensures Access Analyzer doesn't save any accidental +clicks. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/file/targetfiles.md b/docs/accessanalyzer/12.0/admin/datacollector/file/targetfiles.md index 739d152b85..f05e1b1ab3 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/file/targetfiles.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/file/targetfiles.md @@ -11,7 +11,7 @@ results for the specific folder or file. It is a wizard page for all of the cate ![File Search Wizard Target Files page](/images/accessanalyzer/12.0/admin/datacollector/file/targetfiles.webp) -Within the Target files configuration page, select the desired method to refine the query. +Within the Target files configuration page, select the method you want to use to refine the query. :::note Some options are grayed out depending on the option selected. @@ -21,7 +21,7 @@ Some options are grayed out depending on the option selected. **Where is the file or folder?** This section supplies options for using a fixed path (wildcards and system variables) or registry -lookup values that are supported by the data collector. This header is available for all Category +lookup values that the data collector supports. This header is available for all Category selections. For either option, enter the path in the text box or click the browse button (**…**) to select from @@ -33,19 +33,18 @@ network neighborhoods which begin with `\\`. ::: -- Fixed path – Specify a specific path to the target files. Use the following format: +- Fixed path – Specify a path to the target files. Use the following format: `drive\filepath` (for example, `C:\WINNT\System32`). The browse button (**…**) opens the Remote Folder Explorer window. :::note - Further information for the Fixed path option is provided by clicking the tooltip - button (**?**). + Click the tooltip button (**?**) for more information about the Fixed path option. ::: - System environment variables – Supply a traditional system root or previously defined variable - that maps to a physical path within the file system. This is typically used when the system root - is installed on a secondary volume. The following are variables that can be entered at the + that maps to a physical path within the file system. You typically use this option when the + system root is installed on a secondary volume. You can enter the following variables at the beginning of the file path: - `%SYSTEMROOT%\Temp` – Expands to `C:\WINNT\Temp` on some target hosts @@ -55,24 +54,24 @@ network neighborhoods which begin with `\\`. - Registry Lookup – Find registry keys and values that exist on a target host in the environment. Click the browse button (**…**) to open the Access Analyzer Registry Browser window. - - Access Analyzer Registry – Connect to a host, then select a registry key and path to be used - for the lookup by the query + - Access Analyzer Registry – Connect to a host, then select a registry key and path for the + query to use in the lookup - Registry Value – This value is automatically populated from the registry key - - Levels – After a registry path has been selected, the Levels slider can be used to + - Levels – After you select a registry path, use the Levels slider to truncate the path for the key value in the Adjust Path dialog box - Current Value – Displays the type of data each registry value contains - Query 32-bit View – Select this checkbox to query a 32-bit view - Query 64-bit View – Select this checkbox to query a 64-bit view - When a **Fixed path** or **Registry Lookup** is mapped, select options to better refine + When you map a **Fixed path** or **Registry Lookup**, select options to better refine the search. Select one, none, or both. - Include network drives – Includes all mapped shared drives in the network in the query :::warning - Including subfolders may result in hundreds of thousands of files being returned - depending on the environment being targeted. + Including subfolders may return hundreds of thousands of files, depending on the + targeted environment. ::: @@ -81,12 +80,12 @@ network neighborhoods which begin with `\\`. **What is the file or folder name?** The options in this section limit the search to folders or files with a specified name against the -targeted host. When the **I am looking for folders** option is selected, more options become -available for further refinement. +targeted host. Selecting the **I am looking for folders** option makes more options available for +further refinement. :::note -The **I am looking for folders** option and it's associated options are unavailable -(grayed out) when the **Calculate Group Size (Files Only)** category is selected. +Selecting the **Calculate Group Size (Files Only)** category makes the **I am looking for +folders** option and its associated options unavailable (grayed out). ::: @@ -96,10 +95,10 @@ The **I am looking for folders** option and it's associated options are unavaila property information on these folders - Include root folder in results – Returns all information within the root folder - - Only include root folder – Returns information only for the root folder. This checkbox is - enabled when the **Include root folder in results** checkbox is selected. + - Only include root folder – Returns information only for the root folder. Selecting the + **Include root folder in results** checkbox enables this checkbox. -- With this name – Specific name of a file or folder. A wildcard is used to match any file or folder +- With this name – Specific name of a file or folder. Use a wildcard to match any file or folder to a specific naming convention. When searching for multiple objects, use a semicolon (`;`) to separate the objects in the list. @@ -121,8 +120,8 @@ a specific time frames. The following options are available: File Size Filter -The File Size Filter option is only available when the **Calculate Group Size (Files Only)** -category is selected. Select an option to activate the filter and narrow the query. +Selecting the **Calculate Group Size (Files Only)** category makes the File Size Filter option +available. Select an option to activate the filter and narrow the query. - None – No file size filter is applied. This option is selected by default. - Below – Filter to files smaller than the specified values diff --git a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/activitysettings.md b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/activitysettings.md index 67c999958f..e0b36c6652 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/activitysettings.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/activitysettings.md @@ -6,17 +6,17 @@ sidebar_position: 50 # FSAA: Activity Settings -The File System Activity Auditor Scan Filter Settings page is where activity scan filter settings -are configured. It is a wizard page for the category of File System Activity Scan. +Use the File System Activity Auditor Scan Filter Settings page to configure activity scan filter +settings. It is a wizard page for the category of File System Activity Scan. ![FSAA Data Collector Wizard Activity Settings page](/images/accessanalyzer/12.0/admin/datacollector/fsaa/activitysettings.webp) In the Scan Filters section, choose from the following options: - Set Scan Filter for Detailed Activity – Enables the **Days** number box. Select the number of past - days for activity details to be collected. + days to collect activity details. - Set Filter for Statistics of Activity – Enables the **Days** number box. Select the number of past - days for activity statistics to be collected. + days to collect activity statistics. In the Log Parsing Limits section, choose from the following option: @@ -28,16 +28,16 @@ In the Scan Limit section, configure the following: - Set Log Processing Limit – Stops the scan after the set number of MB or GB of log files are processed and the threshold number is reached -These filters affect what data is collected from the activity logs. However, enabling these filters +These filters affect what data the scan collects from the activity logs. However, enabling these filters also causes the corresponding bulk import query to purge the database of selected activity information older than the time filter specified here. -If either is left deselected, all available log files are collected and stored. This has a direct -impact on both scan time and database size. +If you leave either deselected, the scan collects and stores all available log files, which directly +affects both scan time and database size. :::tip -Remember, the file activity options require the Activity Monitor to be deployed, configured, and -services running. +Remember, the file activity options require you to deploy and configure the Activity Monitor and run +its services. ::: @@ -55,7 +55,7 @@ Query window. ![Host Mapping Query window](/images/accessanalyzer/12.0/admin/datacollector/fsaa/hostmappingquery.webp) -When the Enable host mapping checkbox is selected, the query textbox is enabled. The SQL query +Selecting the Enable host mapping checkbox enables the query textbox. The SQL query provided by a user should return a set of log locations, target hosts, and host names of the Monitored Hosts in the Activity Monitor. The target tables must reside within the Access Analyzer database and contain at least the following columns: @@ -72,20 +72,19 @@ database and contain at least the following columns: will be mapped to Enter the SQL query by clicking Sample Query then replacing the sample text in the textbox, as shown -above. The SQL query must target tables that have the required columns populated with the host +in the Host Mapping Query window. The SQL query must target tables that have the required columns populated with the host mapping. (Optional) Enter a host in the **Host parameter value (@host)** textbox to test the query to retrieve the data for that host. -Select **Test Query** to open a preview of the results in the Query Results window. Ensure that the -data being retrieved by the query is expected. When this option is selected, the data collector runs -against the target table. +Select **Test Query** to open a preview of the results in the Query Results window. Ensure the query +retrieves the expected data. Selecting this option runs the data collector against the target table. ### Host-Agent Mapping -Access Analyzer can be configured via the Host Mapping feature to support the use of Multiple -Activity Monitor Agents for a single targeted Host. See the examples below: +You can configure Access Analyzer via the Host Mapping feature to support the use of Multiple +Activity Monitor Agents for a single targeted Host. See the following examples: Single-Host Single-Agent Example: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/appletsettings/appletsettings.md b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/appletsettings/appletsettings.md index 51f6b88ffb..5e827d1435 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/appletsettings/appletsettings.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/appletsettings/appletsettings.md @@ -86,23 +86,23 @@ In the Applet Settings section, configure the following options: while the proxy server is busy, before it enters the job engine queue - Applet communication timeout: [number] minutes – This option determines the length of time (in minutes) the Access Analyzer Console attempts to reach the proxy before giving up. Depending on - the job configuration, the data collector behaves in one of three ways after the timeout value has - been exceeded: - - If a communication timeout is reached and the **Stop scan on applet communication timeout** + the job configuration, the data collector behaves in one of three ways after the timeout value + expires: + - If a communication timeout occurs and the **Stop scan on applet communication timeout** option is unchecked, the scan continues running. When the proxy is available again, the data collector gets the database files on the next scan of that host. It will either bring the database files back, if the scan has finished, or display the current state of the scan in a **Running Job** node if it is still running. - - If the communication timeout is reached and the **Stop scan on applet communication timeout** + - If the communication timeout occurs and the **Stop scan on applet communication timeout** option is checked, Access Analyzer automatically suspends or cancels the remote scan. If the **Restart incomplete scans after (0 always restarts) [number] days** option or the **Rescan unimported hosts after (0 always rescans) [number] days** option on the Applet Gathering Settings page are both set to zero or unchecked, the scan cancels. - If either of these options on the Applet Gathering Settings page are checked with values - higher than zero, the scan is suspended after the communication timeout value has been - exceeded + higher than zero, Access Analyzer suspends the scan after the communication timeout value + expires - Scan cancellation timeout: [number] minutes – When checked, this option will timeout the applet - if there is an attempt to pause the scan and the applet doesn't respond + if you attempt to pause the scan and the applet doesn't respond ![Certificate Exchange Options section of the Applet Settings page](/images/accessanalyzer/12.0/admin/datacollector/fsaa/appletsettingscertificateexchangeoptions.webp) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/appletsettings/spnmapping.md b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/appletsettings/spnmapping.md index 90e4e04e6a..d4c7889b93 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/appletsettings/spnmapping.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/appletsettings/spnmapping.md @@ -40,7 +40,7 @@ Use custom SPN mapping to specify which SPN Access Analyzer should present when ## Query requirements - The query must return columns named `Host` and `SPN` (you can use aliases, e.g. `SELECT ServerName AS Host, …`). -- The `@host` parameter - supplied automatically by Access Analyzer as the proxy server - is available if you want to filter by applet host, but it's optional — if your query doesn't reference it, Access Analyzer will use every row returned. +- The `@host` parameter — which Access Analyzer supplies automatically as the proxy server — is available if you want to filter by applet host, but it's optional — if your query doesn't reference it, Access Analyzer will use every row returned. - Host matching is case-insensitive. - Host name format must be consistent. The format you use in the table (FQDN, short name, or IP address) must exactly match the format you use for the applet host. For example, if the applet host uses a fully qualified domain name (FQDN), use the FQDN in the table as well. Don't mix formats — for example, don't store a short hostname while the applet host uses an FQDN. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/azuretenantmapping.md b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/azuretenantmapping.md index b27176e2a2..460990ffaf 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/azuretenantmapping.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/azuretenantmapping.md @@ -6,24 +6,24 @@ sidebar_position: 70 # FSAA: Azure Tenant Mapping -The Azure Tenant Mapping page is where the target domain or Tenant ID are configured for Azure -Information Protection (AIP) scanning. It is a wizard page for the categories of: +Use the Azure Tenant Mapping page to configure the target domain or Tenant ID for Azure Information +Protection (AIP) scanning. It is a wizard page for the categories of: - File System Access/Permission Auditing Scan - File System SDD Scan Remember, select the **Enable scanning of files protected by Azure Information Protection** checkbox on the [FSAA: Scan Settings](/docs/accessanalyzer/12.0/admin/datacollector/fsaa/scansettings.md) page to enable this page in the data collector wizard. -In order for FSAA to scan files protected by AIP, ensure that the prerequisites are met and an Azure -Connection Profile is successfully created. See the +For FSAA to scan files protected by AIP, meet the prerequisites and successfully create an Azure +Connection Profile. See the [Azure Information Protection Target Requirements](/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/azureinformationprotection.md) topic for additional information on configuring the File System solution to scan for AIP labels. ![FSAA Data Collector Wizard Azure Tenant Mapping page](/images/accessanalyzer/12.0/admin/datacollector/fsaa/azuretenantmapping.webp) Populate this page with the App ID (created during prerequisites) and a domain name or Tenant ID for -an Azure environment. These values must be associated with each application ID in the Azure +an Azure environment. You must associate these values with each application ID in the Azure Connection Profile. -Use the **Add** and **Remove** buttons and manually enter or **Paste** into the textbox the required -information. +Use the **Add** and **Remove** buttons, and manually enter or paste the required information into +the textbox. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/bulkimport.md b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/bulkimport.md index c04e40aa56..93bde09d12 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/bulkimport.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/bulkimport.md @@ -6,8 +6,8 @@ sidebar_position: 130 # FSAA: Bulk Import Settings -The Bulk Import Settings page is where the bulk import process settings are configured. It is a -wizard page for the categories of: +Use the Bulk Import Settings page to configure the bulk import process settings. It is a wizard page +for the categories of: - Bulk Import File System Access/Permission Auditing - Bulk Import File System Activity @@ -16,5 +16,5 @@ wizard page for the categories of: ![FSAA Data Collector Wizard Bulk Import Settings page](/images/accessanalyzer/12.0/admin/datacollector/fsaa/bulkimport.webp) Select the **Import incomplete scan data** checkbox to enable imports of partial scan data. If the -scan is stopped before successful completion, this option must be checked in order to bulk import -the data from a partially scanned host. +scan stops before successful completion, select this option to bulk import the data from a +partially scanned host. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/certificatemanagement/certificateauthority.md b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/certificatemanagement/certificateauthority.md index 120490c4eb..08b38aaa3d 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/certificatemanagement/certificateauthority.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/certificatemanagement/certificateauthority.md @@ -19,11 +19,11 @@ custom CA to generate and sign client certificates dynamically. ## How Provide Certificate Authority Works -When **Provide Certificate Authority** is selected: +When you select **Provide Certificate Authority**: 1. FSAA loads the provided CA certificate from a `.pfx` file. 2. FSAA generates client certificates and signs them using the supplied CA. -3. Generated certificates are stored securely by FSAA. +3. FSAA stores generated certificates securely. 4. The FSAA applet presents its client certificate during HTTPS communication. 5. The data collector validates the certificate and establishes a secure connection. @@ -36,10 +36,10 @@ The CA certificate must meet the following requirements: - **Basic Constraints:** `CA=TRUE` - **Key Usage:** certificate signing (`CertSign`) - Certificate is within its valid date range -- PFX file is not password-protected +- PFX file isn't password-protected :::note -FSAA cannot load password-protected PFX files. +FSAA can't load password-protected PFX files. ::: ## Creating the CA Certificate diff --git a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/certificatemanagement/certificatemanagement.md b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/certificatemanagement/certificatemanagement.md index 2cf802d7cf..1f4c0b1e08 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/certificatemanagement/certificatemanagement.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/certificatemanagement/certificatemanagement.md @@ -7,7 +7,7 @@ sidebar_position: 160 # FSAA Applet Certificate Management Overview Communication between the FSAA Data Collector and the FSAA Applet is secure by default using HTTPS. -For authentication, at least three certificates are required and need to be stored in the correct +For authentication, FSAA requires at least three certificates. You store them in the correct certificate store managed by the FSAA Data Collector. These three certificates are: - The certificate authority (stored in the FSAA Certificate Authority Store) @@ -16,32 +16,30 @@ certificate store managed by the FSAA Data Collector. These three certificates a :::note The FSAA Data Collector and Applet server support certificates in both the user’s -certificate store and the computer’s certificate store. It is recommended to store certificates in -the user's certificate store that is running the FSAA Data Collector or Applet server because -administrative access is required for the computer's certificate store. When certificates are -generated using the Automatic option below, they are stored in the user’s certificate store. +certificate store and the computer’s certificate store. Netwrix recommends storing certificates in +the user’s certificate store that is running the FSAA Data Collector or Applet server, because the +computer’s certificate store requires administrative access. When you generate certificates using +the **Automatic** option, FSAA stores them in the user’s certificate store. ::: ![Certificate Exchange Options section of the Applet Settings page](/images/accessanalyzer/12.0/admin/datacollector/fsaa/appletsettingscertificateexchangeoptions.webp) -There are three Certificate Exchange Options provided by the FSAA Data collector: +The FSAA Data Collector provides three Certificate Exchange Options: -- Automatic (Default Option) – The creation of a self-signed certificate and certificate exchange - between the FSAA Data Collector and Applet are handled entirely by the FSAA Data Collector and - Applet server +- Automatic (Default Option) – The FSAA Data Collector and Applet server entirely handle the + creation of a self-signed certificate and certificate exchange between them - The self-signed CA generated will be valid for two years and the FSAA Data Collector and Applet server will also manage expired certificates and remove certificates that are no longer valid from the FSAA stores - Manual – The FSAA Data Collector will expect all certificates to be valid and in their respective - certificate stores prior to running a scan + certificate stores before running a scan - - To create and store certificates, the `FSAACertificateManager.exe` tool can be used. This - application was created to simplify the process of creating certificates and will store the - certificates in the location that the FSAA Data Collector and Applet server expect them to be - stored. See the [FSAA Manual Certificate Configuration](/docs/accessanalyzer/12.0/admin/datacollector/fsaa/certificatemanagement/manualcertificate.md) topic for + - To create and store certificates, use the `FSAACertificateManager.exe` tool. This + application simplifies the process of creating certificates and stores them in the location + that the FSAA Data Collector and Applet server expect. See the [FSAA Manual Certificate Configuration](/docs/accessanalyzer/12.0/admin/datacollector/fsaa/certificatemanagement/manualcertificate.md) topic for additional information. The `FSAACertificateManager.exe` tool is located in the @@ -50,30 +48,30 @@ There are three Certificate Exchange Options provided by the FSAA Data collector with the `-help` command. :::note - If the FSAA Data Collector and Applet are on separate domains without a trust, this - option must be used. + If the FSAA Data Collector and Applet are on separate domains without a trust, you must use + this option. ::: - Provide Certificate Authority – The certificate exchange process is the same as with the Automatic option. However, instead of creating a self-signed certificate, the FSAA Data Collector uses a - certificate you provide through the FSAA Data Collector Wizard. The provided certificate is stored - in the FSAA Certificate Authority Store. + certificate you provide through the FSAA Data Collector Wizard. FSAA stores the provided + certificate in the FSAA Certificate Authority Store. :::note - If the provided certificate is not self-signed as the Certificate Authority, the root - certificate and the Certificate Authority’s certificate chain must also be stored in the FSAA + If the provided certificate isn’t self-signed as the Certificate Authority, you must also + store the root certificate and the Certificate Authority’s certificate chain in the FSAA Certificate Authority Store on both the client and server hosts. ::: :::warning - The FSAA Applet does not support password-protected certificates. Certificates - generated when the Automatic option is selected have no password. When manually creating a - certificate for use with the FSAA Applet the password parameter should be omitted. + The FSAA Applet doesn't support password-protected certificates. Certificates + generated when you select the Automatic option have no password. When you manually create a + certificate for use with the FSAA Applet, omit the password parameter. ::: -Additionally, the port used for secure certificate exchange can be configured by selecting the +Additionally, you can configure the port used for secure certificate exchange by selecting the Specify certificate exchange port checkbox on the Applet Settings page of the FSAA Data Collector Wizard. The default port is 8767. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/certificatemanagement/manualcertificate.md b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/certificatemanagement/manualcertificate.md index 6e8fdb1894..3fc7f891c2 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/certificatemanagement/manualcertificate.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/certificatemanagement/manualcertificate.md @@ -14,15 +14,15 @@ case-sensitive. ## Create and store the required certificates :::note -In these steps, some commands need to be run on the Access Analyzer console and some on +In these steps, you need to run some commands on the Access Analyzer console and some on the Proxy host. In the provided example commands: ::: -- All files that are generated by the Certificate Manager or copied to the Access Analyzer console - are placed in the `%SAInstallDir%\PrivateAssemblies\FILESYSTEMACCESS\Applet\My Certificates` +- The Certificate Manager places all files it generates, or that you copy to the Access Analyzer + console, in the `%SAInstallDir%\PrivateAssemblies\FILESYSTEMACCESS\Applet\My Certificates` directory. The tool creates this folder if it doesn't already exist. -- When operating on the proxy host, files are placed into the root of the **FSAA** folder +- When you operate on the proxy host, the tool places files into the root of the **FSAA** folder :::tip Remember, all commands in the `FSAACertificateManager.exe` tool are case-sensitive. @@ -121,8 +121,8 @@ You will delete these copied files from the destination directory later in Step **Step 7 –** Generate the server certificate signing request and key on the Proxy host. On the proxy -host, run the following command out of the FSAA folder where the `FSAACertificateManager.exe` was -copied to: +host, run the following command out of the FSAA folder where you copied +`FSAACertificateManager.exe`: ``` .\FSAACertificateManager.exe -createCertificateSigningRequest -subjectDN CN=proxy01.my.domain.com -subjectAlternativeNames Proxy01 -outputPath . -name Proxy01 @@ -184,12 +184,12 @@ Successfully added FSAA_Server_Auth to Server **Step 11 –** Repeat Steps 6-10 for each proxy host. -**Step 12 –** Delete all the PFX, CER, and Key files that were generated or copied in the earlier -steps from the output locations. +**Step 12 –** Delete all the PFX, CER, and Key files you generated or copied in the earlier +steps, from the output locations. -You have now stored all the required FSAA certificates in the FSAA managed certificate stores. The -FSAA queries need to be configured to use the **Manual** certificate exchange option. This option -can be found under Applet Settings in the FSAA Data Collector Wizard. See the +You have now stored all the required FSAA certificates in the FSAA managed certificate stores. You +need to configure the FSAA queries to use the **Manual** certificate exchange option. You can find +this option under Applet Settings in the FSAA Data Collector Wizard. See the [FSAA: Applet Settings](/docs/accessanalyzer/12.0/admin/datacollector/fsaa/appletsettings/appletsettings.md) topic for additional information. For additional information on how to use the `FSAACertificateManager.exe` tool, run the diff --git a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/defaultscopingoptions/defaultscopingoptions.md b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/defaultscopingoptions/defaultscopingoptions.md index 82eaf8d30a..9ba71f3b2c 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/defaultscopingoptions/defaultscopingoptions.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/defaultscopingoptions/defaultscopingoptions.md @@ -6,9 +6,9 @@ sidebar_position: 80 # FSAA: Default Scoping Options -The Default Scoping Options page is where scan settings, file details, and file properties settings -can be configured for every resource in the targeted environment by the data collector. The settings -assigned on this page are used by all resources involved in the scan. It is a wizard page for the +Use the Default Scoping Options page to configure scan settings, file details, and file properties +settings that the data collector applies to every resource in the targeted environment. All +resources involved in the scan use the settings assigned on this page. It is a wizard page for the categories of: - File System Access/Permission Auditing Scan diff --git a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/defaultscopingoptions/filedetails.md b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/defaultscopingoptions/filedetails.md index 59907c12d1..dcef17ff0b 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/defaultscopingoptions/filedetails.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/defaultscopingoptions/filedetails.md @@ -6,11 +6,11 @@ sidebar_position: 20 # File Details Tab -The File Details tab allows configuration of settings for file detail collection. +Use the File Details tab to configure settings for file detail collection. ![FSAA Data Collector Wizard Default Scoping Options page File Details tab](/images/accessanalyzer/12.0/admin/datacollector/fsaa/defaultscopingoptions/filedetails.webp) -Select the desired settings for additional scoping: +Select the settings you want for additional scoping: - Scan file-level details – Turns on file-level scanning and collects a full list of files, file size, last modified, and last accessed @@ -19,10 +19,10 @@ Select the desired settings for additional scoping: **File tag metadata collection** -- Collect tags/keywords from file metadata properties – Enables the collection of file Microsoft - Office metadata tags and stores the tags into the tables when the **Scan file-level details** - checkbox and the **Collect File Metadata Tags** checkbox are selected on the page. It only scans - the files that satisfy the scan filter settings. +- Collect tags/keywords from file metadata properties – Collects file Microsoft Office metadata + tags and stores them in the tables when you select the **Scan file-level details** checkbox + and the **Collect File Metadata Tags** checkbox on the page. It only scans the files that + satisfy the scan filter settings. - Include offline files – Include offline files in the scan - Only collect tags/keywords with the following comma-separated values (case-insensitive) – Collects tags from the files and stores the tags into the tables. Filters results to only collect from @@ -39,7 +39,7 @@ The Scan filter settings options are enabled if the **Scan file-level details** selected. - Only files larger than [number] [size unit] – Filters the results to only collect file data on - files larger than the set value. If this option is not set, all file sizes are collected. + files larger than the set value. If this option isn't set, all file sizes are collected. - Only files last modified more than [number] [time period] ago – Filters results to only collect file data on files modified older than the set value - Only files last modified less than [number] [time period] ago – Filters results to only collect @@ -49,7 +49,7 @@ selected. not set, all file types are collected. :::warning -Be careful when configuring these settings. If no filters are applied when file detail -scanning has been enabled, it can result in returning large amounts of data to the database. +Be careful when configuring these settings. If you don't apply filters while file detail +scanning is enabled, the scan can return large amounts of data to the database. ::: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/defaultscopingoptions/fileproperties.md b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/defaultscopingoptions/fileproperties.md index ccbab1d904..542d2ed202 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/defaultscopingoptions/fileproperties.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/defaultscopingoptions/fileproperties.md @@ -6,8 +6,8 @@ sidebar_position: 30 # File Properties (Folder Summary) Tab -The File Properties (Folder Summary) tab is where file property collection settings for the scan is -configured. +Use the File Properties (Folder Summary) tab to configure file property collection settings for +the scan. ![FSAA Data Collector Wizard Default Scoping Options page File Properties (Folder Summary) tab](/images/accessanalyzer/12.0/admin/datacollector/fsaa/defaultscopingoptions/fileproperties.webp) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/defaultscopingoptions/scansettings.md b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/defaultscopingoptions/scansettings.md index 54cf9a01a5..3c8c50faa2 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/defaultscopingoptions/scansettings.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/defaultscopingoptions/scansettings.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Scan Settings Tab -The Scan Settings tab allows configuration of data collection settings. +Use the Scan Settings tab to configure data collection settings. ![FSAA Data Collector Wizard Default Scoping Options page Scan Settings tab](/images/accessanalyzer/12.0/admin/datacollector/fsaa/scansettings.webp) @@ -24,10 +24,10 @@ The Scan Settings tab has the following configurable options: - Last Access Time (LAT) preservation – Preserves Data Access timestamp attribute on files that are scanned for Metadata tags and sensitive data - - Warn if unable to preserve Last Access Time – Scan throws a warning if the LAT cannot be + - Warn if unable to preserve Last Access Time – Scan throws a warning if the LAT can't be preserved. The file is still scanned unless the Skip file if unable to preserve Last Access Time checkbox is also selected. - - Skip file if unable to preserve Last Access Time – Scan skips the file if the LAT cannot be + - Skip file if unable to preserve Last Access Time – Scan skips the file if the LAT can't be preserved Selecting the **Last Access Time (LAT) preservation** checkbox enables the **Action on failure to @@ -37,13 +37,13 @@ enable LAT preservation** and **Action on changed LAT after scan** dropdown me - Action on failure to enable LAT Preservation – Before scanning each file, FSAA attempts to enable an operating system feature to preserve the LAT when accessing the file. This operation may fail - for a variety of reasons, which include but are not limited to: the operating system or file - system where the file is located does not support LAT preservation, or insufficient permissions + for a variety of reasons, which include but aren't limited to: the operating system or file + system where the file is located doesn't support LAT preservation, or insufficient permissions from the service account trying to access the file. The following configuration addresses a failure to enable the LAT preservation mode: - Continue to scan file silently – FSAA scans the file with the possibility that LAT - preservation is not possible. No warning will be shown. + preservation isn't possible. No warning will be shown. - Continue to scan file with warning – FSAA scans the file with the possibility that LAT will not be preserved. A warning will be shown for this file. - Skip file silently – FSAA will not scan the file. No warning will be shown. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/overview.md index b31a5abdf0..fee03cadcf 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/overview.md @@ -32,13 +32,13 @@ available with a special Access Analyzer license. See the **Sensitive Data Discovery Considerations** If running Sensitive Data Discovery (SDD) scans, you must increase the minimum amount -of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. By default, SDD scans are -configured to run two concurrent threads. For example, if the job is configured to scan 8 hosts at a -time with two concurrent SDD threads, then an extra 32 GB of RAM are required (8x2x2=32). +of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. By default, SDD scans run two +concurrent threads. For example, if a job scans 8 hosts at a time with two concurrent SDD threads, it +requires an extra 32 GB of RAM (8x2x2=32). ## FSAA Query Configuration -The FSAA Data Collector is configured through the File System Access Auditor Data Collector Wizard. +Configure the FSAA Data Collector through the File System Access Auditor Data Collector Wizard. The wizard contains the following pages, which change based up on the query category selected: - [FSAA: Query Selection](/docs/accessanalyzer/12.0/admin/datacollector/fsaa/queryselection.md) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/queryselection.md b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/queryselection.md index a5c9f1660d..7cfaf56cc3 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/queryselection.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/queryselection.md @@ -34,7 +34,7 @@ auditing focus: - Scan and import – Collects Distributed File System information :::note - Starting with v8.1, DFS Audits are completed with a streaming method and do not + Starting with v8.1, DFS Audits are completed with a streaming method and don't require a bulk import query following the scan query. ::: @@ -69,46 +69,46 @@ installed on the Access Analyzer Console before the FSAA Data Collector can coll ::: -Once a query scan using the FSAA DC has been executed, the **Maintenance** button is enabled to -allow troubleshooting of scan errors that may have occurred. +After you run a query scan using the FSAA DC, the **Maintenance** button becomes available so you +can troubleshoot scan errors that occurred. :::warning -Do not use the Maintenance button unless instructed by -[Netwrix Support](https://www.netwrix.com/support.html). It is possible to cause corruption of the -database and loss of data to occur. +Don't use the Maintenance button unless instructed by +[Netwrix Support](https://www.netwrix.com/support.html). Using it can corrupt the database and +cause data loss. ::: ## Maintenance Wizard -The Maintenance Wizard is opened by clicking the **Maintenance** button on the Query Selection page -of the FSAA Data Collector Wizard. You can use the wizard to reset hosts or repair file system data +Click the **Maintenance** button on the Query Selection page of the FSAA Data Collector Wizard to +open the Maintenance Wizard. You can use the wizard to reset hosts or repair file system data errors. ![Maintenance Wizard Maintenance Selection page](/images/accessanalyzer/12.0/admin/datacollector/fsaa/maintenancewizardselection.webp) -The Maintenance Selection page allows you to select the type of maintenance to be performed: +Use the Maintenance Selection page to select the type of maintenance to perform: - Reset Hosts – Resets the Access GUID column value in the SA_FSAA_Hosts table for the Hosts selected. Allows data to be bulk imported when there is a GUID mismatch. - Repair – Resets the MinResourceID and MinTrusteeID column values to 0. Removes duplicate and data consistency issues, including resources with nonexistent parents. Deletes StrucMap database. -Select the required option and click **Next**. The subsequent wizard page is determined by the -selection made. +Select the required option and click **Next**. Your selection determines which wizard page displays +next. -- If Reset Hosts was selected, the Reset Hosts page displays: +- If you select Reset Hosts, the Reset Hosts page displays: ![Maintenance Wizard Reset Hosts page](/images/accessanalyzer/12.0/admin/datacollector/fsaa/maintenancewizardresethosts.webp) - Select the desired hosts to reset the SQL data for, and click **Reset Hosts** to perform the + Select the hosts you want to reset the SQL data for, and click **Reset Hosts** to perform the maintenance. -- If Repair was selected, the Repair Tool page displays: +- If you select Repair, the Repair Tool page displays: ![Maintenance Wizard Repair Tool page](/images/accessanalyzer/12.0/admin/datacollector/fsaa/maintenancewizardrepair.webp) - Select the desired hosts to repair the SQL data for, and click **Run** to perform the + Select the hosts you want to repair the SQL data for, and click **Run** to perform the maintenance. Click **Finish** to close the wizard when you have completed the required maintenance. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/scanserverselection.md b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/scanserverselection.md index bbb31ff98c..c607a2be6e 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/scanserverselection.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/scanserverselection.md @@ -6,7 +6,7 @@ sidebar_position: 40 # FSAA: Scan Server Selection -The Scan Server Selection page is where the server that executes the scan is configured. It is a +Use the Scan Server Selection page to configure the server that executes the scan. It is a wizard page for the categories of: - File System Access/Permission Auditing Scan @@ -15,7 +15,7 @@ wizard page for the categories of: ![FSAA Data Collector Wizard Scan Server Selection page](/images/accessanalyzer/12.0/admin/datacollector/fsaa/scanserverselection.webp) -Using the radio buttons, select where the execution of the applet will take place: +Using the radio buttons, select where the applet runs: - Automatic (Local for NAS device hosts, Remote for Windows hosts) – Applet is deployed to all targeted Windows servers. Other targeted devices, for example NAS, are scanned locally by the @@ -44,16 +44,16 @@ Using the radio buttons, select where the execution of the applet will take plac choose from. If more than one list is selected, scanning is distributed across each host. :::info -It is best practice in global implementations to utilize a specific remote server or proxy scanner +It is best practice in global implementations to use a specific remote server or proxy scanner that is located in the same data center as the target hosts. This is particularly beneficial if the Access Analyzer Console server is in a different data center. See the [Proxy Scanning Architecture](/docs/accessanalyzer/12.0/install/filesystemproxy/overview.md#proxy-scanning-architecture) topic for additional information. ::: -In the bottom section, the checkbox options affect the execution of the applet: +In the bottom section, the checkbox options affect how the applet runs: -- Fallback to local mode if applet can't start – If the applet cannot be deployed on the target +- Fallback to local mode if applet can't start – If the applet can't be deployed on the target host, it is deployed locally on the same server as the Access Analyzer Console and the scan collects data across the network - Run remote applet with normal priority (non-proxy applet server uses background priority by diff --git a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/scansettings.md b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/scansettings.md index 8a9d25a5a3..3bc137cada 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/scansettings.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/scansettings.md @@ -6,7 +6,7 @@ sidebar_position: 60 # FSAA: Scan Settings -The Scan Settings page is where additional scan protocols and settings are configured. It is a +Use the Scan Settings page to configure additional scan protocols and settings. It is a wizard page for the categories of: - System Access/Permission Auditing Scan @@ -14,16 +14,16 @@ wizard page for the categories of: ![FSAA Data Collector Wizard Scan Settings page](/images/accessanalyzer/12.0/admin/datacollector/fsaa/scansettings_1.webp) -In the Scan Protocols section, select the desired checkboxes for including certain types of shared +In the Scan Protocols section, select the checkboxes you want for including certain types of shared folders: - Scan Windows (SMB/CIFS) shares – Includes types of Windows and NAS shares - Scan NFS exports (shares) – Includes this type of UNIX and NAS shares -In the middle section, select the desired checkboxes for additional settings: +In the middle section, select the checkboxes you want for additional settings: - Enable file system scan streaming – Sends the streamed data directly to the Access Analyzer - database. A bulk import query is not required when this option is selected + database. A bulk import query isn't required when this option is selected - Enable scanning of files protected by Azure Information Protection – Adds additional options to this wizard to scan for protection labels and encrypted files for sensitive data @@ -37,7 +37,7 @@ In the middle section, select the desired checkboxes for additional settings: permissions. Click **Configure Query** to open the Manual Shares Query window. See the [Enable the Use SQL Query to Manually Specify Shares](#enable-the-use-sql-query-to-manually-specify-shares) topic for additional information. -- NetApp communication security – This option provides the ability to choose levels of encryption +- NetApp communication security – This option lets you choose levels of encryption and authentication applied during Access Auditing scans of NetApp devices ![NetApp communication security options](/images/accessanalyzer/12.0/admin/datacollector/fsaa/scansettingsnetapp.webp) @@ -84,7 +84,7 @@ columns for all shares in the target environment: - Host – Name of host where the share resides matching the Host Master table Name field value :::info - Use this column but it is not required. + Use this column but it isn't required. ::: @@ -95,8 +95,8 @@ columns for all shares in the target environment: - 0 = CIFS share - 1 = NFS share -For example, if the share has a path of `\\cec-fs01\Documentation`, then the columns are populated -in this way: +For example, if the share has a path of `\\cec-fs01\Documentation`, the query populates the columns +as follows: - Host – `cec-fs01` - Share – `Documentation` @@ -104,8 +104,8 @@ in this way: - ShareType – `0` :::warning -If the FSAA Data Collector has identified a share in a previous scan, but that share is -not in a table targeted by this query, then it is marked as a deleted share. +If the FSAA Data Collector identified a share in a previous scan, but that share isn't +in a table targeted by this query, the data collector marks it as a deleted share. ::: @@ -118,11 +118,11 @@ the data for that host. Select **Test Query** to open a preview of the results in the Query Results window. Ensure that the data being retrieved by the query is expected. -When this option is selected, the data collector runs against the target table to enumerate shares +When you select this option, the data collector runs against the target table to enumerate shares in the environment. :::tip -Remember, if a share is not in the target table, the data collector assumes that the share does +Remember, if a share isn't in the target table, the data collector assumes that the share does not exist and marks it as deleted. ::: @@ -131,7 +131,7 @@ not exist and marks it as deleted. The HTTPS encryption options for the NetApp communication security setting of the global Remote Data Collection Configuration page in the File System Access Auditor Data Collector Wizard requires a -certificate. If the organization uses a self-signed certificate, it is necessary to add this +certificate. If the organization uses a self-signed certificate, add this certificate to enable HTTPS encryption of Access Analyzer communications. The certificate (`cacert.pem`) which is shipped with Access Analyzer is in the DC folder of the @@ -139,16 +139,16 @@ installation directory. The default location is: **…\STEALTHbits\StealthAUDIT\DC** -If employing remote applet mode or proxy servers, then the certificate (`cacert.pem`) must exist in +If you use remote applet mode or proxy servers, the certificate (`cacert.pem`) must exist in the FSAA folder where the `FSAAAppletServer.exe` process is running (applet/proxy host). Therefore, -it is necessary to also copy it to the FSAA folder on the target hosts andr proxy servers. This is -done at runtime when using remote applet mode, but any updates or custom certificates must be copied -manually. The default location is: +also copy it to the FSAA folder on the target hosts and proxy servers. The system copies it +automatically at runtime when you use remote applet mode, but you must copy any updates or custom +certificates manually. The default location is: **…\STEALTHbits\StealthAUDIT\FSAA** :::info -Do not overwrite this certificate. It is fully trusted by Netwrix. Instead, add +Don't overwrite this certificate. Netwrix fully trusts it. Instead, add an underscore (\_) character to the start of the file name. Then copy the organization’s self-signed certificate to this location with the name `cacert.pem`. ::: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/scopingoptions.md b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/scopingoptions.md index e617329afd..f63d319037 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/scopingoptions.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/scopingoptions.md @@ -6,8 +6,8 @@ sidebar_position: 90 # FSAA: Scoping Options -The Scoping Options page is where scan settings, file details, and file properties settings can be -configured for a specified resource in the targeted environment. It is a wizard page for the +Use the Scoping Options page to configure scan settings, file details, and file properties settings +for a specified resource in the targeted environment. It is a wizard page for the following categories: - File System Access/Permission Auditing Scan @@ -27,15 +27,15 @@ The Scoping Options buttons have the following: conflicting settings occur with one resource - Import – Import scoping options from a `.fsaascope` file. - - If a conflict arises between an existing configured scoping option and an option that is being - imported, the user will be prompted to resolve the conflict by either keeping the existing - configuration or importing the new one, which will overwrite the scoping option. + - If a conflict arises between an existing configured scoping option and the option being + imported, the system prompts you to resolve the conflict by keeping the existing + configuration or importing the new one, which overwrites the scoping option. -- Export – Take the currently configured scoping options in the job and export it to a `.fsaascope` +- Export – Take the configured scoping options in the job and export it to a `.fsaascope` file -By default, priority is assigned in the order it is added to the table. Priority can also be -manually assigned with the Increase Priority and Decrease Priority buttons or in the +By default, priority follows the order in which you add items to the table. You can also manually +assign priority with the Increase Priority and Decrease Priority buttons or in the [Scoping Configuration Window](#scoping-configuration-window). If there is a conflict between an inclusion scoping option and an exclusion scoping option with the same priority, the inclusion takes precedence. @@ -45,8 +45,8 @@ scoping options and the expected results. ## Scoping Configuration Window -The Scoping Configuration Window allows a specific share or folder to be included or excluded from -the scan. Only included resources require additional scoping. Remember, these settings override the +Use the Scoping Configuration Window to include or exclude a specific share or folder from the +scan. Only included resources require additional scoping. Remember, these settings override the default scoping settings for the selected resource. ![Scoping Configuration Window](/images/accessanalyzer/12.0/admin/datacollector/fsaa/scopingconfigurationwindow.webp) @@ -54,7 +54,7 @@ default scoping settings for the selected resource. Set the Resource Name and Host Name: - Resource Name – Specify a local path or individual share to the target folder or the share name -- Host Name – Apply scoping options to a specific target host. If a host name is not supplied, all +- Host Name – Apply scoping options to a specific target host. If a host name isn't supplied, all hosts targeted by the job have the scoping options applied. Both the Resource Name and Host Name textboxes support regular expressions and pattern matching. @@ -94,15 +94,15 @@ Then set Scoping Type and Priority: :::note Any included files or folders inherit all options previously checked in the [FSAA: Default Scoping Options](/docs/accessanalyzer/12.0/admin/datacollector/fsaa/defaultscopingoptions/defaultscopingoptions.md) page. Manually apply new options if - the default ones are not desired in this scan. + the default ones aren't desired in this scan. ::: - Priority – Numerical value that determines which options are used in the case of more than one scoping option overlaps for a particular resource. Lower numerical values have a higher priority for this scan. When multiple scoping options are added to a single resource, and there is no - conflict, the scoping options are merged. However, in some instances, the settings conflict. Below - are some known conflicts and their results: + conflict, the scoping options are merged. However, in some instances, the settings conflict. The + following are some known conflicts and their results: - Conflict between two options for a single resource – Higher priority takes precedence - Folder scoping option conflicts with a share scoping option – Folder takes precedence - Conflict between two scoping options with the same priority – Path determines which option is @@ -176,11 +176,13 @@ All other folder paths are excluded. **Additional Considerations** -The scoping options listed above can be used to scope for SMB shares and NFS exports but NFS exports -are enumerated differently. The include/exclude logic outlined above should be the same for both, -but when scoping for NFS exports the Resource Name should be the full path to the export. +Use the scoping options described in +[Scoping Configuration Window](#scoping-configuration-window) to scope for SMB shares and NFS +exports, but NFS exports are enumerated differently. The include/exclude logic described earlier +in this section should be the same for both, but when scoping for NFS exports the Resource Name +should be the full path to the export. -For example, in the scenario below, the NFS export named NFS_Export is included. All other exports +For example, in the following scenario, the NFS export named NFS_Export is included. All other exports are excluded. Within the NFS_Export export, folder path \ifs\NFS_Export\Test_Folder is included. All other folder paths are excluded. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/scopingqueries.md b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/scopingqueries.md index 1661d19d49..4ae51f993d 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/scopingqueries.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/scopingqueries.md @@ -48,17 +48,17 @@ The Scoping Queries buttons have the following functionality: :::note These two Scan Resource Filters are both Share Include queries by default. To restrict the -scan to only Open Shares or only DFS Shares it is necessary to also configure the Scoping Options on +scan to only Open Shares or only DFS Shares, also configure the Scoping Options on the previous page of the wizard to exclude all other shares. ::: -For example, to restrict the scan to only Open Shares and exclude all other shares, the Scoping -Options page should be configured as shown: +For example, to restrict the scan to only Open Shares and exclude all other shares, configure the +Scoping Options page as shown: ![FSAA Data Collector Wizard Scoping Options page Open shares configuration](/images/accessanalyzer/12.0/admin/datacollector/fsaa/scopingoptionsopenshares.webp) -The Scoping Queries page should be configured as shown: +Configure the Scoping Queries page as shown: ![FSAA Data Collector Wizard Scoping Queries page Open shares configuration](/images/accessanalyzer/12.0/admin/datacollector/fsaa/scopingqueriesopenshares.webp) @@ -67,8 +67,8 @@ scoping scenarios. ## Scoping Query Configuration Window -The Scoping Query Configuration window allows you to create a custom Scoping Query to specify shares -and folders to be included in or excluded from the scan. +Use the Scoping Query Configuration window to create a custom Scoping Query that specifies shares +and folders to include in or exclude from the scan. ![Scoping Query Configuration window](/images/accessanalyzer/12.0/admin/datacollector/fsaa/scopingqueryconfiguration.webp) @@ -93,8 +93,6 @@ Scoping Options Query Configuration window. ![Advanced Scoping Options Query Configuration window](/images/accessanalyzer/12.0/admin/datacollector/fsaa/advancedscopingoptionsqueryconfiguration.webp) -Follow the steps to configure a query. - **Step 1 –** Enter a SQL Query that will return a list of resources to be included in or excluded from the scan. @@ -115,5 +113,5 @@ Ensure that the data being retrieved by the query is expected. **Step 4 –** Click **OK**. -When a query configuration is enabled, the data collector runs against the target table to configure +When you enable a query configuration, the data collector runs against the target table to configure scoping for shares or folders in the environment. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/sddcriteria.md b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/sddcriteria.md index 165b34989f..5f83b30948 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/sddcriteria.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/sddcriteria.md @@ -6,8 +6,8 @@ sidebar_position: 120 # FSAA: SDD Criteria Settings -The SDD Criteria Settings page is where criteria to be used for discovering sensitive data during a -scan is configured. It is a wizard page for the category of Sensitive Data Scan. +Use the SDD Criteria Settings page to configure criteria for discovering sensitive data during a +scan. It is a wizard page for the category of Sensitive Data Scan. ![FSAA Data Collector Wizard SDD Criteria Settings page](/images/accessanalyzer/12.0/admin/datacollector/fsaa/sddcriteria.webp) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/sensitivedatasettings.md b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/sensitivedatasettings.md index 97dbafa8f1..59835126d3 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/sensitivedatasettings.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/sensitivedatasettings.md @@ -6,7 +6,7 @@ sidebar_position: 110 # FSAA: Sensitive Data Settings -The Sensitive Data Settings page is where sensitive data discovery settings are configured. It is a +Use the Sensitive Data Settings page to configure sensitive data discovery settings. It is a wizard page for the category of Sensitive Data Scan. ![FSAA Data Collector Wizard Sensitive Data Settings page](/images/accessanalyzer/12.0/admin/datacollector/fsaa/sensitivedata.webp) @@ -19,10 +19,9 @@ wizard page for the category of Sensitive Data Scan. sensitive data within digital images of physical documents :::note - The OCR option is intended to work for clear scanned physical documents or documents - directly converted to images, with standard fonts. It will not work for scanning photos of - documents and may not be able to recognize text on images of credit cards, driver's licenses, or - other identity cards. + The OCR option works for clear scanned physical documents or documents directly converted to + images, with standard fonts. It doesn't work for scanning photos of documents and may not + recognize text on images of credit cards, driver's licenses, or other identity cards. ::: @@ -45,7 +44,7 @@ Use the radio buttons to select the File types to scan: - Spreadsheets - Text/Markup files -- Perform differential scan of – Enables users to choose whether to employ incremental scanning: +- Perform differential scan of – Choose whether to employ incremental scanning: - Files modified or newly discovered since last scan – Scans newly discovered files and files with a modified date after the previous scan date @@ -53,10 +52,10 @@ Use the radio buttons to select the File types to scan: - Files modified within the last [number] days – Only scans files with a modified date within the specified date range -The Performance Options section allows the user to modulate the efficiency of SDD scans. +Use the Performance Options section to adjust the efficiency of SDD scans. - Number of SDD scan processes [number] – Increases the number of SDD scanner processes that spawn - as part of a scan, increasing parallel scanning. The value should not exceed 2x the number of CPU + as part of a scan, increasing parallel scanning. The value shouldn't exceed 2x the number of CPU threads available. :::info diff --git a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/standardtables.md b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/standardtables.md index b45d6f6103..2c2b5578e5 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/standardtables.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/standardtables.md @@ -12,7 +12,7 @@ these tables regardless of the job executing the query. ## File System Access Auditing Tables & Views -The tables and their associated views are grouped by types. +The following sections group the tables and their views by type. **Structure Tables** @@ -26,8 +26,8 @@ The tables and their associated views are grouped by types. | Tables | Details | | -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| SA_FSAA_Trustees | Contains information about any domain user, group, or security principal that has been assigned permissions. This table does not contain local users and groups since none of the trustees in this table are specific to any one host. | -| SA_FSAA_LocalTrustees | Contains information about any trustees that do not belong to a domain, primarily local users and local groups | +| SA_FSAA_Trustees | Contains information about any domain user, group, or security principal that has been assigned permissions. This table doesn't contain local users and groups since none of the trustees in this table are specific to any one host. | +| SA_FSAA_LocalTrustees | Contains information about any trustees that don't belong to a domain, primarily local users and local groups | | SA_FSAA_TrusteeEquivalence | Contains information about Local Group membership. The trustees described can be found in the SA_FSAA_LocalTrustees table. | **Access Calculation Tables** @@ -69,7 +69,7 @@ The tables and their associated views are grouped by types. Views are the recommended way for Access Analyzer users to obtain the information gathered by the FSAA Data Collector. They contain additional information for building queries easily. The following -is an explanation of the corresponding views created for some of the tables generated by the FSAA +describes the corresponding views created for some of the tables generated by the FSAA Data Collector: **Permission Views** @@ -99,7 +99,7 @@ Data Collector: ## File System Activity Auditing Tables & Views -The tables and their associated views are grouped by types. +The following sections group the tables and their views by type. **Activity Changes Tables (FSAC)** @@ -118,7 +118,7 @@ The tables and their associated views are grouped by types. Views are the recommended way for Access Analyzer users to obtain the information gathered by the FSAA Data Collector. They contain additional information for building queries easily. The following -is an explanation of the corresponding views created for some of the tables generated by the FSAA +describes the corresponding views created for some of the tables generated by the FSAA Data Collector: **Activity Change Views (FSAC)** @@ -135,7 +135,7 @@ Data Collector: ## File System DFS Auditing Tables & Views -The tables and their associated views are grouped by types. +The following sections group the tables and their views by type. **FSDFS Tables** @@ -146,7 +146,7 @@ The tables and their associated views are grouped by types. Views are the recommended way for Access Analyzer users to obtain the information gathered by the FSAA Data Collector. They contain additional information for building queries easily. The following -is an explanation of the corresponding views created for some of the tables generated by the FSAA +describes the corresponding views created for some of the tables generated by the FSAA Data Collector: **FSDFS Views** @@ -157,7 +157,7 @@ Data Collector: ## File System Sensitive Data Discovery Auditing (SEEK) Tables & Views -The tables and their associated views are grouped by types. +The following sections group the tables and their views by type. **FSDLP Tables** @@ -171,7 +171,7 @@ The tables and their associated views are grouped by types. Views are the recommended way for Access Analyzer users to obtain the information gathered by the FSAA Data Collector. They contain additional information for building queries easily. The following -is an explanation of the corresponding views created for some of the tables generated by the FSAA +describes the corresponding views created for some of the tables generated by the FSAA Data Collector: **FSDLP Views** diff --git a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/workflows.md b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/workflows.md index d6a70ac09d..e224e70d93 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/workflows.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/workflows.md @@ -26,19 +26,19 @@ Additional workflows include: - Drop Tables & Views – Drops the standard reference tables and views :::tip -Remember, the FSAA Data Collector always records data in Standard Reference Tables, no matter what -job it is applied to. +Remember, the FSAA Data Collector always records data in Standard Reference Tables, no matter which +job runs it. ::: ## Remove File System Access Scan Category -The FSAA Data Collector can be used to clean-up or troubleshoot the applet and proxy scanning -servers. This would need to be done through a new job’s query. Set the host list and Connection -Profile to target the desired applet and proxy servers. +Use the FSAA Data Collector to clean up or troubleshoot the applet and proxy scanning +servers. Do this through a new job’s query. Set the host list and Connection +Profile to target the applet and proxy servers you want. -Follow these steps to build a new query using the FSAA Data Collector with the Remove scan -executables and data category. +To build a new query using the FSAA Data Collector with the Remove scan +executables and data category: **Step 1 –** Navigate to the **Configure** node of a new or chosen job and select the **Queries** node. @@ -46,7 +46,7 @@ node. **Step 2 –** In the Query Selection view, click the **Create Query** link. The Query Properties window displays. -**Step 3 –** Select the **Data Source** tab. From the **Data Collector** drop-down menu, select +**Step 3 –** Select the **Data Source** tab. From the **Data Collector** dropdown menu, select **FILESYSTEMACCESS** and then click the **Configure** button. The File System Access Auditor Data Collector Wizard opens. @@ -57,25 +57,25 @@ Collector Wizard opens. **Step 5 –** Click **Finish** to save the selection and close the wizard. Then click **OK** to close the Query Properties window. -This job has now been configured to run the FSAA Data Collector to remove the file system access +You've now configured this job to run the FSAA Data Collector and remove the file system access audit scan applet and data from the target server. Run the job to clean-up the targeted hosts. ## Update Proxy Service Category -The FSAA Data Collector can be used to upgrade the File System Proxy Service already installed on +Use the FSAA Data Collector to upgrade the File System Proxy Service already installed on proxy servers. The FS_UpdateProxy Job is preconfigured to run with the default settings with the category of Update proxy service. It is available through the Instant Job Library under the File System library. -The Update Proxy Service category option enables users with the ability to update v8.0+ File System -Proxy Service installations to newer versions. When this query is employed, the job compresses the -updated binaries and deploy them to the proxy server. Once the proxy server has no active sessions, -the Netwrix Access Analyzer (formerly Enterprise Auditor) FSAA Proxy Scanner service shuts down and -the components are updated. Finally, the service restarts itself. +The Update Proxy Service category option lets users update v8.0+ File System Proxy Service +installations to newer versions. When you use this query, the job compresses the updated binaries +and deploys them to the proxy server. When the proxy server has no active sessions, the Netwrix +Access Analyzer (formerly Enterprise Auditor) FSAA Proxy Scanner service shuts down and updates the +components. Finally, the service restarts itself. :::note -This option is not for updating v7.x File System Proxy installations. Those must be -manually updated to at least v8.0 on the proxy server before this query can be used to automate the +This option isn't for updating v7.x File System Proxy installations. You must manually update +those to at least v8.0 on the proxy server before you can use this query to automate the process. ::: @@ -85,14 +85,14 @@ the FS_UpdateProxy Job. ## Remove Host Category -The FSAA Data Collector can be used to clean-up the Standard Reference Tables by removing data for -particular hosts. This would need to be done through a new job’s query. The host to be removed is -set as the host list for the new job. The Connection Profile applied should be the same as the one +Use the FSAA Data Collector to clean up the Standard Reference Tables by removing data for +particular hosts. Do this through a new job’s query. Set the host to remove as the host list for +the new job. The Connection Profile applied should be the same as the one used for the associated **FileSystem** > **0.Collection** > … **Bulk Import** Job. :::warning -Be careful when applying this query task, as it results in the deletion of collected -data. Ensure proper configuration prior to job execution. +Be careful when applying this query task, as it deletes collected +data. Ensure proper configuration before job execution. ::: @@ -101,8 +101,8 @@ Manually enter individual hosts into the host list executing this query. ::: -Follow the steps to build a new query using the FSAA Data Collector with the Remove host data -category. +To build a new query using the FSAA Data Collector with the Remove host data +category: **Step 1 –** Navigate to the **Configure** node of a new or chosen job and select the **Queries** node. @@ -110,7 +110,7 @@ node. **Step 2 –** In the Query Selection view, click the **Create Query** link. The Query Properties window displays. -**Step 3 –** Select the **Data Source** tab. From the **Data Collector** drop-down menu, select +**Step 3 –** Select the **Data Source** tab. From the **Data Collector** dropdown menu, select **FILESYSTEMACCESS** and then click **Configure**. The File System Access Auditor Data Collector Wizard opens. @@ -121,25 +121,25 @@ Wizard opens. **Step 5 –** Click **Finish** to save the selection and close the wizard. Then click **OK** to close the Query Properties window. -This job has now been configured to run the FSAA Data Collector to remove the host identified in the +You've now configured this job to run the FSAA Data Collector and remove the host identified in the job’s **Configure** > **Hosts** node. Run the job to clean-up the targeted hosts. :::tip Remember, this job deletes data from the Access Analyzer database. Use caution and ensure proper -configuration prior to job execution. +configuration before job execution. ::: ## Remove Host and Criteria SDD Data The FS_SDD_DELETE job removes host and criteria sensitive data matches from the Tier 1 database. It -is preconfigured to run analysis tasks with temporary tables that requires modification prior to job +is preconfigured to run analysis tasks with temporary tables that requires modification before job execution. It is available through the Instant Job Library under the File System library. See the [Instant Job Wizard](/docs/accessanalyzer/12.0/admin/jobs/instantjobs/overview.md) topic for additional information. ![FS_SDD_DELETE Job in Job's Tree](/images/accessanalyzer/12.0/admin/datacollector/fsaa/sdddelete.webp) -The 0.Collection Job Group must be run before executing the FS_SDD_DELETE Job. +Run the 0.Collection Job Group before executing the FS_SDD_DELETE Job. ### Analysis Tasks for the FS_SDD_DELETE Job @@ -147,7 +147,7 @@ The analysis tasks are deselected by default. View the analysis tasks by navigat **Jobs** > **FS_SDD_DELETE** > **Configure** node and select **Analysis**. :::warning -Applying these analysis tasks result in the deletion of collected data. +Applying these analysis tasks deletes collected data. ::: @@ -159,10 +159,10 @@ Applying these analysis tasks result in the deletion of collected data. ### Configure the FS_SDD_DELETE Analysis Tasks -Follow the steps to configure and run the analysis tasks. +Configure and run the analysis tasks: -**Step 1 –** Prior to job execution, modify the desired analysis tasks using the -[Customizable Analysis Parameters for FS_SDD_DELETE Job](#customizable-analysis-parameters-for-fs_sdd_delete-job) +**Step 1 –** Before job execution, modify the analysis tasks you want using the +[Customizable Analysis Parameters for FS_SDD_DELETE Job](#customizable-analysis-parameters-for-fssdddelete-job) instructions. **Step 2 –** In the Analysis Selection Pane, check the type of analysis task that will be run. @@ -174,17 +174,17 @@ status is visible from the **Running Instances** node. analysis tasks. :::warning -Do not leave these analysis tasks checked in order to avoid accidental data loss. +Don't leave these analysis tasks checked to avoid accidental data loss. ::: -All of these tables have been dropped from the SQL Server database and the data is no longer +The job has dropped all of these tables from the SQL Server database, and the data is no longer available. ### Customizable Analysis Parameters for FS_SDD_DELETE Job -A customizable parameter enables Access Analyzer users to set the sensitive data values that will be -deleted during this job’s analysis. +A customizable parameter lets Access Analyzer users set the sensitive data values that this job +deletes during its analysis. | Analysis Task | Customizable Parameter Name | Value Indicates | | ---------------------- | --------------------------- | --------------------------------------------- | @@ -192,12 +192,11 @@ deleted during this job’s analysis. | Delete Criteria | #Criteria | List of Criteria to be removed | | Remove Host & Criteria | #Criteria #hosts | List of Criteria and Host Names to be removed | -The parameters that can be customized are listed in a section at the bottom of the SQL Script -Editor. Follow the steps to customize analysis task parameters. +You can customize these parameters in a section at the bottom of the SQL Script Editor. To customize analysis task parameters: **Step 1 –** Navigate to the **FS_SDD_DELETE** > **Configure** node and select **Analysis**. -**Step 2 –** In the Analysis Selection view, select the desired analysis task and click on +**Step 2 –** In the Analysis Selection view, select the analysis task you want and click **Analysis Configuration**. The SQL Script Editor opens. ![ FS_SDD_DELETE Job Analysis Task in SQL Script Editor](/images/accessanalyzer/12.0/admin/datacollector/fsaa/sdddeletesqlscripteditor.webp) @@ -207,7 +206,7 @@ or **#hosts** row, depending on the analysis task chosen, and then **Edit Table* window opens. :::warning -Do not change any parameters where the Value states `Created during execution`. +Don't change any parameters where the Value states `Created during execution`. ::: @@ -224,7 +223,7 @@ to save any changes. Other Edit Table buttons include: **Step 5 –** Click Save and Close to finalize the customization and close the SQL Script Editor. -The job is now ready to be executed. +The job is now ready to run. ## Drop Tables & Views @@ -246,7 +245,7 @@ The analysis tasks are deselected by default. View the analysis tasks by navigat **Jobs** > **FS_DropTables** > **Configure** node and select **Analysis**. :::warning -Applying these analysis tasks result in the deletion of collected data. +Applying these analysis tasks deletes collected data. ::: @@ -261,7 +260,7 @@ Applying these analysis tasks result in the deletion of collected data. - **4. Drop FSDFS Tables** – Drops the File System DFS Auditing tables imported from the previous runs - **5. Drop FSAA Tables** – Drops File System Access Auditing tables imported from the previous runs -Do not try to run these tasks separately, as they are designed to work together. Follow these steps +Don't try to run these tasks separately, as they are designed to work together. Follow these steps to run the analysis tasks: **Step 1 –** In the Analysis Selection Pane, click **Select All**. All tasks will be checked. @@ -273,9 +272,9 @@ status is visible from the **Running Job** node. All** to deselect these analysis tasks. :::warning -Do not leave these analysis tasks checked in order to avoid accidental data loss. +Don't leave these analysis tasks checked to avoid accidental data loss. ::: -All of these tables have been dropped from the SQL Server database and the data is no longer +The job has dropped all of these tables from the SQL Server database, and the data is no longer available. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/grouppolicy/category.md b/docs/accessanalyzer/12.0/admin/datacollector/grouppolicy/category.md index 09b98f598c..54c65db4b9 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/grouppolicy/category.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/grouppolicy/category.md @@ -6,23 +6,23 @@ sidebar_position: 10 # GroupPolicy: Category -On the GroupPolicy Data Collector Category page, select the required query category to be executed. +On the GroupPolicy Data Collector Category page, select the required query category to run. ![Group Policy Data Collector Wizard Category page](/images/accessanalyzer/12.0/admin/datacollector/grouppolicy/category.webp) The available categories are: - Group Policy Objects – Retrieves the GPO’s list in the domain and where each is linked -- Policies State – Provides the ability to return information on configured policies and policy +- Policies State – lets you return information on configured policies and policy parts from the individual policies which have been selected - - For example, selecting **Account Policies** > **Policy Password** will result in **Account - Policies** > **Policy Password** being returned for the targeted domains + - For example, if you select **Account Policies** > **Policy Password**, the results include + **Account Policies** > **Policy Password** for the targeted domains -- Policies State for all GPOs – Provides the ability to return information on selected policy parts +- Policies State for all GPOs – lets you return information on selected policy parts from all policies within the domain - - For example, selecting **Account Policies** > **Password Policy** will result in **Password - Policy** being returned for all policies in the targeted domains + - For example, if you select **Account Policies** > **Password Policy**, the results include + **Password Policy** for all policies in the targeted domains - Local policies – Returns effective security policies in effect at the individual workstation diff --git a/docs/accessanalyzer/12.0/admin/datacollector/grouppolicy/options.md b/docs/accessanalyzer/12.0/admin/datacollector/grouppolicy/options.md index e100cffcaa..2c64653e2c 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/grouppolicy/options.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/grouppolicy/options.md @@ -6,14 +6,14 @@ sidebar_position: 40 # GroupPolicy: Options -The Options page is used to configure how to return multi-valued properties and how policy results -are presented. It is a wizard page for all categories. +Use the Options page to configure how to return multi-valued properties and how to present policy +results. It is a wizard page for all categories. ![Group Policy Data Collector Wizard Options page](/images/accessanalyzer/12.0/admin/datacollector/grouppolicy/options.webp) The configurable options are: -- Result Presentation – Select one of the following options. This section is not available for the +- Result Presentation – Select one of the following options. This section isn't available for the Group Policy Objects category. - Each part of each policy on a new row diff --git a/docs/accessanalyzer/12.0/admin/datacollector/grouppolicy/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/grouppolicy/overview.md index 125793c892..a6cf34f161 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/grouppolicy/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/grouppolicy/overview.md @@ -6,13 +6,13 @@ sidebar_position: 240 # GroupPolicy Data Collector -The GroupPolicy Data Collector provides the ability to retrieve the GPO’s list in the domain and +The GroupPolicy Data Collector lets you retrieve the GPO’s list in the domain and where they are linked, return information on configured policies and policy parts from the -individual policies that have been selected, return information on selected policy parts from all +individual policies you select, return information on selected policy parts from all policies within the domain, and return effective security policies in effect at the individual workstation. -The GroupPolicy Data Collector is a core component of Access Analyzer, but it has been preconfigured +The GroupPolicy Data Collector is a core component of Access Analyzer, but it comes preconfigured within the Active Directory Solution and the Windows Solution. While the data collector is available with all Access Analyzer license options, the Windows Solution is only available with a special Access Analyzer licenses. See the following topics for additional information: @@ -38,7 +38,7 @@ Access Analyzer licenses. See the following topics for additional information: ## GroupPolicy Query Configuration -The GroupPolicy Data Collector is configured through the Group Policy Data Collector Wizard. The +Configure the GroupPolicy Data Collector through the Group Policy Data Collector Wizard. The available pages change based upon the query category selected. It contains the following wizard pages: @@ -51,5 +51,5 @@ pages: ![Group Policy Data Collector Wizard Welcome page](/images/accessanalyzer/12.0/admin/datacollector/grouppolicy/welcome.webp) -The Welcome page can be hidden by selecting the **Do not display this page the next time** checkbox -when the wizard is open and configuration settings are saved. +To hide the Welcome page, select the **Don't display this page the next time** checkbox while the +wizard is open; the wizard saves your configuration settings. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/grouppolicy/policieslist.md b/docs/accessanalyzer/12.0/admin/datacollector/grouppolicy/policieslist.md index f063e5361a..df3bb1bf34 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/grouppolicy/policieslist.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/grouppolicy/policieslist.md @@ -6,7 +6,7 @@ sidebar_position: 30 # GroupPolicy: Policies List -The Policies List page is where the policies from the desired GPOs to be queried are selected. It is +Use the Policies List page to select the policies from the GPOs you want to query. It is a wizard page for the categories of: - Policies State @@ -15,10 +15,10 @@ a wizard page for the categories of: ![Group Policy Data Collector Wizard Policies List page](/images/accessanalyzer/12.0/admin/datacollector/grouppolicy/policieslist.webp) -Select the policies or policy parts to be audited. The category dictates how this selection is -applied across the domain or local host. +Select the policies or policy parts you want to audit. The category dictates how this selection +applies across the domain or local host. -To search parts of a policy, drill into the policy and select the desired policy parts. Click +To search parts of a policy, drill into the policy and select the policy parts you want. Click **Check all** to select all properties, and click **Uncheck all** to deselect all properties. Search for a policy by entering a policy name in the Search box and clicking **Search**. @@ -27,4 +27,4 @@ The policy parts returned may have multiple values. ::: -At least one policy or policy part must be selected in order to proceed to the next wizard page. +You must select at least one policy or policy part to proceed to the next wizard page. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/grouppolicy/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/grouppolicy/summary.md index 61f1da8d45..02e385e3b3 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/grouppolicy/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/grouppolicy/summary.md @@ -10,6 +10,6 @@ The Summary page displays a summary of the configured query. It is a wizard page ![Group Policy Data Collector Wizard Summary page](/images/accessanalyzer/12.0/admin/datacollector/grouppolicy/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Group Policy Data Collector Wizard to ensure that no accidental clicks -are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** to close +the Group Policy Data Collector Wizard as a best practice, ensuring the wizard doesn't save any +accidental clicks. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/grouppolicy/target.md b/docs/accessanalyzer/12.0/admin/datacollector/grouppolicy/target.md index 42b2f688f3..fa959c71c7 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/grouppolicy/target.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/grouppolicy/target.md @@ -6,8 +6,8 @@ sidebar_position: 20 # GroupPolicy: Target -The Target page is where a host from which to get data (in wizard only) and .admx source are -identified. It is a wizard page for the categories of: +Use the Target page to identify the host to get data from (wizard only) and the .admx source. It is +a wizard page for the categories of: - Policies State - Policies State for all GPOs @@ -19,14 +19,14 @@ In the Connect to section of the page, select from the following options: - Default domain – Select this option to connect to the default domain - This domain – Select this option and click the ellipsis to open the Browse for Domain window. Then - select the desired domain. Click **OK**. + select the domain you want. Click **OK**. -In the Use these job credentials to browse section of the page, if multiple credentials are set up, -select the credentials to use for the query from the dropdown menu. +In the Use these job credentials to browse section of the page, if you've set up multiple +credentials, select the credentials to use for the query from the dropdown menu. :::note -If the Default Connection profile has only one set of credentials, the dropdown will be -grayed out and will only display the default credentials for that profile. +If the Default Connection profile has only one set of credentials, the dropdown grays out and +displays only the default credentials for that profile. ::: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/inifile/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/inifile/overview.md index af012e4220..8c1d79387a 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/inifile/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/inifile/overview.md @@ -36,5 +36,5 @@ following wizard pages: ![INI File Data Collector Wizard Welcome page](/images/accessanalyzer/12.0/admin/datacollector/inifile/welcome.webp) -The Welcome page can be hidden by selecting the **Do not display this page the next time** box when -the wizard is open and configuration settings are saved. +Select the **Don't display this page the next time** box to hide the Welcome page when the wizard is +open and configuration settings are saved. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/inifile/properties.md b/docs/accessanalyzer/12.0/admin/datacollector/inifile/properties.md index c6fa84776c..ccc8ee72b4 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/inifile/properties.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/inifile/properties.md @@ -15,7 +15,7 @@ Use the following options to determine which data to adult: - All contents – Collect all contents from the INI file :::note - `*` can be used for matching wildcard or single characters. + Use `*` to match a wildcard or single character. ::: @@ -27,7 +27,7 @@ Use the following options to determine which data to adult: - Click the ellipses (**…**) to open a file explorer window - Select an appropriate .INI file -- Properties – Select a checkbox next to any desired properties. **Select All** or **Clear All** can - also be used. +- Properties – Select a checkbox next to any desired properties, or use **Select All** or **Clear + All**. - If **Differences from standard** is selected, all properties are selected and cannot be altered. + If **Differences from standard** is selected, all properties are selected and can't be altered. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/inifile/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/inifile/summary.md index b7146a1112..d1faefee09 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/inifile/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/inifile/summary.md @@ -6,10 +6,9 @@ sidebar_position: 30 # INIFile: Summary -The Summary page is where the selected configuration settings are listed. +The Summary page lists the selected configuration settings. ![INI File Data Collector Wizard Summary page](/images/accessanalyzer/12.0/admin/datacollector/inifile/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the INIFile Data Collector Wizard ensuring that no accidental clicks are -saved. +Click **Finish** to save configuration changes. If you didn't make changes, click **Cancel** to close +the INIFile Data Collector Wizard and avoid saving accidental clicks. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/inifile/targetfiles.md b/docs/accessanalyzer/12.0/admin/datacollector/inifile/targetfiles.md index dfaaa7850b..9a74b5b121 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/inifile/targetfiles.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/inifile/targetfiles.md @@ -20,7 +20,7 @@ Configure the Target Files options: Browser and connect to a host to select a registry key and path to be used for the lookup. - Registry Value – This value is automatically populated from the registry key - - Levels – The Levels slider can be used to truncate the path for the key value in the Adjust + - Levels – Use the Levels slider to truncate the path for the key value in the Adjust Path dialog box - Current value – Displays the current value for the registry key diff --git a/docs/accessanalyzer/12.0/admin/datacollector/ldap.md b/docs/accessanalyzer/12.0/admin/datacollector/ldap.md index 2f4f4d1743..00bb6c34e4 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/ldap.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/ldap.md @@ -6,10 +6,10 @@ sidebar_position: 260 # LDAP Data Collector -The LDAP Data Collector uses LDAP to query Active Directory returning the specified objects and -attributes. For example, a query can be configured to return all user objects at the selected level. -Another query can be configured to return a master list of all user objects found within the target -domain. Wildcards and LDAP filters can be applied to the query configurations. +The LDAP Data Collector uses LDAP to query Active Directory and return the specified objects and +attributes. For example, you can configure a query to return all user objects at the selected level. +You can configure another query to return a master list of all user objects found within the target +domain. You can apply wildcards and LDAP filters to the query configurations. The LDAP Data Collector is a core component of Access Analyzer, but it has been preconfigured within the Active Directory Solution. While the data collector is available with all Access Analyzer @@ -38,7 +38,7 @@ following configuration options: - Connect to the server – Use the default domain controller entered in the box, or enter an alternate server -- Naming context – Select a directory partition from the drop-down list: **Default Context**, +- Naming context – Select a directory partition from the dropdown list: **Default Context**, **Configuration Context**, or **Schema Context** - Connect – Connects to the domain specified. The root folder of the domain is displayed in the left pane of the window. @@ -77,7 +77,7 @@ The Options window contains configure connection options and multi-value results - Server Port - If the Connect Securely with TLS/SSL option is selected, use Server Port `686` - - If the Connect Securely with TLS/SSL option is not selected, use Server Port `389` + - If the Connect Securely with TLS/SSL option isn't selected, use Server Port `389` - Authentication Type @@ -119,7 +119,7 @@ The Custom Filter window provides options for creating a complex filter. ![Custom Filter window](/images/accessanalyzer/12.0/admin/datacollector/customfilter.webp) -Select a **Field** and **Condition** from the drop-down lists. Enter a **Value** for the condition. +Select a **Field** and **Condition** from the dropdown lists. Enter a **Value** for the condition. Click **Add** to add the filter to the Filter Lines table. - Filter Lines will be combined with a logical – Select the **AND** or **OR** option. **AND** is diff --git a/docs/accessanalyzer/12.0/admin/datacollector/nis/category.md b/docs/accessanalyzer/12.0/admin/datacollector/nis/category.md index 6aaad7933e..89f61bd95d 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/nis/category.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/nis/category.md @@ -6,7 +6,7 @@ sidebar_position: 30 # NIS: Category -The Category page is used to identify which type of NIS information to retrieve. +Use the Category page to identify which type of NIS information to retrieve. ![NIS Data Collector Wizard Category page](/images/accessanalyzer/12.0/admin/datacollector/nis/category.webp) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/nis/configurejob.md b/docs/accessanalyzer/12.0/admin/datacollector/nis/configurejob.md index eb11058b3c..94cf3396af 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/nis/configurejob.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/nis/configurejob.md @@ -6,13 +6,13 @@ sidebar_position: 20 # Unix Connection Profile & Host List -The NIS Data Collector requires a custom Connection Profile and host list be created and assigned to -the job or job group conducting the data collection. The host inventory option during host list -creation makes it necessary to configure the Connection Profile first. +The NIS Data Collector requires you to create a custom Connection Profile and host list and assign +them to the job or job group conducting the data collection. The host inventory option during host +list creation requires you to configure the Connection Profile first. ## Connection Profile -Creating the Connection Profile requires having an account with access to the targeted NIS server. +Creating the Connection Profile requires an account with access to the targeted NIS server. Create a Connection Profile and set the following information on the User Credentials window: @@ -24,17 +24,17 @@ Create a Connection Profile and set the following information on the User Creden - Password/Confirm - If not using a private key, enter the **Password** and re-type in the **Confirm** field - - If using a private key, then the password is not needed. Provide the private key information + - If using a private key, then the password isn't needed. Provide the private key information in the **Use the following private key when connecting** field. - Use the following port/ports(CSV) for SSH - - The SSH port needs to be opened in software and hardware firewalls + - Open the SSH port in software and hardware firewalls - If desired, select this option and provide the port value - Use the following private key when connecting - - This option uses the authentication method of an SSH Private Key + - This option uses SSH private key authentication - Supported Key types: - Open SSH @@ -42,7 +42,7 @@ Create a Connection Profile and set the following information on the User Creden - If desired, select this option and provide the key value -Once the Connection Profile is created, it is time to create the custom host list. See the +After you create the Connection Profile, create the custom host list. See the [Connection](/docs/accessanalyzer/12.0/admin/settings/connection/overview.md) topic for additional information. ## Custom Host List diff --git a/docs/accessanalyzer/12.0/admin/datacollector/nis/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/nis/overview.md index e8313bbcf2..6436ddd976 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/nis/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/nis/overview.md @@ -24,7 +24,7 @@ information. **Permissions** -- No special permissions are needed aside from access to a NIS server +- This data collector needs no special permissions aside from access to a NIS server ## NIS Query Configuration @@ -41,5 +41,5 @@ following wizard pages: ![NIS Data Collector Wizard Welcome page](/images/accessanalyzer/12.0/admin/datacollector/nis/welcome.webp) -The Welcome page can be hidden by selecting the **Do not display this page the next time** checkbox -when the wizard is open and configuration settings are saved. +Select the **Don't display this page the next time** checkbox to hide the Welcome page when the +wizard is open and configuration settings are saved. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/nis/query.md b/docs/accessanalyzer/12.0/admin/datacollector/nis/query.md index 0a8332d717..59826c83a6 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/nis/query.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/nis/query.md @@ -6,8 +6,8 @@ sidebar_position: 60 # NIS: NIS Query -The NIS Query page is where the NIS query regular expressions are configured and tested. It is a -wizard page for the category of: +Use the NIS Query page to configure and test the NIS query regular expressions. It is a wizard page +for the category of: - Custom NIS Scan diff --git a/docs/accessanalyzer/12.0/admin/datacollector/nis/results.md b/docs/accessanalyzer/12.0/admin/datacollector/nis/results.md index c0b88759e4..3b3f5db625 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/nis/results.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/nis/results.md @@ -6,15 +6,15 @@ sidebar_position: 70 # NIS: Results -The Results page is where properties from Unix to be gathered are selected. It is a wizard page for -both categories. +Use the Results page to select properties from Unix to gather. It is a wizard page for both +categories. ![NIS Data Collector Wizard Results page](/images/accessanalyzer/12.0/admin/datacollector/nis/results.webp) -Available properties have checkboxes that can be selected individually, or you can use the **Select -All**, **Clear All**, and **Reset to defaults** buttons. All selected properties are gathered. -Available properties vary based on the category selected. +Select available properties' checkboxes individually, or use the **Select All**, **Clear All**, and +**Reset to defaults** buttons. Access Analyzer gathers all selected properties. Available properties +vary based on the category selected. -This information is not available within the standard reference tables and views. Instead, this -information can be viewed in the `SA_[Job Name]_DEFAULT` table, which is created when any of these -properties are selected. +This information isn't available within the standard reference tables and views. Instead, you can +view this information in the `SA_[Job Name]_DEFAULT` table, which is created when you select any of +these properties. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/nis/settings.md b/docs/accessanalyzer/12.0/admin/datacollector/nis/settings.md index 9cba17c616..1300937ab5 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/nis/settings.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/nis/settings.md @@ -6,8 +6,8 @@ sidebar_position: 40 # NIS: NIS Settings -The NIS Settings page is where the NIS domain and a NIS server are configured for testing. It is a -wizard page for both categories. +Use the NIS Settings page to configure the NIS domain and a NIS server for testing. It is a wizard +page for both categories. ![NIS Data Collector Wizard NIS Settings page](/images/accessanalyzer/12.0/admin/datacollector/nis/settings.webp) @@ -15,8 +15,8 @@ Configure the NIS domain and sample NIS server: - NIS Domain Name – Enter the case-sensitive name of the NIS domain to scan. This is the value returned by `/bin/domainname` on UNIX systems. -- (Optional) Sample NIS Server – Enter the host name or IP address of a NIS server for the above - domain to use for testing. This system should be running the `ypserv` process and be accessible +- (Optional) Sample NIS Server – Enter the host name or IP address of a NIS server for the NIS domain + to use for testing. This system should be running the `ypserv` process and be accessible from the Access Analyzer Console. Then, click **Test**. - Test – The data collector attempts to connect to the specified server and access information from the specified domain. It returns a message indicating success or failure. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/nis/sidmappings.md b/docs/accessanalyzer/12.0/admin/datacollector/nis/sidmappings.md index 09a5960437..1bca286e37 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/nis/sidmappings.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/nis/sidmappings.md @@ -6,13 +6,14 @@ sidebar_position: 50 # NIS: SID Mappings -The SID Mappings page is where the Windows-style SID mappings for the Unix User ID and Group ID are -specified. It is a wizard page for the category of: +Use the SID Mappings page to specify the Windows-style SID mappings for the Unix User ID and Group +ID. It is a wizard page for the category of: - Scan NIS User and Groups ![NIS Data Collector Wizard SID Mappings page](/images/accessanalyzer/12.0/admin/datacollector/nis/sidmappings.webp) The default settings work for most environments. Use this page to **Add**, **Edit**, or **Remove** -ID Mappings. Multiple entries are allowed. For each range of User ID or Group ID entered, the offset -is added to the ID and the resulting SID is the format with `%d` replaced by the ID. +ID Mappings. You can add multiple entries. For each range of User ID or Group ID entered, Access +Analyzer adds the offset to the ID, and the resulting SID uses the format with `%d` replaced by the +ID. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/nis/standardtables.md b/docs/accessanalyzer/12.0/admin/datacollector/nis/standardtables.md index 50c7956833..115b6cca4a 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/nis/standardtables.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/nis/standardtables.md @@ -10,7 +10,7 @@ The NIS Data Collector gathers essential user and group inventory information in reference tables. Unlike other Access Analyzer data collectors, the NIS Data Collector writes data to these tables regardless of the job executing the query. -These tables and their associated views are outlined below: +These tables and their associated views appear in the following table: | Table | Details | | ------------------- | -------------------------------------------------------------------------------------- | @@ -19,9 +19,8 @@ These tables and their associated views are outlined below: | SA_NIS_Users | Contains extended information about users, department, title, and so on | Views are the recommended way for Access Analyzer users to obtain the information gathered by the -NIS Data Collector. They contain additional information for building queries easily. The following -is an explanation of the corresponding view created for some of the tables generated by the NIS Data -Collector: +NIS Data Collector. They contain additional information for building queries. The following table +explains the corresponding view created for some of the tables generated by the NIS Data Collector: | Views | Details | | ----------------------- | ------------------------------------- | diff --git a/docs/accessanalyzer/12.0/admin/datacollector/nis/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/nis/summary.md index 1a2be70801..7efc385254 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/nis/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/nis/summary.md @@ -6,11 +6,9 @@ sidebar_position: 80 # NIS: Summary -The Summary page is where configuration settings are summarized. It is a wizard page for both -categories. +The Summary page summarizes the configuration settings. It is a wizard page for both categories. ![NIS Data Collector Wizard Summary page](/images/accessanalyzer/12.0/admin/datacollector/nis/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the NIS Data Collector Wizard to ensure that no accidental clicks are -saved. +Click **Finish** to save configuration changes. If you didn't make changes, click **Cancel** to close +the NIS Data Collector Wizard and avoid saving accidental clicks. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/nosql/category.md b/docs/accessanalyzer/12.0/admin/datacollector/nosql/category.md index 2c6a615906..7566b39efe 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/nosql/category.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/nosql/category.md @@ -31,5 +31,5 @@ The query categories are: - NoSQL Utilities - - Remove NoSQL Storage Tables — All connection related and filter data will be removed for + - Remove NoSQL Storage Tables — Removes all connection-related and filter data for NoSQL databases diff --git a/docs/accessanalyzer/12.0/admin/datacollector/nosql/configurejob.md b/docs/accessanalyzer/12.0/admin/datacollector/nosql/configurejob.md index bbb862cb73..5ef373f9e5 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/nosql/configurejob.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/nosql/configurejob.md @@ -19,9 +19,9 @@ window. For an Active Directory account, set the following on the User Credentials window: - Select Account Type – Active Directory Account -- Domain – Drop-down menu with available trusted domains will appear. Either type the short domain +- Domain – dropdown menu with available trusted domains will appear. Either enter the short domain name in the textbox or select a domain from the menu. -- User name – Type the user name +- User name – Enter the user name - Password Storage – Choose the option for credential password storage: - Application – Uses the configured Profile Security setting as selected at the **Settings** > @@ -29,10 +29,10 @@ For an Active Directory account, set the following on the User Credentials windo additional information. - CyberArk – Uses the CyberArk Enterprise Password Vault. See the [CyberArk Integration](/docs/accessanalyzer/12.0/admin/settings/connection/cyberarkintegration.md) topic for additional - information. The password fields do not apply for CyberArk password storage. + information. The password fields don't apply for CyberArk password storage. -- Password – Type the password -- Confirm – Re-type the password +- Password – Enter the password +- Confirm – Re-enter the password **SQL** @@ -43,8 +43,8 @@ For a SQL account, set the following on the User Credentials window: - Password Storage – Application (Uses the configured Profile Security setting as selected at the **Settings** > **Application** node. See the [Application](/docs/accessanalyzer/12.0/admin/settings/application/overview.md) topic for additional information.) -- Password – Type the password -- Confirm – Re-type the password +- Password – Enter the password +- Confirm – Re-enter the password See the [Connection](/docs/accessanalyzer/12.0/admin/settings/connection/overview.md) and [Application](/docs/accessanalyzer/12.0/admin/settings/application/overview.md) topics for additional information. @@ -52,10 +52,9 @@ See the [Connection](/docs/accessanalyzer/12.0/admin/settings/connection/overvie ## Host List Jobs using the NoSQL Data Collector must create a host list with the servers containing the target -databases. Setup the list of MongoDB hosts that needs to be monitored. Be sure to use a specific +databases. Set up the list of MongoDB hosts to monitor. Be sure to use a specific host name (if forcing the connection to a secondary host) or just the cluster name if connecting to the cluster. See the [Host Management](/docs/accessanalyzer/12.0/admin/hostmanagement/overview.md) topic for additional information. -Additionally, the database clusters / instances must be added to the Filter page in the query -configuration. See the [NoSQL: Filter](/docs/accessanalyzer/12.0/admin/datacollector/nosql/filter.md) topic for additional information. +Additionally, add the database clusters/instances to the Filter page in the query configuration. See the [NoSQL: Filter](/docs/accessanalyzer/12.0/admin/datacollector/nosql/filter.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/nosql/criteria.md b/docs/accessanalyzer/12.0/admin/datacollector/nosql/criteria.md index 6ac48d8e8a..904f39ddad 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/nosql/criteria.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/nosql/criteria.md @@ -6,8 +6,8 @@ sidebar_position: 40 # NoSQL: Criteria -The Criteria page is where the criteria to be used for discovering sensitive data is configured. It -is a wizard page for the category of Sensitive Data Collection. +Use the Criteria page to configure the criteria for discovering sensitive data. It is a wizard page +for the category of Sensitive Data Collection. ![NoSQL Data Collector Wizard Criteria page](/images/accessanalyzer/12.0/admin/datacollector/nosql/criteria.webp) @@ -21,8 +21,8 @@ The options on the Criteria page are: - Select All – Click **Select All** to enable all sensitive data criteria for scanning - Clear All – Click **Clear All** to remove all selections from the table - - Select the checkboxes next to the sensitive data criteria options to enable it to be scanned - for during job execution + - Select the checkboxes next to the sensitive data criteria options to scan for them during job + execution The table contains the following types of criteria: @@ -36,7 +36,7 @@ The table contains the following types of criteria: :::note Adding unnecessary criteria can adversely impact the scanner performance and can cause the -scanning job to take a long time. If performance is adversely affected, revisit the sensitive data -scanning criteria and remove criteria that is not required. +scanning job to take a long time. If performance suffers, revisit the sensitive data scanning +criteria and remove criteria that isn't required. ::: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/nosql/filter.md b/docs/accessanalyzer/12.0/admin/datacollector/nosql/filter.md index 84c26d9910..5f0dc44832 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/nosql/filter.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/nosql/filter.md @@ -6,10 +6,10 @@ sidebar_position: 50 # NoSQL: Filter -The Filter page is where the query can be scoped to target specific databases or instances. It is a -wizard page for the Sensitive Data Collection category. +Use the Filter page to scope the query to target specific databases or instances. It is a wizard +page for the Sensitive Data Collection category. -It is necessary to populate the available Mongo databases/instances before the query can be scoped. +Populate the available Mongo databases/instances before you can scope the query. See the [Manage Connections Window](#manage-connections-window) topic for additional information. ![NoSQL Data Collector Wizard Filter page](/images/accessanalyzer/12.0/admin/datacollector/nosql/filter.webp) @@ -40,7 +40,7 @@ The configurable filter options are: - Selections — Displays selected database objects for which the query has been scoped. Right click to open context menu: - - Remove Pattern — Selected database/instance will be removed from the query + - Remove Pattern — Removes the selected database/instance from the query - Edit Pattern — Opens the Edit Pattern dialogue with the following options (See the [Build or Edit Pattern](#build-or-edit-pattern) topic for additional information): @@ -50,7 +50,7 @@ The configurable filter options are: ## Manage Connections Window -The Manage Connections window enables users to add MongoDB database instances to search for +Use the Manage Connections window to add MongoDB database instances to search for sensitive data. Click **Connections** to open the window. ![Manage Connections window](/images/accessanalyzer/12.0/admin/datacollector/nosql/manageconnections.webp) @@ -64,8 +64,8 @@ additional information on how to connect to a MongoDB database, see the MongoDB - Is Active — Select the checkbox to include the database on the Servers Pane on the Filter page - Server Label — The name of the server - Host — Name or IP address of the host where the database is located -- Port Number — Port number for the database. The default port is 27017. If a non-default port is - being used, it should be specified in the Port Number section. +- Port Number — Port number for the database. The default port is 27017. If you use a non-default + port, specify it in the Port Number section. - Auth Database — The database used for authorization. Typically it is the **admin** database. - Read Preference — Read preference describes how MongoDB clients route read operations to the members of a replica set by default, an application directs its read operations to the primary @@ -80,7 +80,7 @@ In the Manage Connections table, the following information is also listed: information has been validated. **N** indicates the information has not been validated. - Last Inspected — Indicates the date and time of when the connection information was last inspected. If blank, the connection information has not yet been validated. -- Enable Impersonation – Impersonation does not apply to MongoDB and this column will be blank. +- Enable Impersonation – Impersonation doesn't apply to MongoDB and this column will be blank. The Manage Connections window has the following buttons: @@ -92,7 +92,7 @@ The Manage Connections window has the following buttons: #### Build or Edit Pattern -The Build / Edit Pattern window enables users to apply a custom scoping filter to the query. +Use the Build / Edit Pattern window to apply a custom scoping filter to the query. ![Edit Existing Pattern window](/images/accessanalyzer/12.0/admin/datacollector/nosql/editpattern.webp) @@ -104,7 +104,7 @@ The Build / Edit Pattern window has the following features: - Pattern — Build a custom filter to be applied to the selected database objects :::note - Color-coding indicating Excluded and Included objects does not display until after a - selection is validated using the **Validate Selections** button on the Filter page. + Color-coding indicating Excluded and Included objects doesn't display until you validate a + selection using the **Validate Selections** button on the Filter page. ::: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/nosql/options.md b/docs/accessanalyzer/12.0/admin/datacollector/nosql/options.md index 1c92f81c3e..a4d6b31355 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/nosql/options.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/nosql/options.md @@ -21,13 +21,13 @@ The sensitive data scan settings are: database or cluster - Limit of documents to scan — Scan limited number of documents in each database or cluster. This option is ideal when discovering sensitive data and has minimal impact on the MongoDB - cluster performance. However, if the Subject Profile Request feature is being leveraged, then - all the documents in all the database or cluster need to be scanned. + cluster performance. However, if you use the Subject Profile Request feature, Access Analyzer + must scan all the documents in the database or cluster. - Scan documents randomly — Access Analyzer requests a set of documents from each database when - scanning for sensitive data. The database engine does not return random data from a - collection. Instead, Access Analyzer returns sequential documents in a collection. In order to - ensure a statistical discrete uniform distribution of data being scanned, this option can be - selected. When selected, the Access Analyzer sensitive data scanner requests randomized + scanning for sensitive data. The database engine doesn't return random data from a + collection. Instead, Access Analyzer returns sequential documents in a collection. To + ensure a statistical discrete uniform distribution of the scanned data, select this option. + When selected, the Access Analyzer sensitive data scanner requests randomized documents from each collection in all the targeted databases. - Scan database names for sensitive data – Scans database names for sensitive data if the database @@ -40,10 +40,10 @@ The sensitive data scan settings are: - Store discovered sensitive data – Stores potentially sensitive data in the Access Analyzer database. Any sampled sensitive data discovered based on the matched criteria is stored in the - Access Analyzer database. This functionality can be disabled by clearing this checkbox. + Access Analyzer database. Clear this checkbox to disable this functionality. :::note - The **Store discovered sensitive data** option is required to view Content Audit + You must select the **Store discovered sensitive data** option to view Content Audit reports in the Access Information Center for MongoDB data. ::: @@ -54,10 +54,10 @@ The sensitive data scan settings are: ::: -- Resume scan from last point on error — Resumes scan from where the previous scan left off when the - scan was stopped as a result of an error +- Resume scan from last point on error — Resumes scan from where the previous scan left off when an + error stops the scan :::tip -Remember, the Sensitive Data Discovery Add-on is required to use the sensitive data collection +Remember, you need the Sensitive Data Discovery Add-on to use the sensitive data collection option. ::: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/nosql/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/nosql/overview.md index c85cd11d07..de634200d5 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/nosql/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/nosql/overview.md @@ -8,7 +8,7 @@ sidebar_position: 280 The NoSQL Data Collector for MongoDB provides information on MongoDB Cluster configuration, limited user permissions, scans collections for sensitive data, and identifies who has access to sensitive -data. It also supports the execution of custom queries against all targeted MongoDB cluster nodes. +data. It also supports executing custom queries against all targeted MongoDB cluster nodes. The NoSQL Data Collector has been preconfigured within the MongoDB Solution. Both this data collector and the solution are available with a special Access Analyzer license. See the @@ -22,7 +22,7 @@ information. **Ports** - MongoDB Cluster -- Default port is 27017 (A custom port can be configured) +- Default port is 27017 (you can configure a custom port) **Permissions** @@ -35,15 +35,15 @@ information. - Read Only access to any user databases is required for sensitive data discovery - Read access to NOSQL instance - Read access to MongoDB instance -- Requires NOSQL Full-Text and Semantic Extractions for Search feature to be installed on the target +- Requires installing the NOSQL Full-Text and Semantic Extractions for Search feature on the target NOSQL instances when using the Scans full rows for sensitive data option on the Options wizard page **Sensitive Data Discovery Considerations** -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the minimum amount -of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For example, if the job -is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are required (8x2=16). +If you run Sensitive Data Discovery (SDD) scans, increase the minimum amount of RAM. Each thread +requires a minimum of 2 additional GB of RAM per host. For example, if you configure the job to scan +8 hosts at a time, you need an extra 16 GB of RAM (8x2=16). ## NoSQL Query Configuration diff --git a/docs/accessanalyzer/12.0/admin/datacollector/nosql/results.md b/docs/accessanalyzer/12.0/admin/datacollector/nosql/results.md index 9c4d776c0d..16e36f5d79 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/nosql/results.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/nosql/results.md @@ -6,11 +6,10 @@ sidebar_position: 60 # NoSQL: Results -The Results page is where the properties that will be gathered are selected. It is a wizard page for -all of the categories. +Select the properties to gather on the Results page. This wizard page applies to all categories. ![NoSQL Data Collector Wizard Results page](/images/accessanalyzer/12.0/admin/datacollector/nosql/results.webp) -Properties can be selected individually, or the **Select All**, **Clear All**, and **Reset to -Defaults** buttons can be used. All selected properties are gathered. Available properties vary -based on the category selected. +Select properties individually, or use the **Select All**, **Clear All**, and **Reset to +Defaults** buttons. The data collector gathers all selected properties. Available properties vary +based on the selected category. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/nosql/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/nosql/summary.md index fec35f9e22..4926de6fe4 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/nosql/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/nosql/summary.md @@ -6,11 +6,10 @@ sidebar_position: 70 # NoSQL: Summary -The Summary page is where the configuration settings are summarized. It is a wizard page for all of -the categories. +The Summary page summarizes the configuration settings. This wizard page applies to all +categories. ![NoSQL Data Collector Wizard Summary page](/images/accessanalyzer/12.0/admin/datacollector/nosql/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the NoSQL Data Collector Wizard ensuring that no accidental clicks are -saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** instead +to close the NoSQL Data Collector Wizard without saving accidental clicks. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/overview.md index 7299bd1d59..0778e95556 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/overview.md @@ -11,57 +11,55 @@ This topic covers the configuration wizards that are unique to each data collect ## Query Selection -The Access Analyzer data collectors can collect information from a wide range of environments. Data -collection tasks are assigned to jobs at the **Configure** > **Queries** node level. See the +The Access Analyzer data collectors can collect information from a wide range of environments. You +assign data collection tasks to jobs at the **Configure** > **Queries** node level. See the [Queries Node](/docs/accessanalyzer/12.0/admin/jobs/job/configure/queries.md) topic for additional information. ![Query Selection page](/images/accessanalyzer/12.0/admin/datacollector/queryselection.webp) -The Query Selection page is split into the Tables and Queries sections. The Tables section has the +The Query Selection page has two sections: Tables and Queries. The Tables section has the following options: - Table – Select a pre-configured table or select DEFAULT to create a new one - Add Table – Add a new table to the Table dropdown list -- Rename Table – Rename the current table selected -- Delete Table – Delete the current table selected +- Rename Table – Rename the currently selected table +- Delete Table – Delete the currently selected table -The Queries section is where the Data Collectors are configured. The Queries section has the -following options: +Configure the Data Collectors in the Queries section, which has the following options: - Add from Library – Opens the Libraries window. Add a pre-built query from the Access Analyzer library. See the [Add Query from Library](#add-query-from-library) topic for additional information. - Create Query – Click **Create Query** to add a new query task to a job. See the [Create or Modify a Query](#create-or-modify-a-query) topic for additional information. -- Delete Query – Delete the currently selected query +- Delete Query – Delete the selected query - Query Properties – Select an existing query and click **Query Properties** to modify its configuration ### Add Query from Library -Pre-built queries can be added to the Data Collector job through the Libraries window. +Add pre-built queries to the Data Collector job through the Libraries window. ![Libraries window](/images/accessanalyzer/12.0/admin/datacollector/addqueryfromlibrary.webp) The Libraries window toolbar has the following options: -- Create New Library – Create a new library entry. The new Library will be added to the Library - dropdown menu. -- Delete Library – Deletes the currently selected library +- Create New Library – Create a new library entry. Access Analyzer adds the new library to the + Library dropdown menu. +- Delete Library – Deletes the selected library - Cut – Cut the selected task in the library to the clipboard - Copy – Copy the selected task in the library to the clipboard -- Paste – Paste cut or copied item from the clipboard into the currently selected library -- Delete Selected Task – Deletes the currently selected task +- Paste – Paste cut or copied item from the clipboard into the selected library +- Delete Selected Task – Deletes the selected task Click **Add** to confirm the query selection and add it to the Queries list on the Query Selection -page. If no selection is needed or intended, click **Cancel** to close the Libraries window without +page. If you don't want to make a selection, click **Cancel** to close the Libraries window without adding a pre-built query into the Queries list. ### Create or Modify a Query To open the Query Properties window, click **Create Query** for a new query or **Query Properties** -for an existing query. There are three tabs in the Query Properties window where queries can be -configured. These tabs are:. +for an existing query. The Query Properties window has three tabs for configuring queries: - [General Tab](#general-tab) - [Data Source Tab](#data-source-tab) @@ -81,15 +79,15 @@ The General tab displays: - Name – Name of the query supplied by the creator of the query - Description – Description of the query supplied by the creator of the query - Table – Name of the native data table for this query - - The table name is supplied by the creator in the Query Selection view - - Tables are named DEFAULT, unless modified - - Within the SQL database, the table name will be prefaced with `SA_[Job Name]_` + - The creator supplies the table name in the Query Selection view + - Access Analyzer names tables DEFAULT, unless the creator modifies the name + - Within the SQL database, Access Analyzer prefaces the table name with `SA_[Job Name]_` - ID – Query GUID generated by Access Analyzer for this query task. - - The query GUID is referenced by the **SMARTLog** Data Collector, **ExchangeMetrics** Data - Collector, and the **PowerShell** Data Collector. + - The **SMARTLog** Data Collector, **ExchangeMetrics** Data Collector, and **PowerShell** Data + Collector reference the query GUID. - When using the **SMARTLog** Data Collector or the **ExchangeMetrics** Data Collector, the - `state` file for the query’s Persist log state feature can be found in the SA_CommonData + `state` file for the query’s Persist log state feature is in the SA_CommonData folder in the Access Analyzer installation directory: …/STEALTHbits/StealthAUDIT/Jobs/SA_CommonData/[Data Collector]/[Query GUID]/[Target @@ -109,15 +107,15 @@ Use the Data Source tab to configure the data collector and query. The Data Source tab displays: -- Data Collector – Data collector selected from the drop-down menu. +- Data Collector – Data collector selected from the dropdown menu. - Query – Query configuration string. - Configure – Opens the wizard for the selected data collector. Each Data Collector task has its own Configuration Wizard. - Properties – Configured query properties. -When creating a new query, expand the **Data Collector** drop-down menu, which provides a list of -all licensed data collectors in alphabetical order. The **Query** and **Property** sections are -auto-filled according to the configuration. The buttons at the bottom of the Property section are +When creating a new query, expand the **Data Collector** dropdown menu, which provides a list of +all licensed data collectors in alphabetical order. The configuration automatically fills the +**Query** and **Property** sections. The buttons at the bottom of the Property section are for advanced features to manipulate the query. The **+** and **–** buttons manually add or remove individual properties from the query. The script button opens the VBScript Editor window for query manipulation scripts. @@ -144,15 +142,14 @@ The Filter tab has the following items: - Use the **+** and **–** buttons to add and remove filters from the query - Key – Labels identifying the configurable value in the filter - Value – When applicable, add a new value to the filter using the dropdown menu. Otherwise, create - a new one by typing in the desired value. + a new one by typing in the value you want. :::info -Use the default settings for filters. Filters can be used to substitute or delete +Use the default settings for filters. Use filters to substitute or delete data values during data collection. For more information on the impacts of adding filters to queries, contact [Netwrix Support](https://www.netwrix.com/support.html). ::: -Click **OK** to save changes and exist the Query Properties window. If no changes were made or -intended, it is best practice to click **Cancel** to exit the Query Properties window to ensure -unintended changes are not saved. +Click **OK** to save changes and exist the Query Properties window. If you made no changes, click +**Cancel** to exit the Query Properties window and avoid saving unintended changes. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/passwordsecurity/dictionaries.md b/docs/accessanalyzer/12.0/admin/datacollector/passwordsecurity/dictionaries.md index 883f3cc830..fd4e1c551f 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/passwordsecurity/dictionaries.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/passwordsecurity/dictionaries.md @@ -6,21 +6,21 @@ sidebar_position: 30 # PasswordSecurity: Dictionaries -The Dictionaries page provides configuration settings for storing passwords to be used as a -reference for the scan. +The Dictionaries page provides configuration settings for storing passwords that the scan uses as a +reference. ![Password Security Data Collection Wizard Dictionary options page](/images/accessanalyzer/12.0/admin/datacollector/passwordsecurity/dictionaries.webp) The configurable dictionary options are: - Use Stealthbits dictionary (> 100,000 passwords) – If enabled, compares passwords against - out-of-the-box dictionary comprised of commonly used password hashes + a built-in dictionary comprised of commonly used password hashes - Automatically update the Stealthbits dictionary – Checks for the latest version of the Netwrix - weak password dictionary file when the job is executed, and downloads the latest version from the + weak password dictionary file when the job runs, and downloads the latest version from the [Netwrix website](https://www.netwrix.com/) - - If the Access Analyzer server does not have an internet connection, the weak password - dictionary can be downloaded directly from the + - If the Access Analyzer server doesn't have an internet connection, you can download the weak + password dictionary directly from the [My Products](https://www.netwrix.com/my_products.html) page of the Netwrix website. See the [Download the Netwrix Weak Password Dictionary](#download-the-netwrix-weak-password-dictionary) topic for additional information. @@ -29,8 +29,8 @@ The configurable dictionary options are: - Add – Add a custom dictionary file in one of the following formats: - Plaintext – Line separated in a text file - - NLTM Hashes – Can be added with hashes or sorted hashes. The haveibeenpwned dictionary can be - used. See the + - NLTM Hashes – Provide hashes or sorted hashes. You can use the haveibeenpwned + dictionary. See the [Download and Configure the Have I Been Pwnd (HIBP) Hash List](#download-and-configure-the-have-i-been-pwnd-hibp-hash-list) topic for additional information. @@ -43,8 +43,8 @@ The configurable dictionary options are: ## Download the Netwrix Weak Password Dictionary -**Step 1 –** If the Access Analyzer server does not have an internet connection, the weak passwords -dictionary can be downloaded directly from the +**Step 1 –** If the Access Analyzer server doesn't have an internet connection, download the weak +passwords dictionary directly from the [My Products](https://www.netwrix.com/my_products.html) page of the Netwrix website. **Step 2 –** After downloading the dictionary file manually do one the following: @@ -67,18 +67,18 @@ dictionary can be downloaded directly from the ## Download and Configure the Have I Been Pwnd (HIBP) Hash List If you don't have internet access on the Netwrix Access Analyzer (formerly Enterprise Auditor) -server or want to download the files from another location that has internet access, you can do so -by using the Pwnd Passwords Downloader. +server, or you want to download the files from another location with internet access, use the Pwnd +Passwords Downloader. -The Pwnd Passwords Downloader is a Dotnet tool used to download all Pwned Passwords hash ranges and -save them offline so they can be used without a dependency on the k-anonymity API. Use this tool to -get the latest breached hashes from the Have I Been Pwnd (HIBP) database. +The Pwnd Passwords Downloader is a Dotnet tool that downloads all Pwned Passwords hash ranges and +saves them offline for use without a dependency on the k-anonymity API. Use this tool to get the +latest breached hashes from the Have I Been Pwnd (HIBP) database. :::note The [](https://github.com/HaveIBeenPwned/PwnedPasswordsDownloader)[Pwnd Passwords Downloader](https://github.com/HaveIBeenPwned/PwnedPasswordsDownloader) -is a third party, open source tool, created by the HaveIBeenPwned team and distributed under a BSD -3-Clause License. You might experience issues during the hash download process, depending on your +is a third-party, open source tool that the HaveIBeenPwned team created and distributes under a +BSD 3-Clause License. You might experience issues during the hash download process, depending on your threading settings or the load on the CloudFlare backend. The Pwnd Passwords Downloader tool will automatically retry to continue downloading the hashes until it fully completes the download process. @@ -94,14 +94,14 @@ The Pwnd Passwords Downloader has the following prerequisite: can download .NET 6 from Microsoft: [https://dotnet.microsoft.com/en-us/download/dotnet/6.0](https://dotnet.microsoft.com/en-us/download/dotnet/6.0) -The HIBP database takes up additional space on the machine where it is copied (approximately 13 GB, -but subject to change). The Have I Been Pwnd database (HIBP) hashes can take up to 30 GB. Make sure +The HIBP database takes up additional space on the machine where you copy it (approximately 13 GB, +but subject to change). The Have I Been Pwnd database (HIBP) hashes can take up to 30 GB. ensure that you have enough free space on your disk in your Netwrix Access Analyzer (formerly Enterprise Auditor) install directory (`%sainstalldir%`). ### Install the Pwnd Passwords Downloader -Follow the steps to install the Pwnd Passwords Downloader. +To install the Pwnd Passwords Downloader: **Step 3 –** Open command prompt, and navigate to your .NET install folder (for example, `C:\Program Files (x86)\dotnet`). @@ -118,7 +118,7 @@ dotnet tool install --global haveibeenpwned-downloader ### Update an Installed Pwnd Passwords Downloader -Follow the steps to update an installed Pwnd Passwords Downloader. +To update an installed Pwnd Passwords Downloader: **Step 1 –** Open the command prompt. @@ -132,7 +132,7 @@ dotnet tool update --global haveibeenpwned-downloader ### Download NTML Hashes with the Pwnd Passwords Downloader -Follow the steps to download NTLM hashes. +To download NTLM hashes: **Step 1 –** Navigate to the folder where you want to download the hashes. @@ -155,5 +155,5 @@ This screenshot shows the completed download. haveibeenpwned-downloader.exe -n pwnedpasswords_ntlm -o ``` -For a complete list of available parameters, please check the +For a complete list of available parameters, check the [Pwnd Passwords Downloader GitHub page](https://github.com/HaveIBeenPwned/PwnedPasswordsDownloader). diff --git a/docs/accessanalyzer/12.0/admin/datacollector/passwordsecurity/options.md b/docs/accessanalyzer/12.0/admin/datacollector/passwordsecurity/options.md index 1f6dc601cd..bc046abd80 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/passwordsecurity/options.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/passwordsecurity/options.md @@ -14,11 +14,11 @@ The configurable scan options are: - Encrypt communications with Active Directory (SSL) – Enables communication to the domain controller over SSL -- Analyze historical passwords – Scans historical passwords that have been stored in Active +- Analyze historical passwords – Scans historical passwords stored in Active Directory :::warning - Enabling the following option will return clear text passwords to be stored in the + Enabling the following option returns clear text passwords and stores them in the Access Analyzer database for the following exceptions: **Clear Text Password**, **Potential Keytab Password**, and **Weak Password** (when leveraging a plaintext password dictionary). ::: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/passwordsecurity/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/passwordsecurity/overview.md index 04a2672334..91b2c54e31 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/passwordsecurity/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/passwordsecurity/overview.md @@ -10,8 +10,8 @@ The PasswordSecurity Data Collector compares passwords stored in Active Director passwords in the Netwrix weak password dictionary or custom dictionaries. The PasswordSecurity Data Collector also checks for common misconfigurations with passwords in Active Directory. -The PasswordSecurity Data Collector is a core component of Access Analyzer, but it has been -preconfigured within the Active Directory Solution. While the data collector is available with all +The PasswordSecurity Data Collector is a core component of Access Analyzer, but Access Analyzer +preconfigures it within the Active Directory Solution. While the data collector is available with all Access Analyzer license options, the Active Directory Solution is only available with a special Access Analyzer license. See the [Active Directory Solution](/docs/accessanalyzer/12.0/solutions/activedirectory/overview.md) topic for additional @@ -37,7 +37,7 @@ information. ## PasswordSecurity Query Configuration -The PasswordSecurity Data Collector is configured through the Password Security Data Collector +Configure the PasswordSecurity Data Collector through the Password Security Data Collector Wizard, which contains the following wizard pages: - [PasswordSecurity: Category](/docs/accessanalyzer/12.0/admin/datacollector/passwordsecurity/category.md) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/passwordsecurity/results.md b/docs/accessanalyzer/12.0/admin/datacollector/passwordsecurity/results.md index 4aa9746f26..3964f199d3 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/passwordsecurity/results.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/passwordsecurity/results.md @@ -6,9 +6,9 @@ sidebar_position: 40 # PasswordSecurity: Results -The Results page is where Active Directory properties to be gathered are selected. +Select the Active Directory properties to gather on the Results page. ![Password Security Data Collection Wizard Results page](/images/accessanalyzer/12.0/admin/datacollector/passwordsecurity/results.webp) -Properties can be selected individually or by using the **Select All** or **Clear All** buttons. All -selected properties are gathered. +Select properties individually or use the **Select All** or **Clear All** buttons. The data +collector gathers all selected properties. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/passwordsecurity/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/passwordsecurity/summary.md index 4920001c4f..a56069fd31 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/passwordsecurity/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/passwordsecurity/summary.md @@ -10,6 +10,5 @@ The Summary page displays a summary of the configured query. ![Password Security Data Collection Wizard Summary page](/images/accessanalyzer/12.0/admin/datacollector/passwordsecurity/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Active Directory Data Collector Wizard to ensure that no accidental -clicks are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** instead to +close the Active Directory Data Collector Wizard without saving accidental clicks. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/permissionmatrix.md b/docs/accessanalyzer/12.0/admin/datacollector/permissionmatrix.md index 41d3ccb41c..acbe30ea28 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/permissionmatrix.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/permissionmatrix.md @@ -6,9 +6,8 @@ sidebar_position: 10 # Permissions by Data Collector (Matrix) -The Access Analyzer data collectors are capable of collecting information from a variety of sources. -Each data collector requires specific protocols, ports, and permissions for the collection of data -to occur. +The Access Analyzer data collectors can collect information from a variety of sources. +Each data collector requires specific protocols, ports, and permissions to collect data. Many data collectors are included as core components. However, some data collectors require specific license features. The following table provides a quick reference for each data collector. @@ -22,7 +21,7 @@ license features. The following table provides a quick reference for each data c | AWS | The AWS Data Collector collects IAM users, groups, roles, and policies, as well as S3 permissions, content, and sensitive data from the target Amazon Web Services (AWS) accounts. |
  • HTTPS
|
  • 443
| To collect details about the AWS Organization, the following permission is required:
  • organizations:DescribeOrganization
To collect details regarding IAM, the following permissions are required:
  • iam:GenerateCredentialReport
  • iam:GenerateServiceLastAccessedDetails
  • iam:Get\*
  • iam:List\*
  • iam:Simulate\*
  • sts:GetAccessKeyInfo
To collect details related to S3 buckets and objects, the following permissions are required:
  • s3:Describe\*
  • s3:Get\*
  • s3:HeadBucket
  • s3:List\*
| | AzureADInventory | The AzureADInventory Data Collector catalogs user and group object information from Microsoft Entra ID, formerly Azure Active Directory. This data collector is a core component of Access Analyzer and is preconfigured in the .Entra ID Inventory Solution. |
  • HTTP
  • HTTPS
  • REST
|
  • TCP 80 and 443
| **Microsoft Graph API**
Application Permissions:
  • AuditLog.Read.All – Read all audit log data
  • Directory.Read.All – Read directory data
Delegated Permissions:
  • Group.Read.All – Read all groups
  • User.Read.All – Read all users' full profiles
**Access URLs**
  • https://login.windows.net
  • https://graph.windows.net
  • https://login.microsoftonline.com
  • https://graph.microsoft.com
  • All sub-directories of the access URLs listed
| | Box _\*requires license_ | The Box Data Collector audits access, group membership, and content within a Box enterprise. |
  • HTTP
  • HTTPS
|
  • TCP 80
  • TCP 443
|
  • Box Enterprise Administrator
| -| CommandLineUtility | The CommandLineUtility Data Collector provides the ability to remotely spawn, execute, and extract data provided by a Microsoft native or third-party command line utility. |
  • Remote Registry
  • RPC
|
  • TCP 135-139
  • Randomly allocated high TCP ports
|
  • Member of the local Administrators group
| +| CommandLineUtility | The CommandLineUtility Data Collector lets you remotely spawn, execute, and extract data provided by a Microsoft native or third-party command line utility. |
  • Remote Registry
  • RPC
|
  • TCP 135-139
  • Randomly allocated high TCP ports
|
  • Member of the local Administrators group
| | DiskInfo | The DiskInfo Data Collector provides enumeration of disks and their associated properties. |
  • RPC
  • WMI
|
  • TCP 135
  • Randomly allocated high TCP ports
|
  • Member of the local Administrators group
| | DNS _\*requires license_ | The DNS Data Collector provides information regarding DNS configuration and records. |
  • RPC
|
  • TCP 135
  • Randomly allocated high TCP ports
|
  • Member of the Domain Administrators group
| | DropboxAccess _\*requires license_ | The DropboxAccess Data Collector audits access, group membership, and content within a Dropbox environment. |
  • HTTP
  • HTTPS
|
  • TCP 80
  • TCP443
|
  • Dropbox Team Administrator
| @@ -32,12 +31,12 @@ license features. The following table provides a quick reference for each data c | EWSPublicFolder _\*requires license_ | The EWSPublicFolder Data Collector provides configuration options to extract public folder contents, permissions, and sensitive data, and is preconfigured within the Exchange Solution. |
  • HTTPS
  • ADSI
  • LDAP
|
  • TCP 389
  • TCP 443
| For Exchange servers:
  • Exchange Admin Role
  • Discovery Management Role
  • Application Impersonation Role
  • Exchange Online License with a mailbox
For Exchange Online:
  • Exchange Admin Role
  • Discovery Management Role
  • Exchange Online License with a mailbox
| | Exchange2K _\*requires license_ | The Exchange2K Data Collector extracts configuration details from Exchange organizations for versions 2003 and later. |
  • LDAP
  • MAPI
  • PowerShell
  • RPC
  • WMI
|
  • TCP 135-139
  • Randomly allocated high TCP ports
  • TCP 389
  • Optional TCP 445
|
  • Member of the Exchange Administrator group
  • Domain Admin for AD property collection
  • Public Folder Management
| | ExchangeMailbox _\*requires license_ | The ExchangeMailbox Data Collector extracts configuration details from the Exchange Store to provide statistical, content, permission, and sensitive data reporting on mailboxes. |
  • MAPI
  • RPC
|
  • TCP 135
  • Randomly allocated high TCP ports
|
  • Member of the Exchange Administrator group
  • Organization Management
  • Discovery Management
| -| ExchangeMetrics _\*requires license_ | The ExchangeMetrics Data Collector collects Mail-Flow metrics from the Exchange Message Tracking Logs on the Exchange servers. Some examples of this include server volume and message size statistics. |
  • RPC
  • WMI
|
  • TCP 135
  • Randomly allocated high TCP ports
|
  • Member of the local Administrator group on the targeted Exchange server(s)
| -| ExchangePS _\*requires license_ | The ExchangePS Data Collector utilizes the Exchange CMDlets to return information about the Exchange environment utilizing PowerShell. This data collector has been designed to work with Exchange 2010 and newer. |
  • PowerShell
|
  • TCP 135
  • Randomly allocated high TCP ports
| For Exchange servers:
  • Remote PowerShell enabled on a single Exchange server
  • Windows Authentication enabled for the PowerShell Virtual Directory on the same Exchange server where Remote PowerShell has been enabled
  • View-Only Organization Management Role Group
  • Discovery Search Management Role Group
  • Public Folder Management Role Group
  • Mailbox Search Role
For Exchange Online:
  • Discovery Management Role
  • Organization Management Role
| +| ExchangeMetrics _\*requires license_ | The ExchangeMetrics Data Collector collects Mail-Flow metrics from the Exchange Message Tracking Logs on the Exchange servers. Some examples of this include server volume and message size statistics. |
  • RPC
  • WMI
|
  • TCP 135
  • Randomly allocated high TCP ports
|
  • Member of the local Administrator group on the targeted Exchange servers
| +| ExchangePS _\*requires license_ | The ExchangePS Data Collector uses the Exchange CMDlets to return information about the Exchange environment using PowerShell. This data collector has been designed to work with Exchange 2010 and newer. |
  • PowerShell
|
  • TCP 135
  • Randomly allocated high TCP ports
| For Exchange servers:
  • Remote PowerShell enabled on a single Exchange server
  • Windows Authentication enabled for the PowerShell Virtual Directory on the same Exchange server where Remote PowerShell has been enabled
  • View-Only Organization Management Role Group
  • Discovery Search Management Role Group
  • Public Folder Management Role Group
  • Mailbox Search Role
For Exchange Online:
  • Discovery Management Role
  • Organization Management Role
| | ExchangePublicFolder _\*requires license_ | The ExchangePublicFolder Data Collector audits an Exchange Public Folder, including contents, permissions, ownership, and replicas. |
  • MAPI
  • RPC
|
  • TCP 135
  • Randomly allocated high TCP ports
|
  • Member of the Exchange Administrator group
  • Organization Management
| | File | The File Data Collector provides file and folder enumeration, properties, and permissions. |
  • RPC
  • WMI
|
  • TCP 135-139
  • Randomly allocated high TCP ports
  • Optional TCP 445
|
  • Member of the Local Administrators group
| | FileSystemAccess (FSAA) _\*requires license_ | The FileSystemAccess (FSAA) Data Collector collects permissions, content, and activity, and sensitive data information for Windows and NAS file systems. |
  • Remote Registry
  • WMI
|
  • Ports vary based on the Scan Mode Option selected. See the [File System Scan Options](/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/scanoptions.md) topic for additional information.
|
  • Permissions vary based on the Scan Mode Option selected. See the [File System Supported Platforms](/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/filesystems.md) topic for additional information.
| -| GroupPolicy | The GroupPolicy Data Collector provides the ability to retrieve the GPO’s list in the domain and where they are linked, return information on configured policies and policy parts from the individual policies that have been selected, return information on selected policy parts from all policies within the domain, and return effective security policies in effect at the individual workstation. |
  • LDAP
  • RPC
|
  • TCP 389
  • TCP 135-139
  • Randomly allocated high TCP ports
|
  • Member of the Domain Administrators group (if targeting domain controllers)
  • Member of the Local Administrators group
| +| GroupPolicy | The GroupPolicy Data Collector lets you retrieve the GPO’s list in the domain and where they are linked, return information on configured policies and policy parts from the individual policies that have been selected, return information on selected policy parts from all policies within the domain, and return effective security policies in effect at the individual workstation. |
  • LDAP
  • RPC
|
  • TCP 389
  • TCP 135-139
  • Randomly allocated high TCP ports
|
  • Member of the Domain Administrators group (if targeting domain controllers)
  • Member of the Local Administrators group
| | INIFile | The INIFile Data Collector provides options to configure a task to collect information about log entries on target hosts. |
  • RPC
|
  • TCP 135-139
  • Randomly allocated high TCP ports
  • Optional TCP 445
|
  • Member of the Local Administrators group
| | LDAP | The LDAP Data Collector uses LDAP to query Active Directory returning the specified objects and attributes. |
  • LDAP
|
  • TCP 389
|
  • Member of the Domain Administrators group
| | NIS | The NIS Data Collector inventories a NIS domain for user and group information, mapping to Windows-style SIDs. |
  • NIS
|
  • TCP 111 or UDP 111
  • Randomly allocated high TCP ports
|
  • No special permissions are needed aside from access to a NIS server
| @@ -52,7 +51,7 @@ license features. The following table provides a quick reference for each data c | Services | The Services Data Collector enumerates status and settings from remote services. |
  • RPC
  • WMI
|
  • TCP 135-139
  • Randomly allocated high TCP ports
|
  • Member of the Local Administrators group
| | SharePointAccess (SPAA) _\*requires license_ | The SharePointAccess (SPAA) Data Collector audits access, group membership, and content within a SharePoint on-premises and SharePoint Online environment. The SPAA Data Collector has been preconfigured within the SharePoint Solution. |
  • MS SQL
  • Remote Registry
  • SP CSOM (Web Services via HTTP & HTTPS)
  • SP Server API
  • WCF AUTH via TCP (configurable)
|
  • Ports vary based on the Scan Mode selected and target environment. See the [SharePoint Scan Options](/docs/accessanalyzer/12.0/requirements/sharepoint/scanoptions/scanoptions.md) topic for additional information.
|
  • Permissions vary based on the Scan Mode selected and target environment. See the [SharePoint Support](/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepoint.md) topic for additional information.
| | SMARTLog | The SMARTLog Data Collector provides search and extraction of details from Windows Event Logs (online or offline) and Microsoft Exchange Internet Information Server (IIS) logs. |
  • Log
  • Remote Event
  • RPC
|
  • TCP 135
  • TCP 445
  • Randomly allocated high TCP ports
|
  • Member of the Domain Administrators group (if targeting domain controllers)
  • Member of the local Administrators group
| -| SQL _\*requires license_ | The SQL Data Collector provides information on database configuration, permissions, data extraction, application name of the application responsible for activity events, an IP Address or Host name of the client server, and sensitive data reports. This data collector also provides information on Oracle databases including infrastructure and operations. | TCP | For Db2 Target:
  • Specified by Instances table (default is 5000)
For MySQL Target:
  • Specified by Instances table (default is 3306)
For Oracle Target:
  • Specified by Instances table (default is 1521)
For PostgreSQL Target:
  • Specified by Instances table (default is 5432)
For SQL Target:
  • Specified by Instances table (default is 1433)
| **For MySQL Target:**
  • Read access to MySQL instance to include all databases contained within each instance
  • Windows Only — Domain Admin or Local Admin privilege
**For Oracle Target:**
  • User with SYSDBA role
  • Local Administrator on the target servers – Only applies to Windows Servers and not on Linux or Unix operating systems
**For PostgreSQL Target:**
  • Read access to all the databases in PostgreSQL cluster or instance
  • Windows Only — Domain Admin or Local Admin privilege
**For Redshift Target:**
  • Read-access to the following tables:
  • pg_tables
  • pg_user
**For SQL Target:**
For Instance Discovery, local rights on the target SQL Servers:
  • Local group membership to Remote Management Users
  • Permissions on the following WMI NameSpaces: `root\Microsoft\SQLServer, root\interop`
For permissions for data collection:
  • Read access to SQL instance
  • Requires SQL Full-Text and Semantic Extractions for Search feature to be installed on the target SQL instance(s) when using the **Scan full rows for sensitive data** option on the Options wizard page
  • Grant Authenticate Server to [DOMAIN\USER]
  • Grant Connect SQL to [DOMAIN\USER]
  • Grant View any database to [DOMAIN\USER]
  • Grant View any definition to [DOMAIN\USER]
  • Grant View server state to [DOMAIN\USER]
  • Grant Control Server to [DOMAIN\USER] (specifically required for the Weak Passwords Job)
| +| SQL _\*requires license_ | The SQL Data Collector provides information on database configuration, permissions, data extraction, application name of the application responsible for activity events, an IP Address or Host name of the client server, and sensitive data reports. This data collector also provides information on Oracle databases including infrastructure and operations. | TCP | For Db2 Target:
  • Specified by Instances table (default is 5000)
For MySQL Target:
  • Specified by Instances table (default is 3306)
For Oracle Target:
  • Specified by Instances table (default is 1521)
For PostgreSQL Target:
  • Specified by Instances table (default is 5432)
For SQL Target:
  • Specified by Instances table (default is 1433)
| **For MySQL Target:**
  • Read access to MySQL instance to include all databases contained within each instance
  • Windows Only — Domain Admin or Local Admin privilege
**For Oracle Target:**
  • User with SYSDBA role
  • Local Administrator on the target servers – Only applies to Windows Servers and not on Linux or Unix operating systems
**For PostgreSQL Target:**
  • Read access to all the databases in PostgreSQL cluster or instance
  • Windows Only — Domain Admin or Local Admin privilege
**For Redshift Target:**
  • Read-access to the following tables:
  • pg_tables
  • pg_user
**For SQL Target:**
For Instance Discovery, local rights on the target SQL Servers:
  • Local group membership to Remote Management Users
  • Permissions on the following WMI NameSpaces: `root\Microsoft\SQLServer, root\interop`
For permissions for data collection:
  • Read access to SQL instance
  • Requires SQL Full-Text and Semantic Extractions for Search feature to be installed on the target SQL instances when using the **Scan full rows for sensitive data** option on the Options wizard page
  • Grant Authenticate Server to [DOMAIN\USER]
  • Grant Connect SQL to [DOMAIN\USER]
  • Grant View any database to [DOMAIN\USER]
  • Grant View any definition to [DOMAIN\USER]
  • Grant View server state to [DOMAIN\USER]
  • Grant Control Server to [DOMAIN\USER] (specifically required for the Weak Passwords Job)
| | SystemInfo | The SystemInfo Data Collector extracts information from the target system based on the selected category. |
  • Remote Registry
  • RPC
  • WMI
|
  • TCP 135-139
  • Randomly allocated high TCP ports
|
  • Member of the Local Administrators group
| | TextSearch | The TextSearch Data Collector enables searches through text based log files. |
  • RPC
|
  • TCP 135-139
  • Randomly allocated high TCP ports
|
  • Member of the Local Administrators group
| | Unix _\*requires license_ | The Unix Data collector provides host inventory, software inventory, and logical volume inventory on UNIX & Linux platforms. |
  • SSH
|
  • TCP 22
  • User configurable
|
  • Root permissions in Unix/Linux
| diff --git a/docs/accessanalyzer/12.0/admin/datacollector/powershell/editquery.md b/docs/accessanalyzer/12.0/admin/datacollector/powershell/editquery.md index 67d932ee21..e13dbcebee 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/powershell/editquery.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/powershell/editquery.md @@ -15,10 +15,10 @@ The options on the Edit Query page are: - Open – Click to import and open a PowerShell script - Script Editor – Input PowerShell script to use for the configured job -- Parameters – The Parameters tab located on the right-hand side of the Edit Query page is used to - bring up the Parameters window. See the [Parameters](#parameters) topic for additional +- Parameters – Use the Parameters tab, located on the right-hand side of the Edit Query page, to + open the Parameters window. See the [Parameters](#parameters) topic for additional information. -- Use table input for PowerShell script – select the checkbox to bring up the Input options for the +- Use table input for PowerShell script – select the checkbox to display the Input options for the PowerShell script. See the [Input Options](#input-options) topic for additional information. ## Parameters @@ -36,8 +36,8 @@ The options in the Parameters Window are: - Delete – Delete a parameter :::note -Only user created parameters can be edited or deleted. Pre-configured parameters cannot be -edited or deleted. +You can edit or delete only user-created parameters. You can't edit or delete preconfigured +parameters. ::: @@ -64,22 +64,22 @@ The options in the Add/Edit Variable window are: ## Input Options -When the Use table input for PowerShell script option is selected on the Edit Query page, additional +When you select the Use table input for PowerShell script option on the Edit Query page, additional options display to define the source for input data. ![Edit Query page input options](/images/accessanalyzer/12.0/admin/datacollector/powershell/editqueryinput.webp) The input options are: -- Please select name – Select the input table to be used from the drop-down menu +- select name – Select the input table to use from the dropdown menu - Filter nulls – Excludes values that are null from input - Filter duplicates – Excludes any values that are duplicate from input -- Text Box – Displays an example of how the input can be used in a PowerShell script +- Text Box – Displays an example of how to use the input in a PowerShell script - Columns – Displays the columns in the selected input table. If applicable, select the checkbox to include the column in the input. - Input Data – Preview how the input data will look in the Input Data tab ![Text Box and the Columns tab populated with information](/images/accessanalyzer/12.0/admin/datacollector/powershell/editqueryinputtable.webp) -Selecting an input table in the **Please select name** dropdown populates the Text Box and the +Selecting an input table in the **select name** dropdown populates the Text Box and the Columns tab with information. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/powershell/options.md b/docs/accessanalyzer/12.0/admin/datacollector/powershell/options.md index fc07764cbe..26f662804d 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/powershell/options.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/powershell/options.md @@ -12,11 +12,11 @@ The Options page provides the option to execute the script remotely on the targe The configurable options are: -- Execute remotely – Remotely executes the script on the target host. If this checkbox is not - selected, the script will be executed from the Access Analyzer Console server. +- Execute remotely – Remotely executes the script on the target host. If you don't select this + checkbox, Access Analyzer executes the script from the Access Analyzer Console server. - Use impersonation within server executable – Executes the script with the job credentials -For cmdlets requiring explicit credentials, a single credential set from the job's Connection -Profile can be referenced using `Get-Credential` or the `$JobCredential` variable, a `PSCredential` -type object. All credentials from the job’s Connection Profile may be accessed via the +For cmdlets that require explicit credentials, you can reference a single credential set from the +job's Connection Profile using `Get-Credential` or the `$JobCredential` variable, a `PSCredential` +type object. You can access all credentials from the job's Connection Profile via the `$JobCredentials` array. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/powershell/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/powershell/overview.md index d90b57b9be..cd8f3d10c6 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/powershell/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/powershell/overview.md @@ -25,7 +25,7 @@ component of Access Analyzer and is available with all Access Analyzer licenses. ## PowerShell Query Configuration -The PowerShell Data Collector is configured through the PowerShell Data Collector Wizard, which +Configure the PowerShell Data Collector through the PowerShell Data Collector Wizard, which contains the following pages: - Welcome @@ -37,5 +37,5 @@ contains the following pages: ![PowerShell Data Collector Wizard Welcome page](/images/accessanalyzer/12.0/admin/datacollector/powershell/welcome.webp) -The Welcome page can be hidden by checking the **Do not display this page the next time** box when -the wizard is open and configuration settings are saved. +You can hide the Welcome page by checking the **Don't display this page the next time** box while +the wizard is open and saving configuration settings. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/powershell/results.md b/docs/accessanalyzer/12.0/admin/datacollector/powershell/results.md index 473a23b5d9..3744a66d6f 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/powershell/results.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/powershell/results.md @@ -13,5 +13,5 @@ components. The Results page options are: -- Properties to return – List of available properties which can be gathered for the PowerShell query -- ROWKEY's components – List of available properties based on which ROWKEY will be built +- Properties to return – List of available properties to gather for the PowerShell query +- ROWKEY's components – List of available properties that Access Analyzer uses to build ROWKEY diff --git a/docs/accessanalyzer/12.0/admin/datacollector/powershell/sampleserver.md b/docs/accessanalyzer/12.0/admin/datacollector/powershell/sampleserver.md index cedd069bd9..9c7948eb33 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/powershell/sampleserver.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/powershell/sampleserver.md @@ -12,11 +12,11 @@ The Sample Server page provides a box to select a server to generate the result The Select Server page options are: -- Server name – Server to be used during configuration -- Validate – Validates the script results and retrieves result columns. Validation must be run in - order to populate and enable the Results page. +- Server name – Server to use during configuration +- Validate – Validates the script results and retrieves result columns. Run validation to populate + and enable the Results page. The server selected here replaces any `[SAHOSTNAME]` tokens in the PowerShell script. During -execution, the `[SAHOSTNAME]` tokens are replaced in turn by each host in the host list. If no +execution, each host in the host list replaces the `[SAHOSTNAME]` tokens in turn. If no `[SAHOSTHAME]` tokens exist in the PowerShell script, then the server name and the hosts in the host list have no effect. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/powershell/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/powershell/summary.md index 7686a3a503..84fc78b70a 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/powershell/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/powershell/summary.md @@ -11,6 +11,5 @@ Data Collector Wizard. ![PowerShell Data Collector Wizard Summary page](/images/accessanalyzer/12.0/admin/datacollector/powershell/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the PowerShell Data Collector Wizard ensuring that no accidental clicks -are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** instead to +close the PowerShell Data Collector Wizard without saving accidental clicks. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/registry.md b/docs/accessanalyzer/12.0/admin/datacollector/registry.md index 416e1e2359..d2965e741c 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/registry.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/registry.md @@ -8,12 +8,12 @@ sidebar_position: 310 The Registry Data Collector queries the registry and returns keys, key values, and permissions on the keys. The data in the native tables returned by the Registry Data Collector is dependent upon -the query configuration. For example, a query could be configured to only show permissions on -registry keys in a 32-bit view. Another query could be configured to show a listing of all keys and -key values in a 64-bit view. Wildcards can also be used in query configurations. +the query configuration. For example, you can configure a query to show permissions only on +registry keys in a 32-bit view. You can configure another query to show a listing of all keys and +key values in a 64-bit view. You can also use wildcards in query configurations. -The Registry Data Collector is a core component of Access Analyzer, but it has been preconfigured -within both the Active Directory Solution and the Windows Solution. While the data collector is +The Registry Data Collector is a core component of Access Analyzer, but Access Analyzer +preconfigures it within both the Active Directory Solution and the Windows Solution. While the data collector is available with all Access Analyzer license options, these solutions are only available with a special Access Analyzer licenses. See the following topics for additional information: @@ -36,23 +36,22 @@ special Access Analyzer licenses. See the following topics for additional inform ## Registry Query Configuration -The Registry Data Collector is configured through the Registry Browser window. +Configure the Registry Data Collector through the Registry Browser window. ![Registry Browser window](/images/accessanalyzer/12.0/admin/datacollector/browser.webp) The configurable options are: -- Sample Host – The host to connect to. If this box is left blank, the connection is to the local +- Sample Host – The host to connect to. If you leave this box blank, the connection is to the local host. - 64-bit view – The default view is 32-bit. Select the **64-bit view** checkbox to switch to a 64-bit view. -- Connect – Connect to host’s registry. If no host is specified in the Sample Host box, the +- Connect – Connect to host’s registry. If you don't specify a host in the Sample Host box, the connection is to the local host’s registry. - Query 32-bit view – Select this checkbox to query the 32-bit view of the registry - Query 64-bit view – Select this checkbox to query the 64-bit view of the registry -- Name – The key value. Key values can be added to the Selected Properties list by pressing the - **ctrl** key, selecting the keys to add, and then clicking the **Add currently selected value** - button. +- Name – The key value. To add key values to the Selected Properties list, press the **ctrl** key, + select the keys to add, and click the **Add selected value** button. - Type – The key value type - Data – The key value path - Root Path – The path to the selected key @@ -71,11 +70,11 @@ to do the following: | Icon | Name | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------- | | ![Select all peer keys for this node](/images/accessanalyzer/12.0/admin/datacollector/selectall.webp) | Select all peer keys for this node | -| ![Add name of currently selected key](/images/accessanalyzer/12.0/admin/datacollector/addname.webp) | Add name of currently selected key | -| ![Add full path of the currently selected key](/images/accessanalyzer/12.0/admin/datacollector/addpath.webp) | Add full path of the currently selected key | -| ![Add last write date/time of currently selected key](/images/accessanalyzer/12.0/admin/datacollector/adddatetime.webp) | Add last write date/time of currently selected key | +| ![Add name of selected key](/images/accessanalyzer/12.0/admin/datacollector/addname.webp) | Add name of selected key | +| ![Add full path of the selected key](/images/accessanalyzer/12.0/admin/datacollector/addpath.webp) | Add full path of the selected key | +| ![Add last write date/time of selected key](/images/accessanalyzer/12.0/admin/datacollector/adddatetime.webp) | Add last write date/time of selected key | | ![Add security properties for selected key](/images/accessanalyzer/12.0/admin/datacollector/addproperties.webp) | Add security properties for selected key | | ![Enumerate all values for this key](/images/accessanalyzer/12.0/admin/datacollector/enumeratevalues.webp) | Enumerate all values for this key | -| ![Add currently selected value](/images/accessanalyzer/12.0/admin/datacollector/addvalue.webp) | Add currently selected value | +| ![Add selected value](/images/accessanalyzer/12.0/admin/datacollector/addvalue.webp) | Add selected value | | ![Delete properties from selection](/images/accessanalyzer/12.0/admin/datacollector/delete.webp) | Delete properties from selection | | ![Go to selected key](/images/accessanalyzer/12.0/admin/datacollector/goto.webp) | Go to selected key | diff --git a/docs/accessanalyzer/12.0/admin/datacollector/script/add.md b/docs/accessanalyzer/12.0/admin/datacollector/script/add.md index 7307e07660..2f2fc386ff 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/script/add.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/script/add.md @@ -6,17 +6,17 @@ sidebar_position: 20 # Add a Script to an Existing Query -The Query Properties window provides the ability to add a script to an existing query. Typically, a -script is used to augment a query providing services such as conversion of returned data. +The Query Properties window lets you add a script to an existing query. Typically, you use a +script to augment a query, providing services such as converting returned data. -Follow the steps to add a script. +To add a script: **Step 1 –** Navigate to the job's **Configure** node and select **Queries**. **Step 2 –** Click **Create Query** to open the Query Properties window. -**Step 3 –** Select the **Data Source** tab and select the desired data collector in the Data -Collector drop-down menu. +**Step 3 –** Select the **Data Source** tab and select the data collector you want in the Data +Collector dropdown menu. ![Query Properties window](/images/accessanalyzer/12.0/admin/datacollector/script/querypropertiesexisting.webp) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/script/editor.md b/docs/accessanalyzer/12.0/admin/datacollector/script/editor.md index da9ee8b3d8..6968b73531 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/script/editor.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/script/editor.md @@ -6,7 +6,7 @@ sidebar_position: 30 # VBScript Editor -The VBScript Editor window provides the means to add a script. The window is ideal for editing small +The VBScript Editor window lets you add a script. The window is ideal for editing small scripts and for pasting larger scripts from external scripting tools. ![VBScript Editor window](/images/accessanalyzer/12.0/admin/datacollector/script/vbscripteditor.webp) @@ -14,10 +14,10 @@ scripts and for pasting larger scripts from external scripting tools. The options in the VBScript Editor are: - Save and Close – Use this option to save the script and close the window -- Syntax Check – Use this option to check the syntax of your script. This does not identify logic +- Syntax Check – Use this option to check the syntax of your script. This doesn't identify logic errors, only cases where the script syntax is incorrect. It helps reduce the overhead of debugging - a script. When selected, a Script Errors window opens and a syntax check is performed. Any - syntactical errors are displayed within the window. + a script. When you select this option, a Script Errors window opens and performs a syntax check, + displaying any syntax errors within the window. - Load from file – Use this option to load a VB script from a .vbs file - Save to file – Use this option to save the current script in the Editor - Undo – Undo previous changes made to the script (Shortcut is Ctrl+Z) @@ -25,8 +25,8 @@ The options in the VBScript Editor are: - Cut – Cut the highlighted text - Copy – Copy the highlighted text - Paste – Paste cut or copied text into the VB Script Editor -- Online VBScript Language Reference – Opens internet browser to the Microsoft Technical - Documentation website from where documentation for Visual Basic Script can be navigated to +- Online VBScript Language Reference – Opens a web browser to the Microsoft Technical + Documentation website, where you can find documentation for Visual Basic Script After adding or modifying a script, click **Save and close**. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/script/example1.md b/docs/accessanalyzer/12.0/admin/datacollector/script/example1.md index ce0a66a03e..60f019a663 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/script/example1.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/script/example1.md @@ -7,26 +7,26 @@ sidebar_position: 70 # Script Example 1: Conversion of Data This script example demonstrates how to perform a query and modify returned data. The script -provides the data collector with the information that would have been provided if the user interface -had been used to design the query. However, in this case it is all done through script. The data -collector returns a value that is then converted and stored by Access Analyzer. +provides the data collector with the same information you would provide by using the user +interface to design the query. However, in this case, the script does all of this instead. The +data collector returns a value that Access Analyzer then converts and stores. -This script starts by defining a query using the Perfmon Data Collector. Notice that the -**WorkingQuery** object is used, not the Query object. This is done to preserve the Query object, -since the Query object will be used to store the results that are different from what the data -collector is providing. +This script starts by defining a query using the Perfmon Data Collector. Notice that the script +uses the **WorkingQuery** object, not the Query object. The script preserves the Query object this +way, because it later uses the Query object to store results that differ from what the data +collector provides. -The script then issues the query by calling `WorkingQuery.Execute`. When the query completes, -**WorkingQuery** is set to view the first row of results by setting the **ResultRow** property. The -value within the **System Up Time** property is then transferred into the `REMAINDER` variable so -that it can be more easily manipulated. +The script then issues the query by calling `WorkingQuery.Execute`. When the query completes, the +script sets **WorkingQuery** to view the first row of results by setting the **ResultRow** +property. The script then transfers the value within the **System Up Time** property into the +`REMAINDER` variable for easier manipulation. The script then takes the value of `REMAINDER`, which is in seconds, and converts it to days, hours, -minutes, and seconds. These values are then recorded in the Query object so that Access Analyzer can -store this data. +minutes, and seconds. The script then records these values in the Query object so that Access +Analyzer can store this data. :::note -In this task, the hours, minutes, and seconds properties were specified manually using the +In this task, you specified the hours, minutes, and seconds properties manually using the task dialog. See the [Script Properties](/docs/accessanalyzer/12.0/admin/datacollector/script/properties.md) topic for additional information. ::: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/script/example2.md b/docs/accessanalyzer/12.0/admin/datacollector/script/example2.md index aa4ec0cc63..245afe1854 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/script/example2.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/script/example2.md @@ -11,25 +11,26 @@ database list from SQL Server and then proceeds to the File System Data Collecto the database file, essentially inventorying the installed databases, their paths, and sizes. :::note -Because the object instances are not thread-safe, scripts like these that use objects -external to Access Analyzer should be run with only one thread. +Because the object instances aren't thread-safe, run scripts like these that use objects +external to Access Analyzer with only a single thread. ::: -In this example, a connection is opened with a SQL server. The SQL server name is provided by Access -Analyzer during the query. Access Analyzer provides the active host to the script using the +In this example, the script opens a connection with a SQL server. Access Analyzer provides the SQL +server name during the query. Access Analyzer provides the active host to the script using the **Query.Host** property. The script then queries the Master database, requesting a **recordset** containing all databases and -proceeds to get the row count. Setting the **Query.ResultRows** property creates a row of storage -for each record in the recordset. It then proceeds to read data from each row by looping row by row. -For each row, the database name, filename, and ID are captured. The script then calls a function to -get the size of the file. The **FileSize** function uses the database filename to construct a query -to the File System Data Collector, which ultimately returns the size of the file. +gets the row count. Setting the **Query.ResultRows** property creates a row of storage +for each record in the recordset. It then reads data from each row, looping row by row. +For each row, the script captures the database name, filename, and ID. The script then calls a +function to get the size of the file. The **FileSize** function uses the database filename to +construct a query to the File System Data Collector, which ultimately returns the size of the +file. -The data for each database is stored in the Query object. +The script stores the data for each database in the Query object. -Finally, the SQL objects are freed. +Finally, the script frees the SQL objects. ## Example of Compound Query Script diff --git a/docs/accessanalyzer/12.0/admin/datacollector/script/methodsproperties.md b/docs/accessanalyzer/12.0/admin/datacollector/script/methodsproperties.md index 72509af3da..776e87170b 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/script/methodsproperties.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/script/methodsproperties.md @@ -13,7 +13,7 @@ The Query and Working Query objects support the following methods and properties | Methods | Description | | -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Execute | Executes the object query. Use this to perform the query after setting the source, path, and properties. | -| Reset | Resets the object’s properties to their original values. Use this if the source, path, or properties have been modified, but the original values are desired. | +| Reset | Resets the object’s properties to their original values. Use this if you modified the source, path, or properties, but want the original values. | | AddProperty (attributes : string) | Adds a property to the query. Using the following format: NAME=``;COLUMN=``;VALUE=``;DATATYPE=``;SIZE=``;KEY=`` | | DeleteProperty (propertyname : string) | Removes a property from a query. | @@ -26,7 +26,7 @@ The Query and Working Query objects support the following methods and properties | Path : sting | Sets or retrieves the path | | Paths : integer | Sets or retrieves the current path for multi-path tasks | | ResultData (Property : string) : Variant | Sets or retrieves the value for the property specified | -| ResultData (PropertyIndex : integer) : Variant | Sets ResultRow to the desired row before accessing this property | +| ResultData (PropertyIndex : integer) : Variant | Sets ResultRow to the row you want before accessing this property | | ResultRow : integer | Sets or retrieves the current row. For non-enumerated tasks, ResultRow will always be 0. | -| ResultRows : integer | Sets or returns the count of rows. Use this to determine the number of rows returned after an enumerated task is executed. Set this property to create a multi-row return value. | +| ResultRows : integer | Sets or returns the count of rows. Use this to determine the number of rows returned after an enumerated task runs. Set this property to create a multi-row return value. | | Message (index : integer, type : string) | Sets or returns a message in the indicated position. Use MessageCount to determine the number of messages. These messages appear in the job MessageLog. | diff --git a/docs/accessanalyzer/12.0/admin/datacollector/script/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/script/overview.md index 3ab6edc2b1..27cbc8932e 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/script/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/script/overview.md @@ -7,22 +7,22 @@ sidebar_position: 320 # Script Data Collector The Script Data Collector provides VB Script exit from Access Analyzer. Static queries are sometimes -inadequate for demanding auditing tasks. The Script Data Collector provides a means to add a custom +inadequate for demanding auditing tasks. The Script Data Collector lets you add a custom script to a query. Access Analyzer implements Microsoft Visual Basic Script (VB Script) with -extensions that provide script writers the ability to interface directly with Access Analyzer. +extensions that let script writers interface directly with Access Analyzer. The following examples describe situations where using a script may be useful: - Conversions – One of the most frequent uses of a scriptis for converting a value from one thing to another, for example `build1230` to `at risk`. See the [Script Example 1: Conversion of Data](/docs/accessanalyzer/12.0/admin/datacollector/script/example1.md) topic for additional information. -- Compound Queries – This is a query that cannot be performed using a single query. See the +- Compound Queries – A query you can't perform using a single query. See the [Script Example 2: Command Query](/docs/accessanalyzer/12.0/admin/datacollector/script/example2.md) topic for additional information. - Interfacing with External Systems – This is a query that requires access to external data. For example, the query needs to access a corporate database to obtain a location code. -The Script Data Collector is a core component of Access Analyzer, but it has been preconfigured -within the Windows Solution. While the data collector is available with all Access Analyzer license +The Script Data Collector is a core component of Access Analyzer, but Access Analyzer +preconfigures it within the Windows Solution. While the data collector is available with all Access Analyzer license options, the Windows Solution is only available with a special Access Analyzer license. See the [Windows Solution](/docs/accessanalyzer/12.0/solutions/windows/overview.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/script/properties.md b/docs/accessanalyzer/12.0/admin/datacollector/script/properties.md index 3afff6df1a..c61dfa267c 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/script/properties.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/script/properties.md @@ -6,31 +6,31 @@ sidebar_position: 60 # Script Properties -The Data Source tab is used to select the data collector to be used. The configurable options are: +Use the Data Source tab to select the data collector. The configurable options are: - Source – Used to select data collector - Path – Displays the returned path from the data collector :::warning - Editing the path is considered an advanced operation. Entering an incorrect value + Editing the path is an advanced operation. Entering an incorrect value may render the query inoperable. ::: - - The path is used to identify the selection from within the data collector. The path + - The path identifies the selection from within the data collector. The path essentially tells the data collector where the data is and depending on the data collector, may define selected options. It is sometimes convenient to edit the path manually. - - For example: If defining a file system query using the File System Data Collector, the path - would automatically be filled in with the selected details. A minor change like changing the - file location can be done manually by editing the path. + - For example, if you define a file system query using the File System Data Collector, the + data collector automatically fills in the path with the selected details. You can manually + make minor changes, like changing the file location, by editing the path. -- Properties – As the Path is used to define where the target data is, the properties are used to - define what data is desired. Each property has a series of attributes including: +- Properties – As the Path defines where the target data is, the properties define what data you + want. Each property has a series of attributes including: - Name – Identifies the target data. Modifying this affects what data the data collector returns. - Column – Specifies the column name within the result data. Use this to specify the column name - that will be used within the report output. This is set by default to match the **Name** + for the report output. Access Analyzer sets this by default to match the **Name** attribute. - DataType – Used to determine the format of the data for reporting purposes. It affects sorting order and the ability to graph content. In some cases, the data collector is unable to @@ -43,24 +43,24 @@ The Data Source tab is used to select the data collector to be used. The configu - For example: Querying the registry for a value stored as **REG_SZ** returns a string, as - **REG_SZ** is a string type in the registry. However, sometimes numbers are recorded in - **REG_SZ** entries. If you determine that the content returned could always be interpreted as - numeric, you could override the default `STRING` value and set it to `NUMERIC`. This provides + **REG_SZ** is a string type in the registry. However, sometimes **REG_SZ** entries contain + numbers. If you determine that the returned content is always numeric, you can override the + default `STRING` value and set it to `NUMERIC`. This provides proper sorting and charting ability. - Size – Used to determine the width of the field used to hold String data. Setting the size smaller than the actual returned data will cause Access Analyzer to truncate the data in the view. However, the actual stored data in the result table will contain the full result. - Value – Reserved for internal use -- Key – Used to identify a key property. A key property is used to identify the property that - contains a unique value for enumerated tasks. A Key value is required for Change Detection and - Conformance Management on enumerated tasks. To identify a property that uniquely identifies each +- Key – Used to identify a key property. A key property identifies the property that + contains a unique value for enumerated tasks. Change Detection and Conformance Management on + enumerated tasks require a Key value. To identify a property that uniquely identifies each row, set the Key attribute to `YES`. ## Adding and Removing Properties Manually -Although the property list is automatically populated by the data collectors, additional properties -may be added manually. Doing so allocates storage within Access Analyzer during data collection and +Although the data collectors automatically populate the property list, you can add additional +properties manually. Doing so allocates storage within Access Analyzer during data collection and creates corresponding columns in the output table. Use a script to reference and populate these properties. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/script/reference.md b/docs/accessanalyzer/12.0/admin/datacollector/script/reference.md index 730b1062d7..3907ca3057 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/script/reference.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/script/reference.md @@ -6,21 +6,21 @@ sidebar_position: 50 # Script Reference -Access Analyzer provides extensions to standard Visual Basic Script. These extensions allow access -to and manipulation of task data, in addition to invoking queries. They are implemented through two -objects. +Access Analyzer provides extensions to standard Visual Basic Script. These extensions let you +access and manipulate task data, in addition to invoking queries. Access Analyzer implements them +through two objects. **Query Object** The Query object provides access to the current query configuration and data. Use this to examine -the results of a query or to manipulate the query before it is executed. Changing properties of this -object will change the way the task is executed by Access Analyzer. +the results of a query or to manipulate the query before Access Analyzer executes it. Changing +properties of this object changes the way Access Analyzer executes the task. **Working Query Object** The Working Query object is identical to the Query object. This object supports the same methods and -properties as the Query object but its properties and methods do not access the current query. Think -of this object as allowing the ability to create a task on the fly. Use this object to perform -queries, while leaving the original task undisturbed. This is valuable when performing compound -queries isneeded. See the [Script Example 2: Command Query](/docs/accessanalyzer/12.0/admin/datacollector/script/example2.md) topic for additional +properties as the Query object but its properties and methods don't access the current query. Think +of this object as letting you create a task dynamically at runtime. Use this object to perform +queries, while leaving the original task undisturbed. This is valuable when you need to perform +compound queries. See the [Script Example 2: Command Query](/docs/accessanalyzer/12.0/admin/datacollector/script/example2.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/script/run.md b/docs/accessanalyzer/12.0/admin/datacollector/script/run.md index 473121d8a0..1ed45cbeb3 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/script/run.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/script/run.md @@ -6,16 +6,16 @@ sidebar_position: 10 # Run a Stand-Alone Script -Some situations require a script to be used exclusively without defining a data source. The Query -Properties window provides the ability to add and run a script. +Some situations require you to use a script exclusively without defining a data source. The Query +Properties window lets you add and run a script. -Follow the steps to add a script. +To add a script: **Step 1 –** Go to the job's **Configure** node and select **Queries**. **Step 2 –** Click **Create Query** to open the Query Properties window. -**Step 3 –** Select the **Data Source** tab, and select **SCRIPT** in the Data Collector drop-down +**Step 3 –** Select the **Data Source** tab, and select **SCRIPT** in the Data Collector dropdown menu. ![Query Properties window](/images/accessanalyzer/12.0/admin/datacollector/script/querypropertiesstandalone.webp) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/services.md b/docs/accessanalyzer/12.0/admin/datacollector/services.md index 484851de5a..b00fc9fca0 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/services.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/services.md @@ -7,8 +7,8 @@ sidebar_position: 330 # Services Data Collector The Services Data Collector enumerates status and settings from remote services. The Services Data -Collector is a core component of Access Analyzer, but it has been preconfigured within the Windows -Solution. While the data collector is available with all Access Analyzer license options, the +Collector is a core component of Access Analyzer, but Access Analyzer preconfigures it within the +Windows Solution. While the data collector is available with all Access Analyzer license options, the Windows Solution is only available with a special Access Analyzer license. See the [Windows Solution](/docs/accessanalyzer/12.0/solutions/windows/overview.md) topic for additional information. @@ -28,7 +28,7 @@ Windows Solution is only available with a special Access Analyzer license. See t ## Services Query Configuration -The Services Data Collector is configured through the Service Browser window. +Configure the Services Data Collector through the Service Browser window. ![Service Browser window](/images/accessanalyzer/12.0/admin/datacollector/servicebrowser.webp) @@ -36,14 +36,15 @@ The Services Data Collector is configured through the Service Browser window. - All Services – Select this option to build the query to extract information from all services on the target host - Specific Services – Select this option to build the query to extract information from specific - services on the target host. Select the checkboxes next to the desired services for the query + services on the target host. Select the checkboxes next to the services you want for the query after clicking **Connect**. - Connect – Click **Connect** to connect to the host and display a list of all services found -- Available Properties – Select the properties to be returned +- Available Properties – Select the properties to return :::note -In cases where the query does not find the selected services on the target host, the -`InternalName` column that is returned reflects the `DisplayName` column and no other values are -retrieved. If the services are found on the host, the `DisplayName` value in the table is resolved. +In cases where the query doesn't find the selected services on the target host, the +returned `InternalName` column reflects the `DisplayName` column, and the query retrieves no other +values. If the query finds the services on the host, it resolves the `DisplayName` value in the +table. ::: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/smartlog/collectionmethod.md b/docs/accessanalyzer/12.0/admin/datacollector/smartlog/collectionmethod.md index e2f7f09b89..534f4a5a60 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/smartlog/collectionmethod.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/smartlog/collectionmethod.md @@ -6,13 +6,13 @@ sidebar_position: 60 # SMARTLog: Collection Method -The Collection Method page is used to select the collection method employed by the data collector. -It is a wizard page for all log types. +Use the Collection Method page to select the collection method the data collector uses. This +wizard page applies to all log types. ![SMART Log DC Wizard Collection Method page](/images/accessanalyzer/12.0/admin/datacollector/smartlog/collectionmethod.webp) -Select the collection method from the following options to set how the collection routine is -executed to collect the data from the target. +Select the collection method from the following options to set how the collection routine collects +data from the target. - Using network query – Connects to the target log over the network via RPC and reads events - Using server side applet – Deploys a remote executable to the target host and then runs as a @@ -20,17 +20,17 @@ executed to collect the data from the target. Access Analyzer Console. :::note - The applet cannot be used to target the local host. + You can't use the applet to target the local host. ::: - Copy the log locally and process (Not available for all query scenarios) – Extract events from an - offline log by moving the log to the Access Analyzer Console and having it processed on the local - host instead of the target host. In order to use this option, the log type selected for the query + offline log by moving the log to the Access Analyzer Console and processing it on the local + host instead of the target host. To use this option, the log type selected for the query must be **Windows Event Log (Archived)**. -The Applet Options section is only visible when the **Using server side applet** collection method -is selected. +The Applet Options section is only visible when you select the **Using server side applet** +collection method. - Connection retries count – The number of times to retry a failed connection. The default is 15. - Retry delay (ms) – The time between retries of a failed connection. The default is 5000 diff --git a/docs/accessanalyzer/12.0/admin/datacollector/smartlog/criteria.md b/docs/accessanalyzer/12.0/admin/datacollector/smartlog/criteria.md index 39da93264d..34811f6ffb 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/smartlog/criteria.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/smartlog/criteria.md @@ -6,15 +6,15 @@ sidebar_position: 50 # SMARTLog: Criteria -The Criteria page is used to specify the search criteria. A test query can be run with the sample -host entered on the Sample Host page to confirm the results that will be returned by the query. It -is a wizard page for all log types. +Use the Criteria page to specify the search criteria. You can run a test query with the sample +host you entered on the Sample Host page to confirm the results the query will return. This +wizard page applies to all log types. ![SMART Log DC Wizard Criteria page](/images/accessanalyzer/12.0/admin/datacollector/smartlog/criteria.webp) The **Limit number of records to** setting has a default of `1000`. -Follow the steps to configure the search criteria. +To configure the search criteria: ![Filter button on Criteria page](/images/accessanalyzer/12.0/admin/datacollector/smartlog/criteriafilter.webp) @@ -36,12 +36,11 @@ that level. The available options are **AND**, **OR**, **NOT AND**, and **NOT O - To remove a row (condition or group), click the ellipsis (**…**) on the row and select **Remove Row** -- To remove all currently configured criteria, click **Filter** and select **Clear All** +- To remove all configured criteria, click **Filter** and select **Clear All** -**Step 6 –** Click **Show data** to run a test query and sample the data that will be returned that -is connected to a target log based upon the configured criteria. The data is displayed in the -Records found table. +**Step 6 –** Click **Show data** to run a test query and sample the data that the query returns +from the target log based on the configured criteria. The Records found table displays the data. -The search criteria has now been configured and the results it returns tested. Configure the -criteria further if the returned results are not as expected, or click **Next** to continue to the +You have now configured the search criteria and tested the results it returns. Configure the +criteria further if the returned results aren't as expected, or click **Next** to continue to the next wizard page. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/smartlog/eventlogoptions.md b/docs/accessanalyzer/12.0/admin/datacollector/smartlog/eventlogoptions.md index 9e9e54d4f5..b2d11969e0 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/smartlog/eventlogoptions.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/smartlog/eventlogoptions.md @@ -6,12 +6,12 @@ sidebar_position: 80 # SMARTLog: Event Log Options -The Event Log Options page is used to configure additional options. It is a wizard page for all log -types. +Use the Event Log Options page to configure additional options. This wizard page applies to all +log types. ![SMART Log DC Wizard Event Log Options page](/images/accessanalyzer/12.0/admin/datacollector/smartlog/eventlogoptions.webp) -The following additional options can be selected: +You can select the following additional options: - Lookup user name – Resolves SIDs found in the event descriptions to friendly display name values - Resolve GUIDs – Resolves GUIDs found in the event descriptions to friendly display name values diff --git a/docs/accessanalyzer/12.0/admin/datacollector/smartlog/logstate.md b/docs/accessanalyzer/12.0/admin/datacollector/smartlog/logstate.md index 36e1a5c091..9d00369c7f 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/smartlog/logstate.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/smartlog/logstate.md @@ -6,12 +6,12 @@ sidebar_position: 70 # SMARTLog: Log State -The Log State page is used to configure how to search the log. It is a wizard page for all log +Use the Log State page to configure how to search the log. It's a wizard page for all log types. ![SMART Log DC Wizard Log State page](/images/accessanalyzer/12.0/admin/datacollector/smartlog/logstate.webp) -Select the **Persist log state** checkbox to search the log from where the search last left off. A -state file is created for each host configured in the query. State files can be viewed within Access -Analyzer and are named by the query GUID. State files display the record the search last left off -on, the event log, and the date of the last entry. +Select the **Persist log state** checkbox to search the log from where the search last left off. +Access Analyzer creates a state file for each host configured in the query. You can view state +files, named by the query GUID, within Access Analyzer. State files display the record the search +last left off on, the event log, and the date of the last entry. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/smartlog/logtype.md b/docs/accessanalyzer/12.0/admin/datacollector/smartlog/logtype.md index 8da04a8a2e..b72864139e 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/smartlog/logtype.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/smartlog/logtype.md @@ -6,7 +6,7 @@ sidebar_position: 10 # SMARTLog: Log Type -The Log Type page is used to select the log type to be processed. +Use the Log Type page to select the log type to process. ![SMART Log DC Wizard Log Type page](/images/accessanalyzer/12.0/admin/datacollector/smartlog/logtype.webp) @@ -15,16 +15,16 @@ The log types are: - Windows Event Log – Connects to and extract information from any Windows event log made available on the target host - Windows Event Log (Archived) – Extract events from an offline log by moving the log to the Access - Analyzer Console and having it processed on the local host instead of the target host + Analyzer Console and processing it on the local host instead of the target host - Internet Information Server Log – An Exchange query that returns information from Outlook Web Access IIS logs found on CAS servers - - The IIS log must be configured to generate specific columns in order for the SMARTLog Data + - You must configure the IIS log to generate specific columns for the SMARTLog Data Collector to audit them. See the [IIS Log Auditing Requirements](#iis-log-auditing-requirements) topic for additional information. -- File Change Detection Log – This is a legacy option. It should not be selected. +- File Change Detection Log – This is a legacy option. Don't select it. ## IIS Log Auditing Requirements diff --git a/docs/accessanalyzer/12.0/admin/datacollector/smartlog/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/smartlog/overview.md index 52235e1601..ffbf797e7f 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/smartlog/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/smartlog/overview.md @@ -9,8 +9,8 @@ sidebar_position: 350 The SMARTLog Data Collector provides search and extraction of details from Windows Event Logs (online or offline) and Microsoft Exchange Internet Information Server (IIS) logs. -The SMARTLog Data Collector is a core component of Access Analyzer, but it has been preconfigured -within the Active Directory Solution, Exchange Solution, SQL Solution, and the Windows Solution. +The SMARTLog Data Collector is a core component of Access Analyzer, but the Active Directory +Solution, Exchange Solution, SQL Solution, and Windows Solution preconfigure it. While the data collector is available with all Access Analyzer license options, these solutions are only available with a special Access Analyzer licenses. See following sections for additional information: @@ -43,7 +43,7 @@ topic for additional information related to permissions required for targeting E ## SMARTLog Query Configuration -The SMARTLog Data Collector is configured through the SMART Log DC Wizard, which contains the +You configure the SMARTLog Data Collector through the SMART Log DC Wizard, which contains the following wizard pages: - Welcome diff --git a/docs/accessanalyzer/12.0/admin/datacollector/smartlog/results.md b/docs/accessanalyzer/12.0/admin/datacollector/smartlog/results.md index cb0d24107d..c73e85eccc 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/smartlog/results.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/smartlog/results.md @@ -6,8 +6,8 @@ sidebar_position: 40 # SMARTLog: Results -The Results page is where the events to be returned by the query are selected. It is a wizard page -for all log types. The description strings within the log records can also be selected for the +Use the Results page to select the events that the query returns. It's a wizard page +for all log types. You can also select the description strings within the log records for the query. ![SMART Log DC Wizard Results page](/images/accessanalyzer/12.0/admin/datacollector/smartlog/results.webp) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/smartlog/samplehost.md b/docs/accessanalyzer/12.0/admin/datacollector/smartlog/samplehost.md index 9a9fa6cc22..ef44c61ae0 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/smartlog/samplehost.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/smartlog/samplehost.md @@ -6,7 +6,7 @@ sidebar_position: 20 # SMARTLog: Sample Host -The Sample Host page is used to configure the host. It is a wizard page for all log types. +Use the Sample Host page to configure the host. It's a wizard page for all log types. ![SMART Log DC Wizard Sample Host page](/images/accessanalyzer/12.0/admin/datacollector/smartlog/samplehost.webp) @@ -38,16 +38,16 @@ and select a computer. The options in the Select Computer window are: ![Advanced Select Computer window](/images/accessanalyzer/12.0/admin/datacollector/smartlog/selectcomputerwindowadvanced.webp) -The Common Queries section is included on the advanced Select Computer window in addition to object -type and location in the original Select Computer window. +The advanced Select Computer window includes the Common Queries section in addition to object +type and location from the original Select Computer window. -- Name – Select a qualifier from the drop-down menu and enter a name of an object in the associated +- Name – Select a qualifier from the dropdown menu and enter a name of an object in the associated text box -- Description – Select a qualifier from the drop-down menu and enter a description in the associated +- Description – Select a qualifier from the dropdown menu and enter a description in the associated text box - Select the **Disabled accounts** checkbox to include disabled accounts in the search - Select the **Non-expiring password** checkbox to include non-expiring passwords in the search -- Select the number of **Days since last logon** from the drop-down menu +- Select the number of **Days since last logon** from the dropdown menu - Click the **Columns** button to open the Choose Columns window ![Choose Columns window](/images/accessanalyzer/12.0/admin/datacollector/smartlog/choosecolumnswindow.webp) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/smartlog/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/smartlog/summary.md index fabf9bd49e..b27a82cabf 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/smartlog/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/smartlog/summary.md @@ -10,5 +10,5 @@ The Summary page displays a summary of the configured query. It is a wizard page ![SMART Log DC Wizard Summary page](/images/accessanalyzer/12.0/admin/datacollector/smartlog/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the SMART Log DC Wizard to ensure that no accidental clicks are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** instead to +close the SMART Log DC Wizard without saving accidental clicks. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/smartlog/targetlog/filedetectionlog.md b/docs/accessanalyzer/12.0/admin/datacollector/smartlog/targetlog/filedetectionlog.md index 625deb733c..47ac072a1e 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/smartlog/targetlog/filedetectionlog.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/smartlog/targetlog/filedetectionlog.md @@ -6,7 +6,7 @@ sidebar_position: 20 # SMARTLog: Target Log for File Detection Log Type -The Target Log page is where logs are selected to be collected. This version is a wizard page for +Use the Target Log page to select logs to collect. This version is a wizard page for the File Change Detection log type. ![SMART Log DC Wizard Target Log page for File Change Detection Log](/images/accessanalyzer/12.0/admin/datacollector/smartlog/targetlogtype/targetlogfiledetection.webp) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/smartlog/targetlog/targetlog.md b/docs/accessanalyzer/12.0/admin/datacollector/smartlog/targetlog/targetlog.md index 74d723f8d6..680cbec1fb 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/smartlog/targetlog/targetlog.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/smartlog/targetlog/targetlog.md @@ -6,7 +6,7 @@ sidebar_position: 30 # SMARTLog: Target Log -The Target Log page is where logs are selected to be collected. There are three versions of this +Use the Target Log page to select logs to collect. There are three versions of this wizard page that change based on log type. This version is a wizard page for the log types of: - Windows Event Log (Archived) @@ -21,9 +21,9 @@ information on the other versions of this wizard page. The configurable options are: - Path – Enter or browse to the path to the log -- File mask – Enter file names to limit the file names to return from the path entered. Asterisks - can be used for wildcards. For example, `u_ex*.log` would match **u_ex170530.log**. When no mask - is set, all files from the listed path are returned. +- File mask – Enter file names to limit the file names to return from the path entered. Use asterisks + for wildcards. For example, `u_ex*.log` would match **u_ex170530.log**. If you don't set + a mask, Access Analyzer returns all files from the listed path. - Log files to be processed – Select from the following options: - All diff --git a/docs/accessanalyzer/12.0/admin/datacollector/smartlog/targetlog/windowseventlog.md b/docs/accessanalyzer/12.0/admin/datacollector/smartlog/targetlog/windowseventlog.md index 8f22e62c05..ac719082c7 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/smartlog/targetlog/windowseventlog.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/smartlog/targetlog/windowseventlog.md @@ -6,10 +6,10 @@ sidebar_position: 10 # SMARTLog: Target Log for Windows Event Log Type -The Target Log page is where logs are selected to be collected. This version is a wizard page for +Use the Target Log page to select logs to collect. This version is a wizard page for the log type of Windows Event Log. ![SMART Log DC Wizard Target Log page for Windows Event Log](/images/accessanalyzer/12.0/admin/datacollector/smartlog/targetlogtype/targetlogwindowsevent.webp) -Only one log can be targeted per query task. The selected log is displayed at the bottom of the -wizard page. +You can target only one log per query task. Access Analyzer displays the selected log at the +bottom of the wizard page. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/spaa/activitydatescope.md b/docs/accessanalyzer/12.0/admin/datacollector/spaa/activitydatescope.md index d08aa3550b..5165450144 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/spaa/activitydatescope.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/spaa/activitydatescope.md @@ -6,17 +6,17 @@ sidebar_position: 110 # SPAA: Activity Date Scope -The Activity Date Scope page is where the range of dates for which the SharePoint activity scan will -collect data is configured. It is a wizard page for the category of Scan SharePoint Activity. +Use the Activity Date Scope page to configure the range of dates for which the SharePoint activity +scan collects data. It's a wizard page for the category of Scan SharePoint Activity. ![Activity Date Scope page](/images/accessanalyzer/12.0/admin/datacollector/spaa/activitydatescope.webp) Use the radio buttons to select the **Scan Filters**. - Relative Timespan - - Collect Activity from the last 180 days – The number of days to collect activity can be - configured with the up and down arrows - - Retain data – The timespan for data retention. Select from the drop-down list: + - Collect Activity from the last 180 days – Configure the number of days to collect activity + with the up and down arrows + - Retain data – The timespan for data retention. Select from the dropdown list: - within timespan - forever - Absolute Timespan diff --git a/docs/accessanalyzer/12.0/admin/datacollector/spaa/activityloglocations.md b/docs/accessanalyzer/12.0/admin/datacollector/spaa/activityloglocations.md index 2dcdfbad4c..3312846a13 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/spaa/activityloglocations.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/spaa/activityloglocations.md @@ -6,8 +6,8 @@ sidebar_position: 120 # SPAA: Activity Log Locations -The Activity Log Locations page is where to manually configure log locations to avoid requiring -remote registry access to locate the activity event log files. It is a wizard page for the category +Use the Activity Log Locations page to manually configure log locations, to avoid requiring remote +registry access to locate the activity event log files. It's a wizard page for the category of Scan SharePoint Activity. ![Activity Log Locations page](/images/accessanalyzer/12.0/admin/datacollector/spaa/activityloglocations.webp) @@ -16,7 +16,7 @@ The options in the Activity Log Locations page are: - Add – Opens the Customize Activity Log UNC Paths location window to add a new host - Add Default – Opens the Customize Activity Log UNC Paths location window for the default host -- Edit – Opens the Customize Activity Log UNC Paths window for the selected host. If edits are made, +- Edit – Opens the Customize Activity Log UNC Paths window for the selected host. If you make edits, click **OK** to save the changes. - Remove – Removes the selected host @@ -31,17 +31,17 @@ The options in the Customize Activity Log UNC Paths Window are: Activity Logs (as configured in **Activity Monitor** > **Monitored Hosts**) :::note - For On-Premises environments you do not need to specify an Activity Log UNC path as + For On-Premises environments you don't need to specify an Activity Log UNC path as the Data Collector will default to finding the log locations via the registry. ::: - Activity archive UNC path – UNC path to the archive location of Activity Logs (as configured in - **Activity Monitor** > **Agents**). If archiving is not enabled in Activity Monitor this can be - left blank. + **Activity Monitor** > **Agents**). If you haven't enabled archiving in Activity Monitor, you can + leave this blank. :::note -In any UNC paths, `%HOST%` will be replaced with the host name. +In any UNC paths, Access Analyzer replaces `%HOST%` with the host name. ::: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/spaa/additionalscoping.md b/docs/accessanalyzer/12.0/admin/datacollector/spaa/additionalscoping.md index a61e6ecc99..5593ae520a 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/spaa/additionalscoping.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/spaa/additionalscoping.md @@ -6,33 +6,33 @@ sidebar_position: 60 # SPAA: Additional Scoping -The Additional Scoping page is where the scan can be limited by depth of the scan. It is a wizard +Use the Additional Scoping page to limit the scan by depth. It's a wizard page for the categories of: - Scan SharePoint Access - Scan For Sensitive Content :::warning -Users should not change scans in a way that would result in less data being returned on -a subsequent scan (i.e. scanning fewer web applications, scanning fewer site collections, or a -shallower depth scan). Those resources not included in a subsequent scan are marked as deleted in -the Tier 2 database and subsequently removed from the Tier 1 database. +Don't change scans in a way that results in returning less data on a subsequent scan (i.e. +scanning fewer web applications, scanning fewer site collections, or a shallower depth scan). +Access Analyzer marks resources not included in a subsequent scan as deleted in the Tier 2 +database and later removes them from the Tier 1 database. ::: ![Additional Scoping page](/images/accessanalyzer/12.0/admin/datacollector/spaa/additionalscoping.webp) -If checked, set the **Limit scanned depth to: [number] level(s)** option to the desired depth. If -this option is not checked then the entire farm is scanned. If the scoping depth is set to **0** -then only root site collections are scanned. Each increment to the depth adds an additional level of -depth from that point. +If checked, set the **Limit scanned depth to: [number] levels** option to the depth you want. If +you don't check this option, Access Analyzer scans the entire farm. If you set the scoping depth to +**0**, Access Analyzer scans only root site collections. Each increment to the depth adds an +additional level of depth from that point. Check the **Perform differential scan** box to enable the job to run a differential scan. -Differential scanning is enabled by default. When this option is enabled, SPAA scan will only parse -files for content/SDD if it has been modified since the last scan. +Access Analyzer enables differential scanning by default. When you enable this option, the SPAA +scan will only parse files for content/SDD if they changed since the last scan. :::note -This option only applies to Tag collection and Sensitive data collection. Files will be -still be scanned for permissions regardless of whether this option is checked or not. +This option only applies to Tag collection and Sensitive data collection. Access Analyzer will +still scan files for permissions regardless of whether you check this option. ::: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/spaa/agentsettings.md b/docs/accessanalyzer/12.0/admin/datacollector/spaa/agentsettings.md index 7038dc3f79..ccdf7d05e3 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/spaa/agentsettings.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/spaa/agentsettings.md @@ -6,20 +6,20 @@ sidebar_position: 70 # SPAA: Agent Settings -The Agent Settings page is where the SharePoint Agent Service is configured. It is a wizard page for +Use the Agent Settings page to configure the SharePoint Agent Service. It's a wizard page for the category of Scan SharePoint Access. ![Agent Settings page](/images/accessanalyzer/12.0/admin/datacollector/spaa/agentsettings.webp) The **Enable Agent Service Scans** checkbox enables collecting SharePoint data through the agent -services instead of directly from SharePoint. This option requires a **Network Port** to be entered. +services instead of directly from SharePoint. This option requires you to enter a **Network Port**. Agent Service Identity radio buttons are: - Use Job Credentials when job has same credentials as agent services - Use Custom Identity for other agent service credential scenarios - Specify identity in the format `spn:name` or `upn:name` - - The token `%HOST%` may be substituted for the host name + - You can substitute the token `%HOST%` for the host name -This option requires the SharePoint Agent to be installed on the application server. See the +This option requires you to install the SharePoint Agent on the application server. See the [SharePoint Agent Installation](/docs/accessanalyzer/12.0/install/sharepointagent/overview.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/spaa/bulkimportsettings.md b/docs/accessanalyzer/12.0/admin/datacollector/spaa/bulkimportsettings.md index c51e8f0ac3..1904ce3948 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/spaa/bulkimportsettings.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/spaa/bulkimportsettings.md @@ -6,7 +6,7 @@ sidebar_position: 80 # SPAA: Bulk Import Settings -The Bulk Import Settings page is where the bulk import process settings are configured. It is a +Use the Bulk Import Settings page to configure the bulk import process settings. It's a wizard page for the categories of: - Bulk Import Access Scan Results @@ -14,7 +14,7 @@ wizard page for the categories of: ![Bulk Import Settings page](/images/accessanalyzer/12.0/admin/datacollector/spaa/bulkimportsettings.webp) -Subsequent hosts in job lists will get host IDs incremented by 1. The Host Identifier may require an -offset to avoid overlapping IDs in collected data. If the **Set Host ID** checkbox is left -unchecked, then Access Analyzer assigns values starting from 1 to every host. This feature is -intended only for SQL Server Replication. +Access Analyzer increments host IDs by 1 for subsequent hosts in job lists. The Host Identifier may require an +offset to avoid overlapping IDs in collected data. If you leave the **Set Host ID** checkbox +unchecked, Access Analyzer assigns values starting from 1 to every host. Use this feature only for +SQL Server Replication. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/spaa/category.md b/docs/accessanalyzer/12.0/admin/datacollector/spaa/category.md index 901fdf3bd2..b2474a7d2b 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/spaa/category.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/spaa/category.md @@ -30,7 +30,7 @@ The options on the Category page are: Analyzer database :::tip -Remember, the sensitive data discovery options require the Sensitive Data Discovery Add-On to be -installed on the Access Analyzer Console. If the SharePoint Agent is used, then it must also be -installed on the application server that hosts the Central Administration component. +Remember, the sensitive data discovery options require you to install the Sensitive Data Discovery +Add-On on the Access Analyzer Console. If you use the SharePoint Agent, you must also install it on +the application server that hosts the Central Administration component. ::: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/spaa/configurejob.md b/docs/accessanalyzer/12.0/admin/datacollector/spaa/configurejob.md index 04a0d6839f..136c7efdd7 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/spaa/configurejob.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/spaa/configurejob.md @@ -6,12 +6,12 @@ sidebar_position: 20 # SharePoint Custom Connection Profile & Host List -The SPAA Data Collector requires a custom Connection Profile and a custom host list to be created -and assigned to the job conducting the data collection. The host inventory option during host list -creation makes it necessary to configure the Connection Profile first. While SharePoint on-premises -uses the Active Directory account type for the credential within a Connection Profile, it is -necessary for online credentials to be listed first in the credentials list within a Connection -Profile housing credentials to both environments. +The SPAA Data Collector requires you to create a custom Connection Profile and a custom host list +and assign them to the job conducting the data collection. The host inventory option during host +list creation requires you to configure the Connection Profile first. While SharePoint on-premises +uses the Active Directory account type for the credential within a Connection Profile, you must +list online credentials first in the credentials list within a Connection Profile housing +credentials to both environments. ## SharePoint Farm @@ -25,17 +25,17 @@ The provisioned credential used should be an Active Directory account. Create a Connection Profile and set the following information on the User Credentials window: - Select Account Type – Active Directory Account -- Domain – Drop-down menu with available trusted domains displays. Either type the short domain name +- Domain – dropdown menu with available trusted domains displays. Either enter the short domain name in the textbox or select a domain from the menu. -- User name – Type the user name +- User name – Enter the user name - Password Storage – Choose the for credential password storage: - Application – Uses Access Analyzer’s configured Profile Security setting as selected at the **Settings** > **Application** node - CyberArk – Uses the CyberArk Enterprise Password Vault -- Password – Type the password -- Confirm – Re-type the password +- Password – Enter the password +- Confirm – Re-enter the password -Once the Connection Profile is created, it is time to create the custom host list. See the +After you create the Connection Profile, create the custom host list. See the [Connection](/docs/accessanalyzer/12.0/admin/settings/connection/overview.md) topic for additional information. ### SharePoint Farm Host in a Custom Host List @@ -43,7 +43,7 @@ Once the Connection Profile is created, it is time to create the custom host lis The custom host list should include: - One application server per farm -- Host name without a domain suffix, this means the host name should not contain a period character +- Host name without a domain suffix, this means the host name shouldn't contain a period character See the [Add Hosts](/docs/accessanalyzer/12.0/admin/hostmanagement/actions/add.md) section for instruction on creating a custom static host list. @@ -82,31 +82,31 @@ Create a Connection Profile and set the following information on the User Creden - 5 – US Government-High - 6 – US Government-DoD - An example string matching the configuration from above is: + An example string that matches this configuration is: C:\Program Files (x86)\STEALTHbits\StealthAUDIT\PrivateAssemblies\spaa_cert_myorg.pfx,PasswordGoesHere,0 :::note - `PasswordGoesHere` should be replaced with the password used when generating the - self-signed X.509 certificate if the Microsoft Entra ID Application was Registered and - Provisioned manually or the $appPassword parameter used in the SP_RegisterAzureAppAuth Instant - Job if that method was used. + Replace `PasswordGoesHere` with the password used when generating the self-signed X.509 + certificate if you registered and provisioned the Microsoft Entra ID Application manually, or + with the $appPassword parameter used in the SP_RegisterAzureAppAuth Instant Job if you used + that method. ::: -Once the Connection Profile is created, it is time to create the custom host list. See the +After you create the Connection Profile, create the custom host list. See the [Connection](/docs/accessanalyzer/12.0/admin/settings/connection/overview.md) topic for additional information. ### SharePoint Online Host in a Custom Host List The custom host list should include: -- Web or cloud hosts should be specified using the full web DNS part of the site URL, for example an - Office 365 site with the URL http://TestSite.sharepoint.com should be added as a host with name +- Specify web or cloud hosts using the full web DNS part of the site URL. For example, add an + Office 365 site with the URL http://TestSite.sharepoint.com as a host named TestSite.sharepoint.com -- Do not use the admin site, for example TestSite-admin.sharepoint.com -- Do not use IP Addresses +- Don't use the admin site, for example TestSite-admin.sharepoint.com +- Don't use IP Addresses - Host name must be in DNS format See the [Add Hosts](/docs/accessanalyzer/12.0/admin/hostmanagement/actions/add.md) topic for instructions on creating a custom diff --git a/docs/accessanalyzer/12.0/admin/datacollector/spaa/dlpauditsettings.md b/docs/accessanalyzer/12.0/admin/datacollector/spaa/dlpauditsettings.md index 1d10e1f465..2f57e52b05 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/spaa/dlpauditsettings.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/spaa/dlpauditsettings.md @@ -6,14 +6,14 @@ sidebar_position: 90 # SPAA: DLP Audit Settings -The DLP Audit Settings page is where sensitive data discovery settings are configured. It is a +Use the DLP Audit Settings page to configure sensitive data discovery settings. It's a wizard page for the category of Scan For Sensitive Content. :::warning -Users should not change scans in a way that would result in less data being returned on -a subsequent scan (i.e. scanning fewer web applications, scanning fewer site collections, or a -shallower depth scan). Those resources not included in a subsequent scan are marked as deleted in -the Tier 2 database and subsequently removed from the Tier 1 database. +Don't change scans in a way that results in returning less data on a subsequent scan (i.e. +scanning fewer web applications, scanning fewer site collections, or a shallower depth scan). +Access Analyzer marks resources not included in a subsequent scan as deleted in the Tier 2 +database and later removes them from the Tier 1 database. ::: @@ -21,11 +21,11 @@ the Tier 2 database and subsequently removed from the Tier 1 database. Configure the **Scan Performance** options: -- Don’t process files larger than: Size Limit [number] MB – Limits the files to be scanned for - sensitive content to only files smaller than the specified size. The checkbox is selected by +- Don’t process files larger than: Size Limit [number] MB – Limits sensitive content scanning to + files smaller than the specified size. The checkbox is selected by default. The default size is 2 MB. - Number of SDD scan processes [number] – Increases the number of SDD scanner processes that spawn - as part of a scan, increasing parallel scanning. The value should not exceed 2x the number of CPU + as part of a scan, increasing parallel scanning. The value shouldn't exceed 2x the number of CPU threads available. Use the radio buttons to select the **File types to scan**: @@ -36,17 +36,16 @@ Use the radio buttons to select the **File types to scan**: sensitive data content :::note - The OCR option is intended to work for clear scanned physical documents or documents - directly converted to images, with standard fonts. It will not work for scanning photos of - documents and may not be able to recognize text on images of credit cards, driver's licenses, or - other identity cards. + Use the OCR option for clear scanned physical documents or documents directly converted to + images, with standard fonts. It won't work for scanning photos of documents and may not + recognize text on images of credit cards, driver's licenses, or other identity cards. ::: Use the checkboxes to select to **Store Match Hits**: - Store discovered sensitive data – Stores match hits for sensitive data in the SPAA Tier 2 - database. If this option is not selected, then the match hits for sensitive data are still - reported but the data columns are masked in the database. -- Limit stored matches per criteria to [number] – Enabled when the Store discovered sensitive data - checkbox is selected. Limits the number of stored matches per criteria to the specified number. + database. If you don't select this option, Access Analyzer still reports the match hits for + sensitive data but masks the data columns in the database. +- Limit stored matches per criteria to [number] – Active only when you select the Store discovered + sensitive data checkbox. Limits the number of stored matches per criteria to the specified number. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/spaa/droptables.md b/docs/accessanalyzer/12.0/admin/datacollector/spaa/droptables.md index 7207b0a59b..9f9bb18050 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/spaa/droptables.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/spaa/droptables.md @@ -6,11 +6,11 @@ sidebar_position: 160 # SPAA Drop Tables & Views Workflow -If it becomes necessary to clear the SPAA Data Collector tables and views to resolve an issue, the -SP_DropTables Job is preconfigured to run analysis tasks that drop functions and views for the -SharePoint Solution as well as the standard tables and views generated by the **SPAA** Data +If you need to clear the SPAA Data Collector tables and views to resolve an issue, use the +preconfigured SP_DropTables Job to run analysis tasks that drop functions and views for the +SharePoint Solution, as well as the standard tables and views generated by the **SPAA** Data Collector. It is available through the Instant Job Library under the SharePoint library. Since this -job does not require a host to target, select **Local host** on the Hosts page of the Access +job doesn't require a host to target, select **Local host** on the Hosts page of the Access Analyzer Instant Job Wizard. See the [Instant Job Wizard](/docs/accessanalyzer/12.0/admin/jobs/instantjobs/overview.md) topic for additional information. @@ -20,7 +20,7 @@ Navigate to the **Jobs** > **SP_DropTables** > **Configure** node and select **A the analysis tasks. :::warning -Applying these analysis tasks will result in the deletion of collected data. +Applying these analysis tasks will delete collected data. ::: @@ -37,10 +37,10 @@ The default analysis tasks are: - **4. Drop SPAA Tables** – Drops the SharePoint Access Auditing tables imported from the previous runs -Do not try to run these tasks separately, as they are designed to work together. Follow these steps -to run the analysis tasks: +Don't try to run these tasks separately, since Netwrix designed them to work together. Follow +these steps to run the analysis tasks: -**Step 1 –** In the Analysis Selection Pane, click **Select All**. All tasks will be checked. +**Step 1 –** In the Analysis Selection Pane, click **Select All**, which checks all tasks. **Step 2 –** Right-click the **SP_DropTables** Job and select **Run Job**. The analysis execution status will be visible from the **Running Jobs** node. @@ -49,9 +49,9 @@ status will be visible from the **Running Jobs** node. All** to deselect these analysis tasks. :::info -Do not leave these analysis tasks checked in order to avoid accidental data loss. +Don't leave these analysis tasks checked to avoid accidental data loss. ::: -All of these tables have been dropped from the SQL Server database and the data is no longer -available. +The SP_DropTables Job drops all of these tables from the SQL Server database, and the data is no +longer available. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/spaa/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/spaa/overview.md index 8f1e0824c0..0b526f5083 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/spaa/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/spaa/overview.md @@ -7,8 +7,8 @@ sidebar_position: 340 # SharePointAccess Data Collector The SharePointAccess (SPAA) Data Collector audits access, group membership, and content within a -SharePoint on-premises and SharePoint Online environment. The SPAA Data Collector has been -preconfigured within the SharePoint Solution. Both this data collector and the solution are +SharePoint on-premises and SharePoint Online environment. The SharePoint Solution +preconfigures the SPAA Data Collector. Both this data collector and the solution are available with a special Access Analyzer license. See the [SharePoint Solution](/docs/accessanalyzer/12.0/solutions/sharepoint/overview.md) topic for additional information. The SPAA Data Collector has the following requirements: @@ -34,13 +34,13 @@ The SPAA Data Collector has the following requirements: **Sensitive Data Discovery Considerations** -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the minimum amount -of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For example, if the job -is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are required (8x2=16). +If you run Sensitive Data Discovery (SDD) scans, you must increase the minimum amount +of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For example, if you +configure the job to scan 8 hosts at a time, it requires an extra 16 GB of RAM (8x2=16). ## SPAA Query Configuration -The SharePointAccess Data Collector is configured through the SharePoint Access Auditor Data +You configure the SharePointAccess Data Collector through the SharePoint Access Auditor Data Collector Wizard. The wizard contains the following pages, which change based up on the query Category selected: @@ -61,5 +61,5 @@ Category selected: ![SPAA Data Collector Wizard Welcome Page](/images/accessanalyzer/12.0/admin/datacollector/spaa/welcomepage.webp) -The Welcome page can be hidden by checking the **Do not display this page the next time** box when -the wizard is open and configuration settings are saved. +You can hide the Welcome page by checking the **Don't display this page the next time** box when +the wizard is open and you save configuration settings. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/spaa/results.md b/docs/accessanalyzer/12.0/admin/datacollector/spaa/results.md index 507a348002..9344719bd5 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/spaa/results.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/spaa/results.md @@ -6,12 +6,13 @@ sidebar_position: 140 # SPAA: Results -The Results page is where properties that will be gathered are selected. It is a wizard page for all +Use the Results page to select properties to gather. It's a wizard page for all of the categories. ![Results page](/images/accessanalyzer/12.0/admin/datacollector/spaa/results.webp) -Properties can be checked individually, or the **Select All**and **Clear All** buttons can be used. -All checked properties are gathered. Available properties vary based on the category selected. This -information is not available within the standard reference tables. Instead, this information can be -viewed in the table created by the query task, for example SA_1-SPAA_SystemScans_Access table. +You can check properties individually, or use the **Select All** and **Clear All** buttons. +Access Analyzer gathers all checked properties. Available properties vary based on the category +selected. This information isn't available within the standard reference tables. Instead, you can +view this information in the table created by the query task, for example the +SA_1-SPAA_SystemScans_Access table. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/spaa/scanscopingoptions.md b/docs/accessanalyzer/12.0/admin/datacollector/spaa/scanscopingoptions.md index 1510625f2c..c2fa623c20 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/spaa/scanscopingoptions.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/spaa/scanscopingoptions.md @@ -6,7 +6,7 @@ sidebar_position: 50 # SPAA: Scan Scoping Options -The Scan Scoping Options page provides scoping options to specify the list of URLs to be scanned. It +The Scan Scoping Options page provides scoping options to specify the list of URLs to scan. It is a wizard page for the categories of: - Scan SharePoint Access @@ -16,7 +16,7 @@ is a wizard page for the categories of: The options on the Scan Scoping Options page are: -- Add – When a URL is entered in the text box, adds the URL to the Scope box +- Add – Entering a URL in the text box adds it to the Scope box - To scope for a SharePoint Host Named Site Collections, use the text box to enter the URL for both the Web App and the HNSC with custom non-existent URL extensions added. See the @@ -24,19 +24,19 @@ The options on the Scan Scoping Options page are: topic for additional information. :::note - If sites are included in the Scope box, all other sites are excluded from the scan. + If you include sites in the Scope box, Access Analyzer excludes all other sites from the scan. ::: - Import CSV – Opens a file explorer to browse for a CSV file - Scope box – Lists all added URLs -- Scope drop-down list – Select include to include a URL in the scan. Select exclude to exclude a +- Scope dropdown list – Select include to include a URL in the scan. Select exclude to exclude a URL from the scan. - Remove – Removes the selected URL from the Scope box ## Scoping to SharePoint Host Named Site Collections -In order to scope to objects within host named site collections, add a scope line which includes the +to scope to objects within host named site collections, add a scope line which includes the URL of the web application containing the host named site collection. To scope the host named site collection URL `http://sample.com/documents/` for a host named site collection that exists under the web application URL `http://example.com`, follow the steps: @@ -56,24 +56,24 @@ the HNSCs. Click **Add**. ![Scan Scoping Options example](/images/accessanalyzer/12.0/admin/datacollector/spaa/scanscopingoptionsexample.webp) -**Step 4 –** The Web App URL must appear above the HNSC URL, as depicted in the example above. +**Step 4 –** The Web App URL must appear above the HNSC URL, as depicted in the preceding example. -**Step 5 –** The SharePoint Access Auditor Data Collector Wizard is now configured to filter for the -URL inside the SharePoint Host Named Site Collections. +**Step 5 –** You have now configured the SharePoint Access Auditor Data Collector Wizard to filter +for the URL inside the SharePoint Host Named Site Collections. ## Virtual Hosts -In order to decrease the scan time in large SharePoint Online environments, it is possible to break -Site Collections for a single host down into subsets, or **Virtual Hosts**, that are treated as -separate hosts by Access Analyzer. This allows multiple scans of a single host to be run -concurrently. Follow the steps to configure this. +To decrease the scan time in large SharePoint Online environments, break +Site Collections for a single host down into subsets, or **Virtual Hosts**, that Access Analyzer +treats as separate hosts. This allows you to run multiple scans of a single host +concurrently. To configure this: ![CSV file with host and site collection information](/images/accessanalyzer/12.0/admin/datacollector/spaa/virtualhostscsv.webp) -**Step 1 –** Create a new CSV file. Add into rows the information for the host and site collection -URLs you want to scan in the format `HOSTNAME#DESIGNATOR;URL`. +**Step 1 –** Create a new CSV file. Add rows containing the host and site collection URL +information you want to scan, using the format `HOSTNAME#DESIGNATOR;URL`. -- Each unique `DESIGNATOR` is treated as a separate host comprised of the specified URLs. +- Access Analyzer treats each unique `DESIGNATOR` as a separate host comprised of the specified URLs. ![Host List for targeting the Virtual Hosts](/images/accessanalyzer/12.0/admin/datacollector/spaa/virtualhostshostlist.webp) @@ -88,15 +88,16 @@ Wizard, use the **Import CSV** button to import the information from the CSV fil **Step 4 –** Click **Next** to continue through the other pages of the SharePoint Access Auditor Data Collector Wizard. Then click **Finish** on the Summary Page. -Access Analyzer is now configured to scan multiple site collections for the same host concurrently. +You have now configured Access Analyzer to scan multiple site collections for the same host +concurrently. -A new host folder is created for each Virtual Host in `Jobs/SA_CommonData/SHAREPOINTACCESS`. You -will also see a separate line on the Running Instances tab for each Virtual Host included in the -scan. +Access Analyzer creates a new host folder for each Virtual Host in +`Jobs/SA_CommonData/SHAREPOINTACCESS`. You will also see a separate line on the Running Instances +tab for each Virtual Host included in the scan. :::note -The Host List for Bulk Import should be configured to contain each Virtual Host included -in the above scan using the `HOSTNAME#DESIGNATOR` format. After Bulk Import, the data contained in +You should configure the Host List for Bulk Import to contain each Virtual Host included in the +preceding scan, using the `HOSTNAME#DESIGNATOR` format. After Bulk Import, the data contained in Tier 1 Database tables and views will resemble a scan run against multiple hosts. ::: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/spaa/selectdlpcriteria.md b/docs/accessanalyzer/12.0/admin/datacollector/spaa/selectdlpcriteria.md index f871e54ec7..0632ec48da 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/spaa/selectdlpcriteria.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/spaa/selectdlpcriteria.md @@ -6,14 +6,14 @@ sidebar_position: 100 # SPAA: Select DLP Criteria -The Select Criteria page is where criteria to be used for discovering sensitive data are configured. -It is a wizard page for the category of Scan For Sensitive Content. +Use the Select Criteria page to configure criteria for discovering sensitive data. It's a wizard +page for the category of Scan For Sensitive Content. :::warning -Users should not change scans in a way that would result in less data being returned on -a subsequent scan (i.e. scanning fewer web applications, scanning fewer site collections, or a -shallower depth scan). Those resources not included in a subsequent scan are marked as deleted in -the Tier 2 database and subsequently removed from the Tier 1 database. +Don't change scans in a way that results in returning less data on a subsequent scan (i.e. +scanning fewer web applications, scanning fewer site collections, or a shallower depth scan). +Access Analyzer marks resources not included in a subsequent scan as deleted in the Tier 2 +database and later removes them from the Tier 1 database. ::: @@ -28,8 +28,8 @@ The options on the Select DLP Criteria page are: sensitive data criteria to scan for - Select All – Click **Select All** to enable all sensitive data criteria for scanning - Clear All – Click **Clear All** to remove all selections from the table -- Select the checkboxes next to the sensitive data criteria options to enable it to be scanned for - during job execution +- Select the checkboxes next to the sensitive data criteria options to include them in job + execution scans The table contains the following types of criteria: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/spaa/settings.md b/docs/accessanalyzer/12.0/admin/datacollector/spaa/settings.md index 4af1a7ebfc..63b3321325 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/spaa/settings.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/spaa/settings.md @@ -6,51 +6,49 @@ sidebar_position: 40 # SPAA: SharePoint Data Collection Settings -The SharePoint data collection settings page is where additional scan settings are configured. It is -a wizard page for the categories of: +Use the SharePoint data collection settings page to configure additional scan settings. It's a +wizard page for the categories of: - Scan SharePoint Access - Scan For Sensitive Content :::warning -Users should not change scans in a way that would result in less data being returned on -a subsequent scan (i.e. scanning fewer web applications, scanning fewer site collections, or a -shallower depth scan). Those resources not included in a subsequent scan are marked as deleted in -the Tier 2 database and subsequently removed from the Tier 1 database. +Don't change scans in a way that results in returning less data on a subsequent scan (i.e. +scanning fewer web applications, scanning fewer site collections, or a shallower depth scan). +Access Analyzer marks resources not included in a subsequent scan as deleted in the Tier 2 +database and later removes them from the Tier 1 database. ::: ![SharePoint data collection settings page](/images/accessanalyzer/12.0/admin/datacollector/spaa/datacollectionsettings.webp) -The Probable Owners section provides options for how probable ownership will be calculated: +The Probable Owners section provides options for how Access Analyzer calculates probable ownership: - Limit maximum number of Probable Owners per resource: [number] – Return the maximum user supplied number of probable owners per resource The Collect Personal Sites checkbox enables or disables collection during the scan of personal site collections of individual users. Personal site collections are a SharePoint feature which gives -every user their own site collection, and which are used by Office 365 to store a user’s OneDrive -files. Personal sites are configured by default to only be accessible by the user to whom they -belong, and so it is likely that the Connection Profile that the data collector is assigned may not -have access to some users’ personal sites. There are three radio buttons for identifying how the -query treats personal sites to which it does not have access: +every user their own site collection, and that Office 365 uses to store a user’s OneDrive +files. By default, only the user who owns a personal site can access it, so the Connection Profile +assigned to the data collector might not have access to some users’ personal sites. Three radio +buttons identify how the query treats personal sites it doesn't have access to: -- Skip inaccessible personal sites – Inaccessible personal sites are not scanned +- Skip inaccessible personal sites – Access Analyzer doesn't scan inaccessible personal sites - Force scan account as admin of inaccessible personal sites – Make the Connection Profile - credentials a Site Collection Administrator of any personal sites to which it does not have + credentials a Site Collection Administrator of any personal sites to which it doesn't have access: - - The personal sites will be scanned - - When the scan is complete, the permissions are restored to what they were prior to the scan, - referring to those credentials made a Site Collection Administrator of personal sites in order - to conduct the scan. + - Access Analyzer scans the personal sites + - When the scan is complete, Access Analyzer restores the original permissions for any + credentials it temporarily made a Site Collection Administrator to conduct the scan. - Requires the account used in the Connection Profile credentials to have the Global Administrator role for SharePoint Online or be a Farm Administrator for SharePoint on premise. - This permission is required to facilitate altering the administrators of site collections. + This permission lets Access Analyzer alter the administrators of site collections. :::note The Microsoft SharePoint API employed to remove personal Site Collection - Administrator is unreliable, and occasionally the scanning account is left as a Site + Administrator is unreliable and occasionally leaves the scanning account as a Site Collection Administrator of personal sites. This may leave the scanning account visible to SharePoint users on the permissions of the files in their personal sites. ::: @@ -58,20 +56,20 @@ query treats personal sites to which it does not have access: :::info Only use this option if that account is clearly identifiable as an - administrative account, and users are advised of the possibility that the account could + administrative account, and you advise users that the account could appear on the permissions of their personal site collection documents. ::: - Force Company Administrator as admin of inaccessible personal sites – Make the special Company - Administrator account an administrator of any personal sites to which it does not have access + Administrator account an administrator of any personal sites to which it doesn't have access - - The personal sites will be scanned - - When the scan is complete, the Company Administrator account is left as an administrator of - the users’ personal site collections + - Access Analyzer scans the personal sites + - When the scan is complete, Access Analyzer leaves the Company Administrator account as an + administrator of the users’ personal site collections - Requires the account used in the Connection Profile credentials to have the Global Administrator role for SharePoint Online or be a Farm Administrator for SharePoint on premise. - This permission is required to facilitate altering the administrators of site collections. + This permission lets Access Analyzer alter the administrators of site collections. :::note The Company Administrator account is a special SharePoint Online and SharePoint @@ -79,12 +77,12 @@ query treats personal sites to which it does not have access: ::: -The **Extract Document Tags** option enables the collection of metadata tags from Microsoft Office -files in SharePoint. Since this option requires the retrieval and scanning of each document, it -results in a noticeable increase in scan time. +The **Extract Document Tags** option enables collecting metadata tags from Microsoft Office +files in SharePoint. Since this option requires retrieving and scanning each document, it +noticeably increases scan time. -- Select a preferred zone – Use the drop-down list to select a preferred zone within the web - application to target the scan. If a targeted web application does not have the selected preferred +- Select a preferred zone – Use the dropdown list to select a preferred zone within the web + application to target the scan. If a targeted web application doesn't have the selected preferred zone, the scan targets the default zone for that web application. Options include: - Default diff --git a/docs/accessanalyzer/12.0/admin/datacollector/spaa/standardtables.md b/docs/accessanalyzer/12.0/admin/datacollector/spaa/standardtables.md index 678e74c8f9..df455da325 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/spaa/standardtables.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/spaa/standardtables.md @@ -12,17 +12,17 @@ Data Collector writes data to these tables regardless of the job executing the q ## SharePoint Access Auditing Tables & Views -The tables and their associated views are grouped by types. +This section groups the tables and their associated views by type. **Structure Tables** | Tables | Details | | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| SA_SPAA_Hosts | Contains the names and ID of all SharePoint hosts that have been scanned for permissions. | +| SA_SPAA_Hosts | Contains the names and ID of all SharePoint hosts that Access Analyzer scanned for permissions. | | SA_SPAA_Resources | Contains information about all audited resources, which can be site collections, sites, libraries, lists, or folders. This provides information on the hierarchy relationship, as well as references to the name and rights applied to that folder. | | SA_SPAA_Sharing | Contains the view and edit links for anonymously shared resources, indicates if a resource is shared directly with trustees, and indicates whether a resource has a pending sharing request. | | SA_SPAA_SharingUsers | Contains information about the users to whom resources are shared with such as their email, login name, title, department, and describes whether the sharing grants is view only or edit permissions. | -| SA_SPAA_SiteCollections | Contains a list of site collections that were audited and references the SA_SPAA_Resources and SA_SPAA_Trustees tables for the administrators of each site collection. | +| SA_SPAA_SiteCollections | Contains a list of audited site collections and references the SA_SPAA_Resources and SA_SPAA_Trustees tables for the administrators of each site collection. | | SA_SPAA_WebApplications | Contains a list of web applications audited. | | SA_SPAA_WebAppURls | Contains a list of URLs for each web application audited. | @@ -30,14 +30,14 @@ The tables and their associated views are grouped by types. | Tables | Details | | --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| SA_SPAA_Trustees | Contains information about any domain user, group, or security principal that has been assigned permissions. This table does not contain local user and groups, as none of the trustees in this table are specific to any one host. | +| SA_SPAA_Trustees | Contains information about any domain user, group, or security principal with assigned permissions. This table doesn't contain local user and groups, as none of the trustees in this table are specific to any one host. | | SA_SPAA_TrusteeGroupMembers | Table contains information on SharePoint group membership. | **Access Calculation Tables** | Tables | Details | | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| SA_SPAA_Permissions | Contains information on the actual permissions that have been granted to resources. Each entry summarizes the rights assigned to every trustee that would appear on the permissions of a SharePoint resource. | +| SA_SPAA_Permissions | Contains information on the actual permissions granted to resources. Each entry summarizes the rights assigned to every trustee that would appear on the permissions of a SharePoint resource. | | SA_SPAA_Roles | Contains information about all of the roles on all of the site collections. | | SA_SPAA_RolesProxy | Contains a mapping of role sets to individually assigned role definitions. A role set is a distinct set of roles that are applied to one or more resources. | | SA_SPAA_WebAppPolicies | Contains summarized rights for every trustee in a web application policy. Each policy refers to a specific URL within that web application. | @@ -46,7 +46,7 @@ The tables and their associated views are grouped by types. | Tables | Details | | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| SA_SPAA_Exceptions | Contains information about security issues and concerns. One out-of-the-box exception stored inside this table is the Open Resource exception, which identifies where resources are open to Everyone, Authenticated Users, or Domain Users. | +| SA_SPAA_Exceptions | Contains information about security issues and concerns. One built-in exception stored inside this table is the Open Resource exception, which identifies where resources are open to Everyone, Authenticated Users, or Domain Users. | | SA_SPAA_ExceptionTypes | Contains summary information about exceptions. It details how many exceptions are found on each host scanned and breaks them down by exception type. | **Content Tables** @@ -59,7 +59,7 @@ The tables and their associated views are grouped by types. | SA_SPAA_Tags | Contains the individual tags which were found in documents. |  Views are the recommended way for Access Analyzer users to obtain the information gathered by the -SPAA Data Collector. They contain additional information for building queries easily. The following +SPAA Data Collector. They contain additional information for building queries. The following is an explanation of the corresponding views created for some of the tables generated by the SPAA Data Collector: @@ -67,8 +67,8 @@ Data Collector: | Views | Details | | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| SA_SPAA_PermissionsView | Provides any object permission, regardless of whether they have been made directly to folders or are inherited. An object includes site, site collection, list, library, folder, and so on. | -| SA_SPAA_DirectPermissionsView | Provides permissions that are directly applied to resources. | +| SA_SPAA_PermissionsView | Provides any object permission, regardless of whether Access Analyzer made them directly to folders or inherited them. An object includes site, site collection, list, library, folder, and so on. | +| SA_SPAA_DirectPermissionsView | Provides permissions directly applied to resources. | | SA_SPAA_EffectiveAccessView | Provides information on every trustee with access to a resource and the trustee’s level of access. This will do complete group expansion, but also take into account security principals such as Authenticated Users. Also, this view will not just expand permissions; it will calculate access by making sure every user has access to the web application. | | SA_SPAA_WebAppPoliciesView | Provides details around the web application policies that are applied to the audited SharePoint environment. These policies allow or deny access to the entire web application for the specified trustees. | @@ -83,7 +83,7 @@ Data Collector: | Views | Details | | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| SA_SPAA_ExceptionsView | Provides information on instances of exceptions that exist on the audited hosts. This view will contain a row for each exception type for each host. Exceptions are specific conditions set forth by Access Analyzer that are considered to be issues, such as folders with open access. | +| SA_SPAA_ExceptionsView | Provides information on instances of exceptions that exist on the audited hosts. This view will contain a row for each exception type for each host. Exceptions are specific conditions that Access Analyzer flags as issues, such as folders with open access. | **Additional Views** @@ -95,7 +95,7 @@ Data Collector: | Views | Details | | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| SA_SPAA_PermissionScopeResources | Provides information on the actual permissions that have been granted to resources. Each entry summarizes the rights assigned to every trustee that would appear on the permissions of a SharePoint resource. | +| SA_SPAA_PermissionScopeResources | Provides information on the actual permissions granted to resources. Each entry summarizes the rights assigned to every trustee that would appear on the permissions of a SharePoint resource. | ## SharePoint Activity Auditing Tables & Views @@ -111,7 +111,7 @@ The tables and their associated views are: | SA_SPAC_EventNames | Contains a list of SharePoint event names, their IDs, and a description of each event. | Views are the recommended way for Access Analyzer users to obtain the information gathered by the -SPAA Data Collector. They contain additional information for building queries easily. The following +SPAA Data Collector. They contain additional information for building queries. The following is an explanation of the corresponding views created for some of the tables generated by the SPAA Data Collector: @@ -126,7 +126,7 @@ Data Collector: The tables and their associated views are: :::note -Lists and libraries are excluded from Sensitive Data Discovery Auditing. +Access Analyzer excludes lists and libraries from Sensitive Data Discovery Auditing. ::: @@ -134,12 +134,12 @@ Lists and libraries are excluded from Sensitive Data Discovery Auditing. | Tables | Details | | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| SA_SPDLP_Criteria | Contains the sensitive data criteria which are selected for collection by the scan engine (data collector configuration). | +| SA_SPDLP_Criteria | Contains the sensitive data criteria selected for collection by the scan engine (data collector configuration). | | SA_SPDLP_Matches | Contains rolled up aggregate counts of the sensitive data criteria matches found during the scan. | | SA_SPDLP_MatchHits | Contains the actual sensitive data within files that matched selected criteria. For example, if the credit card criteria is used, this table will contain the potential credit card numbers identified within each files with hits. | Views are the recommended way for Access Analyzer users to obtain the information gathered by the -SPAA Data Collector. They contain additional information for building queries easily. The following +SPAA Data Collector. They contain additional information for building queries. The following is an explanation of the corresponding views created for some of the tables generated by the SPAA Data Collector: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/spaa/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/spaa/summary.md index e8a4fa7568..318d261984 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/spaa/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/spaa/summary.md @@ -6,11 +6,10 @@ sidebar_position: 150 # SPAA: Summary Page -The Summary page is where configuration settings are summarized. It is a wizard page for all of the +The Summary page summarizes the configuration settings. It's a wizard page for all of the categories. **-![Summary Page](/images/accessanalyzer/12.0/admin/datacollector/spaa/summarypage.webp)** -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the SharePoint Access Auditor Data Collector Wizard ensuring that no -accidental clicks are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** instead to +close the SharePoint Access Auditor Data Collector Wizard without saving accidental clicks. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/spaa/testaccess.md b/docs/accessanalyzer/12.0/admin/datacollector/spaa/testaccess.md index a48f5d29c3..6fbc98cd32 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/spaa/testaccess.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/spaa/testaccess.md @@ -22,11 +22,11 @@ The options and sections on the Test Access page are: Server text box. Click **Check Access** to test access to the SharePoint environment. - For example – `sbnjqasp30` or `sbnjqasp3.qa.com` - - Do not include `http[s]://` or use a URL for the server name. The Test Access function cannot - be scoped to individual Web applications. + - Don't include `http[s]://` or use a URL for the server name. You can't scope the Test Access + function to individual Web applications. -- Access Test Results – Displays information on test results. Test criteria are listed in the - **Description** column. Test results will be returned as either **Pass** or **Fail** in the +- Access Test Results – Displays information on test results. Access Analyzer lists test criteria + in the **Description** column and returns test results as either **Pass** or **Fail** in the Results column. - Save Report – Click **Save Report** to export and save a text version of the test results diff --git a/docs/accessanalyzer/12.0/admin/datacollector/sql/category.md b/docs/accessanalyzer/12.0/admin/datacollector/sql/category.md index f7676daf5c..688ae35c17 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/sql/category.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/sql/category.md @@ -91,7 +91,7 @@ The query categories are: - Latest Week Backup – Information about the latest week backup - Oldest and Newest Backup – Information about the oldest and the most recent backups - - Database File Without Backup – Indicates file names of the files that are not present in + - Database File Without Backup – Indicates file names of the files that aren't present in the RMAN backup - Utilities diff --git a/docs/accessanalyzer/12.0/admin/datacollector/sql/configurejob.md b/docs/accessanalyzer/12.0/admin/datacollector/sql/configurejob.md index 8c6ca83224..7ac3de67b7 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/sql/configurejob.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/sql/configurejob.md @@ -6,9 +6,9 @@ sidebar_position: 10 # SQL Custom Connection Profile & Default Dynamic Host List -The SQL Data Collector requires a custom Connection Profile and Host List. The **SQL SERVERS** -default host list can be used with this data collector for the SQL Solution. The host inventory -option during host list creation makes it necessary to configure the Connection Profile first. +The SQL Data Collector requires a custom Connection Profile and Host List. You can use the +**SQL SERVERS** default host list with this data collector for the SQL Solution. The host +inventory option during host list creation requires you to configure the Connection Profile first. ## Connection Profile @@ -17,20 +17,20 @@ Create a Connection Profile and set the following information on the User Creden - For an Active Directory account: - Select Account Type – Active Directory Account - - Domain – Drop-down menu with available trusted domains will appear. Either type the short + - Domain – dropdown menu with available trusted domains will appear. Either enter the short domain name in the textbox or select a domain from the menu. - - User name – Type the user name - - Password Storage – Choose the desired option for credential password storage: + - User name – Enter the user name + - Password Storage – Choose the option you want for credential password storage: - Application – Uses the configured Profile Security setting as selected at the **Settings** > **Application** node. See the [Application](/docs/accessanalyzer/12.0/admin/settings/application/overview.md) topic for additional information. - CyberArk – Uses the CyberArk Enterprise Password Vault. See the [CyberArk Integration](/docs/accessanalyzer/12.0/admin/settings/connection/cyberarkintegration.md) topic for - additional information. The password fields do not apply for CyberArk password storage. + additional information. The password fields don't apply for CyberArk password storage. - - Password – Type the password - - Confirm – Re-type the password + - Password – Enter the password + - Confirm – Re-enter the password - For a SQL account: @@ -39,30 +39,30 @@ Create a Connection Profile and set the following information on the User Creden - Password Storage – Application (Uses the configured Profile Security setting as selected at the **Settings** > **Application** node. See the [Application](/docs/accessanalyzer/12.0/admin/settings/application/overview.md) topic for additional information.) - - Password – Type the password - - Confirm – Re-type the password + - Password – Enter the password + - Confirm – Re-enter the password See the [Connection](/docs/accessanalyzer/12.0/admin/settings/connection/overview.md) topic for additional information. ## Host List -The required host list depends on the database that the SQL data collector is being used for. +The required host list depends on the database for which you use the SQL data collector. ### Default Dynamic Host List (SQL) Jobs using the SQL Data Collector can use the SQL Servers default host list. This is a dynamic host -list that is populated from hosts in the Host Master Table which meet the host inventory criteria -for the list, `IsSQLServer = True`. Since the SQL Servers host list is default, it is available to -jobs and job groups for host assignment. See the [Host Management](/docs/accessanalyzer/12.0/admin/hostmanagement/overview.md) +list that Access Analyzer populates from hosts in the Host Master Table which meet the host +inventory criteria for the list, `IsSQLServer = True`. Since the SQL Servers host list is default, +it is available to jobs and job groups for host assignment. See the [Host Management](/docs/accessanalyzer/12.0/admin/hostmanagement/overview.md) topic for additional information. ### Oracle / MySQL / PostgreSQL / Db2 -Jobs in the Oracle, MySQL, Postgre SQL, or Db2 solution using the SQL Data Collector must be -configured to query a host list with the servers containing the target databases. Setup the list of -hosts that needs to be monitored. Be sure to use a specific host name (if forcing the connection to +You must configure jobs in the Oracle, MySQL, PostgreSQL, or Db2 solution that use the SQL Data +Collector to query a host list with the servers containing the target databases. Set up the list of +hosts that you need to monitor. Be sure to use a specific host name (if forcing the connection to a secondary host) or just the server name if connecting to the server. See the [Host Management](/docs/accessanalyzer/12.0/admin/hostmanagement/overview.md) topic for additional information. -Additionally, the database instances must be added to the Filter page in the query configuration. +Additionally, you must add the database instances to the Filter page in the query configuration. See the [SQL: Filter](/docs/accessanalyzer/12.0/admin/datacollector/sql/filter.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/sql/criteria.md b/docs/accessanalyzer/12.0/admin/datacollector/sql/criteria.md index 904c7514d6..d1f19e9e9d 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/sql/criteria.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/sql/criteria.md @@ -6,8 +6,8 @@ sidebar_position: 40 # SQL: Criteria -The Criteria page is where criteria to be used for discovering sensitive data are configured. It is -a wizard page for the Sensitive Data Collection category. +Use the Criteria page to configure criteria for discovering sensitive data. It's a wizard page for +the Sensitive Data Collection category. ![SQL Data Collector Wizard Criteria page](/images/accessanalyzer/12.0/admin/datacollector/sql/criteria.webp) @@ -21,8 +21,8 @@ The options on the Criteria page are: - Select All– Click **Select All** to enable all sensitive data criteria for scanning - Clear All – Click **Clear All** to remove all selections from the table - - Select the checkboxes next to the sensitive data criteria options to enable it to be scanned - for during job execution + - Select the checkboxes next to the sensitive data criteria options to include them in job + execution scans The table contains the following types of criteria: @@ -36,7 +36,7 @@ The table contains the following types of criteria: :::note Adding unnecessary criteria can adversely impact the scanner performance and can cause the -scanning job to take a long time. If performance is adversely affected, revisit the sensitive data -scanning criteria and remove criteria that is not required. +scanning job to take a long time. If performance suffers, revisit the sensitive data +scanning criteria and remove criteria that isn't required. ::: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/sql/customqueryoracle.md b/docs/accessanalyzer/12.0/admin/datacollector/sql/customqueryoracle.md index 2a15d5c932..8eb13c3c8e 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/sql/customqueryoracle.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/sql/customqueryoracle.md @@ -16,11 +16,11 @@ The configurable options are: - Test Database: - - Data Source – Select the host\instance from the drop-down menu - - Database – Select the database from the drop-down menu + - Data Source – Select the host\instance from the dropdown menu + - Database – Select the database from the dropdown menu - Convert CDB to DBA on non-container databases - SQL Query textbox – Enter the custom SQL script - Validate Query – Click to test the query, results display in the box -- Row limit – Enter a number to limit the rows the query is tested on +- Row limit – Enter a number to limit the rows used to test the query diff --git a/docs/accessanalyzer/12.0/admin/datacollector/sql/customquerysql.md b/docs/accessanalyzer/12.0/admin/datacollector/sql/customquerysql.md index 600150e4fd..2ad32dc973 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/sql/customquerysql.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/sql/customquerysql.md @@ -20,9 +20,9 @@ The configurable options are: - Test Database: - - Data Source – Select the host\instance from the drop-down menu - - Database – Select the database from the drop-down menu + - Data Source – Select the host\instance from the dropdown menu + - Database – Select the database from the dropdown menu - SQL Query textbox – Enter the custom SQL script - Validate Query – Click to test the query, results display in the box -- Row limit – Enter a number to limit the rows the query is tested on +- Row limit – Enter a number to limit the rows used to test the query diff --git a/docs/accessanalyzer/12.0/admin/datacollector/sql/filter.md b/docs/accessanalyzer/12.0/admin/datacollector/sql/filter.md index 6917351844..7f90cd9c22 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/sql/filter.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/sql/filter.md @@ -6,7 +6,7 @@ sidebar_position: 50 # SQL: Filter -The Filter page is where the query can be scoped to target specific databases or instances. It is a +Use the Filter page to scope the query to target specific databases or instances. It is a wizard page for the categories of: - Permissions > Permissions Collection @@ -46,14 +46,14 @@ wizard page for the categories of: - Utilities – Remove Storage Data -It is necessary for the SA_SQL_Instances table to be populated before available databases/instances -can populate the Available Server audits list. For Oracle and SQL, the SA_SQL_Instances table is -populated through an instance discovery query. See the +You must populate the SA_SQL_Instances table before available databases/instances +can populate the Available Server audits list. For Oracle and SQL, Access Analyzer populates the SA_SQL_Instances table +through an instance discovery query. See the [0-SQL_InstanceDiscovery Job](/docs/accessanalyzer/12.0/solutions/databases/sql/collection/0-sql_instancediscovery.md) -topic for additional information. For PostgreSQL and MySQL Scans, the SA_SQL_Instances table is -populated manually in the Manage Connections window. See the -[Manage Connections Window](#manage-connections-window) topic for additional information. Once the -table has been populated, a query can be scoped. +topic for additional information. For PostgreSQL and MySQL Scans, you populate the SA_SQL_Instances table +manually in the Manage Connections window. See the +[Manage Connections Window](#manage-connections-window) topic for additional information. After you +populate the table, you can scope a query. ![SQL Data Collector Wizard Filter page](/images/accessanalyzer/12.0/admin/datacollector/sql/filter.webp) @@ -72,13 +72,13 @@ The configurable filter options are: - Select from the available list and click **Add** -- Selected databases or instances — Displays selected database objects for which the query has been - scoped. Additional options include: +- Selected databases or instances — Displays selected database objects scoped for the query. + Additional options include: - Remove — Removes the selected database/instance from the query - Include — Reverts an exclusion. By default, all sub tables are included. - Exclude — Excludes selected databases/instances and displays them in red - - Add Custom Filter — Opens the Add custom filter window to build a custom filter to be applied + - Add Custom Filter — Opens the Add custom filter window to build a custom filter to apply to the selected databases/instances. See the [Add Custom Filter Window](#add-custom-filter-window) topic for additional information. - Import CSV — Import a list of databases/instances from a CSV file @@ -86,7 +86,7 @@ The configurable filter options are: ## Manage Connections Window -The Manage Connections window enables you to add database instances to search. Click the +Use the Manage Connections window to add database instances to search. Click the **Connections** button to open it. ![Manage Connections window](/images/accessanalyzer/12.0/admin/datacollector/sql/manageconnections.webp) @@ -99,18 +99,18 @@ Select a row in the table to edit that instance, or create a new instance to add - Database System — Select from a list of available databases - Service Name — Name of the service - Host — Name or IP address of the host where the database is located -- Port Number — Port number for the database. If a non-default port is being used, it should be - specified in the Port Number section. +- Port Number — Port number for the database. If you use a non-default port, specify it in the + Port Number section. - Default Database — Account used to access the database. Admin is recommended. - Enable impersonation — Select to enable impersonation - Service Type— If applicable, select whether the service type is **Service** or **SID** In the Manage Connections Table, the following information is also listed: -- Was Inspected — Indicates whether information for a connection was validated. **Y** indicates the - information has been validated. **N** indicates the information has not been validated. -- Last Inspected — Indicates the date and time of when the connection information was last - inspected. If blank, the connection information has not yet been validated. +- Was Inspected — Indicates whether Access Analyzer validated the connection information. **Y** + indicates Access Analyzer validated the information. **N** indicates it hasn't. +- Last Inspected — Indicates the date and time Access Analyzer last inspected the connection + information. If blank, Access Analyzer hasn't validated the information yet. The Manage Connections window has the following buttons: @@ -127,7 +127,7 @@ you to apply a custom scoping filter to the query. ![Add custom filter window](/images/accessanalyzer/12.0/admin/datacollector/sql/addcustomfilter.webp) -Type the filter in the window and click Save. The following characters can be used in the filter: +Enter the filter in the window and click Save. You can use the following characters in the filter: - Forward slash (/) – Path separator - Asterisk (\*) – Wild card for any combination of characters diff --git a/docs/accessanalyzer/12.0/admin/datacollector/sql/options.md b/docs/accessanalyzer/12.0/admin/datacollector/sql/options.md index 18b0618d10..4e9ae86995 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/sql/options.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/sql/options.md @@ -76,11 +76,11 @@ The sensitive data scan settings are: **SDD Options** - Store discovered sensitive data – Stores potentially sensitive data in the Access Analyzer - database. Any sampled sensitive data discovered based on the matched criteria is stored in the - Access Analyzer database. This functionality can be disabled by clearing this option. + database, including any sampled sensitive data discovered based on the matched criteria. Clear + this option to disable this functionality. :::note - The **Store discovered sensitive data** option is required to view Content Audit + You must select the **Store discovered sensitive data** option to view Content Audit reports in the Access Information Center for SQL data. ::: @@ -91,9 +91,9 @@ The sensitive data scan settings are: ::: -- Resume scan from last point on error – Resumes scan from where the previous scan left off when the - previous scan was stopped as a result of an error +- Resume scan from last point on error – Resumes scan from where the previous scan left off if an + error stopped the previous scan :::tip -Remember, Sensitive Data Discovery is required to use the sensitive data collection option. +Remember, using the sensitive data collection option requires Sensitive Data Discovery. ::: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/sql/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/sql/overview.md index bff74a7012..ad89fa80d8 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/sql/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/sql/overview.md @@ -107,12 +107,12 @@ thread requires a minimum of 2 additional GB of RAM per host. For example, a job ## SQL Query Configuration -The SQL Data Collector is configured through the SQL Data Collector Wizard. The wizard contains the +You configure the SQL Data Collector through the SQL Data Collector Wizard. The wizard contains the following pages, which change based upon the query category selected: :::note -The SQL Data Collector is used in multiple Access Analyzer Solutions, and the query -categories used are dependent on the solution. +Multiple Access Analyzer Solutions use the SQL Data Collector, and the query +categories depend on the solution. ::: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/sql/results.md b/docs/accessanalyzer/12.0/admin/datacollector/sql/results.md index 5ff24b083c..7e254b69e0 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/sql/results.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/sql/results.md @@ -6,11 +6,11 @@ sidebar_position: 90 # SQL: Results -The Results page is where the properties that will be gathered are selected. It is a wizard page for +Use the Results page to select the properties to gather. It is a wizard page for all of the categories. ![SQL Data Collector Wizard Results Page](/images/accessanalyzer/12.0/admin/datacollector/sql/results.webp) -Properties can be selected individually, or the **Select All** and **Clear All** buttons can be -used. All selected properties are gathered. Available properties vary based on the category +You can select properties individually, or use the **Select All** and **Clear All** buttons. +Access Analyzer gathers all selected properties. Available properties vary based on the category selected. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/sql/rowkey.md b/docs/accessanalyzer/12.0/admin/datacollector/sql/rowkey.md index 7111bec544..371ecead33 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/sql/rowkey.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/sql/rowkey.md @@ -11,6 +11,6 @@ categories. ![SQL Data Collector Wizard Rowkey Page](/images/accessanalyzer/12.0/admin/datacollector/sql/rowkey.webp) -Properties selected on the Results page are listed. Select the property or properties to act as the -Rowkey. Properties can be selected individually, or the **Select All** and **Clear All** buttons can -be used. +The Rowkey page lists properties selected on the Results page. Select the property or properties to +act as the Rowkey. You can select properties individually, or use the **Select All** and **Clear +All** buttons. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/sql/settings.md b/docs/accessanalyzer/12.0/admin/datacollector/sql/settings.md index 6ab1cb2033..771c8a07f8 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/sql/settings.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/sql/settings.md @@ -11,7 +11,7 @@ instances. It is a wizard page for the category of Utilities. ![SQL Data Collector Wizard Data removal settings Page](/images/accessanalyzer/12.0/admin/datacollector/sql/settings.webp) -Data from the selected categories will be removed from the Access Analyzer database: +Access Analyzer removes data from the selected categories from the Access Analyzer database: - Permissions - Audits diff --git a/docs/accessanalyzer/12.0/admin/datacollector/sql/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/sql/summary.md index 0808b9785a..45b2a5cc78 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/sql/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/sql/summary.md @@ -6,11 +6,10 @@ sidebar_position: 110 # SQL: Summary -The Summary page is where the configuration settings are summarized. It is a wizard page for all of +The Summary page summarizes the configuration settings. It is a wizard page for all of the categories. ![SQL Data Collector Wizard Summary Page](/images/accessanalyzer/12.0/admin/datacollector/sql/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the SQL Data Collector Wizard ensuring that no accidental clicks are -saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** instead to +close the SQL Data Collector Wizard without saving accidental clicks. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/filetypes.md b/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/filetypes.md index 98b511f721..88ed381ff7 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/filetypes.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/filetypes.md @@ -6,9 +6,9 @@ sidebar_position: 70 # SystemInfo: File Types -The File Types page is where to enable count file types and specify filename masks if it is desired -to count files of given types. Two properties are generated for every mask provided, one for size -and one for count. It is a wizard page for the category of File Shares. +Use the File Types page to enable file type counting and specify filename masks if you want to +count files of specific types. Access Analyzer generates two properties for every mask provided, +one for size and one for count. It is a wizard page for the category of File Shares. ![System Info Data Collector Wizard File Types page](/images/accessanalyzer/12.0/admin/datacollector/systeminfo/filetypes.webp) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/jobscope.md b/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/jobscope.md index e68b538c32..b0ef981ff5 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/jobscope.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/jobscope.md @@ -6,7 +6,7 @@ sidebar_position: 60 # SystemInfo: Job Scope -The Job Scope page is where to select whether or not scoping should be used during execution. It is +Use the Job Scope page to select whether to use scoping during execution. It is a wizard page for the category of File Shares. ![System Info Data Collector Wizard Job Scope page](/images/accessanalyzer/12.0/admin/datacollector/systeminfo/jobscope.webp) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/options.md b/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/options.md index 55ef317f4a..dd9e3b4b26 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/options.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/options.md @@ -26,11 +26,11 @@ For the File Shares and Open File Shares categories: ![System Info Data Collector Wizard Options page for File Shares category](/images/accessanalyzer/12.0/admin/datacollector/systeminfo/optionsfileshares.webp) Select from the following options to control the depth of processing and the amount of information -to be returned by the query: +the query returns: - Include file level permissions - - Do not collect inherited file permissions + - Don't collect inherited file permissions - Return All Folders @@ -38,7 +38,7 @@ to be returned by the query: - Limit returned subfolders depth to – Specify the number of levels -- Size units for corresponding properties – Select the desired size unit: +- Size units for corresponding properties – Select the size unit you want: - Bytes - KBytes diff --git a/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/overview.md index be58c65ca8..f1af863e62 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/overview.md @@ -7,8 +7,8 @@ sidebar_position: 370 # SystemInfo Data Collector The SystemInfo Data Collector extracts information from the target system based on the selected -category. The SystemInfo Data Collector is a core component of Access Analyzer, but it has been -preconfigured within the Windows Solution. While the data collector is available with all Access +category. The SystemInfo Data Collector is a core component of Access Analyzer, but Access Analyzer +preconfigures it within the Windows Solution. While the data collector is available with all Access Analyzer license options, the Windows Solution is only available with a special Access Analyzer license. See the [Windows Solution](/docs/accessanalyzer/12.0/solutions/windows/overview.md) topic for additional information. @@ -30,7 +30,7 @@ information. ## SystemInfo Query Configuration -The SystemInfo Data Collector is configured through the System Info Data Collector Wizard, which +You configure the SystemInfo Data Collector through the System Info Data Collector Wizard, which contains the following wizard pages: - Welcome @@ -45,5 +45,5 @@ contains the following wizard pages: ![System Info Data Collector Wizard Welcome page](/images/accessanalyzer/12.0/admin/datacollector/systeminfo/welcome.webp) -The Welcome page can be hidden by selecting the **Do not display this page the next time** checkbox -when the wizard is open and configuration settings are saved. +You can hide the Welcome page by selecting the **Don't display this page the next time** checkbox +when the wizard is open and you save configuration settings. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/probableowner.md b/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/probableowner.md index 410b9ab38a..c12b817a26 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/probableowner.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/probableowner.md @@ -7,7 +7,7 @@ sidebar_position: 40 # SystemInfo: Probable Owner On the Probable Owner page, select options for determining the owner using weighted calculations. -This page is enabled when the **Probable Owner** property is selected on the Results page. +This page becomes available when you select the **Probable Owner** property on the Results page. ![System Info Data Collector Wizard Probable Owner page](/images/accessanalyzer/12.0/admin/datacollector/systeminfo/probableowner.webp) @@ -20,7 +20,7 @@ In the Determine owner section, select from the following options: - Determine owner from Current User - Determine owner from Last User - Custom weights – Select this radio button to use custom weights to determine the probable owner. - These weights can be set by clicking the ellipsis next to the Result weights box to open the + Set these weights by clicking the ellipsis next to the Result weights box to open the Probable Owner Settings window. ![Custom weights Probable Owner Settings window](/images/accessanalyzer/12.0/admin/datacollector/systeminfo/customweights.webp) @@ -52,7 +52,7 @@ Click **Set Users to Exclude** to open the Probable Owner Settings window: In the Output options section, select from the following options: -- Get the most probable owner(s) +- Get the most probable owners - Get probable owners with relative deviation to the most probable owner – Enables the following option: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/results.md b/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/results.md index 5b089854c5..26276434c8 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/results.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/results.md @@ -6,11 +6,11 @@ sidebar_position: 20 # SystemInfo: Results -The Results page is used to select which properties are gathered out of those available for the +Use the Results page to select which properties to gather from those available for the category. It is a wizard page for all categories. ![System Info Data Collector Wizard Results page](/images/accessanalyzer/12.0/admin/datacollector/systeminfo/results.webp) -Properties can be selected individually or the **Check all**, **Uncheck all**, and **Reset to -defaults** buttons can be used. All selected properties are gathered. Available properties vary +You can select properties individually, or use the **Check all**, **Uncheck all**, and **Reset to +defaults** buttons. Access Analyzer gathers all selected properties. Available properties vary based on the category selected. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/summary.md index 2407432b34..05fa9bc7dd 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/summary.md @@ -10,6 +10,5 @@ The Summary page displays a summary of the configured query. It is a wizard page ![System Info Data Collector Wizard Summary page](/images/accessanalyzer/12.0/admin/datacollector/systeminfo/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the System Info Data Collector Wizard ensuring that no accidental clicks -are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** instead to +close the System Info Data Collector Wizard without saving accidental clicks. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/vipmembership.md b/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/vipmembership.md index 77142f5185..4cee2b2368 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/vipmembership.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/vipmembership.md @@ -7,8 +7,8 @@ sidebar_position: 50 # SystemInfo: VIP Membership The VIP Membership provides the option to add members to a VIP List and exclude them from contact -about probable ownership. Any users can be added to VIP membership. This page is enabled when the -VIPList property is selected on the Results page. +about probable ownership. You can add any users to VIP membership. This page becomes available +when you select the VIPList property on the Results page. ![System Info Data Collector Wizard VIP Membership page](/images/accessanalyzer/12.0/admin/datacollector/systeminfo/vipmembership.webp) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/textsearch/advancedcriteria.md b/docs/accessanalyzer/12.0/admin/datacollector/textsearch/advancedcriteria.md index 941235e841..97f50f03b1 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/textsearch/advancedcriteria.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/textsearch/advancedcriteria.md @@ -6,8 +6,8 @@ sidebar_position: 30 # TextSearch: Advanced Criteria -The Advanced Criteria page is displayed if the **Use advanced criteria (instead of simple -criteria)** checkbox is selected on the Search Criteria page. This page provides configuration +The Advanced Criteria page displays if you select the **Use advanced criteria (instead of simple +criteria)** checkbox on the Search Criteria page. This page provides configuration options to specify the text to search for across the entire row of each file or within the specified column in each row. @@ -17,7 +17,7 @@ The configurable options are: - Return Multiple Columns – Return data values in multiple columns - Load Sample Data – Click this button to browse for sample data to test the filters entered. If the - sample data file is large, it is recommended to sample an excerpt of the file to reduce the amount + sample data file is large, sample an excerpt of the file to reduce the amount of time it takes to load the data. - Customize – Click this button to open the Filter builder @@ -26,4 +26,4 @@ The configurable options are: See the [Filtration Dialog](/docs/accessanalyzer/12.0/admin/navigate/datagrid.md#filtration-dialog) topic for information on using the Filter builder. -The filter section cannot be blank. +The filter section can't be blank. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/textsearch/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/textsearch/overview.md index fd1b767340..1441dcc771 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/textsearch/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/textsearch/overview.md @@ -7,8 +7,8 @@ sidebar_position: 380 # TextSearch Data Collector The TextSearch Data Collector enables searches through text based log files. The TextSearch Data -Collector is a core component of Access Analyzer, but it has been preconfigured within the Windows -Solution. While the data collector is available with all Access Analyzer license options, the +Collector is a core component of Access Analyzer, but Access Analyzer preconfigures it within the +Windows Solution. While the data collector is available with all Access Analyzer license options, the Windows Solution is only available with a special Access Analyzer license. See the [Windows Solution](/docs/accessanalyzer/12.0/solutions/windows/overview.md) topic for additional information. @@ -27,7 +27,7 @@ Windows Solution is only available with a special Access Analyzer license. See t ## TextSearch Query Configuration -The TextSearch Data Collector is configured through the Text Search Data Collector Wizard, which +You configure the TextSearch Data Collector through the Text Search Data Collector Wizard, which contains the following wizard pages: - Welcome @@ -39,5 +39,5 @@ contains the following wizard pages: ![Text Search Data Collector Wizard Welcome page](/images/accessanalyzer/12.0/admin/datacollector/textsearch/welcome.webp) -The Welcome page can be hidden by selecting the **Do not display this page the next time** checkbox -when the wizard is open and configuration settings are saved. +You can hide the Welcome page by selecting the **Don't display this page the next time** checkbox +when the wizard is open and you save configuration settings. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/textsearch/results.md b/docs/accessanalyzer/12.0/admin/datacollector/textsearch/results.md index 70afb245a6..2754860f87 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/textsearch/results.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/textsearch/results.md @@ -6,12 +6,12 @@ sidebar_position: 40 # TextSearch: Results -The Results page is where properties that will be gathered are selected. +Use the Results page to select properties to gather. ![Text Search Data Collector Wizard Results page](/images/accessanalyzer/12.0/admin/datacollector/textsearch/results.webp) -Properties can be selected individually or the **Check all**, **Uncheck All**, and **Reset to -Defaults** buttons can be used. All selected properties are gathered. Available properties vary +You can select properties individually, or use the **Check all**, **Uncheck All**, and **Reset to +Defaults** buttons. Access Analyzer gathers all selected properties. Available properties vary based on the category selected. - Size units – Select from the following: diff --git a/docs/accessanalyzer/12.0/admin/datacollector/textsearch/searchcriteria.md b/docs/accessanalyzer/12.0/admin/datacollector/textsearch/searchcriteria.md index 1dc19e705c..f8ad94030c 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/textsearch/searchcriteria.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/textsearch/searchcriteria.md @@ -14,8 +14,8 @@ entire row of each file. The configurable functions are: - Use advanced criteria (instead of simple criteria) – Select this checkbox to display the Advanced - Criteria page and configure the search with additional filtering options. Advanced search criteria - is configured on the Advanced Criteria page. See the + Criteria page and configure the search with additional filtering options. Configure advanced search criteria + on the Advanced Criteria page. See the [TextSearch: Advanced Criteria](/docs/accessanalyzer/12.0/admin/datacollector/textsearch/advancedcriteria.md) topic for additional information. - Simple Criteria diff --git a/docs/accessanalyzer/12.0/admin/datacollector/textsearch/sourcefiles.md b/docs/accessanalyzer/12.0/admin/datacollector/textsearch/sourcefiles.md index 048e01d26c..3e9b15df2c 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/textsearch/sourcefiles.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/textsearch/sourcefiles.md @@ -21,11 +21,11 @@ The Location section provides options to scope the search. - Current Job Directory – Search the job’s root folder for the specified file - Registry Lookup – Select this option to programmatically obtain a file path from a registry key that exists on the target host in the environment. Click the ellipsis to open the Access Analyzer - Registry Browser and connect to a host to select a registry key and path to be used for the + Registry Browser and connect to a host to select a registry key and path to use for the lookup. - Value Name – This value is automatically populated from the registry key - - Levels – The Levels slider can be used to truncate the path for the key value in the Adjust + - Levels – Use the Levels slider to truncate the path for the key value in the Adjust Path dialog box - Current value data – Displays the current value for the registry key - Query 32-bit – Select this checkbox to query a 32-bit view @@ -37,7 +37,7 @@ The Files section provides options to define the object or set of objects to fin - File name – Enter file names to search in the following format: `filename.extension`. Separate multiple file names with a semicolon and no spaces between the names. Wild cards can be used. -- File type – Select the extension type of the file name entered above to tell the collection +- File type – Select the extension type of the file name you entered to tell the collection routine how the data within the underlying file is structured and should be handled: - Autodetect – Select this when the data type is unknown. The data collection routine will @@ -48,7 +48,7 @@ The Files section provides options to define the object or set of objects to fin - Binary - Space Separated Text -- First line is header captions line – Enabled when CSV, TSV, or Space Separated Text is selected +- First line is header captions line – Active only when you select CSV, TSV, or Space Separated Text **Options** @@ -71,17 +71,17 @@ The Last Modification Time Filter section provides options to apply time filters Clicking the ellipsis in the Location section of the Source Files page opens the Remote Folder Explorer search window. In the Remote Folder Explorer window, navigate to the file folder location -and add the path to the scope. Multiple paths can be added to the scope. +and add the path to the scope. You can add multiple paths to the scope. ![Remote Folder Explorer window](/images/accessanalyzer/12.0/admin/datacollector/textsearch/remotefolderexplorer.webp) The Remote Folder Explorer functions are: -- Sample from host (path) – If the desired file does not exist on the local Access Analyzer Console, +- Sample from host (path) – If the file you want doesn't exist on the local Access Analyzer Console, enter the name of the host that contains the file and click **Connect** to browse that host - Selected Path – Displays the path selected in the box above - Add path – Click **Add path** to add the selected path to the Path box. This adds the path to the search scope. - Delete path – Select a path in the Path box and click **Delete path** to delete the path from the search scope -- Path – Displays the paths that have been added to the search scope +- Path – Displays the paths added to the search scope diff --git a/docs/accessanalyzer/12.0/admin/datacollector/textsearch/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/textsearch/summary.md index e0898aded6..5e841a8c1e 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/textsearch/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/textsearch/summary.md @@ -10,6 +10,5 @@ The Summary page displays a summary of the configured query. ![Text Search Data Collector Wizard Summary page](/images/accessanalyzer/12.0/admin/datacollector/textsearch/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Text Search Data Collector Wizard ensuring that no accidental clicks -are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** instead to +close the Text Search Data Collector Wizard without saving accidental clicks. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/unix/editscript.md b/docs/accessanalyzer/12.0/admin/datacollector/unix/editscript.md index e3303e377d..cfdbbbe858 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/unix/editscript.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/unix/editscript.md @@ -6,7 +6,7 @@ sidebar_position: 30 # Unix: Edit Script -The Edit Script page allows the script to be customized. +Use the Edit Script page to customize the script. ![Unix Data Collector Wizard Edit Script page](/images/accessanalyzer/12.0/admin/datacollector/unix/editscript.webp) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/unix/input.md b/docs/accessanalyzer/12.0/admin/datacollector/unix/input.md index 57269886ab..b40c8d5544 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/unix/input.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/unix/input.md @@ -15,12 +15,12 @@ The configurable options are: - Use SQL table for scoping input – Select the checkbox to enable scoping options - Input Table - - Name – Select the SQL table from the drop-down menu + - Name – Select the SQL table from the dropdown menu - Filter Nulls – Select the checkbox to ignore blank rows in the table - Filter Duplicates – Select the checkbox to ignore duplicate rows in the table - Filter by host column – Select the checkbox to sort rows by host -- Columns – Select the desired rows from the SQL table +- Columns – Select the rows you want from the SQL table - Data Input Method - Run command once per table row diff --git a/docs/accessanalyzer/12.0/admin/datacollector/unix/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/unix/overview.md index 3774b0c11e..a38cfffefb 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/unix/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/unix/overview.md @@ -7,8 +7,8 @@ sidebar_position: 390 # Unix Data Collector The Unix Data collector provides host inventory, software inventory, and logical volume inventory on -UNIX & Linux platforms. The Unix Data Collector has been preconfigured within the Unix Solution. -Both this data collector and the solution are available with a special Access Analyzer license. See +UNIX & Linux platforms. Access Analyzer preconfigures the Unix Data Collector within the Unix +Solution. Both this data collector and the solution are available with a special Access Analyzer license. See the [Unix Solution](/docs/accessanalyzer/12.0/solutions/unix/overview.md) topic for additional information. **Protocols** @@ -24,14 +24,14 @@ the [Unix Solution](/docs/accessanalyzer/12.0/solutions/unix/overview.md) topic - Root permissions in Unix/Linux -If the Root permission is unavailable, a least privileged model can be used. See the +If the Root permission is unavailable, you can use a least privileged model. See the [Least Privilege Model](/docs/accessanalyzer/12.0/requirements/unix/target.md#least-privilege-model) topic additional information. ## Unix Query Configuration -The Unix Data Collector is configured through the Unix Data Collector Wizard. It is designed to scan -and import information from UNIX / Linux systems. The Unix Data Collector has these pages: +You configure the Unix Data Collector through the Unix Data Collector Wizard. It scans +and imports information from UNIX / Linux systems. The Unix Data Collector has these pages: - [Unix: Settings](/docs/accessanalyzer/12.0/admin/datacollector/unix/settings.md) - [Unix: Input](/docs/accessanalyzer/12.0/admin/datacollector/unix/input.md) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/unix/results.md b/docs/accessanalyzer/12.0/admin/datacollector/unix/results.md index 6ee5a873ca..8f30b9cf3e 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/unix/results.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/unix/results.md @@ -6,16 +6,16 @@ sidebar_position: 50 # Unix: Results -On the Results page, select which properties will be gathered out of those available for the query. -Additionally select properties based on which ROWKEY will be built. +On the Results page, select which properties Access Analyzer gathers for the query. +Additionally, select the properties that make up the ROWKEY. ![Unix Data Collector Wizard Results page](/images/accessanalyzer/12.0/admin/datacollector/unix/results.webp) The configurable options are: -- Properties to return – Select the desired columns -- ROWKEY's components – Select the desired columns +- Properties to return – Select the columns you want +- ROWKEY's components – Select the columns you want Click **Finish** to save the configuration changes, or **Back** to return to the previous page. If -no changes were made, it is a best practice to click **Cancel** to close the Unix Data Collector -Wizard to make sure that no accidental settings are saved. +you made no changes, click **Cancel** instead to close the Unix Data Collector Wizard without +saving accidental settings. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/usersgroups/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/usersgroups/overview.md index 3d0a280a88..d2915c62dc 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/usersgroups/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/usersgroups/overview.md @@ -9,7 +9,7 @@ sidebar_position: 400 The UsersGroups Data Collector audits user and group accounts for both local and domain, extracting system policies. -The UsersGroups Data Collector has been preconfigured within the Windows Solution. Both this data +Access Analyzer preconfigures the UsersGroups Data Collector within the Windows Solution. Both this data collector and the solution are available with a special Access Analyzer license. See the [Windows Solution](/docs/accessanalyzer/12.0/solutions/windows/overview.md) topic for additional information. @@ -29,7 +29,7 @@ collector and the solution are available with a special Access Analyzer license. - Member of the Local Administrators group - - If a less-privileged option is required, you can use a regular domain user that has been added + - If a less-privileged option is required, you can use a regular domain user added to the **Network access: Restrict clients allowed to make remote calls to SAM** Local Security Policy @@ -37,7 +37,7 @@ collector and the solution are available with a special Access Analyzer license. ## UsersGroups Query Configuration -The UsersGroups Data Collector is configured through the Users and Groups Browser wizard, which +You configure the UsersGroups Data Collector through the Users and Groups Browser wizard, which contains the following wizard pages: - Welcome @@ -46,5 +46,5 @@ contains the following wizard pages: ![Users and Groups Browser wizard Welcome page](/images/accessanalyzer/12.0/admin/datacollector/usersgroups/welcome.webp) -The Welcome page can be hidden by selecting the **Do not display this page the next time** box when -the wizard is open and configuration settings are saved. +You can hide the Welcome page by selecting the **Don't display this page the next time** box when +the wizard is open and you save configuration settings. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/usersgroups/results/groups.md b/docs/accessanalyzer/12.0/admin/datacollector/usersgroups/results/groups.md index 89e15c3f3b..61047f2f84 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/usersgroups/results/groups.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/usersgroups/results/groups.md @@ -46,8 +46,8 @@ options opens the Find a Group or Find a User browser. ![Find a group window](/images/accessanalyzer/12.0/admin/datacollector/usersgroups/category/findagroup.webp) -The Find a Group and Find a User browsers display a list of groups or users, depending on which one -is being used, that can be selected for the option. Select from a specific host using the Sample +The Find a Group and Find a User browsers display a list of groups or users you can select for the +option, depending on which browser you use. Select from a specific host using the Sample from host option, or leave the text field blank and click **Connect** to retrieve all user groups or users that are selectable. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/usersgroups/results/results.md b/docs/accessanalyzer/12.0/admin/datacollector/usersgroups/results/results.md index 95e6eff791..85521a8c19 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/usersgroups/results/results.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/usersgroups/results/results.md @@ -6,7 +6,7 @@ sidebar_position: 10 # UsersGroups: Results -The Results page is where the type of data to be returned is configured. Each type has a different +Use the Results page to configure the type of data to return. Each type has a different set of options. ![Users and Groups Browser wizard Results page Category selection](/images/accessanalyzer/12.0/admin/datacollector/usersgroups/results.webp) diff --git a/docs/accessanalyzer/12.0/admin/datacollector/usersgroups/results/security.md b/docs/accessanalyzer/12.0/admin/datacollector/usersgroups/results/security.md index 6959317e1a..fc4eec6499 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/usersgroups/results/security.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/usersgroups/results/security.md @@ -6,11 +6,11 @@ sidebar_position: 30 # UsersGroups: Security Category -This Security policy is used to audit security policies. +Use this category to audit security policies. ![Users and Groups Browser wizard Results page Security category](/images/accessanalyzer/12.0/admin/datacollector/usersgroups/category/security.webp) -Select from the following options for what data will be returned: +Select from the following options for the data to return: - Security Policy (User Rights Assignment) – Identifies user rights assignment for each individual policy part that grants or removes rights diff --git a/docs/accessanalyzer/12.0/admin/datacollector/usersgroups/results/users.md b/docs/accessanalyzer/12.0/admin/datacollector/usersgroups/results/users.md index 53f7b0029b..0f28653f4f 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/usersgroups/results/users.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/usersgroups/results/users.md @@ -15,11 +15,11 @@ In the Users section, select from the following options: - All users – All users found on the target host - All users in the following groups – Click the ellipsis (**…**) to open the Find a Group browser window and specify a group. See the [Find a Group/User Browser](#find-a-groupuser-browser) topic - for additional information. A specific group can also be entered manually into the text field. + for additional information. You can also enter a specific group manually into the text field. - These users – Click the ellipsis (**…**) to open the Find a User browser window and specify one or more users. See the [Find a Group/User Browser](#find-a-groupuser-browser) topic for additional - information. A specific user can also be entered manually into the text field. -- Special users – The users found can be flagged as special users in the following categories: + information. You can also enter a specific user manually into the text field. +- Special users – Flag found users as special users in the following categories: - Administrator - Guest @@ -64,8 +64,8 @@ opens the Find a Group or Find a User browser. ![Find a group window](/images/accessanalyzer/12.0/admin/datacollector/usersgroups/category/findagroup.webp) -The Find a Group and Find a User browsers display a list of groups or users, depending on which one -is being used, that can be selected for the option. Select from a specific host using the Sample +The Find a Group and Find a User browsers display a list of groups or users you can select for the +option, depending on which browser you use. Select from a specific host using the Sample from host option, or leave the text field blank and click **Connect** to retrieve all user groups or users that are selectable. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/usersgroups/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/usersgroups/summary.md index a0b5b5fefe..cd46268021 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/usersgroups/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/usersgroups/summary.md @@ -10,6 +10,5 @@ The Summary page displays a summary of the configured query. ![Users and Groups Browser wizard Summary page](/images/accessanalyzer/12.0/admin/datacollector/usersgroups/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the Users and Groups Browser wizard ensuring that no accidental clicks are -saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** instead to +close the Users and Groups Browser wizard without saving accidental clicks. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/wmicollector/classes.md b/docs/accessanalyzer/12.0/admin/datacollector/wmicollector/classes.md index f484d39ee9..aaf8cfe275 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/wmicollector/classes.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/wmicollector/classes.md @@ -10,6 +10,6 @@ On the Classes page, configure the WMICollector namespaces and classes to use as ![WMI Browser wizard Classes page](/images/accessanalyzer/12.0/admin/datacollector/wmicollector/classes.webp) -Select the **Namespace** and **Class** from the drop-down lists to use as a data source. The default -namespace, **root\CIMV2**, is typically what should be used. Select the **Win32 classes only** +Select the **Namespace** and **Class** from the dropdown lists to use as a data source. You +typically use the default namespace, **root\CIMV2**. Select the **Win32 classes only** checkbox to use only Win32 classes. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/wmicollector/overview.md b/docs/accessanalyzer/12.0/admin/datacollector/wmicollector/overview.md index 8242a80b76..72acecb4ff 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/wmicollector/overview.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/wmicollector/overview.md @@ -7,8 +7,8 @@ sidebar_position: 410 # WMICollector Data Collector The WMICollector Data Collector identifies data for certain types of WMI classes and namespaces. The -WMICollector Data Collector is a core component of Access Analyzer, but it has been preconfigured -within the Windows Solution. While the data collector is available with all Access Analyzer license +WMICollector Data Collector is a core component of Access Analyzer, but Access Analyzer +preconfigures it within the Windows Solution. While the data collector is available with all Access Analyzer license options, the Windows Solution is only available with a special Access Analyzer license. See the [Windows Solution](/docs/accessanalyzer/12.0/solutions/windows/overview.md) topic for additional information. @@ -28,7 +28,7 @@ options, the Windows Solution is only available with a special Access Analyzer l ## WMICollector Query Configuration -The WMICollector Data Collector is configured through the WMI Browser wizard, which contains the +You configure the WMICollector Data Collector through the WMI Browser wizard, which contains the following wizard pages: - Welcome @@ -39,5 +39,5 @@ following wizard pages: ![WMI Browser wizard Welcome page](/images/accessanalyzer/12.0/admin/datacollector/wmicollector/welcome.webp) -The Welcome page can be hidden by selecting the **Do not display this page the next time** checkbox -when the wizard is open and configuration settings are saved. +You can hide the Welcome page by selecting the **Don't display this page the next time** checkbox +when the wizard is open and you save configuration settings. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/wmicollector/properties.md b/docs/accessanalyzer/12.0/admin/datacollector/wmicollector/properties.md index 8dcfe3daba..505d085b29 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/wmicollector/properties.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/wmicollector/properties.md @@ -10,10 +10,10 @@ On the Properties page, select the properties to extract. ![WMI Browser wizard Properties page](/images/accessanalyzer/12.0/admin/datacollector/wmicollector/properties.webp) -If the **Extract only selected instances** checkbox is not selected, data is returned from all -process instances displayed in the **Instances of `\`** box. To return data from a -single process instance, select an instance and select the **Extract only selected instances** -checkbox. Only one instance can be selected at a time. +If you don't select the **Extract only selected instances** checkbox, Access Analyzer returns data +from all process instances displayed in the **Instances of `\`** box. To return +data from a single process instance, select an instance and select the **Extract only selected +instances** checkbox. You can select only one instance at a time. -In the **Instance data** box, select the checkboxes next to the desired properties to return during +In the **Instance data** box, select the checkboxes next to the properties you want to return during query execution. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/wmicollector/samplehost.md b/docs/accessanalyzer/12.0/admin/datacollector/wmicollector/samplehost.md index c2089a3a8f..2a3cea94e9 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/wmicollector/samplehost.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/wmicollector/samplehost.md @@ -10,7 +10,7 @@ On the Sample Host page, enter a sample host to populate options for the query. ![WMI Browser wizard Sample Host page](/images/accessanalyzer/12.0/admin/datacollector/wmicollector/samplehost.webp) -On the Sample Host page, if the desired classes and namespaces to audit reside on the local host, -click **Next**. (The local host is represented by `.` in the **Sample host name** box). If a -different sample host is needed to populate the namespace and class options, enter the name for the +On the Sample Host page, if the classes and namespaces you want to audit reside on the local host, +click **Next**. (A period (`.`) represents the local host in the **Sample host name** box). If you need +a different sample host to populate the namespace and class options, enter the name for the remote host and click **Next**. diff --git a/docs/accessanalyzer/12.0/admin/datacollector/wmicollector/summary.md b/docs/accessanalyzer/12.0/admin/datacollector/wmicollector/summary.md index 961cb26dac..0996dfb448 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/wmicollector/summary.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/wmicollector/summary.md @@ -10,5 +10,5 @@ The Summary page, or Results page, displays a summary of the configured query. ![WMI Browser wizard Summary page](/images/accessanalyzer/12.0/admin/datacollector/wmicollector/summary.webp) -Click **Finish** to save configuration changes. If no changes were made, it is a best practice to -click **Cancel** to close the WMI Browser wizard ensuring that no accidental clicks are saved. +Click **Finish** to save configuration changes. If you made no changes, click **Cancel** instead to +close the WMI Browser wizard without saving accidental clicks. diff --git a/docs/accessanalyzer/12.0/admin/hostdiscovery/activities.md b/docs/accessanalyzer/12.0/admin/hostdiscovery/activities.md index 63e49678d0..300cdcb246 100644 --- a/docs/accessanalyzer/12.0/admin/hostdiscovery/activities.md +++ b/docs/accessanalyzer/12.0/admin/hostdiscovery/activities.md @@ -19,7 +19,7 @@ The options are: - A confirmation window displays. Click **Yes** to complete the deletion - Run Query – Begins an immediate execution of the selected query -- Stop Query – Stops the selected query which is currently running +- Stop Query – Stops the selected query which is running - No action occurs if the query is **Idle** diff --git a/docs/accessanalyzer/12.0/admin/hostdiscovery/log.md b/docs/accessanalyzer/12.0/admin/hostdiscovery/log.md index 31de07f4c9..ffc08c6552 100644 --- a/docs/accessanalyzer/12.0/admin/hostdiscovery/log.md +++ b/docs/accessanalyzer/12.0/admin/hostdiscovery/log.md @@ -17,9 +17,9 @@ the [Host Discovery](/docs/accessanalyzer/12.0/admin/settings/hostdiscovery.md) The following options are above the data grid: - Reload Log – Refresh the log data for the selected Log date and Query Name -- Log date – Select the desired **Log date** from the drop-down menu to view transactions +- Log date – Select the **Log date** you want from the dropdown menu to view transactions - Query Name – The default selection is **All Queries**. To narrow the data to a desired query, - select a query name from the drop-down menu. + select a query name from the dropdown menu. The data grid contains the following columns: diff --git a/docs/accessanalyzer/12.0/admin/hostdiscovery/overview.md b/docs/accessanalyzer/12.0/admin/hostdiscovery/overview.md index 77c32302ed..cec0fc851c 100644 --- a/docs/accessanalyzer/12.0/admin/hostdiscovery/overview.md +++ b/docs/accessanalyzer/12.0/admin/hostdiscovery/overview.md @@ -11,7 +11,7 @@ the Host Discovery node to discover hosts within the targeted environment that m criteria (for example, all domain controllers for Active Directory auditing). The Host Discovery queries view displays a list of previously configured queries, opens the Host -Discovery Wizard to create new queries, and is where host inventory process can be automated. The +Discovery Wizard to create new queries, and lets you automate the host inventory process. The **Host Discovery** node houses the Discovery Log. The **Settings** > **Host Discovery** node contains the global settings that affect discovery queries. See the [Host Discovery](/docs/accessanalyzer/12.0/admin/settings/hostdiscovery.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/admin/hostdiscovery/queries.md b/docs/accessanalyzer/12.0/admin/hostdiscovery/queries.md index 447ad2a1ed..fee662859d 100644 --- a/docs/accessanalyzer/12.0/admin/hostdiscovery/queries.md +++ b/docs/accessanalyzer/12.0/admin/hostdiscovery/queries.md @@ -10,7 +10,7 @@ The Host Discovery Queries Pane contains a list of previously-configured queries ![Host Discovery Queries Pane](/images/accessanalyzer/12.0/admin/hostdiscovery/queries.webp) -The list of previously configured queries is provided in a table format with the following columns: +The list of previously configured queries appears in a table format with the following columns: - Name – Displays the name assigned to the query during creation - Query Source – Identifies where the query searches for hosts @@ -27,13 +27,13 @@ The list of previously configured queries is provided in a table format with the - Snapshot – Only shows host found during the most recent query execution :::note - The Snapshot mode is configured on the Options page of the Host Discovery Wizard. + Configure the Snapshot mode on the Options page of the Host Discovery Wizard. ::: ## View Hidden Columns -Follow the steps to view the hidden columns in the table: +To view the hidden columns in the table: **Step 1 –** Right-click a header in the table, which opens a context menu. @@ -47,7 +47,7 @@ Follow the steps to view the hidden columns in the table: ![Drag hidden colum into table](/images/accessanalyzer/12.0/admin/hostdiscovery/queriesaddhiddencolumn.webp) -**Step 4 –** Drag and drop the desired column between any header of the table. +**Step 4 –** Drag and drop the column you want between any header of the table. ![Host Discovery Queries table with column added](/images/accessanalyzer/12.0/admin/hostdiscovery/querieshiddencolumnadded.webp) diff --git a/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/addomaincontrollers.md b/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/addomaincontrollers.md index 4b7049c7d3..9f9c9c4b61 100644 --- a/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/addomaincontrollers.md +++ b/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/addomaincontrollers.md @@ -20,8 +20,8 @@ Directory server (Discover Domain Controllers)** option. Click **Next**. **Step 2 –** On the Query page, name the query and select the credentials used to access the source. - Query Name – Provide a unique descriptive name for this query by typing over the `NEWQUERY` - default name. Two queries can't have the same name. If you use an existing name, a number is - automatically appended to the query name, for example `NEWQUERY` becomes `NEWQUERY1`. + default name. Two queries can't have the same name. If you use an existing name, Access Analyzer automatically appends a number + to the query name, for example `NEWQUERY` becomes `NEWQUERY1`. - Credentials – Select a Connection Profile. These credentials require the appropriate permissions for querying the source: @@ -43,7 +43,7 @@ Click **Next** to continue. domains and sites. By default, all domains and sites are selected. If desired, scope to target specific domains and sites. -- Connection – Select the radio button to specify the server to be connected to and searched: +- Connection – Select the radio button to specify the server to connect to and search: - Connect to default directory – Selects a default domain controller from the domain in which the Access Analyzer Console server resides @@ -73,7 +73,7 @@ Click **Next** to continue. - Run the query when jobs that reference it are run – Select this option to automatically execute the Host Discovery query before executing a job that has the host list generated by this query - assigned. This ensures any new hosts have been discovered and are available for auditing. + assigned. This ensures Access Analyzer has discovered any new hosts and they're available for auditing. :::info Use this setting only for host lists tied to specific jobs that require @@ -85,7 +85,7 @@ Click **Next** to continue. - Yes, grow the host list by appending newly discovered hosts – The host list includes every host the query has ever discovered - - No, only show hosts that were found during the most recent run – The host list generated by + - No, only show hosts found during the most recent run – The host list generated by this query includes only hosts found in the most recent query execution. This option removes hosts from the generated host list, but doesn't remove hosts from the Host Master Table. @@ -127,7 +127,7 @@ configuration process. query at another time. Both options close the Host Discovery Wizard and return to the Host Discovery Queries view on the -Host Discovery node. If **Yes** is selected, the **Query State** indicates the running query. +Host Discovery node. If you select **Yes**, the **Query State** indicates the running query. ## Required Permissions diff --git a/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/adexchange.md b/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/adexchange.md index 5e54d419d8..66b102f6c8 100644 --- a/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/adexchange.md +++ b/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/adexchange.md @@ -21,8 +21,8 @@ Directory server (Discover Exchange servers)** option. Click **Next**. **Step 2 –** On the Query page, name the query and select the credentials used to access the source. - Query Name – Provide a unique descriptive name for this query by typing over the `NEWQUERY` - default name. Two queries can't have the same name. If you use an existing name, a number is - automatically appended to the query name, for example `NEWQUERY` becomes `NEWQUERY1`. + default name. Two queries can't have the same name. If you use an existing name, Access Analyzer automatically appends a number + to the query name, for example `NEWQUERY` becomes `NEWQUERY1`. - Credentials – Select a Connection Profile. These credentials require the appropriate permissions for querying the source: @@ -52,7 +52,7 @@ Leave this page unchanged. If you must modify this page, see the - Run the query when jobs that reference it are run – Select this option to automatically execute the Host Discovery query before executing a job that has the host list generated by this query - assigned. This ensures any new hosts have been discovered and are available for auditing. + assigned. This ensures Access Analyzer has discovered any new hosts and they're available for auditing. :::info Use this setting only for host lists tied to specific jobs that require @@ -64,7 +64,7 @@ Leave this page unchanged. If you must modify this page, see the - Yes, grow the host list by appending newly discovered hosts – The host list includes every host the query has ever discovered - - No, only show hosts that were found during the most recent run – The host list generated by + - No, only show hosts found during the most recent run – The host list generated by this query includes only hosts found in the most recent query execution. This option removes hosts from the generated host list, but doesn't remove hosts from the Host Master Table. @@ -106,7 +106,7 @@ configuration process. query at another time. Both options close the Host Discovery Wizard and return to the Host Discovery Queries view on the -Host Discovery node. If **Yes** is selected, the **Query State** indicates the running query. +Host Discovery node. If you select **Yes**, the **Query State** indicates the running query. ## Required Permissions diff --git a/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/adgeneral.md b/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/adgeneral.md index 901e0466ff..372baa0806 100644 --- a/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/adgeneral.md +++ b/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/adgeneral.md @@ -21,8 +21,8 @@ Directory server (General)** option. Click **Next**. **Step 2 –** On the Query page, name the query and select the credentials used to access the source. - Query Name – Provide a unique descriptive name for this query by typing over the `NEWQUERY` - default name. Two queries can't have the same name. If you use an existing name, a number is - automatically appended to the query name, for example `NEWQUERY` becomes `NEWQUERY1`. + default name. Two queries can't have the same name. If you use an existing name, Access Analyzer automatically appends a number + to the query name, for example `NEWQUERY` becomes `NEWQUERY1`. - Credentials – Select a Connection Profile. These credentials require the appropriate permissions for querying the source: @@ -77,7 +77,7 @@ Click **Next** to continue. - Run the query when jobs that reference it are run – Select this option to automatically execute the Host Discovery query before executing a job that has the host list generated by this query - assigned. This ensures any new hosts have been discovered and are available for auditing. + assigned. This ensures Access Analyzer has discovered any new hosts and they're available for auditing. :::info Use this setting only for host lists tied to specific jobs that require @@ -89,7 +89,7 @@ Click **Next** to continue. - Yes, grow the host list by appending newly discovered hosts – The host list includes every host the query has ever discovered - - No, only show hosts that were found during the most recent run – The host list generated by + - No, only show hosts found during the most recent run – The host list generated by this query includes only hosts found in the most recent query execution. This option removes hosts from the generated host list, but doesn't remove hosts from the Host Master Table. @@ -131,7 +131,7 @@ configuration process. query at another time. Both options close the Host Discovery Wizard and return to the Host Discovery Queries view on the -Host Discovery node. If **Yes** is selected, the **Query State** indicates the running query. +Host Discovery node. If you select **Yes**, the **Query State** indicates the running query. ## Required Permissions diff --git a/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/csv.md b/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/csv.md index f4b0fd52d0..2758e462be 100644 --- a/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/csv.md +++ b/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/csv.md @@ -31,8 +31,8 @@ The source in this case is the Access Analyzer Console server. - Query Name – Provide a unique descriptive name for this query by typing over the `NEWQUERY` - default name. Two queries can't have the same name. If you use an existing name, a number is - automatically appended to the query name, for example `NEWQUERY` becomes `NEWQUERY1`. + default name. Two queries can't have the same name. If you use an existing name, Access Analyzer automatically appends a number + to the query name, for example `NEWQUERY` becomes `NEWQUERY1`. - Credentials – Select a Connection Profile. These credentials require the appropriate permissions for querying the source: @@ -69,7 +69,7 @@ Click **Next** to continue. - Run the query when jobs that reference it are run – Select this option to automatically execute the Host Discovery query before executing a job that has the host list generated by this query - assigned. This ensures any new hosts have been discovered and are available for auditing. + assigned. This ensures Access Analyzer has discovered any new hosts and they're available for auditing. :::info Use this setting only for host lists tied to specific jobs that require @@ -81,7 +81,7 @@ Click **Next** to continue. - Yes, grow the host list by appending newly discovered hosts – The host list includes every host the query has ever discovered - - No, only show hosts that were found during the most recent run – The host list generated by + - No, only show hosts found during the most recent run – The host list generated by this query includes only hosts found in the most recent query execution. This option removes hosts from the generated host list, but doesn't remove hosts from the Host Master Table. @@ -123,7 +123,7 @@ configuration process. query at another time. Both options close the Host Discovery Wizard and return to the Host Discovery Queries view on the -Host Discovery node. If **Yes** is selected, the **Query State** indicates the running query. +Host Discovery node. If you select **Yes**, the **Query State** indicates the running query. ## Required Permissions diff --git a/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/database.md b/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/database.md index 379c029b11..c1f3b4151b 100644 --- a/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/database.md +++ b/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/database.md @@ -26,8 +26,8 @@ database** option. Click **Next**. **Step 2 –** On the Query page, name the query and select the credentials used to access the source. - Query Name – Provide a unique descriptive name for this query by typing over the `NEWQUERY` - default name. Two queries can't have the same name. If you use an existing name, a number is - automatically appended to the query name, for example `NEWQUERY` becomes `NEWQUERY1`. + default name. Two queries can't have the same name. If you use an existing name, Access Analyzer automatically appends a number + to the query name, for example `NEWQUERY` becomes `NEWQUERY1`. - Credentials – Select a Connection Profile. These credentials require the appropriate permissions for querying the source: @@ -65,11 +65,11 @@ names are located: ![Test connection succeeded confirmation window](/images/accessanalyzer/12.0/admin/hostdiscovery/wizard/datalinkpropertiestestconnection.webp) - - Click **Test Connection** to confirm a connection has been established. Click **OK** on the + - Click **Test Connection** to confirm the connection succeeded. Click **OK** on the confirmation window. - Database – Select the **Select the database on the server** option and use the dropdown menu to select the database - - The other tabs in the Data Link Properties window shouldn't be modified + - Don't modify the other tabs in the Data Link Properties window: - Provider tab – The database connector, dictated by the source of the data and the data sources that are available on the Access Analyzer Console server. This is set by default @@ -93,7 +93,7 @@ Click **Next** to continue. - Run the query when jobs that reference it are run – Select this option to automatically execute the Host Discovery query before executing a job that has the host list generated by this query - assigned. This ensures any new hosts have been discovered and are available for auditing. + assigned. This ensures Access Analyzer has discovered any new hosts and they're available for auditing. :::info Use this setting only for host lists tied to specific jobs that require @@ -105,7 +105,7 @@ Click **Next** to continue. - Yes, grow the host list by appending newly discovered hosts – The host list includes every host the query has ever discovered - - No, only show hosts that were found during the most recent run – The host list generated by + - No, only show hosts found during the most recent run – The host list generated by this query includes only hosts found in the most recent query execution. This option removes hosts from the generated host list, but doesn't remove hosts from the Host Master Table. @@ -147,7 +147,7 @@ configuration process. query at another time. Both options close the Host Discovery Wizard and return to the Host Discovery Queries view on the -Host Discovery node. If **Yes** is selected, the **Query State** indicates the running query. +Host Discovery node. If you select **Yes**, the **Query State** indicates the running query. ## Required Permissions diff --git a/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/ipnetwork.md b/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/ipnetwork.md index 5e5740d1c4..593479c906 100644 --- a/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/ipnetwork.md +++ b/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/ipnetwork.md @@ -20,8 +20,8 @@ option. Click **Next**. **Step 2 –** On the Query page, name the query and select the credentials used to access the source. - Query Name – Provide a unique descriptive name for this query by typing over the `NEWQUERY` - default name. Two queries can't have the same name. If you use an existing name, a number is - automatically appended to the query name, for example `NEWQUERY` becomes `NEWQUERY1`. + default name. Two queries can't have the same name. If you use an existing name, Access Analyzer automatically appends a number + to the query name, for example `NEWQUERY` becomes `NEWQUERY1`. - Credentials – Select a Connection Profile. These credentials require the appropriate permissions for querying the source: @@ -62,10 +62,10 @@ Click **Next** to continue. - IP Ranges box – Displays the selected range of IP Addresses. Use the links at the top of the box to edit the list: - - Add as inclusion – Adds information provided in the IP Address Textboxes into the to be - collected list - - Add as exclusion – Adds information provided in the IP Address Textboxes into the to be - ignored list + - Add as inclusion – Adds the information from the IP Address Textboxes to the list of + addresses to include + - Add as exclusion – Adds the information from the IP Address Textboxes to the list of + addresses to exclude - Remove – Removes the selection from the IP Ranges box - (Optional) Only include host with the following ports open – If selected, this option limits the @@ -84,7 +84,7 @@ Click **Next** to continue. - Run the query when jobs that reference it are run – Select this option to automatically execute the Host Discovery query before executing a job that has the host list generated by this query - assigned. This ensures any new hosts have been discovered and are available for auditing. + assigned. This ensures Access Analyzer has discovered any new hosts and they're available for auditing. :::info Use this setting only for host lists tied to specific jobs that require @@ -96,7 +96,7 @@ Click **Next** to continue. - Yes, grow the host list by appending newly discovered hosts – The host list includes every host the query has ever discovered - - No, only show hosts that were found during the most recent run – The host list generated by + - No, only show hosts found during the most recent run – The host list generated by this query includes only hosts found in the most recent query execution. This option removes hosts from the generated host list, but doesn't remove hosts from the Host Master Table. @@ -138,7 +138,7 @@ configuration process. query at another time. Both options close the Host Discovery Wizard and return to the Host Discovery Queries view on the -Host Discovery node. If **Yes** is selected, the **Query State** indicates the running query. +Host Discovery node. If you select **Yes**, the **Query State** indicates the running query. ## Required Permissions diff --git a/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/overview.md b/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/overview.md index 33d9be835e..ee6a121ad0 100644 --- a/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/overview.md +++ b/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/overview.md @@ -6,13 +6,13 @@ sidebar_position: 30 # Host Discovery Wizard -The Host Discovery Wizard gives complete control over how hosts are discovered on the targeted -network and which hosts are discovered. +The Host Discovery Wizard gives complete control over how Access Analyzer discovers hosts on the +targeted network and which hosts it discovers. ![Console with Create Query Option Highlighted](/images/accessanalyzer/12.0/admin/hostdiscovery/wizard/createqueryhighlighted.webp) Use the Host Discovery Wizard to create new queries. The wizard opens in the Results pane. Use any -of the following methods in order to access the Host Discovery Wizard from the Host Discovery node: +of the following methods to access the Host Discovery Wizard from the Host Discovery node: - Select **Create Query** in the Activities pane - Right-click the **Host Discovery** node and select **Create Query** from the pop-up menu @@ -38,7 +38,6 @@ for hosts. Hosts are discoverable using one of the following options: - [Import From a Database](/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/database.md) – Imports a host list from a specified SQL Server database :::note -The Advanced Options checkbox in the lower-left corner is a legacy item and should not be -selected. +Don't select the Advanced Options checkbox in the lower-left corner; it's a legacy item. ::: diff --git a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/add.md b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/add.md index fb78353439..bd8e97c8ac 100644 --- a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/add.md +++ b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/add.md @@ -7,7 +7,7 @@ sidebar_position: 10 # Add Hosts The **Add Hosts** option creates a new host list. It can be accessed through the **Host Management** -node. Follow the steps to add a new host list. +node. To add a new host list: ![Add Hosts option on Activities pane of the Host Management node](/images/accessanalyzer/12.0/admin/hostmanagement/actions/addhosts.webp) @@ -18,9 +18,9 @@ node. Follow the steps to add a new host list. **Step 2 –** On the Manual Host Entry page, choose to either enter the hosts manually one at a time, or use the **Import** option. When the list is completed, click **Next**. -- To enter hosts manually, type the host name in the **Host name** textbox. Then click **Add**. The - entry will appear in the **Host list** box. Repeat the process until all hosts for this list have - been entered. +- To enter hosts manually, enter the host name in the **Host name** textbox. Then click **Add**. The + entry will appear in the **Host list** box. Repeat the process until you've entered all hosts for + this list. - The **Import** option opens the Import Hosts window. See the [Import Hosts Option](/docs/accessanalyzer/12.0/admin/hostmanagement/actions/importhost.md) topic for additional information. - Use **Remove** to delete a selected host from the **Host list** box @@ -30,7 +30,7 @@ or use the **Import** option. When the list is completed, click **Next**. **Step 3 –** On the Specify Host List Properties page, provide a unique descriptive **Host List Name**. -- There cannot be two host lists with the same name. Access Analyzer automatically appends a numeral +- There can't be two host lists with the same name. Access Analyzer automatically appends a numeral to the end of a host list name to avoid duplicates. **Step 4 –** On the Specify Host List Properties page, configure when inventory fields should be diff --git a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/deletehost.md b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/deletehost.md index 238cad6377..79867a8a57 100644 --- a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/deletehost.md +++ b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/deletehost.md @@ -4,24 +4,24 @@ description: "Delete Host(s)" sidebar_position: 30 --- -# Delete Host(s) +# Delete Hosts -Use the **Delete Host(s)** option at the **Host Management** node to permanently delete a host from +Use the **Delete Hosts** option at the **Host Management** node to permanently delete a host from the master host table, or at an individual host list node to remove the host from the selected list. ## Delete From Host Management Node -Follow the steps to delete a host from the Host Management node. +To delete a host from the Host Management node: **Step 1 –** In the Host Management node, select the host in the data grid and click **Delete -Host(s)** on the Activities pane. +Hosts** on the Activities pane. ![Confirm dialog box](/images/accessanalyzer/12.0/admin/hostmanagement/actions/confirmdeletehost.webp) :::warning -A deletion from the host master table at the Host Management node cannot be undone, as +A deletion from the host master table at the Host Management node can't be undone, as it deletes it from the host management database tables. It also removes the host from any host list -to which it has been assigned. Click **Cancel** to stop the deletion. +it's assigned to. Click **Cancel** to stop the deletion. ::: @@ -32,9 +32,9 @@ The host is no longer in the master host table. ## Delete From Individual Host List -Follow the steps to delete a host from an individual host list. +To delete a host from an individual host list: -**Step 1 –** In the host list, select the host in the data grid and click **Delete Host(s)** on the +**Step 1 –** In the host list, select the host in the data grid and click **Delete Hosts** on the Activities pane. ![Confirm dialog box](/images/accessanalyzer/12.0/admin/hostmanagement/actions/confirmdeletehost.webp) @@ -48,12 +48,12 @@ is limited to removing the selected host from the current host list. ![Confirm deletion from master host table dialog box](/images/accessanalyzer/12.0/admin/hostmanagement/actions/confirmdeletehostmaster.webp) :::warning -A deletion from the host master table cannot be undone, as it deletes it from the host +A deletion from the host master table can't be undone, as it deletes it from the host management database tables. ::: -**Step 3 –** If the host is not found in another static host list, Access Analyzer asks if you also +**Step 3 –** If the host isn't found in another static host list, Access Analyzer asks if you also want to remove the host from the Host Master Table. On the Confirm dialog, select the desired action. diff --git a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/deletelist.md b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/deletelist.md index 37040ef69e..bff99da579 100644 --- a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/deletelist.md +++ b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/deletelist.md @@ -10,7 +10,7 @@ Use the **Delete List** option to remove the selected list. This option is avail individual host list node. :::info -Before deleting a host list, first ensure it is not assigned to a job. +Before deleting a host list, first ensure it isn't assigned to a job. ::: @@ -19,7 +19,7 @@ Before deleting a host list, first ensure it is not assigned to a job. ![Confirm dialog box](/images/accessanalyzer/12.0/admin/hostmanagement/actions/confirmdeletelist.webp) :::warning -This action cannot be undone. Click **Cancel** to stop the deletion. +This action can't be undone. Click **Cancel** to stop the deletion. ::: @@ -31,14 +31,14 @@ lists. ![Confirm deletion of orphaned hosts from master host table dialog box](/images/accessanalyzer/12.0/admin/hostmanagement/actions/confirmdeletelistmaster.webp) **Step 3 –** If no hosts are found in any other host list, then Access Analyzer asks if you want to -remove the host from the master host table. On the Confirm dialog box, select the desired option. +remove the host from the master host table. On the Confirm dialog box, select the option you want. - Yes – Deletes the specified host from the master host table -- No – Does not delete the specified host from the master host table -- No to All – Does not delete other hosts that are not found in another static host list from the +- No – Doesn't delete the specified host from the master host table +- No to All – Doesn't delete other hosts that aren't found in another static host list from the master host table - Yes to All – Deletes other hosts not found in any other static host list from the master host table When the operation is complete, the list is no longer visible under the Host Management node in the -Navigation pane and it cannot be used to execute jobs against. +Navigation pane and you can't use it to execute jobs against. diff --git a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/editlist.md b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/editlist.md index 2a76d8e7b5..6e40125da3 100644 --- a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/editlist.md +++ b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/editlist.md @@ -19,7 +19,7 @@ the Specify Host List Properties page where you can modify the following: - Host List Name :::warning - Changing the name of a host list that has been assigned to a job can cause the job + Changing the name of a host list assigned to a job can cause the job to fail. ::: diff --git a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/editquery.md b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/editquery.md index 6ae23ad8a0..0ded97e385 100644 --- a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/editquery.md +++ b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/editquery.md @@ -11,7 +11,7 @@ Use the **Edit Query** option to modify host lists created by a Host Discovery q ![Edit Query option on Activities pane](/images/accessanalyzer/12.0/admin/hostmanagement/actions/editquery.webp) In the Navigation pane, select the query-created host list to edit and click **Edit Query**. The -Host Discovery Wizard opens to the Query page where the query settings for the selected -query-created host list are modified. See the +Host Discovery Wizard opens to the Query page, where you can modify the query settings for the +selected query-created host list. See the [Host Discovery Wizard](/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/overview.md) topic for information on modifying these settings. diff --git a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/export.md b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/export.md index f47698ec18..1be6667bea 100644 --- a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/export.md +++ b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/export.md @@ -7,7 +7,7 @@ sidebar_position: 70 # Export Data Use the **Export Data** option to export all information available in the current grid view for the -selected host list to a HTML, XML , or CSV file. Follow the steps to export data. +selected host list to a HTML, XML, or CSV file. To export data: **Step 1 –** Select the Host Management or individual host list node to export data from, and configure the data grid to contain all the columns you want to export. See the diff --git a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/importhost.md b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/importhost.md index b8144f954d..8e7aeb3980 100644 --- a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/importhost.md +++ b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/importhost.md @@ -9,7 +9,7 @@ sidebar_position: 20 On the Manual Host Entry page of the Host List Wizard, the **Import** option allows hosts to be imported from either a CSV file or a database into the host list being created. -Follow the steps to import hosts. +To import hosts: ![Import option on the Manual Host Entry page of the Host List Wizard](/images/accessanalyzer/12.0/admin/hostmanagement/actions/hostlistwizardimport.webp) @@ -28,11 +28,11 @@ step. - CSV File - - File Name – Click the ellipsis (**…**) to open a browser window and select the CSV file. This - file needs to be stored on the Access Analyzer Console server. Once selected, a preview of the - file is shown in the preview box. - - Includes header row – Select this checkbox if the file contains a header row. Otherwise, the - header row will be included in the import (visible within the preview box). + - File Name – Click the ellipsis (**…**) to open a browser window and select the CSV file. You + must store this file on the Access Analyzer Console server. After you select the file, Access + Analyzer shows a preview in the preview box. + - Includes header row – Select this checkbox if the file contains a header row. Otherwise, Access Analyzer + includes the header row in the import (visible within the preview box). ![Import Hosts window for importing from Database](/images/accessanalyzer/12.0/admin/hostmanagement/actions/importhostsdatabase.webp) @@ -45,15 +45,15 @@ step. information. :::note - The Provider, Advanced, and All tabs of the Data Link Properties window should not - be modified. + Don't modify the Provider, Advanced, and All tabs of the Data Link Properties + window. ::: - - Table – Use the dropdown to select the table that contains the hosts to be imported. A preview - of the selected table is displayed in the preview box. + - Table – Use the dropdown to select the table that contains the hosts to import. Access Analyzer displays a preview + of the selected table in the preview box. -**Step 4 –** Use either the drop-down menu or click on the column in the preview box to select the +**Step 4 –** Use either the dropdown menu or click the column in the preview box to select the column containing the host names. The selected column is highlighted in the preview box. **Step 5 –** Click **OK** to complete the import. diff --git a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/importlocation.md b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/importlocation.md index ff0a098bfd..09c070ba0d 100644 --- a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/importlocation.md +++ b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/importlocation.md @@ -11,14 +11,14 @@ customized version of the Import Hosts window. Add host locations from a CSV fil database without creating a new host list. See the [Host Inventory Data Grid](/docs/accessanalyzer/12.0/admin/hostmanagement/datagrid.md) topic for information on the Location column of host inventory. -Follow the steps to import physical location data for hosts. +To import physical location data for hosts: **Step 1 –** Ensure the import source file has columns for both the host name as it is identified within Access Analyzer and the location. :::note -When a host name does not match any existing hosts within the Host Master Table, it can be -added as a new host. +When a host name doesn't match any existing hosts within the Host Master Table, you can +add it as a new host. ::: @@ -36,11 +36,11 @@ step. - CSV File - - File Name – Click the ellipsis (**…**) to open a browser window and select the CSV file. This - file needs to be stored on the Access Analyzer Console server. Once selected, a preview of the - file is shown in the preview box. - - Includes header row – Select this checkbox if the file contains a header row. Otherwise, the - header row will be included in the import (visible within the preview box). + - File Name – Click the ellipsis (**…**) to open a browser window and select the CSV file. You + must store this file on the Access Analyzer Console server. After you select the file, Access + Analyzer shows a preview in the preview box. + - Includes header row – Select this checkbox if the file contains a header row. Otherwise, Access Analyzer + includes the header row in the import (visible within the preview box). - Database @@ -51,20 +51,20 @@ step. information. :::note - The Provider, Advanced, and All tabs of the Data Link Properties window should not - be modified. + Don't modify the Provider, Advanced, and All tabs of the Data Link Properties + window. ::: - - Table – Use the dropdown to select the table that contains the hosts to be imported. A preview - of the selected table is displayed in the preview box. + - Table – Use the dropdown to select the table that contains the hosts to import. Access Analyzer displays a preview + of the selected table in the preview box. -**Step 5 –** Use either the drop-down menu or click on the column in the preview box to select the +**Step 5 –** Use either the dropdown menu or click the column in the preview box to select the column containing the host names. The selected column is highlighted in the preview box. ![Import Hosts window Location column selection](/images/accessanalyzer/12.0/admin/hostmanagement/actions/importlocationcsv.webp) -**Step 6 –** Use the **Import column** drop-down menu to select the column containing the location +**Step 6 –** Use the **Import column** dropdown menu to select the column containing the location information. The selected column is highlighted a lighter color in the preview box. **Step 7 –** Click **OK** to complete the import. @@ -72,12 +72,12 @@ information. The selected column is highlighted a lighter color in the preview b ![Imported Location column data in the data grid](/images/accessanalyzer/12.0/admin/hostmanagement/actions/importlocationcomplete.webp) The Location column now contains the imported information. If any of the hosts included in the -import file are not already in the Host Master Table, Access Analyzer prompts for confirmation on -whether or not to import the host. Selecting **Yes** or **Yes to All** adds the new hosts to the +import file aren't already in the Host Master Table, Access Analyzer prompts for confirmation on +whether to import the host. Selecting **Yes** or **Yes to All** adds the new hosts to the Host Master Table but not to any individual host lists. :::note -Any new hosts that match dynamic host list criteria will be added to the appropriate +Access Analyzer adds any new hosts that match dynamic host list criteria to the appropriate dynamic host lists. ::: diff --git a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/overview.md b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/overview.md index 3d4ddb2b0f..5d3a30c3ef 100644 --- a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/overview.md +++ b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/overview.md @@ -18,9 +18,9 @@ The available actions are: - [Add Hosts](/docs/accessanalyzer/12.0/admin/hostmanagement/actions/add.md) – Create a new host list by manually entering hosts or importing a host list (only available in the Host Management node) - [View/Edit Host](/docs/accessanalyzer/12.0/admin/hostmanagement/actions/viewhost.md) – Open the Host Details View, which displays the collected host - inventory information for the selected host in an easier-to-read format and allows you to manually + inventory information for the selected host in an easier-to-read format and lets you manually edit the host inventory information -- [Delete Host(s)](/docs/accessanalyzer/12.0/admin/hostmanagement/actions/deletehost.md) – Delete host from the selected list (permanently deletes host +- [Delete Hosts](/docs/accessanalyzer/12.0/admin/hostmanagement/actions/deletehost.md) – Delete host from the selected list (permanently deletes host from the host master table if used in the Host Management node) - [Import Location](/docs/accessanalyzer/12.0/admin/hostmanagement/actions/importlocation.md) – Import the physical location data for hosts from a CSV file or database without creating a new host list. Location column is in the @@ -35,8 +35,9 @@ The available actions are: - [Export Data](/docs/accessanalyzer/12.0/admin/hostmanagement/actions/export.md) – Export the current data grid to a HTML, XML, or CSV file - [Suspend/Resume Host Inventory](/docs/accessanalyzer/12.0/admin/hostmanagement/actions/suspend.md) – Pause an **In progress** host inventory or resume a paused **In queue** host inventory -- External commands – Sub-header (not activity) that separates the Activities above which occur - within the Access Analyzer Console from the Activities below which open external processes: +- External commands – Sub-header (not activity) that separates the activities that occur + within the Access Analyzer Console from the following external command activities, which open + external processes: - Manage Host – Opens the Microsoft Management Console interface for the selected host if it has that feature enabled @@ -50,7 +51,7 @@ Activities available only at the individual host list nodes are: - [Edit List](/docs/accessanalyzer/12.0/admin/hostmanagement/actions/editlist.md) – Edit the selected host list in the Host List Wizard - [Edit Query](/docs/accessanalyzer/12.0/admin/hostmanagement/actions/editquery.md) – Edit the Host Discovery query settings for the selected query-created host list -- [Rename List](/docs/accessanalyzer/12.0/admin/hostmanagement/actions/rename.md) – Rename the selected host list (should not be used if the host list has - already been assigned to a job for execution) +- [Rename List](/docs/accessanalyzer/12.0/admin/hostmanagement/actions/rename.md) – Rename the selected host list (don't use this option if you've + already assigned the host list to a job for execution) - [Delete List](/docs/accessanalyzer/12.0/admin/hostmanagement/actions/deletelist.md) – Delete the selected host list - [View Query](/docs/accessanalyzer/12.0/admin/hostmanagement/actions/viewquery.md) – Opens the Host Discovery Queries window diff --git a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/refresh.md b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/refresh.md index 6c6c09a0e8..a5e7d33e2a 100644 --- a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/refresh.md +++ b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/refresh.md @@ -6,7 +6,7 @@ sidebar_position: 90 # Refresh Hosts -Use the **Refresh Hosts** option to manually execute the Host Inventory query. It can be selected +Use the **Refresh Hosts** option to manually execute the Host Inventory query. You can select it for the following: - All hosts – Use from the Host Management node @@ -21,4 +21,4 @@ Select the hosts or host list to inventory and then click **Refresh Hosts** in t ![Refresh Hosts Confirm dialog](/images/accessanalyzer/12.0/admin/hostmanagement/actions/refreshhostsconfirm.webp) -When only particular hosts are selected in a list, a dialog box asks for confirmation of the action. +When you select only particular hosts in a list, a dialog box asks you to confirm the action. diff --git a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/rename.md b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/rename.md index fbc22e0bb7..743b70c87f 100644 --- a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/rename.md +++ b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/rename.md @@ -10,7 +10,7 @@ Use the Rename List option to change the name of a selected host list. This opti from an individual host list node. :::warning -Changing the name on a host list that has been assigned to a job can cause the job to +Changing the name on a host list that you've already assigned to a job can cause the job to fail. ::: @@ -21,7 +21,7 @@ Select the host list to rename and click **Rename List** to open the Host list n the new name for the host list and click **OK**. :::note -Host list names can also be changed using the **Edit List** option, see the +You can also change host list names using the **Edit List** option. See the [Edit List](/docs/accessanalyzer/12.0/admin/hostmanagement/actions/editlist.md) topic for additional information. ::: diff --git a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/savetolist.md b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/savetolist.md index 8cdf9b68af..5b17037174 100644 --- a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/savetolist.md +++ b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/savetolist.md @@ -9,7 +9,7 @@ sidebar_position: 120 Use the **Save Selected To List** option to create a static host list. This option is available from either the Host Management node or an individual host list node. See the [Static Host Lists](/docs/accessanalyzer/12.0/admin/hostmanagement/lists.md#static-host-lists) topic for additional information on static host -lists. This option is inactive until at least one host within the data grid is selected. +lists. This option is inactive until you select at least one host in the data grid. ![Save Selected To List option in Host Management node](/images/accessanalyzer/12.0/admin/hostmanagement/actions/savetolist.webp) diff --git a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/saveview.md b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/saveview.md index 3c636b240d..755ebd9093 100644 --- a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/saveview.md +++ b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/saveview.md @@ -8,11 +8,11 @@ sidebar_position: 110 Use the **Save Current View** option to create a dynamic host list. This option is available from either the Host Management node or an individual host list node. The option is inactive until you -apply a filter to the data grid. Follow the steps to create a dynamic host list. +apply a filter to the data grid. To create a dynamic host list: **Step 1 –** Select the Host Management or individual host list node to create the host list from. -**Step 2 –** Filter the data grid for the desired criteria. See the +**Step 2 –** Filter the data grid for the criteria you want. See the [Host Inventory Data Grid](/docs/accessanalyzer/12.0/admin/hostmanagement/datagrid.md) topic for additional information. ![savecurrentview](/images/accessanalyzer/12.0/admin/hostmanagement/actions/savecurrentview.webp) @@ -26,12 +26,12 @@ and click **OK**. The new host list displays under the Host Management node. When the Access Analyzer Console closes the host lists under the Host Management node, the hosts reorganize in alphanumeric order. Like the -default host lists, custom dynamic host lists are auto-populated and updated according to host -inventory. +default host lists, Access Analyzer auto-populates and updates custom dynamic host lists according +to host inventory. :::info -Do not modify the criteria once a dynamic based list has been created. It is -better to delete and recreate the list in order to modify a dynamic-based list. +Don't modify the criteria after you create a dynamic-based list. Instead, delete and recreate the +list. ::: diff --git a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/suspend.md b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/suspend.md index ddf5cb096e..18b5da3e81 100644 --- a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/suspend.md +++ b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/suspend.md @@ -10,11 +10,11 @@ Use the **Suspend Host Inventory** option to pause an in progress inventory. ![Suspend Host Inventory](/images/accessanalyzer/12.0/admin/hostmanagement/actions/suspendhostinventory.webp) -Once clicked, the option changes to **Resume Host Inventory** and the **In progress** host +After you click it, the option changes to **Resume Host Inventory** and the **In progress** host inventories change to an **In queue** state. :::note -Clicking **Refresh Hosts** while inventory is suspended adds to the queue but does not +Clicking **Refresh Hosts** while inventory is suspended adds to the queue but doesn't resume the inventory. ::: diff --git a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/viewhost.md b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/viewhost.md index 5fb55e4a00..97a6028118 100644 --- a/docs/accessanalyzer/12.0/admin/hostmanagement/actions/viewhost.md +++ b/docs/accessanalyzer/12.0/admin/hostmanagement/actions/viewhost.md @@ -20,9 +20,9 @@ The Host Details View displays in the Results pane, and the rest of the Access A unavailable while it is open. You can use the view to manually edit the host inventory information. - Edit – Enables the textboxes and checkboxes for editing -- Apply – Saves any changes. This button appears when **Edit** is clicked. +- Apply – Saves any changes. This button appears when you click **Edit**. - Save as HTML – Exports the current view of the selected host’s inventory to an HTML file. Click, - then provide a name and location for the export. The export is now sharable as desired. This + then provide a name and location for the export. Share the export as desired. This button is inactive while in edit mode. -- Cancel – Abandons any changes. This button displays when **Edit** is clicked. +- Cancel – Abandons any changes. This button displays when you click **Edit**. - Close – Exits the Host Details View diff --git a/docs/accessanalyzer/12.0/admin/hostmanagement/datagrid.md b/docs/accessanalyzer/12.0/admin/hostmanagement/datagrid.md index 7720ec692d..0db926934d 100644 --- a/docs/accessanalyzer/12.0/admin/hostmanagement/datagrid.md +++ b/docs/accessanalyzer/12.0/admin/hostmanagement/datagrid.md @@ -12,7 +12,7 @@ at the **Host Management** node (the Host Master Table) or at individual host li ![Host Inventory Data Grid](/images/accessanalyzer/12.0/admin/hostmanagement/datagrid.webp) -The icon for each host entry is an indicator of its inventory state: +The icon for each host entry indicates its inventory state: | Icon | Inventory State | | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | @@ -33,8 +33,8 @@ Use the horizontal scrollbar at the bottom to view the host inventory data, whic :::note If the Access Analyzer application is stopped during host inventory collection, hosts queued for inventory retain the **InventoryState** of **In queue** within the Host Management - node data grid, as this is the last known state of inventory. It retains that state until the - next host inventory collection is executed against the host. + node data grid, as this is the last known state of inventory. It retains that state until + Access Analyzer executes the next host inventory collection against the host. ::: diff --git a/docs/accessanalyzer/12.0/admin/hostmanagement/lists.md b/docs/accessanalyzer/12.0/admin/hostmanagement/lists.md index 4ed240a659..70fdabac9d 100644 --- a/docs/accessanalyzer/12.0/admin/hostmanagement/lists.md +++ b/docs/accessanalyzer/12.0/admin/hostmanagement/lists.md @@ -6,8 +6,8 @@ sidebar_position: 20 # Hosts Lists -A host list is a grouping of hosts for the purpose of executing jobs against. Every host list -created can be accessed by expanding the **Host Management** node in the Navigation pane. +A host list is a grouping of hosts to execute jobs against. You can access every host list +by expanding the **Host Management** node in the Navigation pane. ![Host Management Node in the Jobs Tree](/images/accessanalyzer/12.0/admin/hostmanagement/jobstree.webp) @@ -35,42 +35,43 @@ the data collected by host inventory. ## Dynamic Host Lists -Dynamic host lists are lists of hosts that are grouped according to selected criteria within the -host inventory. Each time a host inventory record is refreshed, the hosts are automatically added to -or removed from dynamic host lists in accordance with the criteria set for the list. They include +Dynamic host lists group hosts according to selected criteria within the host inventory. Each time +Access Analyzer refreshes a host inventory record, it automatically adds or removes hosts from +dynamic host lists according to the criteria set for the list. They include both the default host lists and custom created dynamic host lists. See the [Host Inventory](/docs/accessanalyzer/12.0/admin/settings/hostinventory.md) topic for a list of the default host lists and instructions on controlling which of these lists are visible under the Host Management node. -Custom dynamic host lists are created by filtering the data grid and using the -[Save Current View](/docs/accessanalyzer/12.0/admin/hostmanagement/actions/saveview.md) option in the Activities pane or right-click menu. This can -be done at the Host Management node with the Host Master Table or at any host list node. See the +Create custom dynamic host lists by filtering the data grid and using the +[Save Current View](/docs/accessanalyzer/12.0/admin/hostmanagement/actions/saveview.md) option in the Activities pane or right-click menu. Do this +at the Host Management node with the Host Master Table or at any host list node. See the [Filter](/docs/accessanalyzer/12.0/admin/navigate/datagrid.md#filter) topic for additional information on filtering data grids. :::info -Do not modify the criteria once a dynamic based list has been created. It is -better to delete and recreate the list in order to modify a dynamic-based list. +Don't modify the criteria after you create a dynamic-based list. Instead, delete and recreate the +list. ::: ## Static Host Lists -Static host lists are created either through host discovery queries or manually entered within the -**Host Management** node. Lists created by [Host Discovery Node](/docs/accessanalyzer/12.0/admin/hostdiscovery/overview.md) -queries are updated each time the query is run, manually or scheduled. Other static host lists can -only be changed manually. Custom host lists are frequently created in order to scope a job to +Access Analyzer creates static host lists automatically through host discovery queries, or you can +create them manually within the **Host Management** node. +[Host Discovery Node](/docs/accessanalyzer/12.0/admin/hostdiscovery/overview.md) queries create these +lists and update them each time you run the query, manually or on a schedule. You can only change +other static host lists manually. You frequently create custom host lists to scope a job to execute against a select set of hosts. For example, a user running the Exchange Solution might create a list to just run Mailbox queries -against. Whereas a user running the File System Solution might create a list of servers being used +against. Whereas a user running the File System Solution might create a list of servers used for file shares. There are two common ways to create static host lists: - Use the [Add Hosts](/docs/accessanalyzer/12.0/admin/hostmanagement/actions/add.md) option in the Activities pane or right-click menu to access the Host List Wizard -- Select multiple hosts from the data grid using the Windows Ctrl and left-click function. This can - be done from the Host Mast Table or any host list under the Host Management node. Then use the +- Select multiple hosts from the data grid using the Windows Ctrl and left-click function. You can + do this from the Host Mast Table or any host list under the Host Management node. Then use the [Save Selected To List](/docs/accessanalyzer/12.0/admin/hostmanagement/actions/savetolist.md) option in the Activities pane or right-click menu to open the Host List Wizard with a pre-filled in Manual Host Entry page. diff --git a/docs/accessanalyzer/12.0/admin/hostmanagement/overview.md b/docs/accessanalyzer/12.0/admin/hostmanagement/overview.md index 263d84cc9f..f8c181f45e 100644 --- a/docs/accessanalyzer/12.0/admin/hostmanagement/overview.md +++ b/docs/accessanalyzer/12.0/admin/hostmanagement/overview.md @@ -6,8 +6,8 @@ sidebar_position: 30 # Host Management -The **Host Management** node is used to manage hosts in a targeted environment. Hosts configured -under the **Host Management** node can be audited using other features in Access Analyzer. This node +Use the **Host Management** node to manage hosts in a targeted environment. You can audit hosts +configured under the **Host Management** node using other features in Access Analyzer. This node maintains information for audited computers. To view information on all computers in the environment, use the [.Active Directory Inventory Solution](/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/overview.md), @@ -15,7 +15,7 @@ specifically the Active Directory Summary report. The Host Management node provides a master list of every host ever introduced to Access Analyzer. Introduce hosts through [Host Discovery Node](/docs/accessanalyzer/12.0/admin/hostdiscovery/overview.md) queries or by entering -them manually. Hosts are removed from this list only by manually deleting them. This master listing +them manually. You can only remove hosts from this list by manually deleting them. This master listing of hosts, or the Host Master Table, is designed around unique host names, not necessarily unique hosts themselves. The data grid provides all host inventory information collected on the hosts. See the [Host Inventory Data Grid](/docs/accessanalyzer/12.0/admin/hostmanagement/datagrid.md) topic for additional information. @@ -23,7 +23,7 @@ the [Host Inventory Data Grid](/docs/accessanalyzer/12.0/admin/hostmanagement/da The Host Management process consists of the following phases: - Host Discovery – The process of discovering hosts to audit through Host Discovery queries, which - can be scoped to identify computers with commonalities. These queries are managed under the Host + you can scope to identify computers with commonalities. You manage these queries under the Host Discovery node. See the [Host Discovery Node](/docs/accessanalyzer/12.0/admin/hostdiscovery/overview.md) topic for additional information. - Host Inventory – The process of collecting key pieces of information about each host to aid in diff --git a/docs/accessanalyzer/12.0/admin/jobs/features.md b/docs/accessanalyzer/12.0/admin/jobs/features.md index 96d93aa710..31d07f2291 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/features.md +++ b/docs/accessanalyzer/12.0/admin/jobs/features.md @@ -6,13 +6,13 @@ sidebar_position: 40 # Special Features & Functions -There are several special features and functions available for jobs and job components with which -Access Analyzer users should be familiar. +Access Analyzer users should be familiar with several special features and functions available for +jobs and job components. **View XML Files** -Job, query, analysis, and action property windows all have the **View XML** option. These provide -the ability to edit through an XML text window. +Job, query, analysis, and action property windows all have the **View XML** option. These let you +edit through an XML text window. **Open Explore Folder** @@ -21,19 +21,19 @@ the **Explore Folder** option in the right-click menu. **Publish Reports after Report Generation** -Reports that have been generated but not published can be sent to the Web Console using the +You can send generated but unpublished reports to the Web Console by using the **Publish** option in the right-click menu from the selected Jobs tree, job group, or job node. See the [Publish Reports Window](#publish-reports-window) topic for additional information. **Job Configuration Change Tracking** -Jobs configuration changes can be tracked using the **Changes** option in the right-click menu from +You can track job configuration changes using the **Changes** option in the right-click menu from the selected Jobs tree, job group, or job node. See the [Changes Window](/docs/accessanalyzer/12.0/admin/jobs/overview.md#changes-window) topic for additional information. **Job Export** -Jobs can be exported to a ZIP file using the **Export** option in the right-click menu from the +You can export jobs to a ZIP file using the **Export** option in the right-click menu from the selected job group or job node. See the [Export Job to Zip Archive Window](#export-job-to-zip-archive-window) topic for additional information. @@ -60,33 +60,33 @@ There are two options for where to save the ZIP file: - Save in the exported folder – Saves the file in the job’s directory, for example `%sainstalldir%Jobs\GROUP_.Active Directory Inventory\.Active Directory Inventory.zip` -- Save in the following location – Allows you to either type or browse to the desired save location +- Save in the following location – Type or browse to the save location you want -The **Email this archive**checkbox provides the opportunity to send an email notification with the +The **Email this archive** checkbox lets you send an email notification with the attached ZIP file. ![Support Email window](/images/accessanalyzer/12.0/admin/jobs/supportemail.webp) -When the archive has been created, the Access Analyzer Support Email window opens. By default, the -recipient is set to [Netwrix Support](https://www.netwrix.com/support.html) but it can be modified -prior to sending. Additional recipients can be added, and the Subject and email body can be -modified. +After Access Analyzer creates the archive, the Support Email window opens. By default, Access +Analyzer sets the recipient to [Netwrix Support](https://www.netwrix.com/support.html), but you can +change it before sending. You can also add additional recipients and modify the Subject and email +body. ## Publish Reports Window -The **Publish Reports** wizard allows you to better manage the list of reports published to the Web +Use the **Publish Reports** wizard to better manage the list of reports published to the Web Console. -When you right-click on a job group or job and select **Publish**, the Publish Reports wizard opens. -You can choose the list of reports to be published or removed from the Web Console. +When you right-click a job group or job and select **Publish**, the Publish Reports wizard opens. +You can choose which reports to publish or remove from the Web Console. -Follow the steps to publish the reports. +To publish the reports: -**Step 1 –** Right-click on a job group or job and select **Publish** from the drop-down list. +**Step 1 –** Right-click a job group or job and select **Publish** from the dropdown list. ![Publish Reports wizard Action Type page](/images/accessanalyzer/12.0/admin/jobs/publishreportsactiontype.webp) -**Step 2 –** On the Action Type page, select the type of action to be performed on the reports and +**Step 2 –** On the Action Type page, select the type of action to perform on the reports and click **Next**: - Publish Reports @@ -94,11 +94,11 @@ click **Next**: ![Publish Reports wizard Report Tree page](/images/accessanalyzer/12.0/admin/jobs/publishreportsreporttree.webp) -**Step 3 –** On the Report Tree page, select the reports to be published or removed (depending on -the Action Type selected in the previous step). Click **Next** to proceed with the action. +**Step 3 –** On the Report Tree page, select the reports to publish or remove (depending on +the Action Type you selected in the previous step). Click **Next** to proceed with the action. **Step 4 –** The Progress page shows you the status of the action. When it has completed, click **Finish** to exit the wizard. -Published reports can be viewed under the **[Job]** > **Results** node or through the Web Console. +You can view published reports under the **[Job]** > **Results** node or through the Web Console. See the [Reporting](/docs/accessanalyzer/12.0/admin/report/overview.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/admin/jobs/group/overview.md b/docs/accessanalyzer/12.0/admin/jobs/group/overview.md index 1e2de34053..80f8664fee 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/group/overview.md +++ b/docs/accessanalyzer/12.0/admin/jobs/group/overview.md @@ -6,18 +6,18 @@ sidebar_position: 10 # Job Groups -Job groups are designed to manage related jobs and can contain sub-job groups to ensure that related -jobs are executed in the correct order. To create a new job group, right-click on the desired +Job groups manage related jobs and can contain sub-job groups to ensure related +jobs execute in the correct order. To create a new job group, right-click the desired location (Jobs tree or another job group) and select **Create Group**. Then provide a unique, descriptive name taking into consideration the alphanumeric ordering of the Jobs tree. ![Example of Job Group Structure](/images/accessanalyzer/12.0/admin/jobs/group/jobgroupstructure.webp) -Job groups are organized similar to the Jobs tree, with the Settings node at the top, followed by -sub-job groups (job group for collection first, if applicable), then followed by analysis and -reporting jobs. Both are sorted in alphanumeric order. This is necessary because data collection -jobs must run prior to the analysis and reporting jobs that rely on the collected data without -consideration to the job’s name (alphanumeric order). +Access Analyzer organizes job groups similar to the Jobs tree, with the Settings node at the top, +followed by sub-job groups (job group for collection first, if applicable), then followed by +analysis and reporting jobs. It sorts both in alphanumeric order. This is necessary because data +collection jobs must run before the analysis and reporting jobs that rely on the collected data, +regardless of alphanumeric naming order. ## Job Group Description Page @@ -43,13 +43,13 @@ Job Library, and creating a job. Pre-configured job group description pages provide users with shortcuts and links to many of the -functions that can be accessed in the Jobs Tree in the Navigation Pane. +functions available in the Jobs Tree in the Navigation Pane. ![Job Group Description page](/images/accessanalyzer/12.0/admin/jobs/group/descriptionpage.webp) The sections of the job group description page are: -- Job Group Settings Shortcuts – These pages can also be accessed through the job group Settings +- Job Group Settings Shortcuts – You can also access these pages through the job group Settings Nodes in the Navigation Pane. See the [Job Groups Settings Node](/docs/accessanalyzer/12.0/admin/jobs/group/settings/settings.md) topic for additional information. @@ -61,11 +61,11 @@ The sections of the job group description page are: - Help – Opens the [Netwrix Technical Knowledge Center](https://helpcenter.netwrix.com/) in a browser to a relevant landing page for the job group -- Run Now – Runs the currently selected job group +- Run Now – Runs the selected job group - Schedule – Opens the Schedule page to schedule the job group - Open Folder – Opens the job group’s folder location with supporting files in the Windows Explorer -- Create Group – Creates a job group within the currently selected job group -- Create Job – Creates a job within the currently selected Job +- Create Group – Creates a job group within the selected job group +- Create Job – Creates a job within the selected Job - Add Instant Job – Add an Instant Job using the Instant Job Wizard. See the [Instant Job Wizard](/docs/accessanalyzer/12.0/admin/jobs/instantjobs/overview.md) topic for additional information. @@ -75,12 +75,12 @@ The Overview section provides summary information about the job group. This sect following information: - Assigned Host List – Hovering over the **Assigned Host List** button shows a tool-tip with - information on the hosts lists are assigned to the job group + information on which host lists you've assigned to the job group - - Click on the **Assigned Host List** button to go to the Job Group's Host List Assignment node. + - Click the **Assigned Host List** button to go to the Job Group's Host List Assignment node. See the [Host Lists Assignment](/docs/accessanalyzer/12.0/admin/jobs/group/settings/hostlistsassignment.md) topic for additional information. -- Show Inherited Settings – Click on the **Show Inherited Settings** button to view information on +- Show Inherited Settings – Click the **Show Inherited Settings** button to view information on the following: - Connection Profile @@ -89,18 +89,18 @@ following information: - Reporting Settings - Storage Account -- Contents – Shows the job groups and jobs contained within the currently selected job group +- Contents – Shows the job groups and jobs contained within the selected job group :::note -If applicable, the page shows special instructions for which hosts need to be targeted for +If applicable, the page shows special instructions for which hosts you need to target for proper job group execution. ::: ### Job Settings: Inherited and Directly Applied -Job group settings can be applied directly or inherited. On the job group level, it is considered -that all settings are applied directly. +Job group settings can be applied directly or inherited. At the job group level, all settings apply +directly. ![Show Inherited Settings on Job Overview page](/images/accessanalyzer/12.0/admin/jobs/group/showinheritedsettings.webp) diff --git a/docs/accessanalyzer/12.0/admin/jobs/group/settings/connection.md b/docs/accessanalyzer/12.0/admin/jobs/group/settings/connection.md index d67a6d9e8e..8587f2002e 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/group/settings/connection.md +++ b/docs/accessanalyzer/12.0/admin/jobs/group/settings/connection.md @@ -7,28 +7,27 @@ sidebar_position: 10 # Connection Node At the job group level, the **Connection** node identifies the Connection Profile assigned for the -job group. All Connection Profiles are created at the global level (**Settings** > **Connection**). +job group. You create all Connection Profiles at the global level (**Settings** > **Connection**). ![Job Group Connection Settings](/images/accessanalyzer/12.0/admin/jobs/group/connection.webp) -By default, all job groups are set to inherit the **Use Default Profile** option from the global -level or a parent job group. See the [Connection](/docs/accessanalyzer/12.0/admin/settings/connection/overview.md) topic for +By default, Access Analyzer sets all job groups to inherit the **Use Default Profile** option from +the global level or a parent job group. See the [Connection](/docs/accessanalyzer/12.0/admin/settings/connection/overview.md) topic for additional information. -If the Default Setting is not preferred, select the custom type of connection settings desired -below: +If you don't prefer the Default Setting, select one of the following custom connection settings: - System default - - For manual or ad hoc job execution, the account logged into the Access Analyzer Console is - applied to the target hosts for authentication - - For scheduled job execution, the account supplied as the Schedule Service account at the - **Settings** > **Schedule** node is applied to the target hosts for authentication + - For manual or ad hoc job execution, Access Analyzer applies the account logged into the + Access Analyzer Console to the target hosts for authentication + - For scheduled job execution, Access Analyzer applies the account supplied as the Schedule + Service account at the **Settings** > **Schedule** node to the target hosts for authentication - Select one of the following user defined profiles - - Select a pre-configured Connection Profile from the drop-down menu + - Select a pre-configured Connection Profile from the dropdown menu Selecting the **Set all the child objects to inherit these settings** option forces inheritance of -this setting to all sub-groups and jobs within the job group. When enabled, this option overrides -any custom settings configured for the child objects. +this setting to all sub-groups and jobs within the job group. When you enable this option, it +overrides any custom settings configured for the child objects. diff --git a/docs/accessanalyzer/12.0/admin/jobs/group/settings/history.md b/docs/accessanalyzer/12.0/admin/jobs/group/settings/history.md index a175e5b956..a73a1dca4d 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/group/settings/history.md +++ b/docs/accessanalyzer/12.0/admin/jobs/group/settings/history.md @@ -11,17 +11,17 @@ assigned for the job group. ![Job Group History Settings](/images/accessanalyzer/12.0/admin/jobs/group/history.webp) -By default, all job groups are set to inherit **Use Default Setting** option from the global level -(**Settings** > **History**) or a parent job group. See the [History](/docs/accessanalyzer/12.0/admin/settings/history.md) +By default, Access Analyzer sets all job groups to inherit the **Use Default Setting** option from +the global level (**Settings** > **History**) or a parent job group. See the [History](/docs/accessanalyzer/12.0/admin/settings/history.md) topic for additional information. :::warning -It is important to understand that some pre-configured jobs require history retention -while others do not support it. See job group and job descriptions for additional information. +Some pre-configured jobs require history retention +while others don't support it. See job group and job descriptions for additional information. ::: -If the Default Setting is not preferred, select the custom type of retention settings desired below: +If you don't prefer the Default Setting, select one of the following custom retention settings: - Data Retention Period @@ -34,5 +34,5 @@ If the Default Setting is not preferred, select the custom type of retention set - Retain previous job logs for [number] [time period] Selecting the **Set all the child objects to inherit these settings** option forces inheritance of -this setting to all sub-groups and jobs within the job group. When enabled, this option overrides -any custom settings configured for the child objects. +this setting to all sub-groups and jobs within the job group. When you enable this option, it +overrides any custom settings configured for the child objects. diff --git a/docs/accessanalyzer/12.0/admin/jobs/group/settings/hostlistsassignment.md b/docs/accessanalyzer/12.0/admin/jobs/group/settings/hostlistsassignment.md index dcc26f9b1b..3bf26f3ee4 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/group/settings/hostlistsassignment.md +++ b/docs/accessanalyzer/12.0/admin/jobs/group/settings/hostlistsassignment.md @@ -11,21 +11,21 @@ job group. ![Job Group Host Lists Assignment](/images/accessanalyzer/12.0/admin/jobs/group/hostlistassignment.webp) -At a top-level job group, there is no host list to be inherited. The **Use Default Settings** option -is grayed-out. However, a sub-job group can inherit host lists from a parent job group. Host lists -are configured through the **Host Management** node. See the +At a top-level job group, there's no host list to inherit. The **Use Default Settings** option +is grayed-out. However, a sub-job group can inherit host lists from a parent job group. You configure +host lists through the **Host Management** node. See the [Host Management](/docs/accessanalyzer/12.0/admin/hostmanagement/overview.md) topic for additional information. Several pre-defined solutions have default host lists already assigned to the solution, for example the .Active Directory Inventory Job Group has the Default domain controller assigned at the job group and inherited to the jobs. -Select the host lists to be targeted by the job group. The **Filter host lists by** feature scopes -the list to match the search string provided. At the bottom of the list is an indicator of how many -hosts lists have been selected out of the total number of hosts lists known to the Access Analyzer -Console. If a filter has been applied, there is also an indicator of how many host lists matched the +Select the host lists to target with the job group. The **Filter host lists by** feature scopes +the list to match the search string provided. At the bottom of the list, an indicator shows how many +host lists you've selected out of the total number of host lists known to the Access Analyzer +Console. If you've applied a filter, an indicator also shows how many host lists matched the search string. Selecting the **Set all the child objects to inherit these settings** option forces inheritance of -this setting to all sub-groups and jobs within the job group. When enabled, this option overrides -any custom settings configured for the child objects. +this setting to all sub-groups and jobs within the job group. When you enable this option, it +overrides any custom settings configured for the child objects. diff --git a/docs/accessanalyzer/12.0/admin/jobs/group/settings/reporting.md b/docs/accessanalyzer/12.0/admin/jobs/group/settings/reporting.md index bac3782a45..76693487a0 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/group/settings/reporting.md +++ b/docs/accessanalyzer/12.0/admin/jobs/group/settings/reporting.md @@ -7,23 +7,23 @@ sidebar_position: 40 # Reporting Node At the job group level, the **Reporting** node identifies the report publishing and email -configurations assigned for the job group. By default, all job groups are set to inherit the -reporting settings, the **Use default setting** option, from the global level (**Settings** > -**Reporting**), or a parent job group. See the [Reporting](/docs/accessanalyzer/12.0/admin/settings/reporting.md) topic for +configurations assigned for the job group. By default, Access Analyzer sets all job groups to +inherit the reporting settings, the **Use default setting** option, from the global level +(**Settings** > **Reporting**), or a parent job group. See the [Reporting](/docs/accessanalyzer/12.0/admin/settings/reporting.md) topic for additional information. :::note -If the Role Based Access feature is enabled, it also displays a list of all accounts -granted access to the published reports via the Web Console that are generated by any jobs within -the job group. +If you enable the Role Based Access feature, it also displays a list of all accounts +granted access, via the Web Console, to the published reports that jobs within the job group +generate. ::: ![Job Group Reporting Settings page](/images/accessanalyzer/12.0/admin/jobs/group/reporting.webp) Checking the **Set all the child objects to inherit these settings** option at the bottom of the -page forces inheritance of these settings to all sub-groups and jobs within the job group. When -enabled, this option overrides any custom settings configured for the child objects. +page forces inheritance of these settings to all sub-groups and jobs within the job group. When you +enable this option, it overrides any custom settings configured for the child objects. :::note The **Set all the child objects to inherit these settings** option has no impact on the diff --git a/docs/accessanalyzer/12.0/admin/jobs/group/settings/settings.md b/docs/accessanalyzer/12.0/admin/jobs/group/settings/settings.md index 5efc549bcb..38824429b2 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/group/settings/settings.md +++ b/docs/accessanalyzer/12.0/admin/jobs/group/settings/settings.md @@ -6,12 +6,12 @@ sidebar_position: 10 # Job Groups Settings Node -A job group’s Settings node is where custom configurations can be set and where the host lists are -assigned to a job group. +A job group’s Settings node is where you set custom configurations and assign host lists to a job +group. ![Job group settings in the Jobs Tree](/images/accessanalyzer/12.0/admin/jobs/group/settings.webp) -These settings inherit the global settings down by default unless inheritance is broken at a job +These settings inherit the global settings down by default unless you break inheritance at a job group or a job level. - [Connection Node](/docs/accessanalyzer/12.0/admin/jobs/group/settings/connection.md) – Use the default Connection Profile or break inheritance to @@ -22,7 +22,7 @@ group or a job level. job group or break inheritance on assigned host lists for this job group :::note - Host List Assignments is not a global setting. The pre-configured solutions may + Host List Assignments isn't a global setting. The pre-configured solutions may contain Host List Assignments configured to use Global Default Host Lists, for example All Domain Controllers. See the [Default Host Lists](/docs/accessanalyzer/12.0/admin/settings/hostinventory.md#default-host-lists) topic for additional @@ -33,15 +33,15 @@ group or a job level. - [Reporting Node](/docs/accessanalyzer/12.0/admin/jobs/group/settings/reporting.md) – Use the default report settings or break inheritance on Published Report settings, Email settings, and Report role assignment for this job group - [Storage Node](/docs/accessanalyzer/12.0/admin/jobs/group/settings/storage.md) – Use the default storage profile or break inheritance on where this - job group's data is stored + job group stores its data -If changes are made, click **Save** to implement the changes. Changes are not implemented unless -they are saved. +If you make changes, click **Save** to implement them. Access Analyzer doesn't implement changes +unless you save them. -**Host List Assignment** and **Connection** are the two settings that should always be confirmed +**Host List Assignment** and **Connection** are the two settings you should always confirm before executing a job group or job when data collection is included. The assigned host lists -contains the hosts that are targeted by the job’s data collection queries. The assigned Connection +contain the hosts that the job’s data collection queries target. The assigned Connection Profile must have the appropriate level of permissions in order for the data collection to be successful. See the [Permissions by Data Collector (Matrix)](/docs/accessanalyzer/12.0/admin/datacollector/permissionmatrix.md) topic for -information on the recommended permissions needed on the targeted hosts in order to collect data. +information on the recommended permissions needed on the targeted hosts to collect data. diff --git a/docs/accessanalyzer/12.0/admin/jobs/group/settings/storage.md b/docs/accessanalyzer/12.0/admin/jobs/group/settings/storage.md index 2a7634cc98..bbfe3f835d 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/group/settings/storage.md +++ b/docs/accessanalyzer/12.0/admin/jobs/group/settings/storage.md @@ -7,16 +7,16 @@ sidebar_position: 50 # Storage Node At the job group level, the Storage node identifies the Storage Profile assigned for the job group. -All Storage Profiles are created at the global level (**Settings** > **Storage**). See the +You create all Storage Profiles at the global level (**Settings** > **Storage**). See the [Storage](/docs/accessanalyzer/12.0/admin/settings/storage/overview.md) topic for additional information. ![Job Group Storage Settings](/images/accessanalyzer/12.0/admin/jobs/group/storage.webp) -By default, all job groups are set to inherit the **Use Default Profile** option from the global -level or a parent job group. If it is necessary for a job group to send data to a different +By default, Access Analyzer sets all job groups to inherit the **Use Default Profile** option from +the global level or a parent job group. If a job group needs to send data to a different database, the Storage Profile must already exist at the global level. Select the **Use This -Profile** radio button and choose the non-default Storage Profile from the drop-down menu. +Profile** radio button and choose the non-default Storage Profile from the dropdown menu. Selecting the **Set all the child objects to inherit these settings** option forces inheritance of -this setting to all sub-groups and jobs within the job group. When enabled, this option overrides -any custom settings configured for the child objects. +this setting to all sub-groups and jobs within the job group. When you enable this option, it +overrides any custom settings configured for the child objects. diff --git a/docs/accessanalyzer/12.0/admin/jobs/instantiate.md b/docs/accessanalyzer/12.0/admin/jobs/instantiate.md index 68b0231ff9..3bf0d2283b 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/instantiate.md +++ b/docs/accessanalyzer/12.0/admin/jobs/instantiate.md @@ -24,12 +24,12 @@ prefix for all job groups. `JOB_` is the prefix for all jobs. Changing the prefi from the Jobs tree without deleting it. Instantiating new, external jobs is as easy as copying and pasting the job or job group into this -location. However, copying an existing job within the Jobs directory is not supported. If the job +location. However, copying an existing job within the Jobs directory isn't supported. If the job already exists within the Access Analyzer Console server, copying outside of the console may result in reporting issues. :::warning -Do not use these steps to copy an existing job. +Don't use these steps to copy an existing job. ::: @@ -50,7 +50,7 @@ colleague, or other entity, it is most likely in one of two formats: ![Extract zip file contents to the Jobs folder](/images/accessanalyzer/12.0/admin/jobs/instantiateextract.webp) -- If in archive format, extract the desired content to the Jobs directory +- If in archive format, extract the content you want to the Jobs directory - Use the default path or specify a specific path using the browse button (…) - Select whether to **Show extracted files when complete**. This option is selected by default. @@ -64,7 +64,7 @@ match that of the jobs or job groups that are already there. ![Refresh Tree](/images/accessanalyzer/12.0/admin/jobs/refreshtree.webp) -**Step 4 –** In the Access Analyzer Console, right-click on the **Jobs** node and select **Refresh +**Step 4 –** In the Access Analyzer Console, right-click the **Jobs** node and select **Refresh Tree**. ![Job displayed in the Jobs Tree](/images/accessanalyzer/12.0/admin/jobs/instantiatejobstree.webp) diff --git a/docs/accessanalyzer/12.0/admin/jobs/instantjobs/ad_passwordexpirationnotification.md b/docs/accessanalyzer/12.0/admin/jobs/instantjobs/ad_passwordexpirationnotification.md index 4eb2f67c7b..e9f76e0da1 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/instantjobs/ad_passwordexpirationnotification.md +++ b/docs/accessanalyzer/12.0/admin/jobs/instantjobs/ad_passwordexpirationnotification.md @@ -7,10 +7,10 @@ sidebar_position: 10 # AD_PasswordExpirationNotification Job The AD_PasswordExpirationNotification Job determines when Active Directory user passwords are about -to expire and can be configured to send notifications to users prior to password expiration. It is +to expire and can be configured to send notifications to users before password expiration. It is available through the Instant Job Library under the Active Directory library. See the [Instant Job Wizard](/docs/accessanalyzer/12.0/admin/jobs/instantjobs/overview.md) section for instructions to add this instant job into the Jobs -tree. Since this job does not require a host to target, select Local host on the Hosts page of the +tree. Since this job doesn't require a host to target, select Local host on the Hosts page of the Instant Job Wizard. ![AD_PasswordExpirationNotification job in the Jobs tree](/images/accessanalyzer/12.0/admin/jobs/instantjobs/jobstree_3.webp) @@ -44,7 +44,7 @@ The default analysis tasks are: - Contains a configurable parameter for the number of days until a password expires to be identified - See the - [Customizable Analysis Tasks for the AD_PasswordExpirationNotification Job](#customizable-analysis-tasks-for-the-ad_passwordexpirationnotification-job) + [Customizable Analysis Tasks for the AD_PasswordExpirationNotification Job](#customizable-analysis-tasks-for-the-adpasswordexpirationnotification-job) topic for additional information. - **2. Domain Summary** – Creates an interim processing table in the database for use by downstream analysis and report generation @@ -56,7 +56,7 @@ The default analysis tasks are: the job’s Results node - **5. Help Desk Notification** – Sends notification of users with passwords set to expire in X days - See the - [Notification Analysis Task in the AD_PasswordExpirationNotification Job](#notification-analysis-task-in-the-ad_passwordexpirationnotification-job) + [Notification Analysis Task in the AD_PasswordExpirationNotification Job](#notification-analysis-task-in-the-adpasswordexpirationnotification-job) topic for additional information. ## Action for the AD_PasswordExpirationNotification Job @@ -77,7 +77,7 @@ The default actions are: password expiration - Requires the Notification Actions license feature - See the - [Action Task in the AD_PasswordExpirationNotification Job](#action-task-in-the-ad_passwordexpirationnotification-job) + [Action Task in the AD_PasswordExpirationNotification Job](#action-task-in-the-adpasswordexpirationnotification-job) topic for additional information. In addition to the tables created by the analysis and action tasks, the @@ -92,11 +92,11 @@ AD_PasswordExpirationNotification Job produces the following pre-configured repo Customizable parameters enable Access Analyzer users to set the values used to classify user and group objects during this job’s analysis. The parameters can be customized and are listed in a -section at the bottom of the SQL Script Editor. Follow the steps to customize an analysis task’s -parameters. +section at the bottom of the SQL Script Editor. To customize an analysis task’s +parameters: :::warning -Do not change the table names or report name to align with a different value supplied +Don't change the table names or report name to align with a different value supplied for this parameter. Modifying the table names will result in analysis and report errors downstream. Only the report title and descriptions can be modified within the report configuration. ::: @@ -107,21 +107,21 @@ Only the report title and descriptions can be modified within the report configu | 1. User Password Information | @pswLen | 15 | Number of days left until a password expires, should be set according to an organizations policy. | The parameters that can be customized are listed in a section at the bottom of the SQL Script -Editor. Follow the steps to customize an analysis task’s parameters. +Editor. To customize an analysis task’s parameters: **Step 1 –** Navigate to the **AD_PasswordExpirationNotification** > **Configure** node and select **Analysis** to view the analysis tasks. **Step 2 –** In the Analysis Selection view, select the **1. User Password Information** Analysis -Task and click on **Analysis Configuration**. The SQL Script Editor opens. +Task and click **Analysis Configuration**. The SQL Script Editor opens. ![1. User Password Information Analysis Task in SQL Script Editor](/images/accessanalyzer/12.0/admin/jobs/instantjobs/customizeanalysistask.webp) **Step 3 –** In the parameters section at the bottom of the editor, find the Value column. -Double-click on the current value and change as desired. +Double-click the current value and change as desired. :::warning -Do not change any parameters where the Value states **Created during execution**. +Don't change any parameters where the Value states **Created during execution**. ::: @@ -131,7 +131,7 @@ The new value will be applied to the next job execution. ## Notification Analysis Task in the AD_PasswordExpirationNotification Job -The Notification Analysis Task can be used to send a single email to specified recipients containing +Use the Notification Analysis Task to send a single email to specified recipients containing a list of all users whose passwords will expire in the specified number of days, that is the users listed in the PasswordExpirationNotification_ExpiresWithin15Days table. The analysis is enabled by default. Therefore, when the job is executed the following message is sent to the specified @@ -141,7 +141,7 @@ recipient, such as the organization’s help desk, with information from the ass > > Support Team, > -> Heads-up.  The following users are facing password expiration in seven days or less: +> Heads-up. The following users are facing password expiration in seven days or less: > >**[ -- Password for [User] ([NTAccount]) expires in [DaysUntilExpiration] days]** > @@ -150,22 +150,22 @@ recipient, such as the organization’s help desk, with information from the ass > Netwrix :::warning -Do not modify the tags, highlighted in bold text above. +Don't modify the tags, highlighted in bold text above. ::: The Subject or message body can be modified, for example to replace `Netwrix` with the -organization’s name. Follow the steps to configure the 5. Help Desk Notification Analysis Task. +organization’s name. To configure the 5. Help Desk Notification Analysis Task: **Step 1 –** Navigate to the **AD_PasswordExpirationNotification** > **Configure** node and select **Analysis** to view the Analysis tasks. **Step 2 –** In the Analysis Selection view, select the **5. Help Desk Notification Analysis Task** -and click on **Analysis Configuration**. The Notification Data Analysis Module opens. +and click **Analysis Configuration**. The Notification Data Analysis Module opens. ![SMTP properties page](/images/accessanalyzer/12.0/admin/jobs/instantjobs/smtpproperties.webp) -**Step 3 –** Use the **Next** button to navigate to the SMTP properties page. Do not make changes to +**Step 3 –** Use the **Next** button to navigate to the SMTP properties page. Don't make changes to the preceding pages. The email configuration takes place on the SMTP page. Provide the recipients’ email addresses, Message Subject, and add the notification email content. @@ -187,7 +187,7 @@ In the Message section, the **Subject** should be configured. Then set the email box as desired. **Step 4 –** To save these configuration changes, use the **Next** button to navigate to the Summary -page. Do not make changes to any other pages. Click **Finish**. The Notification Data Analysis +page. Don't make changes to any other pages. Click **Finish**. The Notification Data Analysis Module window closes. ![Analyis Tasks view](/images/accessanalyzer/12.0/admin/jobs/instantjobs/analysistaskshelpdesknotification.webp) @@ -203,7 +203,7 @@ is executed. The 1. User Notification Action Task uses the SendMail Action Module to send users notification of password expiration. It targets the SMTP Address Column of the users whose passwords are going to -expire within the desired number of days, that is the users listed in the +expire within the number of days you set, that is the users listed in the PasswordExpirationNotification_ExpiresWithin15Days_UserNotifications table. The action is enabled by default. Therefore, when the job is executed the following message is sent to all users in the associated table: @@ -212,8 +212,8 @@ associated table: > > Hello **[User]**, > -> The password for the account **[NTAccount]** expires on **[ExpirationDate]**. Please change the -> password prior to the expiration date.  If account profiles are used on mobile devices, please +> The password for the account **[NTAccount]** expires on **[ExpirationDate]**. Change the +> password before the expiration date. If account profiles are used on mobile devices, > remember to update the password on each device used. > > Thank you, @@ -221,14 +221,14 @@ associated table: > Netwrix :::warning -Do not change the recipient for the action task. While the tags can be moved, do not +Don't change the recipient for the action task. While the tags can be moved, don't remove or modify the tags, which are highlighted in bold text above. ::: The subject or message body can be modified, for example to replace `Netwrix` with the -organization’s name. Follow the steps to modify the Subject or message body within the 1. User -Notification Action Task. +organization’s name. To modify the Subject or message body within the 1. User +Notification Action Task: :::note It is necessary for the @@ -244,7 +244,7 @@ before this action task can be modified. on **Action Properties** to view the actions. :::warning -Do not modify the action task properties. +Don't modify the action task properties. ::: diff --git a/docs/accessanalyzer/12.0/admin/jobs/instantjobs/ex_registerazureappauth.md b/docs/accessanalyzer/12.0/admin/jobs/instantjobs/ex_registerazureappauth.md index adda8b9628..59d41146cd 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/instantjobs/ex_registerazureappauth.md +++ b/docs/accessanalyzer/12.0/admin/jobs/instantjobs/ex_registerazureappauth.md @@ -22,7 +22,7 @@ authentication and provision appropriate permissions for Exchange Online scans. - Azure AD PowerShell module installed on targeted hosts :::note - If the module is not already installed, the job will attempt to install it. + If the module isn't already installed, the job will attempt to install it. ::: @@ -49,7 +49,7 @@ authentication and provision appropriate permissions for Exchange Online scans. ## Using the EX_RegisterAzureAppAuth Job -Follow the steps to configure and run the EX_RegisterAzureAppAuth Job. +To configure and run the EX_RegisterAzureAppAuth Job: **Step 1 –** In Access Analyzer navigate to the Exchange Job Group (or any other Job Group you wish to place the EX_RegistureAzureApp job into). @@ -72,7 +72,7 @@ use for the Microsoft Entra ID application. Click **Save**. **Step 6 –** (Optional) For non-standard tenant types, edit the **Azure Environment Name...** option to provide the full environment name. For a standard tenant, leave this option blank. -- For example, if leveraging a government (or GCC) tenant, enter **AzureGovernment** +- For example, if using a government (or GCC) tenant, enter **AzureGovernment** - Additional options include: AzureChinaCloud, AzureCloud, AzureGermanyCloud, AzurePPE, AzureGovernment2, and AzureGovernment3 @@ -86,9 +86,9 @@ The job is now ready to be run. Log-in as a Global Administrator, and grant administrator consent to the Application's configured API Permissions. -- If this login attempt fails or you close the browser, you will need to login to Microsoft Entra ID +- If this login attempt fails or you close the browser, you will need to log in to Microsoft Entra ID as a Global Administrator and navigate to the Application's API Permissions to grant Admin Consent - before the Application can be used for Exchange scans in Access Analyzer. + before you can use the Application for Exchange scans in Access Analyzer. The Microsoft Entra ID application is now provisioned with the necessary permissions for Exchange Online scans. There will be a new Connection Profile for this Application. Restart the Access diff --git a/docs/accessanalyzer/12.0/admin/jobs/instantjobs/fs_migrateschema.md b/docs/accessanalyzer/12.0/admin/jobs/instantjobs/fs_migrateschema.md index 309f54c69c..21d267ce7a 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/instantjobs/fs_migrateschema.md +++ b/docs/accessanalyzer/12.0/admin/jobs/instantjobs/fs_migrateschema.md @@ -6,7 +6,7 @@ sidebar_position: 40 # FS_MigrateSchema Job -The FS_Migrate_Schema Job migrates the schema in order to support the use of 64-bit ResourceID's +The FS_Migrate_Schema Job migrates the schema to support the use of 64-bit ResourceID's without affecting data. It is available through the Instant Job Library under the File System library. See the [Instant Job Wizard](/docs/accessanalyzer/12.0/admin/jobs/instantjobs/overview.md) topic for instructions to add this instant job into the Jobs tree. @@ -24,7 +24,7 @@ Runtime Details: - Multi-console Support – Not supported - Additional Notes – None -The FS_Migrate Schema Job migrates the schema in order to support the use of 64-bit ResourceID's +The FS_Migrate Schema Job migrates the schema to support the use of 64-bit ResourceID's without affecting data. ## Analysis Tasks for the FS_MigrateSchema Job @@ -33,7 +33,7 @@ Navigate to the **Jobs** > **FS_MigrateSchema** > **Configure** node and select the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -42,23 +42,23 @@ preconfigured for this job. The default analysis tasks are: -- 1.Migrate Resources – Migrates the SA_FSAA_Resources table to leverage 64-bit IDs -- 2.Migrate UnixRights – Migrates the SA_FSAA_UnixRights table to leverage 64-bit IDs -- 3.Migrate Gates – Migrates the SA_Gates table to leverage 64-bit IDs -- 4.Migrate GatesProxy – Migrates the SA_FSAA_GatesProxy table to leverage 64-bit IDs -- 5.Migrate Exceptions – Migrates the SA_FSAA_Exceptions table to leverage 64-bit IDs -- 6.Migrate ProbableOwners – Migrates the SA_FSAA_ProbableOwners table to leverage 64-bit IDs -- 7.Migrate FileSizes – Migrates the SA_FSAA_FileSizes table to leverage 64-bit IDs -- 8.Migrate FileTypes – Migrates the SA_FSAA_FileTypes table to leverage 64-bit IDs -- 9.Migrate FileAges – Migrates the SA_FSAA_FileAges table to leverage 64-bit IDs -- 10.Migrate FileTags – Migrates the SA_FSAA_FileTags table to leverage 64-bit IDs -- 11.Migrate DFS Links – Migrates the SA_FSDFS_Links table to leverage 64-bit IDs -- 12.Migrate DLP Matches – Migrates the SA_FSDLP_Matches table to leverage 64-bit IDs -- 13.Migrate DLP MatchHits – Migrates the SA_FSDLP_MatchHits table to leverage 64-bit IDs +- 1.Migrate Resources – Migrates the SA_FSAA_Resources table to use 64-bit IDs +- 2.Migrate UnixRights – Migrates the SA_FSAA_UnixRights table to use 64-bit IDs +- 3.Migrate Gates – Migrates the SA_Gates table to use 64-bit IDs +- 4.Migrate GatesProxy – Migrates the SA_FSAA_GatesProxy table to use 64-bit IDs +- 5.Migrate Exceptions – Migrates the SA_FSAA_Exceptions table to use 64-bit IDs +- 6.Migrate ProbableOwners – Migrates the SA_FSAA_ProbableOwners table to use 64-bit IDs +- 7.Migrate FileSizes – Migrates the SA_FSAA_FileSizes table to use 64-bit IDs +- 8.Migrate FileTypes – Migrates the SA_FSAA_FileTypes table to use 64-bit IDs +- 9.Migrate FileAges – Migrates the SA_FSAA_FileAges table to use 64-bit IDs +- 10.Migrate FileTags – Migrates the SA_FSAA_FileTags table to use 64-bit IDs +- 11.Migrate DFS Links – Migrates the SA_FSDFS_Links table to use 64-bit IDs +- 12.Migrate DLP Matches – Migrates the SA_FSDLP_Matches table to use 64-bit IDs +- 13.Migrate DLP MatchHits – Migrates the SA_FSDLP_MatchHits table to use 64-bit IDs - 14.Migrate DLP MatchHits Subject Profile – Migrates the SA_FSDLP_MatchHits_SubjectProfile table to - leverage 64-bit IDs -- 15.Migrate FSAC ActivityEvents – Migrates the SA_FSAC_ActivityEvents table to leverage 64-bit IDs -- 16.Migrate DailyActivity – Migrates the SA_FSAC_DailyActivity table to leverage 64-bit IDs -- 17.Migrate FSAC RenameTargets – Migrates the SA_FSAC_RenameTargets table to leverage 64-bit IDs -- 18.Migrate FSAC Exceptions – Migrates the SA_FSAC_Exceptions table to leverage 64-bit IDs + use 64-bit IDs +- 15.Migrate FSAC ActivityEvents – Migrates the SA_FSAC_ActivityEvents table to use 64-bit IDs +- 16.Migrate DailyActivity – Migrates the SA_FSAC_DailyActivity table to use 64-bit IDs +- 17.Migrate FSAC RenameTargets – Migrates the SA_FSAC_RenameTargets table to use 64-bit IDs +- 18.Migrate FSAC Exceptions – Migrates the SA_FSAC_Exceptions table to use 64-bit IDs - 19.Refresh Views – Updates viewable metadata diff --git a/docs/accessanalyzer/12.0/admin/jobs/instantjobs/overview.md b/docs/accessanalyzer/12.0/admin/jobs/instantjobs/overview.md index 9845375b55..40bba6673e 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/instantjobs/overview.md +++ b/docs/accessanalyzer/12.0/admin/jobs/instantjobs/overview.md @@ -12,12 +12,12 @@ solve a wide range of problems within each category. Instant jobs help solve spe instant solutions available align to an organization’s license key. See the[Solutions](/docs/accessanalyzer/12.0/solutions/overview.md) topic for additional information. -Follow the steps to install an instant solution or an instant job with the Instant Job Wizard. +To install an instant solution or an instant job with the Instant Job Wizard: ![Add Instant Job from context menu](/images/accessanalyzer/12.0/admin/jobs/instantjobs/addinstantjob.webp) -**Step 1 –** Select the Jobs tree (for an instant solution) or the desired job group (for an instant -job), right-click on the node, and select **Add Instant Job**. +**Step 1 –** Select the Jobs tree (for an instant solution) or the job group you want (for an instant +job), right-click the node, and select **Add Instant Job**. ![Instant Job Wizard Welcome page](/images/accessanalyzer/12.0/admin/jobs/instantjobs/welcome.webp) @@ -30,12 +30,12 @@ category, or click the plus icon (+) to expand a category group. ![Selected Instant Job](/images/accessanalyzer/12.0/admin/jobs/instantjobs/selectinstantjob.webp) -**Step 4 –** Select the desired instant solution or job. To select multiple instant solutions or +**Step 4 –** Select the instant solution or job you want. To select multiple instant solutions or jobs, press the Windows **Ctrl** key and select the items to install. Click **Next**. ![Host Assignment page](/images/accessanalyzer/12.0/admin/jobs/instantjobs/hostassignment.webp) -**Step 5 –** Some of the Library selections add a Host Assignment page. If this page does not +**Step 5 –** Some of the Library selections add a Host Assignment page. If this page doesn't appear, skip to Step 7. If the page does appear, select either the **Use default settings (Inherit from the parent group, if any)** or **Specify individual hosts or hosts lists** option. If the first option is selected, skip to Step 7. If the second option is selected, click **Next** to go to the @@ -46,7 +46,7 @@ Host Lists and Individual Hosts wizard pages. | *Host Lists page* | *Individual Hosts page* | **Step 6 –** Some of the Library selections add a Host Lists, and Individual Hosts page. If these -pages do not appear with the selection, skip to Step 7. If the pages do appear, check the host list +pages don't appear with the selection, skip to Step 7. If the pages do appear, check the host list to be assigned to the job group or job. Alternatively enter hosts manually. Then click **Next**. ![Summary page](/images/accessanalyzer/12.0/admin/jobs/instantjobs/summary.webp) diff --git a/docs/accessanalyzer/12.0/admin/jobs/instantjobs/sas_executionstatistics.md b/docs/accessanalyzer/12.0/admin/jobs/instantjobs/sas_executionstatistics.md index a4f062d022..0196cf2c30 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/instantjobs/sas_executionstatistics.md +++ b/docs/accessanalyzer/12.0/admin/jobs/instantjobs/sas_executionstatistics.md @@ -10,7 +10,7 @@ The SAS_ExecutionStatistics Job tracks historical performance of Access Analyzer functions and highlights when a particular task takes an abnormal length of time to execute. It is available through the Instant Job Library under the Access Analyzer Utilities library. See the [Instant Job Wizard](/docs/accessanalyzer/12.0/admin/jobs/instantjobs/overview.md) section for instructions to add this instant job into the Jobs -tree. Since this job does not require a host to target, select Local host on the Hosts page of the +tree. Since this job doesn't require a host to target, select Local host on the Hosts page of the Instant Job Wizard. The job is dependent upon the Job Statistics Retention configuration in the **Settings** > @@ -39,7 +39,7 @@ Navigate to the **Jobs** > **SAS_ExecutionStatistics** > **Configure** node and to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/admin/jobs/instantjobs/sp_registerazureappauth.md b/docs/accessanalyzer/12.0/admin/jobs/instantjobs/sp_registerazureappauth.md index 868b3201ec..2c91c5ad23 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/instantjobs/sp_registerazureappauth.md +++ b/docs/accessanalyzer/12.0/admin/jobs/instantjobs/sp_registerazureappauth.md @@ -19,10 +19,10 @@ authentication and provision appropriate permissions for SharePoint Online scans ## Instantiate the SP_RegisterAzureAppAuth Job. -Follow the steps to instantiate the SP_RegisterAzureAppAuth Job. +To instantiate the SP_RegisterAzureAppAuth Job: **Step 1 –** In Access Analyzer navigate to the SharePoint Job Group (or any other Job Group you -wish to place the SP_RegistureAzureApp job into). +want to place the SP_RegistureAzureApp job into). **Step 2 –** Click **Add Instant Job** to open the Instant Job Wizard. @@ -41,8 +41,8 @@ application (for example, `myorg.onmicrosoft.com`). Click **Save**. The job is n After the job successfully runs it will open a browser window to Microsoft Entra ID that, when logged-in as a Global Administrator, allows the user to grant administrator consent to the Application's configured API Permissions. If the login attempt fails, or the user closes the -browser, they will need to login to Microsoft Entra ID as a Global Administrator and navigate to the -Application's API Permissions to grant Admin Consent before the Application can be used for +browser, they will need to log in to Microsoft Entra ID as a Global Administrator and navigate to the +Application's API Permissions to grant Admin Consent before you can use the Application for SharePoint scans in Access Analyzer. **Additional Considerations** diff --git a/docs/accessanalyzer/12.0/admin/jobs/instantjobs/sp_removehost.md b/docs/accessanalyzer/12.0/admin/jobs/instantjobs/sp_removehost.md index 025bf16c85..4867ddd9d1 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/instantjobs/sp_removehost.md +++ b/docs/accessanalyzer/12.0/admin/jobs/instantjobs/sp_removehost.md @@ -30,7 +30,7 @@ Navigate to the **Jobs** > **SP_RemoveHost** > **Configure** node and select **A the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -39,4 +39,4 @@ preconfigured for this job. The default analysis tasks are: -- Remove Host(s) — Remove Scanned Hosts from Tier 1 +- Remove Hosts — Remove Scanned Hosts from Tier 1 diff --git a/docs/accessanalyzer/12.0/admin/jobs/job/configure/actions.md b/docs/accessanalyzer/12.0/admin/jobs/job/configure/actions.md index 4586caaa82..a388902750 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/job/configure/actions.md +++ b/docs/accessanalyzer/12.0/admin/jobs/job/configure/actions.md @@ -49,7 +49,7 @@ The Actions section at the top has five options: - Execute Action – Opens the Action Execution window and starts executing the selected action - - Does not require an action task to be checked, only selected + - Doesn't require an action task to be checked, only selected ![Buttons at the bottom of Action Selection page](/images/accessanalyzer/12.0/admin/jobs/job/configure/actionselectiontablebuttons.webp) diff --git a/docs/accessanalyzer/12.0/admin/jobs/job/configure/analysis/analysiscustomizableparameters.md b/docs/accessanalyzer/12.0/admin/jobs/job/configure/analysis/analysiscustomizableparameters.md index bee592a9bf..5d4840920d 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/job/configure/analysis/analysiscustomizableparameters.md +++ b/docs/accessanalyzer/12.0/admin/jobs/job/configure/analysis/analysiscustomizableparameters.md @@ -7,11 +7,11 @@ sidebar_position: 10 # Configure the Customizable Parameters in an Analysis Task The parameters that can be customized and are listed in a section at the bottom of the SQL Script -Editor. Follow the steps to customize an analysis task’s parameters. +Editor. To customize an analysis task’s parameters: **Step 1 –** Navigate to the Job’s **Configure** node and select **Analysis**. -**Step 2 –** In the Analysis Selection view, select the desired analysis task and click **Analysis +**Step 2 –** In the Analysis Selection view, select the analysis task you want and click **Analysis Configuration**. The SQL Script Editor opens. **Step 3 –** At the top of the SQL Script Editor, select **Parameters**. @@ -27,11 +27,11 @@ based on the Job. **Step 4 –** In the parameters section at the bottom of the editor, find the Value column. :::warning -Do not change any parameters where the Value states **Created during execution**. +Don't change any parameters where the Value states **Created during execution**. ::: -- Double-click on the customizable value and change as desired +- Double-click the customizable value and change as desired **Step 5 –** Click **Save and Close** to finalize the customization and close the SQL Script Editor. diff --git a/docs/accessanalyzer/12.0/admin/jobs/job/configure/hosts.md b/docs/accessanalyzer/12.0/admin/jobs/job/configure/hosts.md index 9ab7d66701..b98c4ed22b 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/job/configure/hosts.md +++ b/docs/accessanalyzer/12.0/admin/jobs/job/configure/hosts.md @@ -20,7 +20,7 @@ it triggers a host inventory query according to the global settings. The host wi any individual host lists. See the [Manually Add Hosts to a Job](#manually-add-hosts-to-a-job) topic for additional information. -Click **Save** to apply any changes to the host selection. Changes are not implemented unless they +Click **Save** to apply any changes to the host selection. Changes aren't implemented unless they are saved. ## Manually Add Hosts to a Job diff --git a/docs/accessanalyzer/12.0/admin/jobs/job/configure/queries.md b/docs/accessanalyzer/12.0/admin/jobs/job/configure/queries.md index 2fb899876f..110d1715f0 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/job/configure/queries.md +++ b/docs/accessanalyzer/12.0/admin/jobs/job/configure/queries.md @@ -15,21 +15,21 @@ chart with recommended permissions per data collector. ![Query Selection page](/images/accessanalyzer/12.0/admin/jobs/job/configure/queryselection.webp) -The Query Selection view lists all queries for the selected job. Though it is possible to have -multiple queries in a single job, it is not usually recommended. The listed information includes: +The Query Selection view lists all queries for the selected job. Though a single job can have +multiple queries, it isn't usually recommended. The listed information includes: - Name – Name of the query (as provided by the creator of the query) - Source – Name of the Access Analyzer data collector - Table – Name of the Native Data table -- Enumerates – Whether or not the data collector will return enumerated data, or multiple lines of +- Enumerates – Whether the data collector will return enumerated data, or multiple lines of data per target host - If **Yes**, only one query can write to a single table - If **No**, then multiple related queries can write to a single table - Properties – Number of the properties to be returned - Filters – Number of in-line filters applied to the data being returned by the query -- Script – Whether or not a VB Script was added to the query +- Script – Whether a VB Script was added to the query - If **Yes**, a VB Script was added to query execution - - If **No**, a VB Script was not added to query execution + - If **No**, a VB Script wasn't added to query execution - Description – Description of the query (as provided by the creator of the query) ## Tables @@ -46,8 +46,8 @@ The Tables section at the top has three options: database table if it has already been created. This action does require confirmation. :::warning - Do not delete the last table in a job’s Query Selection view. Doing so will also - delete the Messages table. In order to delete the last table, it is necessary to delete the job. + Don't delete the last table in a job’s Query Selection view. Doing so will also + delete the Messages table. To delete the last table, delete the job. ::: diff --git a/docs/accessanalyzer/12.0/admin/jobs/job/configure/reports.md b/docs/accessanalyzer/12.0/admin/jobs/job/configure/reports.md index 9fe360ef38..b07c189740 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/job/configure/reports.md +++ b/docs/accessanalyzer/12.0/admin/jobs/job/configure/reports.md @@ -15,7 +15,7 @@ related to configuring reports. The options at the top of the Reports view are: - Properties – Opens the [Job Properties](/docs/accessanalyzer/12.0/admin/jobs/job/properties/overview.md) page for the job that the report is for -- Run Now – Runs the currently selected job that the report is for +- Run Now – Runs the selected job that the report is for - Open Folder – Opens the Report’s folder location with supporting files in the Windows Explorer - View Log – Opens the log for the job that the report is for diff --git a/docs/accessanalyzer/12.0/admin/jobs/job/create.md b/docs/accessanalyzer/12.0/admin/jobs/job/create.md index 5560b52aa3..5233c72643 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/job/create.md +++ b/docs/accessanalyzer/12.0/admin/jobs/job/create.md @@ -6,11 +6,11 @@ sidebar_position: 50 # Create a New Job -Follow the steps to create a new job. +To create a new job: ![Create Job from Jobs Tree context menu](/images/accessanalyzer/12.0/admin/jobs/job/createjob.webp) -**Step 1 –** Select the Jobs tree or the desired job group to add the new job to. Right-click and +**Step 1 –** Select the Jobs tree or the job group you want to add the new job to. Right-click and select **Create Job**. ![New Job added to Jobs Tree](/images/accessanalyzer/12.0/admin/jobs/job/newjob.webp) @@ -19,7 +19,7 @@ select **Create Job**. considerations for naming conventions: :::warning -Do not end a job name with a space. +Don't end a job name with a space. ::: diff --git a/docs/accessanalyzer/12.0/admin/jobs/job/disableenable.md b/docs/accessanalyzer/12.0/admin/jobs/job/disableenable.md index e9c666f844..fd58914fb3 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/job/disableenable.md +++ b/docs/accessanalyzer/12.0/admin/jobs/job/disableenable.md @@ -6,9 +6,9 @@ sidebar_position: 60 # Disable or Enable a Job -Job groups may contain individual jobs that should not be run when the entire job group is run. Some +Job groups may contain individual jobs that shouldn't be run when the entire job group is run. Some job groups also contain jobs that can optionally be run separately from the rest of the job group. -Individual jobs can be disabled or enabled at the job group or job level. Disabled jobs do not +Individual jobs can be disabled or enabled at the job group or job level. Disabled jobs don't execute when the parent job group is run. If the role based access feature is enabled, the ability to enable and disable jobs is limited by @@ -17,21 +17,21 @@ for additional information. ## Disable a Job -Jobs can be disabled from the Jobs tree. Disabled jobs cannot be run manually, through a scheduled -task, or executed as part of the job group. Follow the steps to disable a job. +Jobs can be disabled from the Jobs tree. Disabled jobs can't be run manually, through a scheduled +task, or executed as part of the job group. To disable a job: **Step 1 –** Select a job group or job. :::note When disabling jobs at the job group level, all jobs contained in the job group are -disabled, but the job group is not disabled. Any additional jobs added to that job group at a later +disabled, but the job group isn't disabled. Any additional jobs added to that job group at a later time will be enabled by default. ::: ![Disable Job from Jobs Tree](/images/accessanalyzer/12.0/admin/jobs/job/disablejob.webp) -**Step 2 –** Right-click on the job group or job and select **Disable Job(s)** from the menu. +**Step 2 –** Right-click the job group or job and select **Disable Jobs** from the menu. ![Disabled Job in the Jobs Tree](/images/accessanalyzer/12.0/admin/jobs/job/disabledjob.webp) @@ -43,7 +43,7 @@ Disabled jobs are grayed out, and a red cross is displayed in front of the job. A yellow banner also notifies users that a job is disabled in the Job’s Description page. Additionally, if a disabled job is run, a warning message appears in the Messages table stating: -`[UserName] requested [JobName] to run but it is in a disabled state`. Job statistics also do not +`[UserName] requested [JobName] to run but it is in a disabled state`. Job statistics also don't display on the job’s description page. ## Enable a Job @@ -56,6 +56,6 @@ group to enable all of the disabled jobs. ![Enable Job from Jobs Tree](/images/accessanalyzer/12.0/admin/jobs/job/enablejob.webp) -**Step 2 –** Right-click on the job group or job and select **Enable Job(s)** from the menu. +**Step 2 –** Right-click the job group or job and select **Enable Jobs** from the menu. The job is now enabled. If a job group was selected, all the jobs in the group are now enabled. diff --git a/docs/accessanalyzer/12.0/admin/jobs/job/overview.md b/docs/accessanalyzer/12.0/admin/jobs/job/overview.md index 00e7272390..4dddfacbf9 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/job/overview.md +++ b/docs/accessanalyzer/12.0/admin/jobs/job/overview.md @@ -21,7 +21,7 @@ structure to run those jobs together in the proper order. ::: -Jobs do not have a Settings node like a job group. Job Properties provide the option to break +Jobs don't have a Settings node like a job group. Job Properties provide the option to break inheritance on global or job group settings. See the [Job Properties](/docs/accessanalyzer/12.0/admin/jobs/job/properties/overview.md) topic for additional information. @@ -42,7 +42,7 @@ the Web Console. ## Job Description Page The Job Description page displays shortcuts, links, and important information on the job. The Job -Page allows users to view and modify common job configurations, such as Connection and Storage +Page lets users view and modify common job configurations, such as Connection and Storage profiles, job properties, SQL analysis parameters, and PowerShell parameters. Depending on the type of job, the description page will appear different and display information specific to the job selected. @@ -103,7 +103,7 @@ information: - Graph – Displays a line graph that has information for the last five times the job was executed -Prior to running any job or job group, ensure the following have been properly configured: +Before running any job or job group, ensure the following have been properly configured: - Queries, Analysis, Actions, and Reports are configured as desired - If collecting data, at least one host list has been assigned @@ -142,7 +142,7 @@ The following settings can be inherited from a parent: If a job has analysis parameters that can be customized, those parameters can be configured in the Configuration section of the Job Description Page. -Follow the steps to configure customizable parameters using the Configuration option on the Job +To configure customizable parameters using the Configuration option on the Job Description Page: **Step 1 –** Navigate to the **Jobs > [Job Group] > [Job]** node. If the job has customizable @@ -150,7 +150,7 @@ parameters, they will be located under Configuration in the job's Overview secti ![Configuration section of Job description page](/images/accessanalyzer/12.0/admin/jobs/job/descriptionpageconfigurationsection.webp) -**Step 2 –** Click on a parameter to open the Parameter Configuration window. +**Step 2 –** Click a parameter to open the Parameter Configuration window. :::note To view a tool-tip that contains information about the Variable Name and the Task Name diff --git a/docs/accessanalyzer/12.0/admin/jobs/job/properties/autoretry.md b/docs/accessanalyzer/12.0/admin/jobs/job/properties/autoretry.md index 106e4c1305..2805961a40 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/job/properties/autoretry.md +++ b/docs/accessanalyzer/12.0/admin/jobs/job/properties/autoretry.md @@ -11,7 +11,7 @@ the selected host status values: Offline, Failed, Errors, and Warnings. ![Auto Retry tab of Job Properties](/images/accessanalyzer/12.0/admin/jobs/job/properties/autoretry.webp) -Check the desired Host Status values to generate a retry, and then configure the Refresh Data and +Check the Host Status values you want to generate a retry, and then configure the Refresh Data and Retry Options settings. Finally, enter a User name (domain\user) and Password in the Scheduler Authentication section. diff --git a/docs/accessanalyzer/12.0/admin/jobs/job/properties/connection.md b/docs/accessanalyzer/12.0/admin/jobs/job/properties/connection.md index d327878d46..2fd0b368e6 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/job/properties/connection.md +++ b/docs/accessanalyzer/12.0/admin/jobs/job/properties/connection.md @@ -21,7 +21,7 @@ is where the Connection Profile should be configured. If the host list is set un ![Connection tab of the Jop Properties](/images/accessanalyzer/12.0/admin/jobs/job/properties/viewxml.webp) -Select the desired option to identify the required Connection Profile for the job. See the +Select the option you want to identify the required Connection Profile for the job. See the [Connection Node](/docs/accessanalyzer/12.0/admin/jobs/group/settings/connection.md) topic for additional information for the three connection options. diff --git a/docs/accessanalyzer/12.0/admin/jobs/job/properties/general.md b/docs/accessanalyzer/12.0/admin/jobs/job/properties/general.md index df8da9c2cd..71e505163c 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/job/properties/general.md +++ b/docs/accessanalyzer/12.0/admin/jobs/job/properties/general.md @@ -20,7 +20,7 @@ The following options are available: CSV file in the job’s output directory. If there are multiple tables in the job, this option creates one file per table. - Timeout [value] minutes – Job’s thread timeout value -- Command – Provides the ability to enter a command that will be executed from the command line upon +- Command – lets you enter a command that will be executed from the command line upon job completion ## Log Level @@ -30,7 +30,7 @@ The log level feature includes the following options: - Use global setting – use the Application log level feature, configured at the global level. :::note - By selecting the another option from the drop-down list, you break inheritance for + By selecting the another option from the dropdown list, you break inheritance for this job. ::: diff --git a/docs/accessanalyzer/12.0/admin/jobs/job/properties/history.md b/docs/accessanalyzer/12.0/admin/jobs/job/properties/history.md index 1517e071db..eaef25f648 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/job/properties/history.md +++ b/docs/accessanalyzer/12.0/admin/jobs/job/properties/history.md @@ -14,8 +14,8 @@ broken inheritance at a job group level, or to configure settings just for this By default, all jobs are set to inherit the Data Retention Period and Log Retention Period settings, the **Use Default Setting** option. Deselect the **Use Default Settings** option to configure custom -settings for the job. Then provide the desired Data Retention Period and Log Retention Period -settings. See the [History](/docs/accessanalyzer/12.0/admin/settings/history.md) topic for additional information. +settings for the job. Then provide the Data Retention Period and Log Retention Period +settings you want. See the [History](/docs/accessanalyzer/12.0/admin/settings/history.md) topic for additional information. Click **OK** to save configuration changes and close the Job Properties window. Click **Cancel** if no changes were made. diff --git a/docs/accessanalyzer/12.0/admin/jobs/job/properties/performance.md b/docs/accessanalyzer/12.0/admin/jobs/job/properties/performance.md index 1938ef7c2e..89ec4242a8 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/job/properties/performance.md +++ b/docs/accessanalyzer/12.0/admin/jobs/job/properties/performance.md @@ -6,7 +6,7 @@ sidebar_position: 20 # Performance Tab -The Performance tab provides options that can be used to improve job performance and runtime. +The Performance tab provides options you can use to improve job performance and runtime. ![Performance tab of Job Properties](/images/accessanalyzer/12.0/admin/jobs/job/properties/performance.webp) @@ -14,12 +14,12 @@ Adjust the following settings by sliding the needle up and down the line: - Concurrent Worker Threads – The number of worker threads selected equals the number of hosts being queried concurrently. If needed, this value can be increased. -- Skip Hosts that do not respond to PING – Selected by default. Deselect if a target host has been +- Skip Hosts that don't respond to PING – Selected by default. Deselect if a target host has been configured to not respond to PING requests, allowing Access Analyzer to scan the target host without a PING response. :::note - In most cases, it is not recommend to deselect this option, as it causes the job to + In most cases, it isn't recommend to deselect this option, as it causes the job to continue querying offline hosts until the job timeout value is reached, set by default to 20 minutes. ::: diff --git a/docs/accessanalyzer/12.0/admin/jobs/job/properties/reportroles.md b/docs/accessanalyzer/12.0/admin/jobs/job/properties/reportroles.md index d57ec36927..129dd62921 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/job/properties/reportroles.md +++ b/docs/accessanalyzer/12.0/admin/jobs/job/properties/reportroles.md @@ -14,15 +14,15 @@ for additional information. ![Report Roles tab of Job Properties](/images/accessanalyzer/12.0/admin/jobs/job/properties/reportroles.webp) -On the Report Roles tab, report role inheritance cannot be broken. Access to reports is inherited +On the Report Roles tab, report role inheritance can't be broken. Access to reports is inherited from the global level to job groups to jobs to report configuration. All user roles configured at the global level (**Settings** > **Roles**) are inherited down to all reports. Only the Global -Options Administrator, the Access Administrator, and the Host Management Administrator do not have +Options Administrator, the Access Administrator, and the Host Management Administrator don't have access to reports. The **Include Report Viewers from this object's parent** option can be unchecked to automatically remove any user with the Report Viewer role inherited from a parent object to the job. Remember, -this does not apply to global inheritance. +this doesn't apply to global inheritance. Additional accounts can be added with the Report Viewer role at the job level and inherited down to all reports generated by the job. Click **Add Report Viewer** to open the Select User or Group @@ -36,7 +36,7 @@ The table displays the following information: - Type – Account type (user or group) - Role – Role assigned to account which grants access to reports - Inherited From – Indicates the level at which the account was granted access to reports. Remember, - global inheritance cannot be broken. + global inheritance can't be broken. Click **OK** to save configuration changes and close the Job Properties window. Click **Cancel** if no changes were made. diff --git a/docs/accessanalyzer/12.0/admin/jobs/job/properties/reportsettings.md b/docs/accessanalyzer/12.0/admin/jobs/job/properties/reportsettings.md index a55cb9a39c..4d2558b6f9 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/job/properties/reportsettings.md +++ b/docs/accessanalyzer/12.0/admin/jobs/job/properties/reportsettings.md @@ -13,9 +13,9 @@ this job. ![Report Settings tab of Job Properties](/images/accessanalyzer/12.0/admin/jobs/job/properties/reportsettings.webp) -Use the Publish Options drop-down menu to customize the publish setting for the job. To configure +Use the Publish Options dropdown menu to customize the publish setting for the job. To configure custom Email settings for the job, select the **Use These Email Settings** option and then provide -the desired Email information. Multiple email addresses can be input by adding a semicolon (;) and +the Email information you want. Multiple email addresses can be input by adding a semicolon (;) and space between entries. See the [Reporting Node](/docs/accessanalyzer/12.0/admin/jobs/group/settings/reporting.md) topic for additional information on the Publish and Email options. diff --git a/docs/accessanalyzer/12.0/admin/jobs/job/properties/storage.md b/docs/accessanalyzer/12.0/admin/jobs/job/properties/storage.md index 97cbf195e0..3e32e563f8 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/job/properties/storage.md +++ b/docs/accessanalyzer/12.0/admin/jobs/job/properties/storage.md @@ -14,7 +14,7 @@ group level, or to configure settings just for this job. By default, all jobs are set to inherit the storage setting, the **Use Default** option. To configure a different profile for the job, select the **Use This Profile** option and select the -desired Storage Profile from the drop-down menu. Storage Profiles can only be configured at the +desired Storage Profile from the dropdown menu. Storage Profiles can only be configured at the **Settings** > **Storage** node. See the [Storage](/docs/accessanalyzer/12.0/admin/settings/storage/overview.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/admin/jobs/job/results.md b/docs/accessanalyzer/12.0/admin/jobs/job/results.md index bfbe385e54..a46966f1eb 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/job/results.md +++ b/docs/accessanalyzer/12.0/admin/jobs/job/results.md @@ -23,7 +23,7 @@ Every job generates a native data table when executed, which appears at the top The native data table, or raw data table, is produced by query execution. It contains all raw data collected by the scan. It is often named DEFAULT, but may have another name that is set during query configuration. If no query is executed by the job, the DEFAULT table is listed as a placeholder only -and will be empty (0 rows). It is possible to have multiple queries in the same job, though not +and will be empty (0 rows). A job can have multiple queries, though not recommended. These queries could write to the same native data table, or each query could write to its own native data table. If multiple native data tables are being generated by one job, they are listed in alphanumeric order at the top of the Results node list. diff --git a/docs/accessanalyzer/12.0/admin/jobs/job/status.md b/docs/accessanalyzer/12.0/admin/jobs/job/status.md index 09b32fbd35..55cb9c90d8 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/job/status.md +++ b/docs/accessanalyzer/12.0/admin/jobs/job/status.md @@ -36,6 +36,6 @@ The Status node tables are: `WARNING: No Host found for processing`. - If this message is generated by an analysis or reporting job, then there is no problem as that - type of job does not need a host list assigned + type of job doesn't need a host list assigned - However, if this message is generated by a job running a data collection query, this warning would explain why the native data table is empty diff --git a/docs/accessanalyzer/12.0/admin/jobs/overview.md b/docs/accessanalyzer/12.0/admin/jobs/overview.md index ecaa2840a6..049f8fbf2d 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/overview.md +++ b/docs/accessanalyzer/12.0/admin/jobs/overview.md @@ -69,14 +69,14 @@ jobs can be enabled to track changes to configuration settings. When enabled, co are tracked in change logs stored within the job folder. Changes can also be viewed within this window. -Remember, custom jobs are not shipped with Access Analyzer but instead user created. +Remember, custom jobs aren't shipped with Access Analyzer but instead user created. The Changes window opens from the **Changes** option in the right-click menu from the selected Jobs tree, job group, or job node. ![Changes Window](/images/accessanalyzer/12.0/admin/jobs/changeswindow.webp) -Select **Enabled** from the drop-down menu in the upper-left corner to turn on change tracking of +Select **Enabled** from the dropdown menu in the upper-left corner to turn on change tracking of configuration settings. Select a modification from the table and click **Undo** to revert the change. @@ -110,7 +110,7 @@ the Access Analyzer pop-up window to confirm the merge. Changes between releases are tracked. Only jobs that are locked can be upgraded. :::note -Jobs that are included in Access Analyzer are locked and changes cannot be made to those +Jobs that are included in Access Analyzer are locked and changes can't be made to those jobs. ::: diff --git a/docs/accessanalyzer/12.0/admin/maintenance/backuprecovery.md b/docs/accessanalyzer/12.0/admin/maintenance/backuprecovery.md index 795d536ed0..8d3a4755b8 100644 --- a/docs/accessanalyzer/12.0/admin/maintenance/backuprecovery.md +++ b/docs/accessanalyzer/12.0/admin/maintenance/backuprecovery.md @@ -6,20 +6,20 @@ sidebar_position: 30 # Backup and Recovery -For data recovery purposes, the Access Analyzer does not need a complete image back up of the Access +For data recovery purposes, the Access Analyzer doesn't need a complete image back up of the Access Analyzer Console server. Rather a standard file level back up of a few key components is all that is necessary. This document contains a step-by-step guide for back up and recovery. The choice of back up utility is left to the Access Analyzer user. :::note -This does not cover back up of the Access Analyzer database. +This doesn't cover back up of the Access Analyzer database. ::: ## Steps to Back Up the Console Server -Follow these steps to back up the key components necessary for data recovery of the Access Analyzer -Console server. +To back up the key components necessary for data recovery of the Access Analyzer +Console server: **Step 1 –** Obtain or save the installation media for Access Analyzer. @@ -58,7 +58,7 @@ Follow these steps for data recovery of the Access Analyzer Console server. **Step 1 –** Confirm the prerequisites have been met on the Access Analyzer Console Server. See the [Requirements](/docs/accessanalyzer/12.0/requirements/overview.md) topic for specific prerequisites. -**Step 2 –** Install the Access Analyzer application. Do not start the Access Analyzer application +**Step 2 –** Install the Access Analyzer application. Don't start the Access Analyzer application at this time. **Step 3 –** Restore all of the backed up files and folders from Step 2 of Steps to Back up the diff --git a/docs/accessanalyzer/12.0/admin/maintenance/bestpractices.md b/docs/accessanalyzer/12.0/admin/maintenance/bestpractices.md index 8dab10b820..d6133d65f9 100644 --- a/docs/accessanalyzer/12.0/admin/maintenance/bestpractices.md +++ b/docs/accessanalyzer/12.0/admin/maintenance/bestpractices.md @@ -6,20 +6,20 @@ sidebar_position: 50 # Best Practices -With any new product, a few pointers can really get us started on the right foot. In the spirit of -making you successful, here are some tips that will help you become an effective user of the Access -Analyzer in no time. Enjoy! +With any new product, a few pointers can really help you start off on the right foot. In the spirit +of making you successful, here are some tips that will help you become an effective user of the +Access Analyzer in no time. Enjoy! ## Do The following is a list of best practices to use for Access Analyzer: -- Read all Job and Job Group descriptions and instructions prior to running any solution -- Scope all collection queries to target just the desired objects, locations, or hosts you want to +- Read all Job and Job Group descriptions and instructions before running any solution +- Scope all collection queries to target just the objects, locations, or hosts you want to collect information from -- Run new solutions against a single host or subset of data prior to running against all to ensure +- Run new solutions against a single host or subset of data before running against all to ensure proper operation, configuration, and output of each job -- Leverage service accounts (if possible) containing the proper permissions to access the +- Use service accounts (if possible) containing the proper permissions to access the information you want to audit rather than personal user accounts (this will reduce “access denied” warnings due to insufficient privileges) - Set a username and password for any scheduled task @@ -27,30 +27,30 @@ The following is a list of best practices to use for Access Analyzer: Analyzer System Requirements & Installation Notes document for details) - Set a connection profile inside the Job “properties” menu for any job that runs using the Exchange Metrics data collector -- Check the “Messages” table within any Job’s “Results” node if reports do not generate or +- Check the “Messages” table within any Job’s “Results” node if reports don't generate or collection doesn’t appear to be working properly - Configure history settings at the Job level (as opposed to at the Global or Job Group level) to avoid unnecessary storage consumption within SQL - Contact Netwrix Support with ANY questions you have -## Do Not +## Don't The following is a list of practices to avoid for Access Analyzer. -- Do not change Job or Job Group names within the Job Tree -- Do not attempt to run an entire Solution Set without configuring your scoping options first -- Do not confuse WARNINGS for errors in data collection. Warnings are purely informational -- Do not change the name of your Access Analyzer database -- Do not edit a job’s configuration or open any query or analysis rule while that job is running -- Do not use the Fully Qualified Domain Name of a host when manually entering hosts to run queries +- Don't change Job or Job Group names within the Job Tree +- Don't attempt to run an entire Solution Set without configuring your scoping options first +- Don't confuse WARNINGS for errors in data collection. Warnings are purely informational +- Don't change the name of your Access Analyzer database +- Don't edit a job’s configuration or open any query or analysis rule while that job is running +- Don't use the Fully Qualified Domain Name of a host when manually entering hosts to run queries against; instead, use the Common Name -- Do not enable “Debug” logging unless needed for additional troubleshooting -- Do not change the database Access Analyzer writes to at the global level; instead, change the +- Don't enable “Debug” logging unless needed for additional troubleshooting +- Don't change the database Access Analyzer writes to at the global level; instead, change the database at the job level if desired ### Contact Support -When the checklist items do not resolve the issue, contact support with as much applicable +When the checklist items don't resolve the issue, contact support with as much applicable information as possible from the table below. It is possible that a hot fix may already exist for the product. diff --git a/docs/accessanalyzer/12.0/admin/maintenance/troubleshooting.md b/docs/accessanalyzer/12.0/admin/maintenance/troubleshooting.md index e5bc613fd8..de250935e3 100644 --- a/docs/accessanalyzer/12.0/admin/maintenance/troubleshooting.md +++ b/docs/accessanalyzer/12.0/admin/maintenance/troubleshooting.md @@ -24,7 +24,7 @@ purposes. This includes: - The Application log which contains logging of all activities within Access Analyzer - The Upgrade log which logs activities related to the upgrade process -- The upgrade archive which is a zip file containing all of your Access Analyzer jobs prior to the +- The upgrade archive which is a zip file containing all of your Access Analyzer jobs before the upgrade process - Sensitive Data logs that contain details from sensitive data scans performed against various repositories @@ -35,14 +35,14 @@ See the [Logs](#logs) topic for additional information. ## Logs -Access Analyzer has a few areas where it stores logs. Make sure the log level is set to DEBUG in -Access Analyzer to gather all necessary information. Once the logs have been created and sent to -Netwrix Support, then reset the logging level to save disc space. +Access Analyzer has a few areas where it stores logs. Ensure the log level is set to DEBUG in +Access Analyzer to gather all necessary information. After the logs have been created and sent to +Netwrix Support, reset the logging level to save disc space. To set your logging level to debug go to **Settings** > **Application** – **Set the Application log level to Debug** and restart the application. -#### Where Are the Logs Located? +#### Log File Locations | Log Name | Log Location | | --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | diff --git a/docs/accessanalyzer/12.0/admin/navigate/activitiespane.md b/docs/accessanalyzer/12.0/admin/navigate/activitiespane.md index 6020b88cf6..263e7f030f 100644 --- a/docs/accessanalyzer/12.0/admin/navigate/activitiespane.md +++ b/docs/accessanalyzer/12.0/admin/navigate/activitiespane.md @@ -6,10 +6,10 @@ sidebar_position: 40 # Activities Pane -The Activities pane displays a list of activities which can be conducted within the currently +The Activities pane displays a list of activities which can be conducted within the selected console section. It is only visible if there are activities available for the selected section. In the few cases where the Results pane is a wizard, this pane becomes the navigation pane -for the wizard, e.g. the Access Analyzer Host Discovery Wizard. If the currently selected console +for the wizard, e.g. the Access Analyzer Host Discovery Wizard. If the selected console section has an associated Activities Pane, it can be found on the right-hand side of the Access Analyzer Console. @@ -23,4 +23,4 @@ The following console sections have associated Activities Panes: - Jobs > [Job Group/Job] > Settings node The Guidance section of the Activities Pane will display context sensitive information depending on -what the currently selected console section is. +what the selected console section is. diff --git a/docs/accessanalyzer/12.0/admin/navigate/datagrid.md b/docs/accessanalyzer/12.0/admin/navigate/datagrid.md index 6c0c426cd1..756436af28 100644 --- a/docs/accessanalyzer/12.0/admin/navigate/datagrid.md +++ b/docs/accessanalyzer/12.0/admin/navigate/datagrid.md @@ -23,7 +23,7 @@ Grid view in the Results Pane, indicates how many rows of data are available wit (the first value) and how many rows of data are available in the Access Analyzer database for this data grid (the second value). The maximum value can be changed by the user and only affects the maximum number of rows available for this data grid within the Access Analyzer Console. The total -value is automatically supplied from the Access Analyzer database and cannot be changed by the user. +value is automatically supplied from the Access Analyzer database and can't be changed by the user. If the total value is less than the maximum value, then all available data for this grid is present for sorting, filtering, and searching. @@ -57,7 +57,7 @@ for information on right-click menus within a data grid. ### Customization Window -The Customization window can be used to customize the data grid to only display specific columns. +Use the Customization window to customize the data grid to only display specific columns. ![Customization Window](/images/accessanalyzer/12.0/admin/navigate/datagridfunctionality2.webp) @@ -66,7 +66,7 @@ To open the Customization window, select Field Chooser from the column header ri ![Customization Window](/images/accessanalyzer/12.0/admin/navigate/datagridfunctionality3.webp) Any column that has been removed from the data grid, either by dragging it off the screen or by -dropping it into this window, will be listed here. A column not currently displayed can be returned +dropping it into this window, will be listed here. A column not displayed can be returned to the data grid by dragging-and-dropping it from this window onto the header row. ### Footer @@ -80,8 +80,8 @@ To enable the footer, right-click in a column header and select Footer from the ![Footer display](/images/accessanalyzer/12.0/admin/navigate/datagridfunctionality5.webp) -The footer appears as a gray bar at the bottom of the grid (or grid group). Right-click on the -footer under the desired column. Only the options applicable to the desired column will be valid for +The footer appears as a gray bar at the bottom of the grid (or grid group). Right-click the +footer under the column you want. Only the options applicable to that column will be valid for selection. ![Footer options](/images/accessanalyzer/12.0/admin/navigate/datagridfunctionality6.webp) @@ -133,7 +133,7 @@ either to the stationary section on the left or to the mobile section on the rig counts as a single row for the total rows value, but displays in two rows with the second row dedicated for the moved column. -Drag the column header(s) back to the table to remove the grouping or use the Clear Sort option in +Drag the column headers back to the table to remove the grouping or use the Clear Sort option in the [Data Grid Right-Click Menu](#data-grid-right-click-menu). Additionally, the sort will clear when the user navigates to another place in the console. @@ -145,9 +145,9 @@ dialog located above the Activities Pane. ![Filter](/images/accessanalyzer/12.0/admin/navigate/datagridfunctionality12.webp) -In the header of every column is a drop-down arrow. This provides users with the ability to filter -the data grid for a particular item or items within a column. The drop-down menu has the options of -(All), (Custom…), and an alphabetical listing of all items currently within that column for the data +In the header of every column is a dropdown arrow. This provides users with the ability to filter +the data grid for a particular item or items within a column. The dropdown menu has the options of +(All), (Custom…), and an alphabetical listing of all items within that column for the data grid. - [Custom Filter](#custom-filter) – Click Custom Filter in the header dropdown to open the Custom @@ -171,20 +171,20 @@ The Custom Filter window options are: - Second Comparison Operator – Select from a list of different logical operators that will apply to the second custom filter criteria. - Two wildcard options: - - The underscore (\_) can be used to represent any single character - - The asterisk (\*) can be used to represent any series of characters + - Use the underscore (\_) to represent any single character + - Use the asterisk (\*) to represent any series of characters #### Creating a Custom Filter -Follow the steps to create a Custom Filter: +To create a Custom Filter: **Step 1 –** Click the dropdown arrow in the column header for the column where the Custom Filter is going to be applied and select (Custom…) from the list. The Custom Filter window opens. ![Creating a Custom Filter](/images/accessanalyzer/12.0/admin/navigate/datagridfunctionality14.webp) -**Step 2 –** Set the desired criteria for the custom filter. Select the logical operator from the -drop-down menu on the left and set the criteria in the textbox on the right. +**Step 2 –** Set the criteria you want for the custom filter. Select the logical operator from the +dropdown menu on the left and set the criteria in the textbox on the right. **Step 3 –** Select either AND/OR and set the second criteria field, following the same method as Step 2. @@ -207,7 +207,7 @@ set. See the [Filtration Dialog](#filtration-dialog) topic for additional inform feature. Filters can be cleared by clicking the red X in the filtration dialog (to clear all filter -statements), selecting All from the column’s drop-down menu (to clear filters one column at a time), +statements), selecting All from the column’s dropdown menu (to clear filters one column at a time), or by navigating to another place in the console (to clear all filter statements). However, the Recent Filters option in the filtration dialog provides a list of the most recent filters applied to the data set for users to quickly return to a filtered view. @@ -253,7 +253,7 @@ The filter options and logical operators are: - Comparison Operator – The comparison operator (dark red text) can be changed by clicking on it to open a menu with: - equals - - does not equal + - doesn't equal - is less than - is less than or equal to - is greater than @@ -261,7 +261,7 @@ The filter options and logical operators are: - like - not like - is blank - - is not blank + - isn't blank - between - not between - in diff --git a/docs/accessanalyzer/12.0/admin/navigate/overview.md b/docs/accessanalyzer/12.0/admin/navigate/overview.md index 8b40ee74e5..90e3482821 100644 --- a/docs/accessanalyzer/12.0/admin/navigate/overview.md +++ b/docs/accessanalyzer/12.0/admin/navigate/overview.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Navigating the Console -There are several options that can be used to navigate the Access Analyzer Console. This section +Several options let you navigate the Access Analyzer Console. This section covers basic Access Analyzer Console navigation, including menu options, buttons, and the different panes through which users can access Access Analyzer’s various functions and options. @@ -21,8 +21,8 @@ The primary sections of the Access Analyzer Console are: - [Results Pane](/docs/accessanalyzer/12.0/admin/navigate/resultspane.md) – Displays various interfaces based on what is selected in the Navigation Pane or Activities Pane - [Activities Pane](/docs/accessanalyzer/12.0/admin/navigate/activitiespane.md) – Displays a list of activities which can be conducted within - the currently selected console section + the selected console section -Access Analyzer Data Grids also have specific navigation options that enable users to filter, group, +Access Analyzer Data Grids also have specific navigation options that let users filter, group, and search through data. See the [Data Grid Functionality](/docs/accessanalyzer/12.0/admin/navigate/datagrid.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/admin/navigate/pane.md b/docs/accessanalyzer/12.0/admin/navigate/pane.md index 2b430a6e13..5e1e482507 100644 --- a/docs/accessanalyzer/12.0/admin/navigate/pane.md +++ b/docs/accessanalyzer/12.0/admin/navigate/pane.md @@ -135,7 +135,7 @@ Menu items include: needs to be modified. Unlocking a job will prevent Job Initiators from scheduling or running the job. This option only applies to Role Based Access. See the [Role Based Access](/docs/accessanalyzer/12.0/admin/settings/access/rolebased/overview.md) for additional information. -- Enable/Disable Job(s) – Disables the selected job or job group and skips them during scan +- Enable/Disable Jobs – Disables the selected job or job group and skips them during scan execution. When a job group is disabled, all existing jobs within the job group are disabled. See the [Disable or Enable a Job](/docs/accessanalyzer/12.0/admin/jobs/job/disableenable.md) topic for more information. - Schedules – Opens the [Schedule Jobs](/docs/accessanalyzer/12.0/admin/schedule/overview.md#schedule-jobs) to schedule job group diff --git a/docs/accessanalyzer/12.0/admin/navigate/top.md b/docs/accessanalyzer/12.0/admin/navigate/top.md index f5cbfb7598..02a69f7a47 100644 --- a/docs/accessanalyzer/12.0/admin/navigate/top.md +++ b/docs/accessanalyzer/12.0/admin/navigate/top.md @@ -159,4 +159,4 @@ The options in the Button Bar are: | ![paste](/images/accessanalyzer/12.0/admin/navigate/paste.webp) | Clipboard with paper | Paste the query from the clipboard (Ctrl + V) | | ![delete](/images/accessanalyzer/12.0/admin/navigate/delete.webp) | Red X | Delete the selected query | -Select a button for the desired action. +Select a button for the action you want. diff --git a/docs/accessanalyzer/12.0/admin/overview.md b/docs/accessanalyzer/12.0/admin/overview.md index 82141d8b6e..de57eac81e 100644 --- a/docs/accessanalyzer/12.0/admin/overview.md +++ b/docs/accessanalyzer/12.0/admin/overview.md @@ -14,7 +14,7 @@ applications with the application. ## Data Collectors Overview -Access Analyzer leverages a wide variety of APIs and protocols to connect to and communicate with +Access Analyzer uses a wide variety of APIs and protocols to connect to and communicate with the systems and applications in an organization’s environment. From MAPI to PowerShell, WMI, LDAP, CIFS, and more. It uses the best, most appropriate data collection methodology for every data collection task. The majority of Access Analyzer data comes from agentless scans and log collection. diff --git a/docs/accessanalyzer/12.0/admin/report/chartwizard/chartformat.md b/docs/accessanalyzer/12.0/admin/report/chartwizard/chartformat.md index 867bb53d98..ea9b05fca8 100644 --- a/docs/accessanalyzer/12.0/admin/report/chartwizard/chartformat.md +++ b/docs/accessanalyzer/12.0/admin/report/chartwizard/chartformat.md @@ -33,5 +33,5 @@ The Chart Format page has the following options: for the chart type. If a value greater than the default is entered, then the value automatically resets back to the default. -Once you have configured the options as required, click **Next** to proceed to the Data Source page. +After you configure the options as required, click **Next** to proceed to the Data Source page. See the [Data Source](/docs/accessanalyzer/12.0/admin/report/chartwizard/datasource.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/admin/report/chartwizard/configure.md b/docs/accessanalyzer/12.0/admin/report/chartwizard/configure.md index 7437907fa4..981792251d 100644 --- a/docs/accessanalyzer/12.0/admin/report/chartwizard/configure.md +++ b/docs/accessanalyzer/12.0/admin/report/chartwizard/configure.md @@ -6,7 +6,7 @@ sidebar_position: 30 # Configure -The Configure page of the Chart Configuration wizard allows you to configure the chart as required. +Use the Configure page of the Chart Configuration wizard to configure the chart as required. The page consist of two tabs, Chart Configuration and Data Preview. ## Chart Configuration @@ -17,9 +17,9 @@ shown in the chart. ![Chart Configuration wizard Configure page](/images/accessanalyzer/12.0/admin/report/chartwizard/configure.webp) -The left side shows all the columns from the data source table that can be used for the label axis. +The left side shows all the columns from the data source table that you can use for the label axis. For example, the label column is the x-axis on a line chart and the y-axis on a bar chart. Select -the checkbox of the desired label column from the list. You can use the search bar to filter this +the checkbox of the label column you want from the list. You can use the search bar to filter this list of columns. If a datetime label column has been selected, you can optionally select a transformation function @@ -42,25 +42,25 @@ existing data series. The following options are available: - Color Picker – Available only for pie charts. Opens the Pie slices color window, which allows you to customize the color for each slice of the pie chart. On the Pie slices color window: - - Select the row of the desired value to customize and click **Change Color** - - Use the color picker to choose the desired color, then click **OK** + - Select the row of the value you want to customize and click **Change Color** + - Use the color picker to choose the color you want, then click **OK** - Repeat for each color you want to customize - Click **OK** to save your selections and close the Pie slices color window, or click **Cancel** to close the window without changing the colors -At the bottom of the page is a preview of the chart as it is currently configured using the +At the bottom of the page is a preview of the chart as it is configured using the available data. See the [Chart Preview](#chart-preview) topic for additional information. Additionally, you can see a preview of the source data table in the Data Preview tab. See the [Data Preview](#data-preview) topic for additional information. -Once you have finished configuring the chart, click **Finish** to close the wizard. You are returned +After you finish configuring the chart, click **Finish** to close the wizard. You are returned to the Widgets page of the Report Configuration wizard, where the newly configured chart is shown. You must complete the Report Configuration wizard to save the chart on the report. See the [Widgets Page](/docs/accessanalyzer/12.0/admin/report/wizard/widgets.md) topic for additional information. ### Add New Series / Edit Series Window -The Add new series and Edit series windows allow you to configure the data series of the chart. The +Use the Add new series and Edit series windows to configure the data series of the chart. The appropriate window is opened by clicking **Add** to create a new series, or by selecting an existing series and clicking **Edit**. @@ -68,8 +68,8 @@ series and clicking **Edit**. These windows contain the following options for the data series: -- Column table – This table displays the available columns in the source table that are not - currently selected in a series for the chart. Select the checkbox for column that contains the +- Column table – This table displays the available columns in the source table that aren't + selected in a series for the chart. Select the checkbox for column that contains the data for the series. You can use the search bar to filter the list of columns. :::note @@ -77,7 +77,7 @@ These windows contain the following options for the data series: ::: -- Select a function to aggregate the column by – Use the drop-down to select an aggregation +- Select a function to aggregate the column by – Use the dropdown to select an aggregation function. The available options vary depending on the column selected. The possible options are: - None @@ -98,7 +98,7 @@ window without saving. ### Chart Preview -At the bottom of the page a preview of the currently configured chart is displayed. +At the bottom of the page a preview of the configured chart is displayed. ![Chart preview](/images/accessanalyzer/12.0/admin/report/chartwizard/configurechartpreview.webp) @@ -115,14 +115,14 @@ would cause them: ## Data Preview -The Data Preview tab allows you to see and customize the data that is to be shown in the chart. +Use the Data Preview tab to see and customize the data that is to be shown in the chart. ![Data Preview tab](/images/accessanalyzer/12.0/admin/report/chartwizard/configuredatapreview.webp) The buttons above the column names provide you the following options for configuring the table arrangement: -- Filter Editor – Opens the Filter Editor which allows you to add custom filters with conditional +- Filter Editor – Opens the Filter Editor, which lets you add custom filters with conditional statements and logical connectives - Best Fit (all columns) –  Adjusts the width of the columns to display all the data within the cells diff --git a/docs/accessanalyzer/12.0/admin/report/chartwizard/datasource.md b/docs/accessanalyzer/12.0/admin/report/chartwizard/datasource.md index 499a0db977..76e7153330 100644 --- a/docs/accessanalyzer/12.0/admin/report/chartwizard/datasource.md +++ b/docs/accessanalyzer/12.0/admin/report/chartwizard/datasource.md @@ -10,7 +10,7 @@ On the Data Source page of the Chart Configuration wizard configure the data sou ![Chart Configuration wizard Data Source page](/images/accessanalyzer/12.0/admin/report/chartwizard/datasource.webp) -In order to generate results, a location must first be selected as the source of the data. The table +to generate results, a location must first be selected as the source of the data. The table on this wizard page contains a list of tables and views within Access Analyzer from jobs that have been executed. Select the required data source from the table. @@ -26,5 +26,5 @@ There are the following additional data source options: - Show historical data – If there is historical data, selecting this option displays all collections. It is keyed off of the Jobruntimekey column. -Once you have selected the data source, click **Next** to proceed to the Configure page. See the +After you select the data source, click **Next** to proceed to the Configure page. See the [Configure](/docs/accessanalyzer/12.0/admin/report/chartwizard/configure.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/admin/report/chartwizard/overview.md b/docs/accessanalyzer/12.0/admin/report/chartwizard/overview.md index ea96d3f829..3e05d29ffa 100644 --- a/docs/accessanalyzer/12.0/admin/report/chartwizard/overview.md +++ b/docs/accessanalyzer/12.0/admin/report/chartwizard/overview.md @@ -6,7 +6,7 @@ sidebar_position: 40 # Chart Configuration Wizard -The Chart Configuration wizard allows you to configure the charts that display on reports. The +Use the Chart Configuration wizard to configure the charts that display on reports. The wizard opens when you select to configure a Chart widget from the Widgets page of the Report Configuration Wizard. See the [Widgets Page](/docs/accessanalyzer/12.0/admin/report/wizard/widgets.md) topic for additional information. @@ -16,6 +16,6 @@ The Chart Configuration wizard consists of three pages: - [Data Source](/docs/accessanalyzer/12.0/admin/report/chartwizard/datasource.md) - [Configure](/docs/accessanalyzer/12.0/admin/report/chartwizard/configure.md) -Once you have finished configuring the chart, click **Finish** to close the wizard. You are returned +After you finish configuring the chart, click **Finish** to close the wizard. You are returned to the Widgets page of the Report Configuration wizard, where the newly configured chart is shown. You must complete the Report Configuration wizard to save the chart on the report. diff --git a/docs/accessanalyzer/12.0/admin/report/cleanup.md b/docs/accessanalyzer/12.0/admin/report/cleanup.md index 13fd033c2b..f94df628e3 100644 --- a/docs/accessanalyzer/12.0/admin/report/cleanup.md +++ b/docs/accessanalyzer/12.0/admin/report/cleanup.md @@ -6,18 +6,18 @@ sidebar_position: 80 # Report Cleanup when Deleting a Job or Job Group -When deleting a job or job group, the Delete Job and Delete Group wizards allow you to delete any -published reports contained in the jobs that are being deleted. Follow the steps to delete a job or -job group that contains published reports. +When deleting a job or job group, the Delete Job and Delete Group wizards let you delete any +published reports contained in the jobs that are being deleted. To delete a job or +job group that contains published reports: :::warning -Deleted objects cannot be restored. +Deleted objects can't be restored. ::: ![Delete Group on right-click menu](/images/accessanalyzer/12.0/admin/report/jobstree.webp) -**Step 1 –** In the Jobs tree, right-click on the job or group that you want to delete and select +**Step 1 –** In the Jobs tree, right-click the job or group that you want to delete and select **Delete Job/Group**. ![Delete Group wizard page](/images/accessanalyzer/12.0/admin/report/deletegroup.webp) diff --git a/docs/accessanalyzer/12.0/admin/report/create.md b/docs/accessanalyzer/12.0/admin/report/create.md index f69215f639..f8fcaf5d71 100644 --- a/docs/accessanalyzer/12.0/admin/report/create.md +++ b/docs/accessanalyzer/12.0/admin/report/create.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Creating a Report -Creating and customizing reports allows you to design outputs uniquely crafted to your requirements. +Create and customize reports to design outputs uniquely crafted to your requirements. Reports can vary by section order, sourced data, file format, and other elements within the reports configuration. @@ -16,16 +16,15 @@ You can add additional reports by the following methods: - [Copy an Existing Report](#copy-an-existing-report) :::note -It is important to consider whether a report should be added to an existing job, or a new -job created to generate the report. Contact [Netwrix Support](https://www.netwrix.com/support.html) +Consider whether to add a report to an existing job or create a new +job to generate the report. Contact [Netwrix Support](https://www.netwrix.com/support.html) for additional information on report outputs. ::: ## Create a Custom Report -You can create a new custom report for an existing job from the job’s Reports node. Follow the steps -to create a new report. +You can create a new custom report for an existing job from the job’s Reports node. **Step 1 –** Navigate to **Jobs** > **[Job]** > **Configure** and select the **Reports** node. @@ -49,17 +48,16 @@ topic. ## Copy an Existing Report You can create a new report by copying an existing report and pasting it in a job’s Reports node. -You can then optionally customize the report as required. Follow the steps to create a copy of an -existing report. +You can then optionally customize the report as required. ![Copy Report](/images/accessanalyzer/12.0/admin/report/copy.webp) -**Step 1 –** Navigate to the Reports node where the desired report to copy is located. Click the +**Step 1 –** Navigate to the Reports node where the report you want to copy is located. Click the vertical ellipsis menu next to the report and select Copy. ![Paste Report](/images/accessanalyzer/12.0/admin/report/paste.webp) -**Step 2 –** Navigate to the Reports node in the desired destination for the new report. Click the +**Step 2 –** Navigate to the Reports node in the destination you want for the new report. Click the vertical ellipsis menu in the header row of the Reports table and select Paste. The copy of the report is added to the Reports table. Reports that are copied maintain the same diff --git a/docs/accessanalyzer/12.0/admin/report/edit.md b/docs/accessanalyzer/12.0/admin/report/edit.md index 7e8f1ca039..b92f654fb0 100644 --- a/docs/accessanalyzer/12.0/admin/report/edit.md +++ b/docs/accessanalyzer/12.0/admin/report/edit.md @@ -6,15 +6,13 @@ sidebar_position: 20 # Editing Existing Reports -It is not recommended to edit existing reports unless there are changes to a job’s settings at the +It isn't recommended to edit existing reports unless there are changes to a job’s settings at the global level, job group level, or job level. Changes to when data is collected, the types of data -collected, and the properties of collected data are not reflected in a report’s configuration. As a +collected, and the properties of collected data aren't reflected in a report’s configuration. As a result, generated reports could appear with blank fields or misleading information about the purpose of the collected data, unless the report is modified to reflect the changes to the job's settings. To modify a report, use the Report Configuration Wizard. -Follow the steps to modify an existing report. - **Step 1 –** Navigate to the Reports node that contains the report. ![Configure Report](/images/accessanalyzer/12.0/admin/report/configure.webp) @@ -25,7 +23,7 @@ Follow the steps to modify an existing report. [Report Configuration Wizard](/docs/accessanalyzer/12.0/admin/report/wizard/overview.md) topic for instructions. - You must go through all pages of the wizard, and click **Finish** on the final page to save your - changes. Skip any sections or pages that do not require changes to the existing configuration. You + changes. Skip any sections or pages that don't require changes to the existing configuration. You can click **Cancel** on any page to exit the wizard without saving your changes. Your configuration updates have been saved. To view the updated report you need to first generate diff --git a/docs/accessanalyzer/12.0/admin/report/interactivegrids/copyingcells.md b/docs/accessanalyzer/12.0/admin/report/interactivegrids/copyingcells.md index b1220a42db..ab9e923553 100644 --- a/docs/accessanalyzer/12.0/admin/report/interactivegrids/copyingcells.md +++ b/docs/accessanalyzer/12.0/admin/report/interactivegrids/copyingcells.md @@ -12,7 +12,7 @@ under a column can be selected and copied to the clipboard. ![Copy Cell Data](/images/accessanalyzer/12.0/admin/report/interactivegrids/copycell.webp) -To copy a cell, select the cell, then right-click on it and select **Copy Cell Data**. +To copy a cell, select the cell, then right-click it and select **Copy Cell Data**. :::note You may need to allow programmatic clipboard access for your browser the first time you diff --git a/docs/accessanalyzer/12.0/admin/report/interactivegrids/grouping.md b/docs/accessanalyzer/12.0/admin/report/interactivegrids/grouping.md index 9f21a5691c..5a5ae6e2fa 100644 --- a/docs/accessanalyzer/12.0/admin/report/interactivegrids/grouping.md +++ b/docs/accessanalyzer/12.0/admin/report/interactivegrids/grouping.md @@ -6,11 +6,11 @@ sidebar_position: 10 # Grouping Data -If grouping is enabled, the **Group by** field provides a drop-down list of categories by which the +If grouping is enabled, the **Group by** field provides a dropdown list of categories by which the data can be grouped. :::note -Grouping and filtering cannot be enabled at the same time. If grouping is enabled, the +Grouping and filtering can't be enabled at the same time. If grouping is enabled, the Filter icon is disabled in the report. ::: @@ -20,5 +20,5 @@ The following example shows an interactive grid in which grouping has been enabl ![Group by option](/images/accessanalyzer/12.0/admin/report/interactivegrids/groupby.webp) -The drop-down list to the right of the Group by field can be accessed by clicking the down arrow. -Click an item from the drop-down list to group the report by that category. +The dropdown list to the right of the Group by field can be accessed by clicking the down arrow. +Click an item from the dropdown list to group the report by that category. diff --git a/docs/accessanalyzer/12.0/admin/report/interactivegrids/overview.md b/docs/accessanalyzer/12.0/admin/report/interactivegrids/overview.md index bb460827f8..10631f4607 100644 --- a/docs/accessanalyzer/12.0/admin/report/interactivegrids/overview.md +++ b/docs/accessanalyzer/12.0/admin/report/interactivegrids/overview.md @@ -6,8 +6,8 @@ sidebar_position: 70 # Interactive Grids -Interactive grids in the table section of a report provide the ability to interact with the data and -filter it as required. Interactive grids allow you to perform the following actions: +Interactive grids in the table section of a report let you interact with the data and +filter it as required. With interactive grids, you can perform the following actions: - Group data - Search and filter data @@ -19,7 +19,7 @@ filter it as required. Interactive grids allow you to perform the following acti The toolbar in an interactive grid can display the following options: - Filter icon – Click this icon to activate searching and filter the data -- Group by – Provides a drop-down list of available categories to select for grouping. When grouping +- Group by – Provides a dropdown list of available categories to select for grouping. When grouping is enabled, searching is disabled. - Up arrow and down arrow – Click to expand or collapse the groups - Download Data – Click to download all data to a CSV file. This option is displayed when the diff --git a/docs/accessanalyzer/12.0/admin/report/interactivegrids/paging.md b/docs/accessanalyzer/12.0/admin/report/interactivegrids/paging.md index c6b8d69a5d..5c8fc8ffda 100644 --- a/docs/accessanalyzer/12.0/admin/report/interactivegrids/paging.md +++ b/docs/accessanalyzer/12.0/admin/report/interactivegrids/paging.md @@ -6,20 +6,20 @@ sidebar_position: 30 # Paging -Paging allows users to interact with large sets of data more efficiently when viewing, filtering, -and sorting generated report tables by limiting the amount of data being displayed at a given time. -Reports provide the ability to navigate to specific pages using arrows at the bottom of the report. +Use paging to interact with large sets of data more efficiently when viewing, filtering, +and sorting generated report tables by limiting the amount of data displayed at a given time. +Reports let you navigate to specific pages using arrows at the bottom of the report. Paging is enabled by default. See the [Grid](/docs/accessanalyzer/12.0/admin/report/wizard/widgets.md#grid) topic for additional information. :::note -Paging and grouping cannot be enabled at the same time. When Paging is enabled, the +Paging and grouping can't be enabled at the same time. When Paging is enabled, the Grouping options are disabled for the report. ::: ![Paging](/images/accessanalyzer/12.0/admin/report/interactivegrids/paging.webp) -When paging is enabled, arrows are displayed that allow you to navigate to the next page, last page, +When paging is enabled, arrows appear so you can navigate to the next page, last page, previous page, or first page. If the data is filtered, it is indicated at the end of the line. Each page contains 10 records. diff --git a/docs/accessanalyzer/12.0/admin/report/interactivegrids/searchfilter.md b/docs/accessanalyzer/12.0/admin/report/interactivegrids/searchfilter.md index e236c2a57a..8b0d032eb5 100644 --- a/docs/accessanalyzer/12.0/admin/report/interactivegrids/searchfilter.md +++ b/docs/accessanalyzer/12.0/admin/report/interactivegrids/searchfilter.md @@ -10,7 +10,7 @@ When dealing with large sets of data, it may be useful to search for a desired a be done using the Filter icon. :::note -Searching and grouping cannot be enabled at the same time. If grouping is enabled, the +Searching and grouping can't be enabled at the same time. If grouping is enabled, the Search icon is disabled in the report. ::: @@ -23,7 +23,7 @@ The following example shows an interactive grid in which searching has been enab Enter search criteria in the boxes under the columns to filter the data. Click the search icon again to clear the filters. -Click on a column to sort by that column. Clicking on a cell in a column automatically expands the +Click a column to sort by that column. Clicking on a cell in a column automatically expands the column size to fit the largest length of text contained in the column. ## Searching Enumerated Tables @@ -35,7 +35,7 @@ types to display as enumerated tables. To change the enumeration in the report, select an option from the enumerated column list. When enumeration is set on an interactive grid, a second download button is displayed with the name of -the currently selected enumerated column. You can use this to download a CSV file that only contains +the selected enumerated column. You can use this to download a CSV file that only contains the data for the selected enumeration. ## Filtering on Dates & Times @@ -45,12 +45,12 @@ filter on specific time periods. ![Date column filter](/images/accessanalyzer/12.0/admin/report/interactivegrids/datefilter.webp) -Enter a Start and End date and select the desired time period. +Enter a Start and End date and select the time period you want. ## Filtering on Numeric Columns -Comparison operators can also be used for filtering. Comparison operators which can be used for -filtering include the following: +Use comparison operators to filter data. The available comparison operators include the +following: | Description | Operator | | ------------------------ | -------- | @@ -67,5 +67,5 @@ Columns can be added or removed from the table. ![Add and remove columns](/images/accessanalyzer/12.0/admin/report/interactivegrids/addremovecolumns.webp) -Right-click on a column to display a list of the available columns. Select the checkboxes of the +Right-click a column to display a list of the available columns. Select the checkboxes of the columns you want to be displayed. Click the up or down arrows to scroll through the list of columns. diff --git a/docs/accessanalyzer/12.0/admin/report/overview.md b/docs/accessanalyzer/12.0/admin/report/overview.md index 8e00f92d8f..ec32024e74 100644 --- a/docs/accessanalyzer/12.0/admin/report/overview.md +++ b/docs/accessanalyzer/12.0/admin/report/overview.md @@ -6,7 +6,7 @@ sidebar_position: 110 # Reporting -Access Analyzer provides the ability to report on collected data in multiple ways such as tables, +Access Analyzer lets you report on collected data in multiple ways such as tables, views, graphs, and emails. Depending on the type of data collected, different reporting methods can simplify how to present and understand the information. diff --git a/docs/accessanalyzer/12.0/admin/report/tags.md b/docs/accessanalyzer/12.0/admin/report/tags.md index eac344ce7d..de757165d4 100644 --- a/docs/accessanalyzer/12.0/admin/report/tags.md +++ b/docs/accessanalyzer/12.0/admin/report/tags.md @@ -8,7 +8,7 @@ sidebar_position: 60 Tags can be added to reports to describe the content of the report and use cases for the report. For example, tags can be included in a report to show the compliance frameworks to which the report -maps. To view tags or click on tag links, reports must be viewed in the Web Console. Tags are not +maps. To view tags or click tag links, reports must be viewed in the Web Console. Tags aren't supported in reports in the Jobs tree. ![Web Console Home Page](/images/accessanalyzer/12.0/admin/report/webconsolehome.webp) @@ -20,7 +20,7 @@ the Tags tab in the Navigation section on the right-hand side of the Published R |:-----------------------------------------------------------------------------------------------------:|:--------------------------------------------------------------------------------------------------------------:| | *Privileged Accounts Tag on Published Reports homepage* | *Privileged Accounts Tag page* | -Click on a tag to view all reports that contain the selected tag. +Click a tag to view all reports that contain the selected tag. ![Job Group view in the Web Console](/images/accessanalyzer/12.0/admin/report/jobgroupview.webp) @@ -31,13 +31,13 @@ name. ![Report header](/images/accessanalyzer/12.0/admin/report/reportheader.webp) When viewing a report in either the Web Console or the Access Analyzer console, tags are displayed -below the report title. Click on a tag to view all reports that contain that tag. If the tag is +below the report title. Click a tag to view all reports that contain that tag. If the tag is selected from the Reports view in the Access Analyzer Console, the Published Reports Web Console opens and direct users to the tag page. ## Default Tags in Reports -The following sections list out of the box reports that contain each tag. The tags are: +The following sections list the default reports that contain each tag. The tags are: ### Open Access diff --git a/docs/accessanalyzer/12.0/admin/report/view.md b/docs/accessanalyzer/12.0/admin/report/view.md index 07b1c0165e..5bcc441c72 100644 --- a/docs/accessanalyzer/12.0/admin/report/view.md +++ b/docs/accessanalyzer/12.0/admin/report/view.md @@ -21,7 +21,7 @@ report is unpublished, the report is still displayed here. ![Report in the Results node](/images/accessanalyzer/12.0/admin/report/viewresultsnode.webp) -Select the desired report to be viewed. The report displays in the Results pane of the console. +Select the report you want to view. The report displays in the Results pane of the console. ![Access report from configure page](/images/accessanalyzer/12.0/admin/report/viewconfigure.webp) @@ -45,7 +45,7 @@ that solution’s job group. This list includes reports with changed Publish Pat Clicking a report name link opens the selected report, or navigate through the folders to select a report. -From within the Web Console, reports cannot be edited or deleted. However, the interactive grid +From within the Web Console, reports can't be edited or deleted. However, the interactive grid functions are enabled. See the [Interactive Grids](/docs/accessanalyzer/12.0/admin/report/interactivegrids/overview.md) topic for additional information. An additional feature available within the Web Console is the option to download data as a CSV file, which can be enabled for grid elements. This exports the data within diff --git a/docs/accessanalyzer/12.0/admin/report/wizard/authoring.md b/docs/accessanalyzer/12.0/admin/report/wizard/authoring.md index 49e7b310e1..be55950f61 100644 --- a/docs/accessanalyzer/12.0/admin/report/wizard/authoring.md +++ b/docs/accessanalyzer/12.0/admin/report/wizard/authoring.md @@ -41,17 +41,15 @@ Configure the following settings as required: [Report Settings Tab](/docs/accessanalyzer/12.0/admin/jobs/job/properties/reportsettings.md) topics for additional information.) - Publish report – Select this option to publish the report - - Do not publish report – Select this option to not publish the report + - Don't publish report – Select this option to not publish the report - Publish State – Shows the current publish state of the report. If the report is already published, you can click the link to open the report in the Web Console. ## Add Tags to a Report You can add tags to reports to describe the content and use cases of the report (see the -[Tags](/docs/accessanalyzer/12.0/admin/report/tags.md) topic for additional information). The Tag Editor allows you to select the tags -for a report, including creating new ones to select. - -Follow the steps to select tags using the Tag Editor. +[Tags](/docs/accessanalyzer/12.0/admin/report/tags.md) topic for additional information). Use the Tag Editor to select the tags +for a report, including creating new ones. **Step 1 –** On the Authoring page of the Report Configuration wizard, click the **Edit** button located next to the Tags text box. @@ -62,7 +60,7 @@ located next to the Tags text box. report. - In addition to selecting existing tags, you can also add new tags to be selected. To create a tag, - enter the desired tag name in the text box and click **Add**. + enter the tag name in the text box and click **Add**. **Step 3 –** Click **OK**. diff --git a/docs/accessanalyzer/12.0/admin/report/wizard/email.md b/docs/accessanalyzer/12.0/admin/report/wizard/email.md index 574943f913..5f746d5ed6 100644 --- a/docs/accessanalyzer/12.0/admin/report/wizard/email.md +++ b/docs/accessanalyzer/12.0/admin/report/wizard/email.md @@ -26,7 +26,7 @@ for additional information. ::: -To configure the setting for the report, use the Settings drop-down menu to select one of the +To configure the setting for the report, use the Settings dropdown menu to select one of the following options: - Use default setting – The default option. Applies the Global notification settings, or whatever @@ -34,9 +34,9 @@ following options: **Email this report** is enabled by default, then using this option sends the report to the recipients configured at the parent level where the inheritance begins. - Email this report – Select this option if you want to email the report and the inherited setting - is **Do not email this report**, or if you want to configure specific email settings for the + is **Don't email this report**, or if you want to configure specific email settings for the report. If it is selected, you must then configure the additional fields below. -- Do not email this report – Select this option to not email the report +- Don't email this report – Select this option to not email the report ![Settings configured to email the report](/images/accessanalyzer/12.0/admin/report/wizard/emailconfigured.webp) @@ -55,7 +55,7 @@ configure: `[ReportName]`variable being automatically populated. - Send-To / Send-Cc / Send-Bcc – Enter the email addresses of the required recipients for the email notification. Use a semicolon (;) to separate multiple recipients. -- Do not e-mail this report if blank – Select this checkbox to not email the report if all elements +- Don't e-mail this report if blank – Select this checkbox to not email the report if all elements of it are blank when it is generated - A blank report can occur if there is an error in data collection or if the report is configured for data which might not always be present (for example, new computer objects diff --git a/docs/accessanalyzer/12.0/admin/report/wizard/layout.md b/docs/accessanalyzer/12.0/admin/report/wizard/layout.md index b3185c749c..51a93c1bce 100644 --- a/docs/accessanalyzer/12.0/admin/report/wizard/layout.md +++ b/docs/accessanalyzer/12.0/admin/report/wizard/layout.md @@ -6,16 +6,16 @@ sidebar_position: 40 # Layout Page -The Layout page allows you to configure the layout of the report's content. +Use the Layout page to configure the layout of the report's content. ![layout](/images/accessanalyzer/12.0/admin/report/wizard/layout.webp) -Follow the steps to select the layout: +To select the layout: -**Step 1 –** Click the **Select the number of rows** drop-down menu and select an option from: 1 +**Step 1 –** Click the **Select the number of rows** dropdown menu and select an option from: 1 row, 2 rows, or 3 rows. -**Step 2 –** Click on the layout tile you want for the report. +**Step 2 –** Click the layout tile you want for the report. The layout for the report has been selected. Each box on the selected tile corresponds to a separate widget that you next need to configure on the [Widgets Page](/docs/accessanalyzer/12.0/admin/report/wizard/widgets.md) page of the Report diff --git a/docs/accessanalyzer/12.0/admin/report/wizard/overview.md b/docs/accessanalyzer/12.0/admin/report/wizard/overview.md index 6793558de6..96a035df4c 100644 --- a/docs/accessanalyzer/12.0/admin/report/wizard/overview.md +++ b/docs/accessanalyzer/12.0/admin/report/wizard/overview.md @@ -10,10 +10,8 @@ You can use the Report Configuration Wizard to configure reports. The wizard can existing report or when creating a new report. See the [Creating a Report](/docs/accessanalyzer/12.0/admin/report/create.md) and [Editing Existing Reports](/docs/accessanalyzer/12.0/admin/report/edit.md) topics for additional information. -Follow the steps to configure a report using the wizard. - :::note -Skip any sections or pages that do not require changes to the existing configuration. +Skip any sections or pages that don't require changes to the existing configuration. ::: @@ -27,18 +25,18 @@ specific settings. Click **Next**. **Step 4 –** The [Publish Security Page](/docs/accessanalyzer/12.0/admin/report/wizard/publishsecurity.md) page is only enabled if role-based access is configured for the Access Analyzer console. On this page you can view and configure -accounts with permissions to view the report. If you are not using role-based access, you can skip +accounts with permissions to view the report. If you aren't using role-based access, you can skip this page. Click **Next**. **Step 5 –** On the [Layout Page](/docs/accessanalyzer/12.0/admin/report/wizard/layout.md) page, select the number of rows using the dropdown -menu. Then select the desired pre-defined layout from the options displayed. Click **Next**. +menu. Then select the pre-defined layout you want from the options displayed. Click **Next**. **Step 6 –** On the [Widgets Page](/docs/accessanalyzer/12.0/admin/report/wizard/widgets.md) page, configure widgets for each element of the layout. **Step 7 –** Click **Finish** to save your changes. -- If you do not want to save your changes or have not made any changes, click **Cancel** on any page +- If you don't want to save your changes or have not made any changes, click **Cancel** on any page to exit the wizard without saving your changes. Your configuration has been saved. For information on how to view your report, see the diff --git a/docs/accessanalyzer/12.0/admin/report/wizard/publishsecurity.md b/docs/accessanalyzer/12.0/admin/report/wizard/publishsecurity.md index c04792d778..537169b571 100644 --- a/docs/accessanalyzer/12.0/admin/report/wizard/publishsecurity.md +++ b/docs/accessanalyzer/12.0/admin/report/wizard/publishsecurity.md @@ -32,7 +32,7 @@ steps to add an account. ![Select User, Service Account, or Group window](/images/accessanalyzer/12.0/admin/report/wizard/addreportviewer.webp) -**Step 2 –** On the Select User, Service Account or Group window, select the desired account and +**Step 2 –** On the Select User, Service Account or Group window, select the account you want and then click **OK**. ![Report Viewer user added in wizard](/images/accessanalyzer/12.0/admin/report/wizard/reportviewer.webp) @@ -40,7 +40,7 @@ then click **OK**. The selected account is added to the list with a Role of Report Viewer. :::note -The permission for accounts that are not Inherited can also be removed using the wizard. +The permission for accounts that aren't Inherited can also be removed using the wizard. To remove an account, select it and then click **Remove**. ::: diff --git a/docs/accessanalyzer/12.0/admin/report/wizard/widgets.md b/docs/accessanalyzer/12.0/admin/report/wizard/widgets.md index 11f4367544..b6f8853cb0 100644 --- a/docs/accessanalyzer/12.0/admin/report/wizard/widgets.md +++ b/docs/accessanalyzer/12.0/admin/report/wizard/widgets.md @@ -16,7 +16,7 @@ locations where widgets need to be configured. ![Configure widgets](/images/accessanalyzer/12.0/admin/report/wizard/widgetsconfigure.webp) -To add a new widget to an empty element, click **Configure** and select the desired widget type from +To add a new widget to an empty element, click **Configure** and select the widget type you want from the dropdown menu. The following widgets are available: - [Grid](#grid) diff --git a/docs/accessanalyzer/12.0/admin/runninginstances/jobdetails.md b/docs/accessanalyzer/12.0/admin/runninginstances/jobdetails.md index 2dfe497db7..5d7d08f1b5 100644 --- a/docs/accessanalyzer/12.0/admin/runninginstances/jobdetails.md +++ b/docs/accessanalyzer/12.0/admin/runninginstances/jobdetails.md @@ -38,7 +38,7 @@ The tab includes: - Status – Execution status, for example **Queued**, **Running**, **Success**, or **Warning**. - Message – Access Analyzer message regarding runtime activity - Runtime – Duration of task execution -- Stop – Aborts all currently running instances +- Stop – Aborts all running instances ## History Tab diff --git a/docs/accessanalyzer/12.0/admin/runninginstances/overview.md b/docs/accessanalyzer/12.0/admin/runninginstances/overview.md index 08ffe7f89e..9c12237199 100644 --- a/docs/accessanalyzer/12.0/admin/runninginstances/overview.md +++ b/docs/accessanalyzer/12.0/admin/runninginstances/overview.md @@ -43,13 +43,13 @@ It also has hyperlinks for: Clicking on any of the hyperlinks displays more information about the running job. The **ProcessID**, **View Details, View Log**, and **Stop** links only work while the job is running. -Once the job is complete, these links are disabled. The host and Connection Profile links continue +After the job is complete, these links are disabled. The host and Connection Profile links continue to work. The **View Schedule** link only displays and is valid for jobs that are running via a -scheduled task and is not enabled for interactive job executions. +scheduled task and isn't enabled for interactive job executions. ![Number of jobs running on bottom bar](/images/accessanalyzer/12.0/admin/runninginstances/overviewbottombar.webp) -The number of jobs currently being run can be found in the lower-left-hand corner of the Access +The number of jobs being run can be found in the lower-left-hand corner of the Access Analyzer Console. ## View Host diff --git a/docs/accessanalyzer/12.0/admin/schedule/overview.md b/docs/accessanalyzer/12.0/admin/schedule/overview.md index 2f018bdfee..89586fbefb 100644 --- a/docs/accessanalyzer/12.0/admin/schedule/overview.md +++ b/docs/accessanalyzer/12.0/admin/schedule/overview.md @@ -35,7 +35,7 @@ Jobs can be scheduled at the job group or job level. ![Schedule option from Job Tree](/images/accessanalyzer/12.0/admin/schedule/jobtree.webp) -Select the desired job group or job. Right-click on the node and select **Schedule** to open the +Select the job group or job you want. Right-click the node and select **Schedule** to open the Schedule wizard. ![Schedule Job wizard](/images/accessanalyzer/12.0/admin/schedule/schedule.webp) diff --git a/docs/accessanalyzer/12.0/admin/schedule/renamewizard.md b/docs/accessanalyzer/12.0/admin/schedule/renamewizard.md index 9c810df14a..1c0a23a96c 100644 --- a/docs/accessanalyzer/12.0/admin/schedule/renamewizard.md +++ b/docs/accessanalyzer/12.0/admin/schedule/renamewizard.md @@ -12,11 +12,11 @@ to provide the credentials needed for the scheduled task, so that the task is st after it has been renamed. Custom credentials are configured on the Run as page of the Schedule wizard. See the [Run As](wizard.md#run-as) topic for additional information. -If a scheduled task does not contain custom credentials, then the job, job group, inventory query, +If a scheduled task doesn't contain custom credentials, then the job, job group, inventory query, or discovery query can be renamed and the scheduled task is automatically renamed without requiring the wizard. -Follow the steps to update the credential for a scheduled task. +Update the credential for a scheduled task. ![Rename Scheduled Task wizard Tasks page](/images/accessanalyzer/12.0/admin/schedule/tasks.webp) @@ -29,7 +29,7 @@ for and click **Update**. ![Group with multiple sub-group credentials to be updated](/images/accessanalyzer/12.0/admin/schedule/taskssubgroups.webp) - If you are renaming a group that has sub-groups that use custom credentials, then the wizard - displays these accounts even if the parent group does not use custom credentials. For sub-groups, + displays these accounts even if the parent group doesn't use custom credentials. For sub-groups, the table additionally shows the path to the sub-group, and only the sub-groups that have custom credentials set are displayed in the wizard. If there are multiple groups requiring credentials, then all of them must be updated. @@ -59,7 +59,7 @@ renamed. ![Rename Scheduled Task wizard Progress page](/images/accessanalyzer/12.0/admin/schedule/progress.webp) -**Step 5 –** The Progress page shows a progress bar and message. Once the scheduled tasks have been +**Step 5 –** The Progress page shows a progress bar and message. After the scheduled tasks are renamed successfully, click **Finish** to close the wizard. The scheduled tasks have now been renamed and will run as before . The modified task name shows in diff --git a/docs/accessanalyzer/12.0/admin/schedule/wizard.md b/docs/accessanalyzer/12.0/admin/schedule/wizard.md index 6b34dccbf0..16ec0d387f 100644 --- a/docs/accessanalyzer/12.0/admin/schedule/wizard.md +++ b/docs/accessanalyzer/12.0/admin/schedule/wizard.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Schedule Wizard -The schedule wizard allows you to configure scheduled tasks for jobs, job groups, Host Discovery +Use the schedule wizard to configure scheduled tasks for jobs, job groups, Host Discovery queries, and Host Inventory queries. The wizard has five wizard pages with options for setting up the schedule task: @@ -54,7 +54,7 @@ The options in the Trigger window are: Days [value] of the month or the [value] [Day of the Week] of the month. By default, this is set to recur every month. To select only specific months, use Months dropdown menu and deselect the undesired months. - - The drop-down menu next to **Start** opens a calendar view for selecting the date + - The dropdown menu next to **Start** opens a calendar view for selecting the date - Selecting the **Synchronize across time zones** checkbox will synchronize the scheduled task to run without respect to the time zone @@ -78,7 +78,7 @@ configuration of this tab is optional. ![Host List wizard page](/images/accessanalyzer/12.0/admin/schedule/hostlist.webp) -Choose the desired setting from the following options: +Choose the setting you want from the following options: - Use Host list from Job – A default setting and applies the host list designated at the job or job group level. This is also the recommended setting. @@ -95,7 +95,7 @@ queried by the task being scheduled. Customizations to the configuration of this ![Connection wizard page](/images/accessanalyzer/12.0/admin/schedule/connection.webp) -Choose the desired setting from the following options: +Choose the setting you want from the following options: - Use Profile from Job – A default setting and applies the Connection Profile designated at the job or job group level @@ -123,7 +123,7 @@ The options on the Run as wizard page are: - Use default Schedule Service Account – Uses the default Schedule Service Account that is set at the **Settings** > **Schedule** node - Use selected Schedule Service Account – Select the Schedule Service Account to use for the task - from a list of available accounts in the drop-down menu + from a list of available accounts in the dropdown menu - Use Custom Credentials – Use custom credentials not stored in the Access Analyzer Console. Enter the User Name for the custom credentials. diff --git a/docs/accessanalyzer/12.0/admin/schema/sqldc/coretables/overview.md b/docs/accessanalyzer/12.0/admin/schema/sqldc/coretables/overview.md index f0ffba48f0..02edc15bb3 100644 --- a/docs/accessanalyzer/12.0/admin/schema/sqldc/coretables/overview.md +++ b/docs/accessanalyzer/12.0/admin/schema/sqldc/coretables/overview.md @@ -49,7 +49,7 @@ |---|---|---|---|---|---|---|---| | id | int | | No | PK | | IDENTITY | Surrogate primary key | | instance_id | int | | No | | | | Reference to the hosting SQL Server instance | -| active_database_id | int | | Yes | | FK | | FK to `SA_SQLServer_Databases.id`; links to the currently active database record | +| active_database_id | int | | Yes | | FK | | FK to `SA_SQLServer_Databases.id`; links to the active database record | | name | nvarchar | 128 | No | | | | Database name as recorded in audit events | | minimum_event_datetime | datetime2 | | Yes | | | | Earliest event timestamp recorded for this database | @@ -715,7 +715,7 @@ **Indexes:** `UQ_SA_SQLServer_Events_StaleDataLookup` on `(file_id, event_time)` (nonclustered, non-unique despite UQ_ prefix) -> **Note:** Despite the `UQ_` prefix used in some environments, this index is **not unique** per the live schema (`is_unique = 0`). +> **Note:** Despite the `UQ_` prefix used in some environments, this index **isn't unique** per the live schema (`is_unique = 0`). --- @@ -950,7 +950,7 @@ | instance_id | int | | No | PK | | IDENTITY | Auto-incrementing surrogate primary key | | instance_label | nvarchar | 256 | No | | | | Unique display label for the instance | | service_name | nvarchar | 128 | Yes | | | | Named instance or service/database name | -| is_active | bit | | No | | | `1` | Whether the instance is currently active for data collection | +| is_active | bit | | No | | | `1` | Whether the instance is active for data collection | | enable_impersonation | bit | | No | | | `0` | Whether Windows impersonation is enabled for connecting to this instance | | database_type | int | | No | | | | Database platform type (see Section 6.11) | | host_name | nvarchar | 150 | No | | | | Server hostname or IP address | diff --git a/docs/accessanalyzer/12.0/admin/schema/sqldc/enumeration/overview.md b/docs/accessanalyzer/12.0/admin/schema/sqldc/enumeration/overview.md index 8ff9afaedf..9dbf419d41 100644 --- a/docs/accessanalyzer/12.0/admin/schema/sqldc/enumeration/overview.md +++ b/docs/accessanalyzer/12.0/admin/schema/sqldc/enumeration/overview.md @@ -265,13 +265,13 @@ Used to compute the `Database Type` column in `SA_SQLServer_EffectiveRoleMembers | `5` | MySql | MySQL | | `6` | AzureSqlServerManagedInstance | Azure SQL Managed Instance | | `7` | SaDataSource | StealthAUDIT Data Source | -| `8` | AWSPostgres | AWS PostgreSQL (not currently supported) | -| `9` | AWSMySql | AWS MySQL (not currently supported) | -| `10` | EDBPostgreSql | EDB PostgreSQL (not currently supported) | -| `11` | SqlServerCluster | SQL Server Cluster (not currently supported) | +| `8` | AWSPostgres | AWS PostgreSQL (not supported) | +| `9` | AWSMySql | AWS MySQL (not supported) | +| `10` | EDBPostgreSql | EDB PostgreSQL (not supported) | +| `11` | SqlServerCluster | SQL Server Cluster (not supported) | | `12` | Db2LUW | IBM Db2 LUW | | `20` | MongoDb | MongoDB | :::note Within the SQL Server Data Collector context, only values `0` (Unset), `1` (SqlServer), `2` (AzureSqlServer), and `6` (AzureSqlServerManagedInstance) are applicable. The remaining values are used by other database collector modules that share the `SA_SQL_Instances` table. -::: \ No newline at end of file +::: diff --git a/docs/accessanalyzer/12.0/admin/schema/sqldc/reportingtables/overview.md b/docs/accessanalyzer/12.0/admin/schema/sqldc/reportingtables/overview.md index 024266a3db..bb5584d4c6 100644 --- a/docs/accessanalyzer/12.0/admin/schema/sqldc/reportingtables/overview.md +++ b/docs/accessanalyzer/12.0/admin/schema/sqldc/reportingtables/overview.md @@ -1,6 +1,6 @@ # Reporting Tables -The following 59 tables are **denormalized reporting tables** populated by NAA analysis jobs. They use human-readable column names with spaces (e.g., `"Database Type"`, `"Instance"`) and are designed for direct consumption by the NAA console and reports. They do not participate in foreign key relationships with the core tables. +The following 59 tables are **denormalized reporting tables** populated by NAA analysis jobs. They use human-readable column names with spaces (e.g., `"Database Type"`, `"Instance"`) and are designed for direct consumption by the NAA console and reports. They don't participate in foreign key relationships with the core tables. :::note All reporting tables share a common `Database Type` column (varchar/nvarchar) that identifies the SQL Server platform variant (e.g., `"SQL Server"`, `"Azure SQL Database"`, `"Azure SQL Managed Instance"`). None of these tables have primary keys or foreign keys — they are heap tables optimized for bulk INSERT/TRUNCATE patterns. @@ -625,7 +625,7 @@ All reporting tables share a common `Database Type` column (varchar/nvarchar) th | Database | nvarchar | 128 | Yes | | Database name | | Schema | nvarchar | 128 | Yes | | Schema name | | Table | nvarchar | 128 | Yes | | Table name containing sensitive data | -| Criteria | nvarchar | MAX | Yes | | Matched SDD criteria name(s) | +| Criteria | nvarchar | MAX | Yes | | Matched SDD criteria names | | Table Row Count | bigint | | Yes | | Total rows in the table | | Match Count | bigint | | Yes | | Number of sensitive data matches | | Match Types | nvarchar | MAX | Yes | | Types of matches found | @@ -679,7 +679,7 @@ All reporting tables share a common `Database Type` column (varchar/nvarchar) th | Client | nvarchar | 128 | Yes | | Client IP or hostname | | Application | nvarchar | 128 | Yes | | Application name | | Action | nvarchar | 56 | Yes | | Action type (SELECT, INSERT, UPDATE, etc.) | -| Criteria | nvarchar | 256 | Yes | | SDD criteria name(s) for the object | +| Criteria | nvarchar | 256 | Yes | | SDD criteria names for the object | | Match Data | nvarchar | 256 | Yes | | Sample match data | --- @@ -710,7 +710,7 @@ All reporting tables share a common `Database Type` column (varchar/nvarchar) th | Instance | nvarchar | 128 | Yes | | SQL Server instance name | | Database | nvarchar | 128 | Yes | | Database name | | Object | nvarchar | 128 | Yes | | Object name containing sensitive data | -| Criteria | nvarchar | MAX | Yes | | SDD criteria name(s) | +| Criteria | nvarchar | MAX | Yes | | SDD criteria names | | Permission | nvarchar | 128 | Yes | | Permission name | | Grantee | nvarchar | 513 | Yes | | Grantee principal | | Grantee Id | nvarchar | 128 | Yes | | Grantee identifier | diff --git a/docs/accessanalyzer/12.0/admin/schema/sqldc/views/overview.md b/docs/accessanalyzer/12.0/admin/schema/sqldc/views/overview.md index 2d74f9ba6a..06a84c8dd1 100644 --- a/docs/accessanalyzer/12.0/admin/schema/sqldc/views/overview.md +++ b/docs/accessanalyzer/12.0/admin/schema/sqldc/views/overview.md @@ -117,7 +117,7 @@ | is_policy_checked | bit | | No | SA_SQLServer_SqlLogins.is_policy_checked | Whether password policy is enforced | | is_expiration_checked | bit | | No | SA_SQLServer_SqlLogins.is_expiration_checked | Whether password expiration is enforced | | password_hash | varbinary | 256 | Yes | SA_SQLServer_SqlLogins.password_hash | Hashed password value | -| is_locked | bit | | Yes | SA_SQLServer_SqlLogins.is_locked | Whether the account is currently locked out | +| is_locked | bit | | Yes | SA_SQLServer_SqlLogins.is_locked | Whether the account is locked out | | is_expired | bit | | Yes | SA_SQLServer_SqlLogins.is_expired | Whether the password has expired | | is_must_change | bit | | Yes | SA_SQLServer_SqlLogins.is_must_change | Whether the password must be changed at next login | | password_hash_algorithm | int | | Yes | SA_SQLServer_SqlLogins.password_hash_algorithm | Algorithm used to hash the password | diff --git a/docs/accessanalyzer/12.0/admin/settings/access/restapi/assignappaccess.md b/docs/accessanalyzer/12.0/admin/settings/access/restapi/assignappaccess.md index 0ba777e48c..2f702889a0 100644 --- a/docs/accessanalyzer/12.0/admin/settings/access/restapi/assignappaccess.md +++ b/docs/accessanalyzer/12.0/admin/settings/access/restapi/assignappaccess.md @@ -6,8 +6,8 @@ sidebar_position: 10 # Assign Application Access through the Web Service -An application can be assigned to access data remotely through the Web Service. Follow the steps to -assign roles in the Console. +An application can be assigned to access data remotely through the Web Service. Assign roles in the +Console: ![Add Access option on Access page](/images/accessanalyzer/12.0/admin/settings/access/rolebased/addaccess.webp) @@ -50,11 +50,11 @@ name** box to filter the list of objects by the characters entered. app token. - Application name – The name of the application accessing that data -- Access Expiration – The expiration for the client secret. Select an option for the desired access - expiration: +- Access Expiration – The expiration for the client secret. Select the access expiration option + you want: - - Access expires within – Select a time frame from the drop-down list. The default is 72 hours. - - Access expires on specified date – Select a date from the drop-down list + - Access expires within – Select a time frame from the dropdown list. The default is 72 hours. + - Access expires on specified date – Select a date from the dropdown list - Generate – Click this button to generate the Client ID and Client secret - Client ID – Copy the Client ID into the application accessing data remotely through the Web diff --git a/docs/accessanalyzer/12.0/admin/settings/access/restapi/getdata.md b/docs/accessanalyzer/12.0/admin/settings/access/restapi/getdata.md index 34b83c7c1a..aa93ced752 100644 --- a/docs/accessanalyzer/12.0/admin/settings/access/restapi/getdata.md +++ b/docs/accessanalyzer/12.0/admin/settings/access/restapi/getdata.md @@ -28,7 +28,7 @@ GET, POST - **object-name** – Required value that specifies the unique object name. - **alias-name** – Required value that specifies the unique alias associated with the table, available as a more thoughtfully designed namespace. - **jobRuntimeKey**(Optional) – The execution to retrieve information for. If this is omitted the latest report is provided. -- **filters** (Optional) – A filter to be applied prior to returning data, multiple filters are applied with `and` operators. If an array is specified for the value field for a filter, the filter returns any successful match from the array of values. String comparisons are case insensitive. A list of the available functions is below. Filter functions: +- **filters** (Optional) – A filter to be applied before returning data, multiple filters are applied with `and` operators. If an array is specified for the value field for a filter, the filter returns any successful match from the array of values. String comparisons are case insensitive. A list of the available functions is below. Filter functions: - equals - not_equals - greater (greater_equal) @@ -81,7 +81,7 @@ Sample JSON response: **ERRORS** - 400 One or more the parameters passed in are invalid. -- 404 The object requested does not exist. +- 404 The object requested doesn't exist. ## PROC @@ -100,7 +100,7 @@ POST **PARAMETERS** - **object-name** – Required value that specifies the unique object name. -- **groupby**(Optional) – A list of columns to group each row by, resulting in a JSON object that contains those keys followed by an array of entries. The parameters passed in here are passed to the stored procedure untouched. Arrays are mapped to a user defined table type, currently only single value arrays are supported. +- **groupby**(Optional) – A list of columns to group each row by, resulting in a JSON object that contains those keys followed by an array of entries. The parameters passed in here are passed to the stored procedure untouched. Arrays are mapped to a user defined table type, only single value arrays are supported. Sample JSON request: @@ -139,4 +139,4 @@ Sample JSON request: **ERRORS** - 400 One or more the parameters passed in are invalid. -- 404 The object requested does not exist. +- 404 The object requested doesn't exist. diff --git a/docs/accessanalyzer/12.0/admin/settings/access/restapi/obtaintoken.md b/docs/accessanalyzer/12.0/admin/settings/access/restapi/obtaintoken.md index 4fd23ba3f2..c081205113 100644 --- a/docs/accessanalyzer/12.0/admin/settings/access/restapi/obtaintoken.md +++ b/docs/accessanalyzer/12.0/admin/settings/access/restapi/obtaintoken.md @@ -38,7 +38,7 @@ article for additional information. ::: -If the token does not have the ability to perform this request, is invalid, or the specific resource +If the token doesn't have the ability to perform this request, is invalid, or the specific resource has been blocked from access remotely, an HTTP status code of 401 is returned. If the request for an access token is valid, the authorization server generates an access token and diff --git a/docs/accessanalyzer/12.0/admin/settings/access/restapi/refreshtoken.md b/docs/accessanalyzer/12.0/admin/settings/access/restapi/refreshtoken.md index a52d82f245..1f362eb0c9 100644 --- a/docs/accessanalyzer/12.0/admin/settings/access/restapi/refreshtoken.md +++ b/docs/accessanalyzer/12.0/admin/settings/access/restapi/refreshtoken.md @@ -11,8 +11,8 @@ refresh token when the access token expires. - `grant_type` (Required) – The `grant_type` parameter must be set to `client_credentials` - `refresh_token` (Required) – The refresh token previously issue to the client -- `scope` (Optional) – The requested scope must not include additional scopes that were not issued - in the original access token. If the scope is not included in the request, the service issues an +- `scope` (Optional) – The requested scope must not include additional scopes that weren't issued + in the original access token. If the scope isn't included in the request, the service issues an access token with the same scope as previously issued. - Client Authentication – Required if the client was issued a secret @@ -30,11 +30,11 @@ grant_type=refresh_token &client_secret=xxxxxxxxxx ``` -If the token does not have the ability to perform this request, is invalid, or the specific resource +If the token doesn't have the ability to perform this request, is invalid, or the specific resource has been blocked from access remotely, an HTTP status code of 401 is returned. The response for a refresh token is the same as the response for an access token. Optionally, a new -refresh token can be included in the response. If a new refresh token is not included in the +refresh token can be included in the response. If a new refresh token isn't included in the response, the current refresh token will continue to be valid. The following example shows a successful access token response: diff --git a/docs/accessanalyzer/12.0/admin/settings/access/rolebased/assignroles.md b/docs/accessanalyzer/12.0/admin/settings/access/rolebased/assignroles.md index bfb8323205..1fce927d89 100644 --- a/docs/accessanalyzer/12.0/admin/settings/access/rolebased/assignroles.md +++ b/docs/accessanalyzer/12.0/admin/settings/access/rolebased/assignroles.md @@ -17,7 +17,7 @@ roles and enable Role Based Access. ::: -Follow the steps to assign roles in the Access Analyzer Console. +Assign roles in the Access Analyzer Console: ![Add Access option on the Access page](/images/accessanalyzer/12.0/admin/settings/access/rolebased/addaccess.webp) @@ -37,7 +37,7 @@ ellipsis (**…**) to browse for accounts with the Select User or Group window. [Group Managed Service Accounts](https://learn.microsoft.com/en-us/windows-server/security/group-managed-service-accounts/group-managed-service-accounts-overview) article for additional information. - - Change the location to the desired domain and click **Object Types**, then select **Service + - Change the location to the domain you want and click **Object Types**, then select **Service Accounts**. - Add the gMSA name (`gMSAadmin$`), then click **OK**. - The Member Type will show as `msDS-GroupManagedServiceAccount` on the Access page. @@ -50,11 +50,11 @@ user and role is added to the Role Membership list in the Roles view. **Step 5 –** Repeat Steps 1-4 to assign roles to other groups or users. **Step 6 –** Click **Save** and then **OK** to confirm the changes. All applied roles are lost if -they are not saved. +they aren't saved. Role Based Access is enabled when the first role has been assigned. -![Error message when Administrator role is not specified](/images/accessanalyzer/12.0/admin/settings/access/rolebased/noadminerror.webp) +![Error message when Administrator role isn't specified](/images/accessanalyzer/12.0/admin/settings/access/rolebased/noadminerror.webp) The first role or set of roles saved must include the Administrator role. Clicking **Save** for the first role or set or roles without including the Administrator generates an error message in the @@ -64,11 +64,11 @@ When Role Based Access is first enabled, restart the Access Analyzer application are properly active. When saving roles for the first time, an NEAUsers local group is created on the Access Analyzer Console server with permissions to the Access Analyzer application directory. When users are assigned roles, they are added to this NEAUsers group to give them the necessary -permissions. This allows roles to be leveraged without requiring local Administrator rights. +permissions. This allows roles to be used without requiring local Administrator rights. :::note -The Web Administrator and Report Viewer roles do not require access to the Access Analyzer -console, so users assigned these roles are not added to the NEAUsers group. +The Web Administrator and Report Viewer roles don't require access to the Access Analyzer +console, so users assigned these roles aren't added to the NEAUsers group. ::: @@ -81,11 +81,11 @@ There are two separate sets of permissions: ## Edit Role Members' Responsibilities -Follow the steps to edit a Access Analyzer user’s role. +Edit an Access Analyzer user's role: ![Edit Member Role](/images/accessanalyzer/12.0/admin/settings/access/rolebased/editmemberrole.webp) -**Step 1 –** On the Access page, select the desired user and click **Edit Member Role**. +**Step 1 –** On the Access page, select the user and click **Edit Member Role**. ![Edit Console Access wizard page](/images/accessanalyzer/12.0/admin/settings/access/rolebased/consoleaccessedit.webp) @@ -96,7 +96,7 @@ Follow the steps to edit a Access Analyzer user’s role. **Step 4 –** Repeat Steps 1-3 to edit other users’ roles. **Step 5 –** Click **Save** and then **OK** to confirm the changes. All applied roles are lost if -they are not saved. +they aren't saved. The changed roles take affect the next time the users logs into the Access Analyzer application. If a user is actively logged into Access Analyzer at the same time the role for that user is changed, @@ -104,11 +104,11 @@ then the user needs to exit and re-launch the application for the role to take e ## Delete Role Member -Follow the steps to delete a user from having access to the Access Analyzer Console. +Delete a user's access to the Access Analyzer Console: ![Delete Role Member](/images/accessanalyzer/12.0/admin/settings/access/rolebased/deleterolemember.webp) -**Step 1 –** On the Access page, select the desired user and click **Delete Role Member**. The +**Step 1 –** On the Access page, select the user and click **Delete Role Member**. The selected user will be removed from the list. :::note @@ -120,7 +120,7 @@ is completed. **Step 2 –** Repeat Step 1 to remove other users as desired. **Step 3 –** Click **Save** and then **OK** to confirm the deletions. The users will not be deleted -if the changes are not saved. +if the changes aren't saved. The deleted users will no longer be able to log into the Access Analyzer application. If a user is actively logged into Access Analyzer at the same time of the deletion, the user will need to exit diff --git a/docs/accessanalyzer/12.0/admin/settings/access/rolebased/configureroles.md b/docs/accessanalyzer/12.0/admin/settings/access/rolebased/configureroles.md index 44168e3ca4..1df8150885 100644 --- a/docs/accessanalyzer/12.0/admin/settings/access/rolebased/configureroles.md +++ b/docs/accessanalyzer/12.0/admin/settings/access/rolebased/configureroles.md @@ -23,7 +23,7 @@ This is a three-part process: - Delete Role Members :::note -This configuration process is not required if only using Role Based Access to secure +This configuration process isn't required if only using Role Based Access to secure Published Reports. See the [Securing Published Reports Only](/docs/accessanalyzer/12.0/admin/settings/access/rolebased/securereports.md) topic for additional information. ::: @@ -32,7 +32,7 @@ information. ## Configure the Installation Account The Access Analyzer Installation Account is used both to perform the initial installation of Access -Analyzer and to change Storage Profile settings. It needs additional rights in order to query +Analyzer and to change Storage Profile settings. It needs additional rights to query objects in the master database. This is only necessary so the user can enumerate the available databases to choose from when configuring the Access Analyzer Storage Profile. @@ -56,15 +56,15 @@ GO ## Configure Roles in SQL Management Studio -It is necessary to provision rights to the SQL Server database so the Access Analyzer application +Provision rights to the SQL Server database so the Access Analyzer application rights and database access rights are consistent and provide the minimum rights necessary to support the Access Analyzer roles. This approach involves creating custom database roles which will be assigned rights and privileges. Then, individual domain user accounts must be assigned to these roles. :::note -For any SQL Server version prior to 2012, Windows groups cannot be used because SQL Server -does not allow the assignment of default schemas to Windows groups. Access Analyzer requires the +For any SQL Server version before 2012, Windows groups can't be used because SQL Server +doesn't allow the assignment of default schemas to Windows groups. Access Analyzer requires the default schema of [dbo] to function properly. ::: @@ -76,7 +76,7 @@ To create the roles within the SQL Server database, run the following script. ![Query Window](/images/accessanalyzer/12.0/admin/settings/access/rolebased/sqlcreateroles.webp) Be sure to set the context of this query to the Access Analyzer database by selecting the right -database from the drop-down window. Alternatively, prefix the script with a +database from the dropdown window. Alternatively, prefix the script with a `USE [Access Analyzer DATABASE NAME]` clause. ``` @@ -118,13 +118,13 @@ GO ``` -Once the script has been successfully executed, assign domain users to these database roles. +After the script executes successfully, assign domain users to these database roles. ### Assigning Users to SQL Roles Now that the SQL Server database roles have been created the next step is to assign domain users to -those roles. This can be done interactively in SQL Management Studio. Follow the steps to assign -users to SQL Server database roles. +those roles. This can be done interactively in SQL Management Studio. Assign users to SQL Server +database roles: **Step 1 –** Connect to the Access Analyzer database through SQL Management Studio. @@ -142,7 +142,7 @@ users to SQL Server database roles. | ![New User Option](/images/accessanalyzer/12.0/admin/settings/access/rolebased/sqlusersnewuser.webp) | **Step 3 –** After confirmation of role creation, the next step is to map users to these roles. -Right-click on the **Security** > **Users** node and select **New User**. +Right-click the **Security** > **Users** node and select **New User**. ![Database User Window](/images/accessanalyzer/12.0/admin/settings/access/rolebased/sqluserwindow.webp) diff --git a/docs/accessanalyzer/12.0/admin/settings/access/rolebased/customroles.md b/docs/accessanalyzer/12.0/admin/settings/access/rolebased/customroles.md index a7ba65d4c0..7f0ebe144f 100644 --- a/docs/accessanalyzer/12.0/admin/settings/access/rolebased/customroles.md +++ b/docs/accessanalyzer/12.0/admin/settings/access/rolebased/customroles.md @@ -10,7 +10,7 @@ A custom role can be created within Access Analyzer to combine the rights of oth Follow the steps below to create a custom role. **Step 1 –** In the Access Analyzer directory, navigate to **PrivateAssemblies** and edit the -**rba-roles.conf** file.  Add a new section for the custom role as shown in the following +**rba-roles.conf** file. Add a new section for the custom role as shown in the following instructions: ``` @@ -26,9 +26,9 @@ instructions: - Replace `Special User` between the double quotes in the script above with the name of the new role. - Replace `Description of Special User` between the double quotes in the script above with a - description of what a user assigned the new role is able to do. + description of what a user assigned the new role can do. -**Step 2 –** Add privileged values for the desired rights on new lines between the beginning comment +**Step 2 –** Add privileged values for the rights you want on new lines between the beginning comment `` and ending comment `` in the script above. - For example, to create a single role which has the same privileges as the Host Management @@ -40,7 +40,7 @@ See the sections below for examples of how roles should be added in the **rba-ro ## Default Global Options Administrator Privileges -The following example shows what is currently contained in the Global Options Administrator role, +The following example shows what is contained in the Global Options Administrator role, and how the created role should be added in the **rba-roles.conf** file. ``` @@ -85,7 +85,7 @@ and how the created role should be added in the **rba-roles.conf** file. ## Default Host Management Administrator Privileges -The following example shows what is currently contained in the Host Management Administrator role, +The following example shows what is contained in the Host Management Administrator role, and how the created role should be added in the **rba-roles.conf** file. ``` diff --git a/docs/accessanalyzer/12.0/admin/settings/access/rolebased/faq.md b/docs/accessanalyzer/12.0/admin/settings/access/rolebased/faq.md index 66ee5ad4b3..b1bc7f2c08 100644 --- a/docs/accessanalyzer/12.0/admin/settings/access/rolebased/faq.md +++ b/docs/accessanalyzer/12.0/admin/settings/access/rolebased/faq.md @@ -17,22 +17,22 @@ only locked jobs can be run. Therefore, the Job Initiator can only run or schedu already been locked. :::note -Locked jobs do not affect the functionality of the Administrator role. See the +Locked jobs don't affect the functionality of the Administrator role. See the [Role Definitions](/docs/accessanalyzer/12.0/admin/settings/access/rolebased/roledefinitions.md) topic for more information. ::: -How can I make sure that a lock on a job will not get tampered with through the associated XML file? +How does Access Analyzer protect a lock on a job from tampering through the associated XML file? The Scheduling Service Account provides limited rights for the Job Approver. Previously, the Job -Approver required permissions on the Jobs folder in order to apply the lock to a job. Now, the -credentials specified in the Scheduling Service Account will be used to apply the locks. Therefore, -the Job Approver no longer needs access to the Jobs folder and cannot manually remove or tamper with +Approver required permissions on the Jobs folder to apply the lock to a job. Now, Access Analyzer +uses the credentials specified in the Scheduling Service Account to apply the locks. Therefore, +the Job Approver no longer needs access to the Jobs folder and can't manually remove or tamper with the associated XML file. :::note -If using a Job Initiator’s credentials for a Schedule Service Account, all jobs must be -locked in order for them to be executed. See the [Role Definitions](/docs/accessanalyzer/12.0/admin/settings/access/rolebased/roledefinitions.md) and +If the Schedule Service Account uses a Job Initiator's credentials, all jobs must be +locked before they run. See the [Role Definitions](/docs/accessanalyzer/12.0/admin/settings/access/rolebased/roledefinitions.md) and [Roles & the Schedule Service Account](/docs/accessanalyzer/12.0/admin/settings/access/rolebased/scheduleserviceaccount.md) topics for more information. ::: @@ -41,33 +41,33 @@ Why can the Host Management Administrator not manage settings for the Host Disco Inventory nodes under Settings? The Host Management Administrator role is designed specifically to access the Host Management node. -Therefore, this role does not grant access to the global settings menu under the Settings node. +Therefore, this role doesn't grant access to the global settings menu under the Settings node. :::note -In order to access this node, the user must have either the Administrator or the Global +to access this node, the user must have either the Administrator or the Global Options Administrator role. See the [Role Definitions](/docs/accessanalyzer/12.0/admin/settings/access/rolebased/roledefinitions.md) topic for more information. ::: -What rights do I need to give the user on the local machine in order to use Access Analyzer? +What rights does the user need on the local machine to use Access Analyzer? Enabling Role Based Access removes the necessity to explicitly provide users rights on the Access Analyzer folder structure. Instead, when the Administrator role is first assigned and Role Based -Access is enabled, a new local group called NEAUsers is created on Access Analyzer Console server. -This NEAUsers group is given the necessary permissions on the Access Analyzer application directory. -When a user is assigned a role, they are added to the NEAUsers group to give them the necessary -access to Access Analyzer. +Access is enabled, Access Analyzer creates a new local group called NEAUsers on the Access Analyzer +Console server. Access Analyzer grants the NEAUsers group the necessary permissions on the Access Analyzer application directory. +When you assign a user a role, Access Analyzer adds them to the NEAUsers group to give them the +necessary access to Access Analyzer. See the [Assign User to Role Members](/docs/accessanalyzer/12.0/admin/settings/access/rolebased/assignroles.md) topic for additional information. When a user’s role is changed, when does the new role take affect? -If a user’s role has been altered while they are in an active Access Analyzer session, the user must +If you change a user's role while they're in an active Access Analyzer session, the user must exit the Access Analyzer Console and re-open the application for the new role to take effect. This -is also true if a user has been given an additional role or removed from role membership. The -capabilities of the new role will not come into effect until the Access Analyzer application has -been restarted. +is also true if you give a user an additional role or remove them from role membership. The +capabilities of the new role don't take effect until the user restarts the Access Analyzer +application. :::note See the @@ -76,18 +76,18 @@ See the ::: -I locked a job, but when going back to it, it appears to be unlocked. Why? +A job was locked, but it now appears unlocked. Why? -A locked job signifies that the job has been approved for execution and should not be modified. If a -job is modified in any way, the lock is immediately removed. Although most roles should not be able -to modify locked jobs, the Administrator role can. This role is not governed by the limitations of -Role Based Access. Thus, if a locked job is modified by an Administrator, the job will become -unlocked. This event will be logged as a job-change related event by Administrator in the Access -Analyzer Event Log. +A locked job signifies that the Job Approver approved the job for execution and that no one should +modify it. If anyone modifies a job in any way, Access Analyzer immediately removes the lock. +Although most roles shouldn't be able to modify locked jobs, the Administrator role can, because +Role Based Access limitations don't govern this role. Thus, if an Administrator modifies a locked +job, the job becomes unlocked. The Access Analyzer Event Log records this event as a job-change-related +event performed by the Administrator. :::note -If using a Job Initiator’s credentials for the Schedule Service Account, all jobs must be -locked in order for them to execute. See the [Role Definitions](/docs/accessanalyzer/12.0/admin/settings/access/rolebased/roledefinitions.md), +If the Schedule Service Account uses a Job Initiator's credentials, all jobs must be +locked before they can execute. See the [Role Definitions](/docs/accessanalyzer/12.0/admin/settings/access/rolebased/roledefinitions.md), [Workflow with Role Based Access Enabled](/docs/accessanalyzer/12.0/admin/settings/access/rolebased/workflow.md), and [Roles and the Event Log](/docs/accessanalyzer/12.0/admin/settings/access/rolebased/eventlog.md) topics for more information. ::: @@ -96,13 +96,12 @@ topics for more information. What should be the group type when assigning Role Based Access to an AD group in a multi-domain environment? -When assigning an Role Based Access to an AD group, it is important to consider the domain +When assigning Role Based Access to an AD group, consider the domain relationship between the AD group and the Access Analyzer server. If the Access Analyzer server and the AD group are in different domains then the AD group must be a -universal group. If the group type is not universal then it will result in the RBA being unable to -access the user's group membership and the user who is a member of that AD group will be unable to -view any reports. +universal group. If the group type isn't universal, RBA can't access the user's group membership, +and the user in that AD group can't view any reports. However, if both the Access Analyzer server and the AD group are in the same domain, the AD group can be either a local group, global group, or universal group. diff --git a/docs/accessanalyzer/12.0/admin/settings/access/rolebased/overview.md b/docs/accessanalyzer/12.0/admin/settings/access/rolebased/overview.md index fe3207808c..8809e547d6 100644 --- a/docs/accessanalyzer/12.0/admin/settings/access/rolebased/overview.md +++ b/docs/accessanalyzer/12.0/admin/settings/access/rolebased/overview.md @@ -6,48 +6,48 @@ sidebar_position: 10 # Role Based Access -Role Based Access allows Access Analyzer users to not have local Administrator rights on the console -server. This is done through the creation of different roles which cover all aspects of the Access -Analyzer work flow introduced by enabling Role Based Access. These roles can be leveraged without -such elevated rights. Responsibilities within the Access Analyzer Console have been divided among -these roles. - -Role Based Access also allows users to secure published reports when accessed through the Web -Console. This is done by first enabling Role Based Access and then by assigning users/groups as -viewers to the reports to which they should have access. - -Report security through Role Based Access can be applied without implementing a least privileged -access model to the Access Analyzer Console. See the +Role Based Access allows Access Analyzer users to work without local Administrator rights on the +console server. It does this by creating different roles that cover all aspects of the Access +Analyzer workflow introduced by enabling Role Based Access. Users can use these roles without +such elevated rights. Role Based Access divides responsibilities within the Access Analyzer +Console among these roles. + +With Role Based Access, users can also secure published reports when accessed through the Web +Console. To do this, first enable Role Based Access, then assign users or groups as viewers to +the reports they should access. + +You can apply report security through Role Based Access without implementing a least privileged +access model for the Access Analyzer Console. See the [Securing Published Reports Only](/docs/accessanalyzer/12.0/admin/settings/access/rolebased/securereports.md) topic for additional information. :::note -The least privileged access model to the Access Analyzer Console does not work in -conjunction with the Exchange Solution. Role Based Access can be enabled, but the Administrator role -is required to run the Exchange Solution jobs. +The least privileged access model to the Access Analyzer Console doesn't work in +conjunction with the Exchange Solution. You can enable Role Based Access, but running the +Exchange Solution jobs requires the Administrator role. ::: :::warning -Please use caution when enabling Role Based Access, as it is a very powerful tool -within the console designed to be difficult to disable once activated. If Role Based Access is -enabled by accident, please contact [Netwrix Support](https://www.netwrix.com/support.html) for +use caution when enabling Role Based Access, as it is a very powerful tool +within the console designed to be difficult to disable once activated. If you enable Role Based +Access by accident, contact [Netwrix Support](https://www.netwrix.com/support.html) for assistance in disabling it. ::: -The account used to perform the initial Access Analyzer installation, as well as to change Storage -Profile settings after installation, require additional rights in order to query objects in the +The account you use to perform the initial Access Analyzer installation, and to change Storage +Profile settings after installation, requires additional rights to query objects in the master database. See the [Configure the Installation Account](configureroles.md#configure-the-installation-account) topic for additional information on this account. -To enable Role Based Access within Access Analyzer, corresponding roles must first be created within -SQL Management Studio. Then Access Analyzer users must be assigned roles both in SQL Management -Studio and in Access Analyzer. +To enable Role Based Access within Access Analyzer, first create the corresponding roles in SQL +Management Studio. Then assign roles to Access Analyzer users in both SQL Management Studio and +Access Analyzer. The first Access Analyzer user assigned a role must be an Administrator. Assigning this first user role officially enables Role Based Access within Access Analyzer. When Role Based access is first -enabled, an NEAUsers local group is created on the Access Analyzer server with the required -permissions to the Access Analyzer application directory. When a user is assigned a role, they are -added to the NEAUsers group to give them the necessary access. See the +enabled, Access Analyzer creates an NEAUsers local group on the Access Analyzer server with the +required permissions to the Access Analyzer application directory. When you assign a user a role, +Access Analyzer adds them to the NEAUsers group to give them the necessary access. See the [Assign User to Role Members](/docs/accessanalyzer/12.0/admin/settings/access/rolebased/assignroles.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/admin/settings/access/rolebased/roledefinitions.md b/docs/accessanalyzer/12.0/admin/settings/access/rolebased/roledefinitions.md index 194dd2456b..6c8c04d7b9 100644 --- a/docs/accessanalyzer/12.0/admin/settings/access/rolebased/roledefinitions.md +++ b/docs/accessanalyzer/12.0/admin/settings/access/rolebased/roledefinitions.md @@ -6,19 +6,19 @@ sidebar_position: 10 # Role Definitions -The following is a list of all roles leveraged within Access Analyzer once Role Based Access is -enabled, including their intended functionality. A user may have more than one role assigned to -them. +The following is a list of all roles used within Access Analyzer once Role Based Access is +enabled, including their intended functionality. You can assign a user more than one role. :::note -When a job is moved or copied to a separate job group, it inherits the assigned roles at -the parent and global level from the new job group. Any previous role inheritance is overwritten. +When you move or copy a job to a separate job group, it inherits the assigned roles at +the parent and global level from the new job group. Access Analyzer overwrites any previous +role inheritance. ::: - OS Administrator – Used only for installation purposes - - This is not not a configured role, but rather the access required during installation + - This isn't not a configured role, but rather the access required during installation - Administrator – At least one must be set before any other roles are assigned @@ -27,8 +27,8 @@ the parent and global level from the new job group. Any previous role inheritanc - Rights to preform an upgrade on Access Analyzer :::note -In order to use Role Base Access with the Exchange Solution, all Exchange users must be -assigned the Administrator role. This is because the solution requires local Administrator rights on +to use Role Base Access with the Exchange Solution, assign all Exchange users the +Administrator role. This is because the solution requires local Administrator rights on the Access Analyzer Console server. ::: @@ -58,8 +58,8 @@ the Access Analyzer Console server. - Global Options Administrator - Able to modify global settings, except for the **Setting** > **Access** node - - The Exchange node is the exception due to its requirements. Therefore, this node cannot be - modified by the Global Options Administrator. + - The Exchange node is the exception due to its requirements. Therefore, the Global Options + Administrator can't modify this node. - Rights to view report Tags within the Web Console but not report content or permissions - Host Management Administrator @@ -120,8 +120,9 @@ the Access Analyzer Console server. **Configure** > **Reports**> **Configure** > **Publish Security** page) – Able to view only this report -By default, many roles are granted rights to view all reports and report content. The inheritance of -the Report Viewer role can be broken at the job group, job, or report configuration levels. See the +By default, Access Analyzer grants many roles rights to view all reports and report content. You +can break the inheritance of the Report Viewer role at the job group, job, or report configuration +levels. See the [Report Viewer Inheritance](#report-viewer-inheritance) topic for additional information. ## Access Analyzer Console Roles & Rights @@ -198,15 +199,15 @@ This table describes the roles that will be created within the SQL Server databa they will have to the Access Analyzer database. It also describes which Access Analyzer roles they are mapped to. -| Database Role(s) | Access Analyzer Role | Rights | Role Description | +| Database Roles | Access Analyzer Role | Rights | Role Description | | --------------------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | | SMP Administrator db_datareader db_datawriter | Administrator Job Initiator Job Initiator (No Actions) | On the dbo schema: ALTER, EXECUTE, INSERT, UPDATE, REFERENCES On the Access Analyzer database: CREATE TABLE, CREATE VIEW, CREATE PROCEDURE, CREATE FUNCTION, CREATE TYPE | This role is used by full Administrators and Job Initiators who must run the 2-FSAA Bulk Import Job which requires manipulation of the Access Analyzer database | | SMP Builder | Job Builder Host Management Administrator | On the dbo schema: ELECT, INSERT, DELETE On the Access Analyzer database: CREATE TABLE | This role is used by the Job Builder who must be able to create/delete tables, view data, and insert and delete hosts from the Access Analyzer Console | -| SMP Viewer | Job Viewer Access Administrator Job Approver All other roles | On the dbo schema: SELECT | This role is used by all roles who do not require anything more than just reading data and information from the database | +| SMP Viewer | Job Viewer Access Administrator Job Approver All other roles | On the dbo schema: SELECT | This role is used by all roles who don't require anything more than just reading data and information from the database | ## Report Viewer Inheritance -When Role-Based Access is enabled, users assigned the following roles inherit rights to view all +When you enable Role-Based Access, users assigned the following roles inherit rights to view all reports and their content: - Administrator role @@ -218,10 +219,9 @@ reports and their content: - Job Viewer - Web Administrator -Additional users can be assigned the Report Viewer role at the global, job group, job, or report -configuration levels. These rights are inherited down through child objects. However, the Report -Viewer role inheritance can be broken at any level. Break inheritance to remove the right to view -specific reports at: +You can assign additional users the Report Viewer role at the global, job group, job, or report +configuration levels. Child objects inherit these rights. However, you can break the Report Viewer +role inheritance at any level. Break inheritance to remove the right to view specific reports at: - Job Group level – **[Job Group]** >**Settings** > **Reporting** node - Job level – **[Job]** > **Properties** >**Report Roles** tab @@ -245,5 +245,5 @@ There are two options that control inheritance for Report Viewers when selected: Viewer role inherited from a parent object at the lower levels - Set all the child objects to inherit these settings – Only available at the Job Group level. Sets all Jobs and Reports to inherit group settings for all child objects by automatically selecting - the **Include Report Viewers from this object’s parent** option. Any previous configurations are - overwritten once **Yes** is selected in the confirmation window. + the **Include Report Viewers from this object’s parent** option. Access Analyzer overwrites any + previous configurations once you select **Yes** in the confirmation window. diff --git a/docs/accessanalyzer/12.0/admin/settings/access/rolebased/scheduleserviceaccount.md b/docs/accessanalyzer/12.0/admin/settings/access/rolebased/scheduleserviceaccount.md index d7a1d2e575..82f0f5629e 100644 --- a/docs/accessanalyzer/12.0/admin/settings/access/rolebased/scheduleserviceaccount.md +++ b/docs/accessanalyzer/12.0/admin/settings/access/rolebased/scheduleserviceaccount.md @@ -6,9 +6,9 @@ sidebar_position: 30 # Roles & the Schedule Service Account -Once Role-Based Access is enabled, a user or group with the appropriate access role has the ability +Once you enable Role-Based Access, a user or group with the appropriate access role has the ability to schedule a job or job group as a Schedule Service Account at the **Settings** > **Schedule** -node. Multiple accounts can be added as needed. +node. You can add multiple accounts as needed. **Who Configures This Account?** @@ -16,7 +16,7 @@ node. Multiple accounts can be added as needed. - Power User role - Global Options Administrator role -Whose Credentials Should Be Used as the Schedule Service Account? +Whose Credentials Should You Use for the Schedule Service Account? - A user with either: @@ -25,18 +25,18 @@ Whose Credentials Should Be Used as the Schedule Service Account? - Job Initiator role :::note -In order to run or schedule a Host Inventory query, the Schedule Service Account must have +to run or schedule a Host Inventory query, the Schedule Service Account must have an Administrator, Power User, or Host Management Administrator role. Therefore, if the account has the Job Initiator role assigned, it must have the Host Management Administrator role as well. ::: -The Schedule Service Account is used to access the Task folders when scheduling tasks and to apply -locks on jobs. +Access Analyzer uses the Schedule Service Account to access the Task folders when scheduling tasks +and to apply locks on jobs. - Schedule Tasks - - In order to have the appropriate level of rights to schedule tasks, the credentials specified + - to have the appropriate level of rights to schedule tasks, the credentials specified must at least have the following: - Create Files/Write Data rights on the Windows Task Folder @@ -44,7 +44,7 @@ locks on jobs. - Otherwise, they should have local Administrator privileges on the Access Analyzer Console server - - The user whose credentials are specified must also have a role that allows the scheduling of + - The user whose credentials are specified must also have a role that allows scheduling tasks – Administrator, Power User, or Job Initiator - Apply Locks @@ -55,19 +55,19 @@ locks on jobs. ::: - - These credentials are used to apply locks on jobs, enabling the Job Approver to have fewer - rights on the Jobs directory. Therefore, the credentials specified must at least have the - following: + - Access Analyzer uses these credentials to apply locks on jobs, which lets the Job Approver + have fewer rights on the Jobs directory. Therefore, the credentials specified must at least + have the following: - Modify rights on this directory - Otherwise, these credentials should have local Administrator privileges on the Access Analyzer Console server - - The Job Approver uses these credentials to apply locks. Therefore, the Job Approver must be - added to the local policy **Impersonate a client after Authentication**. + - The Job Approver uses these credentials to apply locks. Therefore, you must add the Job + Approver to the local policy **Impersonate a client after Authentication**. -Do not choose the **Use local System account to schedule tasks** option. This account does not have -the appropriate rights to apply locks on jobs. Therefore, it does not work in conjunction with Role +Don't choose the **Use local System account to schedule tasks** option. This account doesn't have +the appropriate rights to apply locks on jobs. Therefore, it doesn't work in conjunction with Role Based Access. See the [Schedule](/docs/accessanalyzer/12.0/admin/settings/schedule.md) topic for additional instructions on configuring the Schedule diff --git a/docs/accessanalyzer/12.0/admin/settings/access/rolebased/securereports.md b/docs/accessanalyzer/12.0/admin/settings/access/rolebased/securereports.md index d440f0b810..91089fed8b 100644 --- a/docs/accessanalyzer/12.0/admin/settings/access/rolebased/securereports.md +++ b/docs/accessanalyzer/12.0/admin/settings/access/rolebased/securereports.md @@ -6,14 +6,14 @@ sidebar_position: 60 # Securing Published Reports Only -In order to secure published reports through the Web Console, it is necessary to enable Role Based -Access within the Access Analyzer Console. If that is the only reason the Role Based Access feature -is being enabled, ensure the following requirements are met: +To secure published reports through the Web Console, enable Role Based +Access within the Access Analyzer Console. If that is the only reason you're enabling the Role +Based Access feature, ensure you meet the following requirements: - Administrator role assigned to all Access Analyzer Console users - - Anyone not assigned an Administrator role are unable to access the Access Analyzer Console - after Role Based Access is enabled + - Anyone without an Administrator role can't access the Access Analyzer Console after you + enable Role Based Access - Web Administrator role assigned to individuals who should have access to all reports, tags, and report permissions but not the Access Analyzer Console @@ -25,7 +25,7 @@ is being enabled, ensure the following requirements are met: - Job Level Assignment – Access to reports published by the job - Report Configuration Level Assignment – Access to the specific report -Follow the steps to assign roles at the global level. +Assign roles at the global level as follows. **Step 1 –** Navigate to the **Settings** > **Access** node. @@ -44,8 +44,8 @@ ellipsis (**…**) to browse for accounts with the Select User or Group window. ![Console Access page with user added](/images/accessanalyzer/12.0/admin/settings/access/rolebased/consoleaccessfinish.webp) -**Step 5 –** Select a role for the group or user from the Role list. Click **Finish**. The group or -user and role is added to the Role Membership list in the Roles view. +**Step 5 –** Select a role for the group or user from the Role list. Click **Finish**. Access +Analyzer adds the group or user and role to the Role Membership list in the Roles view. :::warning The first role or set of roles saved must include the Administrator role. Clicking Save @@ -57,20 +57,20 @@ the Access Analyzer Console. **Step 6 –** Repeat Steps 2-4 to assign the Administrator, Web Administrator, and Report Viewer roles to other groups or users. -**Step 7 –** Click **Save** and then **OK** to confirm the changes. All applied roles are lost if -they are not saved. +**Step 7 –** Click **Save** and then **OK** to confirm the changes. You lose all applied roles if +you don't save them. -Role Based Access is enabled when the first role has been assigned. +Access Analyzer enables Role Based Access when you assign the first role. -![Error message when Administrator role is not specified](/images/accessanalyzer/12.0/admin/settings/access/rolebased/noadminerror.webp) +![Error message when Administrator role isn't specified](/images/accessanalyzer/12.0/admin/settings/access/rolebased/noadminerror.webp) The first role or set of roles saved must include the Administrator role. Clicking **Save** for the first role or set or roles without including the Administrator generates an error message in the Access Analyzer Console. -When Role Based Access is first enabled, restart the Access Analyzer application to ensure all roles -are properly active. The Report Viewer role can be assigned at the job group, job, and report -configuration levels. See the [Reporting Node](/docs/accessanalyzer/12.0/admin/jobs/group/settings/reporting.md), +When you first enable Role Based Access, restart the Access Analyzer application to ensure all +roles are properly active. You can assign the Report Viewer role at the job group, job, and +report configuration levels. See the [Reporting Node](/docs/accessanalyzer/12.0/admin/jobs/group/settings/reporting.md), [Report Roles Tab](/docs/accessanalyzer/12.0/admin/jobs/job/properties/reportroles.md), and [Publish Security Page](/docs/accessanalyzer/12.0/admin/report/wizard/publishsecurity.md) topics for additional information. diff --git a/docs/accessanalyzer/12.0/admin/settings/access/rolebased/workflow.md b/docs/accessanalyzer/12.0/admin/settings/access/rolebased/workflow.md index 04b4e7c5b7..5e26a9da35 100644 --- a/docs/accessanalyzer/12.0/admin/settings/access/rolebased/workflow.md +++ b/docs/accessanalyzer/12.0/admin/settings/access/rolebased/workflow.md @@ -6,8 +6,8 @@ sidebar_position: 70 # Workflow with Role Based Access Enabled -The following workflow summarizes the necessary steps involved to deploy a job once Role Based -Access is enabled and roles have been assigned. +The following workflow summarizes the necessary steps involved to deploy a job once you enable +Role Based Access and assign roles. **Step 1 –** The Job Builder creates and configures a Access Analyzer job @@ -16,40 +16,41 @@ rejects it ![Lock Job option in right-click menu](/images/accessanalyzer/12.0/admin/settings/access/rolebased/lockjob.webp) -- If a job is approved, then a lock needs to be applied by right-clicking the job title in the Jobs +- If the Job Approver approves a job, apply a lock by right-clicking the job title in the Jobs tree and selecting **Lock Job** -- If a job is rejected, then the job remains unlocked -- If the **Lock Job** option is visible, then the job has not yet been approved -- If the **Lock Job** option is not visible, then the job has been approved +- If the Job Approver rejects a job, the job remains unlocked +- If the **Lock Job** option is visible, the Job Approver hasn't approved the job yet +- If the **Lock Job** option isn't visible, the Job Approver has approved the job ![Unlock Job option in right-click menu](/images/accessanalyzer/12.0/admin/settings/access/rolebased/unlockjob.webp) **Step 3 –** The Job Initiator can choose to run the job directly through the Access Analyzer -Console or schedule it to run with the Schedule Service Account. This user will know the job was -approved by the grayed-out **Unlock Job** option in the right-click menu. +Console or schedule it to run with the Schedule Service Account. The grayed-out **Unlock Job** +option in the right-click menu tells this user the job was approved. - Job Initiator/Job Initiator (No Actions) – The Job Initiator can only execute locked job. - For the Job Initiator (No Actions) role, the user is unable to execute a job which contains configured actions, even if it is approved and locked - - Both roles can enable and disable job groups and jobs regardless of whether or not they are - locked. Disabled jobs are grayed out with a red x next to it and are not executed with the job - group. When applied at the job group level, all nested jobs are disabled and do not run. - However, any new job added to that group is enabled by default. + - Both roles can enable and disable job groups and jobs regardless of whether they are + locked. Disabled jobs are grayed out with a red x next to them, and Access Analyzer doesn't + execute them with the job group. When you disable a job group, Access Analyzer also disables + all nested jobs, and they don't run. However, Access Analyzer enables any new job added to + that group by default. :::note The Job initiator can also publish the reports already generated by the job. ::: -- Publish – To publish reports which have already been generated to the Web Console +- Publish – To publish reports the job has already generated to the Web Console - See the [Report Settings Tab](/docs/accessanalyzer/12.0/admin/jobs/job/properties/reportsettings.md) topic for additional information ![Report under the Results Node in the Jobs Tree](/images/accessanalyzer/12.0/admin/settings/access/rolebased/reportjobstree.webp) -**Step 4 –** After a job has been successfully run, the **Job Viewer** can now view the results of +**Step 4 –** After a job runs successfully, the **Job Viewer** can now view the results of the job under the job’s Status and Results node, or in the Web Console. See the [Viewing Generated Reports](/docs/accessanalyzer/12.0/admin/report/view.md) topic for additional information. @@ -62,10 +63,10 @@ Console. ## Other Console Roles -Any modifications needed in the Settings or Host Management nodes must be done by the corresponding -administrator role (Global Options Administrator, Access Administrator, or Host Management -Administrator). These roles can be used in conjunction with any other role (for example, a user can -be a Job Builder and Global Options Administrator in order to build jobs and manage corresponding +The corresponding administrator role (Global Options Administrator, Access Administrator, or Host +Management Administrator) must make any modifications needed in the Settings or Host Management +nodes. You can use these roles in conjunction with any other role (for example, a user can +be a Job Builder and Global Options Administrator to build jobs and manage corresponding Connection Profiles). ### Web Administrator @@ -82,8 +83,8 @@ Console. ### Report Viewer -The Report Viewer can view reports within the Web Console according to where the user’s role was -assigned: global, job group, job, or report configuration. +The Report Viewer can view reports within the Web Console according to where you assigned the +user’s role: global, job group, job, or report configuration. :::tip Remember, a user with only the Report Viewer role is unable to access the Access Analyzer Console. diff --git a/docs/accessanalyzer/12.0/admin/settings/application/overview.md b/docs/accessanalyzer/12.0/admin/settings/application/overview.md index 31e1c180c9..c8eb9df798 100644 --- a/docs/accessanalyzer/12.0/admin/settings/application/overview.md +++ b/docs/accessanalyzer/12.0/admin/settings/application/overview.md @@ -13,15 +13,15 @@ Analyzer Console functions. **Application Log** -The Access Analyzer Application Log section determines what information is stored in the Access -Analyzer application log. +The Access Analyzer Application Log section determines what information Access Analyzer stores +in the application log. ![Application Log](/images/accessanalyzer/12.0/admin/settings/application/applicationlog.webp) The Application log level controls the types of messages generated for each job and the application. -It can be modified at the job level in the **Job Properties** window. See the +You can modify it at the job level in the **Job Properties** window. See the [General Tab](/docs/accessanalyzer/12.0/admin/jobs/job/properties/general.md) topic for additional information. Options -available in the Application log level drop-down menu include: +available in the Application log level dropdown menu include: - Debug – Records everything that happens during job execution, most verbose level of logging @@ -47,47 +47,47 @@ available in the Application log level drop-down menu include: - Records job completion time :::info -Set the log level to **Warning**. The global log level determines what messages are written to the SA_Messages table and visible in the NAA Console. If a job has a higher log level than the global setting, those additional messages will be written to the job log only and will not appear in the database. For additional information on changing the job log level, see [Job Properties | General tab](https://docs.netwrix.com/docs/accessanalyzer/12_0/admin/jobs/job/properties/general). +Set the log level to **Warning**. The global log level determines what messages Access Analyzer writes to the SA_Messages table and displays in the Access Analyzer Console. If a job has a higher log level than the global setting, those additional messages go to the job log only and don't appear in the database. For additional information on changing the job log level, see [Job Properties | General tab](https://docs.netwrix.com/docs/accessanalyzer/12_0/admin/jobs/job/properties/general). ::: -The other log levels are designed to assist with troubleshooting job execution issues. The Debug -level is only recommended when experiencing problems. After the problem is fixed or the Application -log has been sent to [Netwrix Support](https://www.netwrix.com/support.html), reduce the logging +The other log levels are designed to assist with troubleshooting job execution issues. Only use +the Debug level when experiencing problems. After you fix the problem or send the Application +log to [Netwrix Support](https://www.netwrix.com/support.html), reduce the logging level to **Warning** or **Info**. **Profile Security** The Profile Security section provides the option to enable an enhanced method of encryption to -various credentials stored by the Access Analyzer application. +various credentials the Access Analyzer application stores. ![Profile Security](/images/accessanalyzer/12.0/admin/settings/application/profilesecurity.webp). -There are two options available in the Profiles stored with drop-down menu: +There are two options available in the Profiles stored with dropdown menu: -- Application – Default setting, does not employ the enhanced encryption +- Application – Default setting, doesn't employ the enhanced encryption - Vault – Enables the enhanced encryption of stored credentials. See the [Vault](/docs/accessanalyzer/12.0/admin/settings/application/vault.md) topic for requirements and additional information. **Usage Statistics** -The Usage Statistics section allows you to select whether to send usage statistics data to Netwrix -to help us improve our product. +Use the Usage Statistics section to select whether to send usage statistics data to Netwrix +to help improve the product. ![Usage Statistics](/images/accessanalyzer/12.0/admin/settings/application/usagestatistics.webp) -- If selected, usage statistics are collected and sent to Netwrix +- If selected, Access Analyzer collects usage statistics and sends them to Netwrix - - Upon startup of the Access Analyzer console, the system checks if usage statistics have been - sent in the last 7 days. If they have not been, stored procedures run against the Access + - Upon startup of the Access Analyzer console, the system checks whether it has sent usage + statistics in the last 7 days. If it hasn't, stored procedures run against the Access Analyzer database and gather data about job runs, access times, and environmental details like - resource counts, users counts, number of exceptions, and so on. This data is then sent back to - Netwrix to help us identify usage trends and common pain points, so that we can use this - information to improve the product. - - Only anonymous statistic-level data is included. No private company or personal data is - collected or sent to Netwrix. + resource counts, user counts, number of exceptions, and so on. Access Analyzer then sends + this data back to Netwrix to help identify usage trends and common problem areas and + improve the product. + - This includes only anonymous statistic-level data. Access Analyzer doesn't collect or send + any private company or personal data to Netwrix. -- If cleared, no usage statistics are collected or sent to Netwrix +- If cleared, Access Analyzer doesn't collect or send usage statistics to Netwrix **Host Target Options** @@ -111,7 +111,7 @@ Console. - Automatically rename duplicate columns within a table – Checks for and renames columns with duplicate names - Automatically correct invalid column names – Checks for and corrects column names which contain - characters SQL cannot handle + characters SQL can't handle :::info Leave both options selected. @@ -123,27 +123,27 @@ Console. - Maximum row count for interactive grid view – Indicates the number of rows displayed in tables accessible in under a job’s Status and Results nodes - - Maximum row count is set to 1000 by default and has a cap of 99,999 rows. This number does not + - Maximum row count defaults to 1000 and has a cap of 99,999 rows. This number doesn't impact the number of rows within the SQL database. To view the full row count for a table exceeding this size, use the SQL Server Management Studio or another SQL Server interface tool which displays the full table. -Filtered data grids are not lost if persistent filters are not saved. The Filtration Dialog +Filtered data grids aren't lost if you don't save persistent filters. The Filtration Dialog available for every data grid maintains a list of recent filters. See the [Data Grid Functionality](/docs/accessanalyzer/12.0/admin/navigate/datagrid.md) topic for additional information. **Cleanup** The Cleanup section is designed to conserve space in the SQL Database Transaction Log. It only works -when the database is configured to use Simple Recovery Model. +when you configure the database to use Simple Recovery Model. ![Cleanup Options](/images/accessanalyzer/12.0/admin/settings/application/cleanup.webp) -- Compact Database Transaction Log – If selected, every time the Access Analyzer application is - closed, the Database Transaction Log is compacted +- Compact Database Transaction Log – If selected, Access Analyzer compacts the Database + Transaction Log every time you close the Access Analyzer application :::info - In most environments, it is recommended to leave this option selected. If a + In most environments, leave this option selected. If a scheduled task ends while multiple tasks are still running, the process of compacting the database freezes it and causes the running tasks to fail. ::: @@ -153,14 +153,14 @@ when the database is configured to use Simple Recovery Model. of SUCCESS, WARNING, or ERROR to indicate what happened on that host during job execution :::info - It is recommended that this option be left selected. + Leave this option selected. ::: **Application Exit Options** -The Application Exit Options section controls whether or not a confirmation is displayed when the -Access Analyzer application is closed. +The Application Exit Options section controls whether Access Analyzer displays a confirmation +when you close the Access Analyzer application. ![Application Exit Options](/images/accessanalyzer/12.0/admin/settings/application/applicationexitoptions.webp) @@ -170,10 +170,10 @@ application closes without confirmation. ![Confirm Exit](/images/accessanalyzer/12.0/admin/settings/application/confirmexitwindow.webp) -The Confirm Exit window requires the **Yes** button to be clicked before the Access Analyzer +The Confirm Exit window requires you to click **Yes** before the Access Analyzer application closes. The **Cancel** and **Save** buttons are in the lower-right corner of the Application view. These -buttons become enabled when modifications are made to the Application global settings. Whenever -changes are made at the global level, click **Save** and then **OK** to confirm the changes. -Otherwise, click **Cancel** if no changes were intended. +buttons become enabled when you modify the Application global settings. Whenever +you make changes at the global level, click **Save** and then **OK** to confirm the changes. +Otherwise, click **Cancel** if you didn't intend to make changes. diff --git a/docs/accessanalyzer/12.0/admin/settings/application/vault.md b/docs/accessanalyzer/12.0/admin/settings/application/vault.md index a39c433f0c..08c5d2471d 100644 --- a/docs/accessanalyzer/12.0/admin/settings/application/vault.md +++ b/docs/accessanalyzer/12.0/admin/settings/application/vault.md @@ -7,15 +7,15 @@ sidebar_position: 10 # Vault The Access Analyzer vault provides additional security through enhanced encryption to various -credentials stored by the Access Analyzer application, such as Connection Profile credentials or -Schedule Service Account credentials. In order to enable the vault, the following prerequisites must -be met in the order listed: +credentials the Access Analyzer application stores, such as Connection Profile credentials or +Schedule Service Account credentials. to enable the vault, meet the following prerequisites +in the order listed: - Access Analyzer Vault Service must be running - - This service was installed during the Access Analyzer installation and is configured for - Manual Startup Type - - It needs to be configured to Log On (Service > Properties) with a service account which has + - The Access Analyzer installation installs this service and configures it for Manual + Startup Type + - You need to configure it to Log On (Service > Properties) with a service account that has Log on as Service rights, as well as Read and Execute rights to the VaultService.exe file located within the Access Analyzer installation directory @@ -23,17 +23,17 @@ be met in the order listed: - The vault was designed to provide enhanced security when employing the Role Based Access, or least privilege, option of Access Analyzer - - At least one Administrator role must be assigned to enable the vault: + - You must assign at least one Administrator role to enable the vault: - - If full Role Based Access is not desired but enabling the vault is, all of the Access - Analyzer users should be given the Administrator role - - No additional Role Based Access prerequisites are required for this option + - If you don't want full Role Based Access but do want to enable the vault, give all + Access Analyzer users the Administrator role + - This option doesn't require additional Role Based Access prerequisites - See the [Access](/docs/accessanalyzer/12.0/admin/settings/access/overview.md) topic for additional information on Role Based Access :::note - Once the vault has been enabled, it is not possible to disable Role Based Access - without first disabling the vault. Please contact + After you enable the vault, you can't disable Role Based Access + without first disabling the vault. contact [Netwrix Support](https://www.netwrix.com/support.html) for assistance in disabling Role Based Access. ::: @@ -46,17 +46,17 @@ be met in the order listed: If the previous prerequisites have not been met, then one of the following errors will occur when attempting to save the Vault Profile Security setting: - - Role Based Access Error – Role Based Access must be configured in order to use the Access - Analyzer Vault. Please configure Role Based Access and try again - - Access Analyzer Vault Service Error – Access Analyzer is not running + - Role Based Access Error – Role Based Access must be configured to use the Access + Analyzer Vault. configure Role Based Access and try again + - Access Analyzer Vault Service Error – Access Analyzer isn't running - The Netwrix Access Analyzer (formerly Enterprise Auditor) Web Server service must be run with an account that has the Administrator role assigned - - If the Administrator role is not assigned, the vault service does not allow the web server to - access the SQL profile and throws an access denied error in the web server log file + - If you don't assign the Administrator role, the vault service doesn't allow the web server + to access the SQL profile and throws an access denied error in the web server log file -The credentials which are encrypted once the vault has been enabled are: +The credentials that the Access Analyzer Vault Service encrypts after you enable the vault are: - Storage Profile credentials - Connection Profile credentials @@ -64,12 +64,13 @@ The credentials which are encrypted once the vault has been enabled are: - Role Definitions - Role Assignments -Once encrypted, the files with these stored credentials are moved into a new directory location. +Once encrypted, the Access Analyzer Vault Service moves the files with these stored credentials +into a new directory location. -This location is protected by the service account used to run the Access Analyzer Vault Service. +The service account used to run the Access Analyzer Vault Service protects this location. ## Disabling the Vault To disable the vault, navigate to the **Settings** > **Application** node and change the Profile -Security section setting to **Application**. It is a best practice to also stop the Access Analyzer +Security section setting to **Application**. As a best practice, also stop the Access Analyzer Vault Service. diff --git a/docs/accessanalyzer/12.0/admin/settings/connection/create/activedirectory.md b/docs/accessanalyzer/12.0/admin/settings/connection/create/activedirectory.md index fda1943041..0c6a311fd4 100644 --- a/docs/accessanalyzer/12.0/admin/settings/connection/create/activedirectory.md +++ b/docs/accessanalyzer/12.0/admin/settings/connection/create/activedirectory.md @@ -6,14 +6,14 @@ sidebar_position: 10 # Active Directory Account for User Credentials -If the account type selected on the User Credentials window is **Active Directory Account**, the -following information is required for the credential: +If the account type selected on the User Credentials window is **Active Directory Account**, you +must provide the following information for the credential: ![User Credentials Window - Active Directory](/images/accessanalyzer/12.0/admin/settings/connection/profile/activedirectoryaccount.webp) -- Domain – Drop-down menu with available trusted domains will appear. Either type the short domain +- Domain – dropdown menu with available trusted domains will appear. Either enter the short domain name in the textbox or select a domain from the menu. -- User name – Type the user name +- User name – Enter the user name - Password Storage – Choose the option for credential password storage: - Application – Uses the configured Profile Security setting as selected at the **Settings** > @@ -21,11 +21,11 @@ following information is required for the credential: additional information. - CyberArk – Uses the CyberArk Enterprise Password Vault. See the [CyberArk Integration](/docs/accessanalyzer/12.0/admin/settings/connection/cyberarkintegration.md) topic for additional information. The - password fields do not apply for CyberArk password storage. + password fields don't apply for CyberArk password storage. - Managed Service Account – Use previously configured MSA and gMSAs for authentication. The - password fields are not applicable when this option is selected. See the + password fields aren't applicable when this option is selected. See the [Group Managed Service Accounts (gMSA) Configuration](/docs/accessanalyzer/12.0/admin/settings/connection/gmsa.md) topic for additional information. -- Password – Type the password -- Confirm – Re-type the password +- Password – Enter the password +- Confirm – Re-enter the password diff --git a/docs/accessanalyzer/12.0/admin/settings/connection/create/aws.md b/docs/accessanalyzer/12.0/admin/settings/connection/create/aws.md index 1290603d91..686f0a267e 100644 --- a/docs/accessanalyzer/12.0/admin/settings/connection/create/aws.md +++ b/docs/accessanalyzer/12.0/admin/settings/connection/create/aws.md @@ -13,17 +13,17 @@ type in the User Credentials window. The required credentials for Amazon Web Services are: -- Access Key ID — Used to sign programmatic requests made to AWS. If access keys are not available, +- Access Key ID — Used to sign programmatic requests made to AWS. If access keys aren't available, create them with the IAM console. - Password Storage: Application – Uses the configured Profile Security setting as selected at the **Settings >** **Application** node -- Secret Key — Used to sign programmatic requests made to AWS. If secret keys are not available, +- Secret Key — Used to sign programmatic requests made to AWS. If secret keys aren't available, create them with the IAM console. - Scan Roles — Role used to scan other organization accounts ## Create a Connection Profile for AWS -A new connection profile will need to be created to be leveraged in the AWS Solution. +You need to create a new connection profile for use in the AWS Solution. **Step 1 –** Under Settings > Connection, click Add Connection profile. @@ -33,7 +33,7 @@ A new connection profile will need to be created to be leveraged in the AWS Solu Access Token section. :::tip -Remember, these are obtained from AWS when the permissions are configured. See the +Remember, you obtain these from AWS when you configure the permissions. See the [Configure AWS for Scans](/docs/accessanalyzer/12.0/requirements/aws/configurescans.md) topic for additional information. ::: @@ -41,4 +41,4 @@ information. **Step 4 –** Click OK in the User Credentials modal, name the Connection Profile, and click Save. -This connection profile can now be assigned to the AWS Solution. +You can now assign this connection profile to the AWS Solution. diff --git a/docs/accessanalyzer/12.0/admin/settings/connection/create/create.md b/docs/accessanalyzer/12.0/admin/settings/connection/create/create.md index 9946b42e84..7ef5b42228 100644 --- a/docs/accessanalyzer/12.0/admin/settings/connection/create/create.md +++ b/docs/accessanalyzer/12.0/admin/settings/connection/create/create.md @@ -6,8 +6,6 @@ sidebar_position: 10 # Create a Connection Profile -Follow the steps to create a Connection Profile. - ![Add Connection Profile](/images/accessanalyzer/12.0/admin/settings/connection/profile/addconnectionprofile.webp) **Step 1 –** Click Add Connection profile at the top of the Connection view. @@ -18,15 +16,15 @@ Follow the steps to create a Connection Profile. name in the Connection profile name textbox. :::note -A good profile name should be chosen so that it does not need to be changed at a later -time. If the profile name is changed after being applied to job groups or jobs, it requires the user -to go back through all of those job groups or jobs and re-apply the Connection Profile. +Choose a good profile name so that you don't need to change it later. If you change the +profile name after applying it to job groups or jobs, you must go back through all of those job +groups or jobs and reapply the Connection Profile. ::: ![Add User Credential](/images/accessanalyzer/12.0/admin/settings/connection/profile/addusercredential.webp) -**Step 3 –** Now it is time to add credentials to this profile. Click Add User credential and the +**Step 3 –** Add credentials to this profile. Click Add User credential and the User Credentials window opens. ![User Credentials](/images/accessanalyzer/12.0/admin/settings/connection/profile/activedirectoryaccount.webp) @@ -51,8 +49,8 @@ See the individual account type sections for information on the fields. Then cli ![Error Message for Password](/images/accessanalyzer/12.0/admin/settings/connection/profile/passworddifferserror.webp) :::note -If the entered passwords are not the same, an error message will pop-up after clicking OK -on the User Credentials window. Click OK on the error message and re-type the passwords. +If the entered passwords aren't the same, an error message pops up after you click OK +on the User Credentials window. Click OK on the error message and re-enter the passwords. ::: @@ -69,28 +67,28 @@ are no more credentials to try. :::info Limit the User Credentials list to a minimal number per profile, especially when -considering that a successful authentication does not automatically mean that particular credential -has the appropriate level of permissions in order for the data collection to occur. +considering that a successful authentication doesn't automatically mean that particular credential +has the appropriate level of permissions for the data collection to occur. ::: ![Arrange Priority](/images/accessanalyzer/12.0/admin/settings/connection/profile/moveupdown.webp) -There are Move Up and Move Down buttons for arranging priority within the User Credentials list. +Use the Move Up and Move Down buttons to arrange priority within the User Credentials list. ![Apply local login credentials](/images/accessanalyzer/12.0/admin/settings/connection/profile/usewindowsaccountoption.webp) **Step 6 –** (Optional): At the bottom of the Connection view, is the Use the Windows account that Access Analyzer runs with before trying the user credentials above option. This option is per -Connection Profile. If checked, Access Analyzer applies the local login credentials prior to any of +Connection Profile. If checked, Access Analyzer applies the local login credentials before any of the credentials saved to the Connection Profile. :::note -If a data collector utilizes an applet, this option must be unchecked. +If a data collector uses an applet, uncheck this option. ::: -**Step 7 –** When the user credentials have been added and ordered, click Save and then OK to +**Step 7 –** After you add and order the user credentials, click Save and then OK to confirm the changes to the Connection Profile. The new Connection Profile is now visible in the Profile list and available for use at the job group @@ -98,36 +96,32 @@ or job level. ## Edit User Credentials within a Connection Profile -Follow the steps to edit user credentials within a Connection Profile. - ![Edit Connection Profile](/images/accessanalyzer/12.0/admin/settings/connection/profile/editusercredentials.webp) -**Step 1 –** Select the Connection Profile to be modified from the Profile list. Remember, changing -the Connection Profile name results in breaking job groups or jobs that are assigned this profile. +**Step 1 –** Select the Connection Profile you want to modify from the Profile list. Remember, +changing the Connection Profile name results in breaking job groups or jobs assigned this profile. -**Step 2 –** Select the user credential to be edited from the User Credentials list. Click Edit. +**Step 2 –** Select the user credential you want to edit from the User Credentials list. Click Edit. ![User Credentials](/images/accessanalyzer/12.0/admin/settings/connection/profile/selectaccounttype.webp) **Step 3 –** Modify the information in the User Credentials window. For the password, choose between the Use the existing password option or the Specify a new password below option. Click OK. -**Step 4 –** When the Connection Profile’s user credentials have been edited as desired, click Save +**Step 4 –** After you edit the Connection Profile’s user credentials as desired, click Save and then OK to confirm the changes to the Connection Profile. -The edited user credentials are now used for authentication to target hosts for this Connection -Profile. +Access Analyzer now uses the edited user credentials for authentication to target hosts for this +Connection Profile. ## Delete a User Credential from a Connection Profile -Follow the steps to delete a user credential from a Connection Profile. - ![Delete User Credentials](/images/accessanalyzer/12.0/admin/settings/connection/profile/deleteusercredentials.webp) -**Step 1 –** Select the Connection Profile to be modified from the Profile list. Remember, changing -the Connection Profile name results in breaking job groups or jobs that are assigned this profile. +**Step 1 –** Select the Connection Profile you want to modify from the Profile list. Remember, +changing the Connection Profile name results in breaking job groups or jobs assigned this profile. -**Step 2 –** Select the user credential to be edited from the User Credentials list. Click Delete. +**Step 2 –** Select the user credential you want to delete from the User Credentials list. Click Delete. ![Confirmation message for deletion](/images/accessanalyzer/12.0/admin/settings/connection/profile/deleteusercredentialsconfirm.webp) @@ -145,20 +139,16 @@ The default profile is marked with the green checkmark. ![defaultconnectionprofile](/images/accessanalyzer/12.0/admin/settings/connection/profile/defaultconnectionprofile.webp) -Follow the steps to set a new default Connection Profile. - ![Set a Default Connection Profile](/images/accessanalyzer/12.0/admin/settings/connection/profile/setasdefaultconnectionprofile.webp) -**Step 1 –** Select the desired profile in the Connection Profile list and click Set as default. +**Step 1 –** Select the profile in the Connection Profile list and click Set as default. **Step 2 –** The green checkmark moves. Click Save and then OK to confirm the changes. -This Connection Profile is now used as the default Connection Profile. +Access Analyzer now uses this Connection Profile as the default Connection Profile. ## Delete a Connection Profile -Follow the steps to delete a Connection Profile. - ![Delete a Connection Profile](/images/accessanalyzer/12.0/admin/settings/connection/profile/deleteconnectionprofile.webp) **Step 1 –** Select the profile from the Connection Profile list and click Delete. diff --git a/docs/accessanalyzer/12.0/admin/settings/connection/create/dropbox.md b/docs/accessanalyzer/12.0/admin/settings/connection/create/dropbox.md index a2be06eb9b..99a0f5db5b 100644 --- a/docs/accessanalyzer/12.0/admin/settings/connection/create/dropbox.md +++ b/docs/accessanalyzer/12.0/admin/settings/connection/create/dropbox.md @@ -16,6 +16,6 @@ The required credentials for Dropbox are: - Password Storage – Application (Uses the configured Profile Security setting as selected at the **Settings** > **Application** node. See the [Application](/docs/accessanalyzer/12.0/admin/settings/application/overview.md) topic for additional information.) -- Access Token – Copy and paste the access token after it has been generated from the Scan Options - page of the DropboxAccess Data Collector configuration wizard. See the Dropbox for User +- Access Token – Copy and paste the access token after the DropboxAccess Data Collector + configuration wizard generates it from the Scan Options page. See the Dropbox for User Credentials topic for additional information. diff --git a/docs/accessanalyzer/12.0/admin/settings/connection/create/entraid.md b/docs/accessanalyzer/12.0/admin/settings/connection/create/entraid.md index 183c35c958..9f4eddf6c4 100644 --- a/docs/accessanalyzer/12.0/admin/settings/connection/create/entraid.md +++ b/docs/accessanalyzer/12.0/admin/settings/connection/create/entraid.md @@ -21,7 +21,7 @@ The required credentials for this account type are: - Password Storage – Application (Uses the configured Profile Security setting as selected at the **Settings** > **Application** node. See the [Application](/docs/accessanalyzer/12.0/admin/settings/application/overview.md) topic for additional information.) -- Key – The required Key depends on the target environment the Connection Profile is being used for: +- Key – The required Key depends on the target environment where you use the Connection Profile: - Entra ID – Client secret value for the Access Analyzer application registered with Microsoft Entra ID. See the diff --git a/docs/accessanalyzer/12.0/admin/settings/connection/create/exchangemodernauth.md b/docs/accessanalyzer/12.0/admin/settings/connection/create/exchangemodernauth.md index 04843591d6..e08b9e8f4e 100644 --- a/docs/accessanalyzer/12.0/admin/settings/connection/create/exchangemodernauth.md +++ b/docs/accessanalyzer/12.0/admin/settings/connection/create/exchangemodernauth.md @@ -16,11 +16,11 @@ The values for the required credentials for the Exchange Modern Authentication a - Password Storage – Application (Uses the configured Profile Security setting as selected at the **Settings** > **Application** node. See the [Application](/docs/accessanalyzer/12.0/admin/settings/application/overview.md) topic for additional information.) -- Organization – The primary domain name of the Microsoft Entra tenant being leveraged to make the +- Organization – The primary domain name of the Microsoft Entra tenant used to make the connection. See the [Identify the Tenant's Name](/docs/accessanalyzer/12.0/requirements/exchange/exchangeonline/access.md#identify-the-tenants-name) topic for additional information. -- Email Address – The email address for the mailbox to be leveraged in Exchange Online environment +- Email Address – The email address for the mailbox used in Exchange Online environment scans. The mailbox must belong to the primary domain used in the Organization field. - AppID – Application (client) ID of the Access Analyzer application registered with Microsoft Entra ID. See the diff --git a/docs/accessanalyzer/12.0/admin/settings/connection/create/localwindows.md b/docs/accessanalyzer/12.0/admin/settings/connection/create/localwindows.md index e264f35875..5c3dade01e 100644 --- a/docs/accessanalyzer/12.0/admin/settings/connection/create/localwindows.md +++ b/docs/accessanalyzer/12.0/admin/settings/connection/create/localwindows.md @@ -13,7 +13,7 @@ User Credentials window. The required credentials for the Local Windows Account are: -- User name – Type the user name +- User name – Enter the user name - Password Storage – Choose the option for credential password storage: - Application – Uses the configured Profile Security setting as selected at the **Settings** > @@ -21,14 +21,14 @@ The required credentials for the Local Windows Account are: additional information. - CyberArk – Uses the CyberArk Enterprise Password Vault. See the [CyberArk Integration](/docs/accessanalyzer/12.0/admin/settings/connection/cyberarkintegration.md) topic for additional information. The - password fields do not apply for CyberArk password storage. + password fields don't apply for CyberArk password storage. :::note - If using the CyberArk option, then the associated Connection Profile can only have - one user credential in it. Multiple user credentials are not supported with the CyberArk - integration when using local Windows accounts. + If you use the CyberArk option, the associated Connection Profile can only have + one user credential in it. The CyberArk integration doesn't support multiple user + credentials when you use local Windows accounts. ::: -- Password – Type the password -- Confirm – Re-type the password +- Password – Enter the password +- Confirm – Re-enter the password diff --git a/docs/accessanalyzer/12.0/admin/settings/connection/create/oracle.md b/docs/accessanalyzer/12.0/admin/settings/connection/create/oracle.md index 2d8ba704b5..f66e698023 100644 --- a/docs/accessanalyzer/12.0/admin/settings/connection/create/oracle.md +++ b/docs/accessanalyzer/12.0/admin/settings/connection/create/oracle.md @@ -14,24 +14,24 @@ window. The required credentials for Oracle are: - Domain – Field options are dependent upon the additional account type option selected: - - Oracle Account – Domain is not a field for this type of credential - - Windows account that Access Analyzer is run with – (Domain is not a field for this type of + - Oracle Account – Domain isn't a field for this type of credential + - Windows account that Access Analyzer is run with – (Domain isn't a field for this type of credential) - - Active Directory – Drop-down menu with available trusted domains displays. Either type the + - Active Directory – dropdown menu with available trusted domains displays. Either enter the short domain name in the textbox or select a domain from the menu. -- User name – Type the user name - - This is not a field for the additional account type of Windows account that Access Analyzer is +- User name – Enter the user name + - This isn't a field for the additional account type of Windows account that Access Analyzer is run with is selected - Password Storage: Application – Uses the configured Profile Security setting as selected at the **Settings >** **Application** node -- Password – Type the password - - This is not a field for the additional account type of Windows account that Access Analyzer is +- Password – Enter the password + - This isn't a field for the additional account type of Windows account that Access Analyzer is run with -- Confirm – Re-type the password - - This is not a field for the additional account type of Windows account that Access Analyzer is +- Confirm – Re-enter the password + - This isn't a field for the additional account type of Windows account that Access Analyzer is run with -- Role – Specify an Oracle role, if desired. The drop-down menu provides a list of roles. Either - type the role name in the textbox or select a role from the menu. +- Role – Specify an Oracle role, if desired. The dropdown menu provides a list of roles. Either + enter the role name in the textbox or select a role from the menu. - **NOTE:** When using a least privileged model for Oracle, **SYSDBA** must be selected for the Role. - Additional Account type – Select radio button of the secondary account type from the list at the diff --git a/docs/accessanalyzer/12.0/admin/settings/connection/create/sql.md b/docs/accessanalyzer/12.0/admin/settings/connection/create/sql.md index 23c576f38f..04da18c785 100644 --- a/docs/accessanalyzer/12.0/admin/settings/connection/create/sql.md +++ b/docs/accessanalyzer/12.0/admin/settings/connection/create/sql.md @@ -10,7 +10,7 @@ This information applies to **Select Account Type** > **SQL Authentication** in window. :::note -SQL Authentication credentials are used in the Connection Profiles for the SQL, MySQL, and +You use SQL Authentication credentials in the Connection Profiles for the SQL, MySQL, and PostgreSQL Solutions. ::: @@ -23,5 +23,5 @@ The required credentials for SQL Authentication are: - Password Storage – Application (Uses the configured Profile Security setting as selected at the **Settings** > **Application** node. See the [Application](/docs/accessanalyzer/12.0/admin/settings/application/overview.md) topic for additional information.) -- Password – Type the password -- Confirm – Re-type the password +- Password – Enter the password +- Confirm – Re-enter the password diff --git a/docs/accessanalyzer/12.0/admin/settings/connection/create/task.md b/docs/accessanalyzer/12.0/admin/settings/connection/create/task.md index cf77933eea..cd25ae7d76 100644 --- a/docs/accessanalyzer/12.0/admin/settings/connection/create/task.md +++ b/docs/accessanalyzer/12.0/admin/settings/connection/create/task.md @@ -17,10 +17,10 @@ The required credentials for Task (Local) and Task (Domain) are: - Domain - Local – Not a field for this type of credential, defaults to `` - - Domain – Drop-down menu with available trusted domains displays. Either type the short domain + - Domain – dropdown menu with available trusted domains displays. Either enter the short domain name in the textbox or select a domain from the menu. -- User name – Type the user name +- User name – Enter the user name - Password Storage: Application – Uses the configured Profile Security setting as selected at the **Settings > Application** node -- Password – Type the password -- Confirm – Re-type the password +- Password – Enter the password +- Confirm – Re-enter the password diff --git a/docs/accessanalyzer/12.0/admin/settings/connection/create/unix.md b/docs/accessanalyzer/12.0/admin/settings/connection/create/unix.md index af9901751d..710fa37379 100644 --- a/docs/accessanalyzer/12.0/admin/settings/connection/create/unix.md +++ b/docs/accessanalyzer/12.0/admin/settings/connection/create/unix.md @@ -20,12 +20,12 @@ The required credentials for the Unix Account are: - Password/Confirm - If not using a private key, enter the **Password** and re-type in the **Confirm** field - - If using a private key, then the password is not needed. Provide the private key information + - If you use a private key, the password isn't needed. Provide the private key information in the **Use the following private key when connecting** field. - Use the following port/ports (CSV) for SSH - - The SSH port needs to be opened in software and hardware firewalls + - You need to open the SSH port in software and hardware firewalls - If desired, select this option and provide the port value - Use the following private key when connecting diff --git a/docs/accessanalyzer/12.0/admin/settings/connection/create/webservices.md b/docs/accessanalyzer/12.0/admin/settings/connection/create/webservices.md index 62083d668c..033299d779 100644 --- a/docs/accessanalyzer/12.0/admin/settings/connection/create/webservices.md +++ b/docs/accessanalyzer/12.0/admin/settings/connection/create/webservices.md @@ -16,6 +16,6 @@ The required credentials for Web Services (JWT) are: - User name – `{not a field for this type of credential}` - Password Storage: Application – Uses the configured Profile Security setting as selected at the **Settings > Application** node -- Access Token – Copy and paste the StealthDEFEND App Token after it has been generated within - StealthDEFEND. See the [FS_DEFEND_SDD Job](/docs/accessanalyzer/12.0/admin/jobs/instantjobs/fs_defend_sdd.md) topic for +- Access Token – Copy and paste the StealthDEFEND App Token after StealthDEFEND generates it. + See the [FS_DEFEND_SDD Job](/docs/accessanalyzer/12.0/admin/jobs/instantjobs/fs_defend_sdd.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/admin/settings/connection/cyberarkintegration.md b/docs/accessanalyzer/12.0/admin/settings/connection/cyberarkintegration.md index 2394d3426e..058326b395 100644 --- a/docs/accessanalyzer/12.0/admin/settings/connection/cyberarkintegration.md +++ b/docs/accessanalyzer/12.0/admin/settings/connection/cyberarkintegration.md @@ -6,31 +6,32 @@ sidebar_position: 20 # CyberArk Integration -In order for Access Analyzer to be able to retrieve service account passwords from the CyberArk -Password Vault, the following prerequisites must be completed: +For Access Analyzer to retrieve service account passwords from the CyberArk +Password Vault, complete the following prerequisites: - The Secrets Manager must be installed on the Access Analyzer Console server. The organization’s Vault administrator can provide the Secrets Manager installation package and most likely needs to - be present during the installation to provide credentials in order for the Secrets Manager + be present during the installation to provide credentials for the Secrets Manager installation to complete. See the CyberArk [Credential Provider (CP)](https://docs.cyberark.com/credential-providers/Latest/en/Content/CP%20and%20ASCP/Installing-CP.htm) article for additional information. -- An application must be added to CyberArk for the integration with Access Analyzer. The Application - Id of this application must then be added to the `GlobalOptions.xml` file for Access Analyzer. See - the [Customize CyberArk Application Id](#customize-cyberark-application-id) topic for additional - information. The application can be locked down by providing an OS User, a Path, or a Hash. See +- An application must be added to CyberArk for the integration with Access Analyzer. You must then + add the Application Id of this application to the `GlobalOptions.xml` file for Access Analyzer. + See the [Customize CyberArk Application Id](#customize-cyberark-application-id) topic for + additional information. You can lock down the application by providing an OS User, a Path, or a + Hash. See the CyberArk [Add applications](https://docs.cyberark.com/credential-providers/14.0/en/Content/Common/Adding-Applications.htm) article for additional information. - The OS User needs to be the account running Access Analyzer. This could be the account used to launch the Access Analyzer application or an account used as the Schedule Service Account - within Access Analyzer. More than one OS User can be added. + within Access Analyzer. You can add more than one OS User. - The Path should be a local path to the `StealthAUDIT.exe` file. The path should end with the file name: `…\StealthAUDIT.exe`. - - The Hash should be generated using the **AimGetAppInfo** tool in the + - Generate the Hash using the **AimGetAppInfo** tool in the `…\CyberArk\ApplicationPasswordProvider\Utils` folder on the server where Secrets Manager is - installed. AimGetAppInfo should be run in an Administrator Command Prompt. Run the following + installed. Run AimGetAppInfo in an Administrator Command Prompt. Run the following command: ``` @@ -54,12 +55,12 @@ Password Vault, the following prerequisites must be completed: ![Allowed Machines list for the CyberArk application](/images/accessanalyzer/12.0/admin/settings/connection/allowedmachines.webp) - - The machine name for the Access Analyzer console needs to be added on the Allowed Machines + - Add the machine name for the Access Analyzer console to the Allowed Machines list for the CyberArk application -- Once the Secrets Manager installation has completed and the Access Analyzer application has been - created, the necessary CyberArk accounts must be given access to the Safes in which the Access - Analyzer service accounts are stored. This includes the account which was created automatically +- After the Secrets Manager installation completes and you create the Access Analyzer application, + give the necessary CyberArk accounts access to the Safes in which the Access + Analyzer service accounts are stored. This includes the account CyberArk creates automatically during the Secrets Manager installation, as well as the account created automatically as a result of the application creation. @@ -67,19 +68,19 @@ Password Vault, the following prerequisites must be completed: - The account created during the AIM installation is under the naming convention `Prov_[COMPUTERNAME]`, where `COMPUTERNAME` is the name of the computer on which AIM is - installed. This account should be given **Retrieve accounts**, **List accounts**, and **View - Safe Members** rights on the desired Safes. + installed. Give this account **Retrieve accounts**, **List accounts**, and **View + Safe Members** rights on the Safes it needs to access. - The account created during the application creation has the same name as the application - itself and should be given **Retrieve accounts** rights on the desired Safes + itself. Give it **Retrieve accounts** rights on the Safes it needs to access ## Customize CyberArk Application Id -The Application id value of the application created within CyberArk for the integration with Access -Analyzer must be configured within Access Analyzer. This is done in the `GlobalOptions.xml` file +You must configure Access Analyzer with the Application id value of the application created within +CyberArk for the integration. You do this in the `GlobalOptions.xml` file within the Access Analyzer installation directory. The default location is `…\STEALTHbits\StealthAUDIT\`. -Follow the steps to customize the CyberArk Application Id within Access Analyzer. +Customize the CyberArk Application Id within Access Analyzer: **Step 1 –** Navigate to the `GlobalOptions.xml` file. Open it with a text editor, for example Notepad. @@ -125,8 +126,8 @@ window when configuring an **Active Directory Account** or **Local Windows Accou The credential information supplied in the User Credentials window must be an exact match to what is in CyberArk as the privileged account for which it is linked. It is case-sensitive. -If the Connection Profile with a Local Windows Account credential using CyberArk password storage is -used to target multiple hosts, then the local credential on each host needs to have the exact same +If you use the Connection Profile with a Local Windows Account credential using CyberArk password +storage to target multiple hosts, the local credential on each host needs to have the exact same username and password combination. ![Connection view with CyberArk credentials](/images/accessanalyzer/12.0/admin/settings/connection/usercredentials.webp) @@ -141,8 +142,8 @@ in CyberArk. These values are case-sensitive, and must be an exact match. ![User Credentials window for Active Directory Account](/images/accessanalyzer/12.0/admin/settings/connection/usercredentialsad.webp) -The table below shows the values from your CyberArk configuration that the User Credentials window -should be populated with: +The following table shows the values from your CyberArk configuration that you should use to +populate the User Credentials window: | Access Analyzer | CyberArk Property | CyberArk Description | Example Value | | --------------- | ----------------- | -------------------------------------- | ----------------- | @@ -159,8 +160,8 @@ value is `` and the CyberArk Address property value is the server address. ![User Credentials window for Local Windows Account](/images/accessanalyzer/12.0/admin/settings/connection/usercredentialslocal.webp) -The table below shows the values from your CyberArk configuration that the User Credentials window -should be populated with: +The following table shows the values from your CyberArk configuration that you should use to +populate the User Credentials window: | Access Analyzer | CyberArk Property | CyberArk Description | Example Value | | --------------- | ----------------- | -------------------------------------- | ------------- | @@ -171,7 +172,7 @@ should be populated with: :::info Only use one Local Windows Account credential with CyberArk password storage in a Connection Profile. As part of the Access Analyzer to CyberArk integration, the Access Analyzer job -is stopped immediately if the query from Access Analyzer to CyberArk for the credential fails. -Therefore, a second credential within the Connection Profile would not be queried. +stops immediately if the query from Access Analyzer to CyberArk for the credential fails. +Therefore, Access Analyzer wouldn't query a second credential within the Connection Profile. ::: diff --git a/docs/accessanalyzer/12.0/admin/settings/connection/gmsa.md b/docs/accessanalyzer/12.0/admin/settings/connection/gmsa.md index 2a98ee4628..cde422d5c1 100644 --- a/docs/accessanalyzer/12.0/admin/settings/connection/gmsa.md +++ b/docs/accessanalyzer/12.0/admin/settings/connection/gmsa.md @@ -7,17 +7,17 @@ sidebar_position: 30 # Group Managed Service Accounts (gMSA) Configuration Access Analyzer can use a previously-configured Group Managed Service Accounts (gMSA/MSA) account. -Make sure that Managed Service Account is selected in the User Credentials window. See the +ensure that Managed Service Account is selected in the User Credentials window. See the [Create a Connection Profile](/docs/accessanalyzer/12.0/admin/settings/connection/create/create.md) or [Create a Schedule Service Account](/docs/accessanalyzer/12.0/admin/settings/schedule.md#create-a-schedule-service-account) topic for additional information. -To run a job or scheduled task with a gMSA/MSA account, the following prerequisites must be met: +To run a job or scheduled task with a gMSA/MSA account, meet the following prerequisites: - The account that Access Analyzer is run with must have permissions to retrieve the gMSA account password - The gMSA account must be a Local Admin in the target hosts -- The gMSA account does not have to be a local admin in the Access Analyzer Console +- The gMSA account doesn't have to be a local admin in the Access Analyzer Console - The Data Collector used must support unicode characters in the Connection Profile's credential password to retrieve the gMSA account password @@ -27,7 +27,7 @@ mechanism in the query configuration. ::: :::note Action Modules -Using action modules with gMSAs is not currently supported. +Access Analyzer doesn't support using action modules with gMSAs. ::: See the Microsoft diff --git a/docs/accessanalyzer/12.0/admin/settings/connection/overview.md b/docs/accessanalyzer/12.0/admin/settings/connection/overview.md index 9b256eb395..7a39233fb0 100644 --- a/docs/accessanalyzer/12.0/admin/settings/connection/overview.md +++ b/docs/accessanalyzer/12.0/admin/settings/connection/overview.md @@ -11,28 +11,28 @@ the information Access Analyzer uses to connect to the target hosts during job e ![Connection](/images/accessanalyzer/12.0/admin/settings/connection/connectionpage.webp) -There are two methods for authentication to a targeted host: +You can authenticate to a targeted host using one of two methods: - Use Local Login Credentials - Use a Connection Profile ## Use Local Login Credentials -This method is traditionally assigned through the **Only use the Windows account that the +You traditionally assign this method through the **Only use the Windows account that the application is run with System default** option. It is generally referred to as the System Default or trusted method. When used, Access Analyzer authenticates to the target hosts during host inventory or job execution with the Windows account used to launch Access Analyzer. This can be: -- Account which was used to log on to the Access Analyzer Console server and start the application -- Account which was used to launch the Access Analyzer application through the run-as security +- Account used to log on to the Access Analyzer Console server and start the application +- Account used to launch the Access Analyzer application through the run-as security context -- Account which was used to provision a Windows scheduled task when running a job group or job via a +- Account used to provision a Windows scheduled task when running a job group or job via a scheduled task ## Use a Connection Profile -This method allows you to define a Connection Profile which houses one or several sets of -credentials to be used for authentication on the target hosts during host inventory or job +Use this method to define a Connection Profile which houses one or several sets of +credentials for authentication on the target hosts during host inventory or job execution. The credentials specified in a Connection Profile could be any of the following: - Local machine account @@ -44,21 +44,21 @@ execution. The credentials specified in a Connection Profile could be any of the - Web service JWT - Oracle account -For the majority of auditing scenarios, domain-based accounts are preferred if not required by the -nature of the auditing task. The credentials must have the permissions required by the data +For the majority of auditing scenarios, use domain-based accounts unless the auditing task requires +otherwise. The credentials must have the permissions required by the data collector being used. ### Password Storage Options -The password for the credential provided can be stored in Access Analyzer application or Access -Analyzer Vault. Certain types of credentials can be stored in CyberArk®. +You can store the password for the credential provided in the Access Analyzer application or +Access Analyzer Vault. You can store certain types of credentials in CyberArk®. -Choosing to store passwords in either the Access Analyzer application or the Access Analyzer Vault -is a global setting configured in the **Settings** > **Application** node. See the +You configure whether to store passwords in the Access Analyzer application or the Access Analyzer +Vault as a global setting in the **Settings** > **Application** node. See the [Application](/docs/accessanalyzer/12.0/admin/settings/application/overview.md) topic for additional information. The Access Analyzer vault provides enhanced security through enhanced encryption to various -credentials stored by the Access Analyzer application. See the [Vault](/docs/accessanalyzer/12.0/admin/settings/application/vault.md) +credentials the Access Analyzer application stores. See the [Vault](/docs/accessanalyzer/12.0/admin/settings/application/vault.md) topic for additional information. CyberArk integration stores supported credentials in the CyberArk Enterprise Password Vault. @@ -70,9 +70,9 @@ additional information. ![Cancel and Save options](/images/accessanalyzer/12.0/admin/settings/connection/cancelsavebuttons.webp) The **Cancel** and **Save** buttons are in the lower-right corner of the Connection view. These -buttons become enabled when modifications are made to the Connection global setting. +buttons become enabled when you modify the Connection global setting. ![Information update message box](/images/accessanalyzer/12.0/admin/settings/connection/settingssavedmessage.webp) -Whenever changes are made at the global level, click **Save** and then **OK** to confirm the -changes. Otherwise, click **Cancel** if no changes were intended. +Whenever you make changes at the global level, click **Save** and then **OK** to confirm the +changes. Otherwise, click **Cancel** if you didn't intend to make changes. diff --git a/docs/accessanalyzer/12.0/admin/settings/exchange.md b/docs/accessanalyzer/12.0/admin/settings/exchange.md index 9f147534b5..3f750966a2 100644 --- a/docs/accessanalyzer/12.0/admin/settings/exchange.md +++ b/docs/accessanalyzer/12.0/admin/settings/exchange.md @@ -11,22 +11,22 @@ These settings are exclusive to the Access Analyzer for Exchange Solution. ![Exchange - Set up the connection](/images/accessanalyzer/12.0/admin/settings/exchange_1.webp) -The Exchange node is grayed-out by default. In order for these settings to be enabled, it is -necessary to install both Access Analyzer MAPI CDO and Microsoft Exchange MAPI CDO on the Access -Analyzer Console server. See the +The Exchange node is grayed-out by default. To enable these settings, install both Access Analyzer +MAPI CDO and Microsoft Exchange MAPI CDO on the Access Analyzer Console server. See the [StealthAUDIT MAPI CDO Installation](/docs/accessanalyzer/12.0/install/mapicdo/installation.md) topic for additional information. -Once the requirements have been met, the Exchange node is enabled for configuration. These settings -are utilized to make MAPI connections to the Exchange Server for the Mailbox, PublicFolder, -Exchange2K, and ExchangePS Data Collectors. The Client Access Server field, or CAS, is also utilized -by the ExchangePS Data Collector in order to make Remote PowerShell connections for Exchange 2010 or -newer. The data collectors apply these settings unless modified inside the job query. +After you meet the requirements, Access Analyzer enables the Exchange node for configuration. +Access Analyzer uses these settings to make MAPI connections to the Exchange Server for the +Mailbox, PublicFolder, Exchange2K, and ExchangePS Data Collectors. The ExchangePS Data Collector +also uses the Client Access Server field, or CAS, to make Remote PowerShell connections for +Exchange 2010 or newer. The data collectors apply these settings unless modified inside the job +query. ![Set up the connection](/images/accessanalyzer/12.0/admin/settings/exchange_3.webp) The three options in the Exchange Connection Setting section at the top of the window are dependent -on which version of Exchange is audited. +on which version of Exchange you audit. - For Auditing Microsoft Exchange 2007 or Older Versions: - Select the radio button for System Attendant (2003 & 2007) – The System Attendant Account is @@ -39,38 +39,38 @@ on which version of Exchange is audited. - Use the mailbox associated with the Windows account that Access Analyzer is run with – This option uses either the account logged into the Access Analyzer Console server or the account set to run the Access Analyzer application. - - Exchange Mailbox (2010 and newer) – This option allows an Exchange Mailbox Alias to be - specified for MAPI connections. + - Exchange Mailbox (2010 and newer) – This option lets you specify an Exchange Mailbox + Alias for MAPI connections. - Enter the Alias name in the textbox. The Alias needs to be an Exchange 2010 or newer - mailbox, not a mail-enabled service account. However, this mailbox does not need + mailbox, not a mail-enabled service account. However, this mailbox doesn't need rights on the Exchange Organization; it only needs to reside within it. - Enter the name of the physical CAS in the Client Access Server textbox. This server can be - part of an array, but do not enter the name of a CAS Array. This should also be the - Exchange CAS where both Remote PowerShell and Windows Authentication on the PowerShell - Virtual Directory have been enabled. + part of an array, but don't enter the name of a CAS Array. This should also be the + Exchange CAS where you have enabled both Remote PowerShell and Windows Authentication on + the PowerShell Virtual Directory. :::info -Once the Exchange Connection Settings have been properly configured for the -version of Exchange to be audited, it is strongly recommended that the settings be tested. +After you properly configure the Exchange Connection Settings for the version of Exchange you +want to audit, test the settings. ::: In the Test Exchange Connection Settings section: -- Enter a Mailbox Server with mailboxes to be audited in the Exchange Server textbox. +- Enter a Mailbox Server with mailboxes you want to audit in the Exchange Server textbox. - Click the Test Exchange settings link. ![Test Exchange Connection Setting](/images/accessanalyzer/12.0/admin/settings/exchange_4.webp) If the Exchange Connection Settings are correct, an output field opens. At the bottom of the output -field, a mailbox count is stated and a message appears which says, “You have successfully connected -to this Exchange Server.” Click OK. +field, Access Analyzer states a mailbox count and displays a message that says, “You have +successfully connected to this Exchange Server.” Click OK. ![exchange_6](/images/accessanalyzer/12.0/admin/settings/exchange_6.webp) The Cancel and Save buttons are in the lower-right corner of the Exchange view. These buttons become -enabled when modifications are made to the Exchange global setting. Whenever changes are made at the -global level, click Save and then OK to confirm the changes. Otherwise, click Cancel if no changes -were intended. +enabled when you modify the Exchange global setting. Whenever you make changes at the +global level, click Save and then OK to confirm the changes. Otherwise, click Cancel if you didn't +intend to make changes. diff --git a/docs/accessanalyzer/12.0/admin/settings/history.md b/docs/accessanalyzer/12.0/admin/settings/history.md index 51bc3dc6d2..7682ffa7bf 100644 --- a/docs/accessanalyzer/12.0/admin/settings/history.md +++ b/docs/accessanalyzer/12.0/admin/settings/history.md @@ -6,7 +6,7 @@ sidebar_position: 50 # History -The History node is where the history retention of job data and job logs are configured. The setting +The History node is where you configure the history retention of job data and job logs. The setting specified here at the global level applies to all jobs in the Jobs tree unless specifically changed at the job group or job level. See the [History Node](/docs/accessanalyzer/12.0/admin/jobs/group/settings/history.md) and [History Tab](/docs/accessanalyzer/12.0/admin/jobs/job/properties/history.md) topics for additional information. @@ -14,7 +14,7 @@ at the job group or job level. See the [History Node](/docs/accessanalyzer/12.0/ ![History Global Settings](/images/accessanalyzer/12.0/admin/settings/history.webp) The Data Retention Period settings are for configuring the job data history retention within the -database. There are three options: +database. Choose from three options: - Never retain previous job data - Retain previous job data for [number] [time period] @@ -25,29 +25,30 @@ for more control over the quantity of data by applying history retention at the level. All jobs run with this default setting only keep the most current record set. :::warning -It is important to understand that some pre-configured jobs require history retention -while others do not support it. Changing the history retention settings at the global level can +Some pre-configured jobs require history retention +while others don't support it. Changing the history retention settings at the global level can cause issues with data analysis and reporting on jobs that don't support it. See the relevant job group and job descriptions for additional information. ::: -The Diagnostics Retention Period settings determine how long this data is retained for all jobs that -do not have an explicit setting. Setting the retention period for a specific job overrides the -default setting. There are two settings: +The Diagnostics Retention Period settings determine how long Access Analyzer retains this data for +all jobs that don't have an explicit setting. Setting the retention period for a specific job +overrides the default setting. Configure two settings: - Logs and Messages - Retain previous application logs, job logs, and messages for [number] [time period] – Controls - how long the messages for previous job executions are stored in the SA_Messages table for each - job. Older job execution messages are cleared. - - The default value is 7 Times. With this setting, the messages are stored for the previous - seven job executions. + how long Access Analyzer stores the messages for previous job executions in the SA_Messages + table for each job. Access Analyzer clears older job execution messages. + - The default value is 7 Times. With this setting, Access Analyzer stores the messages for the + previous seven job executions. - Job Statistics - - Retain job statistics in database for [number] [time period] – Controls how long job - statistics history is stored within the Access Analyzer database in the following two tables: + - Retain job statistics in database for [number] [time period] – Controls how long Access + Analyzer stores job statistics history within the Access Analyzer database in the following + two tables: - SA_JobStatsTbl - SA_JobTaskStatsTbl @@ -56,19 +57,19 @@ default setting. There are two settings: This directly affects each job’s **Status** node. See the [Status Node](/docs/accessanalyzer/12.0/admin/jobs/job/status.md) topic for additional information. -For both the **Logs and Messages** and **Job Statistics** options above: +For both the **Logs and Messages** and **Job Statistics** options: -- Enter a number in the first textbox and select the desired time period from the drop-down menu in - the second box. Retention can be set to a specific number of **Days**, **Weeks**, **Months**, or +- Enter a number in the first textbox and select the time period you want from the dropdown menu in + the second box. You can set retention to a specific number of **Days**, **Weeks**, **Months**, or **Times** for both. - All jobs run with this setting add the newly collected data set or job logs on top of the - previously collected record sets or logs. Any record sets or logs outside the specified historical - retention limit are dropped. + previously collected record sets or logs. Access Analyzer drops any record sets or logs outside + the specified historical retention limit. The **Cancel** and **Save** buttons are in the lower-right corner of the History view. These buttons -become enabled when modifications are made to the History global settings. Whenever changes are made +become enabled when you modify the History global settings. Whenever you make changes at the global level, click **Save** and then **OK** to confirm the changes. Otherwise, click -**Cancel** if no changes were intended. +**Cancel** if you didn't intend to make changes. ## Job Data History Retention & Database Size Concerns @@ -80,19 +81,19 @@ following scenario explains a common concern. - To reduce data retention periods, navigate to the **Settings** > **History** node. Change the time period to a smaller interval, for example 90 days. Click **Save** and rerun the jobs. - - All of the record sets outside the new retention limit are dropped, and the database size is - back down where it belongs + - Access Analyzer drops all of the record sets outside the new retention limit, and the + database size returns to where it belongs ## Job Logs -The job logs are stored within the output folder of each job. They can be read in the Access -Analyzer Console within the job’s **Status** > **Messages** table. To access the logs within the -job’s directory, right-click on the job’s node in the Navigation pane and select **Explore Folder**. +Access Analyzer stores the job logs within the output folder of each job. You can read them in the +Access Analyzer Console within the job’s **Status** > **Messages** table. To access the logs within the +job’s directory, right-click the job’s node in the Navigation pane and select **Explore Folder**. ![Job Logs in the job's Output folder in File Explorer](/images/accessanalyzer/12.0/admin/settings/historyjoblogs.webp) -The most recent log is open. Older jobs are stored as zip files, according to the Log Retention -Period setting. Each log is named in the following format: +The most recent log is open. Access Analyzer stores older jobs as zip files, according to the Log +Retention Period setting. Access Analyzer names each log in the following format: - Open/Latest Log Name – `[Jobname]_Log.tsv` - Older/Zipped Log Name – `[Jobname]_Log_[Date]_[Time].zip` diff --git a/docs/accessanalyzer/12.0/admin/settings/hostdiscovery.md b/docs/accessanalyzer/12.0/admin/settings/hostdiscovery.md index 4b2527683a..8ea3ac1522 100644 --- a/docs/accessanalyzer/12.0/admin/settings/hostdiscovery.md +++ b/docs/accessanalyzer/12.0/admin/settings/hostdiscovery.md @@ -7,23 +7,23 @@ sidebar_position: 60 # Host Discovery The Host Discovery node is for configuring the settings which dictate how Access Analyzer handles -newly discovered hosts, what information is logged during the host discovery process, and how long -the logged information is stored. +newly discovered hosts, what information Access Analyzer logs during the host discovery process, +and how long it stores the logged information. ![Host Discovery page](/images/accessanalyzer/12.0/admin/settings/hostdiscovery.webp) In the Host Discovery Options section at the top is a checkbox for the **Perform the first inventory -right away for newly discovered hosts** option. This option is selected by default. +right away for newly discovered hosts** option. By default, Access Analyzer selects this option. - If selected, Access Analyzer retrieves information about a host as soon as it is discovered -- If deselected, the host inventory information can be obtained later according to the Host +- If deselected, you can obtain the host inventory information later according to the Host Inventory node options The configurable options in the Discovery Log section are: -- Retention period – Determines how long the Host Discovery query log is kept. This is set by - default to 14 days which is based on average Access Analyzer usage. -- Log level – Determines what information is stored in the Host Discover query log +- Retention period – Determines how long Access Analyzer keeps the Host Discovery query log. This + defaults to 14 days, based on average Access Analyzer usage. +- Log level – Determines what information Access Analyzer stores in the Host Discover query log ![Log level options](/images/accessanalyzer/12.0/admin/settings/hostdiscoveryloglevels.webp) @@ -33,8 +33,8 @@ The log levels are: logging - Records all Info level information - - If files are referenced or updated during the process of running the query then the path to - the affected file is shown + - If the query references or updates files while running, Access Analyzer shows the path to + the affected file - Helps [Netwrix Support](https://www.netwrix.com/support.html) to assist in diagnosing issues which may be causing host inventories to fail - Creates the largest file @@ -56,16 +56,15 @@ The log levels are: - Error – Records all errors which occur during the host discovery process :::info - Set the Log Level to Error. The default setting is Info, but it is - recommended that the setting for daily use be set to Error. The other log levels are designed to - assist with troubleshooting host discovery and host inventory issues. + Set the Log Level to Error for daily use. The default setting is Info. The other log levels + are designed to assist with troubleshooting host discovery and host inventory issues. ::: The **Cancel** and **Save** buttons are in the lower-right corner of the Host Discovery view. These -buttons become enabled when modifications are made to the Host Discovery global settings. Whenever -changes are made at the global level, click **Save** and then **OK** to confirm the changes. -Otherwise, click **Cancel** if no changes were intended. +buttons become enabled when you modify the Host Discovery global settings. Whenever +you make changes at the global level, click **Save** and then **OK** to confirm the changes. +Otherwise, click **Cancel** if you didn't intend to make changes. ![Host Discovery Log under Host Discovery node](/images/accessanalyzer/12.0/admin/settings/hostdiscoverylog.webp) diff --git a/docs/accessanalyzer/12.0/admin/settings/hostinventory.md b/docs/accessanalyzer/12.0/admin/settings/hostinventory.md index dd7dc1eda9..8bc3e5f7c1 100644 --- a/docs/accessanalyzer/12.0/admin/settings/hostinventory.md +++ b/docs/accessanalyzer/12.0/admin/settings/hostinventory.md @@ -12,7 +12,7 @@ setting what out-of-the box host lists are visible in the Host Management node. ![Host Inventory Settings page](/images/accessanalyzer/12.0/admin/settings/hostinventory.webp) -In the Inventory Items section, there are four program property groups: +The Inventory Items section contains four program property groups: - Operating System – Includes 7 Items - Application – Includes 7 Items @@ -21,8 +21,8 @@ In the Inventory Items section, there are four program property groups: Each of these groups brings back the properties enumerated in the list below the group title. These collected properties correspond to the columns in the Host Management tables. Deselecting a checkbox -prevents that information from being collected for target hosts. However, some solutions require -this information. +prevents Access Analyzer from collecting that information for target hosts. However, some +solutions require this information. :::info Leave the default setting of all the groups selected. Consult with @@ -31,15 +31,15 @@ groups. ::: -In the Performance Tuning section, there are five settings which allocate console resources to the +The Performance Tuning section contains five settings that allocate console resources to the host inventory process: -- Threads – Indicates the number of job threads that are employed during the host inventory process +- Threads – Indicates the number of job threads Access Analyzer employs during the host inventory + process - The default setting is 20 Threads - - Maximum thread count is 100. Thread count will revert back to 100 if values over 100 are - entered. - - Restart Access Analyzer if thread count is changed for changes to take place + - Maximum thread count is 100. Thread count reverts back to 100 if you enter values over 100. + - Restart Access Analyzer if you change thread count for changes to take place - Thread timeout [in seconds] – Indicates the time a thread will spend in retrieving information from a host @@ -48,16 +48,16 @@ host inventory process: - If thread can't receive an active response from target host, the thread will move on to the next host in the queue -- Stop on Failed Ping – If the Stop on Failed Ping checkbox is selected, hosts that don't respond - to pings aren't queried. Otherwise, hosts will be queried regardless. +- Stop on Failed Ping – If the Stop on Failed Ping checkbox is selected, Access Analyzer doesn't + query hosts that don't respond to pings. Otherwise, Access Analyzer queries hosts regardless. - PING timeout [in seconds] – Indicates the time a thread will spend pinging a host - Default setting is 4 seconds - - If thread can't connect with a host, the host will be designated as being offline and the - thread will move on to the next host in the queue + - If the thread can't connect with a host, Access Analyzer designates the host as offline and + the thread moves on to the next host in the queue - Only refresh inventory items older than [time selected] – Indicates the time that needs to pass - before the host inventory process is automatically refreshed + before Access Analyzer automatically refreshes the host inventory process - Default setting is 60 days - The number textbox has a five-character limit @@ -72,16 +72,17 @@ host inventory process: [Host Discovery Wizard](/docs/accessanalyzer/12.0/admin/hostdiscovery/wizard/overview.md) topic for additional information. The Desired Host List Views section at the bottom contains all available host lists, both -built-in lists and custom-created lists. There are seven Default Hosts Lists which correspond -to the solutions that target them. During the host inventory process, hosts which meet the filter -criteria for these default lists are automatically populated into that host list. A checkmark in +built-in lists and custom-created lists. Seven Default Host Lists correspond +to the solutions that target them. During the host inventory process, Access Analyzer automatically +populates hosts which meet the filter criteria for these default lists into that host list. A +checkmark in front of the host list indicates that the list is visible in the **Host Management** > **All Hosts** node. The **Cancel** and **Save** buttons are in the lower-right corner of the Host Inventory view. These -buttons become enabled when modifications are made to the Host Inventory global settings. Whenever -changes are made at the global level, click **Save** and then **OK** to confirm the changes. -Otherwise, click **Cancel** if no changes were intended. +buttons become enabled when you modify the Host Inventory global settings. Whenever +you make changes at the global level, click **Save** and then **OK** to confirm the changes. +Otherwise, click **Cancel** if you didn't intend to make changes. ## Default Host Lists @@ -90,7 +91,7 @@ filter criteria. These lists correspond to the pre-configured solution jobs whic ### AD Host List -The **AD** Host List can be expanded and contains five sub-groups used by the Active Directory +You can expand the **AD** Host List, which contains five sub-groups used by the Active Directory Solution and the Active Directory Inventory Solution: ![AD Host List](/images/accessanalyzer/12.0/admin/settings/ad.webp) @@ -113,7 +114,7 @@ There are no sub-groups for ALL WINDOWS HOSTS. ### DG Host List -The **DG** Host List can be expanded and contains three sub-groups used by the Data Access +You can expand the **DG** Host List, which contains three sub-groups used by the Data Access Governance for File System Solution. ![DG Host List](/images/accessanalyzer/12.0/admin/settings/dg.webp) @@ -126,8 +127,8 @@ The sub-groups are: ### EXCHANGE Host List -The **EXCHANGE** Host List can be expanded and contains six sub-groups used by the Exchange -Solution. Four of these sub-groups can also be expand. +You can expand the **EXCHANGE** Host List, which contains six sub-groups used by the Exchange +Solution. You can also expand four of these sub-groups. ![EXCHANGE Host List](/images/accessanalyzer/12.0/admin/settings/exchange.webp) @@ -153,7 +154,7 @@ There are no sub-groups for SQL SERVERS. ### Windows Server Host List -The **Windows Server** Host List can be expanded and contains three sub-groups used by the +You can expand the **Windows Server** Host List, which contains three sub-groups used by the Windows Solution. ![Windows Server Host List](/images/accessanalyzer/12.0/admin/settings/windowsserver.webp) @@ -166,7 +167,7 @@ The sub-groups are: ### Work Station Host List -The **Work Station** Host List can be expanded and contains one sub-group used by the Windows +You can expand the **Work Station** Host List, which contains one sub-group used by the Windows Solution. ![Work Station Host List](/images/accessanalyzer/12.0/admin/settings/workstation.webp) diff --git a/docs/accessanalyzer/12.0/admin/settings/notification.md b/docs/accessanalyzer/12.0/admin/settings/notification.md index 0a54bbec5c..8462576bce 100644 --- a/docs/accessanalyzer/12.0/admin/settings/notification.md +++ b/docs/accessanalyzer/12.0/admin/settings/notification.md @@ -6,31 +6,31 @@ sidebar_position: 80 # Notification -The Notification node is where email notifications are configured. Emails can be sent from the +The Notification node is where you configure email notifications. You can send emails from the Access Analyzer Console for a variety of purposes: reports on collected data, change detection alerts, conformance analysis notification, and more. ![Global Settings Notification page](/images/accessanalyzer/12.0/admin/settings/notification.webp) -To enable notifications from the Access Analyzer Console, a mail server must be configured for +To enable notifications from the Access Analyzer Console, configure a mail server for Access Analyzer to employ for sending emails. -Access Analyzer supports authentication and encryption when sending email notifications. -Notifications can be configured based on the requirements of an organizations mail environment. +Access Analyzer supports authentication and encryption when sending email notifications. You can +configure notifications based on the requirements of an organizations mail environment. -Enable Access Analyzer notifications by configuring the Mail Server and Sender Information. It is -recommended to send a test email to yourself after initial configuration to ensure proper settings. +Enable Access Analyzer notifications by configuring the Mail Server and Sender Information. Send a +test email to yourself after initial configuration to ensure proper settings. See the [Test Notification Settings](#test-notification-settings) topic for additional information. The **Cancel** and **Save** buttons are in the lower-right corner of the Notification view. These -buttons become enabled when modifications are made to the Notification global setting. Whenever -changes are made at the global level, click **Save** and then **OK** to confirm the changes. -Otherwise, click **Cancel** if no changes were intended. +buttons become enabled when you modify the Notification global setting. Whenever +you make changes at the global level, click **Save** and then **OK** to confirm the changes. +Otherwise, click **Cancel** if you didn't intend to make changes. ## Configure SMTP Server Information -The Mail Server section at the top of the page is where an organization’s SMTP Server information is -provided. +The Mail Server section at the top of the page is where you provide an organization’s SMTP Server +information. ![Mail Server settings on Notification page](/images/accessanalyzer/12.0/admin/settings/server.webp) @@ -67,45 +67,45 @@ account. **Step 2 –** Click **Save**. -The credentials for Mail Server authentication account have been updated and committed to the -Console. +Access Analyzer updates and commits the credentials for the Mail Server authentication account to +the Console. ## Sender Information -The Sender Information section is where the sender information is provided. +The Sender Information section is where you provide the sender information. ![Sender Information section on Notification page](/images/accessanalyzer/12.0/admin/settings/senderinformation.webp) Configure the sender information for all Access Analyzer notifications. Since this is a global settings, any recipients configured at this level receive all notifications sent from Access -Analyzer, and are sent to this recipient list unless inheritance is broken at the job group or job +Analyzer, and are sent to this recipient list unless you break inheritance at the job group or job level. - Sender Name – Name displayed in the sent from field of the email -- Sender Address – Sender’s email address. This does not have to be a real email address, unless +- Sender Address – Sender’s email address. This doesn't have to be a real email address, unless required by the organization. It can be something as simple as `accessanalyzer@yourdomain.com`. ## Email Content -The Email Content section is where the recipient information is provided. +The Email Content section is where you provide the recipient information. ![Email Content section on Notification page](/images/accessanalyzer/12.0/admin/settings/emailcontent.webp) - To / CC / BCC – Enter the email addresses for the recipients of the email notifications. Use a semicolon (;) to separate multiple recipients. - Recipients listed at this global level receive all email notifications sent by Access Analyzer - unless inheritance is broken at the job group or job levels + unless you break inheritance at the job group or job levels ## Test Notification Settings -Once the global **Notification** settings have been configured, it is recommended to send a test -email to ensure proper configuration. This verifies all settings are correct and email is received -as expected. +After you configure the global **Notification** settings, send a test +email to ensure proper configuration. This verifies all settings are correct and that you receive +the email as expected. ![Test Email Settings button](/images/accessanalyzer/12.0/admin/settings/test.webp) -The Test Email Settings button sends a test email to the recipient list. It is recommended that you -test by sending an email to yourself. Once all Notification settings are configured, click the +The Test Email Settings button sends a test email to the recipient list. Test by sending an email +to yourself. Once you configure all Notification settings, click the **Test Email Settings** button. ![Test email sent successfully message](/images/accessanalyzer/12.0/admin/settings/testsuccess.webp) @@ -115,13 +115,14 @@ A message displays stating that the test e-mail was sent successfully. ![Test email error message example](/images/accessanalyzer/12.0/admin/settings/testerror.webp) :::note -If there are any problems with the information, an error message will appear during the -Test Email settings process. Correct the Notification settings until the test email is sent -successfully. +If any problems occur with the information, an error message appears during the +Test Email settings process. Correct the Notification settings until Access Analyzer sends the +test email successfully. ::: ![Netwrix Enterprise Auditor test e-mail](/images/accessanalyzer/12.0/admin/settings/testemail.webp) -This email is sent to all recipients when the **Test Email settings** link is clicked. When the -Notification settings are configured, click **Save** and then **Ok** to complete the configuration. +Access Analyzer sends this email to all recipients when you click the **Test Email settings** +link. When you configure the Notification settings, click **Save** and then **Ok** to complete +the configuration. diff --git a/docs/accessanalyzer/12.0/admin/settings/overview.md b/docs/accessanalyzer/12.0/admin/settings/overview.md index 0fd64df73b..80fb7fc0cd 100644 --- a/docs/accessanalyzer/12.0/admin/settings/overview.md +++ b/docs/accessanalyzer/12.0/admin/settings/overview.md @@ -6,15 +6,15 @@ sidebar_position: 20 # Global Settings -The global settings have an overall impact on the running ofAccess Analyzer jobs. Settings are -inherited through a parent-child structure from the Settings node through the Jobs tree to the -individual jobs unless inheritance is broken by direct assignment at either the job group or the -individual job level. +The global settings have an overall impact on the running of Access Analyzer jobs. Access Analyzer +inherits settings through a parent-child structure from the Settings node through the Jobs tree to +the individual jobs, unless direct assignment at either the job group or the individual job level +breaks the inheritance. ![Configuration Settings](/images/accessanalyzer/12.0/admin/settings/globalsettings.webp) -Some of these settings are configured during the initial launching of theAccess Analyzer Console. -Others are configured as desired by the end-user. Expand the Settings node in the Navigation pane to +You configure some of these settings during the initial launch of the Access Analyzer Console, and +configure others as needed. Expand the Settings node in the Navigation pane to select a global setting to configure: - [Access](/docs/accessanalyzer/12.0/admin/settings/access/overview.md) @@ -37,11 +37,11 @@ select a global setting to configure: according to the data collector being used - [Exchange](/docs/accessanalyzer/12.0/admin/settings/exchange.md) - Required for auditing an organization’s Exchange environment - - Only enabled for configuration once the Access Analyzer for Exchange Solution prerequisites + - Only enabled for configuration after the Access Analyzer for Exchange Solution prerequisites are installed - Configure Microsoft Exchange server connections and requires Exchange server versions and names - - The ExchangeMailbox, Exchange2K, ExchangePS, and ExchangePublicFolder Data Collectors utilize + - The ExchangeMailbox, Exchange2K, ExchangePS, and ExchangePublicFolder Data Collectors use these global settings - [History](/docs/accessanalyzer/12.0/admin/settings/history.md) - Configure job data retention period settings @@ -65,11 +65,11 @@ select a global setting to configure: - [Schedule](/docs/accessanalyzer/12.0/admin/settings/schedule.md) - Optional configuration during the initial launch if Windows authentication is used with the Storage Profile - - Required in order to schedule host inventory, job, analysis task, and action task execution + - Required to schedule host inventory, job, analysis task, and action task execution - Provide credentials used against the Access Analyzer Console server to execute scheduled jobs with the Windows Task Scheduler - Creating a Schedule Service Account requires credentials on the Access Analyzer Console server - - Multiple Schedule Service Accounts can be configured + - You can configure multiple Schedule Service Accounts - [Sensitive Data](/docs/accessanalyzer/12.0/admin/settings/sensitivedata/overview.md) - Flag locations which are known to contain false positive criteria matches to be filtered out of Sensitive Data Discovery reports diff --git a/docs/accessanalyzer/12.0/admin/settings/reporting.md b/docs/accessanalyzer/12.0/admin/settings/reporting.md index 65df5f4142..46a8e259bd 100644 --- a/docs/accessanalyzer/12.0/admin/settings/reporting.md +++ b/docs/accessanalyzer/12.0/admin/settings/reporting.md @@ -7,21 +7,20 @@ sidebar_position: 90 # Reporting The Reporting node is for configuring the global settings for publishing Access Analyzer reports. -The Web Console is where any reports which have been published can be viewed outside of the Access +The Web Console is where users can view published reports outside the Access Analyzer Console. The Web Console provides a consolidated logon housing both the published reports -and the AIC (when applicable). +and the Access Information Center (AIC) (when applicable). ![Global Settings Reporting page](/images/accessanalyzer/12.0/admin/settings/reporting.webp) -The publishing of reports can be disabled at the global level by selecting **Do not publish -reports** from the Publish Option drop-down menu. It can also be disabled at the job group, job, or +The publishing of reports can be disabled at the global level by selecting **Don't publish +reports** from the Publish Option dropdown menu. It can also be disabled at the job group, job, or report configuration level. See the [Jobs Tree](/docs/accessanalyzer/12.0/admin/jobs/overview.md) topic for additional information. The **Cancel** and **Save** buttons are in the lower-right corner of the Reporting view. These -buttons become enabled when modifications are made to the Reporting global settings. Whenever -changes are made at the global level, click **Save** and then **OK** to confirm the changes. -Otherwise, click **Cancel** if no changes were intended. +buttons become enabled when you modify the Reporting global settings. Whenever you make changes at the global level, click **Save** and then **OK** to confirm the changes. +Otherwise, click **Cancel** if you didn't intend to make changes. ## Website URL @@ -34,10 +33,10 @@ The default address is: http://[Fully Qualified Domain Name of the Access Analyzer Console server]:8082 -This link is used to access the Web Console, and it is used for the web link in an emailed report. -The protocol and port number may need to be modified to align with the organization’s environment, -but it must match the information in the website’s configuration file. If the Web Console has been -secured, this address must be manually updated: +This link accesses the Web Console, and it also serves as the web link in an emailed report. +You might need to modify the protocol and port number to align with the organization’s environment, +but it must match the information in the website’s configuration file. If the Web Console is +secured, you must manually update this address: https://[Fully Qualified Domain Name of the StealthAUDIT Console server]:[Port Number] @@ -51,11 +50,11 @@ topic for additional information. ## Publish Option -The Publish Option allows you to enable or disable the publishing of reports at the global level. +Use the Publish Option to enable or disable the publishing of reports at the global level. ![Publish Option on Global Settings Reporting page](/images/accessanalyzer/12.0/admin/settings/publish.webp) -Select the **Publish reports** option to publish all Access Analyzer reports or select **Do not +Select the **Publish reports** option to publish all Access Analyzer reports or select **Don't publish reports** to disable the publishing. The inheritance of this setting can be broken at the job group, job, or report levels. @@ -65,10 +64,10 @@ Configure email reports sent out by Access Analyzer using the Email Report optio ![Email options on Global Settings Reporting page](/images/accessanalyzer/12.0/admin/settings/email.webp) -The **E-mail reports** checkbox enables recipients to receive all published reports, unless -inheritance is broken at the job group, job, or report level. Separate multiple recipients with a -semicolon. If commas are used as delimiters for email addresses, they will be converted into -semicolons when the settings are saved. +The **E-mail reports** checkbox enables recipients to receive all published reports, unless direct +assignment at the job group, job, or report level breaks the inheritance. Separate multiple +recipients with a semicolon. If you use commas to delimit email addresses, Access Analyzer converts +them into semicolons when you save the settings. :::info Configure email reporting at a specific level to ensure recipients only receive @@ -77,23 +76,23 @@ reports which apply to them. :::note -Email reports does not work unless Access Analyzer has been configured to send email +Email reports doesn't work unless you configure Access Analyzer to send email notifications through the **Notification** node. See the [Notification](/docs/accessanalyzer/12.0/admin/settings/notification.md) topic for additional information. ::: -The **Do Not Email Report If Blank** checkbox prevents reports from being sent via email if all -elements are blank when generated. A blank report can occur if there is an error in data collection -or if the report is configured for data which might not always be present (for example, new computer -objects created since last scan). +The **Don't Email Report If Blank** checkbox stops Access Analyzer from sending reports by email if +all elements are blank when generated. A blank report can occur if there is an error in data +collection or if you configured the report for data that might not always be present (for example, +new computer objects created since last scan). :::info -Enable the **Do Not Email Report If Blank** option. +Enable the **Don't Email Report If Blank** option. ::: -The report can be sent using the desired **Email Content** option: +You can send the report using the **Email Content** option you want: - Web Link – Sends an email notice that the report has been published and provides the recipient with a link to it in the Web console @@ -102,15 +101,15 @@ The report can be sent using the desired **Email Content** option: without row limit) to an email as a CSV file, excluding any charts - PDF – Attaches the report to an email as a PDF file -The **Subject(Prefix)** field identifies the prefix of the email subject line, unless inheritance is -broken at the job group, job, or report level. The prefix appears in the email header preceding the +The **Subject(Prefix)** field identifies the prefix of the email subject line, unless direct +assignment at the job group, job, or report level breaks the inheritance. The prefix appears in the email header preceding the report name. If left blank, Access Analyzer applies a prefix of `Access Analyzer Report` to the email subject line. ## Configure JavaScript Settings for the Web Console Any browser used to access the Web Console must have JavaScript allowed for all features of the Web -Console to function correctly. If the JavaScript permission is not set as allowed for the entire +Console to function correctly. If the JavaScript permission isn't set as allowed for the entire browser, you must add the Web Console as an allowed site. Follow the steps to allow JavaScript on the Web Console in Microsoft Edge. @@ -128,9 +127,9 @@ under All permissions. Console and click **Add**. :::note -If the global Allowed option is selected, you do not need to specifically add the Web +If you select the global Allowed option, you don't need to specifically add the Web Console as an allowed site. ::: -The Web Console's URL is added to the Allow list and JavaScript is enabled for the Web Console. +Microsoft Edge adds the Web Console's URL to the Allow list and enables JavaScript for the Web Console. diff --git a/docs/accessanalyzer/12.0/admin/settings/schedule.md b/docs/accessanalyzer/12.0/admin/settings/schedule.md index 460ecd17df..884a6ca30e 100644 --- a/docs/accessanalyzer/12.0/admin/settings/schedule.md +++ b/docs/accessanalyzer/12.0/admin/settings/schedule.md @@ -6,28 +6,28 @@ sidebar_position: 100 # Schedule -The Schedule node contains objects referred to as Schedule Service Accounts. A Schedule Service -Account is used to run scheduled tasks on the Access Analyzer Console server. +The Schedule node contains objects referred to as Schedule Service Accounts. Use a Schedule Service +Account to run scheduled tasks on the Access Analyzer Console server. ![Schedule node](/images/accessanalyzer/12.0/admin/settings/schedule.webp) -Jobs can be executed manually as desired or scheduled to execute at designated times. For example, +You can execute jobs manually, or schedule them to execute at designated times. For example, you could schedule a job to run during hours when the office is closed and network traffic is low. Windows uses the Schedule Service Account to access the task folders when launching scheduled tasks. -Schedule Service Accounts are configured at the global level, and this account can be used to +Configure Schedule Service Accounts at the global level. Use this account to schedule jobs in the Schedule Wizard. See the [Schedules](/docs/accessanalyzer/12.0/admin/schedule/overview.md) topic for additional information. :::warning -On Windows 2016 servers, the Schedule Service Account cannot be signed into an active -session when the time comes for a scheduled task to start. Windows blocks the starting or running of -scheduled tasks using an account that is logged into the server. +On Windows 2016 servers, you can't sign the Schedule Service Account into an active +session when the time comes for a scheduled task to start. Windows blocks scheduled tasks from +starting or running when they use an account that's logged in to the server. ::: **Password Storage Options** -The password for the credential provided can be stored in the Access Analyzer application or the +You can store the password for the provided credential in the Access Analyzer application or the Access Analyzer Vault. Choosing between the Access Analyzer application and Access Analyzer Vault is a global setting @@ -55,16 +55,16 @@ least the following to meet Least Privileged specifications: - Write Attributes - Write Extended Attributes -- To configure Least Privilege Model Schedule Service Accounts when Role Based Access is enabled, +- To configure Least Privilege Model Schedule Service Accounts when you enable Role Based Access, see the [Role Based Access](/docs/accessanalyzer/12.0/admin/settings/access/rolebased/overview.md) topic for additional information - If using Windows authentication for the Storage Profile, the Schedule Service Account must have a sufficient level of rights to connect to and interact with the Access Analyzer database. See the [Storage](/docs/accessanalyzer/12.0/admin/settings/storage/overview.md) topic for additional information. The **Cancel** and **Save** buttons are in the lower-right corner of the Schedule view. These -buttons become enabled when modifications are made to the Schedule global settings. Whenever changes -are made at the global level, click **Save** and then **OK** to confirm the changes. Otherwise, -click **Cancel** if no changes were intended. +buttons become enabled when you modify the Schedule global settings. Whenever you make changes +at the global level, click **Save** and then **OK** to confirm the changes. Otherwise, +click **Cancel** if you didn't intend to make changes. The Access Analyzer vault provides enhanced security through enhanced encryption to various credentials stored by the Access Analyzer application. See the [Vault](/docs/accessanalyzer/12.0/admin/settings/application/vault.md) topic @@ -72,7 +72,7 @@ for additional information. ## Schedule Service Account Types -There are two types of accounts that can be used to configure the Schedule Service Account. +Two types of accounts are available for the Schedule Service Account. ![serviceaccounttypes](/images/accessanalyzer/12.0/admin/settings/serviceaccounttypes.webp) @@ -83,7 +83,7 @@ Use one of the following options for the Schedule Service Account: - Credentials must have privileges sufficient for scheduling tasks on the Access Analyzer Console server. If not, scheduled tasks fail to start. - - This option cannot be edited or deleted + - You can't edit or delete this option - User-supplied credentials – Provide credentials for a specific account with sufficient rights to schedule tasks on the Access Analyzer Console server @@ -92,20 +92,16 @@ Use one of the following options for the Schedule Service Account: - A local Windows account is a specific account and not the default local system account :::tip -Remember, the Schedule Service Account cannot be signed into an active session on the Access -Analyzer Console server when the time comes for a scheduled task to start when it has a Windows 2016 -operating system. +Remember, on an Access Analyzer Console server running Windows 2016, you can't sign the Schedule +Service Account into an active session when the time comes for a scheduled task to start. ::: ## Create a Schedule Service Account -Follow the steps to create a Schedule Service Account. - :::tip -Remember, the Schedule Service Account cannot be signed into an active session on the Access -Analyzer Console server when the time comes for a scheduled task to start when it has a Windows 2016 -operating system. +Remember, on an Access Analyzer Console server running Windows 2016, you can't sign the Schedule +Service Account into an active session when the time comes for a scheduled task to start. ::: @@ -130,12 +126,12 @@ types are: - Application – Uses Access Analyzer’s configured Profile Security setting as selected at the **Settings** > **Application** node - Managed Service Account – Use previously configured MSA and gMSAs for authentication. The - password fields are not applicable when this option is selected. See the + password fields aren't applicable when you select this option. See the [Group Managed Service Accounts (gMSA) Configuration](/docs/accessanalyzer/12.0/admin/settings/connection/gmsa.md) topic for additional information. - - Password – Type the password - - Confirm – Re-type the password + - Password – Enter the password + - Confirm – Re-enter the password - Local Account – Use this option to specify a local account for the Access Analyzer Console server @@ -145,43 +141,43 @@ types are: - Application – Uses Access Analyzer’s configured Profile Security setting as selected at the **Settings** > **Application** node - - Password – Type the password - - Confirm – Re-type the password + - Password – Enter the password + - Confirm – Re-enter the password -**Step 3 –** Click **OK** and the credentials are verified. If there are no problems with the +**Step 3 –** Click **OK**. Access Analyzer verifies the credentials. If there are no problems with the provided credentials, the User Credentials window closes. Otherwise, one of the following error messages might appear: -- Passwords Do Not Match Error +- Passwords Don't Match Error - ![Passwords Do Not Match Error](/images/accessanalyzer/12.0/admin/settings/passwordsdontmatch.webp) + ![Passwords Don't Match Error](/images/accessanalyzer/12.0/admin/settings/passwordsdontmatch.webp) - - This error indicates the two password entries do not match. Click **OK** and reenter the + - This error indicates the two password entries don't match. Click **OK** and reenter the passwords. - Bad User Name or Password Error ![Bad User Name or Password Error](/images/accessanalyzer/12.0/admin/settings/incorrectlogondetails.webp) - - This error indicates either the user account does not exist or the username and password do + - This error indicates either the user account doesn't exist or the username and password do not match. Click **OK** and reenter the information. - Insufficient Rights Error ![Insufficient Rights Error](/images/accessanalyzer/12.0/admin/settings/insufficientrights.webp) - - This error indicates the account supplied does not have sufficient rights to create and run + - This error indicates the account supplied doesn't have sufficient rights to create and run scheduled tasks. Click **OK** and provide credentials with sufficient rights. - GPO Network Security Error ![GPO Network Security Error](/images/accessanalyzer/12.0/admin/settings/gponetworksecurity.webp) - - This error indicates that the GPO Network Security settings are configured to not allow - storage of passwords and credentials for network authentication. Click OK. Disable the + - This error indicates that the GPO Network Security settings block storage of passwords and + credentials for network authentication. Click OK. Disable the domain’s GPO Network Security settings or exempt the Access Analyzer Server from GPO. - This error will also appear when trying to schedule a task using the domain’s Schedule Service - Account where GPO Network Security is set to not allow storage of passwords and credentials + Account where the GPO Network Security setting blocks storage of passwords and credentials for network authentication **Step 4 –** The credential information appears in the User Credentials table. Click **Save** and @@ -192,33 +188,28 @@ Access Analyzer can now schedule tasks with this Scheduled Service Account. ## Edit a Schedule Service Account -Follow the steps to edit a Schedule Service Account credentials. - :::tip -Remember, the Schedule Service Account cannot be signed into an active session on the Access -Analyzer Console server when the time comes for a scheduled task to start when it has a Windows 2016 -operating system. +Remember, on an Access Analyzer Console server running Windows 2016, you can't sign the Schedule +Service Account into an active session when the time comes for a scheduled task to start. ::: ![Edit option in the Schedule view](/images/accessanalyzer/12.0/admin/settings/edit.webp) -**Step 1 –** Select a credential from the User Credentials list and click on **Edit**. The User +**Step 1 –** Select a credential from the User Credentials list and click **Edit**. The User Credentials window opens. **Step 2 –** Modify the credential information as needed. See Step 2 of the [Create a Schedule Service Account](#create-a-schedule-service-account) topic for additional information. -**Step 3 –** Click **OK** and the credentials will be verified. If there are no problems with the +**Step 3 –** Click **OK**. Access Analyzer verifies the credentials. If there are no problems with the provided credentials, the User Credentials window closes. Access Analyzer can now schedule tasks with this Scheduled Service Account. ## Delete a Schedule Service Account -Follow the steps to delete a Schedule Service Account. - ![Delete option in the Schedule view](/images/accessanalyzer/12.0/admin/settings/delete.webp) **Step 1 –** Select the credential from the User Credentials list and click **Delete**. The Delete @@ -232,6 +223,6 @@ Credentials confirmation window appears. Account. Click **Save** and then **OK** to confirm the changes. To ensure these changes take effect, exit and restart the Access Analyzer application. -If all Schedule Service Accounts are removed and only the local System account remains, Access -Analyzer cannot create or run scheduled tasks unless the local system account has adequate +If you remove all Schedule Service Accounts and only the local System account remains, Access +Analyzer can't create or run scheduled tasks unless the local system account has adequate permissions. diff --git a/docs/accessanalyzer/12.0/admin/settings/sensitivedata/criteria.md b/docs/accessanalyzer/12.0/admin/settings/sensitivedata/criteria.md index e520fb1793..74f7117164 100644 --- a/docs/accessanalyzer/12.0/admin/settings/sensitivedata/criteria.md +++ b/docs/accessanalyzer/12.0/admin/settings/sensitivedata/criteria.md @@ -13,23 +13,22 @@ jobs using the Criteria Tab. The options on the Criteria Tab are: -- Add – Opens the Select Criteria window to add search criteria that will be inherited by Sensitive - Data scan jobs. See the [Select Criteria Window](#select-criteria-window) topic for additional +- Add – Opens the Select Criteria window to add search criteria that Sensitive Data scan jobs + inherit. See the [Select Criteria Window](#select-criteria-window) topic for additional information. -- Remove – Removes the selected criteria from being inherited by Sensitive Data scan jobs +- Remove – Removes the selected criteria, so Sensitive Data scan jobs no longer inherit them - Launch Editor – Opens the Sensitive Data Criteria Editor. See the [Sensitive Data Criteria Editor](/docs/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/overview.md) topic for additional information. - Search selected criteria – Filter the criteria listed in the Criteria tab The **Cancel** and **Save** buttons are in the lower-right corner of the Sensitive Data view. These -buttons become enabled when modifications are made to the Sensitive Data global settings. Whenever -changes are made at the global level, click **Save** and then **OK** to confirm the changes. -Otherwise, click **Cancel** if no changes were intended. +buttons become enabled when you modify the Sensitive Data global settings. Whenever you make changes at the global level, click **Save** and then **OK** to confirm the changes. +Otherwise, click **Cancel** if you didn't intend to make changes. ## Select Criteria Window -Follow the steps to add Search Criteria for Sensitive Data scan jobs. +Add Search Criteria for Sensitive Data scan jobs: ![Add criteria](/images/accessanalyzer/12.0/admin/settings/sensitivedata/addcriteria.webp) @@ -37,13 +36,13 @@ Follow the steps to add Search Criteria for Sensitive Data scan jobs. ![Select Criteria window](/images/accessanalyzer/12.0/admin/settings/sensitivedata/selectcriteria.webp) -**Step 2 –** Select the checkbox to select the criteria. Use the **Search Criteria** text field to -filter the list using keywords or expand each category to view and select individual Sensitive Data +**Step 2 –** Select the checkbox for each criterion you want. Use the **Search Criteria** text field +to filter the list by keyword, or expand each category to view and select individual Sensitive Data search criteria. **Step 3 –** Click **OK** to confirm changes. The Select Criteria window closes. **Step 4 –** Click **Save** on the Sensitive Data view to save changes. -The selected Search Criteria are now inherited by Sensitive Data scan jobs that are set to use -global sensitive data criteria settings. +Sensitive Data scan jobs that use global sensitive data criteria settings now inherit the selected +Search Criteria. diff --git a/docs/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/add.md b/docs/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/add.md index eeb1f80544..91bfdf2fe5 100644 --- a/docs/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/add.md +++ b/docs/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/add.md @@ -6,25 +6,23 @@ sidebar_position: 10 # Adding False Positive Exclusion Filters -Follow the steps to add a False Positive Exclusion Filter. - ![Add Filter on False Positives tab](/images/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/addfilter.webp) **Step 1 –** Click **Add Filter** to open the Add False Positive Exclusion Filter window. ![Add False Positive Exclusion Filter window](/images/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/addexclusionfilterwindow.webp) -**Step 2 –** Enter the **File Path** according to the type of format for the repository. +**Step 2 –** Enter the **File Path** using the format required for the repository type. **Step 3 –** Indicate the type of repository by selecting either **File System** or **SharePoint** -from the **Source** drop-down menu. +from the **Source** dropdown menu. -**Step 4 –** Select the required criteria from the list by selecting the relevant checkboxes. You -can use the **Search Criteria** textbox to filter the list by keywords. +**Step 4 –** Select the required criteria from the list by checking the relevant boxes. You +can use the **Search Criteria** textbox to filter the list by keyword. **Step 5 –** Click **OK** to add the filter to the False Criteria list. The Add False Positive Exclusion Filter window closes. **Step 6 –** Click **Save** on the Sensitive Data view to save changes. -The false positive exclusion filter is now applied to Sensitive Data reports. +Access Analyzer now applies the false positive exclusion filter to Sensitive Data reports. diff --git a/docs/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/delete.md b/docs/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/delete.md index 68825cdc8e..1704dd2fc4 100644 --- a/docs/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/delete.md +++ b/docs/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/delete.md @@ -6,7 +6,7 @@ sidebar_position: 30 # Deleting False Positive Exclusion Filters -Follow the steps to delete a False Positive Exclusion Filter. +To delete a False Positive Exclusion Filter: ![Delete Filter on False Positives tab](/images/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/deletefilter.webp) @@ -14,4 +14,4 @@ Follow the steps to delete a False Positive Exclusion Filter. **Step 2 –** Click **Save** on the Sensitive Data view to save changes. -The false positive exclusion filter has been successfully deleted. +Access Analyzer deletes the false positive exclusion filter. diff --git a/docs/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/edit.md b/docs/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/edit.md index b6caf7a1da..b6d1a8ed4f 100644 --- a/docs/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/edit.md +++ b/docs/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/edit.md @@ -6,8 +6,6 @@ sidebar_position: 20 # Editing False Positive Exclusion Filters -Follow the steps to edit a False Positive Exclusion Filter. - ![Edit Filter on False Positives tab](/images/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/editfilter.webp) **Step 1 –** Click **Edit Filter** to open the Edit False Positive Exclusion Filter window. @@ -21,4 +19,4 @@ closes. **Step 4 –** Click **Save** on the Sensitive Data view to save changes. -The false positive exclusion filter has been successfully edited. +Access Analyzer updates the false positive exclusion filter. diff --git a/docs/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/export.md b/docs/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/export.md index 8bdaf0abfc..ac761ca75f 100644 --- a/docs/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/export.md +++ b/docs/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/export.md @@ -6,7 +6,7 @@ sidebar_position: 50 # Exporting False Positive Exclusion Filters -Follow the steps to export selected False Positive Exclusion Filters into a TXT file. +Export selected False Positive Exclusion Filters into a TXT file. ![Export on False Positives tab](/images/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/exportfilter.webp) @@ -18,4 +18,4 @@ Explorer opens. **Step 2 –** Enter a File name for the TXT file that the exported false positive exclusion filters will be contained in. Click **Save**. -The False Positive Exclusion Filters are now exported. +Access Analyzer exports the False Positive Exclusion Filters. diff --git a/docs/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/import.md b/docs/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/import.md index 17f8b147f9..1eccd8b36c 100644 --- a/docs/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/import.md +++ b/docs/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/import.md @@ -10,7 +10,7 @@ Create an import (TXT) file containing a list of file paths for the files to be Sensitive Data reports. The text file should have one file path per row. The import file needs to be scoped to a single solution and a criteria set. -Follow the steps to import a list of False Positive Exclusion Filter. +Import a list of False Positive Exclusion Filters: ![Import on False Positives tab](/images/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/importfilter.webp) @@ -19,12 +19,12 @@ window. ![Select False Positive Exclusion Filter file to import window](/images/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/importfileexplorer.webp) -**Step 2 –** Navigate to the file that will be imported. Select the file and click **Open**. The +**Step 2 –** Navigate to the file to import. Select the file and click **Open**. The Configure Imported False Positive Exclusion Filters window opens. ![Configure Imported False Positive Exclusion Filters window](/images/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/configureexclusionfilterwindow.webp) -**Step 3 –** Select the repository type from the **Source** drop-down menu. +**Step 3 –** Select the repository type from the **Source** dropdown menu. **Step 4 –** Select the required criteria from the list. You can use the **Search Criteria** textbox to filter the list by keywords. @@ -34,6 +34,7 @@ Filters window closes. **Step 6 –** Click **Save** on the Sensitive Data view to save changes. -The imported list of False Positive Exclusion Filters are now applied to Sensitive Data reports. If -all of the files in the import were not meant to have the same Source and Criteria set, see the +Access Analyzer now applies the imported list of False Positive Exclusion Filters to Sensitive Data +reports. If +all of the files in the import weren't meant to have the same Source and Criteria set, see the [Editing False Positive Exclusion Filters](/docs/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/edit.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/overview.md b/docs/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/overview.md index 77c7faaf34..3936fbb6dc 100644 --- a/docs/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/overview.md +++ b/docs/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/overview.md @@ -6,9 +6,9 @@ sidebar_position: 20 # False Positives Tab -Configure False Positive exclusion filters using the options in the False Positives tab. False -Positives Filters listed here as False Positives results in the corresponding matches being removed -from Access Analyzer and Access Information Center reports. +Configure False Positive exclusion filters using the options on the False Positives tab. Filters +listed here remove the corresponding matches from Access Analyzer and Access Information Center +reports. ![False Positives tab](/images/accessanalyzer/12.0/admin/settings/sensitivedata/exclusions/falsepositivestab.webp) @@ -40,6 +40,5 @@ Filters: - Criteria – Sensitive Data criteria where the exclusion filter is applied The **Cancel** and **Save** buttons are in the lower-right corner of the Sensitive Data view. These -buttons become enabled when modifications are made to the Sensitive Data global settings. Whenever -changes are made at the global level, click **Save** and then **OK** to confirm the changes. -Otherwise, click **Cancel** if no changes were intended. +buttons become enabled when you modify the Sensitive Data global settings. Whenever you make changes at the global level, click **Save** and then **OK** to confirm the changes. +Otherwise, click **Cancel** if you didn't intend to make changes. diff --git a/docs/accessanalyzer/12.0/admin/settings/sensitivedata/overview.md b/docs/accessanalyzer/12.0/admin/settings/sensitivedata/overview.md index d7d4af8e1e..c92756cb50 100644 --- a/docs/accessanalyzer/12.0/admin/settings/sensitivedata/overview.md +++ b/docs/accessanalyzer/12.0/admin/settings/sensitivedata/overview.md @@ -12,7 +12,7 @@ positive exclusion filters. These settings require Sensitive Data Discovery to b information. :::note -Sensitive data exclusion filters can only be applied to the +You can only apply sensitive data exclusion filters to the [File System Solution](/docs/accessanalyzer/12.0/solutions/filesystem/overview.md) and the [SharePoint Solution](/docs/accessanalyzer/12.0/solutions/sharepoint/overview.md). ::: diff --git a/docs/accessanalyzer/12.0/admin/settings/servicenow.md b/docs/accessanalyzer/12.0/admin/settings/servicenow.md index e9322d9ff6..79b4e12806 100644 --- a/docs/accessanalyzer/12.0/admin/settings/servicenow.md +++ b/docs/accessanalyzer/12.0/admin/settings/servicenow.md @@ -7,8 +7,8 @@ sidebar_position: 120 # ServiceNow The ServiceNow® node is for configuring the settings needed to integrate with ServiceNow. These -settings are exclusive to the Access Analyzer integration with ServiceNow and are used by the -ServiceNow Action Module. See the [ServiceNow Action Module](/docs/accessanalyzer/12.0/admin/action/servicenow/overview.md) topic +settings are exclusive to the Access Analyzer integration with ServiceNow, and the ServiceNow +Action Module uses them. See the [ServiceNow Action Module](/docs/accessanalyzer/12.0/admin/action/servicenow/overview.md) topic for additional information. ![ServiceNow node](/images/accessanalyzer/12.0/admin/settings/servicenow.webp) @@ -16,22 +16,19 @@ for additional information. Provide ServiceNow authentication information to your ServiceNow instance. - Instance – The ServiceNow instance, for example `example.service-now.com` -- User Name and Password – The **Settings** > **ServiceNow** node at the global level can be - configured with a credential provisioned to create incidents as Callers in the **Assigned to** +- User Name and Password – You can configure the **Settings** > **ServiceNow** node at the global + level with a credential provisioned to create incidents as Callers in the **Assigned to** field, and any other ServiceNow incident field that references the **sys_user** table. The **Cancel** and **Save** buttons are in the lower-right corner of the ServiceNow view. These -buttons become enabled when modifications are made to the ServiceNow global settings. Whenever -changes are made at the global level, click **Save** and then **OK** to confirm the changes. -Otherwise, click **Cancel** if no changes were intended. +buttons become enabled when you modify the ServiceNow global settings. Whenever you make changes at the global level, click **Save** and then **OK** to confirm the changes. +Otherwise, click **Cancel** if you didn't intend to make changes. ## Update ServiceNow Authentication Credentials -Follow the steps to update the ServiceNow authentication credentials. - **Step 1 –** In the ServiceNow Authentication section, enter a new **Password** for the user account. **Step 2 –** Click **Save**. -The credentials have been updated for ServiceNow authentication. +Access Analyzer updates the credentials for ServiceNow authentication. diff --git a/docs/accessanalyzer/12.0/admin/settings/storage/add.md b/docs/accessanalyzer/12.0/admin/settings/storage/add.md index 874b25c73a..06be21957b 100644 --- a/docs/accessanalyzer/12.0/admin/settings/storage/add.md +++ b/docs/accessanalyzer/12.0/admin/settings/storage/add.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Add a Storage Profile -Follow the steps to create a Storage Profile. +Create a Storage Profile: ![Add Storage profile option](/images/accessanalyzer/12.0/admin/settings/storage/addprofile.webp) @@ -19,8 +19,8 @@ Profile name to a unique and descriptive name. ![Server Name field](/images/accessanalyzer/12.0/admin/settings/storage/addprofileservername.webp) -**Step 3 –** Type the SQL **Server name** in the textbox provided. This can be a NetBIOS name, a -fully qualified domain name, or an IP Address. If the SQL Server specified is configured to use a +**Step 3 –** Enter the SQL **Server name** in the textbox provided. This can be a NetBIOS name, a +fully qualified domain name, or an IP Address. If the specified SQL Server uses a named instance, provide the **Instance name** in the next textbox. ![Command timeout field](/images/accessanalyzer/12.0/admin/settings/storage/addprofiletimeout.webp) @@ -45,17 +45,17 @@ for additional information. |:-------------------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------------------------------------------------------------------:| | *Good Connection Test* | *Bad Connection Test* | -**Step 6 –** It is recommended to test the credentials provided at this point. The radio button for -**Use existing database** should be selected by default. Test the SQL Server connection by clicking -the drop-down arrow for an existing database. If the connection is established, a listing of -databases appears. If the connection cannot be established, an error warning displays. +**Step 6 –** Test the credentials you provided at this point. By default, Access Analyzer selects the +radio button for **Use existing database**. Test the SQL Server connection by clicking +the dropdown arrow for an existing database. If Access Analyzer establishes the connection, a listing +of databases appears. If Access Analyzer can't establish the connection, an error warning displays. ![Database options](/images/accessanalyzer/12.0/admin/settings/storage/addprofiledatabase.webp) **Step 7 –** Set the database through one of the following options: - Use existing database – Click this radio button and select a database from this list provided in - the drop-down menu + the dropdown menu - Create new database – Click this radio button and provide a unique, descriptive name in the textbox @@ -66,8 +66,8 @@ the appropriate permissions and lists any that are missing. If no permissions ar message appears in the Connection report window. When there is a `Successful connection test`, click **Close**. -**Step 9 –** If **Create new database** was selected, the new database now exists. If **Use existing -database** was selected, the Storage Profile is now linked to the database. Click **Save** and then +**Step 9 –** If you selected **Create new database**, the new database now exists. If you selected +**Use existing database**, the Storage Profile is now linked to the database. Click **Save** and then **OK** to complete the creation of the new Storage Profile. -The new Storage Profile is available to be used by Access Analyzer. +Access Analyzer can now use the new Storage Profile. diff --git a/docs/accessanalyzer/12.0/admin/settings/storage/default.md b/docs/accessanalyzer/12.0/admin/settings/storage/default.md index 0a82c29851..2cfbbc8f02 100644 --- a/docs/accessanalyzer/12.0/admin/settings/storage/default.md +++ b/docs/accessanalyzer/12.0/admin/settings/storage/default.md @@ -6,9 +6,9 @@ sidebar_position: 30 # Set a Default Storage Profile -While multiple Storage Profiles can exist, only one profile can be set as the default. A green -checkmark next to the profile name indicates the default Storage Profile. Follow the steps to change -the default Storage Profile at the global level. +While multiple Storage Profiles can exist, you can set only one profile as the default. A green +checkmark next to the profile name indicates the default Storage Profile. Change the default Storage +Profile at the global level: ![Set as Default option on Storage page](/images/accessanalyzer/12.0/admin/settings/storage/default.webp) @@ -17,27 +17,28 @@ storage profile window opens. ![Change storage profile window](/images/accessanalyzer/12.0/admin/settings/storage/changestorageprofile.webp) -**Step 2 –** There are three options for host management data migration. Select the desired option, -choose whether or not to apply the secondary option, and click **OK**. +**Step 2 –** There are three options for host management data migration. Select the option you want, +choose whether to apply the secondary option, and click **OK**. - Merge your host management data with data in the destination table (Recommended) – This option keeps existing hosts and host discovery tasks in the destination and updates the tasks based on the information found in the source database - - Use destination value on conflict – If selected, any conflicting information between the - destination table and the source database is resolved in favor of the destination table + - Use destination value on conflict – If selected, this option resolves any conflicting + information between the destination table and the source database in favor of the destination + table - Overwrite data in the destination table – This option replaces existing hosts and host discovery tasks with ones found in the source database - - Also overwrite shared host inventory data – If selected, host inventory data is also replaced - with data found in the source database + - Also overwrite shared host inventory data – If selected, this option also replaces host + inventory data with data found in the source database -- Don’t copy your host management data to destination table – This option does not copy, update, or +- Don’t copy your host management data to destination table – This option doesn't copy, update, or overwrite information between databases - - Clear data in destination table – If selected, all host management data in the destination - table is deleted + - Clear data in destination table – If selected, this option deletes all host management data in + the destination table ![Change storage profile window when transfer is complete](/images/accessanalyzer/12.0/admin/settings/storage/changestorageprofilefinish.webp) @@ -46,11 +47,11 @@ choose whether or not to apply the secondary option, and click **OK**. ![Storage page with new default storage profile](/images/accessanalyzer/12.0/admin/settings/storage/defaultsave.webp) **Step 4 –** A blue arrow now points to the new default Storage Profile. However, the arrow is also -an indication that the new default is not fully recognized by Access Analyzer. Click **Save** and +an indication that Access Analyzer doesn't yet fully recognize the new default. Click **Save** and then **OK** to confirm the changes. **Step 5 –** Finally, to ensure these changes take effect, exit the Access Analyzer application and relaunch it. -The blue arrow is replaced by the green checkmark, indicating the new default Storage Profile is -recognized. +The green checkmark replaces the blue arrow, indicating that Access Analyzer now recognizes the new +default Storage Profile. diff --git a/docs/accessanalyzer/12.0/admin/settings/storage/delete.md b/docs/accessanalyzer/12.0/admin/settings/storage/delete.md index 62517f0759..2bc0ae4828 100644 --- a/docs/accessanalyzer/12.0/admin/settings/storage/delete.md +++ b/docs/accessanalyzer/12.0/admin/settings/storage/delete.md @@ -6,17 +6,17 @@ sidebar_position: 40 # Delete a Storage Profile -Follow the steps to delete a Storage Profile. +To delete a Storage Profile: :::note -This procedure does not delete databases from the SQL Server. It only removes the selected +This procedure doesn't delete databases from the SQL Server. It only removes the selected Storage Profile from this Access Analyzer Console. ::: ![Delete Storage Profile option](/images/accessanalyzer/12.0/admin/settings/storage/delete.webp) -**Step 1 –** Select the Storage Profile to be removed, and click **Delete**. +**Step 1 –** Select the Storage Profile you want to delete, and click **Delete**. ![Confirm delete selected profile dialog](/images/accessanalyzer/12.0/admin/settings/storage/deleteconfirm.webp) @@ -25,4 +25,4 @@ Storage Profile from this Access Analyzer Console. **Step 3 –** The profile disappears from the Storage Profiles list. Click **Save** and then **OK** to confirm the changes. -The Storage Profile has now been deleted. +Access Analyzer deletes the Storage Profile. diff --git a/docs/accessanalyzer/12.0/admin/settings/storage/overview.md b/docs/accessanalyzer/12.0/admin/settings/storage/overview.md index fa6b500da7..fd0d5c6fe0 100644 --- a/docs/accessanalyzer/12.0/admin/settings/storage/overview.md +++ b/docs/accessanalyzer/12.0/admin/settings/storage/overview.md @@ -40,7 +40,7 @@ Each Storage Profile consists of the following parts: ::: - - Windows authentication – Leverages the account used to run the Access Analyzer Console + - Windows authentication – Uses the account used to run the Access Analyzer Console :::note This option affects the credentials used for Schedule Service Accounts. See the @@ -48,16 +48,16 @@ Each Storage Profile consists of the following parts: ::: - - SQL Server authentication – Leverages the account provided in the **User name** and + - SQL Server authentication – Uses the account provided in the **User name** and **Password** textboxes - Use existing password – Use the password configured for the Storage Profile account - Specify a new password below – Enter a new password for the selected Storage Profile account - Database name – Name of the Access Analyzer database to use in this storage profile - - Use existing database – Drop-down menu provides a list of databases on the named SQL Server, + - Use existing database – dropdown menu provides a list of databases on the named SQL Server, provided the connection information supplied is correct. If the menu is empty, then a - connection to the SQL Server was not established. + connection to the SQL Server wasn't established. - Create new database – Access Analyzer automatically creates a new database using the name provided in the textbox. This value should be a unique, descriptive name. @@ -78,9 +78,9 @@ A green checkmark in the Storage Profiles list indicates the default Storage Pro The **Cancel** and **Save** buttons are in the lower-right corner of the Storage view. These buttons -become enabled when modifications are made to the Storage global setting. Whenever changes are made +become enabled when you modify the Storage global settings. Whenever you make changes at the global level, click **Save** and then **OK** to confirm the changes. Otherwise, click -**Cancel** if no changes were intended. +**Cancel** if you didn't intend to make changes. The vault provides enhanced security through enhanced encryption to various credentials stored by the Access Analyzer application. See the [Vault](/docs/accessanalyzer/12.0/admin/settings/application/vault.md) topic for additional diff --git a/docs/accessanalyzer/12.0/admin/settings/storage/updateauth.md b/docs/accessanalyzer/12.0/admin/settings/storage/updateauth.md index 11f161406c..31fe705594 100644 --- a/docs/accessanalyzer/12.0/admin/settings/storage/updateauth.md +++ b/docs/accessanalyzer/12.0/admin/settings/storage/updateauth.md @@ -6,9 +6,6 @@ sidebar_position: 20 # Update Authentication Credentials in a Storage Profile -Follow the steps to update authentication credentials for a Storage Profile in the Access Analyzer -Console. - **Step 1 –** Navigate to the **Settings** > **Storage** page. **Step 2 –** Locate and select a **Storage Profile** to update. @@ -21,4 +18,4 @@ Console. **Step 5 –** Click **Apply**. -A new password has been added to a Storage profile. +Access Analyzer adds the new password to the Storage Profile. diff --git a/docs/accessanalyzer/12.0/cdsa/job.md b/docs/accessanalyzer/12.0/cdsa/job.md index 07ad440294..addcb73355 100644 --- a/docs/accessanalyzer/12.0/cdsa/job.md +++ b/docs/accessanalyzer/12.0/cdsa/job.md @@ -11,7 +11,7 @@ The CDSA Job is available through the Instant Job Library under the CDSA library this instant job to the Jobs tree. When installing the job, select **Local host** on the Host pages of the Instant Job Wizard. -Ensure the supporting solutions have successfully collected and analyzed data prior to running this +Ensure the supporting solutions have successfully collected and analyzed data before running this job. See the [Presentation Dependencies](/docs/accessanalyzer/12.0/cdsa/presentation.md) topic for alignment between presentation slides and jobs that supply the data points. @@ -29,12 +29,12 @@ The CDSA job generates three PowerPoint files: self-review as a PDF file :::warning -Do not send any these presentations to a customer in PowerPoint format. +Don't send any these presentations to a customer in PowerPoint format. ::: -The printable assets can be converted to PDFs or printed booklet style at a professional print shop -(suggested) if desired. +You can convert the printable assets to PDFs, or have them printed booklet style at a professional +print shop (suggested), if desired. These presentations are located within the job’s folder in the Access Analyzer installation directory, which varies according to the location of the job within the Jobs tree. Navigate to this @@ -53,7 +53,7 @@ are two presentation options for the live slide show: - The **ePHI Security Assessment** slide show contains the ending slides with select summary slides from the Classic slide show and is applicable to the healthcare industry -Use the Custom Slide Show drop-down menu on the Slide Show ribbon in PowerPoint to select the +Use the Custom Slide Show dropdown menu on the Slide Show ribbon in PowerPoint to select the appropriate presentation. :::note @@ -73,7 +73,7 @@ Both of the printable assets have two customized options for converting to a PDF - ePHI Security Assessment – Contains the ending slides with select summary slides from the Classic slide show and is applicable to the healthcare industry -Follow the steps to create the appropriate custom PDF. +To create the appropriate custom PDF: **Step 1 –** Use the **Save As** option. @@ -81,12 +81,12 @@ Follow the steps to create the appropriate custom PDF. **Step 3 –** Click **Options** and change the Range to **Custom show**. -**Step 4 –** By default, this is set to the **CDSA Classic** show. If needed, change it to the +**Step 4 –** By default, the file uses the **CDSA Classic** show. If needed, change it to the **ePHI Security Assessment** show. **Step 5 –** Click **OK** to confirm the option, and then click **Save** to generate the PDF. -The presentation is converted to a PDF with only the applicable slides included. +PowerPoint converts the presentation to a PDF with only the applicable slides included. :::note Slide 16 is hidden by default as same information is available on Slides 17-19. diff --git a/docs/accessanalyzer/12.0/cdsa/overview.md b/docs/accessanalyzer/12.0/cdsa/overview.md index 1fb89ff57c..b794fb2263 100644 --- a/docs/accessanalyzer/12.0/cdsa/overview.md +++ b/docs/accessanalyzer/12.0/cdsa/overview.md @@ -15,7 +15,7 @@ The CDSA job depends upon several Access Analyzer solutions for data collection. ## Supporting Solutions -At a minimum the following solutions need to run prior to the CDSA job to provide the data used to +At a minimum the following solutions need to run before the CDSA job to provide the data used to generate the CDSA presentations: - .Active Directory Inventory Solution diff --git a/docs/accessanalyzer/12.0/cdsa/presentation.md b/docs/accessanalyzer/12.0/cdsa/presentation.md index 795a74482e..ab511aed89 100644 --- a/docs/accessanalyzer/12.0/cdsa/presentation.md +++ b/docs/accessanalyzer/12.0/cdsa/presentation.md @@ -6,10 +6,10 @@ sidebar_position: 20 # Presentation Dependencies -In the following subsections, each slide is aligned to the jobs that supply its data. The slide +The following subsections align each slide to the jobs that supply its data. The slide number is specific to the **Netwrix_CDSA_Presentation.pptx** file, as there are slight various in page numbering with the files designed to be saved as PDFs. Many jobs contribute to multiple slides, -so jobs are highlighted in bold text the first time they are listed. +so this topic highlights jobs in bold text the first time they appear. ## Executive Summary Slide @@ -416,8 +416,8 @@ Data is also supplied by the following jobs when they have been executed: ## Additional Findings (FS, AD, Windows OS) Slide -Slide 17 in the **Netwrix_CDSA_Presentation.pptx** file is hidden by default. It is recommended to -use Slides 18-20 instead, even when the primary jobs are the only ones supplying data. Slide 17 is +Slide 17 in the **Netwrix_CDSA_Presentation.pptx** file is hidden by default. Use Slides 18-20 +instead, even when the primary jobs are the only ones supplying data. Slide 17 is an alternative to slides 18-20. It has the following primary job dependencies: - .Active Directory Inventory diff --git a/docs/accessanalyzer/12.0/gettingstarted.md b/docs/accessanalyzer/12.0/gettingstarted.md index f37693f394..31b86db720 100644 --- a/docs/accessanalyzer/12.0/gettingstarted.md +++ b/docs/accessanalyzer/12.0/gettingstarted.md @@ -6,14 +6,14 @@ sidebar_position: 2 # Getting Started -Once Access Analyzer is installed, the following workflow will quickly enable users to begin +Once Access Analyzer is installed, use the following workflow to quickly begin auditing the organization’s IT infrastructure. See the [Navigating the Console](/docs/accessanalyzer/12.0/admin/navigate/overview.md) topic for additional information and data grid functionality. ## Initial Configuration During First Launch -During the initial Access Analyzer Configuration Wizard, users are walked through configuring +The initial Access Analyzer Configuration Wizard walks you through configuring several key global settings: - Storage @@ -22,25 +22,25 @@ several key global settings: - Requires credential on the SQL® Server database which is used to create and modify the Access Analyzer database - Option to either create a new database or point to an existing database - - If using Windows Authentication, the Schedule node must be configured also + - If using Windows Authentication, you must also configure the Schedule node - See the [Storage](/docs/accessanalyzer/12.0/admin/settings/storage/overview.md) topic for additional information - Schedule - - Only appears if the Storage Profile is configured to use Windows Authentication - - If the Storage Profile is configured to use SQL Authentication, the setting is configured + - Only appears if you configure the Storage Profile to use Windows Authentication + - If you configure the Storage Profile to use SQL Authentication, you configure the setting later - See the [Schedule](/docs/accessanalyzer/12.0/admin/settings/schedule.md) topic for additional information - Instant Job - - Install the pre-configured solutions for which the organization is licensed + - Install the pre-configured solutions the organization has a license for - See the [Instant Job Wizard](/docs/accessanalyzer/12.0/admin/jobs/instantjobs/overview.md) topic for additional information ## Global Settings Configured -The global Settings have an overall impact on the running of Access Analyzer jobs. They are managed +The global Settings have an overall impact on the running of Access Analyzer jobs. You manage them through the Settings node at the top of the Navigation pane. The following global Settings require configuration from the start: @@ -57,7 +57,7 @@ The other global Settings provide additional options for impacting how Access An privileged application of Access Analyzer and report viewing or the enable the REST API :::note - If Role Based Access is enabled by accident, contact + If you enable Role Based Access by accident, contact [Netwrix Support](https://www.netwrix.com/support.html) for assistance in disabling it. ::: @@ -67,7 +67,7 @@ The other global Settings provide additional options for impacting how Access An - [Exchange](/docs/accessanalyzer/12.0/admin/settings/exchange.md) – Configure Microsoft® Exchange Server connections :::warning -Do not configure data retention at the global level without ensuring History is +Don't configure data retention at the global level without ensuring History is supported by ALL solutions to be run. ::: @@ -88,23 +88,23 @@ See the [Global Settings](/docs/accessanalyzer/12.0/admin/settings/overview.md) ## Discover Hosts Within the terminology of Access Analyzer, hosts are the machines being targeted during data -collection. Hosts can be discovered or manually introduced to Access Analyzer. Known hosts are then -inventoried to populate dynamic host lists. Host discovery is done at the Host Discovery  node. -Hosts are manually introduced at the Host Management node. +collection. You can discover hosts or manually introduce them to Access Analyzer. Access Analyzer +then inventories known hosts to populate dynamic host lists. Perform host discovery at the Host +Discovery node. Manually introduce hosts at the Host Management node. -Host management consists of maintaining up-to-date host inventories and host lists which can be -assigned to job groups or jobs as targeted hosts. See the +Host management consists of maintaining up-to-date host inventories and host lists that you can +assign to job groups or jobs as targeted hosts. See the [Host Management](/docs/accessanalyzer/12.0/admin/hostmanagement/overview.md) topic for additional information. ## Job Workflow -Once the global Settings are configured and hosts have been introduced to Access Analyzer, it is +After you configure the global Settings and introduce hosts to Access Analyzer, it's time to begin auditing. This requires an understanding of the relationship between solutions, job groups, jobs, queries, analysis, actions, and reports. The Access Analyzer job is the fundamental unit. Jobs are responsible for all data collection -queries, analysis tasks, notification tasks, action tasks, and report generation. When Jobs are -designed to work together, they are housed within job groups to control the order of job execution. +queries, analysis tasks, notification tasks, action tasks, and report generation. When jobs are +designed to work together, job groups house them to control the order of job execution. Solutions are pre-configured job groups which have been designed to target specific types of environments to audit for specific data sets, typically the most common types of information desired. diff --git a/docs/accessanalyzer/12.0/index.md b/docs/accessanalyzer/12.0/index.md index 8f757e84f2..36c8f6e79e 100644 --- a/docs/accessanalyzer/12.0/index.md +++ b/docs/accessanalyzer/12.0/index.md @@ -19,7 +19,7 @@ The platform framework contains the following key components: Access Analyzer contains over 40 built-in data collection modules covering both on-premises and cloud-based platforms from Operating Systems to Office 365. Leveraging an agentless architectural -approach, our proprietary AnyData collector provides an easy, wizard-driven interface for +approach, the proprietary AnyData collector provides a wizard-driven interface for configuring the application to collect exactly the data needed, enabling fast, flawless, lightest-weight possible data collection from dozens of data sources. @@ -34,8 +34,8 @@ require a license. The .Active Directory Inventory Solution is designed to provide essential user, group membership, and computer details from the targeted domains to many Access Analyzer built-in solutions. Key -information includes user status, user attributes, and group membership. The collected data is -accessed by other Access Analyzer solutions and the Netwrix Access Information Center for analysis. +information includes user status, user attributes, and group membership. Other Access Analyzer solutions and the Netwrix Access Information Center access the collected data +for analysis. This is a core solution available to all Access Analyzer users. @@ -65,7 +65,7 @@ information. The .NIS Inventory Solution is designed to provide essential user and group membership information from a NIS domain, mapping these principals to Windows-style SIDs. This provides valuable -information to the File Systems Solution when auditing NFS shares. +information to the File Systems Solution for auditing NFS shares. This is a core solution available to all Access Analyzer users. @@ -131,18 +131,18 @@ reports that provide visibility into various aspects of supported databases. - Instance Discovery – The Instance Discovery Solution discovers instances on supported database servers. - MongoDB Solution – The MongoDB Solution automates the process of understanding where MongDB - databases exist and provides an overview of the MongoDB environment in order to answer questions + databases exist and provides an overview of the MongoDB environment to answer questions around data access. With visibility into every corner of MongoDB and the operating system it relies upon, organizations can proactively highlight and prioritize risks to sensitive data. Additionally, organizations can automate manual, time-consuming, and expensive processes - associated with compliance, security, and operations to easily adhere to best practices that keep + associated with compliance, security, and operations to adhere to best practices that keep MongoDB Server safe and operational. - MySQL Solution – The MySQL Solution automates the process of understanding where SQL databases - exist and provides an overview of the MySQL environment in order to answer questions around data + exist and provides an overview of the MySQL environment to answer questions around data access. With visibility into every corner of Microsoft SQL Server and the Windows operating system it relies upon, organizations can proactively highlight and prioritize risks to sensitive data. Additionally, organizations can automate manual, time-consuming, and expensive processes - associated with compliance, security, and operations to easily adhere to best practices that keep + associated with compliance, security, and operations to adhere to best practices that keep SQL Server safe and operational. - Oracle Solution – The Oracle Solution delivers comprehensive permissions, activity, and sensitive data auditing and reporting for Oracle databases. Through the power of Access Analyzer, users can @@ -219,9 +219,8 @@ Sensitive data auditing requires the Sensitive Data Discovery Add-on. ### Unix Solution -The Unix Solution reports on areas of administrative concern for Unix and Linux systems. Attention -is given to users and group details, privileged access rights, and NFS and Samba sharing -configurations. +The Unix Solution reports on areas of administrative concern for Unix and Linux systems, focusing on +users and group details, privileged access rights, and NFS and Samba sharing configurations. See the [Unix Solution](/docs/accessanalyzer/12.0/solutions/unix/overview.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/install/application/database/database.md b/docs/accessanalyzer/12.0/install/application/database/database.md index 633147cb50..d97adb77eb 100644 --- a/docs/accessanalyzer/12.0/install/application/database/database.md +++ b/docs/accessanalyzer/12.0/install/application/database/database.md @@ -6,20 +6,20 @@ sidebar_position: 10 # Access Analyzer Database -The Access Analyzer database is dynamic in nature. There are a handful of required system tables -which are created at installation time or when individual features are used the first time. All -other data tables in the Access Analyzer database are created and bound to individual jobs which are -added to the Access Analyzer Console. As jobs are created and modified, corresponding tables are -created and modified in the database. A job can generate one or more tables. - -The structure and schema of each data table is controlled by the Access Analyzer data collector used -to collect data and write results to the table. There is a one-to-one relationship between a task +The Access Analyzer database is dynamic in nature. Access Analyzer creates a handful of required +system tables at installation time or when you use individual features for the first time. It +creates and binds all other data tables in the Access Analyzer database to individual jobs that you +add to the Access Analyzer Console. As you create and modify jobs, Access Analyzer creates and +modifies corresponding tables in the database. A job can generate one or more tables. + +The Access Analyzer data collector used to collect data and write results to the table controls the +structure and schema of each data table. There is a one-to-one relationship between a task created within a Access Analyzer job and the table to which the task writes results. Creating tasks or adding and removing properties within a task modifies the schema of the table on subsequent execution of the job. Access Analyzer offers users the ability to modify its preconfigured jobs or create custom jobs and -tasks as needed. Therefore, precise schema information for data tables cannot be predicted, +tasks as needed. Therefore, precise schema information for data tables can't be predicted, restricted, or locked down. ## Database Permissions @@ -34,8 +34,8 @@ to the database. ::: -If database owner rights cannot be obtained, the following SQL script can be executed by a database -administrator (DBA) against the Access Analyzer database to grant the necessary permissions to the +If database owner rights can't be obtained, a database +administrator (DBA) can execute the following SQL script against the Access Analyzer database to grant the necessary permissions to the appropriate users (replacing `` and `` with the appropriate values): ```sql @@ -86,16 +86,16 @@ Analyzer. user-configured time frame - Reporting Needs – Anticipated data needed to generate reports -Recommended SQL Server database sizes are provided for specific solutions in the -[Requirements](/docs/accessanalyzer/12.0/requirements/overview.md) topics. These recommendations are based on +The [Requirements](/docs/accessanalyzer/12.0/requirements/overview.md) topics provide recommended +SQL Server database sizes for specific solutions. These recommendations are based on environmental factors, the number of target objects within an environment (users, hosts, mailboxes, -etc.), and the applicable factors listed above for the specific solution. +etc.), and the applicable factors described earlier in this topic for the specific solution. ### Customer Examples of Database Sizing -The overall database size is ultimately governed by an organization’s auditing objectives. The -examples below provide a glimpse into how these objectives combine with the applicable factors above -to impact the Access Analyzer database resource consumption. +An organization’s auditing objectives ultimately govern the overall database size. The +following examples provide a glimpse into how these objectives combine with the applicable factors +described earlier in this topic to impact the Access Analyzer database resource consumption. - Example from an Active Directory Solution Customer - An Active Directory (AD) customer intends to collect AD User/Group/Membership information and @@ -115,9 +115,9 @@ to impact the Access Analyzer database resource consumption. information on file permissions and ages (and possibly, ad hoc, information on file system activity) with an overall plan to identify stale data, consolidate active data on a subset of the organization’s file system infrastructure, and to move that active data to a cloud-based - platform like SharePoint Online. Activity monitoring (FSAC) is to be used ad hoc against open - shares to profile resource ownership and also to validate the “staleness” of certain - resources. The database sizing for a project of this scope could be up to 750 GB for the + platform like SharePoint Online. The customer plans to use Activity monitoring (FSAC) ad hoc + against open shares to profile resource ownership and also to validate the “staleness” of + certain resources. The database sizing for a project of this scope could be up to 750 GB for the database, 240 GB for the transaction log, and 380 GB of TEMPDB space. - Example from an Exchange Solution Customer - An Exchange customer only intends to collect Mail-Flow Metrics for 100,000 Mailboxes from 10 @@ -131,12 +131,12 @@ to impact the Access Analyzer database resource consumption. ## Securing the Access Analyzer Database -The typical database configuration is to have **sysadmin Server Role** assigned to the ID used to +The typical database configuration assigns the **sysadmin Server Role** to the ID used to connect to the SQL instance. It will allow full control over the instance where the Access Analyzer -database resides. This configuration is chosen because Access Analyzer requires some interaction -with the master database in order to install and configure the initial Access Analyzer database. -When it is necessary to secure the Access Analyzer database, the following steps should be followed -to achieve the minimum SQL security levels without breaking core Access Analyzer functionality. +database resides. Use this configuration because Access Analyzer requires some interaction +with the master database to install and configure the initial Access Analyzer database. +The following sections describe how to secure the Access Analyzer database and achieve the minimum +SQL security levels without breaking core Access Analyzer functionality. ### Database Creation & First Level of Security @@ -145,7 +145,7 @@ for the server roles and user mappings. ![SQL Server Management Studio create New Database](/images/accessanalyzer/12.0/install/application/createnewdatabase.webp) -**Step 1 –** Create a new database for use with Access Analyzer. Right-click on the **Databases** +**Step 1 –** Create a new database for use with Access Analyzer. Right-click the **Databases** node and choose **New Database**. ![SQL Server Management Studio New Database window](/images/accessanalyzer/12.0/install/application/newdatabase.webp) @@ -168,8 +168,8 @@ Analyzer database. The available options are Windows authentication and SQL Serv ![SQL Server Management Studio new login with Windows authentication](/images/accessanalyzer/12.0/install/application/loginwindows.webp) -- If **Windows authentication** is desired, then click **Search** and select the desired Windows - account, which has been set up for use with Access Analyzer. +- If **Windows authentication** is desired, then click **Search** and select the Windows + account that's set up for use with Access Analyzer. ![SQL Server Management Studio new login with SQL Server authentication](/images/accessanalyzer/12.0/install/application/loginsql.webp) @@ -177,7 +177,7 @@ Analyzer database. The available options are Windows authentication and SQL Serv Analyzer. :::note -Set the **Default Database** as Access Analyzer (or the desired Access Analyzer database) +Set the **Default Database** as Access Analyzer (or the Access Analyzer database you want) and choose English as the **Default Language**. ::: @@ -212,8 +212,8 @@ This step requires the completion of the Access Analyzer installation. See the ![Connection report window](/images/accessanalyzer/12.0/install/application/connectionreport.webp) -- Click **Apply** and a Connection report window will open. Verify that the connection and test - table drop were performed successfully. +- Click **Apply** and a Connection report window will open. Verify that Access Analyzer performed the + connection and test table drop successfully. - Click **Close** on the Connection report window and then **Save** the new Storage Profile. ![Change storage profile dialog](/images/accessanalyzer/12.0/install/application/changestorageprofile.webp) @@ -225,11 +225,11 @@ appropriate options and then click **OK** to migrate data. ::: -**Step 9 –** Make sure to close and re-open the Access Analyzer Console before continuing to -configure or use Access Analyzer if a new database Storage Profile was chosen as the default. +**Step 9 –** ensure to close and re-open the Access Analyzer Console before continuing to +configure or use Access Analyzer if you chose a new database Storage Profile as the default. -The **blue arrow** signifies the default profile was changed but does not take effect until the -required restart of the Access Analyzer Console. +The **blue arrow** signifies that you changed the default profile, but the change doesn't take +effect until you restart the Access Analyzer Console. See the [Access Analyzer Initial Configuration](/docs/accessanalyzer/12.0/install/application/firstlaunch.md) topic to perform these steps during the initial configuration process after installation. diff --git a/docs/accessanalyzer/12.0/install/application/database/otherlanguages.md b/docs/accessanalyzer/12.0/install/application/database/otherlanguages.md index 0044b4b8b5..07654aba36 100644 --- a/docs/accessanalyzer/12.0/install/application/database/otherlanguages.md +++ b/docs/accessanalyzer/12.0/install/application/database/otherlanguages.md @@ -11,21 +11,21 @@ environment, specifically when the environment uses a non-Latin alphabet. ## Requirements -The following collation requirements need to be met prior to the Access Analyzer installation. +Meet the following collation requirements before installing Access Analyzer. ### Database & Server Collation Settings -The collation settings at the database level must match what is set at the server level. +The collation settings at the database level must match the server-level collation setting. **Symptoms** Common errors that occur are: -- Implicit conversion of VARCHAR value to VARCHAR cannot be performed because the collation of the +- Implicit conversion of VARCHAR value to VARCHAR can't be performed because the collation of the value is unresolved due to a collation conflict. - - Could not find stored procedure `#SA_ImportObject` - - Cannot drop the procedure `#SA_ImportObject`, because it does not exist or lack of permission -- Cannot resolve the collation conflict between **SQL_Latin1_General_CP1_CI_AS** and + - Couldn't find stored procedure `#SA_ImportObject` + - Can't drop the procedure `#SA_ImportObject`, because it doesn't exist or lack of permission +- Can't resolve the collation conflict between **SQL_Latin1_General_CP1_CI_AS** and **French_CI_AS** in the equal to operation. **Cause** @@ -37,17 +37,15 @@ Therefore, there will be issues in analysis due to the mismatch. **Resolution** -The following is a work-around which we use to avoid collation errors. However, when making changes +The following is a workaround to avoid collation errors. However, when making changes at the SQL Server level, use caution as it actually rebuilds all user/system database objects. If -there are schema bound objects (i.e. Constraints), the whole operation will fail. Make sure to have +there are schema bound objects (i.e. Constraints), the whole operation will fail. ensure to have all of the information or scripts needed to recreate the Access Analyzer user’s databases and all of -the objects in them. Customers should use a localized version of the SQL Server, and this should not +the objects in them. Customers should use a localized version of the SQL Server, and this shouldn't be done in production environments. #### Change Collation at the Database Level -Follow the steps to change the collation at the database level. - **Step 1 –** Access the Database Properties in SQL Server Management Studio. ![SQL Server Management Studio Database Properties window](/images/accessanalyzer/12.0/install/application/databasepropertiescollation.webp) @@ -58,8 +56,6 @@ Now that the collations match, proceed with Access Analyzer installation. #### Change Collation at the SQL Server Level -Follow the steps to change the collation at the SQL Server level. - ![SQL Server Configuration Manager](/images/accessanalyzer/12.0/install/application/sqlserverconfigurationmanager.webp) **Step 1 –** Stop the SQL Server service from the Configuration Manager. @@ -87,13 +83,13 @@ Now that the collations match, proceed with Access Analyzer installation. ### Case Sensitive Collation -Access Analyzer does not support case sensitive collation settings. Case insensitive collations are -notated by having **CI** in the collation, for example **Latin1_General_CI_AS**. +Access Analyzer doesn't support case sensitive collation settings. Case insensitive collations +include **CI** in the collation name, for example **Latin1_General_CI_AS**. **Cause** -For example, `SYS.INDEXES` will be unable to be found if there was an English install of SQL Server -but a Turkish collation which is case sensitive. So `'SYS.INDEXES != 'sys.indexes' `in the +For example, if there's an English install of SQL Server but a Turkish collation, which is case +sensitive, SQL Server can't find `SYS.INDEXES`. So `'SYS.INDEXES != 'sys.indexes' `in the environment. **Resolution** @@ -105,9 +101,9 @@ All collation settings must be case insensitive. The following are possible problems for future consideration. During comparison or joining of columns, collation conflict error occurs in two cases if collation -of one column does not match with collation of another column: +of one column doesn't match with collation of another column: -This can be generated by the following script: +The following script can generate this: ``` CREATE TABLE TestTab @@ -119,18 +115,18 @@ INSERT INTO TestTab VALUES (1, 'abc', 'abc')  SELECT * FROM TestTab WHERE CharCol = CharCol2 ``` -- Error Returned – Cannot resolve the collation conflict between **Greek_CI_AS** and +- Error Returned – Can't resolve the collation conflict between **Greek_CI_AS** and **French_CI_AS** in the equal to operation. -- Resolution – If the select statement is changed as below, then it would run successfully. +- Resolution – If you change the select statement as follows, it runs successfully. ``` SELECT * FROM TestTab WHERE CharCol = CharCol2 COLLATE Albanian_CI_AI ``` :::note -Explicit collation (Albanian_CI_AI) is not one of any column, but after that it will -complete successfully. The collation of two columns have not been matched, instead the third rule of -collation precedence was implemented. See the Microsoft +Explicit collation (Albanian_CI_AI) isn't one of any column, but after that it will +complete successfully. SQL Server hasn't matched the collation of the two columns; instead, it +implements the third rule of collation precedence. See the Microsoft [Collation Precedence](https://learn.microsoft.com/en-us/sql/t-sql/statements/collation-precedence-transact-sql) article for additional information. ::: diff --git a/docs/accessanalyzer/12.0/install/application/firstlaunch.md b/docs/accessanalyzer/12.0/install/application/firstlaunch.md index dce40faf05..cfdd4ea176 100644 --- a/docs/accessanalyzer/12.0/install/application/firstlaunch.md +++ b/docs/accessanalyzer/12.0/install/application/firstlaunch.md @@ -6,8 +6,8 @@ sidebar_position: 30 # Access Analyzer Initial Configuration -Once the Access Analyzer installation process is complete, and before performing actions within -Access Analyzer, the initial settings for the Access Analyzer Console must be configured. +After the Access Analyzer installation process is complete, and before performing actions within +Access Analyzer, you must configure the initial settings for the Access Analyzer Console. ![Newrix Access Governance shortcut](/images/accessanalyzer/12.0/install/application/shortcut.webp) @@ -36,7 +36,7 @@ StealthAUDIT root folder path to copy from**. See the **Step 4 –** Configure the options on the SQL Server Settings page. - Server name – Enter the database server host name (NetBIOS name, FQDN, or IP Address) -- Instance name – If the SQL Server is configured to use an instance name, provide the instance name +- Instance name – If you configured the SQL Server to use an instance name, provide the instance name in the text box. If not, leave this text box blank. - To change the instance port number, provide the instance name in the format @@ -46,30 +46,30 @@ StealthAUDIT root folder path to copy from**. See the - Command timeout [number] minutes – Number of minutes before Access Analyzer halts any SQL queries running for that amount of time. This prevents SQL queries from running excessively long. The default is 1440 minutes. -- Windows authentication – Leverages the account used to open the Access Analyzer Console. This +- Windows authentication – Uses the account used to open the Access Analyzer Console. This option will use Windows NT Authentication to authenticate to the SQL Server. It also requires the Schedule Service Account to have proper permissions on the SQL database. -- SQL Server authentication – Leverages an account created within the SQL Server. +- SQL Server authentication – Uses an account created within the SQL Server. - - User name and password – If SQL Server authentication is selected, provide the **User name** + - User name and password – If you select SQL Server authentication, provide the **User name** and **Password** for the SQL account. - Specify a new password below – Specify a new password for the SQL server. -- Use existing database – Confirm the SQL Server connection has been established by selecting the - radio button for **Use existing database** and clicking the drop-down arrow. If a listing of - databases appears, then the connection has been established. Select this option to use a - pre-existing database. Then select a database from the drop-down menu of available databases. +- Use existing database – Confirm that Access Analyzer established the SQL Server connection by + selecting the radio button for **Use existing database** and clicking the dropdown arrow. If a + listing of databases appears, Access Analyzer established the connection. Select this option to + use a pre-existing database. Then select a database from the dropdown menu of available databases. - Create new database – Select this option to create a new database during the configuration of the storage profile. Enter a unique, descriptive name for the new database. If multiple databases - might exist for Access Analyzer, then the default name of Access Analyzer is not recommended. + might exist for Access Analyzer, avoid using the default name of Access Analyzer. See the [Securing the Access Analyzer Database](/docs/accessanalyzer/12.0/install/application/database/database.md#securing-the-access-analyzer-database) topic for additional information on creating a SQL Server database for Access Analyzer. **Step 5 –** Click **Next**. -- If SQL Server authentication is used, the Options page is displayed next. Skip to Step 7. -- If Windows Server authentication is used, the **Schedule Account** page is enabled for +- If you use SQL Server authentication, the Options page displays next. Skip to Step 7. +- If you use Windows Server authentication, the **Schedule Account** page becomes enabled for configuration. Continue to Step 6. ![Schedule Account Configuration page](/images/accessanalyzer/12.0/install/application/scheduleaccount.webp) @@ -79,7 +79,7 @@ page. The account configured here must be an Active Directory account and must h Access Analyzer Console server’s local Task folders as well as sufficient rights to the Access Analyzer database. -There are two options that can be selected: +You can select one of two options: - Skip this step, I will configure a schedule service account later – Select this radio button to skip this step and configure the schedule service account later @@ -93,22 +93,21 @@ There are two options that can be selected: ![Configuration wizard Options page](/images/accessanalyzer/12.0/install/application/options.webp) -**Step 7 –** On the Options page, select whether to send usage statistics to Netwrix to help us -improve our product. After the Usage Statistics option is set as desired, click **Next** to +**Step 7 –** On the Options page, select whether to send usage statistics to Netwrix to help improve the product. After you set the Usage Statistics option as desired, click **Next** to continue. -- If selected, usage statistics are collected and sent to Netwrix +- If selected, Access Analyzer collects usage statistics and sends them to Netwrix - - Upon startup of the Access Analyzer console, the system checks if usage statistics have been - sent in the last 7 days. If they have not been, stored procedures run against the Access + - Upon startup of the Access Analyzer console, the system checks whether it sent usage + statistics in the last 7 days. If not, stored procedures run against the Access Analyzer database and gather data about job runs, access times, and environmental details like - resource counts, users counts, number of exceptions, and so on. This data is then sent back to - Netwrix to help us identify usage trends and common pain points, so that we can use this - information to improve the product. - - Only anonymous statistic-level data is included. No private company or personal data is - collected or sent to Netwrix. + resource counts, users counts, number of exceptions, and so on. Access Analyzer then sends this + data back to Netwrix to help identify usage trends and common issues, which Netwrix uses to + improve the product. + - Access Analyzer includes only anonymous statistic-level data, and doesn't collect or send any + private company or personal data to Netwrix. -- If cleared, no usage statistics are collected or sent to Netwrix +- If cleared, Access Analyzer doesn't collect or send usage statistics to Netwrix ![Progress page when upgrade process has completed](/images/accessanalyzer/12.0/install/application/completed_1.webp) @@ -126,6 +125,6 @@ the log after exiting the wizard, it is located in the installation directory at ![Netwrix Acces Governance Settings Node](/images/accessanalyzer/12.0/install/application/settingsnode.webp) The Access Analyzer Console is now ready for custom configuration and use. There are a few -additional steps to complete in order to begin collecting data, such as configuring a Connection +additional steps to complete to begin collecting data, such as configuring a Connection Profile and a Schedule Service account as well as discovering hosts and setting up host lists. See the [Getting Started](/docs/accessanalyzer/12.0/gettingstarted.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/install/application/overview.md b/docs/accessanalyzer/12.0/install/application/overview.md index b4478b1262..c0f9bf9bc2 100644 --- a/docs/accessanalyzer/12.0/install/application/overview.md +++ b/docs/accessanalyzer/12.0/install/application/overview.md @@ -11,7 +11,7 @@ required when first launching the Access Analyzer Console. It also includes addi such as how to secure the Access Analyzer Database, and configuring the Web Console for viewing reports outside of the Access Analyzer Console. -Prior to installing Access Analyzer, please ensure that all of the prerequisites have been met. See +Before installing Access Analyzer, ensure that you meet all of the prerequisites. See the [Requirements](/docs/accessanalyzer/12.0/requirements/overview.md) topic for more information. ## Binaries @@ -22,16 +22,14 @@ Your Netwrix Representative will provide the appropriate binaries. - Access Analyzer binary – Core installation package - Includes data collectors, analysis modules, and action modules - - An organization’s license key, needed during installation, controls which components are laid - down during installation - - If your license includes Sensitive Data Discovery (SDD), the necessary SDD components are - installed + - An organization’s license key, needed during installation, controls which components the + installation lays down + - If your license includes Sensitive Data Discovery (SDD), Access Analyzer installs the necessary SDD components - Installs the Web Console - File System Proxy binary – Installation package for the File System Proxy Scanning option - - If your license includes Sensitive Data Discovery (SDD), the necessary SDD components are - installed + - If your license includes Sensitive Data Discovery (SDD), Access Analyzer installs the necessary SDD components - See the [File System Proxy Service Installation](/docs/accessanalyzer/12.0/install/filesystemproxy/wizard.md) topic for additional information. @@ -45,8 +43,7 @@ Your Netwrix Representative will provide the appropriate binaries. - SharePoint Agent binary – Installation package for the SharePoint Agent (optional for Access Auditing of SharePoint farms) - - If your license includes Sensitive Data Discovery (SDD), the necessary SDD components are - installed + - If your license includes Sensitive Data Discovery (SDD), Access Analyzer installs the necessary SDD components - See the [SharePoint Agent Installation](/docs/accessanalyzer/12.0/install/sharepointagent/overview.md) topic for additional information. @@ -70,7 +67,7 @@ Your Netwrix Representative will provide the appropriate binaries. are logged into the Netwrix Partner Portal can download the latest version of their software products from the My Product page: [https://www.netwrix.com/par/site/products](https://www.netwrix.com/my_products.html). To - receive an invitation to the Partner Portal, please contact + receive an invitation to the Partner Portal, contact [netwrix.msp@netwrix.com](http://netwrix.msp@netwrix.com/). - See the [Netwrix Access Information Center Documentation](https://helpcenter.netwrix.com/category/accessinformationcenter) diff --git a/docs/accessanalyzer/12.0/install/application/reports/adfs.md b/docs/accessanalyzer/12.0/install/application/reports/adfs.md index 944062cdb9..98b9a9e934 100644 --- a/docs/accessanalyzer/12.0/install/application/reports/adfs.md +++ b/docs/accessanalyzer/12.0/install/application/reports/adfs.md @@ -6,11 +6,11 @@ sidebar_position: 80 # Configuring the Web Console to use ADFS -The Access Analyzer Webserver and Access Information Center are able to support Single-Sign-On (SSO) +The Access Analyzer Webserver and Access Information Center can support Single-Sign-On (SSO) leveraging WSFederation with SAML tokens. This guide contains steps for implementing SSO using Active Directory Federation Services (ADFS). -Follow the steps to configure the Web Console to use ADFS authentication: +Configure the Web Console to use ADFS authentication: :::note A certificate from the ADFS server is required. Confer with a PKI administrator to @@ -21,7 +21,7 @@ determine which certificate method will conform to the organization's security p **Step 1 –** Import the certificate for the ADFS server onto the hosting server using the Certificate Management MMC snap-in. -- If used, self-signed certificates will also need to be imported +- If used, also import self-signed certificates **Step 2 –** On the ADFS server, open **AD FS Management**. @@ -33,7 +33,7 @@ Add Relying Party Trust Wizard to configure the relying party trust: **Next**. - On the Specify Display Name page, enter a display name for the relying party trust. Click **Next**. -- On the Configure URL page, do not select any options and click **Next**. +- On the Configure URL page, don't select any options and click **Next**. ![Identifier added on the Configure Identifiers page](/images/accessanalyzer/12.0/install/application/reports/relyingpartytrustwizardidentifier.webp) @@ -46,7 +46,7 @@ Add Relying Party Trust Wizard to configure the relying party trust: ![Add an Endpoint window](/images/accessanalyzer/12.0/install/application/reports/addanendpointwindow.webp) -**Step 4 –** Double-click on the newly added relying party trust to open it's Properties window. +**Step 4 –** Double-click the newly added relying party trust to open it's Properties window. Navigate to the Endpoints tab and click **Add WS-Federation**. On the Add an Endpoint window, add ``https://``:``/federation`` as the Trusted URL, then click **OK**. @@ -66,7 +66,7 @@ right-hand panel. - On the Configure Claim Rule page, enter a name in the **Claim rule name** field. -If the SID claim is not configured by default, add it to the Claim Description as follows: +If ADFS doesn't configure the SID claim by default, add it to the Claim Description as follows: ![Configure Claim Rule SID Properties](/images/accessanalyzer/12.0/install/application/reports/claimrulenamesidproperties.webp) @@ -121,12 +121,12 @@ The following is an example of how the parameters should look when configured in **Step 9 –** Navigate to Services (`services.msc`). Restart the **Access Analyzer Web Server** service. -ADFS authentication is now enabled for Access Analyzer. +Access Analyzer now supports ADFS authentication. ## Update the Published Reports URL for ADFS -If ADFS does not accept `http://localhost:8082/` as an acceptable path, the path will need to be -updated in the Published Reports properties window. Follow the steps to configure the Published +If ADFS doesn't accept `http://localhost:8082/` as an acceptable path, you must update the path +in the Published Reports properties window. Configure the Published Reports URL for ADFS: **Step 1 –** Right-click the Published Reports shortcut on the desktop and select **Properties**. @@ -137,4 +137,4 @@ Reports URL for ADFS: **Step 3 –** Click **Apply**. Exit the window. -The Published Reports URL is now configured for ADFS. +You've now configured the Published Reports URL for ADFS. diff --git a/docs/accessanalyzer/12.0/install/application/reports/disclaimer.md b/docs/accessanalyzer/12.0/install/application/reports/disclaimer.md index 2edb8758e9..ce192e450d 100644 --- a/docs/accessanalyzer/12.0/install/application/reports/disclaimer.md +++ b/docs/accessanalyzer/12.0/install/application/reports/disclaimer.md @@ -8,7 +8,6 @@ sidebar_position: 70 Users can add a disclaimer message to the logon screen by adding a custom `Disclaimer.txt` file in the Web folder in the Access Analyzer directory and configuring the `WebServer.exe.config` file. -Follow the steps to configure the optional disclaimer message: **Step 1 –** Navigate to the Web folder of the installation directory: ` …\STEALTHbits\StealthAUDIT\Web`. @@ -18,8 +17,8 @@ Follow the steps to configure the optional disclaimer message: **Step 2 –** Create a `Disclaimer.txt` file in the Web folder. Write a custom disclaimer that displays on the login page for the Web Console. -- The text file must be named `Disclaimer.txt`. The disclaimer message option is not configured - properly if using a text file with a different name. +- You must name the text file `Disclaimer.txt`. If you use a text file with a different name, the + disclaimer message option won't work correctly. ![File Explorer WebServer.exe.config](/images/accessanalyzer/12.0/install/application/reports/webserverexeconfigfile.webp) @@ -43,10 +42,10 @@ displays on the login page for the Web Console. ![Web Console login page with disclaimer message](/images/accessanalyzer/12.0/install/application/reports/webconsolelogindisclaimer.webp) -**Step 7 –** To check if the disclaimer message was configured correctly, open the Web Console to -access the login page. +**Step 7 –** To check whether you configured the disclaimer message correctly, open the Web Console +to access the login page. -- If the disclaimer is configured correctly, the custom disclaimer message displays at the bottom of - the login page. +- If you configured the disclaimer correctly, the custom disclaimer message displays at the bottom + of the login page. The disclaimer message displays on the Web Console login page. diff --git a/docs/accessanalyzer/12.0/install/application/reports/domains.md b/docs/accessanalyzer/12.0/install/application/reports/domains.md index c6fb702078..d5ee4fc857 100644 --- a/docs/accessanalyzer/12.0/install/application/reports/domains.md +++ b/docs/accessanalyzer/12.0/install/application/reports/domains.md @@ -8,23 +8,23 @@ sidebar_position: 30 When the `AuthenticationDomains` parameter in the **WebServer.exe.config** file is blank, only domain users from the domain where the Access Analyzer Console resides can access the Web Console. -Access can be granted from other domains when specified within this parameter. +You can grant access from other domains by specifying them within this parameter. :::note -Once another domain is added, then it is necessary to also add the domain where the Access +After adding another domain, also add the domain where the Access Analyzer Console resides. ::: All domains provided or enumerated must have a trust relationship with the domain where Access -Analyzer resides. Follow the steps to allow access to the Web Console from other domains. +Analyzer resides. **Step 1 –** Open the **WebServer.exe.config** file with a text editor, for example Notepad. It is located within the Web folder of the Access Analyzer installation directory. ![WebServer.exe.config file in Notepad](/images/accessanalyzer/12.0/install/application/reports/webserverexeconfigmultipledomains.webp) -**Step 2 –** Add the desired domains to the value for the `AuthenticationDomains` parameter: +**Step 2 –** Add the domains you want to the value for the `AuthenticationDomains` parameter: ``` @@ -40,10 +40,10 @@ Use domain name in a comma-separated list. For example: **Step 4 –** Navigate to Services (`services.msc`). Restart the Access Analyzer Web Server service. -The Web Console can now be accessed from multiple domains. +Users can now access the Web Console from multiple domains. :::note -In order for the AIC to be accessed from these domains, this must also be configured for +For users to access the AIC from these domains, you must also configure this setting for the AIC. See the Multiple Domains topic in the [Netwrix Access Information Center Documentation](https://helpcenter.netwrix.com/category/accessinformationcenter) for additional information. diff --git a/docs/accessanalyzer/12.0/install/application/reports/entraidsso.md b/docs/accessanalyzer/12.0/install/application/reports/entraidsso.md index f7780723e2..e277493faf 100644 --- a/docs/accessanalyzer/12.0/install/application/reports/entraidsso.md +++ b/docs/accessanalyzer/12.0/install/application/reports/entraidsso.md @@ -6,9 +6,9 @@ sidebar_position: 50 # Microsoft Entra ID Single Sign-On -Microsoft Entra ID Single Sign-On (SSO) can be configured for logging in to the Web Console to view -reports. When configured, users accessing the Web Console are directed to the Microsoft Entra -ID login page, and can log in using their existing Entra credentials. +You can configure Microsoft Entra ID Single Sign-On (SSO) for logging in to the Web Console to view +reports. When configured, the Web Console directs users to the Microsoft Entra +ID login page, where they can log in using their existing Entra credentials. The following is required to use Microsoft Entra ID SSO: @@ -20,9 +20,8 @@ ID, and then configure the Web Console to use it. ## Configure an Application in Microsoft Entra ID -An application must be registered for the Web Console with your Microsoft Entra ID tenant and be -configured with the necessary single sign-on settings. Follow the steps to create and configure the -application. +You must register an application for the Web Console with your Microsoft Entra ID tenant and +configure it with the necessary single sign-on settings. Create and configure the application: **Step 1 –** Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com/). @@ -53,8 +52,7 @@ Configuration section. Add your Identifier and Reply URL, and then click **Save* https://app0190.train90.local:8082/federation ``` -**Step 6 –** Next, click **Edit** on the Attributes & Claims section. The four claims in the table -below are required. For each of these, click **Add new claim**, enter the information from the +**Step 6 –** Next, click **Edit** on the Attributes & Claims section. The four claims in the following table are required. For each of these, click **Add new claim**, enter the information from the table, and then click **Save**. | Name | Namespace | Source attribute | @@ -64,23 +62,23 @@ table, and then click **Save**. | sid | http://schemas.xmlsoap.org/ws/2005/05/identity/claims | user.onpremisessecurityidentifier | | upn | http://schemas.xmlsoap.org/ws/2005/05/identity/claims | user.onpremisesuserprincipalname | -Once configured they should show under Additional claims as below: +Once configured, they should show under Additional claims as follows: ![Claims configured](/images/accessanalyzer/12.0/install/application/reports/entraidssoclaims.webp) **Step 7 –** In the **Manage** > **Users and groups** section for your application, add any required users or groups to give permission to access the application. -The application is now configured with the necessary settings. The next step is to enable the use of +You've now configured the application with the necessary settings. The next step is to enable the use of Microsoft Entra ID SSO in the web server config file. ## Enable in the Web Server Config File -To enable Microsoft Entra ID SSO for the Web Console, the web server config file needs to be updated -with values from Microsoft Entra ID. Follow the steps to enable the SSO. +To enable Microsoft Entra ID SSO for the Web Console, you need to update the web server config file +with values from Microsoft Entra ID. Enable the SSO: :::tip -Remember, Enabling Entra ID SSO requires SSL to already have been enabled for the web server. See +Remember, enabling Entra ID SSO requires that you already enabled SSL for the web server. See the [Securing the Web Console](/docs/accessanalyzer/12.0/install/application/reports/secure.md) topic for additional information. ::: @@ -95,17 +93,17 @@ Parameters in the config file, and add the required values from your Microsoft E - WsFederationMetaData – Metadata markup for describing the services provided - - This value can be retrieved from your application in Microsoft Entra ID: **Manage** > **Single + - You can retrieve this value from your application in Microsoft Entra ID: **Manage** > **Single sign-on** > **SAML Certificates** > **App Federation Metadata Url** - WsFederationRealm – Maps to the application identifier to Microsoft Entra ID - - This value can be retrieved from your application in Microsoft Entra ID: **Manage** > **Single + - You can retrieve this value from your application in Microsoft Entra ID: **Manage** > **Single sign-on** > **Basic SAML Configuration** > **Identifier** - WsFederationReply – This is the endpoint for the configured relying party trust - - This value can be retrieved from your application in Microsoft Entra ID: **Manage** > **Single + - You can retrieve this value from your application in Microsoft Entra ID: **Manage** > **Single sign-on** > **Basic SAML Configuration** > **Reply URL** For example: @@ -121,4 +119,4 @@ For example: **Step 4 –** Navigate to Services (`services.msc`). Restart the Netwrix Access Analyzer (formerly Enterprise Auditor) Web Server service. -The Web Console has been enabled for Microsoft Entra ID single sign-on. +You've now enabled Microsoft Entra ID single sign-on for the Web Console. diff --git a/docs/accessanalyzer/12.0/install/application/reports/kerberosencryption.md b/docs/accessanalyzer/12.0/install/application/reports/kerberosencryption.md index 917acd99be..fbbebfcfa2 100644 --- a/docs/accessanalyzer/12.0/install/application/reports/kerberosencryption.md +++ b/docs/accessanalyzer/12.0/install/application/reports/kerberosencryption.md @@ -10,28 +10,28 @@ If a computer's Local Security Policy, or applicable Group Policy, enforces cert methods for Kerberos authentication, then the service account running the Access Analyzer Web Server must support the same encryption methods. -If encryption methods have been configured for Kerberos on the Access Analyzer server but not on the -service account running the Access Analyzer Web Server service, then users will not be able to -log-in to the Web Console and will receive the below error message. +If you configured encryption methods for Kerberos on the Access Analyzer server but not on the +service account running the Access Analyzer Web Server service, users won't be able to +log in to the Web Console and will receive the following error message. ![Kerberos Error Message](/images/accessanalyzer/12.0/install/application/reports/kerberoserrormessage.webp) -When this occurs, the following error will be logged: +When this occurs, Access Analyzer logs the following error: _ERROR - Unhandled server error: Nancy.RequestExecutionException: Oh noes! ---> -System.Security.SecurityException: The encryption type requested is not supported by the KDC_. +System.Security.SecurityException: The encryption type requested isn't supported by the KDC_. -This error will be logged in the following location: +Access Analyzer logs this error in the following location: **%SAINSTALLDIR%\SADatabase\Logs\Web\service.log** -While it is not required to configure these settings, this section provides the locations and steps +While it isn't required to configure these settings, this section provides the locations and steps necessary to configure encryption methods in Local and Group policies to allow Kerberos for the Report Index if an error does occur. ## Local Security Policies -Follow the steps to configure a Local Security Policy to allow Kerberos. +Configure a Local Security Policy to allow Kerberos. **Step 1 –** Open the Local Security Policy window. @@ -48,14 +48,14 @@ policy > click **Properties**. **Step 5 –** Click **Apply**, then click **OK**. -A Local Security Policy has been configured to allow encryption methods for Kerberos. Proceed to the -[Configure Active Directory Users and Computers Settings to allow Kerberos](#configure-active-directory-users-and-computers-settings-to-allow-kerberos) -section of this topic to ensure Active Directory Users and Computer settings are configured to allow +You've now configured a Local Security Policy to allow encryption methods for Kerberos. Proceed to +the [Configure Active Directory Users and Computers Settings to allow Kerberos](#configure-active-directory-users-and-computers-settings-to-allow-kerberos) +section of this topic to ensure you configure Active Directory Users and Computer settings to allow the encryption methods for Kerberos. ## Group Security Policy -Follow the steps to configure a Local Group Security Policy to allow Kerberos. +Configure a Local Group Security Policy to allow Kerberos. **Step 1 –** Open the Local Group Policy Editor window. @@ -73,17 +73,17 @@ policy, then click **Properties**. **Step 5 –** Click **Apply**, then click **OK**. -A Local Group Security Policy has been configured to allow encryption methods for Kerberos. Proceed -to the +You've now configured a Local Group Security Policy to allow encryption methods for Kerberos. +Proceed to the [Configure Active Directory Users and Computers Settings to allow Kerberos](#configure-active-directory-users-and-computers-settings-to-allow-kerberos) -section of this topic to ensure Active Directory Users and Computer settings are configured to allow +section of this topic to ensure you configure Active Directory Users and Computer settings to allow the encryption methods for Kerberos. ## Configure Active Directory Users and Computers Settings to allow Kerberos -Follow the steps to ensure the settings for Active Directory Users and Computers are configured to -allow the encryption methods to allow Kerberos. Configurations selected in this section should -reflect the configuration options selected in the two sections above. See the +Ensure you configure the settings for Active Directory Users and Computers to +allow the encryption methods for Kerberos. Configurations you select in this section should +reflect the configuration options you selected in the two preceding sections. See the [Local Security Policies](#local-security-policies) and [Group Security Policy](#group-security-policy) topics for additional information. @@ -103,6 +103,6 @@ reflect the configuration options selected in the two sections above. See the **Step 6 –** Click **Apply**, then click **OK**. -Active Directory Users and Computer settings have been configured to allow the encryption methods +You've now configured Active Directory Users and Computer settings to allow the encryption methods for Kerberos. These settings should match the configuration options for Local Security Policies and Local Group Policies. diff --git a/docs/accessanalyzer/12.0/install/application/reports/okta.md b/docs/accessanalyzer/12.0/install/application/reports/okta.md index 4d3ffa765f..b20cb83937 100644 --- a/docs/accessanalyzer/12.0/install/application/reports/okta.md +++ b/docs/accessanalyzer/12.0/install/application/reports/okta.md @@ -8,7 +8,7 @@ sidebar_position: 90 Create an Access Analyzer Application in Okta Using the WS-Fed Template -Follow the steps to create an Access Analyzer Application in Okta Using the WS-Fed Template: +To create an Access Analyzer Application in Okta using the WS-Fed template: **Step 1 –** Log in to Okta. @@ -28,12 +28,12 @@ Retrieve the Values to Paste into the Access Analyzer WebServer.exe.config File **Step 1 –** In the Access Analyzer application, click the **Sign On** tab. -**Step 2 –** Right click on the **Identity Provider metadata** link and select **Copy Link Address** +**Step 2 –** Right click the **Identity Provider metadata** link and select **Copy Link Address** to get the value for the WSFederationMetadata URL. **** -**Step 3 –** Click on the General tab to copy the value for the **Realm**. This value will be unique +**Step 3 –** Click the General tab to copy the value for the **Realm**. This value will be unique per tenant. `https://www.okta.com/` @@ -44,7 +44,7 @@ per tenant. Edit the WebServer.exe.config File -Follow the steps to edit the **WebServer.exe.config** file: +To edit the **WebServer.exe.config** file: **Step 1 –** Open the **WebServer.exe.config** file with a text editor, such as Notepad++. It is located in the Web folder within the Access Analyzer installation. @@ -111,7 +111,7 @@ populate the following fields. ![oktaprofileeditor](/images/accessanalyzer/12.0/install/application/reports/oktaprofileeditor.webp) -**Step 2 –** Navigate to the Directory menu and select **Profile Editor** from the drop-down menu. +**Step 2 –** Navigate to the Directory menu and select **Profile Editor** from the dropdown menu. Click the **Edit Profile** button for the Access Analyzer application. ![Okta Add Attribute button](/images/accessanalyzer/12.0/install/application/reports/oktaaddattribute.webp) @@ -138,12 +138,12 @@ attribute, click **Save and Add Another**. ![To Okta option under the Directory Provisioning Tab](/images/accessanalyzer/12.0/install/application/reports/oktadirectoryprovisioningtookta.webp) -**Step 5 –** Navigate to the **Directory** menu and click on the **Provisioning** tab. Click **To +**Step 5 –** Navigate to the **Directory** menu and click the **Provisioning** tab. Click **To Okta**. ![Okta Show Unmapped Attributes](/images/accessanalyzer/12.0/install/application/reports/oktashowunmappedattributes.webp) -**Step 6 –** Locate and map the attributes that were added for the profile by clicking the +**Step 6 –** Locate and map the attributes that you added for the profile by clicking the **Pencil** icon to edit attributes. To locate the attributes, scroll down and select **Show Unmapped Attributes**. @@ -165,7 +165,7 @@ additional information. ## Setting Up Multi-Factor Authentication -Follow the steps to configure multi-factor-authentication for Access Analyzer: +To configure multi-factor authentication for Access Analyzer: ![Okta MFA App Sign on Rule window](/images/accessanalyzer/12.0/install/application/reports/oktamfaappsignonrule.webp) @@ -181,4 +181,4 @@ opens. Configure the following options: **Step 2 –** Scroll down to the Access section. Check the **Prompt for factor** box and select **Every Sign On**. Click **Save**. -Multi-Factor Authentication is now configured for Access Analyzer. +You've now configured Multi-Factor Authentication for Access Analyzer. diff --git a/docs/accessanalyzer/12.0/install/application/reports/overview.md b/docs/accessanalyzer/12.0/install/application/reports/overview.md index 073ba21c27..b135ca2f1e 100644 --- a/docs/accessanalyzer/12.0/install/application/reports/overview.md +++ b/docs/accessanalyzer/12.0/install/application/reports/overview.md @@ -6,7 +6,7 @@ sidebar_position: 40 # Reports via the Web Console -The Web Console is where any reports which have been published can be viewed outside of the Access +The Web Console is where you can view any published reports outside of the Access Analyzer Console. This is also known as the Published Reports site. - Web Console – This console uses an embedded website for published reports. It provides a @@ -19,7 +19,7 @@ Console upon installation. :::note The Access Analyzer Web Server service must run as an account that has access to the -Access Analyzer database. This may be a different account than the one used to connect Access +Access Analyzer database. This may be a different account than the one you use to connect Access Analyzer to the database. If the Access Analyzer Vault service is running, the account running the Web Server service must be an Access Analyzer Administrator. See the [Vault](/docs/accessanalyzer/12.0/admin/settings/application/vault.md) topic for additional information. @@ -30,8 +30,8 @@ The Web folder that the Access Analyzer installer places at the root of the Acce directory also contains a `WebServer.exe.config` file. This file contains configurable parameters. :::warning -If encryption methods have been configured for Kerberos on the Access Analyzer server -but not on the service account running the Access Analyzer Web Server service, then users will not +If you configure encryption methods for Kerberos on the Access Analyzer server +but not on the service account running the Access Analyzer Web Server service, users will not be able to log-in to the Web Console and will receive an error message. See the [Manage Kerberos Encryption Warning for the Web Console](/docs/accessanalyzer/12.0/install/application/reports/kerberosencryption.md) topic for additional information on configuring security polices to allow Kerberos encryption. @@ -40,21 +40,21 @@ information on configuring security polices to allow Kerberos encryption. ## Log into the Web Console -In order for a user to log into the Web Console, the user’s account must have the User Principal -Name (UPN) attribute populated within Active Directory. Then the user can login using domain -credentials. If multiple domains are being utilized, then +To log into the Web Console, the user’s account must have a populated User Principal +Name (UPN) attribute within Active Directory. Then the user can login using domain +credentials. If the organization uses multiple domains, the username needs to be in the `domain\username` format when logging into the Published Reports site. -Access to reports in the Web Console can be managed through the Role Based Access feature of Access +You can manage access to reports in the Web Console through the Role Based Access feature of Access Analyzer (**Settings** > **Access**). The Web Administrator role and the Report Viewer role grant access to the published reports. See the [Role Based Access](/docs/accessanalyzer/12.0/admin/settings/access/rolebased/overview.md) topic for addition information. -The address to the Web Console can be configured within the Access Analyzer Console (**Settings** > +You can configure the address to the Web Console within the Access Analyzer Console (**Settings** > **Reporting**). The default address is `http://[hostname.domain.com]:8082`. From the Access Analyzer -Console server, it can be accessed at `http://localhost/` with any standard browser. To access the +Console server, you can access it at `http://localhost/` with any standard browser. To access the Web Console from another machine in or connected to the environment, replace localhost with the name of the Access Analyzer Console. See the [Update Website URLs](secure.md#update-website-urls) topic for additional information. @@ -67,7 +67,7 @@ topic for additional information. ::: -Follow the steps to login to the Web Console. +To log in to the Web Console: **Step 1 –** To open the Web Console page, use one of the following methods: @@ -80,7 +80,7 @@ Follow the steps to login to the Web Console. - `https://[machinename]:8082` :::note -The URL that is used may need to be added to the browser’s list of trusted sites. +You may need to add the URL to the browser’s list of trusted sites. ::: diff --git a/docs/accessanalyzer/12.0/install/application/reports/secure.md b/docs/accessanalyzer/12.0/install/application/reports/secure.md index 27fb00c1c9..95ca242c0f 100644 --- a/docs/accessanalyzer/12.0/install/application/reports/secure.md +++ b/docs/accessanalyzer/12.0/install/application/reports/secure.md @@ -6,19 +6,19 @@ sidebar_position: 10 # Securing the Web Console -Published reports can be accessed in the Web Console. There are several options for enhancing +You can access published reports in the Web Console. There are several options for enhancing security. Additional configuration options for enhanced security include: - Enable SSL – The `BindingUrl` parameter shows the port used by the Access Analyzer web server for SSL reports. If SSL is enabled, the value will be HTTPS instead of HTTP. -- Enable Multiple Domain Access – The `AuthenticationDomains` parameter allows the Web Console to be - accessed from multiple domains. By default this parameter is blank, allowing only domain users +- Enable Multiple Domain Access – The `AuthenticationDomains` parameter lets users + access the Web Console from multiple domains. By default this parameter is blank, allowing only domain users from the domain where the Access Analyzer Console resides to access the Web Console. -- Enable Single Sign-On – The `WindowsAuthentication` parameter allows domain users to be - automatically logged into the Web Console. By default this parameter is set to `false`, which - requires domain users to login each time the Web Console is accessed. See the +- Enable Single Sign-On – The `WindowsAuthentication` parameter lets domain users log in + automatically to the Web Console. By default this parameter is set to `false`, which + requires domain users to login each time they access the Web Console. See the [Enable Single Sign-On](/docs/accessanalyzer/12.0/install/application/reports/sso.md) topic for additional information. :::note @@ -27,13 +27,13 @@ Additional configuration options for enhanced security include: ::: -These parameters can be configured within the **WebServer.exe.config** file in the Web folder of the +You can configure these parameters within the **WebServer.exe.config** file in the Web folder of the Access Analyzer installation directory `…\STEALTHbits\StealthAUDIT\Web`. ## Enable SSL for the Web Console -To enable Secure Sockets Layer (SSL) for secure, remote connections to the Web Console it is -necessary to bind a certificate to the port. See the +To enable Secure Sockets Layer (SSL) for secure, remote connections to the Web Console, you must +bind a certificate to the port. See the [Use a Self-Signed Certificate for SSL](#use-a-self-signed-certificate-for-ssl) topic for more information. Follow the steps on the server where Access Analyzer is installed to enable SSL for the Web Console. @@ -41,8 +41,8 @@ Web Console. :::note The following steps require a certificate to be available. Organizations typically have one or more system administrators responsible for Public Key Infrastructure (PKI) and certificates. -To continue with this configuration it will first be necessary to confer with the PKI administrator -to determine which certificate method will conform to the organization’s security policies. +To continue with this configuration, you must first confer with the PKI administrator +to determine which certificate method conforms to the organization’s security policies. Optionally, see [Use a Self-Signed Certificate for SSL](#use-a-self-signed-certificate-for-ssl) for an Administrator PowerShell command which will both create and import a self-signed certificate. ::: @@ -52,16 +52,16 @@ an Administrator PowerShell command which will both create and import a self-sig snap-in. :::note -If using a self-signed certificate, it will also need to be imported. +If you're using a self-signed certificate, you must also import it. ::: -**Step 2 –** Create an SSL binding. It is necessary to use the certificate’s **Hash** value for the +**Step 2 –** Create an SSL binding. Use the certificate’s **Hash** value for the `$certHash` value: :::note -The following Administrator PowerShell dir command can be run on the certificate's “drive” -to find the **Hash** value of a certificate which was already created and the output will include +You can run the following Administrator PowerShell dir command on the certificate's “drive” +to find the **Hash** value of an existing certificate. The output includes the Thumbprint (**Hash**) value and the certificate name: ::: @@ -92,8 +92,8 @@ located within the Web folder of the Access Analyzer installation directory. ``` -- After changing the `BindingUrl` value in the **WebServer.exe.config** file, the Website URL must - be updated to match the new value in the following places: +- After you change the `BindingUrl` value in the **WebServer.exe.config** file, you must + update the Website URL to match the new value in the following places: - Access Analyzer's **Settings** > **Reporting** node - Access Analyzer's Published Reports Desktop icon properties - See the [Update Website URLs](#update-website-urls) topic for additional information. @@ -104,14 +104,14 @@ located within the Web folder of the Access Analyzer installation directory. Enterprise Auditor) Web Server service. :::note -If also using the AIC, then SSL needs to be enabled for the AIC using this certificate. +If you're also using the AIC, you must enable SSL for the AIC using this certificate. See the Securing the AIC section of the [Netwrix Access Information Center Documentation](https://helpcenter.netwrix.com/category/accessinformationcenter) for additional information. ::: -The Web Console has been enabled for SSL communication. Access it using the server’s fully qualified +You have now enabled the Web Console for SSL communication. Access it using the server’s fully qualified domain name and the HTTPS port (`https://[hostname.domain.com]:8082`). If a self-signed certificate was used, then the client-side access to the Web Console will generate a Certificate error. See the [Add the Certificate for Client-Side Access](#add-the-certificate-for-client-side-access) topic for @@ -127,8 +127,6 @@ URL must be updated to match the new value in the following places: **Update the Website URL in the Reporting Node** -Follow the steps to update the Website URL in the **Settings** > **Reporting** node. - **Step 1 –** Expand **Settings** and select the **Reporting** node. ![Access Governance Reporting Settings page](/images/accessanalyzer/12.0/install/application/reports/websiteurlreporting.webp) @@ -137,14 +135,11 @@ Follow the steps to update the Website URL in the **Settings** > **Reporting** n **Step 3 –** Click **Save**. -The Website URL is now updated. +You have now updated the Website URL. Update the URL in the Published Reports Desktop Icon Properties -Follow the steps to update the URL in the Published Reports desktop icon's Published Report's -Properties window. - -**Step 1 –** Right click on the **Published Reports** desktop shortcut and click **Properties**. +**Step 1 –** Right click the **Published Reports** desktop shortcut and click **Properties**. ![Published Reports desktop icon properties](/images/accessanalyzer/12.0/install/application/reports/publishedreportsproperties.webp) @@ -153,7 +148,7 @@ Properties window. **Step 3 –** Click **Apply** and then **OK** to exit. -The URL is now updated. +You have now updated the URL. ### Remove Certificate from the Port @@ -190,12 +185,12 @@ The output will show this info: `80F78FD2566793D2F39E748CDF6DED09B6F57A82  CN=machinename.domain.com` -The Thumbprint value is the certificate **Hash** value to be used when binding to the port. The port +The Thumbprint value is the certificate **Hash** value you use when binding to the port. The port can be the same as in HTTP (8082). Use this **Hash** value for Step 2 of the [Enable SSL for the Web Console](#enable-ssl-for-the-web-console) instructions. -Creation and import of the self-signed certificate can be validated in Microsoft Management Console. -Follow these steps to confirm the certificate is in Microsoft Management Console. +You can validate the creation and import of the self-signed certificate in Microsoft Management Console. +Confirm the certificate is in Microsoft Management Console. **Step 1 –** Open Microsoft Management Console (`mmc.exe`). @@ -217,14 +212,14 @@ window. Click **OK** to close the window. **Step 5 –** Navigate to **Certificates** > **Personal** > **Certificates**. The certificate should show in the pane on the right. -The self-signed certificate was created and imported. Repeat these steps for each client-side host. +You have now created and imported the self-signed certificate. Repeat these steps for each client-side host. ### Add the Certificate for Client-Side Access When you open the Web Console with SSL enabled, the web browser shows a Your connection isn't -private warning message. This can be removed by importing the certificate onto the client server. +private warning message. You can remove this by importing the certificate onto the client server. -Follow the steps to remove the certificate error. +Remove the certificate error. **Step 1 –** Open the Web Console in your browser. @@ -240,7 +235,7 @@ Viewer from the warning details. - In Microsoft Edge, click the **Your Connection to this site isn't secure** section, and then click the certificate icon. -- In Google Chrome, click **Certificate is not valid**. +- In Google Chrome, click **Certificate isn't valid**. ![Web browser Certificate Viewer window](/images/accessanalyzer/12.0/install/application/reports/certificateviewer.webp) @@ -263,7 +258,7 @@ should state that the import was successful. Click **OK** to close out all dialo ![Microsoft Management Console Trusted Root Certification Authorities Certificates](/images/accessanalyzer/12.0/install/application/reports/addcertificateconsole.webp) **Step 7 –** In the Microsoft Management Console, check the **Trusted Root Certification -Authorities** > **Certificates**. The self-signed certificate should now be listed there. +Authorities** > **Certificates**. The self-signed certificate should now appear there. The client-side access to the Web Console will no longer generate a certificate error. Repeat these steps for each client-side host. diff --git a/docs/accessanalyzer/12.0/install/application/reports/sso.md b/docs/accessanalyzer/12.0/install/application/reports/sso.md index 52320c6c3d..708fd25f01 100644 --- a/docs/accessanalyzer/12.0/install/application/reports/sso.md +++ b/docs/accessanalyzer/12.0/install/application/reports/sso.md @@ -6,10 +6,10 @@ sidebar_position: 40 # Enable Single Sign-On -Single sign-on using Windows authentication allows users to be automatically log into the Web -Console according to the user’s current login session. When opening a session from a different -domain, the user will be prompted for credentials from a pop-up windows. After authenticating, the -user will be automatically logged in the Web Console. +With single sign-on using Windows authentication, the Web Console automatically logs users +in according to the user’s current login session. When a user opens a session from a different +domain, a pop-up window prompts the user for credentials. After authenticating, the Web Console +automatically logs the user in. :::note The Web Console also supports using Microsoft Entra ID single sign-on. See the @@ -17,7 +17,7 @@ The Web Console also supports using Microsoft Entra ID single sign-on. See the ::: -Follow the steps to enable single sign-on for the Web Console. +Enable single sign-on for the Web Console. **Step 1 –** Open the **WebServer.exe.config** file with a text editor, for example Notepad. It is located within the Web folder of the Access Analyzer installation directory. @@ -35,15 +35,15 @@ located within the Web folder of the Access Analyzer installation directory. **Step 4 –** Navigate to Services (`services.msc`). Restart the Netwrix Access Analyzer (formerly Enterprise Auditor) Web Server service. -The Web Console has been enabled for single sign-on. +You have now enabled the Web Console for single sign-on. ## Local Intranet Settings -Next, configure local intranet settings to enable SSO. This enables users to have authentication -pass through Windows Authentication and bypass SSO configuration Prompts for credentials via Browser -pop-up. +Next, configure local intranet settings to enable SSO. With this configuration, authentication +passes through Windows Authentication and bypasses SSO configuration prompts for credentials via +browser pop-up. -Follow the steps to configure local intranet settings. +Configure local intranet settings. **Step 1 –** Open Windows Internet Properties (**Control Panel** > **Network and Internet** > **Internet Options**). @@ -70,7 +70,7 @@ Authentication will now pass through Windows Authentication and bypass SSO confi credentials via Browser pop-up :::note -A list of allowed authentication servers can also be configured using the +You can also configure a list of allowed authentication servers using the AuthServerAllowList policy. ::: diff --git a/docs/accessanalyzer/12.0/install/application/reports/timeout.md b/docs/accessanalyzer/12.0/install/application/reports/timeout.md index 9932fb5305..244d0eeca8 100644 --- a/docs/accessanalyzer/12.0/install/application/reports/timeout.md +++ b/docs/accessanalyzer/12.0/install/application/reports/timeout.md @@ -6,19 +6,17 @@ sidebar_position: 60 # Timeout Parameter for the Web Console -The Web Console is configured with a default timeout parameter of 15 minutes. This can be configured +The Web Console has a default timeout parameter of 15 minutes. You can configure this within the **WebServer.exe.config** file in the Web folder of the Access Analyzer installation directory: **…\STEALTHbits\StealthAUDIT\Web** -Follow the steps to modify the timeout parameter for the Web Console. - **Step 1 –** Open the **WebServer.exe.config** file with a text editor, for example Notepad. ![WebServer.exe.config file in Notepad](/images/accessanalyzer/12.0/install/application/reports/webserverexeconfigtimeout.webp) -**Step 2 –** Change the value for the `SessionTimeout` parameter to the desired number of minutes: +**Step 2 –** Change the value for the `SessionTimeout` parameter to the number of minutes you want: ``` diff --git a/docs/accessanalyzer/12.0/install/application/updatelicense.md b/docs/accessanalyzer/12.0/install/application/updatelicense.md index 19bfbd5779..cdba2f5a27 100644 --- a/docs/accessanalyzer/12.0/install/application/updatelicense.md +++ b/docs/accessanalyzer/12.0/install/application/updatelicense.md @@ -6,23 +6,22 @@ sidebar_position: 60 # Update License Key -It is necessary to install a new license key for an existing Access Analyzer installation due to the -following: +Install a new license key for an existing Access Analyzer installation for the following reasons: - To renew a Access Analyzer license that is due to expire - To grant access to additional Solutions - To enable Sensitive Data Discovery -In these situations it is possible to update the license file without going through the full +In these situations, you can update the license file without going through the full installation process. ## Install a New License File -Follow the steps to update the Access Analyzer license key without installing a new version of the -Access Analyzer Console. +Update the Access Analyzer license key without installing a new version of the Access Analyzer +Console: -**Step 1 –** Ensure the new `StealthAUDIT.lic` license file is stored locally on the Access Analyzer -Console server in order to be referenced during the installation process. +**Step 1 –** Store the new `StealthAUDIT.lic` license file locally on the Access Analyzer +Console server so the installer can reference it during the installation process. ![Windows Control Panel Uninstall or change a program window](/images/accessanalyzer/12.0/install/application/controlpaneluninstall.webp) @@ -43,13 +42,13 @@ Features**), select the Access Analyzer application and click **Change**. **Step 5 –** On the License File page, click **Browse** and navigate to the **StealthAUDIT.lic** file. It must be stored on the Access Analyzer Console server before the installation begins. When -the path to the file is visible in the text box, click **Next**. The license will be imported. +the path to the file is visible in the text box, click **Next**. The installer imports the license. ![License Features page](/images/accessanalyzer/12.0/install/application/licensefeatures.webp) **Step 6 –** The License Features page displays a list of all features covered by the imported license. It also displays the name of the organization which owns the license, the expiration date, -and the host limit. These are the features that will be installed. Click **Next**. +and the host limit. These are the features the installer will install. Click **Next**. ![Setup Wizard Ready to change page](/images/accessanalyzer/12.0/install/application/ready_1.webp) @@ -59,6 +58,6 @@ and the host limit. These are the features that will be installed. Click **Next* **Step 8 –** When the installation has completed, click **Finish** to exit the wizard. -The new license file has been imported. If the license granted access to any additional solutions, -they will now be accessible from within the Access Analyzer Console. If the new license added -Sensitive Data Discovery, the necessary components for Sensitive Data Discovery have been installed. +You have now imported the new license file. If the license granted access to any additional solutions, +they are now accessible from within the Access Analyzer Console. If the new license added +Sensitive Data Discovery, Access Analyzer has now installed the necessary components for Sensitive Data Discovery. diff --git a/docs/accessanalyzer/12.0/install/application/upgrade/overview.md b/docs/accessanalyzer/12.0/install/application/upgrade/overview.md index baf5d872d4..ad0bfe86a8 100644 --- a/docs/accessanalyzer/12.0/install/application/upgrade/overview.md +++ b/docs/accessanalyzer/12.0/install/application/upgrade/overview.md @@ -10,15 +10,15 @@ Access Analyzer 12.0 uses the Upgrade Wizard. For upgrades from versions of Acce no longer supported, contact [Netwrix Support](https://www.netwrix.com/support.html) for assistance. :::note -If any customizations have been done by a Netwrix Engineer, please ensure custom work is -not lost during the upgrade process. While using the Upgrade Wizard, customizations are archived -prior to solution upgrades. These archives are available after the solution upgrades have been -completed. Contact [Netwrix Support](https://www.netwrix.com/support.html) for additional +If a Netwrix Engineer has made any customizations, ensure the custom work is +not lost during the upgrade process. The Upgrade Wizard archives customizations +before solution upgrades. These archives are available after the solution upgrades +complete. Contact [Netwrix Support](https://www.netwrix.com/support.html) for additional information. ::: -The purpose of this document is to provide the basic steps needed for upgrading Access Analyzer and +This document provides the basic steps for upgrading Access Analyzer and the stock solutions. Contact [Netwrix Support](https://www.netwrix.com/support.html) for additional information. @@ -33,59 +33,59 @@ Analyzer application directory. If you already have Role Based Access enabled in version of Access Analyzer, then during the first initialization of Access Analyzer 12.0 the following happens: -- The NEAUsers local group is created on the Access Analyzer Console server, and is given the - required permissions on the Access Analyzer application (StealthAUDIT) folder -- Existing configured RBA users are added to this new NEAUsers group +- Access Analyzer 12.0 creates the NEAUsers local group on the Access Analyzer Console server and + gives it the required permissions on the Access Analyzer application (StealthAUDIT) folder +- Access Analyzer 12.0 adds existing configured RBA users to this new NEAUsers group :::note - The Web Administrator and Report Viewer roles do not require access to the Access - Analyzer console, so users assigned these roles are not added to the NEAUsers group. + The Web Administrator and Report Viewer roles don't require access to the Access + Analyzer console, so Access Analyzer doesn't add users assigned these roles to the NEAUsers group. ::: :::note - Adding a user to the NEAUsers group does not apply to the Web Service access type, it + Adding a user to the NEAUsers group doesn't apply to the Web Service access type, it only gives Console access. ::: -- The local users group is removed from the Access Analyzer application folder permissions +- Access Analyzer 12.0 removes the local users group from the Access Analyzer application folder permissions For this process to complete successfully, on first launch the user running Access Analyzer must -have local administrator rights. Otherwise, an exception will be thrown during the initialization. +have local administrator rights. Otherwise, Access Analyzer throws an exception during initialization. Multiple Access Analyzer Consoles Connecting to the Same Database -In environments where multiple Access Analyzer Consoles are using the same SQL Server database, -every console using the database must also be updated. The act of connecting a Access Analyzer +In environments where multiple Access Analyzer Consoles use the same SQL Server database, +you must also update every console that uses the database. The act of connecting a Access Analyzer Console with a newer version to a database updates the database’s schema pursuant to the new definition. If a Access Analyzer Console with an older version connects to the same database after -the schema has been updated, corruption to Access Analyzer’s system tables can result. +you update the schema, corruption to Access Analyzer’s system tables can result. SQL Server Supported Version Change for the Access Analyzer Database With the release of Access Analyzer v12.0, SQL Server 2016 through SQL Server 2022 are the supported versions for the Access Analyzer database. -To grant access to additional Solutions in an existing Access Analyzer installation, a new license -key is required. To update the Access Analyzer license key without installing a new version of the +To grant access to additional Solutions in an existing Access Analyzer installation, you need a new +license key. To update the Access Analyzer license key without installing a new version of the Access Analyzer Console, see the [Update License Key](/docs/accessanalyzer/12.0/install/application/updatelicense.md) topic for instructions. **License Key Changes** -The following changes in licensing requires the organization needing a new key: +The following licensing changes require the organization to obtain a new key: - Access Analyzer v12.0 - - No additional licenses are required for this version + - This version doesn't require additional licenses - Enterprise Auditor v11.6 - - No additional licenses are required for this version + - This version doesn't require additional licenses - StealthAUDIT v11.5 - - No additional licenses are required for this version + - This version doesn't require additional licenses See the [Update License Key](/docs/accessanalyzer/12.0/install/application/updatelicense.md) section for instructions on updating the license key. diff --git a/docs/accessanalyzer/12.0/install/application/upgrade/solutionconsiderations.md b/docs/accessanalyzer/12.0/install/application/upgrade/solutionconsiderations.md index 3f06ab8f3c..2747278ea5 100644 --- a/docs/accessanalyzer/12.0/install/application/upgrade/solutionconsiderations.md +++ b/docs/accessanalyzer/12.0/install/application/upgrade/solutionconsiderations.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Solution Upgrade Considerations -The following items must be taken into consideration for upgrades: +Consider the following items for upgrades: **Access Information Center** @@ -23,7 +23,7 @@ instructions. **Sensitive Data Discovery** -- In Access Analyzer 12.0 the Sensitive Data Discovery features are included in the standard +- Access Analyzer 12.0 includes the Sensitive Data Discovery features in the standard installations when your license includes it. If you have the old Sensitive Data Discovery Add-On installed from a previous Access Analyzer version, then you must manually uninstall it from the Access Analyzer Console server, and any File System proxy and SharePoint Agent servers where it is @@ -31,18 +31,18 @@ instructions. :::warning The new global settings will overwrite any previously configured criteria. Make a - note of any configured Sensitive Data Criteria before upgrading Access Analyzer. Sensitive Data - Criteria must be reconfigured after an upgrade. + note of any configured Sensitive Data Criteria before upgrading Access Analyzer. You must + reconfigure Sensitive Data Criteria after an upgrade. ::: -- Sensitive Data Criteria selection is configured globally and used by default in all solution sets. +- You configure Sensitive Data Criteria selection globally, and Access Analyzer uses it by default in all solution sets. See the [Configure Global Sensitive Data Settings](#configure-global-sensitive-data-settings) for additional information. **Active Directory Solution Considerations** -- The Active Directory solution by default upgrades as **Upgrade in Place**. Do not change this +- The Active Directory solution by default upgrades as **Upgrade in Place**. Don't change this upgrade option. After completing the upgrade, you need to manually add the new **Active Directory** > **7. Certificate Authority** job group from the `InstantSolutions` directory. - For Activity – Ensure the Netwrix Activity Monitor is a compatible version. See the Upgrade @@ -52,7 +52,7 @@ instructions. **File System Solution Considerations** -- For Proxy Mode as a Service – File System Proxy Service needs to be updated on the proxy servers. +- For Proxy Mode as a Service – You need to update the File System Proxy Service on the proxy servers. See the [Upgrade Proxy Service Procedure](/docs/accessanalyzer/12.0/install/filesystemproxy/upgrade.md) topic for instructions. - For Activity – Ensure the Netwrix Activity Monitor is a compatible version. See the Upgrade @@ -62,8 +62,8 @@ instructions. **SharePoint Solution Considerations** -- For SharePoint Agent – Access Analyzer SharePoint Agent needs to be updated on the SharePoint - server where it was installed. See the +- For SharePoint Agent – You need to update the Access Analyzer SharePoint Agent on the SharePoint + server where you installed it. See the [Upgrade SharePoint Agent](/docs/accessanalyzer/12.0/install/sharepointagent/upgrade.md) section for instructions. - For Activity – Ensure the Stealthbits Activity Monitor is a compatible version. See the Upgrade Instructions in the @@ -85,7 +85,7 @@ After upgrading to Access Analyzer 12.0, run the latest version of the **File Sy **0.Collection** > **0-Create Schema** job to migrate the File System Solution to the latest database schema. -This database schema migration should be performed before running other jobs in the File System +Perform this database schema migration before running other jobs in the File System Solution after upgrading to Access Analyzer 12.0. See the [File System Solution](/docs/accessanalyzer/12.0/solutions/filesystem/overview.md) topic for additional @@ -95,36 +95,35 @@ information. :::warning The new global Settings will overwrite any previously configured criteria. Make a note -of any configured Sensitive Data Criteria before commencing the upgrade Access Analyzer. Sensitive -Data Criteria must be reconfigured after an upgrade. +of any configured Sensitive Data Criteria before upgrading Access Analyzer. You must reconfigure +Sensitive Data Criteria after an upgrade. ::: -If Sensitive Data Criteria are configured differently for each solution, re-configure the criteria +If you configure Sensitive Data Criteria differently for each solution, re-configure the criteria selection at the solution level. See the topic for the applicable solution for additional information. -If the same Sensitive Data Criteria are used for all solutions, configure the criteria selection at -the global **Settings** > **Sensitive Data** node, which will then be used by default in all +If you use the same Sensitive Data Criteria for all solutions, configure the criteria selection at +the global **Settings** > **Sensitive Data** node, which Access Analyzer then uses by default in all solutions. The Sensitive Data node provides configuration options to manage Sensitive Data Criteria and false positive exclusion filters. See the [Sensitive Data](/docs/accessanalyzer/12.0/admin/settings/sensitivedata/overview.md) topic for additional information. -Follow the steps to configure Sensitive Data Criteria at the global level. +To configure Sensitive Data Criteria at the global level: ![Global Settings Sensitive Data node](/images/accessanalyzer/12.0/install/application/upgrade/sensitivedata.webp) -**Step 1 –** If the same Sensitive Data Criteria are used for all solutions, configure the criteria -selection at the global Settings level, which will then be used by default in all solution sets. +**Step 1 –** If you use the same Sensitive Data Criteria for all solutions, configure the criteria +selection at the global Settings level, which Access Analyzer then uses by default in all solution sets. Navigate to the **Settings** > **Sensitive Data** node and click **Add** to open the Select Criteria window. ![Sensitive Data Select Criteria window](/images/accessanalyzer/12.0/install/application/upgrade/selectcriteria.webp) -**Step 2 –** Select the desired criteria. Use the **Search Criteria** text field to filter the list +**Step 2 –** Select the criteria you want. Use the **Search Criteria** text field to filter the list using keywords or expand each category to view and select individual Sensitive Data search criteria, then click **OK**. -By default, Sensitive Data Criteria configured at the global Settings level is inherited down to the -applicable solutions. +By default, applicable solutions inherit the Sensitive Data Criteria configured at the global Settings level. diff --git a/docs/accessanalyzer/12.0/install/application/upgrade/wizard.md b/docs/accessanalyzer/12.0/install/application/upgrade/wizard.md index 7ea88c9e50..43a78a8544 100644 --- a/docs/accessanalyzer/12.0/install/application/upgrade/wizard.md +++ b/docs/accessanalyzer/12.0/install/application/upgrade/wizard.md @@ -7,19 +7,19 @@ sidebar_position: 20 # Access Analyzer Core Upgrade Instructions :::warning -If Role Based Access has been enabled, a user with the Administrator role must perform -the upgrade. Other user roles do not have the necessary permissions to perform upgrades. +If you have enabled Role Based Access, a user with the Administrator role must perform +the upgrade. Other user roles don't have the necessary permissions to perform upgrades. ::: -Follow the steps to upgrade to Access Analyzer 12.0 on the same server where an older version of +Upgrade to Access Analyzer 12.0 on the same server where an older version of Access Analyzer is installed. :::note -If any customizations have been done by a Netwrix Engineer, please ensure the custom work -is not lost during the upgrade process. While using the Upgrade Wizard, customizations are archived -prior to solution upgrades. These archives are available after the solution upgrades have been -completed. Contact [Netwrix Support](https://www.netwrix.com/support.html) for additional +If a Netwrix Engineer has made any customizations, ensure the custom work +isn't lost during the upgrade process. The Upgrade Wizard archives customizations +before solution upgrades. These archives are available after the solution upgrades +complete. Contact [Netwrix Support](https://www.netwrix.com/support.html) for additional information. ::: @@ -41,44 +41,44 @@ files, and reports remain in the installation directory after the uninstall proc :::note If you have the old Netwrix Sensitive Data Discovery Add-On installed, you must uninstall -it before continuing with this upgrade. For Access Analyzer 12.0, Sensitive Data Discovery is -installed as part of the main installation if your license includes it. +it before continuing with this upgrade. For Access Analyzer 12.0, the main installation includes +Sensitive Data Discovery if your license includes it. ::: -- The `WebServer.exe.config` file is automatically retained in a Backup folder created under the Web - folder of the installation directory. Any custom application settings contained in this file are - kept as part of this upgrade process. +- The installer automatically retains the `WebServer.exe.config` file in a Backup folder under the Web + folder of the installation directory and keeps any custom application settings in this file as + part of this upgrade process. ![Setup Wizard Welcome page](/images/accessanalyzer/12.0/install/application/welcome.webp) **Step 2 –** Install Access Analyzer 12.0. See the [Access Analyzer Core Installation](/docs/accessanalyzer/12.0/install/application/wizard.md) topic for detailed instructions. -- Before installation, ensure the new `StealthAUDIT.lic` license file is stored locally on the - Access Analyzer Console in order to be referenced during the installation process -- Access Analyzer is installed to the following directory by default: `…\STEALTHbits\StealthAUDIT` +- Before installation, store the new `StealthAUDIT.lic` license file locally on the + Access Analyzer Console so the installer can reference it during the installation process +- The installer installs Access Analyzer to the following directory by default: `…\STEALTHbits\StealthAUDIT` - If another installation path is designated, please be sure to leave `STEALTHbits\StealthAUDIT` + If another installation path is designated, be sure to leave `STEALTHbits\StealthAUDIT` as the path suffix in the installation wizard. -- During the installation, any customizations to the settings in the `WebServer.exe.config` file are - automatically restored from the backup file retained when installing the previous version. The - `../Web/Backup` folder is deleted after the settings have been restored. +- During the installation, the installer automatically restores any customizations to the settings + in the `WebServer.exe.config` file from the backup file retained when installing the previous + version. The installer deletes the `../Web/Backup` folder after it restores the settings. -After the installation is completed, the upgrade wizard launches from the Access Analyzer desktop +After the installation completes, the upgrade wizard launches from the Access Analyzer desktop icon. ## Upgrade Wizard -Once the Access Analyzer installation process is complete, it is necessary to go through the Upgrade +After the Access Analyzer installation process is complete, go through the Upgrade Wizard. There are three Upgrade options for a solution: - Full Upgrade – Performs a full synchronization of the directory and file structure of the solution to mirror the Instant Solution - Upgrade in place – Performs file content updates of jobs matching the Instant Solutions but does not change the Jobs tree structure -- Do not upgrade – No upgrade is performed, leaving the previous version of the solution +- Don't upgrade – Performs no upgrade, leaving the previous version of the solution The default settings configured within the Advanced Upgrade Options window align with the best practices of the Netwrix Professional Services and Support teams. @@ -90,25 +90,25 @@ Upgrade action is set to **Full Upgrade** or **Upgrade in place**: | -------- | ----------------------------------------------------------------------------------- | -------------------- | ------------------------ | | Normal | Job exists in Locked state and has matching ID in Instant Solutions | Upgrade | Upgrade | | New | Job exists in Instant Solutions but not in the Jobs tree for an existing solution | Install | Install | -| Removed | Job exists in Locked state in the Jobs tree but does not exist in Instant Solutions | Delete | Nothing | +| Removed | Job exists in Locked state in the Jobs tree but doesn't exist in Instant Solutions | Delete | Nothing | | Copied | Original job exists in original location, but multiple instances of the job exists | Delete | Upgrade | | Moved | Original job exists but in a different location than in the Instant Solutions | Move & Upgrade | Upgrade | | Renamed | Job found via ID match but was renamed | Rename & Upgrade | Upgrade | | Conflict | Changes have been made to the job | Overwrite | Overwrite | -Conflicts are identified when customizations have been made by either a user or a Netwrix engineer. -Conflicts need to be either resolved prior to the upgrade action or manually applied after the -upgrade is complete. Conflict resolution can be done on the Changes window by undoing a -customization. However, if the conflict is undone prior to a solution upgrade, then the -customization will not be archived. +The Upgrade Wizard identifies conflicts when a user or a Netwrix engineer has made customizations. +You need to either resolve conflicts before the upgrade action or manually apply them after the +upgrade is complete. You can resolve conflicts on the Changes window by undoing a +customization. However, if you undo the conflict before a solution upgrade, the +Upgrade Wizard will not archive the customization. :::warning -If Role Based Access has been enabled, a user with the Administrator role must perform -the upgrade. Other user roles do not have the necessary permissions to perform upgrades. +If you have enabled Role Based Access, a user with the Administrator role must perform +the upgrade. Other user roles don't have the necessary permissions to perform upgrades. ::: -Follow the steps to use the Upgrade Wizard. +Use the Upgrade Wizard: **Step 1 –** Launch the Access Analyzer application. The installation wizard placed the Access Analyzer icon on the desktop. @@ -118,17 +118,17 @@ Analyzer icon on the desktop. **Step 2 –** The Access Analyzer Configuration Wizard opens. Click **Next** to continue. :::note -When Access Analyzer12.0 is installed on a server where a previous version of Access -Analyzer had been installed, the Version Selection page of the Configuration Wizard will not appear. +When you install Access Analyzer 12.0 on a server that already has a previous version of Access +Analyzer installed, the Version Selection page of the Configuration Wizard doesn't appear. ::: ![Configuration Wizard Solution Set Files page with conflicts](/images/accessanalyzer/12.0/install/application/upgrade/solutionsetfiles.webp) -**Step 3 –** On the Solution Set Files page, only upgrade conflicts are displayed by default. +**Step 3 –** By default, the Solution Set Files page displays only upgrade conflicts. :::info -Investigate the changes where conflicts have been identified before proceeding. +Investigate the changes where the Upgrade Wizard has identified conflicts before proceeding. ::: @@ -143,31 +143,31 @@ Additional options include: ![View conflicts in the Changes window](/images/accessanalyzer/12.0/install/application/upgrade/changes.webp) -**Step 5 –** (Optional) Conflicts can be resolved on the Changes window, which is opened by the -**View conflicts** button. Remember, if the conflict is resolved prior to a solution upgrade, then -the customization will not be archived. To resolve a conflict, select it from the list and click -**Undo**. +**Step 5 –** (Optional) You can resolve conflicts on the Changes window, which the +**View conflicts** button opens. Remember, if you resolve the conflict before a solution upgrade, +the Upgrade Wizard will not archive the customization. To resolve a conflict, select it from the +list and click **Undo**. -**Step 6 –** When the Upgrade options have been set as desired. Click **Next**. +**Step 6 –** When you have set the Upgrade options as desired, click **Next**. ![Configuration wizard Options page](/images/accessanalyzer/12.0/install/application/upgrade/options.webp) -**Step 7 –** On the Options page, select whether to send usage statistics to Netwrix to help us -improve our product. After the Usage Statistics option is set as desired, click **Next** to +**Step 7 –** On the Options page, select whether to send usage statistics to Netwrix to help +improve the product. After you set the Usage Statistics option as desired, click **Next** to continue. -- If selected, usage statistics are collected and sent to Netwrix +- If selected, Access Analyzer collects usage statistics and sends them to Netwrix - - Upon startup of the Access Analyzer console, the system checks if usage statistics have been - sent in the last 7 days. If they have not been, stored procedures run against the Access + - Upon startup of the Access Analyzer console, the system checks whether it has sent usage + statistics in the last 7 days. If it hasn't, stored procedures run against the Access Analyzer database and gather data about job runs, access times, and environmental details like - resource counts, users counts, number of exceptions, and so on. This data is then sent back to - Netwrix to help us identify usage trends and common pain points, so that we can use this - information to improve the product. - - Only anonymous statistic-level data is included. No private company or personal data is - collected or sent to Netwrix. + resource counts, users counts, number of exceptions, and so on. The system then sends this + data back to Netwrix to identify usage trends and common problem areas, which Netwrix uses to + improve the product. + - Access Analyzer includes only anonymous statistic-level data. It doesn't collect or send any + private company or personal data to Netwrix. -- If cleared, no usage statistics are collected or sent to Netwrix +- If cleared, Access Analyzer doesn't collect or send usage statistics to Netwrix ![Configuration Wizard Progress page](/images/accessanalyzer/12.0/install/application/upgrade/progress.webp) diff --git a/docs/accessanalyzer/12.0/install/application/wizard.md b/docs/accessanalyzer/12.0/install/application/wizard.md index 9c831184e3..ab5a034496 100644 --- a/docs/accessanalyzer/12.0/install/application/wizard.md +++ b/docs/accessanalyzer/12.0/install/application/wizard.md @@ -7,8 +7,7 @@ sidebar_position: 20 # Access Analyzer Core Installation Save the organization’s Access Analyzer license key, received from your Netwrix Sales -Representative, to the server where Access Analyzer is to be installed. Then follow the steps to -install Access Analyzer. +Representative, to the server where you will install Access Analyzer. :::note The process explained in this topic assumes that both the downloaded binary and the @@ -17,8 +16,8 @@ license (.lic) file are located on the server which will become the Access Analy :::warning -If User Account Control (UAC) is enabled on the server, ensure the installation package -is run in Administrative/privilege mode. +If User Account Control (UAC) is enabled on the server, ensure you run the installation package +in Administrative/privilege mode. ::: @@ -49,7 +48,7 @@ install Access Analyzer. The default destination folder is file. When the path to the file is visible in the textbox, click **Next**. :::note -The license file must be stored on the Access Analyzer Console server before the +You must store the license file on the Access Analyzer Console server before the installation begins. ::: @@ -58,7 +57,7 @@ installation begins. **Step 6 –** The License Features page displays a list of all features covered by the imported license. It also displays the name of the organization which owns the license, the expiration date, -and the host limit. These are the features that will be installed. Click **Next**. +and the host limit. These are the features the installer will install. Click **Next**. ![Ready to install Netwrix Access Governance page](/images/accessanalyzer/12.0/install/application/ready.webp) @@ -69,6 +68,6 @@ installation. **Step 8 –** When the installation has completed, click **Finish** to exit the wizard. -The Access Analyzer Console has been installed, and two desktop icons have been created: Access -Analyzer and Published Reports. Launch the Access Analyzer application to complete the initial -configuration. +You have now installed the Access Analyzer Console, and the installer has created two desktop +icons: Access Analyzer and Published Reports. Launch the Access Analyzer application to complete +the initial configuration. diff --git a/docs/accessanalyzer/12.0/install/filesystemproxy/configuredatacollector.md b/docs/accessanalyzer/12.0/install/filesystemproxy/configuredatacollector.md index 3333a8f02c..32bb63c444 100644 --- a/docs/accessanalyzer/12.0/install/filesystemproxy/configuredatacollector.md +++ b/docs/accessanalyzer/12.0/install/filesystemproxy/configuredatacollector.md @@ -12,7 +12,7 @@ Access Auditor Data Collector Wizard from the job’s query. On the Applet Settings wizard page, select the following option: -- Require applet to be running as service on target – Must be selected in the Applet Launch +- Require applet to be running as service on target – Select this option in the Applet Launch Mechanism section to prevent the deployment of the applet or the ad hoc installation of the service during the scan diff --git a/docs/accessanalyzer/12.0/install/filesystemproxy/overview.md b/docs/accessanalyzer/12.0/install/filesystemproxy/overview.md index f11962eaca..1bc291c52b 100644 --- a/docs/accessanalyzer/12.0/install/filesystemproxy/overview.md +++ b/docs/accessanalyzer/12.0/install/filesystemproxy/overview.md @@ -6,20 +6,20 @@ sidebar_position: 20 # File System Proxy as a Service Overview -The File System Solution can be enabled to use proxy servers for scanning targeted file systems in +You can enable the File System Solution to use proxy servers for scanning targeted file systems in very large or widely dispersed environments. -When File System scans are run in proxy mode as a service, there are two methods available for +When you run File System scans in proxy mode as a service, two methods are available for deploying the service: -- Pre-Installed File System Proxy Service – File System Proxy Service installation package must be - installed on the Windows proxy servers prior to executing the scans. This is the recommended +- Pre-Installed File System Proxy Service – You must install the File System Proxy Service + installation package on the Windows proxy servers before executing the scans. This is the recommended method. -- Ad Hoc File System Proxy Service Deployment – File System Proxy Service is installed on the - Windows proxy server when the job is executed +- Ad Hoc File System Proxy Service Deployment – Access Analyzer installs the File System Proxy + Service on the Windows proxy server when the job runs -The data collection processing is conducted by the proxy server where the service is running and -leverages a local mode-type scan to each of the target hosts. The final step in data collection is +The proxy server where the service is running conducts the data collection processing and +uses a local mode-type scan to each of the target hosts. The final step in data collection is to compress and transfer the data collected in the SQLite databases, or Tier 2 databases, back to the Access Analyzer Console server. @@ -33,7 +33,7 @@ the required prerequisites. ## Supported Platforms -The File System Proxy Service for the Access Analyzer File System Solution can be installed on the +You can install the File System Proxy Service for the Access Analyzer File System Solution on the following Windows operating systems: - Windows Server 2022 @@ -42,15 +42,15 @@ following Windows operating systems: ## Proxy Scanning Architecture -Access Analyzer is configured by default to process data collection against ten target hosts -simultaneously. When File System scans are run in local mode ten hosts process simultaneously, and -processing against the eleventh host begins after the processing against the first host is -completed. Proxy scanning architecture supports large deployments or widely dispersed environments. +By default, Access Analyzer processes data collection against ten target hosts +simultaneously. When you run File System scans in local mode, ten hosts process simultaneously, and +processing against the eleventh host begins after the processing against the first host +completes. Proxy scanning architecture supports large deployments or widely dispersed environments. -A proxy server is any server that can be leveraged to process data collection against target hosts. +A proxy server is any server that can process data collection against target hosts. :::warning -The File System Proxy Service cannot be installed on the same server as Access +You can't install the File System Proxy Service on the same server as Access Analyzer. ::: @@ -62,38 +62,38 @@ Two options are available for implementing the proxy scanning architecture: ### Proxy Mode with Applet -When File System scans are run in proxy mode with applet, it means the File System applet is -deployed to the Windows proxy server when the job is executed to conduct data collection. The data -collection processing is initiated by the proxy server where the applet is deployed and leverages a +When you run File System scans in proxy mode with applet, Access Analyzer deploys the File System +applet to the Windows proxy server when the job runs to conduct data collection. The proxy server +where the applet is deployed initiates the data collection processing and uses a local mode-type scan to each of the target hosts. The final step in data collection is to compress and transfer the data collected in the SQLite databases, or Tier 2 databases, back to the Access Analyzer Console server. ![Diagram of Enterprise Auditor server sending an FSAA applet to a proxy server](/images/accessanalyzer/12.0/install/filesystemproxy/proxymodewithapplet.webp) -The diagram illustrates the Access Analyzer server sending an FSAA applet to a proxy server, which +The diagram illustrates the Access Analyzer server sending a FileSystemAccess (FSAA) applet to a proxy server, which runs the scan against a file server, and then returns data to the Access Analyzer server. ### Proxy Mode as a Service -When File System scans are run in proxy mode as a service, there are two methods available for +When you run File System scans in proxy mode as a service, two methods are available for deploying the service: -- Pre-Installed File System Proxy Service – File System Proxy Service installation package must be - installed on the Windows proxy servers prior to executing the scans. This is the recommended +- Pre-Installed File System Proxy Service – You must install the File System Proxy Service + installation package on the Windows proxy servers before executing the scans. This is the recommended method. -- Ad Hoc File System Proxy Service Deployment – File System Proxy Service is installed on the - Windows proxy server when the job is executed +- Ad Hoc File System Proxy Service Deployment – Access Analyzer installs the File System Proxy + Service on the Windows proxy server when the job runs -The data collection processing is conducted by the proxy server where the service is running and -leverages a local mode-type scan to each of the target hosts. The final step in data collection is +The proxy server where the service is running conducts the data collection processing and +uses a local mode-type scan to each of the target hosts. The final step in data collection is to compress and transfer the data collected in the SQLite databases, or Tier 2 databases, back to the Access Analyzer Console server. -The proxy communication is configured during the installation of the service on the proxy server and -certificate exchange options are configured via the Applet Settings page of the File System Access -Auditing Data Collector Wizard. The credential provided for the secure communications in the -installation wizard is also added to the Access Analyzer Connection Profile assigned to the File +You configure the proxy communication during the installation of the service on the proxy server, and +you configure certificate exchange options via the Applet Settings page of the File System Access +Auditing Data Collector Wizard. The installation wizard also adds the credential provided for the +secure communications to the Access Analyzer Connection Profile assigned to the File System Solution. See the [File System Proxy Service Installation](/docs/accessanalyzer/12.0/install/filesystemproxy/wizard.md) topic for additional information. @@ -104,25 +104,25 @@ The diagram illustrates the Access Analyzer server communicating securely with t a proxy server, which runs the scan against a file server, collecting the data locally and securely. Then the proxy service returns data securely to the Access Analyzer server. -When a proxy mode scan is initiated from the Access Analyzer Console, it will distribute hosts to be -scanned across all proxy hosts. Access Analyzer monitors the scans from the central console. Once -all proxy hosts have completed scanning, all results and SQLite databases are returned to the Access -Analyzer Console server. +When you initiate a proxy mode scan from the Access Analyzer Console, Access Analyzer distributes hosts +for scanning across all proxy hosts. Access Analyzer monitors the scans from the central console. Once +all proxy hosts have completed scanning, Access Analyzer returns all results and SQLite databases to +the Access Analyzer Console server. ![Diagram of difference between an implementation with and without proxy servers](/images/accessanalyzer/12.0/install/filesystemproxy/fsaaproxyarchitecture.webp) The diagram shows the difference between an implementation of Access Analyzer without proxy servers (on the left) and with proxy servers (on the right). On the right side of the diagram, the scans -have been configured to use the local host and two additional proxy servers to perform the FSAA Data +use the local host and two additional proxy servers to perform the FSAA Data Collector scans. This allows it to execute three times as many concurrent hosts than would be possible without proxy servers. This provides a clear benefit in scalability and scan times. The proxy functionality for the FSAA Data Collector provides security and reliability. :::tip -Remember, It is recommended that the File System Proxy Service is installed on the proxy server -before running File System scans in proxy mode as a service. Once installed, the FileSystemAccess -(FSAA) Data Collector must be configured to use the service. See the +Install the File System Proxy Service on the proxy server before running File System scans in +proxy mode as a service. After installation, you must configure the FileSystemAccess +(FSAA) Data Collector to use the service. See the [File System Data Collection Configuration for Proxy as a Service](/docs/accessanalyzer/12.0/install/filesystemproxy/configuredatacollector.md) topic for additional information. ::: @@ -130,7 +130,7 @@ for additional information. ## Sensitive Data Discovery Auditing Consideration -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the minimum amount -of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. By default, SDD scans are -configured to run two concurrent threads. For example, if the job is configured to scan 8 hosts at a -time with two concurrent SDD threads, then an extra 32 GB of RAM are required (8x2x2=32). +If you run Sensitive Data Discovery (SDD) scans, you must increase the minimum amount +of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. By default, SDD scans +run two concurrent threads. For example, if you configure the job to scan 8 hosts at a +time with two concurrent SDD threads, you need an extra 32 GB of RAM (8x2x2=32). diff --git a/docs/accessanalyzer/12.0/install/filesystemproxy/silentinstall.md b/docs/accessanalyzer/12.0/install/filesystemproxy/silentinstall.md index 55b9bd0a51..02c0e1098b 100644 --- a/docs/accessanalyzer/12.0/install/filesystemproxy/silentinstall.md +++ b/docs/accessanalyzer/12.0/install/filesystemproxy/silentinstall.md @@ -6,12 +6,12 @@ sidebar_position: 30 # Silent Installer Option for Proxy -It is possible to use one of the following methods to complete a silent installation of the File +Use one of the following methods to complete a silent installation of the File System Proxy Service. :::warning For all Active Directory versions, aside from Windows 2012 R2, the silent installer -does not prompt an error message if a duplicate SPN value exists in the targeted domain for +doesn't prompt an error message if a duplicate SPN value exists in the targeted domain for [Option 1: Run as LocalSystem](#option-1-run-as-localsystem). Having duplicate SPN’s in the targeted Active Directory environment prohibits connection to the proxy service, resulting in a failed scan. ::: @@ -21,16 +21,16 @@ If a desired SPN already exists in a Windows 2012 R2 domain, the silent installe following message: > _There is a problem with this Windows Installer package. A script required for this install to -> complete could not be run. Contact your support personnel or package vendor_. +> complete couldn't be run. Contact your support personnel or package vendor_. To resolve the problem, remove the duplicate SPN value and rerun the installer to complete -installation. For any additional issues, verbose logging is included in the silent installer and +installation. For any additional issues, the silent installer includes verbose logging and creates an `install.txt` file on the desktop. ## Option 1: Run as LocalSystem -Follow the steps to install the File System Proxy Service on the targeted proxy servers with a -silent installer. +Install the File System Proxy Service on the targeted proxy servers with a +silent installer: **Step 1 –** Copy the `FileSystemProxy.msi` executable to the desktop of the server designated as the proxy server. @@ -43,7 +43,7 @@ msiexec /i FileSystemProxy.msi /qb /l*v install.log SVC_ACCOUNT_TYPE=SYSTEM - To add a non-default install directory, append `PRODUCTDIR="[path]"` to the command. - - `path` – The path to the desired installation directory and must include + - `path` – The installation directory path, which must include `...\STEALTHbits\StealthAUDIT\FSAA\...` For example: @@ -52,12 +52,12 @@ msiexec /i FileSystemProxy.msi /qb /l*v install.log SVC_ACCOUNT_TYPE=SYSTEM msiexec /i FileSystemProxy.msi /qb /l*v install.log SVC_ACCOUNT_TYPE=SYSTEM PRODUCTDIR="E:\STEALTHbits\StealthAUDIT\FSAA" ``` -The SPN value is automatically added to the computer object in Active Directory with this option. +This option automatically adds the SPN value to the computer object in Active Directory. ## Option 2: Run as a Service Account -Follow the steps to install the File System Proxy Service on the targeted proxy servers with a -silent installer. +Install the File System Proxy Service on the targeted proxy servers with a +silent installer: **Step 1 –** Copy the `FileSystemProxy.exe` executable to the desktop of the server designated as the proxy server. @@ -71,11 +71,11 @@ msiexec /i FileSystemProxy.msi /qb /l*v install.log SVC_ACCOUNT_TYPE=DOMAIN SVC_ - `DOMAIN\USERNAME` – The service account credentials, which need to be a member the Local Administrators group and have the**Log on as a service** local policy  (**Local Policies** > **User Rights Assignment**) -- `secret` – The password for the credentials provided above (within quotes) +- `secret` – The password for the `DOMAIN\USERNAME` credentials (within quotes) - To add a non-default install directory, append `PRODUCTDIR="[path]"` to the command. - - `path` – The path to the desired installation directory and must include + - `path` – The installation directory path, which must include `...\STEALTHbits\StealthAUDIT\FSAA\...` For example: diff --git a/docs/accessanalyzer/12.0/install/filesystemproxy/troubleshooting.md b/docs/accessanalyzer/12.0/install/filesystemproxy/troubleshooting.md index 5290b9ce4c..12bdb3d794 100644 --- a/docs/accessanalyzer/12.0/install/filesystemproxy/troubleshooting.md +++ b/docs/accessanalyzer/12.0/install/filesystemproxy/troubleshooting.md @@ -10,21 +10,20 @@ The following are potential errors that may occur during installation and how to | Error Message | Resolution | | ----------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Service ‘Access Analyzer FSAA Proxy Scanner’ (StealthAUDITFSAA) failed to start. Verify that you have sufficient privileges to start system services. | The domain account used during setup does not have sufficient privileges to start the service. Open Local Security Policies on the proxy server. In User Rights Assignment under Local policies, add the desired user to the Log on as a service policy. Once the user has this privilege, retry the installation. | +| Service ‘Access Analyzer FSAA Proxy Scanner’ (StealthAUDITFSAA) failed to start. Verify that you have sufficient privileges to start system services. | The domain account used during setup doesn't have sufficient privileges to start the service. Open Local Security Policies on the proxy server. In User Rights Assignment under Local policies, add the user to the Log on as a service policy. After the user has this privilege, retry the installation. | The following are potential errors that may occur during File System scans and how to resolve each. | Error Message | Resolution | | --------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Failed to launch SDD client (2): The system cannot find the file specified. | This indicates the Sensitive Data Discovery Add-On is not installed on the proxy server. | -| Error creating DLP components. Error:Error initializing DLP communications, received invalid pipe handle. | This indicates the Sensitive Data Discovery Add-On is not installed on the proxy server. | -| Unable to start scan: Could not initialize scan session with any proxy host supplied | This can indicate a few things and is a broad error:
  • The Access Analyzer Console cannot reach the proxy server via the network.
  • Network communications are blocked for TCP on port 8766 – possibly by the Windows Firewall on the Access Analyzer Console server or proxy server, or by another firewall in the network (it is possible for this port to be customized through the FSAA Data Collector query configuration).
  • The Netwrix Access Analyzer (formerly Enterprise Auditor) FSAA Proxy Scanner service is not running or is not installed on the target proxy server.
| +| Failed to launch SDD client (2): The system can't find the file specified. | This indicates the Sensitive Data Discovery Add-On isn't installed on the proxy server. | +| Error creating DLP components. Error:Error initializing DLP communications, received invalid pipe handle. | This indicates the Sensitive Data Discovery Add-On isn't installed on the proxy server. | +| Unable to start scan: Couldn't initialize scan session with any proxy host supplied | This can indicate a few things and is a broad error:
  • The Access Analyzer Console can't reach the proxy server via the network.
  • Network communications are blocked for TCP on port 8766 – possibly by the Windows Firewall on the Access Analyzer Console server or proxy server, or by another firewall in the network (you can customize this port through the FSAA Data Collector query configuration).
  • The Netwrix Access Analyzer (formerly Enterprise Auditor) FSAA Proxy Scanner service isn't running or isn't installed on the target proxy server.
| ## Verbose Logging -Sometimes it is necessary to enable verbose logging in order to troubleshoot a problem with the -proxy server. +Enable verbose logging to troubleshoot a problem with the proxy server. Run the following command in the directory where the installer lives (to prompt the install): diff --git a/docs/accessanalyzer/12.0/install/filesystemproxy/uninstall.md b/docs/accessanalyzer/12.0/install/filesystemproxy/uninstall.md index cc332f88c8..0d15e7cd16 100644 --- a/docs/accessanalyzer/12.0/install/filesystemproxy/uninstall.md +++ b/docs/accessanalyzer/12.0/install/filesystemproxy/uninstall.md @@ -6,8 +6,8 @@ sidebar_position: 50 # Uninstall Proxy Service Process -The process to properly uninstall the File System Proxy Service is completed through the -uninstalling of the Access Analyzer File System Scanning Proxy program. +To properly uninstall the File System Proxy Service, uninstall the Access Analyzer File System +Scanning Proxy program. **Step 1 –** Open Control Panel and select **Programs** > **Uninstall a program**. @@ -17,12 +17,12 @@ uninstalling of the Access Analyzer File System Scanning Proxy program. and click **Uninstall**. :::note -If the installation was configured to use the LocalSystem account to run the RPC service -the two SPN values are removed for that machine in Active Directory. If the service is running with -a supplied account, the SPN values would need to be manually removed for that machine in Active -Directory (unless the uninstall was completed as part of the +If you configured the installation to use the LocalSystem account to run the RPC service, +the uninstaller removes the two SPN values for that machine in Active Directory. If the service is +running with a supplied account, you must manually remove the SPN values for that machine in Active +Directory (unless you completed the uninstall as part of the [Upgrade Proxy Service Procedure](/docs/accessanalyzer/12.0/install/filesystemproxy/upgrade.md)). ::: -When the uninstall process is complete, this program is removed from the list. +When the uninstall process is complete, the program no longer appears in the list. diff --git a/docs/accessanalyzer/12.0/install/filesystemproxy/upgrade.md b/docs/accessanalyzer/12.0/install/filesystemproxy/upgrade.md index 367817fb06..29058dad16 100644 --- a/docs/accessanalyzer/12.0/install/filesystemproxy/upgrade.md +++ b/docs/accessanalyzer/12.0/install/filesystemproxy/upgrade.md @@ -6,9 +6,9 @@ sidebar_position: 40 # Upgrade Proxy Service Procedure -When the Access Analyzer Console and File System Solution are upgraded, it is necessary to also -upgrade the File System Proxy Service when running Access Analyzer in Proxy Mode as a Service. This -upgrade can be done in two ways: +When you upgrade the Access Analyzer Console and File System Solution, also +upgrade the File System Proxy Service when running Access Analyzer in Proxy Mode as a Service. You +can do this upgrade in two ways: - Automatically – An instant job within the Access Analyzer Console - Manually – On each server hosting the proxy service @@ -16,21 +16,21 @@ upgrade can be done in two ways: :::warning When upgrading the Proxy Service to 11.6 from a previous version for the first time, you must manually uninstall the previous version and follow the [Manual Upgrade](#manual-upgrade) -steps below. Subsequent 11.6 upgrades can be done using the automatic upgrade option. +steps. You can do subsequent 11.6 upgrades using the automatic upgrade option. ::: :::note If you have the old Netwrix Sensitive Data Discovery Add-On installed, you must uninstall -it before continuing with this upgrade. For Access Analyzer 12.0, Sensitive Data Discovery is -installed as part of the main installation if your license includes it. +it before continuing with this upgrade. For Access Analyzer 12.0, the main installation includes +Sensitive Data Discovery if your license includes it. ::: ## Automatic Upgrade The **FS_UpdateProxy** Job is available through the Instant Job Wizard. This job updates the File -System Proxy Service on all servers in the assigned host list. Follow the steps to instantiate this +System Proxy Service on all servers in the assigned host list. Instantiate this job. **Step 1 –** Within the **Jobs** tree, right-click and select **Add Instant Job**. The Instant Job @@ -46,15 +46,15 @@ Expand the category and select the **FS_UpgradeProxy** Job. Click **Next**. **Step 4 –** On the Host Assignment page, select the **Specify individual hosts or host lists** option and click **Next**. -**Step 5 –** On the Host Lists page, assign the host lists containing the proxy servers to be -updated . Multiple host lists can be added. Click Next. +**Step 5 –** On the Host Lists page, assign the host lists containing the proxy servers you want to +update. You can add multiple host lists. Click Next. **Step 6 –** On the Individual Hosts page, click **Next**. **Step 7 –** Review the Summary and click either **Save & Exit** or **Save & Run Jobs Now**. -The proxy does not update until the job is run. Once successfully ran, the servers in the assigned -host lists have been updated. +The proxy doesn't update until you run the job. Once the job runs successfully, Access Analyzer +updates the servers in the assigned host lists. ## Manual Upgrade diff --git a/docs/accessanalyzer/12.0/install/filesystemproxy/wizard.md b/docs/accessanalyzer/12.0/install/filesystemproxy/wizard.md index 519a6bbe78..b90eab4f24 100644 --- a/docs/accessanalyzer/12.0/install/filesystemproxy/wizard.md +++ b/docs/accessanalyzer/12.0/install/filesystemproxy/wizard.md @@ -7,9 +7,9 @@ sidebar_position: 10 # File System Proxy Service Installation The File System Proxy installer is designed to simplify the process of setting up File System -Scanning Proxy as a service on the designated proxy server. It is a best practice to use a -specifically provisioned domain account as the File System Proxy service account. Follow the steps -to install the FSAA service on the targeted proxy servers. +Scanning Proxy as a service on the designated proxy server. As a best practice, use a +specifically provisioned domain account as the File System Proxy service account. To install the +FileSystemAccess (FSAA) service on the targeted proxy servers: **Step 1 –** Run the `FileSystemProxy.exe` executable. The Netwrix Access Analyzer (formerly Enterprise Auditor) File System Scanning Proxy Setup wizard opens. @@ -34,8 +34,8 @@ folder page. On the Change destination folder page, choose a different destination folder for the installation. - Look in – Select which folder or sub-folder to complete installation in using the Look in - drop-down -- Up one level – Click the Up one level button to select the folder one level above the currently + dropdown +- Up one level – Click the Up one level button to select the folder one level above the selected one - Create a new folder – Click to create a new folder for the destination of the installation @@ -62,33 +62,33 @@ radio buttons. Then, click **Next**. **Step 7 –** When the installation completes, click **Finish** to exit the wizard. :::note -If the File System Proxy Service is installed on multiple servers, then a custom host list -of proxy servers should also be created in Netwrix Access Analyzer (formerly Enterprise Auditor). +If the File System Proxy Service is installed on multiple servers, you should also create a custom +host list of proxy servers in Netwrix Access Analyzer (formerly Enterprise Auditor). ::: -Once the File System Proxy Service has been installed on any proxy server, it is necessary to -configure the File System Solution certificate exchange method for Proxy Mode as a Service. See the +After you install the File System Proxy Service on any proxy server, configure the File System +Solution certificate exchange method for Proxy Mode as a Service. See the [FSAA Applet Certificate Management Overview](/docs/accessanalyzer/12.0/admin/datacollector/fsaa/certificatemanagement/certificatemanagement.md) topic for additional information. ## Custom Parameters for File System Proxy Service -The port and priority parameters can be modified for the File System Proxy Service on the registry +You can modify the port and priority parameters for the File System Proxy Service on the registry key: **HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\StealthAUDITFSAA\ImagePath** -- Port parameter – Only needs to be added to the registry key value if a custom port is used. The - default port of 8766 does not need to be set as a parameter +- Port parameter – You only need to add this to the registry key value if you use a custom port. + You don't need to set the default port of 8766 as a parameter - Append `-e [PORT NUMBER]` to the ImagePath key value -- Priority parameter – Can be modified so that the service runs as a background priority, which may - be desired if the service has been installed directly on a file server +- Priority parameter – You can modify this so that the service runs as a background priority, which + may be useful if you installed the service directly on a file server - Append `-r 0` to the ImagePath key value :::note - If both parameters are added, there is no required order. + If you add both parameters, there is no required order. ::: @@ -98,12 +98,12 @@ key: ::: -Follow the steps to configure these service parameters. +Configure these service parameters: ![Netwrix Enterprise Auditor FSAA Proxy Scanner service in the Services Management Console](/images/accessanalyzer/12.0/install/filesystemproxy/service.webp) **Step 1 –** After installing the File System Proxy Service, open Services Management Console -(`services.msc`). To stop the service, right-click on the Netwrix Access Analyzer (formerly +(`services.msc`). To stop the service, right-click the Netwrix Access Analyzer (formerly Enterprise Auditor) FSAA Proxy Scanner service and select **Stop**. ![File System Proxy ImagePath registry key in the Registry Editor](/images/accessanalyzer/12.0/install/filesystemproxy/regedit.webp) @@ -112,8 +112,8 @@ Enterprise Auditor) FSAA Proxy Scanner service and select **Stop**. **HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\StealthAUDITFSAA\ImagePath** -**Step 3 –** Right-click on the **ImagePath** key and select **Modify**. The Value data was set -during installation according to the installation directory location selected. +**Step 3 –** Right-click the **ImagePath** key and select **Modify**. The installer set the Value data +during installation according to the installation directory location you selected. - Priority set to background priority: - Add `-r 0` to the end of the path value @@ -126,7 +126,7 @@ during installation according to the installation directory location selected. **C:\Program Files (x86)\STEALTHbits\StealthAUDIT\FSAA\StealthAUDITRPC.EXEFSAASrv.DLL -e 1234** :::note - The port number needs to be added to the path only if a custom port is used. + You only need to add the port number to the path if you use a custom port. ::: @@ -151,5 +151,5 @@ section for additional configurations required to run scans in proxy mode as a s **Step 7 –** Repeat the previous step for each of the **FileSystem** > **0.Collection** jobs to employ this proxy service. -The custom port identified is now used for communication between the File System Proxy Service and -Access Analyzer. +Access Analyzer now uses the custom port you identified for communication between the File System +Proxy Service and Access Analyzer. diff --git a/docs/accessanalyzer/12.0/install/mapicdo/appendix.md b/docs/accessanalyzer/12.0/install/mapicdo/appendix.md index 5fc9baad9b..62895e478b 100644 --- a/docs/accessanalyzer/12.0/install/mapicdo/appendix.md +++ b/docs/accessanalyzer/12.0/install/mapicdo/appendix.md @@ -6,16 +6,16 @@ Exchange MAPI CDO. ::: -Before installing either binary, close the Access Analyzer application and ensure the following -requirements have been met: +Before installing either binary, close the Access Analyzer application and ensure you meet the +following requirements: -- Exchange System Manager for Exchange 2003 is not installed on the Access Analyzer Console server. -- Microsoft Outlook is not installed on the Access Analyzer Console server. +- Exchange System Manager for Exchange 2003 isn't installed on the Access Analyzer Console server. +- Microsoft Outlook isn't installed on the Access Analyzer Console server. These programs will interfere with the Microsoft Exchange MAPI CDO installation and with MAPI connections if they are installed on the Access Analyzer Console server. -Follow these steps to install the Microsoft Exchange MAPI CDO. +Install the Microsoft Exchange MAPI CDO. **Step 1 –** Download and run the ExchangeMapiCDO application from Microsoft. @@ -46,5 +46,5 @@ agreement and click Next. **Step 6 –** When the installation is complete, click Finish. -Reopen the Access Analyzer application, and the Settings > Exchange node is enabled for +Reopen the Access Analyzer application. Access Analyzer enables the Settings > Exchange node for configuration. diff --git a/docs/accessanalyzer/12.0/install/mapicdo/installation.md b/docs/accessanalyzer/12.0/install/mapicdo/installation.md index 834e54de5b..b4ee801e43 100644 --- a/docs/accessanalyzer/12.0/install/mapicdo/installation.md +++ b/docs/accessanalyzer/12.0/install/mapicdo/installation.md @@ -1,17 +1,17 @@ # StealthAUDIT MAPI CDO Installation -Both the Access Analyzer MAPI CDO and the Microsoft® Exchange MAPI CDO must to be installed in -order to enable the Settings > Exchange node. +You must install both the Access Analyzer MAPI CDO and the Microsoft® Exchange MAPI CDO +to enable the Settings > Exchange node. ![exchangenode](/images/accessanalyzer/12.0/stealthaudit/install_guides/mapi_cdo_install/exchangenode.webp) -The Microsoft Exchange MAPI CDO is only required to run the MAPI-based data collectors. See the +You only need the Microsoft Exchange MAPI CDO to run the MAPI-based data collectors. See the [Exchange Solution](/docs/accessanalyzer/12.0/solutions/exchange/overview.md) topic for additional information. -The Access Analyzer MAPI CDO can be downloaded from the -[Product Downloads](https://www.stealthbits.com/product-downloads) page of the Netwrix website. The -Microsoft Exchange MAPI CDO can be downloaded directly from Microsoft. See the +You can download the Access Analyzer MAPI CDO from the +[Product Downloads](https://www.stealthbits.com/product-downloads) page of the Netwrix website. You +can download the Microsoft Exchange MAPI CDO directly from Microsoft. See the [Appendix for the StealthAUDIT MAPI CDO Installation Guide](/docs/accessanalyzer/12.0/install/mapicdo/appendix.md) for requirements and installation steps to install the Microsoft Exchange MAPI CDO. @@ -21,16 +21,16 @@ Exchange MAPI CDO. ::: -Before installing either binary, close the Access Analyzer application and ensure the following -requirements have been met: +Before installing either binary, close the Access Analyzer application and ensure you meet the +following requirements: -- Exchange System Manager for Exchange 2003 is not installed on the Access Analyzer Console server. -- Microsoft Outlook is not installed on the Access Analyzer Console server. +- Exchange System Manager for Exchange 2003 isn't installed on the Access Analyzer Console server. +- Microsoft Outlook isn't installed on the Access Analyzer Console server. These programs interfere with MAPI connections if they are installed on the Access Analyzer Console server. -Follow the steps to install the Access Analyzer MAPI CDO. +Install the Access Analyzer MAPI CDO: **Step 1 –** Run the StealthAuditMapiCDO executable. diff --git a/docs/accessanalyzer/12.0/install/overview.md b/docs/accessanalyzer/12.0/install/overview.md index 39ab7a684b..5782bd50e7 100644 --- a/docs/accessanalyzer/12.0/install/overview.md +++ b/docs/accessanalyzer/12.0/install/overview.md @@ -21,7 +21,7 @@ information. ## File System Proxy Service -The File System Solution can be enabled to use proxy servers for scanning targeted file systems in +You can enable the File System Solution to use proxy servers for scanning targeted file systems in very large or widely dispersed environments. The File System Proxy installer is designed to simplify the process of setting up File System Scanning Proxy as a service on the designated proxy server. diff --git a/docs/accessanalyzer/12.0/install/sharepointagent/overview.md b/docs/accessanalyzer/12.0/install/sharepointagent/overview.md index 0273ce5ac3..ce504906b8 100644 --- a/docs/accessanalyzer/12.0/install/sharepointagent/overview.md +++ b/docs/accessanalyzer/12.0/install/sharepointagent/overview.md @@ -21,8 +21,8 @@ The version of the SharePoint Agent must also match the major version of Access ## Supported Platforms -The SharePoint Agent for the Access Analyzer SharePoint & SharePoint Online Solution can be -installed on the following SharePoint versions as targeted environments: +You can install the SharePoint Agent for the Access Analyzer SharePoint & SharePoint Online Solution +on the following SharePoint versions as targeted environments: - SharePoint® 2019 - SharePoint® 2016 @@ -30,6 +30,6 @@ installed on the following SharePoint versions as targeted environments: ## Sensitive Data Discovery Auditing Consideration -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the minimum amount -of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For example, if the job -is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are required (8x2=16). +If you run Sensitive Data Discovery (SDD) scans, you must increase the minimum amount +of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For example, if you +configure the job to scan 8 hosts at a time, you need an extra 16 GB of RAM (8x2=16). diff --git a/docs/accessanalyzer/12.0/install/sharepointagent/upgrade.md b/docs/accessanalyzer/12.0/install/sharepointagent/upgrade.md index 2a8a5b7842..5709368979 100644 --- a/docs/accessanalyzer/12.0/install/sharepointagent/upgrade.md +++ b/docs/accessanalyzer/12.0/install/sharepointagent/upgrade.md @@ -6,8 +6,6 @@ sidebar_position: 20 # Upgrade SharePoint Agent -Follow the steps to upgrade the SharePoint Agent. - ![Windows Control Panel Uninstall or change a program window](/images/accessanalyzer/12.0/install/sharepointagent/uninstall.webp) **Step 1 –** From Programs and Features (**Control Panel** > **Programs** > **Programs and @@ -15,13 +13,13 @@ Features**), uninstall the previous version of SharePoint Agent. :::note If you have the old Netwrix Sensitive Data Discovery Add-On installed, you must uninstall -it before continuing with this upgrade. For Access Analyzer 12.0, Sensitive Data Discovery is -installed as part of the main installation if your license includes it. +it before continuing with this upgrade. For Access Analyzer 12.0, the main installation includes +Sensitive Data Discovery if your license includes it. ::: **Step 2 –** Install the new version of the SharePoint Agent. See the [Installing the SharePoint Agent](/docs/accessanalyzer/12.0/install/sharepointagent/wizard.md) topic for instructions. -Now that the SharePoint Agent has been upgraded, it can be used by the SharePoint Solution. See the +Now that you have upgraded the SharePoint Agent, the SharePoint Solution can use it. See the [SharePoint Solution](/docs/accessanalyzer/12.0/solutions/sharepoint/overview.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/install/sharepointagent/wizard.md b/docs/accessanalyzer/12.0/install/sharepointagent/wizard.md index 02d17224c5..d23601d5c4 100644 --- a/docs/accessanalyzer/12.0/install/sharepointagent/wizard.md +++ b/docs/accessanalyzer/12.0/install/sharepointagent/wizard.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Installing the SharePoint Agent -The installer will prompt for credentials which are used to set the identity that the SharePoint +The installer will prompt for credentials that set the identity the SharePoint Access Auditor Agent service runs as. The agent service does no additional impersonation, so this is the account used to connect to and enumerate SharePoint. The service account credentials provided need to be a member of the Log on as a service local policy. Additionally, the credentials provided @@ -15,8 +15,8 @@ the Access Analyzer Console. See the [SharePoint Scan Options](/docs/accessanalyzer/12.0/requirements/sharepoint/scanoptions/scanoptions.md) topic for detailed permission information. -Follow the steps to install the SharePoint Agent on the application server which hosts the Central -Administration component of the targeted SharePoint farms. +Install the SharePoint Agent on the application server which hosts the Central Administration +component of the targeted SharePoint farms: **Step 1 –** Run the `SharePointAgent.exe` executable to open the Netwrix Access Analyzer (formerly Enterprise Auditor) SharePoint Agent Setup Wizard. @@ -49,7 +49,7 @@ SharePoint Agent page, click **Install** to start the installation. **Step 7 –** When the installation has completed, click **Finish** to exit the wizard. -Now that the SharePoint Agent has been installed on the appropriate application server, it can be -used by the SharePoint Solution. See the +Now that you have installed the SharePoint Agent on the appropriate application server, the +SharePoint Solution can use it. See the [SharePoint Solution](/docs/accessanalyzer/12.0/solutions/sharepoint/overview.md) topic for instructions on enabling agent service scans on the Agent Settings page. diff --git a/docs/accessanalyzer/12.0/requirements/activedirectory/activedirectory.md b/docs/accessanalyzer/12.0/requirements/activedirectory/activedirectory.md index ca25dd38b3..0dbd6225b7 100644 --- a/docs/accessanalyzer/12.0/requirements/activedirectory/activedirectory.md +++ b/docs/accessanalyzer/12.0/requirements/activedirectory/activedirectory.md @@ -10,8 +10,8 @@ The core components for Netwrix Access Analyzer (formerly Enterprise Auditor) ar Analyzer Console server, SQL Server, and Access Information Center. See the [Requirements](/docs/accessanalyzer/12.0/requirements/overview.md) topic for the core requirements. -In addition to these, integration with either the Netwrix Activity Monitor or the Netwrix Threat -Prevention is required for event activity data to be scanned. See the +In addition to these, you need integration with either the Netwrix Activity Monitor or the Netwrix +Threat Prevention to scan event activity data. See the [Netwrix Activity Monitor Documentation](https://helpcenter.netwrix.com/category/activitymonitor) or the [Netwrix Threat Prevention Documentation](https://helpcenter.netwrix.com/category/threatprevention) diff --git a/docs/accessanalyzer/12.0/requirements/activedirectory/target/access.md b/docs/accessanalyzer/12.0/requirements/activedirectory/target/access.md index 279cd76da0..fc7e10c62e 100644 --- a/docs/accessanalyzer/12.0/requirements/activedirectory/target/access.md +++ b/docs/accessanalyzer/12.0/requirements/activedirectory/target/access.md @@ -21,7 +21,7 @@ article for additional information. **Domain Controller Requirements** -The following are requirements for the domain controllers to be scanned: +The following are requirements for the domain controllers you want to scan: - .NET Framework 4.5+ installed - WINRM Service installed @@ -105,7 +105,7 @@ The following firewall ports are needed: ## Least Privilege Model You can configure a least privilege model based on your auditing needs and the data collection jobs -you use. The following jobs and their corresponding data collectors can be run with a +you use. You can run the following jobs and their corresponding data collectors with a least privilege permissions model. **1-AD_Scan Job Permissions** @@ -234,7 +234,7 @@ the following minimum requirements: - Read permission on the Certification Authority, granted through the Certification Authority console's Security tab -The Certification Authority server does not require local administrator rights. +The Certification Authority server doesn't require local administrator rights. :::info If the job fails to collect Certification Authority security, registry, or enrollment agent data diff --git a/docs/accessanalyzer/12.0/requirements/activedirectory/target/activity/activity.md b/docs/accessanalyzer/12.0/requirements/activedirectory/target/activity/activity.md index f3d78dfbcb..cee926d202 100644 --- a/docs/accessanalyzer/12.0/requirements/activedirectory/target/activity/activity.md +++ b/docs/accessanalyzer/12.0/requirements/activedirectory/target/activity/activity.md @@ -30,7 +30,7 @@ In this method, you will be deploying two agents: - Next, deploy the AD Agent to all domain controllers in the target domain. -Follow the steps to setup integration between Activity Monitor and Access Analyzer through an API +Set up integration between Activity Monitor and Access Analyzer through an API server. **Step 1 –** Deploy the Activity Agent to the API server. @@ -41,7 +41,7 @@ The next step is to configure the agent deployed to the API server. ## Configure API Server Agent -Follow the steps to configure the agent deployed to the API server. +Configure the agent deployed to the API server. **Step 1 –** On the Agents tab of the Activity Monitor Console, select the agent deployed to the API server. @@ -51,8 +51,8 @@ API server. **Step 3 –** Select the **API Server** tab and configure the following: - Select the **Enable API access on this agent** checkbox. -- The default **API server port (TCP)** is 4494, but it can be modified if desired. Ensure the - modified port is also used by Access Analyzer. +- The default **API server port (TCP)** is 4494, but you can modify it if desired. Ensure Access + Analyzer also uses the modified port. - Click **Add Application**. The Add or edit API client window opens. - Configure the following: @@ -63,19 +63,19 @@ API server. - Click **Copy** and save the Client Secret value to a text file. :::warning - It is not possible to retrieve the value after closing the Add or edit - API client window. It must be copied first. + You can't retrieve the value after closing the Add or edit + API client window. Copy it first. ::: - - By default, the **Secret Expires** in 3 days. That means it must be used in the Access - Analyzer Connection Profile within 72 hours or a new secret will need to be generated. Modify + - By default, the **Secret Expires** in 3 days. That means you must use it in the Access + Analyzer Connection Profile within 72 hours, or you will need to generate a new secret. Modify if desired. - Click **OK** to save the configuration and close the Add or edit API client window. -- If the Activity Monitor Console server is not the API Server, then click **Use this console** to +- If the Activity Monitor Console server isn't the API Server, then click **Use this console** to grant the Activity Monitor the ability to manage the API server. -- The IPv4 or IPv6 allowlist allows you to limit access to the API server data to specific hosts. +- Use the IPv4 or IPv6 allowlist to limit access to the API server data to specific hosts. **Step 4 –** Click **OK** to save the configuration and close the Agent properties window. @@ -83,7 +83,7 @@ The next step is to configure the agents deployed to the domain controllers. ## Configure Domain Controller Agent -Follow the steps to configure the agent deployed to the domain controller. +Configure the agent deployed to the domain controller. **Step 1 –** On the Agents tab of the Activity Monitor Console, select an agent deployed to domain controller. @@ -94,9 +94,9 @@ controller. - Select the **Enable Archiving for this agent** checkbox. - Select the **Archive log files on a UNC path** option. Click the **...** button and navigate to - the desired network share on the API server. -- The **User name** and **User password** fields only need to be filled in if the account used to - install the agent does not have access to this share. + the network share you want on the API server. +- Fill in the **User name** and **User password** fields only if the account used to + install the agent doesn't have access to this share. :::tip Remember, The account used to install the agent on a domain controller is a Domain @@ -110,7 +110,7 @@ controller. **Step 5 –** Repeat Steps 1-4 for each agent deployed to domain controller. -These agent are configured to save the Archive logs to the selected share. +These agents save the Archive logs to the selected share. ## Configure Monitored Domain Output @@ -119,16 +119,16 @@ Enterprise Auditor). **Step 1 –** Select the **Monitored Domains** tab. -**Step 2 –** Select the desired domain and click **Add Output**. The Add New Ouptut window opens. +**Step 2 –** Select the domain you want and click **Add Output**. The Add New Ouptut window opens. **Step 3 –** Configure the following: -- Configure the desired number of days for the **Period to keep Log files**. This is the number of - days the log files are kept on the API server configured in the sections above. This needs to be - set to a greater value than the days between Access Analyzer scans. +- Configure the number of days you want for the **Period to keep Log files**. This is the number of + days the log files are kept on the API server you configured earlier. You need to + set this to a greater value than the days between Access Analyzer scans. - For example, if Access Analyzer runs the **AD_ActivityCollection** Job once a week (every 7 - days), then the Activity Monitor output should be configured to retain at least 10 days of log + days), you should configure the Activity Monitor output to retain at least 10 days of log files. - Check the **This log file is for StealthAUDIT** box. @@ -142,12 +142,12 @@ Access Analyzer now has access to the agent log files for this domain. ## Configure Connection Profile -Follow the steps to configure the Connection Profile in Access Analyzer. +Configure the Connection Profile in Access Analyzer. :::tip -Remember, the Client ID and Client Secret were generated by the API server and copied to a text -file. If the secret expired before the Connection Profile is configured, it will need to be -re-generated. +Remember, the API server generated the Client ID and Client Secret, and you copied them to a text +file. If the secret expires before you configure the Connection Profile, you will need to +re-generate it. ::: @@ -172,19 +172,19 @@ name. Group. Select the **Settings > Connection** node. **Step 7 –** Select the **Select one of the following user defined profiles** option. Expand the -drop-down menu and select the Connection Profile with this credential. +dropdown menu and select the Connection Profile with this credential. **Step 8 –** Click **Save** and then **OK** to confirm the changes to the job group settings. -The Connection Profile will now be used for AD Activity collection. +Access Analyzer will now use the Connection Profile for AD Activity collection. ## Configure the AD_ActivityCollection Job -The Access Analyzer requires additional configurations in order to collect domain activity data. -Follow the steps to configure the **AD_ActivityCollection** Job. +The Access Analyzer requires additional configurations to collect domain activity data. +Configure the **AD_ActivityCollection** Job. :::note -Ensure that the **.Active Directory Inventory** Job Group has been successfully run +Ensure that you have successfully run the **.Active Directory Inventory** Job Group against the target domain. ::: @@ -223,10 +223,10 @@ last step. - Absolute Timespan – Set the date range for activity logs to collect when the scan is run :::info -The threshold should be set to ensure the logs are collected before the Activity +You should set the threshold to ensure the logs are collected before the Activity Monitor domain output log retention expires. For example, if Access Analyzer runs the -**AD_ActivityCollection** Job once a week (every 7 days), then the Activity Monitor output should be -configured to retain at least 10 days of log files. +**AD_ActivityCollection** Job once a week (every 7 days), you should configure the Activity Monitor +output to retain at least 10 days of log files. ::: @@ -246,30 +246,30 @@ Credential with the Refresh token: - Click **OK** to save and close the User Credentials window. - Click **Save** and then **OK** to confirm the changes to the Connection Profile. -The query is now configured to target the Activity Monitor API Server to collect domain activity -logs. +Access Analyzer now targets the Activity Monitor API Server with this query to collect domain +activity logs. ### (Optional) Configure Import of AD Activity into Netwrix Access Information Center -AD Activity data can be imported into Netwrix Access Information Center by the -**AD_ActivityCollection** Job. However, this is disabled by default. Follow the steps to enable the -importing of AD activity data into the Access Information Center. +The **AD_ActivityCollection** Job can import AD Activity data into Netwrix Access Information +Center. However, this is disabled by default. Enable the +import of AD activity data into the Access Information Center. **Step 1 –** Navigate to the **Jobs** > **Active Directory** > **6.Activity** > **0.Collection** > **AD_ActivityCollection** Job. **Step 2 –** On the job's Overview page, enable the import of AD Events. -- Click on the **Enable to import AD events into the AIC** parameter. +- Click the **Enable to import AD events into the AIC** parameter. - On the Parameter Configuration window, select the **Enabled** checkbox and click **Save**. **Step 3 –** On the job's Overview page, enable the import of authentication Events. -- Click on the **Enable to import authentication events into the AIC** parameter. +- Click the **Enable to import authentication events into the AIC** parameter. - On the Parameter Configuration window, select the **Enabled** checkbox and click **Save**. **Step 4 –** Optionally, modify the **List of attributes to track for Object Modified changes** and **Number of days to retain activity data in the AIC** parameters. -The **AD_ActivityCollection** Job is now configured to import both AD events and authentication -events into the Netwrix Access Information Center. +You have now configured the **AD_ActivityCollection** Job to import both AD events and +authentication events into the Netwrix Access Information Center. diff --git a/docs/accessanalyzer/12.0/requirements/activedirectory/target/activity/filearchive.md b/docs/accessanalyzer/12.0/requirements/activedirectory/target/activity/filearchive.md index d77004d36c..c4c266063c 100644 --- a/docs/accessanalyzer/12.0/requirements/activedirectory/target/activity/filearchive.md +++ b/docs/accessanalyzer/12.0/requirements/activedirectory/target/activity/filearchive.md @@ -6,9 +6,9 @@ sidebar_position: 10 # File Archive Repository Option -As an alternative to using an API Server, Netwrix Activity Monitor can be configured to store all -archived logs to a network share. This option requires all of the domain logs to be stored in the -same share location in order for Access Analyzer to collect the AD Activity data. +As an alternative to using an API Server, you can configure Netwrix Activity Monitor to store all +archived logs to a network share. This option requires storing all of the domain logs in the +same share location for Access Analyzer to collect the AD Activity data. **Prerequisite** @@ -16,7 +16,7 @@ Deploy the AD Agent to each domain controller in the target domain. ## Configure Domain Controller Agent -Follow the steps to configure the agent deployed to the domain controller. +Configure the agent deployed to the domain controller. :::note These steps assume the network share where the activity log files will be archived already @@ -34,12 +34,12 @@ controller. - Check the Enable Archiving for this agent box. - Select the **Archive log files on a UNC path** option. Click the ... button and navigate to the desired network share. -- The **User name** and **User password** fields only need to be filled in if the account used to - install the agent does not have access to this share. +- Fill in the **User name** and **User password** fields only if the account used to + install the agent doesn't have access to this share. :::tip Remember, The account used to install the agent on a domain controller is a Domain - Administrator account. This is typically the credential that will be used in the Netwrix Access + Administrator account. This is typically the credential you will use in the Netwrix Access Analyzer (formerly Enterprise Auditor) Connection Profile. However, a least privilege option is a domain user account with Read access to this share. ::: @@ -52,7 +52,7 @@ controller. **Step 5 –** Repeat Steps 1-4 for each agent deployed to domain controller pointing to the same network share in Step 3 for each agent. -These agent are configured to save the Archive logs to the selected share. +These agents save the Archive logs to the selected share. ## Configure Monitored Domain Output @@ -61,16 +61,16 @@ Enterprise Auditor). **Step 1 –** Select the **Monitored Domains** tab. -**Step 2 –** Select the desired domain and click **Add Output**. The Add New Ouptut window opens. +**Step 2 –** Select the domain you want and click **Add Output**. The Add New Ouptut window opens. **Step 3 –** Configure the following: -- Configure the desired number of days for the **Period to keep Log files**. This is the number of - days the log files are kept on the API server configured in the sections above. This needs to be - set to a greater value than the days between Access Analyzer scans. +- Configure the number of days you want for the **Period to keep Log files**. This is the number of + days the log files are kept on the API server you configured earlier. You need to + set this to a greater value than the days between Access Analyzer scans. - For example, if Access Analyzer runs the **AD_ActivityCollection** Job once a week (every 7 - days), then the Activity Monitor output should be configured to retain at least 10 days of log + days), you should configure the Activity Monitor output to retain at least 10 days of log files. - Check the **This log file is for StealthAUDIT** box. @@ -84,7 +84,7 @@ Access Analyzer now has access to the agent log files for this domain. ## Configure Connection Profile -Follow the steps to configure the Connection Profile in Access Analyzer. +Configure the Connection Profile in Access Analyzer. **Step 1 –** On the Settings > Connection node of the Access Analyzer Console, select the Connection Profile for the Active Directory solution. If you haven't yet created a Connection Profile or desire @@ -111,19 +111,19 @@ a specific one for AD Activity, create a new one and provide a unique descriptiv the **Settings > Connection** node. **Step 7 –** Select the **Select one of the following user defined profiles** option. Expand the -drop-down menu and select the Connection Profile with this credential. +dropdown menu and select the Connection Profile with this credential. **Step 8 –** Click **Save** and then **OK** to confirm the changes to the job group settings. -The Connection Profile will now be used for AD Activity collection. +Access Analyzer will now use the Connection Profile for AD Activity collection. ## Configure the AD_ActivityCollection Job -Access Analyzer requires additional configurations in order to collect domain activity data. Follow +Access Analyzer requires additional configurations to collect domain activity data. Follow the steps to configure the **AD_ActivityCollection** Job. :::note -Ensure that the .Active Directory Inventory Job Group has been successfully run against +Ensure that you have successfully run the .Active Directory Inventory Job Group against the target domain. ::: @@ -154,10 +154,10 @@ Click **Next**. - Absolute Timespan – Set the date range for activity logs to collect when the scan is run :::info -The threshold should be set to ensure the logs are collected before the Activity +You should set the threshold to ensure the logs are collected before the Activity Monitor domain output log retention expires. For example, if Access Analyzer runs the -**AD_ActivityCollection** Job once a week (every 7 days), then the Activity Monitor output should be -configured to retain at least 10 days of log files. +**AD_ActivityCollection** Job once a week (every 7 days), you should configure the Activity Monitor +output to retain at least 10 days of log files. ::: @@ -168,5 +168,5 @@ the collected data in the SQL Server database. **Step 9 –** Click **OK** to save the changes and close the Query Properties page. -The query is now configured to target the network share where the Activity Monitor domain activity +This query now targets the network share where the Activity Monitor domain activity logs are archived. diff --git a/docs/accessanalyzer/12.0/requirements/activedirectory/target/activity/threatprevention.md b/docs/accessanalyzer/12.0/requirements/activedirectory/target/activity/threatprevention.md index 6f3d36b0dc..619a14549c 100644 --- a/docs/accessanalyzer/12.0/requirements/activedirectory/target/activity/threatprevention.md +++ b/docs/accessanalyzer/12.0/requirements/activedirectory/target/activity/threatprevention.md @@ -6,22 +6,22 @@ sidebar_position: 20 # Send Active Directory Event Data from Netwrix Threat Prevention to Netwrix Access Analyzer -When Netwrix Threat Prevention is configured to monitor a domain, the event data collected by the -policies can be provided to Netwrix Access Analyzer (formerly Enterprise Auditor) for auditing and +When you configure Netwrix Threat Prevention to monitor a domain, you can provide the event data +collected by the policies to Netwrix Access Analyzer (formerly Enterprise Auditor) for auditing and analysis. This is accomplished by configuring Threat Prevention to send data to Netwrix Activity Monitor, which in turn creates the activity log files that Access Analyzer collects. :::note -Threat Prevention can only be configured to send event data to one Netwrix application, -either Netwrix Activity Monitor or Netwrix Threat Manager but not both. However, the Activity -Monitor can be configured with outputs for Access Analyzer and Threat Manager. +You can only configure Threat Prevention to send event data to one Netwrix application, +either Netwrix Activity Monitor or Netwrix Threat Manager but not both. However, you can configure +the Activity Monitor with outputs for Access Analyzer and Threat Manager. ::: -Follow the steps to configure this integration. +Configure this integration. :::info -It is a best practice to use the API Server option of the Activity Monitor for +As a best practice, use the API Server option of the Activity Monitor for this integration between Threat Prevention and Access Analyzer. ::: @@ -41,12 +41,12 @@ Threat Manager Configuration** on the menu. The Netwrix Threat Manager Configura - App Token – Leave this field blank for integration with Activity Monitor - Policies – The table displays all policies created in Threat Prevention along with a State icon - indicating if the policy is active. Check the **Send** box for the desired policies monitoring the - target domain activity. + indicating if the policy is active. Check the **Send** box for the policies you want that monitor + the target domain activity. **Step 3 –** Click **Save**. -All real-time event data from the selected policies is now sent to Activity Monitor. Additional -policies can be added to this data stream through the Netwrix Threat Manager Configuration window or -by selecting the **Send to Netwrix Threat Manager** option on the Actions tab of the respective -policy. +Threat Prevention now sends all real-time event data from the selected policies to Activity +Monitor. You can add additional policies to this data stream through the Netwrix Threat Manager +Configuration window or by selecting the **Send to Netwrix Threat Manager** option on the Actions +tab of the respective policy. diff --git a/docs/accessanalyzer/12.0/requirements/activedirectory/target/overview.md b/docs/accessanalyzer/12.0/requirements/activedirectory/target/overview.md index e5cad5f2ed..bb25a830b6 100644 --- a/docs/accessanalyzer/12.0/requirements/activedirectory/target/overview.md +++ b/docs/accessanalyzer/12.0/requirements/activedirectory/target/overview.md @@ -7,7 +7,7 @@ sidebar_position: 10 # Active Directory Domain Target Requirements Netwrix Access Analyzer (formerly Enterprise Auditor) can execute scans on Active Directory domains. -The Netwrix Activity Monitor can be configured to monitor activity on Active Directory domains and +You can configure the Netwrix Activity Monitor to monitor activity on Active Directory domains and make the event data available for Access Analyzer Active Directory Activity scans. ## Auditing Permissions @@ -16,7 +16,7 @@ The following permission is needed: - Member of the Domain Administrators group -Some collection jobs do allow for a least privilege model. See the +Some collection jobs allow for a least privilege model. See the [Active Directory Auditing Configuration](/docs/accessanalyzer/12.0/requirements/activedirectory/target/access.md) topic for additional information. ## Auditing Port Requirements @@ -27,7 +27,7 @@ Ports vary based on the data collector being used. See the ## Activity Auditing Permissions :::note -Active Directory domain activity events can also be monitored through Netwrix Threat +You can also monitor Active Directory domain activity events through Netwrix Threat Prevention. This requires integration between it and Netwrix Activity Monitor to enable access to the data for Access Analyzer Active Directory Activity scans. See the [Send Active Directory Event Data from Netwrix Threat Prevention to Netwrix Access Analyzer](/docs/accessanalyzer/12.0/requirements/activedirectory/target/activity/threatprevention.md) @@ -37,8 +37,8 @@ topic for additional information. Requirements to Deploy the AD Agent on the Domain Controller -The Netwrix Activity Monitor must have an AD Agent deployed on the domain controller to be -monitored. While actively monitoring, the AD Agent generates activity log files stored on the +The Netwrix Activity Monitor must have an AD Agent deployed on each domain controller you want to +monitor. While actively monitoring, the AD Agent generates activity log files stored on the server. The credential used to deploy the AD Agent must have the following permissions on the server: @@ -46,8 +46,8 @@ server: - READ and WRITE access to the archive location for Archiving feature only :::note -For monitoring an Active Directory domain, the AD Agent must be installed on all domain -controllers within the domain to be monitored. +To monitor an Active Directory domain, you must install the AD Agent on all domain +controllers within the domain. ::: @@ -74,9 +74,9 @@ are required for communication between the Agent server and the Netwrix Activity | -------------------------------- | -------- | ----- | ------------------- | | Activity Monitor to Agent Server | TCP | 4498 | Agent Communication | -The Windows firewall rules need to be configured on the Windows server, which require certain -inbound rules be created if the scans are running in applet mode. These scans operate over a default -port range, which cannot be specified via an inbound rule. For more information, see the Microsoft +You need to configure the Windows firewall rules on the Windows server, which require you to +create certain inbound rules if the scans are running in applet mode. These scans operate over a +default port range, which you can't specify via an inbound rule. For more information, see the Microsoft [Connecting to WMI on a Remote Computer](https://msdn.microsoft.com/en-us/library/windows/desktop/aa389290(v=vs.85).aspx) article. diff --git a/docs/accessanalyzer/12.0/requirements/activedirectorypermissionsanalyzer/target.md b/docs/accessanalyzer/12.0/requirements/activedirectorypermissionsanalyzer/target.md index 5844b2b7c4..44803343bc 100644 --- a/docs/accessanalyzer/12.0/requirements/activedirectorypermissionsanalyzer/target.md +++ b/docs/accessanalyzer/12.0/requirements/activedirectorypermissionsanalyzer/target.md @@ -21,7 +21,7 @@ article for additional information. **Domain Controller Requirements** -The following are requirements for the domain controllers to be scanned: +The following are requirements for the domain controllers you want to scan: - .NET Framework 4.5+ installed - WINRM Service installed diff --git a/docs/accessanalyzer/12.0/requirements/aws/aws.md b/docs/accessanalyzer/12.0/requirements/aws/aws.md index 74da6a3ba7..2d0ed89f43 100644 --- a/docs/accessanalyzer/12.0/requirements/aws/aws.md +++ b/docs/accessanalyzer/12.0/requirements/aws/aws.md @@ -17,7 +17,7 @@ target environment requirements. **RAM, CPU, and Disk Space** -These are dependent upon the size of the target environment: +These depend on the size of the target environment: | Environment | Large | Medium – Small | | ----------- | -------------- | -------------- | @@ -27,20 +27,19 @@ These are dependent upon the size of the target environment: | Disk Space | 30 GB | 30 GB | :::note -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the -minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For -example, if the job is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are -required (8x2=16). +If you run Sensitive Data Discovery (SDD) scans, increase the minimum amount of RAM. Each +thread requires a minimum of 2 additional GB of RAM per host. For example, if you configure the +job to scan 8 hosts at a time, you need an extra 16 GB of RAM (8x2=16). ::: **Sensitive Data Discovery Auditing Requirement** :::note -The appropriate JDK (Java) version for Sensitive Data Discovery is installed on the -server. The JDK deployed is prepackaged and does not require any configuration; it has been -preconfigured to work with Access Analyzer and should never be customized through Java. It will not -conflict with other JDKs or Java Runtimes in the same environment. +Access Analyzer installs the appropriate JDK (Java) version for Sensitive Data Discovery on +the server. This JDK comes prepackaged and preconfigured to work with Access Analyzer, requires no +additional configuration, and you should never customize it through Java. It doesn't conflict with +other JDKs or Java Runtimes in the same environment. ::: @@ -48,7 +47,7 @@ conflict with other JDKs or Java Runtimes in the same environment. **RAM, CPU, and Disk Space** -These are dependent upon the size of the target environment. +These depend on the size of the target environment. | Environment | Large | Medium – Small | | ------------------------ | -------------- | -------------- | diff --git a/docs/accessanalyzer/12.0/requirements/aws/configurescans.md b/docs/accessanalyzer/12.0/requirements/aws/configurescans.md index 3d2f0f9900..69af9617f8 100644 --- a/docs/accessanalyzer/12.0/requirements/aws/configurescans.md +++ b/docs/accessanalyzer/12.0/requirements/aws/configurescans.md @@ -6,13 +6,12 @@ sidebar_position: 20 # Configure AWS for Scans -In order to scan multiple AWS accounts using one account you need to create a role in each target -account, so that It can provide the designated scanning account permissions to scan resources it -controls. This is achieved through the following steps which will need to be completed leveraging a -user with administrative access to each target account: +To scan multiple AWS accounts using one account, create a role in each target account so it +can grant the designated scanning account permission to scan the resources it controls. Complete +the following steps using a user with administrative access to each target account: **Step 1 –** Create a Managed Policy in each target account that will be used to allow access to -account (S3, Org and IAM). +account (S3, Org, and IAM). **Step 2 –** Create a Role in each target account that will be used to allow access to listing IAM users. @@ -20,16 +19,16 @@ users. **Step 3 –** Create a Managed Policy in the designated scanning account that will be used to allow the service account to assume the configured role in each target account. -**Step 4 –** Add Role to Access Analyzer. The Role created in the scanning account will need to be -added to the **1-AWS_OrgScan**, **2-AWS_S3Scan**, and **3-AWS_IAMScan** job query configurations. +**Step 4 –** Add the role created in the scanning account to Access Analyzer's +**1-AWS_OrgScan**, **2-AWS_S3Scan**, and **3-AWS_IAMScan** job query configurations. See the [AWS: Login Roles](/docs/accessanalyzer/12.0/admin/datacollector/aws/loginroles.md) topic for additional information. -Once these steps are completed, the role must be added to the AWS queries within Access Analyzer. +After you complete these steps, add the role to the AWS queries within Access Analyzer. ## Create a Managed Policy in Each Target Account -The following steps will need to be completed in each target account. +Complete the following steps in each target account. **Step 1 –** Sign into the Identity and Access Management Console (IAM) as an administrator of the Trusting account. @@ -86,7 +85,7 @@ and click **Create policy**. **Step 7 –** Click **Create Policy**. :::note -If the designated scanning account is not in Root (Master Account), create a second policy +If the designated scanning account isn't in Root (Master Account), create a second policy in the Master Account with the following JSON definition: ::: @@ -109,12 +108,11 @@ in the Master Account with the following JSON definition: } ``` -The next step is to create a role in each target account that will be used to allow access to -listing IAM users. +The next step is to create a role in each target account that allows access to list IAM users. ## Create a Role in Each Target Account -The following steps will need to be completed in each target account. For this, you will need the +Complete the following steps in each target account. For this, you need the Account ID of the designating scanning account. :::note @@ -133,7 +131,7 @@ target account. ![Create role page Another AWS account option](/images/accessanalyzer/12.0/requirements/target/config/createrole.webp) **Step 3 –** Select the **Another AWS Account** option and add the Account ID of the scanning -account that will be leveraged within Access Analyzer. +account that Access Analyzer uses. **Step 4 –** Click **Next: Permissions**. @@ -151,13 +149,13 @@ account that will be leveraged within Access Analyzer. **Step 9 –** Click **Create Role**. -The next step is to create a Managed Policy in the designated scanning account that will be used to -allow the service account to assume the configured role in each target account. +The next step is to create a Managed Policy in the designated scanning account that lets the +service account assume the configured role in each target account. ## Configure the Scanning Account -Create a Managed Policy in the scanning account that will be used to allow the user to assume the -roles configured in each target account. +Create a Managed Policy in the scanning account that lets the user assume the roles configured in +each target account. **Step 1 –** Sign into the Identity and Access Management Console (IAM) as an administrator of the scanning account. @@ -197,8 +195,8 @@ scanning account. ``` :::note -Replace `ROLENAME` with the name of the role that was created. If the `ROLENAME` is -different in each account, then a policy will need to be created for each distinct role name. +Replace `ROLENAME` with the name of the role you created. If `ROLENAME` differs across +accounts, create a policy for each distinct role name. ::: @@ -216,8 +214,8 @@ different in each account, then a policy will need to be created for each distin ![Security credentials tab](/images/accessanalyzer/12.0/requirements/target/config/securitycredentials.webp) -**Step 10 –** In the Security credentials tab, click **Create access key**. Make sure to note the -Access key ID and Secret access key which need to be input into Access Analyzer. +**Step 10 –** In the Security credentials tab, click **Create access key**, and note the Access +key ID and Secret access key. Enter both into Access Analyzer. You can now create the Connection Profile for the AWS Solution. See the [Amazon Web Services for User Credentials](/docs/accessanalyzer/12.0/admin/settings/connection/create/aws.md) topic diff --git a/docs/accessanalyzer/12.0/requirements/aws/target.md b/docs/accessanalyzer/12.0/requirements/aws/target.md index 2d5a6919bb..f45279c2c7 100644 --- a/docs/accessanalyzer/12.0/requirements/aws/target.md +++ b/docs/accessanalyzer/12.0/requirements/aws/target.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Target Amazon Web Service Requirements, Permissions, and Ports -The Access Analyzer for AWS Solution provides the ability to audit Amazon Web Services (AWS) to +The Access Analyzer for AWS Solution lets you audit Amazon Web Services (AWS) to collect IAM users, groups, roles, and policies, as well as S3 permissions, content, and sensitive data from target AWS accounts. It scans: diff --git a/docs/accessanalyzer/12.0/requirements/box/box.md b/docs/accessanalyzer/12.0/requirements/box/box.md index d96200d4e7..1c61730ba7 100644 --- a/docs/accessanalyzer/12.0/requirements/box/box.md +++ b/docs/accessanalyzer/12.0/requirements/box/box.md @@ -17,7 +17,7 @@ environment requirements. **RAM, CPU, and Disk Space** -These are dependent upon the size of the target environment: +These depend on the size of the target environment: | Environment | Large | Medium – Small | | ----------- | ----------------------- | ---------------------- | @@ -30,7 +30,7 @@ These are dependent upon the size of the target environment: **RAM, CPU, and Disk Space** -These are dependent upon the size of the target environment. +These depend on the size of the target environment. | Environment | Large | Medium – Small | | ------------------------ | ----------------------- | ---------------------- | diff --git a/docs/accessanalyzer/12.0/requirements/databases/azuresql/azuresql.md b/docs/accessanalyzer/12.0/requirements/databases/azuresql/azuresql.md index dcfa0cbc40..5fd69449d5 100644 --- a/docs/accessanalyzer/12.0/requirements/databases/azuresql/azuresql.md +++ b/docs/accessanalyzer/12.0/requirements/databases/azuresql/azuresql.md @@ -13,10 +13,10 @@ used by AzureSQL to return the required audit logs. See the Microsoft Knowledge Base article for additional information. :::info -It is recommended to create a new user when leveraging a least privilege access -model to access the AzureSQL database because the user must exist in the master database and all -target databases. A least privilege access model is one that uses the bare minimum privileges -required to carry out collections for the AzureSQL data collector. +Netwrix recommends creating a new user when you use a least privilege access model to +access the AzureSQL database, because the user must exist in the master database and all target +databases. A least privilege access model is one that uses the bare minimum privileges required to +carry out collections for the AzureSQL data collector. ::: @@ -27,7 +27,7 @@ The Least Privilege Model requires the following role and permissions: - Control permission on target databases :::note - Control permission must be granted on any database you want to collect data for. + Grant Control permission on any database you want to collect data for. ::: diff --git a/docs/accessanalyzer/12.0/requirements/databases/azuresql/azuresqlaccess.md b/docs/accessanalyzer/12.0/requirements/databases/azuresql/azuresqlaccess.md index 55500526b7..61a231eec9 100644 --- a/docs/accessanalyzer/12.0/requirements/databases/azuresql/azuresqlaccess.md +++ b/docs/accessanalyzer/12.0/requirements/databases/azuresql/azuresqlaccess.md @@ -9,8 +9,8 @@ sidebar_position: 20 Access Analyzer for Azure SQL relies on the native Azure SQL auditing capabilities to collect and report on user activity, as well as successful or unsuccessful server or database logon activity. Azure SQL Auditing supports three different audit log destinations. At present Access Analyzer only -supports storage as the audit log destination. This document describes the necessary permissions -required to configure the Access Analyzer Azure SQL Job Group. +supports storage as the audit log destination. This document describes the permissions required to +configure the Access Analyzer Azure SQL Job Group. With Access Analyzer for Azure SQL, you can create custom roles for differential access to Access Analyzer. @@ -22,8 +22,8 @@ Access Analyzer for Azure SQL creates roles specifically to target Azure SQL Dat The scope of a particular role largely defines that role. A scope-defined role has access to, or is limited to all resources in a Management Group, Subscription, Resource Group or -Resource. For example, if all SQL databases reside within a resource group, then the scope can be -restricted to that resource group. If databases reside in different resource groups, then the scope +Resource. For example, if all SQL databases reside within a resource group, you can restrict the +scope to that resource group. If databases reside in different resource groups, then the scope for the custom role should be at the subscription level. This enables Access Analyzer to discover all SQL databases in the subscription. @@ -114,8 +114,8 @@ following example) and save it to a local directory. it. Selecting that file enables the Review + Create button. Click **Review + Create** to create the role or click **Next** to review and edit the permissions. -When you open the JSON file, the Custom Role Name and Description boxes are populated -automatically. You can customize the name and description of the custom role in this step. +Opening the JSON file automatically populates the Custom Role Name and Description boxes. +You can customize the name and description of the custom role in this step. ![Azure SQL Configuration - Create a Cusotm Role window](/images/accessanalyzer/12.0/requirements/target/config/azuresqlperm_customrolecreation_4.webp) diff --git a/docs/accessanalyzer/12.0/requirements/databases/databases.md b/docs/accessanalyzer/12.0/requirements/databases/databases.md index ca3e635d2d..07f7e444e1 100644 --- a/docs/accessanalyzer/12.0/requirements/databases/databases.md +++ b/docs/accessanalyzer/12.0/requirements/databases/databases.md @@ -30,7 +30,7 @@ See the following topics for target environment requirements: **RAM, CPU, and Disk Space** -These are dependent upon the size of the target environment: +These depend on the size of the target environment: | Environment | Extra-Large | Large | Medium | Small | | ----------- | -------------------- | ------------------------ | --------------------- | -------------------- | @@ -76,7 +76,7 @@ conflict with other JDKs or Java Runtimes in the same environment. **RAM, CPU, and Disk Space** -These are dependent upon the size of the target environment. +These depend on the size of the target environment. | Environment | Extra-Large | Large | Medium | Small | | ------------------------ | -------------------- | ------------------------ | --------------------- | -------------------- | diff --git a/docs/accessanalyzer/12.0/requirements/databases/db2.md b/docs/accessanalyzer/12.0/requirements/databases/db2.md index f0fdafeee4..c906f566e3 100644 --- a/docs/accessanalyzer/12.0/requirements/databases/db2.md +++ b/docs/accessanalyzer/12.0/requirements/databases/db2.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Target Db2 Requirements, Permissions, and Ports -The Access Analyzer for Databases Solution provides the ability to audit and monitor Db2 database +The Access Analyzer for Databases Solution lets you audit and monitor Db2 database environments to collect permissions and sensitive data. It scans: - DB2LUW 11+ diff --git a/docs/accessanalyzer/12.0/requirements/databases/mongodb.md b/docs/accessanalyzer/12.0/requirements/databases/mongodb.md index b17ec05975..70e5ab1f2a 100644 --- a/docs/accessanalyzer/12.0/requirements/databases/mongodb.md +++ b/docs/accessanalyzer/12.0/requirements/databases/mongodb.md @@ -6,7 +6,7 @@ sidebar_position: 20 # Target MongoDB Requirements, Permissions, and Ports -The Access Analyzer for Databases Solution provides the ability to audit and monitor MongoDB +The Access Analyzer for Databases Solution lets you audit and monitor MongoDB database environments to collect permissions and sensitive data. It scans: - MongoDB 5.0 diff --git a/docs/accessanalyzer/12.0/requirements/databases/mysql.md b/docs/accessanalyzer/12.0/requirements/databases/mysql.md index dead4951f6..547b6cf0fa 100644 --- a/docs/accessanalyzer/12.0/requirements/databases/mysql.md +++ b/docs/accessanalyzer/12.0/requirements/databases/mysql.md @@ -6,7 +6,7 @@ sidebar_position: 30 # Target MySQL Requirements, Permissions, and Ports -The Access Analyzer for Databases Solution provides the ability to audit and monitor MySQL database +The Access Analyzer for Databases Solution lets you audit and monitor MySQL database environments to collect permissions and sensitive data. It scans: - MySQL 5.x diff --git a/docs/accessanalyzer/12.0/requirements/databases/oracle/leastprivilege.md b/docs/accessanalyzer/12.0/requirements/databases/oracle/leastprivilege.md index b93a6f09c6..b1c2ef0077 100644 --- a/docs/accessanalyzer/12.0/requirements/databases/oracle/leastprivilege.md +++ b/docs/accessanalyzer/12.0/requirements/databases/oracle/leastprivilege.md @@ -6,9 +6,9 @@ sidebar_position: 10 # Oracle Target Least Privilege Model -We recommend using an account DBA privilege to run Access Analyzer against an Oracle database. -However, if that is not acceptable all the privileges that are required to configure and run the -solution are below and can be used to implement the least privileges necessary. +Netwrix recommends using an account with DBA privilege to run Access Analyzer against an Oracle +database. If that isn't acceptable, this topic lists all the privileges required to configure and +run the solution. Use them to implement the least privileges necessary. ## Create Session Privilege @@ -21,7 +21,7 @@ GRANT CREATE SESSION TO %USERNAME%;          ``` :::note -The above command will grant the privilege only in the current container. To follow the +This command grants the privilege only in the current container. To follow the least privilege model, only grant the privilege on the containers (or pluggable databases) that you will be scanning with Access Analyzer. ::: @@ -36,7 +36,7 @@ GRANT CREATE SESSION TO %USERNAME% CONTAINER=ALL;          ## User Credentials Role -When using a least privileged model for Oracle, **SYSDBA** must be selected for the Role in the User +When using a least privileged model for Oracle, select **SYSDBA** for the Role in the User Credentials window for the Oracle Connection Profile. See the [Oracle for User Credentials](/docs/accessanalyzer/12.0/admin/settings/connection/create/oracle.md) topic for additional information. @@ -45,22 +45,22 @@ additional information. This Job uses Nmap to locate listening Oracle ports on servers by scanning for ports using the service Oracle TNS Listener or optionally using specified ports, such as 1521. The Nmap utility can -be downloaded from [nmap.org](http://www.nmap.org/). To run this job, the user needs to have a -permission to execute any PowerShell script on the local host if the host is running the Microsoft -Windows operating system. In addition, on the Windows host, PowerShell execution policy needs to be -sent as well. For example, to set the execution policy to `Unrestricted`, run the following command -on the PowerShell command line: +be downloaded from [nmap.org](http://www.nmap.org/). To run this job, the user needs permission to +execute any PowerShell script on the local host if the host runs the Microsoft Windows operating +system. In addition, you need to set the PowerShell execution policy on the Windows host. For +example, to set the execution policy to `Unrestricted`, run the following command on the PowerShell +command line: ``` Set-ExecutionPolicy -ExecutionPolicy Unrestricted           ``` -In case of Linux and UNIX hosts, the `plink` command needs to be executed on the Access Analyzer +For Linux and UNIX hosts, run the `plink` command on the Access Analyzer Console server to update the local file with the SSH keys. :::note -The plink utility in the Access Analyzer installation directory has to be used. A version -of plink gets installed with the Nmap utility. +Use the plink utility in the Access Analyzer installation directory. The Nmap utility +installs a version of plink. ::: @@ -77,11 +77,11 @@ C:\Program Files (x86)\Stealthbits\StealthAUDIT\plink   -store_new_k ## Oracle SID Discovery This Job collects the Oracle SID from discovered Oracle servers and uses WMI or SSH to collect -running Oracle processes from the Oracle servers. The process is used to determine the name of the +running Oracle processes from the Oracle servers. This process determines the name of the Oracle SID. When multiple Oracle instances are running on a server, each SID will have its own entry in this table. -This Job requires local administrator rights on the target hosts in order to read the running +This Job requires local administrator rights on the target hosts to read the running processes using either WMI or SSH. ## Oracle Instance Discovery @@ -117,12 +117,12 @@ ALTER USER %USERNAME% SET CONTAINER_DATA=ALL CONTAINER = CURRENT; ## Oracle Permission Auditing -The Oracle Permissions Scan job is responsible for collecting all permissions from all licensed +The Oracle Permissions Scan job collects all permissions from all licensed database types for all target instances. ### Oracle Database 19c Series Permissions -In order to collect permissions from Oracle Database 19c series, the user credential requires at +to collect permissions from Oracle Database 19c series, the user credential requires at least the following `SELECT` privilege on the targeted database for the following views and tables: - CDB_COL_PRIVS view @@ -189,7 +189,7 @@ GRANT SELECT ON DBA_TAB_PRIVS TO %USERNAME%; ### Oracle Database 12c Series Permissions -In order to collect permissions from Oracle Database 12c series, the user credential requires at +to collect permissions from Oracle Database 12c series, the user credential requires at least the following `SELECT` privilege on the targeted database for the following views and tables: - CDB_COL_PRIVS view @@ -233,7 +233,7 @@ GRANT SELECT ON SYS.USER$ TO %USERNAME%; ### Oracle Database 11g Series Permissions -In order to collect permissions from Oracle Database 11g series, the user credential requires at +to collect permissions from Oracle Database 11g series, the user credential requires at least the following `SELECT` privileges on the targeted database for the following views and tables: - DBA_COL_PRIVS view @@ -273,8 +273,7 @@ GRANT SELECT ON SYS.USER$ TO %USERNAME%; ## Oracle Sensitive Data Auditing -This job is responsible for identifying sensitive data that has been stored within target database -instances. +This job identifies sensitive data stored within target database instances. Before running this scan, ensure that Oracle database statistics are up to date at least for the targeted schema or tables. Use one of the following commands: @@ -286,7 +285,7 @@ EXEC DBMS_STATS.GATHER_TABLE_STATS('%SCHEMA_NAME%', ‘%TABLE_NAME%’); ### Oracle Database 12c Series Sensitive Data -In order to perform a sensitive data scan on Oracle database 12c series, the user credential +to perform a sensitive data scan on Oracle database 12c series, the user credential requires at least the following `SELECT` privileges on the targeted database for the following views: @@ -307,7 +306,7 @@ GRANT SELECT ON CDB_OBJECTS TO %USERNAME%; ### Oracle Database 11g Series Sensitive Data -In order to perform a sensitive data scan on Oracle database 11g series, the user credential +to perform a sensitive data scan on Oracle database 11g series, the user credential requires at least the following `SELECT` privileges on the targeted database for the following views: @@ -324,9 +323,12 @@ GRANT SELECT ON DBA_TAB_COLS TO %USERNAME%; GRANT SELECT ON DBA_OBJECTS TO %USERNAME%; ``` -Please note that the `SELECT` privilege needs to be granted individually on all sensitive data -tables to be targeted (more secure). To accomplish it, run the following command for each targeted -sensitive data table: +:::note +Grant the `SELECT` privilege individually on all sensitive data tables you want to target +(more secure). +::: + +To accomplish it, run the following command for each targeted sensitive data table: ``` GRANT SELECT ON %YOUR_SENSITIVE_DATA_TABLE% TO %USERNAME%; @@ -341,12 +343,11 @@ GRANT SELECT ANY TABLE TO %USERNAME%; ## Oracle Activity Auditing -This job is responsible for collecting audit data from configured database server audits on target -endpoints. +This job collects audit data from configured database server audits on target endpoints. ### Oracle Database 12c Series Activity Data -In order to perform an activity data scan on Oracle database 12c series, the user credential +to perform an activity data scan on Oracle database 12c series, the user credential requires at least the following `SELECT` privileges on the targeted database for the following views: @@ -363,8 +364,8 @@ GRANT SELECT ON CDB_COMMON_AUDIT_TRAIL TO %USERNAME%; GRANT SELECT ON UNIFIED_AUDIT_TRAIL TO %USERNAME%; ``` -If the audit trail mode is `QUEUED`, then audit records are not written to disk until the in-memory -queues are full. The following procedure explicitly flushes the queues to disk, so that the audit +If the audit trail mode is `QUEUED`, then Oracle doesn't write audit records to disk until the +in-memory queues are full. The following procedure explicitly flushes the queues to disk, so that the audit trail records are viewable in the `UNIFIED_AUDIT_TRAIL` view: ``` @@ -373,7 +374,7 @@ EXEC SYS.DBMS_AUDIT_MGMT.FLUSH_UNIFIED_AUDIT_TRAIL; ### Oracle Database 11g Series Activity Data -In order to perform an activity data scan on Oracle database 11g series, the user credential +to perform an activity data scan on Oracle database 11g series, the user credential required at least the following `SELECT` privileges on the targeted database for the following views: @@ -390,10 +391,10 @@ GRANT SELECT ON DBA_COMMON_AUDIT_TRAIL TO %USERNAME%; ## Oracle Users with Default Passwords Job -The 4-Oracle_DefaultPasswordUsers job is responsible for collecting usernames of users whose -passwords have not been updated since the database creation. +The 4-Oracle_DefaultPasswordUsers job collects usernames of users who haven't updated their +passwords since the database was created. -The user needs to have a `SELECT` privilege on `CDB_USERS_WITH_DEFPWD` table for Oracle container +The user needs `SELECT` privilege on `CDB_USERS_WITH_DEFPWD` table for Oracle container databases (version 12c and higher) or `DBA_USERS_WITH_DEFPWD` for the non-container database (any version below 12c). diff --git a/docs/accessanalyzer/12.0/requirements/databases/oracle/oracle.md b/docs/accessanalyzer/12.0/requirements/databases/oracle/oracle.md index 075ed31f9b..f25dc75429 100644 --- a/docs/accessanalyzer/12.0/requirements/databases/oracle/oracle.md +++ b/docs/accessanalyzer/12.0/requirements/databases/oracle/oracle.md @@ -6,7 +6,7 @@ sidebar_position: 40 # Target Oracle Requirements, Permissions, and Ports -The Access Analyzer for Databases Solution provides the ability to audit and monitor Oracle database +The Access Analyzer for Databases Solution lets you audit and monitor Oracle database environments to collect permissions, sensitive data, and activity events. It scans: - Oracle Database 12c diff --git a/docs/accessanalyzer/12.0/requirements/databases/postgresql.md b/docs/accessanalyzer/12.0/requirements/databases/postgresql.md index c57771625a..658ff9d630 100644 --- a/docs/accessanalyzer/12.0/requirements/databases/postgresql.md +++ b/docs/accessanalyzer/12.0/requirements/databases/postgresql.md @@ -6,7 +6,7 @@ sidebar_position: 50 # Target PostgreSQL Requirements, Permissions, and Ports -The Access Analyzer for Databases Solution provides the ability to audit and monitor PostgreSQL +The Access Analyzer for Databases Solution lets you audit and monitor PostgreSQL database environments to collect permissions and sensitive data. It scans: - Open Source PostgreSQL 9x through 12x diff --git a/docs/accessanalyzer/12.0/requirements/databases/redshift.md b/docs/accessanalyzer/12.0/requirements/databases/redshift.md index ec3a445d05..5bf5e07714 100644 --- a/docs/accessanalyzer/12.0/requirements/databases/redshift.md +++ b/docs/accessanalyzer/12.0/requirements/databases/redshift.md @@ -6,7 +6,7 @@ sidebar_position: 60 # Target Redshift Requirements, Permissions, and Ports -The Access Analyzer for Databases Solution provides the ability to audit and monitor Redshift +The Access Analyzer for Databases Solution lets you audit and monitor Redshift database environments to collect permissions and sensitive data. It scans: - Amazon AWS Redshift diff --git a/docs/accessanalyzer/12.0/requirements/dropbox/dropbox.md b/docs/accessanalyzer/12.0/requirements/dropbox/dropbox.md index 5f528fb984..077efd3c5b 100644 --- a/docs/accessanalyzer/12.0/requirements/dropbox/dropbox.md +++ b/docs/accessanalyzer/12.0/requirements/dropbox/dropbox.md @@ -10,8 +10,8 @@ The core components for Netwrix Access Analyzer (formerly Enterprise Auditor) ar Analyzer Console server, SQL Server, and Access Information Center. See the [Requirements](/docs/accessanalyzer/12.0/requirements/overview.md) topic for the core requirements. -In addition to these, integration with either the Netwrix Activity Monitor or the Netwrix Threat -Prevention is required for event activity data to be scanned. See the +In addition to these, you need to integrate either the Netwrix Activity Monitor or the Netwrix +Threat Prevention to scan event activity data. See the [Netwrix Activity Monitor Documentation](https://helpcenter.netwrix.com/category/activitymonitor) or the [Netwrix Threat Prevention Documentation](https://helpcenter.netwrix.com/category/threatprevention) @@ -24,7 +24,7 @@ environment requirements. **RAM, CPU, and Disk Space** -These are dependent upon the size of the target environment: +These depend on the size of the target environment: | Environment | Large | Medium – Small | | ----------- | ----------------------- | ---------------------- | @@ -34,20 +34,19 @@ These are dependent upon the size of the target environment: | Disk Space | 30 GB | 30 GB | :::note -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the -minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host.For -example, if the job is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are -required (8x2=16). +If you run Sensitive Data Discovery (SDD) scans, increase the minimum amount of RAM. Each +thread requires a minimum of 2 additional GB of RAM per host. For example, if you configure the +job to scan 8 hosts at a time, you need an extra 16 GB of RAM (8x2=16). ::: **Sensitive Data Discovery Auditing Requirement** :::note -The appropriate JDK (Java) version for Sensitive Data Discovery is installed on the -server. The JDK deployed is prepackaged and does not require any configuration; it has been -preconfigured to work with Access Analyzer and should never be customized through Java. It will not -conflict with other JDKs or Java Runtimes in the same environment. +Access Analyzer installs the appropriate JDK (Java) version for Sensitive Data Discovery on +the server. This JDK comes prepackaged and preconfigured to work with Access Analyzer, requires no +additional configuration, and you should never customize it through Java. It doesn't conflict with +other JDKs or Java Runtimes in the same environment. ::: @@ -55,7 +54,7 @@ conflict with other JDKs or Java Runtimes in the same environment. **RAM, CPU, and Disk Space** -These are dependent upon the size of the target environment. +These depend on the size of the target environment. | Environment | Large | Medium – Small | | ------------------------ | ----------------------- | ---------------------- | diff --git a/docs/accessanalyzer/12.0/requirements/dropbox/target.md b/docs/accessanalyzer/12.0/requirements/dropbox/target.md index c1a3bc8f66..a5ed13345d 100644 --- a/docs/accessanalyzer/12.0/requirements/dropbox/target.md +++ b/docs/accessanalyzer/12.0/requirements/dropbox/target.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Target Dropbox Requirements, Permissions, and Ports -The Access Analyzer for AWS Solution provides the ability to audit Dropbox. It scans: +The Access Analyzer for AWS Solution lets you audit Dropbox. It scans: - Dropbox @@ -20,10 +20,10 @@ This solution employs the following data collector to scan the target environmen - Dropbox Team Administrator -The DropboxAccess Data Collector requires the generation of an access token that is used to -configure the Connection Profile for Dropbox. The access token is generated from within the Dropbox -Access Auditor Data Collector Wizard on the Scan Options page. Once the access token is copied into -a Connection Profile for Dropbox, it will be saved and does not need to be generated again. See the +The DropboxAccess Data Collector requires generating an access token to configure the Connection +Profile for Dropbox. You generate the access token from within the Dropbox Access Auditor Data +Collector Wizard on the Scan Options page. After you copy the access token into a Connection +Profile for Dropbox, Access Analyzer saves it and you don't need to generate it again. See the [DropboxAccess: Scan Options](/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/scanoptions.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/requirements/entraid/entraid.md b/docs/accessanalyzer/12.0/requirements/entraid/entraid.md index a921d8a2cf..2ff3de58b0 100644 --- a/docs/accessanalyzer/12.0/requirements/entraid/entraid.md +++ b/docs/accessanalyzer/12.0/requirements/entraid/entraid.md @@ -22,7 +22,7 @@ for target environment requirements. **RAM, CPU, and Disk Space** -These are dependent upon the size of the target environment: +These depend on the size of the target environment: | Environment | Large | Medium – Small | | ----------- | ----------------------- | ---------------------- | @@ -35,7 +35,7 @@ These are dependent upon the size of the target environment: **RAM, CPU, and Disk Space** -These are dependent upon the size of the target environment. +These depend on the size of the target environment. | Environment | Large | Medium – Small | | ------------------------ | ----------------------- | ---------------------- | diff --git a/docs/accessanalyzer/12.0/requirements/entraid/entraid/access.md b/docs/accessanalyzer/12.0/requirements/entraid/entraid/access.md index 1d06b6dcf1..3bc34aa749 100644 --- a/docs/accessanalyzer/12.0/requirements/entraid/entraid/access.md +++ b/docs/accessanalyzer/12.0/requirements/entraid/entraid/access.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Microsoft Entra ID Auditing Configuration -The Access Analyzer for Entra ID Solution provides the ability to audit Microsoft Entra ID, formerly +The Access Analyzer for Entra ID Solution lets you audit Microsoft Entra ID, formerly Azure Active Directory. It scans: - Microsoft Entra ID (formerly Azure AD) @@ -23,19 +23,19 @@ Microsoft Entra ID. **Configuration Settings from the Registered Application** -The following settings are needed from your tenant once you have registered the application: +The following settings are needed from your tenant after you register the application: - Client ID – This is the Application (client) ID for the registered application - Key – This is the Client Secret Value generated when a new secret is created :::warning - It is not possible to retrieve the value after saving the new key. It must be - copied first. + You can't retrieve the value after saving the new key, so copy it + first. ::: :::note -In order to add custom attributes, you will also need to know the Tenant name of the Entra +to add custom attributes, you will also need to know the Tenant name of the Entra ID environment. ::: @@ -67,10 +67,10 @@ The following permissions are required: ## Register a Microsoft Entra ID Application -Follow the steps to register Access Analyzer with Microsoft Entra ID. +Register Access Analyzer with Microsoft Entra ID. :::note -The steps below are for registering an app through the Microsoft Entra admin center. These +The following steps are for registering an app through the Microsoft Entra admin center. These steps may vary slightly if you use a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: @@ -92,14 +92,14 @@ registrations. **Step 5 –** Click **Register**. The Overview page for the newly registered app opens. Review the newly created registered -application. Now that the application has been registered, permissions need to be granted to it. +application. Now that you've registered the application, grant it permissions. ## Grant Permissions to the Registered Application -Follow the steps to grant permissions to the registered application. +Grant permissions to the registered application. :::note -The steps below are for registering an app through the Microsoft Entra admin center. These +The following steps are for registering an app through the Microsoft Entra admin center. These steps may vary slightly if you use a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: @@ -131,11 +131,11 @@ tab. Select the following permissions: **Step 6 –** Click **Grant Admin Consent for [tenant]**. Then click **Yes** in the confirmation window. -Now that the permissions have been granted to it, the Connection Profile and host settings for -Access Analyzer need to be collected. +Now that you've granted the permissions, collect the Connection Profile and host settings for +Access Analyzer. :::note -Additional permissions need to be configured to collect Microsoft Entra roles information. +Configure additional permissions to collect Microsoft Entra roles information. See the [Microsoft Entra Roles Auditing Configuration](/docs/accessanalyzer/12.0/requirements/entraid/entraid/entraroles.md) topic for additional information. @@ -144,10 +144,10 @@ topic for additional information. ## Identify the Client ID -Follow the steps to find the registered application's Client ID. +Find the registered application's Client ID. :::note -The steps below are for registering an app through the Microsoft Entra admin center. These +The following steps are for registering an app through the Microsoft Entra admin center. These steps may vary slightly if you use a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: @@ -161,7 +161,7 @@ list. **Step 3 –** Save this value in a text file. -This Application (client) ID value is needed for the Access Analyzer Connection Profile and the +You need this Application (client) ID value for the Access Analyzer Connection Profile and the Custom Attributes page of the AzureADInventory Data Collector. See the [Azure Active Directory for User Credentials](/docs/accessanalyzer/12.0/admin/settings/connection/create/entraid.md) topic and the @@ -170,18 +170,18 @@ topic for additional information. Next generate the application’s Client Secre ## Generate the Client Secret Key -Follow the steps to find the registered application's Client Secret, create a new key, and save its +Find the registered application's Client Secret, create a new key, and save its value when saving the new key. :::note -The steps below are for registering an app through the Microsoft Entra admin center. These +The following steps are for registering an app through the Microsoft Entra admin center. These steps may vary slightly if you use a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: :::warning -It is not possible to retrieve the value after saving the new key. It must be copied +You can't retrieve the value after saving the new key, so copy it first. ::: @@ -208,17 +208,17 @@ list. **Step 5 –** Click **Add** to generate the key. :::warning -If this page is left before the key is copied, then the key is not retrievable, and -this process will have to be repeated. +If you leave this page before copying the key, the key becomes unretrievable, and +you'll have to repeat this process. ::: -**Step 6 –** The Client Secret will be displayed in the Value column of the table. You can use the +**Step 6 –** The Value column of the table shows the Client Secret. You can use the Copy to clipboard button to copy the Client Secret. **Step 7 –** Save this value in a text file. -This Client Secret value is needed for the Access Analyzer Connection Profile and the Custom +You need this Client Secret value for the Access Analyzer Connection Profile and the Custom Attributes page of the AzureADInventory Data Collector. See the [Azure Active Directory for User Credentials](/docs/accessanalyzer/12.0/admin/settings/connection/create/entraid.md) topic and the @@ -227,10 +227,10 @@ topic for additional information. ## Identify the Tenant Name -Follow the steps to find the Tenant Name where the registered application resides. +Find the Tenant Name where the registered application resides. :::note -The steps below are for registering an app through the Microsoft Entra admin center. These +The following steps are for registering an app through the Microsoft Entra admin center. These steps may vary slightly if you use a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: @@ -245,7 +245,7 @@ names** to open the Custom domain names list. **Step 4 –** Save this value in a text file. -This is needed for the Host List and the Custom Attributes page of the AzureADInventory Data +You need this for the Host List and the Custom Attributes page of the AzureADInventory Data Collector. See the [Microsoft Entra ID Connection Profile & Host List](/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/configurejob.md) and [AzureADInventory: Custom Attributes](/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/customattributes.md) diff --git a/docs/accessanalyzer/12.0/requirements/entraid/entraid/entraroles.md b/docs/accessanalyzer/12.0/requirements/entraid/entraid/entraroles.md index 21766ce6df..5a62cc8c8d 100644 --- a/docs/accessanalyzer/12.0/requirements/entraid/entraid/entraroles.md +++ b/docs/accessanalyzer/12.0/requirements/entraid/entraid/entraroles.md @@ -22,20 +22,20 @@ Microsoft Entra ID. **Configuration Settings from the Registered Application** -The following settings are needed from your tenant once you have registered the application: +The following settings are needed from your tenant after you register the application: - Client ID – This is the Application (client) ID for the registered application - Key – This is the Client Secret Value generated when a new secret is created :::warning - It is not possible to retrieve the value after saving the new key. It must be - copied first. + You can't retrieve the value after saving the new key, so copy it + first. ::: :::note -It is recommended to use the same registered application for the Access and Entra roles -auditing configurations. In this case, these values are only needed once for the tenant. See the +Netwrix recommends using the same registered application for the Access and Entra roles +auditing configurations. In this case, you only need these values once for the tenant. See the [Microsoft Entra ID Registered Application](#microsoft-entra-id-registered-application) topic for additional information. ::: @@ -62,26 +62,26 @@ The following permissions are required for Microsoft Entra Roles auditing: ## Microsoft Entra ID Registered Application -You must have a registered application to assign the required permissions to. It is recommended to -use the same registered application that is used for access auditing using the AzureADInventory data +You must have a registered application to assign the required permissions to. Netwrix recommends +using the same registered application you use for access auditing with the AzureADInventory data collector. See the [Register a Microsoft Entra ID Application](/docs/accessanalyzer/12.0/requirements/entraid/entraid/access.md#register-a-microsoft-entra-id-application) topic for additional information on registering an application. -The Client ID and Key for the registered application are required for the Access Analyzer connection +You need the Client ID and Key for the registered application for the Access Analyzer connection profile. If, as recommended, you are using a single registered application for the tenant, then you -do not need to add an additional user credential in the connection profile. If you create a separate -registered application for Entra roles auditing, then the Client ID and Key for this must be added +don't need to add an additional user credential in the connection profile. If you create a separate +registered application for Entra roles auditing, add the Client ID and Key for this to the connection profile as an additional Azure Active Directory user credential. See the [Microsoft Entra ID Connection Profile & Host List](/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/configurejob.md) topic for additional information. -Once you have the registered application, the next step is to grant it the required permissions for +After you have the registered application, the next step is to grant it the required permissions for the Entra data collector. ## Grant Permissions to the Registered Application -Follow the steps to grant the required permissions to the registered application. +Grant the required permissions to the registered application. **Step 1 –** Log in to [Azure Portal](https://portal.azure.com/). @@ -104,12 +104,12 @@ tab. Select the following permissions: **Step 7 –** Click **Grant Admin Consent for [tenant]**. Then click **Yes** in the confirmation window. -The permissions have been granted to the registered application. Next, you need to create a custom +You've granted the permissions to the registered application. Next, create a custom role and assign the necessary resource manager permissions. ## Create Custom Role with Resource Manager Permissions -Follow the steps to create the required custom role and assign the necessary permissions. +Create the required custom role and assign the necessary permissions. **Step 1 –** In Azure portal, navigate to **Management groups** within the Microsoft Entra tenant. @@ -120,9 +120,9 @@ Follow the steps to create the required custom role and assign the necessary per group. :::info -It is recommended to create this custom role at the root management group level. -This ensures that all of necessary information on the Microsoft Entra environment is collected. -Creating the custom role on a lower level management group can result in missing data. +Netwrix recommends creating this custom role at the root management group level. +This ensures Access Analyzer collects all the necessary information on the Microsoft Entra +environment. Creating the custom role on a lower level management group can result in missing data. ::: @@ -173,7 +173,7 @@ permissions. ::: -**Step 7 –** Once the permissions are configured, click **Create** on the Review + create tab to +**Step 7 –** After you configure the permissions, click **Create** on the Review + create tab to finish creating the custom role. Now that you have created the custom role with the necessary permissions, you must assign this @@ -181,7 +181,7 @@ custom role to the registered application. ## Assign the Custom Role to the App Registration -Follow the steps to assign the custom role to your registered application. +Assign the custom role to your registered application. **Step 1 –** Navigate back to Access Control (IAM) in the Tenant Root Group. @@ -197,5 +197,5 @@ application from the list and click **Select**. **Step 5 –** On the Review + assign tab, click **Review + assign** to complete the role assignment. -The registered application has now been configured with all the necessary permissions for Entra +You've now configured the registered application with all the necessary permissions for Entra roles scans. diff --git a/docs/accessanalyzer/12.0/requirements/entraid/entraid/overview.md b/docs/accessanalyzer/12.0/requirements/entraid/entraid/overview.md index 186f93242a..6e3849ba23 100644 --- a/docs/accessanalyzer/12.0/requirements/entraid/entraid/overview.md +++ b/docs/accessanalyzer/12.0/requirements/entraid/entraid/overview.md @@ -11,8 +11,8 @@ formerly Azure Active Directory. ## Auditing Permissions -It is necessary to register Access Analyzer as a web application to the targeted Microsoft Entra ID -in order for Access Analyzer to scan the environment. This generates the Client ID (App ID) and Key +Register Access Analyzer as a web application in the targeted Microsoft Entra ID so it can scan the +environment. This generates the Client ID (App ID) and Key (App Key) needed for the Connection Profile credentials and the Custom Attributes Import Wizard page. @@ -20,9 +20,9 @@ See the [Microsoft Entra ID Auditing Configuration](/docs/accessanalyzer/12.0/re ## Entra Roles Permissions -To collect Microsoft Entra roles information from the Microsoft Entra tenant additional permissions -are required to be assigned to the registered application. This includes creating a custom role with -the required resource manager permissions. +To collect Microsoft Entra roles information from the Microsoft Entra tenant, you must assign +additional permissions to the registered application. This includes creating a custom role with the +required resource manager permissions. See the [Microsoft Entra Roles Auditing Configuration](/docs/accessanalyzer/12.0/requirements/entraid/entraid/entraroles.md) diff --git a/docs/accessanalyzer/12.0/requirements/exchange/exchange.md b/docs/accessanalyzer/12.0/requirements/exchange/exchange.md index 6eb9b84750..a58b03ab65 100644 --- a/docs/accessanalyzer/12.0/requirements/exchange/exchange.md +++ b/docs/accessanalyzer/12.0/requirements/exchange/exchange.md @@ -10,8 +10,8 @@ The core components for Netwrix Access Analyzer (formerly Enterprise Auditor) ar Analyzer Console server, SQL Server, and Access Information Center. See the [Requirements](/docs/accessanalyzer/12.0/requirements/overview.md) topic for the core requirements. -In addition to these, integration with either the Netwrix Activity Monitor or the Netwrix Threat -Prevention is required for event activity data to be scanned. See the +In addition to these, you need to integrate either the Netwrix Activity Monitor or the Netwrix +Threat Prevention to scan event activity data. See the [Netwrix Activity Monitor Documentation](https://helpcenter.netwrix.com/category/activitymonitor) or the [Netwrix Threat Prevention Documentation](https://helpcenter.netwrix.com/category/threatprevention) @@ -26,7 +26,7 @@ See the following topics for target environment requirements: **RAM, CPU, and Disk Space** -These are dependent upon the size of the target environment: +These depend on the size of the target environment: | Environment | Extra Large – Large | Medium – Small | | ----------- | ------------------------- | ----------------------- | @@ -36,20 +36,19 @@ These are dependent upon the size of the target environment: | Disk Space | 120 GB | 120 GB | :::note -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the -minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host.For -example, if the job is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are -required (8x2=16). +If you run Sensitive Data Discovery (SDD) scans, increase the minimum amount of RAM. Each +thread requires a minimum of 2 additional GB of RAM per host. For example, if you configure the +job to scan 8 hosts at a time, you need an extra 16 GB of RAM (8x2=16). ::: **Sensitive Data Discovery Auditing Requirement** :::note -The appropriate JDK (Java) version for Sensitive Data Discovery is installed on the -server. The JDK deployed is prepackaged and does not require any configuration; it has been -preconfigured to work with Access Analyzer and should never be customized through Java. It will not -conflict with other JDKs or Java Runtimes in the same environment. +Access Analyzer installs the appropriate JDK (Java) version for Sensitive Data Discovery on +the server. This JDK comes prepackaged and preconfigured to work with Access Analyzer, requires no +additional configuration, and you should never customize it through Java. It doesn't conflict with +other JDKs or Java Runtimes in the same environment. ::: @@ -58,7 +57,7 @@ conflict with other JDKs or Java Runtimes in the same environment. The following are additional requirements for the Access Analyzer Console server specific to running the Exchange Solution: -- Outlook should not be installed +- Outlook shouldn't be installed - StealthAUDIT MAPI CDO installed (for MAPI- based data collectors). See the [StealthAUDIT MAPI CDO Installation](/docs/accessanalyzer/12.0/install/mapicdo/installation.md) topic for additional information. @@ -87,7 +86,7 @@ Analyzer. **RAM, CPU, and Disk Space** -These are dependent upon the size of the target environment. +These depend on the size of the target environment. | Environment | Extra-Large | Large | Medium | Small | | ------------------------ | ------------------ | ----------------- | ----------------- | ---------------- | diff --git a/docs/accessanalyzer/12.0/requirements/exchange/exchangeonline/access.md b/docs/accessanalyzer/12.0/requirements/exchange/exchangeonline/access.md index 01fedd1e17..22ffcf91d8 100644 --- a/docs/accessanalyzer/12.0/requirements/exchange/exchangeonline/access.md +++ b/docs/accessanalyzer/12.0/requirements/exchange/exchangeonline/access.md @@ -6,8 +6,8 @@ sidebar_position: 10 # Exchange Online Auditing Configuration -It is necessary to register Access Analyzer as a web application to the targeted Microsoft Entra ID, -formerly Azure Active Directory, in order for Access Analyzer to scan the environment. This +Register Access Analyzer as a web application in the targeted Microsoft Entra ID, formerly Azure +Active Directory, so it can scan the environment. This generates the Client ID (App ID) and self-signed certificate (Certificate Thumbprint) needed for the Connection Profile credentials and/or the Custom Attributes Import Wizard page. See [Microsoft Support](https://docs.microsoft.com/en-us/azure/active-directory/active-directory-reporting-api-prerequisites-azure-portal) @@ -21,7 +21,7 @@ Microsoft Entra ID. **Configuration Settings from the Registered Application** -The following settings are needed from your tenant once you have registered the application: +The following settings are needed from your tenant after you register the application: - Client ID – This is the Application (client) ID for the registered application - Tenant name – This is the primary domain name of the Microsoft Entra tenant @@ -30,9 +30,9 @@ The following settings are needed from your tenant once you have registered the Configure Modern Authentication for Exchange Online using EX_RegisterAzureAppAuth Instant Job -Registering a Microsoft Entra ID application and provisioning it to grant permissions to Exchange -Online can be automated using the EX_RegisterAzureAppAuth job from the Access Analyzer Instant Job -Library. The EX_RegisterAzureAppAuth job uses the PowerShell Data Collector to automatically +You can automate registering a Microsoft Entra ID application and provisioning it to grant +permissions to Exchange Online using the EX_RegisterAzureAppAuth job from the Access Analyzer +Instant Job Library. The EX_RegisterAzureAppAuth job uses the PowerShell Data Collector to automatically configure modern authentication for Exchange Online. It requires: - A Connection Profile containing a Microsoft Entra ID Global Admin credential with an Account Type @@ -48,7 +48,7 @@ configure modern authentication for Exchange Online. It requires: - Azure AD PowerShell module installed on targeted hosts :::note - If the module is not already installed, the job will attempt to install it. + If the module isn't already installed, the job will attempt to install it. ::: @@ -58,7 +58,7 @@ configure modern authentication for Exchange Online. It requires: Install-Module AzureAD ``` - - TLS 1.2 is required for the Azure AD PowerShell module. Run the following command to configure + - You need TLS 1.2 for the Azure AD PowerShell module. Run the following command to configure it: ``` @@ -107,12 +107,12 @@ The following permissions are required: ## Create Self–Signed Certificate -A self signed certificate needs to be created on the Access Analyzer console server. This is used by -Access Analyzer to connect to the Microsoft Entra tenant. +Create a self-signed certificate on the Access Analyzer console server. Access Analyzer uses this +certificate to connect to the Microsoft Entra tenant. Follow the steps create the self-signed certificate. -**Step 1 –** To generate a certificate, use the sample PowerShell command below: +**Step 1 –** To generate a certificate, use the following sample PowerShell command: - Change the following parameters in the sample PowerShell command. See the Microsoft [New-SelfSignedCertificate](https://docs.microsoft.com/en-us/powershell/module/pki/new-selfsignedcertificate) @@ -122,9 +122,9 @@ Follow the steps create the self-signed certificate. certificate - Subject – A unique name for the new App (always starts with CN=, to denote a canonical name) - FriendlyName – Same as Subject name minus the canonical name prefix - - NotAfter – A datetime string denoting the certificate's expiration date - in the above sample, - Get-Date.AddYears(11) specifies that the certificate will expire 11 years from the current - datetime + - NotAfter – A datetime string denoting the certificate's expiration date - in the following + sample, Get-Date.AddYears(11) specifies that the certificate will expire 11 years from the + current datetime Example PowerShell: @@ -138,7 +138,7 @@ $certPath variable (see Step 1). :::note The environment variable `SAINSTALLDIR` always points to the base Access Analyzer install -directory; simply append the PrivateAssemblies to point to that folder with the following cmdlet: +directory; append the PrivateAssemblies to point to that folder with the following cmdlet: ::: @@ -167,15 +167,15 @@ Export-PfxCertificate -Cert $cert -FilePath "$($env:SAINSTALLDIR)PrivateAssembli [Export-PfxCertificate](https://docs.microsoft.com/en-us/powershell/module/pki/export-pfxcertificate) article for additional information. -The self signed certificate has been created. The next steps are to create a Microsoft Entra ID +You've created the self-signed certificate. The next steps are to create a Microsoft Entra ID application and then upload this certificate to it. ## Register a Microsoft Entra ID Application -Follow the steps to register Access Analyzer with Microsoft Entra ID. +Register Access Analyzer with Microsoft Entra ID. :::note -The steps below are for registering an app through the Microsoft Entra admin center. These +The following steps are for registering an app through the Microsoft Entra admin center. These steps may vary slightly if you use a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: @@ -197,14 +197,14 @@ registrations. **Step 5 –** Click **Register**. The Overview page for the newly registered app opens. Review the newly created registered -application. Now that the application has been registered, permissions need to be granted to it. +application. Now that you've registered the application, grant it permissions. ## Upload Self-Signed Certificate Follow the steps upload your self-signed certificate. :::note -The steps below are for registering an app through the Microsoft Entra admin center. These +The following steps are for registering an app through the Microsoft Entra admin center. These steps may vary slightly if you use a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: @@ -225,17 +225,17 @@ Optionally add a Description. **Step 6 –** Click **Add**. -The Certificate Thumbprint of this uploaded certificate is needed for the Access Analyzer Connection +You need the Certificate Thumbprint of this uploaded certificate for the Access Analyzer Connection Profile. See the [Exchange Modern Authentication for User Credentials](/docs/accessanalyzer/12.0/admin/settings/connection/create/exchangemodernauth.md) topic for additional information. ## Grant Permissions to the Registered Application -Follow the steps to grant permissions to the registered application. +Grant permissions to the registered application. :::note -The steps below are for registering an app through the Microsoft Entra admin center. These +The following steps are for registering an app through the Microsoft Entra admin center. These steps may vary slightly if you use a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: @@ -264,15 +264,15 @@ uses tab to find and select Office 365 Exchange Online. Select the following per **Step 6 –** Click **Grant Admin Consent for [tenant]**. Then click **Yes** in the confirmation window. -Now that the permissions have been granted to it, the Connection Profile and host settings for -Access Analyzer need to be collected. +Now that you've granted the permissions, collect the Connection Profile and host settings for +Access Analyzer. ## Identify the Tenant's Name -Follow the steps to find the Tenant Name where the registered application resides. +Find the Tenant Name where the registered application resides. :::note -The steps below are for registering an app through the Microsoft Entra admin center. These +The following steps are for registering an app through the Microsoft Entra admin center. These steps may vary slightly if you use a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: @@ -287,16 +287,16 @@ names** to open the Custom domain names list. **Step 4 –** Save this value in a text file. -This is needed for the Access Analyzer Connection Profile. See the +You need this for the Access Analyzer Connection Profile. See the [Exchange Modern Authentication for User Credentials](/docs/accessanalyzer/12.0/admin/settings/connection/create/exchangemodernauth.md) topic for additional information. Next identify the application’s Client ID. ## Identify the Client ID -Follow the steps to find the registered application's Client ID. +Find the registered application's Client ID. :::note -The steps below are for registering an app through the Microsoft Entra admin center. These +The following steps are for registering an app through the Microsoft Entra admin center. These steps may vary slightly if you use a different Microsoft portal. See the relevant Microsoft documentation for additional information. ::: @@ -310,6 +310,6 @@ list. **Step 3 –** Save this value in a text file. -This is needed for the Access Analyzer Connection Profile. See the +You need this for the Access Analyzer Connection Profile. See the [Exchange Modern Authentication for User Credentials](/docs/accessanalyzer/12.0/admin/settings/connection/create/exchangemodernauth.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/requirements/exchange/exchangeonline/exchangeonline.md b/docs/accessanalyzer/12.0/requirements/exchange/exchangeonline/exchangeonline.md index bb35b58f1e..91d4468f0a 100644 --- a/docs/accessanalyzer/12.0/requirements/exchange/exchangeonline/exchangeonline.md +++ b/docs/accessanalyzer/12.0/requirements/exchange/exchangeonline/exchangeonline.md @@ -6,7 +6,7 @@ sidebar_position: 30 # Target Exchange Online Requirements, Permissions, and Ports -The Access Analyzer for Exchange Solution provides the ability to audit Exchange Online. It scans: +The Access Analyzer for Exchange Solution lets you audit Exchange Online. It scans: - Exchange Online (Limited) diff --git a/docs/accessanalyzer/12.0/requirements/exchange/support/mailflow.md b/docs/accessanalyzer/12.0/requirements/exchange/support/mailflow.md index a0a46ca194..a6be61cf11 100644 --- a/docs/accessanalyzer/12.0/requirements/exchange/support/mailflow.md +++ b/docs/accessanalyzer/12.0/requirements/exchange/support/mailflow.md @@ -8,7 +8,7 @@ sidebar_position: 10 The ExchangeMetrics Data Collector collects Mail-Flow metrics from the Exchange Message Tracking Logs on the Exchange servers. Some examples of this include server volume and message size -statistics. This data collector utilizes an applet to process and collect summarized metrics from +statistics. This data collector uses an applet to process and collect summarized metrics from the Message Tracking Log. 1. HUB Metrics Job Group Requirement @@ -17,7 +17,7 @@ In addition to the permissions required by the ExchangeMetrics Data Collector, t Profile assigned to the 1. HUB Metrics Job Group requires the following permission and User Rights (based on default settings): -- Member of the local Administrator group on the targeted Exchange server(s) where the Hub Transport +- Member of the local Administrator group on the targeted Exchange servers where the Hub Transport service is running - Log on as a Service Group Policy: @@ -30,7 +30,7 @@ Profile assigned to the 1. HUB Metrics Job Group requires the following permissi This is required because the ExchangeMetrics Data Collector is an applet-based data collector. It requires -- Member of the local Administrator group on the targeted Exchange server(s) +- Member of the local Administrator group on the targeted Exchange servers This grants access to the Message Tracking Logs and the ability to create the `SA_ExchangeMetricsData` folder, which will contain the applet files and the processed message @@ -39,8 +39,8 @@ tracking log files stored inside a SQLite database for each day. For example: \\ExchangeServerName\c$\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\MessageTracking -If there have been additional security or permission modifications on the server(s), the following -rights and policies may need to be enabled on the targeted host: +If there have been additional security or permission modifications on the servers, you may need to +enable the following rights and policies on the targeted host: - Ensure the Administrator group has been granted Full Control over Message Tracking Log Directories - WMI Control (`wmimgmt.msc`) > Right Click Properties > Security diff --git a/docs/accessanalyzer/12.0/requirements/exchange/support/mapi.md b/docs/accessanalyzer/12.0/requirements/exchange/support/mapi.md index 2c0064aca9..ac4250d0fb 100644 --- a/docs/accessanalyzer/12.0/requirements/exchange/support/mapi.md +++ b/docs/accessanalyzer/12.0/requirements/exchange/support/mapi.md @@ -10,7 +10,7 @@ The Exchange2K, ExchangeMailbox, and ExchangePublicFolder data collectors have o requirements. These data collectors supports Exchange 2010 through Exchange 2013. Since this data collectors are -MAPI-based, they do not support Exchange Online, Exchange 2019, nor Exchange 2016. +MAPI-based, they don't support Exchange Online, Exchange 2019, nor Exchange 2016. All MAPI-based data collectors have the following prerequisites: diff --git a/docs/accessanalyzer/12.0/requirements/exchange/support/powershell.md b/docs/accessanalyzer/12.0/requirements/exchange/support/powershell.md index 4deac51328..0ef9cfee03 100644 --- a/docs/accessanalyzer/12.0/requirements/exchange/support/powershell.md +++ b/docs/accessanalyzer/12.0/requirements/exchange/support/powershell.md @@ -6,8 +6,8 @@ sidebar_position: 30 # Exchange PowerShell Permissions -The ExchangePS Data Collector utilizes PowerShell to collect various information from the Exchange -environment. This data collector utilizes Remote PowerShell to collect information about Exchange +The ExchangePS Data Collector uses PowerShell to collect various information from the Exchange +environment. This data collector uses Remote PowerShell to collect information about Exchange Users Configuration, Mailboxes, Public Folders, and Exchange Online Mail-Flow. **Job Group Requirements in Addition to ExchangePS** @@ -47,13 +47,12 @@ assigned to these job groups requires the following permissions: **Remote PowerShell and Windows Authentication Enabled** -The Remote PowerShell and Windows Authentication configurations for Exchanges servers are required -to be enabled on at least one Exchange server running the Client Access Service so that the -ExchangePS Data Collector can make a remote PowerShell connection and authenticate through Access -Analyzer. +You must enable the Remote PowerShell and Windows Authentication configurations for Exchange +servers on at least one Exchange server running the Client Access Service so that the ExchangePS +Data Collector can make a remote PowerShell connection and authenticate through Access Analyzer. Access Analyzer passes credentials saved in the Connection Profile to the data collector so that it -is able to connect to the targeted host. This requires the Exchange server to allow for Windows +can connect to the targeted host. This requires the Exchange server to allow for Windows Authentication. See the [Enable Remote PowerShell for ExchangePS Data Collector](#enable-remote-powershell-for-exchangeps-data-collector) topic and the @@ -62,19 +61,19 @@ topic for additional information. **View-Only Organization Management Role Group** -This is required so the ExchangePS Data Collector is able to run the various Exchange PowerShell +This is required so the ExchangePS Data Collector can run the various Exchange PowerShell cmdlets. **Public Folder Management** -This permission is only required if utilizing the ExchangePublicFolder Data Collector or +This permission is only required if using the ExchangePublicFolder Data Collector or ExchangeMailbox Data Collector, as well as the PublicFolder or Mailbox Action Modules. This is -required in order to make a connection through the MAPI protocol. The following job group requires +required to make a connection through the MAPI protocol. The following job group requires the Public Folder Management Role Group: - **5. Public Folders** > **Ownership** -If not running this collection, then this permission is not required. +If not running this collection, then this permission isn't required. **Mailbox Search Role** @@ -93,14 +92,14 @@ topic for additional information. There are five different scoping options within this data collector. Since not all query categories support all scoping options, No Scoping is an option. If there are no scoping options available, -then the data collector should be run against the host specified in the Summary page of the data -collector wizard. +run the data collector against the host specified in the Summary page of the data collector +wizard. **No Scoping** This option will gather information about the entire Exchange Organization. When using the applet, the data collector will gather information about the Exchange Forest in which the Access Analyzer -Console currently resides. For Remote PowerShell, the data collector will gather information about +Console resides. For Remote PowerShell, the data collector will gather information about the Exchange Organization to which the Remote PowerShell connection was made. This refers to the server entered in the Client Access Server (CAS) field of the global configuration from the **Settings** > **Exchange** node or on the Scope Page of the data collector wizard. See the @@ -111,7 +110,7 @@ information. This option will gather information about any databases which are chosen. When using the applet, the data collector will return databases in the Scope by DB page of the data collector wizard for the -Exchange Organization in which the Access Analyzer Console currently resides, as well as, only +Exchange Organization in which the Access Analyzer Console resides, as well as, only return information about those databases. For Remote PowerShell, the data collector will return databases in the Scope by DB page of the data collector wizard for the Exchange Forest, as well as, only return information about those databases. See the @@ -122,7 +121,7 @@ additional information. This option will gather information about any mailboxes which are chosen. When using the applet, the data collector will return mailboxes in the Scope by Mailboxes page of the data collector wizard for -the Exchange Forest in which the Access Analyzer Console currently resides, as well as, only return +the Exchange Forest in which the Access Analyzer Console resides, as well as, only return information about those mailboxes. For Remote PowerShell, the data collector will return mailboxes in the Scope by Mailboxes page of the data collector wizard for the Exchange Forest, as well as, only return information about those mailboxes. See the @@ -135,14 +134,14 @@ This option will gather information about objects which reside on the chosen ser this option, the data collector will then use the Host List applied to the job’s **Configure** > **Hosts** node as the servers scoping list. When using the applet, the data collector will deploy a process to the targeted host to run the PowerShell on that server. For Remote PowerShell, the data -collector will deploy no applet and utilize the WinRM protocol to gather information about the +collector will deploy no applet and use the WinRM protocol to gather information about the objects on that server. **Scope by Public Folder** This option will gather information about any public folders which are chosen. When using the applet, the data collector will return public folders in the Scope by Public Folders page of the -data collector wizard for the Exchange Forest in which the Access Analyzer Console currently +data collector wizard for the Exchange Forest in which the Access Analyzer Console resides, as well as, only return information about those public folders. For Remote PowerShell, the data collector will return public folders in the Scope by Public Folders page of the data collector wizard for the Exchange Forest, as well as, only return information about those public folders. See @@ -152,7 +151,7 @@ topic for additional information. ## Enable Remote PowerShell for ExchangePS Data Collector -Follow these steps to enable Remote PowerShell. +Enable Remote PowerShell. **Step 1 –** On the server that Access Analyzer will connect with Remote PowerShell, open PowerShell. @@ -165,7 +164,7 @@ Enable-PSRemoting **Step 3 –** When prompted, type `A` and `A` again to enable the appropriate services and protocols. -Remote PowerShell has been enabled. See the Microsoft +You've enabled Remote PowerShell. See the Microsoft [Tip: Enable and Use Remote Commands in Windows PowerShell](https://technet.microsoft.com/en-us/library/ff700227.aspx) article for additional information. @@ -173,9 +172,8 @@ Next, enable Windows Authentication for PowerShell Virtual Directory on the same ## Enable Windows Authentication for PowerShell Virtual Directory -Once Remote PowerShell has been enabled on an Exchange Server in the environment, it is necessary to -also enable Windows Authentication for the PowerShell Virtual Directory on the same Exchange server. -Follow these steps to enable Windows Authentication. +After you enable Remote PowerShell on an Exchange Server in the environment, enable Windows +Authentication for the PowerShell Virtual Directory on the same Exchange server. **Step 1 –** On the server where Remote PowerShell was enabled, open the Internet Information Services (IIS) Manager. @@ -187,13 +185,13 @@ Services (IIS) Manager. ![IIS Enable Windows Authentication](/images/accessanalyzer/12.0/requirements/solutions/exchange/iismanagerauth.webp) -**Step 3 –** Right-click on **Windows Authentication** and select **Enable**. +**Step 3 –** Right-click **Windows Authentication** and select **Enable**. -Windows Authentication has been enabled for the PowerShell Virtual Directory. +You've enabled Windows Authentication for the PowerShell Virtual Directory. ## Create Custom Application Impersonation Role in Exchange -Follow the steps to create the custom Application Impersonation role. The process is the same for +Create the custom Application Impersonation role. The process is the same for Exchange 2010 Service Pack 1 through Exchange 2019 and Exchange Online. **Step 1 –** Within the Exchange Admin Center, navigate to the permissions section and select admin @@ -223,8 +221,8 @@ The new role group appears in the list. ## Enable Exchange Mailbox Access Auditing -The 4. Mailboxes Job Group requires the Exchange Mailbox Access Auditing to be enabled. In order to -collect Mailbox Access Auditing events, it is necessary to enable Exchange Mailbox Access Auditing +The 4. Mailboxes Job Group requires you to enable Exchange Mailbox Access Auditing. To +collect Mailbox Access Auditing events, enable Exchange Mailbox Access Auditing for Exchange. See the following Microsoft articles: - Exchange Online – diff --git a/docs/accessanalyzer/12.0/requirements/exchange/support/remoteconnections.md b/docs/accessanalyzer/12.0/requirements/exchange/support/remoteconnections.md index 6e6a747aa1..ba14f43263 100644 --- a/docs/accessanalyzer/12.0/requirements/exchange/support/remoteconnections.md +++ b/docs/accessanalyzer/12.0/requirements/exchange/support/remoteconnections.md @@ -7,8 +7,8 @@ sidebar_position: 20 # Exchange Remote Connections Permissions The SMARTLog Data Collector processes the IIS Logs on the server running the Client Access Service -(CAS) to return information about the remote connections being made to Exchange. This data collector -uses an applet to process and collect the IIS Logs. +(CAS) to return information about remote connections to Exchange. This data collector uses an applet +to process and collect the IIS Logs. 2. CAS Metrics Job Group Requirement @@ -16,7 +16,7 @@ In addition to the permissions required by the SMARTLog Data Collector, the Conn assigned to the 2. CAS Metrics Job Group requires the following permissions and User Rights (based on default settings): -- Member of the local Administrator group on the targeted Exchange server(s) where the Client Access +- Member of the local Administrator group on the targeted Exchange servers where the Client Access Service is running - Log on as a Service Group Policy: @@ -39,7 +39,7 @@ example: **\\ExchangeServerName\c$\Program Files (x86)\STEALTHbits\StealthAUDIT\LogProcessor** -If there have been additional security or permission modifications on the server(s), the following +If there have been additional security or permission modifications on the servers, the following rights and policies may need to be enabled on the targeted host: - Ensure the Administrator group has been granted Full Control over IIS Log Directories diff --git a/docs/accessanalyzer/12.0/requirements/exchange/support/webservicesapi.md b/docs/accessanalyzer/12.0/requirements/exchange/support/webservicesapi.md index e7d63767fd..e40ef43db1 100644 --- a/docs/accessanalyzer/12.0/requirements/exchange/support/webservicesapi.md +++ b/docs/accessanalyzer/12.0/requirements/exchange/support/webservicesapi.md @@ -6,7 +6,7 @@ sidebar_position: 40 # Exchange Web Services API Permissions -The EWSMailbox and EWSPublicFolder data collectors utilizes Exchange Web Services API to access and +The EWSMailbox and EWSPublicFolder data collectors uses Exchange Web Services API to access and communicate with Exchange. These data collectors collect statistical, content, permission, and sensitive data information from mailboxes and public folders. diff --git a/docs/accessanalyzer/12.0/requirements/exchange/target.md b/docs/accessanalyzer/12.0/requirements/exchange/target.md index db0bc2bb8c..4ca285699f 100644 --- a/docs/accessanalyzer/12.0/requirements/exchange/target.md +++ b/docs/accessanalyzer/12.0/requirements/exchange/target.md @@ -24,16 +24,16 @@ The following are requirements for the Exchange servers to be scanned: - Enable Remote PowerShell on one Client Access Server (CAS) - Enable Windows Authentication for the PowerShell Virtual Directory on the same CAS - .NET Framework 4.5+ installed on all Exchange servers to be targeted -- WINRM Service installed on all Exchange servers to be targeted as a back up in the event of a +- WINRM Service installed on all Exchange servers to be targeted as a back up if there is a remote PowerShell failure - Within the Access Analyzer Console, the global **Settings > Exchange** node must be configured :::note - For Exchange 2013, 2016, and 2019 – If the global Settings have been configured for - "MAPI over HTTP," then an actual CAS server name was supplied and will be used by the ExchangePS - Data Collector. If the global Settings have been configured for "MAPI over HTTPS," then the - global Settings will have a web address instead of an actual server. Therefore, each ExchangePS - query requires the CAS server to be set as the specific server on the Category page. See the + For Exchange 2013, 2016, and 2019 – If you configure the global Settings for "MAPI over HTTP," + you supply an actual CAS server name, and the ExchangePS Data Collector uses it. If you configure + the global Settings for "MAPI over HTTPS," the global Settings use a web address instead of an + actual server. In this case, each ExchangePS query requires you to set the CAS server as the + specific server on the Category page. See the [ExchangePS Data Collector & Client Access Server](/docs/accessanalyzer/12.0/solutions/exchange/recommended.md) topic for a list of queries for which this would apply. ::: @@ -103,7 +103,7 @@ additional information. **For Exchange Mail Flow with ExchangeMetrics Data Collector** -- Member of the local Administrator group on the targeted Exchange server(s) +- Member of the local Administrator group on the targeted Exchange servers See the [Exchange Mail-Flow Permissions](/docs/accessanalyzer/12.0/requirements/exchange/support/mailflow.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystem.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystem.md index 0cc53e9160..0d8a5945f6 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystem.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystem.md @@ -10,11 +10,11 @@ The core components for Netwrix Access Analyzer (formerly Enterprise Auditor) ar Analyzer Console server, SQL Server, and Access Information Center. See the [Requirements](/docs/accessanalyzer/12.0/requirements/overview.md) topic for the core requirements. -The File System solution can be configure to use Proxy servers either an applet or as a service. See -the [File System Scan Options](/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/scanoptions.md) topic for additional information. +You can configure the File System solution to use Proxy servers, either as an applet or as a service. +See the [File System Scan Options](/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/scanoptions.md) topic for additional information. -In addition to these, integration with either the Netwrix Activity Monitor or the Netwrix Threat -Prevention is required for event activity data to be scanned. See the +You also need to integrate with either Netwrix Activity Monitor or Netwrix Threat Prevention to scan +event activity data. See the [Netwrix Activity Monitor Documentation](https://helpcenter.netwrix.com/category/activitymonitor) or the [Netwrix Threat Prevention Documentation](https://helpcenter.netwrix.com/category/threatprevention) @@ -29,7 +29,7 @@ See the following topics for target environment requirements: **RAM, CPU, and Disk Space** -These are dependent upon the size of the target environment: +These depend on the size of the target environment: | Environment | Enterprise | Extra-Large | Large | Medium | Small | | ----------- | ------------------------------ | ----------------------------------- | ----------------------------------- | ----------------------------------- | ----------------------------------- | @@ -38,26 +38,26 @@ These are dependent upon the size of the target environment: | Cores | 8 CPU | 8 CPU | 8 CPU | 4 CPU | 2 CPU | | Disk Space | 1.5 TB | 770 GB | 470 GB | 270 GB | 130 GB | -The above recommended disk space sizing information is based on the needs of Access Analyzer as well +This recommended disk space sizing information is based on the needs of Access Analyzer as well as the File System solution for running Permission scans with default configuration (500 MB per million files and folders), that means no tag collection, file-level scanning, activity, or sensitive data. -- For tag collection, add 125 MB per million documents to the totals above +- For tag collection, add 125 MB per million documents to these totals - For activity collection, add 250 MB per million files and folders and another 125 MB per million - activity events to the totals above + activity events to these totals - For sensitive data collection, add 500 MB per million files and folders and another 1%-10% of the total size of the documents scanned for sensitive data (depending on targeted document types and - selected criteria) to the totals above + selected criteria) to these totals -For example, in order to scan 200 million files and folders, of which 10 million files will be +For example, to scan 200 million files and folders, of which 10 million files will be scanned for tag collection and sensitive data with a total size of 6 TB, you would need: 160 GB for permission collection + 1.25 GB for tag collection (10x125 MB) + 100 GB for sensitive data collection (200x500 MB) + 600 GB additional for sensitive data collection (10% of 6 TB) = 861.25 GB total disk space. :::note -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the +If you run Sensitive Data Discovery (SDD) scans, you need to increase the minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. By default, SDD scans are configured to run two concurrent threads. For example, if the job is configured to scan 8 hosts at a time with two concurrent SDD threads, then an extra 32 GB of RAM are @@ -68,16 +68,16 @@ required (8x2x2=32). **Additional Server Considerations for File System Scans** If Data Activity Tracking for NAS is required or if NetApp Filers running Clustered Data ONTAP are -in scope, reducing latency between the scanning server and the target device is highly recommended. -Additional hardware may be required, especially if the target NAS devices are not collocated with +in scope, you should reduce latency between the scanning server and the target device. +Additional hardware may be required, especially if the target NAS devices aren't collocated with the Access Analyzer Console server. **Sensitive Data Discovery Auditing Requirement** :::note The appropriate JDK (Java) version for Sensitive Data Discovery is installed on the -server. The JDK deployed is prepackaged and does not require any configuration; it has been -preconfigured to work with Access Analyzer and should never be customized through Java. It will not +server. The JDK deployed is prepackaged and doesn't require any configuration; it's +preconfigured to work with Access Analyzer, so don't customize it through Java. It will not conflict with other JDKs or Java Runtimes in the same environment. ::: @@ -85,7 +85,7 @@ conflict with other JDKs or Java Runtimes in the same environment. Permissions on the Console Server to Run File System Scans In most cases the Access Analyzer user is a member of the local Administrators group on the -application server. However, if the Role Based Access usage is employed, then the user assigned the +application server. However, if you use Role Based Access, the user assigned the role of Job Initiator (for manual execution) or the credential used for the Schedule Service Account (for scheduled execution) must have the following permissions to execute File System scans in local mode, applet mode, or proxy mode with applet: @@ -96,12 +96,12 @@ mode, applet mode, or proxy mode with applet: - Administrators These permissions grant the credential the ability to create a high integrity token capable of -leveraging the “Back up files and directories” from where the Access Analyzer executable is run. +leveraging the “Back up files and directories” right on the host where the Access Analyzer executable runs. Additionally, the credential must have `WRITE` access to the `…\StealthAUDIT\FSAA` folder in the -installation directory. This is required by either the user account running the Access Analyzer -application, when manually executing jobs from the console, or the Schedule Service Account assigned -within Access Analyzer, when running jobs as a scheduled tasks. +installation directory. Either the user account running the Access Analyzer application (when +manually executing jobs from the console) or the Schedule Service Account assigned within Access +Analyzer (when running jobs as scheduled tasks) needs this access. See the [File System Scan Options](/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/scanoptions.md) topic and the [File System Supported Platforms](/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/filesystems.md) topic for permissions required to scan @@ -111,7 +111,7 @@ the environment. **RAM, CPU, and Disk Space** -These are dependent upon the size of the target environment. +These depend on the size of the target environment. | Environment | Enterprise | Extra-Large | Large | Medium | Small | | ------------------------ | ------------------------------ | ----------------------------------- | ----------------------------------- | ----------------------------------- | ----------------------------------- | diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/azurefiles.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/azurefiles.md index e5204363ae..c6695ac311 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/azurefiles.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/azurefiles.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Azure Files Target Requirements -Azure Files is a fully managed, cloud-based file sharing service from Microsoft that allows users to +Azure Files is a fully managed, cloud-based file sharing service from Microsoft. It lets users access file shares from anywhere as a virtual network drive. Access Analyzer uses the File System solution to execute Access Auditing (FSAA) and Sensitive Data Discovery Auditing scans on Azure Files. @@ -20,8 +20,8 @@ required both in Access Analyzer and the Azure environments: ## Create Host List -A host list containing the desired target Azure hosts must be created and assigned to the collection -jobs. You can create the host list with either of the following two methods: +You must create a host list containing the Azure hosts you want to target and assign it to the +collection jobs. You can create the host list with either of the following two methods: - Use the FS_AzureTenantScan instant job to create the host list automatically. See the [FS_AzureTenantScan Job](/docs/accessanalyzer/12.0/solutions/filesystem/collection/fs_azuretenantscan.md) topic for @@ -55,7 +55,7 @@ applet, and credentials for each storage account. These should be configured as - Client ID – The name of the storage account - For example, if the target is `files.file.core.windows.net` then the Client ID should be - `files`. It is not case sensitive. + `files`. It isn't case sensitive. - Key – Connection string value for access keys on the storage account @@ -72,21 +72,21 @@ Azure Files scans require the following configuration of the job and query perfo ### Jobs Targeting Azure Files For FSAA and SEEK scans targeting Azure Files storage accounts, you must clear the **Skip Hosts that -do not respond to PING** option in the job properties. +don't respond to PING** option in the job properties. ![Skip Hosts option on Performance tab of the Job Properties window](/images/accessanalyzer/12.0/requirements/target/config/skiphostsoption.webp) -Right-click on the required scan job in the Jobs tree, and select **Properties** to open the Job -Properties window. Navigate to the Performance tab, and ensure the **Skip Hosts that do not respond -to PING** option is not selected. See the +Right-click the required scan job in the Jobs tree, and select **Properties** to open the Job +Properties window. Navigate to the Performance tab, and ensure the **Skip Hosts that don't respond +to PING** option isn't selected. See the [Job Properties](/docs/accessanalyzer/12.0/admin/jobs/job/properties/overview.md) and [Performance Tab](/docs/accessanalyzer/12.0/admin/jobs/job/properties/performance.md) topics for additional information. ### Query Configuration Considerations -Last Access Time (LAT) preservation is not supported for Azure Files scans. This option must not be -selected in the query for the FSAA or SEEK scan job. +Last Access Time (LAT) preservation isn't supported for Azure Files scans. Don't select this option +in the query for the FSAA or SEEK scan job. ![Last Access Time (LAT) preservation option in FSAA DC wizard](/images/accessanalyzer/12.0/requirements/target/config/latpreservationoption.webp) diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/azureinformationprotection.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/azureinformationprotection.md index 9e8fa50972..5d7963377a 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/azureinformationprotection.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/azureinformationprotection.md @@ -6,15 +6,15 @@ sidebar_position: 20 # **Azure Information Protection Target Requirements** -Microsoft® Azure is a cloud-based computing platform that provides a range of services, such as file storage. Azure uses Azure Information Protection (AIP) labels, a Microsoft tool used to classify and protect stored files. Access Analyzer employs the File System Solution to execute Access Auditing (FSAA) and/or Sensitive Data Discovery Auditing scans in order to find AIP Protection labels and scan protected (i.e. encrypted) files for sensitive data. +Microsoft® Azure is a cloud-based computing platform that provides a range of services, such as file storage. Azure uses Azure Information Protection (AIP) labels, a Microsoft tool used to classify and protect stored files. Access Analyzer employs the File System Solution to execute Access Auditing (FSAA) and/or Sensitive Data Discovery Auditing scans to find AIP Protection labels and scan protected (i.e. encrypted) files for sensitive data. -This document provides information needed to properly configure access required by Access Analyzer to successfully scan for Azure Information Protection labels in a targeted environment. +This document explains how to configure the access Access Analyzer needs to scan for Azure Information Protection labels in a target environment. :::info **NOTE** -Access Analyzer does not scan for AIP Marking labels, only Protection labels. +Access Analyzer doesn't scan for AIP Marking labels, only Protection labels. ::: @@ -39,7 +39,7 @@ Ensure the following prerequisites are met before configuring AIP scanning: * The PowerShell `Install-Module` command requires: * PowerShell 5.0 (Run as Administrator) * Windows Server 2016 and later -* Active Directory Rights Management Services Client 2.1 installed on the server where the FSAA applet or proxy is being run +* Active Directory Rights Management Services Client 2.1 installed on the server where the FSAA applet or proxy runs ### Rights Management Service Client Installation @@ -75,7 +75,7 @@ Read the System Requirements and Install Instructions provided by Microsoft to c :::warning - This will disappear once you leave the page! + This disappears when you leave the page. ::: 4. Add API permissions @@ -93,7 +93,7 @@ Read the System Requirements and Install Instructions provided by Microsoft to c ## **Enable the Account as an AIP Super User using PowerShell** -Follow the steps to enable the Service Principal Account in AIP as a Super User: +Enable the Service Principal Account in AIP as a Super User: :::info @@ -135,7 +135,7 @@ The Service Principal Account is now successfully added to the Azure Information ## **Access Analyzer Configurations** -Before Access Analyzer can scan for AIP labels, two configurations must be done prior to the initial scan. +Complete two configurations before Access Analyzer can scan for AIP labels. * [Azure Connection Profile](https://docs.netwrix.com/docs/accessanalyzer/12_0/requirements/filesystem/filesystems/azureinformationprotection#azure-connection-profile) * [Configure FSAA Data Collector](https://docs.netwrix.com/docs/accessanalyzer/12_0/requirements/filesystem/filesystems/azureinformationprotection#configure-fsaa-data-collector) diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellcelerravnx/access.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellcelerravnx/access.md index 2b7f11c235..9266641319 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellcelerravnx/access.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellcelerravnx/access.md @@ -14,7 +14,7 @@ Follow the steps assign group membership through Computer Management. **Step 1 –** Open Computer Management (`compmgmt.msc`). -**Step 2 –** Right-click on the Computer Management (local) node and select Connect to another +**Step 2 –** Right-click the Computer Management (local) node and select Connect to another computer. **Step 3 –** Enter the name of the Dell device in the textbox and click OK. diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellcelerravnx/activity/activity.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellcelerravnx/activity/activity.md index 50bb133989..3dd675aef1 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellcelerravnx/activity/activity.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellcelerravnx/activity/activity.md @@ -11,15 +11,15 @@ events. All audit data can be forwarded to the Dell Common Event Enabler (CEE). listens for all events coming through the Dell CEE and translates all relevant information into entries in the Log files or syslog messages. -Complete the following checklist prior to configuring the Activity Monitor to monitor the host. +Complete the following checklist before configuring the Activity Monitor to monitor the host. Instructions for each item of the checklist are detailed within the following sections. **Checklist Item 1: Plan Deployment** -- Prior to beginning the deployment, gather the following: +- Before beginning the deployment, gather the following: - - DNS name of Celerra or VNX CIFS share(s) to be monitored - - Data Mover or Virtual Data Mover hosting the share(s) to be monitored + - DNS name of Celerra or VNX CIFS shares to be monitored + - Data Mover or Virtual Data Mover hosting the shares to be monitored - Account with access to the CLI - Download the Dell CEE from: @@ -38,9 +38,9 @@ Instructions for each item of the checklist are detailed within the following se - Important: - - Open MS-RPC ports between the Dell device and the Windows proxy server(s) where the Dell CEE + - Open MS-RPC ports between the Dell device and the Windows proxy servers where the Dell CEE is installed - - Dell CEE 8.4.2 through Dell CEE 8.6.1 are not supported for use with the VCAPS feature + - Dell CEE 8.4.2 through Dell CEE 8.6.1 aren't supported for use with the VCAPS feature - Dell CEE requires .NET Framework 3.5 to be installed on the Windows proxy server - See the [Install & Configure Dell CEE](/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellcelerravnx/activity/installcee.md) topic for instructions. diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellcelerravnx/activity/installcee.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellcelerravnx/activity/installcee.md index 3f79cf2f19..e6009a33fa 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellcelerravnx/activity/installcee.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellcelerravnx/activity/installcee.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Install & Configure Dell CEE -Dell CEE should be installed on a Windows or a Linux server. The Dell CEE software is not a Netwrix +Dell CEE should be installed on a Windows or a Linux server. The Dell CEE software isn't a Netwrix product. Dell customers have a support account with Dell to access the download. :::tip @@ -20,10 +20,10 @@ Monitor agent will be deployed (recommended) or on any other Windows or Linux se ::: -Follow the steps to install the Dell CEE. +To install Dell CEE, complete the following steps. **Step 1 –** Obtain the latest CEE install package from Dell and any additional license required for -this component. It is recommended to use the most current version. +this component. Use the most current version. **Step 2 –** Follow the instructions in the Dell [Using the Common Event Enabler on Windows Platforms](https://www.dell.com/support/home/en-us/product-support/product/common-event-enabler/docs) @@ -33,7 +33,7 @@ guide to install and configure the CEE. The installation will add two services t - EMC CEE Monitor (Display Name: EMC CEE Monitor) :::info -The latest version of .NET Framework and Dell CEE is recommended to use with the +Use the latest version of .NET Framework and Dell CEE with the asynchronous bulk delivery (VCAPS) feature. ::: @@ -41,14 +41,14 @@ asynchronous bulk delivery (VCAPS) feature. See the [CEE Debug Logs](/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellunity/activity/validate.md#cee-debug-logs) section for information on troubleshooting issues related to Dell CEE. -After Dell CEE installation is complete, it is necessary to -[Connect Data Movers to the Dell CEE Server](#connect-data-movers-to-the-dell-cee-server). +After Dell CEE installation is complete, +[connect the Data Movers to the Dell CEE Server](#connect-data-movers-to-the-dell-cee-server). ## Configure Dell Registry Key Settings There may be situations when Dell CEE needs to be installed on a different Windows server than the -one where the Activity Monitor activity agent is deployed. In those cases it is necessary to -manually set the Dell CEE registry key to forward events. +one where the Activity Monitor activity agent is deployed. In those cases, manually set the Dell +CEE registry key to forward events. **Step 1 –** Open the Registry Editor (run regedit). @@ -58,12 +58,12 @@ manually set the Dell CEE registry key to forward events. **HKEY_LOCAL_MACHINE\SOFTWARE\EMC\CEE\CEPP\AUDIT\Configuration** -**Step 3 –** Right-click on **Enabled** and select Modify. The Edit DWORD Value window opens. +**Step 3 –** Right-click **Enabled** and select Modify. The Edit DWORD Value window opens. **Step 4 –** In the Value data field, enter the value of 1. Click OK, and the Edit DWORD Value window closes. -**Step 5 –** Right-click on **EndPoint** and select Modify. The Edit String window opens. +**Step 5 –** Right-click **EndPoint** and select Modify. The Edit String window opens. **Step 6 –** In the Value data field, enter the StealthAUDIT value with the IP Address for the Windows proxy server hosting the Activity Monitor activity agent. Use the following format: @@ -94,13 +94,13 @@ Mover. administrative account should have a $ character in the terminal. :::note -Do not use a # charter. +Don't use a # charter. ::: **Step 2 –** Create or retrieve the `cepp.conf` file. -If there is not a `cepp.conf` file on the Data Mover(s), use a text editor to create a new blank +If there isn't a `cepp.conf` file on the Data Movers, use a text editor to create a new blank file in the home directory named `cepp.conf`. The following is an example command if using the text editor ‘vi’ to create a new blank file: @@ -126,7 +126,7 @@ The Activity Monitor requires the following parameters to be set in the `cepp.co - `pool name= ` - This should equal the name assigned to the configuration container. This container is composed - of the server(s) IP Address or FQDN where the Dell CEE is installed and where the list of + of the servers IP Address or FQDN where the Dell CEE is installed and where the list of events to be monitored is located. It can be named as desired but must be a pool name. - `servers= ` - This should equal the IP Address or FQDN of the Windows server where the Dell CEE is @@ -175,7 +175,7 @@ The Activity Monitor requires the following parameters to be set in the `cepp.co postevents=CloseModified|CloseUnmodified|CreateDir|CreateFile|DeleteDir|DeleteFile|RenameDir|RenameFile|SetAclDir|SetAclFile -**Step 4 –** Move the `cepp.conf` file to the Data Mover(s) root file system. Run the following +**Step 4 –** Move the `cepp.conf` file to the Data Movers root file system. Run the following command: **$ server_file [DATA_MOVER_NAME]‑put cepp.conf cepp.conf** @@ -201,7 +201,7 @@ Then verify the CEPA status using the following command: **server_cepp [DATA_MOVER_NAME] -service –status** -Once the `cepp.config` file has been configured, it is time to configure and enable monitoring with +After you configure the `cepp.config` file, configure and enable monitoring with the Activity Monitor. See the [Netwrix Activity Monitor Documentation](https://helpcenter.netwrix.com/category/activitymonitor) for additional information. diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellcelerravnx/activity/validate.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellcelerravnx/activity/validate.md index 2664d4594e..6e33035bb2 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellcelerravnx/activity/validate.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellcelerravnx/activity/validate.md @@ -6,8 +6,8 @@ sidebar_position: 20 # Validate Setup -Once the Activity Monitor agent is configured to monitor the Dell device, the automated -configuration must be validated to ensure events are being monitored. +After you configure the Activity Monitor agent to monitor the Dell device, validate the automated +configuration to ensure it's monitoring events. ## Validate Dell CEE Registry Key Settings @@ -18,13 +18,12 @@ topic for information on manually setting the registry key. ::: -After the Activity Monitor activity agent has been configured to monitor the Dell device, it will -configure the Dell CEE automatically if it is installed on the same server as the agent. This needs -to be set manually in the rare situations where it is necessary for the Dell CEE to be installed on -a different server than the Windows proxy server(s) where the Activity Monitor activity agent is -deployed. +After you configure the Activity Monitor activity agent to monitor the Dell device, the agent +automatically configures Dell CEE if it's installed on the same server. In rare cases, if you +install Dell CEE on a different server than the Windows proxy servers where the activity agent is +deployed, you need to set this manually. -If the monitoring agent is not registering events, validate that the EndPoint is accurately set. +If the monitoring agent isn't registering events, validate that the EndPoint is accurately set. Open the Registry Editor (run regedit). For the synchronous real-time delivery mode (AUDIT), use the following steps. @@ -90,22 +89,22 @@ additional information. ## Validate Dell CEE Services are Running -After the Activity Monitor Activity Agent has been configured to monitor the Dell device, the Dell -CEE services should be running. If the Activity Agent is not registering events and the EndPoint is +After you configure the Activity Monitor Activity Agent to monitor the Dell device, the Dell +CEE services should be running. If the Activity Agent isn't registering events and the EndPoint is set accurately, validate that the Dell CEE services are running. Open the Services (run `services.msc`). ![services](/images/activitymonitor/8.0/config/dellpowerstore/services.webp) -The following services laid down by the Dell CEE installer should have Running as their status: +The following services installed by the Dell CEE installer should show Running as their status: - Dell CAVA - Dell CEE Monitor ## Dell CEE Debug Logs -If an issue arises with communication between the Dell CEE and the Activity Monitor, the debug logs -need to be enabled for troubleshooting purposes. Follow the steps. +If an issue arises with communication between the Dell CEE and the Activity Monitor, enable the +debug logs for troubleshooting. Follow the steps. **Step 6 –** In the Activity Monitor Console, change the **Trace level** value in the lower right corner to Trace. @@ -121,19 +120,19 @@ and Disable monitoring. **HKEY_LOCAL_MACHINE\SOFTWARE\EMC\CEE\Configuration** -**Step 10 –** Right-click on **Debug** and select Modify. The Edit DWORD Value window opens. In the +**Step 10 –** Right-click **Debug** and select Modify. The Edit DWORD Value window opens. In the Value data field, enter the value of 3F. Click OK, and the Edit DWORD Value window closes. :::note -If the Debug DWORD Value does not exist, it needs to be added. +If the Debug DWORD Value doesn't exist, add it. ::: -**Step 11 –** Right-click on **Verbose** and select Modify. The Edit DWORD Value window opens. In +**Step 11 –** Right-click **Verbose** and select Modify. The Edit DWORD Value window opens. In the Value data field, enter the value of 3F. Click OK, and the Edit DWORD Value window closes. :::note -If the Verbose DWORD Value does not exist, it needs to be added. +If the Verbose DWORD Value doesn't exist, add it. ::: @@ -154,7 +153,7 @@ and Enable monitoring. - Use the **Collect Logs** button to collect debug logs from the activity agent :::info -After the logs have been gathered and sent to Netwrix Support, reset these +After you gather the logs and send them to Netwrix Support, reset these configurations. ::: diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellcelerravnx/overview.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellcelerravnx/overview.md index 74c72d46ea..7132c844af 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellcelerravnx/overview.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellcelerravnx/overview.md @@ -38,12 +38,12 @@ topic for additional information. Troubleshooting Dell Celerra & Dell VNX Denied Access Errors -If there are folders to which the credential is denied access, it is likely that the Backup -Operators group does not have the “Back up files and directories” right. In that case, it is -necessary to assign additional the “Back up files and directories” right to those groups or to -create a new local group, using Computer Management from a Windows server. Then assign rights to it -using the CelerraManagementTool.msc plugin, which is available to Dell customers. For further -information, see the Celerra guide Using Windows Administrative Tools on VNX found on the Celerra +If there are folders to which the credential is denied access, the Backup +Operators group likely doesn't have the “Back up files and directories” right. In that case, +assign the “Back up files and directories” right to those groups, or +create a new local group using Computer Management on a Windows server. Then assign rights to it +using the CelerraManagementTool.msc plugin, which is available to Dell customers. For more +information, see the Celerra guide Using Windows Administrative Tools on VNX on the Celerra website. ## Access & Sensitive Data Auditing Port Requirements @@ -65,7 +65,7 @@ server: - Membership in the local Administrators group - READ and WRITE access to the archive location for Archiving feature only -It is also necessary to enable the Remote Registry Service on the Activity Agent server. +You also need to enable the Remote Registry Service on the Activity Agent server. For integration between the Activity Monitor and Access Analyzer, the credential used by Access Analyzer to read the activity log files must have also have this permission. @@ -88,9 +88,9 @@ instructions. **Activity Monitor Archive Location** -If the activity log files are being archived, configurable within the Netwrix Activity Monitor -Console, then the credential used by Access Analyzer to read the activity log files must also have -READ and WRITE permissions on the archive location. +If you configure the Netwrix Activity Monitor Console to archive activity log files, the credential +used by Access Analyzer to read the activity log files must also have READ and WRITE permissions on +the archive location. ## Activity Auditing Port Requirements @@ -101,9 +101,9 @@ are required for communication between the Agent server and the Netwrix Activity | -------------------------------- | -------- | ----- | ------------------- | | Activity Monitor to Agent Server | TCP | 4498 | Agent Communication | -The Windows firewall rules need to be configured on the Windows server, which require certain -inbound rules be created if the scans are running in applet mode. These scans operate over a default -port range, which cannot be specified via an inbound rule. For more information, see the Microsoft +Configure the Windows firewall rules on the Windows server. If the scans run in applet mode, create +the required inbound rules. These scans operate over a default port range, which you can't specify +in an inbound rule. For more information, see the Microsoft [Connecting to WMI on a Remote Computer](https://msdn.microsoft.com/en-us/library/windows/desktop/aa389290(v=vs.85).aspx) article. @@ -119,7 +119,7 @@ Monitor Activity Agent server and the target Dell device: Additional Firewall Rules for Integration between Access Analyzer and Activity Monitor -Firewall settings are dependent upon the type of environment being targeted. The following firewall +Firewall settings depend on the type of environment being targeted. The following firewall settings are required for communication between the agent server and the Access Analyzer Console: | Communication Direction | Protocol | Ports | Description | diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellpowerscale/activity/activity.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellpowerscale/activity/activity.md index bf57ca9e42..e29b48eaaa 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellpowerscale/activity/activity.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellpowerscale/activity/activity.md @@ -20,15 +20,15 @@ initiated the activity. The stored events are then forwarded by the node to the concurrently to several instances. At this point, Dell CEE forwards the audit event to a defined endpoint, such as Activity Monitor agent. -Complete the following checklist prior to configuring Activity Monitor to monitor the host. +Complete the following checklist before configuring Activity Monitor to monitor the host. Instructions for each item of the checklist are detailed within the following sections. **Checklist Item 1: Plan Deployment** -- Prior to beginning the deployment, gather the following: +- Before beginning the deployment, gather the following: - - DNS name of Isilon/PowerScale CIFS share(s) to be monitored - - Access Zone(s) containing the CIFS shares to be monitored + - DNS name of Isilon/PowerScale CIFS shares to be monitored + - Access Zones containing the CIFS shares to be monitored - Account with access to the OneFS UI or CLI - Download the Dell CEE from: @@ -36,8 +36,8 @@ Instructions for each item of the checklist are detailed within the following se :::info You can achieve higher throughput and fault tolerance by monitoring the -Isilon/PowerScale cluster with more than one pair of Dell CEE and Activity Monitor Agent. The -activity will be evenly distributed between the pairs. +Isilon/PowerScale cluster with more than one pair of Dell CEE and Activity Monitor Agent. Activity +Monitor evenly distributes the activity between the pairs. ::: @@ -79,20 +79,20 @@ Checklist Item 3: Configure Auditing on the Dell Isilon/PowerScale Cluster - Important: - Value of the **Storage Cluster Name** field must exactly match the name entered for the - monitored host in the Activity Monitor Console. If the Storage Cluster Name cannot be modified + monitored host in the Activity Monitor Console. If the Storage Cluster Name can't be modified (for example, another 3rd party depends on it), you need to set the Host Aliases parameter in the Activity Monitor Console. Otherwise, if for some reason the Storage Cluster Name must be - left empty, one can list OneFS cluster node names in the Host Aliases. + left empty, you can list OneFS cluster node names in the Host Aliases. - - If the Storage Cluster Name is not empty, set the Host Aliases parameter to its value + - If the Storage Cluster Name isn't empty, set the Host Aliases parameter to its value - If the Storage Cluster Name is empty, set the Host Aliases to a semicolon-separated list of OneFS node names - Include all Access Zones to be monitored in the auditing configuration - As soon as the first CEE is installed, Isilon/PowerScale will start to send all activity, including all previous audit events, to the agent. The start time can be modified to exclude - previously recorded audit events to prevent the agent from becoming overloaded with data. It - can be done using OneFS CLI only with isi audit modify command to edit the start time. + previously recorded audit events to prevent the agent from becoming overloaded with data. You + can only do this using the OneFS CLI with the isi audit modify command to edit the start time. - Start time command: @@ -123,7 +123,7 @@ For automatic configuration, an account needs to be provisioned with the followi - ISI_PRIV_AUDIT -Privileges can be added to a role and then the role can be assigned to an account. Use the following +You can add privileges to a role and then assign the role to an account. Use the following commands to create a role, add privileges, and assign the role to an account: ``` @@ -133,7 +133,7 @@ isi auth roles modify activity_monitor --add-priv-write="ISI_PRIV_AUDIT" isi auth roles modify activity_monitor --add-user="ACCOUNT_NAME" ``` -Assigned privileges can be verified with the following command: +Verify assigned privileges with the following command: ``` isi auth mapping token "ACCOUNT_NAME" diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellpowerscale/activity/installcee.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellpowerscale/activity/installcee.md index 4d26538774..95c5237b9e 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellpowerscale/activity/installcee.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellpowerscale/activity/installcee.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Install Dell CEE -Dell CEE should be installed on a Windows or a Linux server. The Dell CEE software is not a Netwrix +Dell CEE should be installed on a Windows or a Linux server. The Dell CEE software isn't a Netwrix product. Dell customers have a support account with Dell to access the download. :::tip @@ -20,10 +20,10 @@ Monitor agent will be deployed (recommended) or on any other Windows or Linux se ::: -Follow the steps to install the Dell CEE. +To install Dell CEE, complete the following steps. **Step 1 –** Obtain the latest CEE install package from Dell and any additional license required for -this component. It is recommended to use the most current version. +this component. Use the most current version. **Step 2 –** Follow the instructions in the Dell [Using the Common Event Enabler on Windows Platforms](https://www.dell.com/support/home/en-us/product-support/product/common-event-enabler/docs) @@ -33,7 +33,7 @@ guide to install and configure the CEE. The installation will add two services t - EMC CEE Monitor (Display Name: EMC CEE Monitor) :::info -The latest version of .NET Framework and Dell CEE is recommended to use with the +Use the latest version of .NET Framework and Dell CEE with the asynchronous bulk delivery (VCAPS) feature. ::: @@ -45,8 +45,8 @@ issues related to Dell CEE. ## Configure Dell Registry Key Settings There may be situations when Dell CEE needs to be installed on a different Windows server than the -one where the Activity Monitor activity agent is deployed. In those cases it is necessary to -manually set the Dell CEE registry key to forward events. +one where the Activity Monitor activity agent is deployed. In those cases, manually set the Dell +CEE registry key to forward events. **Step 1 –** Open the Registry Editor (run regedit). @@ -56,12 +56,12 @@ manually set the Dell CEE registry key to forward events. **HKEY_LOCAL_MACHINE\SOFTWARE\EMC\CEE\CEPP\AUDIT\Configuration** -**Step 3 –** Right-click on **Enabled** and select Modify. The Edit DWORD Value window opens. +**Step 3 –** Right-click **Enabled** and select Modify. The Edit DWORD Value window opens. **Step 4 –** In the Value data field, enter the value of 1. Click OK, and the Edit DWORD Value window closes. -**Step 5 –** Right-click on **EndPoint** and select Modify. The Edit String window opens. +**Step 5 –** Right-click **EndPoint** and select Modify. The Edit String window opens. **Step 6 –** In the Value data field, enter the StealthAUDIT value with the IP Address for the Windows proxy server hosting the Activity Monitor activity agent. Use the following format: diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellpowerscale/activity/manualconfiguration.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellpowerscale/activity/manualconfiguration.md index cc3b8a747d..1bf0eb65ea 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellpowerscale/activity/manualconfiguration.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellpowerscale/activity/manualconfiguration.md @@ -22,7 +22,7 @@ cluster, include all relevant zones. Ensure that OneFS collects only events you are interested in. By default, OneFS may monitor things like directory reads, which can take up a large amount of space. Configuring the OneFS events that -need monitoring is not done through the Activity Monitor console. Configure OneFS event monitoring +need monitoring isn't done through the Activity Monitor console. Configure OneFS event monitoring using OneFS CLI with the isi audit modify command for each access zone. Enabling monitoring for only what is needed for the environment will reduce the data load to the agent. @@ -53,19 +53,18 @@ server hosting CEE. Use either of the following format: http://[SERVER Name]:[PORT]/cee :::info -When deploying multiple Dell CEE instances at scale, it is recommended that an -accommodating agent must be configured with each CEE instance. If multiple CEE instances send events +When deploying multiple Dell CEE instances at scale, configure an accommodating agent for each CEE +instance. If multiple CEE instances send events to just one agent, it may create an overflow of data and overload the agent. Distributing the activity stream into pairs will be the most efficient way of monitoring large data sets at scale. ::: **Step 5 –** Also in the Event Forwarding section, set the **Storage Cluster Name** value. It must -be an exact match to the name which is entered in the Activity Monitor for the **Monitored Host** -list. +exactly match the name entered in the Activity Monitor for the **Monitored Host** list. This name is used as a ‘tag’ on all events coming through the CEE. This name must exactly match what -is in the Activity Monitor or it does not recognize the events. +is in the Activity Monitor or it doesn't recognize the events. :::info Use the CIFS DNS name for Dell OneFS. @@ -78,12 +77,12 @@ name entered here must exactly match what is used for Access Analyzer as a targe ::: -If the Storage Cluster Name cannot be modified (for example, another third-party depends on it), you +If the Storage Cluster Name can't be modified (for example, another third-party depends on it), you need to set the Host Aliases parameter in the Activity Monitor Console: -- If the Storage Cluster Name is not empty, set the Host Aliases parameter to its value +- If the Storage Cluster Name isn't empty, set the Host Aliases parameter to its value - If the Storage Cluster Name is empty, set the Host Aliases to a semicolon-separated list of OneFS node names -Next, it is time to configure the monitoring agent on the Windows server to monitor the +Next, configure the monitoring agent on the Windows server to monitor the Isilon/PowerScale device. diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellpowerscale/activity/validate.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellpowerscale/activity/validate.md index 6c80e466bd..dcc95275f4 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellpowerscale/activity/validate.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellpowerscale/activity/validate.md @@ -6,18 +6,17 @@ sidebar_position: 30 # Validate Setup -Once the Activity Monitor agent is configured to monitor the Dell device, the automated -configuration must be validated to ensure events are being monitored. +After you configure the Activity Monitor agent to monitor the Dell device, validate the automated +configuration to ensure it's monitoring events. ## Validate Dell CEE Registry Key Settings -After the Activity Monitor activity agent has been configured to monitor the Dell device, it will -configure the Dell CEE automatically if it is installed on the same server as the agent. This needs -to be set manually in the rare situations where it is necessary for the Dell CEE to be installed on -a different server than the Windows proxy server(s) where the Activity Monitor activity agent is -deployed. +After you configure the Activity Monitor activity agent to monitor the Dell device, the agent +automatically configures Dell CEE if it's installed on the same server. In rare cases, if you +install Dell CEE on a different server than the Windows proxy servers where the activity agent is +deployed, you need to set this manually. -If the monitoring agent is not registering events, validate that the EndPoint is accurately set. +If the monitoring agent isn't registering events, validate that the EndPoint is accurately set. Open the Registry Editor (run regedit). For the synchronous real-time delivery mode (AUDIT), use the following steps. @@ -83,22 +82,22 @@ additional information. ## Validate Dell CEE Services are Running -After the Activity Monitor Activity Agent has been configured to monitor the Dell device, the Dell -CEE services should be running. If the Activity Agent is not registering events and the EndPoint is +After you configure the Activity Monitor Activity Agent to monitor the Dell device, the Dell +CEE services should be running. If the Activity Agent isn't registering events and the EndPoint is set accurately, validate that the Dell CEE services are running. Open the Services (run `services.msc`). ![services](/images/activitymonitor/8.0/config/dellpowerstore/services.webp) -The following services laid down by the Dell CEE installer should have Running as their status: +The following services installed by the Dell CEE installer should show Running as their status: - Dell CAVA - Dell CEE Monitor ## Dell CEE Debug Logs -If an issue arises with communication between the Dell CEE and the Activity Monitor, the debug logs -need to be enabled for troubleshooting purposes. Follow the steps. +If an issue arises with communication between the Dell CEE and the Activity Monitor, enable the +debug logs for troubleshooting. Follow the steps. **Step 6 –** In the Activity Monitor Console, change the **Trace level** value in the lower right corner to Trace. @@ -114,19 +113,19 @@ and Disable monitoring. **HKEY_LOCAL_MACHINE\SOFTWARE\EMC\CEE\Configuration** -**Step 10 –** Right-click on **Debug** and select Modify. The Edit DWORD Value window opens. In the +**Step 10 –** Right-click **Debug** and select Modify. The Edit DWORD Value window opens. In the Value data field, enter the value of 3F. Click OK, and the Edit DWORD Value window closes. :::note -If the Debug DWORD Value does not exist, it needs to be added. +If the Debug DWORD Value doesn't exist, add it. ::: -**Step 11 –** Right-click on **Verbose** and select Modify. The Edit DWORD Value window opens. In +**Step 11 –** Right-click **Verbose** and select Modify. The Edit DWORD Value window opens. In the Value data field, enter the value of 3F. Click OK, and the Edit DWORD Value window closes. :::note -If the Verbose DWORD Value does not exist, it needs to be added. +If the Verbose DWORD Value doesn't exist, add it. ::: @@ -147,7 +146,7 @@ and Enable monitoring. - Use the **Collect Logs** button to collect debug logs from the activity agent :::info -After the logs have been gathered and sent to Netwrix Support, reset these +After you gather the logs and send them to Netwrix Support, reset these configurations. ::: @@ -158,8 +157,7 @@ The debug log is stored in `/opt/CEEPack/emc_cee_svc.log` file. To enable verbos and Verbose parameters under **Configuration** to 255 and restart the CEE. :::note -Debug logs should only be used for troubleshooting purposes. It's recommended to have -Debug Logs disabled by default. +Only use debug logs for troubleshooting. Disable debug logs by default. ::: diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellpowerscale/overview.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellpowerscale/overview.md index 8192a7b757..311d540cdd 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellpowerscale/overview.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellpowerscale/overview.md @@ -38,7 +38,7 @@ topic for additional information. **Additional Sensitive Data Discovery Auditing Permission** -In order to execute scoped Sensitive Data Discovery Auditing scans, the credential must also have +to execute scoped Sensitive Data Discovery Auditing scans, the credential must also have the LOCAL:System provider selected in each access zone in which the shares to be scanned reside. The credential must have an Authentication Provider configured for the Isilon/PowerScale device. For @@ -71,8 +71,8 @@ Share permissions can now be granted to this credential. ## BackupAdmin Role Assignment for OneFS -Follow the steps to assign the credential to the **BackupAdmin** role through OneFS Storage -Administration Console. +To assign the credential to the **BackupAdmin** role through the OneFS Storage Administration +Console, complete the following steps. **Step 1 –** Navigate to the **Access** tab > **Membership & Roles** for the System Access Zone. @@ -111,8 +111,8 @@ export** (per NFS export): - Always read-only clients - Root Clients -The NFS export to be scanned also needs to be configured so root squash is disabled, which is -performed in the same Edit export menu as the above settings. +You must also disable root squash for the NFS export, which you configure in the same Edit export +menu as these settings. **Step 1 –** Navigate to the export's **Root user mapping** settings. @@ -120,14 +120,12 @@ performed in the same Edit export menu as the above settings. **Step 3 –** Set both User and Group to **0** (effectively mapping root client UID/GID to 0). -Both of these steps need to be performed in each NFS export's settings that a user would like to -scan. +Perform both of these steps in each NFS export's settings that you want to scan. ### Troubleshooting NFSv3 Export Access -If Access Analyzer is not discovering the expected NFS export, it is possible that the export policy -is not properly configured to allow the Access Analyzer server or proxy server IP Address to mount -the NFS export. One step in troubleshooting this issue is to confirm a Unix client (or WSL for +If Access Analyzer isn't discovering the expected NFS export, the export policy might not be +configured to allow the Access Analyzer server or proxy server IP address to mount the NFS export. One step in troubleshooting this issue is to confirm a Unix client (or WSL for Windows) in the same IP range as the Access Analyzer server or proxy server can mount the NFS export. @@ -159,7 +157,7 @@ server: - Membership in the local Administrators group - READ and WRITE access to the archive location for Archiving feature only -It is also necessary to enable the Remote Registry Service on the Activity Agent server. +You also need to enable the Remote Registry Service on the Activity Agent server. For integration between the Activity Monitor and Access Analyzer, the credential used by Access Analyzer to read the activity log files must have also have this permission. @@ -182,9 +180,9 @@ instructions. **Activity Monitor Archive Location** -If the activity log files are being archived, configurable within the Netwrix Activity Monitor -Console, then the credential used by Access Analyzer to read the activity log files must also have -READ and WRITE permissions on the archive location. +If you configure the Netwrix Activity Monitor Console to archive activity log files, the credential +used by Access Analyzer to read the activity log files must also have READ and WRITE permissions on +the archive location. ## Activity Auditing Port Requirements @@ -195,9 +193,9 @@ are required for communication between the Agent server and the Netwrix Activity | -------------------------------- | -------- | ----- | ------------------- | | Activity Monitor to Agent Server | TCP | 4498 | Agent Communication | -The Windows firewall rules need to be configured on the Windows server, which require certain -inbound rules be created if the scans are running in applet mode. These scans operate over a default -port range, which cannot be specified via an inbound rule. For more information, see the Microsoft +Configure the Windows firewall rules on the Windows server. If the scans run in applet mode, create +the required inbound rules. These scans operate over a default port range, which you can't specify +in an inbound rule. For more information, see the Microsoft [Connecting to WMI on a Remote Computer](https://msdn.microsoft.com/en-us/library/windows/desktop/aa389290(v=vs.85).aspx) article. @@ -213,7 +211,7 @@ Monitor Activity Agent server and the target Dell Isilon/PowerScale device: Additional Firewall Rules for Integration between Access Analyzer and Activity Monitor -Firewall settings are dependent upon the type of environment being targeted. The following firewall +Firewall settings depend on the type of environment being targeted. The following firewall settings are required for communication between the agent server and the Access Analyzer Console: | Communication Direction | Protocol | Ports | Description | diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellunity/access.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellunity/access.md index 8434e7f0bb..f4e1623f62 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellunity/access.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellunity/access.md @@ -14,7 +14,7 @@ Follow the steps assign group membership through Computer Management. **Step 1 –** Open Computer Management (`compmgmt.msc`). -**Step 2 –** Right-click on the Computer Management (local) node and select Connect to another +**Step 2 –** Right-click the Computer Management (local) node and select Connect to another computer. **Step 3 –** Enter the name of the Dell device in the textbox and click OK. diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellunity/activity/activity.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellunity/activity/activity.md index 5d57a74b20..7c4dd2220d 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellunity/activity/activity.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellunity/activity/activity.md @@ -20,14 +20,14 @@ activity log file is created if there is no activity for the day. **Configuration Checklist** -Complete the following checklist prior to configuring activity monitoring of Dell Unity devices. +Complete the following checklist before configuring activity monitoring of Dell Unity devices. Instructions for each item of the checklist are detailed within the following topics. **Checklist Item 1: Plan Deployment** -- Prior to beginning the deployment, gather the following: +- Before beginning the deployment, gather the following: - - Data Mover or Virtual Data Mover hosting the share(s) to be monitored + - Data Mover or Virtual Data Mover hosting the shares to be monitored - Account with access to the CLI - Download the Dell CEE from: @@ -35,7 +35,7 @@ Instructions for each item of the checklist are detailed within the following to **Checklist Item 2: [Install Dell CEE](/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellunity/activity/installcee.md)** -- Dell CEE should be installed on the Windows proxy server(s) where the Activity Monitor activity +- Dell CEE should be installed on the Windows proxy servers where the Activity Monitor activity agent will be deployed :::info @@ -46,9 +46,9 @@ Instructions for each item of the checklist are detailed within the following to - Important: - - Open MS-RPC ports between the Dell device and the Windows proxy server(s) where the Dell CEE + - Open MS-RPC ports between the Dell device and the Windows proxy servers where the Dell CEE is installed - - Dell CEE 8.4.2 through Dell CEE 8.6.1 are not supported for use with the VCAPS feature + - Dell CEE 8.4.2 through Dell CEE 8.6.1 aren't supported for use with the VCAPS feature - Dell CEE requires .NET Framework 3.5 to be installed on the Windows proxy server **Checklist Item 3: Dell Unity Device Configuration** @@ -69,8 +69,8 @@ Instructions for each item of the checklist are detailed within the following to Checklist Item 5: Configure Dell CEE to Forward Events to the Activity Agent :::note -When Dell CEE is installed on Windows proxy server(s) where the Activity Monitor activity -agent will be deployed, the following steps are not needed. +When Dell CEE is installed on Windows proxy servers where the Activity Monitor activity +agent will be deployed, the following steps aren't needed. ::: diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellunity/activity/installcee.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellunity/activity/installcee.md index 86e17ed859..faa3387313 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellunity/activity/installcee.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellunity/activity/installcee.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Install Dell CEE -Dell CEE should be installed on a Windows or a Linux server. The Dell CEE software is not a Netwrix +Dell CEE should be installed on a Windows or a Linux server. The Dell CEE software isn't a Netwrix product. Dell customers have a support account with Dell to access the download. :::tip @@ -20,10 +20,10 @@ Monitor agent will be deployed (recommended) or on any other Windows or Linux se ::: -Follow the steps to install the Dell CEE. +To install Dell CEE, complete the following steps. **Step 1 –** Obtain the latest CEE install package from Dell and any additional license required for -this component. It is recommended to use the most current version. +this component. Use the most current version. **Step 2 –** Follow the instructions in the Dell [Using the Common Event Enabler on Windows Platforms](https://www.dell.com/support/home/en-us/product-support/product/common-event-enabler/docs) @@ -33,19 +33,19 @@ guide to install and configure the CEE. The installation will add two services t - EMC CEE Monitor (Display Name: EMC CEE Monitor) :::info -The latest version of .NET Framework and Dell CEE is recommended to use with the +Use the latest version of .NET Framework and Dell CEE with the asynchronous bulk delivery (VCAPS) feature. ::: -After Dell CEE installation is complete, it is necessary to complete the +After Dell CEE installation is complete, complete the [Unity Initial Setup with Unisphere](/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellunity/activity/setupunisphere.md). ## Configure Dell Registry Key Settings There may be situations when Dell CEE needs to be installed on a different Windows server than the -one where the Activity Monitor activity agent is deployed. In those cases it is necessary to -manually set the Dell CEE registry key to forward events. +one where the Activity Monitor activity agent is deployed. In those cases, manually set the Dell +CEE registry key to forward events. **Step 1 –** Open the Registry Editor (run regedit). @@ -55,12 +55,12 @@ manually set the Dell CEE registry key to forward events. **HKEY_LOCAL_MACHINE\SOFTWARE\EMC\CEE\CEPP\AUDIT\Configuration** -**Step 3 –** Right-click on **Enabled** and select Modify. The Edit DWORD Value window opens. +**Step 3 –** Right-click **Enabled** and select Modify. The Edit DWORD Value window opens. **Step 4 –** In the Value data field, enter the value of 1. Click OK, and the Edit DWORD Value window closes. -**Step 5 –** Right-click on **EndPoint** and select Modify. The Edit String window opens. +**Step 5 –** Right-click **EndPoint** and select Modify. The Edit String window opens. **Step 6 –** In the Value data field, enter the StealthAUDIT value with the IP Address for the Windows proxy server hosting the Activity Monitor activity agent. Use the following format: diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellunity/activity/setupunisphere.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellunity/activity/setupunisphere.md index 99180a7932..f901ef939c 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellunity/activity/setupunisphere.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellunity/activity/setupunisphere.md @@ -6,12 +6,12 @@ sidebar_position: 20 # Unity Initial Setup with Unisphere -Follow the steps to configure the initial setup for a Unity device with Unisphere. +To configure the initial setup for a Unity device with Unisphere, complete the following steps. **Step 1 –** Edit the NAS Server > Protection and Events > Events Publishing > Select Pool settings: -- Add CEPA server – This is the server where CEE is installed. It is recommended that this is also - the server were the Activity Monitor activity agent is deployed. +- Add CEPA server – This is the server where CEE is installed. Use the same server for the Activity + Monitor activity agent when possible. - Enable the following events for Post Events. Required Unity events needed for CIFS Activity: @@ -29,5 +29,5 @@ Required Unity events needed for NFS Activity: - NFS Events Publishing – Enabled (required for NFS protocol monitoring) - SMB Events publishing – Enabled (required for SMB / CIFS protocol monitoring) -Once Unity setup is complete, it is time to configure and enable monitoring with the Activity +After you complete the Unity setup, configure and enable monitoring with the Activity Monitor. diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellunity/activity/validate.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellunity/activity/validate.md index 8b6e6fbaeb..2c6ee5746d 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellunity/activity/validate.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellunity/activity/validate.md @@ -6,8 +6,8 @@ sidebar_position: 30 # Validate Setup -Once the Activity Monitor agent is configured to monitor the Dell device, the automated -configuration must be validated to ensure events are being monitored. +After you configure the Activity Monitor agent to monitor the Dell device, validate the automated +configuration to ensure it's monitoring events. ## Validate CEE Registry Key Settings @@ -18,13 +18,12 @@ topic for information on manually setting the registry key. ::: -After the Activity Monitor activity agent has been configured to monitor the Dell device, it will -configure the Dell CEE automatically if it is installed on the same server as the agent. This needs -to be set manually in the rare situations where it is necessary for the Dell CEE to be installed on -a different server than the Windows proxy server(s) where the Activity Monitor activity agent is -deployed. +After you configure the Activity Monitor activity agent to monitor the Dell device, the agent +automatically configures Dell CEE if it's installed on the same server. In rare cases, if you +install Dell CEE on a different server than the Windows proxy servers where the activity agent is +deployed, you need to set this manually. -If the monitoring agent is not registering events, validate that the EndPoint is accurately set. +If the monitoring agent isn't registering events, validate that the EndPoint is accurately set. Open the Registry Editor (run regedit). For the synchronous real-time delivery mode (AUDIT), use the following steps. @@ -90,22 +89,22 @@ additional information. ## Validate Dell CEE Services are Running -After the Activity Monitor Activity Agent has been configured to monitor the Dell device, the Dell -CEE services should be running. If the Activity Agent is not registering events and the EndPoint is +After you configure the Activity Monitor Activity Agent to monitor the Dell device, the Dell +CEE services should be running. If the Activity Agent isn't registering events and the EndPoint is set accurately, validate that the Dell CEE services are running. Open the Services (run `services.msc`). ![services](/images/activitymonitor/8.0/config/dellpowerstore/services.webp) -The following services laid down by the Dell CEE installer should have Running as their status: +The following services installed by the Dell CEE installer should show Running as their status: - Dell CAVA - Dell CEE Monitor ## CEE Debug Logs -If an issue arises with communication between the Dell CEE and the Activity Monitor, the debug logs -need to be enabled for troubleshooting purposes. Follow the steps. +If an issue arises with communication between the Dell CEE and the Activity Monitor, enable the +debug logs for troubleshooting. Follow the steps. **Step 6 –** In the Activity Monitor Console, change the **Trace level** value in the lower right corner to Trace. @@ -121,19 +120,19 @@ and Disable monitoring. **HKEY_LOCAL_MACHINE\SOFTWARE\EMC\CEE\Configuration** -**Step 10 –** Right-click on **Debug** and select Modify. The Edit DWORD Value window opens. In the +**Step 10 –** Right-click **Debug** and select Modify. The Edit DWORD Value window opens. In the Value data field, enter the value of 3F. Click OK, and the Edit DWORD Value window closes. :::note -If the Debug DWORD Value does not exist, it needs to be added. +If the Debug DWORD Value doesn't exist, add it. ::: -**Step 11 –** Right-click on **Verbose** and select Modify. The Edit DWORD Value window opens. In +**Step 11 –** Right-click **Verbose** and select Modify. The Edit DWORD Value window opens. In the Value data field, enter the value of 3F. Click OK, and the Edit DWORD Value window closes. :::note -If the Verbose DWORD Value does not exist, it needs to be added. +If the Verbose DWORD Value doesn't exist, add it. ::: @@ -154,7 +153,7 @@ and Enable monitoring. - Use the **Collect Logs** button to collect debug logs from the activity agent :::info -After the logs have been gathered and sent to Netwrix Support, reset these +After you gather the logs and send them to Netwrix Support, reset these configurations. ::: diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellunity/overview.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellunity/overview.md index 7ee308b3e3..5453442e4b 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellunity/overview.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/dellunity/overview.md @@ -37,12 +37,12 @@ topic for additional information. **Troubleshooting Dell Unity Denied Access Errors** -If there are folders to which the credential is denied access, it is likely that the Backup -Operators group does not have the “Back up files and directories” right. In that case, it is -necessary to assign additional the “Back up files and directories” right to those groups or to -create a new local group, using Computer Management from a Windows server. Then assign rights to it -using the CelerraManagementTool.msc plugin, which is available to Dell customers. For further -information, see the Celerra guide Using Windows Administrative Tools on VNX found on the Celerra +If there are folders to which the credential is denied access, the Backup +Operators group likely doesn't have the “Back up files and directories” right. In that case, +assign the “Back up files and directories” right to those groups, or +create a new local group using Computer Management on a Windows server. Then assign rights to it +using the CelerraManagementTool.msc plugin, which is available to Dell customers. For more +information, see the Celerra guide Using Windows Administrative Tools on VNX on the Celerra website. ## Access & Sensitive Data Auditing Port Requirements @@ -64,7 +64,7 @@ server: - Membership in the local Administrators group - READ and WRITE access to the archive location for Archiving feature only -It is also necessary to enable the Remote Registry Service on the Activity Agent server. +You also need to enable the Remote Registry Service on the Activity Agent server. For integration between the Activity Monitor and Access Analyzer, the credential used by Access Analyzer to read the activity log files must have also have this permission. @@ -86,9 +86,9 @@ See the [Dell Unity Activity Auditing Configuration](/docs/accessanalyzer/12.0/r **Activity Monitor Archive Location** -If the activity log files are being archived, configurable within the Netwrix Activity Monitor -Console, then the credential used by Access Analyzer to read the activity log files must also have -READ and WRITE permissions on the archive location. +If you configure the Netwrix Activity Monitor Console to archive activity log files, the credential +used by Access Analyzer to read the activity log files must also have READ and WRITE permissions on +the archive location. ## Activity Auditing Port Requirements @@ -99,9 +99,9 @@ are required for communication between the Agent server and the Netwrix Activity | -------------------------------- | -------- | ----- | ------------------- | | Activity Monitor to Agent Server | TCP | 4498 | Agent Communication | -The Windows firewall rules need to be configured on the Windows server, which require certain -inbound rules be created if the scans are running in applet mode. These scans operate over a default -port range, which cannot be specified via an inbound rule. For more information, see the Microsoft +Configure the Windows firewall rules on the Windows server. If the scans run in applet mode, create +the required inbound rules. These scans operate over a default port range, which you can't specify +in an inbound rule. For more information, see the Microsoft [Connecting to WMI on a Remote Computer](https://msdn.microsoft.com/en-us/library/windows/desktop/aa389290(v=vs.85).aspx) article. @@ -117,7 +117,7 @@ Monitor Activity Agent server and the target Dell device: Additional Firewall Rules for Integration between Access Analyzer and Activity Monitor -Firewall settings are dependent upon the type of environment being targeted. The following firewall +Firewall settings depend on the type of environment being targeted. The following firewall settings are required for communication between the agent server and the Access Analyzer Console: | Communication Direction | Protocol | Ports | Description | diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/filesystems.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/filesystems.md index 628802ece1..f9705160a7 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/filesystems.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/filesystems.md @@ -76,8 +76,8 @@ See the topic for target environment requirements. ## Azure Files Support -Azure Files is a fully managed, cloud-based file sharing service from Microsoft that allows users to -access file shares from anywhere as a virtual network drive. Access Analyzer supports Access +Azure Files is a fully managed, cloud-based file sharing service from Microsoft. With Azure Files, +users can access file shares from anywhere as a virtual network drive. Access Analyzer supports Access Auditing (FSAA) and Sensitive Data Discovery Auditing scans of Azure Files. See the [Azure Files Target Requirements](/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/azurefiles.md) topic for additional information. @@ -114,7 +114,7 @@ environment requirements. See the [Hitachi Target Requirements](/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/hitachi/overview.md) topic for target environment requirements. -**Nasuni Nasuni Edge Appliances** +**Nasuni Edge Appliances** - 8.0+ diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/hitachi/activity/activity.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/hitachi/activity/activity.md index f3d6c50347..396cdbbd28 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/hitachi/activity/activity.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/hitachi/activity/activity.md @@ -11,7 +11,7 @@ multiple file systems. Auditing is enabled and configured per file system. This to enable auditing on an HNAS and to configure the Activity Monitor to monitor activity coming from the Hitachi device auditing. -The Activity Monitor does not use the EVS or file system name to connect to HNAS. Therefore, all +The Activity Monitor doesn't use the EVS or file system name to connect to HNAS. Therefore, all that is required of the user for HNAS activity collection is the following: - Logs path (UNC) @@ -39,11 +39,11 @@ clients using other protocols would be costly in terms of system performance, be operation would have to be audited as an open operation. **Therefore, when file system auditing is enabled, by default, only clients connecting through the CIFS protocol are allowed access to the file system.** Access by clients using other protocols, like NFS, can, however, be allowed. When -such access is allowed, access to file system objects through these protocols is not audited.” +such access is allowed, access to file system objects through these protocols isn't audited.” :::note File system auditing can be configured to deny access to clients connecting with protocols -that cannot be audited (NFS). Please see the Hitachi +that can't be audited (NFS). see the Hitachi [Server and Cluster Administration Guide](https://support.hds.com/download/epcra/hnas0106.pdf) for additional information. ::: @@ -51,7 +51,7 @@ additional information. **Configuration Checklist** -Complete the following checklist prior to configuring activity monitoring of Hitachi devices. +Complete the following checklist before configuring activity monitoring of Hitachi devices. Instructions for each item of the checklist are detailed within the following topics. **Checklist Item 1: [Configure Audit Logs on HNAS](/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/hitachi/activity/configurelogs.md)** diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/hitachi/activity/configureaccesstologs.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/hitachi/activity/configureaccesstologs.md index deade0c148..184fcdea91 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/hitachi/activity/configureaccesstologs.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/hitachi/activity/configureaccesstologs.md @@ -6,8 +6,8 @@ sidebar_position: 20 # Configure Access to HNAS Audit Logs on Activity Agent Server -Follow the steps to configure access to the HNAS audit logs on the Windows server hosting the -Activity Monitor activity agent. +To configure access to the HNAS audit logs on the Windows server hosting the Activity Monitor +activity agent, complete the following steps. **Step 1 –** On the Windows computer, go to Run and type `compmgmt.msc`. @@ -22,9 +22,9 @@ Folders > Shares. **Step 5 –** Select the Security tab and click Advanced. **Step 6 –** In the Advanced Security Settings dialog box, select the Audit tab. Click Add or Edit -to select the users and groups to be audited and add the desired user or group. +to select the users and groups to be audited and add the user or group you want to audit. **Step 7 –** Select All for Type, and Full Control for Basic permissions. -Once access has been configured on both the Hitachi device and the Activity Agent server, it is time -to configure and enable monitoring with the Activity Monitor Console. +After you configure access on both the Hitachi device and the Activity Agent server, configure and +enable monitoring with the Activity Monitor Console. diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/hitachi/activity/configurelogs.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/hitachi/activity/configurelogs.md index 7c28b1fff3..ca24ebc10f 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/hitachi/activity/configurelogs.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/hitachi/activity/configurelogs.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Configure Audit Logs on HNAS -Follow the steps to configure access to the HNAS audit logs on the Hitachi device. +To configure access to the HNAS audit logs on the Hitachi device, complete the following steps. **Step 1 –** Open a browser and enter the IP Address for HNAS in the address bar to launch the Hitachi Storage Navigator (SN). Enter the username and password. @@ -33,7 +33,7 @@ auditing). In the Audit Log section, set the maximum log file size to a value of is recommended to set it to 16 MB. In the Log roll over policy section, select New. The product does not support the Wrap policy. Click OK to close. -Once access has been configured on the Hitachi device, it is necessary to configure access to the -HNAS audit logs on the Windows server. See the +After access is configured on the Hitachi device, configure access to the HNAS audit logs on the +Windows server. See the [Configure Access to HNAS Audit Logs on Activity Agent Server](/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/hitachi/activity/configureaccesstologs.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/hitachi/overview.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/hitachi/overview.md index 11406b2b9f..6cca5091d6 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/hitachi/overview.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/hitachi/overview.md @@ -49,7 +49,7 @@ server: - Membership in the local Administrators group - READ and WRITE access to the archive location for Archiving feature only -It is also necessary to enable the Remote Registry Service on the Activity Agent server. +You also need to enable the Remote Registry Service on the Activity Agent server. For integration between the Activity Monitor and Access Analyzer, the credential used by Access Analyzer to read the activity log files must have also have this permission. @@ -71,9 +71,9 @@ See the [Hitachi Activity Auditing Configuration](/docs/accessanalyzer/12.0/requ **Activity Monitor Archive Location** -If the activity log files are being archived, configurable within the Netwrix Activity Monitor -Console, then the credential used by Access Analyzer to read the activity log files must also have -READ and WRITE permissions on the archive location. +If you configure the Netwrix Activity Monitor Console to archive activity log files, the credential +used by Access Analyzer to read the activity log files must also have READ and WRITE permissions on +the archive location. ## Activity Auditing Port Requirements @@ -84,15 +84,15 @@ are required for communication between the Agent server and the Netwrix Activity | -------------------------------- | -------- | ----- | ------------------- | | Activity Monitor to Agent Server | TCP | 4498 | Agent Communication | -The Windows firewall rules need to be configured on the Windows server, which require certain -inbound rules be created if the scans are running in applet mode. These scans operate over a default -port range, which cannot be specified via an inbound rule. For more information, see the Microsoft +Configure the Windows firewall rules on the Windows server. If the scans run in applet mode, create +the required inbound rules. These scans operate over a default port range, which you can't specify +in an inbound rule. For more information, see the Microsoft [Connecting to WMI on a Remote Computer](https://msdn.microsoft.com/en-us/library/windows/desktop/aa389290(v=vs.85).aspx) article. Additional Firewall Rules for Integration between Access Analyzer and Activity Monitor -Firewall settings are dependent upon the type of environment being targeted. The following firewall +Firewall settings depend on the type of environment being targeted. The following firewall settings are required for communication between the agent server and the Access Analyzer Console: | Communication Direction | Protocol | Ports | Description | diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/nasuni/access.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/nasuni/access.md index e64b33da3b..baca1eb4ba 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/nasuni/access.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/nasuni/access.md @@ -6,12 +6,12 @@ sidebar_position: 10 # Nasuni Edge Appliance Access & Sensitive Data Auditing Configuration -It is necessary to generate an API Key Name and Passcode for each on-premise Nasuni Edge Appliance +Generate an API Key Name and Passcode for each on-premise Nasuni Edge Appliance and cloud filer. ## Nasuni Filer Management Interface -Follow the steps to generate a Nasuni API Access Key in the Nasuni Filer Management Interface. +To generate a Nasuni API Access Key in the Nasuni Filer Management Interface: **Step 1 –** Within the **Configuration** menu, under **USERS & SECURITY**, select API Access Keys. The API Access Keys page opens. @@ -39,14 +39,14 @@ documentation for additional information. ## Nasuni Management Console -Follow the steps to generate a Nasuni API Access Key in the Nasuni Management Console. +To generate a Nasuni API Access Key in the Nasuni Management Console: **Step 1 –** Click Filers and select API Keys from the menu on the left. The Filer API Access Key Settings page opens. **Step 2 –** Click New API Key button. The Add API Access Key window opens. -**Step 3 –** From the Filer drop-down menu, select the desired Nasuni Edge Appliance. Then enter a +**Step 3 –** From the Filer dropdown menu, select the Nasuni Edge Appliance you want. Then enter a Name for the key; for example, the name of the application. **Step 4 –** Click Add API Key. @@ -68,13 +68,12 @@ documentation for additional information. ## Nasuni Best Practices for Access Auditing -Nasuni is a hybrid NAS where actively-used data is stored on a Nasuni Edge appliance while the -authoritative copy of all files and meta data is stored in private or public cloud object storage -platforms by the UniFS® global file system, and there are egress fees associated with transferring -data between the two. In order to minimize these egress fees and optimize scan performance, it is -recommended to deploy a dedicated Nasuni Edge Appliance with all shares to be scanned by Access -Analyzer mounted, and the Access Analyzer console server, in the same region where the authoritative -copy resides. +Nasuni is a hybrid NAS: actively used data resides on a Nasuni Edge Appliance, while the UniFS® +global file system stores the authoritative copy of all files and metadata in private or public +cloud object storage platforms. Because transferring data between the two incurs egress fees, +deploy a dedicated Nasuni Edge Appliance with all shares you want Access Analyzer to scan mounted, +and place the Access Analyzer console server in the same region as the authoritative copy. This +minimizes egress fees and optimizes scan performance. See the [External Auditing and Nasuni Best Practices](https://nasuni.my.salesforce.com/sfc/p/#external-auditing-and-nasuni-best-practices) diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/nasuni/activity.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/nasuni/activity.md index b4a1c231fb..e1017802ba 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/nasuni/activity.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/nasuni/activity.md @@ -6,14 +6,14 @@ sidebar_position: 20 # Nasuni Edge Appliance Activity Auditing Configuration -Generation of an API Access Key is required for Nasuni activity monitoring. The Nasuni Edge -Appliance generates its own audit trail. An API Access Key is used by the Activity Monitor to form a +You must generate an API Access Key for Nasuni activity monitoring. The Nasuni Edge +Appliance generates its own audit trail. The Activity Monitor uses an API Access Key to form a network connection to the appliance. Nasuni will then stream event data to the activity agent. See [Nasuni Support Documentation](https://www.nasuni.com/support/) for additional information. **Configuration Checklist** -Complete the following checklist prior to configuring activity monitoring of Nasuni Edge Appliances. +Complete the following checklist before configuring activity monitoring of Nasuni Edge Appliances. Instructions for each item of the checklist are detailed within the following topics. **Checklist Item 1: Generate Nasuni API Access Key** @@ -30,7 +30,7 @@ Instructions for each item of the checklist are detailed within the following to ## Nasuni Filer Management Interface -Follow the steps to generate a Nasuni API Access Key in the Nasuni Filer Management Interface. +To generate a Nasuni API Access Key in the Nasuni Filer Management Interface: **Step 1 –** Within the **Configuration** menu, under **USERS & SECURITY**, select API Access Keys. The API Access Keys page opens. @@ -43,8 +43,8 @@ The API Access Keys page opens. **Step 5 –** In the Successfully Generated API Key window, copy the Key Passcode. -Both the Key Name and the Key Passcode are required by the Activity Monitor in order to connect to -the Nasuni Edge Appliance. Once the API Key has been generated, it is time to configure and enable +The Activity Monitor requires both the Key Name and the Key Passcode to connect to +the Nasuni Edge Appliance. After you generate the API key, configure and enable monitoring with the Activity Monitor console. :::note @@ -55,22 +55,22 @@ the exact same case as generated. ## Nasuni Management Console -Follow the steps to generate a Nasuni API Access Key in the Nasuni Management Console. +To generate a Nasuni API Access Key in the Nasuni Management Console: **Step 1 –** Click Filers and select API Keys from the menu on the left. The Filer API Access Key Settings page opens. **Step 2 –** Click New API Key button. The Add API Access Key window opens. -**Step 3 –** From the Filer drop-down menu, select the desired Nasuni Edge Appliance. Then enter a +**Step 3 –** From the Filer dropdown menu, select the Nasuni Edge Appliance you want. Then enter a Name for the key; for example, the name of the application. **Step 4 –** Click Add API Key. **Step 5 –** A message appears which includes the Key Passcode; copy the Key Passcode. -Both the Key Name and the Key Passcode are required by the Activity Monitor in order to connect to -the Nasuni Edge Appliance. Once the API Key has been generated, it is time to configure and enable +The Activity Monitor requires both the Key Name and the Key Passcode to connect to +the Nasuni Edge Appliance. After you generate the API key, configure and enable monitoring with the Activity Monitor console. :::note diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/nasuni/overview.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/nasuni/overview.md index 02e743064e..3826f40861 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/nasuni/overview.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/nasuni/overview.md @@ -59,7 +59,7 @@ Analyzer to read the activity log files must have also have this permission. **Nasuni Edge Appliance Requirements** -Additionally, it is necessary to generate an API Access Key for Nasuni activity monitoring. See the +Additionally, generate an API Access Key for Nasuni activity monitoring. See the [Nasuni Edge Appliance Activity Auditing Configuration](/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/nasuni/activity.md) topic for instructions. **Activity Monitor Archive Location** @@ -79,7 +79,7 @@ are required for communication between the Agent server and the Netwrix Activity The Windows firewall rules need to be configured on the Windows server, which require certain inbound rules be created if the scans are running in applet mode. These scans operate over a default -port range, which cannot be specified via an inbound rule. For more information, see the Microsoft +port range, which can't be specified via an inbound rule. For more information, see the Microsoft [Connecting to WMI on a Remote Computer](https://msdn.microsoft.com/en-us/library/windows/desktop/aa389290(v=vs.85).aspx) article. diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/access/access.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/access/access.md index 94bcf8786b..109b67f9f0 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/access/access.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/access/access.md @@ -30,7 +30,7 @@ api-volume-list-info-iter-* ## Bypass NTFS Security for 7-Mode -In order to bypass NTFS, the credential needs to at least have the following permissions on the +to bypass NTFS, the credential needs to at least have the following permissions on the NetApp device: - Group membership in both of the following groups: diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/access/provisionaccess.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/access/provisionaccess.md index 90c2f0de68..189231b365 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/access/provisionaccess.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/access/provisionaccess.md @@ -8,13 +8,13 @@ sidebar_position: 10 This section describes the steps needed to create a user account with the privileges required to execute Access Auditing (FSAA) and/or Sensitive Data Discovery Auditing scans from Access Analyzer. -It is necessary to: +Complete the following steps: - Create Role - Create a Group & Assign Role - Add User to Group -Relevant NetApp Documentation: To learn more about node access controls, please visit the NetApp +Relevant NetApp Documentation: To learn more about node access controls, visit the NetApp website and read the [na_useradmin – Administers node access controls](https://library.netapp.com/ecmdocs/ECMP1511537/html/man1/na_useradmin.1.html) article. @@ -47,7 +47,7 @@ After the role is created, Create a Group & Assign Role. ## Create a Group & Assign Role -Once the role has been created, it must be attached to a group. The following command needs to be +After the role is created, it must be attached to a group. The following command needs to be run to create a group and assign the role to it. ``` diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/activity/activity.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/activity/activity.md index 2e5a162f87..7c0721f9b8 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/activity/activity.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/activity/activity.md @@ -6,30 +6,30 @@ sidebar_position: 20 # NetApp Data ONTAP 7-Mode Activity Auditing Configuration -The Activity Monitor agent employed to monitor NetApp leverages 128-bit encrypted Remote Procedure +The Activity Monitor agent employed to monitor NetApp uses 128-bit encrypted Remote Procedure Calls (RPC), NetApp ONTAP-API, and NetApp FPolicy to monitor file system events. This includes both -NetApp 7-Mode and Cluster-Mode configurations. To learn more about FPolicy please visit the NetApp +NetApp 7-Mode and Cluster-Mode configurations. To learn more about FPolicy visit the NetApp website and read the [What FPolicy is](https://library.netapp.com/ecmdocs/ECMP1401220/html/GUID-54FE1A84-6CF0-447E-9AAE-F43B61CA2138.html) article. -If the activity agent is stopped, a notification will be sent to the NetApp device to disconnect and -disable the associated FPolicy policy, but it will not be removed. +If the activity agent stops, it sends a notification to the NetApp device to disconnect and +disable the associated FPolicy policy, but it doesn't remove the policy. -If the network connection is lost between the activity agent and the NetApp device, the NetApp -device is configured with a default timeout to wait for a response. If a response is not received -from the Activity Agent within the timeout, then the NetApp device will disconnect and disable the -FPolicy policy. The Activity Agent will check every minute by default to see if the FPolicy policy -has been disabled and will enable it (if the auto-enable functionality is enabled for the agent). -The default setting to check every minute is configurable. +If the network connection between the activity agent and the NetApp device drops, the NetApp +device waits for a response for a default timeout period. If the NetApp device doesn't receive a +response from the Activity Agent within the timeout, it disconnects and disables the +FPolicy policy. By default, the Activity Agent checks every minute to see if the FPolicy policy +is disabled and re-enables it (if the auto-enable functionality is enabled for the agent). +The default check interval of one minute is configurable. -The NetApp FPolicy uses a “push” mechanism such that notification will only be sent to the activity -agent when a transaction occurs. Daily activity log files are created only if activity is performed. -No activity log file will be created if there is no activity for the day. +The NetApp FPolicy uses a “push” mechanism, so it sends a notification to the activity +agent only when a transaction occurs. The Activity Agent creates daily activity log files +only when activity occurs. It doesn't create an activity log file for a day with no activity. **Configuration Checklist** -Complete the following checklist prior to configuring activity monitoring of NetApp Data ONTAP +Complete the following checklist before configuring activity monitoring of NetApp Data ONTAP 7-Mode devices. Instructions for each item of the checklist are detailed within the following topics. @@ -37,7 +37,7 @@ topics. - Gather the following information: - Names of the vFiler™(s) to be monitored - - DNS name of the CIFS shares(s) to be monitored + - DNS name of the CIFS sharess to be monitored **Checklist Item 2: [Provision FPolicy Account](/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/activity/provisionactivity.md)** diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/activity/configurefpolicy.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/activity/configurefpolicy.md index eda4fcc7d7..253a01c2fe 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/activity/configurefpolicy.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/activity/configurefpolicy.md @@ -15,9 +15,9 @@ A tailored FPolicy ::: -- If using vFilers the FPolicy must be created on the vFiler, and the Activity Monitor must target - the vFiler. This is because FPolicy operates on the affected vFiler. Therefore, when executing - these commands on a vFiler, the commands must be run from a vFiler context (e.g. via the vFiler +- If using vFilers, create the FPolicy on the vFiler, and target the vFiler with the Activity + Monitor. This is because FPolicy operates on the affected vFiler. Therefore, when you run + these commands on a vFiler, run them from a vFiler context (e.g., via the vFiler run command). - Allow the Activity Monitor to create an FPolicy automatically. See the [Automatic Configuration of FPolicy](#automatic-configuration-of-fpolicy) topic for additional @@ -30,7 +30,7 @@ A tailored FPolicy ## Manually Configure FPolicy (Recommended Option) This section describes how to manually configure FPolicy. Manual configuration of the FPolicy is -recommended so that the policy can be scoped. It is necessary to create six FPolicy components and +recommended so that the policy can be scoped. Create six FPolicy components and then enable the FPolicy. See the sections corresponding to each part of this list: - [Part 1: Create FPolicy](#part-1-create-fpolicy) @@ -41,12 +41,12 @@ then enable the FPolicy. See the sections corresponding to each part of this lis - [Part 6: Scope FPolicy for Specific Volumes](#part-6-scope-fpolicy-for-specific-volumes) - [Part 7: Enable FPolicy](#part-7-enable-fpolicy) -If using vFilers the FPolicy must be created on the vFiler, and the Activity Monitor must target the -vFiler. This is because FPolicy operates on the affected vFiler. Therefore, when executing these -commands on a vFiler, the commands must be run from a vFiler context (e.g. via the vFiler run +If using vFilers, create the FPolicy on the vFiler, and target the vFiler with the Activity Monitor. +This is because FPolicy operates on the affected vFiler. Therefore, when you run these +commands on a vFiler, run them from a vFiler context (e.g., via the vFiler run command). -Relevant NetApp Documentation: To learn more about configuring file policies, please visit the +Relevant NetApp Documentation: To learn more about configuring file policies, visit the NetApp website and read [na_fpolicy – configure file policies](https://library.netapp.com/ecmdocs/ECMP1196890/html/man1/na_fpolicy.1.html) article. @@ -68,9 +68,9 @@ fpolicy create StealthAUDIT screen ### Part 2: Set FPolicy Required to Off -If the `FPolicy Required` value is set to on, user requests are denied if an FPolicy server is not -available to implement the policy. If it is set to off, user requests are allowed when it is not -possible to apply the policy to the file because no FPolicy server is available. +If you set the `FPolicy Required` value to on, the NetApp device denies user requests when no +FPolicy server is available to implement the policy. If you set it to off, the NetApp device +allows user requests even when no FPolicy server is available to apply the policy to the file. IMPORTANT: @@ -175,6 +175,6 @@ fpolicy enable StealthAUDIT ## Automatic Configuration of FPolicy The Activity Monitor can automatically configure FPolicy on the targeted NetApp Data ONTAP 7-Mode -device. The FPolicy created monitors all file system activity. This is done when the NetApp device -is assigned to the agent for monitoring. This option is enabled on the NetApp FPolicy Configuration +device. The FPolicy created monitors all file system activity. This happens when you assign the +NetApp device to the agent for monitoring. This option is enabled on the NetApp FPolicy Configuration page of the Add New Host window. diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/activity/customizefpolicy.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/activity/customizefpolicy.md index 77843dad69..4d90aecbe9 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/activity/customizefpolicy.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/activity/customizefpolicy.md @@ -7,7 +7,7 @@ sidebar_position: 40 # Customize FPolicy Policy Name There may be situations when FPolicy needs to be named something other than StealthAUDIT. In those -cases it is necessary to manually add a parameter to the Activity Monitor agent’s `sbtfilemon.ini` +cases, manually add a parameter to the Activity Monitor agent’s `sbtfilemon.ini` file. After the monitoring agent has been deployed, follow the steps. **Step 1 –** Open to the `sbtfilemon.ini` file on the agent server in a text editor: diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/activity/provisionactivity.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/activity/provisionactivity.md index 690a741a7c..e32a2de224 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/activity/provisionactivity.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/activity/provisionactivity.md @@ -16,7 +16,7 @@ Provisioning this account is a three part process: - Part 2: Create a Group & Assign Role - Part 3: Add User to Group -Relevant NetApp Documentation: To learn more about node access controls, please visit the NetApp +Relevant NetApp Documentation: To learn more about node access controls, visit the NetApp website and read the [na_useradmin – Administers node access controls](https://library.netapp.com/ecmdocs/ECMP1511537/html/man1/na_useradmin.1.html) article. @@ -74,7 +74,7 @@ After the role is created, complete Part 2: Create a Group & Assign Role. ## Part 2: Create a Group & Assign Role -Once the role has been created, it must be attached to a group. The following command needs to be +After the role is created, it must be attached to a group. The following command needs to be run to create a group and assign the role to it. ``` diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/overview.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/overview.md index 406c269a72..96e82deddf 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/overview.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netapp7mode/overview.md @@ -115,7 +115,7 @@ are required for communication between the Agent server and the Netwrix Activity The Windows firewall rules need to be configured on the Windows server, which require certain inbound rules be created if the scans are running in applet mode. These scans operate over a default -port range, which cannot be specified via an inbound rule. For more information, see the Microsoft +port range, which can't be specified via an inbound rule. For more information, see the Microsoft [Connecting to WMI on a Remote Computer](https://msdn.microsoft.com/en-us/library/windows/desktop/aa389290(v=vs.85).aspx) article. @@ -139,7 +139,7 @@ Agent server and the target NetApp Data ONTAP 7-Mode device: Activity Monitor. :::note -If either HTTP or HTTPS are not enabled, the FPolicy on the NetApp Data ONTAP 7-Mode +If either HTTP or HTTPS aren't enabled, the FPolicy on the NetApp Data ONTAP 7-Mode device must be configured manually. Also, the External Engine will not reconnect automatically in the case of a server reboot or service restart. ::: diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/access/access.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/access/access.md index 4389bf9613..8ecd2969d4 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/access/access.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/access/access.md @@ -104,8 +104,8 @@ The following permissions are required: cifs users-and-groups local-group add-members ‑group-name "BUILTIN\Backup Operators" ‑member-names [DOMAIN_USER] ‑vserver [SVM_NAME] ``` -If an ACE does not already exist for a specific user/group on an SVM's c$ share, then it needs to be -added with the desired rights (No_access, Read, Change, or Full_Control). To check the current ACE +If an ACE doesn't already exist for a specific user/group on an SVM's c$ share, then it needs to be +added with the rights you want (No_access, Read, Change, or Full_Control). To check the current ACE for a user or group on each SVM's c$ share, the following ONTAP CLI command should be used at the cluster management level. @@ -117,7 +117,7 @@ The output will list each SVM's ACL for its c$ share. For example: ![ONTAP CLI Command Output Example](/images/accessanalyzer/12.0/config/netappcmode/accesscifsmethod2.webp) -If the desired ACE does not exist on an SVM's c$ share, then one can be created with the following +If the ACE you want doesn't exist on an SVM's c$ share, then one can be created with the following command: ``` @@ -127,7 +127,7 @@ vserver cifs share access-control create -share c$ -user-or-group [USER_OR_GROUP If an existing ACE needs to be modified, the following command should be used: :::warning -The following command will overwrite an existing ACE. For example, it is possible to +The following command will overwrite an existing ACE. For example, you can downgrade a user with Full_Control to Read, or vice versa. ::: @@ -142,14 +142,14 @@ instead give the SVM's Backup Operators group read-only access to each share to ::: -In order to utilize Access Analyzer’s LAT Preservation (Last Access Time) feature during sensitive +to use Access Analyzer’s LAT Preservation (Last Access Time) feature during sensitive data scans and metadata tag collection, applying ONTAP’s SeRestorePrivilege to the service account is also required. As an alternative to membership in BUILTIN\Backup Operators, SeBackupPrivilege can be directly applied to a user via the NetApp command line. -The following commands can be used to grant these permissions to the service account to be used for +Use the following commands to grant these permissions to the service account used for scanning by Access Analyzer. Use the following commands to add SeBackupPrivilege to the Service Account (or a BUILTIN Group): @@ -196,13 +196,13 @@ cifs share access-control show ‑vserver [SVM_NAME] ‑share c$ ## NFSv3 Credential Configuration -The following is a list of example commands that can be used to configure a NetApp export policy to +Use the following example commands to configure a NetApp export policy to scan a volume via NFSv3 using the Access Analyzer File System Solution. :::warning The export policy for a volume's parent (ex. the SVM's root volume), or the export policy for a qtree's parent, must have access rights that are equal or wider in scope to the export -policy for the target volume/qtree. If Access Analyzer cannot access all segments of a target +policy for the target volume/qtree. If Access Analyzer can't access all segments of a target volume/qtree's junction path, then NFS access will be denied. ::: @@ -259,7 +259,7 @@ volume modify ‑vserver testserver ‑volume testVolume ‑policy testNFS ### Troubleshooting NFSv3 Export Access If Access Analyzeris not discovering the expected NFS export, it is possible that the export policy -is not properly configured to allow the Access Analyzer server or proxy server IP Address to mount +isn't properly configured to allow the Access Analyzer server or proxy server IP Address to mount the NFS export. One step in troubleshooting this issue is to confirm a Unix client (or WSL for Windows) in the same IP range as the Access Analyzer server or proxy server can mount the NFS export. diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/access/configureemptyfpolicy.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/access/configureemptyfpolicy.md index 7902707762..a73f0efe8b 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/access/configureemptyfpolicy.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/access/configureemptyfpolicy.md @@ -95,14 +95,14 @@ Example: security login role show enterpriseauditor ``` -Relevant NetApp Documentation: To learn more about creating security login roles, please visit the +Relevant NetApp Documentation: To learn more about creating security login roles, visit the NetApp website and read the [security login role create](https://library.netapp.com/ecmdocs/ECMP1196817/html/security/login/role/create.html) article. ## Create Security Login for FSAA Scans -Once the access control role has been created, apply it to a domain account. +After the access control role is created, apply it to a domain account. **:::warning** @@ -154,7 +154,7 @@ Verify that the output is displayed as follows: ![validatesecuritylogincreation](/images/activitymonitor/8.0/config/netappcmode/validatesecuritylogincreation.webp) -Relevant NetApp Documentation: To learn more about creating security logins, please visit the NetApp +Relevant NetApp Documentation: To learn more about creating security logins, visit the NetApp website and read the [security login create](https://library.netapp.com/ecmdocs/ECMP12452955/html/security/login/create.html) article. @@ -165,7 +165,7 @@ The External Engine defines how FPolicy makes and manages connections to externa IMPORTANT: -- The `-primary-servers` must be the server from which the StealthAUDIT scans will be executed: +- The `-primary-servers` must be the server that runs the StealthAUDIT scans: - StealthAUDIT Console server for local mode - proxy server if running in any of the proxy mode options @@ -211,7 +211,7 @@ Verify that the output is displayed as follows: ![validateexternalenginecreation](/images/accessanalyzer/12.0/config/netappcmode/validateexternalenginecreation.webp) -Relevant NetApp Documentation: To learn more about creating an external engine, please visit the +Relevant NetApp Documentation: To learn more about creating an external engine, visit the NetApp website and read the [vserver fpolicy policy external-engine create](https://library.netapp.com/ecmdocs/ECMP1366832/html/vserver/fpolicy/policy/external-engine/create.html) article. @@ -259,7 +259,7 @@ Verify that the output is displayed as follows: ![validatefpolciyeventcreation](/images/accessanalyzer/12.0/config/netappcmode/validatefpolciyeventcreation.webp) -Relevant NetApp Documentation: To learn more about creating an event, please visit the NetApp +Relevant NetApp Documentation: To learn more about creating an event, visit the NetApp website and read the [vserver fpolicy policy event create](https://library.netapp.com/ecmdocs/ECMP1196817/html/vserver/fpolicy/policy/event/create.html) article. @@ -313,7 +313,7 @@ fpolicy policy show ‑instance ![validatefpolicypolicycreation](/images/accessanalyzer/12.0/config/netappcmode/validatefpolicypolicycreation.webp) -Relevant NetApp Documentation: To learn more about creating a policy, please visit the NetApp +Relevant NetApp Documentation: To learn more about creating a policy, visit the NetApp website and read the [vserver fpolicy policy create](https://library.netapp.com/ecmdocs/ECMP1366832/html/vserver/fpolicy/policy/create.html) article. @@ -325,9 +325,9 @@ The FPolicy scope creates the filters necessary to perform scans on specific sha IMPORTANT: - The SVM used must be the SVM hosting the CIFS shares. -- It is not necessary to specify both volumes and shares. One or the other is sufficient. +- It isn't necessary to specify both volumes and shares. One or the other is sufficient. -Use the following command to create the FPolicy scope by volume(s): +Use the following command to create the FPolicy scope by volumes: ``` vserver fpolicy policy scope create ‑vserver [SVM_NAME] ‑policy-name StealthAUDIT ‑volumes-to-include @@ -339,7 +339,7 @@ Example: vserver fpolicy policy scope create ‑vserver testserver ‑policy-name StealthAUDIT ‑volumes-to-include ``` -Use the following command to create the FPolicy scope by share(s): +Use the following command to create the FPolicy scope by shares: ``` vserver fpolicy policy scope create ‑vserver [SVM_NAME] ‑policy-name StealthAUDIT ‑shares-to-include @@ -363,14 +363,14 @@ fpolicy policy scope show ‑instance ![validatefpolicyscopecreation](/images/accessanalyzer/12.0/config/netappcmode/validatefpolicyscopecreation.webp) -Relevant NetApp Documentation: To learn more about creating scope, please visit the NetApp website +Relevant NetApp Documentation: To learn more about creating scope, visit the NetApp website and read the [vserver fpolicy policy scope create](https://library.netapp.com/ecmdocs/ECMP1196817/html/vserver/fpolicy/policy/scope/create.html) article. ## Enable the Empty FPolicy -Once the empty FPolicy has been created, it must be enabled. +After the empty FPolicy is created, it must be enabled. IMPORTANT: @@ -400,7 +400,7 @@ vserver fpolicy show ![validatefpolicyenabled](/images/accessanalyzer/12.0/config/netappcmode/validatefpolicyenabled.webp) -Relevant NetApp Documentation: To learn more about enabling a policy, please visit the NetApp +Relevant NetApp Documentation: To learn more about enabling a policy, visit the NetApp website and read the [vserver fpolicy enable](https://library.netapp.com/ecmdocs/ECMP1196817/html/vserver/fpolicy/enable.html) article. diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/activity/activity.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/activity/activity.md index 694c852784..e8758e0d62 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/activity/activity.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/activity/activity.md @@ -6,7 +6,7 @@ sidebar_position: 20 # NetApp Data ONTAP Cluster-Mode Activity Auditing Configuration -The Activity Monitor agent employed to monitor NetApp leverages NetApp ONTAP API, and the NetApp +The Activity Monitor agent employed to monitor NetApp uses NetApp ONTAP API, and the NetApp FPolicy framework to monitor file system events. This includes both NetApp 7-Mode and Cluster-Mode configurations. For more information about FPolicy read the [What are the two parts of the FPolicy solution ](https://library.netapp.com/ecmdocs/ECMP1401220/html/GUID-54FE1A84-6CF0-447E-9AAE-F43B61CA2138.html) @@ -25,17 +25,17 @@ list of volumes, list of LIFs. Depending on the configuration, the agent can als of FPolicy to ensure it is enabled; configure FPolicy and register or unregister itself. The FPolicy framework enables the collection of audit events on the ONTAP side and their transfer to -the agent(s) via the designated Data LIFs. Each LIF establishes its own connection with one or +the agents via the designated Data LIFs. Each LIF establishes its own connection with one or several agents and sends notifications as soon as the file transaction occurs. The FPolicy connection is asynchronous and buffered; both ONTAP and Activity Monitor have techniques in place to -make sure that connections are alive and working. The connection can be secured using TLS with +ensure that connections are alive and working. The connection can be secured using TLS with server or mutual authentication. FPolicy may have a significant impact on file system throughput, and it is always a best practice to monitor performance when enabling FPolicy. :::info -Create a tailored FPolicy which only collects the desired activity from the +Create a tailored FPolicy which only collects the activity you want from the environment to limit the scope and impact. ::: @@ -43,13 +43,13 @@ environment to limit the scope and impact. For scale-out and fault tolerance purposes, the product supports a range of deployment options. A single agent can receive events from multiple SVMs. Or events from a single SVM can be distributed among multiple agents. Or a set of SVMs can distribute events among a set of agents. The choice -depends on the fault tolerance requirements and the expected event flow. As a rule of thumb, the -_average_ load on a single agent should not exceed 5000 events per second. +depends on the fault tolerance requirements and the expected event flow. As a guideline, the +_average_ load on a single agent shouldn't exceed 5000 events per second. Starting with ONTAP 9.15.1, the FPolicy Persistent Store provides resilience and predictable latency during scenarios such as network delays or bursts of activity. The feature uses a dedicated volume for each SVM as a staging buffer before events are sent to the agent. FPolicy will automatically -create a volume if one does not already exist. +create a volume if one doesn't already exist. :::info Enable the Persistent Store feature and allow it to create a volume @@ -59,7 +59,7 @@ automatically. ## Configuration Checklist -Complete the following checklist prior to configuring the activity monitoring of NetApp Data ONTAP +Complete the following checklist before configuring the activity monitoring of NetApp Data ONTAP Cluster-Mode devices. Instructions for each item of the checklist are detailed within the following sections. @@ -67,10 +67,10 @@ sections. - Gather the following information: - - Names of the SVM(s) to be monitored + - Names of the SVMs to be monitored - FPolicy is configured for each SVM separately - - This should be the SVM(s) hosting the CIFS or NFS shares(s) to be monitored + - This should be the SVMs hosting the CIFS or NFS sharess to be monitored - Credentials to access ONTAP to provision a role and account. - Desired functionality level: @@ -91,7 +91,7 @@ sections. - Limiting the FPolicy to specific file operations is an effective way to limit the performance impact of FPolicy - - IP Address of the server(s) where the Activity Monitor Agent is deployed + - IP Address of the servers where the Activity Monitor Agent is deployed - API enabled in ONTAP: the classic ONTAPI/ZAPI or the new REST API - The product supports the REST API for ONTAP 9.13.1 and above. @@ -218,9 +218,9 @@ Monitor Agent. - It monitors file system activity on all volumes and shares of the SVM. - FPolicy configuration is automatically updated to reflect the Activity Monitor configuration. - - Requires a Privileged Access credential be provided. + - Requires you to provide a Privileged Access credential. -- Enable the Persistent Store to increase the resilience and control the latency in case of network +- Enable the Persistent Store to increase the resilience and control the latency during network outages or bursts of activity **Checklist Item 5: Activity Monitor Configuration** diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/activity/configurefirewall.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/activity/configurefirewall.md index 1a2d7de662..77ac955971 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/activity/configurefirewall.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/activity/configurefirewall.md @@ -30,11 +30,11 @@ Monitor. Both classic ONTAPI/ZAPI and the new REST API are supported. Starting with ONTAP 9.13.1, the product uses REST API by default if it is available. HTTP and HTTPS protocols are supported. For HTTPS, two -modes are supported: strict and ignore errors. For the strict mode, the product allows you to -disable the host name validation in case the agent cannot resolve the FQDN of the LIF. +modes are supported: strict and ignore errors. For the strict mode, you can +disable the host name validation if the agent can't resolve the FQDN of the LIF. Enabling the API access varies depending on ONTAP version. The following sections list common steps -on enabling the API access. Please refer to the NetApp documentation for more details. +on enabling the API access. refer to the NetApp documentation for more details. ### Management-http Service @@ -74,7 +74,7 @@ network interface service-policy add-service -service management-https -policy d ### Firewall Policy -For ONTAP 9.5 and older, the following commands can be used to either create a new firewall policy +For ONTAP 9.5 and older, use the following commands to either create a new firewall policy or modify an existing policy if ONTAPI is blocked. #### Create New Firewall HTTP Policy @@ -148,15 +148,15 @@ Verify that the output is displayed as follows: ## FPolicy The FPolicy framework enables the collection of audit events on the ONTAP side and their transfer to -the agent(s) via the designated Data LIFs. Each LIF establishes its own connection with one or +the agents via the designated Data LIFs. Each LIF establishes its own connection with one or several agents and sends notifications as soon as the file transaction occurs. The FPolicy connection is asynchronous and buffered; both ONTAP and Activity Monitor have techniques in place to -make sure that connections are alive and working. The connection can be secured using TLS with +ensure that connections are alive and working. The connection can be secured using TLS with server or mutual authentication. ONTAP cluster nodes connect to the agent on port 9999 by default. The port can be changed in the -agent's settings. The agent adds this port to Windows Firewall exclusions automatically. Please -ensure the port is not blocked by other firewalls between ONTAP and the agent. +agent's settings. The agent adds this port to Windows Firewall exclusions automatically. Ensure the +port isn't blocked by other firewalls between ONTAP and the agent. ### Data-fpolicy-client Service diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/activity/configurefpolicy.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/activity/configurefpolicy.md index 0e1fea0f40..5c3763e845 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/activity/configurefpolicy.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/activity/configurefpolicy.md @@ -13,11 +13,11 @@ There are two ways to configure FPolicy: - Activity Monitor agent can facilitate the [Automatic Configuration of FPolicy](#automatic-configuration-of-fpolicy) for the monitored SVM - using the ONTAP API. This mode is simple, but does not allow you to exclude certain volumes or + using the ONTAP API. This mode is simple, but you can't exclude certain volumes or shares of the SVM from being monitored. It also requires additional permissions to create and modify FPolicy. -- Another option is to [Manually Configure FPolicy](#manually-configure-fpolicy) for each SVM. This - mode allows you to fine tune FPolicy by excluding certain volumes or shares from being monitored. +- Another option is to [Manually Configure FPolicy](#manually-configure-fpolicy) for each SVM. With + this mode, you can fine-tune FPolicy by excluding certain volumes or shares from being monitored. It also reduces product permissions. Regardless of the FPolicy configuration approach, perform extra steps if you need to secure FPolicy @@ -78,9 +78,9 @@ locally on the Activity Monitor Console server. ### Create PEM File for Client Certificate -A certificate (Client Certificate) for the SVM needs to be copied to a PEM file. This is required -for the TLS, mutual authentication option. Follow the steps to create the PEM file for the Client -Certificate. +Copy a certificate (Client Certificate) for the SVM to a PEM file. This certificate is required +for the TLS, mutual authentication option. To create the PEM file for the Client +Certificate: **Step 1 –** On the SVM , use the following command to show the security certificate details: @@ -95,8 +95,8 @@ security certificate show -vserver testserver -type server instance ``` **Step 2 –** Copy the security certificate details into a text file and copy the public key to a PEM -file. The following variables from security details will be needed to set mutual-authentication -during Part 6 of manual configuration and prior to automatic configuration: +file. You need the following variables from the security details to set mutual-authentication +during Part 6 of manual configuration and before automatic configuration: - SVM - Common Name @@ -117,7 +117,7 @@ dedicated volume for each SVM as a staging buffer before events are sent to the Persistent Store requires the following parameters: -- Volume name – If the volume does not exist, it will be created automatically (recommended). +- Volume name – If the volume doesn't exist, it will be created automatically (recommended). - Initial volume size – Specifies the starting size of the volume. - Autosize mode – Options include Off, Grow, or Grow/Shrink. @@ -141,7 +141,7 @@ To check that the SVM has assigned local tiers, use the following command: **vserver show -vserver [SVM_NAME] -fields aggr-list** -The command shows currently local tiers. If no tiers are assigned, "-" is displayed. +The command shows local tiers. If no tiers are assigned, "-" is displayed. To assign local tiers to the SVM use the following command: @@ -161,7 +161,7 @@ the directory structure, and protects it from accidental deletion by marking it If you choose to create the volume manually, ensure the following: -- The volume is not mounted and has no junction point. +- The volume isn't mounted and has no junction point. - The snapshot policy for the volume is set to none. For additional and up-to-date recommendations on volumes for the Persistent Store, refer to the @@ -170,8 +170,8 @@ NetApp documentation. ## Manually Configure FPolicy This section describes how to manually configure FPolicy. Use manual configuration when you need to -scope the policy to monitor specific volumes or shares. It is necessary to -create several FPolicy components and then enable the FPolicy. See the sections corresponding to +scope the policy to monitor specific volumes or shares. Create several FPolicy components and then +enable the FPolicy. See the sections corresponding to each part of this list: - Part 1: Install Server Certificate on the SVM (only if using TLS authentication) @@ -185,7 +185,7 @@ each part of this list: - Part 3: Create FPolicy Events - - An FPolicy event defines which protocol(s) to monitor and which file access events to monitor. + - An FPolicy event defines which protocols to monitor and which file access events to monitor. - Part 4: Create Persistent Store (only if Persistent Store is used. RECOMMENDED) @@ -211,7 +211,7 @@ each part of this list: - Part 8: Enable the FPolicy - - Once the FPolicy is enabled, the Activity Monitor Agent can be configured to monitor the SVM. + - After the FPolicy is enabled, the Activity Monitor Agent can be configured to monitor the SVM. - Part 9: Connect FPolicy Server / Agent to Cluster Node (optional) @@ -266,7 +266,7 @@ IMPORTANT: - The following values are required: - `engine-name StealthAUDITEngine`, the names of the external engine object can be customized - (see below). + (see [Customization of FPolicy Object Names](#customization-of-fpolicy-object-names)). - `port 9999`, Port number can be customized, but it is recommended to use 9999. - `extern-engine-type asynchronous` - `ssl-option no-auth` @@ -377,7 +377,7 @@ IMPORTANT: - `read` – File read operations - `first-read` – Limits notification to only first read operations for CIFS protocol. For - ONTAP 9.2+, this filter can be used for both CIFS and NFS protocols. + ONTAP 9.2+, use this filter for both CIFS and NFS protocols. - `rename`– File rename operations - `rename_dir`– Directory rename operations @@ -409,7 +409,7 @@ IMPORTANT: - `write` – File write operations - `first-write` – Limits notification to only first write operations for CIFS protocol. For - ONTAP 9.2+, this filter can be used for both CIFS and NFS protocols. + ONTAP 9.2+, use this filter for both CIFS and NFS protocols. - For failed/denied events, the list of supported file operations is limited to the following values: @@ -531,7 +531,7 @@ IMPORTANT: - `volume` – The name of the volume used for event storage. - - If the volume does not exist, it will be automatically created on an assigned local tier. + - If the volume doesn't exist, it will be automatically created on an assigned local tier. This is recommended. - `size` – The initial size of the volume. The format is `[KB|MB|GB]`. @@ -691,10 +691,10 @@ with an asterisk (\*). IMPORTANT: - The SVM used must be the SVM hosting the CIFS or NFS shares to be monitored. -- It is not necessary to specify both volumes and shares. One or the other is sufficient. +- It isn't necessary to specify both volumes and shares. One or the other is sufficient. - If you want to monitor everything, set the "`volumes-to-include`" value to "`*`". -Use the following command to create the FPolicy scope by specifying volume(s): +Use the following command to create the FPolicy scope by specifying volumes: ``` vserver fpolicy policy scope create -vserver [SVM_NAME] -policy-name StealthAUDIT -volumes-to-include [VOLUME_NAME],[VOLUME_NAME] @@ -706,7 +706,7 @@ Example: vserver fpolicy policy scope create -vserver testserver -policy-name StealthAUDIT -volumes-to-include samplevolume1,samplevolume2 ``` -Use the following command to create the FPolicy scope by specifying share(s): +Use the following command to create the FPolicy scope by specifying shares: ``` vserver fpolicy policy scope create -vserver [SVM_NAME] -policy-name StealthAUDIT -shares-to-include [SHARE_NAME],[SHARE_NAME] @@ -876,7 +876,7 @@ Starting ONTAP 9.15.1 and later versions, it is recommended to enable the Persis that stores events on disk before they are sent to the Activity Monitor Agent. This reduces client-side latency and increases resilience during network delays or bursts of activity. To enable the Persistent Store, specify a volume name and size on the Persistent Store tab of the FPolicy page -in the monitored host properties. The volume will be automatically created if it does not already +in the monitored host properties. The volume will be automatically created if it doesn't already exist. See the [Persistent Store](#persistent-store) topic for additional information on the recommended volume size. @@ -926,6 +926,6 @@ These names can be customized in the monitored host's settings in the Activity M useful in two scenarios: - You want the names to match the company policies; -- You want to configure FPolicy manually using your custom names, but also want to leverage the +- You want to configure FPolicy manually using your custom names, but also want to use the "Enable and Connect FPolicy" feature of the Activity Monitor, so that the product ensures that FPolicy stays enabled and connected at all times. diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/activity/provisionactivity.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/activity/provisionactivity.md index a06458469c..c5ec9592ea 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/activity/provisionactivity.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/activity/provisionactivity.md @@ -26,7 +26,7 @@ The permissions needed depends on the functionality level: - Least Privileged: ONLY Collect Events – This is the minimal functionality level. A user manually configures FPolicy and ensures that it stays enabled and connected. The product only collects - events. This functionality level is not recommended as it requires an additional solution that + events. This functionality level isn't recommended as it requires an additional solution that tracks the state of FPolicy and fixes the problem should ONTAP disconnect or should the policy become disabled. - **_RECOMMENDED:_** Less Privileged: Enable/Connect Policy & Collect Events – With this level, the @@ -41,8 +41,8 @@ Part 2. See the [Validate Part 1: Security Role Configuration](#validate-part-1-security-role-configuration) topic for additional information. -If the FPolicy is to be used for both the Activity Monitor and Access Analyzer, the account also -needs to be provisioned with an additional permission. See the +If you plan to use FPolicy for both the Activity Monitor and Access Analyzer, provision the account +with an additional permission. See the [Access Analyzer Integration](#access-analyzer-integration) topic for additional information. The commands to create a role and names of permissions depend on the ONTAP API used. The product @@ -105,7 +105,7 @@ security login rest-role create -role enterpriseauditorrest -api "/api/svm/svms" ``` :::note -If the FPolicy account is configured with these permissions, it is necessary to manually +If the FPolicy account is configured with these permissions, manually configure the FPolicy. See the [Configure FPolicy](/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/activity/configurefpolicy.md) topic for additional information. ::: @@ -129,7 +129,7 @@ permissions to collect events: :::tip Remember, this permission permits the Activity Monitor to enable the FPolicy. If the “Enable - and connect FPolicy” option is employed but the permission is not provided, the agent will + and connect FPolicy” option is employed but the permission isn't provided, the agent will encounter “Failed to enable policy” errors, but it will still be able to connect to the FPolicy. Since this permission model requires a manual configuration of the FPolicy, then the need to manually enable the FPolicy will be met. @@ -194,7 +194,7 @@ security login rest-role create -role enterpriseauditorrest -api "/api/protocols ``` :::note -If the FPolicy account is configured with these permissions, it is necessary to manually +If the FPolicy account is configured with these permissions, manually configure the FPolicy. See the [Configure FPolicy](/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/activity/configurefpolicy.md) topic for additional information. ::: @@ -342,7 +342,7 @@ article. ## Part 2: Create Security Login -Once the access control role has been created, apply it to a domain account. Ensure the following +After the access control role is created, apply it to a domain account. Ensure the following requirements are met: - The SVM used in the following command must be the same SVM used when creating the access control diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/overview.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/overview.md index 16dd962e83..96e3407364 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/overview.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/netappcmode/overview.md @@ -132,7 +132,7 @@ are required for communication between the Agent server and the Netwrix Activity The Windows firewall rules need to be configured on the Windows server, which require certain inbound rules be created if the scans are running in applet mode. These scans operate over a default -port range, which cannot be specified via an inbound rule. For more information, see the Microsoft +port range, which can't be specified via an inbound rule. For more information, see the Microsoft [Connecting to WMI on a Remote Computer](https://msdn.microsoft.com/en-us/library/windows/desktop/aa389290(v=vs.85).aspx) article. @@ -151,7 +151,7 @@ Agent server and the target NetApp Data ONTAP Cluster-Mode device: Activity Monitor. :::note -If either HTTP or HTTPS are not enabled, the FPolicy on the NetApp Data ONTAP 7-Mode +If either HTTP or HTTPS aren't enabled, the FPolicy on the NetApp Data ONTAP 7-Mode device must be configured manually. Also, the External Engine will not reconnect automatically in the case of a server reboot or service restart. ::: diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/nutanix/access.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/nutanix/access.md index 6483fe3c3e..01a52aed2c 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/nutanix/access.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/nutanix/access.md @@ -11,7 +11,7 @@ Admin: Backup Access only** role assigned. ## Nutanix Prism Central Interface -Follow the steps to configure the required account in the Nutanix Prism Central Interface. +To configure the required account in the Nutanix Prism Central Interface: **Step 1 –** Select the **Home** dropdown and select **File Server**. diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/nutanix/activity.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/nutanix/activity.md index 4e77226158..d9f6bab55f 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/nutanix/activity.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/nutanix/activity.md @@ -12,7 +12,7 @@ A user having REST API access must be created on the Nutanix Files server to mon server using Activity Monitor. Additional configurations are done automatically by Activity Monitor using the Nutanix API with the help of this user. -Follow the steps to create a new user account with Nutanix Prism: +## Create a new user account with Nutanix Prism **Step 1 –** Open Nutanix Prism web portal. @@ -37,7 +37,7 @@ Monitor. :::note -Nutanix Files does not report events for activity originating from a server where the +Nutanix Files doesn't report events for activity originating from a server where the Activity Monitor Agent is installed. ::: diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/nutanix/overview.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/nutanix/overview.md index 096d93ef24..74d8ff0368 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/nutanix/overview.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/nutanix/overview.md @@ -53,7 +53,7 @@ are required for communication between the Agent server and the Netwrix Activity The Windows firewall rules need to be configured on the Windows server, which require certain inbound rules be created if the scans are running in applet mode. These scans operate over a default -port range, which cannot be specified via an inbound rule. For more information, see the Microsoft +port range, which can't be specified via an inbound rule. For more information, see the Microsoft [Connecting to WMI on a Remote Computer](https://msdn.microsoft.com/en-us/library/windows/desktop/aa389290(v=vs.85).aspx) article. diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/qumulo/activity.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/qumulo/activity.md index 28cc36243e..171dd6cde1 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/qumulo/activity.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/qumulo/activity.md @@ -7,8 +7,7 @@ sidebar_position: 10 # Qumulo Activity Auditing Configuration The Netwrix Activity Monitor can be configured to monitor activity on Qumulo devices. To prepare -Qumulo to be monitored, an account needs to be provisioned and the audit event format may need to be -modified. +Qumulo for monitoring, provision an account and modify the audit event format if needed. ## Provision Account @@ -19,7 +18,7 @@ steps to create a new account in the Qumulo web user interface with the Observer **Step 2 –** Assign the Observers role to the user using **Cluster** > **Role Management**. -This credential will then be used when configuring the Activity Agent to monitor the Qumulo device. +Use this credential when configuring the Activity Agent to monitor the Qumulo device. ## Verify Audit Event Format @@ -32,7 +31,7 @@ advanced filtering of Microsoft Office activity also requires the JSON format. The JSON format for audit events was introduced in Qumulo Core 6.0.1. The new format can be enabled via an SSH session to the Qumulo cluster. -Follow the steps to verify that audit event format and change the format, if needed. +Verify the audit event format and change it, if needed: **Step 1 –** Connect to the Qumulo cluster with SSH. diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/qumulo/overview.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/qumulo/overview.md index 76f37aade5..672f01673c 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/qumulo/overview.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/qumulo/overview.md @@ -50,7 +50,7 @@ are required for communication between the Agent server and the Netwrix Activity The Windows firewall rules need to be configured on the Windows server, which require certain inbound rules be created if the scans are running in applet mode. These scans operate over a default -port range, which cannot be specified via an inbound rule. For more information, see the Microsoft +port range, which can't be specified via an inbound rule. For more information, see the Microsoft [Connecting to WMI on a Remote Computer](https://msdn.microsoft.com/en-us/library/windows/desktop/aa389290(v=vs.85).aspx) article. diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/windowsfile/access.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/windowsfile/access.md index b74fcf9d87..8af8374f9d 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/windowsfile/access.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/windowsfile/access.md @@ -17,7 +17,7 @@ Namespaces. ## Windows File System (Standard) -Configure the credential(s) with the following rights on the Windows host(s): +Configure the credentials with the following rights on the Windows hosts: - Granted the "Network access: Restrict clients allowed to make remote calls to SAM" Local Policies > Security Options privilege - Granted the “Backup files and directories” local policy privilege @@ -30,11 +30,11 @@ Configure the credential(s) with the following rights on the Windows host(s): - Local Administrators - Granted the “Log on as a batch” privilege - Remote Registry service must be enabled on the host where the applet is deployed (Applet or Proxy w/ Applet scans) to determine the system platform and where to deploy the applet. - - The local policy, “Network access: Do not allow storage of passwords and credentials for network authentication” must be disabled in order for the applet to start. + - The local policy, “Network access: Don't allow storage of passwords and credentials for network authentication” must be disabled in order for the applet to start. - Sensitive Data Discovery Auditing scans require .NET Framework 4.7.2 or later to be installed on the server where the applet is to be deployed in order for Sensitive Data Discovery collections to successfully occur. :::note -In order to collect data on administrative shares and local policies (logon policies) for a Windows target, the credential must have group membership in the local Administrators group. +to collect data on administrative shares and local policies (logon policies) for a Windows target, the credential must have group membership in the local Administrators group. ::: ## Windows File System Clusters @@ -43,7 +43,7 @@ The permissions necessary to collect file system data from a Windows File System for all nodes that comprise the cluster. :::note -It is necessary to target the Windows Cluster File Server Role Server (name clients connect to) of interest when running a File System scan against a Windows File System Cluster. +Target the Windows Cluster File Server Role Server (name clients connect to) of interest when running a File System scan against a Windows File System Cluster. ::: Configure credentials on all cluster nodes according to the Windows File System (Standard) permissions, with the following additional requirements: @@ -54,7 +54,7 @@ Configure credentials on all cluster nodes according to the Windows File System ### Host List Considerations -It is necessary to target the Windows File Server Cluster (name of the cluster) of interest when running a File System scan against a Windows File System Cluster. Within the Master Host Table, there should be a host entry for the cluster as well as for each node. Additionally, each of these host entries must have the name of the cluster in the `WinCluster` column in the host inventory data. This may need to be updated manually. +Target the Windows File Server Cluster (name of the cluster) of interest when running a File System scan against a Windows File System Cluster. Within the Master Host Table, there should be a host entry for the cluster as well as for each node. Additionally, each of these host entries must have the name of the cluster in the `WinCluster` column in the host inventory data. This may need to be updated manually. See the View/Edit section of the [Host Management Activities](https://docs.netwrix.com/docs/accessanalyzer/12_0/admin/hostmanagement/actions/overview) topic for additional information on host inventory. @@ -62,7 +62,7 @@ See the View/Edit section of the [Host Management Activities](https://docs.netwr The host targeted by the File System scans is only the host entry for the cluster. For example: -The environment has a Windows File System Cluster named `ExampleCluster1` with three nodes named `ExampleNodeA`, `ExampleNodeB`, and `ExampleNodeC`. There would be four host entries in the Access Analyzer Master Host Table: `ExampleCluster1`, `ExampleNodeA`, `ExampleNodeB`, and `ExampleNodeC`. Each of these four entries would have the same value of the cluster name in the `WinCluster` column: `ExampleCluster1`. An additional entry containing the File Server Role Server name(s) should also be added, including the WinCluster name of the nodes. **This File Server Role Server name will be our target host.** +The environment has a Windows File System Cluster named `ExampleCluster1` with three nodes named `ExampleNodeA`, `ExampleNodeB`, and `ExampleNodeC`. There would be four host entries in the Access Analyzer Master Host Table: `ExampleCluster1`, `ExampleNodeA`, `ExampleNodeB`, and `ExampleNodeC`. Each of these four entries would have the same value of the cluster name in the `WinCluster` column: `ExampleCluster1`. An additional entry containing the File Server Role Server names should also be added, including the WinCluster name of the nodes. **This File Server Role Server name is the target host.** ### Least Privilege Permission Model for Windows Clusters @@ -84,7 +84,7 @@ comprise the cluster: The FileSystem > 0.Collection > 0-FSDFS System Scans Job is configured by default to target the default domain controller for the domain in which Access Analyzer resides. This is the appropriate target host for this job when targeting a domain-based namespace. To target a standalone namespace -or multiple namespaces, create a custom host list of the server(s) hosting the namespace(s). Then +or multiple namespaces, create a custom host list of the servers hosting the namespaces. Then assign the custom host list to the 0-FSDFS System Scans Job. No additional host list is require for the FileSystem > 0.Collection Job Group unless additional file servers are also being targeted. diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/windowsfile/activity.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/windowsfile/activity.md index 64ffdd9481..b1eb7b6535 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/windowsfile/activity.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/windowsfile/activity.md @@ -10,7 +10,7 @@ In order for Netwrix Access Analyzer to collect and store Windows file server ac ## Windows File System (Standard) -Configure the credential(s) with the following rights on the Windows host(s): +Configure the credentials with the following rights on the Windows hosts: - For **Local** or **Proxy as a Service Mode** Scans: - Group membership in both of the following local groups: @@ -21,7 +21,7 @@ Configure the credential(s) with the following rights on the Windows host(s): - Local Administrators - Granted the “Log on as a batch” privilege - Remote Registry service must be enabled on the host where the applet is deployed (Applet or Proxy w/ Applet scans) to determine the system platform and where to deploy the applet. - - The local policy, “Network access: Do not allow storage of passwords and credentials for network authentication” must be disabled in order for the applet to start. + - The local policy, “Network access: Don't allow storage of passwords and credentials for network authentication” must be disabled in order for the applet to start. - Granted the "Network access: Restrict clients allowed to make remote calls to SAM" Local Policies > Security Options privilege - Granted the “Backup files and directories” local policy privilege - The service account in the credential profile requires access to the admin share (e.g. `C$`) where the `sbtfilemon.ini` file exists @@ -29,10 +29,10 @@ Configure the credential(s) with the following rights on the Windows host(s): ## Windows File System Clusters -In order to monitor a Windows File System Cluster, an Activity Agent needs to be deployed on all nodes that comprise the Windows File System Cluster. +To monitor a Windows File System Cluster, deploy an Activity Agent on all nodes that comprise the cluster. :::note -It is necessary to target the Windows Cluster File Server Role Server (name clients connect to) when running a File System scan against a Windows File System Cluster. +Target the Windows Cluster File Server Role Server (name clients connect to) when running a File System scan against a Windows File System Cluster. ::: Configure credentials according to the Windows File System (Standard) permissions on all cluster nodes that comprise the cluster, with the following additional requirements: @@ -43,7 +43,7 @@ Configure credentials according to the Windows File System (Standard) permission ### Host List Considerations -It is necessary to target the Windows File Server Cluster (name of the cluster) of interest when running a File System scan against a Windows File System Cluster. Within the Master Host Table, there should be a host entry for the cluster as well as for each node. Additionally, each of these host entries must have the name of the cluster in the `WinCluster` column in the host inventory data. This may need to be updated manually. +Target the Windows File Server Cluster (name of the cluster) of interest when running a File System scan against a Windows File System Cluster. Within the Master Host Table, there should be a host entry for the cluster as well as for each node. Additionally, each of these host entries must have the name of the cluster in the `WinCluster` column in the host inventory data. This may need to be updated manually. See the View/Edit section of the [Host Management Activities](https://docs.netwrix.com/docs/accessanalyzer/12_0/admin/hostmanagement/actions/overview) topic for additional information on host inventory. @@ -53,7 +53,7 @@ The host targeted by the File System scans is only the host entry for the cluste :::note Example: -The environment has a Windows File System Cluster named `ExampleCluster1` with three nodes named `ExampleNodeA`, `ExampleNodeB`, and `ExampleNodeC`. There would be four host entries in the Access Analyzer Master Host Table: `ExampleCluster1`, `ExampleNodeA`, `ExampleNodeB`, and `ExampleNodeC`. Each of these four entries would have the same value of the cluster name in the `WinCluster` column: `ExampleCluster1`. An additional entry containing the File Server Role Server name(s) should also be added, including the WinCluster name of the nodes. This File Server Role Server name will be our target host. +The environment has a Windows File System Cluster named `ExampleCluster1` with three nodes named `ExampleNodeA`, `ExampleNodeB`, and `ExampleNodeC`. There would be four host entries in the Access Analyzer Master Host Table: `ExampleCluster1`, `ExampleNodeA`, `ExampleNodeB`, and `ExampleNodeC`. Each of these four entries would have the same value of the cluster name in the `WinCluster` column: `ExampleCluster1`. An additional entry containing the File Server Role Server names should also be added, including the WinCluster name of the nodes. This File Server Role Server name is the target host. ::: ### Host Mapping @@ -83,4 +83,4 @@ If a least privilege model is required by the organization, then the credential * `HKEY_LOCAL_MACHINE\Cluster\Nodes` * `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SBTLogging\Parameters` -Additionally, the credential must have READ access to the path where the activity log files are located. \ No newline at end of file +Additionally, the credential must have READ access to the path where the activity log files are located. diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/windowsfile/overview.md b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/windowsfile/overview.md index 6ba064a2da..1ea616697f 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/windowsfile/overview.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/filesystems/windowsfile/overview.md @@ -61,7 +61,7 @@ are required for communication between the Agent server and the Netwrix Activity The Windows firewall rules need to be configured on the Windows server, which require certain inbound rules be created if the scans are running in applet mode. These scans operate over a default -port range, which cannot be specified via an inbound rule. For more information, see the Microsoft +port range, which can't be specified via an inbound rule. For more information, see the Microsoft [Connecting to WMI on a Remote Computer](https://msdn.microsoft.com/en-us/library/windows/desktop/aa389290(v=vs.85).aspx) article. diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/applet-mode-scans/appletmodepermissions.md b/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/applet-mode-scans/appletmodepermissions.md index f50afaac10..4dea984329 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/applet-mode-scans/appletmodepermissions.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/applet-mode-scans/appletmodepermissions.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Applet Mode Permissions -When File System scans are run in applet mode, it means the File System applet is deployed to the target host when the job is executed to conduct data collection. However, the applet can only be deployed to a server with a Windows operating system. The data is collected on the Windows target host where the applet is deployed. The final step in data collection is to compress and transfer the data collected in the SQLite database(s), or Tier 2 database(s), back to the Access Analyzer Console server. If the target host is a NAS device, the File System scans will default to local mode for that host. +When File System scans are run in applet mode, it means the File System applet is deployed to the target host when the job is executed to conduct data collection. However, the applet can only be deployed to a server with a Windows operating system. The data is collected on the Windows target host where the applet is deployed. The final step in data collection is to compress and transfer the data collected in the SQLite databases, or Tier 2 databases, back to the Access Analyzer Console server. If the target host is a NAS device, the File System scans will default to local mode for that host. Additionally, the credential must have `WRITE` access to the `…\StealthAUDIT\FSAA` folder in the installation directory on the target host/proxy server as well as on the Access Analyzer Console server. This is required by either the user account running the Access Analyzer application, when manually executing jobs within the console, or the Schedule Service Account assigned within Access Analyzer, when running jobs as a scheduled tasks. @@ -21,7 +21,7 @@ the applet. ::: :::warning -The local policy, “Network access: Do not allow storage of passwords and credentials +The local policy, “Network access: Don't allow storage of passwords and credentials for network authentication” must be disabled in order for the applet to start. ::: @@ -37,8 +37,8 @@ By default, the Applet will run as the connection profile account unless an addi The account used in the connection profile associated with the File System scan jobs, should have the appropriate permissions required to access the target host. See the [File System Supported Platforms](https://docs.netwrix.com/docs/accessanalyzer/12_0/requirements/filesystem/filesystems/) page for specific requirements per target file system. -## How do I determine if I’m using Applet Mode scanning? +## Determine whether you're using Applet Mode scanning The best way to verify if you’re using Applet Mode scanning is via the FSAA Data Collector Query Settings > [Scan Server Selection](https://docs.netwrix.com/docs/accessanalyzer/12_0/admin/datacollector/fsaa/scanserverselection) page: -- **Automatic** — If the target host being scanned is a Windows host, NEA will deploy for FS scanning. \ No newline at end of file +- **Automatic** — If the target host being scanned is a Windows host, NEA will deploy for FS scanning. diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/applet-mode-scans/appletmodeports.md b/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/applet-mode-scans/appletmodeports.md index ff440b76b5..e2bf98e386 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/applet-mode-scans/appletmodeports.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/applet-mode-scans/appletmodeports.md @@ -6,7 +6,7 @@ sidebar_position: 20 # Applet Mode Port Requirements -The following are the firewall settings are required when executing the Access Auditing (FSAA) +The following firewall settings are required when executing the Access Auditing (FSAA) and/or Sensitive Data Discovery Auditing scans in applet mode for communication between Access Analyzer and the host: diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/local-mode-scans/localmodepermissions.md b/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/local-mode-scans/localmodepermissions.md index fdad7eebc1..372539eda3 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/local-mode-scans/localmodepermissions.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/local-mode-scans/localmodepermissions.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Local Mode Permissions -When File System scans are run in local mode, it means all of the data collection processing is conducted by the Access Analyzer Console server across the network. The data is collected in the SQLite database(s), or Tier 2 database(s), on the Access Analyzer Console server, and then imported into the Access Analyzer database, or Tier 1 database, on the SQL Server. +When File System scans are run in local mode, it means all of the data collection processing is conducted by the Access Analyzer Console server across the network. The data is collected in the SQLite databases, or Tier 2 databases, on the Access Analyzer Console server, and then imported into the Access Analyzer database, or Tier 1 database, on the SQL Server. The account used to run either a manual execution or a scheduled execution of the File System scans, must have the following permissions on the Access Analyzer Console server: @@ -19,7 +19,7 @@ The account used to run either a manual execution or a scheduled execution of th Additionally, the credential must have `WRITE` access to the `…\StealthAUDIT\FSAA` folder in the installation directory on the Access Analyzer Console server. This is required by either the user account running the Access Analyzer application, when manually executing jobs within the console, or the Schedule Service Account assigned within Access Analyzer, when running jobs as a scheduled tasks. -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host.  By default, SDD scans are configured to run two concurrent threads. For example, if the job is configured to scan 8 hosts at a time with two concurrent SDD threads, then an extra 32 GB of RAM are required (8x2x2=32). +If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. By default, SDD scans are configured to run two concurrent threads. For example, if the job is configured to scan 8 hosts at a time with two concurrent SDD threads, then an extra 32 GB of RAM are required (8x2x2=32). Firewall rules must be configured to allow for communication between the applicable servers. See the [Local Mode Port Requirements](https://docs.netwrix.com/docs/accessanalyzer/12_0/requirements/filesystem/scanoptions/local-mode-scans/localmodeports) topic for firewall rule information. @@ -32,9 +32,9 @@ See the [Local Mode Port Requirements](/docs/accessanalyzer/12.0/requirements/fi The account used in the connection profile associated with the File System scan jobs, should have the appropriate permissions required to access the target host. See the [File System Supported Platforms](https://docs.netwrix.com/docs/accessanalyzer/12_0/requirements/filesystem/filesystems/) page for specific requirements per target file system. -## How do I determine if I’m using Local Mode scanning? +## Determine whether you're using Local Mode scanning The best way to verify if you’re using Local Mode scanning is via the FSAA Data Collector Query Settings > [Scan Server Selection](https://docs.netwrix.com/docs/accessanalyzer/12_0/admin/datacollector/fsaa/scanserverselection) page: -- **Automatic** — If the target host being scanned is a NAS/Non-Windows host, a Local Mode scan will be utilized. -- **Local Server** — This will utilize a Local Mode scan, regardless of the OSType of the target host. \ No newline at end of file +- **Automatic** — If the target host being scanned is a NAS/Non-Windows host, a Local Mode scan will be used. +- **Local Server** — This will use a Local Mode scan, regardless of the OSType of the target host. diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/local-mode-scans/localmodeports.md b/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/local-mode-scans/localmodeports.md index 339a712512..672f9650fa 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/local-mode-scans/localmodeports.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/local-mode-scans/localmodeports.md @@ -6,7 +6,7 @@ sidebar_position: 20 # Local Mode Port Requirements -The following are the firewall settings are required when executing the Access Auditing (FSAA) +The following firewall settings are required when executing the Access Auditing (FSAA) and/or Sensitive Data Discovery Auditing scans in local mode for communication between Access Analyzer and the target host: diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/proxy-mode-scans/as-a-service/proxymodeservicepermissions.md b/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/proxy-mode-scans/as-a-service/proxymodeservicepermissions.md index 638c395cb4..daa0d20d4c 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/proxy-mode-scans/as-a-service/proxymodeservicepermissions.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/proxy-mode-scans/as-a-service/proxymodeservicepermissions.md @@ -53,7 +53,7 @@ rule information. - Console ↔ Proxy: **NAA** **Computer Account (Kerberos)** - Target Access (Proxy ↔ Targets): Connection Profile Account :::note -If the service is deployed by the File System Scan job (as opposed to manually installed), the account used by the connection profile will be used to run the FSAA Proxy Service unless **Run service as Local System** is checked on the Applet Settings page of the job query. Alternatively, you can add a credential to the connection profile using either **Task (Local)** or **Task (Domain)** to run the service. +If the File System Scan job deploys the service (as opposed to a manual installation), the FSAA Proxy Service runs using the connection profile account unless you select **Run service as Local System** on the Applet Settings page of the job query. Alternatively, you can add a credential to the connection profile using either **Task (Local)** or **Task (Domain)** to run the service. If the target host resides in a different domain than the proxy server and there is no trust relationship between the two domains, you must stack a task credential for the proxy domain with the credential for scanning the target file system. diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/proxy-mode-scans/as-a-service/proxymodeserviceports.md b/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/proxy-mode-scans/as-a-service/proxymodeserviceports.md index d273ae4d88..e20e55532e 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/proxy-mode-scans/as-a-service/proxymodeserviceports.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/proxy-mode-scans/as-a-service/proxymodeserviceports.md @@ -6,7 +6,7 @@ sidebar_position: 20 # Proxy Mode as a Service Port Requirements -The following are the firewall settings are required when executing the Access Auditing (FSAA) +The following firewall settings are required when executing the Access Auditing (FSAA) and/or Sensitive Data Discovery Auditing scans in proxy mode as a service for communication between Access Analyzer and the proxy server: @@ -22,7 +22,7 @@ Data Collector Wizard. ::: -The following are the firewall settings are required when executing the Access Auditing (FSAA) +The following firewall settings are required when executing the Access Auditing (FSAA) and/or Sensitive Data Discovery Auditing scans in proxy mode as a service for communication between the proxy server and the target host: diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/proxy-mode-scans/proxymodeserver.md b/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/proxy-mode-scans/proxymodeserver.md index 773449ce98..7694d4e31b 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/proxy-mode-scans/proxymodeserver.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/proxy-mode-scans/proxymodeserver.md @@ -27,8 +27,8 @@ The server can be physical or virtual. The requirements for Access Analyzer are: RAM, CPU, and Disk Space are dependent upon the size of the target environment: :::warning -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the -minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. By +If you run Sensitive Data Discovery (SDD) scans, increase the minimum amount of RAM. Each +thread requires a minimum of 2 additional GB of RAM per host. By default, SDD scans are configured to run two concurrent threads. For example, if the job is configured to scan 8 hosts at a time with two concurrent SDD threads, then an extra 32 GB of RAM are required (8x2x2=32). @@ -65,8 +65,8 @@ required (8x2x2=32). - 2 CPU Cores - 130 GB Disk Space -The above recommended disk space sizing information is based on the needs of Access Analyzer as well -as the File System solution for running Permission scans with out of the box configuration (500 MB +This recommended disk space sizing information is based on the needs of Access Analyzer as well +as the File System solution for running Permission scans with the default configuration (500 MB per million files and folders), that means no tag collection, file-level scanning, activity, or sensitive data. @@ -77,7 +77,7 @@ sensitive data. total size of the documents scanned for sensitive data (depending on targeted document types and selected criteria) to the totals above -For example, in order to scan 200 million files and folders, of which 10 million files will be +For example, to scan 200 million files and folders, of which 10 million files will be scanned for tag collection and sensitive data with a total size of 6 TB, you would need: 160 GB for permission collection + 1.25 GB for tag collection (10x125 MB) + 100 GB for sensitive data collection (200x500 MB) + 600 GB additional for sensitive data collection (10% of 6 TB) = 861.25 GB @@ -107,7 +107,7 @@ The following are additional requirements for the server: **Sensitive Data Discovery Auditing** The appropriate JDK (Java) version for Sensitive Data Discovery is installed on the server. The JDK -deployed is prepackaged and does not require any configuration. It will not conflict with other JDKs +deployed is prepackaged and doesn't require any configuration. It will not conflict with other JDKs or Java Runtimes in the same environment. See the following topics for additional information, based on the type of proxy mode you plan to diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/proxy-mode-scans/with-applet/proxymodeappletpermissions.md b/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/proxy-mode-scans/with-applet/proxymodeappletpermissions.md index ab5c4aaa49..2cfe18fe5a 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/proxy-mode-scans/with-applet/proxymodeappletpermissions.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/proxy-mode-scans/with-applet/proxymodeappletpermissions.md @@ -14,7 +14,7 @@ Configure the credentials with the following rights on the proxy servers: - Granted the Backup files and directories local policy privilege - Granted the Log on as a batch privilege -Additionally, the credential must have `WRITE` access to the `…\StealthAUDIT\FSAA` folder in the installation directory on the proxy server as well as on the Access Analyzer Console server. This is required by either the user account running the Access Analyzer application, when manually executing jobs within the console, or the Schedule Service Account assigned within Access Analyzer, when running jobs as a scheduled tasks. +Additionally, the credential must have `WRITE` access to the `…\StealthAUDIT\FSAA` folder in the installation directory on the proxy server as well as on the Access Analyzer Console server. Whichever account runs the job needs this access — either the user account running the Access Analyzer application, when you execute jobs manually within the console, or the Schedule Service Account assigned within Access Analyzer, when jobs run as scheduled tasks. :::tip Remember, Remote Registry Service must be enabled on the host where the applet is deployed (for @@ -29,9 +29,8 @@ for network authentication” must be disabled for the applet to start. ::: -Sensitive Data Discovery Auditing scans require .NET Framework 4.7.2 or later to be installed on the -server where the applet is to be deployed in order for Sensitive Data Discovery collections to -successfully occur. +Sensitive Data Discovery Auditing scans require .NET Framework 4.7.2 or later on the server where +the applet is deployed. See the [Proxy Mode with Applet Port Requirements](/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/proxy-mode-scans/with-applet/proxymodeappletports.md) topic for firewall rule @@ -40,14 +39,14 @@ information. **Secure Proxy Communication Considerations** For Proxy Mode with Applet scans, the certificate exchange mechanism and certificate exchange port -must be configured via the File System Access Auditing Data Collector Wizard before executing a -scan. See the +must be configured via the File System Access Auditing (FSAA) Data Collector Wizard before executing +a scan. See the [FSAA Applet Certificate Management Overview](/docs/accessanalyzer/12.0/admin/datacollector/fsaa/certificatemanagement/certificatemanagement.md) topic for additional information. ## Accounts Used - **Job Execution:** Scheduled Task or Console User (launches the job) -- Console ↔ Applet: **NAA** **Computer Account (Kerberos)** +- Console ↔ Applet: **Netwrix Access Analyzer (NAA) Computer Account (Kerberos)** - Target Access (Applet ↔ Targets): Connection Profile Account :::note diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/proxy-mode-scans/with-applet/proxymodeappletports.md b/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/proxy-mode-scans/with-applet/proxymodeappletports.md index 7664a4b031..e1873c13a9 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/proxy-mode-scans/with-applet/proxymodeappletports.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/proxy-mode-scans/with-applet/proxymodeappletports.md @@ -6,9 +6,9 @@ sidebar_position: 20 # Proxy Mode with Applet Port Requirements -The following are the firewall settings are required when executing the Access Auditing (FSAA) -and/or Sensitive Data Discovery Auditing scans in proxy mode with applet for communication between -Access Analyzer and the proxy server: +The following firewall settings are required for communication between Access Analyzer and the +proxy server when running Access Auditing (FSAA) and/or Sensitive Data Discovery Auditing scans in +proxy mode with applet: | Communication Direction | Protocol | Ports | Description | | -------------------------------------------------------- | -------- | ----- | ---------------------------------------- | @@ -23,9 +23,9 @@ Data Collector Wizard. ::: -The following are the firewall settings are required when executing the Access Auditing (FSAA) -and/or Sensitive Data Discovery Auditing scans in proxy mode with applet for communication between -the proxy server and the target host: +The following firewall settings are required for communication between the proxy server and the +target host when running Access Auditing (FSAA) and/or Sensitive Data Discovery Auditing scans in +proxy mode with applet: | Communication Direction | Protocol | Ports | Description | | ------------------------------------------ | -------- | ----- | ----------- | diff --git a/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/scanoptions.md b/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/scanoptions.md index 53dbfc47a1..c19aa5e6a6 100644 --- a/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/scanoptions.md +++ b/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/scanoptions.md @@ -6,21 +6,21 @@ sidebar_position: 10 # File System Scan Options -Required permissions on the targeted file system are dependent upon not only the type of environment -targeted but also the mode in which the data collection scan is executed. There are three primary +Required permissions on the targeted file system depend on the type of environment targeted and the +mode in which the data collection scan runs. There are three primary types of scan modes: local, applet, or proxy. The proxy mode can be conducted via applet deployment, or via running as a service (installed in advance). -For the purpose of this document, “applet” refers to the runtime deployment of the +To describe scan modes in this document, “applet” refers to the runtime deployment of the `FSAAAppletServer.exe` to either the target host (applet mode scans) or the proxy host (proxy mode -with applet scans) via Microsoft Task Scheduler. A “proxy” host is any host which can be leveraged +with applet scans) via Microsoft Task Scheduler. A “proxy” host is any host you can use for running File System scans against target hosts. ## Local Mode When File System scans are run in local mode, it means all of the data collection processing is conducted by the Access Analyzer Console server across the network. The data is collected in the -SQLite database(s), or Tier 2 database(s), on the Access Analyzer Console server, and then imported +SQLite databases, or Tier 2 databases, on the Access Analyzer Console server, and then imported into the Access Analyzer database, or Tier 1 database, on the SQL Server. ![Illustrates the Enterprise Auditor server running the scan against a file server](/images/accessanalyzer/12.0/requirements/solutions/filesystem/localmode.webp) @@ -35,7 +35,7 @@ See the following topics for additional information: ## Applet Mode :::warning -The local policy, “Network access: Do not allow storage of passwords and credentials +The local policy, “Network access: Don't allow storage of passwords and credentials for network authentication” must be disabled in order for the applet to start. ::: @@ -44,7 +44,7 @@ When File System scans are run in applet mode, it means the File System applet i target host when the job is executed to conduct data collection. However, the applet can only be deployed to a server with a Windows operating system. The data is collected on the Windows target host where the applet is deployed. The final step in data collection is to compress and transfer the -data collected in the SQLite database(s), or Tier 2 database(s), back to the Access Analyzer Console +data collected in the SQLite databases, or Tier 2 databases, back to the Access Analyzer Console server. If the target host is a NAS device, the File System scans will default to local mode for that host. @@ -61,14 +61,14 @@ See the following topics for additional information: ## Proxy Mode with Applet :::warning -The local policy, “Network access: Do not allow storage of passwords and credentials +The local policy, “Network access: Don't allow storage of passwords and credentials for network authentication” must be disabled in order for the applet to start. ::: When File System scans are run in proxy mode with applet, it means the File System applet is deployed to the Windows proxy server when the job is executed to conduct data collection. The data -collection processing is initiated by the proxy server where the applet is deployed and leverages a +collection processing is initiated by the proxy server where the applet is deployed and uses a local mode-type scan to each of the target hosts. The final step in data collection is to compress and transfer the data collected in the SQLite databases, or Tier 2 databases, back to the Access Analyzer Console server. @@ -86,17 +86,17 @@ See the following topics for additional information: ## Proxy Mode as a Service -When File System scans are run in proxy mode as a service, there are two methods available for -deploying the service: +When File System scans are run in proxy mode as a service, you can deploy the service in one of two +ways: - Pre-Installed File System Proxy Service – File System Proxy Service installation package must be - installed on the Windows proxy servers prior to executing the scans. This is the recommended + installed on the Windows proxy servers before executing the scans. This is the recommended method. - Ad Hoc File System Proxy Service Deployment – File System Proxy Service is installed on the Windows proxy server when the job is executed The data collection processing is conducted by the proxy server where the service is running and -leverages a local mode-type scan to each of the target hosts. The final step in data collection is +uses a local mode-type scan to each of the target hosts. The final step in data collection is to compress and transfer the data collected in the SQLite databases, or Tier 2 databases, back to the Access Analyzer Console server. diff --git a/docs/accessanalyzer/12.0/requirements/overview.md b/docs/accessanalyzer/12.0/requirements/overview.md index ec1f7714c0..760c77faf5 100644 --- a/docs/accessanalyzer/12.0/requirements/overview.md +++ b/docs/accessanalyzer/12.0/requirements/overview.md @@ -7,9 +7,8 @@ sidebar_position: 20 # Requirements This topic describes the recommended configuration of the servers needed to install the application -in a production environment. Depending on the size of the organization, it is recommended to review -your environment and requirements with a Netwrix engineer prior to deployment to ensure all -exceptions are covered. +in a production environment. Depending on the size of your organization, review your environment +and requirements with a Netwrix engineer before deployment to make sure all exceptions are covered. ## Architecture Overview @@ -18,8 +17,8 @@ The following servers and applications are required for installation of the appl **Core Components** - Access Analyzer Console Server – This is where the v12.0 application is installed. -- SQL Server for Access Analyzer Database – As a data-intensive application, a well-provisioned, - dedicated SQL Server is recommended. +- SQL Server for Access Analyzer Database – Because Access Analyzer is a data-intensive + application, use a well-provisioned, dedicated SQL Server for the database. - Access Information Center Application Server – This application is typically installed on the Access Analyzer Console server and is a browser-based, interactive dashboard for exploring permissions, activity, and sensitive data. @@ -37,10 +36,10 @@ The following servers and applications are required for installation of the appl **File System Solution-Specific Components** -- Access Analyzer File System Proxy Server – In certain environments, a proxy server may be utilized - to scan hosts in remote or firewalled sites to increase scan capacity in large environments. This - feature can be implemented through either an applet or a service. The applet would be deployed as - part of the data collection process. The service should be installed prior to data collection. See +- Access Analyzer File System Proxy Server – In certain environments, a proxy server can scan hosts + in remote or firewalled sites to increase scan capacity in large environments. You can implement + this feature through either an applet or a service: the applet deploys as part of the data + collection process, and you install the service before data collection. See the [Proxy Mode as a Service](/docs/accessanalyzer/12.0/requirements/filesystem/scanoptions/scanoptions.md#proxy-mode-as-a-service) topic for server requirements. @@ -48,7 +47,7 @@ The following servers and applications are required for installation of the appl - Access Analyzer SharePoint Agent Server – For agent-based scans, this application can be installed on the SharePoint application server that hosts the “Central Administration” component of the - targeted farm(s) to auditing permissions, content, and sensitive data for SharePoint On-Premise. + targeted farms to auditing permissions, content, and sensitive data for SharePoint On-Premise. See the [SharePoint Scan Options](/docs/accessanalyzer/12.0/requirements/sharepoint/scanoptions/scanoptions.md) topic for server requirements. @@ -66,8 +65,8 @@ The following servers and applications are required for installation of the appl **Target Environment Considerations** -The target environment encompasses all servers, devices, or infrastructure to be audited by Access -Analyzer. Most solutions have additional target requirements. +The target environment encompasses all servers, devices, or infrastructure that Access Analyzer +audits. Most solutions have additional target requirements. ## Access Analyzer Console & Access Information Center Server Requirements @@ -176,7 +175,7 @@ The following additional considerations are recommended for the SQL Server: - The standard Autogrowth setting can cause Access Analyzer job delays. Database growth is computationally intensive. While SQL Server is growing the database, no other activity can occur. - If this option is employed, please speak with a Netwrix engineer to determine an appropriate + If you use this option, speak with a Netwrix engineer to determine an appropriate setting for best performance. - Microsoft SQL Server supports TLS 1.2, which requires the Access Analyzer Console server to have either SQL Server Native Client 11 or Microsoft OleDB 18 installed. @@ -191,10 +190,10 @@ The following permissions are required on the databases: ## Virtual Environment Recommendations -While physical machines are always preferred, we fully support the use of virtual machines. This -section contains special considerations when leveraging virtualization. +While physical machines are always preferred, Access Analyzer fully supports the use of virtual machines. This +section contains special considerations for virtualized environments. -- VMWare® ESX® – If using ESX, the following specifications are recommended: +- VMWare® ESX® – If you use ESX, the following specifications are recommended: - ESX 4.0 / ESXi™ 4.1 or higher - Virtual Hardware 7 or higher @@ -202,5 +201,5 @@ section contains special considerations when leveraging virtualization. - Virtual Storage Consideration - - In the server requirements, when separate disks are required for the servers, that should - translate to separate data stores on the VM host machine. + - When the server requirements call for separate disks, use separate data stores on the VM + host machine. diff --git a/docs/accessanalyzer/12.0/requirements/sharepoint/scanoptions/agent-based-scans/agentpermissions.md b/docs/accessanalyzer/12.0/requirements/sharepoint/scanoptions/agent-based-scans/agentpermissions.md index d0a8d7f8a7..fe3eb42a95 100644 --- a/docs/accessanalyzer/12.0/requirements/sharepoint/scanoptions/agent-based-scans/agentpermissions.md +++ b/docs/accessanalyzer/12.0/requirements/sharepoint/scanoptions/agent-based-scans/agentpermissions.md @@ -8,7 +8,7 @@ sidebar_position: 10 When Access Analyzer SharePoint scans are run in agent-based mode, the Access Analyzer SharePoint Agent must be installed on the SharePoint Application server which hosts the Central Administration -component prior to executing the scans. This is typically the first server stood up during the +component before executing the scans. This is typically the first server stood up during the SharePoint farm installation process in this mode. The data collection processing is conducted by the SharePoint Agent for the target environment. The final step in data collection is to transfer the data collected in the SQLite databases, or Tier 2 databases, on the Access Analyzer SharePoint @@ -32,19 +32,19 @@ The following are additional requirements for the Access Analyzer SharePoint Age :::note The appropriate JDK (Java) version for Sensitive Data Discovery is installed on the -server. The JDK deployed is prepackaged and does not require any configuration; it has been +server. The JDK deployed is prepackaged and doesn't require any configuration; it has been preconfigured to work with Access Analyzer and should never be customized through Java. It will not conflict with other JDKs or Java Runtimes in the same environment. ::: -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the minimum amount -of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For example, if the job +If you run Sensitive Data Discovery (SDD) scans, increase the minimum amount of RAM. Each thread +requires a minimum of 2 additional GB of RAM per host. For example, if the job is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are required (8x2=16). ## Permissions Explained -If limited provisioning of the service account is not required by the organization, then the +If limited provisioning of the service account isn't required by the organization, then the following permissions are sufficient for successful agent-based scans: - Membership in the local Administrator group on the on server where the Access Analyzer SharePoint @@ -77,11 +77,11 @@ following permissions are sufficient for successful agent-based scans: - This is required so the Access Analyzer auditing account can make calls against the SharePoint web services to remotely gather information around permissions, site hierarchy, content and more - - If the group does not exist already, then you need to create a new group at that level and + - If the group doesn't exist already, then you need to create a new group at that level and grant it Read access. Specifically, it is a group that exists within Central - Administration at the farm administrator level. This group only requires Read access and - is not giving farm admin access. Once the group is created, add the service account that - Access Analyzer will be leveraging to scan SharePoint. + Administration at the farm administrator level. This group requires only Read access, not + farm admin access. After the group is created, add the service account that + Access Analyzer uses to scan SharePoint. - Web Application permissions: @@ -95,7 +95,7 @@ following permissions are sufficient for successful agent-based scans: - SPDataAccess on the SharePoint Content database and all Configuration databases - - This permission should be applied on the desired Configuration database and all Content + - This permission should be applied on the Configuration database and all Content databases for the SharePoint version - This version-specific permission is required for Access Analyzer to execute read operations directly against the SharePoint databases, gather information from the @@ -112,14 +112,14 @@ following permissions are sufficient for successful agent-based scans: administrative access - This grants Access Analyzer rights to scan MySites -Additional permission models are explained for a less and least permission model. +The following sections explain the less privilege and least privilege permission models. ## SharePoint Agent-Based Less Privilege Permission Model If restricted permissions are desired by the organization, then the following permissions are needed for the service account to successfully run SharePoint Agent-based scans. -Prior to installation of the SharePoint Agent, the service account to be supplied during +Before installing the SharePoint Agent, the service account to be supplied during installation and later used to run the Access Auditing (SPAA) and Sensitive Data Discovery Auditing scans against the targeted SharePoint environment needs the following permissions: @@ -148,8 +148,8 @@ following permissions: `C:\Program Files\STEALTHbits\StealthAUDIT\SPAA` -The Access Analyzer SharePoint Agent utilizes Microsoft APIs. The Microsoft APIs require an account -with the following permissions in order to collect all of the data: +The Access Analyzer SharePoint Agent uses Microsoft APIs. The Microsoft APIs require an account +with the following permissions to collect all of the data: - WSS_CONTENT_APPLICATION_POOLS on the SharePoint Content databases - WSS_CONTENT_APPLICATION_POOLS on the SharePoint Configuration database @@ -164,7 +164,7 @@ If scans include Web Application scoping, this last permission requirement is al If a least privilege model is required by the organization, then the following permissions are needed for the service account to successfully run SharePoint Agent-based scans. -Prior to installation of the SharePoint Agent, the service account to be supplied during +Before installing the SharePoint Agent, the service account to be supplied during installation and later used to run the Access Auditing (SPAA) and Sensitive Data Discovery Auditing scans the targeted SharePoint environment needs the following permissions: @@ -209,8 +209,8 @@ following permissions: `C:\Program Files\STEALTHbits\StealthAUDIT\SPAA` -The Access Analyzer SharePoint Agent utilizes Microsoft APIs. The Microsoft APIs require an account -with the following permissions in order to collect all of the data: +The Access Analyzer SharePoint Agent uses Microsoft APIs. The Microsoft APIs require an account +with the following permissions to collect all of the data: - `'GRANT EXECUTE'` permissions on the following stored procedures in the SharePoint Configuration database: @@ -222,8 +222,8 @@ with the following permissions in order to collect all of the data: - `proc_ReturnWebFeatures` :::note - The above four stored procedures would already have the correct permissions if Web - Application scoping is desired. + These four stored procedures already have the correct permissions if Web Application + scoping is desired. ::: diff --git a/docs/accessanalyzer/12.0/requirements/sharepoint/scanoptions/agent-based-scans/agentports.md b/docs/accessanalyzer/12.0/requirements/sharepoint/scanoptions/agent-based-scans/agentports.md index 52eebd64c8..c51f6c96f3 100644 --- a/docs/accessanalyzer/12.0/requirements/sharepoint/scanoptions/agent-based-scans/agentports.md +++ b/docs/accessanalyzer/12.0/requirements/sharepoint/scanoptions/agent-based-scans/agentports.md @@ -6,9 +6,9 @@ sidebar_position: 20 # SharePoint Agent Ports -The following are the firewall settings are required when executing the Access Auditing (FSAA) -and/or Sensitive Data Discovery Auditing scans in Agent-based mode for communication between Access -Analyzer and the target host: +The following firewall settings are required for communication between Access Analyzer and the +target host when running Access Auditing (FSAA) and/or Sensitive Data Discovery Auditing scans in +Agent-based mode: | Port | Protocol | Source | Direction | Target | Purpose | | ------- | -------- | --------------------------------------- | --------- | --------------------------------------- | ---------------------------------------------------------------------- | diff --git a/docs/accessanalyzer/12.0/requirements/sharepoint/scanoptions/agent-less-scans/agentlesspermissions.md b/docs/accessanalyzer/12.0/requirements/sharepoint/scanoptions/agent-less-scans/agentlesspermissions.md index 33ab35d0e3..b7964d4210 100644 --- a/docs/accessanalyzer/12.0/requirements/sharepoint/scanoptions/agent-less-scans/agentlesspermissions.md +++ b/docs/accessanalyzer/12.0/requirements/sharepoint/scanoptions/agent-less-scans/agentlesspermissions.md @@ -9,7 +9,7 @@ sidebar_position: 10 When SharePoint agent-less scans are run, it means all of the data collection processing is conducted by the Access Analyzer Console server across the network. -The SharePoint agent-less scan architecture requires permissions to be configured on the specified +The SharePoint agent-less scan architecture requires you to configure permissions on the specified server: - SharePoint Application Server permissions: diff --git a/docs/accessanalyzer/12.0/requirements/sharepoint/scanoptions/scanoptions.md b/docs/accessanalyzer/12.0/requirements/sharepoint/scanoptions/scanoptions.md index c06e8758c5..6fef88a8a0 100644 --- a/docs/accessanalyzer/12.0/requirements/sharepoint/scanoptions/scanoptions.md +++ b/docs/accessanalyzer/12.0/requirements/sharepoint/scanoptions/scanoptions.md @@ -6,8 +6,8 @@ sidebar_position: 10 # SharePoint Scan Options -Required permissions on the targeted SharePoint environment are dependent upon not only the type of -environment targeted but also the type of data collection scan being executed. There are two types +Required permissions on the targeted SharePoint environment depend on the type of environment +targeted and the type of data collection scan running. There are two types of Access Auditing (SPAA) and/or Sensitive Data Discovery Auditing scans: agent-based and agent-less. The Activity Auditing (SPAC) scans run as agent-less scans from Access Analyzer, but they require the Netwrix Activity Monitor to have an activity agent deployed in the target @@ -17,7 +17,7 @@ environment. When Access Analyzer SharePoint scans are run in agent-based mode, the Access Analyzer SharePoint Agent must be installed on the SharePoint Application server which hosts the Central Administration -component prior to executing the scans. This is typically the first server stood up during the +component before executing the scans. This is typically the first server stood up during the SharePoint farm installation process in this mode. The data collection processing is conducted by the SharePoint Agent for the target environment. The final step in data collection is to transfer the data collected in the SQLite databases, or Tier 2 databases, on the Access Analyzer SharePoint diff --git a/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint.md b/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint.md index 16afd1c4be..d5001ffa25 100644 --- a/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint.md +++ b/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint.md @@ -10,18 +10,17 @@ The core components for Netwrix Access Analyzer (formerly Enterprise Auditor) ar Analyzer Console server, SQL Server, and Access Information Center. See the [Requirements](/docs/accessanalyzer/12.0/requirements/overview.md) topic for the core requirements. -The SharePoint solution can be configured to run without an agent or to use the Access Analyzer +You can configure the SharePoint solution to run without an agent or to use the Access Analyzer SharePoint Agent. See the [SharePoint Agent Installation](/docs/accessanalyzer/12.0/install/sharepointagent/overview.md) topic for additional information. -In addition to these, integration with either the Netwrix Activity Monitor is required for event -activity data to be scanned. See the +You must also integrate with the Netwrix Activity Monitor to scan event activity data. See the [Netwrix Activity Monitor Documentation](https://helpcenter.netwrix.com/category/activitymonitor) for installation requirements and information on collecting activity data. :::note -For Activity Auditing (SPAC) scans, the audit logs generated by SharePoint must be -retained for more days than the number of days between the Access Analyzer scans. +For Activity Auditing (SPAC) scans, retain the audit logs that SharePoint generates for more days +than the interval between Access Analyzer scans. ::: @@ -59,10 +58,9 @@ These are dependent upon the size of the target environment: | Disk Space | 460 GB | 280 GB | 160 GB | 80 GB | :::note -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the -minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host.For -example, if the job is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are -required (8x2=16). +If you run Sensitive Data Discovery (SDD) scans, increase the minimum amount of RAM. Each thread +requires a minimum of 2 additional GB of RAM per host. For example, if the job is configured to +scan 8 hosts at a time, then an extra 16 GB of RAM are required (8x2=16). ::: @@ -70,7 +68,7 @@ required (8x2=16). :::note The appropriate JDK (Java) version for Sensitive Data Discovery is installed on the -server. The JDK deployed is prepackaged and does not require any configuration; it has been +server. The JDK deployed is prepackaged and doesn't require any configuration; it has been preconfigured to work with Access Analyzer and should never be customized through Java. It will not conflict with other JDKs or Java Runtimes in the same environment. ::: diff --git a/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepoint.md b/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepoint.md index cee7bf548b..5e1d585aa2 100644 --- a/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepoint.md +++ b/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepoint.md @@ -10,7 +10,7 @@ Netwrix products audit and monitor Microsoft® SharePoint® environments. Access the SharePoint solution to execute Access Auditing (SPAA) and Sensitive Data Discovery Auditing scans against SharePoint on-premise and SharePoint Online. Through integration with Activity Monitor, Access Analyzer can also execute Activity Auditing (SPAC) scans against SharePoint -on-premise and SharePoint online environments. Additionally, Activity Monitor can be configured to +on-premise and SharePoint online environments. Additionally, you can configure Activity Monitor to provide activity data to various SIEM products. Ports and permissions vary based on the scan mode option selected as well as the target environment. diff --git a/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepoint/access.md b/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepoint/access.md index 224a1d8c56..93ef371434 100644 --- a/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepoint/access.md +++ b/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepoint/access.md @@ -30,14 +30,14 @@ The service account must be a member of the `Farm Read` group at the farm level. Access Analyzer to call the SharePoint web services to gather permissions, site hierarchy, and content information remotely. -Follow these steps to configure farm-level permissions on SharePoint 2013 through SharePoint 2019: +Configure farm-level permissions on SharePoint 2013 through SharePoint 2019: 1. In the SharePoint **Central Administration Center**, navigate to the **Security** section. 2. Select **Manage the farm administrators group** under **Users**. 3. If the `Farm Read` group exists, add the service account to that group. If the group has been deleted, create a new group: - Select **More** under the **Groups** section. - - Select **New Group** from the **New** drop-down menu. + - Select **New Group** from the **New** dropdown menu. - Ensure the group has the `Read – Can view pages and list items and download documents` permission. - Add the service account to the new group. @@ -50,7 +50,7 @@ The service account requires a custom policy role with `Site Collection Auditor` permissions at the web application level. This allows Access Analyzer to execute web service calls against **Central Administration**. -Follow these steps to configure web application-level permissions on SharePoint 2013 through +Configure web application-level permissions on SharePoint 2013 through SharePoint 2019: 1. In the **Central Administration Center**, navigate to the **Application Management** section. @@ -82,7 +82,7 @@ configuration database and all content databases. This allows Access Analyzer to operations directly against the SharePoint databases and gather information about web application and content database locations. -Follow these steps to configure database server permissions: +Configure database server permissions: 1. Open the SharePoint database server user configuration in SQL Server Management Studio. 2. Grant the service account the `SPDataAccess` database role membership on the following diff --git a/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepoint/activity.md b/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepoint/activity.md index e35c5d82bd..d622f4dcad 100644 --- a/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepoint/activity.md +++ b/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepoint/activity.md @@ -6,8 +6,8 @@ sidebar_position: 20 # SharePoint On-Premise Activity Auditing Configuration -SharePoint Event Auditing must be enabled for each site collection to be monitored by the Netwrix -Activity Monitor and/or audited by Netwrix Access Analyzer (formerly Enterprise Auditor). +Enable SharePoint Event Auditing for each site collection that the Netwrix Activity Monitor +monitors or that Netwrix Access Analyzer (formerly Enterprise Auditor) audits. ## User Requirements @@ -44,7 +44,7 @@ select the events to be audited. **Step 6 –** Click OK to save the changes. -SharePoint will create the audit logs to be monitored by the Netwrix Activity Monitor and/or audited -by Access Analyzer. See the Microsoft +SharePoint creates the audit logs that the Netwrix Activity Monitor monitors and/or that Access +Analyzer audits. See the Microsoft [Configure audit settings for a site collection (SharePoint 2013/2016/2019)](https://support.office.com/en-us/article/Configure-audit-settings-for-a-site-collection-a9920c97-38c0-44f2-8bcb-4cf1e2ae22d2) article for additional information. diff --git a/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepoint/overview.md b/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepoint/overview.md index 7bea1053d2..12f83b86c9 100644 --- a/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepoint/overview.md +++ b/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepoint/overview.md @@ -7,8 +7,8 @@ sidebar_position: 10 # SharePoint Target Requirements Netwrix Access Analyzer (formerly Enterprise Auditor) can execute Access Auditing (SPAA) and/or -Sensitive Data Discovery Auditing scans on SharePoint farms. The Netwrix Activity Monitor can be -configured to monitor activity on SharePoint farms and make the event data available for Access +Sensitive Data Discovery Auditing scans on SharePoint farms. You can configure the Netwrix Activity +Monitor to monitor activity on SharePoint farms and make the event data available for Access Analyzer Activity Auditing (SPAC) scans. ## Access & Sensitive Data Auditing Permissions @@ -38,7 +38,7 @@ Activity Agent must have the following permissions on the proxy server: - Membership in the local Administrators group - READ and WRITE access to the archive location for Archiving feature only -It is also necessary to enable the Remote Registry Service on the Activity Agent server. +Also enable the Remote Registry Service on the Activity Agent server. For integration between the Activity Monitor and Access Analyzer, the credential used by Access Analyzer to read the activity log files must have also have this permission. @@ -62,15 +62,15 @@ are required for communication between the Agent server and the Netwrix Activity | -------------------------------- | -------- | ----- | ------------------- | | Activity Monitor to Agent Server | TCP | 4498 | Agent Communication | -The Windows firewall rules need to be configured on the Windows server, which require certain -inbound rules be created if the scans are running in applet mode. These scans operate over a default -port range, which cannot be specified via an inbound rule. For more information, see the Microsoft +Configure the Windows firewall rules on the Windows server. If the scans run in applet mode, create +certain inbound rules. These scans operate over a default port range, which can't be specified via +an inbound rule. For more information, see the Microsoft [Connecting to WMI on a Remote Computer](https://msdn.microsoft.com/en-us/library/windows/desktop/aa389290(v=vs.85).aspx) article. Additional Firewall Rules for Integration between Access Analyzer and Activity Monitor -Firewall settings are dependent upon the type of environment being targeted. The following firewall +Firewall settings depend on the type of environment being targeted. The following firewall settings are required for communication between the agent server and the Access Analyzer Console: | Communication Direction | Protocol | Ports | Description | diff --git a/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepointonline/access.md b/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepointonline/access.md index 45b5188f6e..ddd27fd02c 100644 --- a/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepointonline/access.md +++ b/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepointonline/access.md @@ -19,7 +19,7 @@ Microsoft Entra ID. **Configuration Settings from the Registered Application** -The following settings are needed from your tenant once you have registered the application: +After you register the application, the following settings are needed from your tenant: - Client ID – This is the Application (client) ID for the registered application - Key – The comma delimited string containing the path to the certificate PFX file, certificate @@ -28,9 +28,10 @@ The following settings are needed from your tenant once you have registered the Configure Modern Authentication for SharePoint Online using SP_RegisterAzureAppAuth Instant Job -Registering a Microsoft Entra ID application and provisioning it to grant permissions to SharePoint -Online can be automated using the SP_RegisterAzureAppAuth job from the Access Analyzer Instant Job -Library. The SP_RegisterAzureAppAuth job uses the PowerShell Data Collector to automatically +You can automate registering a Microsoft Entra ID application and provisioning it to grant +permissions to SharePoint Online with the SP_RegisterAzureAppAuth job from the Access Analyzer +Instant Job Library. The SP_RegisterAzureAppAuth job uses the PowerShell Data Collector to +automatically configure modern authentication for SharePoint Online. It requires: - A Connection Profile containing the following two user credentials, both with an Account Type of @@ -103,7 +104,7 @@ against Entra ID while requesting the App Only access token. See the Microsoft [Granting access via Azure AD App-Only](https://learn.microsoft.com/en-us/sharepoint/dev/solution-guidance/security-apponly-azuread) article for additional information. -Follow the steps create the self-signed X.509 certificate. +Create the self-signed X.509 certificate: **Step 1 –** To generate a certificate, use the sample PowerShell command below: @@ -162,7 +163,7 @@ more secure before running this cmdlet. ## Register a Microsoft Entra ID Application -Follow the steps to register Access Analyzer with Microsoft Entra ID. +Register Access Analyzer with Microsoft Entra ID: :::note The steps below are for registering an app through the Microsoft Entra admin center. These @@ -187,11 +188,11 @@ registrations. **Step 5 –** Click **Register**. The Overview page for the newly registered app opens. Review the newly created registered -application. Now that the application has been registered, permissions need to be granted to it. +application. Now that you've registered the application, grant it permissions. ## Upload Self-Signed Certificate -Follow the steps to provision the upload your self-signed certificate. +Upload your self-signed certificate: :::note The steps below are for registering an app through the Microsoft Entra admin center. These @@ -219,7 +220,7 @@ The upload certificate public key .cer file is an application key credential. ## Grant Permissions to the Registered Application -Follow the steps to grant permissions to the registered application. +Grant permissions to the registered application: :::note The steps below are for registering an app through the Microsoft Entra admin center. These @@ -298,12 +299,12 @@ Select the following permissions: **Step 12 –** Click **Grant Admin Consent for [tenant]**. Then click **Yes** in the confirmation window. -Now that the permissions have been granted to it, the Connection Profile and host settings for -Access Analyzer need to be collected. +Now that you've granted the permissions, collect the Connection Profile and host settings for +Access Analyzer. ## Identify the Client ID -Follow the steps to find the registered application's Client ID. +Find the registered application's Client ID: :::note The steps below are for registering an app through the Microsoft Entra admin center. These diff --git a/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepointonline/activity.md b/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepointonline/activity.md index 520ea3d565..1a6eed6f33 100644 --- a/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepointonline/activity.md +++ b/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepointonline/activity.md @@ -6,8 +6,8 @@ sidebar_position: 20 # SharePoint Online Activity Auditing Configuration -In order to collect logs and monitor SharePoint Online activity using the Netwrix Activity Monitor, -it needs to be registered with Microsoft® Entra ID® (formerly Azure AD). +To collect logs and monitor SharePoint Online activity, register the Netwrix Activity Monitor with +Microsoft® Entra ID® (formerly Azure AD). :::note A user account with the Global Administrator role is required to register an app with @@ -26,15 +26,14 @@ additional information. **Configuration Settings from the Registered Application** -The following settings are needed from your tenant once you have registered the application: +After you register the application, the following settings are needed from your tenant: - Tenant ID – This is the Tenant ID for Microsoft Entra ID - Client ID – This is the Application (client) ID for the registered application - Client Secret – This is the Client Secret Value generated when a new secret is created :::warning - It is not possible to retrieve the value after saving the new key. It must be - copied first. + You can't retrieve the value after saving the new key, so copy it first. ::: @@ -55,7 +54,7 @@ The following settings are needed from your tenant once you have registered the ## Register a Microsoft Entra ID Application -Follow the steps to register Activity Monitor with Microsoft Entra ID. +Register Activity Monitor with Microsoft Entra ID: :::note The steps below are for registering an app through the Microsoft Entra admin center. These @@ -84,11 +83,11 @@ registrations. **Step 5 –** Click **Register**. The Overview page for the newly registered app opens. Review the newly created registered -application. Now that the application has been registered, permissions need to be granted to it. +application. Now that you've registered the application, grant it permissions. ## Grant Permissions to the Registered Application -Follow the steps to grant permissions to the registered application. +Grant permissions to the registered application: :::note The steps below are for registering an app through the Microsoft Entra admin center. These @@ -131,12 +130,11 @@ Microsoft APIs tab. Select the following permissions: **Step 9 –** Click **Grant Admin Consent for [tenant]**. Then click **Yes** in the confirmation window. -Now that the permissions have been granted to it, the settings required for Activity Monitor need to -be collected. +Now that you've granted the permissions, collect the settings required for Activity Monitor. ## Identify the Client ID -Follow the steps to find the registered application's Client ID. +Find the registered application's Client ID: :::note The steps below are for registering an app through the Microsoft Entra admin center. These @@ -174,7 +172,7 @@ application’s Client Secret Key. **Overview Page** -Follow the steps to find the tenant name where the registered application resides. +Find the tenant name where the registered application resides: :::note The steps below are for registering an app through the Microsoft Entra admin center. These @@ -194,8 +192,8 @@ application’s Client Secret Key. ## Generate the Client Secret Key -Follow the steps to find the registered application's Client Secret, create a new key, and save its -value when saving the new key. +Find the registered application's Client Secret, create a new key, and save its +value when saving the new key: :::note The steps below are for registering an app through the Microsoft Entra admin center. These @@ -205,7 +203,7 @@ documentation for additional information. :::warning -It is not possible to retrieve the value after saving the new key. It must be copied +It isn't possible to retrieve the value after saving the new key. It must be copied first. ::: @@ -225,15 +223,15 @@ list. :::note Setting the duration on the key to expire requires reconfiguration at the time of - expiration. It is best to configure it to expire in 1 or 2 years. + expiration. Configure it to expire in 1 or 2 years. ::: **Step 5 –** Click **Add** to generate the key. :::warning -If this page is left before the key is copied, then the key is not retrievable, and -this process will have to be repeated. +If you leave this page before copying the key, you can't retrieve it, and you'll have to repeat +this process. ::: @@ -246,15 +244,15 @@ This is needed for adding a SharePoint Online host in the Activity Monitor. ## Enable Auditing for SharePoint Online -Follow the steps to enable auditing for SharePoint Online so the Activity Monitor can receive -events. +Enable auditing for SharePoint Online so the Activity Monitor can receive +events: **Step 1 –** In the Microsoft Purview compliance portal at [https://purview.microsoft.com](https://purview.microsoft.com/), go to **Solutions** > **Audit**. Or, to go directly to the Audit page at [https://purview.microsoft.com/audit/auditsearch](https://purview.microsoft.com/audit/auditsearch). -**Step 2 –** If auditing is not turned on for your organization, a banner is displayed prompting you +**Step 2 –** If auditing isn't turned on for your organization, a banner is displayed prompting you start recording user and admin activity. **Step 3 –** Select the **Start recording** user and **admin activity** banner. diff --git a/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepointonline/overview.md b/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepointonline/overview.md index 2e5aa98f4a..6248b11c58 100644 --- a/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepointonline/overview.md +++ b/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepointonline/overview.md @@ -7,8 +7,8 @@ sidebar_position: 20 # SharePoint Online Target Requirements Netwrix Access Analyzer (formerly Enterprise Auditor) can execute Access Auditing (SPAA) and -Sensitive Data Discovery Auditing scans on SharePoint Online. The Netwrix Activity Monitor can be -configured to monitor activity on SharePoint Online and make the event data available for Access +Sensitive Data Discovery Auditing scans on SharePoint Online. You can configure the Netwrix Activity +Monitor to monitor activity on SharePoint Online and make the event data available for Access Analyzer Activity Auditing (SPAC) scans. ## Access & Sensitive Data Auditing Permissions @@ -47,7 +47,7 @@ server: - Membership in the local Administrators group - READ and WRITE access to the archive location for Archiving feature only -It is also necessary to enable the Remote Registry Service on the Activity Agent server. +Also enable the Remote Registry Service on the Activity Agent server. For integration between the Activity Monitor and Access Analyzer, the credential used by Access Analyzer to read the activity log files must have also have this permission. @@ -71,15 +71,15 @@ are required for communication between the Agent server and the Netwrix Activity | -------------------------------- | -------- | ----- | ------------------- | | Activity Monitor to Agent Server | TCP | 4498 | Agent Communication | -The Windows firewall rules need to be configured on the Windows server, which require certain -inbound rules be created if the scans are running in applet mode. These scans operate over a default -port range, which cannot be specified via an inbound rule. For more information, see the Microsoft +Configure the Windows firewall rules on the Windows server. If the scans run in applet mode, create +certain inbound rules. These scans operate over a default port range, which can't be specified via +an inbound rule. For more information, see the Microsoft [Connecting to WMI on a Remote Computer](https://msdn.microsoft.com/en-us/library/windows/desktop/aa389290(v=vs.85).aspx) article. Additional Firewall Rules for Integration between Access Analyzer and Activity Monitor -Firewall settings are dependent upon the type of environment being targeted. The following firewall +Firewall settings depend on the type of environment being targeted. The following firewall settings are required for communication between the agent server and the Access Analyzer Console: | Communication Direction | Protocol | Ports | Description | diff --git a/docs/accessanalyzer/12.0/requirements/unix/target.md b/docs/accessanalyzer/12.0/requirements/unix/target.md index 40db4d2a1c..ac4f7ac8da 100644 --- a/docs/accessanalyzer/12.0/requirements/unix/target.md +++ b/docs/accessanalyzer/12.0/requirements/unix/target.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Target Unix Requirements, Permissions, and Ports -The Access Analyzer for Unix Solution provides the ability to audit Unix servers. It scans: +The Access Analyzer for Unix Solution lets you audit Unix servers. It scans: - AIX® 4+ - Solaris™ 8+ @@ -33,7 +33,7 @@ This solution employs the following data collectors to scan the target environme - Root permissions in Unix/Linux -If the Root permission is unavailable, a least privileged model can be used. See the +If the Root permission is unavailable, you can use a least privileged model instead. See the [Least Privilege Model](#least-privilege-model) topic additional information. ## Ports @@ -53,7 +53,7 @@ The following firewall ports are needed: ## Least Privilege Model Access Analyzer for Unix collects information from Unix devices by running commands or executing -scripts on your Unix hosts (if configured properly our tool can SCP scripts to your hosts before +scripts on your Unix hosts (if configured properly, Access Analyzer can SCP scripts to your hosts before execution). Therefore, the domain or local user credentials entered in the Connection Profile within the Access Analyzer must be capable of running the necessary commands, executing the necessary scripts or, in some cases, have rights to SCP scripts to the host. @@ -62,7 +62,7 @@ scripts or, in some cases, have rights to SCP scripts to the host. Access Analyzer for Unix connects to your host in two ways: -- Plink – This mechanism is leveraged during our tools Host Inventory to test connectivity to a host +- Plink – This mechanism is used during Access Analyzer's Host Inventory to test connectivity to a host and to collect basic details about a host (Host Name, OS Type, etc.) - Implementation of the SSH2 protocol built into Access Analyzer – This is how the Unix Data Collector interacts with and pulls information from your environment @@ -81,15 +81,15 @@ Access Analyzer for Unix connects to your host in two ways: - SSH port opened in software and hardware firewalls. Default is 22. - - If you do not use Port 22, you can specify your SSH port in the Connection Profile + - If you don't use Port 22, you can specify your SSH port in the Connection Profile ### Commands for Non-Root Accounts -We recommend using the root account to run Access Analyzer against a Unix system. However, if that -is not acceptable all the commands we leverage in the solution set are below and can be used to -implement least privilege: +Netwrix recommends using the root account to run Access Analyzer against a Unix system. However, if +that isn't acceptable, the following commands used by the solution let you implement least +privilege: -All Perl scripts require the account to be able to execute the following commands: +All Perl scripts require the account to execute the following commands: ``` scp [script] to a target location: /tmp/[script] @@ -118,7 +118,7 @@ environment to run the following commands: - `cat /etc/security/user` (read access) - `cat /etc/shadow` - - Requires root or customization to job to utilize sudo without password prompt (:NOPASSWD) + - Requires root or customization to job to use sudo without password prompt (:NOPASSWD) - `egrep /etc/security/user` (read access) - `egrep /etc/login.defs` (read access) @@ -150,7 +150,7 @@ The 2.PrivilegedAccess > Sudoers > 0.Collection > UX_ParseSudoers Job requires p Unix environment to run the following commands: :::note -To parse sudoers we either need root or an account that has access to use sudo without +To parse sudoers, the account needs root access or access to use sudo without a password prompt (:NOPASSWD) ::: diff --git a/docs/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/configuration.md b/docs/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/configuration.md index ada5834ca4..f75d967eb7 100644 --- a/docs/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/configuration.md +++ b/docs/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/configuration.md @@ -11,7 +11,7 @@ edit, and remove sub-criteria information for User Criteria. ![Configuration Pane](/images/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/configurationpanesystemcriteria.webp) -The information in the configuration pane changes based on the criteria currently selected in the +The information in the configuration pane changes based on the criteria selected in the navigation pane. ![Options at the top of the configuration pane](/images/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/configurationpanetop.webp) @@ -19,7 +19,7 @@ navigation pane. The options at the top of the Configuration Pane are: :::note -Configuration settings for System Criteria cannot be modified. +Configuration settings for System Criteria can't be modified. ::: @@ -40,7 +40,7 @@ Configuration settings for System Criteria cannot be modified. - The risk score can be set to **Low**, **Medium**, or **High** - Click the **Risk Score** button to change the risk score for user-configured criteria -- Required matched criteria list – Lists the sub-criteria configured for the currently selected +- Required matched criteria list – Lists the sub-criteria configured for the selected top-level criteria in the navigation pane. The columns in the table are: - Name – Name of the sub-criteria @@ -54,7 +54,7 @@ Configuration settings for System Criteria cannot be modified. The options at the bottom of the configuration pane are: :::note -Configuration settings for System Criteria cannot be modified. +Configuration settings for System Criteria can't be modified. ::: @@ -67,7 +67,7 @@ Configuration settings for System Criteria cannot be modified. - [Summary Criteria](/docs/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/summary.md) - Remove – Remove sub-criteria from the Required matched sub-criteria list -- Edit – Edit the currently selected sub-criteria +- Edit – Edit the selected sub-criteria - Must match at least this many criteria – Adjust the slider to configure how many sub-criteria must be matched for the sensitive data criteria to be reported @@ -76,13 +76,13 @@ Configuration settings for System Criteria cannot be modified. required matched criteria list :::warning - The character distance feature does not account for summaries that are nested + The character distance feature doesn't account for summaries that are nested within other summaries. ::: - Matches should be within this proximity of characters – Match hits for this criteria should be - within this many characters of one another in order for there to be a match. Adjust the slider to + within this many characters of one another for there to be a match. Adjust the slider to set the default character distance required for match hits. - The minimum value is 0 @@ -90,15 +90,15 @@ Configuration settings for System Criteria cannot be modified. - Using this feature requires any combination of two or more Regular Expression (Pattern) and Keyword sub-criteria -- Include keywords as part of match hits – Select this option to enable the inclusion of keywords as - part of match hits. This option determines whether a match found based on a Keyword Criteria is +- Include keywords as part of match hits – Select this option to include keywords in match hits. + This option determines whether a match found based on a Keyword Criteria is reported as a match hit. When this option is selected, any matches found for a word in the Keyword - list is reported as match hit. If this option is not selected, then only matches found based on + list is reported as match hit. If this option isn't selected, then only matches found based on Pattern or child Summary Criteria are reported as a match hit. - Metadata for this criteria – Click the green plus (**+**) button to add a new metadata type for the criteria. Delete a metadata type by clicking the **X** button in the gray metadata tag. - - For a list of available out-of-the-box metadata tags, see the + - For a list of available predefined metadata tags, see the [Default Metadata Tag Values](/docs/accessanalyzer/12.0/sensitivedatadiscovery/metadatatags.md) topic for additional information - Cancel – Exit the Sensitive Data Criteria Editor without saving changes @@ -115,8 +115,8 @@ The options in the Criteria Tester are: - Use the following sample text – Enter sample text to test against current configured criteria in the **Use the following sample text** textbox - Use the following file – Click **Browse** to import a file as sample text to test against - currently configured criteria -- Test Data – Click **Test Data** to test the sample text against currently configured criteria. + configured criteria +- Test Data – Click **Test Data** to test the sample text against configured criteria. Match hits show in the **Test Results** section. - Test Results – Displays match hits for the sample text typed into the text box. The two tabs under Test Results are: diff --git a/docs/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/keyword.md b/docs/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/keyword.md index c285ad4d0e..16d36e7431 100644 --- a/docs/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/keyword.md +++ b/docs/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/keyword.md @@ -21,8 +21,8 @@ The options on the Keywords window are: - Match Type – Choose whether keyword matches for the Keyword criteria **Must match** or **Must not match** - Case Sensitive Keywords – If enabled, checks letter case when matching keywords -- Count only distinct occurrences – Select the checkbox to enable only distinct occurrences to be - counted during scan jobs +- Count only distinct occurrences – Select the checkbox to count only distinct occurrences during + scan jobs - Apply these keywords to these file components – Select which file components the keywords apply to: diff --git a/docs/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/overview.md b/docs/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/overview.md index 844188b33d..c30852d2c2 100644 --- a/docs/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/overview.md +++ b/docs/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/overview.md @@ -6,10 +6,10 @@ sidebar_position: 50 # Sensitive Data Criteria Editor -The Sensitive Data Criteria Editor is accessed from the Criteria Tab in the -**Settings** > **Sensitive Data** node. Use the Sensitive Data Criteria Editor to view pre-defined -criteria and to customize or create user-defined criteria. Sensitive Data Criteria can be configured -in individual data collectors that use Sensitive Data Discovery or can be configured to inherit +Access the Sensitive Data Criteria Editor from the Criteria tab in the +**Settings** > **Sensitive Data** node. Use it to view pre-defined +criteria and to customize or create user-defined criteria. You can configure Sensitive Data Criteria +in individual data collectors that use Sensitive Data Discovery, or configure it to inherit Sensitive Data Criteria settings from the **Settings** > **Sensitive Data** node. See the [Sensitive Data](/docs/accessanalyzer/12.0/admin/settings/sensitivedata/overview.md) topic for additional information. @@ -17,10 +17,9 @@ Sensitive Data Criteria settings from the **Settings** > **Sensitive Data** nod The Sensitive Data Criteria Editor contains two sections: -- Navigation pane – User-configured criteria can be added and removed in the navigation pane using - the Add or Remove options. See the [Navigation Pane](#navigation-pane) topic for additional - information. -- Configuration pane – Displays configured settings for the currently selected criteria in the +- Navigation pane – Add or remove user-configured criteria using the Add or Remove options in the + navigation pane. See the [Navigation Pane](#navigation-pane) topic for additional information. +- Configuration pane – Displays configured settings for the selected criteria in the navigation pane. See the [Configuration Pane](/docs/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/configuration.md) topic for additional information. ## Navigation Pane @@ -37,6 +36,6 @@ The options in the Navigation Pane are: - System Criteria – Lists all pre-configured criteria. For a list of pre-configured System Criteria, see the [Sensitive Data System Criteria](/docs/accessanalyzer/12.0/sensitivedatadiscovery/systemcriteria.md) topic for additional information. - - System Criteria cannot be modified or removed. To use existing System Criteria configurations - in a User Criteria, right-click on a System Criteria and select **Duplicate** from the + - System Criteria can't be modified or removed. To use existing System Criteria configurations + in a User Criteria, right-click a System Criteria and select **Duplicate** from the right-click menu. A configurable copy of the System Criteria appears under User Criteria. diff --git a/docs/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/regularexpression.md b/docs/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/regularexpression.md index 4b170eac9f..41c4ac31ae 100644 --- a/docs/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/regularexpression.md +++ b/docs/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/regularexpression.md @@ -7,8 +7,8 @@ sidebar_position: 20 # Regular Expression (Pattern) Criteria Regular Expression criteria are a set of pattern matching rules that provide a concise and flexible -means for matching strings of text. This criteria type can be used to verify a series of numbers as -potentially valid, for example credit card numbers. +means for matching strings of text. Use this criteria type to verify a series of numbers as +potentially valid, for example, credit card numbers. ![Regular Expression window](/images/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/criteriatype/regularexpression.webp) @@ -18,7 +18,7 @@ The options on the Regular Expression window are: - Expression – Enter the Regular Expression in the Expression text box - Case Sensitive Expression – Select the checkbox for case sensitive Regular Expression pattern matching -- Validation – Select a validation method from the Validation drop-down. The default value is **No +- Validation – Select a validation method from the Validation dropdown. The default value is **No validation required**. :::note @@ -34,9 +34,9 @@ The options on the Regular Expression window are: - Match Type – Choose whether pattern matches for the Regular Expression criteria **Must match** or **Must not match** - - Must match – The Regular Expression must be matched for there to be a match - - Must not match – If the Regular Expression is matched and is designated **Must not match**, - then the potential match is invalidated + - Must match – The Regular Expression must match for the criteria to register a match + - Must not match – If the Regular Expression matches and is designated **Must not match**, + the potential match is invalidated - Apply this expression to these file components – Select which file components the expression applies to: diff --git a/docs/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/summary.md b/docs/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/summary.md index 66e9ef6a23..f2bf2d6d08 100644 --- a/docs/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/summary.md +++ b/docs/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/summary.md @@ -6,8 +6,7 @@ sidebar_position: 40 # Summary Criteria -Summary criteria are designed as a way of combining Regular Expression (Pattern) criteria and -Keyword criteria. +Summary criteria combine Regular Expression (Pattern) criteria and Keyword criteria. ![Edit new Summary criteria](/images/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/criteriatype/newsummarycriteria.webp) @@ -22,7 +21,7 @@ The options on the Summary criteria configuration page are: - Test Criteria – Opens the Criteria Tester window to test current Summary criteria configurations. See the [Criteria Tester Window](/docs/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/configuration.md#criteria-tester-window) topic for additional information. -- Required matched criteria – Lists sub-criteria configured for currently selected criteria in the +- Required matched criteria – Lists sub-criteria configured for selected criteria in the navigation pane. The columns in the table are: - Name – Name of the sub-criteria @@ -34,7 +33,7 @@ The options on the Summary criteria configuration page are: - Add – Add a sub-criteria to the required matched criteria list. The three types of sub-criteria that can be added are **Keyword**, **Pattern**, and **Summary**. - Remove – Remove the selected sub-criteria from the Required matched criteria list -- Edit – Edit the currently selected sub-criteria +- Edit – Edit the selected sub-criteria - Match Type – Choose whether match hits for the Summary criteria **Must match** or **Must not match** - Must match at least this many criteria – Adjust the slider to configure how many sub-criteria must @@ -45,7 +44,7 @@ The options on the Summary criteria configuration page are: Required matched criteria list :::warning -The character distance feature does not account for summaries that are nested within +The character distance feature doesn't account for summaries that are nested within other summaries. ::: @@ -58,7 +57,6 @@ other summaries. - Using this feature requires any combination of two or more Regular Expression (Pattern) and Keyword sub-criteria -- Include keywords as part of match hits – Select this checkbox to enable the inclusion of keywords - as part of match hits +- Include keywords as part of match hits – Select this checkbox to include keywords in match hits - Cancel – Exit the Sensitive Data Criteria Editor without saving changes -- Save – Save changes made to the currently selected criteria +- Save – Save changes made to the selected criteria diff --git a/docs/accessanalyzer/12.0/sensitivedatadiscovery/metadatatags.md b/docs/accessanalyzer/12.0/sensitivedatadiscovery/metadatatags.md index 0800f579fc..722dc63c10 100644 --- a/docs/accessanalyzer/12.0/sensitivedatadiscovery/metadatatags.md +++ b/docs/accessanalyzer/12.0/sensitivedatadiscovery/metadatatags.md @@ -6,7 +6,7 @@ sidebar_position: 40 # Default Metadata Tag Values -Sensitive Data Criteria can be tagged with one or more metadata tags to describe the criteria. The +You can tag Sensitive Data Criteria with one or more metadata tags to describe the criteria. The following is a list of default metadata tag values: | Tag Name | Value Description | diff --git a/docs/accessanalyzer/12.0/sensitivedatadiscovery/overview.md b/docs/accessanalyzer/12.0/sensitivedatadiscovery/overview.md index 2f65c823ad..6467c663b6 100644 --- a/docs/accessanalyzer/12.0/sensitivedatadiscovery/overview.md +++ b/docs/accessanalyzer/12.0/sensitivedatadiscovery/overview.md @@ -13,11 +13,12 @@ criteria or create new criteria. :::note Sensitive Data Discovery requires a special license. If your license includes Sensitive Data Discovery, then the necessary components for Sensitive Data Discovery are installed during the -Access Analyzer, FSAA Proxy, and SPAA Agent installations. +Access Analyzer, File System Access Auditing (FSAA) Proxy, and SharePoint Access Auditing (SPAA) +Agent installations. ::: -Sensitive Data Discovery can be used with any of the following Access Analyzer solutions: +You can use Sensitive Data Discovery with any of the following Access Analyzer solutions: - AWS Solution - Dropbox Solution @@ -50,7 +51,7 @@ Data Discovery. :::note The appropriate JDK (Java) version for Sensitive Data Discovery is installed on the -server. The JDK deployed is prepackaged and does not require any configuration; it has been +server. The JDK deployed is prepackaged and doesn't require any configuration; it has been preconfigured to work with Access Analyzer and should never be customized through Java. It will not conflict with other JDKs or Java Runtimes in the same environment. diff --git a/docs/accessanalyzer/12.0/sensitivedatadiscovery/supportedformats.md b/docs/accessanalyzer/12.0/sensitivedatadiscovery/supportedformats.md index 87fdfb97ae..91b3a3fddd 100644 --- a/docs/accessanalyzer/12.0/sensitivedatadiscovery/supportedformats.md +++ b/docs/accessanalyzer/12.0/sensitivedatadiscovery/supportedformats.md @@ -7,7 +7,7 @@ sidebar_position: 10 # Supported Formats for Scanning & Metadata This topic provides a comprehensive listing of all formats supported by Sensitive Data Discovery. -The list is divided into three major categories: +The list has three major categories: - [Scan-able Formats](#scan-able-formats) - [Metadata Only Formats](#metadata-only-formats) @@ -101,10 +101,10 @@ attachment’s file type is a scan-able format, then it can extract text from th | Tagged Image File Format | .TIF, .TIFF | :::note -The **FileSystem** > **0.Collection** > **1-SEEK System Scans** job can perform Optical -Character Recognition (OCR) scans for Raster image files by enabling the option on the SDD Audit -Settings page in the File System Access Auditor Data Collector Wizard. This is an option for the -Sensitive Data Scan category. See the +You can enable Optical Character Recognition (OCR) scans for raster image files on the SDD Audit +Settings page in the File System Access Auditor Data Collector Wizard. This option belongs to the +Sensitive Data Scan category. The **FileSystem** > **0.Collection** > **1-SEEK System Scans** job +then performs the OCR scans. See the [1-SEEK System Scans Job](/docs/accessanalyzer/12.0/solutions/filesystem/collection/1-seek_system_scans.md) topic for additional information. ::: @@ -165,15 +165,14 @@ multimedia. The following file formats are supported as metadata only formats. ## Scans Against Files with no Extensions -Files with no extensions can be scanned by modifying the XML file for each job where this type of -scan is desired. Add the following line to the `PerScanExtraScanOptions` section of a job's XML -script: +To scan files with no extensions, modify the XML file for each job that requires this type of scan. +Add the following line to the `PerScanExtraScanOptions` section of a job's XML script: ``` true ``` -This line must be added to a specific location within the XML script. See below: +Add this line to a specific location within the XML script, as shown in the following example: ``` @@ -192,5 +191,5 @@ This line must be added to a specific location within the XML script. See below: ``` -Once this line has been added to the job's XML script and the XML file is saved, files with no +After you add this line to the job's XML script and save the XML file, files with no extensions are included in scans for the job. diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/ad_activitycollection.md b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/ad_activitycollection.md index aeb28170aa..2235b8c6c0 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/ad_activitycollection.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/ad_activitycollection.md @@ -12,18 +12,18 @@ days default). ![AD_ActivityCollection Job in the Jobs Tree](/images/accessanalyzer/12.0/solutions/activedirectory/activity/jobstree_1.webp) -There are two ways AD Activity data can be retrieved by Access Analyzer: +Access Analyzer can retrieve AD Activity data in two ways: - Network share containing the archive logs - API Server connected to the archive logs This is configured in the query. See the -[Queries for the AD_ActivityCollection Job](#queries-for-the-ad_activitycollection-job) topic for +[Queries for the AD_ActivityCollection Job](#queries-for-the-adactivitycollection-job) topic for additional information. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/12.0/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -32,13 +32,12 @@ instructions on how to edit parameters on a job overview page. The AD_ActivityCollection page has the following configurable parameters: -- Enable to import AD events into the AIC +- Enable to import AD events into the Netwrix Access Information Center (AIC) - Enable to import authentication events into the AIC :::note The import of AD events and authentication events is disabled by default. You must - enable these parameters for the activity data to be imported into the Netwrix Access Information - Center. See the + enable these parameters for the activity data to be imported into the AIC. See the [(Optional) Configure Import of AD Activity into Netwrix Access Information Center](/docs/accessanalyzer/12.0/requirements/activedirectory/target/activity/activity.md#optional-configure-import-of-ad-activity-into-netwrix-access-information-center) topic for instructions. ::: @@ -48,7 +47,7 @@ The AD_ActivityCollection page has the following configurable parameters: - Number of days to retain activity data in the AIC See the -[Customize Analysis Parameters for the AD_ActivityCollection Job](#customize-analysis-parameters-for-the-ad_activitycollection-job) +[Customize Analysis Parameters for the AD_ActivityCollection Job](#customize-analysis-parameters-for-the-adactivitycollection-job) topic for additional information. ## Queries for the AD_ActivityCollection Job @@ -70,9 +69,9 @@ The AD_ActivityCollection Job uses the ADActivity Data Collector for the followi ### Configure the Query to Import from the Activity Monitor -The AD_ActivityCollection Job requires configuration to collect data. Follow the steps to modify the -query configuration when Netwrix Activity Monitor is configured to host domain activity logs on an -API server. +The AD_ActivityCollection Job requires configuration to collect data. Complete the following steps to +modify the query configuration when Netwrix Activity Monitor is configured to host domain activity +logs on an API server. :::note Ensure the Activity Monitor API Server and the required Connection Profile are @@ -144,9 +143,9 @@ logs. ### Configure the Query to Import from a Share -The AD_ActivityCollection Job requires configuration to collect data. Follow the steps to modify the -query configuration when Netwrix Activity Monitor is configured to store activity logs on a network -share. +The AD_ActivityCollection Job requires configuration to collect data. Complete the following steps to +modify the query configuration when Netwrix Activity Monitor is configured to store activity logs on +a network share. :::note Ensure the Activity Monitor domain output and the required Connection Profile are @@ -205,7 +204,7 @@ Navigate to the **Jobs** > **Active Directory** > **6.Activity** > **0.Collecti **AD_ActivityCollection** Job. Select the **Configure** > **Analysis** node. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -229,8 +228,8 @@ The following analysis tasks are selected by default: ### Customize Analysis Parameters for the AD_ActivityCollection Job -The customizable parameters for this job allow you to configure importing of AD activity data into -the Netwrix Access Information Center. +Use these customizable parameters to configure how the job imports AD activity data into the Netwrix +Access Information Center. | Analysis Task | Customizable Parameter Name | Default Value | Value Indicates | | ----------------------------------------------- | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- | diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/ad_ldapqueries.md b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/ad_ldapqueries.md index 76522d757c..f862997f42 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/ad_ldapqueries.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/ad_ldapqueries.md @@ -7,8 +7,8 @@ sidebar_position: 50 # LDAP > AD_LDAPQueries Job The **LDAP** > **AD_LDAPQueries** Job analyzes LDAP traffic to determine trends such as most -expensive queries, most active servers and users, successful/failed and signing status. This data -can be used to troubleshoot performance issues, load balancing, and poorly configured services. +expensive queries, most active servers and users, successful/failed and signing status. Use this data +to troubleshoot performance issues, load balancing, and poorly configured services. ![AD_LDAPQueries Job in the Jobs Tree](/images/accessanalyzer/12.0/solutions/activedirectory/activity/ldapjobstree.webp) @@ -23,7 +23,7 @@ Navigate to the **Active Directory** > **6.Activity** > **LDAP** > **AD_LDAPQuer **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Except for the **Largest Queries** task, do not modify or deselect the remaining +Except for the **Largest Queries** task, don't modify or deselect the remaining selected analysis tasks. The remaining analysis tasks are preconfigured for this job. ::: @@ -38,7 +38,7 @@ The following non-configurable analysis tasks are selected by default: - User Summary – Creates the SA_AD_LDAPQueries_UserSummary table accessible under the job’s Results node -The following configurable analysis task can be optionally enabled: +The following analysis task is optional: - Largest Queries – Creates the SA_AD_LDAPQueries_ExpensiveQueries table accessible under the job’s Results node @@ -54,10 +54,10 @@ pre-configured reports: ### Configure the Largest Queries Analysis Task -Customizable parameters enable you to set the values used to control the minimum objects returned +Use the customizable parameters to set the values that control the minimum objects returned and the days of traffic to analyze during this job’s analysis. The parameters can be customized and -are listed in a section at the bottom of the SQL Script Editor. Follow the steps to customize an -analysis task’s parameters. +are listed in a section at the bottom of the SQL Script Editor. Complete the following steps to +customize an analysis task’s parameters. **Step 1 –** Navigate to the **Active Directory** > **6.Activity** > **LDAP** > **AD_LDAPQueries** > **Configure** node and select **Analysis**. @@ -68,14 +68,14 @@ analysis task’s parameters. **Analysis Configuration**. The SQL Script Editor opens. :::warning -Do not change any parameters where the Value states `Created during execution`. +Don't change any parameters where the Value states `Created during execution`. ::: ![Largest Queries analysis task in the SQL Script Editor](/images/accessanalyzer/12.0/solutions/activedirectory/activity/ldapsqlscripteditor.webp) **Step 3 –** In the parameters section at the bottom of the editor, find the Value column. There are -two integer variables that can be modified. Double-click on the current **value** and change as +two integer variables that can be modified. Double-click the current **value** and change as desired: - @objects_returned – Controls the minimum number of objects returned for the queries to be diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/ad_lockouts.md b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/ad_lockouts.md index fc5ec314f1..9913e92dff 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/ad_lockouts.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/ad_lockouts.md @@ -23,7 +23,7 @@ Navigate to the **Active Directory** > **6.Activity** > **Lockouts** > **AD_Lock **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/changes/ad_computermodifications.md b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/changes/ad_computermodifications.md index 1467c5c4b6..b4ccadafc6 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/changes/ad_computermodifications.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/changes/ad_computermodifications.md @@ -14,7 +14,7 @@ Navigate to the **Active Directory** > **6.Activity** > **Changes** > **AD_Compu **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/changes/ad_groupmodifications.md b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/changes/ad_groupmodifications.md index db642fbc08..385e7acf06 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/changes/ad_groupmodifications.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/changes/ad_groupmodifications.md @@ -7,7 +7,7 @@ sidebar_position: 20 # AD_GroupModifications Job The AD_GroupModifications Job provides a report of all changes to group objects. A separate report -is provided to highlight group membership changes. The list of top perpetrators can be used to +is provided to highlight group membership changes. Use the list of top perpetrators to identify out of band changes. ## Analysis Tasks for the AD_GroupModifications Job @@ -16,7 +16,7 @@ Navigate to the **Jobs** > **Active Directory** > **6.Activity** > **Changes** > **AD_GroupModifications** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/changes/ad_usermodifications.md b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/changes/ad_usermodifications.md index 195a6efff2..eefbd230ac 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/changes/ad_usermodifications.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/changes/ad_usermodifications.md @@ -14,7 +14,7 @@ Navigate to the **Jobs** > **Active Directory** > **6.Activity** > **Changes** > **AD_UserModifications** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/changes/overview.md b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/changes/overview.md index d786267148..490fb0e0e0 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/changes/overview.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/changes/overview.md @@ -6,7 +6,7 @@ sidebar_position: 30 # Changes Job Group -The Changes Job Group provides an audit trail for changes made to Computer, Group and User objects +The Changes Job Group provides an audit trail for changes made to Computer, Group, and User objects within the environment. ![Changes Job Group in the Jobs Tree](/images/accessanalyzer/12.0/solutions/activedirectory/activity/changes/jobstree.webp) diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/groupusage/ad_accesschanges.md b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/groupusage/ad_accesschanges.md index 76761597ea..ab197a03e7 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/groupusage/ad_accesschanges.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/groupusage/ad_accesschanges.md @@ -6,9 +6,9 @@ sidebar_position: 10 # AD_AccessChanges Job -The AD_AccessChanges Job highlights the type and number of resources across the environment where -access has been affected. Groups which have historically been the cause of most access changes are -highlighted, to show potential issues in access sprawl and provisioning. +The AD_AccessChanges Job highlights the type and number of resources in the environment affected by +access changes. It also highlights groups that have historically caused the most access changes, +revealing potential issues in access sprawl and provisioning. ## Analysis Tasks for the AD_AccessChanges Job @@ -16,7 +16,7 @@ Navigate to the **Jobs** > **Active Directory** > **6.Activity** > **Group Usage **AD_AccessChanges** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/groupusage/ad_grouphosts.md b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/groupusage/ad_grouphosts.md index 45c8b8d3be..f26051e95f 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/groupusage/ad_grouphosts.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/groupusage/ad_grouphosts.md @@ -14,7 +14,7 @@ Navigate to the **Jobs** > **Active Directory** > **6.Activity** > **GroupUsage* **AD_GroupHosts** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -35,4 +35,4 @@ following pre-configured reports: | Report | Description | Default Tags | Report Elements | | ---------------- | ------------------------------------------------------------------- | ---------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Group Host Usage | Understand what groups are utilizing what hosts in the environment. | CCPA GDPR SOX HIPPA PCI-DSS GLBA ITAR FERPA FISMA ISO27001 | This report is comprised of three elements:
  • Table – Displays security groups by target hosts
  • Table – Displays hosts by associated groups
  • Table – Displays authentication details
| +| Group Host Usage | Understand what groups are using what hosts in the environment. | CCPA GDPR SOX HIPPA PCI-DSS GLBA ITAR FERPA FISMA ISO27001 | This report is comprised of three elements:
  • Table – Displays security groups by target hosts
  • Table – Displays hosts by associated groups
  • Table – Displays authentication details
| diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/groupusage/ad_groupmemberactivity.md b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/groupusage/ad_groupmemberactivity.md index 6e8d47938c..c794684ab9 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/groupusage/ad_groupmemberactivity.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/groupusage/ad_groupmemberactivity.md @@ -32,9 +32,10 @@ follow pre-configured report: ### Configure the Group Member Activity Analysis Task -Customizable parameters enable you to set the values used to include the SIDs for admin groups +Use the customizable parameters to set the values that include the SIDs for admin groups during this job’s analysis. The parameters can be customized and are listed in a section at the -bottom of the SQL Script Editor. Follow the steps to customize an analysis task’s parameters. +bottom of the SQL Script Editor. Complete the following steps to customize an analysis task’s +parameters. **Step 1 –** Navigate to the **Active Directory** > **6.Activity** > **Group Usage** > **AD_GroupMemberActivity** > **Configure** node and select **Analysis**. @@ -42,10 +43,10 @@ bottom of the SQL Script Editor. Follow the steps to customize an analysis task ![Group Member Activity analysis task configuration](/images/accessanalyzer/12.0/solutions/activedirectory/activity/groupusage/groupmemberactivityanalysisconfiguration.webp) **Step 2 –** In the Analysis Selection view, select the Group Member Activity analysis task and -click on **Analysis Configuration**. The SQL Script Editor opens. +click **Analysis Configuration**. The SQL Script Editor opens. :::warning -Do not change any parameters where the Value states `Created during execution`. +Don't change any parameters where the Value states `Created during execution`. ::: @@ -54,8 +55,8 @@ Do not change any parameters where the Value states `Created during execution`. **Step 3 –** In the parameters section at the bottom of the editor, find the Value column. Select the cell for the temporary table called #admingroups, and click **Edit Table** to modify the value. -- The new value should include SIDs for admin groups to be considered administrative groups beyond - the default admin groups. +- The new value should include the SIDs of any additional groups you want the job to treat as + administrative groups, beyond the default admin groups. **Step 4 –** Click **Save and Close** to finalize the customization and close the SQL Script Editor window. diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/ad_authenticationprotocol.md b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/ad_authenticationprotocol.md index 24d770c2bd..1814518ebc 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/ad_authenticationprotocol.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/ad_authenticationprotocol.md @@ -7,7 +7,7 @@ sidebar_position: 10 # AD_AuthenticationProtocol Job The AD_Authentication Job shows what protocols are being used to authenticate across the environment -and will help to identify what services and computers may be affected when disabling NTLM. +and will help to identify what services and computers may be affected if you disable NTLM. ## Analysis Tasks for the AD_AuthenticationProtocol Job @@ -16,7 +16,7 @@ Navigate to the **Active Directory** > **6.Activity** > **Operations** > tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/ad_domaincontrollertraffic.md b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/ad_domaincontrollertraffic.md index 8efb6c4e4a..00a5bbfeb3 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/ad_domaincontrollertraffic.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/ad_domaincontrollertraffic.md @@ -7,9 +7,9 @@ sidebar_position: 20 # AD_DomainControllerTraffic Job The AD_DomainControllerTraffic Job provides a summary of the amount of traffic for Changes, -Authentication, Replication, and LDAP Queries for each domain controller which can be used to -identify issues with load balancing. If the AD_DCSummary job has been run, the roles for each domain -controller will be provided. +Authentication, Replication, and LDAP Queries for each domain controller. Use this summary to +identify issues with load balancing. If you've run the AD_DCSummary job, the report includes the roles for each domain +controller. ## Analysis Tasks for the AD_DomainControllerTraffic Job @@ -18,7 +18,7 @@ Navigate to the **Active Directory** > **6.Activity** > **Operations** > tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/ad_hardcodeddcs.md b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/ad_hardcodeddcs.md index cc6cc87b1a..cf0a356aa9 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/ad_hardcodeddcs.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/ad_hardcodeddcs.md @@ -14,7 +14,7 @@ Navigate to the **Active Directory** > **6.Activity** > **Operations** > **AD_Ha **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/ad_loadbalancing.md b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/ad_loadbalancing.md index 5a2a39386a..9737c1db75 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/ad_loadbalancing.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/ad_loadbalancing.md @@ -7,9 +7,9 @@ sidebar_position: 40 # AD_LoadBalancing Job The AD_LoadBalancing Job analyzes each domain controller's traffic to show what percent of all LDAP, -Replication, Authentication and Changes are being handled by that particular machine. This helps to -highlight domain controllers which are over utilized relative to others within the domain, or unused -domain controllers which may be decommissioned. +Replication, Authentication, and Changes traffic that particular machine handles. This helps you +identify domain controllers that are overused relative to others in the domain, or unused domain +controllers that you can decommission. ## Analysis Task for the AD_LoadBalancing Job @@ -17,7 +17,7 @@ Navigate to the **Active Directory** > **6.Activity** > **Operations** > **AD_Lo **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/ad_machineowners.md b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/ad_machineowners.md index 12bd0a2662..47067a92b8 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/ad_machineowners.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/ad_machineowners.md @@ -14,7 +14,7 @@ Navigate to the **Active Directory** > **6.Activity** > **Operations** > **AD_Ma **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/overview.md b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/overview.md index 18b3fd9707..0b8a674ffd 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/overview.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/overview.md @@ -21,15 +21,15 @@ Schedule these jobs to run with the 0.Collection job group. - [AD_AuthenticationProtocol Job](/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/ad_authenticationprotocol.md) – Shows what protocols are being used to authenticate across the environment and will help to identify what services and computers - may be affected when disabling NTLM + may be affected if you disable NTLM - [AD_DomainControllerTraffic Job](/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/ad_domaincontrollertraffic.md) – Provides a summary of the amount - of traffic for Changes, Authentication, Replication, and LDAP Queries for each domain controller - which can be used to identify issues with load balancing. If the AD_DCSummary job has been run, - the roles for each DC will be provided. + of traffic for Changes, Authentication, Replication, and LDAP Queries for each domain controller. + Use this summary to identify issues with load balancing. If you've run the AD_DCSummary job, + the report includes the roles for each DC. - [AD_HardcodedDCs Job](/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/ad_hardcodeddcs.md) – Highlight machines that have communicated with only one DC - [AD_LoadBalancing Job](/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/ad_loadbalancing.md) – Analyzes each domain controller's traffic to show - what percent of all LDAP, Replication, Authentication and Changes are being handled by that - particular machine. This helps to highlight domain controllers which are over utilized relative to - others within the domain, or unused domain controllers which may be decommissioned. + what percent of all LDAP, Replication, Authentication, and Changes traffic that particular machine + handles. This helps you identify domain controllers that are overused relative to others in the + domain, or unused domain controllers that you can decommission. - [AD_MachineOwners Job](/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/ad_machineowners.md) – Helps to identify the owner of a particular host diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/overview.md b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/overview.md index b5b0a3dcbc..ecf0881006 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/overview.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/overview.md @@ -32,11 +32,11 @@ The 6.Activity Job Group is comprised of the following jobs: access across the entire environment, the actions taken by the members of a group, and identifies where groups may be used for authorization in applications - [LDAP > AD_LDAPQueries Job](/docs/accessanalyzer/12.0/solutions/activedirectory/activity/ad_ldapqueries.md) – Analyzes LDAP traffic to determine trends such as - most expensive queries, most active servers and users, successful/failed and signing status. This - data can be used to troubleshoot performance issues, load balancing, and poorly configured + most expensive queries, most active servers and users, successful/failed and signing status. Use + this data to troubleshoot performance issues, load balancing, and poorly configured services. - [Lockouts > AD_Lockouts Job](/docs/accessanalyzer/12.0/solutions/activedirectory/activity/ad_lockouts.md)– Provides a listing of all account lockouts with - relevant details which can be used to aid troubleshooting + relevant details to aid troubleshooting - [Operations Job Group](/docs/accessanalyzer/12.0/solutions/activedirectory/activity/operations/overview.md) – Reports on Active Directory activity events related to operational activity. This group can help report on probable machine owners based on authentications, domain controller traffic and activity, and authentication protocols being used diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/privilegedaccounts/ad_adminaccounts.md b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/privilegedaccounts/ad_adminaccounts.md index e96c4b2d55..b52a5c5693 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/privilegedaccounts/ad_adminaccounts.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/privilegedaccounts/ad_adminaccounts.md @@ -14,7 +14,7 @@ Navigate to the **Jobs** > **Active Directory** > **6.Activity** > **Privileged **AD_AdminAccounts** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -41,9 +41,10 @@ follow pre-configured reports: ### Configure the Summarize Administrative Account Activity Analysis Task -Customizable parameters enable you to set the values used to include the NT Account name for admin +Use the customizable parameters to set the values that include the NT Account name for admin groups during this job’s analysis. The parameters can be customized and are listed in a section at -the bottom of the SQL Script Editor. Follow the steps to customize an analysis task’s parameters. +the bottom of the SQL Script Editor. Complete the following steps to customize an analysis task’s +parameters. **Step 1 –** Navigate to the **Active Directory** > **6.Activity** > **Privileged Accounts** > **AD_AdminAccounts** > **Configure** node and select **Analysis**. @@ -54,7 +55,7 @@ the bottom of the SQL Script Editor. Follow the steps to customize an analysis t Activity** analysis task and click **Analysis Configuration**. The SQL Script Editor opens. :::warning -Do not change any parameters where the Value states `Created during execution`. +Don't change any parameters where the Value states `Created during execution`. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/privilegedaccounts/ad_serviceaccountauth.md b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/privilegedaccounts/ad_serviceaccountauth.md index 100a6cdd36..6c0f033b51 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/privilegedaccounts/ad_serviceaccountauth.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/privilegedaccounts/ad_serviceaccountauth.md @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **Active Directory** > **6.Activity** > **Operations* **AD_ServiceAccountAuth** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/privilegedaccounts/overview.md b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/privilegedaccounts/overview.md index b13e8cdf27..d76b81d22d 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/privilegedaccounts/overview.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/privilegedaccounts/overview.md @@ -19,6 +19,6 @@ Schedule these jobs to run with the 0.Collection job group. - [AD_AdminAccounts Job](/docs/accessanalyzer/12.0/solutions/activedirectory/activity/privilegedaccounts/ad_adminaccounts.md) – Shows all actions taken by domain administrators - within the environment being compromised + within the environment - [AD_ServiceAccountAuth Job](/docs/accessanalyzer/12.0/solutions/activedirectory/activity/privilegedaccounts/ad_serviceaccountauth.md) – Shows the last time a service account, identified by the presence of a servicePrincipalName, was active within the environment diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/recommended.md b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/recommended.md index 0d7ead0f56..fdea2904c7 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/recommended.md @@ -6,27 +6,27 @@ sidebar_position: 10 # Recommended Configurations for the 6.Activity Job Group -The **Active Directory** > **6.Activity** Job Group has been configured by default to run with the -out-of-the-box settings. It can be run directly or scheduled. +By default, the **Active Directory** > **6.Activity** Job Group runs with the default settings. You +can run it directly or schedule it. **Dependencies** - Successfully execute the **.Active Directory Inventory** Job Group - Netwrix Activity Monitor 4.1+ is archiving AD Activity Logs -- Successfully execute the **Active Directory** > **5.Domains Job Group** prior to running the +- Successfully execute the **Active Directory** > **5.Domains Job Group** before running the Operations Job Group - (Optional) Successfully execute the **Active Directory Permissions Analyzer** > **0.Collection** Job Group - (Optional) Successfully execute the **FileSystem** > **0.Collection** Job Group -**Targeted Host(s)** +**Targeted Hosts** Netwrix Activity Monitor API Server or the host with the network share housing archived log files. **Connection Profile** -Connection Profiles must be set directly on the -[0.Collection > AD_ActivityCollection Job](/docs/accessanalyzer/12.0/solutions/activedirectory/activity/ad_activitycollection.md) in order to connect to either +Set Connection Profiles directly on the +[0.Collection > AD_ActivityCollection Job](/docs/accessanalyzer/12.0/solutions/activedirectory/activity/ad_activitycollection.md) to connect to either the SAM API Server or the host with the network share housing the archived log files. **Access Token** @@ -39,18 +39,18 @@ Required for SAM API Server integration for the This group can be scheduled to run as desired. :::info -Run from the 6.Activity Job Group level in order to correlate 0.Collection job +Run from the 6.Activity Job Group level to correlate 0.Collection job group data with other jobs. ::: **History Retention** -History is not supported. Turning on history will cause issues with data analysis and reporting. +History isn't supported. Turning on history will cause issues with data analysis and reporting. **Multi-Console Support** -Multiple Access Analyzer Consoles are not supported. This group should be run from a single Access +Multiple Access Analyzer Consoles aren't supported. Run this group from a single Access Analyzer Console. **Workflow** @@ -69,7 +69,7 @@ Monitor API Server or the host with the network share housing the archived log f **Step 6 –** Run the jobs as desired. -**Step 7 –** Run from the **6.Activity** Job Group level in order to correlate 0.Collection job +**Step 7 –** Run from the **6.Activity** Job Group level to correlate 0.Collection job group data with other jobs. **Step 8 –** Review the reports generated by the jobs. diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/ad_securityassessment.md b/docs/accessanalyzer/12.0/solutions/activedirectory/ad_securityassessment.md index a8254b286b..7e0829f4d9 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/ad_securityassessment.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/ad_securityassessment.md @@ -9,7 +9,7 @@ sidebar_position: 90 The AD_SecurityAssessment Job performs checks against Active Directory security best practices in order to proactively identify critical security configurations that leave Active Directory vulnerable to attack. The result are reports that provide a listing of findings by severity and -category with corresponding details that can be used to prioritize and remediate security issues. +category with corresponding details you can use to prioritize and remediate security issues. ![AD Security Assessment Job](/images/accessanalyzer/12.0/solutions/activedirectory/securityassessmentjobstree.webp) @@ -17,7 +17,7 @@ category with corresponding details that can be used to prioritize and remediate **Dependencies** -One or more of the following job groups or jobs must be run to produce results: +To produce results, run one or more of the following job groups or jobs: - .Active Directory Inventory Job Group - Active Directory Job Group @@ -51,14 +51,14 @@ One or more of the following job groups or jobs must be run to produce results: - Windows > Privileged Accounts > Service Accounts > SG_ServiceAccounts :::note -If any of the above jobs are not completed, the AD_SecurityAssessment job will run but all -checks will not be assessed. +If any of these jobs aren't completed, the AD_SecurityAssessment job runs, but it doesn't +assess all checks. ::: **Target Host** -This job group does not collect data. No target host is required. +This job group doesn't collect data. No target host is required. **Connection Profile** @@ -70,11 +70,11 @@ Scheduled to run as desired **History Retention** -History is not supported. Turning on history will cause issues with data analysis and reporting. +History isn't supported. Turning on history will cause issues with data analysis and reporting. **Multi-console Support** -Multiple StealthAUDIT consoles are not supported. This job should be run from a single StealthAUDIT +Multiple StealthAUDIT consoles aren't supported. Run this job from a single StealthAUDIT console. ## Analysis Task for the AD_SecurityAssessment Job @@ -83,7 +83,7 @@ Navigate to the **Jobs** > Active Directory > AD_SecurityAssessment > Configure **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/certificateauthority/ad_cacollection.md b/docs/accessanalyzer/12.0/solutions/activedirectory/certificateauthority/ad_cacollection.md index a76c4886ef..20553c7392 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/certificateauthority/ad_cacollection.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/certificateauthority/ad_cacollection.md @@ -12,8 +12,7 @@ job is located in the Collection job group. **Target Host** -It is recommended to target the **ONE DOMAIN CONTROLLER PER DOMAIN** or **Default domain -controller** host list. +Target the **ONE DOMAIN CONTROLLER PER DOMAIN** or **Default domain controller** host list. ## Queries for the AD_CACollection Job @@ -39,7 +38,7 @@ Navigate to the **Active Directory** > **7.Certificate Authority** > **Collectio **AD_CACollection** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/certificateauthority/ad_certificateaudit.md b/docs/accessanalyzer/12.0/solutions/activedirectory/certificateauthority/ad_certificateaudit.md index 3aea5b8016..df46f0fd16 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/certificateauthority/ad_certificateaudit.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/certificateauthority/ad_certificateaudit.md @@ -14,7 +14,7 @@ Navigate to the **Active Directory** > **7.Certificate Authority** > **AD_Certif **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -33,4 +33,4 @@ produces the following pre-configured report: | Report | Description | Default Tags | Report Elements | | ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Certificate Authority Configuration | This report helps in identifying Certificate Authority configuration risks associated with permissions applied on the Active Directory object level as well as other unintended configurations set on the Certificate Authority level. Additionally, the rights on a Certificate Authority should be limited to those intended to administer or manage the Certificate Authority, so the ManageCA rights and ManageCertificate rights should be reviewed for potential misconfiguration. | None | This report is comprised of three elements:
  • Stacked Bar Chart – Displays a summary of Certificate Authority permissions
  • Table – Provides details on Certificate Authorities
  • Table – Provides details on access rights
| +| Certificate Authority Configuration | This report helps identify Certificate Authority configuration risks associated with permissions applied on the Active Directory object level as well as other unintended configurations set on the Certificate Authority level. Additionally, limit the rights on a Certificate Authority to those needed to administer or manage it, and review the ManageCA and ManageCertificate rights for potential misconfiguration. | None | This report is comprised of three elements:
  • Stacked Bar Chart – Displays a summary of Certificate Authority permissions
  • Table – Provides details on Certificate Authorities
  • Table – Provides details on access rights
| diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/certificateauthority/ad_certificaterequests.md b/docs/accessanalyzer/12.0/solutions/activedirectory/certificateauthority/ad_certificaterequests.md index 0f4063c5ad..078710c3cd 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/certificateauthority/ad_certificaterequests.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/certificateauthority/ad_certificaterequests.md @@ -11,8 +11,8 @@ are expiring soon. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable -parameters used by analysis tasks in the job. See the +Use the Configuration section on a Job's overview page to modify any customizable parameters used +by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/12.0/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -20,9 +20,9 @@ The AD_CertificateRequests job has the following configurable parameter: - Number of days to consider a cert close to expiration (default 60) -This parameter sets the definition of an expiring certificate, which is used by the Certificate -Expiration analysis task to identify any certificates expiring with this specified next number of -days. The default is 60 days. +This parameter defines what counts as an expiring certificate. The Certificate Expiration analysis +task uses it to identify certificates expiring within the specified number of days. The default is +60 days. ## Analysis Tasks for the AD_CertificateRequests Job @@ -30,7 +30,7 @@ Navigate to the **Active Directory** > **7.Certificate Authority** > **AD_Certif **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -41,8 +41,8 @@ The default analysis tasks are: - Suspicious Principal Certs – Identifies certificates that show the requester requesting a certificate for a different principal -- OID in Template – Analysis on certificate Extended Key Usage (EKU) Object Identifier (OID) being - in template OID +- OID in Template – Identifies certificates where the Extended Key Usage (EKU) Object Identifier + (OID) is in the template OID - Certificate Expiration – Identifies certificates that expire in the next number of days set by the customizable parameter. The default number of days is 60. Creates the SA_AD_CertificateRequests_ExpiringSoon table accessible under the job’s Results node. diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/ad_cleanupprogress.md b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/ad_cleanupprogress.md index 1c78484f63..82b9b79bb8 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/ad_cleanupprogress.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/ad_cleanupprogress.md @@ -6,10 +6,10 @@ sidebar_position: 50 # AD_CleanupProgress Job -The AD_CleanupProgress Job performs checks against Active Directory security best practices in order -to proactively identify critical security configurations that leave Active Directory vulnerable to +The AD_CleanupProgress Job performs checks against Active Directory security best practices to +proactively identify critical security configurations that leave Active Directory vulnerable to attack. The result is a report which provides a listing of findings by severity and category with -corresponding details that can be used to prioritize and remediate security issues. +corresponding details you can use to prioritize and remediate security issues. ![AD_CleanupProgress Job in the Jobs Tree](/images/accessanalyzer/12.0/solutions/activedirectory/cleanup/cleanupprogressjobstree.webp) @@ -17,8 +17,8 @@ corresponding details that can be used to prioritize and remediate security issu **Step 1 –** Ensure the following prerequisites are met: -- The .Active Directory Inventory Job Group needs to be successfully run prior to running this job -- The following jobs from the Active Directory Solution must be run prior to running this job: +- The .Active Directory Inventory Job Group needs to be successfully run before running this job +- The following jobs from the Active Directory Solution must be run before running this job: - **Active Directory** > **1.Groups** > **AD_DuplicateGroups** - **Active Directory** > **2.Users** > **AD_DirectMembership** @@ -35,7 +35,7 @@ Navigate to the **Active Directory** > **Cleanup** > **AD_CleanupProgress** > ** select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/computers/ad_deprovisioncomputers.md b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/computers/ad_deprovisioncomputers.md index 14f625f17d..0218713fdb 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/computers/ad_deprovisioncomputers.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/computers/ad_deprovisioncomputers.md @@ -10,7 +10,7 @@ The AD_DeprovisionComputers Job provides a simple automated workflow deprovision **Step 1 –** Move stale computers to a staging OU for deletion. -**Step 2 –** The assigned manager is alerted by email of the impending deletion. +**Step 2 –** Alerts the assigned manager by email of the impending deletion. **Step 3 –** Disables computer accounts. @@ -19,8 +19,8 @@ staging OU. The default is 365 days. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable -parameters used by analysis tasks in the job. See the +Use the Configuration section on a Job's overview page to modify any customizable parameters used +by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/12.0/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -29,7 +29,7 @@ The AD_DeprovisionComputers page has the following configurable parameters: - Days in the Staging OU before Deleting Account See the -[Customizable Analysis Parameters for the AD_DeprovisionComputers Job](#customizable-analysis-parameters-for-the-ad_deprovisioncomputers-job) +[Customizable Analysis Parameters for the AD_DeprovisionComputers Job](#customizable-analysis-parameters-for-the-addeprovisioncomputers-job) topic for additional information. ## Analysis Tasks for the AD_DeprovisionComputers Job @@ -47,13 +47,13 @@ The default analysis tasks are: under the job’s Results node - This analysis task contains a configurable parameter: `@days_before_deleting`. See the - [Customizable Analysis Parameters for the AD_DeprovisionComputers Job](#customizable-analysis-parameters-for-the-ad_deprovisioncomputers-job) + [Customizable Analysis Parameters for the AD_DeprovisionComputers Job](#customizable-analysis-parameters-for-the-addeprovisioncomputers-job) topic for additional information. ### Customizable Analysis Parameters for the AD_DeprovisionComputers Job -Customizable parameters enable you to set the values used to classify user and group objects during -this job’s analysis. +Use customizable parameters to set the values used to classify user and group objects during this +job's analysis. | Analysis Task | Customizable Parameter Name | Default Value | Value Indicates | | --------------------------- | --------------------------- | ------------- | ---------------------------------------------- | @@ -69,7 +69,7 @@ Navigate to the **Active Directory** > **Cleanup** > **3.Computers** > **AD_Depr **Configure** node and select **Actions** to view the actions. :::warning -Do not enable the actions unless it is required. Disable the actions after execution to +Don't enable the actions unless it is required. Disable the actions after execution to prevent making unintended and potentially harmful changes to Active Directory. ::: @@ -85,7 +85,7 @@ The action tasks must be executed together and in order. - Move Computers – Move computers to staging OU for deletion - - The target staging OU must be set in the Move Computers Action Task prior to executing the + - The target staging OU must be set in the Move Computers Action Task before executing the action tasks. See the [Configure the Target OU](/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/configuretargetou.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/computers/ad_deprovisioncomputers_status.md b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/computers/ad_deprovisioncomputers_status.md index fda4c83df8..64ef1271a1 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/computers/ad_deprovisioncomputers_status.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/computers/ad_deprovisioncomputers_status.md @@ -16,7 +16,7 @@ Navigate to the **Active Directory** > **Cleanup** > **3.Computers** > tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/computers/overview.md b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/computers/overview.md index 856c8fefc9..86dbba8092 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/computers/overview.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/computers/overview.md @@ -24,10 +24,10 @@ The jobs in the 3.Computers Job Group are: - The .Active Directory Inventory Job Group needs to be successfully run - For the AD_DeprovisionComputers Job, the target OU needs to be manually set in the Move Computers - Action Task prior to executing the actions. See the - [Action Tasks for the AD_DeprovisionComputers Job](ad_deprovisioncomputers.md#action-tasks-for-the-ad_deprovisioncomputers-job) + Action Task before executing the actions. See the + [Action Tasks for the AD_DeprovisionComputers Job](ad_deprovisioncomputers.md#action-tasks-for-the-addeprovisioncomputers-job) topic for additional information. -- The AD_DeprovisionComputers Job needs to be run prior to running the +- The AD_DeprovisionComputers Job needs to be run before running the AD_DeprovisionComputers_Status Job **Step 2 –** Schedule the 3.Computers Job Group to run as desired after the prerequisites have been diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/configuretargetou.md b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/configuretargetou.md index ed002bb746..a0375d4830 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/configuretargetou.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/configuretargetou.md @@ -6,13 +6,13 @@ sidebar_position: 60 # Configure the Target OU -Follow the steps to configure the target staging OU. +Configure the target staging OU: **Step 1 –** Navigate to the **[Job]** > **Configure** > **Actions** node. ![Action Properties button on Action Selection page](/images/accessanalyzer/12.0/solutions/activedirectory/cleanup/configuretargetouactionproperties.webp) -**Step 2 –** On the Action Selection page, select the desired action task and click **Action +**Step 2 –** On the Action Selection page, select the action task you want and click **Action Properties**. **Step 3 –** In the Action Properties window, select **Configure Action**. The Active Directory @@ -21,8 +21,8 @@ Action Module Wizard opens. ![Move Objects page of the Active Directory Action Module Wizard](/images/accessanalyzer/12.0/solutions/activedirectory/cleanup/configuretargetouactionmodulewizard.webp) **Step 4 –** Navigate to the Move Objects page of the Active Directory Action Module Wizard. In the -OU field, enter or browse to the desired target OU. To create the target OU location, select the -**Create target OU location if it does not already exist** checkbox. +OU field, enter or browse to the target OU you want. To create the target OU location, select the +**Create target OU location if it doesn't already exist** checkbox. **Step 5 –** Navigate to the Summary page and click **Finish**. diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/deprovision/ad_deprovisiongroups.md b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/deprovision/ad_deprovisiongroups.md index ca35e7bef4..257356ac92 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/deprovision/ad_deprovisiongroups.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/deprovision/ad_deprovisiongroups.md @@ -6,24 +6,24 @@ sidebar_position: 10 # AD_DeprovisionGroups Job -The AD_DeprovisionGroups Job provides an automated workflow to deprovision stale groups. This -workflow is completed by the action tasks. +The AD_DeprovisionGroups Job provides an automated workflow to deprovision stale groups. The action +tasks complete this workflow. **Step 1 –** Move stale groups to a staging OU for deletion. -**Step 2 –** The group is changed to a distribution list. +**Step 2 –** Changes the group to a distribution list. -**Step 3 –** The assigned manager is alerted by email of the impending deletion. +**Step 3 –** Alerts the assigned manager by email of the impending deletion. -**Step 4 –** The group is flagged as **To Be Deleted**. +**Step 4 –** Flags the group as **To Be Deleted**. -**Step 5 –** After a configurable amount of days in the staging OU, the group is deleted from the +**Step 5 –** After a configurable amount of days in the staging OU, deletes the group from the staging OU. The default is 365 days. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable -parameters used by analysis tasks in the job. See the +Use the Configuration section on a Job's overview page to modify any customizable parameters used +by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/12.0/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -32,7 +32,7 @@ The AD_DeprovisionGroups page has the following configurable parameters: - Days in the Staging OU before deletion See the -[Customizable Analysis Parameters for the AD_DeprovisionGroups Job](#customizable-analysis-parameters-for-the-ad_deprovisiongroups-job) +[Customizable Analysis Parameters for the AD_DeprovisionGroups Job](#customizable-analysis-parameters-for-the-addeprovisiongroups-job) topic for additional information. ## Analysis Tasks for the AD_DeprovisionGroups Job @@ -49,13 +49,13 @@ The default analysis tasks are: - Groups to Delete – Identifies groups in the Stale Groups OU that are ready to be deleted - This analysis task contains a configurable parameter: `@days_before_deleting`. See the - [Customizable Analysis Parameters for the AD_DeprovisionGroups Job](#customizable-analysis-parameters-for-the-ad_deprovisiongroups-job) + [Customizable Analysis Parameters for the AD_DeprovisionGroups Job](#customizable-analysis-parameters-for-the-addeprovisiongroups-job) topic for additional information. ### Customizable Analysis Parameters for the AD_DeprovisionGroups Job -Customizable parameters enable you to set the values used to classify user and group objects during -this job’s analysis. +Use customizable parameters to set the values used to classify user and group objects during this +job's analysis. | Analysis Task | Customizable Parameter Name | Default Value | Value Indicates | | ---------------- | --------------------------- | ------------- | -------------------------------------- | @@ -71,7 +71,7 @@ Navigate to the **Active Directory** > **Cleanup** > **1.Groups** > **1. Deprovi **AD_DeprovisonGroups** > **Configure** node and select **Actions** to view the action tasks. :::warning -Do not enable the actions unless it is required. Disable the actions after execution to +Don't enable the actions unless it is required. Disable the actions after execution to prevent making unintended and potentially harmful changes to Active Directory. ::: @@ -87,15 +87,15 @@ The action tasks must be executed together and in order. - Move Groups – Move groups to staging OU - - The target staging OU must be set in the Move Groups Action Task prior to executing the action + - The target staging OU must be set in the Move Groups Action Task before executing the action tasks. See the [Configure the Target OU](/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/configuretargetou.md) topic for additional information. -- Disable Groups – The group is changed to a distribution list +- Disable Groups – Changes the group to a distribution list - Notify Manager – Notify assigned manager by email of the impending deletion -- Update Description – The group is changed to a distribution list to prevent its use for - authentication and flagged as **To Be Deleted** -- Delete Groups – After a configurable amount of days in the staging OU, the group is deleted. The +- Update Description – Changes the group to a distribution list to prevent its use for + authentication and flags it as **To Be Deleted** +- Delete Groups – After a configurable amount of days in the staging OU, deletes the group. The default is 365 days. After the `@days_before_deleting` analysis parameter has been configured and the target OU has been diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/deprovision/ad_deprovisiongroups_status.md b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/deprovision/ad_deprovisiongroups_status.md index 2566235230..0f7962ae12 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/deprovision/ad_deprovisiongroups_status.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/deprovision/ad_deprovisiongroups_status.md @@ -15,7 +15,7 @@ Navigate to the **Active Directory** > **Cleanup** > **1.Groups** > **1. Deprovi tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis tasks is +Don't modify or deselect the selected analysis task. The analysis tasks is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/overview.md b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/overview.md index 1cf8e664dc..2bbb616580 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/overview.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/overview.md @@ -6,8 +6,8 @@ sidebar_position: 20 # 1.Groups Job Group -The 1.Groups Job Group provides a workflow to safely deprovision groups, as well as the ability to -stamp security groups with what resources they are given access to. +The 1.Groups Job Group provides a workflow to safely deprovision groups and stamp security groups +with the resources they can access. ![1.Groups Job Group in the Jobs Tree](/images/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/groupsjobtree.webp) @@ -25,8 +25,8 @@ The jobs in the 1.Groups Job Group are: for all security groups to show where the group is provisioned inside the environment. - [AD_GroupCleanup_Permissions Job](/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/stamping/ad_groupcleanup_permissions.md) – This job reports - on where security groups are being used to assign permissions. This can be used to prioritize - remediation for groups that are rarely used. + on where security groups are being used to assign permissions. Use this information to + prioritize remediation for groups that are rarely used. - [AD_GroupStamping Job](/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/stamping/ad_groupstamping.md) – This job replaces the Notes attribute for all security groups to show where the group is provisioned inside the environment. This overwrites the Notes field with data from Access Analyzer. @@ -37,10 +37,10 @@ The jobs in the 1.Groups Job Group are: - The .Active Directory Inventory Job Group needs to be successfully run - For the AD_DeprovisionGroups Job, the target OU needs to be manually set in the Move Groups Action - Task prior to executing the actions. See the - [Action Tasks for the AD_DepvisionGroups Job](deprovision/ad_deprovisiongroups.md#action-tasks-for-the-ad_depvisiongroups-job) + Task before executing the actions. See the + [Action Tasks for the AD_DepvisionGroups Job](deprovision/ad_deprovisiongroups.md#action-tasks-for-the-addepvisiongroups-job) topic for additional information. -- The AD_DeprovisionGroups Job needs to be run prior to running the AD_DeprovisionGroups_Status Job +- The AD_DeprovisionGroups Job needs to be run before running the AD_DeprovisionGroups_Status Job **Step 2 –** Schedule the 1.Groups Job Group to run as desired after the prerequisites have been satisfied. diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/stamping/ad_groupcleanup_permissions.md b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/stamping/ad_groupcleanup_permissions.md index bb53e84bc1..23cf6817ba 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/stamping/ad_groupcleanup_permissions.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/stamping/ad_groupcleanup_permissions.md @@ -7,7 +7,7 @@ sidebar_position: 10 # AD_GroupCleanup_Permissions Job The AD_GroupCleanup_Permissions Job reports on where security groups are being used to assign -permissions. This can be used to prioritize remediation for groups that are rarely used. +permissions. Use this information to prioritize remediation for groups that are rarely used. ## Analysis Tasks for the AD_GroupCleanup_Permissions Job @@ -16,7 +16,7 @@ Navigate to the **Active Directory** > **Cleanup** > **1.Groups** > **2. Group S tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/stamping/ad_groupstamping.md b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/stamping/ad_groupstamping.md index 6ad91c8268..444f65952c 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/stamping/ad_groupstamping.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/stamping/ad_groupstamping.md @@ -16,7 +16,7 @@ Navigate to the **Active Directory** > **Cleanup** > **1.Groups** > **2. Group S AD_GroupStamping** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/overview.md b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/overview.md index 79f0eedd13..ec29a8b63c 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/overview.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/overview.md @@ -28,12 +28,11 @@ environment. The job groups in the Cleanup Job Group are: - [1.Groups Job Group](/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/overview.md) – Provides an automated workflow to safely deprovision - groups, as well as the ability to stamp security groups with what resources they are given access - to + groups and stamp security groups with the resources they can access - [2.Users Job Group](/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/users/overview.md) – Provides an automated workflow to deprovision stale and unused user accounts - [3.Computers Job Group](/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/computers/overview.md) – Provides an automated workflow to deprovision stale computer accounts - [AD_CleanupProgress Job](/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/ad_cleanupprogress.md) – Tracks Active Directory computer, group, and - user exceptions over time. This information can be used to provide a high-level picture of an + user exceptions over time. Use this information to provide a high-level picture of an organization's Active Directory cleanup effort. diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/recommended.md b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/recommended.md index 4ae21882f5..9238cbd6b6 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/recommended.md @@ -14,7 +14,7 @@ The Cleanup job group has the following prerequisites: - The Active Directory Actions license feature is required - The Active Directory Actions Module must be installed -- The .Active Directory Inventory Job Group needs to be successfully run prior to running this job +- The .Active Directory Inventory Job Group needs to be successfully run before running this job group - The following job groups from the Activity Directory job group need to be successfully run prior to running this job group: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/users/ad_deprovisionusers.md b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/users/ad_deprovisionusers.md index 95d81b2307..5c668d8531 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/users/ad_deprovisionusers.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/users/ad_deprovisionusers.md @@ -11,11 +11,11 @@ accounts. **Step 1 –** Move stale users to a staging OU for deletion. -**Step 2 –** The assigned manager is alerted by email of the impending deletion. +**Step 2 –** Alerts the assigned manager by email of the impending deletion. -**Step 3 –** User accounts are disabled. +**Step 3 –** Disables user accounts. -**Step 4 –** Users are flagged as **To Be Deleted**. +**Step 4 –** Flags users as **To Be Deleted**. **Step 5 –** Delete users from the staging OU. @@ -23,8 +23,8 @@ accounts. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable -parameters used by analysis tasks in the job. See the +Use the Configuration section on a Job's overview page to modify any customizable parameters used +by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/12.0/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -33,7 +33,7 @@ The AD_DeprovisionUsers page has the following configurable parameters: - Days in the Stale Users OU before being deleted See the -[Customizable Analysis Parameters for the AD_DeprovisionUsers Job](#customizable-analysis-parameters-for-the-ad_deprovisionusers-job) +[Customizable Analysis Parameters for the AD_DeprovisionUsers Job](#customizable-analysis-parameters-for-the-addeprovisionusers-job) topic for additional information. ## Analysis Tasks for the AD_DeprovisionUsers Job @@ -50,15 +50,15 @@ The default analysis tasks are: deleted - This analysis task contains a configurable parameter: `@days_before_deleting`. See the - [Customizable Analysis Parameters for the AD_DeprovisionUsers Job](#customizable-analysis-parameters-for-the-ad_deprovisionusers-job) + [Customizable Analysis Parameters for the AD_DeprovisionUsers Job](#customizable-analysis-parameters-for-the-addeprovisionusers-job) topic for additional information. - Identify Group Membership – Identifies stale user membership to remove ### Customizable Analysis Parameters for the AD_DeprovisionUsers Job -Customizable parameters enable you to set the values used to classify user and group objects during -this job’s analysis. +Use customizable parameters to set the values used to classify user and group objects during this +job's analysis. | Analysis Task | Customizable Parameter Name | Default Value | Value Indicates | | ----------------------- | --------------------------- | ------------- | ----------------------------------------------- | @@ -74,7 +74,7 @@ Navigate to the **Active Directory** > **Cleanup** > **2.Users** > **AD_Deprovis **Configure** node and select **Actions** to view the actions. :::warning -Do not enable the actions unless it is required. Disable the actions after execution to +Don't enable the actions unless it is required. Disable the actions after execution to prevent making unintended and potentially harmful changes to Active Directory. ::: @@ -90,7 +90,7 @@ The action tasks must be executed together and in order. - Move Users – Move users to staging OU for deletion - - The target OU must be set in the Move Users Action Task prior to executing the action tasks. + - The target OU must be set in the Move Users Action Task before executing the action tasks. See the [Configure the Target OU](/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/configuretargetou.md) topic for additional information. - Notify Manager – Notify assigned manager by email of the impending deletion diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/users/ad_deprovisionusers_status.md b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/users/ad_deprovisionusers_status.md index f1d3e79ca0..9564d6f6a7 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/users/ad_deprovisionusers_status.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/users/ad_deprovisionusers_status.md @@ -14,7 +14,7 @@ Navigate to the **Active Directory** > **Cleanup** > **2.Users** > **AD_Deprovis **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/users/overview.md b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/users/overview.md index 4fa7116698..7f726aa891 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/users/overview.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/users/overview.md @@ -23,10 +23,10 @@ The jobs in the 2.Users Job Group are: - The .Active Directory Inventory Job Group needs to be successfully run - For the AD_DeprovisionUsers Job, the target OU needs to be manually set in the Move Users Action - Task prior to executing the actions. See the - [Action Tasks for the AD_DeprovisionUsers Job](ad_deprovisionusers.md#action-tasks-for-the-ad_deprovisionusers-job) + Task before executing the actions. See the + [Action Tasks for the AD_DeprovisionUsers Job](ad_deprovisionusers.md#action-tasks-for-the-addeprovisionusers-job) topic for additional information. -- The AD_DeprovisionUsers Job needs to be run prior to running the AD_DeprovisionUsers_Status Job +- The AD_DeprovisionUsers Job needs to be run before running the AD_DeprovisionUsers_Status Job **Step 2 –** Schedule the 2.Users Job Group to run as desired after the prerequisites have been satisfied. diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/computers/ad_computerdelegation.md b/docs/accessanalyzer/12.0/solutions/activedirectory/computers/ad_computerdelegation.md index e767b277dc..88a29b88e5 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/computers/ad_computerdelegation.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/computers/ad_computerdelegation.md @@ -6,11 +6,11 @@ sidebar_position: 20 # AD_ComputerDelegation Job -The AD_ComputerDelegation Job provides details on computer accounts that have been enabled for -unconstrained delegation. Once this configuration is enabled for a computer, any time an account -connects to the computer for any reason, their ticket-granting ticket (TGT) is stored in memory so -it can be used later by the computer for impersonation, which exposes a significant security risk in -cases where privileged accounts access the computer.  See the +The AD_ComputerDelegation Job provides details on computer accounts that have unconstrained +delegation enabled. When an account connects to one of these computers, Active Directory stores the +account's ticket-granting ticket (TGT) in memory. The computer can then reuse that TGT for +impersonation, which creates a significant security risk if privileged accounts access the computer. +See the [What Is Kerberos Delegation?](https://blog.netwrix.com/2021/11/30/what-is-kerberos-delegation-an-overview-of-kerberos-delegation/) Netwrix blog article for more information about this configuration and the related security risks. @@ -20,7 +20,7 @@ Navigate to the **Active Directory** > **3.Computers** > **AD_ComputerDelegation and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the analysis task. The analysis task is preconfigured for +Don't modify or deselect the analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/computers/ad_stalecomputers.md b/docs/accessanalyzer/12.0/solutions/activedirectory/computers/ad_stalecomputers.md index 439730b1e5..ba42321829 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/computers/ad_stalecomputers.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/computers/ad_stalecomputers.md @@ -10,8 +10,8 @@ The AD_StaleComputers Job provides details on stale computers that may be candid ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable -parameters used by analysis tasks in the job. See the +Use the Configuration section on a Job's overview page to modify any customizable parameters used +by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/12.0/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -21,7 +21,7 @@ The AD_StaleComputers Job has the following configurable parameters: - Consider disabled accounts as stale See the -[Customizable Analysis Parameters for the AD_StaleComputers Job](#customizable-analysis-parameters-for-the-ad_stalecomputers-job) +[Customizable Analysis Parameters for the AD_StaleComputers Job](#customizable-analysis-parameters-for-the-adstalecomputers-job) topic for additional information. ## Analysis Tasks for the AD_StaleComputers Job @@ -30,7 +30,7 @@ Navigate to the **Active Directory** > **3.Computers** > **AD_StaleComputers** > and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the **2. Summarize by Domain** analysis task. This analysis +Don't modify or deselect the **2. Summarize by Domain** analysis task. This analysis task is preconfigured for this job. ::: @@ -44,7 +44,7 @@ The default analysis tasks are: - Identifies computer objects that are disabled or have exceeded the defined threshold of inactivity - Creates the SA_AD_StaleComputers_Details table accessible under the job’s Results node - - Definition of a stale computer can be customized + - You can customize the definition of a stale computer - **2. Summarize by Domain** – Creates the SA_AD_StaleComputers_DomainSummay table accessible under the job’s Results node @@ -65,7 +65,7 @@ Analysis parameters that can be customized have the following default values: | Analysis Task | Customizable Parameter Name | Default Value | Value Indicates | | --------------------------- | --------------------------- | ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 1. Identify Stale Computers | @days_since_last_logon | 90 | A computer object that has been inactive for 90 days or more | -| 1. Identify Stale Computers | @consider_disable | 1 | A computer object that has been disabled:
  • Value 1 = Disabled computers are included as stale
  • Value 0 = Disabled computers are not included as stale
| +| 1. Identify Stale Computers | @consider_disable | 1 | A computer object that has been disabled:
  • Value 1 = Disabled computers are included as stale
  • Value 0 = Disabled computers aren't included as stale
| See the diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/computers/overview.md b/docs/accessanalyzer/12.0/solutions/activedirectory/computers/overview.md index 2d439a8958..7a712d8e0b 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/computers/overview.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/computers/overview.md @@ -14,10 +14,10 @@ computer accounts, including stale computers and computers that have been truste The following jobs comprise the 3.Computers Job Group: - [AD_ComputerDelegation Job](/docs/accessanalyzer/12.0/solutions/activedirectory/computers/ad_computerdelegation.md) – Provides details on computer accounts that - have been trusted for delegation. Once this configuration is enabled for a computer, any time an - account connects to the computer for any reason, their ticket-granting ticket (TGT) is stored in - memory so it can be used later by the computer for impersonation, which exposes a significant - security risk in cases where privileged accounts access the computer.  See the + have unconstrained delegation enabled. When an account connects to one of these computers, Active + Directory stores the account's ticket-granting ticket (TGT) in memory. The computer can then reuse + that TGT for impersonation, which creates a significant security risk if privileged accounts + access the computer. See the [What Is Kerberos Delegation?](https://blog.netwrix.com/2021/11/30/what-is-kerberos-delegation-an-overview-of-kerberos-delegation/) Netwrix blog article for more information about this configuration and the related security risks. - [AD_StaleComputers Job](/docs/accessanalyzer/12.0/solutions/activedirectory/computers/ad_stalecomputers.md) – Provides details on stale computers that may be diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/computers/recommended.md b/docs/accessanalyzer/12.0/solutions/activedirectory/computers/recommended.md index 521cf0da01..e9996c7a2c 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/computers/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/computers/recommended.md @@ -11,22 +11,22 @@ default settings. It can be run directly or scheduled. **Dependencies** -The **.Active Directory Inventory** Job Group needs to be successfully executed prior to running +The **.Active Directory Inventory** Job Group needs to be successfully executed before running this job group. **Target Host** -This job group does not collect data. No target host is required. +This job group doesn't collect data. No target host is required. **Connection Profile** -This job group does not collect data. No specific Connection Profile is required. +This job group doesn't collect data. No specific Connection Profile is required. **Schedule Frequency** -The data analyzed by the 3.Computers Job Group jobs is collected by the .Active Directory Inventory -Job Group. Therefore, it is recommended to schedule these jobs to run after the .Active Directory -Inventory job group collection has completed. These jobs can be scheduled to run as desired. +The .Active Directory Inventory Job Group collects the data that the 3.Computers Job Group jobs +analyze. Schedule these jobs to run after the .Active Directory Inventory Job Group finishes +collecting data, and run them as often as needed. **Run at the Job Group Level** @@ -43,8 +43,8 @@ analysis tasks are preconfigured for this Job Group. Some analysis tasks have customizable parameters: -- The **Active Directory** > **3.Computers** > **AD_StaleComputers** Job defines stale users. The - parameters can be customized. +- The **Active Directory** > **3.Computers** > **AD_StaleComputers** Job defines stale users. You + can customize the parameters. **Workflow** diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/domains/ad_dcsummary.md b/docs/accessanalyzer/12.0/solutions/activedirectory/domains/ad_dcsummary.md index 8447752c7e..3e76c2fe07 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/domains/ad_dcsummary.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/domains/ad_dcsummary.md @@ -16,7 +16,7 @@ Navigate to the **Active Directory > 5.Domains > AD_DCSummary > Configure** node **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/domains/ad_domaininfo.md b/docs/accessanalyzer/12.0/solutions/activedirectory/domains/ad_domaininfo.md index 9821d07153..3e1550e263 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/domains/ad_domaininfo.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/domains/ad_domaininfo.md @@ -16,7 +16,7 @@ The AD_DomainInfo Job uses the ActiveDirectory Data Collector and the LDAP Data following queries: :::warning -Do not modify the queries. The queries are preconfigured for this job. +Don't modify the queries. The queries are preconfigured for this job. ::: @@ -42,7 +42,7 @@ Navigate to the **Active Directory > 5.Domains > AD_DomainInfo > Configure** nod **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/domains/ad_dsrmsettings.md b/docs/accessanalyzer/12.0/solutions/activedirectory/domains/ad_dsrmsettings.md index a23153dfef..b689df26b6 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/domains/ad_dsrmsettings.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/domains/ad_dsrmsettings.md @@ -7,8 +7,8 @@ sidebar_position: 50 # AD_DSRMSettings Job The AD_DRSMSettings Job provides details on domain controller registry settings for the -DSRMAdminLogonBehavior key. If this key is set to 1 or 2, the DSRM Admin Account can be used to log -in to the domain controller even if it has not been started in DSRM which can present a potential +DSRMAdminLogonBehavior key. If this key is set to 1 or 2, the DSRM Admin Account can log +in to the domain controller even if it has not been started in DSRM, which can present a potential security vulnerability. Additional information on this registry key is available in this [Microsoft Document](https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc732714(v=ws.10)?redirectedfrom=MSDN). @@ -18,7 +18,7 @@ Navigate to the **Active Directory > 5.Domains > AD_DSRMSettings > Configure** n **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -37,4 +37,4 @@ the following pre-configured report: | Report | Description | Default Tags | Report Elements | | ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| DSRM Admin Security | This report highlights domain controller registry settings for the DSRMAdminLogonBehavior key. If this key is set to 1 or 2, the DSRM Admin account can be used to log in to the domain controller even if it has not been started in DSRM. This is a potential vulnerability. See the Microsoft [Restartable AD DS Step-by-Step Guide](https://technet.microsoft.com/en-us/library/cc732714(v=ws.10).aspx) for additional information. | None | This report is comprised of two elements:
  • Pie Chart – Displays DSRM admin logon  by domain controller
  • Table – Provides details on domain controllers
| +| DSRM Admin Security | This report highlights domain controller registry settings for the DSRMAdminLogonBehavior key. If this key is set to 1 or 2, the DSRM Admin account can log in to the domain controller even if it has not been started in DSRM. This is a potential vulnerability. See the Microsoft [Restartable AD DS Step-by-Step Guide](https://technet.microsoft.com/en-us/library/cc732714(v=ws.10).aspx) for additional information. | None | This report is comprised of two elements:
  • Pie Chart – Displays DSRM admin logon  by domain controller
  • Table – Provides details on domain controllers
| diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/domains/ad_kerberoastingrisk.md b/docs/accessanalyzer/12.0/solutions/activedirectory/domains/ad_kerberoastingrisk.md index 540c5b92ef..59c861d03e 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/domains/ad_kerberoastingrisk.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/domains/ad_kerberoastingrisk.md @@ -10,7 +10,8 @@ The AD_KerberoastingRisk job identifies accounts vulnerable to kerberoasting. Ke threat where attackers target service accounts in Active Directory to steal their passwords. In a kerberoasting attack, attackers request service tickets (TGS) for service accounts from the Key -Distribution Center (KDC). These tickets are encrypted with the service account's password hash. +Distribution Center (KDC). Active Directory encrypts these tickets with the service account's +password hash. Attackers attempt to crack these hashes offline to reveal the passwords for the service accounts. Encryption types vulnerable to kerberoasting include RC4 and DES. AES-128 can also be considered @@ -22,7 +23,7 @@ article for additional information on kerberoasting. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/12.0/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -43,7 +44,7 @@ Navigate to the **Active Directory** > **5.Domains** > **AD_KerberoastingRisk** and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -54,9 +55,9 @@ The default analysis tasks are: - Kerberoasting Details – Provides details on accounts vulnerabilities to Kerberoasting - - This task uses three customizable parameters. These allow you to optionally consider AES-128 - as a weak encryption type, consider Password Never Expires as being easily crackable, and - include disabled user accounts. See the + - This task uses three customizable parameters. Use these parameters to optionally consider + AES-128 as a weak encryption type, consider Password Never Expires as being easily crackable, + and include disabled user accounts. See the [Parameter Configuration](#parameter-configuration) topic for additional information. - Kerberoasting Summary – Summarizes accounts by domain with counts for multiple vulnerabilities diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/domains/collection/ad_domaincontrollers.md b/docs/accessanalyzer/12.0/solutions/activedirectory/domains/collection/ad_domaincontrollers.md index 2a68d9685d..d1046f7775 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/domains/collection/ad_domaincontrollers.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/domains/collection/ad_domaincontrollers.md @@ -6,8 +6,8 @@ sidebar_position: 10 # AD_DomainControllers Job -The 0.Collection > AD_DomainControllers Job collects domain controller details which will be further -analyzed in order to provide information on domains, sites, and trusts. +The 0.Collection > AD_DomainControllers Job collects domain controller details for further analysis +to provide information on domains, sites, and trusts. ## Queries for the AD_DomainControllers Job @@ -15,7 +15,7 @@ The AD_DomainControllers Job uses the LDAP Data Collector and the ActiveDirector the following queries: :::warning -Except the first query, do not modify the remaining queries. The remaining queries are +Except the first query, don't modify the remaining queries. The remaining queries are preconfigured for this job. ::: @@ -26,7 +26,7 @@ The queries for this job are: - Domain Controller Listing – Targets one domain controller per domain known to Access Analyzer to collect a listing of all domain controllers - - Can be modified to connect securely with TLS/SSL. + - You can modify this query to connect securely with TLS/SSL. - See the [Connect Securely with TLS/SSL](#connect-securely-with-tlsssl) topic for additional information. - Actual Bridgehead Servers – Targets one domain controller per domain known to Access Analyzer to @@ -47,10 +47,10 @@ The queries for this job are: ### Connect Securely with TLS/SSL The Domain Controller Listing Query in the AD_DomainControllers Job is configured to use the LDAP -Data Collector. This query can be optionally configured to connect securely with TLS/SSL. +Data Collector. You can optionally configure this query to connect securely with TLS/SSL. :::warning -Do not modify any other settings in this query. +Don't modify any other settings in this query. ::: @@ -72,6 +72,6 @@ opens. **Ignore Certificate Errors** to connect even if certificate errors occur. Use **Server Port** 686 for a secure connection. Click **OK** to close the Options page. -**Step 6 –** Step 13 – Then click **OK** to close the LDAP template form wizard. +**Step 6 –** Click **OK** to close the LDAP template form wizard. The job now connects securely with TLS/SSL. diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/domains/collection/ad_dsrm.md b/docs/accessanalyzer/12.0/solutions/activedirectory/domains/collection/ad_dsrm.md index 0c045d1858..d988c9de71 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/domains/collection/ad_dsrm.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/domains/collection/ad_dsrm.md @@ -7,17 +7,17 @@ sidebar_position: 20 # AD_DSRM Job The **0.Collection > AD_DSRM** Job collects data related to domain controller registry settings for -the DSRMAdminLogonBehavior key. If this key is set to 1 or 2, the DSRM Admin Account can be used to -log in to the domain controller even if it has not been started in DSRM which can present a +the DSRMAdminLogonBehavior key. If this key is set to 1 or 2, the DSRM Admin Account can log in to +the domain controller even if it has not been started in DSRM, which can present a potential security vulnerability. Additional information on this registry key is available in this [Microsoft Document](https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc732714(v=ws.10)?redirectedfrom=MSDN). ## Query for the AD_DSRM Job -The AD_TimeSync Job uses the Registry Data Collector for the following query: +The AD_DSRM Job uses the Registry Data Collector for the following query: :::warning -Do not modify this query. The query is preconfigured for this job. +Don't modify this query. The query is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/domains/collection/ad_timesync.md b/docs/accessanalyzer/12.0/solutions/activedirectory/domains/collection/ad_timesync.md index d5a41bcb9b..a1de19ca8d 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/domains/collection/ad_timesync.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/domains/collection/ad_timesync.md @@ -14,7 +14,7 @@ domain controller within the domain. The AD_TimeSync Job uses the Registry Data Collector for the following query: :::warning -Do not modify this query. The query is preconfigured for this job. +Don't modify this query. The query is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/domains/collection/overview.md b/docs/accessanalyzer/12.0/solutions/activedirectory/domains/collection/overview.md index b4ec884cdb..be61903bb2 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/domains/collection/overview.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/domains/collection/overview.md @@ -6,18 +6,18 @@ sidebar_position: 20 # 0.Collection Job Group -The **5.Domains > 0.Collection** Job Group collects the data which will be further analyzed in order -to provide details on domains, sites, and trusts. +The **5.Domains > 0.Collection** Job Group collects the data for further analysis to provide details +on domains, sites, and trusts. ![0.Collection Job Group](/images/accessanalyzer/12.0/solutions/activedirectory/domains/collection/collectionjobstree.webp) The 0.Collection Job Group is comprised of: -- [AD_DomainControllers Job](/docs/accessanalyzer/12.0/solutions/activedirectory/domains/collection/ad_domaincontrollers.md) – Collects domain controller details which - will be further analyzed in order to provide information on domains, sites, and trusts. +- [AD_DomainControllers Job](/docs/accessanalyzer/12.0/solutions/activedirectory/domains/collection/ad_domaincontrollers.md) – Collects domain controller details for + further analysis to provide information on domains, sites, and trusts. - [AD_DSRM Job](/docs/accessanalyzer/12.0/solutions/activedirectory/domains/collection/ad_dsrm.md) – Collects data related to domain controller registry settings for the - DSRMAdminLogonBehavior key. If this key is set to 1 or 2, the DSRM Admin Account can be used to - log in to the domain controller even if it has not been started in DSRM which can present a + DSRMAdminLogonBehavior key. If this key is set to 1 or 2, the DSRM Admin Account can log in to + the domain controller even if it has not been started in DSRM, which can present a potential security vulnerability. Additional information on this registry key is available in this [Microsoft Document](https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc732714(v=ws.10)?redirectedfrom=MSDN). - [AD_TimeSync Job](/docs/accessanalyzer/12.0/solutions/activedirectory/domains/collection/ad_timesync.md) – Collects TimeSync information from the registry for each diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/domains/overview.md b/docs/accessanalyzer/12.0/solutions/activedirectory/domains/overview.md index 65406ef5b3..7a7b6f5fcf 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/domains/overview.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/domains/overview.md @@ -13,8 +13,8 @@ configurations that may leave your environment at risk. The following components comprises the 5.Domains job group: -- [0.Collection Job Group](/docs/accessanalyzer/12.0/solutions/activedirectory/domains/collection/overview.md) – Collects the data which will be further - analyzed in order to provide details on domains, sites, and trusts +- [0.Collection Job Group](/docs/accessanalyzer/12.0/solutions/activedirectory/domains/collection/overview.md) – Collects the data that this job group + analyzes to provide details on domains, sites, and trusts - [AD_DCSummary Job](/docs/accessanalyzer/12.0/solutions/activedirectory/domains/ad_dcsummary.md) – Provides operational reporting related to the details collected for each domain controller. For each domain controller, the report identifies the FSMO role, whether it is a bridgehead server, whether it is a global catalog, and the time server it @@ -24,7 +24,7 @@ The following components comprises the 5.Domains job group: domain and forest functional levels, and types and directions of trusts - [AD_DSRMSettings Job](/docs/accessanalyzer/12.0/solutions/activedirectory/domains/ad_dsrmsettings.md) – Provides details on domain controller registry settings for the DSRMAdminLogonBehavior key. If this key is set to 1 or 2, the DSRM Admin Account - can be used to log in to the domain controller even if it has not been started in DSRM which can + can log in to the domain controller even if it has not been started in DSRM, which can present a potential security vulnerability. - [AD_KerberoastingRisk Job](/docs/accessanalyzer/12.0/solutions/activedirectory/domains/ad_kerberoastingrisk.md) – Identifies accounts vulnerable to kerberoasting. Kerberoasting is a threat where attackers target service accounts in Active diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/domains/recommended.md b/docs/accessanalyzer/12.0/solutions/activedirectory/domains/recommended.md index 11954b4d04..ce660aaf43 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/domains/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/domains/recommended.md @@ -11,7 +11,7 @@ default settings. It can be run directly or scheduled. **Dependencies** -This job group does not have dependencies. +This job group doesn't have dependencies. **Targeted Hosts** @@ -50,7 +50,7 @@ entire job group, instead of the individual jobs. **Query Configuration** The 5.Domains > 0.Collection > AD_DomainControllers job should be run with the default query -configurations. Most of these queries are preconfigured for this Job Group and should not be +configurations. Most of these queries are preconfigured for this Job Group and shouldn't be modified. The following query can be modified to use a secure connection with TLS/SSL: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/grouppolicy/ad_cpassword.md b/docs/accessanalyzer/12.0/solutions/activedirectory/grouppolicy/ad_cpassword.md index 3bd3434757..b5e5be4fdb 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/grouppolicy/ad_cpassword.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/grouppolicy/ad_cpassword.md @@ -8,20 +8,20 @@ sidebar_position: 20 The AD_CPassword Job identifies passwords that are stored in Group Policy Preferences which present a security risk allowing attackers access to these passwords. Microsoft published the AES private -key, which can be used to decrypt passwords stored in Group Policy Preferences. See the Microsoft +key, which attackers can use to decrypt passwords stored in Group Policy Preferences. See the Microsoft [2.2.1.1.4 Password Encryption](https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-gppref/2c15cbf0-f086-4c74-8b70-1f2fa45dd4be) article for additional information. Since Authenticated Users have read access to SYSVOL, any malicious insider or attacker can search for the cPassword file inside XML files shared through SYSVOL to decrypt them. GPOs can be stored in the `%ProgramData%\Microsoft\Group Policy\History` -folder on each machine, meaning any results found by this job should be deleted off every computer -once this policy has been removed. +folder on each machine. After you remove this policy, delete any results this job found from every +computer. ## Query for the AD_CPassword Job The AD_CPassword Job uses the PowerShell Data Collector for the following query: :::warning -Do not modify the query. The query is preconfigured for this job +Don't modify the query. The query is preconfigured for this job ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/grouppolicy/ad_grouppolicy.md b/docs/accessanalyzer/12.0/solutions/activedirectory/grouppolicy/ad_grouppolicy.md index 2fb4cf6a82..d3361ae12e 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/grouppolicy/ad_grouppolicy.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/grouppolicy/ad_grouppolicy.md @@ -14,7 +14,7 @@ provides details on the containers they are linked to, and the settings that are The AD_GroupPolicy Job uses the GroupPolicy Data Collector for the following query: :::warning -Do not modify the queries. The queries are preconfigured for this job. +Don't modify the queries. The queries are preconfigured for this job. ::: @@ -35,7 +35,7 @@ Navigate to the **Active Directory** > **4.GroupPolicy** > **AD_GroupPolicy** > and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/grouppolicy/ad_overlappinggpos.md b/docs/accessanalyzer/12.0/solutions/activedirectory/grouppolicy/ad_overlappinggpos.md index d7b0b829d4..14d0464645 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/grouppolicy/ad_overlappinggpos.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/grouppolicy/ad_overlappinggpos.md @@ -15,7 +15,7 @@ Navigate to the **Active Directory** > **4. Group Policy** > **AD_OverlappingGPO node and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected first analysis task. The first analysis task is +Don't modify or deselect the selected first analysis task. The first analysis task is preconfigured for this job. ::: @@ -30,7 +30,7 @@ The default analysis tasks are: The following analysis tasks are deselected by default: :::note -Deselect the **Conflicting** analysis task before selecting the analysis tasks below. +Deselect the **Conflicting** analysis task before selecting the following analysis tasks. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/grouppolicy/ad_passwordpolicies.md b/docs/accessanalyzer/12.0/solutions/activedirectory/grouppolicy/ad_passwordpolicies.md index 37662dd0f4..d31fcdcfcd 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/grouppolicy/ad_passwordpolicies.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/grouppolicy/ad_passwordpolicies.md @@ -15,7 +15,7 @@ different password policies within a single domain. The AD_PasswordPolicies Job uses the LDAP Data Collector for the following query: :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -35,7 +35,7 @@ Navigate to the **Active Directory** > **4.GroupPolicy** > **AD_PasswordPolicies node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/grouppolicy/overview.md b/docs/accessanalyzer/12.0/solutions/activedirectory/grouppolicy/overview.md index 7cfce90290..108e12a4ce 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/grouppolicy/overview.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/grouppolicy/overview.md @@ -16,14 +16,14 @@ The following components comprise the 4.Group Policy Job Group: - [AD_CPassword Job](/docs/accessanalyzer/12.0/solutions/activedirectory/grouppolicy/ad_cpassword.md) – Identifies passwords that are stored in Group Policy Preferences which present a security risk allowing attackers access to these passwords. Microsoft - published the AES private key, which can be used to decrypt passwords stored in Group Policy + published the AES private key, which attackers can use to decrypt passwords stored in Group Policy Preferences. See the Microsoft [2.2.1.1.4 Password Encryption](https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-gppref/2c15cbf0-f086-4c74-8b70-1f2fa45dd4be) article for additional information. Since Authenticated Users have read access to SYSVOL, any malicious insider or attacker can search for the cPassword file inside XML files shared through SYSVOL to decrypt them. GPOs can be stored in the `%ProgramData%\Microsoft\Group Policy\History` - folder on each machine, meaning any results found by this job should be deleted off every computer - once this policy has been removed. + folder on each machine. After you remove this policy, delete any results this job found from every + computer. - [AD_GroupPolicy Job](/docs/accessanalyzer/12.0/solutions/activedirectory/grouppolicy/ad_grouppolicy.md) – Audits all Group Policies that are present on the Domain Controller, and provides details on the containers they are linked to and the settings that are configured diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/grouppolicy/recommended.md b/docs/accessanalyzer/12.0/solutions/activedirectory/grouppolicy/recommended.md index c93ba4b510..a84076c9e9 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/grouppolicy/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/grouppolicy/recommended.md @@ -11,7 +11,7 @@ settings. It can be run directly or scheduled. **Dependencies** -This job group does not have dependencies. +This job group doesn't have dependencies. **Targeted Hosts** @@ -41,7 +41,7 @@ This job group can be scheduled to run as desired. :::info Run the jobs in the 4.Group Policy Job Group together and in order by running the entire job group, instead of the individual jobs. However, these jobs can be run independently, with -the exception of the AD_OverlappingGPOs Job, which is dependent upon the AD_GroupPolicy Job for data +the exception of the AD_OverlappingGPOs Job, which depends on the AD_GroupPolicy Job for data collection. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_circularnesting.md b/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_circularnesting.md index 52b65b51a4..8ba2525ebc 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_circularnesting.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_circularnesting.md @@ -15,7 +15,7 @@ Navigate to the **Active Directory** > **1.Groups** > **AD_CircularNesting** > * and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_dclogongroups.md b/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_dclogongroups.md index 126b38572f..6f39c5c96c 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_dclogongroups.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_dclogongroups.md @@ -6,7 +6,7 @@ sidebar_position: 30 # AD_DCLogonGroups Job -The AD_DCLogonGroups Job identifies users who are able to log on to Domain Controllers through +The AD_DCLogonGroups Job identifies users who can log on to Domain Controllers through effective membership to the Enterprise Admins, Domain Admins, Administrators, Backup Operators, Account Operators, Print Operators, or Remote Desktop Users groups. This type of access should be limited to only those individuals who require this level of administrative privileges. @@ -17,7 +17,7 @@ Navigate to the **Active Directory** > **1.Groups** > **AD_DCLogonGroups** > **C select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_duplicategroups.md b/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_duplicategroups.md index 1a35b7c932..d28531a961 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_duplicategroups.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_duplicategroups.md @@ -15,7 +15,7 @@ Navigate to the **Active Directory** > **1.Groups** > **AD_DuplicateGroups** > * and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_emptygroups.md b/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_emptygroups.md index 400a619083..6b0bd950d0 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_emptygroups.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_emptygroups.md @@ -15,7 +15,7 @@ Navigate to the **Active Directory** > **1.Groups** > **AD_EmptyGroups** > **Con select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_groupprobableowners.md b/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_groupprobableowners.md index 28bb2ef58b..98040cf4aa 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_groupprobableowners.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_groupprobableowners.md @@ -6,8 +6,8 @@ sidebar_position: 60 # AD_GroupProbableOwners Job -The AD_GroupProbableOwners Job determines potential owners for Active Directory Groups which can be -used to perform automated membership reviews and enable self-service group management and membership +The AD_GroupProbableOwners Job determines potential owners for Active Directory Groups, which you can +use to perform automated membership reviews and enable self-service group management and membership requests. ## Analysis Tasks for the AD_GroupProbableOwners Job @@ -16,7 +16,7 @@ Navigate to the **Active Directory** > **1.Groups** > **AD_GroupProbableOwners** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_largestgroups.md b/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_largestgroups.md index c6b1d69945..6fe51d7c1c 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_largestgroups.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_largestgroups.md @@ -7,8 +7,8 @@ sidebar_position: 70 # AD_LargestGroups Job The AD_LargestGroups Job identifies groups with large effective member counts. These types of groups -may cause administrative overhead and burden in being able to easily understand who is getting -access to resources, or how much access is being granted to resources through these groups. +can create administrative overhead, making it hard to see who has access to resources or how much +access these groups grant. ## Analysis Task for the AD_LargestGroups Job @@ -16,7 +16,7 @@ Navigate to the **Active Directory** > **1.Groups** > **AD_LargestGroups** > **C select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_mailsecuritygroups.md b/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_mailsecuritygroups.md index 3ef9f6c6c9..9fadde48b4 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_mailsecuritygroups.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_mailsecuritygroups.md @@ -14,7 +14,7 @@ Navigate to the **Active Directory** > **1.Groups** > **AD_MailSecurityGroups** and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_nestedgroups.md b/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_nestedgroups.md index 5788cab962..09793c9629 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_nestedgroups.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_nestedgroups.md @@ -7,8 +7,8 @@ sidebar_position: 90 # AD_NestedGroups Job The AD_NestedGroups Job identifies nested groups within Active Directory and provides details such -as the levels of nesting. While Active Directory provides the ability to nest certain types of -groups within other groups, Microsoft recommends nesting does not go beyond two levels in order to +as the levels of nesting. While Active Directory lets you nest certain types of +groups within other groups, Microsoft recommends nesting doesn't go beyond two levels to avoid difficulties in understanding effective membership and access. ## Analysis Tasks for the AD_NestedGroups Job @@ -17,7 +17,7 @@ Navigate to the **Active Directory** > **1.Groups** > **AD_NestedGroups** > **Co select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_sensitivesecuritygroups.md b/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_sensitivesecuritygroups.md index 5585ab1354..ab0fe3a5b1 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_sensitivesecuritygroups.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_sensitivesecuritygroups.md @@ -17,7 +17,7 @@ Navigate to the **Active Directory** > **1.Groups** > **AD_SensitiveSecurityGrou node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_stalegroups.md b/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_stalegroups.md index b33ce94b41..5a0b87bd34 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_stalegroups.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_stalegroups.md @@ -16,7 +16,7 @@ Navigate to the **Active Directory** > **1.Groups** > **AD_StaleGroups** > **Con select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -37,4 +37,4 @@ the following pre-configured report: | Report | Description | Default Tags | Report Elements | | ------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Stale Effective Membership (A.K.A. Stale Groups) | This report identifies groups with stale effective membership. A stale user is defined as someone who has not logged into the domain in over 60 days, is expired, or currently disabled. | None | This report is comprised of three elements:
  • Bar Chart – Displays group membership
  • Table – Provides details on membership
  • Table – Provides details on group membership
| +| Stale Effective Membership (A.K.A. Stale Groups) | This report identifies groups with stale effective membership. A stale user is defined as someone who has not logged into the domain in over 60 days, is expired, or disabled. | None | This report is comprised of three elements:
  • Bar Chart – Displays group membership
  • Table – Provides details on membership
  • Table – Provides details on group membership
| diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/groups/overview.md b/docs/accessanalyzer/12.0/solutions/activedirectory/groups/overview.md index 6626322d5f..526189c710 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/groups/overview.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/groups/overview.md @@ -16,7 +16,7 @@ The following jobs comprise the 1.Groups Job Group: - [AD_CircularNesting Job](/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_circularnesting.md) – Identifies circularly nested groups within Active Directory which can pose administrative and operational challenges with identifying effective access to resources -- [AD_DCLogonGroups Job](/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_dclogongroups.md) – Identifies users who are able to log on to Domain +- [AD_DCLogonGroups Job](/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_dclogongroups.md) – Identifies users who can log on to Domain Controllers through effective membership to the Enterprise Admins, Domain Admins, Administrators, Backup Operators, Account Operators, Print Operators, or Remote Desktop Users groups. This type of access should be limited to only those individuals who require this level of administrative @@ -27,12 +27,11 @@ The following jobs comprise the 1.Groups Job Group: - [AD_EmptyGroups Job](/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_emptygroups.md) – Identifies empty and single member groups which are suitable candidates for consolidation or cleanup - [AD_GroupProbableOwners Job](/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_groupprobableowners.md) – Determines potential owners for Active - Directory Groups which can be used to perform automated membership reviews and enable self-service + Directory Groups you can use to perform automated membership reviews and enable self-service group management and membership requests - [AD_LargestGroups Job](/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_largestgroups.md) – Identifies groups with large effective member - counts. These types of groups may cause administrative overhead and burden in being able to easily - understand who is getting access to resources, or how much access is being granted to resources - through these groups. + counts. These types of groups can create administrative overhead, making it hard to see who has + access to resources or how much access these groups grant. - The definition of a large group is set by the **.Active Directory Inventory** > **3-AD_Exceptions** Job. It can be customized. See the @@ -42,9 +41,9 @@ The following jobs comprise the 1.Groups Job Group: - [AD_MailSecurityGroups Job](/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_mailsecuritygroups.md) – Identifies mail-enabled security groups within Active Directory - [AD_NestedGroups Job](/docs/accessanalyzer/12.0/solutions/activedirectory/groups/ad_nestedgroups.md) – Identifies nested groups within Active Directory and - provides details such as the levels of nesting. While Active Directory provides the ability to - nest certain types of groups within other groups, Microsoft recommends nesting does not go beyond - two levels in order to avoid difficulties in understanding effective membership and access. + provides details such as the levels of nesting. While Active Directory lets you + nest certain types of groups within other groups, Microsoft recommends nesting doesn't go beyond + two levels to avoid difficulties in understanding effective membership and access. - The definition of a deeply nested group is set by the **.Active Directory Inventory** > **3-AD_Exceptions** Job. It can be customized. See the diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/groups/recommended.md b/docs/accessanalyzer/12.0/solutions/activedirectory/groups/recommended.md index 63a9a82ec0..2c94a66e55 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/groups/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/groups/recommended.md @@ -11,16 +11,16 @@ settings. It can be run directly or scheduled. **Dependencies** -The **.Active Directory Inventory** Job Group needs to be successfully executed prior to running +The **.Active Directory Inventory** Job Group needs to be successfully executed before running this job group. **Target Host** -This job group does not collect data. No target host is required. +This job group doesn't collect data. No target host is required. **Connection Profile** -This job group does not collect data. No specific Connection Profile is required. +This job group doesn't collect data. No specific Connection Profile is required. **Schedule Frequency** @@ -50,8 +50,8 @@ Some analysis tasks have customizable parameters: - Customize within **.Active Directory Inventory** > **3-AD_Exceptions** Job analysis tasks :::note - Changes to an exception’s definition will affect all jobs dependent upon that - exception as well as all Access Information Center Exceptions reports. + Changes to an exception’s definition affect all jobs that depend on that + exception, as well as all Access Information Center Exceptions reports. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_directmembership.md b/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_directmembership.md index ae16f94261..ce11ac66ae 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_directmembership.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_directmembership.md @@ -6,7 +6,7 @@ sidebar_position: 20 # AD_DirectMembership Job -The AD_DirectMembership Job identifies users who do not have any group membership. This condition +The AD_DirectMembership Job identifies users who don't have any group membership. This condition may indicate unnecessary user accounts that are suitable candidates for review and cleanup. ## Analysis Tasks for the AD_DirectMembership Job @@ -15,7 +15,7 @@ Navigate to the **Active Directory** > **2.Users** > **AD_DirectMembership** > * and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_duplicateusers.md b/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_duplicateusers.md index ab0a3d1397..64a8c137ca 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_duplicateusers.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_duplicateusers.md @@ -16,7 +16,7 @@ Navigate to the **Active Directory** > **2.Users** > **AD_DuplicateUsers** > **C select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_orphanedusers.md b/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_orphanedusers.md index 2a4f96137d..010dca0d5f 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_orphanedusers.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_orphanedusers.md @@ -15,7 +15,7 @@ Navigate to the **Active Directory** > **2.Users** > **AD_OrphanedUsers** > **Co select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_passwordstatus.md b/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_passwordstatus.md index 18c2e95eaa..d77e49f394 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_passwordstatus.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_passwordstatus.md @@ -15,7 +15,7 @@ Navigate to the **Active Directory** > **2.Users** > **AD_PasswordStatus** > **C select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigure for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_serviceaccounts.md b/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_serviceaccounts.md index 58ec8e9a54..1c621dbe4f 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_serviceaccounts.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_serviceaccounts.md @@ -26,7 +26,7 @@ Navigate to the **Active Directory** > **2.Users** > **AD_ServiceAccounts** > ** select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_sidhistory.md b/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_sidhistory.md index 369b3728fe..8d2455606e 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_sidhistory.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_sidhistory.md @@ -17,7 +17,7 @@ Navigate to the **Active Directory** > **2.Users** > **AD_SIDHistory** > **Confi select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_staleusers.md b/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_staleusers.md index 3249482e8d..53c079f0be 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_staleusers.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_staleusers.md @@ -7,12 +7,12 @@ sidebar_position: 80 # AD_StaleUsers Job The AD_StaleUsers job identifies potentially stale users based on the amount of time since their -last login to the domain, or if the account has been disabled. These accounts should be reviewed and -cleaned up in order to increase security and reduce complexity. +last log in to the domain, or if the account has been disabled. These accounts should be reviewed and +cleaned up to increase security and reduce complexity. :::note The definition of a stale user is set by the .Active Directory Inventory solution. These -parameters, including the number of days since last login to be considered stale (by default 60 +parameters, including the number of days since last log in to be considered stale (by default 60 days), can be customized within the **.Active Directory Inventory** > **3-AD_Exceptions** job's **Stale Users** analysis task. See the [3-AD_Exceptions Job](/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/3-ad_exceptions.md) topic for additional @@ -26,7 +26,7 @@ Navigate to the **Active Directory** > **2.Users** > **AD_StaleUsers** > **Confi select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -44,4 +44,4 @@ the following pre-configured report: | Report | Description | Default Tags | Report Elements | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Stale Users | This report identifies user accounts which have not logged into the domain for an extended amount of time or are currently disabled. A user account is considered stale if the last logon is over 60 days ago, is currently disabled, or expired. | None | This report is comprised of three elements:
  • Stacked Bar Chart – Displays users by domain
  • Table – Provides details on users
  • Table – Provides details on users by domain
| +| Stale Users | This report identifies user accounts which have not logged into the domain for an extended amount of time or are disabled. A user account is considered stale if the last logon is over 60 days ago, is disabled, or expired. | None | This report is comprised of three elements:
  • Stacked Bar Chart – Displays users by domain
  • Table – Provides details on users
  • Table – Provides details on users by domain
| diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_userattributecompletion.md b/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_userattributecompletion.md index c48531545f..9b0232649a 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_userattributecompletion.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_userattributecompletion.md @@ -16,7 +16,7 @@ Navigate to the **Active Directory** > **2.Users** > **AD_UserAttributeCompletio node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_userdelegation.md b/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_userdelegation.md index 156d05fd78..0687d94dea 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_userdelegation.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_userdelegation.md @@ -8,7 +8,7 @@ sidebar_position: 100 The AD_Delegation Job highlights user accounts which are trusted for delegation. Kerberos delegation enables an application to access resources hosted on a different server, and opens up several -avenues to compromise based on the type of delegation enabled.  See the +avenues to compromise based on the type of delegation enabled. See the [What Is Kerberos Delegation?](https://blog.netwrix.com/2021/11/30/what-is-kerberos-delegation-an-overview-of-kerberos-delegation/) Netwrix blog article for more information about this configuration and the related security risks. @@ -18,7 +18,7 @@ Navigate to the **Active Directory** > **2.Users** > **AD_UserDelegation** > **C select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_usertoken.md b/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_usertoken.md index 44517ed218..6355a092e8 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_usertoken.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_usertoken.md @@ -18,7 +18,7 @@ Navigate to the **Active Directory** > **2.Users** > **AD_UserToken** > **Config select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_weakpasswords.md b/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_weakpasswords.md index f620bcd2d2..4bb060dab8 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_weakpasswords.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_weakpasswords.md @@ -19,20 +19,20 @@ dictionaries and other exceptions. Exceptions include: - Delegable Admins – Administrator account is allowed to be delegated to a service - DES Encryption Only – Account is using Kerberos DES encryption. DES encryption is considered weak as the 56-bit key is prone to brute force attacks. See the Microsoft - [AD DS: User accounts and trusts in this domain should not be configured for DES only](https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ff646918(v=ws.10)) + [AD DS: User accounts and trusts in this domain shouldn't be configured for DES only](https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ff646918(v=ws.10)) article for additional information. - Empty Password – Account has an empty password -- Kerberos Pre-authentication is not required – Account does not require Kerberos +- Kerberos Pre-authentication isn't required – Account doesn't require Kerberos pre-authentication. Kerberos pre-authentication can mitigate against brute force attacks. See the Microsoft - [Kerberos Pre-Authentication: Why It Should Not Be Disabled](https://learn.microsoft.com/en-us/archive/technet-wiki/23559.kerberos-pre-authentication-why-it-should-not-be-disabled) + [Kerberos Pre-Authentication: Why It Shouldn't Be Disabled](https://learn.microsoft.com/en-us/archive/technet-wiki/23559.kerberos-pre-authentication-why-it-should-not-be-disabled) article for additional information. - LM Hash – Account has stored LM hashes. The LM hash is a relatively weak hash that is prone to brute force attacks. See the Microsoft [How to prevent Windows from storing a LAN manager hash of your password in Active Directory and local SAM databases](https://learn.microsoft.com/en-US/troubleshoot/windows-server/windows-security/prevent-windows-store-lm-hash-password) article for additional information. - Password Never Expires – Account has a password that never expires -- Password Not Required – Account does not require a password +- Password Not Required – Account doesn't require a password - Weak Historical Password – Account has a historical password that was found in the dictionary - Weak Password – Account has a password that was found in the dictionary - Shares Common Password – Account shares a password with another account @@ -53,8 +53,8 @@ The query for this job are: ### Configure the Weak Passwords Query -The PasswordSecurity Data Collector can be scoped if desired. Follow the steps to modify the query -configuration. +The PasswordSecurity Data Collector can be scoped if desired. To modify the query configuration, +complete the following steps. **Step 1 –** Navigate to the job’s Configure node and select Queries. @@ -67,7 +67,7 @@ Collector Wizard opens. ![Password Security Data Collection Wizard Scan options page](/images/accessanalyzer/12.0/solutions/activedirectory/users/optionsweakpassword.webp) :::warning -Read the warning prior to enabling the cleartext password feature. +Read the warning before enabling the cleartext password feature. ::: @@ -95,7 +95,7 @@ Navigate to the **Active Directory** > **2.Users** > **AD_WeakPasswords** > **Co select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/users/overview.md b/docs/accessanalyzer/12.0/solutions/activedirectory/users/overview.md index 6ba5f375ff..a41d8e4e7d 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/users/overview.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/users/overview.md @@ -13,7 +13,7 @@ concern such as weak passwords, user token size, or stale users. The following components comprise the 2.Users Job Group: -- [AD_DirectMembership Job](/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_directmembership.md) – Identifies users who do not have any group +- [AD_DirectMembership Job](/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_directmembership.md) – Identifies users who don't have any group membership. This condition may indicate unnecessary user accounts that are suitable candidates for review and cleanup. - [AD_DuplicateUsers Job](/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_duplicateusers.md) – Identifies multiple user accounts which may be @@ -31,8 +31,8 @@ The following components comprise the 2.Users Job Group: include when a user has a historical SID from their current domain, or when a non-admin user has a historical SID with administrative rights, both of which may be indicators of compromise. - [AD_StaleUsers Job](/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_staleusers.md) – Identifies potentially stale users based on the amount of - time since their last login to the domain, or if the account has been disabled. These accounts - should be reviewed and cleaned up in order to increase security and reduce complexity. + time since their last log in to the domain, or if the account has been disabled. These accounts + should be reviewed and cleaned up to increase security and reduce complexity. - [AD_UserAttributeCompletion Job](/docs/accessanalyzer/12.0/solutions/activedirectory/users/ad_userattributecompletion.md) – Identifies which attributes are present within User fields in Active Directory, and which ones are blank for a majority of objects. This may indicate accounts within Active Directory which are lacking appropriate diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/users/recommended.md b/docs/accessanalyzer/12.0/solutions/activedirectory/users/recommended.md index 7a8c702563..18b709263d 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/users/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/users/recommended.md @@ -7,15 +7,14 @@ sidebar_position: 10 # Recommended Configurations for the 2.Users Job Group The **Active Directory** > **2.Users** Job Group has been configured by default to run with the -out-of-the-box settings. It can be run directly or scheduled. +default settings. It can be run directly or scheduled. **Dependencies** -- The **.Active Directory Inventory** Job Group needs to be successfully executed prior to running - this job group +- Successfully run the **.Active Directory Inventory** Job Group before running this job group. - - For the **AD_ServiceAccounts** Job, the **.Active Directory Inventory** > **1-AD_Scan** Job - needs to be configured to collect **servicePrincipalName** as a Custom Attribute + - For the **AD_ServiceAccounts** Job, configure the **.Active Directory Inventory** > + **1-AD_Scan** Job to collect **servicePrincipalName** as a Custom Attribute - For the **AD_WeakPassword** Job: @@ -26,12 +25,12 @@ out-of-the-box settings. It can be run directly or scheduled. topic for additional information. :::info - If this job is not to be used, disable the job to prevent execution when the - job group is executed. + If you don't need this job, disable it to prevent it from running with the + job group. ::: -**Targeted Host(s)** +**Targeted Hosts** Only the **AD_WeakPasswords** Job requires a host list. The host list assignment has been configured under the **2. Users** > **AD_WeakPasswords** > **Configure** > **Hosts** node. It is set to target @@ -53,9 +52,8 @@ additional information. **Schedule Frequency** The data analyzed by the **2.Users** Job Group jobs is collected by the **.Active Directory -Inventory** Job Group. Therefore, it is recommended to schedule these jobs to run after the -**.Active Directory Inventory** job group collection has completed. These jobs can be scheduled to -run as desired. +Inventory** Job Group. Therefore, schedule these jobs to run after the **.Active Directory +Inventory** job group collection finishes. These jobs can be scheduled to run as desired. **Run at the Job Group Level** @@ -63,7 +61,7 @@ Run the jobs in the **2.Users** Job Group together and in order by running the e instead of the individual jobs. :::tip -Remember, if the **AD_WeakPassword** Job is not to be executed, it can be disabled. +If you don't need to run the **AD_WeakPassword** Job, disable it. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/1-ad_scan.md b/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/1-ad_scan.md index d79856e843..01b09fe1be 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/1-ad_scan.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/1-ad_scan.md @@ -8,7 +8,7 @@ sidebar_position: 20 The 1-AD_Scan Job collects data from Active Directory. In most environments, this job requires no additional customizations before running it. Optionally, the job can be configured to scope scan -options and to collect custom attributes. For enable SSL encryption for communication with Active +options and to collect custom attributes. To enable SSL encryption for communication with Active Directory, see the [Enable SSL Option](#enable-ssloption) topic for additional information. ## Queries for the 1-AD Scan Job @@ -21,14 +21,14 @@ The 1-AD_Scan Job uses the ADInventory Data Collector for the following query: objects - This query can be modified. See the - [Customize the 1-AD_Scan Query](#customize-the-1-ad_scan-query) topic for additional + [Customize the 1-AD_Scan Query](#customize-the-1-adscan-query) topic for additional information. ### Customize the 1-AD_Scan Query The 1-AD_Scan Job has been preconfigured to run with the default settings with the category of Scan -Active Directory. Follow the steps to set any desired customizations to scan options or to collect -custom attributes. +Active Directory. To set any customizations to scan options or to collect +custom attributes, complete the following steps. **Step 1 –** Navigate to the **.Active Directory Inventory** > **1-AD_Scan** > **Configure** node and select **Queries**. @@ -40,8 +40,7 @@ opens. DC Wizard opens. :::warning -Do not make changes to other wizard pages as they have been pre-configured for the -purpose of this job. +Don't make changes to other wizard pages. They're preconfigured for this job. ::: @@ -67,8 +66,8 @@ topic for additional information. click **Cancel** if no changes were made. Then click **OK** to close the Query Properties window. :::note -In order for the Access Information Center to populate NFS permissions within File System -reports, the .Active Directory Inventory Job Group must be configured to collect the **uid** and +For the Access Information Center to populate NFS permissions within File System +reports, configure the .Active Directory Inventory Job Group to collect the **uid** and **uidNumber** attributes for Users. See the [NFS Permissions for the AIC ](#nfs-permissions-for-the-aic) topic for additional information. ::: @@ -76,7 +75,7 @@ reports, the .Active Directory Inventory Job Group must be configured to collect The 1-AD_Scan Job is now ready to run with the customized settings. If any custom attributes are added to the data collection, the **Create Extended Attributes View** analysis task can be enabled -in order to have visibility into the collected data. +to have visibility into the collected data. ## Analysis Tasks for the 1-AD_Scan Job @@ -84,7 +83,7 @@ View the analysis tasks by navigating to the **.Active Directory Inventory** > * **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -123,14 +122,14 @@ topic, the 1-AD_Scan Job produces the following pre-configured report: ## NFS Permissions for the AIC -In order for the Access Information Center to populate NFS resources within all File System -permissions and resource audit reports, the .Active Directory Inventory Job Group must be configured +For the Access Information Center to populate NFS resources within all File System +permissions and resource audit reports, configure the .Active Directory Inventory Job Group to collect the following custom attributes for Users: - uid - uidNumber -Follow the steps to add the custom attributes. +To add the custom attributes, complete the following steps. **Step 1 –** Navigate to the Active Directory Inventory DC Wizard for the AD Inventory Query within the 1-AD_Scan Job. @@ -141,8 +140,8 @@ the 1-AD_Scan Job. option is deselected. :::note -Whenever query configurations are modified, it is necessary to do a full scan. After the -first full scan, differential scanning can be re-enabled. +Whenever you modify query configurations, run a full scan. After the +first full scan, you can re-enable differential scanning. ::: @@ -175,7 +174,7 @@ The .Active Directory Inventory Job Group is now collecting attributes required visible within the Access Information Center. :::tip -Remember, it is necessary to re-enable differential scanning after Step 5 if desired. +Remember to re-enable differential scanning after Step 5 if desired. ::: @@ -185,7 +184,7 @@ for additional information. ## Enable SSL Option -Follow the steps to enable SSL encryption for communications with Active Directory: +To enable SSL encryption for communications with Active Directory, complete the following steps: **Step 1 –** Navigate to the **1-AD_Scan > Configure** node and select **Queries**. diff --git a/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/2-ad_changes.md b/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/2-ad_changes.md index ca1096b64b..711a825ebf 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/2-ad_changes.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/2-ad_changes.md @@ -8,12 +8,12 @@ sidebar_position: 30 The 2-AD_Changes Job tracks changes within all scanned domains. Reports in the job highlight Active Directory changes which have occurred since the last time the .Active Directory Inventory Job Group -was run. It is dependent on the running of the 1-AD_Scan Job, also located in the .Active Directory +was run. It is dependent on running the 1-AD_Scan Job, also located in the .Active Directory Inventory Job Group. The 1-AD_Scan Job must have the Query Option to **Track changes into Change tracking tables** -selected in order for the Analysis Tasks in the 2-AD_Changes Job to work. See Step 4 of the -[Customize the 1-AD_Scan Query](1-ad_scan.md#customize-the-1-ad_scan-query) topic for additional +selected for the Analysis Tasks in the 2-AD_Changes Job to work. See Step 4 of the +[Customize the 1-AD_Scan Query](1-ad_scan.md#customize-the-1-adscan-query) topic for additional information. ## Analysis Tasks for the 2-AD_Changes Job @@ -22,7 +22,7 @@ View the analysis tasks by navigating to the **.Active Directory Inventory** > * **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -113,7 +113,7 @@ following analysis tasks are deselected by default: Notification must have recipients configured for the analysis task. Optionally, the email subject and body can be modified. See the -[Notification Analysis Tasks for the 2-AD_Changes Job](#notification-analysis-tasks-for-the-2-ad_changes-job) +[Notification Analysis Tasks for the 2-AD_Changes Job](#notification-analysis-tasks-for-the-2-adchanges-job) topic for additional information. In addition to the tables and views created by the analysis tasks, the 2-AD_Changes Job produces the @@ -125,32 +125,32 @@ following pre-configured reports: | Group Membership Changes (A.K.A. Most Active Groups) | This report tracks group membership changes in Active Directory. | None | This report is comprised of three elements:
  • Bar graph – Displays Most Active Groups (Past 24 Hours)
  • Table – Provides details on the most active groups (Past 24 Hours)
  • Table – Provides details on the most active groups
| | New Principals | This report identifies when principals have been created on the targeted domains. | None | This report is comprised of two elements:
  • Bar graph – Displays New Principals by Domain (Past 24 Hours)
  • Table – Provides details on the new principals by domain
| | Object Moves | This report tracks object moves in Active Directory. | None | This report is comprised of two elements:
  • Table – Displays Most Active OUs (Past 24 Hours)
  • Table – Provides details on the most active OUs
| -| Org Changes (A.K.A. Organizational Changes) | This report tracks organizational moves such as manager, title or department changes. | None | This report is comprised of three elements:
  • Bar graph – Displays Organizational Changes (Past 24 Hours)
  • Table – Provides details on organizational changes (Past 24 Hours)
  • Table – Provides details on the organizational changes
| +| Org Changes (A.K.A. Organizational Changes) | This report tracks organizational moves such as manager, title, or department changes. | None | This report is comprised of three elements:
  • Bar graph – Displays Organizational Changes (Past 24 Hours)
  • Table – Provides details on organizational changes (Past 24 Hours)
  • Table – Provides details on the organizational changes
| | Principal Deletions (A.K.A. Past 24 Hours) | This report identifies when principals have been deleted from the targeted domains. | None | This report is comprised of three elements:
  • Bar graph – Displays Deleted Principals by Domain (Past 24 Hours)
  • Table – Provides details on deleted principals by domain (Past 24 Hours)
  • Table – Provides details on the principals by domain
| | User Account Status Changes | This report tracks user account status changes. | None | This report is comprised of three elements:
  • Bar graph – Displays User Account Control Changes (Past 24 Hours)
  • Table – Provides details on user account control changes (Past 24 Hours)
  • Table – Provides details on the user account control changes
| ### Notification Analysis Tasks for the 2-AD_Changes Job -In order for Access Analyzer to send email notifications, it is necessary for the **Settings** > -**Notification** node to be properly configured. See the +To send email notifications, properly configure the **Settings** > +**Notification** node. See the [Notification](/docs/accessanalyzer/12.0/admin/settings/notification.md) topic for instructions on enabling the Access Analyzer Console to send email notifications. Once email notifications have been enabled, the -individual notification analysis tasks can be configured and enabled. Follow the steps to configure -a notification analysis task. +individual notification analysis tasks can be configured and enabled. To configure +a notification analysis task, complete the following steps. **Step 1 –** Navigate to the **.Active Directory Inventory** > **2-AD_Changes** > **Configure** node and select **Analysis**. ![Notification Analysis Tasks for the 2-AD_Changes Job](/images/accessanalyzer/12.0/solutions/activedirectoryinventory/changesanalysisnotification.webp) -**Step 2 –** In the Analysis Selection view, select the desired notification analysis task and click +**Step 2 –** In the Analysis Selection view, select the notification analysis task you want and click **Analysis Configuration**. The Notification Data Analysis Module opens. ![Notification Data Analysis Module SMTP properties page](/images/accessanalyzer/12.0/solutions/activedirectoryinventory/notificationanalysissmtp.webp) :::warning -Do not make changes to the pages preceding the SMTP page. +Don't make changes to the pages preceding the SMTP page. ::: @@ -169,9 +169,9 @@ provided. You can use the following options: ![Message section of SMTP properties page](/images/accessanalyzer/12.0/solutions/activedirectoryinventory/notificationanalysissmtpmessage.webp) -**Step 5 –** In the Message section, edit the **Subject**. It is not recommended to remove any -parameters. Then, customize the email content in the textbox to provide an explanation of the -notification to the recipients. +**Step 5 –** In the Message section, edit the **Subject**. Don't remove any parameters. Then, +customize the email content in the textbox to provide an explanation of the notification to the +recipients. **Step 6 –** Click **Next** to save these configuration changes and navigate to the Summary page. Do not make changes to any other pages. Click **Finish**. The Notification Data Analysis Module window diff --git a/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/3-ad_exceptions.md b/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/3-ad_exceptions.md index b6578e3397..ae2683f8c2 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/3-ad_exceptions.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/3-ad_exceptions.md @@ -12,7 +12,7 @@ running the 1-AD_Scan Job, also located in the .Active Directory Inventory Job G ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/12.0/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -28,7 +28,7 @@ The 3-AD_Exceptions Job has the following configurable parameters: - List of administrative groups See the -[Customize Analysis Parameters for the 3-AD_Exceptions Job](#customize-analysis-parameters-for-the-3-ad_exceptions-job) +[Customize Analysis Parameters for the 3-AD_Exceptions Job](#customize-analysis-parameters-for-the-3-adexceptions-job) topic for additional information. ## Analysis Tasks for the 3-AD_Exceptions Job @@ -38,7 +38,7 @@ View the analysis tasks by navigating to the **.Active Directory Inventory** > * the security concerns within them can be modified. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/overview.md b/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/overview.md index b7d92961b8..336a527fdd 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/overview.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/overview.md @@ -6,7 +6,7 @@ sidebar_position: 10 # .Active Directory Inventory Solution -Active Directory (AD) acts as the central nervous system of any Microsoft environment and plays a +Active Directory (AD) is the core identity infrastructure of any Microsoft environment and plays a vital role in granting access to resources such as Exchange, File Systems, SharePoint, and SQL Server. The .Active Directory Inventory Solution is designed to provide essential user, group membership, and computer details from the targeted domains to many Access Analyzer built-in @@ -50,14 +50,13 @@ Inventory Job Group. The .Active Directory Inventory Solution is a core component of all Access Analyzer installations. Typically this solution is instantiated during installation, but it can be installed from the -Instant Job Wizard. Once it has been installed into the Jobs tree, navigate to the solution: -**Jobs** > **.Active Directory Inventory**. This group has been named in such a way to keep it at -the top of the Jobs tree. +Instant Job Wizard. After it has been installed into the Jobs tree, navigate to the solution: +**Jobs** > **.Active Directory Inventory**. This group's name keeps it at the top of the Jobs tree. ## Jobs -This Job Group is comprised of three jobs that collect, analyze, and report on data. The data -collection is conducted by the ADInventory Data Collector. See the +This Job Group is comprised of three jobs that collect, analyze, and report on data. The +ADInventory Data Collector performs the data collection. See the [Standard Reference Tables & Views for the ADInventory Data Collector](/docs/accessanalyzer/12.0/admin/datacollector/adinventory/standardtables.md) topic for database table information. diff --git a/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/recommended.md b/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/recommended.md index bfa25c9ab4..19a0f7535d 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/recommended.md @@ -7,12 +7,12 @@ sidebar_position: 10 # Recommended Configurations for the .Active Directory Inventory Solution The .Active Directory Inventory Solution has been configured by default to run with the -out-of-the-box settings, but some settings are optional for configuration. It can be run directly or +default settings, but some settings are optional for configuration. It can be run directly or scheduled. **Dependencies** -This job group does not have dependencies. +This job group doesn't have dependencies. **Targeted Hosts** @@ -53,11 +53,11 @@ Schedule the .Active Directory Inventory Job Group to run once a day. If there are frequent AD changes within the target environment, then it can be executed more often. -It is best to rerun it anytime AD changes might have occurred. +Rerun it whenever AD changes occur. **Run at the Solution Level** -The jobs in the .Active Directory Inventory Job Group should be run together and in order by running +Run the jobs in the .Active Directory Inventory Job Group together and in order by running the entire solution, instead of the individual jobs. **Query Configuration** @@ -90,6 +90,6 @@ when targeting multiple domains. **Step 2 –** Set a Connection Profile. -**Step 3 –** chedule the .Active Directory Inventory Job Group to run as desired. +**Step 3 –** Schedule the .Active Directory Inventory Job Group to run as desired. **Step 4 –** Review the reports generated by the .Active Directory Inventory Job Group. diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/ad_brokeninheritance.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/ad_brokeninheritance.md index 73f0ac69d4..8388f4b6be 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/ad_brokeninheritance.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/ad_brokeninheritance.md @@ -19,7 +19,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **6.BrokenInheritanc **AD_BrokenInheritance** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/ad_openaccess.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/ad_openaccess.md index decee2f36c..4f7a26376c 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/ad_openaccess.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/ad_openaccess.md @@ -20,7 +20,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **5.Open Access** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/ad_oupermissions.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/ad_oupermissions.md index ab86a4fd3f..92e750066c 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/ad_oupermissions.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/ad_oupermissions.md @@ -19,7 +19,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **3.OUs** > **AD_OUP **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -34,7 +34,7 @@ The default analysis tasks are: downstream analysis and report generation - Shadow Access OU Paths – Calculates the object location and permissions for shadow access - OU Ownership – Lists the owners of each OU and determines if they are a non-standard owner. - Principals that are not administrators are considered non-standard owners of OU objects. Creates + Principals that aren't administrators are considered non-standard owners of OU objects. Creates the SA_AD_OUOwnership_Details table accessible under the job’s Results node. - OU Ownership Summary – Summarizes owner type by domain diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/ad_shadowaccess.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/ad_shadowaccess.md index a068b08e9b..009a6b205e 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/ad_shadowaccess.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/ad_shadowaccess.md @@ -33,7 +33,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **AD_ShadowAccess** and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks, with the exception of the +Don't modify or deselect the selected analysis tasks, with the exception of the **Calculate Shadow Access** analysis tasks. The analysis tasks are preconfigured for this job. The **Calculate Shadow Access** analysis task is the only analysis task that has customizable parameters. @@ -55,7 +55,7 @@ The default analysis tasks are: Results node - This Analysis Task has configurable parameters. See the - [Configure the Analysis Tasks for the AD_ShadowAccess Job](#configure-the-analysis-tasks-for-the-ad_shadowaccess-job) + [Configure the Analysis Tasks for the AD_ShadowAccess Job](#configure-the-analysis-tasks-for-the-adshadowaccess-job) topic for additional information. - Shadow Access Paths Cleanup – Removes calculated rows that are no longer used @@ -70,7 +70,7 @@ the following pre-configured reports. See the -[Report Functions for the AD_ShadowAccess Job](#report-functions-for-the-ad_shadowaccess-job) topic +[Report Functions for the AD_ShadowAccess Job](#report-functions-for-the-adshadowaccess-job) topic for additional information. ### Customizable Analysis Tasks for the AD_ShadowAccess Job @@ -88,15 +88,15 @@ The default values for customizable parameters are: | @disabled | 0 | Set to 0 to ignore disabled users | | See the -[Configure the Analysis Tasks for the AD_ShadowAccess Job](#configure-the-analysis-tasks-for-the-ad_shadowaccess-job) +[Configure the Analysis Tasks for the AD_ShadowAccess Job](#configure-the-analysis-tasks-for-the-adshadowaccess-job) topic for additional information. ### Configure the Analysis Tasks for the AD_ShadowAccess Job Customizable parameters enable Access Analyzer users to set the values used to classify user and group objects during this job’s analysis. The parameters can be customized and are listed in a -section at the bottom of the SQL Script Editor. Follow the steps to customize an analysis task’s -parameters. +section at the bottom of the SQL Script Editor. To customize an analysis task’s +parameters, complete the following steps. **Step 1 –** Navigate to the **Active Directory Permissions Analyzer** > **AD_ShadowAccess** > **Configure** node and select **Analysis** to view analysis tasks. @@ -109,12 +109,12 @@ then click **Analysis Configuration**. The SQL Script Editor opens. ![SQL Script Editor](/images/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/shadowaccesssqlscripteditor.webp) **Step 3 –** In the parameters section at the bottom of the editor, find the Value column. -Double-click on the current value and change as desired. +Double-click the current value and change as desired. - If the variable type is a table, select the cell and click **Edit Table** to modify the value. :::warning -Do not change any parameters where the Value states `Created during execution`. +Don't change any parameters where the Value states `Created during execution`. ::: @@ -154,7 +154,7 @@ domain and sensitive data. The last report element displays information on potential attack paths for users found in the targeted domain. Clicking on the green plus sign next to an attack path will open an Attack Path -window that displays a step-by-step process of how a user object, if compromised, can be used to +window that displays a step-by-step process of how an attacker can use a compromised user object to conduct a shadow attack. ![Attack Path window example](/images/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/shadowaccessreport3.webp) diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_certificaterights.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_certificaterights.md index 6097f52ef3..81c06aee9a 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_certificaterights.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_certificaterights.md @@ -14,7 +14,7 @@ objects within the targeted domains. The AD_CertificateRights job uses the ADPermissions data collector for the following query: :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -31,7 +31,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **0.Collection** > **AD_CertificateRights** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_computerrights.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_computerrights.md index 7c6285b2fe..05d272a18d 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_computerrights.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_computerrights.md @@ -14,7 +14,7 @@ Active Directory. The AD_ComputerRights Job uses the ADPermissions Data Collector for the following query: :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -31,7 +31,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **0.Collection** > **AD_ComputerRights** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_containerrights.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_containerrights.md index 037f16d9ce..b826339053 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_containerrights.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_containerrights.md @@ -14,7 +14,7 @@ Active Directory. The AD_ContainerRights Job uses the ADPermissions Data Collector for the following query: :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -31,7 +31,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **0.Collection** > **AD_ContainerRights** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_domainrights.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_domainrights.md index 80ab8ae1a7..46008e2a45 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_domainrights.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_domainrights.md @@ -14,7 +14,7 @@ Active Directory. The AD_DomainRights Job uses the ADPermissions Data Collector for the following query: :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -31,7 +31,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **0.Collection** > * **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_grouprights.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_grouprights.md index 47f70088d8..4287f0b5ec 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_grouprights.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_grouprights.md @@ -14,7 +14,7 @@ Directory. The AD_GroupRights Job uses the ADPermissions Data Collector for the following query: :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -31,7 +31,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **0.Collection** > * **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_ourights.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_ourights.md index 42d68b1a2f..1900bbbe64 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_ourights.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_ourights.md @@ -14,7 +14,7 @@ in Active Directory. The AD_OURights Job uses the ADPermissions Data Collector for the following query: :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -31,7 +31,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **0.Collection** > * **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_siterights.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_siterights.md index 8f0c732381..8de97f0429 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_siterights.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_siterights.md @@ -14,7 +14,7 @@ Directory. The AD_SiteRights Job uses the ADPermissions Data Collector for the following query: :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -31,7 +31,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **0.Collection** > * **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_userrights.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_userrights.md index 2b1998627f..c520c91880 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_userrights.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_userrights.md @@ -14,7 +14,7 @@ Directory. The AD_UserRights Job uses the ADPermissions Data Collector for the following query: :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -31,7 +31,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **0.Collection** > * **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/overview.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/overview.md index 1111e2ce72..c36a762cbc 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/overview.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/overview.md @@ -24,7 +24,7 @@ The jobs in the 0.Collection job group are: domain objects within the targeted domains - [AD_GroupRights Job](/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_grouprights.md) – Collects all Active Directory permissions applied to group objects within the targeted domains -- [AD_OURights Job](/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_ourights.md) – Collects all Active Directory permissions applied to group +- [AD_OURights Job](/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_ourights.md) – Collects all Active Directory permissions applied to organizational unit objects within the targeted domains - [AD_SiteRights Job](/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/collection/ad_siterights.md) – Collects all Active Directory permissions applied to site objects within the targeted domains diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/computers/ad_computerpermissions.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/computers/ad_computerpermissions.md index 657cdebb1c..d63db93a73 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/computers/ad_computerpermissions.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/computers/ad_computerpermissions.md @@ -15,7 +15,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **4.Computers** > **AD_ComputerPermissions** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -29,7 +29,7 @@ The default analysis tasks are: - Summarize computer object permissions – Creates an interim processing table in the database for use by downstream analysis and report generation - Computer Ownership – Lists the owners of each computer object and determines if they are a - non-standard owner. Users that are not administrators are considered non-standard owners of + non-standard owner. Users that aren't administrators are considered non-standard owners of computer objects. Creates the SA_AD_ComputerOwnership_Details table accessible under the job’s Results node. - Computer Ownership Summary – Summarizes owner type by domain diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/computers/ad_lapspermissions.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/computers/ad_lapspermissions.md index 02564a67b8..262a1cf883 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/computers/ad_lapspermissions.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/computers/ad_lapspermissions.md @@ -15,7 +15,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **4.Computers** > **AD_LAPSPermissions** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/containers/ad_adminsdholder.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/containers/ad_adminsdholder.md index 05ece97a15..2254a5bcfe 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/containers/ad_adminsdholder.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/containers/ad_adminsdholder.md @@ -15,7 +15,7 @@ Container in Active Directory. The AD_AdminSDHolder Job uses the PowerShell Data Collector for the following query: :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -32,7 +32,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **7.Containers** > **AD_AdminSDHolder** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/containers/ad_containerpermissions.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/containers/ad_containerpermissions.md index 2c2b5572d1..fecfd5e230 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/containers/ad_containerpermissions.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/containers/ad_containerpermissions.md @@ -6,7 +6,7 @@ sidebar_position: 20 # AD_ContainerPermissions Job -The AD_ContainerPermissions Job is responsible for reporting on all Active Directory permissions +The AD_ContainerPermissions Job reports on all Active Directory permissions applied to container objects within the targeted domains. ## Analysis Tasks for the AD_ContainerPermissions Job @@ -15,7 +15,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **7.Containers** > **AD_ContainerPermissions** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/containers/overview.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/containers/overview.md index 7e2c595958..634b20249d 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/containers/overview.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/containers/overview.md @@ -15,7 +15,7 @@ The jobs in the 7.Containers Job Group are: - [AD_AdminSDHolder Job](/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/containers/ad_adminsdholder.md) – Reports on all non-default Active Directory permissions applied to the AdminSDHolder container within the targeted domains. The AdminSDHolder - container can be leveraged by an attacker to create persistence within the environment. See the + container can be used by an attacker to create persistence within the environment. See the Microsoft [AdminSDHolder, Protected Groups and SDPROP](https://technet.microsoft.com/en-us/library/2009.09.sdadminholder.aspx) article for additional information. diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/domains/ad_certificateauthorityrights.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/domains/ad_certificateauthorityrights.md index dd9633f776..24c98041ff 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/domains/ad_certificateauthorityrights.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/domains/ad_certificateauthorityrights.md @@ -16,7 +16,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **8.Domains** > tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -38,4 +38,4 @@ job produces the following pre-configured report. | Report | Description | Default Tags | Report Elements | | ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Enrollment Permissions | This report highlights vulnerable Access control Lists (ACLs) with permissions or owners assigned to open groups and non-standard ACLs with owners that are not domain or enterprise admins. | None | This report is comprised of three elements:
  • Bar Chart – Displays risky permissions by principal
  • Pie Chart – Displays risky permissions by count
  • Table – Provides details on risky permissions
| +| Enrollment Permissions | This report highlights vulnerable Access control Lists (ACLs) with permissions or owners assigned to open groups and non-standard ACLs with owners that aren't domain or enterprise admins. | None | This report is comprised of three elements:
  • Bar Chart – Displays risky permissions by principal
  • Pie Chart – Displays risky permissions by count
  • Table – Provides details on risky permissions
| diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/domains/ad_certificatetemplates.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/domains/ad_certificatetemplates.md index effa7f145d..77cec4302c 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/domains/ad_certificatetemplates.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/domains/ad_certificatetemplates.md @@ -14,7 +14,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **8.Domains** > **AD_CertificateTemplates** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/domains/ad_certificatevulnerabilities.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/domains/ad_certificatevulnerabilities.md index ff442e3623..28a4ad3cf0 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/domains/ad_certificatevulnerabilities.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/domains/ad_certificatevulnerabilities.md @@ -16,7 +16,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **8.Domains** > tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: @@ -30,7 +30,7 @@ The default analysis task is: - SubjectAltName Allows Privilege Escalation (ESC1) - Defined EKUs Allow Arbitrary Certificate Signing (ESC2) - - Certificates in Combination can be used for Arbitrary Privilege Escalation (ESC3) + - Certificates in Combination Allow Arbitrary Privilege Escalation (ESC3) - Exploitable Access Control Entries on Templates (ESC4) - Public Key Infrastructure Misconfigurations (ESC5) - EDITF_ATTRIBUTESUBJECTALTNAME2 Allows Privilege Escalation (ESC6) diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/domains/ad_domainpermissions.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/domains/ad_domainpermissions.md index 715b858e04..6cb13c2785 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/domains/ad_domainpermissions.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/domains/ad_domainpermissions.md @@ -15,7 +15,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **8.Domains** > **AD_DomainPermissions** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/domains/ad_domainreplication.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/domains/ad_domainreplication.md index f9fedb2e4e..953e68e371 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/domains/ad_domainreplication.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/domains/ad_domainreplication.md @@ -15,7 +15,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **8.Domains** > **AD_DomainReplication** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/groups/ad_groupmembershippermissions.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/groups/ad_groupmembershippermissions.md index a7bfb21290..b35c19e089 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/groups/ad_groupmembershippermissions.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/groups/ad_groupmembershippermissions.md @@ -16,7 +16,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **2.Groups** > tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/groups/ad_grouppermissions.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/groups/ad_grouppermissions.md index f36f60be71..d7892efa7b 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/groups/ad_grouppermissions.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/groups/ad_grouppermissions.md @@ -15,7 +15,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **2.Groups** > **AD_ **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -29,7 +29,7 @@ The default analysis tasks are: - Summarize group object permissions – Creates an interim processing table in the database for use by downstream analysis and report generation - Group Ownership – Lists the owners of each group object and determines if they are a non-standard - owner. Principals that are not administrators are considered non-standard owners of group objects. + owner. Principals that aren't administrators are considered non-standard owners of group objects. - Group Ownership Summary – Summarizes owner type by domain In addition to the tables and views created by the analysis tasks, the AD_GroupPermissions job diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/overview.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/overview.md index c739d5975d..a4c836a4ec 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/overview.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/overview.md @@ -6,9 +6,9 @@ sidebar_position: 50 # Active Directory Permissions Analyzer Solution -The Access Analyzer Active Directory Permissions Analyzer Solution enables organizations to easily -and automatically determine effective permissions applied to any and all Active Directory (AD) -objects. AD, Security, and Network Administrators can easily browse and compare information from +The Access Analyzer Active Directory Permissions Analyzer Solution enables organizations to +automatically determine effective permissions applied to all Active Directory (AD) +objects. AD, Security, and Network Administrators can browse and compare information from individual or multiple domains using comprehensive, preconfigured analyses and reports focused on permissions associated with AD domains, organizational units, groups, users, and computers. These capabilities enable them to obtain the most authoritative view of who has access to what in AD. @@ -42,8 +42,8 @@ installed from the Instant Job Wizard, see the [Instant Job Wizard](/docs/accessanalyzer/12.0/admin/jobs/instantjobs/overview.md) topic for additional information. When purchased separately, the Permissions Analyzer Solution is installed into the Jobs tree with the Active Directory instant solution. The license limits the solution to just the **Jobs** > -**Active Directory Permissions Analyzer** Job Group. Once installed into the Jobs tree, navigate to -the solution: **Jobs** > **Active Directory Permissions Analyzer**. The 0.Collection Job Group +**Active Directory Permissions Analyzer** Job Group. After you install the solution into the Jobs tree, navigate to +it: **Jobs** > **Active Directory Permissions Analyzer**. The 0.Collection Job Group collects the data. The other job groups run analysis on the collected data and generate reports. ## Job Groups @@ -72,8 +72,8 @@ The job groups and jobs in the Active Directory Permissions Analyzer Solution ar - [4.Computers Job Group](/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/computers/overview.md) – Reports on all Active Directory permissions applied to computer objects within the targeted domains - [5.Open Access > AD_OpenAccess Job](/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/ad_openaccess.md) – Reports on all Active Directory - permissions granting open access within the targeted domains. Open Access can be defined as access - granted to security principals such as: Domain Users, Authenticated Users, and Everyone. + permissions granting open access within the targeted domains. Open Access means access + granted to security principals such as Domain Users, Authenticated Users, and Everyone. - [6.Broken Inheritance > AD_BrokenInheritance Job](/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/ad_brokeninheritance.md) – Reports on all locations within Active Directory where inheritance is broken within the targeted domains - [7.Containers Job Group](/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/containers/overview.md) – Reports on all Active Directory permissions diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/recommended.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/recommended.md index d6de0beda2..2f14fe2c55 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/recommended.md @@ -8,11 +8,11 @@ sidebar_position: 10 **Dependencies** -The following Access Analyzer job groups need to be successfully run: +Successfully run the following Access Analyzer job groups: - .Active Directory Inventory Job Group -The following jobs need to be run prior to running the [AD_ShadowAccess Job](/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/ad_shadowaccess.md): +Run the following jobs before running the [AD_ShadowAccess Job](/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/ad_shadowaccess.md): - .Active Directory Inventory >1-AD_Scan > ADInventory - Active Directory > 1.Groups > AD_SensitiveSecurityGroups @@ -21,7 +21,7 @@ The following jobs need to be run prior to running the [AD_ShadowAccess Job](/do - Active Directory Permissions Analyzer > 1.Users > AD_ResetPasswordPermissions - Active Directory Permissions Analyzer > 2.Groups > AD_GroupMembershipPermissions -The following jobs can be optionally run to enhance reporting in the +You can optionally run the following jobs to enhance reporting in the [AD_ShadowAccess Job](/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/ad_shadowaccess.md): - Active Directory > 2.Users > AD_WeakPasswords @@ -51,7 +51,7 @@ This job group can be scheduled to run as desired. **Workflow** -**Step 1 –** Prerequisite: Successful execution of the .Active Directory Inventory Job Group. +**Step 1 –** Prerequisite: Successfully run the .Active Directory Inventory Job Group. **Step 2 –** Schedule the Active Directory Permissions Analyzer Job Group to run as desired. diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/sites/ad_dcshadowpermissions.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/sites/ad_dcshadowpermissions.md index 97264d6ef6..9027f77123 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/sites/ad_dcshadowpermissions.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/sites/ad_dcshadowpermissions.md @@ -15,7 +15,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **9.Sites** > **AD_DCShadowPermissions** > **Configure** node and select **Analysis** to view analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/sites/ad_sitepermissions.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/sites/ad_sitepermissions.md index 2be820a4bb..8e75393317 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/sites/ad_sitepermissions.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/sites/ad_sitepermissions.md @@ -15,7 +15,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **9.Sites** > **AD_S **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/users/ad_resetpasswordpermissions.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/users/ad_resetpasswordpermissions.md index 14bed4f8f0..fad81cc5f0 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/users/ad_resetpasswordpermissions.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/users/ad_resetpasswordpermissions.md @@ -18,7 +18,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **1.Users** > tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/users/ad_userpermissions.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/users/ad_userpermissions.md index 9182111f66..7190f6db1b 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/users/ad_userpermissions.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/users/ad_userpermissions.md @@ -16,7 +16,7 @@ Navigate to the **Active Directory Permissions Analyzer** > **1.Users** > **AD_U **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -30,7 +30,7 @@ The default analysis tasks are: - Summarize user object permissions – Creates an interim processing table in the database for use by downstream analysis and report generation - User Ownership – Lists the owners of each user object and determines if they are a non-standard - owner. Principals that are not administrators are considered non-standard owners of user objects. + owner. Principals that aren't administrators are considered non-standard owners of user objects. Creates the SA_AD_UserOwnership_Details table accessible under the job’s Results node. - User Ownership Summary – Summarizes the owner type by domain diff --git a/docs/accessanalyzer/12.0/solutions/anyid/anyid_csv.md b/docs/accessanalyzer/12.0/solutions/anyid/anyid_csv.md index 49f42927df..6130aab858 100644 --- a/docs/accessanalyzer/12.0/solutions/anyid/anyid_csv.md +++ b/docs/accessanalyzer/12.0/solutions/anyid/anyid_csv.md @@ -32,7 +32,7 @@ Local Host **Connection Profile** -The AnyID_CSV job does not require a connection profile. +The AnyID_CSV job doesn't require a connection profile. **History Retention** @@ -50,11 +50,11 @@ Schedule the job as required. **Query Configuration** This job contains configurable queries. See the -[Configure the AnyID_CSV Query](#configure-the-anyid_csvquery) topic for additional information. +[Configure the AnyID_CSV Query](#configure-the-anyidcsvquery) topic for additional information. **Analysis Configuration** -See the [Analysis Tasks for the AnyID_CSV Job](#analysis-tasks-for-the-anyid_csvjob) topic for +See the [Analysis Tasks for the AnyID_CSV Job](#analysis-tasks-for-the-anyidcsvjob) topic for additional information. **Workflow** @@ -76,11 +76,11 @@ The AnyID_CSV query uses the PowerShell Data Collector. The query is: - CSV Import – Imports identities and attributes from a CSV file. See the - [Configure the AnyID_CSV Query](#configure-the-anyid_csvquery) topic for additional information. + [Configure the AnyID_CSV Query](#configure-the-anyidcsvquery) topic for additional information. ### Configure the AnyID_CSV Query -Follow the steps to configure the AnyID_CSV query. +To configure the AnyID_CSV query, complete the following steps. ![ The name of the source repository parameter on the job Overview page](/images/accessanalyzer/12.0/solutions/anyid/csvoverviewpage.webp) @@ -109,11 +109,12 @@ The following attributes must be configured in order for the job to execute prop - $inputfile – File path to the CSV file which contains the identity and attribute information -- $RequiredAttributes – The list of attributes that need to be found in the document in order to +- $RequiredAttributes – The list of attributes that need to be found in the document to trigger a match - - An attribute in the Attributes list will not be considered a match (in reporting and AIC) - unless an attribute in the RequiredAttributes list is also found in the same file + - An attribute in the Attributes list will not be considered a match (in reporting and the + Access Information Center (AIC)) unless an attribute in the RequiredAttributes list is also + found in the same file - $Attributes – The list of attributes that will be scanned for during sensitive data scanning @@ -139,7 +140,7 @@ Navigate to the **Jobs** > **AnyID Connectors** > **AnyID_CSV** > **Configure** **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/anyid/anyid_epicclarity.md b/docs/accessanalyzer/12.0/solutions/anyid/anyid_epicclarity.md index abbe3349ca..61b63cb3a6 100644 --- a/docs/accessanalyzer/12.0/solutions/anyid/anyid_epicclarity.md +++ b/docs/accessanalyzer/12.0/solutions/anyid/anyid_epicclarity.md @@ -8,7 +8,7 @@ sidebar_position: 20 The AnyID_EpicClarity job collects patient information from Epic including MRNs, SSNs, Subscriber IDs, and Account IDs. An account with read access to the underlying Clarity Oracle database is -required in order to run queries. +required to run queries. ![AnyID_EpicClarity Job in the Jobs Tree](/images/accessanalyzer/12.0/solutions/anyid/epicclarityjoblocation.webp) @@ -22,7 +22,7 @@ The following are recommended configurations for the AnyID_EpicClarity job: The AnyID_EpicClarity job requires a CSV file with a filepath configured in the job's query to collect data. See the -[Configure the AnyID_EpicClarity Queries](#configure-the-anyid_epicclarity-queries) topic for +[Configure the AnyID_EpicClarity Queries](#configure-the-anyidepicclarity-queries) topic for additional information. **Targeted Host** @@ -44,12 +44,12 @@ Not supported **Schedule Frequency** -This job should be run based on the desired frequency of Sensitive Data Scans. +This job should be run based on the frequency you want for Sensitive Data Scans. **Query Configuration** This job contains configurable queries. See the Configure the -[Configure the AnyID_EpicClarity Queries](#configure-the-anyid_epicclarity-queries) topic for +[Configure the AnyID_EpicClarity Queries](#configure-the-anyidepicclarity-queries) topic for additional information. **Analysis Configuration** @@ -78,12 +78,12 @@ The queries are: - Epic Clarity Identity IDs – Imports Epic Clarity subject profile information on identity IDs The above queries have configurable parameters. See the -[Configure the AnyID_EpicClarity Queries](#configure-the-anyid_epicclarity-queries) topic for +[Configure the AnyID_EpicClarity Queries](#configure-the-anyidepicclarity-queries) topic for additional information. ### Configure the AnyID_EpicClarity Queries -Follow the steps to configure the AnyID_EpicClarity queries. +To configure the AnyID_EpicClarity queries, complete the following steps. **Step 1 –** Navigate to the **AnyID Connectors** > **AnyID_EpicClarity** > **Configure** node and select **Queries**. @@ -107,10 +107,11 @@ information. Configure the following attributes as needed: - $Attributes – The list of attributes that will be scanned for during sensitive data scanning. Default values are MRN, SSN, Name, Date of Birth, Subscriber ID, Identity ID, and Account ID. - - An attribute in the Attributes list will not be considered a match (in reporting and AIC) - unless an attribute in the RequiredAttributes list is also found in the same file + - An attribute in the Attributes list will not be considered a match (in reporting and the + Access Information Center (AIC)) unless an attribute in the RequiredAttributes list is also + found in the same file -- $RequiredAttributes – The list of attributes that need to be found in the document in order to +- $RequiredAttributes – The list of attributes that need to be found in the document to trigger a match. The default values are SSN, MRN, and IdentityID. - An attribute in the Attributes list will not be considered a match (in reporting and AIC) @@ -130,7 +131,7 @@ Navigate to the **Jobs** > **AnyID Connectors** > **AnyID_EpicClarity** > **Con select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/anyid/anyid_paycom.md b/docs/accessanalyzer/12.0/solutions/anyid/anyid_paycom.md index 78f7313c73..aae887e58b 100644 --- a/docs/accessanalyzer/12.0/solutions/anyid/anyid_paycom.md +++ b/docs/accessanalyzer/12.0/solutions/anyid/anyid_paycom.md @@ -7,7 +7,7 @@ sidebar_position: 30 # AnyID_Paycom Job The AnyID_Paycom job pulls employee information from Paycom including name, address, date of Birth, -and SSN. Contact the organization's Paycom administrator in order to generate the CSV export +and SSN. Contact the organization's Paycom administrator to generate the CSV export required for this job. The recommended approach is to copy the CSV file to the Access Analyzer Console for best import performance. @@ -29,7 +29,7 @@ Local Host **Connection Profile** -The AnyID_Paycom job does not require a connection profile. +The AnyID_Paycom job doesn't require a connection profile. **History Retention** @@ -42,12 +42,12 @@ Not supported **Schedule Frequency** -This job should be run based on the desired frequency of Sensitive Data Scans. +This job should be run based on the frequency you want for Sensitive Data Scans. **Query Configuration** This job contains configurable queries. See the -[Configure the AnyID_Paycom Job](#configure-the-anyid_paycom-job) topic for additional information. +[Configure the AnyID_Paycom Job](#configure-the-anyidpaycom-job) topic for additional information. **Analysis Configuration** @@ -72,12 +72,12 @@ The AnyID_Paycom job uses the PowerShell Data Collector for the query. The queries are: - Paycom CSV Import – Imports a CSV file with information from Paycom. This query has configurable - parameters. See the [Configure the AnyID_Paycom Job](#configure-the-anyid_paycom-job) topic for + parameters. See the [Configure the AnyID_Paycom Job](#configure-the-anyidpaycom-job) topic for additional information. ### Configure the AnyID_Paycom Job -Follow the steps to configure the AnyID_Paycom query. +To configure the AnyID_Paycom query, complete the following steps. **Step 1 –** Navigate to the **AnyID Connectors** > **AnyID_Paycom** > **Configure** node and select **Queries**. @@ -95,16 +95,17 @@ the page to expand the Parameters window. See the [PowerShell: Edit Query](/docs/accessanalyzer/12.0/admin/datacollector/powershell/editquery.md) topic for additional information. Configure the following attributes as needed: -- $SAHOSTNAME – Created during execution. This parameter cannot be modified. -- $JobCredential – Created during execution. This parameter cannot be modified. -- $JobCredentials – Created during execution. This parameter cannot be modified. +- $SAHOSTNAME – Created during execution. This parameter can't be modified. +- $JobCredential – Created during execution. This parameter can't be modified. +- $JobCredentials – Created during execution. This parameter can't be modified. - $inputfile – File path to the CSV file which contains the identity and attribute information - $Attributes – The list of attributes that will be scanned for during sensitive data scanning - - An attribute in the Attributes list will not be considered a match (in reporting and AIC) - unless an attribute in the RequiredAttributes list is also found in the same file + - An attribute in the Attributes list will not be considered a match (in reporting and the + Access Information Center (AIC)) unless an attribute in the RequiredAttributes list is also + found in the same file -- $RequiredAttributes – The list of attributes that need to be found in the document in order to +- $RequiredAttributes – The list of attributes that need to be found in the document to trigger a match - An attribute in the Attributes list will not be considered a match (in reporting and AIC) @@ -129,7 +130,7 @@ Navigate to the **Jobs** > **AnyID Connectors** > **AnyID_Paycom** > **Configur **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/anyid/anyid_salesforce.md b/docs/accessanalyzer/12.0/solutions/anyid/anyid_salesforce.md index f5fbdc9258..da59901759 100644 --- a/docs/accessanalyzer/12.0/solutions/anyid/anyid_salesforce.md +++ b/docs/accessanalyzer/12.0/solutions/anyid/anyid_salesforce.md @@ -7,7 +7,7 @@ sidebar_position: 40 # AnyID_Salesforce Job The AnyID_Salesforce job collects Salesforce contact details including phone, address, email, and -date of birth. This job requires API access to Salesforce in order to collect this information. The +date of birth. This job requires API access to Salesforce to collect this information. The list of collected attributes can be adjusted as necessary. ![AnyID_Salesforce Job in the Jobs Tree](/images/accessanalyzer/12.0/solutions/anyid/salesforcejoblocation.webp) @@ -56,7 +56,7 @@ Schedule the job as required. **Query Configuration** This job contains configurable queries. See the -[Configure the AnyID_Salesforce Query](#configure-the-anyid_salesforce-query) topic for additional +[Configure the AnyID_Salesforce Query](#configure-the-anyidsalesforce-query) topic for additional information. **Analysis Configuration** @@ -82,12 +82,12 @@ The AnyID_Salesforce job uses the PowerShell Data Collector for the query. The query is: - PS Salesforce Import – Imports Salesforce information for analysis. This query has configurable - parameters. See the [Configure the AnyID_Salesforce Query](#configure-the-anyid_salesforce-query) + parameters. See the [Configure the AnyID_Salesforce Query](#configure-the-anyidsalesforce-query) topic for additional information. ### Configure the AnyID_Salesforce Query -Follow the steps to configure the AnyID_Salesforce query. +To configure the AnyID_Salesforce query, complete the following steps. **Step 1 –** Navigate to the **AnyID Connectors** > **AnyID_Salesforce** > **Configure** node and select **Queries**. @@ -105,15 +105,16 @@ the page to expand the Parameters window. See the [PowerShell: Edit Query](/docs/accessanalyzer/12.0/admin/datacollector/powershell/editquery.md) topic for additional information. Configure the following attributes as needed: -- $SAHOSTNAME – Created during execution. This parameter cannot be modified. -- $JobCredential – Created during execution. This parameter cannot be modified. -- $JobCredentials – Created during execution. This parameter cannot be modified. +- $SAHOSTNAME – Created during execution. This parameter can't be modified. +- $JobCredential – Created during execution. This parameter can't be modified. +- $JobCredentials – Created during execution. This parameter can't be modified. - $Attributes – The list of attributes that will be scanned for during sensitive data scanning - - An attribute in the Attributes list will not be considered a match (in reporting and AIC) - unless an attribute in the RequiredAttributes list is also found in the same file + - An attribute in the Attributes list will not be considered a match (in reporting and the + Access Information Center (AIC)) unless an attribute in the RequiredAttributes list is also + found in the same file -- $RequiredAttributes – The list of attributes that need to be found in the document in order to +- $RequiredAttributes – The list of attributes that need to be found in the document to trigger a match - An attribute in the Attributes list will not be considered a match (in reporting and AIC) @@ -135,7 +136,7 @@ Navigate to the **Jobs** > **AnyID Connectors** > **AnyID_Salesforce** > **Conf select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/anyid/overview.md b/docs/accessanalyzer/12.0/solutions/anyid/overview.md index ad75fe889e..74b5bcf6cf 100644 --- a/docs/accessanalyzer/12.0/solutions/anyid/overview.md +++ b/docs/accessanalyzer/12.0/solutions/anyid/overview.md @@ -6,24 +6,24 @@ sidebar_position: 60 # AnyID Connectors Solution -The AnyID Connectors Solution allows you to quickly find where data for identities are stored, +Use the AnyID Connectors Solution to quickly find where data for identities are stored, reducing the response time to Data Subject Access Requests (DSARs). Integration with third party -repositories allows you to perform exact data matching for profiles such as employees, customers, +repositories lets you perform exact data matching for profiles such as employees, customers, students, or patients across any data repository. Data Privacy Engine works in conjunction with Access Analyzer Sensitive Data Discovery scans to create an efficient, secure IdentityIndex™ that privacy, security, and legal professionals can -leverage to quickly and easily map the location of subject information. Through a series of -preconfigured Identity Connectors,you can easily extract identity-related attributes about customers +use to quickly map the location of subject information. Through a series of +preconfigured Identity Connectors, you can extract identity-related attributes about customers and other potential subjects from verified systems of record like Salesforce, Epic, Peoplesoft, and Paycom, as well as homegrown or alternative platforms. Through the creation of a Subject Profile for each individual, Access Analyzer’s broad-reaching Sensitive Data Discovery engine accurately identifies the specific location of a subject’s data -across virtually any cloud or on-premises data repository. With this context in tow, organizations -can now easily perform Data Subject Access Requests (DSARs), zero-in on where the implementation of -Privacy by Design principles are needed most urgently, and know for certain when breach attempts and -activities involve consumer, patient, resident, and other subject data. +across virtually any cloud or on-premises data repository. With this context, organizations +can perform Data Subject Access Requests (DSARs), identify where Privacy by Design principles are +needed most urgently, and confirm when breach attempts and activities involve consumer, patient, +resident, and other subject data. ## Supported Platforms @@ -40,7 +40,7 @@ for additional information. ![AnyID Connectors Solution in the Jobs Tree](/images/accessanalyzer/12.0/solutions/anyid/jobstree.webp) -Once installed into the Jobs tree, navigate to the solution: **Jobs** > **AnyID Connectors**. +After you install the solution into the Jobs tree, navigate to it: **Jobs** > **AnyID Connectors**. ## Jobs @@ -62,12 +62,12 @@ The jobs in the AnyID Connectors Solution are: this when a native integration may not be available, or an export is the best option. - [AnyID_EpicClarity Job](/docs/accessanalyzer/12.0/solutions/anyid/anyid_epicclarity.md) – Collects patient information from Epic including MRNs, SSNs, Subscriber IDs, and Account IDs. An account with read access to the underlying Clarity - Oracle database is required in order to run queries. + Oracle database is required to run queries. - [AnyID_Paycom Job](/docs/accessanalyzer/12.0/solutions/anyid/anyid_paycom.md) – Pulls employee information from Paycom including Name, - Address, Date of Birth, and SSN. Contact your Paycom administrator in order to generate the CSV + Address, Date of Birth, and SSN. Contact your Paycom administrator to generate the CSV export required for this job. - [AnyID_Salesforce Job](/docs/accessanalyzer/12.0/solutions/anyid/anyid_salesforce.md) – Collects Salesforce Contact details including Phone, - Address, Email, and Date of birth. This job requires API access to Salesforce in order to collect + Address, Email, and Date of birth. This job requires API access to Salesforce to collect this information. :::note diff --git a/docs/accessanalyzer/12.0/solutions/aws/collection/1.aws_orgscan.md b/docs/accessanalyzer/12.0/solutions/aws/collection/1.aws_orgscan.md index 0a5eaf9d3a..8a6f6c87d6 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/collection/1.aws_orgscan.md +++ b/docs/accessanalyzer/12.0/solutions/aws/collection/1.aws_orgscan.md @@ -23,7 +23,7 @@ The 1.AWS_OrgScan job has the following configurable query: ### Configure the Org Scan Query The Org Scan query in the 1.AWS_OrgScan job has been preconfigured to run with the default settings -with the category of Collect Org Data. Follow the steps to set any desired customizations. +with the category of Collect Org Data. To set any desired customizations, complete the following steps. **Step 1 –** Navigate to the **AWS** > **0.Collection** > **1.AWS_OrgScan** > **Configure** node and select the **Queries** node. diff --git a/docs/accessanalyzer/12.0/solutions/aws/collection/2.aws_s3scan.md b/docs/accessanalyzer/12.0/solutions/aws/collection/2.aws_s3scan.md index 18ede10066..ceea86a2da 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/collection/2.aws_s3scan.md +++ b/docs/accessanalyzer/12.0/solutions/aws/collection/2.aws_s3scan.md @@ -23,7 +23,7 @@ The 2.AWS_S3Scan job has the following configurable query: ### Configure the S3 Scan Query The S3 Scan query in the 2.AWS_S3 Scan job has been preconfigured to run with the default settings -with the category of Collect S3. Follow the steps to set any desired customizations. +with the category of Collect S3. To set any desired customizations, complete the following steps. **Step 1 –** Navigate to the **AWS** > **0.Collection** > **2.AWS_S3Scan** > **Configure** node and select the **Queries** node. @@ -63,7 +63,7 @@ Navigate to the **AWS** > **0.Collection** > **2.AWS_S3Scan** > **Configure** no **Analysis** to view analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/aws/collection/3.aws_iamscan.md b/docs/accessanalyzer/12.0/solutions/aws/collection/3.aws_iamscan.md index 2729e78d91..5897d25572 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/collection/3.aws_iamscan.md +++ b/docs/accessanalyzer/12.0/solutions/aws/collection/3.aws_iamscan.md @@ -23,7 +23,7 @@ The 3.AWS_IAMScan job has the following configurable query: ### Configure the IAM Scan Query The IAM Scan query in the 3.AWS_IAMScan job has been preconfigured to run with the default settings -with the category of Collect IAM Data. Follow the steps to set any desired customizations. +with the category of Collect IAM Data. To set any desired customizations, complete the following steps. **Step 1 –** Navigate to the **AWS** > **0.Collection** > **3.AWS_IAMScan** > **Configure** node and select the **Queries** node. @@ -54,7 +54,7 @@ View the analysis tasks by navigating to the **AWS** > **0.Collection** > **3.AW **Configure** node and selecting **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/aws/collection/4.aws_s3sddscan.md b/docs/accessanalyzer/12.0/solutions/aws/collection/4.aws_s3sddscan.md index 43a3fda53c..ddca91616d 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/collection/4.aws_s3sddscan.md +++ b/docs/accessanalyzer/12.0/solutions/aws/collection/4.aws_s3sddscan.md @@ -22,8 +22,8 @@ The 4.AWS_S3SDDScan job has the following configurable query: ### Configure the AWS S3 Sensitive Data Scan Query The AWS S3 Sensitive Data Scan query in the 4.AWS_S3SDDScan job has been preconfigured to run with -the default settings with the category of Collect SDD Data. Follow the steps to set any desired -customizations. +the default settings with the category of Collect SDD Data. To set any desired +customizations, complete the following steps. **Step 1 –** Navigate to the **AWS** > **0.Collection** > **4.AWS_S3SDD Scan** > **Configure** node and select the **Queries** node. @@ -94,7 +94,7 @@ View the analysis tasks by navigating to the **AWS** > **0.Collection** > **4.AW **Configure** node and selecting **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/aws/collection/overview.md b/docs/accessanalyzer/12.0/solutions/aws/collection/overview.md index 490317e431..46511dedee 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/collection/overview.md +++ b/docs/accessanalyzer/12.0/solutions/aws/collection/overview.md @@ -17,7 +17,7 @@ The 0.Collection Job Group is comprised of: password policies and accounts within the organization - [2.AWS_S3Scan Job](/docs/accessanalyzer/12.0/solutions/aws/collection/2.aws_s3scan.md) – Collects details about the AWS S3 buckets including details about the objects in those buckets -- [3.AWS_IAMScan Job](/docs/accessanalyzer/12.0/solutions/aws/collection/3.aws_iamscan.md) – Collects details about users, groups, policies, roles and +- [3.AWS_IAMScan Job](/docs/accessanalyzer/12.0/solutions/aws/collection/3.aws_iamscan.md) – Collects details about users, groups, policies, roles, and other IAM related identities - [4.AWS_S3SDDScan Job](/docs/accessanalyzer/12.0/solutions/aws/collection/4.aws_s3sddscan.md) – Collects details about S3 objects containing sensitive data diff --git a/docs/accessanalyzer/12.0/solutions/aws/groups/aws_groupmembers.md b/docs/accessanalyzer/12.0/solutions/aws/groups/aws_groupmembers.md index 610c63c0fb..0f7bf71e97 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/groups/aws_groupmembers.md +++ b/docs/accessanalyzer/12.0/solutions/aws/groups/aws_groupmembers.md @@ -15,7 +15,7 @@ Navigate to the **AWS** > **3.Groups** > **AWS_GroupMembers** > **Configure** no **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/aws/groups/aws_nopolicygroups.md b/docs/accessanalyzer/12.0/solutions/aws/groups/aws_nopolicygroups.md index 664280a88c..9cb7f7ed98 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/groups/aws_nopolicygroups.md +++ b/docs/accessanalyzer/12.0/solutions/aws/groups/aws_nopolicygroups.md @@ -14,7 +14,7 @@ Navigate to the **AWS** > **3.Groups** > **AWS_NoPolicyGroups** > **Configure** **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -35,4 +35,4 @@ produces the following preconfigured report: | Report | Description | Default Tags | Report Element | | ----------------------- | ----------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Groups With No Policies | This report identifies groups that do not have a policy assigned. | None | This report is comprised of the following elements:
  • Stacked Bar Chart – Displays top accounts by no policy group counts
  • Table – Shows no policy groups by accounts
  • Table – Provides details on no policy groups
| +| Groups With No Policies | This report identifies groups that don't have a policy assigned. | None | This report is comprised of the following elements:
  • Stacked Bar Chart – Displays top accounts by no policy group counts
  • Table – Shows no policy groups by accounts
  • Table – Provides details on no policy groups
| diff --git a/docs/accessanalyzer/12.0/solutions/aws/groups/aws_stalegroups.md b/docs/accessanalyzer/12.0/solutions/aws/groups/aws_stalegroups.md index 21f1fbfba4..d879196ceb 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/groups/aws_stalegroups.md +++ b/docs/accessanalyzer/12.0/solutions/aws/groups/aws_stalegroups.md @@ -11,17 +11,17 @@ definition for staleness is set by default to 60 days. This can be configured. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/12.0/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. The AWS_StaleGroups job has the following configurable parameter: -- Days without login to consider an account stale +- Days without log in to consider an account stale See the -[Customizable Analysis Tasks for the AWS_StaleGroups Job](#customizable-analysis-tasks-for-the-aws_stalegroups-job) +[Customizable Analysis Tasks for the AWS_StaleGroups Job](#customizable-analysis-tasks-for-the-awsstalegroups-job) topic for additional information. ## Analysis Tasks for the AWS_StaleGroups Job @@ -30,7 +30,7 @@ Navigate to the **AWS** > **3.Groups** > **AWS_StaleGroups** > **Configure** nod **Analysis** to view the analysis tasks. :::warning -Do not deselect the selected analysis tasks. The analysis tasks are preconfigured for +Don't deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. Only modify the analysis tasks listed in the customizable analysis tasks section. ::: @@ -42,9 +42,9 @@ The following analysis tasks are selected by default: - Stale Group Details – Highlights the staleness of users in AWS groups. Creates the AWS_StaleGroup_Details table accessible under the job’s Results node. - - The number of days without login to consider an account stale can be customized. By default it + - The number of days without log in to consider an account stale can be customized. By default it is set to 60. See the - [Customizable Analysis Tasks for the AWS_StaleGroups Job](#customizable-analysis-tasks-for-the-aws_stalegroups-job) + [Customizable Analysis Tasks for the AWS_StaleGroups Job](#customizable-analysis-tasks-for-the-awsstalegroups-job) topic for additional information. - Stale Group Summary – Summarizes statistics for stale groups. Creates the AWS_StaleGroup_Summary @@ -57,7 +57,7 @@ The default values for parameters that can be customized are: | Analysis Task | Customizable Parameter Name | Default Value | Value Indicates | | ------------------- | --------------------------- | ------------- | ----------------------------------------------- | -| Stale Group Details | @StaleThreshold | 60 | Days without login to consider an account stale | +| Stale Group Details | @StaleThreshold | 60 | Days without log in to consider an account stale | See the [Configure the Customizable Parameters in an Analysis Task](/docs/accessanalyzer/12.0/admin/jobs/job/configure/analysis/analysiscustomizableparameters.md) diff --git a/docs/accessanalyzer/12.0/solutions/aws/organizations/aws_accounts.md b/docs/accessanalyzer/12.0/solutions/aws/organizations/aws_accounts.md index 5543d303d7..b7523198dd 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/organizations/aws_accounts.md +++ b/docs/accessanalyzer/12.0/solutions/aws/organizations/aws_accounts.md @@ -17,7 +17,7 @@ Navigate to the **AWS** > **1.Organizations** > **AWS_Accounts** > **Configure** **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/aws/organizations/aws_memberaccountusers.md b/docs/accessanalyzer/12.0/solutions/aws/organizations/aws_memberaccountusers.md index a51e606fb4..b36a42e2cb 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/organizations/aws_memberaccountusers.md +++ b/docs/accessanalyzer/12.0/solutions/aws/organizations/aws_memberaccountusers.md @@ -6,7 +6,7 @@ sidebar_position: 20 # AWS_MemberAccountUsers Job -The AWS_MemberAccountUsers job highlights users that are not located in the primary AWS Identity +The AWS_MemberAccountUsers job highlights users that aren't located in the primary AWS Identity Source, which is generally the Master AWS Account for the Organization. ## Analysis Tasks for the AWS_MemberAccountUsers Job @@ -15,7 +15,7 @@ Navigate to the **AWS** > **1.Organizations** > **AWS_MemberAccountUsers** > **C select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -36,4 +36,4 @@ produces the following preconfigured report: | Report | Description | Default Tags | Report Element | | -------------------- | -------------------------------------------------------------------------------------- | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Member Account Users | This report highlights user accounts that are not contained in the AWS Master Account. | None | This report is comprised of the following elements:
  • Stacked Bar Chart – Displays top member account users by org
  • Table – Shows member account users by Org
  • Table – Provides details on member account users
| +| Member Account Users | This report highlights user accounts that aren't contained in the AWS Master Account. | None | This report is comprised of the following elements:
  • Stacked Bar Chart – Displays top member account users by org
  • Table – Shows member account users by Org
  • Table – Provides details on member account users
| diff --git a/docs/accessanalyzer/12.0/solutions/aws/organizations/overview.md b/docs/accessanalyzer/12.0/solutions/aws/organizations/overview.md index 2dd6b8dddf..c29944cde4 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/organizations/overview.md +++ b/docs/accessanalyzer/12.0/solutions/aws/organizations/overview.md @@ -15,7 +15,7 @@ The 1.Organizations job jroup is comprised of: - [AWS_Accounts Job](/docs/accessanalyzer/12.0/solutions/aws/organizations/aws_accounts.md) – Provides detailed information about the accounts that exist in each AWS Organization. This job also determines the AWS Master Account for each Organization. - The AWS Master Account can be set manually by adding a line for each Organization in the temporary - table #IdentitySourceAccount in the analysis task parameters for this job. -- [AWS_MemberAccountUsers Job](/docs/accessanalyzer/12.0/solutions/aws/organizations/aws_memberaccountusers.md) – Highlights users that are not located in + You can set the AWS Master Account manually by adding a line for each Organization in the + temporary table #IdentitySourceAccount in the analysis task parameters for this job. +- [AWS_MemberAccountUsers Job](/docs/accessanalyzer/12.0/solutions/aws/organizations/aws_memberaccountusers.md) – Highlights users that aren't located in the primary AWS Identity Source, which is generally the Master AWS Account for the Organization diff --git a/docs/accessanalyzer/12.0/solutions/aws/overview.md b/docs/accessanalyzer/12.0/solutions/aws/overview.md index 8f752dc53b..7a9943e901 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/overview.md +++ b/docs/accessanalyzer/12.0/solutions/aws/overview.md @@ -6,10 +6,10 @@ sidebar_position: 70 # AWS Solution -Access Analyzer for AWS allows organizations to secure their data residing in Amazon Web Services -(AWS) S3 platform, reducing their risk exposure through proactive, automated auditing and reporting -of S3 permissions, sensitive data, and ultimately a consolidated view of user access rights across -dozens of structured and unstructured data resources both on-premises and in the cloud. +Access Analyzer for AWS helps organizations secure data stored in the Amazon Web Services (AWS) S3 +platform. It reduces risk exposure through proactive, automated auditing and reporting of S3 +permissions and sensitive data, giving you a consolidated view of user access rights across dozens +of structured and unstructured data resources, both on-premises and in the cloud. The AWS Solution is designed to provide information about data access such as: @@ -17,11 +17,11 @@ The AWS Solution is designed to provide information about data access such as: - Who is accessing your data - What sensitive data is being stored and accessed -The AWS Solution provides the ability to audit AWS IAM and S3. Access Analyzer uses the AWS solution +The AWS Solution lets you audit AWS IAM and S3. Access Analyzer uses the AWS solution to collect IAM users, groups, roles, and policies, as well as S3 permissions, content, and sensitive -data from target AWS accounts. The solution requires a special Access Analyzer license. It can be -focused to only conduct auditing of AWS IAM. Additionally, the Sensitive Data Discovery Add-On -enables the solution to search AWS S3 content for sensitive data. +data from target AWS accounts. The solution requires a special Access Analyzer license. You can focus it to audit only AWS IAM. +Additionally, the Sensitive Data Discovery Add-On enables the solution to search AWS S3 content for +sensitive data. **Supported Platforms** @@ -36,25 +36,25 @@ topic for additional information. **Sensitive Data Discovery Considerations** -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the minimum amount -of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For example, if the job -is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are required (8x2=16). +If you run Sensitive Data Discovery (SDD) scans, increase the minimum amount of RAM. Each thread +requires a minimum of 2 additional GB of RAM per host. For example, a job configured to scan 8 +hosts at a time requires an extra 16 GB of RAM (8x2=16). :::note -The appropriate JDK (Java) version for Sensitive Data Discovery is installed on the -server. The JDK deployed is prepackaged and does not require any configuration; it has been -preconfigured to work with Access Analyzer and should never be customized through Java. It will not +Access Analyzer installs the appropriate JDK (Java) version for Sensitive Data Discovery on the +server. The deployed JDK is prepackaged and doesn't require any configuration. Access Analyzer +preconfigures it to work with the product, so never customize it through Java. It will not conflict with other JDKs or Java Runtimes in the same environment. ::: **Location** -The AWS Solution requires a special Access Analyzer license. It can be installed from the Access +The AWS Solution requires a special Access Analyzer license. You can install it from the Access Analyzer Instant Job Wizard. See the [Instant Job Wizard](/docs/accessanalyzer/12.0/admin/jobs/instantjobs/overview.md) topic for information on installing instant solutions from the Access Analyzer Library. -Once it has been installed into the Jobs tree, navigate to the solution: **Jobs** > **AWS**. +After you install it into the Jobs tree, navigate to the solution: **Jobs** > **AWS**. ## Job Groups diff --git a/docs/accessanalyzer/12.0/solutions/aws/policies/aws_custommanagedpolicies.md b/docs/accessanalyzer/12.0/solutions/aws/policies/aws_custommanagedpolicies.md index c1ed041844..bcac941c81 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/policies/aws_custommanagedpolicies.md +++ b/docs/accessanalyzer/12.0/solutions/aws/policies/aws_custommanagedpolicies.md @@ -15,7 +15,7 @@ Navigate to the **AWS** > **5.Policies** > **AWS_CustomManagedPolicies** > **Con select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/aws/policies/aws_inlinepolicies.md b/docs/accessanalyzer/12.0/solutions/aws/policies/aws_inlinepolicies.md index 7de42e513c..63a488ee30 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/policies/aws_inlinepolicies.md +++ b/docs/accessanalyzer/12.0/solutions/aws/policies/aws_inlinepolicies.md @@ -15,7 +15,7 @@ Navigate to the **AWS** > **5.Policies** > **AWS_InlinePolicies** > **Configure* **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/aws/policies/aws_managedpolicies.md b/docs/accessanalyzer/12.0/solutions/aws/policies/aws_managedpolicies.md index db57a58073..c011a1ee8c 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/policies/aws_managedpolicies.md +++ b/docs/accessanalyzer/12.0/solutions/aws/policies/aws_managedpolicies.md @@ -14,7 +14,7 @@ Navigate to the **AWS** > **5.Policies** > **AWS_ManagedPolicies** > **Configure **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/aws/policies/aws_sensitivepolicies.md b/docs/accessanalyzer/12.0/solutions/aws/policies/aws_sensitivepolicies.md index c012690919..70acd181c8 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/policies/aws_sensitivepolicies.md +++ b/docs/accessanalyzer/12.0/solutions/aws/policies/aws_sensitivepolicies.md @@ -15,7 +15,7 @@ Navigate to the **AWS** > **5.Policies** > **AWS_SensitivePolicies** > **Configu **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/aws/policies/aws_unusedmanagedpolicies.md b/docs/accessanalyzer/12.0/solutions/aws/policies/aws_unusedmanagedpolicies.md index d2277734f1..6f7c5d3ddf 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/policies/aws_unusedmanagedpolicies.md +++ b/docs/accessanalyzer/12.0/solutions/aws/policies/aws_unusedmanagedpolicies.md @@ -7,12 +7,12 @@ sidebar_position: 50 # AWS_UnusedManagedPolicies Job The AWS_UnusedManagedPolicies job provides details on customer managed policies that exist in the -AWS Organization. Optionally, AWS managed policies can be included by changing the parameter for the +AWS Organization. Optionally, include AWS managed policies by changing the parameter for the analysis task. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/12.0/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -22,7 +22,7 @@ The AWS_UnusedManagedPolicies job has the following configurable parameter: - True or False value to include policies managed by AWS See the -[Customizable Analysis Tasks for the AWS_UnusedManagedPolicies Job](#customizable-analysis-tasks-for-the-aws_unusedmanagedpolicies-job) +[Customizable Analysis Tasks for the AWS_UnusedManagedPolicies Job](#customizable-analysis-tasks-for-the-awsunusedmanagedpolicies-job) topic for additional information. ## Analysis Tasks for the AWS_UnusedManagedPolicies Job @@ -31,7 +31,7 @@ Navigate to the **AWS** > **5.Policies** > **AWS_UnusedManagedPolicies** > **Con select **Analysis** to view the analysis tasks. :::warning -Do not deselect the selected analysis tasks. The analysis tasks are preconfigured for +Don't deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. Only modify the analysis tasks listed in the customizable analysis tasks section. ::: @@ -43,8 +43,8 @@ The following analysis tasks are selected by default: - Unused Managed Policies – Policies not assigned to any group or user. Creates the AWS_UnusedPolicies_Details table accessible under the job’s Results node. - - Optionally, AWS managed policies can be included by setting the parameter to True. See the - [Customizable Analysis Tasks for the AWS_UnusedManagedPolicies Job](#customizable-analysis-tasks-for-the-aws_unusedmanagedpolicies-job) + - Optionally, include AWS managed policies by setting the parameter to True. See the + [Customizable Analysis Tasks for the AWS_UnusedManagedPolicies Job](#customizable-analysis-tasks-for-the-awsunusedmanagedpolicies-job) topic for additional information. - Unused Managed Policy Summary – Summary by AWS Organization of unused managed policies. Creates @@ -69,4 +69,4 @@ produces the following preconfigured report: | Report | Description | Default Tags | Report Element | | ----------------------- | --------------------------------------------------------------------------- | ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Unused Managed Policies | This report identifies policies that are not assigned to any group or user. | None | This report is comprised of the following elements:
  • Stacked Bar Chart – Displays unused managed policies by account
  • Table – Shows unused managed policies by account
  • Table – Provides details on unused managed policies
| +| Unused Managed Policies | This report identifies policies that aren't assigned to any group or user. | None | This report is comprised of the following elements:
  • Stacked Bar Chart – Displays unused managed policies by account
  • Table – Shows unused managed policies by account
  • Table – Provides details on unused managed policies
| diff --git a/docs/accessanalyzer/12.0/solutions/aws/policies/aws_userpolicies.md b/docs/accessanalyzer/12.0/solutions/aws/policies/aws_userpolicies.md index d8f14e716b..4309176066 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/policies/aws_userpolicies.md +++ b/docs/accessanalyzer/12.0/solutions/aws/policies/aws_userpolicies.md @@ -15,7 +15,7 @@ Navigate to the **AWS** > **5.Policies** > **AWS_UserPolicies** > **Configure** **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/aws/policies/overview.md b/docs/accessanalyzer/12.0/solutions/aws/policies/overview.md index cafb7b530a..f53182bdfe 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/policies/overview.md +++ b/docs/accessanalyzer/12.0/solutions/aws/policies/overview.md @@ -22,8 +22,8 @@ The 5.Policies job group is comprised of: - [AWS_SensitivePolicies Job](/docs/accessanalyzer/12.0/solutions/aws/policies/aws_sensitivepolicies.md) – Provides details on users, groups, and roles as well as the policies granting them sensitive permissions - [AWS_UnusedManagedPolicies Job](/docs/accessanalyzer/12.0/solutions/aws/policies/aws_unusedmanagedpolicies.md) – Provides details on customer - managed policies that exist in the AWS Organization. Optionally, AWS managed policies can be - included by changing the @IncludeAWSManaged parameter on the analysis task. + managed policies that exist in the AWS Organization. Optionally, include AWS managed policies + by changing the @IncludeAWSManaged parameter on the analysis task. - [AWS_UserPolicies Job](/docs/accessanalyzer/12.0/solutions/aws/policies/aws_userpolicies.md) – Provides details outlining user policy assignment. This includes where the policy is assigned, directly or at a group level, and if the policy assignment has been duplicated. diff --git a/docs/accessanalyzer/12.0/solutions/aws/recommended.md b/docs/accessanalyzer/12.0/solutions/aws/recommended.md index 4691959fb1..b48abae736 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/aws/recommended.md @@ -6,9 +6,9 @@ sidebar_position: 10 # Recommended Configuration for the AWS Solution -The AWS Solution is configured to inherit settings from the global Settings node. The Connection -Profile must be assigned before job execution. Once it is assigned to the job group, it can be run -directly or scheduled. +The AWS Solution is configured to inherit settings from the global Settings node. You must assign +the Connection Profile before job execution. After you assign it to the job group, you can run it +directly or schedule it. **Dependencies** @@ -22,25 +22,25 @@ For AWS IAM Auditing: [Target Amazon Web Service Requirements, Permissions, and Ports](/docs/accessanalyzer/12.0/requirements/aws/target.md) topic for additional information on permissions -Some of the 0.Collection job group queries can be scoped to target specific S3 Objects. However, it -is necessary for the SA_AWS_Instances table to be populated before attempting to scope the queries. -Therefore, the AWS_S3Scan job must be manually executed before attempting to scope the S3 queries. +You can scope some of the 0.Collection job group queries to target specific S3 objects. However, +populate the SA_AWS_Instances table before scoping the queries. Therefore, manually run the +AWS_S3Scan job before scoping the S3 queries. **Target Host** -The AWS Data Collector identifies AWS instances via the created Roles and therefore does not require -a host list to be assigned. No target host is required (assign Local Host). +The AWS Data Collector identifies AWS instances via the created Roles and therefore doesn't require +you to assign a host list. No target host is required (assign Local Host). **Connection Profile** The AWS Data Collector requires a specific set of permissions. The account used can be either a Web -Services (JWT) account or an Amazon Web Services account. Once the account has been provisioned, +Services (JWT) account or an Amazon Web Services account. After you provision the account, create a custom Connection Profile containing the credentials for the targeted environment. See the [Amazon Web Services for User Credentials](/docs/accessanalyzer/12.0/admin/settings/connection/create/aws.md) topic for additional information. The Connection Profile is assigned under the **AWS** > **Settings** > **Connection** node. It is set -to **Use Default Profile**, as configured at the global Settings level. However, if this is not the +to **Use Default Profile**, as configured at the global Settings level. However, if this isn't the Connection Profile with the necessary permissions for targeting the AWS instances, click the **Select one of the following user defined profiles** option and select the appropriate Connection Profile. @@ -50,15 +50,15 @@ on creating a Connection Profile. **Access Token** -Creating the Connection Profile requires having the **Access Key ID** and the **Secret Access Key** -that was generated by the Amazon Web Services application. See the +Creating the Connection Profile requires the **Access Key ID** and the **Secret Access Key** +generated by the Amazon Web Services application. See the [Configure AWS for Scans](/docs/accessanalyzer/12.0/requirements/aws/configurescans.md) topic for additional information. **Schedule Frequency** Schedule the AWS job group to run weekly or daily, depending on the amount of data in the -environment. If there are frequent AWS changes within the target environment, then it can be -executed more often. It is best to rerun it anytime AWS changes might have occurred. +environment. If the target environment has frequent AWS changes, run it more often. Rerun it +anytime AWS changes might have occurred. **History Retention** @@ -70,8 +70,8 @@ Not supported. **Run Order** -The jobs in the 0.Collection job group must be run first and in order. The other job groups can be -run in any order, together or individually, after running the 0.Collection job group. +Run the jobs in the 0.Collection job group first and in order. You can run the other job groups in +any order, together or individually, after running the 0.Collection job group. :::info Run the solution at the top level. @@ -80,35 +80,35 @@ Run the solution at the top level. **Run at the Solution Level** -The jobs in the AWS job group should be run together and in order by running the entire solution, -instead of the individual jobs. +Run the jobs in the AWS job group together and in order by running the entire solution, instead of +the individual jobs. **Run at the Job Group Level** -For environments with a large amount of S3 data, it may be desirable to run the 3.AWS_S3Scan job and -the 4.AWS_S3SDDScan job less frequently than the other jobs in the 0.Collection job group. +For environments with a large amount of S3 data, run the 3.AWS_S3Scan job and the 4.AWS_S3SDDScan +job less frequently than the other jobs in the 0.Collection job group. **Query Configuration** -The following queries in the 0.Collection job group require the created AWS Roles to be added to the +The following queries in the 0.Collection job group require you to add the created AWS Roles to the Login Roles page: - [1.AWS_OrgScan Job](/docs/accessanalyzer/12.0/solutions/aws/collection/1.aws_orgscan.md) - [2.AWS_S3Scan Job](/docs/accessanalyzer/12.0/solutions/aws/collection/2.aws_s3scan.md) - [3.AWS_IAMScan Job](/docs/accessanalyzer/12.0/solutions/aws/collection/3.aws_iamscan.md) -The following queries in the 0.Collection job group can be modified to limit the depth of the scan: +You can modify the following queries in the 0.Collection job group to limit the depth of the scan: - [2.AWS_S3Scan Job](/docs/accessanalyzer/12.0/solutions/aws/collection/2.aws_s3scan.md) - [4.AWS_S3SDDScan Job](/docs/accessanalyzer/12.0/solutions/aws/collection/4.aws_s3sddscan.md) **Analysis Configuration** -This solution can be run with the default analysis configuration. However, the following parameters -can be modified: +You can run this solution with the default analysis configuration. However, you can modify the +following parameters: - The `@STALETHRESHOLD` parameter determines the number of days after which content is considered - stale. It is set to default of 60 days. The `@STALETHRESHOLD` parameter can be customized in the + stale. It is set to default of 60 days. You can customize the `@STALETHRESHOLD` parameter in the following analysis tasks: - **2. Users** > **AWS_StaleUsers** > **Stale Users** Analysis Task diff --git a/docs/accessanalyzer/12.0/solutions/aws/roles/aws_roles.md b/docs/accessanalyzer/12.0/solutions/aws/roles/aws_roles.md index 7de716ee3d..75c48f1cf7 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/roles/aws_roles.md +++ b/docs/accessanalyzer/12.0/solutions/aws/roles/aws_roles.md @@ -14,7 +14,7 @@ Navigate to the **AWS** > **4.Roles** > **AWS_Roles** > **Configure** node and s to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/aws/roles/aws_staleroles.md b/docs/accessanalyzer/12.0/solutions/aws/roles/aws_staleroles.md index a483cd2f26..596476fb71 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/roles/aws_staleroles.md +++ b/docs/accessanalyzer/12.0/solutions/aws/roles/aws_staleroles.md @@ -6,23 +6,23 @@ sidebar_position: 20 # AWS_StaleRoles Job -The AWS_StaleRoles job provides details on roles that are considered stale. Highlighting roles that -have not been used in more than 60 days and those that have never been used. The 60 day parameter is +The AWS_StaleRoles job provides details on roles that are considered stale, highlighting roles that +haven't been used in more than 60 days and those that have never been used. The 60 day parameter is configurable. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/12.0/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. The AWS_StaleRoles job has the following configurable parameter: -- Days without login to consider an account stale +- Days without log in to consider an account stale See the -[Customizable Analysis Tasks for the AWS_StaleRoles Job](#customizable-analysis-tasks-for-the-aws_staleroles-job) +[Customizable Analysis Tasks for the AWS_StaleRoles Job](#customizable-analysis-tasks-for-the-awsstaleroles-job) topic for additional information. ## Analysis Tasks for the AWS_StaleRoles Job @@ -31,7 +31,7 @@ Navigate to the **AWS** > **4.Roles** > **AWS_StaleRoles** > **Configure** node **Analysis** to view the analysis tasks. :::warning -Do not deselect the selected analysis tasks. The analysis tasks are preconfigured for +Don't deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. Only modify the analysis tasks listed in the customizable analysis tasks section. ::: @@ -43,9 +43,9 @@ The following analysis tasks are selected by default: - Stale Role Details – Highlights the roles in AWS that are considered stale. Creates the AWS_StaleRole_Details table accessible under the job’s Results node. - - The number of days without login to consider an account stale can be customized. By default it - is set to 60. See the - [Customizable Analysis Tasks for the AWS_StaleRoles Job](#customizable-analysis-tasks-for-the-aws_staleroles-job) + - You can customize the number of days without a login to consider an account stale. By default + it is set to 60. See the + [Customizable Analysis Tasks for the AWS_StaleRoles Job](#customizable-analysis-tasks-for-the-awsstaleroles-job) topic for additional information. - Stale Role Summary – Summarizes stale roles by AWS Account. Creates the AWS_StaleRole_Summary @@ -57,7 +57,7 @@ The default values for parameters that can be customized are: | Analysis Task | Customizable Parameter Name | Default Value | Value Indicates | | ------------------ | --------------------------- | ------------- | ------------------------------------------------ | -| Stale Role Details | @StaleThreshold | 60 | Days without login to consider an account stale. | +| Stale Role Details | @StaleThreshold | 60 | Days without log in to consider an account stale. | See the [Configure the Customizable Parameters in an Analysis Task](/docs/accessanalyzer/12.0/admin/jobs/job/configure/analysis/analysiscustomizableparameters.md) diff --git a/docs/accessanalyzer/12.0/solutions/aws/roles/overview.md b/docs/accessanalyzer/12.0/solutions/aws/roles/overview.md index 932202b662..6c649f7632 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/roles/overview.md +++ b/docs/accessanalyzer/12.0/solutions/aws/roles/overview.md @@ -13,6 +13,6 @@ The 4.Roles job group provides details on roles in the AWS IAM environment. The 4.Roles job group is comprised of: - [AWS_Roles Job](/docs/accessanalyzer/12.0/solutions/aws/roles/aws_roles.md) – Provides details on roles in the AWS IAM environment -- [AWS_StaleRoles Job](/docs/accessanalyzer/12.0/solutions/aws/roles/aws_staleroles.md) – Provides details on roles that are considered stale. - Highlighting roles that have not been used in more than 60 days and those that have never been +- [AWS_StaleRoles Job](/docs/accessanalyzer/12.0/solutions/aws/roles/aws_staleroles.md) – Provides details on roles that are considered stale, + highlighting roles that haven't been used in more than 60 days and those that have never been used. diff --git a/docs/accessanalyzer/12.0/solutions/aws/s3content/aws_s3buckets.md b/docs/accessanalyzer/12.0/solutions/aws/s3content/aws_s3buckets.md index c1f4db1a3e..eccdfda6fe 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/s3content/aws_s3buckets.md +++ b/docs/accessanalyzer/12.0/solutions/aws/s3content/aws_s3buckets.md @@ -14,7 +14,7 @@ Navigate to the **AWS** > **7.S3 Content** > **AWS_S3Buckets** > **Configure** n **Analysis** to view the analysis task. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/aws/s3content/aws_s3buckettags.md b/docs/accessanalyzer/12.0/solutions/aws/s3content/aws_s3buckettags.md index 245f17d910..c95d133731 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/s3content/aws_s3buckettags.md +++ b/docs/accessanalyzer/12.0/solutions/aws/s3content/aws_s3buckettags.md @@ -6,8 +6,8 @@ sidebar_position: 20 # AWS_S3BucketTags Job -The AWS_S3BucketTags job identifies tags associated with AWS S3 Buckets. Tagging can be helpful to -identify the storage class or purpose of a bucket and can be used in AWS IAM Policy assignments. +The AWS_S3BucketTags job identifies tags associated with AWS S3 Buckets. Tagging can help identify +the storage class or purpose of a bucket, and you can use tags in AWS IAM Policy assignments. ## Analysis Tasks for the AWS_S3BucketTagsJob @@ -15,7 +15,7 @@ Navigate to the **AWS** > **7.S3 Content** > **AWS_S3BucketTags** > **Configure* **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/aws/s3content/overview.md b/docs/accessanalyzer/12.0/solutions/aws/s3content/overview.md index eb05d44b4f..b75e89bd6b 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/s3content/overview.md +++ b/docs/accessanalyzer/12.0/solutions/aws/s3content/overview.md @@ -15,5 +15,5 @@ The 7.S3 Content job group is comprised of: - [AWS_S3Buckets Job](/docs/accessanalyzer/12.0/solutions/aws/s3content/aws_s3buckets.md) – Provides a summary of AWS S3 buckets including total object size and counts - [AWS_S3BucketTags Job](/docs/accessanalyzer/12.0/solutions/aws/s3content/aws_s3buckettags.md) – Identifies tags associated with AWS S3 Buckets. - Tagging can be helpful to identify the storage class or purpose of a bucket and can be used in AWS + Tagging can help identify the storage class or purpose of a bucket, and you can use tags in AWS IAM Policy assignments. diff --git a/docs/accessanalyzer/12.0/solutions/aws/s3permissions/aws_brokeninheritance.md b/docs/accessanalyzer/12.0/solutions/aws/s3permissions/aws_brokeninheritance.md index 45288e202d..12ba39f98a 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/s3permissions/aws_brokeninheritance.md +++ b/docs/accessanalyzer/12.0/solutions/aws/s3permissions/aws_brokeninheritance.md @@ -15,7 +15,7 @@ Navigate to the **AWS** > **6.S3 Permissions** > **AWS_BrokenInheritance** > **C select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/aws/s3permissions/aws_effectivepermissions.md b/docs/accessanalyzer/12.0/solutions/aws/s3permissions/aws_effectivepermissions.md index 51a7fbe19c..5014e3f031 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/s3permissions/aws_effectivepermissions.md +++ b/docs/accessanalyzer/12.0/solutions/aws/s3permissions/aws_effectivepermissions.md @@ -15,7 +15,7 @@ Navigate to the **AWS** > **6.S3 Permissions** > **AWS_EffectivePermissions** > and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/aws/s3permissions/aws_openbuckets.md b/docs/accessanalyzer/12.0/solutions/aws/s3permissions/aws_openbuckets.md index e4703ed5a8..bb2816b376 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/s3permissions/aws_openbuckets.md +++ b/docs/accessanalyzer/12.0/solutions/aws/s3permissions/aws_openbuckets.md @@ -15,7 +15,7 @@ Navigate to the **AWS** > **6.S3 Permissions** > **AWS_OpenBuckets** > **Configu **Analysis** to view the analysis task. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/aws/sensitivedata/aws_sensitivedata.md b/docs/accessanalyzer/12.0/solutions/aws/sensitivedata/aws_sensitivedata.md index 9d3b828e38..e586a57591 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/sensitivedata/aws_sensitivedata.md +++ b/docs/accessanalyzer/12.0/solutions/aws/sensitivedata/aws_sensitivedata.md @@ -15,7 +15,7 @@ Navigate to the **AWS** > **8.S3 Sensitive Data** > **AWS_SensitiveData** > **Co select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/aws/sensitivedata/aws_sensitivedata_permissions.md b/docs/accessanalyzer/12.0/solutions/aws/sensitivedata/aws_sensitivedata_permissions.md index de4f813c6d..9d6fa1eca8 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/sensitivedata/aws_sensitivedata_permissions.md +++ b/docs/accessanalyzer/12.0/solutions/aws/sensitivedata/aws_sensitivedata_permissions.md @@ -15,7 +15,7 @@ Navigate to the **AWS** > **8.S3 Sensitive Data** > **AWS_SensitiveData_Permissi **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/aws/users/aws_accesskeys.md b/docs/accessanalyzer/12.0/solutions/aws/users/aws_accesskeys.md index b1fe3e687e..e4695b637c 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/users/aws_accesskeys.md +++ b/docs/accessanalyzer/12.0/solutions/aws/users/aws_accesskeys.md @@ -15,7 +15,7 @@ Navigate to the **AWS** > **2.Users** > **AWS_AccessKeys** > **Configure** node **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/aws/users/aws_mfastatus.md b/docs/accessanalyzer/12.0/solutions/aws/users/aws_mfastatus.md index fb673f096b..93197355f8 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/users/aws_mfastatus.md +++ b/docs/accessanalyzer/12.0/solutions/aws/users/aws_mfastatus.md @@ -15,7 +15,7 @@ Navigate to the **AWS** > **2.Users** > **AWS_MFAStatus** > **Configure** node a **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/aws/users/aws_rootaccounts.md b/docs/accessanalyzer/12.0/solutions/aws/users/aws_rootaccounts.md index 5e3cc53de7..a1235037a0 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/users/aws_rootaccounts.md +++ b/docs/accessanalyzer/12.0/solutions/aws/users/aws_rootaccounts.md @@ -15,7 +15,7 @@ Navigate to the **AWS** > **2.Users** > **AWS_RootAccounts** > **Configure** nod **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/aws/users/aws_staleusers.md b/docs/accessanalyzer/12.0/solutions/aws/users/aws_staleusers.md index 061f8a17aa..c2be6b9ca3 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/users/aws_staleusers.md +++ b/docs/accessanalyzer/12.0/solutions/aws/users/aws_staleusers.md @@ -11,7 +11,7 @@ used, highlighting those over specified number of days (default 60) or that have ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/12.0/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -21,7 +21,7 @@ The AWS_StaleUsers job has the following configurable parameter: - Number of days before considering a user stale See the -[Customizable Analysis Tasks for the AWS_StaleUsers Job](#customizable-analysis-tasks-for-the-aws_staleusers-job) +[Customizable Analysis Tasks for the AWS_StaleUsers Job](#customizable-analysis-tasks-for-the-awsstaleusers-job) topic for additional information. ## Analysis Tasks for the AWS_StaleUsers Job @@ -30,7 +30,7 @@ Navigate to the **AWS** > **2.Users** > **AWS_StaleUsers** > **Configure** node **Analysis** to view the analysis tasks. :::warning -Do not deselect the selected analysis tasks. The analysis tasks are preconfigured for +Don't deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. Only modify the analysis tasks listed in the customizable analysis tasks section. ::: @@ -42,8 +42,8 @@ The following analysis tasks are selected by default: - Stale Users – Identifies user accounts that have not been logged in to in the last 60 days. Creates the AWS_StaleUser_Details table accessible under the job’s Results node. - - The number of days can be customized from the default value of 60. See the - [Customizable Analysis Tasks for the AWS_StaleUsers Job](#customizable-analysis-tasks-for-the-aws_staleusers-job) + - You can customize the number of days from the default value of 60. See the + [Customizable Analysis Tasks for the AWS_StaleUsers Job](#customizable-analysis-tasks-for-the-awsstaleusers-job) topic for additional information. - Stale User Summary – Summarizes stale users in AWS. Creates the AWS_StaleUser_Summary table diff --git a/docs/accessanalyzer/12.0/solutions/box/activity/forensics/box_deletions.md b/docs/accessanalyzer/12.0/solutions/box/activity/forensics/box_deletions.md index 3ca24b514a..7c7c8742fa 100644 --- a/docs/accessanalyzer/12.0/solutions/box/activity/forensics/box_deletions.md +++ b/docs/accessanalyzer/12.0/solutions/box/activity/forensics/box_deletions.md @@ -16,7 +16,7 @@ Navigate to **Box** > **1.Activity** > **Forensics** > **Box_Deletions** > **Con select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/box/activity/forensics/box_downloads.md b/docs/accessanalyzer/12.0/solutions/box/activity/forensics/box_downloads.md index 130d18d9de..5cdb9604b6 100644 --- a/docs/accessanalyzer/12.0/solutions/box/activity/forensics/box_downloads.md +++ b/docs/accessanalyzer/12.0/solutions/box/activity/forensics/box_downloads.md @@ -15,7 +15,7 @@ Navigate to **Box** > **1.Activity** > **Forensics** > **Box_Downloads** > **Con select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/box/activity/forensics/box_externaluseractivity.md b/docs/accessanalyzer/12.0/solutions/box/activity/forensics/box_externaluseractivity.md index a504f231c2..9dbf63cb62 100644 --- a/docs/accessanalyzer/12.0/solutions/box/activity/forensics/box_externaluseractivity.md +++ b/docs/accessanalyzer/12.0/solutions/box/activity/forensics/box_externaluseractivity.md @@ -17,7 +17,7 @@ Navigate to **Box** > **1.Activity** > **Forensics** > **Box_ExternalUserActivit node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/box/activity/forensics/box_externalusercollaborations.md b/docs/accessanalyzer/12.0/solutions/box/activity/forensics/box_externalusercollaborations.md index c83dd9d657..6cd5ec3138 100644 --- a/docs/accessanalyzer/12.0/solutions/box/activity/forensics/box_externalusercollaborations.md +++ b/docs/accessanalyzer/12.0/solutions/box/activity/forensics/box_externalusercollaborations.md @@ -16,7 +16,7 @@ Navigate to **Box** > **1.Activity** > **Forensics** > **Box_ExternalUserCollabo **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/box/activity/forensics/box_permissionchanges.md b/docs/accessanalyzer/12.0/solutions/box/activity/forensics/box_permissionchanges.md index 78eb34d876..6cb9341975 100644 --- a/docs/accessanalyzer/12.0/solutions/box/activity/forensics/box_permissionchanges.md +++ b/docs/accessanalyzer/12.0/solutions/box/activity/forensics/box_permissionchanges.md @@ -6,7 +6,7 @@ sidebar_position: 50 # Box_PermissionChanges Job -The Box_PermissionChannges Job provides details on permission changes that have occurred over the +The Box_PermissionChanges Job provides details on permission changes that have occurred over the past 30 days. ## Analysis Tasks for the Box_PermissionChanges Job @@ -15,7 +15,7 @@ Navigate to **Box** > **1.Activity** > **Forensics** > **Box_PermissionChanges** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/box/activity/forensics/box_sharing.md b/docs/accessanalyzer/12.0/solutions/box/activity/forensics/box_sharing.md index 6ad9614d8d..37bd780b36 100644 --- a/docs/accessanalyzer/12.0/solutions/box/activity/forensics/box_sharing.md +++ b/docs/accessanalyzer/12.0/solutions/box/activity/forensics/box_sharing.md @@ -14,7 +14,7 @@ Navigate to **Box** > **1.Activity** > **Forensics** > **Box_Sharing** > **Confi select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/box/activity/forensics/overview.md b/docs/accessanalyzer/12.0/solutions/box/activity/forensics/overview.md index 225d40e890..ead4e8db5e 100644 --- a/docs/accessanalyzer/12.0/solutions/box/activity/forensics/overview.md +++ b/docs/accessanalyzer/12.0/solutions/box/activity/forensics/overview.md @@ -23,7 +23,7 @@ The Forensics Job Group is comprised of: user activity which has occurred over the past 30 days - [Box_ExternalUserCollaborations Job](/docs/accessanalyzer/12.0/solutions/box/activity/forensics/box_externalusercollaborations.md) – Identifies collaboration invites sent to external users. These collaborations should be reviewed to ensure sensitive data - is not being shared outside of your organization. + isn't being shared outside of your organization. - [Box_PermissionChanges Job](/docs/accessanalyzer/12.0/solutions/box/activity/forensics/box_permissionchanges.md) – Provides details on permission changes that have occurred over the past 30 days - [Box_Sharing Job](/docs/accessanalyzer/12.0/solutions/box/activity/forensics/box_sharing.md) – Provides details on sharing activity that has occurred over diff --git a/docs/accessanalyzer/12.0/solutions/box/activity/overview.md b/docs/accessanalyzer/12.0/solutions/box/activity/overview.md index eba6e719e1..e518d609aa 100644 --- a/docs/accessanalyzer/12.0/solutions/box/activity/overview.md +++ b/docs/accessanalyzer/12.0/solutions/box/activity/overview.md @@ -6,9 +6,8 @@ sidebar_position: 30 # 1.Activity Job Group -The **Box** > **1.Activity** Job Group identifies long term trends of activity providing insight -into user activity, usage statistics, and suspicious behavior identifies long-term trends of -activity providing insight into user activity, usage statistics, and suspicious behavior. +The **Box** > **1.Activity** Job Group identifies long-term trends of activity, providing insight +into user activity, usage statistics, and suspicious behavior. ![1.Activity Job Group in the Jobs Tree](/images/accessanalyzer/12.0/solutions/box/activity/jobstree.webp) diff --git a/docs/accessanalyzer/12.0/solutions/box/activity/suspiciousactivity/box_failedlogins.md b/docs/accessanalyzer/12.0/solutions/box/activity/suspiciousactivity/box_failedlogins.md index bd75e92241..8760dbc54c 100644 --- a/docs/accessanalyzer/12.0/solutions/box/activity/suspiciousactivity/box_failedlogins.md +++ b/docs/accessanalyzer/12.0/solutions/box/activity/suspiciousactivity/box_failedlogins.md @@ -16,7 +16,7 @@ Navigate to **Box** > **1.Activity** > **Suspicious Activity** > **Box_FailedLog **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/box/activity/suspiciousactivity/box_firsttimefolderaccess.md b/docs/accessanalyzer/12.0/solutions/box/activity/suspiciousactivity/box_firsttimefolderaccess.md index 153df09f1e..f320c2ea01 100644 --- a/docs/accessanalyzer/12.0/solutions/box/activity/suspiciousactivity/box_firsttimefolderaccess.md +++ b/docs/accessanalyzer/12.0/solutions/box/activity/suspiciousactivity/box_firsttimefolderaccess.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **Box** > **1.Activity** > **Suspic **Box_FirstTimeFolderAccess** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/box/activity/suspiciousactivity/box_unusualdownloadactivity.md b/docs/accessanalyzer/12.0/solutions/box/activity/suspiciousactivity/box_unusualdownloadactivity.md index 479253fa70..7f93de2f8a 100644 --- a/docs/accessanalyzer/12.0/solutions/box/activity/suspiciousactivity/box_unusualdownloadactivity.md +++ b/docs/accessanalyzer/12.0/solutions/box/activity/suspiciousactivity/box_unusualdownloadactivity.md @@ -16,7 +16,7 @@ Navigate to **Box** > **1.Activity** > **Suspicious Activity** > **Box_UnusualDo **Configure** node and select **Analysis** to view analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -33,4 +33,4 @@ produces the following pre-configured report: | Report | Description | Default Tags | Report Elements | | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Unusual Download Activity | This report provides insight into download activity that deviates from the normal range of expected downloads.  This is determined by using historical data for each file. | None | This report is comprised of two elements:
  • Bar Chart – Displays top 5 most recent unusual download activity
  • Table – Provides details on unusual download activity
| +| Unusual Download Activity | This report provides insight into download activity that deviates from the normal range of expected downloads. This is determined by using historical data for each file. | None | This report is comprised of two elements:
  • Bar Chart – Displays top 5 most recent unusual download activity
  • Table – Provides details on unusual download activity
| diff --git a/docs/accessanalyzer/12.0/solutions/box/activity/suspiciousactivity/box_unusualuseractivity.md b/docs/accessanalyzer/12.0/solutions/box/activity/suspiciousactivity/box_unusualuseractivity.md index 61309f287d..bf34360a48 100644 --- a/docs/accessanalyzer/12.0/solutions/box/activity/suspiciousactivity/box_unusualuseractivity.md +++ b/docs/accessanalyzer/12.0/solutions/box/activity/suspiciousactivity/box_unusualuseractivity.md @@ -16,7 +16,7 @@ Navigate to **Box** > **1.Activity** > **Suspicious Activity** > **Box_UnusualUs **Configure** node and select **Analysis** to view analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -33,4 +33,4 @@ pre-configured report: | Report | Description | Default Tags | Report Elements | | --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Unusual User Activity | This report provides insight into user activity that deviates from the normal range of expected activity.  This is determined by using historical data for each user. | None | This report is comprised of two elements:
  • Bar Chart – Displays top 5 most recent unusual user activity
  • Table – Provides details on unusual user activity
| +| Unusual User Activity | This report provides insight into user activity that deviates from the normal range of expected activity. This is determined by using historical data for each user. | None | This report is comprised of two elements:
  • Bar Chart – Displays top 5 most recent unusual user activity
  • Table – Provides details on unusual user activity
| diff --git a/docs/accessanalyzer/12.0/solutions/box/activity/suspiciousactivity/box_weekendactivity.md b/docs/accessanalyzer/12.0/solutions/box/activity/suspiciousactivity/box_weekendactivity.md index cb69070467..e93326fd52 100644 --- a/docs/accessanalyzer/12.0/solutions/box/activity/suspiciousactivity/box_weekendactivity.md +++ b/docs/accessanalyzer/12.0/solutions/box/activity/suspiciousactivity/box_weekendactivity.md @@ -16,7 +16,7 @@ Navigate to **Box** > **1.Activity** > **Suspicious Activity** > **Box_WeekendAc **Configure** node and select **Analysis** to view analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/box/activity/usagestatistics/box_folders_mostactive.md b/docs/accessanalyzer/12.0/solutions/box/activity/usagestatistics/box_folders_mostactive.md index 9854b4a062..4bccd46f99 100644 --- a/docs/accessanalyzer/12.0/solutions/box/activity/usagestatistics/box_folders_mostactive.md +++ b/docs/accessanalyzer/12.0/solutions/box/activity/usagestatistics/box_folders_mostactive.md @@ -15,7 +15,7 @@ Navigate to **Box** > **1.Activity** > **Usage Statistics** > **Box_Folders_Most **Configure** node and select **Analysis** to view analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/box/activity/usagestatistics/box_folders_stale.md b/docs/accessanalyzer/12.0/solutions/box/activity/usagestatistics/box_folders_stale.md index f0f75c479b..6f9162e240 100644 --- a/docs/accessanalyzer/12.0/solutions/box/activity/usagestatistics/box_folders_stale.md +++ b/docs/accessanalyzer/12.0/solutions/box/activity/usagestatistics/box_folders_stale.md @@ -16,7 +16,7 @@ Navigate to **Box** > **1.Activity** > **Usage Statistics** > **Box_Folders_Stal node and select **Analysis** to view analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/box/activity/usagestatistics/box_users_mostactive.md b/docs/accessanalyzer/12.0/solutions/box/activity/usagestatistics/box_users_mostactive.md index 14f0f5d183..73de4e74b6 100644 --- a/docs/accessanalyzer/12.0/solutions/box/activity/usagestatistics/box_users_mostactive.md +++ b/docs/accessanalyzer/12.0/solutions/box/activity/usagestatistics/box_users_mostactive.md @@ -15,7 +15,7 @@ Navigate to **Box** > **1.Activity** > **Usage Statistics** > **Box_Users_MostAc **Configure** node and select **Analysis** to view analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/box/box_access.md b/docs/accessanalyzer/12.0/solutions/box/box_access.md index d551bdf8ac..c18531149b 100644 --- a/docs/accessanalyzer/12.0/solutions/box/box_access.md +++ b/docs/accessanalyzer/12.0/solutions/box/box_access.md @@ -7,7 +7,7 @@ sidebar_position: 50 # Box_Access Job The Box_Access Job analyzes access granted to users and groups in an organization's Box environment -in order to report on effective access rights, file-level permissions, and inactive access rights +to report on effective access rights, file-level permissions, and inactive access rights that can be revoked. ## Analysis Tasks for the Box_Access Job @@ -16,7 +16,7 @@ Navigate to **Box** > **Box_Access** > **Configure** node and select **Analysis* tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/box/box_groupmembership.md b/docs/accessanalyzer/12.0/solutions/box/box_groupmembership.md index 75d0ac1ce8..1b0d003349 100644 --- a/docs/accessanalyzer/12.0/solutions/box/box_groupmembership.md +++ b/docs/accessanalyzer/12.0/solutions/box/box_groupmembership.md @@ -15,7 +15,7 @@ Navigate to **Box** > **Box_GroupMembership** > **Configure** node and select ** analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/box/collection/1-box_access_scans.md b/docs/accessanalyzer/12.0/solutions/box/collection/1-box_access_scans.md index 5225f3a691..35fa8f5b90 100644 --- a/docs/accessanalyzer/12.0/solutions/box/collection/1-box_access_scans.md +++ b/docs/accessanalyzer/12.0/solutions/box/collection/1-box_access_scans.md @@ -1,25 +1,24 @@ # 1-Box_Access Scans Job -The 1-Box_Access Scans Job collects the data which will be further analyzed in order to provide -details on Box access rights, policies, configurations, and content. +The 1-Box_Access Scans Job collects data for further analysis, providing details on Box access +rights, policies, configurations, and content. ## Queries for the 1-Box_Access Scans Job The Scan Query uses the Box Data Collector to target all Box hosts and has been preconfigured to use -the Scan Box Permissions Category. If this query is not configured but has the access token, a full -scan of all folders at full depth is performed. Optionally, configure the query to limit the depth +the Scan Box Permissions Category. If this query isn't configured but has the access token, the job +performs a full scan of all folders at full depth. Optionally, configure the query to limit the depth of the scan. ![Queries for the 1-Box_Access Scans Job](/images/accessanalyzer/12.0/solutions/box/collection/accessqueries.webp) The 1-Box_Access Scans Job has the following queries: -- Scan Query – Collects access data which will be further analyzed in order to provide details on - Box access rights, policies, configurations, and content +- Scan Query – Collects access data for further analysis, providing details on Box access rights, + policies, configurations, and content -Prior to the first execution, it is necessary to authenticate to the targeted Box environment. This -is done on the Authenticate page of the Scan query. Additionally, the following default -configurations are commonly customized: +Before the first execution, authenticate to the targeted Box environment on the Authenticate page of +the Scan query. Additionally, the following default configurations are commonly customized: - Exclusions page: @@ -29,54 +28,54 @@ configurations are commonly customized: - Not scoped -See the [Configure the 1-Box_Access Scans Job](#configure-the-1-box_access-scans-job) section for +See the [Configure the 1-Box_Access Scans Job](#configure-the-1-boxaccess-scans-job) section for instructions. ### Configure the 1-Box_Access Scans Job -The 1-Box_Access Scans Job contains the Scan Query. Follow the steps to configure the query. +The 1-Box_Access Scans Job contains the Scan Query. To configure the query, complete the following steps. **Step 1 –** Navigate to the **Box** > **0.Collection** > **1-Box_Access Scans** > **Configure** node and select **Queries**. -**Step 1 –** In the Query Selection view, select the Scan Query and click **Query Properties**. The +**Step 2 –** In the Query Selection view, select the Scan Query and click **Query Properties**. The Query Properties window opens. -**Step 2 –** Select the **Data Source** tab, and click **Configure**. The Box Data Collector Wizard +**Step 3 –** Select the **Data Source** tab, and click **Configure**. The Box Data Collector Wizard opens. ![Box Data Collector Wizard Exclusions page](/images/accessanalyzer/12.0/solutions/box/collection/accessexclusions.webp) -**Step 3 –** On the Exclusions Page: +**Step 4 –** On the Exclusions Page: - Add folders to be excluded - Add folders to be included (scope scan to only these folders) ![Box Data Collector Wizard Additional Scoping page](/images/accessanalyzer/12.0/solutions/box/collection/accessadditionalscoping.webp) -**Step 4 –** On the Additional Scoping page: +**Step 5 –** On the Additional Scoping page: - Optionally, select this option to limit the depth of the scan across the targeted Box account ![Box Data Collector Wizard Scope by User page](/images/accessanalyzer/12.0/solutions/box/collection/accessuserscope.webp) -**Step 5 –** On the Scope By User Page: +**Step 6 –** On the Scope By User Page: - Optionally, limit the scope of the scan to specified users by providing a CSV file ![Box Data Collector Wizard Authenticate page](/images/accessanalyzer/12.0/solutions/box/collection/accessauthenticate.webp) -**Step 6 –** The Authenticate page is where the connection to the target Box environment is -configured. Click **Authorize** to launch the BoxLogin window and generate an authorization code. -This code allows Access Analyzer to report on the Box Enterprise. +**Step 7 –** On the Authenticate page, configure the connection to the target Box environment. Click +**Authorize** to launch the BoxLogin window and generate an authorization code. This code allows +Access Analyzer to report on the Box Enterprise. :::note -Authentication to the target Box environment only needs to be completed once, prior to the -first scan and only in one of the scan jobs. +You only need to complete authentication to the target Box environment once, before the first scan +and only in one of the scan jobs. ::: -**Step 7 –** Navigate to the Summary page, click **Finish** to save any setting modifications or +**Step 8 –** Navigate to the Summary page, click **Finish** to save any setting modifications or click **Cancel** if no changes were made. Then click **OK** to close the Query Properties window. The 1-Box_Access Scans Job will execute according to the connection settings configuration. diff --git a/docs/accessanalyzer/12.0/solutions/box/collection/1-box_activity_scans.md b/docs/accessanalyzer/12.0/solutions/box/collection/1-box_activity_scans.md index 26bc5e3fb1..f70f7779b4 100644 --- a/docs/accessanalyzer/12.0/solutions/box/collection/1-box_activity_scans.md +++ b/docs/accessanalyzer/12.0/solutions/box/collection/1-box_activity_scans.md @@ -1,7 +1,7 @@ # 1-Box_Activity Scans Job -The 1-Box_Activity Scans Job collects the data which will be further analyzed in order to provide -visibility into user activity events within Box. +The 1-Box_Activity Scans Job collects data for further analysis, providing visibility into user +activity events within Box. ## Queries for the 1-Box_Activity Scans Job @@ -12,13 +12,12 @@ the Scan Box Permissions Category. The 1-Box_Activity Scans Job has the following queries: -- Activity Scan – Collects activity data which will be further analyzed in order to provide - visibility into user activity events within Box. +- Activity Scan – Collects activity data for further analysis, providing visibility into user + activity events within Box. -Prior to the first execution, it is necessary to authenticate to the targeted Box environment if -this has not already been done when configuring the 1-Box_Access Scans Job. This is done on the -Authenticate page of the Activity Scan query. Additionally, the following default configurations are -commonly customized: +Before the first execution, authenticate to the targeted Box environment on the Authenticate page of +the Activity Scan query, unless you already completed this step when you configured the +1-Box_Access Scans Job. Additionally, the following default configurations are commonly customized: - Exclusions page: @@ -28,13 +27,13 @@ commonly customized: - Not scoped -See the [Configure the 1-Box_Activity Scans Job](#configure-the-1-box_activity-scans-job) section +See the [Configure the 1-Box_Activity Scans Job](#configure-the-1-boxactivity-scans-job) section for instructions. ### Configure the 1-Box_Activity Scans Job -The 1-Box_Activity Scans Job contains the Activity Scan Query. Follow the steps to configure the -query. +The 1-Box_Activity Scans Job contains the Activity Scan Query. To configure the +query, complete the following steps. **Step 1 –** Navigate to the **Box** > **0.Collection** > **1-Box_Activity Scans** > **Configure** node and select **Queries**. @@ -79,13 +78,13 @@ opens. ![Box Data Collector Wizard Authenticate page](/images/accessanalyzer/12.0/solutions/box/collection/activityauthenticate.webp) -**Step 9 –** The Authenticate page is where the connection to the target Box environment is -configured. Click **Authorize** to launch the BoxLogin window and generate an authorization code. -This code allows Access Analyzer to report on the Box Enterprise. +**Step 9 –** On the Authenticate page, configure the connection to the target Box environment. Click +**Authorize** to launch the BoxLogin window and generate an authorization code. This code allows +Access Analyzer to report on the Box Enterprise. :::note -Authentication to the target Box environment only needs to be completed once, prior to the -first scan and only in one of the scan jobs. +You only need to complete authentication to the target Box environment once, before the first scan +and only in one of the scan jobs. ::: diff --git a/docs/accessanalyzer/12.0/solutions/box/collection/2-box_import.md b/docs/accessanalyzer/12.0/solutions/box/collection/2-box_import.md index dcc939b73b..d5aac34f11 100644 --- a/docs/accessanalyzer/12.0/solutions/box/collection/2-box_import.md +++ b/docs/accessanalyzer/12.0/solutions/box/collection/2-box_import.md @@ -6,9 +6,9 @@ sidebar_position: 10 # 2-Box_Import Job -The 2-Box_Import Job takes the data that has been collected from the 1-Box_Access Scans Job and the -1-Box_Activity Scans Job and imports it to the Access Analyzer database to be analyzed in order to -provide detailed reports on Box access rights, policies, configurations, activities, and content. +The 2-Box_Import Job takes the data collected from the 1-Box_Access Scans Job and the +1-Box_Activity Scans Job and imports it into the Access Analyzer database for analysis, providing +detailed reports on Box access rights, policies, configurations, activities, and content. ## Queries for the 2-Box_Import Job @@ -19,6 +19,6 @@ Permissions Category. The 2-Box_Import Job has the following query: -- Import - Takes the data that has been collected from Box and imports it to the Access Analyzer - database to be analyzed in order to provide detailed reports on Box access rights, policies, - configurations, activities, and content. +- Import - Takes the data collected from Box and imports it into the Access Analyzer database for + analysis, providing detailed reports on Box access rights, policies, configurations, activities, + and content. diff --git a/docs/accessanalyzer/12.0/solutions/box/collection/overview.md b/docs/accessanalyzer/12.0/solutions/box/collection/overview.md index 5aea99df88..4b00c46471 100644 --- a/docs/accessanalyzer/12.0/solutions/box/collection/overview.md +++ b/docs/accessanalyzer/12.0/solutions/box/collection/overview.md @@ -6,17 +6,17 @@ sidebar_position: 20 # 0.Collection Job Group -The 0.Collection Job Group collects data which will be further analyzed in order to provide details -on Box access rights, policies, configurations, activities, and content. +The 0.Collection Job Group collects data for further analysis, providing details on Box access +rights, policies, configurations, activities, and content. ![Box > Collection Job Group in the Jobs Tree](/images/accessanalyzer/12.0/solutions/box/collection/jobstree.webp) The 0.Collection Job Group is comprised of: -- [1-Box_Access Scans Job](/docs/accessanalyzer/12.0/solutions/box/collection/1-box_access_scans.md) – Collects the data which will be further analyzed - in order to provide details on Box access rights, policies, configurations, and content -- [1-Box_Activity Scans Job](/docs/accessanalyzer/12.0/solutions/box/collection/1-box_activity_scans.md) – Collects the data which will be further - analyzed in order to provide visibility into user activity events within Box -- [2-Box_Import Job](/docs/accessanalyzer/12.0/solutions/box/collection/2-box_import.md) – Takes the data that has been collected from Box and imports - it to the Access Analyzer database to be analyzed in order to provide detailed reports on Box - access rights, policies, configurations, activities, and content +- [1-Box_Access Scans Job](/docs/accessanalyzer/12.0/solutions/box/collection/1-box_access_scans.md) – Collects data for further analysis, providing + details on Box access rights, policies, configurations, and content +- [1-Box_Activity Scans Job](/docs/accessanalyzer/12.0/solutions/box/collection/1-box_activity_scans.md) – Collects data for further analysis, providing + visibility into user activity events within Box +- [2-Box_Import Job](/docs/accessanalyzer/12.0/solutions/box/collection/2-box_import.md) – Takes the data collected from Box and imports it into the + Access Analyzer database for analysis, providing detailed reports on Box access rights, policies, + configurations, activities, and content diff --git a/docs/accessanalyzer/12.0/solutions/box/content/box_filemetrics.md b/docs/accessanalyzer/12.0/solutions/box/content/box_filemetrics.md index 793a7917de..f1d1c84836 100644 --- a/docs/accessanalyzer/12.0/solutions/box/content/box_filemetrics.md +++ b/docs/accessanalyzer/12.0/solutions/box/content/box_filemetrics.md @@ -20,7 +20,7 @@ Navigate to **Box** > **2.Content** > **Box_FileMetrics** > **Configure** node a **Analysis** to view analysis tasks. :::warning -Most of these analysis tasks should never be modified and never be deselected. +Don't modify or deselect most of these analysis tasks. ::: @@ -32,7 +32,7 @@ The following analysis tasks are selected by default: Results node - Set to consider content stale after 30 days which is the @STALETHRESHOLD parameter value - See the - [Customize Analysis Tasks for the Box_FileMetrics Job](#customize-analysis-tasks-for-the-box_filemetrics-job) + [Customize Analysis Tasks for the Box_FileMetrics Job](#customize-analysis-tasks-for-the-boxfilemetrics-job) topic for additional information. - File Count by User – Creates the Box_FileMetrics_UserFileCount table accessible under the job’s Results node diff --git a/docs/accessanalyzer/12.0/solutions/box/content/box_foldermetrics.md b/docs/accessanalyzer/12.0/solutions/box/content/box_foldermetrics.md index f2444ed92a..b767ab24fc 100644 --- a/docs/accessanalyzer/12.0/solutions/box/content/box_foldermetrics.md +++ b/docs/accessanalyzer/12.0/solutions/box/content/box_foldermetrics.md @@ -22,7 +22,7 @@ Navigate to **Box** > **2.Content** > **Box_FolderMetrics** > **Configure** node **Analysis** to view analysis tasks. :::warning -Most of these analysis tasks should never be modified and never be deselected. +Don't modify or deselect most of these analysis tasks. ::: @@ -34,7 +34,7 @@ The following analysis tasks are selected by default: Results node - Set to consider content stale after 30 days which is the @STALETHRESHOLD parameter value - See the - [Customizable Analysis Tasks for the Box_FolderMetrics Job](#customizable-analysis-tasks-for-the-box_foldermetrics-job) + [Customizable Analysis Tasks for the Box_FolderMetrics Job](#customizable-analysis-tasks-for-the-boxfoldermetrics-job) topic for additional information. - Largest Folders – Creates the Box_FolderMetrics_Largest table accessible under the job’s Results node diff --git a/docs/accessanalyzer/12.0/solutions/box/overview.md b/docs/accessanalyzer/12.0/solutions/box/overview.md index d9c2032cec..766f964421 100644 --- a/docs/accessanalyzer/12.0/solutions/box/overview.md +++ b/docs/accessanalyzer/12.0/solutions/box/overview.md @@ -21,9 +21,8 @@ for additional information. **Location** -The Box Solution requires a special Access Analyzer license. It can be installed from the Instant -Job Wizard. Once it has been installed into the Jobs tree, navigate to the solution: **Jobs** > -**Box**. +The Box Solution requires a special Access Analyzer license. Install it from the Instant Job +Wizard. After you install it into the Jobs tree, navigate to the solution: **Jobs** > **Box**. ![Box Solution in the Jobs Tree](/images/accessanalyzer/12.0/solutions/box/jobstree.webp) @@ -39,16 +38,15 @@ an organization's Box environment. The Box Solution has the following job groups and jobs: -- [0.Collection Job Group](/docs/accessanalyzer/12.0/solutions/box/collection/overview.md) – Collects the data which will be further - analyzed in order to provide details on Box access rights, policies, configurations, activities, - and content +- [0.Collection Job Group](/docs/accessanalyzer/12.0/solutions/box/collection/overview.md) – Collects data for further analysis, providing + details on Box access rights, policies, configurations, activities, and content - [1.Activity Job Group](/docs/accessanalyzer/12.0/solutions/box/activity/overview.md) – Identifies long term trends of activity providing insight into user activity, usage statistics, and suspicious behavior by analyzing enterprise events within the Box environment - [2.Content Job Group](/docs/accessanalyzer/12.0/solutions/box/content/overview.md) – Analyzes and summarizes the content of the Box environment, highlighting users with the most content as well as what type of content exists - [Box_Access Job](/docs/accessanalyzer/12.0/solutions/box/box_access.md) – Analyzes access granted to users and groups in an organization's - Box environment in order to report on effective access rights, file-level permissions, and + Box environment to report on effective access rights, file-level permissions, and inactive access rights that can be revoked - [Box_GroupMembership Job](/docs/accessanalyzer/12.0/solutions/box/box_groupmembership.md) – Expands group membership in an organization's Box environment diff --git a/docs/accessanalyzer/12.0/solutions/box/recommended.md b/docs/accessanalyzer/12.0/solutions/box/recommended.md index 57021c0fe9..7818e065ef 100644 --- a/docs/accessanalyzer/12.0/solutions/box/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/box/recommended.md @@ -6,11 +6,11 @@ sidebar_position: 10 # Recommended Configurations for the Box Solution -The jobs that run analysis tasks in the Box Solution requires the host list to be assigned. +The jobs that run analysis tasks in the Box Solution require you to assign a host list. **Dependencies** -- The .Active Directory Inventory Job Group must be successfully run prior to running this Job Group +- The .Active Directory Inventory Job Group must be successfully run before running this Job Group - 2-Box_Import Job – Imports data collected by the 1-Box_Access Scans Job and 1-Box_Activity Scans Job @@ -20,29 +20,29 @@ The jobs that run analysis tasks in the Box Solution requires the host list to b Within host inventory, the Box hosts will return a HostStatus of **Offline**. -If multiple Enterprise_IDs are to be scanned, it is necessary to duplicate the jobs within the -0.Collection Job Group for each target host. Since the 2-Box_Import Job must always be run after the -1-Box_Access Scans Job and 1-Box_Activity Scans Job, it is a best practice to set up sub-job groups -for each target named to identify the target, for example EMEA Box. Copying the jobs will append a -number to the job’s name. Once authorization codes have been generated for each 1-Box_Access Scans -Job and 1-Box_Activity Scans Job, then the solution can be scheduled to run as desired. +To scan multiple Enterprise_IDs, duplicate the jobs within the 0.Collection Job Group for each +target host. Since the 2-Box_Import Job must always run after the 1-Box_Access Scans Job and +1-Box_Activity Scans Job, set up sub-job groups for each target as a best practice, named to +identify the target, for example, EMEA Box. Copying the jobs will append a number to the job's +name. After you generate authorization codes for each 1-Box_Access Scans Job and 1-Box_Activity +Scans Job, you can schedule the solution to run as desired. **Connection Profile** -The Box Solution requires a specific credential for the Connection Profile which has access to the -SA Installer location. It is also necessary to authenticate to the target Box environment, which is -done through the Box Data Collector query configuration. An Enterprise Admin account (or Co-Admin -account with permission to **Run new reports and access existing reports** enabled) credential is -needed to generate an authorization code in the form of an Access Token. This can be done through -the query configuration either in the 1-Box_Access Scans Job’ Authentication wizard page or the -1-Box_Activity Scans Job’s Authentication wizard page of the Box Data Collector Wizard. See the +The Box Solution requires a specific credential for the Connection Profile that has access to the +SA Installer location. You also need to authenticate to the target Box environment through the Box +Data Collector query configuration. You need an Enterprise Admin account (or a Co-Admin account +with the **Run new reports and access existing reports** permission enabled) to generate an +authorization code in the form of an Access Token. Configure this through the query configuration +in either the 1-Box_Access Scans Job's Authentication wizard page or the 1-Box_Activity Scans Job's +Authentication wizard page of the Box Data Collector Wizard. See the [Box Data Collector](/docs/accessanalyzer/12.0/admin/datacollector/box/overview.md) topic for additional information. **Access Token** The Access Token is valid for 60 days. If Box scans are running on a regular schedule, then the Access Token automatically refreshes once an hour. However, if it has been more than 60 days since -the last scan, it is necessary to regenerate the Access Token. +the last scan, regenerate the Access Token. **Schedule Frequency** @@ -56,7 +56,7 @@ This solution can be run with the default query configuration. However, the foll - 1-Box_Access Scans Scan query - 1-Box_Activity Scans Activity Scan query -The Box_Import Job's Import query is preconfigured to run a full import and should not be modified. +The Box_Import Job's Import query is preconfigured to run a full import and shouldn't be modified. **Analysis Configuration** @@ -77,15 +77,14 @@ can be modified: depth. **Step 3 –** In the 1-Box_Access Scans Job, configure the Scan query to generate an authentication -code to authenticate to the targeted Box environment. This step only needs to be run prior to the -first scan. +code to authenticate to the targeted Box environment. Run this step only before the first scan. **Step 4 –** (Optional) Modify analysis task parameters for the reporting jobs. **Step 5 –** Schedule the Box Job Group to run as desired. :::note -The 0.Collection > 2-Box_Import Job must be run after the 1-Box_Access Scans Job and +The 0.Collection > 2-Box_Import Job must run after the 1-Box_Access Scans Job and 1-Box_Activity Scans Job because it imports the data collected by the scan jobs. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/azuresql/collection-azuresql/1-azuresql_permissionscan.md b/docs/accessanalyzer/12.0/solutions/databases/azuresql/collection-azuresql/1-azuresql_permissionscan.md index c95bcac63a..438a1353c4 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/azuresql/collection-azuresql/1-azuresql_permissionscan.md +++ b/docs/accessanalyzer/12.0/solutions/databases/azuresql/collection-azuresql/1-azuresql_permissionscan.md @@ -41,10 +41,10 @@ job. **Step 4 –** To query for specific databases/instances, navigate to the [SQL Data Collector](/docs/accessanalyzer/12.0/admin/datacollector/sql/overview.md) page. The default query target is All databases. The default query scope is Only select database objects and click Retrieve. The -Available database objects will be populated. Databases and instances can be added in the following +wizard populates the available database objects. Add databases and instances in the following ways: -- Select the desired database objects and click Add. +- Select the database objects you want and click Add. - Use the Import CSV button to import a list from a CSV file, if desired. - Optionally, use the Add Custom Filter button to create and apply a custom filter. diff --git a/docs/accessanalyzer/12.0/solutions/databases/azuresql/overview.md b/docs/accessanalyzer/12.0/solutions/databases/azuresql/overview.md index 1ced28a936..504aa98eae 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/azuresql/overview.md +++ b/docs/accessanalyzer/12.0/solutions/databases/azuresql/overview.md @@ -28,9 +28,8 @@ thread requires a minimum of 2 additional GB of RAM per host. For example, a job :::note Access Analyzer installs the appropriate JDK (Java) version for Sensitive Data Discovery on the -server. The JDK deployed is prepackaged and doesn't require any configuration; it has been -preconfigured to work with Access Analyzer and should never be customized through Java. It will not -conflict with other JDKs or Java Runtimes in the same environment. +server. This JDK comes prepackaged and preconfigured for Access Analyzer, so don't customize it +through Java. It will not conflict with other JDKs or Java Runtimes in the same environment. ::: **Location** diff --git a/docs/accessanalyzer/12.0/solutions/databases/azuresql/recommended.md b/docs/accessanalyzer/12.0/solutions/databases/azuresql/recommended.md index f3691ef491..d070f88c47 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/azuresql/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/databases/azuresql/recommended.md @@ -38,7 +38,7 @@ schedule it. **Targeted Hosts** -The 0.Collection Job Group has been set to run against the following default dynamic host list: +By default, the 0.Collection Job Group runs against the following dynamic host list: - All targeted Azure SQL Tenants diff --git a/docs/accessanalyzer/12.0/solutions/databases/db2/collection/db2_configuration.md b/docs/accessanalyzer/12.0/solutions/databases/db2/collection/db2_configuration.md index 367f1b7e8a..76ec1cb5fd 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/db2/collection/db2_configuration.md +++ b/docs/accessanalyzer/12.0/solutions/databases/db2/collection/db2_configuration.md @@ -21,11 +21,11 @@ The query is: ## Recommended Configuration for the Configuration Query -Prior to running an Db2 0.Collection query, you must establish a connection to the appropriate IBM -Db2 server. As long as that connection is set up first, it is recommended that no configuration -changes be made to the 0.Collection jobs before they run. +Before running a Db2 0.Collection query, you must establish a connection to the appropriate IBM +Db2 server. As long as you set up that connection first, don't make configuration +changes to the 0.Collection jobs before they run. -It is also recommended that the connection only be established for the 1-Db2 SensitiveDataScan Job. -Once the connection is established, it applies to all jobs in the 0.Collection job group. It does +Establish the connection only for the 1-Db2 SensitiveDataScan Job. After you establish the +connection, it applies to all jobs in the 0.Collection job group. It does not apply to any other job groups. For additional information on establishing a database connection, see [1-Db2_SensitiveDataScan](/docs/accessanalyzer/12.0/solutions/databases/db2/collection/db2_sensitivedatascan.md). diff --git a/docs/accessanalyzer/12.0/solutions/databases/db2/collection/db2_permissionscan.md b/docs/accessanalyzer/12.0/solutions/databases/db2/collection/db2_permissionscan.md index d8649d52b5..43cef3a667 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/db2/collection/db2_permissionscan.md +++ b/docs/accessanalyzer/12.0/solutions/databases/db2/collection/db2_permissionscan.md @@ -13,7 +13,7 @@ This job collects Db2 database level permissions from all the targeted Db2 datab The 2-Db2_PermissionScan Job uses the SQL Data Collector for queries. :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -25,12 +25,12 @@ The query is: ## Recommended Configuration for the Db2 Permission Query -Prior to running an Db2 0.Collection query, you must establish a connection to the appropriate IBM -Db2 server. As long as that connection is set up first, it is recommended that no configuration -changes be made to the 0.Collection jobs before they run. +Before running a Db2 0.Collection query, you must establish a connection to the appropriate IBM +Db2 server. As long as you set up that connection first, don't make configuration +changes to the 0.Collection jobs before they run. -It is also recommended that the connection only be established for the 1-Db2 SensitiveDataScan Job. -Once the connection is established, it applies to all jobs in the 0.Collection job group. It does +Establish the connection only for the 1-Db2 SensitiveDataScan Job. After you establish the +connection, it applies to all jobs in the 0.Collection job group. It does not apply to any other job groups. For additional information on establishing a database connection, see [1-Db2_SensitiveDataScan](/docs/accessanalyzer/12.0/solutions/databases/db2/collection/db2_sensitivedatascan.md). @@ -40,7 +40,7 @@ Navigate to the **Databases** > **0.Collection** > **Db2** > **2-Db2_PermissionS **Configure** node and select Analysis to view the Analysis Tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/db2/collection/db2_sensitivedatascan.md b/docs/accessanalyzer/12.0/solutions/databases/db2/collection/db2_sensitivedatascan.md index da106e0f67..7ba50d6a71 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/db2/collection/db2_sensitivedatascan.md +++ b/docs/accessanalyzer/12.0/solutions/databases/db2/collection/db2_sensitivedatascan.md @@ -21,14 +21,14 @@ The query is: ## Recommended Configuration for the SensitiveDataScan Query -It is only necessary to set up the connection for the 1-Db2 SensitiveDataScan Job. Once the +You only need to set up the connection for the 1-Db2 SensitiveDataScan Job. After the connection is established, custom configurations apply to all other job queries within the -0.Collection job group. Follow the steps to customize configurations. +0.Collection job group. To customize configurations, complete the following steps. **Step 1 –** Navigate to the Databases > 0.Collection > Db2 > 1-Db2_SensitiveDataScan > Configure node and select Queries. -**Step 2 –** In the Query Selection view, select the SensitiveDataScan query click on Query +**Step 2 –** In the Query Selection view, select the SensitiveDataScan query click Query Properties. The Query Properties window appears. **Step 3 –** Select the Data Source tab, and click Configure. The SQL Data Collector Wizard opens @@ -40,7 +40,7 @@ with Sensitive Data Collection category selected. ![Sensitive Data Scan Settings](/images/accessanalyzer/12.0/solutions/databases/db2/collection/sensitivedatajoboptions.webp) -**Step 5 –** To modify sensitive data scan options, select the desired scan options. See the +**Step 5 –** To modify sensitive data scan options, select the scan options you want. See the [SQL: Options](/docs/accessanalyzer/12.0/admin/datacollector/sql/options.md) page for additional information. :::warning @@ -54,7 +54,7 @@ may significantly increase scan time. ![Select Criteria](/images/accessanalyzer/12.0/solutions/databases/db2/collection/sensitivedatacriteria.webp) -**Step 7 –** To modify criteria, click on **Use the following selected criteria:** and select your +**Step 7 –** To modify criteria, click **Use the following selected criteria:** and select your choices. By default, the Sensitive Data Scan job is set to **Use Global Criteria**. :::note @@ -72,7 +72,7 @@ topic for additional information. **Step 9 –** Click **Connections** to open the Manage Connections window. :::note -SQL databases must be added to the query before they can be scanned. Before you can add a +You must add SQL databases to the query before you can scan them. Before you can add a query, you must establish a connection to the database. ::: @@ -82,15 +82,15 @@ query, you must establish a connection to the database. **Step 10 –** In the Manage Connections window, enter the following information: - Instance Label — Custom name of the instance -- Database System — A drop down containing all available database servers. Select the Db2LUW server +- Database System — A dropdown containing all available database servers. Select the Db2LUW server to configure Db2 queries. - Service Name — Custom name of the service - Host — Name or IP address of the host where the database is located. Host list is IBM DB2 - Port Number — Port number for the selected database - Default Database — Default Database -**Step 11 –** After completing the above information fields, click **Test Connection** to validate -the new connection. Once validated, click **Create New Connection** to finalize the connection. +**Step 11 –** After completing the information fields, click **Test Connection** to validate +the new connection. After it's validated, click **Create New Connection** to finalize the connection. **Step 12 –** Navigate to the Filter page. Select Only select database objects or **All database objects**. Collection queries are configured by default to target Only select database objects. @@ -103,14 +103,14 @@ For more information on filtering, see the **Step 13 –** Click Retrieve. The Available database objects box will populate. -**Step 14 –** Add the Databases and instances to be audited. Databases and instances can be added in +**Step 14 –** Add the Databases and instances to be audited. You can add databases and instances in the following ways: -- Select the desired database objects and click Add. +- Select the database objects you want and click Add. - Use the Import CSV button to import a list from a CSV file, if desired. - Optionally use the Add Custom Filter button to create and apply a custom filter. -Selected database objects to be audited will display. +The database objects you selected appear. **Step 15 –** Click **Next** and navigate to the Summary page, click Finish to save any setting modifications or click Cancel if no changes were made. Then click OK to close the Query Properties @@ -124,7 +124,7 @@ Navigate to the **Databases** > **0.Collection** > **Db2** > **1-Db2_SensitiveDa **Configure** node and select **Analysis** to view the Analysis Tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/db2/db2_databasesizing.md b/docs/accessanalyzer/12.0/solutions/databases/db2/db2_databasesizing.md index 307d516291..c2b6a129e1 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/db2/db2_databasesizing.md +++ b/docs/accessanalyzer/12.0/solutions/databases/db2/db2_databasesizing.md @@ -18,7 +18,7 @@ Navigate to the **Jobs** > **Databases** > **Db2** > **Configuration** > **Db2_ **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/db2/overview.md b/docs/accessanalyzer/12.0/solutions/databases/db2/overview.md index 7217dda46f..6ed3de666c 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/db2/overview.md +++ b/docs/accessanalyzer/12.0/solutions/databases/db2/overview.md @@ -22,30 +22,29 @@ for additional information. **Sensitive Data Discovery Considerations** -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the minimum amount -of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For example, if the job -is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are required (8x2=16). +If you run Sensitive Data Discovery (SDD) scans, increase the minimum amount of RAM. Each thread +requires a minimum of 2 additional GB of RAM per host. For example, a job configured to scan 8 hosts +at a time requires an extra 16 GB of RAM (8x2=16). :::note -The appropriate JDK (Java) version for Sensitive Data Discovery is installed on the -server. The JDK deployed is prepackaged and does not require any configuration; it has been -preconfigured to work with Access Analyzer and should never be customized through Java. It will not -conflict with other JDKs or Java Runtimes in the same environment. +Access Analyzer installs the appropriate JDK (Java) version for Sensitive Data Discovery on the +server. This JDK comes prepackaged and preconfigured for Access Analyzer, so don't customize it +through Java. It will not conflict with other JDKs or Java Runtimes in the same environment. ::: **Location** -The Db2 Solution requires a special Access Analyzer license. It can be installed from the Access -Analyzer Instant Job Wizard. Once it has been installed in the Jobs tree, navigate to the solution: +The Db2 Solution requires a special Access Analyzer license. You can install it from the Access +Analyzer Instant Job Wizard. After you install it in the Jobs tree, navigate to the solution: Jobs > **Databases** > **Db2**. -The 0.Collection Job Group collects the data. The Db2 Solution Set Collection group is designed to -collect high level summary information from targeted Db2 Database Servers. This information is used -by other jobs in the Db2 Solution for further analysis and producing respective reports. +The 0.Collection Job Group collects the data. The Db2 Solution Set Collection group collects high +level summary information from targeted Db2 Database Servers. Other jobs in the Db2 Solution use +this information for further analysis and to produce respective reports. -The Database Solution license includes all supported database platforms supported by Access -Analyzer. Additionally, Sensitive Data Discovery enables the solution to search database content for +The Database Solution license covers all database platforms that Access Analyzer supports. +Additionally, Sensitive Data Discovery enables the solution to search database content for sensitive data. ## Db2 Job Group Overview @@ -59,8 +58,8 @@ Permissions. The following comprises the Db2 solution: - [0.Collection Job Group](/docs/accessanalyzer/12.0/solutions/databases/db2/collection/overview.md) — Collects high level summary information from - targeted Db2 Servers. This information is used by other jobs in the Db2 Solution Set for further - analysis and producing respective report. + targeted Db2 Servers. Other jobs in the Db2 Solution Set use this information for further + analysis and to produce respective reports. - [Configuration > Db2_DatabaseSizing Job](/docs/accessanalyzer/12.0/solutions/databases/db2/db2_databasesizing.md) — Provides insight into Db2 server configuration settings diff --git a/docs/accessanalyzer/12.0/solutions/databases/db2/permissions/db2_directpermissions.md b/docs/accessanalyzer/12.0/solutions/databases/db2/permissions/db2_directpermissions.md index b3f5d03e91..2ea7604b0c 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/db2/permissions/db2_directpermissions.md +++ b/docs/accessanalyzer/12.0/solutions/databases/db2/permissions/db2_directpermissions.md @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **Databases** > **Db2** > **Permissions** > **Db2_Dir **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/db2/permissions/db2_effectivepermissions.md b/docs/accessanalyzer/12.0/solutions/databases/db2/permissions/db2_effectivepermissions.md index cb9bb3abbf..5a620aa067 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/db2/permissions/db2_effectivepermissions.md +++ b/docs/accessanalyzer/12.0/solutions/databases/db2/permissions/db2_effectivepermissions.md @@ -16,7 +16,7 @@ Navigate to the **Jobs** > **Databases** > **Db2** > **Permissions** > Tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/db2/recommended.md b/docs/accessanalyzer/12.0/solutions/databases/db2/recommended.md index 9a55c8b076..9f24b9daed 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/db2/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/databases/db2/recommended.md @@ -6,10 +6,10 @@ sidebar_position: 10 # Recommended Configuration for the Db2 Solution -The Db2 Solution has been configured to inherit down from the **Db2** > **Settings** node. However, +The Db2 Solution inherits settings from the **Db2** > **Settings** node. However, it is best practice to assign the host list and the Connection Profile at the data collection level, -the 0.Collection Job Group. Once these are assigned to the job group, it can be run directly or -scheduled. +the 0.Collection Job Group. After you assign these to the job group, you can run it directly or +schedule it. **Dependencies** @@ -33,28 +33,29 @@ scheduled. - .Instance Discovery Job Group run successfully -**Targeted Host(s)** +**Targeted Hosts** -The Db2 Job Group has been configured to inherit the host list assignment from the collection group +The Db2 Job Group inherits the host list assignment from the collection group level. -The host list assignment should be assigned under the **Databases** > **0.Collection** > **Db2** > +Assign the host list under the **Databases** > **0.Collection** > **Db2** > **Settings** > **Host List Assignment** node. The Local host box is checked by default. **Connection Profile** The SQL Data Collector requires a specific set of permissions. See the Permissions section for necessary permissions. The account used can be either an Active Directory account or a SQL account. -Once the account has been provisioned, create a custom Connection Profile containing the credentials +After you provision the account, create a custom Connection Profile containing the credentials for the targeted environment. See the [SQL Custom Connection Profile & Default Dynamic Host List](/docs/accessanalyzer/12.0/admin/datacollector/sql/configurejob.md) topic for additional information. -The Connection Profile should be assigned under the Databases > 0.Collection > Db2 > Settings > -Connection node. It is set to Use the Default Profile, as configured at the global settings level. +Assign the Connection Profile under the Databases > 0.Collection > Db2 > Settings > +Connection node. By default, the connection node uses the Default Profile configured at the global +settings level. However, since this may not be the Connection Profile with the necessary permissions for the assigned hosts, click the radio button for the Select one of the following user defined profiles -option and select the appropriate Connection Profile drop-down menu. +option and select the appropriate Connection Profile dropdown menu. See the [Connection](/docs/accessanalyzer/12.0/admin/settings/connection/overview.md) topic for additional information. @@ -65,8 +66,8 @@ This job group can be scheduled to run as desired. **Run Order** -The 0.Collection Jobs must be run first and in order. The other Db2 sub-job groups can be run in any -order, together or individually, after running the 0.Collection Job Group. +Run the 0.Collection Jobs first and in order. You can run the other Db2 sub-job groups in any +order, together, or individually, after running the 0.Collection Job Group. :::info Run the solution at the top level. @@ -76,7 +77,7 @@ Run the solution at the top level. **Workflow** 1. Install IBM Db2 Server Client and required clients and drivers -2. Configure and assign host list and connection profile(s) +2. Configure and assign host list and connection profiles 3. Define the connection information 4. Schedule the .Instance Discovery job group and 0.Collection job group to run as desired 5. Review the reports generated by the 0.Collection job group diff --git a/docs/accessanalyzer/12.0/solutions/databases/db2/sensitivedata/db2_sensitivedata.md b/docs/accessanalyzer/12.0/solutions/databases/db2/sensitivedata/db2_sensitivedata.md index 5468dffa69..e943540a26 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/db2/sensitivedata/db2_sensitivedata.md +++ b/docs/accessanalyzer/12.0/solutions/databases/db2/sensitivedata/db2_sensitivedata.md @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **Databases** > **Db2** > **Sensitive Data** > **Db2_ **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/db2/sensitivedata/db2_sensitivedatapermissions.md b/docs/accessanalyzer/12.0/solutions/databases/db2/sensitivedata/db2_sensitivedatapermissions.md index add81a9fe4..e65030af0b 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/db2/sensitivedata/db2_sensitivedatapermissions.md +++ b/docs/accessanalyzer/12.0/solutions/databases/db2/sensitivedata/db2_sensitivedatapermissions.md @@ -16,7 +16,7 @@ Navigate to the **Jobs** > **Databases** > **Db2** > **Sensitive Data** > tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/mongodb/collection/mongodb_configuration.md b/docs/accessanalyzer/12.0/solutions/databases/mongodb/collection/mongodb_configuration.md index 8bec09b0a5..31ddf1803b 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/mongodb/collection/mongodb_configuration.md +++ b/docs/accessanalyzer/12.0/solutions/databases/mongodb/collection/mongodb_configuration.md @@ -6,7 +6,7 @@ sidebar_position: 10 # MongoDB_Configuration Job -The MongoDB_Configuration job is designed to collect MongoDB server instance and database +The MongoDB_Configuration job collects MongoDB server instance and database configuration settings for use in the following analysis jobs and respective reports. ## Queries for the MongoDB_Configuration Job @@ -14,7 +14,7 @@ configuration settings for use in the following analysis jobs and respective rep The MongoDB_Configuration Job uses the NoSQL Data Collector for queries. :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/mongodb/collection/mongodb_sensitivedatascan.md b/docs/accessanalyzer/12.0/solutions/databases/mongodb/collection/mongodb_sensitivedatascan.md index e9b8d5a666..1119da4e34 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/mongodb/collection/mongodb_sensitivedatascan.md +++ b/docs/accessanalyzer/12.0/solutions/databases/mongodb/collection/mongodb_sensitivedatascan.md @@ -6,7 +6,7 @@ sidebar_position: 20 # MongoDB_SensitiveDataScan Job -The MongoDB_SensitiveDataScan Job is designed to discover sensitive data in MongoDB databases based +The MongoDB_SensitiveDataScan Job discovers sensitive data in MongoDB databases based on pre-defined or user-defined search criteria. ## Queries for the MongoDB_SensitiveDataScan Job @@ -26,7 +26,7 @@ The query is: ## Configure the MongoDB SDD Query The MongoDB SDD Query is preconfigured to run using the default settings for the Sensitive Data -Collection category. Follow the steps to customize configurations. +Collection category. To customize configurations, complete the following steps. **Step 1 –** Navigate to the **Databases** > **0.Collection** > **MongoDB** > **MongoDB_SensitiveDataScan** > **Configure** node and select Queries. @@ -37,7 +37,7 @@ The Query Properties window opens. **Step 3 –** Select the Data Source tab, and click Configure. The NoSQL Data Collector Wizard opens. :::warning -Do not make changes to wizard pages not listed in these steps. They have been +Don't make changes to wizard pages not listed in these steps. They have been pre-configured for this job. ::: @@ -47,7 +47,7 @@ page. ![Sensitive Data Scan Settings](/images/accessanalyzer/12.0/install/application/options.webp) -**Step 5 –** Select the desired scan options. +**Step 5 –** Select the scan options you want. **Step 6 –** Navigate to the [NoSQL: Criteria](/docs/accessanalyzer/12.0/admin/datacollector/nosql/criteria.md) page. @@ -56,7 +56,7 @@ page. **Step 7 –** To modify criteria, navigate to the [NoSQL: Criteria](/docs/accessanalyzer/12.0/admin/datacollector/nosql/criteria.md) page. By default, the Sensitive -Data Scan job is configured to scan for criteria configured in the Global Criteria settings. See the +Data Scan job scans for criteria in the Global Criteria settings. See the [Sensitive Data Criteria Editor](/docs/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/overview.md) topic for additional information. @@ -71,7 +71,7 @@ may significantly increase scan time. ![Database Selection Settings](/images/accessanalyzer/12.0/admin/datacollector/ewsmailbox/filter.webp) -**Step 9 –** MongoDB databases must be added to the query before they can be scanned. Click +**Step 9 –** You must add MongoDB databases to the query before you can scan them. Click **Connections** to open the Manage Connections window. ![Manage Connections window](/images/accessanalyzer/12.0/admin/datacollector/nosql/manageconnections.webp) @@ -99,7 +99,7 @@ Connections window. **Step 13 –** On the Filter page, click Retrieveto populate the Servers pane with the databases and collections. -**Step 14 –** (Optional) Right click on an object in the list to include or exclude it from the +**Step 14 –** (Optional) Right click an object in the list to include or exclude it from the sensitive data scan, or build /edit a pattern to create a custom filter. See the [NoSQL: Filter](/docs/accessanalyzer/12.0/admin/datacollector/nosql/filter.md) topic for additional information. @@ -117,7 +117,7 @@ Navigate to the Databases > > 0.Collection > MongoDB > MongoDB_SensitiveDataScan and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/mongodb/collection/overview.md b/docs/accessanalyzer/12.0/solutions/databases/mongodb/collection/overview.md index c8c3ce09da..ba33778906 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/mongodb/collection/overview.md +++ b/docs/accessanalyzer/12.0/solutions/databases/mongodb/collection/overview.md @@ -6,9 +6,9 @@ sidebar_position: 20 # 0.Collection Job Group -The MongoDB Solution Collection group is designed to collect high level summary information from -targeted MongoDB Servers.  This information is used by other jobs in the MongoDB Solution Set for -further analysis and producing respective reports. +The MongoDB Solution Collection group collects high level summary information from +targeted MongoDB Servers. Other jobs in the MongoDB Solution Set use this information for +further analysis and to produce respective reports. ![0](/images/accessanalyzer/12.0/solutions/databases/mongodb/collection/0.collecitonjobgroup.webp) diff --git a/docs/accessanalyzer/12.0/solutions/databases/mongodb/mongodb_database_sizing.md b/docs/accessanalyzer/12.0/solutions/databases/mongodb/mongodb_database_sizing.md index 8f2bab2745..be375c45cd 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/mongodb/mongodb_database_sizing.md +++ b/docs/accessanalyzer/12.0/solutions/databases/mongodb/mongodb_database_sizing.md @@ -10,7 +10,7 @@ Navigate to the **Jobs > Databases > MongoDB > Configuration > MongoDB_Databa node and select Analysis to view the Analysis Tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/mongodb/mongodb_sensitivedata.md b/docs/accessanalyzer/12.0/solutions/databases/mongodb/mongodb_sensitivedata.md index 5edfd6721a..3e128eed57 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/mongodb/mongodb_sensitivedata.md +++ b/docs/accessanalyzer/12.0/solutions/databases/mongodb/mongodb_sensitivedata.md @@ -6,7 +6,7 @@ sidebar_position: 40 # Sensitive Data > MongoDB_SensitiveData Job -The Sensitive Data Job Group is designed to provide insight into where sensitive data exists and who +The Sensitive Data Job Group provides insight into where sensitive data exists and who has access to it across all the targeted MongoDB databases. ![Sensitive Data Job Group](/images/accessanalyzer/12.0/solutions/databases/mongodb/sensitivedatajobgroup.webp) @@ -22,7 +22,7 @@ Navigate to the MongoDB > **Databases** > **Sensitive Data**> MongoDB_SensitiveD and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/mongodb/overview.md b/docs/accessanalyzer/12.0/solutions/databases/mongodb/overview.md index adba9623df..1c3e20e0da 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/mongodb/overview.md +++ b/docs/accessanalyzer/12.0/solutions/databases/mongodb/overview.md @@ -7,7 +7,7 @@ sidebar_position: 20 # MongoDB Solution Data privacy and security is quickly evolving to be on equal footing with traditional security -measures focused on the network, hardware, or software the data is contained within. Organizations +measures focused on the network, hardware, or software that contains the data. Organizations aligning to concepts like Data-Centric Audit and Protection (DCAP) as defined by Gartner, or the requirements of strict compliance regulations like EU GDPR, are looking to implement processes that help them understand where sensitive data is stored, who or what is leveraging their privileges to @@ -15,15 +15,15 @@ access the data, and how each database has been configured. As part of Stealthbits comprehensive Data Access Governance suite for structured and unstructured data, Access Analyzer for MongoDB automates the process of understanding where MongoDB databases -exist and provides an overview of the MongoDB environment in order to answer questions around data +exist and provides an overview of the MongoDB environment to answer questions around data access: - Who has access to your data? - Where is sensitive data being stored? -With visibility into every corner of MongoDB, organizations can proactively highlight and prioritize +With visibility into all areas of MongoDB, organizations can proactively highlight and prioritize risks to sensitive data. Additionally, organizations can automate manual, time-consuming, and -expensive processes associated with compliance, security, and operations to easily adhere to best +expensive processes associated with compliance, security, and operations to adhere to best practices that keep MongoDB Server safe and operational. **Supported Platforms** @@ -41,33 +41,33 @@ topic for additional information. **Sensitive Data Discovery Considerations** -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the minimum amount -of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For example, if the job -is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are required (8x2=16). +If you run Sensitive Data Discovery (SDD) scans, increase the minimum amount +of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For example, a job +configured to scan 8 hosts at a time requires an extra 16 GB of RAM (8x2=16). -By default, the job is configured to use 10 threads, which can be adjusted based on available +By default, the job uses 10 threads. You can adjust this based on available resources on the Access Analyzer server. :::note -The appropriate JDK (Java) version for Sensitive Data Discovery is installed on the -server. The JDK deployed is prepackaged and does not require any configuration; it has been -preconfigured to work with Access Analyzer and should never be customized through Java. It will not +Access Analyzer installs the appropriate JDK (Java) version for Sensitive Data Discovery on the +server. This JDK comes prepackaged and preconfigured for Access Analyzer, so don't customize it +through Java. It will not conflict with other JDKs or Java Runtimes in the same environment. ::: **Location** -The Structured Sensitive Data Discovery License is required to run the MongoDB Solution. The MongoDB -Solution can be installed from the Access Analyzer Instant Job Wizard. Once it has been installed -into the Jobs tree, navigate to the solution: Jobs > **Databases** > MongoDB. +The Structured Sensitive Data Discovery License is required to run the MongoDB Solution. You can +install it from the Access Analyzer Instant Job Wizard. After you install it +in the Jobs tree, navigate to the solution: Jobs > **Databases** > MongoDB. The 0.Collection Job Group scans MongoDB instances on the target hosts, and collects configuration and sensitive data. The other job groups analyze the collected data and generate reports. -The Database Solution license includes all supported database platforms supported by Access -Analyzer. Additionally, Sensitive Data Discovery enables the solution to search database content for +The Database Solution license covers all database platforms that Access Analyzer supports. +Additionally, Sensitive Data Discovery enables the solution to search database content for sensitive data. ## Job Groups @@ -80,8 +80,8 @@ visibility into MongoDB Sensitive Data. The following job groups comprise the MongoDB Solution: - [ 0.Collection Job Group](/docs/accessanalyzer/12.0/solutions/databases/mongodb/collection/overview.md) — Collects high level summary information from - targeted MongoDB Servers. This information is used by other jobs in the MongoDB Solution Set for - further analysis and producing respective reports. + targeted MongoDB Servers. Other jobs in the MongoDB Solution Set use this information for + further analysis and to produce respective reports. - [Analysis Tasks for the MongoDB_Database_Sizing Job](/docs/accessanalyzer/12.0/solutions/databases/mongodb/mongodb_database_sizing.md) — Provides insight into MongoDB server configuration settings - [Sensitive Data > MongoDB_SensitiveData Job](/docs/accessanalyzer/12.0/solutions/databases/mongodb/mongodb_sensitivedata.md) — Provides insight into diff --git a/docs/accessanalyzer/12.0/solutions/databases/mongodb/recommended.md b/docs/accessanalyzer/12.0/solutions/databases/mongodb/recommended.md index 5133bdb0ce..dc827cea1e 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/mongodb/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/databases/mongodb/recommended.md @@ -6,37 +6,38 @@ sidebar_position: 10 # Recommended Configuration for the MongoDB Solution -The MongoDB Solution has been configured to inherit down from the MongoDB > Settings node. However, +The MongoDB Solution inherits settings from the MongoDB > Settings node. However, it is best practice to assign the host list and the Connection Profile at the data collection level, -the 0.Collection Job Group. Once these are assigned to the job group, it can be run directly or -scheduled. +the 0.Collection Job Group. After you assign these to the job group, you can run it directly or +schedule it. **Dependencies** -- Query must be configured with list of target database clusters / instances +- The query must be configured with a list of target database clusters or instances Some of the 0.Collection Job Group queries can be scoped to target specific databases/instances. -However, it is necessary to add the databases to the query first. +However, add the databases to the query first. -**Targeted Host(s)** +**Targeted Hosts** -The 0.Collection Job Group must be set to run against a custom host list containing the MongoDB +You must set the 0.Collection Job Group to run against a custom host list containing the MongoDB database instances / clusters. **Connection Profile** The NoSQL Data Collector requires a specific set of permission. See the Permissions section for necessary permissions. The account used can be either an Active Directory account or a SQL account. -Once the account has been provisioned, create a custom Connection Profile containing the credentials +After you provision the account, create a custom Connection Profile containing the credentials for the targeted environment. See the [NoSQL Custom Connection Profile & Host List](/docs/accessanalyzer/12.0/admin/datacollector/nosql/configurejob.md) topic for additional information. -The Connection Profile should be assigned under the MongoDB > 0.Collection > Settings > Connection -node. It is set to Use the Default Profile, as configured at the global settings level. However, +Assign the Connection Profile under the MongoDB > 0.Collection > Settings > Connection +node. By default, the connection node uses the Default Profile configured at the global settings +level. However, since this may not be the Connection Profile with the necessary permissions for the assigned hosts, click the radio button for the Select one of the following user defined profiles option and select -the appropriate Connection Profile drop-down menu. +the appropriate Connection Profile dropdown menu. See the [Connection](/docs/accessanalyzer/12.0/admin/settings/connection/overview.md) topic for additional information. @@ -50,8 +51,8 @@ daily. **Run Order** -The 0.Collection Jobs must be run first and in order. The other MongoDB Solution sub-job groups can -be run in any order, together or individually, after running the 0.Collection Job Group. +Run the 0.Collection Jobs first and in order. You can run the other MongoDB Solution sub-job groups +in any order, together, or individually, after running the 0.Collection Job Group. :::info Run the solution at the top level. @@ -65,7 +66,7 @@ Run the solution at the top level. [NoSQL Custom Connection Profile & Host List](/docs/accessanalyzer/12.0/admin/datacollector/nosql/configurejob.md) topic for additional information. 2. Set the Host list for the 0.Collection Job Group with the servers containing the target - databases. Additionally, the database clusters / instances must be added to the Filter page in + databases. Additionally, add the database clusters or instances to the Filter page in the query configuration. See the [NoSQL Custom Connection Profile & Host List](/docs/accessanalyzer/12.0/admin/datacollector/nosql/configurejob.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/solutions/databases/mysql/collection/mysql_configuration.md b/docs/accessanalyzer/12.0/solutions/databases/mysql/collection/mysql_configuration.md index e2fb9c50c2..7d5ee5748b 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/mysql/collection/mysql_configuration.md +++ b/docs/accessanalyzer/12.0/solutions/databases/mysql/collection/mysql_configuration.md @@ -6,7 +6,7 @@ sidebar_position: 10 # MySQL_Configuration Job -The MySQL_Configuration Job is designed to collect MySQL server instance and database configuration +The MySQL_Configuration Job collects MySQL server instance and database configuration settings for use in the following analysis jobs and respective reports. ## Queries for the MySQL_Configuration Job @@ -14,7 +14,7 @@ settings for use in the following analysis jobs and respective reports. The MySQL_Configuration Job uses the SQL Data Collector for queries. :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/mysql/collection/mysql_sensitivedatascan.md b/docs/accessanalyzer/12.0/solutions/databases/mysql/collection/mysql_sensitivedatascan.md index 347c36f38e..91a5778306 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/mysql/collection/mysql_sensitivedatascan.md +++ b/docs/accessanalyzer/12.0/solutions/databases/mysql/collection/mysql_sensitivedatascan.md @@ -6,7 +6,7 @@ sidebar_position: 20 # MySQL_SensitiveDataScan Job -The MySQL_SensitiveDataScan Job is designed to discover sensitive data in MySQL databases based on +The MySQL_SensitiveDataScan Job discovers sensitive data in MySQL databases based on pre-defined or user-defined search criteria. ## Queries for the MySQL_SensitiveDataScan Job @@ -24,25 +24,25 @@ The query is: ### Configure the SensitiveDataScan Query The MySQL_SensitiveDataScan Job is preconfigured to run using the default settings for the Sensitive -Data Collection category. Follow the steps to customize configurations. +Data Collection category. To customize configurations, complete the following steps. **Step 1 –** Navigate to the Databases > 0.Collection > MySQL > MySQL_SensitiveDataScan > Configure node and select Queries. -**Step 2 –** In the Query Selection view, select the Sensitive Data Scan query click on Query +**Step 2 –** In the Query Selection view, select the Sensitive Data Scan query click Query Properties. The Query Properties window appears. **Step 3 –** Select the Data Source tab, and click Configure. The SQL Data Collector Wizard opens. :::warning -Do not make changes to other wizard pages as they have been pre-configured for this +Don't make changes to other wizard pages as they have been pre-configured for this job. ::: ![Sensitive Data Scan Settings](/images/accessanalyzer/12.0/solutions/databases/mysql/collection/sensitivedatscan_optionspage.webp) -**Step 4 –** To modify sensitive data scan options, select the desired scan options. See the +**Step 4 –** To modify sensitive data scan options, select the scan options you want. See the [SQL: Options](/docs/accessanalyzer/12.0/admin/datacollector/sql/options.md) page for additional information. :::note @@ -56,13 +56,13 @@ may significantly increase scan time. **Step 5 –** To modify criteria, navigate to the [SQL: Criteria](/docs/accessanalyzer/12.0/admin/datacollector/sql/criteria.md) page. By default, the Sensitive -Data Scan job is configured to scan for criteria configured in the Global Criteria settings. See the +Data Scan job scans for criteria in the Global Criteria settings. See the [Sensitive Data Criteria Editor](/docs/accessanalyzer/12.0/sensitivedatadiscovery/criteriaeditor/overview.md) topic for additional information. ![Filters Page](/images/accessanalyzer/12.0/solutions/databases/mysql/collection/sensitivedatscan_filterspage.webp) -**Step 6 –** MySQL databases must be added to the query before they can be scanned. Navigate to the +**Step 6 –** You must add MySQL databases to the query before you can scan them. Navigate to the **Filter** page and click **Connections** to open the Manage Connections window. ![Manage Connections](/images/accessanalyzer/12.0/solutions/databases/mysql/collection/manageconnectionsmysql.webp) @@ -77,12 +77,12 @@ information: Exit the Manage Connections window to return to the Filter page. -**Step 8 –** On the Filter page, the query is configured by default to target Only select database +**Step 8 –** By default, the query targets Only select database objects. Click Retrieve. The Available database objects box will populate. The default filter will -scan all MySQL Databases returned, excluding the listed system schemas and tables in red. Databases -and instances can be added in the following ways: +scan all MySQL Databases returned, excluding the listed system schemas and tables in red. You can +add databases and instances in the following ways: -- Select the desired database objects and click Add. +- Select the database objects you want and click Add. - Use the Import CSV button to import a list from a CSV file, if desired. - Use the Add Custom Filter button to create and apply a custom filter. @@ -97,7 +97,7 @@ Navigate to the **Databases** > **0.Collection** > **MySQL** > **MySQL_Sensitive **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/mysql/collection/mysql_tableprivileges.md b/docs/accessanalyzer/12.0/solutions/databases/mysql/collection/mysql_tableprivileges.md index b49f4032f4..ce05b3f52e 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/mysql/collection/mysql_tableprivileges.md +++ b/docs/accessanalyzer/12.0/solutions/databases/mysql/collection/mysql_tableprivileges.md @@ -6,7 +6,7 @@ sidebar_position: 30 # MySQL_TablePrivileges Job -The MySQL_TablePrivileges job is designed to collect MySQL table privileges from all the targeted +The MySQL_TablePrivileges job collects MySQL table privileges from all the targeted servers. ## Queries for the MySQL_TablePrivileges Job @@ -14,7 +14,7 @@ servers. The MySQL_TablePrivileges Job uses the SQL Data Collector for queries. :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -30,7 +30,7 @@ Navigate to the **Databases** > **0.Collection** > **MySQL** > **MySQL_TablePriv **Configure** node and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/mysql/collection/overview.md b/docs/accessanalyzer/12.0/solutions/databases/mysql/collection/overview.md index 52a23c193f..571dac6f11 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/mysql/collection/overview.md +++ b/docs/accessanalyzer/12.0/solutions/databases/mysql/collection/overview.md @@ -6,19 +6,19 @@ sidebar_position: 20 # 0.Collection Job Group -The MySQL Solution Collection group is designed to collect high level summary information from -targeted MySQL Servers. This information is used by other jobs in the MySQL Solution Set for further -analysis and producing respective reports. +The MySQL Solution Collection group collects high level summary information from +targeted MySQL Servers. Other jobs in the MySQL Solution Set use this information for further +analysis and to produce respective reports. ![0.Collection Job Group for MySQL](/images/accessanalyzer/12.0/solutions/databases/mysql/collection/0.collectionjobgroup.webp) The jobs in the 0.Collection Job Group are: -- [MySQL_Configuration Job](/docs/accessanalyzer/12.0/solutions/databases/mysql/collection/mysql_configuration.md) – Designed to collect MySQL server instance and +- [MySQL_Configuration Job](/docs/accessanalyzer/12.0/solutions/databases/mysql/collection/mysql_configuration.md) – Collects MySQL server instance and database configuration settings for use in the following analysis jobs and respective reports -- [MySQL_SensitiveDataScan Job](/docs/accessanalyzer/12.0/solutions/databases/mysql/collection/mysql_sensitivedatascan.md) – Designed to discover sensitive data in +- [MySQL_SensitiveDataScan Job](/docs/accessanalyzer/12.0/solutions/databases/mysql/collection/mysql_sensitivedatascan.md) – Discovers sensitive data in MySQL databases based on pre-defined or user-defined search criteria -- [MySQL_TablePrivileges Job](/docs/accessanalyzer/12.0/solutions/databases/mysql/collection/mysql_tableprivileges.md) – Designed to collect MySQL table privileges +- [MySQL_TablePrivileges Job](/docs/accessanalyzer/12.0/solutions/databases/mysql/collection/mysql_tableprivileges.md) – Collects MySQL table privileges from all the targeted servers. **Workflow** diff --git a/docs/accessanalyzer/12.0/solutions/databases/mysql/mysql_databasesizing.md b/docs/accessanalyzer/12.0/solutions/databases/mysql/mysql_databasesizing.md index f42fe03855..84a1491f76 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/mysql/mysql_databasesizing.md +++ b/docs/accessanalyzer/12.0/solutions/databases/mysql/mysql_databasesizing.md @@ -20,7 +20,7 @@ Navigate to the **Jobs > Databases > MySQL > Configuration > MySQL_DatabaseSi and select Analysis to view the Analysis Tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/mysql/overview.md b/docs/accessanalyzer/12.0/solutions/databases/mysql/overview.md index b5f110c45c..941b2b64cb 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/mysql/overview.md +++ b/docs/accessanalyzer/12.0/solutions/databases/mysql/overview.md @@ -15,18 +15,18 @@ access the data, and how each database has been configured. As part of Stealthbits comprehensive Data Access Governance suite for structured and unstructured data, Access Analyzer for MySQL automates the process of understanding where MySQL databases exist -and provides an overview of the MySQL environment in order to answer questions around data access: +and provides an overview of the MySQL environment to answer questions around data access: - Who has access to your data? - Where is sensitive data being stored? With visibility into every corner of MySQL, organizations can proactively highlight and prioritize risks to sensitive data. Additionally, organizations can automate manual, time-consuming, and -expensive processes associated with compliance, security, and operations to easily adhere to best +expensive processes associated with compliance, security, and operations to adhere to best practices that keep MySQL Server safe and operational. The MySQL Solution requires a special Access Analyzer license. The Database Solution license -includes all supported database platforms supported by Access Analyzer. Additionally, Sensitive Data +includes all database platforms supported by Access Analyzer. Additionally, Sensitive Data Discovery enables the solution to search database content for sensitive data. By default, the job is configured to use 10 threads, which can be adjusted based on available @@ -48,29 +48,29 @@ topic for additional information. **Sensitive Data Discovery Considerations** -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the minimum amount +If running Sensitive Data Discovery (SDD) scans, increase the minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host.For example, if the job is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are required (8x2=16). :::note The appropriate JDK (Java) version for Sensitive Data Discovery is installed on the -server. The JDK deployed is prepackaged and does not require any configuration; it has been -preconfigured to work with Access Analyzer and should never be customized through Java. It will not +server. The JDK deployed is prepackaged and preconfigured to work with Access Analyzer, requires no +additional configuration, and should never be customized through Java. It doesn't conflict with other JDKs or Java Runtimes in the same environment. ::: **Location** -The Structured Sensitive Data Discovery License is required to run the MySQL Solution. It can be -installed from the Access Analyzer Instant Job Wizard. Once it has been installed into the Jobs +The Structured Sensitive Data Discovery License is required to run the MySQL Solution. Install it +from the Access Analyzer Instant Job Wizard. After you install it into the Jobs tree, navigate to the solution: Jobs > **Databases** > MySQL. The 0.Collection Job Group discovers configuration settings and Sensitive Data in MySQL Instances on the target hosts. The other job groups analyze and report on the data collected by the 0.Collection Job Group. -The Database Solution license includes all supported database platforms supported by Access +The Database Solution license includes all database platforms supported by Access Analyzer. Additionally, Sensitive Data Discovery enables the solution to search database content for sensitive data. diff --git a/docs/accessanalyzer/12.0/solutions/databases/mysql/recommended.md b/docs/accessanalyzer/12.0/solutions/databases/mysql/recommended.md index aec5405ad2..4db41b64c0 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/mysql/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/databases/mysql/recommended.md @@ -8,16 +8,16 @@ sidebar_position: 10 The MySQL Solution has been configured to inherit down from the MySQL > Settings node. However, it is best practice to assign the host list and the Connection Profile at the data collection level, -0.Collection Job Group. Once these are assigned to the job group, it can be run directly or -scheduled. +0.Collection Job Group. After you assign these to the job group, you can run it directly or +schedule it. **Dependencies** - For AWS RDS and Aurora instances, right-click a job in the **MySQL** > **0.Collection** folder and open the properties window. Select the **Performance** tab and ensure that the **Skip Hosts that - do not respond to PING**checkbox is not selected. + don't respond to PING**checkbox isn't selected. -**Targeted Host(s)** +**Targeted Hosts** - The 0.Collection Job Group must be set to run against a custom host list containing the MySQL database instances / clusters. @@ -32,9 +32,9 @@ credentials configured in the Connection Profile must be able to access the MySQ permissions and creating a SQL custom connection profile. The Connection Profile is set to Use the Default Profile, as configured at the global settings -level. However, since this may not be the Connection Profile with the necessary permissions for the -assigned hosts, click the radio button for the Select one of the following user defined profiles -option and select the appropriate Connection Profile drop-down menu. +level. However, if this isn't the Connection Profile with the necessary permissions for the +assigned hosts, select the **Select one of the following user defined profiles** option and choose +the appropriate profile from the Connection Profile dropdown menu. **Schedule Frequency** @@ -42,7 +42,7 @@ Daily **Run Order** -The 0.Collection Job Group must be run first before running the other jobs and job groups. +Run the 0.Collection Job Group before running the other jobs and job groups. :::info Run the solution at the top level: MySQL Job Group @@ -59,12 +59,12 @@ topic for additional information. **Analysis Configuration** This solution should be run with the default analysis configurations. These analysis tasks are -preconfigured and should not be modified or deselected. +preconfigured and shouldn't be modified or deselected. Disabling obsolete or run-desired jobs allows the solution to run more efficiently. To disable a job -or job group, right-click on the item and select Disable Job. +or job group, right-click the item and select Disable Job. :::info -Do not delete any jobs. Instead, jobs should be disabled. +Don't delete any jobs. Instead, disable them. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/mysql/sensitivedata/mysql_sensitivedata.md b/docs/accessanalyzer/12.0/solutions/databases/mysql/sensitivedata/mysql_sensitivedata.md index 9f59902c25..101dc6e958 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/mysql/sensitivedata/mysql_sensitivedata.md +++ b/docs/accessanalyzer/12.0/solutions/databases/mysql/sensitivedata/mysql_sensitivedata.md @@ -15,7 +15,7 @@ Navigate to the **Jobs > MySQL > Sensitive Data > MySQL_SensitiveData > Conf Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/mysql/sensitivedata/mysql_sensitivedatapermissions.md b/docs/accessanalyzer/12.0/solutions/databases/mysql/sensitivedata/mysql_sensitivedatapermissions.md index 0c266a7e4a..d865bf1342 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/mysql/sensitivedata/mysql_sensitivedatapermissions.md +++ b/docs/accessanalyzer/12.0/solutions/databases/mysql/sensitivedata/mysql_sensitivedatapermissions.md @@ -16,7 +16,7 @@ Navigate to the **Jobs > MySQL > Sensitive Data > MySQL_SensitiveDataPermissi and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_activity.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_activity.md index 1163363d53..a73b53bd7e 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_activity.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_activity.md @@ -15,7 +15,7 @@ Navigate to the **Oracle** > **2.Activity** > **Oracle_Activity** > **Configure* **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_logons.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_logons.md index 226457cc86..d9d470f729 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_logons.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_logons.md @@ -15,7 +15,7 @@ Navigate to the **Oracle** > **2.Activity** > **Oracle_Logons** > **Configure** **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_permissionchanges.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_permissionchanges.md index ee20bc5f4c..85f953fc8c 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_permissionchanges.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_permissionchanges.md @@ -16,7 +16,7 @@ Navigate to the **Oracle** > **2.Activity** > **Oracle_PermissionChanges** > **C select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_schemachanges.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_schemachanges.md index 31139d1687..703225e852 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_schemachanges.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_schemachanges.md @@ -15,7 +15,7 @@ Navigate to the **Oracle** > **2.Activity** > **Oracle_SchemaChanges** > **Confi select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_sensitivedataactivity.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_sensitivedataactivity.md index b330434183..7c03a8dcf1 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_sensitivedataactivity.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_sensitivedataactivity.md @@ -15,7 +15,7 @@ Navigate to the **Oracle** > **2.Activity** > **Oracle_SensitiveDataActivity** > and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_suspiciousactivity.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_suspiciousactivity.md index db5a4e0c4e..ae9a677be3 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_suspiciousactivity.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_suspiciousactivity.md @@ -7,7 +7,7 @@ sidebar_position: 60 # Oracle_SuspiciousActivity Job The Oracle_SuspiciousActivity job is designed to provide insight into suspicious behavior based on -user activity that does not conform to normal database activity. +user activity that doesn't conform to normal database activity. ## Analysis Tasks for the Oracle_SuspiciousActivity Job @@ -15,7 +15,7 @@ Navigate to the **Oracle** > **2.Activity** > **Oracle_SuspiciousActivity** > ** select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_unusualactivity.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_unusualactivity.md index 6f65dc4c86..912771eb4e 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_unusualactivity.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_unusualactivity.md @@ -16,7 +16,7 @@ Navigate to the **Oracle** > **2.Activity** > **Oracle_UnusualActivity** > **Con select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/overview.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/overview.md index dfc10f172f..433caeb473 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/overview.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/overview.md @@ -29,7 +29,7 @@ The jobs in the 2.Activity Job Group are: provide detailed information about all the DML (UPDATE, INSERT, DELETE, TRUNCATE) against objects containing sensitive data - [Oracle_SuspiciousActivity Job](/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_suspiciousactivity.md) – This job is designed to provide - insight into suspicious behavior based on user activity that does not conform to normal database + insight into suspicious behavior based on user activity that doesn't conform to normal database activity - [Oracle_UnusualActivity Job](/docs/accessanalyzer/12.0/solutions/databases/oracle/activity/oracle_unusualactivity.md) – This job is designed to analyze user activity based on the audited actions and identify any outliers based on a modified z-score. diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/collection/0-oracle_servers.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/collection/0-oracle_servers.md index 184a41f7b5..70ff5cc135 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/collection/0-oracle_servers.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/collection/0-oracle_servers.md @@ -14,7 +14,7 @@ running on the targeted servers. The Server Discovery query uses the PowerShell Data Collector for the following query: :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -22,7 +22,7 @@ Do not modify the query. The query is preconfigured for this job. - Oracle Servers – Returns a list of Oracle servers from the specified host list -Regarding Oracle instance discovery, there may be errors running the query that are not reported. An +Regarding Oracle instance discovery, there may be errors running the query that aren't reported. An additional log to store the issues has been added for instance discoveries named `Oracle_Server_log_[target_hostname]`. This file can be found in `%sainstalldir%\Jobs\GROUP_ORACLE_0.Collection\GROUP_1.Discovery\JOB_Oracle_Servers\OUTPUT`. See the @@ -35,7 +35,7 @@ Navigate to the **Databases** > **0.Collection** > **Oracle** > **0-Oracle_Serve node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/collection/1-oracle_permissionsscan.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/collection/1-oracle_permissionsscan.md index ca5e015983..48c1670a87 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/collection/1-oracle_permissionsscan.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/collection/1-oracle_permissionsscan.md @@ -20,19 +20,19 @@ The PermissionsScan query uses the SQL Data Collector for the following query: ### Configure the 1-Oracle_PermissionsScan Query The 1-Oracle_PermissionsScan Job is preconfigured to run using the default settings for the -Permissions Collection category in the SQL Data Collector. Follow the steps to customize -configurations: +Permissions Collection category in the SQL Data Collector. To customize +configurations, complete the following steps: **Step 1 –** Navigate to the **Databases** > **0.Collection** > **Oracle** > **1-Oracle_PermissionsScan** > **Configure** node and select Queries. -**Step 2 –** In the Query Selection view, select the PermissionScan query and click on Query +**Step 2 –** In the Query Selection view, select the PermissionScan query and click Query Properties. The Query Properties window opens. **Step 3 –** Select the Data Source tab and click Configure. The SQL Data Collector wizard opens. :::warning -Do not make changes to wizard pages not listed in these steps. They have been +Don't make changes to wizard pages not listed in these steps. They have been pre-configured for this job. ::: @@ -44,7 +44,7 @@ query target is All Databases. The default query scope is Only select database o Retrieve. The Available database objects section will be populated. Databases and instances can be added in the following ways: -- Select the desired database objects and click Add +- Select the database objects you want and click Add - Use the Import CSV button to import a list from a CSV file, if desired - Optionally, use the Add Custom Filter button to create and apply a custom filter @@ -59,7 +59,7 @@ Navigate to the **Databases** > **0.Collection** > **Oracle** > **1-Oracle_Permi **Configure** node and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/collection/2-oracle_sensitivedatascan.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/collection/2-oracle_sensitivedatascan.md index 93405988c7..dd3f05e1ee 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/collection/2-oracle_sensitivedatascan.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/collection/2-oracle_sensitivedatascan.md @@ -22,8 +22,8 @@ The SensitiveDataScan Query uses the SQL Data Collector for the following query: ### Configure the 2-Oracle_SensitiveDataScan Query The 2-Oracle_SensitiveDataScan job is preconfigured to run using the default settings for the -Sensitive Data Collection category in the SQL Data Collector. Follow the steps to customize -configurations: +Sensitive Data Collection category in the SQL Data Collector. To customize +configurations, complete the following steps: **Step 1 –** Navigate to the **Databases** > **0.Collection** > **Oracle** > **2-Oracle_SensitiveDataScan** > **Configure** node and select **Queries**. @@ -35,7 +35,7 @@ Properties**. The Query Properties window opens. opens. :::warning -Do not make changes to wizard pages not listed in these steps. They have been +Don't make changes to wizard pages not listed in these steps. They have been pre-configured for this job. ::: @@ -57,7 +57,7 @@ query target is **All Databases**. The default query scope is **Only select data Click **Retrieve**. The Available database objects section will be populated. Databases and instances can be added in the following ways: -- Select the desired database objects and click **Add** +- Select the database objects you want and click **Add** - Use the **Import CSV** button to import a list from a CSV file, if desired - Optionally, use the **Add Custom Filter** button to create and apply a custom filter @@ -72,7 +72,7 @@ Navigate to the **Databases** > **0.Collection** > **Oracle** > **2-Oracle_Sensi **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/collection/3-oracle_activityscan.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/collection/3-oracle_activityscan.md index 2d38213b56..2e233240bd 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/collection/3-oracle_activityscan.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/collection/3-oracle_activityscan.md @@ -27,19 +27,19 @@ The ActivityScan Query uses the SQL Data Collector for the following query: ### Configure the 3-Oracle_ActivityScan Query The 3-Oracle_ActivityScan Job is preconfigured to run using the default settings for the Server -Audit Events Collection category in the SQL Data Collector. Follow the steps to customize -configurations: +Audit Events Collection category in the SQL Data Collector. To customize +configurations, complete the following steps: **Step 1 –** Navigate to the **Databases** > **0.Collection** > **Oracle** > **3-Oracle_ActivityScan** > **Configure** node and select Queries. -**Step 2 –** In the Query Selection view, select the ActivityScan query and click on Query +**Step 2 –** In the Query Selection view, select the ActivityScan query and click Query Properties. The Query Properties window opens. **Step 3 –** Select the Data Source tab and click Configure. The SQL Data Collector wizard opens. :::warning -Do not make changes to wizard pages not listed in these steps. They have been +Don't make changes to wizard pages not listed in these steps. They have been pre-configured for this job. ::: @@ -56,7 +56,7 @@ query target is All Databases. The default query scope is Only select database o Retrieve. The Available database objects section will be populated. Databases and instances can be added in the following ways: -- Select the desired database objects and click Add +- Select the database objects you want and click Add - Use the Import CSV button to import a list from a CSV file, if desired - Optionally, use the Add Custom Filter button to create and apply a custom filter @@ -71,7 +71,7 @@ Navigate to the **Databases** > **0.Collection** > **Oracle** > **3-Oracle_Activ **Configure** node and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/collection/4-oracle_defaultpasswordusers.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/collection/4-oracle_defaultpasswordusers.md index 5edc63e7ac..322b1b6eb9 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/collection/4-oracle_defaultpasswordusers.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/collection/4-oracle_defaultpasswordusers.md @@ -21,19 +21,19 @@ The 4-Oracle_DefaultPasswordUsers Job uses the SQL Data Collector for the follow ### Configure the 4-Oracle_DefaultPasswordUsers Query The 4-Oracle_DefaultPasswordUsers Job is preconfigured to run using the default settings for the -Permissions Collection category in the SQL Data Collector. Follow the steps to customize -configurations: +Permissions Collection category in the SQL Data Collector. To customize +configurations, complete the following steps: **Step 1 –** Navigate to the **Databases** > **0.Collection** > **Oracle** > **4-Oracle_DefaultPasswordUsers** > **Configure** node and select Queries. -**Step 2 –** In the Query Selection view, select the Users with Default Passwords query and click on +**Step 2 –** In the Query Selection view, select the Users with Default Passwords query and click Query Properties. The Query Properties window opens. **Step 3 –** Select the Data Source tab and click Configure. The SQL Data Collector wizard opens. :::warning -Do not make changes to wizard pages not listed in these steps. They have been +Don't make changes to wizard pages not listed in these steps. They have been pre-configured for this job. ::: @@ -45,7 +45,7 @@ query target is All Databases. The default query scope is Only select database o Retrieve. The Available database objects section will be populated. Databases and instances can be added in the following ways: -- Select the desired database objects and click Add +- Select the database objects you want and click Add - Use the Import CSV button to import a list from a CSV file, if desired - Optionally, use the Add Custom Filter button to create and apply a custom filter diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/collection/5-oracle_configuration.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/collection/5-oracle_configuration.md index 1a8cac971d..90667e5011 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/collection/5-oracle_configuration.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/collection/5-oracle_configuration.md @@ -23,18 +23,18 @@ The queries are: ### Configure the 5-Oracle_Configuration Queries The 5-Oracle_Configuration Job is preconfigured to run using the default settings for the Custom -Oracle Query category in the SQL Data Collector. Follow the steps to customize configurations: +Oracle Query category in the SQL Data Collector. To customize configurations, complete the following steps: **Step 1 –** Navigate to the **Databases** > **0.Collection** > **Oracle** > **5-Oracle_Configuration Job** > **Configure** node and select Queries. -**Step 2 –** In the Query Selection view, select one of the queries and click on Query Properties. +**Step 2 –** In the Query Selection view, select one of the queries and click Query Properties. The Query Properties window opens. **Step 3 –** Select the Data Source tab and click Configure. The SQL Data Collector wizard opens. :::warning -Do not make changes to wizard pages not listed in these steps. They have been +Don't make changes to wizard pages not listed in these steps. They have been pre-configured for this job. ::: @@ -46,7 +46,7 @@ query target is All Databases. The default query scope is Only select database o Retrieve. The Available database objects section will be populated. Databases and instances can be added in the following ways: -- Select the desired database objects and click Add +- Select the database objects you want and click Add - Use the Import CSV button to import a list from a CSV file, if desired - Optionally, use the Add Custom Filter button to create and apply a custom filter diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/oracle_databaselinks.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/oracle_databaselinks.md index 469c473e41..d4b9bd3b2e 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/oracle_databaselinks.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/oracle_databaselinks.md @@ -7,7 +7,7 @@ sidebar_position: 10 # Oracle_DatabaseLinks Job The Oracle_DatabaseLinks Job contains a report that provides information on Database Links where the -listed Oracle Server is able to execute remote commands. +listed Oracle Server can execute remote commands. ## Analysis Tasks for the Oracle_DatabaseLinks Job @@ -15,7 +15,7 @@ Navigate to the **Jobs >  Databases > Oracle > 4.Configuration > Oracle_Databas Job >Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -32,4 +32,4 @@ the following preconfigured report: | Report | Description | Default Tags | Report Elements | | -------------- | -------------------------------------------------------------------------------------------------------- | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Database Links | This report highlights Database Links where the listed Oracle Server is able to execute remote commands. | None | This report is comprised of three elements:
  • Bar Chart – Provides information on top five database links by instance
  • Bar Chart – Provides information on database links by instance (GB)
  • Table – Provides details on database links
| +| Database Links | This report highlights Database Links where the listed Oracle Server can execute remote commands. | None | This report is comprised of three elements:
  • Bar Chart – Provides information on top five database links by instance
  • Bar Chart – Provides information on database links by instance (GB)
  • Table – Provides details on database links
| diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/oracle_databasesizing.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/oracle_databasesizing.md index 2f73f29d50..b3fce67bac 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/oracle_databasesizing.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/oracle_databasesizing.md @@ -15,7 +15,7 @@ Navigate to the **Jobs >  Databases > Oracle > 4.Configuration > Oracle_Databas Job >Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/oracle_datadictionaryprotection.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/oracle_datadictionaryprotection.md index b165d80f29..90645b53e9 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/oracle_datadictionaryprotection.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/oracle_datadictionaryprotection.md @@ -17,7 +17,7 @@ Navigate to the **Jobs >  Databases > Oracle > 4.Configuration > Oracle_DataDic Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/oracle_instancenameissues.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/oracle_instancenameissues.md index b72d93fbaf..fa8e6c17e4 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/oracle_instancenameissues.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/oracle_instancenameissues.md @@ -8,7 +8,7 @@ sidebar_position: 40 The Oracle_InstanceNameIssues Job discovers if names used for Oracle database instances conform to Oracle recommended best practices. The job also checks to see if Oracle SIDs conform to DISA STIG -V-61413 – Oracle instance name or SID should not contain Oracle version numbers. +V-61413 – Oracle instance name or SID shouldn't contain Oracle version numbers. ## Analysis Tasks for the Oracle_InstanceNameIssues Job @@ -16,7 +16,7 @@ Navigate to the **Jobs > Databases > Oracle > 4.Configuration > Oracle_InstanceN Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/oracle_remoteosauthentication.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/oracle_remoteosauthentication.md index 9553e90132..804e6abef3 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/oracle_remoteosauthentication.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/oracle_remoteosauthentication.md @@ -15,7 +15,7 @@ Navigate to the **Jobs > Databases > Oracle > 4.Configuration > Oracle_RemoteOSA Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/overview.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/overview.md index 1b2fd42408..e4574c5bd1 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/overview.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/overview.md @@ -14,7 +14,7 @@ related to Oracle Database Instance configuration settings. The jobs in the 4.Configuration Job Group are: - [Oracle_DatabaseLinks Job](/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/oracle_databaselinks.md) – Contains a report that provides information - on Database Links where the listed Oracle Server is able to execute remote commands + on Database Links where the listed Oracle Server can execute remote commands - [Oracle_DatabaseSizing Job](/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/oracle_databasesizing.md) – Provides details on tablespace file sizes and overall tablespace sizes - [Oracle_DataDictionaryProtection Job](/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/oracle_datadictionaryprotection.md) – This job is designed @@ -24,6 +24,6 @@ The jobs in the 4.Configuration Job Group are: - [Oracle_InstanceNameIssues Job](/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/oracle_instancenameissues.md) – This job is designed to find out if the names used for the Oracle database instances conform to Oracle recommended best practices. The job also checks to see if the Oracle SID conforms to DISA STIG V-61413 – Oracle instance name - or SID should not contain Oracle version numbers. + or SID shouldn't contain Oracle version numbers. - [Oracle_RemoteOSAuthentication Job](/docs/accessanalyzer/12.0/solutions/databases/oracle/configuration/oracle_remoteosauthentication.md) – This job is designed to find out if remote OS authentication is enabled for the targeted Oracle database servers diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/overview.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/overview.md index adcd506425..6155417ad9 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/overview.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/overview.md @@ -15,7 +15,7 @@ access the data, and how each database has been configured. This solution is a comprehensive part of the Data Access Governance suite for structured and unstructured data. Access Analyzer for Oracle automates the process of understanding where Oracle -databases exist and provides an overview of the Oracle environment in order to answer questions +databases exist and provides an overview of the Oracle environment to answer questions around data access: - Who HAS access to your data? @@ -25,11 +25,11 @@ around data access: With visibility into every corner of Oracle® server and the Windows® operating system it relies upon, organizations can proactively highlight and prioritize risks to sensitive data. Additionally, organizations can automate manual, time-consuming, and expensive processes associated with -compliance, security, and operations to easily adhere to best practices that keep Oracle Server safe +compliance, security, and operations to adhere to best practices that keep Oracle Server safe and operational. The Oracle Solution requires a special Access Analyzer license. The Database Solution license -includes all supported database platforms supported by Access Analyzer. Additionally, Sensitive Data +includes all database platforms supported by Access Analyzer. Additionally, Sensitive Data Discovery enables the solution to search database content for sensitive data. **Supported Platforms** @@ -46,22 +46,22 @@ topic for additional information. **Sensitive Data Discovery Considerations** -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the minimum amount +If running Sensitive Data Discovery (SDD) scans, increase the minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host.For example, if the job is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are required (8x2=16). :::note The appropriate JDK (Java) version for Sensitive Data Discovery is installed on the -server. The JDK deployed is prepackaged and does not require any configuration; it has been -preconfigured to work with Access Analyzer and should never be customized through Java. It will not +server. The JDK deployed is prepackaged and preconfigured to work with Access Analyzer, requires no +additional configuration, and should never be customized through Java. It doesn't conflict with other JDKs or Java Runtimes in the same environment. ::: **Location** -The Oracle Solution requires a special Access Analyzer license. It can be installed from the Access -Analyzer Instant Job Wizard. Once it has been installed into the Jobs tree, navigate to the +The Oracle Solution requires a special Access Analyzer license. Install it from the Access +Analyzer Instant Job Wizard. After you install it into the Jobs tree, navigate to the solution: **Jobs** > **Databases** > **0.Collection** > **Oracle** for the 0.Collection job group for Oracle. @@ -69,7 +69,7 @@ The 0.Collection Job Group discovers Oracle Instances on the target hosts. The o **Jobs** > **Databases** > **Oracle** analyze and report on the data collected by the 0.Collection Job Group. -The Database Solution license includes all supported database platforms supported by Access +The Database Solution license includes all database platforms supported by Access Analyzer. Additionally, Sensitive Data Discovery enables the solution to search database content for sensitive data. diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/permissions/oracle_domainuserpermissions.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/permissions/oracle_domainuserpermissions.md index 5018b8750a..9b73735953 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/permissions/oracle_domainuserpermissions.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/permissions/oracle_domainuserpermissions.md @@ -15,7 +15,7 @@ Navigate to the **Oracle** > **3.Permissions** > **Oracle_DomainUserPermissions* node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/permissions/oracle_objectpermissions.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/permissions/oracle_objectpermissions.md index 0c3f0db586..51ee092f25 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/permissions/oracle_objectpermissions.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/permissions/oracle_objectpermissions.md @@ -15,7 +15,7 @@ Navigate to the **Oracle** > **3.Permissions** > **Oracle_ObjectPermissions** > and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/permissions/oracle_publicpermissions.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/permissions/oracle_publicpermissions.md index ed682eed47..4e51f9f958 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/permissions/oracle_publicpermissions.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/permissions/oracle_publicpermissions.md @@ -15,7 +15,7 @@ Navigate to the **Oracle** > **3.Permissions** > **Oracle_PublicPermissions** > and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/permissions/oracle_serverpermissions.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/permissions/oracle_serverpermissions.md index 21cfd975de..f3b2413d0b 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/permissions/oracle_serverpermissions.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/permissions/oracle_serverpermissions.md @@ -15,7 +15,7 @@ Navigate to the **Oracle** > **3.Permissions** > **Oracle_ServerPermissions** > and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/permissions/oracle_sysschemapermissions.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/permissions/oracle_sysschemapermissions.md index c911f09063..ffa54c4f56 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/permissions/oracle_sysschemapermissions.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/permissions/oracle_sysschemapermissions.md @@ -15,7 +15,7 @@ Navigate to the **Oracle** > **3.Permissions** > **Oracle_SysSchemaPermissions** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/recommended.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/recommended.md index 977a1c8ec2..ea47f70b1a 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/recommended.md @@ -6,10 +6,10 @@ sidebar_position: 10 # Recommended Configuration -The Oracle Solution has been configured to inherit down from the Oracle > Settings node. However, it -is best practice to assign the host list and the Connection Profile at the data collection level, -0.Collection Job Group. Once these are assigned to the job group, it can be run directly or -scheduled. +By default, the Oracle Solution inherits from the Oracle > Settings node. However, it's best +practice to assign the host list and the Connection Profile at the data collection level, +0.Collection Job Group. After you assign these to the job group, you can run it directly or +schedule it. **Dependencies** @@ -18,19 +18,18 @@ scheduled. databases Some of the queries in the **Jobs** > **Databases** > **0.Collection** > **Oracle Job Group** can be -scoped to target specific databases and/or instances. However, it is necessary for the -SA_SQL_Instances table to be populated before attempting to scope the queries. Therefore, the -0-Oracle_Servers job must be executed before attempting to scope the rest of the 0.Collection Job -Group queries. +scoped to target specific databases and/or instances. However, you must populate the +SA_SQL_Instances table before you scope the queries. Therefore, run the 0-Oracle_Servers job before +you scope the rest of the 0.Collection Job Group queries. -**Targeted Host(s)** +**Targeted Hosts** The 0.Collection Job Group must be set to run against the following dynamic host list: - Oracle Servers Default dynamic host lists are populated from hosts in the Host Master Table which meet the host -inventory criteria for the list. Ensure the appropriate host list(s) have been populated through +inventory criteria for the list. Ensure the appropriate host lists have been populated through host inventory results. **Connection Profile** @@ -38,20 +37,19 @@ host inventory results. The SQL Data Collector requires a specific set of permissions. The account used can be either an Active Directory account or an Oracle account. -For a Windows-integrated Oracle instance it is possible to use one Active Directory credential that +For a Windows-integrated Oracle instance, you can use one Active Directory credential that has permissions on both the Oracle database and the server. This will not generally be the case in most customer environments, but it is possible. -If the required permissions are assigned to one Active Directory credential, once the account has -been provisioned, create a custom Connection Profile containing the credentials for the targeted -environment. See the [SQL Data Collector](/docs/accessanalyzer/12.0/admin/datacollector/sql/overview.md) topic for +After you provision an Active Directory account with the required permissions, create a custom +Connection Profile containing the credentials for the targeted environment. See the [SQL Data Collector](/docs/accessanalyzer/12.0/admin/datacollector/sql/overview.md) topic for additional information on permissions and creating a SQL custom connection profile. Alternatively, create a connection profile with both the Oracle database credentials and the server credentials for the targeted host. -A Connection Profile with the applicable permissions should be assigned under each jobs Connection -node as follows: +Assign a Connection Profile with the applicable permissions under each job's Connection node as +follows: - Both the Oracle database credentials and the Server credentials for the targeted host (or the previously provisioned AD credentials) for: @@ -66,7 +64,7 @@ node as follows: The Connection Profile is set to Use the Default Profile, as configured at the global settings level. However, since this may not be the Connection Profile with the necessary permissions for the assigned hosts, click the radio button for the Select one of the following user defined profiles -option and select the appropriate Connection Profile drop-down menu. +option and select the appropriate Connection Profile dropdown menu. See the [Connection](/docs/accessanalyzer/12.0/admin/settings/connection/overview.md) topic for additional information. @@ -121,13 +119,13 @@ SQL Data Collector configurations can be modified if desired: **Analysis Configuration** This solution should be run with the default analysis configurations. These analysis tasks are -preconfigured and should not be modified or deselected! +preconfigured and shouldn't be modified or deselected. Remember, disabling obsolete or un-desired jobs allows the solution to run more efficiently. To -disable a job or job group, right-click on the item and select Disable Job. +disable a job or job group, right-click the item and select Disable Job. :::info -Do not delete any jobs. Instead, jobs should be disabled. +Don't delete jobs. Instead, disable them. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/sensitivedata/oracle_sensitivedata.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/sensitivedata/oracle_sensitivedata.md index 43983547c6..dd430dd7f9 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/sensitivedata/oracle_sensitivedata.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/sensitivedata/oracle_sensitivedata.md @@ -15,7 +15,7 @@ Navigate to the **Oracle > 5.Sensitve Data > Oracle_SensitveData > Configure** n **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/sensitivedata/oracle_sensitivedatapermissions.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/sensitivedata/oracle_sensitivedatapermissions.md index 308a9bb6d7..9ea224d59b 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/sensitivedata/oracle_sensitivedatapermissions.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/sensitivedata/oracle_sensitivedatapermissions.md @@ -15,7 +15,7 @@ Navigate to the **Oracle > 5.Sensitive Data > Oracle_SensitiveDataPermissions > select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/usersroles/oracle_passwordissues.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/usersroles/oracle_passwordissues.md index 33169449ec..f03b5470a2 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/usersroles/oracle_passwordissues.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/usersroles/oracle_passwordissues.md @@ -15,7 +15,7 @@ passwords. The Oracle_PasswordIssues Job uses the PowerShell Data Collector for the following query: :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -33,7 +33,7 @@ Navigate to the **Jobs** > **Oracle** > **1.Users and Roles** > **Oracle_Passwor **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/usersroles/oracle_rolemembers.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/usersroles/oracle_rolemembers.md index f927578638..76f50a8036 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/usersroles/oracle_rolemembers.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/usersroles/oracle_rolemembers.md @@ -15,7 +15,7 @@ Navigate to the **Oracle** > **1.Users and Roles** > **Oracle_RoleMembers** > Co select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/usersroles/oracle_systemadministrators.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/usersroles/oracle_systemadministrators.md index 4a7d0dd74e..634f126fe4 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/usersroles/oracle_systemadministrators.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/usersroles/oracle_systemadministrators.md @@ -15,7 +15,7 @@ Navigate to the **Oracle** > **1.Users and Roles** > **Oracle_SystemAdministrato node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/oracle/usersroles/oracle_users.md b/docs/accessanalyzer/12.0/solutions/databases/oracle/usersroles/oracle_users.md index 5820ee8274..82bb025d61 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/oracle/usersroles/oracle_users.md +++ b/docs/accessanalyzer/12.0/solutions/databases/oracle/usersroles/oracle_users.md @@ -15,7 +15,7 @@ Navigate to the **Oracle** > **1.Users and Roles** > **Oracle_Users** > **Config select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/overview.md b/docs/accessanalyzer/12.0/solutions/databases/overview.md index 4c5ebf1fc2..6c035e0cdd 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/overview.md +++ b/docs/accessanalyzer/12.0/solutions/databases/overview.md @@ -23,7 +23,7 @@ reports that provide visibility into various aspects of supported databases: order to answer questions around data access. - [PostgreSQL Solution](/docs/accessanalyzer/12.0/solutions/databases/postgresql/overview.md) – Access Analyzer for PostgreSQL automates the process of understanding where PostgreSQL databases exist and provides an overview of the - PostgreSQL environment in order to answer questions around data access. + PostgreSQL environment to answer questions around data access. - [Redshift Solution](/docs/accessanalyzer/12.0/solutions/databases/redshift/overview.md) – Redshift Solution Set is a comprehensive set of pre-configured audit jobs and reports that provide visibility into various aspects of Redshift: Data Collection, Configuration, and Sensitive Data. @@ -32,8 +32,8 @@ reports that provide visibility into various aspects of supported databases: configuration, sensitive data, and overall security assessment for both the SQL 0.Collection Job Group and Azure SQL 0.Collection Job Group. -The Database Solution license includes all supported database platforms supported by Access -Analyzer. Additionally, Sensitive Data Discovery enables the solution to search database content for +The Database Solution license includes all database platforms supported by Access Analyzer. +Additionally, Sensitive Data Discovery enables the solution to search database content for sensitive data. The following table identifies the type of audit functionality for each supported database platform: @@ -48,7 +48,7 @@ The following table identifies the type of audit functionality for each supporte | PostgreSQL | | \*Partially Supported | | Fully Supported | \*\*Partially Supported | | Redshift | | \*Partially Supported | | Fully Supported | \*\*Partially Supported | -In the above table: +In this table: - \*Partially Supported, "Permission Audit" means the permissions as solely collected at the table level. diff --git a/docs/accessanalyzer/12.0/solutions/databases/postgresql/collection/pgsql_configuration.md b/docs/accessanalyzer/12.0/solutions/databases/postgresql/collection/pgsql_configuration.md index 6f5b04797f..308ab2d1db 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/postgresql/collection/pgsql_configuration.md +++ b/docs/accessanalyzer/12.0/solutions/databases/postgresql/collection/pgsql_configuration.md @@ -14,7 +14,7 @@ PostgreSQL servers. The PgSQL_Configuration Job uses the SQL Data Collector. :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/postgresql/collection/pgsql_sensitivedatascan.md b/docs/accessanalyzer/12.0/solutions/databases/postgresql/collection/pgsql_sensitivedatascan.md index 2d20e518a9..4e5abba40e 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/postgresql/collection/pgsql_sensitivedatascan.md +++ b/docs/accessanalyzer/12.0/solutions/databases/postgresql/collection/pgsql_sensitivedatascan.md @@ -24,18 +24,18 @@ The query is: ### Configure the SensitiveDataScan Query The PgSQL_SensitiveDataScan Job is preconfigured to run using the default settings for the Sensitive -Data Collection category. Follow the steps to customize configurations. +Data Collection category. To customize configurations, complete the following steps. **Step 1 –** Navigate to the **Databases** > **0.Collection** > **PostgreSQL** > **PgSQL_SensitiveDataScan** > **Configure** node and select Queries. -**Step 2 –** In the Query Selection view, select the **PostgreSQL** query click on Query Properties. +**Step 2 –** In the Query Selection view, select the **PostgreSQL** query click Query Properties. The Query Properties window appears. **Step 3 –** Select the Data Source tab, and click Configure. The SQL Data Collector Wizard opens. :::warning -Do not make changes to other wizard pages as they have been pre-configured for this +Don't make changes to other wizard pages as they have been pre-configured for this job. ::: @@ -43,8 +43,8 @@ job. ![Sensitive Data Scan Settings](/images/accessanalyzer/12.0/solutions/databases/postgresql/collection/datascanjobsettings.webp) **Step 4 –** To modify sensitive data scan options, navigate to the -[SQL Data Collector](/docs/accessanalyzer/12.0/admin/datacollector/sql/overview.md) page. Select the desired scan -options. +[SQL Data Collector](/docs/accessanalyzer/12.0/admin/datacollector/sql/overview.md) page. Select the scan +options you want. :::note The Sensitive Data Scan Settings are pre-configured for optimal performance for a @@ -64,8 +64,8 @@ topic for additional information. ![Filters page](/images/accessanalyzer/12.0/solutions/databases/postgresql/collection/sensitivedatascanfilter.webp) -**Step 6 –** PostgreSQL databases must be added to the query before they can be scanned. Navigate to -the **Filter** page and click **Connections** to open the Manage Connections window. +**Step 6 –** Add PostgreSQL databases to the query before you scan them. Navigate to the +**Filter** page and click **Connections** to open the Manage Connections window. ![Manage Connections](/images/accessanalyzer/12.0/solutions/databases/postgresql/collection/manageconnectionspgsql.webp) @@ -83,9 +83,9 @@ Exit the Manage Connections window to return to the Filter page. **Step 8 –** On the Filter page, the query is configured by default to target Only select database objects. Click Retrieve. The Available database objects box will populate. The default filter will scan all PostgreSQL databases returned, excluding the listed system or default schemas and tables in -red. Databases and instances can be added in the following ways: +red. Add databases and instances in the following ways: -- Select the desired database objects and click Add. +- Select the database objects you want and click Add. - Use the Import CSV button to import a list from a CSV file, if desired. - Use the Add Custom Filter button to create and apply a custom filter. @@ -100,7 +100,7 @@ Navigate to the **Databases** > **0.Collection** > **PostgreSQL** > **PgSQL_Sen **Configure** node and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/postgresql/collection/pgsql_tableprivileges.md b/docs/accessanalyzer/12.0/solutions/databases/postgresql/collection/pgsql_tableprivileges.md index edbb748270..57acfb9b73 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/postgresql/collection/pgsql_tableprivileges.md +++ b/docs/accessanalyzer/12.0/solutions/databases/postgresql/collection/pgsql_tableprivileges.md @@ -14,7 +14,7 @@ targeted servers. The PgSQL_TablePrivileges Job uses the SQL Data Collector for queries. :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -30,7 +30,7 @@ Navigate to the **Databases** > **0.Collection** > **PostgreSQL** > **PgSQL_Tabl **Configure** node and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/postgresql/overview.md b/docs/accessanalyzer/12.0/solutions/databases/postgresql/overview.md index 3840fbafc7..a7c139d0b1 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/postgresql/overview.md +++ b/docs/accessanalyzer/12.0/solutions/databases/postgresql/overview.md @@ -6,16 +6,15 @@ sidebar_position: 50 # PostgreSQL Solution -Data privacy and security is quickly evolving to be on equal footing with traditional security -measures focused on the network, hardware, or software the data is contained within. Organizations -aligning to concepts like Data-Centric Audit and Protection (DCAP) as defined by Gartner, or the -requirements of strict compliance regulations like EU GDPR, are looking to implement processes that -help them understand where sensitive data is stored, who or what is leveraging their privileges to -access the data, and how each database has been configured. +Data privacy is becoming as important as traditional security measures focused on the network, +hardware, or software that stores the data. Organizations that align with concepts like +Data-Centric Audit and Protection (DCAP), as defined by Gartner, or with strict compliance +regulations like the EU GDPR, want to understand where sensitive data is stored, who has access to +it, and how each database is configured. As part of Netwrix comprehensive Data Access Governance suite for structured and unstructured data, Access Analyzer for PostgreSQL automates the process of understanding where PostgreSQL databases -exist and provides an overview of the PostgreSQL environment in order to answer questions around +exist and provides an overview of the PostgreSQL environment to answer questions around data access: - Who has access to your data? @@ -23,8 +22,8 @@ data access: With visibility into every corner of PostgreSQL, organizations can proactively highlight and prioritize risks to sensitive data. Additionally, organizations can automate manual, time-consuming, -and expensive processes associated with compliance, security, and operations to easily adhere to -best practices that keep PostgreSQL Server safe and operational. +and expensive processes associated with compliance, security, and operations to adhere to best +practices that keep PostgreSQL Server safe and operational. **Supported Platforms** @@ -41,16 +40,16 @@ topic for additional information. **Sensitive Data Discovery Considerations** -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the minimum amount -of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For example, if the job -is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are required (8x2=16). +If you run Sensitive Data Discovery (SDD) scans, increase the minimum amount of RAM. Each thread +requires a minimum of 2 additional GB of RAM per host. For example, if the job is configured to +scan 8 hosts at a time, it requires an extra 16 GB of RAM (8 x 2 = 16). By default, the job is configured to use 10 threads, which can be adjusted based on available resources on the Access Analyzer server. :::note The appropriate JDK (Java) version for Sensitive Data Discovery is installed on the -server. The JDK deployed is prepackaged and does not require any configuration; it has been +server. The JDK deployed is prepackaged and doesn't require any configuration; it has been preconfigured to work with Access Analyzer and should never be customized through Java. It will not conflict with other JDKs or Java Runtimes in the same environment. ::: @@ -59,15 +58,15 @@ conflict with other JDKs or Java Runtimes in the same environment. **Location** The Structured Sensitive Data Discovery License is required to run the PostgreSQL Solution. It can -be installed from theAccess Analyzer Instant Job Wizard. Once it has been installed into the Jobs +be installed from theAccess Analyzer Instant Job Wizard. After it has been installed into the Jobs tree, navigate to the solution: Jobs > **Databases** > PostgreSQL. The 0.Collection Job Group performs sensitive data discovery and collects information on database configurations on the target hosts. The other job groups analyze and report on the data collected by the 0.Collection Job Group. -The Database Solution license includes all supported database platforms supported by Access -Analyzer. Additionally, Sensitive Data Discovery enables the solution to search database content for +The Database Solution license includes all database platforms supported by Access Analyzer. +Additionally, Sensitive Data Discovery enables the solution to search database content for sensitive data. ## Job Groups diff --git a/docs/accessanalyzer/12.0/solutions/databases/postgresql/pgsql_databasesizing.md b/docs/accessanalyzer/12.0/solutions/databases/postgresql/pgsql_databasesizing.md index 783ffdc1c0..9efa9f27d9 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/postgresql/pgsql_databasesizing.md +++ b/docs/accessanalyzer/12.0/solutions/databases/postgresql/pgsql_databasesizing.md @@ -21,7 +21,7 @@ Navigate to the **Jobs > Databases > PostgreSQL > Configuration > PgSQL_Databa node and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/postgresql/recommended.md b/docs/accessanalyzer/12.0/solutions/databases/postgresql/recommended.md index da349a7e38..fae27a4ac4 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/postgresql/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/databases/postgresql/recommended.md @@ -6,19 +6,19 @@ sidebar_position: 10 # Recommended Configuration for the PostgreSQL Solution -The jobs in the PostgreSQL Solution has been configured to inherit down from the **PostgreSQL** > -**Settings** node. However, it is best practice to assign the host list and the Connection Profile -at the data collection level, 0.Collection Job Group. Once these are assigned to the job group, it -can be run directly or scheduled. +By default, the jobs in the PostgreSQL Solution inherit from the **PostgreSQL** > **Settings** node. +However, it's best practice to assign the host list and the Connection Profile at the data +collection level, 0.Collection Job Group. After you assign these to the job group, you can run it +directly or schedule it. **Dependencies** - **.Active Directory Inventory** Job Group run successfully - For AWS RDS and Aurora instances, right-click a job in the **PostgreSQL** > **0.Collection** folder and open the properties window. Select the **Performance** tab and ensure that the **Skip - Hosts that do not respond to PING**checkbox is not selected. + Hosts that don't respond to PING**checkbox isn't selected. -**Targeted Host(s)** +**Targeted Hosts** - The 0.Collection Job Group must be set to run against a custom host list containing the PostgreSQL database instances / clusters. @@ -35,7 +35,7 @@ permissions and creating a SQL custom connection profile. The Connection Profile is set to **Use the Default Profile**, as configured at the global settings level. However, since this may not be the Connection Profile with the necessary permissions for the assigned hosts, click the radio button for the **Select one of the following user defined profiles** -option and select the appropriate Connection Profile drop-down menu. +option and select the appropriate Connection Profile dropdown menu. **Schedule Frequency** @@ -60,12 +60,12 @@ topic for additional information. **Analysis Configuration** This solution should be run with the default analysis configurations. These analysis tasks are -preconfigured and should not be modified or deselected! +preconfigured and shouldn't be modified or deselected. Disabling obsolete or run-desired jobs allows the solution to run more efficiently. To disable a job -or job group, right-click on the item and select **Disable Job**. +or job group, right-click the item and select **Disable Job**. :::info -Do not delete any jobs. Instead, jobs should be disabled. +Don't delete jobs. Instead, disable them. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/postgresql/sensitivedata/pgsql_sensitivedata.md b/docs/accessanalyzer/12.0/solutions/databases/postgresql/sensitivedata/pgsql_sensitivedata.md index c5c668aa0c..93b3a7abe6 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/postgresql/sensitivedata/pgsql_sensitivedata.md +++ b/docs/accessanalyzer/12.0/solutions/databases/postgresql/sensitivedata/pgsql_sensitivedata.md @@ -15,7 +15,7 @@ Navigate to the **Jobs > Databases > PostgreSQL > Sensitive Data > PgSQL_Sens node and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/postgresql/sensitivedata/pgsql_sensitivedatapermissions.md b/docs/accessanalyzer/12.0/solutions/databases/postgresql/sensitivedata/pgsql_sensitivedatapermissions.md index a091d58cbc..ca8b08a6cc 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/postgresql/sensitivedata/pgsql_sensitivedatapermissions.md +++ b/docs/accessanalyzer/12.0/solutions/databases/postgresql/sensitivedata/pgsql_sensitivedatapermissions.md @@ -17,7 +17,7 @@ Data > PgSQL_SensitiveDataPermissions > Configure** node and select Analysis t tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/redshift/collection/overview.md b/docs/accessanalyzer/12.0/solutions/databases/redshift/collection/overview.md index 79e4e2e17c..9c3dfb2166 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/redshift/collection/overview.md +++ b/docs/accessanalyzer/12.0/solutions/databases/redshift/collection/overview.md @@ -7,7 +7,7 @@ sidebar_position: 20 # 0.Collection Job Group The Redshift Solution Collection group collects high level summary information from targeted -Redshift Servers.  Other jobs in the Redshift Solution Set use this information for further analysis +Redshift Servers. Other jobs in the Redshift Solution Set use this information for further analysis and for producing respective reports. ![0](/images/accessanalyzer/12.0/solutions/databases/redshift/collection/0.collection.webp) diff --git a/docs/accessanalyzer/12.0/solutions/databases/redshift/collection/redshift_configuration.md b/docs/accessanalyzer/12.0/solutions/databases/redshift/collection/redshift_configuration.md index 76ae3a75fa..3ae493956e 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/redshift/collection/redshift_configuration.md +++ b/docs/accessanalyzer/12.0/solutions/databases/redshift/collection/redshift_configuration.md @@ -13,7 +13,7 @@ The Redshift_Configuration job returns additional configuration settings from Re The Redshift_Configuration Job uses the SQL Data Collector for queries. :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/redshift/collection/redshift_sensitivedatascan.md b/docs/accessanalyzer/12.0/solutions/databases/redshift/collection/redshift_sensitivedatascan.md index 565f1ea3dd..2173a38c4d 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/redshift/collection/redshift_sensitivedatascan.md +++ b/docs/accessanalyzer/12.0/solutions/databases/redshift/collection/redshift_sensitivedatascan.md @@ -22,14 +22,14 @@ The query is: ## Recommended Configuration for the SensitiveDataScan Query The Redshift_SensitiveDataScan Job is preconfigured to run using the default settings for the -Sensitive Data Collection category. It is necessary only to set up the connection for the Redshift- -SensitiveDataScan Job. Once the connection is established, it applies to any other 0.Collection job -query. Follow the steps to customize configurations. +Sensitive Data Collection category. You only need to set up the connection for the +Redshift_SensitiveDataScan Job once. After you establish the connection, it applies to any other +0.Collection job query. To customize configurations, complete the following steps. **Step 1 –** Navigate to the **Databases** > **0.Collection** > **Redshift** > **Redshift_SensitiveDataScan** > **Configure** node and select Queries. -**Step 2 –** In the Query Selection view, select the Redshift Sensitive Data Scan query click on +**Step 2 –** In the Query Selection view, select the Redshift Sensitive Data Scan query click Query Properties. The Query Properties window appears. **Step 3 –** Select the Data Source tab, and click Configure. The SQL Data Collector Wizard opens @@ -41,7 +41,7 @@ with Sensitive Data Collection category selected. ![Sensitive Data Scan Settings](/images/accessanalyzer/12.0/solutions/databases/redshift/collection/collectionsensitivedatajoboptions.webp) -**Step 5 –** To modify sensitive data scan options, select the desired scan options. See the +**Step 5 –** To modify sensitive data scan options, select the scan options you want. See the [SQL: Options](/docs/accessanalyzer/12.0/admin/datacollector/sql/options.md) page for additional information. :::note @@ -55,7 +55,7 @@ may significantly increase scan time. ![Select DLP Criteria for Scan](/images/accessanalyzer/12.0/solutions/databases/redshift/collection/collectionsensitivedatacriteria.webp) -**Step 7 –** To modify criteria, click on **Use the following selected criteria:** and select your +**Step 7 –** To modify criteria, click **Use the following selected criteria:** and select your choices. By default, the Sensitive Data Scan job is set to **Use Global Criteria**. Also by default, the following System Criteria have been selected: @@ -80,8 +80,8 @@ topic for additional information. **Step 9 –** Click **Connections** to open the Manage Connections window. :::note -SQL databases must be added to the query before they can be scanned. Before you can add a -query, you must establish a connection to the database. +Add SQL databases to the query before you scan them. Before you add a query, establish a +connection to the database. ::: @@ -111,10 +111,9 @@ For more information on filtering, see the **Step 13 –** Click Retrieve. The Available database objects box will populate. -**Step 14 –** Add the Databases and instances to be audited. Databases and instances can be added in -the following ways: +**Step 14 –** Add the databases and instances to audit, using any of the following methods: -- Select the desired database objects and click Add. +- Select the database objects you want and click Add. - Use the Import CSV button to import a list from a CSV file, if desired. - Optionally use the Add Custom Filter button to create and apply a custom filter. @@ -129,12 +128,12 @@ The 1-Db2_SensitsveDataScan Job is now ready to run with the customized settings ## Analysis Tasks for the Redshift_SensitiveDataScan Navigate to the \_**\_Databases > 0.Collection >**Redshift >\_\_ **Redshift_SensitiveDataScan** > -**Configure** node and select **Analysis** to view the Analysis Tasks. The Analysis tasks do not +**Configure** node and select **Analysis** to view the Analysis Tasks. The Analysis tasks don't require any configuration as they just populate the reports with the collected information and do not collect data themselves. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/redshift/collection/redshift_tableprivileges.md b/docs/accessanalyzer/12.0/solutions/databases/redshift/collection/redshift_tableprivileges.md index a8cadb210a..07fdcb7938 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/redshift/collection/redshift_tableprivileges.md +++ b/docs/accessanalyzer/12.0/solutions/databases/redshift/collection/redshift_tableprivileges.md @@ -14,7 +14,7 @@ targeted servers. The Redshift_TablePrivileges Job uses the SQL Data Collector for queries. :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -30,7 +30,7 @@ Navigate to the **Databases** > **0.Collection** > **Redshift** > **Redshift_Tab **Configure** node and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/redshift/overview.md b/docs/accessanalyzer/12.0/solutions/databases/redshift/overview.md index 3ef9402c24..f9c7aa9219 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/redshift/overview.md +++ b/docs/accessanalyzer/12.0/solutions/databases/redshift/overview.md @@ -26,16 +26,16 @@ topic for additional information. **Sensitive Data Discovery Considerations** -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the minimum amount -of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For example, if the job -is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are required (8x2=16). +If you run Sensitive Data Discovery (SDD) scans, increase the minimum amount of RAM. Each thread +requires a minimum of 2 additional GB of RAM per host. For example, if the job is configured to +scan 8 hosts at a time, it requires an extra 16 GB of RAM (8 x 2 = 16). By default, the job is configured to use 10 threads, which can be adjusted based on available resources on the Access Analyzer server. :::note The appropriate JDK (Java) version for Sensitive Data Discovery is installed on the -server. The JDK deployed is prepackaged and does not require any configuration; it has been +server. The JDK deployed is prepackaged and doesn't require any configuration; it has been preconfigured to work with Access Analyzer and should never be customized through Java. It will not conflict with other JDKs or Java Runtimes in the same environment. ::: @@ -44,14 +44,14 @@ conflict with other JDKs or Java Runtimes in the same environment. **Location** The Redshift Solution requires a special Access Analyzer license. It can be installed from the -Access Analyzer Instant Job Wizard. Once it has been installed in the **Jobs** tree, navigate to the +Access Analyzer Instant Job Wizard. After it has been installed in the **Jobs** tree, navigate to the solution: **Jobs** > **Databases** > **Redshift Solution**. The 0.Collection Job Group discovers SQL instances on the target hosts, and collects the data. The other job groups analyze the collected data and generate reports. -The Database Solution license includes all supported database platforms supported by Access -Analyzer. Additionally, Sensitive Data Discovery enables the solution to search database content for +The Database Solution license includes all database platforms supported by Access Analyzer. +Additionally, Sensitive Data Discovery enables the solution to search database content for sensitive data. ## Redshift Job Group @@ -66,7 +66,7 @@ The following job groups comprise the Redshift Job Group: - [0.Collection Job Group](/docs/accessanalyzer/12.0/solutions/databases/redshift/collection/overview.md) — Collects high level summary information from targeted Redshift Servers. Other jobs in the Redshift Solution Set use this information for further analysis and producing respective report. This Job Group is comprised of the following - jobs(s) + jobss - [Redshift_Configuration Job](/docs/accessanalyzer/12.0/solutions/databases/redshift/collection/redshift_configuration.md) - [Redshift_SensitiveDataScan Job](/docs/accessanalyzer/12.0/solutions/databases/redshift/collection/redshift_sensitivedatascan.md) @@ -78,7 +78,7 @@ The following job groups comprise the Redshift Job Group: - [Sensitive Data Job Group](/docs/accessanalyzer/12.0/solutions/databases/redshift/sensitive_data/overview.md) — Provides insight into where sensitive data exists and who has access to it across all the targeted Redshift databases.This Job Group is - comprised of the following job(s): + comprised of the following jobs: - [Redshift_SensitiveData Job](/docs/accessanalyzer/12.0/solutions/databases/redshift/sensitive_data/redshift_sensitivedata.md) - [Redshift_SensitiveDataPermissions Job](/docs/accessanalyzer/12.0/solutions/databases/redshift/sensitive_data/redshift_sensitivedatapermissions.md) diff --git a/docs/accessanalyzer/12.0/solutions/databases/redshift/recommended.md b/docs/accessanalyzer/12.0/solutions/databases/redshift/recommended.md index d7fcfa492b..d53703be5e 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/redshift/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/databases/redshift/recommended.md @@ -8,35 +8,35 @@ sidebar_position: 10 The Redshift Solution is configured to inherit settings from the global Settings node. However, it is best practice to assign the host list and the Connection Profile at the data collection level, -the 0.Collection Job Group. Once these are assigned to the job group, it can be run directly or +the 0.Collection Job Group. After these are assigned to the job group, it can be run directly or scheduled. **Dependencies** -This job group does not have dependencies. +This job group doesn't have dependencies. -**Targeted Host(s)** +**Targeted Hosts** The Redshift Job Group has been configured to inherit the host list assignment from the collection group level. -The host list assignment should be assigned under the **Redshift** > **0.Collection** > +Assign the host list under the **Redshift** > **0.Collection** > **Settings** > **Host List Assignment** node. The **Local host** box is checked by default. **Connection Profile** The SQL Data Collector requires a specific set of permissions. See the Permissions section for necessary permissions. The account used can be either an Active Directory account or a SQL account. -Once the account has been provisioned, create a custom Connection Profile containing the credentials +After the account has been provisioned, create a custom Connection Profile containing the credentials for the targeted environment. See the [SQL Custom Connection Profile & Default Dynamic Host List](/docs/accessanalyzer/12.0/admin/datacollector/sql/configurejob.md) topic for additional information. -The Connection Profile should be assigned under the **Redshift** > **0.Collection** > **Settings** > +Assign the Connection Profile under the **Redshift** > **0.Collection** > **Settings** > **Connection** node. It is set to **Use the Default Profile**, as configured at the global settings level. However, since this may not be the Connection Profile with the necessary permissions for the assigned hosts, click the radio button for the **Select one of the following user defined profiles** -option and select the appropriate Connection Profile drop-down menu. +option and select the appropriate Connection Profile dropdown menu. See the [Connection](/docs/accessanalyzer/12.0/admin/settings/connection/overview.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/solutions/databases/redshift/redshift_databasesizing.md b/docs/accessanalyzer/12.0/solutions/databases/redshift/redshift_databasesizing.md index 37e6098645..5d271f4a89 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/redshift/redshift_databasesizing.md +++ b/docs/accessanalyzer/12.0/solutions/databases/redshift/redshift_databasesizing.md @@ -6,12 +6,12 @@ sidebar_position: 30 # Configuration > Redshift_DatabaseSizing Job -This group provides insight into details about the Redshift environment and potential +This group provides details about the Redshift environment and potential vulnerabilities related to instance configuration settings. ![configurationjobgroup](/images/accessanalyzer/12.0/solutions/databases/redshift/configurationjobgroup.webp) -The job(s) in the Configuration Job Group are: +The jobs in the Configuration Job Group are: - Redshift_DatabaseSizing Job — Provides details about Redshift databases and overall database size. @@ -21,7 +21,7 @@ Navigate to the **Jobs** > **Databases**> **Redshift** > **Configuration** > **Redshift_DatabaseSizing** > **Configure** node and select **Analysis** to view the Analysis Tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/redshift/sensitive_data/overview.md b/docs/accessanalyzer/12.0/solutions/databases/redshift/sensitive_data/overview.md index 54092a3875..6dad9a1ec3 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/redshift/sensitive_data/overview.md +++ b/docs/accessanalyzer/12.0/solutions/databases/redshift/sensitive_data/overview.md @@ -5,7 +5,7 @@ targeted Redshift databases. ![sensitivedatajobgroup](/images/accessanalyzer/12.0/solutions/databases/redshift/sensitive_data/sensitivedatajobgroup.webp) -The job(s) in the Sensitive Data Job Group are: +The jobs in the Sensitive Data Job Group are: - [Redshift_SensitiveData Job](/docs/accessanalyzer/12.0/solutions/databases/redshift/sensitive_data/redshift_sensitivedata.md) - Provides information on all the data that was discovered in the targeted Redshift database servers based on the selected scan criteria diff --git a/docs/accessanalyzer/12.0/solutions/databases/redshift/sensitive_data/redshift_sensitivedata.md b/docs/accessanalyzer/12.0/solutions/databases/redshift/sensitive_data/redshift_sensitivedata.md index 08eb3c26f5..55e711c678 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/redshift/sensitive_data/redshift_sensitivedata.md +++ b/docs/accessanalyzer/12.0/solutions/databases/redshift/sensitive_data/redshift_sensitivedata.md @@ -9,7 +9,7 @@ Navigate to the **Jobs** > **Databases** > **Redshift** >  **Sensitive Data** > **Redshift_SensitiveData** > **Configure** node and select **Analysis** to view the Analysis Tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/redshift/sensitive_data/redshift_sensitivedatapermissions.md b/docs/accessanalyzer/12.0/solutions/databases/redshift/sensitive_data/redshift_sensitivedatapermissions.md index 176f13b7e9..b87e82282c 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/redshift/sensitive_data/redshift_sensitivedatapermissions.md +++ b/docs/accessanalyzer/12.0/solutions/databases/redshift/sensitive_data/redshift_sensitivedatapermissions.md @@ -11,7 +11,7 @@ Data > Redshift_SensitiveDataPermissions > Configure** node and select Analysi tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/activity/sql_activity.md b/docs/accessanalyzer/12.0/solutions/databases/sql/activity/sql_activity.md index 33e0271e31..741f2cd876 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/activity/sql_activity.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/activity/sql_activity.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 2.Activity > SQL_Activity > Configure node to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/activity/sql_logons.md b/docs/accessanalyzer/12.0/solutions/databases/sql/activity/sql_logons.md index cabdca740b..31dd8c3bdd 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/activity/sql_logons.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/activity/sql_logons.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 2.Activity > SQL_Logons > Configure node to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/activity/sql_permissionchanges.md b/docs/accessanalyzer/12.0/solutions/databases/sql/activity/sql_permissionchanges.md index 97787e34ca..52c8c0c607 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/activity/sql_permissionchanges.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/activity/sql_permissionchanges.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 2.Activity > SQL_PermissionChanges > Conf Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/activity/sql_sensitivedataactivity.md b/docs/accessanalyzer/12.0/solutions/databases/sql/activity/sql_sensitivedataactivity.md index 9c757a37a5..13e146e29f 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/activity/sql_sensitivedataactivity.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/activity/sql_sensitivedataactivity.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 2.Activity > SQL_SensitiveDataActivity > C select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/activity/sql_unusualactivity.md b/docs/accessanalyzer/12.0/solutions/databases/sql/activity/sql_unusualactivity.md index ea2add9018..32b96b1462 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/activity/sql_unusualactivity.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/activity/sql_unusualactivity.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 2.Activity > SQL_UnusualActivity > Config Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/collection/0-sql_instancediscovery.md b/docs/accessanalyzer/12.0/solutions/databases/sql/collection/0-sql_instancediscovery.md index a22f604e2f..09f1787d90 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/collection/0-sql_instancediscovery.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/collection/0-sql_instancediscovery.md @@ -24,7 +24,7 @@ Navigate to the **Databases** > **0.Collection** > **SQL** > **0-SQL_InstanceDis **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/collection/1-sql_permissionsscan.md b/docs/accessanalyzer/12.0/solutions/databases/sql/collection/1-sql_permissionsscan.md index a8a2d69cfc..3ba9c41653 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/collection/1-sql_permissionsscan.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/collection/1-sql_permissionsscan.md @@ -23,18 +23,18 @@ The 1-SQL_PermissionsScan Job uses the SQL Data Collector for the following quer ### Configure the PermissionsScan Query The 1-SQL_PermissionScan Job is preconfigured to run using the default settings within the -Permissions Collection category. Follow the steps to customize configurations. +Permissions Collection category. To customize configurations, complete the following steps. **Step 1 –** Navigate to the **Databases** > 0.Collection > SQL > 1-SQL_PermissionsScan > Configure node and select Queries. -**Step 2 –** In the Query Selection view, select the PermissionsScan query and click on Query +**Step 2 –** In the Query Selection view, select the PermissionsScan query and click Query Properties. The Query Properties window appears. **Step 3 –** Select the Data Source tab and click Configure. The SQL Data Collector Wizard opens. :::warning -Do not make changes to other wizard pages as they have been pre-configured for this +Don't make changes to other wizard pages as they have been pre-configured for this job. ::: @@ -47,7 +47,7 @@ is All databases. The default query scope is Only select database objects and cl Available database objects will be populated. Databases and instances can be added in the following ways: -- Select the desired database objects and click Add. +- Select the database objects you want and click Add. - Use the Import CSV button to import a list from a CSV file, if desired. - Optionally, use the Add Custom Filter button to create and apply a custom filter. @@ -62,7 +62,7 @@ Navigate to the **Databases** > 0.Collection > SQL > 1-SQL_PermissionsScan > Con select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -71,8 +71,8 @@ preconfigured for this job. The default analysis tasks are: -- Remove Old AIC Resources — Removes AIC resources using the old path that did not include the - schema +- Remove Old AIC Resources — Removes Access Information Center (AIC) resources using the old path + that didn't include the schema - AIC Import – Hosts — Imports SQL hosts to the AIC - AIC Import – Instance Permissions Node — Imports a node for instance permissions for each instance - AIC Import – Databases — Imports each database in the SQL instances diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/collection/2-sql_sensitivedatascan.md b/docs/accessanalyzer/12.0/solutions/databases/sql/collection/2-sql_sensitivedatascan.md index 5d99b45c9f..19fbe23561 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/collection/2-sql_sensitivedatascan.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/collection/2-sql_sensitivedatascan.md @@ -34,25 +34,25 @@ The SensitiveDataScan Job uses the SQL Data Collector for the following query: ### Configure the SensitiveDataScan Query The 2-SQL_SensitiveDataScan Job is preconfigured to run using the default settings for the Sensitive -Data Collection category. Follow the steps to customize configurations. +Data Collection category. To customize configurations, complete the following steps. **Step 1 –** Navigate to the **Databases** > 0.Collection > SQL > 2-SQL_SensitiveDataScan > Configure node and select Queries. -**Step 2 –** In the Query Selection view, select the SensitiveDataScan query click on Query +**Step 2 –** In the Query Selection view, select the SensitiveDataScan query click Query Properties. The Query Properties window appears. **Step 3 –** Select the Data Source tab, and click Configure. The SQL Data Collector Wizard opens. :::warning -Do not make changes to other wizard pages as they have been pre-configured for this +Don't make changes to other wizard pages as they have been pre-configured for this job. ::: ![2sqlsensitivedatascanoptionspage](/images/accessanalyzer/12.0/solutions/databases/sql/collection/2sqlsensitivedatascanoptionspage.webp) -**Step 4 –** Select the desired scan options. Navigate to the +**Step 4 –** Select the scan options you want. Navigate to the [SQL: Options](/docs/accessanalyzer/12.0/admin/datacollector/sql/options.md) page for additional information. :::note @@ -85,7 +85,7 @@ System Criteria have been selected: default to target Only select database objects. Click Retrieve. The Available database objects box will populate. Databases and instances can be added in the following ways: -- Select the desired database objects and click Add. +- Select the database objects you want and click Add. - Use the Import CSV button to import a list from a CSV file, if desired. - Optionally use the Add Custom Filter button to create and apply a custom filter. @@ -100,7 +100,7 @@ Navigate to the **Databases** > 0.Collection > SQL > 2-SQL_SensitiveDataScan > select Analysis to view the analysis task. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/collection/3-sql_activityscan.md b/docs/accessanalyzer/12.0/solutions/databases/sql/collection/3-sql_activityscan.md index 48bc6b61d2..ca54a77e89 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/collection/3-sql_activityscan.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/collection/3-sql_activityscan.md @@ -30,18 +30,18 @@ The ActivityScan Job uses the SQL Data Collector for the following query: ### Configure the ActivityScan Query The 3-SQL_ActivityScan Job is preconfigured to run using the default settings within the Server -Audits Events Collection category. Follow the steps to customize configurations. +Audits Events Collection category. To customize configurations, complete the following steps. **Step 1 –** Navigate to the **Databases** > 0.Collection > SQL > 3-SQL_ActivityScan > Configure node and select Queries. -**Step 2 –** In the Query Selection view, click on Query Properties. The Query Properties window +**Step 2 –** In the Query Selection view, click Query Properties. The Query Properties window appears. **Step 3 –** Select the Data Source tab, and click Configure. The SQL Data Collector Wizard opens. :::warning -Do not make changes to other wizard pages as they have been pre-configured for the +Don't make changes to other wizard pages as they have been pre-configured for the purpose of this job. ::: @@ -49,8 +49,8 @@ purpose of this job. ![Options Page](/images/accessanalyzer/12.0/solutions/databases/sql/collection/3sqlactivityscanoptionspage.webp) **Step 4 –** To modify scan options, navigate to the -[SQL Data Collector](/docs/accessanalyzer/12.0/admin/datacollector/sql/overview.md) page. Select the desired scan -options. The query is preconfigured with the following default settings: +[SQL Data Collector](/docs/accessanalyzer/12.0/admin/datacollector/sql/overview.md) page. Select the scan options +you want. The query is preconfigured with the following default settings: - Collect only events since last scan – Collects activity recorded since the previous scan - Number of days you want to keep events in the database – The default setting is 15 days @@ -64,7 +64,7 @@ options. The query is preconfigured with the following default settings: by default to target Only select database objects. Click Retrieve. The Available database objects will be populated. Databases and instances can be added in the following ways: -Select the desired database objects and click Add. +Select the database objects you want and click Add. Use the Import CSV button to import a list from a CSV file. @@ -81,7 +81,7 @@ Navigate to the **Databases** > 0.Collection > SQL > 3-SQL_ActivityScan > Config Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/collection/4-sql_serverlogons.md b/docs/accessanalyzer/12.0/solutions/databases/sql/collection/4-sql_serverlogons.md index faa36ef0bd..8e0b0a463f 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/collection/4-sql_serverlogons.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/collection/4-sql_serverlogons.md @@ -15,7 +15,7 @@ The AppnLogSQL Query uses the SMARTLog Data Collector and has been preconfigured Windows Event Log Type. :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/collection/5-sql_serversettings.md b/docs/accessanalyzer/12.0/solutions/databases/sql/collection/5-sql_serversettings.md index 11d821fd13..6de3270d37 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/collection/5-sql_serversettings.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/collection/5-sql_serversettings.md @@ -35,19 +35,19 @@ The 5-SQL_ServerSettings Job uses the SQL Data Collector for the following queri ### Configure the Configuration Query The 5-SQL_ServerSettings Job’s Configuration Query is configured to run with the default settings -with the Configuration Properties category. Follow the steps to customize configurations. +with the Configuration Properties category. To customize configurations, complete the following steps. **Step 1 –** Navigate to the **Databases** > 0.Collection > SQL > 5-SQL_ServerSettings > Configure node and select Queries. -**Step 2 –** In the Query Selection view, select the Configuration Query and click on Query +**Step 2 –** In the Query Selection view, select the Configuration Query and click Query Properties. The Query Properties window will appear. **Step 3 –** Select the Data Source tab, and click Configure. The SQL Data Collector Wizard will open. :::warning -Do not make changes to other wizard pages as they have been pre-configured for the +Don't make changes to other wizard pages as they have been pre-configured for the purpose of this job. ::: @@ -60,7 +60,7 @@ by default to target All instances. Change the query scope to Only select instan Retrieve. The Available server audits will be populated. Databases and instances can be added in the following ways: -- Select the desired instances and click Add. +- Select the instances you want and click Add. - Use the Import CSV button to import a list from a CSV file. - (Optional) Use the Add Custom Filter button to create and apply a custom filter. @@ -73,20 +73,20 @@ The 5-SQL_ServerSettings Job is now ready to run with the customized settings. The 5-SQL_ServerSettingsJob > Server Query has been preconfigured to run with the default settings with the category of Server Properties. However, the query can be scoped to target specific -databases/instances on the Filters page of the SQL Data Collector Wizard. Follow these steps to -modify the query configuration. +databases/instances on the Filters page of the SQL Data Collector Wizard. To modify the query +configuration, complete the following steps. **Step 1 –** Navigate to the **Databases** > 0.Collection > SQL > 5-SQL_ServerSettings > Configure node and select Queries. -**Step 2 –** In the Query Selection view, select the Server query click on Query Properties. The +**Step 2 –** In the Query Selection view, select the Server query click Query Properties. The Query Properties window will appear. **Step 3 –** Select the Data Source tab, and click Configure. The SQL Data Collector Wizard will open. :::warning -Do not make changes to other wizard pages as they have been pre-configured for the +Don't make changes to other wizard pages as they have been pre-configured for the purpose of this job. ::: @@ -99,7 +99,7 @@ by default to target All instances. Change the query scope to Only select instan Retrieve. The Available server audits will be populated. Databases and instances can be added in the following ways: -- Select the desired instances and click Add. +- Select the instances you want and click Add. - Use the Import CSV button to import a list from a CSV file. - Optionally use the Add Custom Filter button to create and apply a custom filter. diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/overview.md b/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/overview.md index 4a59eacd54..3feda1d7d0 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/overview.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/overview.md @@ -15,18 +15,18 @@ The jobs in the 4.Configuration Job Group are: - [SQL_Authentication Job](/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/sql_authentication.md) – This job identifies authentication settings on targeted SQL and Azure SQL servers that allow SQL server authentication in addition to Windows - authentication. Microsoft recommends that the SQL and Azure SQL servers should be generally - configured to utilize Windows authentication versus SQL authentication. + authentication. Microsoft recommends configuring SQL and Azure SQL servers to use Windows + authentication instead of SQL authentication. - [SQL_BestPractices Job](/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/sql_bestpractices.md) – This job is designed to analyze SQL and Azure SQL server configuration settings and report on any findings that deviate from recommended Microsoft Best Practices when it comes to creating, maintaining, and securing SQL servers - [SQL_CMDShell Job](/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/sql_cmdshell.md) – This job is designed to report if the `xp_cmdshell `stored procedure is enabled or disabled. Since `xp_cmdshell` allows a user to execute operating system - commands when connected to the SQL or Azure SQL server, it can be used to launch malicious + commands when connected to the SQL or Azure SQL server, attackers can use it to launch malicious attacks. Microsoft recommends that the `xp_cmdshell` stored procedure be disabled. - [SQL_DatabaseSizing Job](/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/sql_databasesizing.md) – Provides details on database file sizes and overall database sizes - [SQL_LinkedServers Job](/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/sql_linkedservers.md) – Identifies Linked Servers or remote database servers on which the identified SQL and Azure SQL server can execute commands. Some of the common - remote OLE DB providers include IBM DB2, Oracle, Access and Excel. Typically, linked servers are + remote OLE DB providers include IBM DB2, Oracle, Access, and Excel. Typically, linked servers are used to handle distributed queries in SQL and Azure SQL server. diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/sql_authentication.md b/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/sql_authentication.md index 62d27f5dc7..3c25f174f0 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/sql_authentication.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/sql_authentication.md @@ -8,8 +8,8 @@ sidebar_position: 10 The SQL_Authentication Job identifies authentication settings on targeted SQL and Azure SQL servers that allow SQL server authentication in addition to Windows authentication. Microsoft recommends -that SQL and Azure SQL servers should be generally configured to utilize Windows authentication -versus SQL server authentication. +configuring SQL and Azure SQL servers to use Windows authentication instead of SQL server +authentication. ## Analysis Tasks for the SQL_Authentication Job @@ -17,7 +17,7 @@ Navigate to the **Databases** > SQL > 4.Configuration > SQL_Authentication > Con select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -36,4 +36,4 @@ produces the following pre-configured report. | Report | Description | Default Tags | Report Elements | | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| SQL  Authentication | This report identifies authentication settings on the targeted servers, and highlights those with SQL Authentication enabled. Additionally, the number of SQL logins on a given instance, and whether or not the 'sa' login exists, are indicated. Best practices recommend that SQL instances be integrated login only, and that the 'sa' principal be renamed or removed. | None | This report is comprised of two elements:
  • Pie Chart – Displays instances with integrated security only
  • Table – Displays integrated security details by instance
| +| SQL  Authentication | This report identifies authentication settings on the targeted servers, and highlights those with SQL Authentication enabled. It also indicates the number of SQL logins on a given instance and whether the 'sa' login exists. Best practices recommend using integrated login only for SQL instances and renaming or removing the 'sa' principal. | None | This report is comprised of two elements:
  • Pie Chart – Displays instances with integrated security only
  • Table – Displays integrated security details by instance
| diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/sql_bestpractices.md b/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/sql_bestpractices.md index b016d44de9..06fb1b2a4a 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/sql_bestpractices.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/sql_bestpractices.md @@ -16,7 +16,7 @@ Navigate to the **Databases** > SQL > 4.Configuration > SQL_BestPractices > Con select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/sql_cmdshell.md b/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/sql_cmdshell.md index 68762c3a7f..590a937092 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/sql_cmdshell.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/sql_cmdshell.md @@ -7,8 +7,8 @@ sidebar_position: 30 # SQL_CMDShell Job The SQL_CMDShell Job reports on whether the `xp_cmdshell` stored procedure is enabled or disabled. -Since `xp_cmdshell` allows users to execute operating system commands when connected to the SQL or -the Azure SQL server, it can be used to launch malicious attacks. Microsoft recommends that the +`xp_cmdshell` lets users execute operating system commands when connected to the SQL or +the Azure SQL server, which attackers can use to launch malicious attacks. Microsoft recommends that the `xp_cmdshell` stored procedure be disabled. ## Analysis Tasks for the SQL_CMDShell Job @@ -17,7 +17,7 @@ Navigate to the **Databases** > SQL > 4.Configuration > SQL_CMDShell > Configure Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/sql_databasesizing.md b/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/sql_databasesizing.md index 33e77d121c..bf43a08a50 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/sql_databasesizing.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/sql_databasesizing.md @@ -14,7 +14,7 @@ Navigate to the **Databases** > Jobs > SQL > 4.Configuration > SQL_DatabaseSizi node and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/sql_linkedservers.md b/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/sql_linkedservers.md index 434cc29664..fdc3e3f8e9 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/sql_linkedservers.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/configuration/sql_linkedservers.md @@ -8,7 +8,7 @@ sidebar_position: 50 The SQL_LinkedServers Job identifies Linked Servers or remote database servers on which the identified SQL and Azure SQL servers can execute commands. Some of the common remote -OLE DB providers include IBM DB2, Oracle, Access and Excel. Typically, linked servers are used to +OLE DB providers include IBM DB2, Oracle, Access, and Excel. Typically, linked servers are used to handle distributed queries in SQL and Azure SQL server . ## Analysis Tasks for the SQL_LinkedServers Job @@ -17,7 +17,7 @@ Navigate to the **Databases** > Jobs > SQL > 4.Configuration > SQL_LinkedServers and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are pre-configured for this job. ::: @@ -34,4 +34,4 @@ following preconfigured report: | Report | Description | Default Tags | Report Elements | | -------------- | ----------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Linked Servers | This report highlights Linked Servers where the listed SQL Server is able to execute remote commands. | None | This report is comprised of three elements:
  • Bar Chart – Provides information on top five linked servers by instance
  • Table – Provides details on linked servers by instance
  • Table – Provides details on linked servers
| +| Linked Servers | This report highlights Linked Servers where the listed SQL Server can execute remote commands. | None | This report is comprised of three elements:
  • Bar Chart – Provides information on top five linked servers by instance
  • Table – Provides details on linked servers by instance
  • Table – Provides details on linked servers
| diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/overview.md b/docs/accessanalyzer/12.0/solutions/databases/sql/overview.md index cc56a1f1ed..c7ba5bba47 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/overview.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/overview.md @@ -31,8 +31,8 @@ thread requires a minimum of 2 additional GB of RAM per host. For example, a job :::note The appropriate JDK (Java) version for Sensitive Data Discovery is installed on the -server. The JDK deployed is prepackaged and doesn't require any configuration; it has been -preconfigured to work with Access Analyzer and should never be customized through Java. It will not +server. The JDK deployed is prepackaged and doesn't require any configuration. Netwrix preconfigures +it to work with Access Analyzer, and you shouldn't customize it through Java. It will not conflict with other JDKs or Java Runtimes in the same environment. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/permissions/overview.md b/docs/accessanalyzer/12.0/solutions/databases/sql/permissions/overview.md index e01fa62183..4d707cf76c 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/permissions/overview.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/permissions/overview.md @@ -14,7 +14,7 @@ level across all targeted SQL and Azure SQL servers. The jobs in the 3.Permissions Job Group are: - [SQL_ControlServer Job](/docs/accessanalyzer/12.0/solutions/databases/sql/permissions/sql_controlserver.md) – This job will provide information on control - server permissions. Users with control server permissions allow users to command full control of a + server permissions. Users with control server permissions can command full control of a SQL and Azure SQL server instances - [SQL_DirectPermissions Job](/docs/accessanalyzer/12.0/solutions/databases/sql/permissions/sql_directpermissions.md) – This job will provide information about the permissions granted to users at the schema, database, and server levels diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/permissions/sql_controlserver.md b/docs/accessanalyzer/12.0/solutions/databases/sql/permissions/sql_controlserver.md index f764aba89f..69e8dd651b 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/permissions/sql_controlserver.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/permissions/sql_controlserver.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 3.Permissions > SQL_ControlServer > Confi Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/permissions/sql_directpermissions.md b/docs/accessanalyzer/12.0/solutions/databases/sql/permissions/sql_directpermissions.md index 45f49c09f7..136bd40f45 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/permissions/sql_directpermissions.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/permissions/sql_directpermissions.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 3.Permissions > SQL_DirectPermissions > Co select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/permissions/sql_domainuserpermissions.md b/docs/accessanalyzer/12.0/solutions/databases/sql/permissions/sql_domainuserpermissions.md index 21f177e387..276a543f5b 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/permissions/sql_domainuserpermissions.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/permissions/sql_domainuserpermissions.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 3.Permissions > SQL_DomainUserPermissions select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/permissions/sql_publicpermissions.md b/docs/accessanalyzer/12.0/solutions/databases/sql/permissions/sql_publicpermissions.md index 7867519f23..9d2c92aed3 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/permissions/sql_publicpermissions.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/permissions/sql_publicpermissions.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 5.Permissions > SQL_PublicPermissions > C select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -29,7 +29,7 @@ The default analysis tasks are: - Public Permissions Summary – Creates the SA_SQLServer_PublicPermissions_DatabaseSummary table accessible under the job’s Results node - Public Permissions Summary – Highlights permissions that have been granted to the public role on - objects that are not-default SQL or Azure SQL server objects + objects that aren't-default SQL or Azure SQL server objects - Public Permissions Instance Summary (Non-Default) – Summarizes non-default SQL and Azure SQL server public permissions by instance diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/permissions/sql_serverpermissions.md b/docs/accessanalyzer/12.0/solutions/databases/sql/permissions/sql_serverpermissions.md index 63941d4521..29b15e2675 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/permissions/sql_serverpermissions.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/permissions/sql_serverpermissions.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 3.Permissions > SQL_ServerPermissions > C select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/recommended.md b/docs/accessanalyzer/12.0/solutions/databases/sql/recommended.md index dd5433e622..7b5bcda339 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/recommended.md @@ -19,13 +19,13 @@ Group. After you assign these to the job group, you can run it directly or sched **Dependencies** - .Active Directory Inventory Job Group run successfully -- For Activity Auditing – SQL Server Audit Specifications to be configured on the target databases +- For Activity Auditing – SQL Server Audit Specifications configured on the target databases - Audit destination must be a binary file - See the Microsoft [Create a Server Audit and Database Audit Specification](https://docs.microsoft.com/en-us/sql/relational-databases/security/auditing/create-a-server-audit-and-database-audit-specification) article for additional information. -- For the SQL_SecurityAssessment Job – One or more of the following jobs or job groups must be run - to produce results: +- For the SQL_SecurityAssessment Job – To produce results, run one or more of the following jobs + or job groups: - [0.Collection > SQL Job Group](/docs/accessanalyzer/12.0/solutions/databases/sql/collection/overview.md) - [1.Users and Roles Job Group](/docs/accessanalyzer/12.0/solutions/databases/sql/usersroles/overview.md) - [3.Permissions Job Group](/docs/accessanalyzer/12.0/solutions/databases/sql/permissions/overview.md) @@ -62,9 +62,9 @@ topic for additional information. Assign the Connection Profile under the SQL > 0.Collection > Settings > Connection node. It is set to Use the Default Profile, as configured at the global settings level. However, since -this may not be the Connection Profile with the necessary permissions for the assigned hosts, click -the radio button for the Select one of the following user defined profiles option and select the -appropriate Connection Profile dropdown menu. +this may not be the Connection Profile with the necessary permissions for the assigned hosts, select +the Select one of the following user defined profiles option, then choose the appropriate profile +from the Connection Profile dropdown menu. See the [Connection](/docs/accessanalyzer/12.0/admin/settings/connection/overview.md) topic for additional information. @@ -72,7 +72,7 @@ information. **Schedule Frequency** Schedule the SQL Job Group to run based on the types of auditing and the scope of the target -environment. The general recommendation is to run the solution daily. +environment. Run the solution daily. **Run Order** @@ -93,8 +93,8 @@ Prerequisites: target SQL Server Databases. Audit destination for the configured server or database audit must be a binary file. - The 5-SQL_ServerSettings Job contains the Orphaned Users query which returns users that are - orphaned for each database. The query uses the sp_Change_users_login procedure which requires the - db_owner fixed database to be assigned to the Access Analyzer User. See the + orphaned for each database. The query uses the sp_Change_users_login procedure which requires assigning the + db_owner fixed database to the Access Analyzer User. See the [sp_change_users_login (Transact-SQL)](https://docs.microsoft.com/en-us/sql/relational-databases/system-stored-procedures/sp-change-users-login-transact-sql?view=sql-server-ver15) Microsoft article for additional information. diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/sensitivedata/sql_sensitivedata.md b/docs/accessanalyzer/12.0/solutions/databases/sql/sensitivedata/sql_sensitivedata.md index 32a8038815..92317d0fd5 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/sensitivedata/sql_sensitivedata.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/sensitivedata/sql_sensitivedata.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 5.Sensitve Data > SQL_SensitiveData > Con select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/sensitivedata/sql_sensitivedatapermissions.md b/docs/accessanalyzer/12.0/solutions/databases/sql/sensitivedata/sql_sensitivedatapermissions.md index a30e2c1bbb..785332edf6 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/sensitivedata/sql_sensitivedatapermissions.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/sensitivedata/sql_sensitivedatapermissions.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 5.Sensitve Data > SQL_SensitiveDataPermi node and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/sql_securityassessment.md b/docs/accessanalyzer/12.0/solutions/databases/sql/sql_securityassessment.md index 3b5a56a83b..b09429c754 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/sql_securityassessment.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/sql_securityassessment.md @@ -13,7 +13,7 @@ and NO FINDINGS categories based on severity. **Special Dependencies** -One or more of the following jobs or job groups must be run to produce results: +To produce results, run one or more of the following jobs or job groups: - [0.Collection > SQL Job Group](/docs/accessanalyzer/12.0/solutions/databases/sql/collection/overview.md) - [SQL_PasswordIssues Job](/docs/accessanalyzer/12.0/solutions/databases/sql/usersroles/sql_passwordissues.md) @@ -23,7 +23,7 @@ One or more of the following jobs or job groups must be run to produce results: - [Privileged Accounts Job Group](/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/overview.md) - [Privileged Accounts Job Group](/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/overview.md) -Only information collected from jobs/groups being run will produce findings. +Only information from jobs or job groups that ran produces findings. ### Analysis Task for the SQL_SecurityAssessment Job diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/usersroles/sql_databaseprinciples.md b/docs/accessanalyzer/12.0/solutions/databases/sql/usersroles/sql_databaseprinciples.md index ee5f11be55..dc4f295070 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/usersroles/sql_databaseprinciples.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/usersroles/sql_databaseprinciples.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 3.Users and Roles > SQL_DatabasePrinciple and select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/usersroles/sql_passwordissues.md b/docs/accessanalyzer/12.0/solutions/databases/sql/usersroles/sql_passwordissues.md index f0d2526e92..3ba48507ae 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/usersroles/sql_passwordissues.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/usersroles/sql_passwordissues.md @@ -15,7 +15,7 @@ weak passwords. The Collect Weak Passwords Job uses the PowerShell Data Collector for the following query: :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -32,7 +32,7 @@ Navigate to the Jobs > **Databases** > SQL > 3.Users and Roles > SQL_PasswordIs and select Analysis to view the analysis tasks. :::warning -Most of these analysis tasks are preconfigured and should not be modified and or +Most of these analysis tasks are preconfigured and shouldn't be modified and or deselected unless otherwise specified. ::: @@ -49,7 +49,7 @@ The default analysis tasks are: [Configure the Customizable Parameters in an Analysis Task](/docs/accessanalyzer/12.0/admin/jobs/job/configure/analysis/analysiscustomizableparameters.md) topic for additional information on modifying analysis parameters. - Shared Passwords – Highlights SQL Server Logins with shared password hashes -- No Password – Inserts users that do not have a password set into the details table +- No Password – Inserts users that don't have a password set into the details table - Summarize the Weak Password Results – Summarizes the data that has been collected by the weak passwords job diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/usersroles/sql_rolemembers.md b/docs/accessanalyzer/12.0/solutions/databases/sql/usersroles/sql_rolemembers.md index edd02763c2..5b8c63a015 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/usersroles/sql_rolemembers.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/usersroles/sql_rolemembers.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 3.Users and Roles > SQL_RoleMembers > Conf select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/usersroles/sql_serverprincipals.md b/docs/accessanalyzer/12.0/solutions/databases/sql/usersroles/sql_serverprincipals.md index 16ae55744f..7f2ead1e61 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/usersroles/sql_serverprincipals.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/usersroles/sql_serverprincipals.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 3.Users and Roles > SQL_ServerPrincipals select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/usersroles/sql_sqllogins.md b/docs/accessanalyzer/12.0/solutions/databases/sql/usersroles/sql_sqllogins.md index 10392eba35..a23206cf80 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/usersroles/sql_sqllogins.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/usersroles/sql_sqllogins.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 3.Users and Roles > SQL_SQLLogins > Config Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/sql/usersroles/sql_sysadmins.md b/docs/accessanalyzer/12.0/solutions/databases/sql/usersroles/sql_sysadmins.md index 4ea55eed3c..c74a1864ea 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/sql/usersroles/sql_sysadmins.md +++ b/docs/accessanalyzer/12.0/solutions/databases/sql/usersroles/sql_sysadmins.md @@ -15,7 +15,7 @@ Navigate to the **Databases** > SQL > 3.Users and Roles > SQL_SysAdmins > Config Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task(s). The analysis task(s) are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/databases/update-schema.md b/docs/accessanalyzer/12.0/solutions/databases/update-schema.md index 556b073957..b86c5a29fc 100644 --- a/docs/accessanalyzer/12.0/solutions/databases/update-schema.md +++ b/docs/accessanalyzer/12.0/solutions/databases/update-schema.md @@ -45,6 +45,6 @@ The shared patches applied by this job create the following objects in the stora | `SA_DatabaseUsageMode` | Table | Lookup table for database usage modes (Oracle Service, Oracle SID, Redshift, Azure Managed Instance, Azure Stand Alone, etc.) | | `SA_SQL_GetFriendlyName` | Function | Converts a host name, instance name, and port number from the `SA_SQL_Instances` table into a single display name | -In addition to the shared patches above, each supported database platform (SQL Server, Oracle, +In addition to the shared patches listed in the previous table, each supported database platform (SQL Server, Oracle, MySQL, PostgreSQL, Db2 LUW, Azure SQL) registers its own set of vendor-specific schema patches that are also applied by this job. diff --git a/docs/accessanalyzer/12.0/solutions/dropbox/collection/1-dropbox_permissions_scan.md b/docs/accessanalyzer/12.0/solutions/dropbox/collection/1-dropbox_permissions_scan.md index a26740d7fe..edb6052b02 100644 --- a/docs/accessanalyzer/12.0/solutions/dropbox/collection/1-dropbox_permissions_scan.md +++ b/docs/accessanalyzer/12.0/solutions/dropbox/collection/1-dropbox_permissions_scan.md @@ -10,7 +10,7 @@ The 1-Dropbox_Permissions Scan job collects data from the Dropbox environment on sharing policies, configurations, and content. :::warning -This job should not be run if running sensitive data scans against the Dropbox Business +This job shouldn't be run if running sensitive data scans against the Dropbox Business environment. ::: @@ -28,8 +28,8 @@ The query for the 1-Dropbox_Permissions Scan job is: ### Configure the Dropbox Access Query -Follow the steps to either generate the access token needed for the Connection Profile (only done -prior to first execution) or to set any desired customizations. +To either generate the access token needed for the Connection Profile (only done +before first execution) or to set any desired customizations, complete the following steps. **Step 1 –** Navigate to the **Jobs** > **Dropbox** > **0.Collection** > **1-Dropbox_Permissions Scan** > **Configure** node and select **Queries**. @@ -42,13 +42,13 @@ Data Collector Wizard opens. ![Dropbox Access Auditor Data Collector Wizard Scan Options page](/images/accessanalyzer/12.0/solutions/dropbox/collection/permissionsscanoptionspage.webp) -**Step 4 –** T Use the Scan Options page ito generate the access token prior to the first execution +**Step 4 –** T Use the Scan Options page ito generate the access token before the first execution of the job group. - Remember to copy the access token, either from the textbox or using the **Copy to Clipboard** - button, and use it in the Connection Profile assigned to the Dropbox Solution. Once the access - token has been generated and copied, if no customizations are to be made, click **Cancel** to - close the Dropbox Access Auditor Data Collector wizard. + button, and use it in the Connection Profile assigned to the Dropbox Solution. After you generate + and copy the access token, click **Cancel** to close the Dropbox Access Auditor Data Collector + wizard if you don't need to make any customizations. - See the [DropboxAccess: Scan Options](/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/scanoptions.md) topic for full instructions on generating the access token @@ -64,4 +64,4 @@ collect permissions at the file level. When finished with this page, click **Nex **Step 7 –** On the Summary page, click **Finish** to save any setting modifications or click **Cancel** if no changes were made. Then click **OK** to close the Query Properties window. -If changes were made, the 1-Dropbox_Permissions Scan job has now been customized. +If you made changes, you've now customized the 1-Dropbox_Permissions Scan job. diff --git a/docs/accessanalyzer/12.0/solutions/dropbox/collection/1-dropbox_sdd_scan.md b/docs/accessanalyzer/12.0/solutions/dropbox/collection/1-dropbox_sdd_scan.md index d0c8da422a..737b46d6da 100644 --- a/docs/accessanalyzer/12.0/solutions/dropbox/collection/1-dropbox_sdd_scan.md +++ b/docs/accessanalyzer/12.0/solutions/dropbox/collection/1-dropbox_sdd_scan.md @@ -7,7 +7,7 @@ sidebar_position: 20 # 1-Dropbox_SDD Scan Job The 1-Dropbox_SDD Scan job collects data from the Dropbox environment on access rights, sharing -policies, configurations, content and sensitive data. +policies, configurations, content, and sensitive data. ## Queries for the 1-Dropbox_SDD Scan Job @@ -22,8 +22,8 @@ The query for the 1-Dropbox_SDD Scan job is: ### Configure the Sensitive Data Scan Query -Follow the steps to either generate the access token needed for the Connection Profile (only done -prior to first execution) or to set any desired customizations. +To either generate the access token needed for the Connection Profile (only done +before first execution) or to set any desired customizations, complete the following steps. **Step 1 –** Navigate to the **Jobs** > **Dropbox** > **0.Collection** > **1-Dropbox_SDD Scan** > **Configure** node and select **Queries**. @@ -71,4 +71,4 @@ topic for additional information. **Step 7 –** On the Completion Page, click **Finish** to save any setting modifications or click **Cancel** if no changes were made. Then click **OK** to close the Query Properties window. -If changes were made, the 1-Dropbox_SDD Scan job has now been customized. +If you made changes, you've now customized the 1-Dropbox_SDD Scan job. diff --git a/docs/accessanalyzer/12.0/solutions/dropbox/collection/2-dropbox_permissions_bulk_import.md b/docs/accessanalyzer/12.0/solutions/dropbox/collection/2-dropbox_permissions_bulk_import.md index 1c6e00f127..300215f7a8 100644 --- a/docs/accessanalyzer/12.0/solutions/dropbox/collection/2-dropbox_permissions_bulk_import.md +++ b/docs/accessanalyzer/12.0/solutions/dropbox/collection/2-dropbox_permissions_bulk_import.md @@ -10,7 +10,7 @@ The 2-Dropbox_Permissions Bulk Import job imports the data collected by the 1-Dr Scan job to the Access Analyzer database for use by the analysis tasks. :::warning -This job should not be run if running sensitive data scans against the Dropbox Business +This job shouldn't be run if running sensitive data scans against the Dropbox Business environment. ::: @@ -27,6 +27,6 @@ The query for the 2-Dropbox_Permissions Bulk Import job is: - Dropbox Bulk Import – Imports data collected by the 1-Dropbox_Permissions Scan job to the Access Analyzer database -There are no customization options available for this job. The Summary page of the Dropbox Access -Auditor Data Collector wizard can be viewed at the **Jobs** > **Dropbox** > **0.Collection** > +There are no customization options available for this job. View the Summary page of the Dropbox +Access Auditor Data Collector wizard at the **Jobs** > **Dropbox** > **0.Collection** > **2-Dropbox_Permissions Bulk Import** > **Configure** > **Queries** node. diff --git a/docs/accessanalyzer/12.0/solutions/dropbox/collection/2-dropbox_sdd_bulk_import.md b/docs/accessanalyzer/12.0/solutions/dropbox/collection/2-dropbox_sdd_bulk_import.md index 2536018f38..de9438a3e5 100644 --- a/docs/accessanalyzer/12.0/solutions/dropbox/collection/2-dropbox_sdd_bulk_import.md +++ b/docs/accessanalyzer/12.0/solutions/dropbox/collection/2-dropbox_sdd_bulk_import.md @@ -21,6 +21,6 @@ The query for the 2-Dropbox_SDD Bulk Import job is: - DropboxSDD Bulk Import – Imports data collected by the Dropbox 1-SDD Scan Job into the Access Analyzer database -There are no customization options available for this job. The Summary page of the Dropbox Access -Auditor Data Collector wizard can be viewed at the **Jobs** > **Dropbox** > **0.Collection** > +There are no customization options available for this job. View the Summary page of the Dropbox +Access Auditor Data Collector wizard at the **Jobs** > **Dropbox** > **0.Collection** > **2-Dropbox_SDD Bulk Import** > **Configure** > **Queries** node. diff --git a/docs/accessanalyzer/12.0/solutions/dropbox/collection/overview.md b/docs/accessanalyzer/12.0/solutions/dropbox/collection/overview.md index 7be92240b8..a60e09886e 100644 --- a/docs/accessanalyzer/12.0/solutions/dropbox/collection/overview.md +++ b/docs/accessanalyzer/12.0/solutions/dropbox/collection/overview.md @@ -18,29 +18,29 @@ The 0.Collection job group is comprised of: scanning the target Dropbox site - [1-Dropbox_SDD Scan Job](/docs/accessanalyzer/12.0/solutions/dropbox/collection/1-dropbox_sdd_scan.md) – This job is responsible for scanning sensitive data in the target Dropbox site. The Sensitive Data Discovery Add-On is required to run this job. - The Dropbox sensitive data Discovery Reports in the Access Information Center are also populated - by this data. See the Resource Audits Overview topic in the + This data also populates the Dropbox sensitive data Discovery Reports in the Access Information + Center. See the Resource Audits Overview topic in the [Netwrix Access Information Center Documentation](https://helpcenter.netwrix.com/category/accessinformationcenter) for additional information. - [2-Dropbox_Permissions Bulk Import Job](/docs/accessanalyzer/12.0/solutions/dropbox/collection/2-dropbox_permissions_bulk_import.md) – This job is responsible for importing the collected data into the Access Analyzer database - [2-Dropbox_SDD Bulk Import Job](/docs/accessanalyzer/12.0/solutions/dropbox/collection/2-dropbox_sdd_bulk_import.md) – This job is responsible for importing the collected sensitive data into the Access Analyzer database. The Sensitive Data - Discovery Add-On is required to run this job. The Dropbox sensitive data Discovery Reports in the - Access Information Center are also populated by this data. See the Resource Audits Overview topic + Discovery Add-On is required to run this job. This data also populates the Dropbox sensitive data + Discovery Reports in the Access Information Center. See the Resource Audits Overview topic in the [Netwrix Access Information Center Documentation](https://helpcenter.netwrix.com/category/accessinformationcenter) for additional information. The relationship between the scan and bulk import jobs requires the following considerations: -- A scan job executed from an Access Analyzer Console must be followed by the corresponding bulk - import job from the same Access Analyzer Console version -- Two scan jobs processing the same information, for example two 1-Dropbox_Permissions Scan jobs, - cannot be executed consecutively against the same target host. The corresponding bulk import job, - for example 2-Dropbox_Permissions Bulk Import job, must be executed in between. -- For the Dropbox Solution, the bulk import jobs require the same connection profile as used in the - corresponding scan jobs +- You must run the corresponding bulk import job, from the same Access Analyzer Console version, + immediately after a scan job executed from an Access Analyzer Console +- You can't execute two scan jobs that process the same information, for example two + 1-Dropbox_Permissions Scan jobs, consecutively against the same target host. You must execute the + corresponding bulk import job, for example the 2-Dropbox_Permissions Bulk Import job, in between. +- For the Dropbox Solution, the bulk import jobs require the same connection profile that the + corresponding scan jobs use :::info When running the sensitive data jobs, disable the permissions jobs, and vice @@ -49,8 +49,8 @@ versa. :::tip -Remember, prior to running the Dropbox Solution for the first time, it is necessary to generate an -access token to be used in the Connection Profile. This only needs to be done once. See the +Remember, before running the Dropbox Solution for the first time, generate an +access token to use in the Connection Profile. You only need to do this once. See the [Configure the Dropbox Access Query](1-dropbox_permissions_scan.md#configure-the-dropbox-access-query) topic for additional information. ::: diff --git a/docs/accessanalyzer/12.0/solutions/dropbox/dropbox_access.md b/docs/accessanalyzer/12.0/solutions/dropbox/dropbox_access.md index d6a885116e..11cb9716ca 100644 --- a/docs/accessanalyzer/12.0/solutions/dropbox/dropbox_access.md +++ b/docs/accessanalyzer/12.0/solutions/dropbox/dropbox_access.md @@ -21,7 +21,7 @@ View the analysis tasks by navigating to the **Jobs** > **Dropbox** > **1.Access pbox_Access** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/dropbox/dropbox_content.md b/docs/accessanalyzer/12.0/solutions/dropbox/dropbox_content.md index fb94ade45e..178918c287 100644 --- a/docs/accessanalyzer/12.0/solutions/dropbox/dropbox_content.md +++ b/docs/accessanalyzer/12.0/solutions/dropbox/dropbox_content.md @@ -16,8 +16,8 @@ The Dropbox_Content job is located in the 4.Content job group. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable -parameters used by analysis tasks in the job. See the +Use the Configuration section on a Job's overview page to modify any customizable parameters used +by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/12.0/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -26,7 +26,7 @@ The Dropbox_Content job has the following customizable parameter: - Days since File Modification before a file is considered stale See the -[Customizable Analysis Tasks for the Dropbox_Content Job](#customizable-analysis-tasks-for-the-dropbox_content-job) +[Customizable Analysis Tasks for the Dropbox_Content Job](#customizable-analysis-tasks-for-the-dropboxcontent-job) topic for additional information. ## Analysis Tasks for the Dropbox_Content Job @@ -35,7 +35,7 @@ View the analysis tasks by navigating to the **Jobs** > **Dropbox** > **4.Conten **Dropbox_Content** > **Configure** node and select **Analysis**. :::warning -Most of the analysis tasks should not be modified or deselected. The analysis tasks are +Most of the analysis tasks shouldn't be modified or deselected. The analysis tasks are preconfigured for this job. ::: @@ -48,7 +48,7 @@ preconfigured for this job. - By default, a stale file has not been modified in the past 365 days. You can modify this analysis task to edit this number of days. See the - [Customizable Analysis Tasks for the Dropbox_Content Job](#customizable-analysis-tasks-for-the-dropbox_content-job) + [Customizable Analysis Tasks for the Dropbox_Content Job](#customizable-analysis-tasks-for-the-dropboxcontent-job) topic for additional information. - Creates an interim processing table in the database for use by downstream analysis and report generation @@ -66,8 +66,8 @@ Dropbox_Content job produces the following pre-configured reports. ### Customizable Analysis Tasks for the Dropbox_Content Job The time frame used to define stale content is set by default to 365 days. This can be modified -within the **Determines stale data by owner** analysis task. The customizable parameter feature -enables you to easily set this value. +within the **Determines stale data by owner** analysis task. Use the customizable parameter feature +to set this value. | Customizable Parameter Name | Default Value | Value Indicates | | --------------------------- | ------------- | --------------------------------------------------------------------------------------------- | diff --git a/docs/accessanalyzer/12.0/solutions/dropbox/dropbox_groupmembership.md b/docs/accessanalyzer/12.0/solutions/dropbox/dropbox_groupmembership.md index a0127d6b2a..56921c3897 100644 --- a/docs/accessanalyzer/12.0/solutions/dropbox/dropbox_groupmembership.md +++ b/docs/accessanalyzer/12.0/solutions/dropbox/dropbox_groupmembership.md @@ -20,7 +20,7 @@ View the analysis tasks by navigating to the **Jobs** > **Dropbox** > **3.Group **Dropbox_GroupMembership** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/dropbox/dropbox_sensitivedata.md b/docs/accessanalyzer/12.0/solutions/dropbox/dropbox_sensitivedata.md index d6fe1a48c5..8a20273792 100644 --- a/docs/accessanalyzer/12.0/solutions/dropbox/dropbox_sensitivedata.md +++ b/docs/accessanalyzer/12.0/solutions/dropbox/dropbox_sensitivedata.md @@ -22,7 +22,7 @@ View the analysis tasks by navigating to the **Jobs** > **Dropbox** > **5.Sensit **Dropbox_SensitiveData** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -46,5 +46,5 @@ the Dropbox_SensitiveData job produces the following pre-configured reports. | Report | Description | Default Tags | Report Elements | | -------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Enterprise Summary | This report identifies the type and amount of sensitive content found on Dropbox. | None | This report is comprised of two elements:
  • Pie Chart – Displays criteria summary by match count
  • Table – Provides criteria summary by match count
| -| Folder Details | This report identifies the location of sensitive data, and flags whether or not this data is accessible through open access. | None | This report is comprised of three elements:
  • Bar Chart – Displays top sensitive folders by file count
  • Table – Provides top sensitive folders by file count
  • Table – Provides top sensitive folder details by match count
| +| Folder Details | This report identifies the location of sensitive data, and flags whether this data is accessible through open access. | None | This report is comprised of three elements:
  • Bar Chart – Displays top sensitive folders by file count
  • Table – Provides top sensitive folders by file count
  • Table – Provides top sensitive folder details by match count
| | Sensitive Data Permissions | This report identifies the sensitive data locations and associated permissions. | None | This report is comprised of three elements:
  • Bar Chart – Displays sensitive data permission summary by file count
  • Table – Provides sensitive data permission summary by file count
  • Table – Provides sensitive data permissions by match count
| diff --git a/docs/accessanalyzer/12.0/solutions/dropbox/dropbox_sharing.md b/docs/accessanalyzer/12.0/solutions/dropbox/dropbox_sharing.md index 9671440993..7e842f40c6 100644 --- a/docs/accessanalyzer/12.0/solutions/dropbox/dropbox_sharing.md +++ b/docs/accessanalyzer/12.0/solutions/dropbox/dropbox_sharing.md @@ -9,9 +9,9 @@ sidebar_position: 40 The Dropbox_Sharing job provides insight into the sharing of resources within the targeted Dropbox environment. It is dependent on data collected by the 0.Collection job group. This job processes analysis tasks and generates a report on which resources are being shared and under which policy the -sharing occurs. Best practices often dictate that these resources should be carefully monitored due -to the amount of access to the data. If these resources contain privileged data, the access should -be reevaluated or the sensitive resources relocated. +sharing occurs. Best practices recommend closely monitoring these resources due +to the amount of access to the data. If these resources contain privileged data, reevaluate the +access or relocate the sensitive resources. ![2.Sharing > Dropbox_Sharing Job in the Jobs Tree](/images/accessanalyzer/12.0/solutions/dropbox/sharingjobstree.webp) @@ -23,7 +23,7 @@ View the analysis tasks by navigating to the **Jobs** > **Dropbox** > **2.Sharin **Dropbox_Sharing** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/dropbox/overview.md b/docs/accessanalyzer/12.0/solutions/dropbox/overview.md index 9286ca99a7..5327b0a37e 100644 --- a/docs/accessanalyzer/12.0/solutions/dropbox/overview.md +++ b/docs/accessanalyzer/12.0/solutions/dropbox/overview.md @@ -35,13 +35,13 @@ topic for additional information. **Sensitive Data Discovery Considerations** -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the minimum amount -of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For example, if the job -is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are required (8x2=16). +If you run Sensitive Data Discovery (SDD) scans, increase the minimum amount of RAM. Each thread +requires a minimum of 2 additional GB of RAM per host. For example, if the job is configured to +scan 8 hosts at a time, the job requires an extra 16 GB of RAM (8x2=16). :::note The appropriate JDK (Java) version for Sensitive Data Discovery is installed on the -server. The JDK deployed is prepackaged and does not require any configuration; it has been +server. The JDK deployed is prepackaged and doesn't require any configuration; it has been preconfigured to work with Access Analyzer and should never be customized through Java. It will not conflict with other JDKs or Java Runtimes in the same environment. ::: @@ -49,9 +49,8 @@ conflict with other JDKs or Java Runtimes in the same environment. **Location** -The Dropbox Solution requires a special Access Analyzer license. It can be installed from the -Instant Job Wizard. Once it has been installed into the Jobs tree, navigate to the solution: -**Jobs** > **Dropbox**. +The Dropbox Solution requires a special Access Analyzer license. Install it from the Instant Job +Wizard. After you install it into the Jobs tree, navigate to the solution: **Jobs** > **Dropbox**. The 0.Collection job group collects the data. The other job groups run analyses on the collected data and generate reports. @@ -59,8 +58,7 @@ data and generate reports. ## Job Groups The Dropbox Solution offers an overview of an organization’s Dropbox environment by scanning the -targeted Dropbox site. It is comprised of jobs which collect, analyze, and report on data. The data -collection is conducted by the DropboxAccess Data Collector. See the +targeted Dropbox site. It is comprised of jobs which collect, analyze, and report on data. The DropboxAccess Data Collector collects the data. See the [Standard Reference Tables & Views for the DropboxAccess Data Collector](/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/standardtables.md) topic for database table information. diff --git a/docs/accessanalyzer/12.0/solutions/dropbox/recommended.md b/docs/accessanalyzer/12.0/solutions/dropbox/recommended.md index d7320121cc..3d016a4075 100644 --- a/docs/accessanalyzer/12.0/solutions/dropbox/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/dropbox/recommended.md @@ -6,24 +6,25 @@ sidebar_position: 10 # Recommended Configurations for the Dropbox Solution -The Dropbox Solution requires the host list to be assigned and the Connection Profile configured -before job execution. Once these are assigned to the job group, it can be run directly or scheduled. +The Dropbox Solution requires you to assign the host list and configure the Connection Profile +before job execution. After you assign these to the job group, you can run it directly or schedule +it. **Targeted Hosts** The Dropbox solution has been configured to inherit the host list assignment from the collection job group level. -The host list assignment should be assigned under the **Dropbox** > **0.Collection** > -**Settings** > **Host List Assignment** node. Select the **Local host** option. +Assign the host list under the **Dropbox** > **0.Collection** > **Settings** > **Host List +Assignment** node. Select the **Local host** option. **Connection Profile** The DropboxAccess Data Collector requires a specific set of permissions to generate an access token which is used to configure the Connection Profile for Dropbox. The access token is generated in the Dropbox Access Auditor Data Collector Wizard on the Scan Options page (accessed through the -**1-Dropbox_Permissions Scan** job’s **Queries** node). The access token only needs to be generated -once, prior to running the job group for the first time. Then it is used as the credential in the +**1-Dropbox_Permissions Scan** job’s **Queries** node). You only need to generate the access token +once, before running the job group for the first time. Then it is used as the credential in the Connection Profile. See the [DropboxAccess: Scan Options](/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/scanoptions.md) topic for additional information. @@ -33,21 +34,21 @@ group level. The Connection Profile should be assigned under the **Dropbox** > * **Settings** > **Connection** node. It is set to **Use the Default Profile**, as configured at the global settings level. However, since this may not be the Connection Profile with the necessary permissions for Dropbox, select the **Select one of the following user defined profiles** option and -select the appropriate Connection Profile from the drop-down menu. See the +select the appropriate Connection Profile from the dropdown menu. See the [Custom Dropbox Connection Profile & Host List](/docs/accessanalyzer/12.0/admin/datacollector/dropboxaccess/configurejob.md) topic for additional information on configuring the Dropbox credential. The Dropbox bulk import jobs -requires the same connection profile as used in the corresponding Dropbox scan jobs +require the same connection profile that the corresponding Dropbox scan jobs use. See the [Connection](/docs/accessanalyzer/12.0/admin/settings/connection/overview.md) topic for additional information on creating Connection Profiles. **Schedule Frequency** -The Dropbox solution can be scheduled to run as desired. +Schedule the Dropbox solution to run as desired. **History Retention** -Not supported and should be turned off. +History retention isn't supported for the Dropbox Solution. Turn it off. **Multi Console Support** @@ -55,7 +56,7 @@ Not supported. **Run Order** -The 0.Collection jobs must be run first and in order. Run the **1-Dropbox_Permissions Scan** job and +Run the 0.Collection jobs first and in order. Run the **1-Dropbox_Permissions Scan** job and then the **2-Dropbox_Permissions Bulk Import** job. For the sensitive data jobs, run the **1-Dropbox_SDD Scan** job and then the **2-Dropbox_SDD Bulk Import** job. @@ -65,7 +66,7 @@ versa. ::: -After running the 0.Collection jobs, the other Dropbox solution job groups can be run in any order. +After running the 0.Collection jobs, you can run the other Dropbox solution job groups in any order. Best practice is to run at the solution level. **Query Configuration** @@ -80,12 +81,12 @@ information. This solution should be run with the default analysis configuration. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this solution. ::: -Though the analysis tasks should not be deselected the time frame used to define staleness can be +Though the analysis tasks shouldn't be deselected the time frame used to define staleness can be modified: - Stale content set to default of 365 days @@ -98,7 +99,7 @@ modified: The jobs contained in the solution use custom SQL scripts to render views on collected data. SQL views are used to populate report element tables and graphs. Changing or modifying the group, job, -or table names will result in no data displayed within the Access Information Center. +or table names causes the Access Information Center to display no data. **Workflow** @@ -110,11 +111,11 @@ Scan** job). **Step 2 –** Run the **2-Dropbox_Permissions Bulk Import** job (for sensitive data, run the **2-Dropbox_SDD Bulk Import** job). -**Step 3 –** Run the desired corresponding analysis and reporting sub-job groups. +**Step 3 –** Run the corresponding analysis and reporting sub-job groups you want. :::tip -Remember, prior to running the Dropbox solution for the first time, it is necessary to generate an -access token to be used in the Connection Profile. This only needs to be done once. See the +Remember, before running the Dropbox solution for the first time, generate an +access token to use in the Connection Profile. You only need to do this once. See the [Configure the Dropbox Access Query](collection/1-dropbox_permissions_scan.md#configure-the-dropbox-access-query) topic for additional information. ::: diff --git a/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_circularnesting.md b/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_circularnesting.md index 092369a474..a8f42c6ab3 100644 --- a/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_circularnesting.md +++ b/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_circularnesting.md @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **Entra ID** > **1.Groups** > **AAD_CircularNesting** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_duplicategroups.md b/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_duplicategroups.md index 1c138602ef..401464bd9f 100644 --- a/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_duplicategroups.md +++ b/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_duplicategroups.md @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **Entra ID** > **1.Groups** > **AAD_DuplicateGroups** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_emptygroups.md b/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_emptygroups.md index 268871e27f..e82be477bf 100644 --- a/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_emptygroups.md +++ b/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_emptygroups.md @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **Entra ID** > **1.Groups** > **AAD_EmptyGroups** > * and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_groupdirsync.md b/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_groupdirsync.md index 9d6da1dc9b..ee4ca26af8 100644 --- a/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_groupdirsync.md +++ b/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_groupdirsync.md @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **Entra ID** > **1.Groups** > **AAD_GroupDirSync** > and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_largestgroups.md b/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_largestgroups.md index be816e8322..215618da3d 100644 --- a/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_largestgroups.md +++ b/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_largestgroups.md @@ -6,9 +6,9 @@ sidebar_position: 50 # AAD_LargestGroups Job -The AAD_LargestGroups Job identifies groups with large effective member counts. These groups may -cause administrative overhead and burden in being able to easily understand who is getting access to -resources, or how much access is being granted to resources through these groups. +The AAD_LargestGroups Job identifies groups with large effective member counts. These groups can +create administrative overhead, making it hard to see who has access to resources and how much +access these groups grant. ## Analysis Tasks for the AAD_LargestGroups Job @@ -16,7 +16,7 @@ Navigate to the **Jobs** > **Entra ID** > **1.Groups** > **AAD_LargestGroups** > and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_nestedgroups.md b/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_nestedgroups.md index f2bc2567eb..6f62a70f0a 100644 --- a/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_nestedgroups.md +++ b/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_nestedgroups.md @@ -7,9 +7,9 @@ sidebar_position: 60 # AAD_NestedGroups Job The AAD_NestedGroups Job identifies nested groups within Microsoft Entra ID and provides details -such as the levels of nesting. While Microsoft Entra ID provides the ability to nest certain types -of groups within other groups, Microsoft recommends nesting does not go beyond two levels in order -to avoid difficulties in understanding effective membership and access. +such as the levels of nesting. While Microsoft Entra ID lets you nest certain types +of groups within other groups, Microsoft recommends nesting doesn't go beyond two levels to avoid +difficulties in understanding effective membership and access. ## Analysis Tasks for the AAD_NestedGroups Job @@ -17,7 +17,7 @@ Navigate to the **Jobs** > **Entra ID** > **1.Groups** > **AAD_NestedGroups** > and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_probableowners.md b/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_probableowners.md index 5aff291057..9c39393cac 100644 --- a/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_probableowners.md +++ b/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_probableowners.md @@ -6,9 +6,9 @@ sidebar_position: 70 # AAD_ProbableOwners Job -The AAD_ProbableOwners Job determines potential owners for Microsoft Entra ID Groups which can be -used to perform automated membership reviews and enable self-service group management and membership -requests. +The AAD_ProbableOwners Job determines potential owners for Microsoft Entra ID groups. Use these +results to perform automated membership reviews and enable self-service group management and +membership requests. ## Analysis Tasks for the AAD_ProbableOwners Job @@ -16,7 +16,7 @@ Navigate to the **Jobs** > **Entra ID** > **1.Groups** > **AAD_ProbableOwners** and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_stalegroups.md b/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_stalegroups.md index 5d5c862d55..f8477859d2 100644 --- a/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_stalegroups.md +++ b/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_stalegroups.md @@ -17,7 +17,7 @@ Navigate to the **Jobs** > **Entra ID** > **1.Groups** > **AAD_StaleGroups** > * and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -38,4 +38,4 @@ following pre-configured report. | Report | Description | Default Tags | Report Elements | | ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Stale Effective Membership (Stale Groups) | This report identifies groups with stale effective membership. A stale user is defined as someone who has not logged into the domain in over 30 days or is currently disabled. | None | This report is comprised of three elements:
  • Chart – Displays group membership
  • Table – Provides group membership details
  • Tables – Provides stale groups organization summary
| +| Stale Effective Membership (Stale Groups) | This report identifies groups with stale effective membership. A stale user is defined as someone who has not logged into the domain in over 30 days or is disabled. | None | This report is comprised of three elements:
  • Chart – Displays group membership
  • Table – Provides group membership details
  • Tables – Provides stale groups organization summary
| diff --git a/docs/accessanalyzer/12.0/solutions/entraid/groups/overview.md b/docs/accessanalyzer/12.0/solutions/entraid/groups/overview.md index 266cb0938d..ccbb137453 100644 --- a/docs/accessanalyzer/12.0/solutions/entraid/groups/overview.md +++ b/docs/accessanalyzer/12.0/solutions/entraid/groups/overview.md @@ -24,15 +24,14 @@ The jobs in the 1.Groups Job Group are: - [AAD_GroupDirSync Job](/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_groupdirsync.md) – Summarizes on-premises Active Directory syncing in the audited Microsoft Entra ID environment - [AAD_LargestGroups Job](/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_largestgroups.md) – Identifies groups with large effective member - counts. These types of groups may cause administrative overhead and burden in being able to easily - understand who is getting access to resources, or how much access is being granted to resources - through these groups. + counts. These types of groups can create administrative overhead, making it hard to see who has + access to resources and how much access these groups grant. - [AAD_NestedGroups Job](/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_nestedgroups.md) – Identifies nested groups within Microsoft Entra ID - and provides details such as the levels of nesting. While Microsoft Entra ID provides the ability - to nest certain types of groups within other groups, Microsoft recommends nesting does not go - beyond two levels in order to avoid difficulties in understanding effective membership and access. + and provides details such as the levels of nesting. While Microsoft Entra ID lets you nest + certain types of groups within other groups, Microsoft recommends nesting doesn't go + beyond two levels to avoid difficulties in understanding effective membership and access. - [AAD_ProbableOwners Job](/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_probableowners.md) – Determines potential owners for Microsoft Entra - ID Groups which can be used to perform automated membership reviews and enable self-service group + ID groups. Use these results to perform automated membership reviews and enable self-service group management and membership requests - [AAD_StaleGroups Job](/docs/accessanalyzer/12.0/solutions/entraid/groups/aad_stalegroups.md)– Identifies Microsoft Entra ID groups that contain potentially stale users. Users are considered stale if they have never logged onto the domain, diff --git a/docs/accessanalyzer/12.0/solutions/entraid/overview.md b/docs/accessanalyzer/12.0/solutions/entraid/overview.md index 53367cebff..9147aba68b 100644 --- a/docs/accessanalyzer/12.0/solutions/entraid/overview.md +++ b/docs/accessanalyzer/12.0/solutions/entraid/overview.md @@ -24,7 +24,7 @@ for additional information. The Entra ID Solution requires a special Access Analyzer license. It can be installed from the Instant Job Wizard, see the [Instant Job Wizard](/docs/accessanalyzer/12.0/admin/jobs/instantjobs/overview.md) topic for -additional information. Once it has been installed into the Jobs tree, navigate to the solution: +additional information. After it's installed into the Jobs tree, navigate to the solution: **Jobs** > **Entra ID**. The .Entra ID Inventory Job Group collects the data. The Entra ID Job Groups run analysis and diff --git a/docs/accessanalyzer/12.0/solutions/entraid/recommended.md b/docs/accessanalyzer/12.0/solutions/entraid/recommended.md index 3c022bc153..35782db046 100644 --- a/docs/accessanalyzer/12.0/solutions/entraid/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/entraid/recommended.md @@ -21,15 +21,15 @@ information. **Targeted Hosts** -The Entra ID Solution does not require a target host because the jobs use data collected from the +The Entra ID Solution doesn't require a target host because the jobs use data collected from the .Entra ID Inventory Job Group and the .Active Directory Inventory Job Group. However, Access -Analyzer jobs do not execute successfully without a host list assigned. Assign the host list under +Analyzer jobs don't execute successfully without a host list assigned. Assign the host list under the **Entra ID** > **Settings** > **Host Lists Assignment** node. Check the **Local host** box and click **Save**. **Connection Profile** -Since the Entra ID Solution is not collecting any data, a specific connection profile is not +Since the Entra ID Solution isn't collecting any data, a specific connection profile isn't necessary. Therefore, the default setting **Use the Default Profile** is sufficient for this solution. @@ -53,8 +53,8 @@ The following is the recommended workflow: **Step 1 –** Assign the Local host at the solution level as described above. -**Step 2 –** Run the .Entra ID Inventory Job Group. If on-premises directory syncing information is -desired, run the .Active Directory Inventory Job Group. +**Step 2 –** Run the .Entra ID Inventory Job Group. If you want on-premises directory syncing +information, run the .Active Directory Inventory Job Group. **Step 3 –** Schedule the solution to run as desired with consideration to the run schedules of the solutions collecting data. diff --git a/docs/accessanalyzer/12.0/solutions/entraid/users/aad_directmembership.md b/docs/accessanalyzer/12.0/solutions/entraid/users/aad_directmembership.md index bd5cdd4e76..1145929de8 100644 --- a/docs/accessanalyzer/12.0/solutions/entraid/users/aad_directmembership.md +++ b/docs/accessanalyzer/12.0/solutions/entraid/users/aad_directmembership.md @@ -6,7 +6,7 @@ sidebar_position: 10 # AAD_DirectMembership Job -The AAD_DirectMembership Job identifies Microsoft Entra ID users who do not have any group +The AAD_DirectMembership Job identifies Microsoft Entra ID users who don't have any group membership. This condition may indicate unnecessary user accounts that are suitable candidates for review and cleanup. @@ -16,7 +16,7 @@ Navigate to the **Jobs** > **Entra ID** > **2.Users** > **AAD_DirectMembership** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/entraid/users/aad_disabledusers.md b/docs/accessanalyzer/12.0/solutions/entraid/users/aad_disabledusers.md index b62779946a..11d551206d 100644 --- a/docs/accessanalyzer/12.0/solutions/entraid/users/aad_disabledusers.md +++ b/docs/accessanalyzer/12.0/solutions/entraid/users/aad_disabledusers.md @@ -7,7 +7,7 @@ sidebar_position: 20 # AAD_DisabledUsers Job The AAD_DisabledUsers Job identifies disabled user accounts within Microsoft Entra ID. These -accounts should be reviewed and cleaned up in order to increase security and reduce complexity. +accounts should be reviewed and cleaned up to increase security and reduce complexity. ## Analysis Tasks for the AAD_DisabledUsers Job @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **Entra ID** > **2.Users** > **AAD_DisabledUsers** > and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/entraid/users/aad_staleusers.md b/docs/accessanalyzer/12.0/solutions/entraid/users/aad_staleusers.md index 72b425fe40..cea18537e1 100644 --- a/docs/accessanalyzer/12.0/solutions/entraid/users/aad_staleusers.md +++ b/docs/accessanalyzer/12.0/solutions/entraid/users/aad_staleusers.md @@ -7,7 +7,7 @@ sidebar_position: 30 # AAD_StaleUsers Job The AAD_StaleUsers Job identifies potentially stale users based on a variety of factors. These -accounts should be reviewed and cleaned up in order to increase security and reduce complexity. +accounts should be reviewed and cleaned up to increase security and reduce complexity. ## Analysis Tasks for the AAD_StaleUsers Job @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **Entra ID** > **2.Users** > **AAD_StaleUsers** > **C select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -34,4 +34,4 @@ following pre-configured report. | Report | Description | Default Tags | Report Elements | | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Stale Users | This report identifies user accounts which have not logged into the domain for an extended amount of time or are currently disabled. A user account is considered stale if the last logon is over 30 days ago or is currently disabled. | None | This report is comprised of three elements:
  • Stacked Bar Chart – Displays users by domain
  • Table – Provides details on users
  • Tables – Provides details on users by domain
| +| Stale Users | This report identifies user accounts which have not logged into the domain for an extended amount of time or are disabled. A user account is considered stale if the last logon is over 30 days ago or is disabled. | None | This report is comprised of three elements:
  • Stacked Bar Chart – Displays users by domain
  • Table – Provides details on users
  • Tables – Provides details on users by domain
| diff --git a/docs/accessanalyzer/12.0/solutions/entraid/users/aad_userattributecompletion.md b/docs/accessanalyzer/12.0/solutions/entraid/users/aad_userattributecompletion.md index 3d287aea16..f95116f5ac 100644 --- a/docs/accessanalyzer/12.0/solutions/entraid/users/aad_userattributecompletion.md +++ b/docs/accessanalyzer/12.0/solutions/entraid/users/aad_userattributecompletion.md @@ -16,7 +16,7 @@ Navigate to the **Jobs** > **Entra ID** > **2.Users** > **AAD_UserAttributeCompl **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/entraid/users/aad_userdirsync.md b/docs/accessanalyzer/12.0/solutions/entraid/users/aad_userdirsync.md index 40764372a1..caa8c98170 100644 --- a/docs/accessanalyzer/12.0/solutions/entraid/users/aad_userdirsync.md +++ b/docs/accessanalyzer/12.0/solutions/entraid/users/aad_userdirsync.md @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **Entra ID** > **2.Users** > **AAD_UserDirSync** > ** select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/entraid/users/overview.md b/docs/accessanalyzer/12.0/solutions/entraid/users/overview.md index 96608e6cf6..811f4b3b72 100644 --- a/docs/accessanalyzer/12.0/solutions/entraid/users/overview.md +++ b/docs/accessanalyzer/12.0/solutions/entraid/users/overview.md @@ -17,10 +17,10 @@ The jobs in the 2.Users Job Group are: not have any group membership. This condition may indicate unnecessary user accounts that are suitable candidates for review and cleanup. - [AAD_DisabledUsers Job](/docs/accessanalyzer/12.0/solutions/entraid/users/aad_disabledusers.md) – Identifies disabled user accounts within Microsoft - Entra ID. These accounts should be reviewed and cleaned up in order to increase security and + Entra ID. These accounts should be reviewed and cleaned up to increase security and reduce complexity. - [AAD_StaleUsers Job](/docs/accessanalyzer/12.0/solutions/entraid/users/aad_staleusers.md)– Identifies potentially stale users based on a variety of - factors. These accounts should be reviewed and cleaned up in order to increase security and reduce + factors. These accounts should be reviewed and cleaned up to increase security and reduce complexity. - [AAD_UserAttributeCompletion Job](/docs/accessanalyzer/12.0/solutions/entraid/users/aad_userattributecompletion.md)– Identifies which attributes are present within User fields in Microsoft Entra ID, and which ones are blank for a majority of diff --git a/docs/accessanalyzer/12.0/solutions/entraidinventory/1-aad_scan.md b/docs/accessanalyzer/12.0/solutions/entraidinventory/1-aad_scan.md index 3e81a76e00..1a76879a4f 100644 --- a/docs/accessanalyzer/12.0/solutions/entraidinventory/1-aad_scan.md +++ b/docs/accessanalyzer/12.0/solutions/entraidinventory/1-aad_scan.md @@ -27,7 +27,7 @@ The 1-AAD_Scan job uses the AzureADInventory and Entra Data Collectors for the f - AAD Inventory – Targets Microsoft Entra tenants to collect inventory data for user group objects - _(Optional)_ This query can be modified to specify scan options and to collect custom - attributes. See the [Configure the AAD_Inventory Query](#configure-the-aad_inventory-query) + attributes. See the [Configure the AAD_Inventory Query](#configure-the-aadinventory-query) topic for additional information. - Entra – Collects Entra roles details from the target Microsoft Entra tenants @@ -35,14 +35,14 @@ The 1-AAD_Scan job uses the AzureADInventory and Entra Data Collectors for the f ### Configure the AAD_Inventory Query The 1-AAD_Scan job is configured to run with the default settings with the category of Scan Entra -ID. Follow the steps to customize configurations. +ID. To customize configurations: **Step 1 –** Navigate to the **.Entra ID Inventory** > **1-AAD_Scan** > **Configure** node and select **Queries**. ![Query Properties button on Query Selection page](/images/accessanalyzer/12.0/solutions/entraidinventory/scanqueryselectionproperties.webp) -**Step 2 –** In the Query Selection view, click on **Query Properties** to open the Query Properties +**Step 2 –** In the Query Selection view, click **Query Properties** to open the Query Properties window. ![Query Properties window](/images/accessanalyzer/12.0/solutions/entraidinventory/scanqueryproperties.webp) @@ -94,7 +94,7 @@ Navigate to the **.Entra ID Inventory** > **1-AAD_Scan** > **Configure** node an **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/entraidinventory/2-aad_exceptions.md b/docs/accessanalyzer/12.0/solutions/entraidinventory/2-aad_exceptions.md index f89f17123f..08dc2fc27f 100644 --- a/docs/accessanalyzer/12.0/solutions/entraidinventory/2-aad_exceptions.md +++ b/docs/accessanalyzer/12.0/solutions/entraidinventory/2-aad_exceptions.md @@ -16,7 +16,7 @@ Navigate to the **.Entra ID Inventory** > **2-AAD_Exceptions** > **Configure** n modified. :::warning -Most of these analysis tasks are preconfigured and should not be modified and not be +Most of these analysis tasks are preconfigured and shouldn't be modified or deselected. There are a few which are deselected by default, as they are for troubleshooting purposes. ::: @@ -80,7 +80,7 @@ The default values for parameters that can be customized are: | Stale Membership | @STALE_THRESHOLD | 10 | A group where 10% of its effective members are stale users | See the -[Configure the Analysis Tasks for the 2-AAD_Exceptions Job](#configure-the-analysis-tasks-for-the-2-aad_exceptions-job) +[Configure the Analysis Tasks for the 2-AAD_Exceptions Job](#configure-the-analysis-tasks-for-the-2-aadexceptions-job) section for instructions to modify parameters. See the [AzureADInventory Exception Types Translated](/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/standardtables.md#azureadinventory-exception-types-translated) topic for an explanation of Exception Types. @@ -89,8 +89,7 @@ topic for an explanation of Exception Types. Customizable parameters enable Access Analyzer users to set the values used to classify user and group objects during this job’s analysis. The parameters can be customized and are listed in a -section at the bottom of the SQL Script Editor. Follow the steps to customize an analysis task’s -parameters. +section at the bottom of the SQL Script Editor. To customize an analysis task’s parameters: :::warning Modifying these parameters affects solutions with .Entra ID Inventory Job Group @@ -113,7 +112,7 @@ Configuration**. The SQL Script Editor opens. **Step 4 –** Double-click in a field in the Value column and enter a custom value. :::warning -Do not change any parameters where the Value states **Created during execution**. +Don't change any parameters where the Value states **Created during execution**. ::: diff --git a/docs/accessanalyzer/12.0/solutions/entraidinventory/recommended.md b/docs/accessanalyzer/12.0/solutions/entraidinventory/recommended.md index 06ceaa3430..f2e1189ec7 100644 --- a/docs/accessanalyzer/12.0/solutions/entraidinventory/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/entraidinventory/recommended.md @@ -12,7 +12,7 @@ to the job group, it can be run directly or scheduled. **Dependencies** -This job group does not have dependencies. +This job group doesn't have dependencies. **Targeted Hosts** @@ -22,7 +22,7 @@ All Microsoft Entra Tenants. The Connection Profile is assigned under **.Entra ID Inventory** > **Settings** > **Connection**. It is set to **Use the Default Profile**, as configured at the global **Settings** level. However, if -this is not the Connection Profile with the necessary permissions for targeting the Microsoft Entra +this isn't the Connection Profile with the necessary permissions for targeting the Microsoft Entra tenants, select the **Select one of the following user defined profiles** option and select the appropriate Connection Profile. See the [Microsoft Entra ID Connection Profile & Host List](/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/configurejob.md) @@ -47,14 +47,14 @@ often. It is best to rerun it anytime Entra ID changes might have occurred. **Run at the Solution Level** -The jobs in the .Entra ID Inventory Job Group should be run together and in order by running the -entire solution, instead of the individual jobs. +Run the jobs in the .Entra ID Inventory Job Group together and in order by running the entire +solution, instead of the individual jobs. **Query Configuration** -Run the solution with the default query configuration for best results. While it is recommended to -make no changes to the [1-AAD_Scan Job](/docs/accessanalyzer/12.0/solutions/entraidinventory/1-aad_scan.md), a possible modification might be to scope -the query to not collect login activity. +Run the solution with the default query configuration for best results. It's best to leave the +[1-AAD_Scan Job](/docs/accessanalyzer/12.0/solutions/entraidinventory/1-aad_scan.md) unchanged, but a possible modification is to scope +the query to skip collecting sign-in activity. **Analysis Configuration** diff --git a/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/ex_activesync.md b/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/ex_activesync.md index 1b9e4dd22d..7c4025065f 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/ex_activesync.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/ex_activesync.md @@ -18,7 +18,7 @@ View the analysis tasks by navigating to the **Exchange** > **2. CAS Metrics** > **EX_ActiveSync** > **Configure** node and select **Analysis**. :::warning -Most of these analysis tasks are preconfigured and should not be modified or +Most of these analysis tasks are preconfigured and shouldn't be modified or deselected. There are some that are deselected by default, as they are for troubleshooting purposes. ::: @@ -50,7 +50,7 @@ The following analysis task deletes table data from the analysis jobs. This anal remain cleared unless specifically needed: :::warning -Do not select the **00. Deletes all History** option. This analysis task is for +Don't select the **00. Deletes all History** option. This analysis task is for troubleshooting and cleanup only. Data will be deleted from the database. ::: @@ -72,7 +72,7 @@ the following pre-configured reports: | Report | Description | Default Tags | Report Elements | | ----------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Device Types (Device Population) | This report identifies what device models are currently being used with ActiveSync, and the average load they put on the environment each day. | None | This report is comprised of two elements:
  • Bar Chart – Displays most popular devices
  • Table – Provides details on most popular devices
| +| Device Types (Device Population) | This report identifies what device models are being used with ActiveSync, and the average load they put on the environment each day. | None | This report is comprised of two elements:
  • Bar Chart – Displays most popular devices
  • Table – Provides details on most popular devices
| | Server Traffic (Top Servers by Average Daily Traffic) | This report ranks CAS servers by volume of ActiveSync traffic. | None | This report is comprised of two elements:
  • Bar Chart – Displays top users by average daily traffic
  • Table – Provides details on top users by average daily traffic
| | Top Users (Top Users by Average Daily Traffic) | This report shows the top users of ActiveSync. | None | This report is comprised of two elements:
  • Bar Chart – Displays top users by average daily traffic
  • Table – Provides details on top users by average daily traffic
| | User Devices (User Phones) | This report identifies all devices which have been associated with a User, and the time frames when they were used. | None | This report is comprised of one element:
  • Table – Provides details on user devices
| diff --git a/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/ex_aspolicies.md b/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/ex_aspolicies.md index e959d2671f..05169fed8e 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/ex_aspolicies.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/ex_aspolicies.md @@ -26,7 +26,7 @@ The following query is included in the EX_ASPolicies Job. The ExchangePS Data Collector can be scoped if desired. -Follow the steps to scope the ExchangePS Data Collector: +To scope the ExchangePS Data Collector: **Step 1 –** Navigate to job’s **Configure** node and select **Queries**. @@ -37,28 +37,28 @@ Properties**. The Query Properties window opens. Wizard opens. :::warning -Do not modify other wizard pages. The wizard pages are pre-configured for this job. +Don't modify other wizard pages. The wizard pages are pre-configured for this job. ::: ![ExchangePS Data Collector Wizard Scope page](/images/activitymonitor/8.0/config/activedirectory/scope.webp) -**Step 4 –** Navigate to the Scope page, and select the desired scoping method from those available. +**Step 4 –** Navigate to the Scope page, and select the scoping method you want from those available. See the [ExchangePS: Scope](/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scope.md) topic for additional information. - Scope by Database – Select the **Scope by Database Target Host: Local Host** option. Then, click - **Next** and identify the desired databases on the Scope by Databases page. See the + **Next** and identify the databases you want on the Scope by Databases page. See the [ExchangePS: Scope by DB](/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scopedatabases.md) topic for additional information. - Scope by Mailbox – Select the **Scope by Mailbox Target Host: Local Host** option. Then, click - **Next** and identify the desired mailboxes on the Scope by Mailboxes page. See the + **Next** and identify the mailboxes you want on the Scope by Mailboxes page. See the [ExchangePS: Scope by Mailboxes](/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scopemailboxes.md) topic for additional information. - Scope by Server – Select the **Scope by Server Target Host: Exchange MB Server** option. The job returns results for specific servers selected in job’s **Configure** > **Hosts** node. - Scope by Public Folder – Select the **Scope by Public Folder** option. Then, click **Next** and - identify the desired mailboxes on the Scope by Public Folders page. See the + identify the mailboxes you want on the Scope by Public Folders page. See the [ExchangePS: Scope by Public Folders](/docs/accessanalyzer/12.0/admin/datacollector/exchangeps/scopepublicfolders.md) topic for additional information. - _Remember,_ the scoping options available vary based on the pre-defined query configurations. @@ -73,7 +73,7 @@ View the analysis tasks by navigating to the **Exchange** > **2. CAS Metrics** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/ex_iislogs.md b/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/ex_iislogs.md index 4bb6eda1a6..544587cd31 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/ex_iislogs.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/ex_iislogs.md @@ -6,7 +6,7 @@ sidebar_position: 20 # 0.Collection > EX_IISLogs Job -The 0.Collection > EX_IISLogs Job provides data collection to be utilized in the ActiveSync, Outlook +The 0.Collection > EX_IISLogs Job provides data collection to be used in the ActiveSync, Outlook Web Access, and Outlook Anywhere Reports. This job goes out to each server that contains the IIS Logs and parses the log to return the data to the Access Analyzer database. @@ -36,7 +36,7 @@ modified on the Target Log page of the SMART Log DC Wizard. See the [SMARTLog Data Collector](/docs/accessanalyzer/12.0/admin/datacollector/smartlog/overview.md) topic for additional information. -Follow the steps to modify the query configuration. +To modify the query configuration: **Step 1 –** Navigate to the **Exchange** > **2. CAS Metrics** > **0. Collection** > **EX_IISLogs** > **Configure** node and select **Queries**. @@ -47,7 +47,7 @@ opens. **Step 3 –** Select the **Data Source** tab, and click **Configure**. The SMART Log DC Wizard opens. :::warning -Do not modify other wizard pages. The other wizard pages are pre-configured for this +Don't modify other wizard pages. The other wizard pages are pre-configured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/ex_owatraffic.md b/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/ex_owatraffic.md index 289d37db36..083bef26e9 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/ex_owatraffic.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/ex_owatraffic.md @@ -18,7 +18,7 @@ View the analysis tasks by navigating to the **Exchange** > **2. CAS Metrics** > Access** > **EX_OWATraffic** > **Configure** node and select **Analysis**. :::warning -Most of these analysis tasks are preconfigured and should not be modified ordeselected. +Most of these analysis tasks are preconfigured and shouldn't be modified ordeselected. There is one that is deselected by default, as it is for troubleshooting purposes. ::: @@ -46,7 +46,7 @@ The following analysis task deletes table data from data collection and analysis task should remain cleared unless specifically needed: :::warning -Do not select the **00. Delete all History** option. This analysis task is for +Don't select the **00. Delete all History** option. This analysis task is for troubleshooting and cleanup only. Data will be deleted from the database. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/ex_rpctraffic.md b/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/ex_rpctraffic.md index af0bcbff75..5aff79b1cb 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/ex_rpctraffic.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/ex_rpctraffic.md @@ -19,7 +19,7 @@ View the analysis tasks by navigating to the **Exchange** > **2. CAS Metrics** > Anywhere** > **EX_RPCTraffic** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -47,7 +47,7 @@ The following analysis tasks deletes table data from data collection and analysi analysis tasks should remain cleared unless specifically needed: :::warning -Do not select the **00. Delete all History** option. This analysis task is for +Don't select the **00. Delete all History** option. This analysis task is for troubleshooting and cleanup only. Data will be deleted from the database. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/overview.md b/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/overview.md index 4f773c431b..22bc918d5d 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/overview.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/overview.md @@ -6,7 +6,7 @@ sidebar_position: 30 # 2.CAS Metrics Job Group -The 2. CAS Metrics Job Group is comprised of data collection, analysis and reports that focus on +The 2. CAS Metrics Job Group is comprised of data collection, analysis, and reports that focus on remote connections (Outlook Web Access, ActiveSync, and Outlook Anywhere Access) occurring within your organization. This job group goes out to each server that contains the IIS Logs and parses the logs to return the data to the Access Analyzer database. @@ -15,7 +15,7 @@ logs to return the data to the Access Analyzer database. The jobs in the 2.CAS Metrics Job Group are: -- [0.Collection > EX_IISLogs Job](/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/ex_iislogs.md) – Provides data collection to be utilized in the +- [0.Collection > EX_IISLogs Job](/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/ex_iislogs.md) – Provides data collection to be used in the ActiveSync, Outlook Web Access, and Outlook Anywhere Reports. This job group goes out to each server that contains the IIS Logs and parses the logs to return the data to the Access Analyzer database. diff --git a/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/recommended.md b/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/recommended.md index fe03b7c152..4e910d204c 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/recommended.md @@ -60,7 +60,7 @@ Run this Job Group at 2:00 AM. **History Retention** -History retention should not be enabled on this job group. History is kept through analysis tasks. +History retention shouldn't be enabled on this job group. History is kept through analysis tasks. Modify the following analysis tasks to customize the amount of history which is kept. | Job Name | Analysis Task Name | Default History | @@ -84,12 +84,12 @@ No other queries should be modified. The 2. CAS Metrics Job Group should be run with the default analysis configurations. :::warning -Most of these analysis tasks are preconfigured and should not be modified or +Most of these analysis tasks are preconfigured and shouldn't be modified or deselected. There are some that are deselected by default, as they are for troubleshooting purposes. ::: -The following analysis tasks should not be deselected, but their parameters can be modified: +The following analysis tasks shouldn't be deselected, but their parameters can be modified: - **ActiveSync** > **EX_ActiveSync** Job – **07. SET HISTORY RETENTION** Analysis Task - **Outlook Anywhere** > **EX_RPCTraffic** Job – **05. SET HISTORY RETENTION** Analysis Task diff --git a/docs/accessanalyzer/12.0/solutions/exchange/databases/collection/ex_dbinfo.md b/docs/accessanalyzer/12.0/solutions/exchange/databases/collection/ex_dbinfo.md index 364e39f368..4f16b34cae 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/databases/collection/ex_dbinfo.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/databases/collection/ex_dbinfo.md @@ -6,7 +6,7 @@ sidebar_position: 10 # 1.Local > EX_DBInfo Job -The EX_DBInfo job utilizes Exchange PowerShell to gather 2010/2013 Mailbox Size information. +The EX_DBInfo job uses Exchange PowerShell to gather 2010/2013 Mailbox Size information. ![1.Local > EX_DBInfo Job in the Jobs Tree](/images/accessanalyzer/12.0/solutions/exchange/databases/collection/localjobstree.webp) diff --git a/docs/accessanalyzer/12.0/solutions/exchange/databases/collection/ex_pfinfo.md b/docs/accessanalyzer/12.0/solutions/exchange/databases/collection/ex_pfinfo.md index 0fb7196ea1..84564fd0e6 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/databases/collection/ex_pfinfo.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/databases/collection/ex_pfinfo.md @@ -6,7 +6,7 @@ sidebar_position: 20 # 2.PF > EX_PFInfo Job -The EX_PFInfo job utilizes MAPI to gather Public Folder Database Information focusing on database +The EX_PFInfo job uses MAPI to gather Public Folder Database Information focusing on database sizing, growth, and trends. ![2.PF > EX_PFInfo Job in the Jobs Tree](/images/accessanalyzer/12.0/solutions/exchange/databases/collection/pfjobstree.webp) @@ -18,7 +18,7 @@ The EX_PFInfo job is located in the 2.PF job group. The EX_PFInfo Job uses the Exchange2K Data Collector for the query. :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/databases/collection/overview.md b/docs/accessanalyzer/12.0/solutions/exchange/databases/collection/overview.md index 692a6f50fd..ea72783600 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/databases/collection/overview.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/databases/collection/overview.md @@ -13,7 +13,7 @@ database sizing, growth, and trends. The jobs in the 0.Collection Job Group are: -- [1.Local > EX_DBInfo Job](/docs/accessanalyzer/12.0/solutions/exchange/databases/collection/ex_dbinfo.md) – Utilizes Exchange PowerShell to gather 2010/2013 Mailbox +- [1.Local > EX_DBInfo Job](/docs/accessanalyzer/12.0/solutions/exchange/databases/collection/ex_dbinfo.md) – uses Exchange PowerShell to gather 2010/2013 Mailbox Size Information -- [2.PF > EX_PFInfo Job](/docs/accessanalyzer/12.0/solutions/exchange/databases/collection/ex_pfinfo.md) – Utilizes MAPI to gather Public Folder Database Information +- [2.PF > EX_PFInfo Job](/docs/accessanalyzer/12.0/solutions/exchange/databases/collection/ex_pfinfo.md) – uses MAPI to gather Public Folder Database Information focusing on database sizing, growth, and trends diff --git a/docs/accessanalyzer/12.0/solutions/exchange/databases/ex_dbsizing.md b/docs/accessanalyzer/12.0/solutions/exchange/databases/ex_dbsizing.md index 35038c13ac..719aafc1a8 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/databases/ex_dbsizing.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/databases/ex_dbsizing.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **Exchange** > **3. Databases** > * **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -44,7 +44,7 @@ The following analysis task deletes table data from data collection and analysis task should remain cleared unless specifically needed: :::warning -Do not select the **00. Deletes all Stored Data** option. This analysis task is for +Don't select the **00. Deletes all Stored Data** option. This analysis task is for troubleshooting and cleanup only. Data will be deleted from the database. ::: @@ -60,7 +60,7 @@ following pre-configured reports: | Report | Description | Default Tags | Report Elements | | ---------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Database Details (Storage Group Details) | This report provides the details of Mailbox Stores grouped by Server, then Storage Group. This report helps administrators locate Storage Groups that may be growing out of control. If a storage group with very few users is extremely large, further investigation may be required. | None | This report is comprised of two elements:
  • Bar Chart – Displays database sizes
  • Table – Provides details on database sizes
| -| Database Growth Statistics | This report displays the top 10 Databases that grew over the last 30 days in pure MB. This report is filtered on the Rank Column for Top 10 and may be modified to fit any desired Top outcome. | None | This report is comprised of four elements:
  • Stacked Bar Chart – Displays store size growth
  • Stacked Bar Chart – Displays WhiteSpace growth
  • Table – Provides details on store size growth
  • Table – Provides details on WhiteSpace growth
| +| Database Details (Storage Group Details) | This report provides the details of Mailbox Stores grouped by Server, then Storage Group. This report helps administrators locate Storage Groups with unchecked growth. If a storage group with very few users is extremely large, investigate further. | None | This report is comprised of two elements:
  • Bar Chart – Displays database sizes
  • Table – Provides details on database sizes
| +| Database Growth Statistics | This report displays the top 10 Databases that grew over the last 30 days in pure MB. This report filters on the Rank column for the top 10 results, but you can modify it to show a different top number. | None | This report is comprised of four elements:
  • Stacked Bar Chart – Displays store size growth
  • Stacked Bar Chart – Displays WhiteSpace growth
  • Table – Provides details on store size growth
  • Table – Provides details on WhiteSpace growth
| | Historical Database Information | This report shows the history of the store size, white space, mailbox count, and hard drive space on all targeted servers. | None | This report is comprised of one element:
  • Table – Displays details on historical store information
| -| Mailbox Counts by Database | This report graphically displays the number of Mailboxes by Database.  It provides an overall picture of the Exchange Mailbox Environment. Having a clear break down of the number of mailboxes per database allows for better planning of architecture in the future. | None | This report is comprised of two elements:
  • Bar Chart – Displays mailbox counts by database
  • Table – Provides details on mailbox counts by database
| +| Mailbox Counts by Database | This report graphically displays the number of Mailboxes by Database. It provides an overall picture of the Exchange Mailbox Environment. A clear breakdown of mailbox counts per database helps you plan future architecture. | None | This report is comprised of two elements:
  • Bar Chart – Displays mailbox counts by database
  • Table – Provides details on mailbox counts by database
| diff --git a/docs/accessanalyzer/12.0/solutions/exchange/databases/ex_dbtrending.md b/docs/accessanalyzer/12.0/solutions/exchange/databases/ex_dbtrending.md index 6f1fccff1e..5bc274b434 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/databases/ex_dbtrending.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/databases/ex_dbtrending.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **Exchange** > **3. Databases** > * **Configure** node and selecting **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -39,4 +39,4 @@ the following pre-configured report: | Report | Description | Default Tags | Report Elements | | --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Capacity Planning
  • Databases
| This report displays the growth rate trend of your private stores and the growth rate trend of your public stores.  The trend is projected for two months. These reports help identify bad trends in growth on Exchange servers for hard drive space usage is key in avoiding running out of space. | None | This report is comprised of two elements:
  • Line Chart – Displays private store trend
  • Line Chart – Displays public store trend
| +| Capacity Planning
  • Databases
| This report displays the growth rate trend of your private stores and the growth rate trend of your public stores. The trend is projected for two months. These reports help identify bad growth trends on Exchange servers, since managing hard drive space usage is key to avoiding running out of space. | None | This report is comprised of two elements:
  • Line Chart – Displays private store trend
  • Line Chart – Displays public store trend
| diff --git a/docs/accessanalyzer/12.0/solutions/exchange/databases/overview.md b/docs/accessanalyzer/12.0/solutions/exchange/databases/overview.md index 0a35c89fee..7424964f51 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/databases/overview.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/databases/overview.md @@ -22,7 +22,7 @@ The following comprise the 3. Databases Job Group: The 3. Databases Job Group uses a MAPI-based data collector, Exchange2K. Therefore, it requires both Access Analyzer MAPI CDO and Microsoft Exchange MAPI CDO to be installed on the Access Analyzer -Console server. Once these have been installed, the **Settings** > **Exchange** node must be +Console server. After these are installed, the **Settings** > **Exchange** node must be configured for proper connection to the Exchange server. See the [Exchange](/docs/accessanalyzer/12.0/admin/settings/exchange.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/solutions/exchange/databases/recommended.md b/docs/accessanalyzer/12.0/solutions/exchange/databases/recommended.md index 706566b6ca..bfbc7bbe0f 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/databases/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/databases/recommended.md @@ -56,7 +56,7 @@ Run this Job Group at 3:00 AM. **History Retention** -History retention should not be enabled on this job group. History is kept through analysis tasks. +History retention shouldn't be enabled on this job group. History is kept through analysis tasks. Modify the following analysis tasks to customize the amount of history which is kept: | Job Name | Analysis Task Name | Default History | @@ -82,7 +82,7 @@ deselected. There are some that are deselected by default, as they are for troub ::: -The following analysis task should not be deselected, but the parameters can be modified: +The following analysis task shouldn't be deselected, but the parameters can be modified: - **EX_DBSizing** Job – **SET HISTORY RETENTION** Analysis Task diff --git a/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/ex_dlcleanup.md b/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/ex_dlcleanup.md index c20d1bfb83..47d705181f 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/ex_dlcleanup.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/ex_dlcleanup.md @@ -16,7 +16,7 @@ View the analysis task by navigating to the **Exchange** > **6. Distribution Lis **EX_DLCleanup** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/ex_groupexpansion.md b/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/ex_groupexpansion.md index 11d3d97525..5b354cbdbb 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/ex_groupexpansion.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/ex_groupexpansion.md @@ -18,7 +18,7 @@ View the analysis tasks by navigating to the **Exchange** > **6. Distribution Li Membership** > **EX_GroupExpansion** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/membershipanalysis/ex_circularnesting.md b/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/membershipanalysis/ex_circularnesting.md index d2b0071b75..d063b207b4 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/membershipanalysis/ex_circularnesting.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/membershipanalysis/ex_circularnesting.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **Exchange** > **6. Distribution Li Analysis** > **EX_CircularNesting** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/membershipanalysis/ex_emptygroups.md b/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/membershipanalysis/ex_emptygroups.md index fe9661aec6..ac3a062430 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/membershipanalysis/ex_emptygroups.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/membershipanalysis/ex_emptygroups.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **Exchange** > **6. Distribution Li Analysis** > **EX_EmptyGroups** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/membershipanalysis/ex_largestgroups.md b/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/membershipanalysis/ex_largestgroups.md index da59184b01..568e747d9a 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/membershipanalysis/ex_largestgroups.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/membershipanalysis/ex_largestgroups.md @@ -14,7 +14,7 @@ View the analysis task by navigating to the **Exchange** > **6. Distribution Lis Analysis** > **EX_LargestGroups** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/membershipanalysis/ex_nestedgroups.md b/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/membershipanalysis/ex_nestedgroups.md index 37f75161e0..ecc41a92da 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/membershipanalysis/ex_nestedgroups.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/membershipanalysis/ex_nestedgroups.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **Exchange** > **6. Distribution Li Analysis** > **EX_NestedGroups** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/membershipanalysis/ex_stalegroups.md b/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/membershipanalysis/ex_stalegroups.md index 7fdda5586e..98aec367c3 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/membershipanalysis/ex_stalegroups.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/membershipanalysis/ex_stalegroups.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **Exchange** > **6. Distribution Li Analysis** > **EX_StaleGroups** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/recommended.md b/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/recommended.md index 899adaf8bf..3602c9cb54 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/distributionlists/recommended.md @@ -25,7 +25,7 @@ The following job groups need to be successfully run: **Schedule Frequency** This job group has been designed to run daily after the .Active Directory Inventory Job Group has -been run, to analyze distribution list membership. This job group does not collect data. It uses the +been run, to analyze distribution list membership. This job group doesn't collect data. It uses the data collection from the .Active Directory Inventory Job Group. :::info diff --git a/docs/accessanalyzer/12.0/solutions/exchange/ex_useroverview.md b/docs/accessanalyzer/12.0/solutions/exchange/ex_useroverview.md index ccdb4051c3..4297da22c0 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/ex_useroverview.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/ex_useroverview.md @@ -15,7 +15,7 @@ environment. **Dependencies** -The following job groups need to be successfully run prior to this job: +The following job groups need to be successfully run before this job: - **.Active Directory Inventory** Job Group - **.Entra ID Inventory** Job Group @@ -27,8 +27,7 @@ The following job groups need to be successfully run prior to this job: **Schedule Frequency** -It is recommended to run this job daily after running its dependencies, but it can be scheduled to -run as desired. +Run this job daily after its dependencies run, but you can schedule it at another time if needed. ## Analysis Tasks for the EX_Mailflow_UserOverview Job @@ -36,7 +35,7 @@ View the analysis task by navigating to the **Exchange** > **EX_UserOverview** > and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/collection/appletstatuscheck.md b/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/collection/appletstatuscheck.md index 6ac184610b..3a6b0472be 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/collection/appletstatuscheck.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/collection/appletstatuscheck.md @@ -14,7 +14,7 @@ Exchange servers. The .AppletStatusCheck Job uses the Script Data Collector. :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/collection/ex_metricscollection.md b/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/collection/ex_metricscollection.md index ab0ff8c5e0..b7e66a0406 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/collection/ex_metricscollection.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/collection/ex_metricscollection.md @@ -6,7 +6,7 @@ sidebar_position: 20 # EX_MetricsCollection Job -The EX_MetricsCollection Job is comprised of multiple queries that utilize the ExchangeMetrics Data +The EX_MetricsCollection Job is comprised of multiple queries that use the ExchangeMetrics Data Collector to process and collect the message tracking logs on the Exchange servers in the environment. These queries collect server, domain, user, and distribution list traffic including but not limited to: sent, received, journal, NDRs, and transports messages. These queries are configured @@ -45,7 +45,7 @@ View the analysis tasks by navigating to the **Exchange** > **1. HUB Metrics** > **EX_MetricsCollection** > **Configure** node and selecting **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -78,7 +78,7 @@ The following analysis task deletes table data from data collection and analysis task should remain deselected unless specifically needed: :::warning -Do not select the **00. Deletes all Stored Data** option. This analysis task is for +Don't select the **00. Deletes all Stored Data** option. This analysis task is for troubleshooting and cleanup only. Data will be deleted from the database. ::: @@ -92,8 +92,8 @@ troubleshooting and cleanup only. Data will be deleted from the database. The **08. SET HISTORY RETENTION** analysis task controls the retention period for the job’s data. This is why the Data Retention Period options at the global, job group, or job Properties settings -are not supported for the job group. The number of months can be modified. If desired, the parameter -can be set to a specified number of days. Follow these steps to modify the history retention period. +aren't supported for the job group. The number of months can be modified. If desired, the parameter +can be set to a specified number of days. To modify the history retention period: **Step 1 –** Navigate to the job’s **Configure** node and select **Analysis**. @@ -128,21 +128,21 @@ Skip to Step 5. **Step 5 –** Click **Save and Close**. The SQL Script Editor closes. -The modified history retention period is now applied during future job executions. +Access Analyzer applies the modified history retention period to future job executions. ## Troubleshooting Data Collection -There might be times when it is necessary to purge the data either through dropping the tables from -the database or truncating the data within the tables. This option is provided through ananalysis -task that is not selected by default. Only one analysis task within a job should be enabled when the -desire is to purge that database. +There might be times when you need to purge the data either through dropping the tables from +the database or truncating the data within the tables. An analysis task that isn't selected by +default provides this option. Enable only one analysis task within a job when you want to purge +that database. :::warning This analysis task deletes information collected or produced by jobs in this solution. ::: -Follow these steps to troubleshoot data collection: +To troubleshoot data collection: **Step 1 –** Navigate to the job’s **Configure** node and select **Analysis**. @@ -159,9 +159,9 @@ Remember, only one task should be selected. **Step 3 –** In the Navigation pane, right-click the **Analysis** node and select **Execute Analyses**. -**Step 4 –** After the analysis task has been executed, return to the Analysis Selection view. -Deselect the analysis task which was executed and reselect the default analysis tasks (if any had -been cleared in Step 2). +**Step 4 –** After you execute the analysis task, return to the Analysis Selection view. Deselect +the analysis task you executed and reselect the default analysis tasks (if you cleared any in +Step 2). -The selected purge of data and tables has taken place, and the analysis tasks have been reset to the -default state. +Access Analyzer purges the selected data and tables and resets the analysis tasks to their default +state. diff --git a/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/collection/ex_metricsdetails.md b/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/collection/ex_metricsdetails.md index 7d5089e351..074517de4d 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/collection/ex_metricsdetails.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/collection/ex_metricsdetails.md @@ -9,8 +9,8 @@ sidebar_position: 30 The EX_MetricsDetails Job collects daily user-to-user Traffic. Walk through this jobs query to configure the internal domains to collect the sender to recipient traffic from. By default, the query is configured to collect the previous 1 day of Message Tracking Logs and has @netwrix.com -configured as the domain. If the domains are not configured in the query, then most likely data -collection does not return. +configured as the domain. If the domains aren't configured in the query, then most likely data +collection doesn't return. ## Queries for the EX_MetricsDetails Job @@ -31,7 +31,7 @@ The following query is included in the EX_MetricsDetails Job: The Activity Metrics Query has been preconfigured to run with the ExchangeMetrics Data Collector to collect user traffic per day. The domains must be configured for data collection to return data. -Follow the steps to configure the Activity Metrics Query. +To configure the Activity Metrics Query: **Step 1 –** Navigate to the **Exchange** > **1. HUB Metrics** > **0. Collection** > **EX_MetricsDetails** > **Configure** node and select **Queries**. @@ -43,7 +43,7 @@ Properties**. The Query Properties window opens. Collector Wizard opens. :::warning -Do not modify other wizard pages. The wizard pages are pre-configured for this job. +Don't modify other wizard pages. The wizard pages are pre-configured for this job. ::: @@ -65,7 +65,7 @@ View the analysis tasks by navigating to the **Exchange** > **1. HUB Metrics** > **EX_MetricsDetails** > **Configure** node and selecting **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -87,7 +87,7 @@ The following analysis task clears table data from data collection and analysis task should remain deselected unless specifically needed: :::warning -Do not select the **00. DROP HISTORY** option. This analysis task is for +Don't select the **00. DROP HISTORY** option. This analysis task is for troubleshooting and cleanup only. Data will be deleted from the database. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/collection/overview.md b/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/collection/overview.md index f3820c46a6..949d990c3e 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/collection/overview.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/collection/overview.md @@ -15,7 +15,7 @@ The jobs in the 0.Collection Job Group are: - [.AppletStatusCheck Job](/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/collection/appletstatuscheck.md) – Checks the health and status of the applet deployed to the target Exchange servers -- [EX_MetricsCollection Job](/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/collection/ex_metricscollection.md) – Comprised of multiple queries that utilize +- [EX_MetricsCollection Job](/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/collection/ex_metricscollection.md) – Comprised of multiple queries that use the Exchange Metrics Data Collect to process and collect the message tracking logs on the Exchange servers in the environment. These queries collect server, domain, user, and distribution list traffic including but not limited to sent, received, journal, NDRs, and transports message. These @@ -28,6 +28,6 @@ The jobs in the 0.Collection Job Group are: This job's query needs to be configured to the internal domains from which to collect the sender to recipient traffic. By default, the query is configured to collect the previous 1 day of Message Tracking Logs and has @netwrix.com configured as the domain. If the domains are - not configured in the query, then most likely data collection does not return. + not configured in the query, then most likely data collection doesn't return. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_deliverytimes.md b/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_deliverytimes.md index d51bd9c869..9f69f7c2e0 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_deliverytimes.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_deliverytimes.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **Exchange** > **1. HUB Metrics** > **EX_DeliveryTimes** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_dlmetrics.md b/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_dlmetrics.md index bf3c170293..c6a243cc97 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_dlmetrics.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_dlmetrics.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **Exchange** > **1. HUB Metrics** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_domainmetrics.md b/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_domainmetrics.md index ad3286f10d..1d48d192d0 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_domainmetrics.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_domainmetrics.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **Exchange** > **1. HUB Metrics** > **EX_DomainMetrics** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_hourlymetrics.md b/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_hourlymetrics.md index 292cbbac66..a3cc4ef405 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_hourlymetrics.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_hourlymetrics.md @@ -15,13 +15,13 @@ View the analysis tasks by navigating to the **Exchange** > **1. HUB Metrics** > **EX_HourlyMetrics** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_messagesize.md b/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_messagesize.md index f6210bdbb6..aa2431ddf0 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_messagesize.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_messagesize.md @@ -14,7 +14,7 @@ View the analysis task by navigating to the **Exchange** > **1. HUB Metrics** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_servermetrics.md b/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_servermetrics.md index a0a7b46083..012f7e29a8 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_servermetrics.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_servermetrics.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **Exchange** > **1. HUB Metrics** > **EX_ServerMetrics** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_usermetrics.md b/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_usermetrics.md index 102fee40b0..f62aaba917 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_usermetrics.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_usermetrics.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **Exchange** > **1. HUB Metrics** > **EX_UserMetrics** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/overview.md b/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/overview.md index 2afe653761..fa4bc38c22 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/overview.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/overview.md @@ -6,9 +6,9 @@ sidebar_position: 20 # 1.HUB Metrics Job Group -The 1. HUB Metrics Job Group is comprised of data collection, analysis and reports that focus on -mail-flow activity occurring within your organization. This job group goes out to each server that -contains the Message Tracking Logs and parse the log to return the data to the Access Analyzer +The 1. HUB Metrics Job Group is comprised of data collection, analysis, and reports that focus on +mail-flow activity occurring within your organization. This job group connects to each server that +contains the Message Tracking Logs and parses the log to return the data to the Access Analyzer database. ![1.HUB Metrics Job Group in the Jobs Tree](/images/accessanalyzer/12.0/solutions/exchange/hubmetrics/jobstree.webp) @@ -27,6 +27,6 @@ The following job groups and jobs comprise the 1. HUB Metrics Job Group: - [EX_MessageSize Job](/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_messagesize.md) – Provides information around size of messages sent and received - [EX_ServerMetrics Job](/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_servermetrics.md) – Provides visibility into server mail-flow - statistics, such as, sent, received, journaling, transport and NDR counts and sizes + statistics, such as, sent, received, journaling, transport, and NDR counts and sizes - [EX_UserMetrics Job](/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/ex_usermetrics.md) – Provides information around each user’s mail-flow in the organization diff --git a/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/recommended.md b/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/recommended.md index 0152ff06ff..4ef99d2b6c 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/recommended.md @@ -54,7 +54,7 @@ Run this job group at 1:00 AM. **History Retention** -History retention should not be enabled on this job group. History is kept through analysis tasks. +History retention shouldn't be enabled on this job group. History is kept through analysis tasks. Modify the following analysis tasks to customize the amount of history which is kept: | Job Name | Analysis Task Name | Default History | @@ -82,13 +82,13 @@ following exceptions: The 1. HUB Metrics Job Group should be run with the default analysis configurations. :::warning -Most of these analysis tasks are preconfigured and should not be modified or +Most of these analysis tasks are preconfigured and shouldn't be modified or deselected. There are a few which are deselected by default, as they are for troubleshooting purposes. ::: -The following analysis tasks should not be deselected, but their parameters can be modified: +The following analysis tasks shouldn't be deselected, but their parameters can be modified: - **0. Collection** > **EX_MetricsCollection** Job – **08. SET HISTORY RETENTION** Analysis Task - **0. Collection** > **EX_MetricsDetails** Job – **02. SET HISTORY RETENTION** Analysis Task diff --git a/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/ex_features.md b/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/ex_features.md index 157cef2013..fa49cda48a 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/ex_features.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/ex_features.md @@ -7,7 +7,7 @@ sidebar_position: 20 # Features > EX_Features Job The EX_Features job is comprised of data collection and a report that provides information around -which features have been enabled or disabled on Mailboxes, such as ActiveSync, IMAP, POP and more. +which features have been enabled or disabled on Mailboxes, such as ActiveSync, IMAP, POP, and more. :::info Schedule the Features Job Group to run weekly on any desired recurrence. diff --git a/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/logons/ex_mailboxlogons.md b/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/logons/ex_mailboxlogons.md index 1470aa3a06..6fe2c39f67 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/logons/ex_mailboxlogons.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/logons/ex_mailboxlogons.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **Exchange** > **4. Mailboxes** > * **EX_MailboxLogons** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -45,7 +45,7 @@ The following analysis task deletes table data from data collection and analysis task should remain cleared unless specifically needed: :::warning -Do not select the **00. Delete All Historical Data** option. This analysis task is for +Don't select the **00. Delete All Historical Data** option. This analysis task is for troubleshooting and cleanup only. Data will be deleted from the database. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/logons/overview.md b/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/logons/overview.md index f29eecb31d..0ed7ee57fd 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/logons/overview.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/logons/overview.md @@ -6,8 +6,8 @@ sidebar_position: 30 # Logons Job Group -The Logons Job Group provides collection of Native Mailbox Access Auditing logs from Exchange to -provide reporting around mailbox logon activity. +The Logons Job Group collects Native Mailbox Access Auditing logs from Exchange to provide reporting +around mailbox logon activity. :::info Schedule the Logons Job Group to run daily at 7 PM. diff --git a/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/overview.md b/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/overview.md index 484cba06b9..2c18d14298 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/overview.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/overview.md @@ -20,10 +20,10 @@ These jobs are compatible with the Office 365 environment. - [Features > EX_Features Job](/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/ex_features.md) – Comprised of data collection and a report that provides information around which features have been enabled or disabled on mailboxes, such as - ActiveSync, IMAP, POP and more + ActiveSync, IMAP, POP, and more - [Logons Job Group](/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/logons/overview.md) – Provides collection of Native Mailbox Access Auditing logs from Exchange to provide reporting around mailbox logon activity -- [Permissions Job Group](/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/permissions/overview.md) – Comprised of data collection, analysis and +- [Permissions Job Group](/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/permissions/overview.md) – Comprised of data collection, analysis, and reports that focus on access granted to each mailbox in the environment including, Mailbox Rights, Active Directory Permissions, Delegation, and Folder Permissions - [Sizing Job Group](/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/sizing/overview.md) – Provides data collection, analyses, and reports which diff --git a/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/permissions/collection/ex_sendas.md b/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/permissions/collection/ex_sendas.md index 45fe9090fe..d16ce41ee9 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/permissions/collection/ex_sendas.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/permissions/collection/ex_sendas.md @@ -38,7 +38,7 @@ View the analysis task by navigating to the **Exchange** > **4. Mailboxes** > ** **0.Collection** > **EX_SendAs** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/permissions/ex_admingroups.md b/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/permissions/ex_admingroups.md index b45a90eb87..f048e84a07 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/permissions/ex_admingroups.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/permissions/ex_admingroups.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **Exchange** > **4. Mailboxes** > * **EX_AdminGroups** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/permissions/ex_mailboxaccess.md b/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/permissions/ex_mailboxaccess.md index 09c26dc90d..18ec959717 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/permissions/ex_mailboxaccess.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/permissions/ex_mailboxaccess.md @@ -16,7 +16,7 @@ View the analysis tasks by navigating to the **Exchange** > **4. Mailboxes** > * **EX_MailboxAccess** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -52,7 +52,7 @@ The following analysis tasks are selected by default: - 12.Send As Summary – Creates the SA_EX_MailboxAccess_SendAsSummary table accessible under the job’s Results node -The following analysis tasks is selected to export data to the AIC: +The following analysis task is selected to export data to the Access Information Center (AIC): - 13.AIC Import - Export Exchange Permissions – Exports delegates, Send AS rights, mailbox permissions, and Active Directory rights to the Access Information Center @@ -73,5 +73,5 @@ the following pre-configured reports: | Delegation (Delegates) | This report identifies users where Delegate/Send on Behalf Of rights have been assigned and which objects the users have been given rights to. | None | This report is comprised of two elements:
  • Bar Chart – Displays top users by number of delegates
  • Table – Provides details on top users by number of delegates
| | Full Control Access (Mailboxes with Full Control) | This report identifies users with the largest amount of Full Control rights assigned to other individuals. | None | This report is comprised of two elements:
  • Bar Chart – Displays top users with full control granted
  • Table – Provides details on top users with full control granted
| | Incorrect Default And Anon Permissions | This report identifies where Default or Anonymous have any role assignment other than **None** or **Free/Busy time**. | None | This report is comprised of three elements:
  • Bar Chart – Displays top users with incorrect default/anon permissions
  • Table – Provides details on top users with incorrect default/anon permissions
  • Table – Provides role details
| -| Missing Anonymous Permissions | This report identifies folders where Anonymous permissions are not assigned. | None | This report is comprised of one element:
  • Table – Provides details on missing anonymous permissions
| +| Missing Anonymous Permissions | This report identifies folders where Anonymous permissions aren't assigned. | None | This report is comprised of one element:
  • Table – Provides details on missing anonymous permissions
| | Send As (Send-As Rights) | This report identifies which users have the highest number of users with Send-As rights to their mailbox. | None | This report is comprised of three elements:
  • Stacked Bar Chart – Displays top users by send as rights granted
  • Table – Provides details on top users by send as right granted
  • Table – Provides additional details
| diff --git a/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/permissions/overview.md b/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/permissions/overview.md index d74fae1059..9e021caed8 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/permissions/overview.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/permissions/overview.md @@ -6,7 +6,7 @@ sidebar_position: 40 # Permissions Job Group -The Permissions job group is comprised of data collection, analysis and reports that focus on access +The Permissions job group is comprised of data collection, analysis, and reports that focus on access granted to each mailbox in the environment including, Mailbox Rights, Active Directory Permissions, Delegation, and Folder Permissions. diff --git a/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/recommended.md b/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/recommended.md index ef26b86bb1..2c78c8a52a 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/recommended.md @@ -8,7 +8,7 @@ sidebar_position: 10 **Dependencies** -This job group requires the following items to be enabled: +This job group requires you to enable the following items: - Exchange Access Auditing is enabled in the Exchange environment @@ -16,7 +16,7 @@ This job group requires the following items to be enabled: [Enable Exchange Mailbox Access Auditing](/docs/accessanalyzer/12.0/requirements/exchange/support/powershell.md#enable-exchange-mailbox-access-auditing) topic for additional information. -The following job groups need to be successfully run: +Successfully run the following job groups first: - **.Active Directory Inventory** Job Group - **.Entra ID Inventory** Job Group @@ -38,11 +38,11 @@ on-premises to run against: - Local host This Job Group can target a custom host list for Exchange Online instead of targeting Exchange -on-premises. However, do not try to target both types of environments. +on-premises. However, don't try to target both types of environments. **Connection Profile** -A Connection Profile must be set directly on the collection jobs within each sub-job group: +Set a Connection Profile directly on the collection jobs within each sub-job group: - **Features** > **EX_Features** Job - **Logons** > **0.Collection** > **EX_MailboxActivity** Job @@ -62,7 +62,7 @@ topic for additional information. **Schedule Frequency** -It is not recommended to run these jobs at the 4. Mailboxes job group level. The Logons sub-job +Don't run these jobs at the 4. Mailboxes job group level. The Logons sub-job group and Sizing job group have been designed to run daily. The Features sub-job group and Permissions job group have been designed to run weekly. See the table for recommended times: @@ -75,7 +75,7 @@ Permissions job group have been designed to run weekly. See the table for recomm **History Retention** -History retention should not be enabled on this job group. History is kept through analysis tasks. +Don't enable history retention on this job group. History is kept through analysis tasks. Modify the following analysis tasks to customize the amount of history which is kept: | Job Name | Analysis Task Name | Default History | @@ -85,7 +85,7 @@ Modify the following analysis tasks to customize the amount of history which is **Query Configuration** -The 4. Mailboxes job group is designed to be run with the default query configurations. However, the +Run the 4. Mailboxes job group with the default query configurations. However, the following queries can be modified: - **Features** > **EX_Features** Job – **User Mailbox Settings** Query @@ -96,20 +96,20 @@ following queries can be modified: - **Permissions** > **0. Collection** > **EX_SendAs** Job – **Send AS - Rights** Query - **Sizing** > **0. Collection** > **EX_MBSize** Job – **Mailbox Counts and Sizes** Query -No other queries should be modified. +Don't modify other queries. **Analysis Configuration** -The 4. Mailboxes job group should be run with the default analysis configurations. +Run the 4. Mailboxes job group with the default analysis configurations. :::warning -Most of these analysis tasks are preconfigured and should not be modified or +Most of these analysis tasks are preconfigured and shouldn't be modified or deselected. There are some tasks that are deselected by default, as they are for troubleshooting purposes. ::: -The following analysis tasks should not be deselected, but their parameters can be modified: +The following analysis tasks shouldn't be deselected, but their parameters can be modified: - **Logons** > **EX_MailboxLogons** Job – **03.SET HISTORY RETENTION** Analysis Task - **Sizing** > **EX_MailboxSizes** Job – **02.SET HISTORY RETENTION** Analysis Task diff --git a/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/sizing/ex_mailboxsizes.md b/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/sizing/ex_mailboxsizes.md index e6f9401410..4818ae9b01 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/sizing/ex_mailboxsizes.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/sizing/ex_mailboxsizes.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **Exchange** > **4. Mailboxes** > * **EX_MailboxSizes** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -47,8 +47,8 @@ The following analysis task deletes table data from data collection and analysis task should remain cleared unless specifically needed: :::warning -Do not select the **00.Delete All Data** option. This analysis task is for -troubleshooting and cleanup only. Data will be deleted from the database: +Don't select the **00.Delete All Data** option. This analysis task is for +troubleshooting and cleanup only. Selecting it deletes data from the database: ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/sizing/ex_stalemailboxes.md b/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/sizing/ex_stalemailboxes.md index ba1f1c93be..f4255b480e 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/sizing/ex_stalemailboxes.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/sizing/ex_stalemailboxes.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **Exchange** > **4. Mailboxes** > * **EX_StaleMailboxes** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -35,5 +35,5 @@ produces the following pre-configured reports: | Report | Description | Default Tags | Report Elements | | --------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Orphaned Mailboxes | Orphaned Mailboxes do not have an Active Directory account associated with them, and generally can be safely deleted. | None | This report is comprised of three elements:
  • Bar Chart – Displays orphan mailbox storage
  • Table – Provides details on all orphaned mailboxes
  • Table – Provides details on orphan mailbox storage
| +| Orphaned Mailboxes | Orphaned Mailboxes don't have an Active Directory account associated with them, and generally can be safely deleted. | None | This report is comprised of three elements:
  • Bar Chart – Displays orphan mailbox storage
  • Table – Provides details on all orphaned mailboxes
  • Table – Provides details on orphan mailbox storage
| | Stale Users (Mailboxes associated with Stale AD Accounts) | This report shows mailboxes which are tied to stale user accounts. | None | This report is comprised of three elements:
  • Bar Chart – Displays stale user mailboxes
  • Table – Provides details stale user mailboxes
  • Table – Provides additional details on stale user mailboxes
| diff --git a/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/sizing/ex_storesizes.md b/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/sizing/ex_storesizes.md index 93ed8d1a0c..4378471169 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/sizing/ex_storesizes.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/sizing/ex_storesizes.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **Exchange** > **4. Mailboxes** > **Sizing** > **EX_StoreSizes** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow.md b/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow.md index 98aff0077f..d5d270a86f 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow.md @@ -14,7 +14,7 @@ The EX_Mailflow job is located in the **Mailflow** > **0. Collection** job group ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/12.0/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -23,7 +23,7 @@ The EX_Mailflow job has the following configurable parameter: - Number of months to keep -See the [Analysis Tasks for the EX_Mailflow Job](#analysis-tasks-for-the-ex_mailflow-job) topic for +See the [Analysis Tasks for the EX_Mailflow Job](#analysis-tasks-for-the-exmailflow-job) topic for additional information. ## Queries for the EX_Mailflow Job @@ -44,7 +44,7 @@ The following queries are included in the EX_Mailflow job: - LocalDomains – Collects domains local to the Office 365 environment :::warning - Do not modify this query. The query is preconfigured for this job. + Don't modify this query. The query is preconfigured for this job. ::: @@ -56,7 +56,7 @@ The following queries are included in the EX_Mailflow job: The ExchangePS Data Collector configured with the Mail Flow Metrics category can be scoped to specific report dates. By default, the MailFlow Query is set to report on the Last 7 Days. -Follow the steps to modify the query configuration: +To modify the query configuration: **Step 1 –** Navigate to the **Exchange** > **8. Exchange Online** > **0. Collection** > **EX_Mailflow** > **Configure** node and select **Queries**. @@ -68,7 +68,7 @@ Properties window opens. Wizard opens. :::warning -Do not modify other wizard pages. The wizard pages are pre-configured for this job. +Don't modify other wizard pages. The wizard pages are pre-configured for this job. ::: @@ -94,7 +94,7 @@ View the analysis tasks by navigating to the **Exchange** > **8. Exchange Online Collection** > **EX_Mailflow** > **Configure** node and selecting **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -120,8 +120,8 @@ The following analysis task deletes table data from data collection and analysis task should remain cleared unless specifically needed: :::warning -Do not select the **00. Deletes all Stored Data** option. This analysis task is for -troubleshooting and cleanup only. Data will be deleted from the database. +Don't select the **00. Deletes all Stored Data** option. This analysis task is for +troubleshooting and cleanup only. Selecting it deletes data from the database. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow_dl.md b/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow_dl.md index da59f4a13f..74ece60563 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow_dl.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow_dl.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **Exchange** > **8. Exchange Online **EX_Mailflow_DL** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow_domain.md b/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow_domain.md index 338496649d..324bc22e3d 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow_domain.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow_domain.md @@ -11,7 +11,7 @@ coming from. This job is set to analyze the last 30 days. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/12.0/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -21,7 +21,7 @@ The EX_Mailflow_Domain job has the following configurable parameter: - Number of days to show in tables and reports See the -[Analysis Tasks for the EX_Mailflow_Domain Job](#analysis-tasks-for-the-ex_mailflow_domain-job) +[Analysis Tasks for the EX_Mailflow_Domain Job](#analysis-tasks-for-the-exmailflowdomain-job) topic for additional information. ## Analysis Tasks for the EX_Mailflow_Domain Job @@ -30,7 +30,7 @@ View the analysis task by navigating to the **Exchange** > **8. Exchange Online* **EX_Mailflow_Domain** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow_mailbox.md b/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow_mailbox.md index 1011be02a6..4eb6c540af 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow_mailbox.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow_mailbox.md @@ -11,7 +11,7 @@ This job is set to analyze the last 30 days. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/12.0/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -22,7 +22,7 @@ The EX_Mailflow_Mailbox job has the following configurable parameter: Count** and **User Mailboxes by Message Size** analysis tasks. The default is **30** days. See the -[Analysis Tasks for the EX_Mailflow_Mailbox Job](#analysis-tasks-for-the-ex_mailflow_mailbox-job) +[Analysis Tasks for the EX_Mailflow_Mailbox Job](#analysis-tasks-for-the-exmailflowmailbox-job) topic for additional information. ## Analysis Tasks for the EX_Mailflow_Mailbox Job @@ -31,7 +31,7 @@ View the analysis tasks by navigating to the **Exchange** > **8. Exchange Online **EX_Mailflow_Mailbox** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow_orgoverview.md b/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow_orgoverview.md index caeab5b77c..91b896c3da 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow_orgoverview.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow_orgoverview.md @@ -11,7 +11,7 @@ This job is set to analyze the last 30 days. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/12.0/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -21,7 +21,7 @@ The EX_Mailflow_OrgOverview job has the following configurable parameter: - Number of days of data to display See the -[Analysis Tasks for the EX_Mailflow_OrgOverview Job](#analysis-tasks-for-the-ex_mailflow_orgoverview-job) +[Analysis Tasks for the EX_Mailflow_OrgOverview Job](#analysis-tasks-for-the-exmailfloworgoverview-job) topic for additional information. ## Analysis Tasks for the EX_Mailflow_OrgOverview Job diff --git a/docs/accessanalyzer/12.0/solutions/exchange/online/recommended.md b/docs/accessanalyzer/12.0/solutions/exchange/online/recommended.md index b4a733cbc2..2a5667e48a 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/online/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/online/recommended.md @@ -8,7 +8,7 @@ sidebar_position: 10 **Dependencies** -The following Access Analyzer job groups need to be successfully run: +Successfully run the following Access Analyzer job groups first: - .Active Directory Inventory - .Entra ID Inventory @@ -16,7 +16,7 @@ The following Access Analyzer job groups need to be successfully run: **Targeted Hosts** The Mailflow job group uses Remote PowerShell through the ExchangePS Data Collector and the -PowerShell Data Collector. The host list needs to be set to one of the following: +PowerShell Data Collector. Set the host list to one of the following: - Local Host - Custom Host List for Exchange Online @@ -44,7 +44,7 @@ topic for additional information. **Schedule Frequency** -This job group has been designed to run daily. +Run this job group daily. :::info Run this job group at 1:00 AM. @@ -53,21 +53,21 @@ Run this job group at 1:00 AM. **Query Configuration** -The 8. Exchange Online job group is designed to be run with the default query configurations. +Run the 8. Exchange Online job group with the default query configurations. However, the following queries can be modified: - **Mailflow** > **0. Collection** > **EX_Mailflow** Job – **MailFlow** Query - **EX_ASPolicies** Job – **Exchange Settings** Query -No other queries should be modified. +Don't modify other queries. **Analysis Configuration** -The 8. Exchange Online job group should be run with the default analysis configurations. Most of +Run the 8. Exchange Online job group with the default analysis configurations. Most of these analysis tasks are preconfigured and should never be modified or deselected. There are some that are deselected by default, as they are for troubleshooting purposes. -The following analysis tasks should not be deselected, but their parameters can be modified: +The following analysis tasks shouldn't be deselected, but their parameters can be modified: - **Mailflow** > **0. Collection** > **EX_Mailflow** Job – **03. SET HISTORY RETENTION** Analysis Task @@ -80,7 +80,7 @@ The following analysis tasks should not be deselected, but their parameters can **Step 1 –** Set the host on the EX_Mailflow job. -- The **Mailflow** > **0. Collection** > **EX_Mailflow** job needs to be set to run against one of +- Set the **Mailflow** > **0. Collection** > **EX_Mailflow** job to run against one of the following: - Local Host diff --git a/docs/accessanalyzer/12.0/solutions/exchange/overview.md b/docs/accessanalyzer/12.0/solutions/exchange/overview.md index 974e189a9c..3f315bc879 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/overview.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/overview.md @@ -35,22 +35,22 @@ topics for additional information. **Sensitive Data Discovery Considerations** -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the minimum amount -of RAM. Each thread requires a minimum of 2 additional GB of RAM per host.For example, if the job is -configured to scan 8 hosts at a time , then an extra 16 GB of RAM are required (8x2=16). +If you run Sensitive Data Discovery (SDD) scans, increase the minimum amount of RAM. Each thread +requires a minimum of 2 additional GB of RAM per host. For example, if the job scans 8 hosts at a +time, it requires an extra 16 GB of RAM (8 x 2 = 16). :::note -The appropriate JDK (Java) version for Sensitive Data Discovery is installed on the -server. The JDK deployed is prepackaged and does not require any configuration; it has been -preconfigured to work with Access Analyzer and should never be customized through Java. It will not -conflict with other JDKs or Java Runtimes in the same environment. +Access Analyzer installs the appropriate JDK (Java) version for Sensitive Data Discovery on the +server. This JDK is prepackaged, requires no configuration, and comes preconfigured to work with +Access Analyzer. Don't customize it through Java. It doesn't conflict with other JDKs or Java +Runtimes in the same environment. ::: **Location** The Exchange Solution requires a special Access Analyzer license. It can be installed from the -Access Analyzer Instant Job Wizard. Once it has been installed into the Jobs tree, navigate to the +Access Analyzer Instant Job Wizard. After it's installed into the Jobs tree, navigate to the solution: **Jobs** > **Exchange**. Each job group within the solution collects data, analyzes the data, and reports on the target @@ -66,21 +66,21 @@ The Exchange Solution is divided into categories based upon what is being audite The following job groups comprise the Exchange Solution: -- [1.HUB Metrics Job Group](/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/overview.md) – Comprised of data collection, analysis and +- [1.HUB Metrics Job Group](/docs/accessanalyzer/12.0/solutions/exchange/hubmetrics/overview.md) – Comprised of data collection, analysis, and reports that focus on mail-flow activity occurring within your organization. This job group goes out to each server that contains the Message Tracking Logs and parses the log to return the data to the Access Analyzer database. -- [2.CAS Metrics Job Group](/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/overview.md) – Comprised of data collection, analysis and +- [2.CAS Metrics Job Group](/docs/accessanalyzer/12.0/solutions/exchange/casmetrics/overview.md) – Comprised of data collection, analysis, and reports that focus on remote connections (Outlook Web Access, ActiveSync, and Outlook Anywhere Access) occurring within your organization. This job group goes out to each server that contains the IIS Logs and parses the log to return the data to the Access Analyzer database. -- [3.Databases Job Group](/docs/accessanalyzer/12.0/solutions/exchange/databases/overview.md) – Comprised of data collection, analysis and +- [3.Databases Job Group](/docs/accessanalyzer/12.0/solutions/exchange/databases/overview.md) – Comprised of data collection, analysis, and reports that focus on database sizing, growth, and trends - [4.Mailboxes Job Group](/docs/accessanalyzer/12.0/solutions/exchange/mailboxes/overview.md) – Comprised of data collection, analyses, and reports around mailbox features, logons, permissions, and sizing :::warning - It is not recommended to run this job group at this job group level. + Don't run this job group at this job group level. ::: @@ -106,6 +106,6 @@ The following job groups comprise the Exchange Solution: impact analysis on the environment. This job depends upon multiple job groups. The MAPI-based data collectors require both Access Analyzer MAPI CDO and Microsoft Exchange MAPI CDO -to be installed on the Access Analyzer Console server. Once these have been installed, configure the +on the Access Analyzer Console server. After you install them, configure the **Settings** > **Exchange** node for proper connection to the Exchange server. See the [Exchange](/docs/accessanalyzer/12.0/admin/settings/exchange.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/content/pf_content.md b/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/content/pf_content.md index b94d7fdf5b..4bab951b15 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/content/pf_content.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/content/pf_content.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **Exchange** > **5. Public Folders* **PF_Content** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/content/pf_contentscans.md b/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/content/pf_contentscans.md index e727363058..07507cb943 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/content/pf_contentscans.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/content/pf_contentscans.md @@ -34,7 +34,7 @@ View the analysis task by navigating to the **Exchange** > **5. Public Folders** **Collection** > **PF_ContentScans** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/growthsize/pf_folderscans.md b/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/growthsize/pf_folderscans.md index 1cf8518637..b32414171f 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/growthsize/pf_folderscans.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/growthsize/pf_folderscans.md @@ -34,7 +34,7 @@ View the analysis task by navigating to the **Exchange** > **5. Public Folders** Size** > **Collection** > **PF_FolderScans** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/growthsize/pf_foldersize.md b/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/growthsize/pf_foldersize.md index 54a65f642d..726cc124ce 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/growthsize/pf_foldersize.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/growthsize/pf_foldersize.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **Exchange** > **5. Public Folders* Size** > **PF_FolderSize** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -41,8 +41,8 @@ The following analysis task clears table data from data collection and analysis task should remain cleared unless specifically needed: :::warning -Do not select the **00. Delete all Historical Data** option. This analysis task is for -troubleshooting and cleanup only. Data will be deleted from the database. +Don't select the **00. Delete all Historical Data** option. This analysis task is for +troubleshooting and cleanup only. Selecting it deletes data from the database. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/ownership/pf_folderownership.md b/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/ownership/pf_folderownership.md index 238c266f27..2be3f94560 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/ownership/pf_folderownership.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/ownership/pf_folderownership.md @@ -28,7 +28,7 @@ The following queries are included in the PF_FolderOwnership job: - By default set to search all public folders. It can be scoped. - See the - [Scope the ExchangePublicFolder Data Collector for the PF_FolderOwnership Job](#scope-the-exchangepublicfolder-data-collector-for-the-pf_folderownership-job) + [Scope the ExchangePublicFolder Data Collector for the PF_FolderOwnership Job](#scope-the-exchangepublicfolder-data-collector-for-the-pffolderownership-job) topic for additional information - Assigned Ownership – Collects assigned owners @@ -36,13 +36,13 @@ The following queries are included in the PF_FolderOwnership job: - By default set to search all public folders. It can be scoped. - Probable Owner Calculation can be modified - See the - [Scope the ExchangePublicFolder Data Collector for the PF_FolderOwnership Job](#scope-the-exchangepublicfolder-data-collector-for-the-pf_folderownership-job) + [Scope the ExchangePublicFolder Data Collector for the PF_FolderOwnership Job](#scope-the-exchangepublicfolder-data-collector-for-the-pffolderownership-job) topic for additional information ### Scope the ExchangePublicFolder Data Collector for the PF_FolderOwnership Job -The ExchangePublicFolder Data Collector can be scoped if desired. Follow the steps to modify the -query configuration. +The ExchangePublicFolder Data Collector can be scoped if desired. To modify the +query configuration: :::note These instructions include information on modifying the calculation used to determine @@ -60,7 +60,7 @@ Properties window opens. Data Collector Wizard opens. :::warning -Do not modify other wizard pages. The wizard pages are pre-configured for this job. +Don't modify other wizard pages. The wizard pages are pre-configured for this job. ::: @@ -73,8 +73,8 @@ using the following settings: - Default Public Folders – Select this option to access folders directly with client applications such as Microsoft Outlook. In its default configuration, Exchange System Manager - displays these folders when a public folder tree is expanded. - - System Public Folders – Select this option to access folders that cannot be directly accessed. + displays these folders when you expand a public folder tree. + - System Public Folders – Select this option to access folders that can't be directly accessed. Client applications, such as Microsoft Outlook, use these folders to store information such as free and busy data, offline address lists, and organizational forms. Other folders hold configuration information that is used by custom applications or by Exchange itself. The @@ -122,7 +122,7 @@ View the analysis task by navigating to the **Exchange** > **5. Public Folders** **Collection** > **PF_FolderOwnership** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/ownership/pf_owners.md b/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/ownership/pf_owners.md index 7c9a4cf63e..284388c241 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/ownership/pf_owners.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/ownership/pf_owners.md @@ -17,7 +17,7 @@ View the analysis tasks by navigating to the **Exchange** > **5. Public Folders* **PF_Owners** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/permissions/pf_entitlements.md b/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/permissions/pf_entitlements.md index a1226739f8..1cfdbe8c2f 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/permissions/pf_entitlements.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/permissions/pf_entitlements.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **Exchange** > **5. Public Folders* **Permissions** > **PF_Entitlements** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -34,7 +34,7 @@ The following analysis tasks are selected by default: under the job’s Results node - 04.Unresolved SIDs – Creates the SA_PF_Entitlements_UnresolvedSIDDetails table, accessible under the job’s Results node -- AIC Import - PF Entitlements – Imports public folder entitlements to the Access Information Center +- AIC Import - PF Entitlements – Imports public folder entitlements to the Access Information Center (AIC) In addition to the tables and views created by the analysis tasks, the PF_Entitlements job produces the following pre-configured reports: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/permissions/pf_entitlementscans.md b/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/permissions/pf_entitlementscans.md index 262e9072b2..1cde137ebf 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/permissions/pf_entitlementscans.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/permissions/pf_entitlementscans.md @@ -35,7 +35,7 @@ View the analysis tasks by navigating to the **Exchange** > **5. Public Folders* **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/pf_overview.md b/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/pf_overview.md index 5da366c95a..7f0982c22b 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/pf_overview.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/pf_overview.md @@ -16,7 +16,7 @@ View the analysis tasks by navigating to the **Exchange** > **5. Public Folders* **PF_Overview** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/recommended.md b/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/recommended.md index c52da88b7f..50c345a767 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/recommended.md @@ -78,7 +78,7 @@ Run this job group on Fridays at 8:00 PM. **History Retention** -History retention should not be enabled on this job group. History is kept through analysis tasks. +History retention shouldn't be enabled on this job group. History is kept through analysis tasks. Modify the following analysis task to customize the amount of history which is kept: | Job Name | Analysis Task Name | Default History | @@ -109,7 +109,7 @@ deselected. There are some that are deselected by default, as they are for troub ::: -The following analysis tasks should not be deselected, but their parameters can be modified: +The following analysis tasks shouldn't be deselected, but their parameters can be modified: - **Growth and Size** > **PF_FolderSize** Job – **02.SET HISTORY RETENTION** Analysis Task diff --git a/docs/accessanalyzer/12.0/solutions/exchange/recommended.md b/docs/accessanalyzer/12.0/solutions/exchange/recommended.md index c597fa772b..25e85ca707 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/recommended.md @@ -21,20 +21,20 @@ relevant topic for specific information on job group settings and recommended sc ## ExchangePS Data Collector & Client Access Server A Client Access Server (CAS) name is required for the ExchangePS Data Collector. When targeting -Exchange 2013 or 2016, it is possible for the **Settings** > **Exchange** node to have been -configured with a web address instead of a CAS. +Exchange 2013 or 2016, the **Settings** > **Exchange** node might be configured with a web address +instead of a CAS. - Exchange 2010 Servers – Uses the CAS server set in the global configuration (**Settings** > **Exchange** node) - Exchange 2013 & 2016 – May require a CAS name set in the ExchangePS Data Collector configuration: - - If the **Settings** > **Exchange** node was configured for **MAPI over HTTP**, then a CAS - server name was supplied and that is used by the ExchangePS Data Collector + - If the **Settings** > **Exchange** node was configured for **MAPI over HTTP**, the + ExchangePS Data Collector uses the CAS server name you supplied - If the **Settings** > **Exchange** node was configured for **MAPI over HTTPS**, then the global configuration has a web address instead of an actual server. Therefore, each query requires the CAS server to be set as the specific server on the Category page. -Follow the steps to supply a CAS name for data collection. +To supply a CAS name for data collection: **Step 1 –** Navigate to the job’s **Configure** node and select **Queries**. @@ -45,8 +45,8 @@ opens. Wizard opens. :::warning -Unless otherwise indicated within the job group section, do not make changes to other -wizard pages as they have been pre-configured for the purpose of the job. +Unless otherwise indicated within the job group section, don't make changes to other +wizard pages as they have been pre-configured for the job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/sensitivedata/collection/ex_mailbox_sdd.md b/docs/accessanalyzer/12.0/solutions/exchange/sensitivedata/collection/ex_mailbox_sdd.md index e3c3243922..7fdee61cbb 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/sensitivedata/collection/ex_mailbox_sdd.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/sensitivedata/collection/ex_mailbox_sdd.md @@ -28,7 +28,7 @@ The following query is included in the EX_Mailbox_SDD job: - US SSN - See the - [Configure the EWSMailbox Data Collector for the EX_Mailbox_SDD Job](#configure-the-ewsmailbox-data-collector-for-the-ex_mailbox_sdd-job) + [Configure the EWSMailbox Data Collector for the EX_Mailbox_SDD Job](#configure-the-ewsmailbox-data-collector-for-the-exmailboxsdd-job) topic for additional information ### Configure the EWSMailbox Data Collector for the EX_Mailbox_SDD Job @@ -36,7 +36,7 @@ The following query is included in the EX_Mailbox_SDD job: The Exchange Sensitive Data Discovery query has been preconfigured to run with the EWSMailbox Data Collector to scan for sensitive data. -Follow the steps to configure the scope of the EWSMailbox Data Collector: +To configure the scope of the EWSMailbox Data Collector: **Step 1 –** Navigate to the **Exchange** > **7. Sensitive Data** > **0. Collection** > **EX_Mailbox_SDD** > **Configure** node and select **Queries**. @@ -48,7 +48,7 @@ click **Query Properties**. The Query Properties window opens. Wizard opens. :::warning -Do not make changes to other wizard pages as they have been pre-configured for the +Don't make changes to other wizard pages as they have been pre-configured for the purpose of this job. ::: @@ -64,7 +64,7 @@ information. ![EWS Mailbox Data Collector Wizard Scope select page](/images/accessanalyzer/12.0/solutions/exchange/sensitivedata/collection/mailboxscopeselect.webp) **Step 5 –** To retrieve available mailboxes, click **Retrieve** on the Scope Select page. Select -the desired mailboxes and click **Add**. See the +the mailboxes you want and click **Add**. See the [EWSMailbox: Scope Select](/docs/accessanalyzer/12.0/admin/datacollector/ewsmailbox/scopeselect.md) topic for additional information. @@ -76,7 +76,7 @@ Sensitive data matches can be limited to reduce storage space. See the additional information. :::note -By default, discovered sensitive data strings are not stored in the Access Analyzer +By default, discovered sensitive data strings aren't stored in the Access Analyzer database. ::: @@ -125,7 +125,7 @@ View the analysis task by navigating to the **Exchange** > **7.Sensitive Data** **EX_Mailbox_SDD** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: @@ -134,4 +134,4 @@ preconfigured for this job. The following analysis task is selected by default: -- AIC Import - Exchange SSD – Imports Exchange sensitive data to the Access Information Center +- AIC Import - Exchange SDD – Imports Exchange sensitive data to the Access Information Center (AIC) diff --git a/docs/accessanalyzer/12.0/solutions/exchange/sensitivedata/collection/ex_publicfolder_sdd.md b/docs/accessanalyzer/12.0/solutions/exchange/sensitivedata/collection/ex_publicfolder_sdd.md index ca9f69936a..9821d5155e 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/sensitivedata/collection/ex_publicfolder_sdd.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/sensitivedata/collection/ex_publicfolder_sdd.md @@ -28,7 +28,7 @@ The following query is included in the EX_PublicFolder_SDD job: - Tax Forms - US SSN - - See the [Configure the EX_PublicFolder_SDD Query](#configure-the-ex_publicfolder_sdd-query) + - See the [Configure the EX_PublicFolder_SDD Query](#configure-the-expublicfoldersdd-query) topic for additional information ### Configure the EX_PublicFolder_SDD Query @@ -46,7 +46,7 @@ Data Collector to scan for sensitive data. Collector Wizard opens. :::warning -Do not modify other wizard pages. The wizard pages are pre-configured for this job. +Don't modify other wizard pages. The wizard pages are pre-configured for this job. ::: @@ -58,7 +58,7 @@ Sensitive data matches can be limited to reduce storage space. See the for additional information. :::note -By default, discovered sensitive data strings are not stored in the Access Analyzer +By default, discovered sensitive data strings aren't stored in the Access Analyzer database. ::: @@ -88,7 +88,7 @@ additional information. ![EWS Public Folder Data Collector Wizard Results page](/images/accessanalyzer/12.0/solutions/exchange/sensitivedata/collection/publicfolderresults.webp) **Step 7 –** To select which properties are gathered based on category, navigate to the Results -page.  See the +page. See the [EWSPublicFolder: Results](/docs/accessanalyzer/12.0/admin/datacollector/ewspublicfolder/results.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/solutions/exchange/sensitivedata/ex_sddresults.md b/docs/accessanalyzer/12.0/solutions/exchange/sensitivedata/ex_sddresults.md index 8cf62002f4..5701c0c9fa 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/sensitivedata/ex_sddresults.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/sensitivedata/ex_sddresults.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **Exchange** > **7. Sensitive Data* **EX_SDDResults** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -41,8 +41,8 @@ The following analysis task deletes table data from data collection and analysis task should remain cleared unless specifically needed: :::warning -Do not select the **Deletes all Stored Data** option. This analysis task is for -troubleshooting and cleanup only. Data will be deleted from the database. +Don't select the **Deletes all Stored Data** option. This analysis task is for +troubleshooting and cleanup only. It deletes data from the database. ::: diff --git a/docs/accessanalyzer/12.0/solutions/exchange/sensitivedata/overview.md b/docs/accessanalyzer/12.0/solutions/exchange/sensitivedata/overview.md index fd8a10c31e..67f747eaa4 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/sensitivedata/overview.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/sensitivedata/overview.md @@ -24,7 +24,7 @@ These jobs are compatible with the Office 365 environment. types of sensitive data that was located within Exchange mailboxes and public folders within the environment -The 7. Sensitive Data job group is comprised of jobs that utilize the EWSMailbox and EWSPublicFolder +The 7. Sensitive Data job group is comprised of jobs that use the EWSMailbox and EWSPublicFolder Data Collectors to locate sensitive data found in mailboxes and public folders in the Exchange environment. It also contains analysis and reporting jobs to order and analyze the data returned by the queries. See the [Exchange](/docs/accessanalyzer/12.0/admin/settings/exchange.md) topic for additional diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/activity/forensics/fs_deletions.md b/docs/accessanalyzer/12.0/solutions/filesystem/activity/forensics/fs_deletions.md index 5c0e0e39a5..01c8e4d091 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/activity/forensics/fs_deletions.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/activity/forensics/fs_deletions.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * **FS_Deletions** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -57,7 +57,7 @@ following pre-configured report: A Notification analysis task sends email notification to recipients when the job is executed. It requires the global **Notification** settings to be configured (**Settings** > **Notifications**) for SMTP server information, but it uses the recipient list provided through the analysis task. -Follow the steps to configure a notification analysis task. +To configure a notification analysis task: **Step 1 –** Navigate to the job’s **Configure** node and select **Analysis**. @@ -65,7 +65,7 @@ Follow the steps to configure a notification analysis task. **Analysis Configuration** . The Notification Data Analysis Module wizard opens. :::warning -Do not make changes to other wizard pages as they have been pre-configured for the +Don't make changes to other wizard pages as they have been pre-configured for the purpose of this job. ::: @@ -77,8 +77,8 @@ purpose of this job. ![Recipients section](/images/accessanalyzer/12.0/solutions/filesystem/activity/forensics/notificationsmtprecipients.webp) **Step 4 –** In the Recipients section, provide the email addresses or distribution lists (fully -qualified address) for those who are to receive this notification. Multiple addresses can be -provided. You can use the following options: +qualified address) for the recipients. You can provide multiple addresses. You can use the +following options: - Add – Add an email address to the E-mail field - Remove – Remove an email address from the Recipients list @@ -92,22 +92,21 @@ provided. You can use the following options: ![Message section](/images/accessanalyzer/12.0/solutions/filesystem/activity/forensics/notificationsmtpmessage.webp) -**Step 5 –** In the Message section, edit the **Subject**. It is not recommended to remove any -parameters. Then, customize the email content in the textbox to provide an explanation of the -notification to the recipients. +**Step 5 –** In the Message section, edit the **Subject**. Don't remove any parameters. Then, +customize the email content in the textbox to provide an explanation of the notification to the +recipients. **Step 6 –** Navigate to the Summary page. Click **Finish** to save any setting modifications or click **Cancel** if no changes were made. The Notification Data Analysis Module wizard closes. -**Step 7 –** This Notification analysis task is now configured to send emails to the provided -recipient list. In the Analysis Selection view, select this task so that notifications can be sent -automatically during the execution of the job. +**Step 7 –** The Notification analysis task now sends emails to the provided recipient list. In the +Analysis Selection view, select this task so the job sends notifications automatically when it runs. :::tip Remember, all of the analysis tasks should remain in the default order indicated by the numbering. -Do not deselect any of the SQLscripting analysis tasks. +Don't deselect any of the SQLscripting analysis tasks. ::: -Once the Notification analysis task is configured and enabled alerts are sent when the trigger has -been identified by this job. +After you configure and enable the Notification analysis task, the job sends alerts when it +identifies the trigger. diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/activity/forensics/fs_permissionchanges.md b/docs/accessanalyzer/12.0/solutions/filesystem/activity/forensics/fs_permissionchanges.md index 45813af258..98c1eea5ba 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/activity/forensics/fs_permissionchanges.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/activity/forensics/fs_permissionchanges.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * **FS_PermissionChanges** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/activity/fs_leastprivilegedaccess.md b/docs/accessanalyzer/12.0/solutions/filesystem/activity/fs_leastprivilegedaccess.md index d39f0ac766..46c040e94d 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/activity/fs_leastprivilegedaccess.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/activity/fs_leastprivilegedaccess.md @@ -7,7 +7,7 @@ sidebar_position: 20 # Least Privileged Access > FS_LeastPrivilegedAccess Job The FS_LeastPrivilegedAccess job is designed to report on activity event information that can assist -in identifying least privilege from targeted file servers. It identifies where trustees are not +in identifying least privilege from targeted file servers. It identifies where trustees aren't leveraging their permissions to resources from targeted file servers. Requires **Access Auditing** component data collection. @@ -21,7 +21,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Access** > **FS_LeastPrivilegedAccess** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -54,5 +54,5 @@ produces the following pre-configured reports: | Report | Description | Default Tags | Report Elements | | ------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Overprovisioning Risk by Share | This report identifies shares with the largest amount of unutilized entitlements and assigns a risk rating to each one. | GDPR SOX HIPAA PCI-DSS GLBA ITAR FERPA FISMA ISO27001 | This report is comprised of two elements:
  • Pie Chart – Displays shares by overprovisioning risk
  • Table – Provides details on shares by overprovisioning risk
| -| Overprovisioning Summary | This report shows the percentage of all entitlements which are being used. An entitlement refers to one user's access to one folder. | GDPR SOX HIPAA PCI-DSS GLBA ITAR FERPA FISMA ISO27001 | This report is comprised of two elements:
  • Pie Chart – entitlements by level of usage
  • Table – Provides details on entitlements
| -| Remediation | If all members of a group are not using their full access, then modification to group permissions on the share will be suggested here. | None | This report is comprised of one element:
  • Table – Provides details on recommended changes to permissions
| +| Overprovisioning Summary | This report shows the percentage of all entitlements in use. An entitlement refers to one user's access to one folder. | GDPR SOX HIPAA PCI-DSS GLBA ITAR FERPA FISMA ISO27001 | This report is comprised of two elements:
  • Pie Chart – entitlements by level of usage
  • Table – Provides details on entitlements
| +| Remediation | If all members of a group aren't using their full access, this report suggests changes to group permissions on the share. | None | This report is comprised of one element:
  • Table – Provides details on recommended changes to permissions
| diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/activity/security/fs_adminactvity.md b/docs/accessanalyzer/12.0/solutions/filesystem/activity/security/fs_adminactvity.md index c3754e9a5a..0b29404eaf 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/activity/security/fs_adminactvity.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/activity/security/fs_adminactvity.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * **FS_AdminActivity** > **Configure** node and select Analysis. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -45,4 +45,4 @@ the following pre-configured reports: | Administrator Activity Details | This report shows the details of administrator activity on file shares. | None | This report is comprised of one element:
  • Table – Provides details on last 30 days of administrator activity
| | Administrator Activity Overview | This report identifies the types of actions administrators are performing across your network. | None | This report is comprised of two elements:
  • Pie Chart – Displays last 30 days of administrator activity
  • Table – Provides details on types of actions
| | Most Active Administrators | This report ranks administrators by number of shares they have activity in. | None | This report is comprised of two elements:
  • Bar Chart – Displays last 30 days of administrator activity
  • Table – Provides details on administrator activity
| -| Suspicious Admin Activity | This report highlights all administrator reads in shares where they do not have access. | GDPR SOX HIPAA PCI-DSS GLBA ITAR FERPA FISMA ISO27001 | This report is comprised of one element:
  • Table – Provides details on last 30 days of administrator activity
| +| Suspicious Admin Activity | This report highlights all administrator reads in shares where they don't have access. | GDPR SOX HIPAA PCI-DSS GLBA ITAR FERPA FISMA ISO27001 | This report is comprised of one element:
  • Table – Provides details on last 30 days of administrator activity
| diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/activity/security/fs_highriskactivity.md b/docs/accessanalyzer/12.0/solutions/filesystem/activity/security/fs_highriskactivity.md index 9dccb9f90b..bc52c322aa 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/activity/security/fs_highriskactivity.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/activity/security/fs_highriskactivity.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * **FS_HighRiskActivity** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -37,4 +37,4 @@ produces the following pre-configured report: | Report | Description | Default Tags | Report Elements | | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| High Risk Activity | High Risk Activity is any action performed by a user who has access to a particular resource only through a High Risk Trustee (for example, Everyone, Authenticated Users, or Domain Users). Unless action is taken, these users will lose access once the open access is remediated. | GDPR SOX HIPAA PCI-DSS GLBA ITAR FERPA FISMA ISO27001 | This report is comprised of three elements:
  • Pie Chart – Displays last 30 days of activity
  • Table – Provides details on activity by user
  • Table – Provides details on activity by share
| +| High Risk Activity | High Risk Activity is any action performed by a user who has access to a particular resource only through a High Risk Trustee (for example, Everyone, Authenticated Users, or Domain Users). Unless you take action, these users lose access when you remediate the open access. | GDPR SOX HIPAA PCI-DSS GLBA ITAR FERPA FISMA ISO27001 | This report is comprised of three elements:
  • Pie Chart – Displays last 30 days of activity
  • Table – Provides details on activity by user
  • Table – Provides details on activity by share
| diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/activity/security/fs_localuseractivity.md b/docs/accessanalyzer/12.0/solutions/filesystem/activity/security/fs_localuseractivity.md index 3381209398..e6b38dc0cf 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/activity/security/fs_localuseractivity.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/activity/security/fs_localuseractivity.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * **FS_LocalUserActivity** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_deniedactivity.md b/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_deniedactivity.md index 9a8d2023a8..e08a3250ed 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_deniedactivity.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_deniedactivity.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Activity** > **FS_DeniedActivity** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_highesthourlyactivity.md b/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_highesthourlyactivity.md index 8976e492cb..b03329321f 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_highesthourlyactivity.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_highesthourlyactivity.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Activity** > **FS_HighestHourlyActivity** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_hourlyshareactivity.md b/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_hourlyshareactivity.md index 740e08aa60..31d430b9f7 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_hourlyshareactivity.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_hourlyshareactivity.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Activity** > **FS_HourlyShareActivity** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_modifiedbinaries.md b/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_modifiedbinaries.md index 4db2a8a819..745869a37e 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_modifiedbinaries.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_modifiedbinaries.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Activity** > **FS_ModifiedBinaries** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_peergroupactivity.md b/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_peergroupactivity.md index 3549087fb2..7b671ce075 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_peergroupactivity.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_peergroupactivity.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Activity** > **FS_PeerGroupActivity** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_ransomware.md b/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_ransomware.md index 39f800dbfc..2c66ad1f90 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_ransomware.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_ransomware.md @@ -6,10 +6,9 @@ sidebar_position: 60 # FS_Ransomware Job -The FS_Ransomware job is comprised of analysis and reports which use the data collected by the -**0.Collection** job group to provide information on periods of time in which users are responsible -for an abnormally high number of updates. This can be indicative of ransomware. Additionally, -activity involving files which are known as ransomware artifacts is highlighted. +The FS_Ransomware job uses the data collected by the **0.Collection** job group to identify periods +when users make an abnormally high number of updates, which can indicate ransomware. It also +highlights activity involving known ransomware artifacts. ## Analysis Tasks for the FS_Ransomeware Job @@ -17,7 +16,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Activity** > **FS_Ransomware** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_sensitivedataactivity.md b/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_sensitivedataactivity.md index 8ddbbf1334..bccc55714c 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_sensitivedataactivity.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_sensitivedataactivity.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Activity** > **FS_SensitiveDataActivity** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_stalefileactivity.md b/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_stalefileactivity.md index d5819ebad5..999d04901b 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_stalefileactivity.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_stalefileactivity.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Activity** > **FS_StaleFileActivity** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_usershareactivity.md b/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_usershareactivity.md index 27e3b48479..c57a8b973b 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_usershareactivity.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_usershareactivity.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Activity** > **FS_UserShareActivity** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_weekendactivity.md b/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_weekendactivity.md index 5d295c5ba7..b4c984eec7 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_weekendactivity.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/activity/suspiciousactivity/fs_weekendactivity.md @@ -17,7 +17,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Activity** > **FS_WeekendActivity** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/activity/usagestatistics/fs_groupusage.md b/docs/accessanalyzer/12.0/solutions/filesystem/activity/usagestatistics/fs_groupusage.md index 3d69cc9333..70d9486da7 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/activity/usagestatistics/fs_groupusage.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/activity/usagestatistics/fs_groupusage.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Statistics** > **FS_GroupUsage** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/activity/usagestatistics/fs_mostactiveservers.md b/docs/accessanalyzer/12.0/solutions/filesystem/activity/usagestatistics/fs_mostactiveservers.md index 4a195f256e..615326daa8 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/activity/usagestatistics/fs_mostactiveservers.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/activity/usagestatistics/fs_mostactiveservers.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Statistics** > **FS_MostActiveServers** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/activity/usagestatistics/fs_mostactiveusers.md b/docs/accessanalyzer/12.0/solutions/filesystem/activity/usagestatistics/fs_mostactiveusers.md index 2d26861f81..5597182f28 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/activity/usagestatistics/fs_mostactiveusers.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/activity/usagestatistics/fs_mostactiveusers.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Statistics** > **FS_MostActiveUsers** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/activity/usagestatistics/fs_staleshares.md b/docs/accessanalyzer/12.0/solutions/filesystem/activity/usagestatistics/fs_staleshares.md index b03dc71b1f..f07c944fd1 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/activity/usagestatistics/fs_staleshares.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/activity/usagestatistics/fs_staleshares.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **FileSystem** > **5.Activity** > * Statistics** > **FS_StaleShares** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/adhocaudits/fs_shareaudit.md b/docs/accessanalyzer/12.0/solutions/filesystem/adhocaudits/fs_shareaudit.md index f9e248e258..9c5d6bb905 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/adhocaudits/fs_shareaudit.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/adhocaudits/fs_shareaudit.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the FileSystem > Ad Hoc Audits > FS_Sha node and select Analysis. :::warning -Do not modify or deselect the last three selected analysis tasks. The analysis tasks +Don't modify or deselect the last three selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/adhocaudits/fs_trusteepermissions.md b/docs/accessanalyzer/12.0/solutions/filesystem/adhocaudits/fs_trusteepermissions.md index 00ce7c1bf7..61a7494561 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/adhocaudits/fs_trusteepermissions.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/adhocaudits/fs_trusteepermissions.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the FileSystem > Ad Hoc Audits > FS_Tru Configure node and select Analysis. :::warning -Do not modify or deselect the second selected analysis task. The analysis task is +Don't modify or deselect the second selected analysis task. The analysis task is preconfigured for this job. ::: @@ -38,4 +38,4 @@ produces the following pre-configured report: | Report | Description | Default Tags | Report Elements | | ------------------------- | ------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Trustee Permissions Audit | This report provides an overview of the access sprawl across the environment for the select trustee(s). | None | This report is comprised of two elements:
  • Bar Chart – Displays summary of trustees
  • Table – Provides details on trustee permissions
| +| Trustee Permissions Audit | This report provides an overview of the access sprawl across the environment for the select trustees. | None | This report is comprised of two elements:
  • Bar Chart – Displays summary of trustees
  • Table – Provides details on trustee permissions
| diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/adhocaudits/overview.md b/docs/accessanalyzer/12.0/solutions/filesystem/adhocaudits/overview.md index 1ba94793f9..262fffc3bb 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/adhocaudits/overview.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/adhocaudits/overview.md @@ -9,7 +9,7 @@ sidebar_position: 100 The Ad Hoc Audits Job Group is designed to report on resources and trustees that have been provided by the user from targeted file servers. -The Ad Hoc Audits Job Group tables and reports are blank if the CSV file is not modified to contain +The Ad Hoc Audits Job Group tables and reports are blank if the CSV file isn't modified to contain the required information before job execution. :::info diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/delete/fs_deletefiles.md b/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/delete/fs_deletefiles.md index abe42051f5..aa188068fd 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/delete/fs_deletefiles.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/delete/fs_deletefiles.md @@ -11,7 +11,7 @@ previously quarantined and can be deleted. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/12.0/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -21,7 +21,7 @@ The FS_DeleteFiles job has the following configurable parameter: - Number of days without access after which a file is a deletion candidate See the -[Customizable Analysis Tasks for the FS_DeleteFiles Job](#customizable-analysis-tasks-for-the-fs_deletefiles-job) +[Customizable Analysis Tasks for the FS_DeleteFiles Job](#customizable-analysis-tasks-for-the-fsdeletefiles-job) topic for additional information. ## Analysis Tasks for the FS_DeleteFiles Job @@ -30,7 +30,7 @@ Navigate to the **FileSystem** > **Cleanup** > **4. Delete** > **FS_DeleteFiles* node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -64,7 +64,7 @@ Navigate to the **FileSystem** > **Cleanup** > **4. Delete** > **FS_DeleteFiles* node and select **Actions** to view the action tasks. :::warning -Do not enable the action unless it is required. Disable the action after execution to +Don't enable the action unless it is required. Disable the action after execution to prevent making unintended and potentially harmful changes to Active Directory. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/delete/fs_deletefiles_status.md b/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/delete/fs_deletefiles_status.md index 706a39d97a..d13683311a 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/delete/fs_deletefiles_status.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/delete/fs_deletefiles_status.md @@ -16,7 +16,7 @@ Navigate to the **FileSystem** > **Cleanup** > **4. Delete** > **FS_DeleteFiles_ **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/fs_cleanupassessment.md b/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/fs_cleanupassessment.md index 5e29df3fee..0b5c4cab62 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/fs_cleanupassessment.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/fs_cleanupassessment.md @@ -35,7 +35,7 @@ have completed. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/12.0/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -49,7 +49,7 @@ The FS_CleanupAssessment job has the following configurable parameters: - Upper bound for files to be included in the FileDetails table (by LastModfied, in days) See the -[Customizable Analysis Tasks for the FS_CleanupAssessment Job](#customizable-analysis-tasks-for-the-fs_cleanupassessment-job) +[Customizable Analysis Tasks for the FS_CleanupAssessment Job](#customizable-analysis-tasks-for-the-fscleanupassessment-job) topic for additional information. ## Analysis Tasks for the FS_CleanupAssessment Job @@ -58,7 +58,7 @@ Navigate to the **FileSystem** > **Cleanup** > **1. Cleanup Assessment** > **FS_CleanupAssessment** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -73,14 +73,14 @@ The following analysis tasks are selected by default: - See the [Include Metadata Tag Information](#include-metadata-tag-information) topic for instructions on how to include metadata tag information in this table - Has 3 configurable parameters. See the - [Customizable Analysis Tasks for the FS_CleanupAssessment Job](#customizable-analysis-tasks-for-the-fs_cleanupassessment-job) + [Customizable Analysis Tasks for the FS_CleanupAssessment Job](#customizable-analysis-tasks-for-the-fscleanupassessment-job) topic for additional information. - Create file-level details table – Creates the SA_FS_CleanupAssessment_FileDetails table accessible under the job’s Results node - Has 2 configurable parameters. See the - [Customizable Analysis Tasks for the FS_CleanupAssessment Job](#customizable-analysis-tasks-for-the-fs_cleanupassessment-job) + [Customizable Analysis Tasks for the FS_CleanupAssessment Job](#customizable-analysis-tasks-for-the-fscleanupassessment-job) topic for additional information. - Summarize share-level information – Creates the SA_FS_CleanupAssessment_ShareDetails table @@ -140,7 +140,7 @@ Data Collector Wizard opens. the **Collect tags/keywords from file metadata properties** option. :::warning -Do not make changes to other wizard pages as they have been pre-configured for the +Don't make changes to other wizard pages as they have been pre-configured for the purpose of this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/fs_cleanupprogress.md b/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/fs_cleanupprogress.md index cf8ee551c5..4acaae00b8 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/fs_cleanupprogress.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/fs_cleanupprogress.md @@ -15,7 +15,7 @@ Navigate to the **FileSystem** > **Cleanup** > **FS_CleanupProgress** > **Config select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/notify/fs_notifyowners.md b/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/notify/fs_notifyowners.md index 71e9cf1cc1..d36d79f946 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/notify/fs_notifyowners.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/notify/fs_notifyowners.md @@ -16,7 +16,7 @@ Navigate to the **FileSystem** > **Cleanup** > **2. Notify** > **FS_NotifyOwners node and select **Actions** to view the action tasks. :::warning -Do not enable the action unless it is required. Disable the action after execution to +Don't enable the action unless it is required. Disable the action after execution to prevent making unintended and potentially harmful changes to Active Directory. ::: @@ -27,9 +27,9 @@ The following action task is deselected by default. - Notify Owners – Notifies share owners using SendMail module -Prior to running the FS_NotifyOwners job, it is necessary to select the **Notify Owners** task and +Before running the FS_NotifyOwners job, select the **Notify Owners** task and configure the properties for the SendMail action module. See the -[Configure the FS_NotifyOwners Action](#configure-the-fs_notifyowners-action) topic for additional +[Configure the FS_NotifyOwners Action](#configure-the-fsnotifyowners-action) topic for additional information. ### Configure the FS_NotifyOwners Action @@ -37,12 +37,12 @@ information. The recipients and the text of the email can be customized on the Properties page within the Send Mail Action Module Wizard. The [1. Cleanup Assessment > FS_CleanupAssessment Job](/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/fs_cleanupassessment.md) must be run before -the Send Mail Action Module Wizard can be opened. Follow these steps to customize the Notify Owners -action task. +the Send Mail Action Module Wizard can be opened. To customize the Notify Owners +action task: **Step 1 –** Navigate to the job’s **Configure** node and select **Actions**. -**Step 2 –** In the Action Selection view, select the desired action task and click **Action +**Step 2 –** In the Action Selection view, select the action task you want and click **Action Properties** to view the Action Properties page. **Step 3 –** Click **Configure Action** to open the Send Mail Action Module Wizard. diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/notify/fs_notifyowners_status.md b/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/notify/fs_notifyowners_status.md index 3a2c8f99b7..781c3badda 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/notify/fs_notifyowners_status.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/notify/fs_notifyowners_status.md @@ -16,7 +16,7 @@ Navigate to the **FileSystem** > **Cleanup** > **2. Notify** > **FS_NotifyOwners **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/overview.md b/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/overview.md index 6ef4d927c7..7b702a08da 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/overview.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/overview.md @@ -35,8 +35,8 @@ The Cleanup job group includes the following job groups and jobs: Many jobs in this group include one or more pre-built actions designed to apply operations to the data tables generated by the job’s analysis tasks. These actions perform the cleanup operations. By -default, the actions do not execute as part of the job group. You must select the actions you want -to run prior to execution. See the [Action Modules](/docs/accessanalyzer/12.0/admin/action/overview.md) topic for +default, the actions don't execute as part of the job group. You must select the actions you want +to run before execution. See the [Action Modules](/docs/accessanalyzer/12.0/admin/action/overview.md) topic for additional information. ## Recommended Configurations for the FS Cleanup Job Group @@ -47,7 +47,7 @@ The Cleanup job group has the following recommended configuration settings. The Cleanup job group has the following prerequisites: -- Successfully execute the **.Active Directory Inventory** job group prior to running this job group +- Successfully execute the **.Active Directory Inventory** job group before running this job group - The **File System Actions** license must be installed - Successfully execute the **FileSystem** > **0.Collection** job group with the following options enabled: @@ -64,7 +64,7 @@ dependencies. See the relevant topic for the job or job group for information ab **Target Host** -This job group does not collect data. No target host is required. +This job group doesn't collect data. No target host is required. **Schedule Frequency** diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/quarantine/fs_quarantinedata.md b/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/quarantine/fs_quarantinedata.md index e45883e953..56e2134b83 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/quarantine/fs_quarantinedata.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/quarantine/fs_quarantinedata.md @@ -14,13 +14,13 @@ Navigate to the **FileSystem** > **Cleanup** > **3. Quarantine** > **FS_Quaranti **Configure** node and select **Actions** to view the action tasks. :::warning -Do not enable the actions unless they are required. Disable the actions after execution +Don't enable the actions unless they are required. Disable the actions after execution to prevent making unintended and potentially harmful changes to Active Directory. ::: :::warning -Do not modify the action tasks. The action tasks are preconfigured for this job. +Don't modify the action tasks. The action tasks are preconfigured for this job. ::: @@ -31,5 +31,5 @@ The following action tasks are deselected by default: - Give domain user full control – Gives a specified domain user full control over stale files - Break inherited permissions – Breaks inherited permissions -Prior to running the FS_QuarantineData job, it is necessary to select the **Give domain user full +Before running the FS_QuarantineData job, select the **Give domain user full control** or **Break inherited permissions** task to perform an action. diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/quarantine/fs_quarantinedata_status.md b/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/quarantine/fs_quarantinedata_status.md index 4f641a3107..1295fb62b1 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/quarantine/fs_quarantinedata_status.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/quarantine/fs_quarantinedata_status.md @@ -15,7 +15,7 @@ Navigate to the **FileSystem** > **Cleanup** > **3. Quarantine** > **FS_Quaranti **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/quarantine/fs_restoreinheritance.md b/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/quarantine/fs_restoreinheritance.md index d2f704fdbe..d91544292a 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/quarantine/fs_restoreinheritance.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/quarantine/fs_restoreinheritance.md @@ -14,7 +14,7 @@ Navigate to the **FileSystem** > **Cleanup** > **3. Quarantine** > **FS_RestoreI **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: @@ -32,13 +32,13 @@ Navigate to the **FileSystem** > **Cleanup** > **3. Quarantine** > **FS_RestoreI **Configure** node and select **Actions** to view the action tasks. :::warning -Do not enable the action unless it is required. Disable the action after execution to +Don't enable the action unless it is required. Disable the action after execution to prevent making unintended and potentially harmful changes to Active Directory. ::: :::warning -Do not modify the action task. The action task is preconfigured for this job. +Don't modify the action task. The action task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/quarantine/fs_restoreinheritance_status.md b/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/quarantine/fs_restoreinheritance_status.md index 8af2597e1f..35e6d2f130 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/quarantine/fs_restoreinheritance_status.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/quarantine/fs_restoreinheritance_status.md @@ -16,7 +16,7 @@ Navigate to the **FileSystem** > **Cleanup** > **3. Quarantine** > tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/collection/0-create_schema.md b/docs/accessanalyzer/12.0/solutions/filesystem/collection/0-create_schema.md index 19203ed329..73da320190 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/collection/0-create_schema.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/collection/0-create_schema.md @@ -8,11 +8,11 @@ sidebar_position: 10 The 0-Create Schema job within the 0.Collection job group creates and updates the schema for the tables, views, and functions used by the rest of the File System Solution. This job needs to run -prior to the other jobs in the 0.Collection job group for both new installations and upgrades. The -job can be scheduled with any of the collections. Do not delete the job from the job tree. +before the other jobs in the 0.Collection job group for both new installations and upgrades. The +job can be scheduled with any of the collections. Don't delete the job from the job tree. :::info -This job does not need to be moved. Leave it to run as part of the 0.Collection +This job doesn't need to be moved. Leave it to run as part of the 0.Collection job group. ::: @@ -23,7 +23,7 @@ View the analysis task by navigating to the **FileSystem** > **0.Collection** > Schema** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/collection/0-fs_nasuni.md b/docs/accessanalyzer/12.0/solutions/filesystem/collection/0-fs_nasuni.md index 711d744de9..9fd5803b21 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/collection/0-fs_nasuni.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/collection/0-fs_nasuni.md @@ -6,13 +6,13 @@ sidebar_position: 30 # 0-FS_Nasuni Job -The 0-FS_Nasuni job is required in order to target Nasuni Edge Appliances. The job can be added from +The 0-FS_Nasuni job is required to target Nasuni Edge Appliances. The job can be added from the Access Analyzer Instant Job Library. See the [Instant Job Wizard](/docs/accessanalyzer/12.0/admin/jobs/instantjobs/overview.md) topic to add this instant job to the 0.Collection job group. :::warning -It is necessary to rename the job after it has been added to the 0.Collection job group +Rename the job after it has been added to the 0.Collection job group from **FS_Nasuni** to **0-FS_Nasuni**, so that it runs immediately after the 0-Create Schema job. ::: @@ -32,7 +32,7 @@ The queries for the 0-FS_Nasuni job use the PowerShell Data collector to gather volume data, and share data from the Nasuni environment. :::warning -Do not modify the queries. The queries are preconfigured for this job. +Don't modify the queries. The queries are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/collection/0-fsdfs_system_scans.md b/docs/accessanalyzer/12.0/solutions/filesystem/collection/0-fsdfs_system_scans.md index 63a62bb1fa..bc85e1b770 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/collection/0-fsdfs_system_scans.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/collection/0-fsdfs_system_scans.md @@ -6,8 +6,8 @@ sidebar_position: 20 # 0-FSDFS System Scans Job -The 0-FSDFS System Scans job enumerates a list of all root and link targets in the distributed file -system and creating a dynamic host list that will be used by the components. +The 0-FSDFS System Scans job enumerates all root and link targets in the distributed file system +and creates a dynamic host list for the components to use. ## Query for the 0-FSDFS System Scans Job @@ -15,7 +15,7 @@ The DFS System Scan Query uses the FSAA Data Collector and has been preconfigure Scan Category. :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: @@ -29,7 +29,7 @@ View the analysis tasks by navigating to the **FileSystem** > **0.Collection** > Scans** > **Configure** node and selecting **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/collection/1-fsac_system_scans.md b/docs/accessanalyzer/12.0/solutions/filesystem/collection/1-fsac_system_scans.md index 00932ab84c..3f1750dcc9 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/collection/1-fsac_system_scans.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/collection/1-fsac_system_scans.md @@ -56,7 +56,7 @@ purpose of this job. ![Applet Settings](/images/accessanalyzer/12.0/solutions/filesystem/collection/fsacappletsettings.webp) **Step 4 –** The Applet Settings page applies to the applet and proxy mode scans which you select -on the Scan Server Level Page. If employing proxy servers, see the +on the Scan Server Selection page. If employing proxy servers, see the [FSAA: Applet Settings](/docs/accessanalyzer/12.0/admin/datacollector/fsaa/appletsettings/appletsettings.md) topic for configuration instructions. diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/collection/1-seek_system_scans.md b/docs/accessanalyzer/12.0/solutions/filesystem/collection/1-seek_system_scans.md index 9aa94e6a58..b85011479c 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/collection/1-seek_system_scans.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/collection/1-seek_system_scans.md @@ -39,7 +39,7 @@ The following default configurations are commonly customized: - Set to **Store discovered sensitive data** - Set to scan typical documents -- SDD Criteria Settings page: +- SDD (Sensitive Data Discovery) Criteria Settings page: - Set to the following System Criteria: @@ -76,7 +76,7 @@ purpose of this job. ![Applet Settings](/images/accessanalyzer/12.0/solutions/filesystem/collection/fsaaseekappletsettings.webp) **Step 4 –** The Applet Settings page applies to the applet and proxy mode scans which you select -on the Scan Server Level page. If employing proxy servers, see the +on the Scan Server Selection page. If employing proxy servers, see the [FSAA: Applet Settings](/docs/accessanalyzer/12.0/admin/datacollector/fsaa/appletsettings/appletsettings.md) topic for configuration instructions. diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/collection/2-fsaa_bulk_import.md b/docs/accessanalyzer/12.0/solutions/filesystem/collection/2-fsaa_bulk_import.md index db03016aaf..538e90d7ab 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/collection/2-fsaa_bulk_import.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/collection/2-fsaa_bulk_import.md @@ -18,7 +18,7 @@ access/permission auditing Bulk import category. - Bulk import – Imports scan data into SQL Server - - Typically, this query is not modified. See the + - Typically, this query isn't modified. See the [FileSystemAccess Data Collector](/docs/accessanalyzer/12.0/admin/datacollector/fsaa/overview.md) topic for information on when this query should be modified. @@ -28,7 +28,7 @@ View the analysis tasks by navigating to the **FileSystem** > **0.Collection** > Import** > **Configure** node and selecting **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/collection/2-fsac_bulk_import.md b/docs/accessanalyzer/12.0/solutions/filesystem/collection/2-fsac_bulk_import.md index 6102576187..805cdf198a 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/collection/2-fsac_bulk_import.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/collection/2-fsac_bulk_import.md @@ -18,6 +18,6 @@ activity Bulk import category. - Bulk Import – Imports data into SQL Server - - Typically this query is not modified. See the + - Typically this query isn't modified. See the [FileSystemAccess Data Collector](/docs/accessanalyzer/12.0/admin/datacollector/fsaa/overview.md) topic for information on when this query should be modified. diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/collection/2-seek_bulk_import.md b/docs/accessanalyzer/12.0/solutions/filesystem/collection/2-seek_bulk_import.md index acf10d45ea..240238d9b3 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/collection/2-seek_bulk_import.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/collection/2-seek_bulk_import.md @@ -18,6 +18,6 @@ data Bulk import category. - Bulk Import – Imports data into SQL server - - Typically this query is not modified. See the + - Typically this query isn't modified. See the [FileSystemAccess Data Collector](/docs/accessanalyzer/12.0/admin/datacollector/fsaa/overview.md) topic for information on when this query should be modified. diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/collection/3-fsaa_exceptions.md b/docs/accessanalyzer/12.0/solutions/filesystem/collection/3-fsaa_exceptions.md index a89afa028f..8ae598bdc5 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/collection/3-fsaa_exceptions.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/collection/3-fsaa_exceptions.md @@ -6,19 +6,19 @@ sidebar_position: 100 # 3-FSAA Exceptions Job -The 3-FSAA Exceptions job does not use the FSAA Data Collector. Instead it runs analysis on the data +The 3-FSAA Exceptions job doesn't use the FSAA Data Collector. Instead it runs analysis on the data returned by the Access Auditing collection jobs to identify potential security concerns. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/12.0/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. The 3-FSAA Exceptions job has the following customizable parameter: -- Well Known high risk SIDS – Add any additional custom SIDS, but do not remove the default SIDS. +- Well Known high risk SIDS – Add any additional custom SIDS, but don't remove the default SIDS. See the [Analysis Tasks for the 3-FSAA Exceptions Job](#analysis-tasks-for-the-3-fsaa-exceptions-job) topic @@ -30,8 +30,8 @@ View the analysis tasks by navigating to the **FileSystem** > **0.Collection** > Exceptions** > **Configure** node and select **Analysis**. :::warning -Most of these analysis tasks are preconfigured and should not be modified and or -deselected. While it is possible to deselect particular tasks as specified, it is not recommended. +Most of these analysis tasks are preconfigured and shouldn't be modified and or +deselected. You can deselect particular tasks as specified, but it isn't recommended. ::: @@ -40,20 +40,20 @@ deselected. While it is possible to deselect particular tasks as specified, it i The following analysis tasks are selected by default: - Open resources – Any folders that are openly accessible through file shares. Can be deselected if - open resource information is not desired. + open resource information isn't desired. - - Well known high risk SIDS have been set in the `#SIDS` parameter. Do not remove these, but - additional custom SIDS can be added. See the + - Well known high risk SIDS have been set in the `#SIDS` parameter. Don't remove these, but you + can add additional custom SIDS. See the [Configure the Customizable Parameters in an Analysis Task](/docs/accessanalyzer/12.0/admin/jobs/job/configure/analysis/analysiscustomizableparameters.md) topic for additional information. - Disabled users – Any folders where disabled users have been granted access - - Can be deselected if disabled user information is not desired + - Can be deselected if disabled user information isn't desired -- Stale users – Any folders where stale users have been granted access. Stale users are user who +- Stale users – Any folders where stale users have been granted access. Stale users are users who have not logged in for more than 120 days. - - Can be deselected if stale user information is not desired + - Can be deselected if stale user information isn't desired - Reindex Exception IDs – Displays views within the **Results** node of the Access Analyzer Console diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/collection/3-fsac_exceptions.md b/docs/accessanalyzer/12.0/solutions/filesystem/collection/3-fsac_exceptions.md index ca565fdf69..d759131f84 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/collection/3-fsac_exceptions.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/collection/3-fsac_exceptions.md @@ -10,7 +10,7 @@ The 3-FSAC Exceptions job is designed to analyze collected access information fo ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/12.0/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -25,7 +25,7 @@ View the analysis tasks by navigating to the **FileSystem** > **0.Collection** > Exceptions** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -44,7 +44,7 @@ The following analysis tasks are selected by default: - Ransomware – Spikes in updates by user - Unusual user stale data activity – Spikes in stale data activity by user -While it is possible to deselect particular tasks as specified, it is not recommended. The following +You can deselect particular tasks as specified, but it isn't recommended. The following analysis tasks are deselected by default: - Show view – Displays the SA_FSAC_ExceptionsView within the Results node of the Access Analyzer @@ -54,7 +54,7 @@ analysis tasks are deselected by default: ### Customizable Analysis Tasks for the 3-FSAC Exceptions Job -Customizable parameters enable users to set the values used for classification during the job’s +Use customizable parameters to set the values used for classification during the job’s analysis. The 3-FSAC Exceptions job contains the following customizable parameters: | Analysis Task | Customizable Parameter Name | Default Value | Value Indicates | diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/collection/fs_azuretenantscan.md b/docs/accessanalyzer/12.0/solutions/filesystem/collection/fs_azuretenantscan.md index 917690bd99..398af9af42 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/collection/fs_azuretenantscan.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/collection/fs_azuretenantscan.md @@ -13,7 +13,7 @@ Files scans. You can add this job from the Access Analyzer Instant Job Library. See the [Instant Job Wizard](/docs/accessanalyzer/12.0/admin/jobs/instantjobs/overview.md) topic for additional information. -Before running the FS_AzureTenantScan job, you must ensure all the below prerequisites have been +Before running the FS_AzureTenantScan job, you must ensure all the following prerequisites are met, and that the required host list and connection profile have been assigned to the job. ## Prerequisites @@ -32,12 +32,12 @@ The FS_AzureTenantScan job has the following prerequisites: - Storage Account :::note - The custom role cannot be created at the storage account level via the web UI, but + The custom role can't be created at the storage account level via the web UI, but it can be assigned here. ::: -Follow the steps to create the role assignment. +To create the role assignment: **Step 1 –** Go to [Azure Portal](https://portal.azure.com/), and select **Resource Groups** from the navigation menu. @@ -79,7 +79,7 @@ The Azure Tenant Scan query uses the FSAA Data Collector and has been preconfigu Scan and import category. :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/collection/overview.md b/docs/accessanalyzer/12.0/solutions/filesystem/collection/overview.md index 1551be934a..5464298c8a 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/collection/overview.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/collection/overview.md @@ -46,7 +46,7 @@ considerations: - A system scans job executed from a Access Analyzer Console must be followed by the corresponding bulk import job from the same Access Analyzer Console with the same version of Access Analyzer -- Two system scans processing the same information, for example two 1-FSAA System Scans jobs, cannot +- Two system scans processing the same information, for example two 1-FSAA System Scans jobs, can't be executed consecutively against the same target host. The corresponding bulk import job, for example 2-FSAA Bulk Import job, must be executed in between. @@ -54,7 +54,7 @@ The system scans job collects the data and creates a Tier-2 database, or SQLite local host, target host, or proxy host (according to the Applet Gathering Settings configured). The corresponding bulk import job gathers the information from the Tier-2 database, and pulls it into the Tier-1 database, or Access Analyzer SQL backend database, thus completing the collection -process. The collection does not include a bulk import job, as it streams the collected data +process. The collection doesn't include a bulk import job, as it streams the collected data directly into the Tier-1 database. ## File System Access Auditing @@ -72,7 +72,7 @@ The 0.Collection jobs that comprise this auditing component are: - [2-FSAA Bulk Import Job](/docs/accessanalyzer/12.0/solutions/filesystem/collection/2-fsaa_bulk_import.md) – Imports collected access information from the targeted file servers - - The 2-FSAA Bulk Import job does not need to be run when streaming is enabled + - The 2-FSAA Bulk Import job doesn't need to be run when streaming is enabled - [3-FSAA Exceptions Job](/docs/accessanalyzer/12.0/solutions/filesystem/collection/3-fsaa_exceptions.md) – Analyzes collected access information for exceptions @@ -101,7 +101,7 @@ for additional information. It is more efficient to streamline the collection jobs to those desired. Remember, it is a best practice to scope the 0.Collection job group to only include the collection components desired by disabling the undesired collection jobs. Disabling them allows the solution to run more efficiently. -It is not recommended to delete any jobs. The required collection jobs are listed for the following +It isn't recommended to delete any jobs. The required collection jobs are listed for the following workflow. **Workflow (for Access Auditing only)** @@ -112,9 +112,9 @@ The recommended workflow for Access Auditing only is as follows: **Step 2 –** If necessary, run the **2-FSAA Bulk Import** job: -- If streaming is not enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** +- If streaming isn't enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** job. -- If streaming is enabled in the **1-FSAA System Scans** job, do not run **2-FSAA Bulk Import** job. +- If streaming is enabled in the **1-FSAA System Scans** job, don't run **2-FSAA Bulk Import** job. :::info It is best practice to disable undesired Bulk Import jobs. @@ -123,10 +123,10 @@ The recommended workflow for Access Auditing only is as follows: **Step 3 –** Run the **3-FSAA Exceptions** job. -**Step 4 –** Run the desired corresponding analysis and reporting sub-job groups. +**Step 4 –** Run the corresponding analysis and reporting sub-job groups you want. :::note -Please see the [Recommended Configuration for the File System Solution](/docs/accessanalyzer/12.0/solutions/filesystem/recommended.md) +See the [Recommended Configuration for the File System Solution](/docs/accessanalyzer/12.0/solutions/filesystem/recommended.md) topic before continuing with this workflow. ::: @@ -163,7 +163,8 @@ The 0.Collection jobs that comprise the DFS auditing component are: - When run successfully, the 0-FSDFS System Scans job automatically creates a dynamic host list called **DFS HOST LIST**. This is added to the Host Management node. You should assign this - **DFS HOST LIST** to other 0.Collection jobs as outlined in the recommended workflows below. + **DFS HOST LIST** to other 0.Collection jobs as outlined in the recommended workflows in this + section. The components depend on data collected by these jobs to collect within a file system using DFS mappings. @@ -171,7 +172,7 @@ mappings. It is more efficient to streamline the collection jobs to those desired. Remember, it is a best practice to scope the 0.Collection job group to only include the collection components desired by disabling the undesired collection jobs. Disabling them allows the solution to run more efficiently. -It is not recommended to delete any jobs. The required collection jobs are listed for each of the +It isn't recommended to delete any jobs. The required collection jobs are listed for each of the following optional workflows. :::warning @@ -189,9 +190,9 @@ destinations. **Step 3 –** If necessary, run the **2-FSAA Bulk Import** job (with the **DFS HOST LIST** assigned): -- If streaming is not enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** +- If streaming isn't enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** job. -- If streaming is enabled in the **1-FSAA System Scans** job, do not run **2-FSAA Bulk Import** job. +- If streaming is enabled in the **1-FSAA System Scans** job, don't run **2-FSAA Bulk Import** job. :::info It is best practice to disable undesired Bulk Import jobs. @@ -201,7 +202,7 @@ destinations. **Step 4 –** Run the **3-FSAA Exceptions** job (not specifically needed for DFS Auditing, but recommended for **0.Collection** job group). -**Step 5 –** Run the desired corresponding analysis and reporting sub-job groups. +**Step 5 –** Run the corresponding analysis and reporting sub-job groups you want. Recommended Workflow 2 (for AccessAuditing with DFS Auditing and Activity Auditing) @@ -216,9 +217,9 @@ only). **Step 5 –** If necessary, run the **2-FSAA Bulk Import** job (with the **DFS HOST LIST** assigned): -- If streaming is not enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** +- If streaming isn't enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** job. -- If streaming is enabled in the **1-FSAA System Scans** job, do not run **2-FSAA Bulk Import** job. +- If streaming is enabled in the **1-FSAA System Scans** job, don't run **2-FSAA Bulk Import** job. :::info It is best practice to disable undesired Bulk Import jobs. @@ -231,7 +232,7 @@ only). **Step 8 –** Run the **3-FSAC Exceptions** job. -**Step 9 –** Run the desired corresponding analysis and reporting sub-job groups. +**Step 9 –** Run the corresponding analysis and reporting sub-job groups you want. Recommended Workflow 3 (for AccessAuditing with DFS Auditing, Activity, and Sensitive Data Discovery Auditing) @@ -249,9 +250,9 @@ only). **Step 6 –** If necessary, run the **2-FSAA Bulk Import** job (with the **DFS HOST LIST** assigned): -- If streaming is not enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** +- If streaming isn't enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** job. -- If streaming is enabled in the **1-FSAA System Scans** job, do not run **2-FSAA Bulk Import** job. +- If streaming is enabled in the **1-FSAA System Scans** job, don't run **2-FSAA Bulk Import** job. :::info It is best practice to disable undesired Bulk Import jobs. @@ -262,9 +263,9 @@ only). **Step 8 –** If necessary, run the **2-SEEK Bulk Import** job (with the **DFS HOST LIST** assigned): -- If streaming is not enabled in the **1-SEEK System Scans** job, run the **2-SEEK Bulk Import** +- If streaming isn't enabled in the **1-SEEK System Scans** job, run the **2-SEEK Bulk Import** job. -- If streaming is enabled in the **1-SEEK System Scans** job, do not run the **2-SEEK Bulk Import** +- If streaming is enabled in the **1-SEEK System Scans** job, don't run the **2-SEEK Bulk Import** job. :::info @@ -276,10 +277,10 @@ only). **Step 10 –** Run the **3-FSAC Exceptions** job. -**Step 11 –** Run the desired corresponding analysis and reporting sub-job groups. +**Step 11 –** Run the corresponding analysis and reporting sub-job groups you want. :::note -Please see the [Recommended Configuration for the File System Solution](/docs/accessanalyzer/12.0/solutions/filesystem/recommended.md) +See the [Recommended Configuration for the File System Solution](/docs/accessanalyzer/12.0/solutions/filesystem/recommended.md) topic before continuing with these workflows. ::: @@ -305,12 +306,12 @@ for additional information. ::: -Once the Activity Monitor is installed, the monitored host configuration tells it what to monitor +After the Activity Monitor is installed, the monitored host configuration tells it what to monitor and how long to retain the activity log files. The monitoring agent writes one log per day of activity for the host. Then, the FSAA Data Collector gathers the log files to report on file system activity for the targeted host. While the Activity Monitor can be configured to create multiple -outputs, Access Analyzer can only collect one log file per host. Therefore, after the monitored host -has been configured, it is necessary to identify the log file for Access Analyzer. See the +outputs, Access Analyzer can only collect one log file per host. Therefore, after you configure the +monitored host, identify the log file for Access Analyzer. See the [Identify a Log File](#identify-a-log-file) topic for additional information. The data retention period needs to be coordinated between the Activity Monitor and Access Analyzer. @@ -355,7 +356,7 @@ for additional information. It is more efficient to streamline the collection jobs to those desired. Remember, it is a best practice to scope the 0.Collection job group to only include the collection components desired by disabling the undesired collection jobs. Disabling them allows the solution to run more efficiently. -It is not recommended to delete any jobs. The required collection jobs are listed for each of the +It isn't recommended to delete any jobs. The required collection jobs are listed for each of the following optional workflows. **Recommended Workflow 1 (for Access and Activity Auditing)** @@ -369,9 +370,9 @@ only). **Step 4 –** If necessary, run the **2-FSAA Bulk Import** job: -- If streaming is not enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** +- If streaming isn't enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** job. -- If streaming is enabled in the **1-FSAA System Scans** job, do not run **2-FSAA Bulk Import** job. +- If streaming is enabled in the **1-FSAA System Scans** job, don't run **2-FSAA Bulk Import** job. :::info It is best practice to disable undesired Bulk Import jobs. @@ -384,7 +385,7 @@ only). **Step 7 –** Run the **3-FSAC Exceptions** job. -**Step 8 –** Run the desired corresponding analysis and reporting sub-job groups. +**Step 8 –** Run the corresponding analysis and reporting sub-job groups you want. Recommended Workflow 2 (for Access, Activity, and Sensitive Data Discovery Auditing) @@ -399,9 +400,9 @@ only). **Step 5 –** If necessary, run the **2-FSAA Bulk Import** job: -- If streaming is not enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** +- If streaming isn't enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** job. -- If streaming is enabled in the **1-FSAA System Scans** job, do not run **2-FSAA Bulk Import** job. +- If streaming is enabled in the **1-FSAA System Scans** job, don't run **2-FSAA Bulk Import** job. :::info It is best practice to disable undesired Bulk Import jobs. @@ -412,9 +413,9 @@ only). **Step 7 –** If necessary, run the **2-SEEK Bulk Import** job: -- If streaming is not enabled in the **1-SEEK System Scans** job, run the **2-SEEK Bulk Import** +- If streaming isn't enabled in the **1-SEEK System Scans** job, run the **2-SEEK Bulk Import** job. -- If streaming is enabled in the **1-SEEK System Scans** job, do not run the **2-SEEK Bulk Import** +- If streaming is enabled in the **1-SEEK System Scans** job, don't run the **2-SEEK Bulk Import** job. :::info @@ -426,7 +427,7 @@ only). **Step 9 –** Run the **3-FSAC Exceptions** job. -**Step 10 –** Run the desired corresponding analysis and reporting sub-job groups. +**Step 10 –** Run the corresponding analysis and reporting sub-job groups you want. Recommended Workflow 3 (for Access, Activity, DFS, and Sensitive Data Discovery Auditing) @@ -443,9 +444,9 @@ only). **Step 6 –** If necessary, run the **2-FSAA Bulk Import** job: -- If streaming is not enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** +- If streaming isn't enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** job. -- If streaming is enabled in the **1-FSAA System Scans** job, do not run **2-FSAA Bulk Import** job. +- If streaming is enabled in the **1-FSAA System Scans** job, don't run **2-FSAA Bulk Import** job. :::info It is best practice to disable undesired Bulk Import jobs. @@ -456,9 +457,9 @@ only). **Step 8 –** If necessary, run the **2-SEEK Bulk Import** job: -- If streaming is not enabled in the **1-SEEK System Scans** job, run the **2-SEEK Bulk Import** +- If streaming isn't enabled in the **1-SEEK System Scans** job, run the **2-SEEK Bulk Import** job. -- If streaming is enabled in the **1-SEEK System Scans** job, do not run the **2-SEEK Bulk Import** +- If streaming is enabled in the **1-SEEK System Scans** job, don't run the **2-SEEK Bulk Import** job. :::info @@ -470,9 +471,9 @@ only). **Step 10 –** Run the **3-FSAC Exceptions** job. -**Step 11 –** Run the desired corresponding analysis and reporting sub-job groups. +**Step 11 –** Run the corresponding analysis and reporting sub-job groups you want. -Optional Workflow (for Activity Auditing data collection only ) +Optional Workflow (for Activity Auditing data collection only) While activity data can be collected independently, the Activity reports require the Access Auditing components. @@ -486,10 +487,10 @@ only). **Step 4 –** Run the **3-FSAC Exceptions** job. -**Step 5 –** Run the desired corresponding analysis and reporting sub-job groups. +**Step 5 –** Run the corresponding analysis and reporting sub-job groups you want. :::note -Please see the [Recommended Configuration for the File System Solution](/docs/accessanalyzer/12.0/solutions/filesystem/recommended.md) +See the [Recommended Configuration for the File System Solution](/docs/accessanalyzer/12.0/solutions/filesystem/recommended.md) topic before continuing with these workflows. ::: @@ -498,8 +499,8 @@ topic before continuing with these workflows. While the Activity Monitor can have multiple configurations per host, Access Analyzer can only read one of them. Therefore, after the Activity Monitor has been configured to monitor a host, it is -necessary to indicate when that configuration is for Access Analyzer. Follow these steps to identify -the Log file to be read by Access Analyzer. +necessary to indicate when that configuration is for Access Analyzer. To identify +the Log file to be read by Access Analyzer: **Step 1 –** Within the Activity Monitor Console on the **Monitored Hosts** tab, select the desired configuration and click **Edit**. @@ -526,7 +527,8 @@ with `SEEK`. The tables and views are prefixed with `FSDLP`. See the topic for additional information on the data collected. Customized search criteria can be created with the Criteria Editor accessible through the SDD -Criteria Settings page of the File System Access Auditor Data Collector Wizard. See the +(Sensitive Data Discovery) Criteria Settings page of the File System Access Auditor Data Collector +Wizard. See the [Configure the (SEEK) File System Scan Query](1-seek_system_scans.md#configure-the-seek-file-system-scan-query) topic for additional information. @@ -540,15 +542,14 @@ for additional information. **Option to Enable Last Access Timestamp** -The Last Access Timestamp (LAT) is disabled by default in Windows. This means the LAT does not get +The Last Access Timestamp (LAT) is disabled by default in Windows. This means the LAT doesn't get updated by any applications reading the file. As soon as the LAT feature is enabled in Windows, any attempt to read file contents updates the LAT. It stores the time of the last read operation. Since files are read during the Sensitive Data Discovery Auditing scan, when the feature is enabled -in Windows the scan causes each file's LAT to update each time the file is scanned. Therefore, there -is a feature within the job XML file which enables the scan to call a special API in order to keep -each file's LAT from updating when it's scanned. This feature can be enabled by adding -`` tag to the XML. See the [1-SEEK System Scans Job](/docs/accessanalyzer/12.0/solutions/filesystem/collection/1-seek_system_scans.md) +in Windows the scan causes each file's LAT to update each time the file is scanned. Therefore, the +job XML file includes a feature that calls a special API to keep each file's LAT from updating when +scanned. Enable this feature by adding the `` tag to the XML. See the [1-SEEK System Scans Job](/docs/accessanalyzer/12.0/solutions/filesystem/collection/1-seek_system_scans.md) topic for additional information and instructions. This feature works for all scan modes when targeting Windows machines. @@ -566,7 +567,7 @@ The 0.Collection jobs that comprise this auditing component are: - [2-SEEK Bulk Import Job](/docs/accessanalyzer/12.0/solutions/filesystem/collection/2-seek_bulk_import.md) – Imports collected sensitive data information from the targeted file servers - - The 2-SEEK Bulk Import job does not need to be run when streaming is enabled + - The 2-SEEK Bulk Import job doesn't need to be run when streaming is enabled The following job group and jobs in the File System solution depend on data collected by these jobs to generate reports: @@ -584,7 +585,7 @@ for additional information. It is more efficient to streamline the collection jobs to those desired. Remember, it is a best practice to scope the 0.Collection job group to only include the collection components desired by disabling the undesired collection jobs. Disabling them allows the solution to run more efficiently. -It is not recommended to delete any jobs. The required collection jobs are listed for the following +It isn't recommended to delete any jobs. The required collection jobs are listed for the following workflows. Recommended Workflow 1 (for Access and Sensitive Data Discovery Auditing data collection) @@ -601,9 +602,9 @@ the Activity Auditing components. **Step 3 –** If necessary, run the **2-FSAA Bulk Import** job: -- If streaming is not enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** +- If streaming isn't enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** job. -- If streaming is enabled in the **1-FSAA System Scans** job, do not run **2-FSAA Bulk Import** job. +- If streaming is enabled in the **1-FSAA System Scans** job, don't run **2-FSAA Bulk Import** job. :::info It is best practice to disable undesired Bulk Import jobs. @@ -612,9 +613,9 @@ the Activity Auditing components. **Step 4 –** If necessary, run the **2-SEEK Bulk Import** job: -- If streaming is not enabled in the **1-SEEK System Scans** job, run the **2-SEEK Bulk Import** +- If streaming isn't enabled in the **1-SEEK System Scans** job, run the **2-SEEK Bulk Import** job. -- If streaming is enabled in the **1-SEEK System Scans** job, do not run the **2-SEEK Bulk Import** +- If streaming is enabled in the **1-SEEK System Scans** job, don't run the **2-SEEK Bulk Import** job. :::info @@ -624,7 +625,7 @@ the Activity Auditing components. **Step 5 –** Run the **3-FSAA Exceptions** job. -**Step 6 –** Run the desired corresponding analysis and reporting sub-job groups. +**Step 6 –** Run the corresponding analysis and reporting sub-job groups you want. Recommended Workflow 2 (for Access, Activity, and Sensitive Data Discovery Auditing) @@ -639,9 +640,9 @@ only). **Step 5 –** If necessary, run the **2-FSAA Bulk Import** job: -- If streaming is not enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** +- If streaming isn't enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** job. -- If streaming is enabled in the **1-FSAA System Scans** job, do not run **2-FSAA Bulk Import** job. +- If streaming is enabled in the **1-FSAA System Scans** job, don't run **2-FSAA Bulk Import** job. :::info It is best practice to disable undesired Bulk Import jobs. @@ -652,9 +653,9 @@ only). **Step 7 –** If necessary, run the **2-SEEK Bulk Import** job: -- If streaming is not enabled in the **1-SEEK System Scans** job, run the **2-SEEK Bulk Import** +- If streaming isn't enabled in the **1-SEEK System Scans** job, run the **2-SEEK Bulk Import** job. -- If streaming is enabled in the **1-SEEK System Scans** job, do not run the **2-SEEK Bulk Import** +- If streaming is enabled in the **1-SEEK System Scans** job, don't run the **2-SEEK Bulk Import** job. :::info @@ -666,7 +667,7 @@ only). **Step 9 –** Run the **3-FSAC Exceptions** job. -**Step 10 –** Run the desired corresponding analysis and reporting sub-job groups. +**Step 10 –** Run the corresponding analysis and reporting sub-job groups you want. Recommended Workflow 3 (for Access, Activity, DFS, and Sensitive Data Discovery Auditing) @@ -683,9 +684,9 @@ only). **Step 6 –** If necessary, run the **2-FSAA Bulk Import** job: -- If streaming is not enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** +- If streaming isn't enabled in the **1-FSAA System Scans** job, run the **2-FSAA Bulk Import** job. -- If streaming is enabled in the **1-FSAA System Scans** job, do not run **2-FSAA Bulk Import** job. +- If streaming is enabled in the **1-FSAA System Scans** job, don't run **2-FSAA Bulk Import** job. :::info It is best practice to disable undesired Bulk Import jobs. @@ -696,9 +697,9 @@ only). **Step 8 –** If necessary, run the **2-SEEK Bulk Import** job: -- If streaming is not enabled in the **1-SEEK System Scans** job, run the **2-SEEK Bulk Import** +- If streaming isn't enabled in the **1-SEEK System Scans** job, run the **2-SEEK Bulk Import** job. -- If streaming is enabled in the **1-SEEK System Scans** job, do not run the **2-SEEK Bulk Import** +- If streaming is enabled in the **1-SEEK System Scans** job, don't run the **2-SEEK Bulk Import** job. :::info @@ -710,7 +711,7 @@ only). **Step 10 –** Run the **3-FSAC Exceptions** job. -**Step 11 –** Run the desired corresponding analysis and reporting sub-job groups. +**Step 11 –** Run the corresponding analysis and reporting sub-job groups you want. Optional Workflow (for Sensitive Data Discovery Auditing data collection only) @@ -721,9 +722,9 @@ Activity Auditing components. **Step 2 –** If necessary, run the **2-SEEK Bulk Import** job. -- If streaming is not enabled in the **1-SEEK System Scans** job, run the **2-SEEK Bulk Import** +- If streaming isn't enabled in the **1-SEEK System Scans** job, run the **2-SEEK Bulk Import** job. -- If streaming is enabled in the **1-SEEK System Scans** job, do not run the **2-SEEK Bulk Import** +- If streaming is enabled in the **1-SEEK System Scans** job, don't run the **2-SEEK Bulk Import** job. :::info @@ -731,10 +732,10 @@ Activity Auditing components. ::: -**Step 3 –** Run the desired corresponding analysis and reporting sub-job groups. +**Step 3 –** Run the corresponding analysis and reporting sub-job groups you want. :::note -Please see the [Recommended Configuration for the File System Solution](/docs/accessanalyzer/12.0/solutions/filesystem/recommended.md) +See the [Recommended Configuration for the File System Solution](/docs/accessanalyzer/12.0/solutions/filesystem/recommended.md) topic before continuing with these workflows. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/content/fs_filetypes.md b/docs/accessanalyzer/12.0/solutions/filesystem/content/fs_filetypes.md index f5a2296411..64f5c5f256 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/content/fs_filetypes.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/content/fs_filetypes.md @@ -18,7 +18,7 @@ View the analysis tasks by navigating to the **FileSystem** > **4.Content** > ** **FS_FileTypes** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/content/fs_stalecontent.md b/docs/accessanalyzer/12.0/solutions/filesystem/content/fs_stalecontent.md index 16cac3ed34..faa5d7aaaa 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/content/fs_stalecontent.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/content/fs_stalecontent.md @@ -19,7 +19,7 @@ View the analysis tasks by navigating to the **FileSystem** > **4.Content** > ** **FS_StaleContent** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/content/sizing/fs_emptyresources.md b/docs/accessanalyzer/12.0/solutions/filesystem/content/sizing/fs_emptyresources.md index 9b58b5f1ab..9a1106bca2 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/content/sizing/fs_emptyresources.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/content/sizing/fs_emptyresources.md @@ -14,7 +14,7 @@ View the analysis tasks by navigating to the **FileSystem** > **4.Content** > ** **FS_EmptyResources** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/content/sizing/fs_largestresources.md b/docs/accessanalyzer/12.0/solutions/filesystem/content/sizing/fs_largestresources.md index 9af5fa6c4c..8cb8044b7e 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/content/sizing/fs_largestresources.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/content/sizing/fs_largestresources.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **4.Content** > ** **FS_LargestResources** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/content/sizing/fs_smallestresources.md b/docs/accessanalyzer/12.0/solutions/filesystem/content/sizing/fs_smallestresources.md index 2cc3b9e696..a4001be897 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/content/sizing/fs_smallestresources.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/content/sizing/fs_smallestresources.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **4.Content** > ** **FS_SmallestResources** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/content/tags/fs_aiplabels.md b/docs/accessanalyzer/12.0/solutions/filesystem/content/tags/fs_aiplabels.md index 0d55c7e93d..44bd5f22fc 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/content/tags/fs_aiplabels.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/content/tags/fs_aiplabels.md @@ -6,8 +6,8 @@ sidebar_position: 10 # FS_AIPLabels Job -The FS_AIPLabels job is designed to report on resources classified by AIP labels from targeted file -servers. +The FS_AIPLabels job is designed to report on resources classified by Azure Information Protection +(AIP) labels from targeted file servers. ## Analysis Tasks for the FS_AIPLabels Job @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **4.Content** > ** **FS_AIPLabels** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/content/tags/fs_filetags.md b/docs/accessanalyzer/12.0/solutions/filesystem/content/tags/fs_filetags.md index 1d0e190d1d..98dbce0528 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/content/tags/fs_filetags.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/content/tags/fs_filetags.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **4.Content** > ** **FS_FileTags** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_domainuseracls.md b/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_domainuseracls.md index 34ca01c872..7b6cfcc6b4 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_domainuseracls.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_domainuseracls.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **2.Direct Permiss **FS_DomainUserACLs** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -34,8 +34,8 @@ The following analysis tasks are selected by default: - **4. Direct Resources** – Creates an interim processing table in the database for use by downstream analysis and report generation -In addition to the tables and views created by the analysis tasks which displays all direct user -permissions, the FS_DomainUserACLs job produces the following pre-configured report: +The tables and views created by the analysis tasks display all direct user permissions. In +addition, the FS_DomainUserACLs job produces the following pre-configured report: | Report | Description | Default Tags | Report Elements | | ---------------- | -------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_highriskacls.md b/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_highriskacls.md index 213b0f8b35..9e3569a83c 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_highriskacls.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_highriskacls.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **2.Direct Permiss **FS_HighRiskACLs** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_localusersandgroups.md b/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_localusersandgroups.md index 9fb9d0fe4b..6676cbef3e 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_localusersandgroups.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_localusersandgroups.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **2.Direct Permiss **FS_LocalUsersAndGroups** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_missingfullcontrol.md b/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_missingfullcontrol.md index c127695be8..106fba31a3 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_missingfullcontrol.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_missingfullcontrol.md @@ -7,7 +7,7 @@ sidebar_position: 40 # FS_MissingFullControl Job The FS_MissingFullControl job is designed to report on resources from targeted file servers that -have no Full Control rights granted to it. +have no Full Control rights granted to them. ## Analysis Tasks for the FS_MissingFullControl Job @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **2.Direct Permiss **FS_MissingFullControl** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -34,4 +34,4 @@ produces the following pre-configured report: | Report | Description | Default Tags | Report Elements | | --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Missing Full Control Rights | This report identifies folders within the environment which currently do not have any trustee with Full Control rights, adding to administrative burden. | None | This report is comprised of three elements:
  • Bar Chart – Displays shares with missing full control rights
  • Table – Provides details on folder
  • Table – Provides details on shares with missing full control rights
| +| Missing Full Control Rights | This report identifies folders within the environment which don't have any trustee with Full Control rights, adding to administrative burden. | None | This report is comprised of three elements:
  • Bar Chart – Displays shares with missing full control rights
  • Table – Provides details on folder
  • Table – Provides details on shares with missing full control rights
| diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_nestedshares.md b/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_nestedshares.md index c0700f5e1f..89455136d1 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_nestedshares.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_nestedshares.md @@ -6,7 +6,7 @@ sidebar_position: 50 # FS_NestedShares Job -The FS_NestedShares job is is designed to report on nested shares that have been granted direct +The FS_NestedShares job is designed to report on nested shares that have been granted direct permissions from targeted file servers. ## Analysis Tasks for the FS_NestedShares Job @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **2.Direct Permiss **FS_NestedShares** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_sidhistory.md b/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_sidhistory.md index 335b7b4794..b9d924ba21 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_sidhistory.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_sidhistory.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **2.Direct Permiss **FS_SIDHistory** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -39,4 +39,4 @@ the following pre-configured report: | Report | Description | Default Tags | Report Elements | | -------------------- | ------------------------------------------------------------------------------ | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| SID History Overview | This report identifies any applied ACE which utilizes a trustee's SID history. | None | This report is comprised of three elements:
  • Bar Chart – Displays the top 5 hosts by affected folders
  • Table – Provides details on permissions
  • Table – Provides details on trustees
| +| SID History Overview | This report identifies any applied ACE which uses a trustee's SID history. | None | This report is comprised of three elements:
  • Bar Chart – Displays the top 5 hosts by affected folders
  • Table – Provides details on permissions
  • Table – Provides details on trustees
| diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_unresolvedsids.md b/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_unresolvedsids.md index 0377993df6..cebd9cb533 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_unresolvedsids.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_unresolvedsids.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **FileSystem** > **2.Direct Permiss **FS_UnresolvedSIDs** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/overview.md b/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/overview.md index 311da511f9..4a9dbf6b68 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/overview.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/overview.md @@ -20,7 +20,7 @@ The 2.Direct Permissions job group is comprised of: - [FS_LocalUsersAndGroups Job](/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_localusersandgroups.md) – Reports on local users and groups that have been granted direct permissions on resources from targeted file servers - [FS_MissingFullControl Job](/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_missingfullcontrol.md) – Reports on resources from targeted file - servers that have no Full Control rights granted to it + servers that have no Full Control rights granted to them - [FS_NestedShares Job](/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_nestedshares.md) – Reports on nested shares that have been granted direct permissions from targeted file servers - [FS_SIDHistory Job](/docs/accessanalyzer/12.0/solutions/filesystem/directpermissions/fs_sidhistory.md) – Reports on trustees that have a historical SID that has diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/filesystemoverview.md b/docs/accessanalyzer/12.0/solutions/filesystem/filesystemoverview.md index eef311d39d..79e1759230 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/filesystemoverview.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/filesystemoverview.md @@ -9,8 +9,8 @@ sidebar_position: 130 The FileSystemOverview job provides insight into all targeted file servers. It is dependent on data collected by the [File System Access Auditing](collection/overview.md#file-system-access-auditing) components and the components of the [0.Collection Job Group](/docs/accessanalyzer/12.0/solutions/filesystem/collection/overview.md). It also -depends on the running of the sub-job groups within the solution. If only select sub-job groups have -been run, there will be blank sections in the overview report. +depends on the running of the sub-job groups within the solution. If you run only select sub-job +groups, the overview report has blank sections. ![FileSystemOverview Job in the Jobs Tree](/images/accessanalyzer/12.0/solutions/filesystem/filesystemoverviewjobstree.webp) @@ -23,7 +23,7 @@ View the analysis tasks by navigating to the **FileSystem** > **FileSystemOvervi node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/fs_brokeninheritance.md b/docs/accessanalyzer/12.0/solutions/filesystem/fs_brokeninheritance.md index 2f5fe990b6..61ae6443f4 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/fs_brokeninheritance.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/fs_brokeninheritance.md @@ -15,7 +15,7 @@ The FS_BrokenInheritance job is located in the 3.Broken Inheritance job group. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/12.0/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -29,7 +29,7 @@ The FS_BrokenInheritance job has the following configurable parameter: - 2 – Analyze all resources regardless of permission changes between parent and child See the -[Analysis Tasks for the FS_BrokenInheritance Job](#analysis-tasks-for-the-fs_brokeninheritance-job) +[Analysis Tasks for the FS_BrokenInheritance Job](#analysis-tasks-for-the-fsbrokeninheritance-job) topic for additional information. ## Analysis Tasks for the FS_BrokenInheritance Job @@ -38,7 +38,7 @@ View the analysis tasks by navigating to the **FileSystem** > **3.Broken Inherit **FS_BrokenInheritance** > **Configure** node and select **Analysis**. :::warning -Most of these analysis tasks are preconfigured and should not be modified and or +Most of these analysis tasks are preconfigured and shouldn't be modified and or deselected. There are some that are deselected by default, as they are for troubleshooting purposes. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/fs_dlpresults.md b/docs/accessanalyzer/12.0/solutions/filesystem/fs_dlpresults.md index 41555515cc..3b9f922da7 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/fs_dlpresults.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/fs_dlpresults.md @@ -21,7 +21,7 @@ View the analysis tasks by navigating to the **FileSystem** > **7.Sensitive Data **FS_DLPResults** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -54,4 +54,4 @@ the following pre-configured reports: | File Ownership (Sensitive Data Ownership) | This report identifies the top 3 potential owners of files which have been found to contain sensitive content. | None | This report is comprised of one element:
  • Table – Provides details on top owners per file
| | Sensitive Data Access | This report shows who is accessing sensitive data. Emphasis is placed on activity within the last 30 days. | GDPR SOX HIPAA PCI-DSS GLBA ITAR FERPA FISMA ISO27001 | This report is comprised of two elements:
  • Bar Chart – Displays sensitive data access by top users
  • last 30 days
  • Table – Provides details on sensitive data access
| | Sensitive Security Groups | This report identifies groups which are used to provide access to sensitive data. Changes to membership should be closely monitored. | GDPR SOX HIPAA PCI-DSS GLBA ITAR FERPA FISMA ISO27001 | This report is comprised of two elements:
  • Bar Chart – Top groups by access to sensitive files
  • Table – Provides details on group access to sensitive files
| -| Share Details (Shares with Sensitive Content) | This report identifies the location of sensitive data, and flags whether or not this data is accessible through open access. | GDPR SOX HIPAA PCI-DSS GLBA ITAR FERPA FISMA ISO27001 | This report is comprised of three elements:
  • Bar chart – Displays top shares by sensitive file count
  • Table – Provides details on files
  • Table – Provides details on top shares by sensitive file count
| +| Share Details (Shares with Sensitive Content) | This report identifies the location of sensitive data, and flags whether this data is accessible through open access. | GDPR SOX HIPAA PCI-DSS GLBA ITAR FERPA FISMA ISO27001 | This report is comprised of three elements:
  • Bar chart – Displays top shares by sensitive file count
  • Table – Provides details on files
  • Table – Provides details on top shares by sensitive file count
| diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/fs_openaccess.md b/docs/accessanalyzer/12.0/solutions/filesystem/fs_openaccess.md index d2ae30332b..9cf6af3094 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/fs_openaccess.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/fs_openaccess.md @@ -8,7 +8,7 @@ sidebar_position: 30 The FS_OpenAccess job is designed to report on Open Access information from targeted file servers. The definition of Open Access is when a security principal, such as Everyone, Authenticated Users, -or Domain Users, have permissions on a resource. +or Domain Users, has permissions on a resource. ![1.Open Access > FS_OpenAccess Job in the Jobs Tree](/images/accessanalyzer/12.0/solutions/filesystem/openaccessjobstree.webp) @@ -20,7 +20,7 @@ View the analysis tasks by navigating to the **FileSystem** > **1.Open Access** **FS_OpenAccess** > **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/fs_probableowner.md b/docs/accessanalyzer/12.0/solutions/filesystem/fs_probableowner.md index eb5387dcba..1272908bcc 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/fs_probableowner.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/fs_probableowner.md @@ -22,7 +22,7 @@ View the analysis tasks by navigating to the FileSystem > 6.Probable Owner > FS_ Configure node and select Analysis. :::warning -Do not modify or deselect the first and third selected analysis tasks. The analysis +Don't modify or deselect the first and third selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -41,8 +41,8 @@ The following analysis tasks are selected by default: `@maxlevel` parameter set to Value0. - Value0 = root share, Value1 = 1 folder deep, Value2 = 2 folders deep, etc. - Set the variable #FILTERED_TRUSTEES to a CSV file that contains one row for each SID to be - excluded. When the job is run, SIDs specified in the #FILTERED_TRUSTEES variable are excluded - from the analysis and not reported as probable owners. + excluded. When you run the job, it excludes SIDs specified in the #FILTERED_TRUSTEES variable + from the analysis and doesn't report them as probable owners. - See the [Configure the Customizable Parameters in an Analysis Task](/docs/accessanalyzer/12.0/admin/jobs/job/configure/analysis/analysiscustomizableparameters.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/fs_securityassessment.md b/docs/accessanalyzer/12.0/solutions/filesystem/fs_securityassessment.md index 7b543fe7c8..88c114eec9 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/fs_securityassessment.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/fs_securityassessment.md @@ -25,7 +25,7 @@ information from targeted file servers. It is dependent upon the following jobs: - [7.Sensitive Data > FS_DLPResults Job](/docs/accessanalyzer/12.0/solutions/filesystem/fs_dlpresults.md) -If only select sub-job groups have been run, there are blank sections in the overview report. +If you run only select sub-job groups, the overview report has blank sections. ![FS_SecurityAssessment Job in the Jobs Tree](/images/accessanalyzer/12.0/solutions/filesystem/securityassessmentjobstree.webp) @@ -38,7 +38,7 @@ View the analysis tasks by navigating to the **FileSystem** > **FS_SecurityAsses **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/overview.md b/docs/accessanalyzer/12.0/solutions/filesystem/overview.md index 9317265d84..bba0990f84 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/overview.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/overview.md @@ -12,10 +12,10 @@ identification, governance workflows including entitlement reviews and self-serv sensitive data discovery and classification, open access remediation, least-privilege access transformation, and file activity monitoring. -File systems and NAS devices contain the vast majority of an organization’s data. Each day, more -data is created and stored in the nooks and crannies of the environment, beyond the sight of the -people charged with managing it and keeping it safe. The File System Solution is designed to gather -information from file systems and shared folders in order to answer questions around data access: +File systems and NAS devices contain the vast majority of an organization’s data. Each day, +organizations create and store more data across the environment, often outside the visibility of +the people responsible for managing it and keeping it safe. The File System Solution is designed to gather +information from file systems and shared folders to answer questions around data access: - Who has access to your data? - Who is accessing your data? @@ -48,22 +48,22 @@ There is a limit of 100 file system hosts that can be scanned simultaneously. **Sensitive Data Discovery Considerations** -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the minimum amount -of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For example, if the job -is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are required (8x2=16). +If you run Sensitive Data Discovery (SDD) scans, increase the minimum amount of RAM. Each thread +requires a minimum of 2 additional GB of RAM per host. For example, if you configure the job to +scan 8 hosts at a time, it requires an extra 16 GB of RAM (8x2=16). :::note -The appropriate JDK (Java) version for Sensitive Data Discovery is installed on the -server. The JDK deployed is prepackaged and does not require any configuration; it has been -preconfigured to work with Access Analyzer and should never be customized through Java. It will not -conflict with other JDKs or Java Runtimes in the same environment. +Access Analyzer installs the appropriate JDK (Java) version for Sensitive Data Discovery on the +server. This JDK is prepackaged and doesn't require configuration. Netwrix preconfigures it to +work with Access Analyzer, so don't customize it through Java. It doesn't conflict with other JDKs +or Java Runtimes in the same environment. ::: **Location** The File System Solution requires a special Access Analyzer license. It can be installed from the -Instant Job Wizard. Once it has been installed into the Jobs tree, navigate to the solution: +Instant Job Wizard. After it's installed into the Jobs tree, navigate to the solution: **Jobs** > **FileSystem**. The [0.Collection Job Group](/docs/accessanalyzer/12.0/solutions/filesystem/collection/overview.md) collects the data. The other job groups run @@ -81,24 +81,24 @@ function. See the [Job Groups](#job-groups) topic for additional information. The File System Solution offers information on multiple aspects of an organization’s file system infrastructure. This solution is comprised of eleven job groups and an overview job which collect, -analyze, and report on data as well as run action tasks for environmental remediation. The data -collection is conducted by the FileSystemAccess (FSAA) Data Collector. See the +analyze, and report on data as well as run action tasks for environmental remediation. The +FileSystemAccess (FSAA) Data Collector conducts the data collection. See the [Standard Reference Tables & Views for the FSAA Data Collector](/docs/accessanalyzer/12.0/admin/datacollector/fsaa/standardtables.md) section for database table information. ![File System Solution](/images/accessanalyzer/12.0/solutions/filesystem/overviewpage.webp) Each type of auditing depends on specific jobs within the 0.Collection Job Group to collect the data -and its corresponding analysis and reporting job groups. The Access Auditing components represent -the core of the File System Solution and are required by the other auditing options, with the -exception of the Sensitive Data Discovery Auditing component which can be run independently. The -data collection query options for each type are explained within the 0.Collection Job Group section. -Additionally, the corresponding analysis and reporting job groups are listed for each auditing type. +and its corresponding analysis and reporting job groups. The Access Auditing components form the +core of the File System Solution. The other auditing options require them, except Sensitive Data +Discovery Auditing, which you can run independently. The data collection query options for each +type are explained within the 0.Collection Job Group section. Additionally, the corresponding +analysis and reporting job groups are listed for each auditing type. -If intending to run three or all auditing types, see each auditing type section within the +If you intend to run three or all auditing types, see each auditing type section within the 0.Collection Job Group section for information on query options and requirements. It is recommended -to first run the 0.Collection Job Group components in the default order for the desired auditing -types to ensure successful data collection, and then to run the desired sub-groups for reports. +to first run the 0.Collection Job Group components in the default order for the auditing +types you want to ensure successful data collection, and then to run the sub-groups you want for reports. See the [Recommended Configuration for the File System Solution](/docs/accessanalyzer/12.0/solutions/filesystem/recommended.md) topic for additional information on run frequency and job group settings. @@ -144,7 +144,7 @@ of the following jobs: - [FS_SecurityAssessment Job](/docs/accessanalyzer/12.0/solutions/filesystem/fs_securityassessment.md) – Designed to provide a security assessment of all relevant information from targeted file servers -When targeting Nasuni Edge Appliances, it is necessary to add a job from the Instant Job Library +When targeting Nasuni Edge Appliances, add a job from the Instant Job Library (FS_Nasuni Job) which uses the PowerShell Data collector to gather system information, volume data, and share data from the Nasuni environment. This job should be added to the 0.Collection Job Group and should be renamed (0-FS_Nasuni) to run immediately after the 0-Create Schema Job. See the diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/recommended.md b/docs/accessanalyzer/12.0/solutions/filesystem/recommended.md index 440b9af36d..3102f81789 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/recommended.md @@ -20,10 +20,9 @@ additional information. **Dependencies** -- The .Active Directory Inventory job group needs to be executed before running the File System - solution -- The .Entra ID Inventory job group needs to be executed before running the File System solution - (for targeting Azure Files only) +- Run the .Active Directory Inventory job group before you run the File System solution +- Run the .Entra ID Inventory job group before you run the File System solution (for targeting + Azure Files only) - File System Proxy deployed to targeted proxy servers (for proxy scanning architecture only) - Activity Monitor deployed, configured, and services running (for Activity Auditing only) @@ -41,8 +40,8 @@ want to scan. If you target Nasuni Edge Appliances, assign the 0-FS_Nasuni Job a custom host list containing all on-premise Nasuni Edge Appliances and cloud filers. -If using multiple proxy servers, these should also be configured within a different custom-created -host list. Then assign the proxy servers host list on the +If you use multiple proxy servers, configure them within a different custom-created host list. Then +assign the proxy servers host list on the [FSAA: Applet Settings](/docs/accessanalyzer/12.0/admin/datacollector/fsaa/appletsettings/appletsettings.md) page of the File System Access Auditor Data Collector Wizard within the following jobs in the 0.Collection Job Group according to the type of auditing being conducted: @@ -94,17 +93,17 @@ permissions for the supported target platforms. See the for the necessary permission for collecting activity data. Then create a custom Connection Profile containing the appropriate credentials for the targeted environment. -The Connection Profile should be assigned under the **FileSystem** > **0.Collection** job’s -Properties window on the **Connection** tab. It is set to Use the Default Profile, as configured at +Assign the Connection Profile under the **FileSystem** > **0.Collection** job’s Properties window, +on the **Connection** tab. It is set to Use the Default Profile, as configured at the global settings level. However, since this may not be the Connection Profile with the necessary permissions for the assigned hosts, click the radio button for the **Select one of the following user defined profiles** option and select the appropriate Connection Profile dropdown menu. :::tip -Remember, if targeting Nasuni Edge Appliances, the 0-FS_Nasuni Job needs to be assigned a custom -Connection Profile containing the **API Access Key** and **Passcode** for each on-premise Nasuni -Edge Appliance and cloud filer in the target environment. Nasuni API key names are case sensitive. -When providing them, enter them in the exact same case as generated. +Remember, if you target Nasuni Edge Appliances, assign the 0-FS_Nasuni Job a custom Connection +Profile containing the **API Access Key** and **Passcode** for each on-premise Nasuni Edge +Appliance and cloud filer in the target environment. Nasuni API key names are case sensitive. +Enter them in the exact same case as generated. ::: @@ -117,24 +116,24 @@ dependent on the size of the target environment. The FileSystem Solution can be weekly or as desired depending on the types of auditing being conducted and the scope of the target environment. -For example, it may be desired in large environments to run Activity Auditing collection jobs on a -daily basis, but to only run Access Auditing and Sensitive Data Discovery Auditing collection jobs -on a weekly basis followed by the analysis and reporting job groups. +For example, in large environments, you might want to run Activity Auditing collection jobs daily, +but run Access Auditing and Sensitive Data Discovery Auditing collection jobs only weekly, followed +by the analysis and reporting job groups. **Run Order** -Whatever schedule frequency may be configured, it is also recommended to streamline the collection +Whatever schedule frequency you configure, it is also recommended to streamline the collection jobs to those desired. The jobs in the 0.Collection Job Group must be run in order for the auditing type. Run …System Scans jobs and then the corresponding …Bulk Import jobs according to the desired workflow. -The other File System Solution sub-job groups can be run together or individually in any order, -after running the 0.Collection Job Group. The FileSystemOverview Job pulls information from both the +You can run the other File System Solution sub-job groups together or individually, in any order, +after you run the 0.Collection Job Group. The FileSystemOverview Job pulls information from both the 0.Collection Job Group and the other sub-job groups, and the report may contain blank sections if only select sub-job groups are run. :::info -If only conducting one or two types of auditing, scope the solution by disabling +If you're only conducting one or two types of auditing, scope the solution by disabling the undesired collection jobs. Disabling them allows the solution to run more efficiently. It isn't recommended to delete any jobs. See the [Disable or Enable a Job](/docs/accessanalyzer/12.0/admin/jobs/job/disableenable.md) topic for additional information. @@ -256,7 +255,7 @@ Though the analysis tasks shouldn't be deselected, the following parameters can - The .Active Directory Inventory Solution defines large groups, deeply nested groups, stale users, and users with large tokens. These parameters can be customized and are applicable to any - solution, including File System, which incorporate this analyzed data into further analysis. + solution, including File System, which incorporates this analyzed data into further analysis. - Customize within **.Active Directory Inventory** > **3-AD_Exceptions** Job analysis tasks @@ -296,7 +295,7 @@ within an analysis task. The jobs contained in the group use custom SQL scripts to render views on collected data. SQL views populate report element tables and graphs. Changing or modifying the group, job, or -table names result in no data displayed within the reports or the AIC. +table names results in no data displayed within the reports or the AIC. :::tip Remember, it is recommended to scope the 0.Collection Job Group to only include the collection diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroupaicimport.md b/docs/accessanalyzer/12.0/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroupaicimport.md index 27c5c931a0..d7add89ad7 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroupaicimport.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroupaicimport.md @@ -6,23 +6,22 @@ sidebar_position: 20 # FS_ResourceBasedGroupAICImport Job -The FS_ResorceBasedGroupsAICImport Job imports resources and access groups from the -FS_ResoureBasedGroup Job into the Netwrix Access Information Center. This job assigns ownership in -the Access Information Center and then assigns resource groups. This step is required if it is -desired to change access through entitlement reviews, self-service, or for publishing resources to -IAM. +The FS_ResourceBasedGroupsAICImport Job imports resources and access groups from the +FS_ResourceBasedGroups Job into the Netwrix Access Information Center. This job assigns ownership in +the Access Information Center and then assigns resource groups. This step is required if you want +to change access through entitlement reviews, self-service, or publishing resources to IAM. ## Recommended Configurations for the FS_ResourceBasedGroupsAICImport Job **Dependencies** -- The **FS_ResourceBasedGroups** job must be successfully run prior to running this job -- The **.Active Directory Inventory** > **1-AD_Scan** job must be successfully run prior to running +- The **FS_ResourceBasedGroups** job must be successfully run before running this job +- The **.Active Directory Inventory** > **1-AD_Scan** job must be successfully run before running this job - The **File System** > **0.Collection** > **1-FSAA System Scans** job must be successfully run - prior to running this job -- The **File System** > **0.Collection** > **2-FSAA Bulk Import** job must be successfully run prior - to running this job + before running this job +- The **File System** > **0.Collection** > **2-FSAA Bulk Import** job must be successfully run before + running this job **Targeted Hosts** @@ -51,7 +50,7 @@ Not supported **Step 2 –** Run the FS_ResourceBasedGroupsAICImport job. -- See the [Run the FS_ResourceBasedGroupsAICImportJob](#run-the-fs_resourcebasedgroupsaicimportjob) +- See the [Run the FS_ResourceBasedGroupsAICImportJob](#run-the-fsresourcebasedgroupsaicimportjob) topic for additional information **Step 3 –** Review the newly-created resource based groups in the AIC. @@ -63,11 +62,11 @@ Not supported ## Run the FS_ResourceBasedGroupsAICImportJob Now that the target environment follows a Resource Based Groups model, the new resources can be -imported into the Access Information Center. Follow the steps to import the new resources into the -AIC Ownership Workflow. +imported into the Access Information Center. To import the new resources into the +AIC Ownership Workflow: :::warning -It is important to run the .Active Directory Inventory Job Group and **File System** > +Run the .Active Directory Inventory Job Group and **File System** > **0. Collection** Job Group again so that the AD and permissions changes are captured by Access Analyzer. ::: @@ -78,8 +77,8 @@ Job Group again. **Step 2 –** Right click the **FS_ResourceBasedGroupsAICImport** job and select **Run Job**. -The newly created resource based groups are imported to the AIC. The Owner and Access Groups have -been assigned to the resources by the import process. The AIC can now be used to manage these +The newly created resource based groups are imported to the AIC. The import process assigns the +Owner and Access Groups to the resources. The AIC can now be used to manage these resources through Entitlement Reviews, Ad hoc owner changes, and the Self Service access portal. ## Review the New Resource Based Groups in the AIC diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroups.md b/docs/accessanalyzer/12.0/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroups.md index 8b4d5a76b2..446c274b21 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroups.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroups.md @@ -19,7 +19,7 @@ group implementation. **Step 3 –** (Optional) Configure a Host List for the job at the job level. :::note -If a host list is not configured, this job will analyze and commit actions on every File +If a host list isn't configured, this job will analyze and commit actions on every File System server known to Access Analyzer. To scope the actions to target specific servers, configure a host list at the job level to target only those servers. ::: @@ -31,7 +31,7 @@ host list at the job level to target only those servers. - Verify that all actions are disabled :::warning - Do not make configuration changes to the analysis tasks after reviewing and + Don't make configuration changes to the analysis tasks after reviewing and approving the Change Modeling report ::: @@ -50,7 +50,7 @@ host list at the job level to target only those servers. **Step 6 –** Execute File System actions: -- Allow an appropriate grace period for token refresh prior to executing File System action tasks, +- Allow an appropriate grace period for token refresh before executing File System action tasks, for example one week - Disable the Active Directory action tasks - Enable the File System action tasks @@ -71,14 +71,14 @@ host list at the job level to target only those servers. based groups. See the [FS_TraverseGroups Job](/docs/accessanalyzer/12.0/solutions/filesystem/resourcebasedgroups/fs_traversegroups.md) topic for additional information. -**Step 9 –** (Optional) Import resources and access groups from the FS_ResoureBasedGroup Job into +**Step 9 –** (Optional) Import resources and access groups from the FS_ResourceBasedGroups Job into the Netwrix Access Information Center. See the [FS_ResourceBasedGroupAICImport Job](/docs/accessanalyzer/12.0/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroupaicimport.md) topic for additional information. ## Model Intended Changes -Prior to executing the actions to apply changes, the proposed changes can be modeled and reviewed to +Before you execute the actions to apply changes, you can model and review the proposed changes to determine if the parameters are configured as desired. ### Configure the Analyze Group Permissions Analysis Task @@ -108,52 +108,52 @@ information. | Analyze Group Permissions | @add_admin_groups | 1 | Add full control admin groups. 1=true. 0=false. | | Analyze Group Permissions | @admin_groups | | ObjectSIDs of admin groups to add to every share if @add_admin_groups = 1 | | Analyze Group Permissions | #folders | | List of folders to assign RBG to. Overrides @levels_down. | -| Analyze Group Permissions | @activity_filter | 1000 | Filter out users with last activity older than X days ago. Will filter out users who have not accessed the folder within the specified threshold. If activity records show the user has never accessed the folder, users will still be included in resource based groups. | +| Analyze Group Permissions | @activity_filter | 1000 | Filters out users with last activity older than the specified number of days. If activity records show the user has never accessed the folder, the job still includes the user in resource based groups. | ### Execute the Analysis Tasks Execute the analysis tasks to generate the Change Modeling report and review the proposed changed -prior to executing the actions to apply the changes. +before executing the actions to apply the changes. | Report | Description | Default Tags | Report Elements | | --------------- | ---------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Change Modeling | This report shows proposed changes of access for the targeted folders. | None | This report is comprised of three elements:
  • Pie Chart – Displays a proposed access changes summary
  • Table – Provides details on proposed access changes by share
  • Table – Provides details on access modification
| -The Change Modeling report should be used to gain acceptance on the following areas before -implementing the changes: +Use the Change Modeling report to gain acceptance on the following areas before implementing the +changes: - Group Naming Conventions - Cases of Changed Access Access changes occur in the following cases: -- The user is granted full access, but is not a member of the administrator group specified in the +- The user is granted full access, but isn't a member of the administrator group specified in the analysis parameters - The user is granted less access, but is a member of the administrator group specified in the analysis parameters - The user has not used access within the timeframe configured in the analysis parameters -Follow the steps to model the proposed changes. +To model the proposed changes: -**Step 1 –** Make sure all of the analysis tasks are enabled. +**Step 1 –** ensure all of the analysis tasks are enabled. :::warning -Prior to executing the analysis tasks, make sure that all action tasks are disabled. +Before executing the analysis tasks, ensure that all action tasks are disabled. The purpose at this point is only to model the intended changes. ::: -**Step 2 –** In the Configure node, select **Actions** and make sure that all of the action tasks +**Step 2 –** In the Configure node, select **Actions** and ensure that all of the action tasks are disabled. -**Step 3 –** Right click on the **Resource Based Groups** folder and select **Run Group**. This will +**Step 3 –** Right click the **Resource Based Groups** folder and select **Run Group**. This will generate the Change Modeling report. - Wait for the queued jobs to execute. **Step 4 –** In the **FS_ResourceBasedGroups** node, navigate to **Results** > **Change Modeling** -to review the proposed changes prior to executing the actions to apply the changes. +to review the proposed changes before executing the actions to apply the changes. The Change Modeling report has been created for review. Ensure the modeled changes are approved before continuing with implementing them. @@ -161,15 +161,15 @@ before continuing with implementing them. ## Configure & Execute Active Directory Action Tasks :::warning -Do not modify the analysis tasks after the Change Modeling report has been reviewed and +Don't modify the analysis tasks after the Change Modeling report has been reviewed and approved. The approved modeled changes are implemented through the execution of the action tasks. ::: The Active Directory action tasks create and populate resource based groups. The Create Groups and -Update Members action tasks must be updated to specify a Target OU for group creation prior to -enabling and executing the actions. It should also be verified that these action tasks are targeting -the same domain controller. +Update Members action tasks must be updated to specify a Target OU for group creation before +enabling and executing the actions. Also verify that these action tasks target the same domain +controller. View the action tasks by navigating to the **Jobs** > **FileSystem** > **Resourced Based Groups** > **FS_ResourceBasedGroups** > **Configure** node and select **Actions**. @@ -181,7 +181,7 @@ There are the following two Active Directory action tasks: - Create Groups – Creates resource based groups - Update Members – Adds members to the resource based groups based on permissions -It is recommended to review the tables used by the actions prior to executing the actions. The +It is recommended to review the tables used by the actions before executing the actions. The actions act upon the data within the following tables: - FS_ResourceBasedGroups_GroupsToCreate @@ -192,7 +192,7 @@ job’s Results node. The FS_ResourceBasedGroups Job will run analysis tasks aga ### Configure & Enable the Create Groups Action Task -Follow the steps to configure the Create Groups action task. +To configure the Create Groups action task: **Step 1 –** Select the action and click **Action Properties**. @@ -216,7 +216,7 @@ The Create Groups action is configured. ### Configure & Enable the Update Members Action Task -Follow the steps to configure the Create Groups action task. +To configure the Create Groups action task: **Step 1 –** Select the action task and click **Action Properties**. @@ -241,30 +241,30 @@ The Update Members action is configured. ### Execute Active Directory Action Tasks -Make sure that the File System actions are deselected and execute the Active Directory action tasks. +Ensure that the File System actions are deselected and execute the Active Directory action tasks. The Create Groups action creates the resource based groups. The Update Members action populates those groups. Enabled action tasks can be manually executed at the Actions node. Action tasks can be scheduled only at the job level. -Follow the steps to execute the AD actions. +To execute the AD actions: :::warning -Do not modify the analysis tasks after the Change Modeling report has been reviewed and +Don't modify the analysis tasks after the Change Modeling report has been reviewed and approved. The approved modeled changes are implemented through the execution of the action tasks. ::: :::info -Disable the analysis tasks. It is not necessary to collect the data again. +Disable the analysis tasks. It isn't necessary to collect the data again. ::: **Step 1 –** On the Action Selection page, enable the **Create Groups** and **Update Members** actions. -**Step 2 –** Right-click on the **Resource Based Groups** folder and select **Run Group**. +**Step 2 –** Right-click the **Resource Based Groups** folder and select **Run Group**. - Wait for the queued jobs to execute. @@ -273,13 +273,13 @@ The resource based groups are created and populated. ## Execute File System Action Tasks :::warning -Prior to executing the File System action tasks, allow a grace period, for example one +Before executing the File System action tasks, allow a grace period, for example one week. This is important for token refresh to occur as users log off and log on again. ::: The File System actions modify folder permissions and break inheritance. The Modify Permissions and -Break Inheritance actions modules do not require any configuration. +Break Inheritance actions modules don't require any configuration. View the action tasks by navigating to the **Jobs** > **FileSystem** > **Resourced Based Groups** > **FS_ResourceBasedGroups** > **Configure** node and select **Actions**. @@ -289,20 +289,20 @@ View the action tasks by navigating to the **Jobs** > **FileSystem** > **Resourc There are the following two File System action tasks: - Modify Permissions – Modifies folder permissions -- Break Inheritance – Breaks inheritance and remove all previous permissions +- Break Inheritance – Breaks inheritance and removes all previous permissions -It is recommended to review the tables used by the actions prior to executing the actions. The +It is recommended to review the tables used by the actions before executing the actions. The actions act upon the data within the following table: - FS_ResourceBasedGroups_GroupsToCreate -The actions populate the Modify Permissions and Break Inheritance tables, which can viewed under the -job’s Results node. The FS_ResourceBasedGroups Job will run analysis tasks against these tables. +The actions populate the Modify Permissions and Break Inheritance tables, which can be viewed under +the job’s Results node. The FS_ResourceBasedGroups Job will run analysis tasks against these tables. -Follow the steps to execute the FS actions. +To execute the FS actions: :::warning -Do not modify the analysis tasks after the Change Modeling report has been reviewed and +Don't modify the analysis tasks after the Change Modeling report has been reviewed and approved. The approved modeled changes are implemented through the execution of the action tasks. ::: @@ -312,7 +312,7 @@ actions. **Step 2 –** Enable the **Modify Permissions** and **Break Inheritance** actions. -**Step 3 –** Right-click on the **Resource Based Groups** folder and select **Run Group**. +**Step 3 –** Right-click the **Resource Based Groups** folder and select **Run Group**. - Wait for the queued jobs to execute. @@ -329,15 +329,15 @@ purposes. | Action History | This report shows all actions taken on each share for audit trail purposes. | None | This report is comprised of one element:
  • Table – This table provides details on the actions taken on each share
| -Follow the steps to analyze and report on action history. +To analyze and report on action history: :::warning -Disable all of the action tasks prior to generating the Action History report. +Disable all of the action tasks before generating the Action History report. ::: **Step 1 –** On the Action Selection page, disable the **Modify Permissions** and **Break -Inheritance** actions. Make sure all of the action tasks are disabled. +Inheritance** actions. Ensure all of the action tasks are disabled. **Step 2 –** On the Analysis Selection page, enable the **Create view for action status** and **Summarize Access Changes** analysis tasks. diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/resourcebasedgroups/fs_traversegroups.md b/docs/accessanalyzer/12.0/solutions/filesystem/resourcebasedgroups/fs_traversegroups.md index 760ee6d33d..2f2c8d1e0c 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/resourcebasedgroups/fs_traversegroups.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/resourcebasedgroups/fs_traversegroups.md @@ -6,10 +6,10 @@ sidebar_position: 30 # FS_TraverseGroups Job -The **FS_TraverseGroups** Job can be used to create and apply permissions for traverse groups based -on previous resource based groups. This job would be used in the case where the folder to which -resource based groups permissions are applied is not the root share folder, or at the root of the -share. This job prevents users from losing the ability to navigate through the directory structure +Use the **FS_TraverseGroups** Job to create and apply permissions for traverse groups based +on previous resource based groups. Use this job if the folder with resource based group permissions +applied isn't the root share folder, or isn't at the root of the share. This job prevents users +from losing the ability to navigate through the directory structure if the folder is nested. The FS_TraverseGroups Job must be installed from the Instant Job library. See the [Instant Job Wizard](/docs/accessanalyzer/12.0/admin/jobs/instantjobs/overview.md) topic for additional information. @@ -18,7 +18,7 @@ information. **Dependencies** -- The **FS_ResourceBasedGroups** job must be successfully run prior to running this job +- The **FS_ResourceBasedGroups** job must be successfully run before running this job **Targeted Hosts** @@ -44,7 +44,7 @@ Not supported **Step 2 –** Configure a Host List for the job at the job level. :::note -If a host list is not configured, this job will analyze and commit actions on every File +If a host list isn't configured, this job will analyze and commit actions on every File System server known to Access Analyzer. To scope the actions to target specific servers, configure a host list at the job level to target only those servers. ::: @@ -67,7 +67,7 @@ host list at the job level to target only those servers. **Step 5 –** Execute File System action task. -- Allow an appropriate grace period for token refresh prior to executing File System action task, +- Allow an appropriate grace period for token refresh before executing File System action task, for example one week - Disable the Active Directory action task - Enable the Modify Permissions action task @@ -83,7 +83,7 @@ host list at the job level to target only those servers. ## Configure & Execute Analysis Tasks -Prior to executing the action tasks, configure and execute the analysis tasks. +Before executing the action tasks, configure and execute the analysis tasks. ### Configure the Create Groups Analysis Task @@ -115,21 +115,21 @@ For instructions on configuring analysis parameters, see the ### Execute Analysis Tasks -Once the Create Groups analysis task has been configured, execute the analysis tasks. The analysis -tasks are selected by default. Follow the steps to execute the analysis tasks. +After you configure the Create Groups analysis task, execute the analysis tasks. The analysis +tasks are selected by default. To execute the analysis tasks: -**Step 1 –** Make sure all of the analysis tasks are enabled. +**Step 1 –** Ensure all of the analysis tasks are enabled. :::warning -Prior to executing the analysis tasks, make sure that all action tasks are disabled. +Before executing the analysis tasks, ensure that all action tasks are disabled. The purpose at this point is only to create the required traversal tables. ::: -**Step 2 –** In the Configure node, select **Actions** and make sure that all of the action tasks +**Step 2 –** In the Configure node, select **Actions** and ensure that all of the action tasks are disabled. -**Step 3 –** Right click on the **FS_TraverseGroups** job and select **Run Job**. This will generate +**Step 3 –** Right click the **FS_TraverseGroups** job and select **Run Job**. This will generate the Change Modeling report. - Wait for the queued jobs to execute. @@ -139,9 +139,9 @@ The analysis tasks create the required traversal tables accessible under the job ## Configure & Execute Active Directory Action Task The Active Directory action tasks create and populate resource based groups. The Create Groups -action tasks must be updated to specify a Target OU for group creation prior to enabling and -executing the actions. It should also be verified that the action tasks are targeting the same -domain controller. View the actions by navigating to the place in the Jobs tree where the Traverse +action tasks must be updated to specify a Target OU for group creation before enabling and +executing the actions. Also verify that the action tasks target the same domain controller. View +the actions by navigating to the place in the Jobs tree where the Traverse Groups job was installed from the Instant Jobs library. Then go to the **FS_TraverseGroups** > **Configure** node and select **Actions**. The Create Groups action task must be configured to specify the OU for group creation. @@ -159,7 +159,7 @@ There are the following action tasks: - Create Groups – Create groups and add resource based groups - Modify Permissions – Add list groups -It is recommended to review the tables used by the actions prior to executing the actions. For +It is recommended to review the tables used by the actions before executing the actions. For instructions on configuring action tables, see the [Configure & Enable the Create Groups Action Task](#configure--enable-the-create-groups-action-task) topic. The actions act upon the data within the following tables: @@ -172,7 +172,7 @@ tasks against these tables. ### Configure & Enable the Create Groups Action Task -Follow the steps to configure the Create Groups action task. +To configure the Create Groups action task: **Step 1 –** Select the action and click **Action Properties**. @@ -192,12 +192,12 @@ groups is the same domain controller used in the Update Members action task. ### Execute Active Directory Action Task The Create Groups action creates the resource based groups. Enabled action tasks can be manually -executed at the Actions node. Action tasks can be scheduled only at the job level. Follow the steps -to create the resource based groups. +executed at the Actions node. Action tasks can be scheduled only at the job level. To create the +resource based groups: **Step 1 –** On the Action Selection page, enable the **Create Groups** action task. -**Step 2 –** Right-click on the **FS_TraverseGroups** job and select **Run Job**. +**Step 2 –** Right-click the **FS_TraverseGroups** job and select **Run Job**. - Wait for the queued job to execute @@ -205,11 +205,11 @@ The resource based groups are created and populated. ## Execute File System Action Task -Once the Create Groups action has been executed, the Modify Permissions action can be executed. -Follow the steps to execute the action. +After you execute the Create Groups action, you can execute the Modify Permissions action. +To execute the action: :::warning -Prior to executing the File System action tasks, allow a grace period, for example one +Before executing the File System action tasks, allow a grace period, for example one week. This is important for token refresh to occur as users log off and log on again. ::: @@ -218,7 +218,7 @@ week. This is important for token refresh to occur as users log off and log on a **Step 2 –** Enable the **Modify Permissions** action task. -**Step 3 –** Right-click on the **FS_TraverseGroups** job and select Run Job. +**Step 3 –** Right-click the **FS_TraverseGroups** job and select Run Job. - Wait for the queued job to execute. @@ -227,23 +227,23 @@ with the configured permissions. All other permissions will have been removed fr ## Generate the List Traverse Group Changes Report -The Generate the List Traverse Group Changes report displays a list of changes made in the -environment by the action modules. +The List Traverse Group Changes report displays a list of changes made in the environment by the +action modules. | Report | Description | Default Tags | Report Elements | | --------------------------- | ---------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| List Traverse Group Changes | This report shows a list of changes made in the environment by the action modules. | None | This report is comprised of one elements:
  • Table – This table provides details on the changes made to the environment by the action modules
| +| List Traverse Group Changes | This report shows a list of changes made in the environment by the action modules. | None | This report is comprised of one element:
  • Table – This table provides details on the changes made to the environment by the action modules
| - Follow the steps to analyze and report on action history. +To analyze and report on action history: :::warning -Disable all of the action tasks prior to generating the List Traverse Group Changes +Disable all of the action tasks before generating the List Traverse Group Changes report. ::: -**Step 1 –** On the Action Selection page, disable the **Modify Permissions** action task. Make sure +**Step 1 –** On the Action Selection page, disable the **Modify Permissions** action task. Ensure all of the action tasks are disabled. **Step 2 –** On the Analysis Selection page, enable the **Create Groups** and both **Show Table** diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/resourcebasedgroups/overview.md b/docs/accessanalyzer/12.0/solutions/filesystem/resourcebasedgroups/overview.md index 1fa5e8565a..81490dae70 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/resourcebasedgroups/overview.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/resourcebasedgroups/overview.md @@ -14,7 +14,7 @@ inheritance. ## Prerequisites -Action modules are available with a special Access Analyzer license. In order to use the Resource +Action modules are available with a special Access Analyzer license. To use the Resource Based Groups workflow, the following Access Analyzer licensing components are required: - File System Feature @@ -22,7 +22,7 @@ Based Groups workflow, the following Access Analyzer licensing components are re - File System Actions Add-on - Active Directory Actions Add-on -The following job groups must be successfully run prior to using this workflow: +The following job groups must be successfully run before using this workflow: - .Active Directory Inventory Job Group - FileSystem > 0.Collection Job Group @@ -35,7 +35,7 @@ it can be installed from the Instant Job Wizard. ![Resource Based Groups Job Group in the Jobs Tree](/images/accessanalyzer/12.0/solutions/filesystem/resourcebasedgroups/jobstree.webp) -Once it has been installed into the Jobs tree, navigate to the solution: **Jobs** > **FileSystem** > +After it's installed into the Jobs tree, navigate to the solution: **Jobs** > **FileSystem** > **Resource Based Groups**. The FS_TraverseGroups Job and the FS_ResourceBasedGroupsAICImport Job must be installed from the @@ -51,13 +51,13 @@ based groups model. The following jobs comprise the Resource Based Groups Job Group: -- [FS_ResourceBasedGroups Job](/docs/accessanalyzer/12.0/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroups.md) – This job will transform permission on +- [FS_ResourceBasedGroups Job](/docs/accessanalyzer/12.0/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroups.md) – This job will transform permissions on specified folders to a resource based groups model -- [FS_TraverseGroups Job](/docs/accessanalyzer/12.0/solutions/filesystem/resourcebasedgroups/fs_traversegroups.md) – (Optional) This job can be used to create and +- [FS_TraverseGroups Job](/docs/accessanalyzer/12.0/solutions/filesystem/resourcebasedgroups/fs_traversegroups.md) – (Optional) Use this job to create and apply permissions for traverse groups based on previous resource based groups. The - FS_TraverseGroupsJob must be added from the Instant Job Library in order to be used. + FS_TraverseGroupsJob must be added from the Instant Job Library to be used. - [FS_ResourceBasedGroupAICImport Job](/docs/accessanalyzer/12.0/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroupaicimport.md) – (Optional) This job - imports resources and access groups from the FS_ResoureBasedGroup Job into the Netwrix Access + imports resources and access groups from the FS_ResourceBasedGroups Job into the Netwrix Access Information Center. The FS_ResourceBasedGroupsAICImport Job must be added from the Instant Job Library to be used. @@ -65,8 +65,8 @@ The following jobs comprise the Resource Based Groups Job Group: **Dependencies** -- The **.Active Directory Inventory** Job Group must be successfully run prior to running this job -- The **FileSystem** > **0.Collection** Job Group must be successfully run prior to running this job +- The **.Active Directory Inventory** Job Group must be successfully run before running this job +- The **FileSystem** > **0.Collection** Job Group must be successfully run before running this job **Targeted Hosts** @@ -87,10 +87,10 @@ Not supported ## Scheduling the Resource Based Groups Job Group -Netwrix recommends that the job be run by a scheduled task with an unlimited timeout to ensure the -job will not be aborted when an interactive session is ended due to logoff (a logoff based on -inactivity is common in enterprise environments). Netwrix also recommends that the job only be -scheduled for discrete one-time runs so that results may be reviewed after each execution. See the +Netwrix recommends running the job as a scheduled task with an unlimited timeout, so the job isn't +aborted if an interactive session ends due to logoff (a logoff based on inactivity is common in +enterprise environments). Netwrix also recommends scheduling the job only for discrete one-time +runs so you can review results after each execution. See the [Schedule Jobs](/docs/accessanalyzer/12.0/admin/schedule/overview.md#schedule-jobs) topic for additional information. Throughout this document reference to executing a job refers to either manual execution or scheduled diff --git a/docs/accessanalyzer/12.0/solutions/nisinventory/nis_scan.md b/docs/accessanalyzer/12.0/solutions/nisinventory/nis_scan.md index 95dede68c0..cba6c6cf7d 100644 --- a/docs/accessanalyzer/12.0/solutions/nisinventory/nis_scan.md +++ b/docs/accessanalyzer/12.0/solutions/nisinventory/nis_scan.md @@ -27,7 +27,7 @@ This query must be modified. See the ### Configure the NIS Scan Query The NIS Scan job has been preconfigured to run with the default settings with the category of **Scan -NIS Users and Groups**. However, it is necessary to configure the targeted NIS domain. Follow the +NIS Users and Groups**. However, you must configure the targeted NIS domain. Follow the steps to set the target NIS domain and any desired customizations. **Step 1 –** Navigate to the **.NIS Inventory** > **NIS Scan** > **Configure** node and select @@ -40,7 +40,7 @@ opens. opens. :::warning -Do not make changes to other wizard pages as they have been pre-configured for the +Don't make changes to other wizard pages as they have been pre-configured for the purpose of this job. ::: @@ -48,7 +48,7 @@ purpose of this job. ![NIS Settings page](/images/activitymonitor/8.0/config/dellpowerscale/settings.webp) **Step 4 –** On the NIS Settings page, enter the **NIS Domain Name** for the targeted NIS domain. -This step is required prior to running this query. See the +This step is required before running this query. See the [NIS: NIS Settings](/docs/accessanalyzer/12.0/admin/datacollector/nis/settings.md) topic for additional information. - Optional: Test the connection to the domain using the Sample NIS Server section of the page @@ -69,7 +69,7 @@ View the analysis tasks by navigating to the **.NIS Inventory** > **NIS Scan** > and select **Analysis**. :::warning -Most of these analysis tasks are preconfigured and should not be modified or +Most of these analysis tasks are preconfigured and shouldn't be modified or deselected. There is one that is deselected by default, as it is for troubleshooting purposes. ::: @@ -87,7 +87,7 @@ the database: :::warning This analysis task is for troubleshooting and cleanup only. Data will be deleted from -the database. Do not execute this task with the other analysis tasks, as that results in the +the database. Don't execute this task with the other analysis tasks, as that results in the deletion of data that was just collected. ::: @@ -113,7 +113,7 @@ task. SQL database. :::warning -Do not forget to clear the Drop NIS Tables analysis task and reselect all of the other +Don't forget to clear the Drop NIS Tables analysis task and reselect all of the other analysis tasks. ::: diff --git a/docs/accessanalyzer/12.0/solutions/nisinventory/overview.md b/docs/accessanalyzer/12.0/solutions/nisinventory/overview.md index 714000e995..7c8e0f8a52 100644 --- a/docs/accessanalyzer/12.0/solutions/nisinventory/overview.md +++ b/docs/accessanalyzer/12.0/solutions/nisinventory/overview.md @@ -28,17 +28,17 @@ when auditing NFS shares. This information can also be used in the Unix Solution **Location** The .NIS Inventory Solution is a core component of all Access Analyzer installations. It can be -installed from the Access Analyzer Instant Job Wizard.. +installed from the Access Analyzer Instant Job Wizard. ![.NIS Inventory Solution in the Jobs Tree](/images/accessanalyzer/12.0/solutions/nisinventory/jobstree.webp) -Once it has been installed into the Jobs tree, navigate to the solution: **Jobs** > **.NIS -Inventory**. This group has been named in such a way to keep it at the top of the Jobs tree. +After it's installed into the Jobs tree, navigate to the solution: **Jobs** > **.NIS +Inventory**. This group's name keeps it at the top of the Jobs tree. ## NIS Scan Job -The .NIS Inventory Solution contains a single job. This job is configured to use the NIS Data -Collector and then runs analysis on the collected data. +The .NIS Inventory Solution contains a single job. This job uses the NIS Data Collector and then +runs analysis on the collected data. ![.NIS Inventory Solution Overview page](/images/accessanalyzer/12.0/solutions/nisinventory/overviewpage.webp) diff --git a/docs/accessanalyzer/12.0/solutions/nisinventory/recommended.md b/docs/accessanalyzer/12.0/solutions/nisinventory/recommended.md index f2de10583b..9bdcace1b8 100644 --- a/docs/accessanalyzer/12.0/solutions/nisinventory/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/nisinventory/recommended.md @@ -11,11 +11,11 @@ directly or scheduled. **Dependencies** -This job group does not have dependencies. +This job group doesn't have dependencies. **Targeted Hosts** -The host list assignment should be assigned under the **.NIS Inventory** > **NIS Scan** > **Hosts** +Assign the host list under the **.NIS Inventory** > **NIS Scan** > **Hosts** node. Select the custom host list containing the NIS servers or manually add the host in the **Individual hosts** section. See the [Unix Connection Profile & Host List](/docs/accessanalyzer/12.0/admin/datacollector/nis/configurejob.md) topic for @@ -23,9 +23,9 @@ additional information. **Connection Profile** -The Connection Profile should be assigned in the **.NIS Inventory** > **NIS Scan** > **Job -Properties** window on the **Connection** tab. It is set to **Use the Default Profile**, as -configured at the global settings level. However, if this is not the Connection Profile with the +Assign the Connection Profile in the **.NIS Inventory** > **NIS Scan** > **Job +Properties** window, on the **Connection** tab. It is set to **Use the Default Profile**, as +configured at the global settings level. However, if this isn't the Connection Profile with the necessary permissions for targeting the NIS servers, select the **Select one of the following user defined profiles** option and select the appropriate Connection Profile. See the [Unix Connection Profile & Host List](/docs/accessanalyzer/12.0/admin/datacollector/nis/configurejob.md) topic for @@ -55,11 +55,11 @@ analysis task is deselected by default, as it is for troubleshooting purposes on **History Retention** -History retention is not supported and should be turned off. +History retention isn't supported and should be turned off. **Multi-console Support** -Multi-console is not supported. +Multi-console isn't supported. **Workflow** diff --git a/docs/accessanalyzer/12.0/solutions/overview.md b/docs/accessanalyzer/12.0/solutions/overview.md index de5c48350e..d273231990 100644 --- a/docs/accessanalyzer/12.0/solutions/overview.md +++ b/docs/accessanalyzer/12.0/solutions/overview.md @@ -20,10 +20,10 @@ These solutions are broken down by the top-level job group that comprises the so | .NIS Inventory | The .NIS Inventory Solution is designed to provide essential user and group membership information from a NIS domain, mapping these principals to Windows-style SIDs. This provides valuable information to the File Systems Solution when auditing NFS shares.
**Core Solution** | | Active Directory | The Active Directory Solution is designed to provide the information every administrator needs regarding Active Directory configuration, operational management, troubleshooting, analyzing effective permissions, and tracking who is making what changes within your organization.
**Requires Active Directory Licensed Feature** | | Active Directory Permissions Analyzer | The Active Directory Permissions Analyzer Solution is designed to easily and automatically determine effective permissions applied to any and all Active Directory objects, at any scope, allowing for the most authoritative view available of who has access to what in Active Directory.
**Requires Active Directory Permissions Analyzer Licensed Feature** | -| AnyID Connectors | The AnyID Connectors Solution allows you to quickly find where data for identities are stored, reducing the response time to Data Subject Access Requests (DSARs). Integration with third party repositories allows you to perform exact data matching for profiles such as employees, customers, students, or patients across any data repository. | +| AnyID Connectors | Use the AnyID Connectors Solution to quickly find where data for identities are stored, reducing the response time to Data Subject Access Requests (DSARs). Use integration with third party repositories to perform exact data matching for profiles such as employees, customers, students, or patients across any data repository. | | Amazon Web Services | Access Analyzer for AWS allows organizations to secure their data residing in Amazon Web Services (AWS) S3 platform, reducing their risk exposure through proactive, automated auditing and reporting of S3 permissions, sensitive data, and ultimately a consolidated view of user access rights across dozens of structured and unstructured data resources both on-premises and in the cloud. | -| Box | The Box solution set contains jobs to provide visibility into Box access rights, policies, configurations, activities, and more, ensuring you never lose sight or control of your critical assets residing in Box.
**Requires Box Collection Licensed Feature** | -| Databases | Access Analyzer Databases Solution Set is a comprehensive set of pre-configured audit jobs and reports that provide visibility into various aspects of supported databases.
  • Azure SQL – The Azure SQL Solution Set is a comprehensive set of pre-configured audit jobs and reports that provide visibility into various aspects of Azure SQL : Users and Roles, Sensitive Data Discovery, Object Permissions, Configuration, and User Activity.
  • Db2 – The Db2 Solution Set is a comprehensive set of pre-configured audit jobs and reports that provides visibility into various aspects of a Db2 Databases: Sensitive Data Discovery and Object Permissions.
  • Instance Discovery – The Instance Discovery Solution discovers instances on supported database servers.
  • MongoDB Solution – The MongoDB Solution automates the process of understanding where MongDB databases exist and provides an overview of the MongoDB environment in order to answer questions around data access. With visibility into every corner of MongoDB and the operating system it relies upon, organizations can proactively highlight and prioritize risks to sensitive data. Additionally, organizations can automate manual, time-consuming, and expensive processes associated with compliance, security, and operations to easily adhere to best practices that keep MongoDB Server safe and operational.
  • MySQL Solution – The MySQL Solution automates the process of understanding where SQL databases exist and provides an overview of the MySQL environment in order to answer questions around data access. With visibility into every corner of Microsoft SQL Server and the Windows operating system it relies upon, organizations can proactively highlight and prioritize risks to sensitive data. Additionally, organizations can automate manual, time-consuming, and expensive processes associated with compliance, security, and operations to easily adhere to best practices that keep SQL Server safe and operational.
  • Oracle Solution – The Oracle Solution delivers comprehensive permissions, activity, and sensitive data auditing and reporting for Oracle databases. Through the power of Access Analyzer, users can automate Oracle instance discovery, understand who has access to their Oracle databases, the level of permission they have, and who is leveraging their access privileges, identify the location of sensitive information, measure adherence to best practices, and generate workflows and reports to satisfy security, compliance, and operational requirements.
  • PostgreSQL Solution – Access Analyzer PostgreSQL Solution Set is a set of pre-configured audit jobs and reports that provides visibility into PostgreSQL Sensitive Data.
  • Redshift – Access Analyzer Redshift Solution Set is a set of pre-configured audit jobs and reports that provides visibility into Redshift Sensitive Data.
  • SQL Solution – The SQL Solution is an auditing, compliance, and governance solution for Microsoft SQL Server database. Key capabilities include effective access calculation, sensitive data discovery, security configuration assessment, and database activity monitoring.
**Requires SQL Licensed Feature** | +| Box | The Box solution set contains jobs to provide visibility into Box access rights, policies, configurations, activities, and more, so you always have visibility and control over your critical assets in Box.
**Requires Box Collection Licensed Feature** | +| Databases | Access Analyzer Databases Solution Set is a comprehensive set of pre-configured audit jobs and reports that provide visibility into various aspects of supported databases.
  • Azure SQL – The Azure SQL Solution Set is a comprehensive set of pre-configured audit jobs and reports that provide visibility into various aspects of Azure SQL : Users and Roles, Sensitive Data Discovery, Object Permissions, Configuration, and User Activity.
  • Db2 – The Db2 Solution Set is a comprehensive set of pre-configured audit jobs and reports that provides visibility into various aspects of a Db2 Databases: Sensitive Data Discovery and Object Permissions.
  • Instance Discovery – The Instance Discovery Solution discovers instances on supported database servers.
  • MongoDB Solution – The MongoDB Solution automates the process of understanding where MongDB databases exist and provides an overview of the MongoDB environment to answer questions around data access. With visibility across all of MongoDB and the operating system it relies upon, organizations can proactively highlight and prioritize risks to sensitive data. Additionally, organizations can automate manual, time-consuming, and expensive processes associated with compliance, security, and operations to easily adhere to best practices that keep MongoDB Server safe and operational.
  • MySQL Solution – The MySQL Solution automates the process of understanding where SQL databases exist and provides an overview of the MySQL environment to answer questions around data access. With visibility across all of MySQL and the operating system it relies upon, organizations can proactively highlight and prioritize risks to sensitive data. Additionally, organizations can automate manual, time-consuming, and expensive processes associated with compliance, security, and operations to adhere to best practices that keep MySQL safe and operational.
  • Oracle Solution – The Oracle Solution delivers comprehensive permissions, activity, and sensitive data auditing and reporting for Oracle databases. Using Access Analyzer, users can automate Oracle instance discovery, understand who has access to their Oracle databases, the level of permission they have, and who is leveraging their access privileges, identify the location of sensitive information, measure adherence to best practices, and generate workflows and reports to satisfy security, compliance, and operational requirements.
  • PostgreSQL Solution – Access Analyzer PostgreSQL Solution Set is a set of pre-configured audit jobs and reports that provides visibility into PostgreSQL Sensitive Data.
  • Redshift – Access Analyzer Redshift Solution Set is a set of pre-configured audit jobs and reports that provides visibility into Redshift Sensitive Data.
  • SQL Solution – The SQL Solution is an auditing, compliance, and governance solution for Microsoft SQL Server database. Key capabilities include effective access calculation, sensitive data discovery, security configuration assessment, and database activity monitoring.
**Requires SQL Licensed Feature** | | Dropbox | The Dropbox Solution is an auditing, compliance, and governance solution for Dropbox for Business. Key capabilities include effective access calculation, sensitive data discovery, file content inspection, inactive access and stale data identification, and entitlement collection for integration with Identity & Access Management (IAM) processes.
**Requires Dropbox Collection Licensed Feature** | | Entra ID | The Entra ID Solution is a comprehensive set of audit jobs and reports that provide the information regarding Microsoft Entra ID configuration, operational management, and troubleshooting. The jobs within this group help pinpoint potential areas of administrative and security concerns related to Microsoft Entra ID users and groups, including syncing with on-premises Active Directory.
**Requires Entra ID Licensed Feature** | | Exchange | The Exchange Solution provides auditing and reporting on multiple aspects of the Exchange environment to assist with identifying risk, understanding usage, and decreasing bloat. Areas of focus include Audit and Compliance, Maintenance and Cleanup, Metrics and Capacity, Operations and Health, Public Folders and Configuration Baseline.
**Requires Exchange Licensed Feature** | diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/activity/forensics/sp_deletions.md b/docs/accessanalyzer/12.0/solutions/sharepoint/activity/forensics/sp_deletions.md index 306a94931e..505141cab8 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/activity/forensics/sp_deletions.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/activity/forensics/sp_deletions.md @@ -14,7 +14,7 @@ Navigate to the **Jobs** > **SharePoint** > **7.Activity** > **Forensics** > **S **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/activity/forensics/sp_permissionchanges.md b/docs/accessanalyzer/12.0/solutions/sharepoint/activity/forensics/sp_permissionchanges.md index 73c99f3fba..d4e952ecb6 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/activity/forensics/sp_permissionchanges.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/activity/forensics/sp_permissionchanges.md @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **SharePoint** > **7.Activity** > **Forensics** > **SP_PermissionChanges** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -34,4 +34,4 @@ produces the following pre-configured report: | Report | Description | Default Tags | Report Elements | | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Permission Changes | This report identifies SharePoint permission changes based on activity events and determines whether or not that permission change is considered a high security risk. | None | This report is comprised of two elements:
  • Bar Chart – Displays permission change activity in the past seven days
  • Table – Provides permission change details
| +| Permission Changes | This report identifies SharePoint permission changes based on activity events and determines whether that permission change is considered a high security risk. | None | This report is comprised of two elements:
  • Bar Chart – Displays permission change activity in the past seven days
  • Table – Provides permission change details
| diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/activity/forensics/sp_sensitivedataactivity.md b/docs/accessanalyzer/12.0/solutions/sharepoint/activity/forensics/sp_sensitivedataactivity.md index 510f7cbfbc..f22140dbe7 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/activity/forensics/sp_sensitivedataactivity.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/activity/forensics/sp_sensitivedataactivity.md @@ -16,7 +16,7 @@ Navigate to the **Jobs** > **SharePoint** > **7.Activity** > **Forensics** > tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/activity/overview.md b/docs/accessanalyzer/12.0/solutions/sharepoint/activity/overview.md index 9ce3205f35..4a86c87801 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/activity/overview.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/activity/overview.md @@ -7,7 +7,7 @@ sidebar_position: 90 # 7.Activity Job Group The 7.Activity job group generates summary and detail reports of SharePoint activity on the -specified sites. These reports can be used for identifying file, folder, and user related activity +specified sites. Use these reports to identify file, folder, and user related activity across your SharePoint environment. ![7.Activity Job Group in the Jobs Tree](/images/accessanalyzer/12.0/solutions/sharepoint/activity/jobstree.webp) diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/activity/usagestatistics/sp_inactivesites.md b/docs/accessanalyzer/12.0/solutions/sharepoint/activity/usagestatistics/sp_inactivesites.md index 509d093d49..240d42d9ba 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/activity/usagestatistics/sp_inactivesites.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/activity/usagestatistics/sp_inactivesites.md @@ -14,7 +14,7 @@ Navigate to the **Jobs** > **SharePoint** > **7.Activity** > **Usage Statistics* **SP_InactiveSites** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/activity/usagestatistics/sp_mostactivesites.md b/docs/accessanalyzer/12.0/solutions/sharepoint/activity/usagestatistics/sp_mostactivesites.md index b803fd70f8..63b1530682 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/activity/usagestatistics/sp_mostactivesites.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/activity/usagestatistics/sp_mostactivesites.md @@ -14,7 +14,7 @@ Navigate to the **Jobs** > **SharePoint** > **7.Activity** > **Usage Statistics* **SP_MostActiveSites** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: @@ -31,4 +31,4 @@ produces the following pre-configured report: | Report | Description | Default Tags | Report Elements | | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Most Active Sites – Last 30 Days | This report identifies the top five most active sites for the past 30 days. [Reads], [Updates], [Deletes], [Permission Changes] fields reflect the number of unique operations of each type that was performed on the site for this time frame. Unique Resources Accessed, number of active user performing operations on the site, as well as whether or not the active site contains sensitive information. | None | This report is comprised of two elements:
  • Bar Chart – Displays information on most active sites by event count
  • Table – Provides details on most active sites by event count
| +| Most Active Sites – Last 30 Days | This report identifies the top five most active sites for the past 30 days. [Reads], [Updates], [Deletes], [Permission Changes] fields reflect the number of unique operations of each type that was performed on the site for this time frame. This report also shows unique resources accessed, the number of active users performing operations on the site, and whether the active site contains sensitive information. | None | This report is comprised of two elements:
  • Bar Chart – Displays information on most active sites by event count
  • Table – Provides details on most active sites by event count
| diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/activity/usagestatistics/sp_mostactiveusers.md b/docs/accessanalyzer/12.0/solutions/sharepoint/activity/usagestatistics/sp_mostactiveusers.md index 1d92404bd7..d5a717e0ac 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/activity/usagestatistics/sp_mostactiveusers.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/activity/usagestatistics/sp_mostactiveusers.md @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **SharePoint** > **7.Activity** > **Usage Statistics* **SP_MostActiveUsers** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/collection/1-spseek_systemscans.md b/docs/accessanalyzer/12.0/solutions/sharepoint/collection/1-spseek_systemscans.md index 504817891c..107aa1922b 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/collection/1-spseek_systemscans.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/collection/1-spseek_systemscans.md @@ -22,18 +22,18 @@ The query for the 1-SPSEEK SystemScans Job is: ### Configure the Query for the 1-SPSEEK_SystemScans Job The 1-SPSEEK_SystemScans Job has been preconfigured to run with the default settings using the SPAA -Data Collector category of Scan for Sensitive Content, which is not visible within the SharePoint +Data Collector category of Scan for Sensitive Content, which isn't visible within the SharePoint Access Auditor Data Collector Wizard when opened from within this job. :::warning -Users should not change scans in a way that would result in less data being returned on +Users shouldn't change scans in a way that would result in less data being returned on a subsequent scan (i.e. scanning fewer web applications, scanning fewer site collections, or a shallower depth scan). Those resources not included in a subsequent scan are marked as deleted in the Tier 2 database and subsequently removed from the Tier 1 database. ::: -Follow the steps to set any desired customizations. +To set any desired customizations: **Step 1 –** Navigate to the **Jobs** > **SharePoint** > **0.Collection** > **1-SPSEEK_SystemScans** > **Configure** node and select **Queries**. @@ -94,7 +94,7 @@ remove criteria as desired by either manually selecting criteria or using the ** for additional information. :::warning -Do not configure the options on the Results page. +Don't configure the options on the Results page. ::: diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/collection/2-spaa_systemscans.md b/docs/accessanalyzer/12.0/solutions/sharepoint/collection/2-spaa_systemscans.md index e69ac10724..026474e64d 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/collection/2-spaa_systemscans.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/collection/2-spaa_systemscans.md @@ -22,20 +22,20 @@ The query for the 2-SPAA_SystemScans Job is: ### Configure 2-SPAA_SystemScans Job The 2-SPAA_SystemScans Job has been preconfigured to run with the default settings using the SPAA -Data Collector category of Scan SharePoint Access, which is not visible within the SharePoint Access +Data Collector category of Scan SharePoint Access, which isn't visible within the SharePoint Access Auditor Data Collector Wizard when opened from within this job. :::warning -Users should not change scans in a way that would result in less data being returned on +Users shouldn't change scans in a way that would result in less data being returned on a subsequent scan (i.e. scanning fewer web applications, scanning fewer site collections, or a shallower depth scan). Those resources not included in a subsequent scan are marked as deleted in the Tier 2 database and subsequently removed from the Tier 1 database. ::: -Follow the steps to set any desired customizations. +To set any desired customizations: -**Step 1 –** Navigate to the **Jobs** > **SharePoint** > **0.Collection** > **1-SPAA_SystemScans** > +**Step 1 –** Navigate to the **Jobs** > **SharePoint** > **0.Collection** > **2-SPAA_SystemScans** > **Configure** node and select the **Queries** node. **Step 2 –** In the Query Selection view, click **Query Properties**. The Query Properties window @@ -69,7 +69,7 @@ desired and click **Next**. use the default settings unless an agent scan mode is desired. Click **Next**. :::warning -Do not configure the options on the Results page. +Don't configure the options on the Results page. ::: @@ -78,4 +78,4 @@ Do not configure the options on the Results page. **Step 9 –** On the Summary page, click **Finish** to save any setting modifications or click **Cancel** if no changes were made. Then click **OK** to close the Query Properties window. -If changes were made, the 1-SPAA_SystemScans Job has now been customized. +If changes were made, the 2-SPAA_SystemScans Job has now been customized. diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/collection/3-spac_systemscans.md b/docs/accessanalyzer/12.0/solutions/sharepoint/collection/3-spac_systemscans.md index af789c8452..38d82aac8f 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/collection/3-spac_systemscans.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/collection/3-spac_systemscans.md @@ -12,11 +12,11 @@ in each structural level in the SharePoint farm. ## Queries for the 3-SPAC_SystemScans Job The 3-SPAC_SystemScans Job has been preconfigured to run with the default settings using the SPAA -Data Collector category of Scan SharePoint Activity, which is not visible within the SharePoint +Data Collector category of Scan SharePoint Activity, which isn't visible within the SharePoint Access Auditor Data Collector Wizard when opened from within this job. :::warning -Do not modify the query. The query is preconfigured for this job. +Don't modify the query. The query is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/collection/4-spseek_bulkimport.md b/docs/accessanalyzer/12.0/solutions/sharepoint/collection/4-spseek_bulkimport.md index e10b4e1bb8..15cf135624 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/collection/4-spseek_bulkimport.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/collection/4-spseek_bulkimport.md @@ -22,7 +22,7 @@ The query for the 4-SPSEEK Bulk Import Job is: ### Configure 4-SPSEEK_BulkImport Job The 4-SPSEEK_BulkImport Job has been preconfigured to run with the default settings with the SPAA -Data Collector category of **Bulk Import Sensitive Content Scan Results**, which is not visible +Data Collector category of **Bulk Import Sensitive Content Scan Results**, which isn't visible within the SharePoint Access Auditor Data Collector Wizard when opened from within this job. Follow the steps to set any desired customizations. @@ -38,16 +38,16 @@ displays. **Step 4 –** On the [SPAA: Bulk Import Settings](/docs/accessanalyzer/12.0/admin/datacollector/spaa/bulkimportsettings.md) page, the -**Set Host Identifier** is not configured by default. Click **Next**. +**Set Host Identifier** isn't configured by default. Click **Next**. :::note -Unless SQL Server Replication is used, it should not be necessary to adjust the **Host +Unless SQL Server Replication is used, it shouldn't be necessary to adjust the **Host Identifier** seed. ::: :::warning -Do not configure the options on the Results page. +Don't configure the options on the Results page. ::: @@ -81,6 +81,6 @@ The default analysis tasks are: - **5. Create DLP views** – Creates the SA_SPDLP_MatchesView - **6. Create exceptions view** – Creates the SA_SPAA_ExceptionsView -The following analysis task is not selected by default, but can be enabled: +The following analysis task isn't selected by default, but can be enabled: - Display Match Hits – Displays the SA_SPDLP_MatchesHitsView within Access Analyzer. diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/collection/5-spaa_bulkimport.md b/docs/accessanalyzer/12.0/solutions/sharepoint/collection/5-spaa_bulkimport.md index f4e8715dfc..8afba2c6c1 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/collection/5-spaa_bulkimport.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/collection/5-spaa_bulkimport.md @@ -6,7 +6,7 @@ sidebar_position: 50 # 5-SPAA_BulkImport Job -This job is responsible for retrieving the SPAA Tier 2 database information and import it to the +This job is responsible for retrieving the SPAA Tier 2 database information and importing it to the Access Analyzer SQL database. ## Queries for the 5-SPAA_BulkImport Job @@ -22,11 +22,11 @@ The query for the 5-SPAA_BulkImport Job is: ### Configure 5-SPAA_BulkImport Job The 5-SPAA_BulkImport Job has been preconfigured to run with the default settings with the SPAA Data -Collector category of Bulk Import Access Scan Results, which is not visible within the SharePoint -Access Auditor Data Collector Wizard when opened from within this job. Follow the steps to set any -desired customizations. +Collector category of Bulk Import Access Scan Results, which isn't visible within the SharePoint +Access Auditor Data Collector Wizard when opened from within this job. To set any +desired customizations: -**Step 1 –** Navigate to the **Jobs** > **SharePoint** > **0.Collection** > **2-SPAA_BulkImport** > +**Step 1 –** Navigate to the **Jobs** > **SharePoint** > **0.Collection** > **5-SPAA_BulkImport** > **Configure** node and select the **Queries** node. **Step 2 –** In the Query Selection view, click **Query Properties**. The Query Properties window @@ -38,16 +38,16 @@ displays. **Step 4 –** On the [SPAA: Bulk Import Settings](/docs/accessanalyzer/12.0/admin/datacollector/spaa/bulkimportsettings.md) page, the -**Set Host Identifier** is not configured by default. Click **Next**. +**Set Host Identifier** isn't configured by default. Click **Next**. :::note -Unless SQL Server Replication is used, it should not be necessary to adjust the **Host +Unless SQL Server Replication is used, it shouldn't be necessary to adjust the **Host Identifier** seed. ::: :::warning -Do not configure the options on the Results page. +Don't configure the options on the Results page. ::: @@ -60,7 +60,7 @@ If changes were made, the 5-SPAA_BulkImport Job has now been customized. ## Analysis Tasks for 5-SPAA_BulkImport Job -Navigate to the **Jobs** > **SharePoint** > **0.Collection** > **2-SPAA_BulkImport** > **Configure** +Navigate to the **Jobs** > **SharePoint** > **0.Collection** > **5-SPAA_BulkImport** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/collection/6-spac_bulkimport.md b/docs/accessanalyzer/12.0/solutions/sharepoint/collection/6-spac_bulkimport.md index f8c4ab3d31..2dbd428e3c 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/collection/6-spac_bulkimport.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/collection/6-spac_bulkimport.md @@ -6,7 +6,7 @@ sidebar_position: 60 # 6-SPAC_BulkImport Job -This job is responsible for retrieving the SPAC Tier 2 database information and import it to the +This job is responsible for retrieving the SPAC Tier 2 database information and importing it to the Access Analyzer SQL database. ## Queries for the 6-SPAC_BulkImport Job @@ -22,11 +22,11 @@ The query for the 6-SPAC_BulkImport Job is: ### Configure the Query for the 6-SPAC_BulkImport Job The 6-SPAC_BulkImport Job has been preconfigured to run with the default settings with the category -of Bulk Import SharePoint Activity Scan Results, which is not visible within the SharePoint Access -Auditor Data Collector Wizard when opened from within this job. Follow the steps to set any desired -customizations. +of Bulk Import SharePoint Activity Scan Results, which isn't visible within the SharePoint Access +Auditor Data Collector Wizard when opened from within this job. To set any desired +customizations: -**Step 1 –** Navigate to the **Jobs** > **SharePoint** > **0.Collection** > **2-SPAC_BulkImport** > +**Step 1 –** Navigate to the **Jobs** > **SharePoint** > **0.Collection** > **6-SPAC_BulkImport** > **Configure** node and select **Queries**. **Step 2 –** In the Query Selection view, click **Query Properties**. The Query Properties window @@ -38,16 +38,16 @@ displays. **Step 4 –** On the [SPAA: Bulk Import Settings](/docs/accessanalyzer/12.0/admin/datacollector/spaa/bulkimportsettings.md) page, the -**Set Host Identifier** is not configured by default. Click **Next**. +**Set Host Identifier** isn't configured by default. Click **Next**. :::note -Unless SQL Server Replication is used, it should not be necessary to adjust the **Host +Unless SQL Server Replication is used, it shouldn't be necessary to adjust the **Host Identifier** seed. ::: :::warning -Do not configure the options on the Results page. +Don't configure the options on the Results page. ::: @@ -58,7 +58,7 @@ Do not configure the options on the Results page. If changes were made, the 6-SPAC_BulkImport Job has now been customized. -## Analysis Tasks for 2-SPAC_BulkImport Job +## Analysis Tasks for 6-SPAC_BulkImport Job Navigate to the **Jobs** > **SharePoint** > **0.Collection** > **6-SPAC_BulkImport** > **Configure** node and select **Analysis** to view the analysis tasks. diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/collection/7-spaa_exceptions.md b/docs/accessanalyzer/12.0/solutions/sharepoint/collection/7-spaa_exceptions.md index 9782560d31..3183178fdf 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/collection/7-spaa_exceptions.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/collection/7-spaa_exceptions.md @@ -6,12 +6,12 @@ sidebar_position: 70 # 7-SPAA_Exceptions Job -This job searches scanned data for resources that match high risk conditions and retrieving a +This job searches scanned data for resources that match high risk conditions and retrieves a summary of SharePoint exceptions per host. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to easily modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/12.0/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -27,14 +27,14 @@ The 7-SPAA_Exceptions page has the following configurable parameters: See the -[Customizable Analysis Tasks for the 7-SPAA_Exceptions Job](#customizable-analysis-tasks-for-the-7-spaa_exceptions-job) +[Customizable Analysis Tasks for the 7-SPAA_Exceptions Job](#customizable-analysis-tasks-for-the-7-spaaexceptions-job) for additional information. ## Analysis Tasks 7-SPAA_Exceptions Job -The 3-SPAA_Exceptions Job does not use the SPAA Data Collector. Instead it runs analysis on the data -returned by the 2-SPAA_BulkImport Job. View the analysis tasks by navigating to the **Jobs** > -**SharePoint** > **0.Collection** > **3-SPAA_Exceptions** > **Configure** node and select +The 7-SPAA_Exceptions Job doesn't use the SPAA Data Collector. Instead it runs analysis on the data +returned by the 5-SPAA_BulkImport Job. View the analysis tasks by navigating to the **Jobs** > +**SharePoint** > **0.Collection** > **7-SPAA_Exceptions** > **Configure** node and select **Analysis**. :::warning @@ -48,15 +48,15 @@ selected analysis tasks. The default analysis tasks are: - Open resources – Any site collections, sites, libraries, lists, or folders that are openly - accessible. Can be deselected if open resource information is not desired. + accessible. Can be deselected if open resource information isn't desired. - This analysis task contains a configurable parameter: `#opengroups` - Disabled users – Any site collections, sites, libraries, lists, or folders where disabled users - have been granted access. Can be deselected if disabled user information is not desired. + have been granted access. Can be deselected if disabled user information isn't desired. - Stale users – Any site collections, sites, libraries, lists, or folders where stale users have - been granted access. Stale users are user who have not logged in for more than 120 days. Can be - deselected if stale user information is not desired. + been granted access. Stale users are users who have not logged in for more than 120 days. Can be + deselected if stale user information isn't desired. - Unresolved SID – Matches SIDs to .Active Directory Inventory Job Group data to resolve for those users using legacy SIDS or deleted users. - Show view – Displays views within the Results node of the Access Analyzer Console. diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/collection/overview.md b/docs/accessanalyzer/12.0/solutions/sharepoint/collection/overview.md index b0a2e7f504..54711cba9a 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/collection/overview.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/collection/overview.md @@ -7,7 +7,7 @@ sidebar_position: 20 # 0.Collection Job Group The **SharePoint** > **0.Collection** Job Group is designed to collect information from SharePoint -farms using the SPAA Data Collector. The collected data is then available to other SharePoint +farms using the SharePoint Access Auditing (SPAA) Data Collector. The collected data is then available to other SharePoint Solution sub-job groups and the Access Information Center for analysis. ![0.Collection Job Group](/images/accessanalyzer/12.0/solutions/sharepoint/collection/jobstree.webp) @@ -46,21 +46,21 @@ components: [SharePoint Activity Auditing](#sharepoint-activity-auditing) topic for additional information. - SharePoint Sensitive Data Discovery Auditing (SEEK) – The SharePoint Sensitive Data Discovery Auditing (SEEK) component searches file content for sensitive data. It also collects permission - information; therefore, it does not need to be run with the SPAA component. This component employs + information; therefore, it doesn't need to be run with the SPAA component. This component employs the 1-SPSEEK_SystemScans Job, the 5-SPAA_BulkImport Job, the 4-SPSEEK_BulkImport Job, and the 7-SPAA_Exceptions Job. See the [SharePoint Sensitive Data Discovery Auditing (SEEK)](#sharepoint-sensitive-data-discovery-auditing-seek) topic for additional information. -These jobs are numbered to keep them in the necessary run order. Not all jobs need be run. See the +These jobs are numbered to keep them in the necessary run order. Not all jobs need to be run. See the appropriate auditing section for specific job relationships and recommended workflows. The relationship between system scans and bulk import jobs requires the following considerations: -- A system scans job executed from a Access Analyzer Console must be followed by the corresponding +- A system scans job executed from an Access Analyzer Console must be followed by the corresponding bulk import job from the same Access Analyzer Console with the same version of Access Analyzer - Two system scans processing the same information, for example two **2-SPAA_SystemScans** jobs, - cannot be executed consecutively against the same target host. The corresponding bulk import job, + can't be executed consecutively against the same target host. The corresponding bulk import job, for example. **5-SPAA_BulkImport**, must be executed in between. The system scans job collects the data and creates a Tier-2 database, or SQLite database, on the @@ -116,13 +116,13 @@ Runtime Details. **Step 4 –** Run desired corresponding analysis and reporting sub-job groups. -Please see the [Recommended Configuration for the SharePoint Solution](/docs/accessanalyzer/12.0/solutions/sharepoint/recommended.md) topic +see the [Recommended Configuration for the SharePoint Solution](/docs/accessanalyzer/12.0/solutions/sharepoint/recommended.md) topic before continuing with this workflow. :::info Scope the 0.Collection Job Group to only include the collection components desired by disabling the undesired collection jobs. Disabling them allows the solution to run more -efficiently. It is not recommended to delete any jobs. See the +efficiently. It isn't recommended to delete any jobs. See the [Disable or Enable a Job](/docs/accessanalyzer/12.0/admin/jobs/job/disableenable.md) topic for additional information. ::: @@ -137,9 +137,9 @@ and tables specifically incorporated into this component are prefaced with SPAC. [Standard Reference Tables & Views for the SPAA Data Collector](/docs/accessanalyzer/12.0/admin/datacollector/spaa/standardtables.md) topic for additional information on the data collected. -The Access Auditing components must be run in order to create the tables in the database for the -SPAC component to use. Either the SPAA or SEEK Scan job, run to at least a 0-level scan depth (and -the corresponding Bulk Import job) can be used to create these tables. Once an initial 0-level SPAA +The Access Auditing components must be run to create the tables in the database for the +SPAC component to use. Use either the SPAA or SEEK Scan job, run to at least a 0-level scan depth (and +the corresponding Bulk Import job), to create these tables. After an initial 0-level SPAA or SPSEEK scan job and corresponding Bulk Import have been run against a particular SharePoint On Prem farm or SharePoint Online tenant, SPAA or SPSEEK Scan jobs can be run concurrently with SPAC Scan and Bulk Import jobs as needed. @@ -174,8 +174,8 @@ for additional information. **Step 6 –** Run desired corresponding analysis and reporting sub-job groups. :::note -Once an initial 2-SPAA SystemScans job (scoped to at least 0-level depth) and the -corresponding 5-SPAA Bulk Import job have been run, then the SPAA Scans can be run concurrently with +After an initial 2-SPAA SystemScans job (scoped to at least 0-level depth) and the +corresponding 5-SPAA Bulk Import job have been run, the SPAA Scans can be run concurrently with SPAC Scans and Bulk Import jobs as desired. ::: @@ -183,9 +183,9 @@ SPAC Scans and Bulk Import jobs as desired. Recommended Workflow 2 (for Access, Sensitive Data Discovery & Activity Auditing) :::warning -The jobs must be run in the order shown. It is not possible to disable the +The jobs must be run in the order shown. It isn't possible to disable the 1-SPAA_SystemScan and 2-SPAA_BulkImport jobs and run the 0.Collection Job Group because the -remaining jobs are in the wrong order. Renaming the jobs is not an option. +remaining jobs are in the wrong order. Renaming the jobs isn't an option. ::: @@ -202,8 +202,8 @@ remaining jobs are in the wrong order. Renaming the jobs is not an option. **Step 6 –** Run desired corresponding analysis and reporting sub-job groups. :::note -Once an initial 1-SPSEEK SystemScans job (scoped to at least 0-level depth) and the -corresponding 4-SPSEEK Bulk Import job have been run, then the SPSEEK Scans jobs can be run +After an initial 1-SPSEEK SystemScans job (scoped to at least 0-level depth) and the +corresponding 4-SPSEEK Bulk Import job have been run, the SPSEEK Scans jobs can be run concurrently with the SPAC Scans and the Bulk Import jobs as desired. ::: @@ -217,7 +217,7 @@ concurrently with the SPAC Scans and the Bulk Import jobs as desired. **Step 3 –** Run desired corresponding analysis and reporting sub-job groups. :::note -Please see the [Recommended Configuration for the SharePoint Solution](/docs/accessanalyzer/12.0/solutions/sharepoint/recommended.md) +see the [Recommended Configuration for the SharePoint Solution](/docs/accessanalyzer/12.0/solutions/sharepoint/recommended.md) topic before continuing with this workflow. ::: @@ -225,7 +225,7 @@ topic before continuing with this workflow. :::info Scope the 0.Collection Job Group to only include the collection components desired by disabling the undesired collection jobs. Disabling them allows the solution to run more -efficiently. It is not recommended to delete any jobs. See the +efficiently. It isn't recommended to delete any jobs. See the [Disable or Enable a Job](/docs/accessanalyzer/12.0/admin/jobs/job/disableenable.md) topic for additional information. ::: @@ -287,9 +287,9 @@ Recommended Workflow 1 (for Access & Sensitive Data Discovery Auditing) Recommended Workflow 2 (for Access, Sensitive Data Discovery & Activity Auditing) :::warning -The jobs must be run in the order shown. It is not possible to disable the +The jobs must be run in the order shown. It isn't possible to disable the 2-SPAA_SystemScan and 5-SPAA_BulkImport jobs and run the 0.Collection Job Group because the -remaining jobs are in the wrong order. Renaming the jobs is not an option. +remaining jobs are in the wrong order. Renaming the jobs isn't an option. ::: @@ -306,14 +306,14 @@ remaining jobs are in the wrong order. Renaming the jobs is not an option. **Step 6 –** Run desired corresponding analysis and reporting sub-job groups. :::note -Once an initial 1-SPSEEK SystemScans job (scoped to at least 0-level depth) and the -corresponding 4-SPSEEK Bulk Import job have been run, then the SPSEEK Scans can be run concurrently +After an initial 1-SPSEEK SystemScans job (scoped to at least 0-level depth) and the +corresponding 4-SPSEEK Bulk Import job have been run, the SPSEEK Scans can be run concurrently with the SPAC Scans and the Bulk Import jobs as desired. ::: :::note -Please see the [Recommended Configuration for the SharePoint Solution](/docs/accessanalyzer/12.0/solutions/sharepoint/recommended.md) +see the [Recommended Configuration for the SharePoint Solution](/docs/accessanalyzer/12.0/solutions/sharepoint/recommended.md) topic before continuing with this workflow. ::: @@ -321,7 +321,7 @@ topic before continuing with this workflow. :::info Scope the 0.Collection Job Group to only include the collection components desired by disabling the undesired collection jobs. Disabling them allows the solution to run more -efficiently. It is not recommended to delete any jobs. See the +efficiently. It isn't recommended to delete any jobs. See the [Disable or Enable a Job](/docs/accessanalyzer/12.0/admin/jobs/job/disableenable.md) topic for additional information. diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/content/overview.md b/docs/accessanalyzer/12.0/solutions/sharepoint/content/overview.md index daa03e7265..8def6f4a87 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/content/overview.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/content/overview.md @@ -6,11 +6,10 @@ sidebar_position: 60 # 4.Content Job Group -This group provides insight into content stored across SharePoint farms in order to help more -efficiently manage that content. It will provide information on the content taking up the most -space, the content that has not been accessed for extended periods of time, and additional data -describing SharePoint content and the configuration of the repositories such as lists and libraries -which store that content. +This group provides insight into content stored across SharePoint farms to help more +efficiently manage that content. It will provide information about the largest content, +content that hasn't been accessed in a long time, and additional data about SharePoint content +and the configuration of repositories, such as lists and libraries, that store that content. ![4.Content Job Group in the Jobs Tree](/images/accessanalyzer/12.0/solutions/sharepoint/content/contentjobstree.webp) @@ -23,5 +22,5 @@ The 4.Content Job Group is comprised of: - [SP_StaleFiles Job](/docs/accessanalyzer/12.0/solutions/sharepoint/content/sp_stalefiles.md) – Identifies files that have been modified in at least a year across SharePoint farms. This aids administrators and users in cleaning up or archiving old and unchanged files to help maintain a clean and healthy SharePoint environment. Report includes - files, their last modified time, total file size, versions and version size, along with file owner + files, their last modified time, total file size, versions, and version size, along with file owner and file editor information. diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/content/sp_largestfiles.md b/docs/accessanalyzer/12.0/solutions/sharepoint/content/sp_largestfiles.md index b6b16f7b8b..872f09b549 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/content/sp_largestfiles.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/content/sp_largestfiles.md @@ -17,7 +17,7 @@ Navigate to the **Jobs** > **SharePoint** > **4.Content** > **SP_LargestFiles** and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/content/sp_stalefiles.md b/docs/accessanalyzer/12.0/solutions/sharepoint/content/sp_stalefiles.md index 1ea8574f7c..d03e388f1b 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/content/sp_stalefiles.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/content/sp_stalefiles.md @@ -9,12 +9,12 @@ sidebar_position: 20 The SP_StaleFiles Job identifies files that have not been modified in at least a year across SharePoint farms. This aids administrators and users in cleaning up or archiving old and unchanged files to help maintain a clean and healthy SharePoint environment. Report includes files, their last -modified time, total file size, versions and version size, along with file owner and file editor +modified time, total file size, versions, and version size, along with file owner and file editor information. ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/12.0/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -24,7 +24,7 @@ The SP_StaleFiles page has the following configurable parameters: - Days since last modification to be considered stale See the -[Customizable Analysis Tasks for the SP_StaleFiles Job](#customizable-analysis-tasks-for-the-sp_stalefiles-job) +[Customizable Analysis Tasks for the SP_StaleFiles Job](#customizable-analysis-tasks-for-the-spstalefiles-job) for additional information. ## Analysis Tasks for the SP_StaleFiles Job @@ -33,7 +33,7 @@ Navigate to the **Jobs** > **SharePoint** > **4.Content** > **SP_StaleFiles** > and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. Only the `@stale` parameter can be configured for the analysis task. ::: @@ -46,7 +46,7 @@ The default analysis task is: node - This analysis task contains a configurable parameter: `@stale`. See the - [Customizable Analysis Tasks for the SP_StaleFiles Job](#customizable-analysis-tasks-for-the-sp_stalefiles-job) + [Customizable Analysis Tasks for the SP_StaleFiles Job](#customizable-analysis-tasks-for-the-spstalefiles-job) topic for additional information. In addition to the table created by the analysis task which displays the stale file resources, the diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/overview.md b/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/overview.md index bcb6ed9433..b1efc193b8 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/overview.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/overview.md @@ -7,7 +7,7 @@ sidebar_position: 30 # 1.Direct Permissions Job Group The **SharePoint** > **1.Direct Permissions** Job Group provides insight into how directly applied -permissions are configured within the targeted SharePoint environment. It is dependent on data +permissions are configured within the targeted SharePoint environment. It depends on data collected by the [SharePoint Access Auditing](/docs/accessanalyzer/12.0/solutions/sharepoint/collection/overview.md#sharepoint-access-auditing) or [SharePoint Sensitive Data Discovery Auditing (SEEK)](/docs/accessanalyzer/12.0/solutions/sharepoint/collection/overview.md#sharepoint-sensitive-data-discovery-auditing-seek) @@ -22,14 +22,14 @@ The 1.Direct Permissions Job Group is comprised of: directly applied on permissions. Best practices dictate that groups should be used to provide access to resources. - [SP_EmptyDomainGroupPerms Job](/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/sp_emptydomaingroupperms.md) – Identifies empty security groups - with directly assigned permissions to resources, these groups should be deleted from SharePoint + with directly assigned permissions to resources. Delete these groups from SharePoint farms, where found. Inadvertent changes to group membership may open up unwanted access. - [SP_HighRiskPermissions Job](/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/sp_highriskpermissions.md) – Identifies where Authenticated Users, Everyone Except External Users, Anonymous Logon, or Domain users have been directly assigned permissions - [SP_SiteCollectionPerms Job](/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/sp_sitecollectionperms.md) – Most content will inherit the - permissions configured at the root of the site collection. Having an understanding of how those - permissions are assigned is useful for gaining perspective on the overall SharePoint permission + permissions configured at the root of the site collection. Understanding how those + permissions are assigned gives you perspective on the overall SharePoint permission configuration. - [SP_StaleUsers Job](/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/sp_staleusers.md) – Identifies locations where there are stale users directly applied on SharePoint resources. These permissions can be safely removed. diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/sp_domainusers.md b/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/sp_domainusers.md index eb0af9d7fc..cb2f69e5ab 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/sp_domainusers.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/sp_domainusers.md @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **SharePoint** > **1.Direct Permissions** > **SP_Doma **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/sp_emptydomaingroupperms.md b/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/sp_emptydomaingroupperms.md index cc7f9c7eda..2abcdc330e 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/sp_emptydomaingroupperms.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/sp_emptydomaingroupperms.md @@ -7,7 +7,7 @@ sidebar_position: 20 # SP_EmptyDomainGroupPerms Job The SP_EmptyDomainGroupPerms Job identifies empty security groups with directly assigned permissions -to resources, these groups should be deleted from SharePoint farms, where found. Inadvertent changes +to resources. Delete these groups from SharePoint farms, where found. Inadvertent changes to group membership may open up unwanted access. ## Analysis Tasks for the SP_EmptyDomainGroupPerms Job @@ -17,7 +17,7 @@ Navigate to the **Jobs** > **SharePoint** > **1.Direct Permissions** > tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/sp_highriskpermissions.md b/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/sp_highriskpermissions.md index 0f5bc1d680..16d9a50712 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/sp_highriskpermissions.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/sp_highriskpermissions.md @@ -7,7 +7,7 @@ sidebar_position: 30 # SP_HighRiskPermissions Job The SP_HighRiskPermissions Job identifies where Authenticated Users, Everyone Except External Users, -Anonymous Logon, or Domain users have been directly assigned permissions +Anonymous Logon, or Domain users have been directly assigned permissions. ## Analysis Tasks for the SP_HighRiskPermissions Job @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **SharePoint** > **1.Direct Permissions** > **SP_High **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/sp_sitecollectionperms.md b/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/sp_sitecollectionperms.md index 52b2c9b2d6..a446139172 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/sp_sitecollectionperms.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/sp_sitecollectionperms.md @@ -6,8 +6,8 @@ sidebar_position: 40 # SP_SiteCollectionPerms Job -Most content will inherit the permissions configured at the root of the site collection. Having an -understanding of how those permissions are assigned is useful for gaining perspective on the overall +Most content will inherit the permissions configured at the root of the site collection. Understanding +how those permissions are assigned gives you perspective on the overall SharePoint permission configuration. ## Analysis Tasks for the SP_SiteCollectionPerms Job @@ -16,7 +16,7 @@ Navigate to the **Jobs** > **SharePoint** > **1.Direct Permissions** > **SP_Site **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -41,4 +41,4 @@ report: | Report | Description | Default Tags | Report Elements | | ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Direct Site Collection Permissions | Most content will inherit the permissions configured at the root of the site collection. Having an understanding of how those permissions are assigned is useful for gaining perspective on the overall SharePoint permission configuration. | None | This report is comprised of two elements:
  • Bar Chart – Displays top 5 site collections by direct permissions
  • Table – Provides details on site collections by direct permissions breakdown
| +| Direct Site Collection Permissions | Most content will inherit the permissions configured at the root of the site collection. Understanding how those permissions are assigned gives you perspective on the overall SharePoint permission configuration. | None | This report is comprised of two elements:
  • Bar Chart – Displays top 5 site collections by direct permissions
  • Table – Provides details on site collections by direct permissions breakdown
| diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/sp_staleusers.md b/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/sp_staleusers.md index 9df86978c2..4380193058 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/sp_staleusers.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/sp_staleusers.md @@ -6,7 +6,7 @@ sidebar_position: 50 # SP_StaleUsers Job -A stale user is defined as either currently disabled within Active Directory, or has not logged onto +A stale user is a user account that's disabled in Active Directory or hasn't logged on to the domain for over 90 days. This job will identify locations where there are stale users directly applied on SharePoint resources. These permissions can be safely removed. @@ -16,7 +16,7 @@ Navigate to the **Jobs** > **SharePoint** > **1.Direct Permissions** > **SP_Stal **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -37,4 +37,4 @@ users, the SP_StaleUsers Job produces the following pre-configured report: | Report | Description | Default Tags | Report Elements | | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Stale User Permissions | A stale user is defined as either currently disabled within Active Directory, or has not logged onto the domain for over 90 days. | None | This report is comprised of three elements:
  • Bar Chart – Displays top 5 users by affected resources
  • Table – Provides details on top resource by stale user permissions
  • Table – Provides details on top stale users by affected resources
| +| Stale User Permissions | A stale user is a user account that's disabled in Active Directory or hasn't logged on to the domain for over 90 days. | None | This report is comprised of three elements:
  • Bar Chart – Displays top 5 users by affected resources
  • Table – Provides details on top resource by stale user permissions
  • Table – Provides details on top stale users by affected resources
| diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/sp_unresolvedsids.md b/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/sp_unresolvedsids.md index a6b75e2650..5c1d7551f0 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/sp_unresolvedsids.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/directpermissions/sp_unresolvedsids.md @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **SharePoint** > **1.Direct Permissions** > **SP_Unre **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/effectiveaccessaudits/overview.md b/docs/accessanalyzer/12.0/solutions/sharepoint/effectiveaccessaudits/overview.md index 106bebefeb..4e7e6d21e9 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/effectiveaccessaudits/overview.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/effectiveaccessaudits/overview.md @@ -14,9 +14,9 @@ SharePoint environment. The Effective Access Audits Job Group is comprised of: - [Scoping > SP_TrusteeAccess Job](/docs/accessanalyzer/12.0/solutions/sharepoint/effectiveaccessaudits/sp_trusteeaccess.md) – Scopes a list of users to audit their - access across the SharePoint environment. This can also be accomplished by looking users up in the - Access Information Center. However, it is recommended to use this job in scenarios where a report - on multiple users’ effective access at once needs to be generated. + access across the SharePoint environment. You can also look users up in the + Access Information Center. However, use this job when you need to generate a report + on multiple users’ effective access at once. - [SP_TrusteeAudit Job](/docs/accessanalyzer/12.0/solutions/sharepoint/effectiveaccessaudits/sp_trusteeaudit.md) – Provides functionality similar to the Access Information Center by allowing scoped audits of users’ access across the environment diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/effectiveaccessaudits/sp_trusteeaccess.md b/docs/accessanalyzer/12.0/solutions/sharepoint/effectiveaccessaudits/sp_trusteeaccess.md index b19b74019d..0e8c813246 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/effectiveaccessaudits/sp_trusteeaccess.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/effectiveaccessaudits/sp_trusteeaccess.md @@ -6,15 +6,15 @@ sidebar_position: 10 # Scoping > SP_TrusteeAccess Job -The SP_TrusteeAccess job allows you to scope a list of users to audit their access across the +Use the SP_TrusteeAccess job to scope a list of users to audit their access across the SharePoint environment. You can also accomplish this by looking users up in the Access Information -Center, however you want to utilize this job in scenarios where you want to generate a report on +Center. However, use this job when you want to generate a report on multiple users’ effective access at once. :::note Trustees can be specified in the `UserScoping.csv` file for the SP_TrusteeAccess Job. See the -[Configure CSV File for the Query for the SP_TrusteeAccess Job](#configure-csv-file-for-the-query-for-the-sp_trusteeaccess-job) +[Configure CSV File for the Query for the SP_TrusteeAccess Job](#configure-csv-file-for-the-query-for-the-sptrusteeaccess-job) topic for additional information. ::: @@ -32,15 +32,15 @@ The SP_TrusteeAccess Job uses the TextSearch Data Collector for the following qu The default query is: - Scoping – Modifies the CSV in the Job Directory. See the - [Configure CSV File for the Query for the SP_TrusteeAccess Job](#configure-csv-file-for-the-query-for-the-sp_trusteeaccess-job) + [Configure CSV File for the Query for the SP_TrusteeAccess Job](#configure-csv-file-for-the-query-for-the-sptrusteeaccess-job) topic for additional information. ### Configure CSV File for the Query for the SP_TrusteeAccess Job -Follow the steps to specify trustees in the `UserScoping.csv` file. +To specify trustees in the `UserScoping.csv` file: **Step 1 –** Navigate to the **Jobs** > **SharePoint** > **Effective Access Audits** > **Scoping** > -**SP_TrusteeAccess** Job and right-click on the job. Select **Explore Folder** and the job’s +**SP_TrusteeAccess** Job and right-click the job. Select **Explore Folder** and the job’s directory opens. ![UserScoping.csv in the SP_TrusteeAccess Job folder in File Explorer](/images/accessanalyzer/12.0/solutions/sharepoint/effectiveaccessaudits/userscopingfileexplorer.webp) diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/effectiveaccessaudits/sp_trusteeaudit.md b/docs/accessanalyzer/12.0/solutions/sharepoint/effectiveaccessaudits/sp_trusteeaudit.md index 8d878d7a92..50a354bdbf 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/effectiveaccessaudits/sp_trusteeaudit.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/effectiveaccessaudits/sp_trusteeaudit.md @@ -16,7 +16,7 @@ Navigate to the **Jobs** > **SharePoint** > **Effective Access Audits** > **SP_T **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/m365/overview.md b/docs/accessanalyzer/12.0/solutions/sharepoint/m365/overview.md index 43ee5e2317..8cf8b69d8a 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/m365/overview.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/m365/overview.md @@ -7,7 +7,7 @@ sidebar_position: 100 # 8.M365 Job Group The 8.M365 Job Group generates summary and detail reports of SharePoint Activity on the specified -Teams sites. These reports can be used for identifying file, folder, and user related activity +Teams sites. Use these reports to identify file, folder, and user related activity across your SharePoint environment. ![8.M365 Job Group in the Jobs Tree](/images/accessanalyzer/12.0/solutions/sharepoint/m365/jobstree.webp) diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_externalusers.md b/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_externalusers.md index 410040242f..5fc7e55657 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_externalusers.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_externalusers.md @@ -6,16 +6,16 @@ sidebar_position: 10 # SP_ExternalUsers Job -The SP_TeamsExternalUsers Job identifies activity of external users on all monitored SharePoint +The SP_ExternalUsers Job identifies activity of external users on all monitored SharePoint servers. ## Analysis Tasks for the SP_ExternalUsers Job -Navigate to the **Jobs** > **SharePoint** > **8.M365** > **SP_OneDrives** > **Configure** node and +Navigate to the **Jobs** > **SharePoint** > **8.M365** > **SP_ExternalUsers** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -30,7 +30,7 @@ The default analysis task is: - Summarize External User Activity – Creates the SP_ExternalUsersDetails table accessible under the job's Results node -In addition to the tables created by the analysis tasks, the SP_TeamsExternalUsers Job produces the +In addition to the tables created by the analysis tasks, the SP_ExternalUsers Job produces the following preconfigured report: | Report | Description | Default Tags | Report Elements | diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_onedrives.md b/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_onedrives.md index 7990d08acb..5158a9a323 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_onedrives.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_onedrives.md @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **SharePoint** > **8.M365** > **SP_OneDrives** > **Co select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -44,4 +44,4 @@ preconfigured reports: | ------------------------ | -------------------------------------------------------------------- | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | One Drive Activity | This report displays activity information from OneDrives. | None | This report is comprised of three elements:
  • Bar Chart – Provides information on top OneDrives by Operation Count
  • Table – Provides details on OneDriveSummary
  • Table – Provides details on OneDrive Activity Details
| | One Drive Sensitive Data | This report displays sensitive information from OneDrives. | None | This report is comprised of three elements:
  • Bar Chart – Provides information on top OneDrives by sensitive files
  • Table – Provides details on sensitive data summary
  • Table – Provides details on OneDrive file details
| -| One Drive Sensitive Data | This report displays summary level information across all OneDrives. | None | This report is comprised of three elements:
  • Bar Chart – Provides information on OneDrive summary
  • Table – Provides details on top OneDrives by GB
  • Table – Provides details on top OneDrives by GB summary
  • Table – Provides information on OneDrive details
| +| One Drive Summary | This report displays summary level information across all OneDrives. | None | This report is comprised of three elements:
  • Bar Chart – Provides information on OneDrive summary
  • Table – Provides details on top OneDrives by GB
  • Table – Provides details on top OneDrives by GB summary
  • Table – Provides information on OneDrive details
| diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_sharedlinks.md b/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_sharedlinks.md index 81db39bfee..d53caa829e 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_sharedlinks.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_sharedlinks.md @@ -16,7 +16,7 @@ Navigate to the **Jobs** > **SharePoint** > **8.M365** > **SP_SharedLinks** > ** select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -37,11 +37,11 @@ The default analysis tasks are: SA_SP_SharingLinks_Creation_Detail_Last_7_Days, and SA_SP_SharingLinks_Creation_Summary_Last_7_Days tables accessible under the job's Results node -In addition to the tables created by the analysis tasks, the SP_Shared Links Job produces the +In addition to the tables created by the analysis tasks, the SP_SharedLinks Job produces the following preconfigured reports: | Report | Description | Default Tags | Report Elements | | -------------------- | ------------------------------------------------------------------------------------------------------------------ | ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Anonymous Sharing | This report highlights instances where resources are anonymously shared via a shareable link in SharePoint Online. | None | This report is comprised of three elements:
  • Bar Chart – Provides information on the top site collections and anonymously shared files
  • Table – Provides details anonymous sharing summary by site collection
  • Table – Provides details on anonymously sharing details
| -| Shared Link Activity | This report highlights instances of activity via shared links in SharePoint Online. | None | This report is comprised of three elements:
  • Bar Chart – Provides information on the shared link creation for the last 7 days OneDrive summary
  • Table – Provides details on shared link creation summary for the last 7 days
  • Table – Provides details on shared link activity
| -| Shared Links | This report highlights instances of shared links in SharePoint Online. | None | This report is comprised of three elements:
  • Bar Chart Table– Provides information on the shared link summary
  • Bar Chart– Provides details on top site collections by shared files
  • Table – Provides details on site collection summary
  • Table – Provides details on shared links
| +| Anonymous Sharing | This report highlights instances where resources are anonymously shared via a shareable link in SharePoint Online. | None | This report is comprised of three elements:
  • Bar Chart – Provides information on the top site collections and anonymously shared files
  • Table – Provides details on anonymous sharing summary by site collection
  • Table – Provides details on anonymous sharing details
| +| Shared Link Activity | This report highlights instances of activity via shared links in SharePoint Online. | None | This report is comprised of three elements:
  • Bar Chart – Provides information on the shared link creation for the last 7 days
  • Table – Provides details on shared link creation summary for the last 7 days
  • Table – Provides details on shared link activity
| +| Shared Links | This report highlights instances of shared links in SharePoint Online. | None | This report is comprised of four elements:
  • Bar Chart – Provides information on the shared link summary
  • Bar Chart – Provides details on top site collections by shared files
  • Table – Provides details on site collection summary
  • Table – Provides details on shared links
| diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_staleteamsites.md b/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_staleteamsites.md index f0911dfbde..a66cdb71ef 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_staleteamsites.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_staleteamsites.md @@ -7,11 +7,11 @@ sidebar_position: 40 # SP_StaleTeamSites Job The SP_StaleTeamSites Job identifies Teams that have not had activity for a number of days that can -be set in the analysis (Set as 30 Days by Default). +be set in the analysis (Set at 30 Days by Default). ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/12.0/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -21,7 +21,7 @@ The SP_StaleTeamSites page has the following configurable parameters: - Desired Number of Days Since Last Activity To Determine Staleness See the -[Customizable Analysis Tasks for the SP_StaleTeamSites Job](#customizable-analysis-tasks-for-the-sp_staleteamsites-job) +[Customizable Analysis Tasks for the SP_StaleTeamSites Job](#customizable-analysis-tasks-for-the-spstaleteamsites-job) for additional information. ## Analysis Tasks for the SP_StaleTeamSites Job @@ -37,7 +37,7 @@ The default analysis task is: - This task contains a configurable parameter to set the number of days a Team has not had activity for before it's considered stale. See the - [Customizable Analysis Tasks for the SP_StaleTeamSites Job](#customizable-analysis-tasks-for-the-sp_staleteamsites-job) + [Customizable Analysis Tasks for the SP_StaleTeamSites Job](#customizable-analysis-tasks-for-the-spstaleteamsites-job) topic for additional information. In addition to the table created by the analysis task, the SP_StaleTeamSites Job produces the diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_teams.md b/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_teams.md index 8715ed4e7a..e76023aca6 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_teams.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_teams.md @@ -15,7 +15,7 @@ Navigate to the **Jobs** > **SharePoint** > **8.M365** > **SP_Teams** > **Config select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_teamsexternaluseractivity.md b/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_teamsexternaluseractivity.md index e5b9fc39ba..62c9e61493 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_teamsexternaluseractivity.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_teamsexternaluseractivity.md @@ -16,7 +16,7 @@ Navigate to the **Jobs** > **SharePoint** > **8.M365** > tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_teamssensitivedata.md b/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_teamssensitivedata.md index cec32e66a1..feb53b8958 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_teamssensitivedata.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_teamssensitivedata.md @@ -14,7 +14,7 @@ Navigate to the **Jobs** > **SharePoint** > **8.M365** > **SP_TeamsSensitiveData node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/overview.md b/docs/accessanalyzer/12.0/solutions/sharepoint/overview.md index 77bdaba692..e771583881 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/overview.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/overview.md @@ -44,14 +44,14 @@ additional information. **Sensitive Data Discovery Considerations** -If running Sensitive Data Discovery (SDD) scans, it will be necessary to increase the minimum amount +If you run Sensitive Data Discovery (SDD) scans, increase the minimum amount of RAM. Each thread requires a minimum of 2 additional GB of RAM per host. For example, if the job -is configured to scan 8 hosts at a time , then an extra 16 GB of RAM are required (8x2=16). +is configured to scan 8 hosts at a time, then an extra 16 GB of RAM are required (8x2=16). :::note -The appropriate JDK (Java) version for Sensitive Data Discovery is installed on the -server. The JDK deployed is prepackaged and does not require any configuration; it has been -preconfigured to work with Access Analyzer and should never be customized through Java. It will not +Access Analyzer installs the appropriate JDK (Java) version for Sensitive Data Discovery on the +server. The JDK is prepackaged, doesn't require any configuration, and is preconfigured to work with +Access Analyzer. Never customize it through Java. It doesn't conflict with other JDKs or Java Runtimes in the same environment. ::: @@ -59,7 +59,7 @@ conflict with other JDKs or Java Runtimes in the same environment. **Location** The SharePoint Solution requires a special Access Analyzer license. It can be installed from the -Access Analyzer Instant Job Wizard. Once it has been installed into the Jobs tree, navigate to the +Access Analyzer Instant Job Wizard. After it's installed into the Jobs tree, navigate to the solution: **Jobs** > **SharePoint**. The 0.Collection Job Group collects the data. The other job groups and the SP_Overview Job run @@ -70,7 +70,7 @@ analysis on the collected data and generate reports. This SharePoint solution offers information on multiple aspects of an organization’s SharePoint on-premises and SharePoint Online environments. This solution is comprised of 10 sub-job groups and an overview job which collect, analyze, and report on data. The data collection is conducted by the -SharePointAccess (SPAA) Data Collector. See the corresponding +SharePoint Access Auditing (SPAA) Data Collector. See the corresponding [Standard Reference Tables & Views for the SPAA Data Collector](/docs/accessanalyzer/12.0/admin/datacollector/spaa/standardtables.md) topic for database table information. @@ -85,15 +85,15 @@ The following types of auditing can be conducted with the SharePoint Solution: Each type of auditing depends on specific jobs within the 0.Collection Job Group to collect the data and its corresponding analysis/reporting job groups. The Access Auditing components represent the core of the SharePoint Solution. However, the Sensitive Data Discovery Auditing components also -collect the Access Auditing data; therefore it is not necessary to run both sets of collection jobs. +collect the Access Auditing data; therefore it isn't necessary to run both sets of collection jobs. The data collection query options for each type are explained within the 0.Collection Job Group section. Additionally, the corresponding analysis/reporting job groups are listed for each auditing type. -If intending to run two or all auditing types, see each auditing type section within the -0.Collection Job Group section for information on query options and requirements. It is recommended -to first run the 0.Collection Job Group components in the default order for the desired auditing -types to ensure successful data collection, and then to run the desired sub-groups for reports. +If you intend to run two or all auditing types, see each auditing type section within the +0.Collection Job Group section for information on query options and requirements. First run the +0.Collection Job Group components in the default order for the auditing types you want, to ensure +successful data collection, then run the sub-groups you want for reports. See the [Recommended Configuration for the SharePoint Solution](/docs/accessanalyzer/12.0/solutions/sharepoint/recommended.md) topic for additional information on frequency and job group settings. @@ -103,7 +103,7 @@ the following job groups and jobs: - [0.Collection Job Group](/docs/accessanalyzer/12.0/solutions/sharepoint/collection/overview.md) – Designed to collect high level summary information from SharePoint servers. This information is used to populate the SMP Reports based - around the SharePoint and is a requirement for the Access Information Center – SharePoint reports. + around SharePoint and is a requirement for the Access Information Center – SharePoint reports. - This job group is available with the SharePoint license feature @@ -113,20 +113,20 @@ the following job groups and jobs: - [2.High Risk Sites > SP_OpenAccess Job](/docs/accessanalyzer/12.0/solutions/sharepoint/sp_openaccess.md) – Provides insight into any high-risk repositories and high-risk data that may exist within an organization’s SharePoint environment. High risk data is effectively open to the entire organization through modification of SharePoint - permissions to apply well known security principles such as NT AUTHORITY\Authenticated Users, + permissions to apply well known security principals such as NT AUTHORITY\Authenticated Users, Everyone, and Everyone Except External Users. This data must be monitored closely because of its exposure. - [3.Broken Inheritance > SP_BrokenInheritance Job](/docs/accessanalyzer/12.0/solutions/sharepoint/sp_brokeninheritance.md) – Keeping track of - directly applied permissions at mass is not realistic, this job is responsible for performing data + directly applied permissions at scale isn't realistic. This job is responsible for performing data analysis and generating SharePoint broken inheritance reports at the site level. This includes looking at site broken inheritance and the trustees who are assigned to those sites where inheritance is broken so that you can remove that access in favor of providing access via group membership. - [4.Content Job Group](/docs/accessanalyzer/12.0/solutions/sharepoint/content/overview.md) – Provides insight into content stored across - SharePoint farms in order to help more efficiently manage that content. It will provide - information on the content taking up the most space, the content that has not been accessed for - extended periods of time, and additional data describing SharePoint content and the configuration - of the repositories such as lists and libraries which store that content. + SharePoint farms to help more efficiently manage that content. It will provide + information about the largest content, content that hasn't been accessed in a long time, and + additional data about SharePoint content and the configuration of repositories, such as lists + and libraries, that store that content. - [5.Probable Owner > SP_ProbableOwner Job](/docs/accessanalyzer/12.0/solutions/sharepoint/sp_probableowner.md) – Provides reports about probable ownership. The goal of this report is to help you either identify who most likely owns the SharePoint resource or at least someone who can tell you who does. @@ -135,11 +135,11 @@ the following job groups and jobs: - Requires Sensitive Data Discovery -- [7.Activity Job Group](/docs/accessanalyzer/12.0/solutions/sharepoint/activity/overview.md)– Generates summary and detail reports of SharePoint - activity on the specified sites. These reports can be used for identifying file, folder, and user +- [7.Activity Job Group](/docs/accessanalyzer/12.0/solutions/sharepoint/activity/overview.md) – Generates summary and detail reports of SharePoint + activity on the specified sites. Use these reports to identify file, folder, and user related activity across your SharePoint environment. - [8.M365 Job Group](/docs/accessanalyzer/12.0/solutions/sharepoint/m365/overview.md) – Generates summary and detail reports of SharePoint Activity - on the specified Teams sites. These reports can be used for identifying file, folder, and user + on the specified Teams sites. Use these reports to identify file, folder, and user related activity across your SharePoint environment. - [Effective Access Audits Job Group](/docs/accessanalyzer/12.0/solutions/sharepoint/effectiveaccessaudits/overview.md) – Returns reports identifying specific trustees’ effective access across the entire SharePoint environment diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/recommended.md b/docs/accessanalyzer/12.0/solutions/sharepoint/recommended.md index 9efbfdc602..a999da83cc 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/recommended.md @@ -8,25 +8,25 @@ sidebar_position: 10 The SharePoint Solution has been configured to inherit down from the **SharePoint** > **Settings** node. However, it is a best practice to assign the host list and the Connection Profile at the data -collection level, 0.Collection Job Group. Once these are assigned to the job group, it can be run +collection level, 0.Collection Job Group. After these are assigned to the job group, it can be run directly or scheduled. **Dependencies** -- The **.Active Directory Inventory** Job Group needs to be executed prior to running the SharePoint +- The **.Active Directory Inventory** Job Group needs to be executed before running the SharePoint Solution against a SharePoint on-premises environment -- The **.Entra ID Inventory** Job Group needs to be executed prior to running the SharePoint +- The **.Entra ID Inventory** Job Group needs to be executed before running the SharePoint Solution against a SharePoint Online environment - For Agent-based scans, the SharePoint Agent must be installed on the application server (for Access Auditing & Sensitive Data Discovery Auditing only) -**Targeted Host(s)** +**Targeted Hosts** For the 0.Collection Job Group: - Single SharePoint Application server hosting Central Administration per SharePoint farm -The host list assignment should be assigned under the **SharePoint** > **0.Collection** > +Assign the host list under the **SharePoint** > **0.Collection** > **Settings** > **Host List Assignment** node. The list should be a custom-created list for the SharePoint environments to be targeted. Select the checkbox for the custom-created host list. @@ -42,17 +42,17 @@ The SPAA Data Collector requires a specific set of permissions. See the [SharePoint Support](/docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepoint.md) topics for the necessary permissions for both on-premises and online target environments. Then create a custom Connection Profile containing the appropriate credentials for the targeted environment. If a single Connection Profile -contains both on-premises and online credentials, it is necessary for the online credentials to be +contains both on-premises and online credentials, the online credentials must be listed above the on-premises credentials in the Connection Profile credentials list. The Connection Profile should be assigned under the **SharePoint** > **0.Collection** > **Settings** > **Connection** node. It is set to **Use the Default Profile**, as configured at the global settings level. However, since this may not be the Connection Profile with the necessary permissions for the assigned hosts, select the **Select one of the following user defined profiles** -option and select the appropriate Connection Profile from the drop-down menu. +option and select the appropriate Connection Profile from the dropdown menu. The jobs within the 5.Effective Access Audits Job Group import CSV files from the jobs’ directories -using the TextSearch Data Collector. Therefore, it is necessary to assign a Connection Profile with +using the TextSearch Data Collector. Therefore, assign a Connection Profile with rights on the Access Analyzer Console server to access the CSV file saved in the job’s directory. The Connection Profile can be set at either the **Effective Access Audits** > **Settings** > **Connection** node (applies to both jobs) or in the job’s Properties window on the Connection tab. @@ -65,21 +65,21 @@ The jobs in this job group can be scheduled to run as desired. **Run Order** -The 0.Collection Jobs must be run first and in order. RunSystem Scans jobs and then the Bulk Import -jobs according to the desired workflow. The other SharePoint Solution sub-job groups can be run in +The 0.Collection Jobs must be run first and in order. Run System Scans jobs and then the Bulk Import +jobs according to the workflow you want. The other SharePoint Solution sub-job groups can be run in any order, together or individually, after running the 0.Collection Job Group. It is recommended to run at the sub-job group level. The SP_Overview Job pulls information from both the 0.Collection Job Group and the other sub-job groups, and the report may contain blank sections if only select sub-job groups are run. -The Access Information Center requires the execution of the 2-SPAA_BulkImport Job default analysis -tasks in order for permission/access reports to be accessible. For activity reports, the Access -Information Center requires the execution of both the 2-SPAA Bulk Import Job default analysis tasks -and the 2-SPAC Bulk Import Job default analysis tasks. +The Access Information Center requires the 2-SPAA_BulkImport Job's default analysis +tasks to run before permission/access reports are accessible. For activity reports, the Access +Information Center requires the default analysis tasks of both the 2-SPAA Bulk Import Job +and the 2-SPAC Bulk Import Job to run. :::info If only conducting one or two types of auditing, scope the solution by disabling -the undesired collection jobs. Disabling them allows the solution to run more efficiently. It is not +the undesired collection jobs. Disabling them allows the solution to run more efficiently. It isn't recommended to delete any jobs. See the [Disable or Enable a Job](/docs/accessanalyzer/12.0/admin/jobs/job/disableenable.md) topic for additional information. ::: @@ -90,7 +90,7 @@ recommended to delete any jobs. See the This solution can be run with the default query configuration. However, the most common customizations include: -- If using agent-based scanning, it is necessary to enable the agent services on the SharePoint +- If using agent-based scanning, enable the agent services on the SharePoint Access Auditor Data Collector Wizard pages: - Agent Settings page, enable agent service scans: @@ -152,26 +152,26 @@ This solution should be run with the default analysis configuration. Most of the are preconfigured. There are a few which are deselected by default, as they are for troubleshooting purposes. -Though the analysis tasks should not be deselected, the following parameters can be modified: +Though the analysis tasks shouldn't be deselected, the following parameters can be modified: -- Stale File is defined by default to 365 days +- Stale File defaults to 365 days - Customize within the **4.Content** > **SP_StaleFiles** Job -- Stale Teams is defined by default to 30 days +- Stale Teams defaults to 30 days - Customize within the **8.M365** > **SP_StaleTeamSites** Job The .Active Directory Inventory Solution defines large groups, deeply nested groups, stale users, and users with large tokens. These parameters can be customized and are applicable to any solution, -including SharePoint, which incorporate this analyzed data into further analysis. +including SharePoint, which incorporates this analyzed data into further analysis. - Customize within .Active Directory Inventory > 3-AD_Exceptions Job analysis tasks **Additional Considerations** The Effective Access Audits Job Group is designed to work independently of the rest of the solution, -but it is dependent upon the 0.Collection Job Group and the user-modified CSV files. +but it depends on the 0.Collection Job Group and the user-modified CSV files. **Additional Notes** diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/sp_brokeninheritance.md b/docs/accessanalyzer/12.0/solutions/sharepoint/sp_brokeninheritance.md index f648b4fd6a..05e7324b24 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/sp_brokeninheritance.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/sp_brokeninheritance.md @@ -6,7 +6,7 @@ sidebar_position: 50 # 3.Broken Inheritance > SP_BrokenInheritance Job -Keeping track of directly applied permissions at mass is not realistic, the SP_BrokenInheritance job +Keeping track of directly applied permissions at scale isn't realistic. The SP_BrokenInheritance job is responsible for performing data analysis and generating SharePoint broken inheritance reports at the site level. This includes looking at site broken inheritance and the trustees who are assigned to those sites where inheritance is broken so that you can remove that access in favor of providing @@ -22,7 +22,7 @@ Navigate to the **Jobs** > **SharePoint** > **3.Broken Inheritance** > **SP_Brok **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -45,4 +45,4 @@ inheritance, the SP_BrokenInheritance Job produces the following pre-configured | Report | Description | Default Tags | Report Elements | | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Broken Inheritance | This job is responsible for performing data analysis and generating SharePoint direct permission reports at the site level. This includes looking at site broken inheritance and the trustees who are assigned to those sites where inheritance is broken. | None | This report is comprised of two elements:
  • Bar Chart – Displays top 5 site collections by resources with permission changes
  • Table – Provides a site collection summary
  • Table – Provides broken inheritance details
| +| Broken Inheritance | This job is responsible for performing data analysis and generating SharePoint broken inheritance reports at the site level. This includes looking at site broken inheritance and the trustees who are assigned to those sites where inheritance is broken. | None | This report is comprised of two elements:
  • Bar Chart – Displays top 5 site collections by resources with permission changes
  • Table – Provides a site collection summary
  • Table – Provides broken inheritance details
| diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/sp_openaccess.md b/docs/accessanalyzer/12.0/solutions/sharepoint/sp_openaccess.md index e7c268a5bc..d095224987 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/sp_openaccess.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/sp_openaccess.md @@ -16,10 +16,10 @@ its exposure. The job group is comprised of the SP_OpenAccess Job. Minimizing your attack surface is the goal. Open site collections can potentially provide access to privileged data, greatly increasing your -vulnerability. The SP_OpenAccess Job will identify places in the environment where data is able to -be accessed by a very large amount of employees. +vulnerability. The SP_OpenAccess Job will identify places in the environment where data can +be accessed by a very large number of employees. -It is dependent on data collected by the +It depends on data collected by the [SharePoint Access Auditing](collection/overview.md#sharepoint-access-auditing) or [SharePoint Sensitive Data Discovery Auditing (SEEK)](collection/overview.md#sharepoint-sensitive-data-discovery-auditing-seek) components of the [0.Collection Job Group](/docs/accessanalyzer/12.0/solutions/sharepoint/collection/overview.md). @@ -30,7 +30,7 @@ Navigate to the **Jobs** > **SharePoint** > **2.High Risk Sites** > **SP_OpenAcc **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/sp_overview.md b/docs/accessanalyzer/12.0/solutions/sharepoint/sp_overview.md index a1a94fecc3..20ee3fd268 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/sp_overview.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/sp_overview.md @@ -12,11 +12,11 @@ found during scans. ![SP_Overview Job in the Jobs Tree](/images/accessanalyzer/12.0/solutions/sharepoint/overviewjobstree.webp) -It is dependent on data collected by the +It depends on data collected by the [SharePoint Access Auditing](collection/overview.md#sharepoint-access-auditing), [SharePoint Sensitive Data Discovery Auditing (SEEK)](collection/overview.md#sharepoint-sensitive-data-discovery-auditing-seek), and [SharePoint Activity Auditing](collection/overview.md#sharepoint-activity-auditing) components -of the [0.Collection Job Group](/docs/accessanalyzer/12.0/solutions/sharepoint/collection/overview.md). It also depends on the running of the +of the [0.Collection Job Group](/docs/accessanalyzer/12.0/solutions/sharepoint/collection/overview.md). It also depends on running the sub-job groups within the solution. If only select sub-job groups have been run, there will be blank sections of this overview report. @@ -26,14 +26,14 @@ Navigate to the **Jobs** > **SharePoint** > **SP_Overview** > **Configure** node **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: ![Analysis Tasks for the SP_Overview Job](/images/accessanalyzer/12.0/solutions/sharepoint/overviewanalysis.webp) -The default analysis tasks is: +The default analysis task is: - Generate Overview – Creates an interim processing table in the database for use by downstream analysis and report generation diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/sp_probableowner.md b/docs/accessanalyzer/12.0/solutions/sharepoint/sp_probableowner.md index 89f2ac39f4..471a90ee3c 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/sp_probableowner.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/sp_probableowner.md @@ -6,8 +6,8 @@ sidebar_position: 70 # 5.Probable Owner > SP_ProbableOwner Job -The SP_ProbableOwner Job aids in the identification of probable owners for Site Collections and -Sites, which can be used for entitlement reviews. Probably Owner calculation is based on file +The SP_ProbableOwner Job identifies probable owners for Site Collections and +Sites, which you can use for entitlement reviews. Probable Owner calculation is based on file ownership, management structure, and file activity. The goal of this report is to help you identify who most likely owns the SharePoint resource or at least someone who can tell you who does. @@ -21,7 +21,7 @@ Navigate to the **Jobs** > **SharePoint** > **5.Probable Owner** > **SP_ProbableOwner** >**Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/sp_sensitivedata.md b/docs/accessanalyzer/12.0/solutions/sharepoint/sp_sensitivedata.md index 5f74bf9497..c5bd31254d 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/sp_sensitivedata.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/sp_sensitivedata.md @@ -19,7 +19,7 @@ Navigate to the **Jobs** > **SharePoint** > **6.Sensitive Data** > **SP_Sensitiv **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/unix/overview.md b/docs/accessanalyzer/12.0/solutions/unix/overview.md index 75f7245472..2f347a4dba 100644 --- a/docs/accessanalyzer/12.0/solutions/unix/overview.md +++ b/docs/accessanalyzer/12.0/solutions/unix/overview.md @@ -28,7 +28,7 @@ for additional information. **Location** The Unix Solution requires a special Access Analyzer license. It can be installed from the Access -Analyzer Instant Job Wizard. Once it has been installed into the Jobs tree, navigate to the +Analyzer Instant Job Wizard. After it's installed into the Jobs tree, navigate to the solution: **Jobs** > **Unix**. ## Job Groups diff --git a/docs/accessanalyzer/12.0/solutions/unix/privilegedaccess/overview.md b/docs/accessanalyzer/12.0/solutions/unix/privilegedaccess/overview.md index 7bf881a023..f3de1da06f 100644 --- a/docs/accessanalyzer/12.0/solutions/unix/privilegedaccess/overview.md +++ b/docs/accessanalyzer/12.0/solutions/unix/privilegedaccess/overview.md @@ -14,7 +14,7 @@ critical files such as passwd, shadow, sudoers, hosts.deny, and more. The jobs in the 2.Privileged Access job group are: -- [ Sudoers Job Group](/docs/accessanalyzer/12.0/solutions/unix/privilegedaccess/sudoers/overview.md) – The jobs in this job group provide visibility into all +- [Sudoers Job Group](/docs/accessanalyzer/12.0/solutions/unix/privilegedaccess/sudoers/overview.md) – The jobs in this job group provide visibility into all rights granted via sudoers within audited Unix and Linux environments - [UX_CriticalFiles Job](/docs/accessanalyzer/12.0/solutions/unix/privilegedaccess/ux_criticalfiles.md) – This job provides visibility into owners of critical files within audited Unix and Linux environments such as passwd, shadow, sudoers, hosts.deny, and diff --git a/docs/accessanalyzer/12.0/solutions/unix/privilegedaccess/sudoers/ux_sudoers.md b/docs/accessanalyzer/12.0/solutions/unix/privilegedaccess/sudoers/ux_sudoers.md index 99676434f6..50b2fb667d 100644 --- a/docs/accessanalyzer/12.0/solutions/unix/privilegedaccess/sudoers/ux_sudoers.md +++ b/docs/accessanalyzer/12.0/solutions/unix/privilegedaccess/sudoers/ux_sudoers.md @@ -15,7 +15,7 @@ Navigate to the **Unix** > **2.Privileged Access** > **Sudoers** > **UX_Sudoers* node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/unix/privilegedaccess/ux_criticalfiles.md b/docs/accessanalyzer/12.0/solutions/unix/privilegedaccess/ux_criticalfiles.md index 90290258bc..0766555d7b 100644 --- a/docs/accessanalyzer/12.0/solutions/unix/privilegedaccess/ux_criticalfiles.md +++ b/docs/accessanalyzer/12.0/solutions/unix/privilegedaccess/ux_criticalfiles.md @@ -11,7 +11,7 @@ Linux environments such as passwd, shadow, sudoers, hosts.deny, and more. ## Queries for the UX_CriticalFiles Job -The UX_CriticalFIles job uses the Unix Data Collector for the following query: +The UX_CriticalFiles job uses the Unix Data Collector for the following query: :::warning The query is preconfigured for this job. Never modify the query. @@ -30,7 +30,7 @@ Navigate to the **Unix** > **2.Privileged Access** > **UX_CriticalFiles** > **Co select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/unix/recommended.md b/docs/accessanalyzer/12.0/solutions/unix/recommended.md index 0a95dabb67..c01df1c90a 100644 --- a/docs/accessanalyzer/12.0/solutions/unix/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/unix/recommended.md @@ -14,10 +14,10 @@ directly or scheduled. If applicable, the **.NIS Inventory** job group can be run to enable reporting on users and groups from NIS environments. -**Target Host(s)** +**Target Hosts** -All Unix Servers. Create a custom host list in Host Management that contains all Unix servers that -are in scope to be auditing with the Unix solution. +All Unix Servers. Create a custom host list in Host Management that contains all Unix servers you +want to audit with the Unix solution. The Unix job group has been configured to inherit the host list assignment from the solution level. The host list assignment should be assigned under the **Unix** > **Settings** > **Host List @@ -27,7 +27,7 @@ Assignment** node. Select the UNIX servers host list created previously. Set a Connection Profile on the Unix job group with root permissions for Unix/Linux. -If the Root permission is unavailable, a least privileged model can be used. See the +If the Root permission is unavailable, you can use a least privileged model instead. See the [Least Privilege Model](/docs/accessanalyzer/12.0/requirements/unix/target.md#least-privilege-model) topic for permissions needed to target the supported platforms for data collection. @@ -37,7 +37,7 @@ Schedule the Unix Solution or individual job groups to run as desired. **History Retention** -This is not supported in this job group and should be turned off. +This isn't supported in this job group and should be turned off. **Run at the Job Group Level** @@ -57,7 +57,7 @@ The analysis tasks in this job group are preconfigured to run with the default c **Step 1 –** Run a Host Discovery Query to create a host list with All Unix Servers, and assign that host list under the **Unix** > **Settings** > **Host List Assignment** node. -**Step 2 –** (Optional) If applicable, run the **.NIS Inventory** job group run to enable reporting +**Step 2 –** (Optional) If applicable, run the **.NIS Inventory** job group to enable reporting on users and groups from NIS environments. **Step 3 –** Set a Connection Profile on the Unix job group. diff --git a/docs/accessanalyzer/12.0/solutions/unix/sharing/collection/overview.md b/docs/accessanalyzer/12.0/solutions/unix/sharing/collection/overview.md index daf3709a15..a6e58b6759 100644 --- a/docs/accessanalyzer/12.0/solutions/unix/sharing/collection/overview.md +++ b/docs/accessanalyzer/12.0/solutions/unix/sharing/collection/overview.md @@ -16,6 +16,6 @@ The jobs in the 0.Collection job group are: - [UX_NFSConfiguration Job](/docs/accessanalyzer/12.0/solutions/unix/sharing/collection/ux_nfsconfiguration.md) – Collects NFS configuration information which will be further analyzed to identify and categorize risk within audited Unix and Linux environments -- [UX_NFSConfiguration Job](/docs/accessanalyzer/12.0/solutions/unix/sharing/collection/ux_nfsconfiguration.md) – Collects Samba configuration information which +- [UX_SambaConfiguration Job](/docs/accessanalyzer/12.0/solutions/unix/sharing/collection/ux_sambaconfiguration.md) – Collects Samba configuration information which will be further analyzed to identify and categorize risk within audited Unix and Linux environments diff --git a/docs/accessanalyzer/12.0/solutions/unix/sharing/collection/ux_nfsconfiguration.md b/docs/accessanalyzer/12.0/solutions/unix/sharing/collection/ux_nfsconfiguration.md index b4e61b14d8..7af14e4b13 100644 --- a/docs/accessanalyzer/12.0/solutions/unix/sharing/collection/ux_nfsconfiguration.md +++ b/docs/accessanalyzer/12.0/solutions/unix/sharing/collection/ux_nfsconfiguration.md @@ -31,7 +31,7 @@ Navigate to the **Unix** > **3.Sharing** > **0.Collection** > **UX_NFSConfigurat **Configure** node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/unix/sharing/collection/ux_sambaconfiguration.md b/docs/accessanalyzer/12.0/solutions/unix/sharing/collection/ux_sambaconfiguration.md index deb07b5411..e9672573d9 100644 --- a/docs/accessanalyzer/12.0/solutions/unix/sharing/collection/ux_sambaconfiguration.md +++ b/docs/accessanalyzer/12.0/solutions/unix/sharing/collection/ux_sambaconfiguration.md @@ -31,7 +31,7 @@ Navigate to the **Unix** > **3.Sharing** > **0.Collection** > **UX_SambaConfigur **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/unix/sharing/ux_nfs.md b/docs/accessanalyzer/12.0/solutions/unix/sharing/ux_nfs.md index dd8848e23e..a26798aaf3 100644 --- a/docs/accessanalyzer/12.0/solutions/unix/sharing/ux_nfs.md +++ b/docs/accessanalyzer/12.0/solutions/unix/sharing/ux_nfs.md @@ -15,7 +15,7 @@ Navigate to the **Unix** > **3.Sharing** > **UX_NFS** > **Configure** node and s to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/unix/sharing/ux_samba.md b/docs/accessanalyzer/12.0/solutions/unix/sharing/ux_samba.md index 7c8bf01f4b..86bf9534b3 100644 --- a/docs/accessanalyzer/12.0/solutions/unix/sharing/ux_samba.md +++ b/docs/accessanalyzer/12.0/solutions/unix/sharing/ux_samba.md @@ -15,7 +15,7 @@ View the analysis tasks by navigating to the **Unix** > **3.Sharing** > **UX_Sam node and select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -29,7 +29,7 @@ The default analysis tasks are: - Highlights hosts with a large number of risky shares – Creates an interim processing table in the database for use by downstream analysis and report generation -In addition to the tables and views created by the analysis task, the UX_NFS job produces the +In addition to the tables and views created by the analysis task, the UX_Samba job produces the following pre-configured report: | Report | Description | Default Tags | Report Elements | diff --git a/docs/accessanalyzer/12.0/solutions/unix/usersgroups/overview.md b/docs/accessanalyzer/12.0/solutions/unix/usersgroups/overview.md index 253b603662..ce6a694f9a 100644 --- a/docs/accessanalyzer/12.0/solutions/unix/usersgroups/overview.md +++ b/docs/accessanalyzer/12.0/solutions/unix/usersgroups/overview.md @@ -14,7 +14,7 @@ to pinpoint potential areas of administrative concern. The jobs in the 1.Users and Groups job group are: - [0.Collection > UX_UsersAndGroups Job](/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_usersandgroups.md) – Collects user and group related - information from /etc/shadow and their equivalents in order to provide details on user and group + information from /etc/shadow and their equivalents to provide details on user and group conditions to help pinpoint areas of administrative concerns - [UX_DuplicateGroups Job](/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_duplicategroups.md) – This job identifies duplicate groups within the audited Unix or Linux environment. Duplicate groups contain the same group membership as one diff --git a/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_duplicategroups.md b/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_duplicategroups.md index 8754258ef4..55ca95c1ca 100644 --- a/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_duplicategroups.md +++ b/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_duplicategroups.md @@ -16,7 +16,7 @@ Navigate to the **Unix** > **1.Users and Groups** > **UX_DuplicateGroups** > **C select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_emptygroups.md b/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_emptygroups.md index 60b746539c..8f4c216669 100644 --- a/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_emptygroups.md +++ b/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_emptygroups.md @@ -15,7 +15,7 @@ Navigate to the **Unix** > **1.Users and Groups** > **UX_EmptyGroups** > **Confi select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_largegroups.md b/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_largegroups.md index 6efd61b2dd..859cd9f8ea 100644 --- a/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_largegroups.md +++ b/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_largegroups.md @@ -12,7 +12,7 @@ resources, or how much access is being granted to resources through these groups ## Parameter Configuration -The Configuration section on a Job's overview page allows you to easily modify any customizable +Use the Configuration section on a Job's overview page to easily modify any customizable parameters used by analysis tasks in the job. See the [Parameter Configuration](/docs/accessanalyzer/12.0/admin/jobs/job/overview.md#parameter-configuration) topic for instructions on how to edit parameters on a job overview page. @@ -28,7 +28,7 @@ Navigate to the **Unix** > **1.Users and Groups** > **UX_LargeGroups** > **Confi select Analysis to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_localgroups.md b/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_localgroups.md index 941f9fbadb..5a0afc8aee 100644 --- a/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_localgroups.md +++ b/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_localgroups.md @@ -15,7 +15,7 @@ Navigate to the **Unix** > **1.Users and Groups** > **UX_LocalGroups** > **Confi select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_localusers.md b/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_localusers.md index 24ab8e585e..9f0588d9f6 100644 --- a/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_localusers.md +++ b/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_localusers.md @@ -15,7 +15,7 @@ Navigate to the **Unix** > **1.Users and Groups** > **UX_LocalUsers** > **Config select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_passwordsettings.md b/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_passwordsettings.md index e33e7c4378..6a74a5b976 100644 --- a/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_passwordsettings.md +++ b/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_passwordsettings.md @@ -15,7 +15,7 @@ Navigate to the **Unix** > **1.Users and Groups** > **UX_PasswordSettings** > ** select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_usersandgroups.md b/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_usersandgroups.md index 5ab286972f..1436f8e870 100644 --- a/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_usersandgroups.md +++ b/docs/accessanalyzer/12.0/solutions/unix/usersgroups/ux_usersandgroups.md @@ -7,7 +7,7 @@ sidebar_position: 10 # 0.Collection > UX_UsersAndGroups Job The UX_UsersAndGroups job collects user and group information from /etc/passwd, /etc/shadow, and -their equivalents in order to provide details on user and group conditions to help pinpoint +their equivalents to provide details on user and group conditions to help pinpoint potential areas of administrative concern. ![0.Collection > UX_UsersAndGroups Job in the Jobs Tree](/images/accessanalyzer/12.0/solutions/unix/usersgroups/collectionjobstree.webp) @@ -44,7 +44,7 @@ Navigate to the **Unix** > **1.Users and Groups** > **0.Collection** > **UX_User **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/windows/applications/sg_installedapplications.md b/docs/accessanalyzer/12.0/solutions/windows/applications/sg_installedapplications.md index e4c87739e2..b527629f3f 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/applications/sg_installedapplications.md +++ b/docs/accessanalyzer/12.0/solutions/windows/applications/sg_installedapplications.md @@ -19,7 +19,7 @@ The query is preconfigured for this job. Never modify the query. ![Queries for the SG_InstalledApplications Job](/images/accessanalyzer/12.0/solutions/windows/applications/installedapplicationsquery.webp) -The query for the SG_InstalledApplications job are: +The query for the SG_InstalledApplications job is: - Installed Applications – Targets all Windows servers known to Access Analyzer to determine installed applications @@ -30,7 +30,7 @@ Navigate to the **Windows** > **Applications** > **SG_InstalledApplications** > and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/windows/applications/sg_runatboot.md b/docs/accessanalyzer/12.0/solutions/windows/applications/sg_runatboot.md index 47f32fdafb..fa95787586 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/applications/sg_runatboot.md +++ b/docs/accessanalyzer/12.0/solutions/windows/applications/sg_runatboot.md @@ -31,7 +31,7 @@ Navigate to the **Windows** > **Applications** > **SG_RunAtBoot** > **Configure* **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/windows/applications/sg_scheduledtasks.md b/docs/accessanalyzer/12.0/solutions/windows/applications/sg_scheduledtasks.md index cf9e4cedd6..1616b0616b 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/applications/sg_scheduledtasks.md +++ b/docs/accessanalyzer/12.0/solutions/windows/applications/sg_scheduledtasks.md @@ -30,7 +30,7 @@ Navigate to the **Windows** > **Applications** > **SG_ScheduledTasks** > **Confi select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/windows/authentication/overview.md b/docs/accessanalyzer/12.0/solutions/windows/authentication/overview.md index 33c680ab2f..b814a532de 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/authentication/overview.md +++ b/docs/accessanalyzer/12.0/solutions/windows/authentication/overview.md @@ -15,15 +15,15 @@ The jobs in the Authentication job group are: - [SG_LSASettings Job](/docs/accessanalyzer/12.0/solutions/windows/authentication/sg_lsasettings.md) – This job lists LSA settings on all targeted hosts. In particular, the RunAsPPL, RestrictAnonymous, and ValidateKdcPacSignature keys are examined. If - these keys are not set to 1, a host is vulnerable to mimikatz and other exploitation tools. See + these keys aren't set to 1, a host is vulnerable to mimikatz and other exploitation tools. See the Microsoft [Configuring Additional LSA Protection](https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn408187(v=ws.11)) - article for additional ininformation. + article for additional information. - [SG_SecuritySupportProviders Job](/docs/accessanalyzer/12.0/solutions/windows/authentication/sg_securitysupportproviders.md) – This job identifies security support providers on all targeted hosts, highlighting potentially malicious SSPs - [SG_WDigestSettings Job](/docs/accessanalyzer/12.0/solutions/windows/authentication/sg_wdigestsettings.md) – This job lists WDigest settings on all targeted - hosts. In particular, the UseLogonCredentials key is examined. If the KB is not installed, and - this key is not set properly for a given host, cleartext passwords will be stored in memory. See + hosts. In particular, the UseLogonCredentials key is examined. If the KB isn't installed, and + this key isn't set properly for a given host, the host stores cleartext passwords in memory. See the [Microsoft Security Advisory](https://support.microsoft.com/en-us/help/2871997/microsoft-security-advisory-update-to-improve-credentials-protection-a) article for more information. diff --git a/docs/accessanalyzer/12.0/solutions/windows/authentication/sg_lsasettings.md b/docs/accessanalyzer/12.0/solutions/windows/authentication/sg_lsasettings.md index 7ec96d6971..b4ffb1d065 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/authentication/sg_lsasettings.md +++ b/docs/accessanalyzer/12.0/solutions/windows/authentication/sg_lsasettings.md @@ -6,8 +6,8 @@ sidebar_position: 20 # SG_LSASettings Job -The SG_LASettings job lists settings on all targeted hosts. In particular, the RunAsPPL, -RestrictAnonymous, and ValidateKdcPacSignature keys are examined. If these keys are not set to 1, a +The SG_LSASettings job lists LSA settings on all targeted hosts. In particular, the RunAsPPL, +RestrictAnonymous, and ValidateKdcPacSignature keys are examined. If these keys aren't set to 1, a host is vulnerable to mimikatz and other exploitation tools. See the Microsoft [Configuring Additional LSA Protection](https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn408187(v=ws.11)) article for additional information. @@ -34,7 +34,7 @@ Navigate to the **Windows** > **Authentication** > **SG_LSASettings** > **Config select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -43,7 +43,7 @@ preconfigured for this job. The default analysis tasks are: -- TrackRunAsPPL changes – Creates the SG_LSASettings_RunAsPPLChangeTracking table accessible under +- Track RunAsPPL changes – Creates the SG_LSASettings_RunAsPPLChangeTracking table accessible under the job’s Results node - List RunAsPPL setting details – Creates the SG_LSASettings_RunAsPPLDetails table accessible under the job’s Results node @@ -62,6 +62,6 @@ following pre-configured reports. | Report | Description | Default Tags | Report Elements | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Additional LSA Protection | This report summarizes RunAsPPL registry settings on targeted hosts. This key governs whether or not additional LSA protection is enabled. See the Microsoft [Configuring Additional LSA Protection](https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn408187(v=ws.11)) article for additional information. | None | This report is comprised of two elements:
  • Pie Chart – Displays additional LSA protection by host
  • Table – Provides additional LSA Protection Details
| -| PAC Validation | This report indicates whether or not PAC Validation is enabled on all targeted hosts. This is governed by the ValidateKdcPacSignature key. Default behavior in the event of this key's absence depends on the Windows version installed. See the Microsoft [Understanding Microsoft Kerberos PAC Validation](https://learn.microsoft.com/en-gb/archive/blogs/openspecification/understanding-microsoft-kerberos-pac-validation) article for additional information. | None | This report is comprised of two elements:
  • Pie Chart – Displays PAC validation status
  • Table – Provides PAC validation details
| -| Restrict Anonymous Access | This report summarizes RestrictAnonymous registry settings on targeted hosts. This key governs whether or not access over anonymous connections is enabled. See the Microsoft [Restrict Anonymous check](https://learn.microsoft.com/en-us/previous-versions/tn-archive/bb418944(v=technet.10)) article for additional information. | None | This report is comprised of two elements:
  • Pie Chart – Displays anonymous access by host
  • Table – Provides anonymous access details
| +| Additional LSA Protection | This report summarizes RunAsPPL registry settings on targeted hosts. This key governs whether additional LSA protection is enabled. See the Microsoft [Configuring Additional LSA Protection](https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn408187(v=ws.11)) article for additional information. | None | This report is comprised of two elements:
  • Pie Chart – Displays additional LSA protection by host
  • Table – Provides additional LSA Protection Details
| +| PAC Validation | This report indicates whether PAC Validation is enabled on all targeted hosts. This is governed by the ValidateKdcPacSignature key. Default behavior if this key is absent depends on the Windows version installed. See the Microsoft [Understanding Microsoft Kerberos PAC Validation](https://learn.microsoft.com/en-gb/archive/blogs/openspecification/understanding-microsoft-kerberos-pac-validation) article for additional information. | None | This report is comprised of two elements:
  • Pie Chart – Displays PAC validation status
  • Table – Provides PAC validation details
| +| Restrict Anonymous Access | This report summarizes RestrictAnonymous registry settings on targeted hosts. This key governs whether access over anonymous connections is enabled. See the Microsoft [Restrict Anonymous check](https://learn.microsoft.com/en-us/previous-versions/tn-archive/bb418944(v=technet.10)) article for additional information. | None | This report is comprised of two elements:
  • Pie Chart – Displays anonymous access by host
  • Table – Provides anonymous access details
| diff --git a/docs/accessanalyzer/12.0/solutions/windows/authentication/sg_securitysupportproviders.md b/docs/accessanalyzer/12.0/solutions/windows/authentication/sg_securitysupportproviders.md index b3ed9e0791..f54c266b01 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/authentication/sg_securitysupportproviders.md +++ b/docs/accessanalyzer/12.0/solutions/windows/authentication/sg_securitysupportproviders.md @@ -31,7 +31,7 @@ Navigate to the **Windows** > **Authentication** > **SG_SecuritySupportProviders node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/windows/authentication/sg_wdigestsettings.md b/docs/accessanalyzer/12.0/solutions/windows/authentication/sg_wdigestsettings.md index 0d3622fc86..2628eaa55e 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/authentication/sg_wdigestsettings.md +++ b/docs/accessanalyzer/12.0/solutions/windows/authentication/sg_wdigestsettings.md @@ -7,8 +7,8 @@ sidebar_position: 30 # SG_WDigestSettings Job The SG_WDigestSettings job lists WDigest settings on all targeted hosts. In particular, the -UseLogonCredentials key is examined. If this key is not set properly for a given host, cleartext -passwords will be stored in memory. See the +UseLogonCredentials key is examined. If this key isn't set properly for a given host, the host +stores cleartext passwords in memory. See the [Microsoft Security Advisory](https://support.microsoft.com/en-us/help/2871997/microsoft-security-advisory-update-to-improve-credentials-protection-a) article for more information. @@ -36,7 +36,7 @@ Navigate to the **Windows** > **Authentication** > **SG_WDigestSettings** > **Co select **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/windows/openaccess/recommended.md b/docs/accessanalyzer/12.0/solutions/windows/openaccess/recommended.md index 43a1433e24..17e17c635e 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/openaccess/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/windows/openaccess/recommended.md @@ -16,8 +16,8 @@ All Windows Servers **Connection Profile** -Configure a Connection Profile that is not part of the Domain Admin group. The report should be run -with a non-privileged user account. +Configure a Connection Profile that isn't part of the Domain Admin group. Run the report with a +non-privileged user account. **Schedule Frequency** @@ -25,7 +25,7 @@ This job in this job group should be scheduled to run daily. **Workflow** -**Step 1 –** Configure a Connection Profile that is not part of the Domain Admin group. +**Step 1 –** Configure a Connection Profile that isn't part of the Domain Admin group. **Step 2 –** Assign All Windows Servers under Hosts List Assignment. diff --git a/docs/accessanalyzer/12.0/solutions/windows/openaccess/sg_openfolders.md b/docs/accessanalyzer/12.0/solutions/windows/openaccess/sg_openfolders.md index 61a28e899a..7c311d6e9b 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/openaccess/sg_openfolders.md +++ b/docs/accessanalyzer/12.0/solutions/windows/openaccess/sg_openfolders.md @@ -19,15 +19,15 @@ The query for the SG_OpenFolders job is: - OpenAccess – Checks for folders with open access - (Optional) By default, the OpenAccess query used in this job has a search depth of 0 and will - return share-level information. If needed, the subfolder depth can be increased in the query + return share-level information. If needed, you can increase the subfolder depth in the query configuration. See the [Configure the OpenAccess Query](#configure-the-openaccess-query) topic for additional information. ### Configure the OpenAccess Query -The OpenAccess query has been preconfigured to run with the default settings. However, the subfolder -depth can optionally be increased on the Options page in the System Info Data Collector Wizard. -Follow the steps to customize the query. See the +The OpenAccess query has been preconfigured to run with the default settings. However, you can +optionally increase the subfolder depth on the Options page in the System Info Data Collector Wizard. +To customize the query, see the [SystemInfo Data Collector](/docs/accessanalyzer/12.0/admin/datacollector/systeminfo/overview.md) topic for additional information. @@ -45,7 +45,7 @@ Wizard opens. **Step 4 –** Navigate to the Options page and select the **Enumerate subfolders within shared folder** checkbox and then the **Limit returned subfolders depth to** checkbox. -**Step 5 –** Select the desired subfolders depth level using the arrows. Click **Next**. +**Step 5 –** Select the subfolders depth level you want using the arrows. Click **Next**. **Step 6 –** On the Summary page, click **Finish** to save the changes. @@ -57,7 +57,7 @@ Navigate to the **Windows** > **OpenAccess** > **SG_OpenFolders** > **Configure* **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/windows/overview.md b/docs/accessanalyzer/12.0/solutions/windows/overview.md index 8688269f74..d90e099926 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/overview.md +++ b/docs/accessanalyzer/12.0/solutions/windows/overview.md @@ -7,8 +7,8 @@ sidebar_position: 160 # Windows Solution The Windows Solution is designed to provide both high-level and granular views into any sized -organization's infrastructure. Systems are a critical business asset. In order to optimally support -and benefit the business, these systems must be running optimally and be fully secured. The Windows +organization's infrastructure. Systems are a critical business asset. To optimally support +and benefit the business, these systems must run efficiently and stay secure. The Windows Solution allows organizations to quickly inventory, assess, and secure their Windows desktop and server infrastructure from a central location. Key capabilities include privileged account discovery, security configuration and vulnerability assessment, compliance reporting, and asset @@ -29,7 +29,7 @@ topic for additional information. The Windows Solution requires a special Access Analyzer license. It can be installed from the Instant Job Wizard. See the [Instant Job Wizard](/docs/accessanalyzer/12.0/admin/jobs/instantjobs/overview.md) topic for -additional information. Once it has been installed in the Jobs tree, navigate to the solution: +additional information. After it's installed in the Jobs tree, navigate to the solution: **Jobs** > **Windows**. ![Windows Solution in the Jobs Tree](/images/accessanalyzer/12.0/solutions/windows/jobstree.webp) @@ -62,7 +62,7 @@ The jobs and job groups in the Windows Solution are: - [Security Utilities Job Group](/docs/accessanalyzer/12.0/solutions/windows/securityutilities/overview.md) – This group provides a series of security element checks across the audited environment - [SG_SecurityAssessment Job](/docs/accessanalyzer/12.0/solutions/windows/sg_securityassessment.md) – This job performs checks against Windows - security best practices in order to proactively identify critical security configurations that + security best practices to proactively identify critical security configurations that leave the environment vulnerable to attack. The result is a report which provides a listing of - findings by severity and category with corresponding details that can be used to prioritize and + findings by severity and category with corresponding details you can use to prioritize and remediate security issues. diff --git a/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/localadministrators/overview.md b/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/localadministrators/overview.md index cbd491ff6f..7ba010bee7 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/localadministrators/overview.md +++ b/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/localadministrators/overview.md @@ -21,4 +21,4 @@ The jobs in the Local Administrators group are: article for additional information. - [SG_Sessions Job](/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/localadministrators/sg_sessions.md) – This job lists sessions and logged on users from all targeted hosts. These active sessions and logged on users may have their hashes stored in memory on the - target machine, which could be leveraged in a Pass the Hash attack. + target machine, which could be used in a Pass the Hash attack. diff --git a/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/localadministrators/sg_localadmins.md b/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/localadministrators/sg_localadmins.md index bf995d8560..dbf2529dbb 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/localadministrators/sg_localadmins.md +++ b/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/localadministrators/sg_localadmins.md @@ -31,7 +31,7 @@ Navigate to the **Windows** > **Privileged Accounts** > **Local Administrators** **SG_LocalAdmins** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/localadministrators/sg_microsoftlaps.md b/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/localadministrators/sg_microsoftlaps.md index bbdec1f7c5..9f0d8669cd 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/localadministrators/sg_microsoftlaps.md +++ b/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/localadministrators/sg_microsoftlaps.md @@ -34,7 +34,7 @@ Navigate to the **Windows** > **Privileged Accounts** > **Local Administrators** **SG_MicrosoftLAPS** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/localadministrators/sg_sessions.md b/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/localadministrators/sg_sessions.md index d6dc15df3f..6d1375687a 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/localadministrators/sg_sessions.md +++ b/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/localadministrators/sg_sessions.md @@ -8,7 +8,7 @@ sidebar_position: 30 The SG_Sessions job lists sessions and logged on users from all targeted hosts. These active sessions and logged on users may have their hashes stored in memory on the target machine, which -could be leveraged in a Pass the Hash attack. +could be used in a Pass the Hash attack. ## Queries for the SG_Sessions Job diff --git a/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/logonrights/collection/overview.md b/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/logonrights/collection/overview.md index 4e6e8431a4..2c5b5a9ba8 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/logonrights/collection/overview.md +++ b/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/logonrights/collection/overview.md @@ -7,8 +7,8 @@ sidebar_position: 10 # Collection Job Group The Collection job group collects group policy settings, local users, and local group membership -information from Windows servers which will be further analyzed to provide insight into privileged -users within the environment. +information from Windows servers. It further analyzes this information to provide insight into +privileged users within the environment. ![Collection Job Group in the Jobs Tree](/images/accessanalyzer/12.0/solutions/windows/privilegedaccounts/logonrights/collection/collectionjobstree.webp) diff --git a/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/logonrights/collection/sg_localmembership.md b/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/logonrights/collection/sg_localmembership.md index fc51e9f1d9..48ffe4941f 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/logonrights/collection/sg_localmembership.md +++ b/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/logonrights/collection/sg_localmembership.md @@ -29,7 +29,7 @@ Navigate to the **Windows** > **Privileged Accounts** > **Logon Rights** > **Col **SG_LocalMembership** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/logonrights/collection/sg_localusers.md b/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/logonrights/collection/sg_localusers.md index 5f33fba205..c51325a14c 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/logonrights/collection/sg_localusers.md +++ b/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/logonrights/collection/sg_localusers.md @@ -29,7 +29,7 @@ Navigate to the **Windows** > **Privileged Accounts** > **Logon Rights** > **Col **SG_LocalUsers** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/logonrights/overview.md b/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/logonrights/overview.md index 4721bcc951..e742e83e3c 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/logonrights/overview.md +++ b/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/logonrights/overview.md @@ -13,8 +13,8 @@ The Logon Rights job group collects local policy information and reports on priv The jobs and job groups in the Logon Rights job group are: - [Collection Job Group](/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/logonrights/collection/overview.md) – The jobs within this group collect group policy - settings, local users, and local group membership from Windows servers which will be further - analyzed to provide insight into privileged users within the environment + settings, local users, and local group membership from Windows servers. This group further + analyzes the data to provide insight into privileged users within the environment - [SG_AccountPrivileges Job](/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/logonrights/sg_accountprivileges.md) – This job highlights account privileges across the audited environment, filtering out default privileges present on Windows servers - [SG_LocalPolicies Job](/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/logonrights/sg_localpolicies.md) – This job identifies privileged accounts across the diff --git a/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/logonrights/sg_accountprivileges.md b/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/logonrights/sg_accountprivileges.md index b47293fb0c..8d17703ac4 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/logonrights/sg_accountprivileges.md +++ b/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/logonrights/sg_accountprivileges.md @@ -33,7 +33,7 @@ Navigate to the **Windows** > **Privileged Accounts** > **Logon Rights** > **SG_AccountPrivileges** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/logonrights/sg_localpolicies.md b/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/logonrights/sg_localpolicies.md index 01036274ea..802621b9a7 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/logonrights/sg_localpolicies.md +++ b/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/logonrights/sg_localpolicies.md @@ -14,7 +14,7 @@ Navigate to the **Windows** > **Privileged Accounts** > **Logon Rights** > **SG_ **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -39,6 +39,6 @@ following pre-configured reports. | Report | Description | Default Tags | Report Elements | | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Local Account Network Access | This report highlights whether or not the **Local accounts** and **Local account and member of Administrators group** principals can be used to access a given host across the network. | None | This report is comprised of two elements:
  • Stacked Bar Chart – Displays a local accounts access enterprise summary
  • Table – Provides local account network access details
| +| Local Account Network Access | This report highlights whether the **Local accounts** and **Local account and member of Administrators group** principals can access a given host across the network. | None | This report is comprised of two elements:
  • Stacked Bar Chart – Displays a local accounts access enterprise summary
  • Table – Provides local account network access details
| | Local Security Policies | This report identifies effective local security policy assignments. In particular, **Allow log on locally**, **Log on as a batch job**, **Allow log on through Remote Desktop Services**, and **Log on as a service** are considered. Special attention is paid to policies with a large number of trustee assignments. It displays Largest Policies by Number of Domain User Accounts in a graph format, and Trustee Details in a table format. | GDPR, SOX, HIPAA, PCI-DSS, GLBA, ITAR, FERPA, FISMA, ISO27001 | This report is comprised of three elements:
  • Stacked Bar Chart – Displays largest policies by number of domain user accounts
  • Table – Provides details largest policies by number of domain user accounts
  • Table – Provides trustee details
| | Privileged Accounts | This report highlights user accounts with a large number of rights. | None | This report is comprised of two elements:
  • Stacked Bar Chart – Displays top trustees by logon rights
  • Table – Provides details on all trustees
| diff --git a/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/recommended.md b/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/recommended.md index ff4d781aa5..1c48f99543 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/recommended.md @@ -9,8 +9,8 @@ sidebar_position: 10 **Dependencies** - SG_AccountPrivileges – To populate the Local Administrator column, which is hidden by default, the - SG_LocalAdmins job must be run prior to running this job -- The **Logon Rights** > **Collection** job group must be run prior to running the SG_LocalPolicies + SG_LocalAdmins job must be run before running this job +- The **Logon Rights** > **Collection** job group must be run before running the SG_LocalPolicies job **Targeted Hosts** @@ -36,7 +36,7 @@ Domain Admin privileges if targeting domain controllers. - Assign the appropriate target host list under Hosts List Assignment for each job group **Step 2 –** Prerequisite: Ensure that the .Active Directory Inventory job group has successfully -run prior to running this job group. +run before running this job group. **Step 3 –** Schedule the Privileged Accounts job group or the individual job groups within the Privleged Accounts job group to run as desired. diff --git a/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/sg_serviceaccounts.md b/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/sg_serviceaccounts.md index 03b0f86063..915cc5e9a2 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/sg_serviceaccounts.md +++ b/docs/accessanalyzer/12.0/solutions/windows/privilegedaccounts/sg_serviceaccounts.md @@ -37,7 +37,7 @@ Navigate to the **Jobs** > **Windows** > **Privileged Accounts** > **Service Acc **SG_ServiceAccounts** > **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/windows/recommended.md b/docs/accessanalyzer/12.0/solutions/windows/recommended.md index 70696e9fb0..8697a0a535 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/windows/recommended.md @@ -8,7 +8,7 @@ sidebar_position: 10 **Dependencies** -The .Active Directory Inventory job group needs to be executed prior to running the Windows +The .Active Directory Inventory job group needs to be executed before running the Windows Solution. See individual sub-groups and jobs for the dependencies. diff --git a/docs/accessanalyzer/12.0/solutions/windows/securityutilities/openportscan/overview.md b/docs/accessanalyzer/12.0/solutions/windows/securityutilities/openportscan/overview.md index 7782f02abd..e189599d07 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/securityutilities/openportscan/overview.md +++ b/docs/accessanalyzer/12.0/solutions/windows/securityutilities/openportscan/overview.md @@ -6,9 +6,9 @@ sidebar_position: 20 # OpenPortScan Job Group -The OpenPortScan job group reveals all open ports along with the associated executable on the -targeted systems leveraging the jobs within this group. This is accomplished through remotely -executing a netstat command on the target hosts and collecting the results for reporting. +The OpenPortScan job group leverages the jobs within this group to reveal all open ports along with +the associated executable on the targeted systems. This is accomplished through remotely executing a +netstat command on the target hosts and collecting the results for reporting. ![OpenPortScan Job Group in the Jobs Tree](/images/accessanalyzer/12.0/solutions/windows/securityutilities/openportscan/openportscanjobstree.webp) diff --git a/docs/accessanalyzer/12.0/solutions/windows/securityutilities/openportscan/remoteopenport.md b/docs/accessanalyzer/12.0/solutions/windows/securityutilities/openportscan/remoteopenport.md index 4e135604fa..127887c3c7 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/securityutilities/openportscan/remoteopenport.md +++ b/docs/accessanalyzer/12.0/solutions/windows/securityutilities/openportscan/remoteopenport.md @@ -31,7 +31,7 @@ Navigate to the **Windows** > **Security Utilities** > **OpenPortScan** > **Remo **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/12.0/solutions/windows/securityutilities/openportscan/retrievenetstat.md b/docs/accessanalyzer/12.0/solutions/windows/securityutilities/openportscan/retrievenetstat.md index 0e12a759c8..8a3c514d66 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/securityutilities/openportscan/retrievenetstat.md +++ b/docs/accessanalyzer/12.0/solutions/windows/securityutilities/openportscan/retrievenetstat.md @@ -31,7 +31,7 @@ Navigate to the **Windows** > **Security Utilities** > **OpenPortScan** > **Retr **Configure** node and select **Analysis** to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: @@ -43,7 +43,7 @@ The default analysis tasks are: - **1. NETSTAT Result** – Creates the SA_RetrieveNetstat_NETSTAT table accessible under the job’s Results node -In addition to the tables and views created by the analysis tasks, the EX_DeliveryTimes job produces +In addition to the tables and views created by the analysis tasks, the RetrieveNetstat job produces the following pre-configured report. | Report | Description | Default Tags | Report Elements | diff --git a/docs/accessanalyzer/12.0/solutions/windows/securityutilities/overview.md b/docs/accessanalyzer/12.0/solutions/windows/securityutilities/overview.md index 8df9342680..7c68e403ad 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/securityutilities/overview.md +++ b/docs/accessanalyzer/12.0/solutions/windows/securityutilities/overview.md @@ -14,9 +14,9 @@ and collects the results for reporting. The jobs and job groups in the Security Utilities job group are: -- [OpenPortScan Job Group](/docs/accessanalyzer/12.0/solutions/windows/securityutilities/openportscan/overview.md) – Reveals all open ports along with the - associated executable on the targeted systems leveraging the jobs within this group. This is - accomplished through remotely executing a netstat command on the target hosts and collecting the - results for reporting. +- [OpenPortScan Job Group](/docs/accessanalyzer/12.0/solutions/windows/securityutilities/openportscan/overview.md) – Leverages the jobs within this group to reveal all + open ports along with the associated executable on the targeted systems. This is accomplished + through remotely executing a netstat command on the target hosts and collecting the results for + reporting. - [SG_PowerShellCommands Job](/docs/accessanalyzer/12.0/solutions/windows/securityutilities/sg_powershellcommands.md) – This job highlights instances where suspicious PowerShell commands have been found in a host’s PowerShell log diff --git a/docs/accessanalyzer/12.0/solutions/windows/securityutilities/recommended.md b/docs/accessanalyzer/12.0/solutions/windows/securityutilities/recommended.md index 53cdc89888..f38d0e9d7d 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/securityutilities/recommended.md +++ b/docs/accessanalyzer/12.0/solutions/windows/securityutilities/recommended.md @@ -8,12 +8,12 @@ sidebar_position: 10 **Dependencies** -The RemoteOpenPort job must be must be successfully run prior to running the RetrieveNetstat job. +The RemoteOpenPort job must be must be successfully run before running the RetrieveNetstat job. **Targeted Hosts** - OpenPortScan Job Group – There is no assigned host list for this job group. Configure a host list - with any desired systems to be audited prior to running this job group. Both jobs in the + with any desired systems to be audited before running this job group. Both jobs in the OpenPortScan job group need to be assigned the same target host list. - SG_PowerShellCommands – All Windows Servers (No DCs) @@ -30,7 +30,7 @@ This job group can be scheduled to run as desired. **Step 1 –** Ensure that the configured Connection Profile has local administrator privileges and Domain Admin privileges if targeting domain controllers. -**Step 2 –** Configure target hosts prior to running this job group. +**Step 2 –** Configure target hosts before running this job group. **Step 3 –** Remotely execute a netstat command on the target hosts. diff --git a/docs/accessanalyzer/12.0/solutions/windows/securityutilities/sg_powershellcommands.md b/docs/accessanalyzer/12.0/solutions/windows/securityutilities/sg_powershellcommands.md index 596b6a1202..278823d683 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/securityutilities/sg_powershellcommands.md +++ b/docs/accessanalyzer/12.0/solutions/windows/securityutilities/sg_powershellcommands.md @@ -6,8 +6,8 @@ sidebar_position: 30 # SG_PowerShellCommands Job -The SG_PowerShellCommands job lists suspicious PowerShell commands on all targeted hosts. The list -of commands considered can be customized by configuring the Check PowerShell Log query. +The SG_PowerShellCommands job lists suspicious PowerShell commands on all targeted hosts. You can +customize the list of commands considered by configuring the Check PowerShell Log query. ## Queries for the SG_PowerShellCommands Job @@ -25,7 +25,7 @@ The queries for the SG_PowerShellCommands job are: - Check PowerShell log – Checks the PowerShell log - - (Optional) This query can be configured. See the + - (Optional) You can configure this query. See the [Configure the Check PowerShell log Query](#configure-the-check-powershell-log-query) topic for additional information. @@ -33,8 +33,8 @@ The queries for the SG_PowerShellCommands job are: ### Configure the Check PowerShell log Query -The Check PowerShell log query has been preconfigured to run with the default settings. However, the -new criteria can optionally be added on the Criteria page in the Smart Log Data Collector Wizard. +The Check PowerShell log query has been preconfigured to run with the default settings. However, you +can optionally add new criteria on the Criteria page in the Smart Log Data Collector Wizard. **Step 1 –** Navigate to the **Jobs** > **Windows** > **Security Utilities** > **SG_PowerShellCommands** > **Configure** node and select **Queries**. Select the **Check PowerShell @@ -53,7 +53,7 @@ is accessible. **Step 5 –** On the Criteria page, click the **press the button to add a new condition** box. -**Step 6 –** Enter the desired conditions. +**Step 6 –** Enter the conditions you want. **Step 7 –** Click **Next** to navigate to the Summary page and click **Finish**. @@ -65,7 +65,7 @@ View the analysis tasks by navigating to the **Windows** > **Security Utilities* **SG_PowerShellCommands** > **Configure** node and selecting **Analysis**. :::warning -Do not modify or deselect the selected analysis tasks. The analysis tasks are +Don't modify or deselect the selected analysis tasks. The analysis tasks are preconfigured for this job. ::: @@ -87,7 +87,7 @@ The optional analysis tasks is: [Configure the Notify on Suspicious Commands Analysis Task](#configure-the-notify-on-suspicious-commands-analysis-task) topic for additional information. -In addition to the tables and views created by the analysis tasks, the EX_DeliveryTimes job produces +In addition to the tables and views created by the analysis tasks, the SG_PowerShellCommands job produces the following pre-configured report. | Report | Description | Default Tags | Report Elements | @@ -97,7 +97,7 @@ the following pre-configured report. ### Configure the Notify on Suspicious Commands Analysis Task -Follow these steps to configure the notification analysis task. +To configure the notification analysis task: **Step 1 –** Navigate to the **Jobs** > **Windows** > **Security Utilities** > **SG_PowerShellCommands** > **Configure** node and select **Analysis**. @@ -107,14 +107,14 @@ task and click **Analysis Configuration**. The Notification Data Analysis Module ![Notification Data Analysis Module wizard SMTP properties page](/images/accessanalyzer/12.0/solutions/windows/securityutilities/powershellcommandsnotifysmtp.webp) -**Step 3 –** Use the **Next** button to navigate to the SMTP page. Do not make changes to the +**Step 3 –** Use the **Next** button to navigate to the SMTP page. Don't make changes to the preceding pages. ![Recipients section](/images/accessanalyzer/12.0/solutions/windows/securityutilities/powershellcommandsnotifyrecipients.webp) **Step 4 –** In the Recipients section, provide the email addresses or distribution lists (fully -qualified address) for those who are to receive this notification. Multiple addresses can be -provided. You can use the following options: +qualified address) for those who are to receive this notification. You can provide multiple +addresses. You can use the following options: - Add – Add an email address to the E-mail field - Remove – Remove an email address from the Recipients list @@ -123,12 +123,12 @@ provided. You can use the following options: ![Message section](/images/accessanalyzer/12.0/solutions/windows/securityutilities/powershellcommandsnotifymessage.webp) -**Step 5 –** In the Message section, edit the **Subject**. It is not recommended to remove any -parameters. Then, customize the email content in the textbox to provide an explanation of the -notification to the recipients. +**Step 5 –** In the Message section, edit the **Subject**. Don't remove any parameters. Then, +customize the email content in the textbox to provide an explanation of the notification to the +recipients. **Step 6 –** To save these configuration changes, use the **Next** to navigate to the Summary page. -Do not make changes to any other pages. Click **Finish**. The Notification Data Analysis Module +Don't make changes to any other pages. Click **Finish**. The Notification Data Analysis Module window closes. **Step 7 –** This notification analysis task is now configured to send emails. In the Analysis diff --git a/docs/accessanalyzer/12.0/solutions/windows/sg_securityassessment.md b/docs/accessanalyzer/12.0/solutions/windows/sg_securityassessment.md index f3054a90b5..015582e4c0 100644 --- a/docs/accessanalyzer/12.0/solutions/windows/sg_securityassessment.md +++ b/docs/accessanalyzer/12.0/solutions/windows/sg_securityassessment.md @@ -6,10 +6,10 @@ sidebar_position: 70 # SG_SecurityAssessment Job -The SG_SecurityAssessment job performs checks against Windows security best practices in order to +The SG_SecurityAssessment job performs checks against Windows security best practices to proactively identify critical security configurations that leave the environment vulnerable to attack. The result is a report which provides a listing of findings by severity and category with -corresponding details that can be used to prioritize and remediate security issues. +corresponding details you can use to prioritize and remediate security issues. ![SG_SecurityAssessment Job in the Jobs Tree](/images/accessanalyzer/12.0/solutions/windows/securityassessmentjobstree.webp) @@ -64,7 +64,7 @@ Navigate to the **Windows** > **SG_SecurityAssessment** > **Configure** node and to view the analysis tasks. :::warning -Do not modify or deselect the selected analysis task. The analysis task is +Don't modify or deselect the selected analysis task. The analysis task is preconfigured for this job. ::: diff --git a/docs/accessanalyzer/2601/configurations/application-settings.md b/docs/accessanalyzer/2601/configurations/application-settings.md index b52fc75ff3..2fb8eb5235 100644 --- a/docs/accessanalyzer/2601/configurations/application-settings.md +++ b/docs/accessanalyzer/2601/configurations/application-settings.md @@ -19,7 +19,7 @@ This page is available to users with the **Administrator** role only. | **Feature Flags** | Enable or disable product features and integrations | | **Scanning** | Execution history retention for scans and identity syncs | | **File Scanning** | File size limits and excluded extensions for SMB and SharePoint scans | -| **Activity Monitor** | TCP listener behavior and enrollment token for NAM agent connections | +| **Activity Monitor** | TCP listener behavior and enrollment token for Netwrix Activity Monitor (NAM) agent connections | | **Branding** | Company name and support email displayed in the application | ## Feature Flags @@ -31,7 +31,7 @@ Feature flags enable or disable specific product capabilities. Changes take effe | **MIP Labeling** | Enabled | Enables Microsoft Information Protection (MIP) sensitivity label management for SMB file shares and SharePoint Online. When disabled, the label handling options on the Sensitive Data page are hidden and no labels are applied to or read from files during scans. | :::note -Disabling MIP Labeling does not remove existing labels from files. It stops Access Analyzer from applying or updating labels in future scans. +Disabling MIP Labeling doesn't remove existing labels from files. It stops Access Analyzer from applying or updating labels in future scans. ::: ## File Scanning @@ -39,7 +39,7 @@ Disabling MIP Labeling does not remove existing labels from files. It stops Acce These settings control which files are included in content classification during sensitive data scans. Adjusting them can reduce scan duration in environments with large binary or media files. :::note -File metadata — name, size, permissions, and owner — is always collected regardless of file size or extension settings. These limits apply only to content classification during sensitive data scans. +Access Analyzer always collects file metadata — name, size, permissions, and owner — regardless of file size or extension settings. These limits apply only to content classification during sensitive data scans. ::: ### SMB / CIFS @@ -71,7 +71,7 @@ Reducing retention frees database storage. Increasing it extends the history ava ## Activity Monitor -The Activity Monitor category contains settings for the built-in TCP listener and the enrollment token used when connecting Netwrix Activity Monitor (NAM) agents to Access Analyzer. +The Activity Monitor category contains settings for the built-in TCP listener and the enrollment token used when connecting NAM agents to Access Analyzer. ### Enrollment Token @@ -101,6 +101,6 @@ The remaining settings in the Activity Monitor category control TCP listener beh ## Resetting and cache behavior -**Resetting to default:** Each setting has a reset action that restores the factory default value. Resetting one setting does not affect any other settings. +**Resetting to default:** Each setting has a reset action that restores the factory default value. Resetting one setting doesn't affect any other settings. -**Cache:** Application Settings are cached for up to 5 minutes. Changes take effect immediately on the instance that applied them. Other running instances pick up the change within 5 minutes. To force an immediate refresh across all instances, click **Refresh Cache** at the top of the page. +**Cache:** Access Analyzer caches Application Settings for up to 5 minutes. Changes take effect immediately on the instance that applied them. Other running instances pick up the change within 5 minutes. To force an immediate refresh across all instances, click **Refresh Cache** at the top of the page. diff --git a/docs/accessanalyzer/2601/configurations/logs.md b/docs/accessanalyzer/2601/configurations/logs.md index fe3890fab4..f093db1b9b 100644 --- a/docs/accessanalyzer/2601/configurations/logs.md +++ b/docs/accessanalyzer/2601/configurations/logs.md @@ -6,7 +6,7 @@ sidebar_position: 90 # System Logs -The System Logs page displays application-wide log entries generated by Access Analyzer services. Use it to monitor activity, investigate scan failures, and collect diagnostic information for support. +The System Logs page displays application-wide log entries that Access Analyzer services generate. Use it to monitor activity, investigate scan failures, and collect diagnostic information for support. Navigate to **Configuration** > **System Logs** to open the page. @@ -24,7 +24,7 @@ Each log entry contains the following fields. ## Filter logs -The toolbar above the log table provides five independent filters. All active filters are applied together — only entries matching all conditions are shown. Filter state is preserved in the page URL, so you can bookmark or share a filtered view. +The toolbar above the log table provides five independent filters. All active filters combine — the table shows only entries matching all conditions. The page URL preserves filter state, so you can bookmark or share a filtered view. **Search** @@ -43,7 +43,7 @@ Select a severity level to show only entries at that level. The default shows al **Component** -Select one or more components to show entries from those services only. The component list is populated from services that have generated logs. +Select one or more components to show entries from those services only. The component list includes services that have generated logs. **Source** @@ -55,7 +55,7 @@ Use the **From** and **To** fields to restrict entries to a specific time window ## Sort and paginate -The log table is sorted by timestamp, newest first by default. Click the **Timestamp** column header to reverse the sort order. +Access Analyzer sorts the log table by timestamp, newest first by default. Click the **Timestamp** column header to reverse the sort order. Use the rows-per-page control to display 10, 25, 50, or 100 entries per page. @@ -67,7 +67,7 @@ To export log entries for offline review or to provide to support: 2. Click the **Download** button in the toolbar. 3. Select **JSON** or **CSV** from the dropdown. -The export file is named `system-logs-{timestamp}` and reflects all currently active filters. Exports are limited to 10,000 entries. +Access Analyzer names the export file `system-logs-{timestamp}`; the file reflects all active filters. Access Analyzer limits exports to 10,000 entries. CSV exports include the following columns: Timestamp, Level, Message, Trace ID, Span ID, and Attributes. @@ -75,7 +75,7 @@ CSV exports include the following columns: Timestamp, Level, Message, Trace ID, ### Investigate a scan failure -When a scan does not complete as expected: +When a scan doesn't complete as expected: 1. Set the **Source** filter to the data source the scan was running against. 2. Set the **Level** filter to **Error**. @@ -97,7 +97,7 @@ Use this approach to identify what was happening in the system around the time o 1. Open the **Component** dropdown. 2. Select the service you want to focus on. -Multiple components can be selected at the same time to compare activity across services. +You can select multiple components at the same time to compare activity across services. ### Collect logs for a support case diff --git a/docs/accessanalyzer/2601/configurations/sensitive-data.md b/docs/accessanalyzer/2601/configurations/sensitive-data.md index 3cced196f6..ccf5345e5f 100644 --- a/docs/accessanalyzer/2601/configurations/sensitive-data.md +++ b/docs/accessanalyzer/2601/configurations/sensitive-data.md @@ -6,7 +6,7 @@ sidebar_position: 30 # Sensitive Data -The Sensitive Data configuration page defines which types of sensitive content Access Analyzer identifies during scans, whether to run optical character recognition (OCR) on images, and how Microsoft Information Protection (MIP) sensitivity labels are applied to matching files. These settings apply globally and serve as the default for all sensitive data scans. +The Sensitive Data configuration page defines which types of sensitive content Access Analyzer identifies during scans, whether to run optical character recognition (OCR) on images, and how Access Analyzer applies Microsoft Information Protection (MIP) sensitivity labels to matching files. These settings apply globally and serve as the default for all sensitive data scans. Navigate to **Configuration** > **Sensitive Data** to view and update the configuration. @@ -17,7 +17,7 @@ The page has two sections: ## MIP configuration -The MIP configuration section connects Access Analyzer to a Microsoft Entra ID tenant. When a tenant is connected, Access Analyzer retrieves the sensitivity labels defined in your organization's MIP policy and makes them available for mapping in the Sensitive Data Types table. +The MIP configuration section connects Access Analyzer to a Microsoft Entra ID tenant. After you connect a tenant, Access Analyzer retrieves the sensitivity labels defined in your organization's MIP policy and makes them available for mapping in the Sensitive Data Types table. ### Select a tenant @@ -98,7 +98,7 @@ You can assign a MIP label to each enabled data type. When Access Analyzer finds 4. Click **Save Configuration**. :::note -Enabling a data type and assigning a label are independent. A data type with no label assigned is still detected during scans — Access Analyzer identifies matching files but doesn't apply a MIP label to them. +Enabling a data type and assigning a label are independent. Even without an assigned label, Access Analyzer still detects the data type during scans — it identifies matching files but doesn't apply a MIP label to them. ::: ## OCR @@ -117,11 +117,11 @@ The **Label Settings** drawer controls whether Access Analyzer writes MIP sensit These settings apply globally and can be overridden per-scan in the scan configuration. :::note -Label write-back applies to **File Server and SharePoint Online sensitive data scans only**. Entra ID and Active Directory scans do not support label application. +Label write-back applies to **File Server and SharePoint Online sensitive data scans only**. Entra ID and Active Directory scans don't support label application. ::: :::note -Label write-back only occurs when **both** conditions are met: a MIP label is mapped to the detected data type in the Sensitive Data Types table, **and** the relevant option below is enabled. All options are off by default — by default, Access Analyzer detects and classifies files but does not write any labels to files. +Label write-back only occurs when you meet **both** conditions: you map a MIP label to the detected data type in the Sensitive Data Types table, **and** you enable the relevant option in [Options](#options). All options are off by default — by default, Access Analyzer detects and classifies files but doesn't write any labels to files. ::: ### Options @@ -130,10 +130,10 @@ Label write-back only occurs when **both** conditions are met: a MIP label is ma When enabled, Access Analyzer removes the MIP label from a file if a subsequent scan finds the file no longer matches any enabled sensitive data type. Off by default. **Allow overwriting existing labels** -When enabled, Access Analyzer applies the mapped label to files that already have a MIP label assigned. When disabled, files that already carry any MIP label are skipped — only unlabeled files receive a label. Off by default. +When enabled, Access Analyzer applies the mapped label to files that already have a MIP label assigned. When disabled, Access Analyzer skips files that already carry any MIP label — only unlabeled files receive a label. Off by default. - **Allow downgrading labels** *(requires Allow overwriting existing labels to be on)* - When enabled, Access Analyzer can replace a higher-priority label with a lower-priority one (for example, replacing "Confidential" with "General"). When disabled, only upgrades or equal-priority replacements are applied. This option is unavailable when **Allow overwriting existing labels** is off. Off by default. + When enabled, Access Analyzer can replace a higher-priority label with a lower-priority one (for example, replacing "Confidential" with "General"). When disabled, Access Analyzer applies only upgrades or equal-priority replacements. This option is unavailable when **Allow overwriting existing labels** is off. Off by default. To configure label handling: diff --git a/docs/accessanalyzer/2601/configurations/service-accounts/client-id-certificate.md b/docs/accessanalyzer/2601/configurations/service-accounts/client-id-certificate.md index cbc7eded42..123216bd34 100644 --- a/docs/accessanalyzer/2601/configurations/service-accounts/client-id-certificate.md +++ b/docs/accessanalyzer/2601/configurations/service-accounts/client-id-certificate.md @@ -8,14 +8,14 @@ sidebar_position: 4 The Client ID/Certificate credential type authenticates with SharePoint Online using certificate-based authentication. Use this credential type when configuring SharePoint Online source groups. -This requires a registered application in your Entra ID tenant. The certificate itself is generated by the source group wizard — you don't create or upload it here. +This requires a registered application in your Entra ID tenant. The source group wizard generates the certificate itself — you don't create or upload it here. ## Create a Client ID/Certificate service account 1. Navigate to **Configuration** > **Service Accounts**. 2. Click **Add Service Account**. 3. In the **Name** field, enter a descriptive name for this service account. -4. From the **Service account type** drop-down, select **Client ID/Certificate**. +4. From the **Service account type** dropdown, select **Client ID/Certificate**. ![Add service account form showing Client ID/Certificate fields: name, client application ID, and tenant ID](/images/accessanalyzer/2601/configurations/add-service-account-certificate.png) @@ -33,8 +33,8 @@ This requires a registered application in your Entra ID tenant. The certificate ## Certificate -The certificate is not entered in the service account form. When you set up a SharePoint Online source group, the wizard includes a **Generate and Download Certificate** step that creates the certificate and downloads it to your machine. You then upload the certificate to your registered Entra ID application in the Azure portal before testing the connection. +You don't enter the certificate in the service account form. When you set up a SharePoint Online source group, the wizard includes a **Generate and Download Certificate** step that creates the certificate and downloads it to your machine. You then upload the certificate to your registered Entra ID application in the Azure portal before testing the connection. -If you update the service account on an existing source group, the new account's certificate must be uploaded to the registered app before saving. +If you update the service account on an existing source group, you must upload the new account's certificate to the registered app before saving. For steps to register the application and upload the certificate, see [SharePoint Online Connector Requirements](../../connectors/sharepoint-online/overview.md). diff --git a/docs/accessanalyzer/2601/configurations/service-accounts/client-id-secret.md b/docs/accessanalyzer/2601/configurations/service-accounts/client-id-secret.md index ed14b2d54a..254fd2415c 100644 --- a/docs/accessanalyzer/2601/configurations/service-accounts/client-id-secret.md +++ b/docs/accessanalyzer/2601/configurations/service-accounts/client-id-secret.md @@ -8,14 +8,14 @@ sidebar_position: 3 The Client ID/Secret credential type authenticates with Microsoft Entra ID via the Microsoft Graph API. Use this credential type when configuring Entra ID source groups. -This requires a registered application in your Entra ID tenant with the appropriate API permissions granted. +This requires a registered application in your Entra ID tenant with the appropriate API permissions. ## Create a Client ID/Secret service account 1. Navigate to **Configuration** > **Service Accounts**. 2. Click **Add Service Account**. 3. In the **Name** field, enter a descriptive name for this service account. -4. From the **Service account type** drop-down, select **Client ID/Secret**. +4. From the **Service account type** dropdown, select **Client ID/Secret**. ![Add service account form showing Client ID/Secret fields: name, client application ID, and client secret](/images/accessanalyzer/2601/configurations/add-service-account-client-secret.png) diff --git a/docs/accessanalyzer/2601/configurations/service-accounts/overview.md b/docs/accessanalyzer/2601/configurations/service-accounts/overview.md index ac39ff44b0..d8d8a0d429 100644 --- a/docs/accessanalyzer/2601/configurations/service-accounts/overview.md +++ b/docs/accessanalyzer/2601/configurations/service-accounts/overview.md @@ -31,6 +31,6 @@ You can create a service account in two ways: ## Editing service accounts -Credential fields — passwords and client secrets — are never pre-populated when you edit an existing service account. You must re-enter them each time you save changes. +Access Analyzer never pre-populates credential fields — passwords and client secrets — when you edit an existing service account. You must re-enter them each time you save changes. Updating the service account on an existing source group replaces the credentials used for all future scans in that source group. Ensure the replacement account has the required permissions before saving. diff --git a/docs/accessanalyzer/2601/configurations/service-accounts/ssh-username-key.md b/docs/accessanalyzer/2601/configurations/service-accounts/ssh-username-key.md index 52824412a0..07bd38a7cd 100644 --- a/docs/accessanalyzer/2601/configurations/service-accounts/ssh-username-key.md +++ b/docs/accessanalyzer/2601/configurations/service-accounts/ssh-username-key.md @@ -13,7 +13,7 @@ The SSH Username/Key credential type authenticates using an SSH username and pri 1. Navigate to **Configuration** > **Service Accounts**. 2. Click **Add Service Account**. 3. In the **Name** field, enter a descriptive name for this service account. -4. From the **Service account type** drop-down, select **SSH Username/Key**. +4. From the **Service account type** dropdown, select **SSH Username/Key**. ![Add service account form showing SSH Username/Key fields: name, SSH username, and SSH key](/images/accessanalyzer/2601/configurations/add-service-account-ssh.png) diff --git a/docs/accessanalyzer/2601/configurations/service-accounts/username-password.md b/docs/accessanalyzer/2601/configurations/service-accounts/username-password.md index 669b47733c..75b349dc07 100644 --- a/docs/accessanalyzer/2601/configurations/service-accounts/username-password.md +++ b/docs/accessanalyzer/2601/configurations/service-accounts/username-password.md @@ -6,14 +6,14 @@ sidebar_position: 2 # Username and Password -The Username and Password credential type is used by Active Directory and file server source groups. Both require a domain account whose credentials Access Analyzer uses to connect and authenticate during scans. +Active Directory and file server source groups use the Username and Password credential type. Both require a domain account whose credentials Access Analyzer uses to connect and authenticate during scans. ## Create a Username/Password service account 1. Navigate to **Configuration** > **Service Accounts**. 2. Click **Add Service Account**. 3. In the **Name** field, enter a descriptive name for this service account. -4. From the **Service account type** drop-down, select **Username/Password**. +4. From the **Service account type** dropdown, select **Username/Password**. ![Add service account form showing Username/Password fields: name, username, and password](/images/accessanalyzer/2601/configurations/add-service-account-username-password.png) diff --git a/docs/accessanalyzer/2601/configurations/source-groups/scan-executions.md b/docs/accessanalyzer/2601/configurations/source-groups/scan-executions.md index 25364459e3..63e6053e6d 100644 --- a/docs/accessanalyzer/2601/configurations/source-groups/scan-executions.md +++ b/docs/accessanalyzer/2601/configurations/source-groups/scan-executions.md @@ -6,7 +6,7 @@ sidebar_position: 3 # Scan Executions -A scan execution is a single run of a scan at a specific point in time. Each time Access Analyzer runs a scan — whether triggered by a schedule or manually — it creates a new scan execution record. Execution history is retained per source so you can review past run outcomes. +A scan execution is a single run of a scan at a specific point in time. Each time Access Analyzer runs a scan — whether triggered by a schedule or manually — it creates a new scan execution record. Access Analyzer retains execution history per source so you can review past run outcomes. Scan executions are distinct from scan configurations. The [scan configuration](scans.md) defines what to collect and when. The scan execution records what happened during a specific run. @@ -24,11 +24,11 @@ Scan executions are distinct from scan configurations. The [scan configuration]( | **Completed** | The execution finished successfully. | | **Stopped** | The execution was manually stopped before completing. Partial results may have been collected. | | **Cancelled** | The execution was cancelled before it started or early in the run. No results were collected. | -| **Failed** | The execution encountered an error and did not complete. Check the execution log for details. | +| **Failed** | The execution encountered an error and didn't complete. Check the execution log for details. | ## Source group scan status -The source groups list displays an aggregate scan status for each group. This is computed from the most recent scan execution across all sources in the group, using the following priority order: +The source groups list displays an aggregate scan status for each group. Access Analyzer computes this from the most recent scan execution across all sources in the group, using the following priority order: 1. **Paused** — One or more sources has a paused execution, and none are running. 2. **Running** — One or more sources has an execution in a pending, running, pausing, resuming, stopping, or post-processing state. @@ -41,7 +41,7 @@ This means a group shows **Running** even if only one source is actively scannin ## Blocked operations during active executions -Several operations are blocked while a source has an execution in an active state (pending, running, pausing, paused, resuming, stopping, or post-processing): +Access Analyzer blocks several operations while a source has an execution in an active state (pending, running, pausing, paused, resuming, stopping, or post-processing): - **Deleting a source group** — Stop all active scans before deleting the group. - **Removing a source from a group** — Stop the source's active scan before removing it. diff --git a/docs/accessanalyzer/2601/configurations/source-groups/scanners/best-practices.md b/docs/accessanalyzer/2601/configurations/source-groups/scanners/best-practices.md index deee012cd1..8aab2b0e06 100644 --- a/docs/accessanalyzer/2601/configurations/source-groups/scanners/best-practices.md +++ b/docs/accessanalyzer/2601/configurations/source-groups/scanners/best-practices.md @@ -18,11 +18,11 @@ Common labeling patterns: | Route by geographic region | `region=us-east`, `region=eu-west` | | Dedicate scanners to high-sensitivity source groups | `tier=restricted` | -Define a labeling scheme before deploying scanners and apply it consistently. Labels assigned to a source group are used by all scan executions in that group — you don't need to set them per source. +Define a labeling scheme before deploying scanners and apply it consistently. All scan executions in a source group use the labels assigned to that group — you don't need to set them per source. ### Label matching behavior -When a source group has multiple labels configured, a scan is routed to any scanner that matches **at least one** of those label pairs — not all of them. Design your label scheme with this in mind: a scanner carrying `region=us-east` will receive jobs from a source group labeled `region=us-east, tier=restricted` even if the scanner does not carry the `tier=restricted` label. +When a source group has multiple labels configured, Access Analyzer routes a scan to any scanner that matches **at least one** of those label pairs — not all of them. Design your label scheme with this in mind: a scanner carrying `region=us-east` will receive jobs from a source group labeled `region=us-east, tier=restricted` even if the scanner doesn't carry the `tier=restricted` label. For strict isolation, use a single label per source group or ensure scanners are labeled precisely to match only the intended groups. @@ -35,15 +35,15 @@ Label keys and values entered in the Deploy Scanner wizard must follow these rul | Key | Letters, digits, hyphens | 53 characters | | Value | Letters, digits, hyphens, underscores, dots | 63 characters | -Both key and value must start with a letter or digit. Labels are stored with a `dspm.netwrix.com/scanner-` prefix internally — you do not need to include this prefix when entering labels in the wizard. +Both key and value must start with a letter or digit. Access Analyzer stores labels with a `dspm.netwrix.com/scanner-` prefix internally — you don't need to include this prefix when entering labels in the wizard. :::note -The label `scanner-default` is reserved for the built-in system scanner and can't be applied to custom scanners. +Access Analyzer reserves the label `scanner-default` for the built-in system scanner; you can't apply it to custom scanners. ::: ## Plan for scanner redundancy -Assign the same label to multiple scanners that cover the same environment. Scanners sharing a label form a pool — when a scan job is dispatched, Access Analyzer routes it to any available scanner in the pool. If one scanner is offline, unhealthy, or busy, the job routes to another scanner carrying the same label automatically. +Assign the same label to multiple scanners that cover the same environment. Scanners sharing a label form a pool, and Access Analyzer routes each scan job to any available scanner in the pool. If one scanner is offline, unhealthy, or busy, the job routes to another scanner carrying the same label automatically. A single scanner per label is a single point of failure. For production environments, deploy at least two scanners per label. This also distributes scan load across the pool when multiple source groups target the same label simultaneously. @@ -63,7 +63,7 @@ A safe approach is to increase by 2–3 at a time and monitor scan completion ti ## Monitor scanner health -Check the Scanners page regularly to review scanner health status. A scanner in Warning state is under resource pressure — disk, memory, or CPU — and scan performance may be degraded. A scanner in Error state has reported health issues and needs investigation before running additional scans. +Check the Scanners page regularly to review scanner health status. A scanner in Warning state is under resource pressure — disk, memory, or CPU — and scan performance may degrade. A scanner in Error state has reported health issues and needs investigation before running additional scans. Common causes of Warning and Error states: diff --git a/docs/accessanalyzer/2601/configurations/source-groups/scanners/deploy-scanner.md b/docs/accessanalyzer/2601/configurations/source-groups/scanners/deploy-scanner.md index f01f6eeac3..3838a52a4c 100644 --- a/docs/accessanalyzer/2601/configurations/source-groups/scanners/deploy-scanner.md +++ b/docs/accessanalyzer/2601/configurations/source-groups/scanners/deploy-scanner.md @@ -11,7 +11,7 @@ Deploying a scanner registers a remote Linux host as a custom scanner node in Ac ## Before you begin - Confirm the scanner host meets all [requirements](./requirements.md). -- Create an **SSH Username / SSH Key** service account in Access Analyzer with access to the scanner host. You can also create it inline during the wizard — see step 7 below. +- Create an **SSH Username / SSH Key** service account in Access Analyzer with access to the scanner host. You can also create it inline during the wizard — see step 7. - Have the scanner host's public SSH host key ready. You can retrieve it by running the following command from any machine that can reach the host, replacing `` with the scanner's hostname or IP address: ```bash @@ -30,15 +30,15 @@ Deploying a scanner registers a remote Linux host as a custom scanner node in Ac 6. In the **SSH Port** field, enter the SSH port if your scanner host uses a non-standard port. Defaults to `22` if left blank. 7. In the **Service Account** dropdown, select the SSH Username / SSH Key account that has access to the scanner host. - - To create a new service account without leaving the wizard, click **+** next to the dropdown. The account type is pre-set to SSH Username / SSH Key. After saving, the new account is automatically selected and all other fields are preserved. + - To create a new service account without leaving the wizard, click **+** next to the dropdown. The wizard pre-sets the account type to SSH Username / SSH Key. After saving, it automatically selects the new account and preserves all other fields. - To edit the selected account, click the pencil icon. The SSH key field is blank in edit mode — you must re-enter the private key before saving. -8. Under **Labels**, add at least one label. You must add at least one label before the scanner can be deployed — the **Deploy** button remains disabled until a label is applied. +8. Under **Labels**, add at least one label. You must add at least one label before you can deploy the scanner — the **Deploy** button remains disabled until you apply a label. - Enter a key and a value, then click **Add**. The label appears as a chip. - To add additional labels, repeat the process. - To remove a label, click the **×** on its chip. - - Label keys and values are automatically normalized to lowercase with spaces converted to hyphens. + - Access Analyzer automatically normalizes label keys and values to lowercase and converts spaces to hyphens. :::tip Previously used labels appear as chips you can click to pre-fill the key and value fields. This helps you apply consistent labels across multiple scanners. @@ -52,7 +52,7 @@ Deploying a scanner registers a remote Linux host as a custom scanner node in Ac Registration runs automatically and typically completes within five minutes. During registration, Access Analyzer: -1. Runs a preflight check on the scanner host to verify all requirements are met (curl, bash, passwordless sudo, disk space, memory, and CPU). +1. Runs a preflight check on the scanner host to verify it meets all requirements (curl, bash, passwordless sudo, disk space, memory, and CPU). 2. Downloads and installs k3s (a lightweight Kubernetes distribution) on the scanner host. 3. Joins the scanner host to the Access Analyzer Kubernetes cluster as a worker node. 4. Applies the labels you specified. @@ -61,7 +61,7 @@ If registration takes longer than five minutes, check network connectivity and c ## After deployment -The scanner appears immediately in the Scanners table. Its health status shows **Healthy** once the node has fully joined the cluster. +The scanner appears immediately in the Scanners table. Its health status shows **Healthy** when the node has fully joined the cluster. To use the scanner, assign it to a source group by selecting **Custom scanner** under **Scanner Location** when setting up or editing a source group, and matching its label. See [Set Up File Server Source Group](../../../gettingstarted/file-servers/set-up-source-group.md) or the equivalent guide for your connector. diff --git a/docs/accessanalyzer/2601/configurations/source-groups/scanners/manage-scanners.md b/docs/accessanalyzer/2601/configurations/source-groups/scanners/manage-scanners.md index 57e3b4d3ac..f0461512dd 100644 --- a/docs/accessanalyzer/2601/configurations/source-groups/scanners/manage-scanners.md +++ b/docs/accessanalyzer/2601/configurations/source-groups/scanners/manage-scanners.md @@ -30,9 +30,9 @@ Each row in the table represents one registered scanner. | Healthy | Green | The scanner node is reachable and operating normally | | Warning | Yellow | The node is reachable but under resource pressure (disk, memory, or CPU) | | Error | Red | The node is reachable but in an unhealthy state | -| Offline | Gray | The node is not reachable from the Access Analyzer server | +| Offline | Gray | The node isn't reachable from the Access Analyzer server | -Scans may perform poorly on a scanner in Warning state — consider resolving the resource pressure before scheduling large scans. Investigate the scanner host when the status is Error. An Offline scanner cannot run scans — source groups that target it will not execute until the scanner comes back online or a different scanner with the matching label becomes available. +Scans may perform poorly on a scanner in Warning state — consider resolving the resource pressure before scheduling large scans. Investigate the scanner host when the status is Error. An Offline scanner can't run scans — source groups that target it will not execute until the scanner comes back online or a different scanner with the matching label becomes available. ## Scan status @@ -63,4 +63,4 @@ To delete a scanner: 2. Click the delete icon on the scanner row. 3. Confirm the deletion. -A scanner can only be deleted when no scan jobs are running on it. If scans are in progress, wait for them to complete before deleting. The system scanner (built-in scanner on the Access Analyzer server) cannot be deleted. +You can only delete a scanner when no scan jobs are running on it. If scans are in progress, wait for them to complete before deleting. You can't delete the system scanner (built-in scanner on the Access Analyzer server). diff --git a/docs/accessanalyzer/2601/configurations/source-groups/scanners/overview.md b/docs/accessanalyzer/2601/configurations/source-groups/scanners/overview.md index 9b0ec2f071..a3ff3a1650 100644 --- a/docs/accessanalyzer/2601/configurations/source-groups/scanners/overview.md +++ b/docs/accessanalyzer/2601/configurations/source-groups/scanners/overview.md @@ -53,9 +53,9 @@ Labels let you: - Route scans to geographically local scanners (`region=us-east`, `region=eu-west`) - Dedicate scanners to high-sensitivity source groups (`tier=restricted`) -At least one label is required on every custom scanner. Multiple scanners can share the same label — when a source group targets a label that multiple scanners carry, any of those scanners can run the job. +Every custom scanner requires at least one label. Multiple scanners can share the same label — when a source group targets a label that multiple scanners carry, any of those scanners can run the job. -The system scanner does not use labels. Selecting **System scanner** in a source group always uses the built-in scanner on the Access Analyzer server. +The system scanner doesn't use labels. Selecting **System scanner** in a source group always uses the built-in scanner on the Access Analyzer server. ## Related pages diff --git a/docs/accessanalyzer/2601/configurations/source-groups/scanners/requirements.md b/docs/accessanalyzer/2601/configurations/source-groups/scanners/requirements.md index 841765cb9d..dbb0260d36 100644 --- a/docs/accessanalyzer/2601/configurations/source-groups/scanners/requirements.md +++ b/docs/accessanalyzer/2601/configurations/source-groups/scanners/requirements.md @@ -10,7 +10,7 @@ These requirements apply to any Linux host you want to register as a custom scan ## Operating system -Access Analyzer supports any Linux distribution as a scanner host. Ubuntu 20.04 LTS or later is recommended. +Access Analyzer supports any Linux distribution as a scanner host. Netwrix recommends Ubuntu 20.04 LTS or later. Access Analyzer registers the scanner by connecting over SSH and running an automated installation script. The script installs [k3s](https://k3s.io/) — a lightweight Kubernetes distribution — and joins the host to the Access Analyzer cluster as a worker node. @@ -53,7 +53,7 @@ When you click **Deploy** in the Deploy Scanner wizard, Access Analyzer runs the | 22 | TCP | Access Analyzer → Scanner | SSH connection during registration only | | 6443 | TCP | Scanner → Access Analyzer | Kubernetes API — ongoing job dispatch | -Port 22 is only required during the initial registration. After the scanner is registered, the scanner host connects outbound to the Access Analyzer server on port 6443 to receive and run scan jobs. Port 22 can be restricted or closed after registration is complete. +Access Analyzer only requires port 22 during the initial registration. After registration completes, the scanner host connects outbound to the Access Analyzer server on port 6443 to receive and run scan jobs. You can restrict or close port 22 after registration completes. :::note The SSH port defaults to **22** but is configurable in the Deploy Scanner wizard. If your scanner host runs SSH on a non-standard port, enter it in the **SSH Port** field during deployment. @@ -61,7 +61,7 @@ The SSH port defaults to **22** but is configurable in the Deploy Scanner wizard ### Internet access -The registration script downloads the k3s installer from `https://get.k3s.io`. The scanner host must be able to reach this URL **during registration only**. After registration completes, internet access is not required for normal scan operation. +The registration script downloads the k3s installer from `https://get.k3s.io`. The scanner host must be able to reach this URL **during registration only**. After registration completes, normal scan operation doesn't require internet access. ## Service account @@ -71,7 +71,7 @@ Scanner deployment requires an **SSH Username / SSH Key** service account in Acc - Use an **unencrypted** private key in PEM format :::warning -Passphrase-protected private keys are not supported. The registration script will fail if the key requires a passphrase. Use a key generated without a passphrase, or strip the passphrase before creating the service account. +Access Analyzer doesn't support passphrase-protected private keys. The registration script will fail if the key requires a passphrase. Use a key generated without a passphrase, or strip the passphrase before creating the service account. ::: See [SSH Username / SSH Key](../../service-accounts/ssh-username-key.md) to create this account. You can also create it inline from the Deploy Scanner wizard using the **+** button next to the Service Account field without navigating away. diff --git a/docs/accessanalyzer/2601/configurations/source-groups/scans.md b/docs/accessanalyzer/2601/configurations/source-groups/scans.md index 9fcb677e43..e2fd271f85 100644 --- a/docs/accessanalyzer/2601/configurations/source-groups/scans.md +++ b/docs/accessanalyzer/2601/configurations/source-groups/scans.md @@ -23,7 +23,7 @@ The scan types available depend on the source type: Enumerates permissions, folder-level ACLs, sharing links, and access rights across File Server and SharePoint Online sources. Identifies who has access to what across your data sources. -Access scans include a **concurrent** option that allows multiple file paths or objects within a single source to be scanned in parallel. Enable this when scanning large file servers or SharePoint sites to reduce total scan time. +Access scans include a **concurrent** option that scans multiple file paths or objects within a single source in parallel. Enable this when scanning large file servers or SharePoint sites to reduce total scan time. ### Sensitive Data Scan @@ -33,7 +33,7 @@ Sensitive Data Scans include a **concurrent** option that allows classification ### Active Directory Inventory -Synchronizes users, groups, group memberships, and security-relevant attributes from Active Directory domains. The inventory is used to resolve identity information across all other scan types and to populate the Active Directory dashboard. +Synchronizes users, groups, group memberships, and security-relevant attributes from Active Directory domains. Access Analyzer uses the inventory to resolve identity information across all other scan types and to populate the Active Directory dashboard. ### Users, Groups and Roles @@ -43,27 +43,27 @@ Synchronizes users, groups, and role assignments from your Microsoft Entra ID (A When you create a source group, the setup wizard collects scan parameters on page 3 and creates scan configurations that apply to all sources added to the group. Each scan configuration includes: -- **Scan type** — the type of scan to run (see [Scan types](#scan-types) above) +- **Scan type** — the type of scan to run (see [Scan types](#scan-types)) - **Concurrent** — whether to parallelize scanning within a single source (Access Scan and Sensitive Data Scan only) -- **Scan location** — which scanner handles the scan (see [Scan location](#scan-location) below) -- **Schedule** — when and how often the scan runs automatically (see [Schedule](#schedule) below) +- **Scan location** — which scanner handles the scan (see [Scan location](#scan-location)) +- **Schedule** — when and how often the scan runs automatically (see [Schedule](#schedule)) - **Scan parameters** — source-type-specific settings such as scope, depth, and included paths. These vary by connector. Individual sources can override the group-level scan configuration if their requirements differ from the group default. ## Scan location -The **Scan location** setting determines which scanner component executes the scan. It is configured per scan type during source group creation. +The **Scan location** setting determines which scanner component executes the scan. You configure it per scan type during source group creation. | Location | Description | Applicable Source Types | | --- | --- | --- | | **System scanner** | The Access Analyzer service connects directly to the source. This is the default and requires no additional configuration. | Entra ID, SharePoint Online | | **Scanner label** | Routes the scan to a registered edge scanner pool that matches the specified label. The edge scanner connects to the source on behalf of Access Analyzer. | Active Directory, File Server | -For Active Directory and File Server source groups, selecting a scanner label routes all scans in that group to the matching edge scanner pool. If no edge scanners are registered with that label, the scan cannot run. See [Scanners](scanners/overview.md) for setup and label management. +For Active Directory and File Server source groups, selecting a scanner label routes all scans in that group to the matching edge scanner pool. If no edge scanners carry that label, the scan can't run. See [Scanners](scanners/overview.md) for setup and label management. :::note -Entra ID and SharePoint Online source groups always use the system scanner. The scan location setting is not configurable for those source types. +Entra ID and SharePoint Online source groups always use the system scanner. The scan location setting isn't configurable for those source types. ::: ## Schedule @@ -75,7 +75,7 @@ The schedule determines when a scan runs automatically. You configure the schedu | Option | Description | | --- | --- | | **Run scan now** | Starts the scan immediately when the source group is saved. No recurring schedule is set. | -| **Run scan at** | Schedules a single one-time run at a specific date and time. The scan does not repeat after that run. | +| **Run scan at** | Schedules a single one-time run at a specific date and time. The scan doesn't repeat after that run. | | **Advanced** | Sets a recurring schedule using a cron expression. Use this for daily, weekly, or custom interval schedules. | ### Cron schedule format @@ -101,8 +101,8 @@ Advanced scheduling uses standard 5-field cron syntax: | `0 2 1 * *` | Monthly on the 1st at 2:00 AM | | `0 */6 * * *` | Every 6 hours | -Schedule times are evaluated in the server's local timezone. +Access Analyzer evaluates schedule times in the server's local timezone. :::note -If no schedule is configured, the scan does not run automatically. Run it manually from the source groups list using the **Run** action. +If you don't configure a schedule, the scan doesn't run automatically. Run it manually from the source groups list using the **Run** action. ::: diff --git a/docs/accessanalyzer/2601/configurations/source-groups/source-groups.md b/docs/accessanalyzer/2601/configurations/source-groups/source-groups.md index 52296d36e7..3a208b6b43 100644 --- a/docs/accessanalyzer/2601/configurations/source-groups/source-groups.md +++ b/docs/accessanalyzer/2601/configurations/source-groups/source-groups.md @@ -30,14 +30,14 @@ Use the search field to filter by name. You can sort by any column and filter by 1. Click **Add Source Group**. 2. Enter a **Name** and optional **Description**. Names must be unique (case-insensitive) and between 1 and 255 characters. -3. Select the **Source Type**. This value is permanent — it can't be changed after the group is created. +3. Select the **Source Type**. This value is permanent — you can't change it after you create the group. 4. Select or create a **Service Account**. The wizard filters available accounts to those compatible with the selected source type. To create a new account inline, click **+** next to the field. 5. For Active Directory and File Server groups, optionally add **Scanner Labels** to route scans to a specific scanner pool. See [Scanners](scanners/overview.md). 6. Add sources and configure scan parameters. You can also add sources later from the group detail view. 7. Click **Save**. :::warning -Changing the source type is not possible after a source group is created. If you need a different source type, create a new source group and delete the original. +You can't change the source type after you create a source group. If you need a different source type, create a new source group and delete the original. ::: ## Edit a source group @@ -50,7 +50,7 @@ Changing the source type is not possible after a source group is created. If you - Status (Active or Inactive) 3. Click **Save**. -The source type cannot be changed. If you update the service account, the new credentials apply to all future scans in the group — verify the replacement account has the required permissions before saving. +You can't change the source type. If you update the service account, the new credentials apply to all future scans in the group — verify the replacement account has the required permissions before saving. ## Add sources to a group @@ -84,7 +84,7 @@ To stop all running and pending scans in a group, click **Stop** in the actions 2. Confirm the deletion. :::warning -Deleting a source group permanently deletes all sources it contains. This action can't be undone. +Deleting a source group permanently deletes all sources it contains. You can't undo this action. ::: You can't delete a source group while any of its scans are in a pending, running, pausing, paused, resuming, stopping, or post-processing state. Stop all active scans before deleting. diff --git a/docs/accessanalyzer/2601/configurations/users.md b/docs/accessanalyzer/2601/configurations/users.md index 440698d7d3..75ea22e53d 100644 --- a/docs/accessanalyzer/2601/configurations/users.md +++ b/docs/accessanalyzer/2601/configurations/users.md @@ -55,7 +55,7 @@ On first login, Access Analyzer prompts you to enroll an authenticator app for M Keep the bootstrap account active as an emergency recovery account, but don't use it for routine user management. Create at least one named User Admin account during initial setup and use that account for ongoing administration. ::: -For the full first-login walkthrough, see [Quick Install — Step 5](/docs/accessanalyzer/2601/install/quickinstall#step-6-sign-in). +For the full first-login walkthrough, see [Quick Install — Step 6](/docs/accessanalyzer/2601/install/quickinstall#step-6-sign-in). ## Recommended initial setup @@ -64,7 +64,7 @@ After installation, complete the following steps in order before handing the pro | Step | Action | Notes | | --- | --- | --- | | **1** | Sign in as `admin@dspm.local` | Uses the bootstrap User Admin account. Retrieve the password using the kubectl command above. | -| **2** | Create at least one named **User Admin** | Provides a dedicated account for user management with no system configuration access. Use this account for ongoing user administration so that Administrator accounts aren't required for routine user changes. | +| **2** | Create at least one named **User Admin** | Provides a dedicated account for user management with no system configuration access. Use this account for ongoing user administration so that routine user changes don't require Administrator accounts. | | **3** | Create at least one **Administrator** | Grants full access — system configuration and user management. This is typically the person responsible for setting up and maintaining the product. | | **4** | Create **Viewer** accounts as needed | Optional. Add Viewer accounts for stakeholders who need read-only access to dashboards and reports. | | **5** | Sign out of the bootstrap account | Do day-to-day work from named accounts. | @@ -80,7 +80,7 @@ Use this procedure when Access Analyzer manages passwords directly. 1. Click **Add User**. 2. Enter a **Name**. Names must be between 2 and 100 characters. 3. Enter an **Email** address. Email addresses must be unique across all users (case-insensitive). -4. Select a **Role**: **Administrator**, **User Admin**, or **Viewer**. The default is **Viewer** — the intentionally conservative default. Only assign Administrator or User Admin after confirming the user's responsibilities. +4. Select a **Role**: **Administrator**, **User Admin**, or **Viewer**. The default is **Viewer**, an intentionally conservative choice. Only assign Administrator or User Admin after confirming the user's responsibilities. 5. Enter a **Password** and confirm it. 6. Click **Create User**. @@ -96,12 +96,12 @@ Password requirements for local accounts: ### Add a user (Identity Provider) -When your deployment is configured to use an external Identity Provider, you can pre-provision an account before the user's first sign-in. Access Analyzer creates the account record and links it to the user's IdP identity when they sign in for the first time. +When you configure your deployment to use an external Identity Provider, you can pre-provision an account before the user's first sign-in. Access Analyzer creates the account record and links it to the user's IdP identity when they sign in for the first time. 1. Click **Add User**. 2. Enter a **Name**. Names must be between 2 and 100 characters. 3. Enter an **Email** address. The email must match the address the user has in your IdP exactly, including case. -4. Select a **Role**: **Administrator**, **User Admin**, or **Viewer**. The default is **Viewer** — the intentionally conservative default. Only assign Administrator or User Admin after confirming the user's responsibilities. +4. Select a **Role**: **Administrator**, **User Admin**, or **Viewer**. The default is **Viewer**, an intentionally conservative choice. Only assign Administrator or User Admin after confirming the user's responsibilities. 5. Click **Create User**. No password is required. The account is ready for the user to sign in through your IdP. @@ -124,7 +124,7 @@ What you can change depends on the account type: | Identity Provider — pre-provisioned (hasn't signed in yet) | Name, Email, Role | | Identity Provider — provisioned (has signed in at least once) | Role only | -Name and email are locked for provisioned IdP accounts because those values come from the IdP token. To change them, update the user's profile in your IdP. +Access Analyzer locks name and email for provisioned IdP accounts because those values come from the IdP token. To change them, update the user's profile in your IdP. ## Activate a user diff --git a/docs/accessanalyzer/2601/connectors/activedirectory.md b/docs/accessanalyzer/2601/connectors/activedirectory.md index fc76232824..481abb347c 100644 --- a/docs/accessanalyzer/2601/connectors/activedirectory.md +++ b/docs/accessanalyzer/2601/connectors/activedirectory.md @@ -45,4 +45,4 @@ Open the following ports on all domain controllers you want to scan: ## Next steps -Once requirements are met, see [Set Up Active Directory Source Group](../gettingstarted/active-directory/set-up-source-group.md) to configure your first scan. +After you meet the requirements, see [Set Up Active Directory Source Group](../gettingstarted/active-directory/set-up-source-group.md) to configure your first scan. diff --git a/docs/accessanalyzer/2601/connectors/entra-id/app-registration-secret.md b/docs/accessanalyzer/2601/connectors/entra-id/app-registration-secret.md index 8e52193448..998720b323 100644 --- a/docs/accessanalyzer/2601/connectors/entra-id/app-registration-secret.md +++ b/docs/accessanalyzer/2601/connectors/entra-id/app-registration-secret.md @@ -6,7 +6,7 @@ sidebar_position: 30 # Client Secret Configuration -Access Analyzer authenticates to Microsoft Entra ID using a client secret. The client secret is generated within your registered Microsoft Entra ID application and provided to Access Analyzer when configuring the Entra ID connector. +Access Analyzer authenticates to Microsoft Entra ID using a client secret. You generate the client secret within your registered Microsoft Entra ID application and provide it to Access Analyzer when configuring the Entra ID connector. ## Generate a client secret @@ -25,15 +25,15 @@ Access Analyzer authenticates to Microsoft Entra ID using a client secret. The c - **Description** — Enter a description for the secret - **Expires** — Select an expiration period -7. Click **Add**. The client secret value is displayed in the **Value** column. +7. Click **Add**. Access Analyzer displays the client secret value in the **Value** column. :::warning -Copy the client secret value immediately. Once you navigate away from this page, the value can't be retrieved and you'll need to create a new secret. +Copy the client secret value immediately. After you navigate away from this page, you can't retrieve the value and you'll need to create a new secret. ::: ## Assign roles to the app -The registered application must be assigned to the **Global Administrator** role for Entra ID data collection. +You must assign the registered application to the **Global Administrator** role for Entra ID data collection. 1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com/). @@ -51,4 +51,4 @@ The registered application must be assigned to the **Global Administrator** role 8. Search for and select your registered application. -9. Click **Add**. The application is listed on the Assignments page. +9. Click **Add**. Access Analyzer lists the application on the Assignments page. diff --git a/docs/accessanalyzer/2601/connectors/entra-id/entra-requirements.md b/docs/accessanalyzer/2601/connectors/entra-id/entra-requirements.md index cd4c6be7bf..89887a9415 100644 --- a/docs/accessanalyzer/2601/connectors/entra-id/entra-requirements.md +++ b/docs/accessanalyzer/2601/connectors/entra-id/entra-requirements.md @@ -9,11 +9,11 @@ sidebar_position: 20 Access Analyzer connects to Microsoft Entra ID through a registered application using OAuth2 client credentials. You must register a dedicated Microsoft Entra ID application for Access Analyzer and grant it the required permissions before adding Entra ID as a data source. :::note -A user account with the **Global Administrator**, **Application Administrator**, or **Cloud Application Administrator** role is required to register an application and grant admin consent for permissions. +You need a user account with the **Global Administrator**, **Application Administrator**, or **Cloud Application Administrator** role to register an application and grant admin consent for permissions. ::: :::note -The registered application must be assigned to the **Global Administrator** role for Entra ID data collection. +You must assign the registered application to the **Global Administrator** role for Entra ID data collection. ::: ## Register an app in Microsoft Entra ID diff --git a/docs/accessanalyzer/2601/connectors/file-servers/celerra.md b/docs/accessanalyzer/2601/connectors/file-servers/celerra.md index 2af864e745..73229e8d4c 100644 --- a/docs/accessanalyzer/2601/connectors/file-servers/celerra.md +++ b/docs/accessanalyzer/2601/connectors/file-servers/celerra.md @@ -8,7 +8,7 @@ sidebar_position: 50 The Dell EMC Celerra connector reads file shares over SMB to collect share permissions, folder and file ACLs, and file contents for sensitive data classification. The connector doesn't require agent installation on the storage system. -Dell EMC Celerra serves CIFS/SMB file shares through Data Movers. The CIFS service must be licensed and configured on each Data Mover you want to scan. +Dell EMC Celerra serves CIFS/SMB file shares through Data Movers. You must license and configure the CIFS service on each Data Mover you want to scan. ## Supported versions diff --git a/docs/accessanalyzer/2601/connectors/file-servers/cifs.md b/docs/accessanalyzer/2601/connectors/file-servers/cifs.md index 19aa9567af..8cd41acaf7 100644 --- a/docs/accessanalyzer/2601/connectors/file-servers/cifs.md +++ b/docs/accessanalyzer/2601/connectors/file-servers/cifs.md @@ -38,4 +38,4 @@ For domain-based Distributed File System (DFS) namespaces, the scan targets the ## Sensitive Data Discovery -Sensitive Data Discovery (SDD) is handled by the scanner infrastructure. No additional software is required on the target file server. +The scanner infrastructure handles Sensitive Data Discovery (SDD). The target file server doesn't need additional software. diff --git a/docs/accessanalyzer/2601/connectors/file-servers/dell-unity.md b/docs/accessanalyzer/2601/connectors/file-servers/dell-unity.md index 42062d1235..fe36433953 100644 --- a/docs/accessanalyzer/2601/connectors/file-servers/dell-unity.md +++ b/docs/accessanalyzer/2601/connectors/file-servers/dell-unity.md @@ -8,7 +8,7 @@ sidebar_position: 40 The Dell Unity connector reads file shares over SMB to collect share permissions, folder and file ACLs, and file contents for sensitive data classification. The connector doesn't require agent installation on the storage system. -Dell Unity serves CIFS/SMB shares through NAS servers. The CIFS protocol must be configured on each NAS server you want to scan. +Dell Unity serves CIFS/SMB shares through NAS servers. You must configure the CIFS protocol on each NAS server you want to scan. ## Supported versions diff --git a/docs/accessanalyzer/2601/connectors/file-servers/isilon-powerscale.md b/docs/accessanalyzer/2601/connectors/file-servers/isilon-powerscale.md index bd212a1748..a1bca8dff4 100644 --- a/docs/accessanalyzer/2601/connectors/file-servers/isilon-powerscale.md +++ b/docs/accessanalyzer/2601/connectors/file-servers/isilon-powerscale.md @@ -8,7 +8,7 @@ sidebar_position: 30 The Dell Isilon / PowerScale connector reads file shares over SMB to collect share permissions, folder and file ACLs, and file contents for sensitive data classification. The connector doesn't require agent installation on the storage system. -Dell Isilon / PowerScale (based on the OneFS operating system) organizes SMB shares within access zones. The SMB service must be enabled on each access zone you want to scan. +Dell Isilon / PowerScale (based on the OneFS operating system) organizes SMB shares within access zones. You must enable the SMB service on each access zone you want to scan. ## Supported versions diff --git a/docs/accessanalyzer/2601/connectors/file-servers/netapp.md b/docs/accessanalyzer/2601/connectors/file-servers/netapp.md index ec02a17fee..9fb5a87116 100644 --- a/docs/accessanalyzer/2601/connectors/file-servers/netapp.md +++ b/docs/accessanalyzer/2601/connectors/file-servers/netapp.md @@ -8,7 +8,7 @@ sidebar_position: 20 The NetApp ONTAP connector reads file shares over SMB to collect share permissions, folder and file ACLs, and file contents for sensitive data classification. The connector doesn't require agent installation on the storage system. -NetApp ONTAP serves CIFS/SMB shares through Storage Virtual Machines (SVMs). Each SVM has its own CIFS server that the connector connects to independently. The CIFS service must be licensed and enabled on each SVM you want to scan. +NetApp ONTAP serves CIFS/SMB shares through Storage Virtual Machines (SVMs). Each SVM has its own CIFS server that the connector connects to independently. You must license and enable the CIFS service on each SVM you want to scan. ## Supported versions @@ -38,4 +38,4 @@ To add a NetApp ONTAP SVM to Access Analyzer, see [Set Up File Server Source Gro ## Known behavior -NetApp ONTAP may return invalid timestamp values on some systems due to a Year 2038 overflow issue in the ONTAP CIFS implementation. Access Analyzer detects and handles this automatically — affected timestamps are recorded as empty rather than causing a scan error. +NetApp ONTAP may return invalid timestamp values on some systems due to a Year 2038 overflow issue in the ONTAP CIFS implementation. Access Analyzer detects this automatically and records affected timestamps as empty instead of causing a scan error. diff --git a/docs/accessanalyzer/2601/connectors/file-servers/vnx.md b/docs/accessanalyzer/2601/connectors/file-servers/vnx.md index aec64b98c6..d1d8de521a 100644 --- a/docs/accessanalyzer/2601/connectors/file-servers/vnx.md +++ b/docs/accessanalyzer/2601/connectors/file-servers/vnx.md @@ -8,14 +8,14 @@ sidebar_position: 60 The Dell EMC VNX connector reads file shares over SMB to collect share permissions, folder and file ACLs, and file contents for sensitive data classification. The connector doesn't require agent installation on the storage system. -Dell EMC VNX serves CIFS/SMB file shares through Data Movers. The CIFS service must be licensed and configured on each Data Mover you want to scan. +Dell EMC VNX serves CIFS/SMB file shares through Data Movers. You must license and configure the CIFS service on each Data Mover you want to scan. ## Supported versions - VNX2 series (NAS code 8.x) - VNX series (NAS code 7.x) -VNX2 is the second-generation platform; VNX is the original series. Both use the same Data Mover architecture and are configured identically in Access Analyzer. +VNX2 is the second-generation platform; VNX is the original series. Both use the same Data Mover architecture, and you configure them identically in Access Analyzer. ## Requirements diff --git a/docs/accessanalyzer/2601/connectors/sharepoint-online/azure-permissions.md b/docs/accessanalyzer/2601/connectors/sharepoint-online/azure-permissions.md index 08002986af..534e8abf0a 100644 --- a/docs/accessanalyzer/2601/connectors/sharepoint-online/azure-permissions.md +++ b/docs/accessanalyzer/2601/connectors/sharepoint-online/azure-permissions.md @@ -9,7 +9,7 @@ sidebar_position: 10 Access Analyzer connects to SharePoint Online through a Microsoft Entra ID registered application using certificate-based authentication. You must register a dedicated application for Access Analyzer and grant it the required API permissions before adding SharePoint Online as a data source. :::note -A user account with the Global Administrator, Application Administrator, or Cloud Application Administrator role is required to register an application and grant admin consent for permissions. +You need a user account with the Global Administrator, Application Administrator, or Cloud Application Administrator role to register an application and grant admin consent for permissions. ::: ## Register an app in Microsoft Entra ID @@ -47,7 +47,7 @@ The Overview page for the newly registered application opens. Note the following 6. Click an API to access its permissions, then click the **Application permissions** tab. -7. Select the required permissions for each API (see table below). +7. Select the required permissions for each API (see the following table). 8. Click **Add Permissions**. diff --git a/docs/accessanalyzer/2601/connectors/sharepoint-online/overview.md b/docs/accessanalyzer/2601/connectors/sharepoint-online/overview.md index b0c4878e7c..2e8c60e2fa 100644 --- a/docs/accessanalyzer/2601/connectors/sharepoint-online/overview.md +++ b/docs/accessanalyzer/2601/connectors/sharepoint-online/overview.md @@ -32,4 +32,4 @@ When configuring the SharePoint Online source in Access Analyzer, you need the f - **Application (client) ID** - **Directory (tenant) ID** -The certificate is generated by Access Analyzer during source group setup. You download it and upload it to your registered Microsoft Entra ID application before the connection can be tested. +Access Analyzer generates the certificate during source group setup. You download it and upload it to your registered Microsoft Entra ID application before you can test the connection. diff --git a/docs/accessanalyzer/2601/connectors/sharepoint-online/tenant-certificate-config.md b/docs/accessanalyzer/2601/connectors/sharepoint-online/tenant-certificate-config.md index 8661d4f323..eea9bd85ae 100644 --- a/docs/accessanalyzer/2601/connectors/sharepoint-online/tenant-certificate-config.md +++ b/docs/accessanalyzer/2601/connectors/sharepoint-online/tenant-certificate-config.md @@ -28,6 +28,6 @@ Access Analyzer authenticates with SharePoint Online using certificate-based aut 9. Enter a description for the certificate. -10. Click **Add**. The certificate is uploaded to the registered application. +10. Click **Add** to upload the certificate to the registered application. After uploading, return to the Access Analyzer source group wizard and click **Test Connection** to verify the authentication. diff --git a/docs/accessanalyzer/2601/dashboards-reports/my-reports.md b/docs/accessanalyzer/2601/dashboards-reports/my-reports.md index c0b0e171b0..d661678944 100644 --- a/docs/accessanalyzer/2601/dashboards-reports/my-reports.md +++ b/docs/accessanalyzer/2601/dashboards-reports/my-reports.md @@ -24,10 +24,10 @@ You can save any report that has the **Save Report** button in its toolbar. The 6. Review the **Current Filters** section to confirm the active filters are correct. 7. Click **Save Report**. -After saving, Access Analyzer redirects you to **My Reports** where the new report appears in the list. +After you save the report, Access Analyzer redirects you to **My Reports**, where the new report appears in the list. :::note -If no filters are applied when you click **Save Report**, the dialog indicates that no filters are active. You can still save the report, but it will open with the default unfiltered view. +If you don't apply filters before clicking **Save Report**, the dialog indicates that no filters are active. You can still save the report, but it will open with the default unfiltered view. ::: ## Open a saved report diff --git a/docs/accessanalyzer/2601/dashboards-reports/reports.md b/docs/accessanalyzer/2601/dashboards-reports/reports.md index aae3642661..fc48660abf 100644 --- a/docs/accessanalyzer/2601/dashboards-reports/reports.md +++ b/docs/accessanalyzer/2601/dashboards-reports/reports.md @@ -25,7 +25,7 @@ For full details on these reports, see [File Server Reports](/docs/accessanalyze | Report | Description | | --- | --- | -| **Broken Inheritance** | Lists shares and folders where permission inheritance has been broken, meaning the folder's ACL no longer follows its parent. Use this report to find locations where custom permission assignments may have introduced inconsistencies or unexpected access. | +| **Broken Inheritance** | Lists shares and folders where permission inheritance is broken, meaning the folder's ACL no longer follows its parent. Use this report to find locations where custom permission assignments may have introduced inconsistencies or unexpected access. | | **Domain User ACLs** | Shows share and folder permissions assigned directly to domain user accounts. Use this report to identify accounts with direct ACL entries that should be managed through groups instead. | | **High Risk ACLs** | Identifies folders where broad trustees such as Everyone, Authenticated Users, or Domain Users appear in the access control list. Use this report to locate and remediate over-permissioned folders that expose data to wide audiences. | | **Local Administrators** | Lists local administrator accounts and the hosts where they hold that privilege. Use this report to identify non-standard or unauthorized local administrator assignments across your file servers. | @@ -46,7 +46,7 @@ For full details on these reports, see [File Server Reports](/docs/accessanalyze | --- | --- | | **Empty Shares** | Lists shares that contain no files. Use this report to identify shares that can be reviewed for decommissioning or consolidation. | | **Largest Shares** | Ranks file shares by total size. Use this report to identify shares that consume the most storage and prioritize them for review or cleanup. | -| **Nested Shares** | Identifies shares that are nested inside other shares, creating multiple access paths to the same data with potentially different permissions. Use this report to find and resolve configurations that complicate permission management and access auditing. | +| **Nested Shares** | Identifies shares nested inside other shares, creating multiple access paths to the same data with potentially different permissions. Use this report to find and resolve configurations that complicate permission management and access auditing. | | **Stale Content** | Identifies files and shares that haven't been accessed within a configurable threshold. Use this report to locate data that may be a candidate for archiving, deletion, or access review. | ### Sensitive Data diff --git a/docs/accessanalyzer/2601/gettingstarted/active-directory/active-directory.md b/docs/accessanalyzer/2601/gettingstarted/active-directory/active-directory.md index 82de776a1d..ce3c07fa51 100644 --- a/docs/accessanalyzer/2601/gettingstarted/active-directory/active-directory.md +++ b/docs/accessanalyzer/2601/gettingstarted/active-directory/active-directory.md @@ -10,7 +10,7 @@ Access Analyzer scans Active Directory to inventory users, groups, and group mem ## Prerequisites -Before setting up an Active Directory source group, confirm that your environment meets the requirements below. The source group wizard connects to your domain controllers over LDAP or LDAPS, so the Access Analyzer server must be able to reach them on the network and a domain service account must be available with the appropriate read permissions. +Before setting up an Active Directory source group, confirm that your environment meets the following requirements. The source group wizard connects to your domain controllers over LDAP or LDAPS, so the Access Analyzer server must be able to reach them on the network and a domain service account must be available with the appropriate read permissions. ### Service account @@ -29,6 +29,6 @@ See [Username and Password](../../configurations/service-accounts/username-passw ### Before you begin -- The fully qualified domain name (FQDN) of each domain controller you plan to add. IP addresses aren't supported — DIGEST-MD5 authentication requires a resolvable hostname and will fail if an IP address is provided. +- The fully qualified domain name (FQDN) of each domain controller you plan to add. Access Analyzer doesn't support IP addresses — DIGEST-MD5 authentication requires a resolvable hostname and fails if you provide an IP address. - A Username and Password service account created in Access Analyzer with Read access to the domain. - Network connectivity from the Access Analyzer server to port 389 or 636 on each domain controller confirmed. diff --git a/docs/accessanalyzer/2601/gettingstarted/active-directory/reports.md b/docs/accessanalyzer/2601/gettingstarted/active-directory/reports.md index 0a091357f8..bf602f10d4 100644 --- a/docs/accessanalyzer/2601/gettingstarted/active-directory/reports.md +++ b/docs/accessanalyzer/2601/gettingstarted/active-directory/reports.md @@ -10,7 +10,7 @@ After the first Active Directory scan completes, the **AD Scan Summary** dashboa ## AD Scan Summary -The dashboard is organized into four sections: a summary row at the top, a **Users** section, a **Groups** section, and an **All Risks** section. +The dashboard has four sections: a summary row at the top, a **Users** section, a **Groups** section, and an **All Risks** section. ### Summary row diff --git a/docs/accessanalyzer/2601/gettingstarted/active-directory/schema-reference.md b/docs/accessanalyzer/2601/gettingstarted/active-directory/schema-reference.md index 7ae58d38c8..44a6fc5b0f 100644 --- a/docs/accessanalyzer/2601/gettingstarted/active-directory/schema-reference.md +++ b/docs/accessanalyzer/2601/gettingstarted/active-directory/schema-reference.md @@ -5,7 +5,7 @@ sidebar_position: 40 # Active Directory Schema Reference -Access Analyzer stores Active Directory scan data in the `access_analyzer` ClickHouse database. The tables below are created when you set up an Active Directory source group and run a scan. Use this reference when querying scan data directly or integrating Access Analyzer data with external tools. +Access Analyzer stores Active Directory scan data in the `access_analyzer` ClickHouse database. Access Analyzer creates these tables when you set up an Active Directory source group and run a scan. Use this reference when querying scan data directly or integrating Access Analyzer data with external tools. :::note All tables use the `ReplacingMergeTree` engine. Duplicate rows with the same primary key are deduplicated at merge time. Query the `_latest` views to return only the most recent version of each record. @@ -13,7 +13,7 @@ All tables use the `ReplacingMergeTree` engine. Duplicate rows with the same pri ## Metadata columns -All tables include the following columns populated by Access Analyzer during each scan: +All tables include the following columns, which Access Analyzer populates during each scan: | Column | Type | Description | |--------|------|-------------| @@ -108,9 +108,9 @@ Stores one row per user object discovered in an Active Directory scan. | Column | Type | Description | |--------|------|-------------| | `ms_ds_allowed_to_act_on_behalf_of` | `Array(String)` | List of security descriptors for accounts permitted to delegate to this account using resource-based constrained delegation. | -| `ms_ds_allowed_to_delegate_to` | `Array(String)` | List of SPNs this account is permitted to delegate to using constrained delegation. | +| `ms_ds_allowed_to_delegate_to` | `Array(String)` | List of service principal names (SPNs) this account is permitted to delegate to using constrained delegation. | | `ms_ds_supported_encryption_types` | `Nullable(Int32)` | Optional. Bitmask of Kerberos encryption types supported by this account. | -| `service_principal_name` | `Array(String)` | List of service principal names (SPNs) registered to this account. | +| `service_principal_name` | `Array(String)` | List of SPNs registered to this account. | | `legacy_exchange_dn` | `Nullable(String)` | Optional. Legacy Exchange distinguished name, used for mail routing compatibility. | | `ms_ds_user_account_control_computer` | `Nullable(Int32)` | Optional. Computer-specific `userAccountControl` flags stored on the user object in hybrid environments. | @@ -203,9 +203,9 @@ Stores custom Active Directory attribute values collected for user objects durin ### Active Directory Effective Group Membership -Stores the fully flattened, transitively resolved group membership graph. This table is populated by the `active_directory_effective_group_membership_mv` materialized view, which refreshes on a schedule after each scan. Each row represents one effective membership relationship at a given nesting depth. +Stores the fully flattened, transitively resolved group membership graph. The `active_directory_effective_group_membership_mv` materialized view populates this table and refreshes on a schedule after each scan. Each row represents one effective membership relationship at a given nesting depth. -**Engine:** `MergeTree` (not `ReplacingMergeTree`). The table is rebuilt on each refresh rather than deduplicated by version. +**Engine:** `MergeTree` (not `ReplacingMergeTree`). Access Analyzer rebuilds the table on each refresh rather than deduplicating it by version. **Primary key:** `(group_object_guid, member_object_guid)` diff --git a/docs/accessanalyzer/2601/gettingstarted/active-directory/set-up-source-group.md b/docs/accessanalyzer/2601/gettingstarted/active-directory/set-up-source-group.md index 83c7483472..4304eb9741 100644 --- a/docs/accessanalyzer/2601/gettingstarted/active-directory/set-up-source-group.md +++ b/docs/accessanalyzer/2601/gettingstarted/active-directory/set-up-source-group.md @@ -12,8 +12,8 @@ sidebar_position: 3 4. Select a service account from the **Service Account** dropdown, or click **+** to create one inline. Service accounts store the credentials Access Analyzer uses to connect to your domain controllers. See [Service Accounts](../../configurations/service-accounts/overview.md) for details. 5. Click **Add** under **Domain Controllers**, then select **Add Manually**. 6. Enter the following for each domain controller: - - **Server Name / IP** — The FQDN of the domain controller (for example, `dc01.corp.example.com`). IP addresses aren't supported. To add multiple domain controllers, separate entries with a comma or press **Enter** after each one. - - **Domain** — The DNS domain name (for example, `corp.example.com`). Applied to all entries above. + - **Server Name / IP** — The fully qualified domain name (FQDN) of the domain controller (for example, `dc01.corp.example.com`). Access Analyzer doesn't support IP addresses. To add multiple domain controllers, separate entries with a comma or press **Enter** after each one. + - **Domain** — The DNS domain name (for example, `corp.example.com`). Applies to all domain controllers you added in this step. - **Port** — The LDAP port. Default is `389`. Use `636` for LDAPS. 7. Click **Add domain controller**, then click **Done**. Repeat steps 5–7 for each additional domain. 8. If your domain controllers use self-signed certificates on port 636, select **Ignore SSL errors**. diff --git a/docs/accessanalyzer/2601/gettingstarted/entra-id/entra-id.md b/docs/accessanalyzer/2601/gettingstarted/entra-id/entra-id.md index 07dd999590..0ff6b763f0 100644 --- a/docs/accessanalyzer/2601/gettingstarted/entra-id/entra-id.md +++ b/docs/accessanalyzer/2601/gettingstarted/entra-id/entra-id.md @@ -6,15 +6,15 @@ sidebar_position: 1 # Entra ID Scanning Overview -Access Analyzer connects to Microsoft Entra ID to synchronize users, groups, role assignments, and Microsoft Information Protection (MIP) sensitivity labels from your tenant. MIP labels — defined in Microsoft Purview — are retrieved during the scan and made available in the Sensitive Data configuration, where you can map them to sensitive data types for use in file server and SharePoint Online scans. +Access Analyzer connects to Microsoft Entra ID to synchronize users, groups, role assignments, and Microsoft Information Protection (MIP) sensitivity labels from your tenant. Access Analyzer retrieves MIP labels — defined in Microsoft Purview — during the scan and makes them available in the Sensitive Data configuration, where you can map them to sensitive data types for use in file server and SharePoint Online scans. :::note -MIP sensitivity labels are collected during the Entra ID sync and become available for use in **File Server** and **SharePoint Online** Sensitive Data scans. Run the Entra ID scan at least once before enabling MIP label detection in those source groups. +Access Analyzer collects MIP sensitivity labels during the Entra ID sync, and they become available for use in **File Server** and **SharePoint Online** Sensitive Data scans. Run the Entra ID scan at least once before enabling MIP label detection in those source groups. ::: ## Prerequisites -Before setting up an Entra ID source group, confirm that your environment meets the requirements below. The source group wizard connects to Microsoft Entra ID over HTTPS using a registered application's client credentials, so the Access Analyzer server must be able to reach the Microsoft identity platform and an app registration must be configured in your tenant with the required API permissions. +Before setting up an Entra ID source group, confirm that your environment meets the following requirements. The source group wizard connects to Microsoft Entra ID over HTTPS using a registered application's client credentials, so the Access Analyzer server must be able to reach the Microsoft identity platform, and you must configure an app registration in your tenant with the required API permissions. ### Service account diff --git a/docs/accessanalyzer/2601/gettingstarted/entra-id/reports.md b/docs/accessanalyzer/2601/gettingstarted/entra-id/reports.md index 26cfa83f41..b829ef2d77 100644 --- a/docs/accessanalyzer/2601/gettingstarted/entra-id/reports.md +++ b/docs/accessanalyzer/2601/gettingstarted/entra-id/reports.md @@ -19,7 +19,7 @@ The dashboard is organized into three sections: a summary row at the top, an **I | **Users** | Total number of user objects synced from the tenant. | | **Groups** | Total number of group objects synced from the tenant. | | **Roles** | Total number of Azure AD role definitions retrieved. | -| **MIP Labels** | Total number of Microsoft Information Protection sensitivity labels retrieved from the tenant. | +| **MIP Labels** | Total number of Microsoft Information Protection (MIP) sensitivity labels retrieved from the tenant. | ### Identities @@ -34,9 +34,9 @@ The dashboard is organized into three sections: a summary row at the top, an **I | Card | Description | |------|-------------| -| **Active Labels** | Number of sensitivity labels currently active in the tenant. | +| **Active Labels** | Number of sensitivity labels active in the tenant. | | **Label List** | Table listing all retrieved labels, including label name, classification level, and whether the label is active. | :::note -MIP labels retrieved here are made available in **Configuration** > **Sensitive Data**, where you can map them to sensitive data types for use in File Server and SharePoint Online scans. +You can find the MIP labels retrieved here under **Configuration** > **Sensitive Data**, where you can map them to sensitive data types for use in File Server and SharePoint Online scans. ::: diff --git a/docs/accessanalyzer/2601/gettingstarted/entra-id/scanning-options.md b/docs/accessanalyzer/2601/gettingstarted/entra-id/scanning-options.md index 7de69e0ccf..85098ecc6d 100644 --- a/docs/accessanalyzer/2601/gettingstarted/entra-id/scanning-options.md +++ b/docs/accessanalyzer/2601/gettingstarted/entra-id/scanning-options.md @@ -8,10 +8,10 @@ sidebar_position: 2 | Scan type | Description | | --- | --- | -| **Users, Groups, and Roles** | Synchronizes users, groups, and role assignments from the Entra ID tenant. The first scan runs in full; subsequent scans collect only changes since the last run. MIP sensitivity labels are retrieved automatically as part of every scan. | +| **Users, Groups, and Roles** | Synchronizes users, groups, and role assignments from the Entra ID tenant. The first scan runs in full; subsequent scans collect only changes since the last run. Access Analyzer automatically retrieves Microsoft Information Protection (MIP) sensitivity labels as part of every scan. | ## MIP label retrieval -When an Entra ID source group runs, Access Analyzer automatically retrieves Microsoft Information Protection (MIP) sensitivity labels defined in the tenant. These labels are made available in the **Configuration** > **Sensitive Data** page, where you can map them to sensitive data types for use in file server and SharePoint Online scans. +When an Entra ID source group runs, Access Analyzer automatically retrieves Microsoft Information Protection (MIP) sensitivity labels defined in the tenant. You can find these labels on the **Configuration** > **Sensitive Data** page, where you can map them to sensitive data types for use in file server and SharePoint Online scans. There are no per-source-group configuration options for MIP label retrieval — it runs automatically as part of every scan. To configure how labels are applied to files, see [Sensitive Data Configuration](../../configurations/sensitive-data.md). diff --git a/docs/accessanalyzer/2601/gettingstarted/entra-id/schema-reference.md b/docs/accessanalyzer/2601/gettingstarted/entra-id/schema-reference.md index 42a6788f1c..e558b9fa2a 100644 --- a/docs/accessanalyzer/2601/gettingstarted/entra-id/schema-reference.md +++ b/docs/accessanalyzer/2601/gettingstarted/entra-id/schema-reference.md @@ -5,12 +5,12 @@ sidebar_position: 40 # Entra ID schema reference -Access Analyzer stores Entra ID scan data in the `access_analyzer` ClickHouse database. The tables below are populated when you set up an Entra ID source group and run a scan. Use this reference when querying scan data directly or integrating Access Analyzer data with external tools. +Access Analyzer stores Entra ID scan data in the `access_analyzer` ClickHouse database. Access Analyzer populates the following tables when you set up an Entra ID source group and run a scan. Use this reference when querying scan data directly or integrating Access Analyzer data with external tools. -Entra ID data is stored in shared tables that serve multiple connector types. Each row is scoped to your tenant using the `tenancyReference` column, which corresponds to your Entra ID tenant. +Access Analyzer stores Entra ID data in shared tables that serve multiple connector types. The `tenancyReference` column scopes each row to your tenant and corresponds to your Entra ID tenant. :::note -All tables use the `ReplacingMergeTree` engine. Duplicate rows with the same primary key are deduplicated at merge time. Use the `FINAL` keyword or query the available `_latest` views to return only the most recent version of each record. +All tables use the `ReplacingMergeTree` engine, which deduplicates rows with the same primary key at merge time. Use the `FINAL` keyword or query the available `_latest` views to return only the most recent version of each record. ::: ## Metadata columns @@ -110,7 +110,7 @@ Stores Microsoft Information Protection (MIP) sensitivity labels retrieved from | `name` | `String` | Internal name of the label. | | `displayName` | `String` | Display name shown to users in Microsoft 365 applications. | | `description` | `Nullable(String)` | Optional. Description of the label's purpose. | -| `isActive` | `Bool` | Whether the label is currently active in the tenant. | +| `isActive` | `Bool` | Whether the label is active in the tenant. | | `isDeleted` | `Bool` | Whether the label has been deleted. | | `classificationLevel` | `Nullable(String)` | Optional. Classification level assigned to the label. | | `priority` | `Int32` | Display order priority. Lower values appear first. | @@ -118,5 +118,5 @@ Stores Microsoft Information Protection (MIP) sensitivity labels retrieved from | `labelId` | `Nullable(String)` | Microsoft GUID for the label as defined in Microsoft Purview. | :::note -Labels stored here are the source data for MIP label mapping in **Configuration** > **Sensitive Data**. After mapping labels to sensitive data types, they are available for detection during File Server and SharePoint Online scans. +Labels stored here are the source data for MIP label mapping in **Configuration** > **Sensitive Data**. After you map labels to sensitive data types, they are available for detection during File Server and SharePoint Online scans. ::: diff --git a/docs/accessanalyzer/2601/gettingstarted/entra-id/set-up-source-group.md b/docs/accessanalyzer/2601/gettingstarted/entra-id/set-up-source-group.md index 108570ef48..62e5af73db 100644 --- a/docs/accessanalyzer/2601/gettingstarted/entra-id/set-up-source-group.md +++ b/docs/accessanalyzer/2601/gettingstarted/entra-id/set-up-source-group.md @@ -30,7 +30,7 @@ sidebar_position: 3 ## What happens next -Access Analyzer creates the source group and begins syncing users, groups, and roles from your Entra ID tenant. If you selected **Now**, the scan starts immediately. MIP sensitivity labels are retrieved automatically as part of the scan. +Access Analyzer creates the source group and begins syncing users, groups, and roles from your Entra ID tenant. If you selected **Now**, the scan starts immediately. Access Analyzer retrieves Microsoft Information Protection (MIP) sensitivity labels automatically as part of the scan. To check scan progress, navigate to **Configuration** > **Scan Executions**. diff --git a/docs/accessanalyzer/2601/gettingstarted/file-servers/file-servers.md b/docs/accessanalyzer/2601/gettingstarted/file-servers/file-servers.md index a0640d0062..1eaab1b140 100644 --- a/docs/accessanalyzer/2601/gettingstarted/file-servers/file-servers.md +++ b/docs/accessanalyzer/2601/gettingstarted/file-servers/file-servers.md @@ -6,7 +6,7 @@ sidebar_position: 1 # File Server Scanning Overview -Access Analyzer scans file servers over SMB to map share permissions, folder-level ACLs, and file ownership across your environment. It can also scan file contents to locate sensitive data and, if activity monitoring is configured, track file access events over time. Reports surface open access, broken inheritance, direct user permissions, and sensitive data exposure — giving security and compliance teams the visibility they need to reduce unnecessary access and meet data protection requirements. +Access Analyzer scans file servers over SMB to map share permissions, folder-level ACLs, and file ownership across your environment. It can also scan file contents to locate sensitive data and, if you configure activity monitoring, track file access events over time. Reports surface open access, broken inheritance, direct user permissions, and sensitive data exposure — giving security and compliance teams the visibility they need to reduce unnecessary access and meet data protection requirements. ## Supported platforms @@ -21,7 +21,7 @@ Access Analyzer scans any SMB-compatible file server. For platform-specific requ ## Prerequisites -Before setting up a file server source group, confirm that your environment meets the requirements below. The source group wizard connects to your file servers over SMB, so the Access Analyzer server must be able to reach them on the network and a service account must be available with read access to the shares you want to scan. +Before setting up a file server source group, confirm that your environment meets the following requirements. The source group wizard connects to your file servers over SMB, so the Access Analyzer server must be able to reach them on the network and a service account must be available with read access to the shares you want to scan. ### Service account diff --git a/docs/accessanalyzer/2601/gettingstarted/file-servers/reports.md b/docs/accessanalyzer/2601/gettingstarted/file-servers/reports.md index 1fe8e943ad..6cc8fd73ac 100644 --- a/docs/accessanalyzer/2601/gettingstarted/file-servers/reports.md +++ b/docs/accessanalyzer/2601/gettingstarted/file-servers/reports.md @@ -9,14 +9,14 @@ sidebar_position: 50 File Servers source groups include a set of pre-built reports that answer common security questions about permissions, sensitive data exposure, access patterns, and data content across your CIFS/SMB file shares. Reports are available under the Reports section after the first scan completes and update each time a scan runs. :::note -Activity reports (Activity Investigation and Sensitive Data Activity) require Netwrix Activity Monitor (NAM) to be configured and streaming events to Access Analyzer. See [Activity Monitor Integration](../../configurations/activity-monitor-integration.md) for setup instructions. +Activity reports (Activity Investigation and Sensitive Data Activity) require you to configure Netwrix Activity Monitor (NAM) so it streams events to Access Analyzer. See [Activity Monitor Integration](../../configurations/activity-monitor-integration.md) for setup instructions. ::: ## Available reports | Location | Report | Description | |----------|--------|-------------| -| Access / Broken Inheritance | Broken Inheritance | Lists shares and folders where permission inheritance has been broken, meaning the folder's ACL no longer follows its parent. Use this report to find locations where custom permission assignments may have introduced inconsistencies or unexpected access. | +| Access / Broken Inheritance | Broken Inheritance | Lists shares and folders with broken permission inheritance, meaning the folder's ACL no longer follows its parent. Use this report to find locations where custom permission assignments may have introduced inconsistencies or unexpected access. | | Access / Domain User ACLs | Domain User ACLs | Shows share and folder permissions assigned directly to domain user accounts. Use this report to identify accounts with direct ACL entries that should be managed through groups instead. | | Access / High Risk ACLs | High Risk ACLs | Identifies folders where broad trustees such as Everyone, Authenticated Users, or Domain Users appear in the access control list. Use this report to locate and remediate over-permissioned folders that expose data to wide audiences. | | Access / Local Administrators | Local Administrators | Lists local administrator accounts and the hosts where they hold that privilege. Use this report to identify non-standard or unauthorized local administrator assignments across your file servers. | @@ -27,9 +27,9 @@ Activity reports (Activity Investigation and Sensitive Data Activity) require Ne | Activity / Activity Investigation | Activity Investigation | Displays file system events filtered by date range, user, path, and event type. Use this report to trace the actions of a specific user or investigate changes to a specific file or folder. | | Content / Empty Shares | Empty Shares | Lists shares that contain no files. Use this report to identify shares that can be reviewed for decommissioning or consolidation. | | Content / Largest Shares | Largest Shares | Ranks file shares by total size. Use this report to identify shares that consume the most storage and prioritize them for review or cleanup. | -| Content / Nested Shares | Nested Shares | Identifies shares that are nested inside other shares, creating multiple access paths to the same data with potentially different permissions. Use this report to find and resolve configurations that complicate permission management and access auditing. | +| Content / Nested Shares | Nested Shares | Identifies shares that nest inside other shares, creating multiple access paths to the same data with potentially different permissions. Use this report to find and resolve configurations that complicate permission management and access auditing. | | Content / Stale Content | Stale Content | Identifies files and shares that haven't been accessed within a configurable threshold. Use this report to locate data that may be a candidate for archiving, deletion, or access review. | -| Sensitive Data / Sensitive Data Activity | Sensitive Data Activity | Shows file system events involving files that contain sensitive data, filtered by date range, event type, user, and classification taxonomy. Use this report to identify who is reading, modifying, or deleting sensitive files and to detect potential data exfiltration or misuse. | +| Sensitive Data / Sensitive Data Activity | Sensitive Data Activity | Shows file system events involving files that contain sensitive data. You can filter results by date range, event type, user, and classification taxonomy. Use this report to identify who is reading, modifying, or deleting sensitive files and to detect potential data exfiltration or misuse. | | Sensitive Data / Sensitive Data Overview | Sensitive Data Overview | Provides a high-level summary of sensitive data scan findings across CIFS/SMB file shares, including the number of files with matches, classification terms found, and distribution by host and share. Use this report as a starting point for understanding where sensitive data lives in your file server environment. | | Sensitive Data / Share Audit | Share Audit | Shows share-level details in the context of sensitive data findings, including which shares contain files with sensitive data matches. Use this report to understand sensitive data distribution across shares and prioritize remediation. | | Sensitive Data / Stale Data | Stale Data | Identifies files containing sensitive data that haven't been accessed recently. Use this report to find aging sensitive content that may no longer be actively used but still carries exposure risk. | diff --git a/docs/accessanalyzer/2601/gettingstarted/file-servers/scanning-options.md b/docs/accessanalyzer/2601/gettingstarted/file-servers/scanning-options.md index bd3c282d20..6fb261c24a 100644 --- a/docs/accessanalyzer/2601/gettingstarted/file-servers/scanning-options.md +++ b/docs/accessanalyzer/2601/gettingstarted/file-servers/scanning-options.md @@ -16,7 +16,7 @@ sidebar_position: 2 **Access** - **Include Shares** — Select **All shares** to scan every share on the server, or **Custom selection** to specify which shares to include. -- **Exclude Shares** — Enter share paths to skip. Wildcards are supported (for example, `\\fileserver\*\temp*`). +- **Exclude Shares** — Enter share paths to skip. This field supports wildcards (for example, `\\fileserver\*\temp*`). - **Hidden shares** — Select **Automatically enumerate hidden shares** to include hidden shares. Use **Exclude Hidden Shares** to skip specific ones (for example, `ADMIN$, C$, IPC$`). - **File-level permissions** — Select **Include file-level permission data** to collect permissions at the individual file level in addition to folder level. This increases scan time. - **Workers** — Sets the number of concurrent enumeration threads. Default is `3`; valid range is `1–20`. Increase to improve scan speed; decrease to reduce load on the file server. diff --git a/docs/accessanalyzer/2601/gettingstarted/file-servers/schema-reference.md b/docs/accessanalyzer/2601/gettingstarted/file-servers/schema-reference.md index 0c380f6b62..7f0b247ea4 100644 --- a/docs/accessanalyzer/2601/gettingstarted/file-servers/schema-reference.md +++ b/docs/accessanalyzer/2601/gettingstarted/file-servers/schema-reference.md @@ -5,15 +5,15 @@ sidebar_position: 40 # File Servers Schema Reference -Access Analyzer stores File Server scan data in the `access_analyzer` ClickHouse database. The tables below are created when you set up a File Server source group and run a scan. Use this reference when querying scan data directly or integrating Access Analyzer data with external tools. +Access Analyzer stores File Server scan data in the `access_analyzer` ClickHouse database. Setting up a File Server source group and running a scan creates the following tables. Use this reference when querying scan data directly or integrating Access Analyzer data with external tools. :::note -All tables use the `ReplacingMergeTree` engine. Duplicate rows with the same primary key are deduplicated at merge time. Query the `_latest` views to return only the most recent version of each record. +All tables use the `ReplacingMergeTree` engine. The engine deduplicates rows with the same primary key at merge time. Query the `_latest` views to return only the most recent version of each record. ::: ## Metadata columns -All tables include the following columns populated by Access Analyzer during each scan: +All tables include the following columns, which Access Analyzer populates during each scan: | Column | Type | Description | |--------|------|-------------| @@ -71,7 +71,7 @@ Stores the file system inventory collected during a scan — one row per file, d ### CIFS Permission -Stores NTFS ACEs (access control entries) for files and directories — one row per trustee per path. +Stores NTFS access control entries (ACEs) for files and directories — one row per trustee per path. | Column | Type | Description | |--------|------|-------------| @@ -151,10 +151,10 @@ Stores sensitive data classification findings — one row per taxonomy term matc ### CIFS Sensitive Data MIP Labels -Stores Microsoft Information Protection (MIP) sensitivity label decisions for files that contain sensitive data findings. Each row records the label action Access Analyzer determined for a file based on its classification results. MIP labels are sourced from an Entra ID source group configured in the same Access Analyzer instance — Access Analyzer uses that source group to resolve label definitions and apply or recommend label changes. +Stores Microsoft Information Protection (MIP) sensitivity label decisions for files that contain sensitive data findings. Each row records the label action Access Analyzer determined for a file based on its classification results. Access Analyzer sources MIP labels from an Entra ID source group configured in the same Access Analyzer instance and uses that source group to resolve label definitions and apply or recommend label changes. :::note -This table uses `ReplacingMergeTree(decision_timestamp)` rather than `scanned_at`. The most recent decision per file (identified by `source_id`, `host`, `share_name`, and `path`) is kept at merge time. +This table uses `ReplacingMergeTree(decision_timestamp)` rather than `scanned_at`. At merge time, the engine keeps the most recent decision per file (identified by `source_id`, `host`, `share_name`, and `path`). ::: | Column | Type | Description | @@ -163,7 +163,7 @@ This table uses `ReplacingMergeTree(decision_timestamp)` rather than `scanned_at | `host` | `String` | Hostname of the file server. | | `share_name` | `String` | Name of the share containing the file. | | `path` | `String` | Full path of the file this label decision applies to. | -| `mip_is_protected` | `Bool` | Whether the file is currently protected by MIP encryption. | +| `mip_is_protected` | `Bool` | Whether the file is protected by MIP encryption. | | `taxonomy_id` | `Nullable(UUID)` | Optional. Identifier of the taxonomy that triggered this label decision. | | `action` | `Enum8('upgrade', 'keep', 'downgrade', 'clear', 'none')` | The label action Access Analyzer determined: `upgrade` applies a higher-sensitivity label, `downgrade` applies a lower-sensitivity label, `keep` leaves the current label unchanged, `clear` removes the label, and `none` indicates no action was taken. | | `label_id` | `Nullable(UUID)` | Optional. UUID of the MIP sensitivity label selected by the action. | @@ -187,7 +187,7 @@ This table uses `ReplacingMergeTree(decision_timestamp)` rather than `scanned_at ## Views -Access Analyzer creates views that simplify common queries. Use views in preference to querying base tables directly. +Access Analyzer creates views that simplify common queries. Use views instead of querying base tables directly. | View | Base table | Description | |------|------------|-------------| diff --git a/docs/accessanalyzer/2601/gettingstarted/file-servers/set-up-source-group.md b/docs/accessanalyzer/2601/gettingstarted/file-servers/set-up-source-group.md index 2301ca864b..14a5a50fba 100644 --- a/docs/accessanalyzer/2601/gettingstarted/file-servers/set-up-source-group.md +++ b/docs/accessanalyzer/2601/gettingstarted/file-servers/set-up-source-group.md @@ -20,7 +20,7 @@ sidebar_position: 3 - Toggle **Access** to enable scanning of file permissions and access controls. - Under **Include Shares**, select **All shares** to scan every share on the server, or **Custom selection** to specify a list of shares to include. - - Optionally, add share paths to the **Exclude Shares** field to skip specific locations. Wildcards are supported (for example, `\\fileserver\*\temp*`). + - Optionally, add share paths to the **Exclude Shares** field to skip specific locations. The field supports wildcards (for example, `\\fileserver\*\temp*`). - Select **Automatically enumerate hidden shares** to include hidden shares in the scan. Use the **Exclude Hidden Shares** field to exclude specific hidden shares (for example, `ADMIN$, C$, IPC$`). - Select **Include file-level permission data** to collect permissions at the file level in addition to folder level. This increases scan time. - Set **Workers** to control the number of concurrent threads used during enumeration. The default is `3`. The valid range is `1–20`. @@ -29,7 +29,7 @@ sidebar_position: 3 **Sensitive Data scan:** - Toggle **Sensitive Data** to enable scanning of file contents for sensitive data patterns. - - Configure share selection using the same options as the Access scan above. + - Configure share selection using the same options as the Access scan. - Select **Inherit from Global Settings** to use the sensitive data types configured at the system level, or disable this option to configure types for this source group specifically. - If configuring types directly, enable each sensitive data type you want to detect and assign a classification label. - Select **Run OCR** to scan images, screenshots, and scanned documents for sensitive text using optical character recognition (OCR). This increases processing time. diff --git a/docs/accessanalyzer/2601/gettingstarted/sharepoint-online/scanning-options.md b/docs/accessanalyzer/2601/gettingstarted/sharepoint-online/scanning-options.md index 0c2521924d..e3c0f3eab3 100644 --- a/docs/accessanalyzer/2601/gettingstarted/sharepoint-online/scanning-options.md +++ b/docs/accessanalyzer/2601/gettingstarted/sharepoint-online/scanning-options.md @@ -19,10 +19,10 @@ sidebar_position: 2 | **Exclude site URLs** | Excludes specific site collections from the scan. Enter one URL per line. Exclusions take precedence over inclusions. | | **Scan OneDrive** | When enabled, includes OneDrive personal site collections in the scan. Enabled by default. | -The Access scan also reads Microsoft Information Protection (MIP) sensitivity labels from SharePoint item metadata and stores them alongside the permission data. Access Analyzer reads existing labels only — writing or modifying MIP labels on SharePoint Online items is not supported. +The Access scan also reads Microsoft Information Protection (MIP) sensitivity labels from SharePoint item metadata and stores them alongside the permission data. Access Analyzer reads existing labels only — it doesn't support writing or modifying MIP labels on SharePoint Online items. ## Sensitive Data scan The Sensitive Data scan reads file contents to detect and classify sensitive information. It runs after the Access scan completes and uses the file inventory collected during that scan. -Sensitive data classification policies, MIP label mappings, and OCR settings are configured globally and apply to all source groups. To configure them, navigate to **Configuration** > **Sensitive Data**. See [Sensitive Data Configuration](../../configurations/sensitive-data.md) for details. +You configure sensitive data classification policies, MIP label mappings, and optical character recognition (OCR) settings globally, and they apply to all source groups. To configure them, navigate to **Configuration** > **Sensitive Data**. See [Sensitive Data Configuration](../../configurations/sensitive-data.md) for details. diff --git a/docs/accessanalyzer/2601/gettingstarted/sharepoint-online/schema-reference.md b/docs/accessanalyzer/2601/gettingstarted/sharepoint-online/schema-reference.md index b37dcaed99..9da16a1e14 100644 --- a/docs/accessanalyzer/2601/gettingstarted/sharepoint-online/schema-reference.md +++ b/docs/accessanalyzer/2601/gettingstarted/sharepoint-online/schema-reference.md @@ -5,15 +5,15 @@ sidebar_position: 40 # SharePoint Online schema reference -Access Analyzer stores SharePoint Online scan data in the `access_analyzer` ClickHouse database. The tables below are created when you set up a SharePoint Online source group and run a scan. Use this reference when querying scan data directly or integrating Access Analyzer data with external tools. +Access Analyzer stores SharePoint Online scan data in the `access_analyzer` ClickHouse database. Setting up a SharePoint Online source group and running a scan creates the following tables. Use this reference when querying scan data directly or integrating Access Analyzer data with external tools. :::note -All tables use the `ReplacingMergeTree` engine. Duplicate rows with the same primary key are deduplicated at merge time. Query the `_latest` views to return only the most recent version of each record. +All tables use the `ReplacingMergeTree` engine. The engine deduplicates rows with the same primary key at merge time. Query the `_latest` views to return only the most recent version of each record. ::: ## Metadata columns -All tables include the following columns populated by Access Analyzer during each scan: +All tables include the following columns, which Access Analyzer populates during each scan: | Column | Type | Description | |--------|------|-------------| @@ -35,13 +35,13 @@ Stores one row per scanned SharePoint item — sites, lists, document libraries, | `site_id` | `String` | SharePoint identifier of the site collection. | | `item_id` | `String` | Unique identifier of the item within the site. | | `site_url` | `String` | Absolute URL of the site collection. | -| `drive_id` | `String` | Microsoft Graph drive identifier for the document library that contains this item. Empty for sites and lists that do not have a drive. | -| `drive_item_id` | `String` | Microsoft Graph drive item identifier. Empty for items that are not drive items. | +| `drive_id` | `String` | Microsoft Graph drive identifier for the document library that contains this item. Empty for sites and lists that don't have a drive. | +| `drive_item_id` | `String` | Microsoft Graph drive item identifier. Empty for items that aren't drive items. | | `item_type` | `Enum8` | Type of SharePoint item. Values: `SITE`, `LIST`, `LIBRARY`, `LIST_ITEM`. | | `name` | `String` | Display name of the item. | | `file_extension` | `String` | File extension, including the leading period (for example, `.docx`). Empty for non-file items. | | `relative_url` | `String` | Server-relative URL path of the item. | -| `file_size` | `Nullable(Int64)` | Optional. File size in bytes. Null for items that are not files. | +| `file_size` | `Nullable(Int64)` | Optional. File size in bytes. Null for items that aren't files. | | `created_time` | `DateTime` | Timestamp when the item was created in SharePoint. | | `created_by_id` | `String` | SharePoint user identifier of the user who created the item. | | `created_by_email` | `String` | Email address of the user who created the item. | @@ -79,12 +79,12 @@ Stores one row per permission assignment. Each row represents a single principal | `principal_id` | `String` | Identifier of the user or group that holds the permission. | | `principal_type` | `Enum8` | Type of the principal. Values: `USER`, `GROUP`, `SITE_USER`, `SITE_GROUP`. | | `principal_name` | `String` | Display name of the principal. | -| `principal_email` | `String` | Email address of the principal. Empty for groups that do not have an email address. | +| `principal_email` | `String` | Email address of the principal. Empty for groups that don't have an email address. | | `permission_type` | `Enum8` | How the permission was granted. Values: `DIRECT` (assigned directly to the item), `SHARED` (granted through a sharing link). | | `permission_levels` | `Array(Enum8)` | Named permission levels assigned to the principal. Values: `OWNER`, `READ`, `WRITE`. | | `effective_base_permissions` | `Array(Enum8)` | Full set of granular SharePoint base permissions the principal holds. Values include `VIEW_LIST_ITEMS`, `ADD_LIST_ITEMS`, `EDIT_LIST_ITEMS`, `DELETE_LIST_ITEMS`, `MANAGE_LISTS`, `MANAGE_PERMISSIONS`, `MANAGE_WEB`, and others as defined by the SharePoint permission model. | | `normalized_permissions` | `FixedString(5)` | Compact bitmask representation of the permission levels. Used internally for permission comparison. | -| `parent_site_id` | `String` | Identifier of the site collection from which this permission is inherited. Empty for permissions that are not inherited. | +| `parent_site_id` | `String` | Identifier of the site collection from which this permission is inherited. Empty for permissions that aren't inherited. | | `parent_item_id` | `String` | `item_id` of the item from which this permission is inherited. Empty for permissions assigned directly to this item. | | `is_site_admin` | `Bool` | `true` if the principal is a site collection administrator. | | `is_external_user` | `Bool` | `true` if the principal is a guest or external user. | @@ -116,7 +116,7 @@ Stores one row per sharing link. A sharing link may grant access to one or more | `link_type` | `Enum8` | Access level granted by the link. Values: `VIEW`, `EDIT`, `EMBED`, `REVIEW`. | | `link_url` | `String` | Full URL of the sharing link. | | `link_scope` | `Enum8` | Audience the link is accessible to. Values: `ANONYMOUS` (anyone with the link), `ORGANIZATION` (anyone in the organization), `USERS` (specific users only). | -| `expires_on` | `DateTime` | Expiration timestamp of the link. A zero value indicates the link does not expire. | +| `expires_on` | `DateTime` | Expiration timestamp of the link. A zero value indicates the link doesn't expire. | | `is_password_protected` | `Bool` | `true` if the link requires a password to access. | | `prevent_download` | `Bool` | `true` if the link prevents recipients from downloading the file. | @@ -156,7 +156,7 @@ Stores classification results from the sensitive data scan option. Each row repr ## Views -Access Analyzer creates views that simplify common queries. Use views in preference to querying base tables directly. +Access Analyzer creates views that simplify common queries. Use views instead of querying base tables directly. | View | Base table | Description | |------|------------|-------------| diff --git a/docs/accessanalyzer/2601/gettingstarted/sharepoint-online/set-up-source-group.md b/docs/accessanalyzer/2601/gettingstarted/sharepoint-online/set-up-source-group.md index e0923fa8c9..7292948ba9 100644 --- a/docs/accessanalyzer/2601/gettingstarted/sharepoint-online/set-up-source-group.md +++ b/docs/accessanalyzer/2601/gettingstarted/sharepoint-online/set-up-source-group.md @@ -19,7 +19,7 @@ sidebar_position: 3 6. Under **Certificate**, click **Generate and Download Certificate** to generate a certificate and download it to your machine. Upload this certificate to your registered Entra ID application before proceeding. See [Certificate Configuration](../../connectors/sharepoint-online/tenant-certificate-config.md) for upload steps. :::note - If you click **Regenerate Certificate** in the future, the new certificate must be uploaded to your Entra ID App Registration to replace the old one. Removing the old certificate from the App Registration is a manual step in the Azure portal — Access Analyzer cannot remove it on your behalf. + If you click **Regenerate Certificate** in the future, you must upload the new certificate to your Entra ID App Registration to replace the old one. Removing the old certificate from the App Registration is a manual step in the Azure portal — Access Analyzer can't remove it on your behalf. ::: 7. Click **Test Connection** to verify that Access Analyzer can authenticate to your SharePoint Online tenant. Resolve any failures before proceeding. @@ -53,5 +53,5 @@ To check scan progress, navigate to **Configuration** > **Scan Executions**. To modify an existing SharePoint Online source group, navigate to **Configuration** > **Source Groups**, select the source group, and click **Edit**. The wizard reopens with your current configuration pre-populated. You can update the source group name, service account, tenant ID, scan configuration, and scan schedule. :::note -Updating the service account replaces the certificate used to authenticate with SharePoint Online. Ensure the new service account's certificate is uploaded to your registered Entra ID application before saving. +Updating the service account replaces the certificate used to authenticate with SharePoint Online. Ensure you upload the new service account's certificate to your registered Entra ID application before saving. ::: diff --git a/docs/accessanalyzer/2601/gettingstarted/sharepoint-online/sharepoint-online.md b/docs/accessanalyzer/2601/gettingstarted/sharepoint-online/sharepoint-online.md index 517738c004..39a5e5b55f 100644 --- a/docs/accessanalyzer/2601/gettingstarted/sharepoint-online/sharepoint-online.md +++ b/docs/accessanalyzer/2601/gettingstarted/sharepoint-online/sharepoint-online.md @@ -10,11 +10,11 @@ Access Analyzer scans SharePoint Online sites to map permissions, enumerate shar ## Prerequisites -Before setting up a SharePoint Online source group, confirm that your environment meets the requirements below. The source group wizard connects to SharePoint Online over HTTPS using certificate-based authentication, so the Access Analyzer server must be able to reach the Microsoft identity platform and an app registration must be configured in your tenant. The certificate is generated by the wizard — you'll need the application's Client ID before you begin. +Before setting up a SharePoint Online source group, confirm that your environment meets the following requirements. The source group wizard connects to SharePoint Online over HTTPS using certificate-based authentication, so the Access Analyzer server must be able to reach the Microsoft identity platform, and you must configure an app registration in your tenant. The wizard generates the certificate — you'll need the application's Client ID before you begin. ### Service account -Access Analyzer uses a Client ID and Certificate service account to authenticate with SharePoint Online. Only the Client ID is entered when creating the service account — the certificate is generated automatically during source group setup when you click **Generate and Download Certificate**. You then upload the certificate to your registered Entra ID application before the connection can be tested. +Access Analyzer uses a Client ID and Certificate service account to authenticate with SharePoint Online. You enter only the Client ID when creating the service account — Access Analyzer generates the certificate automatically during source group setup when you click **Generate and Download Certificate**. You then upload the certificate to your registered Entra ID application before you can test the connection. See [Client ID/Certificate service account](../../configurations/service-accounts/client-id-certificate.md) to create the service account and [SharePoint Online Connector Requirements](../../connectors/sharepoint-online/overview.md) for instructions on registering the application. @@ -34,7 +34,7 @@ See [Client ID/Certificate service account](../../configurations/service-account - Network connectivity from the Access Analyzer server to port 443 confirmed. :::note -Access Analyzer reads MIP sensitivity labels on SharePoint Online files during Sensitive Data scans. Labels are collected and surfaced in scan results — no changes are made to labels on any scanned file. +Access Analyzer reads Microsoft Information Protection (MIP) sensitivity labels on SharePoint Online files during Sensitive Data scans. It collects the labels and surfaces them in scan results, and it makes no changes to labels on any scanned file. ::: :::note diff --git a/docs/accessanalyzer/2601/install/identity-provider.md b/docs/accessanalyzer/2601/install/identity-provider.md index f3719334fb..80c62fdb3b 100644 --- a/docs/accessanalyzer/2601/install/identity-provider.md +++ b/docs/accessanalyzer/2601/install/identity-provider.md @@ -24,14 +24,14 @@ When you configure `--idp-type`, the installer automatically: 1. Deploys Keycloak (v26.5.3) as part of the cluster 2. Waits for Keycloak to become healthy 3. Creates the IdP federation using the flags you provided -4. Enables OIDC authentication in the Access Analyzer application +4. Enables OpenID Connect (OIDC) authentication in the Access Analyzer application ## Before you begin Confirm the following before running the installer with IdP flags: -- The Access Analyzer cluster system requirements are met — see [Hardware and System Requirements](system/requirements.md) -- TLS certificates are prepared and placed on the VM — see [TLS Certificate Requirements](system/certificates.md) +- Your infrastructure meets the Access Analyzer cluster system requirements — see [Hardware and System Requirements](system/requirements.md) +- You have prepared and placed TLS certificates on the VM — see [TLS Certificate Requirements](system/certificates.md) - You have collected the required credentials from the customer's IdP or directory administrator (see [Identity Provider — Part 1](../configurations/identity-provider.md#part-1-configure-your-identity-provider)) - For LDAP/AD: the Access Analyzer server has network access to the LDAP server on port 636 (LDAPS) or 389 (LDAP) - For a private CA certificate: you have the PEM file available on the server and will pass `--ca-bundle ` to the installer @@ -39,7 +39,7 @@ Confirm the following before running the installer with IdP flags: :::warning `--hostname` is required and must: -- Be a real DNS hostname (not an IP address — IPs will not work because the browser TLS handshake requires the hostname in the certificate's SAN). +- Be a real DNS hostname (not an IP address — IPs will not work because the browser TLS handshake requires the hostname in the certificate's Subject Alternative Name (SAN)). - Be lowercase, and match lowercase in the certificate SAN list. Keycloak derives its OIDC issuer URL from this value; a case mismatch between SAN and browser-normalized hostname produces HTTP 401 at sign-in. - Resolve the same from client browsers and in-cluster pods. The installer configures the in-cluster rewrite automatically; the customer is responsible for the public DNS record or `/etc/hosts` entry that client browsers use. - Avoid the `.local` and `.localhost` TLDs — both break in-cluster DNS resolution and silently break OIDC login flows. @@ -154,7 +154,7 @@ END HIDDEN --> ## Configure Active Directory :::tip -For a step-by-step end-to-end walkthrough using environment variables (recommended for most customers), see the [Quick Install](quickinstall.md). The section below is the flag-level reference. +For a step-by-step end-to-end walkthrough using environment variables (recommended for most customers), see the [Quick Install](quickinstall.md). This section is the flag-level reference. ::: **Required flags:** `--idp-type ad`, `--idp-alias`, `--ldap-url`, `--ldap-bind-dn`, `--ldap-users-dn` @@ -163,7 +163,7 @@ For a step-by-step end-to-end walkthrough using environment variables (recommend **Prompted secret:** LDAP bind credential — entered interactively, never written to disk or logs -If your domain controller's LDAPS certificate is signed by an internal CA not in the OS trust store (typical for on-prem AD), pass the root CA cert via `--ca-bundle`. Without it, Keycloak's LDAPS handshake to the DC will fail with a TLS trust error. The CA that signed the DC's LDAPS certificate may be different from the CA that signed your Access Analyzer server's TLS certificate — verify the DC's cert chain specifically. See [TLS Certificate Requirements](system/certificates.md) for details on assembling the CA bundle. +If an internal CA not in the OS trust store (typical for on-prem AD) signs your domain controller's LDAPS certificate, pass the root CA cert via `--ca-bundle`. Without it, Keycloak's LDAPS handshake to the DC will fail with a TLS trust error. The CA that signed the DC's LDAPS certificate may be different from the CA that signed your Access Analyzer server's TLS certificate — verify the DC's cert chain specifically. See [TLS Certificate Requirements](system/certificates.md) for details on assembling the CA bundle. ```bash export LICENSE_KEY='[YOUR_LICENSE_KEY]' @@ -492,7 +492,7 @@ grep -A 20 "Configuring IdP federation" /var/log/dspm-installer.log | Message | Likely cause | | --- | --- | -| `Failed to authenticate with Keycloak admin CLI` | Keycloak pod not ready; check pod status below | +| `Failed to authenticate with Keycloak admin CLI` | Keycloak pod not ready; see [Check Keycloak pod health](#check-keycloak-pod-health) | | `409 Conflict` from `kcadm.sh create` | An IdP with this alias already exists in Keycloak | | `PKIX path building failed` in Keycloak logs (LDAP sign-ins fail silently) | CA bundle is missing the LDAPS DC's CA — see [TLS Certificate Requirements](system/certificates.md#multi-domain-and-multi-ca-environments) | diff --git a/docs/accessanalyzer/2601/install/quickinstall.md b/docs/accessanalyzer/2601/install/quickinstall.md index de2e028b0e..40ff1979c1 100644 --- a/docs/accessanalyzer/2601/install/quickinstall.md +++ b/docs/accessanalyzer/2601/install/quickinstall.md @@ -78,7 +78,7 @@ The installer offers three ways to provision the server's TLS certificate. Choos | --- | --- | --- | --- | | **Generate self-signed** | Installer generates a certificate automatically — no CA involvement | Quick evaluations and proof-of-concept installs. Not for production — browsers will show a security warning | Nothing — installer handles it | | **Sign with AD Certificate Services** | Installer generates a certificate signing request (CSR) and submits it to your organization's Active Directory Certificate Services (AD CS), where your internal Enterprise CA signs it | Enterprise environments that already run AD CS and where the server can reach the CA | AD CS must be reachable from the server; an account with certificate enrollment rights | -| **Bring your own certificate** | You provide a pre-existing certificate, private key, and CA bundle | Environments with a centralized PKI team, or where AD CS isn't available | Three PEM files — see [file requirements](#bring-your-own-certificate-file-requirements) | +| **Bring your own certificate** | You provide a pre-existing certificate, private key, and CA bundle | Environments with a centralized Public Key Infrastructure (PKI) team, or where AD CS isn't available | Three PEM files — see [file requirements](#bring-your-own-certificate-file-requirements) | #### Bring your own certificate file requirements diff --git a/docs/accessanalyzer/2601/install/security.md b/docs/accessanalyzer/2601/install/security.md index 40fc8a02d1..089088c18e 100644 --- a/docs/accessanalyzer/2601/install/security.md +++ b/docs/accessanalyzer/2601/install/security.md @@ -10,10 +10,10 @@ Follow these recommendations to harden your Access Analyzer deployment. ## License Key Protection -Your Netwrix license key provides access to the OCI package registry. Treat it as a credential: +Your Netwrix license key provides access to the Open Container Initiative (OCI) package registry. Treat it as a credential: -- Do not commit license keys to version control -- Do not store license keys in plaintext configuration files +- Don't commit license keys to version control +- Don't store license keys in plaintext configuration files - Clear shell history after setting the `LICENSE_KEY` environment variable: ```bash @@ -29,7 +29,7 @@ Your Netwrix license key provides access to the OCI package registry. Treat it a ## TLS / SSL - Replace the default self-signed certificate with a certificate issued by a trusted CA for production use -- Ensure outbound TLS verification is enabled by mounting your organization's CA bundle — see [SSL / TLS Configuration](/docs/accessanalyzer/2601/install/system/certificates) +- Mount your organization's CA bundle to enable outbound TLS verification — see [SSL / TLS Configuration](/docs/accessanalyzer/2601/install/system/certificates) ## RBAC and Access Control @@ -60,6 +60,6 @@ Your Netwrix license key provides access to the OCI package registry. Treat it a ## Kubernetes Security -- Secrets at rest are encrypted by default (K3s `--secrets-encryption` flag) -- Kubeconfig file permissions are set to `644` — restrict further if the VM is shared +- K3s encrypts secrets at rest by default (`--secrets-encryption` flag) +- By default, kubeconfig file permissions are `644` — restrict further if the VM is shared - Regularly apply OS security patches to the host VM diff --git a/docs/accessanalyzer/2601/install/system/certificates.md b/docs/accessanalyzer/2601/install/system/certificates.md index 074062a270..9b92f976ca 100644 --- a/docs/accessanalyzer/2601/install/system/certificates.md +++ b/docs/accessanalyzer/2601/install/system/certificates.md @@ -29,14 +29,14 @@ All three files must be in PEM format. When you choose **Bring your own certific ## 2. Application TLS Private Key (`.key`) - **Format**: PEM (`-----BEGIN PRIVATE KEY-----` or `-----BEGIN RSA PRIVATE KEY-----`). -- **Must be readable by the OS user running the installer.** If you extracted the key using `sudo` or another elevated context, the file may be owned by `root` with `0600` permissions — the installer will fail to read it. After extraction, set ownership to the user running the installer: +- **Must be readable by the OS user running the installer.** If you extracted the key using `sudo` or another elevated context, `root` may own the file with `0600` permissions — the installer will fail to read it. After extraction, set ownership to the user running the installer: ```bash sudo chown : /opt/dspm-tls/.key sudo chmod 644 /opt/dspm-tls/.key ``` -- **Never share or commit this file.** Once inside `/opt/dspm-tls/` with correct ownership, restrict access via directory permissions. +- **Never share or commit this file.** After the file is inside `/opt/dspm-tls/` with correct ownership, restrict access via directory permissions. ## 3. CA Bundle (`ca-bundle.crt`) diff --git a/docs/accessanalyzer/2601/install/system/kubernetes.md b/docs/accessanalyzer/2601/install/system/kubernetes.md index 1f86412f14..2fdf2bf161 100644 --- a/docs/accessanalyzer/2601/install/system/kubernetes.md +++ b/docs/accessanalyzer/2601/install/system/kubernetes.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Kubernetes and Operating System -Access Analyzer uses K3s, a lightweight Kubernetes distribution, which is automatically deployed by the installer. No manual Kubernetes setup is required. +Access Analyzer uses K3s, a lightweight Kubernetes distribution that the installer deploys automatically. You don't need to set up Kubernetes manually. ## Operating System @@ -17,7 +17,7 @@ Access Analyzer uses K3s, a lightweight Kubernetes distribution, which is automa | **Kernel version** | 5.15 or later | :::note -Other Linux distributions may work but are not officially tested or supported. Ubuntu 24.04 LTS is the recommended and validated platform. +Other Linux distributions may work, but Netwrix doesn't officially test or support them. Ubuntu 24.04 LTS is the recommended and validated platform. ::: ## K3s Kubernetes @@ -29,7 +29,7 @@ Other Linux distributions may work but are not officially tested or supported. U | **Secrets encryption** | Enabled (at rest) | | **Service name** | `k3s-dspm` | -K3s is installed and managed automatically by the Access Analyzer installer. The `kubectl` command is available immediately after installation for cluster management. +The Access Analyzer installer installs and manages K3s automatically. The `kubectl` command is available immediately after installation for cluster management. ## Kernel Features @@ -50,4 +50,4 @@ The following kernel features must be available. The installer validates these a | **Namespace** | `argocd` | | **UI port** | 8090 (via port-forward) | -ArgoCD is deployed automatically and manages the lifecycle of all Access Analyzer application components through GitOps. +The installer deploys ArgoCD automatically, and ArgoCD manages the lifecycle of all Access Analyzer application components through GitOps. diff --git a/docs/accessanalyzer/2601/install/system/network.md b/docs/accessanalyzer/2601/install/system/network.md index d8989d78a7..ba5e27cba4 100644 --- a/docs/accessanalyzer/2601/install/system/network.md +++ b/docs/accessanalyzer/2601/install/system/network.md @@ -43,7 +43,7 @@ Access Analyzer uses these ports within the VM for service-to-service communicat | 6379 | TCP | Redis | Cache and queue connections | :::note -All internal ports are bound to the local cluster network. Only port 443 (Traefik) is exposed externally for the web interface. +The local cluster network keeps all internal ports contained. Traefik exposes only port 443 externally, for the web interface. ::: ## Connector Network Requirements diff --git a/docs/accessanalyzer/2601/overview/keyconcepts.md b/docs/accessanalyzer/2601/overview/keyconcepts.md index 02aa160256..e4e943fbb4 100644 --- a/docs/accessanalyzer/2601/overview/keyconcepts.md +++ b/docs/accessanalyzer/2601/overview/keyconcepts.md @@ -10,7 +10,7 @@ This page defines the core terminology used throughout Access Analyzer. ## Source Groups -A **source group** is a named collection of related sources that share a common service account and configuration. Sources are the individual hosts or targets within a source group — for example, the specific file servers or domain controllers that Access Analyzer connects to and scans. Source groups are created through the **Connect Source** wizard, which handles source creation, scan configuration, and scheduling in a single workflow. +A **source group** is a named collection of related sources that share a common service account and configuration. Sources are the individual hosts or targets within a source group — for example, the specific file servers or domain controllers that Access Analyzer connects to and scans. The **Connect Source** wizard creates source groups, handling source creation, scan configuration, and scheduling in a single workflow. - **File Server** source groups can contain multiple servers (for example, all file servers in a department) - **Active Directory** source groups can contain multiple domain controllers @@ -28,7 +28,7 @@ A **service account** stores credentials used to authenticate with data sources - **Client ID + Certificate** — SharePoint Online state-in-time scans. Access Analyzer generates the certificate; you upload the public key to your Azure app registration. - **SSH Username / Key** — Edge scanners -Service accounts are managed in **Configuration** > **Service Accounts** and can be shared across multiple sources. +You manage service accounts in **Configuration** > **Service Accounts** and can share them across multiple sources. ## User Roles @@ -37,27 +37,27 @@ Access Analyzer has three roles: | Role | Responsibilities | | --- | --- | | **Administrator** | Full access: manages system configuration (sources, scans, connectors, service accounts, application settings) and user management (create accounts, assign roles, manage users). | -| **User Admin** | User and role management only — creates accounts, assigns roles, and pre-provisions federated users. Cannot change system configuration. | -| **Viewer** | Read-only access to data, reports, and dashboards. Cannot make changes. | +| **User Admin** | User and role management only — creates accounts, assigns roles, and pre-provisions federated users. Can't change system configuration. | +| **Viewer** | Read-only access to data, reports, and dashboards. Can't make changes. | For a full walkthrough of role assignment, see the [Quick Install — Roles](/docs/accessanalyzer/2601/install/quickinstall#roles) section. ## Connectors -A **connector** is the component that performs the actual work of communicating with a source. Each source type has a corresponding connector that handles: +A **connector** is the component that communicates with a source. Each source type has a corresponding connector that handles: - **Test connection** — Validates that credentials and network connectivity are correct - **Access scan / sync** — Enumerates files, folders, permissions, or identities -Connectors are executed as Kubernetes Jobs and managed by the Connector API. +The Connector API executes and manages connectors as Kubernetes Jobs. ## Edge Scanners -An **edge scanner** is a lightweight, containerized agent that Access Analyzer deploys on demand to perform distributed scanning of remote environments. Edge scanners remove the need for a traditional proxy server — they run as short-lived Kubernetes Jobs, execute their scan, and terminate. There is no persistent agent process and no manual deployment required. +An **edge scanner** is a lightweight, containerized agent that Access Analyzer deploys on demand to perform distributed scanning of remote environments. Edge scanners remove the need for a traditional proxy server — they run as short-lived Kubernetes Jobs, execute their scan, and terminate. No persistent agent process exists, and you don't need to deploy them manually. -Edge scanners are used for **Active Directory** and **File Server** sources. Entra ID and SharePoint Online connect directly from the Access Analyzer service and do not use edge scanners. +Access Analyzer uses edge scanners for **Active Directory** and **File Server** sources. Entra ID and SharePoint Online connect directly from the Access Analyzer service and don't use edge scanners. -Edge scanners are registered in **Configuration** > **Source Groups** > **Scanners** and are associated with a service account using **SSH Username / Key** credentials. Scanner labels can be used to route specific scan executions to dedicated scanner pools — for example, to isolate production scanning traffic from non-production environments. +You register edge scanners in **Configuration** > **Source Groups** > **Scanners** and associate them with a service account using **SSH Username / Key** credentials. Use scanner labels to route specific scan executions to dedicated scanner pools — for example, to isolate production scanning traffic from non-production environments. For configuration details and best practices, see [Overview of Scanners](/docs/accessanalyzer/2601/configurations/source-groups/scanners/overview). @@ -68,9 +68,9 @@ A **scan** defines what to analyze and how. Access Analyzer supports several sca - **Access scans** — Enumerate files, folders, and permissions on data sources to identify who has access to what - **Sensitive data scans** — Classify file contents against detection patterns to find PII, credentials, PHI, and financial records - **Identity sync scans** — Synchronize users, groups, and roles from IAM sources (Active Directory Inventory, Entra ID Users/Groups/Roles) -- **Local Users and Groups scans** — Collect local account data from file servers (auto-created when an access scan is enabled) +- **Local Users and Groups scans** — Collect local account data from file servers (created automatically when you enable an access scan) -Scans can be run on demand or scheduled with a cron expression. +You can run scans on demand or schedule them with a cron expression. ## Scan Executions @@ -96,16 +96,16 @@ A **pattern** is a detection rule used during sensitive data scans. Patterns mat - **PHI** — Protected health information - **Financial Records** — Credit card numbers, bank accounts, financial data -Patterns are organized into **taxonomies** — hierarchical groups of classification rules mapped to compliance frameworks (GDPR, CCPA, HIPAA, PCI DSS, GLBA, CMMC). +Access Analyzer organizes patterns into **taxonomies** — hierarchical groups of classification rules mapped to compliance frameworks (GDPR, CCPA, HIPAA, PCI DSS, GLBA, CMMC). ## MIP Labels -**MIP labels** are Microsoft Information Protection sensitivity labels that Access Analyzer reads from scanned files and surfaces alongside sensitive data findings. They are distinct from Sensitive Data Patterns — patterns detect content through classification rules, while MIP labels are labels already applied to files by Microsoft 365 users or automated policies. +**Microsoft Information Protection (MIP) labels** are sensitivity labels that Access Analyzer reads from scanned files and surfaces alongside sensitive data findings. They are distinct from Sensitive Data Patterns — patterns detect content through classification rules, while Microsoft 365 users or automated policies already apply MIP labels directly to files. - **File Server sources** — Access Analyzer reads MIP labels from scanned files and can apply labels to files based on scan findings. -- **SharePoint Online sources** — Access Analyzer reads MIP labels from native SharePoint metadata. Label application is not supported for SharePoint Online. +- **SharePoint Online sources** — Access Analyzer reads MIP labels from native SharePoint metadata. Label application isn't supported for SharePoint Online. -Labels are synced from your Entra ID tenant. To make labels available, an Entra ID source group must exist and its **Users, Groups and Roles** scan must have run at least once. Once synced, labels are mapped to sensitive data types in **Configuration** > **Sensitive Data**. +Access Analyzer syncs labels from your Entra ID tenant. To make labels available, an Entra ID source group must exist and its **Users, Groups and Roles** scan must have run at least once. Once synced, you map labels to sensitive data types in **Configuration** > **Sensitive Data**. ## Dashboards and Reports @@ -113,7 +113,7 @@ Access Analyzer includes pre-built dashboards and reports that surface findings ### Dashboards -Two summary dashboards are embedded in the Access Analyzer interface: +Access Analyzer embeds two summary dashboards in its interface: | Dashboard | What it shows | | --- | --- | @@ -122,7 +122,7 @@ Two summary dashboards are embedded in the Access Analyzer interface: ### Pre-built Reports -Reports are organized by source type and category: +Access Analyzer organizes reports by source type and category: | Source | Categories | | --- | --- | diff --git a/docs/accessanalyzer/2601/overview/overview.md b/docs/accessanalyzer/2601/overview/overview.md index d7d9f194a6..536f4c6d05 100644 --- a/docs/accessanalyzer/2601/overview/overview.md +++ b/docs/accessanalyzer/2601/overview/overview.md @@ -7,7 +7,7 @@ sidebar_position: 10 # Overview :::note Using an older version? -This documentation covers **Access Analyzer 2601**, the latest release — a containerized, Linux-based deployment. If you are running a previous Windows-based installation, select your version below: +This documentation covers **Access Analyzer 2601**, the latest release — a containerized, Linux-based deployment. If you are running a previous Windows-based installation, select your version from the following list: - [Access Analyzer 12.0 documentation](https://docs.netwrix.com/docs/accessanalyzer/12_0) - [Access Analyzer 11.6 documentation](https://docs.netwrix.com/docs/accessanalyzer/11_6) @@ -17,7 +17,7 @@ This documentation covers **Access Analyzer 2601**, the latest release — a con Netwrix Access Analyzer is an on-premises Data Security Posture Management (DSPM) platform that helps security and compliance teams discover where sensitive data lives, who has access to it, and where access risks exist across their environment. -Organizations face a persistent challenge: sensitive data accumulates across file servers, cloud platforms, and identity systems faster than security teams can track it. Permissions expand over time, inheritance gets broken, and stale data sits untouched for years — all without anyone knowing. Access Analyzer addresses this by scanning your data sources and identity providers continuously, classifying what it finds, and surfacing the results in dashboards and reports your team can act on. +Organizations face a persistent challenge: sensitive data accumulates across file servers, cloud platforms, and identity systems faster than security teams can track it. Permissions expand over time, inheritance breaks, and stale data sits untouched for years — all without anyone knowing. Access Analyzer addresses this by scanning your data sources and identity providers continuously, classifying what it finds, and surfacing the results in dashboards and reports your team can act on. Access Analyzer connects to the following source types: @@ -26,17 +26,17 @@ Access Analyzer connects to the following source types: - **Active Directory** — Syncs users, groups, group memberships, and security risks from on-premises AD domains - **Entra ID** — Syncs users, groups, and roles from your Microsoft 365 tenant, and collects Microsoft Information Protection (MIP) sensitivity labels applied across the tenant -After each scan, results are stored in a high-performance analytics database and made available through embedded Metabase dashboards and reports. Security teams can filter by domain, file server, site, or classification type, and drill into specific findings without writing queries. +After each scan, Access Analyzer stores results in a high-performance analytics database and makes them available through embedded Metabase dashboards and reports. Security teams can filter by domain, file server, site, or classification type, and drill into specific findings without writing queries. :::note -Scans are **read-only**. Access Analyzer does not modify files, permissions, or directory objects on any scanned source. No persistent agents are installed on file servers or domain controllers — edge scanners run as short-lived jobs and terminate after each scan. +Scans are **read-only**. Access Analyzer doesn't modify files, permissions, or directory objects on any scanned source. Access Analyzer doesn't install persistent agents on file servers or domain controllers — edge scanners run as short-lived jobs and terminate after each scan. ::: ## Key Capabilities | Capability | Description | | --- | --- | -| **Sensitive Data Discovery** | Classifies file content across file servers and SharePoint Online against built-in detection patterns for PII, PHI, credentials, and financial data. Findings are mapped to compliance frameworks including GDPR, HIPAA, PCI DSS, and CCPA. | +| **Sensitive Data Discovery** | Classifies file content across file servers and SharePoint Online against built-in detection patterns for PII, PHI, credentials, and financial data. Access Analyzer maps findings to compliance frameworks including GDPR, HIPAA, PCI DSS, and CCPA. | | **Access Risk Analysis** | Identifies open access, overly permissive ACLs, broken permission inheritance, and stale entitlements across file shares and SharePoint sites. Shows effective permissions for any user or group. | | **Identity Inventory** | Continuously syncs users, groups, memberships, and roles from Active Directory and Entra ID. Tracks group nesting, stale accounts, and role assignments across your identity providers. | | **File Activity Monitoring** | Ingests real-time file system and SharePoint activity events from Netwrix Activity Monitor. Powers activity reports and enables anomaly detection and sensitive data activity tracking. Requires a separate Netwrix Activity Monitor deployment. | @@ -47,7 +47,7 @@ This section describes how Access Analyzer components are deployed and how data Access Analyzer runs entirely within your Kubernetes cluster. All components — the web application, API server, analytics database, and connector jobs — deploy to a single `access-analyzer` namespace. No data leaves your infrastructure. -The platform uses a scan-as-job model: when a scan is triggered, the Connector API creates an ephemeral Kubernetes Job for the connector type (CIFS, SharePoint, Active Directory, or Entra ID). The job runs, connects to the external source, collects data, and streams results to the data ingestion service, which bulk-inserts them into ClickHouse. When the job completes, it posts a webhook back to the Core API to finalize the scan execution record. +The platform uses a scan-as-job model: triggering a scan causes the Connector API to create an ephemeral Kubernetes Job for the connector type (CIFS, SharePoint, Active Directory, or Entra ID). The job runs, connects to the external source, collects data, and streams results to the data ingestion service, which bulk-inserts them into ClickHouse. When the job completes, it posts a webhook back to the Core API to finalize the scan execution record. ```mermaid graph TB @@ -107,11 +107,11 @@ graph TB **Connector API** — Go service that translates scan requests from the Core API into Kubernetes Job definitions. It creates connector Jobs, monitors their completion, and posts results back to the Core API via webhook. -**Connector Jobs** — Ephemeral Kubernetes Jobs that run the actual scan work. Each connector type (CIFS, SharePoint, Active Directory, Entra ID) is a containerized Python handler. Jobs connect directly to their target source, collect data, and stream rows to the Data Ingestion service in batches. Jobs are created on demand and cleaned up after completion. +**Connector Jobs** — Ephemeral Kubernetes Jobs that perform the scan work. Each connector type (CIFS, SharePoint, Active Directory, Entra ID) is a containerized Python handler. Jobs connect directly to their target source, collect data, and stream rows to the Data Ingestion service in batches. The Connector API creates Jobs on demand and cleans them up after completion. **Data Ingestion** — Python service that receives batched rows from connector jobs and bulk-inserts them into ClickHouse. Provides write isolation — connectors never write to ClickHouse directly. -**Metabase** — Embedded analytics platform pre-configured with Access Analyzer dashboards and reports. Connects to both PostgreSQL and ClickHouse via JDBC. Users access Metabase through the web app with no separate login required. +**Metabase** — Embedded analytics platform pre-configured with Access Analyzer dashboards and reports. Connects to both PostgreSQL and ClickHouse via JDBC. Users access Metabase through the web app and don't need a separate login. ### Data Stores From bb5fd856f3556f953ebf3731e937763e64e3eb4f Mon Sep 17 00:00:00 2001 From: "james.haytko" Date: Mon, 24 Aug 2026 17:44:56 -0500 Subject: [PATCH 04/36] fix: preserve underscores in anchor slugs, restore broken anchor links scripts/check-anchors.sh stripped underscores when slugifying headings, disagreeing with the github-slugger algorithm Docusaurus actually uses (which keeps underscores). The vale-dale autofix trusted this checker and rewrote anchor links like #customize-analysis-tasks-for-the- box_filemetrics-job to .../boxfilemetrics-job across accessanalyzer 11.6 and 12.0 docs, satisfying the buggy local check but breaking the real Docusaurus build (~140+ broken anchors, causing the build-and- deploy job to fail). Fix the slugify regex to keep underscores, and restore the underscores in every anchor link the autofix stripped. Co-Authored-By: Claude Sonnet 5 --- .../admin/datacollector/fsaa/workflows.md | 2 +- .../ad_passwordexpirationnotification.md | 6 +- .../admin/jobs/instantjobs/fs_defend_sdd.md | 2 +- .../11.6/admin/schema/sqldc/overview.md | 268 +++++++++--------- .../activity/ad_activitycollection.md | 4 +- .../computers/ad_deprovisioncomputers.md | 4 +- .../cleanup/computers/overview.md | 2 +- .../deprovision/ad_deprovisiongroups.md | 4 +- .../cleanup/groups/overview.md | 2 +- .../cleanup/users/ad_deprovisionusers.md | 4 +- .../activedirectory/cleanup/users/overview.md | 2 +- .../computers/ad_stalecomputers.md | 2 +- .../activedirectoryinventory/1-ad_scan.md | 2 +- .../activedirectoryinventory/2-ad_changes.md | 4 +- .../3-ad_exceptions.md | 2 +- .../ad_shadowaccess.md | 6 +- .../11.6/solutions/anyid/anyid_csv.md | 6 +- .../11.6/solutions/anyid/anyid_epicclarity.md | 6 +- .../11.6/solutions/anyid/anyid_paycom.md | 4 +- .../11.6/solutions/anyid/anyid_salesforce.md | 4 +- .../solutions/aws/groups/aws_stalegroups.md | 4 +- .../aws/policies/aws_unusedmanagedpolicies.md | 4 +- .../solutions/aws/roles/aws_staleroles.md | 4 +- .../solutions/aws/users/aws_staleusers.md | 4 +- .../box/collection/1-box_access_scans.md | 2 +- .../box/collection/1-box_activity_scans.md | 2 +- .../solutions/box/content/box_filemetrics.md | 2 +- .../box/content/box_foldermetrics.md | 2 +- .../11.6/solutions/dropbox/dropbox_content.md | 4 +- .../solutions/entraidinventory/1-aad_scan.md | 2 +- .../entraidinventory/2-aad_exceptions.md | 2 +- .../exchange/online/mailflow/ex_mailflow.md | 2 +- .../online/mailflow/ex_mailflow_domain.md | 2 +- .../online/mailflow/ex_mailflow_mailbox.md | 2 +- .../mailflow/ex_mailflow_orgoverview.md | 2 +- .../ownership/pf_folderownership.md | 4 +- .../collection/ex_mailbox_sdd.md | 2 +- .../collection/ex_publicfolder_sdd.md | 2 +- .../cleanup/delete/fs_deletefiles.md | 2 +- .../cleanup/fs_cleanupassessment.md | 6 +- .../cleanup/notify/fs_notifyowners.md | 2 +- .../filesystem/fs_brokeninheritance.md | 2 +- .../fs_resourcebasedgroupaicimport.md | 2 +- .../collection/7-spaa_exceptions.md | 2 +- .../sharepoint/content/sp_stalefiles.md | 4 +- .../effectiveaccessaudits/sp_trusteeaccess.md | 4 +- .../sharepoint/m365/sp_staleteamsites.md | 4 +- .../admin/datacollector/fsaa/workflows.md | 2 +- .../ad_passwordexpirationnotification.md | 6 +- .../activity/ad_activitycollection.md | 4 +- .../computers/ad_deprovisioncomputers.md | 4 +- .../cleanup/computers/overview.md | 2 +- .../deprovision/ad_deprovisiongroups.md | 4 +- .../cleanup/groups/overview.md | 2 +- .../cleanup/users/ad_deprovisionusers.md | 4 +- .../activedirectory/cleanup/users/overview.md | 2 +- .../computers/ad_stalecomputers.md | 2 +- .../activedirectoryinventory/1-ad_scan.md | 2 +- .../activedirectoryinventory/2-ad_changes.md | 4 +- .../3-ad_exceptions.md | 2 +- .../ad_shadowaccess.md | 6 +- .../12.0/solutions/anyid/anyid_csv.md | 6 +- .../12.0/solutions/anyid/anyid_epicclarity.md | 6 +- .../12.0/solutions/anyid/anyid_paycom.md | 4 +- .../12.0/solutions/anyid/anyid_salesforce.md | 4 +- .../solutions/aws/groups/aws_stalegroups.md | 4 +- .../aws/policies/aws_unusedmanagedpolicies.md | 4 +- .../solutions/aws/roles/aws_staleroles.md | 4 +- .../solutions/aws/users/aws_staleusers.md | 4 +- .../box/collection/1-box_access_scans.md | 2 +- .../box/collection/1-box_activity_scans.md | 2 +- .../solutions/box/content/box_filemetrics.md | 2 +- .../box/content/box_foldermetrics.md | 2 +- .../12.0/solutions/dropbox/dropbox_content.md | 4 +- .../solutions/entraidinventory/1-aad_scan.md | 2 +- .../entraidinventory/2-aad_exceptions.md | 2 +- .../exchange/online/mailflow/ex_mailflow.md | 2 +- .../online/mailflow/ex_mailflow_domain.md | 2 +- .../online/mailflow/ex_mailflow_mailbox.md | 2 +- .../mailflow/ex_mailflow_orgoverview.md | 2 +- .../ownership/pf_folderownership.md | 4 +- .../collection/ex_mailbox_sdd.md | 2 +- .../collection/ex_publicfolder_sdd.md | 2 +- .../cleanup/delete/fs_deletefiles.md | 2 +- .../cleanup/fs_cleanupassessment.md | 6 +- .../cleanup/notify/fs_notifyowners.md | 2 +- .../filesystem/fs_brokeninheritance.md | 2 +- .../fs_resourcebasedgroupaicimport.md | 2 +- .../collection/7-spaa_exceptions.md | 2 +- .../sharepoint/content/sp_stalefiles.md | 4 +- .../effectiveaccessaudits/sp_trusteeaccess.md | 4 +- .../sharepoint/m365/sp_staleteamsites.md | 4 +- scripts/check-anchors.sh | 5 +- 93 files changed, 281 insertions(+), 278 deletions(-) diff --git a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/workflows.md b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/workflows.md index f55364e625..3b263c2b21 100644 --- a/docs/accessanalyzer/11.6/admin/datacollector/fsaa/workflows.md +++ b/docs/accessanalyzer/11.6/admin/datacollector/fsaa/workflows.md @@ -164,7 +164,7 @@ Applying these analysis tasks result in the deletion of collected data. To configure and run the analysis tasks: **Step 1 –** Before job execution, modify the analysis tasks you want using the -[Customizable Analysis Parameters for FS_SDD_DELETE Job](#customizable-analysis-parameters-for-fssdddelete-job) +[Customizable Analysis Parameters for FS_SDD_DELETE Job](#customizable-analysis-parameters-for-fs_sdd_delete-job) instructions. **Step 2 –** In the Analysis Selection Pane, check the type of analysis task that will be run. diff --git a/docs/accessanalyzer/11.6/admin/jobs/instantjobs/ad_passwordexpirationnotification.md b/docs/accessanalyzer/11.6/admin/jobs/instantjobs/ad_passwordexpirationnotification.md index af02433149..f1317e3133 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/instantjobs/ad_passwordexpirationnotification.md +++ b/docs/accessanalyzer/11.6/admin/jobs/instantjobs/ad_passwordexpirationnotification.md @@ -44,7 +44,7 @@ The default analysis tasks are: - Contains a configurable parameter for the number of days until a password expires to be identified - See the - [Customizable Analysis Tasks for the AD_PasswordExpirationNotification Job](#customizable-analysis-tasks-for-the-adpasswordexpirationnotification-job) + [Customizable Analysis Tasks for the AD_PasswordExpirationNotification Job](#customizable-analysis-tasks-for-the-ad_passwordexpirationnotification-job) topic for additional information. - **2. Domain Summary** – Creates an interim processing table in the database for use by downstream analysis and report generation @@ -56,7 +56,7 @@ The default analysis tasks are: the job’s Results node - **5. Help Desk Notification** – Sends notification of users with passwords set to expire in X days - See the - [Notification Analysis Task in the AD_PasswordExpirationNotification Job](#notification-analysis-task-in-the-adpasswordexpirationnotification-job) + [Notification Analysis Task in the AD_PasswordExpirationNotification Job](#notification-analysis-task-in-the-ad_passwordexpirationnotification-job) topic for additional information. ## Action for the AD_PasswordExpirationNotification Job @@ -77,7 +77,7 @@ The default actions are: password expiration - Requires the Notification Actions license feature - See the - [Action Task in the AD_PasswordExpirationNotification Job](#action-task-in-the-adpasswordexpirationnotification-job) + [Action Task in the AD_PasswordExpirationNotification Job](#action-task-in-the-ad_passwordexpirationnotification-job) topic for additional information. In addition to the tables created by the analysis and action tasks, the diff --git a/docs/accessanalyzer/11.6/admin/jobs/instantjobs/fs_defend_sdd.md b/docs/accessanalyzer/11.6/admin/jobs/instantjobs/fs_defend_sdd.md index a805572cc2..6eb93c9d43 100644 --- a/docs/accessanalyzer/11.6/admin/jobs/instantjobs/fs_defend_sdd.md +++ b/docs/accessanalyzer/11.6/admin/jobs/instantjobs/fs_defend_sdd.md @@ -26,7 +26,7 @@ Runtime Details: - A Connection Profile must be created using the Web Services (JWT) credential account type with the specified Threat Manager App Token and assigned to this job - See the - [Custom Connection Profile for FS_DEFEND_SDD Job](#custom-connection-profile-for-fsdefendsdd-job) + [Custom Connection Profile for FS_DEFEND_SDD Job](#custom-connection-profile-for-fs_defend_sdd-job) topic for additional information - Assign the Connection Profile on the Connection tab of the job’s Properties - The Threat Manager host name with port, [HOST]:8080, and App Token are generated within Threat diff --git a/docs/accessanalyzer/11.6/admin/schema/sqldc/overview.md b/docs/accessanalyzer/11.6/admin/schema/sqldc/overview.md index 36d3354fe8..bc68d32cfb 100644 --- a/docs/accessanalyzer/11.6/admin/schema/sqldc/overview.md +++ b/docs/accessanalyzer/11.6/admin/schema/sqldc/overview.md @@ -15,194 +15,194 @@ The tables fall into two categories: --- ### [Core Data Collection Tables](coretables/overview.md) - - [SA_SQLServer_Instances](coretables/overview.md#sasqlserverinstances) - - [SA_SQLServer_Databases](coretables/overview.md#sasqlserverdatabases) - - [SA_SQLServer_EventDatabases](coretables/overview.md#sasqlservereventdatabases) - - [SA_SQLServer_Schemas](coretables/overview.md#sasqlserverschemas) - - [SA_SQLServer_Objects](coretables/overview.md#sasqlserverobjects) - - [SA_SQLServer_Columns](coretables/overview.md#sasqlservercolumns) - - [SA_SQLServer_ServerPrincipalTypes](coretables/overview.md#sasqlserverserverprincipaltypes) - - [SA_SQLServer_DatabasePrincipalTypes](coretables/overview.md#sasqlserverdatabaseprincipaltypes) - - [SA_SQLServer_ServerPrincipals](coretables/overview.md#sasqlserverserverprincipals) - - [SA_SQLServer_DatabasePrincipals](coretables/overview.md#sasqlserverdatabaseprincipals) - - [SA_SQLServer_EventServerPrincipals](coretables/overview.md#sasqlservereventserverprincipals) - - [SA_SQLServer_EventDatabasePrincipals](coretables/overview.md#sasqlservereventdatabaseprincipals) - - [SA_SQLServer_SqlLogins](coretables/overview.md#sasqlserversqllogins) - - [SA_SQLServer_ServerRoleMembers](coretables/overview.md#sasqlserverserverrolemembers) - - [SA_SQLServer_DatabaseRoleMembers](coretables/overview.md#sasqlserverdatabaserolemembers) - - [SA_SQLServer_EffectiveRoleMembership](coretables/overview.md#sasqlservereffectiverolemembership) - - [SA_SQLServer_PermissionNames](coretables/overview.md#sasqlserverpermissionnames) - - [SA_SQLServer_PermissionClasses](coretables/overview.md#sasqlserverpermissionclasses) - - [SA_SQLServer_PermissionStates](coretables/overview.md#sasqlserverpermissionstates) - - [SA_SQLServer_ServerPermissions](coretables/overview.md#sasqlserverserverpermissions) - - [SA_SQLServer_DatabasePermissions](coretables/overview.md#sasqlserverdatabasepermissions) - - [SA_SQLServer_AsymmetricKeys](coretables/overview.md#sasqlserverasymmetrickeys) - - [SA_SQLServer_AuditInformation](coretables/overview.md#sasqlserverauditinformation) - - [SA_SQLServer_AuditFiles](coretables/overview.md#sasqlserverauditfiles) - - [SA_SQLServer_AuditClassType](coretables/overview.md#sasqlserverauditclasstype) - - [SA_SQLServer_AuditActions](coretables/overview.md#sasqlserverauditactions) - - [SA_SQLServer_Statements](coretables/overview.md#sasqlserverstatements) - - [SA_SQLServer_AdditionalInformation](coretables/overview.md#sasqlserveradditionalinformation) - - [SA_SQLServer_UserEvents](coretables/overview.md#sasqlserveruserevents) - - [SA_SQLServer_Events](coretables/overview.md#sasqlserverevents) - - [SA_SQLServer_ExpressionDependencies](coretables/overview.md#sasqlserverexpressiondependencies) - - [SA_SQLServer_SDD_Criteria](coretables/overview.md#sasqlserversddcriteria) - - [SA_SQLServer_SDD_InstanceCriteria](coretables/overview.md#sasqlserversddinstancecriteria) - - [SA_SQLServer_SDD_DatabaseCriteria](coretables/overview.md#sasqlserversdddatabasecriteria) - - [SA_SQLServer_SDD_ResourceTypes](coretables/overview.md#sasqlserversddresourcetypes) - - [SA_SQLServer_SDD_Resources](coretables/overview.md#sasqlserversddresources) - - [SA_SQLServer_SDD_Matches](coretables/overview.md#sasqlserversddmatches) - - [SA_SQLServer_SDD_MatchHits](coretables/overview.md#sasqlserversddmatchhits) - - [SA_SQLServer_SDD_MatchHits_SubjectProfile](coretables/overview.md#sasqlserversddmatchhitssubjectprofile) - - [SA_SQLServer_SDD_ScanHistory](coretables/overview.md#sasqlserversddscanhistory) - - [SA_SQLServer_SDD_SupportedDataTypes](coretables/overview.md#sasqlserversddsupporteddatatypes) - - [SA_SQL_Patches](coretables/overview.md#sasqlpatches) - - [SA_SQL_Instances](coretables/overview.md#sasqlinstances) - - [SA_SQL_PasswordIssues_LIST](coretables/overview.md#sasqlpasswordissueslist) + - [SA_SQLServer_Instances](coretables/overview.md#sa_sqlserver_instances) + - [SA_SQLServer_Databases](coretables/overview.md#sa_sqlserver_databases) + - [SA_SQLServer_EventDatabases](coretables/overview.md#sa_sqlserver_eventdatabases) + - [SA_SQLServer_Schemas](coretables/overview.md#sa_sqlserver_schemas) + - [SA_SQLServer_Objects](coretables/overview.md#sa_sqlserver_objects) + - [SA_SQLServer_Columns](coretables/overview.md#sa_sqlserver_columns) + - [SA_SQLServer_ServerPrincipalTypes](coretables/overview.md#sa_sqlserver_serverprincipaltypes) + - [SA_SQLServer_DatabasePrincipalTypes](coretables/overview.md#sa_sqlserver_databaseprincipaltypes) + - [SA_SQLServer_ServerPrincipals](coretables/overview.md#sa_sqlserver_serverprincipals) + - [SA_SQLServer_DatabasePrincipals](coretables/overview.md#sa_sqlserver_databaseprincipals) + - [SA_SQLServer_EventServerPrincipals](coretables/overview.md#sa_sqlserver_eventserverprincipals) + - [SA_SQLServer_EventDatabasePrincipals](coretables/overview.md#sa_sqlserver_eventdatabaseprincipals) + - [SA_SQLServer_SqlLogins](coretables/overview.md#sa_sqlserver_sqllogins) + - [SA_SQLServer_ServerRoleMembers](coretables/overview.md#sa_sqlserver_serverrolemembers) + - [SA_SQLServer_DatabaseRoleMembers](coretables/overview.md#sa_sqlserver_databaserolemembers) + - [SA_SQLServer_EffectiveRoleMembership](coretables/overview.md#sa_sqlserver_effectiverolemembership) + - [SA_SQLServer_PermissionNames](coretables/overview.md#sa_sqlserver_permissionnames) + - [SA_SQLServer_PermissionClasses](coretables/overview.md#sa_sqlserver_permissionclasses) + - [SA_SQLServer_PermissionStates](coretables/overview.md#sa_sqlserver_permissionstates) + - [SA_SQLServer_ServerPermissions](coretables/overview.md#sa_sqlserver_serverpermissions) + - [SA_SQLServer_DatabasePermissions](coretables/overview.md#sa_sqlserver_databasepermissions) + - [SA_SQLServer_AsymmetricKeys](coretables/overview.md#sa_sqlserver_asymmetrickeys) + - [SA_SQLServer_AuditInformation](coretables/overview.md#sa_sqlserver_auditinformation) + - [SA_SQLServer_AuditFiles](coretables/overview.md#sa_sqlserver_auditfiles) + - [SA_SQLServer_AuditClassType](coretables/overview.md#sa_sqlserver_auditclasstype) + - [SA_SQLServer_AuditActions](coretables/overview.md#sa_sqlserver_auditactions) + - [SA_SQLServer_Statements](coretables/overview.md#sa_sqlserver_statements) + - [SA_SQLServer_AdditionalInformation](coretables/overview.md#sa_sqlserver_additionalinformation) + - [SA_SQLServer_UserEvents](coretables/overview.md#sa_sqlserver_userevents) + - [SA_SQLServer_Events](coretables/overview.md#sa_sqlserver_events) + - [SA_SQLServer_ExpressionDependencies](coretables/overview.md#sa_sqlserver_expressiondependencies) + - [SA_SQLServer_SDD_Criteria](coretables/overview.md#sa_sqlserver_sdd_criteria) + - [SA_SQLServer_SDD_InstanceCriteria](coretables/overview.md#sa_sqlserver_sdd_instancecriteria) + - [SA_SQLServer_SDD_DatabaseCriteria](coretables/overview.md#sa_sqlserver_sdd_databasecriteria) + - [SA_SQLServer_SDD_ResourceTypes](coretables/overview.md#sa_sqlserver_sdd_resourcetypes) + - [SA_SQLServer_SDD_Resources](coretables/overview.md#sa_sqlserver_sdd_resources) + - [SA_SQLServer_SDD_Matches](coretables/overview.md#sa_sqlserver_sdd_matches) + - [SA_SQLServer_SDD_MatchHits](coretables/overview.md#sa_sqlserver_sdd_matchhits) + - [SA_SQLServer_SDD_MatchHits_SubjectProfile](coretables/overview.md#sa_sqlserver_sdd_matchhits_subjectprofile) + - [SA_SQLServer_SDD_ScanHistory](coretables/overview.md#sa_sqlserver_sdd_scanhistory) + - [SA_SQLServer_SDD_SupportedDataTypes](coretables/overview.md#sa_sqlserver_sdd_supporteddatatypes) + - [SA_SQL_Patches](coretables/overview.md#sa_sql_patches) + - [SA_SQL_Instances](coretables/overview.md#sa_sql_instances) + - [SA_SQL_PasswordIssues_LIST](coretables/overview.md#sa_sql_passwordissues_list) ### [Reporting Tables](reportingtables/overview.md) #### [Activity](reportingtables/overview.md#activity) - - [SA_SQLServer_Activity_Details](reportingtables/overview.md#sasqlserveractivitydetails) - - [SA_SQLServer_Activity_UserDatabaseSummary](reportingtables/overview.md#sasqlserveractivityuserdatabasesummary) - - [SA_SQLServer_Activity_UserInstanceSummary](reportingtables/overview.md#sasqlserveractivityuserinstancesummary) + - [SA_SQLServer_Activity_Details](reportingtables/overview.md#sa_sqlserver_activity_details) + - [SA_SQLServer_Activity_UserDatabaseSummary](reportingtables/overview.md#sa_sqlserver_activity_userdatabasesummary) + - [SA_SQLServer_Activity_UserInstanceSummary](reportingtables/overview.md#sa_sqlserver_activity_userinstancesummary) #### [Authentication](reportingtables/overview.md#authentication) - - [SA_SQLServer_Authentication_Details](reportingtables/overview.md#sasqlserverauthenticationdetails) - - [SA_SQLServer_Authentication_Summary](reportingtables/overview.md#sasqlserverauthenticationsummary) + - [SA_SQLServer_Authentication_Details](reportingtables/overview.md#sa_sqlserver_authentication_details) + - [SA_SQLServer_Authentication_Summary](reportingtables/overview.md#sa_sqlserver_authentication_summary) #### [Control Server](reportingtables/overview.md#control-server) - - [SA_SQLServer_ControlServer_Details](reportingtables/overview.md#sasqlservercontrolserverdetails) - - [SA_SQLServer_ControlServer_DomainUsers](reportingtables/overview.md#sasqlservercontrolserverdomainusers) - - [SA_SQLServer_ControlServer_InstanceSummary](reportingtables/overview.md#sasqlservercontrolserverinstancesummary) + - [SA_SQLServer_ControlServer_Details](reportingtables/overview.md#sa_sqlserver_controlserver_details) + - [SA_SQLServer_ControlServer_DomainUsers](reportingtables/overview.md#sa_sqlserver_controlserver_domainusers) + - [SA_SQLServer_ControlServer_InstanceSummary](reportingtables/overview.md#sa_sqlserver_controlserver_instancesummary) #### [Database Principals](reportingtables/overview.md#database-principals) - - [SA_SQLServer_DatabasePrincipals_Details](reportingtables/overview.md#sasqlserverdatabaseprincipalsdetails) - - [SA_SQLServer_DatabasePrincipals_InstanceSummary](reportingtables/overview.md#sasqlserverdatabaseprincipalsinstancesummary) + - [SA_SQLServer_DatabasePrincipals_Details](reportingtables/overview.md#sa_sqlserver_databaseprincipals_details) + - [SA_SQLServer_DatabasePrincipals_InstanceSummary](reportingtables/overview.md#sa_sqlserver_databaseprincipals_instancesummary) #### [Database Size](reportingtables/overview.md#database-size) - - [SA_SQLServer_DatabaseSize_Details](reportingtables/overview.md#sasqlserverdatabasesizedetails) - - [SA_SQLServer_DatabaseSize_Summary](reportingtables/overview.md#sasqlserverdatabasesizesummary) + - [SA_SQLServer_DatabaseSize_Details](reportingtables/overview.md#sa_sqlserver_databasesize_details) + - [SA_SQLServer_DatabaseSize_Summary](reportingtables/overview.md#sa_sqlserver_databasesize_summary) #### [Direct Permissions](reportingtables/overview.md#direct-permissions) - - [SA_SQLServer_DirectPermissions_DatabaseDetails](reportingtables/overview.md#sasqlserverdirectpermissionsdatabasedetails) - - [SA_SQLServer_DirectPermissions_DatabaseSummary](reportingtables/overview.md#sasqlserverdirectpermissionsdatabasesummary) - - [SA_SQLServer_DirectPermissions_SchemaDetails](reportingtables/overview.md#sasqlserverdirectpermissionsschemadetails) - - [SA_SQLServer_DirectPermissions_SchemaSummary](reportingtables/overview.md#sasqlserverdirectpermissionsschemasummary) - - [SA_SQLServer_DirectPermissions_ServerDetails](reportingtables/overview.md#sasqlserverdirectpermissionsserverdetails) - - [SA_SQLServer_DirectPermissions_ServerSummary](reportingtables/overview.md#sasqlserverdirectpermissionsserversummary) + - [SA_SQLServer_DirectPermissions_DatabaseDetails](reportingtables/overview.md#sa_sqlserver_directpermissions_databasedetails) + - [SA_SQLServer_DirectPermissions_DatabaseSummary](reportingtables/overview.md#sa_sqlserver_directpermissions_databasesummary) + - [SA_SQLServer_DirectPermissions_SchemaDetails](reportingtables/overview.md#sa_sqlserver_directpermissions_schemadetails) + - [SA_SQLServer_DirectPermissions_SchemaSummary](reportingtables/overview.md#sa_sqlserver_directpermissions_schemasummary) + - [SA_SQLServer_DirectPermissions_ServerDetails](reportingtables/overview.md#sa_sqlserver_directpermissions_serverdetails) + - [SA_SQLServer_DirectPermissions_ServerSummary](reportingtables/overview.md#sa_sqlserver_directpermissions_serversummary) #### [Domain User Permissions](reportingtables/overview.md#domain-user-permissions) - - [SA_SQLServer_DomainUserPermissions_Details](reportingtables/overview.md#sasqlserverdomainuserpermissionsdetails) - - [SA_SQLServer_DomainUserPermissions_Summary](reportingtables/overview.md#sasqlserverdomainuserpermissionssummary) + - [SA_SQLServer_DomainUserPermissions_Details](reportingtables/overview.md#sa_sqlserver_domainuserpermissions_details) + - [SA_SQLServer_DomainUserPermissions_Summary](reportingtables/overview.md#sa_sqlserver_domainuserpermissions_summary) #### [Effective Role Members](reportingtables/overview.md#effective-role-members) - - [SA_SQLServer_EffectiveRoleMember_Summary](reportingtables/overview.md#sasqlservereffectiverolemembersummary) + - [SA_SQLServer_EffectiveRoleMember_Summary](reportingtables/overview.md#sa_sqlserver_effectiverolemember_summary) #### [Instance Summary](reportingtables/overview.md#instance-summary) - - [SA_SQLServer_InstanceSummary](reportingtables/overview.md#sasqlserverinstancesummary) + - [SA_SQLServer_InstanceSummary](reportingtables/overview.md#sa_sqlserver_instancesummary) #### [Logons](reportingtables/overview.md#logons) - - [SA_SQLServer_Logons_Details](reportingtables/overview.md#sasqlserverlogonsdetails) - - [SA_SQLServer_Logons_Summary](reportingtables/overview.md#sasqlserverlogonssummary) + - [SA_SQLServer_Logons_Details](reportingtables/overview.md#sa_sqlserver_logons_details) + - [SA_SQLServer_Logons_Summary](reportingtables/overview.md#sa_sqlserver_logons_summary) #### [Password Issues](reportingtables/overview.md#password-issues) - - [SA_SQLServer_PasswordIssues_Details](reportingtables/overview.md#sasqlserverpasswordissuesdetails) - - [SA_SQLServer_PasswordIssues_Summary](reportingtables/overview.md#sasqlserverpasswordissuessummary) + - [SA_SQLServer_PasswordIssues_Details](reportingtables/overview.md#sa_sqlserver_passwordissues_details) + - [SA_SQLServer_PasswordIssues_Summary](reportingtables/overview.md#sa_sqlserver_passwordissues_summary) #### [Permission Changes](reportingtables/overview.md#permission-changes) - - [SA_SQLServer_PermissionChanges_Details](reportingtables/overview.md#sasqlserverpermissionchangesdetails) - - [SA_SQLServer_PermissionChanges_InstanceSummary](reportingtables/overview.md#sasqlserverpermissionchangesinstancesummary) + - [SA_SQLServer_PermissionChanges_Details](reportingtables/overview.md#sa_sqlserver_permissionchanges_details) + - [SA_SQLServer_PermissionChanges_InstanceSummary](reportingtables/overview.md#sa_sqlserver_permissionchanges_instancesummary) #### [Public Permissions](reportingtables/overview.md#public-permissions) - - [SA_SQLServer_PublicPermissions_Details](reportingtables/overview.md#sasqlserverpublicpermissionsdetails) - - [SA_SQLServer_PublicPermissions_DatabaseSummary](reportingtables/overview.md#sasqlserverpublicpermissionsdatabasesummary) - - [SA_SQLServer_PublicPermissions_InstanceSummary](reportingtables/overview.md#sasqlserverpublicpermissionsinstancesummary) - - [SA_SQLServer_PublicPermissions_NonDefault](reportingtables/overview.md#sasqlserverpublicpermissionsnondefault) + - [SA_SQLServer_PublicPermissions_Details](reportingtables/overview.md#sa_sqlserver_publicpermissions_details) + - [SA_SQLServer_PublicPermissions_DatabaseSummary](reportingtables/overview.md#sa_sqlserver_publicpermissions_databasesummary) + - [SA_SQLServer_PublicPermissions_InstanceSummary](reportingtables/overview.md#sa_sqlserver_publicpermissions_instancesummary) + - [SA_SQLServer_PublicPermissions_NonDefault](reportingtables/overview.md#sa_sqlserver_publicpermissions_nondefault) #### [Role Members](reportingtables/overview.md#role-members) - - [SA_SQLServer_RoleMember_Details](reportingtables/overview.md#sasqlserverrolememberdetails) - - [SA_SQLServer_RoleMember_Summary](reportingtables/overview.md#sasqlserverrolemembersummary) + - [SA_SQLServer_RoleMember_Details](reportingtables/overview.md#sa_sqlserver_rolemember_details) + - [SA_SQLServer_RoleMember_Summary](reportingtables/overview.md#sa_sqlserver_rolemember_summary) #### [Security Assessment](reportingtables/overview.md#security-assessment) - - [SA_SQLServer_SecurityAssessment_Results](reportingtables/overview.md#sasqlserversecurityassessmentresults) - - [SA_SQLServer_SecurityAssessment_CategorySummary](reportingtables/overview.md#sasqlserversecurityassessmentcategorysummary) + - [SA_SQLServer_SecurityAssessment_Results](reportingtables/overview.md#sa_sqlserver_securityassessment_results) + - [SA_SQLServer_SecurityAssessment_CategorySummary](reportingtables/overview.md#sa_sqlserver_securityassessment_categorysummary) #### [Sensitive Data](reportingtables/overview.md#sensitive-data) - - [SA_SQLServer_SensitiveData_Details](reportingtables/overview.md#sasqlserversensitivedatadetails) - - [SA_SQLServer_SensitiveData_DatabaseSummary](reportingtables/overview.md#sasqlserversensitivedatadatabasesummary) - - [SA_SQLServer_SensitiveData_EnterpriseSummary](reportingtables/overview.md#sasqlserversensitivedataenterprisesummary) + - [SA_SQLServer_SensitiveData_Details](reportingtables/overview.md#sa_sqlserver_sensitivedata_details) + - [SA_SQLServer_SensitiveData_DatabaseSummary](reportingtables/overview.md#sa_sqlserver_sensitivedata_databasesummary) + - [SA_SQLServer_SensitiveData_EnterpriseSummary](reportingtables/overview.md#sa_sqlserver_sensitivedata_enterprisesummary) #### [Sensitive Data Activity](reportingtables/overview.md#sensitive-data-activity) - - [SA_SQLServer_SensitiveDataActivity_Details](reportingtables/overview.md#sasqlserversensitivedataactivitydetails) - - [SA_SQLServer_SensitiveDataActivity_UserSummary](reportingtables/overview.md#sasqlserversensitivedataactivityusersummary) + - [SA_SQLServer_SensitiveDataActivity_Details](reportingtables/overview.md#sa_sqlserver_sensitivedataactivity_details) + - [SA_SQLServer_SensitiveDataActivity_UserSummary](reportingtables/overview.md#sa_sqlserver_sensitivedataactivity_usersummary) #### [Sensitive Data Permissions](reportingtables/overview.md#sensitive-data-permissions) - - [SA_SQLServer_SensitiveDataPermissions_Details](reportingtables/overview.md#sasqlserversensitivedatapermissionsdetails) - - [SA_SQLServer_SensitiveDataPermissions_DatabaseSummary](reportingtables/overview.md#sasqlserversensitivedatapermissionsdatabasesummary) + - [SA_SQLServer_SensitiveDataPermissions_Details](reportingtables/overview.md#sa_sqlserver_sensitivedatapermissions_details) + - [SA_SQLServer_SensitiveDataPermissions_DatabaseSummary](reportingtables/overview.md#sa_sqlserver_sensitivedatapermissions_databasesummary) #### [Server Permissions](reportingtables/overview.md#server-permissions) - - [SA_SQLServer_ServerPermission_Details](reportingtables/overview.md#sasqlserverserverpermissiondetails) - - [SA_SQLServer_ServerPermission_InstanceSummary](reportingtables/overview.md#sasqlserverserverpermissioninstancesummary) + - [SA_SQLServer_ServerPermission_Details](reportingtables/overview.md#sa_sqlserver_serverpermission_details) + - [SA_SQLServer_ServerPermission_InstanceSummary](reportingtables/overview.md#sa_sqlserver_serverpermission_instancesummary) #### [Server Principals](reportingtables/overview.md#server-principals) - - [SA_SQLServer_ServerPrincipals_Details](reportingtables/overview.md#sasqlserverserverprincipalsdetails) - - [SA_SQLServer_ServerPrincipals_InstanceSummary](reportingtables/overview.md#sasqlserverserverprincipalsinstancesummary) + - [SA_SQLServer_ServerPrincipals_Details](reportingtables/overview.md#sa_sqlserver_serverprincipals_details) + - [SA_SQLServer_ServerPrincipals_InstanceSummary](reportingtables/overview.md#sa_sqlserver_serverprincipals_instancesummary) #### [SysAdmins](reportingtables/overview.md#sysadmins) - - [SA_SQLServer_SysAdmins_Details](reportingtables/overview.md#sasqlserversysadminsdetails) - - [SA_SQLServer_SysAdmins_DomainUsers](reportingtables/overview.md#sasqlserversysadminsdomainusers) - - [SA_SQLServer_SysAdmins_InstanceSummary](reportingtables/overview.md#sasqlserversysadminsinstancesummary) + - [SA_SQLServer_SysAdmins_Details](reportingtables/overview.md#sa_sqlserver_sysadmins_details) + - [SA_SQLServer_SysAdmins_DomainUsers](reportingtables/overview.md#sa_sqlserver_sysadmins_domainusers) + - [SA_SQLServer_SysAdmins_InstanceSummary](reportingtables/overview.md#sa_sqlserver_sysadmins_instancesummary) #### [Unusual Activity](reportingtables/overview.md#unusual-activity) - - [SA_SQLServer_UnusualHourlyUserActivity](reportingtables/overview.md#sasqlserverunusualhourlyuseractivity) - - [SA_SQLServer_UnusualActivitySummary](reportingtables/overview.md#sasqlserverunusualactivitysummary) + - [SA_SQLServer_UnusualHourlyUserActivity](reportingtables/overview.md#sa_sqlserver_unusualhourlyuseractivity) + - [SA_SQLServer_UnusualActivitySummary](reportingtables/overview.md#sa_sqlserver_unusualactivitysummary) #### [User Logins](reportingtables/overview.md#user-logins) - - [SA_SQLServer_UserLogins_Details](reportingtables/overview.md#sasqlserveruserloginsdetails) - - [SA_SQLServer_UserLogins_Summary](reportingtables/overview.md#sasqlserveruserloginssummary) + - [SA_SQLServer_UserLogins_Details](reportingtables/overview.md#sa_sqlserver_userlogins_details) + - [SA_SQLServer_UserLogins_Summary](reportingtables/overview.md#sa_sqlserver_userlogins_summary) #### [Best Practices](reportingtables/overview.md#best-practices) - - [SA_SQL_BestPractices](reportingtables/overview.md#sasqlbestpractices) - - [SA_SQL_BestPractices_Summary](reportingtables/overview.md#sasqlbestpracticessummary) + - [SA_SQL_BestPractices](reportingtables/overview.md#sa_sql_bestpractices) + - [SA_SQL_BestPractices_Summary](reportingtables/overview.md#sa_sql_bestpractices_summary) #### [CMD Shell](reportingtables/overview.md#cmd-shell) - - [SA_SQL_CMDShell_Status](reportingtables/overview.md#sasqlcmdshellstatus) + - [SA_SQL_CMDShell_Status](reportingtables/overview.md#sa_sql_cmdshell_status) #### [Linked Servers](reportingtables/overview.md#linked-servers) - - [SA_SQL_LinkedServer_Details](reportingtables/overview.md#sasqllinkedserverdetails) - - [SA_SQL_LinkedServer_Summary](reportingtables/overview.md#sasqllinkedserversummary) + - [SA_SQL_LinkedServer_Details](reportingtables/overview.md#sa_sql_linkedserver_details) + - [SA_SQL_LinkedServer_Summary](reportingtables/overview.md#sa_sql_linkedserver_summary) ### [Views](views/overview.md) - - [SA_SQLServer_FullEventsView](views/overview.md#sasqlserverfulleventsview) - - [SA_SQLServer_ServerPrincipalsView](views/overview.md#sasqlserverserverprincipalsview) - - [SA_SQLServer_SqlLoginsView](views/overview.md#sasqlserversqlloginsview) - - [SA_SQLServer_DatabasePrincipalsView](views/overview.md#sasqlserverdatabaseprincipalsview) - - [SA_SQLServer_PermissionsView](views/overview.md#sasqlserverpermissionsview) - - [SA_SQLServer_RoleMembersView](views/overview.md#sasqlserverrolemembersview) - - [SA_SQLServer_SqlDatabaseView](views/overview.md#sasqlserversqldatabaseview) - - [SA_SQLServer_DailyLogonsView](views/overview.md#sasqlserverdailylogonsview) - - [SA_SQLServer_SDD_ResourcesView](views/overview.md#sasqlserversddresourcesview) - - [SA_SQLServer_SDD_MatchesView](views/overview.md#sasqlserversddmatchesview) - - [SA_SQLServer_SDD_MatchHitsView](views/overview.md#sasqlserversddmatchhitsview) - - [SA_SQLServer_SensitiveDataPermissionsView](views/overview.md#sasqlserversensitivedatapermissionsview) - - [SA_SQLServer_SDD_MatchHits_SubjectProfileView](views/overview.md#sasqlserversddmatchhitssubjectprofileview) - - [SA_SQLServer_SensitiveDataFullPermissionsView](views/overview.md#sasqlserversensitivedatafullpermissionsview) - - [SA_SQLServer_EffectiveRoleMembershipView](views/overview.md#sasqlservereffectiverolemembershipview) - - [SA_SQL_SDD_MatchesView](views/overview.md#sasqlsddmatchesview) - - [SA_SQL_SDD_MatchHitsView](views/overview.md#sasqlsddmatchhitsview) + - [SA_SQLServer_FullEventsView](views/overview.md#sa_sqlserver_fulleventsview) + - [SA_SQLServer_ServerPrincipalsView](views/overview.md#sa_sqlserver_serverprincipalsview) + - [SA_SQLServer_SqlLoginsView](views/overview.md#sa_sqlserver_sqlloginsview) + - [SA_SQLServer_DatabasePrincipalsView](views/overview.md#sa_sqlserver_databaseprincipalsview) + - [SA_SQLServer_PermissionsView](views/overview.md#sa_sqlserver_permissionsview) + - [SA_SQLServer_RoleMembersView](views/overview.md#sa_sqlserver_rolemembersview) + - [SA_SQLServer_SqlDatabaseView](views/overview.md#sa_sqlserver_sqldatabaseview) + - [SA_SQLServer_DailyLogonsView](views/overview.md#sa_sqlserver_dailylogonsview) + - [SA_SQLServer_SDD_ResourcesView](views/overview.md#sa_sqlserver_sdd_resourcesview) + - [SA_SQLServer_SDD_MatchesView](views/overview.md#sa_sqlserver_sdd_matchesview) + - [SA_SQLServer_SDD_MatchHitsView](views/overview.md#sa_sqlserver_sdd_matchhitsview) + - [SA_SQLServer_SensitiveDataPermissionsView](views/overview.md#sa_sqlserver_sensitivedatapermissionsview) + - [SA_SQLServer_SDD_MatchHits_SubjectProfileView](views/overview.md#sa_sqlserver_sdd_matchhits_subjectprofileview) + - [SA_SQLServer_SensitiveDataFullPermissionsView](views/overview.md#sa_sqlserver_sensitivedatafullpermissionsview) + - [SA_SQLServer_EffectiveRoleMembershipView](views/overview.md#sa_sqlserver_effectiverolemembershipview) + - [SA_SQL_SDD_MatchesView](views/overview.md#sa_sql_sdd_matchesview) + - [SA_SQL_SDD_MatchHitsView](views/overview.md#sa_sql_sdd_matchhitsview) ### [Enumeration & Lookup Values Reference](enumeration/overview.md) - - [Server Principal Types](enumeration/overview.md#server-principal-types-sasqlserverserverprincipaltypes) - - [Database Principal Types](enumeration/overview.md#database-principal-types-sasqlserverdatabaseprincipaltypes) - - [Permission States](enumeration/overview.md#permission-states-sasqlserverpermissionstates) - - [Permission Classes](enumeration/overview.md#permission-classes-sasqlserverpermissionclasses) - - [Permission Names](enumeration/overview.md#permission-names-sasqlserverpermissionnames) - - [Audit Class Types](enumeration/overview.md#audit-class-types-sasqlserverauditclasstype) - - [Audit Actions (Common)](enumeration/overview.md#audit-actions-common-sasqlserverauditactions) - - [SDD Resource Types](enumeration/overview.md#sdd-resource-types-sasqlserversddresourcetypes) + - [Server Principal Types](enumeration/overview.md#server-principal-types-sa_sqlserver_serverprincipaltypes) + - [Database Principal Types](enumeration/overview.md#database-principal-types-sa_sqlserver_databaseprincipaltypes) + - [Permission States](enumeration/overview.md#permission-states-sa_sqlserver_permissionstates) + - [Permission Classes](enumeration/overview.md#permission-classes-sa_sqlserver_permissionclasses) + - [Permission Names](enumeration/overview.md#permission-names-sa_sqlserver_permissionnames) + - [Audit Class Types](enumeration/overview.md#audit-class-types-sa_sqlserver_auditclasstype) + - [Audit Actions (Common)](enumeration/overview.md#audit-actions-common-sa_sqlserver_auditactions) + - [SDD Resource Types](enumeration/overview.md#sdd-resource-types-sa_sqlserver_sdd_resourcetypes) - [SDD Match Location Bitmask](enumeration/overview.md#sdd-match-location-bitmask) - - [Membership Source](enumeration/overview.md#membership-source-sasqlservereffectiverolemembershipmembershipsource) - - [Database Type](enumeration/overview.md#database-type-sasqlservereffectiverolemembershipdatabasetype) + - [Membership Source](enumeration/overview.md#membership-source-sa_sqlserver_effectiverolemembershipmembership_source) + - [Database Type](enumeration/overview.md#database-type-sa_sqlserver_effectiverolemembershipdatabase_type) ### [Table Relationship Diagrams (ERD)](erd/overview.md) - [High-Level Overview](erd/overview.md#high-level-overview) @@ -215,8 +215,8 @@ The tables fall into two categories: - [Complete Index List](indexreference/overview.md#complete-index-listing) ### [Scalar Functions & Stored Procedures](functions/overview.md) - - [SA_SQL_GetFriendlyName](functions/overview.md#sasqlgetfriendlyname-scalar-function) - - [SA_SQLServer_BinarySIDToString](functions/overview.md#sasqlserverbinarysidtostring-scalar-function) - - [SA_SQLServer_GetAuditFileComparisonString](functions/overview.md#sasqlservergetauditfilecomparisonstring-scalar-function) - - [SA_SQLServer_CreateOrUpdateSDDResource](functions/overview.md#sasqlservercreateorupdatesddresource-stored-procedure) + - [SA_SQL_GetFriendlyName](functions/overview.md#sa_sql_getfriendlyname-scalar-function) + - [SA_SQLServer_BinarySIDToString](functions/overview.md#sa_sqlserver_binarysidtostring-scalar-function) + - [SA_SQLServer_GetAuditFileComparisonString](functions/overview.md#sa_sqlserver_getauditfilecomparisonstring-scalar-function) + - [SA_SQLServer_CreateOrUpdateSDDResource](functions/overview.md#sa_sqlserver_createorupdatesddresource-stored-procedure) diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/ad_activitycollection.md b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/ad_activitycollection.md index 4818f46fcc..fec9539bb5 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/activity/ad_activitycollection.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/activity/ad_activitycollection.md @@ -18,7 +18,7 @@ Enterprise Auditor can retrieve AD Activity data in two ways: - API Server connected to the archive logs You configure this in the query. See the -[Queries for the AD_ActivityCollection Job](#queries-for-the-adactivitycollection-job) topic for +[Queries for the AD_ActivityCollection Job](#queries-for-the-ad_activitycollection-job) topic for additional information. ## Parameter Configuration @@ -48,7 +48,7 @@ The AD_ActivityCollection page has the following configurable parameters: - Number of days to retain activity data in the AIC See the -[Customize Analysis Parameters for the AD_ActivityCollection Job](#customize-analysis-parameters-for-the-adactivitycollection-job) +[Customize Analysis Parameters for the AD_ActivityCollection Job](#customize-analysis-parameters-for-the-ad_activitycollection-job) topic for additional information. ## Queries for the AD_ActivityCollection Job diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/computers/ad_deprovisioncomputers.md b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/computers/ad_deprovisioncomputers.md index 8a8bede5b2..5ab7c7d9b5 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/computers/ad_deprovisioncomputers.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/computers/ad_deprovisioncomputers.md @@ -29,7 +29,7 @@ The AD_DeprovisionComputers page has the following configurable parameters: - Days in the Staging OU before Deleting Account See the -[Customizable Analysis Parameters for the AD_DeprovisionComputers Job](#customizable-analysis-parameters-for-the-addeprovisioncomputers-job) +[Customizable Analysis Parameters for the AD_DeprovisionComputers Job](#customizable-analysis-parameters-for-the-ad_deprovisioncomputers-job) topic for additional information. ## Analysis Tasks for the AD_DeprovisionComputers Job @@ -47,7 +47,7 @@ The default analysis tasks are: under the job’s Results node - This analysis task contains a configurable parameter: `@days_before_deleting`. See the - [Customizable Analysis Parameters for the AD_DeprovisionComputers Job](#customizable-analysis-parameters-for-the-addeprovisioncomputers-job) + [Customizable Analysis Parameters for the AD_DeprovisionComputers Job](#customizable-analysis-parameters-for-the-ad_deprovisioncomputers-job) topic for additional information. ### Customizable Analysis Parameters for the AD_DeprovisionComputers Job diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/computers/overview.md b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/computers/overview.md index df604845b2..df55ad2b2a 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/computers/overview.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/computers/overview.md @@ -25,7 +25,7 @@ The jobs in the 3.Computers Job Group are: - The .Active Directory Inventory Job Group needs to be successfully run - For the AD_DeprovisionComputers Job, the target OU needs to be manually set in the Move Computers Action Task before executing the actions. See the - [Action Tasks for the AD_DeprovisionComputers Job](/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/computers/ad_deprovisioncomputers.md#action-tasks-for-the-addeprovisioncomputers-job) + [Action Tasks for the AD_DeprovisionComputers Job](/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/computers/ad_deprovisioncomputers.md#action-tasks-for-the-ad_deprovisioncomputers-job) topic for additional information. - The AD_DeprovisionComputers Job needs to be run before running the AD_DeprovisionComputers_Status Job diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/deprovision/ad_deprovisiongroups.md b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/deprovision/ad_deprovisiongroups.md index 41cbf32a9d..df6f26adb7 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/deprovision/ad_deprovisiongroups.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/deprovision/ad_deprovisiongroups.md @@ -32,7 +32,7 @@ The AD_DeprovisionGroups page has the following configurable parameters: - Days in the Staging OU before deletion See the -[Customizable Analysis Parameters for the AD_DeprovisionGroups Job](#customizable-analysis-parameters-for-the-addeprovisiongroups-job) +[Customizable Analysis Parameters for the AD_DeprovisionGroups Job](#customizable-analysis-parameters-for-the-ad_deprovisiongroups-job) topic for additional information. ## Analysis Tasks for the AD_DeprovisionGroups Job @@ -49,7 +49,7 @@ The default analysis tasks are: - Groups to Delete – Identifies groups in the Stale Groups OU that are ready to be deleted - This analysis task contains a configurable parameter: `@days_before_deleting`. See the - [Customizable Analysis Parameters for the AD_DeprovisionGroups Job](#customizable-analysis-parameters-for-the-addeprovisiongroups-job) + [Customizable Analysis Parameters for the AD_DeprovisionGroups Job](#customizable-analysis-parameters-for-the-ad_deprovisiongroups-job) topic for additional information. ### Customizable Analysis Parameters for the AD_DeprovisionGroups Job diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/overview.md b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/overview.md index 2c9753cc28..380d3f484b 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/overview.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/overview.md @@ -40,7 +40,7 @@ The jobs in the 1.Groups Job Group are: - The .Active Directory Inventory Job Group needs to be successfully run - For the AD_DeprovisionGroups Job, the target OU needs to be manually set in the Move Groups Action Task before executing the actions. See the - [Action Tasks for the AD_DepvisionGroups Job](/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/deprovision/ad_deprovisiongroups.md#action-tasks-for-the-addepvisiongroups-job) + [Action Tasks for the AD_DepvisionGroups Job](/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/groups/deprovision/ad_deprovisiongroups.md#action-tasks-for-the-ad_depvisiongroups-job) topic for additional information. - The AD_DeprovisionGroups Job needs to be run before running the AD_DeprovisionGroups_Status Job diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/users/ad_deprovisionusers.md b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/users/ad_deprovisionusers.md index a3b6ae7d22..8f3b1602fc 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/users/ad_deprovisionusers.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/users/ad_deprovisionusers.md @@ -33,7 +33,7 @@ The AD_DeprovisionUsers page has the following configurable parameters: - Days in the Stale Users OU before being deleted See the -[Customizable Analysis Parameters for the AD_DeprovisionUsers Job](#customizable-analysis-parameters-for-the-addeprovisionusers-job) +[Customizable Analysis Parameters for the AD_DeprovisionUsers Job](#customizable-analysis-parameters-for-the-ad_deprovisionusers-job) topic for additional information. ## Analysis Tasks for the AD_DeprovisionUsers Job @@ -50,7 +50,7 @@ The default analysis tasks are: deleted - This analysis task contains a configurable parameter: `@days_before_deleting`. See the - [Customizable Analysis Parameters for the AD_DeprovisionUsers Job](#customizable-analysis-parameters-for-the-addeprovisionusers-job) + [Customizable Analysis Parameters for the AD_DeprovisionUsers Job](#customizable-analysis-parameters-for-the-ad_deprovisionusers-job) topic for additional information. - Identify Group Membership – Identifies stale user membership to remove diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/users/overview.md b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/users/overview.md index 3a4e314d16..87291e028e 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/users/overview.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/users/overview.md @@ -24,7 +24,7 @@ The jobs in the 2.Users Job Group are: - The .Active Directory Inventory Job Group needs to be successfully run - For the AD_DeprovisionUsers Job, the target OU needs to be manually set in the Move Users Action Task before executing the actions. See the - [Action Tasks for the AD_DeprovisionUsers Job](/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/users/ad_deprovisionusers.md#action-tasks-for-the-addeprovisionusers-job) + [Action Tasks for the AD_DeprovisionUsers Job](/docs/accessanalyzer/11.6/solutions/activedirectory/cleanup/users/ad_deprovisionusers.md#action-tasks-for-the-ad_deprovisionusers-job) topic for additional information. - The AD_DeprovisionUsers Job needs to be run before running the AD_DeprovisionUsers_Status Job diff --git a/docs/accessanalyzer/11.6/solutions/activedirectory/computers/ad_stalecomputers.md b/docs/accessanalyzer/11.6/solutions/activedirectory/computers/ad_stalecomputers.md index ddd1d00672..d2fa23adfe 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectory/computers/ad_stalecomputers.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectory/computers/ad_stalecomputers.md @@ -21,7 +21,7 @@ The AD_StaleComputers Job has the following configurable parameters: - Consider disabled accounts as stale See the -[Customizable Analysis Parameters for the AD_StaleComputers Job](#customizable-analysis-parameters-for-the-adstalecomputers-job) +[Customizable Analysis Parameters for the AD_StaleComputers Job](#customizable-analysis-parameters-for-the-ad_stalecomputers-job) topic for additional information. ## Analysis Tasks for the AD_StaleComputers Job diff --git a/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/1-ad_scan.md b/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/1-ad_scan.md index 8da8be1a55..5fb9049f07 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/1-ad_scan.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/1-ad_scan.md @@ -21,7 +21,7 @@ The 1-AD_Scan Job uses the ADInventory Data Collector for the following query: objects - This query can be modified. See the - [Customize the 1-AD_Scan Query](#customize-the-1-adscan-query) topic for additional + [Customize the 1-AD_Scan Query](#customize-the-1-ad_scan-query) topic for additional information. ### Customize the 1-AD_Scan Query diff --git a/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/2-ad_changes.md b/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/2-ad_changes.md index 1972be10ca..2804cfc58c 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/2-ad_changes.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/2-ad_changes.md @@ -13,7 +13,7 @@ Inventory Job Group. Select the Query Option to **Track changes into Change tracking tables** in the 1-AD_Scan Job so the Analysis Tasks in the 2-AD_Changes Job work. See Step 4 of the -[Customize the 1-AD_Scan Query](/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/1-ad_scan.md#customize-the-1-adscan-query) +[Customize the 1-AD_Scan Query](/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/1-ad_scan.md#customize-the-1-ad_scan-query) topic for additional information. ## Analysis Tasks for the 2-AD_Changes Job @@ -113,7 +113,7 @@ following analysis tasks are deselected by default: Notification must have recipients configured for the analysis task. Optionally, the email subject and body can be modified. See the -[Notification Analysis Tasks for the 2-AD_Changes Job](#notification-analysis-tasks-for-the-2-adchanges-job) +[Notification Analysis Tasks for the 2-AD_Changes Job](#notification-analysis-tasks-for-the-2-ad_changes-job) topic for additional information. In addition to the tables and views created by the analysis tasks, the 2-AD_Changes Job produces the diff --git a/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/3-ad_exceptions.md b/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/3-ad_exceptions.md index c2c5307fbb..60de48c376 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/3-ad_exceptions.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectoryinventory/3-ad_exceptions.md @@ -28,7 +28,7 @@ The 3-AD_Exceptions Job has the following configurable parameters: - List of administrative groups See the -[Customize Analysis Parameters for the 3-AD_Exceptions Job](#customize-analysis-parameters-for-the-3-adexceptions-job) +[Customize Analysis Parameters for the 3-AD_Exceptions Job](#customize-analysis-parameters-for-the-3-ad_exceptions-job) topic for additional information. ## Analysis Tasks for the 3-AD_Exceptions Job diff --git a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/ad_shadowaccess.md b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/ad_shadowaccess.md index 6ace5fe224..eaa205d585 100644 --- a/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/ad_shadowaccess.md +++ b/docs/accessanalyzer/11.6/solutions/activedirectorypermissionsanalyzer/ad_shadowaccess.md @@ -55,7 +55,7 @@ The default analysis tasks are: Results node - This Analysis Task has configurable parameters. See the - [Configure the Analysis Tasks for the AD_ShadowAccess Job](#configure-the-analysis-tasks-for-the-adshadowaccess-job) + [Configure the Analysis Tasks for the AD_ShadowAccess Job](#configure-the-analysis-tasks-for-the-ad_shadowaccess-job) topic for additional information. - Shadow Access Paths Cleanup – Removes calculated rows that are no longer used @@ -70,7 +70,7 @@ the following pre-configured reports. See the -[Report Functions for the AD_ShadowAccess Job](#report-functions-for-the-adshadowaccess-job) topic +[Report Functions for the AD_ShadowAccess Job](#report-functions-for-the-ad_shadowaccess-job) topic for additional information. ### Customizable Analysis Tasks for the AD_ShadowAccess Job @@ -88,7 +88,7 @@ The default values for customizable parameters are: | @disabled | 0 | Set to 0 to ignore disabled users | | See the -[Configure the Analysis Tasks for the AD_ShadowAccess Job](#configure-the-analysis-tasks-for-the-adshadowaccess-job) +[Configure the Analysis Tasks for the AD_ShadowAccess Job](#configure-the-analysis-tasks-for-the-ad_shadowaccess-job) topic for additional information. ### Configure the Analysis Tasks for the AD_ShadowAccess Job diff --git a/docs/accessanalyzer/11.6/solutions/anyid/anyid_csv.md b/docs/accessanalyzer/11.6/solutions/anyid/anyid_csv.md index 6cdf2cce94..25dec74474 100644 --- a/docs/accessanalyzer/11.6/solutions/anyid/anyid_csv.md +++ b/docs/accessanalyzer/11.6/solutions/anyid/anyid_csv.md @@ -52,11 +52,11 @@ Schedule the job as required. **Query Configuration** This job contains configurable queries. See the -[Configure the AnyID_CSV Query](#configure-the-anyidcsvquery) topic for additional information. +[Configure the AnyID_CSV Query](#configure-the-anyid_csvquery) topic for additional information. **Analysis Configuration** -See the [Analysis Tasks for the AnyID_CSV Job](#analysis-tasks-for-the-anyidcsvjob) topic for +See the [Analysis Tasks for the AnyID_CSV Job](#analysis-tasks-for-the-anyid_csvjob) topic for additional information. **Workflow** @@ -78,7 +78,7 @@ The AnyID_CSV query uses the PowerShell Data Collector. The query is: - CSV Import – Imports identities and attributes from a CSV file. See the - [Configure the AnyID_CSV Query](#configure-the-anyidcsvquery) topic for additional information. + [Configure the AnyID_CSV Query](#configure-the-anyid_csvquery) topic for additional information. ### Configure the AnyID_CSV Query diff --git a/docs/accessanalyzer/11.6/solutions/anyid/anyid_epicclarity.md b/docs/accessanalyzer/11.6/solutions/anyid/anyid_epicclarity.md index 08b9915b75..68ca8795b2 100644 --- a/docs/accessanalyzer/11.6/solutions/anyid/anyid_epicclarity.md +++ b/docs/accessanalyzer/11.6/solutions/anyid/anyid_epicclarity.md @@ -22,7 +22,7 @@ The following are recommended configurations for the AnyID_EpicClarity job: The AnyID_EpicClarity job requires a CSV file with a filepath configured in the job's query to collect data. See the -[Configure the AnyID_EpicClarity Queries](#configure-the-anyidepicclarity-queries) topic for +[Configure the AnyID_EpicClarity Queries](#configure-the-anyid_epicclarity-queries) topic for additional information. **Targeted Host** @@ -50,7 +50,7 @@ This job should be run based on the frequency you want for Sensitive Data Scans. **Query Configuration** This job contains configurable queries. See the Configure the -[Configure the AnyID_EpicClarity Queries](#configure-the-anyidepicclarity-queries) topic for +[Configure the AnyID_EpicClarity Queries](#configure-the-anyid_epicclarity-queries) topic for additional information. **Analysis Configuration** @@ -79,7 +79,7 @@ The queries are: - Epic Clarity Identity IDs – Imports Epic Clarity subject profile information on identity IDs The above queries have configurable parameters. See the -[Configure the AnyID_EpicClarity Queries](#configure-the-anyidepicclarity-queries) topic for +[Configure the AnyID_EpicClarity Queries](#configure-the-anyid_epicclarity-queries) topic for additional information. ### Configure the AnyID_EpicClarity Queries diff --git a/docs/accessanalyzer/11.6/solutions/anyid/anyid_paycom.md b/docs/accessanalyzer/11.6/solutions/anyid/anyid_paycom.md index 7aea46735b..bb2ace90b8 100644 --- a/docs/accessanalyzer/11.6/solutions/anyid/anyid_paycom.md +++ b/docs/accessanalyzer/11.6/solutions/anyid/anyid_paycom.md @@ -48,7 +48,7 @@ This job should be run based on the frequency you want for Sensitive Data Scans. **Query Configuration** This job contains configurable queries. See the -[Configure the AnyID_Paycom Job](#configure-the-anyidpaycom-job) topic for additional information. +[Configure the AnyID_Paycom Job](#configure-the-anyid_paycom-job) topic for additional information. **Analysis Configuration** @@ -73,7 +73,7 @@ The AnyID_Paycom job uses the PowerShell Data Collector for the query. The queries are: - Paycom CSV Import – Imports a CSV file with information from Paycom. This query has configurable - parameters. See the [Configure the AnyID_Paycom Job](#configure-the-anyidpaycom-job) topic for + parameters. See the [Configure the AnyID_Paycom Job](#configure-the-anyid_paycom-job) topic for additional information. ### Configure the AnyID_Paycom Job diff --git a/docs/accessanalyzer/11.6/solutions/anyid/anyid_salesforce.md b/docs/accessanalyzer/11.6/solutions/anyid/anyid_salesforce.md index 17dd0cdc8b..fa68909f44 100644 --- a/docs/accessanalyzer/11.6/solutions/anyid/anyid_salesforce.md +++ b/docs/accessanalyzer/11.6/solutions/anyid/anyid_salesforce.md @@ -57,7 +57,7 @@ Schedule the job as required. **Query Configuration** This job contains configurable queries. See the -[Configure the AnyID_Salesforce Query](#configure-the-anyidsalesforce-query) topic for additional +[Configure the AnyID_Salesforce Query](#configure-the-anyid_salesforce-query) topic for additional information. **Analysis Configuration** @@ -83,7 +83,7 @@ The AnyID_Salesforce job uses the PowerShell Data Collector for the query. The query is: - PS Salesforce Import – Imports Salesforce information for analysis. This query has configurable - parameters. See the [Configure the AnyID_Salesforce Query](#configure-the-anyidsalesforce-query) + parameters. See the [Configure the AnyID_Salesforce Query](#configure-the-anyid_salesforce-query) topic for additional information. ### Configure the AnyID_Salesforce Query diff --git a/docs/accessanalyzer/11.6/solutions/aws/groups/aws_stalegroups.md b/docs/accessanalyzer/11.6/solutions/aws/groups/aws_stalegroups.md index d5c7137089..1bc8790c36 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/groups/aws_stalegroups.md +++ b/docs/accessanalyzer/11.6/solutions/aws/groups/aws_stalegroups.md @@ -21,7 +21,7 @@ The AWS_StaleGroups job has the following configurable parameter: - Days without log in to consider an account stale See the -[Customizable Analysis Tasks for the AWS_StaleGroups Job](#customizable-analysis-tasks-for-the-awsstalegroups-job) +[Customizable Analysis Tasks for the AWS_StaleGroups Job](#customizable-analysis-tasks-for-the-aws_stalegroups-job) topic for additional information. ## Analysis Tasks for the AWS_StaleGroups Job @@ -44,7 +44,7 @@ The following analysis tasks are selected by default: - The number of days without log in to consider an account stale can be customized. By default it is set to 60. See the - [Customizable Analysis Tasks for the AWS_StaleGroups Job](#customizable-analysis-tasks-for-the-awsstalegroups-job) + [Customizable Analysis Tasks for the AWS_StaleGroups Job](#customizable-analysis-tasks-for-the-aws_stalegroups-job) topic for additional information. - Stale Group Summary – Summarizes statistics for stale groups. Creates the AWS_StaleGroup_Summary diff --git a/docs/accessanalyzer/11.6/solutions/aws/policies/aws_unusedmanagedpolicies.md b/docs/accessanalyzer/11.6/solutions/aws/policies/aws_unusedmanagedpolicies.md index 335d036dab..541dd2877b 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/policies/aws_unusedmanagedpolicies.md +++ b/docs/accessanalyzer/11.6/solutions/aws/policies/aws_unusedmanagedpolicies.md @@ -22,7 +22,7 @@ The AWS_UnusedManagedPolicies job has the following configurable parameter: - True or False value to include policies managed by AWS See the -[Customizable Analysis Tasks for the AWS_UnusedManagedPolicies Job](#customizable-analysis-tasks-for-the-awsunusedmanagedpolicies-job) +[Customizable Analysis Tasks for the AWS_UnusedManagedPolicies Job](#customizable-analysis-tasks-for-the-aws_unusedmanagedpolicies-job) topic for additional information. ## Analysis Tasks for the AWS_UnusedManagedPolicies Job @@ -44,7 +44,7 @@ The following analysis tasks are selected by default: AWS_UnusedPolicies_Details table accessible under the job’s Results node. - Optionally, AWS managed policies can be included by setting the parameter to True. See the - [Customizable Analysis Tasks for the AWS_UnusedManagedPolicies Job](#customizable-analysis-tasks-for-the-awsunusedmanagedpolicies-job) + [Customizable Analysis Tasks for the AWS_UnusedManagedPolicies Job](#customizable-analysis-tasks-for-the-aws_unusedmanagedpolicies-job) topic for additional information. - Unused Managed Policy Summary – Summary by AWS Organization of unused managed policies. Creates diff --git a/docs/accessanalyzer/11.6/solutions/aws/roles/aws_staleroles.md b/docs/accessanalyzer/11.6/solutions/aws/roles/aws_staleroles.md index 41ca15a779..935bb345b5 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/roles/aws_staleroles.md +++ b/docs/accessanalyzer/11.6/solutions/aws/roles/aws_staleroles.md @@ -22,7 +22,7 @@ The AWS_StaleRoles job has the following configurable parameter: - Days without log in to consider an account stale See the -[Customizable Analysis Tasks for the AWS_StaleRoles Job](#customizable-analysis-tasks-for-the-awsstaleroles-job) +[Customizable Analysis Tasks for the AWS_StaleRoles Job](#customizable-analysis-tasks-for-the-aws_staleroles-job) topic for additional information. ## Analysis Tasks for the AWS_StaleRoles Job @@ -45,7 +45,7 @@ The following analysis tasks are selected by default: - The number of days without log in to consider an account stale can be customized. By default it is set to 60. See the - [Customizable Analysis Tasks for the AWS_StaleRoles Job](#customizable-analysis-tasks-for-the-awsstaleroles-job) + [Customizable Analysis Tasks for the AWS_StaleRoles Job](#customizable-analysis-tasks-for-the-aws_staleroles-job) topic for additional information. - Stale Role Summary – Summarizes stale roles by AWS Account. Creates the AWS_StaleRole_Summary diff --git a/docs/accessanalyzer/11.6/solutions/aws/users/aws_staleusers.md b/docs/accessanalyzer/11.6/solutions/aws/users/aws_staleusers.md index e7bf2514f4..4e52c163e8 100644 --- a/docs/accessanalyzer/11.6/solutions/aws/users/aws_staleusers.md +++ b/docs/accessanalyzer/11.6/solutions/aws/users/aws_staleusers.md @@ -21,7 +21,7 @@ The AWS_StaleUsers job has the following configurable parameter: - Number of days before considering a user stale See the -[Customizable Analysis Tasks for the AWS_StaleUsers Job](#customizable-analysis-tasks-for-the-awsstaleusers-job) +[Customizable Analysis Tasks for the AWS_StaleUsers Job](#customizable-analysis-tasks-for-the-aws_staleusers-job) topic for additional information. ## Analysis Tasks for the AWS_StaleUsers Job @@ -43,7 +43,7 @@ The following analysis tasks are selected by default: Creates the AWS_StaleUser_Details table accessible under the job’s Results node. - The number of days can be customized from the default value of 60. See the - [Customizable Analysis Tasks for the AWS_StaleUsers Job](#customizable-analysis-tasks-for-the-awsstaleusers-job) + [Customizable Analysis Tasks for the AWS_StaleUsers Job](#customizable-analysis-tasks-for-the-aws_staleusers-job) topic for additional information. - Stale User Summary – Summarizes stale users in AWS. Creates the AWS_StaleUser_Summary table diff --git a/docs/accessanalyzer/11.6/solutions/box/collection/1-box_access_scans.md b/docs/accessanalyzer/11.6/solutions/box/collection/1-box_access_scans.md index 413bf3179e..570929b948 100644 --- a/docs/accessanalyzer/11.6/solutions/box/collection/1-box_access_scans.md +++ b/docs/accessanalyzer/11.6/solutions/box/collection/1-box_access_scans.md @@ -35,7 +35,7 @@ configurations are commonly customized: - Not scoped -See the [Configure the 1-Box_Access Scans Job](#configure-the-1-boxaccess-scans-job) section for +See the [Configure the 1-Box_Access Scans Job](#configure-the-1-box_access-scans-job) section for instructions. ### Configure the 1-Box_Access Scans Job diff --git a/docs/accessanalyzer/11.6/solutions/box/collection/1-box_activity_scans.md b/docs/accessanalyzer/11.6/solutions/box/collection/1-box_activity_scans.md index a248622939..6cbb24091c 100644 --- a/docs/accessanalyzer/11.6/solutions/box/collection/1-box_activity_scans.md +++ b/docs/accessanalyzer/11.6/solutions/box/collection/1-box_activity_scans.md @@ -34,7 +34,7 @@ commonly customized: - Not scoped -See the [Configure the 1-Box_Activity Scans Job](#configure-the-1-boxactivity-scans-job) section +See the [Configure the 1-Box_Activity Scans Job](#configure-the-1-box_activity-scans-job) section for instructions. ### Configure the 1-Box_Activity Scans Job diff --git a/docs/accessanalyzer/11.6/solutions/box/content/box_filemetrics.md b/docs/accessanalyzer/11.6/solutions/box/content/box_filemetrics.md index 06f38ab9b9..7fb4f55c99 100644 --- a/docs/accessanalyzer/11.6/solutions/box/content/box_filemetrics.md +++ b/docs/accessanalyzer/11.6/solutions/box/content/box_filemetrics.md @@ -32,7 +32,7 @@ The following analysis tasks are selected by default: Results node - Set to consider content stale after 30 days which is the @STALETHRESHOLD parameter value - See the - [Customize Analysis Tasks for the Box_FileMetrics Job](#customize-analysis-tasks-for-the-boxfilemetrics-job) + [Customize Analysis Tasks for the Box_FileMetrics Job](#customize-analysis-tasks-for-the-box_filemetrics-job) topic for additional information. - File Count by User – Creates the Box_FileMetrics_UserFileCount table accessible under the job’s Results node diff --git a/docs/accessanalyzer/11.6/solutions/box/content/box_foldermetrics.md b/docs/accessanalyzer/11.6/solutions/box/content/box_foldermetrics.md index 79fec47730..22137ef40e 100644 --- a/docs/accessanalyzer/11.6/solutions/box/content/box_foldermetrics.md +++ b/docs/accessanalyzer/11.6/solutions/box/content/box_foldermetrics.md @@ -34,7 +34,7 @@ The following analysis tasks are selected by default: Results node - Set to consider content stale after 30 days which is the @STALETHRESHOLD parameter value - See the - [Customizable Analysis Tasks for the Box_FolderMetrics Job](#customizable-analysis-tasks-for-the-boxfoldermetrics-job) + [Customizable Analysis Tasks for the Box_FolderMetrics Job](#customizable-analysis-tasks-for-the-box_foldermetrics-job) topic for additional information. - Largest Folders – Creates the Box_FolderMetrics_Largest table accessible under the job’s Results node diff --git a/docs/accessanalyzer/11.6/solutions/dropbox/dropbox_content.md b/docs/accessanalyzer/11.6/solutions/dropbox/dropbox_content.md index dfe1c37854..de48ca2ce5 100644 --- a/docs/accessanalyzer/11.6/solutions/dropbox/dropbox_content.md +++ b/docs/accessanalyzer/11.6/solutions/dropbox/dropbox_content.md @@ -26,7 +26,7 @@ The Dropbox_Content job has the following customizable parameter: - Days since File Modification before a file is considered stale See the -[Customizable Analysis Tasks for the Dropbox_Content Job](#customizable-analysis-tasks-for-the-dropboxcontent-job) +[Customizable Analysis Tasks for the Dropbox_Content Job](#customizable-analysis-tasks-for-the-dropbox_content-job) topic for additional information. ## Analysis Tasks for the Dropbox_Content Job @@ -48,7 +48,7 @@ preconfigured for this job. - By default, a stale file has not been modified in the past 365 days. You can modify this analysis task to edit this number of days. See the - [Customizable Analysis Tasks for the Dropbox_Content Job](#customizable-analysis-tasks-for-the-dropboxcontent-job) + [Customizable Analysis Tasks for the Dropbox_Content Job](#customizable-analysis-tasks-for-the-dropbox_content-job) topic for additional information. - Creates an interim processing table in the database for use by downstream analysis and report generation diff --git a/docs/accessanalyzer/11.6/solutions/entraidinventory/1-aad_scan.md b/docs/accessanalyzer/11.6/solutions/entraidinventory/1-aad_scan.md index 7327ea3d1f..1b23b443e7 100644 --- a/docs/accessanalyzer/11.6/solutions/entraidinventory/1-aad_scan.md +++ b/docs/accessanalyzer/11.6/solutions/entraidinventory/1-aad_scan.md @@ -18,7 +18,7 @@ The 1-AAD_Scan job uses the AzureADInventory Data Collector for the following qu - AAD Inventory – Targets Microsoft Entra tenants to collect inventory data for user group objects - _(Optional)_ This query can be modified to specify scan options and to collect custom - attributes. See the [Configure the 1-AAD_Scan Query](#configure-the-1-aadscan-query) topic + attributes. See the [Configure the 1-AAD_Scan Query](#configure-the-1-aad_scan-query) topic for additional information. ### Configure the 1-AAD_Scan Query diff --git a/docs/accessanalyzer/11.6/solutions/entraidinventory/2-aad_exceptions.md b/docs/accessanalyzer/11.6/solutions/entraidinventory/2-aad_exceptions.md index 176f3708b8..c9be8394e1 100644 --- a/docs/accessanalyzer/11.6/solutions/entraidinventory/2-aad_exceptions.md +++ b/docs/accessanalyzer/11.6/solutions/entraidinventory/2-aad_exceptions.md @@ -79,7 +79,7 @@ The default values for parameters that can be customized are: | Stale Membership | @STALE_THRESHOLD | 10 | A group where 10% of its effective members are stale users | See the -[Configure the Analysis Tasks for the 2-AAD_Exceptions Job](#configure-the-analysis-tasks-for-the-2-aadexceptions-job) +[Configure the Analysis Tasks for the 2-AAD_Exceptions Job](#configure-the-analysis-tasks-for-the-2-aad_exceptions-job) section for instructions to modify parameters. See the [AzureADInventory Exception Types Translated](/docs/accessanalyzer/11.6/admin/datacollector/azureadinventory/standardtables.md#azureadinventory-exception-types-translated) topic for an explanation of Exception Types. diff --git a/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow.md b/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow.md index da3218e799..2714a9f408 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow.md @@ -23,7 +23,7 @@ The EX_Mailflow job has the following configurable parameter: - Number of months to keep -See the [Analysis Tasks for the EX_Mailflow Job](#analysis-tasks-for-the-exmailflow-job) topic for +See the [Analysis Tasks for the EX_Mailflow Job](#analysis-tasks-for-the-ex_mailflow-job) topic for additional information. ## Queries for the EX_Mailflow Job diff --git a/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow_domain.md b/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow_domain.md index a5efe5bfcf..92d123b1ec 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow_domain.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow_domain.md @@ -21,7 +21,7 @@ The EX_Mailflow_Domain job has the following configurable parameter: - Number of days to show in tables and reports See the -[Analysis Tasks for the EX_Mailflow_Domain Job](#analysis-tasks-for-the-exmailflowdomain-job) +[Analysis Tasks for the EX_Mailflow_Domain Job](#analysis-tasks-for-the-ex_mailflow_domain-job) topic for additional information. ## Analysis Tasks for the EX_Mailflow_Domain Job diff --git a/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow_mailbox.md b/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow_mailbox.md index b306847eb1..eca57a6ecc 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow_mailbox.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow_mailbox.md @@ -22,7 +22,7 @@ The EX_Mailflow_Mailbox job has the following configurable parameter: Count** and **User Mailboxes by Message Size** analysis tasks. The default is **30** days. See the -[Analysis Tasks for the EX_Mailflow_Mailbox Job](#analysis-tasks-for-the-exmailflowmailbox-job) +[Analysis Tasks for the EX_Mailflow_Mailbox Job](#analysis-tasks-for-the-ex_mailflow_mailbox-job) topic for additional information. ## Analysis Tasks for the EX_Mailflow_Mailbox Job diff --git a/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow_orgoverview.md b/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow_orgoverview.md index d123253e6b..5a1f725481 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow_orgoverview.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/online/mailflow/ex_mailflow_orgoverview.md @@ -21,7 +21,7 @@ The EX_Mailflow_OrgOverview job has the following configurable parameter: - Number of days of data to display See the -[Analysis Tasks for the EX_Mailflow_OrgOverview Job](#analysis-tasks-for-the-exmailfloworgoverview-job) +[Analysis Tasks for the EX_Mailflow_OrgOverview Job](#analysis-tasks-for-the-ex_mailflow_orgoverview-job) topic for additional information. ## Analysis Tasks for the EX_Mailflow_OrgOverview Job diff --git a/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/ownership/pf_folderownership.md b/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/ownership/pf_folderownership.md index 72e7e4e6b7..9c0d6141f6 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/ownership/pf_folderownership.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/publicfolders/ownership/pf_folderownership.md @@ -28,7 +28,7 @@ The following queries are included in the PF_FolderOwnership job: - By default set to search all public folders. It can be scoped. - See the - [Scope the ExchangePublicFolder Data Collector for the PF_FolderOwnership Job](#scope-the-exchangepublicfolder-data-collector-for-the-pffolderownership-job) + [Scope the ExchangePublicFolder Data Collector for the PF_FolderOwnership Job](#scope-the-exchangepublicfolder-data-collector-for-the-pf_folderownership-job) topic for additional information - Assigned Ownership – Collects assigned owners @@ -36,7 +36,7 @@ The following queries are included in the PF_FolderOwnership job: - By default set to search all public folders. It can be scoped. - Probable Owner Calculation can be modified - See the - [Scope the ExchangePublicFolder Data Collector for the PF_FolderOwnership Job](#scope-the-exchangepublicfolder-data-collector-for-the-pffolderownership-job) + [Scope the ExchangePublicFolder Data Collector for the PF_FolderOwnership Job](#scope-the-exchangepublicfolder-data-collector-for-the-pf_folderownership-job) topic for additional information ### Scope the ExchangePublicFolder Data Collector for the PF_FolderOwnership Job diff --git a/docs/accessanalyzer/11.6/solutions/exchange/sensitivedata/collection/ex_mailbox_sdd.md b/docs/accessanalyzer/11.6/solutions/exchange/sensitivedata/collection/ex_mailbox_sdd.md index 9bc0d496bf..1580603df0 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/sensitivedata/collection/ex_mailbox_sdd.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/sensitivedata/collection/ex_mailbox_sdd.md @@ -42,7 +42,7 @@ The following query is included in the EX_Mailbox_SDD job: - US SSN - See the - [Configure the EWSMailbox Data Collector for the EX_Mailbox_SDD Job](#configure-the-ewsmailbox-data-collector-for-the-exmailboxsdd-job) + [Configure the EWSMailbox Data Collector for the EX_Mailbox_SDD Job](#configure-the-ewsmailbox-data-collector-for-the-ex_mailbox_sdd-job) topic for additional information ### Configure the EWSMailbox Data Collector for the EX_Mailbox_SDD Job diff --git a/docs/accessanalyzer/11.6/solutions/exchange/sensitivedata/collection/ex_publicfolder_sdd.md b/docs/accessanalyzer/11.6/solutions/exchange/sensitivedata/collection/ex_publicfolder_sdd.md index 9d62854618..e9711d45a0 100644 --- a/docs/accessanalyzer/11.6/solutions/exchange/sensitivedata/collection/ex_publicfolder_sdd.md +++ b/docs/accessanalyzer/11.6/solutions/exchange/sensitivedata/collection/ex_publicfolder_sdd.md @@ -42,7 +42,7 @@ The following query is included in the EX_PublicFolder_SDD job: - Tax Forms - US SSN - - See the [Configure the EX_PublicFolder_SDD Query](#configure-the-expublicfoldersdd-query) + - See the [Configure the EX_PublicFolder_SDD Query](#configure-the-ex_publicfolder_sdd-query) topic for additional information ### Configure the EX_PublicFolder_SDD Query diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/delete/fs_deletefiles.md b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/delete/fs_deletefiles.md index 62cd3008a0..c53c5bd8f4 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/delete/fs_deletefiles.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/delete/fs_deletefiles.md @@ -21,7 +21,7 @@ The FS_DeleteFiles job has the following configurable parameter: - Number of days without access after which a file is a deletion candidate See the -[Customizable Analysis Tasks for the FS_DeleteFiles Job](#customizable-analysis-tasks-for-the-fsdeletefiles-job) +[Customizable Analysis Tasks for the FS_DeleteFiles Job](#customizable-analysis-tasks-for-the-fs_deletefiles-job) topic for additional information. ## Analysis Tasks for the FS_DeleteFiles Job diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/fs_cleanupassessment.md b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/fs_cleanupassessment.md index 936f1fd7f3..2f90c40deb 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/fs_cleanupassessment.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/fs_cleanupassessment.md @@ -49,7 +49,7 @@ The FS_CleanupAssessment job has the following configurable parameters: - Upper bound for files to be included in the FileDetails table (by LastModfied, in days) See the -[Customizable Analysis Tasks for the FS_CleanupAssessment Job](#customizable-analysis-tasks-for-the-fscleanupassessment-job) +[Customizable Analysis Tasks for the FS_CleanupAssessment Job](#customizable-analysis-tasks-for-the-fs_cleanupassessment-job) topic for additional information. ## Analysis Tasks for the FS_CleanupAssessment Job @@ -73,14 +73,14 @@ The following analysis tasks are selected by default: - See the [Include Metadata Tag Information](#include-metadata-tag-information) topic for instructions on how to include metadata tag information in this table - Has 3 configurable parameters. See the - [Customizable Analysis Tasks for the FS_CleanupAssessment Job](#customizable-analysis-tasks-for-the-fscleanupassessment-job) + [Customizable Analysis Tasks for the FS_CleanupAssessment Job](#customizable-analysis-tasks-for-the-fs_cleanupassessment-job) topic for additional information. - Create file-level details table – Creates the SA_FS_CleanupAssessment_FileDetails table accessible under the job’s Results node - Has 2 configurable parameters. See the - [Customizable Analysis Tasks for the FS_CleanupAssessment Job](#customizable-analysis-tasks-for-the-fscleanupassessment-job) + [Customizable Analysis Tasks for the FS_CleanupAssessment Job](#customizable-analysis-tasks-for-the-fs_cleanupassessment-job) topic for additional information. - Summarize share-level information – Creates the SA_FS_CleanupAssessment_ShareDetails table diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/notify/fs_notifyowners.md b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/notify/fs_notifyowners.md index 3c6782b449..93518b6132 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/notify/fs_notifyowners.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/cleanup/notify/fs_notifyowners.md @@ -29,7 +29,7 @@ The following action task is deselected by default. Before running the FS_NotifyOwners job, select the **Notify Owners** task and configure the properties for the SendMail action module. See the -[Configure the FS_NotifyOwners Action](#configure-the-fsnotifyowners-action) topic for additional +[Configure the FS_NotifyOwners Action](#configure-the-fs_notifyowners-action) topic for additional information. ### Configure the FS_NotifyOwners Action diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/fs_brokeninheritance.md b/docs/accessanalyzer/11.6/solutions/filesystem/fs_brokeninheritance.md index 3f26ea1d1a..6680223e9b 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/fs_brokeninheritance.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/fs_brokeninheritance.md @@ -29,7 +29,7 @@ The FS_BrokenInheritance job has the following configurable parameter: - 2 – Analyze all resources regardless of permission changes between parent and child See the -[Analysis Tasks for the FS_BrokenInheritance Job](#analysis-tasks-for-the-fsbrokeninheritance-job) +[Analysis Tasks for the FS_BrokenInheritance Job](#analysis-tasks-for-the-fs_brokeninheritance-job) topic for additional information. ## Analysis Tasks for the FS_BrokenInheritance Job diff --git a/docs/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroupaicimport.md b/docs/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroupaicimport.md index 123385b297..fd33e9c308 100644 --- a/docs/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroupaicimport.md +++ b/docs/accessanalyzer/11.6/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroupaicimport.md @@ -50,7 +50,7 @@ Not supported **Step 2 –** Run the FS_ResourceBasedGroupsAICImport job. -- See the [Run the FS_ResourceBasedGroupsAICImportJob](#run-the-fsresourcebasedgroupsaicimportjob) +- See the [Run the FS_ResourceBasedGroupsAICImportJob](#run-the-fs_resourcebasedgroupsaicimportjob) topic for additional information **Step 3 –** Review the newly-created resource based groups in the AIC. diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/collection/7-spaa_exceptions.md b/docs/accessanalyzer/11.6/solutions/sharepoint/collection/7-spaa_exceptions.md index 9730d520b1..9ed86e83d8 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/collection/7-spaa_exceptions.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/collection/7-spaa_exceptions.md @@ -27,7 +27,7 @@ The 7-SPAA_Exceptions page has the following configurable parameters: See the -[Customizable Analysis Tasks for the 7-SPAA_Exceptions Job](#customizable-analysis-tasks-for-the-7-spaaexceptions-job) +[Customizable Analysis Tasks for the 7-SPAA_Exceptions Job](#customizable-analysis-tasks-for-the-7-spaa_exceptions-job) for additional information. ## Analysis Tasks 7-SPAA_Exceptions Job diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/content/sp_stalefiles.md b/docs/accessanalyzer/11.6/solutions/sharepoint/content/sp_stalefiles.md index 71a2573588..bc7311f7b1 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/content/sp_stalefiles.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/content/sp_stalefiles.md @@ -24,7 +24,7 @@ The SP_StaleFiles page has the following configurable parameters: - Days since last modification to be considered stale See the -[Customizable Analysis Tasks for the SP_StaleFiles Job](#customizable-analysis-tasks-for-the-spstalefiles-job) +[Customizable Analysis Tasks for the SP_StaleFiles Job](#customizable-analysis-tasks-for-the-sp_stalefiles-job) for additional information. ## Analysis Tasks for the SP_StaleFiles Job @@ -46,7 +46,7 @@ The default analysis task is: node - This analysis task contains a configurable parameter: `@stale`. See the - [Customizable Analysis Tasks for the SP_StaleFiles Job](#customizable-analysis-tasks-for-the-spstalefiles-job) + [Customizable Analysis Tasks for the SP_StaleFiles Job](#customizable-analysis-tasks-for-the-sp_stalefiles-job) topic for additional information. In addition to the table created by the analysis task which displays the stale file resources, the diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/effectiveaccessaudits/sp_trusteeaccess.md b/docs/accessanalyzer/11.6/solutions/sharepoint/effectiveaccessaudits/sp_trusteeaccess.md index 2fc92d5cea..b2df392e00 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/effectiveaccessaudits/sp_trusteeaccess.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/effectiveaccessaudits/sp_trusteeaccess.md @@ -14,7 +14,7 @@ at once. :::note Trustees can be specified in the `UserScoping.csv` file for the SP_TrusteeAccess Job. See the -[Configure CSV File for the Query for the SP_TrusteeAccess Job](#configure-csv-file-for-the-query-for-the-sptrusteeaccess-job) +[Configure CSV File for the Query for the SP_TrusteeAccess Job](#configure-csv-file-for-the-query-for-the-sp_trusteeaccess-job) topic for additional information. ::: @@ -32,7 +32,7 @@ The SP_TrusteeAccess Job uses the TextSearch Data Collector for the following qu The default query is: - Scoping – Modifies the CSV in the Job Directory. See the - [Configure CSV File for the Query for the SP_TrusteeAccess Job](#configure-csv-file-for-the-query-for-the-sptrusteeaccess-job) + [Configure CSV File for the Query for the SP_TrusteeAccess Job](#configure-csv-file-for-the-query-for-the-sp_trusteeaccess-job) topic for additional information. ### Configure CSV File for the Query for the SP_TrusteeAccess Job diff --git a/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_staleteamsites.md b/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_staleteamsites.md index 2d4d064c62..b23be2f4ab 100644 --- a/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_staleteamsites.md +++ b/docs/accessanalyzer/11.6/solutions/sharepoint/m365/sp_staleteamsites.md @@ -21,7 +21,7 @@ The SP_StaleTeamSites page has the following configurable parameters: - Desired Number of Days Since Last Activity To Determine Staleness See the -[Customizable Analysis Tasks for the SP_StaleTeamSites Job](#customizable-analysis-tasks-for-the-spstaleteamsites-job) +[Customizable Analysis Tasks for the SP_StaleTeamSites Job](#customizable-analysis-tasks-for-the-sp_staleteamsites-job) for additional information. ## Analysis Tasks for the SP_StaleTeamSites Job @@ -37,7 +37,7 @@ The default analysis task is: - This task contains a configurable parameter to set the number of days a Team has not had activity for before it's considered stale. See the - [Customizable Analysis Tasks for the SP_StaleTeamSites Job](#customizable-analysis-tasks-for-the-spstaleteamsites-job) + [Customizable Analysis Tasks for the SP_StaleTeamSites Job](#customizable-analysis-tasks-for-the-sp_staleteamsites-job) topic for additional information. In addition to the table created by the analysis task, the SP_StaleTeamSites Job produces the diff --git a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/workflows.md b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/workflows.md index e224e70d93..4d88448650 100644 --- a/docs/accessanalyzer/12.0/admin/datacollector/fsaa/workflows.md +++ b/docs/accessanalyzer/12.0/admin/datacollector/fsaa/workflows.md @@ -162,7 +162,7 @@ Applying these analysis tasks deletes collected data. Configure and run the analysis tasks: **Step 1 –** Before job execution, modify the analysis tasks you want using the -[Customizable Analysis Parameters for FS_SDD_DELETE Job](#customizable-analysis-parameters-for-fssdddelete-job) +[Customizable Analysis Parameters for FS_SDD_DELETE Job](#customizable-analysis-parameters-for-fs_sdd_delete-job) instructions. **Step 2 –** In the Analysis Selection Pane, check the type of analysis task that will be run. diff --git a/docs/accessanalyzer/12.0/admin/jobs/instantjobs/ad_passwordexpirationnotification.md b/docs/accessanalyzer/12.0/admin/jobs/instantjobs/ad_passwordexpirationnotification.md index e9f76e0da1..d7c4c666a3 100644 --- a/docs/accessanalyzer/12.0/admin/jobs/instantjobs/ad_passwordexpirationnotification.md +++ b/docs/accessanalyzer/12.0/admin/jobs/instantjobs/ad_passwordexpirationnotification.md @@ -44,7 +44,7 @@ The default analysis tasks are: - Contains a configurable parameter for the number of days until a password expires to be identified - See the - [Customizable Analysis Tasks for the AD_PasswordExpirationNotification Job](#customizable-analysis-tasks-for-the-adpasswordexpirationnotification-job) + [Customizable Analysis Tasks for the AD_PasswordExpirationNotification Job](#customizable-analysis-tasks-for-the-ad_passwordexpirationnotification-job) topic for additional information. - **2. Domain Summary** – Creates an interim processing table in the database for use by downstream analysis and report generation @@ -56,7 +56,7 @@ The default analysis tasks are: the job’s Results node - **5. Help Desk Notification** – Sends notification of users with passwords set to expire in X days - See the - [Notification Analysis Task in the AD_PasswordExpirationNotification Job](#notification-analysis-task-in-the-adpasswordexpirationnotification-job) + [Notification Analysis Task in the AD_PasswordExpirationNotification Job](#notification-analysis-task-in-the-ad_passwordexpirationnotification-job) topic for additional information. ## Action for the AD_PasswordExpirationNotification Job @@ -77,7 +77,7 @@ The default actions are: password expiration - Requires the Notification Actions license feature - See the - [Action Task in the AD_PasswordExpirationNotification Job](#action-task-in-the-adpasswordexpirationnotification-job) + [Action Task in the AD_PasswordExpirationNotification Job](#action-task-in-the-ad_passwordexpirationnotification-job) topic for additional information. In addition to the tables created by the analysis and action tasks, the diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/ad_activitycollection.md b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/ad_activitycollection.md index 2235b8c6c0..fe792054e7 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/activity/ad_activitycollection.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/activity/ad_activitycollection.md @@ -18,7 +18,7 @@ Access Analyzer can retrieve AD Activity data in two ways: - API Server connected to the archive logs This is configured in the query. See the -[Queries for the AD_ActivityCollection Job](#queries-for-the-adactivitycollection-job) topic for +[Queries for the AD_ActivityCollection Job](#queries-for-the-ad_activitycollection-job) topic for additional information. ## Parameter Configuration @@ -47,7 +47,7 @@ The AD_ActivityCollection page has the following configurable parameters: - Number of days to retain activity data in the AIC See the -[Customize Analysis Parameters for the AD_ActivityCollection Job](#customize-analysis-parameters-for-the-adactivitycollection-job) +[Customize Analysis Parameters for the AD_ActivityCollection Job](#customize-analysis-parameters-for-the-ad_activitycollection-job) topic for additional information. ## Queries for the AD_ActivityCollection Job diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/computers/ad_deprovisioncomputers.md b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/computers/ad_deprovisioncomputers.md index 0218713fdb..4dc9dc7662 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/computers/ad_deprovisioncomputers.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/computers/ad_deprovisioncomputers.md @@ -29,7 +29,7 @@ The AD_DeprovisionComputers page has the following configurable parameters: - Days in the Staging OU before Deleting Account See the -[Customizable Analysis Parameters for the AD_DeprovisionComputers Job](#customizable-analysis-parameters-for-the-addeprovisioncomputers-job) +[Customizable Analysis Parameters for the AD_DeprovisionComputers Job](#customizable-analysis-parameters-for-the-ad_deprovisioncomputers-job) topic for additional information. ## Analysis Tasks for the AD_DeprovisionComputers Job @@ -47,7 +47,7 @@ The default analysis tasks are: under the job’s Results node - This analysis task contains a configurable parameter: `@days_before_deleting`. See the - [Customizable Analysis Parameters for the AD_DeprovisionComputers Job](#customizable-analysis-parameters-for-the-addeprovisioncomputers-job) + [Customizable Analysis Parameters for the AD_DeprovisionComputers Job](#customizable-analysis-parameters-for-the-ad_deprovisioncomputers-job) topic for additional information. ### Customizable Analysis Parameters for the AD_DeprovisionComputers Job diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/computers/overview.md b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/computers/overview.md index 86dbba8092..85c06bd838 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/computers/overview.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/computers/overview.md @@ -25,7 +25,7 @@ The jobs in the 3.Computers Job Group are: - The .Active Directory Inventory Job Group needs to be successfully run - For the AD_DeprovisionComputers Job, the target OU needs to be manually set in the Move Computers Action Task before executing the actions. See the - [Action Tasks for the AD_DeprovisionComputers Job](ad_deprovisioncomputers.md#action-tasks-for-the-addeprovisioncomputers-job) + [Action Tasks for the AD_DeprovisionComputers Job](ad_deprovisioncomputers.md#action-tasks-for-the-ad_deprovisioncomputers-job) topic for additional information. - The AD_DeprovisionComputers Job needs to be run before running the AD_DeprovisionComputers_Status Job diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/deprovision/ad_deprovisiongroups.md b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/deprovision/ad_deprovisiongroups.md index 257356ac92..a11eac7da5 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/deprovision/ad_deprovisiongroups.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/deprovision/ad_deprovisiongroups.md @@ -32,7 +32,7 @@ The AD_DeprovisionGroups page has the following configurable parameters: - Days in the Staging OU before deletion See the -[Customizable Analysis Parameters for the AD_DeprovisionGroups Job](#customizable-analysis-parameters-for-the-addeprovisiongroups-job) +[Customizable Analysis Parameters for the AD_DeprovisionGroups Job](#customizable-analysis-parameters-for-the-ad_deprovisiongroups-job) topic for additional information. ## Analysis Tasks for the AD_DeprovisionGroups Job @@ -49,7 +49,7 @@ The default analysis tasks are: - Groups to Delete – Identifies groups in the Stale Groups OU that are ready to be deleted - This analysis task contains a configurable parameter: `@days_before_deleting`. See the - [Customizable Analysis Parameters for the AD_DeprovisionGroups Job](#customizable-analysis-parameters-for-the-addeprovisiongroups-job) + [Customizable Analysis Parameters for the AD_DeprovisionGroups Job](#customizable-analysis-parameters-for-the-ad_deprovisiongroups-job) topic for additional information. ### Customizable Analysis Parameters for the AD_DeprovisionGroups Job diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/overview.md b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/overview.md index 2bbb616580..8052ea3807 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/overview.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/groups/overview.md @@ -38,7 +38,7 @@ The jobs in the 1.Groups Job Group are: - The .Active Directory Inventory Job Group needs to be successfully run - For the AD_DeprovisionGroups Job, the target OU needs to be manually set in the Move Groups Action Task before executing the actions. See the - [Action Tasks for the AD_DepvisionGroups Job](deprovision/ad_deprovisiongroups.md#action-tasks-for-the-addepvisiongroups-job) + [Action Tasks for the AD_DepvisionGroups Job](deprovision/ad_deprovisiongroups.md#action-tasks-for-the-ad_depvisiongroups-job) topic for additional information. - The AD_DeprovisionGroups Job needs to be run before running the AD_DeprovisionGroups_Status Job diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/users/ad_deprovisionusers.md b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/users/ad_deprovisionusers.md index 5c668d8531..e5839b3a23 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/users/ad_deprovisionusers.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/users/ad_deprovisionusers.md @@ -33,7 +33,7 @@ The AD_DeprovisionUsers page has the following configurable parameters: - Days in the Stale Users OU before being deleted See the -[Customizable Analysis Parameters for the AD_DeprovisionUsers Job](#customizable-analysis-parameters-for-the-addeprovisionusers-job) +[Customizable Analysis Parameters for the AD_DeprovisionUsers Job](#customizable-analysis-parameters-for-the-ad_deprovisionusers-job) topic for additional information. ## Analysis Tasks for the AD_DeprovisionUsers Job @@ -50,7 +50,7 @@ The default analysis tasks are: deleted - This analysis task contains a configurable parameter: `@days_before_deleting`. See the - [Customizable Analysis Parameters for the AD_DeprovisionUsers Job](#customizable-analysis-parameters-for-the-addeprovisionusers-job) + [Customizable Analysis Parameters for the AD_DeprovisionUsers Job](#customizable-analysis-parameters-for-the-ad_deprovisionusers-job) topic for additional information. - Identify Group Membership – Identifies stale user membership to remove diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/users/overview.md b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/users/overview.md index 7f726aa891..ce31625905 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/users/overview.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/cleanup/users/overview.md @@ -24,7 +24,7 @@ The jobs in the 2.Users Job Group are: - The .Active Directory Inventory Job Group needs to be successfully run - For the AD_DeprovisionUsers Job, the target OU needs to be manually set in the Move Users Action Task before executing the actions. See the - [Action Tasks for the AD_DeprovisionUsers Job](ad_deprovisionusers.md#action-tasks-for-the-addeprovisionusers-job) + [Action Tasks for the AD_DeprovisionUsers Job](ad_deprovisionusers.md#action-tasks-for-the-ad_deprovisionusers-job) topic for additional information. - The AD_DeprovisionUsers Job needs to be run before running the AD_DeprovisionUsers_Status Job diff --git a/docs/accessanalyzer/12.0/solutions/activedirectory/computers/ad_stalecomputers.md b/docs/accessanalyzer/12.0/solutions/activedirectory/computers/ad_stalecomputers.md index ba42321829..c1f1536ee1 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectory/computers/ad_stalecomputers.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectory/computers/ad_stalecomputers.md @@ -21,7 +21,7 @@ The AD_StaleComputers Job has the following configurable parameters: - Consider disabled accounts as stale See the -[Customizable Analysis Parameters for the AD_StaleComputers Job](#customizable-analysis-parameters-for-the-adstalecomputers-job) +[Customizable Analysis Parameters for the AD_StaleComputers Job](#customizable-analysis-parameters-for-the-ad_stalecomputers-job) topic for additional information. ## Analysis Tasks for the AD_StaleComputers Job diff --git a/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/1-ad_scan.md b/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/1-ad_scan.md index 01b09fe1be..5091ea4729 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/1-ad_scan.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/1-ad_scan.md @@ -21,7 +21,7 @@ The 1-AD_Scan Job uses the ADInventory Data Collector for the following query: objects - This query can be modified. See the - [Customize the 1-AD_Scan Query](#customize-the-1-adscan-query) topic for additional + [Customize the 1-AD_Scan Query](#customize-the-1-ad_scan-query) topic for additional information. ### Customize the 1-AD_Scan Query diff --git a/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/2-ad_changes.md b/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/2-ad_changes.md index 711a825ebf..375a7a63db 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/2-ad_changes.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/2-ad_changes.md @@ -13,7 +13,7 @@ Inventory Job Group. The 1-AD_Scan Job must have the Query Option to **Track changes into Change tracking tables** selected for the Analysis Tasks in the 2-AD_Changes Job to work. See Step 4 of the -[Customize the 1-AD_Scan Query](1-ad_scan.md#customize-the-1-adscan-query) topic for additional +[Customize the 1-AD_Scan Query](1-ad_scan.md#customize-the-1-ad_scan-query) topic for additional information. ## Analysis Tasks for the 2-AD_Changes Job @@ -113,7 +113,7 @@ following analysis tasks are deselected by default: Notification must have recipients configured for the analysis task. Optionally, the email subject and body can be modified. See the -[Notification Analysis Tasks for the 2-AD_Changes Job](#notification-analysis-tasks-for-the-2-adchanges-job) +[Notification Analysis Tasks for the 2-AD_Changes Job](#notification-analysis-tasks-for-the-2-ad_changes-job) topic for additional information. In addition to the tables and views created by the analysis tasks, the 2-AD_Changes Job produces the diff --git a/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/3-ad_exceptions.md b/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/3-ad_exceptions.md index ae2683f8c2..075d72ed03 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/3-ad_exceptions.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectoryinventory/3-ad_exceptions.md @@ -28,7 +28,7 @@ The 3-AD_Exceptions Job has the following configurable parameters: - List of administrative groups See the -[Customize Analysis Parameters for the 3-AD_Exceptions Job](#customize-analysis-parameters-for-the-3-adexceptions-job) +[Customize Analysis Parameters for the 3-AD_Exceptions Job](#customize-analysis-parameters-for-the-3-ad_exceptions-job) topic for additional information. ## Analysis Tasks for the 3-AD_Exceptions Job diff --git a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/ad_shadowaccess.md b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/ad_shadowaccess.md index 009a6b205e..7d1e3fd493 100644 --- a/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/ad_shadowaccess.md +++ b/docs/accessanalyzer/12.0/solutions/activedirectorypermissionsanalyzer/ad_shadowaccess.md @@ -55,7 +55,7 @@ The default analysis tasks are: Results node - This Analysis Task has configurable parameters. See the - [Configure the Analysis Tasks for the AD_ShadowAccess Job](#configure-the-analysis-tasks-for-the-adshadowaccess-job) + [Configure the Analysis Tasks for the AD_ShadowAccess Job](#configure-the-analysis-tasks-for-the-ad_shadowaccess-job) topic for additional information. - Shadow Access Paths Cleanup – Removes calculated rows that are no longer used @@ -70,7 +70,7 @@ the following pre-configured reports. See the -[Report Functions for the AD_ShadowAccess Job](#report-functions-for-the-adshadowaccess-job) topic +[Report Functions for the AD_ShadowAccess Job](#report-functions-for-the-ad_shadowaccess-job) topic for additional information. ### Customizable Analysis Tasks for the AD_ShadowAccess Job @@ -88,7 +88,7 @@ The default values for customizable parameters are: | @disabled | 0 | Set to 0 to ignore disabled users | | See the -[Configure the Analysis Tasks for the AD_ShadowAccess Job](#configure-the-analysis-tasks-for-the-adshadowaccess-job) +[Configure the Analysis Tasks for the AD_ShadowAccess Job](#configure-the-analysis-tasks-for-the-ad_shadowaccess-job) topic for additional information. ### Configure the Analysis Tasks for the AD_ShadowAccess Job diff --git a/docs/accessanalyzer/12.0/solutions/anyid/anyid_csv.md b/docs/accessanalyzer/12.0/solutions/anyid/anyid_csv.md index 6130aab858..76c4801bfb 100644 --- a/docs/accessanalyzer/12.0/solutions/anyid/anyid_csv.md +++ b/docs/accessanalyzer/12.0/solutions/anyid/anyid_csv.md @@ -50,11 +50,11 @@ Schedule the job as required. **Query Configuration** This job contains configurable queries. See the -[Configure the AnyID_CSV Query](#configure-the-anyidcsvquery) topic for additional information. +[Configure the AnyID_CSV Query](#configure-the-anyid_csvquery) topic for additional information. **Analysis Configuration** -See the [Analysis Tasks for the AnyID_CSV Job](#analysis-tasks-for-the-anyidcsvjob) topic for +See the [Analysis Tasks for the AnyID_CSV Job](#analysis-tasks-for-the-anyid_csvjob) topic for additional information. **Workflow** @@ -76,7 +76,7 @@ The AnyID_CSV query uses the PowerShell Data Collector. The query is: - CSV Import – Imports identities and attributes from a CSV file. See the - [Configure the AnyID_CSV Query](#configure-the-anyidcsvquery) topic for additional information. + [Configure the AnyID_CSV Query](#configure-the-anyid_csvquery) topic for additional information. ### Configure the AnyID_CSV Query diff --git a/docs/accessanalyzer/12.0/solutions/anyid/anyid_epicclarity.md b/docs/accessanalyzer/12.0/solutions/anyid/anyid_epicclarity.md index 61b63cb3a6..960cbadb2f 100644 --- a/docs/accessanalyzer/12.0/solutions/anyid/anyid_epicclarity.md +++ b/docs/accessanalyzer/12.0/solutions/anyid/anyid_epicclarity.md @@ -22,7 +22,7 @@ The following are recommended configurations for the AnyID_EpicClarity job: The AnyID_EpicClarity job requires a CSV file with a filepath configured in the job's query to collect data. See the -[Configure the AnyID_EpicClarity Queries](#configure-the-anyidepicclarity-queries) topic for +[Configure the AnyID_EpicClarity Queries](#configure-the-anyid_epicclarity-queries) topic for additional information. **Targeted Host** @@ -49,7 +49,7 @@ This job should be run based on the frequency you want for Sensitive Data Scans. **Query Configuration** This job contains configurable queries. See the Configure the -[Configure the AnyID_EpicClarity Queries](#configure-the-anyidepicclarity-queries) topic for +[Configure the AnyID_EpicClarity Queries](#configure-the-anyid_epicclarity-queries) topic for additional information. **Analysis Configuration** @@ -78,7 +78,7 @@ The queries are: - Epic Clarity Identity IDs – Imports Epic Clarity subject profile information on identity IDs The above queries have configurable parameters. See the -[Configure the AnyID_EpicClarity Queries](#configure-the-anyidepicclarity-queries) topic for +[Configure the AnyID_EpicClarity Queries](#configure-the-anyid_epicclarity-queries) topic for additional information. ### Configure the AnyID_EpicClarity Queries diff --git a/docs/accessanalyzer/12.0/solutions/anyid/anyid_paycom.md b/docs/accessanalyzer/12.0/solutions/anyid/anyid_paycom.md index aae887e58b..eb36da5408 100644 --- a/docs/accessanalyzer/12.0/solutions/anyid/anyid_paycom.md +++ b/docs/accessanalyzer/12.0/solutions/anyid/anyid_paycom.md @@ -47,7 +47,7 @@ This job should be run based on the frequency you want for Sensitive Data Scans. **Query Configuration** This job contains configurable queries. See the -[Configure the AnyID_Paycom Job](#configure-the-anyidpaycom-job) topic for additional information. +[Configure the AnyID_Paycom Job](#configure-the-anyid_paycom-job) topic for additional information. **Analysis Configuration** @@ -72,7 +72,7 @@ The AnyID_Paycom job uses the PowerShell Data Collector for the query. The queries are: - Paycom CSV Import – Imports a CSV file with information from Paycom. This query has configurable - parameters. See the [Configure the AnyID_Paycom Job](#configure-the-anyidpaycom-job) topic for + parameters. See the [Configure the AnyID_Paycom Job](#configure-the-anyid_paycom-job) topic for additional information. ### Configure the AnyID_Paycom Job diff --git a/docs/accessanalyzer/12.0/solutions/anyid/anyid_salesforce.md b/docs/accessanalyzer/12.0/solutions/anyid/anyid_salesforce.md index da59901759..3a9bf82097 100644 --- a/docs/accessanalyzer/12.0/solutions/anyid/anyid_salesforce.md +++ b/docs/accessanalyzer/12.0/solutions/anyid/anyid_salesforce.md @@ -56,7 +56,7 @@ Schedule the job as required. **Query Configuration** This job contains configurable queries. See the -[Configure the AnyID_Salesforce Query](#configure-the-anyidsalesforce-query) topic for additional +[Configure the AnyID_Salesforce Query](#configure-the-anyid_salesforce-query) topic for additional information. **Analysis Configuration** @@ -82,7 +82,7 @@ The AnyID_Salesforce job uses the PowerShell Data Collector for the query. The query is: - PS Salesforce Import – Imports Salesforce information for analysis. This query has configurable - parameters. See the [Configure the AnyID_Salesforce Query](#configure-the-anyidsalesforce-query) + parameters. See the [Configure the AnyID_Salesforce Query](#configure-the-anyid_salesforce-query) topic for additional information. ### Configure the AnyID_Salesforce Query diff --git a/docs/accessanalyzer/12.0/solutions/aws/groups/aws_stalegroups.md b/docs/accessanalyzer/12.0/solutions/aws/groups/aws_stalegroups.md index d879196ceb..312883107d 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/groups/aws_stalegroups.md +++ b/docs/accessanalyzer/12.0/solutions/aws/groups/aws_stalegroups.md @@ -21,7 +21,7 @@ The AWS_StaleGroups job has the following configurable parameter: - Days without log in to consider an account stale See the -[Customizable Analysis Tasks for the AWS_StaleGroups Job](#customizable-analysis-tasks-for-the-awsstalegroups-job) +[Customizable Analysis Tasks for the AWS_StaleGroups Job](#customizable-analysis-tasks-for-the-aws_stalegroups-job) topic for additional information. ## Analysis Tasks for the AWS_StaleGroups Job @@ -44,7 +44,7 @@ The following analysis tasks are selected by default: - The number of days without log in to consider an account stale can be customized. By default it is set to 60. See the - [Customizable Analysis Tasks for the AWS_StaleGroups Job](#customizable-analysis-tasks-for-the-awsstalegroups-job) + [Customizable Analysis Tasks for the AWS_StaleGroups Job](#customizable-analysis-tasks-for-the-aws_stalegroups-job) topic for additional information. - Stale Group Summary – Summarizes statistics for stale groups. Creates the AWS_StaleGroup_Summary diff --git a/docs/accessanalyzer/12.0/solutions/aws/policies/aws_unusedmanagedpolicies.md b/docs/accessanalyzer/12.0/solutions/aws/policies/aws_unusedmanagedpolicies.md index 6f7c5d3ddf..e1f12c6328 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/policies/aws_unusedmanagedpolicies.md +++ b/docs/accessanalyzer/12.0/solutions/aws/policies/aws_unusedmanagedpolicies.md @@ -22,7 +22,7 @@ The AWS_UnusedManagedPolicies job has the following configurable parameter: - True or False value to include policies managed by AWS See the -[Customizable Analysis Tasks for the AWS_UnusedManagedPolicies Job](#customizable-analysis-tasks-for-the-awsunusedmanagedpolicies-job) +[Customizable Analysis Tasks for the AWS_UnusedManagedPolicies Job](#customizable-analysis-tasks-for-the-aws_unusedmanagedpolicies-job) topic for additional information. ## Analysis Tasks for the AWS_UnusedManagedPolicies Job @@ -44,7 +44,7 @@ The following analysis tasks are selected by default: AWS_UnusedPolicies_Details table accessible under the job’s Results node. - Optionally, include AWS managed policies by setting the parameter to True. See the - [Customizable Analysis Tasks for the AWS_UnusedManagedPolicies Job](#customizable-analysis-tasks-for-the-awsunusedmanagedpolicies-job) + [Customizable Analysis Tasks for the AWS_UnusedManagedPolicies Job](#customizable-analysis-tasks-for-the-aws_unusedmanagedpolicies-job) topic for additional information. - Unused Managed Policy Summary – Summary by AWS Organization of unused managed policies. Creates diff --git a/docs/accessanalyzer/12.0/solutions/aws/roles/aws_staleroles.md b/docs/accessanalyzer/12.0/solutions/aws/roles/aws_staleroles.md index 596476fb71..1a63a69a1e 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/roles/aws_staleroles.md +++ b/docs/accessanalyzer/12.0/solutions/aws/roles/aws_staleroles.md @@ -22,7 +22,7 @@ The AWS_StaleRoles job has the following configurable parameter: - Days without log in to consider an account stale See the -[Customizable Analysis Tasks for the AWS_StaleRoles Job](#customizable-analysis-tasks-for-the-awsstaleroles-job) +[Customizable Analysis Tasks for the AWS_StaleRoles Job](#customizable-analysis-tasks-for-the-aws_staleroles-job) topic for additional information. ## Analysis Tasks for the AWS_StaleRoles Job @@ -45,7 +45,7 @@ The following analysis tasks are selected by default: - You can customize the number of days without a login to consider an account stale. By default it is set to 60. See the - [Customizable Analysis Tasks for the AWS_StaleRoles Job](#customizable-analysis-tasks-for-the-awsstaleroles-job) + [Customizable Analysis Tasks for the AWS_StaleRoles Job](#customizable-analysis-tasks-for-the-aws_staleroles-job) topic for additional information. - Stale Role Summary – Summarizes stale roles by AWS Account. Creates the AWS_StaleRole_Summary diff --git a/docs/accessanalyzer/12.0/solutions/aws/users/aws_staleusers.md b/docs/accessanalyzer/12.0/solutions/aws/users/aws_staleusers.md index c2be6b9ca3..9292328cd8 100644 --- a/docs/accessanalyzer/12.0/solutions/aws/users/aws_staleusers.md +++ b/docs/accessanalyzer/12.0/solutions/aws/users/aws_staleusers.md @@ -21,7 +21,7 @@ The AWS_StaleUsers job has the following configurable parameter: - Number of days before considering a user stale See the -[Customizable Analysis Tasks for the AWS_StaleUsers Job](#customizable-analysis-tasks-for-the-awsstaleusers-job) +[Customizable Analysis Tasks for the AWS_StaleUsers Job](#customizable-analysis-tasks-for-the-aws_staleusers-job) topic for additional information. ## Analysis Tasks for the AWS_StaleUsers Job @@ -43,7 +43,7 @@ The following analysis tasks are selected by default: Creates the AWS_StaleUser_Details table accessible under the job’s Results node. - You can customize the number of days from the default value of 60. See the - [Customizable Analysis Tasks for the AWS_StaleUsers Job](#customizable-analysis-tasks-for-the-awsstaleusers-job) + [Customizable Analysis Tasks for the AWS_StaleUsers Job](#customizable-analysis-tasks-for-the-aws_staleusers-job) topic for additional information. - Stale User Summary – Summarizes stale users in AWS. Creates the AWS_StaleUser_Summary table diff --git a/docs/accessanalyzer/12.0/solutions/box/collection/1-box_access_scans.md b/docs/accessanalyzer/12.0/solutions/box/collection/1-box_access_scans.md index 35fa8f5b90..ddb96dc6f0 100644 --- a/docs/accessanalyzer/12.0/solutions/box/collection/1-box_access_scans.md +++ b/docs/accessanalyzer/12.0/solutions/box/collection/1-box_access_scans.md @@ -28,7 +28,7 @@ the Scan query. Additionally, the following default configurations are commonly - Not scoped -See the [Configure the 1-Box_Access Scans Job](#configure-the-1-boxaccess-scans-job) section for +See the [Configure the 1-Box_Access Scans Job](#configure-the-1-box_access-scans-job) section for instructions. ### Configure the 1-Box_Access Scans Job diff --git a/docs/accessanalyzer/12.0/solutions/box/collection/1-box_activity_scans.md b/docs/accessanalyzer/12.0/solutions/box/collection/1-box_activity_scans.md index f70f7779b4..d932e8a9a2 100644 --- a/docs/accessanalyzer/12.0/solutions/box/collection/1-box_activity_scans.md +++ b/docs/accessanalyzer/12.0/solutions/box/collection/1-box_activity_scans.md @@ -27,7 +27,7 @@ the Activity Scan query, unless you already completed this step when you configu - Not scoped -See the [Configure the 1-Box_Activity Scans Job](#configure-the-1-boxactivity-scans-job) section +See the [Configure the 1-Box_Activity Scans Job](#configure-the-1-box_activity-scans-job) section for instructions. ### Configure the 1-Box_Activity Scans Job diff --git a/docs/accessanalyzer/12.0/solutions/box/content/box_filemetrics.md b/docs/accessanalyzer/12.0/solutions/box/content/box_filemetrics.md index f1d1c84836..f0532634cb 100644 --- a/docs/accessanalyzer/12.0/solutions/box/content/box_filemetrics.md +++ b/docs/accessanalyzer/12.0/solutions/box/content/box_filemetrics.md @@ -32,7 +32,7 @@ The following analysis tasks are selected by default: Results node - Set to consider content stale after 30 days which is the @STALETHRESHOLD parameter value - See the - [Customize Analysis Tasks for the Box_FileMetrics Job](#customize-analysis-tasks-for-the-boxfilemetrics-job) + [Customize Analysis Tasks for the Box_FileMetrics Job](#customize-analysis-tasks-for-the-box_filemetrics-job) topic for additional information. - File Count by User – Creates the Box_FileMetrics_UserFileCount table accessible under the job’s Results node diff --git a/docs/accessanalyzer/12.0/solutions/box/content/box_foldermetrics.md b/docs/accessanalyzer/12.0/solutions/box/content/box_foldermetrics.md index b767ab24fc..2525499e5e 100644 --- a/docs/accessanalyzer/12.0/solutions/box/content/box_foldermetrics.md +++ b/docs/accessanalyzer/12.0/solutions/box/content/box_foldermetrics.md @@ -34,7 +34,7 @@ The following analysis tasks are selected by default: Results node - Set to consider content stale after 30 days which is the @STALETHRESHOLD parameter value - See the - [Customizable Analysis Tasks for the Box_FolderMetrics Job](#customizable-analysis-tasks-for-the-boxfoldermetrics-job) + [Customizable Analysis Tasks for the Box_FolderMetrics Job](#customizable-analysis-tasks-for-the-box_foldermetrics-job) topic for additional information. - Largest Folders – Creates the Box_FolderMetrics_Largest table accessible under the job’s Results node diff --git a/docs/accessanalyzer/12.0/solutions/dropbox/dropbox_content.md b/docs/accessanalyzer/12.0/solutions/dropbox/dropbox_content.md index 178918c287..e0002d2b01 100644 --- a/docs/accessanalyzer/12.0/solutions/dropbox/dropbox_content.md +++ b/docs/accessanalyzer/12.0/solutions/dropbox/dropbox_content.md @@ -26,7 +26,7 @@ The Dropbox_Content job has the following customizable parameter: - Days since File Modification before a file is considered stale See the -[Customizable Analysis Tasks for the Dropbox_Content Job](#customizable-analysis-tasks-for-the-dropboxcontent-job) +[Customizable Analysis Tasks for the Dropbox_Content Job](#customizable-analysis-tasks-for-the-dropbox_content-job) topic for additional information. ## Analysis Tasks for the Dropbox_Content Job @@ -48,7 +48,7 @@ preconfigured for this job. - By default, a stale file has not been modified in the past 365 days. You can modify this analysis task to edit this number of days. See the - [Customizable Analysis Tasks for the Dropbox_Content Job](#customizable-analysis-tasks-for-the-dropboxcontent-job) + [Customizable Analysis Tasks for the Dropbox_Content Job](#customizable-analysis-tasks-for-the-dropbox_content-job) topic for additional information. - Creates an interim processing table in the database for use by downstream analysis and report generation diff --git a/docs/accessanalyzer/12.0/solutions/entraidinventory/1-aad_scan.md b/docs/accessanalyzer/12.0/solutions/entraidinventory/1-aad_scan.md index 1a76879a4f..465cfb7d37 100644 --- a/docs/accessanalyzer/12.0/solutions/entraidinventory/1-aad_scan.md +++ b/docs/accessanalyzer/12.0/solutions/entraidinventory/1-aad_scan.md @@ -27,7 +27,7 @@ The 1-AAD_Scan job uses the AzureADInventory and Entra Data Collectors for the f - AAD Inventory – Targets Microsoft Entra tenants to collect inventory data for user group objects - _(Optional)_ This query can be modified to specify scan options and to collect custom - attributes. See the [Configure the AAD_Inventory Query](#configure-the-aadinventory-query) + attributes. See the [Configure the AAD_Inventory Query](#configure-the-aad_inventory-query) topic for additional information. - Entra – Collects Entra roles details from the target Microsoft Entra tenants diff --git a/docs/accessanalyzer/12.0/solutions/entraidinventory/2-aad_exceptions.md b/docs/accessanalyzer/12.0/solutions/entraidinventory/2-aad_exceptions.md index 08dc2fc27f..c534e4df49 100644 --- a/docs/accessanalyzer/12.0/solutions/entraidinventory/2-aad_exceptions.md +++ b/docs/accessanalyzer/12.0/solutions/entraidinventory/2-aad_exceptions.md @@ -80,7 +80,7 @@ The default values for parameters that can be customized are: | Stale Membership | @STALE_THRESHOLD | 10 | A group where 10% of its effective members are stale users | See the -[Configure the Analysis Tasks for the 2-AAD_Exceptions Job](#configure-the-analysis-tasks-for-the-2-aadexceptions-job) +[Configure the Analysis Tasks for the 2-AAD_Exceptions Job](#configure-the-analysis-tasks-for-the-2-aad_exceptions-job) section for instructions to modify parameters. See the [AzureADInventory Exception Types Translated](/docs/accessanalyzer/12.0/admin/datacollector/azureadinventory/standardtables.md#azureadinventory-exception-types-translated) topic for an explanation of Exception Types. diff --git a/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow.md b/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow.md index d5d270a86f..45d1e5c774 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow.md @@ -23,7 +23,7 @@ The EX_Mailflow job has the following configurable parameter: - Number of months to keep -See the [Analysis Tasks for the EX_Mailflow Job](#analysis-tasks-for-the-exmailflow-job) topic for +See the [Analysis Tasks for the EX_Mailflow Job](#analysis-tasks-for-the-ex_mailflow-job) topic for additional information. ## Queries for the EX_Mailflow Job diff --git a/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow_domain.md b/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow_domain.md index 324bc22e3d..2f8f247f14 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow_domain.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow_domain.md @@ -21,7 +21,7 @@ The EX_Mailflow_Domain job has the following configurable parameter: - Number of days to show in tables and reports See the -[Analysis Tasks for the EX_Mailflow_Domain Job](#analysis-tasks-for-the-exmailflowdomain-job) +[Analysis Tasks for the EX_Mailflow_Domain Job](#analysis-tasks-for-the-ex_mailflow_domain-job) topic for additional information. ## Analysis Tasks for the EX_Mailflow_Domain Job diff --git a/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow_mailbox.md b/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow_mailbox.md index 4eb6c540af..c9e26a25e7 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow_mailbox.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow_mailbox.md @@ -22,7 +22,7 @@ The EX_Mailflow_Mailbox job has the following configurable parameter: Count** and **User Mailboxes by Message Size** analysis tasks. The default is **30** days. See the -[Analysis Tasks for the EX_Mailflow_Mailbox Job](#analysis-tasks-for-the-exmailflowmailbox-job) +[Analysis Tasks for the EX_Mailflow_Mailbox Job](#analysis-tasks-for-the-ex_mailflow_mailbox-job) topic for additional information. ## Analysis Tasks for the EX_Mailflow_Mailbox Job diff --git a/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow_orgoverview.md b/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow_orgoverview.md index 91b896c3da..dc731c74b8 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow_orgoverview.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/online/mailflow/ex_mailflow_orgoverview.md @@ -21,7 +21,7 @@ The EX_Mailflow_OrgOverview job has the following configurable parameter: - Number of days of data to display See the -[Analysis Tasks for the EX_Mailflow_OrgOverview Job](#analysis-tasks-for-the-exmailfloworgoverview-job) +[Analysis Tasks for the EX_Mailflow_OrgOverview Job](#analysis-tasks-for-the-ex_mailflow_orgoverview-job) topic for additional information. ## Analysis Tasks for the EX_Mailflow_OrgOverview Job diff --git a/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/ownership/pf_folderownership.md b/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/ownership/pf_folderownership.md index 2be3f94560..3edad19274 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/ownership/pf_folderownership.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/publicfolders/ownership/pf_folderownership.md @@ -28,7 +28,7 @@ The following queries are included in the PF_FolderOwnership job: - By default set to search all public folders. It can be scoped. - See the - [Scope the ExchangePublicFolder Data Collector for the PF_FolderOwnership Job](#scope-the-exchangepublicfolder-data-collector-for-the-pffolderownership-job) + [Scope the ExchangePublicFolder Data Collector for the PF_FolderOwnership Job](#scope-the-exchangepublicfolder-data-collector-for-the-pf_folderownership-job) topic for additional information - Assigned Ownership – Collects assigned owners @@ -36,7 +36,7 @@ The following queries are included in the PF_FolderOwnership job: - By default set to search all public folders. It can be scoped. - Probable Owner Calculation can be modified - See the - [Scope the ExchangePublicFolder Data Collector for the PF_FolderOwnership Job](#scope-the-exchangepublicfolder-data-collector-for-the-pffolderownership-job) + [Scope the ExchangePublicFolder Data Collector for the PF_FolderOwnership Job](#scope-the-exchangepublicfolder-data-collector-for-the-pf_folderownership-job) topic for additional information ### Scope the ExchangePublicFolder Data Collector for the PF_FolderOwnership Job diff --git a/docs/accessanalyzer/12.0/solutions/exchange/sensitivedata/collection/ex_mailbox_sdd.md b/docs/accessanalyzer/12.0/solutions/exchange/sensitivedata/collection/ex_mailbox_sdd.md index 7fdee61cbb..c6f1210817 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/sensitivedata/collection/ex_mailbox_sdd.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/sensitivedata/collection/ex_mailbox_sdd.md @@ -28,7 +28,7 @@ The following query is included in the EX_Mailbox_SDD job: - US SSN - See the - [Configure the EWSMailbox Data Collector for the EX_Mailbox_SDD Job](#configure-the-ewsmailbox-data-collector-for-the-exmailboxsdd-job) + [Configure the EWSMailbox Data Collector for the EX_Mailbox_SDD Job](#configure-the-ewsmailbox-data-collector-for-the-ex_mailbox_sdd-job) topic for additional information ### Configure the EWSMailbox Data Collector for the EX_Mailbox_SDD Job diff --git a/docs/accessanalyzer/12.0/solutions/exchange/sensitivedata/collection/ex_publicfolder_sdd.md b/docs/accessanalyzer/12.0/solutions/exchange/sensitivedata/collection/ex_publicfolder_sdd.md index 9821d5155e..5ebf51a486 100644 --- a/docs/accessanalyzer/12.0/solutions/exchange/sensitivedata/collection/ex_publicfolder_sdd.md +++ b/docs/accessanalyzer/12.0/solutions/exchange/sensitivedata/collection/ex_publicfolder_sdd.md @@ -28,7 +28,7 @@ The following query is included in the EX_PublicFolder_SDD job: - Tax Forms - US SSN - - See the [Configure the EX_PublicFolder_SDD Query](#configure-the-expublicfoldersdd-query) + - See the [Configure the EX_PublicFolder_SDD Query](#configure-the-ex_publicfolder_sdd-query) topic for additional information ### Configure the EX_PublicFolder_SDD Query diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/delete/fs_deletefiles.md b/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/delete/fs_deletefiles.md index aa188068fd..c3d83a6fe2 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/delete/fs_deletefiles.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/delete/fs_deletefiles.md @@ -21,7 +21,7 @@ The FS_DeleteFiles job has the following configurable parameter: - Number of days without access after which a file is a deletion candidate See the -[Customizable Analysis Tasks for the FS_DeleteFiles Job](#customizable-analysis-tasks-for-the-fsdeletefiles-job) +[Customizable Analysis Tasks for the FS_DeleteFiles Job](#customizable-analysis-tasks-for-the-fs_deletefiles-job) topic for additional information. ## Analysis Tasks for the FS_DeleteFiles Job diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/fs_cleanupassessment.md b/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/fs_cleanupassessment.md index 0b5c4cab62..985b2e5212 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/fs_cleanupassessment.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/fs_cleanupassessment.md @@ -49,7 +49,7 @@ The FS_CleanupAssessment job has the following configurable parameters: - Upper bound for files to be included in the FileDetails table (by LastModfied, in days) See the -[Customizable Analysis Tasks for the FS_CleanupAssessment Job](#customizable-analysis-tasks-for-the-fscleanupassessment-job) +[Customizable Analysis Tasks for the FS_CleanupAssessment Job](#customizable-analysis-tasks-for-the-fs_cleanupassessment-job) topic for additional information. ## Analysis Tasks for the FS_CleanupAssessment Job @@ -73,14 +73,14 @@ The following analysis tasks are selected by default: - See the [Include Metadata Tag Information](#include-metadata-tag-information) topic for instructions on how to include metadata tag information in this table - Has 3 configurable parameters. See the - [Customizable Analysis Tasks for the FS_CleanupAssessment Job](#customizable-analysis-tasks-for-the-fscleanupassessment-job) + [Customizable Analysis Tasks for the FS_CleanupAssessment Job](#customizable-analysis-tasks-for-the-fs_cleanupassessment-job) topic for additional information. - Create file-level details table – Creates the SA_FS_CleanupAssessment_FileDetails table accessible under the job’s Results node - Has 2 configurable parameters. See the - [Customizable Analysis Tasks for the FS_CleanupAssessment Job](#customizable-analysis-tasks-for-the-fscleanupassessment-job) + [Customizable Analysis Tasks for the FS_CleanupAssessment Job](#customizable-analysis-tasks-for-the-fs_cleanupassessment-job) topic for additional information. - Summarize share-level information – Creates the SA_FS_CleanupAssessment_ShareDetails table diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/notify/fs_notifyowners.md b/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/notify/fs_notifyowners.md index d36d79f946..d1100f6889 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/notify/fs_notifyowners.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/cleanup/notify/fs_notifyowners.md @@ -29,7 +29,7 @@ The following action task is deselected by default. Before running the FS_NotifyOwners job, select the **Notify Owners** task and configure the properties for the SendMail action module. See the -[Configure the FS_NotifyOwners Action](#configure-the-fsnotifyowners-action) topic for additional +[Configure the FS_NotifyOwners Action](#configure-the-fs_notifyowners-action) topic for additional information. ### Configure the FS_NotifyOwners Action diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/fs_brokeninheritance.md b/docs/accessanalyzer/12.0/solutions/filesystem/fs_brokeninheritance.md index 61ae6443f4..203de256e4 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/fs_brokeninheritance.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/fs_brokeninheritance.md @@ -29,7 +29,7 @@ The FS_BrokenInheritance job has the following configurable parameter: - 2 – Analyze all resources regardless of permission changes between parent and child See the -[Analysis Tasks for the FS_BrokenInheritance Job](#analysis-tasks-for-the-fsbrokeninheritance-job) +[Analysis Tasks for the FS_BrokenInheritance Job](#analysis-tasks-for-the-fs_brokeninheritance-job) topic for additional information. ## Analysis Tasks for the FS_BrokenInheritance Job diff --git a/docs/accessanalyzer/12.0/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroupaicimport.md b/docs/accessanalyzer/12.0/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroupaicimport.md index d7add89ad7..ab494f9a49 100644 --- a/docs/accessanalyzer/12.0/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroupaicimport.md +++ b/docs/accessanalyzer/12.0/solutions/filesystem/resourcebasedgroups/fs_resourcebasedgroupaicimport.md @@ -50,7 +50,7 @@ Not supported **Step 2 –** Run the FS_ResourceBasedGroupsAICImport job. -- See the [Run the FS_ResourceBasedGroupsAICImportJob](#run-the-fsresourcebasedgroupsaicimportjob) +- See the [Run the FS_ResourceBasedGroupsAICImportJob](#run-the-fs_resourcebasedgroupsaicimportjob) topic for additional information **Step 3 –** Review the newly-created resource based groups in the AIC. diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/collection/7-spaa_exceptions.md b/docs/accessanalyzer/12.0/solutions/sharepoint/collection/7-spaa_exceptions.md index 3183178fdf..08736993e4 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/collection/7-spaa_exceptions.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/collection/7-spaa_exceptions.md @@ -27,7 +27,7 @@ The 7-SPAA_Exceptions page has the following configurable parameters: See the -[Customizable Analysis Tasks for the 7-SPAA_Exceptions Job](#customizable-analysis-tasks-for-the-7-spaaexceptions-job) +[Customizable Analysis Tasks for the 7-SPAA_Exceptions Job](#customizable-analysis-tasks-for-the-7-spaa_exceptions-job) for additional information. ## Analysis Tasks 7-SPAA_Exceptions Job diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/content/sp_stalefiles.md b/docs/accessanalyzer/12.0/solutions/sharepoint/content/sp_stalefiles.md index d03e388f1b..380bd046a0 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/content/sp_stalefiles.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/content/sp_stalefiles.md @@ -24,7 +24,7 @@ The SP_StaleFiles page has the following configurable parameters: - Days since last modification to be considered stale See the -[Customizable Analysis Tasks for the SP_StaleFiles Job](#customizable-analysis-tasks-for-the-spstalefiles-job) +[Customizable Analysis Tasks for the SP_StaleFiles Job](#customizable-analysis-tasks-for-the-sp_stalefiles-job) for additional information. ## Analysis Tasks for the SP_StaleFiles Job @@ -46,7 +46,7 @@ The default analysis task is: node - This analysis task contains a configurable parameter: `@stale`. See the - [Customizable Analysis Tasks for the SP_StaleFiles Job](#customizable-analysis-tasks-for-the-spstalefiles-job) + [Customizable Analysis Tasks for the SP_StaleFiles Job](#customizable-analysis-tasks-for-the-sp_stalefiles-job) topic for additional information. In addition to the table created by the analysis task which displays the stale file resources, the diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/effectiveaccessaudits/sp_trusteeaccess.md b/docs/accessanalyzer/12.0/solutions/sharepoint/effectiveaccessaudits/sp_trusteeaccess.md index 0e8c813246..c8d55cf712 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/effectiveaccessaudits/sp_trusteeaccess.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/effectiveaccessaudits/sp_trusteeaccess.md @@ -14,7 +14,7 @@ multiple users’ effective access at once. :::note Trustees can be specified in the `UserScoping.csv` file for the SP_TrusteeAccess Job. See the -[Configure CSV File for the Query for the SP_TrusteeAccess Job](#configure-csv-file-for-the-query-for-the-sptrusteeaccess-job) +[Configure CSV File for the Query for the SP_TrusteeAccess Job](#configure-csv-file-for-the-query-for-the-sp_trusteeaccess-job) topic for additional information. ::: @@ -32,7 +32,7 @@ The SP_TrusteeAccess Job uses the TextSearch Data Collector for the following qu The default query is: - Scoping – Modifies the CSV in the Job Directory. See the - [Configure CSV File for the Query for the SP_TrusteeAccess Job](#configure-csv-file-for-the-query-for-the-sptrusteeaccess-job) + [Configure CSV File for the Query for the SP_TrusteeAccess Job](#configure-csv-file-for-the-query-for-the-sp_trusteeaccess-job) topic for additional information. ### Configure CSV File for the Query for the SP_TrusteeAccess Job diff --git a/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_staleteamsites.md b/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_staleteamsites.md index a66cdb71ef..28b44146e2 100644 --- a/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_staleteamsites.md +++ b/docs/accessanalyzer/12.0/solutions/sharepoint/m365/sp_staleteamsites.md @@ -21,7 +21,7 @@ The SP_StaleTeamSites page has the following configurable parameters: - Desired Number of Days Since Last Activity To Determine Staleness See the -[Customizable Analysis Tasks for the SP_StaleTeamSites Job](#customizable-analysis-tasks-for-the-spstaleteamsites-job) +[Customizable Analysis Tasks for the SP_StaleTeamSites Job](#customizable-analysis-tasks-for-the-sp_staleteamsites-job) for additional information. ## Analysis Tasks for the SP_StaleTeamSites Job @@ -37,7 +37,7 @@ The default analysis task is: - This task contains a configurable parameter to set the number of days a Team has not had activity for before it's considered stale. See the - [Customizable Analysis Tasks for the SP_StaleTeamSites Job](#customizable-analysis-tasks-for-the-spstaleteamsites-job) + [Customizable Analysis Tasks for the SP_StaleTeamSites Job](#customizable-analysis-tasks-for-the-sp_staleteamsites-job) topic for additional information. In addition to the table created by the analysis task, the SP_StaleTeamSites Job produces the diff --git a/scripts/check-anchors.sh b/scripts/check-anchors.sh index 67ec31a6e2..17a27f048a 100755 --- a/scripts/check-anchors.sh +++ b/scripts/check-anchors.sh @@ -43,10 +43,13 @@ slugify() { # are NOT collapsed and leading/trailing hyphens are NOT trimmed. A # heading like "Step 4 — Configure" (em dash stripped, two spaces # remain) slugs to "step-4--configure", not "step-4-configure". + # Underscores are preserved — github-slugger only strips punctuation/ + # symbols, not word characters like `_` (e.g. "Box_FileMetrics" stays + # "box_filemetrics", not "boxfilemetrics"). printf '%s' "$heading" \ | sed -E 's/^#+ +//' \ | tr '[:upper:]' '[:lower:]' \ - | sed -E "s/[^a-z0-9 -]//g" \ + | sed -E "s/[^a-z0-9 _-]//g" \ | sed -E 's/ /-/g' } From 293947a569ec7ffb27de4dc24ba46e1d4edd07de Mon Sep 17 00:00:00 2001 From: "james.haytko" Date: Mon, 24 Aug 2026 18:15:22 -0500 Subject: [PATCH 05/36] fix: preserve underscores in vale-autofix.sh anchor slugify MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit scripts/vale-autofix.sh had its own slugify() that diverged from github-slugger (used by Docusaurus): it stripped underscores and collapsed/trimmed hyphens, neither of which github-slugger does. This is the same class of bug just fixed in scripts/check-anchors.sh, and it lives in update_heading_anchors(), the function that auto-rewrites anchor links in vale-autofix.yml's "Fix heading anchors" step whenever a heading is renamed — so a future underscore-containing heading rename would silently compute the wrong new anchor and reproduce this PR's original failure. Also corrects two now-incorrect expectations in test-slugify.sh that had encoded the old (wrong) hyphen-collapsing behavior. Co-Authored-By: Claude Sonnet 5 --- scripts/test-slugify.sh | 10 +++++++--- scripts/vale-autofix.sh | 12 ++++++++---- 2 files changed, 15 insertions(+), 7 deletions(-) diff --git a/scripts/test-slugify.sh b/scripts/test-slugify.sh index 4697d82a04..da12c20a34 100644 --- a/scripts/test-slugify.sh +++ b/scripts/test-slugify.sh @@ -41,9 +41,13 @@ assert_slug "## Step 1. Configure" "step-1-configure" assert_slug '## Setup the Application {#setup}' "setup" assert_slug '### Advanced Options {#advanced-opts}' "advanced-opts" -# Extra whitespace and hyphens -assert_slug "## Lots of Spaces" "lots-of-spaces" -assert_slug "## Already-Hyphenated--Word" "already-hyphenated-word" +# Extra whitespace and hyphens — github-slugger does NOT collapse runs of +# hyphens or trim them; each removed/replaced character leaves its slot. +assert_slug "## Lots of Spaces" "lots---of---spaces" +assert_slug "## Already-Hyphenated--Word" "already-hyphenated--word" + +# Underscores are preserved (word characters, not punctuation) +assert_slug "## Box_FileMetrics Job" "box_filemetrics-job" # Edge cases assert_slug "## 123 Numbers First" "123-numbers-first" diff --git a/scripts/vale-autofix.sh b/scripts/vale-autofix.sh index 6d578550af..03b82cdbfb 100755 --- a/scripts/vale-autofix.sh +++ b/scripts/vale-autofix.sh @@ -16,13 +16,17 @@ slugify() { return fi + # Mirrors github-slugger's behavior (used by Docusaurus, and by + # scripts/check-anchors.sh): each removed character leaves its + # surrounding whitespace intact, so runs of hyphens are NOT collapsed + # and leading/trailing hyphens are NOT trimmed. Underscores are + # preserved — github-slugger only strips punctuation/symbols, not word + # characters like `_` (e.g. "Box_FileMetrics" stays "box_filemetrics"). echo "$heading" \ | sed -E 's/^#+ +//' \ | tr '[:upper:]' '[:lower:]' \ - | sed -E "s/[^a-z0-9 -]//g" \ - | sed -E 's/ +/-/g' \ - | sed -E 's/-+/-/g' \ - | sed -E 's/^-+//;s/-+$//' + | sed -E "s/[^a-z0-9 _-]//g" \ + | sed -E 's/ /-/g' } _get_product_version_folder() { From 8e6de13e88497625f8ce8d5d63cf7995883df561 Mon Sep 17 00:00:00 2001 From: "james.haytko" Date: Mon, 24 Aug 2026 18:51:28 -0500 Subject: [PATCH 06/36] fix(scripts): correct word-overlap scoring, dedupe slugify, wire up tests MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit _word_overlap_score() in vale-autofix.sh counted empty array elements (produced by uncollapsed hyphen runs after the earlier slugify fix) in its maxlen denominator, deflating scores enough to push real heading renames below the match threshold — silently skipping an anchor repair that used to work. Also extracts the duplicated slugify() (previously hand-synced between vale-autofix.sh and check-anchors.sh, and the source of two rounds of the same underscore bug) into a single scripts/lib/slugify.sh both scripts source. test-slugify.sh now tests that shared implementation directly instead of only vale-autofix.sh's copy. Wires scripts/test-slugify.sh and scripts/test-anchor-update.sh into CI (new `npm run test:scripts`, run as a step in vale-autofix.yml) so regressions in either script are caught automatically instead of only by manual review. Co-Authored-By: Claude Sonnet 5 --- .github/workflows/vale-autofix.yml | 4 ++++ package.json | 1 + scripts/check-anchors.sh | 23 +------------------ scripts/lib/slugify.sh | 26 +++++++++++++++++++++ scripts/test-slugify.sh | 7 +++--- scripts/vale-autofix.sh | 37 +++++++++++------------------- 6 files changed, 49 insertions(+), 49 deletions(-) create mode 100644 scripts/lib/slugify.sh diff --git a/.github/workflows/vale-autofix.yml b/.github/workflows/vale-autofix.yml index 0864b83ea9..8ceb306e48 100644 --- a/.github/workflows/vale-autofix.yml +++ b/.github/workflows/vale-autofix.yml @@ -57,6 +57,10 @@ jobs: git config user.name "github-actions[bot]" git config user.email "github-actions[bot]@users.noreply.github.com" + - name: Test anchor/slugify scripts + if: steps.bot-check.outputs.skip != 'true' + run: npm run test:scripts + - name: Get changed markdown files id: changed-files if: steps.bot-check.outputs.skip != 'true' diff --git a/package.json b/package.json index 299c99cc17..76481ea33d 100644 --- a/package.json +++ b/package.json @@ -22,6 +22,7 @@ "kb:dry": "node scripts/copy-kb-to-versions.mjs --dry", "kb:test:aa": "npm run kb:clean && npm run prestart && npm run start", "kb:prodtest:aa": "npm run kb:clean && npm run prebuild && npm run build && npm run serve", + "test:scripts": "bash scripts/test-slugify.sh && bash scripts/test-anchor-update.sh", "prepare": "husky || true" }, "dependencies": { diff --git a/scripts/check-anchors.sh b/scripts/check-anchors.sh index 17a27f048a..d2cf269273 100755 --- a/scripts/check-anchors.sh +++ b/scripts/check-anchors.sh @@ -8,6 +8,7 @@ set -euo pipefail REPO_ROOT="$(git rev-parse --show-toplevel)" +source "$REPO_ROOT/scripts/lib/slugify.sh" ERRORS=0 # Bash 3-compatible heading cache: parallel arrays of keys and values HEADING_CACHE_KEYS=() @@ -31,28 +32,6 @@ _cache_set() { HEADING_CACHE_VALS+=("$val") } -slugify() { - local heading="$1" - # Respect explicit anchor IDs: ## Heading {#custom-id} - if [[ "$heading" =~ \{#([a-zA-Z0-9_-]+)\} ]]; then - printf '%s' "${BASH_REMATCH[1]}" - return - fi - # Mirrors github-slugger's behavior (used by Docusaurus): each removed - # character leaves its surrounding whitespace intact, so runs of hyphens - # are NOT collapsed and leading/trailing hyphens are NOT trimmed. A - # heading like "Step 4 — Configure" (em dash stripped, two spaces - # remain) slugs to "step-4--configure", not "step-4-configure". - # Underscores are preserved — github-slugger only strips punctuation/ - # symbols, not word characters like `_` (e.g. "Box_FileMetrics" stays - # "box_filemetrics", not "boxfilemetrics"). - printf '%s' "$heading" \ - | sed -E 's/^#+ +//' \ - | tr '[:upper:]' '[:lower:]' \ - | sed -E "s/[^a-z0-9 _-]//g" \ - | sed -E 's/ /-/g' -} - load_headings() { local file="$1" _cache_get "$file" && return diff --git a/scripts/lib/slugify.sh b/scripts/lib/slugify.sh new file mode 100644 index 0000000000..aac0fcebf4 --- /dev/null +++ b/scripts/lib/slugify.sh @@ -0,0 +1,26 @@ +# slugify.sh — shared heading-to-anchor slug logic +# Sourced by scripts/check-anchors.sh and scripts/vale-autofix.sh so the two +# scripts can't drift out of sync (see the PR history of both files for what +# happens when they do). + +slugify() { + local heading="$1" + # Respect explicit anchor IDs: ## Heading {#custom-id} + if [[ "$heading" =~ \{#([a-zA-Z0-9_-]+)\} ]]; then + printf '%s' "${BASH_REMATCH[1]}" + return + fi + # Mirrors github-slugger's behavior (used by Docusaurus): each removed + # character leaves its surrounding whitespace intact, so runs of hyphens + # are NOT collapsed and leading/trailing hyphens are NOT trimmed. A + # heading like "Step 4 — Configure" (em dash stripped, two spaces + # remain) slugs to "step-4--configure", not "step-4-configure". + # Underscores are preserved — github-slugger only strips punctuation/ + # symbols, not word characters like `_` (e.g. "Box_FileMetrics" stays + # "box_filemetrics", not "boxfilemetrics"). + printf '%s' "$heading" \ + | sed -E 's/^#+ +//' \ + | tr '[:upper:]' '[:lower:]' \ + | sed -E "s/[^a-z0-9 _-]//g" \ + | sed -E 's/ /-/g' +} diff --git a/scripts/test-slugify.sh b/scripts/test-slugify.sh index da12c20a34..9c0a1f5a21 100644 --- a/scripts/test-slugify.sh +++ b/scripts/test-slugify.sh @@ -1,9 +1,10 @@ #!/usr/bin/env bash -# test-slugify.sh — unit tests for the slugify function in vale-autofix.sh +# test-slugify.sh — unit tests for the shared slugify function +# (scripts/lib/slugify.sh), sourced by both vale-autofix.sh and +# check-anchors.sh. set -euo pipefail -# Source just the functions (--test mode skips the main script logic) -source "$(dirname "$0")/vale-autofix.sh" --test +source "$(cd "$(dirname "$0")" && pwd)/lib/slugify.sh" PASS=0 FAIL=0 diff --git a/scripts/vale-autofix.sh b/scripts/vale-autofix.sh index 03b82cdbfb..d824391a0c 100755 --- a/scripts/vale-autofix.sh +++ b/scripts/vale-autofix.sh @@ -5,29 +5,11 @@ set -euo pipefail -# --- Shared functions --- - -slugify() { - local heading="$1" +SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" - # Check for custom anchor ID: {#custom-id} - if [[ "$heading" =~ \{#([a-zA-Z0-9_-]+)\} ]]; then - echo "${BASH_REMATCH[1]}" - return - fi +# --- Shared functions --- - # Mirrors github-slugger's behavior (used by Docusaurus, and by - # scripts/check-anchors.sh): each removed character leaves its - # surrounding whitespace intact, so runs of hyphens are NOT collapsed - # and leading/trailing hyphens are NOT trimmed. Underscores are - # preserved — github-slugger only strips punctuation/symbols, not word - # characters like `_` (e.g. "Box_FileMetrics" stays "box_filemetrics"). - echo "$heading" \ - | sed -E 's/^#+ +//' \ - | tr '[:upper:]' '[:lower:]' \ - | sed -E "s/[^a-z0-9 _-]//g" \ - | sed -E 's/ /-/g' -} +source "$SCRIPT_DIR/lib/slugify.sh" _get_product_version_folder() { local filepath="$1" @@ -51,16 +33,23 @@ _word_overlap_score() { local -a ow nw IFS='-' read -ra ow <<< "$old_slug" IFS='-' read -ra nw <<< "$new_slug" - local intersect=0 word nword + local intersect=0 oreal=0 nreal=0 word nword for word in "${ow[@]}"; do [ -z "$word" ] && continue + oreal=$((oreal + 1)) for nword in "${nw[@]}"; do [ -z "$nword" ] && continue if [ "$word" = "$nword" ]; then intersect=$((intersect + 1)); break; fi done done - local maxlen=${#ow[@]} - [ ${#nw[@]} -gt "$maxlen" ] && maxlen=${#nw[@]} + for nword in "${nw[@]}"; do + [ -n "$nword" ] && nreal=$((nreal + 1)) + done + # Count only non-empty tokens: uncollapsed hyphen runs in the slug produce + # empty elements when split on '-', which would otherwise inflate the + # denominator and deflate the score below the rename-match threshold. + local maxlen=$oreal + [ "$nreal" -gt "$maxlen" ] && maxlen=$nreal [ "$maxlen" -eq 0 ] && echo 0 && return echo $(( (intersect * 100) / maxlen )) } From 14733af4a8b58d9420acbc9d6d2616eed54089df Mon Sep 17 00:00:00 2001 From: "james.haytko" Date: Mon, 24 Aug 2026 19:04:45 -0500 Subject: [PATCH 07/36] fix(scripts): trim trailing whitespace/ATX close in slugify, dedupe word-overlap matches MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit slugify() stripped leading "## " but nothing trailing, so a heading like "## Clients " (or "## Overview ##") slugged to "clients-"/"overview-". Docusaurus doesn't see that trailing whitespace — remark trims it from the heading's text node before github-slugger ever runs — so the two disagreed. check-anchors.sh was already like this (harmless there: read-only, and the step is continue-on-error). It became load-bearing in vale-autofix.sh once the consolidation removed that script's old trailing-hyphen trim, letting update_heading_anchors() write a "#clients-" anchor that would 404 at build time. Verified against remark+github-slugger directly. Also fixes _word_overlap_score() double-counting a repeated old-slug token against the same new-slug token (e.g. two "the"s both matching one "the"), which could inflate a score past the match threshold. Matched tokens are now marked consumed so each new-slug word can only satisfy one match. Co-Authored-By: Claude Sonnet 5 --- scripts/lib/slugify.sh | 11 ++++++++++- scripts/test-slugify.sh | 7 +++++++ scripts/vale-autofix.sh | 13 ++++++++++--- 3 files changed, 27 insertions(+), 4 deletions(-) diff --git a/scripts/lib/slugify.sh b/scripts/lib/slugify.sh index aac0fcebf4..7d60dfd043 100644 --- a/scripts/lib/slugify.sh +++ b/scripts/lib/slugify.sh @@ -18,8 +18,17 @@ slugify() { # Underscores are preserved — github-slugger only strips punctuation/ # symbols, not word characters like `_` (e.g. "Box_FileMetrics" stays # "box_filemetrics", not "boxfilemetrics"). + # + # Trailing whitespace (and a trailing ATX closing sequence, e.g. + # "## Overview ##") must be stripped BEFORE punctuation removal, because + # Docusaurus never slugs it: remark trims it off the heading's text node + # before github-slugger ever sees it. Leading/trailing trims only run + # once, after the ATX markers are gone, so they can't be confused with + # intentional interior whitespace runs. printf '%s' "$heading" \ - | sed -E 's/^#+ +//' \ + | sed -E 's/^#+[[:space:]]+//' \ + | sed -E 's/[[:space:]]+#+[[:space:]]*$//' \ + | sed -E 's/[[:space:]]+$//' \ | tr '[:upper:]' '[:lower:]' \ | sed -E "s/[^a-z0-9 _-]//g" \ | sed -E 's/ /-/g' diff --git a/scripts/test-slugify.sh b/scripts/test-slugify.sh index 9c0a1f5a21..107134ad70 100644 --- a/scripts/test-slugify.sh +++ b/scripts/test-slugify.sh @@ -50,6 +50,13 @@ assert_slug "## Already-Hyphenated--Word" "already-hyphenated--word" # Underscores are preserved (word characters, not punctuation) assert_slug "## Box_FileMetrics Job" "box_filemetrics-job" +# Trailing whitespace and ATX closing sequences: remark strips these from +# the heading's text node before github-slugger ever runs, so slugify() +# must match — not leave a trailing hyphen. +assert_slug "## Clients " "clients" +assert_slug "## Overview ##" "overview" +assert_slug "#### C#" "c" + # Edge cases assert_slug "## 123 Numbers First" "123-numbers-first" assert_slug "## ALL CAPS HEADING" "all-caps-heading" diff --git a/scripts/vale-autofix.sh b/scripts/vale-autofix.sh index d824391a0c..f9dd6d677a 100755 --- a/scripts/vale-autofix.sh +++ b/scripts/vale-autofix.sh @@ -33,13 +33,20 @@ _word_overlap_score() { local -a ow nw IFS='-' read -ra ow <<< "$old_slug" IFS='-' read -ra nw <<< "$new_slug" - local intersect=0 oreal=0 nreal=0 word nword + local intersect=0 oreal=0 nreal=0 word nword i + local -a used=() for word in "${ow[@]}"; do [ -z "$word" ] && continue oreal=$((oreal + 1)) - for nword in "${nw[@]}"; do + for i in "${!nw[@]}"; do + nword="${nw[$i]}" [ -z "$nword" ] && continue - if [ "$word" = "$nword" ]; then intersect=$((intersect + 1)); break; fi + [ -n "${used[$i]:-}" ] && continue + if [ "$word" = "$nword" ]; then + intersect=$((intersect + 1)) + used[$i]=1 + break + fi done done for nword in "${nw[@]}"; do From f5fac69e6115d70b9f364a9a8674553d75cf25cb Mon Sep 17 00:00:00 2001 From: "james.haytko" Date: Mon, 24 Aug 2026 19:32:04 -0500 Subject: [PATCH 08/36] fix(ci): trigger test:scripts on script changes, wire up orphaned test, avoid SCRIPT_DIR clobber Addresses process-level review findings: the vale-autofix workflow's path filter meant test:scripts never ran on PRs that only touched the scripts it tests; test-md-extension-autofix.sh wasn't wired into any test entry point despite md-extension-autofix.sh running as a real PR check; and vale-autofix.sh's unnamespaced SCRIPT_DIR silently clobbered test-anchor-update.sh's own variable of the same name when sourced. Co-Authored-By: Claude Sonnet 5 --- .github/workflows/vale-autofix.yml | 2 ++ package.json | 2 +- scripts/vale-autofix.sh | 7 +++++-- 3 files changed, 8 insertions(+), 3 deletions(-) diff --git a/.github/workflows/vale-autofix.yml b/.github/workflows/vale-autofix.yml index 8ceb306e48..b48e78c74c 100644 --- a/.github/workflows/vale-autofix.yml +++ b/.github/workflows/vale-autofix.yml @@ -10,6 +10,8 @@ on: - '!docs/**/CLAUDE.md' - '!docs/**/SKILL.md' - '!docs/kb/**' + - 'scripts/**' + - 'package.json' concurrency: group: vale-autofix-${{ github.event.pull_request.number }} diff --git a/package.json b/package.json index 76481ea33d..433664fc15 100644 --- a/package.json +++ b/package.json @@ -22,7 +22,7 @@ "kb:dry": "node scripts/copy-kb-to-versions.mjs --dry", "kb:test:aa": "npm run kb:clean && npm run prestart && npm run start", "kb:prodtest:aa": "npm run kb:clean && npm run prebuild && npm run build && npm run serve", - "test:scripts": "bash scripts/test-slugify.sh && bash scripts/test-anchor-update.sh", + "test:scripts": "bash scripts/test-slugify.sh && bash scripts/test-anchor-update.sh && bash scripts/test-md-extension-autofix.sh", "prepare": "husky || true" }, "dependencies": { diff --git a/scripts/vale-autofix.sh b/scripts/vale-autofix.sh index f9dd6d677a..99542a92a3 100755 --- a/scripts/vale-autofix.sh +++ b/scripts/vale-autofix.sh @@ -5,11 +5,14 @@ set -euo pipefail -SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" +# Namespaced (not SCRIPT_DIR) because this file is sourced by +# test-anchor-update.sh, which sets its own SCRIPT_DIR before sourcing — +# a shared name here would silently clobber the caller's. +_VALE_AUTOFIX_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" # --- Shared functions --- -source "$SCRIPT_DIR/lib/slugify.sh" +source "$_VALE_AUTOFIX_DIR/lib/slugify.sh" _get_product_version_folder() { local filepath="$1" From 7c6fef99a90060132d39e3d2dd885b54db057199 Mon Sep 17 00:00:00 2001 From: "james.haytko" Date: Tue, 25 Aug 2026 19:05:22 -0500 Subject: [PATCH 09/36] dataclassification 5.7, 5.6.2, directorymanager 11.1 --- .../addingsource/adding_source.md | 2 +- .../sourcesintro/addingsource/box.md | 5 +- .../addingsource/database/database.md | 17 +-- .../database/database_config_wizard.md | 19 +-- .../addingsource/dropbox_source.md | 10 +- .../addingsource/exchange_mailbox.md | 6 +- .../addingsource/exchange_server.md | 10 +- .../sourcesintro/addingsource/file_system.md | 18 +-- .../sourcesintro/addingsource/google_drive.md | 10 +- .../addingsource/outlook_mail_archive.md | 10 +- .../sourcesintro/addingsource/sharepoint.md | 13 +- .../addingsource/sharepoint_online.md | 6 +- .../sourcesintro/collection_inclusions.md | 2 +- .../dynamic_source_groups_-_exchange.md | 4 +- .../dynamic_source_groups_-_google_drive.md | 4 +- .../dynamic_source_groups_-_sharepoint.md | 2 +- .../sourcegroups/source_groups.md | 12 +- .../sourcesintro/sources_intro.md | 2 +- .../sourcesmanage/config_spo_tenancy.md | 17 +-- .../sourcesintro/sourcesmanage/manage_box.md | 10 +- .../sourcesmanage/manage_database.md | 35 +++-- .../sourcesmanage/manage_dropbox.md | 8 +- .../sourcesmanage/manage_exchange.md | 12 +- .../sourcesmanage/manage_file_system.md | 11 +- .../sourcesmanage/manage_googledrive.md | 16 +- .../manage_configuring_defaults.md | 6 +- ...configuring_subsite_and_list_processing.md | 8 +- .../manage_configuring_tagging.md | 16 +- .../manage_managing_list_of_exclusions.md | 6 +- .../manage_setting_advanced_configuration.md | 8 +- .../managesharepoint/manage_sharepoint.md | 2 +- ...anage_working_with_sharepoint_templates.md | 6 +- .../sourcesmanage/sources_manage.md | 12 +- .../sourcesintro/tagging.md | 5 +- .../sourcesintro/view_content.md | 4 +- .../taxonomiesintro/clues/browse.md | 6 +- .../taxonomiesintro/clues/clue_add.md | 12 +- .../taxonomiesintro/clues/clues.md | 2 +- .../taxonomiesintro/clues/clues_types.md | 56 +++---- .../clues/export_search_results.md | 5 +- .../clues/manageclues/bulk_edit.md | 4 +- .../clues/manageclues/manage_clues.md | 2 +- .../taxonomiesintro/clues/search.md | 4 +- .../taxonomiesintro/other.md | 2 +- .../taxonomiesintro/related.md | 6 +- .../taxonomiesintro/search_index.md | 4 +- .../taxonomiesintro/search_taxonomies.md | 7 +- .../taxonomiesintro/standalone_taxonomies.md | 13 +- .../taxonomiesintro/suggestions.md | 12 +- .../taxonomiesintro/taxonomies_intro.md | 4 +- .../taxonomiesintro/taxonomy_add.md | 2 +- .../taxonomiesintro/taxonomy_manage.md | 20 +-- .../taxonomysettings/labels.md | 11 +- .../multi-user_environments.md | 6 +- .../taxonomysettings/settings_levels.md | 8 +- .../taxonomiesintro/working_set.md | 2 +- .../workflows/actions/actions.md | 4 +- .../actionsbysources/actions_by_sources.md | 2 +- .../advanced_actions_classification.md | 2 +- .../advanced_actions_exchange.md | 2 +- .../advanced_actions_files.md | 4 +- .../mip_workflow_action.md | 2 +- .../advanced_actions_sharepoint.md | 6 +- .../workflows_spa_content_hubs.md | 4 +- .../workflowsemail/workflows_email.md | 4 +- .../advanced_window_migration.md | 8 +- .../workflowsmigration/workflows_migration.md | 14 +- .../workflows/actions/workflows_plugin.md | 2 +- .../managingworkflows/managing_workflows.md | 8 +- .../step_1_select_content_type.md | 6 +- .../step_2_select_automated_action.md | 5 +- .../step_3_specify_conditions.md | 4 +- .../workflows/mip_intro.md | 12 +- .../workflows/workflows.md | 7 +- .../workflows/workflows_run_log.md | 2 +- docs/dataclassification/5.6.2/dashboards.md | 25 ++- .../dataanalysisoverview.md | 2 +- .../dsaroverview/dsar_overview.md | 9 +- .../dsaroverview/dsar_roles.md | 10 +- .../dsaroverview/dsar_searches.md | 10 +- .../dsaroverview/dsar_settings.md | 11 +- .../dsaroverview/dsar_view_search_results.md | 5 +- .../dsaroverview/run_searches.md | 8 +- .../reportingintro/autoclassification.md | 10 +- .../reportingintro/content_distribution.md | 9 +- .../reportingintro/overview_dashboard.md | 13 +- .../report_subscriptions_manage.md | 16 +- .../reportingintro/report_suscriptions.md | 4 +- .../reportingintro/reporting_intro.md | 6 +- .../classification_reports.md | 3 +- .../reportingbuiltin/clue_building_reports.md | 4 +- .../reportingbuiltin/documentation_reports.md | 7 +- .../reportingbuiltin/reporting_built-in.md | 4 +- .../reportingbuiltin/system_reports.md | 10 +- .../reportingbuiltin/top_reports_charts.md | 11 +- .../deployment/appliance/ndc_overview.md | 2 +- .../appliance/nvap_configure_vm_script.md | 10 +- .../appliance/nvap_deploy_hyperv.md | 2 +- .../appliance/nvap_deploy_vmware.md | 4 +- .../deployment/appliance/nvap_overview.md | 4 +- .../appliance/nvap_system_requirments.md | 4 +- .../config_infrastructure_intro.md | 2 +- .../configinfrastructure/config_nfs_fs.md | 9 +- .../config_spo_modern_auth.md | 12 +- .../configinfrastructure/configure_box.md | 12 +- .../configinfrastructure/configure_gdrive.md | 20 ++- .../configureexchange/configure_exchange.md | 11 +- .../create_azureapp_exchangeonline_mfa.md | 10 +- .../mip_configure_infrastructure.md | 4 +- .../datastorages/data_storages.md | 15 +- .../distributed_query_server_mode.md | 21 ++- .../ndcserverclient/ndc_server_client.md | 9 +- .../initialconfig/initial_config_health.md | 6 +- .../initialconfig/initial_config_modes.md | 10 +- .../initialconfig/initial_config_summary.md | 2 +- .../initial_config_taxonomies.md | 2 +- .../initialconfig/initial_config_users.md | 6 +- .../deployment/installation/installation.md | 4 +- .../deployment/installation/ndc_database.md | 15 +- .../deployment/requirements/account_reqs.md | 2 +- .../requirements/hardware_requirements.md | 6 +- .../requirements/software_requirements.md | 15 +- .../requirements/supported_content.md | 2 +- .../5.6.2/deployment/supported_sources.md | 4 +- .../5.6.2/deployment/upgrade.md | 15 +- docs/dataclassification/5.6.2/index.md | 2 +- .../5.6.2/overview/how_it_works.md | 13 +- .../5.6.2/overview/whatsnew.md | 2 +- .../utilities_backup_restore.md | 12 +- .../utilitiescleaner/cleaner_step_2.md | 2 +- .../configuration/config_email.md | 25 ++- .../configuration/config_metadata.md | 13 +- .../configuration/configuration.md | 7 +- .../coreconfiguration/core_administration.md | 14 +- .../coreconfiguration/core_collector.md | 10 +- .../coreconfiguration/core_indexer.md | 4 +- .../coreconfiguration/core_system.md | 2 +- .../coreclassifier/classifier_app.md | 2 +- .../coreclassifier/classifier_engine.md | 6 +- .../coreclassifier/classifier_general.md | 8 +- .../classifier_monitored_content.md | 12 +- .../configuration/language_stemming.md | 55 +++---- .../configuration/redaction.md | 14 +- .../configuration/system_configuration.md | 35 ++--- .../configuration/text_handling.md | 52 +++---- .../users/password_manager.md | 11 +- .../users/secure_ndc.md | 30 ++-- .../users/user_management.md | 48 +++--- .../users/users.md | 8 +- .../users/web_service_security.md | 10 +- .../contentconfigurationoverview.md | 2 +- .../introduction/addsource/addbox.md | 2 +- .../introduction/addsource/addgdsource.md | 10 +- .../addsingledatabase/databaseconfigwizard.md | 13 +- .../introduction/addsource/addsource.md | 4 +- .../introduction/addsource/contentserver.md | 6 +- .../introduction/addsource/exchangemailbox.md | 6 +- .../introduction/addsource/exchangeserver.md | 13 +- .../addsource/outlookmailarchive.md | 4 +- .../introduction/addsource/overview.md | 26 ++-- .../introduction/addsource/overview_1.md | 12 +- .../addsource/sharepointonline.md | 10 +- .../introduction/contentsource.md | 10 +- .../introduction/introduction.md | 2 +- .../introduction/manage/exchangemailbox.md | 16 +- .../manage/introduction/introduction.md | 2 +- .../introduction/managinglistofexclusions.md | 15 +- .../introduction/remoteeventreceivers.md | 5 +- .../manage/introduction/reviewdashboard.md | 2 +- .../settingadvancedconfiguration.md | 10 +- .../manage/introduction/spodefaults.md | 4 +- .../sposubsiteandlistprocessing.md | 17 +-- .../manage/introduction/spotagging.md | 24 +-- .../manage/introduction/workwithtemplates.md | 13 +- .../introduction/manage/manage.md | 16 +- .../introduction/manage/managebox.md | 13 +- .../introduction/manage/managedatabase.md | 27 ++-- .../introduction/manage/managedropbox.md | 6 +- .../introduction/manage/managefilesystem.md | 4 +- .../introduction/manage/managegoogledrive.md | 17 +-- .../introduction/manage/spotenancy.md | 14 +- .../narrowdatacollectionsource.md | 2 +- .../introduction/sourcegroups/exchange.md | 2 +- .../introduction/sourcegroups/googledrive.md | 4 +- .../introduction/sourcegroups/overview.md | 2 +- .../introduction/sourcegroups/sharepoint.md | 2 +- .../introduction/tagging.md | 5 +- .../introduction/viewcontent.md | 6 +- .../taxonomies/add.md | 4 +- .../taxonomies/additionalconfiguration.md | 2 +- .../taxonomies/builtintaxonomies.md | 6 +- .../taxonomies/calculations.md | 4 +- .../taxonomies/clues/addclue.md | 17 +-- .../taxonomies/clues/browse.md | 15 +- .../taxonomies/clues/clues.md | 2 +- .../taxonomies/clues/cluestypes.md | 68 ++++----- .../taxonomies/clues/exportsearchresults.md | 7 +- .../taxonomies/clues/manageclues/bulkedit.md | 8 +- .../clues/manageclues/bulkimport.md | 2 +- .../clues/manageclues/manageclues.md | 2 +- .../taxonomies/clues/search.md | 4 +- .../taxonomies/create.md | 28 ++-- .../taxonomies/enablewriteclassifications.md | 23 ++- .../taxonomies/import.md | 28 ++-- .../taxonomies/introduction.md | 4 +- .../taxonomies/languages/intro_languages.md | 4 +- .../taxonomies/languages/languagesupport.md | 6 +- .../taxonomies/managetaxonomies/manage.md | 36 ++--- .../managetaxonomies/multiuserenvironments.md | 8 +- .../taxonomies/related.md | 8 +- .../taxonomies/searchandfiltertaxonomies.md | 14 +- .../taxonomies/searchindex.md | 6 +- .../taxonomies/settings/globalsettings.md | 4 +- .../taxonomies/settings/settingspanel.md | 6 +- .../taxonomies/settings/termsettings.md | 10 +- .../taxonomies/suggestions.md | 14 +- .../taxonomies/workingset.md | 4 +- .../workflows/actions/actions.md | 5 +- .../availableactions/availableactions.md | 2 +- .../availableactions/classification.md | 5 +- .../actions/availableactions/contentserver.md | 14 +- .../availableactions/createworkflow.md | 53 +++---- .../availableactions/emailalert/emailalert.md | 4 +- .../emailalert/modifyemailalertaction.md | 9 +- .../actions/availableactions/exchange.md | 6 +- .../actions/availableactions/files/files.md | 4 +- .../availableactions/files/modifymiplabels.md | 6 +- .../files/updatepermissions.md | 2 +- .../migratedocument/migratedocument.md | 25 ++- .../migratedocument/migration.md | 14 +- .../migratedocument/migrationdestinations.md | 11 +- .../availableactions/sharepoint/labels.md | 13 +- .../availableactions/sharepoint/sharepoint.md | 8 +- .../sharepoint/spacontenthubs.md | 4 +- .../workflows/actions/plugin.md | 5 +- .../workflows/introduction.md | 6 +- .../addworkflowwizard/addworkflowwizard.md | 2 +- .../step1selectcontenttype.md | 4 +- .../step2selectautomatedaction.md | 5 +- .../step3specifyconditions.md | 17 +-- .../step4setnameandenable.md | 7 +- .../workflows/manage/delete.md | 4 +- .../workflows/manage/editsettings.md | 4 +- .../workflows/manage/manage.md | 8 +- .../workflows/overview.md | 4 +- .../workflows/runlog.md | 2 +- docs/dataclassification/5.7/dashboards.md | 4 +- .../dataanalysisoverview.md | 2 +- .../dsar/crestesearchrequests.md | 7 +- .../5.7/dataanalysisoverview/dsar/overview.md | 8 +- .../5.7/dataanalysisoverview/dsar/roles.md | 6 +- .../5.7/dataanalysisoverview/dsar/searches.md | 2 +- .../5.7/dataanalysisoverview/dsar/settings.md | 8 +- .../dsar/viewsearchresults.md | 6 +- .../builtinreportsoverview.md | 14 +- .../classificationreports.md | 2 +- .../cluebuildingreports.md | 4 +- .../builtinreportsreview/documentreports.md | 6 +- .../builtinreportsreview/systemreports.md | 20 ++- .../builtinreportsreview/topreportscharts.md | 11 +- .../reportingintroduction/capabilities.md | 2 +- .../contentdistributionmap.md | 6 +- .../reportingintroduction/manage.md | 7 +- .../overviewdashboard.md | 23 +-- .../queuedandcustomreports.md | 11 +- .../reportingintroduction.md | 10 +- .../reportsubscriptionsmanage.md | 18 ++- .../reportsuscriptions.md | 4 +- docs/dataclassification/5.7/index.md | 10 +- .../5.7/introduction/deployment/checklist.md | 4 +- .../deployment/clouddeployment.md | 8 +- .../deployment/ndcserverandclient/dqsmode.md | 14 +- .../ndcserverandclient/ndcserverandclient.md | 3 +- ...recoveringencryptionkeyindqsenvironment.md | 8 +- .../deployment/scalabilityandperformance.md | 6 +- .../initialconfiguration/healthalert.md | 3 +- .../initialconfiguration/reviewconfig.md | 2 +- .../initialconfiguration/security.md | 8 +- .../introduction/install/ndcsqldatabase.md | 3 +- .../5.7/introduction/introduction/box.md | 29 ++-- .../introduction/configureinfrastructure.md | 7 +- .../5.7/introduction/introduction/dropbox.md | 2 +- .../exchange/azureappexchangeonlinemfa.md | 17 +-- .../introduction/exchange/exchange.md | 21 +-- .../5.7/introduction/introduction/gdrive.md | 19 ++- .../introduction/introduction/introduction.md | 4 +- .../5.7/introduction/introduction/nfsfs.md | 8 +- .../introduction/spomodernauth.md | 13 +- .../introduction/requirements/accountreqs.md | 6 +- .../requirements/hardwarerequirements.md | 4 +- .../requirements/softwarerequirements.md | 4 +- .../5.7/introduction/supportedsources.md | 2 +- .../5.7/introduction/upgrade.md | 5 +- .../configurevirtualappliance.md | 6 +- .../importvmfromimagetohyperv.md | 2 +- .../importvmfromimagetovmware.md | 4 +- .../introduction/virtualappliance/overview.md | 2 +- .../virtualappliance/systemrequirements.md | 6 +- .../administration/configurationbackup.md | 12 +- .../indexmaintenance/indexmaintenance.md | 6 +- .../administration/indexmaintenance/step1.md | 18 +-- .../administration/indexmaintenance/step2.md | 2 +- .../administration/indexmaintenance/step4.md | 2 +- .../configuration/communicationsettings.md | 18 +-- .../configuration/configmetadata.md | 10 +- .../configuration/configuration.md | 7 +- .../configuration/configurendc.md | 2 +- .../coreconfiguration/administration.md | 8 +- .../classifier/classifier.md | 2 +- .../classifier/conceptclassifier.md | 6 +- .../classifier/generaloptions.md | 4 +- .../coreconfiguration/collector.md | 10 +- .../coreconfiguration/coreconfiguration.md | 6 +- .../coreconfiguration/details.md | 4 +- .../coreconfiguration/indexer.md | 2 +- .../configuration/coreconfiguration/system.md | 4 +- .../configuration/languagestemming.md | 21 +-- .../configuration/redaction.md | 14 +- .../configuration/systemconfiguration.md | 15 +- .../configuration/texthandling.md | 22 ++- .../systemconfigurationoverview/licensing.md | 6 +- .../users/passwordmanager.md | 4 +- .../users/securendc.md | 13 +- .../users/usermanagement.md | 24 ++- .../users/users.md | 4 +- .../users/webservicesecurity.md | 12 +- .../11.1/APIs/commonerrors.md | 6 +- .../11.1/APIs/contactapis/contactapis.md | 2 +- .../11.1/APIs/contactapis/createcontact.md | 2 +- .../11.1/APIs/contactapis/deletecontact.md | 2 +- .../11.1/APIs/contactapis/deletecontacts.md | 4 +- .../11.1/APIs/contactapis/getcontact.md | 2 +- .../11.1/APIs/contactapis/getcontacts.md | 2 +- .../11.1/APIs/contactapis/updatecontact.md | 4 +- .../APIs/datasourceapis/createds/dsexcel.md | 2 +- .../APIs/datasourceapis/createds/dsoracle.md | 2 +- .../APIs/datasourceapis/datasourceapis.md | 6 +- .../11.1/APIs/datasourceapis/deleteds.md | 2 +- .../11.1/APIs/datasourceapis/gefsmdtype.md | 4 +- .../11.1/APIs/datasourceapis/getdstypeid.md | 6 +- .../11.1/APIs/datasourceapis/getdstypename.md | 6 +- .../11.1/APIs/datasourceapis/getfilterds.md | 4 +- .../11.1/APIs/datasourceapis/getfntype.md | 4 +- .../11.1/APIs/datasourceapis/getmdtypest.md | 6 +- docs/directorymanager/11.1/APIs/gettoken.md | 3 +- .../11.1/APIs/groupapis/createsmartgroup.md | 2 +- .../APIs/groupapis/createsmartgroupentraid.md | 4 +- .../11.1/APIs/groupapis/previewmembership.md | 3 +- .../11.1/APIs/groupapis/renewgroup.md | 2 +- .../APIs/jobsapis/createnewjobcollection.md | 2 +- .../11.1/APIs/jobsapis/deletejob.md | 4 +- .../11.1/APIs/jobsapis/getjobcollections.md | 2 +- .../11.1/APIs/jobsapis/jobsapis.md | 6 +- .../11.1/APIs/logsapis/dataservice.md | 4 +- .../11.1/APIs/logsapis/emailservice.md | 2 +- .../11.1/APIs/logsapis/replicationservice.md | 2 +- .../11.1/APIs/logsapis/schedulerservice.md | 2 +- .../11.1/APIs/logsapis/securityservice.md | 2 +- .../11.1/APIs/searchapis/byattribute.md | 2 +- .../11.1/APIs/searchapis/searchapis.md | 2 +- .../11.1/APIs/userapis/createuser.md | 2 +- .../APIs/userapis/getmyexpiringgroupscount.md | 2 +- .../11.1/APIs/userapis/getmysmartgroups.md | 2 +- .../11.1/APIs/userapis/getuser.md | 2 +- .../11.1/APIs/userapis/getusers.md | 2 +- .../11.1/APIs/workflowapis/createroute.md | 4 +- .../11.1/APIs/workflowapis/deleteroute.md | 2 +- .../11.1/APIs/workflowapis/deletewfreq.md | 3 +- .../11.1/APIs/workflowapis/getapprovers.md | 2 +- .../11.1/APIs/workflowapis/getmyreq.md | 2 +- .../workflowapis/getpowerautomatesettings.md | 2 +- .../11.1/APIs/workflowapis/getwfreq.md | 3 +- .../11.1/APIs/workflowapis/getwfroute.md | 2 +- .../admincenter/applications/admincenter.md | 24 ++- .../portal/categories/categories.md | 22 +-- .../applications/portal/categories/custom.md | 6 +- .../portal/categories/dropdownlist.md | 38 ++--- .../applications/portal/categories/grid.md | 42 ++--- .../applications/portal/categories/image.md | 4 +- .../portal/categories/linkedcombo/details.md | 4 +- .../portal/categories/linkedcombo/overview.md | 30 ++-- .../portal/categories/linkedcombo/schema.md | 8 +- .../portal/categories/linkeddropdown.md | 34 ++--- .../portal/categories/multilinetextbox.md | 6 +- .../portal/categories/multivaluedcontrol.md | 46 +++--- .../applications/portal/categories/radio.md | 14 +- .../applications/portal/categories/textbox.md | 24 +-- .../admincenter/applications/portal/create.md | 78 +++++----- .../admincenter/applications/portal/delete.md | 2 +- .../portal/displaytype/badwords.md | 6 +- .../portal/displaytype/createobject.md | 42 ++--- .../portal/displaytype/importexport.md | 4 +- .../portal/displaytype/navigationbar.md | 51 ++++--- .../portal/displaytype/objectcard.md | 34 ++--- .../portal/displaytype/objectlist.md | 6 +- .../portal/displaytype/objectproperties.md | 100 ++++++------ .../displaytype/organizationalhierarchy.md | 8 +- .../portal/displaytype/overview.md | 4 +- .../portal/displaytype/propertyvalidation.md | 28 ++-- .../portal/displaytype/queryattributes.md | 24 +-- .../portal/displaytype/quicksearch.md | 8 +- .../portal/displaytype/searchforms.md | 6 +- .../portal/displaytype/searchresults.md | 8 +- .../portal/displaytype/sendasonbehalf.md | 70 ++++----- .../portal/displaytype/toolbars.md | 12 +- .../applications/portal/overview.md | 6 +- .../applications/portal/server/advanced.md | 22 +-- .../applications/portal/server/general.md | 14 +- .../applications/portal/server/log.md | 20 +-- .../applications/portal/server/nativeiis.md | 12 +- .../applications/portal/server/remoteiis.md | 4 +- .../applications/remoteiisprerequisites.md | 11 +- .../11.1/admincenter/authpolicy/mfa.md | 4 +- .../admincenter/authpolicy/setupauth/email.md | 8 +- .../authpolicy/setupauth/yubikey.md | 2 +- .../11.1/admincenter/authpolicy/sfa.md | 2 +- .../11.1/admincenter/datasource/create.md | 62 ++++---- .../11.1/admincenter/datasource/manage.md | 31 ++-- .../11.1/admincenter/datasource/overview.md | 6 +- .../11.1/admincenter/entitlement/managefs.md | 45 +++--- .../11.1/admincenter/entitlement/managesp.md | 36 ++--- .../11.1/admincenter/entitlement/overview.md | 6 +- .../11.1/admincenter/general/authenticate.md | 22 +-- .../admincenter/general/changepassword.md | 8 +- .../11.1/admincenter/general/concepts.md | 16 +- .../11.1/admincenter/general/dashboard.md | 12 +- .../11.1/admincenter/general/enroll.md | 16 +- .../11.1/admincenter/general/globalpool.md | 6 +- .../11.1/admincenter/general/history.md | 4 +- .../admincenter/general/historyadmincenter.md | 6 +- .../11.1/admincenter/general/licensing.md | 27 ++-- .../11.1/admincenter/general/logs.md | 12 +- .../11.1/admincenter/general/navigation.md | 10 +- .../11.1/admincenter/general/switchaccount.md | 2 +- .../11.1/admincenter/helpdesk/history.md | 14 +- .../helpdesk/operation/asktoenroll.md | 8 +- .../admincenter/helpdesk/operation/export.md | 2 +- .../helpdesk/operation/resetpassword.md | 6 +- .../admincenter/helpdesk/operation/search.md | 12 +- .../helpdesk/operation/unenroll.md | 2 +- .../helpdesk/operation/unlockaccount.md | 8 +- .../11.1/admincenter/helpdesk/overview.md | 2 +- .../admincenter/identitystore/advsentraid.md | 45 +++--- .../identitystore/configure/authtypes.md | 8 +- .../configure/circularreference.md | 8 +- .../configure/dynastysettings.md | 18 +-- .../configure/groupexpirydeletion.md | 8 +- .../identitystore/configure/grouplifecycle.md | 70 ++++----- .../configure/historytracking.md | 24 +-- .../configure/membershiplifecycle.md | 46 +++--- .../configure/messagingprovider.md | 42 ++--- .../identitystore/configure/outofbounds.md | 30 ++-- .../configure/passwordoptions.md | 30 ++-- .../identitystore/configure/ppe/messages.md | 14 +- .../identitystore/configure/ppe/overview.md | 12 +- .../configure/ppe/passphrases.md | 8 +- .../configure/ppe/policyproperties.md | 12 +- .../configure/ppe/rules/characterrules.md | 22 +-- .../configure/ppe/rules/complexityrule.md | 8 +- .../configure/ppe/rules/compromisedrule.md | 2 +- .../configure/ppe/rules/dictionaryrule.md | 16 +- .../configure/ppe/rules/historyrule.md | 12 +- .../configure/ppe/rules/lengthrule.md | 8 +- .../configure/ppe/rules/maximum_age_rule.md | 22 +-- .../configure/ppe/rules/minimum_age_rule.md | 4 +- .../configure/ppe/rules/overview.md | 11 +- .../configure/ppe/rules/patternsrule.md | 14 +- .../configure/ppe/rules/repetitionrule.md | 4 +- .../configure/ppe/rules/similarityrule.md | 4 +- .../configure/ppe/rules/uniquecharacters.md | 4 +- .../configure/ppe/usersgroups.md | 20 +-- .../identitystore/configure/prefixes.md | 18 +-- .../configure/profilevalidation.md | 40 ++--- .../configure/secondwayauthentication.md | 18 +-- .../configure/securityquestions.md | 8 +- .../configure/smsauthentication.md | 6 +- .../identitystore/configure/smtpserver.md | 90 +++++------ .../11.1/admincenter/identitystore/create.md | 20 +-- .../admincenter/identitystore/link/manage.md | 20 +-- .../identitystore/link/overview.md | 32 ++-- .../11.1/admincenter/identitystore/manage.md | 45 +++--- .../admincenter/identitystore/overview.md | 4 +- .../admincenter/identitystore/replication.md | 18 +-- .../admincenter/identitystore/view/details.md | 6 +- .../admincenter/identitystore/view/view.md | 30 ++-- .../admincenter/notification/customize.md | 12 +- .../11.1/admincenter/notification/queue.md | 14 +- .../11.1/admincenter/replication/overview.md | 2 +- .../11.1/admincenter/replication/settings.md | 24 +-- .../11.1/admincenter/schedule/entitlement.md | 15 +- .../admincenter/schedule/entitlementscope.md | 14 +- .../entitlementtemporarypermissions.md | 17 ++- .../admincenter/schedule/grouplifecycle.md | 20 +-- .../admincenter/schedule/groupusageservice.md | 51 ++++--- .../admincenter/schedule/historyretention.md | 28 ++-- .../11.1/admincenter/schedule/manage.md | 71 +++++---- .../schedule/managedbylifecycle.md | 20 +-- .../schedule/membershiplifecycle.md | 18 ++- .../admincenter/schedule/orphangroupupdate.md | 25 ++- .../11.1/admincenter/schedule/overview.md | 8 +- .../11.1/admincenter/schedule/reports.md | 52 +++---- .../admincenter/schedule/schemareplication.md | 26 ++-- .../admincenter/schedule/smartgroupupdate.md | 61 ++++---- .../11.1/admincenter/schedule/synchronize.md | 29 ++-- .../11.1/admincenter/schedule/triggers.md | 30 ++-- .../admincenter/schedule/userlifecycle.md | 14 +- .../schedule/workflowacceleration.md | 23 +-- .../admincenter/securityrole/checkrole.md | 6 +- .../11.1/admincenter/securityrole/create.md | 40 ++--- .../11.1/admincenter/securityrole/criteria.md | 28 ++-- .../11.1/admincenter/securityrole/manage.md | 8 +- .../11.1/admincenter/securityrole/overview.md | 8 +- .../admincenter/securityrole/permissions.md | 16 +- .../securityrole/policy/authentication.md | 10 +- .../securityrole/policy/groupowners.md | 16 +- .../securityrole/policy/helpdesk.md | 144 +++++++++--------- .../policy/membershipobjecttypeenforcement.md | 34 ++--- .../securityrole/policy/newobject.md | 14 +- .../securityrole/policy/password.md | 12 +- .../securityrole/policy/querydesigner.md | 52 +++---- .../admincenter/securityrole/policy/search.md | 8 +- .../securityrole/policy/synchronize.md | 36 ++--- .../admincenter/service/dataservice/create.md | 16 +- .../admincenter/service/dataservice/manage.md | 72 +++++---- .../service/dataservice/overview.md | 8 +- .../11.1/admincenter/service/emailservice.md | 6 +- .../11.1/admincenter/service/overview.md | 8 +- .../admincenter/service/replicationservice.md | 22 ++- .../admincenter/service/schedulerservice.md | 6 +- .../service/securityservice/create.md | 16 +- .../service/securityservice/manage.md | 10 +- .../service/securityservice/overview.md | 7 +- .../service/securityservice/signkeyutility.md | 8 +- .../11.1/admincenter/signin.md | 12 +- .../smsgateway/custom/proxydomain.md | 2 +- .../custom/shortmessage/validate.md | 4 +- .../11.1/admincenter/smsgateway/manage.md | 10 +- .../admincenter/workflow/advancedsettings.md | 6 +- .../workflow/approveracceleration.md | 65 ++++---- .../11.1/admincenter/workflow/overview.md | 24 +-- .../asidentityprovider/metadata.md | 4 +- .../asidentityprovider/register.md | 16 +- .../authenticate/asidentityprovider/signin.md | 5 +- .../adfs/configureadfsindirectorymanager.md | 27 ++-- .../adfs/configurerelayingpartytrust.md | 16 +- .../asserviceprovider/adfs/generateurls.md | 12 +- .../asserviceprovider/adfs/overview.md | 7 +- .../asserviceprovider/adfs/signin.md | 6 +- .../entrasso/configureinentra.md | 8 +- .../configureproviderindirectorymanager.md | 8 +- .../asserviceprovider/entrasso/overview.md | 2 +- .../asserviceprovider/entrasso/signin.md | 8 +- .../asserviceprovider/okta/configureinokta.md | 18 +-- .../okta/configureoktaindirectorymanager.md | 6 +- .../asserviceprovider/okta/signin.md | 5 +- .../onelogin/configureinonelogin.md | 18 +-- .../configureoneloginindirectorymanager.md | 14 +- .../asserviceprovider/onelogin/signin.md | 12 +- .../pingone/configureinpingone.md | 30 ++-- .../configurepingoneindirectorymanager.md | 10 +- .../pingone/generatemetadata.md | 10 +- .../asserviceprovider/pingone/signin.md | 16 +- .../11.1/configureentraid/createuser.md | 8 +- .../configureentraid/register/appregister.md | 8 +- .../credentialprovider/credentialprovider.md | 2 +- .../credentialprovider/installconfigurecp.md | 62 ++++---- .../11.1/install/configure/database.md | 28 ++-- .../11.1/install/configure/gidserver.md | 58 ++++--- .../11.1/install/configure/overview.md | 2 +- .../install/configure/setupauthentication.md | 8 +- .../11.1/install/configure/signingkeyinfo.md | 8 +- .../11.1/install/installer/install.md | 2 +- .../11.1/install/installer/installer.md | 10 +- .../11.1/install/installer/preparationtool.md | 6 +- .../11.1/install/installer/uninstall.md | 16 +- .../11.1/install/installer/whatprepinstall.md | 10 +- .../11.1/install/securityutility.md | 19 +-- .../11.1/install/upgrade/backuprestore.md | 22 +-- .../11.1/install/upgrade/notes.md | 15 +- .../11.1/install/upgrade/overview.md | 2 +- .../managementshell/dynasty/newdynasty.md | 2 +- .../managementshell/dynasty/setdynasty.md | 2 +- .../general/getconnecteduser.md | 2 +- .../general/gettombstoneobject.md | 2 +- .../general/removecontainer.md | 2 +- .../general/sendnotification.md | 2 +- .../managementshell/group/convertgroup.md | 4 +- .../11.1/managementshell/group/movegroup.md | 4 +- .../getavailablemessagingservers.md | 8 +- .../identitystore/getclient.md | 2 +- .../identitystore/getidentitystore.md | 8 +- .../identitystore/getschemaattributes.md | 6 +- .../identitystore/getuserrole.md | 4 +- .../identitystore/newidentitystore.md | 4 +- .../identitystore/sendtestnotification.md | 2 +- .../identitystore/setidentitystore.md | 10 +- .../identitystore/setmessagingserver.md | 2 +- .../connectidentitystore.md | 2 +- .../membership/addgroupmember.md | 2 +- .../managementshell/membership/setobject.md | 2 +- .../11.1/managementshell/overview.md | 30 ++-- .../11.1/managementshell/parameters.md | 128 ++++++++-------- .../managementshell/scheduling/getschedule.md | 4 +- .../managementshell/scheduling/newschedule.md | 2 +- .../managementshell/scheduling/setschedule.md | 2 +- .../managementshell/smartgroup/updategroup.md | 2 +- .../smartgroup/upgradegroup.md | 10 +- .../managementshell/user/getuserenrollment.md | 4 +- .../userlifecycle/terminatedirectreports.md | 4 +- .../userlifecycle/transferdirectreports.md | 4 +- .../directorymanager/11.1/portal/dashboard.md | 7 +- .../11.1/portal/entitlement/fileservers.md | 12 +- .../11.1/portal/entitlement/overview.md | 2 +- .../portal/entitlement/sharepointsites.md | 16 +- .../11.1/portal/generalfeatures/find.md | 22 +-- .../portal/generalfeatures/generalfeatures.md | 6 +- .../11.1/portal/generalfeatures/portal.md | 30 ++-- .../portal/generalfeatures/querysearch.md | 19 ++- .../11.1/portal/generalfeatures/search.md | 39 +++-- .../11.1/portal/generalfeatures/toolbar.md | 12 +- .../11.1/portal/generalfeatures/user.md | 74 ++++----- .../portal/group/allgroups/alldynasties.md | 2 +- .../11.1/portal/group/allgroups/allgroups.md | 8 +- .../portal/group/allgroups/allsmartgroups.md | 2 +- .../portal/group/allgroups/privategroups.md | 2 +- .../portal/group/allgroups/publicgroups.md | 4 +- .../group/allgroups/semiprivategroups.md | 2 +- .../11.1/portal/group/create.md | 6 +- .../11.1/portal/group/create/AD/general.md | 12 +- .../11.1/portal/group/create/AD/group.md | 16 +- .../11.1/portal/group/create/AD/members.md | 8 +- .../11.1/portal/group/create/AD/owners.md | 8 +- .../11.1/portal/group/create/AD/smartgroup.md | 6 +- .../portal/group/create/EntraID/general.md | 4 +- .../11.1/portal/group/create/EntraID/group.md | 14 +- .../11.1/portal/group/create/overview.md | 6 +- .../portal/group/dynasty/AD/createdynasty.md | 26 ++-- .../dynasty/AD/dynastyoptionsmanagerial.md | 24 +-- .../dynasty/AD/dynastyoptionsorggeocus.md | 4 +- .../group/dynasty/EntraID/createdynasty.md | 30 ++-- .../portal/group/dynasty/EntraID/general.md | 6 +- .../11.1/portal/group/dynasty/overview.md | 2 +- .../portal/group/mygroups/mydeletedgroups.md | 2 +- .../11.1/portal/group/mygroups/mydynasties.md | 2 +- .../portal/group/mygroups/myexpiredgroups.md | 4 +- .../portal/group/mygroups/myexpiringgroups.md | 2 +- .../11.1/portal/group/mygroups/mygroups.md | 22 ++- .../portal/group/mygroups/mymemberships.md | 2 +- .../portal/group/mygroups/mysmartgroups.md | 2 +- .../11.1/portal/group/overview.md | 4 +- .../11.1/portal/group/properties/advanced.md | 14 +- .../11.1/portal/group/properties/channels.md | 8 +- .../group/properties/deliveryrestrictions.md | 4 +- .../portal/group/properties/dynastyoptions.md | 62 ++++---- .../11.1/portal/group/properties/email.md | 5 +- .../portal/group/properties/entitlements.md | 8 +- .../11.1/portal/group/properties/general.md | 24 +-- .../11.1/portal/group/properties/history.md | 8 +- .../properties/importadditionalowners.md | 6 +- .../portal/group/properties/importmembers.md | 26 ++-- .../11.1/portal/group/properties/memberof.md | 4 +- .../11.1/portal/group/properties/members.md | 8 +- .../11.1/portal/group/properties/overview.md | 10 +- .../11.1/portal/group/properties/owner.md | 18 +-- .../portal/group/properties/similargroups.md | 2 +- .../portal/group/properties/smartgroup.md | 10 +- .../11.1/portal/group/properties/treeview.md | 4 +- .../portal/group/querydesigner/database.md | 20 +-- .../group/querydesigner/filtercriteria.md | 28 ++-- .../portal/group/querydesigner/general.md | 10 +- .../group/querydesigner/includeexclude.md | 4 +- .../portal/group/querydesigner/overview.md | 14 +- .../querydesigner/passwordexpiryoptions.md | 24 ++- .../11.1/portal/group/querydesigner/script.md | 4 +- .../portal/group/querydesigner/storage.md | 10 +- .../11.1/portal/group/recyclebin/overview.md | 10 +- .../11.1/portal/group/transferownership.md | 8 +- .../group/workingwithgroups/attestation.md | 16 +- .../workingwithgroups/dynastyfunction.md | 6 +- .../workingwithgroups/generalfunction.md | 6 +- .../group/workingwithgroups/groupaccess.md | 6 +- .../group/workingwithgroups/groupdeletion.md | 8 +- .../group/workingwithgroups/groupexpiry.md | 8 +- .../workingwithgroups/groupexpiryfunction.md | 14 +- .../group/workingwithgroups/groupjoinleave.md | 70 ++++----- .../groupmembershipfunction.md | 28 ++-- .../groupownershipfunction.md | 32 ++-- .../group/workingwithgroups/scheduleupdate.md | 13 +- .../workingwithgroups/workingwithgroups.md | 4 +- .../11.1/portal/history/mydirectorygroup.md | 10 +- .../11.1/portal/history/mydirectreport.md | 6 +- .../11.1/portal/history/myhistory.md | 12 +- .../11.1/portal/history/overview.md | 6 +- docs/directorymanager/11.1/portal/login.md | 6 +- .../11.1/portal/reports/dashboard.md | 6 +- .../11.1/portal/reports/generate.md | 10 +- .../11.1/portal/reports/group.md | 18 +-- .../11.1/portal/reports/manage.md | 10 +- .../11.1/portal/reports/user.md | 4 +- .../11.1/portal/request/allrequest.md | 4 +- .../11.1/portal/request/myrequest.md | 2 +- .../11.1/portal/request/overview.md | 20 +-- .../11.1/portal/request/pending.md | 2 +- .../passwordreset.md | 66 ++++---- .../secondfactorauthentication.md | 6 +- .../chooseyourjobcollectiontemplate.md | 8 +- .../portal/synchronize/collection/create.md | 11 +- .../collection/schedulingandnotification.md | 10 +- .../collection/synchronizedjobcollection.md | 16 +- .../create/chooseyourjobtemplate.md | 8 +- .../11.1/portal/synchronize/create/create.md | 16 +- .../portal/synchronize/create/mappingfield.md | 8 +- .../messagingsystemoverview/exchange.md | 8 +- .../messagingsystemoverview/googleapp.md | 14 +- .../messagingsystemoverview.md | 4 +- .../messagingsystemoverview/office365.md | 22 +-- .../create/objectfieldsandmapping.md | 32 ++-- .../create/scheduleandnotification.md | 16 +- .../synchronize/create/selectedfield.md | 20 +-- .../create/sourceanddestination.md | 20 ++- .../portal/synchronize/dtmscript/dtmscript.md | 34 ++--- .../dtmscript/sampletransformscript.md | 2 +- .../dtmscript/visualbasicnetbasic.md | 10 +- .../11.1/portal/synchronize/manage/job.md | 34 ++--- .../synchronize/manage/jobcollection.md | 38 ++--- .../manage/jobcollectiontemplate.md | 24 +-- .../portal/synchronize/manage/jobtemplate.md | 10 +- .../portal/synchronize/manage/schedule.md | 2 +- .../11.1/portal/synchronize/overview.md | 12 +- .../11.1/portal/synchronize/provider.md | 6 +- .../autogenerateuniquepassword.md | 32 ++-- .../synchronize/transformation/overview.md | 4 +- .../11.1/portal/user/create/AD/account.md | 2 +- .../11.1/portal/user/create/AD/contact.md | 6 +- .../11.1/portal/user/create/AD/exchange.md | 6 +- .../11.1/portal/user/create/AD/messaging.md | 8 +- .../11.1/portal/user/create/AD/password.md | 6 +- .../11.1/portal/user/create/AD/user.md | 4 +- .../user/create/EntraID/directoryrole.md | 4 +- .../portal/user/create/EntraID/exchange.md | 10 +- .../portal/user/create/EntraID/mailbox.md | 2 +- .../portal/user/create/EntraID/password.md | 8 +- .../11.1/portal/user/create/overview.md | 2 +- .../11.1/portal/user/linkedaccounts.md | 32 ++-- .../11.1/portal/user/manage/changepassword.md | 14 +- .../11.1/portal/user/manage/directreport.md | 6 +- .../11.1/portal/user/manage/disableduser.md | 6 +- .../11.1/portal/user/manage/resetpassword.md | 10 +- .../11.1/portal/user/manage/unlockaccount.md | 62 ++++---- .../portal/user/manage/validateprofile.md | 14 +- .../11.1/portal/user/manage/viewprofile.md | 4 +- .../11.1/portal/user/overview.md | 6 +- .../user/properties/AD/mailbox/autoreply.md | 8 +- .../user/properties/AD/mailbox/limits.md | 4 +- .../properties/AD/useroverview/account.md | 6 +- .../properties/AD/useroverview/advanced.md | 6 +- .../user/properties/AD/useroverview/email.md | 2 +- .../properties/AD/useroverview/entitlement.md | 4 +- .../properties/AD/useroverview/general.md | 4 +- .../properties/AD/useroverview/memberof.md | 4 +- .../AD/useroverview/organization.md | 14 +- .../user/properties/EntraID/contactinfo.md | 2 +- .../user/properties/EntraID/directoryrole.md | 2 +- .../user/properties/EntraID/identity.md | 6 +- .../11.1/portal/user/properties/overview.md | 2 +- .../11.1/requirements/database.md | 4 +- .../11.1/requirements/hardware.md | 4 +- .../11.1/requirements/overview.md | 2 +- .../permissions/adserviceaccount.md | 20 +-- .../permissions/gmsarequirements.md | 6 +- .../11.1/requirements/sqlcertificate.md | 13 +- .../11.1/ssprportal/navigation.md | 2 +- .../11.1/ssprportal/overview.md | 4 +- 773 files changed, 4577 insertions(+), 4860 deletions(-) diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/adding_source.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/adding_source.md index caf017913b..f1221288de 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/adding_source.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/adding_source.md @@ -16,7 +16,7 @@ To add a content source ![add_source_wizard_thumb_0_0](/images/dataclassification/5.6.2/sources/add_source_wizard_thumb_0_0.webp) -2. Select the source you need and configure its settings. See detailed instructions for the sources: +2. Select the source you need and configure its settings. For detailed instructions, see: - [Box](/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/box.md) - [Add Database Source](/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/database/database.md) diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/box.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/box.md index 13e092fd7a..99593c484b 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/box.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/box.md @@ -9,8 +9,7 @@ sidebar_position: 10 Use the **Box** source configuration window to set up the crawling and classification operations for content stored in a Box Enterprise account. -By default, configuration window displays basic configuration settings only. It is recommended that -you click the "wrench" icon in the bottom left corner to configure advanced settings. +By default, the configuration window displays basic settings only. To configure advanced settings, click the "wrench" icon in the bottom left corner. **NOTE:** To configure advanced settings, your user account may need advanced privileges. [See Users and Security Settings for more information.](/docs/dataclassification/5.6.2/systemconfigurationoverview/users/users.md) @@ -34,7 +33,7 @@ Configure the following: | Email Address | Specify one or more users (email addresses) for impersonated crawling. - If specified explicitly, the crawling engine will impersonate these users when crawling their content as well as shared content where they are the owners. Enter one or several accounts from those listed in the _Managed Users_ on the '_Users and Groups_' tab of the Box console. - If not specified explicitly, the program will automatically create and use an admin user account (_NDC Crawling Account_) for crawling. Remember to provide this app user account with sufficient permissions for the content you want to index (i.e. share access). To share content for crawling with this account, use group membership. | | Re-Index Period | Specifies how often the source should be checked for changes (period in days). Default is **7** days. | | Priority | Set priority for this data source to be crawled. | -| Document Type | Specify a value which can be used to restrict queries when utilizing the Netwrix Data Classification search index. | +| Document Type | Specify a value to restrict queries when using the Netwrix Data Classification search index. | See also: diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/database/database.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/database/database.md index 797e0eec15..5407a8803d 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/database/database.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/database/database.md @@ -6,19 +6,18 @@ sidebar_position: 20 # Add Database Source -The Database source configuration screen allows you to enable the crawling and classification of +Use the Database source configuration screen to enable crawling and classification of content stored in your Microsoft SQL Server, MySQL, and Oracle databases. Content must either be configured / crawled using the configured service accounts (IIS Application Pool User, Windows Services) or by using specific connection details. -Once connected it is possible to create an intelligent content mapping, crawling certain fields as -unstructured index text, and other fields as mapped metadata. For more information please see the +Once connected, you can create an intelligent content mapping, crawling certain fields as +unstructured index text, and other fields as mapped metadata. For more information, see the [Database Configuration Wizard](/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/database/database_config_wizard.md) section. -If you wish to make other configuration changes before collection of the source occurs ensure you -tick the checkbox "_Pause source on creation_". +To make other configuration changes before the initial collection starts, select the **Pause source on creation** checkbox. ![add_database_thumb_0_0](/images/dataclassification/5.6.2/sources/database/add_database_thumb_0_0.webp) @@ -27,10 +26,10 @@ Complete the following fields: | Option | Description | | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Connection Type | Select your connection type: MS SQL, MySQL, or Oracle. | -| Server | Specify the server name of the database system to be crawled ("." can be used to indicate the local server). | -| Database Name | Specify the database that will be crawled. It is possible to configure multiple databases from the same server. | -| Authentication Method | Select authentication method: **Integrated** or **SQL**. - With **Integration** option selected, database will be accessed under the account currently logged on. - With **SQL** option selected, specify user name and password to be used when accessing the database. | -| OCR Processing Mode | Select processing mode for images in the documents: - Disabled – documents' images will not be processed. - Default – defaults to the source settings if configuring a path or the global setting if configured on a source. - Normal – images are processed with normal quality settings. - Enhanced – upscale images further to allow more accurate results. This will provide better accuracy but can lead to longer processing time if the images do not contain text. | +| Server | Specify the server name of the database system to be crawled (use "." to indicate the local server). | +| Database Name | Specify the database that will be crawled. You can configure multiple databases from the same server. | +| Authentication Method | Select authentication method: **Integrated** or **SQL**. - With **Integration** option selected, the database is accessed under the logged-on account. - With **SQL** option selected, specify the user name and password to use when accessing the database. | +| OCR Processing Mode | Select processing mode for images in the documents: - Disabled – documents' images aren't processed. - Default – defaults to the source settings if configuring a path or the global setting if configured on a source. - Normal – images are processed with normal quality settings. - Enhanced – upscale images further to allow more accurate results. This provides better accuracy but can lead to longer processing time if the images don't contain text. | | Source Group | If you want to add database to a source group, select existing, or create a new one. | | Pause source on creation | Select to make other configuration changes before the initial data collection starts. | diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/database/database_config_wizard.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/database/database_config_wizard.md index c9f156f262..42fd8e6494 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/database/database_config_wizard.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/database/database_config_wizard.md @@ -6,10 +6,8 @@ sidebar_position: 10 # Database Configuration Wizard -For the database sources, you can enable security-based crawling, that is, finding sensitive data -(which logically will either be stored in text or binary-based columns). It is possible to create an -intelligent content mapping, crawling certain fields as unstructured index text, and other fields — -as mapped metadata. +For database sources, enable security-based crawling to find sensitive data stored in text or binary-based columns. You can create an +intelligent content mapping, crawling certain fields as unstructured index text, and other fields as mapped metadata. This section explains how to use the Database Configuration Wizard for configuring the crawling process. You can run this wizard when adding the data source, or you can later open the **Source** @@ -33,8 +31,7 @@ strings. ## Tables -On this step, review the grid of the tables in the database that are not currently enabled for -crawling (if already enabled then don't show in this grid) and have at least one text/binary column. +On this step, review the grid of tables in the database that aren't enabled for crawling and have at least one text/binary column. Already-enabled tables don't appear in this grid. Configure your crawling scope considering the following: | Column | Description | @@ -43,7 +40,7 @@ Configure your crawling scope considering the following: | Text Columns | Contains the number of text/binary columns for each table. Click the number link to review the full list. | | Metadata Columns | Contains the number of non-text/binary columns for each table. Click the number link to review the full list. | | Primary Key | Contains the primary key for each table. Review the following Microsoft article for more information on SQL Server primary keys: [Primary Keys Constraints](https://docs.microsoft.com/en-us/sql/relational-databases/tables/primary-and-foreign-key-constraints?view=sql-server-ver15#primary-keys-constraints). | -| Modified Filter | To improve performance the product performs automatic re-indexing against a field in each table that indicates the last modified date of the row. Where possible, the product will automatically map this based upon the exact match or inclusion of one of the below values within the field name. Additional values can be added below in order to support other naming conventions for modified fields (different language or internal convention). | +| Modified Filter | To improve performance the product performs automatic re-indexing against a field in each table that indicates the last modified date of the row. Where possible, the product will automatically map this based upon the exact match or inclusion of one of the below values within the field name. Additional values can be added below to support other naming conventions for modified fields (different language or internal convention). | | Include? | Select if you want to disable crawling for this table. **NOTE:** You can disable crawling for all listed tables using the Include none option in the upper right corner of the wizard or enable crawling accordingly with the Include all. | | View Sample | Shows a table of the top 15 rows allowing to view if the table is one to exclude. | @@ -52,7 +49,7 @@ Configure your crawling scope considering the following: On this step, review tables with missing primary keys and/or missing modified filters. - Missing primary keys – only shows if users have tables that are missing primary keys where the - user can select the primary key from a dropdown of all the columns. This step does not show if + user can select the primary key from a dropdown of all the columns. This step doesn't show if there are no missing primary keys. - Missing modified filters – only shows if there are tables missing modified filters. Here tables are shown that are missing a modified and that have a datetime (or equivalent) typed column to @@ -68,8 +65,8 @@ At this step, review your database configuration. - Excluded Tables – review the full list of the tables to be excluded from classification scope with exclusion reason. -When the database configuration has been completed you will be redirected to the Advanced Source -Configuration, this allows you to define how the database will be crawled. It is possible to crawl -either specific tables, or crawl custom queries (defined select statements, which may use JOIN +When the database configuration is completed, you're redirected to the Advanced Source +Configuration, where you define how the database is crawled. You can crawl +either specific tables or custom queries (defined select statements that may use JOIN statements across multiple tables). [See Database for more information.](/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/manage_database.md) diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/dropbox_source.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/dropbox_source.md index 9b54a71f79..5a7620754b 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/dropbox_source.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/dropbox_source.md @@ -6,10 +6,10 @@ sidebar_position: 30 # Dropbox -The Dropbox source configuration screen allows you to enable the crawling and classification of +Use the Dropbox source configuration screen to enable crawling and classification of content stored in Dropbox cloud storage. -**IMPORTANT!** Make sure you created App for Dropbox crawling before start adding the source. +**IMPORTANT!** Ensure you've created an app for Dropbox crawling before adding the source. [See Configure Dropbox for Crawling for more information.](/docs/dataclassification/5.6.2/deployment/configinfrastructure/config_dropbox.md) ![source_dropbox_thumb_0_0](/images/dataclassification/5.6.2/sources/dropbox/source_dropbox_thumb_0_0.webp) @@ -19,8 +19,8 @@ Complete the following fields: | Option | Description | | ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Access Token | Provide the token you generated when authorizing your App. [See To authorize your app for more information.](/docs/dataclassification/5.6.2/deployment/configinfrastructure/config_dropbox.md) | -| Access Shared Team Folder as: | If you have team folders in your Dropbox namespace and you want to crawl one or more of these folders with Netwrix Data Classification, provide the email address of an account that has access to the desired team folders. For personal folders, this option is not required. For more information, refer to Dropbox [Namespace guide](https://www.dropbox.com/developers/reference/namespace-guide). | -| OCR Processing mode | Select documents' images processing mode: - Disabled – documents' images will not be processed. - Default – defaults to the source settings if configuring a path or the global setting if configured on a source. - Normal – images are processed with normal quality settings. - Enhanced – upscale images further to allow more. | -| Advanced Settings | Click the "wrench" icon in the Settings area (![gdrive_advanced_settings](/images/dataclassification/5.6.2/sources/google_drive/gdrive_advanced_settings.webp)) at the bottom of the screen to expand the following advanced settings: - Re-Index Period — specifies how often the source should be checked for changes. The number specifies the period in days. - Priority — specifies the priority of content source processing in the service queues. - Document Type — can be used to specify a value which can be used to restrict queries when utilizing the core search index. | +| Access Shared Team Folder as: | If you have team folders in your Dropbox namespace and you want to crawl one or more of these folders with Netwrix Data Classification, provide the email address of an account that has access to the team folders you want. For personal folders, this option isn't required. For more information, refer to Dropbox [Namespace guide](https://www.dropbox.com/developers/reference/namespace-guide). | +| OCR Processing mode | Select documents' images processing mode: - Disabled – documents' images will not be processed. - Default – defaults to the source settings if configuring a path or the global setting if configured on a source. - Normal – images are processed with normal quality settings. - Enhanced – upscale images for more accurate results (longer processing time). | +| Advanced Settings | Click the "wrench" icon in the Settings area (![gdrive_advanced_settings](/images/dataclassification/5.6.2/sources/google_drive/gdrive_advanced_settings.webp)) at the bottom of the screen to expand the following advanced settings: - Re-Index Period — specifies how often the source should be checked for changes. The number specifies the period in days. - Priority — specifies the priority of content source processing in the service queues. - Document Type — specify a value to restrict queries when using the core search index. | | Source Group | Netwrix recommends creating a dedicated source group for Dropbox. | | Pause source on creation | Select if you want to make other configuration changes before collection of the source occurs. | diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/exchange_mailbox.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/exchange_mailbox.md index 24289f69e9..9c7923cc25 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/exchange_mailbox.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/exchange_mailbox.md @@ -44,14 +44,14 @@ By default, only basic settings are displayed. To view advanced options, click t | Option | Description | Comments | | ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Basic settings** | | | -| Mailbox | Mailbox to be crawled. | When using impersonation, the settings can be like the following example: - Email Address - administrative account granted Impersonation right, e.g. _administrator@cs.com_ - Mailbox - target mailbox, e.g. _test@cs.com_. | +| Mailbox | Mailbox to be crawled. | When using impersonation, use the following example: - Email Address: administrative account granted Impersonation right, e.g. _administrator@cs.com_ - Mailbox: target mailbox, e.g. _test@cs.com_. | | Crawl Range | Define what portions of data should be retrieved from the Exchange server: - Select **Date Range** to crawl a static set of data within the required interval. - Select **Since** if you want to periodically re-crawl content from the specified date, taking into account the last crawl date for each object. | | | Crawl In-Place Archive | Select this option if you want to crawl Exchange Online in-place archive mailboxes. | Applies to Exchange Online. | -| OCR Processing Mode | Set the processing mode for document images: - **Disabled** - document images will not be processed - **Default** - defaults to the source setting (if configuring a path) or the global setting (if configured on a source) - **Normal** - process the images with normal quality settings - **Enhanced** - upscale the images further to allow more accurate results. | The **Enhanced** mode will provide better accuracy but can lead to longer processing time if the images do not contain text. | +| OCR Processing Mode | Set the processing mode for document images: - **Disabled** - document images aren't processed - **Default** - defaults to the source setting (if configuring a path) or the global setting (if configured on a source) - **Normal** - process the images with normal quality settings - **Enhanced** - upscale the images further to allow more accurate results. | The **Enhanced** mode provides better accuracy but can lead to longer processing time if the images don't contain text. | | Source Group | Select the source group (if any). | | | Pause source on creation | Select if you want to make other configuration changes before data collection occurs. | | | **Advanced settings** | | | | Build Search Index | Select if you want search index to be created. | | | Re-Index Period | Specify how often the source should be checked for changes. Default is **7** days. | Netwrix recommends using default values. | | Priority | Set priority for this data source to be crawled. Select the priority level from the list values: - Highest - High - Normal - Low - Lowest | | -| Document Type | Specify a value which can be used to restrict queries when utilizing the Netwrix Data Classification search index. | | +| Document Type | Specify a value to restrict queries when using the Netwrix Data Classification search index. | | diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/exchange_server.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/exchange_server.md index f27de32ca6..640b386cf9 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/exchange_server.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/exchange_server.md @@ -6,10 +6,10 @@ sidebar_position: 50 # Exchange Server -The Exchange Server source configuration screen allows you to enable the crawling and classification +Use the Exchange Server source configuration screen to enable crawling and classification of multiple Exchange mailboxes from the same Exchange server. -**IMPORTANT!** Automatic detection, crawling and classification of multiple Exchange mailboxes from +**IMPORTANT!** Automatic detection, crawling, and classification of multiple Exchange mailboxes from the same Exchange server (and, respectively, _Exchange Server_ content source configuration) is only supported for Exchange Server 2013 or later due to limitations in the Microsoft APIs. For earlier versions, consider using _Exchange Mailbox_ content source. @@ -25,9 +25,7 @@ To configure an Exchange Server source: ## Authentication type: Modern authentication -**NOTE:** For Email Address / Password, the Administrator account that has been assigned the right -of the Discovery Management role and be given the Mailbox Search and MailboxSearchApplication -permissions. +**NOTE:** For Email Address / Password, use an Administrator account with the Discovery Management role and the Mailbox Search and MailboxSearchApplication permissions. If you plan to use this authentication type, specify the following: @@ -55,7 +53,7 @@ The following settings are also required in both cases: | Option | Description | | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Exchange API URL | By default, the crawling engine will attempt to locate the necessary URL of Exchange Web Services API by using the _Exchange AutoDiscover_ functionality. So, typically, you can leave this field blank. If, however, the _Exchange AutoDiscover_ is not available, then you should specify the Exchange API URL explicitly as follows: `https:///EWS/Exchange.asmx`. | +| Exchange API URL | By default, the crawling engine locates the Exchange Web Services API URL using the _Exchange AutoDiscover_ functionality, so you can typically leave this field blank. If _Exchange AutoDiscover_ is unavailable, specify the Exchange API URL explicitly: `https:///EWS/Exchange.asmx`. | | Crawl Range | Define what portions of data should be retrieved from the Exchange server: - Select **Date Range** to crawl a static set of data within the required interval. - Select **Since** if you want to periodically re-crawl content from the specified date, taking into account the last crawl date for each artifact. | | Match Rules | Define which mailboxes will be crawled as part of an Exchange Server source. Examples: 1. `.*@netwrix.com`— enter the wildcard (\*) and the domain (here `netwrix.com`) to restrict crawling to a set of domain mailboxes 2. `.*`—enter if you want all mailboxes to be crawled | | Detection Period | Specify how often the source should be checked for changes. Default period is 1 day. | diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/file_system.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/file_system.md index 1399a6a1cb..430e92ba94 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/file_system.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/file_system.md @@ -8,7 +8,7 @@ sidebar_position: 60 Use the Source configuration screen to set up the crawling and classification operations for content stored in your file server. Netwrix Data Classification can process individual files or folders. -Select, respectively, **File** or **Folder** at the first screen of the Add content source wizard. +Select, respectively, **File**, or **Folder** at the first screen of the Add content source wizard. ![add_source_wizard_thumb_0_0](/images/dataclassification/5.6.2/sources/add_source_wizard_thumb_0_0.webp) @@ -20,7 +20,7 @@ Use Folder to add the following content sources: - SMB (CIFS) shares - NFS shares -**IMPORTANT!** To add an NFS share, make sure you have configured it for crawling as described in +**IMPORTANT!** To add an NFS share, ensure you've configured it for crawling as described in [Configure NFS File Share for Crawling](/docs/dataclassification/5.6.2/deployment/configinfrastructure/config_nfs_fs.md) By default, configuration window displays basic configuration settings only. To configure advanced @@ -36,19 +36,19 @@ Complete the following fields: | **Basic settings** | | | Folder | Enter the UNC path of the root folder where collection is to start. | | Depth Limit | Specify how many levels the indexing should process. Possible options: - **Exclude Subfolders** - **All Subfolders** (default setting) - **Limit Subfolders** - if selected, specify the required subfolders depth (from 2 to 99) | -| Write classifications | Select if you wish to write classifications directly into the document properties, i.e. use tagging. This applies to DOC/DOCX/XLS/XLSX/PPT/PPTX/PDF. See also [File System](/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/manage_file_system.md). | +| Write classifications | Select if you want to write classifications directly into the document properties, i.e. use tagging. This applies to DOC/DOCX/XLS/XLSX/PPT/PPTX/PDF. See also [File System](/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/manage_file_system.md). | | Source Group | Default value recommended. | | Pause source on creation | Select if you want to make other configuration changes before collection of the source occurs. | | **Advanced settings** | | | Username | Specify the account used to process the folder. | | Password | Provide a password for the account specified above. | | Text Patterns | [See Text Processing for more information.](/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/text_handling.md) | -| Date Filter | Use this calendar control to instruct the program to only crawl the content that has been modified since the specified date. This can be useful for targeting data that is current - in situations where there is a huge volume of content (assuming that the most recent content has the highest risk). | +| Date Filter | Use this calendar control to crawl only content modified since the specified date. This helps prioritize recent data in situations with high content volume, where the most recent content typically carries the highest risk. | | Anonymous Access Allowed | Select this option to disable security filtering for the content source. If cleared, the indexing processes will collect Windows Access Control Lists (ACLs) for the files, and search results will be filtered based upon the end user's Windows identity. | | Duplicate Detection Enabled | Select to exclude duplicates (i.e. documents that contain the same text content) from the index. | -| Re-Index Period | Specifies how often the source should be checked for changes. Netwrix recommends using default values. Default is **7 days**. **NOTE:** Netwrix Data Classification monitors file shares to detect when a document is added/modified. These will then be queued for reprocessing. The source will still be checked for changes based on the re-index period in case any updates are not received. See Manage Sources for more information. | +| Re-Index Period | Specifies how often the source should be checked for changes. Netwrix recommends using default values. Default is **7 days**. **NOTE:** Netwrix Data Classification monitors file shares to detect when a document is added/modified. These are queued for reprocessing. The source is still checked for changes based on the re-index period in case any updates aren't received. See Manage Sources for more information. | | Priority | Netwrix recommends using default values. | -| Document Type | Specify a value that will be used to restrict queries when utilising the search index. | +| Document Type | Specify a value that restricts queries when using the search index. | When finished, click **Save**. @@ -67,15 +67,15 @@ settings, click the "wrench" icon in the bottom left corner. | Option | Description | | ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Basic settings** | | -| File Source | Select how you wish to provide the file location: - **File** - enter file path - **Browse** - browse for the file you need | +| File Source | Select how you want to provide the file location: - **File** - enter file path - **Browse** - browse for the file you need | | Source Group | Default value recommended. | | **Advanced settings** | | | Username | Specify the account used to process the file. | | Password | Provide a password for the account specified above. | | Anonymous Access Allowed | Select this option to disable security filtering for the content source. If cleared, the indexing processes will collect Windows Access Control Lists (ACLs) for the files, and search results will be filtered based upon the end user's Windows identity. | -| Upload | If selected, the file will be uploaded into the NDC SQL database. This will allow the program to present the file to users even if they do not have access to the original file location. | +| Upload | If selected, the file will be uploaded into the NDC SQL database. This will allow the program to present the file to users even if they don't have access to the original file location. | | Text Patterns | [See Text Processing for more information.](/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/text_handling.md) | | Max Collector Retries | Specify how many retries are attempted before automatically removing items from the index when incremental collection indicates that the file has been deleted. Default is **3** retries. | | Re-Index Period | Specifies how often the source should be checked for changes. Netwrix recommends using default values. Default is **7 days**. | | Priority | Netwrix recommends using default values. | -| Document Type | Specify a value that will be used to restrict queries when utilising the search index. | +| Document Type | Specify a value that restricts queries when using the search index. | diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/google_drive.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/google_drive.md index 6560cb66a9..b861fe3068 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/google_drive.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/google_drive.md @@ -6,10 +6,10 @@ sidebar_position: 70 # Google Drive Source -The Google Drive source configuration screen allows you to enable the crawling and classification of +Use the Google Drive source configuration screen to enable crawling and classification of content stored in both G-Suite repositories and Google Drive personal accounts. -**IMPORTANT!** Make sure you created App for GDrive crawling prior to start adding the source. +**IMPORTANT!** Create an app for Google Drive crawling before adding the source. [See Configure G Suite and Google Drive for Crawling for more information.](/docs/dataclassification/5.6.2/deployment/configinfrastructure/configure_gdrive.md) ![add_gdrive_source_thumb_0_0](/images/dataclassification/5.6.2/sources/google_drive/add_gdrive_source_thumb_0_0.webp) @@ -20,13 +20,13 @@ Complete the following fields: | ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Basic settings** | | | Drive Type | Select _Business_. | -| User Email(s) | When adding a G-Suite source, enter the email address of the user's drive that you wish to crawl (via impersonation). | +| User Emails | When adding a G-Suite source, enter the email address of the user's drive that you want to crawl (via impersonation). | | Crawl Shared Items | Select to crawl all files shared with the specified user in addition to any team drives shared with the user. | | Crawl Shared Items | Select to enable crawling of any types of documents shared with the specified user. | | JSON Import | Drag the JSON connection file you downloaded while creating Google service account in the form. | | Project ID | Open the JSON connection file and copy file contents to Project ID field. | -| Write Classifications | Select to enable the writing of classifications back to the Google Drive repository. **NOTE:** Any classifications written to Google Drive are stored in custom properties which are not visible to an end user - they are only accessible via the Google Drive APIs. | +| Write Classifications | Select to enable the writing of classifications back to the Google Drive repository. **NOTE:** Any classifications written to Google Drive are stored in custom properties which aren't visible to end users - they're only accessible via the Google Drive APIs. | | OCR Processing Mode | Select documents' images processing mode: - Disabled – documents' images will not be processed. - Default – defaults to the source settings if configuring a path or the global setting if configured on a source. - Normal – images are processed with normal quality settings. - Enhanced – upscale images further to allow more. | -| Advanced Settings | Click the "wrench" icon in the Settings area (![gdrive_advanced_settings](/images/dataclassification/5.6.2/sources/google_drive/gdrive_advanced_settings.webp)) at the bottom of the screen to expand the following advanced settings: - Re-Index Period — specifies how often the source should be checked for changes. The number specifies the period in days. - Priority — specifies the priority of content source processing in the service queues. - Document Type — can be used to specify a value which can be used to restrict queries when utilizing the core search index. | +| Advanced Settings | Click the "wrench" icon in the Settings area (![gdrive_advanced_settings](/images/dataclassification/5.6.2/sources/google_drive/gdrive_advanced_settings.webp)) at the bottom of the screen to expand the following advanced settings: - Re-Index Period — specifies how often the source should be checked for changes. The number specifies the period in days. - Priority — specifies the priority of content source processing in the service queues. - Document Type — specify a value to restrict queries when using the core search index. | | Source Group | Netwrix recommends creating a dedicated source group for Google Drive. | | Pause source on creation | Select if you want to make other configuration changes before collection of the source occurs. | diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/outlook_mail_archive.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/outlook_mail_archive.md index c92ee90cf2..1855a96d1c 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/outlook_mail_archive.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/outlook_mail_archive.md @@ -6,17 +6,15 @@ sidebar_position: 80 # Outlook Mail Archive -The Outlook Mail Archive source configuration screen allows you to enable the crawling and +Use the Outlook Mail Archive source configuration screen to enable crawling and classification of content stored in PST files: -**NOTE:** If you wish to make other configuration changes before collection of the source occurs -ensure you tick the checkbox Pause source on creation. +**NOTE:** If you want to make other configuration changes before collection of the source occurs, +ensure you select the **Pause source on creation** checkbox. ![add_outlook](/images/dataclassification/5.6.2/sources/exchange_mailbox/add_outlook.webp) -Multiple mailboxes can be added at one time via the "+" button. Collection will process all folders -/ emails / attachments within the mailbox - associating the attachment text with the respective -email. +Add multiple mailboxes at once using the "+" button. Collection processes all folders, emails, and attachments within the mailbox, associating attachment text with the respective email. Select documents' images processing mode: diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/sharepoint.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/sharepoint.md index 7c07cd0f50..5d5e256f53 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/sharepoint.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/sharepoint.md @@ -6,13 +6,12 @@ sidebar_position: 90 # SharePoint -The SharePoint section allows for one or more site collections to be queued for processing that -share the same set of crawling credentials. +The SharePoint section lets you queue one or more site collections for processing with the same crawling credentials. -The following versions of SharePoint are supported: 2010, 2013, 2016, 2019 and SharePoint Online. +The following versions of SharePoint are supported: 2010, 2013, 2016, 2019, and SharePoint Online. -If you wish to make other configuration changes before collection of the source occurs ensure you -tick the checkbox Pause source on creation. +If you want to make other configuration changes before collection of the source occurs, ensure you +select the **Pause source on creation** checkbox. ![addsharepoint](/images/dataclassification/5.6.2/sources/sharepoint/addsharepoint.webp) @@ -24,5 +23,5 @@ Complete the following fields: | Username | Enter username in the following formats: DOMAIN\USERNAME and USERNAME@DOMAIN. | | Write Classifications | Enables synchronization of classifications back to the SharePoint managed metadata fields. The written classifications will be subject to the classification configuration for the site collection. | | OCR Processing Mode | Select documents' images processing mode: - Disabled – documents' images will not be processed. - Default – defaults to the source settings if configuring a path or the global setting if configured on a source. - Normal – images are processed with normal quality settings. - Enhanced – upscale images further to allow more. | -| Re-Index Period | Specifies how often the source should be checked for changes. The number specifies the period in days. **NOTE:** Netwrix Data Classification monitors site collections to detect when a document is added/modified. These will then be queued for reprocessing. The source will still be checked for changes based on the re-index period in case any updates are not received. [See Manage Sources and Control Data Processing for more information.](/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/sources_manage.md) | -| Document Type | Specify a value which can be used to restrict queries when utilizing the Netwrix Data Classification search index. | +| Re-Index Period | Specifies how often the source should be checked for changes. The number specifies the period in days. **NOTE:** Netwrix Data Classification monitors site collections to detect when a document is added/modified. These are queued for reprocessing. The source is checked for changes based on the re-index period in case any updates aren't received. [See Manage Sources and Control Data Processing for more information.](/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/sources_manage.md) | +| Document Type | Specify a value to restrict queries when using the Netwrix Data Classification search index. | diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/sharepoint_online.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/sharepoint_online.md index a36ca148f8..2d9c3c006e 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/sharepoint_online.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/sharepoint_online.md @@ -19,7 +19,7 @@ and others excluded as required. Optionally, it is also possible to set up the resources necessary to ensure Netwrix Data Classification is enabled and configured on the detected OneDrive sites. Templating allows an administrator to pre-configure classification configurations for site collections. For more -information please review the associated templating guide. +information, review the associated templating guide. To crawl the data within SharePoint Online, you need to enable Multi-Factor Authentication: @@ -33,9 +33,9 @@ Complete the following fields: | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | SharePoint URL | - The root of the site collections to be added, by clicking the “(Multiple Urls)” link you can add multiple SharePoint Online Site Collections to be crawled against the same credentials. | | Username | Enter username in the following formats: DOMAIN\USERNAME and USERNAME@DOMAIN. | -| Password | Enter you password for SharePoint Online. | +| Password | Enter your password for SharePoint Online. | | Match Rules | Enter the site collections' path for crawling the documents. At least one match rule must be included. Match rules are regular expressions, for example, https:\/\/example.sharepoint.com\/sites\/. | | Classification template | Specify the required Classification template for writing classifications. See the Enable Write Classifications and [Working with SharePoint templates](/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_working_with_sharepoint_templates.md) topics for more information. | -| Detection Period | Specify how often you will detect new site collections. Default period is 1 day and 0 hour(s). | +| Detection Period | Specify how often you detect new site collections. Default period is 1 day and 0 hours. | After configuring the settings, click the **Save** button. diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/collection_inclusions.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/collection_inclusions.md index bfed0a7eee..595b95e9c9 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/collection_inclusions.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/collection_inclusions.md @@ -9,7 +9,7 @@ sidebar_position: 20 Inclusions and exclusions provide a granular way of limiting collection scope to a specific set of documents within a content source. -This functionality is currently supported for the following source types: +The following source types support inclusions and exclusions: - Exchange - File System diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcegroups/dynamic_source_groups_-_exchange.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcegroups/dynamic_source_groups_-_exchange.md index a350762846..895984d397 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcegroups/dynamic_source_groups_-_exchange.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcegroups/dynamic_source_groups_-_exchange.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Dynamic Source Groups — Exchange -This section contains information on how to configure SharePoint Online dynamic source groups. +This section contains information on how to configure Exchange dynamic source groups. Toggle between Basic and Advanced configuration settings by clicking the icons in the Settings button in the bottom left corner of the page. @@ -16,7 +16,7 @@ The following options can be configured for Exchange Dynamic Source Groups: | Option | Description | | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Authentication Type | Basic — Selecting **Credentials** enables users to authenticate using email address and password credentials Modern (O365) — Selecting **Modern (O365)** enables users to authenticate using Tenant ID | +| Authentication Type | Basic — Selecting **Credentials** lets users authenticate with email address and password credentials. Modern (O365) — Selecting **Modern (O365)** lets users authenticate with Tenant ID. | | Exchange API Url | Enter a URL for an Exchange API for data collection. Leave this field blank to autodetect Exchange APIs. | | Crawl Range | Configure whether to crawl data over a date range or from a specific date onwards. | | Match Rules | At least one match rule must be included, match rules are Regular expressions, such as: - `.*@mydomain.com` - `.*@mydomain.co.uk` | diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcegroups/dynamic_source_groups_-_google_drive.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcegroups/dynamic_source_groups_-_google_drive.md index 6edc8cd17c..d5ddcb6380 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcegroups/dynamic_source_groups_-_google_drive.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcegroups/dynamic_source_groups_-_google_drive.md @@ -12,11 +12,11 @@ the bottom left corner of the page. ![dynamicsourcegroupgd](/images/dataclassification/5.6.2/sources/source_groups/dynamicsourcegroupgd.webp) -The following options can be configured for File Servers Dynamic Source Groups: +The following options can be configured for Google Drive Dynamic Source Groups: | Option | Description | | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Administrator Email | Enter the email for a Google Drive administrator account. The information entered here cannot be edited once the configurations for this dynamic source group are saved. | +| Administrator Email | Enter the email for a Google Drive administrator account. The information entered here can't be edited after you save the configurations for this dynamic source group. | | Crawl Shared Drives | Check the box to enable data collection from shared drives. Uncheck the box to disable this option. | | Crawl User Drives | Check the box to enable data collection from user drives. Uncheck the box to disable this option. | | Match Rules | At least one match rule must be included, match rules are Regular expressions, such as: - `.*\/mySharedDrive.*` | diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcegroups/dynamic_source_groups_-_sharepoint.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcegroups/dynamic_source_groups_-_sharepoint.md index 1521803b54..b68bf066df 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcegroups/dynamic_source_groups_-_sharepoint.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcegroups/dynamic_source_groups_-_sharepoint.md @@ -17,7 +17,7 @@ The following options can be configured for SharePoint Online Dynamic Source Gro | Option | Description | | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | URL | Enter the URL for the SharePoint Online tenant. Entering a tenant here will apply the configurations on the Source Configuration page to all source groups that are created under the tenant. | -| Authentication Type | Credentials — Selecting **Credentials** enables users to authenticate using username and password credentials Modern (O365) — Selecting **Modern (O365)** enables users to authenticate using Tenant ID | +| Authentication Type | Credentials — Selecting **Credentials** lets users authenticate with username and password credentials. Modern (O365) — Selecting **Modern (O365)** lets users authenticate with Tenant ID. | | Match Rules | At least one match rule must be included, match rules are Regular expressions, such as: - `https:\/\/example.sharepoint.com\/sites\/.*` - `.*\/Personal\/.*` - `https:\/\/example-my.sharepoint.com\/.*` | | Classification Template | Search for a Classification Template to apply to Dynamic Source Groups | | Detection Period | The Detection Period set here will apply to all SharePoint Online source groups configured under the URL set in the URL text field. Use the slider to change the Detection Period. To disable detection, set the period to **0** days and **0** hours. | diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcegroups/source_groups.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcegroups/source_groups.md index a902171be0..57b5fcbae3 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcegroups/source_groups.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcegroups/source_groups.md @@ -14,10 +14,10 @@ screen will present the following pop-up: A group can either be "mixed", which allows it to contain all source types, or source specific. In the example above a group would be created entitled "Demo Content", which only supports the addition -of SharePoint sources. If a supporting source group already exists, this can be selected from the -drop-down list provided. [See Dynamic Source Groups for more information.](#dynamic-source-groups) +of SharePoint sources. If a supporting source group already exists, you can select it from the +dropdown list. [See Dynamic Source Groups for more information.](#dynamic-source-groups) -Selecting the cog icon on the main sources grid screen for a source group allows you to amend the +Selecting the cog icon on the main sources grid screen for a source group lets you amend the group settings: ![editgroup](/images/dataclassification/5.6.2/sources/source_groups/editgroup.webp) @@ -41,9 +41,9 @@ Here you can: - _(SharePoint only)_ Supply regular expression rules to support automatically assigning sources to a specific group -Deleting a group will remove all existing items from the group leaving them unassigned. You can also -remove a specific source(s) from a group by selecting the source group in the grid and then -selecting Remove from Group for the required source(s). Source groups can also be created and +Deleting a group removes all existing items from the group, leaving them unassigned. You can also +remove specific sources from a group by selecting the source group in the grid and then +selecting **Remove from Group** for the required sources. Source groups can also be created and assigned as part of the source creation process. ## Dynamic Source Groups diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sources_intro.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sources_intro.md index 89c9d27598..cd225d5d95 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sources_intro.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sources_intro.md @@ -19,7 +19,7 @@ for more information. You can manage the individual content sources or organize them into source groups, which are used as logical containers. -**NOTE:** You can configure the unlimited number of sources to work with. +**NOTE:** You can configure an unlimited number of sources. See next: diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/config_spo_tenancy.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/config_spo_tenancy.md index cb4ad816f0..33724e5216 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/config_spo_tenancy.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/config_spo_tenancy.md @@ -6,20 +6,17 @@ sidebar_position: 80 # Configure the Product to Crawl an Entire SharePoint Online Tenancy -Typically SharePoint environments are crawled on a per site collection basis. Sometimes however -there is a need to crawl an entire SharePoint Online tenancy. The following guide details the -step-by-step instructions in order to configure a whole tenancy for collection. +Typically SharePoint environments are crawled per site collection. Sometimes you need to crawl an entire SharePoint Online tenancy. The following guide details step-by-step instructions for configuring a tenancy for crawling. 1. Add SharePoint Online source as described in the [SharePoint Online](/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/addingsource/sharepoint_online.md) section. - **NOTE:** If this option is not available within the source type selection then it would suggest - that the source type is not currently licensed, please contact support for more details. + **NOTE:** If this option isn't available within the source type selection, it suggests + that the source type isn't licensed. Contact support for details. -2. The Source is configured to the tenancy level, therefore we recommend specifying the URL as the - root site collection URL. This is however not a requirement if you do not have a root site - collection. +2. Configure the Source at the tenancy level. Specify the URL as the root site collection URL if available, + though this isn't required if you don't have a root site collection. 3. Specify an account with tenancy administration rights. Accounts can be specified in either the default AD format _DOMAIN\USERNAME_, or in the format of the user's email address _USERNAME@DOMAIN_. @@ -31,6 +28,6 @@ step-by-step instructions in order to configure a whole tenancy for collection. Business) - `.*`— Identifies any site collections, ensuring that all collections will be crawled -5. Define the required Classification Template, as well as the Detection Period which defines how - often we will detect new site collections +5. Define the required Classification Template and Detection Period, which sets how + often new site collections are detected 6. Select Save. diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/manage_box.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/manage_box.md index 6a4fb298b9..5e09bb0817 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/manage_box.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/manage_box.md @@ -40,14 +40,14 @@ excluded from processing. For that, do the following: 4. To verify exclusion location, enter its path in the **Test Path** field and click **Test**. 5. If needed, you can use metadata conditions to restrict when an exclusion filter should be applied. For that, click **Condition** tab and click **Add**. Then select how the exclusion - conditions will work: it can check if metadata field of the document has any value, is not + conditions work: they check if a metadata field has any value, isn't specified, or matches a specific metadata value. | Criteria | Condition | | ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | Comparison | Compare a value in the document metadata field with the value set by condition. With this criteria selected, you will then need to specify: - **Field name** — document metadata field to check - **Comparison** — operator to use (for example, "does not contain") - **Value** — value to compare against For example, to exclude documents tagged with year 2018, set the condition as follows: - **Field Name** — _DocYear_ - **Comparison** — _equals_ - **Value** — _2018_ | + | Comparison | Compare a value in the document metadata field with the value set by condition. With this criteria selected, you will then need to specify: - **Field name** — document metadata field to check - **Comparison** — operator to use (for example, "doesn't contain") - **Value** — value to compare against For example, to exclude documents tagged with year 2018, set the condition as follows: - **Field Name** — _DocYear_ - **Comparison** — _equals_ - **Value** — _2018_ | | Has any value | Exclude the document if its metadata field has any value. With this criteria selected, specify **Field Name**. | - | Has no values | Exclude the document if metadata field value is not specified. With this criteria selected, specify **Field Name**. | + | Has no values | Exclude the document if metadata field value isn't specified. With this criteria selected, specify **Field Name**. | ![gdrive_exclusion_condition_2_thumb_0_0](/images/dataclassification/5.6.2/sources/gdrive_exclusion_condition_2_thumb_0_0.webp) @@ -58,7 +58,7 @@ excluded from processing. For that, do the following: ## Configure Tagging -To enable the management of metadata for any document type, Box provides the ability to configure +To manage metadata for any document type, Box lets you configure Metadata Templates with collections of attributes (see [this article](https://community.box.com/t5/Organizing-and-Tracking-Content/Using-Metadata/ta-p/30765) for details) ). @@ -92,7 +92,7 @@ To configure tagging | **Field Name** | Defines the attribute name to be used when persisting the classifications (metadata property name). | By default, Classification fields will be used. To use the Metadata Template as well, enter its name and attribute name in the following format: _MetadataTemplateName!!AttributeName_ | | **Single Value Field** | If selected, this option will cause only the highest scoring classification to be written to the field. | | | **Format** | How the classifications should be formatted. | You can create a custom delimited combination of the labels / GUIDs. | -| **Name/ID** or **Class** | Depending on the format, take the term labels, IDs or a combination of both | The corresponding Delimiter must be a string or array type with a maximum length of 3. | +| **Name/ID**, or **Class** | Depending on the format, take the term labels, IDs, or a combination of both | The corresponding Delimiter must be a string or array type with a maximum length of 3. | | **Prefix/** **Suffix** | Will be appended to the formatted string of classifications. | | ![box_tagging_thumb_0_0](/images/dataclassification/5.6.2/sources/box/box_tagging_thumb_0_0.webp) diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/manage_database.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/manage_database.md index 3c145cd58b..1a659e5b2b 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/manage_database.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/manage_database.md @@ -7,12 +7,11 @@ sidebar_position: 20 # Database This section describes how to specify configuration settings for the Database source. You can -specify which tables / views / queries will be crawled, or set up table configuration. Also, you can -use **Write Configuration** options to configure tagging. +specify which tables, views, and queries to crawl, configure table settings, and use **Write Configuration** options to set up tagging. ## Configure tagging -Tagging allows you to write classification taxonomy attributes back to the source database. +Use tagging to write classification taxonomy attributes back to the source database. Each registered taxonomy can be mapped to a property in the database table’s metadata. The program will update a specific column per taxonomy within the source repository with the associated @@ -20,8 +19,8 @@ classifications for a record. You can specify how the classifications should be - Which table should be updated - Which column should be updated -- How to filter the table to ensure that at most only one row will be updated (each update statement - is verified prior to execution in order to ensure that only one row will be updated). +- How to filter the table to ensure only one row is updated (each update statement + is verified before execution to ensure that only one row is updated). These settings are configured in the **Write Configuration** window for the selected entity (table or query). @@ -29,7 +28,7 @@ or query). To configure tagging, do the following: 1. In the **Sources** window, select the required source by clicking on the triple cog icon. -2. Select the entity that you wish to configure tagging for (table or query) and click Edit. +2. Select the entity that you want to configure tagging for (table or query) and click **Edit**. 3. Select **Write Configuration** on the left. Configure tagging options listed below: @@ -51,13 +50,13 @@ You can also specify the following settings: ### Source Configuration -The Source Configuration screen allows you to define which tables / views / queries will be crawled. +Use the Source Configuration screen to define which tables, views, and queries are crawled. The following options are available: - Add Source—Add a new SQL database connection -- Edit Connection—Amend the connection details of the currently selected source -- Add Query—Add a custom method for crawling content (custom SELECT statements), Templates are - provided for Hummingbird, Worksite and Documentum. +- Edit Connection—Edit the connection details of the selected source +- Add Query—Add a custom method for crawling content (custom SELECT statements). Templates are + provided for Hummingbird, Worksite, and Documentum. You can access the Source Configuration screen by selecting the multi-cog (Advanced Configuration) icon from the sources @@ -75,13 +74,13 @@ query, as well as the queries to be used for crawling: ### Primary Key Query -The primary key query should return a set of values that uniquely identify each row to be crawled, -in the event that JOINs are used you should JOIN from the largest dataset to the smallest, to ensure +The primary key query should return a set of values that uniquely identify each row to be crawled. +If JOINs are used, JOIN from the largest dataset to the smallest to ensure that each row is unique. Example: `SELECT PageID FROM Pages` -**NOTE:** Stored procedures are currently not supported. +**NOTE:** Stored procedures aren't supported. ### Content Query @@ -90,7 +89,7 @@ in the primary key query. Example: `SELECT * FROM Pages` -**NOTE:** Stored procedures are currently not supported +**NOTE:** Stored procedures aren't supported Adding the query will take you to the custom query configuration. Here you can update the primary key query and the content query, all other configuration options are described in the Table @@ -100,17 +99,17 @@ Configuration section: ### Table Configuration -The table configuration allows you to choose how each specific entity will be crawled: +Use table configuration to choose how each specific entity is crawled: | Option | Description | | ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Include for Crawling | When checked the table/entity will be enabled in the collection schema. | | Upload Content | When checked the Content fields will be uploaded into the SQL database. Uploaded content can be retrieved after collection by passing the PageId for the record to the QS API call "GetDownload". | -| PK - Primary Key | Please select the fields which uniquely identify the row to be crawled, in the event that multiple rows are returned by the Primary Key, the query will be aborted. Custom queries will not require the primary key to be defined, this will be set automatically from the primary key query. | -| Content | Identifies the fields that will be crawled as searchable text in the core search index. Multiple fields can be mapped to Content, each will be appended with a line break. It is also possible to configure a single binary field type that contains a document, the collection process will load the binary and attempt to convert and extract text from the document. When this functionality is used we recommend setting the ContentFilename or ContentType index mapping to aid the process of text extraction. | +| PK - Primary Key | Select the fields that uniquely identify the row to be crawled. If multiple rows are returned by the Primary Key, the query is aborted. Custom queries don't require the primary key to be defined; it's set automatically from the primary key query. | +| Content | Identifies the fields that are crawled as searchable text in the core search index. Multiple fields can be mapped to Content; each is appended with a line break. You can configure a single binary field type that contains a document; the collection process loads the binary and converts and extracts text from the document. When using this functionality, set the ContentFilename or ContentType index mapping to aid text extraction. | | Metadata | Identifies the fields that will be mapped as metadata values. | | Index Mappings | Index mappings identifies mappings between the entities fields and the internal core database. Each row also contains an information icon identifying its purpose within the crawling process. | | Modified Filter (Incremental Crawls) | This should be set to a field that defines when a row has changed (the modified date for the row). When set the collection process will automatically filter the re-indexing process to rows that have a modified date that is larger than the last crawl time. | -| Re-Index Period | This value is the number of days/hours/minutes that will pass between Re-Indexing. The Re-Indexing process involves querying the table(s) to find new and changed records. | +| Re-Index Period | This value is the number of days, hours, or minutes between re-indexing. The re-indexing process queries the tables to find new and changed records. | ![sqltableconfiguration_thumb_0_0](/images/dataclassification/5.6.2/sources/database/sqltableconfiguration_thumb_0_0.webp) diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/manage_dropbox.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/manage_dropbox.md index 0933353660..d5a3afb067 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/manage_dropbox.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/manage_dropbox.md @@ -27,7 +27,7 @@ To configure exclusions, do the following: 3. Click **Filter** and in the **Filter** field specify the objects (files or folders) to exclude: To exclude a certain file, enter `https://www.dropbox.com/home/`. For - example: _https://www.dropbox.com/home/Reports__/Test Document.docx_ + example: _https://www.dropbox.com/home/Reports/Test Document.docx_ Wildcards can be used anywhere in the exclusion pattern definition as follows: @@ -45,14 +45,14 @@ To configure exclusions, do the following: If needed, you can use metadata conditions to restrict when an exclusion filter should be applied. For that, click **Condition** tab and click **Add**. Then select how the exclusion - conditions will work: it can check if metadata field of the document has any value, is not + conditions work: they check if a metadata field has any value, isn't specified, or matches a specific metadata value. | Criteria | Condition | | ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | Comparison | Compare a value in the document metadata field with the value set by condition. With this criteria selected, you will then need to specify: - **Field name** — document metadata field to check - **Comparison** — operator to use (for example, "does not contain") - **Value** — value to compare against For example, to exclude documents tagged with year 2018, set the condition as follows: - **Field Name** — _DocYear_ - **Comparison** — _equals_ - **Value** — _2018_ | + | Comparison | Compare a value in the document metadata field with the value set by condition. With this criteria selected, specify: - **Field name** — document metadata field to check - **Comparison** — operator to use (for example, "doesn't contain") - **Value** — value to compare against For example, to exclude documents tagged with year 2018, set the condition as: - **Field Name** — _DocYear_ - **Comparison** — _equals_ - **Value** — _2018_ | | Has any value | Exclude the document if its metadata field has any value. With this criteria selected, specify **Field Name**. | - | Has no values | Exclude the document if metadata field value is not specified. With this criteria selected, specify **Field Name**. | + | Has no values | Exclude the document if metadata field value isn't specified. With this criteria selected, specify **Field Name**. | When finished, click **Add**. diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/manage_exchange.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/manage_exchange.md index 675b56da5a..77c2d6488d 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/manage_exchange.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/manage_exchange.md @@ -16,9 +16,9 @@ processing. Do the following: 4. In the **Details** window, on the **Filter** tab enter the name of the entity to exclude. Consider the following: - - If you specify a folder name (e.g. “Drafts”) with no special characters, then any folders with - that specific name will be excluded. Note that adding an exclusion of this type will match any - folders with the name provided, wherever they are within the mailbox. + - If you specify a folder name (e.g. “Drafts”) with no special characters, any folders with + that specific name are excluded. Adding an exclusion of this type matches any + folders with the provided name, wherever they are within the mailbox. - Wrapping the exclusion in wildcard indicators (e.g. “\*Deleted\*”) will match any folder/email with “Deleted” somewhere in the title. @@ -27,14 +27,14 @@ processing. Do the following: 5. If needed, you can use metadata conditions to restrict when an exclusion filter should be applied. For that, click **Condition** tab and click **Add**. Then select how the exclusion - conditions will work: it can check if metadata field of the document has any value, is not + conditions work: they check if a metadata field has any value, isn't specified, or matches a specific metadata value. | Criteria | Condition | | ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | Comparison | Compare a value in the document metadata field with the value set by condition. With this criteria selected, you will then need to specify: - **Field name** — document metadata field to check - **Comparison** — operator to use (for example, "does not contain") - **Value** — value to compare against For example, to exclude documents tagged with year 2018, set the condition as follows: - **Field Name** — _DocYear_ - **Comparison** — _equals_ - **Value** — _2018_ | + | Comparison | Compare a value in the document metadata field with the value set by condition. With this criteria selected, specify: - **Field name** — document metadata field to check - **Comparison** — operator to use (for example, "doesn't contain") - **Value** — value to compare against For example, to exclude documents tagged with year 2018, set the condition as: - **Field Name** — _DocYear_ - **Comparison** — _equals_ - **Value** — _2018_ | | Has any value | Exclude the document if its metadata field has any value. With this criteria selected, specify **Field Name**. | - | Has no values | Exclude the document if metadata field value is not specified. With this criteria selected, specify **Field Name**. | + | Has no values | Exclude the document if metadata field value isn't specified. With this criteria selected, specify **Field Name**. | When finished, click **Add**. diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/manage_file_system.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/manage_file_system.md index 5738a5a5dd..3d8e3663f4 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/manage_file_system.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/manage_file_system.md @@ -11,8 +11,7 @@ and how to configure writing classification attributes back to the content files ## Configure Tagging -You can instruct the program to write classification attributes back to processed files. This -operation is also called "tagging". Tagging is currently supported for the following file types: +You can write classification attributes back to processed files—a process called "tagging". The following file types support tagging: - DOC/DOCX - PPT/PPTX @@ -44,7 +43,7 @@ To configure tagging on a global level | **Enabled** | Use this option to enable / disable tagging with attributes included in this taxonomy. | Cleared by default. | | **Field Name** | Define the attribute name to be used when persisting the classifications (metadata property name). | | | **Format** | How the classifications should be formatted. | You can create a custom delimited combination of the labels / GUIDs. | -| **Name/ID** or **Class** | Depending on the format, take the term labels, IDs or a combination of both | The corresponding Delimiter must be a string or array type, with a maximum length of 3. | +| **Name/ID**, or **Class** | Depending on the format, take the term labels, IDs, or a combination of both | The corresponding Delimiter must be a string or array type, with a maximum length of 3. | | **Prefix/** **Suffix** | Will be appended to the formatted string of classifications. | | Example @@ -117,14 +116,14 @@ You can also configure the list of file locations to exclude from processing. 3. Optionally, enter a test path to verify the settings and click **Test**. 4. If needed, you can use metadata conditions to restrict when an exclusion filter should be applied. For that, click **Condition** tab and click **Add**. Then select how the exclusion - conditions will work: it can check if metadata field of the document has any value, is not + conditions work: they check if a metadata field has any value, isn't specified, or matches a specific metadata value. | Criteria | Condition | | ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | Comparison | Compare a value in the document metadata field with the value set by condition. With this criteria selected, you will then need to specify: - **Field name** — document metadata field to check - **Comparison** — operator to use (for example, "does not contain") - **Value** — value to compare against For example, to exclude documents tagged with year 2018, set the condition as follows: - **Field Name** — _DocYear_ - **Comparison** — _equals_ - **Value** — _2018_ | + | Comparison | Compare a value in the document metadata field with the value set by condition. With this criteria selected, specify: - **Field name** — document metadata field to check - **Comparison** — operator to use (for example, "doesn't contain") - **Value** — value to compare against For example, to exclude documents tagged with year 2018, set the condition as: - **Field Name** — _DocYear_ - **Comparison** — _equals_ - **Value** — _2018_ | | Has any value | Exclude the document if its metadata field has any value. With this criteria selected, specify **Field Name**. | - | Has no values | Exclude the document if metadata field value is not specified. With this criteria selected, specify **Field Name**. | + | Has no values | Exclude the document if metadata field value isn't specified. With this criteria selected, specify **Field Name**. | 5. When finished, click **Add**. 6. Finally, click **Save** and close the window. diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/manage_googledrive.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/manage_googledrive.md index 95fa01b8da..ba3e8ba895 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/manage_googledrive.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/manage_googledrive.md @@ -11,10 +11,10 @@ source. ## Configure Tagging -You can instruct the program to write classification attributes back to to the document properties +You can instruct the program to write classification attributes back to the document properties in the Google Drive repository. Each taxonomy can be mapped to a single property. -**NOTE:** Custom properties are not exposed to end users and are only available to other +**NOTE:** Custom properties aren't exposed to end users and are only available to other applications using the API. By design, Google Drive supports custom properties with the following limitations: @@ -26,7 +26,7 @@ By design, Google Drive supports custom properties with the following limitation **NOTE:** See [this article](https://developers.google.com/drive/api/v3/properties) for details. To overcome these limitations, Google Drive tagging implemented in the solution supports appending a -counter to the field name. So, it is possible to split classifications across multiple fields if a +counter to the field name. You can split classifications across multiple fields if a text limit is hit within the source system. For example, you may have classifications written to the fields “_Agriculture_” and “_Agriculture_1_”. @@ -52,9 +52,9 @@ To configure tagging on a global level | **Enabled** | Use to enable / disables the writing of classifications for the selected taxonomy. | Cleared by default | | **Field Name** | Defines the attribute name to be used when persisting the classifications (metadata property name). | | | **Single Value Field** | If selected, this option will cause only the highest scoring classification to be written to the field. | | -| **Maximum Field** | Specifies the maximum number of properties which can be used to write classifications. Property names will be in the format 'FieldName_X' | This allows more classifications to be written for sources where there is a limit on field length, by writing classifications across multiple properties. | +| **Maximum Field** | Specifies the maximum number of properties to write classifications. Property names are in the format 'FieldName_X' | This lets you write more classifications for sources where there's a limit on field length, by distributing classifications across multiple properties. | | **Format** | How the classifications should be formatted. | You can create a custom delimited combination of the labels / GUIDs. | -| **Name/ID** or **Class** | Depending on the format, take the term labels, IDs or a combination of both | The corresponding Delimiter must be a string or array type with a maximum length of 3. | +| **Name/ID**, or **Class** | Depending on the format, take the term labels, IDs, or a combination of both | The corresponding Delimiter must be a string or array type with a maximum length of 3. | | **Prefix/** **Suffix** | Will be appended to the formatted string of classifications. | | ![googledrivewriteconfiguration_thumb_0_0](/images/dataclassification/5.6.2/sources/google_drive/googledrivewriteconfiguration_thumb_0_0.webp) @@ -86,14 +86,14 @@ _gdrive://corp/Year2020/\*.xlsx_ 3. To verify exclusion location, enter its path in the **Test Path** field and click **Test**. 4. If needed, you can use metadata conditions to restrict when an exclusion filter should be applied. For that, click **Condition** tab and click **Add**. Then select how the exclusion - conditions will work: it can check if metadata field of the document has any value, is not + conditions work: they check if a metadata field has any value, isn't specified, or matches a specific metadata value. | Criteria | Condition | | ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | Comparison | Compare a value in the document metadata field with the value set by condition. With this criteria selected, you will then need to specify: - **Field name** — document metadata field to check - **Comparison** — operator to use (for example, "does not contain") - **Value** — value to compare against For example, to exclude documents tagged with year 2018, set the condition as follows: - **Field Name** — _DocYear_ - **Comparison** — _equals_ - **Value** — _2018_ | + | Comparison | Compare a value in the document metadata field with the value set by condition. With this criteria selected, specify: - **Field name** — document metadata field to check - **Comparison** — operator to use (for example, "doesn't contain") - **Value** — value to compare against For example, to exclude documents tagged with year 2018, set the condition as: - **Field Name** — _DocYear_ - **Comparison** — _equals_ - **Value** — _2018_ | | Has any value | Exclude the document if its metadata field has any value. With this criteria selected, specify **Field Name**. | - | Has no values | Exclude the document if metadata field value is not specified. With this criteria selected, specify **Field Name**. | + | Has no values | Exclude the document if metadata field value isn't specified. With this criteria selected, specify **Field Name**. | ![gdrive_exclusion_condition_2_thumb_0_0](/images/dataclassification/5.6.2/sources/gdrive_exclusion_condition_2_thumb_0_0.webp) diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_configuring_defaults.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_configuring_defaults.md index 749fd7c9fb..f0aa88eeb0 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_configuring_defaults.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_configuring_defaults.md @@ -6,8 +6,8 @@ sidebar_position: 40 # Configuring defaults -The Source Defaults tab allows you to configure defaults that will be used in the absence of list / -subsite configurations. Available options are listed in the table below. +Use the Source Defaults tab to configure defaults that apply when list or +subsite configurations aren't present. Available options are listed below. **NOTE:** To apply the options you set in each section, click the **Save** button in that section. @@ -21,7 +21,7 @@ subsite configurations. Available options are listed in the table below. | Document Date | Assign the internal modified date associated with the document. The selected date will be split into 5 internal fields: _DocYear_, _DocMonth_, _DocDay_, _DocHour_, _DocMins_. | | | Backup Document Date | You can use the dropdown lists to search for and assign fields to the appropriate mappings. | | | **Special Field Mappings** | | | -| The special field mappings allow you to map any of the available SharePoint fields to some of the internal fields for the purposes of search. | | | +| Use the special field mappings to map any available SharePoint fields to internal fields for search purposes. | | | | **Content Field Mappings** | | | | The values configured for each of the default content mappings will be assigned based on the base template of the list (Document Library, Generic List etc). | | | diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_configuring_subsite_and_list_processing.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_configuring_subsite_and_list_processing.md index bf93e2e84a..e4a4e05e2e 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_configuring_subsite_and_list_processing.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_configuring_subsite_and_list_processing.md @@ -15,8 +15,8 @@ the subsites/lists to configure their settings. container is configured for crawling. - The **Has Config?** column contains an indicator showing whether custom metadata mappings have been defined for the entity. -- The **Exclude** link in the last column allows you to exclude the selected list / subsite from - crowling. For excluded entities, this column contains the **Include** link. +- The **Exclude** link in the last column lets you exclude the selected list or subsite from + crawling. For excluded entities, this column contains the **Include** link. **NOTE:** Excluding the entity will not automatically remove content from the index. If content has already been crawled, then it should be manually deleted via the QS; alternatively, you can @@ -24,7 +24,7 @@ re-collect content source data. When new content is defined for crawling (i.e. included), a re-index operation should be performed. -- The **Edit** link allows you to modify settings for the selected list or subsite. See below for +- The **Edit** link lets you modify settings for the selected list or subsite. See below for details. ## List Configuration @@ -52,4 +52,4 @@ Consider the following: - In the absence of a subsite level configuration the collector will automatically use the source level mappings (on a field by field basis). -- Content fields cannot be configured at the subsite level. +- Content fields can't be configured at the subsite level. diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_configuring_tagging.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_configuring_tagging.md index 6b1912efe5..5932ce118f 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_configuring_tagging.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_configuring_tagging.md @@ -17,13 +17,13 @@ Tagging Wizard. To check the prerequisites -1. Make sure you have set up the necessary term sets as described in +1. Ensure you've set up the necessary term sets as described in [this Microsoft article](https://docs.microsoft.com/en-us/sharepoint/set-up-new-term-set). 2. Configure one or more managed metadata columns with the libraries that you plan to apply auto-classification to. See [this Microsoft article](https://support.office.com/en-gb/article/create-a-managed-metadata-column-8fad9e35-a618-4400-b3c7-46f02785d27f) for details. -3. Ensure that the desired term sets are registered as taxonomies within the Netwrix Data +3. Ensure that the term sets you want are registered as taxonomies within the Netwrix Data Classification console. See **Importing Taxonomies - SharePoint** section in Search and Filter Taxonomies for details. 4. Ensure that the appropriate SharePoint product is installed in your SharePoint environment @@ -35,16 +35,16 @@ To check the prerequisites To configure tagging using the wizard -1. Click on the app to start the **SharePoint Tagging wizard**. +1. Click the app to start the **SharePoint Tagging wizard**. ![sharepoint_tagging_wizard_1_thumb_0_0](/images/dataclassification/5.6.2/sources/sharepoint_tagging_wizard_1_thumb_0_0.webp) -2. Configure the Term Sets that you wish to auto-classify. For that, click the **Add** button and - then select the required Term Sets or fields: +2. Configure the Term Sets that you want to auto-classify. Click the **Add** button and + select the required Term Sets or fields: ![sharepoint_tagging_wizard_2_thumb_0_0](/images/dataclassification/5.6.2/sources/sharepoint_tagging_wizard_2_thumb_0_0.webp) -3. If needed, select the specific site/list columns you wish to restrict auto-classification to. +3. If needed, select the specific site/list columns you want to restrict auto-classification to. 4. Confirm the selection. -5. Finally, having configured the desired tagging, you should re-classify the appropriate content — - for the tags to be written back to SharePoint. +5. After configuring the tagging you want, re-classify the appropriate content so the tags + are written back to SharePoint. diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_managing_list_of_exclusions.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_managing_list_of_exclusions.md index c2e26a51ae..60068b4cf4 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_managing_list_of_exclusions.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_managing_list_of_exclusions.md @@ -32,14 +32,14 @@ on the left, and click **Add**. 2. Optionally, enter full exclusion URL to verify the settings and click **Test**. 3. If needed, you can use metadata conditions to restrict when an exclusion filter should be applied. For that, click **Condition** tab and click **Add**. Then select how the exclusion - conditions will work: it can check if metadata field of the document has any value, is not + conditions will work: it can check if metadata field of the document has any value, isn't specified, or matches a specific metadata value. | Criteria | Condition | | ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | Comparison | Compare a value in the document metadata field with the value set by condition. With this criteria selected, you will then need to specify: - **Field name** — document metadata field to check - **Comparison** — operator to use (for example, "does not contain") - **Value** — value to compare against For example, to exclude documents tagged with year 2018, set the condition as follows: - **Field Name** — _DocYear_ - **Comparison** — _equals_ - **Value** — _2018_ | + | Comparison | Compare a value in the document metadata field with the value set by condition. With this criteria selected, you will then need to specify: - **Field name** — document metadata field to check - **Comparison** — operator to use (for example, "doesn't contain") - **Value** — value to compare against For example, to exclude documents tagged with year 2018, set the condition as follows: - **Field Name** — _DocYear_ - **Comparison** — _equals_ - **Value** — _2018_ | | Has any value | Exclude the document if its metadata field has any value. With this criteria selected, specify **Field Name**. | - | Has no values | Exclude the document if metadata field value is not specified. With this criteria selected, specify **Field Name**. | + | Has no values | Exclude the document if metadata field value isn't specified. With this criteria selected, specify **Field Name**. | ![gdrive_exclusion_condition_2_thumb_0_0](/images/dataclassification/5.6.2/sources/gdrive_exclusion_condition_2_thumb_0_0.webp) diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_setting_advanced_configuration.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_setting_advanced_configuration.md index 9cd9a050ff..7d378b302d 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_setting_advanced_configuration.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_setting_advanced_configuration.md @@ -6,7 +6,7 @@ sidebar_position: 20 # Setting advanced configuration -**Advanced SharePoint Configuration** allows you to define which content within the SharePoint site +Use **Advanced SharePoint Configuration** to define which content within the SharePoint site collection will be crawled and to specify metadata mapping settings. To open the Advanced SharePoint Configuration window: @@ -20,7 +20,7 @@ The following option tabs are available: - Include / Exclude an entity (subsite/list) - Define custom metadata mappings per entity (see [Understanding custom metadata mappings](#understanding-custom-metadata-mappings)) -- Source Defaults—Allow you to specify the default custom metadata mapping for the site collection. +- Source Defaults—Use this to specify the default custom metadata mapping for the site collection. - Configuration Viewer—Use this simple XML view to examine the raw configuration. ![sharepointadvancedsourceconfiguration_thumb_0_0](/images/dataclassification/5.6.2/sources/sharepointadvancedsourceconfiguration_thumb_0_0.webp) @@ -32,7 +32,7 @@ fields. There are two types of mapping: - **Content Field Mappings** - The fields which listed as **Content Fields** will be extracted and indexed when the site collection is crawled. -- **Special Field Mappings** (Including _Date_ fields) - These mappings allow you to make use of the +- **Special Field Mappings** (Including _Date_ fields) - These mappings let you use the advanced filtering options available in the core search index. You can map any of the available SharePoint fields to some of the internal fields. For example, you can configure a SharePoint date field to be mapped into the "_Last Modified_" value, allowing results to be retrieved only if they @@ -43,4 +43,4 @@ settings, and finally, the source-level settings. Thus, in the absence of a list configuration, the collector service will automatically use the mappings configured at the subsite level (or global level, if there is no subsite configuration). -Mappings operate on a _Defaults_ basis (described later in this section.) +Mappings operate on a _Defaults_ basis (described in [Understanding custom metadata mappings](#understanding-custom-metadata-mappings).) diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_sharepoint.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_sharepoint.md index 989ef5d847..d3fe21a612 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_sharepoint.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_sharepoint.md @@ -10,7 +10,7 @@ This section contains information on how to configure tagging of your SharePoint site from being processed, define custom configuration to your subsite, and other configuration procedures. -In this article, we will cover: +This article covers: - [Configuring Tagging](/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_configuring_tagging.md) - [Setting advanced configuration](/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_setting_advanced_configuration.md) diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_working_with_sharepoint_templates.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_working_with_sharepoint_templates.md index b3ca270068..5b21a374f5 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_working_with_sharepoint_templates.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_working_with_sharepoint_templates.md @@ -11,7 +11,7 @@ to capture your customizations, so that they can be quickly applied to other Sha and even use the template as the basis for a business solution. In Netwrix Data Classification, you may have site collections and want to use the same tagging -configuration for all of them. It allows you to effectively copy and paste the configuration for one +configuration for all of them. With templates, you can effectively copy and paste the configuration for one source onto others. First you manually configure one source. Then you save that as a template. Then you apply that template to other sources. @@ -19,7 +19,7 @@ To get more details about the tagging function, review the [Configuring Tagging](/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_configuring_tagging.md) article. -In this article, we will cover: +This article covers: - Setting up prerequisites - Using SharePoint API @@ -29,7 +29,7 @@ In this article, we will cover: ## Setting up prerequisites -As part of configuring tagging, make sure you have set the prerequisites, specified in the +As part of configuring tagging, ensure you have set the prerequisites, specified in the [Configuring Tagging](/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/managesharepoint/manage_configuring_tagging.md) article. diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/sources_manage.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/sources_manage.md index 24f432024d..6600d22013 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/sources_manage.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/sourcesmanage/sources_manage.md @@ -8,20 +8,20 @@ sidebar_position: 40 The following commands are available on the **General** tab of the **Sources** section: -- Delete—Removes the source from processing. Its content will not appear in the search results in - due course. +- Delete—Removes the source from processing. Its content will not appear in the search results + immediately. -**NOTE:** This does not delete content from the external system +**NOTE:** This doesn't delete content from the external system - Re-Collect—Queues the source for re-processing. Crawled items will be deleted, and the entire source re-crawled - Re-Index—Queues a source or item to be re-indexed regardless of if the documents were changed or not. You can select Re-Index scope: - - Selected Item(s) and All Descendants — select to Re-Index an Item and child of a child of so + - Selected Items and All Descendants — select to Re-Index an item and child of a child of so forth child element. - - Selected Item(s) and Children — select to Re-Index an Item and its direct child elements. - - Selected Item(s) Only — select to Re-Index only current item and ignore its child elements. + - Selected Items and Children — select to Re-Index an item and its direct child elements. + - Selected Items Only — select to Re-Index only current item and ignore its child elements. - Re-Classify—Queues a source or item to be re-classified against the latest configured classification rules diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/tagging.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/tagging.md index 8adaf95441..9a653bc826 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/tagging.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/tagging.md @@ -10,7 +10,7 @@ sidebar_position: 30 Tagging in Netwrix Data Classification means writing classification attributes back to the content files. Tagging enables external systems (that is, not directly integrated with Netwrix Data -Classification) to leverage the automatically generated classifications for a variety of business +Classification) to use the automatically generated classifications for a variety of business purposes, for example: - Enriching the search experience @@ -32,8 +32,7 @@ Typically, to use tagging, you need to take the following steps: 4. Configure the source-specific settings to map the classifications results back to the source properties, as described in the related section. -**NOTE:** If you are unsure of the correct source specific settings to use, then we recommend -initially working with some sandbox data. +**NOTE:** If you are unsure of the correct source specific settings to use, initially work with some sandbox data. You can **Pause** source processing while you are configuring the correct settings to ensure that no tagging will occur with partial/incorrect configuration settings. diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/view_content.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/view_content.md index fefe81dcea..2030124938 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/view_content.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/sourcesintro/view_content.md @@ -13,11 +13,11 @@ Select the source from the list on the **Sources** - **General** tab, and click ## Content Crawling and Classification Results -Click on a source row in the list of sources on the **General** tab to view the crawled data, +Click a source row in the list of sources on the **General** tab to view the crawled data, including the number of processed documents/URLs (_Documents_ column), the size of the crawled content (_Size_), status, etc. -To browse the whole structure of the crawled content, click on the items in the list. It is also +To browse the whole structure of the crawled content, click the items in the list. It is also possible to filter the list by any field. ![pages_thumb_0_0](/images/dataclassification/5.6.2/sources/pages_thumb_0_0.webp) diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/browse.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/browse.md index 7e0075ac12..bd92d7760e 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/browse.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/browse.md @@ -6,12 +6,12 @@ sidebar_position: 50 # Browse -To view the documents classified for each term, click on the Browse tab. This will display a list of +To view the documents classified for each term, click the Browse tab. This will display a list of documents achieving the minimum score set for classification in the term. [See Classification Rules (Clues) for more information.](/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/clues.md) **NOTE:** This list will include the current classification status of each document and any changes -made to the class, since the last classification, are not taken into account. +made to the class, since the last classification, aren't taken into account. The document text will be highlighted based upon the clues configured for the term. Highlighting will include regular expression matches when configured (Config→Query Server→Enable Regex Browse @@ -24,7 +24,7 @@ You can use the Browse function to: - Identify documents that are receiving a score, but are "missing" being classified because they do not quite reach the terms threshold. For example, changing the mode to "Near Misses <20%" for a - term with a threshold of 50, will find any documents that scored 40 or more, but did not reach the + term with a threshold of 50, will find any documents that scored 40 or more, but didn't reach the threshold. - Identify low scoring documents that are only just reaching the classification threshold. For example, changing the mode to "Low Scoring Documents <20%" for a term with a threshold of 50 diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/clue_add.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/clue_add.md index c172a5ddcc..5bc62fe9d8 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/clue_add.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/clue_add.md @@ -25,7 +25,7 @@ When specifying the clue body, consider exact matching and stemming explained be ### Exact Matching There may be any number of words up to a maximum of 200 characters per clue. However, most clues -will consist of one, two or three words. +will consist of one, two, or three words. Use double quotes around phrases to invoke exact phrase matching. @@ -78,12 +78,12 @@ Higher scores indicate a stronger association with the topic. Consider that clues can also be assigned a negative value, which will prevent incorrect associations. -- Example 3: _Noise pollution_ should not be associated with _Global Warming_. So _Noise pollution_ +- Example 3: _Noise pollution_ shouldn't be associated with _Global Warming_. So _Noise pollution_ would be added with a negative value. ## Mandatory Clues -You can use the Mandatory checkbox to indicate that a clue is required, i.e. a document cannot be +You can use the Mandatory checkbox to indicate that a clue is required, i.e. a document can't be classified against a category unless it matches all of the mandatory clues. The mandatory clue selector is denoted by the \* icon: @@ -99,7 +99,7 @@ user to restrict a clue purely to the current Term Set. ![localclue](/images/dataclassification/5.6.2/taxonomies/localclue.webp) -- Once this option is selected, it will not be possible to amend the clue from any other Term Set +- After this option is selected, it will not be possible to amend the clue from any other Term Set that contains the re-used Term. - If you want to share the Term across all Term Sets again, clear the option from the Term Set in which it was originally enabled. @@ -108,8 +108,8 @@ user to restrict a clue purely to the current Term Set. **NOTE:** The **Synonyms** link is only available for the clues in SQL taxonomies. -The Synonyms link can be used to enter synonym definitions. +Use the Synonyms link to enter synonym definitions. -In general, the use of this facility is not recommended. The preferred approach is to enter each +In general, the use of this facility isn't recommended. The preferred approach is to enter each synonym as separate clues. Entering each synonym as separate clues will generally result in more accurate scoring and therefore to better classification results. diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/clues.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/clues.md index d1a3302477..f45130a4af 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/clues.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/clues.md @@ -23,7 +23,7 @@ the following languages: ![predefined_clues](/images/dataclassification/5.6.2/taxonomies/predefined_clues.webp) -Users can easily extend the out-of-the-box classification rules by adding relevant keywords and +Users can easily extend the predefined classification rules by adding relevant keywords and terms in other languages. In addition, there are predefined classification rules for various national identification and diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/clues_types.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/clues_types.md index 97006262a2..7884fb4450 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/clues_types.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/clues_types.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Types of Clues -The following clue types of clues are available, each clue type is described in detail below: +The following types of clues are available, each is described in detail below: - [Standard Clues](#standard-clues) - [Case-Sensitive Clues](#case-sensitive-clues) @@ -55,7 +55,7 @@ A clue based on document metadata, with matching based on: - Integer Range matches – Such as FIELD > VALUE or FIELD Helpers are provided to format metadata clues, to activate the helper simply select the appropriate -icon for the desired clue type (numeric, date, and basic): +icon for your clue type (numeric, date, and basic): ![metadatacluehelpers](/images/dataclassification/5.6.2/taxonomies/metadatacluehelpers.webp) The date helper supports assisting in the creation of both static and dynamic date clues: @@ -122,15 +122,19 @@ or CSE-FOLDERS=http://www.abc.com/jobs/ -Note that when using cse-Folders with a right-truncated path the path must always end with a slash +:::note +When using cse-Folders with a right-truncated path the path must always end with a slash character. +::: A clue based on selected folders within the path would look like this CSE-FOLDERS=myfolder/myfolder2 -Note that when using cse-Folders with subfolder matches the value must not begin or end with a slash +:::note +When using cse-Folders with subfolder matches the value must not begin or end with a slash character. +::: CSE-FOLDER @@ -140,7 +144,7 @@ CSE-FOLDER=http://www.abc.com/jobs/ matches: http://www.abc.com/jobs/123.txt -does not match: http://www.abc.com/jobs/UK/123.txt +doesn't match: http://www.abc.com/jobs/UK/123.txt CSE-LASTMODIFIEDDATE @@ -252,7 +256,7 @@ This field can be matched using the equal, greater than or less than operators, MODIFIED = 2010-01-01 -MODIFIED MODIFIED > 2010-01-01 +MODIFIED > 2010-01-01 Only the date can be specified, not the time. @@ -260,7 +264,7 @@ Only the date can be specified, not the time. A case-insensitive fuzzy/phonetic phrase match clue. Phonetic clues ignore all non alphanumeric characters. Words that contain no digits are matched using a phonetic algorithm so that words that -sound similar will be matched. Phonetic clues do not use word stemming in the matching process. +sound similar will be matched. Phonetic clues don't use word stemming in the matching process. For example, the following clue: @@ -287,7 +291,7 @@ Definitions of the required syntax for regular expressions can be found in many Microsoft: [Regular Expression Syntax](https://docs.microsoft.com/en-us/previous-versions/visualstudio/visual-studio-2010/ae5bf541(v=vs.100)). -The following example clue matches US Social Security Numbers found anywhere in the document text: +The following example clue matches United States Social Security Numbers found anywhere in the document text: `[/,,/.,/=,\s]((?!000)[0-6]\d{2}|7[0-6]\d|77[0-2])-((?!00)\d{2})-((?!0000)\d{4})[/,,/.,\s]` @@ -302,7 +306,7 @@ This sample clue ensures that: - The first section must be in the range 001 – 772 Any regular expression matches found will be extracted and added to the NDC index automatically. For -example, if we have a document that contains this text: +example, if a document contains this text: Here is one SSN: 407-54-8831 @@ -325,13 +329,13 @@ expression. This is particularly relevant for expressions that may include false social security numbers (simple pattern) or credit card numbers (sample data). The classification engine includes a number of post match validation steps: -- Exclusion Patterns—Provides the ability to exclude a match based upon an exclusion pattern +- Exclusion Patterns—Let you exclude a match based upon an exclusion pattern (exclude sample data etc). Exclusion patterns can be added by selecting the “Exclusions” link. If any exclusion rule is matched the regular expression result will be discarded. **TIP:** Hit count based regular expression clue exclusions — restrict whether a regular expression clue should match based upon the number of unique matches found against the regular - expression. I.E, a regex to match any number against the text: "1 1 1 2 3 4" - has 4 hits, 4 + expression. For example, a regex to match any number against the text: "1 1 1 2 3 4" - has 4 hits, 4 unique numbers. - Validation Checks—Regex validation checks provide a way of reducing false positives returned by @@ -339,26 +343,26 @@ engine includes a number of post match validation steps: - check-digit validations (suitable for credit card numbers, international bank account numbers etc), - - simple pattern-based exclusions to remove test data and values that are not of interest, + - simple pattern-based exclusions to remove test data and values that aren't of interest, - minimum or maximum constraints on both the number of matches and the number of unique matches. - Currently supported checks include: _Mod 97/10_, _Luhn_, _Verhoeff_ + Supported checks include: _Mod 97/10_, _Luhn_, _Verhoeff_ **IMPORTANT!** If any validation check fails, then the regular expression result will be discarded. To add a validation check: -1. Select the Validation Check link for the desired clue +1. Select the Validation Check link for your clue 2. Click Add -3. Select the desired check **Type** from the drop-down list, and specify other settings depending +3. Select your check **Type** from the dropdown list, and specify other settings depending on the type. ![clues_regexp_validationcheck_thumb_0_48](/images/dataclassification/5.6.2/taxonomies/clues_regexp_validationcheck_thumb_0_48.webp) 4. Click Save. -- Proximity Matches—Provides the ability to include/exclude regular expression matches based upon +- Proximity Matches—Let you include/exclude regular expression matches based upon the existence of text before or after the regular expression match. Matches can be added by selecting the “Proximity Matches” link. Matches are processed as follows: @@ -366,13 +370,13 @@ To add a validation check: - If no ‘Include’ matches exist – or, at least one ‘Include’ match passes then the regular expression result will be considered valid -**NOTE:** This functionality is only available when utilising classification Engine v2. The -additional settings are also not currently available in SharePoint Term Sets (but can be linked via +**NOTE:** This functionality is only available when using classification Engine v2. The +additional settings are also not available in SharePoint Term Sets (but can be linked via Term Boosts). ## Required Terms clue -The Required Term clue type can be used to require another class to be classified as a pre-requisite +Use the Required Term clue type to require another class to be classified as a pre-requisite for this class. This is most often used when the children of a class require the parent to also be classified. @@ -386,7 +390,7 @@ A tree view control makes selecting the required class easy: ![requiredterm](/images/dataclassification/5.6.2/taxonomies/requiredterm.webp) -For example, suppose that we have a topic _Pensions_ with two children: +For example, suppose you have a topic _Pensions_ with two children: - Pensions @@ -399,10 +403,10 @@ can simply require documents to be about _Pensions_ by using a Required Class cl ## Term Boost Clues -You use the Term Boost clue type to specify that a Class Score is to be boosted from another term. +Use the Term Boost clue type to specify that a Class Score is to be boosted from another term. This is most often used when a complex class is implemented using several child (or even grandchild) -classes. Basically, you would want to apply these clues to refer to the other term or taxonomy and -review the score for each term, not drilling down to each term. Review the example: +classes. Basically, apply these clues to refer to the other term or taxonomy and +review the score for each term, not exploring deeper into each term. Review the example: ![termboostclue_int_thumb_0_0](/images/dataclassification/5.6.2/taxonomies/termboostclue_int_thumb_0_0.webp) @@ -425,7 +429,7 @@ descendants at once. At classification time if the referenced node or any of its descendants (up to the configured level) reach their threshold then the term boost will be applied. -Select the Exclude Not Available for Tagging check box, if you want to exclude the terms, which are +Select the Exclude Not Available for Tagging checkbox, if you want to exclude the terms, which are not available for tagging. This feature lets you select the grayed-out terms and exclude them for tagging for your taxonomy. For example, you have UK ZIP code, which was tagged as **Available for Tagging** before. It doesn't qualify as sensitive for your Confidential term. Therefore, you can @@ -435,7 +439,7 @@ apply this feature. ## Language Clues -The language clue type can be used to require documents to be written primarily in a specified +Use the language clue type to require documents to be written primarily in a specified language as a filter on classification. For example, if you create a new class and want documents to be classified only if they are written @@ -450,7 +454,7 @@ creating NOT functionality. For example: -If you want to classify any document where a word does NOT exist (such as _Pensions_), you could +If you want to classify any document where a word doesn't exist (such as _Pensions_), you could first add a static clue with a score of 50, and then add a standard clue looking for _Pensions_ with a negative score (-50). diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/export_search_results.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/export_search_results.md index ad73e903b1..75c999e692 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/export_search_results.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/export_search_results.md @@ -11,11 +11,10 @@ options below the search results: ![browsetabexportmodes](/images/dataclassification/5.6.2/taxonomies/browsetabexportmodes.webp) -If there are less than 1000 results, or you wish to have access to the results immediately, you can +If there are less than 1000 results, or you want to have access to the results immediately, you can select the Quick Export option (light icon). -Alternatively the export results will be created in the background, and made available later view -the Queued Reports area. A notification can be sent to an email group upon the completion of report +Alternatively, the background services create the export results and make them available in the Queued Reports area. A notification can be sent to an email group upon the completion of report processing, when selected: ![browsetabexport](/images/dataclassification/5.6.2/taxonomies/browsetabexport.webp) diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/manageclues/bulk_edit.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/manageclues/bulk_edit.md index d984cd5160..c2072ff238 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/manageclues/bulk_edit.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/manageclues/bulk_edit.md @@ -6,11 +6,11 @@ sidebar_position: 10 # Bulk Edit -The Bulk Edit link can be used to make changes to several clues at one time: +Use the Bulk Edit link to make changes to several clues at one time: ![bulkedit](/images/dataclassification/5.6.2/bulkedit.webp) -When this link is used the form changes into a grid editor and many values can be changes and saved +When you use the Bulk Edit link, the form changes into a grid editor and many values can be changed and saved in a single operation. To alter the Mandatory or Is Local settings for all terms quickly simply click the header text to toggle all checkboxes between enabled / disabled. diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/manageclues/manage_clues.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/manageclues/manage_clues.md index e00e223e3c..3882cc86a3 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/manageclues/manage_clues.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/manageclues/manage_clues.md @@ -6,7 +6,7 @@ sidebar_position: 30 # Manage Clues -This section describes how you can edit, import, move and delete clues for the selected taxonomy +This section describes how you can edit, import, move, and delete clues for the selected taxonomy term set. - To delete a clue, select the checkbox next to it and click **Delete**. diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/search.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/search.md index 5454ace535..faba268357 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/search.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/search.md @@ -6,7 +6,7 @@ sidebar_position: 40 # Search Documents by Clue -You can search for documents based on the class clues. For that, click on the name of any single +You can search for documents based on the class clues. For that, click the name of any single clue in the clue list in the management console (or even any suggested clue), go to the **Search** tab and configure search settings. @@ -26,7 +26,7 @@ tab and configure search settings. by quickly examining its usage within the corpus. Consider the following: - The URL filter must end on a folder boundary. - - Use custom filter to specify a number of complex filters: boolean, datetime and numeric. + - Use custom filter to specify a number of complex filters: boolean, datetime, and numeric. **NOTE:** Full description of all filters can be found in the API Reference Guide. You can access it by entering http://localhost/NDC/apidocumentation from your NDC server. If the diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/other.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/other.md index a3f0229ace..dec971c1ae 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/other.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/other.md @@ -15,4 +15,4 @@ additional information: | Info | The Info tab displays the term description (aka Scope Notes) for each preferred term. The Description field is often populated automatically when an external taxonomy is imported automatically using the Scope Notes. | | Logs | All changes made to a term are recorded. The change history may be viewed from the Logs Tab: ![termlogs](/images/dataclassification/5.6.2/taxonomies/termlogs.webp) | | User Edits | When auto-classifications are amended in SharePoint the user edits are recorded in the SQL database, these can later be reviewed to identify terms that require review: ![useredits](/images/dataclassification/5.6.2/taxonomies/useredits.webp) | -| User Suggestions | An optional interface can be enabled to allow users to suggest new terms for the termset hierarchy (http://netwrixdataclassificationserver/conceptQS/Taxonomies/TermSuggest.aspx). Suggestions can trigger automatic notifications to taxonomy administrators, as well as being recorded in the database for later review on the "User Suggestions" tab: ![usersuggestions_thumb_0_0](/images/dataclassification/5.6.2/taxonomies/usersuggestions_thumb_0_0.webp) | +| User Suggestions | An optional interface can be enabled so users can suggest new terms for the termset hierarchy (http://netwrixdataclassificationserver/conceptQS/Taxonomies/TermSuggest.aspx). Suggestions can trigger automatic notifications to taxonomy administrators, as well as being recorded in the database for later review on the "User Suggestions" tab: ![usersuggestions_thumb_0_0](/images/dataclassification/5.6.2/taxonomies/usersuggestions_thumb_0_0.webp) | diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/related.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/related.md index 53f3c33e5c..ef9b140442 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/related.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/related.md @@ -6,11 +6,11 @@ sidebar_position: 100 # Related -The Related tab allows you to view and modify the non-hierarchical relationships between preferred -terms. This tab will only appear if the taxonomy is in SQL, as the SharePoint Term Store does not +Use the Related tab to view and modify the non-hierarchical relationships between preferred +terms. This tab will only appear if the taxonomy is in SQL, as the SharePoint Term Store doesn't support this functionality. ![relatedtermstab](/images/dataclassification/5.6.2/relatedtermstab.webp) When a term is located in multiple branches of the taxonomy (a polyhierarchical taxonomy) – the -Related tab will also display each of the locations to allow you to jump to the specific branch. +Related tab will also display each of the locations so you can jump to the specific branch. diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/search_index.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/search_index.md index a1426894be..0b6ac50f22 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/search_index.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/search_index.md @@ -23,11 +23,11 @@ appear has a great effect on meaning. Nevertheless, the vast majority of retrieval systems available today would regard a document containing all words from a user’s query to be 100% relevant – especially if all of the words are in close proximity. However, this is much too simplistic an approach for effective concept -identification. For example, just because a sentence contains the words “money” and “order” does not +identification. For example, just because a sentence contains the words “money” and “order” doesn't necessarily mean that the topic is about “money orders”. Shannon’s information theory states that the more frequently a sequence appears the less information, or entropy, it contains. Netwrix Data Classification uses this model to compute the -incremental value of compound terms over their lower order components. In this way we are able to +incremental value of compound terms over their lower order components. In this way you can identify the word sequences that convey the most meaning and adjust the standard weightings accordingly. diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/search_taxonomies.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/search_taxonomies.md index d666ddf36d..b1af19f40c 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/search_taxonomies.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/search_taxonomies.md @@ -25,12 +25,11 @@ termset level including: - Reuse Terms - Export CSV -You can also drag-and-drop a node from one location on the tree view to another, once you have -dropped the node you can select to either move, copy, or merge the node(s). +You can also drag-and-drop a node from one location on the tree view to another. After you drop +the node you can select to either move, copy, or merge the nodes. Browser rendering restrictions limits the maximum suitable size per level within the tree view at -10,000 terms. Therefore we recommend that the tree view is structured across multiple branches, both -for performance and usability. Once a branch within the taxonomy reaches 10,000 terms the tree view +10,000 terms. Structure the tree view across multiple branches for performance and usability. When a branch within the taxonomy reaches 10,000 terms the tree view will cap the returned nodes and log a warning to the event logs. Review the following for additional information: diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/standalone_taxonomies.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/standalone_taxonomies.md index 42266a07cf..5c3fedad77 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/standalone_taxonomies.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/standalone_taxonomies.md @@ -6,8 +6,7 @@ sidebar_position: 10 # Built-in Taxonomies Overview -Netwrix Data Classification comes with eight taxonomies with hundreds of classification rules -out-of-the-box. +Netwrix Data Classification comes with eight taxonomies with hundreds of predefined classification rules. The four core taxonomies cover a broad range of sensitive personal, financial, and health-related information. The remaining four taxonomies derive from the core set. They are tailored to meet the @@ -89,7 +88,7 @@ for more information on users' permissions. ### Payment Card Industry Data Security Standard (PCI DSS) -Cardholder data (holder name, card number, expiration and security code) for the major payment +Cardholder data (holder name, card number, expiration, and security code) for the major payment systems: - American Express @@ -101,7 +100,7 @@ systems: - Visa ### Patient Health Information (PHI) -Medical forms, treatment records, prescription drugs, decease names/codes, allergies, social and +Medical forms, treatment records, prescription drugs, decease names/codes, allergies, social, and insurance numbers. ## Derived Taxonomies @@ -179,18 +178,18 @@ information (GDPR Article 9): ### Gramm-Leach-Bliley Act (GLBA) -Combines the Financial Records, PCI DSS and PII (US social security numbers) taxonomies. +Combines the Financial Records, PCI DSS and PII (United States social security numbers) taxonomies. ### Health Insurance Portability and Accountability Act (HIPAA) -Combines the PHI and PII (US social security numbers) taxonomies. +Combines the PHI and PII (United States social security numbers) taxonomies. ## Sensitive and Non-Sensitive Taxonomies While creating your own reports, you can specify whether a taxonomy is sensitive (finance, сredentials) or non-sensitive (file size, language). -**NOTE:** This applies only to customized taxonomies, which you add by yourself. You cannot change +**NOTE:** This applies only to customized taxonomies, which you add by yourself. You can't change the sensitivity settings for the pre-defined taxonomies. To specify sensitive taxonomy: diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/suggestions.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/suggestions.md index 1b6fd037d9..86a7ca0eaf 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/suggestions.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/suggestions.md @@ -6,21 +6,21 @@ sidebar_position: 70 # Suggestions -Clues can be used to statistically produce a list of suggested clues that can be assigned to the +Use clues to statistically produce a list of suggested clues that can be assigned to the term. ![bulkedit](/images/dataclassification/5.6.2/bulkedit.webp) Clues can be suggested for a term via the following methods: -- Suggest Clues for whole term: Click on the Suggest Clues for class link under the class heading to +- Suggest Clues for whole term: Click the Suggest Clues for class link under the class heading to produce a list of suggestions, based on all existing clues in the class. -- Single Clue: Click on the Suggest link against each clue to produce a list of suggestions, based +- Single Clue: Click the Suggest link against each clue to produce a list of suggestions, based on only this clue. -- Class Document: Click on the Suggest link against each class document to produce a list of +- Class Document: Click the Suggest link against each class document to produce a list of suggestions, based on the document. -Once the list of suggested clues has been generated they can be selected and added to the term +When the list of suggested clues has been generated they can be selected and added to the term clues: **NOTE:** Changes made to a class will have no effect unless documents are re-classified. @@ -33,4 +33,4 @@ The clue type can be set to one of the following: - Create Tree Node **NOTE:** If Create Tree Node is selected then these topics shall be added as children of the -currently selected node in the taxonomy structure. +selected node in the taxonomy structure. diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/taxonomies_intro.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/taxonomies_intro.md index 8a2a50cf6a..300c6ed6fd 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/taxonomies_intro.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/taxonomies_intro.md @@ -6,10 +6,10 @@ sidebar_position: 20 # Taxonomies -## What are Taxonomies? +## About Taxonomies Netwrix Data Classification comes with several built-in **taxonomies** with hundreds of -classification rules out-of-the-box. The taxonomies cover a broad range of sensitive personal, +predefined classification rules. The taxonomies cover a broad range of sensitive personal, financial, and health-related information. Each taxonomy contains a set of terms. **Terms** are defined by set of configuration **rules** (also called **clues**). See [Classification Rules (Clues)](/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/clues.md) for diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/taxonomy_add.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/taxonomy_add.md index bdf4e88514..bb1885bdd6 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/taxonomy_add.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/taxonomy_add.md @@ -20,7 +20,7 @@ For the full list of supported taxonomies, refer to 2. Navigate to Loaded Taxonomies, select Add Taxonomies. 3. Select taxonomies that you want to add in the list. - **NOTE:** Multiple taxonomies selection supported. Clicking the search field enables drop-down + **NOTE:** Multiple taxonomies selection supported. Clicking the search field enables dropdown list of default taxonomies. 4. Click Load. diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/taxonomy_manage.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/taxonomy_manage.md index 32296254fa..65d3cdaa05 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/taxonomy_manage.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/taxonomy_manage.md @@ -40,15 +40,15 @@ import options: collection specified, as well as the termstore (preferably as a term store administrator). - Upload—Imports an XML file directly into the SQL database, large taxonomies will be imported by the background services. -- Load—Certain taxonomies are provided out-of-the-box these can be fully used as part of the product +- Load—Certain predefined taxonomies can be fully used as part of the product or simply used as a reference for regular expression and metadata clues. ![addtaxonomies](/images/dataclassification/5.6.2/taxonomies/addtaxonomies.webp) ## Merging SQL Taxonomies -SQL taxonomies also be easily merged / updated from the Global Settings page. Select the Update link -for the taxonomy that you wish to update to load the taxonomy merge wizard: +SQL taxonomies can be easily merged / updated from the Global Settings page. Select the Update link +for the taxonomy that you want to update to load the taxonomy merge wizard: ![mergesqltaxonomyupdatelink](/images/dataclassification/5.6.2/taxonomies/mergesqltaxonomyupdatelink.webp) @@ -69,12 +69,12 @@ update is available (post upgrade): ![mergesqltaxonomypredefinedindicator](/images/dataclassification/5.6.2/taxonomies/mergesqltaxonomypredefinedindicator.webp) **NOTE:** The merge operation relies on matching the source definition to the destination -definition - utilising the Term Id (GUID). If there are no matching ids then the merge operation +definition using the Term Id (GUID). If there are no matching ids then the merge operation will be automatically stopped. In this case the taxonomy should be deleted - and re-imported. ## Merging SharePoint Taxonomies -SharePoint taxonomies can be merged with the use of the TermStoreManager tool (please see the +SharePoint taxonomies can be merged with the use of the TermStoreManager tool (see the associated user guide available via documentation downloads). ## Backing up/Deletinge Taxonomies @@ -106,8 +106,8 @@ Do the following: ## Bulking Updates -The taxonomy update wizard allows large repetitive changes to be made to taxonomies in bulk. The -wizard can be used to: +The taxonomy update wizard allows large repetitive changes to be made to taxonomies in bulk. Use the +wizard to: - Add Clues—Create a default standard clue, a default metadata clue, or simply define the clue template to be used. @@ -121,10 +121,10 @@ scoped to a particular branch by right-clicking the top node of the intended bra ![bulkupdatetreeview](/images/dataclassification/5.6.2/taxonomies/bulkupdatetreeview.webp) -The wizard will then walk you through performing the update. Each update will allow you to restrict +The wizard will then walk you through performing the update. With each update you can restrict the scope of your change by specifying: -- Filters—filters for which terms/clues you wish to update (based on score, clue text, etc). +- Filters—filters for which terms/clues you want to update (based on score, clue text, etc). - Descendants Limit—specify how many levels down the update should process within the tree. - Exclusions—specific terms to exclude from the update. @@ -144,7 +144,7 @@ required term set and click the **Term Management** tab on the right. ![term_management_thumb_0_0](/images/dataclassification/5.6.2/taxonomies/term_management_thumb_0_0.webp) -Then you can work with the tabs you need, including Search, Browse and Working Set tabs. +Then you can work with the tabs you need, including Search, Browse, and Working Set tabs. Review the following for additional information: diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/taxonomysettings/labels.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/taxonomysettings/labels.md index 037a037afe..070e3201f6 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/taxonomysettings/labels.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/taxonomysettings/labels.md @@ -11,13 +11,12 @@ This section contains information on how to configure SharePoint and Office 365 ## SharePoint Labels SharePoint labels (Alternate Term Labels) are alternate labels configured in SharePoint against the -English language. Through the administration interface it is possible to add and remove alternate -labels. It is not currently possible to change the default label (this should be achieved by -renaming the node via the treeview right click menu). +English language. Through the administration interface you can add and remove alternate +labels. You can't change the default label directly (rename the node via the treeview right click menu). ## O365 Labels -For a simple automated experience it is possible to assign Office 365 Classification labels to +For a simple automated experience, assign Office 365 Classification labels to existing Term Set structures within Taxonomy Manager. At the time of classification the classification process will identify any terms that have both met @@ -29,7 +28,7 @@ setting specified at the term level). More than one label can be applied to each term to allow for labels to be applied that are only available on a limited set of site collections. -Simply select Add and choose the label you wish to assign from the drop down list: +Simply select Add and choose the label you want to assign from the dropdown list: ![o365labels_thumb_0_0](/images/dataclassification/5.6.2/taxonomies/o365labels_thumb_0_0.webp) @@ -38,5 +37,5 @@ synchronized down. ## Help -The Help tab displays a list of clue type information, as well as allows you to run the product tour +The Help tab displays a list of clue type information, as well as runs the product tour specific to the Taxonomies area. diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/taxonomysettings/multi-user_environments.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/taxonomysettings/multi-user_environments.md index 7599f3e8f6..b83aad3f68 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/taxonomysettings/multi-user_environments.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/taxonomysettings/multi-user_environments.md @@ -7,14 +7,14 @@ sidebar_position: 30 # Multi-User Environments When several users are maintaining the taxonomy structure simultaneously there is a need to prevent -concurrent access to individual classes so that one user’s work is not overwritten by another user +concurrent access to individual classes so that one user’s work isn’t overwritten by another user working in the same area of the taxonomy. -In order to allow multiple users to work simultaneously we provide a locking facility that allows +To allow multiple users to work simultaneously, use a locking facility that allows each user to reserve one or more classes for private editing. When they have finished a batch of work then they can unlock the classes to release. -In order to enable this facility the administrator should “Enable User Locking” under Config → Core +To enable this facility, the administrator should “Enable User Locking” under Config → Core → Query Server. The administrator should also ensure that Anonymous Access is disabled for the administration web diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/taxonomysettings/settings_levels.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/taxonomysettings/settings_levels.md index 538f40bbd0..ad9f348c98 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/taxonomysettings/settings_levels.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/taxonomysettings/settings_levels.md @@ -20,12 +20,12 @@ level taxonomy settings as well as global settings applicable to the Taxonomies | Option | Description | | --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Content Filters | This field allows the taxonomy to be restricted based on a booleanfilter (e.g. using the “CSE-FOLDERS” field) or any of the 8 document id filters. See the associated design guide for more information about the ContentFilter field in the Taxonomies table. Valid entries include: - cse-folders= http://www.bbc.co.uk/sport/(only process documents from this path) - NOT cse-folders=http://www.bbc.co.uk/sport/ (exclude documents from this path) - Author=Truman Capote (only process documents by this author) - 2 (only process documents with this DocumentID value) - 3,77,890 (only process documents with one of these DocumentID4 values) Note that any number of entries can be combined by concatenation into a single string. Multiple restrictions of the same type are ORed together, so if multiple “cse-folders” entries exist then the document will pass if it matches any one of them. Multiple restrictions of different types are ANDed together, so if multiple types exist then the document must pass all of them in order to get classified. | +| Content Filters | This field allows the taxonomy to be restricted based on a booleanfilter (e.g. using the “CSE-FOLDERS” field) or any of the 8 document id filters. See the associated design guide for more information about the ContentFilter field in the Taxonomies table. Valid entries include: - cse-folders= http://www.bbc.co.uk/sport/(only process documents from this path) - NOT cse-folders=http://www.bbc.co.uk/sport/ (exclude documents from this path) - Author=Truman Capote (only process documents by this author) - 2 (only process documents with this DocumentID value) - 3,77,890 (only process documents with one of these DocumentID4 values) Any number of entries can be combined by concatenation into a single string. Multiple restrictions of the same type are ORed together, so if multiple “cse-folders” entries exist then the document will pass if it matches any one of them. Multiple restrictions of different types are ANDed together, so if multiple types exist then the document must pass all of them to get classified. | | Max Categories | Sets the maximum number of classes from this taxonomy that will be allocated to each document. To set the Max Categories value across all taxonomies use the Settings tab in Index Manager. | -| Default Threshold | Sets the default threshold for newly created terms within the selected taxonomy (does not affect existing terms). | +| Default Threshold | Sets the default threshold for newly created terms within the selected taxonomy (doesn't affect existing terms). | | Create Default Clues | This setting controls the creation of default clues when. If enabled then a default clue is added to all Classes based on the title of the class – or, optionally based on the default metadata clue format. | | Default Clue Score | Sets the default score value for new clues. | -| Default Metadata Clue | Specifies the format of a default metadata clue. This can be used to create automatic “self-referential” clues, as well as static assignments based on the term name in the document metadata. “[TermName]” can be utilised for a dynamic lookup of the classes name. | +| Default Metadata Clue | Specifies the format of a default metadata clue. Use this to create automatic “self-referential” clues, as well as static assignments based on the term name in the document metadata. “[TermName]” enables a dynamic lookup of the classes name. | | Count Mode | Sets the display mode for counts in the treeview. | | Show Empty Nodes | Sets the display mode for empty nodes in the treeview. | | Synchronise Termset | Enables/Disables automatic synchronisation through the TermStoreManager tool for the whole Term Set. | @@ -42,4 +42,4 @@ selected term: | Available for Tagging | Use to prevent any documents getting classified against a class. This would normally only be set to “No” when a class is being used to boost another class – see [Term Boost Clues](/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/clues/clues_types.md#term-boost-clues) for information on terms that use the “Term Boost” type clues. | | Synchronise Term | Enables / Disables automatic synchronisation through the TermStoreManager tool for the term and its children. | | Relevance Threshold | The threshold for each Class defaults to 50 – but can be raised (to reduce the number of documents that get classified) or lowered (to increase the number of documents that get classified). | -| Boosts | The Weighting Boosts can also be adjusted for each Class. Based on the values above you would expect a 10% score boost if one of its child terms was classified. It is possible to set the _“Child”_ boost to 100%, doing so will in effect enable the parent to always be tagged if the child is tagged. An example for this would be a taxonomy containing regions, if a document was tagged as _“England”_ it should also be tagged as _“Europe”_. | +| Boosts | The Weighting Boosts can also be adjusted for each Class. Based on the values above you would expect a 10% score boost if one of its child terms was classified. You can set the _”Child”_ boost to 100%, doing so will in effect enable the parent to always be tagged if the child is tagged. An example for this would be a taxonomy containing regions, if a document was tagged as _”England”_ it should also be tagged as _”Europe”_. | diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/working_set.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/working_set.md index 525fa61798..fcf5d8c3b8 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/working_set.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/working_set.md @@ -7,7 +7,7 @@ sidebar_position: 80 # Working Set A Working Set of documents can be defined and used to test the accuracy of classification rules -against a controlled set of documents. The Working Set is mode can be selected in the Core +against a controlled set of documents. You can select the Working Set mode in the Core Configuration. If Class Level is selected then a different Working Set can be defined for every class. If Taxonomy diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actions.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actions.md index 45bc5cbf34..5b76af0b27 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actions.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actions.md @@ -6,7 +6,7 @@ sidebar_position: 30 # Workflow Actions -Actions are automated operation to be performed with the documents when rule conditions are +Actions are automated operations to be performed with the documents when rule conditions are triggered. There are two types of workflow actions: - Generic actions available for any type of document. These are: @@ -17,7 +17,7 @@ triggered. There are two types of workflow actions: - Source-specific actions -Workflow actions are executed at the final stage of the document processing. +The system executes workflow actions at the final stage of document processing. ## Available Actions by Source diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/actions_by_sources.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/actions_by_sources.md index 394ca87952..6110c9353b 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/actions_by_sources.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/actions_by_sources.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Available Actions -This section lists workflow actions available for the certain content source types. +This section lists workflow actions available for specific content source types. | Content source type | Available actions | | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/advanced_actions_classification.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/advanced_actions_classification.md index 814cb75e45..6ac623f943 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/advanced_actions_classification.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/advanced_actions_classification.md @@ -37,7 +37,7 @@ In the **Add Action** dialog, from the **Action Type** list select **Remove Clas this option is cleared, then after selecting the necessary taxonomy, you will be presented the list of its terms. Select the one you plan to use for filtering. - **NOTE:** Multiple selection is not supported: to configure several filter values, you should + **NOTE:** Multiple selection isn't supported: to configure several filter values, you should repeat this procedure for each filter value you need. 3. **Include Children** - select this option if needed. diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/advanced_actions_exchange.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/advanced_actions_exchange.md index abc82e0fcb..93393c5732 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/advanced_actions_exchange.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/advanced_actions_exchange.md @@ -37,4 +37,4 @@ Specify the following action parameters: | Action parameter | Description | Comments | | ---------------------- | --------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------- | | **Target Folder Name** | The name of the folder the move the email to. | For subfolders, only include the subfolder name (not the full path). | -| **Parent Folder Name** | If the target folder name is not unique, specify the parent folder name — to ensure the correct folder is used. | Optional. | +| **Parent Folder Name** | If the target folder name isn't unique, specify the parent folder name — to ensure the correct folder is used. | Optional. | diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/advancedactionsfiles/advanced_actions_files.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/advancedactionsfiles/advanced_actions_files.md index d9e853e529..254fa7d9c0 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/advancedactionsfiles/advanced_actions_files.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/advancedactionsfiles/advanced_actions_files.md @@ -6,14 +6,14 @@ sidebar_position: 60 # Advanced Actions for File System -In addition to the **Email Alert** ,**Migrate Document** and additional classification, the +In addition to the **Email Alert**, **Migrate Document**, and additional classification, the following actions are available for the **File system** content source type: - **Update Permissions** — this action updates the file system permissions for the classified document. See [Update Permissions](/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/advancedactionsfiles/workflows_updatepermissions.md) for details. -- **Apply MIP Label**, **Remove MIP Label** — these actions, respectively, apply and remove +- **Apply MIP Label**, **Remove MIP Label** — these actions, respectively, apply, and remove sensitivity label to/from a document stored on a file system, using Microsoft Information Protection (MIP). This helps to automate protection policies application. See [Modify MIP Label](/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/advancedactionsfiles/mip_workflow_action.md) diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/advancedactionsfiles/mip_workflow_action.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/advancedactionsfiles/mip_workflow_action.md index 121587d1c3..4ce4570e9f 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/advancedactionsfiles/mip_workflow_action.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/advancedactionsfiles/mip_workflow_action.md @@ -7,7 +7,7 @@ sidebar_position: 20 # Modify MIP Label Netwrix Data Classification is integrated with Microsoft Information Protection (MIP) to enable you -to better track and secure sensitive data on your file servers. +to track and secure sensitive data on your file servers. [See Understanding MIP Labels for more information.](/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/mip_intro.md) - [Modifying MIP Label via Workflow Wizard](#modifying-mip-label-via-workflow-wizard) diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/advancedactionssharepoint/advanced_actions_sharepoint.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/advancedactionssharepoint/advanced_actions_sharepoint.md index e99628b71c..c37b88ce66 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/advancedactionssharepoint/advanced_actions_sharepoint.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/advancedactionssharepoint/advanced_actions_sharepoint.md @@ -6,7 +6,7 @@ sidebar_position: 70 # Advanced Actions for SharePoint -In addition to the **Email Alert** ,**Migrate Document** and additional classification, the +In addition to the **Email Alert**, **Migrate Document**, and additional classification, the following actions are available for the **SharePoint** content source type: - [Migrate Document](/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/workflowsmigration/workflows_migration.md) @@ -26,12 +26,12 @@ following actions are available for the **SharePoint** content source type: [this Microsoft article](https://docs.microsoft.com/en-us/microsoft-365/compliance/labels) for details. - - **Filtered Targeted Meta Update** — this advanced action can be used to update a SharePoint + - **Filtered Targeted Meta Update** — use this advanced action to update a SharePoint property based on rules embedded in the taxonomy clues. Enter the document property to update in the **Update Field**, then select the required **Taxonomy** and enter **Match Field**, i.e. the field name/clue to match on. -- Apply MIP Label, Remove MIP Label — these actions, respectively, apply and remove sensitivity +- Apply MIP Label, Remove MIP Label — these actions, respectively, apply, and remove sensitivity label to/from a document stored on a file system, using Microsoft Information Protection (MIP). This helps to automate protection policies application. See [Modify MIP Label](/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/advancedactionsfiles/mip_workflow_action.md) diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/advancedactionssharepoint/workflows_spa_content_hubs.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/advancedactionssharepoint/workflows_spa_content_hubs.md index 033e47a57b..ac0480d3db 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/advancedactionssharepoint/workflows_spa_content_hubs.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/advancedactionssharepoint/workflows_spa_content_hubs.md @@ -16,8 +16,8 @@ consuming SharePoint Site collections. ![content_type_hubs_thumb_0_0](/images/dataclassification/5.6.2/workflows/content_type_hubs_thumb_0_0.webp) -To configure a Workflow to run against all sites that consume a Content Type Hub please follow the -below steps: +To configure a Workflow to run against all sites that consume a Content Type Hub, follow these +steps: 1. Navigate to Workflows → Configs → Content Type Hubs 2. Select Add diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/workflowsemail/workflows_email.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/workflowsemail/workflows_email.md index 4bcca7f20b..a3a93c764e 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/workflowsemail/workflows_email.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/workflowsemail/workflows_email.md @@ -26,14 +26,14 @@ Specify the following: ![action_email_smtp_thumb_0_0](/images/dataclassification/5.6.2/workflows/actions/action_email_smtp_thumb_0_0.webp) -When finished, slick **Save** to close the dialog and return to email action settings. +When finished, click **Save** to close the dialog and return to email action settings. | Field | Settings to specify | | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Email Subject | Specify the template for email subject. The template can contain dynamic values that will be obtained from the crawled content (e.g. _[cs:PageUrl]_). **TIP:** You can select the corresponding fields from **Add a Merge Field** list on the right. | | Email Body Template | Specify the template for email body. The template can contain dynamic values that will be obtained from the crawled content (e.g. _[cs:PageUrl]_). **TIP:** You can select the corresponding fields from **Add a Merge Field** list on the right. | -To modify action settings for the certain workflow, select the workflow and use the Advanced UI +To modify action settings for a workflow, select the workflow and use the Advanced UI window, as described in the [Modify Email Alert action settings](/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/workflowsemail/advanced_window_email.md) section. diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/workflowsmigration/advanced_window_migration.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/workflowsmigration/advanced_window_migration.md index 3654d80a91..c2661415ac 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/workflowsmigration/advanced_window_migration.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/workflowsmigration/advanced_window_migration.md @@ -23,13 +23,13 @@ These settings are the same for all supported sources. | Setting | Description | Comments | | ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| **Migration Destination** | The root destination to migrate to. | Make sure to define the required destination as Migration Config. | +| **Migration Destination** | The root destination to migrate to. | Ensure to define the required destination as Migration Config. | | **Destination Rename Mode** | Specifies what action to take if a file exists at the destination with the same name. - **None** – overwrite the destination file or issue a “duplicate” error. **NOTE:** Behaviour depends on the migration destination. - **Append Number** - append a numeric counter as a suffix to the file name (e.g. _document_2.txt)_. - **Append Date** - append workflow execution timestamp. | | | **Maintain Folder Structure** | If selected, subfolders will be created in the migration destination to match the relative path in the source. | Applies if this capability is supported by the source system. For Exchange, the path will also include a folder for the mailbox name (e.g. _\\MigrationDestination\User@domain.com\Inbox\HR_). | | **Delete Original Item** | If selected, the original item will be deleted after it is successfully copied to the destination. | Applies if this capability is supported by the source system. | | **Mark Original item as Read Only** | If selected, the original item will be marked as _read-only_. | Applies if this capability is supported by the source system. | | **Redaction Plan** | If redaction plans have been configured, specify the redaction plan to be applied to the document. See [Redaction](/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/redaction.md). | By default, this will be applied to the document at the destination. | -| **Redact Original** | If updating the source item is supported by the source system, then checking this box will cause the redaction plan to be applied to the source document after being successfully migrated. | Note that this option is not available when performing a move (deleting the original item). | +| **Redact Original** | If updating the source item is supported by the source system, then checking this box will cause the redaction plan to be applied to the source document after being successfully migrated. | This option isn't available when performing a move (deleting the original item). | ## Source-specific settings @@ -45,8 +45,8 @@ Settings for SharePoint content migration are described below. | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | | **Library/Folder** | The library and optional subfolder to migrate the document to in the migration destination. | | | **Mode** | Previous versions and metadata can be included. | Only applicable if the source system is also SharePoint. | -| **Dynamic Destination Field Name** | Specify a metadata field on the item that can be used to dynamically lookup the migration destination. | Only applicable if the source system is also SharePoint. | +| **Dynamic Destination Field Name** | Specify a metadata field on the item to dynamically lookup the migration destination. | Only applicable if the source system is also SharePoint. | | **Web Path** | The relative web path for the migration of the document. Format should be any of the following: - _~/WebPath_ —a document found, e.g., at _http://sharepoint/sites/Test/Demo_ with the relative path _~/Subsite_ would attempt to migrate to _http://sharepoint/sites/Test/Demo/subsite_ - _/SiteCollectionPath_ —a document found, e.g., at _http://sharepoint/sites/Test/Demo_ with the relative path _/Subsite_ would attempt to migrate to _http://sharepoint/sites/Test/Subsite_ | Only applicable if a SharePoint relative migration is chosen. | | **List Title** | The name of the library at the web path specified to migrate the document to. | Only applicable if a SharePoint relative migration is chosen. | -| **Fallback - if relative path invalid** | Enables/disables falling back to the standard migration destination if the relative path is unavailable. If the relative path does not exist, and the fallback mode is not enabled, then the Workflow will report a failure. | Only applicable if a SharePoint relative migration is chosen. | +| **Fallback - if relative path invalid** | Enables/disables falling back to the standard migration destination if the relative path is unavailable. If the relative path doesn't exist, and the fallback mode isn't enabled, then the Workflow will report a failure. | Only applicable if a SharePoint relative migration is chosen. | | | | | diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/workflowsmigration/workflows_migration.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/workflowsmigration/workflows_migration.md index 0f467f3b34..f41c3df857 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/workflowsmigration/workflows_migration.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/workflowsmigration/workflows_migration.md @@ -6,7 +6,7 @@ sidebar_position: 20 # Migrate Document -This action can be used to copy or move a document between content sources (from 'source' to +Use this action to copy or move a document between content sources (from 'source' to 'destination'). Simple migration copies the file and any document properties and is supported by all content source types. Migration action properties specific for different content source types are listed in the table below. @@ -27,7 +27,7 @@ to configure related settings. **To configure migration using Workflow wizard:** -On the What do you want to do step, select Migrate Document action. do the following: +On the "What do you want to do?" step, select Migrate Document. Then do the following: 1. Specify migration source and folder: @@ -36,8 +36,8 @@ On the What do you want to do step, select Migrate Document action. do the follo ![migration_destination_thumb_0_0](/images/dataclassification/5.6.2/workflows/actions/migration_destination_thumb_0_0.webp) - - If you created several sources for migration destinations, select on one in the under Where - should the document be migrated to? + - If you created several migration destinations, select one from the "Where + should the document be migrated to?" list. - For Google Drive, you need to specify subfolder to save your files in the Where in the destination should the files be saved? field. @@ -45,13 +45,13 @@ On the What do you want to do step, select Migrate Document action. do the follo | Option | Description | | ----------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | Replicate folder structure | If supported by the source system, subfolders will be created in the migration destination to match the relative path in the source. In the case of Exchange this will also include a folder for the mailbox name (I.E: \\MigrationDestination\User@domain.com\Inbox\HR). | + | Replicate folder structure | If supported by the source system, subfolders will be created in the migration destination to match the relative path in the source. In the case of Exchange this will also include a folder for the mailbox name (i.e., \\MigrationDestination\User@domain.com\Inbox\HR). | | Copy or Move the document | Select one of the following: - Copy - Move | | Mark Source as Read-only | The original item can be marked as read only. | | What action should be taken if the document already exists at the destination | Select action to perform: - Replace - Append | - | Redact the document | If update of the source item is supported by the source system, then using this option will instruct the program to apply the redaction plan to the source document after its successful migration. **NOTE:** This option is not available when performing a move (deleting the original item). | + | Redact the document | If update of the source item is supported by the source system, then using this option will instruct the program to apply the redaction plan to the source document after its successful migration. **NOTE:** This option isn't available when performing a move (deleting the original item). | -To modify action settings for the certain workflow, select the workflow and use the Advanced UI +To modify action settings for a workflow, select the workflow and use the Advanced UI window. See [Modify Migration action settings](/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/workflowsmigration/advanced_window_migration.md) for more information. diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/workflows_plugin.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/workflows_plugin.md index 74ed62a234..97c1345dca 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/workflows_plugin.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/workflows_plugin.md @@ -6,7 +6,7 @@ sidebar_position: 20 # Plugins for Additional Actions -In addition to the common workflow actions provided out-of-the-box, you can set up additional +In addition to the common workflow actions provided by default, you can set up additional actions using the plugins. Either use sample plugins from the vendor, or create your own custom plugins. Plugins should be stored in the dedicated folder, under _C:\Program Files\ConceptSearching\Plugins_. diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/managingworkflows/managing_workflows.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/managingworkflows/managing_workflows.md index 19089171a8..4cb5c4d327 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/managingworkflows/managing_workflows.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/managingworkflows/managing_workflows.md @@ -6,8 +6,8 @@ sidebar_position: 20 # Managing Workflows -Authorized users can create, modify or delete automated workflows that apply to the certain content. -For that, in the administrative web console select Content from the top menu and go to the +Authorized users can create, modify, or delete automated workflows that apply to specific content. +To do this, in the administrative web console select Content from the top menu and go to the **Workflows** tab. ![workflows_thumb_0_0](/images/dataclassification/5.6.2/workflows/workflows_thumb_0_0.webp) @@ -40,9 +40,9 @@ To modify a workflow, follow the steps described in the section. To delete a workflow, follow the steps described in the -[Delete Workflow](/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/managingworkflows/delete_workflow.md)section. +[Delete Workflow](/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/managingworkflows/delete_workflow.md) section. -## Cloning, Enabling or Renaming a Workflow +## Cloning, Enabling, or Renaming a Workflow 1. Click the link in the **Name** column for the required workflow ( e.g. Global for Google Drive in the figure below): diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/managingworkflows/workflowaddworkflowwizard/step_1_select_content_type.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/managingworkflows/workflowaddworkflowwizard/step_1_select_content_type.md index ca88698960..3980795916 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/managingworkflows/workflowaddworkflowwizard/step_1_select_content_type.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/managingworkflows/workflowaddworkflowwizard/step_1_select_content_type.md @@ -9,9 +9,9 @@ sidebar_position: 10 At the first step of the wizard, select the type of content your workflow will process, and specify which content sources of that type should be included in processing. -1. From the drop-down list, select what type of documents you want this workflow to target: - - To apply the workflow to all types of content, selecting **All types**. - - Otherwise, select what type of content you want to be included in the workflow: +1. From the dropdown list, select what type of documents you want this workflow to target: + - To apply the workflow to all types of content, select **All types**. + - Otherwise, select what type of content you want to include in the workflow: - Exchange - File - Google Drive diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/managingworkflows/workflowaddworkflowwizard/step_2_select_automated_action.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/managingworkflows/workflowaddworkflowwizard/step_2_select_automated_action.md index 9791a5cb9c..9cc22eab0f 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/managingworkflows/workflowaddworkflowwizard/step_2_select_automated_action.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/managingworkflows/workflowaddworkflowwizard/step_2_select_automated_action.md @@ -6,9 +6,8 @@ sidebar_position: 20 # Step 2. Select Action -After you select the required type of content source, you will be offered the number of automated -actions available for such content, for example, send an alert by email or update document metadata, -etc. +After you select the required type of content source, you can choose from automated +actions available for that content source, such as sending an email alert or updating document metadata. Click the action you need and configure the necessary settings. For details, see [Available Actions](/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/actions/actionsbysources/actions_by_sources.md). diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/managingworkflows/workflowaddworkflowwizard/step_3_specify_conditions.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/managingworkflows/workflowaddworkflowwizard/step_3_specify_conditions.md index ec95530068..683cb51d61 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/managingworkflows/workflowaddworkflowwizard/step_3_specify_conditions.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/managingworkflows/workflowaddworkflowwizard/step_3_specify_conditions.md @@ -37,7 +37,7 @@ The following options are available: this option is cleared, then after selecting the necessary taxonomy, you will be presented the list of its terms. Select the one you plan to use for filtering. - **NOTE:** Multiple selection is not supported: to configure several filter values, you should + **NOTE:** Multiple selection isn't supported: to configure several filter values, you should repeat this procedure for each filter value you need. 3. **Include Children** - select this option if needed. @@ -51,7 +51,7 @@ Then verify that configured filters are displayed properly: ![workflow_step3_filter_blue_thumb_0_0](/images/dataclassification/5.6.2/workflows/workflow_step3_filter_blue_thumb_0_0.webp) -- Excluding filters (i.e. instructing to include documents without classification tag you selected) +- Excluding filters (i.e. filters that exclude documents with the classification tag you selected) are colored red: ![workflow_step3_filter_red_thumb_0_0](/images/dataclassification/5.6.2/workflows/workflow_step3_filter_red_thumb_0_0.webp) diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/mip_intro.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/mip_intro.md index e4b7d92b4e..bc10689c90 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/mip_intro.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/mip_intro.md @@ -14,15 +14,13 @@ and protection services: - Third parties can use the MIP SDK to integrate with applications, using a standard, consistent data labeling schema and protection service. -MIP technology integration allows adding labels to documents. The label may have any security policy -assigned, for example, the policy to restrict access to sensitive documents. +MIP technology integration to add labels to documents. Labels can have any security policy +assigned, such as policies to restrict access to sensitive documents. Netwrix Data Classification for Files and Folders supports MIP labels as a Workflow action. After -you run the classification procedure, you would want to mark your documents with the labels. For -example, you use the protection label to be available by the person from the domain organization. In -this case, it will require authentication, such as password. - -You can apply the MIP labels to the file share and ShareЗoint sources. Specify this information +you run the classification procedure, you can mark your documents with the appropriate labels. For +example, you can apply a protection label that requires authentication from members of your domain organization. +You can apply the MIP labels to file share and SharePoint sources. Specify this information using the [Create a Workflow using Add Workflow Wizard](/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/managingworkflows/workflowaddworkflowwizard/workflow_add_workflow_wizard.md). Review the following for additional information: diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/workflows.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/workflows.md index afe6c2ec83..95b912a801 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/workflows.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/workflows.md @@ -6,7 +6,7 @@ sidebar_position: 30 # Understanding Workflows -A workflow allows you to configure an automated action that will be performed on a document, +Use a workflow to configure an automated action that will be performed on a document, following a classification decision. For example: - Send an email message to personnel in charge @@ -19,9 +19,8 @@ To set up a workflow, you need to do the following: - Select actions that will take place when one or more rule conditions are met. -Looking for real-life use cases and walk through examples? Check out Netwrix training materials. Go -the[ Netwrix website](https://www.netwrix.com/data_remediation_workflows.html) to find out how you -can easily reduce the exposure of your sensitive data. +Looking for real-life use cases and walk-through examples? Check out Netwrix training materials. Visit the [Netwrix website](https://www.netwrix.com/data_remediation_workflows.html) to find out how you +can reduce the exposure of your sensitive data. See next: diff --git a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/workflows_run_log.md b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/workflows_run_log.md index c95d20c400..f89b6b8b5d 100644 --- a/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/workflows_run_log.md +++ b/docs/dataclassification/5.6.2/contentconfigurationoverview/workflows/workflows_run_log.md @@ -10,7 +10,7 @@ When workflow actions are performed, the corresponding operations are logged to file. Click the Logs tab to view the corresponding audit trails. Here you can change the display period or the number of logs displayed, sort the list or copy its -content, or clear the logs you do not need. +content, or clear the logs you don't need. ![workflowlogs_thumb_0_0](/images/dataclassification/5.6.2/workflows/workflowlogs_thumb_0_0.webp) diff --git a/docs/dataclassification/5.6.2/dashboards.md b/docs/dataclassification/5.6.2/dashboards.md index c9b566ca83..f28ecb41af 100644 --- a/docs/dataclassification/5.6.2/dashboards.md +++ b/docs/dataclassification/5.6.2/dashboards.md @@ -22,50 +22,45 @@ The following statistics are available for each thread type: - Real Execution Time—The actual execution time of each thread (average of each threads run time) Statistics shown on the Dashboard screen are cached and updated regularly by the Collector service. -If the values are not being updated please ensure that the Collector service is running. +If the values aren't being updated, ensure that the Collector service is running. -New content will be shown as awaiting collection, and progress through to fully processed once it -has been classified. +New content appears as awaiting collection and progresses to fully processed after it's classified. -Content that has failed to process fully will be indicated under the "Exceptions" section, with the -following meanings: +Content that fails to process fully appears under the "Exceptions" section, with the following meanings: - Collection Errors—Items that failed to process during collection (typically due to an error from the source system) - Text Extraction Errors—Items that failed text extraction (either partially or fully)—this will typically mean that the full text for the affected documents will not be available -- Collection Exclusions—Items that have been excluded due to the specified configuration (such as - Sources → SharePoint → Exclusions) +- Collection Exclusions—Items the system excluded based on the specified configuration (such as Sources → SharePoint → Exclusions) - Files Skipped—File share items that have been ignored due to the "Files Included" or "Files Excluded" configuration (Sources → File) -- Deleted Automatically—Items that have been detected as removed from the source system -- Deleted Manually—Items removed manually by an end-user via the administration console +- Deleted Automatically—Items the system detected as removed from the source system +- Deleted Manually—Items that end-users removed via the administration console ![dashboard_thumb_0_0](/images/dataclassification/5.6.2/dashboard_thumb_0_0.webp) ## System Health -The health service provides a traffic light based reporting system. Colour-coded traffic lights will -appear in the top menu bar when issues are detected. The traffic lights provide a quick link to this +The health service provides a traffic light-based reporting system. Color-coded traffic lights appear in the top menu bar when the system detects issues. The traffic lights provide a quick link to this page to display more detailed information. You will then see the list of reported issues, with the ability to view a detailed description of the problem and suggested resolution steps. -It is also possible to configure notifications of system issues, along with daily reports of -outstanding system issues. +You can also configure notifications of system issues and daily reports of outstanding system issues. 1. Click Dismiss at the bottom. ![health_config_notifications](/images/dataclassification/5.6.2/health_config_notifications.webp) -2. Select Only dismiss health notifications that are older than one week, if you do not want to be +2. Select Only dismiss health notifications that are older than one week, if you don't want to be notified on outdated issues. 3. Select what you want to dismiss – warnings and all security notifications. ## Netwrix Data Classification Service Viewer -From the Netwrix Data Classification Service Viewer it is possible to view a live stream of the +From the Netwrix Data Classification Service Viewer, you can view a live stream of the current work being processed by the NDC services. As the services progress each document, the display will change. Once all work is complete, "Idle..." will be displayed. diff --git a/docs/dataclassification/5.6.2/dataanalysisoverview/dataanalysisoverview.md b/docs/dataclassification/5.6.2/dataanalysisoverview/dataanalysisoverview.md index aed36faff9..f58efcfa52 100644 --- a/docs/dataclassification/5.6.2/dataanalysisoverview/dataanalysisoverview.md +++ b/docs/dataclassification/5.6.2/dataanalysisoverview/dataanalysisoverview.md @@ -9,7 +9,7 @@ sidebar_position: 120 **Data Analysis** section in Netwrix Data Classification management console includes Reports and DSAR areas: -- To view reports on product operation, indexing and classification results, click Reports. +- To view reports on product operation, indexing, and classification results, click Reports. - To use DSAR search capabilities, click **DSAR**. ![data_analysis_thumb_0_0](/images/dataclassification/5.6.2/data_analysis_thumb_0_0.webp) diff --git a/docs/dataclassification/5.6.2/dataanalysisoverview/dsaroverview/dsar_overview.md b/docs/dataclassification/5.6.2/dataanalysisoverview/dsaroverview/dsar_overview.md index dc8c2ee67b..9d56ed9022 100644 --- a/docs/dataclassification/5.6.2/dataanalysisoverview/dsaroverview/dsar_overview.md +++ b/docs/dataclassification/5.6.2/dataanalysisoverview/dsaroverview/dsar_overview.md @@ -7,13 +7,10 @@ sidebar_position: 20 # Data Subject Access Requests Starting with version 5.5.3, Netwrix Data Classification offers support for Data Subject Access -Requests (DSAR) against the indexed content sources. It provides an interface which allows Subject -Access Requests to be carried out by specifically appointed team members, without elevated access or -inappropriate data exposure. Depending on assigned DSAR role, a user can view his / her searches or -searches submitted by other users. SAR administrators can leverage a simple, intuitive interface to -ensure reliable results and simplify the process of searching the IT estate for data. +Requests (DSAR) against the indexed content sources. It provides an interface that lets specifically appointed team members carry out Subject Access Requests without elevated access or inappropriate data exposure. Depending on assigned DSAR role, a user can view their searches or searches that other users submitted. SAR administrators can use a simple, intuitive interface to +ensure reliable results and simplify searching the IT estate for data. -All search requests are run by the scheduled time set by a Super User. If you have one or more +A Super User's schedule determines when the system runs all search requests. If you have one or more pending searches and for some reason want to run them immediately, you can use the Run now option. For more information, see [DSAR Settings](/docs/dataclassification/5.6.2/dataanalysisoverview/dsaroverview/dsar_settings.md). diff --git a/docs/dataclassification/5.6.2/dataanalysisoverview/dsaroverview/dsar_roles.md b/docs/dataclassification/5.6.2/dataanalysisoverview/dsaroverview/dsar_roles.md index 165c0cdd57..1fee439878 100644 --- a/docs/dataclassification/5.6.2/dataanalysisoverview/dsaroverview/dsar_roles.md +++ b/docs/dataclassification/5.6.2/dataanalysisoverview/dsaroverview/dsar_roles.md @@ -10,13 +10,11 @@ To keep the DSAR request process secure, Netwrix suggests configuring role-based control ensures that only appropriate users can modify DSAR configuration or view data, based on your company policies and the user's job responsibilities. -- DSAR User – basic user role, which will allow access to the tool itself, and allow search requests - to be run. The only requests that this user will be able to view are those submitted by the user - themselves (i.e. they cannot view searches submitted by other users). This role does not have +- DSAR User – basic user role, which grants access to the tool itself and lets users run search requests. The only requests that this user will be able to view are those submitted by the user + themselves (i.e. they can't view searches that other users submitted). This role doesn't have access to any system settings as well as to any of the sensitive data identified, including - filenames/locations. -- DSAR Manager – has all the permissions of the DSAR User role, plus the ability to see and - pause/cancel searches submitted by other users. + filenames/locations of sensitive data. +- DSAR Manager – has all the permissions of the DSAR User role, plus the ability to see and pause/cancel searches that other users submitted. - Super User – has all the permissions of the DSAR Manager role, with the addition of being able to see and amend the DSAR settings (user management, output path, batch run-time). diff --git a/docs/dataclassification/5.6.2/dataanalysisoverview/dsaroverview/dsar_searches.md b/docs/dataclassification/5.6.2/dataanalysisoverview/dsaroverview/dsar_searches.md index 48ca513df9..5fc4a55455 100644 --- a/docs/dataclassification/5.6.2/dataanalysisoverview/dsaroverview/dsar_searches.md +++ b/docs/dataclassification/5.6.2/dataanalysisoverview/dsaroverview/dsar_searches.md @@ -6,8 +6,7 @@ sidebar_position: 40 # Manage Search Requests -The **Searches** interface may contain multiple requests. This section contains information on how -to work with searches to address specific tasks. +The **Searches** interface may contain multiple requests. This section explains how to work with searches to address specific tasks. **NOTE:** To manage the search requests, users require sufficient access rights that are assigned by the **Super User** (DSAR Administrator). See @@ -21,7 +20,7 @@ You can filter your requests by status. Select one of the following under Displa - Active – shows all requests with "_Processed_" status (default view). - Completed – shows all completed requests. Review the [View Search Query Results](/docs/dataclassification/5.6.2/dataanalysisoverview/dsaroverview/dsar_view_search_results.md) - section for instructions on how to complete your request. + section to learn how to complete your request. - Canceled – shows all canceled requests. [See Cancel Search for more information.](#cancel-search) - All – shows all search requests. @@ -36,8 +35,7 @@ Complete_, _Updated Date_, etc. ## Cancel Search -If a search request is pending, you can cancel it — this will prevent the search terms from being -included in the search when it runs. +If a search request is pending, you can cancel it — this prevents the system from using the search terms when it runs. To cancel a search request, do the following: @@ -56,4 +54,4 @@ To template search request, do the following: 2. Locate the Searches tab. 3. Select search and click Template on the right. -A new search window will appear, pre-populated with exactly the same criteria as above. +A new search window will appear, pre-populated with the same criteria. diff --git a/docs/dataclassification/5.6.2/dataanalysisoverview/dsaroverview/dsar_settings.md b/docs/dataclassification/5.6.2/dataanalysisoverview/dsaroverview/dsar_settings.md index 99622549b5..1ed40f68e0 100644 --- a/docs/dataclassification/5.6.2/dataanalysisoverview/dsaroverview/dsar_settings.md +++ b/docs/dataclassification/5.6.2/dataanalysisoverview/dsaroverview/dsar_settings.md @@ -9,7 +9,7 @@ sidebar_position: 20 This section describes Netwrix Data Classification configuration required to run Data Subject Access Requests (DSAR). -**NOTE:** Only users with 'Super User' permissions are able to configure DSAR. +**NOTE:** Only users with 'Super User' permissions can configure DSAR. [See DSAR Roles for more information.](/docs/dataclassification/5.6.2/dataanalysisoverview/dsaroverview/dsar_roles.md) 1. In administrative web console , navigate to Data Analysis → DSAR. @@ -18,16 +18,15 @@ Requests (DSAR). | Option | Description | | ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | Batch Start Time | Review and modify batch run schedule to optimize the timing for your environment. **NOTE:** Please note that this setting affects the batches of all users; there is one batch-run per instance of the DSAR tool. By default, the DSAR batch will only automatically run once a day; to force another batch run within a 24 hour period, use the **Run now** button, as described below. | - | Output Location | Specify a desired file share to export results of DSAR searches. Items are grouped by Case ID. **NOTE:** Please note that there is one output location per instance of the DSAR tool. Changing the Output Location setting does not impact files that have already been placed in their location - i.e., any existing output does not get moved when the setting is changed. | + | Batch Start Time | Review and modify batch run schedule to optimize the timing for your environment. **NOTE:** This setting affects the batches of all users; there is one batch-run per instance of the DSAR tool. By default, the DSAR batch will only automatically run once a day; to force another batch run within a 24 hour period, use the **Run now** button, as described below. | + | Output Location | Specify a desired file share to export results of DSAR searches. Items are grouped by Case ID. **NOTE:** Each instance of the DSAR tool has one output location. Changing the Output Location setting doesn't move existing files. | | Email Notification Group | Specify an email group to send notifications to. Click + to create a new group or select existing one. In the Add dialog, configure Email group as follows: - Group Name – provide a name for the new group. - Email Addresses – select as many addresses as needed. The email group must contain at least one email address. - Email Server – select the email server. See Email Configuration for more information. | ## Run now -All search requests are run by the scheduled time set by a Super User. If you have one or more -pending searches and for some reason want to run them immediately, use Run now option. +A Super User's schedule determines when the system runs all search requests. If you have one or more pending searches and want to run them immediately, use the Run now option. -**NOTE:** This option is only available when there are queued requests and a search is not currently +**NOTE:** This option is only available when there are queued requests and a search isn't in progress to prevent conflicting processes. To run queued search requests immediately diff --git a/docs/dataclassification/5.6.2/dataanalysisoverview/dsaroverview/dsar_view_search_results.md b/docs/dataclassification/5.6.2/dataanalysisoverview/dsaroverview/dsar_view_search_results.md index b85c57e0df..08d5c4c85a 100644 --- a/docs/dataclassification/5.6.2/dataanalysisoverview/dsaroverview/dsar_view_search_results.md +++ b/docs/dataclassification/5.6.2/dataanalysisoverview/dsaroverview/dsar_view_search_results.md @@ -6,8 +6,7 @@ sidebar_position: 50 # View Search Query Results -Depending on assigned DSAR role, a user can view his / her searches or searches submitted by other -users even when its status is "_queued_" or "_in progress_". To view a search query results, do the +Depending on assigned DSAR role, a user can view their searches or searches that other users submitted even when the search status is "_queued_" or "_in progress_". To view a search query results, do the following: 1. In administrative web console , navigate to Data Analysis → DSAR. @@ -24,7 +23,7 @@ following: | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Details | Here you can review search criteria and system details (search status, submitted date etc.) | | Results | This tab contains all records that meet search criteria with the ability to filter by: - Page ID - File location - Modification date - File size In addition, you can export your results to .CSV and XLSX format and simply copy records to a clipboard. | - | Audit Log | On this tab you can see all events related to this search request: when the search was run, who and when reviewed search request results and log. | + | Audit Log | On this tab you can see all events related to this search request: when the search was run, who, and when reviewed search request results and log. | 4. After reviewing the request, user can complete it clicking Close Request on the Results tab or export the results. diff --git a/docs/dataclassification/5.6.2/dataanalysisoverview/dsaroverview/run_searches.md b/docs/dataclassification/5.6.2/dataanalysisoverview/dsaroverview/run_searches.md index b03c737f35..7f5b77949a 100644 --- a/docs/dataclassification/5.6.2/dataanalysisoverview/dsaroverview/run_searches.md +++ b/docs/dataclassification/5.6.2/dataanalysisoverview/dsaroverview/run_searches.md @@ -6,9 +6,7 @@ sidebar_position: 30 # Create Search Requests -Search requests are generally batched and run as one (with the scheduled time set by the Super -User/s), as this will deliver maximum performance, minimize impact across the estate and prevent -delays caused by queuing. You can create as many search requests as needed. +Search requests are generally batched and run together at the schedule the Super User sets, which delivers maximum performance, minimizes impact across the estate, and prevents delays from queuing. You can create as many search requests as needed. To create a search request: @@ -20,7 +18,7 @@ To create a search request: | Option | Description | | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Case ID | Enter Case ID. The Case ID is the unique ID given to the request, to allow tracking throughout the process. **NOTE:** If you choose an existing Case ID, you will be prompted to confirm that you want to run another search for the same ID. This will prevent multiple identical searches from being run for the same search request. | - | Last Name\* | Enter the last name to associate search results with a particular individual. **NOTE:** The last name alone will be passed as a clue – the first name/s alone will not. The field is not case sensitive. | + | Last Name\* | Enter the last name to associate search results with a particular individual. **NOTE:** The last name alone will be passed as a clue – the first name/s alone will not. The field isn't case sensitive. | | First Name\* | Enter the first name to associate search results with a particular individual. **NOTE:** The field can be used only in conjunction with the last name. | | Email Address | Enter email address. Email addresses are unique, so if they are identified within a file, it should be deemed relevant to the request. **NOTE:** The field is case-sensitive. | | Reference | Specify additional references to identify an individual. You can add as many additional parameters as needed. For example: Customer reference, Account reference, Claim reference, Account number, etc. | @@ -37,7 +35,7 @@ find and collate if the only data retrieved pertains to a specified date range r This example describes the search mechanism for **First name** and **Last name** combination. -A search for First name(s) _John Richard_ with the Last name _Smith_ will be searched for as: +A search for first names _John Richard_ with the last name _Smith_ will be searched for as: - John R Smith - John Smith diff --git a/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/autoclassification.md b/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/autoclassification.md index 84e291c63a..0b02000526 100644 --- a/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/autoclassification.md +++ b/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/autoclassification.md @@ -10,17 +10,14 @@ sidebar_position: 40 When large search exports are run the report may take some time to compile, in this instance the background processes create the report and make it available for download via the Queued Reports -dashboard. Reports can be deleted prior to, or after, processing as well as downloaded as many times +dashboard. Reports can be deleted before, or after, processing as well as downloaded as many times as necessary. ![queuedreportresult_thumb_0_0](/images/dataclassification/5.6.2/reporting/queuedreportresult_thumb_0_0.webp) ## Plugins for Custom Reports -While there are a number of reports included in the product by default, it is also expected that -specific business needs may arise that require reporting not covered by the default reports. With -this in mind, you can create custom report using Plugins. Once the custom report plugin is deployed, -the report will appear in the main reports list (with the built-in reports). A sample plugin +While the product includes a number of reports by default, you may have specific business needs that require reporting not covered by the default reports. You can create custom reports using Plugins. After you deploy the custom report plugin, it appears in the main reports list alongside the built-in reports. A sample plugin incorporates: - Custom Parameters @@ -29,5 +26,4 @@ incorporates: - Paging Usually, the application communicates with a server running the administration Web console. To -assemble and combine the search results required for reporting, the NDC server will automatically -communicate with the other servers in the cluster. +assemble and combine the search results that reporting requires, the NDC server automatically communicates with the other servers in the cluster. diff --git a/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/content_distribution.md b/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/content_distribution.md index 02748ca71e..2d115169ae 100644 --- a/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/content_distribution.md +++ b/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/content_distribution.md @@ -6,7 +6,7 @@ sidebar_position: 20 # Content Distribution Map -The Content Distribution treemap allows you to interrogate your data in two different ways: +The Content Distribution treemap lets you interrogate your data in two different ways: - Taxonomy Grouping—When grouped by taxonomy, the treemap will highlight the sources with the largest numbers of documents tagged to the selected taxonomies / terms. An example use case is @@ -14,13 +14,10 @@ The Content Distribution treemap allows you to interrogate your data in two diff Clicking on an area will drill into the term / taxonomy to provide a clear view of the affected sources. Optionally "safe" sources, such as quarantine locations, can be excluded. - Source Grouping—When grouped by source, the treemap will show the level of content either untagged - or tagged within the taxonomy. The treemap will display the top level terms for the selected - taxonomy with the counts including any document that is tagged to either the top level term or one - of its descendants. Documents can be tagged to one or more terms so the number associated with + or tagged within the taxonomy. The treemap displays the top-level terms for the selected taxonomy, with counts that include any document tagged to either the top-level term or one of its descendants. Documents can be tagged to one or more terms so the number associated with each top level term may exceed the number of documents in the source. -It is possible to filter and refine this display, either selecting specific sources / source-groups -or excluding specific sources / source-groups. +You can filter and refine this display by selecting or excluding specific sources and source-groups. ![contentdistribution_thumb_0_0](/images/dataclassification/5.6.2/reporting/contentdistribution_thumb_0_0.webp) diff --git a/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/overview_dashboard.md b/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/overview_dashboard.md index b59bb2227a..8a5bf1672a 100644 --- a/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/overview_dashboard.md +++ b/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/overview_dashboard.md @@ -7,7 +7,7 @@ sidebar_position: 10 # Sensitive Documents Dashboard The dashboard provides a top-level overview of the security classifications tagged against the -content and allows users to drill down into the data to gain visibility of where/what their +content and lets you explore the data in detail to gain visibility of where and what your sensitive content is. By default, the dashboard shows all classified data. However, users can customize it for their needs. [See Customize Dashboard for more information.](#customize-dashboard) @@ -34,8 +34,7 @@ console, do the following: - Select the Dashboard tab on the left. -**IMPORTANT!** The data for the dashboard automatically updates every 15 minutes. Please note that -refreshing the page will not update the data. +**IMPORTANT!** The data for the dashboard automatically updates every 15 minutes. Refreshing the page will not update the data. ## Review Sensitive Documents Dashboard @@ -43,7 +42,7 @@ The dashboard includes the following sections: - Total processed files – shows the actual number of the classified files. - **NOTE:** Folders are not counted. + **NOTE:** Folders aren't counted. - Sensitive Files – helps you identify how many files have been tagged at least once in any of Netwrix built-in sensitive taxonomies except for the following: File Type, File Size, Language. @@ -51,7 +50,7 @@ The dashboard includes the following sections: [Built-in Taxonomies Overview ](/docs/dataclassification/5.6.2/contentconfigurationoverview/taxonomiesintro/standalone_taxonomies.md) section for the full list of predefined taxonomies. - **NOTE:** Custom taxonomies are not counted. + **NOTE:** Custom taxonomies aren't counted. - Sensitive Files by Source (Top 5) – shows the top 5 sources that contain most of your sensitive data. @@ -74,7 +73,7 @@ legacy documents reside. Besides, you can apply filters to narrow the reporting ## Customize Dashboard By default, the dashboard shows all classified data in your environment. However, users can do one -of the following to look after the desired metrics: +of the following to view the metrics you want: - Apply filters to view live data instantly and narrow classifications scope at a glance - Save configurations to quickly access required data @@ -85,7 +84,7 @@ To apply filters ![dashboard_filters_thumb_0_0](/images/dataclassification/5.6.2/reporting/dashboard_filters_thumb_0_0.webp) -2. Select a taxonomy(-ies) and/or a source group(s) you want to see real-time data for. +2. Select one or more taxonomies and/or source groups you want to see real-time data for. 3. Click Apply Filters to immediately review classified data matching your filtering criteria. To save configuration diff --git a/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/report_subscriptions_manage.md b/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/report_subscriptions_manage.md index 663d887a9a..f5bc500ea5 100644 --- a/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/report_subscriptions_manage.md +++ b/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/report_subscriptions_manage.md @@ -6,8 +6,7 @@ sidebar_position: 50 # Manage Reports -This section contains information on how to generate reports, use report templates and enable -Auto-Classification. +This section explains how to generate reports, use report templates, and enable Auto-Classification. ## Generating and Exporting Reports @@ -34,8 +33,7 @@ downloaded to your default downloads folder. ## Save Report Configuration -Netwrix Data Classification allows you to save report configuration settings as a template for the -future use. Then if you need to run the report with the specified parameters more than once, you can +Netwrix Data Classification lets you save report configuration settings as a template for future use. Then if you need to run the report with the specified parameters more than once, you can just load its configuration from the template you have saved. :::note @@ -73,13 +71,13 @@ To save a report configuration template 1. Select a report you want to load the configuration for. 2. Click the **Load Saved Configuration** link. -3. In the **Load Saved Configuration** dialog, select the desired template from the **Template +3. In the **Load Saved Configuration** dialog, select the template you want from the **Template Name** list. 4. Click **Generate** to view the report. ## Manage Subscriptions -Subscriptions for report templates enable you to schedule email delivery of a variety of reports or +Subscriptions for report templates let you schedule email delivery of a variety of reports or set of specific search criteria. Subscriptions are helpful if you are a rare guest of Netwrix Data Classification and you only need to get statistics based on individual criteria. For example, an IT manager can easily provide auditors with weekly reports to prove compliance with regulations. @@ -90,14 +88,14 @@ and click **View Subscriptions** next to an existing template to view and edit s ![managesubscription](/images/dataclassification/5.6.2/reporting/managesubscription.webp) -Checking the **Create a Subscription** box when saving a new report configuration will enable users -to create a new subscription. The following options are configured on the **Manage Subscriptions** +Checking the **Create a Subscription** box when saving a new report configuration lets you +create a new subscription. The following options are configured on the **Manage Subscriptions** page: | Option | Description | | ----------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | | Subscription Name | Create a name for the report subscription | -| Email Group | Enter the email group(s) that will receive the reports. If no email groups are configured, click the **(+)**icon to create new email groups. | +| Email Group | Enter one or more email groups that will receive the reports. If no email groups are configured, click the **(+)**icon to create new email groups. | | Send email when no data is reported | Check this box to send an email with the report even when there is no data. Leave this box unchecked to disable this option. | | Export Format | Select whether to export the report as a **CSV** or **XLSX**. | | Run Every: | Set how often email reports are sent out. Users can choose to send reports in a period of **days**, **weeks**, or **months**. | diff --git a/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/report_suscriptions.md b/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/report_suscriptions.md index b7da14d20b..360882ba70 100644 --- a/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/report_suscriptions.md +++ b/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/report_suscriptions.md @@ -6,7 +6,7 @@ sidebar_position: 60 # Report Subscriptions -Subscriptions for report templates enable you to schedule email delivery of a variety of reports or +Subscriptions for report templates let you schedule email delivery of a variety of reports or set of specific search criteria. Subscriptions are helpful if you are a rare guest of Netwrix Data Classification and you only need to get statistics based on individual criteria. For example, an IT manager can easily provide auditors with weekly reports to prove compliance with regulations. @@ -23,7 +23,7 @@ page: | Option | Description | | ----------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | | Subscription Name | Create a name for the report subscription | -| Email Group | Enter the email group(s) that will receive the reports. If no email groups are configured, click the **(+)**icon to create new email groups. | +| Email Group | Enter one or more email groups that will receive the reports. If no email groups are configured, click the **(+)**icon to create new email groups. | | Send email when no data is reported | Check this box to send an email with the report even when there is no data. Leave this box unchecked to disable this option. | | Export Format | Select whether to export the report as a **CSV** or **XLSX**. | | Run Every: | Set how often email reports are sent out. Users can choose to send reports in a period of **days**, **weeks**, or **months**. | diff --git a/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/reporting_intro.md b/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/reporting_intro.md index 32b5201795..ddae90fa66 100644 --- a/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/reporting_intro.md +++ b/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/reporting_intro.md @@ -6,8 +6,7 @@ sidebar_position: 10 # Reporting Capabilities -Selecting **Analysis** → Reports in the management console helps a user extract a wealth of -information from the NDC index. +Selecting **Analysis** → Reports in the management console gives you access to detailed information from the NDC index. The main **Dashboard** has three high level graphs highlighting the current state of processing: @@ -17,8 +16,7 @@ The main **Dashboard** has three high level graphs highlighting the current stat - Classification Coverage—Shows the percentage of classified content, broken down by type, and the percentage of content that has not received any auto-classifications -It is possible to filter and refine data presentation to look for the areas that contain the largest -amount of documents tagged with a particular term, or to only review specific content. +You can filter and refine data presentation to find areas with the most documents tagged with a particular term, or to review specific content. Reporting capabilities also include the following: diff --git a/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/reportingbuiltin/classification_reports.md b/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/reportingbuiltin/classification_reports.md index 58db96941a..11f0dd3ffb 100644 --- a/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/reportingbuiltin/classification_reports.md +++ b/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/reportingbuiltin/classification_reports.md @@ -12,8 +12,7 @@ Review the list of the built-in classification reports: specifically tags added/removed. To log classification changes, enable the related option in the product configuration; see Enable Auto-Classification Change Logging for details. -- Classification Coverage—Provides a list of documents that have been tagged with X or fewer - classifications. Assists in locating documents that have a low number of auto classifications and +- Classification Coverage—Provides a list of documents with X or fewer classifications. Assists in locating documents that have a low number of auto classifications and highlights the nearest missed classification. Supports filtering by URL and source group. - Clue Counts—Provides a report of the number of clues per term, also includes a count of regular expression clues. diff --git a/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/reportingbuiltin/clue_building_reports.md b/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/reportingbuiltin/clue_building_reports.md index f944168366..a9a86d5c6a 100644 --- a/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/reportingbuiltin/clue_building_reports.md +++ b/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/reportingbuiltin/clue_building_reports.md @@ -10,9 +10,9 @@ Review the list of the built-in clue building reports: - **Auto Classification Review**— Provides a list of documents tagged with a given set of classifications. For full debugging detail, the trace mode "Classification Calculations" must be - enabled prior to auto-classification. + enabled before auto-classification. - Classification Misses—Reports on documents that almost reached the threshold for classification, but ‘missed’ being classified by 20% or less. Supports filtering by URL and source group. - Clue Coverage—Provides a report on the usage of clues within classification tagging. Assists in - highlighting clues that are not aiding the classification process, or clues that are too vague. + highlighting clues that aren't aiding the classification process, or clues that are too vague. Supports filtering by URL and source group. diff --git a/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/reportingbuiltin/documentation_reports.md b/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/reportingbuiltin/documentation_reports.md index 6553e6db76..7dccbc6da3 100644 --- a/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/reportingbuiltin/documentation_reports.md +++ b/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/reportingbuiltin/documentation_reports.md @@ -10,14 +10,11 @@ Review the list of the built-in document reports: - Document Tagging—Provides a report on the manual and automatically assigned document classifications. Supports filtering by URL and source group. -- Duplicate Detection—Provides a list of documents that are considered “duplicates” within the - index, using checksum matching. Supports filtering by URL and source group. +- Duplicate Detection—Provides a list of documents the system identifies as “duplicates” within the index using checksum matching. Supports filtering by URL and source group. - Manual Tagging—Provides a report on the manual and automatically assigned document classifications—filtered specifically to manually classified documents. Supports filtering by URL and source group. -- Near Duplicate Detection—Details near duplicate documents across the index. Near duplicates are - detected as a background process, to enable the background processing simply enable the option - ‘Near Duplicate Detection’ within the NDC Indexer Settings and rebuild the necessary sources. See +- Near Duplicate Detection—Details near duplicate documents across the index. The system detects near duplicates as a background process. To enable this background processing, select the ‘Near Duplicate Detection’ option in the NDC Indexer Settings and rebuild the necessary sources. See Core Configuration for the configuration details. Supports filtering by URL, source group and excluding content types (comma delimited list of content types such as: “css,pdf”). - Page Statuses—Provides a list of documents at a given status within the index. Supports filtering diff --git a/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/reportingbuiltin/reporting_built-in.md b/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/reportingbuiltin/reporting_built-in.md index 82b22d77ed..9e0ee51ab8 100644 --- a/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/reportingbuiltin/reporting_built-in.md +++ b/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/reportingbuiltin/reporting_built-in.md @@ -6,9 +6,7 @@ sidebar_position: 30 # Built-in Reports -Netwrix Data Classification offers a number of built-in reports and charts that refer to indexing -and classification process and results, as well to the system operation. They can be run in browser, -as well as exported to Excel or CSV files. See Manage Reports for more information. +Netwrix Data Classification offers a number of built-in reports and charts that cover the indexing and classification processes, results, and system operation. You can run them in your browser or export them to Excel or CSV files. See Manage Reports for more information. **NOTE:** For some reports, **Auto-classification change logging** must be enabled to supply the reports with the required data. diff --git a/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/reportingbuiltin/system_reports.md b/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/reportingbuiltin/system_reports.md index d2327d3a9d..3aea0c0f80 100644 --- a/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/reportingbuiltin/system_reports.md +++ b/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/reportingbuiltin/system_reports.md @@ -8,11 +8,9 @@ sidebar_position: 50 Review the list of the built-in system reports: -- Failed Write Classifications—Provides a list of documents in the core index that failed to have - their classifications written to the source system (such as SharePoint Managed Metadata Columns). +- Failed Write Classifications—Provides a list of documents in the core index where the system failed to write classifications to the source system (such as SharePoint Managed Metadata Columns). Supports filtering by URL and source group. -- Files Skipped—Provides a list of documents that have been excluded from processing because they - were not explicitly included, or were specifically excluded. See the related sections for the +- Files Skipped—Provides a list of documents the system excluded from processing because they weren't explicitly included or were specifically excluded. See the related sections for the content sources for more information on file inclusion / exclusion. Filtering by URL is supported. - iFilters Detected—Provides a list of detected iFilters per server. iFilters are the Microsoft standard for implementing text extraction from binary files. They are used by many search engines @@ -25,7 +23,7 @@ Review the list of the built-in system reports: - Term History—Displays a history of changes made to a taxonomy (clues added/deleted etc). Supports filtering by term name. - Term Links—Provides a list of links to a specified term (Metadata clues, Term Boosts and Required - Term links)—useful when retiring taxonomy nodes to avoid invalid links to the term you wish to + Term links)—useful when retiring taxonomy nodes to avoid invalid links to the term you want to remove. - Text Extraction Failures—Provides a list of documents in the core index that failed text - extraction (granular iFilter error codes). Supports filtering by URL, title and source group. + extraction (granular iFilter error codes). Supports filtering by URL, title, and source group. diff --git a/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/reportingbuiltin/top_reports_charts.md b/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/reportingbuiltin/top_reports_charts.md index 6e874f55c9..331778f97a 100644 --- a/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/reportingbuiltin/top_reports_charts.md +++ b/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/reportingbuiltin/top_reports_charts.md @@ -6,26 +6,25 @@ sidebar_position: 10 # Top Reports and Charts -Several reports and charts do not belong to any group; they are on top of the list as they provide +Several reports and charts don't belong to any group; they are on top of the list as they provide the most frequently requested information: - **Dashboard**—Shows a high level overview of Netwrix Data Classification operations statistics. ![reports_main_dashboard_thumb_0_0](/images/dataclassification/5.6.2/reporting/reports_main_dashboard_thumb_0_0.webp) -- **Content Distribution** —Allows you to view the distribution of your content in several formats: +- **Content Distribution** — Lets you view the distribution of your content in several formats: grouping by source, grouping by taxonomy, or grouping by term. See [Content Distribution Map](/docs/dataclassification/5.6.2/dataanalysisoverview/reportingintro/content_distribution.md) for details. - **Recent Tagging**—Displays statistics on the tagging results according to the specified filters. - To view this data, make sure the "**Auto-Classification Change Log**" feature is enabled, as - described above, + To view this data, ensure the "**Auto-Classification Change Log**" feature is enabled (see the instructions above), - **Recent Document Processing**—Displays statistics on the document processing results for the last - 7 days. This includes collection, indexing and classification of data in the content sources. + 7 days. This includes collection, indexing, and classification of data in the content sources. ![recent_document_processing_thumb_0_0](/images/dataclassification/5.6.2/reporting/recent_document_processing_thumb_0_0.webp) -- Index Analysis—Provides the ability to manually queue items for background index analysis, +- Index Analysis— Lets you manually queue items for background index analysis, initially scoped to assist in identifying fuzzy matched duplicate documents. - Term Cloud—Displays the top 50 key terms/phrases across the index, selecting a term expands the cloud into the related terms. diff --git a/docs/dataclassification/5.6.2/deployment/appliance/ndc_overview.md b/docs/dataclassification/5.6.2/deployment/appliance/ndc_overview.md index f555b67329..cac9f2979d 100644 --- a/docs/dataclassification/5.6.2/deployment/appliance/ndc_overview.md +++ b/docs/dataclassification/5.6.2/deployment/appliance/ndc_overview.md @@ -7,7 +7,7 @@ sidebar_position: 10 # Features and Benefits Netwrix Data Classification is a platform that identifies data that’s important for your -organization and enables you to reduce risk and unleash the true value of this data. +organization, reducing risk and unleashing the true value of this data. Powered by unique compound term processing technology, it enriches your enterprise content with accurate and consistent metadata empowering you to work with data more confidently. By seeing which diff --git a/docs/dataclassification/5.6.2/deployment/appliance/nvap_configure_vm_script.md b/docs/dataclassification/5.6.2/deployment/appliance/nvap_configure_vm_script.md index 4c8abf23df..b20da3771b 100644 --- a/docs/dataclassification/5.6.2/deployment/appliance/nvap_configure_vm_script.md +++ b/docs/dataclassification/5.6.2/deployment/appliance/nvap_configure_vm_script.md @@ -6,16 +6,15 @@ sidebar_position: 60 # Configure Virtual Appliance -Follow the steps below to configure your virtual appliance with Netwrix Data Classification. +Complete the following steps to configure your virtual appliance with Netwrix Data Classification. -1. For Windows Server, the EULA will be displayed in the License terms page; read and accept the +1. For Windows Server, the License terms page displays the End User License Agreement (EULA); read and accept the agreement. 2. Next, specify a password for the built-in administrator account. Then re-enter your password. Click Finish. 3. Log in to the virtual machine. 4. The Windows PowerShell opens and automatically runs the script. Press any key to read the license - agreement and then press `Y` to accept it. Then you will be prompted to configure the virtual - machine. Press Enter to start. + agreement and then press `Y` to accept it. Then configure the virtual machine. Press Enter to start. | Step | Description | | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | @@ -24,8 +23,7 @@ Follow the steps below to configure your virtual appliance with Netwrix Data Cla | Configure network | - Select `Y` to use DHCP server to configure network settings automatically. - Select `N` to configure required parameters manually. In this case, you will be prompted to set up IP settings manually. | | Join computer to the domain or workgroup | - Select `Y`. Specify the fully qualified domain name to join (e.g., `corp.local`). Then specify domain administrator name and password. - Select `N`. Specify the local administrator name and credentials. | -5. When the script execution completes, you will be prompted to reboot the virtual machine for the - changes to take effect. +5. When the script execution completes, reboot the virtual machine to apply the changes. 6. After reboot, log in to the virtual machine using the domain administrator credentials (for appliances joined to domain) or local administrator credentials (for appliances joined to workgroup). diff --git a/docs/dataclassification/5.6.2/deployment/appliance/nvap_deploy_hyperv.md b/docs/dataclassification/5.6.2/deployment/appliance/nvap_deploy_hyperv.md index af9b032f31..20044844cd 100644 --- a/docs/dataclassification/5.6.2/deployment/appliance/nvap_deploy_hyperv.md +++ b/docs/dataclassification/5.6.2/deployment/appliance/nvap_deploy_hyperv.md @@ -10,7 +10,7 @@ sidebar_position: 50 specified location. 2. Navigate to Start → All Apps → Hyper-V Manager. 3. In the Hyper-V Manager, navigate to Actions → Import virtual machine and follow the instructions - of the wizard. Review the table below for more information. + of the wizard. Review the following table for more information. | Step | Description | | ---------------------- | ---------------------------------------------------------------------- | diff --git a/docs/dataclassification/5.6.2/deployment/appliance/nvap_deploy_vmware.md b/docs/dataclassification/5.6.2/deployment/appliance/nvap_deploy_vmware.md index 8c1f1fbb75..324de0b447 100644 --- a/docs/dataclassification/5.6.2/deployment/appliance/nvap_deploy_vmware.md +++ b/docs/dataclassification/5.6.2/deployment/appliance/nvap_deploy_vmware.md @@ -12,13 +12,13 @@ sidebar_position: 40 **NOTE:** If you are running VMware 6.0, connect to vSphere using the on-premises vSphere client and select File → Deploy OVF Template. -2. Follow the instructions in the table below: +2. Follow the instructions in the following table: | Step | Description | | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Source | Browse for the folder that contains the Netwrix Data Classification virtual appliance template. | | OVF Template Details | Review information on this template. | - | Name and Location | Select a name for the new virtual machine if you do not want to use the default name _"Netwrix Data Classification"_. **NOTE:** The name must be unique within the inventory folder and may contain up to 80 characters including spaces. | + | Name and Location | Select a name for the new virtual machine if you don't want to use the default name _"Netwrix Data Classification"_. **NOTE:** The name must be unique within the inventory folder and may contain up to 80 characters including spaces. | | Resource Pool | Select a resource pool to deploy Netwrix Data Classification virtual appliance. | | Storage | Select destination storage. | | Disk Format | Netwrix recommends to select the Thin Provision option to save your disk space. | diff --git a/docs/dataclassification/5.6.2/deployment/appliance/nvap_overview.md b/docs/dataclassification/5.6.2/deployment/appliance/nvap_overview.md index 2e9a5323d3..a2a0b120ef 100644 --- a/docs/dataclassification/5.6.2/deployment/appliance/nvap_overview.md +++ b/docs/dataclassification/5.6.2/deployment/appliance/nvap_overview.md @@ -7,14 +7,14 @@ sidebar_position: 20 # Virtual Deployment In addition to traditional on-premises deployment, Netwrix Data Classification now offers new -deployment options that can speed time-to-value by getting you up and running in less than 15 +deployment options that can speed time-to-value by enabling deployment in less than 15 minutes. Virtual appliance—If you run a Microsoft Hyper-V or VMware vSphere, you can deploy Netwrix Data Classification as a virtual appliance. Virtual appliance is a VM image file with installed Netwrix Data Classification. The image is also configured to use Microsoft Edge as a default web browser. -The following configuration options available: +You can deploy the following configuration options: - Generalized Windows Server 2022, 180-day evaluation version. - Generalized Windows Server 2019, 180-day evaluation version. diff --git a/docs/dataclassification/5.6.2/deployment/appliance/nvap_system_requirments.md b/docs/dataclassification/5.6.2/deployment/appliance/nvap_system_requirments.md index 6b8b626f83..e0a7ecfcc2 100644 --- a/docs/dataclassification/5.6.2/deployment/appliance/nvap_system_requirments.md +++ b/docs/dataclassification/5.6.2/deployment/appliance/nvap_system_requirments.md @@ -9,14 +9,14 @@ sidebar_position: 30 This section provides the software requirements and represents the default hardware configuration for the virtual machine where Netwrix Data Classification virtual appliance is going to be deployed. -**NOTE:** The requirements below are sufficient for evaluation purposes only. See the +**NOTE:** The following requirements are sufficient for evaluation purposes only. See the [Requirements to Install Netwrix Data Classification](/docs/dataclassification/5.6.2/deployment/requirements/requirements_intro.md) topic for complete information on the requirements for installing Netwrix Data Classification in production environments. ## Software Requirements -The table below lists the minimum software requirements for the virtual appliance deployment: +The following table lists the minimum software requirements for the virtual appliance deployment: | Virtual Environment | Requirements | | ------------------- | -------------------------------------------------------------------- | diff --git a/docs/dataclassification/5.6.2/deployment/configinfrastructure/config_infrastructure_intro.md b/docs/dataclassification/5.6.2/deployment/configinfrastructure/config_infrastructure_intro.md index 4b65398499..7be48c0555 100644 --- a/docs/dataclassification/5.6.2/deployment/configinfrastructure/config_infrastructure_intro.md +++ b/docs/dataclassification/5.6.2/deployment/configinfrastructure/config_infrastructure_intro.md @@ -9,7 +9,7 @@ sidebar_position: 70 Successful crawling requires a certain configuration of native audit settings in the audited environment. Configuring your IT infrastructure may also include enabling certain built-in Windows services, etc. Proper audit configuration is required to ensure audit data integrity, otherwise your -change reports may contain warnings, errors or incomplete audit data. +change reports may contain warnings, errors, or incomplete audit data. Review the following for additional information: diff --git a/docs/dataclassification/5.6.2/deployment/configinfrastructure/config_nfs_fs.md b/docs/dataclassification/5.6.2/deployment/configinfrastructure/config_nfs_fs.md index b460c94c83..5af5d096e5 100644 --- a/docs/dataclassification/5.6.2/deployment/configinfrastructure/config_nfs_fs.md +++ b/docs/dataclassification/5.6.2/deployment/configinfrastructure/config_nfs_fs.md @@ -6,11 +6,10 @@ sidebar_position: 40 # Configure NFS File Share for Crawling -To enable processing Network File System (NFS) file shares it is necessary to enable specific -Windows features. The steps to enable these features differ depending on operating system of the -computer where Netwrix Data Classification is installed. +To process Network File System (NFS) file shares, enable specific Windows features. The steps differ +depending on the operating system where Netwrix Data Classification is installed. -**NOTE:** Prior to configuration, consider the following: +**NOTE:** Before configuration, consider the following: - NFS File shares are only supported from servers running Windows Server 2012 or later (or Windows 10) @@ -21,7 +20,7 @@ computer where Netwrix Data Classification is installed. Add the Folder source as described in the File System section. -**NOTE:** Do not specify username and password while adding data source. +**NOTE:** Don't specify username and password while adding data source. ## To configure Windows Server 2012 Onward diff --git a/docs/dataclassification/5.6.2/deployment/configinfrastructure/config_spo_modern_auth.md b/docs/dataclassification/5.6.2/deployment/configinfrastructure/config_spo_modern_auth.md index 0370ade5bf..b8e122efdd 100644 --- a/docs/dataclassification/5.6.2/deployment/configinfrastructure/config_spo_modern_auth.md +++ b/docs/dataclassification/5.6.2/deployment/configinfrastructure/config_spo_modern_auth.md @@ -28,17 +28,15 @@ Netwrix Data Classification and other services. 1. Open Certificate Manager. 2. Go to search and type in **Certificate**. 3. Choose **Manage Computer Certificates**. - 4. Right-click on the certificate you created. + 4. Right-click the certificate you created. 5. Select **All Tasks**, **Export**. - 6. On the displayed message, click _**_Do not export private key__**. + 6. On the displayed message, click _**_Don't export private key__**. 7. Set file type to _DER-encoded binary x.509_ (CER). 8. Chose location to save the certificate and name it as **leave.cer**. You can later upload it to the Microsoft Entra ID admin center. ## Step 2: Create and Register a New App in Microsoft Entra ID -Follow the steps to register a new Microsoft Entra ID application. - 1. Sign into the **Microsoft 365 Admin Center** (with your _Global Administrator_, _Application Administrator_ or _Cloud Application Administrator_ account). 2. Search for and select **Microsoft Entra ID**. @@ -59,7 +57,7 @@ Follow the steps to register a new Microsoft Entra ID application. ![mfa_0365_2](/images/dataclassification/5.6.2/config_infrastructure/mfa_0365_2.webp) -8. Copy your application ID from the Overview section it to a safe location. +8. Copy your application ID from the Overview section to a safe location. ## Step 3: Grant Required Permissions @@ -74,11 +72,11 @@ Microsoft Entra ID applications can be assigned _Delegated_ or _Application_ per For the newly created app, you should use _Application_ permissions. **NOTE:** By default, a new application is granted one delegated permission for **Microsoft Graph -API** – **User.Read**. It is not required and can be removed. +API** – **User.Read**. It isn't required and can be removed. Do the following: -When found, click on the entry and proceed with adding the necessary permissions. The steps from +When found, click the entry and proceed with adding the necessary permissions. The steps from here on remain the same, so in most cases you would need the Application permissions entry, and the relevant set of permissions therein. diff --git a/docs/dataclassification/5.6.2/deployment/configinfrastructure/configure_box.md b/docs/dataclassification/5.6.2/deployment/configinfrastructure/configure_box.md index b767b78cde..3f793e6597 100644 --- a/docs/dataclassification/5.6.2/deployment/configinfrastructure/configure_box.md +++ b/docs/dataclassification/5.6.2/deployment/configinfrastructure/configure_box.md @@ -23,15 +23,15 @@ Box management portal. ![box_lic_plans_thumb_0_0](/images/dataclassification/5.6.2/config_infrastructure/box_lic_plans_thumb_0_0.webp) -2. Make sure you have configured a valid Google account (with multi-factor authentication supported) +2. Ensure you have configured a valid Google account (with multi-factor authentication supported) and registered it as a _Box Developer Account_. This account is needed to create an app that Netwrix Data Classification will use for interaction with Box API. For more information on the custom apps and Box API, refer to [this article](https://developer.box.com/guides/authentication/sso/). -**NOTE:** Account with multi-factor authentication will be required for private/public keys creation -and usage, so if such authentication is not enabled, the program will display a warning message and -suggest to configure the necessary settings. +**NOTE:** You must use an account with multi-factor authentication for private/public keys creation +and usage. If such authentication isn't enabled, the program displays a warning message and +suggests configuring the necessary settings. ## Procedure Steps @@ -61,7 +61,7 @@ on the Netwrix Data Classification side and described in the 8. Select View Your App on the confirmation screen. 9. Open the **Configuration** window by clicking the related item on the left. - Navigate to Application Access and make sure that level is set to Enterprise. Click **Save + Navigate to Application Access and ensure that level is set to Enterprise. Click **Save changes**. 10. Navigate to **Advanced Features** and turn ON both switches: **Perform Actions as User** and @@ -80,7 +80,7 @@ on the Netwrix Data Classification side and described in the 12. You will be notified about downloading a JSON file with all configuration settings of your app. - **IMPORTANT!** Since Box does not store any private keys, this file contains the only copy of + **IMPORTANT!** Since Box doesn't store any private keys, this file contains the only copy of your private key, so store it securely. ### Step 2. Authorize the App diff --git a/docs/dataclassification/5.6.2/deployment/configinfrastructure/configure_gdrive.md b/docs/dataclassification/5.6.2/deployment/configinfrastructure/configure_gdrive.md index be792db79e..2808524386 100644 --- a/docs/dataclassification/5.6.2/deployment/configinfrastructure/configure_gdrive.md +++ b/docs/dataclassification/5.6.2/deployment/configinfrastructure/configure_gdrive.md @@ -12,10 +12,10 @@ You will need to create a service account and authorize it to access data in ind Drives on behalf of users using the Google Drive API. Depending on your drive type, do the following: -- [Сonfiguring G Suite for Crawling](#сonfiguring-g-suite-for-crawling) +- [Configuring G Suite for Crawling](#configuring-g-suite-for-crawling) - [Configuring Personal Google Drive for Crawling](#configuring-personal-google-drive-for-crawling) -## Сonfiguring G Suite for Crawling +## Configuring G Suite for Crawling In Google Cloud Platform web console: @@ -32,19 +32,17 @@ In G Suite Admin Console: To configure G Suite for crawling -**IMPORTANT!** Google administrative interfaces tend to change over time, so refer to the following -guide for up-to-data instructions on creating OAuth 2.0 service accounts: -[Using OAuth 2.0 for Server to Server Applications](https://developers.google.com/identity/protocols/OAuth2ServiceAccount). +**IMPORTANT!** Google administrative interfaces tend to change over time. See [Using OAuth 2.0 for Server to Server Applications](https://developers.google.com/identity/protocols/OAuth2ServiceAccount) for up-to-date instructions on creating OAuth 2.0 service accounts. Review the following for additional information: | To... | Do... | | ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Create a new project | 1. Navigate to https://console.developers.google.com (Google Cloud Platform web console) while logged in as a G-Suite administrator within the domain to be crawled (if the user is not added within the correct domain then the correct data will not be identified). 2. Create a new project. | +| Create a new project | 1. Navigate to https://console.developers.google.com (Google Cloud Platform web console) while logged in as a G-Suite administrator within the domain to be crawled (if the user isn't added within the correct domain then the correct data won't be identified). 2. Create a new project. | | Select Application type | 1. Once a new project has been created, navigate to APIs&Services → OAuth consent screen. 2. Set User type to "_Internal_". 3. Provide the name for new application. 4. Click Save. | -| Create a new service account | 1. In Google Cloud Platform web console, navigate to Credentials and click Create Credentials. 2. Then, click Service account. 3. Create service account as described in Google official [article](https://developers.google.com/identity/protocols/OAuth2ServiceAccount#article). 4. On the Grant this service account access to project (optional) step, do not select any roles. 5. On the Grant users access to this service account (optional) step, do not grant any user access. Click Done. | +| Create a new service account | 1. In Google Cloud Platform web console, navigate to Credentials and click Create Credentials. 2. Then, click Service account. 3. Create service account as described in Google official [article](https://developers.google.com/identity/protocols/OAuth2ServiceAccount#article). 4. On the Grant this service account access to project (optional) step, don't select any roles. 5. On the Grant users access to this service account (optional) step, don't grant any user access. Click Done. | | Create a service account key | 1. On the Service accounts section, click edit on the account you want to create a key for. 2. Click ![add_key_icon](/images/dataclassification/5.6.2/config_infrastructure/add_key_icon.webp) icon under Actions and select Create key. 3. In the Create private key for `` dialog, select JSON format, and download the file to a known location as it will be required later. **NOTE:** Your new public / private keypair is generated and downloaded to your machine; it serves as the only copy of this key. You are responsible for storing it securely. If you lose this keypair, you will need to generate a new one. | -| Delegate domain-wide authority to the service account | 1. On the Service accounts section, select your service account and click Edit. 2. Click the Show Domain-Wide Delegation link and tick the Enable G Suite Domain-wide Delegation checkbox. 3. Click Save. 4. Once completed, review the "_Domain wide delegation_" column for this account and make sure that the delegation enabled. 5. Click the View Client ID link. 6. Copy your Client ID, you will need it later. | +| Delegate domain-wide authority to the service account | 1. On the Service accounts section, select your service account and click Edit. 2. Click the Show Domain-Wide Delegation link and tick the Enable G Suite Domain-wide Delegation checkbox. 3. Click Save. 4. Once completed, review the "_Domain wide delegation_" column for this account and ensure that the delegation enabled. 5. Click the View Client ID link. 6. Copy your Client ID, you will need it later. | | Enable Google Drive API | 1. In Google Cloud Platform web console, navigate to the API Dashboard and select Enable APIs and Services (if APIs have not previously been enabled). 2. Search for Google Drive API and click Enable (or Manage). 3. Search for Admin SDK API and click Enable (or Manage). 4. Switch to G Suite Admin Console. 5. Navigate to Security → API Controls → Manage Domain-wide Delegation within the Google admin portal. 6. Set the client name to the Client ID you copied on the previous step. 7. Set the API scopes and select Authorize: - https://www.googleapis.com/auth/drive - https://www.googleapis.com/auth/admin.directory.user | ## Configuring Personal Google Drive for Crawling @@ -65,9 +63,9 @@ Review the following for additional information: | To... | Do... | | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Create a new project | 1. Navigate to https://console.developers.google.com Google Cloud Platform web console) while logged in as a G-Suite administrator within the domain to be crawled (if the user is not added within the correct domain then the correct data will not be identified). 2. Create a new project. | +| Create a new project | 1. Navigate to https://console.developers.google.com (Google Cloud Platform web console) while logged in as a G-Suite administrator within the domain to be crawled (if the user isn't added within the correct domain then the correct data won't be identified). 2. Create a new project. | | Select Application type | 1. Once a new project has been created, navigate to APIs&Services → OAuth consent screen. 2. Set User type to "_Internal_". 3. Provide the name for new application. 4. Click Save. | -| Create a new service account | 1. In Google Cloud Platform web console, navigate to IAM & Admin→Service Accounts. 2. Create service account as described in Google official [article](https://developers.google.com/identity/protocols/OAuth2ServiceAccount#article). 3. On the Grant this service account access to project (optional) step, do not select any roles. 4. On the Grant users access to this service account (optional) step, do not grant any user access. Click Done. | +| Create a new service account | 1. In Google Cloud Platform web console, navigate to IAM & Admin→Service Accounts. 2. Create service account as described in Google official [article](https://developers.google.com/identity/protocols/OAuth2ServiceAccount#article). 3. On the Grant this service account access to project (optional) step, don't select any roles. 4. On the Grant users access to this service account (optional) step, don't grant any user access. Click Done. | | Create a service account key | 1. On the Service accounts page, select the account you want to create a key for. 2. Click ![add_key_icon](/images/dataclassification/5.6.2/config_infrastructure/add_key_icon.webp) icon under Actions and select Create key. 3. In the Create private key for `` dialog, select JSON format, and download the file to a known location as it will be required later. **NOTE:** Your new public/private keypair is generated and downloaded to your machine; it serves as the only copy of this key. You are responsible for storing it securely. If you lose this keypair, you will need to generate a new one. | | Enable Google Drive API | 1. In Google Cloud Platform web console, navigate to the API Dashboard and select Enable APIs and Services (if APIs have not previously been enabled). 2. Search for Google Drive API and click Enable (or Manage). | -| Allow sharing for your files and folders | 1. Navigate to each Google Drive account that you wish to crawl 2. Right click each file / folder you wish to crawl and select Share… 3. Enter email address of the service account you created on the Create a new service account step. To view email address, do the following: - In Google API console, navigate to IAM & Admin → Service Accounts. - Select your service account and click Edit. - Review email address in the Email field. 4. If you wish to write classifications or apply workflows, ensure that Can organize, add, &edit option is selected (expand the menu to the right of People field). | +| Allow sharing for your files and folders | 1. Navigate to each Google Drive account that you want to crawl 2. Right click each file / folder you want to crawl and select Share… 3. Enter email address of the service account you created on the Create a new service account step. To view email address, do the following: - In Google API console, navigate to IAM & Admin → Service Accounts. - Select your service account and click Edit. - Review email address in the Email field. 4. If you want to write classifications or apply workflows, ensure that Can organize, add, &edit option is selected (expand the menu to the right of People field). | diff --git a/docs/dataclassification/5.6.2/deployment/configinfrastructure/configureexchange/configure_exchange.md b/docs/dataclassification/5.6.2/deployment/configinfrastructure/configureexchange/configure_exchange.md index f5c45a2879..b5aa65772b 100644 --- a/docs/dataclassification/5.6.2/deployment/configinfrastructure/configureexchange/configure_exchange.md +++ b/docs/dataclassification/5.6.2/deployment/configinfrastructure/configureexchange/configure_exchange.md @@ -8,14 +8,13 @@ sidebar_position: 30 When preparing your Exchange Server for data classification, consider that for on-premise Exchange Server, Basic authentication is supported for crawling account, and for Exchange Online you can use -either Modern authentication or Basic authentication. Both scenarios are described in the sections -below. +either Modern authentication or Basic authentication. Both scenarios are described in the following sections. ## Basic Authentication This method is supported for Exchange Online and on-premise Exchange organizations. You should configure sufficient permissions that will allow the crawling account to impersonate the mailboxes -that you wish to crawl. This requires the setup of two permissions: +that you want to crawl. This requires the setup of two permissions: - ApplicationImpersonation—Allows the crawling account to impersonate each of the mailboxes / users configured for collection @@ -56,18 +55,18 @@ Review the related procedure that corresponds to your Exchange deployment: ADMINUSERNAME **NOTE:** If crawling Microsoft Office 365 for Small Business or many hosted Exchange systems, then -it is not possible to setup Application Impersonation. +it isn't possible to set up Application Impersonation. ## Modern Authentication Starting with version 5.5.3, Netwrix Data Classification allows for crawling Microsoft Exchange Online organization mailboxes using Modern authentication. For that, it uses an Azure AD application -which can leverage Microsoft API to connect to Exchange Online organization. +that uses Microsoft API to connect to Exchange Online organization. **NOTE:** You need to use an admin user name with Modern Authentication. You should configure sufficient permissions that will allow the crawling account to impersonate the -mailboxes that you wish to crawl. This requires the setup of two permissions: +mailboxes that you want to crawl. This requires the setup of two permissions: - ApplicationImpersonation—Allows the crawling account to impersonate each of the mailboxes / users configured for collection diff --git a/docs/dataclassification/5.6.2/deployment/configinfrastructure/configureexchange/create_azureapp_exchangeonline_mfa.md b/docs/dataclassification/5.6.2/deployment/configinfrastructure/configureexchange/create_azureapp_exchangeonline_mfa.md index f8508aa342..b8f9bac818 100644 --- a/docs/dataclassification/5.6.2/deployment/configinfrastructure/configureexchange/create_azureapp_exchangeonline_mfa.md +++ b/docs/dataclassification/5.6.2/deployment/configinfrastructure/configureexchange/create_azureapp_exchangeonline_mfa.md @@ -24,7 +24,7 @@ Netwrix Data Classification and other services. 2. Go to the **Details** tab. 3. Select **Copy to File**. - **NOTE:** Do not export private key. + **NOTE:** Don't export private key. 4. Set file type to _DER-encoded CER_. @@ -62,18 +62,18 @@ Azure AD applications can be assigned _Delegated_ or _Application_ permissions: For the newly created app, you should use _Application_ permissions. **NOTE:** By default, a new application is granted one delegated permission for **Microsoft Graph -API** – **User.Read**. It is not required and can be removed. +API** – **User.Read**. It isn't required and can be removed. Do the following: -When found, click on the entry and proceed with adding the necessary permissions. The steps from +When found, click the entry and proceed with adding the necessary permissions. The steps from here on remain the same, so in most cases you would need the Application permissions entry, and the relevant set of permissions therein (such as full_access_as_app for EWS OAuth, Exchange.ManageAsApp for CBA). Select the relevant entries, hit the Add permissions -1. At the top of the **Request API permissions** pane, click the **APIs my organization uses** tab +1. At the top of the **Request API permissions** pane, click the **APIs your organization uses** tab and search for _Office 365 Exchange Online_. -2. Click on the _Office 365 Exchange Online_ entry in the list of apps found. +2. Click the _Office 365 Exchange Online_ entry in the list of apps found. 3. Proceed with adding the permissions for this app: select **Application permissions** and then select **full_access_as_app**. 4. Click **Add permissions**. diff --git a/docs/dataclassification/5.6.2/deployment/configinfrastructure/mip_configure_infrastructure.md b/docs/dataclassification/5.6.2/deployment/configinfrastructure/mip_configure_infrastructure.md index 0482fb9746..32236a7fae 100644 --- a/docs/dataclassification/5.6.2/deployment/configinfrastructure/mip_configure_infrastructure.md +++ b/docs/dataclassification/5.6.2/deployment/configinfrastructure/mip_configure_infrastructure.md @@ -20,7 +20,7 @@ Review the following for additional information: | To... | Do... | | -------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Set up application registration in Microsoft Azure | Run through the steps described in the following Microsoft article: [Register a client application with Azure Active Directory](https://docs.microsoft.com/en-us/information-protection/develop/setup-configure-mip#register-a-client-application-with-azure-active-directory). Make sure that the following API permissions are set (and have been granted for the tenant): - Azure Rights Management Services - Content.DelegatedWriter - Content.Writer - Microsoft.Graph - User.Read - Microsoft Information Protection Sync Service - UnifiedPolicy.Tenant.Read | +| Set up application registration in Microsoft Azure | Run through the steps described in the following Microsoft article: [Register a client application with Azure Active Directory](https://docs.microsoft.com/en-us/information-protection/develop/setup-configure-mip#register-a-client-application-with-azure-active-directory). Ensure that the following API permissions are set (and have been granted for the tenant): - Azure Rights Management Services - Content.DelegatedWriter - Content.Writer - Microsoft.Graph - User.Read - Microsoft Information Protection Sync Service - UnifiedPolicy.Tenant.Read | | Import certificate in IIS | You can generate custom certificate in IIS which is enough for test and evaluation purposes. However, for production environments, Netwrix recommends importing certificate used by your company. Contact your security administrator to get the certificate. **NOTE:** This certificate need to be installed to the computer where Netwrix Data Classification and all its services run. | -| Export .CER file | 1. In Internet Information Services (IIS) Manager, select the certificate you loaded. 2. Select View under Actions. 3. Go to Details tab and select Copy to File. 4. Proceed with Certificate Export wizard. 5. On the Export Private Key step, select Do not export the private key. 6. On the Export File Format step, select DER encoded binary (.CER). 7. On the File to Export step, select path to store the file. 8. Review export settings and click Finish. | +| Export .CER file | 1. In Internet Information Services (IIS) Manager, select the certificate you loaded. 2. Select View under Actions. 3. Go to Details tab and select Copy to File. 4. Proceed with Certificate Export wizard. 5. On the Export Private Key step, select Don't export the private key. 6. On the Export File Format step, select DER encoded binary (.CER). 7. On the File to Export step, select path to store the file. 8. Review export settings and click Finish. | | Upload the .CER file to Azure | 1. Open [Microsoft Azure portal](https://azure.microsoft.com/en-gb/features/azure-portal/) and navigate to Azure Active Directory → App Registrations. 2. Select application you registered on the Set up application registration in Microsoft Azure step. 3. Navigate to Certificates & secrets on the left. 4. Click Upload certificate. 5. Browse for .CER file you exported and click Add. 6. Copy certificate thumbprint to a known location as it will be required later. | diff --git a/docs/dataclassification/5.6.2/deployment/deploymentplan/datastorages/data_storages.md b/docs/dataclassification/5.6.2/deployment/deploymentplan/datastorages/data_storages.md index d36563a0a4..5b8f3b1946 100644 --- a/docs/dataclassification/5.6.2/deployment/deploymentplan/datastorages/data_storages.md +++ b/docs/dataclassification/5.6.2/deployment/deploymentplan/datastorages/data_storages.md @@ -6,7 +6,7 @@ sidebar_position: 20 # Data Storages and Sizing -Netwrix Data Classification utilizes two data storages: +Netwrix Data Classification uses two data storages: - NDC SQL database — SQL Server database that stores product configuration and metadata for the data sources. @@ -15,7 +15,7 @@ Netwrix Data Classification utilizes two data storages: ### NDC SQL database -Make sure you have NDC Server and **NDC SQL database** deployed on different machines. +Ensure you have NDC Server and **NDC SQL database** deployed on different machines. It is recommended to create the NDC SQL database on a dedicated SQL Server instance. @@ -33,15 +33,15 @@ It is recommended to create the NDC SQL database on a dedicated SQL Server inst - **File growth**: _128 MB_ - recommended value for small to medium environment, _512 MB_ - for large environment, i.e. if planning to index data sources containing 1, 000, 000+ objects. - **Maximum File Size** - select _Unlimited_. -- Make sure that the **Recovery model** for this database is set to _Simple_. Do not change the - recovery model — to avoid log files growth. +- Set the **Recovery model** for this database to _Simple_. Don't change the + recovery model to avoid log file growth. ### NDC Index Required disk space for the NDC Index file storage will depend, in particular, on the data -processing mode you plan to use (_No Index_, _Keyword_ or _Compound Term_). +processing mode you plan to use (_No Index_, _Keyword_, or _Compound Term_). -As a rule of thumb, required space can be calculated as 35% of data you plan to be indexed. For +As a general guideline, required space can be calculated as 35% of data you plan to be indexed. For example, if you have 45 GB of files, they will require up to 15 GB for the NDC Index files. ## Scalability and Performance @@ -56,7 +56,6 @@ environments can be ranged as follows: | Up to 64, 000, 000 | Large-size environment | | | More than 64, 000, 000 | Extra-large environment | System architect's assistance is required for deployment planning requires | -Again, consider that for the large-size and extra-large environments, it is strongly recommended to -configure a cluster of several NDC Servers and apply DQS mode to these clustered servers. See +For large-size and extra-large environments, strongly consider configuring a cluster of several NDC Servers and applying DQS mode to these clustered servers. See [Configuring NDC Servers Cluster and Load Balancing with DQS Mode](/docs/dataclassification/5.6.2/deployment/deploymentplan/ndcserverclient/distributed_query_server_mode.md) for details. diff --git a/docs/dataclassification/5.6.2/deployment/deploymentplan/ndcserverclient/distributed_query_server_mode.md b/docs/dataclassification/5.6.2/deployment/deploymentplan/ndcserverclient/distributed_query_server_mode.md index ab6e31443e..da63e55cae 100644 --- a/docs/dataclassification/5.6.2/deployment/deploymentplan/ndcserverclient/distributed_query_server_mode.md +++ b/docs/dataclassification/5.6.2/deployment/deploymentplan/ndcserverclient/distributed_query_server_mode.md @@ -6,15 +6,15 @@ sidebar_position: 10 # Configuring NDC Servers Cluster and Load Balancing with DQS Mode -The Distributed Query Server (DQS) mode allows you to balance the load between multiple Netwrix Data -Classification Servers (NDC Servers) while data collection, indexing and classification. This +The Distributed Query Server (DQS) mode balances the load between multiple Netwrix Data +Classification Servers (NDC Servers) while data collection, indexing, and classification. This approach is strongly recommended if you need to process large data volumes, for example: - File Servers—Up to 64 m objects per cluster of 4 servers. - SharePoint—Up to 32 m objects per cluster of 4 servers. To apply Distributed Query Server mode, you need to arrange your NDC Servers in a 'cluster' for load -distribution, as described below. Each clustered NDC Server will store its own set of .CSE files — +distribution, as described in the following section. Each clustered NDC Server will store its own set of .CSE files — that is, **NDC Index** will be a distributed index. To assemble and combine data required for the search results, each NDC Server will automatically communicate with the other clustered servers. @@ -29,9 +29,9 @@ DQS mode can be configured via the administrative web console. If you want to implement DQS configuration for your NDC deployment, consider the following: -- This action cannot easily be undone, so before applying the DQS mode, take a full backup of your +- This action can't easily be undone, so before applying the DQS mode, take a full backup of your NDC deployment. Also, read the related documentation sections thoroughly before you start. -- Make sure all servers you plan to add to the DQS cluster have proper network connection and are +- Ensure all servers you plan to add to the DQS cluster have proper network connection and are visible to each other across the network. Adjust firewall settings if necessary. - Initially, all existing documents will be ‘allocated’ to the first server in the 'cluster' and then re-distributed across all configured servers. @@ -47,7 +47,7 @@ To arrange NDC Servers cluster and apply DQS mode 3. Navigate to Settings → Utilities → DQS. 4. Select Enable DQS. - **NOTE:** Once the DQS mode is enabled, you cannot roll back your configuration. Netwrix + **NOTE:** When the DQS mode is enabled, you can't roll back your configuration. Netwrix strongly recommends to ensure that you have taken a full backup of your environment. If ready, confirm the DOS enablement operation when prompted. @@ -67,7 +67,7 @@ To arrange NDC Servers cluster and apply DQS mode 6. Click **Save** to close the dialog. 7. Prepare to install other Netwrix Data Classification Server instances, assuming each server - requires a dedicated machine. Make sure they meet the + requires a dedicated machine. Ensure they meet the [Hardware Requirements](/docs/dataclassification/5.6.2/deployment/requirements/hardware_requirements.md) and general [Software Requirements](/docs/dataclassification/5.6.2/deployment/requirements/software_requirements.md) @@ -80,14 +80,13 @@ To arrange NDC Servers cluster and apply DQS mode **NOTE:** Ignore the confirmation dialog on the existing schema in the selected SQL database. 10. Complete the installation. -11. Repeat steps 2 - 6 for every NDC Server, then review the list of servers to make sure the new +11. Repeat steps 2 - 6 for every NDC Server, then review the list of servers to ensure the new server was included. ![dqs_servers_list_thumb_0_0](/images/dataclassification/5.6.2/deployment/dqs_servers_list_thumb_0_0.webp) -12. If you were configuring the DQS mode for the existing NDC deployment, you will be prompted to - re-collect data from the data sources —in order to re-distribute the content index across all - NDC Servers in the cluster. +12. If you configure DQS mode for the existing NDC deployment, re-collect data from the data sources to + re-distribute the content index across all NDC Servers in the cluster. **NOTE:** To force re-distribution when necessary, you can use the Re-Collect command available after clicking **Run Cleaner** button on the **Settings > Core > Collector** tab. diff --git a/docs/dataclassification/5.6.2/deployment/deploymentplan/ndcserverclient/ndc_server_client.md b/docs/dataclassification/5.6.2/deployment/deploymentplan/ndcserverclient/ndc_server_client.md index a2a29c87b6..d89a72dce2 100644 --- a/docs/dataclassification/5.6.2/deployment/deploymentplan/ndcserverclient/ndc_server_client.md +++ b/docs/dataclassification/5.6.2/deployment/deploymentplan/ndcserverclient/ndc_server_client.md @@ -10,7 +10,7 @@ Netwrix Data Classification **Server** can be deployed on a physical server or o in the virtualized environment on VMware or Microsoft Hyper-V platform. When planning for NDC Server, consider a significant CPU load during data processing. Thus, -installing NDC Server on a highly-loaded production machine is not recommended. For more +installing NDC Server on a highly-loaded production machine isn't recommended. For more information, refer to [Hardware Requirements](/docs/dataclassification/5.6.2/deployment/requirements/hardware_requirements.md). @@ -25,10 +25,9 @@ machine image with pre-installed Netwrix Data Classification on Generalized Wind Remember that for production environments, your NDC Server and database server must meet the [Requirements to Install Netwrix Data Classification](/docs/dataclassification/5.6.2/deployment/requirements/requirements_intro.md). -Virtual appliance configuration is insufficient for production and is not recommended for that +Virtual appliance configuration is insufficient for production and isn't recommended for that purpose. -To balance the load while indexing and classifying data in the large-size and extra-large -environments (i.e. with over ≥ 16 mln objects to process), it is strongly recommended to deploy -several NDC Servers and configure **Distributed Query Server** mode for them. +To balance the load while indexing and classifying data in large-size and extra-large +environments (with over 16 million objects to process), deploy multiple NDC Servers and configure **Distributed Query Server** mode for them. [See Configuring NDC Servers Cluster and Load Balancing with DQS Mode for more information.](/docs/dataclassification/5.6.2/deployment/deploymentplan/ndcserverclient/distributed_query_server_mode.md) diff --git a/docs/dataclassification/5.6.2/deployment/initialconfig/initial_config_health.md b/docs/dataclassification/5.6.2/deployment/initialconfig/initial_config_health.md index 7e839e032e..9c4a4ec2da 100644 --- a/docs/dataclassification/5.6.2/deployment/initialconfig/initial_config_health.md +++ b/docs/dataclassification/5.6.2/deployment/initialconfig/initial_config_health.md @@ -6,7 +6,7 @@ sidebar_position: 50 # Configure Health Alerting -On this step, you will be prompted to email settings for health reporting and select immediate +On this step, configure email settings for health reporting and select immediate health alerts. ![initial_config_health](/images/dataclassification/5.6.2/deployment/initial_config_health.webp) @@ -16,6 +16,6 @@ Complete the following fields: | Setting | Description | | --------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Would you like to configure Health Reporting? | Select Setup now if you want to receive health alerts. You can do it later in the communication settings area. [See System Health for more information.](/docs/dataclassification/5.6.2/dashboards.md#system-health) | -| Who should the email be sent from? | Select a user registered in Netwrix Data Classificationadministrative web console in the field or go to the Specific recipients below and specify one or more email addresses outside your organization. | -| What sort of immediate alerts should be sent? | Select the appropriate alerting level: do not receive any alerts at all, receive errors only, or get both: emails for errors and warnings. [See System Health for more information.](/docs/dataclassification/5.6.2/dashboards.md#system-health) | +| Who should the email be sent from? | Select a user registered in Netwrix Data Classification administrative web console in the field, or go to the Specific recipients field and specify one or more email addresses outside your organization. | +| What sort of immediate alerts should be sent? | Select the appropriate alerting level: don't receive any alerts at all, receive errors only, or get both: emails for errors and warnings. [See System Health for more information.](/docs/dataclassification/5.6.2/dashboards.md#system-health) | | Should a daily health summary be sent? | Select whether you want to receive daily summary on the product health. | diff --git a/docs/dataclassification/5.6.2/deployment/initialconfig/initial_config_modes.md b/docs/dataclassification/5.6.2/deployment/initialconfig/initial_config_modes.md index c0cb60b142..9a26e1f7c9 100644 --- a/docs/dataclassification/5.6.2/deployment/initialconfig/initial_config_modes.md +++ b/docs/dataclassification/5.6.2/deployment/initialconfig/initial_config_modes.md @@ -12,19 +12,19 @@ At this step of the wizard, select processing (indexing) mode for your environme For starter and evaluation purposes, select Keyword mode. -Review the short description below and select mode: +Review the following descriptions and select a mode: ## No Index -In this mode, the core search index will be disabled, heavily reducing the disk space requirements +In this mode, the system disables the core search index, heavily reducing the disk space requirements for the CSE files and improving overall document throughput for classification. Under this mode -Search is not available and Browse functionality is not subject to security trimming. Recommended +Search isn't available and Browse functionality isn't subject to security trimming. Recommended for data discovery, data security governance and compliance use cases. ## Keyword -In this mode the search index will be created; however, disk space required for the core search -index will be of medium size. Both **Browse** and **Search** by keyword will be supported. Overall +In this mode, the system creates a search index; however, disk space required for the core search +index is of medium size. Both **Browse** and **Search** by keyword will be supported. Overall throughput is capable of supporting large number of documents (> 1M). Recommended for compliance, data discovery and classification rules tuning. diff --git a/docs/dataclassification/5.6.2/deployment/initialconfig/initial_config_summary.md b/docs/dataclassification/5.6.2/deployment/initialconfig/initial_config_summary.md index ea6755fbf1..449437001f 100644 --- a/docs/dataclassification/5.6.2/deployment/initialconfig/initial_config_summary.md +++ b/docs/dataclassification/5.6.2/deployment/initialconfig/initial_config_summary.md @@ -6,7 +6,7 @@ sidebar_position: 60 # Review Your Configuration -On this step, review your configuration. Once you complete the wizard, you can: +On this step, review your configuration. After you complete the wizard, you can: - Add a Source - Add a Taxonomy diff --git a/docs/dataclassification/5.6.2/deployment/initialconfig/initial_config_taxonomies.md b/docs/dataclassification/5.6.2/deployment/initialconfig/initial_config_taxonomies.md index 35af972d0f..7f974b6c09 100644 --- a/docs/dataclassification/5.6.2/deployment/initialconfig/initial_config_taxonomies.md +++ b/docs/dataclassification/5.6.2/deployment/initialconfig/initial_config_taxonomies.md @@ -6,7 +6,7 @@ sidebar_position: 30 # Add Taxonomy -On this step, you are prompted to load predefined taxonomies. +On this step, load predefined taxonomies. ![processing_settings_taxonomies](/images/dataclassification/5.6.2/deployment/processing_settings_taxonomies.webp) diff --git a/docs/dataclassification/5.6.2/deployment/initialconfig/initial_config_users.md b/docs/dataclassification/5.6.2/deployment/initialconfig/initial_config_users.md index 3391a9ff0e..3150a60531 100644 --- a/docs/dataclassification/5.6.2/deployment/initialconfig/initial_config_users.md +++ b/docs/dataclassification/5.6.2/deployment/initialconfig/initial_config_users.md @@ -6,7 +6,7 @@ sidebar_position: 40 # Security -On this step, you are prompted to restrict access to administrative web console by adding users. +On this step, restrict access to the administrative web console by adding users. ![initial_config_users](/images/dataclassification/5.6.2/deployment/initial_config_users.webp) @@ -15,7 +15,7 @@ On this step, you are prompted to restrict access to administrative web console **NOTE:** Netwrix recommends enabling this option. - When selected, you are prompted to add super users. Type the name of the new user and click + on + When selected, add super users. Enter the name of the new user and click + on the right. -- Allow access for all users – select to allow any user access administrative web console. +- Allow access for all users – select to allow any user access to the administrative web console. diff --git a/docs/dataclassification/5.6.2/deployment/installation/installation.md b/docs/dataclassification/5.6.2/deployment/installation/installation.md index 20de970312..f8e6b5fa4d 100644 --- a/docs/dataclassification/5.6.2/deployment/installation/installation.md +++ b/docs/dataclassification/5.6.2/deployment/installation/installation.md @@ -48,8 +48,8 @@ sidebar_position: 50 Classification's Services files. For example, _C:\Program Files\NDC Services._ - Provide user name and password for the product services service account. - **NOTE:** This account is granted the Logon as a service privilege automatically on the - computer where Netwrix Data Classification is going to be installed. + **NOTE:** The system automatically grants this account the Logon as a service privilege on the + computer where you install Netwrix Data Classification. - Select additional service options, if necessary. diff --git a/docs/dataclassification/5.6.2/deployment/installation/ndc_database.md b/docs/dataclassification/5.6.2/deployment/installation/ndc_database.md index 1433446aad..e783b8f7b0 100644 --- a/docs/dataclassification/5.6.2/deployment/installation/ndc_database.md +++ b/docs/dataclassification/5.6.2/deployment/installation/ndc_database.md @@ -7,12 +7,11 @@ sidebar_position: 10 # Configure NDC SQL database Netwrix Data Classification uses Microsoft SQL Server database as metadata storage. During -installation, you have been prompted to create a dedicated NDC SQL database on your SQL Server -instance. Upon installation completion, you need to configure it as shown below for the product to -function properly. You can create the database manually prior to the product installation—Using SQL -Server Management Studio or Transact-SQL. Refer to the following Microsoft article for detailed -instructions on how to create a new database: -[Create a Database](https://docs.microsoft.com/en-us/sql/relational-databases/databases/create-a-database). +installation, the system prompts you to create a dedicated NDC SQL database on your SQL Server +instance. Upon installation completion, you need to configure it according to the following steps for the product to +function properly. You can create the database manually before the product installation—Using SQL +Server Management Studio or Transact-SQL. See [Create a Database](https://docs.microsoft.com/en-us/sql/relational-databases/databases/create-a-database) +for detailed instructions on how to create a new database. **NOTE:** For performance purposes, Netwrix strongly recommends to separate NDC and SQL Server machine. @@ -36,7 +35,7 @@ role. | File Growth | - Recommended—128 MB. - Large environment— 512 MB. | | Maximum File Size | Select Unlimited. | -6. Go to Options page and make sure that the Recovery model parameter is set to "_Simple_". +6. Go to Options page and ensure that the Recovery model parameter is set to "_Simple_". - **NOTE:** Netwrix recommends that you do not change the recovery model to avoid log files + **NOTE:** Netwrix recommends that you don't change the recovery model to avoid log files growth. diff --git a/docs/dataclassification/5.6.2/deployment/requirements/account_reqs.md b/docs/dataclassification/5.6.2/deployment/requirements/account_reqs.md index 228543da0b..1dbcf86cdb 100644 --- a/docs/dataclassification/5.6.2/deployment/requirements/account_reqs.md +++ b/docs/dataclassification/5.6.2/deployment/requirements/account_reqs.md @@ -10,6 +10,6 @@ Netwrix Data Classification uses the following accounts: | Account | Description | | ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| **Service Account** | This account is specified during the product setup. Windows domain account that you plan to use as a service account will need the following: - Local Administrator rights on the server where Netwrix Data Classification will be installed. - Permissions to run the Windows Services and IIS Application pool. - SQL Server DBO permissions to the NDC SQL database (if using Windows Authentication to access SQL Server). After installation, this account will be automatically granted the **Logon as a service privilege** on the Netwrix Data Classification server. **NOTE:** Optionally, you can use local account instead of domain account. | +| **Service Account** | This account is specified during the product setup. Windows domain account that you plan to use as a service account will need the following: - Local Administrator rights on the server where Netwrix Data Classification will be installed. - Permissions to run the Windows Services and IIS Application pool. - SQL Server DBO permissions to the NDC SQL database (if using Windows Authentication to access SQL Server). After installation, the system automatically grants this account the **Logon as a service privilege** on the Netwrix Data Classification server. **NOTE:** Optionally, you can use local account instead of domain account. | | Crawl content | Ensure the availability of accounts with sufficient permissions to access your content sources: - SharePoint, SharePoint Online site collection— Site Collection Administrator role. - Exchange mailboxes: 1. **ApplicationImpersonation** —allows the crawling account to impersonate each of the mailboxes / users configured for collection. 2. **Mailbox Search** —allows the crawling account to enumerate mailboxes, i.e. automatic discovery of mailboxes. See [Configure Microsoft Exchange for Crawling and Classification](/docs/dataclassification/5.6.2/deployment/configinfrastructure/configureexchange/configure_exchange.md) for detailed information on configuring these permissions. - Outlook Mail Archive (PST file)— **Read** permission. - File System (SMB, NFS) — **Read** permission for the folders and files you need to crawl. - G Suite and Google Drive —service account needs permissions to read data in the individual and shared Drives on behalf of users using the Google Drive API. See [Configure G Suite and Google Drive for Crawling](/docs/dataclassification/5.6.2/deployment/configinfrastructure/configure_gdrive.md) for detailed information. - Database— **Read** permission for the database schema and data. | | Apply tagging | To use tagging, i.e. to write classification attributes back to the content file, service account will need the appropriate **Modify** permissions on the content source. | diff --git a/docs/dataclassification/5.6.2/deployment/requirements/hardware_requirements.md b/docs/dataclassification/5.6.2/deployment/requirements/hardware_requirements.md index 85a429ffa7..3febbe8e23 100644 --- a/docs/dataclassification/5.6.2/deployment/requirements/hardware_requirements.md +++ b/docs/dataclassification/5.6.2/deployment/requirements/hardware_requirements.md @@ -16,15 +16,17 @@ on the corresponding virtualization platform, in particular: - Microsoft Hyper-V - Nutanix AHV -Note that Netwrix Data Classification supports only Windows OS versions listed in the +:::note +Netwrix Data Classification supports only Windows OS versions listed in the [Software Requirements](/docs/dataclassification/5.6.2/deployment/requirements/software_requirements.md) section. +::: ## Netwrix Data Classification Server The requirements in this section apply to a single Netwrix Data Classification server. -To deploy a server cluster, make sure all planned cluster nodes meet the requirements listed below. +To deploy a server cluster, ensure all planned cluster nodes meet the requirements listed below. Consider deploying 1 Netwrix Data Classification Server per approx. 16, 000, 000 objects to process. See diff --git a/docs/dataclassification/5.6.2/deployment/requirements/software_requirements.md b/docs/dataclassification/5.6.2/deployment/requirements/software_requirements.md index 76bac119d7..d5d047c138 100644 --- a/docs/dataclassification/5.6.2/deployment/requirements/software_requirements.md +++ b/docs/dataclassification/5.6.2/deployment/requirements/software_requirements.md @@ -21,7 +21,10 @@ The following are the software requirements for Netwrix Data Classification inst - Security: - Windows Authentication - Anonymous Authentication - - **NOTE:** The Anonymous Authentication element is included in the default installation of IIS 7. Make sure you use IIS 7 and above. + +:::note +The Anonymous Authentication element is included in the default installation of IIS 7. Ensure you use IIS 7 and above. +::: - Application Development: - ISAPI Extensions - ISAPI Filters @@ -32,12 +35,18 @@ The following are the software requirements for Netwrix Data Classification inst - WCF Services: - HTTP Activation - Named Pipe Activation - - **NOTE:** To activate these features, select them under **.Net Framework Advanced Services** - **WCF Services** from **Windows Features**. + +:::note +To activate these features, select them under **.Net Framework Advanced Services** - **WCF Services** from **Windows Features**. +::: **SQL Server** - [SQL Server 2008 R2 Standard Edition](https://www.microsoft.com/en-us/download/details.aspx?id=26113) (or later). - SQL Server 2016 SP2 recommended (for better performance). -- **NOTE:** For large environments, SQL Server Enterprise edition may be needed; see [Deployment Planning](/docs/dataclassification/5.6.2/deployment/deploymentplan/overview.md). + +:::note +For large environments, SQL Server Enterprise edition may be needed; see [Deployment Planning](/docs/dataclassification/5.6.2/deployment/deploymentplan/overview.md). +::: **Visual Studio** - [Visual C++ Redistributable Packages for Visual Studio 2015](https://www.microsoft.com/en-us/download/details.aspx?id=48145) and above. diff --git a/docs/dataclassification/5.6.2/deployment/requirements/supported_content.md b/docs/dataclassification/5.6.2/deployment/requirements/supported_content.md index 24fd9f4c50..f13a99a2af 100644 --- a/docs/dataclassification/5.6.2/deployment/requirements/supported_content.md +++ b/docs/dataclassification/5.6.2/deployment/requirements/supported_content.md @@ -6,7 +6,7 @@ sidebar_position: 40 # Supported Content Types -The table below lists types of content and their default extensions supported out of the box. +The following table lists types of content and their default extensions supported by default. **NOTE:** To review the full list of available content types, navigate to Config → Text Processing → Content Type Extraction Methods. diff --git a/docs/dataclassification/5.6.2/deployment/supported_sources.md b/docs/dataclassification/5.6.2/deployment/supported_sources.md index dc2ba9d190..399c96ea4a 100644 --- a/docs/dataclassification/5.6.2/deployment/supported_sources.md +++ b/docs/dataclassification/5.6.2/deployment/supported_sources.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Supported Data Sources -The table below lists systems that can be crawled with Netwrix Data Classification: +The following table lists systems that can be crawled with Netwrix Data Classification: | Data Source | Supported Versions | | ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -15,6 +15,6 @@ The table below lists systems that can be crawled with Netwrix Data Classificati | Database | - Microsoft SQL Server 2008 and above - Oracle 10g and above | | Box | - Enterprise - Business / Business Plus - Starter | | Dropbox | - Business | -| Exchange | - Exchange Server 2010 and above - Exchange Online **NOTE:** Automatic detection, crawling and classification of multiple Exchange mailboxes from the same Exchange server (and, respectively, _Exchange Server_ content source configuration in the NDC web console) is only supported for Exchange Server 2013 or later due to limitations in the Microsoft APIs. For earlier versions, consider using _Exchange Mailbox_ content source. | +| Exchange | - Exchange Server 2010 and above - Exchange Online **NOTE:** Automatic detection, crawling, and classification of multiple Exchange mailboxes from the same Exchange server (and, respectively, _Exchange Server_ content source configuration in the NDC web console) is only supported for Exchange Server 2013 or later due to limitations in the Microsoft APIs. For earlier versions, consider using _Exchange Mailbox_ content source. | | Google Drive | - N/A | | Outlook Mail Archive | - Outlook 2010 and above | diff --git a/docs/dataclassification/5.6.2/deployment/upgrade.md b/docs/dataclassification/5.6.2/deployment/upgrade.md index f1d6d175a8..4706ea3801 100644 --- a/docs/dataclassification/5.6.2/deployment/upgrade.md +++ b/docs/dataclassification/5.6.2/deployment/upgrade.md @@ -7,13 +7,13 @@ sidebar_position: 50 # Upgrade to the Latest Version Netwrix recommends that you upgrade from the older versions of Netwrix Data Classification to the -latest version available in order to take advantage of the new features. +latest version available to take advantage of the new features. ## Preparatory Steps -Before you start the upgrade, it is strongly recommended to take the following steps: +Before upgrading, take the following steps: -1. Make sure you have .NET Framework 4.7.2 installed on the computer where Netwrix Data +1. Ensure you have .NET Framework 4.7.2 installed on the computer where Netwrix Data Classification resides. If not, download it from Microsoft website: [Download .NET Framework 4.7.2](https://dotnet.microsoft.com/download/dotnet-framework/net472). 2. Back up NDC SQL database. For that: @@ -23,7 +23,7 @@ Before you start the upgrade, it is strongly recommended to take the following s 2. In Object Explorer, right-click the database and select Tasks → Back Up. 3. Wait for the process to complete. -3. Back up the Index files. For that, it is recommended to do the following: +3. Back up the Index files by completing the following: 1. On the computer where Netwrix Data Classification is installed, start Netwrix Data Classification Service Viewer tool. Select **Stop** next to each service. 2. Locate the folder containing index files (default location is _C:\Program @@ -36,7 +36,7 @@ Before you start the upgrade, it is strongly recommended to take the following s Seamless upgrade to Netwrix Data Classification 5.6.2 is supported for versions 5.5.4 and 5.5.3. To upgrade your deployment, after taking the preparatory steps described above, run the product -setup and follow the wizard steps. When finished, all solution components will be up and running. +setup and follow the wizard steps. When finished, all solution components will be operational. If you need to upgrade from an earlier version, you should perform a staged upgrade, e.g., 5.5.0 → 5.5.1 → 5.5.6. @@ -54,6 +54,5 @@ there are several steps you may need to take after upgrading: ![update_taxonomy](/images/dataclassification/5.6.2/deployment/update_taxonomy.webp) -2. After the upgrade, indexing mode will be set to Compound Term mode. Refer to the following - Netwrix knowledge base article for instructions on how to modify default Index Processing Mode: - [How to modify Index Processing Mode](https://kb.netwrix.com/5353). +2. After the upgrade, indexing mode will be set to Compound Term mode. See [How to modify Index Processing Mode](https://kb.netwrix.com/5353) + for instructions on how to modify default Index Processing Mode. diff --git a/docs/dataclassification/5.6.2/index.md b/docs/dataclassification/5.6.2/index.md index 8bb01b6647..9c9caaa0fa 100644 --- a/docs/dataclassification/5.6.2/index.md +++ b/docs/dataclassification/5.6.2/index.md @@ -7,7 +7,7 @@ sidebar_position: 1 # Features and Benefits Netwrix Data Classification is a platform that identifies data that’s important for your -organization and enables you to reduce risk and unleash the true value of this data. +organization and lets you reduce risk and unleash the true value of this data. Powered by unique compound term processing technology, it enriches your enterprise content with accurate and consistent metadata empowering you to work with data more confidently. By seeing which diff --git a/docs/dataclassification/5.6.2/overview/how_it_works.md b/docs/dataclassification/5.6.2/overview/how_it_works.md index fb3da480d1..0faba8d442 100644 --- a/docs/dataclassification/5.6.2/overview/how_it_works.md +++ b/docs/dataclassification/5.6.2/overview/how_it_works.md @@ -47,11 +47,7 @@ The NDC Collector is implemented as a Microsoft Windows Service. The Indexer takes each new document collected by the conceptCollector and inserts the appropriate information in the NDC Index Database. -This activity can proceed concurrently with retrieval activity. However, heavy-duty indexing -activity can significantly impair retrieval performance and so, if on-going indexing is very -significant, then the conceptIndexer should either be run during quiet periods (perhaps overnight) -or alternatively new information should be constructed off-line with a batch process updating the -live index periodically. +This activity can proceed concurrently with retrieval activity. However, heavy-duty indexing activity can significantly impair retrieval performance. If ongoing indexing is very significant, run the conceptIndexer during quiet periods (perhaps overnight) or construct new information offline with a batch process that updates the live index periodically. If the Indexer is to update the live index as a background task then it is vital that this process runs on the same server where the NDC Index Database is located. @@ -78,12 +74,15 @@ use the extension “.cse” but will use the extension “.tmp” when merging The NDC Index Database files should normally be located on the same server as the Netwrix Data Classification server due to the fact that the query and indexing processes can be disk intensive. -Note that “text.cse” is not supplied since it will be created automatically when the first documents + +:::note +“text.cse” isn't supplied since it will be created automatically when the first documents are collected. +::: ## Classifier -Classifier can be used to classify documents post index time. When this option is being used then an +Classifier lets you classify documents after indexing. When this option is being used then an application can map documents to any external classification system such as a corporate taxonomy or user profiles. diff --git a/docs/dataclassification/5.6.2/overview/whatsnew.md b/docs/dataclassification/5.6.2/overview/whatsnew.md index e9bd20c5b2..672d8d4dc2 100644 --- a/docs/dataclassification/5.6.2/overview/whatsnew.md +++ b/docs/dataclassification/5.6.2/overview/whatsnew.md @@ -11,7 +11,7 @@ sidebar_position: 30 All Netwrix product announcements have moved to the new Netwrix Community. See announcements for Netwrix Data Classification in the [Data Classification](https://community.netwrix.com/c/data-classification/announcements/102) area of -our new community. +the Netwrix Community. The following information highlights the new and enhanced features introduced in this Netwrix Data Classification 5.6.2 version. diff --git a/docs/dataclassification/5.6.2/systemconfigurationoverview/administration/utilities_backup_restore.md b/docs/dataclassification/5.6.2/systemconfigurationoverview/administration/utilities_backup_restore.md index b7ffd0dbd6..4ce5178e94 100644 --- a/docs/dataclassification/5.6.2/systemconfigurationoverview/administration/utilities_backup_restore.md +++ b/docs/dataclassification/5.6.2/systemconfigurationoverview/administration/utilities_backup_restore.md @@ -11,11 +11,11 @@ sidebar_position: 20 The Backup utility allows for the migration of complex Netwrix Data Classification instance configurations. -This allows a user to safely design and test a conceptSearching configuration within a development +This allows a user to safely design and test a Netwrix Data Classification configuration within a development environment and then copy the configuration, or specific parts of the configuration, to a different -environment (I.E production). +environment (for example, production). -The tool supports text replacement to allow user defined URL's to be replaced by the equivalent +The tool supports text replacement to allow user-defined URLs to be replaced by the equivalent destination URL. The following configuration options are available for import / export: - Source Registrations @@ -35,8 +35,8 @@ destination URL. The following configuration options are available for import / ![utilitiesbackup](/images/dataclassification/5.6.2/utilities/utilitiesbackup.webp) -To create a backup simply select Create Backup and select the elements that you wish to include. The -backup password will be required if you export a backup to XML and re-import to a different +To create a backup, select **Create Backup** and select the elements to include. You +must provide the backup password if you export a backup to XML and re-import it to a different environment. -Upon import any items that already exist will be skipped. +Upon import, the system skips items that already exist. diff --git a/docs/dataclassification/5.6.2/systemconfigurationoverview/administration/utilitiescleaner/cleaner_step_2.md b/docs/dataclassification/5.6.2/systemconfigurationoverview/administration/utilitiescleaner/cleaner_step_2.md index 8eeb19ce99..32803bc260 100644 --- a/docs/dataclassification/5.6.2/systemconfigurationoverview/administration/utilitiescleaner/cleaner_step_2.md +++ b/docs/dataclassification/5.6.2/systemconfigurationoverview/administration/utilitiescleaner/cleaner_step_2.md @@ -11,6 +11,6 @@ Specify options for the operation you have selected. | Operation selected | Available options | Details | | ------------------ | -------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Rebuild Index** | **Shrink the "text.cse" file?** - **Shrink** - **Don't Shrink** (default) | Selecting **Shrink** will rebuild the _Text.cse_ file, removing any fragmentation. **Shrink** will require sufficient disk space to process (up to the existing size of _Text.cse_) and may take some time to complete. | -| All operations | **Would you like to re-run the product configuration wizard?** - **Run** - **Don't Run** (default) | Select **Run** if you want to re-configure this instance by going through the initial steps of the product configuration. Note that this will pause all sources. | +| All operations | **Would you like to re-run the product configuration wizard?** - **Run** - **Don't Run** (default) | Select **Run** if you want to re-configure this instance by going through the initial steps of the product configuration. This will pause all sources. | ![cleaner_step_2_thumb_0_0](/images/dataclassification/5.6.2/utilities/cleaner_step_2_thumb_0_0.webp) diff --git a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/config_email.md b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/config_email.md index 2f751557c7..bf425ff51d 100644 --- a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/config_email.md +++ b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/config_email.md @@ -15,25 +15,25 @@ configuring email groups and health service notifications. Review the following ## Email Servers -Email servers can be configured to enable external communication. For instance when the health +Configure email servers to enable external communication. For example, when the health service identifies an issue. -Servers can be amended post configuration by selecting Edit, or, new SMTP servers can be added by -selecting Add Email Server Configuration. +Edit existing servers by selecting **Edit**, or add new SMTP servers by +selecting **Add Email Server Configuration**. ![configemailservers](/images/dataclassification/5.6.2/configuration/configemailservers.webp) The SMTP details should be entered based on the values provided by your network team. Each configuration supports both SSL enabled SMTP servers, and those without SSL enabled. -It is also possible to supply a test email address which will be used to test the configuration +Optionally, supply a test email address to test the configuration settings. ![configemailserveradd](/images/dataclassification/5.6.2/configuration/configemailserveradd.webp) ## Email Groups -Email groups are used to define a logical group of people to email, essentially – a mailing list. +Email groups define a logical group of people to email — essentially a mailing list. Each email group is linked to an SMTP server, so, before configuring an email group, you must configure your Email Servers. @@ -43,24 +43,23 @@ members. ![configaddemailgroup](/images/dataclassification/5.6.2/configuration/configaddemailgroup.webp) -Each group can have one or more members, and can be assigned a friendly name, which will be -displayed when selecting an email group. +Each group can have one or more members and a friendly name. The system displays this name when you select an email group. ## Health Service Notifications -Health Service Notifications can be configured to email a specific group of people when something -goes wrong within the product. Each notification configuration is linked to an email group, so, -before configuring notifications, you must configure your Email Groups. +Configure Health Service Notifications to email a specific group of people when an issue +occurs in the product. Each notification configuration links to an email group, so +configure your Email Groups before configuring notifications. To add a new notification configuration select Add Notification Configuration, or select Edit on each row to change the configuration. ![confighealthnotifications_thumb_0_0](/images/dataclassification/5.6.2/configuration/confighealthnotifications_thumb_0_0.webp) -Notifications can be set to trigger on warnings, or just on errors – by default problems of any -level will be reported. +Set notifications to trigger on warnings or errors. By default, the system reports problems at any +level. -The Daily Summary can also be disabled / enabled, this functionality sends out a summary email of +You can enable or disable the Daily Summary. When enabled, this feature sends a summary email of outstanding problems each morning. ![configaddhealthnotification](/images/dataclassification/5.6.2/configuration/configaddhealthnotification.webp) diff --git a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/config_metadata.md b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/config_metadata.md index ff9a50e451..fd984b9454 100644 --- a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/config_metadata.md +++ b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/config_metadata.md @@ -33,7 +33,7 @@ This list allows metadata values to be mapped from a source value to a new targe ![configmetadatavaluemappings_thumb_0_0](/images/dataclassification/5.6.2/configuration/configmetadatavaluemappings_thumb_0_0.webp) -For example, if we create an entry for the field “Modified By”, with Source=”Cheryl Tweedy” and +For example, if you create an entry for the field “Modified By”, with Source=”Cheryl Tweedy” and Target=”Cheryl Cole”, then a document with this metadata: `“Modified By: Cheryl Tweedy;”` @@ -42,15 +42,14 @@ Will generate an index with this metadata: `“Modified By: Cheryl Cole;”` -This facility can be useful when you need to align metadata field values for example when employees -change their name or are replaced by different people. +Use this feature to align metadata field values, for example when employees +change their name or when replacements are hired. ## Owner Mapping Priorities -This feature applies to the CSE-owner function for a workflow. Suppose, you want to email the -documents after the classification to the CSE owner. Then you may need to specify what is the role -you stand for these documents: Owner, Author, Creator, etc. You can prioritise any of these roles by -clicking the![arrowup](/images/dataclassification/5.6.2/configuration/arrowup.webp) +This feature applies to the CSE-owner function for a workflow. If you want to email the +documents after classification to the CSE owner, specify which role represents these documents: Owner, Author, Creator, or other. You can prioritize any of these roles by +clicking the ![arrowup](/images/dataclassification/5.6.2/configuration/arrowup.webp) or ![arrowadown](/images/dataclassification/5.6.2/configuration/arrowadown.webp) arrows. diff --git a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/configuration.md b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/configuration.md index b0a7d9e07c..3b1e2d88e6 100644 --- a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/configuration.md +++ b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/configuration.md @@ -6,14 +6,13 @@ sidebar_position: 20 # Configuration Options -The Config administration area allows you to specify global system configuration settings. The +Use the Config administration area to specify global system configuration settings. The default screen shows the most commonly amended settings. ![core_thumb_0_0](/images/dataclassification/5.6.2/configuration/core_thumb_0_0.webp) -The most frequently used settings are displayed by default. Some configuration options are hidden -and can be shown by selecting the Advanced Settings ("wrench" icon). Note that they will be only -available +The most frequently used settings are displayed by default. To view additional configuration options, select the Advanced Settings (wrench icon). + [See Users and Security Settings for more information.](/docs/dataclassification/5.6.2/systemconfigurationoverview/users/users.md) See next: diff --git a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/core_administration.md b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/core_administration.md index 674dcd4354..5f2e049a99 100644 --- a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/core_administration.md +++ b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/core_administration.md @@ -19,17 +19,17 @@ Nearly each configuration option has an associated “i” which describes the n | Option | Description | Comment | | ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **General settings** | | | -| Report Source Filter Mode | Use to add an additional filter for either Source Groups (default) or Source(s) | | +| Report Source Filter Mode | Use to add an additional filter for either Source Groups (default) or sources | | | Color Scheme | Select your preferred theme for the UI: orange or blue. | | | Disable Security Trimming | Select this option if you want to ensure that search results retrieved by API or the Taxonomies area will be unfiltered (ignoring the user name of the administrative user). | Disables the application of security trimming from search results (taxonomy browse/search). | | **Advanced settings** | | | | Instance name | Name of the NDC Server instance | | | Administration URL | URL of the web-based management console. Default URL is _http://localhost/conceptQS_. | If necessary, specify another Netwrix standalone server or cluster server instead of local host. You can use server name or IP address. | -| AD Groups Lookup Enabled | Allows you to enable/disable the use of AD groups in User Manager. This option is disabled by default. | It is recommended to keep this option disabled unless AD group support is specifically required. To learn more about User Manager in Netwrix Data Classification, see [User Management](/docs/dataclassification/5.6.2/systemconfigurationoverview/users/user_management.md) | +| AD Groups Lookup Enabled | Enable or disable the use of AD groups in User Manager. This option is disabled by default. | It is recommended to keep this option disabled unless AD group support is specifically required. For more information on User Manager in Netwrix Data Classification, see [User Management](/docs/dataclassification/5.6.2/systemconfigurationoverview/users/user_management.md) | ## Taxonomies -These settings allow you to customize configuration of classification taxonomies. +Use these settings to customize configuration of classification taxonomies. | Option | Description | Comment | | ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- | @@ -41,7 +41,7 @@ These settings allow you to customize configuration of classification taxonomies | Synonims Enabled | Used to control whether synonyms (for each standard clue) are configurable for taxonomies residing in the local SQL database. | | | Working Set Mode | Configures the Working Set functionality under 'Taxonomies'. Possible options: - The **Term Level** is used if a different working set is required for each class. - If **Taxonomy Level** is selected then the same working set shall be used for all classes in the taxonomy. | Changing this option will remove all documents from the current working set. | | Taxonomy Default Page Size | Number of documents returned by Taxonomy Manager. | | -| # Doc Metadata Fields Shown | NUmber of hint fields to be shown in Taxonomy Manager. | | +| # Doc Metadata Fields Shown | Number of hint fields to be shown in Taxonomy Manager. | | | Term User Locking Enabled | Enables/Disables the ability to "lock" terms when performing taxonomy management, preventing other users from editing the locked terms. | | | Enable Regex Browse Highlighting | When enabled, any search results found via the Browse UI will have any matched regular expressions highlighted (based on the selected terms clues). | | | Enable Page Info Regex Highlighting | When enabled, the text shown in a page info dialog will have any matched regular expressions highlighted. | | @@ -50,12 +50,12 @@ These settings allow you to customize configuration of classification taxonomies ## Concept Classifier App -These settings allow you to customize configuration of Concept Classifier app. +Use these settings to customize configuration of Concept Classifier app. | Option | Description | Comment | | ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- | | **General settings** | | | -| Enable Near Duplicate Detection | The relevance threshold for duplicate detection matching (when using the Duplicates link from the SharePoint ribbon). When set to 100%, this option will utilize an exact match (matching checksum). When set to a lower threshold, a fuzzy match will be attempted to locate near duplicates. | Applies only to the deployment with the SharePoint add-in. | -| Duplicate Detection Scope | Enables/disables scoping of duplicates detected via the SharePoint add-in interface. When disabled, duplicates wil be identified anywhere in the index. When enabled, duplicates will be scoped to their source group (or if no source group available - to their source). | Applies only to the deployment with the SharePoint add-in. | +| Enable Near Duplicate Detection | The relevance threshold for duplicate detection matching (when using the Duplicates link from the SharePoint ribbon). When set to 100%, this option will use an exact match (matching checksum). When set to a lower threshold, a fuzzy match will be attempted to locate near duplicates. | Applies only to the deployment with the SharePoint add-in. | +| Duplicate Detection Scope | Enables/disables scoping of duplicates detected via the SharePoint add-in interface. When disabled, duplicates will be identified anywhere in the index. When enabled, duplicates will be scoped to their source group (or if no source group available - to their source). | Applies only to the deployment with the SharePoint add-in. | | **Advanced settings** | | | | Duplicate Detection Archive Indicator | Identifies documents within the View Duplicates display that are tagged with the archive indicator. These identified documents can be optionally filtered from the display. | | diff --git a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/core_collector.md b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/core_collector.md index 8df271a7da..76f89ef1e4 100644 --- a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/core_collector.md +++ b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/core_collector.md @@ -16,8 +16,8 @@ associated “i” which describes the nature of the setting. | **General settings** | | | | Max Document Size | Sets the maximum size of the document to be processed. | Documents exceeding this size will typically be excluded from processing. | | Collect Metadata of Excluded Items | When enabled, the Netwrix Data Classification services will include the document, but from a metadata standpoint only (no text will be extracted from the file). | Used in combination with the "Max Document Size" value. Inactive by default. | -| Collector Threads | The number of overall background threads to be utilized by the Collector to access content from the source system. | Each thread can be considered a "user" when considering load on the source system. For more information, see [this Knowledge Base article](https://kb.netwrix.com/3863). | -| Collector Domain Threads | The number of threads to be utilized by the Collector to access content from the each HTTP domain. (Examples: netwrix.com, google.com, microsoft.com, etc.) The number will be automatically capped by the "Collector Threads" value. | Applies to HTTP source types only. Each thread can be considered a "user" when considering load on the source system. For more information, see [this Knowledge Base article](https://kb.netwrix.com/3863). | +| Collector Threads | The number of overall background threads to be used by the Collector to access content from the source system. | Each thread can be considered a "user" when considering load on the source system. For more information, see [this Knowledge Base article](https://kb.netwrix.com/3863). | +| Collector Domain Threads | The number of threads to be used by the Collector to access content from the each HTTP domain. (Examples: netwrix.com, google.com, microsoft.com, etc.) The number will be automatically capped by the "Collector Threads" value. | Applies to HTTP source types only. Each thread can be considered a "user" when considering load on the source system. For more information, see [this Knowledge Base article](https://kb.netwrix.com/3863). | | Collector File Threads | The number of threads used to crawl file system content. | For more information, see [this Knowledge Base article](https://kb.netwrix.com/3863). | | Process Document Images | If enabled, images will be extracted from supported documents ( (Office XML files and PDFs). These images will be then collected, and any text found will be included (with the document text) for classification. | For this setting to be applied, OCR must also be enabled at a content type level — to ensure that the extracted images are run through the OCR engine. This setting is inactive by default. | | Maximum Images per Document | Maximum amount of images to process through OCR on a per document basis. | | @@ -29,8 +29,8 @@ associated “i” which describes the nature of the setting. | Collector User Agent | Is used by Collector service as part of each web request made when crawling HTTP sources — to identify itself to the crawled systems. | | | Encrypt Text (text.cse) | Encrypts all data stored in **text.cse** (raw document extracts). | Inactive by default. If data already exists in the index, then to enable encryption on that existing data, you should perform re-collection. For that, click **Run Cleaner** button on the right. | | Optimise Text Storage | Reduces storage requirements for stored text. | Enabled by default. At each re-crawl or re-index the programs tries to detect whether the document text has changed. | -| Re-use Text Offsets | Reduces storage requirements for stored text by sharing and reusing the stored text. | May slightly increase the SQL demands —in order to process each de-duplication command. | +| Re-use Text Offsets | Reduces storage requirements for stored text by sharing and reusing the stored text. | May slightly increase the SQL demands — to process each de-duplication command. | | Collector Delay | The sleep time (in milliseconds) between intensive operations, such as storing crawled text. Default is **1** ms. | | -| Collector Polling | The sleep time (in seconds) between Collector batches. | Only utilized when the Collector queue is empty. | +| Collector Polling | The sleep time (in seconds) between Collector batches. | Only used when the Collector queue is empty. | | iFilter Processing Mode | Specify where the iFilter processing will run. Possible options: **Process as Sub Process**— run in a separate process **Process Internally** — run within Collector process | | -| Collector Reader Process Pool Size | The number of external processes that will be utilized for iFilter conversion. | Each additional process adds additional load on the Netwrix Data Classification server. We recommend leaving this setting on its default value. For more information, see [this Knowledge Base article](https://kb.netwrix.com/3863). | +| Collector Reader Process Pool Size | The number of external processes that will be used for iFilter conversion. | Each additional process adds additional load on the Netwrix Data Classification server. Leave this setting on its default value. For more information, see [this Knowledge Base article](https://kb.netwrix.com/3863). | diff --git a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/core_indexer.md b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/core_indexer.md index 94125524b2..5a66a1922b 100644 --- a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/core_indexer.md +++ b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/core_indexer.md @@ -15,9 +15,9 @@ screwdriver icon at **Settings** on the right. | Option | Description | Comment | | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **General settings** | | | -| Indexer Threads | The number of background threads used for the indexer's processing. Default is _0_ (auto). | We recommend leaving this setting on its default value. For more information, see this Knowledge Base article: [https://kb.netwrix.com/3863](https://kb.netwrix.com/3863) | +| Indexer Threads | The number of background threads used for the indexer's processing. Default is _0_ (auto). | Leave this setting on its default value. For more information, see this Knowledge Base article: [https://kb.netwrix.com/3863](https://kb.netwrix.com/3863) | | Near Duplicate Detection Enabled | With this option enabled, the Indexer will attempt a fuzzy match to locate near duplicates within the index (as a background action). These can then be reviewed via the **Near Duplicate Detection** report. | By default, duplicate detection will be based purely on an exact match (matching checksum). | | **Advanced settings** | | | | Indexer Delay | The sleep time (in milliseconds) between intensive operations (for example, extracting terms). Default is _1_ millisecond. | | -| Indexer Polling | The sleep time between Indexer batches. | Only utilised when the indexing queue is empty. | +| Indexer Polling | The sleep time between Indexer batches. | Only used when the indexing queue is empty. | | `DocumentID` Mapping | Used to map fields into the search index ID references. Allows for custom queries based on external IDs against the SOAP search API calls. | Theses are ID3 — ID8 | diff --git a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/core_system.md b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/core_system.md index 7543e1f3d4..bfc421538d 100644 --- a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/core_system.md +++ b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/core_system.md @@ -6,7 +6,7 @@ sidebar_position: 50 # System -This configuration tab contains the settings related to system health, operation and logging. Each +This configuration tab contains the settings related to system health, operation, and logging. Each configuration option has an associated “i” which describes the nature of the setting. ![core_system_thumb_0_0](/images/dataclassification/5.6.2/configuration/core/core_system_thumb_0_0.webp) diff --git a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/coreclassifier/classifier_app.md b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/coreclassifier/classifier_app.md index d16b525098..51826f48f9 100644 --- a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/coreclassifier/classifier_app.md +++ b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/coreclassifier/classifier_app.md @@ -21,7 +21,7 @@ The following options can be configured for conceptClassifier app: | Option | Description | Comment | | -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------- | -| Write Mode | Allows you to configure the update method that will be used by the Classification service to update SharePoint documents. Possible options: - **Alter audit information** - Simple Update operation - **Maintain audit information** - ValidateUpdateListItem operation - **Maintain audit information with no alerts (O365 only)** - SystemUpdate operation | Applies to SharePoint documents. | +| Write Mode | Configure the update method that will be used by the Classification service to update SharePoint documents. Possible options: - **Alter audit information** - Simple Update operation - **Maintain audit information** - ValidateUpdateListItem operation - **Maintain audit information with no alerts (O365 only)** - SystemUpdate operation | Applies to SharePoint documents. | | Manually Classify Cleared Fields | When enabled, fields will be marked as manually classified if the user clears them. If disabled, auto classification must be manually turned off by the user to stop the field being updated. | | | Hide Sql (Local) Taxonomy Calculations | When disabled, any classifications/calculations will be hidden from the SharePoint View Classifications display (Classic and Modern UI). | | | Ignore Manual Classifications From | A semicolon-delimetered list of usernames. Any updates to classification of new documents in SharePoint by these users will be ignored. | | diff --git a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/coreclassifier/classifier_engine.md b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/coreclassifier/classifier_engine.md index ec3a4d632f..98533fdaa6 100644 --- a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/coreclassifier/classifier_engine.md +++ b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/coreclassifier/classifier_engine.md @@ -20,10 +20,10 @@ has an indication of the values that have been changed from the default setting. | -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **General settings** | | | | Boosted Phrasematch Scoring | Automatically boosts the score of Phrasematch clues when the phrase occurs multiple times in the same document. | | -| Boosted Regex Scoring | Automatically boosts the score of Regex clues when the regular expression matches multiple occurrences in the same document. | Selecting this option is not recommended when using the Netwrix compliance taxonomies. | +| Boosted Regex Scoring | Automatically boosts the score of Regex clues when the regular expression matches multiple occurrences in the same document. | Selecting this option isn't recommended when using the Netwrix compliance taxonomies. | | Case-insensitive Regex Processing | Processes any regex or metadata regex rules in a case-insensitive manner. | | | **Advanced settings** | | | | Redis Caching | Use _redis_ module to enable Classifier data caching between the core Windows services and NDC Servers. | This module can be downloaded from [https://github/MicrosoftArchive/redis/releases.](https://github/MicrosoftArchive/redis/releases) Install it locally and open port **6379** required for its operation. For details on servers cluster, see [Configuring NDC Servers Cluster and Load Balancing with DQS Mode](/docs/dataclassification/5.6.2/deployment/deploymentplan/ndcserverclient/distributed_query_server_mode.md) | | Store Trimmed Classification | Enables storing trimmed classifications in SQL (due to max category settings at the global or subset level). | When enabled, classification performance will be improved —however, this will result in additional data within the SQL database. | -| Enable Standard Clue Metadata Matching | By default, standard clues are matched against the extracted text, index text, summary, and title. Use this option if you want to match standard clues also on values found in the document's metadata. | To ensure accurate classification results, we recommend running an index rebuild operation after enabling this mode (use Run Cleaner button). | -| Disable Unclassified Regex Extraction | By default, any regular expression clue will result in additional metadata being added to a document, based on the extracted value(s). Use this option if you want to only extract values for clues on nodes that have achieved their threshold for classification. | | +| Enable Standard Clue Metadata Matching | By default, standard clues are matched against the extracted text, index text, summary, and title. Use this option if you want to match standard clues also on values found in the document's metadata. | To ensure accurate classification results, run an index rebuild operation after enabling this mode (use Run Cleaner button). | +| Disable Unclassified Regex Extraction | By default, any regular expression clue will result in additional metadata being added to a document, based on the extracted values. Use this option if you want to only extract values for clues on nodes that have achieved their threshold for classification. | | diff --git a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/coreclassifier/classifier_general.md b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/coreclassifier/classifier_general.md index c0cd3c7a7f..b6f572fdc7 100644 --- a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/coreclassifier/classifier_general.md +++ b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/coreclassifier/classifier_general.md @@ -6,7 +6,7 @@ sidebar_position: 10 # General Options -The **General** section contains general classification engine settings, e.g. . By default, only +The **General** section contains general classification engine settings. By default, only standard options are displayed. To view advanced options, click the screwdriver icon at **Settings** in the bottom-right corner. @@ -25,12 +25,12 @@ has an indication of the values that have been changed from the default setting. | Max Categories | Sets the maximum number of classifications to be allocated to each document. Possible values: - up to **256** — for 32-bit Windows - up to **1024** — for 64-bit Windows | If a document matches so many categories that the specified value would be exceeded, then the classification service will select the required number of categories based on those that have the highest score. **NOTE:** Higher value causes the engine to use more RAM, so it is recommended to use the default setting (unless it is essential that more categories are allocated to each document). | | Retain Existing Metadata Mode | Specifies how the classification engine should process already existing classification (managed metadata fields). Possible options: - **Retain if not classified** — leave existing classification in place if no auto-classification has been generated - **Overwrite** — clear managed metadata fields | Applies to SharePoint source. | | Auto-Classification Change Logs | Enables a change log for auto-classification: each "Addition"/"Removal" of a classification against a document will be stored in the database as its classifications change. | Inactive by default. See also Enable Auto-Classification Change Logging. | -| Classifier Threads | The number of background threads used for classification. Default is **0 (auto)**. | We recommend leaving this setting on its default value. For more information, see this Knowledge Base article: [https://kb.netwrix.com/3863](https://kb.netwrix.com/3863) | -| Classifier Write Threads | The number of threads to be utilised by the Classifier to update source systems during "tagging" operations (i.e. writing classification back to source system). | Each thread can be considered a "user" when considering load on the source system. For more information, see this Knowledge Base article: [https://kb.netwrix.com/3863](https://kb.netwrix.com/3863) | +| Classifier Threads | The number of background threads used for classification. Default is **0 (auto)**. | Leave this setting on its default value. For more information, see this Knowledge Base article: [https://kb.netwrix.com/3863](https://kb.netwrix.com/3863) | +| Classifier Write Threads | The number of threads to be used by the Classifier to update source systems during "tagging" operations (i.e. writing classification back to source system). | Each thread can be considered a "user" when considering load on the source system. For more information, see this Knowledge Base article: [https://kb.netwrix.com/3863](https://kb.netwrix.com/3863) | | **Advanced settings** | | | | ![core_classifier_general_tab_thumb_0_0](/images/dataclassification/5.6.2/configuration/core/core_classifier_general_tab_thumb_0_0.webp) | | | | Classifier Enabled | Enables / disables the Classifier core component. By default, it is enabled. | | -| SharePoint EMM No Classify Mode | Possible values: - **Do not update Deprecated** (default) — use if you do not want to alter the **Deprecated** setting in SharePoint EMM - **Update Deprecated** — select if you want Deprecated setting to be updated | | +| SharePoint EMM No Classify Mode | Possible values: - **Don't update Deprecated** (default) — use if you don't want to alter the **Deprecated** setting in SharePoint EMM - **Update Deprecated** — select if you want Deprecated setting to be updated | | | Subset Trimming Enabled | This setting applies where both primary (single value) and secondary (multi value) fields are added to a document library for the same taxonomy. - **Off** (default) — the highest scoring term will be shown in both primary and secondary fields. - **On** — the highest scoring term will be shown only in the primary field. | | | Subset Trimming Threshold | If **Subset Trimming Enabled** option is ON, this parameter defines the minimum score required to class the highest scoring term as primary. | If no item has a score higher than this threshold, then all terms will show as secondary terms, and the primary term will be empty. | | Classifier Delay | The sleep time (in milliseconds) between intensive operations, such as storing classification. Default is **1** ms. | | diff --git a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/coreclassifier/classifier_monitored_content.md b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/coreclassifier/classifier_monitored_content.md index eedec47371..6ba2f2123a 100644 --- a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/coreclassifier/classifier_monitored_content.md +++ b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/coreconfiguration/coreclassifier/classifier_monitored_content.md @@ -17,8 +17,8 @@ setting. | Option | Description | Comment | | ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | -| Monitored Document Indicator | Content will be marked for automatic re-classification if it is tagged with a particular term. | Click on the tag icon to select the term that should be used to identify monitored content. | -| Minimum Reclassification Regularity (days) | Defines the minimum period to be used when re-classifying monitored content: from _1_ to _180_ days, default is **1** day. | Content will be marked for reclassification if it was last classified prior to the specified regularity period. | +| Monitored Document Indicator | Content will be marked for automatic re-classification if it is tagged with a particular term. | Click the tag icon to select the term that should be used to identify monitored content. | +| Minimum Reclassification Regularity (days) | Defines the minimum period to be used when re-classifying monitored content: from _1_ to _180_ days, default is **1** day. | Content will be marked for reclassification if it was last classified before the specified regularity period. | To re-classify content that meets specific conditions: @@ -26,15 +26,15 @@ To re-classify content that meets specific conditions: particular term. 2. In the **Monitored Content** section of **System Configuration > Core > Classifier** locate **Monitored Document Indicator**. -3. Click on the tag icon, and in the **Select Term** dialog specify the term that should be used to +3. Click the tag icon, and in the **Select Term** dialog specify the term that should be used to identify monitored content: - ![core_classifier_mc_terms_thumb_0_0](/images/dataclassification/5.6.2/configuration/core/core_classifier_mc_terms_thumb_0_0.webp)4. - When finished, click **Select**, then in the Classifier settings window click **Save**, + ![core_classifier_mc_terms_thumb_0_0](/images/dataclassification/5.6.2/configuration/core/core_classifier_mc_terms_thumb_0_0.webp) +4. When finished, click **Select**, then in the Classifier settings window click **Save**. To re-classify content with a minimum time period between runs: 1. In the **Monitored Content** section of **System Configuration > Core > Classifier** settings window locate **Minimum Reclassification Regularity**. 2. Default reclassification period is 1 day. Use the slider to adjust the value. Content will be - marked for reclassification if it was last classified prior to the specified period. + marked for reclassification if it was last classified before the specified period. 3. Click **Save**. diff --git a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/language_stemming.md b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/language_stemming.md index 6cf2a55954..3482b69741 100644 --- a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/language_stemming.md +++ b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/language_stemming.md @@ -10,27 +10,25 @@ Language stemming is a morphological process that converts words to their root f inflected forms are considered equal. For example, an English language search for the word “baby” will also locate documents containing the word “babies”. -Note that the stemming process is highly language specific and so one word may stem differently in +The stemming process is highly language-specific, so one word may stem differently in different languages. -Netwrix Data Classification has support for most common languages and will detect the language for -each document. However, when an index is to be built for documents in multiple languages it is -normally important that the same stemmer be used for all documents. Otherwise, a search across the -collection may be compromised when some words from the query are stemmed differently in different +Netwrix Data Classification supports most common languages and automatically detects the language for +each document. When building an index for documents in multiple languages, use the same stemmer for all documents. +Otherwise, searches across the collection may be compromised if query words stem differently in different languages. -If all searches are filtered by language then it may make sense to use a different stemmer for each -language. However, in this case we would recommend building a separate index for each language -rather than combining all languages in a single index. +If you filter all searches by language, you might use a different stemmer for each +language. However, it's better to build a separate index for each language +than combining all languages in a single index. -The reason that automatic language detection is important during the indexing process is so that the -correct stoplist is used when extracting terms and concepts. By excluding words in the stoplist the -index size can be significantly reduced. More importantly, the stoplists play an integral part of -the concept identification process. +Automatic language detection during indexing is important because it ensures the +correct stoplist is used when extracting terms and concepts. Excluding stoplist words significantly +reduces index size and improves concept identification. -The stemmer should be selected based on the dominant language for a given index. The default stemmer -is English but this may be configured via the “StemLang” field in the “Config” table in the SQL -Database. +Select the stemmer based on the dominant language for a given index. The default stemmer +is English, but you can configure it via the “StemLang” field in the “Config” table in the SQL +database. Netwrix Data Classification uses the stemming algorithms published as part of the Snowball project (see [http://snowball.tartarus.org](http://snowball.tartarus.org/) for details). @@ -53,7 +51,7 @@ By default, the NDC database will index words containing the following character - “=” - “_” (underscore) -Indexing of these characters can be stopped by removing the relevant entries from the +Stop indexing these characters by removing the relevant entries from the CustomTermCharacters table: - “@” @@ -66,8 +64,7 @@ CustomTermCharacters table: - “=” - “_” (underscore) -Any of the following characters can be included in the list of indexed characters by adding them to -the CustomTermCharacters table: +Add any of the following characters to the CustomTermCharacters table to include them in the list of indexed characters: - “(” - “)” @@ -120,8 +117,8 @@ will match with: and vice versa. -Note that this mapping of diacritics is transparent to the end user and all data displayed will -always contain the original characters formats. Therefore, all document summaries, extracts and +This mapping of diacritics is transparent to the end user, and all data displayed will +always contain the original character formats. Therefore, all document summaries, extracts, and related topics will always be displayed with diacritics if the original documents contained them. In addition, all stopword processing is based on the extended ASCII character set and so stopwords @@ -129,20 +126,18 @@ for different languages are always held with appropriate diacritics. ## Fuzzy Matching Options -It can be useful to search for concepts using a degree of fuzzy matching so that words may be -matched even if the query or documents contain typing errors or variant spelling. +Fuzzy matching lets you search for concepts even if the query or documents contain typing errors or variant spelling. -In general, fuzzy matching improves recall but at the expense of precision. In other words, more -documents should be located but some of these may not be relevant to the query. ConceptSearching -offers several options for fuzzy matching so that an application can balance the needs of precision -and recall. +Fuzzy matching improves recall at the expense of precision. More documents are located, +but some may not be relevant to the query. Netwrix Data Classification offers several fuzzy matching options +to balance precision and recall needs. ### Fuzzy Stemming -Our stemming algorithms can optionally include a degree of fuzzy matching based on removal of -duplicated consonants. The advantage of this technique is that is improves recall without any loss -of precision since duplicated consonants are largely redundant in word matching. Enabling this -option (set StemmingMode=1 in the Config table) will cause the following words to match: +Stemming algorithms can optionally include fuzzy matching based on removing +duplicated consonants. This technique improves recall without losing +precision because duplicated consonants are largely redundant in word matching. Enable this +option (set StemmingMode=1 in the Config table) to match the following words: accelerate with diff --git a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/redaction.md b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/redaction.md index 6405593fa9..b951578343 100644 --- a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/redaction.md +++ b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/redaction.md @@ -14,15 +14,15 @@ for additional information: ## Redaction Plans -Redaction plans can be used as an optional migration step to remove specific entities from supported -content types. During the migration of a document a migration plan will remove the following entity -types (depending on the configuration): +Use redaction plans as an optional migration step to remove specific entities from supported +content types. During migration, a redaction plan removes the following entity +types (depending on configuration): - NLP Entities—Items identified by the NLP entity extraction, such as names or locations - Regex Entities—Items identified by the Regex classification clues, such as credit card numbers or social security numbers - - Specific clues can be skipped as part of a redaction plan by specifying Excluded Clues, such + - Skip specific clues as part of a redaction plan by specifying Excluded Clues, such as: “VISA” or “SSN” (matched to the term name) - Custom Entities—Any custom words or phrases associated with the plan. @@ -34,13 +34,13 @@ retained from each redacted value. ## Redaction Entity Groups -Entity Groups can be used to add redaction entities to specific groups. +Use Entity Groups to add redaction entities to specific groups. ![redactionentitygroups](/images/dataclassification/5.6.2/configuration/redactionentitygroups.webp) ## Redaction Entities -Entities can be used to specify any custom words or phrases that should be removed by a redaction -plan. +Use Entities to specify custom words or phrases that a redaction +plan should remove. ![configredactionentities](/images/dataclassification/5.6.2/configuration/configredactionentities.webp) diff --git a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/system_configuration.md b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/system_configuration.md index bf7e2d6b44..e0fcfd8e45 100644 --- a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/system_configuration.md +++ b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/system_configuration.md @@ -17,66 +17,59 @@ types. ## AD Domains Excluded -The AD Domains Excluded list is used to disable Active Directory expansion for certain domain names. -This is useful in a multi-Domain forest, where the Netwrix Data Classification server does not have +Use the AD Domains Excluded list to prevent Active Directory expansion for certain domain names. +This is useful in multi-domain forests, where the Netwrix Data Classification server doesn't have access to all domains within the forest. ![configaddomainsexcluded](/images/dataclassification/5.6.2/configuration/configaddomainsexcluded.webp) ## Attachments Excluded -When indexing files from that potentially contain attachments (SharePoint List Items) the list of -file locations that will be ignored is defined by the Attachments Excluded list. The definitions in -this list may be viewed and modified via the Attachments Excluded form: +When indexing files that potentially contain attachments (SharePoint List Items), use the Attachments Excluded list to define which file locations to ignore. View and modify these definitions in the Attachments Excluded form: ![configattachementsexcluded](/images/dataclassification/5.6.2/configuration/configattachementsexcluded.webp) -Any file with a path that matches one of these patterns will be ignored. Wildcards may be used -anywhere in the pattern definition, with: +The system ignores any file with a path matching one of these patterns. Use wildcards anywhere in the pattern definition: - The asterisk character (\*) matching any sequence of characters - The question mark character (?) matching any single character ## No Index -Sometimes an application may wish to remove selected documents from all search results. This may be -implemented by specifying No Index entries. +To remove selected documents from all search results, specify No Index entries. ![confignoindex](/images/dataclassification/5.6.2/configuration/confignoindex.webp) -Any number of URLs (or Filenames) may be entered and none of these will ever appear in search -results. Wildcards may be used anywhere in the pattern definition, with: +Enter any number of URLs or filenames, and the system will never display them in search +results. Use wildcards anywhere in the pattern definition: - The asterisk character (\*) matching any sequence of characters - The Question mark character (?) matching any single character ## Proxy Server -The Proxy Server form may be used to define a proxy server to be used when crawling websites, the -proxy server is not used for SharePoint crawling. +Use the Proxy Server form to define a proxy server for crawling websites. The proxy server isn't used for SharePoint crawling. ![configproxyserver](/images/dataclassification/5.6.2/configuration/configproxyserver.webp) -Set Bypass Local to Yes to bypass the proxy server for local addresses (localhost etc). +Set **Bypass Local** to **Yes** to bypass the proxy server for local addresses (such as localhost). -Any other exclusions that should not go through the proxy server should be defined in the Exceptions -list. +Define any other exclusions in the **Exceptions** list — URLs that shouldn't go through the proxy server. ## Suspend Services (Scheduler) All Netwrix Data Classification services run as Windows services. They are responsible for building the search index and classifying documents against the registered taxonomies. -It can be useful to suspend these services from running so that they do not impact query performance -during the peak hours of the working day. Sometimes it may be useful to suspend these services for -some lower priority sources but have them continue to process higher priority sources. +Suspending services prevents them from impacting query performance +during peak hours. You can suspend services for lower-priority sources while allowing them to continue processing higher-priority sources. ![configsuspendservices](/images/dataclassification/5.6.2/configuration/configsuspendservices.webp) -Service suspensions can be configured in the following ways: +Configure service suspensions by specifying: - Source—Which source types the suspension is in place for: all source types, specific source types (SharePoint, Web etc) or specifically against Re-Indexing operations. -- Service—Which services are affected by the suspension: All Services, or, a choice of: NDC +- Service—Which services are affected by the suspension: **All Services** or a choice of: **NDC** Collector, NDC Indexer, NDC Classifier. - Day/Times—Allows the configuration of which days and times the suspension will be in place. diff --git a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/text_handling.md b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/text_handling.md index d0f6d7393a..4e646d48af 100644 --- a/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/text_handling.md +++ b/docs/dataclassification/5.6.2/systemconfigurationoverview/configuration/text_handling.md @@ -19,20 +19,18 @@ This section contains information on how to configure text processing. Related o ## Best Bets -Sometimes an application may wish to push selected documents to the top of a hitlist for specific -queries. This may be implemented by specifying Best Bets for specific query text. +To push selected documents to the top of a hitlist for specific +queries, specify Best Bets for specific query text. ![configbestbets_thumb_0_0](/images/dataclassification/5.6.2/configuration/configbestbets_thumb_0_0.webp) -First, enter the search term that you wish to match and then click the Add button. +First, enter the search term to match and then click the Add button. -Next, click on the term, and specify one or more URLs that should appear at the top of the hit list. +Next, click the term, and specify one or more URLs that should appear at the top of the hit list. ## Content Type Extension Mapping -Sometimes an organization may wish to process certain file types as a different content type. The -primary use case for this is internal content types that map to a content type already understood / -identified. +Organizations sometimes process certain file types as a different content type. This is useful for internal content types that map to an already-understood or identified content type. In this case the example has a .rpt file being treated as a text file, as such the file will be copied to a temporary location as a .txt file and processed as if it were any other text file. @@ -41,18 +39,14 @@ copied to a temporary location as a .txt file and processed as if it were any ot ## Content Type Extraction Methods -The Content Type Extraction methods describes how documents will be handled by the APIs and the core -services. A number of built-in processing methods are available, where there is no available method -the processing will default to running through standard Microsoft Search iFilter processing. +Content Type Extraction methods describe how the APIs and core +services handle documents. A number of built-in processing methods are available. When no available method exists, +the system defaults to running standard Microsoft Search iFilter processing. -The methods can be easily altered by clicking Edit and then selecting the preferred processing -method. It is also possible to specify that an iFilter should be utilised if the primary method -fails to extract text from the document – the backup method will be used if the extraction fails to -find more than 5 characters of text. +Change extraction methods by clicking **Edit** and selecting your preferred processing +method. Optionally, specify a backup iFilter method if the primary method fails to extract text from the document or extracts fewer than 5 characters. -If you have updated the extraction method we recommend re-processing any documents that have already -been processed to ensure consistency. Selecting Re-index from the grid for the affected content type -will re-process the necessary records. +After updating the extraction method, re-process previously-processed documents to ensure consistency. Select **Re-index** from the grid for the affected content type. ![configcontenttypeextractionmethods_thumb_0_0](/images/dataclassification/5.6.2/configuration/configcontenttypeextractionmethods_thumb_0_0.webp) @@ -62,11 +56,10 @@ The language detection list specifies which languages will be considered for aut ![configlanguages_thumb_0_0](/images/dataclassification/5.6.2/configuration/configlanguages_thumb_0_0.webp) -If a language is excluded then it cannot be used to identify the language of a document and it will +If a language is excluded then it can't be used to identify the language of a document and it will be removed from the language options in Taxonomy Manager. -**TIP:** You can also OCR recognition for non-English images. Refer to the following Netwrix -knowledge base article for more information: +**TIP:** You can also OCR recognition for non-English images. For more information, see [How to enable OCR for non-English images](https://kb.netwrix.com/3519). ## No Stem @@ -79,15 +72,15 @@ clue – or a search term. ## OCR Language Mapping -The OCR language mapping configuration screen can be used if you wish to OCR non-English images via +Use the OCR language mapping configuration screen to OCR non-English images via Tesseract. File paths (including parts of paths) can be mapped to specific Tesseract language packs. ![configocrlanguagemapping](/images/dataclassification/5.6.2/configuration/configocrlanguagemapping.webp) ## Synonyms -Often it is important to submit a query and have synonyms automatically included. A generic set of -synonyms may be configured by using the Synonyms form. +To submit a query and have synonyms automatically included, configure a generic set of +synonyms using the Synonyms form. ![configsynonyms](/images/dataclassification/5.6.2/configuration/configsynonyms.webp) @@ -98,20 +91,19 @@ for all pages and/or not relevant to the individual page content. If all of the these HTML pages then this can lead to unwanted search results where a match is made, for example, to an entry in a standard page navigation area. -The Text Patterns feature is provided to assist with the cleanup of HTML documents. TextPatterns can -also be used to index terms that would normally be discarded. +Use the Text Patterns feature to clean up HTML documents and to index terms that would normally be discarded. ![configtextpatterns_thumb_0_0](/images/dataclassification/5.6.2/configuration/configtextpatterns_thumb_0_0.webp) The StartTag and EndTag values are case sensitive strings used to identify the content to be managed, the content is then managed based on the filter type. -There are three tag types that can be used to assist in the cleanup: +Three tag types assist in cleanup: -- FILTER—Extracts a subset of the HTML page, prior to extracting the plain text. Only a single +- FILTER—Extracts a subset of the HTML page, before extracting the plain text. Only a single section will be extracted for each TextFilter processed. -- DELETE—Deletes sections of the HTML page, prior to extracting the plain text. +- DELETE—Deletes sections of the HTML page, before extracting the plain text. - INDEX TERM (EndTag ignored)—Create index terms that would otherwise not be formed. For example the term “E.ON” is a useful one for people interested in energy companies. However, this term would - not normally be created because a full stop normally acts as a term separator. However, if we - create an INDEX TERM for this pattern then it will be detected and indexed as required. + not normally be created because a full stop normally acts as a term separator. However, if you + create an INDEX TERM for this pattern so it will be detected and indexed as required. diff --git a/docs/dataclassification/5.6.2/systemconfigurationoverview/users/password_manager.md b/docs/dataclassification/5.6.2/systemconfigurationoverview/users/password_manager.md index 0a000b564a..0496c4ee76 100644 --- a/docs/dataclassification/5.6.2/systemconfigurationoverview/users/password_manager.md +++ b/docs/dataclassification/5.6.2/systemconfigurationoverview/users/password_manager.md @@ -6,13 +6,10 @@ sidebar_position: 30 # Password Manager -Password manager can be used to automatically schedule password changes, for service accounts that -are being used to access external systems. This is particularly useful when there are business -policies in place to change passwords on a rolling basis. +Use Password Manager to automatically schedule password changes for service accounts that access external systems. This is useful when your organization has rolling password policies. ![passwordmanager_thumb_0_0](/images/dataclassification/5.6.2/security/passwordmanager_thumb_0_0.webp) -To amend the passwords for a username record first select Passwords from the main display. Then -either click Edit on a particular password row, or, click Add Password to add a new password for the -account. It is not possible to have overlapping date ranges for the defined passwords, nor is it -possible to remove all passwords from a user record. +To change a user's passwords, select **Passwords** from the main display. Then +click **Edit** on a password row to edit it, or click **Add Password** to add a new password for the +account. Don't create overlapping date ranges for passwords, and always keep at least one password per user record. diff --git a/docs/dataclassification/5.6.2/systemconfigurationoverview/users/secure_ndc.md b/docs/dataclassification/5.6.2/systemconfigurationoverview/users/secure_ndc.md index e656b8d3f3..54605ef42a 100644 --- a/docs/dataclassification/5.6.2/systemconfigurationoverview/users/secure_ndc.md +++ b/docs/dataclassification/5.6.2/systemconfigurationoverview/users/secure_ndc.md @@ -6,11 +6,9 @@ sidebar_position: 10 # Secure Netwrix Data Classification -The steps described within this article can be used to review the security of your Netwrix Data -Classification deployment and apply any changes you feel necessary to secure the administration of, -and access to, the Classification interfaces. +Use the steps in this article to review your Netwrix Data Classification deployment's security and apply changes to secure administration and access to the Classification interfaces. -In this article we will cover: +This article covers: - [Configuring Administration Console Access](#configuring-administration-console-access) - [Configuring Microsoft SQL Server Security](#configuring-microsoft-sql-server-security) @@ -18,13 +16,13 @@ In this article we will cover: ## Configuring Administration Console Access -By default, post installation, all users will be considered Superusers with access to all areas of -the product. To begin the process of securing the product please follow the below steps: +By default, after installation, all users are considered Superusers with access to all areas of +the product. To secure the product, follow these steps: 1. Access the Administration Console 2. Select Users from the top navigation bar 3. Select Add -4. Your username will be pre-filled and must first be added to ensure that you do not lose access to +4. Your username will be pre-filled and must first be added to ensure that you don't lose access to the system. 5. You can now add other users / groups as required - either as Superusers, or with access to specific areas / functions @@ -48,13 +46,13 @@ the back-end SQL Server database: - C:\Program Files\Concept Searching\Services\ConceptCollectorService - C:\Program Files\Concept Searching\Services\conceptIndexer - 2. Check the Encrypt Connection box as well as the Trust Server Certificate box if you do not + 2. Check the Encrypt Connection box as well as the Trust Server Certificate box if you don't have a valid certificate loaded for SQL Server. 3. Click Save. - Transparent Data Encryption (TDE)—Protects your data at rest within SQL Server. Netwrix Data Classification supports the use of TDE, it should of course be noted that this does incur a - performance overhead. TDE should be managed and configured by your database administrator(s). + performance overhead. TDE should be managed and configured by your database administrators. ### To secure Search Index (CSE File) @@ -65,7 +63,7 @@ groupings to this engine: - All other files—Stores the compound term processing search index, identifying which documents should be returned for a given query -Text.cse can be optionally encrypted, this utilises AES/SHA256 to further improve the security of +You can optionally encrypt Text.cse using AES/SHA256 to further improve the security of the full text at rest. You can enable this mode by: 1. Access the Administration Console; @@ -74,15 +72,15 @@ the full text at rest. You can enable this mode by: spanner to show); 4. Select Save. -The remaining files cannot be reverse engineered to retrieve the full document text - however, do -contain the weightings and terms within the text. We recommend restricting access to all files at -the file system level as well as considering file system encryption. +The remaining files can't be reverse engineered to retrieve the full document text - however, do +contain the weightings and terms within the text. Restrict access to all files at +the file system level as well as consider file system encryption. ## Reviewing web service endpoints There are several web service endpoints which provide access to various levels of information within Netwrix Data Classification. If you are exposing the administration interface to the internet then -you may wish to fully restrict access to these endpoint(s) via your firewall or IIS Configuration +fully restrict access to these endpoints via your firewall or IIS Configuration (potentially removing all external access). The following paths should be considered as part of this process: @@ -91,6 +89,6 @@ The following paths should be considered as part of this process: - \*.asmx - \*.svc -It should be noted that when using Netwrix Data Classification for SharePoint Online certain -endpoints are required, each of these endpoints are located within the folder +When using Netwrix Data Classification for SharePoint Online, certain +endpoints are required. Each endpoint appears in the folder "_/ConceptClassifierApp/_". diff --git a/docs/dataclassification/5.6.2/systemconfigurationoverview/users/user_management.md b/docs/dataclassification/5.6.2/systemconfigurationoverview/users/user_management.md index 97589cc5a3..0a02656ddc 100644 --- a/docs/dataclassification/5.6.2/systemconfigurationoverview/users/user_management.md +++ b/docs/dataclassification/5.6.2/systemconfigurationoverview/users/user_management.md @@ -16,9 +16,9 @@ permissions and manage existing users. Review the following for additional infor ## Authentication Mechanisms -On first install the QS will be configured for Windows authentication. To setup the QS to use an -ADFS server please follow the "Installation and Configuration" guide using the section "ADFS". To -use forms based authentication please disable all other authentication methods in IIS other than: +On first install the QS will be configured for Windows authentication. To set up the QS to use an +ADFS server, follow the "Installation and Configuration" guide using the section "ADFS". To +use forms based authentication, disable all other authentication methods in IIS other than: Anonymous and Forms: To use the authentication forms: @@ -40,7 +40,7 @@ To use the authentication forms: ![iis_thumb_0_0](/images/dataclassification/5.6.2/security/iis_thumb_0_0.webp) -3. If you wish to allow anonymous access to the conceptQS, edit the conceptQS web.config file and +3. To allow anonymous access to the conceptQS, edit the conceptQS web.config file and delete (or comment out) three lines: ```xml @@ -84,17 +84,17 @@ The following example is similar to the previous one, except that we force the f Context rules also contain some parameters for [role mining](/docs/identitymanager/current/user-guide/optimize/assignment-automation/role-mining). -Users are distributed in a hypercube made of all dimensions, like in the following table (left) when we have only 2 dimensions, where for example `1`, `2`, `3`, etc. are users' possible locations, and `A`, `B`, `C`, etc. are users' possible departments in the company. When considering one dimension and sorting the dimension values per user percentage, we get the following table (right). +Users are distributed in a hypercube made of all dimensions, like in the following table (left) when there are only 2 dimensions, where for example `1`, `2`, `3`, etc. are users' possible locations, and `A`, `B`, `C`, etc. are users' possible departments in the company. When considering one dimension and sorting the dimension values per user percentage, the following table (right) shows the result. ![Role Mining Tables](/images/identitymanager/contextrules_rolemining.webp) The tables here represent a simple situation with few dimensions. But the higher the number of dimensions, the more complex are role mining's computations. This is known as the curse of dimensionality. -The following example is similar to the first one, except that we customize some role mining parameters which help tackle the curse of dimensionality: +The following example is similar to the first one, except that it customizes some role mining parameters which help tackle the curse of dimensionality: * `MinIdentitiesCount` establishes that the role mining's engine will generate a role assignment rule only when the rule is applicable to at least 5 users; * `ReductionOutlierPercentage` establishes that the role mining's engine will consider the last 2.0% dimension values (from `Y` to `Z` in the table above) to be grouped together in a single category "Others". :::info - The definition of the outlier percentage is particularly useful when managing, for example a services company with thousands of distinct organizations, where many organizations contain only one or two users. We can safely choose to group into a single fictitious organization the 2% of all users that involve the smallest organizations. + The definition of the outlier percentage is particularly useful when managing, for example a services company with thousands of distinct organizations, where many organizations contain only one or two users. Safely group into a single fictitious organization the 2% of all users that involve the smallest organizations. ::: ```xml @@ -113,7 +113,7 @@ The following example is similar to the first one, except that we customize some ### Certification items :::info -Unlike `ResourcesStartBinding` and `ResourcesEndBinding`, `ResourcesStartExpression` and `ResourcesEndExpression` cannot be used to define the resources to include in the related certification campaigns. Thus, when needing to define which resources to include with more than start/end bindings, add a comparison based on `ResourceCertificationComparisonBinding`, `ResourceCertificationComparisonOperator` and `ResourceCertificationComparisonValue`. +Unlike `ResourcesStartBinding` and `ResourcesEndBinding`, `ResourcesStartExpression` and `ResourcesEndExpression` can't be used to define the resources to include in the related certification campaigns. Thus, when needing to define which resources to include with more than start/end bindings, add a comparison based on `ResourceCertificationComparisonBinding`, `ResourceCertificationComparisonOperator` and `ResourceCertificationComparisonValue`. ::: The following example includes in certification campaigns only the resources that have their `IsActivePosition` property set to `1`. @@ -132,7 +132,7 @@ The following example includes in certification campaigns only the resources tha ``` **Note:** must be configured together with the other `ResourceCertificationComparison` properties. -**Note:** when not specified, certification items are defined by `ResourcesStartBinding` and `ResourcesStartBinding`. And when they are not specified either, TODO: +**Note:** when not specified, certification items are defined by `ResourcesStartBinding` and `ResourcesStartBinding`. And when they aren't specified either, TODO: ## Properties @@ -141,19 +141,19 @@ The following example includes in certification campaigns only the resources tha |---|---| | B0 optional | **Type:** Int64 **Description:** Binding of the dimension 0 (up to 3V in [base32hex](/docs/identitymanager/current/integration-guide/toolkit/parameter-names)). The dimension can then be used in rules to filter the rules' targets. | | DisplayName_L1 required | **Type:** String **Description:** Display name of the context rule in language 1 (up to 16). | -| ExcludeExpression optional | **Type:** String **Description:** C# expression that defines the resources to exclude from context generation, because they should not be part of the role model and provisioning calculations. [See more details on C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). | +| ExcludeExpression optional | **Type:** String **Description:** C# expression that defines the resources to exclude from context generation, because they shouldn't be part of the role model and provisioning calculations. See [C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions) for details. | | Identifier required | **Type:** String **Description:** Unique identifier of the context rule. | | MinIdentitiesCount default value: 0 | **Type:** Int32 **Description:** Minimum number of identities to take into account to generate a rule by the role mining engine. | | Policy required | **Type:** Int64 **Description:** Identifier of the policy that the rule is part of. | | ReductionOutlierPercentage default value: 0.0 | **Type:** Float **Description:** Proportion of identities that are grouped together by role mining to aggregate all the small entities in one "other" category. This is used to speed up the mining process as the number of groups can be greatly reduced. | -| ResourceCertificationComparisonBinding optional | **Type:** Int64 **Description:** import ContextruleCertification from '@site/docs/identitymanager/current/_partials/contextrule-certification.mdx'; Binding of the property whose value is to be compared to `ResourceCertificationComparisonValue` in order to specify the resources to include in the related certification campaigns. | +| ResourceCertificationComparisonBinding optional | **Type:** Int64 **Description:** import ContextruleCertification from '@site/docs/identitymanager/current/_partials/contextrule-certification.mdx'; Binding of the property whose value is to be compared to `ResourceCertificationComparisonValue` to specify the resources to include in the related certification campaigns. | | ResourceCertificationComparisonOperator optional | **Type:** QueryComparisonOperator **Description:** import ContextruleCertification from '@site/docs/identitymanager/current/_partials/contextrule-certification.mdx'; Operator of the comparison that specifies the resources to include in the related certification campaigns. | -| ResourceCertificationComparisonValue optional | **Type:** String **Description:** import ContextruleCertification from '@site/docs/identitymanager/current/_partials/contextrule-certification.mdx'; Value to be compared to the value of `ResourcesCertificationComparisonBinding` in order to specify the resources to include in the related certification campaigns. | +| ResourceCertificationComparisonValue optional | **Type:** String **Description:** import ContextruleCertification from '@site/docs/identitymanager/current/_partials/contextrule-certification.mdx'; Value to be compared to the value of `ResourcesCertificationComparisonBinding` to specify the resources to include in the related certification campaigns. | | ResourcesBinding optional | **Type:** Int64 **Description:** Binding that represents the entity type of the contexts to be created from the `SourceEntityType`. It can also be defined via `ResourcesExpression`. | | ResourcesEndBinding optional | **Type:** Int64 **Description:** Binding of the date property among those from `ResourcesBinding` which specifies the end of validity for all [properties](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/recordsection#child-element-property) of the context. It can also be defined via `ResourcesEndExpression`. **Note:** a context rule's start and end dates are ignored when the related identities are also configured with [record sections](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/recordsection). | -| ResourcesEndExpression optional | **Type:** String **Description:** Expression based on the `ResourcesBinding` entity type that defines the end of validity for all [properties](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/recordsection#child-element-property) of the context. It can also be defined via `ResourcesEndBinding`. [See more details on C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). **Note:** a context rule's start and end dates are ignored when the related identities are also configured with [record sections](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/recordsection). | -| ResourcesExpression optional | **Type:** String **Description:** Expression based on `SourceEntityType` that defines the entity type of the contexts to be created. It can also be defined via `ResourcesBinding`. [See more details on C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). | +| ResourcesEndExpression optional | **Type:** String **Description:** Expression based on the `ResourcesBinding` entity type that defines the end of validity for all [properties](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/recordsection#child-element-property) of the context. It can also be defined via `ResourcesEndBinding`. See [C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions) for details. **Note:** a context rule's start and end dates are ignored when the related identities are also configured with [record sections](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/recordsection). | +| ResourcesExpression optional | **Type:** String **Description:** Expression based on `SourceEntityType` that defines the entity type of the contexts to be created. It can also be defined via `ResourcesBinding`. See [C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions) for details. | | ResourcesStartBinding optional | **Type:** Int64 **Description:** Binding of the date property among those from `ResourcesBinding` which specifies the beginning of validity for all [properties](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/recordsection#child-element-property) of the context. It can also be defined via `ResourcesStartExpression`. **Note:** a context rule's start and end dates are ignored when the related identities are also configured with [record sections](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/recordsection). | -| ResourcesStartExpression optional | **Type:** String **Description:** Expression based on the `ResourcesBinding` entity type that defines the beginning of validity for all [properties](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/recordsection#child-element-property) of the context. It can also be defined via `ResourcesStartBinding`. [See more details on C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). **Note:** a context rule's start and end dates are ignored when the related identities are also configured with [record sections](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/recordsection). | +| ResourcesStartExpression optional | **Type:** String **Description:** Expression based on the `ResourcesBinding` entity type that defines the beginning of validity for all [properties](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/recordsection#child-element-property) of the context. It can also be defined via `ResourcesStartBinding`. See [C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions) for details. **Note:** a context rule's start and end dates are ignored when the related identities are also configured with [record sections](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/recordsection). | | RiskFactorType optional | **Type:** RiskFactorType **Description:** Operator used to aggregate a user's risk scores together to compute the user's global risk score. `0` - **None**. `1` - **Max**: a user's final risk score is the maximum value among all their risk scores. `2` - **Average**: a user's final risk score is the average value of all their risk scores. | | SourceEntityType required | **Type:** Int64 **Description:** Identifier of the entity type of the parent resource. | diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/indirectresourcerule.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/indirectresourcerule.md index b1e6bb07f2..ec5236bf25 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/indirectresourcerule.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/indirectresourcerule.md @@ -26,6 +26,6 @@ For example: |---|---| | Correspondence optional | **Type:** Int64 **Description:** Property used to link the resource with an associated resource in another system, like Microsoft Entra ID (formerly Azure Active Directory) or SharePoint groups. | | CorrespondenceMembershipProperty optional | **Type:** Int64 **Description:** Same as Property but for the associated resource found in the external system. | -| Entitlement optional | **Type:** Int64 **Description:** Property used if the assignment is not given by the property in the external system. In the example, the assignment that we are looking for is not whether a user is in a group. Instead, it is the entitlement(s) given by the groups of which the user is a member. | -| Property required | **Type:** Int64 **Description:** Resource property for membership. Example: if our entity is a group, the group(s) it belongs to. | +| Entitlement optional | **Type:** Int64 **Description:** Property used if the assignment isn't given by the property in the external system. In the example, the assignment being sought isn't whether a user is in a group. Instead, it is the entitlements given by the groups of which the user is a member. | +| Property required | **Type:** Int64 **Description:** Resource property for membership. Example: if the entity is a group, the groups it belongs to. | | ResourceType required | **Type:** Int64 **Description:** Represents the Id of the ResourceType you want to use the rule on. | diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/miningrule.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/miningrule.md index c0cadf7847..082b9c2c6e 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/miningrule.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/miningrule.md @@ -4,7 +4,7 @@ description: "" sidebar_position: 8 --- -After roles are assigned to users, Identity Manager can use mining rules to perform role mining. Role mining means that Identity Manager analyzes existing assignments in order to suggest [single role rules](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/singlerolerule) which will assign [single roles](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/singlerole) to certain users matching given criteria. +After roles are assigned to users, Identity Manager can use mining rules to perform role mining. Role mining means that Identity Manager analyzes existing assignments to suggest [single role rules](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/singlerolerule) which will assign [single roles](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/singlerole) to certain users matching given criteria. :::info The [role mining task](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/jobs/tasks/server/getroleminingtask) replaces the existing single role rules in the specified rule policy with the new generated ones. @@ -52,13 +52,13 @@ The following rules have a different impact whether they are applied individuall | Category optional | **Type:** Int64 **Description:** Identifier of the category containing the roles targeted by role mining's analysis. | | EntityType required | **Type:** Int64 **Description:** Identifier of the entity type that represents the owners of the roles targeted by role mining's entitlement analysis. | | ExcludeRole default value: false | **Type:** Boolean **Description:** `true` to ignore the specified roles during the mining process triggered by the next mining rules (in terms of priority). | -| FalsePositiveMaxPercentage default value: 0.0 | **Type:** Float **Description:** Maximum authorized percentage of false positive assignments, i.e. roles that are assigned to users who should not have them. NETWRIX recommends around 1%, to be lowered when working on a sensitive application and/or a large user population, and vice versa. | +| FalsePositiveMaxPercentage default value: 0.0 | **Type:** Float **Description:** Maximum authorized percentage of false positive assignments, i.e. roles that are assigned to users who shouldn't have them. NETWRIX recommends around 1%, to be lowered when working on a sensitive application and/or a large user population, and vice versa. | | IncludeDoubleValidation default value: true | **Type:** Boolean **Description:** `true` to include in role mining's analysis the roles requiring two validations. | | IncludeNoValidation default value: true | **Type:** Boolean **Description:** `true` to include in role mining's analysis the roles requiring zero validations. | | IncludeSimpleValidation default value: true | **Type:** Boolean **Description:** `true` to include in role mining's analysis the roles requiring one validation. | | IncludeTripleValidation default value: true | **Type:** Boolean **Description:** `true` to include in role mining's analysis the roles requiring three validations. | | Policy required | **Type:** Int64 **Description:** Identifier of the policy that the mining rule is part of. | -| PrecisionMinPercentage default value: 100.0 | **Type:** Float **Description:** Minimum authorized percentage of correct role assignments, considering both the roles that are assigned to users who should have them, and the roles that are not assigned to users who should not have them. NETWRIX recommends around 99.5%, to be lowered when working on a sensitive application and/or a large user population, and vice versa. | -| Priority default value: 0 | **Type:** Int32 **Description:** Priority order of the mining rule. Identity Manager applies mining rules one after the other in descending order. **Info:** a mining rule can generate single role rules only for the single roles that were not already associated with a single role rule by another mining rule during the same role mining task. | +| PrecisionMinPercentage default value: 100.0 | **Type:** Float **Description:** Minimum authorized percentage of correct role assignments, considering both the roles that are assigned to users who should have them, and the roles that aren't assigned to users who shouldn't have them. NETWRIX recommends around 99.5%, to be lowered when working on a sensitive application and/or a large user population, and vice versa. | +| Priority default value: 0 | **Type:** Int32 **Description:** Priority order of the mining rule. Identity Manager applies mining rules one after the other in descending order. **Info:** a mining rule can generate single role rules only for the single roles that weren't already associated with a single role rule by another mining rule during the same role mining task. | | RulePolicy optional | **Type:** Int64 **Description:** Identifier of the policy that the generated single role rules are to be part of. **Note:** NETWRIX recommends using a policy dedicated to role mining in order not to remove existing assignment rules. | | RuleType default value: 0 | **Type:** Int32 **Description:** Represents the type of the generated single role rules. `0` - **Required**: the role is automatically assigned to users matching the criteria. `1` - **RequestedAutomatically**: the role is listed in the permission basket of new workers. These assignments can still be modified. For existing workers, the rule's type is `Suggested`. `2` - **Suggested**: the role is listed among suggested permissions in the permission basket of users matching the criteria during an entitlement request. Suggested assignments must be selected manually to be requested, and will go through the validation process. | diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/policy.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/policy.md index 9693e5618b..dc4d610efe 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/policy.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/policy.md @@ -35,9 +35,9 @@ All `ResourceType`, `SingleRole`, `CompositeRole` and `Category` must belong to | GracePeriod default value: 0 | **Type:** Int32 **Description:** Duration (in minutes) for which a lost automatic entitlement associated with this policy is prolonged. The grace period is only applied if the loss of the entitlement is due to a change in the rules (rule deletion or criteria changes). A review will be required to validate or decline the entitlement prolongation. Inferred entitlements won't be lost unless the end of the grace period is reached or the prolongation is declined. This value can be overwritten for each composite role and single role. | | HasImplicitApproval default value: false | **Type:** Boolean **Description:** `true` to skip the approval circuit when the requester has the appropriate review permissions. This value can be overwritten for each policy object (composite role, single role, resource type). | | Identifier required | **Type:** String **Description:** Unique identifier of the policy. | -| IsExternal default value: false | **Type:** Boolean **Description:** `true` to indicate that the policy's roles are outside Identity Manager's scope. The roles are managed by an external source, and Identity Manager cannot add, update nor delete any role. | +| IsExternal default value: false | **Type:** Boolean **Description:** `true` to indicate that the policy's roles are outside Identity Manager's scope. The roles are managed by an external source, and Identity Manager can't add, update nor delete any role. | | IsProvisioningEnabled default value: false | **Type:** Boolean **Description:** `true` to enable the provisioning policy. | | IsSimulationEnabled default value: false | **Type:** Boolean **Description:** `true` to enable the provisioning policy simulation. | -| ManualAssignmentEndDateLockedToContextMode default value: ExplicitNotContextBoundByDefault | **Type:** PolicyManualAssignmentEndDateLockedToContextMode **Description:** Explicit (default value): The manual assignments' EndDate can be specified by the user or can be locked to match the end date specified by context rules. Never: The manual assignments' EndDate needs to be specified. Always: The manual assignments' EndDate cannot be modified. They are computed by the policy to match the end date specified by context rules. | -| MaxDuration default value: 0 | **Type:** Int32 **Description:** Duration (in minutes) after which the assignments induced by the policy will be automatically revoked, if no earlier end date is specified. It impacts only the assignments which are performed after the maximum duration is set. Pre-existing assignments are not impacted. | +| ManualAssignmentEndDateLockedToContextMode default value: ExplicitNotContextBoundByDefault | **Type:** PolicyManualAssignmentEndDateLockedToContextMode **Description:** Explicit (default value): The manual assignments' EndDate can be specified by the user or can be locked to match the end date specified by context rules. Never: The manual assignments' EndDate needs to be specified. Always: The manual assignments' EndDate can't be modified. They are computed by the policy to match the end date specified by context rules. | +| MaxDuration default value: 0 | **Type:** Int32 **Description:** Duration (in minutes) after which the assignments induced by the policy will be automatically revoked, if no earlier end date is specified. It impacts only the assignments which are performed after the maximum duration is set. Pre-existing assignments aren't impacted. | | ProlongationWithoutApproval default value: false | **Type:** Boolean **Description:** `true` to allow the policy's roles to be extended without any validation. | diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/recordsection.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/recordsection.md index 459b401d37..d32dac53bd 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/recordsection.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/recordsection.md @@ -4,31 +4,31 @@ description: "" sidebar_position: 10 --- -Record sections shape identity data for a given entity type, by grouping properties into sections, for example personal data, contract or position. +Record sections shape identity data for a given entity type, by grouping properties into sections, for example personal data, contract, or position. Record sections impact the generation of identities' contexts which contain users' dimension values valid on a given period of time. The aim is to simplify the application of the role model' rules for provisioning. Thanks to this data organization in sections, the identities of a given entity type can be modeled by more than one context over time, even simultaneously. This means that users can have more than one contract, or position, at a time, and that data changes can be anticipated. -[See more details about identity modeling](/docs/identitymanager/current/integration-guide/identity-management/joiners-movers-leavers/position-change#a-model-for-identity-changes). +See [identity modeling](/docs/identitymanager/current/integration-guide/identity-management/joiners-movers-leavers/position-change#a-model-for-identity-changes) for details. :::info **Configuration recommendations:** -As record sections cannot be configured without a [context rule](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/contextrule), NETWRIX recommends starting with the configuration of the context rule before configuring record sections. +As record sections can't be configured without a [context rule](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/contextrule), NETWRIX recommends starting with the configuration of the context rule before configuring record sections. -NETWRIX recommends defining at least two record sections: a default section for the properties shared by all records, and another section for a given set of properties which differentiate between records. The default section must contain zero properties, the shared properties are those that are not defined in the other section(s). +NETWRIX recommends defining at least two record sections: a default section for the properties shared by all records, and another section for a given set of properties which differentiate between records. The default section must contain zero properties, the shared properties are those that aren't defined in the other sections. -For example, to model several positions for a single user, we configure the default record section to contain the properties shared by all positions such as personal data, and we configure the position section to contain the properties specific to each position. Similar to the position section, we can also typically configure a section for contracts. +For example, to model several positions for a single user, configure the default record section to contain the properties shared by all positions such as personal data, and configure the position section to contain the properties specific to each position. Similar to the position section, you can also typically configure a section for contracts. ::: ## Examples The following example models users from the `Directory_User` entity type with three sets of properties: user properties, contract properties and position properties. All created records will be resources from the `Directory_UserRecord` entity type. -The properties from the contract (or position) section are the properties specific to each contract (or position). The properties from `Directory_User` that are not specified in the record sections are the properties shared between all records, here user properties. +The properties from the contract (or position) section are the properties specific to each contract (or position). The properties from `Directory_User` that aren't specified in the record sections are the properties shared between all records, here user properties. -Each section must be defined with start and end dates, so that Identity Manager's engine is able to combine all periods of validity and apply the rules with the right input at any time. +Each section must be defined with start and end dates, so that Identity Manager's engine can combine all periods of validity and apply the rules with the right input at any time. ```xml Default section: @@ -60,7 +60,7 @@ Position section: ### InstanceKeyExpression -The following example computes a unique key for each record section instance. This way, we can distinguish between contracts thanks to their identifiers, same for positions, and between user property sets thanks to a C# expression based on the start date. +The following example computes a unique key for each record section instance. This way, distinguish between contracts thanks to their identifiers, same for positions, and between user property sets thanks to a C# expression based on the start date. ```xml Default section: @@ -81,14 +81,14 @@ Position section: ``` :::info -An instance key is required when we need to uniquely identify a context, i.e. when we may have several simultaneous contexts. +An instance key is required to uniquely identify a context, that is, when there are several simultaneous contexts. For example, an instance key is required for the position section when users can have overlapping positions. ::: ### IsDefaultBoundariesSection -The following example uses the contract start/end dates as default boundaries in users' [validity period](/docs/identitymanager/current/integration-guide/identity-management/joiners-movers-leavers/on-offboarding#period-of-validity), instead of those from the default section. It may be because, for example, HR services do not enter an end date for the personal data of users on permanent contracts. So we prefer to use the start and end dates of their contracts. +The following example uses the contract start/end dates as default boundaries in users' [validity period](/docs/identitymanager/current/integration-guide/identity-management/joiners-movers-leavers/on-offboarding#period-of-validity), instead of those from the default section. It may be because, for example, HR services don't enter an end date for the personal data of users on permanent contracts. In this case, use the start and end dates of their contracts instead. ```xml Contract section: @@ -100,13 +100,13 @@ Contract section: ### Context extension -There can be some time gap where no context is defined, for example a time gap with a position but no contract or vice versa. Identity Manager offers the possibility to choose whether an existing context is to be extended to the period without context. And in case we decide to use another context and extend its values, which context should it be? +Time gaps may exist where no context is defined, for example with a position but no contract, or vice versa. Identity Manager lets you choose whether to extend an existing context to periods without context. When using another context and extending its values, which context should you use? ![Schema - ExtensionKind](/images/identitymanager/recordsection_extensionkind.webp) -Here, we decide to extend an existing contract to the gap, for example because users' email addresses are built using the contract type to add `-ext` for external users. And we decide to not extend the position. +This example extends an existing contract to the gap, for example because users' email addresses are built using the contract type to add `-ext` for external users. The position isn't extended. -In the following example, the contract section uses `SortKeyExpression` to establish between existing contracts a priority order that will determine which contract should be extended to the gap. Based on this C# expression that returns a value `A`, `B` or `C`, the `ExtendedSortKey` considers as extendable only the contract(s) whose expression returns `C`. +In the following example, the contract section uses `SortKeyExpression` to establish between existing contracts a priority order that will determine which contract should be extended to the gap. Based on this C# expression that returns a value `A`, `B` or `C`, the `ExtendedSortKey` considers as extendable only the contracts whose expression returns `C`. The position section uses `ExtensionKind` set to `None` to block the extension mechanism. @@ -135,16 +135,16 @@ When not specifying any sort key nor extended sort key, Identity Manager will se |---|---| | BoundaryKind default value: 0 | **Type:** RecordBoundaryKind **Description:** Defines how the section dates are computed for a resource, when the current start/end dates are null. `0` - None: start date and end date are equal respectively to the minimum value of `StartProperty` and maximum value of `EndProperty` when comparing the default sections of all records. `1` - Kept: start and end dates are equal respectively to the default start date (1900/01/01 00:00:00) and end date (2079/06/06 00:00:00). **Info:** the boundary has no effect on the default section which is the reference to compute the default dates in other sections. When the default section's start/end dates are null, then they equal the default start/end dates. | | DisplayName_L1 required | **Type:** String **Description:** Display name of the section in language 1 (up to 16). | -| EndProperty optional | **Type:** Int64 **Description:** Date property among those from the `ResourceEntityType` which specifies the end of validity for all [properties](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/recordsection#child-element-property) of the section. It cannot be a property computed by an `EntityPropertyExpression`. | +| EndProperty optional | **Type:** Int64 **Description:** Date property among those from the `ResourceEntityType` which specifies the end of validity for all [properties](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/recordsection#child-element-property) of the section. It can't be a property computed by an `EntityPropertyExpression`. | | ExtendedSortKey optional | **Type:** String **Description:** Value used as a threshold for `SortKeyExpression` values to determine whether the [property](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/recordsection#child-element-property) values of a given record section can be extended from a context where the values are defined to another context where no properties from the section are defined. This extension is enabled only when the value of `SortKeyExpression` of the section is higher (with an ordinal comparison) than `ExtendedSortKey`. | -| ExtensionKind default value: 0 | **Type:** RecordExtensionKind **Description:** Defines whether the section's property values can be extended (copied) from a context where the properties are defined to another context where no properties from the section are defined. `0` - Default: the section's property values can be extended. `4` - None: the section's property values cannot be extended. | +| ExtensionKind default value: 0 | **Type:** RecordExtensionKind **Description:** Defines whether the section's property values can be extended (copied) from a context where the properties are defined to another context where no properties from the section are defined. `0` - Default: the section's property values can be extended. `4` - None: the section's property values can't be extended. | | Identifier required | **Type:** String **Description:** Unique identifier of the section. | -| InstanceKeyExpression optional | **Type:** String **Description:** Expression returning a key to uniquely identify a context, i.e. distinguish between job positions for example when users can have several concurrent positions, or between contracts. [See more details on C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). | +| InstanceKeyExpression optional | **Type:** String **Description:** Expression returning a key to uniquely identify a context, i.e. distinguish between job positions for example when users can have several concurrent positions, or between contracts. See [C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions) for details. | | IsDefaultBoundariesSection default value: false | **Type:** Boolean **Description:** `true` to use the start/end dates of this section as the default boundaries, i.e. the start/end dates of users' [validity period](/docs/identitymanager/current/integration-guide/identity-management/joiners-movers-leavers/on-offboarding#period-of-validity). When no section has `IsDefaultBoundaries` set to `true`, the default section (the one without properties) is automatically selected. | | ResourceEntityType required | **Type:** Int64 **Description:** Identifier of the entity type of the multiple records to be created. | -| SortKeyExpression optional | **Type:** String **Description:** C# expression used to compute a value for each record, to be used as a priority, following an ordinal comparison. [See more details on C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). When a record section has `ExtensionKind` set to `Default` and a priority value higher than `ExtendedSortKey`, then the record property values can be extended from a context where the values are defined to another context where no properties from the section are defined. | +| SortKeyExpression optional | **Type:** String **Description:** C# expression used to compute a value for each record, to be used as a priority, following an ordinal comparison. See [C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions) for details. When a record section has `ExtensionKind` set to `Default` and a priority value higher than `ExtendedSortKey`, then the record property values can be extended from a context where the values are defined to another context where no properties from the section are defined. | | SourceEntityType required | **Type:** Int64 **Description:** Identifier of the entity type of the parent resource. | -| StartProperty optional | **Type:** Int64 **Description:** Date property among those from the `ResourceEntityType` which specifies the beginning of validity for all [properties](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/recordsection#child-element-property) of the section. It cannot be a property computed by an `EntityPropertyExpression`. | +| StartProperty optional | **Type:** Int64 **Description:** Date property among those from the `ResourceEntityType` which specifies the beginning of validity for all [properties](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/recordsection#child-element-property) of the section. It can't be a property computed by an `EntityPropertyExpression`. | ## Child Element: Property A record section is a set of record properties which belong to the resource entity type. @@ -153,7 +153,7 @@ A record section is a set of record properties which belong to the resource enti ### Examples In the following example, the position section gathers the properties `Organization`, `Location` and `Title`, while the default section gathers all the other properties from `Directory_UserRecord`. -The property `Location` can be extended from a context where the location is defined to a context where it is not. The two other properties cannot be extended. +The property `Location` can be extended from a context where the location is defined to a context where it isn't. The two other properties can't be extended. See more details about record extension. @@ -175,6 +175,6 @@ Position section: |Property|Details| |---|---| -| ExtensionKind default value: 0 | **Type:** RecordExtensionKind **Description:** Defines whether the property value can be extended (copied) from a context where the section properties are defined to another context where no properties from the section are defined. `0` - Default: the property value can be extended. `4` - None: the property value cannot be extended. **Note:** a property value can be extended only if the section is extendable too. | +| ExtensionKind default value: 0 | **Type:** RecordExtensionKind **Description:** Defines whether the property value can be extended (copied) from a context where the section properties are defined to another context where no properties from the section are defined. `0` - Default: the property value can be extended. `4` - None: the property value can't be extended. **Note:** a property value can be extended only if the section is extendable too. | | IsExcluded default value: false | **Type:** Boolean **Description:** Excludes the given property from the section. This is used only in the default section to remove properties such as the RecordIdentifier that are always different between all the records and that are thus not interesting for the provisioning rules. | -| Property required | **Type:** Int64 **Description:** Identifier of the property from the record section's `ResourceEntityType` that is to be part of the section. | +| Property required | **Type:** Int64 **Description:** Identifier of the property from the record section's `ResourceEntityType` that is included in the section. | diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/resourceclassificationrule.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/resourceclassificationrule.md index b2b7eaac81..4bf8e6a6dd 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/resourceclassificationrule.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/resourceclassificationrule.md @@ -4,7 +4,7 @@ description: "" sidebar_position: 11 --- -In Identity Manager, this type of rule is used to classify the resources based on a C# expression. +In Identity Manager, use this rule type to classify resources based on a C# expression. ## Examples @@ -23,4 +23,4 @@ The following example declares a rule to classify the Active Directory accounts | ResourceType required | **Type:** Int64 **Description:** Represents the resource type definition. | | ResourceTypeIdentificationConfidenceLevel default value: 0 | **Type:** Int32 **Description:** Defines the confidence level used to match the resources. | | SourceMatchedConfidenceLevel default value: false | **Type:** Boolean **Description:** Defines the confidence level used to match the sources. | -| TargetExpression optional | **Type:** String **Description:** Defines the C# expression used to classify the resources. [See more details on C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). | +| TargetExpression optional | **Type:** String **Description:** Defines the C# expression used to classify the resources. See [C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions) for details. | diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/resourcecorrelationrule.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/resourcecorrelationrule.md index dc9b83199c..a449295265 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/resourcecorrelationrule.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/resourcecorrelationrule.md @@ -4,7 +4,7 @@ description: "" sidebar_position: 12 --- -A correlation rule is used to [correlate](/docs/identitymanager/current/introduction-guide/overview/entitlement-management) the resources, i.e. link resources to their owners. +A correlation rule [correlates](/docs/identitymanager/current/introduction-guide/overview/entitlement-management) resources, linking them to their owners. ## Examples @@ -36,7 +36,7 @@ The following example creates an Active Directory correlation rule based on the ``` -This example also uses a confidence rate equals to 80%. +This example also uses a confidence rate of 80%. ## Properties @@ -46,7 +46,7 @@ This example also uses a confidence rate equals to 80%. | Policy required | **Type:** Int64 **Description:** Identifier of the policy that the rule is part of. | | ResourceType required | **Type:** Int64 **Description:** Identifier of the resource type. | | SourceBinding optional | **Type:** Int64 **Description:** Binding property from the source system. | -| SourceExpression optional | **Type:** String **Description:** Binding expression based on properties from the source system. [See more details on C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). | -| SourceMatchedConfidenceLevel default value: 0 | **Type:** Int32 **Description:** Defines the correlation confidence rate of this rule. If the value is less than 100, we process a manual review step to confirm the choice. | +| SourceExpression optional | **Type:** String **Description:** Binding expression based on properties from the source system. See [C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions) for details. | +| SourceMatchedConfidenceLevel default value: 0 | **Type:** Int32 **Description:** Defines the correlation confidence rate of this rule. If the value is less than 100, a manual review step confirms the choice. | | TargetBinding optional | **Type:** Int64 **Description:** Binding property from the target system. | -| TargetExpression optional | **Type:** String **Description:** Binding expression based on properties from the target system. [See more details on C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). | +| TargetExpression optional | **Type:** String **Description:** Binding expression based on properties from the target system. See [C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions) for details. | diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/resourcetype.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/resourcetype.md index 1ef7ef9d29..e6352d7975 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/resourcetype.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/resourcetype.md @@ -5,7 +5,7 @@ sidebar_position: 13 --- In Identity Manager, a resource type is a conceptual model used to categorize resources. It groups together, with a meaningful name, resources sharing the same intent and the same authorization system. Resource types are assigned directly to a resource rather than mapped to a role. -A resource type can be assigned manually, or configured to be assigned automatically via a [resource type rule](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/resourcetype#child-element-typerule). +A resource type can be assigned manually, or configured to be assigned automatically by a [resource type rule](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/resourcetype#child-element-typerule). ## Examples @@ -23,13 +23,13 @@ The following example declares a new resource type to provision the LDAP service ### DependsOn -This option is used to configure another resource type as prerequisite for this resource type. +This option configures another resource type as a prerequisite for this resource type. For example, a Microsoft Exchange account requires the email address of a related Active Directory account. -In this case, we want to configure the `Exchange Account` resource type so that a user cannot own an Exchange account when they do not own an AD account. +In this case, configure the `Exchange Account` resource type so a user can't own an Exchange account unless they own an AD account. -The following example is meant to perform an automatic check to prevent the execution of any provisioning order for the creation of an Exchange account when the user does not own an AD nominative account. +The following example performs an automatic check to prevent provisioning orders for Exchange account creation when the user doesn't own an AD nominative account: ```xml @@ -37,13 +37,13 @@ The following example is meant to perform an automatic check to prevent the exec ### DependsOnOwnerProperty -This option is used to configure a property as prerequisite for the resource type. +This option configures a property as a prerequisite for the resource type. -Consider an Active Directory administrator account which should be able to perform manual provisioning to ServiceNow. Then it requires the random identifier computed by ServiceNow. +Consider an Active Directory administrator account that performs manual provisioning to ServiceNow. It requires the random identifier computed by ServiceNow. -In this case, we want to configure the `AD_Entry_AdministrationUser` resource type so that a user cannot own an AD administrator account when they do not have an identifier in ServiceNow. +In this case, configure the `AD_Entry_AdministrationUser` resource type so a user can't own an AD administrator account unless they have an identifier in ServiceNow. -The following example is meant to perform an automatic check to prevent the execution of any provisioning order for the creation of an AD administrator account when the user does not have an identifier in ServiceNow. +The following example performs an automatic check to prevent provisioning orders for AD administrator account creation when the user doesn't have an identifier in ServiceNow: ```xml @@ -61,7 +61,7 @@ The following scenario is about a user named Cedric Blanc, whose AD's `sn` prope Let's see what happens when the user's name is changed manually directly in the AD. -Suppose that we change in the AD the last name to `White`. As the scalar rule computes the `sn` value based on the user's data which still states the last name `Blanc`, such a change induces a difference between the value calculated by the rule and the actual value in the AD. This difference is spotted by the next synchronization, triggering a non-conforming assignment on the **Resource Reconciliation** page. +Suppose the last name is changed in the AD to `White`. As the scalar rule computes the `sn` value based on the user's data which still states the last name `Blanc`, such a change induces a difference between the value calculated by the rule and the actual value in the AD. This difference is spotted by the next synchronization, triggering a non-conforming assignment on the **Resource Reconciliation** page. ![Example - State 1](/images/identitymanager/DiscardManualAssignments_state1_V602.webp) @@ -69,13 +69,13 @@ Suppose that we change in the AD the last name to `White`. As the scalar rule co ![Example - Step 2](/images/identitymanager/DiscardManualAssignments_step2_V602.webp) -Once this manual new value is confirmed, the property is stated as `Approved`. +When this manual new value is confirmed, the property is stated as `Approved`. ![Example - State 2](/images/identitymanager/DiscardManualAssignments_state2_V602.webp) -Now suppose that the user's last name is changed to `Black` via Identity Manager's workflows. As the source data is changed, the scalar rule computes a new value for `sn`. There are two options: +Now suppose that the user's last name is changed to `Black` through Identity Manager's workflows. As the source data changes, the scalar rule computes a new value for `sn`. You have two options: -* The default configuration (`DiscardManualAssignments` set to `false`) considers manual assignments, i.e. changes made directly in the managed system, as authoritative. So there will be no provisioning of the newly computed value for `sn`. The current `sn` value that was written manually in the AD stays as is, no matter the changes in the source data (here the user's last name). Identity Manager only states the property's value as `Questioned`. +* The default configuration (`DiscardManualAssignments` set to `false`) treats manual assignments (changes made directly in the managed system) as authoritative. Identity Manager won't provision the newly computed value for `sn`. The current `sn` value that was written manually in the AD remains unchanged, regardless of source data changes (here, the user's last name). Identity Manager marks the property's value as `Questioned`. ![Example - State 3](/images/identitymanager/DiscardManualAssignments_state3_V602.webp) @@ -83,11 +83,11 @@ Now suppose that the user's last name is changed to `Black` via Identity Manager No change in the source data can affect the property's value. However, any manual change made in the managed system will trigger a non-conforming assignment. Then, reconciling the property by choosing to keep Identity Manager's suggested value will make the property's value go back to `Calculated` and thus follow the changes in the source data. ::: -* If `DiscardManualAssignments` is set to `true`, then the state of the property's value does not matter. Identity Manager applies the rules of the role model, and generates a provisioning order to overwrite the manual change `White` with the newly computed value `Black`. +* If `DiscardManualAssignments` is set to `true`, the property's value state doesn't matter. Identity Manager applies the role model's rules and generates a provisioning order to overwrite the manual change `White` with the newly computed value `Black`. ![Example - State 4](/images/identitymanager/DiscardManualAssignments_state4_V602.webp) -In this scenario for Cedric Blanc, these behaviors can be summed up like the following: +In the scenario for Cedric Blanc, these behaviors can be summarized: ![Discardmanualassignments State0 V602](/images/identitymanager/DiscardManualAssignments_state0_V602.webp) @@ -96,37 +96,37 @@ In this scenario for Cedric Blanc, these behaviors can be summed up like the fol |Property|Details| |---|---| | AllowAdd default value: true | **Type:** Boolean **Description:** Enables Identity Manager to automatically create new resources in the managed system when their owners are given the right entitlements. Otherwise, resource managers must create resources manually directly in the managed system. | -| AllowRemove default value: true | **Type:** Boolean **Description:** Enables Identity Manager to automatically deprovision resources in the managed system when their owners are deprived of the right entitlements. Otherwise, Identity Manager is able to delete resources in the managed system only with a manual approval on the **Resource Reconciliation** screen. | -| ApprovalWorkflowType default value: 0 | **Type:** ProvisioningPolicyApprovalWorkflow **Description:** Indicates the number of validation to give to a role given manually (from `None` to `Three`). The value `ManualAssignmentNotAllowed` is used when a manual assignment cannot be performed. **Note:** NETWRIX recommends using `ManualAssignmentNotAllowed` for all resource types. | -| ArgumentsExpression optional | **Type:** String **Description:** C# expression used to compute the arguments of provisioning orders, for example a workflow identifier, in a situation where it is not obvious. The aim is to enable an `InternalWorkflow` connector to fulfill correctly a virtual managed system by launching the right workflows based on a given provisioning order. This expression must return a dictionary of string. **Note:** `ArgumentsExpression` is useful only when provisioning via the following packages: [Active Directory](/docs/identitymanager/current/integration-guide/connectors/references-packages/Active Directory); [Apache Directory](/docs/identitymanager/current/integration-guide/connectors/references-packages/Apache Directory); [Generic LDAP](/docs/identitymanager/current/integration-guide/connectors/references-packages/Generic LDAP); [Open LDAP](/docs/identitymanager/current/integration-guide/connectors/references-packages/Open LDAP); [Oracle LDAP](/docs/identitymanager/current/integration-guide/connectors/references-packages/Oracle LDAP); [Red Hat Directory Server](/docs/identitymanager/current/integration-guide/connectors/references-packages/Red Hat Directory Server); [Workflow](/docs/identitymanager/current/integration-guide/connectors/references-packages/workflow). | +| AllowRemove default value: true | **Type:** Boolean **Description:** Enables Identity Manager to automatically deprovision resources in the managed system when their owners are deprived of the right entitlements. Otherwise, Identity Manager can delete resources in the managed system only with a manual approval on the **Resource Reconciliation** screen. | +| ApprovalWorkflowType default value: 0 | **Type:** ProvisioningPolicyApprovalWorkflow **Description:** Indicates the number of validation to give to a role given manually (from `None` to `Three`). The value `ManualAssignmentNotAllowed` is used when a manual assignment can't be performed. **Note:** NETWRIX recommends using `ManualAssignmentNotAllowed` for all resource types. | +| ArgumentsExpression optional | **Type:** String **Description:** C# expression used to compute the arguments of provisioning orders, for example a workflow identifier, in a situation where it isn't obvious. The aim is to enable an `InternalWorkflow` connector to fulfill correctly a virtual managed system by launching the right workflows based on a given provisioning order. This expression must return a dictionary of string. **Note:** `ArgumentsExpression` is useful only when provisioning via the following packages: [Active Directory](/docs/identitymanager/current/integration-guide/connectors/references-packages/Active Directory); [Apache Directory](/docs/identitymanager/current/integration-guide/connectors/references-packages/Apache Directory); [Generic LDAP](/docs/identitymanager/current/integration-guide/connectors/references-packages/Generic LDAP); [Open LDAP](/docs/identitymanager/current/integration-guide/connectors/references-packages/Open LDAP); [Oracle LDAP](/docs/identitymanager/current/integration-guide/connectors/references-packages/Oracle LDAP); [Red Hat Directory Server](/docs/identitymanager/current/integration-guide/connectors/references-packages/Red Hat Directory Server); [Workflow](/docs/identitymanager/current/integration-guide/connectors/references-packages/workflow). | | BlockProvisioning default value: true | **Type:** Boolean **Description:** `true` to block the provisioning policy orders. | | Category optional | **Type:** Int64 **Description:** Resource type category. | | CorrelateMultipleResources default value: false | **Type:** Boolean **Description:** `true` to extend the QueryRule/CorrelationRule to match as many target resources as possible (no blocking like this is normally the case). | | DependsOn optional | **Type:** Int64 **Description:** Identifier of another resource type that must be provisioned for a given identity before the current resource type can be provisioned for said identity. | | DependsOnOwnerProperty optional | **Type:** Int64 **Description:** Identifier of one of the owner properties that must be filled before the current resource type can be provisioned for said identity. | | Description_L1 optional | **Type:** String **Description:** Describe this resource type in detail. | -| DiscardManualAssignments default value: false | **Type:** Boolean **Description:** `true` to always allow the provisioning of a new property value, i.e. re-computed by a provisioning rule after a change in the source data, no matter the property's current workflow state. Set to `false`, any manual change of a property's value made directly in the target system will be "protected" (only after the change is approved in Identity Manager in **Resource Reconciliation**). It means that a future change in the source data will not trigger the provisioning of the new value to the target system. Instead, Identity Manager will keep the value of the manual change, and state the value as `Questioned`. This option should be set to `true` when: * using multiple authoritative sources and the latest value should be provisioned; * a source system is not often synchronized to Identity Manager but should stay the authoritative source. | +| DiscardManualAssignments default value: false | **Type:** Boolean **Description:** `true` to always allow the provisioning of a new property value, i.e. re-computed by a provisioning rule after a change in the source data, no matter the property's current workflow state. Set to `false`, any manual change of a property's value made directly in the target system will be "protected" (only after the change is approved in Identity Manager in **Resource Reconciliation**). It means that a future change in the source data will not trigger the provisioning of the new value to the target system. Instead, Identity Manager will keep the value of the manual change, and state the value as `Questioned`. This option should be set to `true` when: * using multiple authoritative sources and the latest value should be provisioned; * a source system isn't often synchronized to Identity Manager but should stay the authoritative source. | | DisplayName_L1 required | **Type:** String **Description:** Display name of the resource type in language 1 (up to 16). | -| FulfillHoursAheadOfTime default value: 0 | **Type:** Int32 **Description:** Anticipate resource fulfill order hours ahead of they start time. It is helpful for manual fulfillment and/or long fulfillment process. It differs from TimeOffset because the start date of the resource to fulfill is not impacted. | +| FulfillHoursAheadOfTime default value: 0 | **Type:** Int32 **Description:** Anticipate resource fulfill order hours ahead of they start time. It is helpful for manual fulfillment and/or long fulfillment process. It differs from TimeOffset because the start date of the resource to fulfill isn't impacted. | | HideOnSimplifiedView default value: false | **Type:** Boolean **Description:** `true` to hide this resource type in the basket simplified view. This flag is applied only on automatic assignments. | | Identifier required | **Type:** String **Description:** Unique identifier of the resource type. | | ImplicitApproval default value: 0 | **Type:** Byte **Description:** Indicates if the validation steps of the resource type can be skipped. `0` - Inherited: implicit approval value in the associated policy. `1` - Explicit: all the workflow steps must be approved. `2` - Implicit: the workflow steps can be skipped if the requester has enough permissions. | -| ManualAssignmentEndDateLockedToContextMode default value: Inherited | **Type:** RoleManualAssignmentEndDateLockedToContextMode **Description:** Inherited (default value): Use the policy's ManualAssignmentEndDateLockedToContextMode value. ExplicitNotContextBoundByDefault: The manual assignments' end date can be specified by the user or can be locked to match the end date specified by context rules. By default, in the UI, it is not automatically locked. ExplicitContextBoundByDefault: The manual assignments' end date can be specified by the user or can be locked to match the end date specified by context rules. By default, in the UI, it is automatically locked. Never: The manual assignments' end date needs to be specified. Always: The manual assignments' end date cannot be modified. They are computed by the policy to match the end date specified by context rules. | -| MaximumDelete default value: 0 | **Type:** Int32 **Description:** Deleted lines threshold. Sets the maximum number of resources that can be removed from the resource type when running the provisioning job. | +| ManualAssignmentEndDateLockedToContextMode default value: Inherited | **Type:** RoleManualAssignmentEndDateLockedToContextMode **Description:** Inherited (default value): Use the policy's ManualAssignmentEndDateLockedToContextMode value. ExplicitNotContextBoundByDefault: The manual assignments' end date can be specified by the user or can be locked to match the end date specified by context rules. By default, in the UI, it isn't automatically locked. ExplicitContextBoundByDefault: The manual assignments' end date can be specified by the user or can be locked to match the end date specified by context rules. By default, in the UI, it is automatically locked. Never: The manual assignments' end date needs to be specified. Always: The manual assignments' end date can't be modified. They are computed by the policy to match the end date specified by context rules. | +| MaximumDelete default value: 0 | **Type:** Int32 **Description:** Deleted lines threshold. Sets the maximum number of resources that can be removed from the resource type when the provisioning job runs. | | MaximumDeletePercent default value: 30 | **Type:** Int32 **Description:** Deleted lines threshold in percent. | -| MaximumInsert default value: 0 | **Type:** Int32 **Description:** Inserted lines threshold. Sets the maximum number of resources that can be added into the resource type when running the provisioning job. | +| MaximumInsert default value: 0 | **Type:** Int32 **Description:** Inserted lines threshold. Sets the maximum number of resources that can be added into the resource type when the provisioning job runs. | | MaximumInsertPercent default value: 30 | **Type:** Int32 **Description:** Inserted lines threshold in percent. | -| MaximumUpdate default value: 0 | **Type:** Int32 **Description:** Updated lines threshold. Sets the maximum number of resources that can be modified within the resource type when running the provisioning job. | +| MaximumUpdate default value: 0 | **Type:** Int32 **Description:** Updated lines threshold. Sets the maximum number of resources that can be modified within the resource type when the provisioning job runs. | | MaximumUpdatePercent default value: 30 | **Type:** Int32 **Description:** Updated lines threshold in percent. | | P0 default value: false | **Type:** Boolean **Description:** `true` to indicate that the resource type is parameterized, i.e. there is at least one type rule configured to assign the resource type based on the dimension 0 (up to 3V following the [base32hex convention](/docs/identitymanager/current/integration-guide/toolkit/parameter-names)). | | Policy required | **Type:** Int64 **Description:** Identifier of the policy that the resource type is part of. | | ProlongationWithoutApproval default value: 0 | **Type:** ProlongationWithoutApproval **Description:** Indicates whether the resource type can be extended without any validation. `0` - Inherited: gets the value from the policy. `1` - Enabled. `2` - Disabled. | | R0 default value: false | **Type:** Boolean **Description:** `true` to set the dimension 0 (up to 3V following the [base32hex convention](/docs/identitymanager/current/integration-guide/toolkit/parameter-names)) as a required parameter when assigning the resource type. | -| RemoveOrphans default value: false | **Type:** Boolean **Description:** `true` to authorize the deprovisioning of this resource when it does not have an owner. Can only be `true` when AllowRemove property is also true. | +| RemoveOrphans default value: false | **Type:** Boolean **Description:** `true` to authorize the deprovisioning of this resource when it doesn't have an owner. Can only be `true` when AllowRemove property is also true. | | SourceEntityType required | **Type:** Int64 **Description:** Identifier of the source entity type. | | SuggestAllCorrelations default value: false | **Type:** Boolean **Description:** Suggest all correlations, whatever the confidence rate of the correlation rule. | | TargetEntityType required | **Type:** Int64 **Description:** Identifier of the target entity type. | -| TransmittedStateValidityPeriod default value: 0 | **Type:** Int32 **Description:** Time period (in minutes) after which fulfillment orders in Transmitted/Executed states are automatically set in Error state. **Recommendations:** - When provisioning automatically, then set 1, 2 or 3 times the period between two synchronizations. - When provisioning manually and synchronizing regularly, then set around 15 days. - When provisioning manually with few synchronizations, then don't set it. | +| TransmittedStateValidityPeriod default value: 0 | **Type:** Int32 **Description:** Time period (in minutes) after which fulfillment orders in Transmitted/Executed states are automatically set in Error state. **Recommendations:** - When provisioning automatically, then set 1, 2, or 3 times the period between two synchronizations. - When provisioning manually and synchronizing regularly, then set around 15 days. - When provisioning manually with few synchronizations, then don't set it. | ## Child Element: BinaryRule A *ResourceBinaryRule* allows to specify the file that must be set to an assigned resource **binary property**. It is defined by a child element `` of the `` element. The source file should already be synchronized and stored inside and reference as an EntityType property. @@ -142,20 +142,20 @@ A *ResourceBinaryRule* allows to specify the file that must be set to an assigne #### TimeOffset -[See more information about time offsets](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/resourcetype#timeoffset-3). +See the [time offset](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/resourcetype#timeoffset-3) section for details. ### Properties |Property|Details| |---|---| -| Binding optional | **Type:** Int64 **Description:** Defines the binding expression to get the file property. | +| Binding optional | **Type:** Int64 **Description:** Defines the binding expression for the file property. | | Policy required | **Type:** Int64 **Description:** Identifier of the policy that the rule is part of. | | Property required | **Type:** Int64 **Description:** Identifier of the property used to represent the file on the target EntityType. | | SingleRole optional | **Type:** Int64 **Description:** Identifier of the [single role](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/singlerole). The single role must be assigned to the owner so that the file can be provisioned on the resource. | | TimeOffsetAfterReference default value: 0 | **Type:** Int32 **Description:** Defines the offset after reference (in minutes). | | TimeOffsetBeforeReference default value: 0 | **Type:** Int32 **Description:** Defines the offset before reference (in minutes). | -| TimeOffsetReference default value: 0 | **Type:** TimeOffsetReference **Description:** Offset mode defining which dates to use as references, in order to apply the time offset. The time period for which the rule is applied is adjusted accordingly. `0` - **Default**: the offset inherited from the type rule. `1` - **Around**: the offset before reference is applied from the start date of the resource, and the offset after reference is applied from the end date. `2` - **Before**: the offset before and after reference are both applied from the start date of the resource. `3` - **After**: the offset before and after reference are both applied from the end date of the resource. **Note:** in a situation with several binary rules, the order of application is: `After`, then `Before`, then `Around`, then `Default`. Each rule is able to overwrite those previously applied in case they overlap. **Warning**: two offsets of the same mode should never overlap. Resources' start and end dates can be configured through record sections and/or context rules. | +| TimeOffsetReference default value: 0 | **Type:** TimeOffsetReference **Description:** Offset mode defining which dates to use as references, to apply the time offset. The time period for which the rule is applied is adjusted accordingly. `0` - **Default**: the offset inherited from the type rule. `1` - **Around**: the offset before reference is applied from the start date of the resource, and the offset after reference is applied from the end date. `2` - **Before**: the offset before and after reference are both applied from the start date of the resource. `3` - **After**: the offset before and after reference are both applied from the end date of the resource. **Note:** in a situation with several binary rules, the order of application is: `After`, then `Before`, then `Around`, then `Default`. Each rule can overwrite those previously applied in case they overlap. **Warning**: two offsets of the same mode should never overlap. Resources' start and end dates can be configured through record sections and/or context rules. | ## Child Element: NavigationRule A navigation rule computes the value of a given navigation property for target resources, based on the properties of their owners (source resources and entitlements). These properties are to be provisioned, i.e. written to the managed system. Contrary to [query rules](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/resourcetype#child-element-queryrule), navigation rules assign resources regardless of the attributes of source resources. @@ -166,7 +166,7 @@ A navigation rule is defined by the child element `` of the ` @@ -211,11 +211,11 @@ The `ResourceFromDimension` rule above behaves as if you had created individual - Either `Resource` or `ResourceFromDimension` must be specified, not both - `SingleRole` is required when using `ResourceFromDimension` - The dimension's entity type must match the target entity type of the navigation property -- Do not specify dimension criteria (D0, D1, etc.) when using `ResourceFromDimension` - they are set automatically +- Don't specify dimension criteria (D0, D1, etc.) when using `ResourceFromDimension` - they are set automatically #### TimeOffset -[See more information about time offsets](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/resourcetype#timeoffset-3). +See the [time offset](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/resourcetype#timeoffset-3) section for details. #### Parameterized roles @@ -231,11 +231,11 @@ The `ResourceFromDimension` rule above behaves as if you had created individual | Policy required | **Type:** Int64 **Description:** Identifier of the policy that the rule is part of. | | Property required | **Type:** Int64 **Description:** Identifier of the navigation property to be computed. | | Resource optional | **Type:** Int64 **Description:** Identifier of the resource to be assigned as a value of the impacted navigation property. Said resource must be part of the entity type that the navigation property points to. | -| ResourceFromDimension optional | **Type:** Int64 **Description:** The `ResourceFromDimension` property is a special configuration option for `ResourceNavigationRule` that simulates having as many navigation rules as there are resources in the specified dimension, without actually creating multiple rule entries. **Purpose** When you configure a `ResourceNavigationRule` with `ResourceFromDimension`, the system behaves as if you had created a separate navigation rule for each resource that belongs to the specified dimension. This provides a powerful way to avoid repetitive configuration and maintain consistency across related resources. **Example Scenario** If you have a dimension "Departments" containing 50 department resources, setting `ResourceFromDimension="Departments"` on a single navigation rule is equivalent to creating 50 individual navigation rules, one for each department resource. **Configuration Rules** **Mutually Exclusive Properties** You must choose one approach for defining resources: - Use `Resource` to specify a single, explicit resource - Use `ResourceFromDimension` to dynamically reference all resources in a dimension These two properties cannot be used together on the same navigation rule. **Valid Configuration Examples** ```xml ``` **Required SingleRole Property** When using `ResourceFromDimension`, the `SingleRole` property is mandatory. **Entity Type Compatibility** The dimension specified in `ResourceFromDimension` must have the same entity type as the target entity type of the navigation property. This ensures type safety and consistency. | +| ResourceFromDimension optional | **Type:** Int64 **Description:** The `ResourceFromDimension` property is a special configuration option for `ResourceNavigationRule` that simulates having as many navigation rules as there are resources in the specified dimension, without actually creating multiple rule entries. **Purpose** When you configure a `ResourceNavigationRule` with `ResourceFromDimension`, the system behaves as if you had created a separate navigation rule for each resource that belongs to the specified dimension. This provides a powerful way to avoid repetitive configuration and maintain consistency across related resources. **Example Scenario** If you have a dimension "Departments" containing 50 department resources, setting `ResourceFromDimension="Departments"` on a single navigation rule is equivalent to creating 50 individual navigation rules, one for each department resource. **Configuration Rules** **Mutually Exclusive Properties** You must choose one approach for defining resources: - Use `Resource` to specify a single, explicit resource - Use `ResourceFromDimension` to dynamically reference all resources in a dimension These two properties can't be used together on the same navigation rule. **Valid Configuration Examples** ```xml ``` **Required SingleRole Property** When using `ResourceFromDimension`, the `SingleRole` property is mandatory. **Entity Type Compatibility** The dimension specified in `ResourceFromDimension` must have the same entity type as the target entity type of the navigation property. This ensures type safety and consistency. | | SingleRole optional | **Type:** Int64 **Description:** Identifier of a single role, which users must have to trigger the property computation. | | TimeOffsetAfterReference default value: 0 | **Type:** Int32 **Description:** Time period (in minutes) after the reference end date, which shifts the end of the rule's application. A negative value for the time offset means that the time period is before the reference date. | | TimeOffsetBeforeReference default value: 0 | **Type:** Int32 **Description:** Time period (in minutes) after the reference start date, which shifts the start of the rule's application. A negative value for the time offset means that the time period is before the reference date. | -| TimeOffsetReference default value: 0 | **Type:** TimeOffsetReference **Description:** Offset mode defining which dates to use as references, in order to apply the time offset. The time period for which the rule is applied is adjusted accordingly. `0` - **Default**: the offset inherited from the type rule. `1` - **Around**: the offset before reference is applied from the start date of the resource, and the offset after reference is applied from the end date. `2` - **Before**: the offset before and after reference are both applied from the start date of the resource. `3` - **After**: the offset before and after reference are both applied from the end date of the resource. In a situation with several navigation rules, the order of application is descending (`After`-`Before`-`Around`-`Default`). Thus each time offset is able to overwrite those previously applied in case they overlap, for mono-valued properties. **Warning**: two offsets of the same mode should never overlap for mono-valued properties. Overlapping rules on a multi-valued property do not conflict with each other, Identity Manager stores all computed values. Resources' start and end dates can be configured through record sections and/or context rules. | +| TimeOffsetReference default value: 0 | **Type:** TimeOffsetReference **Description:** Offset mode defining which dates to use as references, to apply the time offset. The time period for which the rule is applied is adjusted accordingly. `0` - **Default**: the offset inherited from the type rule. `1` - **Around**: the offset before reference is applied from the start date of the resource, and the offset after reference is applied from the end date. `2` - **Before**: the offset before and after reference are both applied from the start date of the resource. `3` - **After**: the offset before and after reference are both applied from the end date of the resource. In a situation with several navigation rules, the order of application is descending (`After`-`Before`-`Around`-`Default`). Thus each time offset can overwrite those previously applied in case they overlap, for mono-valued properties. **Warning**: two offsets of the same mode should never overlap for mono-valued properties. Overlapping rules on a multi-valued property don't conflict with each other, Identity Manager stores all computed values. Resources' start and end dates can be configured through record sections and/or context rules. | ## Child Element: QueryRule A query rule computes the value of a given navigation property for target resources, based on the properties of their owners (source resources and entitlements). These properties are to be provisioned, i.e. written to the managed system. Contrary to [navigation rules](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/resourcetype#child-element-navigationrule), query rules assign resources to target resources according to a query via a C# [expression](/docs/identitymanager/current/integration-guide/toolkit/expressions) with conditions, based on the attributes of the source resources. @@ -246,13 +246,13 @@ A query rule is defined by the child element `` of the ` @@ -263,7 +263,7 @@ The following example declares a new rule to compute the parent distinguished na #### TimeOffset -[See more information about time offsets](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/resourcetype#timeoffset-3). +[Learn about time offsets](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/resourcetype#timeoffset-3). ### Properties @@ -271,22 +271,22 @@ The following example declares a new rule to compute the parent distinguished na |Property|Details| |---|---| | Policy required | **Type:** Int64 **Description:** Identifier of the policy that the rule is part of. | -| Property required | **Type:** Int64 **Description:** Identifier of the navigation property to be computed. | -| SourceBinding optional | **Type:** Int64 **Description:** Binding of the property from the source entity type to be compared with the target binding/expression, in order to find a matching resource to be the value of `Property`. | -| SourceExpression optional | **Type:** String **Description:** C# expression to compare with the target binding/expression in order to compute the value of `Property` with the matching resource. [See more details on C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). | +| Property required | **Type:** Int64 **Description:** Identifier of the navigation property to compute. | +| SourceBinding optional | **Type:** Int64 **Description:** Binding of the property from the source entity type to compare with the target binding/expression, finding a matching resource for the `Property` value. | +| SourceExpression optional | **Type:** String **Description:** C# expression to compare with the target binding/expression to compute the value of `Property` with the matching resource. [Learn about C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). | | TargetBinding optional | **Type:** Int64 **Description:** Binding of the property from the entity type pointed by `Property`, which will be the value of `Property` if it matches the source binding/expression. | -| TargetExpression optional | **Type:** String **Description:** C# expression to compare with the source binding/expression in order to compute the value of `Property` with the matching resource. [See more details on C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). **Warning**: it must contain at least one target property, it cannot be a literal expression. | +| TargetExpression optional | **Type:** String **Description:** C# expression to compare with the source binding/expression to compute the value of `Property` with the matching resource. [Learn about C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). **Warning**: it must contain at least one target property; it can't be a literal expression. | | TargetMatchedConfidenceLevel default value: 0 | **Type:** Int32 **Description:** Percentage rate expressing the confidence in the rule according to data quality and sensitivity. Identity Manager considers the rules in descending order of confidence rate, the first matching rule is applied. `0` to `99`: imposes that a resource manager reviews the property computation on the **Resource Reconciliation** page. `100` to `150`: computes the property automatically. | | TimeOffsetAfterReference default value: 0 | **Type:** Int32 **Description:** Time period (in minutes) after the reference end date, which shifts the end of the rule's application. A negative value for the time offset means that the time period is before the reference date. | | TimeOffsetBeforeReference default value: 0 | **Type:** Int32 **Description:** Time period (in minutes) after the reference start date, which shifts the start of the rule's application. A negative value for the time offset means that the time period is before the reference date. | -| TimeOffsetReference default value: 0 | **Type:** TimeOffsetReference **Description:** Offset mode defining which dates to use as references, in order to apply the time offset. The time period for which the rule is applied is adjusted accordingly. `0` - **Default**: the offset inherited from the type rule. `1` - **Around**: the offset before reference is applied from the start date of the resource, and the offset after reference is applied from the end date. `2` - **Before**: the offset before and after reference are both applied from the start date of the resource. `3` - **After**: the offset before and after reference are both applied from the end date of the resource. In a situation with several query rules, the order of application is descending (`After`-`Before`-`Around`-`Default`). Thus each time offset is able to overwrite those previously applied in case they overlap, for mono-valued properties. **Warning**: two offsets of the same mode should never overlap for mono-valued properties. Overlapping rules on a multi-valued property do not conflict with each other, Identity Manager stores all computed values. Resources' start and end dates can be configured through record sections and/or context rules. | +| TimeOffsetReference default value: 0 | **Type:** TimeOffsetReference **Description:** Offset mode defining which dates to use as references, to apply the time offset. The time period for which the rule is applied is adjusted accordingly. `0` - **Default**: the offset inherited from the type rule. `1` - **Around**: the offset before reference is applied from the start date of the resource, and the offset after reference is applied from the end date. `2` - **Before**: the offset before and after reference are both applied from the start date of the resource. `3` - **After**: the offset before and after reference are both applied from the end date of the resource. In a situation with several query rules, the order of application is descending (`After`-`Before`-`Around`-`Default`). Thus each time offset can overwrite those previously applied in case they overlap, for mono-valued properties. **Warning**: two offsets of the same mode should never overlap for mono-valued properties. Overlapping rules on a multi-valued property don't conflict with each other, Identity Manager stores all computed values. Resources' start and end dates can be configured through record sections and/or context rules. | ## Child Element: ScalarRule A scalar rule computes the value of a given scalar property for target resources, based on the properties of their owners (source resources and entitlements). These properties are to be provisioned, i.e. written to the managed system. A scalar rule is defined by the child element `` of the `` element. -[See more information about scalar rules' configuration guidelines](/docs/identitymanager/current/user-guide/set-up/provisioning-rule-creation/scalar-property-computation#guidelines). +See [scalar rules' configuration guidelines](/docs/identitymanager/current/user-guide/set-up/provisioning-rule-creation/scalar-property-computation#guidelines) for details. ### Examples #### Computation based on other properties @@ -332,9 +332,9 @@ The `Binding` attribute complies with the [binding expression syntax](/docs/iden #### IsMapped :::info -Consider a system that we want to connect to Identity Manager (let's call it `SYST`) using a `title` property. Consider also that `SYST` needs to be provisioned with the value of `title`, but does not allow any other system to retrieve said value. +Consider a system that needs to connect to Identity Manager (let's call it `SYST`) using a `title` property. Consider also that `SYST` needs to be provisioned with the value of `title`, but doesn't allow any other system to retrieve said value. -In this case, we set `IsMapped` to false so that Identity Manager sends the adequate provisioning order when needed, and then is able to change the [provisioning state](/docs/identitymanager/current/user-guide/administrate/provisioning#provisioning-states) to `Verified` without [synchronization](/docs/identitymanager/current/user-guide/set-up/synchronization). +In this case, set `IsMapped` to false so that Identity Manager sends the adequate provisioning order when needed, and then can change the [provisioning state](/docs/identitymanager/current/user-guide/administrate/provisioning#provisioning-states) to `Verified` without [synchronization](/docs/identitymanager/current/user-guide/set-up/synchronization). ::: The following example computes users' title in a given managed system, based on Identity Manager's `PersonalTitle` property without ever retrieving the value: @@ -373,7 +373,7 @@ The following example impacts the property for the activation of nominative AD a If the time period of property computation exceeds the limits of the period of resource type assignment, then the period of resource type assignment is extended accordingly. ::: -Note that the rules are applied in a specific order according to their offset reference: `After`, `Before`, `Around` and `Default`. Each rule overwrites pre-existing values. Thus in case of overlapping rules, `Default`-offset rules overwrite the values of `Around`-offset rules, which overwrite the values of `Before`-offset rules, which overwrite the values of `After`-offset rules. We could have the following: +The rules are applied in a specific order according to their offset reference: `After`, `Before`, `Around`, and `Default`. Each rule overwrites pre-existing values. Thus in case of overlapping rules, `Default`-offset rules overwrite the values of `Around`-offset rules, which overwrite the values of `Before`-offset rules, which overwrite the values of `After`-offset rules. The following is an example: ![Schema - Overlapping Offsets](/images/identitymanager/datamodel_scalarrule_timeoffsetoverlap.webp) @@ -383,15 +383,15 @@ Note that the rules are applied in a specific order according to their offset re |Property|Details| |---|---| | Binding optional | **Type:** Int64 **Description:** Defines the binding expression. | -| ComparisonType default value: 0 | **Type:** ComparisonType **Description:** Defines the comparison type for the computed value, when Identity Manager retrieves it from the managed system during synchronization, and compares it to the value stored in Identity Manager's database. `0` - **CaseSensitive**: compares words exactly as they are. `1` - **IgnoreCase**: ignores the difference between upper and lower case. `2` - **IgnoreDiacritics**: considers all letters with diacritics (é, à, ç...) to be equivalent to their base letters (e, a, c...). `3` - **Simplified**: ignores diacritics, case and characters which are not letters. `4` - **Approximate**: does the same as `Simplified` but also ignores some spelling mistakes. Some letters are considered equivalent (Z and S, Y and I, W and V, K and C, SS and C). All H can be missing. A T, D or S can be missing at the very end. Finally, it ignores all duplicate letters (other than SS). `5` - **Trim**: does the same as `CaseSensitive` but ignores all leading and trailing white-space characters. There is no comparison for unmapped properties (`IsMapped` set to `false`). | -| Expression optional | **Type:** String **Description:** Expression used to compute the target property specified in `Property`. [See more details on C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). **Note:** for C# expressions, Identity Manager provides an implicit variable called "assignment" that contains basic information about the linked assigned resource type, i.e. StartDate, EndDate and ParametersValues. | -| IsMapped default value: true | **Type:** Boolean **Description:** `true` to use the scalar rule's computation to both provision the managed system and synchronize the property back to Identity Manager, thus both create and update. Otherwise, the scalar rule's computation is used only to provision the managed system and the property will be ignored during synchronization, thus create only. This way the property can never be displayed as non-conforming. `IsMapped` is usually set to false in order to adapt the configuration to the constraints of the managed system, when Identity Manager does not retrieve and/or update the property value. | +| ComparisonType default value: 0 | **Type:** ComparisonType **Description:** Defines the comparison type for the computed value, when Identity Manager retrieves it from the managed system during synchronization, and compares it to the value stored in Identity Manager's database. `0` - **CaseSensitive**: compares words exactly as they are. `1` - **IgnoreCase**: ignores the difference between upper and lower case. `2` - **IgnoreDiacritics**: considers all letters with diacritics (é, à, ç...) to be equivalent to their base letters (e, a, c...). `3` - **Simplified**: ignores diacritics, case, and characters which aren't letters. `4` - **Approximate**: does the same as `Simplified` but also ignores some spelling mistakes. Some letters are considered equivalent (Z and S, Y and I, W and V, K and C, SS and C). All H can be missing. A T, D, or S can be missing at the very end. Finally, it ignores all duplicate letters (other than SS). `5` - **Trim**: does the same as `CaseSensitive` but ignores all leading and trailing white-space characters. There is no comparison for unmapped properties (`IsMapped` set to `false`). | +| Expression optional | **Type:** String **Description:** Expression used to compute the target property specified in `Property`. See [C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions) for details. **Note:** for C# expressions, Identity Manager provides an implicit variable called "assignment" that contains basic information about the linked assigned resource type, i.e. StartDate, EndDate, and ParametersValues. | +| IsMapped default value: true | **Type:** Boolean **Description:** `true` to use the scalar rule's computation to both provision the managed system and synchronize the property back to Identity Manager, thus both create and update. Otherwise, the scalar rule's computation is used only to provision the managed system and the property will be ignored during synchronization, thus create only. This way the property can never be displayed as non-conforming. `IsMapped` is usually set to false to adapt the configuration to the constraints of the managed system, when Identity Manager doesn't retrieve and/or update the property value. | | Policy required | **Type:** Int64 **Description:** Identifier of the policy that the rule is part of. | | Property required | **Type:** Int64 **Description:** Identifier of the scalar property to be computed. | | SingleRole optional | **Type:** Int64 **Description:** Identifier of a single role that users must have to trigger the property computation. **Warning**: scalar rules must not be dependent on dimensions or role as far as possible as, according to Identity Manager, a good rights policy must be based on group membership and not on mono-valued properties. | | TimeOffsetAfterReference default value: 0 | **Type:** Int32 **Description:** Time period (in minutes) after the reference end date, which shifts the end of the rule's application. A negative value for the time offset means that the time period is before the reference date. | | TimeOffsetBeforeReference default value: 0 | **Type:** Int32 **Description:** Time period (in minutes) after the reference start date, which shifts the start of the rule's application. A negative value for the time offset means that the time period is before the reference date. | -| TimeOffsetReference default value: 0 | **Type:** TimeOffsetReference **Description:** Offset mode defining which dates to use as references, in order to apply the time offset. The time period for which the rule is applied is adjusted accordingly. `0` - **Default**: the offset inherited from the type rule. `1` - **Around**: the offset before reference is applied from the start date of the resource, and the offset after reference is applied from the end date. `2` - **Before**: the offset before and after reference are both applied from the start date of the resource. `3` - **After**: the offset before and after reference are both applied from the end date of the resource. **Note:** in a situation with several scalar rules, the order of application is: `After`, then `Before`, then `Around`, then `Default`. Each rule is able to overwrite those previously applied in case they overlap. **Warning**: two offsets of the same mode should never overlap. Resources' start and end dates can be configured through record sections and/or context rules. | +| TimeOffsetReference default value: 0 | **Type:** TimeOffsetReference **Description:** Offset mode defining which dates to use as references, to apply the time offset. The time period for which the rule is applied is adjusted accordingly. `0` - **Default**: the offset inherited from the type rule. `1` - **Around**: the offset before reference is applied from the start date of the resource, and the offset after reference is applied from the end date. `2` - **Before**: the offset before and after reference are both applied from the start date of the resource. `3` - **After**: the offset before and after reference are both applied from the end date of the resource. **Note:** in a situation with several scalar rules, the order of application is: `After`, then `Before`, then `Around`, then `Default`. Each rule can overwrite those previously applied in case they overlap. **Warning**: two offsets of the same mode should never overlap. Resources' start and end dates can be configured through record sections and/or context rules. | ## Child Element: TypeRule A resource type rule assigns resources to given users if they match specific criteria. These resources are to be provisioned, i.e. written to the managed system. @@ -430,7 +430,7 @@ The following rule will assign an `App1_Standard_Account` resource to all `User` ##### Without any criterion -`Di` and `SingleRole` conditions are not mandatory. A type rule with no condition entails the creation of an AssignedResourceType, and hence of a target resource (from the target entity type), for every source resource (from the source entity type). +`Di` and `SingleRole` conditions aren't mandatory. A type rule with no condition entails the creation of an AssignedResourceType, and hence of a target resource (from the target entity type), for every source resource (from the source entity type). The following example declares a new rule to give the resource type "AD_Entry_NominativeUser" to all users. @@ -443,7 +443,7 @@ The following example declares a new rule to give the resource type "AD_Entry_No ##### TimeOffset -[See more information about time offsets](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/resourcetype#timeoffset-3). +See the [time offset](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/resourcetype#timeoffset-3) section for details. ### Properties @@ -457,5 +457,5 @@ The following example declares a new rule to give the resource type "AD_Entry_No | SingleRole optional | **Type:** Int64 **Description:** Identifier of a single role, which users must have to trigger the resource type assignment. | | TimeOffsetAfterReference default value: 0 | **Type:** Int32 **Description:** Time period (in minutes) after the reference end date, which shifts the end of the rule's application. A negative value for the time offset means that the time period is before the reference date. | | TimeOffsetBeforeReference default value: 0 | **Type:** Int32 **Description:** Time period (in minutes) after the reference start date, which shifts the start of the rule's application. A negative value for the time offset means that the time period is before the reference date. | -| TimeOffsetReference default value: 0 | **Type:** TimeOffsetReference **Description:** Offset mode defining which dates to use as references, in order to apply the time offset. The time period for which the rule is applied is adjusted accordingly. `0` - **Default**: no offset. `1` - **Around**: the offset before reference is applied from the start date of the resource, and the offset after reference is applied from the end date. `2` - **Before**: the offset before and after reference are both applied from the start date of the resource. `3` - **After**: the offset before and after reference are both applied from the end date of the resource. In a situation with several resource type rules, the order of application is descending (`After`-`Before`-`Around`-`Default`). Thus each time offset is able to overwrite those previously applied in case they overlap. **Warning**: two offsets of the same mode should never overlap. Resources' start and end dates can be configured through record sections and/or context rules. | +| TimeOffsetReference default value: 0 | **Type:** TimeOffsetReference **Description:** Offset mode defining which dates to use as references, to apply the time offset. The time period for which the rule is applied is adjusted accordingly. `0` - **Default**: no offset. `1` - **Around**: the offset before reference is applied from the start date of the resource, and the offset after reference is applied from the end date. `2` - **Before**: the offset before and after reference are both applied from the start date of the resource. `3` - **After**: the offset before and after reference are both applied from the end date of the resource. In a situation with several resource type rules, the order of application is descending (`After`-`Before`-`Around`-`Default`). Thus each time offset can overwrite those previously applied in case they overlap. **Warning**: two offsets of the same mode should never overlap. Resources' start and end dates can be configured through record sections and/or context rules. | | Type default value: 0 | **Type:** RuleType **Description:** Represents the type of the rule. `0` - **Required**: the resource type is automatically assigned to users matching the criteria. `1` - **RequestedAutomatically**: the resource type is listed in the permission basket of new workers. These assignments can still be modified. For existing workers, the rule's type is `Suggested`. `2` - **Suggested**: the resource type is listed among suggested permissions in the permission basket of users matching the criteria during an entitlement request. Suggested assignments must be selected manually to be requested, and will go through the validation process. | diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/rolemapping.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/rolemapping.md index bd9767245b..9cef37778c 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/rolemapping.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/rolemapping.md @@ -5,7 +5,7 @@ sidebar_position: 15 --- Defines a naming rule to create a single role in a specific category based on a property. -A navigation rule will also be created by the naming rule, giving the property to the target user when the created single role is assigned to this user. +The naming rule also creates a navigation rule that gives the property to the target user when the single role is assigned. ## Examples @@ -14,10 +14,10 @@ A navigation rule will also be created by the naming rule, giving the property t The following example uses `WhereExpression` to condition the application of the rule. :::info -NETWRIX recommends using this property only when the properties from the rule items do not suffice. +NETWRIX recommends using this property only when the properties from the rule items don't suffice. ::: -Here the naming convention says that we should create a single role for each group (`memberOf` value) whose `dn` starts with `SG_` and whose dn's second part (between two `_`) is made of three characters. +Here, according to the naming convention, create a single role for each group (`memberOf` value) whose `dn` starts with `SG_` and whose dn's second part (between two `_`) is made of three characters. ```xml @@ -33,30 +33,30 @@ Here the naming convention says that we should create a single role for each gro |Property|Details| |---|---| | ApprovalRequired default value: false | **Type:** Boolean **Description:** Indicates that the generated role must be approved before being used by a policy. | -| ApprovalWorkflowType default value: None | **Type:** ProvisioningPolicyApprovalWorkflow **Description:** Indicates the number of validation to give to a manual role (from 0 to 3 inclusive). The value 4 is used when a manual assignment cannot be performed. | +| ApprovalWorkflowType default value: None | **Type:** ProvisioningPolicyApprovalWorkflow **Description:** Indicates the number of validation to give to a manual role (from 0 to 3 inclusive). The value 4 is used when a manual assignment can't be performed. | | Category optional | **Type:** Int64 **Description:** Identifier of the category. | | CategoryDisplayNameBinding optional | **Type:** Int64 **Description:** Defines the binding used to compute the category display name. | -| CategoryDisplayNameExpression optional | **Type:** String **Description:** References the C# or literal expression used to compute the category display name. [See more details on C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). | +| CategoryDisplayNameExpression optional | **Type:** String **Description:** References the C# or literal expression used to compute the category display name. See [C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions) for details. | | CategoryIdentifierBinding optional | **Type:** Int64 **Description:** Binding used to compute the category identifier. | -| CategoryIdentifierExpression optional | **Type:** String **Description:** C# or literal expression used to compute the category identifier. [See more details on C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). | +| CategoryIdentifierExpression optional | **Type:** String **Description:** C# or literal expression used to compute the category identifier. See [C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions) for details. | | CommentActivationOnApproveInReview default value: Inherited | **Type:** CommentActivationWithInherited **Description:** Indicates if a comment is enabled when reviewing a request of the role and deciding to approve it. `0` - Disabled `1` - Optional `2` - Required `3` - Inherited: comment activation in the associated policy. | | CommentActivationOnDeclineInReview default value: Inherited | **Type:** CommentActivationWithInherited **Description:** Indicates if a comment is enabled when reviewing a request of the role and deciding to refuse it. `0` - Disabled `1` - Optional `2` - Required `3` - Inherited: comment activation in the associated policy. | | CommentActivationOnDeleteGapInReconciliation default value: Inherited | **Type:** CommentActivationWithInherited **Description:** Indicates if a comment is enabled when reviewing a non-conforming assignment of the role and deciding to delete it. `0` - Disabled `1` - Optional `2` - Required `3` - Inherited: comment activation in the associated policy. | | CommentActivationOnKeepGapInReconciliation default value: Inherited | **Type:** CommentActivationWithInherited **Description:** Indicates if a comment is enabled when reviewing a non-conforming assignment of the role and deciding to keep it. `0` - Disabled `1` - Optional `2` - Required `3` - Inherited: comment activation in the associated policy. | | DisplayNameBinding optional | **Type:** Int64 **Description:** Defines the binding used to compute the role display name. | -| DisplayNameExpression optional | **Type:** String **Description:** References the C# or literal expression used to compute the role display name. [See more details on C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). | +| DisplayNameExpression optional | **Type:** String **Description:** References the C# or literal expression used to compute the role display name. See [C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions) for details. | | HideOnSimplifiedView default value: false | **Type:** Boolean **Description:** `true` to hide this role in the basket simplified view. This flag is applied only on automatic assignments. | | Identifier required | **Type:** String **Description:** Identifier of the role mapping. | | IdentifierBinding optional | **Type:** Int64 **Description:** Binding used to compute the role identifier. | -| IdentifierExpression optional | **Type:** String **Description:** C# or literal expression used to compute the role identifier. [See more details on C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). | +| IdentifierExpression optional | **Type:** String **Description:** C# or literal expression used to compute the role identifier. See [C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions) for details. | | ImplicitApproval default value: 0 | **Type:** Byte **Description:** Indicates if the validation steps of the single role can be skipped. `0` - Inherited: implicit approval value in the associated policy. `1` - Explicit: all the workflow steps must be approved. `2` - Implicit: the workflow steps can be skipped if the requester has enough permissions. | | ParentCategoryIdentifierBinding optional | **Type:** Int64 **Description:** Defines the binding used to compute the parent category. | -| ParentCategoryIdentifierExpression optional | **Type:** String **Description:** References the C# or literal expression used to compute the parent category. [See more details on C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). | +| ParentCategoryIdentifierExpression optional | **Type:** String **Description:** References the C# or literal expression used to compute the parent category. See [C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions) for details. | | Policy required | **Type:** Int64 **Description:** Identifier of the policy that the rule is part of. | | Property required | **Type:** Int64 **Description:** Property on which the naming rule will be applied. | | ResourceType required | **Type:** Int64 **Description:** Resource type on which the naming rule will be applied. | | RolePolicy optional | **Type:** Int64 **Description:** Identifier of the policy used for the roles created by the naming rule. | -| WhereExpression optional | **Type:** String **Description:** C# expression returning a boolean, used to condition the application of the naming convention. [See more details on C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). | +| WhereExpression optional | **Type:** String **Description:** C# expression returning a boolean, used to condition the application of the naming convention. See [C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions) for details. | ## Child Element: Rule Represent the sets of conditions which will determine the enforcement of the naming rule. diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/singlerole.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/singlerole.md index 751a126622..1cbccfea89 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/singlerole.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/provisioning/singlerole.md @@ -4,12 +4,12 @@ description: "" sidebar_position: 16 --- -A single role is a way to represent an entitlement that is to be assigned to an identity. It brings a layer of abstraction through a user-friendly name, close to the business view. +A single role is a way to represent an entitlement assigned to an identity. It brings a layer of abstraction through a user-friendly name that reflects the business view. -Roles can be used to: -- grant accesses of various types and levels; -- restrict access to sensitive information assets, by grouping entitlements in a form that is meaningful from a business point of view; -- grant the minimum privileges required by an individual to perform his/her job. +Use roles to: +- Grant accesses of various types and levels. +- Restrict access to sensitive information assets by grouping entitlements in business-meaningful forms. +- Grant the minimum privileges an individual needs to perform their job. Roles can be requested manually, or they can be configured to be assigned automatically via [single role rules](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/provisioning/singlerolerule) depending on identities' attributes. @@ -32,7 +32,7 @@ The following example declares a new single role in the default policy; in the c |Property|Details| |---|---| -| ApprovalWorkflowType default value: 0 | **Type:** ProvisioningPolicyApprovalWorkflow **Description:** Number of validations required to assign manually the single role (from `None` to `Three`). The value `ManualAssignmentNotAllowed` is used when a manual assignment cannot be performed. | +| ApprovalWorkflowType default value: 0 | **Type:** ProvisioningPolicyApprovalWorkflow **Description:** Number of validations required to assign manually the single role (from `None` to `Three`). The value `ManualAssignmentNotAllowed` is used when a manual assignment can't be performed. | | Category optional | **Type:** Int64 **Description:** Identifier of the category that the role is part of. | | CommentActivationOnApproveInReview default value: Inherited | **Type:** CommentActivationWithInherited **Description:** Indicates if a comment is enabled when reviewing a request of the role and deciding to approve it. `0` - Disabled. `1` - Optional. `2` - Required. `3` - Inherited: comment activation in the associated policy. | | CommentActivationOnDeclineInReview default value: Inherited | **Type:** CommentActivationWithInherited **Description:** Indicates if a comment is enabled when reviewing a request of the role and deciding to refuse it. `0` - Disabled. `1` - Optional. `2` - Required. `3` - Inherited: comment activation in the associated policy. | @@ -42,14 +42,14 @@ The following example declares a new single role in the default policy; in the c | Description_L1 optional | **Type:** String **Description:** Detailed description of the single role in language 1 (up to 16). | | DisplayName_L1 required | **Type:** String **Description:** Display name of the single role in language 1 (up to 16). | | EntityType required | **Type:** Int64 **Description:** Identifier of the entity type whose resources can receive the single role. | -| GracePeriod optional | **Type:** Int32 **Description:** Duration (in minutes) for which a lost automatic single role is prolonged. The grace period is only applied if the loss of the entitlement is due to a change in the rules (rule deletion or criteria changes). A review will be required to validate or decline the entitlement prolongation. Inferred entitlements won't be lost unless the end of the grace period is reached or the prolongation is declined. If it is not defined, the value is inherited from the policy. | +| GracePeriod optional | **Type:** Int32 **Description:** Duration (in minutes) for which a lost automatic single role is prolonged. The grace period is only applied if the loss of the entitlement is due to a change in the rules (rule deletion or criteria changes). A review will be required to validate or decline the entitlement prolongation. Inferred entitlements won't be lost unless the end of the grace period is reached or the prolongation is declined. If it isn't defined, the value is inherited from the policy. | | HideOnSimplifiedView default value: false | **Type:** Boolean **Description:** `true` to show the role in a user's basket only in advanced view and not simplified view. This flag is applied only on automatic assignments. | | Identifier required | **Type:** String **Description:** Identifier of the single role. | | ImplicitApproval default value: 0 | **Type:** Byte **Description:** Indicates whether the validation steps of the single role can be skipped. `0` - Inherited: implicit approval value from the associated policy. `1` - Explicit: all the workflow steps must be approved. `2` - Implicit: the workflow steps can be skipped if the requester has enough permissions. | -| ManualAssignmentEndDateLockedToContextMode default value: Inherited | **Type:** RoleManualAssignmentEndDateLockedToContextMode **Description:** Inherited (default value): Use the policy's ManualAssignmentEndDateLockedToContextMode value. ExplicitNotContextBoundByDefault: The manual assignments' end date can be specified by the user or can be locked to match the end date specified by context rules. By default, in the UI, it is not automatically locked. ExplicitContextBoundByDefault: The manual assignments' end date can be specified by the user or can be locked to match the end date specified by context rules. By default, in the UI, it is automatically locked. Never: The manual assignments' end date needs to be specified. Always: The manual assignments' end date cannot be modified. They are computed by the policy to match the end date specified by context rules. | -| MaxDuration optional | **Type:** Int32 **Description:** Duration (in minutes) after which the role will be automatically revoked, if no earlier end date is specified. It impacts only the roles which are manually assigned after the maximum duration is set. Pre-assigned roles are not impacted. If no duration is set on the role, the `MaxDuration` of the associated policy is applied. If the `MaxDuration` is set to 0 on the role, it prevents the associated policy from applying its `MaxDuration` to it. | +| ManualAssignmentEndDateLockedToContextMode default value: Inherited | **Type:** RoleManualAssignmentEndDateLockedToContextMode **Description:** Inherited (default value): Use the policy's ManualAssignmentEndDateLockedToContextMode value. ExplicitNotContextBoundByDefault: The manual assignments' end date can be specified by the user or can be locked to match the end date specified by context rules. By default, in the UI, it isn't automatically locked. ExplicitContextBoundByDefault: The manual assignments' end date can be specified by the user or can be locked to match the end date specified by context rules. By default, in the UI, it is automatically locked. Never: The manual assignments' end date needs to be specified. Always: The manual assignments' end date can't be modified. They are computed by the policy to match the end date specified by context rules. | +| MaxDuration optional | **Type:** Int32 **Description:** Duration (in minutes) after which the role will be automatically revoked, if no earlier end date is specified. It impacts only the roles which are manually assigned after the maximum duration is set. Pre-assigned roles aren't impacted. If no duration is set on the role, the `MaxDuration` of the associated policy is applied. If the `MaxDuration` is set to 0 on the role, it prevents the associated policy from applying its `MaxDuration` to it. | | Policy required | **Type:** Int64 **Description:** Identifier of the policy in which the role exists. | | ProlongationWithoutApproval default value: 0 | **Type:** ProlongationWithoutApproval **Description:** Indicates whether the role can be extended without any validation. `0` - Inherited: gets the value from the policy. `1` - Enabled. `2` - Disabled. | | R0 default value: false | **Type:** Boolean **Description:** `true` to set the dimension 0 (up to 3V following the [base32hex convention](/docs/identitymanager/current/integration-guide/toolkit/parameter-names)) as a required parameter when assigning the role. | | State default value: Manual | **Type:** RoleState **Description:** Mark that differentiates the roles analyzed in the role mining process. `0` - Manual: the role was created manually. `1` - Generated: the role was generated by a role mapping rule. | -| Tags optional | **Type:** String **Description:** Label(s) that can later be used to filter the target roles of access certification campaigns. The tag separator is `¤`. | +| Tags optional | **Type:** String **Description:** Labels that can later be used to filter the target roles of access certification campaigns. The tag separator is `¤`. | diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/reporting/reportquery.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/reporting/reportquery.md index 7efa4488a1..42c27c83c3 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/reporting/reportquery.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/reporting/reportquery.md @@ -4,7 +4,7 @@ description: "" sidebar_position: 1 --- -Allows the user to define queries to generate a report in a CSV file. When creating a new ReportQuery it is recommended to also create the linked [MenuItem](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/user-interface/menuitem). +Allows the user to define queries to generate a report in a CSV file. When creating a new ReportQuery, consider also creating the linked [MenuItem](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/user-interface/menuitem). ## Examples diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/resources/resource.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/resources/resource.md index 8815145018..66cc255c6c 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/resources/resource.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/resources/resource.md @@ -31,7 +31,7 @@ The two new resources are inserted in the database using the `` tag. They are assigned the ids `300` and `301`, they are positive integers (since User type resources are resource-identity) and not yet used in the **UR_Resource** table. -The `User` resource properties (FirstName, LastName and Manager) are matched to a **UR_Resource** table column, such as `C4`, `C5` or `I40` according to their data column index, in the above **Entity Type** definition. +The `User` resource properties (FirstName, LastName, and Manager) are matched to a **UR_Resource** table column, such as `C4`, `C5` or `I40` according to their data column index, in the above **Entity Type** definition. * FirstName: index 4 => column C4 * LastName: index 5 => column C5 @@ -54,5 +54,5 @@ Most encountered use cases in real life is populating very tiny datasets like em | C0 optional | **Type:** String **Description:** A column of storage. Going from 0 to 127. | | Dirty default value: false | **Type:** Boolean **Description:** Flag set by the Usercube-Set-RecentlyModifiedFlag task. | | DisplayName_L1 optional | **Type:** String **Description:** Display name of the resource in language 1 (up to 16). | -| I40 optional | **Type:** Int64 **Description:** This columns are used to store the id of an linked entity. When an entity type has a mono-valued association we usually use this columns to store the information. By default there are 10 columns for the storage of the mono-valued associations. | +| I40 optional | **Type:** Int64 **Description:** This columns are used to store the id of an linked entity. When an entity type has a mono-valued association, this column is usually used to store the information. By default there are 10 columns for the storage of the mono-valued associations. | | Type required | **Type:** Int64 **Description:** The type of the resource. References the internal id of an EntityType. | diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/displayentitytype.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/displayentitytype.md index 398a43de47..7314394bb4 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/displayentitytype.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/displayentitytype.md @@ -33,7 +33,7 @@ By default, the entity type with the highest priority is selected first. The end ![Change Selection](/images/identitymanager/ui_displaypriorities_changeselection_v521beta.webp) -Priorities are integer values, positive or negative. The most important priority is assigned to the lowest value. +Priorities are integer values, positive, or negative. The most important priority is assigned to the lowest value. Entity Types with the same priority are sorted by `Identifier`, in the alphabetical order, where relevant. @@ -87,13 +87,13 @@ But the order in which "Workflow for Directory_User" and "Workflow for Directory The `AddedMinutes` property on display properties allows adding or subtracting minutes from `DateTime` fields for timezone adjustments or display purposes. -**Important:** `AddedMinutes` is only applicable to properties of type `DateTime`. It is not compatible with properties of type `DateOnly`. +**Important:** `AddedMinutes` is only applicable to properties of type `DateTime`. It isn't compatible with properties of type `DateOnly`. -When a property uses the `DateOnly` type, any `AddedMinutes` configuration will be ignored because date-only fields do not have a time component to adjust. +When a property uses the `DateOnly` type, any `AddedMinutes` configuration will be ignored because date-only fields don't have a time component to adjust. **Behavior during configuration import/export:** -- **On Import:** If `AddedMinutes` is specified for a `DateOnly` property, the setting will be ignored and a warning will be displayed indicating that it is not applicable to Date Only properties. +- **On Import:** If `AddedMinutes` is specified for a `DateOnly` property, the setting will be ignored and a warning will be displayed indicating that it isn't applicable to Date Only properties. - **On Export:** If `AddedMinutes` exists on a `DateOnly` property, it will be removed from the exported configuration and a warning will notify you of the removal. @@ -107,9 +107,9 @@ When a property uses the `DateOnly` type, any `AddedMinutes` configuration will | HideRoles default value: false | **Type:** Boolean **Description:** `true` to skip the **Access Permissions** step (the one containing the roles) in the default forms for this entity type. | | IconCode optional | **Type:** String **Description:** Defines the icode code ("People", "MapPin", "Suitcase"...). | | IsHierarchical default value: false | **Type:** Boolean **Description:** Is hierarchical entity type. | -| MinSearchLength optional | **Type:** Int32 **Description:** Defines the minimum number of characters from which the search in the auto complete picker starts - 4 if it is not defined (the AutocompleteBinding must be defined). | +| MinSearchLength optional | **Type:** Int32 **Description:** Defines the minimum number of characters from which the search in the auto complete picker starts - 4 if it isn't defined (the AutocompleteBinding must be defined). | | PluralDisplayName_L1 optional | **Type:** String **Description:** Display name of the entity type in plural in language 1 (up to 16). | -| Priority default value: 2147483647 | **Type:** Int32 **Description:** Sets the display priority of the Entity Type in the administration screens dropdown and the dashboard. A priority is an integer value, positive or negative. The highest priority is assigned to the lowest number. See the Priority section above. | +| Priority default value: 2147483647 | **Type:** Int32 **Description:** Sets the display priority of the Entity Type in the administration screens dropdown and the dashboard. A priority is an integer value, positive, or negative. The highest priority is assigned to the lowest number. See the Priority section above. | ## Child Element: Property Entity referencing the Entity properties (with which it share the same ID) that can be displayed in the Identity Manager interface. @@ -129,7 +129,7 @@ Entity referencing the Entity properties (with which it share the same ID) that | IsHidden default value: false | **Type:** Boolean **Description:** Property is hidden. | | IsReadOnly default value: false | **Type:** Boolean **Description:** Property is readOnly. | | IsRequired default value: false | **Type:** Boolean **Description:** Property is required. | -| MinSearchLength optional | **Type:** Int32 **Description:** Defines the minimum number of characters from which the search in the auto complete picker starts - 4 if it is not defined (the input type of the display property must be a picker and the AutocompleteBinding must be defined). | +| MinSearchLength optional | **Type:** Int32 **Description:** Defines the minimum number of characters from which the search in the auto complete picker starts - 4 if it isn't defined (the input type of the display property must be a picker and the AutocompleteBinding must be defined). | | NavigationBinding optional | **Type:** Int64 **Description:** Defines the binding of the resource on which the user will be redirected when he clicks on an element of a BasicCollection. | | OutputType default value: Auto | **Type:** Enumeration **Description:** Identifier of the output type. | | PlaceHolderText_L1 optional | **Type:** String **Description:** Property place holder text. | diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/displaypropertygroup.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/displaypropertygroup.md index c1269f1893..34fa98cb88 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/displaypropertygroup.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/displaypropertygroup.md @@ -31,7 +31,7 @@ Knowing that we have the following properties: ![Display Property Group - Example](/images/identitymanager/displaypropertygroup_example_v603.webp) :::info -Any property without a value is not displayed. +Any property without a value isn't displayed. ::: diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/displaytable.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/displaytable.md index 95c23fbaf2..878ddce045 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/displaytable.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/displaytable.md @@ -6,7 +6,7 @@ sidebar_position: 4 A table displays a collections of entity type data grouped into rows. -[Read more about how to customize display tables](/docs/identitymanager/current/integration-guide/ui/how-tos/custom-display-table). +[Customize display tables](/docs/identitymanager/current/integration-guide/ui/how-tos/custom-display-table). ## Examples @@ -83,13 +83,13 @@ Contains all the display table columns. |Property|Details| |---|---| -| AddedMinutes optional | **Type:** Int32 **Description:** Add minutes to the date field with this property. If the value is not defined, the default value is the one defined for the associated display entity property. | +| AddedMinutes optional | **Type:** Int32 **Description:** Add minutes to the date field with this property. If the value isn't defined, the default value is the one defined for the associated display entity property. | | CanBeFiltered default value: false | **Type:** Boolean **Description:** Can filter the column data. | | ColumnSize default value: 1 | **Type:** Int32 **Description:** Defines the column size. | | DefaultSortPriority optional | **Type:** Int32 **Description:** Defines the default sort priority. | | DisplayBinding optional | **Type:** Int64 **Description:** Represents the linked binding path to a scalar property. | | DisplayName_L1 optional | **Type:** String **Description:** Display name of the column in language 1 (up to 16). | -| IsDisplayInDropDownList default value: false | **Type:** Boolean **Description:** Is a drop down list column. | +| IsDisplayInDropDownList default value: false | **Type:** Boolean **Description:** Is a dropdown list column. | | IsDisplayInSummaryView default value: false | **Type:** Boolean **Description:** Is a summary view column. | | IsResizable default value: false | **Type:** Boolean **Description:** Is resizable column. | | IsSortable default value: false | **Type:** Boolean **Description:** Is sortable column. | diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/form.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/form.md index d63e0d48a2..e88c9f442b 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/form.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/form.md @@ -34,7 +34,7 @@ The following example shows a form called `Directory_UserRecord_View` that invol #### Hide the "Access Permissions" tab -When `HideRoles` is set to `true`, then the **Access Permissions** tab is not accessible. +When `HideRoles` is set to `true`, then the **Access Permissions** tab isn't accessible. ![Access Permissions](/images/identitymanager/Form_hideRoles_V603.webp) @@ -72,7 +72,7 @@ When `WorkflowRequestType` is set to `Helpdesk`, then the finalization step look | MainPropertyLabel_L1 optional | **Type:** String **Description:** Defines the main property label text. | | Menu optional | **Type:** Int64 **Description:** Defines the linked menu item. | | RecordEndProperty optional | **Type:** Int64 **Description:** Defines the workflow end date property. If not specified, the property 'EndDate' of the record entity type is considered as RecordEndProperty. | -| RecordFilter default value: CurrentAndFuture | **Type:** RecordFilter **Description:** Defines the record display option. `0` - Current: shows current positions. `1` - CurrentAndFuture: shows current and future positions. Recommended. `2` - All: shows past, present and future positions. Not recommended for clarity issues. | +| RecordFilter default value: CurrentAndFuture | **Type:** RecordFilter **Description:** Defines the record display option. `0` - Current: shows current positions. `1` - CurrentAndFuture: shows current and future positions. Recommended. `2` - All: shows past, present, and future positions. Not recommended for clarity issues. | | RecordProperty optional | **Type:** Int64 **Description:** Defines the workflow record property. | | RecordSortProperty optional | **Type:** Int64 **Description:** Defines the workflow sort property. | | RecordStartProperty optional | **Type:** Int64 **Description:** Defines the workflow start date property. If not specified, the property 'StartDate' of the record entity type is considered as RecordStartProperty. | @@ -82,7 +82,7 @@ When `WorkflowRequestType` is set to `Helpdesk`, then the finalization step look | WorkflowRequestType default value: 0 | **Type:** WorkflowRequestType **Description:** Type of the request of the related workflow. `0` - None. `1` - Self. `2` - Helpdesk. `3` - Administration. | ## Child Element: Control -A form control is an input field to be filled by a user. Controls can be inserted in other controls in order to display the form fields in a structured way. +A form control is an input field to be filled by a user. Controls can be inserted in other controls to display the form fields in a structured way. ### Examples @@ -114,10 +114,10 @@ In this example is a tree control which defines the relationships between a work |Property|Details| |---|---| -| AddedMinutes optional | **Type:** Int32 **Description:** Add minutes to the date field with this property. If the value is not defined, the default value is the one defined for the associated display entity property. | +| AddedMinutes optional | **Type:** Int32 **Description:** Add minutes to the date field with this property. If the value isn't defined, the default value is the one defined for the associated display entity property. | | Binding optional | **Type:** Int64 **Description:** Identifier of the binding property. **Note:** when displaying an organization chart, this binding is meant to represent the first manager level (N+1). In this case, it must be a mono-valued navigation. | -| Binding2 optional | **Type:** Int64 **Description:** Identifier of the binding property used to represent the second manager level (N+2) in the organization chart. It must be a mono-valued navigation. Cannot be used when `Binding` is not defined. | -| Binding3 optional | **Type:** Int64 **Description:** Identifier of the binding property used to represent the third manager level (N+3) in the organization chart. It must be a mono-valued navigation. Cannot be used when `Binding2` is not defined. | +| Binding2 optional | **Type:** Int64 **Description:** Identifier of the binding property used to represent the second manager level (N+2) in the organization chart. It must be a mono-valued navigation. Can't be used when `Binding` isn't defined. | +| Binding3 optional | **Type:** Int64 **Description:** Identifier of the binding property used to represent the third manager level (N+3) in the organization chart. It must be a mono-valued navigation. Can't be used when `Binding2` isn't defined. | | ColumnSize optional | **Type:** Int32 **Description:** Defines the control column size. | | DefaultValueBinding optional | **Type:** Int64 **Description:** Automatically sets the value in the control depending on this binding and the selected value in another corresponding picker. It's only available for controls with picker. _For example: `` After a selection of an organization in another picker in the form, the field location will be automatically set by the main location of the manager of the selected organization._ | | DisplayName_L1 optional | **Type:** String **Description:** Display name of the control in language 1 (up to 16). | @@ -131,9 +131,9 @@ In this example is a tree control which defines the relationships between a work | InputType default value: Inherited | **Type:** Enumeration **Description:** Input type of the control. | | IsReadOnly optional | **Type:** Boolean **Description:** Is a readonly form control. | | IsRequired optional | **Type:** Boolean **Description:** Is a required form control. | -| LinkedBinding1 optional | **Type:** Int64 **Description:** Coupled with FilterBinding1, it allows filtering on a list of items. LinkedBinding1 defines the binding on which the search will be carried out. Linked filters are only available for controls with the `Picker` InputType. | -| LinkedBinding2 optional | **Type:** Int64 **Description:** Coupled with FilterBinding2, it allows filtering a list of items. LinkedBinding2 defines the binding on which the search will be carried out. Linked filters are only available for controls with the `Picker` InputType. | -| Name optional | **Type:** String **Description:** Identifies the control inside the Form. This is used for translation files when a control cannot be identified by its binding such as for FieldSet. | +| LinkedBinding1 optional | **Type:** Int64 **Description:** Coupled with FilterBinding1, it allows filtering on a list of items. LinkedBinding1 defines the binding on which the search will be performed. Linked filters are only available for controls with the `Picker` InputType. | +| LinkedBinding2 optional | **Type:** Int64 **Description:** Coupled with FilterBinding2, it allows filtering a list of items. LinkedBinding2 defines the binding on which the search will be performed. Linked filters are only available for controls with the `Picker` InputType. | +| Name optional | **Type:** String **Description:** Identifies the control inside the Form. This is used for translation files when a control can't be identified by its binding such as for FieldSet. | | NavigationBinding optional | **Type:** Int64 **Description:** Defines the binding of the resource on which the user will be redirected when he clicks on an element of a BasicCollection. If not defined, the one defined in DisplayEntityProperty is used. | | OutputType default value: Inherited | **Type:** Enumeration **Description:** Output type of the control. | | ParentControl optional | **Type:** Int64 **Description:** Defines the parent form control. | diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/indicator.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/indicator.md index 29131f1e5d..9f6d34e92d 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/indicator.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/indicator.md @@ -10,7 +10,7 @@ More precisely, an indicator displays the appropriate banner whenever the *Bindi The banner is displayed wherever the associated resource appears. -For example, if we create an indicator pointing out the risk score of a user, the banner will show on the left-side of the user [tile](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/user-interface/tile) and the user [form](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/user-interface/form). If we create an indicator pointing out whether an AD account is unused or disabled, the banner will show on the left-side of the AD Entries tile and form. +For example, when creating an indicator pointing out the risk score of a user, the banner will show on the left-side of the user [tile](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/user-interface/tile) and the user [form](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/user-interface/form). When creating an indicator pointing out whether an AD account is unused or disabled, the banner will show on the left-side of the AD Entries tile and form. One entity can show several banners, one for several different properties. They appear one above the other if there are four banners or less, one next to the other if there are more. @@ -27,7 +27,7 @@ The XML file below states that if the risk score is greater than 75, only the in ``` -Note that if you write the "Medium risk" item before the "High risk" one, even if the score if greater than 75, the banner will be orange according to the first item: +If you write the "Medium risk" item before the "High risk" one, even if the score is greater than 75, the banner is orange according to the first item: ```xml @@ -36,13 +36,16 @@ Note that if you write the "Medium risk" item before the "High risk" one, even i ``` +:::note +If you write the "Medium risk" item before the "High risk" one, even if the score is greater than 75, the banner will be orange according to the first item. +::: ## Properties |Property|Details| |---|---| | Binding optional | **Type:** Int64 **Description:** Defines the binding path to a scalar property. | -| ComparisonOperator required | **Type:** QueryComparisonOperator **Description:** Defines how to compare the given binding to an indicator item value. All possible values: - Auto: The SearchOperator is calculated by the engine according to the type of element. - NotEqual: finds the elements that are not equal to the desired value. - Equal: finds the elements that are strictly equal to the desired value. - Contain: finds the elements that contain the desired value. - StartWith: finds the elements that start with the desired value. - EndWith: finds the elements that end with the desired value. - NotContain: finds the elements that do not contain the desired value. - NotStartWith: finds the elements that do not start with the desired value. - NotEndWith: finds the elements that do not end with the desired value. - GreaterThan: finds the elements that are greater than the desired value. - LessThan: finds the elements that are less than the desired value. - GreaterThanOrEqual: finds the elements that are greater than or equal to the desired value. - LessThanOrEqual: finds the elements that are less than or equal to the desired value. - Flexible*: The Flexible search operators transform the desired value according to the FlexibleComparisonExpression defined in Property then search. The flexible operators are: - FlexibleEqual. - FlexibleContain. - FlexibleStartWith. - FlexibleEndWith. | +| ComparisonOperator required | **Type:** QueryComparisonOperator **Description:** Defines how to compare the given binding to an indicator item value. All possible values: - Auto: The SearchOperator is calculated by the engine according to the type of element. - NotEqual: finds the elements that aren't equal to the value. - Equal: finds the elements that are strictly equal to the value. - Contain: finds the elements that contain the value. - StartWith: finds the elements that start with the value. - EndWith: finds the elements that end with the value. - NotContain: finds the elements that don't contain the value. - NotStartWith: finds the elements that don't start with the value. - NotEndWith: finds the elements that don't end with the value. - GreaterThan: finds the elements that are greater than the value. - LessThan: finds the elements that are less than the value. - GreaterThanOrEqual: finds the elements that are greater than or equal to the value. - LessThanOrEqual: finds the elements that are less than or equal to the value. - Flexible*: The Flexible search operators transform the value according to the FlexibleComparisonExpression defined in Property then search. The flexible operators are: - FlexibleEqual. - FlexibleContain. - FlexibleStartWith. - FlexibleEndWith. | | EntityType required | **Type:** Int64 **Description:** Represents the linked entity type. | | OptimizedBinding optional | **Type:** Int64 **Description:** Optimized Binding allows Indicators to be faster displayed. If it is filled in, it takes priority over the Binding located in the Indicator. | | Order required | **Type:** Int32 **Description:** Defines the order in which the banners are displayed. If there is no order needed, its value is zero for all indicators. | diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/menuitem.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/menuitem.md index 4870779a87..52ce6bad7a 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/menuitem.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/menuitem.md @@ -25,7 +25,7 @@ A menu item displays grouped navigation actions. | Identifier required | **Type:** String **Description:** Unique identifier of the item. | | IsExpandedByDefault default value: true | **Type:** Boolean **Description:** Is an expanded by default menu item. | | IsSelfForm default value: false | **Type:** Boolean **Description:** Is a self form menu item. | -| ParentMenuItem optional | **Type:** Int64 **Description:** Defines the parent menu item. Five ParentMenuItem are hard coded: - Dashboard: Allow to display MenuItem in dashboard (Home page) - Nav: Allow to display MenuItem in navigation section (the left part in dashboard) - UserMenu: Allow to display MenuItem in links list on click on user account in the top right corner - Reports: Define all the reports downloadable in the application - Top: Allow to display MenuItem in top bar of the application, between "Home" and "My tasks" | +| ParentMenuItem optional | **Type:** Int64 **Description:** Defines the parent menu item. Five ParentMenuItem are hard coded: - Dashboard: Allow to display MenuItem in dashboard (Home page) - Nav: Allow to display MenuItem in navigation section (the left part in dashboard) - UserMenu: Allow to display MenuItem in links list on click user account in the top right corner - Reports: Define all the reports downloadable in the application - Top: Allow to display MenuItem in top bar of the application, between "Home" and "My tasks" | | ReportQuery optional | **Type:** Int64 **Description:** Represents the linked report query. | | URI optional | **Type:** String **Description:** Represents the menu URI. | | Workflow optional | **Type:** Int64 **Description:** Represents the linked workflow. | diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/searchbar.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/searchbar.md index 2afbe57b7f..7602457421 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/searchbar.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/searchbar.md @@ -4,7 +4,7 @@ description: "" sidebar_position: 8 --- -The SearchBar is an element of the user interface that allows you to search from a list of properties of an EntityType. +Use the SearchBar to search from a list of properties of an EntityType. ## Examples @@ -41,7 +41,7 @@ See SearchBar for more details. | DisplayName_L1 optional | **Type:** String **Description:** Display name of the criteria in language 1 (up to 16). | | InputType required | **Type:** Enumeration **Description:** Type of the research property. (Auto: takes by default the type of the EntityType property.) | | IsVisibleInAdvancedView default value: false | **Type:** Boolean **Description:** `true` to make the property visible in the advanced search but not in the main search properties. | -| Operator default value: 0 | **Type:** QueryComparisonOperator **Description:** Defines how to do the research. All possible values: - Auto: The SearchOperator is calculated by the engine according to the type of element - NotEqual: finds the elements that are not equal to the desired value - Equal: finds the elements that are strictly equal to the desired value - Contain: finds the elements that contain the desired value - StartWith: finds the elements that start with the desired value - EndWith: finds the elements that end with the desired value - NotContain: finds the elements that do not contain the desired value - NotStartWith: finds the elements that do not start with the desired value - NotEndWith: finds the elements that do not end with the desired value - GreaterThan: finds the elements that are greater than the desired value - LessThan: finds the elements that are less than the desired value - GreaterThanOrEqual: finds the elements that are greater than or equal to the desired value - LessThanOrEqual: finds the elements that are less than or equal to the desired value - Flexible*: The Flexible search operators transform the desired value according to the FlexibleComparisonExpression defined in Property then search. The flexible operators are: - FlexibleEqual - FlexibleContain - FlexibleStartWith - FlexibleEndWith | +| Operator default value: 0 | **Type:** QueryComparisonOperator **Description:** Defines how to do the research. All possible values: - Auto: The SearchOperator is calculated by the engine according to the type of element - NotEqual: finds the elements that aren't equal to the value - Equal: finds the elements that are strictly equal to the value - Contain: finds the elements that contain the value - StartWith: finds the elements that start with the value - EndWith: finds the elements that end with the value - NotContain: finds the elements that don't contain the value - NotStartWith: finds the elements that don't start with the value - NotEndWith: finds the elements that don't end with the value - GreaterThan: finds the elements that are greater than the value - LessThan: finds the elements that are less than the value - GreaterThanOrEqual: finds the elements that are greater than or equal to the value - LessThanOrEqual: finds the elements that are less than or equal to the value - Flexible*: The Flexible search operators transform the value according to the FlexibleComparisonExpression defined in Property then search. The flexible operators are: - FlexibleEqual - FlexibleContain - FlexibleStartWith - FlexibleEndWith | | OptimizedBinding1 optional | **Type:** Int64 **Description:** Represents the first optimized binding definition. An optimized binding allows searches to be faster displayed. If it is filled in, it takes priority over the binding located in the search bar criterion column. | | PlaceHolderText_L1 optional | **Type:** String **Description:** Overloads the DisplayName of the search property with this string. | | ToolTipText_L1 optional | **Type:** String **Description:** Text displayed in the tool tip. | diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/tile.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/tile.md index 8519e60995..f05240d204 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/tile.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/user-interface/tile.md @@ -47,7 +47,7 @@ One data to display in a tile. |Property|Details| |---|---| -| AddedMinutes optional | **Type:** Int32 **Description:** Add minutes to the date field with this property. If the value is not defined, the default value is the one defined for the associated display entity property. | +| AddedMinutes optional | **Type:** Int32 **Description:** Add minutes to the date field with this property. If the value isn't defined, the default value is the one defined for the associated display entity property. | | Binding required | **Type:** Int64 **Description:** Defines the binding path to a scalar property. | | LineDisplayOrderIndicator required | **Type:** Int32 **Description:** Defines the display position of the data in the row. | | LineNumber required | **Type:** Int32 **Description:** Defines the number of the line in which the data is displayed. When the tileDesignElement of the tile is "picture-text", four lines are customizable, and 2 lines are hard coded: - 5: id of the resource to navigate on click - 6: photoTag | diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/aspects/addchangeaspect.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/aspects/addchangeaspect.md index cecb19447d..f234a47e6c 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/aspects/addchangeaspect.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/aspects/addchangeaspect.md @@ -41,8 +41,8 @@ The following example computes a new value for the `Card` property in users' rec | Identifier required | **Type:** String **Description:** Unique identifier of the aspect. | | AcceptNullValueExpression optional | **Type:** String **Description:** C# expression returning a boolean, `true` to consider `null` for the new value returned by `Expression`. By default, `null` values are ignored. | | Expression optional | **Type:** String **Description:** C# expression returning a new value for the property to be changed. **Note:** this property can also be defined by a binding via `ExpressionBinding`. | -| ExpressionBinding optional | **Type:** String **Description:** Binding:- that defines the variable type used in the potential expressions specified in the aspect;- whose difference with `Binding` defines the property involved in the aspect.**Note:** required when handling the property of multi-valued objects, for example records, to make sure to modify the property in all records and not only in one. | -| IfExpression optional | **Type:** String **Description:** Expression that conditions the aspect execution. [See more details on C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). | +| ExpressionBinding optional | **Type:** String **Description:** Binding:- that defines the variable type used in the potential expressions specified in the aspect;- whose difference with `Binding` defines the property involved in the aspect.**Note:** required when handling the property of multi-valued objects, for example records, to ensure to modify the property in all records and not only in one. | +| IfExpression optional | **Type:** String **Description:** Expression that conditions the aspect execution. [Learn about C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). | | Priority default value: 0 | **Type:** Int32 **Description:** Execution priority among all aspects. At a given activity state, the aspect with the highest priority will be triggered first.**Note:** the priority can be a negative value. | diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/aspects/assertvalueaspect.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/aspects/assertvalueaspect.md index 24b4b895ba..7d23f0c7f8 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/aspects/assertvalueaspect.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/aspects/assertvalueaspect.md @@ -27,7 +27,7 @@ For example, to manage records, using the `ExpressionBinding` set to `Workflow_D Instead, the `ExpressionBinding` should be set to `Workflow_Directory_User:Directory_User` and the `Expression` should use `C#:user:return user.Records...` ::: -The following example makes sure that a user's positions do not overlap. +The following example makes sure that a user's positions don't overlap. ```xml default value: 0 | **Type:** Int32 **Description:** Execution priority among all aspects. At a given activity state, the aspect with the highest priority will be triggered first.**Note:** the priority can be a negative value. | diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/aspects/assertvaluerequiredaspect.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/aspects/assertvaluerequiredaspect.md index e688344cdb..7af3bc9e9f 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/aspects/assertvaluerequiredaspect.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/aspects/assertvaluerequiredaspect.md @@ -26,8 +26,8 @@ The following example makes sure that the contract start date is specified for a |---|---| | Binding required | **Type:** String **Description:** Binding whose difference with `ExpressionBinding` defines the property to be validated by the aspect. | | Identifier required | **Type:** String **Description:** Unique identifier of the aspect. | -| ExpressionBinding optional | **Type:** String **Description:** Binding:- that defines the variable type used in the potential expressions specified in the aspect;- whose difference with `Binding` defines the property involved in the aspect.**Note:** required when handling the property of multi-valued objects, for example records, to make sure to modify the property in all records and not only in one. | -| IfExpression optional | **Type:** String **Description:** Expression that conditions the aspect execution. [See more details on C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). | +| ExpressionBinding optional | **Type:** String **Description:** Binding:- that defines the variable type used in the potential expressions specified in the aspect;- whose difference with `Binding` defines the property involved in the aspect.**Note:** required when handling the property of multi-valued objects, for example records, to ensure to modify the property in all records and not only in one. | +| IfExpression optional | **Type:** String **Description:** Expression that conditions the aspect execution. [Learn about C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). | | Message_L1 optional | **Type:** String **Description:** Message in language 1 (up to 16) to be displayed when the property is empty. | | Priority default value: 0 | **Type:** Int32 **Description:** Execution priority among all aspects. At a given activity state, the aspect with the highest priority will be triggered first.**Note:** the priority can be a negative value. | diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/aspects/builduniquevalueaspect.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/aspects/builduniquevalueaspect.md index 6fc4032d66..27161fbcb2 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/aspects/builduniquevalueaspect.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/aspects/builduniquevalueaspect.md @@ -24,17 +24,17 @@ The following example generates bots' logins during their creation. | Binding required | **Type:** String **Description:** Binding whose difference with `ExpressionBinding` defines the property to be computed. | | Identifier required | **Type:** String **Description:** Unique identifier of the aspect. | | Expression optional | **Type:** String **Description:** C# expression that computes the unique value.**Note:** the computation can be configured in SQL instead of C# via `SqlBuildExpression`. Decide whether to use either `Expression` or `SqlBuildExpression`, not both. | -| ExpressionBinding optional | **Type:** String **Description:** Binding:- that defines the variable type used in the potential expressions specified in the aspect;- whose difference with `Binding` defines the property involved in the aspect.**Note:** required when handling the property of multi-valued objects, for example records, to make sure to modify the property in all records and not only in one. | +| ExpressionBinding optional | **Type:** String **Description:** Binding:- that defines the variable type used in the potential expressions specified in the aspect;- whose difference with `Binding` defines the property involved in the aspect.**Note:** required when handling the property of multi-valued objects, for example records, to ensure to modify the property in all records and not only in one. | | HistorizeBinding optional | **Type:** String **Description:** Binding that stores all the old values computed by the aspect. | | HistorizeSeparator default value: ¤ | **Type:** String **Description:** Defines the character used as a separator in the `HistorizeBinding` property. | -| IfExpression optional | **Type:** String **Description:** Expression that conditions the aspect execution. [See more details on C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). | -| IterationsCount default value: 0 | **Type:** String **Description:** Maximum number of computation attempts without finding a unique value.**Note:** a variable named `iteration` is available to use the attempt number in the expressions of the aspect and/or of the potential unicity check rules, for example to help manage homonyms. Hence, a custom variable cannot be declared with the name `iteration`. | +| IfExpression optional | **Type:** String **Description:** Expression that conditions the aspect execution. [Learn about C# expression syntax](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). | +| IterationsCount default value: 0 | **Type:** String **Description:** Maximum number of computation attempts without finding a unique value.**Note:** a variable named `iteration` is available to use the attempt number in the expressions of the aspect and/or of the potential unicity check rules, for example to help manage homonyms. Hence, a custom variable can't be declared with the name `iteration`. | | Message_L1 default value: | **Type:** String **Description:** Message in language 1 (up to 16) to be displayed when the value generation failed, i.e. when `IterationsCount` is exceeded. | | OnlyIfNew default value: false | **Type:** String **Description:** `true` to trigger the aspect only for the creation of new resources. | | Priority default value: 0 | **Type:** Int32 **Description:** Execution priority among all aspects. At a given activity state, the aspect with the highest priority will be triggered first.**Note:** the priority can be a negative value. | | SimulationExpression optional | **Type:** String **Description:** Expression used instead of the `Expression` parameter when previewing the workflow result before its implementation. | | SqlBuildExpression optional | **Type:** String **Description:** SQL command that computes the unique value.**Note:** the computation can be configured in C# instead of SQL via `Expression`. Decide whether to use either `SqlBuildExpression` or `Expression`, not both. | -| SqlCheckExpression optional | **Type:** String **Description:** SQL request that checks whether the value computed with the binding/expression is unique, i.e. not yet used by another resource.**Note:** required if zero [unicity check rules](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/workflows/aspects/builduniquevalueaspect#child-element-unicitycheckrule) are linked to the aspect.**Warning:** the SQL request must be efficient because a potential timeout may block the progress of the workflow. For example, when the database's state and indexes are not well known, prefer to use views rather than the whole tables, because views store way fewer elements than tables, which makes them faster to use in a request. | +| SqlCheckExpression optional | **Type:** String **Description:** SQL request that checks whether the value computed with the binding/expression is unique, i.e. not yet used by another resource.**Note:** required if zero [unicity check rules](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/workflows/aspects/builduniquevalueaspect#child-element-unicitycheckrule) are linked to the aspect.**Warning:** the SQL request must be efficient because a potential timeout may block the progress of the workflow. For example, when the database's state and indexes aren't well known, prefer to use views rather than the whole tables, because views store way fewer elements than tables, which makes them faster to use in a request. | ## Child Element: PointCut @@ -58,21 +58,21 @@ A unicity check rule ensures that the expression computed by a [`BuildUniqueValu The comparison performed by these rules to check unicity can be configured in SQL instead of C# via the [`SqlCheckExpression`](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/workflows/aspects/builduniquevalueaspect) property of the aspect. ::: -The value of the source binding/expression is computed based on the properties of the source resource which is the resource whose property we compute via the `BuildUniqueValue` aspect. +The value of the source binding/expression is computed based on the properties of the source resource which is the resource whose property Identity Manager computes via the `BuildUniqueValue` aspect. The rule compares the return value of the source binding/expression with the existing values of the target binding/expression in the target entity type. ![Schema: Unicity Check](/images/identitymanager/aspects_unicitycheck.webp) -> For example, we need to generate an email address for any new user joining the company. We configure in a `BuildUniqueValue` aspect that users' emails are computed with `{firstName}.{lastName}@{EmailDomain}`. +> For example, to generate an email address for any new user joining the company, configure in a `BuildUniqueValue` aspect that users' emails are computed with `{firstName}.{lastName}@{EmailDomain}`. > -> Consider a new user called John Doe. We need to link to the aspect a unicity check rule that is going to compare the email core `john.doe` with the email cores of existing resources in a given entity type. Thus Identity Manager can ensure that the email core is unique, and finally build the unique email address. +> Consider a new user called John Doe. Link to the aspect a unicity check rule that is going to compare the email core `john.doe` with the email cores of existing resources in a given entity type. Thus Identity Manager can ensure that the email core is unique, and finally build the unique email address. Both source and target bindings/expressions must be consistent with the binding/expression used in [the corresponding aspect](/docs/identitymanager/current/integration-guide/toolkit/xml-configuration/workflows/aspects/builduniquevalueaspect) which must not use a `SqlCheckExpression`. :::info -One `BuildUniqueValue` aspect can be linked to many unicity check rules, but should not be linked to more than one rule per target entity type. +One `BuildUniqueValue` aspect can be linked to many unicity check rules, but shouldn't be linked to more than one rule per target entity type. The unicity check rules linked to a same aspect are combined with the AND operator. It means that the aspect's iteration goes up when at least one of the rules detects non-unicity. ::: @@ -89,14 +89,14 @@ When creating or updating a unicity check rule, launch the [`ComputeCorrelationK The following example checks the unicity of the login of a new user. -> In order to be able to write the source and target bindings/expressions of the unicity check rule, you must understand the binding/expression of the corresponding `BuildUniqueValue` aspect: +> to be able to write the source and target bindings/expressions of the unicity check rule, you must understand the binding/expression of the corresponding `BuildUniqueValue` aspect: > ```xml > > > > ``` -We want to check the unicity of the new user's login, compared with the logins of existing users: +To check the unicity of the new user's login, compare it with the logins of existing users: ```xml @@ -108,7 +108,7 @@ Here the source binding and expression are those from the aspect. #### Multiple unicity checks -With the same aspect as the previous example, we might want to compare the login of the new user with the list of reserved logins too: +To compare the login of the new user with the list of reserved logins, use the same aspect as the previous example: ```xml @@ -119,7 +119,7 @@ With the same aspect as the previous example, we might want to compare the login The following example checks the unicity of the email address of a new user. -> In order to be able to write the source and target bindings/expressions of the unicity check rule, you must understand the binding/expression of the corresponding `BuildUniqueValue` aspect: +> to be able to write the source and target bindings/expressions of the unicity check rule, you must understand the binding/expression of the corresponding `BuildUniqueValue` aspect: > ```xml > @@ -145,7 +145,7 @@ The following example checks the unicity of the email address of a new user. > return result;" IterationsCount="10" /> > ``` -We want to include in the unicity check only the email's core `firstName.lastName` without the `@EmailDomain` part. This is why the source expression starts like the aspect's expression but does not add the domain part, and the target expression removes the domain part from existing values: +To include in the unicity check only the email's core `firstName.lastName` without the `@EmailDomain` part, configure the source expression to start like the aspect's expression but not add the domain part, and set the target expression to remove the domain part from existing values: ```xml |Property|Details| |---|---| |SourceBinding
optional|

**Type**
Int64

**Description**
Binding property (from the source entity type specified in the corresponding workflow) whose value is to be compared with the existing values of the target binding/expression.

**Note:** when not specified, the unicity check rule uses the binding from the aspect.

| -|SourceExpression
optional|

**Type**
String

**Description**
Binding expression (based on properties from the source entity type specified in the corresponding workflow) whose value is to be compared with the existing values of the target binding/expression. [See more details on C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions).

**Note:** when not specified, the unicity check rule uses the expression from the aspect.

| +|SourceExpression
optional|

**Type**
String

**Description**
Binding expression (based on properties from the source entity type specified in the corresponding workflow) whose value is to be compared with the existing values of the target binding/expression. [Learn about C# expression syntax](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions).

**Note:** when not specified, the unicity check rule uses the expression from the aspect.

| |TargetBinding
optional|

**Type**
Int64

**Description**
Binding property (from the target entity type) whose values corresponding to existing resources are to be compared with the value of the source binding/expression.

| |TargetEntityType
required|

**Type**
Int64

**Description**
Identifier of the entity type for which the rule checks the property's unicity.

| -|TargetExpression
optional|

**Type**
String

**Description**
Binding expression (based on properties from the target entity type) whose values corresponding to existing resources are to be compared with the value of the source binding/expression. [See more details on C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions).

| +|TargetExpression
optional|

**Type**
String

**Description**
Binding expression (based on properties from the target entity type) whose values corresponding to existing resources are to be compared with the value of the source binding/expression. [Learn about C# expression syntax](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions).

| diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/aspects/invokescriptaspect.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/aspects/invokescriptaspect.md index 172137ba4c..26747a5510 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/aspects/invokescriptaspect.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/aspects/invokescriptaspect.md @@ -24,8 +24,8 @@ The following example executes the script `aspect.ps1` on the local agent, when |---|---| | Identifier required | **Type:** String **Description:** Unique identifier of the aspect. | | Agent optional | **Type:** String **Description:** Agent on which the script will be launched. | -| ExpressionBinding optional | **Type:** String **Description:** Binding:- that defines the variable type used in the potential expressions specified in the aspect;- whose difference with `Binding` defines the property involved in the aspect.**Note:** required when handling the property of multi-valued objects, for example records, to make sure to modify the property in all records and not only in one. | -| IfExpression optional | **Type:** String **Description:** Expression that conditions the aspect execution. [See more details on C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). | +| ExpressionBinding optional | **Type:** String **Description:** Binding:- that defines the variable type used in the potential expressions specified in the aspect;- whose difference with `Binding` defines the property involved in the aspect.**Note:** required when handling the property of multi-valued objects, for example records, to ensure to modify the property in all records and not only in one. | +| IfExpression optional | **Type:** String **Description:** Expression that conditions the aspect execution. [Learn about C# expression syntax](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). | | Priority default value: 0 | **Type:** Int32 **Description:** Execution priority among all aspects. At a given activity state, the aspect with the highest priority will be triggered first.**Note:** the priority can be a negative value. | | ScriptFile optional | **Type:** String **Description:** Path of the script file to be executed by the aspect. | diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/aspects/invokeworkflowaspect.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/aspects/invokeworkflowaspect.md index 697d83cd30..d749490d08 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/aspects/invokeworkflowaspect.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/aspects/invokeworkflowaspect.md @@ -23,8 +23,8 @@ The following example launches the workflow `Directory_User_VehicleRequest` when |---|---| | Identifier required | **Type:** String **Description:** Unique identifier of the aspect. | | Workflow required | **Type:** String **Description:** Identifier of the workflow to be launched. | -| ExpressionBinding optional | **Type:** String **Description:** Binding:- that defines the variable type used in the potential expressions specified in the aspect;- whose difference with `Binding` defines the property involved in the aspect.**Note:** required when handling the property of multi-valued objects, for example records, to make sure to modify the property in all records and not only in one. | -| IfExpression optional | **Type:** String **Description:** Expression that conditions the aspect execution. [See more details on C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). | +| ExpressionBinding optional | **Type:** String **Description:** Binding:- that defines the variable type used in the potential expressions specified in the aspect;- whose difference with `Binding` defines the property involved in the aspect.**Note:** required when handling the property of multi-valued objects, for example records, to ensure to modify the property in all records and not only in one. | +| IfExpression optional | **Type:** String **Description:** Expression that conditions the aspect execution. [Learn about C# expression syntax](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions). | | Priority default value: 0 | **Type:** Int32 **Description:** Execution priority among all aspects. At a given activity state, the aspect with the highest priority will be triggered first.**Note:** the priority can be a negative value. | diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/aspects/notificationaspect.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/aspects/notificationaspect.md index 02b76a5ad3..936b1012dc 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/aspects/notificationaspect.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/aspects/notificationaspect.md @@ -37,7 +37,7 @@ The notification will be sent to all email addresses defined by `Directory_Guest | Identifier required | **Type:** String **Description:** Unique identifier of the aspect. | | Binding optional | **Type:** String **Description:** Binding whose difference with `ExpressionBinding` defines the property that corresponds to identities' email addresses, when `Type` is set to `Binding`. | | CssFile optional | **Type:** String **Description:** Path to the css file that defines the styles for the email.**Note:** the path must be relative to the configuration folder, and the file must be inside it. | -| ExpressionBinding optional | **Type:** String **Description:** Binding:- that defines the variable type used in the potential expressions specified in the aspect;- whose difference with `Binding` defines the property involved in the aspect.**Note:** required when handling the property of multi-valued objects, for example records, to make sure to modify the property in all records and not only in one. | +| ExpressionBinding optional | **Type:** String **Description:** Binding:- that defines the variable type used in the potential expressions specified in the aspect;- whose difference with `Binding` defines the property involved in the aspect.**Note:** required when handling the property of multi-valued objects, for example records, to ensure to modify the property in all records and not only in one. | | Priority default value: 0 | **Type:** Int32 **Description:** Execution priority among all aspects. At a given activity state, the aspect with the highest priority will be triggered first.**Note:** the priority can be a negative value. | | RazorFile_L1 optional | **Type:** String **Description:** Path to the Razor cshtml file that defines the email's body template in language 1 (up to 16).**Note:** the path must be relative to the configuration folder, and the file must be inside it. | | SubjectExpression_L1 optional | **Type:** String **Description:** C# expression that defines the email's subject in language 1 (up to 16). The expression's variable type is defined in `ExpressionBinding`. | @@ -80,7 +80,7 @@ The following example sends a notification email to the performers of the `Reque ``` -The following example sends a notification email to the email address, stored in `Mail`, of the user(s) from `Directory_User` targeted by the workflow, so here the new user created by the `Directory_User_StartInternal` workflow. +The following example sends a notification email to the email address, stored in `Mail`, of the users from `Directory_User` targeted by the workflow, so here the new user created by the `Directory_User_StartInternal` workflow. ```xml @@ -124,6 +124,6 @@ Knowing that we also have: |ActivityState
optional|

**Type**
Enumeration

**Description**
Identifier of the activity state whose last performers are to be notified, when `Type` is set to `Performer`.

**Note:** must be set together with `Activity`.

| |Binding
optional|

**Type**
Int64

**Description**
Binding of the property that represents the notification's recipients, when `Type` is set to `Binding`.

| |EmailAddresses
optional|

**Type**
String

**Description**
Email addresses of the notification's recipients, when `Type` is set to `Hardcoded`.

| -|Expression
optional|

**Type**
String

**Description**
C# expression that returns the email addresses of the notification's recipients, as strings or IEnumerable\, when `Type` is set to `Expression`. The expression's variable type is defined in `ExpressionBinding` in the associated `NotificationAspect`. [See more details on C# expressions](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions).

| -|IsCC
default value: false|

**Type**
Boolean

**Description**
`true` to send the notification email to the recipient(s) as a carbon copy (CC).

| +|Expression
optional|

**Type**
String

**Description**
C# expression that returns the email addresses of the notification's recipients, as strings or IEnumerable\, when `Type` is set to `Expression`. The expression's variable type is defined in `ExpressionBinding` in the associated `NotificationAspect`. [Learn about C# expression syntax](/docs/identitymanager/current/integration-guide/toolkit/expressions#c-expressions).

| +|IsCC
default value: false|

**Type**
Boolean

**Description**
`true` to send the notification email to the recipients as a carbon copy (CC).

| |Type
required|

**Type**
RecipientType

**Description**
Type of recipients for the email notification.

**Actor**: the identities with the permissions to act on the next step of the workflow specified in the pointcut.
**Performer**: the actors of a past workflow step specified in `Activity` and `ActivityState`.
**Binding**: the identities whose email addresses are designated by the property specified in `Binding`.
**Hardcoded**: the identities whose email addresses are specified explicitly in `EmailAddresses`.
**Expression**: the identities whose email addresses match the C# expression specified in `Expression`.
**Profile**: the identities with the permission `/Custom/WorkflowsNotifications/{workflow_identifier}/`
`{activity_identifier}/{activityTemplateState_shortIdentifier}`.

| diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/forms/index.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/forms/index.md index b651d71b13..43e3fa90cd 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/forms/index.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/forms/index.md @@ -31,4 +31,4 @@ Displays a form to update data for several resources simultaneously. Displays a form to select an existing record and update it. - [Workflow Update Several Records Entity Form](./workflowupdateseveralrecordsentityform) -Displays a form to create, update or delete one or several records. +Displays a form to create, update, or delete one or several records. diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/forms/workflowaddandendrecordentityform.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/forms/workflowaddandendrecordentityform.md index b8e5076994..1709139af7 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/forms/workflowaddandendrecordentityform.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/forms/workflowaddandendrecordentityform.md @@ -44,7 +44,7 @@ The contents of `MainControl` and `RecordControl` are visible during the workflo ![Form Example - Update Position](/images/identitymanager/formexample_workflowaddandendrecordentityform_v603.webp) :::note -The content of `RecordUniqueItemControl` is not visible. The user's records that have the same values for all the properties in `RecordUniqueItemControl` will be displayed, and potentially modified, as one. +The content of `RecordUniqueItemControl` isn't visible. The user's records that have the same values for all the properties in `RecordUniqueItemControl` will be displayed, and potentially modified, as one. ::: The contents of `MainSummaryControl` and `RecordSummaryControl` are visible after the workflow's execution: diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/forms/workflowaddrecordentityform.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/forms/workflowaddrecordentityform.md index 309224677d..a7c85b3505 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/forms/workflowaddrecordentityform.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/forms/workflowaddrecordentityform.md @@ -49,7 +49,7 @@ The contents of `MainControl` and `RecordControl` are visible during the workflo ![Form Example - Computer Request](/images/identitymanager/formexample_workflowaddrecordentityform_v603.webp) :::note -The content of `RecordUniqueItemControl` is not visible. The user's records that have the same values for all the properties in `RecordUniqueItemControl` will be displayed, and potentially modified, as one. +The content of `RecordUniqueItemControl` isn't visible. The user's records that have the same values for all the properties in `RecordUniqueItemControl` will be displayed, and potentially modified, as one. ::: The contents of `MainSummaryControl` and `RecordSummaryControl` are visible after the workflow's execution: diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/forms/workflowupdaterecordentitiesform.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/forms/workflowupdaterecordentitiesform.md index 74c79fc858..6cf564d830 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/forms/workflowupdaterecordentitiesform.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/forms/workflowupdaterecordentitiesform.md @@ -48,7 +48,7 @@ The contents of `MainControl` and `RecordControl` are visible during the workflo ![Form Example - Mass Update](/images/identitymanager/formexample_workflowupdaterecordentitiesform_v603.webp) :::note -The content of `RecordUniqueItemControl` is not visible. The user's records that have the same values for all the properties in `RecordUniqueItemControl` will be modified as one. +The content of `RecordUniqueItemControl` isn't visible. The user's records that have the same values for all the properties in `RecordUniqueItemControl` will be modified as one. ::: The contents of `MainSummaryControl` and `RecordSummaryControl` are visible after the workflow's execution: diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/forms/workflowupdaterecordentityform.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/forms/workflowupdaterecordentityform.md index 082471b3bc..20c99642ad 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/forms/workflowupdaterecordentityform.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/forms/workflowupdaterecordentityform.md @@ -73,7 +73,7 @@ The contents of `MainControl` and `RecordControl` are visible during the workflo ![Form Example - Update Data](/images/identitymanager/formexample_workflowupdaterecordentityform_v603.webp) :::note -The content of `RecordUniqueItemControl` is not visible. The user's records that have the same values for all the properties in `RecordUniqueItemControl` will be displayed, and potentially modified, as one. +The content of `RecordUniqueItemControl` isn't visible. The user's records that have the same values for all the properties in `RecordUniqueItemControl` will be displayed, and potentially modified, as one. ::: The contents of `MainSummaryControl` and `RecordSummaryControl` are visible after the workflow's execution: diff --git a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/forms/workflowupdateseveralrecordsentityform.md b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/forms/workflowupdateseveralrecordsentityform.md index cdda78c9d9..6a2ec5a709 100644 --- a/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/forms/workflowupdateseveralrecordsentityform.md +++ b/docs/identitymanager/7.0/integration-guide/toolkit/xml-configuration/workflows/forms/workflowupdateseveralrecordsentityform.md @@ -1,14 +1,14 @@ --- title: "WorkflowUpdateSeveralRecordsEntityForm" -description: "Displays a form to create, update or delete one or several records." +description: "Displays a form to create, update, or delete one or several records." sidebar_position: 9 --- -Displays a form to create, update or delete one or several records. +Displays a form to create, update, or delete one or several records. ## Examples -The following example is a form to create, update and/or delete one or several positions for a given user. +The following example is a form to create, update, and/or delete one or several positions for a given user. ```xml @@ -70,11 +70,11 @@ And with the following form for the data that groups records together: The contents of `MainControl`, `RecordControl`, `RecordSlaveUniqueItemControl` and `RecordSlaveControl` are visible during the workflow's execution: ![Form Example - Manage a User's Positions](/images/identitymanager/formexample_workflowupdateseveralrecordsentityform_v603.webp) -When adding a new position, we decide to make `Title` available, in addition to the fields used to update existing records: +When adding a new position, `Title` is made available in addition to the fields used to update existing records: ![Formexample Workflowupdateseveralrecordsentityform V603](/images/identitymanager/formexample_workflowupdateseveralrecordsentityform_v603.webp) :::note -The content of `RecordUniqueItemControl` is not visible. The user's records that have the same values for all the properties in `RecordUniqueItemControl` will be displayed, and potentially modified, as one. +The content of `RecordUniqueItemControl` isn't visible. The user's records that have the same values for all the properties in `RecordUniqueItemControl` will be displayed, and potentially modified, as one. :::