Overcoming a steep learning curve has improved dark web monitoring and proactive threat response
What is our primary use case?
Our main use case for KELA Cyber is that it provides us a very clean and task-oriented UI with its four main modules, helping us to focus on and see the attack surface from any kind of attacks that can commit cybercrime. It is basically a secure platform providing us with security measures for our organization, helping us to proactively monitor the dark web and cybercrime forums, including domains, brands, executives, credentials, and infrastructure assets. It also helps trigger an internal incident response when something fishy appears, making it a lifesaver for our organization by providing proper information if there is a problem, controlling and blocking threats, and monitoring the infrastructure threat actor's plan to exploit.
A specific time when KELA Cyber helped us catch a security issue was last year during a cyber threat attack on our organization. It provided a threat indicator and shared compromised IPs, domains, and hashes into the SIEM and SOAR tools and security controls. KELA Cyber helped us monitor the threat, produce reports, and examine the threat actor's plan, ultimately blocking the attack and triggering an internal incident response. This saved us a lot in resources and money, basically.
What is most valuable?
The best features KELA Cyber offers include continuous tracking of assets, helping us monitor domain brands across the dark web and crime resources with real-time targeted alerts when relevant information appears. It provides tools to research, pivot, and investigate threat actors, ensuring safe and anonymous use, along with multi-language coverage of underground sources. KELA Cyber also offers high-level dashboards with top trends, daily highlights, insights, and curated intel for decision-making in our organization. These are some top features I love about them.
The real-time targeted alerts from KELA Cyber are very important and crucial for system security as they allow us to respond quickly to any cyberattacks, preventing potential losses for the business and security. We have compliance and security teams available for monitoring, working multiple shifts, so that is why this is essential.
KELA Cyber has impacted our organization positively, particularly in pre-ransomware detection, helping us block networks and underground markets while allowing us to intervene. For example, it has enabled password resets, multi-factor authentication, and segmentation before ransomware affiliates could launch attacks. This has significantly saved us time and money, with a potential 27% time saved and 77% money saved as return on investment metrics.
What needs improvement?
I feel that the initial learning curve can be challenging for new users. Apart from that, we have not faced any significant issues with KELA Cyber; they are doing great, and their SaaS subscription model is acceptable.
The learning curve for onboarding to KELA Cyber could be improved by making the trainings and flows more user-friendly, allowing newcomers to learn the product easily. The learning and development team could work on this aspect to enhance the onboarding experience for new users; that is my observation.
For how long have I used the solution?
I have been working in my current field for more than 25 years now.
What do I think about the scalability of the solution?
KELA Cyber's scalability is truly good, allowing us to adjust seats as needed.
How are customer service and support?
KELA Cyber offered broader underground coverage and strong automation. The customer service is also excellent, providing good support whenever we need it. I would rate customer service as a 10 out of 10.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
We previously used Cyber Sixgill and Flashpoint before choosing KELA Cyber because KELA Cyber offered broader underground coverage and strong automation.
How was the initial setup?
The deployment of KELA Cyber in our environment was quite good, as it integrated easily via primary APIs into the SIEM and security controls using normalized machine-readable intel for blocking, alerting, and correlation. Initial setups were easy for our organization due to our security engineers team, and we did not experience significant challenges.
What about the implementation team?
My experience with the configuration process of KELA Cyber was quite good, involving defining monitored assets such as domains and brands while integrating feeds into existing security workflows. This process was straightforward, aided by support from KELA Cyber analysts, which contributed positively to our procurement and configuration experience.
What was our ROI?
The 27% time saved and 77% savings were calculated from data collected through our yearly reports. This reflects the time saved by securing our resources and preventing potential attacks, along with credential and data leak monitoring that helps us identify employee or customer credentials or internal documents for sale in dark web forums. This capability triggers resets and minimizes security incidents that could lead to legal matters.
What's my experience with pricing, setup cost, and licensing?
The setup cost and licensing for KELA Cyber are competitive compared to other solutions. It operates on a seat-per-basis handled through AWS, which suits our mid-enterprise needs well. The predictable and reasonable cost is a highlight for usability, and scalability is good.
The procurement process for KELA Cyber was good, with billing and licensing structured on a seat basis that we find fair. There were no issues with the metering and billing experience, and everything ran smoothly.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?