How To
Summary
How to determine which user ID invoked an audit event.
Steps
The following example logs /usr/bin/ps events. This example does not cover log management, or other audit configuration details. The example assumes the "/audit" file system exists. See the "Support" section in this note for references.
1) Modify config:start options.
|
# vi /etc/security/audit/config
start:
binmode = off streammode = on ignorenonexistentity = no |
|
# vi /etc/security/audit/objects
/usr/bin/ps:
x = "PS_EXEC" Format:
/path/to/file:
access_mode = "audit_event " An audit-event name can be up to 15 bytes long; longer names are rejected. Valid access modes are read (r), write (w), and execute (x) modes. For directories, search mode is substituted for execute mode. |
|
* /usr/bin/ps
PS_EXEC = printf " %s " Format:
* Is a comment character
AuditEvent = FormatCommand
|
|
Include the "l and r" flags for the logs:
-l The login name of the user.
-r The real user name.
# vi /etc/security/audit/streamcmds:
/usr/sbin/auditstream | /usr/sbin/auditselect -e "event == PS_EXEC" | auditpr -htpPceRlr -w > /audit/stream.out &
|
5) Stop and restart audit.
|
# audit shutdown
# audit start |
|
A) root login:
# ps
B) root login:
# su - userA -c ps
C) userA login:
# sudo ps
|
|
# cat /audit/stream.out
time process parent command event status l
ogin real ------------------------ -------- -------- ------------------------------- --------------- ----------- - ------- -------- Sun May 14 06:55:27 2023 10748250 8126816 ps PS_EXEC OK r oot root audit object exec event detected /usr/bin/ps Sun May 14 06:55:29 2023 10748252 8126816 ps PS_EXEC OK r oot userA audit object exec event detected /usr/bin/ps Sun May 14 06:55:32 2023 10748254 9437590 ps PS_EXEC OK u serA userA audit object exec event detected /usr/bin/ps |
Additional Information
| SUPPORT |
|---|
|
Security configuration involves comprehensive features. Most of these features require advanced review and planning by administrators who are familiar with all of their system requirements. AIX Support does not make specific recommendations to harden your system. Customization is out of the scope of AIX Support, but if you have specific questions about documented usage, our support experts are happy to assist.
You can learn more about the audit functionality on AIX and best practices through the following resources:
If you have specific questions about usage after reviewing the recommended documentation, IBM AIX Support will be happy to assist. If you require consulting services, there are more fee-based services available.
If you require usage assistance, use the following step-by-step instructions to contact IBM to open a case for software with an active and valid support contract.
1. Document (or collect screen captures of) all symptoms, errors, and messages related to your issue. 2. Capture any logs or data relevant to the situation. 3. Contact IBM to open a case: -For electronic support, see the IBM Support Community: 4. Provide a clear, concise description of the issue. - For guidance, see: Working with IBM AIX Support: Describing the problem
5. If the system is accessible, collect a system snap, and upload all of the details and data for your case. - For guidance, see: Working with IBM AIX Support: Collecting snap data |
Related Information
Was this topic helpful?
Document Information
Modified date:
25 May 2023
UID
ibm16482223