SQL Server must protect against a user falsely repudiating by ensuring only clearly unique Active Directory user accounts can connect to the instance.
From MS SQL Server 2016 Instance Security Technical Implementation Guide
Part of SRG-APP-000080-DB-000063
Associated with:
CCI-000166
SV-93837r2_rule
SQL Server must protect against a user falsely repudiating by ensuring only clearly unique Active Directory user accounts can connect to the instance.
Vulnerability discussion
Non-repudiation of actions taken is required in order to maintain data integrity. Examples of particular actions taken by individuals include creating information, sending a message, approving information (e.g., indicating concurrence or signing a contract), and receiving a message. Non-repudiation protects against later claims by a user of not having created, modified, or deleted a particular data item or collection of data in the database. In designing a database, the organization must define the types of data and the user actions that must be protected from repudiation. The implementation must then include building audit features into the application data tables and configuring the DBMS's audit tools to capture the necessary audit trail. Design and implementation also must ensure that applications pass individual user identification to the DBMS, even where the application connects to the DBMS with a standard, shared account. If the computer account of a remote computer is granted access to SQL Server, any service or scheduled task running as NT AUTHORITY\SYSTEM or NT AUTHORITY\NETWORK SERVICE can log into the instance and perform actions. These actions cannot be traced back to a specific user or process.
Check content
Execute the following query:
SELECT name
FROM sys.server_principals
WHERE type in ('U','G')
AND name LIKE '%$'
If no logins are returned, this is not a finding.
If logins are returned, determine whether each login is a computer account.
Launch PowerShell.
Execute the following code:
Note: represents the username portion of the login. For example, if the login is "CONTOSO\user1$", the username is "user1".
([ADSISearcher]"(&(!ObjectCategory=Computer)(Name=))").FindAll()
If no account information is returned, this is not a finding.
If account information is returned, this is a finding.
Fix text
Remove all logins that were returned in the check content.
Pro Tips
Lavender hyperlinks in small type off to the right (of CSS
class id, if you view the page source) point to
globally unique URIs for each document and item. Copy the
link location and paste anywhere you need to talk
unambiguously about these things.
You can obtain data about documents and items in other
formats. Simply provide an HTTP header Accept:
text/turtle or
Accept: application/rdf+xml.
Powered by sagemincer