Database Security Requirements Guide

Version

SRG-APP-000091-DB-000066

Vuln IDs

V-206525
V-32364

Rule IDs

SV-206525r960885_rule
SV-42701

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 make such information available through views or functions. This requirement addresses explicit requests for privilege/permission/role membership information. It does not refer to the implicit retrieval of privileges/permissions/role memberships that the DBMS continually performs to determine if any and every action on the database is permitted.

Checks: C-6785r291243_chk

Review DBMS documentation to verify that audit records can be produced when privileges/permissions/role memberships are retrieved. If the DBMS is not capable of this, this is a finding. If the DBMS is currently required to audit the retrieval of privilege/permission/role membership information, review the DBMS/database security and audit configurations to verify that audit records are produced when privileges/permissions/role memberships are retrieved. If they are not produced, this is a finding.

Fix: F-6785r291244_fix

Deploy a DBMS capable of producing the required audit records when privileges/permissions/role memberships are retrieved. If currently required, configure the DBMS to produce audit records when privileges/permissions/role memberships are retrieved.

b

The DBMS must be able to generate audit records when unsuccessful attempts to retrieve privileges/permissions occur.

AU-12 - Medium - CCI-000172 - V-206526 - SV-206526r960885_rule

RMF Control

AU-12

Severity

M

CCI

Version

SRG-APP-000091-DB-000325

Vuln IDs

V-206526
V-58069

Rule IDs

SV-206526r960885_rule
SV-72499

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 make such information available through views or functions. This requirement addresses explicit requests for privilege/permission/role membership information. It does not refer to the implicit retrieval of privileges/permissions/role memberships that the DBMS continually performs to determine if any and every action on the database is permitted. To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

Checks: C-6786r291246_chk

Review DBMS documentation to verify that audit records can be produced when the system denies or fails to complete attempts to retrieve privileges/permissions/role membership. If the DBMS is not capable of this, this is a finding. If the DBMS is currently required to audit the retrieval of privilege/permission/role membership information, review the DBMS/database security and audit configurations to verify that audit records are produced when the DBMS denies retrieval of privileges/permissions/role memberships. If they are not produced, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when other errors prevent retrieval of privileges/permissions/role memberships. If they are not produced, this is a finding.

Fix: F-6786r291247_fix

Deploy a DBMS capable of producing the required audit records when it denies or fails to complete access to privileges/permissions/role membership. If currently required, configure the DBMS to produce audit records when it denies access to privileges/permissions/role membership. Configure the DBMS to produce audit records when other errors prevent access to privileges/permissions/role membership.

b

The DBMS must initiate session auditing upon startup.

AU-14 - Medium - CCI-001464 - V-206527 - SV-206527r960888_rule

RMF Control

AU-14

Severity

M

CCI

CCI-001464

Version

SRG-APP-000092-DB-000208

Vuln IDs

V-206527
V-32365

Rule IDs

SV-206527r960888_rule
SV-42702

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 the DBMS is running.

Checks: C-6787r291249_chk

Review DBMS vendor documentation to determine whether the DBMS software is capable of session auditing. If the DBMS is not capable of session auditing and a third party product is not being used for session level auditing, this is a finding. If the DBMS is capable of session level auditing and specific session audits are currently defined but session auditing is not enabled; or if a third-party product is available for session auditing and specific session audits are currently defined but session auditing is not enabled, this is a finding.

Fix: F-6787r291250_fix

Deploy a DBMS capable of session auditing. Configure the DBMS software or third-party product to enable session auditing.

b

The DBMS must produce audit records containing sufficient information to establish what type of events occurred.

AU-3 - Medium - CCI-000130 - V-206528 - SV-206528r960891_rule

RMF Control

AU-3

Severity

M

CCI

CCI-000130

Version

SRG-APP-000095-DB-000039

Vuln IDs

V-206528
V-32368

Rule IDs

SV-206528r960891_rule
SV-42705

Information system auditing capability is critical for accurate forensic analysis. Without establishing what type of event occurred, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit record content that may be necessary to satisfy the requirement of this policy includes, for example, time stamps, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked. Associating event types with detected events in the application and audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured application. Database software is capable of a range of actions on data stored within the database. It is important, for accurate forensic analysis, to know exactly what actions were performed. This requires specific information regarding the event type an audit record is referring to. If event type information is not recorded and stored with the audit record, the record itself is of very limited use.

Checks: C-6788r291252_chk

Check DBMS settings and existing audit records to verify information specific to the audit event type is being captured and stored with the audit records. If audit records exist without information regarding what type of event occurred, this is a finding.

Fix: F-6788r291253_fix

Configure DBMS audit settings to include event type as part of the audit record.

b

The DBMS must produce audit records containing time stamps to establish when the events occurred.

AU-3 - Medium - CCI-000131 - V-206529 - SV-206529r960894_rule

RMF Control

AU-3

Severity

M

CCI

CCI-000131

Version

SRG-APP-000096-DB-000040

Vuln IDs

V-206529
V-32369

Rule IDs

SV-206529r960894_rule
SV-42706

Information system auditing capability is critical for accurate forensic analysis. Without establishing when events occurred, it is impossible to establish, correlate, and investigate the events relating to an incident. In order to compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know the date and time when events occurred. Associating the date and time with detected events in the application and audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured application. Database software is capable of a range of actions on data stored within the database. It is important, for accurate forensic analysis, to know exactly when specific actions were performed. This requires the date and time an audit record is referring to. If date and time information is not recorded and stored with the audit record, the record itself is of very limited use.

Checks: C-6789r291255_chk

Check DBMS settings and existing audit records to verify information specific to the date and time of the event is being captured and stored with the audit records. If audit records exist without the date and time of the event, this is a finding.

Fix: F-6789r291256_fix

Configure DBMS audit settings to include the date and time of the occurrence of the event as part of the audit record.

b

The DBMS must produce audit records containing sufficient information to establish where the events occurred.

AU-3 - Medium - CCI-000132 - V-206530 - SV-206530r960897_rule

RMF Control

AU-3

Severity

M

CCI

CCI-000132

Version

SRG-APP-000097-DB-000041

Vuln IDs

V-206530
V-32370

Rule IDs

SV-206530r960897_rule
SV-42707

Information system auditing capability is critical for accurate forensic analysis. Without establishing where events occurred, it is impossible to establish, correlate, and investigate the events relating to an incident. In order to compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know where events occurred, such as application components, modules, session identifiers, filenames, host names, and functionality. Associating information about where the event occurred within the application provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured application.

Checks: C-6790r291258_chk

Check DBMS settings and existing audit records to verify information specific to where the event occurred is being captured and stored with the audit records. If audit records exist without information regarding where the event occurred, this is a finding.

Fix: F-6790r291259_fix

Configure DBMS audit settings to include where the event occurred as part of the audit record.

b

The DBMS must produce audit records containing sufficient information to establish the sources (origins) of the events.

AU-3 - Medium - CCI-000133 - V-206531 - SV-206531r960900_rule

RMF Control

AU-3

Severity

M

CCI

CCI-000133

Version

SRG-APP-000098-DB-000042

Vuln IDs

V-206531
V-32371

Rule IDs

SV-206531r960900_rule
SV-42708

Information system auditing capability is critical for accurate forensic analysis. Without establishing the source of the event, it is impossible to establish, correlate, and investigate the events relating to an incident. In order to compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know where events occurred, such as application components, modules, session identifiers, filenames, host names, and functionality. In addition to logging where events occur within the application, the application must also produce audit records that identify the application itself as the source of the event. Associating information about the source of the event within the application provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured application.

Checks: C-6791r291261_chk

Check DBMS settings and existing audit records to verify information specific to the source (origin) of the event is being captured and stored with audit records. If audit records exist without information regarding the source of the event, this is a finding.

Fix: F-6791r291262_fix

Configure DBMS audit settings to include the source of the event as part of the audit record.

b

The DBMS must produce audit records containing sufficient information to establish the outcome (success or failure) of the events.

AU-3 - Medium - CCI-000134 - V-206532 - SV-206532r960903_rule

RMF Control

AU-3

Severity

M

CCI

CCI-000134

Version

SRG-APP-000099-DB-000043

Vuln IDs

V-206532
V-32373

Rule IDs

SV-206532r960903_rule
SV-42710

Information system auditing capability is critical for accurate forensic analysis. Without information about the outcome of events, security personnel cannot make an accurate assessment as to whether an attack was successful or if changes were made to the security state of the system. Event outcomes can include indicators of event success or failure and event-specific results (e.g., the security state of the information system after the event occurred). As such, they also provide a means to measure the impact of an event and help authorized personnel to determine the appropriate response.

Checks: C-6792r291264_chk

Check DBMS settings and existing audit records to verify information specific to the outcome of the event is being captured and stored with the audit records. If audit records exist without the outcome of the event that occurred, this is a finding.

Fix: F-6792r291265_fix

Configure DBMS audit settings to include the outcome of the event as part of the audit record.

b

The DBMS must produce audit records containing sufficient information to establish the identity of any user/subject or process associated with the event.

AU-3 - Medium - CCI-001487 - V-206533 - SV-206533r960906_rule

RMF Control

AU-3

Severity

M

CCI

CCI-001487

Version

SRG-APP-000100-DB-000201

Vuln IDs

V-206533
V-32374

Rule IDs

SV-206533r960906_rule
SV-42711

Information system auditing capability is critical for accurate forensic analysis. Without information that establishes the identity of the subjects (i.e., users or processes acting on behalf of users) associated with the events, security personnel cannot determine responsibility for the potentially harmful event. Identifiers (if authenticated or otherwise known) include, but are not limited to, user database tables, primary key values, user names, or process identifiers.

Checks: C-6793r291267_chk

Check DBMS settings and existing audit records to verify a user name associated with the event is being captured and stored with the audit records. If audit records exist without specific user information, this is a finding.

Fix: F-6793r291268_fix

Configure DBMS audit settings to include user name as part of the audit record.

b

The DBMS must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject.

AU-3 - Medium - CCI-000135 - V-206534 - SV-206534r960909_rule

RMF Control

AU-3

Severity

M

CCI

CCI-000135

Version

SRG-APP-000101-DB-000044

Vuln IDs

V-206534
V-32375

Rule IDs

SV-206534r960909_rule
SV-42712

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. The 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. Examples 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.

Checks: C-6794r291270_chk

Review the system documentation to identify what additional information the organization has determined to be necessary. Check DBMS settings and existing audit records to verify that all organization-defined additional, more detailed information is in the audit records for audit events identified by type, location, or subject. If any additional information is defined and is not contained in the audit records, this is a finding.

Fix: F-6794r291271_fix

Configure DBMS audit settings to include all organization-defined detailed information in the audit records for audit events identified by type, location, or subject.

b

The DBMS must by default shut down upon audit failure, to include the unavailability of space for more audit log records; or must be configurable to shut down upon audit failure.

AU-5 - Medium - CCI-000140 - V-206535 - SV-206535r960915_rule

RMF Control

AU-5

Severity

M

CCI

CCI-000140

Version

SRG-APP-000109-DB-000049

Vuln IDs

V-206535
V-32383

Rule IDs

SV-206535r960915_rule
SV-42720

It is critical that when the DBMS is at risk of failing to process audit logs as required, it take action to mitigate the failure. Audit processing failures include: software/hardware errors; failures in the audit capturing mechanisms; and audit storage capacity being reached or exceeded. Responses to audit failure depend upon the nature of the failure mode. When the need for system availability does not outweigh the need for a complete audit trail, the DBMS should shut down immediately, rolling back all in-flight transactions. Systems where audit trail completeness is paramount will most likely be at a lower MAC level than MAC I; the final determination is the prerogative of the application owner, subject to Authorizing Official concurrence. In any case, sufficient auditing resources must be allocated to avoid a shutdown in all but the most extreme situations.

Checks: C-6795r291273_chk

If the application owner has determined that the need for system availability outweighs the need for a complete audit trail, this is not applicable (NA). Review DBMS, OS, or third-party logging application settings and/or documentation to determine whether the system is capable of shutting down, rolling back all in-flight transactions, in the case of an auditing failure. If it is not, this is a finding. If the system is capable of shutting down upon audit failure but is not configured to do so, this is a finding.

Fix: F-6795r291274_fix

Configure the system to shut down, rolling back all in-flight transactions, in the case of an auditing failure.

b

The DBMS must be configurable to overwrite audit log records, oldest first (First-In-First-Out - FIFO), in the event of unavailability of space for more audit log records.

AU-5 - Medium - CCI-000140 - V-206536 - SV-206536r960915_rule

RMF Control

AU-5

Severity

M

CCI

CCI-000140

Version

SRG-APP-000109-DB-000321

Vuln IDs

V-206536
V-58061

Rule IDs

SV-206536r960915_rule
SV-72491

It is critical that when the DBMS is at risk of failing to process audit logs as required, it take action to mitigate the failure. Audit processing failures include: software/hardware errors; failures in the audit capturing mechanisms; and audit storage capacity being reached or exceeded. Responses to audit failure depend upon the nature of the failure mode. When availability is an overriding concern, approved actions in response to an audit failure are as follows: (i) If the failure was caused by the lack of audit record storage capacity, the DBMS must continue generating audit records, if possible (automatically restarting the audit service if necessary), overwriting the oldest audit records in a first-in-first-out manner. (ii) If audit records are sent to a centralized collection server and communication with this server is lost or the server fails, the DBMS must queue audit records locally until communication is restored or until the audit records are retrieved manually. Upon restoration of the connection to the centralized collection server, action should be taken to synchronize the local audit data with the collection server. Systems where availability is paramount will most likely be MAC I; the final determination is the prerogative of the application owner, subject to Authorizing Official concurrence. In any case, sufficient auditing resources must be allocated to avoid audit data loss in all but the most extreme situations.

Checks: C-6796r291276_chk

If the application owner has determined that the need for system availability does not outweigh the need for a complete audit trail, this is not applicable (NA). Review DBMS, OS, or third-party logging application settings and/or documentation to determine whether the system is capable of continuing to generate audit records, overwriting the oldest existing records, in the case of an auditing failure. If it is not, this is a finding. If the system is capable of continuing to generate audit records upon audit failure but is not configured to do so, this is a finding.

Fix: F-6796r291277_fix

Deploy a DBMS capable of continuing to generate audit records upon audit failure. Configure the system to continue to generate audit records, overwriting the oldest existing records, in the case of an auditing failure.

b

The DBMS must use system clocks to generate time stamps for use in audit records and application data.

AU-8 - Medium - CCI-000159 - V-206537 - SV-206537r960927_rule

RMF Control

AU-8

Severity

M

CCI

CCI-000159

Version

SRG-APP-000116-DB-000057

Vuln IDs

V-206537
V-32391

Rule IDs

SV-206537r960927_rule
SV-42728

Internal system clocks are typically a feature of server hardware and are maintained and used by the operating system. They are typically synchronized with an authoritative time server at regular intervals. Without an internal system clock used as the reference for the time stored on each event to provide a trusted common reference for the time, forensic analysis would be impeded. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. Time stamps generated by the internal system clock and used by the DBMS shall include both date and time. The time may be expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC. If time sources other than the system time are used for audit records, the timeline of events can get skewed. This makes forensic analysis of the logs much less reliable.

Checks: C-6797r291279_chk

Using product documentation, verify that the DBMS uses current time stamp values obtained from or synchronized with the internal system clock used by the operating system. If it is not able to, this is a finding. If it is able to but is configured so that it does not do so, this is a finding.

Fix: F-6797r291280_fix

Deploy a DBMS that can use time stamp values obtained from or synchronized with the internal system clock used by the operating system. Configure the DBMS to use time stamp values obtained from or synchronized with the internal system clock used by the operating system.

b

The audit information produced by the DBMS must be protected from unauthorized read access.

AU-9 - Medium - CCI-000162 - V-206538 - SV-206538r960930_rule

RMF Control

AU-9

Severity

M

CCI

CCI-000162

Version

SRG-APP-000118-DB-000059

Vuln IDs

V-206538
V-32393

Rule IDs

SV-206538r960930_rule
SV-42730

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 addition, access to audit records provides information an attacker could potentially use to his or her advantage. To 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. This requirement can be achieved through multiple methods which will depend upon system architecture and design. Some commonly employed methods include ensuring log files enjoy the proper file system permissions utilizing file system protections and limiting log data location. Additionally, 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. Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity.

Checks: C-6798r291282_chk

Review locations of audit logs, both internal to the database and database audit logs located at the operating system level. Verify there are appropriate controls and permissions to protect the audit information from unauthorized access. If appropriate controls and permissions do not exist, this is a finding.

Fix: F-6798r291283_fix

