<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Can CyberArk CPM Auto‑Detection: Support for Rule-Based Automation? in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/can-cyberark-cpm-auto-detection-support-for-rule-based/m-p/1416257#M86638</link>
    <description>&lt;P&gt;CyberArk Onboarding Decision &amp;amp; Change Overview (DCO)&lt;/P&gt;&lt;P&gt;1. Purpose&lt;/P&gt;&lt;P&gt;This document outlines the decision regarding the use of Auto-Detection (CPM-based) versus Account Discovery Rules for onboarding privileged accounts in CyberArk.&lt;/P&gt;&lt;P&gt;2. Background&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;3. Problem Statement&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;4. Key Findings&lt;/P&gt;&lt;P&gt;- Auto-Detection is process/technology-driven, not logic-driven.&lt;/P&gt;&lt;P&gt; - No support for conditional onboarding based on naming, type, or environment.&lt;/P&gt;&lt;P&gt; - Discovery Rules support IF/THEN logic and fine-grained policy control.&lt;/P&gt;&lt;P&gt; - Service governance and compliance requirements cannot be fully met with Auto-Detection alone.&lt;/P&gt;&lt;P&gt;5. Options Considered&lt;/P&gt;&lt;P&gt;Option 1: Continue with Auto-Detection&lt;/P&gt;&lt;P&gt; - Pros: Simple, quick deployment&lt;/P&gt;&lt;P&gt; - Cons: Limited control, no conditional logic&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt; Option 2: Hybrid Approach&lt;/P&gt;&lt;P&gt; - Pros: Combines detection visibility with rule-based onboarding&lt;/P&gt;&lt;P&gt; - Cons: Slightly more complex setup&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt; Option 3: Full Discovery Rules Adoption&lt;/P&gt;&lt;P&gt; - Pros: Full control, scalable, governance-aligned&lt;/P&gt;&lt;P&gt; - Cons: Requires design and maintenance effort&lt;/P&gt;&lt;P&gt;6. Recommended Approach&lt;/P&gt;&lt;P&gt;Adopt a hybrid model: Use Auto-Detection for initial account discovery and visibility. Use Discovery Rules for controlled onboarding, Safe assignment, and platform mapping.&lt;/P&gt;&lt;P&gt;7. Implementation Plan&lt;/P&gt;&lt;P&gt;- Enable Auto-Detection for visibility of technologies.&lt;/P&gt;&lt;P&gt; - Design Discovery Rules based on naming conventions, account types, and platforms.&lt;/P&gt;&lt;P&gt; - Map rules to Safes, platforms, and CPM policies.&lt;/P&gt;&lt;P&gt; - Test onboarding scenarios across environments.&lt;/P&gt;&lt;P&gt; - Gradually reduce reliance on Auto-Detection for onboarding actions.&lt;/P&gt;&lt;P&gt;8. Risks &amp;amp; Mitigations&lt;/P&gt;&lt;P&gt;Risk: Incorrect rule configuration&lt;/P&gt;&lt;P&gt; Mitigation: Test in non-production environment&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt; Risk: Over-onboarding or missed accounts&lt;/P&gt;&lt;P&gt; Mitigation: Monitoring and reporting&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt; Risk: Operational complexity&lt;/P&gt;&lt;P&gt; Mitigation: Standardised rule design and documentation&lt;/P&gt;&lt;P&gt;9. Conclusion&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;</description>
    <pubDate>Mon, 15 Jun 2026 10:54:53 GMT</pubDate>
    <dc:creator>RobertS_Cyberark</dc:creator>
    <dc:date>2026-06-15T10:54:53Z</dc:date>
    <item>
      <title>Can CyberArk CPM Auto‑Detection: Support for Rule-Based Automation?</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/can-cyberark-cpm-auto-detection-support-for-rule-based/m-p/1416256#M86637</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;I’m working on CyberArk onboarding and had a query on the &lt;B&gt;Auto‑Detection (CPM-based) feature&lt;/B&gt;.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Does Auto‑Detection support &lt;B&gt;rule-based automation&lt;/B&gt; (like IF/THEN in Discovery rules)?&lt;/LI&gt;&lt;LI&gt;Can we configure &lt;B&gt;conditional onboarding&lt;/B&gt; (based on account type, naming, platform, etc.)?&lt;/LI&gt;&lt;LI&gt;Or is it limited to &lt;B&gt;CPM parameters&lt;/B&gt; (processes, machine sets, detection methods) without flexible rule logic?&lt;/LI&gt;&lt;LI&gt;If not supported, what’s the recommended way to achieve this using &lt;B&gt;Account Discovery rules&lt;/B&gt;?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;We are evaluating whether to continue with Auto‑Detection or move fully to Discovery rules. Any guidance or best practices would help.&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jun 2026 08:51:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/can-cyberark-cpm-auto-detection-support-for-rule-based/m-p/1416256#M86637</guid>
      <dc:creator>Sridhar18</dc:creator>
      <dc:date>2026-06-11T08:51:01Z</dc:date>
    </item>
    <item>
      <title>Re: Can CyberArk CPM Auto‑Detection: Support for Rule-Based Automation?</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/can-cyberark-cpm-auto-detection-support-for-rule-based/m-p/1416257#M86638</link>
      <description>&lt;P&gt;CyberArk Onboarding Decision &amp;amp; Change Overview (DCO)&lt;/P&gt;&lt;P&gt;1. Purpose&lt;/P&gt;&lt;P&gt;This document outlines the decision regarding the use of Auto-Detection (CPM-based) versus Account Discovery Rules for onboarding privileged accounts in CyberArk.&lt;/P&gt;&lt;P&gt;2. Background&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;3. Problem Statement&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;4. Key Findings&lt;/P&gt;&lt;P&gt;- Auto-Detection is process/technology-driven, not logic-driven.&lt;/P&gt;&lt;P&gt; - No support for conditional onboarding based on naming, type, or environment.&lt;/P&gt;&lt;P&gt; - Discovery Rules support IF/THEN logic and fine-grained policy control.&lt;/P&gt;&lt;P&gt; - Service governance and compliance requirements cannot be fully met with Auto-Detection alone.&lt;/P&gt;&lt;P&gt;5. Options Considered&lt;/P&gt;&lt;P&gt;Option 1: Continue with Auto-Detection&lt;/P&gt;&lt;P&gt; - Pros: Simple, quick deployment&lt;/P&gt;&lt;P&gt; - Cons: Limited control, no conditional logic&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt; Option 2: Hybrid Approach&lt;/P&gt;&lt;P&gt; - Pros: Combines detection visibility with rule-based onboarding&lt;/P&gt;&lt;P&gt; - Cons: Slightly more complex setup&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt; Option 3: Full Discovery Rules Adoption&lt;/P&gt;&lt;P&gt; - Pros: Full control, scalable, governance-aligned&lt;/P&gt;&lt;P&gt; - Cons: Requires design and maintenance effort&lt;/P&gt;&lt;P&gt;6. Recommended Approach&lt;/P&gt;&lt;P&gt;Adopt a hybrid model: Use Auto-Detection for initial account discovery and visibility. Use Discovery Rules for controlled onboarding, Safe assignment, and platform mapping.&lt;/P&gt;&lt;P&gt;7. Implementation Plan&lt;/P&gt;&lt;P&gt;- Enable Auto-Detection for visibility of technologies.&lt;/P&gt;&lt;P&gt; - Design Discovery Rules based on naming conventions, account types, and platforms.&lt;/P&gt;&lt;P&gt; - Map rules to Safes, platforms, and CPM policies.&lt;/P&gt;&lt;P&gt; - Test onboarding scenarios across environments.&lt;/P&gt;&lt;P&gt; - Gradually reduce reliance on Auto-Detection for onboarding actions.&lt;/P&gt;&lt;P&gt;8. Risks &amp;amp; Mitigations&lt;/P&gt;&lt;P&gt;Risk: Incorrect rule configuration&lt;/P&gt;&lt;P&gt; Mitigation: Test in non-production environment&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt; Risk: Over-onboarding or missed accounts&lt;/P&gt;&lt;P&gt; Mitigation: Monitoring and reporting&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt; Risk: Operational complexity&lt;/P&gt;&lt;P&gt; Mitigation: Standardised rule design and documentation&lt;/P&gt;&lt;P&gt;9. Conclusion&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Mon, 15 Jun 2026 10:54:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/can-cyberark-cpm-auto-detection-support-for-rule-based/m-p/1416257#M86638</guid>
      <dc:creator>RobertS_Cyberark</dc:creator>
      <dc:date>2026-06-15T10:54:53Z</dc:date>
    </item>
  </channel>
</rss>

