What is our primary use case?
We connect this to our vulnerability scanner as input, our security tools to better determine risk, and our change management tool to provide risk-based vulnerabilities to the remediation teams.
We have three use cases:
1) What is the real Applicable Risk in our environment for new, risky vulnerabilities, especially Zero Day and CISA KEVs?
2) Do the security tools that we have in place today reduce the risk of those vulnerabilities such that we don't have to panic and patch?
3) When the patch remediation team submits an exception to delay patching a particular vulnerability on a particular system, when is the risk of accepting that exception?
How has it helped my organization?
We are able to see the real risk of a vulnerability on our environment with our security tools. We don't have to panic patch for high CVSS/EPSS scored vulnerabilities that are on system that are protected by our network and system security tools.
Overall, we can adjust the risk-based expectations to remediate vulnerabilities to the Applicable risk. This, in turn, will reduce the stress level of the patching teams because fewer vulnerabilities will be rated Critical or High which causes quicker expectations for patching.
I advise you to look at this if you want to improve your maturity in vulnerability management.
What is most valuable?
Integration with security tools to determine the real risk. This is one of the key differentiators: CVSS and EPSS are not always completely accurate for every organization. By connecting directly to these tools, Zafran is able to determine if a security tool alerts or blocks on exploits for an open vulnerability. If the system is protected with a block mode prevention capability in a security tool, the applicable risk is reduced. This can provide more measured and change-managed patching and remediation. We are continuing to add new integrations as we bring them into the company, including a Breach & Attack (BAS) tool. While you have options on what tools to integrate with, the more you integrate, the better it is to determine Applicable Risk.
What needs improvement?
Zafran is a new startup. Features are continuously being added or improved.
1) Continued integrations with existing (less popular) security tools. Not everyone is using the Gartner Magic Quadrant upper right corner security tools, so additional tools will continue to be onboarded as requested.
2) Bringing in anything considered a gap or weakness. This includes AppSec tools using CWEs and System Configuration tools based on CIS Benchmarks to further determine if an exploit is currently blocked or prevented across the entire vulnerability spectrum.
For how long have I used the solution?
What do I think about the stability of the solution?
How are customer service and support?
What about the implementation team?
No, worked direct with Zafran.