<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Blocking Blogs and Forums &amp;quot;Manually&amp;quot; in Web Security</title>
    <link>https://community.cisco.com/t5/web-security/blocking-blogs-and-forums-quot-manually-quot/m-p/1150905#M487</link>
    <description>&lt;P&gt;Sorry about the title - couldn't think of a clever way of saying this!!&lt;BR /&gt;&lt;BR /&gt;We have recently replaced our outdated proxy and filtering solution with a pair of IronPort appliances and are generally pleased with them.&lt;BR /&gt;&lt;BR /&gt;However, one thing that has come up on a few occassions is that, even though the category Blogs &amp;amp; Forums is blocked for most users, there are still a large number of Blog/Forum sites that people can get to.&lt;BR /&gt;&lt;BR /&gt;I understand that a URL category filter couldn't possibly cover every site, especially given the speed at which new ones appear.&lt;BR /&gt;&lt;BR /&gt;What I'm wondering is if anyone has had any success with blocking these sites using a Custom URL Category with a keyword filter. My idea is that this keyword filter could look for "/blog", "/forum" etc. within a URL and then block it based on the assumption that it is a blog or forum.&lt;BR /&gt;&lt;BR /&gt;If anyone has done something like this and is wiliing to share details of how they did it I would greatly appreciate it!  &lt;span class="lia-unicode-emoji" title=":grinning_face_with_smiling_eyes:"&gt;😄&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 07 Jan 2009 17:22:39 GMT</pubDate>
    <dc:creator>dingall</dc:creator>
    <dc:date>2009-01-07T17:22:39Z</dc:date>
    <item>
      <title>Blocking Blogs and Forums "Manually"</title>
      <link>https://community.cisco.com/t5/web-security/blocking-blogs-and-forums-quot-manually-quot/m-p/1150905#M487</link>
      <description>&lt;P&gt;Sorry about the title - couldn't think of a clever way of saying this!!&lt;BR /&gt;&lt;BR /&gt;We have recently replaced our outdated proxy and filtering solution with a pair of IronPort appliances and are generally pleased with them.&lt;BR /&gt;&lt;BR /&gt;However, one thing that has come up on a few occassions is that, even though the category Blogs &amp;amp; Forums is blocked for most users, there are still a large number of Blog/Forum sites that people can get to.&lt;BR /&gt;&lt;BR /&gt;I understand that a URL category filter couldn't possibly cover every site, especially given the speed at which new ones appear.&lt;BR /&gt;&lt;BR /&gt;What I'm wondering is if anyone has had any success with blocking these sites using a Custom URL Category with a keyword filter. My idea is that this keyword filter could look for "/blog", "/forum" etc. within a URL and then block it based on the assumption that it is a blog or forum.&lt;BR /&gt;&lt;BR /&gt;If anyone has done something like this and is wiliing to share details of how they did it I would greatly appreciate it!  &lt;span class="lia-unicode-emoji" title=":grinning_face_with_smiling_eyes:"&gt;😄&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jan 2009 17:22:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/web-security/blocking-blogs-and-forums-quot-manually-quot/m-p/1150905#M487</guid>
      <dc:creator>dingall</dc:creator>
      <dc:date>2009-01-07T17:22:39Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking Blogs and Forums "Manually"</title>
      <link>https://community.cisco.com/t5/web-security/blocking-blogs-and-forums-quot-manually-quot/m-p/1150906#M488</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;dangerousd,&lt;BR /&gt;&lt;BR /&gt;You can definitely block based on regex keyword. I'm not sure how effective this would really be though.&lt;BR /&gt;&lt;BR /&gt;Are you able to verify if the blog and forum pages not categorized contain the work 'blog' or 'forum' somewhere in the URL?&lt;BR /&gt;&lt;BR /&gt;You could certain try this with little overhead (assuming the regex doesn't contain a .*) and then grep the access logs to verify what is hitting this new category.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Jan 2009 00:05:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/web-security/blocking-blogs-and-forums-quot-manually-quot/m-p/1150906#M488</guid>
      <dc:creator>jowolfer</dc:creator>
      <dc:date>2009-01-08T00:05:05Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking Blogs and Forums "Manually"</title>
      <link>https://community.cisco.com/t5/web-security/blocking-blogs-and-forums-quot-manually-quot/m-p/1150907#M489</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Josh. We had someone from IronPort on site a few days ago to provide some training. He agreed with what you said, so I may give that a go at some point.&lt;BR /&gt;&lt;BR /&gt;A lot of the sites we've found which contain blogs that aren't being blocked by IronPort do have obvious keywords in the URL somewhere - most commonly &lt;A href="https://community.cisco.com/www.site.com/blog" target="_blank"&gt;www.site.com/blog&lt;/A&gt; or blog.site.com - or something along those lines.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Jan 2009 22:50:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/web-security/blocking-blogs-and-forums-quot-manually-quot/m-p/1150907#M489</guid>
      <dc:creator>dingall</dc:creator>
      <dc:date>2009-01-28T22:50:43Z</dc:date>
    </item>
  </channel>
</rss>

