Prepare and Copy Custom SD Script Bundles

 

While the CVE files can be distributed directly, the SD scripts need to be zipped together with manifest files first. The Threat Detection and Device Visibility Add-Ons downloaded from the Forescout Support Portal already contain a manifest file, and are ready for distribution. This page explains the zipping process for custom SD scripts.

Pre-requisite: Have the Custom SD Script Ready

You may use the eyeInspect Content Distributor for any custom SD scripts that you previously prepared.

Step-by-step Guide

Step Description Example
1 Unzip the custom SD script files you prepared, and inspect the contents. It should contain a .profile file. 
custom_SD_script.profile
2 Create the manifest file.

Make sure that the filename matches the .profile filename from step 1, and has the extension .manifest. An example manifest file format is given below. Note that all the fields may not be applicable to your file.

File name: custom_SD_script.manifest 
name: Custom SD Script File Name
version: <version number>
description: <description>
threadModel: <threadModel>
minEyeInspectVersion: <version number>
file: custom_SD_script.profile
dependencies:
  - type: <event_type_import>
    file: <name of the CSV file that contains custom event types>

Note: The dependency type currently supported for SD Scripts is event_type_import. The supported file type is CSV.
3 Compress the SD script and manifest files into a zip file. 

zip custom_SD_script.manifest.zip custom_SD_script.manifest custom_SD_script.profile
4 Copy the zip file to the respective folder 
./content-distributor-cli.sh import --type sd-script --path ${HOME}/custom_SD_script.manifest.zip