security-testing

Execute structured red-team security tests on Kubernetes homelab clusters.

Updated Sep 18, 2025
One-click install
npx skills add https://github.com/david-driscoll/home-operations --skill security-testing-david-driscoll
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-testing
Source: https://github.com/david-driscoll/home-operations/tree/main/.agents/skills/security-testing
Command: npx skills add https://github.com/david-driscoll/home-operations --skill security-testing-david-driscoll

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you run structured adversarial testing in a Kubernetes homelab to validate whether network policy, gateway protection, authentication, authorization, container hardening, and supply chain controls actually hold up under realistic attack patterns.

Core Features & Use Cases

  • Adversarial, phase-based testing: Executes a repeatable sequence across network policy enforcement, authentication/WAF behavior, privilege escalation paths, data exfiltration channels, and supply chain weak points.
  • Homelab-specific attack surface validation: Targets documented weaknesses (e.g., label-impersonation, DNS baseline behavior, WAF fail-open risks, gateway routing bypass, crown-jewel credentials, and OCI/Flux promotion paths) using the repo’s references and commands.
  • Operational safety via explicit scope and cleanup: Restricts active mutation to the Dev cluster (integration/live read-only per CLAUDE.md) and requires post-test cleanup of routes/pods/namespace labels to avoid lingering test artifacts.

Quick Start

Use the security-testing Skill to run a phase-focused dev-cluster security test session and generate the required findings and cleanup steps for a controlled red-team validation.

Frequently Asked Questions about security-testing

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

FAQPage Schema
How do I test Kubernetes network policy enforcement for cross-namespace isolation?▼

You can test Kubernetes network policy enforcement for cross-namespace isolation by executing a structured red-team methodology that probes label-impersonation and baseline DNS behavior to validate cluster-wide traffic restrictions.

What is the best way to verify WAF fail-open behavior in a Kubernetes cluster?▼

The best way to verify WAF fail-open behavior in a Kubernetes cluster is to run adversarial gateway routing bypass tests against your dev-cluster, ensuring your gateway protections hold up under realistic attack patterns.

How do I assess RBAC and service-account exposure during Kubernetes red teaming?▼

To assess RBAC and service-account exposure during Kubernetes red teaming, probe authentication and authorization layers to identify privilege escalation paths and exposed crown-jewel credentials within your active testing scenarios.

Can I use this approach to probe OCI and Flux auto-deploy attack paths?▼

Yes, you can probe OCI and Flux auto-deploy attack paths by targeting supply chain weak points during the security validation phases to identify potential container escape and unauthorized promotion vulnerabilities.

Do I need to restrict active security mutation testing to specific Kubernetes clusters?▼

Yes, you must restrict active security mutation testing to the Dev cluster only, keeping integration and live environments read-only while strictly following the authorized scope and performing post-test cleanup of routes and pods.

What cleanup steps are required after testing container escape and data exfiltration paths?▼

After testing container escape and data exfiltration paths, you must perform post-test cleanup of routes, pods, and namespace labels to remove lingering test artifacts and ensure the dev-cluster returns to its original state.