Michael Howard on Secure by Design vs Secure by Default
Aug 27, 2024
auto_awesome
Michael Howard, Principal Security Program Manager at Microsoft, shares his impressive journey in cybersecurity, starting in a small New Zealand team. He emphasizes the enduring importance of foundational security principles, discussing insights gained from vulnerabilities that improved SQL Server. The conversation highlights the difference between 'Secure by Design' and 'Secure by Default', and how collaboration at events like the Blue Hat conference has shaped Microsoft's culture. Michael also reflects on his influential works and the ongoing need for effective security practices among developers.
Michael Howard emphasizes the critical need for secure coding practices, highlighting his contributions to foundational texts on software security.
The cultural shift initiated by the Blue Hat Conference marked a significant change in how Microsoft approached external feedback on security vulnerabilities.
Ongoing challenges in software security necessitate continuous updates and education to mitigate emerging threats and human error effectively.
Deep dives
Michael Howard's Journey at Microsoft
Michael Howard has been with Microsoft for over three decades, reflecting on his journey that began in New Zealand supporting early Windows products. His enthusiasm for technology and security remains unwavering since joining as one of a small team, highlighting the evolution of cybersecurity within the organization. Currently, he transitions from a role focused on Azure Data security to John's Mystic team, where he will apply his extensive knowledge of security engineering. Howard's long-standing tenure illustrates the depth of experience that exists in Microsoft’s cybersecurity landscape.
The Impact of Security Books
Howard is recognized as a prolific author within the cybersecurity community, contributing significantly to secure software development literature. His book, 'Writing Secure Code,' co-authored with David LeBlanc, was born out of necessity when both authors noticed recurring security questions in their work. The response to their work highlights the importance of creating accessible resources on secure design principles, which continue to resonate today, evidenced by their ongoing relevance in modern coding practices. His latest publication, 'Designing and Developing Secure Azure Solutions,' expands on these themes in the context of cloud solutions.
Cultural Shift Through Blue Hat Conferences
Howard reflects on the transformative cultural impact of the Blue Hat Conference, especially the first edition where external security researchers presented their findings to Microsoft employees. This shift from insular engineering perspectives to welcoming external feedback represented a significant change within Microsoft’s approach to security vulnerabilities. Events at Blue Hat, such as David Lichfield's presentation, showcased the importance of understanding and accepting outside perspectives on security threats. Such changes fostered a culture of continuous improvement, prioritizing lessons learned from the security research community.
Secure by Default Principles
Discussions around security design principles, such as Secure by Design and Secure by Default, highlight the ongoing difficulties in keeping software secure amidst evolving threats. Howard emphasizes that products can become less secure over time if they aren't consistently updated in response to emerging vulnerabilities. He underscores the need for both developers' skill enhancement and for implementing protective measures that account for human error. As part of his work, he aims to focus on fostering a security-minded culture and education to uphold these critical principles.
Feedback and Collaboration in Security Research
Howard illustrates the importance of constructive feedback from security researchers and how it should lead to actionable mitigation strategies. The relationship between researchers and developers has evolved, where researchers share their findings with the intention of providing solutions rather than simply pointing out flaws. He mentions how fruitful partnerships lead to actionable changes in Microsoft products, ultimately enhancing security postures. Through effective communication, researchers can guide developers towards safer practices, thereby enriching the overall security landscape.
Michael Howard, Senior Director at Microsoft joins Nic Fillingham on this week's episode of The BlueHat Podcast. Michael shares his journey at Microsoft, starting from his early days in New Zealand as part of a small team of ten. He discusses his extensive career, his contributions to cybersecurity, and his role in the development of essential security books like "Writing Secure Code" and "The Security Development Lifecycle." Michael reflects on the importance of fundamental security principles and how they remain relevant today. He also touches on his recent move within Microsoft to John Lambert's team, where he continues to focus on security culture and education. The conversation delves into the origins of the Blue Hat conference, Michael's experiences at the first event, and the ongoing significance of secure coding practices and mitigations.
In This Episode You Will Learn:
Critical aspects of secure software development and pivotal moments in Microsoft's security
The importance of using specific coding constructs and libraries to improve security
Findings on vulnerabilities that spurred significant security improvements in SQL Server
Some Questions We Ask:
How do you deploy security patches effectively while minimizing disruptions?
What coding constructs and compiler flags did you recommend for better security?
How did external researchers at Blue Hat conferences impact Microsoft's culture?