Webex Source

Cisco Webex is a cloud-based video conferencing and collaboration product suite, which comprises software including Webex Meetings, Webex Teams, and Webex Devices. This Webex source collects admin audit events and webhooks (meetings, rooms, messages, and memberships) data and sends it to Sumo Logic.

Data Source

Admin Audit Events
Webhooks
- Meeting
- Rooms
- Messages
- Memberships

Set up and Configuration

In this configuration, you will create a new Webex Integration App in Webex Develops Portal and generate a Client ID, Client Secret, and OAuth 2.0 authorization code.

Create a New Webex Integration app

A Webex Integration app with specific permissions is required for Sumo Logic to access Admin Audit Events from Webex. Follow the below instructions to create a new Webex Integration app.

Sign in to Webex Developers Portal using your admin account.
Click on your profile in the top right corner, and select My Webex Apps.
Click Create a New App.
Select Create an Integration and add the integration information.
- Integration name. Name of the integration (example: Sumo-C2C).
- Icon. Select an icon, either from default images or upload an image of your choice.
- App Hub Description. Description of the app (example: This App will be used for Sumo Logic Integration to collect Admin Audit Events).
- Redirect URI(s). Required to use https://localhost.
- Scopes. Check audit:events_read (only scope required for collecting admin audit events).
Now click Add Integration at the bottom of the page.
Copy and save the Client ID and Client Secret.
Copy and save the OAuth Authorization URL.

OAuth 2.0 Authorization Code

Follow the below instructions to generate OAuth 2.0 Authorization Code.

In a web browser, open a new tab and paste the OAuth Authorization URL that was copied from the earlier steps and click Enter.
It prompted, sign in to your admin Webex account.
Click Accept.
Ignore the error message in the webpage.

Copy and save the code in the URL, as shown in the following example.
```
https://localhost/?code={{REDACTED_AUTHORIZATION_CODE}}&state=set_state_here
```

Organization ID

Follow the below instructions to colllect your Organization ID.

Sign in to Webex Control Hub Portal using your admin account.
In the Management menu, select Account.
Navigate to the Info tab.
Copy and save the Organization ID.

States

Webex Source is a device security platform that discover devices, tracks behavior, detects threats, and takes action to protect your business. When you create an Webex Source, it goes through the following stages:

Pending. Once the Source is submitted, it is validated, stored, and placed in a Pending state.
Started. A collection task is created on the Hosted Collector.
Initialized. The task configuration is complete in Sumo Logic.
Authenticated. The Source successfully authenticated with Webex.
Collecting. The Source is actively collecting data from Webex.

If the Source has any issues during any one of these states, it is placed in an Error state.

When you delete the source, it is placed in a Stopping state. When it has successfully stopped, it is deleted from your Hosted Collector. On the Collection page, the Health and Status for Sources is displayed. You can click the text in the Health column, such as Error, to open the issue in Health Events to investigate.

Create Webex Source

When you create an Webex source, you add it to a Hosted Collector. Before creating the Source, identify the Hosted Collector you want to use or create a new Hosted Collector. For instructions, see Configure a Hosted Collector.

To configure an Webex source:

In Sumo Logic, select Manage Data > Collection > Collection.
On the Collection page, click Add Source next to a Hosted Collector.
Search for and select Webex.
Enter a Name for the Source. The description is optional.
(Optional) For Source Category, enter any string to tag the output collected from the Source. Category metadata is stored in a searchable field called _sourceCategory.
(Optional) Fields. Click the +Add button to define the fields you want to associate. Each field needs a name (key) and value.
- A green circle with a check mark is shown when the field exists in the Fields table schema.
- An orange triangle with an exclamation point is shown when the field doesn't exist in the Fields table schema. In this case, an option to automatically add the nonexistent fields to the Fields table schema is provided. If a field is sent to Sumo Logic that does not exist in the Fields schema it is ignored, known as dropped.
Client ID. Enter the Client ID collected from the new Webex Integration app.
Client Secret. Enter the Client Secret collected from the new Webex Integration app.
OAuth 2.0 Authorization Code. Enter the OAuth 2.0 Authorization Code collected from the URL.
Organization ID. Enter the Org ID fcollected from the Webex Control Hub PortalURL.
Select Event Categories for Audit Logs. You have the option to Collect all events or Select events, where you can specify the exact event categories you would like to collect from the admin audit logs. You can also select from the pre-defined list or type in event categories.
Click Save.

