STIGQter: STIG Summary: Oracle Database 12c Security Technical Implementation Guide Version: 2 Release: 1 Benchmark Date: 23 Apr 2021: STIGQter: STIG Summary: Oracle Database 12c Security Technical Implementation Guide Version: 2 Release: 1 Benchmark Date: 23 Apr 2021:SV-220299r397765_rule
V-220299
SRG-APP-000243-DB-000128
O121-C2-018900
CAT II
10
Create and document a process for moving data from production to development/test systems, and follow the process.
Modify any code used for moving data from production to development/test systems to ensure copies of production data are not left in nonsecured locations.
Moving data is only a part of the challenge of protecting the data. When the data is moved, it should also be changed so sensitive information is not made available in development environments.
With the Oracle Data Masking Pack for Oracle Enterprise Manager, organizations can comply with data privacy and protection mandates that restrict the use of actual customer data. With Oracle Data Masking Pack, sensitive information, such as credit card or social security numbers, can be replaced with realistic values, allowing production data to be safely used for development, testing, or sharing with out-source or off-shore partners for other nonproduction purposes. When used in conjunction with Oracle Enterprise Manager, it is easy to develop a secure process that is capable of obfuscating the data during the movement process.
If the Oracle Data Masking Pack and Enterprise Manager are not available, develop site-specific procedures to manage and obfuscate sensitive data.
Verify there are proper procedures in place for the refreshing of development/test data from production. Review any scripts or code that exists for the movement of production data to development/test, and verify copies of production data are not left in unprotected locations.
If there is no documented procedure for data movement from production to development/test, this is a finding.
If the code that exists for data movement does not remove any copies of production data from unprotected locations, this is a finding.
V-220299
False
O121-C2-018900
Verify there are proper procedures in place for the refreshing of development/test data from production. Review any scripts or code that exists for the movement of production data to development/test, and verify copies of production data are not left in unprotected locations.
If there is no documented procedure for data movement from production to development/test, this is a finding.
If the code that exists for data movement does not remove any copies of production data from unprotected locations, this is a finding.
M
4059