GCP IAM sync fixes and analysis reliability improvements
GCP IAM sync now works reliably across all GCP organization configurations, and the analysis engine handles edge cases that previously caused silent data loss.
Releases¶
npm supply chain hardening
In response to the March 30 Axios npm supply chain attack (CVE pending, attributed to North Korean threat actor UNC1069), we audited all dependencies and confirmed Thalian is not affected — axios is not in our dependency tree.
Entra ID Conditional Access detection, Okta System Log correlation, and more
Three major detection upgrades: Entra ID Conditional Access policy analysis, Okta System Log correlation rules, and expanded GCP IAM privilege analysis.
Workday HR integration, compliance evidence export, and more
New Workday HR integration, compliance audit evidence export for Enterprise, a redesigned integration library, and a batch of display and gating fixes.
Salesforce integration, Slack alert actions, Okta OAuth 2.0 upgrade
New Salesforce CRM integration, dismiss and snooze actions on Slack alerts, and Okta auth upgrade to OAuth 2.0 client credentials.
SSO coverage per identity, login source attribution, and more
Per-identity SSO vs direct-auth app breakdown, login authority scoring, 7 new SSO coverage findings, identity type filtering, and sync freshness before AI analysis.
AWS IAM, GCP IAM, access review campaigns, and AI remediation planner
Two new cloud IAM integrations, structured access review campaigns with ITSM integration, and Claude-driven remediation planning with reasoning.
AI brief personalization, cross-platform perspectives, behavioral anomalies, and more
Major intelligence upgrade: personalized AI briefs, cross-platform perspective views, behavioral anomaly detection, 7 compound rules, shadow admin detection, benchmark pricing, and UI refinements.
Cross-platform drift signals, automatic remediation after sync, and more
Three new drift signal rules requiring multiple data sources, automatic remediation firing after every sync, AI risk summaries on identity detail, and OAuth scope risk labels.
In-app support form
"Contact support" in the user menu now opens a proper support form (category, subject, message) instead of the Plain chat widget. Tickets are submitted directly to the support inbox and include your workspace name and plan for context. You'll receive a confirmation email when your ticket is submitted.