Manage the compliance lifecycle
Define the right scope and control baseline
Establish boundaries across production cells, control networks, industrial DMZs, remote SCADA sites, connected devices, and supporting services. Record the applicable standard edition, regulatory obligation, organizational role, and assessment period.
Separate asset-owner responsibilities from those of integrators, service providers, and product manufacturers. Document exclusions and their rationale so a site assessment does not imply coverage of the entire enterprise.
01
Map requirements to industrial controls
Connect requirements to control objectives, implementation records, owners, and verification methods. Address zones and conduits, privileged access, configuration management, vulnerability handling, monitoring, and response readiness.
Reuse relevant evidence across overlapping frameworks while preserving each requirement's scope and assessment criteria. A cross-reference helps organize evidence; it does not make different requirements interchangeable.
02
Build a traceable evidence record
Use available platform telemetry, approved integrations, and assessment records to assemble asset inventories, communication observations, security events, configuration reviews, and remediation results.
Associate evidence with its source, collection date, system scope, reporting period, and reviewer. Include policies, training records, supplier documentation, physical security checks, and recovery exercises where technical monitoring cannot establish the result.
03
Identify gaps and manage corrective action
Distinguish assessed controls from partial implementations, failed checks, missing evidence, and justified exclusions. Assign ownership and target dates to findings, with operational impact and maintenance requirements recorded.
For legacy equipment, document proposed compensating controls, validation evidence, and residual risk. Review their acceptability against the applicable requirement and approval process; an internal exception does not automatically satisfy a regulatory obligation.
04
Keep evidence current as operations change
Use observable changes in assets, communications, vulnerabilities, and monitoring coverage to identify controls that need reassessment. Review supporting documentation when equipment, suppliers, access arrangements, or procedures change.
Set review intervals appropriate to each evidence source. Keep stale records and monitoring gaps visible so missing data cannot be mistaken for a successful control check.
05
Produce reports for decisions and scrutiny
Build reports around the selected facility, framework, assessment period, and audience. Present control findings alongside evidence references, unresolved gaps, corrective actions, and review status.
Give leadership a view of operational exposure and decisions required. Give auditors the detail needed to trace a conclusion back to its supporting records.
06