Microsoft to Make Passkeys Default Authentication in Entra ID Starting September 2026
Microsoft will make passkeys the default authentication method in Entra ID starting September 1, 2026. The move is designed to reduce dependence on phishing-vulnerable methods such as SMS codes and voice calls.
Users currently enabled for SMS or voice authentication will be automatically enrolled for passkey support. During their next multifactor authentication attempt, they will receive a prompt to register the new credential.
Passkeys use public-key cryptography and do not rely on shared secrets. This approach prevents phishing attacks, code interception, credential reuse, and techniques such as SIM swapping.
Supported Passkey Options
The Entra ID service supports both synced and device-bound passkeys. Synced credentials can be managed through iCloud Keychain and Google Password Manager. Device-bound options include Microsoft Authenticator, Windows Hello, and physical FIDO2 security keys.
Microsoft will simultaneously retire its native SMS and voice authentication service. This capability will cease to exist in Entra ID on February 1, 2027. After that date, tenants relying solely on SMS or voice for MFA must register a passkey to continue logging in. The requirement will be enforced without any deactivation option.
Related articles
Ozon Data Security Team Details Audit Framework to Eliminate Paper-Only Compliance
Alena, head of the Data Security group at Ozon, describes how the company built an internal audit process that focuses on actual risk reduction instead of producing lengthy formal reports. The team examines personal data, financial records, and other sensitive information across hundreds of microservices while checking role-based access, logging, encryption, and data flows. They analyzed more than 84,000 user-role pairs in one review and identified overly broad permissions on product tagging that could cause major financial losses. A notable case led to the removal of customer names, phones, and addresses from delivery boxes even though the practice was formally allowed under Federal Law 152-FZ. The group uses a scoring model based on data sensitivity, business importance, user count, and potential monetary impact to prioritize which systems to audit first. Additional criteria such as past incidents and critical information infrastructure status can be added to the model. The approach emphasizes real implementation of recommendations, cross-team communication, and hiring analysts who care deeply about practical security outcomes.
Russian Ministry of Transport Unveils Draft Rules for Centralized Passenger Data with Unique Per-Trip IDs
The Russian Ministry of Transport has published a draft regulation expanding centralized databases of passenger and crew personal data. Each traveler and crew member will receive a unique identifier generated separately for every flight or trip that cannot be reused or reassigned. The rules add new mandatory data points including cancellations of boarding, online check-ins, and changes to group tickets. Data must be transmitted within 15 minutes for air and rail tickets and 30 minutes for other modes, with crew details submitted at least 24 hours before departure. Retention remains fixed at seven years. The order, if adopted, will replace the 2024 rules and is open for public comment until 29 August with an intended effective date of 1 March 2027.
Multiple Ozon Apps Removed from Google Play Following Sanctions on Ozon Bank
Several Ozon applications have been removed from the Google Play store, affecting Android users who can no longer download the main Ozon client along with Ozon Fresh, Ozon Seller, Ozon Job and Ozon Travel. Ozon stated that the company did not violate Google Play rules, yet the exact reasons for the removals remain undisclosed. The action follows the earlier disappearance of the Ozon Bank app after the bank was placed under European Union sanctions, although no official connection has been confirmed. Apple users continue to access Ozon services through the App Store, while Android users are directed to alternative stores including RuStore, AppGallery and Galaxy Store. The company also warned against downloading APK files from unverified sources due to security risks. The removals come amid a broader wave of app store purges that also affected Yandex Pay on the App Store. Already installed applications generally continue to function, but users may face difficulties with future updates and reinstalls.
Ruthenium: Custom Chromium Build for Android Adds Russian Trusted Root CA Support
A developer has released Ruthenium, a modified Chromium browser for Android that embeds the Russian Trusted Root CA certificate issued by the Ministry of Digital Development. The build restricts trust to .ru and .рф domains only, avoiding changes to the system-wide Android certificate store. The project patches four Chromium source files to include the root with DNS constraints via CertWithConstraints, disables Google sign-in by default, and removes XR-related code for successful compilation. Ruthenium uses the official Chromium TLS verification logic without introducing a custom verifier. The APK is distributed with SHA-256 checksums, build metadata, and reproducible release tags tied to the exact Chromium revision and certificate digest. Users can install it alongside stock Chrome and use it selectively for Russian government and banking sites that rely on the state root.