STIGQter: STIG Summary: CA IDMS Security Technical Implementation Guide Version: 2 Release: 2 Benchmark Date: 01 Jul 2026:

CA IDMS must use pervasive encryption to cryptographically protect the confidentiality and integrity of all information at rest in accordance with data owner requirements.

DISA Rule

SV-251654r1028319_rule

Vulnerability Number

V-251654

Group Title

SRG-APP-000428-DB-000386

Rule Version

IDMS-DB-000930

Severity

CAT I

CCI(s)

• CCI-000119 - Review and update the current audit and accountability policy on an organization-defined frequency.
• CCI-002476 - Implement cryptographic mechanisms to prevent unauthorized disclosure of organization-defined information at rest on organization-defined system components.

Weight

10

Fix Recommendation

Enable pervasive encryption to protect data at rest:

1. Query system programmers, DBAs, and security team members as needed to determine SMS data and storage classes and data set key labels to use
2. Convert the desired database to a VSAM cluster.
a. If necessary, expand the page size of the area(s) current files. The optimal page size is eight bytes less than the VSAM control interval size.
b. Alter the file definition to change its access method and then generate, punch, and link all DMCLs in which the file's segment is included. Optionally, specify a new database name or other location
information
c. Allocate the new database file(s).

3. Modify the CV and batch JCL to reference the new VSAM data set(s).

4. Using the appropriate OS utility, copy the original database file(s) to the new, VSAM database file(s).

Note that the actual data encryption takes place when the database is written to or read from.

Check Contents

If this CA IDMS has no requirement for confidentiality and integrity of all information at rest in accordance with the data owners requirements, this not applicable.

If required files are not defined as a VSAM dataset this is a finding.

Perform the following for the VSAM dataset

1. LISTC ENT('dsn') ALL"

Where "dsn" is the DSNAME of the cluster; review the ATTRIBUTES section of the output to ensure that the database is defined as NONINEXED (the cluster is an ESDS). If not, this is a finding.

2. In the IDCAMS LISTC output, look for the SMSDATA section. If none is found this is a finding.
Otherwise, find the "DATACLASS" name and query the systems programmer to ensure that the SMS data class specifies "Extended Format" but does not specify "Extended Addressing". If not, this is a finding.

3. In the IDCAMS LISTC output:
Find the "STORAGECLASS" and query the systems programmer to ensure it supports extended format VSAM dataset. If not, this is a finding.

4. Confirm that the database(s) have a data set key label. Places to check for a data set key label:
a. In the SMS data class definition by reviewing the entry for the appropriate data class in ISMF
b. In the output of an IDCAMS LISTC in the ENCRYPTIONDATA section. If "DATA SET ENCRYPTION" is "YES", then the label will be displayed after "DATA SET KEY LABEL".
c. The key label may be assigned through the ESM. Query the security team to determine if this is the case.

5. The database(s) must be defined in the DMCL as "VSAM". Run "IDMSLOOK" to print the contents of the DMCL and look for the desired database(s). If the TYPE column is not "VSAM", this is a finding.

Vulnerability Number

V-251654

Documentable

False

Rule Version

IDMS-DB-000930

Severity Override Guidance

If this CA IDMS has no requirement for confidentiality and integrity of all information at rest in accordance with the data owners requirements, this not applicable.

If required files are not defined as a VSAM dataset this is a finding.

Perform the following for the VSAM dataset

1. LISTC ENT('dsn') ALL"

Where "dsn" is the DSNAME of the cluster; review the ATTRIBUTES section of the output to ensure that the database is defined as NONINEXED (the cluster is an ESDS). If not, this is a finding.

2. In the IDCAMS LISTC output, look for the SMSDATA section. If none is found this is a finding.
Otherwise, find the "DATACLASS" name and query the systems programmer to ensure that the SMS data class specifies "Extended Format" but does not specify "Extended Addressing". If not, this is a finding.

3. In the IDCAMS LISTC output:
Find the "STORAGECLASS" and query the systems programmer to ensure it supports extended format VSAM dataset. If not, this is a finding.

4. Confirm that the database(s) have a data set key label. Places to check for a data set key label:
a. In the SMS data class definition by reviewing the entry for the appropriate data class in ISMF
b. In the output of an IDCAMS LISTC in the ENCRYPTIONDATA section. If "DATA SET ENCRYPTION" is "YES", then the label will be displayed after "DATA SET KEY LABEL".
c. The key label may be assigned through the ESM. Query the security team to determine if this is the case.

5. The database(s) must be defined in the DMCL as "VSAM". Run "IDMSLOOK" to print the contents of the DMCL and look for the desired database(s). If the TYPE column is not "VSAM", this is a finding.

Check Content Reference

M

Target Key

5418