Creating custom signatures | Custom signatures |
Custom signature syntax
Table 2: Information keywords
Keyword and value | Description | ||
|
|
| |
| This optional value is used to identify the signature. It | ||
| cannot be the same value as any other custom rules within | ||
| the same VDOM. If an attack ID is not specified, the | ||
| FortiGate automatically assigns an attack ID to the | ||
| signature. | ||
| An attack ID you assign must be between 1000 and 9999. | ||
| Example: | ||
|
|
| |
| Enter the name of the rule. A rule name must be unique | ||
| within the same VDOM. | ||
| The name you assign must be a string greater than 0 and | ||
| less than 64 characters in length. | ||
| Example: | ||
|
|
| |
Table 3: Session keywords |
|
|
|
|
|
|
|
Keyword and value |
|
| Description |
|
|
|
|
|
| Specify the traffic direction and state to be inspected. | |
from_server |
|
| They can be used for all IP traffic. |
bi_direction }; |
|
| Example: |
|
|
|
|
|
|
|
|
|
|
| The signature checks traffic to and from port 41523. |
|
|
| Previous FortiOS versions used to_client and |
|
|
| to_server values. These are now deprecated, but |
|
|
| still function for backwards compatibility. |
| Specify the protocol type to be inspected. | ||
FTP DNS SMTP POP3 |
| This keyword allows you to specify the traffic type by | |
IMAP SNMP RADIUS |
| protocol rather than by port. If the decoder has the | |
LDAP MSSQL RPC SIP |
| capability to identify the protocol on any port, the | |
| signature can be used to detect the attack no matter | ||
H323 NBSS DCERPC |
| what port the service is running on. Currently, HTTP, | |
SSH SSL}; |
|
| SIP, SSL, and SSH protocols can be identified on any |
|
|
| port based on the content. |
| FortiGate IPS User Guide Version 3.0 MR7 |
24 |