Create a Microsoft SharePoint (MS SharePoint) record in order to authenticate to a MS SharePoint database instance, and scan it for compliance. Windows authentication is required so you'll also need a Windows record for the host running the database.
This record type is only available in accounts with PC or SCA and is only supported for compliance scans.
For the most current list of supported authentication technologies and the versions that have been certified for VM and PC by record type, please refer to the following article:
Authentication Technologies Matrix
- Go to Scans > Authentication.
- Check that you have a Windows record already defined for the host running SharePoint.
- Create a MS SharePoint record for the same host. Go to New > Applications > Microsoft SharePoint.
Note: If the Network Support feature is enabled, then the Windows record must have the same network selected as the Microsoft SharePoint record.
Tell me about user permissionsTell me about user permissions
Managers can add authentication records.
Unit Managers must be granted these permissions:
- Manage PC module / Manage SCA module
- Create/edit authentication records/vaults
Enter IP addresses for the Microsoft SharePoint targets you want to scan for compliance. Each IP may be included in one Microsoft SharePoint record. We'll auto discover the database instances.
You'll provide login credentials for your MS SQL Server database account. Enter the MS SQL Server username and password. Or choose Vault based to retrieve the password from one of the supported vaults.
To use a vault, go to Scans > Authentication > New > Authentication Vaults and tell us about your vault system. Then choose "Authentication Type: Vault based" in your SharePoint record and select your vault type and vault record. At scan time, we'll authenticate to hosts using the username in your record and the password we find in your vault.
Choose the type of authentication you want to perform: Windows or Database. If you choose Windows, provide the name of the Windows domain where the account is stored. The domain name is required because the scanning engine must associate the operating system account with the MS SQL Server database account for authentication.
Our scanners will attempt authentication to your target hosts using one of the authentication protocols selected in the record, starting with the most secure protocol to the least secure protocol. We support these protocols: Kerberos, NTLMv2 and NTLMv1.
When a Unit Manager edits a record, the Unit Manager only sees the IPs in the record that they have permission to. Any changes made by the Unit Manager to the record settings will apply to all hosts defined in the record, regardless of whether all hosts belong to the user's business unit. The record may contain more IPs that are not visible to the Unit Manager.