The problem: two worlds of access, one vendor
In many chemical plants physical access and remote access are managed by different departments. Security knows the companies entering through the gate, and IT knows the vendors with access to the servers. The same vendor can therefore sit in two registers, with different people and different expiry dates, and only an audit notices that the list of authorized persons is inconsistent.
The scenario describes a concept for a chemical-type plant, not a specific deployment. The IT administrator is responsible for a vendor system that requires periodic service interventions. The task is to make the remote vendor visible in the same place as companies entering the site, with access based on the identity of the person.
Step 1: the vendor in the external companies module
The external companies module keeps data on companies, their employees and guests in one place. The remote vendor is entered here as a company with a list of specific people who may carry out the service. Each person has their own record, so when the vendor's team changes the administrator adds or removes individual people, instead of replacing shared access data.
This approach has a practical advantage: the maintenance manager and the IT administrator look at the same list. The question "who from the service company has permissions today" has one answer, not two.
- The service company as one entry with named people.
- People physically on site and people working only remotely in one register.
- A change in the vendor's team recorded as a data change, not as a password exchange.
Operations when the vendor's team changes during the year
Step 2: named accounts instead of a shared password
Remote vendor access is based on named accounts, not on one shared password. Remote service access can run through an IPsec tunnel and named SSH keys. The tunnel provides an encrypted connection between the vendor's network and the plant network, and an SSH key assigned to a person makes it possible to tell who performed a given action.
A shared password has two weaknesses that are obvious in an audit. First, it is not known which of several people logged in. Second, removing one person's access requires changing the password for everyone. A named account solves both problems: the log entry points to the person, and disabling one key does not affect the rest of the team.
What the IT administrator can agree with the vendor
Before going live it is worth writing a short technical agreement: who creates the keys, how a request for a new person is submitted, when access expires after the contract ends, and where session logs are kept. Network configuration details depend on the plant and should not be published outside the implementation team.
Step 3: the same rule as at the gate
A well-designed external companies register applies one rule to both kinds of access: the company is known, the people are named, and the permissions have an expiry date. A service technician entering physically passes the gate with a QR token, and the same technician connecting remotely uses their own key. In both cases it is the same person in the same register.
This does not mean that InnerWeb manages the vendor's network infrastructure or replaces the plant's access control system. InnerWeb is a software producer and complements existing systems. The role of the module is to keep order in the data about companies and people, not to replace a firewall.
Result: one audit list in one place
For the IT department the result is an answer to the question asked in every security audit of the supply chain: which vendors have access and on what basis. For security it is confirmation that the vendor has no additional, unknown people. For the maintenance manager it is a simpler procedure for requesting service.
For a chemical plant subject to infrastructure security requirements, such a list is also evidence. It supports meeting the requirement to supervise suppliers, but it does not replace the plant's own policy.
Sample calculation: order in accounts
Assume a vendor with six remote people, of whom two change over the year. With one shared password every change of team requires rotating the password and passing the new one to the remaining five people, which comes to about 10 contacts a year. With named accounts a change means closing one key and adding one, without contacting the others. This is a sample calculation based on the assumptions above, not a measurement result.
Handling changes in the remote vendor's team
| Parameter | Value |
|---|---|
| Remote people on the vendor side | 6 people |
| Team changes per year | 2 changes |
Result: 10 contacts with a shared password versus 2 key operations with named accounts
Note: Sample calculation based on the assumptions above; it is not a measurement result.
Video
Frequently asked questions
Does a remote vendor need an account in the InnerWeb system?
Access to the infrastructure is based on named accounts and keys, and in the external companies module the vendor is listed as a company with a list of people. The scope is set during implementation.
Is an IPsec tunnel mandatory?
It is one of the possible ways of remote service access. The choice depends on the plant's security policy.
Does InnerWeb replace a firewall?
No. InnerWeb is a software producer and complements the plant's existing systems.
What about a vendor who also comes on site physically?
The same company and the same people appear in the register, and at the gate the person uses a QR token on their badge.
Put your vendors in one register
Let's talk about how to model remote vendors and companies entering the site in one data model. Book a conversation with the InnerWeb team.
Let's talk