| V-251582 | | 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 s... |
| V-251583 | | 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 resou... |
| V-251586 | | 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.
S... |
| V-251587 | | 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 DBM... |
| V-251588 | | 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.
Sa... |
| V-251589 | | 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. T... |
| V-251590 | | 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: S... |
| V-251591 | | 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... |
| V-251592 | | 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.
Satisfie... |
| V-251593 | | 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 DB... |
| V-251601 | | 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-251602 | | 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-251603 | | 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 com... |
| V-251604 | | 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 s... |
| V-251605 | | 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 da... |
| V-251606 | | 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 appr... |
| V-251607 | | 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 gro... |
| V-251611 | | 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... |
| V-251612 | | 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... |
| V-251613 | | 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 Sec... |
| V-251615 | | 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 t... |
| V-251617 | | 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.
Sec... |
| V-251618 | | 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/rol... |
| V-251619 | | 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 ... |
| V-251620 | | 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-251621 | | 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. The... |
| V-251622 | | 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-251623 | | 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-251624 | | 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 messag... |
| V-251625 | | 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 oc... |
| V-251626 | | 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 messag... |
| V-251627 | | 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 t... |
| V-251628 | | 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 organizatio... |
| V-251629 | | 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 organizatio... |
| V-251630 | | 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-251631 | | 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 organizatio... |
| V-251632 | | 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... |
| V-251633 | | 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.
... |
| V-251634 | | 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.
... |
| V-251635 | | 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-251636 | | 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... |
| V-251637 | | 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 comma... |
| V-251638 | | 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-251639 | | 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-251640 | | 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 unauthori... |
| V-251641 | | 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-251642 | | 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. Eac... |
| V-251643 | | 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. Eac... |
| V-251644 | | 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... |
| V-251645 | | 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 agg... |
| V-251646 | | 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 agg... |
| V-251647 | | 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 agg... |
| V-251648 | | 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 agg... |
| V-251649 | | 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 c... |
| V-251650 | | 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 sho... |
| V-251652 | | 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 DB... |
| V-251653 | | 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... |
| V-251655 | | 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... |
| V-251656 | | 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 cryptogr... |
| V-251594 | | IDMS must protect against the use of default userids. | Default sign-ons can be used by individuals to perform adverse actions anonymously.... |
| V-251595 | | 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... |
| V-251596 | | 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 informat... |
| V-251597 | | 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-251598 | | 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 rev... |
| V-251608 | | 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 ob... |
| V-251609 | | 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 no... |
| V-251610 | | 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 install... |
| V-251614 | | 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-251616 | | 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... |
| V-251584 | | 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... |
| V-251585 | | 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 mitigati... |
| V-251599 | | 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 b... |
| V-251600 | | 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, ... |
| V-251654 | | 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 sys... |
