Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
vasilyu1983 avatar

Software Security Appsec

  • 207 installs
  • 73 repo stars
  • Updated July 13, 2026
  • vasilyu1983/ai-agents-public

software-security-appsec is an agent skill providing production-grade application security patterns aligned to OWASP Top 10:2025 and NIST SSDF for auth, input validation, and cryptography.

About

software-security-appsec is a Claude Code skill providing production-grade AppSec patterns aligned to OWASP Top 10:2025 and NIST SSDF. It covers authentication decisions (passkeys/WebAuthn, OAuth 2.1 + PKCE, JWT), input validation, parameterized queries, AES-256-GCM encryption, TLS 1.3, RBAC/ABAC, rate limiting, and secure SDLC gates like threat modeling and dependency scanning. Developers use it when implementing auth, handling untrusted input, working with cryptography, or reviewing security posture. Bundled references cover XSS, API security, cryptography standards, and incident response.

  • OWASP Top 10:2025 and NIST SSDF alignment
  • Auth decision matrix (passkeys, OAuth 2.1, JWT)
  • Reference library on XSS, crypto, and incident response

Software Security Appsec by the numbers

  • 207 all-time installs (skills.sh)
  • +2 installs in the week ending Jul 27, 2026 (Skillselion tracking)
  • Ranked #761 of 2,203 Security skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

software-security-appsec capabilities & compatibility

free, no API key

Capabilities
security audit · authentication · input validation · cryptography · threat modeling
Use cases
security audit · api development
Pricing
Free
From the docs

What software-security-appsec says it does

AppSec patterns aligned with OWASP Top 10:2025 and NIST SSDF.
SKILL.md
Production-grade security patterns for building secure applications in Jan 2026.
SKILL.md
npx skills add https://github.com/vasilyu1983/ai-agents-public --skill software-security-appsec

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs207
repo stars73
Last updatedJuly 13, 2026
Repositoryvasilyu1983/ai-agents-public

How do I implement auth, input validation, and cryptography that meets OWASP Top 10:2025 and NIST SSDF baselines?

security-audit

Who is it for?

Developers implementing or reviewing application security controls (auth, crypto, input handling) against modern standards.

Skip if: General backend development without a security focus, cloud/infra security, or smart-contract auditing as the primary focus.

When should I use this skill?

Implementing authentication or authorization, handling injection-prone input, working with cryptography, or conducting security reviews and threat modeling.

What you get

Security controls and reviews aligned to OWASP Top 10:2025 with concrete auth, crypto, and input-validation patterns.

  • Security controls following OWASP/NIST patterns
  • Security-posture review findings

By the numbers

  • OWASP Top 10:2025 checklist
  • 10-row security-task quick-reference table

Files

SKILL.mdMarkdownGitHub ↗

Software Security & AppSec — Quick Reference

Production-grade security patterns for building secure applications in Jan 2026. Covers OWASP Top 10:2025 (stable) https://owasp.org/Top10/2025/ plus OWASP API Security Top 10 (2023) https://owasp.org/API-Security/ and secure SDLC baselines (NIST SSDF) https://csrc.nist.gov/publications/detail/sp/800-218/final.

---

When to Use This Skill

Activate this skill when:

  • Implementing authentication or authorization systems
  • Handling user input that could lead to injection attacks (SQL, XSS, command injection)
  • Designing secure APIs or web applications
  • Working with cryptographic operations or sensitive data storage
  • Conducting security reviews, threat modeling, or vulnerability assessments
  • Responding to security incidents or compliance audit requirements
  • Building systems that must comply with OWASP, NIST, PCI DSS, GDPR, HIPAA, or SOC 2
  • Integrating third-party dependencies (supply chain security review)
  • Implementing zero trust architecture or modern cloud-native security patterns
  • Establishing or improving secure SDLC gates (threat modeling, SAST/DAST, dependency scanning)

