Skip to main content
All CollectionsHRM
Splunk integration with Right-Hand
Splunk integration with Right-Hand
K
Written by Karthek S
Updated this week

Table of contents.

Integrating using splunk application package download (Recommended for On-prem Splunk Deployments)

1. Download the application package

2. Upload the application package to the customer’s Splunk Instance

  1. Navigate to the Splunk home page.

  2. Click on the settings button placed on the left side of the screen, to manage apps.

  3. On the top right corner, click on Install app from file.

  4. Choose a file and Click on Upload.

3. Setup Application in Splunk

5. After Successful upload, the following screen will appear.

6. Click on Set up now.

7. The following screen will appear.

8. Copy token provided by Cyberready frontend for Splunk integration.

a) Log into the portal and navigate to HRM > Settings > Splunk > View configurations.

b) Once you click View configurations, click on Generate Token and then the copy icon to copy the token.

9. Paste the token into the form above and press the Submit button.

10. The following screen will appear.

Integrating with Splunk by installing the app from Splunk>cloud Apps

Find the Right-Hand app in splunk cloud

  • In the Splunk Console go to Apps --> Browse More Apps --> Type 'Right-hand' --> Hit Search button

  • Locate the App by Name "Right-hand Cybersecurity HRM App for Splunk" and click on Install after providing your splunk login credentials

  • Click on "Open the App" after successfully installing it

  • In the app configuration click on "Continue to app setup page"

  • You should now be navigated to this page

Generating a token and adding it in Splunk App for setup

  • Generate a splunk token from the Right-hand console using the steps below

    • In the Right-hand cybersecurity console navigate to Human Risk Management --> Settings --> Security Vendors

    • Locate Splunk

    • Click on Configure and generate and copy the token

  • Now copy the integration token and paste it in the Splunk Password field and click on Submit

  • Once the token is added the app should now appear in the installed applications in your Splunk console

Create an Alert and hook to Right-Hand Alert Action

  • A search query specific to logs being integrated is required here. You might need help from the SOC Team or RH Team to build this query.

NOTE: Make sure time span is set to All time (real-time)

  • Press the Search button, on the right corner of the search bar to verify that desired logs are appearing in the search, see the example below.

  • On the top-right corner, click on the Save As button and then the Alert option.

  • The Following Popup will appear, fill it with appropriate details.

NOTE: Set Alert type to Real-time and Expires to 365 days

  • Now click on the Add Actions button at the bottom. Find and select Right-Hand-Alert.

  • Click on the Save button.

  • The following screen will appear.

  • Click on View Alert to verify the alert settings. The following screen will appear.


NOTE: Make sure Alert is Enabled and Actions are set to Right-Hand-Alert.

Please refer to this article for the next steps in configuring the mapping attributes.

4. Events Supported by Right-Hand via Splunk integration

Fortinet Ensilo Events

  1. Malicious File (Fortinet Ensilo)

    This event is considered by Right-hand when following conditions are met in the received alerts

    rules list: Dynamic Code
    action: block

Netskope Events

  1. Malicious Website (Netskope)

This event is considered by Right-hand when following conditions are met in the received alerts

alert type: malsite
action: block

Crowdstrike Events

Refer this documentation to understand the conditions used to match crowdstrike events.

  1. Adware File (Crowdstrike)

  2. C2 Server Alert (Crowdstrike)

  3. Malicious Document (Crowdstrike)

  4. Spearphishing Attack (Crowdstrike)

  5. Ransomware (Crowdstrike)

  6. Suspicious Login (Crowdstrike)

  7. Suspicious Credentials File (Crowdstrike)

  8. Malware (Crowdstrike)

  9. Suspicious Remote Access (Crowdstrike)

  10. Unintended Java Download (Crowdstrike)

  11. Unintended Malicious Download via Browser (Crowdstrike)

  12. Unintended Malicious Download (Crowdstrike)

  13. Accidental Tool Download (Crowdstrike)

Mimecast Events

Refer this documentation to understand the conditions used to match crowdstrike events.

  1. Data Loss Prevention (Mimecast)

  2. Malicious Email Attachment(Mimecast)

  3. Impersonation Email(Mimecast)

  4. Malicious URL in Email(Mimecast)

  5. Credential Theft(Mimecast)

  6. BEC Email Alert(Mimecast)

  7. HTTP Policy Blocked Content(Island Browser)

Proofpoint Events

S. no

Detection Rule Name

Conditions

1

Imposter Threat directed at employee

  • has to be in messagesBlcoked array

  • classification: “Impostor (for BEC/Message Text threats)”

2

Malware sent to an employee via Email

  • has to be in messagesBlocked array

  • classification: “Malware”

  • threatType: NA

3

Spam directed at employee

  • has to be in messagesBlocked array

  • classification: “Spam”

4

Phishing Email directed at an employee

  • has to be in messagesBlocked array

  • classification: “Phish”

5

Unsafe Attachments sent to an employee via email

  • has to be in messagesBlocked array

  • classification: “Malware”

  • threatType: “Attachment”

6

URL redirecting to a site hosting malware sent to employee via Email

  • has to be in messagesBlocked array

  • classification: “Malware”

  • threatType: “URL”

7

Employee clicked on a URL containing Malware sent via an email

  • has to be in clicksBlocked array

  • classification: “Malware”

8

Spam Containing Unsafe Attachment Detected by Proofpoint

  • has to be in messagesBlcoked array

  • classification: “Spam”

  • threatType: “Attachment”

9

Employee clicked on a URL containing Phishing Link sent via an email

  • has to be in clicksBlocked array

  • classification: “Phish”

10

Employee clicked on a URL in a spam email

  • has to be in clicksBlocked array

  • classification: “Spam”

SentinelOne Events

Refer this documentation to understand the conditions used to match crowdstrike events.

  1. Malware Found on Employee’s Device

  2. Ransomware Found on Employee’s Device

  3. Trojan Found on Employee’s Device

  4. Potentially Unwanted Application Found on Employee’s Device

  5. Adware Found on Employee’s Device

  6. Virus Found on Employee’s Device

  7. Cryptomining Detected on Employee’s Device

  8. Malicious PDF Found on Employee’s Device

  9. Malicious Office Document Found on Employee’s Device





Did this answer your question?