<?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 This will be seen when the in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-level-5-log-alert/m-p/2977429#M147862</link>
    <description>&lt;P&gt;This will be seen when the user goes from privileged exec mode(Hostname#) to exec&amp;nbsp;mode (Hostname&amp;gt;). So if someone logged in to the privileged exec mode and used the command "disable", it would take them back to enable mode. I think the ASA moves the user back to enable_1 by default. This is an excerpt from my ASA:&lt;/P&gt;
&lt;P&gt;CiscoASA# show curpriv &lt;BR /&gt;Username : enable_15&lt;BR /&gt;Current privilege level : 15&lt;BR /&gt;Current Mode/s : P_PRIV&lt;BR /&gt;CiscoASA# disable&lt;BR /&gt;CiscoASA&amp;gt; show curpriv&lt;BR /&gt;Username : enable_1&lt;BR /&gt;Current privilege level : 1&lt;BR /&gt;Current Mode/s : P_UNPR&lt;BR /&gt;CiscoASA&amp;gt;&lt;/P&gt;</description>
    <pubDate>Wed, 11 Jan 2017 00:36:53 GMT</pubDate>
    <dc:creator>Rahul Govindan</dc:creator>
    <dc:date>2017-01-11T00:36:53Z</dc:date>
    <item>
      <title>ASA Level 5 Log Alert</title>
      <link>https://community.cisco.com/t5/network-security/asa-level-5-log-alert/m-p/2977428#M147861</link>
      <description>&lt;P&gt;Does anyone know why this log message is generated:&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Error Message %ASA-5-502103: User priv level changed: Uname:&amp;nbsp; user From:&amp;nbsp; privilege_level To: privilege_level&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;In my case the Uname: enable_1 is not a recognized username local to the FW, is this generated because FW sees this as a form of unauthorized access?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;H3 class="p_H_Head2"&gt;&lt;SPAN class="pEM_ErrMsg"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;</description>
      <pubDate>Tue, 12 Mar 2019 08:45:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-level-5-log-alert/m-p/2977428#M147861</guid>
      <dc:creator>agoraya</dc:creator>
      <dc:date>2019-03-12T08:45:35Z</dc:date>
    </item>
    <item>
      <title>This will be seen when the</title>
      <link>https://community.cisco.com/t5/network-security/asa-level-5-log-alert/m-p/2977429#M147862</link>
      <description>&lt;P&gt;This will be seen when the user goes from privileged exec mode(Hostname#) to exec&amp;nbsp;mode (Hostname&amp;gt;). So if someone logged in to the privileged exec mode and used the command "disable", it would take them back to enable mode. I think the ASA moves the user back to enable_1 by default. This is an excerpt from my ASA:&lt;/P&gt;
&lt;P&gt;CiscoASA# show curpriv &lt;BR /&gt;Username : enable_15&lt;BR /&gt;Current privilege level : 15&lt;BR /&gt;Current Mode/s : P_PRIV&lt;BR /&gt;CiscoASA# disable&lt;BR /&gt;CiscoASA&amp;gt; show curpriv&lt;BR /&gt;Username : enable_1&lt;BR /&gt;Current privilege level : 1&lt;BR /&gt;Current Mode/s : P_UNPR&lt;BR /&gt;CiscoASA&amp;gt;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jan 2017 00:36:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-level-5-log-alert/m-p/2977429#M147862</guid>
      <dc:creator>Rahul Govindan</dc:creator>
      <dc:date>2017-01-11T00:36:53Z</dc:date>
    </item>
  </channel>
</rss>

