We employ SQL for vulnerability scanning, compliance scanning, security intrusion detection, and drift detection.

We appreciate this feature, especially when combined with CD monitoring. The implementation of requested features has been remarkable, such as scanning for compliance in CRM processes for the US government. We heavily rely on this feature to assess compliance with federal requirements.

Perhaps, it could support more custom implementations, as our company utilizes custom implementations rather than standard ones. Configuring it requires a deep understanding and adjustment to our specific needs, which took some time. Other than that, I'm unsure about potential improvements.

We were considering the possibility of compartmentalizing their tools. Currently, in Sysdig Secure, they bundle multiple features, and we are unable to use them individually. For instance, if we only need compliance scanning, we have to deploy the entire secure package. This is because of the way their agent functions, but I can't delve into more details.

I have been using Sysdig Secure for the past 4 to 5 years. 

Currently, I would rate it around nine to ten. In the past, it was approximately five to six. There have been significant improvements in the last two weeks.

It heavily depends on the features used. We've encountered some bottlenecks due to the architecture of the agent, but I can't elaborate. Other than that, we're using Kubernetes with over thirty thousand services on the masters, and it can handle all of them. Scalability is generally good, unless dealing with specific workloads that pose challenges, but I can't provide details.

We regularly reach out to them with any questions, even minor ones, as that's the support they offer us. I'm not sure if we're considered a valuable customer or if this level of support is standard for everyone, but they always encourage us to ask about anything. So, we frequently ask questions, even simple ones like constructing a proper query from their perspective, and they assist us with these tasks.

Positive

We consistently explore new solutions through proof of concept to assess if there's anything that could potentially replace or offer superior features. Thus far, we haven't come across anything that comprehensively covers all the features Sysdig Secure has, while also maintaining the same level of support and documentation.

Initially, it was challenging. The documentation was insufficient, but over the years, there has been significant improvement. They now offer comprehensive, step-by-step documentation, including Helm Charts, making deployment, especially for those using Helm, quite straightforward in my opinion.We initially began with on-premises deployment but later transitioned to the cloud due to engineering resource constraints, finding it more manageable to handle.

The on-premises deployment took a few days, given its complexity. Now, deploying upgrades or similar tasks takes a maximum of two hours, including testing.

In comparison to other cloud solutions, it's reasonably priced. However, when compared to in-house built open-source projects, it might be considered somewhat costly. The cost depends on whether someone sees the support provided by Sysdig as an advantage or if it's deemed unnecessary. Personally, I find the support to be excellent and consider it a good value.

I would offer the same advice to anyone considering a new product—always compare and weigh the pros and cons based on your specific use case. Overall, I would rate it 8 out of 10. 

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.

Neutral

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.

We are a cloud provider, and we use the solution to collate some issues in our environment. 

The solution has improved the resolution time. We can detect any issue in the syslogs more quickly.

The log monitor is the most valuable feature.

I tested the solution, however, I haven't put my hands on it too much and haven't seen any issues so far.

The dashboard could be more simple and show the more important issues that are detected first. We'd like to be able to set it up so more important issues show up more prominently in the dashboard. 

I have been using this solution for six to twelve months.

The stability is very good. 

We have not tested the scalability. This is my first deployment. 

Our technicians do not often ask for support, however, the support is okay. The questions they asked were handled responsively. 

Positive

We previously used an open source solution. This is the first solution we have used for this kind of work. We are using syslog-ng with Sysdig, and I am comparing them both. 

The solution was easy to deploy and easy to use. The technicians found that it was not too difficult to use.

The initial setup was not complex. It's easy.

I handled the deployment on my own. 

The pricing is okay. I need the cheapest price. However, the pricing I've seen is okay. 

I did not evaluate any other options. I plan on testing more options next year. 

It hasn't necessarily freed up time for me. I haven't noted any time to value yet.

It's a good solution and better than the open source option I tested. I need more time to test and clarify the solution. While it is okay, I expect more from it. I'd like to have something that is out of the box. 

I'd rate the solution an eight out of ten.