The Vulnerabilities area is the central place to manage and act on findings in SpartanX. It sits below assets in the platform hierarchy and is designed to help teams move from discovery into remediation.
Use AI-powered playbooks for faster remediation
At the top of the vulnerabilities view, SpartanX offers targeted playbooks that help automate common follow-up tasks. One of the most powerful examples is the ability to analyze vulnerabilities and create automated fix pull requests in supported source code platforms.
Workflow step | What happens |
1 | Select the relevant collection and asset |
2 | Choose the target branch |
3 | Let SpartanX generate a code fix and raise a pull request |
4 | Have a developer review and approve the pull request |
This workflow is particularly effective for code-level vulnerabilities because it accelerates remediation without removing developer oversight. SpartanX does not merge code changes automatically, which keeps the final approval in human hands.
Understand the difference between code and configuration findings
Not every vulnerability should be treated the same way. A code vulnerability may be suitable for an automated pull request workflow, while a configuration issue, such as a firewall misconfiguration, requires a different type of response. SpartanX distinguishes between those cases so the remediation path fits the issue.
Take manual action on individual findings
If you prefer a more targeted approach, you can open a specific vulnerability and use the available actions directly.
Manual action | Purpose |
Generate pull request | Create a focused remediation change for developer review |
Create Jira ticket | Route the finding into the appropriate team workflow |
Route issues into Jira
For larger organizations, Jira integration is especially helpful. Findings can be turned into tickets and routed to the right team based on the type of issue, which reduces manual coordination and keeps remediation inside the tools teams already use.
Filter and search effectively
When you are working through a large number of findings, filtering becomes essential.
Filter option | Best used for |
Search by keyword | Finding issues related to a particular technology or area, such as APIs |
Filter by severity | Focusing on critical or high-priority findings first |
Filter by collection or asset | Limiting the view to a specific environment segment or target |
The vulnerabilities area is most effective when used as a triage workspace. Review what is most severe, identify what is actually exploitable, then route each finding into the right remediation path.