<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Object-Group on Aaron&#39;s Worthless Words</title>
    <link>https://a996c8ee.aww-3cz.pages.dev/tags/object-group/</link>
    <description>Recent content in Object-Group on Aaron&#39;s Worthless Words</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 05 Apr 2010 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://a996c8ee.aww-3cz.pages.dev/tags/object-group/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>More ASA Objects and Object-groups</title>
      <link>https://a996c8ee.aww-3cz.pages.dev/posts/2010/04/more-asa-objects-and-object-groups/</link>
      <pubDate>Mon, 05 Apr 2010 00:00:00 +0000</pubDate>
      <guid>https://a996c8ee.aww-3cz.pages.dev/posts/2010/04/more-asa-objects-and-object-groups/</guid>
      <description>&lt;p&gt;A few years ago, I developed a Perl-based application that take a template file and pukes out standardized access rules for new hosts as they&amp;rsquo;re added to the network.  This works great for making sure that each host is able to be managed properly.  This solution, however, is not very flexible.  If I need to remove a host&amp;rsquo;s access, I may have to take out 20 rules individually.  That&amp;rsquo;s not really cool, so, at the suggestion of a coworker, I&amp;rsquo;m working on a solution that uses objects, object-groups, and nested object-groups.  This should minimize the configured rules and allow new host rules to be added and removed by simply adding hosts to object-groups.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Using SPF Records To Build Objects</title>
      <link>https://a996c8ee.aww-3cz.pages.dev/posts/2009/10/using-spf-records-to-build-objects/</link>
      <pubDate>Fri, 16 Oct 2009 00:00:00 +0000</pubDate>
      <guid>https://a996c8ee.aww-3cz.pages.dev/posts/2009/10/using-spf-records-to-build-objects/</guid>
      <description>&lt;p&gt;My biggest complain about modern firewalls is their lack of the ability to create rules based on URLs or HTTP streams; you have to open access between IP addresses.  Yes, I know there are other means to do that, but I want my ASA/PIX/FWSM to do it without making me do so much work.&lt;/p&gt;&#xA;&lt;p&gt;Anyway, the fact that you have to use IPs brings up some interesting problems.  Let&amp;rsquo;s say you have a server in a DMZ that needs to query Google for some content.  Since you&amp;rsquo;re a hard-ass network guy like I am, you tell the admin that they have provide the data flow they want to use &amp;ndash; source IP, destination IP, protocol, port.  They come back and tell you that they need their server to connect via HTTP to 74.125.45.100.  You put in the rules as given, but the IP has suddenly changed on you.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Object Groups in the ASA/FWSM/PIX</title>
      <link>https://a996c8ee.aww-3cz.pages.dev/posts/2009/10/object-groups-in-the-asafwsmpix/</link>
      <pubDate>Thu, 01 Oct 2009 00:00:00 +0000</pubDate>
      <guid>https://a996c8ee.aww-3cz.pages.dev/posts/2009/10/object-groups-in-the-asafwsmpix/</guid>
      <description>&lt;p&gt;I can&amp;rsquo;t believe I haven&amp;rsquo;t talked about &lt;em&gt;object-groups&lt;/em&gt; yet.  I had a whole other blog entry written up, and, when I went to link things over, I realized I couldn&amp;rsquo;t find an intro to it.  Here it goes.&lt;/p&gt;&#xA;&lt;p&gt;Welcome to the modern world.  A world of wonder.  A world of quickly-advancing technology.  A world where clusters of machines sit behind load balancers for scalability and availability.  A world where those clusters need access to other clusters.  A world where your firewall rulebase gets so big that it&amp;rsquo;s unreadable without some help.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
