Manage vulnerabilities
Analyze your supply chain security
Role required: User, Vulnerability Manager or User Manager The Inherited section is designed to give you visibility into the dependencies used across all active repositories in a group, helping you monitor the status of these dependencies, regarding ...
See where vulnerabilities are and more details
See the list of vulnerabilities detected Role required: User, Vulnerability Manager or User Manager The Injected section is the first one you see when accessing a group. It provides an overview of all types of vulnerabilities detected in your ...
Examine the evidence of exploitability
The Evidence section on Fluid Attacks' platform provides supporting proof of the existence of a type of vulnerability in your software and, if applicable, is where the hacking team shares how they exploit the security issue in question. To view ...
Request a vulnerability be dismissed as Zero Risk
Role required: User, Vulnerability Manager or User Manager Note: Zero Risk requests generated by members with the User role must be approved by a Vulnerability Manager or User Manager before they are considered by Fluid Attacks. Without this member's ...
See vulnerabilities assigned to you
The platform's To do section is where you keep track of all vulnerabilities whose remediation has been assigned to you as well as the types that have the highest priority scores across all the groups you are a part of, therefore benefitting ...
Assign treatments
A treatment represents the organizational decision that you make concerning your approach to a vulnerability. This page presents a guide on how to apply treatments to reported vulnerabilities on Fluid Attacks' platform. Define a treatment for a ...
Verify fixes with reattacks
Request a reattack Role required: User, Vulnerability Manager or User Manager Note: Before requesting a reattack, make sure you have synced the fixed software version to the platform. When you have fixed your code or service configuration to address ...