October 28, 2026 SaaS Alerts release notes

Respond 0.92.1

Enhancements

Respond for Devices supports rules and IOCs

Respond for Devices can now generate alerts on devices from rules and indicators of compromise (IOCs).

Fortify Action Processor 3.148.1

Enhancements

Additional CIS remediations are available

Fortify now includes additional remediations for Microsoft Entra security settings.

Smart lockout threshold and duration can be configured

The Ensure smart lockout threshold and duration are configured (CIS) remediation configures Microsoft Entra smart lockout with a lockout threshold from 1 to 10 failed sign-ins and a lockout duration from 60 to 18,000 seconds. The defaults are 10 failed sign-ins and 60 seconds, which are also the Microsoft defaults.

Applying the remediation only tightens the existing values. If a tenant already has stricter values, those values are retained. Selecting less restrictive values later does not loosen an existing configuration unless the remediation is undone and applied again.

The custom banned password list and on-premises password protection values share the same Microsoft Entra setting and are not changed. Undo restores each value that Fortify changed to its previous value.

Microsoft Entra ID P1 or P2 is required for Microsoft to enforce values stricter than its defaults. On tenants without either license, Fortify refuses to apply stricter values and makes no changes.

System-preferred multifactor authentication can be enabled

The Ensure system-preferred multifactor authentication is enabled (CIS) remediation sets system-preferred multifactor authentication to Enabled for All users. When MFA is required, users are prompted for the most secure method they have registered, such as a passkey or Microsoft Authenticator notification, instead of the method they selected as their default.

The remediation does not remove authentication methods or require users to register new ones. Existing exclusions are retained. The Microsoft managed state is considered noncompliant because CIS requires the setting to be explicitly enabled.

Undo restores the state and targets that existed before the remediation was applied. This remediation has no parameters.

Microsoft Authenticator on companion applications can be disabled

The Ensure Microsoft Authenticator on companion applications is disabled (CIS) remediation disables Microsoft Authenticator on companion applications, also known as Authenticator Lite in Outlook mobile. Authenticator Lite approval prompts do not display the application name or location.

Users whose only registered MFA method is Authenticator Lite cannot complete multifactor authentication after this setting is disabled. Fortify does not count these users, so registered authentication methods should be checked in the Microsoft Entra admin center before applying the remediation.

Only the Authenticator Lite setting is changed. Undo restores its previous value.

Four actions are updated to version 2 for CIS Microsoft 365 v7

Four actions now apply version 2, aligned with CIS Microsoft 365 v7. A tenant where an action is already completed but does not meet version 2 displays Update available. Templates pinned to version 1 continue applying version 1 until the pinned version is upgraded.

Microsoft Authenticator MFA fatigue protection is improved

Version 2 of Ensure Microsoft Authenticator is configured to protect against MFA fatigue (CIS) enables the Microsoft Authenticator method and adds All users to its targets while retaining groups that are already targeted.

The application name and geographic location notification settings are both targeted at All users.

If a group is limited to passwordless sign-in and All users is not targeted, Fortify makes no changes and identifies the affected group. The group authentication mode must be changed to Any, or the action can remain pinned to version 1 in a template.

When the registration campaign is enabled, users who have not configured Microsoft Authenticator may be prompted to register it at sign-in.

Undo restores the previous state of the authentication method. If the method was previously disabled, it is disabled again. Users who registered Microsoft Authenticator as their only method may then be unable to complete MFA.

Connection filter policy handling is improved

Version 2 of Don't add allowed IP addresses in the connection filter policy also disables the safe list in the Default connection filter policy. The Microsoft default is already off, so most tenants see no change.

Undo enables the safe list only if Fortify disabled it.

Mailbox auditing includes additional recommended audit actions

Version 2 of Ensure mailbox auditing for all users is Enabled adds the CIS-recommended admin, delegate, and owner audit actions to every user mailbox that is missing them, rather than only to mailboxes where auditing is disabled.

The actions are added to each mailbox's existing list without removing existing actions. A mailbox that retains audit records longer than the audit log age limit, which defaults to 180 days, keeps its longer retention period.

After version 2 is applied, Fortify's nightly check adds the same audit actions to new user mailboxes.

Undo does not make changes in the tenant for either version. Mailbox auditing remains enabled, and audit actions are not removed.

SaaS Alerts Fortify Anti-Phishing Policy Collection is updated

Version 2 of SaaS Alerts Fortify Anti-Phishing Policy Collection sets the default phishing email threshold to 3 – More Aggressive and enables Honor DMARC record policy when the message is detected as spoof.

Applying the action also re-enables Fortify's anti-phishing rule if it has been disabled.

A higher threshold causes more messages to be treated as phishing and can result in more legitimate messages being quarantined. Users continue to receive notifications and can release their own quarantined messages.

Fortify application credentials are protected with an application property lock

Fortify now applies Microsoft Entra's app instance property lock to its own enterprise application in each connected tenant. The lock prevents secrets or certificates from being added to the application in the tenant.

Fortify's nightly maintenance applies the lock automatically. No action is required.

Fixes

Generative AI Conditional Access policies apply more reliably

Two Generative AI actions could fail during their first application in a tenant when both attempted to register the same Microsoft Copilot application at the same time. The following actions now apply successfully:

  • All users of Generative AI services are blocked when insider risk is elevated

  • All users of Generative AI services must access from a compliant device when insider risk is moderate

  • Require multifactor authentication for All users of Generative AI services for phishing-resistant

Microsoft Entra settings are preserved during concurrent creation

In a rare timing scenario, the following actions could reset other values in the same Microsoft Entra setting to Microsoft's defaults when that setting was being created at the same time:

  • Ensure custom banned passwords lists are used (CIS)

  • Ensure password protection is enabled for on-prem Active Directory

  • Ensure that 'Users can create Microsoft 365 groups…' is set to 'No' (CIS)

These actions now leave existing values in the setting unchanged.