Sign up to save your podcasts
Or
Share Azure Security Center, Key Vault, and More from Microsoft
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
Azure Security Center, Key Vault, and More from Microsoft
Our guest on the podcast this week is Tom Shinder, Program Manager, Azure Security Engineering at Microsoft.
We discuss security in Microsoft Azure where they have a mindset of assumed breach. How we’ve historically done security is we have looked to build more walls, moats, and force fields to keep the bad guys out. We’ve spent a long time building walls, but they can be hacked and they have. We should not stop prevention efforts, but what we should start to assume you have already been breached and be ready for that. When you assume you’ve already been breached, then focus on detection is critical. The average attacker has been in your system for 280 days before they have been detected, which gives them a lot of time. The goal is to reduce that time to a few days.
We look at Microsoft Azure Active Directory integration. This is meant to be used when deploying new applications into the cloud. Many of these tools allow developers to be able to focus on what really matters instead of focusing on putting out fires.
Microsoft is currently creating improved security standards, starting with a PCI template to help enterprises with regulations.
Encryption can sometimes be difficult with the Key Vault process. Microsoft is aware of some of the challenges and is working on revamping documentation for Key Vault to ease the difficulty. It is a great service that can make life easier, which is why the documentation updates will help make the product more accessible.
Azure Security Center allows you to control you security from one place, and gives recommendations and alerts based on anomaly detection. For hybrid deployments, there is a solution coming soon from Azure Security Center.
View all episodes
By Cloud Technology PartnersOur guest on the podcast this week is Tom Shinder, Program Manager, Azure Security Engineering at Microsoft.
We discuss security in Microsoft Azure where they have a mindset of assumed breach. How we’ve historically done security is we have looked to build more walls, moats, and force fields to keep the bad guys out. We’ve spent a long time building walls, but they can be hacked and they have. We should not stop prevention efforts, but what we should start to assume you have already been breached and be ready for that. When you assume you’ve already been breached, then focus on detection is critical. The average attacker has been in your system for 280 days before they have been detected, which gives them a lot of time. The goal is to reduce that time to a few days.
We look at Microsoft Azure Active Directory integration. This is meant to be used when deploying new applications into the cloud. Many of these tools allow developers to be able to focus on what really matters instead of focusing on putting out fires.
Microsoft is currently creating improved security standards, starting with a PCI template to help enterprises with regulations.
Encryption can sometimes be difficult with the Key Vault process. Microsoft is aware of some of the challenges and is working on revamping documentation for Key Vault to ease the difficulty. It is a great service that can make life easier, which is why the documentation updates will help make the product more accessible.
Azure Security Center allows you to control you security from one place, and gives recommendations and alerts based on anomaly detection. For hybrid deployments, there is a solution coming soon from Azure Security Center.