Go to main content

Trusted Extensions Configuration and Administration

Exit Print View

Updated: March 2019
 
 

How to Apply IPsec Protections in a Multilevel Trusted Extensions Network

    In this procedure, you configure IPsec on two Trusted Extensions systems to handle the following conditions:

  • The two systems, enigma and partym, are multilevel Trusted Extensions systems that are operating in a multilevel network.

  • Application data is encrypted and protected against unauthorized change within the network.

  • The security label of the data is visible in the form of a CALIPSO or CIPSO IP option for use by multilevel routers and security devices on the path between the enigma and partym systems.

  • The security labels that enigma and partym exchange are protected against unauthorized changes.

Before You Begin

You are in the root role in the global zone.

  1. Add the enigma and partym hosts to a cipso security template.

    Follow the procedures in Labeling Hosts and Networks. Use a template with a cipso host type.

  2. Configure IPsec for the enigma and partym systems.

    For the procedure, see How to Secure Network Traffic Between Two Servers With IPsec in Securing the Network in Oracle Solaris 11.4. Use IKE for key management, as described in the following step.

  3. Add labels to IKEv1 negotiations.

    Follow the procedure in How to Configure IKEv1 With Preshared Keys in Securing the Network in Oracle Solaris 11.4, then modify the ike/config file as follows:

    1. Add the keywords label_aware, multi_label, and wire_label inner to the enigma system's /etc/inet/ike/config file.

      The resulting file appears similar to the following. The label additions are highlighted.

      	### ike/config file on enigma, 192.168.116.16
      ## Global parameters
      #
      ## Use IKEv1 to exchange security labels.
      label_aware
      #
      ## Defaults that individual rules can override.
      p1_xform
      { auth_method preshared oakley_group 5 auth_alg sha encr_alg 3des }
      p2_pfs 2
      #
      ## The rule to communicate with partym
      # Label must be unique
      { label "enigma-partym"
      local_addr 192.168.116.16
      remote_addr 192.168.13.213
      multi_label
      wire_label inner
      p1_xform
      { auth_method preshared oakley_group 5 auth_alg sha1 encr_alg aes }
      p2_pfs 5
      }
    2. Add the same keywords to the ike/config file on the partym system.
      	### ike/config file on partym, 192.168.13.213
      ## Global Parameters
      #
      ## Use IKEv1 to exchange security labels.
      label_aware
      #
      p1_xform
      { auth_method preshared oakley_group 5 auth_alg sha encr_alg 3des }
      p2_pfs 2
      ## The rule to communicate with enigma
      # Label must be unique
      { label "partym-enigma"
      local_addr 192.168.13.213
      remote_addr 192.168.116.16
      multi_label
      wire_label inner
      p1_xform
      { auth_method preshared oakley_group 5 auth_alg sha1 encr_alg aes }
      p2_pfs 5
      }
  4. If AH protection of CALIPSO or CIPSO IP options cannot be used on the network, use ESP authentication.

    Use encr_auth_algs rather than auth_algs in the /etc/inet/ipsecinit.conf file to handle authentication. ESP authentication does not cover the IP header and IP options, but will authenticate all information after the ESP header.

    {laddr enigma raddr partym} ipsec {encr_algs any encr_auth_algs any sa shared}

    Note -  You can also add labels to systems that are protected by certificates. Public key certificates are managed in the global zone on Trusted Extensions systems. Modify the ike/config files similarly when completing the procedures in Configuring IKEv1 With Public Key Certificates in Securing the Network in Oracle Solaris 11.4.