Detections
Analytics
O19C-00-013500 - Oracle Database must be configured to prohibit or restrict the use of organization-defined functions, ports, protocols, and/or services, as defined in the Ports, Protocols, and Services Management Category Assurance List (PPSM CAL) and vulnerability assessments.
Information
To prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols/services on information systems.Applications are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., email and web services); however, doing so increases risk over limiting the services provided by any one component.
To support the requirements and principles of least functionality, the application must support the organizational requirements providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues.
Database Management Systems using ports, protocols, and services deemed unsafe are open to attack through those ports, protocols, and services. This can allow unauthorized access to the database and through the database to other components of the information system.
Satisfies: SRG-APP-000142-DB-000094, SRG-APP-000383-DB-000364
NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.
Solution
Disable functions, ports, protocols, and services that are not approved.- - - - -
Change the SQLNET.ora, LISTENER.ora, and TNSNAMES.ora files to reflect the proper use of ports, protocols, and services that are approved at the site.
If changes to the Listener are made, the files associated with the Listener must be reloaded by issuing the following commands at the Unix/Linux or Windows prompt.
Issue the command to verify what the current status is:
$ lsnrctl stat
Load the new file that was corrected to reflect site-specific requirements:
$ lsnrctl reload
Check the status again to verify that the changes have taken place:
$ lsnrctl stat
See Also
https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_Oracle_Database_19c_V1R1_STIG.zip
Item Details
Audit Name: DISA Oracle Database 19c STIG v1r1 Database
Category: CONFIGURATION MANAGEMENT
References: 800-53|CM-7(1)(b), 800-53|CM-7b., CAT|II, CCI|CCI-000382, CCI|CCI-001762, Rule-ID|SV-270558r1065283_rule, STIG-ID|O19C-00-013500, Vuln-ID|V-270558
Plugin: OracleDB
Control ID: 23a782816bf78c6f3582efec11e624ced5666d7d2b7d49190b729868ff6d29c2