Title

Data set masking characters must be properly defined to the CA-TSS security database. (Cat II impact)

Discussion

To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement. Access control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.

Check Content

From the ISPF Command Shell enter: TSS WHOOWNS data set(*) If data set masking characters. (*, %, and +, **) are owned by the MSCA, this is not a finding.

Fix Text

Configure all data set masking characters to be owned the MSCA. Example TSS commands to protect masking characters: TSS ADD(msca) DSN(*) TSS ADD(msca) DSN(%) TSS ADD(msca) DSN(+)

Additional Identifiers

Rule ID: SV-223924r877765_rule

Vulnerability ID: V-223924

Group Title: SRG-OS-000080-GPOS-00048

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.