XFA now supports screen lock timeout enforcement in addition to the existing screen lock enable/disable check.

Previously, XFA only verified whether screen lock was enabled on a device. Now, admins can also configure a maximum allowed timeout duration — and XFA will verify that the device's screen lock timeout is within that limit.

What's new:

• Admins can set a maximum screen lock timeout (in minutes) in their organization's policy
• XFA checks both that screen lock is enabled and that the configured timeout does not exceed the maximum
• Supports macOS, Windows, and Linux with platform-specific timeout detection
• The timeout check works alongside the existing enable/disable check — both must pass for the device to be compliant

This gives organizations tighter control over idle device security, ensuring employees cannot set excessively long timeouts that leave devices exposed.

Configure your policies

XFA's unsafe AI mode check now recognises Claude Code's newer persisted permission modes alongside the legacy dangerouslySkipPermissions flag, so administrators get accurate reporting whenever an agent is configured to auto-approve every tool call.

The following values of permissions.defaultMode in ~/.claude/settings.json (or ~/.claude/settings.local.json) are now flagged as unsafe because they auto-approve every tool call, including shell commands and network requests:

• bypassPermissions — persisted equivalent of running with --dangerously-skip-permissions. Treat this as 'agent has full local user privileges'.
• auto — the new Claude Code 'Auto' mode. Same risk class: skips permission prompts via a classifier and is intended for sandboxed CI, not for personal devices.

Both modes are unsafe to run on machines with credentials or production access. Safe values (default, plan, acceptEdits) remain unflagged. Devices configured with either flagged mode are now reported in the Unsafe AI Mode check, and end users see remediation steps in the in-app guide.

Review your AI policies

Add your own message to the bottom of XFA's onboarding and sign-in cards. Configure two separate messages — one shown during device onboarding, one during sign-in — from the Applications page in your Dashboard to reinforce your policies, link to an internal runbook, or add a bit of your own voice where end users will actually see it.

XFA now talks to your team in Slack. Connect your workspace once, and end users receive device risk alerts, new-device enrollment invitations, sign-in verification requests, and safe-browsing policy notifications as direct messages — no email required.

Admins stay in control: toggle each notification category on or off, pick delivery frequency per section, and connect or disconnect the workspace from the Integrations page in your Dashboard. Messages are localized in English, Dutch, French, Spanish, and Portuguese.

XFA's Linux disk-encryption check now recognises TCG OPAL self-encrypting drives* alongside LUKS.

When drive locking is enabled on an OPAL-capable drive, the device counts as encrypted, giving administrators accurate compliance reporting for Linux devices that rely on hardware encryption.

Review your disk-encryption policy

XFA's Windows disk-encryption check now recognises VeraCrypt system-drive encryption* alongside BitLocker.

Devices whose Windows boot/system drive is encrypted with VeraCrypt are now reported as compliant automatically, no configuration required.

Review your disk-encryption policy

Installing XFA on Linux is now easier than ever. Simply run a single command in your terminal to get started:

curl -fsSL https://distribution.xfa.tech/xfa-native-desktop-application/install.sh | sh

No more picking the right package from a dropdown, just copy, paste, done.

XFA's Linux integrity protection check now recognises AppArmor as a valid mandatory-access-control system, alongside SELinux.

Linux users who rely on AppArmor as their kernel-level integrity protection now pass the check automatically.

Two new MDM and compliance checks are now available for the desktop app:

• Microsoft Intune — Verify whether a device is enrolled in Microsoft Intune. Supports both macOS and Windows.
• Vanta — Detect whether the Vanta compliance monitoring agent is installed and running. Supports macOS, Windows, and Linux.

Both checks can be configured in your organization's policy with warning and blocking actions, just like all other security checks.

These checks are currently available on desktop only.

Configure your policies

XFA now integrates with Noru, a GRC platform that makes compliance manageable for modern teams.

Once connected, XFA automatically syncs your device security data to Noru, giving you:

• Automated compliance - Device security checks are continuously exported as security findings, eliminating manual compliance verification.
• Risk mapping - Each security check is linked to a risk in Noru's risk registry, providing a clear overview of your organization's risk posture.
• Real-time visibility - Findings are synced as they happen, so your compliance dashboard always reflects the current state.

XFA exports 23 security checks across endpoint posture, compliance, configuration, and identity & access categories.

To get started, create an API key in Noru with Write Assets and Write Risks scopes, and connect it from the Integrations page in your XFA dashboard.

Read the announcement | Set up the integration