Purpose
This pilot is for organisations that need stronger internal segmentation between workloads but want a small, controlled proof point before broader platform or security architecture work. It is aimed at validating tighter east-west controls for a selected application pair or segment, document dependencies, and prove that limited micro-segmentation can be introduced without breaking agreed business journeys.
What you get
- Discovery and dependency review for the selected application pair or scoped segment
- Draft allow-list / policy matrix for approved flows and validation checkpoints
- Controlled pilot implementation or simulation for the agreed scope, with evidence and rollback notes
- Close-out summary with gaps, constraints, and next-step recommendations
Typical outcomes
- Better visibility of application dependencies and hidden east-west traffic assumptions
- A practical policy pattern for the scoped application pair or segment
- Clearer understanding of what would be required to scale micro-segmentation safely
Typical pilot scope
A focused micro-segmentation review and pilot for one agreed application pair or limited workload group. Final scope, dependencies, and test method are confirmed through intake and the engagement SoW.
Best fit
- Environments where internal trust boundaries are too broad and application traffic is poorly constrained
- Teams wanting a controlled proof point before wider host-, hypervisor-, or firewall-based segmentation work
- Organisations with a defined application owner and validation contacts available for a small pilot
Prerequisites
- Administrative or delegated access to the relevant policy control point(s) and current diagrams where available
- Named application owner, technical contact, and validation contacts for the selected workload pair
- Agreed change window and a practical rollback path for the scoped pilot
Assumptions and boundaries
- The pilot is limited to one agreed application pair or narrowly defined workload segment
- This pilot does not include full estate dependency mapping, organisation-wide segmentation, or NAC rollout
- The final engagement detail, assumptions, exclusions, and validation scope are confirmed in the SoW before work begins
Common risks we look for
- Undocumented application dependencies that create hidden breakage risk
- Legacy services, hard-coded ports, or service accounts that complicate policy design
- Validation contacts not being available when the pilot needs to be tested
- The pilot being treated as a broader segmentation programme without formal re-scope
What happens after the pilot
If the pilot confirms the right direction, Virtus can help you plan broader segmentation, policy standardisation, or the next appropriate managed or project 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
