<?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 IDSM - Login and Command History in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/idsm-login-and-command-history/m-p/1200480#M77028</link>
    <description>&lt;P&gt;Hi, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How can the login and command history/log along with timestamp be configured on IDSM modules.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;</description>
    <pubDate>Sun, 10 Mar 2019 11:38:57 GMT</pubDate>
    <dc:creator>cisco_lite</dc:creator>
    <dc:date>2019-03-10T11:38:57Z</dc:date>
    <item>
      <title>IDSM - Login and Command History</title>
      <link>https://community.cisco.com/t5/network-security/idsm-login-and-command-history/m-p/1200480#M77028</link>
      <description>&lt;P&gt;Hi, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How can the login and command history/log along with timestamp be configured on IDSM modules.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 11:38:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/idsm-login-and-command-history/m-p/1200480#M77028</guid>
      <dc:creator>cisco_lite</dc:creator>
      <dc:date>2019-03-10T11:38:57Z</dc:date>
    </item>
    <item>
      <title>Re: IDSM - Login and Command History</title>
      <link>https://community.cisco.com/t5/network-security/idsm-login-and-command-history/m-p/1200481#M77029</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm sorry to tell you it can't be configured because that feature doesn;t exist. There is an event generated when a user logs in that can be seen in the event database, aong with a boatload of other system events (show events past 23:59), but no command history logs.&lt;/P&gt;&lt;P&gt;For a security device, it has very little security in and of itself. No AAA, multiple logins on the same username permitted, no forced password change (unless you count the default password). &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Jun 2009 19:33:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/idsm-login-and-command-history/m-p/1200481#M77029</guid>
      <dc:creator>rhermes</dc:creator>
      <dc:date>2009-06-02T19:33:59Z</dc:date>
    </item>
    <item>
      <title>Re: IDSM - Login and Command History</title>
      <link>https://community.cisco.com/t5/network-security/idsm-login-and-command-history/m-p/1200482#M77030</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The modules don't support AAA, therefore they cannot do any 'accounting'. Syslogs are not supported either.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You might be able to get this information from the UNIX backend (regarding who is logging in, and not the commands). But this would not be reocmmended, and perhaps not supported by TAC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Farrukh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Jun 2009 05:46:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/idsm-login-and-command-history/m-p/1200482#M77030</guid>
      <dc:creator>Farrukh Haroon</dc:creator>
      <dc:date>2009-06-03T05:46:43Z</dc:date>
    </item>
  </channel>
</rss>

