Home / cybersecurity / CyberArk Defender – PAM (PAM-DEF) / Cheat Sheet
CyberArk Defender – PAM (PAM-DEF)

PAM-DEF Cheat Sheet

PAM-DEF Tests Where Each Setting Lives — Safe, Platform or Master Policy

Defender-PAM is for administrators who run an existing CyberArk deployment day to day. Stop asking what CyberArk can do and start asking which component, safe permission or policy rule does it.

Check Your Readiness →
Among the harder certs
Avg: Not published by CyberArk
Pass: 750 / 1000
Most candidates understand CyberArk Defender – PAM (PAM-DEF) concepts — and still fail. This exam tests how you apply knowledge under pressure.

CyberArk Defender-PAM Study Guide Domains (2023)

CyberArk publishes no weights; Configure and Manage Passwords has the most objectives (16). Stems pair a business requirement or symptom with a configuration location. Since November 2025 CyberArk exams are delivered in person only. Question count and timing come from third-party sources.

  1. 01
    Onboard Accounts (weight not published) — discovery, pending list, onboarding rules, bulk upload, usages
  2. 02
    Manage the Application (weight not published) — Vault, PVWA, CPM, PSM roles, TCP 1858, System Health, REST API
  3. 03
    Ongoing Maintenance and Troubleshooting (weight not published) — isolating a failing component, break/fix vs. services
  4. 04
    Configure and Manage Passwords (weight not published) — Master Policy, dual control, logon vs. reconcile, platforms, CPM assignment
  5. 05
    Security and Audit Functions (weight not published) — inventory, compliance, entitlements and activity reports, recordings, Blueprint
  6. 06
    Configure Session Management (weight not published) — isolation, recording and Connect rules, HTML5 Gateway, connection components
  7. 07
    Configure User Management (weight not published) — Vendor PAM invitations, access windows, outbound connector

Wrong instinct vs correct approach

Windows discovery found 200 local admin accounts, and new member servers are built every month
✕ Wrong instinct

Prepare a bulk upload file and rerun it monthly

✓ Correct approach

Schedule recurring discovery and create an automatic onboarding rule that sends matching accounts into the right safe and platform. Bulk upload is a one-time import of a known list and misses accounts created later.

Password changes stopped yesterday, yet users still reach the PVWA and open PSM sessions
✕ Wrong instinct

Restart the Vault server to reset all components

✓ Correct approach

Rotation is the CPM's job, so check System Health, the CPM service and CPM logs first. A rebuilt server with a mismatched credential file is a classic cause; restarting the Vault only widens the outage.

Auditors need proof of which admin used a shared account and want retrieved passwords useless afterwards
✕ Wrong instinct

Enable dual control so a manager approves each request

✓ Correct approach

Approval proves authorisation, not possession. Exclusive access locks the account to one user at a time, and one-time password access changes it after release, giving non-repudiation and killing reuse.

An outsourced support firm uses a VPN account and one shared Vault user for all engineers
✕ Wrong instinct

Keep the VPN and add per-engineer Vault users

✓ Correct approach

Use Vendor PAM: individual invitations, mobile strong authentication, time-boxed access windows, sessions brokered and recorded by the PSM, and an outbound-only connector, so no VPN or inbound firewall rules.

Know these cold

  • ▸ Safe controls who and which CPM; platform controls how; Master Policy controls workflow
  • ▸ Components connect to the Vault on TCP 1858; users reach the PVWA over HTTPS
  • ▸ PVWA submits the request; the CPM actually verifies, changes and reconciles on the target
  • ▸ CPM assignment is per safe — o assigned CPM means no automatic rotation
  • ▸ Logon account fixes logon bans; reconcile account fixes passwords changed outside CyberArk
  • ▸ Link usages before rotating service accounts so services, tasks and app pools update
  • ▸ Onboard by risk — omain admins, built-in local admin and root before bulk low-risk accounts
  • ▸ Reports show only safes the requester can see; fix scope through safe membership
  • ▸ Live monitoring needs PSMLiveSessions membership, not Vault administrator rights
  • ▸ Restoring lost function is break/fix for Support; upgrades and redesigns are services engagements

Can you answer these without checking your notes?

In this scenario: "Windows discovery found 200 local admin accounts, and new member servers are built every month" — what should you do first?
Schedule recurring discovery and create an automatic onboarding rule that sends matching accounts into the right safe and platform. Bulk upload is a one-time import of a known list and misses accounts created later.
In this scenario: "Password changes stopped yesterday, yet users still reach the PVWA and open PSM sessions" — what should you do first?
Rotation is the CPM's job, so check System Health, the CPM service and CPM logs first. A rebuilt server with a mismatched credential file is a classic cause; restarting the Vault only widens the outage.
In this scenario: "Auditors need proof of which admin used a shared account and want retrieved passwords useless afterwards" — what should you do first?
Approval proves authorisation, not possession. Exclusive access locks the account to one user at a time, and one-time password access changes it after release, giving non-repudiation and killing reuse.

Common Exam Mistakes — What candidates get wrong

Linking a reconcile account when root simply cannot log on over SSH

A logon account solves connection restrictions: the CPM logs on with it, then switches to root. A reconcile account only resets a password that drifted out of sync. Each must be linked to the account explicitly.

Assuming PSM isolation automatically produces session recordings

Monitoring and isolation, record and save session activity, and transparent connections (the Connect button) are three separate Master Policy rules. Sessions can route through the PSM with recording switched off.

Editing a shipped platform to change policy for a handful of accounts

Every account on that platform inherits the change. Duplicate the platform and assign the subset to the copy. Master Policy exceptions are likewise set per platform, never on an individual account object.

Granting retrieve to users who should only connect through the PSM

Use lets a safe member launch a session; retrieve lets them show or copy the password, which defeats isolation. Auditors need list plus view audit, never retrieve, for entitlement and activity reports.

Treating accounts in the pending list as protected

Discovered accounts sit unmanaged until onboarded into a safe with an active platform. Only then does the CPM verify and rotate. Onboarding rules act on discovery results; they never scan targets themselves.

Resources to help you pass CyberArk Defender - PAM on your first attempt

Defender-PAM asks where each control is configured. Check whether you can place them all.