Skip to article content

Is HTTPS enough to protect your website? What a WAF and CDN add

HTTPS does not establish that your entire website is protected. Understand encryption, a web application firewall and a CDN, and what to ask about their configuration and limits.

HTTPS, a WAF and a CDN address different needs

Your hosting includes “SSL”, someone recommends a firewall and you have heard about a CDN. It is easy to combine these under one idea: “the website is protected”. They serve different purposes, and none establishes the security of the whole website on its own.

Start with three questions: what does each service do, is it configured for your website and who reviews it? A name on an invoice does not answer all three.

You do not need to choose a brand before understanding the need or buy every available tool. Identify the information to protect, functions depending on the website and measures relevant to those risks.

HTTPS protects communication rather than certifying the entire website

HTTPS uses encryption to protect communication between the browser and the server it connects to. It helps prevent people along that path from reading data as plain text. The MDN explanation of HTTPS describes its transport role.

Offers still commonly say “SSL certificate”, although TLS replaced that technology. Establish which certificate is managed, for which domain and who handles renewal.

An encrypted connection does not check excessive user permissions, component flaws or recoverable backups. An address beginning with https:// cannot establish that those other matters are resolved.

A WAF filters requests; a CDN distributes content

A WAF, or web application firewall, inspects application traffic and applies rules to filter requests. It can help mitigate certain attacks, rather than automatically recognising or stopping every problem. Cloudflare’s WAF documentation explains its role and scope.

A CDN is a server network distributing content and potentially storing copies closer to visitors. Some services add filtering or mitigation of attacks attempting to overwhelm a website. These features depend on the product, plan and configuration: “having a CDN” does not specify the full protection. Cloudflare’s explanation of CDNs separates content delivery from additional functions.

A provider may offer CDN, WAF and HTTPS together in one dashboard. That does not make them the same control or confirm that every option is active.

Ask about coverage, configuration and responsibility

A worksheet for understanding what you actually have
MeasureWhat to askEvidence to retain
HTTPS and certificateWhich domains are covered and who receives renewal or error notices?Intended domains, owner and connection checks.
WAFWhich traffic passes through it, which rules apply and who reviews blocks or exceptions?Agreed configuration and an event review example without sensitive data.
CDNWhich content is delivered and stored, and which protections does the service include?Contracted features and treatment of user-specific pages.
Response to an issueWho investigates a notice and what do they need to act?Owners, contact channels, support scope and agreed procedure.

The worksheet supports a conversation rather than certifying security. Paying for a service does not establish that every option is used. Confirmation may require authorised dashboard and log access.

If you receive notices or screenshots of blocked attacks, record what they show and what they cannot establish. Our vulnerability report guide helps separate a signal from a confirmed issue.

Check that protection preserves the functions you need

Assess legitimate use too. If a rule prevents a form submission or a connection between systems, the team needs to investigate the event before adjusting it. Disabling every protection to remove a symptom leaves another question unresolved.

With a CDN, establish which pages can be shared as common content and which contain session data. Shop and private-area settings need to preserve their intended behaviour. A working homepage does not establish that every screen is configured correctly.

Fictional example: after rules change, a form stops confirming submissions. A review should retain the time and journey, compare available events and test the agreed adjustment. This does not establish a firewall as the cause on a particular website.

Review access, components and recovery too

These tools do not replace management of the website itself. Establish who has access and which permissions they need, which components require attention and whether backups could restore the service.

For WordPress, a component’s ongoing suitability may need a specific assessment: what to review when a plugin has not been updated for some time. Adding another tool does not automatically address that situation.

Nodo91 can help review security signals and assess what needs attention. Some aspects are externally observable; confirming internal settings requires agreed access and checks. The assessment explains what was checked, what remains unknown and which steps would help next.