Demo library
Ten chapters, each one a problem Horizon Inc has and the part of Cloudflare One that solves it. Each stands alone, and the named paths below string them into a demo for a particular room.
Twenty-five minutes, a general audience: the whole of Cloudflare One.
A specific question: pick the chapter that answers it. Every chapter page says what it needs before you start, and which part of it is not built yet.
Paths
The whole of Cloudflare One
The overall demo: identity, retiring the VPN, data protection, AI, and the evidence afterwards - one company, one afternoon.
- 1. Identity and per-application access
- 2. VPN replacement for an internal app
- 6. DLP on uploads and on internal apps Planned
- 8. Shadow AI, and the sanctioned path
- 10. Evidence: logs, decrypted payloads, prompts
Replace the VPN
For a room that runs a VPN concentrator and is tired of it.
- 1. Identity and per-application access
- 2. VPN replacement for an internal app
- 3. Privileged SSH and database access
- 7. Device posture for sensitive applications Planned
Secure web gateway and data protection
For a room whose question is what leaves the building, and how.
- 5. DNS filtering for office networks Planned
- 6. DLP on uploads and on internal apps Planned
- 4. Clientless isolated access for contractors Planned
AI security
For a room whose staff and agents are already using AI, sanctioned or not.
The full tour
Every chapter, in order. For a workshop rather than a meeting.
- 1. Identity and per-application access
- 2. VPN replacement for an internal app
- 3. Privileged SSH and database access
- 4. Clientless isolated access for contractors Planned
- 5. DNS filtering for office networks Planned
- 6. DLP on uploads and on internal apps Planned
- 7. Device posture for sensitive applications Planned
- 8. Shadow AI, and the sanctioned path
- 9. Securing MCP and agent access
- 10. Evidence: logs, decrypted payloads, prompts
Chapters
6 of 10 can be run today. Planned chapters are listed so the shape of the library is visible; they have no script yet. See coverage for every capability and where it is shown.
| # | Chapter | Proves | Status |
|---|---|---|---|
| 1 | Who are our people, and what are they allowed to reach? | Access, FlareID (OIDC + SCIM), App Launcher, Access audit log | Ready |
| 2 | Retire the VPN concentrator. | Cloudflare Tunnel, Private network routes, Split tunnels, Internal DNS, Resolver policies, Access | Ready |
| 3 | Admins reach servers without standing credentials. | Access for Infrastructure, SSH certificate authority, Access for SaaS (OIDC), Private network routes | Ready |
| 4 | Contractors get access; they do not get a laptop. | Clientless Browser Isolation, One-time PIN, Access | Planned |
| 5 | Filter the internet for an office with no appliance. | Gateway DNS policies, DNS locations, Block page | Planned |
| 6 | Stop company data leaving through the browser. | Gateway HTTP policies, DLP profiles, Payload logging, Antivirus and sandbox | Planned |
| 7 | Only healthy, managed devices reach production. | Device posture, Device profiles, DEX | Planned |
| 8 | Our staff are pasting customer data into ChatGPT. | Application Library, Gateway HTTP policies, Browser Isolation, AI prompt logging | Ready |
| 9 | Our AI agent reaches what the person driving it cannot. | MCP server portal, Access, Gateway DLP on MCP traffic, AI Gateway | Ready |
| 10 | Show the auditor what happened. | Access audit log, Gateway activity log, Payload and prompt logs | Partial |
Before any of them
- Setup: the Cloudflare One client, the agent client, and the one-time logins.
- Lab only means the chapter reaches the private estate on the lab VM - a server with a private address, which a laptop deploy does not have.
- Sign in as the person each chapter names. Most use Alice Watson, a content strategist with no special access anywhere.