Infrastructure and Network
Segmentation Testing
Verify whether network and management boundaries enforce the intended access policy. The results provide evidence for limiting attack propagation and maintaining protected business or compliance zones.
01 / Overview
Assessment objectives and control obligations
Segmentation validation establishes a directional source–destination matrix with explicit permitted and prohibited service flows. Representative positions evaluate routing, firewall policy, host enforcement and shared-service dependencies. Management-plane reachability and alternate paths receive separate analysis because indirect administrative authority can circumvent an apparently restricted data-plane connection.
Positive control cases and corroborating flow records distinguish enforced denial from destination failure or an unavailable return route. Deviations are reconciled with approved exceptions and operational requirements. Reporting assigns corrective ownership and records untested directions; sampled boundary validation supports assurance without constituting complete regulatory certification.
02 / Technical analysis
Failure mechanisms and security implications
A timeout does not prove an enforced denial; the destination or return route may be unavailable. Control cases establish whether the security boundary caused the result. Management access is examined for indirect bypass.
03 / Scope
Technical coverage and authorisation boundaries
Coverage is agreed in writing before testing begins. The rows below describe what this service normally examines. Exclusions, testing windows and escalation contacts are recorded in the rules of engagement.
- Zone matrix
- User, server, management, DMZ and OT flows in authorised directions.
- Alternate routes
- Shared hosts, backup networks, remote access and cloud links.
- Rule operation
- Broad, expired or shadowed rules and enforcement evidence.
- Supporting tools
- Environment-appropriate instrumentation may include Nmap, Scapy, NetExec, Flow log analysis, Route analysis. Selection follows the investigative objective, compatibility requirements and approved operating constraints. Automated output requires corroboration against implementation evidence or observed execution before classification as a substantiated finding.
04 / Methodology
Investigation and validation methodology
Threat-informed test design aligns architectural trust boundaries, attacker prerequisites and consequential business outcomes. Automated discovery supports attack-surface coverage; manual validation establishes reachability, effective authority and the causal mechanism of each substantiated control failure.
01
Scope and safeguards
Before active work
We agree assets, test identities, techniques, windows, exclusions and stop conditions, and confirm required third party permissions.
02
Agree expected flows
Define representative sources, destinations and service states.
03
Test and reconcile outcomes
Compare observed connections with policy, rules and corroborating flow evidence.
04
Review and verification
Agreed delivery
Findings pass technical review. We explain remediation and, where agreed, verify the correction during the retest window, including relevant bypass cases.
05 / Assessment options
Access models and evidential confidence
Supplied access determines investigative reach, validation depth and evidential confidence. The proposal records the access model, supporting material and unresolved coverage limitations; no model implies unrestricted authority or exhaustive verification.
- Black box
- Testing starts without supplied credentials or internal design material. External exposure is examined, while authenticated workflows may remain inaccessible.
- Grey box
- Representative accounts and selected design information support direct comparison of roles, tenants and sensitive workflows.
- White box
- Source, configuration and design evidence support root cause analysis. Runtime and access limitations are still recorded.
06 / Deliverables
Decision-support and verification deliverables
Deliverables distinguish what was observed, what was concluded and where the evidence stops. The agreed scope states which evidence, review sessions and retesting are included.
Executive summary
The summary explains the demonstrated exposure, the business functions affected and the treatment decisions required, including material uncertainty.
Technical findings
Each confirmed issue records the affected assets, prerequisites, reproduction evidence and a specific remediation. Technical severity is presented separately from business priority.
Coverage and limitations
The record identifies the systems, identities and conditions tested, together with exclusions and assumptions that affect interpretation.
Treatment and retest status
Recommendations are sequenced by risk, dependency and ownership. Any agreed retest records resolved, partly resolved and unresolved issues without implying a new assessment.
Service specific evidence
A directional test matrix records expected policy, observed outcome and relevant exceptions.
07 / References
Applicable technical references
References are selected for the technology and objective in scope, and the edition applied is recorded. A framework mapping supports review; it is not certification or proof of complete compliance.
- NIST technical security assessment guidance
- The technical assessment guide informs planning, authorisation, execution and reporting. Technology specific procedures are selected separately and constrained by operational safety.
- NIST Zero Trust Architecture
- The architecture reference distinguishes policy decisions, enforcement and resource access. It guides design questions rather than certifying an individual product or organisation.
08 / Safeguards
Operational safeguards and evidence governance
Active work is conditional on written authority from the appropriate asset owner and approved rules of engagement. The operating plan specifies permitted procedures, testing windows, prohibited actions, third-party restrictions and nominated stop authority. Unexpected instability or suspected genuine compromise triggers suspension of affected activity pending the client’s operational decision.
Evidence governance applies purpose limitation, data minimisation and access proportionality to collection, transfer, processing, retention and disposal. The signed terms define authorised recipients and any external processing arrangement. Publication, secondary use and disclosure of client material require the applicable written permission.
Conclusions distinguish substantiated exposure, untested consequence and residual uncertainty. Each material finding identifies the control obligation, causal mechanism, observed outcome and verification criteria for the proposed treatment. Technical severity informs analysis; prioritisation and acceptance of residual risk remain decisions for the client’s authorised risk owner.
Coverage depends on available test positions and active services. A boundary test is not complete regulatory certification.
09 / Suitability
Commissioning criteria
Use after network redesign, new connectivity or changes affecting sensitive zone separation.
Next step
Define the assessment you need
Tell us the business decision, the systems involved and any operational constraint. We will explain the coverage proposed, the access required and the evidence the engagement can provide.
- Confidentiality first
A mutual confidentiality agreement is signed before any technical detail is exchanged, so scope discussions can happen safely.
- Scope and cost in writing
Deliverables, access expectations, timeline and fee are confirmed before the engagement begins, and a scope change needs agreement.
- Answered by the delivery team
The consultants who scope an engagement are the consultants who perform it and explain the result to your team.
