Sample Network & Security Assessment
A proof-of-work example showing how VALO evaluates network reliability, segmentation, firewall controls, and remediation priorities.
This is not a client case study. The organization, systems, findings, metrics, and risk values below are fictional and exist only to demonstrate the structure and level of detail of a VALO deliverable.
Executive context
Example organization: Oak Ridge Family Clinic, a fictional single-site clinic with 55 users, one next-generation firewall, three managed switches, nine wireless access points, two internet circuits, six VLANs, and cloud-hosted business applications.
Objective: assess reliability, segmentation, firewall/access controls, administrative exposure, wireless isolation, core services, and HIPAA-relevant network risks.
Sample findings
| ID | Finding | Priority | Impact | Recommended action |
|---|---|---|---|---|
| N-01 | Clinical workstations and general business endpoints share an overly broad trusted VLAN. | High | Compromise of one endpoint increases lateral-movement exposure. | Design role-based segmentation and restrict inter-VLAN flows to documented business requirements. |
| N-02 | Firewall rulebase contains stale any/any service objects and rules without current business owners. | High | Unnecessary network paths increase attack surface and weaken accountability. | Validate rule ownership, remove stale rules, narrow services, and document recurring review. |
| N-03 | Network-device administration is reachable from standard user networks. | High | User-endpoint compromise could expose network management interfaces. | Create a management segment and restrict administration by source, protocol, and authorized identities. |
| N-04 | Guest wireless isolation is incomplete from selected internal RFC1918 ranges. | High | Guest devices may reach internal services not intended for public access. | Enforce firewall isolation, validate ACLs, and retest from guest clients. |
| N-05 | Configuration backups are manual and not verified after network changes. | Moderate | Recovery from hardware failure or configuration error may be delayed. | Automate configuration backup and periodically test restore procedures. |
Example architecture priorities
0–30 days
- Restrict management-plane access.
- Correct guest-network isolation.
- Review high-risk firewall rules.
- Capture current configs and topology.
31–60 days
- Implement segmentation changes.
- Standardize switch management controls.
- Improve configuration backup.
- Review DNS/DHCP dependencies.
61–90 days
- Retest segmentation.
- Validate failover process.
- Document network standards.
- Close findings with evidence.
Flat-fee qualification illustrated
This fictional environment fits the published $2,500 package because it is one small site with a limited device inventory and conventional architecture. A multi-site estate, data center, SD-WAN environment, large switch/AP population, complex BGP/OSPF, NAC/ISE deployment, cloud transit architecture, or major redesign would be custom-scoped instead.
Need a clear picture of your network risk?
We define the scope before work begins so you know the deliverables, boundaries, timeline, and fee.
Request a network assessment