Where this offering fits
Configuration and change management establishes a reviewable baseline for OT assets and makes deviations visible. Its purpose is not to treat every difference as malicious. Legitimate maintenance, emergency changes and unsupported settings all need context before a finding becomes an action.
Architecture and rollout decisions
Choose assets and approved baseline attributes with operations. Validate how the selected configuration collects and compares them. Test an authorised change and an unexplained difference, including the link to the maintenance record. Decide who updates the baseline and who reviews exceptions after a project or vendor service visit.
An evaluation scenario for this offering
Establish a test baseline for a small supported asset group and record an approved maintenance change in the organisation’s normal change system. Make that change through the authorised procedure, then introduce a separate permitted test deviation without an associated approval record. Ask the reviewer to reconcile the two cases from the evidence provided. The exercise should show how a legitimate change is explained and how the unexplained difference stays open. After review, update the baseline only for the accepted state. Preserve the before-and-after values and reviewer decision so later staff can understand why the baseline changed.
Evidence to request for this scope
- Document baseline ownership and approval.
- Confirm supported attributes for representative device models.
- Retain before-and-after evidence with change context.