cybersecurity-principles

Explains cybersecurity foundations, design principles, frameworks, and modern IAM standards.

1|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/TheViziusGroup/vibe-engineering-skills --skill cybersecurity-principles-theviziusgroup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cybersecurity-principles
Source: https://github.com/TheViziusGroup/vibe-engineering-skills/tree/main/plugins/security-principles/skills/cybersecurity-principles
Command: npx skills add https://github.com/TheViziusGroup/vibe-engineering-skills --skill cybersecurity-principles-theviziusgroup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security decisions are often made without grounding in first principles, leading to misconfigured controls, framework confusion, and repeated architectural mistakes. This Skill provides a structured mental model of cybersecurity fundamentals so you can explain why controls exist, evaluate trade-offs, and map principles to modern threats. ## Core Features & Use Cases - Foundational Principles: Covers the Saltzer-Schroeder eight design principles, CIA triad, AAA model, Zero Trust architecture, and defense in depth with real breach case studies (Target, SolarWinds, OPM). - Framework Guidance: Details NIST CSF 2.0, CIS Controls v8.1, ISO 27001:2022, NIST SP 800-63-4, and incident response per NIST SP 800-61 Rev 3, including which framework fits which audience. - Modern IAM & AI-Era Security: Explains phishing-resistant MFA (FIDO2/passkeys), PAM with zero standing privileges, SASE platforms, and maps classic principles to agentic AI risks like prompt injection and non-human identity sprawl. - Use Case: When an engineer asks "why do we need phishing-resistant MFA instead of SMS codes," the Skill explains origin binding, prompt bombing statistics from the Verizon DBIR, and NIST AAL3 requirements. ## Quick Start Ask the assistant to explain why a specific security control exists or which framework to use for a given scenario, such as "why is least privilege important for service accounts."

Frequently Asked Questions about cybersecurity-principles

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

FAQPage Schema
What are the Saltzer-Schroeder security design principles?

The Saltzer-Schroeder principles are eight design rules from 1975: least privilege, fail-safe defaults, open design, separation of privilege, complete mediation, economy of mechanism, least common mechanism, and psychological acceptability. NIST SP 800-160 later expanded them into 33 security engineering principles.

How do I choose between NIST CSF 2.0 and CIS Controls?

NIST CSF 2.0 is the lingua franca for board-level communication, with its Govern function covering risk strategy and supply chain. CIS Controls v8.1 is more prescriptive and the better operational starting point for hands-on hardening via its Implementation Groups.

What is phishing-resistant MFA and why does it matter?

Phishing-resistant MFA uses FIDO2/WebAuthn or PKI with origin binding, so the authenticator cryptographically refuses spoofed domains. SMS, OTP, and push notifications are phishable, and prompt bombing appeared in 14% of incidents per the Verizon 2025 DBIR.

Does Zero Trust mean buying a specific security product?

No, Zero Trust is an architecture and philosophy, not a product. Formalized in NIST SP 800-207, it combines least privilege, complete mediation, and fail-safe defaults so access is per-session, dynamically determined, and never based on network location.

How do classic security principles apply to AI agents?

Least privilege applied to non-human identities is the highest-leverage principle, since agents need scoped, just-in-time credentials. Complete mediation means validating every tool call in a deterministic layer outside the LLM, because system prompts are not a security control.