Automate Vulnerability Lifecycle Management | PlexTrac

0:21
Detecting issues isn’t the problem.

0:23
Security teams are flooded with findings from scanners, pin tests, and other offensive testing.

0:28
The real challenge is acting on that data.

0:31
Without a centralized way to manage and respond, workflows become fragmented and results are siloed across disconnected tools, leading to inconsistency in prioritization, unclear ownership, and ultimately allowing critical threats to linger longer than they should.

0:46
A centralized data management approach is necessary to ensure automated, dynamic, actionable finding delivery, and mature remediation workflows, and also enable consistent processes across platforms.

1:00
So that teams can respond quickly, confidently, and at scale.

1:04
Let’s dive into how Plextrack can help.

1:06
Plextrack automates and transforms how findings are delivered.

1:10
The platform acts as a data control center for all of your automated tools, manual testing, and routing all findings through one consistent workflow.

1:19
Depending on the tools used, scanned results, AKA findings may be scored different by different methodologies because no tool scores or looks at findings the same way.

1:28
This can pose a problem for organizations when trying to prioritize their risk for remediation efforts.

1:36
Plex track’s risk scoring feature solves this issue by allowing you to build contextual scoring equations that leverage finding an asset criteria that is most important to the business.

1:46
Once set up, all findings are scored utilizing your business aware scoring methodology.

1:52
Give you a clearer picture of what should be prioritized first.

1:55
With our workflow automation engine, findings can be shared in action dynamically as they are discovered, not just at the end of an engagement, empowering teams to act immediately instead of waiting for testers to push those findings manually.

2:09
Within workflow automation, we can leverage report level findings as triggered events setting criteria against them to hone in on when we want the system to take actions.

2:17
From there we can identify what those actions should be.

2:22
Let’s take a look at some.

2:25
In this example, I’m having the system essentially close all informational findings for me automatically.

2:34
Here I’ve set the system to look for any findings with the severity of informational.

2:39
I’m only focusing on published reports and I’m having the system as an action change the status of those findings to closed as informational and then I’m also sending out a web hook to say, hey, these have been closed.

2:54
This webook in this case is going to slack, but it could also go to Teams or other webhook type of tool.

3:01
Another option I have, and this gets in more into setting up for our remediation, is I can have the system look for specific findings, maybe that their severity is critical, they are published.

3:16
I had also set it to look for different things like specific tagging on my findings, and then I’m going to have the system.

3:25
Proceed with several actions.

3:27
The first being set it to open needs immediate triage because this is critical.

3:32
I’m having it assigned to a specific user immediately and I’m also having the system create a specific jury ticket for me for that direct client profile, the appropriate project, and the appropriate issue type here.

3:46
So this is all happening automatically via the system.

3:50
I’m also gonna be sending out an email.

3:52
, I can also do this with other avenues and options.

3:56
Thanks for watching today.

3:58
As you saw, Plex helps you act faster and reduce risk by centralizing data and streamlining your workflows, laying a foundation for faster and more efficient remediation and data management.