The use case involves a robust security tool. We conducted evaluations of numerous tools to enhance our security measures. This assessment extended beyond just the systems. We also considered Falco, their open-source version, and Sysdig Falco Platform. Notably, the Falco Platform is integrated into the Sysdig Secure product. The central theme here is security in the context of Sysdig Secure. This tool offers security solutions for various domains including containerized platforms, virtual machines, VDI setups, and safeguarding code repositories like GitHub and Bitbucket. Furthermore, the tool provides insights that stand out distinctly from other products available today. Despite using Microsoft Defender for our virtual machines, it doesn't match up to the comprehensive outcomes delivered by Sysdig Secure. The tool furnishes detailed reports on aspects such as Intrusive Communication, thread level, process level, network level, specific ports, ingress and egress traffic, etc. This comprehensive vantage point empowers vigilant monitoring of all activities within the environment.

Absolutely, it has proven to be highly advantageous, which justifies the investment despite the substantial cost of the software. The primary benefit lies in the in-depth insights it provides at a granular level. It begins from the initial deployment of workloads and extends to details like thread level and syscal level. This includes intricate information on the syscal events, the associated user, the process ID, the accessed ports, and the network level involved. What's noteworthy is that this level of insight isn't limited to real-time monitoring; historical data is also available. This allows for the examination of past events, such as the causes of downtime or failures.

Moreover, they offer a feature to enable data capture, known as "Sysdig capture." This captures data for a specified period before and after an event, typically five minutes. The captured data can then be analyzed. This includes a comprehensive view of file system activities, IO operations, network interactions, process behavior, thread actions, and more. This comprehensive data analysis aids in pinpointing the root causes of various issues. This aspect of their offering provides another significant advantage.

The tool has the capability to conduct scans initially. It can perform scans on your virtual machines, physical machines, containers, and container images. A standout feature is its ability to scan offline container images stored in your container registry. Additionally, it can scan runtime images in your cluster or on your host machine. This allows for the detection of vulnerabilities in running containers, including loaded libraries. Notably, the tool can identify which library vulnerabilities are already present in your system. An added advantage is its capacity to take action beyond threat detection. It has the ability to block access and respond to encountered threats.

There was a security concern related to a specific feature. While the feature itself was promising, it posed a challenge. The situation revolved around code scanning. If your source code is hosted within your own premises, say on Bitbucket, you naturally wouldn't want your code to be accessible to external parties beyond your company. Keeping your code base private is a standard practice.

However, in the case of code scanning using Sysdig Secure, they copy your code to their SaaS platform. This posed an issue for us. When we inquired about this, their response acknowledged the concern. In an upcoming release, they plan to enable code scanning within your on-premises environment through the assistance of an agent. This change is already in progress. While this tool stands out compared to existing solutions in the market, it's important to note that there are still some limitations to consider.

Another drawback we encountered relates to our expertise with Kubernetes. The tool can monitor Kubernetes audit logs, triggering alerts and notifications. However, it falls short in terms of taking direct action based on these alerts. There are different methods of event capture, including through system level and system calls, as well as via Kubernetes audit events. Notably, at the system level, Sysdig Secure can both detect and respond to events, allowing actions like blocking and warning. This proactive approach is effective at the system call level. However, when it comes to monitoring Kubernetes audit events, Sysdig Secure can only notify without being able to execute any further actions. It can't block access or containers. The vendor likened their role to that of a monitoring camera, observing events and sending notifications without the capacity to intervene. This limitation applies to Kubernetes audit events. Given that everything operates within our system, there is a workaround available: configuring system-level policies to block containers as necessary.

I have been using Sysdig Secure for two and a half months and our company is currently planning to purchase.

The product is quite stable.

The product scalability cannot be rated by me as I tried on few clusters and nodes only.

They were well aware of our potential purchase, so their responsiveness was quite high. Even though the initial free trial was for thirty days, they essentially extended it to an unlimited timeframe. I can still access it, and it's functioning well. The process was swift, and we engaged in several support calls during that period.

The process isn't straightforward, as it involves setting up multiple components and deploying around six or seven parts. Handling this on-premises can be quite cumbersome. I wouldn't describe it as extremely complex, but it does carry a level of complexity. It was a long process as the configuration involved various internal aspects such as firewalls and URL access. This process took approximately a week, considering the need to establish the necessary access due to our on-premises setup.

We were particularly interested in deploying the solution on-premises due to our internal requirements. We were hesitant about opting for the SaaS platform due to data transfer concerns. However, an issue we encountered was that the on-premises version has a delay of six months compared to their SaaS offering. To address this, they proposed an alternative solution. If we have an AWS environment or a similar setup on our on-premises infrastructure, they can assist us in hosting the solution there. This introduces a distinct deployment model with three options: on-premises, SaaS, and a hybrid model that leverages our existing AWS setup.

It was an in-house setup done by me by installing Sysdig secure agent on my Kubernetes cluster.

It is quite costly compared to other tools.

We evaluated Microsoft Defender and Suse NeuVector but they weren’t up to the mark.