Red Hat NETSCAPE MANAGEMENT SYSTEM 7.0 - AGENT GUIDE Betriebsanweisung PDF herunterladen (Seite 57)

Secunia.com 57

Third-Party Integration

The Secunia CSI 7.0 provides you with the capability of publishing packages using third-party

patch deployment solutions, for example Altiris. In order to support this feature Secunia has

enhanced the package export feature. The exported xml file contains additional information

that can be helpful in creating packages in other tools, including:

The version numbers

The executable itself

The vulnerability/criticality

Secunia has retained the simplicity of the xml file by giving you the options to exclude large

binary files and applicability paths from the file, in the form of check boxes in the package

creation wizard. To perform a complete export, deselect the Do not include package files

check box during Step 4 of the SPS Package Creation Wizard.

In order for the Secunia CSI to integrate with other patch deployment solutions, you need to

create a configuration file, a script file and an applicability check script file:

Configuration file. The configuration file is actually a representative of the tool and a

visual integration between the Secunia CSI and that tool. The file is an xml file that

should contain the tool name, script name and the input/setting fields required to

configure the settings for the tool (text fields, radio buttons and check boxes are

supported). When the Secunia CSI is launched it checks for the presence of any

configuration file and, if there is a valid configuration file in the Extensions folder in the

CSI path, it dynamically loads a GUI under the Patching menu of CSI. The

configuration file also acts as an input file for the script.

Script file. This script file corresponds to the SDK that the user has created to create

and dispatch the package in the respective tool. The script file can be an executable,

Java, VB, Python, or Perl script. Click Publish to execute the script file.

Applicability Check script file. This script file runs the sps.exe on the computer if the

applicability checks are cleared. This file is published together with the package to

establish if the package is applicable to the system or not.

Create and Publish the Package

1. Place the configuration and script files in the Extensions folder. The Extensions folder

should be created in the same folder as the csi.exe.

2. Launch the Secunia CSI. If the configuration file format is valid, a configuration option will

be visible under the Patching menu (for example, Altiris Configuration).

3. Click the configuration option to open a page where input and settings can be provided and

saved.

4. Go to the SPS creation wizard. Complete all the package wizard fields or import a package.

In Step 4 of 4: Applicability Criteria – Rules, there will be radio buttons allowing you to

select the tool that you want to publish the package with. There will be as many selection

options as there are valid configuration files.

5. Clicking Publish for any tool other than WSUS will run the script placed in the Extensions

folder and named in the xml file.

6. The Secunia CSI waits for script to finish and, depending upon the execution of the script

being successful or not, displays a message.

7. After successful publishing, the package can be seen in the respective tool.

Running the script is a very strong feature. Use caution and ensure the sanity of

the script file before publishing.

1 2 ... 52 53 54 55 56 57 58 59 60 61 62 ... 68 69

Kommentare zu diesen Handbüchern

Keine Kommentare

Red Hat NETSCAPE MANAGEMENT SYSTEM 7.0 - AGENT GUIDE Betriebsanweisung Seite 57

Kommentare zu diesen Handbüchern