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 Static Web Apps - Plan Comparison #cloud #azure Hi All! Azure Static web app is a good service when we have static web apps like javacript frameworks and libraries applictions (Ex: Angular, React, Svelte, Vue, Blazor). It also supports Python 3.10 based static web app as well as per the latest azure news. Other advantage of it is coupled with your Azure AD. so that your code can be directly pushed to azure static web app via either Azure DevOps or Github whenever code push occurs. At the time of azure static web app creation, it asks for deployment source as any one of the below. Based on the selection, it allows you to select the organization, project and repositories from the source. Azure DevOps - Azure AD connected Devops organizations will be listed out Github Other - For ex: If you want to deploy code from other organization. Below table will be helpful to choose the best pricing plan for your workload. Plan/Feature Free Standard ...
1 comment
Read more
Azure - Change custom lookback period for Azure Advisor VM/VMSS right-sizing recommendations #cloud #azure Hi All! Azure Advisor advises/recommeds us to optimize our cloud resources in various places like scaling, security, sizing, performace, cost etc., Now azure releases a new feature that changing lookback period for azure VM/VMSS to get right sizing. Let's consider a scenario that a company is running business and it has some workloads in either azure VM or VMSS. Some of the times VM's usage like CPU or memory is high. Due to this, application performace may be slower adnd user feels some bad experience. Company asks its azure admin to investigate it and when he/she viewd at azure advisor first, it recommends some solution based on last 7 days usage of VM. Here, Company needs the VM usage details biweekly or in someother pattern, not with the default 7 days. Here the new custom lookback period helps to achieve what the company wants. By this featur...
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