Description
Verify identities without MFA that can log in to a privileged virtual machine using separate login credentials. An adversary can leverage the access to move laterally and perform actions with the virtual machine's managed identity. Make sure the virtual machine only has necessary permissions, and revoke the admin-level permissions according to the least privileges principal
Rationaleβ
Integrating multi-factor authentication (MFA) as part of the organizational policy can greatly reduce the risk of an identity gaining control of valid credentials that may be used for additional tactics such as initial access, lateral movement, and collecting information. MFA can also be used to restrict access to cloud resources and APIs.
An Adversary may log into accessible cloud services within a compromised environment using Valid Accounts that are synchronized to move laterally and perform actions with the virtual machine's managed identity. The adversary may then perform management actions or access cloud-hosted resources as the logged-on managed identity.
Impactβ
This recommendation requires an Azure AD P2 License to implement.
Ensure that identities that are provisioned to a virtual machine utilizes an RBAC/ABAC group and is allocated a role using Azure PIM, and the Role settings require MFA or use another PAM solution (like CyberArk) for accessing Virtual Machines.
Auditβ
From Azure Portalβ
- Log in to the Azure portal.
- Select the
Subscription
, then click onAccess control (IAM)
. - Select
Role Assignments
from the top menu and apply filters onAssignment type
asPrivileged administrator roles
andType
asVirtual Machines
. - Verify the list of privileged managed identities attached to any virtual machine.
- If there are privileged managed identities from the above list, then check the list of users without MFA by navigating to
Azure AD
. - In the left navigation pane select
Users
fromManage
. - Click on
Per-User MFA
from the top menu options and for each user withMULTI-FACTOR AUTH STATUS
asDisabled
follow the below-mentioned steps:- Select the
Subscription
, then click onAccess control (IAM)
. - Select
Check access
and click onUser, group, or service principal
. - Enter the user name or email and verify there are no role assignments on the user that provides access like
Virtual Machine Administrator Login
orVirtual Machine User Login
. Make sure this follows the least privileges principal.
- Select the