Managed Firewall
Define which connections are allowed and who maintains the rules.
A managed firewall applies controls between networks within agreed scope. To delegate operations, start with necessary flows and change approval.
Scope, logs, changes, high availability and shared responsibilities must be defined.
Let’s talk
How it works
Turn security policy into rules that can be operated and reviewed.
Internal zones
Managed firewall
Authorised destinationsWho can communicate with whom
Define zones, sources, destinations and applications. The firewall applies policy to traffic crossing it; NAT and VPN belong only where included in the design.
Managed does not mean the provider knows every business permission. Assign a rule owner, change approval and exception review.
Internal zones
Managed firewall
Authorised destinationsMeasure with inspection enabled
Useful throughput and latency depend on traffic, sessions and enabled controls. Review logs, resources and rule matches before disabling protections for a slow application.
Distinguish a correct block from a false positive. An exception needs a reason, scope and review, not a permanently open rule.
Internal zones
Managed firewall
Authorised destinationsKeep security during recovery
A device pair and session synchronisation may form part of a high-availability design. Validate routes, power and behaviour when a node fails.
Test legitimate access and rejection of unauthorised traffic after failover. A bypass allowing everything does not restore protection.
Illustrative case: from situation to decision
- Situation
- A new site needs one application without opening access to the rest of the network.
- Option
- Define source, destination and service, with approval and rollback owners.
- Check
- Test the permitted flow and access that must stay blocked; review logs.
Inspection features, firewall location and high availability depend on the contracted service.
Decisions for your project
- Policy
- Zones, flows, NAT/VPN and each rule’s owner.
- Sizing
- Sessions, inspected throughput, logs and agreed retention.
- Operations
- Changes, escalation, high availability and tests using the same policy.
From design to operation
Review rules and dependencies; migrate with permitted/rejected flow tests and controlled rollback.
Complements, alternatives and variants
Product sources
What challenge would you like to solve?
Tell us what is happening and what needs to change. You do not need to know the catalogue.
What happens next?
- Understand the context
What’s changing, where your teams work and what cannot fail. Still defining the brief? We can help structure it.
- Design the options
Bring needs, Colt capabilities and technical criteria together. Compare alternatives and explain dependencies and limits.
- Validate before committing
Coverage, feasibility, responsibilities and terms. A commercial proposal is developed with the relevant specialists.
ColtPlatinum guides the project and coordinates commercial discussions and follow-up. Colt validates feasibility, enters into the service contract, and provisions, installs and delivers the services.
Availability, coverage, capabilities, SLAs and timelines are subject to technical validation and contract. No diagram is a service guarantee.