Uploading a Policy Configuration for Offline Analysis

Once you have obtained a policy configuration file, you can upload it to SecureTrack, as a revision for a device configured for Offline Analysis, as follows:

  1. Do one of the following:
    • Go to Manage Devices. In the device tree, select the relevant device. Click Import configuration:

      Import config

    • In Compare view, in the device tree, select the relevant device. Click Upload Configuration:

      upload config

  2. Navigate to the policy configuration file, and click Open.

The revision will appear after a few minutes in Compare view.

Alternatively, you can upload a policy configuration file to SecureTrack using CLI, as follows:

  1. Get into the device-collector pod.

    kubectl exec -it deploy/device-collector -c device-collector -- bash
  2. Run the following command, type1 for SecureTrack, and type c to apply the change.

    [<ADMIN> ~]# tos conf
    tos conf
  3. Get the ID of the offline device:

    [<ADMIN> ~]# st stat
    st stat
  4. Exit the pod:

    [<ADMIN> ~]# exit
    exit
  5. Run the following command to get the ID of the device-collector: (If there are multiple IDs, use the first one.)

    kubectl get pods | grep device-collector
    kubectl get pods | grep device-collector
  6. From the SecureTrack host, copy the policy configuration file to the device-collector pod:

    kubectl cp <POLICY_CONFIGURATION_FILE_NAME> device-collector-<device-collector-ID>:/usr/local/st/offline_analysis/offline<ID> -c device-collector
    kubectl cp <POLICY_CONFIGURATION_FILE_NAME> device-collector-<device-collector-ID>:/usr/local/st/offline_analysis/offline<ID> -c device-collector

    where

    • <device-collector-ID> is the ID of the device-collector that you obtained in step 3.

    • <ID> is the ID of the offline device you obtained in step 2.

  7. Connect to the cgi-server pod:

    kubectl exec -it <cgi-server-id> -- bash
    kubectl exec -it <cgi-server-id> -- bash
  8. Run the following command:

    st restart <ID>
    st restart <ID>
  9. where <ID> is the ID# from step 2.

The revision will appear after a few minutes in the Compare view.

The CLImethod is not relevant for remote collectors.