Importing Third-Party Host Checker Policies
Copyright © 2010, Juniper Networks, Inc.
Click the ESAP link.
3.
Click the ESAP Download Page link.
4.
Navigate to the ESAP release you want.
5.
Upload the plug-in zip file to your computer.
6.
Linking to an ESAP Package Shared Object
To create a link from a Secure Access or Infranet Controller configuration tree to a shared
object containing an ESAP package, follow these steps:
In the Device Manager, double-click the Secure Access or Infranet Controller device
1.
to open the device editor, and then select the Configuration tab.
Expand Authentication.
2.
Select Endpoint Security.
3.
From the Host Checker tab, select Endpoint Security Assessment Plug-Ins, and
4.
then click the Add icon.
In the New Endpoint Security Assessment Plug-Ins dialog box, enter an ESAP version
5.
number.
Select a shared binary object from the Path to Package list.
6.
Click OK once to save the link, and again to save the configuration.
7.
For Windows clients, you can create global Host Checker policies that take a third-party
J.E.D.I. DLL that you upload to the IVE and run on client machines.
Uploading a Third-Party Host Checker Policy
Follow these steps to upload a package definition file that the device will recognize:
Name the package definition file
1.
.
META-INF
Create a Host Checker policy package by creating a
2.
folder that contains the
initialization files. For example, a Host Checker policy package might contain:
META-INF/MANIFEST.HCIF hcif-myPestPatrol.dll hcif-myPestPatrol.ini
Upload the Host Checker package to the NSM shared object. You can upload multiple
3.
policy packages to NSM shared objects, each containing a different
file.
MANIFEST.HCIF
and include it in a folder named
MANIFEST.HCIF
file along with the interface DLL and any
Chapter 7: Managing Devices
archive. Include the
zip
META-INF
MANIFEST.HCIF
277
Need help?
Do you have a question about the NETWORK AND SECURITY MANAGER 2010.3 - ADMINISTRATION GUIDE REV1 and is the answer not in the manual?
Questions and answers