.github/workflows/security-training.yml

// types/security-learning.ts
export interface SecurityModule {
  id: string;
  title: string;
  description: string;
  vulnerabilityPatterns: string[]; // Regex or AST patterns
  secureExamples: string[];
  riskLevel: 'LOW' | 'MEDIUM' | 'HIGH' | 'CRITICAL';
  estimatedDuration: number; // Minutes
}

export interface FindingToModuleMap {
  [ruleId: string]: string[]; // SAST Rule ID -> Module IDs
}

// .github/actions/security-bot/index.ts
import { context, getOctokit } from '@actions/github';
import { FindingToModuleMap } from './mapping';

const octokit = getOctokit(process.env.GITHUB_TOKEN);

async function run() {
  const sarifPath = process.env.SARIF_PATH;
  const findings = parseSarif(sarifPath);
  
  for (const finding of findings) {
    const moduleIds = FindingToModuleMap[finding.ruleId];
    if (moduleIds && moduleIds.length > 0) {
      const modules = moduleIds.map(id => 
        `- [Learn: ${getModuleTitle(id)}](${getModuleUrl(id)})`
      ).join('\n');

      const comment = `
        ⚠️ **Security Finding:** ${finding.me

ssage}

    **Recommended Action:**
    ${finding.fix}
    
    **Training:**
    ${modules}
    
    *This comment is generated by the Codcompass Security Bot.*
  `;

  await octokit.rest.issues.createComment({
    owner: context.repo.owner,
    repo: context.repo.repo,
    issue_number: context.issue.number,
    body: comment
  });
}

} }

#### 3. Implement IDE Extensions for Real-Time Feedback
Developers spend most time in the IDE. An extension that highlights insecure patterns as they type and offers quick-fixes with learning links reinforces training continuously.

*   **Implementation:** Build a VS Code extension using the Language Server Protocol (LSP).
*   **Feature:** When a developer hovers over a flagged line, show a tooltip with the security explanation and a "Show Me the Fix" button.

