Connect. Secure. Manage.
Network Configuration Validation
Automate checks against approved Cisco or Meraki configuration standards, producing reviewable exceptions without making unauthorised corrective changes.
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 configuration validation compares the live Cisco or Meraki setup with approved needs. Differences are recorded for review, including deliberate exceptions that may be valid. We build checks that provide evidence for an engineer to assess. Finding a mismatch does not give the tool permission to fix a live device without approval.
Useful visibility
Monitor service-relevant conditions rather than collecting alerts without ownership.
Controlled change
Keep maintenance, automation and configuration work reviewable and recoverable.
Clear escalation
Connect incidents to the right engineering, provider and business contacts.
Define the standard being checked
We start with the customer’s approved setup needs and their purpose. These may concern management access, logging, routing policy, interface roles or a specific service design. A useful rule explains why it matters and which platforms or sites it applies to, rather than copying a large generic benchmark without context.
The standard needs an owner and a version. If the intended setup is unclear, automation cannot reliably decide whether the live estate is correct. We help separate confirmed needs from recommendations awaiting approval so the report does not present an unagreed preference as a mandatory failure.
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
Collect the right evidence safely
The collection method depends on the platform and information required. Supported APIs, structured interfaces or controlled command retrieval may be appropriate. We check that the account has sufficient read access without unnecessarily granting write privileges, and that sensitive values are handled through protected storage and reporting.
Collection completeness is checked. A failed login, truncated response or unsupported model must not produce an apparent pass simply because no contrary evidence was retrieved. The report distinguishes compliant, non-compliant, not applicable and not assessed states according to the evidence actually available.
A useful starting point
Tell us what is happening.
A short description of the problem is enough for an initial discussion.
Make checks platform-aware
Cisco operating systems and Meraki product families differ in syntax and supported functions. The validation logic maps the need to the actual platform behaviour rather than searching for one command string everywhere. An absent clear setting may represent a default, an unsupported feature or a genuine gap, and those interpretations need verification.
We also consider setup inherited from controllers or templates. The effective setting can differ from a locally visible field. Checks should assess the relevant operating model and identify where the source of truth resides, avoiding misleading findings caused by looking at only one part of the setup hierarchy.
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 ↗Manage legitimate exceptions
Some sites or services need an approved departure from the standard. We record the affected scope, reason, owner and review date so the exception remains visible without repeatedly generating an unhelpful alarm. Exceptions should not be broad permanent exclusions that conceal unrelated future changes.
The review process also identifies when an exception is no longer necessary. A temporary migration route or legacy access need may remain long after its original purpose has ended. Validation can highlight that situation, but removal still follows the customer’s approval and change process.
Separate findings from remediation
A validation report identifies evidence and recommended next steps. It does not on its own authorise a write. Some differences require investigation because changing them could interrupt an app or remove a recovery path. We keep remediation in a separate workflow with a clear scope and approval.
Where automated correction is later agreed, its pre-checks and recovery behaviour are designed for the specific need. The fact that a checker can detect a difference does not prove that a generic reverse operation is safe. This separation allows useful assurance to begin without immediately creating an estate-wide change mechanism.
Test the rules and reporting
We test known compliant and non-compliant cases, missing data, version differences and approved exceptions. False positives waste engineering time, while false passes create misplaced confidence. Representative fixtures and a limited pilot help establish that the rule measures what its description claims.
Reports include the target, rule version, evidence time and reason for the result. Sensitive setup is redacted appropriately without removing the context needed for review. The customer can trace a finding to the underlying observation rather than relying on an unexplained score or percentage.
Keep validation useful over time
Standards and platform behaviour change, so checks need ownership and maintenance. We set out how new needs are approved, how current rules are updated and how historical results are compared. A changed rule can alter a compliance percentage without any device setup changing, which should be explained clearly.
MCI can build validation within network automation or provide a focused setup review. The result supports operational assurance and prioritised remediation. But it does not certify every aspect of security or replace app testing. It gives your team a repeatable, evidence-based view of agreed network needs while preserving control over any resulting changes.
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.