External Contractors: Who Touches Your Machines?
· 7 min read · Updated
Lire en français
It is ten past eight on a Tuesday, and the maintenance contractor's technician arrives at reception, signs the register, receives a visitor badge, retrieves the prevention plan drawn up in the spring, then crosses the workshop to the test bench he has come to adjust, and by noon he has left. Three weeks later an incident occurs on that bench, and everyone wonders who worked on it last, on which part, and whether he was still allowed to, since his qualification was due to expire at the start of the month, and it is this question, that of external contractors who touch your machines without the machine knowing it, that we want to raise here.
This article is for operators who host external companies on their equipment, and for security managers who must account for it under NIS2 or a customer's framework.
A dense framework around external contractors that stops at the workshop door
It would be unfair to say that external contractors are not regulated, because they are, abundantly, by texts that each have their own logic and purpose, and we take the French case as an example, as we understand it without being lawyers, while most European countries have, as far as we know, comparable rules.
The French Labour Code organises co-activity, meaning employees of two companies working in the same place, and it provides that a joint preliminary inspection precedes the work, then that a written prevention plan is drawn up as soon as the operation represents at least 400 hours of work over twelve months, or whenever it appears on the list of hazardous work set by an order of 19 March 1993, whatever its duration in that case, and the plan identifies the interference risks between the two activities and the measures taken to prevent them.
Electrical qualification is required for any operation on or near an electrical installation, and it is issued by the worker's employer, within the limits of the tasks entrusted and after suitable training, and since 1 October 2025 a certificate of no medical contraindication issued by the occupational physician is also required for certain operations. The host company, for its part, has every interest in checking while preparing the work that the people coming to its site are qualified for what they will do there, but that check is made on documents and before the day comes.
The NIS2 directive requires the entities it covers to address supply chain security, including the relationships with their direct service providers (Article 21(2)(d)), as well as their access control policies and asset management (Article 21(2)(i)).
IEC 62443-2-4 describes, for its part, what an integration or maintenance provider for industrial systems must be able to guarantee to the asset owner who opens its installations to them.
Each of these texts produces documents, a plan, a qualification certificate, a contract clause, a policy, but none produces by itself the slightest effect on the machine, because the test bench in our example knows nothing about the prevention plan, does not know the qualification's end date and has no idea whether the technician who started it was the one expected, so control stops at the workshop door, when it does not stop at the building's.
What we see most often
When we walk around a site with its managers, four situations recur with a regularity that has struck us, and we describe them without seeing any particular fault.
The shared key. The machine's key switch, or the cabinet key, circulates between the in-house team and the contractor, and people sometimes know how many copies were made, but they rarely know where they all are.
The generic maintenance account. When the equipment has an interface, the contractor quite often uses a shared login created at commissioning and never renewed, which therefore says nothing about who typed it.
Cascading subcontracting. The contract holder sends a subcontractor, who sometimes sends their own, and the prevention plan in principle covers everyone, but information about who is actually on site thins out at every level.
The forgotten revocation. The contract ends, the technician changes employer or their qualification expires, and none of this translates to the field, because the field was never told anything.
None of these situations is, in our view, negligence in the strict sense, because they are the logical consequence of a system in which the right to intervene is written in documents, while the intervention itself happens on equipment that has no means of reading them.
Bringing the rule down to the equipment
The idea we defend is simple in principle, since it consists, rather than recording the right to intervene in a document consulted after the fact, in making it a rule checked at the moment the technician stands in front of the equipment, and a qualification then becomes a dated right, attached to a person and a scope, which stops having effect on its end date without anyone having to think about it.
Four moments seem to us to need covering, and we built our device around them.
- Before the work, the time slot, the equipment and the technician are entered in a rule, together with the validity date of their qualification, and this is the direct translation of the prevention plan into a language the equipment understands.
- On arrival, the technician's presence in front of the equipment is established, and their identity is verified by a cryptographic exchange with the badge or phone they carry, which is proof anchored in hardware, whereas a signature on a register remains a declaration.
- During the work, whatever is powered up, unplugged or replugged is logged, including when it falls outside the planned scope.
- Afterwards, the rule expires by itself, and the log can produce, for each technician and each piece of equipment, the list of granted and denied access.
For contractor work, we have a marked preference for a mode we call Consent, in which access requires validation by an internal manager from their phone and in which nothing happens without an answer, because it fits the reality of maintenance work, which is rarely regular enough to be fully described in advance, and it leaves the decision to someone who knows the situation that day. When an emergency demands it, a break-glass procedure can force access, but the override itself is timestamped, signed and reported, because we prefer a traced exception to an invisible bypass.
Remote or on site: two distinct topics
Contractor management is often confused with securing remote maintenance, because the same companies and technicians are usually involved, but the two subjects are different and the solutions for one do not cover the other, since a very well designed remote-access gateway says nothing about what happens when the same technician comes on site and plugs a laptop into the controller's port, and we developed this point in Remote Access and Physical Access: Two Different Problems.
What it does not replace: prevention plan, qualification and lockout
We think it important to say what such a device does not do, so that it is not mistaken for a shortcut.
- It replaces neither the joint preliminary inspection, nor the prevention plan, nor the interference risk analysis, which remain obligations of the host and the external company.
- It issues no qualification and checks no training, since it applies a validity date it was given and does not attest competence.
- It does not stand in for any safety measure protecting people, because a lockout, known in safety practice as lockout tagout or LOTO, meaning the verified and locked de-energising of equipment before anyone works on it, remains a lockout, and we explain this at length in Cutting the Power Is Not an Emergency Stop.
Finally, external contractors are not employees of the host company, but data about them is still personal data, so their presence and work should only be recorded for a clear purpose, kept for a limited time and brought to their attention, which is naturally done when the prevention plan is drawn up.
Where to start
If you regularly host external contractors, we would suggest starting with a modest exercise, which consists in picking the three pieces of equipment where unplanned work would have the heaviest consequences, and checking, for each one, whether you could say tomorrow who touched it last week. If the answer depends on a reception register and the team's memory, those three are a good starting point, and a deployment in plain observation, which cuts nothing, has been enough in the cases we have seen to produce the answer while changing working habits as little as possible.
Sources
- French Labour Code, Articles R4512-2 (joint preliminary inspection) and R4512-7 (written prevention plan). code.travail.gouv.fr
- Order of 19 March 1993 listing hazardous work requiring a written prevention plan (France).
- French Labour Code, Articles R4544-9 and R4544-10 (electrical qualification). travail-industrie.com
- INRS, Habilitation électrique : foire aux questions. inrs.fr
- Decree No 2025-355 of 18 April 2025 on individual health monitoring of workers and on the qualifications under Articles R4323-56 and R4544-9 of the Labour Code (France), in force on 1 October 2025 (Article 3). Légifrance
- Order of 26 September 2025 setting the models of certificates of no medical contraindication under Articles R4323-56 and R4544-9 of the Labour Code (France). preventionbtp.fr
- Directive (EU) 2022/2555 (NIS2), Article 21. EUR-Lex
- IEC 62443-2-4:2023, Security program requirements for IACS service providers. IEC Webstore
- NF C18-510, Operations on electrical installations and in an electrical environment, prevention of electrical risk (France).