When NOT to Use This Skill

  • General backend development without security focus → use software-backend
  • Infrastructure/cloud security (IAM, network security, container hardening) → use ops-devops-platform
  • Smart contract auditing as primary focus → use software-crypto-web3
  • ML model security (adversarial attacks, data poisoning) → use ai-mlops
  • Compliance-only questions without implementation → consult compliance team directly

---

Quick Reference Table

Security TaskTool/PatternImplementationWhen to Use
Primary AuthPasskeys/WebAuthnnavigator.credentials.create()New apps (2026+), phishing-resistant, broad platform support
Password Storagebcrypt/Argon2bcrypt.hash(password, 12)Legacy auth fallback (never store plaintext)
Input ValidationAllowlist regex/^[a-zA-Z0-9_]{3,20}$/All user input (SQL, XSS, command injection prevention)
SQL QueriesParameterized queriesdb.execute(query, [userId])All database operations (prevent SQL injection)
API AuthenticationOAuth 2.1 + PKCEoauth.authorize({ code_challenge })Third-party auth, API access (deprecates implicit flow)
Token AuthJWT (short-lived)jwt.sign(payload, secret, { expiresIn: '15m' })Stateless APIs (always validate, 15-30 min expiry)
Data EncryptionAES-256-GCMcrypto.createCipheriv('aes-256-gcm')Sensitive data at rest (PII, financial, health)
HTTPS/TLSTLS 1.3Force HTTPS redirectsAll production traffic (data in transit)
Access ControlRBAC/ABACrequireRole('admin', 'moderator')Resource authorization (APIs, admin panels)
Rate Limitingexpress-rate-limitlimiter({ windowMs: 15min, max: 100 })Public APIs, auth endpoints (DoS prevention)
Security RequirementsOWASP ASVSChoose L1/L2/L3Security requirements baseline + test scope

Authentication Decision Matrix (Jan 2026)

MethodUse CaseToken LifetimeSecurity LevelNotes
Passkeys/WebAuthnPrimary auth (2026+)N/A (cryptographic)HighestPhishing-resistant, broad platform support
OAuth 2.1 + PKCEThird-party auth5-15 min accessHighReplaces implicit flow, mandatory PKCE
Session cookiesTraditional web apps30 min - 4 hrsMedium-HighHttpOnly, Secure, SameSite=Strict
JWT statelessAPIs, microservices15-30 minMediumAlways validate signature, short expiry
API keysMachine-to-machineLong-livedLow-MediumRotate regularly, scope permissions

Jurisdiction notes (verify): Authentication assurance requirements vary by country, industry, and buyer. Prefer passkeys/FIDO2; treat SMS OTP as recovery-only/low assurance unless you can justify it.

OWASP Top 10:2025 Quick Checklist

#RiskKey ControlsTest
A01Broken Access ControlRBAC/ABAC, deny by default, CORS allowlistBOLA, BFLA, privilege escalation
A02Security MisconfigurationHarden defaults, disable unused features, error handlingDefault creds, stack traces, headers
A03Supply Chain Failures (NEW)SBOM, dependency scanning, SLSA, code signingOutdated deps, typosquatting, compromised packages
A04Cryptographic FailuresTLS 1.3, AES-256-GCM, key rotation, no MD5/SHA1Weak ciphers, exposed secrets, cert validation
A05InjectionParameterized queries, input validation, output encodingSQLi, XSS, command injection, LDAP injection
A06Insecure DesignThreat modeling, secure design patterns, abuse casesDesign flaws, missing controls, trust boundaries
A07Authentication FailuresMFA/passkeys, rate limiting, secure password storageCredential stuffing, brute force, session fixation
A08Integrity FailuresCode signing, CI/CD pipeline security, SRIUnsigned updates, pipeline poisoning, CDN tampering
A09Logging FailuresStructured JSON, SIEM integration, correlation IDsMissing logs, PII in logs, no alerting
A10Exceptional Conditions (NEW)Fail-safe defaults, complete error recovery, input validationError handling gaps, fail-open, resource exhaustion

