STIGQter STIGQter: STIG Summary: Oracle Database 19c Security Technical Implementation Guide Version: 1 Release: 5 Benchmark Date: 01 Apr 2026:

Oracle Database contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy.

DISA Rule

SV-270577r1137656_rule

Vulnerability Number

V-270577

Group Title

SRG-APP-000243-DB-000128

Rule Version

O19C-00-017400

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

Restrict accessibility of Oracle system tables and other configuration information or metadata to database administrators (DBAs) or other authorized users.

Modify any code used for moving data from production to development/test systems to comply with the organization-defined data transfer policy, and to ensure copies of production data are not left in unsecured locations.

Implement policy and procedures to modify or remove sensitive information in production exports prior to import into development databases.

Check Contents

Review the procedures 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 systems, or to any other location or for any other purpose.

Verify that copies of production data are not left in unprotected locations.

If the code that exists for data movement does not comply with the organization-defined data transfer policy and/or fails to remove any copies of production data from unprotected locations, this is a finding.

If sensitive data is included in the exports and no procedures are in place to remove or modify the data to render it not sensitive prior to import into a development database or policy and procedures are not in place to ensure authorization of development personnel to access sensitive information contained in production data, this is a finding.

Vulnerability Number

V-270577

Documentable

False

Rule Version

O19C-00-017400

Severity Override Guidance

Review the procedures 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 systems, or to any other location or for any other purpose.

Verify that copies of production data are not left in unprotected locations.

If the code that exists for data movement does not comply with the organization-defined data transfer policy and/or fails to remove any copies of production data from unprotected locations, this is a finding.

If sensitive data is included in the exports and no procedures are in place to remove or modify the data to render it not sensitive prior to import into a development database or policy and procedures are not in place to ensure authorization of development personnel to access sensitive information contained in production data, this is a finding.

Check Content Reference

M

Target Key

5672