Cisco & Meraki specialists. Across the UK.
+44 203 196 6566 · option 1sales@proxar.co.uk

Connect. Secure. Manage.

Managed Firewall Services

Arrange ongoing management of Cisco or Meraki firewalls, covering approved policy changes, operational monitoring and clearly scoped support responsibilities.

Cisco Partner since 2009 Projects & ongoing support

Illustrative Cisco and Meraki fibre network rack with structured cabling
Look beyond the alarm.Evidence first. Controlled next steps.
1,000+

Devices supported
across the UK

20+

Client locations
supported

Nearly 8 Tbps

Traffic handled
at peak time

3 min

Average
response time

Average response is not a resolution time or a contractual guarantee. Support scope and response commitments are agreed for each engagement.

Managed firewall services keep agreed Cisco and Meraki firewall rules under controlled care. We define access, change approval, monitoring and escalation for the covered devices. The scope also identifies the other services the firewalls rely on. Broader security operations remain separately agreed, and no firewall service can promise to prevent every incident.

01

Useful visibility

Monitor service-relevant conditions rather than collecting alerts without ownership.

02

Controlled change

Keep maintenance, automation and configuration work reviewable and recoverable.

03

Clear escalation

Connect incidents to the right engineering, provider and business contacts.

Establish the policy and platform baseline

We inventory the appliances, management systems, software, licences and relevant support arrangements. The review identifies interfaces, routing, VPNs and the apps relying on the firewall. An inherited ruleset often contains temporary or poorly described entries, so understanding its purpose is part of onboarding rather than an optional future exercise.

We also establish who owns the risk decisions behind policy. The customer approves business access needs and exceptions, while MCI assesses and implements the agreed technical change. A management service should not make the supplier the unrecorded approver of every connection simply because it has admin access.

Illustrative Cisco and Meraki network operations centre with monitoring displays
01Visibility, monitoring and operational control.
Cisco PartnerCisco Partner
Cisco MerakiCisco Meraki
ISO 9001Quality management
ISO 27001Information security
Cyber EssentialsCyber Essentials
Cyber Essentials PlusCyber Essentials Plus

MCI Network Services is operated by Proxar Ltd. Certifications apply to the certified legal entity and the scope of its certificates. View accreditation information

Make rule requests specific

A useful request identifies sources, destinations, services, business purpose and any expiry or review need. We help distinguish a real app need from an unnecessarily broad permission. Address translation, routing and return traffic are considered alongside the access rule so the change does not solve only one part of the connection.

The change record states how the result will be tested and how it can be reversed. Emergency access may follow an expedited approval route. But it still needs an owner and follow-up. Temporary rules should not become permanent merely because the original incident has been closed.

Illustrative Cisco and Meraki equipment in a modern data-centre aisle
02Resilient infrastructure from rack to service path.

A useful starting point

Tell us what is happening.

A short description of the problem is enough for an initial discussion.

Talk to a specialist

Monitor operation and relevant security events

Monitoring can check device health, ports, VPNs and the state of backup units. Handling security events depends on the licensed features, available data and agreed scope. We state which records are collected and who reviews them. We also define which events need escalation. Collecting every log does not mean someone investigates it around the clock.

A managed firewall service is not automatically a full security operations centre. Threat hunting, endpoint response and broader incident containment require their own tools, authority and coverage. Where those services are provided by another team, the firewall process defines how evidence and approved actions move between the parties.

Illustrative Cisco and Meraki data-centre network infrastructure
03Network infrastructure designed around the workloads it carries.

Investigate incidents across the traffic path

A blocked or failed app can involve policy, routing, NAT, identity, DNS or a remote service. We trace representative traffic and compare observed behaviour with the intended rule. The aim is to identify the actual cause without opening broad access simply to see whether the problem disappears.

Diagnostic information can contain personal or confidential data. We agree the scope and handling of captures and logs, retaining only what is necessary for the investigation. TLS inspection and other sensitive features are treated as clear design and governance decisions, not enabled as a routine troubleshooting shortcut.

Illustrative Cisco and Meraki equipment in organised data-centre racks
04Data-centre connectivity with clear physical and logical boundaries.

Maintain software, licences and resilience

Maintenance planning reviews supported releases, security advisories, feature compatibility and upgrade paths for the actual platform. We agree a change window and validation plan, recognising that high availability does not on its own make every software change non-disruptive. Vendor support and licence dependencies are recorded alongside the technical setup.

Resilience testing considers session behaviour, upstream routing and connected switches and the firewall pair. A standby appliance can be healthy while a shared dependency still creates a single point of failure. Monitoring should identify lost resilience before a second event interrupts the service.

Illustrative Cisco and Meraki network rack in a modern office
05The office network: switching, uplinks and structured cabling.

Review policy quality over time

Regular reviews can find old rules, unused objects and exceptions with no recorded purpose. We propose changes using evidence and input from app owners. A short period with no traffic is not enough reason to remove a rule. The service may run only during recovery or a scheduled business task.

Reporting should connect firewall activity to decisions: recurring blocked apps, risky exceptions, capacity pressure or overdue maintenance. Raw event counts alone provide little assurance. We agree review frequency and ownership so recommendations lead to controlled action rather than another unattended report.

Illustrative Cisco and Meraki fibre network rack with structured cabling
06Fibre, switching and the physical path behind the service.

Agree the service boundary

MCI supports Cisco and Meraki firewalls across the UK, as a standalone arrangement or part of managed networks. The proposal identifies supported assets, change allowances, monitoring, service hours, escalation and customer approvals. Application administration, carrier repair and wider security response are stated separately.

An initial inventory and outline of your current policy-management problems are enough to begin scoping. Do not send passwords or full sensitive settings through a public form. We arrange appropriate access after defining the work, keeping operational convenience and security accountability aligned throughout the service.

Illustrative Cisco and Meraki network operations centre with monitoring displays
07Visibility, monitoring and operational control.

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 6566

Choose option 1

sales@proxar.co.uk

UK-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.

We’ll use these details to respond to your enquiry. Please leave out passwords and sensitive network information. Read our privacy notice.