Cookies on this site. Help us understand what works and improve your experience. Essential cookies keep the site working. With your permission, our visit insights and Google Analytics measure usage, and Google Ads measures advertising. Optional cookies are not required to use the free kit. Change your choice anytime in Cookie settings. Privacy policyCookie policy
Employment contracts must state the employee’s and the organization’s security responsibilities.
Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.
Why this control matters
Employment terms are often the first place security expectations can be made explicit and enforceable. This control works best when HR, line managers, and legal or people operations keep the wording aligned with role risk, access levels, and local employment law, rather than relying on a separate policy no one can point to during onboarding or exit processing. A clear contract trail also supports later disputes about accountability.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
Contracts for some roles omit security duties, creating a gap between onboarding training and enforceable expectations during incidents or misuse.
Confidentiality language exists, but post-employment obligations are missing or vague, so departing staff may not understand retention, return, or non-disclosure duties.
References to the IS policy are outdated or absent, leaving no clear link between employment terms and current acceptable use or reporting obligations.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
Ask HR to maintain a clause library mapped to role sensitivity, covering confidentiality, acceptable use, incident reporting, remote working, and return-of-assets duties. Use Legal or People Ops to review jurisdiction-specific wording and separate standard clauses from high-risk exceptions for privileged, customer-facing, or developer roles. Keep version control so signed contracts can be matched to the approved clause set at the time of hire.
Link the contract pack to induction so every new starter signs the security clauses before access is provisioned. Accountable managers should confirm, for higher-risk roles, that references to the IS policy and related rules are current and understandable. Where post-termination restrictions apply, state what survives employment, such as confidentiality, intellectual property, and device return, without overreaching beyond lawful scope.
Record acceptance in the HR system and retain the signed offer letter, contract, or addendum together with the role description and access approval. During transfers or promotions, trigger a review to update duties if the role changes risk exposure, supplier contact, data handling, or administrative privileges. Treat missing acknowledgements as an onboarding exception requiring prompt follow-up.
Use an annual contract review sample, led by HR and ISMS owners, to check that templates still reflect current practices such as BYOD, hybrid work, or regulated data handling. Track exceptions with a rationale, approver, and review date so auditors can see how unusual clauses were controlled. When legal changes occur, update the template and reissue amendments where needed.
What an auditor will ask to see
Signed terms of employment with security and confidentiality clauses and the employee signature date.
Contract clause matrix showing standard and high-risk wording by role family, approved by HR and Legal.
Recorded addendum or re-sign process after role change, promotion, or policy update.
HR onboarding checklist showing contract acceptance before account creation and access approval.
Baseline documents in the kit
These free kit documents help you document or evidence A.6.2. Each one is tailored to your organization when you build your kit.
Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.
For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.
Get these documents tailored to your organization
109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.