Oracle Database 11.2g Security Technical Implementation Guide

The Oracle Database 11.2g Security Technical Implementation Guide (V1 R19) has 203 STIG checks. New to STIG checklists? Read What is a STIG checklist?, CKL vs CKLB, and STIG vs SCAP benchmark.

Find STIG checks

203STIG checks

Search filters this STIG's checks locally. Separate terms must all match (use quotes for an exact phrase). A search you ran on the Search page carries over here.

Severity

Version

V1 · R19

CurrentPublished Fri Jul 24 2020

Remote database or other external access must use fully-qualified names.

Oracle Database 11.2g Security Technical Implementation Guide

Assessment Title

Rule Text

Remote database or other external access must use fully-qualified names.

Description

Discussion Text

The Oracle GLOBAL_NAMES parameter is used to set the requirement for database link names to be the same name as the remote database whose connection they define. By using the same name for both, ambiguity is avoided and unauthorized or unintended connections to remote databases are less likely.

New to STIG checklists? Read What is a STIG checklist? and CKL vs CKLB.

Objective

V-54071

Rule

SV-68311r1_rule

Severity

medium

Rule Version

O112-BP-026300

Documentable

false

IA Controls

NIST SP 800-53

Rev 5

Assessment Procedure

Check Text

From SQL*Plus:

select value from v$parameter where name = 'global_names';

If the value returned is FALSE, this is a Finding.

Implementation Procedure

Fix Text

From SQL*Plus:

alter system set global_names = TRUE scope = spfile;

NOTE: This parameter, if changed, will affect all currently defined Oracle database links.

The above SQL*Plus command will set the parameter to take effect at next system startup.

STIG check 194 of 203 in the Oracle Database 11.2g STIG checklist

← Previous · V-54069Changes to DBMS security labels must be audited.Next · V-54073 →The /diag subdirectory under the directory assigned to the DIAGNOSTIC_DEST parameter must be protected from unauthorized access.