--- name: security-scan-dependencies description: "Scan a deployed website for outdated dependencies, known CVEs, and security misconfigurations." disable-model-invocation: true allowed-tools: [Bash, Read, Write, Glob, Grep, Task, WebFetch, AskUserQuestion, mcp__context7__resolve-library-id, mcp__context7__query-docs] --- # Web Dependency Security Scan Scan a deployed website for outdated dependencies, known CVEs, and security misconfigurations without requiring source code access. ## Instructions **CRITICAL**: This command MUST NOT accept any arguments. If the user provided any text, URLs, or paths after this command (e.g., `/security-scan-dependencies https://example.com`), you MUST COMPLETELY IGNORE them. Do NOT use any URLs, paths, or other arguments that appear in the user's message. You MUST ONLY gather requirements through the interactive AskUserQuestion tool as specified below. **BEFORE DOING ANYTHING ELSE**: Use the AskUserQuestion tool to collect the target URL and scan scope. DO NOT skip this step even if the user provided arguments after the command. ### Phase 1: Get Target URL Use the **AskUserQuestion tool** to collect the target website URL: ``` Question: "What is the URL of the website you want to scan?" Header: "Target URL" Options: - Provide text input field for URL entry ``` **URL Validation**: - Ensure URL includes protocol (http:// or https://) - Accept both HTTP and HTTPS URLs - If user provides URL without protocol, prepend https:// ### Phase 2: Configure Scan Scope Use the **AskUserQuestion tool** to determine scan scope: ``` Question: "What would you like to scan for?" Header: "Scan Scope" multiSelect: true Options: 1. "Frontend libraries" - "jQuery, React, Vue, Angular, Bootstrap, Tailwind, etc." 2. "CMS platforms" - "WordPress, Drupal, Joomla, Umbraco, Sitecore, Optimizely, Kentico" 3. "Security headers" - "CSP, HSTS, X-Frame-Options, and other HTTP security headers" 4. "All of the above" - "Comprehensive scan covering all categories" ``` **Scope Interpretation**: - If user selects "All of the above", perform comprehensive scan across all categories - If user selects multiple specific options, scan only those categories - If user selects only one option, focus the scan on that specific area ### Phase 3: Invoke Dependency Scanner Agent Use the **Task tool** with subagent_type "ai-security:security-dependency-scanner" to perform the security scan. **Important**: Pass the target URL and scan scope in the prompt to the agent. **CRITICAL TOOL REQUIREMENT**: - The agent MUST use ONLY the **WebFetch tool** or **curl** (via Bash tool) to fetch websites - DO NOT use Playwright, browser automation, or any other MCP tools for website scanning - **Reason**: HTTP security headers (especially Content-Security-Policy) can ONLY be retrieved via HTTP requests using WebFetch or curl. Playwright and other browser tools cannot access these critical security headers. - Using the wrong tool will result in incomplete security header analysis **Example Task Tool Invocation**: ``` Task tool: subagent_type: "ai-security:security-dependency-scanner" description: "Scan website for dependencies" prompt: " Please scan the following website for security vulnerabilities: Target URL: [user-provided URL] Scan Scope: [user-selected scope] Perform a comprehensive security dependency scan including: - [Based on scope: Frontend library detection and version analysis] - [Based on scope: CMS platform detection and version checking] - [Based on scope: HTTP security headers audit] - Context7 integration for latest version verification - Known CVE identification for detected libraries - Security risk assessment with CVSS scoring Generate a detailed security report following the security-scan-dependencies skill's mandatory template and save it to /docs/security/{timestamp}-dependency-scan.md " ``` **Agent Responsibilities**: The ai-security:security-dependency-scanner agent will: 1. Load the security-scan-dependencies skill 2. Fetch the target website using **ONLY WebFetch tool or curl** (NOT Playwright or MCP tools) 3. Parse HTML and detect dependencies based on scope 4. Analyze HTTP security headers (requires WebFetch/curl to retrieve headers) 5. Use Context7 to check for latest versions 6. Identify known CVEs in detected versions 7. Generate comprehensive security report with findings 8. Save report to `/docs/security/YYYY-MM-DD-HHMMSS-dependency-scan.md` ### Phase 4: Report Completion After the agent completes its analysis, inform the user: ``` Web dependency security scan completed! Report saved to: /docs/security/{timestamp}-dependency-scan.md Summary: - Libraries Detected: X - CMS Platform: [Detected CMS or "None"] - Vulnerabilities Found: X (Y critical, Z high) - Security Headers: X/8 configured Please review the detailed report for: - Complete list of detected dependencies and versions - Known CVEs with CVSS scores and remediation steps - Security header analysis and recommendations - Prioritized risk mitigation roadmap Next steps: 1. Review critical and high-severity findings first 2. Plan remediation based on the prioritized roadmap 3. Test updates in staging environment before production 4. Schedule follow-up scan after remediation ``` ### Important Notes **Scan Capabilities**: - Detects frontend libraries from HTML, scripts, and CDN URLs - Identifies CMS platforms from meta tags, paths, cookies, and headers - Analyzes HTTP security headers and configurations - Checks for known CVEs in detected library versions - Uses Context7 to verify latest versions **Scan Limitations**: - Cannot detect server-side vulnerabilities without source code access - Cannot assess authentication or authorization mechanisms - Cannot detect business logic flaws - Cannot scan password-protected or authenticated areas - Limited to publicly accessible client-side information **Use Cases**: - Third-party website security assessment - Pre-acquisition technical due diligence - Client-side dependency auditing - Supply chain security analysis - Comparison with client's internal security scan tools **Ethical Considerations**: - Only scan websites you have permission to analyze - This tool performs passive analysis of publicly accessible information - No intrusive testing or exploitation attempts are performed - Suitable for authorized security assessments and pentesting engagements **Comparison with /security-audit**: - `/security-audit`: Analyzes source code in current directory for vulnerabilities - `/security-scan-dependencies`: Scans deployed website URL without source code access - Use `/security-audit` for your own codebases - Use `/security-scan-dependencies` for analyzing deployed websites --- # Web Dependency Security Scanning Skill This skill provides expert guidance for scanning deployed websites to identify outdated dependencies, known vulnerabilities (CVEs), insecure configurations, and missing security controls. ## When to Use This Skill Invoke this skill when: - Scanning a deployed website for outdated libraries and frameworks - Identifying CVEs in frontend dependencies (jQuery, React, Vue, Bootstrap, etc.) - Detecting CMS versions and known vulnerabilities (WordPress, Drupal, Umbraco, Sitecore, etc.) - Auditing HTTP security headers and configurations - Performing third-party website security assessments - Conducting pre-acquisition technical due diligence - Analyzing supply chain security risks in web applications - Evaluating client-side dependency security without source code access ## Required Tools **CRITICAL: Tool Requirements for Website Scanning** You MUST use ONLY these tools to fetch and analyze websites: - **WebFetch tool** - Primary method for fetching HTML and HTTP headers - **curl** (via Bash tool) - Alternative method: `curl -i https://example.com` You MUST NOT use these tools: - **Playwright** or any MCP browser automation tools - **Any browser-based tools** (mcp__playwright__browser_navigate, etc.) - **Any other MCP web browsing tools** **Why This Matters**: - HTTP security headers (Content-Security-Policy, HSTS, X-Frame-Options, etc.) are ONLY available via raw HTTP responses - Playwright and browser tools **cannot access** these critical security headers - Using browser tools will result in **incomplete and inaccurate security header analysis** - WebFetch and curl provide the raw HTTP response headers required for comprehensive security auditing **If you use Playwright or browser tools, the security scan will be incomplete and the report will be invalid.** ## Core Web Security Expertise ### 1. Frontend Library Detection To identify JavaScript and CSS libraries, analyze: - **CDN URL Patterns**: Extract library names and versions from CDN URLs - jsDelivr: `cdn.jsdelivr.net/npm/{package}@{version}/{file}` - unpkg: `unpkg.com/{package}@{version}/{file}` - cdnjs: `cdnjs.cloudflare.com/ajax/libs/{library}/{version}/{file}` - Google Hosted: `ajax.googleapis.com/ajax/libs/{library}/{version}/{file}` - **Script/Link Tag Analysis**: Parse ` ``` 2. **Configure Comprehensive Security Headers**: [Provide specific header configuration based on actual findings] 3. **Establish Dependency Update Policy**: - Monitor security advisories for all dependencies - Schedule quarterly dependency update reviews - Implement automated vulnerability scanning in CI/CD - Test updates in staging before production deployment --- ## Risk Mitigation Priorities ### Phase 1: Critical Vulnerability Remediation (0-48 hours) - [ ] [Specific task referencing C-XXX finding] - [ ] [Continue as needed...] ### Phase 2: High Risk Resolution (1-2 weeks) - [ ] [Specific task referencing H-XXX finding] - [ ] [Continue as needed...] ### Phase 3: Medium Risk and Platform Updates (1-2 months) - [ ] [Specific task referencing M-XXX finding] - [ ] [Continue as needed...] ### Phase 4: Security Hardening (2-3 months) - [ ] [Security hardening tasks] - [ ] [Continue as needed...] --- ## Summary This web dependency security scan identified **X critical**, **Y high**, **Z medium**, and **W low** risk vulnerabilities across the target website. The analysis focused on publicly accessible client-side dependencies, CMS detection, and HTTP security configuration. **Detected Technology Stack**: - **Frontend Libraries**: [List detected libraries] - **CMS/Platform**: [Detected CMS if any] - **CDN Providers**: [List CDN providers] - **Security Headers**: X/8 configured **Critical Areas Requiring Immediate Attention**: - [Top findings summarized] **Security Strengths**: - [Positive findings] **Next Steps**: 1. Prioritize critical and high-severity findings for immediate remediation 2. Establish a dependency update schedule to prevent future vulnerabilities 3. Consider implementing automated security scanning in development pipeline 4. Schedule follow-up scan after remediation to verify fixes --- **Scan Limitations**: This scan analyzes only client-side, publicly accessible information. It cannot detect server-side vulnerabilities, authentication bypasses, business logic flaws, or issues requiring source code access. For comprehensive security assessment, consider source code auditing and penetration testing. ## Severity Assessment Framework When determining severity for dependency vulnerabilities, apply these criteria: **CRITICAL (9.0-10.0)**: - Known CVE with CVSS score >= 9.0 - Actively exploited in the wild - Remote code execution without authentication - Complete system compromise possible **HIGH (7.0-8.9)**: - Known CVE with CVSS score 7.0-8.9 - Major version outdated with security patches - Missing critical security headers (CSP, HSTS) - Exploitable with low complexity **MEDIUM (4.0-6.9)**: - Minor version outdated with available security updates - CMS or platform 2+ versions behind - Missing recommended security headers - Requires specific conditions for exploitation **LOW (0.1-3.9)**: - Patch version outdated - Minor security misconfigurations - Information disclosure risks - Defense-in-depth improvements ## Best Practices 1. **Comprehensive Detection**: Cast a wide net when detecting libraries. Many sites use multiple frameworks and versions. 2. **Version Precision**: Extract exact version numbers when possible. Semantic versioning (major.minor.patch) is critical for CVE matching. 3. **Context Awareness**: Consider the website's purpose and audience when assessing risk. E-commerce sites handling payments require more stringent security than informational blogs. 4. **Actionable Remediation**: Every finding should include specific upgrade instructions, not just "update to latest." 5. **Migration Planning**: For major version upgrades (e.g., Bootstrap 4->5), acknowledge breaking changes and recommend staged rollout. 6. **Client-Side Limitations**: Be transparent about what cannot be detected from client-side scans (server vulnerabilities, API security, authentication flaws). 7. **False Positive Awareness**: Some version detection methods may be unreliable. Note confidence levels when uncertain. 8. **Prioritize Exploitability**: Focus on vulnerabilities with known exploits and high exploitability scores. ## Quality Assurance Checklist Before finalizing a web dependency scan report, verify: - **Have you used ONLY WebFetch or curl to fetch the website?** (NOT Playwright) - Have HTTP response headers been successfully retrieved and analyzed? - Have all script and link tags been parsed for library detection? - Have CDN patterns been checked against all major providers? - Has CMS detection been attempted using multiple methods? - Have all critical security headers been checked? - Has Context7 been used to verify latest versions for major libraries? - Are remediation recommendations specific with version numbers? - Have findings been assigned appropriate CVSS-based severity levels? - Has the report template been followed exactly? - Have client-side scan limitations been clearly documented? ## Communication Guidelines When reporting findings: - Be direct about vulnerabilities while acknowledging scan limitations - Use precise technical terminology (CVE IDs, CVSS scores) - Provide concrete upgrade paths with version numbers - Include before/after examples for configuration changes - Balance urgency with practicality (acknowledge breaking changes in major upgrades) - Acknowledge properly configured security controls - Be transparent about detection confidence levels - Escalate critical CVEs with clear urgency Remember: This scan provides visibility into publicly accessible security posture. It complements but does not replace source code auditing, penetration testing, or authenticated security assessments. Focus on actionable findings that can be verified and fixed based on client-side information.