- Products
- Learn
- Local User Groups
- Partners
- More
What’s New in Device Diagnostics?
Dec 2nd @ 5pm CET / 11am EST
AI Security Masters
Security in the Pace of AI:
From Threat to Force Multiplier
CPX is Back!
Join us in Las Vegas, Vienna, and/or Bangkok!
Check Point Named a Leader
The Forrester Wave:
Enterprise Firewall Solutions, Q4 2026
What’s New in Agentic Network Orchestration
CheckMates Go:
Fun Ding
Hi Mates,
Is there any documentation available regarding PAM (Privileged Access Management) on Check Point?
Thanks in advance!
What is your needs about PAM?
The customer authenticates to the firewall using both HTTPS and SSH.
However, the challenge is that when the customer initiates a connection through the PAM to access the firewall, a different set of credentials is used.
But I suppose you can store admin credential in your PAM solution, and when the user logs into PAM, when it connects to the firewall the admin credentials are used.
Hello, @RemoteUser
Regarding your question about integrating a Privileged Access Management (PAM) solution with Check Point, we reviewed the current product documentation (R82) to verify how administrator authentication is handled and how user identities are recorded during administrative sessions.
Based on the official documentation, Check Point does not provide a native PAM integration that preserves or records the identity of the original user authenticated by a third-party PAM solution (such as CyberArk, BeyondTrust, Delinea, Wallix, etc.) when establishing administrative connections over SSH, HTTPS (WebUI), or the Management API.
Check Point always authenticates the credentials that are presented during the connection.
In a typical PAM deployment, the administrator first authenticates against the PAM platform using their corporate identity (for example, Active Directory credentials with MFA). After successful authentication, the PAM solution retrieves a privileged account from its secure vault and uses that account to establish the administrative session with the Check Point device.
Administrator
│
▼
PAM Solution
(CyberArk / BeyondTrust / Delinea / etc.)
│
│ User authenticates with corporate credentials
▼
PAM retrieves privileged credentials
│
▼
SSH / HTTPS / API
│
▼
Check Point Gateway or Security Management ServerFrom the Check Point perspective, the authenticated identity is the privileged account that actually connects to the system (for example admin, cpadmin, or another administrative account).
Since the original corporate identity is authenticated only by the PAM platform and is not transmitted as part of the standard SSH or HTTPS authentication process, Check Point has no native mechanism to associate that identity with the administrative session.
This behavior is expected and aligns with the responsibilities of each component.
As a result:
According to the official R82 Security Management Administration Guide, administrator authentication can be configured using supported authentication mechanisms such as:
The documentation does not describe a native authentication mechanism capable of receiving, preserving, or displaying the original identity authenticated by an external Privileged Access Management solution during SSH, HTTPS, or API administrative sessions.
Based on the official Check Point documentation, the behavior observed in your environment is the expected behavior.
When an administrative session is initiated through a third-party PAM solution, Check Point authenticates only the privileged account presented during the connection. The original user identity remains managed by the PAM platform, which is responsible for maintaining the complete audit trail and correlating the end user with the privileged account used during the session.
If preserving end-user identity inside Check Point audit logs is a business requirement, this functionality is currently not documented as a native capability of Check Point Security Management. The recommended approach is to rely on the auditing and session recording features provided by the PAM solution itself.
We hope this clarifies the expected behavior. If you have additional questions regarding your specific PAM implementation or would like to discuss possible deployment alternatives, please let us know and we'll be happy to assist.
Best regards,
Jorge Dias Junior.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 9 | |
| 9 | |
| 7 | |
| 6 | |
| 6 | |
| 6 | |
| 5 | |
| 4 | |
| 3 | |
| 3 |
Tue 24 Nov 2026 @ 01:30 PM (GMT)
La nueva realidad de los ataques DDoS: autonomía, escala y el futuro de la defensaWed 02 Dec 2026 @ 03:30 PM (GMT)
The New DDoS Reality: Autonomy, Scale, and the Future of DefenseTue 24 Nov 2026 @ 01:30 PM (GMT)
La nueva realidad de los ataques DDoS: autonomía, escala y el futuro de la defensaWed 02 Dec 2026 @ 03:30 PM (GMT)
The New DDoS Reality: Autonomy, Scale, and the Future of DefenseAbout CheckMates
Learn Check Point
Advanced Learning
WE SECURE YOUR AI TRANSFORMATION