OpenControls Logo

STIG Viewer

STIGViewer Support

IDMS must restrict the use of code that provides elevated privileges to specific instances.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-251639IDMS-DB-000690SV-251639r961359_ruleCCI-002233medium
Description
When a user has elevated privileges, they may be able to deliberately or inadvertently make alterations to the DBMS structure or data.
STIGDate
CA IDMS Security Technical Implementation Guide2024-09-13

Related Frameworks

1 mapping across 3 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

IAC-21.7Privilege Levels for Code Execution
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (17) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-3Access Enforcement
1.00
AC-3(4)Discretionary Access Control
1.00
AC-6(10)Prohibit Non-privileged Users from Executing Privileged Functions
1.00
AC-6(8)Privilege Levels for Code Execution
1.00
AC-6(9)Log Use of Privileged Functions
1.00
AU-3(1)Additional Audit Information
1.00
CM-5(6)Limit Library Privileges
1.00
CM-7Least Functionality
1.00
CM-7(2)Prevent Program Execution
1.00
CM-7(5)Authorized Software — Allow-by-exception
1.00

+7 more (top 10 by confidence shown)

CCI1 mapping
CCI-002233
1.00

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.