What Evidence Should You Prepare for an OT Cybersecurity Audit?
Most industrial operators fail documentary review before they fail technical review. The segmentation is sound, the monitoring works, the engineers know the plant intimately. But nothing is written down in a form an assessor can accept, approvals were verbal, and the asset inventory lives in one person's spreadsheet. Security was done. It cannot be shown.
That inversion surprises teams who expect an audit to test their defenses. An audit tests your ability to demonstrate your defenses, which is a related but different capability. This article is the checklist of artifacts to have ready, whichever framework you are being assessed against.
The six artifacts every assessment asks for
|
Artifact |
What makes it acceptable |
|
Asset inventory |
Current, maintainable, and covering OT rather than only IT. Must include firmware or software versions, network location and criticality. A PDF appendix from a consultant three years ago is not an inventory. |
|
Risk assessment |
Dated, with a stated method, covering the OT environment specifically. The method matters as much as the findings, because an assessor will test whether the rating is repeatable. |
|
Access records |
Who has access to what, including vendors and contractors, with evidence of granting, review and revocation. Revocation is the part usually missing. |
|
Backup evidence |
Not that backups are configured. That a restore has been tested, when, by whom, and whether it worked. An untested backup is an assumption. |
|
Change records |
Changes to control systems with approvals attached, including who performed the security review. |
|
Training records |
Who was trained, on what, when. Including contractors, which is where most registers stop. |
|
The two that fail most often Backup restore testing and access revocation. Almost every operator can show that backups run and that access is granted, because both are configured in a system that logs them automatically. Far fewer can show that a restore was tested and succeeded, or that access was removed when a project ended or a contractor left. Both gaps share a cause: the automated part of the process creates its own evidence, and the human part does not. |
Supporting evidence worth having ready
- Network and zone diagrams. Current, and ideally expressed as zones and conduits if you work to IEC 62443. An out-of-date diagram is worse than none, because it demonstrates the documentation is not maintained.
- Risk acceptance records. For anything you have decided not to remediate, including legacy equipment you cannot patch. See our guide to managing legacy PLCs and unsupported Windows.
- Incident response plan and exercise records. The plan is the easy part. Evidence that it was tested is what an assessor looks for, which our OT incident response tabletop guide covers.
- Vulnerability management records. What was found, what was decided and why, not only what was scanned. See OT vulnerability management.
- Monitoring configuration and alert handling. That alerts are generated is half the evidence. That someone acted on them is the other half.
- Policies with approval dates and owners. An unapproved or unowned policy is a draft.
What differs by framework
The six core artifacts are common ground across frameworks. Where assessments diverge is depth and formality rather than subject. A NERC CIP audit is prescriptive and evidence-heavy, with specific requirements and a compliance monitoring process behind it, and our NERC CIP audit preparation checklist covers that case in detail. An IEC 62443 assessment is structured around zones, conduits and security levels, so your zone model becomes a central artifact. A customer or insurer assessment is usually lighter but less predictable, and tends to probe supply chain and access harder than a regulator does.
Prepare the common six to a standard that satisfies the most demanding assessment you face, and the lighter ones become straightforward. Preparing separately for each is how documentation sets diverge and contradict each other, which is itself a finding. Our guide to choosing and combining ICS security frameworks covers the selection question.
Three habits that make audits easier
Keep the artifacts where the work happens rather than in an audit folder assembled before each assessment. Evidence compiled retrospectively looks like evidence compiled retrospectively, and assessors recognize it.
Record decisions, not just actions. The decision not to remediate something, with the reasoning and the person who made it, is often stronger evidence of a functioning program than the remediation itself, because it demonstrates the organization is managing risk deliberately.
And date everything, with an owner. An undated document cannot be shown to be current, and an unowned one cannot be shown to be maintained. Those two fields turn a document into an artifact.
Why Choose Arista Cyber
We run documentary readiness reviews before technical assessments, because that is the order an assessor will use and the order in which most operators discover their gaps. Our consultants work on live industrial assets and hold functional safety credentials alongside OT security certification. See our OT risk assessments and our case studies.
Next Steps
Take the six artifacts and ask one question of each: could I produce this tomorrow, dated, owned and current. The ones where the answer is no are your scope, and in our experience backup restore testing and access revocation are the two that come back no most often.
Common Questions
What evidence does an OT cybersecurity audit require?
Six artifacts come up in almost every assessment: a current asset inventory, a dated risk assessment with a stated method, access records including vendors, evidence of tested backup restores, change records with approvals, and training records covering contractors.
What do operators most commonly fail on?
Backup restore testing and access revocation. Both have an automated half that creates its own evidence and a human half that does not, so operators can usually show backups run and access was granted, but not that a restore worked or that access was removed.
Is a consultant report enough as an asset inventory?
No. An inventory needs to be current and maintainable by you. A static report from a previous engagement demonstrates that an inventory was once produced, not that one is kept.
Does the evidence differ between IEC 62443 and NERC CIP?
The subjects are largely the same. The depth and formality differ. NERC CIP is prescriptive and evidence-heavy with a compliance monitoring process behind it. An IEC 62443 assessment places more weight on your zone and conduit model.
Should we keep a dedicated audit folder?
Keep the artifacts where the work happens and generate the pack from them. Evidence assembled retrospectively for each assessment is recognizable as such, and it tends to diverge from what is actually in use.
|
Could you produce all six artifacts tomorrow? Arista Cyber runs documentary readiness reviews for industrial operators: artifact gap assessment against the framework you face, remediation of the evidence gaps, and a mock assessment before the real one. |
Facing tougher cyber security challenges?
Talk to Arista Cyber about your OT security posture.
Request a consultation