CloudflareProtect websites, APIs and networks from attack without adding hardware
Cloudflare places a global network between your users and your applications, so attacks, abusive bots and malicious requests can be filtered before they reach your servers. It also offers Zero Trust access for your own staff through Cloudflare One.

- Reverse proxy
- Traffic to proxied hostnames passes through Cloudflare, and your origin IP address is not exposed
- Layers 3 to 7
- Automatic DDoS detection and mitigation at network and application layers
- Rule-based WAF
- Managed rules, custom rules and rate limiting for web and API traffic
- Cloudflare One
- Zero Trust access, web filtering and data protection for your users
Problems Cloudflare is used to solve
Internet-facing services attract constant automated traffic. These are the issues that usually lead organisations to look at Cloudflare.
| Topic | What it can lead to | How Cloudflare helps |
|---|---|---|
| Distributed denial-of-service (DDoS) attacks | What it can lead to: Websites, APIs or whole network ranges become unreachable, and on-premises equipment or bandwidth is overwhelmed. | How Cloudflare helps: Absorbs and filters attack traffic on Cloudflare’s network at layers 3, 4 and 7. Magic Transit extends this to whole IP ranges using BGP. |
| Attacks on web applications and APIs | What it can lead to: Injection, abuse of known vulnerabilities and malicious requests reaching application servers. | How Cloudflare helps: The web application firewall (WAF) inspects requests against managed and custom rules before they reach your origin. |
| Abusive bots | What it can lead to: Credential stuffing, content scraping, inventory hoarding and fake sign-ups. | How Cloudflare helps: Bot Management uses machine learning to identify and block unwanted bots. |
| Origin servers exposed directly to the internet | What it can lead to: Attackers bypass protections by going straight to the server’s IP address. | How Cloudflare helps: Proxied DNS records return Cloudflare addresses, and Cloudflare Tunnel connects resources without a public IP. |
| Remote access that relies on a VPN | What it can lead to: Users get broad network access once connected, and every application is reachable from every device. | How Cloudflare helps: Cloudflare Access checks each user before granting access to an individual application, as part of Cloudflare One. |
| Slow or inconsistent page loads | What it can lead to: Poor user experience and extra load on origin servers. | How Cloudflare helps: The content delivery network (CDN) caches content close to users and can handle TLS encryption, reducing origin load. |
What Cloudflare does
Cloudflare’s products fall into two broad groups: protecting the applications and networks you publish, and protecting how your own users reach the internet and internal applications.
DDoS protection
Automatic detection and mitigation of DDoS attacks at the network layer (layers 3 and 4) and application layer (layer 7). Cloudflare lists standard, unmetered DDoS protection on all plans.
Web application firewall
Managed rulesets that Cloudflare updates, your own custom rules, and rate limiting rules, with security analytics to review what was blocked.
API Shield
Visibility of API usage and controls to check that APIs are not abused or leaking data.
Bot Management
Machine learning that identifies unwanted bots so they can be blocked.
CDN and DNS
Authoritative DNS for your domain and caching of static and dynamic content on Cloudflare’s network, so origins receive fewer requests.
Cloudflare One (Zero Trust)
Access for application-level authentication, a secure web gateway to filter DNS and web traffic, CASB, data loss prevention (DLP), browser isolation and email security.
Which Cloudflare service fits which problem
Cloudflare is not one product. Matching the service to what you need to protect is the first scoping decision.
| Topic | How traffic reaches Cloudflare | Typical use |
|---|---|---|
| Application services (CDN, WAF, Bot Management, API Shield) | How traffic reaches Cloudflare: You point your domain’s DNS to Cloudflare; proxied hostnames resolve to Cloudflare’s anycast addresses. | Typical use: Public websites, web applications and APIs. |
| Magic Transit | How traffic reaches Cloudflare: Your IP prefixes are announced to Cloudflare using BGP; clean traffic returns over GRE tunnels or private interconnects. | Typical use: DDoS protection for whole networks, data centres and hybrid infrastructure. |
| Cloudflare Tunnel | How traffic reaches Cloudflare: An outbound connection from your environment to Cloudflare, with no public IP needed. | Typical use: Publishing internal applications without opening inbound ports. |
| Cloudflare One (Access, Gateway, client) | How traffic reaches Cloudflare: Users’ devices send traffic through the Cloudflare One client, or users sign in through Access. | Typical use: Replacing or reducing VPN use and filtering staff web traffic. |
Features vary by plan. Confirm which capabilities your plan includes before relying on them.
Before you put an application behind Cloudflare
Points worth checking whether you use Cloudflare or another edge provider. Tick what is already in place: nothing you select is saved or sent.
How VirtuThinko helps you adopt Cloudflare
- 01
Requirements
Identify the domains, APIs, networks or users you want to protect, and the attacks you are most concerned about.
- 02
Proof of concept
Onboard a non-critical hostname or user group and review traffic, rules and analytics with your team.
- 03
Design and deployment
Plan DNS changes, origin lock-down, TLS settings, WAF policies and, where relevant, Zero Trust access policies.
- 04
Tuning and handover
Review security events, adjust rules to reduce false positives and document the configuration.
- 05
Ongoing support
Help with rule changes, new applications and investigating events, as agreed.
No. Your application stays where it is hosted. In the standard setup Cloudflare becomes your authoritative DNS provider, and requests to proxied hostnames pass through Cloudflare’s network before being forwarded to your origin server.
DDoS protection deals with floods of traffic intended to make a service unavailable. The WAF inspects individual web and API requests for attacks such as injection. Cloudflare uses both together for proxied applications.
Yes, through other products. Magic Transit protects whole IP networks from DDoS attacks, and Spectrum provides security and acceleration for TCP and UDP based applications.
Cloudflare’s Zero Trust platform for an organisation’s own users. It includes Access for authenticating users to applications, a secure web gateway to filter DNS and web traffic, CASB, data loss prevention, browser isolation and email security.
No. For example, Cloudflare’s documentation lists a free managed ruleset and limited rate limiting on the Free plan, and some WAF configuration options only on Enterprise. Check the current plan comparison for the features you need.
Explore Cloudflare for your organisation
Tell us which websites, APIs, networks or user groups you want to protect, and where they are hosted. A member of our team will contact you to arrange an initial conversation about whether Cloudflare fits and what a proof of concept would involve.