If you have worked on any enterprise infrastructure, I’m sure you would have atleast heard the scenarios related to data breach or attacks. Security has been a primary concern and will always be. Just in time is one of the feature that allows us to enable ports on Virtual machine only when it is required. This page explains the principles behind Microsoft Defender for Cloud’s just-in-time (JIT) VM access feature and the logic behind the recommendation.
Threat actors actively hunt accessible machines with open management ports, like RDP or SSH. All of your virtual machines are potential targets for an attack. When a VM is successfully compromised, it’s used as the entry point to attack further resources within your environment.
As with all cybersecurity prevention techniques, your goal should be to reduce the attack surface. In this case, that means having fewer open ports, especially management ports.
Your legitimate users also use these ports, so it’s not practical to keep them closed.
To solve this dilemma, Microsoft Defender for Cloud offers JIT. With JIT, you can lock down the inbound traffic to your VMs, reducing exposure to attacks while providing easy access to connect to VMs when needed.
In Azure, you can block inbound traffic on specific ports, by enabling just-in-time VM access. Defender for Cloud ensures “deny all inbound traffic” rules exist for your selected ports in the network security group (NSG) and Azure Firewall rules. These rules restrict access to your Azure VMs’ management ports and defend them from attack.
If other rules already exist for the selected ports, then those existing rules take priority over the new “deny all inbound traffic” rules. If there are no existing rules on the selected ports, then the new rules take top priority in the NSG and Azure Firewall.
In AWS, by enabling JIT-access the relevant rules in the attached EC2 security groups, for the selected ports, are revoked which blocks inbound traffic on those specific ports.
When a user requests access to a VM, Defender for Cloud checks that the user has Azure role-based access control (Azure RBAC) permissions for that VM. If the request is approved, Defender for Cloud configures the NSGs and Azure Firewall to allow inbound traffic to the selected ports from the relevant IP address (or range), for the amount of time that was specified. In AWS, Defender for Cloud creates a new EC2 security group that allows inbound traffic to the specified ports. After the time has expired, Defender for Cloud restores the NSGs to their previous states. Connections that are already established are not interrupted.
JIT does not support VMs protected by Azure Firewalls controlled by Azure Firewall Manager. The Azure Firewall must be configured with Rules (Classic) and cannot use Firewall policies.
The diagram below shows the logic that Defender for Cloud applies when deciding how to categorize your supported VMs:
When Defender for Cloud finds a machine that can benefit from JIT, it adds that machine to the recommendation’s Unhealthy resources tab.
JIT Requires Microsoft Defender for Servers Plan 2 to be enabled on the subscription. Reader and SecurityReader roles can both view the JIT status and parameters. If you want to create custom roles that can work with JIT, you’ll need the details from the table below. If you are setting up JIT on your Amazon Web Service (AWS) VM, you will need to connect your AWS account to Microsoft Defender for Cloud.
To create a least-privileged role for users that need to request JIT access to a VM, and perform no other JIT operations, use the Set-JitLeastPrivilegedRole script from the Defender for Cloud GitHub community pages.
|To enable a user to:||Permissions to set|
|Configure or edit a JIT policy for a VM||Assign these actions to the role:|
On the scope of a subscription or resource group that is associated with the VM:
On the scope of a subscription or resource group of VM:
|Request JIT access to a VM||Assign these actions to the user:|
|Read JIT policies||Assign these actions to the user:|