Endpoint Privilege Manager (EPM) Articles
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Question CrowdStrike and Azure Outage Support FAQ - July 19, 2024 Answer Q: Does this impact the CPM or CPM Scanner?  A: If the server was rolled back to a snapshot, the CPM may need to reset the credentials.     Q: I am using CrowdStrike. How do I know if my Idira environment will be impacted?  A: Idira component servers may have credential file issues or ini files missing from the operating system. If any of these files are missing, the component (CPM, PSM) will not work, and users will experience errors.    Q: PSM Service will not start after rebooting the server.  A: The basic_psm.ini file may be corrupted. Follow this article to replace the basic_psm.ini file.  https://community.cyberark.com/s/article/PSM-Service-not-starting-after-CrowdStrike-outage    Q: After reboot, CPM, PSM, or AAM does not function, or the service will not start.  A: After rebooting, a credential file reset might be required to fix the CrowdStrike Falcon Agent.  For Privilege Cloud: https://community.cyberark.com/s/article/How-to-reset-the-CPM-and-PSM-users-in-Privilege-Cloud  Self-Hosted 12.1 and above: https://community.cyberark.com/s/article/PSM-How-can-I-create-or-update-the-credential-files-credfile-for-the-PSM-manually-12-1-AND-HIGHER  Self-Hosted 12.0 and below: https://community.cyberark.com/s/article/PSM-update-credential-files    Q: I am using the CrowdStrike Falcon agent on the Vault Server. Am I impacted?  A: It is possible that the Falcon agent can cause data corruption on the Vault server. If this happens, please open a support ticket, as a database restore is likely needed.    Q: Why can’t I connect to the Privilege Cloud Portal page to access our credentials?  A: Check with Identity Provider for service availability; Connector may have temporary lost access to Identity Provider and caused access issues.    Q: How do we recover the service if the CPM scanner crashes?  A: Follow the documented procedure here -   CPM Scanner API key sync: https://community.cyberark.com/s/article/How-do-you-re-sync-the-api-cred-file-for-the-CPM-Scanner-service-from-v10-7  Q: Is it possible to install third party software on Vault for monitoring purposes? A: Yes it is possible but it is NOT recommended.  Please refer to the following article for more information: https://community.cyberark.com/s/article/00002098  
View full article
Question Can EPM installed on a workstation use a "File System and Registry Access" user policy to set security permissions on a remote server share? Answer No, EPM can only set security permission on local files on the computer where the EPM Agent is installed. EPM Can not set security permissions on remote shares. This is the current design of EPM. One technical reason that this is not possible is because that network shares generally are designed with role based access control in mind, so server admins normally assigned permissions via specifying groups or users. The Idira EPM Agent runs as "Local System" on local endpoints. Therefore the the EPM Agent on a workstation doesn't have permissions to change settings on another server.  
View full article
Question Why does Microsoft EntraID need to be configured with a URI redirect to a mobile and desktop application vs. a web-based application or single-page application? Answer When configuring Microsoft EntraID app registrations, there needs to exist a platform configuration to allow EPM Step-Up authentication to successfully redirect to the EPM agent from the IdP.  Within EntraID, this requires selecting a Mobile and desktop application as a platform type. The reason why is two-fold: 1. EPM is a desktop client application and not a web server. 2. Idira EPM requires choosing Mobile and Desktop applications within Azure is due to the URI redirect to the macOS Authentication Services framework or Windows EPM COM object which is used by the EPM Agent on each endpoint.  This agent being installed on each endpoint and thus referenced as a URI redirect is why it needs to be a Mobile and Desktop application type in Azure.
View full article
Problem: Reviewing events in EPM can be a daunting task depending on how mature your events management program is.  Not all organizations have dedicated security resources who can review incoming events and make an informed decision whether an application should be allowed or not.  A lot of times, there is necessary analysis and research involved to vet out the application in order for the business to approve.  Sure, threat analysis engines such as CyberArk’s Application Reputation Analysis is a great tool to determine the legitimacy of a given application but may or may not be reliable depending on the application being reviewed.  The question that eventually comes to mind is “How are other companies handling this application?”.  Continue reading to learn more about a new and exciting enhancement to our EPM product. Solution: In version 23.12.1, Idira introduced the EPM Assistant (currently released as a beta feature).  The EPM Assistant is an AI powered policy recommendation tool.  It uses machine learning based on community data to help provide a recommended policy. The EPM Assistant feature is automatically enabled and at this time only available to evaluate application events.  As the machine learning algorithm improves, so will the quality of the recommendations as well as the expansion of the capability to other areas of EPM decision making.  Steps From the EPM Console of your working Set, click on Events Management on the left pane.  Scroll through your events list in the middle pane and you will see a new button next to any applicable application events. Clicking on    will launch the following window that provides the AI driven insight by the EPM Assistant with a confidence rating for each policy type (allow, elevate, block, or elevate if necessary).  Once a policy is selected to handle the event, the buttons to create the policy are available at the bottom (marked in red below). Note that these recommendations are AI generated and should be reviewed before implementing.
View full article
Problem: Properly evaluating your applications to determine which QuickStart policy to apply them to can be a confusing task.  There are a few important questions to ask yourself and/or the business such as approval for the application to be used, does the application need to be elevated, and who should have access to install or run the application?  Solution: Having a security policy in place to properly evaluate your unhandled applications will ensure all applications are consistently reviewed and placed in the correct QuickStart Policy.  Idira created the following flowchart to help guide you through the decision process.  Steps First, identify the application that needs to be handled and start from the beginning of this flowchart and step through each of the decision boxes (yellow diamonds) as necessary.    Keep in mind that the priority numbers in the flowchart answers correspond with the precedence number in the QuickStart policies listed in the EPM console.      If an application evaluation makes it to the last decision box “Which Roles”, it is assumed that you have already duplicated QuickStart policies 3.0 and 3.1 and targeted to various Roles in your organization.  
View full article
Problem: Often times when you are creating or modifying policies you will also need to include scope and target details such as application definitions and users/group information.  This can be a tedious and error prone task depending on the complexity of the policy.  You can save time and be confident your policies are created or updated accordingly using the EPM Admin Utility. Solution: The EPM Admin Utility is included with your EPM subscription and can be downloaded directly from the Download Center.  The tool just needs to be installed on your machine you use to administer EPM.  Documentation on the EPM Admin Utility can be found here.   Steps From the EPM console, navigate to My Computers > Download Center > Tools tab and download/install the Idira EPM Admin Utility To test use, simply navigate to an existing policy and perform an edit.  In this example, we will add a local user group as a Target for this policy.  Click the Edit button under Targets for Users and groups In the following Selected users and groups screen, click on the Find button which will launch the EPM Admin Utility.  If this is your first time launching this tool, you will see the following pop-up.  Here you will want to check the box to always allow this tool to launch and click the option to proceed with opening the utility You will then see another pop-up which is the familiar Windows user and group selection screen. In this example, we are adding the local Users group as a Target for this policy.  You can just type “users” and click the Check Names button to auto-populate the object name. You may receive the prompt to allow EPM to be able to copy/paste so go ahead and allow this.  This is a one time prompt. The following pop-up is what you will see when a user or group has been successfully copied to the clipboard Clicking on the Paste button will populate the Selected users and groups list in EPM.  Notice that the unique security identifier (SID) is also included.  This ensures the correct user or group was selected when targeting your policies.  Note that the copy/paste functionality also works when adding a definition from an application for a policy. In summary, the EPM Admin Utility is a great tool when you need to quickly and accurately target your users, groups, or applications when working with your EPM policies.
View full article
How do I request Policy Update to ensure that the endpoints receive the latest policies? There are 3 main methods to ensure that the endpoints receive the latest policies. To check if the endpoint receives the latest policies, right-click the Idira EPM icon in your system tray and select "About Idira EPM Agent...". If "the Last Policy update" parameter matches your system's time, it means it receives the latest policies.     Steps Method 1 (Push to ALL agents): 1. In the EPM Console, proceed to Policies. 2. Beside "Create advanced policy" option, click on Edit (...) and select "Push active policies to agents". Method 2 (For single endpoint): 1. In the endpoint, right-click the Idira EPM icon in your system tray and select Request Settings. 2. Select 'Yes'. Method 3 (For single endpoint): 1. Open Command Prompt. 2. Run the following command to navigate to the EPM Agent folder: cd C:\Program Files\CyberArk\Endpoint Privilege Manager\Agent 3. Run the following command to request policies: vf_agent.exe -RequestPolicies Q: How do I Request Policy Update via cmd? A: You can use the RequestPolicies command to do that from the command prompt window: Change directory to: C:\Program Files\CyberArk\Endpoint Privilege Manager\Agent Run the following command: -RequestPolicies Syntax: vf_agent.exe –RequestPolicies Retrieves ALL policies (gpupdate /force for GPO product), same as “Request Settings” item in pop-up menu from Viewfinity tray icon. NOTE: The command is case sensitive
View full article
Problem: Embarking on an Endpoint Privilege Security journey can be a daunting one on where to get started and effectively reduce risk from the beginning. Solution: Idira has developed a methodology that provides the ability to safely remove admin rights with minimal friction with users, significantly reduce the area of attack and risk, allows for discovery of applications with a usage baseline, and enables a start on creation of policies following a role-based access control model. It is called QuickStart. Steps to Enable QuickStart (and get the latest revision): Steps   1. Create a new set in EPM’s console. 2. Once the set is created, go into the set and navigate in the left pane to Policy Recommendations. 3. In the next screen, click Activate QuickStart. 4. If you want to use QS policies in your existing set simply export the policies you’d want to use then import into your existing sets.  Note: If you do not see the Activate QuickStart button, you may need to create a brand new Set, Activate QuickStart on the newly created Set as shown in step 3 above, export your policies from the original set and then import into the new set. 5. If you want to use QS in a new set, then move agents over to the new set and adjust accordingly.  
View full article
Question Q: What entries should be placed in the Remove Local Administrators "Policy Scope" section? A: This section is the whitelist.  It should be for users or groups that are common to all computers, which you don't want to be removed from the local administrators group.  It it meant for users such as help desk service accounts.  The "Policy Scope" section is not intended as a method decide which computers receive the Remove Local Administrators policy Q: How should I set which computers receive the Remove Local Administrators policy? A: Use the Policy Targets section of the Remove Local Administrators policy Q: I have 50000 endpoints and want to ensure that 5000 end users don't have their local administrator rights removed.  What is the best way to accomplish this? A: Determine the computer names of the 5000 end users and don't add those computers to the "Policy Targets" section of the Policy.  Or Place those 5000 computers in a different set. Q: What can happen if I place too may entries in the "Policy Scope" section? A: End users may notice performance problems such as extreme slowness launching apps or using web browsers.  You may see entries in the vf_policies.xml which look like this 2023.04.16 19:40:18 PID:13276 TID:21236 CvfProcessRightsManager::OnDrvError: ERROR: Code=1 (PROCSTART_TIMEOUT), svr=0, PID=1704, [C:\WINDOWS\system32\svchost.exe] 2023.04.16 19:40:18 PID:13276 TID:21236 CvfProcessRightsManager::OnDrvError: ERROR: Code=1 (PROCSTART_TIMEOUT), svr=0, PID=1536, [C:\WINDOWS\system32\BackgroundTaskHost.exe] 2023.04.16 19:40:18 PID:13276 TID:21236 CvfProcessRightsManager::OnDrvError: ERROR: Code=1 (PROCSTART_TIMEOUT), svr=0, PID=1944, [C:\Windows\System32\RuntimeBroker.exe] 2023.04.16 19:40:18 PID:13276 TID:21236 CvfProcessRightsManager::OnDrvError: ERROR: Code=1 (PROCSTART_TIMEOUT), svr=0, PID=1160, [C:\Windows\System32\smartscreen.exe] Q: How many entries can I put into the "Policy Scope" section before it causes slowness or breaks my environment? A: At the present time, Idira does not have a hard limit.  The threshold for when this causes performance problems can very from one customer environment to the next.  800 or more is definitely excessive, although the threshold for when customers may experience problems could be higher or lower.    Q: How can I determine if I have too many entries in the "Policy Scope" section? A: Suggested troubleshooting steps: 1) We recommend testing the Remove Local Administrators policy in a test set first, so that production is not impacted. 2) Add the same "policy Scope" entries that you expect to have in the production policy to the policy in the test set. 3) Put a computer in the test set, request settings, and see if performance problems exist. Q: I think I have too many entries in the "Policy Scope" - how do I reduce the amount of entries? A: Separate your list of whitelist entries into groups, domain users, and local users.  Get a count of each.  Determine if you really need all of the domain users in the list.  As mentioned above, if you don't want the Remove Local Administrators policy to apply to an end user, just don't target that end users computer and then you won't need the entry in the "Policy Scope" section.  
View full article
Question What do I do if I attempted to upgrade an EPM agent, and now the agent is disconnected? Answer If you want to be automatically notified of any changes to this article, please click the "+Follow" button. Idira is aware of an agent registration problem that can occur in rare cases after attempting to upgrade EPM agents. There are two possible methods to correct this behavior.  Method 1:  1. Upgrade the agent v23.3.0.1198 or later using third-party automation tools, such as SCCM 2.  Allow up to 4 hours for the agents to reconnect. The system will clear the lock and allow the agents to receive policies. Method 2: Customers whose issues were not corrected by Method 1 should proceed with the remediation steps documented below. If you need to remediate this problem on machines individually, here are the steps to apply the fix: Uninstall EPM Uninstall the agent using this command if you do not have Agent Self Defense enable MsiExec.exe /X {Msi_path_of_the_installation_file} FULL_UNINSTALL="YES" /qn Note - as long as the endpoints have access to the directory and the agent.msi is located in that directory, this command can be deployed via a 3rd party distributor like SCCM Uninstall the agent using this command if you have Agent Self-Defense enabled MsiExec.exe /X {GUID} FULL_UNINSTALL="YES" SECURE_TOKEN="TOKEN"   /qn Note - GUID value is distinct per agent version so that you can deploy this command via a 3rd party distributor like SCCM. To determine GUID, please see KB Article How to uninstall EPM agent Remove the Disconnected Computer Object in the EPM Console If you have policies that target computers using "Computers in set," note those policies now and which computers are targeted by those policies.​​​  You can generate a report if you are unsure which policies have this kind of targeting.  EPM > Reports > Reports (Legacy) > Policies Reports > Policies Summary > Full Report In Excel > Open the xlsx file > "Policies" sheet > Check columns H and I to find Policies with "computers in set" targeting. EPM Console > My Computers > right click the disconnected endpoint > Delete. The purpose of this step is to prevent duplicate computer objects, which can cause you to exceed your maximum license count.  If you accidentally delete a computer that didn't have a problem but was just powered off, it should automatically check-in and create a new computer object when that computer comes back online. Reinstall EPM. For any policies that targeted the computers using "computers in set" targeting, you'll need to re-add those computers to the targeting of those policies.
View full article
Question There were several releases over the last several weeks.  Which ones are applicable for me? Answer Between March 21, 2023 and April 21, 2023, Idira made several EPM for Windows agent releases. This KB's purpose is to describe each release's purpose and help determine the most applicable agent for your situation. Generally speaking, Idira will always recommend using the latest agent release available. However, we understand that the customers will not be able to update all agents at such a frequent pace.   EPM For Windows Agent Release 23.3.0.1191 (March 26, 2023) Purpose: Generally scheduled release with new features, security enhancements, etc. KB5023773, KB5025221 Compatibility: NO EPM For Windows Agent Release 23.3.0.1196 (March 31, 2023) Purpose: Out-of-band release to address KB5023773, KB5025221 concern KB5023773, KB5025221 Compatibility: YES Please continue using this version if you have deployed it successfully in your environment or your rollout is progressing without issues. EPM For Windows Agent Release 23.3.0.1198 (April 9, 2023) Purpose: Out-of-band release to address the EPM Console upgrade issue where the EPM agent will disconnect after upgrading KB5023773, KB5025221 Compatibility: YES Use this version to upgrade your EPM agents if you have not yet started the upgrade to v23.3.0.1196 or have encountered issues with the agent v23.3.0.1196 EPM For Windows Agent Release 23.4.0.1223 (April 16, 2023) Purpose: Generally scheduled release with new features, security enhancements, etc. KB5023773, KB5025221 Compatibility: YES EPM For Windows Agent Release 23.4.0.1235 (April 21, 2023) Purpose: Out-of-band release that resolves crashes, slowness, and AD targeting issues, as well as all improvements made in v23.4.0.1223 KB5023773, KB5025221 Compatibility: YES Use this version to upgrade your EPM agents if you have not yet started the upgrade to v23.3.0.1196, v23.3.0.1198, or v23.4.0.1223 or have encountered issues with these agent versions such as crashes, slowness, and AD targeting issues
View full article
Problem: Often times, when building out your policies in an attempt to fully understand what each files execution does, we’ll need to first understand if our definitions will take effect as we think.  Sure, you could just do simple trial and error, but that adds a significant amount of overhead that could be avoided. Solution: Instead, enable the EPM File Tab and you can right click a file to see how EPM would handle it before you execute it. Steps Navigate to Edit parameters under the General Configuration Set "Show Idira EPM tab in File Properties" to On You can now see the EPM File tab in the application properties to view which policies are active for it    
View full article
Question How to take sudo-based Linux Least Privilege to the next level with Idira Endpoint Privilege Manager for Linux? Answer Introduction  Deciding to enforce least privilege on your users for better security is one thing, but building a least privilege rule set is a completely different thing and far from an easy one. This is especially true when you have a complex infrastructure, lots of different user roles and profiles, and nothing but sudo at your disposal (how long and complicated is your sudoers policy file?!). Lots of administrators are lost in the process of trying to define which users should have access to which commands, and they end up with a hot mess of non-effective policies (either too permissive or too limited) and majorly frustrated users.  This whitepaper explores how Idira Endpoint Privilege Manager for Linux (EPM for Linux) can help you discover which commands users actually use, learn why they use them, and enable an easy way to create policies based on users’ activity.   ​​ Prerequisites / Considerations   This whitepaper will help you understand how easy it is to discover command usage and create policies around them with EPM for Linux, but it would be even better if you tried these scenarios on your own – luckily, it’s very easy to do with our EPM free 30-day trial.  If you already have an EPM tenant set up, you can isolate your experimental setup by creating a new Set.  This document assumes that you have at least some familiarity with Linux and, hopefully, Idira EPM too, but if you don’t, here’s a crash course into EPM.  To learn on security best practices and product boundaries refer to our online help.     Using Learning Mode for Quick Discovery  The Discovery period is an essential step for building a well-designed least privilege rule set. During discovery, EPM administrators “listen” to users to uncover their needs and behavior patterns when it comes to using Linux commands. Discovery policies do not interfere with existing user practices beyond asking them questions to provide context for administrators about why a user needs that specific command. Discovery ends in an “command use baseline”, that administrators can constantly refine – taking into account the organization’s IT policy, security considerations, compliance requirements, and customers’ and partners’ requirements (often imposed as a part of supply chain cybersecurity).    Discovery for organizations that have not yet enforced a least privilege policy   Organizations that have not yet enforced a least privilege policy and allow end users to elevate any command with sudo, can enable discovery of sudo commands in EPM, while still allowing all sudo elevations. This way, end users’ work is not disturbed while discovery and least privilege policies establishment is taking place.   EPM detects any sudo command and, if no specific policy was already set, it will create an event for this command in the Event Management pane and elevate the command. Then, the EPM administrator can review the event with all command details, such as the command binary file, the user who ran it, the justification they provided, and decide whether to add this command to the policies.   Use the following workflow to gather information about sudo command usage and define policies.     Step 1: Activate the default policy to monitor activity  In EPM, we call an application (in Linux, a command or script) handled if at least one policy’s definition set matches this specific application. When an application is executed, EPM iterates through the policy list by policy priority, and the first that matches the application will “handle” that application. If no policy matches the application, it is considered unhandled. You can define default policies to handle “unhandled applications”.   Activate the Elevate unhandled applications default policy to monitor all activity and collect events:  In the Management Console, go to Policies > Default Policies.  In the Additional tab, set the Elevate unhandled applications policy to On, then click Yes to confirm the default settings.  You can also click Edit to set additional attributes, such as the computers that this policy targets (the default is all computers in the Set), whether the policy should target standard end users, or also administrative end users, and whether they’ll be prompted for justification before they can execute a command execution.   Note: This policy affects all its targeted computers, regardless of their platform.  For Linux, this policy only elevates sudo commands.  Step 2: Learn command usage  Callout: The Events Management page in the EPM management console collects all the events that did not match a policy. You can drill down for each event, see its details, and take immediate action to protect endpoints by applying relevant policies.  Use the Events Management page to analyze and learn how users in your enterprise issue commands, and understand how you can implement policies to protect your environment.  Let’s consider an example where John, a standard user, tries to restart the sshd service using the sudo command: ‘sudo systemctl restart sshd’. According to the “Elevate unhandled applications” policy configuration, he is required to authenticate and provide a justification for this action. After John provides the information, the command is successfully elevated.   Note: You can configure EPM not to require users to provide a password to run a sudo command, by setting the “Run without password” configuration in the command definition.    An event is created in the Events Management page with the details of the sudo command that John used. As an EPM administrator, you can review the details of the command, such as its full path or checksum, as well as the justification that John provided.     You can see the number of users who issued this command, and the number of computers on which it was executed, as well as the number of times it was executed. You can click an event to drill down for more details, like the user who executed it and their UID, the user it was executed as, the command line that was typed by the user, the command arguments, the working directory, details of the binary that was used, and more:     Step 3: Define specific policies to control activity  Using the insights that you acquired by checking the context and the user’s justification, you can now define specific policies to elevate or block specific commands, and target them to specific computers and users.  If an event looks like a one-off, you can just delete or ignore it without taking action.   You can continue adding command definitions to the policy going forward, based on the collected events. For details about how to do this, see More event management actions.  For more information about creating and managing policies, see Apply policies.    When you add an event to a policy, it is possible to either choose an existing one or create a new policy:     Let’s add systemctl command to a new policy called “Server IT commands”:     The new Policy Details form appears with the command attributes already filled in:    The administrator can edit the policy details – add a description, update targeting, enable audit, set additional options like scheduled enforcement, and update the command definition if needed:     Once the policy is saved, the systemctl command will be managed and elevated by the new policy, and events for this command will no longer appear in the Events Management page.      Discovery for organizations that have already enforced least privileges with sudoers  Customers who have already defined least privilege policies in sudoers and would like to migrate those to EPM, can use the “Detect privileged unhandled applications” default policy.   This policy detects any unmanaged sudo command and creates an event for it in the Events Management page. Then, the command is executed according to the sudoers policy that is configured on the Linux machine. This is helpful for customers who would like to build their policies in EPM while their existing sudoers policies are still being enforced.     Application Groups for Better Management  An application group is a list of applications (in Linux, commands) that are grouped together for easy management. When you create several policies that include the same set of commands, instead of adding commands one by one to each policy, you can create a group, add the commands to the group, and then use this group in your policies. This is also a great way to ensure that if you need to make any modifications, you can do this once for the group and this change affects every policy that includes the group.  Below is an example of a few command groups for different roles in the organization:   When you review events of commands in the Events Management page, you can also choose to add the command to an application group:     Policy audit  EPM provides policy audit tools that give you an in-depth look at users’ activity in either a report or in the Policy Audit page in the EPM console.   Important: To audit policy events, first enable this capability for the Set, and then for each policy you want to audit.    To enable the audit data collection for the Set, go to Advanced > Agent Configuration and, under Data Collection, set Collect Policy Usage Data to On.  Next, to collect audit for commands that are managed by policies, enable audit collection under the Audit section in the policy details page for each policy for which you want to collect audits. By default, this setting is Off.    When audit is enabled, you can review the audit trail in the Policy Audit page. You can also export the audit trail to reports or use the EPM Events API to export it to external integrated systems.   Note the difference between the Policy Audit and Events Management:  Policy audit is used for auditing purposes and is collected for commands that you already mange in your policies. Events management collects events for unmanaged commands, that usually require attention from the administrator.   Additional Linux Policy Attributes   There are additional options for Linux policies that allow you to define more specific behavior on commands execution for granular control.  Child command handling  There are cases when you want to define how child commands are handled:  Block all – Block all child commands.   This is recommended when the command allows shell escape and you want to make sure that no child commands are created from the command. For example, the vi command on RHEL allows the user to run additional commands from within the editor. If you don’t explicitly prohibit this behavior, the user who is allowed to run an elevated vi command can abuse that privilege to run any other command from within the vi with the same permissions. Using this option blocks this potentially insecure behavior.   Elevate all – Elevate all child commands.   This option is useful when the command is a known command that should be allowed, together with its child commands. It is recommended to include the checksum of the command as part of the policy definition, to verify the command authenticity and prevent command hijacking. If you use this setting with a script, the checksum allows you to verify that the script has not changed.   Elevate if permitted by any policy – Elevate child commands if there’s at least one policy that permits users to elevate this specific command with sudo.   This is recommended when the command executes other unknown commands. For example, when the command is a shell, and you want the shell to be restricted so every command executed in the shell is also validated by the policy.       Environment variables handling  EPM controls the environment variables that are available in the sudo command process, to make sure that only required environment variables are part of the process.   There’s a default list of the variables that are part of the sudo command process and variables that are removed from the process. The EPM administrator can modify these lists separately for each command.           Note: Set the Keep list to ‘*’ to pass all the environment variables that exist in the parent process to the sudo process. This is relevant for commands that need the environment variables from the parent process to be available. These commands are usually executed with the sudo -E option.     Sudo no password   By default, the Linux EPM agent requires users to authenticate before running a sudo command. However, you can disable password authentication for sudo commands. This is relevant for deployments where users authenticate without a password, such as when SSH keys are being used.        Command definition examples  The easiest way to define commands in your policy is to build them based on events collected in the Events Management. You can always edit the command definition that is created automatically based on the event and refine it to suit your needs.    You can find below several examples for command definitions:    The definition above applies on the following commands:  sudo systemctl status sshd  sudo systemctl stop sshd  sudo systemctl start sshd  sudo systemctl restart sshd    The definition above applies on the command ‘sudo su –‘ that opens a root login shell. Since the Child Command option is set to “Elevate if permitted by any policy”, this shell is restricted and commands that are executed in it are elevated only if there’s any policy that allows them.     Conclusion  Idira Endpoint Privilege Manager™ for Linux provides essential endpoint security controls and enforces the principle of least privilege for Linux servers and workstations. It eliminates manually intensive, error-prone sudo administrative processes, allows endpoint security managers to centrally configure sudo, and enforce least privilege across Linux systems, at scale, based on policies.   Idira Endpoint Privilege Manager for Linux is an integral component of Idira Endpoint Privilege Manager, a comprehensive endpoint security solution that provides single pane-of-glass administration and centralized, policy-based privilege management for Windows, macOS and Linux endpoints. With Endpoint Privilege Manager, security professionals can centrally manage geographically dispersed, heterogenous endpoints in a consistent manner from a single SaaS console.  Endpoint Privilege Manager can provide visibility and control over all enterprise endpoints, including remote endpoints that infrequently connect to the corporate network. A flexible reporting engine and detailed event journal make it easy to provide evidence for compliance audits, to support forensics investigations, and to demonstrate cyber readiness and proof of required security controls to insurance underwriters.  Endpoint Privilege Manager REST APIs allow you to tie activity and event auditing into your existing security information and event management (SIEM) platforms. And Endpoint Privilege Manager’s policy engine is accessible via API for integration with external policy orchestration and automation tools.  Endpoint Privilege Manager is delivered as a SaaS solution for rapid deployment, simple operation, and easy integration with other cloud-based services. A SaaS deployment model helps you accelerate time to value and reduce TCO by avoiding on-premises equipment expenses and operations hassles. 
View full article
Question Recently Idira released a notice about Microsoft KB impacting EPM Agent functionality. What should EPM customers know about Microsoft KB 5023773 (preview release, published March 21, 2023) and MS KB5025221 (general release, published April 11, 2023) affecting EPM Agents? Answer If you want to be automatically notified of any changes to this article, please click the "+Follow" button. Q: What impact will this have on my endpoints? A: The EPM service will not be able to start, meaning that agents cannot execute/enforce policies or rotate credentials. All agent functionality will be affected. Specifically, the following key EPM features will not function: •    Executing applications and commands that require administrative privileges •    Installing software managed through EPM •    Rotation of the local admin credentials •    Blocking execution of software according to policies Q: When will my EPM agents be affected? A: As soon as MS KB5023773 or MS KB5025221 are applied, the machine is rebooted.  Q: What operating systems are affected? A: Only Windows 10 machines with MS KB5023773 or MS KB5025221 are affected by the issue.  For issues affecting Windows 11 machines please see EPM - Microsoft Windows 11 22H2 update impact to agents' functionality Q: Will the EPM agents automatically update? A: No. EPM does not support automatic agent updates. Please update all agents using your organization’s preferred software distribution method. Q: What Agent versions do I need to download/install to remediate this issue? A:  •    Idira released several SaaS agents compatible with this Microsoft patch. If you run an agent v23.3.0.1196 or higher without any issues, you may continue using that version. The most recent agent will always be published in your EPM SaaS Console. For the list of agents please see KB Article EPM Agent Releases between March 21, 2023 and April 21, 2023  •    Self-Hosted Customers: Download Agent 11.5.6.127 or later from the Marketplace. This agent is compatible with v11.5.2 of the Server software. If you are running an older version of the Server software, please upgrade to the latest Server v11.5 before deploying the agents. Q. What if I already have Windows Update KB5023773 or KB5025221 applied before upgrading agents? A: If you installed Windows Update KB5023773 or MS KB5025221 before upgrading the agents, please see KB Article: How to Upgrade the EPM Windows Agent after the Cumulative Update Preview for Windows 10 (KB5023773) is installed and the Agent service is down. Q: Does this issue affect Loosely Connected Devices (LCD) agents? A: Yes. Because the agents will not be able to start, they will not be able to perform password management operations. Q: Will subsequent MS Security Patches affect EPM agents that were not upgraded? A: Yes. Microsoft security updates are cumulative and include all changes released previously. Because of that, all subsequent MS Security Patches will have the same effect on the agents that were not upgraded. Q. Will new agents interact differently with other 3rd party security tools, such as EDR? A: We do not expect any impact on the new agent’s interaction with other 3rd party software. Please see the Product Documentation: Third-party security programs for more information. [Update]: There is a known issue with Digital Guardian (please see below). Q: Are there any known issues with the new agents or the upgrade process: A: We are currently aware of the following issues: EPM agent disconnected after upgrading using console -- the issue affects agents v23.3.0.1196; it is fixed in v23.3.0.1198 and higher. Please continue to use agents v23.3.0.1196 that have been successfully deployed. All agents v23.3.0.1198 and higher may run side-by-side with v23.3.0.1196 Agent v23.3.x.x general performance issues -- please deploy agent v23.4.0.1235 EPM Performance problems with Digital Guardian and EPM's "Anti-Tampering Protection" setting -- symptoms include: Inability to save downloads, System slowness when launching applications After upgrading to v23.3.0.1198, EPM Agent services stop EPM - Random Characters in Script Names in Idira EPM Control Panel On Desktop
View full article
Problem: The purpose of this article is to help provide additional guidance and best practices in integrating Idira EPM with Microsoft Sentinel using the Idira EPM data connector that is available from CyberArk’s Marketplace. Idira Marketplace (site.com) On the Idira EPM for Microsoft Sentinel Marketplace page, you can download the Integration Guide (noted in red in the above screenshot). The guide offers step-by-step instructions on how to configure the data connector but lacks some key details that are important to note in order to successfully integrate EPM and Sentinel. The intent of this Tips + Tricks article is the highlight those key details and provide additional insight and best practices to help you successfully deploy the integration. Steps Solution: It is recommended to have the Integration Guide mentioned above available as this article should be used as supplemental material to that guide.   Step 2 in the Integration Guide mentions needing an EPM user account that will be responsible for getting the events from EPM via API.  It is best practice to use an account that is a View Only Set Admin.  To ensure that are no authentication related issues when Sentinel makes a connection to EPM, make sure you are able to interactively log into EPM using this account at https://login.epm.cyberark.com. It is recommended to add Sentinel to the Log Analytics Workspace ahead of running the deployment via the ARM template.  In some cases, you may receive an error during the deployment process if your workspace is not already associated to Sentinel. Step 3 in the Integration Guide describes how to search the Azure Marketplace for the data connector as well as how to deploy. Depending on when you implement this solution and the time when this article was published, you may receive the following error during the deployment process: If this is your case, the deployment can be completed by completing the data connector from Microsoft Sentinel (search for ‘Microsoft Sentinel’ in top search box > select your Workspace > select ‘Data connectors’ > select ‘CyberArkEPM (using Azure Functions)’ in middle pane > select ‘Open connector page’ on right pane. In the following screen, there should be a  button halfway down the center pane.  Click on this button to launch the following deployment template: The fields in red are noteworthy and explained below.  Fields in blue can be left as default. Workspace ID – Found from Log Analytics Workspace > Agents Workspace Key - Found from Log Analytics Workspace > Agents Idira EPM Username – Same username created in EPM Console Idira EPM Password – Password set for EPM user account Idira EPM Server URL - https://login.epm.cyberark.com App Insights Workspace Resource ID – Found from Log Analytics Workspace > Properties > Resource ID Once all required fields are filled in, click on the Review + create button to deploy and configure the data connector. This completes the deployment of the data connector.  To validate that it has been successfully implemented and that EPM and Sentinel are integrated, look for the creation of the ‘CyberArkEPM_CL’ table from the Log Analytics Workspace (keep in mind that it could take an hour for this table to be created): Additionally, you can query ‘CyberArkEPM_CL’ table from Logs and see data pulled in from your EPM set using the user account that was supplied in the deployment template.
View full article
The purpose of this article is to show exact steps for customers who are operating below EPM Server 11.5.2 who need to apply the latest agents to their environments (As of the time of this article 11.5.6.127) Steps Download the server binaries from the SFE – 11.5.2 (https://support.cyberark.com/sfe) Once there, search for Idira PAS Solution Navigate the tree to download the following screenshot: Download required server patches (11.5.3) from the marketplace (https://community.cyberark.com/marketplace/s/#software-aK42J0000000DQ2SAM-) Once there, filter down to grab just the “EPM-Server-dll-Rls-v11.5.3.398.zip”                                                                i.       Download require agent patches (11.5.6 for Windows and 11.5.5 for Mac) (Same link as above) Windows:                                                                 i.       Mac:                                                                i.       Verify pre-reqs Upgrade to 11.5.2 Apply patch CA22-19 (11.5.3)  Apply latest agent executables Download the Agent from the marketplace Upload the agent zip to the EPM Server Replace VFAgentSetup.msi, VFAgentSetupX64.msi, AgentManifest.json files in AgentDeploymentWork directory Navigate to %ProgramFiles%\CyberArk\Endpoint Privilege Manager\Server\VFMNG\AgentDeployment work directory Backup a copy of VFAgentSetup.msi, VFAgentSetupX64.msi, and AgentManifest.json into a different working directoryUnzip Win Agent-Rls-v11.5.6.127.zip Replace contents of zip in AgentDeploymentWork directory IISReset Open CMD as admin Run iisreset Verify agents reflect properly in EPM Server Console Deploy agents as usual  
View full article
Problem: With the increasing security threat landscape, there is more need to add and layer on security software to protect corporate workstations and servers.  These software solutions interact with similar parts of the OS and could cause conflicts with the OS or the security software. An important yet overlooked implementation detail of EPM is ensuring that proper mutual exclusions are added to the exclude lists in both EPM and your 3 rd party security programs.  This means that we do not want EPM to monitor your security programs and vice versa.  These agents can conflict and cause adverse issues on your endpoints such as: High CPU spikes with the EPM agent Latency when viewing the Idira EPM tab False positives seen in 3 rd party security software EPM agents may show “Disconnected” from the EPM console Issues interacting with the context menus EPM agent taskbar icon Steps Solution: The following are best practice guidelines to follow when handling mutual exclusions: This may be an obvious statement but conducting a full analysis of your security technology stack is recommended because this will reduce the effort in troubleshooting a missing exclusion that may not be apparent Regular review and updating of your exclusions to make sure new version of tools are identified so new files and/or folders can be properly excluded from EPM Do not assume the default list of exclusions are applicable for all environments.  Any paths that do not exist in your organization should be removed so EPM can protect those locations Reciprocal exclusion of EPM from other security tools.  Make sure all documented EPM files and folders are excluded to ensure EPM functionality is not blocked by other security products Software development tools could cause CPU spikes on the EPM agent so keep an eye out for these software types: Developer source code directories Developer compiled/output code directories Developer frameworks code directories Developer temporary code and compilers Use good judgement when deciding to exclude via Agent Configuration (globally applied to all endpoints in the Set) versus a more restrictive application policy if specific parameters are known such as the publisher’s signature or folder location For Windows OS with the EPM agent installed: Use the Idira EPM tab to validate that your 3 rd party security software is properly excluded.  It will show as Exclude – [EXCLUDE FILES POLICY] For Mac OS with the EPM agent installed: Right-click on an application and choose Idira EPM: Get Policy Info.  A correctly excluded application will show as Exclude – [EXCLUDE PATHS POLICY MAC] Resources: Idira Documentation on Mutual Exclusions https://docs.cyberark.com/EPM/Latest/en/Content/Installation/InstallAgentsOnEndpointMachines.htm#Thirdpartysecurityprograms Idira Community Knowledge Article (How and What to Exclude) https://community.cyberark.com/s/article/00004063 Prevent Security Software Conflicts Using Mutual Exclusions - Mar 14, 2024 Office Hour https://community.cyberark.com/s/article/EPM-Success-Office-Hours-Hub
View full article
To collect process information on the endpoint using Process Monitor (ProcMon), it is essential to execute the program with elevated privileges. To ensure that these elevated privileges are exclusively applied to Process Monitor, we have created a dedicated policy specifically targeting this application. Steps To utilize the dedicated policy for the Process Monitor Application, please follow these steps: Download the Policy File Download the attached file named "Policy-Elevate-Procmon.epmp". Log in to Idira EPM Console Access your Idira EPM Console and navigate to the Policies section. Import the Policy Click on the three dots on the blue "Create advanced policy" button located at the upper right-hand corner of the screen. Select the "Import policies" option. In the "Policies import" window, browse to the location where you downloaded the file "Policy-Elevate-Procmon.epmp" and select it. Click OK to import the "Policy-Elevate-Procmon.epmp" policy. Activate the Policy Note that imported policies are disabled by default. To activate the policy, click on the three dots next to the policy name and select "Activate". Ensure Policy Change is Received Confirm that the new policy change has been received on the endpoint where the Process Monitor (ProcMon) is required to run. Disable the Policy After Use It is recommended to disable the policy after gathering the required Process Monitor (ProcMon) data. By following these steps, you will successfully implement and manage the dedicated policy for the Process Monitor Application. This policy is equally obligatory for administrative users to mitigate risks associated with "Evasion" and "Remote Code Execution".
View full article
Question Note - this procedure is only required when collecting the Procmon log using the EPM support utility fails (https://docs.cyberark.com/EPM/23.12.0/en/Content/Policies/Collecting%20Agent%20Support%20Info.htm) How do I collect ProcMon logs for EPM (SaaS)?   To collect process information on the endpoint using Process Monitor (ProcMon), it is essential to execute the program with elevated privileges.   To ensure that these elevated privileges are exclusively applied to Process Monitor, we have created a dedicated policy specifically targeting this application.   To download and apply the dedicated policy specifically targeting Process Monitor (ProcMon), follow the link below: https://community.cyberark.com/s/article/EPM-How-to-use-Process-Monitor-ProcMon-Policy-Requirement Answer Note - You will need an Elevate policy for ProcMon or use an Administrator user i. To Collect a ProcMon and Support Info a. Agent Self Defense must be disabled (*steps below) b. Right click the Idira Icon in the system Tray on the endpoint and select ‘Get Support Info’. c. Put a check in all boxes including ‘Process Monitor Recording Session’. d. Click the ‘Continue’ button. e. Click the ‘Accept’ button. f. Follow the instructions on the ‘Process Monitor Recorder’ screen. ii. You can also use ProcMon to collect a boot log: a. Agent Self Defense must be disabled (*steps below) b. Run Procmon.exe. c. Select Options -> Enable Boot Logging. d. Click OK. e. Restart the operating system. f. Wait until the system starts (it may take up to 15 minutes) and run Procmon.exe again. g. Click Yes and save the log file. h. Select All Events in the Events to save section. Specify the path for the logs to be saved, then click OK. i. Gather a fresh support info immediately after the ProcMon is done (right click on the agent icon > Get Support Info > check all the boxes except for "Process Monitor recording session") *Steps to disable Agent Self-Defense (console > Advanced > Agent Configuration > Edit > Extended Protection > Agent self-defense): i. You can generate a secure token via the steps here, https://docs.cyberark.com/Product-Doc/OnlineHelp/EPM/Latest/en/Content/Policies/Protecting%20Agents.htm#BypassagentprotectiononWindowsandmacOS ii. You can disable Agent Self Defense: a. Open a CMD as admin b. Navigate to C:\Program Files\CyberArk\Endpoint Privilege Manager\Agent\ c. Run the command, vf_agent.exe -UseToken {token from step i} For example, vf_agent.exe -UseToken 123 iii. You can re-enable Agent Self Defense by rebooting the endpoint   **TIP** When Procmon is started it will start recording immediately, which may not be what you want.  You can stop the recording by clicking ‘File>Capture Events’ (this will toggle the collection on or off) or click on the icon that looks like a magnifying glass. If you do not want the log that was collected before you stopped the recording you can clear it by clicking ‘Edit>Clear Display’ or click on the icon that looks like a sheet of paper with an envelope on it.   **TIP** Procmon logs get very big, very fast.  To ensure you get the smallest Procmon log possible be sure to plan out your steps ahead of time so that you know every step you need to perform and in what order to reproduce the issue that you are recording. Since we ask for the steps you took during the process anyway you can use this to fulfill that requirement.   Q: How do I collect ProcMon logs for version 10.4- vs 10.5+ of EPM? A: The method you use to collect Process Monitor logs depends on what version of the EPM agent is installed on the endpoint.   With EPM agent version 10.5+ the ability to collect Process Monitor logs has been built into the Get Support Info process.   With EPM agent version 10.4- the Process Monitor tool must be downloaded from the Sysinternals site and run separately, and manually,  apart from the Get Support Info tool.   The steps for collecting a Process Monitor log when EPM Agent 10.5+ is installed are detailed in the Solution Guide for the appropriate version.  Simplified, the steps are below: a. On the EPM console, go to My Computers and right click on the endpoint and select Enable Support Mode. b. On the Enable Support Mode prompt, enter the # of hours for the ProcMon to be elevated and click OK. c. The status will show that the support Mode is till DD-MMM-YY. d. Right click the Idira Icon in the system Tray on the endpoint and select ‘Get Support Info’. e. Put a check in all boxes including ‘Process Monitor Recording Session’. f. Click the ‘Continue’ button. g. Click the ‘Accept’ button. h. Follow the instructions on the ‘Process Monitor Recorder’ screen.   Collecting a system events Process Monitor log when EPM Agent 10.4- is installed is a detailed process outlined below: To Collect a ProcMon and Support Info a. Close all unused applications. b. Agent Self-Defense MUST BE DISABLED before recording any procmon recording. You can disable Agent Self-Defense by going to the console > Advanced > Agent Configuration > Data Collection > Agent self-defense password > set this to a null value, please note the default password is the SetID c. Use ProcMon version 3.05 or higher. Preferably, download the latest version from https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx. d. Make sure Filter->Drop Filtered Events menu item is unchecked. e. Enable Thread Profiling Events in ProcMon (Options->Profiling Events->Generate Thread Profiling Events->Every 100 millisec) f. Run Procmon.exe. Logging will start automatically. g. Minimize Process Monitor and reproduce the issue. h. Maximize Process Monitor and uncheck the option File -> Capture Events. Event logging will stop. i. Select the menu item File -> Save. j. Select All Events in the Events and save in Native Process Monitor Format (PML) to save section. Specify the path for the logs to be saved, then click OK. ***k. Provide a brief description of what was done during the ProcMon including time frame. This will greatly help us when we are referencing the log as it can get quite large. If possible provide a step by step description of what you did to reproduce the issue. ***l. Gather a fresh support info immediately after the ProcMon is done (right click on the agent icon > Get Support Info > check off all the boxes>click the ‘Collect’ button)   You can also use Procom to collect a boot log: a. Agent Self-Defense MUST BE DISABLED before recording any procmon recording b. Run Procmon.exe. c. Select Options -> Enable Boot Logging. d. Click OK. e. Restart the operating system. f. Wait until the system starts (it may take up to 15 minutes) and run Procmon.exe again. g. Click Yes and save the log file.   **TIP** When Procmon is started it will start recording immediately, which may not be what you want.  You can stop the recording by clicking ‘File>Capture Events’ (this will toggle the collection on or off) or click on the icon that looks like a magnifying glass. If you do not want the log that was collected before you stopped the recording you can clear it by clicking ‘Edit>Clear Display’ or click on the icon that looks like a sheet of paper with an envelope on it.   **TIP** Procmon logs get very big, very fast.  To ensure you get the smallest Procmon log possible be sure to plan out your steps ahead of time so that you know every step you need to perform and in what order to reproduce the issue that you are recording. Since we ask for the steps you took during the process anyway you can use this to fulfill that requirement.
View full article
How do I collect a ProcMon boot log?   To collect process information on the endpoint using Process Monitor (ProcMon), it is essential to execute the program with elevated privileges.   If Idira EPM is installed on the End Point, in order to ensure that these elevated privileges are exclusively applied to Process Monitor, we have created a dedicated policy specifically targeting this application.   To download and apply the dedicated policy specifically targeting Process Monitor (ProcMon), follow the link below: https://community.cyberark.com/s/article/EPM-How-to-use-Process-Monitor-ProcMon-Policy-Requirement Steps To start working with Process Monitor, download and unpack an archive with the application. Make sure that the current user account has administrator privileges. (If already downloaded, make sure it is ProcMon version 3.05 or higher. Preferably, download the latest version from https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx) Collecting a boot log: Agent Self-Defense MUST BE DISABLED before recording any procmon recording Run Procmon.exe. Make sure Filter->Drop Filtered Events menu item is unchecked. Select Options -> Enable Boot Logging. Click OK. Restart the operating system. Wait until the system starts(it may take up to 15 minutes) and run Procmon.exe again. When saving the log make sure to select All Events option under Events to save and Native Process Monitor Format (PML) under Format. Click Yes and save the log file. ZIP the generated PML file to save traffic and space. Q: How do I collect a ProcMon boot log?   A: To start working with Process Monitor, download and unpack an archive with the application. Make sure that the current user account has administrator privileges. (If already downloaded, make sure it is ProcMon version 3.05 or higher. Preferably, download the latest version from https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx) Collecting a boot log:   *EDIT 2/3/2017* IF USING EPM Version 6.0+ Agent Self-Defense MUST BE DISABLED before recording any procmon recording Run Procmon.exe. Make sure Filter->Drop Filtered Events menu item is unchecked. Select Options -> Enable Boot Logging. Click OK. Restart the operating system. Wait until the system starts(it may take up to 15 minutes) and run Procmon.exe again. When saving the log make sure to select All Events option under Events to save and Native Process Monitor Format (PML) under Format. Click Yes and save the log file. ZIP the generated PML file to save traffic and space.
View full article
The purpose of this article is to describe some of the contents of a Support Info zip file generated on a Windows computer Steps This describes some of the contents of a SupportInfo zip file: \Trace\dumpProcMap.txt Shows info about the processes currently running at the time the SupportInfo was captured.  Contains good information like what is the process ID, policy used, etc. \Trace\Filter_Drivers.xml Contains information about filter drivers loaded, similar output to running microsoft command fltmc.  This can be used to identify other security products that might be interfering with EPM \Trace\Inventory.trace Contains information about the machine hardware's such as manufacturer, model, serial number. Contains information about local users and groups. Shows installed applications similar to what you'd see in the "Programs and Features" in the control panel. \Trace\Sysinfo.trace Contains EPM agent version information Contains information that EPM agent uses to communicate with the SaaS server (ex: Dispatcher URL, setID, and agent ID) Contains operating system build info, hardware info like memory, ip address, computer name, etc Contains time zone information, useful for matching up Application and System event log entries with other log entries in the SupportInfo Contains information about Windows Services Contains filter driver information \Trace\pas\pasagentlog.txt Can be used to gather information about LCD issues \Trace\VFUpgrade.log The msiinstaller log file from the most recent upgrade attempt \Trace\vf_agent.trace A log recording when the Idira EPM service (vf_agent) starts up. Can be searched for version or agentID to show if the agentID changed or the version was upgraded After the service starts, logging is transferred to vf_agent_srv.trace \Trace\vf_agent_srv.trace Records a lot of information which depends on the logging level.  This is how you set the logging level: EPM console > Advanced > Agent Configuration > "Policies" section > "Trace policy usage on agents" Older versions of this log are kept, and can be opened with notepad vf_agent_srv.trace search terms:   keyword what it can show you ***** Find when the EPM agent service starts up.  This should show you useful information like version, agentID, etc.  Note: may have been removed in later versions setpol See when the EPM agent checks or applies policies. changeid When the agent gets a new vf_policies.xml file. procstart if Policy Usage in Agent Trace is set to Trace All, will show policy name, policy action, PID, and parentPID, and more Senddata Shows when the endpoint tries to upload events to the EPM server.  This is useful for troubleshooting a delay in receiving an event in the console.  Note the log will show different kind of events rlua Logging regarding "Remove Local Administrators" policy RequestPoliciesUpdate2 a request for a policy update.  Look a few lines up.  If you see VF_POLICIES_CHANGED=95 then that means it was an automatic policies update CvfRegistrator Shows the agent trying to register with the SaaS console. Example of success: CvfRegistrator::Register: AAUTH: Registration succeeded ahue entries related to just in time policies CvfProcDefender::ProtectFA The end user uses the Idira control panel "Request Administrative Privileges" rescanning ad groups Agent activity related to policies that use AD Computer Group Targeting CvfADGroupMembershipCache Agent activity related to policies that use AD Computer Group Targeting     \Trace\vf_host.trayicon.x64.{xxx}.trace May show information regarding the systray icon starting up May show errors regarding OPAG request for authorization if you search for challengeid \Application.evtx The Windows Application event log may appear in the zip file, depending on the options chosen when generating the SupportInfo If you open the log in event veiwer on your computer, the timestamps will be using the time relative to your workstation.  So check \trace\sysinfo.trace to check what the time zone was on the endpoint so you can adjust the for the time difference \System.evtx The Windows System event log may appear in the zip file, depending on the options chosen when generating the SupportInfo If you open the log in event veiwer on your computer, the timestamps will be using the time relative to your workstation.  So check \trace\sysinfo.trace to check what the time zone was on the endpoint so you can adjust the for the time difference \Trace\vf_policies.xml This is the policy file that EPM is using for policies. Can be opened with various apps such as chrome or notepad. Can be searched for key phrases to verify an endpoint received a recent policy or setting change. vf_policies.xml search terms   keyword meaning policyusageintrace   A value of 2 means EPM console > Advanced > Agent Configuration > "Policies" section > "Trace policy usage on agents"  = "Trace All" <ChallengeResponse> Corresponds with EPM console > advanced > agent configuration > offline policy authorization generator section [EXCLUDE FILES POLICY] Corresponds with EPM console > advanced > agent configuration > files to be ignored always (windows) [IGNORED LOCATIONS FOR NEW APPS POLICY] Corresponds with EPM console > advanced > agent configuration > exclude new or changed files from Application Catalog and Inbox PrivLackFlushIntervalSec Corresponds with EPM console > advanced > agent configuration > event queue flush period seconds AllowedLocalAdministrators The section of the Remove Local Administrators policy that corresponds with the "scope" section in the console (The users or groups to EXCLUDE from being removed by the policy) action="1" Credential rotation policy action="2" Policy action set to run normal action="3" Policy action set to elevate action="4" Policy action set to elevate if necessary action="11" Set Security Permission Policy action="17" Credential rotation policy action="23" Remove Local Administrators policy epAction="1" A threat protection policy set to detect epAction="2" A threat protection policy set to block
View full article
Question My Endpoint System Information report is displaying empty rows for operating system for some endpoints.  How should I troubleshoot this issue? Answer In the Console go to Endpoints (Beta) then "My Computers. While still in "My Computers" press Control+Shift+F12. This is a special combination which should cause a "Support" button to become visible at the top next to "Organize" and "Computer". Highlight a problematic endpoint.  Note, endpoint needs to be "Alive".  Go to the "Support" drop down. Click "Restart Idira EPM Agent".   Wait 15 minutes then generate the report again If the above fails, please collect SupportInfo logs from the endpoint and submit a case to Idira support
View full article
PROBLEM: Linux systems often struggle with scattered user accounts, making management complex and security weaker. Delays in updating identity and access controls can increase cyber risks and hinder IT support for businesses. Outdated authentication methods further expose corporate Linux environments to unauthorized access and data breaches. SOLUTION: Configure Identity Bridge -- CyberArk’s solution to centralize management of user access, authentication, and authorizations on Linux endpoints. Identity Bridge helps Linux endpoints integrate with Active Directory and modern cloud-based directories while supporting strong, modern authentication protocols. In this article, we’ll be focusing specifically on how to integrate Active Directory into Identity Bridge since that is currently supported, but in the future, other directories will be supported The following graphic shows the components and workflows of Identity Bridging: PREREQUISITES: Identity tenant configurations may require a backend feature flag or entitlement to be enabled by CyberArk’s Identity team. You can contact Idira Identity support and provide them with your tenant ID regarding entitlement and configuration flag requests that may need to be enabled. Note: To enable the required ISPSS platform capabilities, open a support ticket in the Technical Community with the following attributes: Product: Identity and Subject: Enable EPM Identity Bridge. Also provide the ISPSS tenant information. For Linux endpoints: EPM agent must be installed SSH must be enabled Steps STEP-BY-STEP First, you’ll need to integrate your EPM directory with Active Directory. To do so, follow this article, which explains the steps required as well as best practices. Next, you’ll need to configure the Identity Bridge policy on your EPM tenant. For this step, follow this article for a step-by-step guide. Upon completion of these steps, you should be able to authenticate to your Linux endpoints with AD accounts.  
View full article
Implementing Least Privilege on macOS with Idira EPM QuickStart Policies CyberArk’s macOS EPM QuickStart policies offer a pre-configured framework to enhance security and simplify administration. Designed to enforce least-privilege principles, these policies help reduce risk from common threats and streamline policy deployment. To understand QuickStart fundamentals, watch the EPM Video Nuggets on QuickStart and macOS definitions.   What to Expect When Enabling QuickStart Policies Once QuickStart policies are enabled on macOS, you may see frequent EPM application block dialogs.  While it’s meant to protect against malicious code, the block policies can also block legitimate applications that invoke OS-level binaries.  These binaries, which are frequently weaponized by malware, are also known as Loobins (Living Off the Orchard Binaries) and are well known in the security community.  As a result, even trusted applications may trigger blocks under this policy, making it a critical area for review and refinement. To minimize disruptions, you'll need to evaluate blocked events and create exceptions for trusted apps.   Understanding the 2.1 Block Policy Among the various policies included in QuickStart, the 2.1 block policy quickly becomes the most visible and impactful due to its restrictive nature.  This policy must be tuned so that approved applications are exempted. OS binaries like ditto, system_profiler, or ioreg are commonly used by the operating system but can also be abused by attackers to perform malicious actions without triggering traditional security alerts.  A key concept to understand here is context-aware application control.  What this means is we want to prevent the weaponization of OS-level functions by considering what is launched from parent processes to child processes when it comes to allowlisting practices. The 2.1 block policy targets binaries signed with Apple’s Developer ID that invoke OS-level functions (e.g., ditto, system_profiler, ioreg). These can be misused by attackers, but are also used by legitimate apps like Slack or JAMF.  For these cases, we use context-aware application control—evaluating both parent and child processes to determine legitimacy. Steps Exception Handling Workflow The following decision-making workflow can be used to guide you with your evaluation of the parent and child relationship to determine which policy and/or application groups to update.     Identify the Blocked Event 1. This is an example of an application blocked by policy.  Notice that the Publisher is Software Signing.  Provide a justification so this event can be tracked down more easily in Policy Audit.   Review Policy Audit 2. In the EPM console, go to Policy Audit and use the filter to track down the blocked event.  Once found, we want to look under Parent process to confirm if there is a parent process present.   Determine the Parent-Child Relationship 3. In this case, JAMF is the parent process and the OS-level binary is system_profiler. We can follow the workflow diagram and review the next decision point to check if the parent process is in the approved Invokers of Loobins application group. If, however, we see that there is no associated parent process, we would just add an exception directly to the QuickStart - Exceptions to Blocked/Restricted application group (follow No path at first decision point in the workflow diagram).  Note that there are two “Exceptions to Blocked/Restricted” application groups, Global and Developers.  These were created to provide more granular control for different roles/personas in your organization.  a. Again, MacOS QuickStart takes into account context-aware application control meaning we're observing when OS-level binaries are called by 3rd party applications and we can control which parent applications can launch which child processes.   Check the Approved Invokers Group 4. From the EPM Console > Under Policies > Application Groups > click on QuickStart – macOS Global Approved Invokers of Loobins apps to check if there is a definition that matches the parent process identified in step 2.  In this example, it doesn’t exist so we will capture the details from step 2 so we can add a new definition to allow JAMF (the parent process) to launch system_profiler (the child process). In order to capture the entire parent process path, you can triple-click the path itself shown below by the red arrow.  This will allow you to copy/paste the full details to parse out the data so you can build the following definition: Once saved, double-check and make sure your newly added definition is added to the Approved Invokers of Loobins apps Application Group: Create Exception for the Child Binary 5. Next we need to add an exception for the child process.  In this case,  we are adding system_profiler to the 1.0 – QuickStart – Global Exceptions to Blocked/Restricted policy since the child process doesn’t already exist.  Note that there is a 1.0 and a 1.1 policy for QuickStart.  The distinction is that the 1.0 policy is for any global applications while the 1.1 can be tailored for specific roles.  In this example, JAMF is our MDM for the entire organization so we’ll be targeting the 1.0 global policy.  a.        We’ll go ahead and create the following definition and pay special attention to the Parent process property highlighted in red in the following screenshot.  We are choosing the specific application group where JAMF was added in step 4 above. Rinse and Repeat Process 6. At this point, we’ve completed the steps to allow JAMF to access system_profiler using EPM controls.  Note that it’s very possible this exception handling process needs to be followed multiple times per application, since if the one we just excluded above has a series of binaries being called, then we'll need to rinse and repeat using the steps above. Handle Other Blocking Policies 7. Once you’ve completed handling the 2.1 blocking for software signing applications, you can then proceed to addressing the 2.0 blocks (common attack vectors) which most likely won't have parent processes to consider and should just be added to its relevant app group. Manage Elevation Requests 8. You may also encounter elevation attempts that populate in EPM Events Management. For these events, you should review and add ones that are allowed to be elevated into the relevant 3.0 Elevate policy for the current role/persona group you are working with. If it is an auto-updater/helper function that needs to elevate, then you can use the QuickStart - macOS Elevate Installers/Updaters Application Group; otherwise use the QuickStart - Global Approved Elevations Application Group.   Scaling Policy by Persona Group Repeat the above workflow for each user group to reduce noise and fine-tune controls. Duplicate the 1.1 QuickStart – [Role] Exceptions policy and its related App Groups for:   Global – Applications used on all macOS devices Information Security – Tools exclusive to security teams Information Technology – Applications used by IT and support Executives – Applications used by leadership team Developers – Likely the most complex due to diverse toolsets Any other pertinent roles to include   In summary, this article serves as a prescriptive guide on how to execute least privilege on macOS using our QuickStart policies.  These policies were created not only to help you get started with EPM but also allows you to scale in a structured and organized manner that is scalable.
View full article
Question This article outlines the rationale for using the  User.Read.All  permission in the context of EPM, an Azure-registered application, and explains why  User.ReadBasic.All  may not be sufficient for its operational requirements.   Organizations often aim to follow the principle of least privilege when assigning permissions to applications. While  User.ReadBasic.All  appears to be a safer alternative due to its limited scope, it may not meet all functional requirements. EPM requires access to user profile and group membership data to enforce policy-based access and ensure accurate user-to-group mapping within Azure Active Directory (Azure AD). While User.ReadBasic.All  is a more restrictive permission, it does not meet the functional needs of EPM. Answer Key Differences and Justification Permission Scope User.ReadBasic.All  provides access to a limited set of user properties (e.g., display name, email, job title). It does not include group membership information, which is essential for EPM’s policy enforcement logic. Group Membership Requirement EPM relies on group membership data to associate users with Azure AD groups and apply relevant policies. Although  GroupMember.Read.All  grants access to group data, it does not provide a complete view when used without  User.Read.All . Why  User.Read.All  Is Required User.Read.All  includes comprehensive user profile data, including group memberships. This enables EPM to: Evaluate user roles and entitlements. Apply conditional access and compliance policies. Ensure accurate mapping between users and Azure AD groups. For EPM to function securely and effectively as an Azure-registered application, it must access detailed user and group information. The  User.Read.All  permission is necessary to meet these requirements, whereas  User.ReadBasic.All  lacks the scope needed for full policy enforcement and user-group correlation.   For more information on how to register EPM as an Azure application and configure permissions, refer to the official Idira documentation: https://docs.cyberark.com/epm/latest/en/content/admin/azuread-addepmagentasazureregapp.htm?Highlight=azure
View full article
Question Does Idira recommend having a separate MDM config profile for EPM, or is it okay to put Idira in a MDM config profile shared by other applications? Answer We recommend putting Idira in its own config profile not shared by other applications.  The reason for this is to prevent trivial changes to the MDM config profile (for unrelated applications)  from breaking EPM.   If Idira is in a shared config profile with other applications, changes to that config profile may cause Idira extensions from losing their permissions on endpoints.  This would require resubmitting CyberArk's extensions in order to restore permissions.  It is safer to put Idira in its own MDM config profile.
View full article
Question When deploying applications using Microsoft Intune with the "Install as system" option enabled, the Idira EPM Agent may not apply the expected policies. This results in installations being blocked or not elevated, even though matching policies exist. The EPM Agent evaluates policies based on the context of the process initiating the action. When Intune runs installers as the Local System account, the process metadata (e.g., parent process, user context, source path) differs from standard user-initiated installations. As a result: Policy conditions may not match. Trust may not be inherited correctly from the system-level process. Answer To resolve this issue, disable Exclude service accounts from access restrictions via the EPM Console What is Exclude service accounts from access restrictions? The Exclude service accounts from access restrictions setting controls whether the EPM Agent evaluates processes running under built-in service accounts, such as SYSTEM, LOCAL SERVICE, NETWORK SERVICE.   When enabled, system-level processes are ignored by the agent for policy matching. When disabled, system-level processes are included, allowing policies to apply even when applications are installed via Intune or other system-level tools. This setting is critical when using Microsoft Intune’s “Install as system” option, as installers launched this way will otherwise bypass EPM policy evaluation. How to Change This Setting in the EPM Console Log in to the EPM Administration Console. Go to Configuration Click the More actions (...) button in the General configuration section. Select Edit Parameters. Locate the setting labeled Exclude service accounts from access restrictions under the Policies category. Change the value from On to Off. Save the configuration. The updated configuration will be pushed to endpoints according to the Policy update interval defined in your environment. How to Trigger a Policy Update To apply the updated configuration immediately on an endpoint:   Right-click the Idira EPM Agent tray icon. Select Request Settings. How to Confirm the Setting Was Applied on the Endpoint You cannot directly view the agent’s active configuration XML from the file system. Instead, follow these steps to confirm the setting was applied: Collect Support Information from the endpoint: Right-click the Idira EPM Agent tray icon. Select Get Support Info. Extract the ZIP File: Locate the file named something like VfSupInfo <timestamp>.zip . Extract the contents. Navigate to the Configuration File: Inside the extracted folder, locate: vf_policies.xml Open the XML File in a text editor and search for:   <ExcludeAllSystemProcs>False</ExcludeAllSystemProcs>   If the value is  False , the setting has been successfully applied. If it still shows  True , the policy update may not have completed or the configuration change was not saved in the console.   Note: This file is generated as part of the support package and reflects the current applied policy.
View full article
Question: Is it possible to use the Idira EPM to create a policy that can block (blacklist) browser extensions and plugins running on web browser applications? Answer: Yes, it is possible. Google Chrome and Mozilla FireFox have been tested to be working. Using the similar steps below, you should be able to apply to different Browsers. Disclaimer: The instructions below are for the new UI introduced in EPM version 22.6. For old UI, you can refer to this community link for the steps: https://community.cyberark.com/s/question/0D52J000081I7gcSAC/can-cyberark-epm-be-able-to-block-web-browser-extensions-and-plugin-eg-google-chrome-firefox-and-ms-edgeie-browser-extensions-and-plugin Steps The steps below are for Google Chrome on Windows: ========= 1. In the EPM console, go to Policies and select "Create advanced policy". 2. Select "Continue" after you configured the below settings: - Name: *** - Platform: Windows - Action: Allow 3. Under the Scope, add the following and press Done: Publisher's signature starts with Google LLC 4. For the Targets, Audit and End User UI sections, set them accordingly to your requirements. 5. In the options section, proceed to the Application access control and switched it ON. 6. Under the Files on the local disk sub-section, select Edit. Proceed to Add Filename for 2 parameters below: Location: %LOCALAPPDATA%\Google\Chrome\User Data\Default\Extensions\Temp | Access control mode: Off Location: %LOCALAPPDATA%\Google\Chrome\User Data\Default\Extensions\ | Access control mode: Restrict 7. Keep the rest as default (Or edit them if required) and proceed to create the policy. 8. You can either proceed to push active policies to agents (via EPM console) or request settings from the end-user computer (via the EPM icon). Remember to close all Google Chrome browsers and start them again in order for the Block extension to take effect. 9. As a test, when you attempt to add the browser extensions, the below error dialog should appear: ========= The steps below are for Google Chrome on macOS: ========= 1. In the EPM console, go to Policies and select "Create advanced policy". 2. Select "Continue" after you configured the below settings: - Name: *** - Platform: macOS - Action: Allow 3. Under the Scope, add the following and press Done: Publisher's signature starts with Google   4. For the Targets, Audit and End User UI sections, set them accordingly to your requirements. 5. In the options section, proceed to the Application access control and switched it ON.   6. Under the Files on the local disk sub-section, select Edit. Proceed to Add Filename for 2 parameters below: Location: /Users/*/Library/Application Support/Google/Chrome/Default/Extensions/Temp | Access control mode: Off Location: /Users/*/Library/Application Support/Google/Chrome/Default/Extensions | Access control mode: Restrict       7. Keep the rest as default (Or edit them if required) and proceed to create the policy. 8. You can either proceed to push active policies to agents (via EPM console) or request settings from the end-user computer (via the EPM icon). Remember to close all Google Chrome browsers and start them again in order for the Block extension to take effect. 9. As a test, when you attempt to add the browser extensions, the below error dialog should appear:   ========= The steps below are for Mozilla FireFox: ========= 1. In the EPM console, go to Policies and select "Create advanced policy". 2. Select "Continue" after you configured the below settings: - Name: *** - Platform: Windows - Action: Allow 3. Under the Scope, add the following and press Done: Publisher's signature starts with Mozilla Corporation 4. For the Targets, Audit and End User UI sections, set them accordingly to your requirements. 5. In the options section, proceed to the Application access control and switched it ON. 6. Under the Files on the local disk sub-section, select Edit. Proceed to Add Filename for the parameter below: Location: %APPDATA%\Mozilla\Firefox\Profiles\*\extensions\ | Access control mode: Restrict 7. Keep the rest as default (Or edit them if required) and proceed to create the policy. 8. You can either proceed to push active policies to agents (via EPM console) or request settings from the end-user computer (via the EPM icon). Remember to close all Mozilla FireFox browsers and start them again in order for the Block extension to take effect. 9. As a test, when you attempt to add the browser extensions, the below error dialog should appear: ========= The sample epmp files can be found attached in this Knowledge Article.
View full article
Question Why is there no block message from Idira EPM when a .bat script is blocked? Answer Idira Endpoint Privilege Manager (EPM) can apply block actions based on two types of events:  FILEOPEN  and  PROCSTART . However, customers may notice that when a  .bat  script is blocked, no block dialog appears. This behavior is expected and stems from how the operating system interacts with EPM and how EPM is designed to handle these events.   EPM can enforce block on both FILEOPEN  and  PROCSTART  events. However, the logic for displaying block dialogs differs between the two. Whether a block is applied—and whether a dialog is shown—depends on how EPM policies are configured and prioritized. Some policies may block silently without user notification.   The operating system often performs multiple  FILEOPEN  actions when attempting to launch a script. The number of  FILEOPEN  attempts is unpredictable and can be excessive. Applications like Windows Explorer may trigger many  FILEOPEN  events during a single user action (e.g., double-clicking a  .bat  file). To avoid overwhelming users with multiple dialogs, EPM limits dialog display for  FILEOPEN  events.   The absence of a block dialog when a  .bat script is blocked is a result of EPM’s design to balance security enforcement with user experience. 
View full article
Question Is it acceptable to leave the Agent ID in a golden image? Answer No, it is not recommended.   When preparing a golden image for deployment, it’s important to ensure that the Idira EPM Agent ID is not retained in the image. Leaving the Agent ID intact can lead to duplicate identifiers across cloned machines, which may interfere with agent tracking, policy enforcement, and cloning detection mechanisms.   To ensure accurate detection of cloned systems and maintain endpoint uniqueness remove the Agent ID before capturing the golden image. This approach ensures that each deployed machine receives a unique Agent ID, enabling Idira EPM to function as intended and detect cloning events reliably.   Note: We are actively working to detect cloned machines. If cloning is detected, we change the Agent ID. However, to ensure consistency and avoid detection gaps, it is safer and more effective to remove the Agent ID before creating the golden image.
View full article
  • 234 Posts
  • 9 Subscriptions