Home→Blog→Building Security Champions Programs: From Selecti...
People

Building Security Champions Programs: From Selection to Impact Measurement

Create a distributed security awareness network through volunteer champions in each department. Selection criteria, training pathways, time commitment, recognition programs, and measuring real impact on security behaviours.

Alpesh Nakar
Sep 16, 2025
9 min read
🇦🇺 Australian Context
📜 Privacy Act, ACSC

⚡TL;DR

  • •Security champions drive behaviour change through peer credibility: employees trust respected colleagues more than IT lectures
  • •Selection criteria: attitude over technical knowledge, influential in teams, curious about security; target 5-10% of workforce as champions
  • •Training pathway: monthly 45-min security team calls, quarterly deep dives on emerging threats, role-specific training (finance: BEC, HR: W-2 phishing)
  • •Responsibilities: monthly 30-min team briefings, answering peer questions, reporting incidents; 2-4 hours monthly commitment
  • •Recognition programs: public newsletters, performance reviews, tangible incentives (gift cards, professional development); annual champion awards
  • •Impact measurement: team phishing click rates, incident reporting velocity, voluntary training participation; champions outperform non-champion teams by 3-5%

1. Why champions work (psychology of peer influence)

  • Credibility perception: Employees trust champions more than IT. Champions are peers facing same work pressures, understanding business context.
  • Relevance: Finance champion explains BEC red flags in finance context (invoice approvals, payment verification). Sales champion explains account takeover risks in sales context (deal loss, customer contact theft). IT generalisation doesn't land.
  • Accessibility: Champions sit next to employees. "Quick question: Is this email suspicious?" is easier peer conversation than booking IT security meeting.
  • Local accountability: Champions embed security norms in team culture. Peer accountability is stronger than external enforcement.
  • Sustainability: When IT personnel leave organisation, programs disappear. Champion networks sustain through turnover because they're embedded in team structure.

2. Selection criteria for effective champions

  • Attitude over technical knowledge: Choose champions who are curious, respected, and willing to grow. Technical expertise is not required-you will provide training.
  • Influence in their team: Is this person someone colleagues ask for advice? Do they have informal authority? That's your champion. Skip the formal hierarchy-best champion might be senior individual contributor, not manager.
  • Diversity across departments:
    • Finance/Accounting: 1-2 champions (high-value BEC targets)
    • HR/Recruitment: 1-2 champions (W-2 phishing, credential harvesting)
    • Sales/Customer Success: 1-2 champions (account takeover, deal fraud)
    • Engineering/IT: 1-2 champions (insider threat, secrets management, supply chain)
    • Marketing/Communications: 1 champion (brand impersonation, social engineering)
    • Operations/Administration: 1 champion (general awareness for support staff)
  • Target: 5-10% of workforce as champions
    • 50-person org: 3-5 champions
    • 100-person org: 5-10 champions
    • 500-person org: 25-50 champions
    • Quality matters more than quantity. Engaged 5 champions beat disengaged 20.
  • Time commitment: 2-4 hours monthly (easily absorbed). 1-2 hour monthly training call with security team. 30-min to 1-hour monthly team briefing. 30 min for ad-hoc peer questions. Reasonable ask for driven employees.

3. Recruitment and kickoff

  • Approach: Personal invitation from CISO or security leader (not broadcast email). "We think you're someone colleagues respect and turn to for advice. We want to invest in security champions network, and we'd like you to lead this in your department."
  • Value proposition:
    • Professional development: Learn emerging threats, deepen security knowledge
    • Career visibility: CISO recognises your contribution; noted in performance reviews
    • Peer leadership: Lead security initiatives in your team
    • Relatively low time commitment: 2-4 hours monthly
  • Kickoff workshop (2 hours):
    • Threat landscape briefing (current threats facing Australian organisations)
    • Your role and responsibilities as champion (facilitator, not enforcer)
    • Monthly team briefing framework (30-min agenda, how to keep it engaging)
    • Resources you will receive (template presentations, one-pagers, case studies, phishing scenario descriptions)
    • Q&A and relationship building with other champions
  • Ongoing support structure:
    • Monthly security team call with all champions (45 min): threat briefing, Q&A, peer discussion
    • Slack/Teams channel for champions to ask questions and share resources
    • Quarterly in-person champion summit (optional but encouraged) for deeper connection

4. Training pathway for champions

