<div dir="ltr">Hello Jeremy,<br>Thanks for the info, I'm sure our website guru Dan will be looking into ways of securing the server if we go down a PHP CMS route. I dont have logon to the server myself.<br><br>Cheers,<br>
<br>Nathan. <br><br><div class="gmail_quote">On Mon, Sep 29, 2008 at 8:40 PM, Jeremy Hooks <span dir="ltr"><<a href="mailto:jeremyhooks@googlemail.com">jeremyhooks@googlemail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div dir="ltr">Hi Nathan (and anyone else interested)<div><br></div><div>Just a quick email regarding installing ModSecurity on the new server, which we spoke about briefly at the meeting yesterday. I am happy to install ModSecurity and help any other server administration, but I am new to the group so I will understand if you don't want to give me access right away</div>
<div><br></div><div>In case you've not come across it before, ModSecurity is an opensource (GPL) web application firewall. Basically, it sits between Apache and any server side scripting/CGI and runs all requests against a list common exploits (negative security) and/or a list of valid requests (positive security) - depending on the ruleset used.</div>
<div><br></div><div>There are two common rules-sets. Breach's (the company behind ModSec) core rules, which is fully opensource and GotRoot's rules which is more proprietary - still plain text but it is released to non-subscribers after 30 days delay. </div>
<div><br></div><div>As I understand it, the core rules are quite generic and offer good protection against a lots of common known and unknown exploits - however it errs on the side of security, so it can some times break parts of a web app. (usually because they are doing something a little unwise). Got Root seem to be built around common applications and is (probably) more actively developed, however this does mean the ruleset is larger and there will probably more of a performance hit. It might be best to start of using both rulesets (I think Got Root is designed to be able to work) and change this if we run into problems (I will check the modsec lists to see if anyone sees a problem with this).</div>
<div><br></div><div>The is also another product from Breach which is worth considering, ModSecurity Console. It is a proprietary app. but it is free for none up to 3 nodes (servers). It basically makes life easier if you want to actively monitor your logs. I haven't tried it, so far I have been happy greping the log files when I have a problem.</div>
<div><br></div><div>I don't pretend to know a lot about ModSec (probably not even 5% of all there is to know), but I am confident that I can set it up and drastically improve the security of the web server. I have been using it for more than two years on our dedicated remote host at work and we haven't had any problem despite running horribly insecure PHP (horde, mambo (now joomla), amongst others).</div>
<div><br></div><div>Regards.</div><div><br></div><font color="#888888"><div>Jeremy.</div></font></div>
<br>_______________________________________________<br>
Kent mailing list<br>
<a href="mailto:Kent@mailman.lug.org.uk">Kent@mailman.lug.org.uk</a><br>
<a href="https://mailman.lug.org.uk/mailman/listinfo/kent" target="_blank">https://mailman.lug.org.uk/mailman/listinfo/kent</a><br></blockquote></div><br></div>