Application Monitoring


Using OPSEC applications as CVP and UFP resources in your security policy makes those servers an integrated part of your security environment. To allow for easy monitoring of OPSEC products that function alongside VPN-1/FW-1, Check Point developed the AMON API.

AMON is the third tab in the OPSEC Application Properties window (as shown in Figure 7.12). It allows supported applications to report status information to VPN-1/FW-1. This status information is then available in the Check Point System Status Viewer alongside the real-time status of your Check Point applications. This is very useful for monitoring all devices interoperating within the security infrastructure, but another solution would probably be more useful for monitoring your entire network.

click to expand
Figure 7.12: AMON Application Properties ”General Tab

Enabling AMON is as simple as selecting the AMON option under Server Entities , and then setting the Service and AMON Identifier information on the AMON tab. As seen in Figure 7.13, the Service option is usually set to FW1_amon (TCP port 18193), but you should check the documentation that came with your application to ensure that this is the port the application is listening on. The AMON identifier field contains the Management Information Base (MIB) identifier, which also must be provided by your application s vendor.

click to expand
Figure 7.13: OPSEC Application Properties ”AMON Options Tab



Check Point NG[s]AI
Check Point NG[s]AI
ISBN: 735623015
EAN: N/A
Year: 2004
Pages: 149

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net