A service log might report that a page was loaded. An audit record can describe an action your system was configured to observe, such as writing a service configuration. Begin by deciding which action matters and what information you need to review it.
System Auditing · Lesson 1
Audit Events
Learn to choose auditable events that answer a question about a protected file.
Choosing an Audit Question
Suppose the web service's configuration controls who can open a preview. You want to review changes to that file. A useful record would name the object, operation, time, account context, and result. Each field helps someone reconstruct one part of the action.
What should an audit record identify for this review?
Reading the Result
A record can describe a successful write or an unsuccessful attempt. Keep both the operation and its result in view. A denied write can be useful evidence of an attempt. It gives a different conclusion from a successful write.
A record names a write to the configuration and a denied result. What does it show?
Checking Coverage
The audit system only records the events its mechanisms and policies can observe. Before relying on an empty result, check that the policy covered the right path, operations, and time. Record which source you reviewed.
You find no write record in the selected log. Which check helps before concluding no writes occurred?
Lesson complete
You finished Audit Events
You can now select useful audit evidence for a protected resource.
Identify the operation and object you need to review.
Read the recorded result alongside the request.
Check coverage before using an empty search as evidence.
Keep your learning progress
Create a free account to save this lesson and continue learning on any device.
Create a free account