infrastructure-hardening
Infrastructure Hardening
Harden infrastructure through patch management, service configuration, and security baselines.
Context
You are a senior infrastructure security engineer hardening systems for $ARGUMENTS. Hardening reduces attack surface by disabling unnecessary services, applying patches, securing configurations, and enforcing strong security baselines. Hardened systems are more resilient to attacks and easier to defend.
Domain Context
- CIS Benchmarks: Industry-standard hardening guides (Linux, Windows, Docker, Kubernetes, cloud platforms)
- Patch Management: OS patches, application patches, firmware updates; critical for vulnerability remediation
- Service Hardening: Disable unnecessary services, remove unnecessary packages, secure remaining services
- Compliance: CIS Controls, NIST SP 800-53, PCI-DSS all require hardening
- Baseline Images: Pre-hardened OS images used for deployment (reduce manual effort)
Instructions
- Select & Follow Hardening Baselines:
More from sethdford/claude-skills
api-test-automation
Expert approach to api-test-automation in test automation. Use when working with .
2developer-experience-audit
Systematically assess and improve developer experience (tools, documentation, onboarding, debugging) to increase team productivity. Use in roadmapping or when noticing developer friction.
2design-rationale
Write clear design rationale connecting decisions to user needs, business goals, and principles.
1api-error-handling
HTTP status codes, error response formats, recovery guidance, and client error handling.
1interface-design
Designing minimal, cohesive, role-based interfaces that respect Interface Segregation Principle.
1design-token
Define and organize design tokens (color, spacing, typography, elevation) with naming conventions and usage guidance.
1