Purpose
This pilot is for organisations that need clearer internal network separation but want a focused proof point before a broader network redesign or multi-site programme. Aimed at segmenting a flat or weakly separated network into cleaner user, server, IoT, and guest zones with documented controls, validation, and rollback notes for a controlled pilot scope.
What you get
- Discovery of current VLANs, subnets, and key user journeys for the scoped pilot area
- Target zone model, access matrix, and migration/test planning for the agreed scope
- Controlled implementation for the selected zones or cohorts with validation evidence and rollback notes
- Close-out summary with findings, constraints, and next-step recommendations
Typical outcomes
- Cleaner separation between guest, user, server, and device traffic in the scoped pilot area
- Documented access rules and validation outcomes for key business journeys
- A clearer path to broader segmentation or follow-on controls where needed
Typical pilot scope
A focused segmentation pilot for one campus/site or a narrowly defined environment segment. Final scope, zone model, assumptions, exclusions, and validation paths are confirmed in the SoW.
Best fit
- Sites with relatively flat internal access and a need to separate user, server, guest, or device traffic
- Environments where unmanaged exceptions are known but manageable within a limited pilot
- Teams wanting a practical proof point before broader network refresh or redesign work
Prerequisites
- Managed switches and firewalls that support the required VLAN and ACL features for the pilot scope
- Administrative access, diagrams where available, and named technical validation contacts
- Approved change window, rollback expectations, and communication plan for the pilot activity
Assumptions and boundaries
- One campus/site or agreed environment segment only
- This pilot does not include full NAC rollout, global SD-WAN redesign, or broad multi-site segmentation
- The final engagement detail, assumptions, exclusions, and migration boundaries are confirmed in the SoW before work begins
Common risks we look for
- Unmanaged switches, daisy chains, or hard-coded IPs that complicate migration
- Legacy apps, printers, scanners, or voice traffic failing when controls change
- Insufficient rollback preparation for the agreed migration window
- The pilot being treated as a full redesign rather than a controlled proof point
What happens after the pilot
If the pilot confirms the right direction, Virtus can help you plan broader segmentation, additional zones or sites, or an appropriate managed network path.
Roll into managed → Managed Network
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
