Skip to content

IBM DB2 V10.5 LUW Security Technical Implementation Guide

Rules, Groups, and Values defined within the XCCDF Benchmark

  • SRG-APP-000356-DB-000314

    <GroupDescription></GroupDescription>
    Group
  • DB2 must generate audit records when unsuccessful logons or connection attempts occur.

    &lt;VulnDiscussion&gt;For completeness of forensic analysis, it is necessary to track failed attempts to log on to the DBMS. While positive identif...
    Rule Medium Severity
  • SRG-APP-000504-DB-000354

    <GroupDescription></GroupDescription>
    Group
  • SRG-APP-000023-DB-000001

    <GroupDescription></GroupDescription>
    Group
  • DB2 must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals.

    &lt;VulnDiscussion&gt;Enterprise environments make account management for applications and databases challenging and complex. A manual process for ...
    Rule Medium Severity
  • SRG-APP-000033-DB-000084

    <GroupDescription></GroupDescription>
    Group
  • DB2 must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.

    &lt;VulnDiscussion&gt;Authentication with a DoD-approved PKI certificate does not necessarily imply authorization to access the DBMS. To mitigate ...
    Rule Medium Severity
  • SRG-APP-000080-DB-000063

    <GroupDescription></GroupDescription>
    Group
  • DB2 must protect against a user falsely repudiating having performed organization-defined actions.

    &lt;VulnDiscussion&gt;Non-repudiation of actions taken is required in order to maintain data integrity. Examples of particular actions taken by ind...
    Rule Medium Severity
  • SRG-APP-000089-DB-000064

    <GroupDescription></GroupDescription>
    Group
  • DB2 must provide audit record generation capability for DoD-defined auditable events within all DBMS/database components.

    &lt;VulnDiscussion&gt;Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events r...
    Rule Medium Severity
  • SRG-APP-000090-DB-000065

    <GroupDescription></GroupDescription>
    Group
  • DB2 must generate audit records when privileges/permissions are added.

    &lt;VulnDiscussion&gt;Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unautho...
    Rule Medium Severity
  • DB2 must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited.

    &lt;VulnDiscussion&gt;Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel ma...
    Rule Medium Severity
  • SRG-APP-000091-DB-000066

    <GroupDescription></GroupDescription>
    Group
  • DB2 must generate audit records when privileges/permissions are retrieved.

    &lt;VulnDiscussion&gt;Under some circumstances, it may be useful to monitor who/what is reading privilege/permission/role information. Therefore, i...
    Rule Medium Severity
  • SRG-APP-000091-DB-000325

    <GroupDescription></GroupDescription>
    Group
  • DB2 must generate audit records when unsuccessful attempts to retrieve privileges/permissions occur.

    &lt;VulnDiscussion&gt;Under some circumstances, it may be useful to monitor who/what is reading privilege/permission/role information. Therefore, i...
    Rule Medium Severity
  • SRG-APP-000092-DB-000208

    <GroupDescription></GroupDescription>
    Group
  • DB2 must initiate session auditing upon startup.

    &lt;VulnDiscussion&gt;Session auditing is for use when a user's activities are under investigation. To be sure of capturing all activity during tho...
    Rule Medium Severity
  • SRG-APP-000099-DB-000043

    <GroupDescription></GroupDescription>
    Group
  • DB2 must produce audit records containing sufficient information to establish the outcome (success or failure) of the events.

    &lt;VulnDiscussion&gt;Information system auditing capability is critical for accurate forensic analysis. Without information about the outcome of e...
    Rule Medium Severity
  • SRG-APP-000101-DB-000044

    <GroupDescription></GroupDescription>
    Group
  • SRG-APP-000495-DB-000327

    <GroupDescription></GroupDescription>
    Group
  • DB2 must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject.

    &lt;VulnDiscussion&gt;Information system auditing capability is critical for accurate forensic analysis. Reconstruction of harmful events or forens...
    Rule Medium Severity
  • SRG-APP-000109-DB-000049

    <GroupDescription></GroupDescription>
    Group
  • Unless it has been determined that availability is paramount, DB2 must, upon audit failure, cease all auditable activity.

    &lt;VulnDiscussion&gt;It is critical that when the DBMS is at risk of failing to process audit logs as required, it take action to mitigate the fai...
    Rule Medium Severity
  • SRG-APP-000118-DB-000059

    <GroupDescription></GroupDescription>
    Group
  • The audit information produced by DB2 must be protected from unauthorized read access.

    &lt;VulnDiscussion&gt;If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially ma...
    Rule Medium Severity
  • SRG-APP-000119-DB-000060

    <GroupDescription></GroupDescription>
    Group
  • The audit information produced by DB2 must be protected from unauthorized modification.

    &lt;VulnDiscussion&gt;If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially ma...
    Rule Medium Severity
  • SRG-APP-000120-DB-000061

    <GroupDescription></GroupDescription>
    Group
  • The audit information produced by DB2 must be protected from unauthorized deletion.

    &lt;VulnDiscussion&gt;If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially ma...
    Rule Medium Severity
  • SRG-APP-000121-DB-000202

    <GroupDescription></GroupDescription>
    Group
  • DB2 must protect its audit features from unauthorized access.

    &lt;VulnDiscussion&gt;Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Depending up...
    Rule Medium Severity
  • SRG-APP-000122-DB-000203

    <GroupDescription></GroupDescription>
    Group
  • DB2 must protect its audit configuration from unauthorized modification.

    &lt;VulnDiscussion&gt;Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, pro...
    Rule Medium Severity
  • SRG-APP-000123-DB-000204

    <GroupDescription></GroupDescription>
    Group
  • DB2 must protect its audit features from unauthorized removal.

    &lt;VulnDiscussion&gt;Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, pro...
    Rule Medium Severity
  • SRG-APP-000133-DB-000179

    <GroupDescription></GroupDescription>
    Group
  • DB2 must limit privileges to change software modules, to include stored procedures, functions and triggers, and links to software external to DB2.

    &lt;VulnDiscussion&gt;If the system were to allow any user to make changes to software libraries, then those changes might be implemented without u...
    Rule Medium Severity
  • SRG-APP-000133-DB-000179

    <GroupDescription></GroupDescription>
    Group
  • The OS must limit privileges to change the DB2 software resident within software libraries (including privileged programs).

    &lt;VulnDiscussion&gt;If the system were to allow any user to make changes to software libraries, then those changes might be implemented without u...
    Rule Medium Severity
  • SRG-APP-000133-DB-000198

    <GroupDescription></GroupDescription>
    Group
  • The DB2 software installation account must be restricted to authorized users.

    &lt;VulnDiscussion&gt;When dealing with change control issues, it should be noted any changes to the hardware, software, and/or firmware components...
    Rule Medium Severity
  • SRG-APP-000133-DB-000199

    <GroupDescription></GroupDescription>
    Group
  • Database software, including DBMS configuration files, must be stored in dedicated directories, separate from the host OS and other applications.

    &lt;VulnDiscussion&gt;When dealing with change control issues, it should be noted any changes to the hardware, software, and/or firmware components...
    Rule Medium Severity
  • SRG-APP-000133-DB-000200

    <GroupDescription></GroupDescription>
    Group
  • DB2 must generate audit records when unsuccessful attempts to add privileges/permissions occur.

    &lt;VulnDiscussion&gt;Failed attempts to change the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit...
    Rule Medium Severity
  • Database objects (including but not limited to tables, indexes, storage, stored procedures, functions, triggers, links to software external to DB2, etc.) must be owned by database/DBMS principals authorized for ownership.

    &lt;VulnDiscussion&gt;Within the database, object ownership implies full privileges to the owned object, including the privilege to assign access t...
    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