Detections
Analytics
SQL6-D0-001900 - SQL Server must isolate security functions from non-security functions.
Information
An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform security functions.Security functions are the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based.
Developers and implementers can increase the assurance in security functions by employing well-defined security policy models; structured, disciplined, and rigorous hardware and software development techniques; and sound system/security engineering principles.
Database Management Systems typically separate security functionality from non-security functionality via separate databases or schemas. Database objects or code implementing security functionality should not be commingled with objects or code implementing application logic. When security and non-security functionality are commingled, users who have access to non-security functionality may be able to access security functionality.
NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.
Solution
Check the server documentation, locate security-related database objects and code in a separate database, schema, table, or other separate security domain from database objects and code implementing application logic.Microsoft SQL Server 2005 introduced the concept of database object schemas. Schemas are analogous to separate namespaces or containers used to store database objects. Security permissions apply to schemas, making them an important tool for separating and protecting database objects based on access rights. Schemas reduce the work required, and improve the flexibility, for security-related administration of a database.
User-schema separation allows for more flexibility in managing database object permissions. A schema is a named container for database objects, which allows the user to group objects into separate namespaces.
Where possible, locate security-related database objects and code in a separate database, schema, or other separate security domain from database objects and code implementing application logic. In all cases, use GRANT, REVOKE, DENY, ALTER ROLE ... ADD MEMBER ... and/or ALTER ROLE .... DROP MEMBER statements to add and remove permissions on server-level and database-level security-related objects to provide effective isolation.
See Also
https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_MS_SQL_Server_2016_Y24M01_STIG.zip
Item Details
Audit Name: DISA STIG SQL Server 2016 Database Audit v2r8
Category: SYSTEM AND COMMUNICATIONS PROTECTION
References: 800-53|SC-3, CAT|III, CCI|CCI-001084, Rule-ID|SV-213914r879643_rule, STIG-ID|SQL6-D0-001900, STIG-Legacy|SV-93797, STIG-Legacy|V-79091, Vuln-ID|V-213914
Plugin: MS_SQLDB
Control ID: 834b199f7ea1fcbf0c25b237db7f0a1181ef16098daf36cdc73fc48342a9ae42