Skip to main content

Cisco Webex Event Collector

This Integration is part of the Cisco Webex Teams Pack.#

Supported versions

Supported Cortex XSOAR versions: 6.12.0 and later.

Cisco Webex Event Collector fetches Events and Admin Audit Events and Security Audit Events. This integration was integrated and tested with version 1 of CiscoWebex API.

Configure Cisco Webex Event Collector on Cortex XSOAR#

  1. Navigate to Settings > Automation & Feed Integrations.

  2. Search for Cisco Webex Event Collector.

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

    ParameterDescriptionRequired
    URLTrue
    Admin APP Client IDAdmin APP Client ID and Secret.True
    Admin APP Client SecretTrue
    Admin APP Redirect URITrue
    Admin Org IdTrue
    Compliance Officer Client IDCompliance Officer Client ID and Secret.True
    Compliance Officer Client SecretTrue
    Compliance Officer Redirect URITrue
    Trust any certificate (not secure)False
    Use system proxy settingsFalse
    Fetch security audit eventsIn order to fetch security audit events, pro pack needs to be installed on the Webex instance.False
    Maximum number of events per fetchFalse
    1. Run the cisco-webex-oauth-start command with the user argument - you will be prompted to sign in to Cisco Webex with your username and password. (make sure you sign in with the same user as you defined in the user argument admin or compliance officer). You will then be redirected to the redirect URI you defined in the application. The URL will contain a query parameter called code. The value of this query parameter will be used in the next command.
    2. Run the cisco-webex-oauth-complete command with the user and code arguments The user argument should be set to the same value as in the previous command (admin or compliance officer). The code argument should be set to the value returned in the code query parameter from the previous command.
    3. Run the cisco-webex-oauth-test command with the user argument. The user argument should be set to the same value as in the previous command (admin or compliance officer) to ensure connectivity to Cisco Webex.

Commands#

You can execute these commands from the Cortex XSOAR 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.

cisco-webex-oauth-start#


Use this command to start the authorization process. In order to authorize the instance, first run the command, and complete the process in the URL that is returned. You will then be redirected to the callback URL where you will copy the authorization code found in the query parameter code, and paste that value in the command !cisco-webex-oauth-complete as an argument to finish the process.

Base Command#

cisco-webex-oauth-start

Input#

Argument NameDescriptionRequired
userThe user to start authorization. Possible values are: admin, compliance_officer.Required

Context Output#

There is no context output for this command.

cisco-webex-oauth-complete#


Use this command to complete the authorization process. After copying the authorization code found in the query parameter code of the callback URL, paste the value in the command as an argument to finish the process.

Base Command#

cisco-webex-oauth-complete

Input#

Argument NameDescriptionRequired
userThe user to complete authorization. Possible values are: admin, compliance_officer.Required
codeThe authorization code retrieved from the callback URL according to the documentation.Required

Context Output#

There is no context output for this command.

cisco-webex-oauth-test#


Use this command to complete the authorization process. After copying the authorization code found in the query parameter code of the callback URL, paste the value in the command as an argument to finish the process.

Base Command#

cisco-webex-oauth-test

Input#

Argument NameDescriptionRequired
userThe user to complete authorization. Possible values are: admin, compliance_officer.Required

Context Output#

There is no context output for this command.

cisco-webex-get-admin-audit-events#


Gets admin audit events from Cisco Webex.

Base Command#

cisco-webex-get-admin-audit-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
limitMaximum number of events to return.Optional
since_datetimeDate in ISO format (2023-10-01T20:33:22.123Z) to return events from.Optional

Human Readable Output#

Admin Audit Events#

_timeactorIdactorOrgIdcreateddataidsource_log_type
2023-11-02T09:33:26.408Z4444442222222023-11-02T09:33:26.408ZactorOrgName: panw
targetName: panw
operationType: CREATE
eventDescription: An org setting was created or updated.
actorName: admin@example.com
actorEmail: admin@example.com
settingKey: release_migration
settingName: release_migration
settingValue: "MIGRATED"
trackingId: 111111
previousValue: Null
targetType: ORG
targetId: 222222
actorUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/2.2.2.2 Safari/537.36
eventCategory: ORG_SETTINGS
actorIp: 1.1.1.1
targetOrgId: 222222
actionText: admin@example.com has modified the value of setting release_migration for ORG "panw". New value = "MIGRATED", Previous value = Null.
entityType: ORG
targetOrgName: panw
333333Admin Audit Events

Context Output#

There is no context output for this command.

cisco-webex-get-security-audit-events#


Gets security audit events from Cisco Webex.

Base Command#

cisco-webex-get-security-audit-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
limitMaximum number of events to return.Optional
since_datetimeDate in ISO format (2023-10-01T20:33:22.123Z) to return events from.Optional

Human Readable Output#

Security Audit Events#

_timeactorIdactorOrgIdcreateddataidsource_log_type
2023-12-19T07:01:26.486Z4444442222222023-12-19T07:01:26.486ZactorOrgName: panw
eventDescription: A user attempted logging in
actorName: admin@example.com
actorEmail: admin@example.com
authenticationMethod: Non-Interactive
trackingId: 123456
eventStatus: SUCCESS
actorOauthClient: 111111
actorUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36
eventCategory: LOGINS
actorIp: 1.1.1.1
actorClientName: Developer Portal
actionText: admin@example.com attempted logging into panw using client (Developer Portal) and Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36. Login status: SUCCESS.
failedReason:
333333Security Audit Events

Context Output#

There is no context output for this command.

cisco-webex-get-compliance-officer-events#


Gets events from Cisco Webex.

Base Command#

cisco-webex-get-compliance-officer-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
limitMaximum number of events to return.Optional
since_datetimeDate in ISO format (2023-10-01T20:33:22.123Z) to return events from.Optional

Human Readable Output#

Events#

_timeactorIdcreateddataidresourcesource_log_typetype
2023-11-05T13:33:46.417Z2222222023-11-05T13:33:46.417Zid: 333333
roomId: 444444
roomType: group
personId: 222222
personEmail: ksolberg@paloaltonetworks.com
personDisplayName: Kfir Solberg
personOrgId: 555555
isModerator: false
isMonitor: false
isRoomHidden: false
created: 2023-11-05T13:33:46.417Z
111111membershipsEventscreated

Context Output#

There is no context output for this command.