Veritas NetBackup™ Appliance Security Guide
- About the NetBackup appliance Security Guide
- User authentication
- About user authentication on the NetBackup appliance
- About configuring user authentication
- About authenticating LDAP users
- About authenticating Active Directory users
- About authentication using smart cards and digital certificates
- About single sign-on (SSO) authentication and authorization
- About the appliance login banner
- About user name and password specifications
- User authorization
- Intrusion prevention and intrusion detection systems
- About Symantec Data Center Security on the NetBackup appliance
- About the NetBackup appliance intrusion prevention system
- About the NetBackup appliance intrusion detection system
- Reviewing SDCS events on the NetBackup appliance
- Running SDCS in unmanaged mode on the NetBackup appliance
- Running SDCS in managed mode on the NetBackup appliance
- Log files
- Operating system security
- Data security
- Web security
- Network security
- Call Home security
- Remote Management Module (RMM) security
- STIG and FIPS conformance
- Index
Replacing the default IPMI SSL certificate
Veritas recommends that you replace the default IPMI SSL certificate used to access the Veritas Remote Management (RMM) console. You can use a certificate signed by a trusted internal or external Certificate Authority (in PEM format), or by a self-signed certificate. Use the following procedure to create a minimal self-signed certificate on a Linux computer and import it into the IPMI web interface.
Note:
Starting with BMC v2.86, the RMM console does not allow you to upload .key files. You can only upload .pem files for SSL certificates. When you generate a self-signed certificate, you must generate the private key with the .pem file extension.
To create a minimal self-signed certificate on a Linux computer and import it into the RMM console:
- Run the following command to generate the private key called
ipmi.key:$ openssl genrsa -out ipmi.key 2048 Generating RSA private key, 2048 bit long modulus .....+++ .+++ e is 65537 (0x10001)
- Generate a certificate signing request called
ipmi.csrusingipmi.key, filling in each field with their appropriate values:Note:
To avoid extra warnings in your browser, set the CN to the fully qualified domain name of the RMM console. You are about to enter what is called a Distinguished Name or a DN.
$ openssl req -new -key ipmi.key -out ipmi.csr
Refer to the following guidelines to enter information to be incorporated into your certificate request:
Country Name (2 letter code) [AU]:
Enter your Country's name. For example, US.
State or Province Name (full name) [Some-State]:
Enter your State's or Province's name. For example, OR.
Locality Name (eg, city) []:
Enter your Locality name. For example, Springfield.
Organization Name (eg, company) [Internet Widgits Pty Ltd]:
Enter your Organization's name. For example, Veritas.
Organizational Unit Name (eg, section) []:
Enter your Organization Unit's name.
Common Name (eg, YOUR name) []:
Enter
hostname.your.company.Email Address []:
Enter your email address. For example,
email@your.company.A challenge password []:
Enter the appropriate challenge password, which is the extra attribute to be sent with your certificate request.
An optional company name []:
Enter the appropriate optional company name, which is the extra attribute to be sent with your certificate request.
Note:
Enter '.', to leave any field blank.
- Sign
ipmi.csrwithipmi.keyand create a certificate calledipmi.crtthat is valid for 1 year:$ openssl x509 -req -in ipmi.csr -out ipmi.crt -signkey ipmi.key -days 365 Signature ok subject=/C=US/ST=OR/L=Springfield /O=Veritas/OU=Your OU/ CN=hostname.your.company/ emailAddress=email@your.company Getting Private key
- Copy the generated self-signed certificate and the private key files to a host that has access to the appliance RMM console.
- Log in to the RMM console.
- Click Configuration > SSL Certification.
The appliance displays the SSL Upload page.
- From the SSL Upload page, do the following:
Click New SSL Certificate and select the copied self-signed certificate file.
Click New Private Key and select the copied key file.
Click Upload.
- A warning may appear that states an SSL certificate already exists. Press OK to continue.
- A confirmation appears stating that the certificate and the key were uploaded successfully. Press OK to restart the web service.
- Close and reopen the RMM console to verify that the new certificate is being presented.