The vAMI private key must only be accessible to authenticated system administrators or the designated PKI Sponsor.

From VMW vRealize Automation 7.x vAMI Security Technical Implementation Guide

Associated with: CCI-000186

SV-100875r1_rule The vAMI private key must only be accessible to authenticated system administrators or the designated PKI Sponsor.

Vulnerability discussion

The cornerstone of the PKI is the private key used to encrypt or digitally sign information. If the private key is stolen, this will lead to the compromise of the authentication and non-repudiation gained through PKI because the attacker can use the private key to digitally sign documents and can pretend to be the authorized user. Both the holders of a digital certificate and the issuing authority must protect the computers, storage devices, or whatever they use to keep the private keys. Java-based application servers utilize the Java keystore, which provides storage for cryptographic keys and certificates. The keystore is usually maintained in a file stored on the file system.

Check content

At the command prompt, execute the following command: ls -l /opt/vmware/etc/sfcb/file.pem If permissions on the key file are not -r--r----- (440), this is a finding.

Fix text

At the command prompt, enter the following command: chmod 440 /opt/vmware/etc/sfcb/file.pem

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.