Oracle instance names must not contain Oracle version numbers.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-270521 | O19C-00-008600 | SV-270521r1112467_rule | CCI-000366 | medium |
| Description | ||||
| Service names may be discovered by unauthenticated users. If the service name includes version numbers or other database product information, a malicious user may use that information to develop a targeted attack. | ||||
| STIG | Date | |||
| Oracle Database 19c Security Technical Implementation Guide | 2025-06-24 | |||
Related Frameworks
4 paths across 3 frameworks
Related Frameworks
NIST 800-531 mapping
CM-6
1.00
- DISA · 1 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1712 mappings
3.4.1
1.00
- DISA · 1 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
- NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
3.4.2
1.00
- DISA · 1 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
- NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
CCI1 mapping
CCI-000366
1.00
- DISA · 1 · disa_xccdf · related
Details
Check Text (C-270521r1112467_chk)
If using a non-CDB database:
From SQL*Plus:
select instance_name, version from v$instance;
If using a CDB database:
To check the container database (CDB):
From SQL*Plus:
select instance_name, version from v$instance;
To check the pluggable databases (PDBs) within the CDB:
select name from v$pdbs;
Check Instance Name:
If the instance name returned references the Oracle release number, this is a finding.
Numbers used that include version numbers by coincidence are not a finding.
The database administrator (DBA) should be able to relate the significance of the presence of a digit in the SID.
Fix Text (F-74455r1064840_fix)
Follow the instructions in Oracle MetaLink Note 15390.1 (and related documents) to change the SID for the database without recreating the database to a value that does not identify the Oracle version.