TL;DR: New FERC direction for large computational loads reframes data centre remote access as a reliability and accountability issue, not just a connectivity problem, because vendors, integrators and service teams often retain standing pathways into operational systems, according to Forescout. The governance gap is session visibility, third-party approval and shutoff, not uptime tooling.
Editorial analysis by NHI Mgmt Group, based on content published by Forescout: “Secure Remote Access: The Data Center Risk Not on the Uptime Slide”.
Key questions
Q: What breaks when third-party remote access is not tightly scoped?
A: When vendor access is not tied to a specific purpose and expiry, organisations lose control over who can reach sensitive systems, what they can touch, and how long the access remains valid.
Q: Why do standing vendor accounts increase risk in operational environments?
A: Standing vendor accounts extend trust beyond the maintenance task that justified them.
Q: How should teams govern remote maintenance access for industrial devices?
A: Treat OEM maintenance as a controlled identity relationship, not a convenience channel.
Practitioner guidance
- Inventory every third-party remote pathway List vendors, integrators, MSPs and facilities teams that can still reach operational systems, then assign an owner, business justification and expiry date to each pathway.
- Replace shared vendor logins with named access Require named identities for each remote session and remove shared accounts such as generic vendor administrator logins that obscure accountability.
- Add session recording and live termination Monitor remote sessions in real time, retain recordings for investigation, and ensure operators can end a session the moment behaviour looks unsafe.
Bottom line: Remote access in critical infrastructure is now a reliability and accountability issue, not just a connectivity issue.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →