Purpose
This pilot is for organisations considering SASE that need a small, practical quickstart to decide what should come first and what a wider rollout would really involve. intended to establish a pragmatic SASE baseline by selecting one access path, integrating identity, and documenting a phased roadmap before larger change or platform expansion.
What you get
- Selection of one quickstart path, such as ZTNA for one app or SWG/DNS for a pilot cohort
- Identity integration and MFA baseline for the chosen path
- Initial telemetry, exception handling, and visibility setup for the scoped quickstart
- Quickstart architecture notes, findings, and phased next-step roadmap
Typical outcomes
- Identity-anchored access control established for a small, low-risk scope
- Practical evidence of where SASE can add value first in the client environment
- A clearer roadmap for phased rollout rather than platform sprawl or guesswork
Typical pilot scope
A focused SASE quickstart covering one agreed access path and one small pilot scope. Final scope, assumptions, exclusions, and validation method are confirmed through intake and the SoW.
Best fit
- Organisations exploring SASE but not ready to commit to a full stack rollout immediately
- Teams that need a practical first step grounded in identity, visibility, and a limited pilot scope
- Environments where either ZTNA or SWG/DNS is the most sensible first path to test
Prerequisites
- Administrative or delegated access to the chosen platform and the relevant identity system
- A clearly agreed first path, cohort, or application for the quickstart scope
- Named sponsor, technical contact, and validation users available for the pilot period
Assumptions and boundaries
- The quickstart is limited to one agreed path and one limited pilot scope
- This pilot does not include full SASE stack rollout, broad DLP/CASB implementation, or multi-path deployment unless expressly added
- The final engagement detail, assumptions, exclusions, and validation boundaries are confirmed in the SoW before work begins
Common risks we look for
- The client tries to combine too many security paths into one pilot
- Identity or licensing prerequisites are weaker than expected
- Operational ownership is unclear after the quickstart is complete
- The pilot becomes a disguised broader security transformation project
What happens after the pilot
If the quickstart confirms the right direction, Virtus can help you plan the next path, broader rollout sequencing, or an appropriate managed-service follow-on where relevant.
Roll into managed → Safe Web & DNS
Start pilot scoping
Use the intake form to tell us about your current environment, priorities, and the outcome you want to achieve. If the scope looks suitable, we will confirm the next step and send the SoW for approval.
Start pilot scoping
