Authentication

🔬 Findings

The goal of the Authentication app is to ensure that your team uses the most secure authentication methods to access their most critical SaaS applications. Upon initiating a scan (see here), elba will detect the following items:

Google

- Accounts without MFA activated

‍

📁 Browsing issues

Elba will create issues for every user who has not activated the strongest available authentication method for the given source (e.g., MFA for Google) and associate them with the owners of the respective accounts. It's important to note that, at this stage, no user will be notified.

‍

🏌 Activating check

Now that elba has scanned your source and you have reviewed the issues, it’s time to activate the check. Activating a check will engage your team in reviewing and addressing security issues for the specified source.

Users are notified about their security issues every Friday morning, in their weekly digest that computes all their pending actions on elba (see more here on Members notifications).

‍

🔔 User remediation

Users will be able to review the issue and take actions directly from their personal dashboard, in the ‘Checklist’ tab. They’ll be offered detailed context about the issue and guided on how to review it.

Given the critical importance of MFA for user security, the sole remedial action available is to activate MFA. Users will be guided to the relevant source to enable MFA from there.