Webinar: Are you ready to put the "Sec" in DevOps?
Anyone who has worked in software production is likely aware of the tension that can arise when it comes to factoring in security, mostly between developers and the security specialists scrutinizing their code.
In the old days, it wasn't uncommon for the development team to ship code as late as possible, deliberately shortening the window in which the security gurus could check for vulnerabilities - after all, this delayed releases if anything happened to be wrong, and there was already the desire to move on and start building the next awesome feature. However, this had an eventual negative impact, as when the code was eventually checked -- sometimes after an external breach had already occurred -- the code would still bounce back to the developers, their software babies were still called ugly by the security team, and they'd have to drop everything to hotfix code they'd last touched months ago.
This dysfunction continues today, but there is a huge problem: there is much more code being developed, and society is at far greater risk in the event of data breaches occurring. We no longer have time to keep fighting this ancient battle, and in 2020, it's time we all joined the same side against the bad guys.
We must get to a stage where security is seen as a shared responsibility across the entire organization, and throughout the SDLC. This is certainly possible when you commit to a fully-fledged, highly supportive DevSecOps environment. What's more, when you ignite the security fire in your development team with the right training and tools, they are a powerful force in not only squashing bugs, but taking the load off the security specialists who have been spread too thin, for too long.
I'd love you to watch one of my latest webinars, How to put the "Sec" in DevOps:
This was part of the AllTheTalks 24-hour summit event, and it takes a deep look into:
- Why older development methodologies made security best practice so much harder
- Why DevSecOps is the latest game-changer in stopping common security vulnerabilities
- What security as a shared responsibility looks like in an organization
- How you can empower developers to ship secure code with confidence, without sacrificing what they love (hint: it's building awesome features).
See you there!
We must get to a stage where security is seen as a shared responsibility across the entire organization, and throughout the SDLC. This is certainly possible when you commit to a fully-fledged, highly supportive DevSecOps environment.
Matias Madou, Ph.D. is a security expert, researcher, and CTO and co-founder of Secure Code Warrior. Matias obtained his Ph.D. in Application Security from Ghent University, focusing on static analysis solutions. He later joined Fortify in the US, where he realized that it was insufficient to solely detect code problems without aiding developers in writing secure code. This inspired him to develop products that assist developers, alleviate the burden of security, and exceed customers' expectations. When he is not at his desk as part of Team Awesome, he enjoys being on stage presenting at conferences including RSA Conference, BlackHat and DefCon.
Secure Code Warrior is here for your organization to help you secure code across the entire software development lifecycle and create a culture in which cybersecurity is top of mind. Whether you’re an AppSec Manager, Developer, CISO, or anyone involved in security, we can help your organization reduce risks associated with insecure code.
Book a demo
Matias Madou, Ph.D. is a security expert, researcher, and CTO and co-founder of Secure Code Warrior. Matias obtained his Ph.D. in Application Security from Ghent University, focusing on static analysis solutions. He later joined Fortify in the US, where he realized that it was insufficient to solely detect code problems without aiding developers in writing secure code. This inspired him to develop products that assist developers, alleviate the burden of security, and exceed customers' expectations. When he is not at his desk as part of Team Awesome, he enjoys being on stage presenting at conferences including RSA Conference, BlackHat and DefCon.
Matias is a researcher and developer with more than 15 years of hands-on software security experience. He has developed solutions for companies such as Fortify Software and his own company Sensei Security. Over his career, Matias has led multiple application security research projects which have led to commercial products and boasts over 10 patents under his belt. When he is away from his desk, Matias has served as an instructor for advanced application security training courses and regularly speaks at global conferences including RSA Conference, Black Hat, DefCon, BSIMM, OWASP AppSec and BruCon.
Matias holds a Ph.D. in Computer Engineering from Ghent University, where he studied application security through program obfuscation to hide the inner workings of an application.
Anyone who has worked in software production is likely aware of the tension that can arise when it comes to factoring in security, mostly between developers and the security specialists scrutinizing their code.
In the old days, it wasn't uncommon for the development team to ship code as late as possible, deliberately shortening the window in which the security gurus could check for vulnerabilities - after all, this delayed releases if anything happened to be wrong, and there was already the desire to move on and start building the next awesome feature. However, this had an eventual negative impact, as when the code was eventually checked -- sometimes after an external breach had already occurred -- the code would still bounce back to the developers, their software babies were still called ugly by the security team, and they'd have to drop everything to hotfix code they'd last touched months ago.
This dysfunction continues today, but there is a huge problem: there is much more code being developed, and society is at far greater risk in the event of data breaches occurring. We no longer have time to keep fighting this ancient battle, and in 2020, it's time we all joined the same side against the bad guys.
We must get to a stage where security is seen as a shared responsibility across the entire organization, and throughout the SDLC. This is certainly possible when you commit to a fully-fledged, highly supportive DevSecOps environment. What's more, when you ignite the security fire in your development team with the right training and tools, they are a powerful force in not only squashing bugs, but taking the load off the security specialists who have been spread too thin, for too long.
I'd love you to watch one of my latest webinars, How to put the "Sec" in DevOps:
This was part of the AllTheTalks 24-hour summit event, and it takes a deep look into:
- Why older development methodologies made security best practice so much harder
- Why DevSecOps is the latest game-changer in stopping common security vulnerabilities
- What security as a shared responsibility looks like in an organization
- How you can empower developers to ship secure code with confidence, without sacrificing what they love (hint: it's building awesome features).
See you there!
Anyone who has worked in software production is likely aware of the tension that can arise when it comes to factoring in security, mostly between developers and the security specialists scrutinizing their code.
In the old days, it wasn't uncommon for the development team to ship code as late as possible, deliberately shortening the window in which the security gurus could check for vulnerabilities - after all, this delayed releases if anything happened to be wrong, and there was already the desire to move on and start building the next awesome feature. However, this had an eventual negative impact, as when the code was eventually checked -- sometimes after an external breach had already occurred -- the code would still bounce back to the developers, their software babies were still called ugly by the security team, and they'd have to drop everything to hotfix code they'd last touched months ago.
This dysfunction continues today, but there is a huge problem: there is much more code being developed, and society is at far greater risk in the event of data breaches occurring. We no longer have time to keep fighting this ancient battle, and in 2020, it's time we all joined the same side against the bad guys.
We must get to a stage where security is seen as a shared responsibility across the entire organization, and throughout the SDLC. This is certainly possible when you commit to a fully-fledged, highly supportive DevSecOps environment. What's more, when you ignite the security fire in your development team with the right training and tools, they are a powerful force in not only squashing bugs, but taking the load off the security specialists who have been spread too thin, for too long.
I'd love you to watch one of my latest webinars, How to put the "Sec" in DevOps:
This was part of the AllTheTalks 24-hour summit event, and it takes a deep look into:
- Why older development methodologies made security best practice so much harder
- Why DevSecOps is the latest game-changer in stopping common security vulnerabilities
- What security as a shared responsibility looks like in an organization
- How you can empower developers to ship secure code with confidence, without sacrificing what they love (hint: it's building awesome features).
See you there!
Click on the link below and download the PDF of this resource.
Secure Code Warrior is here for your organization to help you secure code across the entire software development lifecycle and create a culture in which cybersecurity is top of mind. Whether you’re an AppSec Manager, Developer, CISO, or anyone involved in security, we can help your organization reduce risks associated with insecure code.
View reportBook a demo
Matias Madou, Ph.D. is a security expert, researcher, and CTO and co-founder of Secure Code Warrior. Matias obtained his Ph.D. in Application Security from Ghent University, focusing on static analysis solutions. He later joined Fortify in the US, where he realized that it was insufficient to solely detect code problems without aiding developers in writing secure code. This inspired him to develop products that assist developers, alleviate the burden of security, and exceed customers' expectations. When he is not at his desk as part of Team Awesome, he enjoys being on stage presenting at conferences including RSA Conference, BlackHat and DefCon.
Matias is a researcher and developer with more than 15 years of hands-on software security experience. He has developed solutions for companies such as Fortify Software and his own company Sensei Security. Over his career, Matias has led multiple application security research projects which have led to commercial products and boasts over 10 patents under his belt. When he is away from his desk, Matias has served as an instructor for advanced application security training courses and regularly speaks at global conferences including RSA Conference, Black Hat, DefCon, BSIMM, OWASP AppSec and BruCon.
Matias holds a Ph.D. in Computer Engineering from Ghent University, where he studied application security through program obfuscation to hide the inner workings of an application.
Anyone who has worked in software production is likely aware of the tension that can arise when it comes to factoring in security, mostly between developers and the security specialists scrutinizing their code.
In the old days, it wasn't uncommon for the development team to ship code as late as possible, deliberately shortening the window in which the security gurus could check for vulnerabilities - after all, this delayed releases if anything happened to be wrong, and there was already the desire to move on and start building the next awesome feature. However, this had an eventual negative impact, as when the code was eventually checked -- sometimes after an external breach had already occurred -- the code would still bounce back to the developers, their software babies were still called ugly by the security team, and they'd have to drop everything to hotfix code they'd last touched months ago.
This dysfunction continues today, but there is a huge problem: there is much more code being developed, and society is at far greater risk in the event of data breaches occurring. We no longer have time to keep fighting this ancient battle, and in 2020, it's time we all joined the same side against the bad guys.
We must get to a stage where security is seen as a shared responsibility across the entire organization, and throughout the SDLC. This is certainly possible when you commit to a fully-fledged, highly supportive DevSecOps environment. What's more, when you ignite the security fire in your development team with the right training and tools, they are a powerful force in not only squashing bugs, but taking the load off the security specialists who have been spread too thin, for too long.
I'd love you to watch one of my latest webinars, How to put the "Sec" in DevOps:
This was part of the AllTheTalks 24-hour summit event, and it takes a deep look into:
- Why older development methodologies made security best practice so much harder
- Why DevSecOps is the latest game-changer in stopping common security vulnerabilities
- What security as a shared responsibility looks like in an organization
- How you can empower developers to ship secure code with confidence, without sacrificing what they love (hint: it's building awesome features).
See you there!
Table of contents
Matias Madou, Ph.D. is a security expert, researcher, and CTO and co-founder of Secure Code Warrior. Matias obtained his Ph.D. in Application Security from Ghent University, focusing on static analysis solutions. He later joined Fortify in the US, where he realized that it was insufficient to solely detect code problems without aiding developers in writing secure code. This inspired him to develop products that assist developers, alleviate the burden of security, and exceed customers' expectations. When he is not at his desk as part of Team Awesome, he enjoys being on stage presenting at conferences including RSA Conference, BlackHat and DefCon.
Secure Code Warrior is here for your organization to help you secure code across the entire software development lifecycle and create a culture in which cybersecurity is top of mind. Whether you’re an AppSec Manager, Developer, CISO, or anyone involved in security, we can help your organization reduce risks associated with insecure code.
Book a demoDownloadResources to get you started
Secure by Design: Defining Best Practices, Enabling Developers and Benchmarking Preventative Security Outcomes
In this research paper, Secure Code Warrior co-founders, Pieter Danhieux and Dr. Matias Madou, Ph.D., along with expert contributors, Chris Inglis, Former US National Cyber Director (now Strategic Advisor to Paladin Capital Group), and Devin Lynch, Senior Director, Paladin Global Institute, will reveal key findings from over twenty in-depth interviews with enterprise security leaders including CISOs, a VP of Application Security, and software security professionals.
Benchmarking Security Skills: Streamlining Secure-by-Design in the Enterprise
Finding meaningful data on the success of Secure-by-Design initiatives is notoriously difficult. CISOs are often challenged when attempting to prove the return on investment (ROI) and business value of security program activities at both the people and company levels. Not to mention, it’s particularly difficult for enterprises to gain insights into how their organizations are benchmarked against current industry standards. The President’s National Cybersecurity Strategy challenged stakeholders to “embrace security and resilience by design.” The key to making Secure-by-Design initiatives work is not only giving developers the skills to ensure secure code, but also assuring the regulators that those skills are in place. In this presentation, we share a myriad of qualitative and quantitative data, derived from multiple primary sources, including internal data points collected from over 250,000 developers, data-driven customer insights, and public studies. Leveraging this aggregation of data points, we aim to communicate a vision of the current state of Secure-by-Design initiatives across multiple verticals. The report details why this space is currently underutilized, the significant impact a successful upskilling program can have on cybersecurity risk mitigation, and the potential to eliminate categories of vulnerabilities from a codebase.
Secure code training topics & content
Our industry-leading content is always evolving to fit the ever changing software development landscape with your role in mind. Topics covering everything from AI to XQuery Injection, offered for a variety of roles from Architects and Engineers to Product Managers and QA. Get a sneak peak of what our content catalog has to offer by topic and role.
Resources to get you started
Revealed: How the Cyber Industry Defines Secure by Design
In our latest white paper, our Co-Founders, Pieter Danhieux and Dr. Matias Madou, Ph.D., sat down with over twenty enterprise security leaders, including CISOs, AppSec leaders and security professionals, to figure out the key pieces of this puzzle and uncover the reality behind the Secure by Design movement. It’s a shared ambition across the security teams, but no shared playbook.
Is Vibe Coding Going to Turn Your Codebase Into a Frat Party?
Vibe coding is like a college frat party, and AI is the centerpiece of all the festivities, the keg. It’s a lot of fun to let loose, get creative, and see where your imagination can take you, but after a few keg stands, drinking (or, using AI) in moderation is undoubtedly the safer long-term solution.
Developer-driven coding.
Securely.
Contact us today and make software security an intrinsic part of your development process.
