What evidence do auditors commonly ask for on A.6.2 Terms and conditions of employment?

Statement of Applicability entry for control A.6.2, showing inclusion or justified exclusion, implementation status and the risks it treats; Standard employment contract and contractor agreement templates with information security clauses reflecting the policies; Signed agreements for a sample of personnel, including confidentiality undertakings signed before access; Pre-employment communication of security roles and responsibilities to candidates; Records showing terms were reviewed after changes in law, regulation or policy.

What is the most common gap auditors find on A.6.2?

Contracts contain a generic confidentiality clause but nothing about classification, handling or consequences

ISO/IEC 27001:2022 · People controls

`A.6.2` Terms and conditions of employment

Employment contracts and agreements are to set out the information security responsibilities of both the individual and the organization. Purpose (stated in ISO/IEC 27002:2022): makes personnel understand what their roles demand of them for security. As an Annex A reference control, it is compared with the controls determined in risk treatment (6.1.3 c) and recorded in the Statement of Applicability as included or excluded, with the justification and implementation status (6.1.3 d); implementation guidance is ISO/IEC 27002:2022 6.2.

Source: ISO/IEC 27001:2022, A.6.2. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open ISO/IEC 27001:2022 in the compliance library.

Clauses 4 to 10 are the management-system requirements: none of them can be excluded when an organisation claims conformity. The 93 Annex A controls are a reference set: one may be excluded with a justification in the Statement of Applicability. Certification bodies assess conformity; the evidence lists here are what auditors commonly ask for, not a list the standard prescribes.

artefacts

held by a system

at each review

hard

to go live

Policy repository / GRC workspace

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

Records showing terms were reviewed after changes in law, regulation or policy · Policy repository / GRC workspace

governing documentDocuments that govern the control

Statement of Applicability entry for control A.6.2, showing inclusion or justified exclusion, implementation status and the risks it treats · Policy repository / GRC workspace
Standard employment contract and contractor agreement templates with information security clauses reflecting the policies · Vendor register / contract repository
Signed agreements for a sample of personnel, including confidentiality undertakings signed before access · Vendor register / contract repository
Pre-employment communication of security roles and responsibilities to candidates · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Contracts contain a generic confidentiality clause but nothing about classification, handling or consequences
Terms were never updated after policy or legal changes
Contractor agreements lack the security terms employees sign
Post-employment obligations are not defined, so they are unenforceable

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

A.6.1 Screening · A.6.3 Information security awareness, education and training