Security Strategy
8 POSTS
What your team should see in the first 30 days after Cloudflare go-live
The first month should leave your team with tested customer journeys, clear change responsibilities, evidence for tuning decisions, and a usable response record.
Ilyas EsmailWhen Cloudflare blocks checkout during your campaign
The campaign is live and support has a blocked-checkout screenshot. Start with the customer journey, connect it to security evidence, and verify the fix through payment.
Ilyas EsmailA Cloudflare WAF change-control runbook for the first hours
A WAF adjustment needs a clear hypothesis, a narrow scope, and a recovery path. Here is what the first hours of a controlled change should contain.
Ilyas EsmailWhat Cloudflare’s H1 2026 DDoS report means for your edge
Cloudflare is already in front of your application. The next step is making sure your configuration, application changes, and incident response stay aligned.
Ilyas EsmailHow South African banks should choose who runs Cloudflare
For a South African bank, the Cloudflare question is not a partner list. It is who owns WAF, bots, DNS, and Sunday night after go-live.
Ilyas EsmailHow to choose who runs Cloudflare
A licence is not an operator. Before you pick who runs Cloudflare, name who will change a WAF rule on a Sunday night.
Ilyas EsmailHow African banks should buy Cloudflare
African banks often buy a Cloudflare licence and leave it half-configured. The real decision is who operates it after go-live.
Ilyas Esmail
Introducing the Vigilbase Network
Vigilbase now operates AS402630, a small but important step toward more reliable, independent infrastructure.
Ilyas Esmail