Endpoint Privilege Manager (EPM) Articles
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
What is EPM's "Run with Elevated Privileges"?   This is a special right-click menu context which can be enabled on an individual basis for "Elevate if necessary" advanced policies.  If enabled in a policy, an end user can right click an app and choose "Run with Elevated Privileges", which will elevate that app and it's child processes.  In addition, EPM's "Run with Elevated Privileges" has the effect to elevating file open/save dialogs.  If the app is not covered by an elevate if necessary policy that has the option enabled, then EPM's right click menu content will not be visible. Steps How can "Run with Elevated Privileges" be enabled in a "Elevate if necessary" policy?   In the "End User UI section" of an "Elevate if necessary" policy, set "Add elevation option to Windows Explorer context menu for applications" to "On"      What is the difference between EPM's "Run with Elevated Privileges" right click context and Windows' built in "Run as administrator" right click Context?   The two are similar, but not identical.  EPM's "Run with Elevated Privileges" applies to child processes.  EPM's "Run with Elevated Privileges" has the effect to elevating file open/save dialogs; Windows' "Run as administrator" does not do this by default.     How can I make end user experience be identical regardless if they use "Run As Administrator" or "Run with Elevated Privileges"?   Create the advanced policy for the app.  Set the policy action to "Elevate if necessary policy".  Create a definition in the policy for the app.  In this definition, uncheck the option "Do not elevate Open File and Save file dialogs" and check the option "include child processes".  In the "End user UI" section of the policy, for both administrative and standard users, set "Prompt users when elevation is necessary" to "Dialog", then choose the desired dialog.  This is changed on a per-policy basis, and is not a global setting.     If I want to use EPM's "Run with Elevated Privileges" right click context, how can I keep users from being confused with the built in "Run as administrator" right-click context?   You can remove the built in "Run as administrator" right-click context by doing the following: EPM Console > Advanced > Agent Configuration Edit the general configuration or create a custom configuration for just select endpoints. Set "Hide Windows Run As... menu items" to On.   How can I change the what is displayed to the end user, in the right click menu context? You can change  "Run with Elevated Privileges" to whatever you want to display by doing the following: EPM Console > Advanced > Agent Configuration Edit the general configuration or create a custom configuration for just select endpoints. Edit the "Shell elevate menu text" setting. How can I use vf_policies.xml to identify if "Run with Elevated Privileges" is enabled in a policy definition? The setting appears as shellExtension="True" when enabled in a policy definition  
View full article
In this article, we will share some frequent questions related to how often the EPM Agent checks in with the console. Steps These are some frequent questions related to how often the EPM Agent checks in with the console:   Q: If the EPM agent is reinstalled, will the agent check in automatically with the console once its reinstalled? A: Yes. It needs to go through a re-registration process on the SaaS back end and then should sync policies momentarily after that. Q: When a computer is powered on, does the agent sync to the console? A: Yes, after the Windows vf_agent service starts and the network is established. * see below Q: When the computer is resuming from sleeping mode, does the agent will sync to the console? A: Yes * see below Q: When the agent has been disconnected from the network, once reconnected will it sync to the console? A: Yes * see below * EPM Agents are always checking on a 30-second interval to see if they can communicate with EPM SaaS. This interval was previously a setting that could be adjusted in (EPM > Advanced Server Configuration). However, now it can not be modified. Realistically, it should be about a minute or so because the agent needs to establish long polling/connectivity with EPM SaaS. After checking in to the console, the EPM agent may perform additional actions. Examples: - Perform agent registration if it has just recently been installed. - Upload events, based on the "Flush" interval configured in advanced agent configuration. - Download policy changes, dependent on settings configuration in the advanced agent configuration. - Process server instructions for actions such as moving sets, uninstalling, upgrading, etc.
View full article
Problem: When it comes to EPM’s main use cases, you make think first that its primary purpose is to manage application approvals while also denying authorized installation or access to malicious programs.  For example, do you want to be able to restrict your users to be able to access only specific Internet sites or be able to allow access to only specific network shares?  These are just a few uses that are possible with EPM.  Read on to learn more! Solution: EPM can also be leveraged to implement more granular access control and DLP like controls such restricting your applications to specific IP addresses and network shares.  When creating an advanced policy for allow, elevate, or elevate if necessary action types, there is an option called Application access control that can be turned on (off by default).   Steps Create an advanced policy from the EPM Console by selecting Policies > Create advanced policy button from within the set you are configuring. Include an appropriate name for the policy, select the correct platform (this feature is only support for Windows and macOS at this time).  Select the appropriate action (allow, elevate, or elevate if necessary) for the application and click on Continue. Next, complete the relevant Scope, Targets, Audit, and End user UI settings for the application and computer(s) that should receive this policy.  Under Options and expand the Application access control submenu. Turn on the Application access control option and define the appropriate resource type, such as restricting the application access to only specific IP addresses or restricting the application to access only authorized network shares. Enabling auditing and end user notifications are both recommended for events and end user management.  Click on the Create button at the bottom to create the new application policy. It is always recommended that policies are created and tested with a pilot group before applying to your production environment.
View full article
Problem: There will undoubtably be a time when an unhandled event needs to be evaluated and approved by the security team before the elevation request can be granted. Depending on your company’s review and approval process, this will likely take time to ensure said application is safe and meets the security requirements to allow it to execute. There may be scenarios where a decision needs to be made quickly due to a business impacting need to elevate the application.  What usually comes to mind first is to grant just-in-time (JIT) elevation on a temporary basis but is JIT really the right answer here?  JIT essentially grants the end user local administrator (LA) rights on the endpoint for that time duration.  Yes, you are limiting the exposure by limiting how long the user has LA rights for but a savvy person such as a developer may try to take advantage of the situation and do more than he/she was approved to do.  EPM events are logged during the JIT period but this may be overhead for the EPM admins to review.  Remember that JIT should only be used for break glass scenarios. So if not JIT then what is the recommended solution? Solution: A better and more secure approach is to request temporary access to an application by using an authorization code.  These authorization codes are generated by the EPM admin and are only applicable for the elevation of the specific application and only that.  The end user is still a standard user on the endpoint so there is no added risk compared to the access granted when JIT is enabled. Authorization codes can be requested directly from the End User UI when the application is trying to install or being elevated.  Authorization codes can also be generated proactively by the EPM admin and provided directly to the end user to enter in when prompted on-screen. This procedure can be integrated into your software request workflow using your current ticketing system as the mechanism to request and retrieve these authorization codes or any other methods used by your end users to contact IT support. Steps Our documentation explains how to configure this solution in detail.  Keep in mind that the OPAG tool is required in order to generate the authorization codes: https://docs.cyberark.com/EPM/Latest/en/Content/EndUser/RequestTempAuth.htm Lastly, if JIT is absolutely necessary, consider enabling the below Protect administrative user groups protection found under Agent Configuration settings.  Choosing the Set from all user and programs prevents a user that was elevated to a local administrator via a JIT policy to be able to add another local administrator account or change the password of an existing local account.  This essentially prevents the user from creating a backdoor account on the endpoint.
View full article
There is an internal limitation by the Windows Scheduler service that prevents processes that require elevated privileges from running even if Task Scheduler is targeted by an Elevate policy with included child processes. When the service is being executed through the Task Scheduler, the elevation token is not checked. This means that even if EPM elevates the task, it will not work. This still persists even if EPM Agent is not installed in the endpoint, and only works when an admin user is used for the scheduled task.
View full article
This guide will help you have the "Block Unhandled Applications" policy turned on and have your browser extensions approved in a whitelist.  When you turn this policy on, it blocks all JavaScript files from executing. We need to clear the browser extensions/add-ons as we would any application.   Steps In this article we will look at the Cisco Webex extension and the Google Chrome browser. To get the folder location of the Cisco Webex extension, when you go to the URL in the Chrome Store, when you select the extension, in the URL is the folder name. See image below. The underlined in red is going to be the folder name. We will need to create an advanced policy of "Allow" to have the browser extensions/add-ons to work properly. Sample for Cisco Webex extension select script: Filename contains ".js" (case insensitive) AND Location is in directory "%localappdata%\Google\Chrome\User Data\Default\Extensions\jlhmfgmfgeifomenelglieieghnjghma" with subfolders (case insensitive) This will allow all JavaScript files in the following location to run. If you want to put the name of each JavaScript file, you can. Be advised that some browser extensions/add-ons can have 4-12 of these JavaScript files. The above method is quicker and still locks down to the specific folder.  We also have to clear the install location otherwise it could still get blocked. Some browser extensions/add-ons use a .crx file for installing. They use a temporary location before moving the correct folder to the above location. This temporary location is used by all browsers such as Microsoft Edge and Mozilla Firefox. location is in directory "%localappdata%\temp\scoped*" (case insensitive) Saving this, the Cisco Webex will install properly and be available in the browser.  For an example of what the Cisco Webex would look like in the Microsoft Edge browser see below:  When you look at this one, the extensions folder is in relation to the Edge browser. Also notice that the folder name is different.   
View full article
The article will provide some steps you can take to troubleshoot why the wrong policy is applying. Generally, these are the reason another policy is applying instead of your desired policy: A) The unwanted policy has a higher priority. B) The unwanted policy has a definition with child processes enabled and it applies to the parent process. C) The desired policy has targeting that does not match. D) The desired policy has definition properties that do not match. E) The desired policy has condition settings which do not match. F) The unwanted policy has exactly the same priority as the desired policy. G) The endpoint has not downloaded the desired policy from the EPM SaaS server. Try to rule out each of the above possible causes until you narrow down the cause, Steps A) The unwanted policy has a higher priority. - Generate SupportInfo logs.  - Open the SupportInfo zip and open vf_agent_srv.trace using notepad.  Find the PROCSTART event for the process launch and get the name of the unwanted policy which is applying. - In the SupportInfo zip look in the trace subfolder.  Open vf_policies.xml using a web browser.  - Search for the name of your desired policy.  Then find the "order" of that policy, which is the priority - Search for the name of the policy which is actually applying on launch.  Check the "order" of that policy. - Lower "order" numbers have a higher priority.  So you can either confirm that this is the possible cause, or you can rule out this as the cause. B) The unwanted policy has a definition with child processes enabled and it applies to the parent process. - In the SupportInfo zip look at the PROCSTART event for the process launch.  - If you don't see "Inherited from" you can rule this out as a possible cause - If you see "Inherited from", then you need to find the parent process.  Look at "Parent=" and take that number.  Search backwards until you find a "PID=" number which matches.  Check if that PROCSTART process launch says "Inheritable".  If it doesn't saw "Inheritable" then keep repeating until you find the reason that the intended policy is not applying.  You can then consider if you should have child processes enabled on the policy definition/ C) The desired policy has targeting that does not match. - In vf_policies.xml, find the desired policy.  Check at the top of that policy's xml to see if there is any user or computer group targeting.  It may look like this: <UserGroupList> <User accountType="User">Domain\joe.smith</User> </UserGroupList> - check to see if it is matches the user who is launching the app - Note in the above example, there is no SID.  If you think this could be a possible cause you can use the EPM Admin Utility to add the targeting to the policy.  When you do this, it will attach the SID to the policy xml, making matching more reliable. - In the SupportInfo, you can search vf_agent_srv.trace for that username to see if any errors appear.   D) The desired policy has definition properties that do not match. - Get the details of the app or file by browsing to it using windows explorer.  Then right click > properties > EPM tab.   - in vf_policies., find the desired policy.  Then find ApplicationGroup id - Copy that application group ID.  Then search downwards for that ID to find the definitions that are in the policy.  Look through each definition's properties (file name, publisher, location, product, etc) to see if they match what is shown on the EPM tab - Note you could also just compare policies in the EPM console, since it is easier to read than looking through xml.  The benefit to just looking at the xml is you know that these are the policy settings the endpoint is using.. E) The desired policy has condition settings which do not match. - This is rarely used but if your desired policy has a schedule or other condition that doesn't match, it can cause a problem F) The unwanted policy has exactly the same priority as the desired policy. - If two policies have exactly the same priority, they may be chosen at random when the app launches.   G) The endpoint has not downloaded the desired policy from the EPM SaaS server. - If vf_policies.xml contains your policy and all of the expected definitions, this is not the issue.
View full article
Question Questions between long polling and traditional connection-based heartbeat method: 1. What is the difference between long polling and traditional connection-based heartbeat method? 2. Do the Agent logs indicate that which method is being used? 3. After the Agent switches to traditional connection-based heartbeat method, will the Agent switch back to long polling method? 4. How to determine the long polling and traditional connection-based heartbeat method URLs? Answer 1. By default, EPM uses “long polling” method: Once a persistent connection is established, the Agent will receive a 1 Byte heartbeat every 30 seconds. The “long polling” method is extremely traffic saving, but requires network equipment (proxy servers, firewalls, routers, etc.) that able to handle numerous live connections simultaneously. If the “long polling” method is not applicable, then EPM uses a traditional connection-based heartbeat method (1 KByte heartbeat every 30 seconds). It is designed to switch to traditional method if persistent connection is not available. 2. When the Agent service starts, this message regarding the What's Up-Long Polling Address can be seen:  CvfRegistrator::ExecuteCommand: INFO: WIU URL is [SERVERADDRESS]/VFLPWIU/.wiu?a=[AGENTID]&s=[SETID] If long polling method is working, the following message will appear periodically in the Agent trace: CvfWIU::_OnReadComplete: INFO: LP data received If traditional connection-based heartbeat method is used instead, the "LP data received" message will not be found. The following message will be seen when switching from long polling to traditional connection-based heartbeat method: CvfDispSender::_WhatsUpV2: Using WIU Version 1: [SERVERADDRESS]/VFWIU/wiu.ashx?a=[AGENTID]&s=[SETID]  3. Yes, on agent registration. Agent registration can happen after agent restart, rebooting of the endpoint and/or Server upgrade/long disconnection. 4. Long polling method URL: [SERVERADDRESS]/VFLPWIU/.wiu?a=[AGENTID]&s=[SETID] For example: https://na107.epm.cyberark.com/VFLPWIU/.wiu?a=52c0a5a5-c823-4107-b5e1-ec98027b9001&s=508de249-6f66-4f73-92d2-09fa259d6557 Connection-based heartbeat method URL: [SERVERADDRESS]/VFWIU/wiu.ashx?a=[AGENTID]&s=[SETID]  For example: https://na107.epm.cyberark.com/VFWIU/wiu.ashx?a=52c0a5a5-c823-4107-b5e1-ec98027b9001&s=508de249-6f66-4f73-92d2-09fa259d6557
View full article
Question If user changes 'Azure account' password (e.g., using PowerShell)? Will windows prompt appear to provide new password?   Answer Unlike the regular On-Prem AD, password sync for users does not happen in Azure infra machines. As long as user provides old password to login to the machine, the machine will accept it and allow the user to login to the machine. If user manually use new password to login to the machine/successful sync of new password in the end machine, then in next subsequent login it will not work with old password. This is the default behavior for Azure. Related articles: https://learn.microsoft.com/en-us/answers/questions/511358/azure-ad-user-password-reset-not-reflected-on-azur  
View full article
Steps For debugging and extra logging, add these parameters to the basic_psm.ini file on the PSM and restart the service:  EnableCredentialProviderLogging=Yes InitialTraceLevels=1,2,3,4,5,6,7    Then look in the Windows Event Logs > Application.  You may see error messages similar to the following: PSMCP248E: Failed to authenticate saml user. Reason: 1330 PSMCP269E Failed to open web interface, SAML feature is probably not installed.   You can use the reason code to investigate the authentication failure. The below web page gives a list of error codes and the reasoning behind them: https://learn.microsoft.com/en-us/windows/win32/debug/system-error-codes--1300-1699-   For the example above, error code 1330, mapped to 'The password for this account has expired.' And checking the PSMSAML user, the box was unchecked for 'password never expires' - after checking this box the issue was resolved.   Another common error is: PSMCP248E: Failed to authenticate saml user. Reason: 1385     Where the code 1385 maps to 'Logon failure: the user has not been granted the requested logon type at this computer.' - Then you can check the PSMSAML user has been added to the 'Allow log on locally' and 'Allow log on through Remote Desktop Services' GPO.      
View full article
Question Why does the EPM dialog background change to a different color?  Answer For default policies, EPM dialog "Launch with elevated privileges" is displayed on a secure desktop background. This appears in a black background and the end-user cannot click on anything else before interacting with the dialog. This is an expected behavior as the dialog now appears on the Secure Desktop (A Windows feature).This change is made as part of security improvements.   This information was mentioned in the release notes (Starting from 24.8 Version): https://docs.cyberark.com/epm/latest/en/content/release%20notes/rn-whatsnew24-8.htm#Behaviorchanges
View full article
Question What is the list of URLs that are currently used by the EPM console? Answer The below URLs are to be whitelisted currently to access EPM console. There may be other URLs to be whitelisted for other features in the future. 1. EPM Dispatcher URL - https://XXX.epm.cyberark.com/VFAGT/VfAgent.asmx For example, https://login.epm.cyberark.com/VFAGT/VfAgent.asmx 2. EPM Server URL - https://XXX.epm.cyberark.com/ For example, https://na129.epm.cyberark.com/ 3. S3 bucket URL (used for agent download) - URL depending on your current tenant region listed in https://community.cyberark.com/s/article/Outbound-firewall-rules-required-for-EPM-SaaS-Agents-to-connect For example, https://epm-downloads.s3.us-east-2.amazonaws.com 4. mix panel (It's used for statistic collection, it doesn't break functionality of EPM console) - https://api.mixpanel.com  
View full article
Question What cause EPM license overuse, and how can these causes be solved or resolved? Answer License overuse can be cause by a variety of factors: 1. The number of endpoints exceeds the number allowed on the license.     a. The customer would need to work with their sales team to get a larger license. 2. The customer has been uninstalling and reinstalling agents, which leaves a count against the license total for both the disconnected agent and the connected agent.     b. Go into the My Computers section of the EPM Set Configuration Console and delete the disconnected agents. If an existing agent is accidentally deleted it will not affect the agent, and the agent will show up in the console the next time it connects. 3. The customer is using non-persistent VDIs in a set not designed to handle them. Each time a machine is created a license is counted but not deleted when the non-persistent VDI is deleted. This could cause the license count to exceed the license total.     a. Put all of the non-persistent VDIs in a set created for them (this can be done at creation time by checking the ‘Is non-persistent VDI Set’, or an existing set can be converted by using this same option. NOTE: This action cannot be reversed). In this type of set the license value is decremented when the non-persistent machine is deleted.     b. You may have to manually delete the non-persistent machines previously created as per step number 2 when you make this change to get the license count below its set limit. You can use the script described in the following article (in on-premise configurations only) to remove duplicate named computers: https://community.cyberark.com/s/article/00005018 In all cases you can wait for the disconnected machines to reach the time limit for disconnected machines to be deleted.  The default is 30 days but can be shortened to as low as 2 days.  You can find this setting in your EPM Set Configuration Console at 'Advanced>Server Configuration>Configuration>Server Time Settings>Deletion (Days)’. But if more licenses continue to be used such as in item 3 then waiting for them to be deleted by the server may not work or take an excessive amount of time.  
View full article
How do I move an endpoint to another set post Agent version 21.6?   Steps There are three ways you can move an endpoint to another set post agent version 21.6.   You can use the EPM Console to perform the move. You can find the details and appropriate steps to do this in our online documentation at this URL under the heading “Move computers to a different set”: https://docs.cyberark.com/Product-Doc/OnlineHelp/EPM/22.8.0/en/Content/EPM/Server%20User%20Guide/My%20Computers.htm   You can uninstall the current agent manually or through the console and manually install the new agent downloaded from the new set. An alternative to manually installing the new agent would be to use a program like SCCM.   Upgrade or install (if same version) using the new Set’s configuration file and install key. You can use the upgrade or install commands from the online guide, https://docs.cyberark.com/Product-Doc/OnlineHelp/EPM/22.8.1/en/Content/Installation/Windows-InstallAgents.htm#Commandlineinstallation An alternative to manually upgrading/installing the new agent from the command line would be to use a program like SCCM.   NOTE: If you are working with an Agent version 21.4 and below, and are staying with an Agent below version 21.4 (such as working with on-prem EPM), then please refer to this Knowledge Base Article for instructions: https://community.cyberark.com/s/article/00004316  
View full article
Question Question 1: How does Windows EPM Agent ensure that the file is not tampered with by any unknown method? For example, the set administrator has created an Allow policy for publisher Adobe Inc. If the unknown file's signature is tampered with and changed from Test Inc. to Adobe Inc., will the Allow policy be applied to this unknown file?   Question 2: How does macOS EPM Agent verify the publisher too?   Answer Answer 1: In general, Windows EPM Agent uses standard Windows publisher verification method winverifytrust. https://learn.microsoft.com/en-us/windows/win32/api/wintrust/nf-wintrust-winverifytrust Additional info on how it works exactly could be found on Microsoft resources. If someone could circumvent the whole system of trust on Windows, it would be a worldwide issue that affects everyone.   Answer 2: For macOS devices, macOS Agent verifies the publisher of the applications via Gatekeeper. Please refer to this Apple document for more information: https://support.apple.com/en-sg/guide/security/sec5599b66df/web 
View full article
Problem Statement A known issue with Azure architecture is that when the password is changed using the Azure portal, It does not sync with the Azure-joined endpoint immediately and takes some time.   Azure mentioned entering the new password in the Azure-joined endpoint to validate the password with the Azure server instead of local validation. This will update the endpoint to use the new password instead of old password.   How does it affect the Endpoint sign-in experience? Endpoint sign-in provides a passwordless log in experience in online mode. But when the endpoint is in offline mode, users must enter their password. Until the password is synced, users must enter their previous password. Steps Resolution To resolve this, the Azure admin adds a user attribute for the last password change date and time information ("lastpasswordchangedatetime"), as part of the token response. During online sign-in, EPM detects the password change and prompts for the new password. Use the following guidelines to add the extra attribute to the claim. Add user attributes to token claims in Microsoft Entra ID/Azure This section provides step-by-step instructions on how to add built-in user attributes to the token that Microsoft Entra ID sends to your application. Prerequisites Register the application with Microsoft Entra ID/Azure. Add the user in the application. Add Built-In Attributes to the Token   For Applications Using  OpenID Connect Sign in to the Microsoft Entra admin center. Navigate to Identity > Applications > Enterprise Applications. From the list, select the OIDC application to open its Overview page. Configure Single Sign-On : Under Manage, select Single Sign-on. In the Attributes & Claims section, select the Edit icon.   Add a Built-In Attribute to the Token as a Claim: On the Attributes & Claims page, select Add new claim. Enter a Name for the claim-  "lastpasswordchangedatetime". Next to Source, select Attribute, and then select the built-in attribute from the dropdown list- "user.lastpasswordchangedatetime". Save the Attribute: Select Save.   For SAML-Based Applications Sign in to the Microsoft Entra admin center. Navigate to Identity > Applications > Enterprise Applications. From the list, select the SAML-based application to open its Overview page. Configure Single Sign-On for SAML: Under Manage, select Single Sign-on. Select SAML as the single sign-on method. In the Attributes & Claims section, select the Edit icon. Add a Built-In Attribute to the Token as a Claim: On the Attributes & Claims page, select Add new claim. Enter a Name for the claim-  "lastpasswordchangedatetime". Next to Source, select Attribute, and then select the built-in attribute from the dropdown list- "user.lastpasswordchangedatetime". Save the Attribute: Select Save. Updating the Application Manifest to Accept Mapped Claims Sign in to the Microsoft Entra admin center. Navigate to the App Registration: Go to Identity > Applications > App registrations. Select your application in the list to open the application's Overview page. Open the Application Manifest: In the left menu, under Manage, select Manifest to open the application manifest. Modify the manifest: Find the acceptMappedClaims key and set its value to true. Select Save.     These steps enable you to successfully add built-in user attributes to the token claims in Microsoft Entra ID/Azure, which ensures that your application receives the necessary user attributes which will help EPM to detects the password change and prompts for the new password.  
View full article
Since macOS 14.2 \ 14.2.1 Printers pane needs another executable to be elevated in order to add a printer. Steps NOTE: This solution requires EPM v24.4 and above Sample policy available in the attachment(login required)   To add the printtool executable, create an advanced policy \ add to existing policy and add the following: Filename is exactly "printtool" (case insensitive) AND Location is in directory "/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/" with subfolders  (case insensitive) AND Publisher's signature is exactly {"Software Signing"} (case sensitive) AND Authorization rights is exactly {"system.print.admin"} (case sensitive)   Filename is exactly "AddPrinter" (case insensitive) AND Location is in directory "/System/Library/CoreServices/AddPrinter.app/Contents/MacOS/" with subfolders (case insensitive) AND Publisher's signature is exactly {"Software Signing"} (case sensitive) AND Authorization rights is exactly {"system.print.admin"} (case sensitive)   Filename is exactly "Print Center" (case insensitive) AND Location is in directory "/System/Applications/Utilities/Print Center.app/Contents/MacOS/" with subfolders (case insensitive) AND Publisher's signature is exactly {"Software Signing) (case sensitive) AND Authorization rights is exactly {"system.print.admin") (case sensitive)   System Preferences System Preferences in {"Printers & Scanners"} This will elevate printtool in addition to Printers pane and will allow the elevation of the Printers pane to add printers\delete\control.
View full article
Question What could be a possible cause of these errors in the vf_agent_srv.trace logs: 2024.08.12 15:10:44 PID:6162 TID:1598 CvfDecryptAES::CvfDecryptAES: NG_CRYPT: CvfDecryptAES succeed 2024.08.12 15:10:44 PID:6162 TID:1598 CvfMsGraphClient::AuthenticateAndConnect: AZR: INFO: Azure-Portal-Authenticate: Decrypted AZCSE 2024.08.12 15:10:44 PID:6162 TID:1598 CvfWinHttpRequest::_SetProxy: AZR: INFO: use Proxy Server 'proxy.domain.com:9400' and Proxy Bypass ''. 2024.08.12 15:10:44 PID:6162 TID:1598 CvfWinHttpRequest::SendRequestData: AZR: ERROR: Connection not established, status: 401 Answer The secret key in the Azure portal does not match the EPM Advanced Agent Configuration The secret key in the Azure portal is expired NOTE: THERE COULD POSSIBLY BE OTHER REASONS FOR THE 401 ERROR
View full article
The purpose of this article is to provide guidance as to what should be looked at and evaluated to ensure that EPM is being used effectively.  We receive requests regularly to perform health checks but every environment is different and the term “health check” is very broad and hard to quantify.  There are, however, some baseline checks that you can perform yourself to better understand how you’re currently doing from an adoption standpoint   Steps Use the following guidelines to determine the general health of your EPM journey.  For a refresher of EPM concepts, see our EPM Video Nugget Playlist!  These are short and concise 3-5 minute videos of key topics to level up on your EPM knowledge so you can get the most out of the solution. Agent Management Keeping a close eye on the number of agents deployed and making sure you do not have more agents deployed than what you are licensed for (over provisioned).  When over provisioned, currently applied policies are still in effect so the endpoints are protected but you will not be able to edit any existing policies or create new ones. Have a good upgrade plan to ensure agents are routinely updated based on your software upgrade policy.  We recommend, at a minimum, to upgrade once or twice a year to keep agents supported.  Agents that are more than one year old are technically unsupported by CyberArk. Privilege Management Handling least privilege should be considered the first objective in the EPM journey.  It is important that this phase be completed first before the other default policies are enabled.  Completing this phase means handling as many unhandled events as possible via policy. Leveraging QuickStart policies can help speed up this phase as well as ensuring business continuity.  There are two Video Nuggets dedicated to QuickStart! Privilege management is not complete until all named local administrator accounts are removed from the endpoints.  Even just one account in the Local Administrator group can result in lateral and vertical movement if compromised!  Run the Users in Local Administrators Group (predefined) report to determine what accounts have local administrator access.  Reports can be run from the EPM console. When least privilege is complete, there will be far less unhandled events to deal with, making it an easier effort to process new events data when the other default policies are enabled.  At this point, consider activating the Remove local administrators default policy to ensure all endpoints with the EPM agent are secured. JIT elevation requests is not meant to be a replacement for local administrator access and should be used for temporary elevation only.   JIT requests should be monitored regularly to identify trends and policies should be created for recurring JIT requests.  Run the Events (predefined) report to get more insight into your JIT requests.  Work to keep JIT requests to a minimum. Granular Application Control Following least privilege, you can then focus on enabling default policies one-by-one in the following recommended order: Applications downloaded from the internet Threat protection Granular application control Ransomware protection When multiple default policies are enabled at once, a large number of events are generated, making it a difficult and overwhelming task to handle.  Instead, enable only one default policy and start with Detect, then Restrict, and finally Block mode.  In each mode, evaluate the Events Management inbox and add exceptions as needed, then proceed to the next mode.  Once in Block mode, you can then proceed to the next default policy and repeat the process and work towards enabling Block mode.  Once all remaining default policies are enabled and in Block mode, you are in the desired default deny state. Use the Events details (predefined) report to investigate what applications are triggering these events.  In Excel, use filters on the eventType column of this report to view events specific to each of these default policies: Control unhandled applications downloaded from the internet – eventType DetectAccess, sourceType Internet Privilege Threat Protection – eventType AttackAttempt and SuspiciousActivityAttempt Control unhandled applications – eventType Launch Protect against ransomware – eventType Ransomware, sourceType Internet Use the information from the Events details report to add exceptions or explicitly block applications in order to drive down the number of unhandled events.  The Events Management inbox should be regularly reviewed to control the number of unhandled events.  In summary, these guidelines should help you determine where you are in the EPM journey as well as how to progress to the next phase.  Leverage the built-in EPM reports to assess your overall health and where to focus in strengthening your endpoint security.
View full article
Question Where to check Applocker logs? Answer The AppLocker log contains information about applications that are affected by AppLocker rules. Each event in the log contains detailed info about: Which file is affected and the path of that file Which packaged app is affected and the package identifier of the app Whether the file or packaged app is allowed or blocked The rule type (path, file hash, or publisher) The rule name The security identifier (SID) for the user or group identified in the rule Review the entries in the Event Viewer to determine if any applications are not included in the rules that you automatically generated. For instance, some line-of-business apps are installed to non-standard locations, such as the root of the active drive (for example: %SystemDrive%). For info about what to look for in the AppLocker event logs, see Monitor app usage with AppLocker. To review the AppLocker log in Event Viewer Open Event Viewer. In the console tree under Application and Services Logs\Microsoft\Windows, click AppLocker. The following table contains information about the events that you can use to determine which apps are affected by AppLocker rules. TABLE 1 Event ID Level Event message Description 8000 Error Application Identity Policy conversion failed. Status *<%1> * Indicates that the policy was not applied correctly to the computer. The status message is provided for troubleshooting purposes. 8001 Information The AppLocker policy was applied successfully to this computer. Indicates that the AppLocker policy was successfully applied to the computer. 8002 Information *<File name> * was allowed to run. Specifies that the .exe or .dll file is allowed by an AppLocker rule. 8003 Warning *<File name> * was allowed to run but would have been prevented from running if the AppLocker policy were enforced. Applied only when the Audit only enforcement mode is enabled. Specifies that the .exe or .dll file would be blocked if the Enforce rules enforcement mode were enabled. 8004 Error *<File name> * was not allowed to run. Access to <file name> is restricted by the administrator. Applied only when the Enforce rules enforcement mode is set either directly or indirectly through Group Policy inheritance. The .exe or .dll file cannot run. 8005 Information *<File name> * was allowed to run. Specifies that the script or .msi file is allowed by an AppLocker rule. 8006 Warning *<File name> * was allowed to run but would have been prevented from running if the AppLocker policy were enforced. Applied only when the Audit only enforcement mode is enabled. Specifies that the script or .msi file would be blocked if the Enforce rules enforcement mode were enabled. 8007 Error *<File name> * was not allowed to run. Access to <file name> is restricted by the administrator. Applied only when the Enforce rules enforcement mode is set either directly or indirectly through Group Policy inheritance. The script or .msi file cannot run. 8008 Error AppLocker disabled on the SKU. Added in Windows Server 2012 and Windows 8. 8020 Information Packaged app allowed. Added in Windows Server 2012 and Windows 8. 8021 Information Packaged app audited. Added in Windows Server 2012 and Windows 8. 8022 Information Packaged app disabled. Added in Windows Server 2012 and Windows 8. 8023 Information Packaged app installation allowed. Added in Windows Server 2012 and Windows 8. 8024 Information Packaged app installation audited. Added in Windows Server 2012 and Windows 8. 8025 Warning Packaged app installation disabled. Added in Windows Server 2012 and Windows 8. 8027 Warning No Packaged app rule configured. Added in Windows Server 2012 and Windows 8. Source: https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-application-control/applocker/using-event-viewer-with-applocker
View full article
Question Why are the onboarded loosely devices not rotating automatically as accordingly to the LCD policy (default 1 day)? Answer There is a misconception on the duration set in the LCD policy. The "Connection retrial interval" parameter from the LCD policy refers to the minimum time between attempts by the agent to access the PVWA Server. This means that the EPM Agent takes roughly 1 day (default setting) to check with PVWA whether there is a temporary password to be rotated, NOT the required period for the password change in Vault. Like all other CPM plugins, the Windows / MacOS Loosely Device platform follows the Master Policy unless there is specific policy rule(s) set in Policy by Platform. The 2 main rules/parameters to be checked are: - Require password change every X days [Policies > Policy By Platform > Windows / macOS Loosely Device (or the correct LCD platform name) > Policy Rule] https://docs.cyberark.com/pam-self-hosted/latest/en/Content/PASIMP/Working-with-Master-Policy-Rules.htm#PasswordManagement - HeadStartInterval (Target Account Platform > Automatic Password Management > Password Change) https://docs.cyberark.com/pam-self-hosted/latest/en/Content/PASREF/Automatic%20Password%20Management%20-%20Password%20Change.htm?tocpath=Administrator%7CReferences%7CConfigure%20the%20system%20through%20PVWA%7CPlatform%20properties%7CAutomatic%20Password%20Management%7C_____4 Using these 2 settings as an example, if the password change is to occur in every 2 days, set the "Require password change every X days" parameter to 7 days and "HeadStartInterval" property to 5 days.  
View full article
Question Please explain the expected behavior of the "Application Coverage by Policies" in the EPM Console.   Answer The following information was is based off behavior of EPM Console version 24.5.1.4050 If a policy is inactive, the "Application Coverage by Policies" still considers the application to be "handled" If a policy was deleted or is inactive but the application still exists in a custom application group (EPM > Policies > Application Groups), "Application Coverage by Policies" considers the application to be handled. This is shown in the "Application Coverage by Policies" as... Priority: 1 Action: N/A Type: Custom application groups   Note: This entry always shows as "inactive" Source Type "OldApplication" means it was installed before the EPM Agent  "Application Coverage by Policies" data is calculated based on current data of application catalog (which has retention of 2 years total) The "Application Coverage by Policies" report data itself has retention of 3 months since the last time the "Analyze coverage" button was clicked. When you delete the custom application group and perform a new "Analyze coverage", the custom application group shown in the pane on the right should now be cleared out. However, on the main "Application Coverage by policies" screen, the application can still be shown as "Handled". This is because the deletion or changing of a policy is not immediate and can vary by several minutes. 
View full article
Question In the Events Management, sometimes pure number (without + sign) is shown in each event. Sometimes, it has + sign displayed. For example, 9 computers vs 9+ computers. What are the circumstances that the number of computers in each event will show either a pure number or a number with + sign? Answer The + Sign indicates that large number of identical events having the same event type, file hash signature and policy arrived in short specified time from agents bringing sufficient information from collected events for policy creation. Therefore, EPM skips exact events and collect only the last events with the same Hash and Policy name (For example, TP policy name) as a "skipped event". This event holds the count of the skipped events. There might have been more computers reporting the same event that their events were skipped which is represented by the plus sign.  
View full article
For those macOS users who were previously using 'sudoers' file to source their PATH environment variable, there is a clever workaround for making additions to PATH without the need to edit /etc/sudoers.cyberark file that is used by EPM and should not be modified. Steps # Open text editor (vim/nano): vim ~/.zshrc # Scroll to the bottom of the file (SHFT+G in vim) # Type ‘i’ to insert PATH="$PATH:/path/to/env/var" # For instance: PATH="$PATH:/usr/bin/bash" # Save the file: :wq # Source the file running the following command: source ~/.zshrc # Confirm the change updates PATH by running the following command: echo $PATH
View full article
Question There are times where a policy will work when user is in the corporate network either at the office or on the VPN but stop working when they are off the network. This generally is caused by policies targeting users within them. If the user group was typed into the browse button, the users SID does not get embedded, and the agent has no one to determine group membership when not domain aware. In this example, note that the user is not a SID, this can cause an issue when a domain controller is not available, e.g. working remotely. Answer To resolve, edit policy in EPM console and browse using our AD picker (EPM Admin Tool) to intended target in the UI, instead of typing the name in manually.  Once that is done, you will see the SID in the vf_policies.xml file as seen below.  
View full article
Question How can I apply a Policy to the specific computer? Answer On Prem Server   In the EPM Console, right-click the Policy you want to apply. On the next screen, please select the computer on "Apply Policy to selected Computers in Set" For SaaS EPM Console: 1) Go to Policies 2) Click on the three dots to edit a policy 3) Scroll down to Targets 4) Select Edit for Computers in this set 5) If policy is for all, uncheck "Apply to All Computers" 6) Click on Add computers button 7) Check the box of computer from the list and select  Add 😎 Click on Done 9) Click on Save for the policy to apply to a computer
View full article
How can I identify if EPM is responsible for removing local administrators on a windows computer? Steps 1) Ensure more verbose logging is enabled EPM Console > Advanced > Agent Configuration > General > Policies > Trace policy usage on agents > Trace All Request Settings on the endpoint if a change was made to this setting 2) Check EPM logging Get a SupportInfo from an endpoint Open the "trace" subfolder and and then open "vf_agent_srv.trace" using notepad. Search for keyword RLUA Here is an example: 2022.08.03 12:52:31 PID:860 TID:6680 CvfPolicyRemLocalUsersTask::_BuildList2Remove: RLUA: INFO: Entry 4. SID=S-1-5-21-3795750040-3624707955-3994292918-1006. DnN=[HOST-5\localadmin2]. Queued for removal. 3) Use Windows Security Event Log If users are still being removed, but your EPM does not show logging or does not even have a policy to remove local administrators, you can do the following to show what is actually removing the users from the local administrators group.  The following is not enabled by default. Enable this group policy: Computer Configuration\Windows Settings\Security Settings\Local Policies\Audit Policy > "Audit account management" After local administrators are removed, check the Windows Security event log and filter by event ID 4799 Here is an example of the log entry when EPM removes the local administrator: Log Name: Security Source: Microsoft-Windows-Security-Auditing Date: 8/3/2022 1:03:30 PM Event ID: 4799 Task Category: Security Group Management Level: Information Keywords: Audit Success User: N/A Computer: host-5.domain.local Description: A security-enabled local group membership was enumerated. Subject: Security ID: SYSTEM Account Name: HOST-5$ Account Domain: DOMAIN Logon ID: 0x3E7 Group: Security ID: BUILTIN\Administrators Group Name: Administrators Group Domain: Builtin Process Information: Process ID: 0x35c Process Name: C:\Program Files\CyberArk\Endpoint Privilege Manager\Agent\vf_agent.exe   Note: Microsoft GPO can also be used to control the local administrator group.  If a Microsoft GPO is what is responsible for removing users from the local administrators group, you can expect to see the following process name in security event log EventID 4799: C:\Windows\System32\svchost.exe
View full article
Question What is the behavior of EPM when there is a "License Overused" error on the EPM console. Answer When you have more agents deployed than the license authorizes you, you will see license overused in the console. This will stop you from being able to create new policies and prevent policies updates to be pushed to the agents. Check the EPM console> My computers tab to see if there are duplicates agents, if there are duplicates, delete them. However, if there are no duplicates agents, customer will need to get a new license from their Account Executives. The following can be done to manage the situation before the new license is provided. 1. Uninstall agents that is not required 2. On the EPM console, My computer tab, delete disconnected agents from the list Note that when the deleted agent is online, the EPM console will register them back to My computer.
View full article
Question What is the minimum permission needed to retrieve a User Request Event using API, then use API to create a JIT policy?   Answer To get events to check for the "User Request" event you just need one role permission: Events > view events & files To create the JIT policy you just need one role permission: Policies > create
View full article
In EPM, when Agent Self Defense is turned off, often the Secure Token used to uninstall agents is forgotten. Agents not connected to the console (remote or other causes) do not get updated and are still protected by Agent Self Defense. Without the Secure Token these agents cannot be uninstalled through normal methods and a more manual method must be used (such as safe mode) to uninstall the EPM Agent. EPM now has a reminder pop-up to record the Secure Token when you disable Agent Self Defense.   Steps 1. Open your EPM Set Console. 2. Go to 'Advanced>Agent Configuration>General configuration>Edit Parameters>Agent self-defense'. 3. Click the box with the three ellipses and select 'Set to off'. 4. A pop-up box will appear with the reminder, and show you the Secure Token. 5. We recommend you copy this Secure Token and store it in a secure location. 6. Click the 'Set to off' button to complete the process, or click the 'Cancel' button to not turn off Agent Self Defense.
View full article
  • 234 Posts
  • 19 Subscriptions
Top Liked Posts in LIVEcommunity Article
Top Liked Authors