Difference between revisions of "Litespeed"
m (→Do the modsecurity rules work with Litespeed) |
m (→Do the modsecurity rules work with Litespeed) |
||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 5: | Line 5: | ||
== Do the modsecurity rules work with Litespeed == | == Do the modsecurity rules work with Litespeed == | ||
| − | + | '''Yes, when used with the [https://www.atomicorp.com/wiki/index.php/ASL_WAF#WAF_Tab ASL Transparent WAF (T-WAF)] in front of Litespeed all rules are supported.''' | |
| + | |||
| + | When using the rules without the ASL Transparent WAF, where the rules are only loaded directly into Litespeed, please see the official Litespeed page for what modsecurity features Litespeed supports: | ||
http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:mod_security_compatibility | http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:mod_security_compatibility | ||
| Line 11: | Line 13: | ||
Currently, if you do not use the T-WAF, this means Litespeed does not support the following features: | Currently, if you do not use the T-WAF, this means Litespeed does not support the following features: | ||
| − | # Output analysis: This means Litespeed can not inspect the output from the web server. This means rules like malware detection, malicious shell prevention, brute force protection, data loss protection and other rules that analyze the output from the web server are not supported by Litespeed, unless you use [ | + | # Output analysis: This means Litespeed can not inspect the output from the web server. This means rules like malware detection, malicious shell prevention, brute force protection, data loss protection and other rules that analyze the output from the web server are not supported by Litespeed, unless you use [https://www.atomicorp.com/wiki/index.php/ASL_WAF#WAF_Tab the ASL Transparent WAF (T-WAF) in front of Litespeed]. |
| − | # XML inspection: Litespeed has chosen to not support XML inspection, this means XML based attacks are unfortunately not protected on that platform, unless you use [ | + | # XML inspection: Litespeed has chosen to not support XML inspection, this means XML based attacks are unfortunately not protected on that platform, unless you use [https://www.atomicorp.com/wiki/index.php/ASL_WAF#WAF_Tab the ASL Transparent WAF (T-WAF) in front of Litespeed]. |
| − | # Multi-part Upload protection: Litspeed does not support scanning attached files content in multi-part upload. If you use [ | + | # Multi-part Upload protection: Litspeed does not support scanning attached files content in multi-part upload. If you use [https://www.atomicorp.com/wiki/index.php/ASL_WAF#WAF_Tab the ASL Transparent WAF (T-WAF) in front of Litespeed] you will be able to scan attached files in a multi-part upload. |
| − | # lua: This is a language that lets us construct advanced rules. Currently they are used for advanced anti-spam protection and advanced SQLi and XSS injection protection. Therefore, these types of rules are not supported by Litespeed, unless you use | + | # lua: This is a language that lets us construct advanced rules. Currently they are used for advanced anti-spam protection and advanced SQLi and XSS injection protection. Therefore, these types of rules are not supported by Litespeed, unless you use [https://www.atomicorp.com/wiki/index.php/ASL_WAF#WAF_Tab the ASL Transparent WAF (T-WAF) in front of Litespeed]. |
| − | + | ||
| − | + | ||
== How to configure a local WAF for litespeed == | == How to configure a local WAF for litespeed == | ||
| − | === ASL | + | === ASL V === |
Step 1) Log into ASL. | Step 1) Log into ASL. | ||
| Line 40: | Line 40: | ||
Step 8) Click Save | Step 8) Click Save | ||
| − | === ASL | + | === ASL 4 === |
Step 1) Log into ASL. | Step 1) Log into ASL. | ||
| Line 66: | Line 66: | ||
== I've loaded the rules into Litespeed, does that mean they work with Litespeed? == | == I've loaded the rules into Litespeed, does that mean they work with Litespeed? == | ||
| − | + | Yes, however please see the LSWS official page for what modsecurity features Litespeed supports and does not support. | |
| − | + | https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:config:mod_security-compatibility | |
Latest revision as of 16:29, 26 July 2022
Contents |
[edit] Does ASL work with LiteSpeed?
Yes, ASL is supported with LiteSpeed.
[edit] Do the modsecurity rules work with Litespeed
Yes, when used with the ASL Transparent WAF (T-WAF) in front of Litespeed all rules are supported.
When using the rules without the ASL Transparent WAF, where the rules are only loaded directly into Litespeed, please see the official Litespeed page for what modsecurity features Litespeed supports:
http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:mod_security_compatibility
Currently, if you do not use the T-WAF, this means Litespeed does not support the following features:
- Output analysis: This means Litespeed can not inspect the output from the web server. This means rules like malware detection, malicious shell prevention, brute force protection, data loss protection and other rules that analyze the output from the web server are not supported by Litespeed, unless you use the ASL Transparent WAF (T-WAF) in front of Litespeed.
- XML inspection: Litespeed has chosen to not support XML inspection, this means XML based attacks are unfortunately not protected on that platform, unless you use the ASL Transparent WAF (T-WAF) in front of Litespeed.
- Multi-part Upload protection: Litspeed does not support scanning attached files content in multi-part upload. If you use the ASL Transparent WAF (T-WAF) in front of Litespeed you will be able to scan attached files in a multi-part upload.
- lua: This is a language that lets us construct advanced rules. Currently they are used for advanced anti-spam protection and advanced SQLi and XSS injection protection. Therefore, these types of rules are not supported by Litespeed, unless you use the ASL Transparent WAF (T-WAF) in front of Litespeed.
[edit] How to configure a local WAF for litespeed
[edit] ASL V
Step 1) Log into ASL.
Step 2) Click on the "ASL" tab.
Step 3) Click on the "WAF Configuration" menu option.
Step 4) Click the "Add" button.
Step 5) In the "Add New TWAF Setting" window from the "Add protection for ..." drop down, select "Local Web Server"
Step 6) Select the port that litespeed runs on. Normally this is port 80.
Step 7) Check the SSL box
Enter the file system path to your SSL certificate, and SSL key in the "Path to SSL Certificate" and "Path to SSL Key file" boxes.
Step 8) Click Save
[edit] ASL 4
Step 1) Log into ASL.
Step 2) Click on the "Configuration" tab.
Step 3) Click on the "WAF" tab and select "WAF configuration".
Step 4) Click the "Add" button.
Step 5) Select "Local Web Server" from the "Add protection for" drop down.
Step 6) Select the port that litespeed runs on. Normally this is port 80.
Step 7) Check the SSL box
Enter the file system path to your SSL certificate, and SSL key in the "Path to SSL Certificate" and "Path to SSL Key file" boxes.
Step 8) Click Save
Note: Litespeed does not support the WAF in embedded mode.
[edit] Questions
[edit] I've loaded the rules into Litespeed, does that mean they work with Litespeed?
Yes, however please see the LSWS official page for what modsecurity features Litespeed supports and does not support.
https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:config:mod_security-compatibility
