Skip to main content

NAC Version 4.1(3)

4.1.3 is available and you can download it here:

Cisco NAC Appliance Software Download Page
Requires a valid Smartnet contract in order to download
























4.1.3 Release Notes
As with all NAC Upgrades, the release notes are extremely important!

4.1.3 CAM Installation & Configuration Guide

4.1.3 CAS Installation & Configuration Guide

Enhancements in Release 4.1(3)

General Enhancements

• Cisco NAC Web Agent

• Support for Clients with Multiple Active NICs

• Clean Access Server HA Heartbeat Link Enhancement

• Clean Access Manager HA Configuration and Heartbeat Link Enhancements

• Guest User Login and Registration Enhancements

• LDAP Authentication Enhancement

• Clean Access Server and WSUS Interaction Enhancement

• Agent Restricted User Access Enhancement

• Device Filter List Display and Import/Export Enhancement

• Agent Report Information Display and Export Enhancement

• VPN SSO Login Enhancement

• Syslog Configuration Enhancement

• Debug Log Download Enhancement

• cisco_api.jsp Enhancement

• CSRF Protection

• Proxy Support Enhancements

• ARP Broadcast Packet Handling Improvement

• Clean Access Server HA ARP Broadcast Enhancement

• Deprecated "Retag Trusted-side Egress Traffic with VLAN (In-Band)" Feature

• Previously-Deprecated Features Removed from CAM/CAS Web Console Pages

• Supported AV/AS Product List Enhancements (Version 67)

Out-of-Band Enhancements

• Access to Authentication VLAN Change Detection Enhancement

• SNMP Inform Notification Enhancement

• SNMP "MAC Move Notification" Switch Port Configuration Support

Clean Access Agent Enhancements

• Clean Access Agent Auto Remediation

• Windows Clean Access Agent Version 4.1.3.0

• Mac OS X Clean Access Agent Version 4.1.3.0


Look out for more detailed explainations and configuration examples from the new features and functionality.
Labels:

Comments

Post a Comment

Popular posts from this blog

Intrusion Prevention Best Practice - IPS Placement

Background In today's organizations, attacks come from everywhere. As cliche as it sounds, networks are borderless and because of this organizations face more sophisticated threats. As networks evolve, many organizations struggle to have intrusion prevention or other security architecture evolve at the same pace. Visibility is everything: you must be able to detect and respond to threats before they cause significant damage. The following entry is all about how to gain visibility at the different areas of the network. IPS Overview Wikipedia defines Intusion Prevention Systems as a "network security appliance that monitor network and/or system activities for malicious activity. The main functions of intrusion prevention systems are to identify malicious activity, log information about said activity, attempt to block/stop activity, and report activity." By deploying IPS, organizations are able to identify, classify, and stop malicious traffic, including worms, spyware ...
4 comments
Read more

Cisco Releases Idenity Services Engine (AKA ISE)

Introduction After years of innovation around Network Access Control, Cisco has released its next generation NAC solution: Identity Services Engine. ISE is combines existing loosely coupled devices AAA, profiling, posture and guest management - in single, scalability appliance. As part of the Cisco TrustSec solution and Cisco’s SecureX architecture for Borderless Networks, the Cisco Identity Service Engine provides a centralized policy engine for business relevant policy definition and enforcement. This policy work horse enables centralized, coordinated policy creation and consistent policy enforcement across the entire corporate infrastructure, from head office to branch office. ISE Features & Benefits Visibility: Single Platform & Pane of Glass - Let IT see who and what is on the network for advanced discovery and troubleshooting Dynamically collects & consolidates endpoint information to make adaptive policy decisions based on ‘context’ Integrates functions previously d...
7 comments
Read more

Why are Virtual Private Networks and Software Defined Perimeters mutually exclusive?

Increased remote work, vulnerabilities popping up and the #killthevpn movement has the cyber security industry laser focused on the transition from VPN to SDP. Let’s start with an acceptable definition of SDP from Wikipedia: “Software-defined perimeter (SDP) framework was developed by the Cloud Security Alliance (CSA) to control access to resources based on identity. Connectivity in a Software Defined Perimeter is based on a need-to-know model, in which device posture and identity are verified before access to application infrastructure is granted.” I hope we all can agree that the “ground truth" of SDP is valid and any organizations will benefit by adopting SDP architecture and principals(including Zero Trust). How is a Remote Access VPN any different than the “Client-to-gateway” deployment model defined for SDP? “In the client-to-gateway implementation, one or more servers are protected behind an Accepting SDP Host such that the Accepting SDP Host acts as a gateway between ...
7 comments
Read more