Error Types

When Sumo Logic detects an issue, it is tracked by Health Events. The following table shows the three possible error types, the reason for the error, if the source attempts to retry, and the name of the event log in the Health Event Index.

Type	Reason	Retries	Retry Behavior	Health Event Name
ThirdPartyConfig	Normally due to an invalid configuration. You'll need to review your Source configuration and make an update.	No retries are attempted until the Source is updated.	Not applicable	ThirdPartyConfigError
ThirdPartyGeneric	Normally due to an error communicating with the third-party service APIs.	Yes	The Source will retry indefinitely.	ThirdPartyGenericError
FirstPartyGeneric	Normally due to an error communicating with the internal Sumo Logic APIs.	Yes	The Source will retry indefinitely.	FirstPartyGenericError

Restarting your Source

If your Source encounters ThirdPartyConfig errors, you can restart it from either the Sumo Logic UI or Sumo Logic API.

UI

To restart your source in the Sumo Logic platform, follow the steps below:

Open the Collection page, and go to Manage Data > Collection > Collection.
Select the source and click the information icon on the right side of the row.
The API usage information popup is displayed. Click the Restart Source button on the bottom left.
Click Confirm to send the restart request.
The bottom left of the platform will provide a notification informing you the request was successful.

API

To restart your source using the Sumo Management API, follow the instructions below:

Method: POST

Example endpoint:

https://api.sumologic.com/api/v1/collectors/{collector_id}/sources/{source_id}/action/restart

Sumo Logic endpoints like api.sumologic.com are different in deployments outside us1. For example, an API endpoint in Europe would begin api.eu.sumologic.com. A service endpoint in us2 (Western U.S.) would begin service.us2.sumologic.com. For more information, see Sumo Logic Endpoints.

JSON Configuration

Sources can be configured using UTF-8 encoded JSON files with the Collector Management API. See how to use JSON to configure Sources for details.

Parameter	Type	Required	Description	Access
`config`	JSON Object	Yes	Contains the configuration-parameters of the Source.	n/a
`schemaRef`	JSON Object	Yes	Use `{"type":"Webex"}` for Webex Source.	not modifiable
`sourceType`	String	Yes	Use `Universal` for Webex Source.	not modifiable

Config Parameters

Parameter	Type	Required	Description	Access
`name`	String	Yes	Type the desired name of the Source and it must be unique per Collector. This value is assigned to the `metadata field _source`.	modifiable
`description`	String	No	Type the description of the Source.	modifiable
`category`	String	No	Type the category of the source. This value is assigned to the metadata field `_sourceCategory`.	modifiable
`fields`	JSON Object	No	JSON map of key-value fields (metadata) to apply to the Collector or Source. Use the boolean field `_siemForward` to enable forwarding to SIEM.	modifiable
`clientId`	String	Yes	Client ID of the Webex Integration created for Sumo Logic from the new Webex Integration app.	modifiable
`clientSecret`	String	Yes	Client Secret of the Webex Integration created for Sumo Logic from the new Webex Integration app.	modifiable
`code`	String	Yes	Code of the Webex Integration created for Sumo Logic.	modifiable
`orgId`	String	Yes	Orgaization Id of the customers Webex account from where you want to collect the audit event from.	modifiable

JSON Example

{
  "api.version":"v1",
  "source":{
    "config":{
      "name":"Webex- sandbox",
      "authorizationCode":"********",
      "clientId":"********",
      "collectAll":false,
      "orgId":"********",
      "eventCategories":["LOGINS","LOGOUT","ORG_SETTINGS"],
      "fields":{
        "_siemForward":false
      },
      "clientSecret":"********",
      "category":"sandbox/webex/audit"
    },
    "schemaRef":{
      "type":"Webex"
    },
    "state":{
      "state":"Pending"
    },
    "sourceType":"Universal"
  }
}

Data Source​

Set up and Configuration​

Create a New Webex Integration app​

OAuth 2.0 Authorization Code​

Organization ID​

States​

Create Webex Source​

Error Types​

Restarting your Source​

UI

API

JSON Configuration​

Config Parameters​

JSON Example​