Connect. Secure. Manage.
Network Vulnerability Review
Review authorised Cisco and Meraki network assets for relevant vulnerabilities, support status and exposure, then prioritise remedial work.
Devices supported
across the UK
Client locations
supported
Traffic handled
at peak time
Average
response time
Average response is not a resolution time or a contractual guarantee. Support scope and response commitments are agreed for each engagement.
A network vulnerability review checks relevant weaknesses against your actual devices and settings. We combine authorised Cisco and Meraki inventory with vendor guidance and the way each service is exposed. This helps prioritise fixes. A version listed in an advisory or a scan result is a starting point for review, rather than the full risk assessment.
Defined trust
Make access boundaries explicit rather than relying on an assumed internal network.
Controlled access
Connect identity, policy and network enforcement to the services people actually use.
Evidence for change
Test the intended security outcome and retain useful operational records.
Establish a reliable asset scope
We agree the devices, management systems, addresses and sites covered by the review. The inventory records hardware families, software versions, operational roles and ownership. Provider-managed equipment and shared infrastructure need clear permission, even where they are reachable from the customer's network.
Inventory quality affects every later conclusion. A device missing from the management system may still carry important traffic, while an old asset record may describe equipment that has already been replaced. We reconcile the agreed sources and identify gaps rather than silently treating the first spreadsheet as a complete account of the estate.
Standards & partnerships
Confidence in the team behind your network.
Cisco Partner
Cisco Meraki
Cyber Essentials
Cyber Essentials PlusMCI Network Services is operated by Proxar Ltd. Certifications apply to the certified legal entity and the scope of its certificates. View accreditation information
Match advisories to the deployed configuration
Cisco and Meraki security information is reviewed against the actual platforms and releases. Where an advisory depends on a feature being enabled or a service being exposed, we check that condition where the available evidence permits. Findings distinguish confirmed applicability from cases requiring further setup or vendor verification.
We also consider software and hardware lifecycle. An unsupported platform can create a remediation problem even when no immediate exploitable issue has been confirmed. The report explains that distinction: lifecycle risk is important. But it should not be presented as proof that a particular attack has succeeded or is possible through every interface.
A useful starting point
Not sure where to start?
Bring the requirement. We will help you define the engineering work.
Use active checks only within agreed limits
Active scanning can provide useful evidence. But it can affect fragile or operationally sensitive systems. We agree the methods, source addresses, timing and stop conditions before running tests. Credentials, when required for an authorised assessment, are handled through a suitable restricted process rather than embedded in the final report.
Where a device cannot safely be scanned, we may use setup and version evidence instead. The resulting limitation is stated clearly. A reduced-impact review does not become a full penetration test simply because the report includes security findings, and a scan that completes successfully does not prove that all relevant weaknesses have been found.
Different environments. The same care.
Built around the work
your network supports.
Finance, banking and the wider private sector. We start with the systems and people that depend on your connections.
Finance & banking
Market-data paths, routing and provider coordination on clients’ behalf.
Financial-market services ↗Offices & multi-site teams
Reliable access between people, workplaces and business applications.
Office network design ↗Data centres & cloud
Network boundaries, workload connections and operational ownership.
Data centre networks ↗Assess exposure and consequence
Prioritisation considers where the affected service is reachable, who can access it and what the device controls. An issue on a public-facing gateway may require a different response from the same issue on a tightly restricted maintenance interface. Compensating controls are considered only where their presence and relevance can be supported.
Business dependencies also influence the plan. A critical routing device may need a carefully tested upgrade even when the vulnerability warrants urgent action. We identify interim restrictions where appropriate and explain the remaining risk, rather than presenting availability and security as problems that can always be resolved independently.
Separate remediation from unsupported assumptions
A recommended software release must fit the hardware, licences and connected systems. We check the vendor's fixed-release information and the customer's compatibility needs before turning a finding into an upgrade proposal. A version that addresses one issue may introduce another operational consideration that needs testing.
Configuration mitigations are documented with their scope and limitations. Restricting access to an affected feature may reduce exposure while a permanent change is prepared. But it is not automatically equivalent to applying the vendor's fix. The customer's risk owner should be able to understand what has changed and what remains unresolved.
Produce a traceable findings register
Each finding records the affected asset, evidence, relevant reference, applicability assessment and recommended action. We avoid reproducing sensitive settings or unnecessary personal data where a narrower record is enough. The register should be usable by the engineers implementing changes and by the people deciding priorities.
False positives and uncertain results receive clear treatment. A finding closed after investigation should retain the reason, not simply disappear from the record. Similarly, an accepted risk needs an owner and review point so it is not mistaken for a completed remediation during the next assessment cycle.
Verify the change and keep the inventory current
Retesting checks the original condition after remediation and records the result. A successful upgrade job is not, by itself, proof that every affected device changed or that an exposed service is now restricted. We compare the actual post-change state with the finding and identify any remaining exceptions.
Our network security assessments can place vulnerability review within a broader setup and operational scope. MCI supports Cisco and Meraki estates across the UK, from focused edge reviews to multi-site inventories. Provide the asset scope and assessment aim, and we can agree a method that produces actionable evidence without overstating what the review can prove.
Technical references
- Cisco security technical resources — Cisco / Cisco Meraki
- Technical guide to information security testing and assessment — NIST
Talk to a specialist
What does your network need next?
Tell us what you are planning, changing or trying to improve. We will help define a practical next step and the engineering scope.
+44 203 196 6566Choose option 1
sales@proxar.co.ukUK-wide service.
Most of our engineers are based in Kent, with a focus on London, Sussex, Essex and Berkshire.
Existing customers should use their agreed support and escalation channels. This form is for service enquiries, not a monitored emergency ticket.
Tell us what you need.
A short outline is enough. Please do not include passwords or sensitive network details.
Thank you. Your enquiry has been submitted.
Please check your name, email and message, then try again.
Your form session expired. Please try again.
Please wait a minute before sending another enquiry.
We could not submit your enquiry. Please call or email us instead.