| Finding ID |
Severity |
Title |
Description |
|
V-253507
|
High |
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 approved by the federal government since this provides assurance they have been tested and validated.
It is the responsibility of the data owner... |
|
V-213734
|
High |
Security-relevant software updates to DB2 must be installed within the time period directed by an authoritative source (e.g. IAVM, CTOs, DTMs, and STIGs). |
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... |
|
V-213718
|
High |
DB2 must prevent non-privileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures. |
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... |
|
V-213702
|
High |
DB2 must use NIST FIPS 140-2 validated cryptographic modules for cryptographic operations. |
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... |
|
V-213701
|
High |
When using command-line tools such as db2, users must use a Connect method that does not expose the password. |
To prevent the compromise of authentication information, such as passwords and PINs, during the authentication process, the feedback from the information system must not provide any information that would allow an unauthorized user to compromise the authentication mechanism.
Obfuscation of user-provided information when typed into the system is a method... |
|
V-213700
|
High |
Applications using the database must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals. |
To prevent the compromise of authentication information, such as passwords and PINs, during the authentication process, the feedback from the information system must not provide any information that would allow an unauthorized user to compromise the authentication mechanism.
Obfuscation of user-provided information when typed into the system is a method... |
|
V-213762
|
Medium |
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.
The DBMS may write audit records to database tables, to files in the file system, to other kinds of local repository, or directly... |
|
V-213761
|
Medium |
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 management utility program. The intent is to capture all activity from administrative and non-standard sources. |
|
V-213760
|
Medium |
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 relating to an incident or identify those responsible for one.
In an SQL environment, types of access include, but are not... |
|
V-213759
|
Medium |
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 relating to an incident, or identify those responsible for one.
In an SQL environment, types of access include, but are not... |
|
V-213758
|
Medium |
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 connections may be due to improper circumvention of the requirement to use the CAC for authentication;... |
|
V-213757
|
Medium |
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 to logons/connections, in the audit logs.
Disconnection may be initiated by the user or forced by the system (as... |
|
V-213756
|
Medium |
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 should include a definition of the functionality considered privileged.
A privileged function in this context is any operation that modifies the structure of... |
|
V-213755
|
Medium |
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 should include a definition of the functionality considered privileged.
A privileged function in this context is any operation that modifies the structure of... |
|
V-213754
|
Medium |
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 information as possible about the incident must be captured. |
|
V-213753
|
Medium |
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. |
|
V-213752
|
Medium |
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 attempts in addition to the successful ones.
For detailed information on categorizing information, refer to FIPS Publication 199, Standards... |
|
V-213751
|
Medium |
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 to FIPS Publication 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information... |
|
V-213750
|
Medium |
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 is necessary to keep track of failed attempts in addition to the successful ones. |
|
V-213749
|
Medium |
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. |
|
V-213748
|
Medium |
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 groups' privileges could go undetected.
In an SQL environment, deleting permissions is typically done via the REVOKE command.
To aid in... |
|
V-213747
|
Medium |
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 could go undetected. Elevated privileges give users access to information and functionality that they should not have; restricted privileges wrongly deny access... |
|
V-213746
|
Medium |
DB2 must generate audit records when unsuccessful attempts to modify 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 attempts in addition to the successful ones.
For detailed information on categorizing information, refer to FIPS Publication 199, Standards... |
|
V-213745
|
Medium |
DB2 must generate audit records when categorized information (e.g., classification levels/security levels) is modified. |
Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected.
For detailed information on categorizing information, refer to FIPS Publication 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information... |
|
V-213744
|
Medium |
DB2 must generate audit records when unsuccessful attempts to modify security objects occur. |
Changes in the database objects (tables, views, procedures, functions) that record and control permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized changes to the security subsystem could go undetected. The database could be severely compromised or rendered inoperative.
To aid in... |
|
V-213743
|
Medium |
DB2 must generate audit records when security objects are modified. |
Changes in the database objects (tables, views, procedures, functions) that record and control permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized changes to the security subsystem could go undetected. The database could be severely compromised or rendered inoperative. |
|
V-213742
|
Medium |
DB2 must generate audit records when unsuccessful attempts to modify privileges/permissions occur. |
Failed attempts to change the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized attempts to elevate or restrict individuals' and groups' privileges could go undetected.
In an SQL environment, modifying permissions is typically done via the GRANT and REVOKE.
To aid... |
|
V-213741
|
Medium |
DB2 must generate audit records when privileges/permissions are modified. |
Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restriction of individuals' and groups' privileges could go undetected. Elevated privileges give users access to information and functionality that they should not have; restricted privileges wrongly deny access... |
|
V-213740
|
Medium |
DB2 must generate audit records when unsuccessful attempts to add privileges/permissions occur. |
Failed attempts to change the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized attempts to elevate or restrict individuals' and groups' privileges could go undetected.
In an SQL environment, adding permissions is typically done via the GRANT command.
To aid in... |
|
V-213739
|
Medium |
DB2 must generate audit records when privileges/permissions are added. |
Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restriction of individuals' and groups' privileges could go undetected. Elevated privileges give users access to information and functionality that they should not have; restricted privileges wrongly deny access... |
|
V-213738
|
Medium |
DB2 must generate audit records when unsuccessful attempts to access categorized information (e.g., classification levels/security levels) occur. |
Use of 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 attempts in addition to the successful ones.
For detailed information on categorizing information, refer to FIPS Publication 199, Standards... |
|
V-213737
|
Medium |
DB2 must generate audit records when categorized information (e.g., classification levels/security levels) are accessed. |
Use of categorized 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... |
|
V-213736
|
Medium |
DB2 must generate audit records when unsuccessful attempts to access security objects occur. |
Changes to the security configuration must be tracked.
This requirement applies to situations where security data is retrieved or modified via data manipulation operations, as opposed to via specialized security functionality.
In an SQL environment, types of access include, but are not necessarily limited to:
SELECT
INSERT
UPDATE
DELETE
EXECUTE... |
|
V-213735
|
Medium |
DB2 must generate audit records when security objects are accessed. |
Changes to the security configuration must be tracked.
This requirement applies to situations where security data is retrieved or modified via data manipulation operations, as opposed to via specialized security functionality.
In an SQL environment, types of access include, but are not necessarily limited to:
SELECT
INSERT
UPDATE
DELETE
EXECUTE |
|
V-213733
|
Medium |
When invalid inputs are received, DB2 must behave in a predictable and documented manner that reflects organizational and system objectives. |
A common vulnerability is unplanned behavior when invalid inputs are received. This requirement guards against adverse or unintended system behavior caused by invalid inputs, where information system responses to the invalid input may be disruptive or cause the system to fail into an unsafe state.
The behavior will be derived... |
|
V-213732
|
Medium |
DB2 must maintain the confidentiality and integrity of information during reception. |
: Information can be either unintentionally or maliciously disclosed or modified during reception, including, for example, during aggregation, at protocol transformation points, and during 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... |
|
V-213731
|
Medium |
DB2 must maintain the confidentiality and integrity of information during preparation for transmission. |
Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, including, for example, during aggregation, at protocol transformation points, 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... |
|
V-213730
|
Medium |
DB2 must implement and/or support cryptographic mechanisms preventing the unauthorized disclosure of organization-defined information at rest on organization-defined information system components. |
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... |
|
V-213729
|
Medium |
DB2 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. |
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... |
|
V-213728
|
Medium |
DB2 must only accept end entity certificates issued by DoD PKI or DoD-approved PKI Certification Authorities (CAs) for the establishment of all encrypted sessions. |
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... |
|
V-213726
|
Medium |
DB2 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. |
Use of nonsecure network functions, ports, protocols, and services exposes the system to avoidable threats. |
|
V-213725
|
Medium |
DB2 must produce audit records of its enforcement of access restrictions associated with changes to the configuration of DB2 or database(s). |
Without auditing the enforcement of access restrictions against changes to configuration, it would be difficult to identify attempted attacks and an audit trail would not be available for forensic investigation for after-the-fact actions.
Enforcement actions are the methods or mechanisms used to prevent unauthorized changes to configuration settings. Enforcement action... |
|
V-213724
|
Medium |
DB2 and the operating system must enforce access restrictions associated with changes to the configuration of DB2 or database(s). |
Failure to provide logical access restrictions associated with changes to configuration may have significant effects on the overall security of the system.
When dealing with access restrictions pertaining to change control, it should be noted that any changes to the hardware, software, and/or firmware components of the information system can... |
|
V-213723
|
Medium |
DB2 must prohibit user installation of logic modules (stored procedures, functions, triggers, views, etc.) without explicit privileged status. |
Allowing regular users to install software, without explicit privileges, creates the risk that untested or potentially malicious software will be installed on the system. Explicit privileges (escalated or administrative privileges) provide the regular user with explicit capabilities and control that exceed the rights of a regular user.
DBMS functionality and... |
|
V-213722
|
Medium |
DB2 must provide an immediate real-time alert to appropriate support staff of all audit failure events requiring real-time alerts. |
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... |
|
V-213721
|
Medium |
DB2 must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75% of maximum audit record storage capacity. |
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... |
|
V-213720
|
Medium |
DB2 must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements. |
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... |
|
V-213719
|
Medium |
DB2 must utilize centralized management of the content captured in audit records generated by all components of DB2. |
Without the ability to centrally manage the content captured in the audit records, identification, troubleshooting, and correlation of suspicious behavior would be difficult and could lead to a delayed or incomplete analysis of an ongoing attack.
The content captured in audit records must be managed from a central location (necessitating... |
|
V-213717
|
Medium |
When supporting applications that require security labeling of data, DB2 must associate organization-defined types of security labels having organization-defined security label values with information in process. |
Without the association of security labels to information, there is no basis for 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... |
|
V-213716
|
Medium |
When supporting applications that require security labeling of data, DB2 must associate organization-defined types of security labels having organization-defined security label values with information in storage. |
Without the association of security labels to information, there is no basis for 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... |
|
V-213715
|
Medium |
DB2 must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect. |
This addresses the termination of user-initiated logical sessions in contrast to the termination of network connections that are associated with communications sessions (i.e., network disconnect). 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... |
|
V-213714
|
Medium |
DB2 must reveal detailed error messages only to the ISSO, ISSM, SA and DBA. |
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... |
|
V-213713
|
Medium |
DB2 must provide non-privileged users with error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries. |
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... |
|
V-213712
|
Medium |
DB2 and associated applications, when making use of dynamic code execution, must scan input data for invalid values that may indicate a code injection attack. |
With respect to database management systems, one class of threat is known as SQL Injection, or more generally, code injection. It takes advantage of the dynamic execution capabilities of various programming languages, including dialects of SQL. In such cases, the attacker deduces the manner in which SQL statements are being... |
|
V-213711
|
Medium |
DB2 and associated applications must reserve the use of dynamic code execution for situations that require it. |
With respect to database management systems, one class of threat is known as SQL Injection, or more generally, code injection. It takes advantage of the dynamic execution capabilities of various programming languages, including dialects of SQL. In such cases, the attacker deduces the manner in which SQL statements are being... |
|
V-213710
|
Medium |
DB2 must check the validity of all data inputs except those specifically identified by the organization. |
Invalid user input occurs when a user inserts data or characters into an application's data entry fields and the application is unprepared to process that data. This results in unanticipated application behavior, potentially leading to an application or information system compromise. Invalid user input is one of the primary methods... |
|
V-213709
|
Medium |
Access to database files must be limited to relevant processes and to authorized, administrative users. |
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. |
|
V-213708
|
Medium |
Database contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy. |
Applications, including DBMSs, must prevent unauthorized and unintended information transfer via shared system resources.
Data used for the development and testing of applications often involves 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,... |
|
V-213707
|
Medium |
DB2 must isolate security functions from non-security functions. |
An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform security functions.
Security functions are the hardware, software, 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... |
|
V-213706
|
Medium |
DB2 must protect the confidentiality and integrity of all information at rest. |
This control is intended to address the confidentiality and integrity of information at rest in 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... |
|
V-213705
|
Medium |
In the event of a system failure, DB2 must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes. |
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.... |
|
V-213704
|
Medium |
DB2 must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values. |
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 approved random number generator.
However, it is... |
|
V-213703
|
Medium |
DB2 must separate user functionality (including user interface services) from database management functionality. |
Information system management functionality includes functions necessary to administer databases, network components, workstations, or servers and typically requires privileged user access.
The 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... |
|
V-213699
|
Medium |
If passwords are used for authentication, DB2 must transmit only encrypted representations of passwords. |
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... |
|
V-213698
|
Medium |
DB2 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. |
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.... |
|
V-213697
|
Medium |
Access to external executables must be disabled or restricted. |
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... |
|
V-213696
|
Medium |
Unused database components which are integrated in DB2 and cannot be uninstalled must be disabled. |
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... |
|
V-213695
|
Medium |
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 organizational operations (e.g., key missions, functions).
It is detrimental for software products to provide, or install by default, functionality exceeding requirements... |
|
V-213694
|
Medium |
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 organizational operations (e.g., key missions, functions).
It is detrimental for software products to provide, or install by default, functionality exceeding requirements... |
|
V-213693
|
Medium |
The role(s)/group(s) used to modify database structure (including but not necessarily limited to tables, indexes, storage, etc.) and logic modules (stored procedures, functions, triggers, links to software external to 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 a robust change management process.
Accordingly, only qualified and authorized individuals shall be allowed to obtain access... |
|
V-213692
|
Medium |
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 can be coded using definer's rights. This allows anyone who utilizes the object to perform the actions if they were the... |
|
V-213691
|
Medium |
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 significant effects on the overall security of the system.
Multiple applications can provide a cumulative negative effect. A vulnerability and subsequent exploit... |
|
V-213690
|
Medium |
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 effects on the overall security of the system.
If the system were to allow any user to make changes to software libraries,... |
|
V-213689
|
Medium |
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 robust change management process.
Accordingly, only qualified and authorized individuals shall be allowed to obtain access to information... |
|
V-213688
|
Medium |
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 robust change management process.
Accordingly, only qualified and authorized individuals shall be allowed to obtain access to information... |
|
V-213687
|
Medium |
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 audit data.
Applications providing tools to interface with audit data will leverage user permissions and roles identifying the user accessing the tools... |
|
V-213686
|
Medium |
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 audit data.
Applications providing tools to interface with audit data will leverage user permissions and roles identifying the user accessing the tools... |
|
V-213685
|
Medium |
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 provide the only means to manipulate and manage application and system log data. It is, therefore, imperative that access to... |
|
V-213684
|
Medium |
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 veracity of audit data, the information system and/or the application must protect audit information from unauthorized deletion. This requirement can be... |
|
V-213683
|
Medium |
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 veracity of audit data the information system and/or the application must protect audit information from unauthorized modification.
This requirement can be... |
|
V-213682
|
Medium |
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 addition, access to audit records provides information an attacker could potentially use to his or her advantage.
To ensure the... |
|
V-213681
|
Medium |
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; failures in the audit capturing mechanisms; and audit storage capacity being reached or exceeded. Responses to audit failure depend... |
|
V-213680
|
Medium |
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 information. To support analysis, some types of events will need information to be logged that exceeds the basic requirements of event type, time... |
|
V-213679
|
Medium |
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 whether an attack was successful or if changes were made to the security state of the system.
Event outcomes can include indicators of event... |
|
V-213678
|
Medium |
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 for the whole time the DBMS is running. |
|
V-213677
|
Medium |
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 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... |
|
V-213676
|
Medium |
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 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... |
|
V-213675
|
Medium |
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.
Suppression of auditing could permit an adversary to evade detection.
Misconfigured audits can degrade the system's performance by overwhelming the... |
|
V-213674
|
Medium |
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 records can be generated from various components within the DBMS (e.g., process, module). Certain specific application functionalities may be audited as... |
|
V-213673
|
Medium |
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 information (e.g., indicating concurrence or signing a contract), and receiving a message.
Non-repudiation protects against later claims by a user of not having created,... |
|
V-213672
|
Medium |
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 that have been issued certificates by DoD-approved PKIs, all DoD systems, including databases, must be properly configured to implement access control policies.
Successful... |
|
V-213671
|
Medium |
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 other error. Managing accounts for the same person in multiple places is inefficient and prone to problems with consistency and synchronization.
A comprehensive... |
|
V-213670
|
Medium |
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 (DoS) attack by exhausting connection resources; and a system can also fail or be degraded by an overload of legitimate... |