Month 1: Foundation

  • Threat landscape overview (phishing, social engineering, insider threats, ransomware)
  • Your role: facilitator and peer educator, not police
  • Resources: presentation templates, one-pagers, phishing scenario descriptions

Months 2-6: Role-specific deep dives

  • Finance champions: BEC tactics, invoice fraud red flags, payment verification workflows
  • HR champions: W-2 phishing, fake job applicant credential harvesting, insider threat indicators
  • Sales champions: Account takeover risks, deal fraud, contact list theft
  • IT/Engineering champions: Secrets management, supply chain attacks, secure coding, insider threat

Months 7-12: Emerging threats and refinement

  • AI-powered phishing (deepfakes, voice cloning)
  • Supply chain attacks targeting your industry
  • Ransomware variants and attack patterns
  • Reflection on what's working in your team; iteration on messaging

5. Champion responsibilities and monthly team briefings

  • Core responsibility: 30-min monthly team briefing covering one security topic or incident case study. Informal, conversational, not lecturing.
  • Briefing structure (30 minutes):
    • 5 min: Real-world case study (anonymised incident relevant to your industry or company)
    • 10 min: Red flags to watch for in your role-specific context
    • 10 min: What to do if you spot suspicious activity (report workflow)
    • 5 min: Q&A and peer discussion
  • Secondary responsibilities:
    • Answering peer security questions (informal, ad-hoc)
    • Promoting phishing simulations and training campaigns in your team
    • Identifying at-risk employees who need additional support (private conversations with IT)
    • Participating in quarterly champion network meetings
    • Reporting suspicious emails from your team promptly
  • What champions are NOT:
    • Police or enforcers ("I caught John visiting a gambling site"-no, don't do this)
    • Security experts ("I don't know ransomware details, that's IT's domain"-completely fine to say)
    • Expected to spend hours per month (if you're spending 10+ hours, you're doing too much)
    • Solo effort (they should collaborate with other champions, IT, and security)

6. Resource and training delivery

  • Monthly briefing templates: Pre-built slide decks, talking points, case study descriptions. Champions personalise with local context, not start from blank page.
  • Resource library (shared portal or Slack):
    • One-pagers on key topics (phishing red flags, password management, incident reporting)
    • Real incident case studies (anonymised) with lessons learned
    • Video clips (2-5 min) on specific threats
    • Scenario-based decision trees ("Is this email suspicious? Follow this workflow to check")
  • Monthly security team call (45 min):
    • First 20 min: Threat briefing (emerging attacks, latest vulnerabilities, industry-specific threats)
    • Next 15 min: Deep dive on one topic (this month: BEC tactics, next month: phishing red flags, etc.)
    • Last 10 min: Q&A, peer discussion, champions sharing what's working in their teams
  • Quarterly champion summit (half-day, optional but encouraged):
    • In-person connection (even 2-3 hour session builds relationship and knowledge-sharing)
    • Advanced threat briefing from security team
    • Peer group discussions: What's working? What's not? How do we overcome resistance?
    • Celebration of impact (metrics dashboard showing click rate improvements, reporting increases)

7. Recognition and incentive programs

  • Public recognition:
    • Mention champions in monthly company security newsletter
    • Call-out in all-hands meetings ("Our champions led 12 team briefings this month on phishing awareness")
    • Leadership testimonials (CEO/CISO recognises champion contributions in written communication)
  • Career development:
    • Noted in performance reviews: "Champion role demonstrates leadership, initiative, and commitment to organisational security"
    • Priority access to advanced security certifications (training budget allocated to champions)
    • Internal mobility preference: champion experience valued in hiring for security-adjacent roles
  • Tangible incentives:
    • Gift cards (AUD $100-200 annually per champion for exceptional contribution)
    • Professional development allowance (AUD $500 toward security certification or conference attendance)
    • Flexible time: 2-4 hours monthly champion work can count toward professional development time (not additional work)
  • Annual champion recognition event:
    • Celebration of champion cohort impact (metrics: click rate reduction, reporting increase, incident reduction)
    • Awards: "Most Impact," "Most Engaged," "Rising Star" (recognition and AUD $200-500 gift card)
    • Executive attendance and speeches (CEO, CISO, CFO recognising champion contributions)
    • Peer networking and relationship strengthening

8. Measuring champion impact

  • Metric 1: Team phishing click rate improvement
    • Establish a baseline click rate for each team before the champion starts
    • Track the click rate at six and twelve months to show the trend over time
    • Compare champion teams to non-champion teams (champions' teams typically outperform)
  • Metric 2: Incident reporting velocity
    • Establish a baseline for how long the team takes to report a suspicious email to IT
    • With an active champion, expect reporting times to drop substantially as the team recognises and reports quickly
  • Metric 3: Voluntary training participation
    • % of champions' teams completing optional advanced training modules
    • Attendance at champion-led briefings (>80% attendance in champion teams typical)
  • Metric 4: Incident reduction
    • Successful phishing attacks in champion teams vs non-champion teams
    • BEC fraud, credential compromise, data exfiltration incidents (lower in champion teams)
  • Metric 5: Champion satisfaction and sustainability
    • Annual champion survey: "Do you find the role valuable? Would you continue next year?"
    • Retention rate: >70% champions continuing role year-to-year indicates program is working

9. Scaling and sustaining champions programs

  • Year 1: Establish pilot champion network (10-20 champions). Build infrastructure (monthly calls, resource library, briefing templates). Demonstrate impact (metrics dashboard).
  • Year 2: Expand to 20-40% of target champions. Add second-tier champions who support primary champions. Establish champion mentor relationships (experienced champions mentor new ones).
  • Year 3+: Full mature network. Champions are embedded in team structure. Onboarding includes orientation to champion network. Turnover is managed (new champion recruited when existing champion departs).
  • Budget: AUD $15-25K annually for 200-person organisation (champion recognition, training resources, coordination). The return through reduced incidents typically far outweighs this investment.

10. Common pitfalls and solutions

  • Pitfall: Champions become too technical, losing peer credibility
    • Fix: Remind champions: "You are not expected to be security experts. Your role is peer educator, not IT lecture." Provide simple talking points and templates. Keep briefings accessible to non-technical employees.
  • Pitfall: Champions burn out from excessive time commitment
    • Fix: Set clear boundaries (2-4 hours monthly). Provide pre-built resources so they're not creating presentations from scratch. Check in quarterly-if champion says they're overloaded, adjust expectations or redistribute work.
  • Pitfall: Champions not recognised or valued by their managers
    • Fix: Secure manager buy-in before recruiting. Frame champion role as professional development opportunity. Include champion work in performance review discussions. Celebrate champions publicly so managers see value.
  • Pitfall: Champions' teams don't engage (briefings feel like IT lecture)
    • Fix: Coach champions on engagement techniques (ask for input, encourage questions, use real-world stories, keep it conversational). Provide "discussion starter" scenarios. Celebrate team improvements publicly so engagement is rewarded.
  • Pitfall: Champion network dissolves when IT personnel leave
    • Fix: Don't create dependency on single IT person. Assign backup security liaison to champion network. Train 2-3 IT staff on champion program operation. Document processes in shared knowledge base.

Call to action

Security champions networks are the highest-ROI awareness program available. Peer educators drive behaviour change faster than IT lectures. Start recruiting 5-10 champions this month. Invest in their training and recognition. Measure team-level impact on click rates, reporting velocity, and incident reduction. Your network will become the foundation of sustainable security culture.

Next steps: Identify 5-10 respected colleagues across departments who would make excellent champions. Reach out with personal invitation this week. Schedule kickoff workshop for next month. Commit to monthly champion calls and quarterly summits.

Assess Your Maturity

Understand where your organisation stands on the Essential Eight maturity model and identify priority controls.

Train Your Team

Hands-on Essential Eight fundamentals course for security teams, architects, and IT leaders.

Frequently Asked Questions

Questions security teams commonly ask about Essential Eight implementation.

Ready to Move from Level 1 to Level 2+?

Start your 12-month Essential Eight maturity journey with expert guidance and practical roadmaps.

Read Next

Continue exploring security insights and best practices

People
Sep 19, 2025
8 min read

Quantify the value of security training through cost-benefit analysis, breach cost avoidance, phishing click rate reduction ROI, and Australian breach cost data to justify ongoing security awareness investment.

Security Culture
Aug 14, 2025
16 min read

Beyond policies and training, learn how to cultivate a genuine security culture where employees become active defenders rather than the weakest link in your cyber security posture.

SharePoint Governance
Nov 3, 2026
12 min read

Copilot does not break your permissions. It reveals them. Five checks a site owner can run in under an hour, no admin rights needed, before Copilot reaches your site.