Illustrative example
HypotheticalA firewall rule is opened for a historian upgrade. The change record sets an expiry date, and verification after the upgrade confirms the rule was removed.
“Changes to logic and configurations happen without a security check or record.”
Uncontrolled changes are a common cause of both security gaps and operational incidents. A lightweight security review keeps changes fast while keeping them visible.
A temporary rule or connection can become permanent.
Inventories and drawings drift when changes aren't recorded.
Responders need to know what changed recently.
Change control is required by most OT frameworks.
A sequence that can be adapted to your environment and scope.
Capture the change, affected assets and reason.
Answer security impact questions for the change type.
Route to the right owner, including emergency changes.
Confirm the result and remove temporary measures.
Update inventory, drawings and risk records.
A firewall rule is opened for a historian upgrade. The change record sets an expiry date, and verification after the upgrade confirms the rule was removed.
It shouldn't. A short set of security questions per change type, with a defined emergency path, adds minutes rather than days.
From the blog
National NIS2 laws are now being enforced. Here is what energy, water, transport and manufacturing operators should be able to show for their OT environments.
Read the articleManufacturers must now report actively exploited vulnerabilities and severe incidents. Asset owners should expect more advisories, and suppliers need a working process.
Read the articleSegmentation diagrams often look perfect and behave very differently. A practical method for zones and conduits that match how your site really works.
Read the articleDescribe where you are today and we'll suggest a practical way forward.