security-fundamentals

Apply defense-in-depth and least-privilege principles to software security challenges.

2|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/MysMon/Spec-Workflow-Toolkit --skill security-fundamentals-mysmon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-fundamentals
Source: https://github.com/MysMon/Spec-Workflow-Toolkit/tree/main/skills/core/security-fundamentals
Command: npx skills add https://github.com/MysMon/Spec-Workflow-Toolkit --skill security-fundamentals-mysmon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security vulnerabilities across projects can lead to data breaches, downtime, and loss of trust. This Skill provides a structured set of security fundamentals that teams can apply across architectures, code, and data handling to reduce risk.

Core Features & Use Cases

  • Defense in Depth: implement layered protections across network, infrastructure, application, and data.
  • Least Privilege: enforce minimal permissions, scoped access, and secure token handling.
  • Input Validation and Threat Modeling: validate inputs at all boundaries and perform threat modeling to prevent common vulnerabilities.

Quick Start

Audit your project against core security principles to reduce risk and harden defenses.

Frequently Asked Questions about security-fundamentals

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I apply defense-in-depth principles to secure my application architecture?

Defense-in-depth secures applications by implementing layered protections across network, infrastructure, application, and data boundaries. This structured approach reduces the risk of a single point of failure causing a data breach.

What is the best way to enforce least privilege and secure token handling?

Least privilege enforces minimal permissions and scoped access to protect sensitive operations. Secure token handling ensures authentication tokens are properly managed, limiting exposure if an access control failure occurs.

How do I perform threat modeling and OWASP risk assessment for my software?

Threat modeling identifies and evaluates potential vulnerabilities during software development. Applying OWASP risk assessment guidelines helps categorize and mitigate common security flaws like insufficient input validation.

Does input validation at trust boundaries prevent common web application vulnerabilities?

Input validation prevents common vulnerabilities by filtering and sanitizing all data entering application boundaries. Validating inputs against strict criteria stops malicious payloads from executing unauthorized application logic.

Can I use these security fundamentals for reviewing secure coding and incident logging?

These security fundamentals apply directly to secure coding reviews by evaluating fail-secure states and incident logging. Implementing incident logging guidelines ensures security events are properly recorded for post-breach analysis.

Why does my application need fail-secure mechanisms during error handling?

Fail-secure mechanisms ensure that when an application encounters an error, it defaults to a denied access state rather than an open one. This prevents accidental exposure of sensitive data during unexpected application failures.