07-08-2008
Parsing Powerbroker Logs for SysAdmin Changes (SOX)
I need to identify a list of AIX command strings that can be used to parse Powerbroker logs for changes that are being made by Unix SysAdmins. Need to filter out (as much as possible) inquiry or routine maintenance activity and concentrate on software/security changes.
This is for internal SOX monitoring (control self-assessment) - I am not an auditor.
Can anyone help? Suggestions?
6 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have a requirement to be able to issue selected commands with root privileges but don't have the ability to su to root due to audit requirements dictating that only our UNIX SA's have that feature.
I was told that Powerbroker would allow me to run the commands as root but our security people... (1 Reply)
Discussion started by: yvs24
1 Replies
2. UNIX for Advanced & Expert Users
Hello,
I am trying to convince my boss to stop allowing our users to login as root (superuser). Currently our users login to our unix server with their own account, then as needed, they will do an su and put in the root password.
This scares me, for a bunch of reasons. Mainly, one is that we... (1 Reply)
Discussion started by: rwallaceisg
1 Replies
3. Shell Programming and Scripting
My file will contain following(log.txt):
start testcase: config loading
......
error XXXX
.....
end testcase: config loading, result failed
start testcase: ping check
.....
error ZZZZZ
.....
error AAAAA
end testcase: Ping check, result failed
I am expecting below output. ... (4 Replies)
Discussion started by: shellscripter
4 Replies
4. Shell Programming and Scripting
Sorry, couldn't really think of a simple subject/title.
So, I have a log file, and the dates are displayed like so:
2009-03-05 02:49:44
So the first and second field are the date/time. I can change them into a unix timestamp easily with:
date -d "2009-03-05 02:49:44" +%s
However,... (17 Replies)
Discussion started by: Rhije
17 Replies
5. Shell Programming and Scripting
I would like to parse through some logs looking for things like exception or failed (grep -i failed). Ideal would be if it were in a menu format so someone without unix ability could just choose option 1 2 or 3 etc. If I could pass the hostname to a variable also that would be awesome, so someone... (5 Replies)
Discussion started by: taekwondo
5 Replies
6. UNIX and Linux Applications
Right now I am parsing Tuxedo logs to calculate response times for various services. I was hoping to find a log tool that had support for Tuxedo and would generate drill down html reports.
---------- Post updated at 02:35 PM ---------- Previous update was at 02:33 PM ----------
I just wanted... (0 Replies)
Discussion started by: Lurch
0 Replies
LEARN ABOUT OPENSOLARIS
inquiry-serial-no
inquiry-device-type(9P) Kernel Properties for Drivers inquiry-device-type(9P)
NAME
inquiry-device-type, inquiry-vendor-id, inquiry-product-id, inquiry-revision-id, inquiry-serial-no - inquiry properties for SCSI devices
DESCRIPTION
These are optional properties, typically created by the system, for SCSI target devices. References to these properties should use their
sys/scsi/impl/inquiry.h defined names.
inquiry-device-type is an integer property. When present, the least significant byte of the value indicates the device type as defined by
the SCSI standard. Consumers of this property should compare the property values with DTYPE_* values defined in sys/scsi/generic/inquiry.h.
inquiry-vendor-id is a string property. When present, it contains the vendor information. This information typically comes from the
scsi_inquiry(9S) "inq_vid" field.
inquiry-product-id is a string property. When present, it contains the product identification. This information typically comes from the
scsi_inquiry(9S) "inq_pid" field.
inquiry-revision-id is a string property. When present, it contains the product revision. This revision typically comes from the
scsi_inquiry(9S) "inq_rev" field.
inquiry-serial-no is a string property. When present, it contains the serial number. The serial number is typically obtained from the EVPD
"Unit Serial Number" SCSI INQUIRY data (page 0x80).
SEE ALSO
scsi_inquiry(9S)
Writing Device Drivers
NOTES
Values established at tran_tgt_init(9E) time by an HBA driver take precedence over values established by the system, and HBA driver values
may not be the same length as the typical scsi_inquiry(9S) field.
SunOS 5.11 18 May 2001 inquiry-device-type(9P)