ASD ISM 1569 Document and share a supplier customer shared responsibility model
What it says
A shared responsibility model is created, documented and shared between suppliers and their customers to articulate the security responsibilities of each party.
Quoted as published. Everything else on this page is written by Control Stack.
In plain English
Create, document and share a shared responsibility model between suppliers and their customers that articulates the security responsibilities of each party.
A shared responsibility model must be created, documented and shared between suppliers and their customers, to articulate the security responsibilities of each party. The model says which security tasks fall to the supplier and which to the customer. All three verbs apply: a model held only in someone's head, or by only one party, falls short. The statement names no particular kind of supplier, and it applies whichever side an organisation is on, as customer or as supplier.
Free. Save your status, tasks and notes.
Why it matters
When supplier and customer each assume the other is handling a security task, such as patching, backups or monitoring, nobody does it, and the gap may only surface during an incident. A shared written model tells each party what is theirs.
How to implement
List the supplier relationships that need a model.
Start from the supplier list (ISM-1631). The statement excludes no type of supplier, so cover products as well as services. If your organisation supplies others, it needs a model for its own customers too.
Start from the supplier's standard model if it has one.
Cloud and software service providers often publish a model you cannot change. Accept it as the base, then write your own side in detail: what your organisation must configure and run. Where a supplier has none, draft one yourself and send it.
Assign every security activity to a party.
Use a table covering access management, configuration, patching, logging, backups, incident reporting and end of service. Where a task is split, say who does which part. An activity with no name against it is a gap to close with the supplier.
Compare the model with the contract.
Contracts with service providers document security requirements (ISM-0072). Fix any conflict between the two, or record which document prevails, so both parties work from the same understanding.
Share the final version and record it.
Send it to the supplier and to the teams running the system, keep a dated copy, and record that both parties hold it. For a published model you cannot change, record the version and date you relied on. Give each customer-side task to a named person.
Keep it running
Update and re-share the model when the service scope changes, new features are turned on, the supplier changes how it runs the service, or an incident shows a responsibility was unclear. Date each version so both parties know which is current.
Evidence and audit
- Check 1 of 3What an auditor asks for
Ask for
The model for suppliers picked from the supplier list (ISM-1631) and accounts payable records, plus the organisation's own customers if it supplies others.
Look at
Whether each has a documented model, and whether a record shows both parties hold it or which published version was relied on.
Good evidence
Each picked relationship has a documented model, and a dated record shows that both the supplier and the customer hold the current version or, for a supplier's published model, which version and date the organisation relied on.
- Check 2 of 3What an auditor asks for
Ask for
A sampled model, read against the system's security activities and the contract.
Look at
Whether every security activity is assigned to a party, and whether anything conflicts with the contract.
Good evidence
Every security activity for that product or service is assigned to one party, or split with each party's part stated, and any conflict with the contract has been fixed or has a recorded decision on which document prevails.
- Check 3 of 3What an auditor asks for
Ask for
A walk-through with the team running the service, using activities the model gives to each party.
Look at
Whether the team holds the current version, and whether what happens in practice matches it.
Good evidence
The team works from the current version, and for each activity sampled, the party doing the work is the party the model names.
Mappings
Closest match in ISO/IEC 27001: A.5.19, Information security in supplier relationships, which partially overlaps with this control.
ISO/IEC 27001: 3 mappings
This control partially overlaps A.5.19.
ISM-1569 requires a documented and shared shared-responsibility model between supplier and customer to clearly assign security responsibilities. ISO/IEC 27001:2022 Annex A 5.19 requires defined processes and procedures to manage information security risks in supplier relationships, which commonly includes clarifying who does what across the engagement. Annex A 5.19 is broader around supplier risk management overall, while ISM-1569 is more specific on mutual documentation and communication of responsibility boundaries.
This control partially overlaps A.5.20.
ISM-1569 requires a documented and shared shared-responsibility model so both parties understand their respective security duties. ISO/IEC 27001:2022 Annex A 5.20 requires agreeing relevant information security requirements with each supplier in supplier agreements, which is a common mechanism to formalise responsibility allocation. Annex A 5.20 focuses on specifying requirements/clauses, whereas ISM-1569 focuses on the explicit responsibility model and its communication between parties (not only contractual requirements).
This control partially overlaps A.6.5.
Annex A 6.5 requires ongoing information security obligations to be defined, enforced and communicated when employment terminates or roles change. ISM-1569 overlaps because a documented shared responsibility model commonly includes continuing obligations after an engagement changes (e.g., confidentiality, return/handling of customer data, and notification responsibilities), which are analogous to post-termination duties. However, ISM-1569 is focused on supplier-customer accountability rather than internal employee offboarding, so it does not fully cover Annex A 6.5's personnel termination/role-change requirement.
ISO/IEC 42001: 1 mapping
This control partially overlaps A.10.2.
Annex A 10.2 requires the organisation to allocate responsibilities across the AI system life cycle between itself and external parties so duties are not left unowned. ISM-1569 directly relates by requiring a documented and shared supplier-customer shared responsibility model that articulates each party's security responsibilities. ISM-1569 is typically scoped to security responsibilities in supplier services, whereas Annex A 10.2 is broader and AI-system-life-cycle oriented (including partners, customers and other third parties beyond suppliers).
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




