| Checked | Name | Title |
|---|
| ☐ | SV-251582r960735_rule | For interactive sessions, IDMS must limit the number of concurrent sessions for the same user to one or allow unlimited sessions. |
| ☐ | SV-251583r1043176_rule | IDMS must support the implementation of an external security manager (ESM) to handle account management and user accesses, etc. |
| ☐ | SV-251584r1137654_rule | IDMS must allow only authorized users to sign on to an IDMS CV. |
| ☐ | SV-251585r1137654_rule | IDMS must enforce applicable access control policies, even after a user successfully signs on to CV. |
| ☐ | SV-251586r1137654_rule | All installation-delivered IDMS USER-level tasks must be properly secured. |
| ☐ | SV-251587r1137654_rule | All installation-delivered IDMS DEVELOPER-level tasks must be properly secured. |
| ☐ | SV-251588r1137654_rule | All installation-delivered IDMS DBADMIN-level tasks must be properly secured. |
| ☐ | SV-251589r1137654_rule | All installation-delivered IDMS DCADMIN-level tasks must be properly secured. |
| ☐ | SV-251590r1137654_rule | All installation-delivered IDMS User-level programs must be properly secured. |
| ☐ | SV-251591r1137654_rule | All installation-delivered IDMS Developer-level Programs must be properly secured. |
| ☐ | SV-251592r1137654_rule | All installation-delivered IDMS Database-Administrator-level programs must be properly secured. |
| ☐ | SV-251593r1137654_rule | All installation-delivered IDMS DC-Administrator-level programs must be properly secured. |
| ☐ | SV-251594r960864_rule | IDMS must protect against the use of default userids. |
| ☐ | SV-251595r960864_rule | 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. |
| ☐ | SV-251596r960864_rule | IDMS must protect against the use of numbered exits that change the userid to a shared id. |
| ☐ | SV-251597r960864_rule | IDMS must protect against the use of web-based applications that use generic IDs. |
| ☐ | SV-251598r960864_rule | IDMS must protect against the use web services that do not require a sign on when actions are performed that may be audited. |
| ☐ | SV-251599r1212353_rule | IDMS must use the ESM to generate auditable records for resources when DOD-defined auditable events occur. |
| ☐ | SV-251600r960879_rule | IDMS must use the ESM to generate auditable records for commands and utilities when DoD-defined auditable events occur. |
| ☐ | SV-251601r960960_rule | Database objects in an IDMS environment must be secured to prevent privileged actions from being performed by unauthorized users. |
| ☐ | SV-251602r960960_rule | 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. |
| ☐ | SV-251603r960960_rule | The commands that allow dynamic definitions of PROGRAM/TASK and the dynamic varying of memory must be secured. |
| ☐ | SV-251604r960960_rule | Databases must be secured to protect from structural changes. |
| ☐ | SV-251605r960960_rule | Database utilities must be secured in CA IDMS and permissions given to appropriate role(s)/groups(s) in the external security manager (ESM). |
| ☐ | SV-251606r960960_rule | The online debugger which can change programs and storage in the CA IDMS address space must be secured. |
| ☐ | SV-251607r960960_rule | CA IDMS must secure the ability to create, alter, drop, grant, and revoke user and/or system profiles to users or groups. |
| ☐ | SV-251608r960963_rule | The EMPDEMO databases, database objects, and applications must be removed. |
| ☐ | SV-251609r960963_rule | Default demonstration and sample databases, database objects, and applications must be removed. |
| ☐ | SV-251610r960963_rule | IDMS components that cannot be uninstalled must be disabled. |
| ☐ | SV-251611r1043177_rule | IDMS nodes, lines, and pterms must be protected from unauthorized use. |
| ☐ | SV-251612r1051115_rule | The IDMS environment must require sign-on for users and restrict them to only authorized functions. |
| ☐ | SV-251613r981946_rule | DBMS authentication using passwords must be avoided. |
| ☐ | SV-251614r961029_rule | Passwords sent through ODBC/JDBC must be encrypted. |
| ☐ | SV-251615r961053_rule | The DBMS must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users). |
| ☐ | SV-251616r961122_rule | IDMS executing in a local mode batch environment must be able to manually recover or restore database areas affected by failed transactions. |
| ☐ | SV-251617r961131_rule | CA IDMS must isolate the security manager to which users, groups, roles are assigned authorities/permissions to resources. |
| ☐ | SV-251618r1137657_rule | IDMS must prevent unauthorized and unintended information transfer via database buffers. |
| ☐ | SV-251619r961158_rule | IDMS must check the validity of all data input unless the organization says otherwise. |
| ☐ | SV-251620r961158_rule | 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. |
| ☐ | SV-251621r961158_rule | CA IDMS must limit the use of dynamic statements in applications, procedures, and exits to circumstances determined by the organization. |
| ☐ | SV-251622r961158_rule | CA IDMS must limit use of IDMS server used in issuing dynamic statements from client applications circumstances determined by the organization. |
| ☐ | SV-251623r961158_rule | 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. |
| ☐ | SV-251624r961167_rule | IDMS must suppress security-related messages so that no information is returned that can be exploited. |
| ☐ | SV-251625r961167_rule | Custom database code and associated application code must not contain information beyond what is needed for troubleshooting. |
| ☐ | SV-251626r961170_rule | IDMS must reveal security-related messages only to authorized users. |
| ☐ | SV-251627r961170_rule | 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). |
| ☐ | SV-251628r1043182_rule | CA IDMS must automatically terminate a terminal session after organization-defined conditions or trigger events of terminal inactivity time. |
| ☐ | SV-251629r1043182_rule | CA IDMS must automatically terminate a batch external request unit after organization-defined conditions or trigger events after the batch program abnormally terminates. |
| ☐ | SV-251630r1043182_rule | CA IDMS must automatically terminate an external run-unit after organization-defined conditions or trigger events of time waiting to issue a database request. |
| ☐ | SV-251631r1043182_rule | 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. |
| ☐ | SV-251632r961224_rule | CA IDMS CV must supply logout functionality to allow the user to implicitly terminate a session initiated by the terminal user. |
| ☐ | SV-251633r961224_rule | CA IDMS CV must supply logout functionality to allow the user to implicitly terminate a session by disconnecting or ending before an explicit logout. |
| ☐ | SV-251634r961224_rule | 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. |
| ☐ | SV-251635r961224_rule | 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. |
| ☐ | SV-251636r961353_rule | IDMS must prevent users without the appropriate access from executing privileged functions or tasks within the IDMS environment. |
| ☐ | SV-251637r961353_rule | IDMS must prevent unauthorized users from executing certain privileged commands that can be used to change the runtime IDMS environment. |
| ☐ | SV-251638r961353_rule | IDMS must protect its user catalogs and system dictionaries to prevent unauthorized users from bypassing or updating security settings. |
| ☐ | SV-251639r961359_rule | IDMS must restrict the use of code that provides elevated privileges to specific instances. |
| ☐ | SV-251640r961461_rule | CA IDMS programs that can be run through a CA IDMS CV must be defined to the CV. |
| ☐ | SV-251641r961470_rule | IDMS terminal and lines that are not secure must be disabled. |
| ☐ | SV-251642r1137659_rule | CA IDMS must protect the system code and storage from corruption by user programs. |
| ☐ | SV-251643r1137659_rule | CA IDMS must protect system and user code and storage from corruption by user programs. |
| ☐ | SV-251644r1137659_rule | CA IDMS must prevent user code from issuing selected SVC privileged functions. |
| ☐ | SV-251645r961638_rule | The system storage used for data collection by the CA IDMS server must be protected. |
| ☐ | SV-251646r961638_rule | The cache table procedures and views used for performance enhancements for dynamic SQL must be protected. |
| ☐ | SV-251647r961638_rule | The storage used for data collection by CA IDMS web services must be protected. |
| ☐ | SV-251648r961638_rule | The storage used for data collection by CA IDMS Server and CA IDMS Web Services must be protected from online display and update. |
| ☐ | SV-251649r961656_rule | IDMS must check for invalid data and behave in a predictable manner when encountered. |
| ☐ | SV-251650r1137667_rule | Maintenance for security-related software updates for CA IDMS modules must be provided. |
| ☐ | SV-251652r960735_rule | 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. |
| ☐ | SV-251653r961167_rule | 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. |
| ☐ | SV-251654r1028319_rule | CA IDMS must use pervasive encryption to cryptographically protect the confidentiality and integrity of all information at rest in accordance with data owner requirements. |
| ☐ | SV-251655r1138541_rule | The DBMS must associate organization-defined types of security labels having organization-defined security label values with information in process. |
| ☐ | SV-251656r1212354_rule | CA IDMS must implement NIST FIPS 140-3 validated cryptographic modules to protect data in transit. |
STIGQter: STIG Summary: