Three reasons California Casualty and Cloudflare should talk.

Point of view

Modernize application delivery and email security around policyholder journeys through phased, measurable changes that preserve the existing application architecture.

Why Cloudflare?
Why now?

Cloudflare offers one migration path from the visible Azure Front Door and Mimecast layers to integrated delivery, application protection, email security, and resilient catastrophe... Quote, account, claims, and catastrophe journeys are trust-critical for the affinity groups California Casualty serves.

DNS / HTTP recon

Azure Front Door is identified by both the www CNAME and x-azure-ref response header; no cf-ray was observed on the apex during recon.

Official company source

California Casualty publicly exposes quote and claims journeys, including an online non-customer claim submission path; the private...

DNS / HTTP recon

Microsoft 365 is identified by MX and SPF, while Mimecast is identified by the public SPF record.

Three highest-impact use cases

What to prove together

Prioritized by business impact and strength of public evidence.

01 Business outcome

Modernize the public edge

Cloudflare CDN + WAF + DDoS Protection + Load Balancing What Cloudflare does

A controlled edge migration can combine delivery, application security, DDoS protection, and traffic steering while preserving Microsoft-hosted origins.

Bounded pilot

Proxy one low-risk hostname or route with the current origin preserved for rollback.

Measure

p95 latency, cache hit ratio, origin offload, blocked attacks, operating cost.

02 Business outcome

Protect quote, account, and claims journeys

Bot Management + API Shield + Turnstile + Rate Limiting What Cloudflare does

Apply bot, abuse, and API controls to the highest-value customer journeys after endpoint discovery.

Bounded pilot

Discover one bounded API or agent workflow, then enforce schema, identity, and rate policy.

Measure

Discovered endpoints, blocked abuse, policy coverage, origin load, p95 latency.

03 Business outcome

Evaluate email-security consolidation

Cloudflare Area 1 Email Security + DMARC Management What Cloudflare does

Run a detection and operational comparison against the identified Mimecast path before any replacement decision.

Bounded pilot

Run a 30-day parallel evaluation for one mail domain or user cohort.

Measure

Detection lift, false positives, analyst time, mailbox cost, user-reported misses.

Discover
Prove
Scale

30-day DiscoverInventory Azure Front Door routes, security policies, traffic, origins, and Mimecast scope; deploy Cloudflare in a non-production or low-risk...

60-day ProveMove a low-risk public route, enable managed WAF and DDoS controls, and run Area 1 in evaluation mode alongside the existing mail path

Scale by evidenceExpand successful edge controls to quote and claims routes, decide email-security scope from comparative results, and document rollback and...

Compact value model

BaselineCurrent vendor run-rate + egress/compute + operating hours.

ValueRetired overlap + avoided load/incidents + hours returned.

DecisionAnnualized pilot delta - Cloudflare run-rate - one-time migration cost.

Cloudflare
overview

ProtectWAF, DDoS, bot, API and email security

AccelerateCDN, DNS, load balancing and smart routing

ConnectZero Trust, private access and secure networking

BuildWorkers, R2, AI and developer services