What evidence do auditors commonly ask for on A.6.6 Confidentiality or non-disclosure agreements?

Statement of Applicability entry for control A.6.6, showing inclusion or justified exclusion, implementation status and the risks it treats; Approved NDA and confidentiality agreement templates covering definition of protected information, duration, termination actions, ownership, permitted use, audit rights, breach notification, return or destruction and non-compliance consequences; Signed agreements for personnel and for relevant external parties, dated before access was granted; A register of agreements in force with their parties and expiry or survival terms; Legal review confirming enforceability in the relevant jurisdictions.

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

NDAs are signed after access has already been given

ISO/IEC 27001:2022 · People controls

`A.6.6` Confidentiality or non-disclosure agreements

Confidentiality or non-disclosure agreements that match the organization's information protection needs are to be identified, written, reviewed regularly and signed by staff and by the outside parties concerned. Purpose (stated in ISO/IEC 27002:2022): maintains the confidentiality of information that personnel or external parties can access. 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.6.

Source: ISO/IEC 27001:2022, A.6.6. 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

Vendor register / contract repository

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

Legal review confirming enforceability in the relevant jurisdictions · Document repository

governing documentDocuments that govern the control

Statement of Applicability entry for control A.6.6, showing inclusion or justified exclusion, implementation status and the risks it treats · Policy repository / GRC workspace
Approved NDA and confidentiality agreement templates covering definition of protected information, duration, termination actions, ownership, permitted use, audit rights, breach notification, return or destruction and non-compliance consequences · HR system / LMS
Signed agreements for personnel and for relevant external parties, dated before access was granted · Vendor register / contract repository
A register of agreements in force with their parties and expiry or survival terms · Vendor register / contract repository

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

NDAs are signed after access has already been given
Templates are outdated and omit return or destruction of information at termination
No register exists, so the organization cannot tell who is bound by what
Agreements with suppliers or consultants are missing because procurement uses its own contract templates

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.5 Responsibilities after termination or change of employment · A.6.7 Remote working