Decision Tree: Security Implementation

Security requirement: [Feature Type]
    ├─ User Authentication?
    │   ├─ Session-based? → Cookie sessions + CSRF tokens
    │   ├─ Token-based? → JWT with refresh tokens (references/authentication-authorization.md)
    │   └─ Third-party? → OAuth2/OIDC integration
    │
    ├─ User Input?
    │   ├─ Database query? → Parameterized queries (NEVER string concatenation)
    │   ├─ HTML output? → DOMPurify sanitization + CSP headers
    │   ├─ File upload? → Content validation, size limits, virus scanning
    │   └─ API parameters? → Allowlist validation (references/input-validation.md)
    │
    ├─ Sensitive Data?
    │   ├─ Passwords? → bcrypt/Argon2 (cost factor 12+)
    │   ├─ PII/financial? → AES-256-GCM encryption + key rotation
    │   ├─ API keys/tokens? → Environment variables + secrets manager
    │   └─ In transit? → TLS 1.3 only
    │
    ├─ Access Control?
    │   ├─ Simple roles? → RBAC (assets/web-application/template-authorization.md)
    │   ├─ Complex rules? → ABAC with policy engine
    │   └─ Relationship-based? → ReBAC (owner, collaborator, viewer)
    │
    └─ API Security?
        ├─ Public API? → Rate limiting + API keys
        ├─ CORS needed? → Strict origin allowlist (never *)
        └─ Headers? → Helmet.js (CSP, HSTS, X-Frame-Options)

---

Security ROI & Business Value (Jan 2026)

Security investment justification and compliance-driven revenue. Full framework: references/security-business-value.md

Quick Breach Cost Reference

Indicative figures (source: IBM Cost of a Data Breach 2024; refresh for current year): https://www.ibm.com/reports/data-breach

MetricGlobal AvgUS AvgImpact
Avg breach cost$4.88M$9.36MBudget justification baseline
Cost per record$165$194Data classification priority
Detection time204 days191 daysSIEM/monitoring ROI
DevSecOps adoption-$1.68M-34%Shift-left justification
IR team-$2.26M-46%Highest ROI control

Compliance → Enterprise Sales

CertificationDeals UnlockedSales Impact
SOC 2 Type II$100K+ enterpriseTypically reduces security questionnaire friction
ISO 27001$250K+ EU enterprisePreferred vendor status
HIPAAHealthcare verticalMarket access
FedRAMP$1M+ governmentUS gov market entry

ROI Formula (Quick Reference)

Security ROI = (Risk Reduction - Investment) / Investment × 100

Risk Reduction = Breach Probability × Avg Cost × Control Effectiveness
Example: 15% × $4.88M × 46% = $337K/year risk reduction

---

Incident Response Patterns (Jan 2026)

Security Incident Playbook

PhaseActions
DetectAlert fires, user report, automated scan
ContainIsolate affected systems, revoke compromised credentials
InvestigateCollect logs, determine scope, identify root cause
RemediatePatch vulnerability, rotate secrets, update defenses
RecoverRestore services, verify fixes, update monitoring
LearnPost-mortem, update playbooks, share lessons

Security Logging Requirements

What to LogFormatRetention
Authentication eventsJSON with correlation ID90 days minimum
Authorization failuresJSON with user context90 days minimum
Data access (sensitive)JSON with resource ID1 year minimum
Security scan resultsSARIF format1 year minimum

Do:

  • Include correlation IDs across services
  • Log to SIEM (Splunk, Datadog, ELK)
  • Mask PII in logs

Avoid:

  • Logging passwords, tokens, or keys
  • Unstructured log formats
  • Missing timestamps or context

Common Security Mistakes

