V-215215

Discussion

Untrusted Certificate Authorities (CA) can issue certificates, but they may be issued by organizations or individuals that seek to compromise DoW systems or by organizations with insufficient security controls. If the CA used for verifying the certificate is not a DoW-approved CA, trust of this CA has not been established. The DoW will only accept PKI-certificates obtained from a DoW-approved internal or external certificate authority. Reliance on CAs for the establishment of secure sessions includes, for example, the use of SSL/TLS certificates.

Check Content

Note: Depending on which version of GSKit is installed on AIX, the GSK commands that are used to manage the Key Database (KDB) have different names. The possible GSK commands are: gsk8capicmd (used below), gsk8capicmd_64 and gsk7cmd.

Check if the system is using LDAP authentication: 

# grep LDAP /etc/security/user 

If no lines are returned, this requirement is not applicable. 

Check if the useSSL option is enabled: 

# grep '^useSSL' /etc/security/ldap/ldap.cfg 
useSSL:yes

If "yes" is not the returned value, this is a finding. 

Verify a certificate is used for client authentication to the server: 

# grep -i '^ldapsslkeyf' /etc/security/ldap/ldap.cfg 
ldapsslkeyf:/tmp/key.kdb

If no line is found, this is a finding. 

Identify the Key Database (KDB), and its password, by asking the ISSO/SA). 

If  no Key Database exists on the system, this is a finding.

List the certificate issuer with IBM GSK:

# gsk8capicmd -cert -list CA -db <KDB_FILE> -pw <KDB_PASSWORD> 

Make note of the client Key Label: 

# gsk8capicmd -cert -details -showOID -db <KDB_FILE> -pw <KDB_PASSWORD> -label <Key Label> 

If the certificate is not issued by DoW PKI or a DoW-approved external PKI, this is a finding.

The IBM GSK Database should only have certificates for the client system and for the LDAP server. 

If more certificates are in the key database than the LDAP server and the client, this is a finding.