Vulnerabilities¶

Manage and track security vulnerabilities discovered during testing.

Overview¶

The Vulnerabilities section provides a centralized view of all security issues discovered across your attack surface.

Accessing Vulnerabilities¶

Navigate to Intelligence → Vulnerabilities
View all discovered vulnerabilities
Filter by severity, status, or asset
Sort and search as needed

📸 Screenshot: Vulnerabilities list

Vulnerability Attributes¶

Basic Information¶

Every Vulnerability Has: - Title: Descriptive name - Severity: Critical, High, Medium, Low - CVSS Score: 0.0-10.0 - Status: New, Assigned, In Progress, Remediated, Verified, Closed - Affected Assets: Which assets are vulnerable - Discovery Date: When found - Last Updated: Most recent change

Detailed Information¶

Additional Details: - Description: What the vulnerability is - Impact: Potential consequences - Remediation: How to fix it - References: CVE, CWE, links - Evidence: Screenshots, output - Notes: User comments

Severity Levels¶

CVSS Scoring¶

Severity Ranges: - Critical: 9.0-10.0 - Immediate action required - High: 7.0-8.9 - Priority remediation - Medium: 4.0-6.9 - Standard remediation - Low: 0.1-3.9 - Backlog

CVSS Factors: - Attack Vector - Attack Complexity - Privileges Required - User Interaction - Scope - Confidentiality Impact - Integrity Impact - Availability Impact

Vulnerability Lifecycle¶

States¶

graph LR
    A[New] --> B[Assigned]
    B --> C[In Progress]
    C --> D[Remediated]
    D --> E[Verified]
    E --> F[Closed]
    E --> C

State Descriptions: - New: Just discovered - Assigned: Owner assigned - In Progress: Being fixed - Remediated: Fix applied - Verified: Fix confirmed - Closed: Complete

Managing States¶

Update Status: 1. Open vulnerability 2. Click Change Status 3. Select new status 4. Add notes 5. Save

Filtering and Searching¶

Quick Filters¶

By Severity: - Critical only - High and above - Medium and above - All severities

By Status: - Open (New, Assigned, In Progress) - Remediated - Verified - Closed

By Asset: - Specific asset - Asset type - Engagement

Advanced Filters¶

Filter Builder:

Severity = "Critical" AND Status = "New"
Asset Type = "Site" AND CVSS > 7.0
Discovery Date > "2024-01-01" AND Status != "Closed"

Vulnerability Details¶

Viewing Details¶

Detail Sections: - Overview: Summary information - Technical Details: In-depth analysis - Affected Assets: List of vulnerable assets - Remediation: Fix instructions - Evidence: Proof of vulnerability - History: Change log - Comments: Team discussion

Adding Evidence¶

Evidence Types: - Screenshots - Tool output - HTTP requests/responses - Proof of concept code - Video recordings

Add Evidence: 1. Open vulnerability 2. Click Add Evidence 3. Upload files or paste text 4. Add description 5. Save

Remediation¶

Assigning Vulnerabilities¶

Assignment Process: 1. Select vulnerability 2. Click Assign 3. Choose owner 4. Set due date 5. Set priority 6. Add notes 7. Save

Tracking Remediation¶

Remediation Workflow: 1. Vulnerability assigned 2. Owner acknowledges 3. Fix developed 4. Fix tested 5. Fix deployed 6. Verification requested 7. Fix verified 8. Vulnerability closed

Remediation Guidance¶

For Each Vulnerability: - Recommended Fix: Best solution - Workaround: Temporary mitigation - References: Additional resources - Estimated Effort: Time to fix

Reporting¶

Vulnerability Reports¶

Generate Reports: 1. Go to Intelligence → Reporting Engine 2. Select Vulnerability Report 3. Configure options 4. Generate

Report Types: - Executive Summary - Technical Details - Remediation Status - Trend Analysis

Metrics¶

Key Metrics: - Total vulnerabilities - By severity - Mean time to detect (MTTD) - Mean time to remediate (MTTR) - Remediation rate - Vulnerability age

Integration¶

Ticketing Systems¶

Create Tickets: - Jira integration - ServiceNow integration - Custom webhooks

Sync Status: - Bi-directional sync - Status updates - Comments sync

SIEM Integration¶

Export to SIEM: - Splunk - ELK Stack - Custom SIEM

Data Format: - JSON - CEF - LEEF

Best Practices¶

✅ Validate Findings: Eliminate false positives
✅ Prioritize by Risk: Not just CVSS
✅ Track Diligently: Use the system
✅ Communicate Clearly: Keep stakeholders informed
✅ Verify Fixes: Always retest
✅ Document Everything: Evidence and decisions

Troubleshooting¶

Vulnerability Not Showing¶

Check: - Filters applied - Status (include closed?) - Permissions - Engagement selection

Duplicate Vulnerabilities¶

Causes: - Multiple scans - Different tools - Same issue, different assets

Solution: - Merge duplicates - Link related - Update deduplication rules

Related: Reporting Engine | Assets | Scan Executions