IDMS must restrict the use of code that provides elevated privileges to specific instances.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-251639 | IDMS-DB-000690 | SV-251639r961359_rule | CCI-002233 | medium |
| Description | ||||
| When a user has elevated privileges, they may be able to deliberately or inadvertently make alterations to the DBMS structure or data. | ||||
| STIG | Date | |||
| CA IDMS Security Technical Implementation Guide | 2024-09-13 | |||
Details
Check Text (C-251639r961359_chk)
Review the system documentation, database, and DBMS security configuration (in SRTT and ESM), source code for DBMS internal logic, source code of external modules invoked by the DBMS, and source code of the application(s) using the database.
If elevation of DBMS privileges is utilized but not documented, this is a finding.
If elevation of DBMS privileges is documented, but not implemented as described in the documentation, this is a finding.
If the privilege-elevation logic can be invoked in ways other than intended, or in contexts other than intended, or by subjects/principals other than intended, this is a finding.
Fix Text (F-55028r807783_fix)
Determine where, when, how, and by what principals/subjects elevated privilege is needed.
Modify the database and DBMS security configuration (in SRTT and external security manager [ESM]), DBMS internal logic, external modules invoked by the DBMS, and the application(s) using the database, to ensure privilege elevation is used only as required.