- Home
- Skills
- DevOps & Cloud
- Security Config Review
Works with the AI Agents you already use
Security Config Review
Review the runtime configuration that actually governs security behavior in production
$16
Security Config Review
Example session with this skill installed
Review this synthetic application's production security configuration. Inspect environment separation, CORS, CSP and security headers, cookie settings, debug exposure, Docker configuration, infrastructure as code, and security sensitive feature flags. Do not modify any files or assume the repository matches a live production environment.
- Read your context and instructions
- Compiled the security config review
Illustrative synthetic demo. It demonstrates the expected review structure. No production deployment, cloud account, live container, external service, or credential was accessed.
Security Configuration Review Record
SCOPE
Synthetic web application containing production configuration, reverse proxy settings, container configuration, and infrastructure as code.
Finding SCR-01
Area
CORS policy
Synthetic observation
The illustrative production configuration allows credentials while accepting an unrestricted origin pattern.
Expected property
Credentialed browser requests should be limited to explicitly trusted origins.
Assessment
SUPPORTED IN SYNTHETIC EXAMPLE
Recommended control
Replace the permissive origin policy with an explicit allowlist derived from the intended production origins.
Finding SCR-02
Area
Session cookie configuration
Synthetic observation
The example session cookie is marked HttpOnly but does not establish Secure in the supplied production configuration.
Assessment
CONFIGURATION DEFECT SUPPORTED IN SYNTHETIC EXAMPLE
Recommended control
Require the cookie to be transmitted only over secure transport in the production configuration.
Finding SCR-03
Area
Debug exposure
Synthetic observation
A diagnostic endpoint is controlled by a feature flag whose production default is enabled in the supplied example.
Risk
Development or diagnostic information may remain exposed when the production deployment uses the provided default.
Recommended control
Use a production safe default and require explicit nonproduction activation.
Finding SCR-04
Area
Container configuration
Synthetic observation
The example container definition does not specify a nonroot runtime user.
Assessment
HARDENING GAP IN SYNTHETIC EXAMPLE
Whether the effective runtime executes as root cannot be proven without runtime evidence.
Runtime Evidence Boundary
The supplied repository configuration was reviewed.
No deployed environment was queried.
No cloud account was accessed.
No container was executed.
No environment variable value was retrieved.
Therefore, the exact live production state remains UNVERIFIED.
Priority Summary
- Restrict credentialed CORS to trusted origins.
- Enforce the production session cookie security property.
- Disable diagnostic exposure by default.
- Verify the effective container identity in the deployed runtime.
Next Step
Route confirmed configuration defects to remediation planning before implementation. Use focused security testing when runtime verification of the resulting controls is required.
Connects securely to your tools. The creator never sees your data.
About this skill
Reviews the runtime and deployment configuration that determines how an application actually behaves outside its source code. It focuses on security relevant defaults, environment separation, browser security controls, containers, cloud configuration, infrastructure as code, administrative exposure, and dangerous feature flags.
What it does
- Reviews environment specific security configuration.
- Checks whether development and production settings are properly separated.
- Reviews CORS policy and allowed origins.
- Reviews Content Security Policy and related browser security headers.
- Examines cookie security attributes and session related configuration.
- Identifies debug, diagnostics, development, and administrative surfaces that may be exposed unintentionally.
- Reviews container and cloud security defaults represented in the supplied configuration.
- Inspects infrastructure as code for security relevant settings.
- Reviews dangerous feature flags and insecure runtime toggles.
- Distinguishes configuration evidence from assumptions about the deployed environment.
How it works
- Configuration inventory identifies environment files, deployment settings, proxy configuration, container definitions, infrastructure as code, and runtime security controls.
- Environment review checks whether development, test, staging, and production behaviors are sufficiently separated.
- Browser boundary review evaluates CORS, CSP, security headers, and cookie attributes where those controls are present.
- Exposure review examines debug interfaces, diagnostics, administrative endpoints, and permissive runtime options.
- Infrastructure review inspects container, cloud, and infrastructure as code settings available in the project context.
- Feature control review checks whether security sensitive behavior can be weakened through unsafe flags or defaults.
- Findings record the configuration evidence, expected security property, impact, and recommended next workflow.
Boundaries
This is a read only configuration security review.
Application code vulnerabilities belong to secure-code-review.
Sensitive data, secret lifecycle, key handling, and cryptographic design belong to data-secrets-crypto-review.
Dependency, build pipeline, CI token, provenance, and SBOM concerns belong to supply-chain-security.
Dynamic proof that a configured security control works belongs to security-testing.
The skill does not modify configuration, deploy infrastructure, change cloud resources, rotate credentials, or claim that repository configuration proves the exact state of a live production environment.
Why this beats prompting it yourself
Generic security reviews often concentrate on application code while the effective security posture is controlled by deployment configuration. A secure implementation can still ship with permissive CORS, insecure cookies, exposed debug functionality, weak headers, unsafe container defaults, or environment settings intended only for development. This skill reviews those operational controls as a distinct security boundary.
Validation
At pack level, JetFerrari Security Engineering passed 58/58 routing integrity checks with zero unresolved cases.
This skill is also covered by pack level structural, installation, discovery, and behavioral validation. No unsupported individual runtime qualification is claimed here.
Use cases
- Review production and development environment separation.
- Audit CORS, CSP, HTTP security headers, and cookie settings.
- Detect debug or administrative exposure before release.
- Review Docker, container, and infrastructure configuration.
- Inspect infrastructure as code for insecure defaults.
- Review security sensitive feature flags and runtime toggles.
Known limitations
The review depends on the configuration, deployment files, infrastructure definitions, environment documentation, and project context available to the agent. Repository configuration may not reflect the exact state of a live environment, so deployed behavior that cannot be established from evidence remains UNVERIFIED. The skill does not modify configuration, deploy infrastructure, access cloud accounts, retrieve credentials, or independently prove runtime enforcement.
Part of JetFerrari Security Engineering.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.
The review depends on the configuration, deployment files, infrastructure definitions, environment documentation, and project context available to the agent. Repository configuration may not represent the exact state of a deployed environment, so runtime behavior that cannot be established from supplied evidence remains UNVERIFIED. The skill does not modify configuration, access cloud accounts, retrieve credentials or environment variable values, deploy infrastructure, or independently prove runtime enforcement.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 24 days ago
Permissions
Access is limited to configuration, deployment files, infrastructure as code, container definitions, and project context supplied for review. The skill may use local read only inspection commands. It does not modify configuration, access cloud accounts, retrieve environment variable values, change infrastructure, contact production systems, or deploy changes.