TL;DR: Routine maintenance keeps OT security controls from turning into stale assumptions, according to Dragos. OT programs need ownership, verification, and exception handling to keep vulnerability intake, patching, configuration, exposure reduction, and access reviews aligned with reality.
Editorial analysis by NHI Mgmt Group, based on content published by Dragos: “The Work that Never Makes the Highlight Reel: MTSA’s Routine Maintenance Requirement”.
Key questions
Q: Why do unpatched vulnerabilities and configuration drift create operational risk so quickly?
A: Because OT systems depend on stable assumptions about reachability, service behaviour, and maintenance timing.
Q: What do security teams get wrong about access reviews?
A: Teams often treat access reviews as proof of control, when they are really only a point-in-time check.
Q: What breaks when routine maintenance is not kept current in OT environments?
A: When routine maintenance falls behind, hardened settings, vulnerability awareness, and access control no longer describe the real environment.
Practitioner guidance
- Implement a formal vulnerability intake workflow Create a monitored channel for vulnerability reports, assign triage ownership, and require a documented remediation or compensating-control decision for each relevant finding.
- Track maintenance responsibility by asset and system owner Maintain a register that shows who owns each system, who approves changes, and who is responsible for patching, exceptions, and support escalation.
- Treat configuration baselines as living control evidence Document approved services, ports, credentials, and remote access paths, then compare live systems against that baseline on a recurring schedule.
Bottom line: Routine maintenance is the mechanism that keeps OT security controls from becoming stale assumptions after the initial hardening work is done.
Glossary terms: Lifecycle Drift, Compensating Control, Configuration Baseline, Access Review
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Routine maintenance is an identity governance problem as much as it is an engineering task. The article is strongest where it shows that access reviews, shared credentials, and log retention sit inside the maintenance requirement, not beside it. That matters because OT programmes often separate device upkeep from identity lifecycle, even though the same drift pattern affects both. A maintenance framework that ignores privileged access is incomplete, especially where vendor accounts and shared credentials remain active long after their original purpose has passed.
A few things that frame the scale:
- Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: How should organisations balance patching with compensating controls in OT?
A: They should patch where it is safe, but document compensating controls where patching would disrupt operations or is not technically feasible. The key is to tie each exception to a risk decision, track it against the asset inventory, and revisit it as part of the maintenance cycle rather than leaving it open-ended.
👉 Read our full editorial: Routine maintenance keeps MTSA security from drifting out of compliance