Configure credentialed scanning for Windows systems
You can provide credentials to a Managed Risk Scanner to allow the scanner to scan your environment with elevated permissions.
Note: To configure credentialed scanning in the Risk Dashboard, see Configure credentialed scanning for Windows systems in the Risk Dashboard.
On Windows, credentialed scans use SMB on port 139 and 445 to authenticate using a username and password.
- Newer versions of SMB use port 445 to directly operate over TCP/IP. NetBIOS is not used.
- Older versions of SMB use port 139 over TCP/IP. This port is used for file and printer sharing over NetBIOS.
Note:
- If you rotate your credentials, you must reset them on the scanner as well.
- To minimize security risks, Arctic Wolf recommends that you use these credentials for scanning only. Do not provide more permissions to these credentials or use them with systems other than the scanner.
These resources are required:
- A valid username, which can contain these characters:
- Any alphanumeric character
- -
- _
- @
- .
- \
- A user account that:
- Has administrator access privileges.
- Has PowerShell execution privileges.
- If your system is not attached to a domain controller (DC), or if you are using a local administrator account on a system that is attached to a DC — Uses this registry key:
SHELL
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ DWORD: LocalAccountTokenFilterPolicy = 1 - If your system is attached to a DC — Is a group domain administrator.
These actions are required:
- Make sure that the scanner can sign into scan targets without access policy restrictions on targets.
- Make sure that the Remote Registry service is active. The Remote Registry Service must be active so that the scanner can access the registry.
Note: You can configure the system to automatically start the registry service at startup. If you configure the system to start the registry service manually, the service starts during credential scans by the scanner and is disabled afterwards.
- Activate file and printer sharing on the target systems.
- You may need to create an exception rule for the scanner in your firewall. Make sure that there are no security policies that would block the scanner from performing credential checks.