TL;DR: Four sources of activity show how far visibility now reaches, from Azure Files to Azure SQL, in Netwrix case work. Identity governance still depends on turning those logs into faster investigation and response, not just adding more event feeds.
Editorial analysis by NHI Mgmt Group, based on content published by Netwrix: “What's New in Netwrix Auditor 10.8: Maximize Visibility, Strengthen Security”.
Key questions
Q: Why do mailbox rule changes and mass deletions matter for IAM teams?
A: Because they often signal that a user or delegated identity is changing how information is hidden, retained or removed.
Q: How can teams tell whether observability is improving identity governance?
A: Teams can tell observability is improving governance when it changes decisions, not just dashboards.
Practitioner guidance
- Expand audit scope beyond core admin logs Include Azure Files, Exchange Online, Microsoft Copilot and Azure SQL activity in the identity monitoring baseline so investigations do not depend on a single service view.
- Prioritise risky mailbox and file events Treat mass deletions and inbox rule changes as high-priority signals because they can indicate concealment, delegated misuse or data removal.
- Measure investigation latency Track how long it takes analysts to move from event detection to a defensible decision, and use that metric to test whether visibility improvements are operationally real.
Bottom line: The core issue is not a lack of telemetry, but the gap between collecting identity-linked events and using them quickly enough to change a security outcome.
Glossary terms: Visibility-to-decision latency, Identity Telemetry, Audit coverage boundary, Governance-relevant activity
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Visibility is now an identity control surface, not a reporting feature. Netwrix is pointing at a problem practitioners already feel: if risky activity cannot be filtered, prioritised, and interpreted quickly, the organisation has telemetry but not control. In IAM and NHI programmes, that is the difference between observability and governance. The practical conclusion is that monitoring tools should be judged by whether they shorten decision time, not by whether they produce more events.
A few things that frame the scale:
- Two-thirds of enterprises have endured a successful cyberattack resulting from compromised non-human identities, with a quarter encountering multiple attacks, according to The 2024 ESG Report: Managing Non-Human Identities.
- Enterprises that have experienced a compromised NHI averaged 2.7 separate incidents in the past 12 months, which shows how quickly one identity weakness can become a repeatable pattern.
A question worth separating out:
Q: How can teams use AI-assisted activity data without overcomplicating governance?
A: Treat AI-assisted activity as another access path that can affect sensitive data, not as a separate governance universe. If Copilot or a similar assistant can trigger actions in storage or databases, the same ownership, review, and escalation rules should apply. That keeps the programme consistent and avoids blind spots.
👉 Read our full editorial: Netwrix Auditor 10.8 adds visibility gaps identity teams need to watch
Visibility is now an identity control surface, not a reporting feature. Netwrix is pointing at a problem practitioners already feel: if risky activity cannot be filtered, prioritised, and interpreted quickly, the organisation has telemetry but not control. In IAM and NHI programmes, that is the difference between observability and governance. The practical conclusion is that monitoring tools should be judged by whether they shorten decision time, not by whether they produce more events.
A few things that frame the scale:
- Two-thirds of enterprises have endured a successful cyberattack resulting from compromised non-human identities, with a quarter encountering multiple attacks, according to The 2024 ESG Report: Managing Non-Human Identities.
- Enterprises that have experienced a compromised NHI averaged 2.7 separate incidents in the past 12 months, which shows how quickly one identity weakness can become a repeatable pattern.
A question worth separating out:
Q: How can teams use AI-assisted activity data without overcomplicating governance?
A: Treat AI-assisted activity as another access path that can affect sensitive data, not as a separate governance universe. If Copilot or a similar assistant can trigger actions in storage or databases, the same ownership, review, and escalation rules should apply. That keeps the programme consistent and avoids blind spots.
👉 Read our full editorial: Netwrix Auditor 10.8 adds visibility gaps identity teams need to watch
Visibility is now a control problem, not a reporting problem. Netwrix is pointing at a familiar but still under-solved gap: teams often have logs, yet they do not have operational visibility into the actions that matter most for identity governance. When file activity, mailbox changes, AI-assisted usage and database events live in separate audit views, the security team inherits delay instead of decision support. The practitioner conclusion is simple: visibility only has value when it shortens the time to action.
A few things that frame the scale:
- Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: What should security teams do when AI-assisted activity falls outside the monitoring model?
A: Bring AI-assisted actions into the same audit and response workflow as other identity-linked events. If Copilot usage can influence access, content handling or data queries, it belongs in the investigation path. Otherwise teams will keep a blind spot exactly where new operational behaviour is emerging.
👉 Read our full editorial: Auditor 10.8 expands identity visibility beyond familiar cloud logs