Tuesday, 8 May 2012

Context-based access control

Context-based access control (CBAC) intelligently filters TCP and UDP packets based on application layer protocol session information that are not specifically denied by an ACL and can be used for intranets, extranets and internets. 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.
With CBAC inspection rules, you can configure alerts and audit trail information on a per-application protocol basis. It generates real-time alerts and audit trails. Audit trails uses system log to track all the networking transaction. It can also mitigate Denial of Service (Dos) and detection which is essential for every computer.
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.


mod7_fig8.png (946×360)

Every computer will have access to network, regarding work, surfing internet and so on. CBAC will check every packets that is in traffic. With CBAC, CBAC can examines the application-layer protocol information to learn about the state of TCP or UDP session. This ensures that our application are not downloading or allowing people to gain access to our computer through these applications.

1 comment:

  1. it's great to know more about context-base access control. i also learn that it can be only permit specified TCP and UDP Traffic through a firewall. also learn that it can be configure alerts to track if there is any hacker doing it. hope to see more of this. this is interesting content that i had read. keep it up!

    ReplyDelete