<?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: how to use auditing in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-use-auditing/m-p/2785500#M78319</link>
    <description>Hi:&lt;BR /&gt;&lt;BR /&gt;It's the 'uid' that identifies an account.  '/etc/passwd' simply maps the uid value to a name.  Thus, there would be no way to distinguish your consultant from the "real" root.&lt;BR /&gt;&lt;BR /&gt;To enable auditing (accounting) have a look at the 'acct' man pages.  You can also search docs.hp.com with a string "auditing" for more information.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
    <pubDate>Tue, 13 Aug 2002 20:44:01 GMT</pubDate>
    <dc:creator>James R. Ferguson</dc:creator>
    <dc:date>2002-08-13T20:44:01Z</dc:date>
    <item>
      <title>how to use auditing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-use-auditing/m-p/2785499#M78318</link>
      <description>We have a consultant working here and we need to give him a root privileged ID, ie, an account that UID=0. We plan on turning on auditing on this ID. My question is that if we have a few other accounts that has the UID=0 which are used by other sysadmins, can auditing still tell me if certain events were triggered by consulant's account? Any thoughts/experience will be appreciated.</description>
      <pubDate>Tue, 13 Aug 2002 20:36:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-use-auditing/m-p/2785499#M78318</guid>
      <dc:creator>JIM NIU</dc:creator>
      <dc:date>2002-08-13T20:36:38Z</dc:date>
    </item>
    <item>
      <title>Re: how to use auditing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-use-auditing/m-p/2785500#M78319</link>
      <description>Hi:&lt;BR /&gt;&lt;BR /&gt;It's the 'uid' that identifies an account.  '/etc/passwd' simply maps the uid value to a name.  Thus, there would be no way to distinguish your consultant from the "real" root.&lt;BR /&gt;&lt;BR /&gt;To enable auditing (accounting) have a look at the 'acct' man pages.  You can also search docs.hp.com with a string "auditing" for more information.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Tue, 13 Aug 2002 20:44:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-use-auditing/m-p/2785500#M78319</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2002-08-13T20:44:01Z</dc:date>
    </item>
    <item>
      <title>Re: how to use auditing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-use-auditing/m-p/2785501#M78320</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;Changing the UID to 0 or 3 will not help as everything will be run by the root only and u will find it diffcult to audit. The other alternative is to restrict direct loggint to root and then the users can SU to root to run the jobs , this way you can know by /var/adm/sulog as to who had lgged in as the root .&lt;BR /&gt;&lt;BR /&gt;Another way is to ahve a restrive login like have a partial access .&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Manoj Srivstava</description>
      <pubDate>Tue, 13 Aug 2002 20:50:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-use-auditing/m-p/2785501#M78320</guid>
      <dc:creator>MANOJ SRIVASTAVA</dc:creator>
      <dc:date>2002-08-13T20:50:34Z</dc:date>
    </item>
    <item>
      <title>Re: how to use auditing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-use-auditing/m-p/2785502#M78321</link>
      <description>If they are auditors for example, the best way would be to:&lt;BR /&gt;&lt;BR /&gt;Implement 'sudo' with pre-conceived commands that they are allowed to use, with everything copied to a 'typescript' file. See man 'script'&lt;BR /&gt;&lt;BR /&gt;Sit with the consultant and run the commands yourself.&lt;BR /&gt;&lt;BR /&gt;If they are auditors, why can't they give you a script to run which you can review before it is started?&lt;BR /&gt;&lt;BR /&gt;When I've dealt with auditors, they do not under any circumstances get near a keyboard. &lt;BR /&gt;&lt;BR /&gt;If you do not implement something to safeguard yourself, you don't what if any changes have been made.</description>
      <pubDate>Tue, 13 Aug 2002 22:09:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-use-auditing/m-p/2785502#M78321</guid>
      <dc:creator>Michael Tully</dc:creator>
      <dc:date>2002-08-13T22:09:10Z</dc:date>
    </item>
    <item>
      <title>Re: how to use auditing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-use-auditing/m-p/2785503#M78322</link>
      <description>The responses here show some common confusion&lt;BR /&gt;about the difference between accounting (acct)&lt;BR /&gt;and auditing (audsys, audisp, etc.).&lt;BR /&gt;&lt;BR /&gt;If you really plan to use the auditing features&lt;BR /&gt;available within trusted mode, you should&lt;BR /&gt;be able to distinguish between the uid 0&lt;BR /&gt;accounts.  This is because each login&lt;BR /&gt;session gets an audit ID in addition to&lt;BR /&gt;a UID.  (See the man pages for getaudid,&lt;BR /&gt;setaudid, and audusr.)&lt;BR /&gt;&lt;BR /&gt;Unless your system is badly misocnfigured, the audit ID is unique for each user on the system.&lt;BR /&gt;The audit records displayed by audisp should&lt;BR /&gt;let you trace the actions of this user.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 14 Aug 2002 06:29:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-use-auditing/m-p/2785503#M78322</guid>
      <dc:creator>doug hosking</dc:creator>
      <dc:date>2002-08-14T06:29:02Z</dc:date>
    </item>
  </channel>
</rss>

