Microsoft Azure SQL Database Security Technical Implementation Guide
Rules, Groups, and Values defined within the XCCDF Benchmark
-
SRG-APP-000381-DB-000361
Group -
Azure SQL Database must produce audit records of its enforcement of access restrictions associated with changes to the configuration of Azure SQL Database(s).
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 ...Rule Medium Severity -
SRG-APP-000383-DB-000364
Group -
Azure SQL Database must only use approved firewall settings deemed by the organization to be secure, including denying public network access.
Use of nonsecure firewall settings, such as allowing public access, exposes the system to avoidable threats.Rule Medium Severity -
SRG-APP-000383-DB-000364
Group -
SRG-APP-000442-DB-000379
Group -
Azure SQL Database must maintain the confidentiality and integrity of information during reception.
Information can be either unintentionally or maliciously disclosed or modified during reception, including, for example, during aggregation, at protocol transformation points, and during packing/un...Rule Medium Severity -
SRG-APP-000492-DB-000332
Group -
Azure SQL DB must be able to generate audit records when security objects are accessed.
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 -
SRG-APP-000492-DB-000333
Group -
Azure SQL DB must generate audit records when 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 -
SRG-APP-000494-DB-000344
Group -
Azure SQL DB must generate audit records when categorized information (e.g., classification levels/security levels) is accessed.
Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. For detailed information on categorizing information, refer ...Rule Medium Severity -
SRG-APP-000494-DB-000345
Group -
SRG-APP-000495-DB-000326
Group -
Azure SQL DB must generate audit records when privileges/permissions are added.
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 -
SRG-APP-000495-DB-000327
Group -
Azure SQL DB must generate audit records when unsuccessful attempts to add privileges/permissions occur.
Failed attempts to change the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized attempts to elevate or restrict privileges could go...Rule Medium Severity -
SRG-APP-000495-DB-000328
Group -
Azure SQL DB must generate audit records when privileges/permissions are modified.
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 -
SRG-APP-000495-DB-000329
Group -
Azure SQL DB must generate audit records when unsuccessful attempts to modify privileges/permissions occur.
Failed attempts to change the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized attempts to elevate or restrict privileges could go...Rule Medium Severity -
SRG-APP-000496-DB-000334
Group -
Azure SQL Database must generate audit records when security objects are modified.
Changes in the database objects (tables, views, procedures, functions) that record and control permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail,...Rule Medium Severity -
SRG-APP-000498-DB-000346
Group -
Azure SQL Database must generate audit records when categorized information (e.g., classification levels/security levels) is modified.
Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. For detailed information on categorizing information, refer ...Rule Medium Severity -
SRG-APP-000498-DB-000347
Group -
SRG-APP-000499-DB-000330
Group -
Azure SQL Database must generate audit records when privileges/permissions are deleted.
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 -
SRG-APP-000499-DB-000331
Group -
Azure SQL Database must generate audit records when unsuccessful attempts to delete privileges/permissions occur.
Failed attempts to change the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized attempts to elevate or restrict privileges could go...Rule Medium Severity -
SRG-APP-000501-DB-000336
Group -
Azure SQL Database must generate audit records when security objects are deleted.
The removal of security objects from the database/DBMS would seriously degrade a system's information assurance posture. If such an event occurs, it must be logged.Rule Medium Severity -
SRG-APP-000501-DB-000337
Group -
SRG-APP-000502-DB-000349
Group -
Azure SQL Database must generate audit records when unsuccessful attempts to delete categories of 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 failed...Rule Medium Severity -
SRG-APP-000503-DB-000350
Group -
Azure SQL Database must generate audit records when successful logons or connections occur.
For completeness of forensic analysis, it is necessary to track who/what (a user or other principal) logs on to Azure SQL Database.Rule Medium Severity -
SRG-APP-000503-DB-000351
Group -
Azure SQL Database must generate audit records when unsuccessful logons or connection attempts occur.
For completeness of forensic analysis, it is necessary to track failed attempts to log on to Azure SQL Database. While positive identification may not be possible in a case of failed authentication...Rule Medium Severity -
SRG-APP-000504-DB-000354
Group -
SRG-APP-000504-DB-000355
Group -
Azure SQL Database must generate audit records for all direct access to the database(s).
In this context, direct access is any query, command, or call to Azure SQL Database that comes from any source other than the application(s) that it supports. Examples would be the command line or ...Rule Medium Severity -
SRG-APP-000505-DB-000352
Group -
Azure SQL Database must generate audit records when concurrent logons/connections by the same user from different workstations occur.
For completeness of forensic analysis, it is necessary to know how long a user's (or other principal's) connection to the Azure Database lasts. This can be achieved by recording disconnections, in ...Rule Medium Severity -
SRG-APP-000506-DB-000353
Group -
Azure SQL Database must generate audit records when concurrent logons/connections by the same user from different workstations occur.
For completeness of forensic analysis, it is necessary to track who logs on to Azure SQL Database. Concurrent connections by the same user from multiple workstations may be valid use of the system...Rule Medium Severity -
SRG-APP-000507-DB-000356
Group -
Azure SQL Database must be able to generate audit records when successful accesses to objects occur.
Without tracking all or selected types of access to all or selected objects (tables, views, procedures, functions, etc.), it would be difficult to establish, correlate, and investigate the events r...Rule Medium Severity -
SRG-APP-000507-DB-000357
Group
Node 2
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.