Skip to content

MS SQL Server 2016 Instance Security Technical Implementation Guide

Rules, Groups, and Values defined within the XCCDF Benchmark

  • SQL Server must maintain a separate execution domain for each executing process.

    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 t...
    Rule Medium Severity
  • When updates are applied to SQL Server software, any software components that have been replaced or made unnecessary must be removed.

    Previous versions of DBMS components that are not removed from the information system after updates have been installed may be exploited by adversaries. Some DBMSs' installation tools may remov...
    Rule Medium Severity
  • 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).

    Security flaws with software applications, including database management systems, are discovered daily. Vendors are constantly updating and patching their products to address newly discovered secur...
    Rule Medium Severity
  • SQL Server must be able to generate audit records when successful and unsuccessful attempts to access security objects occur.

    Changes to the security configuration must be tracked. This requirement applies to situations where security data is retrieved or modified via data manipulation operations, as opposed to via spec...
    Rule Medium Severity
  • SQL Server must generate audit records when successful and unsuccessful attempts to add privileges/permissions occur.

    Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restriction of privileges could go undetected. Elevat...
    Rule Medium Severity
  • SQL Server must generate audit records when successful and unsuccessful attempts to modify privileges/permissions occur.

    Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restriction of privileges could go undetected. Elevat...
    Rule Medium Severity
  • SQL Server must generate audit records when successful and unsuccessful attempts to delete privileges/permissions occur.

    Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restriction of privileges could go undetected. Elevat...
    Rule Medium Severity
  • SQL Server must generate audit records when successful and unsuccessful attempts to delete categorized information (e.g., classification levels/security levels) occur.

    Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. To aid in diagnosis, it is necessary to keep track of faile...
    Rule Medium Severity
  • SQL Server must generate audit records for all privileged activities or other system-level access.

    Without tracking privileged activity, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. System documentati...
    Rule Medium Severity
  • SQL Server must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur.

    Without tracking privileged activity, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. System documentati...
    Rule Medium Severity

The content of the drawer really is up to you. It could have form fields, definition lists, text lists, labels, charts, progress bars, etc. Spacing recommendation is 24px margins. You can put tabs in here, and can also make the drawer scrollable.

Capacity
Modules