III - Administrative Public
Rules and Groups employed by this XCCDF Profile
-
SRG-APP-000023-DB-000001
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.
Enterprise environments make account management for applications and databases challenging and complex. A manual process for account management functions adds the risk of a potential oversight or o...Rule Medium Severity -
SRG-APP-000033-DB-000084
Group -
DB2 must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.
Authentication with a DoD-approved PKI certificate does not necessarily imply authorization to access the DBMS. To mitigate the risk of unauthorized access to sensitive information by entities tha...Rule Medium Severity -
SRG-APP-000080-DB-000063
Group -
DB2 must protect against a user falsely repudiating having performed organization-defined actions.
Non-repudiation of actions taken is required in order to maintain data integrity. Examples of particular actions taken by individuals include creating information, sending a message, approving info...Rule Medium Severity -
SRG-APP-000089-DB-000064
Group -
DB2 must provide audit record generation capability for DoD-defined auditable events within all DBMS/database components.
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit re...Rule Medium Severity -
SRG-APP-000090-DB-000065
Group -
DB2 must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited.
Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent or interfere with the auditing of critical events. ...Rule Medium Severity -
SRG-APP-000091-DB-000066
Group -
DB2 must generate audit records when privileges/permissions are retrieved.
Under some circumstances, it may be useful to monitor who/what is reading privilege/permission/role information. Therefore, it must be possible to configure auditing to do this. DBMSs typically mak...Rule Medium Severity -
SRG-APP-000091-DB-000325
Group -
DB2 must generate audit records when unsuccessful attempts to retrieve privileges/permissions occur.
Under some circumstances, it may be useful to monitor who/what is reading privilege/permission/role information. Therefore, it must be possible to configure auditing to do this. DBMSs typically mak...Rule Medium Severity -
SRG-APP-000092-DB-000208
Group -
DB2 must initiate session auditing upon startup.
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 ...Rule Medium Severity -
SRG-APP-000099-DB-000043
Group -
DB2 must produce audit records containing sufficient information to establish the outcome (success or failure) of the events.
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 wheth...Rule Medium Severity -
SRG-APP-000101-DB-000044
Group -
DB2 must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject.
Information system auditing capability is critical for accurate forensic analysis. Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough infor...Rule Medium Severity -
SRG-APP-000109-DB-000049
Group -
Unless it has been determined that availability is paramount, DB2 must, upon audit failure, cease all auditable activity.
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; failu...Rule Medium Severity -
SRG-APP-000118-DB-000059
Group -
The audit information produced by DB2 must be protected from unauthorized read access.
If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is difficult, if not impossible, to achieve. In ...Rule Medium Severity -
SRG-APP-000119-DB-000060
Group -
The audit information produced by DB2 must be protected from unauthorized modification.
If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. To ensure the veraci...Rule Medium Severity -
SRG-APP-000120-DB-000061
Group -
The audit information produced by DB2 must be protected from unauthorized deletion.
If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. To ensure the veracit...Rule Medium Severity -
SRG-APP-000121-DB-000202
Group -
DB2 must protect its audit features from unauthorized access.
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 ...Rule Medium Severity -
SRG-APP-000122-DB-000203
Group -
DB2 must protect its audit configuration from unauthorized modification.
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 au...Rule Medium Severity -
SRG-APP-000123-DB-000204
Group -
DB2 must protect its audit features from unauthorized removal.
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 au...Rule Medium Severity -
SRG-APP-000133-DB-000179
Group -
DB2 must limit privileges to change software modules, to include stored procedures, functions and triggers, and links to software external to DB2.
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 robus...Rule Medium Severity -
SRG-APP-000133-DB-000179
Group -
The OS must limit privileges to change the DB2 software resident within software libraries (including privileged programs).
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 robus...Rule Medium Severity -
SRG-APP-000133-DB-000198
Group -
The DB2 software installation account must be restricted to authorized users.
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 effec...Rule Medium Severity -
SRG-APP-000133-DB-000199
Group -
Database software, including DBMS configuration files, must be stored in dedicated directories, separate from the host OS and other applications.
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 signi...Rule Medium Severity -
SRG-APP-000133-DB-000200
Group -
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.
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...Rule Medium Severity -
SRG-APP-000133-DB-000362
Group -
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 DB2, etc.) must be restricted to authorized users.
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 ...Rule Medium Severity -
SRG-APP-000141-DB-000090
Group -
Default demonstration and sample databases, database objects, and applications must be removed.
Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizatio...Rule Medium Severity -
SRG-APP-000141-DB-000091
Group -
Unused database components, DBMS software, and database objects must be removed.
Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizatio...Rule Medium Severity
Node 2
The content of the drawer really is up to you. It could have form fields, definition lists, text lists, labels, charts, progress bars, etc. Spacing recommendation is 24px margins. You can put tabs in here, and can also make the drawer scrollable.