Works with the AI Agents you already use
Website Security Misconfiguration Detector
Identifies web server misconfigurations and risky HTTP headers with evidence-based remediation plans.
$39.99
Website Security Misconfiguration Detector
Example session with this skill installed
Review these Nginx headers for our staging site: Server: nginx/1.18.0, X-Frame-Options: SAMEORIGIN, Set-Cookie: sessionid=123; Path=/; HttpOnly. Is this secure?
- Read your context and instructions
- Compiled the website security misconfiguration
I have reviewed the provided HTTP headers for your staging environment. The configuration shows some basic protections but leaves several high-priority vectors open.
Website Security Configuration Review
Executive Summary
The server is leaking version information and lacks modern browser-side security headers. While session cookies use the HttpOnly flag, they are vulnerable to interception and cross-site requests.
Findings
| ID | Title | Severity | Status | Evidence |
|---|---|---|---|---|
| SEC-01 | Missing Secure Attribute | High | Observed | Set-Cookie: sessionid=123; Path=/; HttpOnly |
| SEC-02 | Server Version Leak | Low | Observed | Server: nginx/1.18.0 |
| SEC-03 | Missing CSP | Medium | Observed | No Content-Security-Policy header found |
Detailed Findings
SEC-01: Missing Secure Attribute on Session Cookie
- Risk: Cookies sent without the
Secureflag can be intercepted over unencrypted connections.
Remediation: Update the Nginx or application config to include the Secure and SameSite=Lax (or Strict) attributes.
- Verification: Inspect headers in a browser dev tool to ensure the
Secureflag is present.
SEC-02: Server Version Disclosure
- Risk: Revealing specific version numbers helps attackers target known vulnerabilities for that build.
- Remediation: Add
server_tokens off;to your Nginxhttporserverblock. - Rollback: Simply remove the directive or set it to
onif legacy debugging is required.
Positive Controls Observed
X-Frame-Options: SAMEORIGINis correctly implemented to prevent basic clickjacking.HttpOnlyflag is present, mitigating basic XSS-based cookie theft.
Prioritized Action Plan
- Immediate: Add the
Secureflag to session cookies. - Short-term: Disable
server_tokensand implement a baseContent-Security-Policy. - Follow-up: Review TLS protocol versions to ensure TLS 1.0/1.1 are disabled.
Next steps
- Provide your Nginx
.conffile (redacted) for a deeper review of directory permissions. - Apply
server_tokens off;in your staging environment and reload Nginx. - Test the application UI after adding a CSP to ensure no legitimate scripts are blocked.
Connects securely to your tools. The creator never sees your data.
About this skill
Default configurations and unhardened web servers are low-hanging fruit for attackers. This skill reviews your configuration files, manifests, and HTTP headers to identify risky settings before they are exploited.
What it does
- Transport Analysis evaluates HTTPS enforcement, HSTS rollout, and TLS protocol policies.
- Header Auditing checks for missing or misconfigured Content-Security-Policy, CORS, and frame protections.
- Session Review inspects cookie attributes like Secure, HttpOnly, and SameSite for exposure.
- Access Control identifies public admin interfaces, directory listing, and default server pages.
- Secrets Detection scans for exposed environment files, backups, and source maps in the config.
- Remediation Planning provides vendor-specific secure settings with rollback instructions.
How it works
- Supply Evidence by providing redacted configuration snippets, HTTP header dumps, or deployment manifests.
- Define Scope to classify provided data as observed, inferred, or unknown to prevent false positives.
- Execute Review across domains including caching, DNS, file handling, and server defaults.
- Receive Report containing prioritized findings, evidence-backed risks, and staged remediation steps.
Frameworks & tools
Works with Nginx, Apache, IIS, and Cloudflare configurations. Supports review of security headers, TLS summaries, and framework-specific manifests for Node.js, Python, or PHP environments.
Why this beats prompting it yourself
Generic prompts often hallucinate vulnerabilities or miss compensating controls. This skill follows a structured workflow that distinguishes observed facts from assumptions, ensuring every finding is mapped to specific lines in your configuration with a verifiable remediation path.
Use cases
- Auditing Nginx or Apache configuration files before a production deployment.
- Reviewing HTTP response headers for a new web application to ensure basic hardening.
- Validating CORS and cookie policies for a staging environment handling sensitive data.
- Identifying exposed management endpoints or debug modes left on by mistake.
Known limitations
Does not perform active penetration testing or intrusive probing. Requires manual redaction of secrets by the user before sharing files.
Requires user-redacted configs. No active exploitation or intrusive probing. Limited to provided evidence; cannot verify settings not in the supplied snippets.
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 any payment.
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 10 days ago