Launching scans

🍳 Selecting a source

Initiate a scan on any source, and elba will identify potential security issues for your teams. For every source scanned, the process will encompass all available apps. Below is a list of the apps available for each source:

  • Google: Data Protection, 3rd Party Apps, Authentication
  • Slack: Data Protection
  • Confluence: Data Protection
  • Github: 3rd Party Apps
  • M365: 3rd Party Apps
  • Dropbox: Data Protection, 3rd Party Apps

For more detailed information on how elba stores data during scans, please click here. For additional details regarding the required scopes for each source, please click here.

‍

🤝 Granting permissions

Our scans rely on API calls and we need to be granted some scopes for every source.

‍

🛫  Solving users inconsistencies

We need to link your source userbase with elba users, so we can assign and send them the potential security issues. We perform an automated matching based on the email address, but in some cases there might be some inconsistencies. If it happens, you’ll have to identify these users, either as elba users or as external users.

‍

‍

⏳ Waiting for the results

Our scan might take up to 3 days to perform if you have a large organization. But don’t you worry, you’ll be notified by email when your scan is over to check the results.