Works with the AI Agents you already use
Cloud Security Configuration Drift Investigator
- **TLS/SSL Review** audits protocol versions, cipher suites, and certificate alignment from provided reports.
$34.90
Cloud Security Configuration Drift Investigator
Example session with this skill installed
Audit these HTTP response headers for production:
HTTP/1.1 200 OK
Server: nginx/1.18.0
Content-Type: text/html
X-Frame-Options: SAMEORIGIN
Set-Cookie: sessionid=xyz123; Path=/; HttpOnly
- Read your context and instructions
- Compiled the cloud security configuration
The assessment of the provided HTTP headers is complete. I have identified three configuration weaknesses ranging from Low to Medium severity.
Website Security Configuration Audit
Assessment scope
- Website / domain: [User Specified]
- Environment: Production
- Evidence sources: HTTP Response Headers
- Baseline: Defensive Best Practices
Findings Overview
| ID | Finding | Severity | Confidence | Affected component | Status |
|---|---|---|---|---|---|
| SEC-01 | Missing HSTS Header | High | High | Transport Security | Open |
| SEC-02 | Missing Content Security Policy | Medium | High | Application Shell | Open |
| SEC-03 | Insecure Cookie Attribute | Medium | High | Session Management | Open |
| SEC-04 | Server Version Disclosure | Low | High | Information Discovery | Open |
Detailed Findings
SEC-01: Missing Strict-Transport-Security (HSTS)
- Severity: High | Confidence: High
- Observed: Header not present in response.
- Expected:
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload - Impact: Allows potential SSL stripping attacks and protocol downgrades.
- Remediation: Add the HSTS header to the Nginx configuration block.
- Verification: Run
curl -Iand verify header presence in production output.
SEC-03: Missing 'Secure' Attribute on Session Cookie
- Severity: Medium | Confidence: High
- Observed:
Set-Cookie: sessionid=xyz123; Path=/; HttpOnly - Expected: Cookie must include the
Secureflag for production environments. - Impact: Cookies may be transmitted over unencrypted connections if HTTPS is bypassed.
- Remediation: Update application session configuration to set
Secure: true.
Next steps
- Implement the
Strict-Transport-Securityheader in your Nginx configuration. - Update the session management logic to include the
Secureflag on all cookies. - Provide an updated header capture to verify these findings are resolved.
Connects securely to your tools. The creator never sees your data.
About this skill
Manual security audits are slow, inconsistent, and prone to oversight. This skill automates the analysis of website configuration evidence to identify hardening gaps and prioritize risks without intrusive scanning.
What it does
- Header Analysis evaluates CSP, HSTS, CORS, and other security headers for misconfigurations.
- TLS/SSL Review audits protocol versions, cipher suites, and certificate alignment from provided reports.
- Identity & Session Audit checks cookie attributes like Secure, HttpOnly, and SameSite for exposure risks.
- DNS Hygiene identifies missing SPF/DMARC records or potential dangling DNS entries.
- Platform Hardening flags verbose error reporting, default pages, and version disclosure in server configs.
- Remediation Planning generates prioritized action plans with specific verification steps for developers.
How it works
- Define Scope by providing the authorized domain, environment, and assessment objectives.
- Input Evidence by uploading sanitized HTTP headers, Nginx/Apache configs, or scan outputs.
- Analyze Controls against established security baselines or defensive best practices.
- Review Report including severity ratings, confidence levels, and technical remediation steps.
Frameworks & tools
Works with evidence from Nginx, Apache, WordPress, and cloud platforms. Analyzes outputs from TLS scanners, dependency inventories, and standard web server configuration files.
Why this beats prompting it yourself
Generic prompts often miss the nuance of compensating controls or fail to separate severity from confidence. This skill uses a structured methodology to ensure evidence is traced to specific findings while redacting sensitive data.
Use cases
- Auditing HTTP response headers before a production release.
- Hardening Nginx or Apache configuration files against best practices.
- Reviewing third-party TLS reports to prioritize infrastructure updates.
- Generating a post-remediation verification checklist for QA teams.
Known limitations
Does not perform live scanning or exploitation. Requires sanitized configuration evidence provided by the user. Cannot automate the deployment of fixes.
Requires user-provided configuration evidence. No independent web scanning or exploitation. Cannot modify production settings. Results depend on evidence freshness.
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
Permissions
No special permissions declared or detected