ModSecurity Handbook: Getting Started - Bad Request

Recommendations

Info

Figure 2-1. The homepage of www.modsecurity.org General Resources The following resources are the bare essentials: ModSecurity web site ModSecurity’s web site [https://www.modsecurity.org] is probably going to be your main source of information. You should visit the web site from time to time, as well as subscribe to receive the updates from the blog. Official documentation The official ModSecurity documentation [https://www.modsecurity.org/documentation/] is maintained in a wiki, but copies of it are made for inclusion with every release. Issue tracker The ModSecurity issue tracker [https://www.modsecurity.org/tracker/] is the place you will want to visit for one of two reasons: to report a problem with ModSecurity itself (e.g., when you find a bug) or to check out the progress on the next (major or General Resources 19
minor) version. Before reporting any problems, go through the Support Checklist [http://www.modsecurity.org/documentation/support-request-checklist.html], which will help you assemble the information required to help resolve your problem. Providing as much information as you can will help the developers understand and replicate the problem, and provide a fix (or a workaround) quickly. Users’ mailing list The users’ mailing list [http://lists.sourceforge.net/lists/listinfo/mod-security-users] (mod-security-users@lists.sourceforge.net) is a general-purpose mailing list where you can discuss ModSecurity. Feel free to ask questions, propose improvements, and discuss ideas. That is the place where you’ll hear first about new ModSecurity versions. ModSecurity@Freshmeat If you subscribe to the users’ mailing list, you will generally find out about new versions of ModSecurity as soon as they are released. If you care only about version releases, however, you may consider subscribing to the new version notifications at the ModSecurity page at Freshmeat [http://freshmeat.net/projects/modsecurity]. Core Rules mailing list Starting with version 2, the Core Rules [http://www.owasp.org/index.php/ Category:OWASP_ModSecurity_Core_Rule_Set_Project] project is part of OWASP [http://www.owasp.org], and has a separate mailing list (owasp-modsecurity-corerule-set@lists.owasp.org). Developer Resources If you are interested in development work, you will need these: Developers’ mailing list The developers’ mailing list [https://lists.sourceforge.net/lists/listinfo/mod-security-developers] is generally a lonely place, but if you do decide to start playing with the ModSecurity source code, this list is the place to go to discuss your work. Source code access The source code of ModSecurity is hosted at a Subversion repository at SourceForge [http://sourceforge.net/projects/mod-security/develop], which allows you to access it directly or through a web-based user interface. FishEye interface If you are not looking to start developing immediately but still want to have a look at the source code of ModSecurity, I recommend that you use the ModSecurity FishEye interface [https://www.modsecurity.org/fisheye/], which is much better than the stock interface available at SourceForge. 20 Chapter 1: Introduction
Page 1 and 2: MODSECURITY HANDBOOK The Complete G
Page 3 and 4: ModSecurity Handbook Ivan Ristić
Page 5 and 6: Table of Contents Preface to the Fr
Page 7 and 8: Advanced Logging Configuration 66 I
Page 9 and 10: Initializing Records 122 Controllin
Page 11 and 12: Rule per Keyword Approach 194 Combi
Page 13 and 14: SecRequestBodyInMemoryLimit 263 Sec
Page 15 and 16: REQUEST_BODY 287 REQUEST_BODY_LENGT
Page 17 and 18: eplaceComments 304 replaceNulls 304
Page 19 and 20: streq 330 validateByteRange 330 val
Page 21 and 22: Preface I didn’t mean to write th
Page 23 and 24: chapter goes under the hood of ModS
Page 25 and 26: open source, you can extend it dire
Page 27 and 28: I User Guide This part, with its 14
Page 29 and 30: eleased in November 2002, but a few
Page 31 and 32: similar restrictions, either direct
Page 33 and 34: Embedded Because ModSecurity is an
Page 35 and 36: Request header transformation Apach
Page 37 and 38: invoke the rules specified to work
Page 39 and 40: what was read. The fourth message t
Page 41 and 42: In the example traces, you’ve obs
Page 43: Rule writing Rule writing is an ess
Page 47 and 48: 2 Installation Before you can insta
Page 49 and 50: gpg: Signature made Wed 12 Aug 2009
Page 51 and 52: Once you have determined the locati
Page 53 and 54: Compile-Time Options The configurat
Page 55 and 56: # yum install mod_security On CentO
Page 57 and 58: 3 Configuration Now that you have M
Page 59 and 60: Audit logs /opt/modsecurity/var/aud
Page 61 and 62: file, I refer to any other ModSecur
Page 63 and 64: SecRequestBodyAccess On Once this f
Page 65 and 66: Note To instruct ModSecurity to ins
Page 67 and 68: For now, we also assume that you wi
Page 69 and 70: The SecArgumentSeparator directive
Page 71 and 72: DA %{MULTIPART_DATA_AFTER}, \ HF %{
Page 73 and 74: 4 Logging This section covers the l
Page 75 and 76: One way to make debugging easier is
Page 77 and 78: the use of multiple segments is to
Page 79 and 80: Concurrent Audit Log Initially, Mod
Page 81 and 82: How Remote Logging Works Remote log
Page 83 and 84: Activating Remote Logging You will
Page 85 and 86: That’s basically all you need to
Page 87 and 88: Note Storage of intercepted files c
Page 89 and 90: print "$output\n"; Note If you need
Page 91 and 92: Dynamically Altering Logging Config
Page 93 and 94: Now you need to add a phase rule th
Page 95 and 96:
Index A Action part H header, 343 a
Page 97 and 98:
adding new variable, 235 extension
Page 99 and 100:
performance comparing rule sets, 18
Page 101 and 102:
SecChrootDir directive, 252 SecColl
Page 103:
WebApp-Info part H header, 346 web
show all

ModSecurity Handbook: Getting Started - Bad Request

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?