<?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 Re: FWSM in multi context mode in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/fwsm-in-multi-context-mode/m-p/1034243#M895345</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;George&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If a user can log in to the admin context then from there they can access the system execution space and the other contexts. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However if you gave a user the ability to log in to one of the other contexts ie. contextA they would not be able to move from contextA to system execution space or any of the other contexts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So giving access to the admin context gives system administrator access to all 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>Wed, 08 Oct 2008 16:36:50 GMT</pubDate>
    <dc:creator>Jon Marshall</dc:creator>
    <dc:date>2008-10-08T16:36:50Z</dc:date>
    <item>
      <title>FWSM in multi context mode</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-in-multi-context-mode/m-p/1034242#M895343</link>
      <description>&lt;P&gt;Can anyone explain what the purpose of the admin context is? The other user contexts seem pretty self explanatory. &lt;/P&gt;&lt;P&gt;What is the purpose of admin context?&lt;/P&gt;&lt;P&gt;How is different from the other contexts?&lt;/P&gt;&lt;P&gt;What would it be used for?&lt;/P&gt;&lt;P&gt;We are going to manage the FWSM with Cisco Security Manager and are curious about how to implement the multiple contexts.&lt;/P&gt;&lt;P&gt;Any insight or info would be appreciated.&lt;/P&gt;&lt;P&gt;Thanks....&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 13:54:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-in-multi-context-mode/m-p/1034242#M895343</guid>
      <dc:creator>georgeburtz</dc:creator>
      <dc:date>2019-03-11T13:54:43Z</dc:date>
    </item>
    <item>
      <title>Re: FWSM in multi context mode</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-in-multi-context-mode/m-p/1034243#M895345</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;George&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If a user can log in to the admin context then from there they can access the system execution space and the other contexts. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However if you gave a user the ability to log in to one of the other contexts ie. contextA they would not be able to move from contextA to system execution space or any of the other contexts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So giving access to the admin context gives system administrator access to all 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>Wed, 08 Oct 2008 16:36:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-in-multi-context-mode/m-p/1034243#M895345</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2008-10-08T16:36:50Z</dc:date>
    </item>
    <item>
      <title>Re: FWSM in multi context mode</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-in-multi-context-mode/m-p/1034244#M895347</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;George,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Admin Context Configuration&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The admin context is just like any other context, except that when a user logs in to the admin context, then that user has system administrator rights and can access the system and all other contexts. The admin context is not restricted in any way, and can be used as a regular context. However, because logging into the admin context grants you administrator privileges over all contexts, you might need to restrict access to the admin context to appropriate users. The admin context must reside on Flash memory, and not remotely.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If your system is already in multiple context mode, or if you convert from single mode, the admin context is created automatically as a file on the internal Flash memory called admin.cfg. This context is named "admin." If you do not want to use admin.cfg as the admin context, you can change the admin context. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please refer the below URL for details:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/docs/security/fwsm/fwsm32/configuration/guide/contxt_f.html#wp1149689" target="_blank"&gt;http://www.cisco.com/en/US/docs/security/fwsm/fwsm32/configuration/guide/contxt_f.html#wp1149689&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Arul&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;** Please rate all helpful posts **&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Oct 2008 17:18:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-in-multi-context-mode/m-p/1034244#M895347</guid>
      <dc:creator>ajagadee</dc:creator>
      <dc:date>2008-10-08T17:18:04Z</dc:date>
    </item>
  </channel>
</rss>

