Skip to main content

Shared Responsibility Model

a governance framework, adapted from cloud computing, dividing security and governance obligations between a vendor (what they control and secure) and a customer (what remains theirs to configure and govern) in a third-party service relationship.

Defined in 3 GAGE programs, which carry 4 distinct definitions of it. The wording above is taught in Certified Agentic AI Governance Professional (CAAGP).

How each discipline defines it

The same term does different work depending on who is using it. These are the definitions as each program teaches them, unedited.

Certified AI Data Governance Professional (CADGP)

The division of security and configuration responsibility between a cloud provider (typically responsible for the underlying infrastructure) and the customer organization (typically responsible for access, encryption, and retention configured on top of it), relevant to this topic because it splits the custodian role across an internal and an external party.

Certified Agentic AI Governance Professional (CAAGP)

a governance framework, adapted from cloud computing, dividing security and governance obligations between a vendor (what they control and secure) and a customer (what remains theirs to configure and govern) in a third-party service relationship.

Certified Enterprise Governance, Risk and Compliance Professional (CEGP)

A provider's published division of operational responsibility for a specific service. Differs by provider and by service, changes over time, and is not a contract term.

Certified Enterprise Governance, Risk and Compliance Professional (CEGP)

A supplier's published allocation of which layers it operates and secures and which the customer does. A map of operations, never of accountability.

Where it is taught

The exact lessons this term appears in. The first module of every program is free with a free account.

Where it shows up at work

A definition is where Shared Responsibility Model starts. The lessons above teach it inside the competencies below, which are what job descriptions ask for and what the GAGE credential records. Every link here is drawn from the same careers map that builds a role's readiness check.

Turns controls into enforceable obligations: data use, change notice, audit rights, incident duties, subcontractors, IP, exit and deletion.

One lesson on this page teach it as a primary outcome.

Tiers vendors by use and impact, requests evidence instead of promises, tests in the customer's context, and plans monitoring and exit.

One lesson on this page teach it as a primary outcome.

Establishes ownership, stewardship, councils, decision rights and issue workflows so data has a named owner and a defined meaning.

One lesson on this page teach it as a primary outcome.

Roles that hire for it

Each role page shows the full competency set, what the seat decides, and a readiness check against your own evidence.

How job descriptions say it

Postings rarely use the textbook word. These are the phrases the careers map reads as asking for the competencies above.

“data processing agreement”“audit rights”“vendor risk”“third-party risk”“third party ai”“due diligence”

Where the frameworks place it: GDPR Article 28; EU AI Act value-chain obligations; NIST AI RMF GOVERN 6 and MANAGE 3; ISO/IEC 42001 Annex A supplier controls.

One interview question about it

Which contract terms would you insist on before a vendor's model touches customer data, and what happens when the vendor changes the model?

Asked of candidates for contract terms that allocate ai risk. Answering it in your own words is exactly how a GAGE topic is passed, and the credential records the pass where an employer can check it.

If you come from another field

Some backgrounds already carry this competency, and the readiness check gives credit for it.

Terms it appears with

Not an alphabetical neighbourhood: these are the terms taught in the same lessons, ranked by how often they appear together.