Explore the expanded editions. Read every sample free before choosing a book.

Portfolio evidence / 3 MIN READ

A new export date does not make an old observation current

Use a fictional configuration timeline to separate observation time, extraction time and the date of the claim.

Server racks and network cabling inside a data center
Illustrative photograph by imgix on Unsplash.
On this page

A recently downloaded file can describe an old state. Before relying on it, identify when the relevant condition was observed, what changed afterward and the date of the assertion you are trying to support.

Inspect the fictional packet

An analyst is asked on June 15 whether a fictional supplier's current admin portal requires the configured second authentication factor. The packet contains an April 10 configuration screenshot, exported from an evidence repository on June 14. A change record says the portal's identity integration was replaced May 20. No post-change verification is included.

DateWhat happenedWhat it establishes
April 10Configuration was capturedEvidence of the displayed setting then, within the screenshot's scope
May 20Identity integration changedA relevant dependency changed after the observation
June 14Old screenshot was exportedRecent retrieval, not a new observation
June 15Current-state answer requestedThe assertion needs support at a later point

The screenshot does not establish the June 15 claim. It also does not prove that the second factor was disabled. Both confident conclusions exceed this packet.

Write a precise evidence request

Ask for a current, appropriately scoped verification of the relevant configuration and behavior after the identity change, with the system, account scope, date and method identified. Follow the authorized review process; do not collect credentials, recovery codes or unnecessary personal records.

A bounded note could say: “The April observation predates a material identity change. The June export date does not resolve that gap. Current enforcement is unconfirmed from this packet; request scoped post-change verification and retain the earlier evidence as historical support.”

Now suppose a June 12 record demonstrates the setting and a permitted verification for one specified admin account. That is newer relevant evidence, but the scope still matters. Do not extend one account's result to all roles, alternate login paths or every date since May without supporting work.

Avoid an invented expiry rule

There is no supplied rule here that evidence expires after 30, 60 or 90 days. An old design document might still explain an unchanged design; a new screenshot might miss the very path under review. Evaluate relevance to the assertion and known changes rather than age alone.

NIST's continuous-monitoring guidance provides background on ongoing visibility into assets and controls. The dates and conclusions above are original fictional practice, not a NIST-prescribed assessment procedure.

For resource selection, use evidence-freshness preparation. Keep observation date, extraction date, claim date, intervening change and unresolved scope together in your finished note.

PUT IT INTO PRACTICE

Risk & Evidence Portfolio Kit

Connect the individual document to a complete fictional case, with registers and a versioned decision memo.

Choose another free evidence, application or portfolio task