mcpField
D
defense-in-depth

defense-in-depth

github.com/dralgorhythmSecurity12875 installsUpdated 14w ago
Repository

About defense-in-depth

A security skill for teams applying defense in depth across perimeter, network, host, application, and data layers. It provides control examples and a checklist, including least-privilege guidance.

Key features

  1. 01Controls across five security layers
  2. 02Perimeter and network protections
  3. 03Host and application safeguards
  4. 04Data encryption and access logging
  5. 05Least-privilege guidance

Use cases

  1. 01Reviewing layered security coverage
  2. 02Building a security control checklist
  3. 03Scoping permissions for sensitive operations

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/dralgorhythm/claude-agentic-framework --skill defense-in-depth

After installing, type/defense-in-depthin Claude Code to confirm it loaded.

Details

From the project README

Defense in Depth

Security Layers

┌─────────────────────────────────┐
│         Perimeter Security       │  WAF, DDoS Protection
├─────────────────────────────────┤
│         Network Security         │  Firewalls, VPNs, Segmentation
├─────────────────────────────────┤
│         Host Security            │  OS Hardening, Patching
├─────────────────────────────────┤
│         Application Security     │  AuthN, AuthZ, Input Validation
├─────────────────────────────────┤
│         Data Security            │  Encryption, Access Control
└─────────────────────────────────┘

Layer Controls

1. Perimeter
  • Web Application Firewall (WAF)
  • DDoS protection
  • Rate limiting
  • Bot detection
2. Network
  • Network segmentation (VPCs, subnets)
  • Security groups / firewalls
  • VPN for internal access
  • Zero-trust network access
3. Host
  • OS hardening
  • Patch management
  • Endpoint protection
  • File integrity monitoring
4. Application
  • Authentication (OAuth2, OIDC)
  • Authorization (RBAC, ABAC)
  • Input validation
  • Output encoding
  • Session management
  • Secure headers
5. Data
  • Encryption at rest (AES-256)
  • Encryption in transit (TLS 1.3)
  • Key management
  • Data masking
  • Access logging

Security Checklist

  • WAF configured with OWASP rules
  • Network segmentation in place
  • All traffic encrypted (TLS)
  • Authentication on all endpoints
  • Least privilege access controls
  • Secrets managed securely
  • Audit logging enabled
  • Backups encrypted and tested

Principle of Least Privilege

Grant only the minimum permissions needed:

  • Use IAM roles, not long-lived credentials
  • Scope permissions to specific resources
  • Regular access reviews
  • Just-in-time access for sensitive operations

Comments

Markdown supported