Connect. Secure. Manage.
Palo Alto Firewall Integration
Connect existing Palo Alto firewalls to Cisco or Meraki networks, validating routing, NAT and policy handoffs without duplicating firewall responsibilities.
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.
Palo Alto firewall integration connects a retained security platform to a Cisco or Meraki network without losing sight of traffic paths and policy ownership. MCI helps plan and validate the surrounding routing, segmentation and operational handoffs. The purpose is to make the combined service work as intended, not to replace a specialist firewall strategy simply because the rest of the network uses another vendor.
This work may form part of a campus refresh, a data-centre change or the introduction of a new external connection. We establish which team owns the firewall and which decisions belong to the network project before changing either side.
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.
Map the traffic that must cross the firewall
The starting point is the application requirement: source, destination, direction and the reason communication is permitted. We relate that requirement to the existing network segments and the firewall’s role in the path.
A design should identify the expected return traffic as well as the outward route. Address translation, multiple uplinks and alternative paths can make the apparent connection different from the path actually used.
We do not assume that allowing a destination on one control proves the entire service is correctly configured. Routing, policy and application behaviour need to be considered together.
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
Preserve the security boundary during network change
A new switch, route or network segment can alter which traffic reaches a firewall. The project should make clear which connections must continue to pass through inspection and which should remain isolated.
We review the intended attachment and routing arrangement with the firewall owner. Any change that would bypass an existing control needs an explicit security decision, not a quiet workaround to make an application test succeed.
The integration record distinguishes network changes from firewall policy changes. This helps maintain a clear approval trail when separate teams have different access and responsibilities.
A useful starting point
Not sure where to start?
Bring the requirement. We will help you define the engineering work.
Examine availability and path changes
Where the firewall operates within a resilient design, the surrounding network needs to support the intended recovery behaviour. We assess the relevant connections and the paths traffic may take after a failure.
The existence of duplicate devices does not by itself prove that an application will recover as required. The test plan should consider the service, the allowed failure conditions and any limits on what can be exercised safely.
Observations are recorded with their scope. A successful test of one path change should not be presented as proof of every possible failure combination across the network and security environment.
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 ↗Plan evidence and supplier coordination
Logs, interface information and controlled traffic observations can help establish where a connection is failing. The useful evidence depends on which team can see each part of the path.
Where a problem requires deeper inspection, packet analysis can be scoped with the firewall and application owners. Collection authority and information handling are agreed before potentially sensitive traffic is captured.
Manufacturer support remains subject to the relevant entitlement and ownership. MCI can participate in technical coordination where agreed without implying an official Palo Alto Networks relationship or unlimited responsibility for every security feature.
Hand over a connection that can be maintained
The finished record should describe the network boundary, relevant addressing and route decisions, test results and change owners. It should also identify where later application changes need security review.
A mixed estate becomes harder to support when each team has only its own diagram and no shared account of the handoff. We aim to leave enough common information for future changes and incidents to be coordinated sensibly.
For a new or changing firewall connection, describe the objective through our contact page. Our Cisco and Meraki network services can then be aligned with the retained Palo Alto platform and your existing security responsibilities.
Palo Alto integration questions
Will you redesign all of our firewall policies?
Not automatically. Policy design or remediation can be a separate scope from network integration. We identify the policies relevant to the proposed connection and agree which team is responsible for assessing or changing them.
Can you help when one direction of traffic works?
Yes. The investigation considers routing, translation, policy and the observations available on both sides. A one-direction symptom can have several explanations, so we test the relevant path rather than make a blanket assumption about the cause.
Does integration make the network compliant?
No. A working connection or reviewed security boundary is not a certification of regulatory or contractual compliance. The work can provide useful technical evidence, but wider obligations and independent assessments remain separate matters.
Can the firewall remain with our security provider?
Yes, where access and responsibilities are clear. We can coordinate the Cisco or Meraki network side while your provider retains the firewall. Joint acceptance tests are important because neither team’s individual configuration proves the complete service.
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.