Apply controls and modify permissions to protect database audit log data from unauthorized access, whether stored in the database itself or at the OS level.

b

The audit information produced by the DBMS must be protected from unauthorized modification.

AU-9 - Medium - CCI-000163 - V-206539 - SV-206539r960933_rule

RMF Control

AU-9

Severity

M

CCI

CCI-000163

Version

SRG-APP-000119-DB-000060

Vuln IDs

V-206539
V-32394

Rule IDs

SV-206539r960933_rule
SV-42731

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 veracity of audit data the information system and/or the application must protect audit information from unauthorized modification. This requirement can be achieved through multiple methods that will depend upon system architecture and design. Some commonly employed methods include ensuring log files enjoy the proper file system permissions and limiting log data locations. Applications providing a user interface to audit data will leverage user permissions and roles identifying the user accessing the data and the corresponding rights that the user enjoys in order to make access decisions regarding the modification of audit data. Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity. Modification of database audit data could mask the theft of, or the unauthorized modification of, sensitive data stored in the database.

Checks: C-6799r291285_chk

Review locations of audit logs, both internal to the database and database audit logs located at the operating system level. Verify there are appropriate controls and permissions to protect the audit information from unauthorized modification. If appropriate controls and permissions do not exist, this is a finding.

Fix: F-6799r291286_fix

Apply controls and modify permissions to protect database audit log data from unauthorized modification, whether stored in the database itself or at the OS level.

b

The audit information produced by the DBMS must be protected from unauthorized deletion.

AU-9 - Medium - CCI-000164 - V-206540 - SV-206540r960936_rule

RMF Control

AU-9

Severity

M

CCI

CCI-000164

Version

SRG-APP-000120-DB-000061

Vuln IDs

V-206540
V-32395

Rule IDs

SV-206540r960936_rule
SV-42732

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 veracity of audit data, the information system and/or the application must protect audit information from unauthorized deletion. This requirement can be achieved through multiple methods which will depend upon system architecture and design. Some commonly employed methods include: ensuring log files enjoy the proper file system permissions utilizing file system protections; restricting access; and backing up log data to ensure log data is retained. Applications providing a user interface to audit data will leverage user permissions and roles identifying the user accessing the data and the corresponding rights the user enjoys in order make access decisions regarding the deletion of audit data. Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity. Deletion of database audit data could mask the theft of, or the unauthorized modification of, sensitive data stored in the database.

Checks: C-6800r291288_chk

Review locations of audit logs, both internal to the database, and database audit logs located at the operating system level. Verify there are appropriate controls and permissions to protect the audit information from unauthorized deletion. If appropriate controls and permissions do not exist, this is a finding.

Fix: F-6800r291289_fix

Apply controls and modify permissions to protect database audit log data from unauthorized deletion, whether stored in the database itself or at the OS level.

b

The DBMS must protect its audit features from unauthorized access.

AU-9 - Medium - CCI-001493 - V-206541 - SV-206541r960939_rule

RMF Control

AU-9

Severity

M

CCI

CCI-001493

Version

SRG-APP-000121-DB-000202

Vuln IDs

V-206541
V-32397

Rule IDs

SV-206541r960939_rule
SV-42734

Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Depending upon the log format and application, system and application log tools may provide the only means to manipulate and manage application and system log data. It is, therefore, imperative that access to audit tools be controlled and protected from unauthorized access. Applications 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 access to audit tools. Audit tools include, but are not limited to, OS-provided audit tools, vendor-provided audit tools, and open source audit tools needed to successfully view and manipulate audit information system activity and records. If an attacker were to gain access to audit tools, he 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.

Checks: C-6801r291291_chk

Review the access permissions to tools used to view or modify audit log data. These tools may include features within the DBMS itself or software external to the database. If appropriate permissions and access controls to prevent unauthorized access are not applied to these tools, this is a finding.

Fix: F-6801r291292_fix

Apply or modify access controls and permissions (both within the DBMS and in the file system/operating system) to tools used to view or modify audit log data. Tools must be accessible by authorized personnel only.

b

The DBMS must protect its audit configuration from unauthorized modification.

AU-9 - Medium - CCI-001494 - V-206542 - SV-206542r960942_rule

RMF Control

AU-9

Severity

M

CCI

CCI-001494

Version

SRG-APP-000122-DB-000203

Vuln IDs

V-206542
V-32398

Rule IDs

SV-206542r960942_rule
SV-42735

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. Applications 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. Audit 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.

Checks: C-6802r291294_chk

Review the access permissions to tools used to view or modify audit log data. These tools may include features within the DBMS itself or software external to the database. If appropriate permissions and access controls to prevent unauthorized configuration are not applied to these tools, this is a finding.

Fix: F-6802r291295_fix

Apply or modify access controls and permissions (both within the DBMS and in the file system/operating system) to tools used to view or modify audit log data. Tools must be configurable by authorized personnel only.

b

The DBMS must protect its audit features from unauthorized removal.

AU-9 - Medium - CCI-001495 - V-206543 - SV-206543r960945_rule

RMF Control

AU-9

Severity

M

CCI

CCI-001495

Version

SRG-APP-000123-DB-000204

Vuln IDs

V-206543
V-32399

Rule IDs

SV-206543r960945_rule
SV-42736

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. Applications 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 deletion of audit tools. Audit 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.

Checks: C-6803r291297_chk

Review the access permissions to tools used to view or modify audit log data. These tools may include features within the DBMS itself or software external to the database. If appropriate permissions and access controls to prevent unauthorized removal are not applied to these tools, this is a finding.

Fix: F-6803r291298_fix

Apply or modify access controls and permissions (both within the DBMS and in the file system/operating system) to tools used to view or modify audit log data. Ensure that tools may be removed by authorized personnel only.

b

The DBMS must limit privileges to change software modules, to include stored procedures, functions and triggers, and links to software external to the DBMS.

CM-5 - Medium - CCI-001499 - V-206544 - SV-206544r960960_rule

RMF Control

CM-5

Severity

M

CCI

Version

SRG-APP-000133-DB-000179

Vuln IDs

V-206544
V-32415

Rule IDs

SV-206544r960960_rule
SV-42752

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. Accordingly, only qualified and authorized individuals shall be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications. Unmanaged changes that occur to the database software libraries or configuration can lead to unauthorized or compromised installations.

Checks: C-6804r291300_chk

Review monitoring procedures and implementation evidence to verify monitoring of changes to database software libraries, related applications, and configuration files is done. Verify the list of files, directories, and database application objects (procedures, functions, and triggers) being monitored is complete. If monitoring does not occur or is not complete, this is a finding.

Fix: F-6804r291301_fix

Implement procedures to monitor for unauthorized changes to DBMS software libraries, related software application libraries, and configuration files. If a third-party automated tool is not employed, an automated job that reports file information on the directories and files of interest and compares them to the baseline report for the same will meet the requirement. Use file hashes or checksums for comparisons, as file dates may be manipulated by malicious users.

c

The DBMS software installation account must be restricted to authorized users.

CM-5 - High - CCI-001499 - V-206545 - SV-206545r960960_rule

RMF Control

CM-5

Severity

H

CCI

Version

SRG-APP-000133-DB-000198

Vuln IDs

V-206545
V-32414

Rule IDs

SV-206545r960960_rule
SV-42751

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. 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. Accordingly, only qualified and authorized individuals shall be allowed access to information system components for purposes of initiating changes, including upgrades and modifications. DBA and other privileged administrative or application owner accounts are granted privileges that allow actions that can have a great impact on database security and operation. It is especially important to grant privileged access to only those persons who are qualified and authorized to use them.

Checks: C-6805r291303_chk

Review procedures for controlling, granting access to, and tracking use of the DBMS software installation account. If access or use of this account is not restricted to the minimum number of personnel required or if unauthorized access to the account has been granted, this is a finding.

Fix: F-6805r291304_fix

Develop, document, and implement procedures to restrict and track use of the DBMS software installation account.

b

Database software, including DBMS configuration files, must be stored in dedicated directories, or DASD pools, separate from the host OS and other applications.

CM-5 - Medium - CCI-001499 - V-206546 - SV-206546r960960_rule

RMF Control

CM-5

Severity

M

CCI

Version

SRG-APP-000133-DB-000199

Vuln IDs

V-206546
V-32413

Rule IDs

SV-206546r960960_rule
SV-42750

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. Multiple 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.

Checks: C-6806r291306_chk

Review the DBMS software library directory and note other root directories located on the same disk directory or any subdirectories. If any non-DBMS software directories exist on the disk directory, examine or investigate their use. If any of the directories are used by other applications, including third-party applications that use the DBMS, this is a finding. Only applications that are required for the functioning and administration, not use, of the DBMS should be located in the same disk directory as the DBMS software libraries. If other applications are located in the same directory as the DBMS, this is a finding. For databases located on mainframes, confirm that the database and its configuration files are isolated in their own DASD pools. If database software and database configuration files share DASD with other applications, this is a finding.

Fix: F-6806r291307_fix

Install all applications on directories separate from the DBMS software library directory. Relocate any directories or reinstall other application software that currently shares the DBMS software library directory. For mainframe-based databases, locate database software and configuration files in separate DASD pools from other mainframe applications.

b

Database objects (including but not limited to tables, indexes, storage, stored procedures, functions, triggers, links to software external to the DBMS, etc.) must be owned by database/DBMS principals authorized for ownership.

CM-5 - Medium - CCI-001499 - V-206547 - SV-206547r960960_rule

RMF Control

CM-5

Severity

M

CCI

Version

SRG-APP-000133-DB-000200

Vuln IDs

V-206547
V-32412

Rule IDs

SV-206547r960960_rule
SV-42749

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 procedures can be coded using definer's rights. This allows anyone who utilizes the object to perform the actions if they were the owner. If not properly managed, this can lead to privileged actions being taken by unauthorized individuals. Conversely, if critical tables or other objects rely on unauthorized owner accounts, these objects may be lost when an account is removed.

Checks: C-6807r291309_chk

Review system documentation to identify accounts authorized to own database objects. Review accounts that own objects in the database(s). If any database objects are found to be owned by users not authorized to own database objects, this is a finding.

Fix: F-6807r291310_fix

Assign ownership of authorized objects to authorized object owner accounts.

b

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 the DBMS, etc.) must be restricted to authorized users.

CM-5 - Medium - CCI-001499 - V-206548 - SV-206548r960960_rule

RMF Control

CM-5

Severity

M

CCI

Version

SRG-APP-000133-DB-000362

Vuln IDs

V-206548
V-58129

Rule IDs

SV-206548r960960_rule
SV-72559

If the DBMS 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 that are part of a robust change management process. Accordingly, only qualified and authorized individuals shall be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications. Unmanaged changes that occur to the database software libraries or configuration can lead to unauthorized or compromised installations.

Checks: C-6808r291312_chk

Identify the group(s)/role(s) established for DBMS modification. Obtain the list of users in those group(s)/roles. Identify the individuals authorized to modify the DBMS. If unauthorized access to the group(s)/role(s) has been granted, this is a finding.

Fix: F-6808r291313_fix

Revoke unauthorized memberships in the DBMS modification group(s)/role(s).

b

Default demonstration and sample databases, database objects, and applications must be removed.

CM-7 - Medium - CCI-000381 - V-206549 - SV-206549r960963_rule

RMF Control

CM-7

Severity

M

CCI

Version

SRG-APP-000141-DB-000090

Vuln IDs

V-206549
V-32423

Rule IDs

SV-206549r960963_rule
SV-42760

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). It 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. DBMSs must adhere to the principles of least functionality by providing only essential capabilities. Demonstration 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 the DBMS and host system.

Checks: C-6809r291315_chk

Review vendor documentation and vendor websites to identify vendor-provided demonstration or sample databases, database applications, objects, and files. Review the DBMS to determine if any of the demonstration and sample databases, database applications, or files are installed in the database or are included with the DBMS application. If any are present in the database or are included with the DBMS application, this is a finding.

Fix: F-6809r291316_fix

Remove any demonstration and sample databases, database applications, objects, and files from the DBMS.

b

Unused database components, DBMS software, and database objects must be removed.

CM-7 - Medium - CCI-000381 - V-206550 - SV-206550r960963_rule

RMF Control

CM-7

Severity

M

CCI

Version

SRG-APP-000141-DB-000091

Vuln IDs

V-206550
V-32424

Rule IDs

SV-206550r960963_rule
SV-42761

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). It is detrimental for software products to provide, or install by default, functionality exceeding requirements or mission objectives. DBMSs must adhere to the principles of least functionality by providing only essential capabilities.

Checks: C-6810r291318_chk

Review the list of components and features installed with the database. Use the DBMS product installation tool if supported and review the product installation documentation. If unused components or features are installed and are not documented and authorized, this is a finding.

Fix: F-6810r291319_fix

Uninstall unused components or features that are installed and can be uninstalled. Remove any database objects and applications that are installed to support them.

b

Unused database components that are integrated in the DBMS and cannot be uninstalled must be disabled.

CM-7 - Medium - CCI-000381 - V-206551 - SV-206551r960963_rule

RMF Control

CM-7

Severity

M

CCI

Version

SRG-APP-000141-DB-000092

Vuln IDs

V-206551
V-32426

Rule IDs

SV-206551r960963_rule
SV-42763

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). It is detrimental for software products to provide, or install by default, functionality exceeding requirements or mission objectives. DBMSs must adhere to the principles of least functionality by providing only essential capabilities. Unused, unnecessary DBMS components increase the attack vector for the DBMS by introducing additional targets for attack. By minimizing the services and applications installed on the system, the number of potential vulnerabilities is reduced. Components of the system that are unused and cannot be uninstalled must be disabled. The techniques available for disabling components will vary by DBMS product, OS, and the nature of the component and may include DBMS configuration settings, OS service settings, OS file access security, and DBMS user/role permissions.

Checks: C-6811r291321_chk

Review the DBMS for unused components of the system that cannot be uninstalled. If unused components or features are present on the system, can be disabled, and are not disabled, this is a finding.

Fix: F-6811r291322_fix

Disable any unused components or features that cannot be uninstalled.

b

Access to external executables must be disabled or restricted.

CM-7 - Medium - CCI-000381 - V-206552 - SV-206552r960963_rule

RMF Control

CM-7

Severity

M

CCI

Version

SRG-APP-000141-DB-000093

Vuln IDs

V-206552
V-32427

Rule IDs

SV-206552r960963_rule
SV-42764

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). It is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. Applications must adhere to the principles of least functionality by providing only essential capabilities. DBMSs may spawn additional external processes to execute procedures that are defined in the DBMS 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 the DBMS and provide unauthorized access to the host system.

Checks: C-6812r291324_chk

Review the database for definitions of application executable objects stored external to the database. Determine if there are methods to disable use or access, or to remove definitions for external executable objects. Verify each application executable object listed is authorized by the ISSO. If any are not, this is a finding.

Fix: F-6812r291325_fix

Disable use of or remove any external application executable object definitions that are not authorized.

b

The DBMS 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.

CM-7 - Medium - CCI-000382 - V-206553 - SV-206553r960966_rule

RMF Control

CM-7

Severity

M

CCI

CCI-000382

Version

SRG-APP-000142-DB-000094

Vuln IDs

V-206553
V-32428

Rule IDs

SV-206553r960966_rule
SV-42765

In order 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/protocols/services on information systems. Applications 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. To 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, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues. Database Management Systems using ports, protocols, and services deemed unsafe are open to attack through those ports, protocols, and services. This can allow unauthorized access to the database and through the database to other components of the information system.

Checks: C-6813r291327_chk

Review the DBMS settings and local documentation for functions, ports, protocols, and services that are not approved. If any are found, this is a finding.

Fix: F-6813r291328_fix

Disable functions, ports, protocols, and services that are not approved.

b

The DBMS must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).

IA-2 - Medium - CCI-000764 - V-206554 - SV-206554r960969_rule

RMF Control

IA-2

Severity

M

CCI

CCI-000764

Version

SRG-APP-000148-DB-000103

Vuln IDs

V-206554
V-32442

Rule IDs

SV-206554r960969_rule
SV-42779

