Addressing Information Security Within Supplier Agreements
Plain English Translation
ISO 27001 Annex A.5.20 requires that specific information security obligations are explicitly defined and agreed upon in contracts with suppliers. It is not enough to simply select a secure vendor; the organization must legally bind the supplier to specific security standards, data protection requirements, and service levels appropriate to the risk and type of relationship. This ensures that security expectations are enforceable and clear to both parties.
Technical Implementation
Use the tabs below to select your organization size.
Required Actions (startup)
- Review and archive Terms of Service (ToS) for all critical SaaS tools (e.g., AWS, GitHub)
- Ensure all contractors sign a standard NDA and Contractor Agreement
Required Actions (scaleup)
- Implement a standard Security Addendum for all new vendor contracts
- Require signed Data Processing Agreements (DPAs) from all vendors processing PII
Required Actions (enterprise)
- Negotiate custom security terms including 'Right to Audit' clauses with strategic suppliers
- Automate the validation of signed agreements within a Vendor Risk Management (VRM) platform
It is an organizational control that mandates establishing and agreeing on relevant information security requirements with each supplier based on the type of supplier relationship.
Agreements should include clauses for data protection, confidentiality, access controls, acceptable use, incident reporting timelines, right to audit, and requirements for return or destruction of data upon termination. WatchDog Security's Vendor Risk Management can help track which clause categories are required per vendor risk tier and keep the signed agreement evidence attached to the vendor record.
Requirements are determined by risk assessment; a supplier handling sensitive PII requires strict DPAs and incident reporting clauses, whereas a facility maintenance vendor may only require physical security and confidentiality agreements.
Auditors expect to see a Third-Party Management Policy and signed examples of agreements (such as MSAs, cloud service agreements, or signed Terms of Service) for in-scope suppliers like cloud providers, database providers, and contractors. WatchDog Security's Vendor Risk Management can provide a centralized view of in-scope suppliers with linked signed agreements and review status to speed up audit sampling.
Yes, for suppliers processing personal data (PII), a DPA is typically required to define specific data protection obligations, ensuring alignment with privacy regulations and A.5.20 requirements. WatchDog Security's Vendor Risk Management can flag vendors that process PII and require a DPA before moving the vendor to an approved status.
Common clauses include commitments to encryption, availability SLAs, breach notification timeframes, adherence to audit standards (e.g., SOC 2), and data residency requirements.
Agreements should include 'flow-down' clauses requiring the supplier to ensure their own subcontractors (your fourth parties) adhere to the same or equivalent security obligations.
Agreements should specify strict timelines for notification (e.g., within 24-72 hours of detection) and the method of communication to ensure the organization can meet its own regulatory reporting obligations.
SLAs (Service Level Agreements) define measurable performance metrics for availability and support, while security addendums allow organizations to append specific technical security requirements to standard contracts.
A.5.19 focuses on the broader process of managing supplier risk (identification, assessment, monitoring), while A.5.20 specifically focuses on the contractual establishment and agreement of security requirements.
A.5.20 is about turning security expectations into enforceable contract obligations, which often fails when agreements, addendums, and DPAs are scattered across inboxes and shared drives. WatchDog Security's Vendor Risk Management helps by linking each vendor record to required agreement types (MSA, DPA, security addendum), tracking signature status, and keeping an auditable checklist of which security clauses must be present for the vendor’s risk tier.
Organizations struggle to keep supplier security language consistent as teams reuse outdated templates or negotiate one-off terms without a baseline. WatchDog Security's Policy Management helps by maintaining controlled templates for security addendums and contractual clause standards with versioning and approval history, making it easier to roll out updated requirements and demonstrate that teams are using current, approved language.
| Version | Date | Author | Description |
|---|---|---|---|
| 1.0.0 | 2026-02-17 | WatchDog Security GRC Team | Initial publication |