Aruba

SSL-VPN with Fortinet Firewall with Ping ID MFA and ClearPass OnGuard Health Check

Overview SSL-VPN with Multifactor Authentication that verifies that Legitimate user has connected to the network with Second Factor of Verification The Health Check of the End-Client makes sure that Only Compliant user are allowed onto the network The Setup Involves below components Fortinet Firewall as SSL-VPN Concentrator ClearPass Policy Manager and ClearPass OnGuard LDAP/AD Ping

SSL-VPN with Fortinet Firewall with Ping ID MFA and ClearPass OnGuard Health Check Read More »

SSL-VPN With Endpoint Posture Compliance Check in Fortinet VPN and Aruba ClearPass Environment

Introduction With the current pandemic situation most of the employees are working from home by using the VPN connections to their enterprise network. Since the employees are connecting over public network and using their personal devices, it poses a great security risk to respective enterprises. To mitigate this issue, we are integrating Fortinet VPN solution

SSL-VPN With Endpoint Posture Compliance Check in Fortinet VPN and Aruba ClearPass Environment Read More »

Using Clearpass as an Accounting Proxy server

Clearpass can be used as an accounting proxy to pass on accounting packets from your NAD devices to an external server like a firewall.etc.   Purpose: ClearPass Integration with Fortinet through Radius Accounting (RSSO) would provide the User Data Flow Analysis from user perspective instead of IP address or MAC Address.   Check out the

Using Clearpass as an Accounting Proxy server Read More »

Aruba MPSK implementation per user instead of per device

Introduction:   Aruba MPSK was introduced in the AOS release 8.4.x, a feature using which you can leverage the use of different PSK’s for different devices. The traditional approach is well documented in the link below: https://community.arubanetworks.com/t5/Security/Setting-up-MPSK-for-headless-IoT-devices/td-p/522858   Need for per user MPSK:   We at Airowire Networks had the privilege of working with a

Aruba MPSK implementation per user instead of per device Read More »

Why is it a bad idea to use port 389 for LDAP communication between Clearpass and your Active Directory?

What is LDAP: LDAP stands for Lightweight Directory Access Protocol. As the name suggests, it is a lightweight client-server protocol for accessing directory services, specifically X.500-based directory services. LDAP runs over TCP/IP or other connection-oriented transfer services. LDAP is defined in RFC2251 “The Lightweight Directory Access Protocol (v3).   Connection between LDAP and Clearpass: On

Why is it a bad idea to use port 389 for LDAP communication between Clearpass and your Active Directory? Read More »

Scroll to Top