<?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 ASA-5510 - Security Contexts required? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-5510-security-contexts-required/m-p/1023627#M940363</link>
    <description>&lt;P&gt;I'm looking to deploy an ASA-5510 as our internet firewall.  We'll be using a DS3 coming into a Cisco 3845 router and we want to service 4 different, NATed networks.  My question is, can the ASA-5510 with a Base license service the needs of all three networks, or do we need to upgrade and enable security contexts?  If we don't need them, are there any advantages to having security contexts in this situation?  Thanks. &lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 12:22:08 GMT</pubDate>
    <dc:creator>ssewallatrc</dc:creator>
    <dc:date>2019-03-11T12:22:08Z</dc:date>
    <item>
      <title>ASA-5510 - Security Contexts required?</title>
      <link>https://community.cisco.com/t5/network-security/asa-5510-security-contexts-required/m-p/1023627#M940363</link>
      <description>&lt;P&gt;I'm looking to deploy an ASA-5510 as our internet firewall.  We'll be using a DS3 coming into a Cisco 3845 router and we want to service 4 different, NATed networks.  My question is, can the ASA-5510 with a Base license service the needs of all three networks, or do we need to upgrade and enable security contexts?  If we don't need them, are there any advantages to having security contexts in this situation?  Thanks. &lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 12:22:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5510-security-contexts-required/m-p/1023627#M940363</guid>
      <dc:creator>ssewallatrc</dc:creator>
      <dc:date>2019-03-11T12:22:08Z</dc:date>
    </item>
    <item>
      <title>Re: ASA-5510 - Security Contexts required?</title>
      <link>https://community.cisco.com/t5/network-security/asa-5510-security-contexts-required/m-p/1023628#M940364</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You don't really need security contexts if you are simply natting 4 different networks, the 5510 will do this quite easily with a single context. You can still have separation between the networks with DMZ's etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However if you need absolute separation between these 4 networks, for example they are 4 separate customers then you may well want to consider using security contexts. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Mar 2008 20:15:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5510-security-contexts-required/m-p/1023628#M940364</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2008-03-25T20:15:42Z</dc:date>
    </item>
    <item>
      <title>Re: ASA-5510 - Security Contexts required?</title>
      <link>https://community.cisco.com/t5/network-security/asa-5510-security-contexts-required/m-p/1023629#M940365</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;just to add to that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Common Uses for Security Contexts &lt;/P&gt;&lt;P&gt;You might want to use multiple security contexts in the following situations: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;â&amp;#128;¢You are a service provider and want to sell security services to many customers. By enabling multiple security contexts on the security appliance, you can implement a cost-effective, space-saving solution that keeps all customer traffic separate and secure, and also eases configuration. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;â&amp;#128;¢You are a large enterprise or a college campus and want to keep departments completely separate. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;â&amp;#128;¢You are an enterprise that wants to provide distinct security policies to different departments. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;â&amp;#128;¢You have any network that requires more than one security appliance. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unsupported Features &lt;/P&gt;&lt;P&gt;Multiple context mode does not support the following features: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;â&amp;#128;¢Dynamic routing protocols &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Security contexts support only static routes. You cannot enable OSPF, RIP, or EIGRP in multiple context mode. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;â&amp;#128;¢VPN &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;â&amp;#128;¢Multicast routing. Multicast bridging is supported. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;â&amp;#128;¢Threat Detection &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Franco&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Mar 2008 21:19:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5510-security-contexts-required/m-p/1023629#M940365</guid>
      <dc:creator>francisco_1</dc:creator>
      <dc:date>2008-03-25T21:19:54Z</dc:date>
    </item>
    <item>
      <title>Re: ASA-5510 - Security Contexts required?</title>
      <link>https://community.cisco.com/t5/network-security/asa-5510-security-contexts-required/m-p/1023630#M940366</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the reply.  Basically, I'll have one of the 4 networks with a more "liberal" security policy and the other 3 can have the same, more restrictive policy.  As long as I can keep the 1 liberal network away from the other 3, I'm happy. The ASA-5510 base shouldn't have a problem with this?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Mar 2008 17:35:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5510-security-contexts-required/m-p/1023630#M940366</guid>
      <dc:creator>ssewallatrc</dc:creator>
      <dc:date>2008-03-26T17:35:02Z</dc:date>
    </item>
  </channel>
</rss>

