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

The OS must limit privileges to change the database management system (DBMS) software resident within software libraries (including privileged programs).

DISA Rule

SV-270515r1065210_rule

Vulnerability Number

V-270515

Group Title

SRG-APP-000133-DB-000179

Rule Version

O19C-00-007900

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

Restrict access to the DBMS software libraries to accounts that require access based on job function.

Check Contents

Review permissions that control access to the DBMS software libraries. The software library location may be determined from vendor documentation or service/process executable paths.

Typically, only the DBMS software installation/maintenance account or system administrator (SA) account requires access to the software library for operational support such as backups. Any other accounts should be scrutinized and the reason for access documented. Accounts should have the least amount of privilege required to accomplish the job.

Below is one example for how to review accounts with access to software libraries for a Linux-based system:
cat /etc/group |grep -i dba
--Example output:
dba:x:102:

--take above number and input in below grep command
cat /etc/passwd |grep 102

If any accounts are returned that are not required and authorized to have access to the software library location do have access, this is a finding.

Vulnerability Number

V-270515

Documentable

False

Rule Version

O19C-00-007900

Severity Override Guidance

Review permissions that control access to the DBMS software libraries. The software library location may be determined from vendor documentation or service/process executable paths.

Typically, only the DBMS software installation/maintenance account or system administrator (SA) account requires access to the software library for operational support such as backups. Any other accounts should be scrutinized and the reason for access documented. Accounts should have the least amount of privilege required to accomplish the job.

Below is one example for how to review accounts with access to software libraries for a Linux-based system:
cat /etc/group |grep -i dba
--Example output:
dba:x:102:

--take above number and input in below grep command
cat /etc/passwd |grep 102

If any accounts are returned that are not required and authorized to have access to the software library location do have access, this is a finding.

Check Content Reference

M

Target Key

5672