Secure Software Engineering

Use when designing or implementing software securely: define security requirements, threat-model a feature, choose secure defaults, design authentication and authorization, handle untrusted data and secrets, evaluate dependencies, or review security-sensitive changes. Use for prevention during requirements, design, implementation, and review; not for post-build security assessments or scanning an existing codebase.

theheavenlyd3mon Updated 60 repo stars

File contents

theheavenlyd3mon/hermes-profiles commit 69db531af1

Frequently asked questions

npx get-skill add theheavenlyd3mon/secure-software-engineering