STIGQter: STIG Summary: MS SQL Server 2016 Instance Security Technical Implementation Guide Version: 2 Release: 3 Benchmark Date: 23 Apr 2021: STIGQter: STIG Summary: MS SQL Server 2016 Instance Security Technical Implementation Guide Version: 2 Release: 3 Benchmark Date: 23 Apr 2021:SV-213933r617437_rule
V-213933
SRG-APP-000080-DB-000063
SQL6-D0-004000
CAT II
10
Remove user-accessible shared accounts and use individual user IDs.
Build/configure applications to ensure successful individual authentication prior to shared account access.
Ensure each user's identity is received and used in audit data in all relevant circumstances.
Design, develop, and implement a method to log use of any account to which more than one person has access. Restrict interactive access to shared accounts to the fewest persons possible.
Obtain the list of authorized SQL Server accounts in the system documentation.
Determine if any accounts are shared. A shared account is defined as a username and password that are used by multiple individuals to log into SQL Server. An example of a shared account is the SQL Server installation account. Windows Groups are not shared accounts as the group itself does not have a password.
If accounts are determined to be shared, determine if individuals are first individually authenticated.
If individuals are not individually authenticated before using the shared account (e.g., by the operating system or possibly by an application making calls to the database), this is a finding.
The key is individual accountability. If this can be traced, this is not a finding.
If accounts are determined to be shared, determine if they are directly accessible to end users. If so, this is a finding.
Review contents of audit logs, traces and data tables to confirm that the identity of the individual user performing the action is captured.
If shared identifiers are found, and not accompanied by individual identifiers, this is a finding.
Note: Privileged installation accounts may be required to be accessed by the DBA or other administrators for system maintenance. In these cases, each use of the account must be logged in some manner to assign accountability for any actions taken during the use of the account.
V-213933
False
SQL6-D0-004000
Obtain the list of authorized SQL Server accounts in the system documentation.
Determine if any accounts are shared. A shared account is defined as a username and password that are used by multiple individuals to log into SQL Server. An example of a shared account is the SQL Server installation account. Windows Groups are not shared accounts as the group itself does not have a password.
If accounts are determined to be shared, determine if individuals are first individually authenticated.
If individuals are not individually authenticated before using the shared account (e.g., by the operating system or possibly by an application making calls to the database), this is a finding.
The key is individual accountability. If this can be traced, this is not a finding.
If accounts are determined to be shared, determine if they are directly accessible to end users. If so, this is a finding.
Review contents of audit logs, traces and data tables to confirm that the identity of the individual user performing the action is captured.
If shared identifiers are found, and not accompanied by individual identifiers, this is a finding.
Note: Privileged installation accounts may be required to be accessed by the DBA or other administrators for system maintenance. In these cases, each use of the account must be logged in some manner to assign accountability for any actions taken during the use of the account.
M
3993