NetBackup and Veritas Appliances Hardening Guide

Last Published:
Product(s): Appliances (10.2, 5.1.1, 3.0), NetBackup (10.2, 5.1.1, 3.0)
Platform: NetBackup Appliance OS,Flex Appliance OS,Linux,UNIX,Windows
  1. Top recommendations to improve your NetBackup and Veritas appliances security posture
    1.  
      Introduction
    2.  
      Keeping all systems and software updated
    3.  
      Enabling multifactor authentication
    4.  
      Increasing the appliance security level
    5.  
      Implementing an immutable data vault
    6.  
      Securing credentials
    7.  
      Reducing network exposure
    8.  
      Enabling encryption
    9.  
      Enabling catalog protection
    10.  
      Enabling malware scanning and anomaly detection
    11.  
      Enabling security observability
    12.  
      Restricting user access
    13.  
      Configuring a sign-in banner
  2. Steps to protect Flex Appliance
    1.  
      About Flex Appliance hardening
    2. Managing single sign-on (SSO)
      1.  
        Managing identity providers (IDPs)
      2.  
        Importing single sign-on (SSO) users
    3.  
      Managing user authentication with smart cards or digital certificates
    4. About lockdown mode
      1.  
        Changing the lockdown mode
    5.  
      Using network access control
    6.  
      Using an external certificate
    7.  
      Forwarding logs
    8.  
      Creating a NetBackup WORM storage server instance
    9. Configuring an isolated recovery environment on a WORM storage server
      1.  
        Configuring data transmission between a production environment and an IRE WORM storage server
    10.  
      Protecting the NetBackup catalog on a WORM storage server
    11.  
      Using a sign-in banner
  3. Steps to protect NetBackup Appliance
    1.  
      About NetBackup Appliance hardening
    2. About single sign-on (SSO) authentication and authorization
      1.  
        Configure single sign-on (SSO) for a NetBackup Appliance
    3. About authentication using smart cards and digital certificates
      1.  
        2FA
      2.  
        Smart card Authentication for NetBackup Web UI
      3.  
        Smart card authentication for NetBackup Appliance Web UI
      4.  
        Smart card authentication for NetBackup Appliance Shell Menu
      5.  
        Configure role-based access control
      6.  
        Configure authentication for a smart card or digital certificate for the NetBackup Web UI
    4.  
      Disable user access to the NetBackup appliance operating system
    5.  
      About Network Access Control
    6. About data encryption
      1.  
        KMS support
    7.  
      FIPS 140-2 conformance for NetBackup Appliance
    8.  
      About implementing external certificates
    9. About forwarding logs to an external server
      1.  
        Uploading certificates for TLS
      2.  
        Enabling log forwarding
    10.  
      Creating the appliance login banner
  4. Steps to protect NetBackup
    1.  
      About NetBackup hardening
    2. Configure NetBackup for single sign-on (SSO)
      1.  
        Configure the SAML KeyStore
      2.  
        Configure the SAML keystore and add and enable the IDP configuration
      3.  
        Enroll the NetBackup primary server with the IDP
    3. Configure user authentication with smart cards or digital certificates
      1.  
        Configure smart card authentication with a domain
      2.  
        Configure smart card authentication without a domain
    4. Access codes
      1.  
        Get CLI access through web UI authentication
      2.  
        Approve your CLI access request
      3.  
        Approve CLI access requests of other users
    5. Workflow to configure immutable and indelible data
      1.  
        About configuring disk pool storage
      2.  
        Use WORM setting
      3.  
        Creating a backup policy
    6. Add a configuration for an external CMS server
      1.  
        Add a credential for CyberArk
    7. Configuring an isolated recovery environment on a NetBackup BYO media server
      1.  
        Configuring AIR for replicating backup images from production environment to IRE BYO environment
    8. About FIPS support in NetBackup
      1.  
        Enable FIPS mode on NetBackup during installation
      2.  
        Enable FIPS mode on a NetBackup host after installation
      3.  
        Enable FIPS mode for the NetBackup Authentication Broker service
      4.  
        Enable FIPS mode for the NetBackup Administration Console
      5.  
        NB_FIPS_MODE option for NetBackup servers and clients
    9.  
      Installing KMS
    10. Workflow for external KMS configuration
      1.  
        Validating KMS credentials
      2.  
        Configuring KMS credentials
      3.  
        Configuring KMS
      4.  
        Creating keys in an external KMS
      5. Workflow to configure data-in-transit encryption
        1.  
          Configure the global data-in-transit encryption setting
        2. Configure the DTE mode on a client
          1.  
            DTE_CLIENT_MODE for clients
        3. How DTE configuration settings work in various NetBackup operations
          1.  
            Backup
          2.  
            Restore
          3.  
            MSDP backup, restore, and optimized duplication
          4.  
            Universal-Share policy backup
          5.  
            Catalog backup and recovery
          6.  
            Duplication
          7.  
            Synthetic backup
          8.  
            Verify
          9.  
            Import
          10.  
            Replication
        4.  
          Configure the DTE mode on the media server
        5. Modify the DTE mode on a backup image
          1.  
            DTE_IGNORE_IMAGE_MODE for NetBackup servers
    11. Workflow to use external certificates for NetBackup host communication
      1. About certificate revocation lists for external CA
        1.  
          How CRLs from ECA_CRL_PATH are used
        2.  
          How CRLs from CDP URLs are used
      2.  
        Configuring an external certificate for the NetBackup web server
      3.  
        Configuring the primary server to use an external CA-signed certificate
      4. Configuring an external certificate for a clustered primary server
        1. Configuration options for external CA-signed certificates for a virtual name
          1.  
            CLUSTER_ECA_CERT_PATH for clustered primary server
          2.  
            CLUSTER_ECA_TRUST_STORE_PATH for clustered primary server
          3.  
            CLUSTER_ECA_PRIVATE_KEY_PATH for clustered primary server
          4.  
            CLUSTER_ECA_KEY_PASSPHRASEFILE for clustered primary server
      5. Configuring a NetBackup host (media server, client, or cluster node) to use an external CA-signed certificate after installation
        1.  
          Enrolling an external certificate for a remote host
      6. Configuration options for external CA-signed certificates
        1. ECA_CERT_PATH for NetBackup servers and clients
          1.  
            Specifying Windows certificate store for ECA_CERT_PATH
        2.  
          ECA_TRUST_STORE_PATH for NetBackup servers and clients
        3.  
          ECA_PRIVATE_KEY_PATH for NetBackup servers and clients
        4.  
          ECA_KEY_PASSPHRASEFILE for NetBackup servers and clients
        5.  
          ECA_CRL_CHECK for NetBackup servers and clients
        6.  
          ECA_CRL_PATH for NetBackup servers and clients
        7.  
          ECA_CRL_PATH_SYNC_HOURS for NetBackup servers and clients
        8.  
          ECA_CRL_REFRESH_HOURS for NetBackup servers and clients
        9.  
          ECA_DISABLE_AUTO_ENROLLMENT for NetBackup servers and clients
        10.  
          ECA_DR_BKUP_WIN_CERT_STORE for NetBackup servers and clients
        11.  
          MANAGE_WIN_CERT_STORE_PRIVATE_KEY option for NetBackup primary servers
    12.  
      Guidelines for managing the primary server NetBackup catalog
    13. About protecting the MSDP catalog
      1. About the MSDP shadow catalog
        1.  
          Changing the MSDP shadow catalog path
        2.  
          Changing the MSDP shadow catalog schedule
        3.  
          Changing the number of MSDP catalog shadow copies
      2.  
        About the MSDP catalog backup policy
    14. How to set up malware scanning
      1.  
        Prerequisites for a scan host
      2.  
        Configuring a new scan host pool
    15. About backup anomaly detection
      1.  
        Detecting backup anomalies on the primary server
      2.  
        Detecting backup anomalies on the media server
      3.  
        Configure anomaly detection settings
      4.  
        View anomalies
    16.  
      Send audit events to system logs
    17.  
      Send audit events to log forwarding endpoints
    18.  
      Display a banner to users when they sign in

