I really love the feature within Sweet Security platform that allows you to visualize the specific packages or functions that are being loaded to the memory and are actually being executed by the operational system. The fact that they know how to filter those really helps to reduce our time invested in the triage and also in the remediation and mitigation steps for which vulnerability. This is an amazing feature. It's not the main feature of the platform, but that's something I really love about it. Before we had Sweet Security, upon any type of detection of activity, we needed to conduct a lot of deep investigations in different platforms and in different logs until we could build the larger picture. Once we inserted Sweet Security in the runtime protection, we are able to actually see each and every request being made from the application level towards the infrastructure. For example, there might be an API that gets a request, then ingests it into the backend and the backend processes it. We were able to see an API request being made and the exact method that it was infiltrated into the infrastructure. Previously, we were not able to correlate between an application layer event to an infrastructure layer event, but with Sweet Security, it's much easier. It reduces the time for an analyst to understand what's really happening. Any suspicion of an incident or something similar will not be a standalone. It will be part of a chain where you can see what happens from the application layer, then what it caused within the infrastructure layer.
