{"stig":{"title":"Microsoft SQL Server 2022 Instance Security Technical Implementation Guide","version":"1","release":"4"},"checks":[{"vulnId":"V-271263","ruleId":"SV-271263r1108405_rule","severity":"medium","ruleTitle":"SQL Server must limit the number of concurrent sessions to an organization-defined number per user for all accounts and/or account types.","description":"Database management includes the ability to control the number of users and user sessions using a DBMS. Unlimited concurrent connections to the DBMS 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.\n\nThis 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.\n\nThe capability to limit the number of concurrent sessions per user must be configured in or added to the DBMS (for example, by use of a logon trigger), when this is technically feasible. Note that it is not sufficient to limit sessions via a web server or application server alone, because legitimate users and adversaries can potentially connect to the DBMS by other means.\n\nThe 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, two 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.\n\nSessions may also be referred to as connections or logons, which for the purposes of this requirement are synonyms.","checkContent":"Review the system documentation to determine whether any concurrent session limits have been defined. If it does not, assume a limit of 10 for database administrators and two for all other users. \n \nIf 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.\n\nDue to excessive CPU consumption when using a logon trigger, an alternative method of limiting concurrent sessions is setting the max connection limit within SQL Server to an appropriate value. This serves to block a distributed denial-of-service (DDOS) attack by limiting the attacker's connections while allowing a database administrator to still force a SQL connection.\n\nIn SQL Server Management Studio's Object Explorer tree, right-click on the Server Name >> Properties >> Connections Tab.\n\nOR\n\nRun the query:\nEXEC sys.sp_configure N'user connections'\n\nIf the max connection limit is set to 0 (unlimited) or does not match the documented value, this is a finding.\n \nOtherwise, determine if a logon trigger exists: \n \nIn SQL Server Management Studio's Object Explorer tree, expand [SQL Server Instance] >> Server Objects >> Triggers.\n \nOR \n \nRun the query: \nSELECT name FROM master.sys.server_triggers; \n \nIf no triggers are listed, this is a finding. \n \nIf triggers are listed, identify the trigger(s) limiting the number of concurrent sessions per user. If none are found, this is a finding. If they are present but disabled, this is a finding. \n \nExamine the trigger source code for logical correctness and for compliance with the documented limit(s). If errors or variances exist, this is a finding.\n \nVerify 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.","fixText":"If a trigger consumes too much CPU, an example alternative method for limiting the concurrent users is setting the max connection limit on SQL Server.\n\nIn SQL Server Management Studio's Object Explorer tree, right-click on the Server Name >> Properties >> Connections Tab >> Set the Maximum Number of Concurrent Connections to a value other than 0 (0 = unlimited), and document it.\n\nOR\n\nRun the query:\n\nEXEC sys.sp_configure N'user connections','5000' /* this is an example max limit */\nGO\nRECONFIGURE WITH OVERRIDE\nGO\n\nRestart SQL Server for the setting to take effect.\n\nReference: https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/configure-the-user-connections-server-configuration-option?\n\nOtherwise, establish 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. \n\nExample script:\n \nCREATE TRIGGER SQL_STIG_Connection_Limit \nON ALL SERVER WITH EXECUTE AS 'renamed_sa' /*Make sure to use the renamed SA account here*/ \nFOR LOGON \nAS \nBEGIN \nIf (Select COUNT(1) from sys.dm_exec_sessions WHERE is_user_process = 1 AND original_login_name = ORIGINAL_LOGIN() ) > \n (CASE ORIGINAL_LOGIN()\n WHEN 'domain/ima.dba' THEN 150 /*this is a busy DBA's domain account */\n WHEN 'application1_login' THEN 6 /* this is a SQL login for an application */\n WHEN 'application2_login' THEN 20 /* this is a SQL login for another application */\n …\n ELSE 1 /* All unspecified users are restricted to a single login */\n END)\n BEGIN \n PRINT 'The login [' + ORIGINAL_LOGIN() + '] has exceeded its concurrent session limit.' \n ROLLBACK; \n END\nEND; \n \nReference: https://msdn.microsoft.com/en-us/library/ms189799.aspx","ccis":["CCI-000054"]},{"vulnId":"V-271264","ruleId":"SV-271264r1111061_rule","severity":"high","ruleTitle":"SQL Server must be configured to use the most-secure authentication method available.","description":"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. \n \nA comprehensive application account management process that includes automation helps to ensure that accounts designated as requiring attention are consistently and promptly addressed. \n \nExamples include, but are not limited to, using automation to act on multiple accounts designated as inactive, suspended, or terminated, or by disabling accounts located in noncentralized account stores, such as multiple servers. Account management functions can also include assignment of group or role membership; identifying account type; specifying user access authorizations (i.e., privileges); account removal, update, or termination; and administrative alerts. The use of automated mechanisms can include, for example: using email or text messaging to notify account managers when users are terminated or transferred; using the information system to monitor account usage; and using automated telephone notification to report atypical system account usage. \n \nSQL Server must be configured to automatically use organization-level account management functions, and these functions must immediately enforce the organization's current account policy. \n \nAutomation may comprise differing technologies that when placed together contain an overall mechanism supporting an organization's automated account management requirements. \n \nSQL Server supports several authentication methods to allow operation in various environments, Kerberos, NTLM, and SQL Server. An instance of SQL Server must be configured to use the most secure method available. Service accounts used by SQL Server should be unique to a given instance.","checkContent":"If the SQL Server is not part of an Active Directory domain, this is Not Applicable. \n\nObtain the fully qualified domain name of the SQL Server instance: \n\n1. Launch Windows Explorer. \n2. Right-click \"Computer\" or \"This PC\" (Varies by OS level). \n3. Click \"Properties\". Note the value shown for \"Full computer name\". \n\nNote: For a cluster, this value must be obtained from the Failover Cluster Manager.\n\nObtain the TCP port that is supporting the SQL Server instance:\n \n1. Click \"Start\".\n2. Type \"SQL Server 2022 Configuration Manager\".\n3. From the search results, click \"SQL Server 2022 Configuration Manager\". \n4. From the tree on the left, expand \"SQL Server Network Configuration\". \n5. Click \"Protocols for \" where is the name of the instance (MSSQLSERVER is the default name). \n6. In the right pane, right-click \"TCP/IP\" and choose \"Properties\". \n7. In the window that opens, click the \"IP Addresses\" tab. Note the TCP port configured for the instance. \n\nObtain the service account that is running the SQL Server service: \n\n1. Click \"Start\". \n2. Type \"SQL Server 2022 Configuration Manager\". \n3. From the search results, click \"SQL Server 2022 Configuration Manager\". \n4. From the tree on the left, select \"SQL Server Services\". Note the account listed in the \"Log On As\" column for the SQL Server instance being reviewed. \n5. Launch a command-line or PowerShell window. \n6. Enter the following command where is the identity of the service account:\n setspn -L \n Example: setspn -L CONTOSO\\sql2016svc \n7. Review the Registered Service Principal Names returned. \n\nIf the listing does not contain the following supported service principal names (SPN) formats, this is a finding. \n\nNamed instance\n MSSQLSvc/:[ | ], where:\n MSSQLSvc is the service that is being registered.\n is the fully qualified domain name of the server.\n is the TCP port number.\n is the name of the SQL Server instance.\n\nDefault instance\n MSSQLSvc/: | MSSQLSvc/, where:\n MSSQLSvc is the service that is being registered.\n is the fully qualified domain name of the server.\n is the TCP port number.\n\nIf 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.","fixText":"Ensure Service Principal Names (SPNs) are properly registered for the SQL Server instance. \n\nUse the Microsoft Kerberos Configuration Manager to review Kerberos configuration issues for a given SQL Server instance. \n\nhttps://www.microsoft.com/en-us/download/details.aspx?id=39046 \n\nAlternatively, SPNs for SQL Server can be manually registered. \n\nFor other connections that support Kerberos the SPN is registered in the format MSSQLSvc// for a named instance. The format for registering the default instance is MSSQLSvc/.\n\nUsing an account with permissions to register SPNs, issue the following commands from a command-prompt: \n\nsetspn -S MSSQLSvc/ \nsetspn -S MSSQLSvc/: \nFor a named instance, use:\nsetspn -S MSSQLSvc/: \nsetspn -S MSSQLSvc/: \n\nRestart the SQL Server instance. \n\nMore information regarding this process is available at https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/register-a-service-principal-name-for-kerberos-connections#Manual.","ccis":["CCI-000015"]},{"vulnId":"V-271265","ruleId":"SV-271265r1108933_rule","severity":"high","ruleTitle":"SQL Server must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals.","description":"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. \n \nA comprehensive application account management process that includes automation helps to ensure that accounts designated as requiring attention are consistently and promptly addressed. \n \nExamples include, but are not limited to, using automation to act on multiple accounts designated as inactive, suspended, or terminated, or by disabling accounts located in noncentralized account stores, such as multiple servers. Account management functions can also include assignment of group or role membership; identifying account type; specifying user access authorizations (i.e., privileges); account removal, update, or termination; and administrative alerts. The use of automated mechanisms can include, for example, using email or text messaging to notify account managers when users are terminated or transferred; using the information system to monitor account usage; and using automated telephone notification to report atypical system account usage. \n \nSQL Server must be configured to automatically use organization-level account management functions, and these functions must immediately enforce the organization's current account policy. \n \nAutomation may be composed of differing technologies that when placed together contain an overall mechanism supporting an organization's automated account management requirements.","checkContent":"Determine whether SQL Server is configured to use only Windows authentication. \n \nIn the Object Explorer in SQL Server Management Studio (SSMS), right-click on the server instance. \nSelect \"Properties\", then select the Security page. \n \nIf Windows Authentication Mode is selected, this is not a finding. \n \nOR \n \nIn a query interface such as the SSMS Transact-SQL editor, run the statement: \nSELECT CASE SERVERPROPERTY('IsIntegratedSecurityOnly') \nWHEN 1 THEN 'Windows Authentication' \nWHEN 0 THEN 'Windows and SQL Server Authentication' \nEND as [Authentication Mode] \n \nIf the returned value in the \"Authentication Mode\" column is \"Windows Authentication\", this is not a finding. \n \nMixed mode (both SQL Server authentication and Windows authentication) is in use. If the need for mixed mode has not been documented and approved by the information system security officer (ISSO)/information system security manager (ISSM), this is a finding. \n \nFrom the documentation, obtain the list of accounts authorized to be managed by SQL Server. \n \nDetermine the accounts (SQL Logins) actually managed by SQL Server. Run the statement: \n \nSELECT name \nFROM sys.sql_logins \nWHERE type_desc = 'SQL_LOGIN' AND is_disabled = 0; \n \nIf any accounts listed by the query are not listed in the documentation, this is a finding.","fixText":"If mixed mode is required, document the need and justification; describe the measures taken to ensure the use of SQL Server authentication is kept to a minimum; describe the measures taken to safeguard passwords; and list or describe the SQL Logins used.\n\nDocumentation must be approved by the ISSO/ISSM.\n \nIf mixed mode is not required, disable it as follows: \n \n1. In the SSMS Object Explorer, right-click on the server instance. \n2. Select Properties >> Security page.\n3. Click the radio button for \"Windows Authentication Mode\".\n4. Click \"OK\". \n5. Restart the SQL Server instance. \n \nOR \n \nRun the statement: \n\nUSE [master] \nEXEC xp_instance_regwrite N'HKEY_LOCAL_MACHINE', N'Software\\Microsoft\\MSSQLServer\\MSSQLServer', N'LoginMode', REG_DWORD, 2 \nGO \n \nRestart the SQL Server instance. \n \nFor each account being managed by SQL Server but not requiring it, drop or disable the SQL Login. Replace it with an appropriately configured account, as needed. \n \nTo drop or disable a login in the SSMS Object Explorer, navigate to \"Security Logins\". \nRight-click on the login name and click \"Delete\" or \"Disable\". \n \nTo drop or disable a login by using a query: \n\nUSE master; \nDROP LOGIN login_name; \nALTER LOGIN login_name DISABLE; \n \nDropping a login does not delete the equivalent database user(s). There may be more than one database containing a user mapped to the login. Drop the user(s) unless still needed. \n \nTo drop a user in the SSMS Object Explorer: \nNavigate to Databases >> Security Users. \nRight-click on the username. \nClick \"Delete\". \n \nTo drop a user via a query: \n\nUSE database_name; \nDROP USER ;","ccis":["CCI-000015"]},{"vulnId":"V-271266","ruleId":"SV-271266r1137654_rule","severity":"high","ruleTitle":"SQL Server must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.","description":"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. \n \nSuccessful 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. \n \nAccess control policies include identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system. \n \nThis requirement is applicable to access control enforcement applications, a category that includes database management systems. If SQL Server does not follow applicable policy when approving access, it may be in conflict with networks or other applications in the information system. This may result in users either gaining or being denied access inappropriately and in conflict with applicable policy.","checkContent":"Review the system documentation to determine the required levels of protection for DBMS server securables by type of login. \n \nReview the permissions in place on the server. \n \nIf the permissions do not match the documented requirements, this is a finding. \n \nUse the supplemental file \"Instance permissions assignments to logins and roles.sql\".","fixText":"Use GRANT, REVOKE, DENY, ALTER SERVER ROLE … ADD MEMBER … and/or ALTER SERVER ROLE …. DROP MEMBER statements to add and remove permissions on server-level securables, bringing them into line with the documented requirements.","ccis":["CCI-000213"]},{"vulnId":"V-271267","ruleId":"SV-271267r1108417_rule","severity":"medium","ruleTitle":"SQL Server must protect against a user falsely repudiating by ensuring only clearly unique Active Directory user accounts can connect to the instance.","description":"Nonrepudiation of actions taken is required 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. \n \nNonrepudiation 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. \n \nIn designing a database, the organization must define the types of data and the user actions that must be protected from repudiation. The implementation must then include building audit features into the application data tables and configuring the DBMS's audit tools to capture the necessary audit trail. Design and implementation also must ensure that applications pass individual user identification to the DBMS, even where the application connects to the DBMS with a standard, shared account. \n \nIf the computer account of a remote computer is granted access to SQL Server, any service or scheduled task running as NT AUTHORITY\\SYSTEM or NT AUTHORITY\\NETWORK SERVICE can log into the instance and perform actions. These actions cannot be traced back to a specific user or process.","checkContent":"Execute the following:\n\nSELECT name\nFROM sys.server_principals\nWHERE type in ('U','G')\nAND name LIKE '%$'\n\nIf no logins are returned, this is not a finding.\n\nIf logins are returned, determine whether each login is a computer account.\n\nLaunch PowerShell and execute the following code:\n\nNote: represents the username portion of the login. For example, if the login is \"CONTOSO\\user1$\", the username is \"user1\".\n\n([ADSISearcher]\"(&(ObjectCategory=Computer)(Name=))\").FindAll()\n\nIf no account information is returned, this is not a finding.\n\nIf account information is returned, this is a finding.","fixText":"Remove all logins that were returned in the check content.","ccis":["CCI-000166"]},{"vulnId":"V-271268","ruleId":"SV-271268r1136917_rule","severity":"medium","ruleTitle":"SQL Server must protect against a user falsely repudiating by ensuring the NT AUTHORITY SYSTEM account is not used for administration.","description":"Nonrepudiation of actions taken is required 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. \n \nNonrepudiation 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. \n \nIn designing a database, the organization must define the types of data and the user actions that must be protected from repudiation. The implementation must then include building audit features into the application data tables and configuring the DBMS's audit tools to capture the necessary audit trail. Design and implementation also must ensure that applications pass individual user identification to the DBMS, even where the application connects to the DBMS with a standard, shared account. \n \nAny user with enough access to the server can execute a task that will be run as NT AUTHORITY\\SYSTEM either using task scheduler or other tools. At this point, NT AUTHORITY\\SYSTEM essentially becomes a shared account because the operating system and SQL Server are unable to determine who created the process. \n \nPrior to SQL Server 2012, NT AUTHORITY\\SYSTEM was a member of the sysadmin role by default. This allowed jobs/tasks to be executed in SQL Server without the approval or knowledge of the DBA because it looked like operating system activity.","checkContent":"Execute the following queries. The first query checks for clustering and availability groups being provisioned in the database engine. The second query lists permissions granted to the local system account.\n\nSELECT\n SERVERPROPERTY('IsClustered') AS [IsClustered],\n SERVERPROPERTY('IsHadrEnabled') AS [IsHadrEnabled]\n\nEXECUTE AS LOGIN = 'NT AUTHORITY\\SYSTEM'\n\nSELECT * FROM fn_my_permissions(NULL, 'server')\n\nREVERT\n\nGO\n\nIf \"IsClustered\" returns \"1\", \"IsHadrEnabled\" returns \"0\", and any permissions have been granted to the Local System account beyond \"CONNECT SQL\", \"VIEW SERVER STATE\", \"VIEW ANY DATABASE\", \"VIEW SERVER PERFORMANCE STATE\", and \"VIEW SERVER SECURITY STATE\", this is a finding.\n \nIf \"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\", \"VIEW ANY DATABASE\", \"VIEW SERVER PERFORMANCE STATE\", and \"VIEW SERVER SECURITY STATE\", this is a finding.\n \nIf 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.","fixText":"Remove permissions that were identified as not allowed in the check content.\n\nUSE Master;\n\nREVOKE TO [NT AUTHORITY\\SYSTEM]\n\nGO\n\nTo grant permissions to services or applications, use the Service SID of the service or a domain service account.","ccis":["CCI-000166"]},{"vulnId":"V-271269","ruleId":"SV-271269r1108423_rule","severity":"medium","ruleTitle":"SQL Server must protect against a user falsely repudiating by ensuring all accounts are individual, unique, and not shared.","description":"Nonrepudiation of actions taken is required 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. \n \nNonrepudiation 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. \n \nIn designing a database, the organization must define the types of data and the user actions that must be protected from repudiation. The implementation must then include building audit features into the application data tables and configuring SQL Server's audit tools to capture the necessary audit trail. Design and implementation also must ensure that applications pass individual user identification to SQL Server, even where the application connects to SQL Server with a standard, shared account.\n\nSatisfies: SRG-APP-000080-DB-000063, SRG-APP-000815-DB-000160","checkContent":"Obtain the list of authorized SQL Server accounts in the system documentation. \n \nDetermine if any accounts are shared. A shared account is defined as a username and password that are used by multiple individuals to log into SQL Server. An example of a shared account is the SQL Server installation account. Windows Groups are not shared accounts as the group itself does not have a password. \n \nIf accounts are determined to be shared, determine if individuals are first individually authenticated. \n \nIf individuals are not individually authenticated before using the shared account (e.g., by the operating system or by an application making calls to the database), this is a finding. \n \nThe key is individual accountability. If this can be traced, this is not a finding. \n \nIf accounts are determined to be shared, determine if they are directly accessible to end users. If so, this is a finding. \n \nReview contents of audit logs, traces, and data tables to confirm that the identity of the individual user performing the action is captured. \n \nIf shared identifiers are found and are not accompanied by individual identifiers, this is a finding. \n \nNote: 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.","fixText":"Remove user-accessible shared accounts and use individual user IDs. \n \nBuild/configure applications to ensure successful individual authentication prior to shared account access. \n \nEnsure each user's identity is received and used in audit data in all relevant circumstances. \n \nDesign, develop, and implement a method to log use of any account to which more than one person has access. Restrict interactive access to shared accounts to the fewest persons possible.","ccis":["CCI-000166","CCI-004045"]},{"vulnId":"V-271270","ruleId":"SV-271270r1108426_rule","severity":"medium","ruleTitle":"SQL Server must be configured to generate audit records for DOD-defined auditable events within all DBMS/database components.","description":"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. \n \nAudit 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. \n \nDOD has defined the list of events for which SQL Server will provide an audit record generation capability as the following: \n \n(i) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels); \n \n(ii) Access actions, such as successful and unsuccessful logon attempts, privileged activities, or other system-level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system; and \n \n(iii) All account creation, modification, disabling, and termination actions. \n \nOrganizations may define additional events requiring continuous or ad hoc auditing.","checkContent":"Review the server documentation to determine if any additional events are required to be audited. If no additional events are required, this is not a finding. \n \nExecute the following to get all of the installed audits: \n \nSELECT name AS 'Audit Name', \nstatus_desc AS 'Audit Status', \naudit_file_path AS 'Current Audit File' \nFROM sys.dm_server_audit_status \n \nAll currently defined audits for the SQL server instance will be listed. If no audits are returned, this is a finding. \n \nTo view the actions being audited by the audits, execute the following: \n \nSELECT a.name AS 'AuditName', \ns.name AS 'SpecName', \nd.audit_action_name AS 'ActionName', \nd.audited_result AS 'Result' \nFROM sys.server_audit_specifications s \nJOIN sys.server_audits a ON s.audit_guid = a.audit_guid \nJOIN sys.server_audit_specification_details d ON s.server_specification_id = d.server_specification_id \nWHERE a.is_state_enabled = 1 \n \nCompare the documentation to the list of generated audit events. If there are any missing events, this is a finding.","fixText":"Add all required audit events to the STIG-compliant audit specification server documentation.","ccis":["CCI-000169"]},{"vulnId":"V-271271","ruleId":"SV-271271r1108429_rule","severity":"medium","ruleTitle":"SQL Server must allow only the information system security manager (ISSM) (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited.","description":"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. \n \nSuppression of auditing could permit an adversary to evade detection. \n \nMisconfigured audits can degrade the system's performance by overwhelming the audit log. Misconfigured audits may also make it more difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.","checkContent":"Obtain the list of approved audit maintainers from the system documentation. \n \nReview the server roles and individual logins that have the following role memberships, all of which enable the ability to create and maintain audit definitions. \n \nsysadmin \ndbcreator \n \nReview the server roles and individual logins that have the following permissions, all of which enable the ability to create and maintain audit definitions. \n \nALTER ANY SERVER AUDIT \nCONTROL SERVER \nALTER ANY DATABASE \nCREATE ANY DATABASE \n \nUse the following query to determine the roles and logins that have the listed permissions: \n \nSELECT-- DISTINCT \n CASE \n WHEN SP.class_desc IS NOT NULL THEN \n CASE \n WHEN SP.class_desc = 'SERVER' AND S.is_linked = 0 THEN 'SERVER' \n WHEN SP.class_desc = 'SERVER' AND S.is_linked = 1 THEN 'SERVER (linked)' \n ELSE SP.class_desc \n END \n WHEN E.name IS NOT NULL THEN 'ENDPOINT' \n WHEN S.name IS NOT NULL AND S.is_linked = 0 THEN 'SERVER' \n WHEN S.name IS NOT NULL AND S.is_linked = 1 THEN 'SERVER (linked)' \n WHEN P.name IS NOT NULL THEN 'SERVER_PRINCIPAL' \n ELSE '???' \n END AS [Securable Class], \n CASE \n WHEN E.name IS NOT NULL THEN E.name \n WHEN S.name IS NOT NULL THEN S.name \n WHEN P.name IS NOT NULL THEN P.name \n ELSE '???' \n END AS [Securable], \n P1.name AS [Grantee], \n P1.type_desc AS [Grantee Type], \n sp.permission_name AS [Permission], \n sp.state_desc AS [State], \n P2.name AS [Grantor], \n P2.type_desc AS [Grantor Type], \nR.name AS [Role Name] \nFROM \n sys.server_permissions SP \n INNER JOIN sys.server_principals P1 \n ON P1.principal_id = SP.grantee_principal_id \n INNER JOIN sys.server_principals P2 \n ON P2.principal_id = SP.grantor_principal_id \n \n FULL OUTER JOIN sys.servers S \n ON SP.class_desc = 'SERVER' \n AND S.server_id = SP.major_id \n \n FULL OUTER JOIN sys.endpoints E \n ON SP.class_desc = 'ENDPOINT' \n AND E.endpoint_id = SP.major_id \n \n FULL OUTER JOIN sys.server_principals P \n ON SP.class_desc = 'SERVER_PRINCIPAL' \n AND P.principal_id = SP.major_id \n \nFULL OUTER JOIN sys.server_role_members SRM \nON P.principal_id = SRM.member_principal_id \n \nLEFT OUTER JOIN sys.server_principals R \nON SRM.role_principal_id = R.principal_id \nWHERE sp.permission_name IN ('ALTER ANY SERVER AUDIT','CONTROL SERVER','ALTER ANY DATABASE','CREATE ANY DATABASE') \nOR R.name IN ('sysadmin','dbcreator') \n \nIf 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.","fixText":"Create a server role specifically for audit maintainers and give it permission to maintain audits without granting it unnecessary permissions (the role name used here is an example; other names may be used):\n \nCREATE SERVER ROLE SERVER_AUDIT_MAINTAINERS; \nGO \n \nGRANT ALTER ANY SERVER AUDIT TO SERVER_AUDIT_MAINTAINERS; \nGO \n \nUse REVOKE and/or DENY and/or ALTER SERVER ROLE ... DROP MEMBER ... statements to remove the ALTER ANY SERVER AUDIT permission from all logins. Then, for each authorized login, run the statement:\n \nALTER SERVER ROLE SERVER_AUDIT_MAINTAINERS ADD MEMBER; \nGO \n \nUse REVOKE and/or DENY and/or ALTER SERVER ROLE ... DROP MEMBER ... statements to remove CONTROL SERVER, ALTER ANY DATABASE and CREATE ANY DATABASE permissions from logins that do not need them.","ccis":["CCI-000171"]},{"vulnId":"V-271272","ruleId":"SV-271272r1109110_rule","severity":"medium","ruleTitle":"SQL Server must generate audit records when attempts to access privileges, categorized information, and security objects occur.","description":"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.\n \nThis requirement includes 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. \n\nChanges to the security configuration must also be tracked. \n\nSecurity configuration tracking applies to situations where security data is retrieved or modified via data manipulation operations, as opposed to via specialized security functionality. \n\nIn a SQL environment, types of access include but are not necessarily limited to: \nSELECT \nINSERT \nUPDATE \nDELETE \nEXECUTE\n\nChanges in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. \n \nFor 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.\n \nTo aid in diagnosis, it is necessary to track failed attempts in addition to the successful ones.\n\nSatisfies: SRG-APP-000091-DB-000325, SRG-APP-000091-DB-000066, SRG-APP-000492-DB-000332, SRG-APP-000492-DB-000333, SRG-APP-000494-DB-000344, SRG-APP-000494-DB-000345, SRG-APP-000498-DB-000346, SRG-APP-000498-DB-000347, SRG-APP-000502-DB-000348, SRG-APP-000502-DB-000349, SRG-APP-000507-DB-000356, SRG-APP-000507-DB-000357","checkContent":"Review the system documentation to determine if SQL Server is required to audit when the following events occur:\n\n- Attempts to retrieve privilege/permission/role membership information.\n- Security objects are accessed, modified, or deleted.\n- Data classifications (e.g., classification levels/security levels) are accessed, modified, or deleted.\n- Any other specified objects are accessed, modified, or deleted as required by the site.\n\nIf SQL Server is not required to audit any of the above, this is not a finding. \n \nIf the documentation does not exist, this is a finding. \n \nDetermine if an audit is configured and started by executing the following query. If no records are returned, this is a finding. \n \nSELECT name AS 'Audit Name', \nstatus_desc AS 'Audit Status', \naudit_file_path AS 'Current Audit File' \nFROM sys.dm_server_audit_status \n \nIf auditing the retrieval of the above information or objects is required, execute the following to verify the SCHEMA_OBJECT_ACCESS_GROUP is included in the server audit specification: \n \nSELECT a.name AS 'AuditName', \ns.name AS 'SpecName', \nd.audit_action_name AS 'ActionName', \nd.audited_result AS 'Result' \nFROM sys.server_audit_specifications s \nJOIN sys.server_audits a ON s.audit_guid = a.audit_guid \nJOIN sys.server_audit_specification_details d ON s.server_specification_id = d.server_specification_id \nWHERE a.is_state_enabled = 1 AND d.audit_action_name = 'SCHEMA_OBJECT_ACCESS_GROUP' \n \nIf the SCHEMA_OBJECT_ACCESS_GROUP is not returned in an active audit, this is a finding.","fixText":"Deploy an audit to log when attempts to access privileges, categorized information, security objects, and any other specific objects occur. \n\nRefer to the supplemental file \"SQL 2022 Audit.sql\".","ccis":["CCI-000172"]},{"vulnId":"V-271273","ruleId":"SV-271273r1109234_rule","severity":"medium","ruleTitle":"SQL Server must initiate session auditing upon startup.","description":"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.","checkContent":"When audits are enabled, they start up when the instance starts. Refer to https://msdn.microsoft.com/en-us/library/cc280386.aspx#Anchor_2 \n \nCheck if an audit is configured and enabled by executing the following query: \n \nSELECT name AS 'Audit Name', \nstatus_desc AS 'Audit Status', \naudit_file_path AS 'Current Audit File' \nFROM sys.dm_server_audit_status \nWHERE status_desc = 'STARTED' \n \nAll currently defined audits for the SQL server instance will be listed. If no audits are returned, this is a finding.","fixText":"Configure the SQL audit(s) to automatically start during system startup. \n \nALTER SERVER AUDIT [] WITH STATE = ON \n \nExecute the following: \n \nSELECT name AS 'Audit Name', \n status_desc AS 'Audit Status', \n audit_file_path AS 'Current Audit File' \nFROM sys.dm_server_audit_status \nWHERE status_desc = 'STARTED' \n \nEnsure the SQL STIG Audit is configured to initiate session auditing upon startup.","ccis":["CCI-001464"]},{"vulnId":"V-271280","ruleId":"SV-271280r1108456_rule","severity":"medium","ruleTitle":"SQL Server must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject.","description":"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. \n \nThe 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. \n \nExamples of detailed information the organization may require in audit records are full-text recording of privileged commands or the individual identities of shared account users.","checkContent":"If a SQL Server Audit is not in use for audit purposes, this is a finding unless a third-party product is being used that can perform detailed auditing for SQL Server. \n \nReview system documentation to determine whether SQL Server is required to audit any events, and any fields, in addition to those in the standard audit. \n \nIf there are none specified, this is not a finding. \n \nIf SQL Server Audit is in use, compare the audit specification(s) with the documented requirements. \n \nIf any such requirement is not satisfied by the audit specification(s) (or by supplemental, locally deployed mechanisms), this is a finding.","fixText":"Design and deploy an audit that captures all auditable events and data items. In the event a third-party tool is used for auditing, it must contain all the required information, including but not limited to, events, type, location, subject, date and time, and by whom the change occurred. \n \nImplement additional custom audits to capture the additional organizational required information.","ccis":["CCI-000135"]},{"vulnId":"V-271282","ruleId":"SV-271282r1109273_rule","severity":"medium","ruleTitle":"The audit information produced by SQL Server must be protected from unauthorized access, modification, and deletion.","description":"If audit data were to become compromised, competent forensic analysis and discovery of the true source of potentially malicious system activity would be difficult, if not impossible, to achieve. In addition, access to audit records provides information an attacker could potentially use to their advantage. \n\nTo 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. \n\nThis requirement can be achieved through multiple methods, which will depend on system architecture and design. Some commonly employed methods include ensuring log files enjoy the proper file system permissions using file system protections and limiting log data location. \n\nAdditionally, applications with user interfaces to audit records should not allow for the unfettered manipulation of or access to those records via the application. If the application provides access to the audit data, the application becomes accountable for ensuring that audit information is protected from unauthorized access. SQL Server is able to view and manipulate audit file data. \n\nAudit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity.\n\nSatisfies: SRG-APP-000118-DB-000059, SRG-APP-000119-DB-000060, SRG-APP-000120-DB-000061","checkContent":"If the database is set up to write audit logs using APPLICATION or SECURITY event logs rather than writing to a file, this is Not Applicable.\n\nObtain the SQL Server Audit file location(s) by running the following SQL script: \n\nSELECT log_file_path AS \"Audit Path\" \nFROM sys.server_file_audits \n\nFor each audit, the path column will give the location of the file. \n\nVerify that all audit files have the correct permissions by doing the following for each audit file: Navigate to audit folder location(s) using a command prompt or Windows Explorer. \n\nRight-click the file/folder and click \"Properties\". On the \"Security\" tab, verify the following permissions are applied: \n\nAdministrator (read) \nUsers (none) \nAudit Administrator (Full Control) \nAuditors group (Read) \nSQL Server Service SID OR Service Account (Full Control) \nSQL Server SQL Agent Service SID OR Service Account, if SQL Server Agent is in use. (Read, Execute, Write) \n\nIf any less restrictive permissions are present (and not specifically justified and approved), this is a finding.","fixText":"Modify audit file permissions to meet the requirement to protect against unauthorized access. \n\nApplication event log and security log permissions are covered in the Windows Server STIGs. Reference these depending on the OS in use.\n\nNavigate to audit folder location(s) using a command prompt or Windows Explorer. Right-click the file and click \"Properties\". \n\nOn the Security tab, modify the security permissions to: \n\nAdministrator (read) \nUsers (none) \nAudit Administrator(Full Control) \nAuditors group (Read) \nSQL Server Service SID OR Service Account (Full Control) [Notes 1, 2] \nSQL Server SQL Agent Service SID OR Service Account, if SQL Server Agent is in use. (Read, Execute, Write) [Notes 1, 2] \n\n----- \nNote 1: It is highly advisable to use a separate account for each service. When installing SQL Server in single-server mode, users can opt to have these provisioned for them. These automatically generated accounts are referred to as virtual accounts. Each virtual account has an equivalent Service SID with the same name. The installer also creates an equivalent SQL Server login, also with the same name. Applying folder and file permissions to Service SIDs rather than to domain accounts or local computer accounts provides tighter control, because these permissions are available only to the specific service when it is running and not in any other context. However, when using failover clustering, a domain account must be specified at installation, rather than a virtual account. For more on this topic, refer to http://msdn.microsoft.com/en-us/library/ms143504(v=sql.130).aspx. \n\nNote 2: Tips for adding a service SID/virtual account to a folder's permission list:\n\n1. In Windows Explorer, right-click the folder and select \"Properties\". \n2. Select the \"Security\" tab. \n3. Click \"Edit\". \n4. Click \"Add\". \n5. Click \"Locations\". \n6. Select the computer name. \n7. Search for the name. \n 7.a. SQL Server Service \n 7.a.i. Type \"NT SERVICE\\MSSQL\" and click \"Check Names\". (This is the first 16 characters of the name. At least one character must follow \"NT SERVICE\\\"; this will present with a list of all matches. If the full, correct name was typed, step 7.a.ii is bypassed.) \n 7.a.ii. Select the \"MSSQL$\" user and click \"OK\".\n 7.b. SQL Agent Service \n 7.b.i. Type \"NT SERVICE\\SQL\" and click \"Check Names\". \n 7.b.ii. Select the \"SQLAgent$\" user and click \"OK\". \n8. Click \"OK\". \n9. Permission like a normal user from here.","ccis":["CCI-000162","CCI-000163","CCI-000164"]},{"vulnId":"V-271283","ruleId":"SV-271283r1108465_rule","severity":"medium","ruleTitle":"SQL Server must protect its audit configuration from authorized and unauthorized access and modification.","description":"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. \n \nApplications 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. \n \nAudit tools include, but are not limited to, vendor-provided and open-source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.\n\nIf an attacker were to gain access to audit tools, they could analyze audit logs for system weaknesses or weaknesses in the auditing itself. An attacker could also manipulate logs to hide evidence of malicious activity.\n\nSatisfies: SRG-APP-000121-DB-000202, SRG-APP-000122-DB-000203, SRG-APP-000123-DB-000204","checkContent":"Check the server documentation for a list of approved users with access to SQL Server Audits.\n \nTo create, alter, or drop a server audit, principals require the ALTER ANY SERVER AUDIT or the CONTROL SERVER permission.\n \nReview the SQL Server permissions granted to principals. Look for permissions ALTER ANY SERVER AUDIT, ALTER ANY DATABASE AUDIT, CONTROL SERVER: \n \nSELECT login.name, perm.permission_name, perm.state_desc \nFROM sys.server_permissions perm \nJOIN sys.server_principals login \nON perm.grantee_principal_id = login.principal_id \nWHERE permission_name in ('ALTER ANY DATABASE AUDIT', 'ALTER ANY SERVER AUDIT', 'CONTROL SERVER') \nand login.name not like '##MS_%'; \n \nIf unauthorized accounts have these privileges, this is a finding.","fixText":"Remove audit-related permissions from individuals and roles not authorized to have them. \n \nUSE master; \nDENY [ALTER ANY SERVER AUDIT] TO [User]; \nGO","ccis":["CCI-001493","CCI-001494","CCI-001495"]},{"vulnId":"V-271284","ruleId":"SV-271284r1109111_rule","severity":"medium","ruleTitle":"SQL Server must limit privileges to change software modules, to include stored procedures, functions and triggers, and links to software external to SQL Server.","description":"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. \n \nAccordingly, only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications. \n \nUnmanaged changes that occur to the database software libraries or configuration can lead to unauthorized or compromised installations.","checkContent":"Review server documentation to determine the process by which shared software libraries are monitored for change. Ensure the process alerts for changes in a file's ownership, modification dates, and hash value at a minimum.\n\nIf alerts do not at least hash their value, this is a finding.\n\nTo determine the location for these instance-specific binaries:\n\n1. Launch SQL Server Management Studio (SSMS).\n2. Connect to the instance to be reviewed.\n3. Right-click server name in Object Explorer.\n4. Click \"Facets\".\n5. Select the \"Server\" facet.\n6. Record the value for the \"RootDirectory\" facet property.\n\nTip: Use the Get-FileHash cmdlet shipped with PowerShell 5.0 to get the SHA-2 hash of one or more files.","fixText":"Implement and document a process by which changes made to software libraries are monitored and alerted. A PowerShell based hashing solution is one such process. The Get-FileHash command can be used to compute the SHA-2 hash of one or more files. For more information, refer to the following link:\nhttps://msdn.microsoft.com/en-us/powershell/reference/5.1/microsoft.powershell.utility/get-filehash\n\nUsing the Export-Clixml command, a baseline can be established and exported to a file:\nhttps://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/export-clixml?view=powershell-7.5\n\nUsing the Compare-Object command, a comparison of the latest baseline versus the original baseline can expose the differences:\nhttps://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-powershell-1.0/ee156812(v=technet.10)?redirectedfrom=MSDN","ccis":["CCI-001499"]},{"vulnId":"V-271285","ruleId":"SV-271285r1109236_rule","severity":"medium","ruleTitle":"SQL Server must limit privileges to change software modules and links to software external to SQL Server.","description":"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. \n \nAccordingly, only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications. \n \nUnmanaged changes that occur to the database software libraries or configuration can lead to unauthorized or compromised installations.","checkContent":"Review Server documentation to determine the authorized owner and users or groups with modify rights for this SQL instance's binary files. Additionally check the owner and users or groups with modify rights for shared software library paths on disk. \n \nIf any unauthorized users are granted modify rights or the owner is incorrect, this is a finding. \n\nTo determine the location for these instance-specific binaries:\n\n1. Launch SQL Server Management Studio (SSMS). \n2. Connect to the instance to be reviewed. \n3. Right-click server name in \"Object Explorer\".\n4. Click \"Facets\".\n5. Select the \"Server\" facet. \n6. Record the value for the \"RootDirectory\" facet property. \n7. Navigate to the folder above and review the \"Binn\" subdirectory.\n\nTIP: Use the Get-FileHash cmdlet shipped with PowerShell 5.0 to get the SHA-2 hash of one or more files.","fixText":"Change the ownership of all shared software libraries on disk to the authorized account. Remove any modify permissions granted to unauthorized users or groups.","ccis":["CCI-001499"]},{"vulnId":"V-271286","ruleId":"SV-271286r1108474_rule","severity":"high","ruleTitle":"SQL Server software installation account must be restricted to authorized users.","description":"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. \n\nIf 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. \n\nDBA and other privileged administrative or application owner accounts are granted privileges that allow actions that can have a great impact on SQL Server security and operation. It is especially important to grant privileged access to only those persons who are qualified and authorized to use them.","checkContent":"From the system documentation, obtain the list of accounts authorized to install/update SQL Server. Run the following PowerShell command to list all users who have installed/modified SQL Server 2022 software and compare the list against those persons who are qualified and authorized to use the software. \n \nsl \"C:\\Program files\\Microsoft SQL Server\\160\\Setup Bootstrap\\Log\" \nGet-ChildItem -Recurse | Select-String -Pattern \"LogonUser = \" \n \nIf any accounts are shown that are not authorized in the system documentation, this is a finding.","fixText":"From a command prompt, open lusrmgr.msc. Navigate to \"Users\" and right-click \"Individual User\". Select \"Properties\", then \"Member Of\". \n \nConfigure SQL Server and OS settings and access controls to restrict user access to objects and data that the user is authorized to view/use.","ccis":["CCI-001499"]},{"vulnId":"V-271287","ruleId":"SV-271287r1108843_rule","severity":"medium","ruleTitle":"Database software, including DBMS configuration files, must be stored in dedicated directories, separate from the host OS and other applications.","description":"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. \n \nMultiple 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.","checkContent":"Determine the directory in which SQL Server has been installed:\n\nUsing SQL Server Management Studio's Object Explorer, right-click [SQL Server Instance], select \"Facets\", then record the value of RootDirectory.\n\nDetermine the Operating System directory:\n1. Click \"Start\".\n2. Type \"Run\".\n3. Press \"Enter\".\n4. Type \"%windir%\".\n5. Click \"Ok\".\n6. Record the value in the address bar.\n\nVerify the SQL Server RootDirectory is not in the Operating System directory.\n\nCompare the SQL RootDirectory and the Operating System directory. If the SQL RootDirectory is in the same directory as the Operating System, this is a finding.\n\nVerify the SQL Server RootDirectory is not in another application's directory.\n\nNavigate to the SQL RootDirectory using Windows Explorer.\n\nExamine each directory for evidence another application is stored in it.\n\nIf evidence exists the SQL RootDirectory is in another application's directory, this is a finding.\n\nIf the SQL RootDirectory is not in the Operating System directory or another application's directory, this is not a finding.\n\nExamples:\n1. The Operating System directory is \"C:\\Windows\". The SQL RootDirectory is \"D:\\Program Files\\MSSQLSERVER\\MSSQL\". The MSSQLSERVER directory is not living in the Operating System directory or the directory of another application. This is not a finding.\n\n2. The Operating System directory is \"C:\\Windows\". The SQL RootDirectory is \"C:\\Windows\\MSSQLSERVER\\MSSQL\". This is a finding.\n\n3. 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.","fixText":"Reinstall SQL Server application components using dedicated directories that are separate from the operating system. \n \nRelocate or reinstall other application software that currently shares directories with SQL Server components separate from the operating system and/or temporary storage.","ccis":["CCI-001499"]},{"vulnId":"V-271290","ruleId":"SV-271290r1109112_rule","severity":"medium","ruleTitle":"Default demonstration and sample databases, database objects, and applications must be removed.","description":"Information systems are capable of providing a wide variety of functions and services. Some of the default functions and services may not be necessary to support essential organizational operations (e.g., key missions, functions). \n \nIt 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. \n \nDBMSs must adhere to the principles of least functionality by providing only essential capabilities. \n \nDemonstration and sample database objects and applications present publicly known attack points for malicious users. These demonstration and sample objects are meant to provide simple examples of coding specific functions and are not developed to prevent vulnerabilities from being introduced to SQL Server and host system.","checkContent":"Review vendor documentation and vendor websites to identify vendor-provided demonstration or sample databases, database applications, objects, and files. Review the SQL Server to determine if any of the demonstration and sample databases, database applications, or files are installed in the database or included with the SQL Server Instance. \n\nRun the following query to check for names matching known sample databases. Sample databases may have been renamed, so this is not an exhaustive list.\n\nSELECT name\nFROM sys.databases\nWHERE name LIKE '%pubs%'\nOR name LIKE '%northwind%'\nOR name LIKE '%adventureworks%'\nOR name LIKE '%wideworldimporters%'\nOR name LIKE '%contoso%'\n\nIf any sample databases are found, this is a finding.","fixText":"Remove all demonstration or sample databases from production instances.","ccis":["CCI-000381"]},{"vulnId":"V-271291","ruleId":"SV-271291r1108899_rule","severity":"medium","ruleTitle":"Unused database components, DBMS software, and database objects must be removed.","description":"Information systems are capable of providing a wide variety of functions and services. Some of the default functions and services may not be necessary to support essential organizational operations (e.g., key missions, functions). \n \nIt is detrimental for software products to provide, or install by default, functionality exceeding requirements or mission objectives. \n \nDBMSs must adhere to the principles of least functionality by providing only essential capabilities.","checkContent":"From the server documentation, obtain a listing of required components. \n \nGenerate a listing of components installed on the server. \n \n1. Click \"Start\".\n2. Type \"SQL Server 2022 Installation Center\".\n3. Launch the program.\n4. Click \"Tools\".\n5. Click \"Installed SQL Server features discovery report\". \n6. Compare the feature listing against the required components listing. \n \nIf any features are installed, but are not required, this is a finding.","fixText":"Remove all features that are not required.","ccis":["CCI-000381"]},{"vulnId":"V-271292","ruleId":"SV-271292r1111143_rule","severity":"medium","ruleTitle":"The SQL Server Replication Xps feature must be disabled unless specifically required and approved.","description":"SQL Server is capable of providing a wide range of features and services. Some of the default features and services may not be necessary and enabling them could adversely affect the security of the system.\n\nEnabling 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.","checkContent":"To determine if [Replication Xps] is enabled, execute the following command:\nSELECT name, value, value_in_use\nFROM sys.configurations\nWHERE name = 'Replication Xps'\n \nIf [value_in_use] is a [1], review the system documentation to determine whether the use of [Replication Xps] is approved. If it is not approved, this is a finding.","fixText":"Disable use of or remove any external application executable object definitions that are not approved.\n\nTo disable the use of [Replication Xps] option, from the query prompt:\nEXEC SP_CONFIGURE 'show advanced options', 1; \nRECONFIGURE WITH OVERRIDE;\nEXEC SP_CONFIGURE 'replication xps', 0;\nRECONFIGURE WITH OVERRIDE;\nEXEC SP_CONFIGURE 'show advanced options', 0; \nRECONFIGURE WITH OVERRIDE;\nGO \nRECONFIGURE; \nGO","ccis":["CCI-000381"]},{"vulnId":"V-271293","ruleId":"SV-271293r1111138_rule","severity":"medium","ruleTitle":"The SQL Server External Scripts Enabled feature must be disabled, unless specifically required and approved.","description":"SQL Server is capable of providing a wide range of features and services. Some of the default features and services may not be necessary and enabling them could adversely affect the security of the system.\n\nThe External Scripts Enabled feature allows scripts external to SQL such as files located in an R library to be executed.","checkContent":"To determine if [External Scripts Enabled] is enabled, execute the following command:\nSELECT name, value, value_in_use\nFROM sys.configurations\nWHERE name = 'External Scripts Enabled'\n \nIf [value_in_use] is a [1], review the system documentation to determine whether the use of [External Scripts Enabled] is approved. If it is not approved, this is a finding.","fixText":"Disable use of or remove any external application executable object definitions that are not approved.\n\nTo disable the use of [External Scripts Enabled] option, from the query prompt:\nEXEC SP_CONFIGURE 'External Scripts Enabled', 0;\nRECONFIGURE WITH OVERRIDE;","ccis":["CCI-000381"]},{"vulnId":"V-271295","ruleId":"SV-271295r1111135_rule","severity":"medium","ruleTitle":"The remote Data Archive feature must be disabled unless specifically required and approved.","description":"Information systems are capable of providing a wide variety of functions and services. Some of the default functions and services may not be necessary to support essential organizational operations (e.g., key missions, functions). \n\nIt is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. \n\nApplications must adhere to the principles of least functionality by providing only essential capabilities.\n\nSQL 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.\n\nSQL 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.\n\nThe Remote Data Archive feature allows an export of local SQL Server data to an Azure SQL Database. An exploit to the SQL Server instance could result in a compromise of the host system and external SQL Server resources.","checkContent":"To determine if [Remote Data Archive] is enabled, execute the following command:\nSELECT name, value, value_in_use\nFROM sys.configurations\nWHERE name = 'Remote Data Archive'\n \nIf [value_in_use] is a [1], review the system documentation to determine whether the use of [Remote Data Archive] is approved. If it is not approved, this is a finding.","fixText":"Disable use of or remove any external application executable object definitions that are not approved.\n\nTo disable the use of [Remote Data Archive] option, from the query prompt: \nEXEC SP_CONFIGURE 'Remote Data Archive', 0;\nRECONFIGURE WITH OVERRIDE;","ccis":["CCI-000381"]},{"vulnId":"V-271296","ruleId":"SV-271296r1111132_rule","severity":"medium","ruleTitle":"The \"Allow Polybase Export\" feature must be disabled, unless specifically required and approved.","description":"Information systems are capable of providing a wide variety of functions and services. Some of the default functions and services may not be necessary to support essential organizational operations (e.g., key missions, functions). \n\nIt is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. \n\nApplications must adhere to the principles of least functionality by providing only essential capabilities.\n\nSQL 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.\n\nThe Allow Polybase Export feature allows an export of data to an external data source such as Hadoop File System or Azure Data Lake. An exploit to the SQL Server instance could result in a compromise of the host system and external SQL Server resources.","checkContent":"To determine if [Allow Polybase Export] is enabled, execute the following command:\nSELECT name, value, value_in_use\nFROM sys.configurations\nWHERE name = 'Allow Polybase Export'\n \nIf [value_in_use] is a [1], review the system documentation to determine whether the use of [Allow Polybase Export] is approved. If it is not approved, this is a finding.","fixText":"Disable use of or remove any external application executable object definitions that are not approved.\n\nTo disable the use of [Allow Polybase Export] option, from the query prompt: \nEXEC SP_CONFIGURE 'Allow Polybase Export', 0;\nRECONFIGURE WITH OVERRIDE;","ccis":["CCI-000381"]},{"vulnId":"V-271297","ruleId":"SV-271297r1111129_rule","severity":"medium","ruleTitle":"The \"Hadoop Connectivity\" feature must be disabled unless specifically required and approved.","description":"Information systems are capable of providing a wide variety of functions and services. Some of the default functions and services may not be necessary to support essential organizational operations (e.g., key missions, functions). \n\nIt is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. \n\nApplications must adhere to the principles of least functionality by providing only essential capabilities.\n\nSQL 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.\n\nSQL 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.\n\nThe \"Hadoop Connectivity\" feature allows multiple types of external data sources to be created and used across all sessions on the server. An exploit to the SQL Server instance could result in a compromise of the host system and external SQL Server resources.","checkContent":"To determine if [Hadoop Connectivity] is enabled, execute the following command:\nSELECT name, value, value_in_use\nFROM sys.configurations\nWHERE name = 'Hadoop Connectivity'\n \nIf [value_in_use] is a [1], review the system documentation to determine whether the use of [Hadoop Connectivity] is approved. If it is not approved, this is a finding.","fixText":"Disable use of or remove any external application executable object definitions that are not approved.\n\nTo disable the use of [Hadoop Connectivity] option, from the query prompt:\nEXEC SP_CONFIGURE 'hadoop connectivity', 0; \nRECONFIGURE WITH OVERRIDE;","ccis":["CCI-000381"]},{"vulnId":"V-271298","ruleId":"SV-271298r1111126_rule","severity":"medium","ruleTitle":"The \"Remote Access\" feature must be disabled unless specifically required and approved.","description":"Information systems are capable of providing a wide variety of functions and services. Some of the default functions and services may not be necessary to support essential organizational operations (e.g., key missions, functions). \n\nIt is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. \n\nApplications must adhere to the principles of least functionality by providing only essential capabilities.\n\nSQL 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.\n\nThe \"Remote Access\" option controls the execution of local stored procedures on remote servers or remote stored procedures on local server. Remote access functionality can be abused to launch a denial-of-service (DoS) attack on remote servers by off-loading query processing to a target.","checkContent":"To determine if [Remote Access] is enabled, execute the following command:\nSELECT name, value, value_in_use\nFROM sys.configurations\nWHERE name = 'Remote Access'\n \nIf [value_in_use] is a [1], review the system documentation to determine whether the use of [Remote Access] is approved. If it is not approved, this is a finding.","fixText":"Disable use of [Remote Access] if it is not authorized.\n \nTo disable the use of [Remote Access], from the query prompt: \nEXEC SP_CONFIGURE 'remote access', 0;\nRECONFIGURE WITH OVERRIDE;","ccis":["CCI-000381"]},{"vulnId":"V-271299","ruleId":"SV-271299r1108513_rule","severity":"medium","ruleTitle":"Access to linked servers must be disabled or restricted, unless specifically required and approved.","description":"Information systems are capable of providing a wide variety of functions and services. Some of the default functions and services may not be necessary to support essential organizational operations (e.g., key missions, functions). \n\nIt is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. \n\nApplications must adhere to the principles of least functionality by providing only essential capabilities. \n\nSQL 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. \n\nA 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.","checkContent":"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.\n \nTo obtain a list of linked servers, execute the following command:\n \nSELECT name\nFROM sys.servers s \nWHERE s.is_linked = 1 \n \nReview the system documentation to determine whether the linked servers listed are required and approved. If it is not approved, this is a finding. \n \nRun the following to get a linked server login mapping: \n \nSELECT s.name, p.principal_id, l.remote_name \nFROM sys.servers s \nJOIN sys.linked_logins l ON s.server_id = l.server_id \nLEFT JOIN sys.server_principals p ON l.local_principal_id = p.principal_id \nWHERE s.is_linked = 1 \n \nReview 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.","fixText":"Remove any linked servers and all associated logins that are not authorized. \n \nTo remove a linked server and all associated logins run the following: \n \nsp_dropserver 'LinkedServerName', 'droplogins'; \n \nTo remove a login from a linked server run the following: \n \nEXEC sp_droplinkedsrvlogin 'LoginName', NULL;","ccis":["CCI-000381"]},{"vulnId":"V-271300","ruleId":"SV-271300r1109264_rule","severity":"medium","ruleTitle":"Access to nonstandard, extended stored procedures must be disabled or restricted, unless specifically required and approved.","description":"Information systems are capable of providing a wide variety of functions and services. Some of the default functions and services may not be necessary to support essential organizational operations (e.g., key missions, functions). \n \nIt is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. \n \nApplications must adhere to the principles of least functionality by providing only essential capabilities. \n \nSQL 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. \n \nExtended stored procedures are DLLs that an instance of SQL Server can dynamically load and run. Extended stored procedures run directly in the address space of an instance of SQL Server and are programmed by using the SQL Server Extended Stored Procedure API. Nonstandard extended stored procedures can compromise the integrity of the SQL Server process. This feature will be removed in a future version of Microsoft SQL Server. Do not use this feature in new development work and modify applications that currently use this feature as soon as possible.","checkContent":"Extended stored procedures are DLLs that an instance of SQL Server can dynamically load and run. Extended stored procedures run directly in the address space of an instance of SQL Server and are programmed by using the SQL Server Extended Stored Procedure API. \n \nNonstandard extended stored procedures can compromise the integrity of the SQL Server process. This feature will be removed in a future version of SQL Server. Do not use this feature in new development work and modify applications that currently use this feature as soon as possible. \n \nTo determine if nonstandard extended stored procedures exist, run the following:\n\nUSE [master]\nGO\nDECLARE @xplist AS TABLE\n(\n xp_name sysname,\n source_dll nvarchar(255)\n)\nINSERT INTO @xplist\nEXEC sp_helpextendedproc\n\nSELECT X.xp_name, X.source_dll, O.is_ms_shipped FROM @xplist X JOIN sys.all_objects O ON X.xp_name = O.name WHERE O.is_ms_shipped = 0 ORDER BY X.xp_name\n \nIf any records are returned, review the system documentation to determine whether the use of nonstandard extended stored procedures are required and approved.\n\nIf it is not approved, this is a finding.","fixText":"Remove any nonstandard extended stored procedures that are not documented and approved using the following:\n \nsp_dropextendedproc 'proc name'","ccis":["CCI-000381"]},{"vulnId":"V-271301","ruleId":"SV-271301r1109114_rule","severity":"medium","ruleTitle":"Access to common language runtime (CLR) code must be disabled or restricted unless specifically required and approved.","description":"Information systems are capable of providing a wide variety of functions and services. Some of the default functions and services may not be necessary to support essential organizational operations (e.g., key missions, functions). \n \nIt is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. \n \nApplications must adhere to the principles of least functionality by providing only essential capabilities. \n \nSQL 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. \n \nThe CLR component of the .NET Framework for Microsoft Windows in SQL Server allows users to write stored procedures, triggers, user-defined types, user-defined functions, user-defined aggregates, and streaming table-valued functions, using any .NET Framework language, including Microsoft Visual Basic .NET and Microsoft Visual C#. CLR packing assemblies can access resources protected by .NET Code Access Security when it runs managed code. Specifying UNSAFE enables the code in the assembly complete freedom to perform operations in the SQL Server process space that can potentially compromise the robustness of SQL Server. UNSAFE assemblies can also potentially subvert the security system of either SQL Server or the common language runtime.","checkContent":"To determine if [CLR] is enabled, execute the following command: \n\nSELECT name, value, value_in_use\nFROM sys.configurations\nWHERE name = 'clr enabled'\n \nIf [value_in_use] is a [1], review the system documentation to determine whether the use of [CLR] is approved. If it is not approved, this is a finding.","fixText":"Disable use of or remove any CLR code that is not authorized.\n\nTo disable the use of CLR, from the query prompt: \n \nEXEC SP_CONFIGURE 'clr enabled', 0;\nRECONFIGURE WITH OVERRIDE;\n\nFor any approved CLR code with Unsafe or External permissions, use the ALTER ASSEMBLY to change the permission set for the assembly and ensure a certificate is configured.","ccis":["CCI-000381"]},{"vulnId":"V-271302","ruleId":"SV-271302r1109113_rule","severity":"medium","ruleTitle":"Access to xp_cmdshell must be disabled unless specifically required and approved.","description":"Information systems are capable of providing a wide variety of functions and services. Some of the default functions and services may not be necessary to support essential organizational operations (e.g., key missions, functions). \n \nIt is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. \n \nApplications must adhere to the principles of least functionality by providing only essential capabilities. \n \nSQL 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. \n \nThe xp_cmdshell extended stored procedure allows execution of host executables outside the controls of database access permissions. This access may be exploited by malicious users who have compromised the integrity of the SQL Server database process to control the host operating system to perpetrate additional malicious activity.","checkContent":"To determine if [xp_cmdshell] is enabled, execute the following command: \n\nSELECT name, value, value_in_use\nFROM sys.configurations\nWHERE name = 'xp_cmdshell'\n \nIf [value_in_use] is a [1], review the system documentation to determine whether the use of [xp_cmdshell] is approved. If it is not approved, this is a finding.","fixText":"Disable use of or remove any external application executable object definitions that are not approved.\n\nTo disable the use of xp_cmdshell, from the query prompt: \n\nEXEC SP_CONFIGURE 'show advanced options', 1; \nRECONFIGURE WITH OVERRIDE;\nEXEC SP_CONFIGURE 'xp_cmdshell', 0;\nRECONFIGURE WITH OVERRIDE;\nEXEC SP_CONFIGURE 'show advanced options', 0; \nRECONFIGURE WITH OVERRIDE;","ccis":["CCI-000381"]},{"vulnId":"V-271303","ruleId":"SV-271303r1109116_rule","severity":"medium","ruleTitle":"SQL Server must be configured to prohibit or restrict the use of organization-defined ports, as defined in the Ports, Protocols, and Services Management (PPSM) Category Assurance List (CAL) and vulnerability assessments.","description":"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. \n \nApplications 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. \n \nTo support the requirements and principles of least functionality, the application must support the organizational requirements providing only essential capabilities and limiting the use of ports to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues. \n \nSQL Server using ports deemed unsafe is open to attack through those ports. This can allow unauthorized access to the database and through the database to other components of the information system.","checkContent":"Review SQL Server Configuration for the ports used by SQL Server. \n \nTo determine whether SQL Server is configured to use a fixed port or dynamic ports, in the right-side pane, double-click on the TCP/IP entry to open the Properties dialog. (The default fixed port is 1433.) \n\nAlternatively, run the following SQL query to determine the port used by SQL Server:\n\nSELECT ISNULL(CONVERT(VARCHAR(25),local_tcp_port),'Dynamic Ports are Enabled')\nFROM sys.dm_exec_connections\nWHERE session_id = @@SPID\n \nIf any ports in use are in conflict with PPSM guidance and not explained and approved in the system documentation, this is a finding.","fixText":"Use SQL Server Configuration to change the ports used by SQL Server to comply with PPSM guidance, or document the need for other ports, and obtain written approval. Close ports no longer needed.","ccis":["CCI-000382"]},{"vulnId":"V-271304","ruleId":"SV-271304r1109265_rule","severity":"medium","ruleTitle":"SQL Server must be configured to prohibit or restrict the use of organization-defined protocols as defined in the Ports, Protocols, and Services Management (PPSM) Category Assurance List (CAL) and vulnerability assessments.","description":"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. \n \nApplications 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. \n \nTo support the requirements and principles of least functionality, the application must support the organizational requirements providing only essential capabilities and limiting the use of protocols to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues. \n \nSQL Server using protocols deemed unsafe is open to attack through those protocols. This can allow unauthorized access to the database and through the database to other components of the information system.\n\nSatisfies: SRG-APP-000142-DB-000094, SRG-APP-000383-DB-000364","checkContent":"To determine the protocol(s) enabled for SQL Server, open SQL Server Configuration Manager. In the left pane, expand SQL Server Network Configuration. Click on the entry for the SQL Server instance under review: \"Protocols for\". The right-side pane displays the protocols enabled for the instance. \n\nAlternatively, run the following SQL Script and review the registry_key for enabled protocols.\n\nSELECT \n*\nFROM sys.dm_server_registry\nWHERE registry_key like 'HKLM\\Software\\Microsoft\\Microsoft SQL Server\\%\\MSSQLServer\\SuperSocketNetLib\\%'\n AND value_name = 'enabled'\n AND value_data = 1\n \nIf any listed protocols are enabled but not documented and authorized, this is a finding.","fixText":"Navigate to SQL Server Configuration Manager >> SQL Server Network Configuration >> Protocols, then right-click on each listed protocol that is enabled but not authorized and select \"Disable\".","ccis":["CCI-000382"]},{"vulnId":"V-271305","ruleId":"SV-271305r1109239_rule","severity":"medium","ruleTitle":"SQL Server must uniquely identify and authenticate users (or processes acting on behalf of organizational users).","description":"To ensure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system. \n \nOrganizational 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: \n \n(i) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and \n(ii) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals using shared accounts for detailed accountability of individual activity.\n\nSatisfies: SRG-APP-000148-DB-000103, SRG-APP-000180-DB-000115","checkContent":"Obtain the list of authorized SQL Server accounts in the system documentation. \n\nDetermine if any accounts are shared. A shared account is defined as a username and password that are used by multiple individuals to log in to SQL Server. Active Directory groups are not shared accounts as the group itself does not have a password. \n\nRun the following query to return all server-level principals:\n\nSELECT name\nFROM sys.server_principals\nWHERE type in ('U','S','E')\nAND name NOT LIKE '%$'\n\nIf any of the returned accounts are shared, determine if individuals are first individually authenticated. \n\nIf 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. \n\nThe key is individual accountability. If this can be traced, this is not a finding. \n\nIf accounts are shared, determine if they are directly accessible to end users. If so, this is a finding. \n\nReview contents of audit logs and data tables to confirm that the identity of the individual user performing the action is captured. \n\nIf shared identifiers are found and not accompanied by individual identifiers, this is a finding.\n\nExecute the following query:\n\nSELECT name\nFROM sys.server_principals\nWHERE type in ('U','S','E')\nAND name LIKE '%$'\n\nIf users are returned, determine whether each user is a computer account.\n\nLaunch PowerShell.\n\nExecute the following code:\n\nNote: represents the username portion of the user. For example, if the user is \"CONTOSO\\user1$\", the username is \"user1\".\n\n([ADSISearcher]\"(&(ObjectCategory=Computer)(Name=))\").FindAll()\n\nIf no account information is returned, this is not a finding.\n\nIf account information is returned, this is a finding.","fixText":"Remove all shared accounts and computer accounts.\n\nTo remove users, run the following command for each user:\n\nDROP USER [ IF EXISTS ] ;","ccis":["CCI-000764","CCI-000804"]},{"vulnId":"V-271306","ruleId":"SV-271306r1109119_rule","severity":"high","ruleTitle":"Contained databases must use Windows principals.","description":"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.\n \nThe 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.\n \nIn 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.","checkContent":"Execute the following query to determine if Contained Databases are used: \n\nSELECT * FROM sys.databases WHERE containment = 1\n\nIf any records are returned, check the server documentation for a list of authorized contained database users. \n\nExecute the following query to ensure contained database users are not using SQL Authentication:\n\nEXEC sp_MSforeachdb 'USE [?]; SELECT DB_NAME() AS DatabaseName, *\nFROM sys.database_principals dp\ninner join sys.databases d on d.name = dp.name\nWHERE dp.authentication_type = 2\nand d.containment = 1'\n\nIf any records are returned, this is a finding.","fixText":"Configure SQL Server contained databases to have users originating from Microsoft Entra (Azure Active Directory) principals. Remove any users not created from Microsoft Entra principals. \n\nReference Contained Databases: https://learn.microsoft.com/en-us/sql/relational-databases/databases/contained-databases?","ccis":["CCI-004066"]},{"vulnId":"V-271307","ruleId":"SV-271307r1109241_rule","severity":"high","ruleTitle":"If DBMS authentication using passwords is employed, SQL Server must enforce the DOD standards for password complexity and lifetime.","description":"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 regarding 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.\n\nBy 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.\n\nOS/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. \n \nThe 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. \n \nIn 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.\n\nSatisfies: SRG-APP-000164-DB-000401, SRG-APP-000700-DB-000100","checkContent":"Check for use of SQL Authentication:\n\nSELECT CASE SERVERPROPERTY('IsIntegratedSecurityOnly')\nWHEN 1 THEN 'Windows Authentication' WHEN 0 THEN 'SQL Authentication' \nEND as [Authentication Mode]\n\nIf the returned value in the \"Authentication Mode\" column is \"Windows Authentication\", this is not a finding. \n\nSQL Server should be configured to inherit password complexity and password lifetime rules from the operating system. Review the SQL Server Instance to ensure logons are created with respect to the complexity settings and password lifetime rules by running the following statement:\n\nSELECT\n[name],\nis_expiration_checked,\nis_policy_checked,*\nFROM\nsys.sql_logins\nWHERE\nis_disabled = 0\nAND name NOT IN ('##MS_PolicyTsqlExecutionLogin##','##MS_PolicyEventProcessingLogin##')\nAND sid <> 1\n \nIf any account does not have both \"is_expiration_checked\" and \"is_policy_checked\" equal to \"1\", this is a finding.","fixText":"Ensure check of policy and expiration are enforced when SQL logins are created. \n\nUse the command below to set CHECK_EXPIRATION and CHECK_POLICY for any login found to be noncompliant:\n\nALTER LOGIN [LoginnameHere] WITH CHECK_EXPIRATION=ON;\nALTER LOGIN [LoginNameHere] WITH CHECK_POLICY=ON;\n\nNew SQL authenticated logins must be created with CHECK_EXPIRATION and CHECK_POLICY set to ON.\n\nCREATE LOGIN [LoginNameHere] WITH PASSWORD = 'ComplexPasswordHere', CHECK_EXPIRATION = ON, CHECK_POLICY = ON;","ccis":["CCI-004066","CCI-003627"]},{"vulnId":"V-271309","ruleId":"SV-271309r1109243_rule","severity":"high","ruleTitle":"If passwords are used for authentication, SQL Server must transmit only encrypted representations of passwords.","description":"The DOD standard for authentication is DOD-approved PKI certificates.\n\nAuthentication based on User ID and Password may be used only when it is not possible to employ a PKI certificate, and requires authorizing official (AO) approval.\n\nIn such cases, passwords need to be protected at all times, and encryption is the standard method for protecting passwords during transmission.\n\nDBMS passwords sent in clear text format across the network are vulnerable to discovery by unauthorized users. Disclosure of passwords may easily lead to unauthorized access to the database.","checkContent":"If SQL Server is using \"Windows Authentication mode\" this requirement can be marked as Not Applicable.\n\nOpen SQL Server Configuration Manager by typing \"SQL Server 2022 Configuration Manager\" in the search bar and pressing \"Enter\".\n\nNavigate to SQL Server Configuration Manager >> SQL Server Network Configuration. Right-click on \"Protocols\", where there is a placeholder for the SQL Server instance name and click on \"Properties\". \n\nOn the \"Flags\" tab, if \"Force Encryption\" is set to \"NO\", this is a finding.\n\nOn the \"Flags\" tab, if \"Force Encryption\" is set to \"YES\", examine the certificate used on the \"Certificate\" tab.\n\nIf it is not a DOD approved certificate, or if no certificate is listed, this is a finding.\n\nFor clustered instances, the Certificate will NOT be shown in the SQL Server Configuration Manager.\n\n1. From a command prompt, navigate to the certificate store where the Full Qualified Domain Name (FQDN) certificate is stored, by typing \"Manage computer certificates\" in the search bar and pressing \"Enter\".\n2. In the left side of the window, expand the \"Personal\" folder, and click \"Certificates\".\n3. Verify the Certificate with the FQDN name is issued by the DOD. Double-click the certificate, click the \"Details\" tab, and note the value for the Thumbprint.\n4. Ensure the value for the \"Thumbprint\" field matches the value in the registry by running regedit and looking at \"HKLM\\SOFTWARE\\Microsoft\\Microsoft SQL Server\\\\MSSQLServer\\SuperSocketNetLib\\Certificate\".\n5. Run this on each node of the cluster.\n\nIf any nodes have a certificate in use by SQL that is not issued or approved by DOD, this is a finding.","fixText":"Configure SQL Server to encrypt authentication data for remote connections using DOD-approved cryptography.\n\nDeploy encryption to the SQL Server Network Connections.\n\nFrom the search bar, open SQL Server Configuration Manager by typing \"SQL Server 2022 Configuration Manager\" and pressing \"ENTER\".\n\nNavigate to SQL Server Configuration Manager >> SQL Server Network Configuration. Right-click on \"Protocols for\", where there is a placeholder for the SQL Server instance name, and click on \"Properties\".\n\nIn the \"Protocols for Properties\" dialog box, on the \"Certificate\" tab, select the DOD certificate from the drop down for the Certificate box, and then click \"OK\". On the \"Flags\" tab, in the \"ForceEncryption\" box, select \"Yes\", and then click \"OK\" to close the dialog box. Then restart the SQL Server service.\n\nFor clustered instances install the certificate after setting \"Force Encryption\" to \"Yes\" in SQL Server Configuration Manager.\n\n1. Navigate to the certificate store where the FQDN certificate is stored, by typing \"Manage computer certificates\" in the search bar and pressing \"ENTER\".\n2. On the \"Properties\" page for the certificate, go to the \"Details\" tab and copy the \"thumbprint\" value of the certificate to a \"Notepad\" window.\n3. Remove the spaces between the hex characters in the \"thumbprint\" value in Notepad.\n4. Start regedit, navigate to the following registry key, and copy the value from step 2: HKLM\\SOFTWARE\\Microsoft\\Microsoft SQL Server\\\\MSSQLServer\\SuperSocketNetLib\\Certificate.\n5. If the SQL virtual server is currently on this node, failover to another node in the cluster, and then reboot the node where the registry change occurred.\n6. Repeat this procedure on all the nodes. Configure SQL Server to encrypt authentication data for remote connections using DOD-approved cryptography.\n\nDeploy encryption to the SQL Server Network Connections.","ccis":["CCI-000197"]},{"vulnId":"V-271310","ruleId":"SV-271310r1111062_rule","severity":"high","ruleTitle":"Confidentiality of information during transmission must be controlled through the use of an approved TLS version.","description":"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.\n\nReferences:\nTLS Support 1.2 for SQL Server: https://support.microsoft.com/en-us/kb/3135244 \nTLS Registry Settings: https://docs.microsoft.com/en-us/windows-server/security/tls/tls-registry-settings","checkContent":"Access the SQL Server.\nAccess an administrator command prompt.\nType \"regedit\" to launch the Registry Editor.\n \nNavigate to:\nHKLM\\SYSTEM\\CurrentControlSet\\Control\\SecurityProviders\\SCHANNEL\\Protocols\\TLS 1.2\n\nIf this key does not exist, this is a finding.\n\nVerify a REG_DWORD value of \"0\" for \"DisabledByDefault\" and a value of \"1\" for \"Enabled\" for both Client and Server.\n \nNavigate to:\nHKLM\\SYSTEM\\CurrentControlSet\\Control\\SecurityProviders\\SCHANNEL\\Protocols\\TLS 1.0\nHKLM\\SYSTEM\\CurrentControlSet\\Control\\SecurityProviders\\SCHANNEL\\Protocols\\TLS 1.1\nHKLM\\SYSTEM\\CurrentControlSet\\Control\\SecurityProviders\\SCHANNEL\\Protocols\\SSL 2.0\nHKLM\\SYSTEM\\CurrentControlSet\\Control\\SecurityProviders\\SCHANNEL\\Protocols\\SSL 3.0\n\nUnder each key, verify a REG_DWORD value of \"1\" for \"DisabledByDefault\" and a value of \"0\" for \"Enabled\" for both Client and Server subkeys.\n \nIf 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 III.","fixText":"Important Note: Incorrectly modifying the Windows Registry can result in serious system errors. Before making any modifications, ensure there is a recent backup of the system and registry settings.\n\nAccess the SQL Server.\nAccess an administrator command prompt. \nType \"regedit\" to launch the Registry Editor.\n \nEnable TLS 1.2:\n \n1. Navigate to the path HKLM\\SYSTEM\\CurrentControlSet\\Control\\SecurityProviders\\SCHANNEL\\Protocols.\n a. If the \"TLS 1.2\" key does not exist, right-click \"Protocols\".\n b. Click \"New\".\n c. Click \"Key\".\n d. Type the name \"TLS 1.2\".\n\n2. Navigate to the \"TLS 1.2\" subkey.\n a. If the subkey \"Client\" does not exist, right-click \"TLS 1.2\".\n b. Click \"New\".\n c. Click \"Key\".\n d. Type the name \"Client\".\n e. Repeat steps A-D for the \"Server\" subkey.\n\n3. Navigate to the \"Client\" subkey.\n a. If the value \"Enabled\" does not exist, right-click on \"Client\".\n b. Click \"New\".\n c. Click \"DWORD\".\n d. Enter \"Enabled\" as the name.\n e. Repeat steps A-D for the value \"DisabledByDefault\".\n\n4. Double-click \"Enabled\".\n\n5. In Value Data, enter \"1\".\n\n6. Click \"OK\".\n\n7. Double-click \"DisabledByDefault\".\n\n8. In Value Data, enter \"0\".\n\n9. Click \"OK\".\n\n10. Repeat steps 3-9 for the \"Server\" subkey.\n \nDisable unwanted SSL/TLS protocol versions:\n\n1. Navigate to the path HKLM\\SYSTEM\\CurrentControlSet\\Control\\SecurityProviders\\SCHANNEL\\Protocols.\n a. If the \"TLS 1.0\" key does not exist, right-click \"Protocols\".\n b. Click \"New\".\n c. Click \"Key\".\n d. Type the name \"TLS 1.0\".\n\n2. Navigate to the \"TLS 1.0\" subkey.\n a. If the subkey \"Client\" does not exist, right-click \"TLS 1.0\".\n b. Click \"New\".\n c. Click \"Key\".\n d. Type the name \"Client\".\n e. Repeat steps A-D for the \"Server\" subkey.\n\n3. Navigate to the \"Client\" subkey.\n a. If the value \"Enabled\" does not exist, right-click on \"Client\".\n b. Click \"New\".\n c. Click \"DWORD\".\n d. Enter \"Enabled\" as the name.\n e. Repeat steps A-D for the value \"DisabledByDefault\".\n\n4. Double-click \"Enabled\".\n\n5. In Value Data, enter \"0\".\n\n6. Click \"OK\".\n\n7. Double-click \"DisabledByDefault\".\n\n8. In Value Data, enter \"1\".\n\n9. Click \"OK\".\n\n10. Repeat steps 3-9 for the \"Server\" subkey.\n\n11. Repeat steps 1-10 for \"TLS 1.1\", \"SSL 2.0\", and \"SSL 3.0\".","ccis":["CCI-000197"]},{"vulnId":"V-271313","ruleId":"SV-271313r1111146_rule","severity":"high","ruleTitle":"When 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.","description":"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.\n\nObfuscation of user-provided information when typed into the system is a method used in addressing this risk.\n\nFor example, displaying asterisks when a user types in a password or PIN is an example of obscuring feedback of authentication information.\n\nThis requirement is applicable when mixed-mode authentication is enabled. When this is the case, password-authenticated accounts can be created in and authenticated by SQL Server. Other STIG requirements prohibit the use of mixed-mode authentication except when justified and approved. This deals with the exceptions.\n\nSQLCMD and other command-line tools are part of any SQL Server installation. These tools can accept a plain text password but do offer alternative techniques. Since the typical user of these tools is a database administrator, the consequences of password compromise are particularly serious. Therefore, the use of plain-text passwords must be prohibited, as a matter of practice and procedure.","checkContent":"Run this query to determine whether SQL Server authentication is enabled:\nEXEC master.sys.xp_loginconfig 'login mode'; \n\nIf the config_value returned is \"Windows NT Authentication\", this is not a finding.\n\nFor 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 authorizing approval (AO) approval has been obtained; if not, this is a finding.\n\nRequest evidence that all users of the tool are trained on the importance of not using the plain-text password option, how to keep the password hidden, and that they adhere to this practice; if not, this is a finding.","fixText":"Where possible, change the login mode to Windows-only:\nUSE [master]\nGO\nEXEC xp_instance_regwrite N'HKEY_LOCAL_MACHINE', N'Software\\Microsoft\\MSSQLServer\\MSSQLServer', N'LoginMode', REG_DWORD, 1;\nGO\n\nIf mixed-mode authentication is necessary, then for SQLCMD, which cannot be configured not to accept a plain-text password when mixed-mode authentication is enabled, and any other essential tool with the same limitation:\n1. Document the need for it, who uses it, and any relevant mitigations, and obtain AO approval.\n2. Train all users of the tool in the importance of not using the plain-text password option and in how to keep the password hidden.","ccis":["CCI-000206"]},{"vulnId":"V-271314","ruleId":"SV-271314r1109121_rule","severity":"high","ruleTitle":"SQL Server must use NIST FIPS 140-2 or 140-3 validated cryptographic operations for encryption, hashing, and signing.","description":"Use of weak or not validated cryptographic algorithms undermines the purposes of using 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. \n \nApplications, including DBMSs, using 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. \n \nNSA Type- (where =1, 2, 3, 4) products are NSA-certified, hardware-based encryption modules.\n\nThe standard for validating cryptographic modules will transition to the NIST FIPS 140-3 publication.\n\nFIPS 140-2 modules can remain active for up to five years after validation or until September 21, 2026, when the FIPS 140-2 validations will be moved to the historical list. Even on the historical list, CMVP supports the purchase and use of these modules for existing systems. While Federal Agencies decide when they move to FIPS 140-3 only modules, purchasers are reminded that for several years there may be a limited selection of FIPS 140-3 modules from which to choose. CMVP recommends purchasers consider all modules that appear on the Validated Modules Search Page:\nhttps://csrc.nist.gov/projects/cryptographic-module-validation-program/validated-modules\n\nMore information on the FIPS 140-3 transition can be found here: \nhttps://csrc.nist.gov/Projects/fips-140-3-transition-effort/.\n\nSatisfies: SRG-APP-000179-DB-000114, SRG-APP-000176-DB-000068, SRG-APP-000224-DB-000384, SRG-APP-000514-DB-000381, SRG-APP-000514-DB-000382, SRG-APP-000514-DB-000383","checkContent":"Verify that Windows is configured to require the use of FIPS compliant algorithms. \n \n1. Click \"Start\".\n2. Type \"Local Security Policy\".\n3. Press \"Enter\".\n4. Expand \"Local Policies\".\n5. Select \"Security Options\".\n6. Review the Security Setting for \"System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing\". \n \nIf the Security Setting for this option is \"Disabled\", this is a finding.\n\nAlternatively, run the following code in PowerShell:\n\nGet-ItemProperty -Path HKLM:\\SYSTEM\\CurrentControlSet\\Control\\Lsa\\FipsAlgorithmPolicy | Select Enabled\n\nIf the returned value is \"0\", this is a finding.","fixText":"Configure Windows to require the use of FIPS compliant algorithms for the unclassified information that requires it. \n \n1. Click \"Start\".\n2. Type \"Local Security Policy\".\n3. Press \"Enter\". \n4. Expand \"Local Policies\". \n5. Select \"Security Options\".\n6. Locate \"System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing\". \n7. Change the Setting option to \"Enabled\". \n8. Restart Windows.","ccis":["CCI-000803","CCI-000186","CCI-001188","CCI-002450"]},{"vulnId":"V-271322","ruleId":"SV-271322r1108582_rule","severity":"high","ruleTitle":"The Master Key must be backed up and stored in a secure location that is not on the SQL Server.","description":"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.","checkContent":"If the application owner and authorizing official have determined that encryption of data at rest is not required, this is not a finding. \n \nReview procedures for and evidence of backup of the Master Key in the System Security Plan. \n \nIf the procedures or evidence does not exist, this is a finding. \n \nIf 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.\n\nIf procedures do not indicate access restrictions to the Master Key backup, this is a finding.","fixText":"Document 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.\n\nBACKUP MASTER KEY TO FILE = 'path_to_file' \nENCRYPTION BY PASSWORD = 'password'; \n \nAs this requires a password, take care to ensure it is not exposed to unauthorized persons or stored as plain text.","ccis":["CCI-001199"]},{"vulnId":"V-271323","ruleId":"SV-271323r1108585_rule","severity":"high","ruleTitle":"The Service Master Key must be backed up and stored in a secure location that is not on the SQL Server.","description":"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.","checkContent":"Review procedures for and evidence of backup of the Server Service Master Key in the System Security Plan. \n \nIf the procedures or evidence does not exist, this is a finding.\n \nIf 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. \n\nIf procedures do not indicate access restrictions to the Service Master Key backup, this is a finding.","fixText":"Document and implement procedures to safely back up and store the Service Master Key in a secure location that is not on the SQL Server. In the procedures, include methods to establish evidence of backup and storage, and careful, restricted access and restoration of the Service Master Key.\n \nBACKUP SERVICE MASTER KEY TO FILE = 'path_to_file' \nENCRYPTION BY PASSWORD = 'password'; \n \nAs this requires a password, take care to ensure it is not exposed to unauthorized persons or stored as plain text.","ccis":["CCI-001199"]},{"vulnId":"V-271324","ruleId":"SV-271324r1192911_rule","severity":"high","ruleTitle":"SQL Server must protect the confidentiality and integrity of all information at rest.","description":"This control is intended to address the confidentiality and integrity of information at rest in nonmobile 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. \n \nUser 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. \n \nIf the confidentiality and integrity of SQL Server data is not protected, the data will be open to compromise and unauthorized modification.","checkContent":"Review system documentation to determine whether the system handles classified information. If the system does not handle classified information, the severity of this check is downgraded to CAT II. \n \nIf the application owner and authorizing official (AO) have determined that encryption of data at rest is required, verify the data on secondary devices is encrypted. \n \nIf full-disk encryption is being used, this is not a finding. \n \nIf data encryption is required, verify the data is encrypted before being put on the secondary device by executing the following:\n \nSELECT\n db.name AS DatabaseName,\n db.is_encrypted AS IsEncrypted,\n CASE\n WHEN dm.encryption_state = 0 THEN 'No database encryption key present, no encryption'\n WHEN dm.encryption_state = 1 THEN 'Unencrypted'\n WHEN dm.encryption_state = 2 THEN 'Encryption in progress'\n WHEN dm.encryption_state = 3 THEN 'Encrypted'\n WHEN dm.encryption_state = 4 THEN 'Key change in progress'\n WHEN dm.encryption_state = 5 THEN 'Decryption in progress'\n WHEN dm.encryption_state = 6 THEN 'Protection change in progress'\n END AS EncryptionState,\n dm.encryption_state AS EncryptionState,\n dm.key_algorithm AS KeyAlgorithm,\n dm.key_length AS KeyLength\nFROM\n sys.databases db\nLEFT JOIN sys.dm_database_encryption_keys dm ON db.database_id = dm.database_id\nWHERE db.database_id > 4\nORDER BY [DatabaseName] ; \n \nFor each user database where encryption is required, verify encryption is in effect. If it is not, this is a finding. \n \nVerify 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.","fixText":"Apply appropriate controls to protect the confidentiality and integrity of data on a secondary device. Where encryption is required, this can be done by full-disk encryption or by database encryption. \n\nTo enable database encryption, create a master key, create a database encryption key, protect it by using mechanisms tied to the master key, and then turn encryption on.\n\nImplement physical security measures, operating system access control lists, and organizational controls appropriate to the sensitivity level of the data in the database(s).","ccis":["CCI-001199"]},{"vulnId":"V-271327","ruleId":"SV-271327r1137657_rule","severity":"medium","ruleTitle":"SQL Server must prevent unauthorized and unintended information transfer via Instant File Initialization (IFI).","description":"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.\n\nWhen 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.\n\nHistorically, transaction log files couldn't be initialized instantaneously. However, starting with SQL Server 2022 (16.x) (all editions), transaction log autogrowth events up to 64 MB can benefit from instant file initialization. The default auto growth size increment for new databases is 64 MB. Transaction log file autogrowth events larger than 64 MB can't benefit from instant file initialization.\n\nInstant file initialization is allowed for transaction log growth on databases that have transparent data encryption (TDE) enabled, due to the nature of how the transaction log file is expanded, and the fact that the transaction log is written into in a serial fashion.","checkContent":"Review system configuration to determine whether IFI support has been enabled (IFI is enabled by default).\n\nRun the following query in SSMS:\n\nSELECT\n\tservicename\n\t,instant_file_initialization_enabled\nFROM sys.dm_server_services \n\nIf the column instant_file_initialization_enabled returns a value of \"Y\", then IFI is enabled.\n\nAlternatively, navigate to Start >> Control Panel >> System and Security >> Administrative Tools >> Local Security Policy >> Local Policies >> User Rights Assignment >> Perform volume maintenance tasks.\n\nThe default SQL service account for a default instance is NT SERVICE\\MSSQLSERVER or for a named instance is NT SERVICE\\MSSQL$InstanceName.\n\nIf the SQL service account or SQL service SID has been granted \"Perform volume maintenance tasks\" Local Rights Assignment, this means that IFI is enabled.\n\nReview the system documentation to determine if IFI is required.\n\nIf IFI is enabled but not documented as required, this is a finding.\n\nIf IFI is not enabled, this is not a finding.","fixText":"If 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.\n\nTo grant an account the \"Perform volume maintenance tasks\" permission:\n\n1. On the computer where the data file will be created, open the Local Security Policy application (secpol.msc).\n2. In the left pane, expand \"Local Policies\" then select \"User Rights Assignment\".\n3. In the right pane, double-click \"Perform volume maintenance tasks\".\n4. Select \"Add User or Group\" and add the SQL Server service account.\n5. Select \"Apply\", then close all Local Security Policy dialog boxes.\n6. Restart the SQL Server service.\n7. Check the SQL Server error log at startup.","ccis":["CCI-001090"]},{"vulnId":"V-271328","ruleId":"SV-271328r1137657_rule","severity":"medium","ruleTitle":"SQL Server must prevent unauthorized and unintended information transfer via shared system resources.","description":"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.","checkContent":"Review system documentation to determine whether common criteria compliance is required due to potential impact on system performance. \n\nSQL Server Residual Information Protection (RIP) requires a memory allocation to be overwritten with a known pattern of bits before memory is reallocated to a new resource. Meeting the RIP standard can contribute to improved security; however, overwriting the memory allocation can slow performance. After the common criteria compliance enabled option is enabled, the overwriting occurs. \n\nReview the Instance configuration: \n\nSELECT value_in_use\nFROM sys.configurations\nWHERE name = 'common criteria compliance enabled'\n\nIf \"value_in_use\" is set to \"1\" this is not a finding.\n\nIf \"value_in_use\" is set to \"0\" this is a finding. \n\nIf no results are returned, common criteria compliance is not available in the installed version of SQL Server, this is a finding. Common criteria compliance is only supported in Enterprise and Developer editions of SQL Server.\n\nNote: Enabling this feature may impact performance on highly active SQL Server instances. If an exception justifying setting SQL Server RIP to disabled (value_in_use set to \"0\") has been documented and approved, then this is downgraded to a CAT III finding.","fixText":"Configure SQL Server to effectively protect the private resources of one process or user from unauthorized access by another process or user. \n\nTo enable the use of [Common Criteria Compliance], from the query prompt: \n \nEXEC SP_CONFIGURE 'show advanced options', 1; \nRECONFIGURE WITH OVERRIDE;\nEXEC SP_CONFIGURE 'common criteria compliance enabled', 1;\nRECONFIGURE WITH OVERRIDE;\nEXEC SP_CONFIGURE 'show advanced options', 0; \nRECONFIGURE WITH OVERRIDE;","ccis":["CCI-001090"]},{"vulnId":"V-271329","ruleId":"SV-271329r1137658_rule","severity":"medium","ruleTitle":"Access to database files must be limited to relevant processes and to authorized, administrative users.","description":"Applications, including SQL Server, must prevent unauthorized and unintended information transfer via shared system resources. Permitting only DBMS 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.","checkContent":"Review the permissions granted to users by the operating system/file system on the database files, database log files, and database backup files. \n\nTo obtain the location of SQL Server data, transaction log, and backup files, open and execute the supplemental file \"Get SQL Data and Backup Directories.sql\".\n\nFor each of the directories returned by the above script, verify whether the correct permissions have been applied.\n\n1. Launch Windows Explorer.\n2. Navigate to the folder.\n3. Right-click the folder and click \"Properties\".\n4. Navigate to the \"Security\" tab.\n5. Review the listing of principals and permissions.\n\nAccount Type Directory Type Permission\n-----------------------------------------------------------------------------------------------\nDatabase Administrators ALL Full Control\nSQL Server Service SID Data; Log; Backup; Full Control\nSQL Server Agent Service SID Backup Full Control\nSYSTEM ALL Full Control\nCREATOR OWNER ALL Full Control\n\nFor information on how to determine a \"Service SID\", refer to https://aka.ms/sql-service-sids.\n\nAdditional permission requirements, including full directory permissions and operating system rights for SQL Server, are documented at https://aka.ms/sqlservicepermissions.\n\nIf any additional permissions are granted but not documented as authorized, this is a finding.","fixText":"Remove any unauthorized permission grants from SQL Server data, log, and backup directories.\n\n1. On the \"Security\" tab, highlight the user entry.\n2. Click \"Remove\".","ccis":["CCI-001090"]},{"vulnId":"V-271331","ruleId":"SV-271331r1108609_rule","severity":"medium","ruleTitle":"SQL Server and associated applications must reserve the use of dynamic code execution for situations that require it.","description":"With respect to database management systems, one class of threat is known as SQL Injection, or more generally, code injection. It takes advantage of the dynamic execution capabilities of various programming languages, including dialects of SQL. In such cases, the attacker deduces the manner in which SQL statements are being processed, either from inside knowledge or by observing system behavior in response to invalid inputs. When the attacker identifies scenarios where SQL queries are being assembled by application code (which may be within the database or separate from it) and executed dynamically, the attacker is then able to craft input strings that subvert the intent of the query. Potentially, the attacker can gain unauthorized access to data, including security settings, and severely corrupt or destroy the database.\n\nThe principal protection against code injection is not to use dynamic execution except where it provides necessary functionality that cannot be used otherwise. Use strongly typed data items rather than general-purpose strings as input parameters to task-specific, precompiled stored procedures and functions (and triggers).\n\nThis calls for inspection of application source code, which will require collaboration with the application developers. It is recognized that in many cases, the database administrator (DBA) is organizationally separate from the application developers, and may have limited, if any, access to source code. Nevertheless, protections of this type are so important to the secure operation of databases that they must not be ignored. At a minimum, the DBA must attempt to obtain assurances from the development organization that this issue has been addressed and must document what has been discovered.","checkContent":"Review DBMS source code (stored procedures, functions, triggers) and application source code, to identify cases of dynamic code execution.\n\nIf dynamic code execution is employed in circumstances where the objective could practically be satisfied by static execution with strongly typed parameters, this is a finding.","fixText":"Where dynamic code execution is employed in circumstances where the objective could practically be satisfied by static execution with strongly typed parameters, modify the code to do so.","ccis":["CCI-001310"]},{"vulnId":"V-271332","ruleId":"SV-271332r1108612_rule","severity":"medium","ruleTitle":"SQL Server and associated applications, when making use of dynamic code execution, must scan input data for invalid values that may indicate a code injection attack.","description":"With respect to database management systems, one class of threat is known as SQL Injection, or more generally, code injection. It takes advantage of the dynamic execution capabilities of various programming languages, including dialects of SQL. In such cases, the attacker deduces the manner in which SQL statements are being processed, either from inside knowledge or by observing system behavior in response to invalid inputs. When the attacker identifies scenarios where SQL queries are being assembled by application code (which may be within the database or separate from it) and executed dynamically, the attacker is then able to craft input strings that subvert the intent of the query. Potentially, the attacker can gain unauthorized access to data, including security settings, and severely corrupt or destroy the database.\n\nThe principal protection against code injection is not to use dynamic execution except where it provides necessary functionality that cannot be used otherwise. Use strongly typed data items rather than general-purpose strings as input parameters to task-specific, precompiled stored procedures and functions (and triggers).\n\nWhen dynamic execution is necessary, ways to mitigate the risk include the following, which should be implemented both in the on-screen application and at the database level, in the stored procedures:\n- Allow strings as input only when necessary. \n- Rely on data typing to validate numbers, dates, etc. Do not accept invalid values. If substituting other values for them, think carefully about whether this could be subverted.\n- Limit the size of input strings to what is truly necessary.\n- If single quotes/apostrophes, double quotes, semicolons, equals signs, angle brackets, or square brackets will never be valid as input, reject them.\n- If comment markers will never be valid as input, reject them. In SQL, these are -- or /* */ \n- If HTML and XML tags, entities, comments, etc., will never be valid, reject them.\n- If wildcards are present, reject them unless truly necessary. In SQL these are the underscore and the percentage sign, and the word ESCAPE is also a clue that wildcards are in use.\n- If SQL key words, such as SELECT, INSERT, UPDATE, DELETE, CREATE, ALTER, DROP, ESCAPE, UNION, GRANT, REVOKE, DENY, MODIFY will never be valid, reject them. Use case-insensitive comparisons when searching for these. Bear in mind that some of these words, particularly Grant (as a person's name), could also be valid input. \n- If there are range limits on the values that may be entered, enforce those limits.\n- Institute procedures for inspection of programs for correct use of dynamic coding, by a party other than the developer.\n- Conduct rigorous testing of program modules that use dynamic coding, searching for ways to subvert the intended use.\n- Record the inspection and testing in the system documentation.\n- Bear in mind that all this applies not only to screen input, but also to the values in an incoming message to a web service or to a stored procedure called by a software component that has not itself been hardened in these ways. Not only can the caller be subject to such vulnerabilities; it may itself be the attacker.\n\nThis calls for inspection of application source code, which will require collaboration with the application developers. It is recognized that in many cases, the database administrator (DBA) is organizationally separate from the application developers, and may have limited, if any, access to source code. Nevertheless, protections of this type are so important to the secure operation of databases that they must not be ignored. At a minimum, the DBA must attempt to obtain assurances from the development organization that this issue has been addressed and must document what has been discovered.","checkContent":"Review DBMS source code (stored procedures, functions, triggers) and application source code to identify cases of dynamic code execution.\n\nIf dynamic code execution is employed without protective measures against code injection, this is a finding.","fixText":"Where dynamic code execution is used, modify the code to implement protections against code injection.","ccis":["CCI-001310"]},{"vulnId":"V-271334","ruleId":"SV-271334r1109125_rule","severity":"medium","ruleTitle":"SQL Server must reveal detailed error messages only to documented and approved individuals or roles.","description":"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. \n \nSome default DBMS error messages can contain information that could aid an attacker in, among other things, identifying the database type, host address, or state of the database. Custom errors may contain sensitive customer information. \n \nIt is important that detailed error messages be visible only to those who are authorized to view them; that general users receive only generalized acknowledgment that errors have occurred; and that these generalized messages appear only when relevant to the user's task. For example, a message along the lines of, \"An error has occurred. Unable to save your changes. If this problem persists, please contact your help desk.\" would be relevant. A message such as \"Warning: your transaction generated a large number of page splits\" would likely not be relevant. \"ABGQ is not a valid widget code.\" would be appropriate; but \"The INSERT statement conflicted with the FOREIGN KEY constraint \"WidgetTransactionFK\". The conflict occurred in database \"DB7\", table \"dbo.WidgetMaster\", column 'WidgetCode'\" would not, as it reveals too much about the database structure.","checkContent":"Error messages within applications, custom database code (stored procedures, triggers) must be enforced by guidelines and code review practices. \n\nSQL Server generates certain system events and user-defined events to the SQL Server error log. The SQL Server error log can be viewed using SQL Server Management Studio GUI. All users granted the security admin or sysadmin level of permission are able to view the logs. Review the users returned in the following script: \n\nUSE master \nGO\nSELECT Name \nFROM syslogins \nWHERE (sysadmin = 1 or securityadmin = 1) \nand hasaccess = 1; \n\nIf any nonauthorized users have access to the SQL Server Error Log located at Program Files\\Microsoft SQL Server\\MSSQL.n\\MSSQL\\LOG, this is a finding. \n\nIn 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. \n\nIf any nonauthorized users have access to the SQL Server Error Log in SQL Server Management Studio or if documentation does not exist stating that full error messages must be returned, this is a finding.\n\nOtherwise, verify if trace flag 3625 is enabled to mask certain system-level error information returned to nonadministrative users. \n \nLaunch SQL Server Configuration Manager >> select SQL Server Services >> select the SQL Server >> right-click and select Properties >> select Startup Parameters tab >> verify -T3625 exists in the dialogue window.\n\nOR\n\nRun the query:\nDBCC TRACESTATUS;\n\nIf TraceFlag 3625 does not return with Status = 1, and if documentation does not exist stating that full error messages must be returned, this is a finding.","fixText":"Configure audit logging, tracing, and/or custom code in the database or application to record detailed error messages generated by SQL Server for review by authorized personnel. \n \nIf any nonauthorized users have access to the SQL Server Error Log in SQL Server Management Studio, use the REVOKE or DENY commands to remove them from the security admin or sysadmin roles.\n \nIf any nonauthorized users have access to the SQL Server Error Log located at Program Files\\Microsoft SQL Server\\MSSQL.n\\MSSQL\\LOG, remove their permissions. \n \nConsider enabling trace flag 3625 to mask certain system-level error information returned to nonadministrative users. \n\nConfigure audit logging, tracing and/or custom code in the database or application to record detailed error messages generated by SQL Server, for review by authorized personnel. \n \nIf any nonauthorized users have access to the SQL Server Error Log in SQL Server Management Studio, use the REVOKE or DENY commands to remove them from the security admin or sysadmin roles. \n\nIf any nonauthorized users have access to the SQL Server Error Log located at Program Files\\Microsoft SQL Server\\MSSQL.n\\MSSQL\\LOG, remove their permissions. \n \nEnable trace flag 3625 to mask certain system-level error information returned to nonadministrative users. \n \nTo launch SQL Server Configuration Manager, select SQL Server Services, select the SQL Server, then right-click and select \"Properties\". Select the \"Startup Parameters\" tab, enter \"-T3625\", and then click \"Add\". Click \"OK\", then restart SQL instance.","ccis":["CCI-001314"]},{"vulnId":"V-271341","ruleId":"SV-271341r1111081_rule","severity":"medium","ruleTitle":"SQL Server must prevent nonprivileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures.","description":"Preventing nonprivileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges. \n \nSystem documentation should include a definition of the functionality considered privileged. \n \nDepending on circumstances, privileged functions can include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Nonprivileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from nonprivileged users. \n \nA privileged function in SQL Server/database context is any operation that modifies the structure of the database, its built-in logic, or its security settings. This would include all Data Definition Language (DDL) statements and all security-related statements. In an SQL environment, it encompasses, but is not necessarily limited to: \nCREATE \nALTER \nDROP \nGRANT \nREVOKE \nDENY \n \nThere may also be Data Manipulation Language (DML) statements that, subject to context, should be regarded as privileged. Possible examples include: \nTRUNCATE TABLE; \nDELETE, or \nDELETE affecting more than n rows, for some n, or \nDELETE without a WHERE clause; \n \nUPDATE or \nUPDATE affecting more than n rows, for some n, or \nUPDATE without a WHERE clause; \n \nAny SELECT, INSERT, UPDATE, or DELETE to an application-defined security table executed by other than a security principal. \n \nDepending on the capabilities of SQL Server and the design of the database and associated applications, the prevention of unauthorized use of privileged functions may be achieved by means of DBMS security features, database triggers, other mechanisms, or a combination of these.","checkContent":"Review server-level securables and built-in role membership to ensure only authorized users have privileged access and the ability to create server-level objects and grant permissions to themselves or others. \n \nReview the system documentation to determine the required levels of protection for DBMS server securables by type of login. \n \nReview the permissions in place on the server. If the actual permissions do not match the documented requirements, this is a finding. \n \nGet all permission assignments to logins and roles: \n \nSELECT DISTINCT \n CASE \n WHEN SP.class_desc IS NOT NULL THEN \n CASE \n WHEN SP.class_desc = 'SERVER' AND S.is_linked = 0 THEN 'SERVER' \n WHEN SP.class_desc = 'SERVER' AND S.is_linked = 1 THEN 'SERVER (linked)' \n ELSE SP.class_desc \n END \n WHEN E.name IS NOT NULL THEN 'ENDPOINT' \n WHEN S.name IS NOT NULL AND S.is_linked = 0 THEN 'SERVER' \n WHEN S.name IS NOT NULL AND S.is_linked = 1 THEN 'SERVER (linked)' \n WHEN P.name IS NOT NULL THEN 'SERVER_PRINCIPAL' \n ELSE '???' \n END AS [Securable Class], \n CASE \n WHEN E.name IS NOT NULL THEN E.name \n WHEN S.name IS NOT NULL THEN S.name \n WHEN P.name IS NOT NULL THEN P.name \n ELSE '???' \n END AS [Securable], \n P1.name AS [Grantee], \n P1.type_desc AS [Grantee Type], \n sp.permission_name AS [Permission], \n sp.state_desc AS [State], \n P2.name AS [Grantor], \n P2.type_desc AS [Grantor Type] \nFROM \n sys.server_permissions SP \n INNER JOIN sys.server_principals P1 \n ON P1.principal_id = SP.grantee_principal_id \n INNER JOIN sys.server_principals P2 \n ON P2.principal_id = SP.grantor_principal_id \n \n FULL OUTER JOIN sys.servers S \n ON SP.class_desc = 'SERVER' \n AND S.server_id = SP.major_id \n \n FULL OUTER JOIN sys.endpoints E \n ON SP.class_desc = 'ENDPOINT' \n AND E.endpoint_id = SP.major_id \n \n FULL OUTER JOIN sys.server_principals P \n ON SP.class_desc = 'SERVER_PRINCIPAL' \n AND P.principal_id = SP.major_id \n \nGet all server role memberships: \n \nSELECT \n R.name AS [Role], \n M.name AS [Member] \nFROM \n sys.server_role_members X \n INNER JOIN sys.server_principals R ON R.principal_id = X.role_principal_id \n INNER JOIN sys.server_principals M ON M.principal_id = X.member_principal_id \n \nThe CONTROL SERVER permission is similar but not identical to the sysadmin fixed server role. Permissions do not imply role memberships, and role memberships do not grant permissions (e.g., CONTROL SERVER does not imply membership in the sysadmin fixed server role). \n \nEnsure only the documented and approved logins have privileged functions in SQL Server. \n \nIf the current configuration does not match the documented baseline, this is a finding.","fixText":"Restrict the granting of permissions to server-level securables to only those authorized, most notably: members of sysadmin and securityadmin built-in instance-level roles, CONTROL SERVER permission, and use of the GRANT with GRANT permission.","ccis":["CCI-002235"]},{"vulnId":"V-271342","ruleId":"SV-271342r1108642_rule","severity":"medium","ruleTitle":"Use of credentials and proxies must be restricted to necessary cases only.","description":"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. \n \nPrivilege elevation must be used only where necessary and protected from misuse.","checkContent":"Review the server documentation to obtain a listing of accounts used for executing external processes. Execute the following to obtain a listing of accounts currently configured for use by external processes. \n \nSELECT C.name AS credential_name, C.credential_identity \nFROM sys.credentials C \nGO \n \nSELECT P.name AS proxy_name, C.name AS credential_name, C.credential_identity \nFROM sys.credentials C \nJOIN msdb.dbo.sysproxies P ON C.credential_id = P.credential_id \nWHERE P.enabled = 1 \nGO \n \nIf any Credentials or SQL Agent Proxy accounts are returned that are not documented and authorized, this is a finding.","fixText":"Remove any SQL Agent Proxy accounts and credentials that are not authorized. \n \nDROP CREDENTIAL \nGO \n \nUSE [msdb] \nEXEC sp_delete_proxy @proxy_name = '' \nGO","ccis":["CCI-002233"]},{"vulnId":"V-271343","ruleId":"SV-271343r1108645_rule","severity":"medium","ruleTitle":"SQL Server must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements.","description":"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. \n \nIf support personnel are not notified immediately upon storage volume utilization reaching 75 percent, they are unable to plan for storage capacity expansion. \n \nThe appropriate support staff include, at a minimum, the information system security officer (ISSO), the database administrator (DBA), and system administrator (SA). \n \nMonitoring of free space can be accomplished using Microsoft System Center or a third-party monitoring tool.","checkContent":"If the database is setup to write audit logs using APPLICATION or SECURITY event logs rather than writing to a file, this is Not Applicable.\n\nCheck the server documentation for the SQL Audit file size configurations. Locate the Audit file path and drive. \n \nSELECT max_file_size, max_rollover_files, log_file_path AS \"Audit Path\" \nFROM sys.server_file_audits \n \nCalculate the space needed as the maximum file size and number of files from the SQL Audit File properties. \n \nIf the calculated product of the \"max_file_size\" times the \"max_rollover_files\" exceeds the size of the storage location, this is a finding; \n\nOR if \"max_file_size\" is set to \"0\" (Unlimited), this is a finding;\n\nOR if \"max_rollover_files\" are set to \"0\" (None) or \"2147483647\" (Unlimited), this is a finding.","fixText":"Review the SQL Audit file location; ensure the destination has enough space available to accommodate the maximum total size of all files that could be written. \n \nConfigure the maximum number of audit log files that are to be generated, staying within the number of logs the system was sized to support. \n \nUpdate the \"max_files\" or \"max_rollover_files\" parameter of the audits to ensure the correct number of files is defined.\n\nIf writing to application event logs or security logs, space considerations are covered in the Windows Server STIGs. Be sure to reference these depending on the OS in use.","ccis":["CCI-001849"]},{"vulnId":"V-271344","ruleId":"SV-271344r1111082_rule","severity":"medium","ruleTitle":"SQL Server must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75 percent of maximum audit record storage capacity.","description":"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. \n \nIf support personnel are not notified immediately upon storage volume utilization reaching 75 percent, they are unable to plan for storage capacity expansion. \n \nThe appropriate support staff include, at a minimum, the information system security officer (ISSO), the database administrator (DBA), and the system administrator (SA). \n \nMonitoring of free space can be accomplished using Microsoft System Center or a third-party monitoring tool.","checkContent":"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. \n \nIf no alert exists to notify support staff in the event the SQL Audit drive reaches 75 percent, this is a finding.","fixText":"Use 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 percent.","ccis":["CCI-001855"]},{"vulnId":"V-271345","ruleId":"SV-271345r1109254_rule","severity":"medium","ruleTitle":"SQL Server must provide an immediate real-time alert to appropriate support staff of all audit log failures.","description":"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. \n\nThe appropriate support staff include, at a minimum, the information system security officer (ISSO), the database administrator (DBA), and the system administrator (SA).\n\nA failure of database auditing will result in either the database continuing to function without auditing or in a complete halt to database operations. When audit processing fails, appropriate personnel must be alerted immediately to avoid further downtime or unaudited transactions.\n\nAlerts 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.","checkContent":"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.\n\nIf real-time alerts are not sent upon auditing failure, this is a finding.","fixText":"Configure the system to provide immediate real-time alerts to appropriate support staff when an audit log failure occurs.","ccis":["CCI-001858"]},{"vulnId":"V-271346","ruleId":"SV-271346r1109256_rule","severity":"medium","ruleTitle":"SQL Server must record time stamps in audit records and application data that can be mapped to Coordinated Universal Time (UTC), formerly Greenwich Mean Time (GMT).","description":"If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis. \n \nTime stamps generated by SQL Server must include date and time. Time is commonly expressed in UTC, a modern continuation of GMT, or local time with an offset from UTC.","checkContent":"SQL Server Audits store the timestamp in UTC time. \n \nDetermine if the computer is joined to a domain. \n \nSELECT DEFAULT_DOMAIN()[DomainName] \n \nIf this is not NULL, this is not a finding. \n \nIf the computer is not joined to a domain, determine what the time source is. (Run the following command in an elevated PowerShell session.) \n \n w32tm /query /source \n \nIf the results of the command return \"Local CMOS Clock\" and this is not documented with justification and authorizing official (AO) authorization, this is a finding. \n \nIf the OS does not synchronize with a time server, review the procedure for maintaining accurate time on the system. \n \nIf such a procedure does not exist, this is a finding. \n \nIf the procedure exists, review evidence that the correct time is actually maintained. \n \nIf the evidence indicates otherwise, this is a finding.","fixText":"Where possible, configure the operating system to automatic synchronize with an official time server, using NTP. \n \nWhere there is reason not to implement automatic synchronization with an official time server, using NTP, document the reason, and the procedure for maintaining the correct time, and obtain AO approval. Enforce the procedure.","ccis":["CCI-001890"]},{"vulnId":"V-271349","ruleId":"SV-271349r1108938_rule","severity":"medium","ruleTitle":"Windows must enforce access restrictions associated with changes to the configuration of the SQL Server instance.","description":"Failure to provide logical access restrictions associated with changes to configuration may have significant effects on the overall security of the system. \n \nWhen 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. \n \nAccordingly, only qualified and authorized individuals should be allowed to obtain access to system components for the purposes of initiating changes, including upgrades and modifications.","checkContent":"Obtain a list of users who have privileged access to the server via the local administrators group. \n \n1. Launch lusrmgr.msc.\n2. Select \"Groups\".\n3. Double-click \"Administrators\".\n \nAlternatively, execute the following command in PowerShell: \n\nnet localgroup administrators \n \nCheck the server documentation to verify the users returned are authorized. \n \nIf the users are not documented and authorized, this is a finding.","fixText":"Remove users from the local Administrators group who are not authorized.","ccis":["CCI-001813"]},{"vulnId":"V-271350","ruleId":"SV-271350r1111084_rule","severity":"medium","ruleTitle":"SQL Server must enforce access restrictions associated with changes to the configuration of the instance.","description":"Failure to provide logical access restrictions associated with changes to configuration may have significant effects on the overall security of the system. \n \nWhen 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. \n \nAccordingly, only qualified and authorized individuals should be allowed to obtain access to system components for the purposes of initiating changes, including upgrades and modifications.","checkContent":"Obtain a list of logins who have privileged permissions and role memberships in SQL. \n \nExecute the following to obtain a list of logins and roles and their respective permissions assignment: \nSELECT p.name AS Principal, \np.type_desc AS Type, \nsp.permission_name AS Permission, \nsp.state_desc AS State \nFROM sys.server_principals p \nINNER JOIN sys.server_permissions sp ON p.principal_id = sp.grantee_principal_id \nWHERE sp.permission_name = 'CONTROL SERVER' \nOR sp.state = 'W' \n \nExecute the following to obtain a list of logins and their role memberships: \nSELECT m.name AS Member, \nm.type_desc AS Type, \nr.name AS Role \nFROM sys.server_principals m \nINNER JOIN sys.server_role_members rm ON m.principal_id = rm.member_principal_id \nINNER JOIN sys.server_principals r ON rm.role_principal_id = r.principal_id \nWHERE r.name IN ('sysadmin','securityadmin','serveradmin') \n \nCheck 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.","fixText":"Revoke unauthorized permissions from principals. \n \nhttps://learn.microsoft.com/en-us/sql/t-sql/statements/revoke-server-permissions-transact-sql?\n \nRemove unauthorized logins from roles. \n \nALTER SERVER ROLE DROP MEMBER login; \n \nhttps://learn.microsoft.com/en-us/sql/t-sql/statements/alter-server-role-transact-sql?","ccis":["CCI-001813"]},{"vulnId":"V-271351","ruleId":"SV-271351r1167494_rule","severity":"medium","ruleTitle":"SQL Server must produce audit records when attempts to modify SQL Server configuration and privileges occur within the database(s).","description":"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.\n \nEnforcement 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.\n\nChanges in the permissions, privileges, and roles granted to users and roles, as well as privileged activity, 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.\n \nA privileged function in this context is any operation that modifies the structure of the database, its built-in logic, or its security settings. This would include all Data Definition Language (DDL) statements and all security-related statements. In a SQL environment, it encompasses, but is not necessarily limited to, CREATE, ALTER, DROP, GRANT, REVOKE, and DENY. \n \nThere may also be Data Manipulation Language (DML) statements that, subject to context, should be regarded as privileged. Possible examples in SQL include TRUNCATE TABLE, SELECT, INSERT, UPDATE, or DELETE (to a security table executed by a user other than a security principal).\n \nDepending on the capabilities of SQL Server and the design of the database and associated applications, audit logging may be achieved by means of DBMS auditing features, database triggers, other mechanisms, or a combination of these. \n \nNote that it is particularly important to audit, and tightly control, any action that weakens the implementation of this requirement, since the objective is to have a complete audit trail of all administrative activity.\n \nTo aid in diagnosis, it is necessary to track failed attempts in addition to the successful ones.\n\nSatisfies: SRG-APP-000381-DB-000361, SRG-APP-000495-DB-000326, SRG-APP-000495-DB-000327, SRG-APP-000495-DB-000328, SRG-APP-000495-DB-000329, SRG-APP-000499-DB-000330, SRG-APP-000499-DB-000331, SRG-APP-000504-DB-000354, SRG-APP-000504-DB-000355","checkContent":"Review the SQL configuration to verify that audit records are produced when denied actions occur.\n\nTo determine if an audit is configured, execute the following script:\n\nSELECT name AS 'Audit Name',\nstatus_desc AS 'Audit Status',\naudit_file_path AS 'Current Audit File'\nFROM sys.dm_server_audit_status\n\nIf no records are returned, this is a finding.\n\nExecute the following to verify the following events are included in the server audit specification:\n\nAPPLICATION_ROLE_CHANGE_PASSWORD_GROUP,\nAUDIT_CHANGE_GROUP,\nBACKUP_RESTORE_GROUP,\nDATABASE_CHANGE_GROUP,\nDATABASE_OBJECT_ACCESS_GROUP,\nDATABASE_OBJECT_CHANGE_GROUP,\nDATABASE_OBJECT_OWNERSHIP_CHANGE_GROUP,\nDATABASE_OBJECT_PERMISSION_CHANGE_GROUP,\nDATABASE_OWNERSHIP_CHANGE_GROUP,\nDATABASE_OPERATION_GROUP,\nDATABASE_PERMISSION_CHANGE_GROUP,\nDATABASE_PRINCIPAL_CHANGE_GROUP,\nDATABASE_PRINCIPAL_IMPERSONATION_GROUP,\nDATABASE_ROLE_MEMBER_CHANGE_GROUP,\nDBCC_GROUP,\nLOGIN_CHANGE_PASSWORD_GROUP,\nLOGOUT_GROUP,\nSCHEMA_OBJECT_OWNERSHIP_CHANGE_GROUP,\nSCHEMA_OBJECT_PERMISSION_CHANGE_GROUP,\nSERVER_OBJECT_CHANGE_GROUP,\nSERVER_OBJECT_OWNERSHIP_CHANGE_GROUP,\nSERVER_OBJECT_PERMISSION_CHANGE_GROUP,\nSERVER_OPERATION_GROUP,\nSERVER_PERMISSION_CHANGE_GROUP,\nSERVER_PRINCIPAL_CHANGE_GROUP,\nSERVER_PRINCIPAL_IMPERSONATION_GROUP,\nSERVER_ROLE_MEMBER_CHANGE_GROUP,\nSERVER_STATE_CHANGE_GROUP,\nTRACE_CHANGE_GROUP,\nUSER_CHANGE_PASSWORD_GROUP\n\nSELECT a.name AS 'AuditName',\ns.name AS 'SpecName',\nd.audit_action_name AS 'ActionName',\nd.audited_result AS 'Result'\nFROM sys.server_audit_specifications s\nJOIN sys.server_audits a ON s.audit_guid = a.audit_guid\nJOIN sys.server_audit_specification_details d ON s.server_specification_id = d.server_specification_id\nWHERE a.is_state_enabled = 1\nAND d.audit_action_name IN (\n'APPLICATION_ROLE_CHANGE_PASSWORD_GROUP',\n'AUDIT_CHANGE_GROUP',\n'BACKUP_RESTORE_GROUP',\n'DATABASE_CHANGE_GROUP',\n'DATABASE_OBJECT_ACCESS_GROUP',\n'DATABASE_OBJECT_CHANGE_GROUP',\n'DATABASE_OBJECT_OWNERSHIP_CHANGE_GROUP',\n'DATABASE_OBJECT_PERMISSION_CHANGE_GROUP',\n'DATABASE_OWNERSHIP_CHANGE_GROUP',\n'DATABASE_OPERATION_GROUP',\n'DATABASE_PERMISSION_CHANGE_GROUP',\n'DATABASE_PRINCIPAL_CHANGE_GROUP',\n'DATABASE_PRINCIPAL_IMPERSONATION_GROUP',\n'DATABASE_ROLE_MEMBER_CHANGE_GROUP', \n'DBCC_GROUP',\n'LOGIN_CHANGE_PASSWORD_GROUP',\n'LOGOUT_GROUP',\n'SCHEMA_OBJECT_OWNERSHIP_CHANGE_GROUP',\n'SCHEMA_OBJECT_PERMISSION_CHANGE_GROUP',\n'SERVER_OBJECT_CHANGE_GROUP',\n'SERVER_OBJECT_OWNERSHIP_CHANGE_GROUP',\n'SERVER_OBJECT_PERMISSION_CHANGE_GROUP',\n'SERVER_OPERATION_GROUP',\n'SERVER_PERMISSION_CHANGE_GROUP',\n'SERVER_PRINCIPAL_CHANGE_GROUP',\n'SERVER_PRINCIPAL_IMPERSONATION_GROUP',\n'SERVER_ROLE_MEMBER_CHANGE_GROUP',\n'SERVER_STATE_CHANGE_GROUP',\n'TRACE_CHANGE_GROUP',\n'USER_CHANGE_PASSWORD_GROUP'\n)\nOrder by d.audit_action_name\n\nIf the identified groups are not returned, this is a finding.","fixText":"Add the required events to the server audit specification to audit denied actions.\n\nRefer to the supplemental file \"SQL2022Audit.sql\" script.\n\nReference: https://learn.microsoft.com/en-us/sql/relational-databases/security/auditing/sql-server-audit-database-engine?","ccis":["CCI-003938","CCI-000172"]},{"vulnId":"V-271358","ruleId":"SV-271358r1137659_rule","severity":"medium","ruleTitle":"SQL Server services must be configured to run under unique dedicated user accounts.","description":"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.","checkContent":"Review the server documentation to obtain a listing of required service accounts. Review the accounts configured for all SQL Server services installed on the server. \n \nRun the following query in SSMS:\n\nSELECT servicename,service_account FROM sys.dm_server_services\n \nReview the returned results. If any services are configured with the same service account or with an account that is not documented and authorized, this is a finding.","fixText":"Configure SQL Server services to have a documented, dedicated account. \n \nFor nondomain servers, consider using virtual service accounts (VSAs). \nFor more information, refer to: https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/configure-windows-service-accounts-and-permissions? \n \nFor standalone domain-joined servers, consider using managed service accounts. \nFor more information, refer to: https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/configure-windows-service-accounts-and-permissions?\n \nFor clustered instances, consider using group managed service accounts. \nFor more information, refer to: https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/configure-windows-service-accounts-and-permissions? \nor \nhttps://learn.microsoft.com/en-us/archive/blogs/markweberblog/group-managed-service-accounts-gmsa-and-sql-server-2016","ccis":["CCI-002530"]},{"vulnId":"V-271359","ruleId":"SV-271359r1137659_rule","severity":"medium","ruleTitle":"SQL Server must maintain a separate execution domain for each executing process.","description":"Database management systems can maintain separate execution domains for each executing process by assigning each process a separate address space. \n \nEach 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. \n \nMaintaining separate execution domains for executing processes can be achieved, for example, by implementing separate address spaces.","checkContent":"Review the server documentation to determine whether use of CLR assemblies is required. Run the following query to determine whether CLR is enabled for the instance: \nSELECT name, value, value_in_use \nFROM sys.configurations \nWHERE name = 'clr enabled' \n \nIf \"value_in_use\" is a \"1\" and CLR is not required, this is a finding.","fixText":"Disable use of or remove any CLR code that is not authorized.\n\nTo disable the use of CLR, from the query prompt: \nEXEC SP_CONFIGURE 'clr enabled', 0;\nRECONFIGURE WITH OVERRIDE;","ccis":["CCI-002530"]},{"vulnId":"V-271362","ruleId":"SV-271362r1108702_rule","severity":"medium","ruleTitle":"When invalid inputs are received, the SQL Server must behave in a predictable and documented manner that reflects organizational and system objectives.","description":"A common vulnerability is unplanned behavior when invalid inputs are received. This requirement guards against adverse or unintended system behavior caused by invalid inputs, where information system responses to the invalid input may be disruptive or cause the system to fail into an unsafe state.\n\nThe behavior will be derived from the organizational and system requirements and includes, but is not limited to, notification of the appropriate personnel, creating an audit record, and rejecting invalid input.\n\nThis calls for inspection of application source code, which will require collaboration with the application developers. It is recognized that in many cases, the database administrator (DBA) is organizationally separate from the application developers, and may have limited, if any, access to source code. Nevertheless, protections of this type are so important to the secure operation of databases that they must not be ignored. At a minimum, the DBA must attempt to obtain assurances from the development organization that this issue has been addressed and must document what has been discovered.","checkContent":"Review DBMS code (stored procedures, functions, triggers), application code, settings, column and field definitions, and constraints to determine whether the database is protected against invalid input. \n\nIf code exists that allows invalid data to be acted upon or input into the database, this is a finding. \n\nIf column/field definitions are not reflective of the data, this is a finding. \n\nIf columns/fields do not contain constraints and validity checking where required, this is a finding. \n\nWhere a column/field is noted in the system documentation as necessarily free form, even though its name and context suggest that it should be strongly typed and constrained, the absence of these protections is not a finding. \n\nWhere a column/field is clearly identified by name, caption or context as Notes, Comments, Description, Text, etc., the absence of these protections is not a finding.","fixText":"Use parameterized queries, stored procedures, constraints and foreign keys to validate data input. \n\nModify SQL Server to properly use the correct column data types as required in the database.","ccis":["CCI-002754"]},{"vulnId":"V-271364","ruleId":"SV-271364r1137667_rule","severity":"medium","ruleTitle":"Security-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).","description":"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. \n \nOrganization-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). \n \nThis requirement will apply to software patch management solutions that are used to install patches across the enclave and also to applications themselves that are not part of that patch management solution. For example, many browsers today provide the capability to install their own patch software. Patch criticality, as well as system criticality, will vary. Therefore, the tactical situations regarding the patch management process will also vary. This means that the time period used must be a configurable parameter. Time frames for application of security-relevant software updates may be dependent upon the Information Assurance Vulnerability Management (IAVM) process. \n \nSQL Server will be configured to check for and install security-relevant software updates within an identified time period from the availability of the update. The specific time period will be defined by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs).","checkContent":"Obtain evidence that software patches are consistently applied to SQL Server within the time frame defined for each patch. To be considered supported, Microsoft must report that the version is supported by security patches to known vulnerability. Review the Support dates at https://learn.microsoft.com/en-us/troubleshoot/sql/releases/download-and-install-latest-updates.\n \nCheck the SQL Server version by running the following script: \n\nPrint @@version \n \nIf the SQL Server version is not shown as supported, this is a finding. \n \nIf such evidence cannot be obtained, or the evidence that is obtained indicates a pattern of noncompliance, this is a finding.","fixText":"Upgrade SQL Server to the Microsoft-supported version. Institute and adhere to policies and procedures to ensure that patches are consistently applied to SQL Server within the time allowed.","ccis":["CCI-002605"]},{"vulnId":"V-271365","ruleId":"SV-271365r1138543_rule","severity":"high","ruleTitle":"Microsoft SQL Server products must be a version supported by the vendor.","description":"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.\n\nSystems at unsupported servicing levels or releases will not receive security updates for new vulnerabilities, which leaves them subject to exploitation.\n\nWhen maintenance updates and patches are no longer available, the database software is no longer considered supported and should be upgraded or decommissioned.","checkContent":"Review the system documentation and interview the database administrator.\n\nIdentify all database software components.\n\nReview the version and release information.\n\nVerify the SQL Server version via one of the following methods: \n\nConnect to the server by using Object Explorer in SQL Server Management Studio. After Object Explorer is connected, it will show the version information in parentheses with the username used to connect to the specific instance of SQL Server.\n\nOr, from SQL Server Management Studio execute the following:\nSELECT @@VERSION;\n\nMore information for finding the version is available at the following link: https://learn.microsoft.com/en-us/troubleshoot/sql/releases/find-my-sql-version.\n\nAccess the vendor website or use other means to verify the version is still supported. Refer to https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2016.\n\nIf the installed version or any of the software components are not supported by the vendor, this is a finding.","fixText":"Remove or decommission all unsupported software products.\n\nUpgrade unsupported DBMS or unsupported components to a supported version of the product.","ccis":["CCI-003376"]},{"vulnId":"V-271370","ruleId":"SV-271370r1111091_rule","severity":"medium","ruleTitle":"SQL Server must generate audit records when successful and unsuccessful attempts to modify or delete security objects occur.","description":"Changes and deletions of 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. \n \nTo aid in diagnosis, it is necessary to track failed attempts in addition to the successful ones.\n\nSatisfies: SRG-APP-000496-DB-000334, SRG-APP-000496-DB-000335, SRG-APP-000501-DB-000336, SRG-APP-000501-DB-000337","checkContent":"Review the SQL configuration to verify that audit records are produced when denied actions occur.\n\nTo determine if an audit is configured, execute the following script:\nSELECT name AS 'Audit Name',\nstatus_desc AS 'Audit Status',\naudit_file_path AS 'Current Audit File'\nFROM sys.dm_server_audit_status\n\nIf no records are returned, this is a finding.\n\nExecute the following to verify the events below are included in the server audit specification:\nSCHEMA_OBJECT_CHANGE_GROUP\n\nSELECT a.name AS 'AuditName',\ns.name AS 'SpecName',\nd.audit_action_name AS 'ActionName',\nd.audited_result AS 'Result'\nFROM sys.server_audit_specifications s\nJOIN sys.server_audits a ON s.audit_guid = a.audit_guid\nJOIN sys.server_audit_specification_details d ON s.server_specification_id = d.server_specification_id\nWHERE a.is_state_enabled = 1\nAND d.audit_action_name IN (\n'SCHEMA_OBJECT_CHANGE_GROUP'\n)\nOrder by d.audit_action_name\n\nIf the identified groups are not returned, this is a finding.","fixText":"Add the required events to the server audit specification to audit denied actions.\n\nRefer to the supplemental file \"SQL2022Audit.sql\" script.\n\nReference: https://learn.microsoft.com/en-us/sql/relational-databases/security/auditing/sql-server-audit-database-engine?","ccis":["CCI-000172"]},{"vulnId":"V-271375","ruleId":"SV-271375r1111093_rule","severity":"medium","ruleTitle":"SQL Server must generate audit records when successful and unsuccessful logons or connection attempts occur.","description":"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.\n\nSatisfies: SRG-APP-000503-DB-000350, SRG-APP-000503-DB-000351, SRG-APP-000506-DB-000353","checkContent":"Review the SQL configuration to verify that audit records are produced when denied actions occur.\n\nTo determine if an audit is configured, execute the following script:\nSELECT name AS 'Audit Name',\nstatus_desc AS 'Audit Status',\naudit_file_path AS 'Current Audit File'\nFROM sys.dm_server_audit_status\n\nIf no records are returned, this is a finding.\n\nExecute the following to verify the events below are included in the server audit specification:\nSUCCESSFUL_LOGIN_GROUP\nFAILED_LOGIN_GROUP\n\nSELECT a.name AS 'AuditName',\ns.name AS 'SpecName',\nd.audit_action_name AS 'ActionName',\nd.audited_result AS 'Result'\nFROM sys.server_audit_specifications s\nJOIN sys.server_audits a ON s.audit_guid = a.audit_guid\nJOIN sys.server_audit_specification_details d ON s.server_specification_id = d.server_specification_id\nWHERE a.is_state_enabled = 1\nAND d.audit_action_name IN (\n'SUCCESSFUL_LOGIN_GROUP',\n'FAILED_LOGIN_GROUP'\n)\nOrder by d.audit_action_name\n\nIf the identified groups are not returned, this is a finding.\n\nAlternatively: \n\n1. In SQL Management Studio, right-click on the instance.\n2. Select \"Properties\".\n3. Select \"Security\" on the left side.\n4. Check the setting for \"Login auditing\".\n \nIf \"Both failed and successful logins\" is not selected, this is a finding.","fixText":"Add the required events to the server audit specification to audit denied actions.\n\nRefer to the supplemental file \"SQL2022Audit.sql\" script.\n\nReference: https://learn.microsoft.com/en-us/sql/relational-databases/security/auditing/sql-server-audit-database-engine?\n\nAlternatively, enable \"Both failed and successful logins\".\n\n1. In SQL Management Studio, right-click on the instance.\n2. Select \"Properties\".\n3. Select \"Security\" on the left side.\n4. Select \"Both failed and successful logins\". \n5. Click \"OK\".","ccis":["CCI-000172"]},{"vulnId":"V-271381","ruleId":"SV-271381r1111095_rule","severity":"medium","ruleTitle":"SQL Server must generate audit records for all direct access to the database(s).","description":"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 nonstandard sources.","checkContent":"Determine whether any Server Audits are configured to filter records. From SQL Server Management Studio, execute the following query:\nSELECT name AS AuditName, predicate AS AuditFilter\nFROM sys.server_audits\nWHERE predicate IS NOT NULL\n\nIf any audits are returned, review the associated filters. If any direct access to the database(s) is being excluded, this is a finding.","fixText":"Check the system documentation for required SQL Server Audits. Remove any Audit filters that exclude or reduce required auditing. Update filters to ensure direct access is not excluded.","ccis":["CCI-000172"]},{"vulnId":"V-271385","ruleId":"SV-271385r1108771_rule","severity":"medium","ruleTitle":"The 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.","description":"Information stored in one location is vulnerable to accidental or incidental deletion or alteration. \n \nOff-loading is a common process in information systems with limited audit storage capacity. \n \nThe system 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.","checkContent":"Review the system documentation for a description of how audit records are off-loaded. \n \nIf 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. \n \nIf 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.","fixText":"Configure the system or deploy and configure software tools to transfer audit records to a centralized log management system, continuously and in near-real time where a continuous network connection to the log management system exists, or at least weekly in the absence of such a connection.","ccis":["CCI-001851"]},{"vulnId":"V-271387","ruleId":"SV-271387r1111140_rule","severity":"medium","ruleTitle":"The SQL Server Browser service must be disabled unless specifically required and approved.","description":"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.\n\nThis 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. \n\nThis requirement is not intended to prohibit use of the Browser service in any circumstances. It calls for administrators and management to consider whether the benefits of its use outweigh the potential negative consequences of it being used by an attacker to browse the current infrastructure and retrieve a list of running SQL Server instances.","checkContent":"Open SQL Server Configuration Manager. Select SQL Server Services. Review the Start Mode and State of SQL Server Browser.\n\nIf its Start Type is shown as \"Disabled\", this is not a finding.\n\nIf the need for the SQL Server Browser service is documented and authorized, verify the SQL Instances that do not require use of the SQL Browser Service are hidden with the following SQL script:\nDECLARE @HiddenInstance INT \nEXEC master.dbo.Xp_instance_regread \n N'HKEY_LOCAL_MACHINE', \n N'Software\\Microsoft\\MSSQLServer\\MSSQLServer\\SuperSocketNetLib', \n N'HideInstance', \n @HiddenInstance output \n\nSELECT CASE \n WHEN @HiddenInstance = 0 \n AND Serverproperty('IsClustered') = 0 THEN 'No' \n ELSE 'Yes' \n END AS [Hidden]\n\nIf the value of \"Hidden\" is \"Yes\", this is not a finding.\n\nIf the value of \"Hidden\" is \"No\" and the startup type of the \"SQL Server Browser\" service is not \"Disabled\", this is a finding.","fixText":"If SQL Server Browser is needed, document the justification and obtain the appropriate authorization. \n\nWhere SQL Server Browser is judged unnecessary, the Service can be disabled. \n\nTo disable, in the Services tool, double-click \"SQL Server Browser\". Set \"Startup Type\" to \"Disabled\". If \"Service Status\" is \"Running\", click \"Stop\" and then click \"OK\".","ccis":["CCI-000366"]},{"vulnId":"V-271388","ruleId":"SV-271388r1111098_rule","severity":"medium","ruleTitle":"SQL Server must configure SQL Server Usage and Error Reporting Auditing.","description":"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 view all data Microsoft collects with this feature, for compliance, regulatory or privacy validation reasons.","checkContent":"Review the server documentation to determine if auditing of the telemetry data is required. If auditing of telemetry data is not required, this is not a finding. \n \nIf auditing of telemetry data is required, determine the telemetry service username by executing the following query: \nSELECT name \nFROM sys.server_principals \nWHERE name LIKE '%SQLTELEMETRY%' \n \nReview the values of the following registry key: \nNote: InstanceId refers to the type and instance of the feature (e.g., MSSQL16.SqlInstance, MSAS16.SSASInstance, MSRS16.SSRSInstance). \n \nHKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Microsoft SQL Server\\[InstanceId]\\CPE\\UserRequestedLocalAuditDirectory \n \nIf the registry key does not exist or the value is blank, this is a finding. \n \nNavigate the path defined in the \"UserRequestedLocalAuditDirectory\" registry key in file explorer. \n \nRight-click on the folder and choose \"Properties\". Open the \"Security\" tab.\n \nVerify the SQLTELEMETRY account has the following permissions: \n- List folder contents \n- Read \n- Write \n \nIf the permissions are not set properly on the folder, this is a finding. \n \nOpen services.msc and find the telemetry service. \n- For Database Engine, use SQL Server CEIP service (). \n- For Analysis Services, use SQL Server Analysis Services CEIP (). \n \nRight-click on the service and choose \"Properties\". Verify the \"Startup type\" is \"Automatic.\" \n \nIf the service is not configured to automatically start, this is a finding. \n \nReview 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. \n \nIf no processes and procedures exist for reviewing telemetry data, this is a finding.","fixText":"Configure 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. \n \nCreate a folder to store the telemetry audit data in. \n \nGrant the SQLTELEMETRY service the following permissions on the folder: \n- List folder contents \n- Read \n- Write \n \nCreate and configure the following registry key: \nNote: InstanceId refers to the type and instance of the feature. (e.g., MSSQL16.SqlInstance, MSAS16.SSASInstance, MSRS16.SSRSInstance) \n \nHKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Microsoft SQL Server\\[InstanceId]\\CPE\\UserRequestedLocalAuditDirectory [string] \n \nSet the \"UserRequestedLocalAuditDirectory\" key value to the path of the telemetry audit folder. \n \nSet the telemetry service to start automatically. Restart the service. \n- For Database Engine, use SQL Server CEIP service (). \n- For Analysis Services, use SQL Server Analysis Services CEIP ().","ccis":["CCI-000366"]},{"vulnId":"V-271389","ruleId":"SV-271389r1109133_rule","severity":"medium","ruleTitle":"SQL Server must configure Customer Feedback and Error Reporting.","description":"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.","checkContent":"Review the values for CustomerFeedback and EnableErrorReporting.\n\nOption 1:\nLaunch \"Registry Editor\" \n \nNavigate to:\nHKEY_LOCAL_MACHINE\\Software\\Microsoft\\Microsoft SQL Server\\[InstanceId]\\CPE \nReview the following values: CustomerFeedback, EnableErrorReporting \n \nNavigate to HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Microsoft SQL Server\\160 \nReview the following values: CustomerFeedback, EnableErrorReporting \n \nOption 2:\nRun the PowerShell commands:\n\nGet-ItemProperty -Path \"HKLM:\\Software\\Microsoft\\Microsoft SQL Server\\\\CPE\"\nGet-ItemProperty -Path \"HKLM:\\ Software\\Microsoft\\Microsoft SQL Server\\160\"\n\nReview the following values: CustomerFeedback, EnableErrorReporting\n\nIf this is a classified system, and any of the above values are not \"0\", this is a finding. \n \nIf this is an unclassified system, review the server documentation to determine whether CEIP participation is authorized. \n \nIf CEIP participation is not authorized, and any of the above values are \"1\", this is a finding.","fixText":"To disable participation in the CEIP program, change the value of the following registry keys to \"0\". \n \nTo enable participation in the CEIP program, change the value of the following registry keys to \"1\". \n \nHKEY_LOCAL_MACHINE\\Software\\Microsoft\\Microsoft SQL Server\\[InstanceId]\\CPE\\CustomerFeedback \nHKEY_LOCAL_MACHINE\\Software\\Microsoft\\Microsoft SQL Server\\[InstanceId]\\CPE\\EnableErrorReporting \nHKEY_LOCAL_MACHINE\\Software\\Microsoft\\Microsoft SQL Server\\160\\CustomerFeedback \nHKEY_LOCAL_MACHINE\\Software\\Microsoft\\Microsoft SQL Server\\160\\EnableErrorReporting\n\nOr in PowerShell, run:\n\nSet-ItemProperty -Path \"HKLM:\\Software\\Microsoft\\Microsoft SQL Server\\[InstanceId]\\CPE\" -Name CustomerFeedback -Value 0\nSet-ItemProperty -Path \"HKLM:\\Software\\Microsoft\\Microsoft SQL Server\\[InstanceId]\\CPE\" -Name EnableErrorReporting -Value 0\nSet-ItemProperty -Path \"HKLM:\\Software\\Microsoft\\Microsoft SQL Server\\160\" -Name CustomerFeedback -Value 0\nSet-ItemProperty -Path \"HKLM:\\Software\\Microsoft\\Microsoft SQL Server\\160\" -Name EnableErrorReporting -Value 0","ccis":["CCI-000366"]},{"vulnId":"V-271400","ruleId":"SV-271400r1167497_rule","severity":"medium","ruleTitle":"SQL Server must, for password-based authentication, require immediate selection of a new password upon account recovery.","description":"Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords or passphrases are preferable over shorter passwords. Enforced composition rules provide marginal security benefits while decreasing usability. However, organizations may choose to establish certain rules for password generation (e.g., minimum character length for long passwords) under certain circumstances and can enforce this requirement in IA-5(1)(h). Account recovery can occur, for example, in situations when a password is forgotten. Cryptographically protected passwords include salted one-way cryptographic hashes of passwords. The list of commonly used, compromised, or expected passwords includes passwords obtained from previous breach corpuses, dictionary words, and repetitive or sequential characters. The list includes context-specific words, such as the name of the service, username, and derivatives thereof.","checkContent":"Check for use of SQL Server Authentication:\n\nSELECT CASE SERVERPROPERTY('IsIntegratedSecurityOnly') WHEN 1 THEN 'Windows Authentication' WHEN 0 THEN 'SQL Server Authentication' END as [Authentication Mode]\n\nIf the returned value in the \"Authentication Mode\" column is \"Windows Authentication\", this is not a finding.\n\nIf the returned value is not \"Windows Authentication\", verify SQL Server is configured to require immediate selection of a new password upon account recovery.\n\nAll scripts, functions, triggers, and stored procedures used to create a user or reset a user's password for SQL logins should include a line similar to the following password_option:\n\nMUST_CHANGE\n\nExample:\nCREATE LOGIN STIG_test WITH PASSWORD ='Password' MUST_CHANGE, \n CHECK_EXPIRATION = ON,\n CHECK_POLICY = ON;\n\nIf they do not, this is a finding.\n\nIf SQL Server is not configured to require immediate selection of a new password upon account recovery for accounts using SQL login, this is a finding.","fixText":"Configure the DBMS to require immediate selection of a new password for accounts using SQL login upon account recovery.\n\nEnsure all scripts, functions, triggers, and stored procedures used to create a user or reset a user's password for SQL logins include a line similar to the following password_option:\n\nMUST_CHANGE\n\nIf MUST_CHANGE is specified, CHECK_EXPIRATION and CHECK_POLICY must be set to ON. Otherwise, the statement will fail.\n\nMore information can be found at https://learn.microsoft.com/en-us/sql/t-sql/statements/alter-login-transact-sql?view=sql-server-ver16.","ccis":["CCI-004063"]},{"vulnId":"V-274444","ruleId":"SV-274444r1137654_rule","severity":"medium","ruleTitle":"The SQL Server default account [sa] must be disabled.","description":"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. \n\nThis [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. \n\nSome applications that run on SQL Server require the [sa] account to be enabled for the application to function properly. These applications that require the [sa] account to be enabled are usually legacy systems.","checkContent":"Check SQL Server settings to determine if the [sa] (system administrator) account has been disabled by executing the following query: \nUSE master;\nGO\nSELECT name, is_disabled\nFROM sys.sql_logins\nWHERE principal_id = 1;\nGO\n\nVerify that the \"name\" column contains the current name of the [sa] database server account.\n\nIf the \"is_disabled\" column is not set to \"1\", this is a finding.","fixText":"Modify the enabled flag of SQL Server's [sa] (system administrator) account by running the following script:\nUSE master; \nGO \nALTER LOGIN [sa] DISABLE; \nGO","ccis":["CCI-000213"]},{"vulnId":"V-274445","ruleId":"SV-274445r1111103_rule","severity":"medium","ruleTitle":"The SQL Server default account [sa] must have its name changed.","description":"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. \n\nSince 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.","checkContent":"Verify the SQL Server default [sa] (system administrator) account name has been changed by executing the following query:\nUSE master; \nGO \nSELECT * \nFROM sys.sql_logins \nWHERE [name] = 'sa' OR [principal_id] = 1; \nGO \n\nIf the login account name \"SA\" or \"sa\" appears in the query output, this is a finding.","fixText":"Modify the SQL Server's [sa] (system administrator) account by running the following script:\n\nUSE master; \nGO \nALTER LOGIN [sa] WITH NAME = \nGO","ccis":["CCI-000381"]},{"vulnId":"V-274446","ruleId":"SV-274446r1111106_rule","severity":"medium","ruleTitle":"Execution of startup stored procedures must be restricted to necessary cases only.","description":"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.\n\nWhen \"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.","checkContent":"Review the system documentation to obtain a listing of documented stored procedures used by SQL Server during startup. Execute the following query:\nSelect [name] as StoredProc\nFrom sys.procedures\nWhere OBJECTPROPERTY(OBJECT_ID, 'ExecIsStartup') = 1\n\nIf any stored procedures are returned that are not documented, this is a finding.","fixText":"To disable startup stored procedure(s), run the following in Master for each undocumented procedure:\nsp_procoption @procname = '', @OptionName = 'Startup', @optionValue = 'Off'","ccis":["CCI-002233"]},{"vulnId":"V-274447","ruleId":"SV-274447r1111109_rule","severity":"medium","ruleTitle":"The SQL Server Mirroring endpoint must use AES encryption.","description":"Information can be 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.\n\nUse 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. \n\nSQL Mirroring endpoints support different encryption algorithms, including no-encryption. Using a weak encryption algorithm or plaintext in communication protocols can lead to data loss, data manipulation, and/or connection hijacking.","checkContent":"If the data owner does not have a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process, and the requirement is documented and authorized, this is not a finding.\n\nIf Database Mirroring is in use, run the following to check for encrypted transmissions:\nSELECT name, type_desc, encryption_algorithm_desc\nFROM sys.database_mirroring_endpoints\nWHERE encryption_algorithm != 2\n\nIf any records are returned, this is a finding.","fixText":"Run the following to enable encryption on the mirroring endpoint:\nALTER ENDPOINT \nFOR DATABASE_MIRRORING\n(ENCRYPTION = REQUIRED ALGORITHM AES)","ccis":["CCI-000366"]},{"vulnId":"V-274448","ruleId":"SV-274448r1111112_rule","severity":"medium","ruleTitle":"The SQL Server Service Broker endpoint must use AES encryption.","description":"Information can be 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.\n\nUse of this requirement will be limited to situations where the data owner has a strict requirement for ensuring that data integrity and confidentiality is maintained at every step of the data transfer and handling process. \n\nSQL Server Service Broker endpoints support different encryption algorithms, including no-encryption. Using a weak encryption algorithm or plaintext in communication protocols can lead to data loss, data manipulation, and/or connection hijacking.","checkContent":"If the data owner does not have a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process, and the requirement is documented and authorized, this is not a finding.\n\nIf SQL Service Broker is in use, run the following to check for encrypted transmissions:\nSELECT name, type_desc, encryption_algorithm_desc\nFROM sys.service_broker_endpoints\nWHERE encryption_algorithm != 2\n\nIf any records are returned, this is a finding.","fixText":"Run the following to enable encryption on the Service Broker endpoint:\nALTER ENDPOINT \nFOR SERVICE_BROKER\n(ENCRYPTION = REQUIRED ALGORITHM AES)","ccis":["CCI-000366"]},{"vulnId":"V-274449","ruleId":"SV-274449r1111115_rule","severity":"medium","ruleTitle":"SQL Server execute permissions to access the registry must be revoked unless specifically required and approved.","description":"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). \n\nIt is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. \n\nApplications must adhere to the principles of least functionality by providing only essential capabilities.\n\nSQL 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 operating system security context than SQL Server and provide unauthorized access to the host system.\n\nThe registry contains sensitive information, including password hashes and clear text passwords. Registry extended stored procedures allow Microsoft SQL Server to access the machine's registry. The sensitivity of these procedures is exacerbated if Microsoft SQL Server is run under the Windows account LocalSystem. LocalSystem can read and write nearly all values in the registry, even those not accessible by the administrator. Unlike the xp_cmdshell extended stored procedure, which runs under a separate context if executed by a login not in the sysadmin role, the registry extended stored procedures always execute under the security context of the MSSQLServer service. Because the sensitive information is stored in the registry, it is essential that access to that information be properly guarded.","checkContent":"To determine if permissions to execute registry extended stored procedures have been revoked from all users (other than dbo), execute the following command:\nSELECT OBJECT_NAME(major_id) AS [Stored Procedure]\n,dpr.NAME AS [Principal]\nFROM sys.database_permissions AS dp\nINNER JOIN sys.database_principals AS dpr ON dp.grantee_principal_id = dpr.principal_id\nWHERE major_id IN (\n OBJECT_ID('xp_regaddmultistring')\n,OBJECT_ID('xp_regdeletekey')\n,OBJECT_ID('xp_regdeletevalue')\n,OBJECT_ID('xp_regenumvalues')\n,OBJECT_ID('xp_regenumkeys')\n,OBJECT_ID('xp_regremovemultistring')\n,OBJECT_ID('xp_regwrite')\n,OBJECT_ID('xp_instance_regaddmultistring')\n,OBJECT_ID('xp_instance_regdeletekey')\n,OBJECT_ID('xp_instance_regdeletevalue')\n,OBJECT_ID('xp_instance_regenumkeys')\n,OBJECT_ID('xp_instance_regenumvalues')\n,OBJECT_ID('xp_instance_regremovemultistring')\n,OBJECT_ID('xp_instance_regwrite')\n)\nAND dp.[type] = 'EX'\nORDER BY dpr.NAME;\n\nIf any records are returned, review the system documentation to determine if accessing the registry via extended stored procedures is required and authorized. If it is not authorized, this is a finding.","fixText":"Remove execute permissions to any registry extended stored procedure from all users (other than dbo):\nUSE master\nGO\nREVOKE EXECUTE ON [] FROM []\nGO","ccis":["CCI-000381"]},{"vulnId":"V-274450","ruleId":"SV-274450r1111117_rule","severity":"medium","ruleTitle":"Filestream must be disabled unless specifically required and approved.","description":"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). \n\nIt is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. \n\nApplications must adhere to the principles of least functionality by providing only essential capabilities.\n\nThe most significant potential for attacking an instance is through the use of features that expose an external interface or ad hoc execution capability. FILESTREAM integrates the SQL Server Database Engine with an NTFS file system by storing varbinary(max) binary large object (BLOB) data as files on the file system. Transact-SQL statements can insert, update, query, search, and back up FILESTREAM data.","checkContent":"Review the system documentation to determine if FileStream is in use. If in use and authorized, this is not a finding. \n\nIf FileStream is not documented as being authorized, execute the following query:\nEXEC sp_configure 'filestream access level'\n\nIf \"run_value\" is greater than \"0\", this is a finding.\n\nThis rule checks that the Filestream SQL-specific option is disabled.\nSELECT CASE \n WHEN EXISTS (SELECT * \n FROM sys.configurations \n WHERE Name = 'filestream access level' \n AND Cast(value AS INT) = 0) THEN 'No' \n ELSE 'Yes'\n END AS TSQLFileStreamAccess;\n\nIf the above query returns \"Yes\" in the \"FileStreamEnabled\" field, this is a finding.","fixText":"Disable the use of Filestream.\n\n1. Delete all FILESTREAM columns from all tables. ALTER TABLE DROP COLUMN \n2. Disassociate tables from the FILESTREAM filegroups. ALTER TABLE SET (FILESTREAM_ON = 'NULL'\n3. Remove all FILESTREAM data containers. ALTER DATABASE REMOVE FILE \n4. Remove all FILESTREAM filegroups. ALTER DATABASE REMOVE FILEGROUP \n5. Disable FILESTREAM.\nEXEC sp_configure filestream_access_level, 0 \n RECONFIGURE \n6. Restart the SQL Service.","ccis":["CCI-000381"]},{"vulnId":"V-274451","ruleId":"SV-274451r1111120_rule","severity":"medium","ruleTitle":"The Ole Automation Procedures feature must be disabled unless specifically required and approved.","description":"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). \n\nIt is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. \n\nApplications must adhere to the principles of least functionality by providing only essential capabilities.\n\nSQL 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 operating system security context than SQL Server and provide unauthorized access to the host system.\n\nSQL 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 system security.\n\nThe \"Ole Automation Procedures\" option controls whether OLE Automation objects can be instantiated within Transact-SQL batches. These are extended stored procedures that allow SQL Server users to execute functions external to SQL Server in the security context of SQL Server.\n\nThe \"Ole Automation Procedures\" extended stored procedure allows execution of host executables outside the controls of database access permissions. This access may be exploited by malicious users who have compromised the integrity of the SQL Server database process to control the host operating system to perpetrate additional malicious activity.","checkContent":"To determine if the \"Ole Automation Procedures\" option is enabled, execute the following query: \nEXEC SP_CONFIGURE 'show advanced options', '1'; \nRECONFIGURE WITH OVERRIDE; \nEXEC SP_CONFIGURE 'Ole Automation Procedures'; \n\nIf the value of \"config_value\" is \"0\", this is not a finding. \n\nIf 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.","fixText":"Disable use of or remove any external application executable object definitions that are not authorized. To disable the use of \"Ole Automation Procedures\" option, from the query prompt:\nsp_configure 'show advanced options', 1; \nGO \nRECONFIGURE; \nGO \nsp_configure 'Ole Automation Procedures', 0; \nGO \nRECONFIGURE; \nGO","ccis":["CCI-000381"]},{"vulnId":"V-274452","ruleId":"SV-274452r1111123_rule","severity":"medium","ruleTitle":"The SQL Server User Options feature must be disabled unless specifically required and approved.","description":"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 system security.\n\nThe \"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 enables changing the default values of the SET options (if the server's default settings are not appropriate).","checkContent":"To determine if \"User Options\" option is enabled, execute the following query:\nEXEC SP_CONFIGURE 'show advanced options', '1'; \nRECONFIGURE WITH OVERRIDE; \nEXEC SP_CONFIGURE 'user options'; \n\nIf the value of \"config_value\" is \"0\", this is not a finding. \n\nIf 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.","fixText":"Disable use of or remove any external application executable object definitions that are not authorized. To disable the use of the \"User Options\" option, from the query prompt:\nsp_configure 'show advanced options', 1; \nGO \nRECONFIGURE; \nGO \nsp_configure 'user options', 0; \nGO \nRECONFIGURE; \nGO","ccis":["CCI-000381"]}]}