STIGQter: STIG Summary: Oracle Database 11.2g Security Technical Implementation Guide Version: 2 Release: 1 Benchmark Date: 23 Apr 2021: STIGQter: STIG Summary: Oracle Database 11.2g Security Technical Implementation Guide Version: 2 Release: 1 Benchmark Date: 23 Apr 2021:SV-238475r667599_rule
V-238475
SRG-APP-000516-DB-000363
O112-C2-016700
CAT II
10
Obtain and utilize native or third-party NIST-validated FIPS 140-2-compliant cryptography solution for the DBMS. Configure cryptographic functions to use FIPS 140-2-compliant algorithms and hashing functions.
Deploy Oracle 11.2.0.4 with the January 2014 CPU patch.
The strength requirements are dependent upon data classification.
For unclassified data, where cryptography is required:
AES 128 for encryption
SHA 256 for hashing
NSA has established the suite B encryption requirements for protecting National Security Systems (NSS) as follows.
AES 128 for Secret
AES 256 for Top Secret
SHA 256 for Secret
SHA 384 for Top Secret
National Security System is defined as:
(OMB Circular A-130) Any telecommunications or information system operated by the United States Government, the function, operation, or use of which (1) involves intelligence activities; (2) involves cryptologic activities related to national security; (3) involves command and control of military forces; (4) involves equipment that is an integral part of a weapon or weapons system; or (5) is critical to the direct fulfillment of military or intelligence missions, but excluding any system that is to be used for routine administrative and business applications (including payroll, finance, logistics, and personnel management applications).
There is more information on this topic in the Oracle Database 11.2g Advanced Security Administrator's Guide, which may be found at http://docs.oracle.com/cd/E11882_01/network.112/e40393.pdf
FIPS 140-2 can be downloaded from http://csrc.nist.gov/publications/PubsFIPS.html#140-2
Review the system documentation to determine whether the database handles classified information. If the database handles classified information, upgrade the severity Category Code to I.
Review the system documentation to discover sensitive or classified data identified by the Information Owner that requires encryption. If no sensitive or classified data is identified as requiring encryption by the Information Owner, this is not a finding.
Have the DBA use select statements in the database to review sensitive data stored in tables as identified in the system documentation.
If all sensitive data identified is encrypted within the database objects, encryption of the DBMS data files is optional and not a finding.
If all sensitive data is not encrypted within database objects, review encryption applied to the DBMS host data files. If no encryption is applied, this is a finding.
V-238475
False
O112-C2-016700
Review the system documentation to determine whether the database handles classified information. If the database handles classified information, upgrade the severity Category Code to I.
Review the system documentation to discover sensitive or classified data identified by the Information Owner that requires encryption. If no sensitive or classified data is identified as requiring encryption by the Information Owner, this is not a finding.
Have the DBA use select statements in the database to review sensitive data stored in tables as identified in the system documentation.
If all sensitive data identified is encrypted within the database objects, encryption of the DBMS data files is optional and not a finding.
If all sensitive data is not encrypted within database objects, review encryption applied to the DBMS host data files. If no encryption is applied, this is a finding.
M
4057