Microsoft brings FIPS 140 Compliance to Authenticator supporting Federal Agencies
Many customers work in environments with security and compliance concerns requiring authenticators to use cryptography validated by the Federal Information Processing Standards (FIPS) 140 (reference NIST SP 800-63B). We're excited that Microsoft Authenticator on iOS is now FIPS 140 compliant (Android coming soon). Authenticator version 6.6.8 and higher on iOS is FIPS 140 compliant for all Azure Active Directory (Azure AD) authentications using push multifactor authentications (MFA), Passwordless Phone Sign-In (PSI), and time-based one-time passcodes (TOTP).
FIPS 140 compliance for Authenticator also helps federal agencies meet the requirements of Executive Order (EO) 14028, “Improving the Nation’s Cybersecurity” and healthcare organizations with Electronic Prescriptions for Controlled Substances (EPCS).
No changes in configuration are required in the Authenticator app or Azure Portal to enable this capability. Users on Authenticator version 6.6.8 and higher on iOS are FIPS 140 compliant by default for Azure AD authentications.
Authenticator leverages the native Apple cryptography to achieve FIPS 140, Security Level 1 compliance on Apple iOS devices. For more information about the certifications being used, reference the Apple CoreCrypto module.
As always, we want to hear from you! Feel free to leave comments down below or reach out to us on aka.ms/AzureADFeedback.
Best regards,
Alex Weinert (@Alex_T_Weinert)
VP Director of Identity Security, Microsoft
Learn more about Microsoft identity:
- Related Articles: Advanced Microsoft Authenticator security features are now generally available!, Authentication strength – choose the right auth method for your scenario!, Defend your users from MFA fatigue attacks
- Get to know Microsoft Entra – a comprehensive identity and access product family
- Return to the Microsoft Entra (Azure AD) blog home
- Join the conversation on Twitter and LinkedIn
- Share product suggestions on the Entra (Azure AD) forum
Published on:
Learn moreRelated posts
Sync identities from Rippling to Microsoft Entra ID
Today, we’re thrilled to announce that customers using Rippling HCM can now automatically provision users to on-premises Active Directory and ...
Microsoft Entra ID Governance for government
I’m pleased to announce that as of November 1, 2024, Microsoft Entra ID Governance is available for federal agencies, state and local governme...
Update to security defaults
As part of the Secure Future Initiative, we’ve evolved our security approach to align with three security principles: secure by design, secure...
Meet Microsoft Entra at Ignite 2024: November 18-22
Microsoft Ignite is just around the corner, taking place from Monday, November 18, 2024 through Friday, November 22, 2024, in Chicago, Illinoi...
Manage Microsoft Entra ID role assignments with Microsoft Entra ID Governance
I’m excited to announce that we now support Microsoft Entra role assignments in Microsoft Entra ID Governance's Entitlement Management feature...
The latest enhancements in Microsoft Authenticator
Hi folks, I'm thrilled to announce three major Microsoft Entra ID advancements that will help you protect your users with phishing-resi...
Microsoft Security announcements and demos at Authenticate 2024
The Microsoft Security team is excited to connect with you next week at Authenticate 2024 Conference, taking place October 14 to 16 in Carlsba...
What's new in Microsoft Entra - September 2024
We’re excited to announce the general availability of Microsoft Entra Suite—one of the industry’s most comprehensive secure access solutions f...
Explore the key benefits of Microsoft Entra Private Access
The traditional network security models are becoming increasingly ineffective in a world where remote work and cloud services are the norm. Co...
Join us at the Microsoft Entra Suite Showcase!
This fall, we are bringing the Microsoft Entra Suite Showcase to cities worldwide. Join us to explore how our latest advancements in secure id...