Send CyberArk Endpoint Privilege Manager logs to LogPulse

CyberArk EPM events (elevations, blocked and trusted applications, threat protection), the policy audit trail and the admin audit log.

In short
To send CyberArk Endpoint Privilege Manager logs to LogPulse, add CyberArk Endpoint Privilege Manager under Configure → Sources → Cloud. LogPulse reads the CyberArk EPM REST API itself, without an agent. Events land in the endpoint, audit indexes with source cyberark_epm and fill the Endpoint, Change data models.

Overview

How CyberArk Endpoint Privilege Manager data reaches LogPulse
Vendor
CyberArk EPM REST API
Collect
Integration pollerreads new events, maps the fields
Store
index=endpoint
index=audit
  1. CyberArk EPM REST API to Integration poller
  2. Integration poller to index=endpoint
  3. Integration poller to index=audit

LogPulse signs in to CyberArk Endpoint Privilege Manager with the credential you give it and fetches new events every five minutes by default. You can set the interval per integration, from one minute to 24 hours.

What you need

  • CyberArk EPM SaaS
  • An EPM user with local EPM authentication (not SAML)
  • In LogPulse: a role that may manage API keys. Cloud integrations fall under that right.

1. Create a credential in CyberArk Endpoint Privilege Manager

Field in LogPulseWhere you find it
EPM userAn EPM user with local EPM authentication and a role that may read events and the audit logs, such as Auditor.
PasswordStored encrypted and never shown again.
Application IDA name for this connection. EPM shows it with each logon.
Dispatcher (optional)Leave empty for login.epm.cyberark.com. EPM itself tells LogPulse which server your tenant is on.
Set ID (optional)Only when you want one set: its ID from the address bar of the EPM console.

2. Add the integration in LogPulse

Go to Configure → Sources → Cloud and choose CyberArk Endpoint Privilege Manager. Fill in the fields, tick the data sources you want and save. LogPulse first tests the connection with your credential and tells you what is wrong when it fails.

Tip: Secrets are stored encrypted and never shown again. To change one, paste a new value; the rest stays.

What arrives

Data sourceIndexSourceSourcetypeWhat it holds
Eventsendpointcyberark_epmcyberark:epm:raw:eventsElevations, blocked and trusted applications and threat protection.
Policy auditendpointcyberark_epmcyberark:epm:raw:policy:auditApplications that ran under a policy with auditing on.
Admin audit logauditcyberark_epmcyberark:epm:admin:auditChanges in the EPM console.

The index is the kind of data and the source is the product, so detection rules for that kind of data find CyberArk Endpoint Privilege Manager without changes.

Note: EPM SaaS only. The EPM user must use local EPM authentication, not SAML.
Note: Every set the user has a role in is read, up to 20, unless you fill in one Set ID.

Fields and data models

Data modelWhat you get
EndpointApplications with path, command line, hash, publisher, user and policy.
ChangeConsole changes: administrator, feature and address.

Field names follow the CIM field names. These are the fields LogPulse sets on CyberArk Endpoint Privilege Manager events; a field is left out when CyberArk Endpoint Privilege Manager did not send a value.

  • action
  • category
  • description
  • dest
  • dest_id
  • file_hash
  • id
  • justification
  • object_category
  • os
  • parent_process
  • parent_process_hash
  • parent_process_user
  • policy
  • policy_category
  • process
  • process_hash
  • process_name
  • process_path
  • process_publisher
  • run_as_user
  • session_id
  • set
  • signature
  • src
  • src_ip
  • user
  • user_is_admin
  • user_role
  • vendor_action

The original record of CyberArk Endpoint Privilege Manager is kept with each event under raw, so nothing the vendor sent is lost.

3. Check the data

The first events arrive within a few minutes. Check what came in:

earliest=-1h index IN (endpoint, audit) source IN (cyberark_epm)
| stats count by index, source, sourcetype

The integration page in LogPulse shows when it last read events and the last error, if any.

Troubleshooting

The connection test names what is wrong. These are the answers you are most likely to see.

What you seeWhat to do
CyberArk EPM refused the username, password or application ID.The user must sign in with local EPM authentication. A user that signs in through SAML or CyberArk Identity cannot be used.
The password of this EPM user has expired. Set a new one in EPM first.Sign in to the EPM console as that user, set a new password and paste it in the integration.
The user has no role in any set yet.Give the user a role that may read events and the audit logs, such as Auditor, in each set you want to read.
The test passes but no events arrive.Run the search above over a longer time. No results: check on the integration page that the data source is switched on and when it last read events. CyberArk Endpoint Privilege Manager may also simply have had nothing new.

Frequently asked questions

How do I send CyberArk Endpoint Privilege Manager logs to LogPulse?
Add the CyberArk Endpoint Privilege Manager cloud integration under Configure, Sources, Cloud in LogPulse and fill in EPM user, Password, Application ID. LogPulse reads the CyberArk EPM REST API itself, every five minutes by default; there is nothing to install.
Which permissions does LogPulse need in CyberArk Endpoint Privilege Manager?
CyberArk EPM SaaS. An EPM user with local EPM authentication (not SAML). Read access is enough for collecting logs.
Which index does CyberArk Endpoint Privilege Manager data go to?
The index is the kind of data: endpoint, audit. The source is the product: cyberark_epm. Each data source has its own sourcetype, listed on this page.
Which data models does CyberArk Endpoint Privilege Manager fill?
Endpoint, Change. Detection rules and dashboards written for a data model work on CyberArk Endpoint Privilege Manager without changes.