name security-champion-program description Design and run an organizational security champion program: role definitions, selection, training paths, office hours, metrics, and escalation between product teams and AppSec. Use when security champions, AppSec champions, federated security program, champion RACI, security office hours, or building distributed security ownership inside engineering orgs.
Security Champion Program
Design a security champion program that embeds practical security ownership
in product teams without making every engineer full-time AppSec. Org process
design (roles, enablement, rituals, metrics, escalation) โ not exploit work.
When To Use
Standing up or refreshing a security champion / federated AppSec network
Defining champion roles , time allocation, and RACI with central AppSec
Building training , office hours, review habits, and first-pass triage
Choosing program metrics and escalation paths to AppSec / IR
Mentions: security champions, AppSec champions, federated security, security
guild, office hours, ๅฎๅ
จๅคงไฝฟ, ๅฎๅ
จๅ ๅ
Do not use as primary for:
Need Skill instead SSDLC phase gates / release policy secure-sdlc-checklistSTRIDE workshop facilitation threat-modeling-strideSAST/DAST operation and triage sast-dast-tooling-usageIncident runbook / SEV operator steps incident-runbook-writingImplementation hardening / recon code-quality-standards / recon-and-methodology
Scope And Principles
In scope: Org-owned teams; champions; training; office hours; metrics;
escalation SLAs; recognition and capacity protection.Out of scope: Unauthorized third-party testing; unpaid heroics replacing
AppSec hiring; champion as default SEV-1 on-call.Org policy, risk matrix, and existing SDLC gates outrank generic templates.
Champions amplify AppSec; they alone do not accept Critical residual risk.
Coverage: one champion per squad/domain + backup; avoid multi-domain sprawl.
Core Roles
Role Owns Does not own Champion (per squad/domain)Local questions, PR security habits, first-pass scanner triage, training relay, early risk tickets Org policy, Critical risk accept, IR command AppSec Standards, tools, deep threat work, exceptions, severity SLAs, coaching Day-to-day feature delivery for every squad Eng manager Time protection, gate adherence, security debt priority Being the sole security expert Product / risk acceptor Written business risk accept + review date Technical control design alone
Workflow
1. Charter and sponsorship
One-page charter : purpose, in/out of scope, time budget (e.g. 10โ20% or
fixed hours/sprint), success criteria for 2โ3 quarters.
Secure a sponsor who protects time and credits champion work in reviews.
Align to secure-sdlc-checklist so champions enforce existing gates โ not a
parallel process.
Publish RACI: design review, scanner findings, exceptions, incidents, vendors.
2. Select and onboard
Prefer influential volunteers (senior IC/tech lead) with manager sign-off.
Onboard kit: severity model, lite threat-model checklist, secure PR
checklist, tool access, escalation contacts, secrets/PII redaction norms.Pair with AppSec 2โ4 weeks (shadow office hours; co-review one high-risk PR).
Keep a roster : team, backup, start date, training stage.
3. Training path
Stage Focus Outcome Foundations Data class, authZ, secrets, log redaction, SSDLC gates Spots high-risk changes Domain track Web/API, cloud, mobile, data/ML as relevant Applies local checklists Facilitation Prep for threat-modeling-stride workshops Escalates with DFDs Continuous Brown-bags, postmortem themes, FP clinics Skills stay current
Pair with code-quality-standards and secrets-management-hygiene; add class
skills only when the team surface requires them.
4. Rituals
AppSec office hours (weekly): designs, PR questions, exception drafts โ
not full IR bridges.Planning loop: champion flags high-risk stories (auth, money, admin, PII,
new trust boundaries).PR habit: high-risk PRs get checklist review; deep issues escalate with
evidence.Champion guild (monthly): patterns, tool pain, top risks โ action-logged.Document office hours vs ticket vs SEV path.
5. Escalation
Trigger Path Design uncertainty / new boundary Champion prep โ AppSec / threat-modeling-stride Suspected Critical in owned system Champion โ AppSec triage โ IR if active exploit Scanner Critical/High Champion first-pass โ AppSec on dispute (org SLA) Residual risk accept Draft โ product + AppSec + named acceptor + expiry Third-party / no auth Stop โ vendor/legal process only
6. Metrics and sustainability
Metric Why Coverage (% squads with named + backup) Blind spots Time budget honored Burnout prevention High-risk changes with design/threat-model link Shift-left quality Median High โ owned ticket with due date Flow, not heroics Office-hours unblock rate; exception age Enablement + risk hygiene
Avoid ranking teams by raw finding volume. Recognize wins; rotate/backfill with
handoff after 12โ18 months; champions are not default SEV-1 page.
Routing
Situation Primary Helper Champion program, roles, training, office hours, metrics This skill โ Lifecycle gates champions enforce secure-sdlc-checklistthis skill (people model) Deep STRIDE workshops threat-modeling-stridethis skill (who prepares) Scanner triage playbooks sast-dast-tooling-usagethis skill (first-pass owner) Incident operator procedures incident-runbook-writingthis skill (champion vs IR) Code fixes / secure review quality code-quality-standardsalways on code changes
Output Checklist
