Onboard Sentry ↗
SaaS Security connects to the Sentry API using a personal access token that you generate from a Sentry account. After connecting, SaaS Security scans your Sentry instance for misconfigured settings and account risks.
Note: The supported Sentry account plan for SaaS Security scans is the Business Plan.
The onboarding process requires the following credential:
| Item | Description |
|---|---|
| Personal Token | A personal access token generated from a Sentry account. This unique alphanumeric string gives SaaS Security read-only access to organization and member data for a Sentry organization. |
Step 1 — Generate a personal access token
- Identify the Sentry account you will use to generate the token.
Required permissions: No elevated permissions are required, but the account must be a member of the organization you want SaaS Security to scan.
- Open a browser to the Sentry login page and log in to the account you identified.
- On the Sentry dashboard, open the account drop-down menu in the upper-left corner and select Personal Tokens.
- On the Personal Tokens page, click Create New Token.
- Select the following permission scopes for the token:
- member:read
- org:read
- Enter a name for the token — for example, SaaS-Security-Integration-Token — then click Create Token.
- Copy the personal access token and save it to a text file.
Note: Do not proceed to the next step until you have copied the personal token. You must provide this token during the onboarding process.
Step 2 — Connect SaaS Security to Sentry
- Log in to Cortex.
- Select Settings > Data Sources and Integrations > Add New and click the Sentry tile.
- On the Capabilities tab, enter a name for this instance.
- Under Default Capabilities, confirm Security Posture is selected.
- Click Next.
- On the Connections tab, select Log in with Credentials and enter your personal token.
- Click Next.
- On the Configurations tab:
- Set the Sync Interval.
- (Optional) Add a Tag.
- Click Next to complete onboarding.