EPM in MAC

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

EPM in MAC

L2 Linker

Hi Team,

I am currently working on implementing privilege management for macOS devices using CyberArk EPM in an environment where Jamf is used for device management.

I would like to understand best practices and real-world approaches followed by others who have implemented EPM for macOS.

Specifically, I am looking for guidance on the below areas:

  1. Integration & Setup
  • How is EPM typically deployed via Jamf (agent deployment, policies, prerequisites)?
  • Are there any key considerations during initial setup?
  1. Privilege Management Strategy
  • What is the recommended approach for removing local admin rights and transitioning users to standard accounts?
  • How do you handle exceptions where admin access is required?
  1. Policy Design
  • What types of applications/actions are typically allowed with elevation?
  • What categories are commonly blocked by default?
  • Do you follow publisher-based, hash-based, or path-based rules predominantly?
  1. User Experience
  • How do you balance security with user productivity?
  • Do you use justification prompts or automatic elevation for approved apps?
  1. Monitoring & Tuning
  • Do you start with audit mode before enforcement?
  • How do you fine-tune policies based on user activity?
  1. Challenges & Lessons Learned
  • What were the key challenges faced during implementation?
  • Any pitfalls to avoid, especially in a Jamf-managed environment?

Any insights, sample approaches, or implementation experiences would be really helpful.

Thanks in advance!

5 REPLIES 5

L7 Applicator

Big question

 

macOS Endpoint Privilege Manager (EPM) – Deployment Checklist

 

1. Pre-Deployment Readiness

- Confirm Jamf Pro manages all target Macs

- Validate supported macOS versions and EPM agent version

- Identify pilot users (IT & power users)

- Inventory admin-required applications and developer tools

- Communicate rollout plan to Service Desk and users

 

2. Jamf Configuration

- Upload signed EPM agent PKG to Jamf

- Create Jamf deployment policy scoped to pilot group

- Deploy required configuration profiles:

 - System Extensions

 - Full Disk Access

 - Notifications approval

 - Network permissions

- Verify agent check-in and connectivity

 

3. Initial EPM Configuration

- Enable SSO (SAML/IdP)

- Create Sets (Pilot and Production)

- Assign Pilot set to Detect/Audit Mode

- Confirm telemetry in EPM console

 

4. Privilege Strategy

- Do not remove admin rights initially

- Observe admin actions and elevation attempts

- Categorize applications and use cases

 

5. Policy Design

- Allow/Elevate:

 - Jamf and device management tools

 - Approved enterprise software

 - Apple-signed system operations

- Block:

 - Unsigned or unknown apps

 - Living-off-the-land binaries (context-aware)

 - User-writable execution paths

- Prefer publisher-based rules

 

6. User Experience

- Auto-elevate low-risk frequent apps

- Use justification prompts for high-risk actions

- Provide clear user messaging and Service Desk escalation

 

7. Remove Local Admin Rights

- Ensure policy coverage is complete

- Remove admin rights from Pilot users

- Monitor for 7–14 days

- Roll into Production

 

8. Monitoring & Tuning

- Review events daily

- Add allow rules for legitimate blocks

- Tighten broad rules

 

9. Operational Guardrails

- Define break-glass access

- Document common elevations

- Configure exclusions for other security tools

- Align upgrade cadence

 

10. Go-Live Success Criteria

- 95%+ Macs without local admin

- Minimal user prompts

- Stable agent health

- Service Desk readiness

 

L5 Sessionator

Hi @Sumitha Sudheer​ ,

 

You can also see macOS best practices in our online docs here - https://docs.cyberark.com/epm/latest/en/content/landingpages/lpmacos-best-practices.htm

 

 

Thanks,

L4 Transporter

Hi @Sumitha Sudheer​ 

Two of our community members have shared answers to your question. Could you let us know if any of these resolved your issue?

If so, please mark the appropriate answer as “Select as Best” to help other members find the solution easily.

If the issue remains unresolved, I recommend submitting a ticket with our support team for further assistance.

Thank you,

Shaked

L2 Linker

Hi everyone,

We currently have Elevate on Windows configured with source URL–based controls, including URL whitelisting (e.g., for URL-1). If needed, could we implement the same functionality on Mac as well?

Please let me know if this is feasible or if any additional details are required.

Thanks,

Sumitha

L2 Linker

For the MAC OS, Only support the trust policy for Publisher's signature and Software distributor type only

 

Online Doc : https://docs.cyberark.com/epm/latest/en/content/epm/server%20user%20guide/trustpolicies-newui.htm#Trusted2

  • 90 Views
  • 5 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!