Skip to main content

Slack Event Collector

This Integration is part of the Slack Pack.#

Supported versions

Supported Cortex XSOAR versions: 6.8.0 and later.

Slack logs event collector integration for XSIAM. This integration was integrated and tested with version v1 of Slack Audit Logs API.

Configure Slack Event Collector on Cortex XSIAM#

  1. Navigate to Settings > Integrations > Servers & Services.

  2. Search for Slack Event Collector.

  3. Click Add instance to create and configure a new integration instance.

    ParameterDescriptionRequired
    Server URLTrue
    User TokenTrue
    The product name corresponding to the integration that originated the eventsFalse
    The vendor name corresponding to the integration that originated the eventsFalse
    The maximum number of audit logs to fetchFalse
    First fetch time intervalData is not available prior to March 2018.False
    Trust any certificate (not secure)False
    Use system proxy settingsFalse
  4. Click Test to validate the URLs, token, and connection.

Commands#

You can execute these commands from the Cortex XSIAM CLI, as part of an automation, or in a playbook. After you successfully execute a command, a DBot message appears in the War Room with the command details.

slack-get-events#


Gets audit log events from Slack.

Base Command#

slack-get-events

Input#

Argument NameDescriptionRequired
should_push_eventsIf true, the command will create events, otherwise it will only display them. Possible values are: true, false. Default is false.Required
limitNumber of results to return, maximum is 9999. Default is 10.Optional
oldestOccurrence time of the least recent audit event to include (inclusive). Data is not available prior to March 2018. Default is 3 days.Optional
latestOccurrence time of the most recent audit event to include (inclusive).Optional
actionName of the action.Optional
actorID of the user who initiated the action.Optional
entityID of the target entity of the action (such as a channel, workspace, organization, file).Optional

Context Output#

There is no context output for this command.

Command Example#

!slack-get-events action=user_login oldest="15 months ago" limit=1

Context Example#

{
"SlackEvents": [
{
"id":"0123a45b-6c7d-8900-e12f-3456789gh0i1",
"date_create":1521214343,
"action":"user_login",
"actor":{
"type":"user",
"user":{
"id":"W123AB456",
"name":"Charlie Parker",
"email":"bird@slack.com"
}
},
"entity":{
"type":"user",
"user":{
"id":"W123AB456",
"name":"Charlie Parker",
"email":"bird@slack.com"
}
},
"context":{
"location":{
"type":"enterprise",
"id":"E1701NCCA",
"name":"Birdland",
"domain":"birdland"
},
"ua":"Mozilla\/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit\/537.36 (KHTML, like Gecko) Chrome\/64.0.3282.186 Safari\/537.36",
"session_id": "847288190092",
"ip_address":"1.23.45.678"
}
}
]
}

Human Readable Output#

Slack Audit Logs#

actionactorcontextdate_createentityid
user_logintype: user
user: {"id": "W123AB456", "name": "Charlie Parker", "email": "bird@slack.com"}
location: {"type": "enterprise", "id": "E1701NCCA", "name": "Birdland", "domain": "birdland"}
ua: Mozilla\/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit\/537.36 (KHTML, like Gecko) Chrome\/64.0.3282.186 Safari\/537.36
session_id: 847288190092
ip_address: 1.23.45.678
1970-01-18 14:33:34type: user
user: {"id": "W123AB456", "name": "Charlie Parker", "email": "bird@slack.com"}
0123a45b-6c7d-8900-e12f-3456789gh0i2