PoC & Demos
I like PoCs that are simple, measurable, and focused on reducing adoption risk. The goal is not just “it works”, but “we know what to monitor and how to deploy safely”.
Define success
Agree on what “good” means: coverage, latency impact, false positives, and operational effort.
Run a scoped test
Start small: one app / one domain / one traffic segment with clear rollback.
Validate & document
Findings, gaps, tuning recommendations, and a rollout plan with owners.
What a PoC plan usually contains
- Scope: domains/apps, environments, and traffic segments
- Success criteria: security outcomes + performance constraints
- Test cases: attacks to block, edge cases to allow
- Observability: what logs/metrics we use to validate
- Rollout approach: phased enablement, tuning loop, and rollback steps
Good PoCs produce a clear decision: “go”, “go with changes”, or “don’t go yet” — with reasons.