Cisco Multicloud Defense vs. Kindite

For WAF functionality and delivery of websites, It's very well suited for traditional firewalling, if you're doing that already, it can be quite difficult to rearchitect everything around this product. So an example of that would be if, like us, you came from a datacenter style architecture within your cloud environment and you are trying to move to a more cloud-fronted architecture. Probably the best way to put it is that can be quite difficult, but once you've deployed, it gets easier operationally. So to kind of reverse engineer everything and then do everything again can be quite tedious in some ways. But that will be specific to people depending on where they're coming from with it.

Incentivized

• The thing that I'd like the most about Cisco Multicloud Defense so far is that it's allowed me to look at security within our cloud environment in a new way and to rebuild it in a far more scalable fashion while giving more control to people that are actually involved in the delivery end of things some ability to manage the networking security within that.

Incentivized

• I think there are some GUI changes that could be made, and probably will be made as the product matures moreso to align it with the wider Cisco security platform look and feel

Incentivized

If it maintains its current direction it will be very disruptive in the cloud security space

Incentivized

It is a straightforward platform to use - no overcomplication or hidden menus - everything is cleanly presented

Incentivized

As of yet I havent logged a TAC case - It will be interesting to see how it is supported as a new product in the medium term

Incentivized

I come from a deployment background, so I've used most of the vendor's firewall technologies. In the cloud, I've primarily used Cisco's legacy Firepower product. It doesn't really parallel with them in that it's not a traditional firewall appliance sitting in the cloud. Its utilization of tags and how it groups objects are separated a little bit as it's very intrinsically linked with the cloud environment itself. It doesn't just sit in it, it spans out into it in a much more organic way. And because of that then you can, as I mentioned before, if there are security requirements that exist on one server, it is very easy to replicate these over to another server utilizing tags without having to configure this new server you're spinning up within the firewall itself. It will pull it all into its inventory with no intervention from you.

Incentivized

• Our availability has increased because of how availability works within this product. Whereas before as running two virtual machines for firewalls, the automated end of this entire deployment where if it sees a health issue, it will build another version itself and drain the old one and re-add the traffic into the new one very cleanly with very little loss. So that's really greatly improved our availability. Then the deployment of new services will also be quicker because, as I mentioned, it is tag-based, if you already have a preexisting tag architecture, you can just add new services into that and they will automatically be pulled into the new system. So it's more efficient in that way. In terms of commercials, I guess it's kind of similar. I don't think it will make a massive commercial difference to us, but in terms of the operational element it will.

Incentivized