IBM i security is strongest when it is measured, reviewed, and adjusted. Auditing and authority collection give you the evidence needed to do that work responsibly.
Why this matters
Permissions often drift over time. A user or program may still have access long after the original reason has disappeared.
Core concepts
Audit evidence
Auditing records security-relevant activity so teams can review what happened.
Authority collection
Authority collection helps identify the permissions actually used by users and applications.
Least privilege
The goal is to keep only the access that is genuinely required.
Continuous review
Security is a process, not a one-time setup step.
Practical example
If a service account only reads a small set of files, authority collection can help confirm that it does not need broader production access.
Common mistakes
- Turning on auditing but never reviewing the results.
- Leaving overly broad access in place because it is familiar.
- Confusing temporary operational access with permanent permission needs.
Where this fits in the series
If you want the platform foundation first, read the pillar article, What Is AS400 (IBM i)? A Complete Beginner’s Guide.