To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system. Organizational 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: (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 (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.

Checks: C-6814r291330_chk

Review DBMS settings to determine whether organizational users are uniquely identified and authenticated when logging on/connecting to the system. If organizational users are not uniquely identified and authenticated, this is a finding.

Fix: F-6814r291331_fix

Configure DBMS settings to uniquely identify and authenticate all organizational users who log on/connect to the system.

c

If DBMS authentication, using passwords, is employed, the DBMS must enforce the DOD standards for password complexity and lifetime.

High - CCI-004066 - V-206555 - SV-206555r981946_rule

RMF Control

Severity

H

CCI

CCI-004066

Version

SRG-APP-000164-DB-000401

Vuln IDs

V-206555
V-61407

Rule IDs

SV-206555r981946_rule
SV-75897

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 AO-approved. The 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. In 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.

Checks: C-6815r981944_chk

If DBMS authentication, using passwords, is not employed, this is not a finding. If the DBMS is configured to inherit password complexity and lifetime rules from the operating system or access control program, this is not a finding. Review the DBMS settings relating to password complexity. Determine whether the following rules are enforced. If any are not, this is a finding. a. minimum of 15 characters, including at least one of each of the following character sets: - Uppercase. - Lowercase. - Numerics. - Special characters (e.g., ~ ! @ # $ % ^ & * ( ) _ + = - ' [ ] / ? > <). b. Minimum number of characters changed from previous password: 50 percent of the minimum password length; that is, eight. Review the DBMS settings relating to password lifetime. Determine whether the following rules are enforced. If any are not, this is a finding. a. Password lifetime limits for interactive accounts: Minimum 24 hours, maximum 60 days. b. Password lifetime limits for noninteractive accounts: Minimum 24 hours, maximum 365 days. c. Number of password changes before an old one may be reused: Minimum of five.

Fix: F-6815r981945_fix

If the use of passwords is not needed, configure the DBMS to prevent their use if it is capable of this; if it is not, institute policies and procedures to prohibit their use. If the DBMS can inherit password complexity rules from the operating system or access control program, configure it to do so. Otherwise, use DBMS configuration parameters and/or custom code to enforce the following rules for passwords: a. Minimum of 15 characters, including at least one of each of the following character sets: - Uppercase. - Lowercase. - Numerics. - Special characters (e.g., ~ ! @ # $ % ^ & * ( ) _ + = - ' [ ] / ? > <). b. Minimum number of characters changed from previous password: 50 percent of the minimum password length; that is, eight. c. Password lifetime limits for interactive accounts: Minimum 24 hours, maximum 60 days. d. Password lifetime limits for non-interactive accounts: Minimum 24 hours, maximum 365 days. e. Number of password changes before an old one may be reused: Minimum of five.

c

The DBMS must for password-based authentication, store passwords using an approved salted key derivation function, preferably using a keyed hash.

High - CCI-004062 - V-206556 - SV-206556r981949_rule

RMF Control

Severity

H

CCI

CCI-004062

Version

SRG-APP-000171-DB-000074

Vuln IDs

V-206556
V-32468

Rule IDs

SV-206556r981949_rule
SV-42805

The 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. In such cases, database passwords stored in clear text, using reversible encryption, or using unsalted hashes would be vulnerable to unauthorized disclosure. Database passwords must always be in the form of one-way, salted hashes when stored internally or externally to the DBMS.

Checks: C-6816r981947_chk

Review the list of DBMS database objects, database configuration files, associated scripts, and applications defined within and external to the DBMS that access the database. The list should also include files or settings used to configure the operational environment for the DBMS and for interactive DBMS user accounts. Determine whether any DBMS database objects, database configuration files, associated scripts, applications defined within or external to the DBMS that access the database, and DBMS/user environment files/settings contain database passwords. If any do, confirm that DBMS passwords stored internally or externally to the DBMS are hashed using FIPS-approved cryptographic algorithms and include a salt. If any passwords are stored in clear text, this is a finding. If any passwords are stored with reversible encryption, this is a finding. If any passwords are stored using unsalted hashes, this is a finding.

Fix: F-6816r981948_fix

Develop, document, and maintain a list of DBMS database objects, database configuration files, associated scripts, applications defined within or external to the DBMS that access the database, and DBMS/user environment files/settings in the System Security Plan. Record whether they do or do not contain DBMS passwords. If passwords are present, ensure they are correctly hashed using one-way, salted hashing functions, and that the hashes are protected by host system security.

c

If passwords are used for authentication, the DBMS must transmit only encrypted representations of passwords.

IA-5 - High - CCI-000197 - V-206557 - SV-206557r961029_rule

RMF Control

IA-5

Severity

H

CCI

CCI-000197

Version

SRG-APP-000172-DB-000075

Vuln IDs

V-206557
V-32469

Rule IDs

SV-206557r961029_rule
SV-42806

The 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. In such cases, passwords need to be protected at all times, and encryption is the standard method for protecting passwords during transmission. DBMS 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.

Checks: C-6817r291339_chk

Review configuration settings for encrypting passwords in transit across the network. If passwords are not encrypted, this is a finding. If it is determined that passwords are passed unencrypted at any point along the transmission path between the source and destination, this is a finding.

Fix: F-6817r291340_fix

Configure encryption for transmission of passwords across the network. If the database does not provide encryption for logon events natively, employ encryption at the OS or network level. Ensure passwords remain encrypted from source to destination.

b

The DBMS, when utilizing PKI-based authentication, must validate certificates by performing RFC 5280-compliant certification path validation.

IA-5 - Medium - CCI-000185 - V-206558 - SV-206558r961038_rule

RMF Control

IA-5

Severity

M

CCI

CCI-000185

Version

SRG-APP-000175-DB-000067

Vuln IDs

V-206558
V-32475

Rule IDs

SV-206558r961038_rule
SV-42812

The DoD standard for authentication is DoD-approved PKI certificates. A certificate’s certification path is the path from the end entity certificate to a trusted root certification authority (CA). Certification path validation is necessary for a relying party to make an informed decision regarding acceptance of an end entity certificate. Certification path validation includes checks such as certificate issuer trust, time validity and revocation status for each certificate in the certification path. Revocation status information for CA and subject certificates in a certification path is commonly provided via certificate revocation lists (CRLs) or online certificate status protocol (OCSP) responses. Database Management Systems that do not validate certificates by performing RFC 5280-compliant certification path validation are in danger of accepting certificates that are invalid and/or counterfeit. This could allow unauthorized access to the database.

Checks: C-6818r291342_chk

Review DBMS configuration to verify that certificates being accepted by the DBMS are validated by performing RFC 5280-compliant certification path validation. If certificates are not being validated by performing RFC 5280-compliant certification path validation, this is a finding.

Fix: F-6818r291343_fix

Configure the DBMS to validate certificates by performing RFC 5280-compliant certification path validation.

c

The DBMS must enforce authorized access to all PKI private keys stored/utilized by the DBMS.

IA-5 - High - CCI-000186 - V-206559 - SV-206559r961041_rule

RMF Control

IA-5

Severity

H

CCI

CCI-000186

Version

SRG-APP-000176-DB-000068

Vuln IDs

V-206559
V-32476

Rule IDs

SV-206559r961041_rule
SV-42813

The DoD standard for authentication is DoD-approved PKI certificates. PKI certificate-based authentication is performed by requiring the certificate holder to cryptographically prove possession of the corresponding private key. If the private key is stolen, an attacker can use the private key(s) to impersonate the certificate holder. In cases where the DBMS-stored private keys are used to authenticate the DBMS to the system’s clients, loss of the corresponding private keys would allow an attacker to successfully perform undetected man in the middle attacks against the DBMS system and its clients. Both the holder of a digital certificate and the issuing authority must take careful measures to protect the corresponding private key. Private keys should always be generated and protected in FIPS 140-2 or 140-3 validated cryptographic modules. All access to the private key(s) of the DBMS must be restricted to authorized and authenticated users. If unauthorized users have access to one or more of the DBMS's private keys, an attacker could gain access to the key(s) and use them to impersonate the database on the network or otherwise perform unauthorized actions.

Checks: C-6819r836855_chk

Review DBMS configuration to determine whether appropriate access controls exist to protect the DBMS's private key(s). If the DMBS’s private key(s) are not stored in a FIPS 140-2 or 140-3 validated cryptographic module, this is a finding. If access to the DBMS’s private key(s) is not restricted to authenticated and authorized users, this is a finding.

Fix: F-6819r836856_fix

Store all DBMS PKI private keys in a FIPS 140-2 or 140-3 validated cryptographic module. Ensure access to the DBMS PKI private keys is restricted to only authenticated and authorized users.

b

The DBMS must map the PKI-authenticated identity to an associated user account.

IA-5 - Medium - CCI-000187 - V-206560 - SV-206560r961044_rule

RMF Control

IA-5

Severity

M

CCI

CCI-000187

Version

SRG-APP-000177-DB-000069

Vuln IDs

V-206560
V-32478

Rule IDs

SV-206560r961044_rule
SV-42815

The DoD standard for authentication is DoD-approved PKI certificates. Once a PKI certificate has been validated, it must be mapped to a DBMS user account for the authenticated identity to be meaningful to the DBMS and useful for authorization decisions.

Checks: C-6820r291348_chk

Review DBMS configuration to verify DBMS user accounts are being mapped directly to unique identifying information within the validated PKI certificate. If user accounts are not being mapped to authenticated identities, this is a finding.

Fix: F-6820r291349_fix

Configure the DBMS to map the authenticated identity directly to the DBMS user account.

c

The DBMS must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.

IA-6 - High - CCI-000206 - V-206561 - SV-206561r961047_rule

RMF Control

IA-6

Severity

H

CCI

CCI-000206

Version

SRG-APP-000178-DB-000083

Vuln IDs

V-206561
V-32479

Rule IDs

SV-206561r961047_rule
SV-42816

The DoD standard for authentication is DoD-approved PKI certificates. Normally, with PKI authentication, the interaction with the user for authentication will be handled by a software component separate from the DBMS, such as ActivIdentity ActivClient. However, in cases where the DBMS controls the interaction, this requirement applies. To prevent the compromise of authentication information such as passwords and PINs during the authentication process, the feedback from the system must not provide any information that would allow an unauthorized user to compromise the authentication mechanism. Obfuscation of user-provided authentication secrets when typed into the system is a method used in addressing this risk. Displaying asterisks when a user types in a password or a smart card PIN is an example of obscuring feedback of authentication secrets. This calls for review of applications, 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.

Checks: C-6821r291351_chk

If all interaction with the user for purposes of authentication is handled by a software component separate from the DBMS, this is not a finding. If any application, tool or feature associated with the DBMS/database displays any authentication secrets (to include PINs and passwords) during - or after - the authentication process, this is a finding.

Fix: F-6821r291352_fix

Modify and configure each non-compliant application, tool, or feature associated with the DBMS/database so that it does not display authentication secrets.

c

The DBMS must use NIST FIPS 140-2 or 140-3 validated cryptographic modules for cryptographic operations.

IA-7 - High - CCI-000803 - V-206562 - SV-206562r961050_rule

RMF Control

IA-7

Severity

H

CCI

CCI-000803

Version

SRG-APP-000179-DB-000114

Vuln IDs

V-206562
V-32480

Rule IDs

SV-206562r961050_rule
SV-42817

Use of weak or not validated cryptographic algorithms undermines the purposes of utilizing 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 the DBMS. Applications (including DBMSs) utilizing 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. NSA Type-X (where X=1, 2, 3, 4) products are NSA-certified, hardware-based encryption modules. The standard for validating cryptographic modules will transition to the NIST FIPS 140-3 publication. FIPS 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: https://csrc.nist.gov/projects/cryptographic-module-validation-program/validated-modules More information on the FIPS 140-3 transition can be found here: https://csrc.nist.gov/Projects/fips-140-3-transition-effort/

Checks: C-6822r836858_chk

Review DBMS configuration to verify it is using NIST FIPS 140-2 or 140-3 validated cryptographic modules for cryptographic operations. If NIST FIPS 140-2 or 140-3 validated modules are not being used for all cryptographic operations, this is a finding.

Fix: F-6822r836859_fix

Utilize NIST FIPS 140-2 or 140-3 validated cryptographic modules for all cryptographic operations.

b

The DBMS must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).

IA-8 - Medium - CCI-000804 - V-206563 - SV-206563r961053_rule

RMF Control

IA-8

Severity

M

CCI

CCI-000804

Version

SRG-APP-000180-DB-000115

Vuln IDs

V-206563
V-32481

Rule IDs

SV-206563r961053_rule
SV-42818

Non-organizational users include all information system users other than organizational users, which include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors, guest researchers, individuals from allied nations). Non-organizational users shall be uniquely identified and authenticated for all accesses other than those accesses explicitly identified and documented by the organization when related to the use of anonymous access, such as accessing a web server. Accordingly, a risk assessment is used in determining the authentication needs of the organization. Scalability, practicality, and security are simultaneously considered in balancing the need to ensure ease of use for access to federal information and information systems with the need to protect and adequately mitigate risk to organizational operations, organizational assets, individuals, other organizations, and the Nation.

Checks: C-6823r291357_chk

Review DBMS settings to determine whether non-organizational users are uniquely identified and authenticated when logging onto the system. If non-organizational users are not uniquely identified and authenticated, this is a finding.

Fix: F-6823r291358_fix

Configure DBMS settings to uniquely identify and authenticate all non-organizational users who log onto the system.

b

The DBMS must separate user functionality (including user interface services) from database management functionality.

SC-2 - Medium - CCI-001082 - V-206564 - SV-206564r961095_rule

RMF Control

SC-2

Severity

M

CCI

CCI-001082

Version

SRG-APP-000211-DB-000122

Vuln IDs

V-206564
V-32514

Rule IDs

SV-206564r961095_rule
SV-42851

Information system management functionality includes functions necessary to administer databases, network components, workstations, or servers and typically requires privileged user access. The separation of user functionality from information system management functionality is either physical or logical and is accomplished by using different computers, different central processing units, different instances of the operating system, different network addresses, combinations of these methods, or other methods, as appropriate. An example of this type of separation is observed in web administrative interfaces that use separate authentication methods for users of any other information system resources. This may include isolating the administrative interface on a different domain and with additional access controls. If administrative functionality or information regarding DBMS management is presented on an interface available for users, information on DBMS settings may be inadvertently made available to the user.

Checks: C-6824r291360_chk

Check DBMS settings and vendor documentation to verify that administrative functionality is separate from user functionality. If administrator and general user functionality are not separated either physically or logically, this is a finding.

Fix: F-6824r291361_fix

Configure DBMS to separate database administration and general user functionality.

b

The DBMS must invalidate session identifiers upon user logout or other session termination.

SC-23 - Medium - CCI-001185 - V-206565 - SV-206565r961113_rule

RMF Control

SC-23

Severity

M

CCI

CCI-001185

Version

SRG-APP-000220-DB-000149

Vuln IDs

V-206565
V-32523

Rule IDs

SV-206565r961113_rule
SV-42860

Captured sessions can be reused in "replay" attacks. This requirement limits the ability of adversaries to capture and continue to employ previously valid session IDs. This requirement focuses on communications protection for the DBMS session rather than for the network packet. The intent of this control is to establish grounds for confidence at each end of a communications session in the ongoing identity of the other party and in the validity of the information being transmitted. Session IDs are tokens generated by DBMSs to uniquely identify a user's (or process's) session. DBMSs will make access decisions and execute logic based on the session ID. Unique session IDs help to reduce predictability of said identifiers. Unique session IDs address man-in-the-middle attacks, including session hijacking or insertion of false information into a session. If the attacker is unable to identify or guess the session information related to pending application traffic, they will have more difficulty in hijacking the session or otherwise manipulating valid sessions. When a user logs out, or when any other session termination event occurs, the DBMS must terminate the user session(s) to minimize the potential for sessions to be hijacked.

Checks: C-6825r291363_chk

Review DBMS settings and vendor documentation to verify user sessions are terminated, and session identifiers invalidated, upon user logout. If they are not, this is a finding. Review system documentation and organization policy to identify other events that should result in session terminations. If other session termination events are defined, review DBMS settings to verify occurrences of these events would cause session termination, invalidating the session identifiers. If occurrences of defined session terminating events do not cause session terminations, invalidating the session identifiers, this is a finding.

Fix: F-6825r291364_fix

Configure DBMS settings to terminate sessions, invalidating their session identifiers, upon user logout. Configure DBMS settings to terminate sessions, invalidating their session identifiers, upon the occurrence of any organization- or policy-defined session termination event.

b

The DBMS must recognize only system-generated session identifiers.

SC-23 - Medium - CCI-001664 - V-206566 - SV-206566r961116_rule

RMF Control

SC-23

Severity

M

CCI

CCI-001664

Version

SRG-APP-000223-DB-000168

Vuln IDs

V-206566
V-32526

Rule IDs

SV-206566r961116_rule
SV-42863

DBMSs utilize sessions and session identifiers to control application behavior and user access. If an attacker can guess the session identifier or can inject or manually insert session information, the session may be compromised. This requirement focuses on communications protection for the DBMS session rather than for the network packet. The intent of this control is to establish grounds for confidence at each end of a communications session in the ongoing identity of the other party and in the validity of the information being transmitted. The DBMS must recognize only system-generated session identifiers. If an attacker were able to generate a session with a non-system-generated session identifier and have it recognized by the system, the attacker could gain access to the system without passing through access controls designed to limit database sessions to authorized users.

Checks: C-6826r291366_chk

Review DBMS settings and vendor documentation to determine whether the DBMS recognizes session identifiers that are not system-generated. If the DBMS recognizes session identifiers that are not system generated, this is a finding.

Fix: F-6826r291367_fix

Utilize a DBMS product that only recognizes session identifiers that are system-generated.

b

The DBMS must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values.

SC-23 - Medium - CCI-001188 - V-206567 - SV-206567r961119_rule

RMF Control

SC-23

Severity

M

CCI

CCI-001188

Version

SRG-APP-000224-DB-000384

Vuln IDs

V-206567
V-58165

Rule IDs

SV-206567r961119_rule
SV-72595

One class of man-in-the-middle, or session hijacking, attack involves the adversary guessing at valid session identifiers based on patterns in identifiers already known. The preferred technique for thwarting guesses at Session IDs is the generation of unique session identifiers using a FIPS 140-2 or 140-3 approved random number generator. However, it is recognized that available DBMS products do not all implement the preferred technique yet may have other protections against session hijacking. Therefore, other techniques are acceptable, provided they are demonstrated to be effective.

Checks: C-6827r291369_chk

Review DBMS vendor documentation and system behavior (and if necessary, consult vendor representatives) to determine whether the DBMS can provide demonstrably effective protection against man-in-the-middle attacks that guess at session identifier values. If not, this is a finding. Review DBMS settings to determine whether protections against man-in-the-middle attacks that guess at session identifier values are enabled. If they are not, this is a finding.

Fix: F-6827r291370_fix

Utilize a DBMS product that can provide demonstrably effective protection against man-in-the-middle attacks that guess at session identifier values. Configure DBMS settings to enable protections against man-in-the-middle attacks that guess at session identifier values.

b

The DBMS must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.

SC-24 - Medium - CCI-001190 - V-206568 - SV-206568r961122_rule

RMF Control

SC-24

Severity

M

CCI

CCI-001190

Version

SRG-APP-000225-DB-000153

Vuln IDs

V-206568
V-32528

Rule IDs

SV-206568r961122_rule
SV-42865

Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. Failure to a known secure state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the information system or a component of the system. Failure to a known safe state helps prevent systems from failing to a state that may cause loss of data or unauthorized access to system resources. Systems that fail suddenly and with no incorporated failure state planning may leave the hosting system available but with a reduced security protection capability. Preserving information system state data also facilitates system restart and return to the operational mode of the organization with less disruption of mission/business processes. Databases must fail to a known consistent state. Transactions must be successfully completed or rolled back. In general, security mechanisms should be designed so that a failure will follow the same execution path as disallowing the operation. For example, application security methods, such as isAuthorized(), isAuthenticated(), and validate(), should all return false if there is an exception during processing. If security controls can throw exceptions, they must be very clear about exactly what that condition means. Abort refers to stopping a program or function before it has finished naturally. The term abort refers to both requested and unexpected terminations.

Checks: C-6828r291372_chk

Check DBMS settings and vendor documentation to verify the DBMS properly handles transactions in the event of a system failure. If open transactions are not rolled back to a consistent state during system failure, this is a finding. The consistent state must include a security configuration that is at least as restrictive as before the system failure. If this is not guaranteed, this is a finding.

Fix: F-6828r291373_fix

Configure DBMS settings so that, in the event of a system failure, the DBMS will roll back open transactions to a consistent state, to include a security configuration that is at least as restrictive as before the system failure.

b

In the event of a system failure, the DBMS must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes.

SC-24 - Medium - CCI-001665 - V-206569 - SV-206569r961125_rule

RMF Control

SC-24

Severity

M

CCI

CCI-001665

Version

SRG-APP-000226-DB-000147

Vuln IDs

V-206569
V-32529

Rule IDs

SV-206569r961125_rule
SV-42866

Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. Failure to a known secure state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the information system or a component of the system. Preserving information system state information helps to facilitate system restart and return to the operational mode of the organization with less disruption of mission/business processes. Since it is usually not possible to test this capability in a production environment, systems should either be validated in a testing environment or prior to installation. This requirement is usually a function of the design of the IDPS component. Compliance can be verified by acceptance/validation processes or vendor attestation.

Checks: C-6829r291375_chk

Check DBMS settings to determine whether organization-defined system state information is being preserved in the event of a system failure. If organization-defined system state information is not being preserved, this is a finding.

Fix: F-6829r291376_fix

Configure DBMS settings to preserve any organization-defined system state information in the event of a system failure.

c

The DBMS must protect the confidentiality and integrity of all information at rest.

SC-28 - High - CCI-001199 - V-206570 - SV-206570r961128_rule

RMF Control

SC-28

Severity

H

CCI

CCI-001199

Version

SRG-APP-000231-DB-000154

Vuln IDs

V-206570
V-32534

Rule IDs

SV-206570r961128_rule
SV-42871

This control is intended to address the confidentiality and integrity of information at rest in non-mobile 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. User 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. If the confidentiality and integrity of application data is not protected, the data will be open to compromise and unauthorized modification.

Checks: C-6830r291378_chk

If the application owner and Authorizing Official have determined that encryption of data at rest is NOT required, this is not a finding. Review DBMS settings to determine whether controls exist to protect the confidentiality and integrity of data at rest in the database. If controls do not exist or are not enabled, this is a finding.

Fix: F-6830r291379_fix

Apply appropriate controls to protect the confidentiality and integrity of data at rest in the database.

b

The DBMS must isolate security functions from non-security functions.

SC-3 - Medium - CCI-001084 - V-206571 - SV-206571r961131_rule

RMF Control

SC-3

Severity

M

CCI

CCI-001084

Version

SRG-APP-000233-DB-000124

Vuln IDs

V-206571
V-32536

Rule IDs

SV-206571r961131_rule
SV-42873

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.

Checks: C-6831r291381_chk

Check DBMS settings to determine whether objects or code implementing security functionality are located in a separate security domain, such as a separate database or schema created specifically for security functionality. If security-related database objects or code are not kept separate, this is a finding.

Fix: F-6831r291382_fix

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.

b

Database contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy.

SC-4 - Medium - CCI-001090 - V-206572 - SV-206572r961149_rule

RMF Control

SC-4

Severity

M

CCI

CCI-001090

Version

SRG-APP-000243-DB-000128

Vuln IDs

V-206572
V-32547

Rule IDs

SV-206572r961149_rule
SV-42884

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 copying data from production. It is important that specific procedures exist for this process, to include the conditions under which such transfer may take place, where the copies may reside, and the rules for ensuring sensitive data are not exposed. Copies of sensitive data must not be misplaced or left in a temporary location without the proper controls.

Checks: C-6832r291384_chk

Review the procedures for the refreshing of development/test data from production. Review any scripts or code that exists for the movement of production data to development/test systems, or to any other location or for any other purpose. Verify that copies of production data are not left in unprotected locations. If the code that exists for data movement does not comply with the organization-defined data transfer policy and/or fails to remove any copies of production data from unprotected locations, this is a finding.

Fix: F-6832r291385_fix

Modify any code used for moving data from production to development/test systems to comply with the organization-defined data transfer policy, and to ensure copies of production data are not left in unsecured locations.

b

The DBMS must prevent unauthorized and unintended information transfer via shared system resources.

SC-4 - Medium - CCI-001090 - V-206573 - SV-206573r961149_rule

RMF Control

SC-4

Severity

M

CCI

CCI-001090

Version

SRG-APP-000243-DB-000373

Vuln IDs

V-206573
V-58149

Rule IDs

SV-206573r961149_rule
SV-72579

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.

Checks: C-6833r291387_chk

Review the DBMS architecture to find out if and how it protects the private resources of one process or user (such as working memory, temporary tables, uncommitted data) from unauthorized access by another user or process. If it does not effectively do so, this is a finding.

Fix: F-6833r291388_fix

Deploy a DBMS capable of effectively protecting the private resources of one process or user from unauthorized access by another user or process. Configure the DBMS to effectively protect the private resources of one process or user from unauthorized access by another user or process.

b

Access to database files must be limited to relevant processes and to authorized, administrative users.

SC-4 - Medium - CCI-001090 - V-206574 - SV-206574r961149_rule

RMF Control

SC-4

Severity

M

CCI

CCI-001090

Version

SRG-APP-000243-DB-000374

Vuln IDs

V-206574
V-58151

Rule IDs

SV-206574r961149_rule
SV-72581

Applications, including DBMSs, 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.

Checks: C-6834r291390_chk

Review the permissions granted to users by the operating system/file system on the database files, database log files and database backup files. If any user/role who is not an authorized system administrator with a need to know or database administrator with a need to know, or a system account for running DBMS processes, is permitted to read/view any of these files, this is a finding.

Fix: F-6834r291391_fix

Configure the permissions granted by the operating system/file system on the database files, database log files, and database backup files so that only relevant system accounts and authorized system administrators and database administrators with a need to know are permitted to read/view these files.

b

The DBMS must check the validity of all data inputs except those specifically identified by the organization.

SI-10 - Medium - CCI-001310 - V-206575 - SV-206575r961158_rule

RMF Control

SI-10

Severity

M

CCI

CCI-001310

Version

SRG-APP-000251-DB-000160

Vuln IDs

V-206575
V-32555

Rule IDs

SV-206575r961158_rule
SV-42892

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 application behavior, potentially leading to an application or information system compromise. Invalid user input is one of the primary methods employed when attempting to compromise an application. 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. Potentially, the attacker can gain unauthorized access to data, including security settings, and severely corrupt or destroy the database. Even when no such hijacking takes place, invalid input that gets recorded in the database, whether accidental or malicious, reduces the reliability and usability of the system. Available protections include data types, referential constraints, uniqueness constraints, range checking, and application-specific logic. Application-specific logic can be implemented within the database in stored procedures and triggers, where appropriate. This 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.

Checks: C-6835r291393_chk

Review DBMS code (stored procedures, functions, and triggers), application code, settings, column and field definitions, and constraints to determine whether the database is protected against invalid input. If code exists that allows invalid data to be acted upon or input into the database, this is a finding. If column/field definitions do not exist in the database, this is a finding. If columns/fields do not contain constraints and validity checking where required, this is a finding. Where 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. Where 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.

Fix: F-6835r291394_fix

Modify database code to properly validate data before it is put into the database or acted upon by the database. Modify the database to contain column/field definitions for each column/field in the database. Modify the database to contain constraints and validity checking on database columns and tables that require them for data integrity.

b

The DBMS and associated applications must reserve the use of dynamic code execution for situations that require it.

SI-10 - Medium - CCI-001310 - V-206576 - SV-206576r961158_rule

RMF Control

SI-10

Severity

M

CCI

CCI-001310

Version

SRG-APP-000251-DB-000391

Vuln IDs

V-206576
V-58179

Rule IDs

SV-206576r961158_rule
SV-72609

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. The principal protection against code injection is not to use dynamic execution except where it provides necessary functionality that cannot be utilized otherwise. Use strongly typed data items rather than general-purpose strings as input parameters to task-specific, pre-compiled stored procedures and functions (and triggers). This 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.

Checks: C-6836r291396_chk

Review DBMS source code (stored procedures, functions, triggers) and application source code, to identify cases of dynamic code execution. If 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.

Fix: F-6836r291397_fix

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.

b

The DBMS and associated applications, when making use of dynamic code execution, must scan input data for invalid values that may indicate a code injection attack.

SI-10 - Medium - CCI-001310 - V-206577 - SV-206577r961158_rule

RMF Control

SI-10

Severity

M

CCI

CCI-001310

Version

SRG-APP-000251-DB-000392

Vuln IDs

V-206577
V-58181

Rule IDs

SV-206577r961158_rule
SV-72611

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. The principal protection against code injection is not to use dynamic execution except where it provides necessary functionality that cannot be utilized otherwise. Use strongly typed data items rather than general-purpose strings as input parameters to task-specific, pre-compiled stored procedures and functions (and triggers). When 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: -- Allow strings as input only when necessary. -- 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. -- Limit the size of input strings to what is truly necessary. -- If single quotes/apostrophes, double quotes, semicolons, equals signs, angle brackets, or square brackets will never be valid as input, reject them. -- If comment markers will never be valid as input, reject them. In SQL, these are -- or /* */ -- If HTML and XML tags, entities, comments, etc., will never be valid, reject them. -- 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. -- 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. -- If there are range limits on the values that may be entered, enforce those limits. -- Institute procedures for inspection of programs for correct use of dynamic coding, by a party other than the developer. -- Conduct rigorous testing of program modules that use dynamic coding, searching for ways to subvert the intended use. -- Record the inspection and testing in the system documentation. -- 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. This 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.

Checks: C-6837r291399_chk

Review DBMS source code (stored procedures, functions, triggers) and application source code to identify cases of dynamic code execution. If dynamic code execution is employed without protective measures against code injection, this is a finding.

Fix: F-6837r291400_fix

Where dynamic code execution is used, modify the code to implement protections against code injection.

b

The DBMS must provide non-privileged users with error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.

SI-11 - Medium - CCI-001312 - V-206578 - SV-206578r961167_rule

RMF Control

SI-11

Severity

M

CCI

CCI-001312

Version

SRG-APP-000266-DB-000162

Vuln IDs

V-206578
V-32570

Rule IDs

SV-206578r961167_rule
SV-42907

Any DBMS or associated application providing too much information in error messages on the screen or printout risks compromising the data and security of the system. The structure and content of error messages need to be carefully considered by the organization and development team. Databases can inadvertently provide a wealth of information to an attacker through improperly handled error messages. In addition to sensitive business or personal information, database errors can provide host names, IP addresses, user names, and other system information not required for troubleshooting but very useful to someone targeting the system. Carefully consider the structure/content of error messages. The extent to which information systems are able to identify and handle error conditions is guided by organizational policy and operational requirements. Information that could be exploited by adversaries includes, for example, logon attempts with passwords entered by mistake as the username, mission/business information that can be derived from (if not stated explicitly by) information recorded, and personal information, such as account numbers, social security numbers, and credit card numbers. This 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.

Checks: C-6838r291402_chk

Check DBMS settings and custom database code to verify that error messages do not contain information beyond what is needed for troubleshooting the issue. If database errors contain PII data, sensitive business data, or information useful for identifying the host system or database structure, this is a finding.

Fix: F-6838r291403_fix

Configure DBMS settings, custom database code, and associated application code not to divulge sensitive information or information useful for system identification in error messages.

b

The DBMS must reveal detailed error messages only to the ISSO, ISSM, SA and DBA.

SI-11 - Medium - CCI-001314 - V-206579 - SV-206579r961170_rule

RMF Control

SI-11

Severity

M

CCI

CCI-001314

Version

SRG-APP-000267-DB-000163

Vuln IDs

V-206579
V-32571

Rule IDs

SV-206579r961170_rule
SV-42908

If the DBMS 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. Some default DBMS error messages can contain information that could aid an attacker in, among others things, identifying the database type, host address, or state of the database. Custom errors may contain sensitive customer information. It 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. Administrative users authorized to review detailed error messages typically are the ISSO, ISSM, SA, and DBA. Other individuals or roles may be specified according to organization-specific needs, with appropriate approval. This 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.

Checks: C-6839r291405_chk

Check DBMS settings and custom database code to determine if detailed error messages are ever displayed to unauthorized individuals. If detailed error messages are displayed to individuals not authorized to view them, this is a finding.

Fix: F-6839r291406_fix

Configure DBMS settings, custom database code, and associated application code not to display detailed error messages to those not authorized to view them.

b

The DBMS must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.

AC-12 - Medium - CCI-002361 - V-206580 - SV-206580r961221_rule

RMF Control

AC-12

Severity

M

CCI

CCI-002361

Version

SRG-APP-000295-DB-000305

Vuln IDs

V-206580
V-58025

Rule IDs

SV-206580r961221_rule
SV-72455

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). A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational information system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions. Session termination ends all processes associated with a user's logical session except those batch processes/jobs that are specifically created by the user (i.e., session owner) to continue after the session is terminated. Conditions or trigger events requiring automatic session termination can include, for example, organization-defined periods of user inactivity, targeted responses to certain types of incidents, and time-of-day restrictions on information system use. This capability is typically reserved for specific cases where the system owner, data owner, or organization requires additional assurance.

