Authentication strengths
This page describes the configuration of authentication strengths within Microsoft Entra ID associated with systems built according to the guidance provided by ASD's Blueprint for Secure Cloud.
Estimated reading time: 1 minute
Instruction
The below tables outline the as built configuration for ASD’s Blueprint for Secure Cloud (the Blueprint) for the Microsoft Entra admin portal at the following URL:
The settings described on these pages provide a baseline implementation for a system configured using the Blueprint. Any implementation implied by these pages should not be considered as prescriptive as to how an organisation must scope, build, document, or assess a system.
Implementation of the guidance provided by the Blueprint will differ depending on an organisation’s operating context and organisational culture. Organisations should implement the Blueprint in alignment with their existing change management, business processes and frameworks.
Placeholders such as <ORGANISATION.GOV.AU>, <BLUEPRINT.GOV.AU> and <TENANT-NAME> should be replaced with the relevant details as required.
| Item | Value |
|---|---|
| Phishing-resistant MFA and TAP | |
| Name | Phishing-resistant MFA and TAP |
| Phishing-resistant MFA | Windows Hello For Business Passkeys (FIDO2) Certificate-based Authentication (Multifactor) |
| Multifactor authentication | Temporary Access Pass (One-time use) Temporary Access Pass (Multi-use) |
New authentication strengths can take some time to appear for use in Conditional Access policy drop-downs.