A security reviewer asks who authorized a network change and where the current configuration came from. A file called 'final' will not answer that. Connect the request, decision, implemented version and review result so the reviewer can follow the evidence.
Agree what is being reviewed
Operational technology, or OT, works with physical processes. Your security and compliance team should establish the review boundary and applicable obligations. NIST CSF can help organize cybersecurity risk; a generic evidence list cannot establish compliance for every facility.
Give each question a useful source
| Review question | Useful evidence |
|---|---|
| What is in scope? | An asset list with location, owner and review date. |
| Why was a change made? | The request, assessment and authorized decision. |
| Was the action implemented? | Version, implementation time and review result. |
| What remains unresolved? | An exception with responsibility and review date. |
Prepare the permitted review copy
- 01
Get the review questions and evidence scope from the responsible reviewer.
- 02
Identify a trusted source, evidence owner and date for each answer.
- 03
Exclude passwords, tokens and irrelevant sensitive details from the shared copy.
- 04
Test the recipient's access to the intended version and disclose open items clearly.
Evidence management is not certification
AutoNexit helps retain records and enforce access; it is not a security scanner or certifier. Legal applicability, including NIS2 where relevant, needs separate qualified review. Distinguish missing documentation from an unimplemented control: they require different corrective actions.
Primary sources
Technical claims and product boundaries were checked against these primary sources. Fact-checked
Frequently asked questions
Should device passwords be attached?
Do not publish passwords or keys in the review copy. Manage emergency access through the organization's approved secure process.
Is a screenshot sufficient evidence?
It may contribute, but assess its origin, date, scope and connection to the action being reviewed.
Does no recorded incident prove the control works?
No. Record the relevant review or test outcome and the limits of observation.
Should an accepted exception be left out?
Keep its reason, risk, decision owner and next review visible to the authorized reviewer.