Cloud Security Programs with AWS Security Services

Getting to know the AWS Security portfolio of tools is key to getting AWS Security right for any Cloud Security Program. We spoke to Mark Terenzoni, Director of Risk Management, in AWS. Mark spoke about the evolving landscape of cloud security and gave a deep dive into AWS's suite of services like GuardDuty, Security Hub, Inspector, and the innovative Security Lake. Mark highlighted the varied adoption phases of these services, with foundational tools like GuardDuty and Security Hub being widely utilized. He also shared the trends in tool consolidation and the importance of integrated security solutions in the cloud.
Questions asked:
00:00 A bit about Mark
00:19 Exploring AWS Security Services
00:53 Understanding the Need for AWS Security Services
02:03 How Companies are Adopting AWS's Native Security Services
04:55 Customer Responsibility in AWS Cloud Security
05:47 Starting Your Cloud Security Program with AWS
07:25 Measuring Maturity of Cloud Security Program
08:45 Next-Level AWS Cloud Security Program Elements
10:05 Building Capable Teams for Robust AWS Cloud Security
11:23 AWS re:Invent 2023 Security Announcements
15:01 Consolidation of Cloud Security Services
16:13 Amazon Security Lake Explained
17:56 What is Open Cybersecurity Schema Framework
19:36 Further Learning and Connecting with AWS Expert Mark Terenzoni
--------------------------------------------------------------------------------
📱Cloud Security Podcast Social Media📱
_____________________________________
Twitter: / cloudsecpod
Facebook: / cloudsecuritypodcast
LinkedIn: / cloud-security-podcast
Website: cloudsecuritypodcast.tv/
#cloudsecurity #awssecurity #awsreinvent

[@marouanebouaricha3071]

i would love if you could setup a podcast with Kelsey Hightower next time

[@CloudSecurityPodcast]

Any particular question you would like us to ask him during the interview ? We have had Kelsey as guest in previous season and would def love to bring him back again.

[@rahulbdmehta]

I still feel AWS needs to work on predictability of cost of these services, if they can build something which gives visibility/estimate based of artifacts/signal in ecosystem, it would increase the adoption. I would not like to keep hearing from cost center regarding increased security hub or inspector cost every month just because dev team is getting super innovative with new s/w and configuration. One of the strong and less spoken reasons for tool consolidation is cost predictabilty. Example - i would prefer tennable more then inspector for this reason too.