CA IDMS Security Technical Implementation Guide
Rules, Groups, and Values defined within the XCCDF Benchmark
-
SRG-APP-000033-DB-000084
<GroupDescription></GroupDescription>Group -
SRG-APP-000001-DB-000031
<GroupDescription></GroupDescription>Group -
For interactive sessions, IDMS must limit the number of concurrent sessions for the same user to one or allow unlimited sessions.
<VulnDiscussion>Multiple interactive sessions can provide a way to cause a DoS attack against IDMS if a user ID and password were compromised...Rule Medium Severity -
SRG-APP-000023-DB-000001
<GroupDescription></GroupDescription>Group -
IDMS must support the implementation of an external security manager (ESM) to handle account management and user accesses, etc.
<VulnDiscussion>Internal security in a DBMS can be complex to implement and maintain with the increased possibility of no access or the wrong...Rule Medium Severity -
SRG-APP-000033-DB-000084
<GroupDescription></GroupDescription>Group -
IDMS must allow only authorized users to sign on to an IDMS CV.
<VulnDiscussion>Unauthorized users signing on to IDMS can pose varying amounts of risk depending upon the security of the IDMS resources in a...Rule High Severity -
SRG-APP-000033-DB-000084
<GroupDescription></GroupDescription>Group -
IDMS must enforce applicable access control policies, even after a user successfully signs on to CV.
<VulnDiscussion>Unless the DBMS is secured properly, there are innumerable ways that a system and its data can be compromised. The IDMS SRTT ...Rule High Severity -
IDMS must protect against the use of external request exits that change the userid to a shared id when actions are performed that may be audited.
<VulnDiscussion>Non-repudiation of actions taken is required in order to maintain data integrity. Examples of particular actions taken by ind...Rule Low Severity -
SRG-APP-000080-DB-000063
<GroupDescription></GroupDescription>Group -
IDMS must protect against the use of numbered exits that change the userid to a shared id.
<VulnDiscussion>Non-repudiation of actions taken is required to maintain data integrity. Examples of particular actions taken by individuals ...Rule Low Severity -
SRG-APP-000080-DB-000063
<GroupDescription></GroupDescription>Group -
IDMS must protect against the use of web-based applications that use generic IDs.
<VulnDiscussion>Web-based applications that allow a generic ID can be a door into IDMS allowing unauthorized changes whose authors may not be...Rule Low Severity -
SRG-APP-000080-DB-000063
<GroupDescription></GroupDescription>Group -
IDMS must protect against the use web services that do not require a sign on when actions are performed that may be audited.
<VulnDiscussion>IDMS web services provide a way for web-based applications to access an IDMS database. If not secured, the Web services inter...Rule Low Severity -
SRG-APP-000089-DB-000064
<GroupDescription></GroupDescription>Group -
IDMS must use the ESM to generate auditable records for resources when DoD-defined auditable events occur.
<VulnDiscussion>Audit records provide a tool to help research events within IDMS. IDMS does not produce audit records, but when using externa...Rule High Severity -
SRG-APP-000089-DB-000064
<GroupDescription></GroupDescription>Group -
IDMS must use the ESM to generate auditable records for commands and utilities when DoD-defined auditable events occur.
<VulnDiscussion>Audit records provide a tool to help research events within IDMS. IDMS itself does not produce audit records but, when extern...Rule High Severity
Node 2
The content of the drawer really is up to you. It could have form fields, definition lists, text lists, labels, charts, progress bars, etc. Spacing recommendation is 24px margins. You can put tabs in here, and can also make the drawer scrollable.