How does the CrowdStrike Identity Analyzer help administrators identify users with stale passwords that have not been changed for an extended period?

Question

Options

• AThrough automated password expiration enforcement.
• BBy integrating with the cloud provider's activity logs to extract password change timestamps.
• CUsing the Stale Credential Detection feature.
• DBy generating periodic reminders to users to update their passwords.

• A
  3% (1)
• B
  7% (2)
• C
  90% (27)

Explanation

Option A: Password expiration enforcement is a policy-driven mechanism, not a detection feature. The question specifically asks about identifying stale passwords, not enforcing policy compliance. Option B: While integration with cloud provider logs is part of the Identity Analyzer's capabilities, this approach alone does not detect stale passwords effectively. Additional processing, such as the Stale Credential Detection feature, is required to analyze and identify such users. Option C: The Stale Credential Detection feature of the CrowdStrike Identity Analyzer proactively identifies credentials, including passwords, that have not been updated within a specified time period. This is the most accurate and direct solution for the scenario. Option D: Sending reminders may encourage users to change passwords, but it is not a detection mechanism for stale passwords. The question is about identifying stale credentials, not prompting

No community discussion yet for this question.