What to take away
A security finding can require several handoffs before it is resolved. Use four practical scenarios to evaluate the whole workflow, whether you choose separate tools or a connected platform.
Start with the job, then compare the handoffs
A training completion, an application visit and a permission change answer different questions. Evaluate them separately. For each scenario, record the source, the person responsible for the decision, the supported action and the evidence that the action took effect.
Use an authorised test environment and synthetic data for evaluation. These scenarios are questions to test, not a statement that every product or connector supports every action.
| Scenario | What to ask the reviewer to demonstrate |
|---|---|
| Broad file sharing | Identify the file and its current audience, obtain business context, and distinguish a requested change from permissions verified in the source. |
| Third-party application access | Show the actual OAuth grant or connected account. Keep a browser observation separate, and show the supported way to remove access. |
| AI use in the browser | State which enrolled browsers, prompt or upload types and configured controls are covered. Explain an unsupported case without presenting it as inspected. |
| Access review | Keep the review decision, the removal request and verified revocation distinct. Show how a manual action is tracked when the connector cannot perform it. |
Compare the tools you actually have
For awareness tools, inspect what follows a lesson or simulation. For DLP and posture tools, inspect how a finding reaches the person with business context. For native admin consoles, check the exact resource, permissions and licence required. For a connected platform, follow the same object through the complete journey rather than assuming a shared dashboard proves integration.
Google’s app-access documentation describes configured and accessed applications, OAuth scopes and access controls; its application lists can update after a delay. Microsoft’s access-review documentation distinguishes review roles and outcomes and lists licensing requirements. Use those source-specific limits when evaluating your own environment.
References: Google Workspace: control which apps access your data · Microsoft Entra: plan an access reviews deployment
Evaluate Elba on the same basis
Elba brings Data Protection, Apps & Access, AI Security and Security Awareness into one platform. Start with a workflow supported by your connected sources and enrolled browsers. In a demo, ask to see the finding, the relevant employee or administrator decision and the resulting source evidence. Coverage and available actions differ by integration; a proposed or pending action is not a verified result.
Evaluation checklist
Your checks stay on this page and reset when you reload it.
Sources & further reading
Primary documentation used to review this guide. Product settings and edition requirements can change; check the linked documentation before making changes.