Checks: C-6840r291408_chk

Review system documentation to obtain the organization's definition of circumstances requiring automatic session termination. If the documentation explicitly states that such termination is not required or is prohibited, this is not a finding. If the documentation requires automatic session termination, but the DBMS is not configured accordingly, this is a finding.

Fix: F-6840r291409_fix

Configure the DBMS to automatically terminate a user session after organization-defined conditions or trigger events requiring session termination.

b

The DBMS must provide logout functionality to allow the user to manually terminate a session initiated by that user.

AC-12 - Medium - CCI-002363 - V-206581 - SV-206581r961224_rule

RMF Control

AC-12

Severity

M

CCI

CCI-002363

Version

SRG-APP-000296-DB-000306

Vuln IDs

V-206581
V-58035

Rule IDs

SV-206581r961224_rule
SV-72465

If a user cannot explicitly end a DBMS session, the session may remain open and be exploited by an attacker; this is referred to as a zombie session. Such logout may be explicit or implicit. Examples of explicit are: clicking on a "Log Out" link or button in the application window; clicking the Windows Start button and selecting "Log Out" or "Shut Down." Examples of implicit logout are: closing the application's (main) window; powering off the workstation without invoking the OS shutdown. Both the explicit and implicit logouts must be detected by the DBMS. In all cases, the DBMS must ensure that the user's DBMS session and all processes owned by the session are terminated. This should not, however, interfere with batch processes/jobs initiated by the user during his/her online session: these should be permitted to run to completion.

Checks: C-6841r291411_chk

Determine, by reviewing DBMS documentation and/or inquiring of the vendor's technical support staff, whether the DBMS satisfies this requirement; and, if it does, determine whether this is inherent, unchangeable behavior, or a configurable feature. If the DBMS does not satisfy the requirement, this is a permanent finding. If the behavior is inherent, this is permanently not a finding. If the behavior is configurable, and the current configuration does not enforce it, this is a finding.

Fix: F-6841r291412_fix

Where relevant, modify the configuration to allow the user to manually terminate a session initiated by that user.

b

The DBMS must associate organization-defined types of security labels having organization-defined security label values with information in storage.

AC-16 - Medium - CCI-002262 - V-206582 - SV-206582r961269_rule

RMF Control

AC-16

Severity

M

CCI

CCI-002262

Version

SRG-APP-000311-DB-000308

Vuln IDs

V-206582
V-58037

Rule IDs

SV-206582r961269_rule
SV-72467

Without the association of security labels to information, there is no basis for the DBMS to make security-related access-control decisions. Security labels are abstractions representing the basic properties or characteristics of an entity (e.g., subjects and objects) with respect to safeguarding information. These labels are typically associated with internal data structures (e.g., tables, rows) within the database and are used to enable the implementation of access control and flow control policies, reflect special dissemination, handling or distribution instructions, or support other aspects of the information security policy. One example includes marking data as classified or FOUO. These security labels may be assigned manually or during data processing, but, either way, it is imperative these assignments are maintained while the data is in storage. If the security labels are lost when the data is stored, there is the risk of a data compromise. The mechanism used to support security labeling may be a feature of the DBMS product, a third-party product, or custom application code.

Checks: C-6842r291414_chk

If security labeling is not required, this is not a finding. If security labeling requirements have been specified, but the security labeling is not implemented or does not reliably maintain labels on information in storage, this is a finding.

Fix: F-6842r291415_fix

Enable DBMS features, deploy third-party software, or add custom data structures, data elements and application code, to provide reliable security labeling of information in storage.

b

The DBMS must associate organization-defined types of security labels having organization-defined security label values with information in process.

AC-16 - Medium - CCI-002263 - V-206583 - SV-206583r961272_rule

RMF Control

AC-16

Severity

M

CCI

CCI-002263

Version

SRG-APP-000313-DB-000309

Vuln IDs

V-206583
V-58039

Rule IDs

SV-206583r961272_rule
SV-72469

Without the association of security labels to information, there is no basis for the DBMS to make security-related access-control decisions. Security labels are abstractions representing the basic properties or characteristics of an entity (e.g., subjects and objects) with respect to safeguarding information. These labels are typically associated with internal data structures (e.g., tables, rows) within the database and are used to enable the implementation of access control and flow control policies, reflect special dissemination, handling or distribution instructions, or support other aspects of the information security policy. One example includes marking data as classified or FOUO. These security labels may be assigned manually or during data processing, but, either way, it is imperative these assignments are maintained while the data is in storage. If the security labels are lost when the data is stored, there is the risk of a data compromise. The mechanism used to support security labeling may be a feature of the DBMS product, a third-party product, or custom application code.

Checks: C-6843r291417_chk

If security labeling is not required, this is not a finding. If security labeling requirements have been specified, but the security labeling is not implemented or does not reliably maintain labels on information in process, this is a finding.

Fix: F-6843r291418_fix

Enable DBMS features, deploy third-party software, or add custom data structures, data elements and application code, to provide reliable security labeling of information in process.

b

The DBMS must associate organization-defined types of security labels having organization-defined security label values with information in transmission.

AC-16 - Medium - CCI-002264 - V-206584 - SV-206584r961275_rule

RMF Control

AC-16

Severity

M

CCI

CCI-002264

Version

SRG-APP-000314-DB-000310

Vuln IDs

V-206584
V-58041

Rule IDs

SV-206584r961275_rule
SV-72471

Without the association of security labels to information, there is no basis for the DBMS to make security-related access-control decisions. Security labels are abstractions representing the basic properties or characteristics of an entity (e.g., subjects and objects) with respect to safeguarding information. These labels are typically associated with internal data structures (e.g., tables, rows) within the database and are used to enable the implementation of access control and flow control policies, reflect special dissemination, handling or distribution instructions, or support other aspects of the information security policy. One example includes marking data as classified or FOUO. These security labels may be assigned manually or during data processing, but, either way, it is imperative these assignments are maintained while the data is in storage. If the security labels are lost when the data is stored, there is the risk of a data compromise. The mechanism used to support security labeling may be a feature of the DBMS product, a third-party product, or custom application code.

Checks: C-6844r291420_chk

If security labeling is not required, this is not a finding. If security labeling requirements have been specified, but the security labeling is not implemented or does not reliably maintain labels on information in transmission, this is a finding.

Fix: F-6844r291421_fix

Enable DBMS features, deploy third-party software, or add custom data structures, data elements and application code, to provide reliable security labeling of information in transmission.

b

The DBMS must enforce discretionary access control policies, as defined by the data owner, over defined subjects and objects.

AC-3 - Medium - CCI-002165 - V-206585 - SV-206585r961317_rule

RMF Control

AC-3

Severity

M

CCI

CCI-002165

Version

SRG-APP-000328-DB-000301

Vuln IDs

V-206585
V-58019

Rule IDs

SV-206585r961317_rule
SV-72449

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 which mode (e.g., read or write). Ownership is usually acquired as a consequence of creating the object or via specified ownership assignment. DAC allows the owner to determine who will have access to objects they control. An example of DAC includes user-controlled table permissions. When discretionary access control policies are implemented, subjects are not constrained with regard to what actions they can take with information for which they have already been granted access. Thus, subjects that have been granted access to information are not prevented from passing (i.e., the subjects have the discretion to pass) the information to other subjects or objects. A subject that is constrained in its operation by Mandatory Access Control policies is still able to operate under the less rigorous constraints of this requirement. Thus, while Mandatory Access Control imposes constraints preventing a subject from passing information to another subject operating at a different sensitivity level, this requirement permits the subject to pass the information to any subject at the same sensitivity level. The policy is bounded by the information system boundary. Once the information is passed outside of the control of the information system, additional means may be required to ensure the constraints remain in effect. While the older, more traditional definitions of discretionary access control require identity-based access control, that limitation is not required for this use of discretionary access control.

Checks: C-6845r291423_chk

Review system documentation to identify the required discretionary access control (DAC). Review the security configuration of the database and DBMS. If applicable, review the security configuration of the application(s) using the database. If the discretionary access control defined in the documentation is not implemented in the security configuration, this is a finding.

Fix: F-6845r291424_fix

Implement the organization's DAC policy in the security configuration of the database and DBMS, and, if applicable, the security configuration of the application(s) using the database.

b

The DBMS must prevent non-privileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures.

AC-6 - Medium - CCI-002235 - V-206586 - SV-206586r961353_rule

RMF Control

AC-6

Severity

M

CCI

CCI-002235

Version

SRG-APP-000340-DB-000304

Vuln IDs

V-206586
V-58023

Rule IDs

SV-206586r961353_rule
SV-72453

Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges. System documentation should include a definition of the functionality considered privileged. Depending on circumstances, privileged functions can include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged 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 non-privileged users. A privileged function in the DBMS/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: CREATE ALTER DROP GRANT REVOKE DENY There may also be Data Manipulation Language (DML) statements that, subject to context, should be regarded as privileged. Possible examples include: TRUNCATE TABLE; DELETE, or DELETE affecting more than n rows, for some n, or DELETE without a WHERE clause; UPDATE or UPDATE affecting more than n rows, for some n, or UPDATE without a WHERE clause; any SELECT, INSERT, UPDATE, or DELETE to an application-defined security table executed by other than a security principal. Depending on the capabilities of the DBMS 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.

Checks: C-6846r291426_chk

Review the system documentation to obtain the definition of the database/DBMS functionality considered privileged in the context of the system in question. Review the DBMS security configuration and/or other means used to protect privileged functionality from unauthorized use. If the configuration does not protect all of the actions defined as privileged, this is a finding.

Fix: F-6846r291427_fix

Configure DBMS security to protect all privileged functionality.

b

Execution of software modules (to include stored procedures, functions, and triggers) with elevated privileges must be restricted to necessary cases only.

AC-6 - Medium - CCI-002233 - V-206587 - SV-206587r961359_rule

RMF Control

AC-6

Severity

M

CCI

CCI-002233

Version

SRG-APP-000342-DB-000302

Vuln IDs

V-206587
V-58021

Rule IDs

SV-206587r961359_rule
SV-72451

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. Privilege elevation must be utilized only where necessary and protected from misuse. This 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.

Checks: C-6847r291429_chk

Review the system documentation, database and DBMS security configuration, source code for DBMS internal logic, source code of external modules invoked by the DBMS, and source code of the application(s) using the database. If elevation of DBMS privileges is utilized but not documented, this is a finding. If elevation of DBMS privileges is documented, but not implemented as described in the documentation, this is a finding. If the privilege-elevation logic can be invoked in ways other than intended, or in contexts other than intended, or by subjects/principals other than intended, this is a finding.

Fix: F-6847r291430_fix

Determine where, when, how, and by what principals/subjects elevated privilege is needed. Modify the database and DBMS security configuration, DBMS internal logic, external modules invoked by the DBMS, and the application(s) using the database, to ensure privilege elevation is used only as required.

b

The DBMS must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements.

AU-4 - Medium - CCI-001849 - V-206591 - SV-206591r961392_rule

RMF Control

AU-4

Severity

M

CCI

CCI-001849

Version

SRG-APP-000357-DB-000316

Vuln IDs

V-206591
V-58053

Rule IDs

SV-206591r961392_rule
SV-72483

In order to ensure sufficient storage capacity for the audit logs, the DBMS must be able to allocate audit record storage capacity. Although another requirement (SRG-APP-000515-DB-000318) mandates that audit data be off-loaded to a centralized log management system, it remains necessary to provide space on the database server to serve as a buffer against outages and capacity limits of the off-loading mechanism. The task of allocating audit record storage capacity is usually performed during initial installation of the DBMS and is closely associated with the DBA and system administrator roles. The DBA or system administrator will usually coordinate the allocation of physical drive space with the application owner/installer and the application will prompt the installer to provide the capacity information, the physical location of the disk, or both. In determining the capacity requirements, consider such factors as: total number of users; expected number of concurrent users during busy periods; number and type of events being monitored; types and amounts of data being captured; the frequency/speed with which audit records are off-loaded to the central log management system; and any limitations that exist on the DBMS's ability to reuse the space formerly occupied by off-loaded records.

Checks: C-6851r291441_chk

Investigate whether there have been any incidents where the DBMS ran out of audit log space since the last time the space was allocated or other corrective measures were taken. If there have been, this is a finding.

Fix: F-6851r291442_fix

Allocate sufficient audit file/table space to support peak demand.

b

The DBMS must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75% of maximum audit record storage capacity.

AU-5 - Medium - CCI-001855 - V-206592 - SV-206592r961398_rule

RMF Control

AU-5

Severity

M

CCI

CCI-001855

Version

SRG-APP-000359-DB-000319

Vuln IDs

V-206592
V-58057

Rule IDs

SV-206592r961398_rule
SV-72487

Organizations are required to use a central log management system, so, under normal conditions, the audit space allocated to the DBMS on its own server will not be an issue. However, space will still be required on the DBMS server for 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. If support personnel are not notified immediately upon storage volume utilization reaching 75%, they are unable to plan for storage capacity expansion. The appropriate support staff include, at a minimum, the ISSO and the DBA/SA.

Checks: C-6852r291444_chk

Review system configuration. If appropriate support staff are not notified immediately upon storage volume utilization reaching 75%, this is a finding.

Fix: F-6852r291445_fix

Configure the system to notify appropriate support staff immediately upon storage volume utilization reaching 75%.

b

The DBMS must provide an immediate real-time alert to appropriate support staff of all audit log failures.

AU-5 - Medium - CCI-001858 - V-206593 - SV-206593r961401_rule

RMF Control

AU-5

Severity

M

CCI

CCI-001858

Version

SRG-APP-000360-DB-000320

Vuln IDs

V-206593
V-58059

Rule IDs

SV-206593r961401_rule
SV-72489

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. The appropriate support staff include, at a minimum, the ISSO and the DBA/SA. A 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. Alerts 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).

Checks: C-6853r850970_chk

Review DBMS 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. If real-time alerts are not sent upon auditing failure, this is a finding.

Fix: F-6853r531242_fix

Configure the system to provide immediate real-time alerts to appropriate support staff when an audit log failure occurs.

b

The DBMS must record time stamps, in audit records and application data, that can be mapped to Coordinated Universal Time (UTC, formerly GMT).

AU-8 - Medium - CCI-001890 - V-206594 - SV-206594r961443_rule

RMF Control

AU-8

Severity

M

CCI

CCI-001890

Version

SRG-APP-000374-DB-000322

Vuln IDs

V-206594
V-58063

Rule IDs

SV-206594r961443_rule
SV-72493

If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis. Time stamps generated by the DBMS must include date and time. Time is commonly expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC. Some DBMS products offer a data type called TIMESTAMP that is not a representation of date and time. Rather, it is a database state counter and does not correspond to calendar and clock time. This requirement does not refer to that meaning of TIMESTAMP.

Checks: C-6854r291450_chk

Verify that the DBMS generates time stamps, in audit records and application data, that maps to UTC. If it does not, this is a finding.

Fix: F-6854r291451_fix

Ensure the DBMS generates time stamps, in audit records and application data, that maps to UTC.

b

The DBMS must generate time stamps, for audit records and application data, with a minimum granularity of one second.

AU-8 - Medium - CCI-001889 - V-206595 - SV-206595r961446_rule

RMF Control

AU-8

Severity

M

CCI

CCI-001889

Version

SRG-APP-000375-DB-000323

Vuln IDs

V-206595
V-58065

Rule IDs

SV-206595r961446_rule
SV-72495

Without sufficient granularity of time stamps, it is not possible to adequately determine the chronological order of records. Time stamps generated by the DBMS must include date and time. Granularity of time measurements refers to the precision available in time stamp values. Granularity coarser than one second is not sufficient for audit trail purposes. Time stamp values are typically presented with three or more decimal places of seconds; however, the actual granularity may be coarser than the apparent precision. For example, SQL Server's GETDATE()/CURRENT_TMESTAMP values are presented to three decimal places, but the granularity is not one millisecond: it is about 1/300 of a second. Some DBMS products offer a data type called TIMESTAMP that is not a representation of date and time. Rather, it is a database state counter and does not correspond to calendar and clock time. This requirement does not refer to that meaning of TIMESTAMP.

Checks: C-6855r291453_chk

Review product documentation to verify that the DBMS can generate time stamps with a granularity of one second or finer. If it cannot, this is a finding. Review audit log records produced by the DBMS for confirmation that time stamps are recorded to a precision of one second or finer. If not, this is a finding. Review time stamp values in audit trail columns/fields in application data in the database. If the time stamps are not recorded to a precision of one second or finer, this is a finding.

Fix: F-6855r291454_fix

Deploy a DBMS that can generate and record time stamps with a granularity of one second or finer. Configure auditing so that the time stamps are recorded to a precision of one second or finer. Modify applications and/or column/field definitions so that the time stamps in audit trail columns/fields in application data are recorded to a precision of one second or finer.

b

The DBMS must prohibit user installation of logic modules (stored procedures, functions, triggers, views, etc.) without explicit privileged status.

