Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Secure device commissioning builds security into the process of bringing new equipment into service, so that hardening, identity, and documentation are complete before the device carries production.

What Is Secure Device Commissioning?
Commissioning is the window in which an industrial device can be changed freely. Before the plant depends on it, a controller can be reconfigured, a firmware version chosen, a password set, and a certificate installed without a change request, an outage, or a production loss. Once the device carries process, every one of those actions becomes expensive. Secure device commissioning is the practice of using that window properly.
The cost asymmetry is severe. Setting a unique password during commissioning takes a minute. Changing the same password three years later means scheduling an outage, coordinating with the vendor, verifying the control application still connects, and updating documentation nobody has read since handover. Most of the default credentials found during industrial assessments are not there because anyone decided to leave them; they are there because the moment to change them passed.
Commissioning is usually performed by an integrator or the equipment vendor, often under time pressure at the end of a capital project when the budget is spent and the plant wants to start. That is precisely why the security requirements must be contractual and the acceptance criteria written before mobilisation. A sensible arrangement names security sign-off as a condition of handover, gives the asset owner the right to witness the hardening steps, and requires the integrator to deliver credentials through a controlled channel rather than in a spreadsheet attached to an email.
Remote and zero-touch provisioning deserves specific attention. Devices that fetch configuration from a cloud service on first power-up remove manual effort and introduce a new trust relationship; verify how the device authenticates the server, what happens if that fails, and whether an attacker on the same network can answer first.
The NCSC’s Cyber Assessment Framework expects secure configuration and asset management as ongoing capabilities rather than one-off projects, and an assessor will look for evidence that new equipment enters service in a known state. The same expectation appears in IEC 62443-2-4, which is the most practical document to hand an integrator. At Privia Security, our Infrastructure and Architecture Review Services can sit alongside your FAT and SAT programme so that security acceptance happens while the fix is still inexpensive.
The asset owner, in a privileged access management vault, with the integrator’s installation accounts disabled at handover. If the vendor needs ongoing access for support, issue a named, time-limited account through your brokered remote access path rather than sharing the engineering credential. Document the arrangement so it survives staff changes on both sides.
It is the ideal time. The system is assembled, reachable, and not yet controlling anything, so active testing that would be unacceptable on a live plant is straightforward. Agree the scope with the integrator in advance, allow time in the FAT schedule, and treat findings as defects to be closed before shipment.
Record that explicitly and compensate around it. Place the device in a zone whose boundary provides the control the device cannot, restrict which systems may address it, and monitor the conduit. The commissioning record should state the limitation and name the accepted risk, so it reappears at the next review rather than being forgotten.
They are the same discipline at opposite ends. Removing a device should revoke its certificates and accounts, remove its firewall rules, close its inventory record, and ensure stored configurations and any process data on it are securely erased. Orphaned rules and ghost assets from poor decommissioning are a common finding during architecture reviews.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.