From 14255c79dd9b5c37b6a4b206331563cb2454eaf9 Mon Sep 17 00:00:00 2001 From: hinderjd Date: Sat, 20 Jul 2024 12:22:22 -0600 Subject: [PATCH] Update Powerstig to parse\apply U_MS_SQL_Server_2016_Instance_V3R1_Manual_STIG #1373 --- CHANGELOG.md | 2 + ..._2016_Instance_STIG_V3R1_Manual-xccdf.log} | 0 ..._2016_Instance_STIG_V3R1_Manual-xccdf.xml} | 292 +++++++++--------- ...lServer-2016-Instance-3.1.org.default.xml} | 4 +- ...11.xml => SqlServer-2016-Instance-3.1.xml} | 104 +++---- 5 files changed, 190 insertions(+), 212 deletions(-) rename source/StigData/Archive/SQL Server/{U_MS_SQL_Server_2016_Instance_STIG_V2R11_Manual-xccdf.log => U_MS_SQL_Server_2016_Instance_STIG_V3R1_Manual-xccdf.log} (100%) rename source/StigData/Archive/SQL Server/{U_MS_SQL_Server_2016_Instance_STIG_V2R11_Manual-xccdf.xml => U_MS_SQL_Server_2016_Instance_STIG_V3R1_Manual-xccdf.xml} (84%) rename source/StigData/Processed/{SqlServer-2016-Instance-2.11.org.default.xml => SqlServer-2016-Instance-3.1.org.default.xml} (81%) rename source/StigData/Processed/{SqlServer-2016-Instance-2.11.xml => SqlServer-2016-Instance-3.1.xml} (98%) diff --git a/CHANGELOG.md b/CHANGELOG.md index 4411017c4..84f9db37e 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,6 +2,8 @@ ## [Unreleased] +* Update Powerstig to parse\apply U_MS_SQL_Server_2016_Instance_V3R1_Manual_STIG [#1373](https://github.com/microsoft/PowerStig/issues/1373) + ## [4.22.0] - 2024-05-31 * Update Powerstig to parse/apply Microsoft Edge STIG - Ver 1, Rel 8 [#1350](https://github.com/microsoft/PowerStig/issues/1350) diff --git a/source/StigData/Archive/SQL Server/U_MS_SQL_Server_2016_Instance_STIG_V2R11_Manual-xccdf.log b/source/StigData/Archive/SQL Server/U_MS_SQL_Server_2016_Instance_STIG_V3R1_Manual-xccdf.log similarity index 100% rename from source/StigData/Archive/SQL Server/U_MS_SQL_Server_2016_Instance_STIG_V2R11_Manual-xccdf.log rename to source/StigData/Archive/SQL Server/U_MS_SQL_Server_2016_Instance_STIG_V3R1_Manual-xccdf.log diff --git a/source/StigData/Archive/SQL Server/U_MS_SQL_Server_2016_Instance_STIG_V2R11_Manual-xccdf.xml b/source/StigData/Archive/SQL Server/U_MS_SQL_Server_2016_Instance_STIG_V3R1_Manual-xccdf.xml similarity index 84% rename from source/StigData/Archive/SQL Server/U_MS_SQL_Server_2016_Instance_STIG_V2R11_Manual-xccdf.xml rename to source/StigData/Archive/SQL Server/U_MS_SQL_Server_2016_Instance_STIG_V3R1_Manual-xccdf.xml index a550a0d82..d98f1f765 100644 --- a/source/StigData/Archive/SQL Server/U_MS_SQL_Server_2016_Instance_STIG_V2R11_Manual-xccdf.xml +++ b/source/StigData/Archive/SQL Server/U_MS_SQL_Server_2016_Instance_STIG_V3R1_Manual-xccdf.xml @@ -1,4 +1,4 @@ -acceptedMS SQL Server 2016 Instance Security Technical Implementation GuideThis Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.DISASTIG.DOD.MILRelease: 11 Benchmark Date: 24 Jan 20243.4.1.229161.10.02I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>SRG-APP-000001-DB-000031<GroupDescription></GroupDescription>SQL6-D0-003600SQL Server must limit the number of concurrent sessions to an organization-defined number per user for all accounts and/or account types.<VulnDiscussion>Database management includes the ability to control the number of users and user sessions utilizing SQL Server. Unlimited concurrent connections to SQL Server could allow a successful Denial of Service (DoS) attack by exhausting connection resources; and a system can also fail or be degraded by an overload of legitimate users. Limiting the number of concurrent sessions per user is helpful in reducing these risks. This requirement addresses concurrent session control for a single account. It does not address concurrent sessions by a single user via multiple system accounts; and it does not deal with the total number of sessions across all accounts. @@ -6,7 +6,7 @@ The capability to limit the number of concurrent sessions per user must be confi The organization will need to define the maximum number of concurrent sessions by account type, by account, or a combination thereof. In deciding on the appropriate number, it is important to consider the work requirements of the various types of users. For example, 2 might be an acceptable limit for general users accessing the database via an application; but 10 might be too few for a database administrator using a database management GUI tool, where each query tab and navigation pane may count as a separate session. -(Sessions may also be referred to as connections or logons, which for the purposes of this requirement are synonyms.)</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93825V-79119CCI-000054Establish the limit(s) appropriate to the type(s) of user account accessing the SQL Server instance, and record them in the system documentation. Implement one or more logon triggers to enforce the limit(s), without exposing the dynamic management views to general users. +(Sessions may also be referred to as connections or logons, which for the purposes of this requirement are synonyms.)</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93825V-79119CCI-000054Establish the limit(s) appropriate to the type(s) of user account accessing the SQL Server instance, and record them in the system documentation. Implement one or more logon triggers to enforce the limit(s), without exposing the dynamic management views to general users. Example script below: @@ -18,7 +18,7 @@ BEGIN If (Select COUNT(1) from sys.dm_exec_sessions WHERE is_user_process = 1 AND original_login_name = ORIGINAL_LOGIN() ) > (CASE ORIGINAL_LOGIN() WHEN 'renamed_sa' THEN 40 /*i.e. the renamed system administrator SQL Login can have up to 40 concurrent logins... */ - WHEN 'domain/ima.dba' THEN 150 /*this is a busy DBA’s domain account */ + WHEN 'domain\ima.dba' THEN 150 /*this is a busy DBA’s domain account */ WHEN 'application1_login' THEN 6 /* this is a SQL login for an application */ WHEN 'application2_login' THEN 20 /* this is a SQL login for another application */ … @@ -30,7 +30,7 @@ If (Select COUNT(1) from sys.dm_exec_sessions WHERE is_user_process = 1 AND orig END END; -Reference: https://msdn.microsoft.com/en-us/library/ms189799.aspxReview the system documentation to determine whether any limits have been defined. If it does not, assume a limit of 10 for database administrators and 2 for all other users. +Reference: https://msdn.microsoft.com/en-us/library/ms189799.aspxReview the system documentation to determine whether any limits have been defined. If it does not, assume a limit of 10 for database administrators and 2 for all other users. If a mechanism other than a logon trigger is used, verify its correct operation by the appropriate means. If it does not work correctly, this is a finding. @@ -50,7 +50,7 @@ If triggers are listed, identify the trigger(s) limiting the number of concurren Examine the trigger source code for logical correctness and for compliance with the documented limit(s). If errors or variances exist, this is a finding. -Verify that the system does execute the trigger(s) each time a user session is established. If it does not operate correctly for all types of user, this is a finding.SRG-APP-000023-DB-000001<GroupDescription></GroupDescription>SQL6-D0-003700SQL Server must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals.<VulnDiscussion>Enterprise environments make account management for applications and databases challenging and complex. A manual process for account management functions adds the risk of a potential oversight or other error. Managing accounts for the same person in multiple places is inefficient and prone to problems with consistency and synchronization. +Verify that the system does execute the trigger(s) each time a user session is established. If it does not operate correctly for all types of user, this is a finding.SRG-APP-000023-DB-000001<GroupDescription></GroupDescription>SQL6-D0-003700SQL Server must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals.<VulnDiscussion>Enterprise environments make account management for applications and databases challenging and complex. A manual process for account management functions adds the risk of a potential oversight or other error. Managing accounts for the same person in multiple places is inefficient and prone to problems with consistency and synchronization. A comprehensive application account management process that includes automation helps to ensure that accounts designated as requiring attention are consistently and promptly addressed. @@ -128,7 +128,7 @@ SELECT name FROM sys.sql_logins WHERE type_desc = 'SQL_LOGIN' AND is_disabled = 0; -If any accounts listed by the query are not listed in the documentation, this is a finding.SRG-APP-000023-DB-000001<GroupDescription></GroupDescription>SQL6-D0-003800SQL Server must be configured to utilize the most-secure authentication method available.<VulnDiscussion>Enterprise environments make account management for applications and databases challenging and complex. A manual process for account management functions adds the risk of a potential oversight or other error. Managing accounts for the same person in multiple places is inefficient and prone to problems with consistency and synchronization. +If any accounts listed by the query are not listed in the documentation, this is a finding.SRG-APP-000023-DB-000001<GroupDescription></GroupDescription>SQL6-D0-003800SQL Server must be configured to utilize the most-secure authentication method available.<VulnDiscussion>Enterprise environments make account management for applications and databases challenging and complex. A manual process for account management functions adds the risk of a potential oversight or other error. Managing accounts for the same person in multiple places is inefficient and prone to problems with consistency and synchronization. A comprehensive application account management process that includes automation helps to ensure that accounts designated as requiring attention are consistently and promptly addressed. @@ -220,7 +220,7 @@ Default instance <FQDN> is the fully qualified domain name of the server. <port> is the TCP port number. -If the MSSQLSvc service is registered for any fully qualified domain names that do not match the current server, this may indicate the service account is shared across SQL Server instances. Review server documentation, if the sharing of service accounts across instances is not documented and authorized, this is a finding.SRG-APP-000033-DB-000084<GroupDescription></GroupDescription>SQL6-D0-003900SQL Server must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.<VulnDiscussion>Authentication with a DoD-approved PKI certificate does not necessarily imply authorization to access SQL Server. To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems, including databases, must be properly configured to implement access control policies. +If the MSSQLSvc service is registered for any fully qualified domain names that do not match the current server, this may indicate the service account is shared across SQL Server instances. Review server documentation, if the sharing of service accounts across instances is not documented and authorized, this is a finding.SRG-APP-000033-DB-000084<GroupDescription></GroupDescription>SQL6-D0-003900SQL Server must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.<VulnDiscussion>Authentication with a DoD-approved PKI certificate does not necessarily imply authorization to access SQL Server. To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems, including databases, must be properly configured to implement access control policies. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement. @@ -232,7 +232,7 @@ Review the permissions actually in place on the server. If the actual permissions do not match the documented requirements, this is a finding. -Use the supplemental file "Instance permissions assignments to logins and roles.sql."SRG-APP-000080-DB-000063<GroupDescription></GroupDescription>SQL6-D0-004000SQL Server must protect against a user falsely repudiating by ensuring all accounts are individual, unique, and not shared.<VulnDiscussion>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. +Use the supplemental file "Instance permissions assignments to logins and roles.sql."SRG-APP-000080-DB-000063<GroupDescription></GroupDescription>SQL6-D0-004000SQL Server must protect against a user falsely repudiating by ensuring all accounts are individual, unique, and not shared.<VulnDiscussion>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. @@ -258,7 +258,7 @@ Review contents of audit logs, traces and data tables to confirm that the identi 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.SRG-APP-000080-DB-000063<GroupDescription></GroupDescription>SQL6-D0-004100SQL Server must protect against a user falsely repudiating by ensuring the NT AUTHORITY SYSTEM account is not used for administration.<VulnDiscussion>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. +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.SRG-APP-000080-DB-000063<GroupDescription></GroupDescription>SQL6-D0-004100SQL Server must protect against a user falsely repudiating by ensuring the NT AUTHORITY SYSTEM account is not used for administration.<VulnDiscussion>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. @@ -296,7 +296,7 @@ If IsClustered returns 1, IsHadrEnabled returns 0, and any permissions have been If IsHadrEnabled returns 1 and any permissions have been granted to the Local System account beyond "CONNECT SQL", "CREATE AVAILABILITY GROUP", "ALTER ANY AVAILABILITY GROUP", "VIEW SERVER STATE", and "VIEW ANY DATABASE", this is a finding. If both IsClustered and IsHadrEnabled return 0 and any permissions have been granted to the Local System account beyond "CONNECT SQL" and "VIEW ANY DATABASE", this is a finding. -SRG-APP-000080-DB-000063<GroupDescription></GroupDescription>SQL6-D0-004200SQL Server must protect against a user falsely repudiating by ensuring only clearly unique Active Directory user accounts can connect to the instance.<VulnDiscussion>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. +SRG-APP-000080-DB-000063<GroupDescription></GroupDescription>SQL6-D0-004200SQL Server must protect against a user falsely repudiating by ensuring only clearly unique Active Directory user accounts can connect to the instance.<VulnDiscussion>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. @@ -323,7 +323,7 @@ Note: <name> represents the username portion of the login. For example, if If no account information is returned, this is not a finding. -If account information is returned, this is a finding.SRG-APP-000089-DB-000064<GroupDescription></GroupDescription>SQL6-D0-004300SQL Server must be configured to generate audit records for DoD-defined auditable events within all DBMS/database components.<VulnDiscussion>Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. +If account information is returned, this is a finding.SRG-APP-000089-DB-000064<GroupDescription></GroupDescription>SQL6-D0-004300SQL Server must be configured to generate audit records for DoD-defined auditable events within all DBMS/database components.<VulnDiscussion>Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within SQL Server (e.g., process, module). Certain specific application functionalities may be audited as well. The list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating audit records. @@ -357,7 +357,7 @@ JOIN sys.server_audits a ON s.audit_guid = a.audit_guid JOIN sys.server_audit_specification_details d ON s.server_specification_id = d.server_specification_id WHERE a.is_state_enabled = 1 -Compare the documentation to the list of generated audit events. If there are any missing events, this is a finding.SRG-APP-000090-DB-000065<GroupDescription></GroupDescription>SQL6-D0-004400SQL Server must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited.<VulnDiscussion>Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent or interfere with the auditing of critical events. +Compare the documentation to the list of generated audit events. If there are any missing events, this is a finding.SRG-APP-000090-DB-000065<GroupDescription></GroupDescription>SQL6-D0-004400SQL Server must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited.<VulnDiscussion>Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent or interfere with the auditing of critical events. Suppression of auditing could permit an adversary to evade detection. @@ -444,7 +444,7 @@ ON SRM.role_principal_id = R.principal_id WHERE sp.permission_name IN ('ALTER ANY SERVER AUDIT','CONTROL SERVER','ALTER ANY DATABASE','CREATE ANY DATABASE') OR R.name IN ('sysadmin','dbcreator') -If any of the logins, roles, or role memberships returned have permissions that are not documented, or the documented audit maintainers do not have permissions, this is a finding.SRG-APP-000091-DB-000325<GroupDescription></GroupDescription>SQL6-D0-004600SQL Server must generate audit records when successful/unsuccessful attempts to retrieve privileges/permissions occur.<VulnDiscussion>Under some circumstances, it may be useful to monitor who/what is reading privilege/permission/role information. Therefore, monitoring must be possible. DBMSs typically make such information available through views or functions. +If any of the logins, roles, or role memberships returned have permissions that are not documented, or the documented audit maintainers do not have permissions, this is a finding.SRG-APP-000091-DB-000325<GroupDescription></GroupDescription>SQL6-D0-004600SQL Server must generate audit records when successful/unsuccessful attempts to retrieve privileges/permissions occur.<VulnDiscussion>Under some circumstances, it may be useful to monitor who/what is reading privilege/permission/role information. Therefore, monitoring must be possible. DBMSs typically make such information available through views or functions. This requirement addresses explicit requests for privilege/permission/role membership information. It does not refer to the implicit retrieval of privileges/permissions/role memberships that SQL Server continually performs to determine if any and every action on the database is permitted. @@ -474,7 +474,7 @@ JOIN sys.server_audits a ON s.audit_guid = a.audit_guid JOIN sys.server_audit_specification_details d ON s.server_specification_id = d.server_specification_id WHERE a.is_state_enabled = 1 AND d.audit_action_name = 'SCHEMA_OBJECT_ACCESS_GROUP' -If the SCHEMA_OBJECT_ACCESS_GROUP is not returned in an active audit, this is a finding.SRG-APP-000092-DB-000208<GroupDescription></GroupDescription>SQL6-D0-004700SQL Server must initiate session auditing upon startup.<VulnDiscussion>Session auditing is for use when a user's activities are under investigation. To be sure of capturing all activity during those periods when session auditing is in use, it needs to be in operation for the whole time SQL Server is running.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93847V-79141CCI-001464Configure the SQL Audit(s) to automatically start during system start-up. +If the SCHEMA_OBJECT_ACCESS_GROUP is not returned in an active audit, this is a finding.SRG-APP-000092-DB-000208<GroupDescription></GroupDescription>SQL6-D0-004700SQL Server must initiate session auditing upon startup.<VulnDiscussion>Session auditing is for use when a user's activities are under investigation. To be sure of capturing all activity during those periods when session auditing is in use, it needs to be in operation for the whole time SQL Server is running.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93847V-79141CCI-001464Configure the SQL Audit(s) to automatically start during system start-up. ALTER SERVER AUDIT [<Server Audit Name>] WITH STATE = ON @@ -499,7 +499,7 @@ audit_file_path AS 'Current Audit File' FROM sys.dm_server_audit_status WHERE status_desc = 'STARTED' -All currently defined audits for the SQL server instance will be listed. If no audits are returned, this is a finding.SRG-APP-000101-DB-000044<GroupDescription></GroupDescription>SQL6-D0-005500SQL Server must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject.<VulnDiscussion>Information system auditing capability is critical for accurate forensic analysis. Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. To support analysis, some types of events will need information to be logged that exceeds the basic requirements of event type, time stamps, location, source, outcome, and user identity. If additional information is not available, it could negatively impact forensic investigations into user actions or other malicious events. +All currently defined audits for the SQL server instance will be listed. If no audits are returned, this is a finding.SRG-APP-000101-DB-000044<GroupDescription></GroupDescription>SQL6-D0-005500SQL Server must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject.<VulnDiscussion>Information system auditing capability is critical for accurate forensic analysis. Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. To support analysis, some types of events will need information to be logged that exceeds the basic requirements of event type, time stamps, location, source, outcome, and user identity. If additional information is not available, it could negatively impact forensic investigations into user actions or other malicious events. The organization must determine what additional information is required for complete analysis of the audited events. The additional information required is dependent on the type of information (e.g., sensitivity of the data and the environment within which it resides). At a minimum, the organization must employ either full-text recording of privileged commands or the individual identities of users of shared accounts, or both. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. @@ -513,7 +513,7 @@ If there are none specified, this is not a finding. If SQL Server Audit is in use, compare the audit specification(s) with the documented requirements. -If any such requirement is not satisfied by the audit specification(s) (or by supplemental, locally-deployed mechanisms), this is a finding.SRG-APP-000109-DB-000049<GroupDescription></GroupDescription>SQL6-D0-005600SQL Server must by default shut down upon audit failure, to include the unavailability of space for more audit log records; or must be configurable to shut down upon audit failure.<VulnDiscussion>It is critical that when SQL Server is at risk of failing to process audit logs as required, it takes action to mitigate the failure. Audit processing failures include: software/hardware errors; failures in the audit capturing mechanisms; and audit storage capacity being reached or exceeded. Responses to audit failure depend upon the nature of the failure mode. +If any such requirement is not satisfied by the audit specification(s) (or by supplemental, locally-deployed mechanisms), this is a finding.SRG-APP-000109-DB-000049<GroupDescription></GroupDescription>SQL6-D0-005600SQL Server must by default shut down upon audit failure, to include the unavailability of space for more audit log records; or must be configurable to shut down upon audit failure.<VulnDiscussion>It is critical that when SQL Server is at risk of failing to process audit logs as required, it takes action to mitigate the failure. Audit processing failures include: software/hardware errors; failures in the audit capturing mechanisms; and audit storage capacity being reached or exceeded. Responses to audit failure depend upon the nature of the failure mode. When the need for system availability does not outweigh the need for a complete audit trail, SQL Server should shut down immediately, rolling back all in-flight transactions. @@ -534,7 +534,7 @@ SELECT * FROM sys.server_audits; By observing the [name] and [is_state_enabled] columns, identify the row or rows in use. -If the [on_failure_desc] is "SHUTDOWN SERVER INSTANCE" on this/these row(s), this is not a finding. Otherwise, this is a finding.SRG-APP-000109-DB-000321<GroupDescription></GroupDescription>SQL6-D0-005700SQL Server must be configurable to overwrite audit log records, oldest first (First-In-First-Out - FIFO), in the event of unavailability of space for more audit log records.<VulnDiscussion>It is critical that when SQL Server is at risk of failing to process audit logs as required, it take action to mitigate the failure. Audit processing failures include; software/hardware errors; failures in the audit capturing mechanisms; and audit storage capacity being reached or exceeded. Responses to audit failure depend upon the nature of the failure mode. +If the [on_failure_desc] is "SHUTDOWN SERVER INSTANCE" on this/these row(s), this is not a finding. Otherwise, this is a finding.SRG-APP-000109-DB-000321<GroupDescription></GroupDescription>SQL6-D0-005700SQL Server must be configurable to overwrite audit log records, oldest first (First-In-First-Out - FIFO), in the event of unavailability of space for more audit log records.<VulnDiscussion>It is critical that when SQL Server is at risk of failing to process audit logs as required, it take action to mitigate the failure. Audit processing failures include; software/hardware errors; failures in the audit capturing mechanisms; and audit storage capacity being reached or exceeded. Responses to audit failure depend upon the nature of the failure mode. When availability is an overriding concern, approved actions in response to an audit failure are as follows: @@ -567,7 +567,7 @@ If no records are returned, this is a finding. If the "storage_type" is "APPLICATION LOG" or "SECURITY LOG", this is not a finding. If the "storage_type" is "FILE" and "max_rollover_files" is greater than zero, this is not a finding. Otherwise, this is a finding. -SRG-APP-000118-DB-000059<GroupDescription></GroupDescription>SQL6-D0-005900The audit information produced by SQL Server must be protected from unauthorized access, modification, and deletion.<VulnDiscussion>If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is difficult, if not impossible, to achieve. In addition, access to audit records provides information an attacker could potentially use to his or her advantage. +SRG-APP-000118-DB-000059<GroupDescription></GroupDescription>SQL6-D0-005900The audit information produced by SQL Server must be protected from unauthorized access, modification, and deletion.<VulnDiscussion>If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is difficult, if not impossible, to achieve. In addition, access to audit records provides information an attacker could potentially use to his or her advantage. To ensure the veracity of audit data, the information system and/or the application must protect audit information from any and all unauthorized access. This includes read, write, copy, etc. @@ -630,7 +630,7 @@ Auditors group (Read) SQL Server Service SID OR Service Account (Full Control) SQL Server SQL Agent Service SID OR Service Account, if SQL Server Agent is in use. (Read, Execute, Write) -If any less restrictive permissions are present (and not specifically justified and approved), this is a finding.SRG-APP-000122-DB-000203<GroupDescription></GroupDescription>SQL6-D0-006300SQL Server must protect its audit configuration from authorized and unauthorized access and modification.<VulnDiscussion>Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit data. +If any less restrictive permissions are present (and not specifically justified and approved), this is a finding.SRG-APP-000122-DB-000203<GroupDescription></GroupDescription>SQL6-D0-006300SQL Server must protect its audit configuration from authorized and unauthorized access and modification.<VulnDiscussion>Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit data. Applications providing tools to interface with audit data will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order make access decisions regarding the modification of audit tools. SQL Server is an application that does provide access to audit data. @@ -655,7 +655,7 @@ ON perm.grantee_principal_id = login.principal_id WHERE permission_name in ('ALTER ANY DATABASE AUDIT', 'ALTER ANY SERVER AUDIT', 'CONTROL SERVER') and login.name not like '##MS_%'; -If unauthorized accounts have these privileges, this is a finding.SRG-APP-000133-DB-000179<GroupDescription></GroupDescription>SQL6-D0-006500SQL Server must limit privileges to change software modules and links to software external to SQL Server.<VulnDiscussion>If the system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. +If unauthorized accounts have these privileges, this is a finding.SRG-APP-000133-DB-000179<GroupDescription></GroupDescription>SQL6-D0-006500SQL Server must limit privileges to change software modules and links to software external to SQL Server.<VulnDiscussion>If the system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. Accordingly, only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications. @@ -665,7 +665,7 @@ If any unauthorized users are granted modify rights or the owner is incorrect, t To determine the location for these instance-specific binaries, Launch SQL Server Management Studio (SSMS) >> Connect to the instance to be reviewed >> Right-click server name in Object Explorer >> Click Facets >> Select the Server facet >> Record the value for the "RootDirectory" facet property. -Navigate to the folder above, and review the "Binn" subdirectory.SRG-APP-000133-DB-000179<GroupDescription></GroupDescription>SQL6-D0-006600SQL Server must limit privileges to change software modules, to include stored procedures, functions and triggers, and links to software external to SQL Server.<VulnDiscussion>If the system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. +Navigate to the folder above, and review the "Binn" subdirectory.SRG-APP-000133-DB-000179<GroupDescription></GroupDescription>SQL6-D0-006600SQL Server must limit privileges to change software modules, to include stored procedures, functions and triggers, and links to software external to SQL Server.<VulnDiscussion>If the system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. Accordingly, only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications. @@ -683,7 +683,7 @@ To determine the location for these instance-specific binaries: Launch SQL Server Management Studio (SSMS) >> Connect to the instance to be reviewed >> Right-click server name in Object Explorer >> Click Facets >> Select the Server facet >> Record the value for the "RootDirectory" facet property -TIP: Use the Get-FileHash cmdlet shipped with PowerShell 5.0 to get the SHA-2 hash of one or more files.SRG-APP-000133-DB-000198<GroupDescription></GroupDescription>SQL6-D0-006700SQL Server software installation account must be restricted to authorized users.<VulnDiscussion>When dealing with change control issues, it should be noted any changes to the hardware, software, and/or firmware components of the information system and/or application can have significant effects on the overall security of the system. +TIP: Use the Get-FileHash cmdlet shipped with PowerShell 5.0 to get the SHA-2 hash of one or more files.SRG-APP-000133-DB-000198<GroupDescription></GroupDescription>SQL6-D0-006700SQL Server software installation account must be restricted to authorized users.<VulnDiscussion>When dealing with change control issues, it should be noted any changes to the hardware, software, and/or firmware components of the information system and/or application can have significant effects on the overall security of the system. If the system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. Accordingly, only qualified and authorized individuals must be allowed access to information system components for purposes of initiating changes, including upgrades and modifications. @@ -694,7 +694,7 @@ Configure SQL Server and OS settings and access controls to restrict user access sl "C:\program files\microsoft sql server\130\setup bootstrap\Log" Get-ChildItem -Recurse | Select-String -Pattern "LogonUser = " -If any accounts are shown that are not authorized in the system documentation, this is a finding.SRG-APP-000133-DB-000199<GroupDescription></GroupDescription>SQL6-D0-006800Database software, including DBMS configuration files, must be stored in dedicated directories, separate from the host OS and other applications.<VulnDiscussion>When dealing with change control issues, it should be noted any changes to the hardware, software, and/or firmware components of the information system and/or application can potentially have significant effects on the overall security of the system. +If any accounts are shown that are not authorized in the system documentation, this is a finding.SRG-APP-000133-DB-000199<GroupDescription></GroupDescription>SQL6-D0-006800Database software, including DBMS configuration files, must be stored in dedicated directories, separate from the host OS and other applications.<VulnDiscussion>When dealing with change control issues, it should be noted any changes to the hardware, software, and/or firmware components of the information system and/or application can potentially have significant effects on the overall security of the system. Multiple applications can provide a cumulative negative effect. A vulnerability and subsequent exploit to one application can lead to an exploit of other applications sharing the same security context. For example, an exploit to a web server process that leads to unauthorized administrative access to host system directories can most likely lead to a compromise of all applications hosted by the same system. Database software not installed using dedicated directories both threatens and is threatened by other hosted applications. Access controls defined for one application may by default provide access to the other application's database objects or directories. Any method that provides any level of separation of security context assists in the protection between applications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93875V-79169CCI-001499Re-install SQL Server application components using dedicated directories that are separate from the operating system. @@ -734,7 +734,7 @@ Examples: 2) The Operating System directory is "C:\Windows". The SQL RootDirectory is "C:\Windows\MSSQLSERVER\MSSQL". This is a finding. -3) The Operating System directory is "C:\Windows". The SQL RootDirectory is "D:\Program Files\Microsoft Office\MSSQLSERVER\MSSQL". The MSSQLSERVER directory is in the Microsoft Office directory, which indicates Microsoft Office is installed here. This is a finding.SRG-APP-000141-DB-000090<GroupDescription></GroupDescription>SQL6-D0-006900Default demonstration and sample databases, database objects, and applications must be removed.<VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). +3) The Operating System directory is "C:\Windows". The SQL RootDirectory is "D:\Program Files\Microsoft Office\MSSQLSERVER\MSSQL". The MSSQLSERVER directory is in the Microsoft Office directory, which indicates Microsoft Office is installed here. This is a finding.SRG-APP-000141-DB-000090<GroupDescription></GroupDescription>SQL6-D0-006900Default demonstration and sample databases, database objects, and applications must be removed.<VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). It is detrimental for software products to provide, or install by default, functionality exceeding requirements or mission objectives. Examples include, but are not limited to, installing advertising software, demonstrations, or browser plugins not related to requirements or providing a wide array of functionality, not required for every mission, that cannot be disabled. @@ -749,7 +749,7 @@ Northwind AdventureWorks WorldwideImporters -If any of these databases exist, this is a finding.SRG-APP-000141-DB-000091<GroupDescription></GroupDescription>SQL6-D0-007000Unused database components, DBMS software, and database objects must be removed.<VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). +If any of these databases exist, this is a finding.SRG-APP-000141-DB-000091<GroupDescription></GroupDescription>SQL6-D0-007000Unused database components, DBMS software, and database objects must be removed.<VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). It is detrimental for software products to provide, or install by default, functionality exceeding requirements or mission objectives. @@ -761,7 +761,7 @@ Click Start >> Type "SQL Server 2016 Installation Center" >> Launch Compare the feature listing against the required components listing. -If any features are installed, but are not required, this is a finding.SRG-APP-000141-DB-000092<GroupDescription></GroupDescription>SQL6-D0-007100Unused database components that are integrated in SQL Server and cannot be uninstalled must be disabled.<VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). +If any features are installed, but are not required, this is a finding.SRG-APP-000141-DB-000092<GroupDescription></GroupDescription>SQL6-D0-007100Unused database components that are integrated in SQL Server and cannot be uninstalled must be disabled.<VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). It is detrimental for software products to provide, or install by default, functionality exceeding requirements or mission objectives. @@ -779,7 +779,7 @@ Launch SQL Server Configuration Manager. If any components that are installed but are not required are not disabled, this is a finding. -If any required components are not installed, this is a finding.SRG-APP-000141-DB-000093<GroupDescription></GroupDescription>SQL6-D0-007200Access to xp_cmdshell must be disabled, unless specifically required and approved.<VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). +If any required components are not installed, this is a finding.SRG-APP-000141-DB-000093<GroupDescription></GroupDescription>SQL6-D0-007200Access to xp_cmdshell must be disabled, unless specifically required and approved.<VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). It is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. @@ -808,7 +808,7 @@ EXEC SP_CONFIGURE 'xp_cmdshell'; If the value of "config_value" is "0", this is not a finding. -Review the system documentation to determine whether the use of "xp_cmdshell" is required and approved. If it is not approved, this is a finding.SRG-APP-000141-DB-000093<GroupDescription></GroupDescription>SQL6-D0-007300Access to CLR code must be disabled or restricted, unless specifically required and approved.<VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). +Review the system documentation to determine whether the use of "xp_cmdshell" is required and approved. If it is not approved, this is a finding.SRG-APP-000141-DB-000093<GroupDescription></GroupDescription>SQL6-D0-007300Access to CLR code must be disabled or restricted, unless specifically required and approved.<VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). It is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. @@ -849,7 +849,7 @@ FROM sys.assemblies WHERE permission_set_desc != 'SAFE' AND is_user_defined = 1; -If any records are returned, review the system documentation to determine if the use of UNSAFE assemblies is approved. If it is not approved, this is a finding.SRG-APP-000141-DB-000093<GroupDescription></GroupDescription>SQL6-D0-007400Access to Non-Standard extended stored procedures must be disabled or restricted, unless specifically required and approved.<VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). +If any records are returned, review the system documentation to determine if the use of UNSAFE assemblies is approved. If it is not approved, this is a finding.SRG-APP-000141-DB-000093<GroupDescription></GroupDescription>SQL6-D0-007400Access to Non-Standard extended stored procedures must be disabled or restricted, unless specifically required and approved.<VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). It is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. @@ -881,7 +881,7 @@ SELECT X.xp_name, X.source_dll, O.is_ms_shipped FROM @xplist X JOIN sys.all_obje If any records are returned, review the system documentation to determine whether the use of Non-Standard extended stored procedures are required and approved. -If it is not approved, this is a finding.SRG-APP-000141-DB-000093<GroupDescription></GroupDescription>SQL6-D0-007500Access to linked servers must be disabled or restricted, unless specifically required and approved.<VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). It is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. Applications must adhere to the principles of least functionality by providing only essential capabilities. SQL Server may spawn additional external processes to execute procedures that are defined in the SQL Server but stored in external host files (external procedures). The spawned process used to execute the external procedure may operate within a different OS security context than SQL Server and provide unauthorized access to the host system. A linked server allows for access to distributed, heterogeneous queries against OLE DB data sources. After a linked server is created, distributed queries can be run against this server, and queries can join tables from more than one data source. If the linked server is defined as an instance of SQL Server, remote stored procedures can be executed. This access may be exploited by malicious users who have compromised the integrity of the SQL Server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93889V-79183CCI-000381Disable use of or remove any linked servers that are not authorized. +If it is not approved, this is a finding.SRG-APP-000141-DB-000093<GroupDescription></GroupDescription>SQL6-D0-007500Access to linked servers must be disabled or restricted, unless specifically required and approved.<VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). It is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. Applications must adhere to the principles of least functionality by providing only essential capabilities. SQL Server may spawn additional external processes to execute procedures that are defined in the SQL Server but stored in external host files (external procedures). The spawned process used to execute the external procedure may operate within a different OS security context than SQL Server and provide unauthorized access to the host system. A linked server allows for access to distributed, heterogeneous queries against OLE DB data sources. After a linked server is created, distributed queries can be run against this server, and queries can join tables from more than one data source. If the linked server is defined as an instance of SQL Server, remote stored procedures can be executed. This access may be exploited by malicious users who have compromised the integrity of the SQL Server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93889V-79183CCI-000381Disable use of or remove any linked servers that are not authorized. To remove a linked server and all associated logins run the following: @@ -905,7 +905,7 @@ JOIN sys.linked_logins l ON s.server_id = l.server_id LEFT JOIN sys.server_principals p ON l.local_principal_id = p.principal_id WHERE s.is_linked = 1 -Review the linked login mapping and check the remote name as it can impersonate sysadmin. If a login in the list is impersonating sysadmin and system documentation does not require this, it is a finding.SRG-APP-000142-DB-000094<GroupDescription></GroupDescription>SQL6-D0-007600SQL Server must be configured to prohibit or restrict the use of organization-defined protocols as defined in the PPSM CAL and vulnerability assessments.<VulnDiscussion>In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary protocols on information systems. +Review the linked login mapping and check the remote name as it can impersonate sysadmin. If a login in the list is impersonating sysadmin and system documentation does not require this, it is a finding.SRG-APP-000142-DB-000094<GroupDescription></GroupDescription>SQL6-D0-007600SQL Server must be configured to prohibit or restrict the use of organization-defined protocols as defined in the PPSM CAL and vulnerability assessments.<VulnDiscussion>In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary protocols on information systems. Applications are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., email and web services); however, doing so increases risk over limiting the services provided by any one component. @@ -915,7 +915,7 @@ SQL Server using protocols deemed unsafe is open to attack through those protoco If Named Pipes is enabled and not specifically required and authorized, this is a finding. -If any listed protocol is enabled but not authorized, this is a finding.SRG-APP-000142-DB-000094<GroupDescription></GroupDescription>SQL6-D0-007700SQL Server must be configured to prohibit or restrict the use of organization-defined ports, as defined in the PPSM CAL and vulnerability assessments.<VulnDiscussion>In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports on information systems. +If any listed protocol is enabled but not authorized, this is a finding.SRG-APP-000142-DB-000094<GroupDescription></GroupDescription>SQL6-D0-007700SQL Server must be configured to prohibit or restrict the use of organization-defined ports, as defined in the PPSM CAL and vulnerability assessments.<VulnDiscussion>In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports on information systems. Applications are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., email and web services); however, doing so increases risk over limiting the services provided by any one component. @@ -925,7 +925,7 @@ SQL Server using ports deemed unsafe is open to attack through those ports. This To determine whether SQL Server is configured to use a fixed port or dynamic ports, in the right-hand pane double-click on the TCP/IP entry, to open the Properties dialog. (The default fixed port is 1433.) -If these are in conflict with PPSM guidance, and not explained and approved in the system documentation, this is a finding.SRG-APP-000148-DB-000103<GroupDescription></GroupDescription>SQL6-D0-007800SQL Server must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).<VulnDiscussion>To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system. +If these are in conflict with PPSM guidance, and not explained and approved in the system documentation, this is a finding.SRG-APP-000148-DB-000103<GroupDescription></GroupDescription>SQL6-D0-007800SQL Server must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).<VulnDiscussion>To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system. Organizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and any processes acting on behalf of users) must be uniquely identified and authenticated for all accesses, except the following: @@ -940,24 +940,29 @@ If accounts are determined to be shared, determine if individuals are first indi 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. -If accounts are determined to be shared, determine if they are directly accessible to end users. If so, this is a finding.SRG-APP-000164-DB-000401<GroupDescription></GroupDescription>SQL6-D0-007900If DBMS authentication using passwords is employed, SQL Server must enforce the DoD standards for password complexity and lifetime.<VulnDiscussion>OS/enterprise authentication and identification must be used (SRG-APP-000023-DB-000001). Native DBMS authentication may be used only when circumstances make it unavoidable; and must be documented and AO-approved. +If accounts are determined to be shared, determine if they are directly accessible to end users. If so, this is a finding.SRG-APP-000164-DB-000401<GroupDescription></GroupDescription>SQL6-D0-007900If DBMS authentication using passwords is employed, SQL Server must enforce the DOD standards for password complexity and lifetime.<VulnDiscussion>Windows Authentication is the default authentication mode and is much more secure than SQL Server Authentication. Windows Authentication uses Kerberos security protocol, provides password policy enforcement with regard to complexity validation for strong passwords, provides support for account lockout, and supports password expiration. A connection made using Windows Authentication is sometimes called a trusted connection, because SQL Server trusts the credentials provided by Windows. + +By using Windows Authentication, Windows groups can be created at the domain level, and a login can be created on SQL Server for the entire group. Managing access at the domain level can simplify account administration. + +OS/enterprise authentication and identification must be used (SRG-APP-000023-DB-000001). Native SQL Server authentication may be used only when circumstances make it unavoidable and must be documented and Authorizing Official (AO)-approved. -The DoD standard for authentication is DoD-approved PKI certificates. Authentication based on User ID and Password may be used only when it is not possible to employ a PKI certificate, and requires AO approval. +The DOD standard for authentication is DOD-approved PKI certificates. Authentication based on User ID and Password may be used only when it is not possible to employ a PKI certificate and requires AO approval. -In such cases, the DoD standards for password complexity and lifetime must be implemented. DBMS products that can inherit the rules for these from the operating system or access control program (e.g., Microsoft Active Directory) must be configured to do so. For other DBMSs, the rules must be enforced using available configuration parameters or custom code.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93897V-79191CCI-000192Configure the SQL Server operating system and SQL Server logins for compliance. +In such cases, the DOD standards for password complexity and lifetime must be implemented. DBMS products that can inherit the rules for these from the operating system or access control program (e.g., Microsoft Active Directory) must be configured to do so. For other DBMSs, the rules must be enforced using available configuration parameters or custom code.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93897V-79191CCI-004066When possible, use Windows authentication. + +If using SQL Server authentication, configure the SQL Server operating system and SQL Server logins for compliance. -1. Ensure the password complexity requirements for the corresponding DISA Windows Server Security Technical Implementation Guide are met on the server where the SQL Server Instance is installed. +1. Ensure the password complexity requirements for the corresponding DISA Windows Server STIG are met on the server where the SQL Server Instance is installed. 2. Ensure SQL Server is configured to inherit password complexity rules from the operating system for SQL logins. Ensure check of policy and expiration are enforced when SQL logins are created. -CREATE LOGIN <login_name> WITH PASSWORD= <enterStrongPasswordHere>, CHECK_EXPIRATION = ON, CHECK_POLICY = ON; -Check for use of SQL Server Authentication: +CREATE LOGIN <login_name> WITH PASSWORD= <enterStrongPasswordHere>, CHECK_EXPIRATION = ON, CHECK_POLICY = ON;Check for use of SQL Server Authentication: SELECT CASE SERVERPROPERTY('IsIntegratedSecurityOnly') WHEN 1 THEN 'Windows Authentication' WHEN 0 THEN 'SQL Server Authentication' END as [Authentication Mode] -If the returned value in the "[Authentication Mode]" column is "Windows Authentication", this is not a finding. +If the returned value in the "Authentication Mode" column is "Windows Authentication", this is not a finding. -SQL Server should be configured to inherit password complexity and password lifetime rules from the operating system. +If the returned value in the "Authentication Mode" column is "SQL Server Authentication", SQL Server should be configured to inherit password complexity and password lifetime rules from the operating system. Review SQL Server to ensure logons are created with respect to the complexity settings and password lifetime rules by running the statement: @@ -968,19 +973,17 @@ Review any accounts returned by the query other than the disabled SA account, ## If any account does not have both "is_expiration_checked" and "is_policy_checked" equal to “1”, this is a finding. -Review the Operating System settings relating to password complexity. +Review the operating system settings relating to password complexity. -Determine whether the following rules are enforced. If any are not, this is a finding. +To check the server operating system for password complexity: -Check the server operating system for password complexity: +Navigate to Start >> All Programs >> Administrative Tools >> Local Security Policy, and to review the local policies on the machine, go to Account Policy >> Password Policy. -Navigate to Start >> All Programs >> Administrative Tools >> Local Security Policy, and to review the local policies on the machine, go to Account Policy >> Password Policy:. - -Ensure the DISA Windows Password Policy is set on the SQL Server member server.SRG-APP-000164-DB-000401<GroupDescription></GroupDescription>SQL6-D0-008000Contained databases must use Windows principals.<VulnDiscussion>OS/enterprise authentication and identification must be used (SRG-APP-000023-DB-000001). Native DBMS authentication may be used only when circumstances make it unavoidable; and must be documented and AO-approved. +Ensure the DISA Windows Password Policy is set on the SQL Server member server. If any are not, this is a finding.SRG-APP-000164-DB-000401<GroupDescription></GroupDescription>SQL6-D0-008000Contained databases must use Windows principals.<VulnDiscussion>OS/enterprise authentication and identification must be used (SRG-APP-000023-DB-000001). Native DBMS authentication may be used only when circumstances make it unavoidable, and must be documented and Authorizing Official (AO)-approved. -The DoD standard for authentication is DoD-approved PKI certificates. Authentication based on User ID and Password may be used only when it is not possible to employ a PKI certificate, and requires AO approval. +The DOD standard for authentication is DOD-approved PKI certificates. Authentication based on User ID and Password may be used only when it is not possible to employ a PKI certificate, and requires AO approval. -In such cases, the DoD standards for password complexity and lifetime must be implemented. DBMS products that can inherit the rules for these from the operating system or access control program (e.g., Microsoft Active Directory) must be configured to do so. For other DBMSs, the rules must be enforced using available configuration parameters or custom code.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93899V-79193CCI-000192Configure the SQL Server contained databases to have users originating from Windows principals. Remove any users not created from Windows principals.Execute the following query to determine if Contained Databases are used: +In such cases, the DOD standards for password complexity and lifetime must be implemented. DBMS products that can inherit the rules for these from the operating system or access control program (e.g., Microsoft Active Directory) must be configured to do so. For other DBMSs, the rules must be enforced using available configuration parameters or custom code.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93899V-79193CCI-004066Configure the SQL Server contained databases to have users originating from Windows principals. Remove any users not created from Windows principals.Execute the following query to determine if contained databases are used: SELECT * FROM sys.databases WHERE containment = 1 @@ -988,7 +991,7 @@ If any records are returned. Check the server documentation for a list of author EXEC sp_MSforeachdb 'USE [?]; SELECT DB_NAME() AS DatabaseName, * FROM sys.database_principals WHERE authentication_type = 2' -If any records are returned, this is a finding.SRG-APP-000172-DB-000075<GroupDescription></GroupDescription>SQL6-D0-008200If passwords are used for authentication, SQL Server must transmit only encrypted representations of passwords.<VulnDiscussion>The DoD standard for authentication is DoD-approved PKI certificates. +If any records are returned, this is a finding.SRG-APP-000172-DB-000075<GroupDescription></GroupDescription>SQL6-D0-008200If passwords are used for authentication, SQL Server must transmit only encrypted representations of passwords.<VulnDiscussion>The DoD standard for authentication is DoD-approved PKI certificates. Authentication based on User ID and Password may be used only when it is not possible to employ a PKI certificate, and requires AO approval. @@ -1040,7 +1043,7 @@ For clustered instances, the Certificate will NOT be shown in the SQL Server Con 5. This check needs to be run on each node of the cluster. If any nodes have a certificate in use by SQL that is not issued or approved by DoD, this is a finding. -SRG-APP-000172-DB-000075<GroupDescription></GroupDescription>SQL6-D0-008300Confidentiality of information during transmission is controlled through the use of an approved TLS version.<VulnDiscussion>Transport Layer Security (TLS) encryption is a required security setting as a number of known vulnerabilities have been reported against Secure Sockets Layer (SSL) and earlier versions of TLS. Encryption of private information is essential to ensuring data confidentiality. If private information is not encrypted, it can be intercepted and easily read by an unauthorized party. SQL Server must use a FIPS-approved minimum TLS version 1.2, and all non-FIPS-approved SSL and TLS versions must be disabled. NIST SP 800-52 Rev.2 specifies the preferred configurations for government systems. +SRG-APP-000172-DB-000075<GroupDescription></GroupDescription>SQL6-D0-008300Confidentiality of information during transmission is controlled through the use of an approved TLS version.<VulnDiscussion>Transport Layer Security (TLS) encryption is a required security setting as a number of known vulnerabilities have been reported against Secure Sockets Layer (SSL) and earlier versions of TLS. Encryption of private information is essential to ensuring data confidentiality. If private information is not encrypted, it can be intercepted and easily read by an unauthorized party. SQL Server must use a FIPS-approved minimum TLS version 1.2, and all non-FIPS-approved SSL and TLS versions must be disabled. NIST SP 800-52 Rev.2 specifies the preferred configurations for government systems. References: TLS Support 1.2 for SQL Server: https://support.microsoft.com/en-us/kb/3135244 @@ -1144,7 +1147,7 @@ HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3 Under each key, verify a REG_DWORD value of "1" for "DisabledByDefault" and a value of "0" for "Enabled" for both Client and Server subkeys. If any of the respective registry paths are non-existent or contain values other than specified above, this is a finding. If Vendor documentation supporting the configuration is provided, reduce this finding to a CAT 3. -SRG-APP-000176-DB-000068<GroupDescription></GroupDescription>SQL6-D0-008400SQL Server must enforce authorized access to all PKI private keys stored/utilized by SQL Server.<VulnDiscussion>The DoD standard for authentication is DoD-approved PKI certificates. PKI certificate-based authentication is performed by requiring the certificate holder to cryptographically prove possession of the corresponding private key. +SRG-APP-000176-DB-000068<GroupDescription></GroupDescription>SQL6-D0-008400SQL Server must enforce authorized access to all PKI private keys stored/utilized by SQL Server.<VulnDiscussion>The DoD standard for authentication is DoD-approved PKI certificates. PKI certificate-based authentication is performed by requiring the certificate holder to cryptographically prove possession of the corresponding private key. If the private key is stolen, an attacker can use the private key(s) to impersonate the certificate holder. In cases where SQL Server-stored private keys are used to authenticate SQL Server to the system’s clients, loss of the corresponding private keys would allow an attacker to successfully perform undetected man in the middle attacks against SQL Server system and its clients. @@ -1164,7 +1167,7 @@ Ensure that "System cryptography: Use FIPS-compliant algorithms for encryption, If "System cryptography: Use FIPS-compliant algorithms for encryption, hashing, and signing" is not enabled, this is a finding. -For more information, see https://support.microsoft.com/en-us/kb/3141890.SRG-APP-000179-DB-000114<GroupDescription></GroupDescription>SQL6-D0-008700SQL Server must use NIST FIPS 140-2 or 140-3 validated cryptographic modules for cryptographic operations.<VulnDiscussion>Use of weak or not validated cryptographic algorithms undermines the purposes of utilizing encryption and digital signatures to protect data. Weak algorithms can be easily broken, and not validated cryptographic modules may not implement algorithms correctly. Unapproved cryptographic modules or algorithms should not be relied on for authentication, confidentiality, or integrity. Weak cryptography could allow an attacker to gain access to, and modify data stored in, the database as well as the administration settings of SQL Server. +For more information, see https://support.microsoft.com/en-us/kb/3141890.SRG-APP-000179-DB-000114<GroupDescription></GroupDescription>SQL6-D0-008700SQL Server must use NIST FIPS 140-2 or 140-3 validated cryptographic modules for cryptographic operations.<VulnDiscussion>Use of weak or not validated cryptographic algorithms undermines the purposes of utilizing encryption and digital signatures to protect data. Weak algorithms can be easily broken, and not validated cryptographic modules may not implement algorithms correctly. Unapproved cryptographic modules or algorithms should not be relied on for authentication, confidentiality, or integrity. Weak cryptography could allow an attacker to gain access to, and modify data stored in, the database as well as the administration settings of SQL Server. Applications, including DBMSs, utilizing cryptography are required to use approved NIST FIPS 140-2 or 140-3 validated cryptographic modules that meet the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. @@ -1182,7 +1185,7 @@ In the dialog box that appears, if the radio buttons are active, click "Enabled" If, in the "Security Setting" column, the value is "Disabled," this is a finding. -https://support.microsoft.com/en-us/kb/955720SRG-APP-000180-DB-000115<GroupDescription></GroupDescription>SQL6-D0-008800SQL Server must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).<VulnDiscussion>Non-organizational users include all information system users other than organizational users, which include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors, guest researchers, individuals from allied nations). +https://support.microsoft.com/en-us/kb/955720SRG-APP-000180-DB-000115<GroupDescription></GroupDescription>SQL6-D0-008800SQL Server must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).<VulnDiscussion>Non-organizational users include all information system users other than organizational users, which include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors, guest researchers, individuals from allied nations). Non-organizational users must be uniquely identified and authenticated for all accesses other than those accesses explicitly identified and documented by the organization when related to the use of anonymous access, such as accessing a web server. @@ -1198,7 +1201,7 @@ If accounts are determined to be shared, determine if individuals are first indi If the documentation indicates that this is a public-facing, read-only (from the point of view of public users) database that does not require individual authentication, this is not a finding. -If non-organizational users are not uniquely identified and authenticated, this is a finding.SRG-APP-000224-DB-000384<GroupDescription></GroupDescription>SQL6-D0-009200SQL Server must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values.<VulnDiscussion>One class of man-in-the-middle, or session hijacking, attack involves the adversary guessing at valid session identifiers based on patterns in identifiers already known. +If non-organizational users are not uniquely identified and authenticated, this is a finding.SRG-APP-000224-DB-000384<GroupDescription></GroupDescription>SQL6-D0-009200SQL Server must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values.<VulnDiscussion>One class of man-in-the-middle, or session hijacking, attack involves the adversary guessing at valid session identifiers based on patterns in identifiers already known. The preferred technique for thwarting guesses at Session IDs is the generation of unique session identifiers using a FIPS 140-2 or FIPS 140-3 approved random number generator. @@ -1208,7 +1211,7 @@ Click Start >> Type "Local Security Policy" >> Press Enter >> Click Start >> Type "Local Security Policy" >> Press Enter >> Expand "Local Policies" >> Select "Security Options" >> Locate "System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing." -If the Security Setting for this option is "Disabled", this is a finding.SRG-APP-000231-DB-000154<GroupDescription></GroupDescription>SQL6-D0-009500SQL Server must protect the confidentiality and integrity of all information at rest.<VulnDiscussion>This control is intended to address the confidentiality and integrity of information at rest in non-mobile devices and covers user information and system information. Information at rest refers to the state of information when it is located on a secondary storage device (e.g., disk drive, tape drive) within an organizational information system. Applications and application users generate information throughout the course of their application use. +If the Security Setting for this option is "Disabled", this is a finding.SRG-APP-000231-DB-000154<GroupDescription></GroupDescription>SQL6-D0-009500SQL Server must protect the confidentiality and integrity of all information at rest.<VulnDiscussion>This control is intended to address the confidentiality and integrity of information at rest in non-mobile devices and covers user information and system information. Information at rest refers to the state of information when it is located on a secondary storage device (e.g., disk drive, tape drive) within an organizational information system. Applications and application users generate information throughout the course of their application use. User data generated, as well as application-specific configuration data, needs to be protected. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate. @@ -1242,31 +1245,31 @@ ORDER BY [Database Name] ; For each user database where encryption is required, verify that encryption is in effect. If not, this is a finding. -Verify that there are physical security measures, operating system access control lists and organizational controls appropriate to the sensitivity level of the data in the database(s). If not, this is a finding.SRG-APP-000231-DB-000154<GroupDescription></GroupDescription>SQL6-D0-009600The Service Master Key must be backed up, stored offline and off-site.<VulnDiscussion>Backup and recovery of the Service Master Key may be critical to the complete recovery of the database. Creating this backup should be one of the first administrative actions performed on the server. Not having this key can lead to loss of data during recovery.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93913V-79207CCI-001199Document and implement procedures to safely back up and store the Service Master Key. Include in the procedures methods to establish evidence of backup and storage, and careful, restricted access and restoration of the Service Master Key. Also, include provisions to store the key off-site. +Verify that there are physical security measures, operating system access control lists and organizational controls appropriate to the sensitivity level of the data in the database(s). If not, this is a finding.SRG-APP-000231-DB-000154<GroupDescription></GroupDescription>SQL6-D0-009600The Service Master Key must be backed up and stored in a secure location that is not on the SQL Server.<VulnDiscussion>Backup and recovery of the Service Master Key may be critical to the complete recovery of the database. Creating this backup should be one of the first administrative actions performed on the server. Not having this key can lead to loss of data during recovery.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93913V-79207CCI-001199Document and implement procedures to safely back up and store the Service Master Key in a secure location that is not on the SQL Server. Include in the procedures methods to establish evidence of backup and storage, and careful, restricted access and restoration of the Service Master Key. BACKUP SERVICE MASTER KEY TO FILE = 'path_to_file' ENCRYPTION BY PASSWORD = 'password'; -As this requires a password, take care to ensure it is not exposed to unauthorized persons or stored as plain text.Review procedures for, and evidence of backup of, the Server Service Master Key in the System Security Plan. - -If the procedures or evidence does not exist, this is a finding. +As this requires a password, take care to ensure it is not exposed to unauthorized persons or stored as plain text.Review procedures for and evidence of backup of the Server Service Master Key in the System Security Plan. -If the procedures do not indicate offline and off-site storage of the Service Master Key, this is a finding. - -If procedures do not indicate access restrictions to the Service Master Key backup, this is a finding.SRG-APP-000231-DB-000154<GroupDescription></GroupDescription>SQL6-D0-009700The Master Key must be backed up, stored offline and off-site.<VulnDiscussion>Backup and recovery of the Master Key may be critical to the complete recovery of the database. Not having this key can lead to loss of data during recovery.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93915V-79209CCI-001199Document and implement procedures to safely back up and store the Master Key. Include in the procedures methods to establish evidence of backup and storage, and careful, restricted access and restoration of the Master Key. Also, include provisions to store the key off-site. +If the procedures or evidence does not exist, this is a finding. +If the procedures do not indicate that a backup of the Service Master Key is stored in a secure location that is not on the SQL Server, this is a finding. + +If procedures do not indicate access restrictions to the Service Master Key backup, this is a finding.SRG-APP-000231-DB-000154<GroupDescription></GroupDescription>SQL6-D0-009700The Master Key must be backed up and stored in a secure location that is not on the SQL Server.<VulnDiscussion>Backup and recovery of the Master Key may be critical to the complete recovery of the database. Not having this key can lead to loss of data during recovery.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93915V-79209CCI-001199Document and implement procedures to safely back up and store the Master Key in a secure location that is not on the SQL Server. Include in the procedures methods to establish evidence of backup and storage, and careful, restricted access and restoration of the Master Key. + BACKUP MASTER KEY TO FILE = 'path_to_file' ENCRYPTION BY PASSWORD = 'password'; -As this requires a password, take care to ensure it is not exposed to unauthorized persons or stored as plain text.If the application owner and Authorizing Official have determined that encryption of data at rest is not required, this is not a finding. +As this requires a password, take care to ensure it is not exposed to unauthorized persons or stored as plain text.If the application owner and authorizing official have determined that encryption of data at rest is not required, this is not a finding. -Review procedures for, and evidence of backup of, the Master Key in the System Security Plan. +Review procedures for and evidence of backup of the Master Key in the System Security Plan. If the procedures or evidence does not exist, this is a finding. -If the procedures do not indicate offline and off-site storage of the Master Key, this is a finding. - -If procedures do not indicate access restrictions to the Master Key backup, this is a finding.SRG-APP-000243-DB-000373<GroupDescription></GroupDescription>SQL6-D0-009800SQL Server must prevent unauthorized and unintended information transfer via shared system resources.<VulnDiscussion>The purpose of this control is to prevent information, including encrypted representations of information, produced by the actions of a prior user/role (or the actions of a process acting on behalf of a prior user/role) from being available to any current user/role (or current process) that obtains access to a shared system resource (e.g., registers, main memory, secondary storage) after the resource has been released back to the information system. Control of information in shared resources is also referred to as object reuse.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93917V-79211CCI-001090Configure SQL Server to effectively protect the private resources of one process or user from unauthorized access by another user or process. +If the procedures do not indicate that a backup of the Master Key is stored in a secure location that is not on the SQL Server, this is a finding. + +If procedures do not indicate access restrictions to the Master Key backup, this is a finding.SRG-APP-000243-DB-000373<GroupDescription></GroupDescription>SQL6-D0-009800SQL Server must prevent unauthorized and unintended information transfer via shared system resources.<VulnDiscussion>The purpose of this control is to prevent information, including encrypted representations of information, produced by the actions of a prior user/role (or the actions of a process acting on behalf of a prior user/role) from being available to any current user/role (or current process) that obtains access to a shared system resource (e.g., registers, main memory, secondary storage) after the resource has been released back to the information system. Control of information in shared resources is also referred to as object reuse.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93917V-79211CCI-001090Configure SQL Server to effectively protect the private resources of one process or user from unauthorized access by another user or process. sp_configure 'show advanced options', 1; GO @@ -1290,15 +1293,21 @@ If "value_in_use" is set to "1" this is not a finding. If "value_in_use" is set to "0" this is a finding. NOTE: Enabling this feature may impact performance on highly active SQL Server instances. If an exception justifying setting SQL Server Residual Information Protection (RIP) to disabled (value_in_use set to "0") has been documented and approved, then this may be downgraded to a CAT III finding. -SRG-APP-000243-DB-000373<GroupDescription></GroupDescription>SQL6-D0-009900SQL Server must prevent unauthorized and unintended information transfer via Instant File Initialization (IFI).<VulnDiscussion>The purpose of this control is to prevent information, including encrypted representations of information, produced by the actions of a prior user/role (or the actions of a process acting on behalf of a prior user/role) from being available to any current user/role (or current process) that obtains access to a shared system resource (e.g., registers, main memory, secondary storage) after the resource has been released back to the information system. Control of information in shared resources is also referred to as object reuse.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93919V-79213CCI-001090If IFI is not documented as being required, disable instant file initialization for the instance of SQL Server by removing the SQL Service SID and/or service account from the "Perform volume maintenance tasks" Local Rights Assignment.Review the system documentation to determine if Instant File Initialization (IFI) is required. +SRG-APP-000243-DB-000373<GroupDescription></GroupDescription>SQL6-D0-009900SQL Server must prevent unauthorized and unintended information transfer via Instant File Initialization (IFI).<VulnDiscussion>The purpose of this control is to prevent information, including encrypted representations of information, produced by the actions of a prior user/role (or the actions of a process acting on behalf of a prior user/role) from being available to any current user/role (or current process) that obtains access to a shared system resource (e.g., registers, main memory, secondary storage) after the resource has been released back to the information system. Control of information in shared resources is also referred to as object reuse. -If IFI is documented as required, this is not a finding. +When Instant File Initialization (IFI) is in use, the deleted disk content is overwritten only as new data is written to the files. For this reason, the deleted content might be accessed by an unauthorized principal until some other data writes on that specific area of the data file.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93919V-79213CCI-001090If IFI is not documented as being required, disable instant file initialization for the instance of SQL Server by removing the SQL Service SID and/or service account from the "Perform volume maintenance tasks" Local Rights Assignment.Review system configuration to determine whether IFI support has been enabled (by default in SQL Server 2016). -Review system configuration to determine whether IFI support has been enabled (by default in SQL Server 2016). +Start >> Control Panel >> System and Security >> Administrative Tools >> Local Security Policy >> Local Policies >> User Rights Assignment >> Perform volume maintenance tasks -Start >> Control Panel >> Administrative Tools >> Local Security Policy >> Local Policies >> User Rights Assignment +The default SQL service account for a default instance is NT SERVICE\MSSQLSERVER or for a named instance is NT SERVICE\MSSQL$InstanceName. -If the SQL Service SID (Default instance: NT SERVICE\MSSQLSERVER. Named instance: NT SERVICE\MSSQL$InstanceName) has been granted "Perform volume maintenance tasks" Local Rights Assignment and if it is not documented in the system documentation, this is a finding.SRG-APP-000243-DB-000374<GroupDescription></GroupDescription>SQL6-D0-010000Access to database files must be limited to relevant processes and to authorized, administrative users.<VulnDiscussion>SQL Server must prevent unauthorized and unintended information transfer via shared system resources. Permitting only SQL Server processes and authorized, administrative users to have access to the files where the database resides helps ensure that those files are not shared inappropriately and are not open to backdoor access and manipulation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93921V-79215CCI-001090Remove any unauthorized permission grants from SQL Server data, log, and backup directories. +If the SQL service account or SQL service SID has been granted "Perform volume maintenance tasks" Local Rights Assignment, this means that Instant File Initialization (IFI) is enabled. + +Review the system documentation to determine if Instant File Initialization (IFI) is required. + +If IFI is enabled but not documented as required, this is a finding. + +If IFI is not enabled, this is not a finding.SRG-APP-000243-DB-000374<GroupDescription></GroupDescription>SQL6-D0-010000Access to database files must be limited to relevant processes and to authorized, administrative users.<VulnDiscussion>SQL Server must prevent unauthorized and unintended information transfer via shared system resources. Permitting only SQL Server processes and authorized, administrative users to have access to the files where the database resides helps ensure that those files are not shared inappropriately and are not open to backdoor access and manipulation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93921V-79215CCI-001090Remove any unauthorized permission grants from SQL Server data, log, and backup directories. 1) On the "Security" tab, highlight the user entry. 2) Click "Remove".Review the permissions granted to users by the operating system/file system on the database files, database log files, and database backup files. @@ -1327,7 +1336,7 @@ https://aka.ms/sql-service-sids Additional permission requirements, including full directory permissions and operating system rights for SQL Server, are documented at: https://aka.ms/sqlservicepermissions -If any additional permissions are granted but not documented as authorized, this is a finding.SRG-APP-000267-DB-000163<GroupDescription></GroupDescription>SQL6-D0-010100SQL Server must reveal detailed error messages only to the ISSO, ISSM, SA, and DBA.<VulnDiscussion>If SQL Server provides too much information in error logs and administrative messages to the screen, this could lead to compromise. The structure and content of error messages need to be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements. +If any additional permissions are granted but not documented as authorized, this is a finding.SRG-APP-000267-DB-000163<GroupDescription></GroupDescription>SQL6-D0-010100SQL Server must reveal detailed error messages only to the ISSO, ISSM, SA, and DBA.<VulnDiscussion>If SQL Server provides too much information in error logs and administrative messages to the screen, this could lead to compromise. The structure and content of error messages need to be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements. Some default DBMS error messages can contain information that could aid an attacker in, among others things, identifying the database type, host address, or state of the database. Custom errors may contain sensitive customer information. @@ -1354,7 +1363,7 @@ If any non-authorized users have access to the SQL Server Error Log located at P In addition, the SQL Server Error Log is also located at Program Files\Microsoft SQL Server\MSSQL.n\MSSQL\LOG\. Review the permissions on this folder to ensure that only authorized users are listed. -If any non-authorized users have access to the SQL Server Error Log in SQL Server Management Studio, this is a finding.SRG-APP-000340-DB-000304<GroupDescription></GroupDescription>SQL6-D0-010400SQL Server must prevent non-privileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures.<VulnDiscussion>Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges. +If any non-authorized users have access to the SQL Server Error Log in SQL Server Management Studio, this is a finding.SRG-APP-000340-DB-000304<GroupDescription></GroupDescription>SQL6-D0-010400SQL Server must prevent non-privileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures.<VulnDiscussion>Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges. System documentation should include a definition of the functionality considered privileged. @@ -1448,7 +1457,7 @@ The CONTROL SERVER permission is similar but not identical to the sysadmin fixed Ensure only the documented and approved logins have privileged functions in SQL Server. -If the current configuration does not match the documented baseline, this is a finding.SRG-APP-000342-DB-000302<GroupDescription></GroupDescription>SQL6-D0-010500Use of credentials and proxies must be restricted to necessary cases only.<VulnDiscussion>In certain situations, to provide required functionality, a DBMS needs to execute internal logic (stored procedures, functions, triggers, etc.) and/or external code modules with elevated privileges. However, if the privileges required for execution are at a higher level than the privileges assigned to organizational users invoking the functionality applications/programs, those users are indirectly provided with greater privileges than assigned by organizations. +If the current configuration does not match the documented baseline, this is a finding.SRG-APP-000342-DB-000302<GroupDescription></GroupDescription>SQL6-D0-010500Use of credentials and proxies must be restricted to necessary cases only.<VulnDiscussion>In certain situations, to provide required functionality, a DBMS needs to execute internal logic (stored procedures, functions, triggers, etc.) and/or external code modules with elevated privileges. However, if the privileges required for execution are at a higher level than the privileges assigned to organizational users invoking the functionality applications/programs, those users are indirectly provided with greater privileges than assigned by organizations. Privilege elevation must be utilized only where necessary and protected from misuse.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93927V-79221CCI-002233Remove any SQL Agent Proxy accounts and credentials that are not authorized. @@ -1469,17 +1478,7 @@ JOIN msdb.dbo.sysproxies P ON C.credential_id = P.credential_id WHERE P.enabled = 1 GO -If any Credentials or SQL Agent Proxy accounts are returned that are not documented and authorized, this is a finding.SRG-APP-000356-DB-000314<GroupDescription></GroupDescription>SQL6-D0-010700SQL Server must utilize centralized management of the content captured in audit records generated by all components of SQL Server.<VulnDiscussion>Without the ability to centrally manage the content captured in the audit records, identification, troubleshooting, and correlation of suspicious behavior would be difficult and could lead to a delayed or incomplete analysis of an ongoing attack. - -The content captured in audit records must be managed from a central location (necessitating automation). Centralized management of audit records and logs provides for efficiency in maintenance and management of records, as well as the backup and archiving of those records. - -SQL Server may write audit records to database tables, to files in the file system, to other kinds of local repository, or directly to a centralized log management system. Whatever the method used, it must be compatible with off-loading the records to the centralized system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93929V-79223CCI-001844Configure and/or deploy software tools to ensure that SQL Server audit records are written directly to or systematically transferred to a centralized log management system.Review the system documentation for a description of how audit records are off-loaded and how local audit log space is managed. - -If the SQL Server audit records are not written directly to or systematically transferred to a centralized log management system, this is a finding.SRG-APP-000356-DB-000315<GroupDescription></GroupDescription>SQL6-D0-010800SQL Server must provide centralized configuration of the content to be captured in audit records generated by all components of SQL Server.<VulnDiscussion>If the configuration of SQL Server's auditing is spread across multiple locations in the database management software, or across multiple commands, only loosely related, it is harder to use and takes longer to reconfigure in response to events. - -SQL Server must provide a unified tool for audit configuration.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93931V-79225CCI-001844Configure and/or deploy software tools to ensure that SQL Server audit records (to include traces used for audit purposes) are written directly to or systematically transferred to a centralized log management system.Review the system documentation for a description of how audit records are off-loaded and how local audit log space is managed. - -If the SQL Server audit records (to include traces used for audit purposes) are not written directly to or systematically transferred to a centralized log management system, this is a finding.SRG-APP-000357-DB-000316<GroupDescription></GroupDescription>SQL6-D0-010900SQL Server must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements.<VulnDiscussion>In order to ensure sufficient storage capacity for the audit logs, SQL Server must be able to allocate audit record storage capacity. Although another requirement (SRG-APP-000515-DB-000318) mandates that audit data be off-loaded to a centralized log management system, it remains necessary to provide space on the database server to serve as a buffer against outages and capacity limits of the off-loading mechanism. +If any Credentials or SQL Agent Proxy accounts are returned that are not documented and authorized, this is a finding.SRG-APP-000357-DB-000316<GroupDescription></GroupDescription>SQL6-D0-010900SQL Server must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements.<VulnDiscussion>In order to ensure sufficient storage capacity for the audit logs, SQL Server must be able to allocate audit record storage capacity. Although another requirement (SRG-APP-000515-DB-000318) mandates that audit data be off-loaded to a centralized log management system, it remains necessary to provide space on the database server to serve as a buffer against outages and capacity limits of the off-loading mechanism. The task of allocating audit record storage capacity is usually performed during initial installation of SQL Server and is closely associated with the DBA and system administrator roles. The DBA or system administrator will usually coordinate the allocation of physical drive space with the application owner/installer and the application will prompt the installer to provide the capacity information, the physical location of the disk, or both. @@ -1498,7 +1497,7 @@ FROM sys.server_file_audits Calculate the space needed as the maximum file size and number of files from the SQL Audit File properties. -If the calculated product of the "max_file_size" times the "max_rollover_files" exceeds the size of the storage location or if "max_file_size" or "max_rollover_files" are set to "0" (UNLIMITED), this is a finding.SRG-APP-000359-DB-000319<GroupDescription></GroupDescription>SQL6-D0-011000SQL Server must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75% of maximum audit record storage capacity.<VulnDiscussion>Organizations are required to use a central log management system, so, under normal conditions, the audit space allocated to SQL Server on its own server will not be an issue. However, space will still be required on the server for SQL Server audit records in transit, and, under abnormal conditions, this could fill up. Since a requirement exists to halt processing upon audit failure, a service outage would result. +If the calculated product of the "max_file_size" times the "max_rollover_files" exceeds the size of the storage location or if "max_file_size" or "max_rollover_files" are set to "0" (UNLIMITED), this is a finding.SRG-APP-000359-DB-000319<GroupDescription></GroupDescription>SQL6-D0-011000SQL Server must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75% of maximum audit record storage capacity.<VulnDiscussion>Organizations are required to use a central log management system, so, under normal conditions, the audit space allocated to SQL Server on its own server will not be an issue. However, space will still be required on the server for SQL Server audit records in transit, and, under abnormal conditions, this could fill up. Since a requirement exists to halt processing upon audit failure, a service outage would result. If support personnel are not notified immediately upon storage volume utilization reaching 75%, they are unable to plan for storage capacity expansion. @@ -1506,7 +1505,7 @@ The appropriate support staff include, at a minimum, the ISSO and the DBA/SA. Monitoring of free space can be accomplished using Microsoft System Center or a third-party monitoring tool.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93935V-79229CCI-001855Utilize operating system alerting mechanisms, SQL Agent, Operations Management tools, and/or third-party tools to configure the system to notify appropriate support staff immediately upon storage volume utilization reaching 75%.The operating system and SQL Server offer a number of methods for checking the drive or volume free space. Locate the destination drive where SQL Audits are stored and review system configuration. -If no alert exist to notify support staff in the event the SQL Audit drive reaches 75%, this is a finding.SRG-APP-000360-DB-000320<GroupDescription></GroupDescription>SQL6-D0-011100SQL Server must provide an immediate real-time alert to appropriate support staff of all audit log failures.<VulnDiscussion>It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without a real-time alert, security personnel may be unaware of an impending failure of the audit capability, and system operation may be adversely affected. +If no alert exist to notify support staff in the event the SQL Audit drive reaches 75%, this is a finding.SRG-APP-000360-DB-000320<GroupDescription></GroupDescription>SQL6-D0-011100SQL Server must provide an immediate real-time alert to appropriate support staff of all audit log failures.<VulnDiscussion>It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without a real-time alert, security personnel may be unaware of an impending failure of the audit capability, and system operation may be adversely affected. The appropriate support staff include, at a minimum, the ISSO and the DBA/SA. @@ -1514,7 +1513,7 @@ A failure of database auditing will result in either the database continuing to Alerts provide organizations with urgent messages. Real-time alerts provide these messages immediately (i.e., the time from event detection to alert occurs in seconds or less). Alerts can be generated using tools like the SQL Server Agent Alerts and Database Mail.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93937V-79231CCI-001858Configure the system to provide immediate real-time alerts to appropriate support staff when an audit log failure occurs.Review SQL Server settings, OS, or third-party logging software settings to determine whether a real-time alert will be sent to the appropriate personnel when auditing fails for any reason. -If real-time alerts are not sent upon auditing failure, this is a finding.SRG-APP-000374-DB-000322<GroupDescription></GroupDescription>SQL6-D0-011200SQL Server must record time stamps in audit records and application data that can be mapped to Coordinated Universal Time (UTC, formerly GMT).<VulnDiscussion>If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis. +If real-time alerts are not sent upon auditing failure, this is a finding.SRG-APP-000374-DB-000322<GroupDescription></GroupDescription>SQL6-D0-011200SQL Server must record time stamps in audit records and application data that can be mapped to Coordinated Universal Time (UTC, formerly GMT).<VulnDiscussion>If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis. Time stamps generated by SQL Server must include date and time. Time is commonly expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93939V-79233CCI-001890Where possible, configure the operating system to automatic synchronize with an official time server, using NTP. @@ -1538,7 +1537,7 @@ If such a procedure does not exist, this is a finding. If the procedure exists, review evidence that the correct time is actually maintained. -If the evidence indicates otherwise, this is a finding.SRG-APP-000380-DB-000360<GroupDescription></GroupDescription>SQL6-D0-011400SQL Server must enforce access restrictions associated with changes to the configuration of the instance.<VulnDiscussion>Failure to provide logical access restrictions associated with changes to configuration may have significant effects on the overall security of the system. +If the evidence indicates otherwise, this is a finding.SRG-APP-000380-DB-000360<GroupDescription></GroupDescription>SQL6-D0-011400SQL Server must enforce access restrictions associated with changes to the configuration of the instance.<VulnDiscussion>Failure to provide logical access restrictions associated with changes to configuration may have significant effects on the overall security of the system. When dealing with access restrictions pertaining to change control, it should be noted that any changes to the hardware, software, and/or firmware components of the information system can potentially have significant effects on the overall security of the system. @@ -1573,7 +1572,7 @@ INNER JOIN sys.server_role_members rm ON m.principal_id = rm.member_principal_id INNER JOIN sys.server_principals r ON rm.role_principal_id = r.principal_id WHERE r.name IN ('sysadmin','securityadmin','serveradmin') -Check the server documentation to verify the logins and roles returned are authorized. If the logins and/or roles are not documented and authorized, this is a finding.SRG-APP-000380-DB-000360<GroupDescription></GroupDescription>SQL6-D0-011500Windows must enforce access restrictions associated with changes to the configuration of the SQL Server instance.<VulnDiscussion>Failure to provide logical access restrictions associated with changes to configuration may have significant effects on the overall security of the system. +Check the server documentation to verify the logins and roles returned are authorized. If the logins and/or roles are not documented and authorized, this is a finding.SRG-APP-000380-DB-000360<GroupDescription></GroupDescription>SQL6-D0-011500Windows must enforce access restrictions associated with changes to the configuration of the SQL Server instance.<VulnDiscussion>Failure to provide logical access restrictions associated with changes to configuration may have significant effects on the overall security of the system. When dealing with access restrictions pertaining to change control, it should be noted that any changes to the hardware, software, and/or firmware components of the information system can potentially have significant effects on the overall security of the system. @@ -1589,9 +1588,10 @@ net localgroup administrators Check the server documentation to verify the users returned are authorized. -If the users are not documented and authorized, this is a finding.SRG-APP-000381-DB-000361<GroupDescription></GroupDescription>SQL6-D0-011800SQL Server must produce audit records of its enforcement of access restrictions associated with changes to the configuration of SQL Server or database(s).<VulnDiscussion>Without auditing the enforcement of access restrictions against changes to configuration, it would be difficult to identify attempted attacks and an audit trail would not be available for forensic investigation for after-the-fact actions. +If the users are not documented and authorized, this is a finding.SRG-APP-000381-DB-000361<GroupDescription></GroupDescription>SQL6-D0-011800SQL Server must produce audit records of its enforcement of access restrictions associated with changes to the configuration of SQL Server or database(s).<VulnDiscussion>Without auditing the enforcement of access restrictions against changes to configuration, it would be difficult to identify attempted attacks and an audit trail would not be available for forensic investigation for after-the-fact actions. -Enforcement actions are the methods or mechanisms used to prevent unauthorized changes to configuration settings. Enforcement action methods may be as simple as denying access to a file based on the application of file permissions (access restriction). Audit items may consist of lists of actions blocked by access restrictions or changes identified after the fact.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93945V-79239CCI-001814Add the required events to the server audit specification to audit denied actions. +Enforcement actions are the methods or mechanisms used to prevent unauthorized changes to configuration settings. Enforcement action methods may be as simple as denying access to a file based on the application of file permissions (access restriction). Audit items may consist of lists of actions blocked by access restrictions or changes identified after the fact.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93945V-79239CCI-003938Add the required events to the server audit specification to audit denied actions. + USE [master]; GO @@ -1630,8 +1630,7 @@ ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (TRACE_CHAN GO ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION WITH (STATE = ON); -GO -Determine if an audit is configured to capture denied actions and started by executing the following query: +GODetermine if an audit is configured to capture denied actions and started by executing the following query: SELECT name AS 'Audit Name', status_desc AS 'Audit Status', @@ -1711,7 +1710,7 @@ AND d.audit_action_name IN ( ) Order by d.audit_action_name -If the identified groups are not returned, this is a finding.SRG-APP-000383-DB-000364<GroupDescription></GroupDescription>SQL6-D0-011900SQL Server must disable network functions, ports, protocols, and services deemed by the organization to be nonsecure, in accord with the Ports, Protocols, and Services Management (PPSM) guidance.<VulnDiscussion>Use of nonsecure network functions, ports, protocols, and services exposes the system to avoidable threats.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93947V-79241CCI-001762Assign the approved TCP/IP port number to the SQL Server Database Engine. +If the identified groups are not returned, this is a finding.SRG-APP-000383-DB-000364<GroupDescription></GroupDescription>SQL6-D0-011900SQL Server must disable network functions, ports, protocols, and services deemed by the organization to be nonsecure, in accord with the Ports, Protocols, and Services Management (PPSM) guidance.<VulnDiscussion>Use of nonsecure network functions, ports, protocols, and services exposes the system to avoidable threats.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93947V-79241CCI-001762Assign the approved TCP/IP port number to the SQL Server Database Engine. 1. In SQL Server Configuration Manager, in the console pane, expand SQL Server Network Configuration, expand Protocols for <instance name>, and then double-click "TCP/IP". 2. In the "TCP/IP Properties" dialog box, on the "IP Addresses" tab, several IP addresses appear in the format IP1, IP2, up to IPAll. One of these is for the IP address of the loopback adapter, 127.0.0.1. Additional IP addresses appear for each IP Address on the computer. (You will probably see both IP version 4 and IP version 6 addresses.) Right-click each address, and then click "Properties" to identify the IP address that you want to configure. 3. If the "TCP Dynamic Ports" dialog box contains "0", indicating the Database Engine is listening on dynamic ports, delete the "0". @@ -1730,7 +1729,7 @@ Obtain a list of all approved network libraries, communication ports, and protoc Verify that the protocols are enabled for the instance. -If any ports or protocols are used that are not specifically approved in the server documentation, this is a finding.SRG-APP-000431-DB-000388<GroupDescription></GroupDescription>SQL6-D0-012300SQL Server must maintain a separate execution domain for each executing process.<VulnDiscussion>Database management systems can maintain separate execution domains for each executing process by assigning each process a separate address space. +If any ports or protocols are used that are not specifically approved in the server documentation, this is a finding.SRG-APP-000431-DB-000388<GroupDescription></GroupDescription>SQL6-D0-012300SQL Server must maintain a separate execution domain for each executing process.<VulnDiscussion>Database management systems can maintain separate execution domains for each executing process by assigning each process a separate address space. Each process has a distinct address space so that communication between processes is controlled through the security functions, and one process cannot modify the executing code of another process. @@ -1746,7 +1745,7 @@ SELECT name, value, value_in_use FROM sys.configurations WHERE name = 'clr enabled' -If "value_in_use" is a "1" and CLR is not required, this is a finding.SRG-APP-000431-DB-000388<GroupDescription></GroupDescription>SQL6-D0-012400SQL Server services must be configured to run under unique dedicated user accounts.<VulnDiscussion>Database management systems can maintain separate execution domains for each executing process by assigning each process a separate address space. Each process has a distinct address space so that communication between processes is controlled through the security functions, and one process cannot modify the executing code of another process. Maintaining separate execution domains for executing processes can be achieved, for example, by implementing separate address spaces.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93951V-79245CCI-002530Configure SQL Server services to have a documented, dedicated account. +If "value_in_use" is a "1" and CLR is not required, this is a finding.SRG-APP-000431-DB-000388<GroupDescription></GroupDescription>SQL6-D0-012400SQL Server services must be configured to run under unique dedicated user accounts.<VulnDiscussion>Database management systems can maintain separate execution domains for each executing process by assigning each process a separate address space. Each process has a distinct address space so that communication between processes is controlled through the security functions, and one process cannot modify the executing code of another process. Maintaining separate execution domains for executing processes can be achieved, for example, by implementing separate address spaces.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93951V-79245CCI-002530Configure SQL Server services to have a documented, dedicated account. For non-domain servers, consider using virtual service accounts (VSA). See https://msdn.microsoft.com/en-us/library/ms143504.aspx#VA_Desc for more information. @@ -1756,7 +1755,7 @@ For clustered instances, consider using group managed service accounts. See http Click Start >> Type "SQL Server Configuration Manager" >> Launch the program >> Click SQL Server Services tree node. Review the "Log On As" column for each service. -If any services are configured with the same service account or are configured with an account that is not documented and authorized, this is a finding.SRG-APP-000454-DB-000389<GroupDescription></GroupDescription>SQL6-D0-012700When updates are applied to SQL Server software, any software components that have been replaced or made unnecessary must be removed.<VulnDiscussion>Previous versions of DBMS components that are not removed from the information system after updates have been installed may be exploited by adversaries. +If any services are configured with the same service account or are configured with an account that is not documented and authorized, this is a finding.SRG-APP-000454-DB-000389<GroupDescription></GroupDescription>SQL6-D0-012700When updates are applied to SQL Server software, any software components that have been replaced or made unnecessary must be removed.<VulnDiscussion>Previous versions of DBMS components that are not removed from the information system after updates have been installed may be exploited by adversaries. Some DBMSs' installation tools may remove older versions of software automatically from the information system. In other cases, manual review and removal will be required. In planning installations and upgrades, organizations must include steps (automated, manual, or both) to identify and remove the outdated modules. @@ -1766,7 +1765,7 @@ Generate a listing of components installed on the server. Click Start >> Type "SQL Server 2016 Installation Center" >> Launch the program >> Click Tools >> Click "Installed SQL Server features discovery report" -Compare the feature listing against the required components listing. If any features are installed, but are not required, this is a finding.SRG-APP-000456-DB-000390<GroupDescription></GroupDescription>SQL6-D0-012800Security-relevant software updates to SQL Server must be installed within the time period directed by an authoritative source (e.g. IAVM, CTOs, DTMs, and STIGs).<VulnDiscussion>Security flaws with software applications, including database management systems, are discovered daily. Vendors are constantly updating and patching their products to address newly discovered security vulnerabilities. Organizations (including any contractor to the organization) are required to promptly install security-relevant software updates (e.g., patches, service packs, and hot fixes). Flaws discovered during security assessments, continuous monitoring, incident response activities, or information system error handling must also be addressed expeditiously. +Compare the feature listing against the required components listing. If any features are installed, but are not required, this is a finding.SRG-APP-000456-DB-000390<GroupDescription></GroupDescription>SQL6-D0-012800Security-relevant software updates to SQL Server must be installed within the time period directed by an authoritative source (e.g. IAVM, CTOs, DTMs, and STIGs).<VulnDiscussion>Security flaws with software applications, including database management systems, are discovered daily. Vendors are constantly updating and patching their products to address newly discovered security vulnerabilities. Organizations (including any contractor to the organization) are required to promptly install security-relevant software updates (e.g., patches, service packs, and hot fixes). Flaws discovered during security assessments, continuous monitoring, incident response activities, or information system error handling must also be addressed expeditiously. Organization-defined time periods for updating security-relevant software may vary based on a variety of factors including, for example, the security category of the information system or the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw). @@ -1778,7 +1777,7 @@ Check the SQL Server version by running the following script: Print @@version If the SQL Server version is not shown as supported, this is a finding. -If such evidence cannot be obtained, or the evidence that is obtained indicates a pattern of noncompliance, this is a finding.SRG-APP-000492-DB-000332<GroupDescription></GroupDescription>SQL6-D0-012900SQL Server must be able to generate audit records when successful and unsuccessful attempts to access security objects occur.<VulnDiscussion>Changes to the security configuration must be tracked. +If such evidence cannot be obtained, or the evidence that is obtained indicates a pattern of noncompliance, this is a finding.SRG-APP-000492-DB-000332<GroupDescription></GroupDescription>SQL6-D0-012900SQL Server must be able to generate audit records when successful and unsuccessful attempts to access security objects occur.<VulnDiscussion>Changes to the security configuration must be tracked. This requirement applies to situations where security data is retrieved or modified via data manipulation operations, as opposed to via specialized security functionality. @@ -1819,7 +1818,7 @@ JOIN sys.server_audits a ON s.audit_guid = a.audit_guid JOIN sys.server_audit_specification_details d ON s.server_specification_id = d.server_specification_id WHERE a.is_state_enabled = 1 AND d.audit_action_name = 'SCHEMA_OBJECT_ACCESS_GROUP' -If the "SCHEMA_OBJECT_ACCESS_GROUP" is not returned in an active audit, this is a finding.SRG-APP-000494-DB-000345<GroupDescription></GroupDescription>SQL6-D0-013200SQL Server must generate audit records when successful and unsuccessful attempts to access categorized information (e.g., classification levels/security levels) occur.<VulnDiscussion>Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. +If the "SCHEMA_OBJECT_ACCESS_GROUP" is not returned in an active audit, this is a finding.SRG-APP-000494-DB-000345<GroupDescription></GroupDescription>SQL6-D0-013200SQL Server must generate audit records when successful and unsuccessful attempts to access categorized information (e.g., classification levels/security levels) occur.<VulnDiscussion>Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. For detailed information on categorizing information, refer to FIPS Publication 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems. @@ -1851,7 +1850,7 @@ JOIN sys.server_audits a ON s.audit_guid = a.audit_guid JOIN sys.server_audit_specification_details d ON s.server_specification_id = d.server_specification_id WHERE a.is_state_enabled = 1 AND d.audit_action_name = 'SCHEMA_OBJECT_ACCESS_GROUP' -If the "SCHEMA_OBJECT_ACCESS_GROUP" is not returned in an active audit, this is a finding.SRG-APP-000495-DB-000327<GroupDescription></GroupDescription>SQL6-D0-013400SQL Server must generate audit records when successful and unsuccessful attempts to add privileges/permissions occur.<VulnDiscussion>Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restriction of privileges could go undetected. Elevated privileges give users access to information and functionality that they should not have; restricted privileges wrongly deny access to authorized users. +If the "SCHEMA_OBJECT_ACCESS_GROUP" is not returned in an active audit, this is a finding.SRG-APP-000495-DB-000327<GroupDescription></GroupDescription>SQL6-D0-013400SQL Server must generate audit records when successful and unsuccessful attempts to add privileges/permissions occur.<VulnDiscussion>Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restriction of privileges could go undetected. Elevated privileges give users access to information and functionality that they should not have; restricted privileges wrongly deny access to authorized users. In an SQL environment, adding permissions is typically done via the GRANT command, or, in the negative, the DENY command. @@ -1919,7 +1918,7 @@ SERVER_OBJECT_PERMISSION_CHANGE_GROUP SERVER_PERMISSION_CHANGE_GROUP SERVER_ROLE_MEMBER_CHANGE_GROUP -If no records are returned, this is a finding.SRG-APP-000495-DB-000329<GroupDescription></GroupDescription>SQL6-D0-013600SQL Server must generate audit records when successful and unsuccessful attempts to modify privileges/permissions occur.<VulnDiscussion>Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restriction of privileges could go undetected. Elevated privileges give users access to information and functionality that they should not have; restricted privileges wrongly deny access to authorized users. +If no records are returned, this is a finding.SRG-APP-000495-DB-000329<GroupDescription></GroupDescription>SQL6-D0-013600SQL Server must generate audit records when successful and unsuccessful attempts to modify privileges/permissions occur.<VulnDiscussion>Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restriction of privileges could go undetected. Elevated privileges give users access to information and functionality that they should not have; restricted privileges wrongly deny access to authorized users. In an SQL environment, modifying permissions is typically done via the GRANT, REVOKE, and DENY commands. @@ -1987,7 +1986,7 @@ SERVER_OBJECT_PERMISSION_CHANGE_GROUP SERVER_PERMISSION_CHANGE_GROUP SERVER_ROLE_MEMBER_CHANGE_GROUP -If no records are returned, this is a finding.SRG-APP-000496-DB-000335<GroupDescription></GroupDescription>SQL6-D0-013800SQL Server must generate audit records when successful and unsuccessful attempts to modify security objects occur.<VulnDiscussion>Changes in the database objects (tables, views, procedures, functions) that record and control permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized changes to the security subsystem could go undetected. The database could be severely compromised or rendered inoperative. +If no records are returned, this is a finding.SRG-APP-000496-DB-000335<GroupDescription></GroupDescription>SQL6-D0-013800SQL Server must generate audit records when successful and unsuccessful attempts to modify security objects occur.<VulnDiscussion>Changes in the database objects (tables, views, procedures, functions) that record and control permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized changes to the security subsystem could go undetected. The database could be severely compromised or rendered inoperative. To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones. @@ -2024,7 +2023,7 @@ JOIN sys.server_audits a ON s.audit_guid = a.audit_guid JOIN sys.server_audit_specification_details d ON s.server_specification_id = d.server_specification_id WHERE a.is_state_enabled = 1 AND d.audit_action_name = 'SCHEMA_OBJECT_CHANGE_GROUP' -If the "SCHEMA_OBJECT_CHANGE_GROUP" is not returned in an active audit, this is a finding.SRG-APP-000498-DB-000347<GroupDescription></GroupDescription>SQL6-D0-014000SQL Server must generate audit records when successful and unsuccessful attempts to modify categorized information (e.g., classification levels/security levels) occur.<VulnDiscussion>Changes in categories of information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. +If the "SCHEMA_OBJECT_CHANGE_GROUP" is not returned in an active audit, this is a finding.SRG-APP-000498-DB-000347<GroupDescription></GroupDescription>SQL6-D0-014000SQL Server must generate audit records when successful and unsuccessful attempts to modify categorized information (e.g., classification levels/security levels) occur.<VulnDiscussion>Changes in categories of information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones. @@ -2056,7 +2055,7 @@ JOIN sys.server_audits a ON s.audit_guid = a.audit_guid JOIN sys.server_audit_specification_details d ON s.server_specification_id = d.server_specification_id WHERE a.is_state_enabled = 1 AND d.audit_action_name = 'SCHEMA_OBJECT_ACCESS_GROUP' -If the "SCHEMA_OBJECT_ACCESS_GROUP" is not returned in an active audit, this is a finding.SRG-APP-000499-DB-000331<GroupDescription></GroupDescription>SQL6-D0-014200SQL Server must generate audit records when successful and unsuccessful attempts to delete privileges/permissions occur.<VulnDiscussion>Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restriction of privileges could go undetected. Elevated privileges give users access to information and functionality that they should not have; restricted privileges wrongly deny access to authorized users. +If the "SCHEMA_OBJECT_ACCESS_GROUP" is not returned in an active audit, this is a finding.SRG-APP-000499-DB-000331<GroupDescription></GroupDescription>SQL6-D0-014200SQL Server must generate audit records when successful and unsuccessful attempts to delete privileges/permissions occur.<VulnDiscussion>Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restriction of privileges could go undetected. Elevated privileges give users access to information and functionality that they should not have; restricted privileges wrongly deny access to authorized users. In an SQL environment, deleting permissions is typically done via the REVOKE or DENY command. @@ -2122,7 +2121,7 @@ SERVER_PERMISSION_CHANGE_GROUP SERVER_ROLE_MEMBER_CHANGE_GROUP Reference: -https://msdn.microsoft.com/en-us/library/cc280663.aspxSRG-APP-000501-DB-000337<GroupDescription></GroupDescription>SQL6-D0-014400SQL Server must generate audit records when successful and unsuccessful attempts to delete security objects occur.<VulnDiscussion>The removal of security objects from the database/DBMS would seriously degrade a system's information assurance posture. If such an action is attempted, it must be logged. +https://msdn.microsoft.com/en-us/library/cc280663.aspxSRG-APP-000501-DB-000337<GroupDescription></GroupDescription>SQL6-D0-014400SQL Server must generate audit records when successful and unsuccessful attempts to delete security objects occur.<VulnDiscussion>The removal of security objects from the database/DBMS would seriously degrade a system's information assurance posture. If such an action is attempted, it must be logged. To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones. @@ -2159,7 +2158,7 @@ JOIN sys.server_audits a ON s.audit_guid = a.audit_guid JOIN sys.server_audit_specification_details d ON s.server_specification_id = d.server_specification_id WHERE a.is_state_enabled = 1 AND d.audit_action_name = 'SCHEMA_OBJECT_CHANGE_GROUP' -If the "SCHEMA_OBJECT_CHANGE_GROUP" is not returned in an active audit, this is a finding.SRG-APP-000502-DB-000349<GroupDescription></GroupDescription>SQL6-D0-014600SQL Server must generate audit records when successful and unsuccessful attempts to delete categorized information (e.g., classification levels/security levels) occur.<VulnDiscussion>Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. +If the "SCHEMA_OBJECT_CHANGE_GROUP" is not returned in an active audit, this is a finding.SRG-APP-000502-DB-000349<GroupDescription></GroupDescription>SQL6-D0-014600SQL Server must generate audit records when successful and unsuccessful attempts to delete categorized information (e.g., classification levels/security levels) occur.<VulnDiscussion>Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones. @@ -2191,7 +2190,7 @@ JOIN sys.server_audits a ON s.audit_guid = a.audit_guid JOIN sys.server_audit_specification_details d ON s.server_specification_id = d.server_specification_id WHERE a.is_state_enabled = 1 AND d.audit_action_name = 'SCHEMA_OBJECT_ACCESS_GROUP' -If the "SCHEMA_OBJECT_ACCESS_GROUP" is not returned in an active audit, this is a finding.SRG-APP-000503-DB-000351<GroupDescription></GroupDescription>SQL6-D0-014800SQL Server must generate audit records when successful and unsuccessful logons or connection attempts occur.<VulnDiscussion>For completeness of forensic analysis, it is necessary to track who/what (a user or other principal) logs on to SQL Server. It is also necessary to track failed attempts to log on to SQL Server. While positive identification may not be possible in a case of failed authentication, as much information as possible about the incident must be captured. +If the "SCHEMA_OBJECT_ACCESS_GROUP" is not returned in an active audit, this is a finding.SRG-APP-000503-DB-000351<GroupDescription></GroupDescription>SQL6-D0-014800SQL Server must generate audit records when successful and unsuccessful logons or connection attempts occur.<VulnDiscussion>For completeness of forensic analysis, it is necessary to track who/what (a user or other principal) logs on to SQL Server. It is also necessary to track failed attempts to log on to SQL Server. While positive identification may not be possible in a case of failed authentication, as much information as possible about the incident must be captured. Satisfies: SRG-APP-000503-DB-000350</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-93995V-79289CCI-000172Add both "SUCCESSFUL_LOGIN_GROUP" and "FAILED_LOGIN_GROUP" to the server audit specification. USE [master]; @@ -2244,7 +2243,7 @@ Right-click on the instance >> Select "Security" on the left hand side >> Check the setting for "Login auditing" -If "Both failed and successful logins" is not selected, this is a finding.SRG-APP-000504-DB-000354<GroupDescription></GroupDescription>SQL6-D0-014900SQL Server must generate audit records for all privileged activities or other system-level access.<VulnDiscussion>Without tracking privileged activity, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. +If "Both failed and successful logins" is not selected, this is a finding.SRG-APP-000504-DB-000354<GroupDescription></GroupDescription>SQL6-D0-014900SQL Server must generate audit records for all privileged activities or other system-level access.<VulnDiscussion>Without tracking privileged activity, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. System documentation should include a definition of the functionality considered privileged. @@ -2361,7 +2360,7 @@ JOIN sys.server_audit_specification_details d ON s.server_specification_id = d.s WHERE a.is_state_enabled = 1 AND d.audit_action_name IN ('APPLICATION_ROLE_CHANGE_PASSWORD_GROUP','AUDIT_CHANGE_GROUP','BACKUP_RESTORE_GROUP','DATABASE_CHANGE_GROUP','DATABASE_OBJECT_CHANGE_GROUP','DATABASE_OBJECT_OWNERSHIP_CHANGE_GROUP','DATABASE_OBJECT_PERMISSION_CHANGE_GROUP','DATABASE_OPERATION_GROUP','DATABASE_OWNERSHIP_CHANGE_GROUP','DATABASE_PERMISSION_CHANGE_GROUP','DATABASE_PRINCIPAL_CHANGE_GROUP','DATABASE_PRINCIPAL_IMPERSONATION_GROUP','DATABASE_ROLE_MEMBER_CHANGE_GROUP','DBCC_GROUP','LOGIN_CHANGE_PASSWORD_GROUP','SCHEMA_OBJECT_CHANGE_GROUP','SCHEMA_OBJECT_OWNERSHIP_CHANGE_GROUP','SCHEMA_OBJECT_PERMISSION_CHANGE_GROUP','SERVER_OBJECT_CHANGE_GROUP','SERVER_OBJECT_OWNERSHIP_CHANGE_GROUP','SERVER_OBJECT_PERMISSION_CHANGE_GROUP','SERVER_OPERATION_GROUP','SERVER_PERMISSION_CHANGE_GROUP','SERVER_PRINCIPAL_CHANGE_GROUP','SERVER_PRINCIPAL_IMPERSONATION_GROUP','SERVER_ROLE_MEMBER_CHANGE_GROUP','SERVER_STATE_CHANGE_GROUP','TRACE_CHANGE_GROUP','USER_CHANGE_PASSWORD_GROUP') -If the identified groups are not returned, this is a finding.SRG-APP-000504-DB-000355<GroupDescription></GroupDescription>SQL6-D0-015000SQL Server must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur.<VulnDiscussion>Without tracking privileged activity, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. +If the identified groups are not returned, this is a finding.SRG-APP-000504-DB-000355<GroupDescription></GroupDescription>SQL6-D0-015000SQL Server must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur.<VulnDiscussion>Without tracking privileged activity, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. System documentation should include a definition of the functionality considered privileged. @@ -2502,7 +2501,7 @@ Order by d.audit_action_name If the identified groups are not returned, this is a finding. -SRG-APP-000505-DB-000352<GroupDescription></GroupDescription>SQL6-D0-015100SQL Server must generate audit records showing starting and ending time for user access to the database(s).<VulnDiscussion>For completeness of forensic analysis, it is necessary to know how long a user's (or other principal's) connection to SQL Server lasts. This can be achieved by recording disconnections, in addition to logons/connections, in the audit logs. +SRG-APP-000505-DB-000352<GroupDescription></GroupDescription>SQL6-D0-015100SQL Server must generate audit records showing starting and ending time for user access to the database(s).<VulnDiscussion>For completeness of forensic analysis, it is necessary to know how long a user's (or other principal's) connection to SQL Server lasts. This can be achieved by recording disconnections, in addition to logons/connections, in the audit logs. Disconnection may be initiated by the user or forced by the system (as in a timeout) or result from a system or network failure. To the greatest extent possible, all disconnections must be logged.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-94001V-79295CCI-000172Add the "LOGOUT_GROUP" to the server audit specification USE [master]; @@ -2601,7 +2600,7 @@ Order by d.audit_action_name If the identified groups are not returned, this is a finding. -SRG-APP-000506-DB-000353<GroupDescription></GroupDescription>SQL6-D0-015200SQL Server must generate audit records when concurrent logons/connections by the same user from different workstations occur.<VulnDiscussion>For completeness of forensic analysis, it is necessary to track who logs on to SQL Server. +SRG-APP-000506-DB-000353<GroupDescription></GroupDescription>SQL6-D0-015200SQL Server must generate audit records when concurrent logons/connections by the same user from different workstations occur.<VulnDiscussion>For completeness of forensic analysis, it is necessary to track who logs on to SQL Server. Concurrent connections by the same user from multiple workstations may be valid use of the system; or such connections may be due to improper circumvention of the requirement to use the CAC for authentication; or they may indicate unauthorized account sharing; or they may be because an account has been compromised. @@ -2647,7 +2646,7 @@ If "SUCCESSFUL_LOGIN_GROUP" is not in the active audit, determine whether "Both In SQL Management Studio: Right-click on the instance >> Select "Properties" >> Select "Security" on the left hand side >> Check the setting for "Login auditing" -If "Both failed and successful logins" is not selected, this is a finding.SRG-APP-000507-DB-000357<GroupDescription></GroupDescription>SQL6-D0-015400SQL Server must generate audit records when successful and unsuccessful accesses to objects occur.<VulnDiscussion>Without tracking all or selected types of access to all or selected objects (tables, views, procedures, functions, etc.), it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. +If "Both failed and successful logins" is not selected, this is a finding.SRG-APP-000507-DB-000357<GroupDescription></GroupDescription>SQL6-D0-015400SQL Server must generate audit records when successful and unsuccessful accesses to objects occur.<VulnDiscussion>Without tracking all or selected types of access to all or selected objects (tables, views, procedures, functions, etc.), it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. In an SQL environment, types of access include, but are not necessarily limited to: SELECT @@ -2684,7 +2683,7 @@ JOIN sys.server_audits a ON s.audit_guid = a.audit_guid JOIN sys.server_audit_specification_details d ON s.server_specification_id = d.server_specification_id WHERE a.is_state_enabled = 1 AND d.audit_action_name = 'SCHEMA_OBJECT_ACCESS_GROUP' -If the "SCHEMA_OBJECT_ACCESS_GROUP" is not returned in an active audit, this is a finding.SRG-APP-000508-DB-000358<GroupDescription></GroupDescription>SQL6-D0-015500SQL Server must generate audit records for all direct access to the database(s).<VulnDiscussion>In this context, direct access is any query, command, or call to SQL Server that comes from any source other than the application(s) that it supports. Examples would be the command line or a database management utility program. The intent is to capture all activity from administrative and non-standard sources.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-94009V-79303CCI-000172Check the system documentation for required SQL Server Audits. Remove any Audit filters that exclude or reduce required auditing. Update filters to ensure administrative activity is not excluded.Determine whether any Server Audits are configured to filter records. From SQL Server Management Studio execute the following query: +If the "SCHEMA_OBJECT_ACCESS_GROUP" is not returned in an active audit, this is a finding.SRG-APP-000508-DB-000358<GroupDescription></GroupDescription>SQL6-D0-015500SQL Server must generate audit records for all direct access to the database(s).<VulnDiscussion>In this context, direct access is any query, command, or call to SQL Server that comes from any source other than the application(s) that it supports. Examples would be the command line or a database management utility program. The intent is to capture all activity from administrative and non-standard sources.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-94009V-79303CCI-000172Check the system documentation for required SQL Server Audits. Remove any Audit filters that exclude or reduce required auditing. Update filters to ensure administrative activity is not excluded.Determine whether any Server Audits are configured to filter records. From SQL Server Management Studio execute the following query: SELECT name AS AuditName, predicate AS AuditFilter FROM sys.server_audits @@ -2692,7 +2691,7 @@ WHERE predicate IS NOT NULL If any audits are returned, review the associated filters to determine whether administrative activities are being excluded. -If any audits are configured to exclude administrative activities, this is a finding.SRG-APP-000514-DB-000381<GroupDescription></GroupDescription>SQL6-D0-015600SQL Server must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to provision digital signatures.<VulnDiscussion>Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated. +If any audits are configured to exclude administrative activities, this is a finding.SRG-APP-000514-DB-000381<GroupDescription></GroupDescription>SQL6-D0-015600SQL Server must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to provision digital signatures.<VulnDiscussion>Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated. For detailed information, refer to NIST FIPS Publication 140-2 or Publication 140-3, Security Requirements For Cryptographic Modules. Note that the product's cryptographic modules must be validated and certified by NIST as FIPS-compliant.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-94011V-79305CCI-002450In Windows, open Administrative Tools >> Local Security Policy. @@ -2702,7 +2701,7 @@ In the right-side pane, double-click on "System cryptography: Use FIPS compliant Click Start >> Type "Local Security Policy" >> Press Enter >> Expand "Local Policies" >> Select "Security Options" >> Locate "System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing." -If the Security Setting for this option is "Disabled" this is a finding.SRG-APP-000514-DB-000382<GroupDescription></GroupDescription>SQL6-D0-015700SQL Server must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to generate and validate cryptographic hashes.<VulnDiscussion>Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated. +If the Security Setting for this option is "Disabled" this is a finding.SRG-APP-000514-DB-000382<GroupDescription></GroupDescription>SQL6-D0-015700SQL Server must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to generate and validate cryptographic hashes.<VulnDiscussion>Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated. For detailed information, refer to NIST FIPS Publication 140-2 or Publication 140-3, Security Requirements For Cryptographic Modules. Note that the product's cryptographic modules must be validated and certified by NIST as FIPS-compliant.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-94013V-79307CCI-002450Configure Windows to require the use of FIPS compliant algorithms. @@ -2710,7 +2709,7 @@ Click Start >> Type "Local Security Policy" >> Press Enter >> Click Start >> Type "Local Security Policy" >> Press Enter >> Expand "Local Policies" >> Select "Security Options" >> Locate "System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing." -If "System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing" is not enabled, this is a finding.SRG-APP-000514-DB-000383<GroupDescription></GroupDescription>SQL6-D0-015800SQL Server must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to protect unclassified information requiring confidentiality and cryptographic protection, in accordance with the data owners requirements.<VulnDiscussion>Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated. +If "System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing" is not enabled, this is a finding.SRG-APP-000514-DB-000383<GroupDescription></GroupDescription>SQL6-D0-015800SQL Server must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to protect unclassified information requiring confidentiality and cryptographic protection, in accordance with the data owners requirements.<VulnDiscussion>Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated. It is the responsibility of the data owner to assess the cryptography requirements in light of applicable federal laws, Executive Orders, directives, policies, regulations, and standards. @@ -2722,7 +2721,7 @@ Verify that Windows is configured to require the use of FIPS compliant algorithm Click Start >> Type "Local Security Policy" >> Press Enter >> Expand "Local Policies" >> Select "Security Options" >> Locate "System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing." -If "System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing" is not enabled, this is a finding.SRG-APP-000515-DB-000318<GroupDescription></GroupDescription>SQL6-D0-015900The system SQL Server must off-load audit data to a separate log management facility; this must be continuous and in near real time for systems with a network connection to the storage facility and weekly or more often for stand-alone systems.<VulnDiscussion>Information stored in one location is vulnerable to accidental or incidental deletion or alteration. +If "System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing" is not enabled, this is a finding.SRG-APP-000515-DB-000318<GroupDescription></GroupDescription>SQL6-D0-015900The system SQL Server must off-load audit data to a separate log management facility; this must be continuous and in near real time for systems with a network connection to the storage facility and weekly or more often for stand-alone systems.<VulnDiscussion>Information stored in one location is vulnerable to accidental or incidental deletion or alteration. Off-loading is a common process in information systems with limited audit storage capacity. @@ -2730,7 +2729,7 @@ The system SQL Server may write audit records to database tables, to files in th If the system has a continuous network connection to the centralized log management system, but the DBMS audit records are not written directly to the centralized log management system or transferred in near-real-time, this is a finding. -If the system does not have a continuous network connection to the centralized log management system, and the DBMS audit records are not transferred to the centralized log management system weekly or more often, this is a finding.SRG-APP-000516-DB-000363<GroupDescription></GroupDescription>SQL6-D0-016000SQL Server must configure Customer Feedback and Error Reporting.<VulnDiscussion>By default, Microsoft SQL Server enables participation in the customer experience improvement program (CEIP). This program collects information about how its customers are using the product. Specifically, SQL Server collects information about the installation experience, feature usage, and performance. This information helps Microsoft improve the product to better meet customer needs.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-94019V-79313CCI-000366To disable participation in the CEIP program, change the value of the following registry keys to zero (0). +If the system does not have a continuous network connection to the centralized log management system, and the DBMS audit records are not transferred to the centralized log management system weekly or more often, this is a finding.SRG-APP-000516-DB-000363<GroupDescription></GroupDescription>SQL6-D0-016000SQL Server must configure Customer Feedback and Error Reporting.<VulnDiscussion>By default, Microsoft SQL Server enables participation in the customer experience improvement program (CEIP). This program collects information about how its customers are using the product. Specifically, SQL Server collects information about the installation experience, feature usage, and performance. This information helps Microsoft improve the product to better meet customer needs.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-94019V-79313CCI-000366To disable participation in the CEIP program, change the value of the following registry keys to zero (0). To enable participation in the CEIP program, change the value of the following registry keys to one (1). @@ -2749,7 +2748,7 @@ If this is a classified system, and any of the above values are not zero (0), th If this is an unclassified system, review the server documentation to determine whether CEIP participation is authorized. -If CEIP participation is not authorized, and any of the above values are one (1), this is a finding.SRG-APP-000516-DB-000363<GroupDescription></GroupDescription>SQL6-D0-016100SQL Server must configure SQL Server Usage and Error Reporting Auditing.<VulnDiscussion>By default, Microsoft SQL Server enables participation in the customer experience improvement program (CEIP). This program collects information about how its customers are using the product. Specifically, SQL Server collects information about the installation experience, feature usage, and performance. This information helps Microsoft improve the product to better meet customer needs. The Local Audit component of SQL Server Usage Feedback collection writes data collected by the service to a designated folder, representing the data (logs) that will be sent to Microsoft. The purpose of the Local Audit is to allow customers to see all data Microsoft collects with this feature, for compliance, regulatory or privacy validation reasons.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-94021V-79315CCI-000366Configure the instance to audit telemetry data. More information about auditing telemetry data can be found at https://msdn.microsoft.com/en-us/library/mt743085.aspx. +If CEIP participation is not authorized, and any of the above values are one (1), this is a finding.SRG-APP-000516-DB-000363<GroupDescription></GroupDescription>SQL6-D0-016100SQL Server must configure SQL Server Usage and Error Reporting Auditing.<VulnDiscussion>By default, Microsoft SQL Server enables participation in the customer experience improvement program (CEIP). This program collects information about how its customers are using the product. Specifically, SQL Server collects information about the installation experience, feature usage, and performance. This information helps Microsoft improve the product to better meet customer needs. The Local Audit component of SQL Server Usage Feedback collection writes data collected by the service to a designated folder, representing the data (logs) that will be sent to Microsoft. The purpose of the Local Audit is to allow customers to see all data Microsoft collects with this feature, for compliance, regulatory or privacy validation reasons.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-94021V-79315CCI-000366Configure the instance to audit telemetry data. More information about auditing telemetry data can be found at https://msdn.microsoft.com/en-us/library/mt743085.aspx. Create a folder to store the telemetry audit data in. @@ -2806,7 +2805,7 @@ If the service is not configured to automatically start, this is a finding. Review the processes and procedures for reviewing the telemetry data. If there is evidence that the telemetry data is periodically reviewed in accordance with the processes and procedures, this is not a finding. -If no processes and procedures exist for reviewing telemetry data, this is a finding.SRG-APP-000033-DB-000084<GroupDescription></GroupDescription>SQL6-D0-016200The SQL Server default account [sa] must be disabled.<VulnDiscussion>SQL Server's [sa] account has special privileges required to administer the database. The [sa] account is a well-known SQL Server account and is likely to be targeted by attackers and thus more prone to providing unauthorized access to the database. +If no processes and procedures exist for reviewing telemetry data, this is a finding.SRG-APP-000033-DB-000084<GroupDescription></GroupDescription>SQL6-D0-016200The SQL Server default account [sa] must be disabled.<VulnDiscussion>SQL Server's [sa] account has special privileges required to administer the database. The [sa] account is a well-known SQL Server account and is likely to be targeted by attackers and thus more prone to providing unauthorized access to the database. This [sa] default account is administrative and could lead to catastrophic consequences, including the complete loss of control over SQL Server. If the [sa] default account is not disabled, an attacker might be able to gain access through the account. SQL Server by default disables the [sa] account at installation. @@ -2825,7 +2824,7 @@ GO Verify that the "name" column contains the current name of the [sa] database server account. -If the "is_disabled" column is not set to "1", this is a finding.SRG-APP-000141-DB-000092<GroupDescription></GroupDescription>SQL6-D0-016300SQL Server default account [sa] must have its name changed.<VulnDiscussion>SQL Server's [sa] account has special privileges required to administer the database. The [sa] account is a well-known SQL Server account name and is likely to be targeted by attackers, and is thus more prone to providing unauthorized access to the database. +If the "is_disabled" column is not set to "1", this is a finding.SRG-APP-000141-DB-000092<GroupDescription></GroupDescription>SQL6-D0-016300SQL Server default account [sa] must have its name changed.<VulnDiscussion>SQL Server's [sa] account has special privileges required to administer the database. The [sa] account is a well-known SQL Server account name and is likely to be targeted by attackers, and is thus more prone to providing unauthorized access to the database. Since the SQL Server [sa] is administrative in nature, the compromise of a default account can have catastrophic consequences, including the complete loss of control over SQL Server. Since SQL Server needs for this account to exist and it should not be removed, one way to mitigate this risk is to change the [sa] account name.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-94025V-79319CCI-000381Modify the SQL Server's [sa] (system administrator) account by running the following script: @@ -2841,7 +2840,7 @@ FROM sys.sql_logins WHERE [name] = 'sa' OR [principal_id] = 1; GO -If the login account name "SA" or "sa" appears in the query output, this is a finding.SRG-APP-000342-DB-000302<GroupDescription></GroupDescription>SQL6-D0-016400Execution of startup stored procedures must be restricted to necessary cases only.<VulnDiscussion>In certain situations, to provide required functionality, a DBMS needs to execute internal logic (stored procedures, functions, triggers, etc.) and/or external code modules with elevated privileges. However, if the privileges required for execution are at a higher level than the privileges assigned to organizational users invoking the functionality applications/programs, those users are indirectly provided with greater privileges than assigned by organizations. +If the login account name "SA" or "sa" appears in the query output, this is a finding.SRG-APP-000342-DB-000302<GroupDescription></GroupDescription>SQL6-D0-016400Execution of startup stored procedures must be restricted to necessary cases only.<VulnDiscussion>In certain situations, to provide required functionality, a DBMS needs to execute internal logic (stored procedures, functions, triggers, etc.) and/or external code modules with elevated privileges. However, if the privileges required for execution are at a higher level than the privileges assigned to organizational users invoking the functionality applications/programs, those users are indirectly provided with greater privileges than assigned by organizations. When 'Scan for startup procs' is enabled, SQL Server scans for and runs all automatically run stored procedures defined on the server. The execution of start-up stored procedures will be done under a high privileged context, therefore it is a commonly used post-exploitation vector.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-94027V-79321CCI-002233To disable start up stored procedure(s), run the following in Master for each undocumented procedure: @@ -2851,7 +2850,7 @@ Select [name] as StoredProc From sys.procedures Where OBJECTPROPERTY(OBJECT_ID, 'ExecIsStartup') = 1 -If any stored procedures are returned that are not documented, this is a finding.SRG-APP-000516-DB-000363<GroupDescription></GroupDescription>SQL6-D0-016500SQL Server Mirroring endpoint must utilize AES encryption.<VulnDiscussion>Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. +If any stored procedures are returned that are not documented, this is a finding.SRG-APP-000516-DB-000363<GroupDescription></GroupDescription>SQL6-D0-016500SQL Server Mirroring endpoint must utilize AES encryption.<VulnDiscussion>Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. @@ -2867,7 +2866,7 @@ SELECT name, type_desc, encryption_algorithm_desc FROM sys.database_mirroring_endpoints WHERE encryption_algorithm != 2 -If any records are returned, this is a finding.SRG-APP-000516-DB-000363<GroupDescription></GroupDescription>SQL6-D0-016600SQL Server Service Broker endpoint must utilize AES encryption.<VulnDiscussion>Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. +If any records are returned, this is a finding.SRG-APP-000516-DB-000363<GroupDescription></GroupDescription>SQL6-D0-016600SQL Server Service Broker endpoint must utilize AES encryption.<VulnDiscussion>Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. @@ -2883,7 +2882,7 @@ SELECT name, type_desc, encryption_algorithm_desc FROM sys.service_broker_endpoints WHERE encryption_algorithm != 2 -If any records are returned, this is a finding.SRG-APP-000141-DB-000093<GroupDescription></GroupDescription>SQL6-D0-016700SQL Server execute permissions to access the registry must be revoked, unless specifically required and approved.<VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). +If any records are returned, this is a finding.SRG-APP-000141-DB-000093<GroupDescription></GroupDescription>SQL6-D0-016700SQL Server execute permissions to access the registry must be revoked, unless specifically required and approved.<VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). It is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. @@ -2922,7 +2921,7 @@ WHERE major_id IN ( AND dp.[type] = 'EX' ORDER BY dpr.NAME; -If any records are returned, review the system documentation to determine whether the accessing of the registry via extended stored procedures are required and authorized. If it is not authorized, this is a finding.SRG-APP-000141-DB-000093<GroupDescription></GroupDescription>SQL6-D0-016800Filestream must be disabled, unless specifically required and approved.<VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). +If any records are returned, review the system documentation to determine whether the accessing of the registry via extended stored procedures are required and authorized. If it is not authorized, this is a finding.SRG-APP-000141-DB-000093<GroupDescription></GroupDescription>SQL6-D0-016800Filestream must be disabled, unless specifically required and approved.<VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). It is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. @@ -2956,7 +2955,7 @@ SELECT CASE ELSE 'Yes' END AS TSQLFileStreamAccess; -If the above query returns "Yes" in the "FileStreamEnabled" field, this is a finding.SRG-APP-000141-DB-000093<GroupDescription></GroupDescription>SQL6-D0-017000Ole Automation Procedures feature must be disabled, unless specifically required and approved. <VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). +If the above query returns "Yes" in the "FileStreamEnabled" field, this is a finding.SRG-APP-000141-DB-000093<GroupDescription></GroupDescription>SQL6-D0-017000Ole Automation Procedures feature must be disabled, unless specifically required and approved. <VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). It is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. @@ -2985,7 +2984,7 @@ EXEC SP_CONFIGURE 'Ole Automation Procedures'; If the value of "config_value" is "0", this is not a finding. -If the value of "config_value" is "1", review the system documentation to determine whether the use of "Ole Automation Procedures" is required and authorized. If it is not authorized, this is a finding.SRG-APP-000141-DB-000092<GroupDescription></GroupDescription>SQL6-D0-017100SQL Server User Options feature must be disabled, unless specifically required and approved.<VulnDiscussion>SQL Server is capable of providing a wide range of features and services. Some of the features and services, provided by default, may not be necessary, and enabling them could adversely affect the security of the system. +If the value of "config_value" is "1", review the system documentation to determine whether the use of "Ole Automation Procedures" is required and authorized. If it is not authorized, this is a finding.SRG-APP-000141-DB-000092<GroupDescription></GroupDescription>SQL6-D0-017100SQL Server User Options feature must be disabled, unless specifically required and approved.<VulnDiscussion>SQL Server is capable of providing a wide range of features and services. Some of the features and services, provided by default, may not be necessary, and enabling them could adversely affect the security of the system. The user options option specifies global defaults for all users. A list of default query processing options is established for the duration of a user's work session. The user options option allows you to change the default values of the SET options (if the server's default settings are not appropriate).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-94041V-79335CCI-000381Disable use of or remove any external application executable object definitions that are not authorized. To disable the use of "User Options" option, from the query prompt:  @@ -3004,7 +3003,7 @@ EXEC SP_CONFIGURE 'user options'; If the value of "config_value" is "0", this is not a finding. -If the value of "config_value" is "1", review the system documentation to determine whether the use of "user options" is required and authorized. If it is not authorized, this is a finding.SRG-APP-000141-DB-000093<GroupDescription></GroupDescription>SQL6-D0-017200Remote Access feature must be disabled, unless specifically required and approved.<VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). +If the value of "config_value" is "1", review the system documentation to determine whether the use of "user options" is required and authorized. If it is not authorized, this is a finding.SRG-APP-000141-DB-000093<GroupDescription></GroupDescription>SQL6-D0-017200Remote Access feature must be disabled, unless specifically required and approved.<VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). It is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. @@ -3031,7 +3030,7 @@ EXEC SP_CONFIGURE 'remote access'; If the value of "config_value" is "0", this is not a finding. -If the value of "config_value" is "1", review the system documentation to determine whether the use of "Remote Access" is required (linked servers) and authorized. If it is not authorized, this is a finding.SRG-APP-000141-DB-000093<GroupDescription></GroupDescription>SQL6-D0-017400Hadoop Connectivity feature must be disabled, unless specifically required and approved. <VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). +If the value of "config_value" is "1", review the system documentation to determine whether the use of "Remote Access" is required (linked servers) and authorized. If it is not authorized, this is a finding.SRG-APP-000141-DB-000093<GroupDescription></GroupDescription>SQL6-D0-017400Hadoop Connectivity feature must be disabled, unless specifically required and approved. <VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). It is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. @@ -3058,7 +3057,7 @@ EXEC SP_CONFIGURE 'hadoop connectivity'; If the value of "config_value" is "0", this is not a finding. -If the value of "config_value" is "1", review the system documentation to determine whether the use of "Hadoop Connectivity" option is required and authorized. If it is not authorized, this is a finding.SRG-APP-000141-DB-000093<GroupDescription></GroupDescription>SQL6-D0-017500Allow Polybase Export feature must be disabled, unless specifically required and approved. <VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). +If the value of "config_value" is "1", review the system documentation to determine whether the use of "Hadoop Connectivity" option is required and authorized. If it is not authorized, this is a finding.SRG-APP-000141-DB-000093<GroupDescription></GroupDescription>SQL6-D0-017500Allow Polybase Export feature must be disabled, unless specifically required and approved. <VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). It is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. @@ -3085,7 +3084,7 @@ EXEC SP_CONFIGURE 'allow polybase export'; If the value of "config_value" is "0", this is not a finding. -If the value of "config_value" is "1", review the system documentation to determine whether the use of "Allow Polybase Export" is required and authorized. If it is not authorized, this is a finding.SRG-APP-000141-DB-000093<GroupDescription></GroupDescription>SQL6-D0-017600Remote Data Archive feature must be disabled, unless specifically required and approved. <VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). +If the value of "config_value" is "1", review the system documentation to determine whether the use of "Allow Polybase Export" is required and authorized. If it is not authorized, this is a finding.SRG-APP-000141-DB-000093<GroupDescription></GroupDescription>SQL6-D0-017600Remote Data Archive feature must be disabled, unless specifically required and approved. <VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). It is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. @@ -3112,7 +3111,7 @@ EXEC SP_CONFIGURE 'remote data archive'; If the value of "config_value" is "0", this is not a finding. -If the value of "config_value" is "1", review the system documentation to determine whether the use of "Remote Data Archive" is required and authorized. If it is not authorized, this is a finding.SRG-APP-000141-DB-000092<GroupDescription></GroupDescription>SQL6-D0-017700SQL Server External Scripts Enabled feature must be disabled, unless specifically required and approved.<VulnDiscussion>SQL Server is capable of providing a wide range of features and services. Some of the features and services, provided by default, may not be necessary, and enabling them could adversely affect the security of the system. +If the value of "config_value" is "1", review the system documentation to determine whether the use of "Remote Data Archive" is required and authorized. If it is not authorized, this is a finding.SRG-APP-000141-DB-000092<GroupDescription></GroupDescription>SQL6-D0-017700SQL Server External Scripts Enabled feature must be disabled, unless specifically required and approved.<VulnDiscussion>SQL Server is capable of providing a wide range of features and services. Some of the features and services, provided by default, may not be necessary, and enabling them could adversely affect the security of the system. The External Scripts Enabled feature allows scripts external to SQL such as files located in an R library to be executed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-94053V-79347CCI-000381Disable use of or remove any external application executable object definitions that are not authorized. To disable the use of "External Scripts Enabled" option, from the query prompt:  @@ -3131,7 +3130,7 @@ EXEC SP_CONFIGURE 'external scripts enabled'; If the value of "config_value" is "0", this is not a finding. -If the value of "config_value" is "1", review the system documentation to determine whether the use of "External Scripts Enabled" is required and authorized. If it is not authorized, this is a finding.SRG-APP-000516-DB-000363<GroupDescription></GroupDescription>SQL6-D0-017800The SQL Server Browser service must be disabled unless specifically required and approved.<VulnDiscussion>The SQL Server Browser simplifies the administration of SQL Server, particularly when multiple instances of SQL Server coexist on the same computer. It avoids the need to hard-assign port numbers to the instances and to set and maintain those port numbers in client systems. It enables administrators and authorized users to discover database management system instances, and the databases they support, over the network. SQL Server uses the SQL Server Browser service to enumerate instances of the Database Engine installed on the computer. This enables client applications to browse for a server, and helps clients distinguish between multiple instances of the Database Engine on the same computer. +If the value of "config_value" is "1", review the system documentation to determine whether the use of "External Scripts Enabled" is required and authorized. If it is not authorized, this is a finding.SRG-APP-000516-DB-000363<GroupDescription></GroupDescription>SQL6-D0-017800The SQL Server Browser service must be disabled unless specifically required and approved.<VulnDiscussion>The SQL Server Browser simplifies the administration of SQL Server, particularly when multiple instances of SQL Server coexist on the same computer. It avoids the need to hard-assign port numbers to the instances and to set and maintain those port numbers in client systems. It enables administrators and authorized users to discover database management system instances, and the databases they support, over the network. SQL Server uses the SQL Server Browser service to enumerate instances of the Database Engine installed on the computer. This enables client applications to browse for a server, and helps clients distinguish between multiple instances of the Database Engine on the same computer. This convenience also presents the possibility of unauthorized individuals gaining knowledge of the available SQL Server resources. Therefore, it is necessary to consider whether the SQL Server Browser is needed. Typically, if only a single instance is installed, using the default name (MSSQLSERVER) and port assignment (1433), the Browser is not adding any value. The more complex the installation, the more likely SQL Server Browser is to be helpful. @@ -3147,7 +3146,7 @@ Either navigate, via the Windows Start Menu and/or Control Panel, to "Administra Scroll to "SQL Server Browser". -If its Startup Type is not shown as "Disabled", this is a finding.SRG-APP-000141-DB-000092<GroupDescription></GroupDescription>SQL6-D0-017900SQL Server Replication Xps feature must be disabled, unless specifically required and approved.<VulnDiscussion>SQL Server is capable of providing a wide range of features and services. Some of the features and services, provided by default, may not be necessary, and enabling them could adversely affect the security of the system. +If its Startup Type is not shown as "Disabled", this is a finding.SRG-APP-000141-DB-000092<GroupDescription></GroupDescription>SQL6-D0-017900SQL Server Replication Xps feature must be disabled, unless specifically required and approved.<VulnDiscussion>SQL Server is capable of providing a wide range of features and services. Some of the features and services, provided by default, may not be necessary, and enabling them could adversely affect the security of the system. Enabling the replication XPs opens a significant attack surface area that can be used by an attacker to gather information about the system and potentially abuse the privileges of SQL Server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-94057V-79351CCI-000381Disable use of or remove any external application executable object definitions that are not authorized. To disable the use of "Replication Xps" option, from the query prompt:  @@ -3166,7 +3165,7 @@ EXEC SP_CONFIGURE 'replication xps'; If the value of "config_value" is "0", this is not a finding. -If the value of "config_value" is "1", review the system documentation to determine whether the use of "Replication Xps" is required and authorized. If it is not authorized, this is a finding.SRG-APP-000516-DB-000363<GroupDescription></GroupDescription>SQL6-D0-018000If the SQL Server Browser Service is specifically required and approved, SQL instances must be hidden.<VulnDiscussion>The SQL Server Browser simplifies the administration of SQL Server, particularly when multiple instances of SQL Server coexist on the same computer. It avoids the need to hard-assign port numbers to the instances and to set and maintain those port numbers in client systems. It enables administrators and authorized users to discover database management system instances, and the databases they support, over the network. SQL Server uses the SQL Server Browser service to enumerate instances of the Database Engine installed on the computer. This enables client applications to browse for a server, and helps clients distinguish between multiple instances of the Database Engine on the same computer. +If the value of "config_value" is "1", review the system documentation to determine whether the use of "Replication Xps" is required and authorized. If it is not authorized, this is a finding.SRG-APP-000516-DB-000363<GroupDescription></GroupDescription>SQL6-D0-018000If the SQL Server Browser Service is specifically required and approved, SQL instances must be hidden.<VulnDiscussion>The SQL Server Browser simplifies the administration of SQL Server, particularly when multiple instances of SQL Server coexist on the same computer. It avoids the need to hard-assign port numbers to the instances and to set and maintain those port numbers in client systems. It enables administrators and authorized users to discover database management system instances, and the databases they support, over the network. SQL Server uses the SQL Server Browser service to enumerate instances of the Database Engine installed on the computer. This enables client applications to browse for a server, and helps clients distinguish between multiple instances of the Database Engine on the same computer. This convenience also presents the possibility of unauthorized individuals gaining knowledge of the available SQL Server resources. Therefore, it is necessary to consider whether the SQL Server Browser is needed. Typically, if only a single instance is installed, using the default name (MSSQLSERVER) and port assignment (1433), the Browser is not adding any value. The more complex the installation, the more likely SQL Server Browser is to be helpful. @@ -3189,7 +3188,7 @@ SELECT CASE If the value of "Hidden" is "Yes", this is not a finding. -If the value of "Hidden" is "No" and the startup type of the "SQL Server Browser" service is not "Disabled", this is a finding.SRG-APP-000178-DB-000083<GroupDescription></GroupDescription>SQL6-D0-018100When using command-line tools such as SQLCMD in a mixed-mode authentication environment, users must use a logon method that does not expose the password.<VulnDiscussion>To prevent the compromise of authentication information, such as passwords and PINs, during the authentication process, the feedback from the information system must not provide any information that would allow an unauthorized user to compromise the authentication mechanism. +If the value of "Hidden" is "No" and the startup type of the "SQL Server Browser" service is not "Disabled", this is a finding.SRG-APP-000178-DB-000083<GroupDescription></GroupDescription>SQL6-D0-018100When using command-line tools such as SQLCMD in a mixed-mode authentication environment, users must use a logon method that does not expose the password.<VulnDiscussion>To prevent the compromise of authentication information, such as passwords and PINs, during the authentication process, the feedback from the information system must not provide any information that would allow an unauthorized user to compromise the authentication mechanism. Obfuscation of user-provided information when typed into the system is a method used in addressing this risk. @@ -3212,7 +3211,7 @@ If the config_value returned is "Windows NT Authentication", this is not a findi For SQLCMD, which cannot be configured not to accept a plain-text password, and any other essential tool with the same limitation, verify that the system documentation explains the need for the tool, who uses it, and any relevant mitigations; and that AO approval has been obtained; if not, this is a finding. -Request evidence that all users of the tool are trained in the importance of not using the plain-text password option and in how to keep the password hidden; and that they adhere to this practice; if not, this is a finding.SRG-APP-000178-DB-000083<GroupDescription></GroupDescription>SQL6-D0-018200Applications must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.<VulnDiscussion>To prevent the compromise of authentication information, such as passwords and PINs, during the authentication process, the feedback from the information system must not provide any information that would allow an unauthorized user to compromise the authentication mechanism. +Request evidence that all users of the tool are trained in the importance of not using the plain-text password option and in how to keep the password hidden; and that they adhere to this practice; if not, this is a finding.SRG-APP-000178-DB-000083<GroupDescription></GroupDescription>SQL6-D0-018200Applications must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.<VulnDiscussion>To prevent the compromise of authentication information, such as passwords and PINs, during the authentication process, the feedback from the information system must not provide any information that would allow an unauthorized user to compromise the authentication mechanism. Obfuscation of user-provided information when typed into the system is a method used in addressing this risk. @@ -3220,16 +3219,13 @@ For example, displaying asterisks when a user types in a password or PIN, is an Database applications may allow for entry of the account name and password as a visible parameter of the application execution command. This practice must be prohibited and disabled to prevent shoulder surfing.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993SV-94063V-79357CCI-000206Configure or modify applications to prohibit display of passwords in clear text.Determine whether any applications that access the database allow for entry of the account name and password, or PIN. -If any do, determine whether these applications obfuscate authentication data; if they do not, this is a finding.SRG-APP-000456-DB-000400<GroupDescription></GroupDescription>SQL6-D0-018300Microsoft SQL Server products must be a version supported by the vendor.<VulnDiscussion>Unsupported commercial and database systems should not be used because fixes to newly identified bugs will not be implemented by the vendor. The lack of support can result in potential vulnerabilities. +If any do, determine whether these applications obfuscate authentication data; if they do not, this is a finding.SRG-APP-000456-DB-000400<GroupDescription></GroupDescription>SQL6-D0-018300Microsoft SQL Server products must be a version supported by the vendor.<VulnDiscussion>Unsupported commercial and database systems should not be used because fixes to newly identified bugs will not be implemented by the vendor. The lack of support can result in potential vulnerabilities. Systems at unsupported servicing levels or releases will not receive security updates for new vulnerabilities, which leaves them subject to exploitation. -When maintenance updates and patches are no longer available, the database software is no longer considered supported and should be upgraded or decommissioned.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993CCI-003376Remove or decommission all unsupported software products. - -Upgrade unsupported DBMS or unsupported components to a supported version of the product. +When maintenance updates and patches are no longer available, the database software is no longer considered supported and should be upgraded or decommissioned.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target MS SQL Server 2016 InstanceDISADPMS TargetMS SQL Server 2016 Instance3993CCI-003376Remove or decommission all unsupported software products. -More information can be found here: -https://learn.microsoft.com/en-us/sql/sql-server/end-of-support/sql-server-end-of-support-overview?view=sql-server-ver16Review the system documentation and interview the database administrator. +Upgrade unsupported DBMS or unsupported components to a supported version of the product.Review the system documentation and interview the database administrator. Identify all database software components. diff --git a/source/StigData/Processed/SqlServer-2016-Instance-2.11.org.default.xml b/source/StigData/Processed/SqlServer-2016-Instance-3.1.org.default.xml similarity index 81% rename from source/StigData/Processed/SqlServer-2016-Instance-2.11.org.default.xml rename to source/StigData/Processed/SqlServer-2016-Instance-3.1.org.default.xml index aac866a53..b308f469c 100644 --- a/source/StigData/Processed/SqlServer-2016-Instance-2.11.org.default.xml +++ b/source/StigData/Processed/SqlServer-2016-Instance-3.1.org.default.xml @@ -5,9 +5,9 @@ Each setting in this file is linked by STIG ID and the valid range is in an associated comment. --> - + - + diff --git a/source/StigData/Processed/SqlServer-2016-Instance-2.11.xml b/source/StigData/Processed/SqlServer-2016-Instance-3.1.xml similarity index 98% rename from source/StigData/Processed/SqlServer-2016-Instance-2.11.xml rename to source/StigData/Processed/SqlServer-2016-Instance-3.1.xml index b7e5d3f7b..3b255bb35 100644 --- a/source/StigData/Processed/SqlServer-2016-Instance-2.11.xml +++ b/source/StigData/Processed/SqlServer-2016-Instance-3.1.xml @@ -1,4 +1,4 @@ - + <VulnDiscussion>Database management includes the ability to control the number of users and user sessions utilizing SQL Server. Unlimited concurrent connections to SQL Server could allow a successful Denial of Service (DoS) attack by exhausting connection resources; and a system can also fail or be degraded by an overload of legitimate users. Limiting the number of concurrent sessions per user is helpful in reducing these risks. @@ -579,17 +579,17 @@ To determine whether SQL Server is configured to use a fixed port or dynamic por If these are in conflict with PPSM guidance, and not explained and approved in the system documentation, this is a finding. - <VulnDiscussion>OS/enterprise authentication and identification must be used (SRG-APP-000023-DB-000001). Native DBMS authentication may be used only when circumstances make it unavoidable; and must be documented and AO-approved. + <VulnDiscussion>OS/enterprise authentication and identification must be used (SRG-APP-000023-DB-000001). Native DBMS authentication may be used only when circumstances make it unavoidable, and must be documented and Authorizing Official (AO)-approved. -The DoD standard for authentication is DoD-approved PKI certificates. Authentication based on User ID and Password may be used only when it is not possible to employ a PKI certificate, and requires AO approval. +The DOD standard for authentication is DOD-approved PKI certificates. Authentication based on User ID and Password may be used only when it is not possible to employ a PKI certificate, and requires AO approval. -In such cases, the DoD standards for password complexity and lifetime must be implemented. DBMS products that can inherit the rules for these from the operating system or access control program (e.g., Microsoft Active Directory) must be configured to do so. For other DBMSs, the rules must be enforced using available configuration parameters or custom code.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +In such cases, the DOD standards for password complexity and lifetime must be implemented. DBMS products that can inherit the rules for these from the operating system or access control program (e.g., Microsoft Active Directory) must be configured to do so. For other DBMSs, the rules must be enforced using available configuration parameters or custom code.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False V-79193 False - Execute the following query to determine if Contained Databases are used: + Execute the following query to determine if contained databases are used: SELECT * FROM sys.databases WHERE containment = 1 @@ -664,21 +664,27 @@ For each user database where encryption is required, verify that encryption is i Verify that there are physical security measures, operating system access control lists and organizational controls appropriate to the sensitivity level of the data in the database(s). If not, this is a finding. - <VulnDiscussion>The purpose of this control is to prevent information, including encrypted representations of information, produced by the actions of a prior user/role (or the actions of a process acting on behalf of a prior user/role) from being available to any current user/role (or current process) that obtains access to a shared system resource (e.g., registers, main memory, secondary storage) after the resource has been released back to the information system. Control of information in shared resources is also referred to as object reuse.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + <VulnDiscussion>The purpose of this control is to prevent information, including encrypted representations of information, produced by the actions of a prior user/role (or the actions of a process acting on behalf of a prior user/role) from being available to any current user/role (or current process) that obtains access to a shared system resource (e.g., registers, main memory, secondary storage) after the resource has been released back to the information system. Control of information in shared resources is also referred to as object reuse. + +When Instant File Initialization (IFI) is in use, the deleted disk content is overwritten only as new data is written to the files. For this reason, the deleted content might be accessed by an unauthorized principal until some other data writes on that specific area of the data file.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False V-79213 False - Review the system documentation to determine if Instant File Initialization (IFI) is required. + Review system configuration to determine whether IFI support has been enabled (by default in SQL Server 2016). + +Start >> Control Panel >> System and Security >> Administrative Tools >> Local Security Policy >> Local Policies >> User Rights Assignment >> Perform volume maintenance tasks + +The default SQL service account for a default instance is NT SERVICE\MSSQLSERVER or for a named instance is NT SERVICE\MSSQL$InstanceName. -If IFI is documented as required, this is not a finding. +If the SQL service account or SQL service SID has been granted "Perform volume maintenance tasks" Local Rights Assignment, this means that Instant File Initialization (IFI) is enabled. -Review system configuration to determine whether IFI support has been enabled (by default in SQL Server 2016). +Review the system documentation to determine if Instant File Initialization (IFI) is required. -Start >> Control Panel >> Administrative Tools >> Local Security Policy >> Local Policies >> User Rights Assignment +If IFI is enabled but not documented as required, this is a finding. -If the SQL Service SID (Default instance: NT SERVICE\MSSQLSERVER. Named instance: NT SERVICE\MSSQL$InstanceName) has been granted "Perform volume maintenance tasks" Local Rights Assignment and if it is not documented in the system documentation, this is a finding. +If IFI is not enabled, this is not a finding. <VulnDiscussion>SQL Server must prevent unauthorized and unintended information transfer via shared system resources. Permitting only SQL Server processes and authorized, administrative users to have access to the files where the database resides helps ensure that those files are not shared inappropriately and are not open to backdoor access and manipulation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> @@ -840,34 +846,6 @@ WHERE P.enabled = 1 GO If any Credentials or SQL Agent Proxy accounts are returned that are not documented and authorized, this is a finding. - - - <VulnDiscussion>Without the ability to centrally manage the content captured in the audit records, identification, troubleshooting, and correlation of suspicious behavior would be difficult and could lead to a delayed or incomplete analysis of an ongoing attack. - -The content captured in audit records must be managed from a central location (necessitating automation). Centralized management of audit records and logs provides for efficiency in maintenance and management of records, as well as the backup and archiving of those records. - -SQL Server may write audit records to database tables, to files in the file system, to other kinds of local repository, or directly to a centralized log management system. Whatever the method used, it must be compatible with off-loading the records to the centralized system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - V-79223 - False - - Review the system documentation for a description of how audit records are off-loaded and how local audit log space is managed. - -If the SQL Server audit records are not written directly to or systematically transferred to a centralized log management system, this is a finding. - - - <VulnDiscussion>If the configuration of SQL Server's auditing is spread across multiple locations in the database management software, or across multiple commands, only loosely related, it is harder to use and takes longer to reconfigure in response to events. - -SQL Server must provide a unified tool for audit configuration.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> - - False - V-79225 - False - - Review the system documentation for a description of how audit records are off-loaded and how local audit log space is managed. - -If the SQL Server audit records (to include traces used for audit purposes) are not written directly to or systematically transferred to a centralized log management system, this is a finding. <VulnDiscussion>If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis. @@ -1288,7 +1266,7 @@ For SQLCMD, which cannot be configured not to accept a plain-text password, and Request evidence that all users of the tool are trained in the importance of not using the plain-text password option and in how to keep the password hidden; and that they adhere to this practice; if not, this is a finding. - + <VulnDiscussion>Unsupported commercial and database systems should not be used because fixes to newly identified bugs will not be implemented by the vendor. The lack of support can result in potential vulnerabilities. Systems at unsupported servicing levels or releases will not receive security updates for new vulnerabilities, which leaves them subject to exploitation. @@ -1539,35 +1517,35 @@ If any nodes have a certificate in use by SQL that is not issued or approved by - <VulnDiscussion>Backup and recovery of the Service Master Key may be critical to the complete recovery of the database. Creating this backup should be one of the first administrative actions performed on the server. Not having this key can lead to loss of data during recovery.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + <VulnDiscussion>Backup and recovery of the Service Master Key may be critical to the complete recovery of the database. Creating this backup should be one of the first administrative actions performed on the server. Not having this key can lead to loss of data during recovery.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False V-79207 False - Review procedures for, and evidence of backup of, the Server Service Master Key in the System Security Plan. - -If the procedures or evidence does not exist, this is a finding. + Review procedures for and evidence of backup of the Server Service Master Key in the System Security Plan. -If the procedures do not indicate offline and off-site storage of the Service Master Key, this is a finding. +If the procedures or evidence does not exist, this is a finding. +If the procedures do not indicate that a backup of the Service Master Key is stored in a secure location that is not on the SQL Server, this is a finding. + If procedures do not indicate access restrictions to the Service Master Key backup, this is a finding. - <VulnDiscussion>Backup and recovery of the Master Key may be critical to the complete recovery of the database. Not having this key can lead to loss of data during recovery.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> + <VulnDiscussion>Backup and recovery of the Master Key may be critical to the complete recovery of the database. Not having this key can lead to loss of data during recovery.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False V-79209 False - If the application owner and Authorizing Official have determined that encryption of data at rest is not required, this is not a finding. + If the application owner and authorizing official have determined that encryption of data at rest is not required, this is not a finding. -Review procedures for, and evidence of backup of, the Master Key in the System Security Plan. +Review procedures for and evidence of backup of the Master Key in the System Security Plan. If the procedures or evidence does not exist, this is a finding. -If the procedures do not indicate offline and off-site storage of the Master Key, this is a finding. - +If the procedures do not indicate that a backup of the Master Key is stored in a secure location that is not on the SQL Server, this is a finding. + If procedures do not indicate access restrictions to the Master Key backup, this is a finding. @@ -2686,11 +2664,15 @@ If any of these databases exist, this is a finding. - <VulnDiscussion>OS/enterprise authentication and identification must be used (SRG-APP-000023-DB-000001). Native DBMS authentication may be used only when circumstances make it unavoidable; and must be documented and AO-approved. + <VulnDiscussion>Windows Authentication is the default authentication mode and is much more secure than SQL Server Authentication. Windows Authentication uses Kerberos security protocol, provides password policy enforcement with regard to complexity validation for strong passwords, provides support for account lockout, and supports password expiration. A connection made using Windows Authentication is sometimes called a trusted connection, because SQL Server trusts the credentials provided by Windows. + +By using Windows Authentication, Windows groups can be created at the domain level, and a login can be created on SQL Server for the entire group. Managing access at the domain level can simplify account administration. + +OS/enterprise authentication and identification must be used (SRG-APP-000023-DB-000001). Native SQL Server authentication may be used only when circumstances make it unavoidable and must be documented and Authorizing Official (AO)-approved. -The DoD standard for authentication is DoD-approved PKI certificates. Authentication based on User ID and Password may be used only when it is not possible to employ a PKI certificate, and requires AO approval. +The DOD standard for authentication is DOD-approved PKI certificates. Authentication based on User ID and Password may be used only when it is not possible to employ a PKI certificate and requires AO approval. -In such cases, the DoD standards for password complexity and lifetime must be implemented. DBMS products that can inherit the rules for these from the operating system or access control program (e.g., Microsoft Active Directory) must be configured to do so. For other DBMSs, the rules must be enforced using available configuration parameters or custom code.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> +In such cases, the DOD standards for password complexity and lifetime must be implemented. DBMS products that can inherit the rules for these from the operating system or access control program (e.g., Microsoft Active Directory) must be configured to do so. For other DBMSs, the rules must be enforced using available configuration parameters or custom code.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls> False @@ -2706,9 +2688,9 @@ In such cases, the DoD standards for password complexity and lifetime must be im SELECT CASE SERVERPROPERTY('IsIntegratedSecurityOnly') WHEN 1 THEN 'Windows Authentication' WHEN 0 THEN 'SQL Server Authentication' END as [Authentication Mode] -If the returned value in the "[Authentication Mode]" column is "Windows Authentication", this is not a finding. +If the returned value in the "Authentication Mode" column is "Windows Authentication", this is not a finding. -SQL Server should be configured to inherit password complexity and password lifetime rules from the operating system. +If the returned value in the "Authentication Mode" column is "SQL Server Authentication", SQL Server should be configured to inherit password complexity and password lifetime rules from the operating system. Review SQL Server to ensure logons are created with respect to the complexity settings and password lifetime rules by running the statement: @@ -2719,15 +2701,13 @@ Review any accounts returned by the query other than the disabled SA account, ## If any account does not have both "is_expiration_checked" and "is_policy_checked" equal to “1”, this is a finding. -Review the Operating System settings relating to password complexity. - -Determine whether the following rules are enforced. If any are not, this is a finding. +Review the operating system settings relating to password complexity. -Check the server operating system for password complexity: +To check the server operating system for password complexity: -Navigate to Start >> All Programs >> Administrative Tools >> Local Security Policy, and to review the local policies on the machine, go to Account Policy >> Password Policy:. +Navigate to Start >> All Programs >> Administrative Tools >> Local Security Policy, and to review the local policies on the machine, go to Account Policy >> Password Policy. -Ensure the DISA Windows Password Policy is set on the SQL Server member server. +Ensure the DISA Windows Password Policy is set on the SQL Server member server. If any are not, this is a finding. @@ -2917,7 +2897,7 @@ If the calculated product of the "max_file_size" times the "max_rollover_files" - <VulnDiscussion>Without auditing the enforcement of access restrictions against changes to configuration, it would be difficult to identify attempted attacks and an audit trail would not be available for forensic investigation for after-the-fact actions. + <VulnDiscussion>Without auditing the enforcement of access restrictions against changes to configuration, it would be difficult to identify attempted attacks and an audit trail would not be available for forensic investigation for after-the-fact actions. Enforcement actions are the methods or mechanisms used to prevent unauthorized changes to configuration settings. Enforcement action methods may be as simple as denying access to a file based on the application of file permissions (access restriction). Audit items may consist of lists of actions blocked by access restrictions or changes identified after the fact.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>