sethdford/claude-skills - Page 8

certificate-management

Manage digital certificates for HTTPS, mutual TLS, code signing, and infrastructure security.

cloud-security-posture

Assess and improve cloud infrastructure security posture through configuration review, access control, and compliance monitoring.

container-security-review

Review container security including image scanning, runtime policies, and supply chain integrity.

iam-policy-design

Design and implement least-privilege IAM policies for cloud and on-premise environments.

infrastructure-hardening

Harden infrastructure through patch management, service hardening, and secure baselines.

kubernetes-security

Secure Kubernetes clusters through RBAC, network policies, pod security, and runtime monitoring.

network-segmentation

Design and implement network segmentation to limit lateral movement and contain breaches.

zero-trust-architecture

Design and implement zero-trust architecture to authenticate and authorize all access, eliminating trust based on location.

authentication-design

Design secure authentication systems with strong password policies, MFA, secure password reset, and session management.

authorization-design

Design authorization systems (access control, role-based permissions, principle of least privilege) to enforce fine-grained access policies.

cryptography-selection

Select appropriate cryptographic algorithms and parameters for encryption, hashing, key derivation, and digital signatures.

input-validation-patterns

Design and implement input validation patterns (whitelisting, boundary checks, type validation) to prevent injection and buffer overflow attacks.

output-encoding

Implement context-specific output encoding to prevent XSS and injection attacks. Encode HTML, URL, JavaScript, and other contexts appropriately.

owasp-top-ten-check

Audit application architecture and code against OWASP Top 10 vulnerabilities. Use when assessing application security posture and prioritizing fixes.

secrets-management

Manage API keys, credentials, and secrets securely using vaults, environment variables, and rotation policies. Prevent secrets from being committed to code or exposed in logs.

secure-coding-review

Review code systematically for security vulnerabilities using OWASP Top 10, secure coding patterns, and static analysis best practices. Use when reviewing pull requests, conducting security code reviews, or implementing secure development practices.

session-management

Implement secure session handling with proper token generation, storage, expiry, CSRF protection, and session invalidation.

alert-triage

Triage security alerts to classify as true/false positives and prioritize investigation and response.

detection-engineering

Build detection engineering capabilities including threat modeling, detection hypothesis development, and hypothesis testing.

log-analysis-security

Analyze logs to investigate security incidents, identify attack patterns, and build detection rules.

security-monitoring-strategy

Develop comprehensive security monitoring strategy covering detection sources, alert tuning, and operational resilience.

siem-rule-design

Design SIEM (Security Information & Event Management) detection rules to identify suspicious activity and attacks.

threat-intelligence-integration

Integrate threat intelligence into security operations to proactively detect and hunt threats.

vulnerability-management-program

Establish vulnerability management program to identify, prioritize, remediate, and track vulnerabilities across infrastructure.

bug-bounty-program

Establish and manage bug bounty programs to leverage external researchers for vulnerability discovery.

red-team-exercise

Plan and execute red team exercises to test security controls and incident response capabilities.

secure-architecture-review

Review system architecture and design for security flaws, compliance gaps, and architectural improvements.

security-awareness-training

Develop and deliver security awareness training to build organizational security culture and reduce human risk.

security-champion-program

Establish security champion program to embed security expertise across teams and improve security culture.

security-documentation

Develop comprehensive security documentation including policies, procedures, architecture, and runbooks.

security-metrics-dashboard

Create security metrics dashboards to track program effectiveness, trends, and KPIs for leadership reporting.

abuse-case-design

Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.

asset-inventory

Create a comprehensive inventory of assets (data, systems, infrastructure, people) and their criticality, value, and dependencies. Use when prioritizing threats and allocating security resources.

attack-tree-modeling

Build hierarchical attack trees showing how attackers decompose goals into sub-goals and exploits. Use when analyzing attack paths, prioritizing security investments, or assessing attacker effort and cost.

data-flow-diagram-security

Create and analyze DFDs (Data Flow Diagrams) with security focus, identifying data flows across trust boundaries, storage, and processing points. Use when modeling system architecture for threat analysis.

risk-scoring

Quantify risk using likelihood and impact, apply severity ratings, and prioritize mitigations. Use when prioritizing threats, allocating security budget, and communicating risk to leadership.

stride-analysis

Systematically identify and document threats using the STRIDE framework (Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, Elevation of Privilege). Use when designing systems, reviewing architectures, conducting security design…

threat-identification

Systematically identify threats from threat libraries, historical CVEs, and attacker tactics. Use when augmenting STRIDE analysis with known threats from MITRE ATT&CK, CWE, or your industry.

threat-library

Build and maintain a reusable threat library tailored to your organization, platform, and threat landscape. Use when cataloging threats for future analyses, threat modeling sessions, and architecture reviews.

trust-boundary-analysis

Identify trust boundaries in system architecture where privilege levels, authority, or security contexts change. Use when designing authentication, authorization, and inter-component communication.