Insecure Defaults

What it does

This skill helps identify and remediate common insecure default configurations in software. It analyzes system settings, file permissions, and network configurations to highlight potential vulnerabilities arising from defaults that are not secure by design. The goal is to improve the security posture of systems by proactively addressing these weaknesses.

When to use it

• Security Audits: During a security assessment of a new or existing application or infrastructure.
• DevSecOps Pipelines: Integrate into CI/CD pipelines to automatically check for insecure defaults during deployment.
• Onboarding New Systems: When deploying new servers, containers, or applications to ensure secure initial configurations.
• Compliance Checks: To verify adherence to security best practices and compliance standards that address default settings.

Key capabilities

• Identification of common insecure default configurations.
• Reporting on potential vulnerabilities arising from defaults.
• Provides remediation suggestions for identified issues.

Example prompts

• "Check this server's configuration for insecure defaults."
• "Analyze the file permissions in /var/www and report any insecure default settings."
• "Review the network configuration of this container for common insecure default configurations."

Tips & gotchas

The effectiveness of this skill depends on having access to relevant system configuration files and data. It's best used with a clear understanding of the target environment’s architecture and security requirements.