I am not familiar with the current deployment options for Cisco Secure Workload, but it seems to involve deploying an agent, which is about as complex as other solutions. One significant difference among these products is how much they enable you to manage noise. Some criticisms of products like Palo Cortex or Rapid7 are that they are very noisy, with lots of false positives and alerts that customers do not consider actionable. In order for an alert to be actionable, customers need to know what steps to take to resolve it, and sometimes the products are not clear enough. Wiz has been differentiating itself recently by adding extra controls in the scoring, allowing for a custom component to the security scoring. This makes alerts less noisy and easier to focus on for customers who want fewer alerts coming out of the product. Security is a problem that never ends, and customers appreciate the ability to focus their activity since their teams can only handle so much at a time. Therefore, the more these products can do to be less noisy and provide clarity and focus, the better they will perform.

The initial setup of this solution is complex because you need to have a good understanding of your information system. You need to tag your different assets. 

It took two people approximately one week to deploy. It is a full-time commitment to deploy this solution, and after that, you need to implement controls to tag the assets.

I rate the initial setup a nine out of ten. We use the micro-segmentation features two times a year.

The implementation is pretty straightforward.

The initial setup is straightforward. It doesn't take long to deploy. You just need to install the agents on the machines and if you want to install it on-premises then you use the cloud servers to help with the setup. The entire process takes a week or two. 

The initial set up took some time because we wanted to test some different client scenarios before we offered it as a service to clients. To get a good set up for the different scenarios and to make sure that we had a good procedure to wipe all the disks and that we had the necessary proof that the disk was securely wiped before going to integration with the next clients. It took some time to see how could we do that.

The solution's setup process isn't too easy or hard. It is moderate in terms of ease of implementation.

It's best to have one to two people available to handle deployment and maintenance. Even though one person can handle the process, it's good to have a backup if they go on vacation or take PTO. Usually, engineers can handle any task. 

The initial setup was straightforward, and deployment took one to two days.

The setup was complex because of how our network is structured. In the network administration setup, Cisco Tetration requires some planning.

The complexity of the setup depends on the version being installed. The cloud version can be up and running in a couple of hours. The other version could take a couple of weeks. Customers who do not already know the product shouldn't really be deploying it on their own. Once it's up and running, a single person can manage and grow the entire environment in a fraction of the time it would take to do manually. Some organizations will allow as little as 2-3 hours a week and some will have to spend a lot more time on it. The resource allocation really just depends on what it is being used for.

It was very straightforward since we're doing cloud-based management.

The initial setup was complex, because it had a bunch of little details that needed to be tied together.

The initial setup was straightforward. It took us about three days to deploy the solution. To reach your first operational capability, from then onwards, it depends on the scenario. We usually spend weeks, if not months, in order to adapt the system to the customer's use case and this requires professional services, specific for the situation.