AzureFunBytes Episode 57 – Securing @Azure with @shehackspurple
AzureFunBytes is a weekly opportunity to learn more about the fundamentals and foundations that make up Azure. It’s a chance for me to understand more about what people across the Azure organization do and how they do it. Every week we get together at 11 AM Pacific on and learn more about Azure.
On this week’s AzureFunBytes Episode 57, Securing Azure, I welcome from to give an overview of security basics within Azure!
Tanya Janca, also known as SheHacksPurple, is the best-selling author of ‘’. She is also the founder of We Hack Purple, an online learning academy, community and podcast that revolves around teaching everyone to create secure software. Tanya has been coding and working in IT for over twenty years, won countless awards, and has been everywhere from startups to public service to tech giants (Microsoft, Adobe, & Nokia). She has worn many hats; startup founder, pentester, CISO, AppSec Engineer, and software developer. She is an award-winning public speaker, active blogger & streamer and has delivered hundreds of talks and trainings on 6 continents. She values diversity, inclusion, and kindness, which shines through in her countless initiatives.
Our agenda:
- Tanya made an Azure course
- Why it’s important to secure your Azure instance
- Let’s investigate a security incident
- How could we have prevented this?
- Security center overview
Azure Security Center
provides unified security management and advanced threat protection across hybrid cloud workloads. By implementing Security Center into your workloads, you can use best practices to strengthen the security posture of your apps and IT infrastructure.
:
Keeping your resources safe is a joint effort between your cloud provider, Azure, and you, the customer. You have to make sure your workloads are secure as you move to the cloud, and at the same time, when you move to IaaS (infrastructure as a service) there is more customer responsibility than there was in PaaS (platform as a service), and SaaS (software as a service). Azure Security Center provides you the tools needed to harden your network, secure your services and make sure you’re on top of your security posture.
Azure Security Center addresses the three most urgent security challenges:
- Rapidly changing workloads – It’s both a strength and a challenge of the cloud. On the one hand, end users are empowered to do more. On the other, how do you make sure that the ever-changing services people are using and creating are up to your security standards and follow security best practices?
- Increasingly sophisticated attacks – Wherever you run your workloads, the attacks keep getting more sophisticated. You have to secure your public cloud workloads, which are, in effect, an Internet facing workload that can leave you even more vulnerable if you don’t follow security best practices.
- Security skills are in short supply – The number of security alerts and alerting systems far outnumbers the number of administrators with the necessary background and experience to make sure your environments are protected. Staying up-to-date with the latest attacks is a constant challenge, making it impossible to stay in place while the world of security is an ever-changing front.
To help you protect yourself against these challenges, Security Center provides you with the tools to:
- Strengthen security posture: Security Center assesses your environment and enables you to understand the status of your resources, and whether they are secure.
- Protect against threats: Security Center assesses your workloads and raises threat prevention recommendations and security alerts.
- Get secure faster: In Security Center, everything is done in cloud speed. Because it is natively integrated, deployment of Security Center is easy, providing you with auto provisioning and protection with Azure services.
Learn about Azure fundamentals with me!
Live stream is normally found on Twitch, YouTube, and at 11 AM PT / 2 PM ET Thursday. You can also find the recordings here as well:
Useful Docs:
The post appeared first on .
