Armor vs. Cloudflare Zero Trust Services

Armor gives you what you need to be successful regardless of technical ability. If you can maintain the systems yourself, you are definitely ahead of the game with their service. If you're not prepared to configure and maintain the systems, they do a pretty good job of getting it set up during the onboarding process so that you don't need to dig into the technical guts too much. If you find yourself in over your head, their support staff can handle it for you in most cases.

Incentivized

I wanted to securely connect to my servers without getting tracked by malicious attackers, even though I was on public Wi-Fi. Security was my top priority, and I also wanted a setup that was easy and quick to start and provided great network performance. Cloudflare's Zero trust matches my criteria for becoming my first choice.

Incentivized

• Security - we have requirements met right out of the box and the implementation of new resources is done with security in mind.
• Speed - We can scale resources easy and the infrastructure is fast and efficient.
• Responsiveness - Support tickets are handled very fast with almost immediate solutions.

Incentivized

• Block access to known bad, risky, or unwanted destinations at the DNS or HTTP level.
• Excellent protection for remote users.
• Best in class browser isolation techniques.

Incentivized

• Authentication and access against the secure messaging portal is overkill when the response I'm logging in to see merely says, "yes, we have your message. An agent will respond shortly". There should be an option to receive updates like this through email.
• The online portal that allows us to clone servers is very slow to respond. More than once I've spun up an additional server due to the lack of visual feedback on the initial request.
• The web application firewall does not seem to be sophisticated enough to differentiate between logged in administrators and end users. We use a CMS system which allows admins to create scripts. These often get barred by the WAF even though they are not malicious.

Incentivized

• Cloudflare picks the nearest device location to route the traffic, but It would be great if we could select any particular location.
• Cloudflare enables monitoring for all the connected clients; it would be great if we could monitor any individual client device while keeping some client devices private.
• Sometimes, its DNS is not able to resolve a few project websites; we have to manually purge the cache and even disable the Security to get the work done. So, it would be better if we could manually provide a DNS list or whitelist some websites.

Incentivized

Within a few hours, new engineers are trained in basic tasks and are quite happy they are able to resolve issues independently. After SSO is configured, onboarding is as simple as signing into m365 via a web browser popup.

Incentivized

Approximately 50% of all messages we receive are automated. Either that an agent will be assigned, has been assigned, or a ticket is closed. I'd like to see more 'real' interaction, and less box ticking, though I appreciate process has to be followed. That's the one point off. Everything else is very good.

Incentivized

Good chat support from the portal for basic questions and minor issues. The enterprise support line is provided as well.

As long as all Cloudflare products and services rely on anycast technology, in a complex approach Cloudflare is faster and more relevant for cloud applications. The balance between security and performance is fully established. Also, Cloudflare has quite a good stack for API connection protection, like the API Shield example, which makes it more effective compared to F5 for example. Warp as a ZTNA agent gives better visibility and device posture information than FortiClient does.

Incentivized

• Cloudflare has provided us with 100% uptime even during planned maintenance
• Cloudflare has reduced time for engineering fixes from hours (or days) to minutes in some cases (primarily through Workers)

Incentivized