Website security checklist for UAE businesses

Short answer

Seventeen public settings decide most of a website's outside-in security: HTTPS, the HTTP-to-HTTPS redirect, HSTS, six browser security headers, cookie flags, mixed content, outdated JavaScript, server version leaks, SPF, DMARC, DNSSEC, CAA and security.txt. The table below ranks them by impact and shows the UAE PDPL, PCI DSS and OWASP references SiteShield cites for each.

For website owners, IT teams and agencies in the UAE & GCCBy Mumshad JawadUpdated

The checklist, by priority

Points are the weight each item carries in a SiteShield grade, out of 100. The top seven items carry 90 of the 120 points.

#ItemPointsStandards citedFix
1Site loads over HTTPS30UAE PDPL: security of personal data
PCI DSS 4.0 Req. 4.2
OWASP ASVS V9
Install a free TLS certificate (Let's Encrypt, or put the site behind Cloudflare's free plan) and serve every page over https://.
2DMARC policy12Business email compromise (BEC) defence
Google & Yahoo bulk sender rules (2024)
Publish a TXT record at _dmarc.yourdomain: start with v=DMARC1; p=none; rua=mailto:you@yourdomain, review reports for 2–4 weeks, then move to p=quarantine and p=reject.
3http:// redirects to https://10OWASP ASVS V9
PCI DSS 4.0 Req. 4.2
Add a permanent (301) redirect from http:// to https:// on your server or CDN. On Cloudflare: SSL/TLS → Edge Certificates → Always Use HTTPS.
4HSTS (Strict-Transport-Security)10OWASP ASVS V14.4
Mozilla web security guidelines
Send the header: Strict-Transport-Security: max-age=31536000; includeSubDomains
5Content-Security-Policy10PCI DSS 4.0 Req. 6.4.3 (payment page scripts)
OWASP ASVS V14.4
Start with a report-only policy, e.g. Content-Security-Policy-Report-Only: default-src 'self'; then allow the domains you really use and switch to enforcing.
6No known-vulnerable JavaScript libraries10OWASP Top 10 A06: Vulnerable and Outdated Components
PCI DSS 4.0 Req. 6.3.3
Update the libraries listed above to their latest versions and remove any you no longer use.
7SPF record8Business email compromise (BEC) defence
UAE TDRA / aeCERT email security guidance
Publish one TXT record on your domain, e.g. v=spf1 include:_spf.google.com ~all (use your email provider's value). If you never send email from this domain: v=spf1 -all
8Clickjacking protection5OWASP ASVS V14.4Send X-Frame-Options: SAMEORIGIN, or add frame-ancestors 'self' to your Content-Security-Policy.
9Cookie security flags5OWASP ASVS V3.4
UAE PDPL: security of personal data
Set cookies with: Secure; HttpOnly; SameSite=Lax
10No mixed content5OWASP ASVS V9Change every http:// resource link on the page to https:// (or a relative path).
11X-Content-Type-Options3OWASP ASVS V14.4Send X-Content-Type-Options: nosniff
12Software versions hidden3OWASP ASVS V14.3Remove version numbers from the Server and X-Powered-By headers and the generator meta tag (e.g. server_tokens off; in nginx, expose_php = Off in PHP).
13Referrer-Policy2UAE PDPL: data minimisationSend Referrer-Policy: strict-origin-when-cross-origin
14Permissions-Policy2OWASP ASVS V14.4Send Permissions-Policy: camera=(), microphone=(), geolocation=()
15DNSSEC2UAE TDRA / aeCERT guidanceEnable DNSSEC at your DNS provider (one click on Cloudflare) and add the DS record at your registrar.
16CAA record2CA/Browser Forum baseline requirementsAdd a CAA record, e.g. 0 issue "letsencrypt.org" (list the CAs you actually use).
17security.txt1RFC 9116Publish /.well-known/security.txt with at least: Contact: mailto:security@yourdomain and Expires: (a date within a year).

Each item links to a full guide with platform-specific steps. To see which items your site already passes, run a free scan: it checks all 17 in about 30 seconds.

The standards behind the checklist

UAE PDPL

The UAE's Personal Data Protection Law (Federal Decree-Law No. 45 of 2021) expects organisations that process personal data to protect it with appropriate technical and organisational measures. SiteShield cites it where a setting protects visitors' personal data in transit or in their browser, or limits what is shared.

Cited by: Site loads over HTTPS, Referrer-Policy, Cookie security flags

PCI DSS 4.0

The card industry's security standard for anyone who stores, processes or transmits card data, or whose website can affect a payment page. SiteShield cites requirement 4.2 (strong cryptography in transit), 6.3.3 (patch known vulnerabilities) and 6.4.3 (control the scripts on payment pages).

Cited by: Site loads over HTTPS, http:// redirects to https://, Content-Security-Policy, No known-vulnerable JavaScript libraries

OWASP ASVS and Top 10

The Open Worldwide Application Security Project's Application Security Verification Standard (ASVS 4.0) lists testable requirements: V3 session management, V9 communications, V14 configuration. The OWASP Top 10 (2021) ranks the most common web risks; A06 is vulnerable and outdated components.

Cited by: Site loads over HTTPS, http:// redirects to https://, HSTS (Strict-Transport-Security), Content-Security-Policy, Clickjacking protection, X-Content-Type-Options, Permissions-Policy, Software versions hidden, Cookie security flags, No mixed content, No known-vulnerable JavaScript libraries

UAE TDRA / aeCERT guidance

The UAE's Telecommunications and Digital Government Regulatory Authority (TDRA) and its national computer emergency response team, aeCERT. SiteShield cites their security guidance for the email-authentication and DNS items.

Cited by: SPF record, DNSSEC

Business email compromise (BEC) defence

Fake invoices and payment-change requests sent "from" a real company's domain. SPF and DMARC are the DNS records that stop criminals using your domain this way.

Cited by: SPF record, DMARC policy

Google & Yahoo bulk sender rules (2024)

Since February 2024, Gmail and Yahoo Mail require bulk senders to publish SPF, DKIM and a DMARC record.

Cited by: DMARC policy

RFC 9116

The internet standard that defines security.txt.

Cited by: security.txt

CA/Browser Forum baseline requirements

The rules every public certificate authority follows, including the obligation to check CAA records before issuing.

Cited by: CAA record

Mozilla web security guidelines

Mozilla's widely used recommendations for HTTP security headers, including HSTS.

Cited by: HSTS (Strict-Transport-Security)

This page explains technical controls; it is not legal advice. For a compliance programme, speak to a qualified adviser.

Why email items carry so much weight

Business email compromise starts with an email that appears to come from a real company: a supplier's "new bank details", a CEO's "urgent transfer". DMARC (12 points) and SPF (8 points) are the two DNS records that let Gmail, Outlook and other receivers reject those fakes. They take minutes to publish, which is why they rank above every browser header except HSTS and CSP.

FAQ

Does passing this checklist make my website PDPL or PCI DSS compliant?

No. Compliance covers far more than a website's public configuration: policies, access control, data handling, contracts and audits. The checklist covers the outside-in technical measures that are easy to verify and often missing, and shows which standard each one supports.

Which items should a UAE business fix first?

Work down the points column: HTTPS (30), then DMARC (12), then the HTTP-to-HTTPS redirect, HSTS, Content-Security-Policy and outdated JavaScript libraries (10 each), then SPF (8). Those seven account for 90 of the 120 points.

Does the checklist apply outside the UAE?

Yes. The checks are the same for any public website: .ae, .sa, .qa, .com or anything else. Only the legal references differ; Saudi Arabia, Qatar and Bahrain have their own personal data protection laws, and the DIFC and ADGM free zones have their own data protection rules.

See which items your site passes

Run all 17 checks on your website and email domain in about 30 seconds. Free, no signup, passive checks only.

Rather not do it yourself? Fix it for me starts at AED 750 (about USD 205 by PayPal), quote agreed first. Monitoring re-scans weekly for AED 99/month or AED 990/year.