Skip to content

II - Mission Support Classified

Rules and Groups employed by this XCCDF Profile

  • SRG-APP-000499-DB-000330

    Group
  • DB2 must generate audit records when privileges/permissions are deleted.

    Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restriction of individuals' and groups' privileges co...
    Rule Medium Severity
  • SRG-APP-000499-DB-000331

    Group
  • DB2 must generate audit records when unsuccessful attempts to delete privileges/permissions occur.

    Failed attempts to change the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized attempts to elevate or restrict individuals' and gr...
    Rule Medium Severity
  • SRG-APP-000501-DB-000336

    Group
  • DB2 must generate audit records when security objects are deleted.

    The removal of security objects from the database/DBMS would seriously degrade a system's information assurance posture. If such an event occurs, it must be logged.
    Rule Medium Severity
  • SRG-APP-000501-DB-000337

    Group
  • DB2 must generate audit records when unsuccessful attempts to delete security objects occur.

    The removal of security objects from the database/DBMS would seriously degrade a system's information assurance posture. If such an action is attempted, it must be logged. To aid in diagnosis, it ...
    Rule Medium Severity
  • SRG-APP-000502-DB-000348

    Group
  • DB2 must generate audit records when categorized information (e.g., classification levels/security levels) is deleted.

    Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. For detailed information on categorizing information, refer t...
    Rule Medium Severity
  • SRG-APP-000502-DB-000349

    Group
  • DB2 must generate audit records when unsuccessful attempts to delete categorized information (e.g., classification levels/security levels) occur.

    Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. To aid in diagnosis, it is necessary to keep track of failed ...
    Rule Medium Severity
  • SRG-APP-000503-DB-000350

    Group
  • DB2 must generate audit records when successful logons or connections occur.

    For completeness of forensic analysis, it is necessary to track who/what (a user or other principal) logs on to the DBMS.
    Rule Medium Severity
  • SRG-APP-000503-DB-000351

    Group
  • DB2 must generate audit records when unsuccessful logons or connection attempts occur.

    For completeness of forensic analysis, it is necessary to track failed attempts to log on to the DBMS. While positive identification may not be possible in a case of failed authentication, as much ...
    Rule Medium Severity
  • SRG-APP-000504-DB-000354

    Group
  • DB2 must generate audit records for all privileged activities or other system-level access.

    Without tracking privileged activity, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. System documentation...
    Rule Medium Severity
  • SRG-APP-000504-DB-000355

    Group
  • DB2 must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur.

    Without tracking privileged activity, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. System documentation...
    Rule Medium Severity
  • SRG-APP-000505-DB-000352

    Group
  • DB2 must generate audit records showing starting and ending time for user access to the database(s).

    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 t...
    Rule Medium Severity
  • SRG-APP-000506-DB-000353

    Group
  • DB2 must generate audit records when concurrent logons/connections by the same user from different workstations occur.

    For completeness of forensic analysis, it is necessary to track who logs on to the DBMS. Concurrent connections by the same user from multiple workstations may be valid use of the system; or such ...
    Rule Medium Severity
  • SRG-APP-000507-DB-000356

    Group
  • DB2 must generate audit records when successful accesses to objects occur.

    Without tracking all or selected types of access to all or selected objects (tables, views, procedures, functions, etc.), it would be difficult to establish, correlate, and investigate the events r...
    Rule Medium Severity
  • SRG-APP-000507-DB-000357

    Group
  • DB2 must generate audit records when unsuccessful accesses to objects occur.

    Without tracking all or selected types of access to all or selected objects (tables, views, procedures, functions, etc.), it would be difficult to establish, correlate, and investigate the events r...
    Rule Medium Severity
  • SRG-APP-000508-DB-000358

    Group
  • DB2 must generate audit records for all direct access to the database(s).

    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...
    Rule Medium Severity
  • SRG-APP-000515-DB-000318

    Group
  • DB2 must off-load audit data to a separate log management facility; this must be continuous and in near real time for systems with a network connection to the storage facility and weekly or more often for stand-alone systems.

    Information stored in one location is vulnerable to accidental or incidental deletion or alteration. Off-loading is a common process in information systems with limited audit storage capacity. T...
    Rule Medium Severity
  • SRG-APP-000416-DB-000380

    Group
  • DB2 must use NSA-approved cryptography to protect classified information in accordance with the data owners requirements.

    Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards ...
    Rule High Severity
  • SRG-APP-000001-DB-000031

    Group
  • DB2 must limit the number of concurrent sessions to an organization-defined number per user for all accounts and/or account types.

    Database management includes the ability to control the number of users and user sessions utilizing a DBMS. Unlimited concurrent connections to the DBMS could allow a successful Denial of Service (...
    Rule Medium Severity

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

Capacity
Modules