<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>owasp on Privacy, Power, &amp; Protection In The Cyber Century</title>
    <link>https://blog.eutopian.io/tags/owasp/</link>
    <description>Recent content in owasp on Privacy, Power, &amp; Protection In The Cyber Century</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <copyright>All rights reserved - 2017</copyright>
    <lastBuildDate>Wed, 31 May 2017 21:23:30 +0000</lastBuildDate><atom:link href="https://blog.eutopian.io/tags/owasp/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Elephant Proofing Your Web Servers</title>
      <link>https://blog.eutopian.io/elephant-proofing-your-web-servers/</link>
      <pubDate>Wed, 31 May 2017 21:23:30 +0000</pubDate>
      
      <guid>https://blog.eutopian.io/elephant-proofing-your-web-servers/</guid>
      <description>750 words, 3 minutes. The Case For Default Deny What&amp;rsquo;s free, permanently reduces your exposure to a range of potential vulnerabilities, requires no maintenance, and takes only a few minutes to implement?
Most web servers are installed to serve content to unauthenticated users on the Internet. Most only have a finite list of URLs or a specific number of web apps. I&amp;rsquo;ve always thought it strange that they install in a default-permit mode.</description>
    </item>
    
  </channel>
</rss>
