Who rated this post

cancel
Showing results for 
Search instead for 
Did you mean: 
the_rock
MVP Gold
MVP Gold

FWIW, straight from our "friend", chatgpt 🙂

Andy

************************************************

ChatGPT said:

Yes, Check Point does not have a traditional NAC (Network Access Control) solution like Cisco ISE, Aruba ClearPass, or FortiNAC. However, Check Point offers some endpoint and network access control capabilities through its broader security portfolio and does support integration with third-party NAC solutions.

🔐 What Check Point Provides (Directly):

  1. Identity Awareness (IA)

    • Core feature on Check Point gateways (including Spark appliances like the 1800).

    • Allows user-based policies by integrating with AD, LDAP, RADIUS, etc.

    • Can map IPs to users/devices.

  2. Harmony Endpoint / Harmony Connect

    • Endpoint control, posture checks, and compliance.

    • Not true NAC but helps control what devices/users can access what, based on endpoint state.

  3. IoT Protect / Asset Management for IoT

    • Can fingerprint and control IoT assets (but again, not a full NAC suite).


Third-Party NAC Integrations (More Complete NAC Capability)

You can enhance NAC capabilities on Spark 1800s by integrating Check Point with third-party NAC solutions, like:

NAC Solution Integration Quality Notes
Cisco ISE Good Use RADIUS integration + pxGrid (for sharing user/device context). Identity Awareness can pull user context from ISE.
Aruba ClearPass Good Similar to Cisco ISE; supports RADIUS and TACACS. Check Point can consume context via Identity Awareness.
Portnox Moderate Cloud-native NAC. Integrates via RADIUS. Useful in SMB/midmarket where Spark appliances are deployed.
Forescout CounterACT Good Passive & agentless. Can tag and enforce on devices. Integrates via API and RADIUS.
FortiNAC Basic Not commonly integrated with Check Point, but possible via RADIUS and logs.

🔧 How Integration Typically Works

  1. RADIUS Authentication

    • The NAC solution acts as RADIUS server.

    • Spark 1800 authenticates users via the NAC.

    • NAC enforces access policies.

  2. Syslog/API Context Sharing

    • Some NACs send user/IP/device metadata to Check Point via syslog or APIs.

    • Check Point’s Identity Awareness consumes that metadata to apply user-aware policies.

  3. Posture Check + Quarantine VLANs

    • NAC can isolate non-compliant devices before they reach the Spark firewall.

    • Spark then enforces firewall policies after NAC authorizes the device.


📦 For Spark 1800 Use Case

Given that Spark appliances are branch/SOHO-oriented, heavy-duty NACs like ISE or ClearPass might be overkill unless you already use them elsewhere. Consider:

  • Portnox CLEAR – Cloud NAC, scalable, SMB-friendly.

  • Aruba ClearPass OnGuard Lite – Lightweight posture/NAC control.

  • Cisco ISE – Only if enterprise-wide and you need strong endpoint posture.

  • Check Point + Harmony Endpoint – If you're also using Harmony Mobile or Endpoint, posture can be partially enforced.


🧠 Recommendation Strategy

If you want a light NAC enhancement for Spark 1800s, propose:

  • Portnox or ClearPass for NAC,

  • Check Point Identity Awareness + Harmony Endpoint (for posture and integration),

  • Use RADIUS authentication on Spark + Identity Awareness to pull NAC metadata.

View solution in original post

(1)
Who rated this post