Question 930
Scenario: Incident response discovers a malicious SaaS app with granted access to employees' mailbox data. Which mechanism should guide the administrative decision?
Explanation
Correct Answer
Defender for Cloud Apps app governance or OAuth policy controls can support revoking risky application grants. The case concerns revoke a compromised oauth integration: Incident response discovers a malicious SaaS app with granted access to employees' mailbox data. Application consent containment must address the granted permissions, not only the app display label. This answers the key interpretation of the requirement because it addresses the explicit constraint. The decisive check is inspect the affected app, tenant grant scope, and recent API activities before response. The corresponding implementation would be revoke the unsafe application consent and investigate data accessed with the prior token.
Incorrect Answers
OAuth risk concerns the permissions granted to applications, not just user interactive sign-ins. The reason this does not settle the present case is the actual condition: Defender for Cloud Apps app governance or OAuth policy controls can support revoking risky application grants.
Connected-app visibility relies on valid service integration and provider-specific APIs. The records needed for this specific case concern: Inspect the affected app, tenant grant scope, and recent API activities before response.
Cloud app audit conclusions must reflect connector coverage and the specific provider log fields. The current corrective requirement is: Revoke the unsafe application consent and investigate data accessed with the prior token.