Installing KMS

The following procedure describes how to install KMS.

Note:

For more information about configuring KMS in a Cloud storage environment refer to the NetBackup Cloud Administrator's Guide.

The KMS service is called nbkms.

The service does not run until the data file has been set up, which minimizes the effect on environments not using KMS.

To install KMS

  1. Run the nbkms -createemptydb command.
  2. Enter a pass phrase for the host master key (HMK). You can also press Enter to create a randomly generated key.
  3. Enter an ID for the HMK. This ID can be anything descriptive that you want to use to identify the HMK.
  4. Enter a pass phrase for the key protection key (KPK).
  5. Enter an ID for the KPK. The ID can be anything descriptive that you want to use to identify the KPK.

    The KMS service starts when after you enter the ID and press Enter.

  6. Start the KMS service as follows:

    On UNIX, run the following command:

    /usr/openv/netbackup/bin/nbkms

    On Windows, do the following:

    Start > Run > Services.msc > Start the NetBackup Key Management Service

  7. Use the grep command to ensure that the service has started, as follows: ps -ef | grep nbkms
  8. Run the following command to register the nbkms service with NetBackup web services:

    nbkmscmd -discovernbkms

  9. Create the key group. The key group name must be an identical match to the volume pool name. All key group names must have a prefix ENCR_.

    Note:

    When using key management with Cloud storage and PureDisk, the ENCR_ prefix is not required for the key group name.

    To create a (non-Cloud storage) key group use the following command syntax. nbkmsutil -createkg -kgname ENCR_volumepoolname

    The ENCR_ prefix is essential. When BPTM receives a volume pool request that includes the ENCR_ prefix, it provides that volume pool name to KMS. KMS identifies it as an exact match of the volume pool and then picks the active key record for backups out of that group.

    To create a Cloud storage key group use the following command syntax.

    nbkmsutil -createkg -kgname storage_server_name:volume_name

  10. Create a key record by using the -createkey option.

    nbkmsutil -createkey -kgname ENCR_volumepool -keyname keyname -activate -desc "message"

    The key name and message are optional; they can help you identify this key when you display the key.

    The -activate option skips the prelive state and creates this key as active.

  11. Provide the pass phrase again when the script prompts you.

    In the following example the key group is called ENCR_pool1 and the key name is Q1_2008_key. The description explains that this key is for the months January, February, and March.

    nbkmsutil -createkey -kgname ENCR_pool1 -keyname Q1_2008_key -activate -desc "key for Jan, Feb, & Mar"

  12. You can create another key record using the same command; a different key name and description help you distinguish they key records: nbkmsutil -createkey -kgname ENCR_pool1 -keyname Q2_2008_key -activate -desc "key for Apr, May, & Jun"

    Note:

    If you create more than one key record by using the command nbkmsutil -kgname name -activate, only the last key remains active.

  13. To list all of the keys that belong to a key group name, use the following command:

    nbkmsutil -listkeys -kgname keyname

    Note:

    You need the passphrase, salt (if applicable), key group name, and key tag to recover this key if it is lost. You must store all this information at a secure place. Salt, key group name, and key tag can be found in the output of the nbkmsutil -listkeys command execution.

    The following command and output use the examples in this procedure.