Connect. Secure. Manage.
Network Configuration Audit
Review Cisco and Meraki configurations against the intended design, highlighting inconsistent settings, unsupported assumptions and operational risks.
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 configuration audit checks whether device settings match the design and working standards you intended. We review Cisco and Meraki setups for important differences, needless exposure and changes that have lost their original purpose. Findings explain the effect and the supporting evidence. That gives your team a clear basis for deciding what to fix.
This is not an exercise in making every device look identical. Different roles can require different settings. The audit distinguishes a justified variation from an undocumented exception and a confirmed weakness from a preference that has no meaningful effect on the service.
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.
Establish the standard and the design context
We start with the setup baseline, design documents and support needs that the estate is expected to follow. Where no standard exists, the engagement can define review criteria with the network owner rather than judging the setup against an undisclosed template.
The scope identifies the devices, software and management systems involved. A setting that is appropriate on one Cisco platform may need different treatment elsewhere, and Meraki setup needs to be understood in its dashboard and template context.
Existing exceptions are reviewed for their purpose and owner. Some may be necessary for a legacy app or external connection; others may have survived long after the original need disappeared.
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
Review management and operational settings
Administrative access, authentication dependencies, logging and time settings are important parts of a maintainable network. We examine whether the setup supports the organisation’s intended access controls and investigation process.
The audit can also consider backup of the settings arrangements and the relationship between stored records and the live state. A backup that does not correspond to the running setup may provide less recovery confidence than its presence suggests.
Sensitive setup information is handled through the agreed process. Credentials and other secrets are not copied unnecessarily into a general findings report, and access to the evidence is limited to the people who need it.
A useful starting point
Tell us what is happening.
A short description of the problem is enough for an initial discussion.
Examine traffic policy and interface roles
We review the relevant routing, switching and security settings against the network’s purpose. That may include VLAN membership, trunk scope, routing policy, management separation and controls at the boundary with another network.
The emphasis is on the actual consequence. A broad policy may create more access than intended, while an overly restrictive setting may interrupt a legitimate app. The audit needs enough context to distinguish those situations.
For a Meraki estate using shared templates, the relationship between common settings and site overrides is part of the review. An apparently local inconsistency may originate in a shared setup that affects several locations.
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 ↗Identify drift and undocumented changes
Comparing the live state with the accepted baseline can reveal changes that were never incorporated into the records. We assess whether those differences are approved, still required and appropriately reflected in the design.
A difference is not automatically a defect. Emergency work may have introduced a necessary workaround, for example. But that workaround still needs an owner and a decision about its future. The audit makes that decision visible instead of allowing temporary setup to become permanent by default.
Where the underlying architecture is unclear, an architecture review may be required before a setup recommendation can be made confidently. Detailed settings should not be corrected against a design that nobody has established.
Turn findings into controlled remediation
The report prioritises material issues and explains the proposed action. It distinguishes changes that can be prepared independently from those requiring app input, vendor checks or a maintenance window.
Remediation is not automatically performed during the audit. Approved changes need their own execution and validation plan, particularly where they affect routing, authentication or access policy. A good finding should make the next engineering task clearer, not encourage an unreviewed bulk change to the settings.
After remediation, the baseline and service records should be updated. This reduces the chance that the same issue reappears because a later engineer restores an obsolete template or backup.
Configuration audit questions
Can you compare sites against a common standard?
Yes. We account for the legitimate differences between site types and make exceptions clear. The aim is meaningful consistency, not forcing specialist locations to inherit settings that were designed for an ordinary branch.
Does the audit include vulnerability scanning?
Not automatically. Configuration review and vulnerability assessment are different activities, although their findings can inform one another. Any active testing requires a defined scope, method and authorisation appropriate to the setup.
Will you remove unused rules during the review?
Not without approval and sufficient evidence. A rule that appears unused in a limited observation period may support an infrequent but important process. We identify candidates for review and the evidence needed before removal.
What do you need from us?
The intended standards, known exceptions and authorised access or setup evidence are useful. Commission a network configuration audit to establish the review boundary and how findings will be assessed with your team.
Talk to a specialist
Need a specialist view?
Tell us what is affected, what changed and what your team has already checked. A short outline is enough to start.
+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.