misconfig

Detects security misconfigurations in application and infrastructure files using scanners and Grep fallback.

12|1|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/florianbuetow/claude-code --skill misconfig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: misconfig
Source: https://github.com/florianbuetow/claude-code/tree/main/plugins/appsec/skills/misconfig
Command: npx skills add https://github.com/florianbuetow/claude-code --skill misconfig

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill identifies and helps remediate security misconfigurations in your application and infrastructure, preventing common vulnerabilities like exposed debug modes, weak CORS policies, and missing security headers.

Core Features & Use Cases

  • Automated Auditing: Scans configuration files (IaC, app configs, server configs) for security weaknesses.
  • Vulnerability Detection: Identifies issues like debug modes enabled in production, overly permissive CORS, default credentials, and missing security headers.
  • Use Case: Before deploying your new microservice, run this Skill to ensure its configuration files don't expose sensitive information or allow unauthorized access.

Quick Start

Use the misconfig skill to check for security misconfigurations in the current project's configuration files.

Frequently Asked Questions about misconfig

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

FAQPage Schema
How do I scan infrastructure configurations for security misconfigurations?

To scan for security misconfigurations, analyze application and infrastructure files like YAML, JSON, TOML, and Dockerfiles to detect enabled debug modes, insecure headers, permissive CORS, and default credentials mapped to OWASP A05.

How does IaC misconfiguration detection map to OWASP A05?

IaC misconfiguration detection maps to OWASP A05 by scanning infrastructure manifests for enabled debug modes, weak CORS policies, default credentials, and missing security headers across various configuration file types.

Does this security scanner integrate with Checkov, TFsec, and Semgrep?

Yes, this security scanner integrates with tools like Checkov, TFsec, KICS, Trivy, and Semgrep, automatically falling back to Grep-based detection when these external scanners are unavailable.

Can I detect default credentials and permissive CORS in JSON and YAML files?

Yes, you can detect default credentials and permissive CORS by analyzing configuration files in formats including JSON, YAML, TOML, INI, properties, env files, Dockerfiles, and IaC manifests.

What happens when a scanner like Trivy or KICS is unavailable during an audit?

When a scanner like Trivy or KICS is unavailable, the auditing process automatically falls back to Grep-based detection to identify security misconfigurations in your configuration files.

What are common security misconfigurations found in Dockerfiles and env files?

Common security misconfigurations in Dockerfiles and env files include enabled debug modes in production, overly permissive CORS settings, default credentials, verbose error handling, and missing security headers.