security-by-design

Embed security-by-design principles into software development before coding begins.

9|3|Updated Jun 4, 2022
One-click install
npx skills add https://github.com/Hack23/riksdagsmonitor --skill security-by-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-by-design
Source: https://github.com/Hack23/riksdagsmonitor/tree/main/.github/skills/security-by-design
Command: npx skills add https://github.com/Hack23/riksdagsmonitor --skill security-by-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security by design helps teams embed security from the outset, preventing insecure designs and costly retrofits.

Core Features & Use Cases

  • Secure by Default: Systems should be secure in their default configuration, default to HTTPS, least privilege, encrypted communications.
  • Defense in Depth: Multiple layers of protection spanning network, application, access control, data, and monitoring.
  • Least Privilege: Minimal permissions for users, processes, and services; scoped credentials; MFA.
  • Fail Securely: Failures do not leak data or weaken security; robust error handling and secure failure modes.
  • Don't Trust User Input: Validate and sanitize all external input; use parameterized queries and proper encoding.
  • Keep Security Simple: Rely on well-tested libraries; minimize surface area and dependencies.
  • Separation of Duties: Code reviews, separate dev/prod environments, audit trails.
  • Economy of Mechanism: Keep security mechanisms simple and leverage standard protocols.

Quick Start

Integrate security-by-design from project kickoff by defining threat models, enforcing secure defaults, and layering defenses across the stack.

Frequently Asked Questions about security-by-design

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

FAQPage Schema
What is security by design in software architecture?

Security by design embeds threat modeling, least privilege, and secure defaults into software architecture from project kickoff to prevent insecure designs before coding begins. It layers defenses across the stack to avoid costly retrofits.

How do I integrate threat modeling into my software development lifecycle?

Integrate threat modeling from project kickoff by documenting security requirements, enforcing code reviews, separating dev and prod environments, and applying defense in depth across network, application, and data layers.

How do I implement least privilege access across CI/CD pipelines?

Implement least privilege across CI/CD by scoping credentials, maintaining minimal permissions for users and services, enforcing audit trails, and ensuring separate environments with strict access controls and MFA.

Does security by design require specific platforms or frameworks to implement?

Security by design requires no specific platforms or frameworks; it relies on standard protocols, well-tested libraries, and secure configurations applied across your existing project planning, architecture, and deployment workflows.

What's the best way to ensure systems fail securely without leaking data?

Ensure systems fail securely by implementing robust error handling and secure failure modes that do not leak data or weaken security, keeping mechanisms simple and validating all external input.

When should I apply defense in depth layers in my application architecture?

Apply defense in depth during architecture planning by layering protection across network, application, access control, data, and monitoring domains to ensure multiple security barriers mitigate potential breaches.