Sending Logs to a third party SIEM

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

Sending Logs to a third party SIEM

L4 Transporter

I am looking for documents to send the privilege cloud logs to a third party SIEM/provider.

 

Can I utilize the secure tunnel to do this or will this need to be done via REST API?

 

Are there any documents on this process?

1 accepted solution

Accepted Solutions

L7 Applicator

It's simple enough. Make sure secure tunnel can talk to siem, that you've liased with cyberark support so the correct translator file and event codes are set up, then configure secure tunnel.

 

Follow https://docs.cyberark.com/privilege-cloud-standard/Latest/en/Content/Privilege%20Cloud/privCloud-connect-siem.htm

And https://docs.cyberark.com/ispss-deployment/latest/en/Content/Privilege%20Cloud/privCloud-deploy-ST.htm#InstallandconfigureSecureTunnel

 

Note some domain names are blacklisted for forwarding siem traffic. If that's an issue, you could create a local dns entry and use that instead. The blocked domains are

 

The following domains cannot be used as host names for Secure Tunnel configuration:

 

*.aws.com

*.amazonaws.com

*.amazon.com

*.cyberark.com

*.cyberark.cloud

View solution in original post

4 REPLIES 4

L7 Applicator

It's simple enough. Make sure secure tunnel can talk to siem, that you've liased with cyberark support so the correct translator file and event codes are set up, then configure secure tunnel.

 

Follow https://docs.cyberark.com/privilege-cloud-standard/Latest/en/Content/Privilege%20Cloud/privCloud-connect-siem.htm

And https://docs.cyberark.com/ispss-deployment/latest/en/Content/Privilege%20Cloud/privCloud-deploy-ST.htm#InstallandconfigureSecureTunnel

 

Note some domain names are blacklisted for forwarding siem traffic. If that's an issue, you could create a local dns entry and use that instead. The blocked domains are

 

The following domains cannot be used as host names for Secure Tunnel configuration:

 

*.aws.com

*.amazonaws.com

*.amazon.com

*.cyberark.com

*.cyberark.cloud

L4 Transporter

Thank you for the information. The third-party provider will be outside of the internal network domain/network. Can the secure tunnel be configured to send the logs outside the internal network?

Yes you can. You just need network connectivity over the siem port from secure tunnel to your siem.

Thank you very much for your response.

  • 1 accepted solution
  • 329 Views
  • 4 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!