•
Destination Network: ip_mailserver
•
Click OK
Specify the Action:
An action is now defined, specifying what signatures the IDP should use when scanning data matching the rule,
and what NetDefendOS should do when a possible intrusion is detected. In this example, intrusion attempts will
cause the connection to be dropped, so Action is set to Protect. The Signatures option is set to
IPS_MAIL_SMTP in order to use signatures that describe attacks from the external network that are based on the
SMTP protocol.
1.
Select the Rule Action tab for the IDP rule
2.
Now enter:
•
Action: Protect
•
Signatures: IPS_MAIL_SMTP
•
Click OK
If logging of intrusion attempts is desired, this can be configured by clicking in the Rule Actions tab when
creating an IDP rule and enabling logging. The Severity should be set to All in order to match all SMTP attacks.
In summary, the following will occur: If traffic from the external network to the mail server occurs, IDP will be
activated. If traffic matches any of the signatures in the IPS_MAIL_SMTP signature group, the connection will be
dropped, thus protecting the mail server.
Using Individual Signatures
The preceding example uses an entire IDP group name when enabling IDP. However, it is possible
to instead specify indvidual signatures or a list of signatures for an IDP rule. Individual signatures
are identified by their unique number ID and multiple signatures is specified as a comma separated
list of these IDs.
For example, to specify signatures with the ID 68343, the CLI in the above example would become:
gw-world:/IDPMailSrvRule> add IDPRuleAction
Action=Protect
IDPServity=All
Signatures=68343
To specify a list which also includes signatures 68345 and 68349:
gw-world:/IDPMailSrvRule> add IDPRuleAction
Action=Protect
IDPServity=All
Signatures=68343,68345,68349
Individual signatures are entered in a similar way when using the Web Interface.
IDP Traffic Shaping
IDP offers an excellent means of identifying different types of traffic flow through NetDefendOS
and the applications responsible for them. This ability is combined with the traffic management
features of NetDefendOS to provide IDP Traffic Shaping which can place bandwidth and priority
restrictions on the specific flows identified.
The IDP traffic shaping feature is discussed in depth in Section 10.2, “IDP Traffic Shaping”.
6.5.8. SMTP Log Receiver for IDP
Events
Chapter 6. Security Mechanisms
360
Summary of Contents for NetDefend DFL-1660
Page 28: ...1 3 NetDefendOS State Engine Packet Flow Chapter 1 NetDefendOS Overview 28 ...
Page 88: ...2 6 3 Restore to Factory Defaults Chapter 2 Management and Maintenance 88 ...
Page 166: ...3 10 DNS Chapter 3 Fundamentals 166 ...
Page 254: ...4 7 5 Advanced Settings for Transparent Mode Chapter 4 Routing 254 ...
Page 268: ...5 4 IP Pools Chapter 5 DHCP Services 268 ...
Page 368: ...6 7 Blacklisting Hosts and Networks Chapter 6 Security Mechanisms 368 ...
Page 390: ...7 4 7 SAT and FwdFast Rules Chapter 7 Address Translation 390 ...
Page 414: ...8 3 Customizing Authentication HTML Pages Chapter 8 User Authentication 414 ...
Page 490: ...9 8 6 Specific Symptoms Chapter 9 VPN 490 ...
Page 528: ...10 4 6 Setting Up SLB_SAT Rules Chapter 10 Traffic Management 528 ...
Page 544: ...11 7 HA Advanced Settings Chapter 11 High Availability 544 ...
Page 551: ...12 3 5 Limitations Chapter 12 ZoneDefense 551 ...
Page 574: ...Default 512 13 9 Miscellaneous Settings Chapter 13 Advanced Settings 574 ...
Page 575: ...13 9 Miscellaneous Settings Chapter 13 Advanced Settings 575 ...