DISA STIGS Viewer

CA IDMS Security Technical Implementation Guide

Overview

Version Date Finding Count (74) Downloads
2 2024-09-13 CAT I (High): 5 CAT II (Medium): 59 CAT III (Low): 10 Excel JSON XML
Stig Description
This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.
Classified Public Sensitive  
I - Mission Critical Classified I - Mission Critical Public I - Mission Critical Sensitive II - Mission Critical Classified II - Mission Critical Public II - Mission Critical Sensitive III - Mission Critical Classified III - Mission Critical Public III - Mission Critical Sensitive

Findings - MAC III - Mission Critical Classified

Finding ID Severity Title Description
V-251654 High CA IDMS must use pervasive encryption to cryptographically protect the confidentiality and integrity of all information at rest in accordance with data owner requirements. This control is intended to address the confidentiality and integrity of information at rest in non-mobile devices and covers user information and system information. Information at rest refers to the state of information when it is located on a secondary storage device (e.g., disk drive, tape drive) within an organizational...
V-251600 High IDMS must use the ESM to generate auditable records for commands and utilities when DoD-defined auditable events occur. Audit records provide a tool to help research events within IDMS. IDMS itself does not produce audit records but, when external security is in place, records can be produced through the ESM. IDMS relies on the ESM to log organization-defined auditable events. To ensure that all secure actions are logged,...
V-251599 High IDMS must use the ESM to generate auditable records for resources when DoD-defined auditable events occur. Audit records provide a tool to help research events within IDMS. IDMS does not produce audit records, but when using external security, records can be produced through the ESM. IDMS relies on the ESM to log organization-defined auditable events. To ensure that all secure actions are logged, those actions must...
V-251585 High IDMS must enforce applicable access control policies, even after a user successfully signs on to CV. Unless the DBMS is secured properly, there are innumerable ways that a system and its data can be compromised. The IDMS SRTT is the basis for mitigating these problems.
V-251584 High IDMS must allow only authorized users to sign on to an IDMS CV. Unauthorized users signing on to IDMS can pose varying amounts of risk depending upon the security of the IDMS resources in an IDMS CV. Until the IDMS sign-on resource type (SGON) is secured anyone can sign on to IDMS. This risk can be mitigated by securing the SGON resource.
V-251656 Medium CA IDMS must implement NIST FIPS 140-2 validated cryptographic modules to protect data-in-transit. Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated. It is the responsibility of the data owner...
V-251655 Medium The DBMS must associate organization-defined types of security labels having organization-defined security label values with information in process. Without the association of security labels to information, there is no basis for the DBMS to make security-related access-control decisions. Security labels are abstractions representing the basic properties or characteristics of an entity (e.g., subjects and objects) with respect to safeguarding information. These labels are typically associated with internal data...
V-251653 Medium The DBMS must provide non-privileged users with error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries. Any DBMS or associated application providing too much information in error messages on the screen or printout risks compromising the data and security of the system. The structure and content of error messages need to be carefully considered by the organization and development team. Databases can inadvertently provide a wealth...
V-251652 Medium The DBMS must develop a procedure to limit the number of concurrent sessions to an organization-defined number per user for all accounts and/or account types. Database management includes the ability to control the number of users and user sessions utilizing a DBMS. Unlimited concurrent connections to the DBMS could allow a successful Denial of Service (DoS) attack by exhausting connection resources; and a system can also fail or be degraded by an overload of legitimate...
V-251650 Medium Maintenance for security-related software updates for CA IDMS modules must be provided. When a problem is found in IDMS, corrective maintenance is published to correct the problem (including security related problems). Published fixes should be applied to the IDMS system to correct any problems found.
V-251649 Medium IDMS must check for invalid data and behave in a predictable manner when encountered. A common vulnerability is unplanned behavior when invalid inputs are received. This requirement guards against adverse or unintended system behavior caused by invalid inputs, where information system responses to the invalid input may be disruptive or cause the system to fail into an unsafe state. The behavior will be derived...
V-251648 Medium The storage used for data collection by CA IDMS Server and CA IDMS Web Services must be protected from online display and update. Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. Use of this requirement will be limited to situations where the...
V-251647 Medium The storage used for data collection by CA IDMS web services must be protected. Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. Use of this requirement will be limited to situations where the...
V-251646 Medium The cache table procedures and views used for performance enhancements for dynamic SQL must be protected. Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. Use of this requirement will be limited to situations where the...
V-251645 Medium The system storage used for data collection by the CA IDMS server must be protected. Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. Use of this requirement will be limited to situations where the...
V-251644 Medium CA IDMS must prevent user code from issuing selected SVC privileged functions. If an SVC is used to facilitate interpartition communication for online applications executing under other DC systems, batch application programs, and programs executed under TP monitors other than DC when running on the same LPAR, privileged functions of the SVC can be protected from these entities that do not run...
V-251643 Medium CA IDMS must protect system and user code and storage from corruption by user programs. Database management systems can maintain separate execution domains for each executing process by assigning each process a separate address space. Each process has a distinct address space so that communication between processes is controlled through the security functions, and one process cannot modify the executing code of another process. Maintaining...
V-251642 Medium CA IDMS must protect the system code and storage from corruption by user programs. Database management systems can maintain separate execution domains for each executing process by assigning each process a separate address space. Each process has a distinct address space so that communication between processes is controlled through the security functions, and one process cannot modify the executing code of another process. Maintaining...
V-251641 Medium IDMS terminal and lines that are not secure must be disabled. Use of nonsecure network functions, ports, protocols, and services exposes the system to avoidable threats.
V-251640 Medium CA IDMS programs that can be run through a CA IDMS CV must be defined to the CV. The ability to add programs to be executed under IDMS can be a problem if malicious programs are added. CA IDMS must prevent installation of unauthorized programs and the ability to dynamically register new programs and tasks.
V-251639 Medium IDMS must restrict the use of code that provides elevated privileges to specific instances. When a user has elevated privileges, they may be able to deliberately or inadvertently make alterations to the DBMS structure or data.
V-251638 Medium IDMS must protect its user catalogs and system dictionaries to prevent unauthorized users from bypassing or updating security settings. Unauthorized access to user profiles, dictionaries, and user catalogs provides the ability to damage the IDMS system.
V-251637 Medium IDMS must prevent unauthorized users from executing certain privileged commands that can be used to change the runtime IDMS environment. Ensure that a subset DCMT commands are secured so that only those with the appropriate authority are able to execute them. Access to these DCMT commands can allow a user to circumvent defined security policies and procedures, and to make other detrimental changes to the CV environment.
V-251636 Medium IDMS must prevent users without the appropriate access from executing privileged functions or tasks within the IDMS environment. In general, all functions within IDMS can be controlled, therefore it is up to the IDMS system administrator to determine which functions or tasks are secured or require proper authorization. Any function within the IDMS environment can be considered privileged if the administrator deems it appropriate. Access to different functions...
V-251635 Medium CA IDMS CV must supply logout functionality to allow the user to implicitly terminate a batch external request unit when the batch job abnormally terminates. IDMS must provide a facility by which an inactive user session may be terminated after a predetermined period of time.
V-251634 Medium CA IDMS CV must supply logout functionality to allow the user to implicitly terminate an external run-unit when a database request has not been made in an organizationally prescribed time frame. If a user cannot explicitly end a DBMS session, the session may remain open and be exploited by an attacker; this is referred to as a zombie session. Such logout may be explicit or implicit. Examples of explicit logouts are: clicking on a "Log Out" link or button in the...
V-251633 Medium CA IDMS CV must supply logout functionality to allow the user to implicitly terminate a session by disconnecting or ending before an explicit logout. If a user cannot explicitly end a DBMS session, the session may remain open and be exploited by an attacker; this is referred to as a zombie session. Such logouts may be explicit or implicit. Examples of explicit logouts are: clicking on a "Log Out" link or button in the...
V-251632 Medium CA IDMS CV must supply logout functionality to allow the user to implicitly terminate a session initiated by the terminal user. If a user does not sign off a terminal after use, it can be used for illegitimate purposes. The IDMS RESOURCE TIMEOUT INTERVAL allows the organization to set a limit to the amount of time it can be left unattended.
V-251631 Medium CA IDMS must automatically terminate a task or session after organization-defined conditions or trigger events of time waiting to get a resource and/or time of inactivity. A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational information system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions. Session termination ends all processes associated with a...
V-251630 Medium CA IDMS must automatically terminate an external run-unit after organization-defined conditions or trigger events of time waiting to issue a database request. Inactive sessions, such as a logged on user who leaves their terminal, may give a bad actor access to the system.
V-251629 Medium CA IDMS must automatically terminate a batch external request unit after organization-defined conditions or trigger events after the batch program abnormally terminates. A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational information system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions. Session termination ends all processes associated with a...
V-251628 Medium CA IDMS must automatically terminate a terminal session after organization-defined conditions or trigger events of terminal inactivity time. A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational information system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions. Session termination ends all processes associated with a...
V-251627 Medium Custom database code and associated application code must reveal detailed error messages only to the Information System Security Officer (ISSO), Information System Security manager (ISSM), Systems Administrator (SA), and Database Administrator (DBA). Detailed error messages issued by custom or user-written code can possibly give too much detail to the users. This code should be examined to ensure that this does not happen.
V-251626 Medium IDMS must reveal security-related messages only to authorized users. Error messages issued to non-privileged users may have contents that should be considered confidential. IDMS should be configured so that these messages are not issued to those users.
V-251625 Medium Custom database code and associated application code must not contain information beyond what is needed for troubleshooting. Error codes issued by custom code could provide more information than needed for problem resolution and should be vetted to make sure this does not occur.
V-251624 Medium IDMS must suppress security-related messages so that no information is returned that can be exploited. Error messages issued to non-privileged users may have contents that should be considered confidential. IDMS should be configured so that these messages are not issued to those users.
V-251623 Medium CA IDMS and associated applications, when making use of dynamic code execution, must scan input data for invalid values that may indicate a code injection attack. When the use of dynamic SQL is necessary, the code should be written so that the invalid data can be found and the appropriate action taken.
V-251622 Medium CA IDMS must limit use of IDMS server used in issuing dynamic statements from client applications circumstances determined by the organization. Server tasks can execute dynamic SQL code and should be protected.
V-251621 Medium CA IDMS must limit the use of dynamic statements in applications, procedures, and exits to circumstances determined by the organization. Dynamic SQL statements are compiled at runtime and, if manipulated by an unauthorized user, can produce an innumerable array of undesired results. These statements should not be used casually.
V-251620 Medium CA IDMS must permit the use of dynamic code execution only in circumstances determined by the organization and limit use of online and batch command facilities from which dynamic statements can be issued. The IDMS Common Facilities (BCF and OCF) can execute commands that can make updates to IDMS, and their use should be protected.
V-251619 Medium IDMS must check the validity of all data input unless the organization says otherwise. Invalid user input occurs when a user inserts data or characters into an application's data entry fields and the application is unprepared to process that data. This results in unanticipated application behavior, potentially leading to an application or information system compromise. Invalid user input is one of the primary methods...
V-251618 Medium IDMS must prevent unauthorized and unintended information transfer via database buffers. The purpose of this control is to prevent information, including encrypted representations of information, produced by the actions of a prior user/role (or the actions of a process acting on behalf of a prior user/role) from being available to any current user/role (or current process) that obtains access to a...
V-251617 Medium CA IDMS must isolate the security manager to which users, groups, roles are assigned authorities/permissions to resources. An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform security functions. Security functions are the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the...
V-251615 Medium The DBMS must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users). Non-organizational users include all information system users other than organizational users, which include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors, guest researchers, individuals from allied nations). Non-organizational users must be uniquely identified and authenticated for all accesses other than those accesses explicitly...
V-251613 Medium DBMS authentication using passwords must be avoided. Passwords that are easy to guess open a vulnerability allowing an unauthorized user to potentially gain access to the DBMS. IDMS uses the External Security Manager (ESM) to enforce complexity and lifetime standards.
V-251612 Medium The IDMS environment must require sign-on for users and restrict them to only authorized functions. To ensure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system. Organizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and any processes acting on behalf of...
V-251611 Medium IDMS nodes, lines, and pterms must be protected from unauthorized use. In order 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....
V-251607 Medium CA IDMS must secure the ability to create, alter, drop, grant, and revoke user and/or system profiles to users or groups. Even when using an external security manager (ESM), IDMS system and user profiles which reside in an IDMS user catalog may be assigned to users or groups. The ability to administer user and system profiles must be secured.
V-251606 Medium The online debugger which can change programs and storage in the CA IDMS address space must be secured. If the DBMS were to allow any user to make changes to database structure or logic, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. Accordingly, only qualified and authorized individuals must be allowed to obtain access...
V-251605 Medium Database utilities must be secured in CA IDMS and permissions given to appropriate role(s)/groups(s) in the external security manager (ESM). IDMS has tasks that are used to perform necessary maintenance, but in the wrong hands could damage the integrity of the DBMS. Tasks that can change database structure must be protected. Satisfies: SRG-APP-000133-DB-000362, SRG-APP-000380-DB-000360
V-251604 Medium Databases must be secured to protect from structural changes. Database objects, like areas and run units, can be changed or deleted if not protected. Steps must be taken to secure these objects via the external security manager (ESM). Satisfies: SRG-APP-000133-DB-000362, SRG-APP-000380-DB-000360
V-251603 Medium The commands that allow dynamic definitions of PROGRAM/TASK and the dynamic varying of memory must be secured. IDMS provides commands that can change memory, the attributes of programs, or tasks and are meant for use by the appropriate administrators. These commands must be protected from use by the wrong personnel. Satisfies: SRG-APP-000133-DB-000362, SRG-APP-000380-DB-000360, SRG-APP-000378-DB-000365
V-251602 Medium The programs that can be run through a CA IDMS CV must be defined to the CV to prevent installation of unauthorized programs; must have the ability to dynamically register new programs; and must have the ability to secure tasks. The IDMS SYSGEN must be protected against unauthorized changes. Satisfies: SRG-APP-000133-DB-000362, SRG-APP-000378-DB-000365
V-251601 Medium Database objects in an IDMS environment must be secured to prevent privileged actions from being performed by unauthorized users. If database objects like areas, schemas, and run units are not secured, they may be changed or deleted by unauthorized users.
V-251593 Medium All installation-delivered IDMS DC-Administrator-level programs must be properly secured. DC Administrator-level programs that are not secured may allow unauthorized users to use them to access and manipulate various resources within the DBMS. Satisfies: SRG-APP-000033-DB-000084, SRG-APP-000211-DB-000122
V-251592 Medium All installation-delivered IDMS Database-Administrator-level programs must be properly secured. DBA-level programs that are not secured may allow unauthorized users to use them to access and manipulate various resources within the DBMS. Satisfies: SRG-APP-000033-DB-000084, SRG-APP-000211-DB-000122
V-251591 Medium All installation-delivered IDMS Developer-level Programs must be properly secured. Developer-level programs that are not secured may allow unauthorized users to access and manipulate various resources within the DBMS. Satisfies: SRG-APP-000033-DB-000084, SRG-APP-000211-DB-000122
V-251590 Medium All installation-delivered IDMS User-level programs must be properly secured. If user-level programs are not secured, then unauthorized users may use them to access and manipulate various resources within the DBMS. Satisfies: SRG-APP-000033-DB-000084, SRG-APP-000211-DB-000122
V-251589 Medium All installation-delivered IDMS DCADMIN-level tasks must be properly secured. If DC Administrator-level tasks are not secured, any user logged on to IDMS may use them to access and manipulate various resources within the DBMS. This can be mitigated using the proper entries in the SRTT. Satisfies: SRG-APP-000033-DB-000084, SRG-APP-000211-DB-000122
V-251588 Medium All installation-delivered IDMS DBADMIN-level tasks must be properly secured. DBA-level tasks that are not secured may allow anyone who signs on to IDMS to use them to access and manipulate various resources within the DBMS. Satisfies: SRG-APP-000033-DB-000084, SRG-APP-000211-DB-000122
V-251587 Medium All installation-delivered IDMS DEVELOPER-level tasks must be properly secured. Developer-level tasks that are not secured may allow anyone who signs on to IDMS to use them to access and manipulate various resources within the DBMS. Satisfies: SRG-APP-000033-DB-000084, SRG-APP-000211-DB-000122
V-251586 Medium All installation-delivered IDMS USER-level tasks must be properly secured. User-level tasks that are not secured may allow anyone who signs on to IDMS to use them to access and manipulate various resources within the DBMS. Satisfies: SRG-APP-000033-DB-000084, SRG-APP-000211-DB-000122
V-251583 Medium IDMS must support the implementation of an external security manager (ESM) to handle account management and user accesses, etc. Internal security in a DBMS can be complex to implement and maintain with the increased possibility of no access or the wrong access to a needed resource. IDMS can be configured to use an ESM as the security repository allowing access rules to be added to already-known users.
V-251582 Medium For interactive sessions, IDMS must limit the number of concurrent sessions for the same user to one or allow unlimited sessions. Multiple interactive sessions can provide a way to cause a DoS attack against IDMS if a user ID and password were compromised. Not allowing multiple sign-ons can mitigate the risk of malicious attacks using multiple sessions for a user.
V-251616 Low IDMS executing in a local mode batch environment must be able to manually recover or restore database areas affected by failed transactions. Local mode update jobs can either use local mode journaling or perform a backup of the database prior to executing the local mode updates. Local mode journaling could be completed if the database is too large to back up in a reasonable amount of time. To use local mode journals...
V-251614 Low Passwords sent through ODBC/JDBC must be encrypted. Unencrypted passwords transmitted from ODBC and JDBC may be intercepted to prevent their being intercepted in a plain-text format.
V-251610 Low IDMS components that cannot be uninstalled must be disabled. DBMSs must adhere to the principles of least functionality by providing only essential capabilities. At installation, all CA IDMS products are installed but can be disabled (i.e., forced to fail if invoked).
V-251609 Low Default demonstration and sample databases, database objects, and applications must be removed. Information systems 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 (e.g., key missions, functions). It is detrimental for software products to provide, or install by default, functionality exceeding requirements...
V-251608 Low The EMPDEMO databases, database objects, and applications must be removed. Demonstration and sample database objects and applications present publicly known attack points for malicious users. These demonstration and sample objects are meant to provide simple examples of coding specific functions, and are not developed to prevent vulnerabilities from being introduced to the DBMS and host system.
V-251598 Low IDMS must protect against the use web services that do not require a sign on when actions are performed that may be audited. IDMS web services provide a way for web-based applications to access an IDMS database. If not secured, the Web services interface could be used to reveal or change sensitive data.
V-251597 Low IDMS must protect against the use of web-based applications that use generic IDs. Web-based applications that allow a generic ID can be a door into IDMS allowing unauthorized changes whose authors may not be determined.
V-251596 Low IDMS must protect against the use of numbered exits that change the userid to a shared id. Non-repudiation of actions taken is required to maintain data integrity. Examples of particular actions taken by individuals include creating information, sending a message, approving information (e.g., indicating concurrence or signing a contract), and receiving a message. Non-repudiation protects against later claims by a user of not having created, modified, or...
V-251595 Low 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. Non-repudiation of actions taken is required in order to maintain data integrity. Examples of particular actions taken by individuals include creating information, sending a message, approving information (e.g., indicating concurrence or signing a contract), and receiving a message. Non-repudiation protects against later claims by a user of not having created,...
V-251594 Low IDMS must protect against the use of default userids. Default sign-ons can be used by individuals to perform adverse actions anonymously.