Topic starter
27/06/2026 1:20 pm
TL;DR: Email remains an identity-adjacent control surface where governance, detection, and user trust still intersect, with on-demand Innovate 2025 event packages conference sessions on email security, enterprise threat trends, and customer-focused product usage, along with ISC2 CPE eligibility and practitioner discussion from CISOs and cybersecurity executives, according to Abnormal AI.
Editorial analysis by NHI Mgmt Group, based on content published by Abnormal AI: “Innovate 2025: Transforming Cybersecurity with AI”.
Key questions
Q: How should teams govern email-driven identity workflows?
A: Treat any workflow that starts in email as an identity process, not just a messaging process.
Q: Why do phishing and impersonation still matter to IAM programmes?
A: Because the attacker’s goal is often to influence an identity decision rather than break authentication directly.
Practitioner guidance
- Map email-driven identity workflows Inventory password reset, approval, and exception workflows that begin in email, then identify where a malicious message could trigger access changes or fraudulent escalation.
- Strengthen out-of-band verification Require secondary verification for sensitive requests that arrive by email, especially when they involve account recovery, privilege changes, or payment-related access.
- Review help desk decision paths Check whether support teams can approve access based on email alone, and remove any path that allows identity changes without independent confirmation.
Bottom line: Email security remains relevant to identity teams because the mailbox is often where access decisions begin, especially for resets, approvals, and exception handling.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 4 days ago by NHI Mgmt Group
27/06/2026 2:38 pm
Email security is part of identity governance, not a separate control silo: The article reinforces a pattern NHIMG sees repeatedly, which is that email is where identity intent is often first shaped. Approval fraud, account recovery abuse, and impersonation all rely on trust at the message layer before they ever reach authentication controls. The practitioner implication is to govern email-driven identity actions with the same discipline applied to access requests and privileged workflows.
A question worth separating out:
Q: How should security teams use conference insights without overrating them?
A: Use them to identify hypotheses, not conclusions. A practitioner should turn event themes into internal tests for detection coverage, support escalation paths, and user decision points, then compare those assumptions with actual logs and incident records. That keeps the programme grounded in evidence rather than vendor narration.
👉 Read our full editorial: Email security event insights that matter for identity teams
This post was modified 4 days ago by NHI Mgmt Group