logo

Database

Sentry Two Factor Not Required

Description

Detects a Sentry organization that requires neither two-factor authentication nor SSO, or whose SSO provider has the Require SSO option off, so its members can sign in with a password alone. A stolen or reused password is then enough to open a member's account and read the organization's issues and events, which carry stack traces, request data and details of the application's users. Sentry refuses to require two-factor authentication while SSO is set up, so for an organization with SSO the rule checks that Require SSO is on.

Weakness:

081 - Lack of multi-factor authentication

Category: Access Subversion

Detection Strategy

    • Reads the details of the organization through the Sentry API with an internal integration token that has the org:read scope and, only when the organization does not require two-factor authentication and has an SSO provider, reads whether that provider requires SSO

    • Reports the organization when it does not require two-factor authentication and has no SSO provider or one that lets members in without SSO; an organization that requires two-factor authentication, or whose SSO is required, is not reported

    • Records in the evidence require2FA, hasAuthProvider and, with an SSO provider, require_link; when a setting the rule needs is missing or is not true or false, or the SSO provider cannot be read, the rule is recorded as unreadable rather than reported as clean

    • Sentry leaves the second factor of the members who sign in through SSO to the identity provider, and its API does not show whether that provider asks for one, so multi-factor authentication has to be enforced at the identity provider

    • Reads the settings of the organization, not its members, so whether each member has a second factor of their own is not evaluated