La interfaz está localizada; las descripciones y documentos de las Skills se traducen automáticamente con IA a su idioma. El código, los comandos, rutas y términos técnicos se mantienen en el original, y prevalece el documento del autor.
Explorar Skills
Diseño y creatividad · SKILL.md

security-awareness

security-awareness

Design security awareness programs — training curriculum, phishing simulations, metrics, role-based content, and compliance. TRIGGER when: user says /security-awareness or asks about security training programs.

Independent GitHub snapshot · Automated classification · Original documentation governs

Documentación de la Skill

GitHub

name: security-awareness description: > Design security awareness programs — training curriculum, phishing simulations, metrics, role-based content, and compliance. TRIGGER when: user says /security-awareness or asks about security training programs. argument-hint: "[relevant context]" user-invocable: true

security awareness

Process

Step 1: Define Scope

Identify the boundaries of what to assess, who is involved, and what assets/processes are in scope.

Step 2: Identify Risks/Requirements

Risk/RequirementCategorySeverityLikelihood
[item][category]H/M/LH/M/L

Step 3: Assess Current Controls

ControlEffectivenessGap
[control]Strong/Adequate/Weak[description]

Step 4: Prioritize Actions

ActionImpactEffortPriority
[action]H/M/LH/M/LP1/P2/P3

Step 5: Develop Mitigation Plan

RiskMitigationOwnerTimeline
[risk][strategy][name][date]

Step 6: Monitor and Report

MetricTargetFrequency
[KRI/metric][threshold]Weekly/Monthly/Quarterly

Output Format

## security awareness: [Scope]
### Risk Summary: [Key findings]
### Controls: [Current state assessment]
### Recommendations: [Prioritized actions]
### Monitoring: [KRIs and reporting cadence]

Quality Checklist

  • Scope clearly defined
  • Risks identified systematically
  • Current controls assessed for effectiveness
  • Recommendations prioritized by risk level
  • Monitoring plan established
  • Stakeholders reviewed findings

Edge Cases

  • For rapidly changing environments, increase assessment frequency
  • If data is limited, use qualitative assessment with expert judgment
  • For cross-organizational risks, coordinate with all affected parties
  • Adjust methodology based on regulatory requirements
Skills guardadas