insecure-defaults

Detect insecure defaults by scanning configuration files and deployment templates to surface hardcoded secrets, weak authentication, and permissive security settings. This reveals fail-open patterns where applications run insecurely in production environments.

A fail-open security pattern occurs when apps default to insecure states, such as running without authentication if a configuration check fails. It impacts production by allowing hardcoded secrets and weak auth to create exploitable vulnerabilities.

Scan IaC templates by analyzing configuration flows and environment variable handling to identify hardcoded secrets and weak authentication. This surfaces permissive security defaults and distinguishes exploitable configurations from fail-secure patterns.

Yes, you can use this security audit approach for environment variable handling review. It analyzes environment variable configuration flows to detect fail-open insecure defaults and surfaces permissive security settings across your codebase.

Fail-open patterns allow apps to run insecurely with permissive defaults when checks fail, while fail-secure patterns block access. Security audits analyze code paths to differentiate exploitable fail-open defaults from fail-secure patterns.