FAIL Bad PracticePASS Correct ApproachRisk
query = "SELECT * FROM users WHERE id=" + userIddb.execute("SELECT * FROM users WHERE id=?", [userId])SQL injection
Storing passwords in plaintext or MD5bcrypt.hash(password, 12) or Argon2Credential theft
res.send(userInput) without encodingres.send(DOMPurify.sanitize(userInput))XSS
Hardcoded API keys in source codeEnvironment variables + secrets managerSecret exposure
Access-Control-Allow-Origin: *Explicit origin allowlistCORS bypass
JWT with no expirationexpiresIn: '15m' + refresh tokensToken hijacking
Generic error messages to logsStructured JSON with correlation IDsDebugging blind spots
SMS OTP as primary factorPasskeys/WebAuthn or TOTP (keep SMS for recovery-only)Credential phishing

---

Optional: AI/Automation Extensions

Note: Security considerations for AI systems. Skip if not building AI features.
LLM Security Patterns
ThreatMitigation
Prompt injectionInput validation, output filtering, sandboxed execution
Data exfiltrationOutput scanning, PII detection
Model theftAPI rate limiting, watermarking
JailbreakingConstitutional AI, guardrails
AI-Assisted Security Tools
ToolUse Case
SemgrepStatic analysis with AI rules
Snyk CodeAI-powered vulnerability detection
GitHub CodeQLSemantic code analysis

---

.NET/EF Core Crypto Integration Security

For C#/.NET crypto/fintech services using Entity Framework Core, see:

  • references/dotnet-efcore-crypto-security.md — Security rules and C# patterns

Key rules summary:

  • No secrets in code — use configuration/environment variables
  • No sensitive data in logs (tokens, keys, PII)
  • Use decimal for financial values, never double/float
  • EF Core or parameterized queries only — no dynamic SQL
  • Generic error messages to users, detailed logging server-side

Navigation

Core Resources (Updated 2024-2026)

Security Business Value & ROI
  • references/security-business-value.md — Breach cost modeling, security ROI formulas, compliance → enterprise sales, investment justification templates
2025 Updates & Modern Architecture
  • references/supply-chain-security.md — Dependency, build, and artifact integrity (SLSA, provenance, signing)
  • references/zero-trust-architecture.md — NIST SP 800-207, service identity, policy-based access
  • references/owasp-top-10.md — OWASP Top 10:2025 (final) guide + 2021→2025 diffs
  • references/advanced-xss-techniques.md — 2024-2025 XSS: mutation XSS, polyglots, SVG attacks, context-aware encoding
API Security, Incident Response & Threat Modeling
  • references/api-security-patterns.md — OWASP API Security Top 10, BOLA/BFLA, rate limiting, API keys, GraphQL/gRPC security
  • references/incident-response-playbook.md — IR team roles, severity triage, containment by incident type, evidence handling, communication templates, postmortem
  • references/threat-modeling-guide.md — STRIDE, PASTA, data flow diagrams, attack trees, risk scoring (CVSS/DREAD), lightweight agile threat modeling
Foundation Security Patterns
  • references/secure-design-principles.md — Defense in depth, least privilege, secure defaults
  • references/authentication-authorization.md — AuthN/AuthZ flows, OAuth 2.1, JWT best practices, RBAC/ABAC
  • references/input-validation.md — Allowlist validation, SQL injection, XSS, CSRF prevention, file upload security
  • references/cryptography-standards.md — AES-256-GCM, Argon2, TLS 1.3, key management
  • references/common-vulnerabilities.md — Path traversal, command injection, deserialization, SSRF
External References
  • data/sources.json — 70+ curated security resources (OWASP 2025, supply chain, zero trust, API security, compliance)
  • Shared checklists: ../software-clean-code-standard/assets/checklists/secure-code-review-checklist.md, ../software-clean-code-standard/assets/checklists/backend-api-review-checklist.md

Templates by Domain

Web Application Security
  • assets/web-application/template-authentication.md — Secure authentication flows (JWT, OAuth2, sessions, MFA)
  • assets/web-application/template-authorization.md — RBAC/ABAC/ReBAC policy patterns
API Security
  • assets/api/template-secure-api.md — Secure API gateway, rate limiting, CORS, security headers
