Multi-context firewalls - what are they and what do they do?
Just six weeks into the new year and reports of cyber-attacks are rife in the media. According to IT Governance, a provider of cyber risk and privacy management solutions, several major incidents occurred in January, boosting the total number of records breached to 1.5bn.
Just yesterday, ZDNet reported that the personal information of 10.6 million guests who stayed at MGM Resorts hotels was stolen and posted to a hacking forum this week. Already in February, the servers at the United Nations have been compromised and a quarter of the Iranian internet has been disrupted.
In addition, Christine Lagarde, the head of the European Central Bank, has expressed her concerns about the global implications of cyber-attacks, telling an audience in France that a well-organised cyber-attack on major financial institutions could lead to a financial crisis.
So, what should businesses be doing about this? Cyber security is one of our focus areas at Franklin Fitch and as a recruiter, I am frequently asked by service providers and large enterprises to find people with experience in multi-context firewalls. Quite often when I ask candidates if they have used them, the response is: “what is that? “or “I’ve never heard of it”.
For me personally, a lot of my technical knowledge is gained from in-depth conversations with my candidates about how they use a specific piece of hardware and what benefits it brings. So, if you, like me, are wondering what multi-context firewalls are, read on and find out more.
Cisco ASA supports multiple firewall contexts, also called firewall multimode or multi-context mode. Multi-context mode divides a single ASA into multiple virtual devices, also known as security contexts. Each context operates a single device, independently from other security contexts. In routers, this is similar to Virtual Routing and Forwarding (VRF).
When would you use multiple security contexts?
A network that requires more than one ASA
A service provider that needs to offer a different security context to each customer
An enterprise that needs to provide distinct security policies for each individual department or users and require a different security context for each one
When wouldn’t you use multiple security contexts?
When VPN Services are required such as remote access or site-to-site VPN tunnels
If dynamic routing protocols are required
If QoS is needed
If multicast routing needs to be supported
If threat detection is required
Context configuration files
In multi-context mode, there are three types of configuration files:
The system configuration – a standard single-mode configuration where the network administrator adds and manages the security contexts
The admin context – no restrictions and can be used as any other security context
The context configurations/user context – for each individual security context. They contain the security policies and interface configurations specific only to that context
ASA Packet Classification
Packets are also classified differently in multi-context firewalls. In multimode configuration, it is possible for interfaces to be shared between contexts, therefore the ASA must distinguish which packets need to be sent to each context.
The ASA categorises packets based on three criteria:
Unique interfaces – 1:1 pairing with a physical link or sub-interfaces (VLAN tags)
Unique MAC addresses – shared interfaces are assigned Unique Virtual Mac addresses per virtual context, in order to alleviate routing issues, which complicates firewall management
NAT configuration – if the use of unique MAC addresses is disabled, then the ASA uses the mapped addresses in the NAT configuration to classify packets. This isn’t very common
In certain cases, you may need to assign a unique MAC address to a shared interface in order to alleviate routing issues, which complicates the firewall management.
Multi context mode offers active/active fail-over per context. Primarily forwards for an individual context and secondary for another. The security contexts divide logically into failure groups, with a maximum of two failure groups. There will never be two active forwarding paths at the same time.
Important to consider
In order to change from single mode to multiple mode or back, the commands must be done from the command line (CLI) and not via the ADSM GUI interface. When changing from single to multimode, the ASA will convert the running configurations into two files, creating a new system configuration file and an admin context file. The original system configuration file is not saved.
By default, all security contexts have unlimited access to the ASA resources. Depending on the environment, resource management may need to be configured to limit some contexts that may be starving other contexts. This is done by configuring resource classes when assigning to contexts.
Multimode offers advantages in certain situations particularly for service providers or an enterprise with multiple departments that require individual security policies. The requirements should be carefully considered before implementing the solution. However, there are also limitations and whilst the number of physical devices you manage may decrease, the complexity of those device configurations may increase.
We pride ourselves on trusted partnerships, whether you're looking for a new role in IT Infrastructure, talent for your team or considering joining Franklin Fitch. Why not start that partnership today?
Copyright © 2019 Franklin Fitch | All rights Reserved. Designed by Venn Digital
Or if you prefer email your CV to email@example.com
Please indiciate whether you would like us to hold onto your details in order to keep you up to date with relevant opportunities