Skip to main content
Dashboard view showing vulnerability groups like XSS and API Vulns

Vulnerability Groups — Manage categorized lists of vulnerabilities

Overview

Vulnerability Groups enable you to organize vulnerabilities from multiple assets, assessments, and sources into logical collections — such as all Access Control issues or API-related vulnerabilities.
This helps teams prioritize fixes, track themes, and export consolidated reports with ease.
Groups can be defined by vulnerability types, impacted components, responsible teams, or business context. They act as dynamic workspaces to simplify remediation management across large vulnerability datasets.

Use Cases

  • Group all Access Control or Authentication issues across multiple systems.
  • Maintain separate vulnerability lists per team or department.
  • Create category-based views (e.g., API Vulnerabilities, Web XSS Issues, Encryption Weaknesses).
  • Generate consolidated reports for specific vulnerability families.

Creating or Updating a Group

Dashboard view showing vulnerability groups like XSS and API Vulns

Vulnerability Groups — Manage categorized lists of vulnerabilities

1

Open Vulnerability Groups

Navigate to Vulnerability Management → Vulnerabilities → Groups.
2

Click ‘Create Group’

Provide a name (e.g., “XSS” or “API Vulnerabilities”) and an optional description to help categorize the group.
3

Save Group

Once saved, your new group will appear in the list, ready to be populated with vulnerabilities.
4

Updating a Group

To rename or edit a group’s description, click the three-dot menu (⋯) on the card and select Edit.
Menu options for editing, managing, or exporting vulnerability groups

Creating and managing vulnerability groups


Viewing Vulnerabilities in a Group

Dashboard view showing vulnerability groups like XSS and API Vulns

Vulnerability Groups — Manage categorized lists of vulnerabilities

1

Select a Group

Click on the group name or the ‘View’ link beside the vulnerability count.
2

Review Grouped Vulnerabilities

View all vulnerabilities added to that group, along with their severity, state, and associated assessments.
3

Drill Down

Click any vulnerability title to open its detailed view and remediation information.

Adding or Removing Vulnerabilities

Dashboard view showing vulnerability groups like XSS and API Vulns

Vulnerability Groups — Manage categorized lists of vulnerabilities

1

Manage Group

Open the group’s Manage option from the menu.
2

Add Vulnerabilities

Search across all vulnerabilities and select the ones you wish to add to the group.
3

Remove Vulnerabilities

To remove, deselect items or use the Remove button in the group management view.
4

Auto-Sync Option (optional)

Groups can be configured to automatically include vulnerabilities matching filters like CWE, severity, or keywords.

Exporting Group Data

Dashboard view showing vulnerability groups like XSS and API Vulns

Vulnerability Groups — Manage categorized lists of vulnerabilities

You can export grouped vulnerabilities either as a CSV file for analysis or as a PDF report for sharing and documentation.

Export CSV

1

Open the Group Menu

Click the three-dot (⋯) menu beside your chosen group.
2

Select ‘Export CSV’

A CSV file will be generated containing all vulnerabilities, including metadata such as title, severity, CVSS, asset, and owner.

Export PDF Report

1

Select ‘Export PDF’

Generate a detailed Consolidated Vulnerability Report with full details, affected assets, CVSS scores, and remediation steps.
2

Download the Report

The report will automatically compile and download, formatted for executive or audit-ready reviews.

CWE-Based Grouping

Vulnerability Groups support organizing findings using CWE (Common Weakness Enumeration) classifications.
This allows teams to group vulnerabilities based on root cause patterns, not just individual findings.
Vulnerability group filtered using CWE identifiers

Vulnerability Groups filtered by CWE categories

How CWE Grouping Helps

CWE-based grouping enables teams to:
  • Track recurring weakness classes (e.g., CWE-79, CWE-89, CWE-287) across applications
  • Identify systemic security flaws instead of isolated bugs
  • Prioritize remediation based on root causes, not just severity
  • Align remediation efforts with secure coding standards and training programs

Creating a CWE-Based Group

1

Create or Edit a Group

Open Vulnerability Groups and create a new group or edit an existing one.
2

Select CWE Criteria

Choose one or more CWE IDs (e.g., CWE-79: Cross-Site Scripting, CWE-287: Improper Authentication).
3

Save Group

All vulnerabilities mapped to the selected CWE identifiers are automatically included in the group.

Example CWE Use Cases

  • CWE-79 (XSS): Track all cross-site scripting issues across web applications
  • CWE-89 (SQL Injection): Monitor database-related injection risks
  • CWE-287 (Authentication): Review identity and access control weaknesses
  • CWE-22 (Path Traversal): Identify file system exposure risks
These groups help teams address patterns of weakness, not just individual vulnerabilities.

Reporting with CWE Context

When exporting a Vulnerability Group:
  • CSV exports include CWE IDs for each vulnerability
  • PDF reports summarize findings by CWE category, severity, and affected assets
This makes CWE-based groups ideal for:
  • Secure coding reviews
  • Engineering retrospectives
  • Compliance and audit reporting
  • Long-term risk reduction initiatives

Best Practices

  • Create functional groups (e.g., API Issues, Auth Flaws) to align with engineering teams.
  • Use CSV exports for bulk remediation tracking in external tools.
  • Use PDF exports for client reporting or audit documentation.
  • Review and refresh groups regularly to ensure updated vulnerability context.

Explore Live Demo

Explore Snapsec Live — No Signup Needed

Jump straight into the live environment and see how Snapsec unifies asset intelligence, threat detection, and vulnerability tracking — all in one dashboard.