November 3, 2026 SaaS Alerts release notes
Fortify Action Processor 3.170.0
Enhancements
BitLocker recovery key access restrictions
Fortify now includes a CIS remediation that prevents users from viewing BitLocker recovery keys for devices they own. The remediation sets Restrict users from recovering the BitLocker key(s) for their owned devices to Yes in Microsoft Entra. No other default user permissions are changed.
If a user is locked out of a device, an administrator with permission to view BitLocker recovery keys must assist with recovery.
Undo restores the setting to the value it had before Fortify applied the remediation.
Shared Bookings page restrictions
Fortify now includes a CIS remediation that prevents users from creating new shared Bookings pages. The remediation turns off Bookings mailbox creation in the default Outlook on the web mailbox policy.
Mailboxes assigned to a different Outlook on the web mailbox policy are not affected. Selected users can retain the ability to create shared Bookings pages when their mailboxes are assigned a different Outlook on the web mailbox policy.
If Bookings is already disabled for the entire organization, Fortify makes no changes and reports the organization as compliant. Fortify does not disable Bookings at the organization level.
Undo restores the previous setting.
Zero-hour auto purge for Microsoft Teams
Fortify now includes a CIS remediation that ensures zero-hour auto purge (ZAP) is enabled for Microsoft Teams. When ZAP is enabled, Teams messages that Microsoft Defender later identifies as malware or high-confidence phishing are quarantined after delivery.
ZAP is enabled by default, so Fortify makes a change only when a saved Teams protection policy has ZAP disabled. Existing excluded participants in the policy are not changed.
Undo disables ZAP only if Fortify previously enabled it.
Requirement: Microsoft Defender for Office 365 Plan 2.
Stay signed in prompt setting
Fortify now includes a CIS remediation that hides the Stay signed in? prompt after users sign in. The remediation sets Users > User settings > Show keep user signed in to No in Microsoft Entra. This setting applies to the entire organization.
Sign-ins are maintained through a session cookie until the browser closes, for a maximum of 24 hours.
If the organization has never saved company branding, Fortify creates a default company branding configuration to store the setting. Fortify does not add a logo, custom text, or colors to the default branding configuration.
Undo sets Show keep user signed in back to Yes unless the setting was already No before Fortify applied the remediation. Any default company branding created by Fortify remains in place so that changes made to it afterward are preserved.
This remediation requires the Microsoft Graph OrganizationalBranding.ReadWrite.All permission. Organizations with automatic permission upgrades enabled do not need to take action because Fortify grants the permission during the next connection refresh. Organizations with automatic upgrades disabled or a Broken connection must reconnect before the remediation can be applied or undone.
Conditional Access for medium- and high-risk sign-ins
Fortify now provides a Conditional Access remediation that creates the Block medium and high risk sign-ins policy.
The policy blocks sign-ins that Microsoft Entra ID Protection identifies as medium or high risk. The policy applies to all users, resources, and client applications, and there is no prompt that a blocked user can complete to proceed. A blocked user can sign in again after an administrator confirms that the sign-in is safe or dismisses the risk.
The Global Administrator role is excluded by default so that an administrator can retain access to the tenant.
The policy provides the following configuration options:
-
Policy state: The policy can be set to Enabled or Report-only.
-
Exclude Global Administrators: The default Global Administrator exclusion can be kept or removed.
-
Users, Groups and Directory Roles: The Not equal to option can be used to configure exemptions, such as a break-glass account.
If Enable Azure AD Identity Protection sign-in risk policies is also used, the blocking policy takes precedence for medium- and high-risk sign-ins.
We recommend evaluating the policy in Report-only mode before enabling it.
Requirement: Microsoft Entra ID P2.
Managed device requirement for security information registration
Fortify now provides a Conditional Access remediation that creates the Require a managed device to register security information policy.
The policy allows users to register or change their multifactor authentication methods and self-service password reset information only from a device that Microsoft Intune marks as compliant or a Microsoft Entra hybrid joined device.
The policy applies to all users except the Global Administrator role and guest and external users.
New users who are registering their first authentication method are also included. A Temporary Access Pass does not bypass the managed device requirement, so organizations should plan how new users will register their authentication methods before enabling the policy.
The policy provides the following configuration options:
-
Policy state: The policy can be set to Enabled or Report-only.
-
Users, Groups and Directory Roles: The Not equal to option can be used to configure exemptions.
This policy can be used alongside Secure security info registration. If both policies are applied, users must satisfy the requirements of both.
Requirement: Microsoft Entra ID P1.
Conditional Access and Security Defaults
When Fortify creates either of these Conditional Access policies, Security Defaults are disabled for the tenant, consistent with other Fortify Conditional Access actions. Undo does not re-enable Security Defaults.
Undo deletes the policy that Fortify created. If applying the remediation disabled an existing policy with the same name, undo restores that policy to its previous state.
Token protection for sign-in sessions
Version 2 of the Require token protection for sign-in sessions Conditional Access remediation now applies only to Mobile apps and desktop clients, aligning the policy with CIS Microsoft 365 v7.
Browsers are no longer selected, so web applications such as Teams on the web continue to work.
Fortify displays Update available when an existing policy meets only the requirements of the previous version. Reapplying the remediation updates the policy in place. Templates pinned to version 1 continue to apply version 1.
Intune-compliant device Conditional Access
Version 2 of the Require Intune compliant device Conditional Access remediation now grants access using Require one of the selected controls. Because the policy has only one control, sign-in behavior remains unchanged.
Version 2 also requires the policy to apply to all users and all resources. If a policy is narrowed to selected users, groups, or roles using Equal to, the policy will report as regressed after it is reapplied. Remove the narrowing before reapplying the remediation.
Fortify displays Update available when an existing policy meets only the requirements of the previous version. Reapplying the remediation updates the policy in place. Templates pinned to version 1 continue to apply version 1.
Security concern reporting in Teams
Version 2 of the Ensure users can report security concerns in Teams remediation changes the CIS My reporting mailbox only configuration so that messages reported by users in Teams are sent only to the designated reporting mailbox. Reported messages are no longer also sent to Microsoft.
Review this behavior before updating to version 2.
Undo restores the previous reporting settings.
Fortify displays Update available when the existing configuration meets only the requirements of the previous version. Reapplying the remediation updates the configuration in place. Templates pinned to version 1 continue to apply version 1.
Fixes
Remediations for previously unsaved tenant settings
Fortify now retries the operation when certain remediations encounter a not found error because the applicable setting has never been saved in the tenant.
This improvement applies to the following remediations:
-
Ensure smart lockout threshold and duration are configured (CIS)
-
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 in Azure portals, API or PowerShell is set to No (CIS)
Previously, these remediations could fail with a not found error when the corresponding tenant setting had never been saved.
Connection permissions
Additional read-only permissions for compliance reporting
The Fortify application now requests additional read-only permissions to access employee leave information and Microsoft Defender for Endpoint device, vulnerability, and software inventory data.
The following permissions are requested:
-
Microsoft Graph User-LifeCycleInfo.Read.All provides read-only access to employee leave dates.
-
Machine.Read.All provides read-only access to Microsoft Defender for Endpoint device inventory data.
-
Vulnerability.Read.All provides read-only access to Microsoft Defender for Endpoint vulnerability data.
-
Software.Read.All provides read-only access to Microsoft Defender for Endpoint software inventory data.
Fortify uses these permissions only to read data for compliance framework reporting available through the Fortify AI agent. The permissions do not allow Fortify to change data in the tenant.
Organizations with automatic permission upgrades enabled do not need to take action. Fortify grants the permissions during the next connection refresh.
Organizations with automatic permission upgrades disabled or with a Broken connection should reconnect to grant the additional permissions.
