Rule: named account instead of a shared password
Vendor remote access is based on named accounts, not on one shared password. The rule looks trivial, but in practice it decides whether, after an incident, you can answer who logged in, and whether after an engineer leaves the vendor you can switch off their access without changing the passwords of everyone else.
Each account should have an owner on the vendor's side and an owner on the plant's side. The first answers for the person, the second for the purpose of access. Without these two names in the documentation the account is anonymous, even if technically it is named.
SSH keys and the IPsec tunnel
Named SSH keys mean one key per person, not one key per company. The private key stays with the person, and on the plant's side we record the public key, the date it was added and its expiry date. A key without an expiry date is access without an end.
The IPsec tunnel limits traffic to agreed addresses and ports, so the network administrator should check that the rules cover only the devices the vendor services. A broad rule for the whole industrial network cancels the benefits of named accounts.
What to check in the keys
Key format and length consistent with the plant's policy, limited validity, no shared keys. Compare the list of keys against the list of the vendor's people.
What to check in the tunnel
Source and destination addresses, port range, binding lifetime, how it is monitored and what happens after the connection drops.
Accounts to review: shared password versus named accounts
Register and evidence
Acceptance requires evidence that access is logged. Check whether logins record the account name, the time, the source address and the end time of the session. The register must be kept in line with the plant's policy, and its availability to the network administrator and security should be agreed in writing.
Ask one control question: can the register show who logged in last Tuesday at 14:00 and what they did? If not, the access is not ready for acceptance, even if it works.
Account lifecycle
A vendor account has a beginning and an end. Record the start date, the planned end date and the person who confirms the switch-off. A quarterly review of accounts helps catch accounts from finished projects.
Sample calculation: 6 engineers at 4 vendors make 24 accounts for the quarterly review. With a shared password there would be 4 entries, but none of them would answer who logged in. The extra work of the review is the price of accountability.
Acceptance: how to close the matter
Acceptance ends with a short protocol: the list of accounts and keys, the list of tunnel rules, the indicated register, the person responsible on both sides. The protocol is signed by the network administrator and the vendor's representative.
It is worth linking the external company's service access to its entry in the external companies module, so that remote service is visible in the same place as on-site service.
Checklist
Video
Frequently asked questions
Are named accounts excessive formality?
No. Only they let you answer who logged in and cut off one person without affecting the rest.
How long is an SSH key valid?
The plant sets the term in its policy. We recommend a short term and a quarterly review.
Is the IPsec tunnel enough?
It protects the transport but does not replace accounts and the register. It is one element of access.
What about access after the project ends?
Switch off the accounts and keys, confirm it in the protocol and remove the tunnel rules.
Accepting vendor remote access?
We will send the checklist in a form ready for signature and go through it with your network administrator.
Let's talk