Medium - CCI-003980 - V-206596 - SV-206596r981956_rule

RMF Control

Severity

M

CCI

CCI-003980

Version

SRG-APP-000378-DB-000365

Vuln IDs

V-206596
V-58135

Rule IDs

SV-206596r981956_rule
SV-72565

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 (escalated or administrative privileges) provide the regular user with explicit capabilities and control that exceed the rights of a regular user. DBMS functionality and the nature and requirements of databases will vary; so while users are not permitted to install unapproved software, there may be instances where the organization allows the user to install approved software packages such as from an approved software repository. The requirements for production servers will be more restrictive than those used for development and research. The DBMS must enforce software installation by users based upon what types of software installations are permitted (e.g., updates and security patches to existing software) and what types of installations are prohibited (e.g., software whose pedigree with regard to being potentially malicious is unknown or suspect) by the organization). In the case of a database management system, this requirement covers stored procedures, functions, triggers, views, etc.

Checks: C-6856r981954_chk

If the DBMS supports only software development, experimentation and/or developer-level testing (that is, excluding production systems, integration testing, stress testing, and user acceptance testing), this is not a finding. Review the DBMS and database security settings with respect to nonadministrative users' ability to create, alter, or replace logic modules, to include but not necessarily only stored procedures, functions, triggers, and views. If any such permissions exist and are not documented and approved, this is a finding.

Fix: F-6856r981955_fix

Document and obtain approval for any nonadministrative users who require the ability to create, alter or replace logic modules. Implement the approved permissions. Revoke any unapproved permissions.

b

The DBMS must enforce access restrictions associated with changes to the configuration of the DBMS or database(s).

CM-5 - Medium - CCI-001813 - V-206597 - SV-206597r961461_rule

RMF Control

CM-5

Severity

M

CCI

CCI-001813

Version

SRG-APP-000380-DB-000360

Vuln IDs

V-206597
V-58125

Rule IDs

SV-206597r961461_rule
SV-72555

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 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. Accordingly, only qualified and authorized individuals should be allowed to obtain access to system components for the purposes of initiating changes, including upgrades and modifications.

Checks: C-6857r291459_chk

Review DBMS vendor documentation with respect to its ability to enforce access restrictions associated with changes to the configuration of the DBMS or database(s). If it is not able to do this, this is a finding. Review the security configuration of the DBMS and database(s). If it does not enforce access restrictions associated with changes to the configuration of the DBMS or database(s), this is a finding.

Fix: F-6857r291460_fix

Deploy a DBMS capable of enforcing access restrictions associated with changes to the configuration of the DBMS or database(s). Configure the DBMS to enforce access restrictions associated with changes to the configuration of the DBMS or database(s).

b

The DBMS must produce audit records of its enforcement of access restrictions associated with changes to the configuration of the DBMS or database(s).

Medium - CCI-003938 - V-206598 - SV-206598r981958_rule

RMF Control

Severity

M

CCI

CCI-003938

Version

SRG-APP-000381-DB-000361

Vuln IDs

V-206598
V-58127

Rule IDs

SV-206598r981958_rule
SV-72557

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. Enforcement 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.

Checks: C-6858r981957_chk

Review DBMS documentation to verify audit records can be produced when the system denies or fails to complete attempts to change the configuration of the DBMS or database(s). If the DBMS is not capable of this, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when the system denies attempts to change the configuration of the DBMS or database(s). If they are not produced, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when other errors prevent attempts to change the configuration of the DBMS or database(s). If they are not produced, this is a finding.

Fix: F-6858r291463_fix

Deploy a DBMS capable of producing the required audit records when it denies or fails to complete attempts to change the configuration of the DBMS or database(s). Configure the DBMS to produce audit records when it denies attempts to change the configuration of the DBMS or database(s). Configure the DBMS to produce audit records when other errors prevent attempts to change the configuration of the DBMS or database(s).

b

The DBMS must disable network functions, ports, protocols, and services deemed by the organization to be nonsecure, in accord with the Ports, Protocols, and Services Management (PPSM) guidance.

CM-7 - Medium - CCI-001762 - V-206599 - SV-206599r961470_rule

RMF Control

CM-7

Severity

M

CCI

CCI-001762

Version

SRG-APP-000383-DB-000364

Vuln IDs

V-206599
V-58133

Rule IDs

SV-206599r961470_rule
SV-72563

Use of nonsecure network functions, ports, protocols, and services exposes the system to avoidable threats.

Checks: C-6859r291465_chk

Review the network functions, ports, protocols, and services supported by the DBMS. If any protocol is prohibited by the PPSM guidance and is enabled, this is a finding.

Fix: F-6859r291466_fix

Deploy a DBMS capable of disabling a network function, port, protocol, or service prohibited by the PPSM guidance. Disable each prohibited network function, port, protocol, or service.

b

The DBMS must prohibit the use of cached authenticators after an organization-defined time period.

IA-5 - Medium - CCI-002007 - V-206601 - SV-206601r961521_rule

RMF Control

IA-5

Severity

M

CCI

CCI-002007

Version

SRG-APP-000400-DB-000367

Vuln IDs

V-206601
V-58137

Rule IDs

SV-206601r961521_rule
SV-72567

If cached authentication information is out-of-date, the validity of the authentication information may be questionable.

Checks: C-6861r291471_chk

Review system settings to determine whether the organization-defined limit for cached authentication is implemented. If it is not implemented, this is a finding.

Fix: F-6861r291472_fix

Modify system settings to implement the organization-defined limit on the lifetime of cached authenticators.

b

The DBMS must only accept end entity certificates issued by DoD PKI or DoD-approved PKI Certification Authorities (CAs) for the establishment of all encrypted sessions.

SC-23 - Medium - CCI-002470 - V-206603 - SV-206603r961596_rule

RMF Control

SC-23

Severity

M

CCI

CCI-002470

Version

SRG-APP-000427-DB-000385

Vuln IDs

V-206603
V-58167

Rule IDs

SV-206603r961596_rule
SV-72597

Only DoD-approved external PKIs have been evaluated to ensure that they have security controls and identity vetting procedures in place which are sufficient for DoD systems to rely on the identity asserted in the certificate. PKIs lacking sufficient security controls and identity vetting procedures risk being compromised and issuing certificates that enable adversaries to impersonate legitimate users. The authoritative list of DoD-approved PKIs is published at http://iase.disa.mil/pki-pke/interoperability. This requirement focuses on communications protection for the DBMS session rather than for the network packet.

Checks: C-6863r291477_chk

If the DBMS will accept non-DoD approved PKI end-entity certificates, this is a finding.

Fix: F-6863r291478_fix

Revoke trust in any certificates not issued by a DoD-approved certificate authority. Configure the DBMS to accept only DoD and DoD-approved PKI end-entity certificates.

b

The DBMS 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.

SC-28 - Medium - CCI-002475 - V-206604 - SV-206604r961599_rule

RMF Control

SC-28

Severity

M

CCI

CCI-002475

Version

SRG-APP-000428-DB-000386

Vuln IDs

V-206604
V-58169

Rule IDs

SV-206604r961599_rule
SV-72599

DBMSs handling data requiring "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. These cryptographic mechanisms may be native to the DBMS or implemented via additional software or operating system/file system settings, as appropriate to the situation. Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields). The decision whether and what to encrypt rests with the data owner and is also influenced by the physical measures taken to secure the equipment and media on which the information resides.

Checks: C-6864r291480_chk

Review the system documentation to determine whether the organization has defined the information at rest that is to be protected from modification, which must include, at a minimum, PII and classified information. If no information is identified as requiring such protection, this is not a finding. Review the configuration of the DBMS, operating system/file system, and additional software as relevant. If any of the information defined as requiring cryptographic protection from modification is not encrypted in a manner that provides the required level of protection, this is a finding.

Fix: F-6864r291481_fix

Configure the DBMS, operating system/file system, and additional software as relevant, to provide the required level of cryptographic protection.

b

The DBMS must implement cryptographic mechanisms preventing the unauthorized disclosure of organization-defined information at rest on organization-defined information system components.

SC-28 - Medium - CCI-002476 - V-206605 - SV-206605r961602_rule

RMF Control

SC-28

Severity

M

CCI

CCI-002476

Version

SRG-APP-000429-DB-000387

Vuln IDs

V-206605
V-58171

Rule IDs

SV-206605r961602_rule
SV-72601

DBMSs handling data requiring "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. These cryptographic mechanisms may be native to the DBMS or implemented via additional software or operating system/file system settings, as appropriate to the situation. Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields). The decision whether and what to encrypt rests with the data owner and is also influenced by the physical measures taken to secure the equipment and media on which the information resides.

Checks: C-6865r291483_chk

Review the system documentation to determine whether the organization has defined the information at rest that is to be protected from disclosure, which must include, at a minimum, PII and classified information. If the documentation indicates no information requires such protections, this is not a finding. Review the configuration of the DBMS, operating system/file system, and additional software as relevant. If any of the information defined as requiring protection is not encrypted in a manner that provides the required level of protection and is not physically secured to the required level, this is a finding.

Fix: F-6865r291484_fix

Configure the DBMS, operating system/file system, and additional software as relevant, to provide the required level of cryptographic protection for information requiring cryptographic protection against disclosure. Secure the premises, equipment, and media to provide the required level of physical protection.

b

The DBMS must maintain a separate execution domain for each executing process.

SC-39 - Medium - CCI-002530 - V-206606 - SV-206606r961608_rule

RMF Control

SC-39

Severity

M

CCI

CCI-002530

Version

SRG-APP-000431-DB-000388

Vuln IDs

V-206606
V-58173

Rule IDs

SV-206606r961608_rule
SV-72603

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.

Checks: C-6866r291486_chk

Review the DBMS architecture to find out if and how it protects the private resources of one process (such as working memory, temporary tables, uncommitted data and, especially, executable code) from unauthorized access or modification by another user or process. If it is not capable of maintaining a separate execution domain for each executing process, this is a finding. If the DBMS is capable of maintaining a separate execution domain for each executing process, but is configured not to do so, this is a finding.

Fix: F-6866r291487_fix

Deploy a DBMS capable of maintaining a separate execution domain for each executing process. If this is a configurable feature, configure the DBMS to implement it.

b

The DBMS must maintain the confidentiality and integrity of information during preparation for transmission.

SC-8 - Medium - CCI-002420 - V-206607 - SV-206607r961638_rule

RMF Control

SC-8

Severity

M

CCI

CCI-002420

Version

SRG-APP-000441-DB-000378

Vuln IDs

V-206607
V-58153

Rule IDs

SV-206607r961638_rule
SV-72583

Information can be either 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. Use 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. When transmitting data, the DBMS, associated applications, and infrastructure must leverage transmission protection mechanisms.

Checks: C-6867r291489_chk

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, this is not a finding. If the DBMS does not employ protective measures against unauthorized disclosure and modification during preparation for transmission, this is a finding.

Fix: F-6867r291490_fix

Implement protective measures against unauthorized disclosure and modification during preparation for transmission.

b

The DBMS must maintain the confidentiality and integrity of information during reception.

SC-8 - Medium - CCI-002422 - V-206608 - SV-206608r961641_rule

RMF Control

SC-8

Severity

M

CCI

CCI-002422

Version

SRG-APP-000442-DB-000379

Vuln IDs

V-206608
V-58155

Rule IDs

SV-206608r961641_rule
SV-72585

Information can be either unintentionally or maliciously disclosed or modified during reception, 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. This requirement applies only to those applications that are either distributed or can allow access to data nonlocally. Use 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. When receiving data, the DBMS, associated applications, and infrastructure must leverage protection mechanisms.

Checks: C-6868r291492_chk

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, this is not a finding. If the DBMS, associated applications, and infrastructure do not employ protective measures against unauthorized disclosure and modification during reception, this is a finding.

Fix: F-6868r291493_fix

Implement protective measures against unauthorized disclosure and modification during reception.

b

When invalid inputs are received, the DBMS must behave in a predictable and documented manner that reflects organizational and system objectives.

SI-10 - Medium - CCI-002754 - V-206609 - SV-206609r961656_rule

RMF Control

SI-10

Severity

M

CCI

CCI-002754

Version

SRG-APP-000447-DB-000393

Vuln IDs

V-206609
V-58183

Rule IDs

SV-206609r961656_rule
SV-72613

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. The 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. This 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.

Checks: C-6869r291495_chk

Review system documentation to determine how input errors are to be handled in general and if any special handling is defined for specific circumstances. Review the source code for database program objects (stored procedures, functions, triggers) and application source code to identify how the system responds to invalid input. If it does not implement the documented behavior, this is a finding.

Fix: F-6869r291496_fix

Revise and deploy the source code for database program objects (stored procedures, functions, triggers) and application source code, to implement the documented behavior.

b

When updates are applied to the DBMS software, any software components that have been replaced or made unnecessary must be removed.

SI-2 - Medium - CCI-002617 - V-206610 - SV-206610r961677_rule

RMF Control

SI-2

Severity

M

CCI

CCI-002617

Version

SRG-APP-000454-DB-000389

Vuln IDs

V-206610
V-58175

Rule IDs

SV-206610r961677_rule
SV-72605

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 remove older versions of software automatically from the information system. In other cases, manual review and removal will be required. In planning installations and upgrades, organizations must include steps (automated, manual, or both) to identify and remove the outdated modules. A transition period may be necessary when both the old and the new software are required. This should be taken into account in the planning.

Checks: C-6870r291498_chk

If software components that have been replaced or made unnecessary are not removed, this is a finding.

Fix: F-6870r291499_fix

Identify and remove software components that have been replaced or made unnecessary.

b

Security-relevant software updates to the DBMS must be installed within the time period directed by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs).

SI-2 - Medium - CCI-002605 - V-206611 - SV-206611r1001008_rule

RMF Control

SI-2

Severity

M

CCI

CCI-002605

Version

SRG-APP-000456-DB-000390

Vuln IDs

V-206611
V-58177

Rule IDs

SV-206611r1001008_rule
SV-72607

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. Organization-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). This 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 utilized 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. The application 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).

Checks: C-6871r291501_chk

Obtain evidence that software patches are consistently applied to the DBMS within the time frame defined for each patch. If such evidence cannot be obtained, or the evidence that is obtained indicates a pattern of noncompliance, this is a finding.

Fix: F-6871r291502_fix

Institute and adhere to policies and procedures to ensure that patches are consistently applied to the DBMS within the time allowed.

b

The DBMS must be able to generate audit records when security objects are accessed.

AU-12 - Medium - CCI-000172 - V-206612 - SV-206612r961791_rule

RMF Control

AU-12

Severity

M

CCI

Version

SRG-APP-000492-DB-000332

Vuln IDs

V-206612
V-58083

Rule IDs

SV-206612r961791_rule
SV-72513

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 specialized security functionality. In an SQL environment, types of access include, but are not necessarily limited to: SELECT INSERT UPDATE DELETE EXECUTE

Checks: C-6872r291504_chk

If the DBMS architecture makes it impossible for any user, even with the highest privileges, to directly view or directly modify the contents of its built-in security objects, and if there are no additional, locally-defined security objects in the database(s), this is not a finding. Review DBMS documentation to verify that audit records can be produced when security objects, such as tables, views, procedures, and functions, are accessed, to include reads, creations, modifications and deletions of data, and execution of logic. If the DBMS is not capable of this, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when security objects, such as tables, views, procedures, and functions, are accessed, to include reads, creations, modifications and deletions of data, and execution of logic. If they are not produced, this is a finding.

Fix: F-6872r291505_fix

Deploy a DBMS capable of producing the required audit records when security objects, such as tables, views, procedures, and functions, are accessed. Configure the DBMS to produce audit records when security objects, such as tables, views, procedures, and functions, are accessed, to include reads, creations, modifications and deletions of data, and execution of logic.

b

The DBMS must generate audit records when unsuccessful attempts to access security objects occur.

AU-12 - Medium - CCI-000172 - V-206613 - SV-206613r961791_rule

RMF Control

AU-12

Severity

M

CCI

Version

SRG-APP-000492-DB-000333

Vuln IDs

V-206613
V-58085

Rule IDs

SV-206613r961791_rule
SV-72515

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 specialized security functionality. In an SQL environment, types of access include, but are not necessarily limited to: SELECT INSERT UPDATE DELETE EXECUTE To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

Checks: C-6873r291507_chk

If the DBMS architecture makes it impossible for any user, even with the highest privileges, to directly view or directly modify the contents of its built-in security objects, and if there are no additional, locally-defined security objects in the database(s), this is not a finding. Review DBMS documentation to verify that audit records can be produced when the system denies or fails to complete attempts to access security objects, such as tables, views, procedures, and functions, such access to include reads, creations, modifications and deletions of data, and execution of logic. If the DBMS is not capable of this, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when the system denies attempts to access security objects, such as tables, views, procedures, and functions, such access to include reads, creations, modifications and deletions of data, and execution of logic. If they are not produced, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when other errors prevent attempts to access security object. If they are not produced, this is a finding.

Fix: F-6873r291508_fix

Deploy a DBMS capable of producing the required audit records when it denies or fails to complete access to security objects, such as tables, views, procedures, and functions. Configure the DBMS to produce audit records when it denies access to security objects, such as tables, views, procedures, and functions, such access to include reads, creations, modifications and deletions of data, and execution of logic. Configure the DBMS to produce audit records when other errors prevent access to security objects, such as tables, views, procedures, and functions, such access to include reads, creations, modifications and deletions of data, and execution of logic.

b

The DBMS must generate audit records when categories of information (e.g., classification levels/security levels) are accessed.

AU-12 - Medium - CCI-000172 - V-206614 - SV-206614r961797_rule

RMF Control

AU-12

Severity

M

CCI

Version

SRG-APP-000494-DB-000344

Vuln IDs

V-206614
V-58095

Rule IDs

SV-206614r961797_rule
SV-72525

Changes in categories of information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. For 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.

Checks: C-6874r291510_chk

Review DBMS documentation to verify that audit records can be produced when categories of information are accessed, to include reads, creations, modifications, and deletions. If the DBMS is not capable of this, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when categories of information are accessed, to include reads, creations, modifications, and deletions. If they are not produced, this is a finding.

Fix: F-6874r291511_fix

Deploy a DBMS capable of producing the required audit records when categories of information are accessed. Configure the DBMS to produce audit records when categories of information are accessed, to include reads, creations, modifications, and deletions.

b

The DBMS must generate audit records when unsuccessful attempts to access categories of information (e.g., classification levels/security levels) occur.

AU-12 - Medium - CCI-000172 - V-206615 - SV-206615r961797_rule

RMF Control

AU-12

Severity

M

CCI

Version

SRG-APP-000494-DB-000345

Vuln IDs

V-206615
V-58097

Rule IDs

SV-206615r961797_rule
SV-72527

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 failed attempts in addition to the successful ones. For 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.

Checks: C-6875r291513_chk

Review DBMS documentation to verify that audit records can be produced when the system denies or fails to complete attempts to access categories of information, such access to include reads, creations, modifications and deletions. If the DBMS is not capable of this, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when the system denies attempts to access categories of information, such access to include reads, creations, modifications and deletions. If they are not produced, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when other errors prevent attempts to access categories of information, such access to include reads, creations, modifications and deletions. If they are not produced, this is a finding.

Fix: F-6875r291514_fix

Deploy a DBMS capable of producing the required audit records when it denies or fails to complete access to categories of information. Configure the DBMS to produce audit records when it denies access to categories of information, such access to include reads, creations, modifications and deletions. Configure the DBMS to produce audit records when other errors prevent access to categories of information, such access to include reads, creations, modifications and deletions.

b

The DBMS must generate audit records when privileges/permissions are added.

AU-12 - Medium - CCI-000172 - V-206616 - SV-206616r961800_rule

RMF Control

AU-12

Severity

M

CCI

Version

SRG-APP-000495-DB-000326

Vuln IDs

V-206616
V-58071

Rule IDs

SV-206616r961800_rule
SV-72501

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. Elevated privileges give users access to information and functionality that they should not have; restricted privileges wrongly deny access to authorized users. In an SQL environment, adding permissions is typically done via the GRANT command, or, in the negative, the DENY command.

Checks: C-6876r291516_chk

Review DBMS documentation to verify that audit records can be produced when privileges/permissions/role memberships are added. If the DBMS is not capable of this, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when privileges/permissions/role memberships are added. If they are not produced, this is a finding.

Fix: F-6876r291517_fix

Deploy a DBMS capable of producing the required audit records when privileges/permissions/role memberships are added. Configure the DBMS to produce audit records when privileges/permissions/role memberships are added.

b

The DBMS must generate audit records when unsuccessful attempts to add privileges/permissions occur.

AU-12 - Medium - CCI-000172 - V-206617 - SV-206617r961800_rule

RMF Control

AU-12

Severity

M

CCI

Version

SRG-APP-000495-DB-000327

Vuln IDs

V-206617
V-58073

Rule IDs

SV-206617r961800_rule
SV-72503

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 undetected. In an SQL environment, adding permissions is typically done via the GRANT command, or, in the negative, the DENY command. To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

Checks: C-6877r291519_chk

Review DBMS documentation to verify that audit records can be produced when the system denies or fails to complete attempts to add privileges/permissions/role membership. If the DBMS is not capable of this, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when the DBMS denies the addition of privileges/permissions/role membership. If they are not produced, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when other errors prevent the addition of privileges/permissions/role membership. If they are not produced, this is a finding.

Fix: F-6877r291520_fix

Deploy a DBMS capable of producing the required audit records when it denies or fails to complete attempts to add privileges/permissions/role membership. Configure the DBMS to produce audit records when it denies attempts to add privileges/permissions/role membership. Configure the DBMS to produce audit records when other errors prevent attempts to add privileges/permissions/role membership.

b

The DBMS must generate audit records when privileges/permissions are modified.

AU-12 - Medium - CCI-000172 - V-206618 - SV-206618r961800_rule

RMF Control

AU-12

Severity

M

CCI

Version

SRG-APP-000495-DB-000328

Vuln IDs

V-206618
V-58075

Rule IDs

SV-206618r961800_rule
SV-72505

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. Elevated privileges give users access to information and functionality that they should not have; restricted privileges wrongly deny access to authorized users. In an SQL environment, modifying permissions is typically done via the GRANT, REVOKE, and DENY commands.

Checks: C-6878r291522_chk

If there is no distinction in the DBMS's security architecture between modifying permissions on the one hand, and adding and deleting permissions on the other hand, this is not a finding. Review DBMS documentation to verify that audit records can be produced when privileges/permissions/role memberships are modified. If the DBMS is not capable of this, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when privileges/permissions/role memberships are modified. If they are not produced, this is a finding.

Fix: F-6878r291523_fix

Deploy a DBMS capable of producing the required audit records when privileges/permissions/role memberships are modified. Configure the DBMS to produce audit records when privileges/permissions/role memberships are modified.

b

The DBMS must generate audit records when unsuccessful attempts to modify privileges/permissions occur.

AU-12 - Medium - CCI-000172 - V-206619 - SV-206619r961800_rule

RMF Control

AU-12

Severity

M

CCI

Version

SRG-APP-000495-DB-000329

Vuln IDs

V-206619
V-58077

Rule IDs

SV-206619r961800_rule
SV-72507

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 undetected. In an SQL environment, modifying permissions is typically done via the GRANT, REVOKE, and DENY commands. To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

Checks: C-6879r291525_chk

If there is no distinction in the DBMS's security architecture between modifying permissions on the one hand, and adding and deleting permissions on the other hand, this is not a finding. Review DBMS documentation to verify that audit records can be produced when the system denies or fails to complete attempts to modify privileges/permissions/role membership. If the DBMS is not capable of this, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when the system denies attempts to modify privileges/permissions/role membership. If they are not produced, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when other errors prevent attempts to modify privileges/permissions/role membership. If they are not produced, this is a finding.

Fix: F-6879r291526_fix

Deploy a DBMS capable of producing the required audit records when it denies or fails to complete attempts to modify privileges/permissions/role membership. Configure the DBMS to produce audit records when it denies attempts to modify privileges/permissions/role membership. Configure the DBMS to produce audit records when other errors prevent attempts to modify privileges/permissions/role membership.

b

The DBMS must generate audit records when security objects are modified.

AU-12 - Medium - CCI-000172 - V-206620 - SV-206620r961803_rule

RMF Control

AU-12

Severity

M

CCI

Version

SRG-APP-000496-DB-000334

Vuln IDs

V-206620
V-58087

Rule IDs

SV-206620r961803_rule
SV-72517

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, unauthorized changes to the security subsystem could go undetected. The database could be severely compromised or rendered inoperative.

Checks: C-6880r291528_chk

If the DBMS architecture makes it impossible for any user, even with the highest privileges, to modify the structure and logic of its built-in security objects, and if there are no additional, locally-defined security objects in the database(s), this is not a finding. Review DBMS documentation to verify that audit records can be produced when security objects are modified. If the DBMS is not capable of this, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when security objects are modified. If they are not produced, this is a finding.

Fix: F-6880r291529_fix

Deploy a DBMS capable of producing the required audit records when security objects, such as tables, views, procedures, and functions, are modified. Configure the DBMS to produce audit records when security objects, such as tables, views, procedures, and functions, are modified.

b

The DBMS must generate audit records when unsuccessful attempts to modify security objects occur.

AU-12 - Medium - CCI-000172 - V-206621 - SV-206621r961803_rule

RMF Control

AU-12

Severity

M

CCI

Version

SRG-APP-000496-DB-000335

Vuln IDs

V-206621
V-58089

Rule IDs

SV-206621r961803_rule
SV-72519

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, unauthorized changes to the security subsystem could go undetected. The database could be severely compromised or rendered inoperative. To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

Checks: C-6881r291531_chk

If the DBMS architecture makes it impossible for any user, even with the highest privileges, to modify the structure and logic of its built-in security objects, and if there are no additional, locally-defined security objects in the database(s), this is not a finding. Review DBMS documentation to verify that audit records can be produced when the system denies or fails to complete attempts to modify security objects. If the DBMS is not capable of this, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when the system denies attempts to modify security objects. If they are not produced, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when other errors prevent attempts to modify security objects. If they are not produced, this is a finding.

Fix: F-6881r291532_fix

Deploy a DBMS capable of producing the required audit records when it denies or fails to complete attempts to modify security objects, such as tables, views, procedures, and functions. Configure the DBMS to produce audit records when it denies attempts to modify security objects, to include reads, creations, modifications, and deletions. Configure the DBMS to produce audit records when other errors prevent attempts to modify security objects, to include reads, creations, modifications, and deletions.

b

The DBMS must generate audit records when categories of information (e.g., classification levels/security levels) are modified.

AU-12 - Medium - CCI-000172 - V-206622 - SV-206622r961809_rule

RMF Control

AU-12

Severity

M

CCI

Version

SRG-APP-000498-DB-000346

Vuln IDs

V-206622
V-58099

Rule IDs

SV-206622r961809_rule
SV-72529

Changes in categories of information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. For 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.

Checks: C-6882r291534_chk

Review DBMS documentation to verify that audit records can be produced when categories of information are modified. If the DBMS is not capable of this, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when categories of information are modified. If they are not produced, this is a finding.

Fix: F-6882r291535_fix

Deploy a DBMS capable of producing the required audit records when categories of information are modified. Configure the DBMS to produce audit records when categories of information are modified.

b

The DBMS must generate audit records when unsuccessful attempts to modify categories of information (e.g., classification levels/security levels) occur.

AU-12 - Medium - CCI-000172 - V-206623 - SV-206623r961809_rule

RMF Control

AU-12

Severity

M

CCI

Version

SRG-APP-000498-DB-000347

Vuln IDs

V-206623
V-58101

Rule IDs

SV-206623r961809_rule
SV-72531

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 failed attempts in addition to the successful ones. For 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.

Checks: C-6883r291537_chk

Review DBMS documentation to verify that audit records can be produced when the system denies or fails to complete attempts to modify categories of information. If the DBMS is not capable of this, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when the system denies attempts to modify categories of information. If they are not produced, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when other errors prevent attempts to modify categories of information. If they are not produced, this is a finding.

Fix: F-6883r291538_fix

Deploy a DBMS capable of producing the required audit records when it denies or fails to complete modification of categories of information. Configure the DBMS to produce audit records when it denies modification of categories of information. Configure the DBMS to produce audit records when other errors prevent modification of categories of information.

b

The DBMS must generate audit records when privileges/permissions are deleted.

AU-12 - Medium - CCI-000172 - V-206624 - SV-206624r961812_rule

RMF Control

AU-12

Severity

M

CCI

Version

SRG-APP-000499-DB-000330

Vuln IDs

V-206624
V-58079

Rule IDs

SV-206624r961812_rule
SV-72509

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. Elevated privileges give users access to information and functionality that they should not have; restricted privileges wrongly deny access to authorized users. In an SQL environment, deleting permissions is typically done via the REVOKE or DENY command.

Checks: C-6884r291540_chk

Review DBMS documentation to verify that audit records can be produced when privileges/permissions/role memberships are removed, revoked, or denied to any user or role. If the DBMS is not capable of this, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when privileges/permissions/role memberships are removed, revoked, or denied to any user or role. If they are not produced, this is a finding.

Fix: F-6884r291541_fix

Deploy a DBMS capable of producing the required audit records when privileges/permissions/role memberships are removed, revoked, or denied to any user or role. Configure DBMS audit settings to generate an audit record when privileges/permissions/role memberships are removed, revoked, or denied to any user or role.

b

The DBMS must generate audit records when unsuccessful attempts to delete privileges/permissions occur.

AU-12 - Medium - CCI-000172 - V-206625 - SV-206625r961812_rule

RMF Control

AU-12

Severity

M

CCI

Version

SRG-APP-000499-DB-000331

Vuln IDs

V-206625
V-58081

Rule IDs

SV-206625r961812_rule
SV-72511

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 undetected. In an SQL environment, deleting permissions is typically done via the REVOKE or DENY command. To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

Checks: C-6885r291543_chk

Review DBMS documentation to verify that audit records can be produced when the system denies or fails to complete attempts remove, revoke, or deny privileges/permissions/role membership to any user or role. If the DBMS is not capable of this, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when the system denies attempts to remove, revoke, or deny privileges/permissions/role membership to any user or role. If they are not produced, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when other errors prevent attempts to remove, revoke, or deny privileges/permissions/role membership to any user or role. If they are not produced, this is a finding.

Fix: F-6885r291544_fix

Deploy a DBMS capable of producing the required audit records when it denies or fails to complete attempts to remove, revoke, or deny privileges/permissions/role membership to any user or role. Configure the DBMS to produce audit records when it denies attempts to remove, revoke, or deny privileges/permissions/role membership to any user or role. Configure the DBMS to produce audit records when other errors prevent attempts to remove, revoke, or deny privileges/permissions/role membership to any user or role.

b

The DBMS must generate audit records when security objects are deleted.

AU-12 - Medium - CCI-000172 - V-206626 - SV-206626r961818_rule

RMF Control

AU-12

Severity

M

CCI

Version

SRG-APP-000501-DB-000336

Vuln IDs

V-206626
V-58091

Rule IDs

SV-206626r961818_rule
SV-72521

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.

Checks: C-6886r291546_chk

If the DBMS architecture makes it impossible for any user, even with the highest privileges, to drop its built-in security objects, and if there are no additional, locally-defined security objects in the database(s), this is not a finding. Review DBMS documentation to verify that audit records can be produced when security objects are drop. If the DBMS is not capable of this, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when security objects are drop. If they are not produced, this is a finding.

Fix: F-6886r291547_fix

Deploy a DBMS capable of producing the required audit records when security objects are deleted. Configure the DBMS to produce audit records when security objects are deleted.

b

The DBMS must generate audit records when unsuccessful attempts to delete security objects occur.

AU-12 - Medium - CCI-000172 - V-206627 - SV-206627r961818_rule

RMF Control

AU-12

Severity

M

CCI

Version

SRG-APP-000501-DB-000337

Vuln IDs

V-206627
V-58093

Rule IDs

SV-206627r961818_rule
SV-72523

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, it is necessary to keep track of failed attempts in addition to the successful ones.

Checks: C-6887r291549_chk

If the DBMS architecture makes it impossible for any user, even with the highest privileges, to drop its built-in security objects, and if there are no additional, locally-defined security objects in the database(s), this is not a finding. Review DBMS documentation to verify that audit records can be produced when the system denies or fails to complete attempts to drop security objects. If the DBMS is not capable of this, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when the system denies attempts to drop security objects. If they are not produced, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when other errors prevent attempts to drop security objects. If they are not produced, this is a finding.

Fix: F-6887r291550_fix

Deploy a DBMS capable of producing the required audit records when it denies or fails to complete attempts to delete security objects. Configure the DBMS to produce audit records when it denies attempts to delete security objects. Configure the DBMS to produce audit records when other errors prevent attempts to delete security objects.

b

The DBMS must generate audit records when categories of information (e.g., classification levels/security levels) are deleted.

AU-12 - Medium - CCI-000172 - V-206628 - SV-206628r961821_rule

RMF Control

AU-12

Severity

M

CCI

Version

SRG-APP-000502-DB-000348

Vuln IDs

V-206628
V-58103

