DEV Community: Avinash Seth

Connect your Azure VM without opening SSH / RDP Ports!

Avinash Seth — Fri, 14 Jan 2022 14:14:00 +0000

When you open PORT 22 for SSH or 3389 for RDP in your Azure VM.

You are fundamentally taking a risk.

You are exposing your VM from public attacks!

As the IP is public, the attacker is just going to run the scripts!

But for early stage startups, small companies this can be a big security loophole and for big companies, this is a major compliance issue!

While early stage startups cannot afford compliance and auditing firms!

They are putting their resources and assets as risk!

Is there a solution to it?

Don't open them?

Yes, this is one solution! If you don't want to access to your VM after creating them!

But I want to access them!

Well in that can you can use Azure Bastion

It is a PAID service by Microsoft Azure, where you can still access your VM without opening those ports!

All you need is your Microsoft Azure Account and Browser!

Avinash Seth — Fri, 14 Jan 2022 03:43:19 +0000

Imagine!

You are having time of your life one fine Sunday morning!

And suddenly you receive a call!

"We are not compliant!"

What do you do?

You look everywhere! But it is too late! You cannot do anything now!

Well that 90 seconds nightmare can be a reality in future!

Way too many #startups, #sysadmin, IT specialist are scared of compliances!

They assume if I'm using a #cloud vendor, I'm already compliant!

But cloud provider has 2 way of saying

Security "OF" cloud
Security "IN" cloud

And these terms can often be confusing!

What is the solution?

If you #infrastructure is over cloud, #compliance and #security can become tricky!

Every major cloud provider has separate shared responsibility for them.

And unfortunately there is no solution that fits all!

So next time if you are planning to use cloud.

Talk to experts about your compliance goal and security goals!