This weekend I successfully passed the SC-100 certification, with it have now achieved my second Expert level cert, the Cybersecurity Architect certification from Microsoft.
Learned a ton, and looking at the exam score, I overstudied on governance, but that’s what I’m interested in, and yes, it’s helped a ton with furthering my knowledge with Azure security infrastructure and design!
This series of articles is to document steps to be taken to transition from an on-premise Active Directory footprint, and migrate the workloads to Azure AD.
A typical migration has the following stages:
Discovery: Find out what is currently in the environment
Pilot: Deploy new cloud capabilities to a small subset of users, applications, and devices
Scale Out: Expand the pilot to complete the transition
Cut-over: Stop using the on-premises authentication
Users and Groups
Microsoft highly recommends a passwordless environment, due to as is depicted in the following graphic, is both highly secure, and convenient.
In my experience, users correctly following secure practices either make or break security initiatives, thus, in my opinion, convenience is crucial
Industry authentication standards rely on one of the following:
Something you Know:
Passwords are great, but unless a vault is used, it is common to use the same, or variation for many personal accounts. Highly vulnerable in modern times, as environments are often compromised, with credentials getting exposed to public sites. The equivalent of writing credentials down on paper and other people finding it.
Something you Have:
Removes the problem of forgetting something you know, but is vulnerable to the object being lost or stolen.
Something you Are:
Much harder to lose a fingerprint than a wallet, however, while this is getting better, historically, biometric sensors can be fairly expensive (cost and support) and have accuracy issues.
Due to the fact each authentication methods have their vulnerabilities, a combination of them is much stronger, hence the modern term “Multi-Factor Authentication” (MFA)
Here’s an example of using the Authenticator App as a convenient multi-factor authentication option in addition to a password.
The Authenticator App turns any iOS or Android phone into a strong, passwordless credential. Users can sign in to any platform or browser by getting a notification to their phone, matching a number displayed on the screen to the one on their phone, and then using their biometric (touch or face) or PIN to confirm.
Passwordless authentication using the Authenticator app follows the same basic pattern as Windows Hello for Business. It’s a little more complicated as the user needs to be identified so that Azure AD can find the Authenticator app version being used:
The user enters their username.
Azure AD detects that the user has a strong credential and starts the Strong Credential flow.
A notification is sent to the app via Apple Push Notification Service (APNS) on iOS devices, or via Firebase Cloud Messaging (FCM) on Android devices.
The user receives the push notification and opens the app.
The app calls Azure AD and receives a proof-of-presence challenge and nonce.
The user completes the challenge by entering their biometric or PIN to unlock private key.
The nonce is signed with the private key and sent back to Azure AD.
Azure AD performs public/private key validation and returns a token.
Until an MFA environment is in place, migrating to Azure’s password self-service (SSPR) gives users the capability of managing their own password resets, which not only greatly helps with the “convenience” point I made above, but in most cases, tremendously decreases help desk support calls.
The following authentication methods are available for SSPR:
Mobile app notification
Mobile app code
Office phone (available only for tenants with paid subscriptions)
Users can only reset their password if they have registered an authentication method that the administrator has enabled.
With a hybrid environment, first install and configure the sync agent to be capable of enabling password writeback, once that is complete, you can configure Azure AD Connect to write password change events back from Azure AD to the on-premises directory.
In addition, the following options are available:
Users can unlock accounts without resetting their password
As of November 20, 2020, Azure now supports FQDN configurations for it’s VPN connections!
This is perfect for customer branches or locations without static public IP addresses (private homes behind a cable modem, etc.) to connect to the Azure VPN gateways. Dynamic DNS services can be leveraged to use the Fully Qualified Domain Name (FQDN) instead of IP addresses!