What do you dislike about Falcon Identity protection?
I think Falcon Identity Protection could improve by having a stronger focus on identity management. It would be more valuable for IAM teams if it expanded beyond identity threat detection to include more day-to-day identity risk and access visibility. I'd like deeper insights into privileged access, service accounts, stale or excessive permissions, and identity changes across environments like Active Directory and Microsoft Entra ID. More detailed reporting on why an identity is high risk, the permissions or memberships contributing to that risk, and suggested remediation steps would also be helpful. Additional IAM-focused workflows, like easier tracking of privileged group changes and dormant accounts, and stronger integrations with Entra ID, Conditional Access, and identity governance tools, would enhance its usefulness. While it's effective at detecting identity-based threats, expanding its governance and access capabilities would make it even better for IAM teams. Review collected by and hosted on G2.com.
Recommendations to others considering Falcon Identity protection:
To enhance Falcon Identity Protection, consider expanding its focus on identity management and governance. This could include deeper insights into privileged access, service accounts, and identity changes across environments. Strengthening integrations with identity governance tools and providing more detailed reporting on identity risks would also be beneficial. Review collected by and hosted on G2.com.
What problems is Falcon Identity protection solving and how is that benefiting you?
I use Falcon Identity Protection for identity protection. It's easy to use with the GUI. It effectively detects identity-based threats but could enhance its value by focusing more on identity governance, access visibility, and remediation capabilities. Review collected by and hosted on G2.com.