STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to Oracle Database 19c Security Technical Implementation Guide

V-270522

CAT II (Medium)

Fixed user and PUBLIC Database links must be authorized for use.

Rule ID

SV-270522r1115956_rule

STIG

Oracle Database 19c Security Technical Implementation Guide

Version

V1R5

CCIs

CCI-000366

Discussion

Database links define connections that may be used by the local Oracle database to access remote Oracle databases (homogenous links) and non-Oracle Databases (heterogeneous links). These links provide a means for a compromise to the local database to spread to remote databases and for a compromise of a remote database to the local database in a distributed database environment. Limiting or eliminating the use of database links, where they are not required to support the operational system, can help isolate compromises, mitigate risk, and reduce the potential attack surface.

Check Content

If using a non-CDB database:
Use the following query to get a list of database links.

From SQL*Plus:

select owner||': '||db_link from dba_db_links;

If using a CDB database:
Use the following query to get a list of database links.

select con_id_to_con_name(con_id) con_id, owner, db_link, username, host from cdb_db_links order by 1,2,3;

Check Results:

If no rows are returned from the first SQL statement, this check is not a finding.

If there are rows returned, verify the database links are required. If they are required and exist, this is not a finding.

Fix Text

Document all authorized connections from the database to remote databases.

Remove all unauthorized remote database connection definitions from the database.

From SQL*Plus:

drop database link [link name];
OR
drop public database link [link name];

Review remote database connection definitions periodically and confirm their use is still required and authorized.