```typescript
// vscode-extension/src/securityLinter.ts
import * as vscode from 'vscode';
import { insecurePatterns } from './patterns';

export function activate(context: vscode.ExtensionContext) {
  const diagnosticCollection = vscode.languages.createDiagnosticCollection('security');

  context.subscriptions.push(
    vscode.workspace.onDidChangeTextDocument((event) => {
      const diagnostics: vscode.Diagnostic[] = [];
      const text = event.document.getText();

      insecurePatterns.forEach(pattern => {
        const regex = new RegExp(pattern.regex, 'g');
        let match;
        while ((match = regex.exec(text)) !== null) {
          const range = new vscode.Range(
            event.document.positionAt(match.index),
            event.document.positionAt(match.index + match[0].length)
          );
          
          const diagnostic = new vscode.Diagnostic(
            range,
            pattern.message,
            vscode.DiagnosticSeverity.Warning
          );
          
          diagnostic.code = {
            value: pattern.ruleId,
            target: vscode.Uri.parse(pattern.learningUrl)
          };
          
          diagnostic.source = 'Codcompass Security';
          diagnostics.push(diagnostic);
        }
      });

      diagnosticCollection.set(event.document.uri, diagnostics);
    })
  );
}

4. Gamify via Engineering Metrics

Replace completion rates with engineering metrics. Track "Security Debt Reduction" and "Secure Pattern Adoption." Recognize developers who fix vulnerabilities quickly or contribute to the security knowledge base.

• Dashboard: Build an internal dashboard showing team vulnerability trends, average time to apply security fixes, and the number of learning modules completed per sprint.

Architecture Decisions

• Decoupled Content Service: Host learning modules on a separate service. This allows security teams to update content without rebuilding CI pipelines or IDE extensions.
• SARIF Standardization: Use SARIF for tool output to ensure compatibility across SAST scanners (Semgrep, CodeQL, SonarQube).
• Blameless Culture: The system must be configured to encourage fixing issues, not punishing developers. Metrics should focus on improvement, not individual fault.

Pitfall Guide

1. The "Click-Next" Fatigue

Mistake: Relying on video modules where developers click through without absorbing content. Fix: Replace videos with interactive code challenges. Use platforms like Codecademy-style sandboxes or internal CTFs where developers must write secure code to pass.

2. Generic Content

Mistake: Providing training on SQL injection to a team that only builds React frontends and uses GraphQL. Fix: Tailor training to the tech stack. Use SAST findings to identify the specific vulnerabilities relevant to the codebase and prioritize those modules.

3. Fear-Based Motivation

Mistake: Using scare tactics ("You will be fired if you cause a breach"). Fix: Focus on empowerment. Frame security as a professional skill that increases code quality and system reliability. Celebrate secure engineering wins.

4. Ignoring Senior Developers

Mistake: Training only junior developers while seniors continue insecure practices. Fix: Require all developers, including staff and principal engineers, to participate in threat modeling and code review security checks. Seniors must model secure behavior.

5. No Feedback Loop

Mistake: Delivering training without measuring its impact on code quality. Fix: Correlate training completion with vulnerability metrics. If a team completes a module on XSS but XSS findings do not drop, the training is ineffective or the tooling is missing.

6. Treating Security as a Gate

Mistake: Blocking PRs for every minor security warning without context. Fix: Implement risk-based gating. Block only critical/high findings. For medium/low, require a fix or a documented risk acceptance. Use the bot to educate, not just block.

7. Over-Reliance on Automation

Mistake: Assuming SAST/DAST tools cover all security risks. Fix: Supplement automated training with manual threat modeling workshops. Tools catch known patterns; humans catch logic flaws and architectural risks.

Production Bundle

Action Checklist

• Audit Current Findings: Export the last 6 months of SAST/DAST findings and categorize by rule and frequency.
• Build Module Map: Create a FindingToModuleMap linking top vulnerability rules to specific learning resources.
• Deploy PR Bot: Implement a CI job that posts educational comments on PRs with security findings.
• Configure IDE Extension: Roll out the custom linter extension to all developer workstations.
• Establish Metrics: Define KPIs for vulnerability density, MTTR, and training engagement.
• Launch Security Champions: Identify and train security champions in each team to drive adoption.
• Run Baseline Assessment: Measure current vulnerability density and MTTR before rolling out changes.
• Review Monthly: Analyze metrics monthly and iterate on training content based on new vulnerability trends.

Decision Matrix

Scenario	Recommended Approach	Why	Cost Impact
Startup / Small Team	PR Bot + ESLint Plugin	Low overhead, immediate feedback, easy to implement.	Low
Enterprise / Legacy Code	SAST Integration + Champion Program	Scalable, addresses legacy debt, builds internal expertise.	Medium
High Compliance (Fin/Med)	Integrated Training + Automated Gating	Ensures auditability, reduces risk of critical findings.	High
High Churn Team	IDE Extension + Onboarding Module	Reduces time-to-competency, consistent baseline for new hires.	Medium
Embedded / IoT	Threat Modeling + Custom Linter	Tools may not cover hardware constraints; human analysis critical.	High

Configuration Template

Use this GitHub Action template to integrate security training into your CI pipeline.

# .github/workflows/security-training.yml
name: Security Training Integration

on:
  pull_request:
    branches: [ main ]

jobs:
  security-scan:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout Code
        uses: actions/checkout@v3

      - name: Run SAST Scan
        uses: github/codeql-action/analyze@v2
        with:
          output: sarif-results.sarif

      - name: Post Educational Comments
        uses: actions/github-script@v6
        env:
          SARIF_PATH: sarif-results.sarif
        with:
          script: |
            const script = require('./.github/actions/security-bot/index.js');
            await script.run();

Quick Start Guide

1. Install the Linter: Add the custom ESLint plugin to your project dependencies.

   npm install --save-dev @codcompass/eslint-plugin-security
   

2. Configure ESLint: Update .eslintrc.js to extend the security plugin.

   module.exports = {
     extends: ['plugin:@codcompass/security/recommended'],
     rules: {
       '@codcompass/security/no-eval': 'warn',
       '@codcompass/security/secure-fetch': 'error'
     }
   };
   

3. Add Mapping File: Create security-mapping.json in the root directory linking rule IDs to learning URLs.
4. Commit and Push: Push changes to trigger the PR bot. Verify that comments appear on PRs with security findings.
5. Verify IDE Feedback: Open a file with a vulnerable pattern and confirm the warning and learning link appear in the IDE.

By engineering security training directly into the developer workflow, you transform security from a compliance burden into a core engineering competency. This approach reduces vulnerabilities, accelerates remediation, and builds a culture where security is an inherent part of code quality.