- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
06-11-2026 01:51 AM
Hi Team,
I’m working on CyberArk onboarding and had a query on the Auto‑Detection (CPM-based) feature.
We are evaluating whether to continue with Auto‑Detection or move fully to Discovery rules. Any guidance or best practices would help.
06-15-2026 03:54 AM
CyberArk Onboarding Decision & Change Overview (DCO)
1. Purpose
This document outlines the decision regarding the use of Auto-Detection (CPM-based) versus Account Discovery Rules for onboarding privileged accounts in CyberArk.
2. Background
CyberArk provides two primary methods for onboarding accounts: CPM-based Auto-Detection and Discovery Rules. Auto-Detection identifies accounts based on technologies and processes, while Discovery Rules allow flexible, condition-based onboarding.
3. Problem Statement
Auto-Detection lacks support for rule-based logic (IF/THEN conditions), limiting the ability to apply granular onboarding criteria. This results in reduced control over account classification, Safe assignment, and platform mapping.
4. Key Findings
- Auto-Detection is process/technology-driven, not logic-driven.
- No support for conditional onboarding based on naming, type, or environment.
- Discovery Rules support IF/THEN logic and fine-grained policy control.
- Service governance and compliance requirements cannot be fully met with Auto-Detection alone.
5. Options Considered
Option 1: Continue with Auto-Detection
- Pros: Simple, quick deployment
- Cons: Limited control, no conditional logic
Option 2: Hybrid Approach
- Pros: Combines detection visibility with rule-based onboarding
- Cons: Slightly more complex setup
Option 3: Full Discovery Rules Adoption
- Pros: Full control, scalable, governance-aligned
- Cons: Requires design and maintenance effort
6. Recommended Approach
Adopt a hybrid model: Use Auto-Detection for initial account discovery and visibility. Use Discovery Rules for controlled onboarding, Safe assignment, and platform mapping.
7. Implementation Plan
- Enable Auto-Detection for visibility of technologies.
- Design Discovery Rules based on naming conventions, account types, and platforms.
- Map rules to Safes, platforms, and CPM policies.
- Test onboarding scenarios across environments.
- Gradually reduce reliance on Auto-Detection for onboarding actions.
8. Risks & Mitigations
Risk: Incorrect rule configuration
Mitigation: Test in non-production environment
Risk: Over-onboarding or missed accounts
Mitigation: Monitoring and reporting
Risk: Operational complexity
Mitigation: Standardised rule design and documentation
9. Conclusion
Auto-Detection alone is insufficient for enterprise-scale onboarding. Discovery Rules provide the required flexibility, control, and compliance alignment. A hybrid approach offers the best balance between discovery and governance.
06-15-2026 03:54 AM
CyberArk Onboarding Decision & Change Overview (DCO)
1. Purpose
This document outlines the decision regarding the use of Auto-Detection (CPM-based) versus Account Discovery Rules for onboarding privileged accounts in CyberArk.
2. Background
CyberArk provides two primary methods for onboarding accounts: CPM-based Auto-Detection and Discovery Rules. Auto-Detection identifies accounts based on technologies and processes, while Discovery Rules allow flexible, condition-based onboarding.
3. Problem Statement
Auto-Detection lacks support for rule-based logic (IF/THEN conditions), limiting the ability to apply granular onboarding criteria. This results in reduced control over account classification, Safe assignment, and platform mapping.
4. Key Findings
- Auto-Detection is process/technology-driven, not logic-driven.
- No support for conditional onboarding based on naming, type, or environment.
- Discovery Rules support IF/THEN logic and fine-grained policy control.
- Service governance and compliance requirements cannot be fully met with Auto-Detection alone.
5. Options Considered
Option 1: Continue with Auto-Detection
- Pros: Simple, quick deployment
- Cons: Limited control, no conditional logic
Option 2: Hybrid Approach
- Pros: Combines detection visibility with rule-based onboarding
- Cons: Slightly more complex setup
Option 3: Full Discovery Rules Adoption
- Pros: Full control, scalable, governance-aligned
- Cons: Requires design and maintenance effort
6. Recommended Approach
Adopt a hybrid model: Use Auto-Detection for initial account discovery and visibility. Use Discovery Rules for controlled onboarding, Safe assignment, and platform mapping.
7. Implementation Plan
- Enable Auto-Detection for visibility of technologies.
- Design Discovery Rules based on naming conventions, account types, and platforms.
- Map rules to Safes, platforms, and CPM policies.
- Test onboarding scenarios across environments.
- Gradually reduce reliance on Auto-Detection for onboarding actions.
8. Risks & Mitigations
Risk: Incorrect rule configuration
Mitigation: Test in non-production environment
Risk: Over-onboarding or missed accounts
Mitigation: Monitoring and reporting
Risk: Operational complexity
Mitigation: Standardised rule design and documentation
9. Conclusion
Auto-Detection alone is insufficient for enterprise-scale onboarding. Discovery Rules provide the required flexibility, control, and compliance alignment. A hybrid approach offers the best balance between discovery and governance.
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!

