Context-based access control
Context-based access control (CBAC) is a feature of
CBAC can be configured to permit specified TCP and UDP traffic through a firewall only when the connection is initiated from within the network needing protection. (In other words, CBAC can inspect traffic for sessions that originate from the external network.) However, while this example discusses inspecting traffic for sessions that originate from the external network, CBAC can inspect traffic for sessions that originate from either side of the firewall. This is the basic function of a stateful inspection firewall.[2]
Without CBAC, traffic filtering is limited to
CBAC inspects traffic that travels through the firewall to discover and manage state information for TCP and UDP sessions. This state information is used to create temporary openings in the firewall's access lists to allow return traffic and additional data connections for permissible sessions (sessions that originated from within the protected internal network).
CBAC works through deep packet inspection and hence Cisco calls it 'IOS firewall' in their Internetwork Operating System (IOS).
CBAC also provides the following benefits:
- Denial-of-serviceprevention and detection
- Real-time alerts and audit trails
See also
- Access control list
- Attribute-based access control (ABAC)
- Discretionary access control (DAC)
- Graph-based access control (GBAC)
- Lattice-based access control (LBAC)
- Mandatory access control (MAC)
- Organisation-based access control (OrBAC)
- Role-based access control (RBAC)
- Rule-set-based access control (RSBAC)
- Capability-based security
- Risk-based authentication
References
- ^ "Context-Based Access Control". TechTutsOnline. 2015-09-11. Retrieved 2019-05-22.
- ^ "Context-Based Access Control (CBAC): Introduction and Configuration". Cisco. Retrieved 2019-05-22.
- ^ "Context-Based Access Control (CBAC)". Danscourses. 2012-03-09. Archived from the original on 2017-03-27. Retrieved 2019-05-22.