{"id":1124,"date":"2019-03-19T16:18:49","date_gmt":"2019-03-19T16:18:49","guid":{"rendered":"http:\/\/www.ankenbrand24.de\/?page_id=1124"},"modified":"2019-03-19T16:21:33","modified_gmt":"2019-03-19T16:21:33","slug":"ddos-fw-sam-vs-fwaccel-dos","status":"publish","type":"page","link":"https:\/\/www.ankenbrand24.de\/index.php\/articles\/check-point-articel\/performance-tuning\/ddos-fw-sam-vs-fwaccel-dos\/","title":{"rendered":"DDoS fwaccel dos"},"content":{"rendered":"\n
\n\n\n\n

R80.x Performance Tuning Tip \u2013 DDoS \u201efw sam\u201c vs. \u201efwaccel dos\u201c<\/span><\/h2>\n\n\n\n
\n\n\n\n\n\n\n
What is SecureXL penalty box?<\/span><\/th>\n<\/tr>\n<\/thead>\n<\/table>\n

\"\"<\/p>\n

The SecureXL penalty box is a mechanism that performs an early drop of packets arriving from suspected sources. This mechanism is supported starting in R75.40VS.<\/p>\n

Why not sam policy rules?<\/p>\n

The SAM policy rules consume some CPU resources on Security Gateway. We recommend to set an expiration that gives you time to investigate, but does not affect performance. The best practice is to keep only the SAM policy rules that you need. If you confirm that an activity is risky, edit the Security Policy, educate users, or otherwise handle the risk. Or better use SecureXL penalty box from a performance point of view.<\/p>\n

The purpose of this feature is to allow the Security Gateway to cope better under high load, possibly caused by a DoS\/DDoS attack. These commands \u201efwaccel dos\u201c and \u201efwaccel6 dos\u201c\u00a0 control the Rate Limiting for DoS mitigation techniques in SecureXL on the local security gateway or cluster member.<\/p>\n

In version R80.20, the penalty box feature is now supported in VSX mode and each virtual system can be independently configured for penalty box operation.<\/p>\n

Attention!<\/strong><\/p>\n

In R80.20, all “sim erdos” commands are no longer supported. They have been replaced with equivalent commands which can be found under “fwaccel dos”. Penalty box is configured separately for IPv4 and IPv6. IPv4 configuration is performed using the “fwaccel dos” command. IPv6 configuration is performed using the “fwaccel6 dos” command.<\/p>\n\n\n\n
Old known SAM rule<\/span><\/th>\n<\/tr>\n<\/thead>\n<\/table>\n

This would be a classic SAM rule which already existed in all versions R77.30, R80.10 and R80.20. In this example the source IP 1.2.3.4 is blocked.<\/p>\n

\"\"<\/p>\n

I don’t want to go into the SAM rules further here. You can read it here: How to create and view Suspicious Activity Monitoring (SAM) Rules<\/a>.<\/p>\n\n\n\n
IP blacklist<\/span><\/th>\n<\/tr>\n<\/thead>\n<\/table>\n

Tip 1
<\/strong><\/span>Controls the IP blacklist in SecureXL. The blacklist blocks all traffic<\/span> to and from the specified IP addresses. It is an easy way to block certain IP addresses quickly and eficiently on SecureXL level.<\/p>\n

The blacklist drops occur in SecureXL, which is more efficient than an Access Control Policy or SAM rule to drop the packets. This can be very helpful e.g. with DoS attacks to block an IP on SecureXL level.<\/p>\n

For example, the traffic from and to IP 1.2.3.4 should be blocked at SecureXL level.<\/p>\n

On gateway set the IP 1.2.3.4 to Secure XL blacklist:<\/p>\n

# fwaccel dos blacklist -a 1.2.3.4<\/strong><\/span>
\"\"
<\/strong><\/span><\/p>\n

On gateway displays all IP’s on the SecureXL blacklist:<\/p>\n

# fwaccel dos blacklist -s<\/strong><\/span><\/p>\n

\"\"<\/strong><\/p>\n

On gateway delete the IP 1.2.3.4 from Secure XL blacklist:<\/p>\n

#\u00a0 fwaccel dos blacklist -d 1.2.3.4<\/strong><\/span><\/p>\n

\"\"<\/strong><\/p>\n\n\n\n
Penalty Box<\/span><\/th>\n<\/tr>\n<\/thead>\n<\/table>\n

Tip 2
<\/strong><\/span>Controls the Penalty Box whitelist in SecureXL.<\/p>\n

The SecureXL Penalty Box is a mechanism that performs an early drop of packets that arrive from suspected sources. The purpose of this feature is to allow the Security Gateway to cope better under high traffic load, possibly caused by a DoS\/DDoS attack. The SecureXL Penalty Box detects clients that sends packets, which the Access Control Policy drops, and clients that violate the IPS protections. If the SecureXL Penalty Box detect a specific client frequently, it puts that client in a penalty box. From that point, SecureXL drops all packets that arrive from the blocked source IP address.<\/p>\n

The Penalty Box whitelist in SecureXL lets you configure the source IP addresses, which the SecureXL Penalty Box never blocks. What is the SecureXL penalty box mechanism for offending IP addresses?<\/a>\u00a0<\/p>\n\n\n\n
Penalty Box whitelist<\/span><\/th>\n<\/tr>\n<\/thead>\n<\/table>\n

Tip 3
<\/strong><\/span>Furthermore there are also the Penalty Box whitelist in SecureXL.<\/p>\n

The SecureXL Penalty Box is a mechanism that performs an early drop of packets that arrive from suspected sources. The purpose of this feature is to allow the Security Gateway to cope better under high traffic load, possibly caused by a DoS\/DDoS attack. The SecureXL Penalty Box detects clients that sends packets, which the Access Control Policy drops, and clients that violate the IPS protections. If the SecureXL Penalty Box detect a specific client frequently, it puts that client in a penalty box. From that point, SecureXL drops all packets that arrive from the blocked source IP address. The Penalty Box whitelist in SecureXL lets you configure the source IP addresses, which the SecureXL Penalty Box never blocks.<\/p>\n\n\n\n
References<\/span><\/th>\n<\/tr>\n<\/thead>\n<\/table>\n

What is the SecureXL penalty box mechanism for offending IP addresses?<\/a>\u00a0
Command Line Interface R80.20 Reference Guide<\/a>\u00a0
Performance Tuning R80.20 Administration Guide<\/a>\u00a0
How to create and view Suspicious Activity Monitoring (SAM) Rules<\/a>\u00a0<\/p>\n

Copyright by Heiko Ankenbrand<\/a>\u00a0 1994-2019<\/p>\n","protected":false},"excerpt":{"rendered":"

R80.x Performance Tuning Tip \u2013 DDoS \u201efw sam\u201c vs. \u201efwaccel dos\u201c What is SecureXL penalty box? The SecureXL penalty box is a mechanism that performs an early drop of packets arriving from suspected sources. This mechanism is supported starting in R75.40VS. Why not sam policy rules? The SAM policy rules consume some CPU resources on<\/p>\n

Read More \u2192<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1068,"menu_order":6,"comment_status":"closed","ping_status":"closed","template":"","meta":[],"_links":{"self":[{"href":"https:\/\/www.ankenbrand24.de\/index.php\/wp-json\/wp\/v2\/pages\/1124"}],"collection":[{"href":"https:\/\/www.ankenbrand24.de\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.ankenbrand24.de\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.ankenbrand24.de\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ankenbrand24.de\/index.php\/wp-json\/wp\/v2\/comments?post=1124"}],"version-history":[{"count":3,"href":"https:\/\/www.ankenbrand24.de\/index.php\/wp-json\/wp\/v2\/pages\/1124\/revisions"}],"predecessor-version":[{"id":1132,"href":"https:\/\/www.ankenbrand24.de\/index.php\/wp-json\/wp\/v2\/pages\/1124\/revisions\/1132"}],"up":[{"embeddable":true,"href":"https:\/\/www.ankenbrand24.de\/index.php\/wp-json\/wp\/v2\/pages\/1068"}],"wp:attachment":[{"href":"https:\/\/www.ankenbrand24.de\/index.php\/wp-json\/wp\/v2\/media?parent=1124"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}