Checklist | 5 min read
FAT and SAT cybersecurity evidence checklist
A checklist-style guide for including cybersecurity verification in factory acceptance, site acceptance and control system handover.
Placeholder
Make cybersecurity testable
Cybersecurity requirements are often difficult to close because they are written too generally or introduced late in the project. FAT and SAT evidence should show what was checked, what was not checked and which assumptions remain open.
The checklist should be linked to project requirements, supplier responsibilities and operational handover needs.
Typical evidence areas
The exact checklist depends on the system, but most control system projects need evidence around architecture, account management, hardening, backup, remote access and communication paths.
Useful evidence
- approved network architecture and interface list
- user and administrator account evidence
- remote access design and approval route
- backup and recovery test evidence
- open action and residual risk register
Related services and problems
Continue through related service, problem and resource pages for the same OT cybersecurity topic.
Discuss practical OT cybersecurity evidence
Use a technical discovery call to frame the system boundary, known constraints and the evidence needed before sharing sensitive site details.