- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Auditing for actions on a specific file
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2004 05:50 AM
07-15-2004 05:50 AM
Auditing for actions on a specific file
I would like to know who and when the file was created, read, and deleted. Changes in permissions would be good as well.
All of this information is in the audit files, but the audisp command doesn't seem to work this way.
Is there another tool for reading these files?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2004 05:57 AM
07-15-2004 05:57 AM
Re: Auditing for actions on a specific file
You can audit the system calls that may be specific to file changes, but not a particular file.
Unix keeps the three times with respect to file/dir.
ll -c --> Change time. Change time is the creation time, till the time file is not chnaged. Once the ctime is modified, creation time can not be known.
ll -u --> Access time. (atime) When a file was accessed.
ll -t --> Modification time (mtime)
You may look into VCS, Clearcase etc for this.
Anil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2004 10:50 PM
07-15-2004 10:50 PM
Re: Auditing for actions on a specific file
audisp is the only HP supplied tool that I'm aware of that can read the files. If it's not sufficient then you could write your own tool to read the the auditing files; audit(4) contains information on the structure of the files.
regards,
Darren.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2004 08:09 AM
07-16-2004 08:09 AM
Re: Auditing for actions on a specific file
Is there a more complete reference, or perhaps a sample program someone has written that I could modify for my own needs?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2004 08:25 AM
07-16-2004 08:25 AM
Re: Auditing for actions on a specific file
HTH
-- Rod Hills
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2004 04:10 AM
07-17-2004 04:10 AM
Re: Auditing for actions on a specific file
We can know the auditing results easily with audisp commands. If you enable the events for auditing with SAM then use as audisp -e
We can get the auding file information as,
# audsys
auditing system is currently off
current file: /.secure/etc/audfile1
next file: /.secure/etc/audfile2
statistics- afs Kb used Kb avail % fs Kb used Kb avail %
current file: 1000 38 96 59981824 15186496 75
next file: 1000 0 100 59981824 15186496 75
(or)
with /etc/rc.config.d/auditing configuration file. It will contain the present auditing file and replacing auditing file.
filename structure contains informations as (audit pathname cnode, audit pathname device, audit pathname inode,
audit pathname length, audit pathname in characters, ptr to next filename )
pathname device - use bdf
BDF>>
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 59981824 15186496 44461696 25% /
du>>
80 /.secure/etc/audfile1
pathname inode - use df
DF>>
/ (/dev/vg00/lvol3 ): 88923392 blocks 1399840 i-nodes
To know the file permission and time ( creation,modify,change ) use the ll command ( use RAC's response to know more)
Use the audomon to get the warning or notification about the audit files overflow and auditfile stoage informations. See audomon man page for more details.
Add all the features in a simple shell script to know about all informations of a auditing file.
Regards,
Muthukumar.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2004 04:57 AM
07-17-2004 04:57 AM
Re: Auditing for actions on a specific file
attached script may be useful to know about auditing files details,auditing space usage and auditing enablement check.
Regards,
Muthukumar.