EPM: Manually collecting logs of Process Monitor (SaaS)

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

Welcome Idira to LIVEcommunity!

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

Meet Idira

Endpoint Privilege Manager (EPM) Articles
7 min read
L0 Member
No ratings

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.

Rate this article:
  • 3611 Views
  • 0 comments
  • 0 Likes
Article Dashboard
Version history
Last Updated:
‎11-05-2026 11:52 AM
Updated by: