| V-255339 | High | Azure SQL Database must protect the confidentiality and integrity of all information at rest. | 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... |
| V-255320 | High | Azure SQL Database must use NSA-approved cryptography to protect classified information in accordance with the data owners requirements. | Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards... |
| V-255301 | High | Azure SQL Databases must integrate with Azure Active Directory for providing account management and automation for all users, groups, roles, and any other principals. | 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... |
| V-255302 | High | Azure SQL Database must enforce approved authorizations for logical access to database information and system resources in accordance with applicable access control policies. | 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... |
| V-255303 | High | Azure SQL Database must enforce approved authorizations for logical access to server information and system resources in accordance with applicable access control policies. | Authentication with a DOD-approved PKI certificate does not necessarily imply authorization to access Azure SQL Database. To mitigate the risk of unauthorized access to sensitive information by... |
| V-255340 | Medium | Azure SQL Database must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect. | This addresses the termination of user-initiated logical sessions in contrast to the termination of network connections that are associated with communications sessions (i.e., network disconnect).... |
| V-255341 | Medium | Azure SQL Database must prevent nonprivileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures. | Preventing nonprivileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges.
System... |
| V-255342 | Medium | Azure SQL Database must utilize centralized management of the content captured in audit records generated by all components of the DBMS. | Without the ability to centrally manage the content captured in the audit records, identification, troubleshooting, and correlation of suspicious behavior would be difficult and could lead to a... |
| V-255343 | Medium | Azure SQL Database must be able to allocate audit record storage capacity in accordance with organization-defined audit record storage requirements. | To ensure sufficient storage capacity for the audit logs, the Azure SQL Database must be able to allocate audit record storage capacity. Although another requirement (SRG-APP-000515-DB-000318)... |
| V-255344 | Medium | Azure SQL Database must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75 percent of maximum audit record storage capacity. | Auditing for Azure SQL Database tracks database events and writes them to an audit log in the Azure storage account, Log Analytics workspace, or Event Hubs.
Under normal conditions, the audit... |
| V-255345 | Medium | 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... |
| V-255346 | Medium | 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. |
| V-255347 | Medium | Azure SQL Database must only use approved firewall settings deemed by the organization to be secure, including denying azure services access to the server. | Use of nonsecure firewall settings, such as allowing azure services to access the server, exposes the system to avoidable threats. |
| V-255348 | Medium | Azure SQL Database must maintain the confidentiality and integrity of information during preparation for transmission. | Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, including, for example, during aggregation, at protocol transformation points,... |
| V-255349 | Medium | 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... |
| V-255308 | Medium | The Azure SQL Database must isolate security functions from nonsecurity functions. | 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,... |
| V-255364 | Medium | 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. |
| V-255368 | Medium | 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. |
| V-255369 | Medium | 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... |
| V-255365 | Medium | Azure SQL Database must generate audit records when unsuccessful attempts to delete security objects occur. | The removal of security objects from the database/DBMS would seriously degrade a system's information assurance posture. If such an action is attempted, it must be logged.
To aid in diagnosis,... |
| V-255362 | Medium | 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.... |
| V-255329 | Medium | Azure SQL Database must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject. | 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... |
| V-255307 | Medium | The role(s)/group(s) used to modify database structure (including but not necessarily limited to tables, indexes, storage, etc.) and logic modules (stored procedures, functions, triggers, links to software external to Azure SQL Database, etc.) must be restricted to authorized users. | If the Azure SQL Database were to allow any user to make changes to database structure or logic, then those changes might be implemented without undergoing the appropriate testing and approvals... |
| V-255363 | Medium | 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... |
| V-255367 | Medium | 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... |
| V-255322 | Medium | Azure SQL Database must implement cryptographic mechanisms preventing the unauthorized disclosure of organization-defined information at rest on organization-defined information system components. | Azure SQL Databases handling data requiring "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.
... |
| V-255360 | Medium | 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... |
| V-255371 | Medium | Azure SQL Database must generate audit records for all unsuccessful attempts to execute 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... |
| V-255361 | Medium | Azure SQL Database must generate audit records when unsuccessful attempts to modify categorized information (e.g., classification levels/security levels) occur. | Changes in categories of information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected.
To aid in diagnosis, it is necessary to keep track of... |
| V-255306 | Medium | Database objects (including but not limited to tables, indexes, storage, stored procedures, functions, triggers, links to software external to Azure SQL Database, etc.) must be owned by database/Azure SQL Database principals authorized for ownership. | Within the database, object ownership implies full privileges to the owned object, including the privilege to assign access to the owned objects to other subjects. Database functions and... |
| V-255335 | Medium | Azure SQL Database must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users). | To ensure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.
Organizational... |
| V-255334 | Medium | The Azure SQL Database must be configured to prohibit or restrict the use of organization-defined functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments. | 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... |
| V-255337 | Medium | Azure SQL Database must uniquely identify and authenticate nonorganizational users (or processes acting on behalf of nonorganizational users). | Nonorganizational users include all information system users other than organizational users, which include organizational employees or individuals the organization deems to have equivalent status... |
| V-255336 | Medium | Azure SQL Database must map the PKI-authenticated identity to an associated user account. | The DOD standard for authentication is DOD-approved PKI certificates. Once a PKI certificate has been validated, it must be mapped to an Azure SQL Database user account for the authenticated... |
| V-255331 | Medium | The audit information produced by Azure SQL Database must be protected from unauthorized modification. | If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is difficult, if not impossible, to achieve. In... |
| V-255330 | Medium | The audit information produced by Azure SQL Database must be protected from unauthorized read access. | If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is difficult, if not impossible, to achieve. In... |
| V-255319 | Medium | Azure SQL Database must enforce access restrictions associated with changes to the configuration of the Azure SQL Database server or database(s). | Failure to provide logical access restrictions associated with changes to configuration may have significant effects on the overall security of the system.
When dealing with access restrictions... |
| V-255318 | Medium | Azure SQL Database must prohibit user installation of logic modules (stored procedures, functions, triggers, views, etc.) without explicit privileged status. | Allowing regular users to install software, without explicit privileges, creates the risk that untested or potentially malicious software will be installed on the system. Explicit privileges... |
| V-255317 | Medium | Azure SQL Database must restrict execution of stored procedures and functions that utilize [execute as] to necessary cases only. | 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... |
| V-255316 | Medium | Azure SQL Database must enforce discretionary access control policies, as defined by the data owner, over defined subjects and objects. | Discretionary Access Control (DAC) is based on the notion that individual users are "owners" of objects and therefore have discretion over who should be authorized to access the object and in... |
| V-255373 | Medium | 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... |
| V-255372 | Medium | 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... |
| V-255313 | Medium | Azure SQL Database must associate organization-defined types of security labels having organization-defined security label values with information in storage. | Without the association of security labels to information, there is no basis for Azure SQL Database to make security-related access-control decisions.
Security labels are abstractions... |
| V-255312 | Medium | The Azure SQL Database and associated applications, when making use of dynamic code execution, must scan input data for invalid values that may indicate a code injection attack. | 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... |
| V-255311 | Medium | The Azure SQL Database and associated applications must reserve the use of dynamic code execution for situations that require it. | 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... |
| V-255376 | Medium | 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... |
| V-255353 | Medium | Azure SQL DB must generate audit records when unsuccessful attempts to access 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... |
| V-255352 | Medium | 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... |
| V-255351 | Medium | 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... |
| V-255350 | Medium | 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... |
| V-255357 | Medium | 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... |
| V-255356 | Medium | 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.... |
| V-255355 | Medium | 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... |
| V-255354 | Medium | 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.... |
| V-255359 | Medium | Azure SQL DB must generate audit records when unsuccessful attempts to modify security objects occur. | 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... |
| V-255358 | Medium | 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... |
| V-255366 | Medium | Azure SQL Database must generate audit records when categories of information (e.g., classification levels/security levels) are deleted. | 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... |
| V-255332 | Medium | The audit information produced by Azure SQL Database must be protected from unauthorized deletion. | If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.
To ensure the... |
| V-255333 | Medium | Azure SQL Database default demonstration and sample databases, database objects, and applications must be removed. | 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... |
| V-255370 | Medium | Azure SQL Database 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... |
| V-255377 | Medium | Azure SQL Database must offload 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. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Offloading is a common process in information systems with limited audit storage capacity.... |
| V-255315 | Medium | Azure SQL Database must associate organization-defined types of security labels having organization-defined security label values with information in transmission. | Without the association of security labels to information, there is no basis for Azure SQL Database to make security-related access-control decisions.
Security labels are abstractions... |
| V-255309 | Medium | Azure SQL Database contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy. | Applications, including DBMSs, must prevent unauthorized and unintended information transfer via shared system resources.
Data used for the development and testing of applications often involves... |
| V-255314 | Medium | Azure SQL Database must associate organization-defined types of security labels having organization-defined security label values with information in process. | Without the association of security labels to information, there is no basis for Azure SQL Database to make security-related access-control decisions.
Security labels are abstractions... |
| V-255375 | Medium | Azure SQL Database must generate audit records when unsuccessful 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... |
| V-255374 | Medium | 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... |
| V-255338 | Medium | Azure SQL Database must separate user functionality (including user interface services) from database management functionality. | Information system management functionality includes functions necessary to administer databases, network components, workstations, or servers and typically requires privileged user access.
The... |
| V-255323 | Medium | When invalid inputs are received, the Azure SQL Database must behave in a predictable and documented manner that reflects organizational and system objectives. | 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... |
| V-255321 | Medium | Azure SQL Database must implement cryptographic mechanisms to prevent unauthorized modification of organization-defined information at rest (to include, at a minimum, PII and classified information) on organization-defined information system components. | Azure SQL Databases handling data requiring "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at... |
| V-255326 | Medium | The Azure SQL Database must be able to generate audit records when privileges/permissions are retrieved. | Under some circumstances, it may be useful to monitor who/what is reading privilege/permission/role information. Therefore, it must be possible to configure auditing to do this. DBMSs typically... |
| V-255327 | Medium | The Azure SQL Database must be able to generate audit records when unsuccessful attempts to retrieve privileges/permissions occur. | Under some circumstances, it may be useful to monitor who/what is reading privilege/permission/role information. Therefore, it must be possible to configure auditing to do this. DBMSs typically... |
| V-255324 | Medium | The Azure SQL Database must be configured to generate audit records for DOD-defined auditable events within all DBMS/database components. | Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit... |
| V-255325 | Medium | Azure SQL Database must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited. | 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.... |
| V-255304 | Medium | Azure SQL Database must protect against a user falsely repudiating by ensuring only clearly unique Active Directory user accounts can connect to the database. | Nonrepudiation of actions taken is required in order to maintain data integrity. Examples of particular actions taken by individuals include creating information, sending a message, approving... |
| V-255305 | Medium | Azure SQL Database must protect against a user falsely repudiating by use of system-versioned tables (Temporal Tables). | Nonrepudiation of actions taken is required in order to maintain data integrity. Examples of particular actions taken by individuals include creating information, sending a message, approving... |
| V-255328 | Medium | Azure SQL Database must initiate session auditing upon startup. | Session auditing is for use when a user's activities are under investigation. To ensure capture of all activity during those periods when session auditing is in use, it needs to be in operation... |
| V-255310 | Medium | Azure SQL Database must check the validity of all data inputs except those specifically identified by the organization. | Invalid user input occurs when a user inserts data or characters into an application's data entry fields and the application is unprepared to process that data. This results in unanticipated... |
