- Supported Cloud Connectors
- Armis Cloud Connector
- AWS Cloud Connector
- AWS Multi-Tenant Cloud Connector
- Azure Cloud Connector
- Azure Cloud Connector Overview
- Azure Audit Source and Event Support
- Prerequisites to Configure the Azure Cloud Connector
- Configure the Azure Cloud Connector
- Collect EventHub Information for Azure EventHub Endpoints
- Collect all Microsoft Defender ATP Events
- Configure Azure to Monitor Security Center Events in Azure VMs
- Bitglass Cloud Connector
- Box Cloud Connector
- Centrify Cloud Connector
- Cisco AMP for Endpoints Cloud Connector
- Cisco Meraki Cloud Connector
- Cisco Umbrella Cloud Connector
- Citrix ShareFile Cloud Connector
- Cloudflare Cloud Connector
- Code42 Incydr Cloud Connector
- CrowdStrike Falcon Cloud Connector
- Cybereason Cloud Connector
- CylanceProtect Cloud Connector
- Dropbox Business Cloud Connector
- Duo Security Cloud Connector
- Egnyte Cloud Connector
- Fidelis Cloud Connector
- GitHub Cloud Connector
- Google Cloud Platform (GCP) Cloud Connector
- Google Cloud Pub/Sub Cloud Connector
- Google Workspace (Formerly G Suite) Cloud Connector
- LastPass Enterprise Cloud Connector
- Mimecast Email Security Cloud Connector
- Netskope Cloud Connector
- Office 365 Cloud Connector
- Okta Cloud Connector
- OneLogin Cloud Connector
- Palo Alto Networks SaaS Security Cloud Connector
- Ping Identity Cloud Connector
- Proofpoint Cloud Connector
- Rapid7 InsightVM Cloud Connector
- Salesforce Cloud Connector
- SentinelOne Cloud Connector
- ServiceNow Cloud Connector
- Slack App Cloud Connector
- Slack Classic App Cloud Connector (Formerly known as Slack Enterprise Grid Cloud Connector)
- Snowflake Cloud Connector
- Sophos Central Cloud Connector
- Symantec CloudSOC Cloud Connector
- Symantec Endpoint Protection (SEP) Mobile Cloud Connector
- Symantec Email Security.cloud Cloud Connector
- Symantec WSS Cloud Connector
- Tenable.io Cloud Connector
- VMware Carbon Black Cloud Endpoint Standard Cloud Connector
- Workday Cloud Connector
- Zoom Cloud Connector
- Custom Cloud Connector
- Webhook Cloud Connector
GitHub Cloud Connector
GitHub is a version control and collaboration platform that offers version control and source code management for developers to host, build software, review code, share, and manage projects. For more information visit their website.
Prerequisites to Configure the GitHub Connector
Before you configure the GitHub connector to monitor your enterprise GitHub server or cloud-based GitHub service, you must complete the following prerequisites:
Allow access to your GitHub server addresses over SSL
Generate a personal access token for the OAuth2 authentication method
Generate the Personal Access Token
To obtain a personal access token:
Log in to GitHub.
On your profile page, in the upper right corner, click the profile image, then click Settings.
In the left pane, navigate to Personal Settings > Developer Settings, then click Personal access tokens.
In the New personal access token section, assign the following token permissions for the connector to retrieve events:
repo – Select all the check boxes.
admin:org – Select the read:org check box.
user – Select the read:user check box.
Click Generate new token.
Copy the token, represented by a string of letters and numbers. Use this token to access GitHub API to complete the GitHub connector configuration.
Configure the GitHub Connector
GitHub is a version control and collaboration platform that offers version control and source code management for developers to host, build software, review code, share, and manage projects. For more information visit their website.
The following table displays audit source API and security events supported by the connector.
Audit Source: API | Service or Module Covered | Event Types | Event Included |
---|---|---|---|
Use the GitHub timeline API | Any | Events supported by GitHub timeline APIs | All GitHub event types and push to repository For more information about events supported by timeline API, see https://docs.github.com/en/rest/reference/activity The following types of repositories can be discovered by GitHub API:
Private repositories owned by an individual cannot be discovered by the GitHub API. |
To configure the GitHub connector to import data into Exabeam Cloud Connector platform:
Complete the Prerequisites to Configure the GitHub Connector.
Log in to the Exabeam Cloud Connectors platform with your registered credentials.
Navigate to Settings > Accounts > Add Account.
Click Select Service to Add, then select GitHub from the list.
In the Accounts section, enter the required information. Required fields are indicated with red bar.
Tenant – Select a tenant to attach to the connector if you are using the multi-tenant edition. Otherwise, select default.
Account Name – Specify a name for the GitHub connector. For example, GitHub_sourcecontrol.
(Optional) Description – Describe the GitHub connector. For example, GitHub cloud service for corporate source control.
Authentication Method – Select oauth2 from the list.
Personal Token: Enter the personal access token that you obtained while completing prerequisites.
Host Name – Enter the GitHub server host name.
Note
If you use enterprise GitHub server, enter GitHub server address. For example, mygithub.myorg.com If you use cloud based GitHub service, enter github.com.
To confirm that the Exabeam Cloud Connector platform communicates with the service, click Test Connection.
Click Done to save your changes. The cloud connector is now set up on the Exabeam Cloud Connector platform.
To ensure that the connector is ready to send and collect data, Start the connector and check that the status shows
OK
.