Rule IDs

SV-206628r961821_rule
SV-72533

Changes in categories of information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. For 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.

Checks: C-6888r291552_chk

Review DBMS documentation to verify that audit records can be produced when categories of information are deleted. If the DBMS is not capable of this, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when categories of information are deleted. If they are not produced, this is a finding.

Fix: F-6888r291553_fix

Deploy a DBMS capable of producing the required audit records when categories of information are deleted. Configure the DBMS to produce audit records when categories of information are deleted.

b

The DBMS must generate audit records when unsuccessful attempts to delete categories of information (e.g., classification levels/security levels) occur.

AU-12 - Medium - CCI-000172 - V-206629 - SV-206629r961821_rule

RMF Control

AU-12

Severity

M

CCI

Version

SRG-APP-000502-DB-000349

Vuln IDs

V-206629
V-58105

Rule IDs

SV-206629r961821_rule
SV-72535

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 failed attempts in addition to the successful ones. For 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.

Checks: C-6889r291555_chk

Review DBMS documentation to verify that audit records can be produced when the system denies or fails to complete attempts to delete categories of information. If the DBMS is not capable of this, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when the system denies attempts to delete categories of information. If they are not produced, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when other errors prevent attempts to delete categories of information. If they are not produced, this is a finding.

Fix: F-6889r291556_fix

Deploy a DBMS capable of producing the required audit records when it denies or fails to complete deletion of categories of information. Configure the DBMS to produce audit records when it denies deletion of categories of information. Configure the DBMS to produce audit records when other errors prevent deletion of categories of information.

b

The DBMS must generate audit records when successful logons or connections occur.

AU-12 - Medium - CCI-000172 - V-206630 - SV-206630r961824_rule

RMF Control

AU-12

Severity

M

CCI

Version

SRG-APP-000503-DB-000350

Vuln IDs

V-206630
V-58107

Rule IDs

SV-206630r961824_rule
SV-72537

For completeness of forensic analysis, it is necessary to track who/what (a user or other principal) logs on to the DBMS.

Checks: C-6890r291558_chk

Review the DBMS audit settings. If an audit record is not generated each time a user (or other principal) logs on or connects to the DBMS, this is a finding.

Fix: F-6890r291559_fix

Configure DBMS audit settings to generate an audit record each time a user (or other principal) logs on or connects to the DBMS. Ensure that the audit record contains the time of the event, the user ID, and session identifier.

b

The DBMS must generate audit records when unsuccessful logons or connection attempts occur.

AU-12 - Medium - CCI-000172 - V-206631 - SV-206631r961824_rule

RMF Control

AU-12

Severity

M

CCI

Version

SRG-APP-000503-DB-000351

Vuln IDs

V-206631
V-58109

Rule IDs

SV-206631r961824_rule
SV-72539

For completeness of forensic analysis, it is necessary to track failed attempts to log on to the DBMS. While positive identification may not be possible in a case of failed authentication, as much information as possible about the incident must be captured.

Checks: C-6891r291561_chk

Review the DBMS audit settings. If an audit record is not generated each time a user (or other principal) attempts but fails to log on or connect to the DBMS (including attempts where the user ID is invalid/unknown), this is a finding.

Fix: F-6891r291562_fix

Configure DBMS audit settings to generate an audit record each time a user (or other principal) attempts but fails to log on or connect to the DBMS. Include attempts where the user ID is invalid/unknown. Ensure that the audit record contains the time of the event and the user ID that was entered (if any).

b

The DBMS must generate audit records for all privileged activities or other system-level access.

AU-12 - Medium - CCI-000172 - V-206632 - SV-206632r961827_rule

RMF Control

AU-12

Severity

M

CCI

Version

SRG-APP-000504-DB-000354

Vuln IDs

V-206632
V-58115

Rule IDs

SV-206632r961827_rule
SV-72545

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 documentation should include a definition of the functionality considered privileged. A 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 an SQL environment, it encompasses, but is not necessarily limited to: CREATE ALTER DROP GRANT REVOKE DENY There may also be Data Manipulation Language (DML) statements that, subject to context, should be regarded as privileged. Possible examples in SQL include: TRUNCATE TABLE; DELETE, or DELETE affecting more than n rows, for some n, or DELETE without a WHERE clause; UPDATE or UPDATE affecting more than n rows, for some n, or UPDATE without a WHERE clause; any SELECT, INSERT, UPDATE, or DELETE to an application-defined security table executed by other than a security principal. Depending on the capabilities of the DBMS 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. Note that it is particularly important to audit, and tightly control, any action that weakens the implementation of this requirement itself, since the objective is to have a complete audit trail of all administrative activity.

Checks: C-6892r291564_chk

Review DBMS documentation to verify that authorized administrative users can designate actions as privileged and that audit records can be produced when privileged actions occur. If the DBMS is not capable of this, this is a finding. Review the system documentation to obtain the definition of the database/DBMS functionality considered privileged in the context of the system in question. Review the DBMS/database security and audit configurations and/or other means used to implement audit logging. If audit logging covers at least all of the actions defined as privileged, this is not a finding; otherwise, this is a finding.

Fix: F-6892r291565_fix

Deploy a DBMS capable of producing the required audit records when privileged actions occur. Configure the DBMS to produce audit records when privileged actions occur.

b

The DBMS must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur.

AU-12 - Medium - CCI-000172 - V-206633 - SV-206633r961827_rule

RMF Control

AU-12

Severity

M

CCI

Version

SRG-APP-000504-DB-000355

Vuln IDs

V-206633
V-58117

Rule IDs

SV-206633r961827_rule
SV-72547

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 documentation should include a definition of the functionality considered privileged. A 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 an SQL environment, it encompasses, but is not necessarily limited to: CREATE ALTER DROP GRANT REVOKE DENY Note that it is particularly important to audit, and tightly control, any action that weakens the implementation of this requirement itself, since the objective is to have a complete audit trail of all administrative activity. To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

Checks: C-6893r291567_chk

Review DBMS documentation to verify that authorized administrative users can designate actions as privileged and that audit records can be produced when the DBMS prevents attempted privileged actions. If the DBMS is not capable of this, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when the DBMS prevents attempted privileged actions. If they are not produced, this is a finding.

Fix: F-6893r291568_fix

Deploy a DBMS capable of producing the required audit records when the DBMS prevents attempted privileged action. Configure the DBMS to produce audit records when the DBMS prevents attempted privileged actions.

b

The DBMS must generate audit records showing starting and ending time for user access to the database(s).

AU-12 - Medium - CCI-000172 - V-206634 - SV-206634r961830_rule

RMF Control

AU-12

Severity

M

CCI

Version

SRG-APP-000505-DB-000352

Vuln IDs

V-206634
V-58111

Rule IDs

SV-206634r961830_rule
SV-72541

For completeness of forensic analysis, it is necessary to know how long a user's (or other principal's) connection to the DBMS lasts. This can be achieved by recording disconnections, in addition to logons/connections, in the audit logs. Disconnection may be initiated by the user or forced by the system (as in a timeout) or result from a system or network failure. To the greatest extent possible, all disconnections must be logged.

Checks: C-6894r291570_chk

Review the DBMS audit settings. If an audit record is not generated each time a user (or other principal) logs off or disconnects from the DBMS voluntarily, or forced by the system, or because of connection or other failure, this is a finding.

Fix: F-6894r291571_fix

Configure DBMS audit settings to generate an audit record each time a user (or other principal) logs off or disconnects, whether voluntarily or forced by the system, or because of connection or other failure, from the DBMS. Ensure that the audit record contains the time of the event, the user ID, and session identifier.

b

The DBMS must generate audit records when concurrent logons/connections by the same user from different workstations occur.

AU-12 - Medium - CCI-000172 - V-206635 - SV-206635r961833_rule

RMF Control

AU-12

Severity

M

CCI

Version

SRG-APP-000506-DB-000353

Vuln IDs

V-206635
V-58113

Rule IDs

SV-206635r961833_rule
SV-72543

For completeness of forensic analysis, it is necessary to track who logs on to the DBMS. Concurrent connections by the same user from multiple workstations may be valid use of the system; or such connections may be due to improper circumvention of the requirement to use the CAC for authentication; or they may indicate unauthorized account sharing; or they may be because an account has been compromised. (If the fact of multiple, concurrent logons by a given user can be reliably reconstructed from the log entries for other events (logons/connections; voluntary and involuntary disconnections), then it is not mandatory to create additional log entries specifically for this.)

Checks: C-6895r291573_chk

Review the DBMS audit settings. If the fact of multiple, concurrent logons by a given user (or other principal) can be reliably reconstructed from the log entries for other events, then this is not a finding. If an audit record is not generated each time a user (or other principal) who is already connected to the DBMS logs on or connects to the DBMS from a different workstation, this is a finding.

Fix: F-6895r291574_fix

Configure DBMS audit settings to generate an audit record each time a user (or other principal) who is already connected to the DBMS logs on or connects to the DBMS from a different workstation.

b

The DBMS must be able to generate audit records when successful accesses to objects occur.

AU-12 - Medium - CCI-000172 - V-206636 - SV-206636r961836_rule

RMF Control

AU-12

Severity

M

CCI

Version

SRG-APP-000507-DB-000356

Vuln IDs

V-206636
V-58119

Rule IDs

SV-206636r961836_rule
SV-72549

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 relating to an incident, or identify those responsible for one. In an SQL environment, types of access include, but are not necessarily limited to: SELECT INSERT UPDATE DELETE EXECUTE

Checks: C-6896r291576_chk

Review DBMS documentation to verify that administrative users can specify database objects for which access must be audited and can specify which kinds of access must be audited. If the DBMS is not capable of this, this is a finding. Review system documentation to determine whether the application owner has specified database objects (tables, views, procedures, functions, etc.) for which access must be audited. Review the DBMS/database security and audit settings to verify that the specified access to the specified objects is audited. If not, this is a finding.

Fix: F-6896r291577_fix

Deploy a DBMS capable of producing the required audit records when object access occurs. Configure audit settings to create audit records when the specified access to the specified objects occurs.

b

The DBMS must generate audit records when unsuccessful accesses to objects occur.

AU-12 - Medium - CCI-000172 - V-206637 - SV-206637r961836_rule

RMF Control

AU-12

Severity

M

CCI

Version

SRG-APP-000507-DB-000357

Vuln IDs

V-206637
V-58121

Rule IDs

SV-206637r961836_rule
SV-72551

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 relating to an incident or identify those responsible for one. In an SQL environment, types of access include, but are not necessarily limited to: SELECT INSERT UPDATE DELETE EXECUTE To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

Checks: C-6897r291579_chk

Review DBMS documentation to verify that administrative users can specify database objects for which access must be audited, and can specify which kinds of access must be audited. If the DBMS is not capable of this, this is a finding. Review DBMS documentation to determine whether the application owner has specified database objects (tables, views, procedures, functions, etc.) for which access must be audited. Review the DBMS/database security and audit settings to verify that audit records are created for unsuccessful attempts at the specified access to the specified objects. If not, this is a finding.

Fix: F-6897r291580_fix

Deploy a DBMS capable of producing the required audit records when object access occurs. Configure audit settings to create audit records when the specified access to the specified objects is unsuccessfully attempted.

b

The DBMS must generate audit records for all direct access to the database(s).

AU-12 - Medium - CCI-000172 - V-206638 - SV-206638r961839_rule

RMF Control

AU-12

Severity

M

CCI

Version

SRG-APP-000508-DB-000358

Vuln IDs

V-206638
V-58123

Rule IDs

SV-206638r961839_rule
SV-72553

In this context, direct access is any query, command, or call to the DBMS 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 non-standard sources.

Checks: C-6898r291582_chk

If the DBMS does not generate audit records for all direct access to the database(s), this is a finding.

Fix: F-6898r291583_fix

Configure the DBMS to generate audit records for all direct access to the database(s).

b

The DBMS must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to provision digital signatures.

SC-13 - Medium - CCI-002450 - V-206639 - SV-206639r961857_rule

RMF Control

SC-13

Severity

M

CCI

Version

SRG-APP-000514-DB-000381

Vuln IDs

V-206639
V-58159

Rule IDs

SV-206639r961857_rule
SV-72589

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 approved by the federal government since this provides assurance they have been tested and validated. For detailed information, refer to NIST FIPS Publication 140-3, Security Requirements For Cryptographic Modules. Note that the product's cryptographic modules must be validated and certified by NIST as FIPS-compliant.

Checks: C-6899r860650_chk

If the DBMS does not employ NIST FIPS 140-2 or 140-3 validated cryptographic modules to provision digital signatures, this is a finding.

Fix: F-6899r860651_fix

Implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to provision digital signatures.

b

The DBMS must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to generate and validate cryptographic hashes.

SC-13 - Medium - CCI-002450 - V-206640 - SV-206640r961857_rule

RMF Control

SC-13

Severity

M

CCI

Version

SRG-APP-000514-DB-000382

Vuln IDs

V-206640
V-58161

Rule IDs

SV-206640r961857_rule
SV-72591

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 approved by the federal government since this provides assurance they have been tested and validated. For detailed information, refer to NIST FIPS Publication 140-3, Security Requirements For Cryptographic Modules. Note that the product's cryptographic modules must be validated and certified by NIST as FIPS-compliant.

Checks: C-6900r860653_chk

If the DBMS does not employ NIST FIPS 140-2 or 140-3 validated cryptographic modules to generate and verify cryptographic hashes, this is a finding.

Fix: F-6900r860654_fix

Implement a NIST FIPS 140-2 or 140-3 validated cryptographic module in the DBMS for generation and verification of cryptographic hashes.

b

The DBMS must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to protect unclassified information requiring confidentiality and cryptographic protection, in accordance with the data owners requirements.

SC-13 - Medium - CCI-002450 - V-206641 - SV-206641r961857_rule

RMF Control

SC-13

Severity

M

CCI

Version

SRG-APP-000514-DB-000383

Vuln IDs

V-206641
V-58163

Rule IDs

SV-206641r961857_rule
SV-72593

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 approved by the federal government since this provides assurance they have been tested and validated. It is the responsibility of the data owner to assess the cryptography requirements in light of applicable federal laws, Executive Orders, directives, policies, regulations, and standards. For detailed information, refer to NIST FIPS Publication 140-3, Security Requirements For Cryptographic Modules. Note that the product's cryptographic modules must be validated and certified by NIST as FIPS-compliant.

Checks: C-6901r860656_chk

If the DBMS does not employ NIST FIPS 140-2 or 140-3 validated cryptographic modules to generate and verify cryptographic hashes, this is a finding.

Fix: F-6901r860657_fix

Implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to provide cryptographic protection for the unclassified information that requires it.

b

The DBMS must off-load audit data to a separate log management facility; this shall 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.

AU-4 - Medium - CCI-001851 - V-206642 - SV-206642r961860_rule

RMF Control

AU-4

Severity

M

CCI

CCI-001851

Version

SRG-APP-000515-DB-000318

Vuln IDs

V-206642
V-58055

Rule IDs

SV-206642r961860_rule
SV-72485

Information stored in one location is vulnerable to accidental or incidental deletion or alteration. Off-loading is a common process in information systems with limited audit storage capacity. The DBMS 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.

Checks: C-6902r291594_chk

Review the system documentation for a description of how audit records are off-loaded. If the DBMS 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. If the DBMS 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.

Fix: F-6902r291595_fix

Configure the DBMS 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.

b

The DBMS must be configured in accordance with the security configuration settings based on DoD security configuration and implementation guidance, including STIGs, NSA configuration guides, CTOs, DTMs, and IAVMs.

CM-6 - Medium - CCI-000366 - V-206643 - SV-206643r961863_rule

RMF Control

CM-6

Severity

M

CCI

CCI-000366

Version

SRG-APP-000516-DB-000363

Vuln IDs

V-206643
V-58131

Rule IDs

SV-206643r961863_rule
SV-72561

Configuring the DBMS to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements. In addition to this SRG, sources of guidance on security and information assurance exist. These include NSA configuration guides, CTOs, DTMs, and IAVMs. The DBMS must be configured in compliance with guidance from all such relevant sources.

Checks: C-6903r291597_chk

Review the DBMS documentation and configuration to determine if the DBMS is configured in accordance with DoD security configuration and implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs and IAVMs. If the DBMS is not configured in accordance with security configuration settings, this is a finding.

Fix: F-6903r291598_fix

Configure the DBMS in accordance with DoD security configuration and implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs and IAVMs.

c

The DBMS must use NSA-approved cryptography to protect classified information in accordance with the data owner's requirements.

SC-13 - High - CCI-002450 - V-233495 - SV-233495r962034_rule

RMF Control

SC-13

Severity

H

CCI