Security Training
Design a security awareness and training program for "$ARGUMENTS" with role-based modules, training cadence, completion tracking, and assessment questions.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"security-security-training","workflow":"security","phase":null,"project":"<project>","event":"skipped","artifact":"<artifact file>","note":"<reason or \"none given\">"}.
Process
Define training audiences:
- All employees — baseline security awareness for the entire organization
- Developers — secure coding practices and application security
- Operations / DevOps — infrastructure security and incident response
- Security team — advanced security skills and certifications
- Leadership / executives — risk governance, compliance, and security investment decisions
- Identify audience-specific risk profiles and knowledge gaps
Design modules per audience:
All employees (baseline awareness):
- Phishing and social engineering recognition (email, phone, SMS, physical)
- Password hygiene and authentication best practices (password managers, MFA)
- Safe browsing and email handling (suspicious links, attachments, downloads)
- Data handling and classification (what is sensitive, how to handle it)
- Physical security awareness (badge access, clean desk, visitor policy)
- Reporting security incidents (what to report, how to report, no-blame culture)
- Remote work security (VPN, public Wi-Fi, device security)
Developers (secure development):
- OWASP Top 10 vulnerabilities with hands-on examples
- Secure coding practices for the organization's technology stack
- Input validation, output encoding, and parameterized queries
- Authentication and session management implementation
- Secrets management in code and configuration
- Secure code review techniques and checklist
- Dependency management and supply chain security
- Security testing integration (SAST, DAST, SCA in CI/CD)
Operations / DevOps (infrastructure security):
- Infrastructure-as-code security and hardening
- Cloud security posture management (IAM, network, storage, logging)
- Container and Kubernetes security
- Network security and segmentation
- Monitoring, logging, and alerting for security events
- Incident response procedures and on-call responsibilities
- Backup and disaster recovery procedures
Security team (advanced skills):
- Threat intelligence analysis and application
- Digital forensics and incident investigation
- Penetration testing and red team exercises
- Security architecture review and design
- Emerging threats and attack techniques
- Certification paths (CISSP, CEH, OSCP, SANS courses)
Leadership (risk governance):
- Cybersecurity risk landscape and business impact
- Regulatory compliance obligations and liability
- Security investment decision-making and ROI
- Incident response governance and communication
- Third-party and supply chain risk oversight
- Board-level reporting on security posture
Set training cadence:
- All employees: annual mandatory training + quarterly phishing simulations + monthly security tips
- Developers: annual secure coding training + quarterly lunch-and-learn + on-demand for new technologies
- Operations: annual infrastructure security training + quarterly tabletop exercises
- Security team: continuous professional development + annual certification renewal
- Leadership: semi-annual briefing + annual board-level security update
- New hire onboarding: security training within first week
Define completion tracking:
- Track training completion by employee, department, and role
- Set compliance targets (e.g., 95% completion within 30 days of assignment)
- Escalate non-completion to managers after 2 reminders
- Report completion metrics to leadership monthly
- Maintain training records for compliance audits (retain for 3+ years)
Create assessment questions:
- Design knowledge checks per module (minimum 5 questions per module)
- Include scenario-based questions testing practical application
- Set passing threshold (80% minimum)
- Require remediation training for failed assessments
- Track assessment scores to identify knowledge gaps across the organization
Plan training delivery:
- Mix of formats: e-learning modules, live workshops, hands-on labs, simulations
- Phishing simulation program with graduated difficulty
- Gamification elements where appropriate (leaderboards, badges, recognition)
- Localization for distributed teams if applicable
- Measure training effectiveness through phishing simulation click rates and incident reduction
Write the artifact to .singularskills/security/<project>/security-training.md with heading:
Security Training Program
Include sections:
- Training Audiences — role definitions and risk profiles
- Module Catalog — per-audience training modules with objectives
- Training Cadence — schedule and frequency per audience
- Completion Tracking — metrics, targets, and escalation procedures
- Assessment Framework — question design, passing thresholds, and remediation
- Delivery Plan — formats, tools, and effectiveness measurement
Output
The security training program written to .singularskills/security/<project>/security-training.md. Present a summary to the user highlighting:
- Training audiences and their specific module focus
- Key modules per role with learning objectives
- Training cadence and compliance targets
- Assessment approach and effectiveness measurement
End the artifact with this paragraph, verbatim:
Not a penetration test or audit. This artifact is generated analysis; validate findings against the live system and have material controls reviewed by a qualified security professional.
1---2name: security-security-training3description: Design a security awareness and training program by audience — all staff, developers, operations, security team, leadership — with modules, cadence, completion tracking, quizzes and phishing simulations. Use when the user needs to train employees on security, run phishing tests, or show training records to an auditor. Not for legal compliance training; see /legal-training-plan.4metadata:5 source: https://skillmd.com/skills/bromso/security-security-training6 argument-hint: "[project] [--skip-checks]"7---89# Security Training1011Design a security awareness and training program for "$ARGUMENTS" with role-based modules, training cadence, completion tracking, and assessment questions.1213**Arguments.** `$ARGUMENTS` may contain the project name and optional flags. Take the first token as `<project>` and treat `--skip-checks` as a flag; never include flags in file paths. All paths below use `<project>`. If `--skip-checks` is present, skip the prerequisite check and, **before writing any artifact**, append one line to `.singularskills/log.jsonl`: `{"ts":"<ISO timestamp>","skill":"security-security-training","workflow":"security","phase":null,"project":"<project>","event":"skipped","artifact":"<artifact file>","note":"<reason or \"none given\">"}`.1415## Process16171. **Define training audiences:**18 - **All employees** — baseline security awareness for the entire organization19 - **Developers** — secure coding practices and application security20 - **Operations / DevOps** — infrastructure security and incident response21 - **Security team** — advanced security skills and certifications22 - **Leadership / executives** — risk governance, compliance, and security investment decisions23 - Identify audience-specific risk profiles and knowledge gaps24252. **Design modules per audience:**2627 **All employees (baseline awareness):**28 - Phishing and social engineering recognition (email, phone, SMS, physical)29 - Password hygiene and authentication best practices (password managers, MFA)30 - Safe browsing and email handling (suspicious links, attachments, downloads)31 - Data handling and classification (what is sensitive, how to handle it)32 - Physical security awareness (badge access, clean desk, visitor policy)33 - Reporting security incidents (what to report, how to report, no-blame culture)34 - Remote work security (VPN, public Wi-Fi, device security)3536 **Developers (secure development):**37 - OWASP Top 10 vulnerabilities with hands-on examples38 - Secure coding practices for the organization's technology stack39 - Input validation, output encoding, and parameterized queries40 - Authentication and session management implementation41 - Secrets management in code and configuration42 - Secure code review techniques and checklist43 - Dependency management and supply chain security44 - Security testing integration (SAST, DAST, SCA in CI/CD)4546 **Operations / DevOps (infrastructure security):**47 - Infrastructure-as-code security and hardening48 - Cloud security posture management (IAM, network, storage, logging)49 - Container and Kubernetes security50 - Network security and segmentation51 - Monitoring, logging, and alerting for security events52 - Incident response procedures and on-call responsibilities53 - Backup and disaster recovery procedures5455 **Security team (advanced skills):**56 - Threat intelligence analysis and application57 - Digital forensics and incident investigation58 - Penetration testing and red team exercises59 - Security architecture review and design60 - Emerging threats and attack techniques61 - Certification paths (CISSP, CEH, OSCP, SANS courses)6263 **Leadership (risk governance):**64 - Cybersecurity risk landscape and business impact65 - Regulatory compliance obligations and liability66 - Security investment decision-making and ROI67 - Incident response governance and communication68 - Third-party and supply chain risk oversight69 - Board-level reporting on security posture70713. **Set training cadence:**72 - **All employees:** annual mandatory training + quarterly phishing simulations + monthly security tips73 - **Developers:** annual secure coding training + quarterly lunch-and-learn + on-demand for new technologies74 - **Operations:** annual infrastructure security training + quarterly tabletop exercises75 - **Security team:** continuous professional development + annual certification renewal76 - **Leadership:** semi-annual briefing + annual board-level security update77 - New hire onboarding: security training within first week78794. **Define completion tracking:**80 - Track training completion by employee, department, and role81 - Set compliance targets (e.g., 95% completion within 30 days of assignment)82 - Escalate non-completion to managers after 2 reminders83 - Report completion metrics to leadership monthly84 - Maintain training records for compliance audits (retain for 3+ years)85865. **Create assessment questions:**87 - Design knowledge checks per module (minimum 5 questions per module)88 - Include scenario-based questions testing practical application89 - Set passing threshold (80% minimum)90 - Require remediation training for failed assessments91 - Track assessment scores to identify knowledge gaps across the organization92936. **Plan training delivery:**94 - Mix of formats: e-learning modules, live workshops, hands-on labs, simulations95 - Phishing simulation program with graduated difficulty96 - Gamification elements where appropriate (leaderboards, badges, recognition)97 - Localization for distributed teams if applicable98 - Measure training effectiveness through phishing simulation click rates and incident reduction991007. **Write the artifact** to `.singularskills/security/<project>/security-training.md` with heading:101102 ## Security Training Program103104 Include sections:105 - **Training Audiences** — role definitions and risk profiles106 - **Module Catalog** — per-audience training modules with objectives107 - **Training Cadence** — schedule and frequency per audience108 - **Completion Tracking** — metrics, targets, and escalation procedures109 - **Assessment Framework** — question design, passing thresholds, and remediation110 - **Delivery Plan** — formats, tools, and effectiveness measurement111112## Output113114The security training program written to `.singularskills/security/<project>/security-training.md`. Present a summary to the user highlighting:115- Training audiences and their specific module focus116- Key modules per role with learning objectives117- Training cadence and compliance targets118- Assessment approach and effectiveness measurement119120End the artifact with this paragraph, verbatim:121122> **Not a penetration test or audit.** This artifact is generated analysis; validate findings against the live system and have material controls reviewed by a qualified security professional.