Cloud-Native Security
  • assets/cloud-native/crypto-security.md — Cryptography usage, key management, HSM integration
Blockchain & Web3 Security
  • references/smart-contract-security-auditing.mdNEW: Smart contract auditing, vulnerability patterns, formal verification, Solidity security

Related Skills

Security Ecosystem
  • ../software-backend/SKILL.md — API implementation patterns and error handling
  • ../software-architecture-design/SKILL.md — Secure system decomposition and dependency design
  • ../ops-devops-platform/SKILL.md — DevSecOps pipelines, secrets management, infrastructure hardening
  • ../software-crypto-web3/SKILL.md — Smart contract security, blockchain vulnerabilities, DeFi patterns
  • ../qa-testing-strategy/SKILL.md — Security testing, SAST/DAST integration, penetration testing
AI/LLM Security
  • ../ai-llm/SKILL.md — LLM security patterns including prompt injection prevention
  • ../ai-mlops/SKILL.md — ML model security, adversarial attacks, privacy-preserving ML
Quality & Resilience
  • ../qa-resilience/SKILL.md — Resilience, safeguards, failure handling, chaos engineering
  • ../qa-refactoring/SKILL.md — Security-focused refactoring patterns

---

Trend Awareness Protocol

IMPORTANT: When users ask recommendation questions about application security, you MUST use WebSearch to check current trends before answering. If WebSearch is unavailable, use data/sources.json + web browsing and state what you verified vs assumed.

Trigger Conditions

  • "What's the best approach for [authentication/authorization]?"
  • "What should I use for [secrets/encryption/API security]?"
  • "What's the latest in application security?"
  • "Current best practices for [OWASP/zero trust/supply chain]?"
  • "Is [security approach] still recommended in 2026?"
  • "What are the latest security vulnerabilities?"
  • "Best auth solution for [use case]?"

Required Searches

1. Search: "application security best practices 2026" 2. Search: "OWASP Top 10 2025 2026" 3. Search: "[authentication/authorization] trends 2026" 4. Search: "supply chain security 2026"

What to Report

After searching, provide:

  • Current landscape: What security approaches are standard NOW
  • Emerging threats: New vulnerabilities or attack vectors
  • Deprecated/declining: Approaches that are no longer secure
  • Recommendation: Based on fresh data and current advisories

Example Topics (verify with fresh search)

  • OWASP Top 10 updates
  • Passkeys and passwordless authentication
  • AI security concerns (prompt injection, model poisoning)
  • Supply chain security (SBOMs, dependency scanning)
  • Zero trust architecture implementation
  • API security (BOLA, broken auth)

---

Pre-Implementation Security Gate

Before building any feature that involves storage, uploads, or user-generated content:

1. Threat model first: Identify what an attacker could do with this feature (file upload → malware, storage → data exfiltration, user content → XSS). 2. Check OWASP mapping: Map the feature to relevant OWASP Top 10 categories above. 3. Define constraints before coding: Set file type allowlist, size limits, storage isolation, and access controls before writing the first line. 4. Review existing security patterns: Check if the project already has upload/storage security utilities to reuse.

Building storage/upload features without upfront security constraints leads to retroactive hardening that is more expensive and error-prone.

Operational Playbooks

  • references/operational-playbook.md — Core security principles, OWASP summaries, authentication patterns, and detailed code examples

Fact-Checking

  • Use web search/web fetch to verify current external facts, versions, pricing, deadlines, regulations, or platform behavior before final answers.
  • Prefer primary sources; report source links and dates for volatile information.
  • If web access is unavailable, state the limitation and mark guidance as unverified.

Related skills

FAQ

Which standards does it align to?

OWASP Top 10:2025, OWASP API Security Top 10 (2023), and the NIST SSDF secure SDLC baseline.

What auth method does it recommend first?

Passkeys/WebAuthn as primary auth for new apps in 2026, with OAuth 2.1 + PKCE and short-lived JWTs as alternatives.

Securityappsecauditcompliance

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.