Title

The Cisco ACI must obtain its public key certificates from an appropriate certificate policy through an approved service provider. (Cat II impact)

Discussion

After the Cisco ACI is initialized, it uses the self-signed certificate as the SSL certificate for HTTPS. This self-signed certificate is neither appropriate nor approved for use in DOD.

Check Content

From the GUI menu bar: 1. Navigate to Admin >> AAA >> Security >> Public Key Management >> Certificate Authorities. 2. Verify the Issuer is an approved CA. If the Cisco ACI does not obtain its public key certificates from an appropriate certificate policy through an approved service provider, this is a finding.

Fix Text

From the GUI menu bar: 1. Navigate to Admin >> AAA >> Security >> Public Key Management >> Certificate Authorities. 2. Fill in the form, including the trusted CA root certificate and CA intermediate certificate. Click "Submit". 3. Navigate to Admin >> AAA >> Security >> Public Key Management >> Key Rings. Fill out the form and click "Submit". 4. Navigate to Admin >> AAA >> Security >> Public Key Management >> Key Rings. Fill out the form and click "Submit". 5. Get the CSR and send it to the CA Organization. 6. On the menu bar, navigate to Admin >> AAA >> Security >> Public Key Management >> Key Rings. 7. Double-click the create Key Ring name and find the Request option. The content in the Request is the CSR. Click "Submit". 8. Update the Signing Certificate on the Web. On the menu bar, navigate to Fabric >> Fabric Policies >> Policies >> Pod >> Management Access >> Default. 9. In the Admin KeyRing drop-down list, choose the desired KeyRing. Click "Submit". After clicking submit, an error occurs due to certificate reasons. Refresh with the new certificate.

Additional Identifiers

Rule ID: SV-271922r1067403_rule

Vulnerability ID: V-271922

Group Title: SRG-APP-000516-NDM-000344

Expert Comments

CCIs tied to check.

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