
Change Management Dashboard showing request summary and vulnerability overview
Overview
The Change Management module allows organizations to securely track and assess changes introduced to their applications, infrastructure, or APIs.It ensures that every new release or feature undergoes a controlled security review before production deployment. Whether you are performing internal change reviews or managing external pentest requests, this module provides a unified process for security validation, approval tracking, and evidence management.
Purpose
Every code deployment or configuration update can impact the security posture.Change Management in Snapsec VM formalizes this process by:
- Documenting change requests with relevant context (title, owner, timeline, dependencies).
- Running targeted assessments on new or modified components.
- Tracking vulnerabilities introduced or fixed through each release.
- Maintaining traceability between changes, vulnerabilities, and pentest results.
Value
Security in Every Release
Ensure each release or feature update goes through defined security checks before deployment.
Centralized Request Tracking
Manage all change and pentest requests from a single interface with clear visibility on status and priority.
Evidence-based Validation
Attach supporting evidence, testing credentials, and API documentation for validation and audit.
Seamless Integration
Link Jira or CI/CD releases with security verification and vulnerability results.
Change Management Dashboard
The Dashboard provides an overview of all pentests and change requests along with key metrics.
Dashboard view summarizing requests and vulnerability distribution
Dashboard Highlights
- Requests by Status — Track running, paused, completed, or pending requests.
- Recent Activities — See recent submissions, updates, and completions.
- Vulnerability Overview — Visualize vulnerabilities associated with each change request, categorized by severity.
- Top Priority Requests — Quickly identify ongoing or urgent security validations.
Creating a Change Request
Creating a change request captures all necessary information for a release or update validation.1
Navigate to Change Management → Change Requests
Click Create New Request to open the change submission form.
2
Add Request Summary
Include priority level, title, requester details, contact information, and a concise summary of the change.
3
Set Timeline
Specify the request date, report deadline, and expected go-live window.
4
Add Technical Details
Provide environment details, URLs, authentication credentials, and link any API documentation or files.
5
Submit for Review
Click Create Request to trigger validation and assign reviewers.

Change Request creation form capturing summary and technical details
Viewing and Managing Change Requests
All existing requests are listed in the Change Requests tab, where you can view, search, and filter by state, priority, or update date. Each request includes linked vulnerabilities, associated evidence, and live metrics showing open/closed issues, severity breakdowns, and trends.
Change Request details with metrics and vulnerability insights
Adding Vulnerabilities to a Change Request
During or after validation, vulnerabilities identified are automatically linked to their associated Change Request.1
From the Assessment
Select vulnerabilities discovered during the pentest and map them to the related change request.
2
Auto Link via Integration
If connected with CI/CD or scanners, vulnerabilities are automatically assigned to their respective change ID.
3
Review and Track Progress
Track each vulnerability’s lifecycle under the Metrics tab within the change request.

Metrics showing severity distribution and vulnerability progress within a change request
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.