Evidence practice / 3 MIN READ
Audit-log retention evidence: a setting is not a retrieval result
Work through a fictional retention claim, an incomplete search and a later retrieval record without overstating what the evidence proves.
On this page
A retention setting describes intended behavior. A retrieval result shows what a particular search returned. Neither alone establishes that every required event was generated, preserved and readable throughout an entire period.
This original fictional case is for interview and portfolio practice. Its 90-day criterion is supplied by the exercise, not a universal legal or security requirement. Do not use real log contents, account identifiers or confidential system records in a public portfolio.
Read the three records
Fictional Vale's internal criterion says its application authentication events must remain retrievable for 90 days. At the review time, you receive:
| Record | What it says |
|---|---|
| Current configuration screenshot | Retention setting is 90 days |
| Search export | Events from the last 30 days |
| Owner's message | Older events are in an archive |
The export's query filter is not supplied. There is no archive retrieval result. Your task is to write a preliminary evidence note, not to decide the organization's entire security posture.
Avoid two unsupported conclusions
“The control passes because the setting says 90 days” confuses configuration with historical operation. The screenshot does not show when that setting took effect or whether every required source was collecting.
“The control fails because the export has only 30 days” also goes beyond the packet. A query limited to 30 days could return that result even when older records exist. The absence of older rows in this bounded export is not proof that they were deleted.
A useful preliminary note
“The current setting is consistent with the exercise's 90-day criterion. The supplied export demonstrates returned events within a 30-day window, but its filter and source coverage are not documented. The archive claim has not been demonstrated. Request the query scope, applicable source inventory, setting history and an authorized retrieval of older in-scope records before concluding on the 90-day claim.”
The request is specific about the missing connection. It does not require unrestricted access or copies of an entire sensitive log store. In real work, use approved access, minimization and handling procedures.
Add one retrieval result
The owner now supplies an approved retrieval record showing readable events from 75 days before the review, with the application source, query bounds and retrieval time documented. Update the note: this supports retrieval of those events at that time. It strengthens the archive claim but does not establish uninterrupted coverage across all 90 days or every required event source.
The next work depends on the actual assessment scope. You might reconcile expected sources, inspect collection gaps or obtain evidence for the boundary period. Do not turn one successful old-event retrieval into a universal completeness claim.
Connect the exercise to primary guidance
Read the NIST SP 800-53 control catalog, including AU-11, for retention context. The CIS Control 8 assessment specification provides another primary framework for examining audit-log management. Apply the relevant version and organizational scope; the fictional numbers here are not a claim about what every framework requires.
Build a defensible practice artifact
Keep the criterion, record list, preliminary conclusion and revised conclusion together. Label the records fictional. Under each conclusion, state its exact scope and remaining uncertainty. The most useful improvement is the changed reasoning after new evidence, not a polished “pass” label.
Use the log-retention preparation comparison to choose between this free exercise and broader connected portfolio practice. For presenting the resulting decision, see the GRC memo example.
PUT IT INTO PRACTICE
GRC Career Transition Guide
Turn this guidance into a focused role brief, experience inventory and application plan.