Skip to main content
JIT VM Access - One way to reduce VM attack surface area

When a cloud resource is publicly accessible, it means it also ready for attack.

In this post, we will see how JIT helps azure virtual machine with public IP enabled securing briely.

Organizations need a VM with public IP sometimes. In this kind of scenario, we need secure the VM from attacker.

Just-In-Time (JIT) is one of the way to secure the VM in following ways.

  • It can block RDP (3389) and SSH (22) ports.
  • It allows to set specific port can be opened for a specific time for specific IP ranges.
  • It can work with VMs only have private IP as well.
  • Azure Bastion can be used to block traffic for a private IP VM until JIT access is enabled.

To enable JIT VM access, Go to configuration and enable it.

Comments

Post a Comment

Popular posts from this blog

Azure Public IP(s) are zone redundant free of cost natively - Generally Available Availability zone gives high availability to an application as well as information by forestalling the physical datacenter disappointments by involving replication of the asset in extra datacenter. Azure typically has 3 zones per region (and not all regions support zone). Thus, while setting up the environment we really want to pick the right region based on our usecase. Public IP helps to access a resource or an application publicly. Azure offers 2 types of SKU for public IP as below Basic Standard Only Standard SKU gives zone facility. Basic SKU is always non-zonal and this SKU also will be retired 09/2025. Standard public IP can be fell into any of the below category No Zone / Non-Zonal - No availability zone at all Zonal - Our services can be replicated in any one of selected zones from three zones. Zone redundant - Resource will be replicated in all 3 zones. It is opposite of...
Post a Comment
Read more
Difference between failed() vs succeededorFailed() in Devops YAML Every organizations embrace Devops culture for CI & CD. Nowadays, everybody prefers YAML which is IaC (Infrastructure as Code) instead of classic UI editor. YAML consists main components as stages, jobs, steps, tasks.... etc., Based on the requirement, Devops engineers need to apply conditions on pipline between tasks or jobs or stages. what is condition? when I want to run a task or job based on some condition like only when my preferred another job failed or succeeded. Here I job1 and job2. I need to run job2 only if job1 fails. Let's see the difference between failed() and succeededorFailed() through the below image.
Post a Comment
Read more
Avoid YAML Validation error in azure devops pipeline Hi All! Consider a scenario that you committed a YML CI/CD file on the repository with some syntax, indentation and/or other error(s). so that pipeline failed. After you find some errors and rectified in the repository file and committed again but pipeline still gets failed because some errors are still there. Now you afraid that even if you fixed error in all the places, what happens if pipeline failed again because your project lead or manager set up build notification mail trigger for build success and fails. you need to answer them for build fail reason. Azure devops pipelines offers YAML validation feature after altered and before committed and before run pipeline. To utilize this feature, what we do is, Instead of modifying the file from repository, Do as below Go to the specific build click "Edit Pipeline" Modify/fix errors and click "validate" as shown in the picture below ...
Post a Comment
Read more