Field notes · Security and compliance · 6 min
What SOC 2 and ISO 27001 require of subcontracted staff
Neither framework bans contract staff. Both expect you to treat a subcontracted engineer with system access exactly as you would an employee, and to prove it.
Sahil Dubey, Group Managing Director · 20 November 2026

Notes
If a contract or subcontracted engineer can reach your production systems or customer data, SOC 2 and ISO 27001 treat that person as in scope. The frameworks do not care whose payroll they are on. An auditor will ask for the same evidence as for an employee, plus evidence that you manage the company supplying them.
What ISO/IEC 27001:2022 expects
The people controls in Annex A apply to anyone working under the organisation's control, which includes contractors. The supplier controls apply to the firm that provides them.
- A.6.1 Screening: background verification before the person starts, proportionate to the access they will have
- A.6.2 Terms and conditions: security responsibilities stated in the contract
- A.6.3 Awareness and training: the contractor completes your security training, not only the supplier's
- A.6.6 Confidentiality agreements: signed and current
- A.5.19 to A.5.22 Supplier relationships: security requirements written into the supplier agreement and the supplier monitored against them
- A.5.15 to A.5.18 Access: provisioned on need, reviewed, and removed promptly at the end of the engagement
What SOC 2 expects
SOC 2 is criteria-based, so the wording is yours, but the same ground is covered. The common criteria on commitment to competence and accountability reach contractors as well as employees. The logical access criteria cover how their accounts are granted, reviewed and removed. The vendor and business-partner risk criterion covers the staffing firm or subcontractor itself.
In a Type II audit, the test is whether those controls operated across the whole period. One contractor who started before their background check was complete, or whose account stayed live after they left, becomes an exception in the report.
The evidence an auditor asks for
- The population of contractors with system access during the period
- Background check completion dated before the start date
- Signed confidentiality and acceptable-use acknowledgements
- Security training completion records
- Access request and approval for each account
- Access removal dated at or near the end date
- The supplier agreement, with its security clauses, and your review of the supplier
Where a subcontract chain makes it harder
With a staffing firm in the middle, and sometimes a second supplier behind it, the engineer's employer is two contracts away from you. Requirements get lost at each hop unless they are flowed down in writing. Ask the staffing firm to show that screening, confidentiality and incident-notification terms are in its agreement with the supplier, and that the supplier's agreement with the engineer carries them too.
It also helps if the supplying company holds its own ISO 27001 certificate or SOC 2 report. That does not replace your controls, but it gives your supplier review something concrete to rely on.
We subcontract engineers to staffing firms and hold ISO/IEC 27001 certification and a SOC 2 Type II report, which we share under NDA. That is our interest in this subject.
A short checklist before a contractor gets access
- Screening complete and recorded
- Confidentiality agreement and security terms signed
- Your security training assigned with a due date
- Named account under your identity provider, with MFA
- Least-privilege access with a stated end date
- Offboarding owner named for the last day
None of this is heavier than what you already do for employees. The failure is nearly always that contractors were onboarded through procurement instead of HR and skipped the steps.
Who wrote this
Sahil Dubey
Group Managing Director
Runs engineering and compliance across the group. Twenty years in infrastructure, most of it on the operations side of systems that were already in production when he inherited them.
- CISA
- AWS Solutions Architect – Professional
- Microsoft Certified: Azure Administrator Associate
More notes
Staffing partners
C2C subcontracting with an offshore vendor: how the paper works
Build vs buy
India or the Philippines: which fits which kind of work
Infrastructure
Managing an Offshore Team: The Operating Cadence