POC Playbook (Distributor/MSP)
Objective
Run a repeatable, defensible POC that proves Cyprob EE value for enterprise and service-provider use cases.
POC Duration
Recommended: 5 to 10 business days.
Roles
- Sponsor: commercial owner of the evaluation
- Security Lead: validates detection quality and workflow fit
- Infra Lead: validates deployment and operational constraints
- Cyprob Team: owns demo flow, technical enablement, and evidence package
Scope Definition
Define scope before any demo execution:
- Target type: lab-only, selected internal segment, or mixed
- Asset count range
- Required deployment model: standard vs air-gapped
- Success criteria and acceptance thresholds
Success Criteria (Minimum)
- Platform deploys in agreed environment model.
- First scan-to-report cycle is completed successfully.
- Findings include evidence sufficient for remediation decisions.
- Team confirms operational fit (auth, roles, visibility, workflow).
Recommended Demo Sequence (5-7 Minutes)
- Show health and login.
- Start scan on pre-agreed target.
- Show discovered assets/services.
- Show finding evidence (not only title/severity).
- Show report generation and export.
- Show ownership flow (team/business-unit context if enabled).
Validation Matrix
Use this matrix during the POC review.
| Area | Validation Question | Evidence |
|---|---|---|
| Detection quality | Are findings actionable, not noisy? | Findings with context/evidence |
| Performance | Is execution time acceptable for agreed scope? | Scan completion timestamps |
| Operations | Can team run/observe/retry without vendor dependency? | Runbook steps + successful repetition |
| Deployment fit | Does it run in required network model (incl. restricted)? | Deployment checks + health validation |
| Reporting | Can leadership-ready output be generated quickly? | Exported PDF/CSV artifacts |
Non-Goals (to prevent POC drift)
- Full environment coverage in first cycle
- Immediate replacement of every legacy workflow
- Exhaustive integration rollout in the same phase
Deliverables at POC End
- POC summary (scope, timeline, outcomes)
- Evidence pack (health checks, scan IDs, finding examples, report artifacts)
- Gap list (technical, process, ownership)
- Production recommendation with phased rollout path
Exit Criteria
POC is considered successful if:
- Minimum success criteria are met,
- Key stakeholders sign off,
- No critical blocker remains unresolved.
Next Action
If exit criteria are met, move to production planning with deployment model selection and operational ownership mapping.