Program Legacy GRC GRC Engineering
All
  • Framework-first focus
  • Documentation-heavy work products
  • Outputs conflated with outcomes
  • GRC treated as internal programs that serve the GRC team’s needs
  • Realistic risk-centered focus
  • Threat-informed everything: policies, controls, trainings, etc.
  • Systems thinking applied across the board: organizational governance, risk analysis, control modeling, etc.
  • Design thinking harnessed to make the right thing to do the easy thing to do
  • GRC treated as a product that serves internal and external customers’ needs
Governance
  • Policies, standards, procedures
  • Docs =/= control reality
  • Metric-less committees & decisions
  • Annual/semi-annual training (boring)
  • PaC enforces “risk tolerance” (pre-deploy/change)
  • “Autocorrect/reconcile” docs ↔ controls
  • Metrics-focused committees & decisions
  • Real-time behavioral interventions & scientific pedagogy
Risk
  • Qualitative risk analysis (manual)
  • Subjective data & heatmaps
  • Fragmented weaknesses & issues
  • Accountability police
  • Fear, Uncertainty, & Doubt (FUD)
  • TPCM, heavily third-party focused
  • Quantitative risk analysis (automated)
  • Objective data & histograms
  • Holistic risk scenarios (threat + vector + asset + impact)
  • Decision support partners
  • Evidence, Logic, Math, Reason (ELMR >>> FUD)
  • TPRM, balanced third + first-party focus
Compliance
  • Periodic, isolated control monitoring
  • Evidence samples
  • Automated, holistic control monitoring & active testing
  • Evidence populations (full)
Trust &
Assurance
  • Opaque, abstracted annual artifacts
  • RFIs handled via email
  • Transparent, real-time, historical visibility into controls
  • Self-service RFIs & questionnaire completion

Governance

Risk

Compliance

Trust & Assurance