スキル一覧に戻る
vasilyu1983

software-security-appsec

by vasilyu1983

25🍴 6📅 2026年1月23日
GitHubで見るManusで実行

SKILL.md


name: software-security-appsec description: Modern application security patterns aligned with OWASP Top 10:2025 (final), OWASP API Security Top 10 (2023), NIST SSDF, zero trust (incl. NSA ZIGs 2026), supply chain security (SBOM), passkeys/WebAuthn, authentication, authorization, input validation, cryptography, plus security ROI, breach cost modeling, and compliance-driven enterprise sales.

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)

Quick Reference Table

Security TaskTool/PatternImplementationWhen to Use
Primary AuthPasskeys/WebAuthnnavigator.credentials.create()New apps (2026+), phishing-resistant, 70% adoption
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)

Authentication Decision Matrix (Jan 2026)

MethodUse CaseToken LifetimeSecurity LevelNotes
Passkeys/WebAuthnPrimary auth (2026+)N/A (cryptographic)HighestPhishing-resistant, 70% user adoption
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

2026 Regulatory Mandates for Passwordless:

  • UAE: March 31, 2026 (SMS OTP deprecated)
  • India: April 1, 2026 (SMS OTP deprecated)
  • EU: Digital Identity Wallet by end of 2026

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

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+ enterprise65% faster security review
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 (Dec 2025)

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

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:

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

Core Resources (Updated 2024-2026)

Security Business Value & ROI

2025 Updates & Modern Architecture

Foundation Security Patterns

External References

Templates by Domain

Web Application Security

API Security

Cloud-Native Security

Blockchain & Web3 Security

Security Ecosystem

AI/LLM Security

Quality & Resilience


Trend Awareness Protocol

IMPORTANT: When users ask recommendation questions about application security, you MUST use WebSearch to check current trends before answering.

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
  • 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)

Operational Playbooks

スコア

総合スコア

60/100

リポジトリの品質指標に基づく評価

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

0/10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

0/5

レビュー

💬

レビュー機能は近日公開予定です