Connect. Secure. Manage.
Network Due Diligence
Assess network assets, licensing, connectivity and operational risks before an acquisition, investment or transfer of infrastructure responsibility.
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.
Network due diligence checks what you may take on before an acquisition or handover. We review assets, links, admin ownership and risks that could affect the deal or transition. The findings make important dependencies visible early. This helps the decision-makers understand the network and plan the work needed after responsibility changes.
A list of switches and firewalls is not enough. A working service may depend on a contract held by another party, an administrator account that cannot be transferred or a connection whose purpose is poorly documented. Due diligence asks whether the network can continue to be operated, supported and changed under the proposed ownership arrangement.
A clear requirement
Turn the business need into a practical network scope with visible dependencies.
A controlled delivery
Plan implementation, testing and rollback before production changes begin.
A supportable result
Leave useful records, ownership and escalation routes behind.
Define the transaction and the review boundary
The review needs to reflect the reason for the exercise. Buying a company differs from taking over a managed service or moving a business unit into a separate organisation. Each creates different questions about access, contracts, network separation and continuity.
We agree which sites, services and information sources are included. Access to the target setup must be authorised, and any restrictions are recorded. Where evidence cannot be received before a decision, the report identifies the uncertainty rather than treating an unverified answer as a clean result.
The work can focus on Cisco and Meraki infrastructure while recognising connections to other vendors, shared IT services and external providers. Those surrounding dependencies often determine whether a transition is straightforward or requires extra engineering.
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
Identify assets and the rights needed to use them
We examine the available inventory alongside ownership, support and licensing information. The practical question is not simply whether a device exists, but whether the receiving organisation will have the rights, access and support arrangements needed to operate it.
For cloud-managed setups, the organisation and administrator structure need particular attention. Hardware possession does not by itself establish control of the management setup. We find the actions and approvals needed for a legitimate handover, subject to the relevant vendor and contractual rules.
Circuit contracts, leased equipment and shared provider services also need to be visible. A connection may be technically suitable but commercially tied to an organisation that will no longer be part of the service. These matters belong in the transition dependencies, not in a late installation checklist.
A useful starting point
Not sure where to start?
Bring the requirement. We will help you define the engineering work.
Understand separation and integration risks
An acquisition may bring overlapping IP address ranges, inconsistent security controls and apps that rely on access to the seller’s systems. A divestment may require those same connections to be removed without disrupting legitimate business activity.
We review the important app and network relationships to identify where integration or separation needs deliberate design. Network merger integration can then develop the rollout plan; due diligence establishes the risks and questions that plan must address.
The review should also distinguish dependencies that are genuinely required from access that has simply accumulated. Carrying every historical route and firewall rule into a new setup can preserve unnecessary exposure and make later rationalisation harder.
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 operational readiness for the handover
We examine whether the network can be supported after the change in responsibility. Useful evidence includes diagrams, records of the settings, incident history, escalation routes and the identity of the people who currently understand the setup.
Where knowledge sits with an individual or supplier, the handover needs to capture it before access or availability changes. Documentation recovery may be a separate piece of work if the available records cannot support a safe transition.
We also identify support and lifecycle concerns that could create early expenditure. A transaction should not proceed on the assumption that everything can remain untouched when important maintenance or replacement decisions are already approaching.
Report material findings in a decision-friendly form
Technical findings are translated into their practical implications: continuity risk, transition effort, missing evidence, potential cost exposure or a dependency on another party’s approval. The report distinguishes urgent conditions from matters that can be addressed after completion.
Due diligence is not a guarantee that every latent fault has been found. The scope, evidence and limitations are part of the result. A restricted document review and a checked technical assessment should not be presented as equivalent exercises.
The deliverable can support commercial discussions and a transition plan. But it does not replace legal advice on the transaction, licence terms or contract transfer. We keep engineering conclusions separate from decisions that belong to legal and commercial advisers.
Network due diligence questions
Can the assessment happen before full access is available?
Yes, as a bounded preliminary review. We can examine supplied documents and responses, identify missing evidence and prioritise follow-up questions. Any conclusion dependent on unverified information remains clearly qualified until the relevant evidence is received.
Will you test the production network during due diligence?
Only within a clearly authorised scope. Disruptive tests are not assumed to be acceptable in a transaction review. Where live verification would improve confidence, we explain the proposed method, its risks and the approval needed.
Can you assess a managed network we do not own?
Yes. The review focuses on the service arrangement, access, duties and transition rights and the technology. Provider-owned equipment must not be treated as an asset that automatically transfers with the business.
How should we begin?
Discuss network due diligence with the type of transaction, decision timetable and broad estate involved. Sensitive transaction documents, credentials and client network information should be shared only through the agreed confidential process.
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.