Check Point Application Control Signature Tool: Administration Guide
Check Point Application Control Signature Tool: Administration Guide
Check Point
Application Control Signature Tool
Administration Guide
Classification: [Restricted]
© 2017 Check Point Software Technologies Ltd.
All rights reserved. This product and related documentation are protected by copyright and
distributed under licensing restricting their use, copying, distribution, and decompilation. No part of
this product or related documentation may be reproduced in any form or by any means without prior
written authorization of Check Point. While every precaution has been taken in the preparation of
this book, Check Point assumes no responsibility for errors or omissions. This publication and
features described herein are subject to change without notice.
RESTRICTED RIGHTS LEGEND:
Use, duplication, or disclosure by the government is subject to restrictions as set forth in
subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS
252.227-7013 and FAR 52.227-19.
TRADEMARKS:
Refer to the Copyright page http://www.checkpoint.com/copyright.html for a list of our trademarks.
Refer to the Third Party copyright notices http://www.checkpoint.com/3rd_party_copyright.html for a
list of relevant copyrights and third-party licenses.
Important Information
Latest Software
We recommend that you install the most recent software release to stay up-to-date with
the latest functional improvements, stability fixes, security enhancements and protection
against new and evolving attacks.
Feedback
Check Point is engaged in a continuous effort to improve its documentation.
Please help us by sending your comments
mailto:[email protected]?subject=Feedback on Application
Control Signature Tool Administration Guide.
Revision History
Date Description
01 November 2017 Updated Scenario Types (on page 6) and HTTP Scenario Window (on
page 11).
Added Office365 Enterprise Domain Scenario Window (on page 19) and
Office365 Consumer User Scenario Window (on page 20).
Introduction
The Application Control Signature Tool lets you create applications and signatures for your own
third-party applications. It expands the applications database in the Check Point gateway and allows
you to create and import your own applications and add them to your policy inside SmartDashboard.
CHAPT ER 2
To get started:
1. Extract the zip file into a new local folder.
2. Run: ACST.exe
Scenario Types
These are the different types of scenarios:
Scenario Actions
HTTP Enter the scenario description and select the fields you need.
To save the scenario, enter a description and values for at least
one of these fields:
• Path
• Host
• User-Agent
• Referrer
• Additional Headers
• Body
For Method, select the required method from the list.
SSL/TLS Enter the scenario description and select the fields you need.
You can select to detect traffic that has both the server name
indication and common name (AND relation) or to detect traffic that
contains at least one of the values (OR relation).
To save the scenario, enter a description and values for at least
one of these fields:
• Server Name Indication
• Common Name
Raw Data Enter the scenario description and the raw data text to detect. For
simple strings, select Simple Data. For regular expressions, select
PCRE. Change the destination ports to a specific range as needed.
To save the scenario, enter the description and:
• For Simple Data - At least one data field.
• For PCRE - LSS and PCRE Data.
Http Response Enter the scenario description and select the header fields you
need.
To save the scenario, enter a description and at least one of these
fields:
• Server - Mark and insert the required value.
• Content-Type - Mark and insert the required value.
• Body - Insert the response body data you want to detect.
Scenario Actions
Office365 Enterprise
Enter the scenario description and add the domains you want to
Domain
detect. To save the scenario, enter a description and at least one
domain.
Office365 Consumer User Enter the scenario description and add the usernames you want to
detect. To save the scenario, enter a description and at least one
username.
R77.30
To import the application to the Application Control and URL Filtering Database:
1. Open SmartDashboard > Application Control and URL Filtering > Applications and Sites.
2. Click Actions > Import.
The Import Applications/Sites window opens.
3. Browse to the *.apps file that the Signature Tool created and click Open.
R80
To import the application to R80 SmartConsole:
See sk111054 http://supportcontent.checkpoint.com/solutions?id=sk111054.
Applications Window
The Applications Window, the main window, contains a list of all the custom applications you
create and their basic properties:
• Name
• Main Category
• Risk
• Description
• Creation Date
• Last Modified Date
Use the tool box to Add, Edit, Delete, and Search an application. To create output files that you can
input into SmartDashboard, click the Export button.
Application Properties:
Main Category The main category of the application. Category from Yes
categories list
Risk Your assessment of how threatening the • Very low risk Yes
application is to security. • Low risk
• Medium risk
• High risk
• Critical risk
IP Scenario
In the IP scenario window, you can create a scenario that detects all traffic that goes to a specific IP
and/or port.
You must enter information for the Scenario Description and IP fields.
Port The port number of the traffic to detect, e.g. A valid port No
25. number from
1-65535.
Simple Data - The raw data to detect, Simple Yes (in Detects raw data text
Data e.g. “hello world.” string "Simple containing the input string.
Data"
mode)
PCRE - LSS A simple string that Simple Yes (in Detects raw data text
appears in the data, e.g. string “PCRE” containing the input string.
“hello.” mode)
PCRE - PCRE A PCRE regular PCRE Yes (in Detects raw data text that
Data expression that matches regular “PCRE” matches the regular
the data, e.g. “^He.*” expressio mode) expression.
n
Body HTTP response body, e.g. Simple No Detects response body text
“<h1>Hello World</h1>” string or containing the input string.
hexadecima
It can also be in hex, e.g. If “starts with” is checked,
l value with
“A1 2D 68”, if you check the detects response body text
the format
“hexadecimal” check box. starting with the input
“XX XX XX”
string.
where X is a
hexadecima
l digit.