{"id":249,"date":"2013-04-15T00:50:19","date_gmt":"2013-04-15T00:50:19","guid":{"rendered":"http:\/\/deoss.net\/info\/?p=249"},"modified":"2013-04-16T23:20:50","modified_gmt":"2013-04-16T23:20:50","slug":"ddos-attack-update","status":"publish","type":"post","link":"https:\/\/deoss.net\/info\/2013\/04\/15\/ddos-attack-update\/","title":{"rendered":"DDoS attack update"},"content":{"rendered":"<p><strong>Good news is that DEOSS is now back on line and running reasonably well. However, I don&#8217;t anticipate that the bad guys will be giving up anytime soon.<\/strong><\/p>\n<p>Consequently, I have been forced to impose some very tight security restrictions in order to fight of this ongoing DDoS attack. The server logs indicate that we are currently experiencing 1 attack every 4 seconds &#8211; though at one point it was 10 attacks per second! To fight them off I have deployed a WAF (<span style=\"text-decoration: underline;\">w<\/span>eb <span style=\"text-decoration: underline;\">a<\/span>pplication <span style=\"text-decoration: underline;\">f<\/span>irewall) called ModSecurity &#8211; amongst a number of other measures. It is a very powerful tool and is holding up well. However its configuration is very poorly documented and its settings are virtually incomprehensible!<\/p>\n<p>In addition I have had to create my own directives to respond to the particular attack we are experiencing. This means that while I finetune the new security measures to suit all the various web applications on DEOSS, you may get experience some &#8220;<em>error 403&#8217;s<\/em>&#8220;. This is the default response of the WAF to anything it considers a threat. So if you are a DEOSS customer and you experience unexpected &#8220;<em>403&#8217;s<\/em>&#8221; then please let me know about them, through the normal channels.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Good news is that DEOSS is now back on line and running reasonably well. However, I don&#8217;t anticipate that the bad guys will be giving up anytime soon. Consequently, I have been forced to impose some very tight security restrictions &hellip; <a href=\"https:\/\/deoss.net\/info\/2013\/04\/15\/ddos-attack-update\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,3],"tags":[],"class_list":["post-249","post","type-post","status-publish","format-standard","hentry","category-good-news","category-server-news"],"_links":{"self":[{"href":"https:\/\/deoss.net\/info\/wp-json\/wp\/v2\/posts\/249","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/deoss.net\/info\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/deoss.net\/info\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/deoss.net\/info\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/deoss.net\/info\/wp-json\/wp\/v2\/comments?post=249"}],"version-history":[{"count":4,"href":"https:\/\/deoss.net\/info\/wp-json\/wp\/v2\/posts\/249\/revisions"}],"predecessor-version":[{"id":262,"href":"https:\/\/deoss.net\/info\/wp-json\/wp\/v2\/posts\/249\/revisions\/262"}],"wp:attachment":[{"href":"https:\/\/deoss.net\/info\/wp-json\/wp\/v2\/media?parent=249"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/deoss.net\/info\/wp-json\/wp\/v2\/categories?post=249"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/deoss.net\/info\/wp-json\/wp\/v2\/tags?post=249"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}