Vulnerability Triage Process Training
Learn the systematic approach to triaging vulnerability reports in your disclosure program. Learn industry-standard processes for evaluation, prioritization, and response management.
Training Overview
This training covers the vulnerability triage lifecycle, from initial report receipt to resolution tracking. You'll learn standardized methodologies used by security teams.
Training Duration: 2-3 hours of focused learning with practical exercises and real-world scenarios.
Module 1: Triage Fundamentals
What is Vulnerability Triage?
Vulnerability triage is the systematic process of evaluating incoming security reports to determine their validity, severity, and priority for remediation. It involves technical assessment, risk evaluation, and resource allocation decisions.
Key Triage Objectives
- Validate reported vulnerabilities and eliminate false positives
- Assess potential impact and exploitability
- Prioritize remediation efforts based on risk
- Allocate appropriate resources for resolution
- Maintain clear communication with reporters
Triage Team Structure
Effective triage requires a multi-disciplinary team with defined roles and responsibilities:
Team Roles
- Triage Lead: Overall process management and final decisions
- Security Analyst: Technical validation and impact assessment
- Development Lead: Remediation feasibility and resource estimation
- Product Owner: Business impact evaluation and prioritization
- Communications Manager: Researcher and stakeholder communication
Module 2: Initial Assessment
Report Intake Process
The first 24-48 hours are critical for establishing effective communication and gathering initial information:
Initial Assessment Checklist
Scope Validation
Verify that the reported vulnerability falls within your program's defined scope:
Common Out-of-Scope Issues
- Third-party services not under your control
- Known issues already in remediation
- Issues requiring physical access
- Social engineering attacks
- Denial of service without actual impact
Module 3: Technical Validation
Reproduction Process
Systematic approach to validating reported vulnerabilities:
Validation Steps:
1. Environment Setup
• Use isolated testing environment
• Mirror production configuration
• Document test conditions
2. Reproduction Attempt
• Follow provided steps exactly
• Document each step and result
• Test variations and edge cases
3. Impact Verification
• Confirm claimed impact is achievable
• Test exploit scenarios
• Assess potential for escalation
4. Documentation
• Record successful reproduction
• Document failed attempts and reasons
• Capture evidence (screenshots, logs)
5. Validation Decision
• Confirmed: Vulnerability exists as described
• Partial: Vulnerability exists but impact differs
• Invalid: Cannot reproduce or not a vulnerability
Common Validation Challenges
- Environment Differences: Production vs. testing environment discrepancies
- Incomplete Information: Missing reproduction steps or context
- Timing Issues: Race conditions or timing-dependent vulnerabilities
- Configuration Specifics: Vulnerability exists only in specific configurations
Module 4: Risk Assessment and CVSS Scoring
CVSS 3.1 Scoring Framework
Use the Common Vulnerability Scoring System to assign standardized severity ratings:
Base Score Metrics
Exploitability Metrics
- Attack Vector (AV): Network, Adjacent, Local, Physical
- Attack Complexity (AC): Low, High
- Privileges Required (PR): None, Low, High
- User Interaction (UI): None, Required
Impact Metrics
- Confidentiality (C): None, Low, High
- Integrity (I): None, Low, High
- Availability (A): None, Low, High
- Scope (S): Unchanged, Changed
Severity Classification
Critical
CVSS: 9.0-10.0
Immediate response required
High
CVSS: 7.0-8.9
Priority remediation
Medium
CVSS: 4.0-6.9
Scheduled remediation
Low
CVSS: 0.1-3.9
Future release cycle
Business Impact Assessment
Consider additional factors beyond technical CVSS scoring:
- Data Sensitivity: Personal, financial, or regulated data exposure
- System Criticality: Core business functions or infrastructure
- Public Exposure: Internet-facing vs. internal systems
- Compliance Requirements: Regulatory or contractual obligations
- Exploit Availability: Public exploits or attack tools
Module 5: Prioritization and Resource Allocation
Priority Matrix
Use a systematic approach to prioritize vulnerabilities based on multiple factors:
| Priority Level | CVSS Score | Business Impact | Response Time |
|---|---|---|---|
| P0 - Emergency | 9.0+ Critical | High business impact | 4-24 hours |
| P1 - High | 7.0-8.9 High | Medium-high impact | 1-7 days |
| P2 - Medium | 4.0-6.9 Medium | Medium impact | 2-4 weeks |
| P3 - Low | 0.1-3.9 Low | Low impact | Next release cycle |
Resource Assignment
Match appropriate resources to vulnerability priority and complexity:
- Senior Developer: Critical and complex vulnerabilities
- Mid-level Developer: High-priority standard fixes
- Junior Developer: Low-complexity, well-defined issues
- Security Team: Validation and verification support
- Architecture Team: Design-level security issues
Module 6: Communication Management
Researcher Communication
Maintain clear, professional communication throughout the triage process:
Communication Templates
Initial Acknowledgment
Thank you for your security report. We have received your submission and assigned tracking ID #[ID]. Our team will review and respond within 48 hours.
Validation Complete
We have validated your report and confirmed the vulnerability. This issue has been classified as [Severity] and assigned to our development team for remediation.
Resolution Complete
The vulnerability you reported has been successfully remediated. We appreciate your responsible disclosure and contribution to our security.
Stakeholder Updates
Keep internal stakeholders informed of triage decisions and progress:
- Executive Dashboard: High-level metrics and critical issues
- Development Teams: Assigned vulnerabilities and timelines
- Security Team: Detailed triage decisions and technical analysis
- Compliance Team: Regulatory implications and requirements
Module 7: Tracking and Metrics
Key Performance Indicators
Response Metrics
- Time to initial acknowledgment
- Time to triage completion
- Time to resolution
- Researcher satisfaction scores
Quality Metrics
- Triage accuracy rate
- False positive rate
- Duplicate report rate
- Severity assessment accuracy
Reporting Dashboard
Maintain visibility into program performance with regular reporting:
Weekly Dashboard
- New reports received and triaged
- Critical and high-priority vulnerabilities
- Average triage and resolution times
- Overdue responses and escalations
- Top vulnerability categories
Practical Exercises
Exercise 1: SQL Injection Triage
Scenario
A researcher reports a SQL injection vulnerability in your user login form. They provide a proof-of-concept showing they can extract usernames and password hashes.
Your Task:
- Determine initial priority level
- Identify validation steps needed
- Calculate CVSS score
- Draft communication to researcher
Exercise 2: Cross-Site Scripting Assessment
Scenario
Report of stored XSS in user profile comments. The researcher shows they can execute JavaScript that steals session cookies of other users viewing the profile.
Your Task:
- Assess scope and impact
- Determine exploitation complexity
- Evaluate business risk
- Assign priority and resources
Advanced Topics
Zero-Day Management
Special considerations for novel vulnerabilities:
- Threat Intelligence: Check for active exploitation in the wild
- Vendor Coordination: Coordinate with third-party vendors if applicable
- Disclosure Timeline: Balance fix development with responsible disclosure
- Media Management: Prepare for potential public attention
Chained Vulnerabilities
Assess combinations of vulnerabilities that create higher impact:
- Evaluate cumulative risk of vulnerability chains
- Consider attack paths and privilege escalation
- Adjust CVSS scoring for combined impact
- Coordinate remediation across multiple teams
Continuous Improvement
Post-Incident Reviews
Learn from each vulnerability to improve your triage process:
Review Questions
- Was the initial severity assessment accurate?
- Did we miss any important impact considerations?
- Were resources allocated appropriately?
- What could we have done differently?
- How can we prevent similar issues in the future?
Training Updates
- Regular team training on new vulnerability types
- Updated CVSS guidelines and scoring examples
- Industry best practice sharing and benchmarking
- Tool training for triage automation and management
Training Complete
You now have the foundational knowledge to implement an effective vulnerability triage process. Practice with real scenarios and continuously refine your approach based on lessons learned.
Related Training Resources
Safe Harbor Policy Creation
Learn to create legal frameworks that protect both researchers and your organization.
View Guide →Security.txt Implementation
Implement RFC 9116 security.txt to make your security contacts discoverable.
Read Guide →