MS SQL Server authentication records are applied automatically to compliance scans when the compliance module is enabled. Note that MS SQL Server records cannot be applied to vulnerability scans at this time.
Each MS SQL Server record identifies: account login credentials, database information (instance name, database name, and port number), and target IP addresses.
Using the specified credentials, the scanning engine is able to authenticate to MS SQL Server databases at the time of the scan in order to gather system information and perform in-depth analysis.
It is recommended you define a dedicated user account for MS SQL Server trusted scanning. You have the option to use a MS SQL Server database account, or a Windows operating system account that is associated with a SQL Server database account.
Account requirements are described in detail in the following document:
MS SQL Server Trusted Scanning: Setup for Compliance Scans
This document is available for download from the Tips & Techniques section on the Resources page (Help > Resources).
Once you've defined a user account to be used for authentication, it's time to add a MS SQL Server authentication record. See Creating MS SQL Server Records for instructions.