Upgrade to Pro — share decks privately, control downloads, hide ads and more …

GRC: Decisions, Risk and Evidence

Sponsored · Ship Features Fearlessly Turn features on and off without deploys. Used by thousands of Ruby developers. →

GRC: Decisions, Risk and Evidence

A practical introduction to linking governance, risk and compliance in a cloud-service decision. Includes decision rights, evidence and a review checklist. Based on the original article: https://manfredimarrocco.blog/2026/10/05/grc-governance-rischio-compliance/

Manfredi Marrocco

November 03, 2026

Transcript

12 slides
  1. CYBERSECURITY & GOVERNANCE | GRC: decisions, risk and evidence |

    A practical introduction for technology and business teams | Manfredi Marrocco · manfredimarrocco.blog
  2. INSIGHTS / GRC | One decision, three perspectives | A

    team wants a new cloud service. | Business seeks speed; security raises risk; compliance checks obligations. | GRC connects these perspectives before the decision. | Manfredi Marrocco · 02
  3. INSIGHTS / GRC | Start with the objective | What

    outcome is the organisation trying to achieve? | Name the service, its users and the decision that is actually needed. | A risk statement without an objective can miss what matters. | Manfredi Marrocco · 03
  4. INSIGHTS / GRC | Governance: who decides? | Clarify decision

    rights, accountability, resources and oversight. | A service owner, risk owner and approving authority may be different people. | Record who is empowered to accept residual risk. | Manfredi Marrocco · 04
  5. INSIGHTS / GRC | Risk: what can affect the objective?

    | Describe an event, its causes and consequences. | Consider access compromise, service interruption and supplier dependency. | Prioritise with proportionate evidence and acknowledge uncertainty. | Manfredi Marrocco · 05
  6. INSIGHTS / GRC | Compliance: which requirements apply? | Identify

    obligations from laws, contracts and internal policies. | Map each relevant requirement to an owner and evidence. | A recommendation is not automatically a legal obligation. | Manfredi Marrocco · 06
  7. INSIGHTS / GRC | The cloud-service decision | Objective: provide

    a service reliably. | Risk: provider outage interrupts customer access. | Requirement: applicable contract and data-processing commitments. | Decision: assess alternatives, controls and residual exposure. | Manfredi Marrocco · 07
  8. INSIGHTS / GRC | Controls and evidence | A contractual

    clause records a commitment. | A recovery test provides evidence about a particular capability. | Neither proves every control works in all circumstances. | Record test scope, date, findings and limitations. | Manfredi Marrocco · 08
  9. INSIGHTS / GRC | Link the chain | OBJECTIVE |

    RISK / REQUIREMENT | DECISION | CONTROL | OWNER | EVIDENCE | REVIEW | Manfredi Marrocco · 09
  10. INSIGHTS / GRC | What happens when things change? |

    A new integration, supplier change or failed recovery test can alter the decision. | Assign a trigger to review the risk and the control. | Separate planned improvements from demonstrated capability. | Manfredi Marrocco · 10
  11. INSIGHTS / GRC | A short decision checklist | What

    is the objective? What can go wrong? | Which requirements apply? Who can decide? | Which evidence supports the control? | What uncertainty remains and when will we review it? | Manfredi Marrocco · 11
  12. INSIGHTS / GRC | Sources and further reading | Original

    article: manfredimarrocco.blog/2026/10/05/grc-governance-rischio-compliance/ | OCEG: oceg.org/ideas/what-is-grc/ | NIST IR 8286C Rev. 1: csrc.nist.gov/pubs/ir/8286/c/r1/final | Manfredi Marrocco · manfredimarrocco.blog | Manfredi Marrocco · 12

More Decks by Manfredi Marrocco

Other Decks in Technology