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
A.5.20 Addressing information security within supplier agreements
Not mandatory by default – decided in your SoA
What it means in plain language
Write the security requirements into supplier contracts so they are enforceable.
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
Supplier due diligence loses value when contractual terms do not require the supplier to maintain the agreed protections. Teams should turn security expectations into enforceable clauses within the Supplier Security Policy and contract pack, so legal, procurement, and business owners can verify that confidentiality, breach handling, deletion, and assurance rights are stated before services start. Good drafting also anticipates exit, subcontracting, and audit access issues.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
The organization relies on verbal assurances or sales-side emails, but the signed agreement does not mention incident notification timing, sub-processing approval, or data return obligations.
Security clauses vary by contract because teams use unvetted templates, making it difficult to show a consistent minimum set of protections for similar supplier types.
There is no clear right to receive evidence or challenge weak controls, so the organization cannot compel follow-up when a supplier’s assurance report or questionnaire reveals gaps.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
Create a standard security schedule or annex that is attached to every relevant supplier contract. Include confidentiality, data handling, incident reporting, access control, deletion or return at termination, subcontractor controls, and cooperation duties. Adjust the clause set by data sensitivity and service criticality rather than using one rigid template for all suppliers.
Require legal review before signature to confirm the clauses are consistent with the commercial terms, privacy obligations, and any cross-border transfer restrictions. The business owner should confirm operational requirements, while information security checks that response times, evidence rights, and exit terms are practical for the service.
Specify the evidence the supplier must provide during the relationship, such as assurance reports, penetration-test summaries, remediation status, or policy confirmation. Where the service is higher risk, include a right to ask questions, escalate unmet obligations, or approve material changes to hosting or subcontracting arrangements.
Define termination and transition clauses that cover secure return, deletion, or archival of customer data, plus confirmation of residual data in backups where applicable. Ensure the contract states who signs off closure, what proof is required, and what happens if deletion cannot be immediate because of technical retention cycles.
What an auditor will ask to see
Signed contracts containing the security annex, breach notification clause, deletion clause, and subcontractor restrictions.
Legal redline or clause checklist showing review of confidentiality, audit rights, and data return provisions.
Exit correspondence or supplier confirmation of deletion, return, or archival at contract end.
Template schedule used by procurement to ensure standard security terms are attached to new agreements.
Baseline documents in the kit
These free kit documents help you document or evidence A.5.20. 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.