A practical way to review external support access without losing sight of production constraints.
Define the task before the route
Choose a real maintenance activity and ask what the supplier must be able to do. Identify the equipment, expected duration and person responsible for approving the work. An account name alone does not explain the operational need. Include the supplier and equipment owner so that the proposed boundary can actually support the task.
Separate approval from availability
A technically available connection is not the same as authorization to use it. Record how a session is requested, who confirms the purpose and how the operator knows work is taking place. Decide how urgent support requests are handled without relying on an undocumented exception that becomes permanent.
Check what the identity can reach
Review the permitted systems and the privileges associated with the account. Consider whether a shared identity makes it difficult to determine who performed the work. Any proposed restriction needs to be tested against the legitimate support requirement, with an agreed fallback if it prevents essential maintenance.
Close the session with evidence
Record the work performed, any configuration changes and unresolved issues. Confirm that temporary permissions have ended and that the equipment owner has completed the agreed operational checks. Retain the information in a place the team can reach during a future fault.
Review when the relationship changes
A supplier change, new support platform or equipment upgrade can invalidate old assumptions. Assign an owner to review access when the support arrangement changes and at a cadence suited to the environment. The objective is a support route that remains useful, accountable and proportionate to the task.
Tie the connection to an authorised maintenance activity
A supplier needs to diagnose equipment during a planned maintenance window. A long-standing remote account provides broader access than the task requires, and the person who originally approved it has left. Review the requested work with the asset owner and the people responsible for production safety and availability. Establish an approved route, a named supplier contact and the access needed for that activity. Changes to operational technology should follow the organisation’s engineering and change-control process rather than a generic IT checklist.
Evidence to collect
- Name the equipment, maintenance purpose, supplier representative and internal decision owner.
- Record the approved connection path, authentication method and permitted time window.
- Check whether the connection can reach other systems or depends on shared credentials.
- Define how the session is ended, evidence retained and temporary access removed or reviewed.
What a useful result looks like
A useful review connects access to a task and an accountable person. If continuous vendor access is genuinely needed, document the reason and compensating oversight rather than describing it as temporary. Confirm how the supplier is contacted if their normal account or email channel is suspected to be compromised. Test any proposed access change under an approved plan that accounts for production dependencies.
Should every vendor connection be disabled immediately?
No blanket change is appropriate. First establish the operational purpose, consequences and authorised change process. Unplanned removal can disrupt maintenance or production. Prioritise excessive or unexplained access and agree a safe remediation sequence with the responsible owners.