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

Configuring AIR for replicating backup images from production environment to IRE BYO environment

Once IRE configuration is completed, the production NetBackup hosts are no longer able to access the IRE MSDP storage server. You need to enable MSDP reverse connection to allow the data transmission between the production MSDP server and the IRE MSDP server.

Note:

AIR configuration operations can be performed when the external network is open by IRE air gap. All the given operations are performed on the IRE MSDP server.

Prerequisites

Before you configure AIR for replicating backup images from production environment to IRE BYO environment, ensure the following:

  • In case of NetBackup certificate authority (CA), get the CA certificate and host certificate for the IRE MSDP storage server from the production primary server.

  • Create a token on the production primary server.

To configure AIR for replicating backup images from production environment to IRE BYO environment

  1. Run the following commands:
    • NetBackup certificate:

      /usr/openv/netbackup/bin/nbcertcmd -getCACertificate -server <production primary server>

      /usr/openv/netbackup/bin/nbcertcmd -getCertificate -server <production primary server> -token <token>

    • External certificate:

      /usr/openv/netbackup/bin/nbcertcmd -enrollCertificate -server <production primary server>

  2. Run the following command to enable MSDP reverse connection.

    /usr/openv/pdde/shell/bin/ire_network_control reverse_connection --add production msdp server

  3. This step is not required if you have not configured any IRE schedule. That is because if the IRE schedule is not configured, MSDP reverse connection is enabled for 24 hours on all days. The production primary server can configure the SLP replication operation with any SLP window.

    Once the MSDP reverse connection is configured, copy the IRE schedule to the NetBackup production domain as an SLP window. Use the following command:

    /usr/openv/pdde/shell/bin/sync_ire_window --production_primary_server production primary server name --production_primary_server_username production primary server username [--slp_window_name slp_window_name ]

    Where:

    The production primary server name is the fully qualified domain name (FQDN) of the primary server in your production environment.

    The production primary server username is the username of a NetBackup user with permission to list SLPs and SLP windows in the production environment.

    The production primary server username must be in domain_name\user_name format on Windows.

    The slp_window_name is the name of the SLP window to be synced with the IRE window. It is an optional parameter. If the SLP window is not specified, an SLP window with the name IRE_DEFAULT_WINDOW is created on the production primary server.

  4. You can then add the IRE WORM storage server as a replication target of the production NetBackup domain. Then add the replication operation to an existing SLP to replicate from production NetBackup domain to IRE WORM storage server using the following command:

    /usr/openv/pdde/shell/bin/add_replication_op --production_primary_server production primary server name --production_primary_server_username production primary server username --source_slp_name source slp name --target_import_slp_name target import slp name --production_storage_server production storage server name --ire_primary_server_username ire primary server username --target_storage_server target storage server name --target_storage_server_username target storage server username --production_storage_unit msdp storage unit name used in source SLP [--slp_window_name slp window name]

    Where:

    The production primary server name is the fully qualified domain name (FQDN) of the primary server in your production environment.

    The production primary server username is the username of a NetBackup user with permission to list SLPs and SLP windows in the production environment.

    The production primary server username must be in domain_name\user_name format on Windows.

    The production storage server name is the fully qualified domain name (FQDN) of the production storage server in your production environment.

    The ire primary server username is the username for administrator user of IRE primary server.

    The ire primary server username must be in domain_name\user_name format on Windows.

    The source slp name is the SLP name on the production primary server against which a replication operation is added.

    The target import slp name is the import SLP name from IRE primary server.

    The target storage server name is the fully qualified domain name (FQDN) of the target WORM storage server.

    The target storage server username is the username of the target WORM storage server.

    The slp_window_name is the name of the SLP window that is synced with the IRE window. Alternatively, it is created on the production primary server before the operation. It is an optional parameter. If the SLP window is not specified, an SLP window with the name IRE_DEFAULT_WINDOW is used that must be created using the sync_ire_window command before the operation.

    The production_storage_unit is the storage unit name of type PureDisk used in source SLP.

    Note:

    The source SLP and target import SLP need to be created before the operation.