ModSecurity Handbook: Getting Started - Bad Request

Recommendations

Info

Figure 2-1. ModSecurity repository root What you probably want is located in the m2/ directory, which houses ModSecurity 2.x. Within that directory, you will find a directory structure that you will find familiar if you’ve worked with Subversion before: m2/ branches/ 2.1.x/ 2.5.x/ 2.6.x/ experimental/ [some stuff you won't care about] tags/ [all releases, one per directory] trunk/ The trunk directory always contains the most recent development version. The active branches may sometimes contain a feature or a fix that has not been released yet. The branches will always be generally stable anyway, and the risk of something breaking is minimal. 26 Chapter 2: Installation
Once you have determined the location of the version of ModSecurity that you wish to use, you can get it using the export command of Subversion, like this: $ svn export https://mod-security.svn.sourceforge.net/svnroot/mod-security/… m2/trunk modsecurity-trunk What you will get in the folder modsecurity-trunk is almost the same as what you get when you download a release. The documentation might not be in sync, however. Starting with ModSecurity 2.6, the master documentation is kept in a wiki, with copies of the wiki included with releases. Installation on Unix Before you can start to compile ModSecurity, you must ensure that you have a complete development toolchain installed. Refer to the documentation of the operating system you are using for instructions. If you’ll be adding ModSecurity to an operating system–provided Apache, you are likely to need to install a specific Apache development package, too. For example, on Debian and Ubuntu, you need to use apache2-prefork-dev or apache2-threaded-dev, depending on which deployment model (process-based or thread-based) you chose. In the next step, ensure that you have resolved all the dependencies before compilation. The dependencies are listed in Table 2.2, “ModSecurity dependencies”. Table 2.2. ModSecurity dependencies Dependency In Apache? Purpose Apache Portable Runtime [http://apr.apache.org] Yes Various APR-Util [http://apr.apache.org] Yes Various mod_unique_id Yes, but may not be installed by default Generate unique transaction ID libcurl [http://curl.haxx.se/libcurl/] No Remote logging (mlogc) libxml2 [http://xmlsoft.org] No XML processing Lua 5.1 [http://www.lua.org] No Writing complex rules in Lua (optional) PCRE [http://www.pcre.org] Yes, but cannot be used by ModSecurity Regular expression matching If you already have Apache installed, you will only ever need to deal with libcurl, libxml2, and Lua. With Apache compiled from source, you will also need the PCRE library. Although Apache comes bundled with one, it is used in a way that does not allow other modules to access it. To work around this issue, install PCRE separately and then tell Apache to use the external copy. I explain how to do that later in this section. Installation on Unix 27
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 and 44: Rule writing Rule writing is an ess
Page 45 and 46: minor) version. Before reporting an
Page 47 and 48: 2 Installation Before you can insta
Page 49: gpg: Signature made Wed 12 Aug 2009
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?