웨비나: DevOps에 “Sec”를 도입할 준비가 되셨나요?
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!
보안이 조직 전체와 SDLC 전체에서 공동 책임으로 간주되는 단계에 도달해야 합니다.이는 완전한 기능을 갖춘 고도로 지원적인 DevSecOps 환경을 이용한다면 확실히 가능합니다.
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는 전체 소프트웨어 개발 라이프사이클에서 코드를 보호하고 사이버 보안을 최우선으로 생각하는 문화를 조성할 수 있도록 조직을 위해 여기 있습니다.AppSec 관리자, 개발자, CISO 또는 보안 관련 누구든 관계없이 조직이 안전하지 않은 코드와 관련된 위험을 줄일 수 있도록 도와드릴 수 있습니다.
데모 예약
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!
아래 링크를 클릭하고 이 리소스의 PDF를 다운로드하십시오.
Secure Code Warrior는 전체 소프트웨어 개발 라이프사이클에서 코드를 보호하고 사이버 보안을 최우선으로 생각하는 문화를 조성할 수 있도록 조직을 위해 여기 있습니다.AppSec 관리자, 개발자, CISO 또는 보안 관련 누구든 관계없이 조직이 안전하지 않은 코드와 관련된 위험을 줄일 수 있도록 도와드릴 수 있습니다.
보고서 보기데모 예약
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!
목차
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는 전체 소프트웨어 개발 라이프사이클에서 코드를 보호하고 사이버 보안을 최우선으로 생각하는 문화를 조성할 수 있도록 조직을 위해 여기 있습니다.AppSec 관리자, 개발자, CISO 또는 보안 관련 누구든 관계없이 조직이 안전하지 않은 코드와 관련된 위험을 줄일 수 있도록 도와드릴 수 있습니다.
데모 예약다운로드시작하는 데 도움이 되는 리소스
%20(1).avif)
.avif)
Threat Modeling with AI: Turning Every Developer into a Threat Modeler
Walk away better equipped to help developers combine threat modeling ideas and techniques with the AI tools they're already using to strengthen security, improve collaboration, and build more resilient software from the start.
