This talk provides a brief history of how DevOps has enabled tech companies to become unicorns. Furthermore, is Security in DevOps important, who is responsible and what can teams do make security a competitive advantage.
The document discusses the importance of DevSecOps. It notes that existing security solutions are no longer adequate as software can now be distributed globally and created more cheaply in the cloud. DevSecOps aims to integrate security into development and operations by making security teams empower developers and help them succeed. It outlines how security tools and responsibilities have evolved from separate security testing to being integrated into product teams. The document argues DevSecOps is important because fixing defects early is cheaper than during production, and most modern applications use open source components which could contain vulnerabilities. It concludes security teams should empower product teams and help solve technology problems while product teams should be mindful of security.
This talk provides a brief history of how DevOps has enabled tech companies to become unicorns. Furthermore, is Security in DevOps important, who is responsible and what can teams do make security a competitive advantage.
DevSecOps in 2031: How robots and humans will secure apps together LogStefan Streichsbier
The year is 2031, how has software development and security evolved in the last decade? Are there any developers or security folks left? Have robots taken our jobs?
We will join Security Engineer Sam, that is responsible for securing a cutting edge application for a hot fintech company in the year 2021. The app has just completed a major release and Sam is sharing her progress and learnings with her peers at a local OWASP meetup. After a night of celebration she wakes up and finds her future self jumping out of a time-machine in her bedroom closet. Time travel paradoxes aside, the future of the world is at stake because a sentient A.I. is threatening to hack the planet. There is a small task force that has been working for a decade on finding a way to finally solve secure software development, and they have done it! There is no time to waste, you are joining your future self to go to the year 2031 and learn what they have learned to bring that knowledge back to present and avoid the dark future from ever happening.
Mobility and security are important factors that need to be prioritized by fintech startups in building user trust.
This presentations shares how to build, develop, and improve these two things so that your business can grow.
This talk by Stefan Streichsbier, Co-Founder of GuardRails.io, provides a brief history of how development, operations and security testing have become highly complex. It continues to outline the key problems with traditional security solutions and why in 2020 companies around the world are still figuring out a good way to manage security as part of rapid development cycles. Specifically, the big challenge of introducing and fixing new security issues versus tackling the existing security dept of existing applications.
To quote Bishop Desmond Tutu, “There comes a point where we need to stop just pulling people out of the river. We need to go upstream and find out why they’re falling in.”
After setting the stage, the remainder of the talk will focus on the paradigm shift that security solutions have to incorporate in order to solve the problem of sustainably secure applications on all layers. This will explore how the elements of Speed, Just in time training, and Data science have to be leveraged to empower development teams around the globe to get ahead for once and finally become able to move fast and be safe at the same time.
The 3 core takeaways for the audience are:
1.) Where security practices have gone wrong so far.
2.) What new technologies will cause a paradigm shift in how security is applied at scale.
3.) How security will look like in 5-10 years.
DevOps is not just about tools, but rather a culture and way of working. It involves cross-functional collaboration between development and operations teams. When implementing DevOps, organizations should focus on automating processes, integrating tools, communicating effectively, and iterating quickly rather than which specific tools to use. DevOps aims to break down silos between teams and move away from a blame culture.
The document discusses the barriers to digital transformation. It begins by looking at how there was initially oblivion, then the development of language led to ambiguity and dogmatism around concepts like CI/CD. This then led to misunderstandings as different levels of an organization adopted new practices at different rates. Incentives and education were also barriers as outdated management principles clashed with new technologies. Overcoming these barriers requires valuing continuous improvement, creating a shared understanding of processes, and believing in the power of new technologies.
- Stefan Streichsbier is the CEO of GuardRails and a professional white-hat hacker who has identified severe shortcomings in security processes and technologies, leading him to create GuardRails.
- The document discusses the evolution of DevOps and increasing complexity, the state of security and how it needs to fit within modern development workflows, and introduces the concept of DevSecOps to address shortcomings and better integrate security.
- Key aspects of DevSecOps discussed include how to create, test, and monitor secure applications and empower development teams to build security in from the start rather than see it as a separate function. Automated security tools and the need to reduce noise and improve usability for developers is also
DevSecOps: Bringing security to the DevOps pipelineAarno Aukia
The document discusses DevSecOps, which aims to automate security practices like testing and monitoring into the development lifecycle. It advocates integrating security practices like static code analysis, dependency management, and container scanning into the build process. For testing, it recommends smoke tests and restricting access to test environments. In deployment, it suggests automating atomic container deployments to remove the need for developer access to production. For operations, it outlines security practices like isolating containers, documenting infrastructure, and preventing configuration drift between environments. The goal is to implement security controls through automation and standardization rather than manual reviews.
The document discusses the rise of DevSecOps and its importance for software development. It notes that existing security solutions are no longer adequate due to the speed of modern development, and that security has become a bottleneck. DevSecOps aims to integrate security practices into development workflows to enable continuous and real-time security. It outlines how security responsibilities have evolved from separate teams to being shared among developers, and how tools have progressed from periodic testing to continuous monitoring and automation. The document argues that DevSecOps is necessary now given the costs of data breaches and risks of vulnerabilities in open source components.
This document discusses how security needs to adapt to keep up with rapid changes in technology and development practices. As internet usage and the number of developers have grown massively, the development process has become more complex, involving tools like AWS and DevOps. However, security has struggled to integrate effectively. The document argues security must improve its developer experience by focusing on high-impact issues, speaking the same language as developers, making tools easy to use, and tightly integrating with development workflows. By learning from how quality evolved, security can become a commodity that developers respect and rely on.
Software Supply Chain Automation Removes Roadblocks to Rugged DevOpsSeniorStoryteller
This document summarizes the benefits experienced by MFS after implementing Jenkins and Nexus to help manage growth in their development organization. Some key points:
1) Jenkins and Nexus helped standardize MFS's development environment, shorten onboarding times, and improve security, code quality, and traceability.
2) Their initial implementation had limited success, but replacing build servers and addressing core issues like branching strategy and artifact management led to wider adoption.
3) Benefits included managing external resources better, inventorying all artifacts, understanding open source licensing risks, and gaining visibility into dependencies and modules.
Safely Removing the Last Roadblock to Continuous DeliverySeniorStoryteller
This document discusses how to implement DevSecOps practices to safely enable continuous delivery. It advocates shifting security left by integrating security practices into development workflows from design through deployment. This allows security issues to be identified and addressed early before they become costly problems. The document outlines DevSecOps staffing models and provides examples of how practices like automated security testing, secure baselines and templates, and monitoring can help operationalize security and reduce mean time to remediate issues from months to hours.
The DevSecOps Showdown: How to Bridge the Gap Between Security and DevelopersDevOps.com
DevSecOps requires processes and tools that enable weaving security throughout the DevOps pipeline. It is much more than a buzzword, and if you'd ask most organizations, well, they believe they are in the process of adopting DevSecOps tools and practices. But, are they?
In order to deeply understand the state of DevSecOps implementation we need to learn more about the relationship between developers and security teams. After surveying more than 560 application security professionals and software developers we found several insights.
Join Jeff Martin, associate VP of product management, and Rhys Arkins, director of product management at WhiteSource, to learn about:
The current challenges of the security and development teams when it comes to AppSec
The contradicting views and gaps between the teams on DevSecOps maturity
How to break the silos and advance toward DevSecOps maturity
Discussion of how security is in crisis but DevSecOps offers a new playbook and gives security a path to influence. Taking a look at the WAF space, we look at how Signal Sciences has created feedback between Dev and Ops and Security to create new value.
DevSecOps is a very loaded term and it includes many topics. Despite what some will lead you to believe, DevSecOps is not just an integration of security testing tools. Nor is it merely a focus on achieving security quality attributes on CI and CD. DevSecOps is beyond the automatizing security testing and there are common misconceptions and roadblocks on how you can establish it successfully.
Learning Objectives:
1: Identify key principles of DevSecOps and see how it relates to DevOps principles.
2: Analyze common pitfalls and see where integration security takes part in DevSecOps.
3: Demonstrate how to do “Continuous Security” by using a lifecycle approach.
(Source: RSA Conference USA 2018)
The practical DevSecOps course is designed to help individuals and organisations in implementing DevSecOps practices, to achieve massive scale in security. This course is divided into 13 chapters, each chapter will have theory, followed by demos and any limitations we need to keep in my mind while implementing them.
More details here - https://www.practical-devsecops.com/
*** DevSecOps: The Evolution of DevOps ***
Have you ever asked yourself the following questions:
What does DevSecOps means?
How is this different from DevOps?
What can we learn from the DevOps movement?
Presentation by James Betteley who shares his experience of shaping DevOps and what he foresees will happen with DevSecOps.
Taking Open Source Security to the Next LevelWhiteSource
Join us for a webinar featuring Forrester VP and Research Director Amy DeMartine to learn more about why open source security has become critical for securing modern applications, the main considerations when evaluating an open source security and license compliance solution and what she sees in store for the future.
Additionally, WhiteSource Senior Director of Product Marketing, Jeff Crum, will discuss recent analysis of the Software Composition Analysis (SCA) market, including takeaways from The Forrester Wave™: Software Composition Analysis, Q2 2019.
The document announces events from DevSecOps Singapore to bring together developers, operations, and security professionals. It describes monthly meetups for talks and networking, workshops over 4 months on integrating security testing into the SDLC, and an annual conference in 2017. It provides announcements for the workshops and conference and calls for speakers, office space, and volunteers to help build the community.
Silver Lining for Miles: DevOps for Building Security SolutionsSeniorStoryteller
This document summarizes a presentation about how security teams can adapt to DevOps and continuous deployment models. It discusses how code deployment has shifted to near-instantaneous changes, security is no longer a gatekeeper, and workarounds will happen if security causes delays. To embrace agility, security must decentralize and provide visibility into the development process for all teams, not just security, by surfacing security data. The key lessons are that embracing DevOps actually helps rather than harms security when done with visibility across rapid iterative changes.
This document discusses DevSecOps and provides information about integrating security practices into the DevOps process. It describes how DevSecOps improves upon traditional DevOps by adding security checks to code, containers, and infrastructure. These checks help detect vulnerabilities, sensitive information, and non-compliance before code is deployed. The document also introduces the open-source auditing tool Lynis, which scans servers to identify vulnerabilities and compliance issues across the operating system, network settings, authentication methods, and more.
Organizations enjoy the speed that DevOps brings to development and delivery. However, most security and compliance monitoring tools have not been able to keep up, becoming the most significant barrier to continuous delivery.
Now some good news: you can easily integrate security into your existing processes to solve this challenge.
In this session, Shiri Ivtsan, Senior Product Manager at WhiteSource, will discuss:
- Leveraging the DevSecOps approach to help speed up security
- Scaling security into your agile processes
- 5 easy ways to start driving DevSecOps in your organization
Open Source Security: How to Lay the Groundwork for a Secure CultureWhiteSource
Open-source components are prevalent in approximately 97% of modern applications and dominate anywhere between 60-80% of their codebases. This is hardly surprising given how integrating open source accelerates software development and enables organizations to keep up with today's frantic release pace and standards of constantly supplying new features and improvements.
However, taking into consideration the fact that recent years have seen an upsurge in reported open-source vulnerabilities, whose details and exploits are publicly available, it's no wonder that organizations are increasingly directing focus towards ensuring that their open-source components are securely integrated into their software.
Join Guy Bar-Gil, Product Manager at WhiteSource, as he discusses:
1. The four layers of open-source security
2. How to integrate continuous security into your SDLC
3. Best practices for organizations to own and execute the security process
This document discusses the concepts of DevSecOps at a high level. It begins with a brief history of development methodologies, from Waterfall to Agile, and how Ops became a bottleneck. This led to trends in Agile Operations and collaboration between Dev and Ops, known as DevOps. DevSecOps expands this to incorporate security. It discusses the importance of culture, processes, and technologies for effective communication, automation, and collaboration across Dev, Ops, and Security. The goal is to enable organizations to deliver inherently secure software at DevOps speed through a high-trust environment and automated security pipelines integrated into the software development lifecycle.
In the world of DevSecOps as you may predict we have three teams working together. Development, the Security team and Operations.
The “Sec” of DevSecOps introduces changes into the following:
• Engineering
• Operations
• Data Science
• Compliance
This document discusses DevSecOps, which involves infusing security practices into the development lifecycle to enable faster release cycles while maintaining security. It notes that over 53,000 cybersecurity incidents occurred in India in 2017. Implementing DevSecOps requires changes across an organization's people, processes, tools, and governance to embed security responsibilities across all teams. The typical DevSecOps pipeline shifts security left through activities like threat modeling, security testing, and monitoring throughout the development lifecycle.
DevOps continues to be a buzzword in the software development and operations world, but is it really a paradigm shift? It depends on what lens you view it through.
Roman Garber, an active software security engineering and software team lead thinks so. Ed Adams, Security Innovation CEO, a 20-year software quality veteran and former mechanical engineer, curmudgeonly disagrees.
DevSecCon Asia 2017 Shannon Lietz: Security is Shifting LeftDevSecCon
The document discusses the concept of DevSecOps, which involves taking a holistic approach to shift security left in the software development process. It involves collaboration between developers, operations, and security teams. DevSecOps aims to build security and compliance into software development from the beginning through processes and tools. The document provides examples of how DevSecOps operates and is organized, the skills required, challenges to adoption, and emphasizes the importance of experimentation. It argues that with everyone participating in DevSecOps, safer software can be developed sooner.
- Stefan Streichsbier is the CEO of GuardRails and a professional white-hat hacker who has identified severe shortcomings in security processes and technologies, leading him to create GuardRails.
- The document discusses the evolution of DevOps and increasing complexity, the state of security and how it needs to fit within modern development workflows, and introduces the concept of DevSecOps to address shortcomings and better integrate security.
- Key aspects of DevSecOps discussed include how to create, test, and monitor secure applications and empower development teams to build security in from the start rather than see it as a separate function. Automated security tools and the need to reduce noise and improve usability for developers is also
DevSecOps: Bringing security to the DevOps pipelineAarno Aukia
The document discusses DevSecOps, which aims to automate security practices like testing and monitoring into the development lifecycle. It advocates integrating security practices like static code analysis, dependency management, and container scanning into the build process. For testing, it recommends smoke tests and restricting access to test environments. In deployment, it suggests automating atomic container deployments to remove the need for developer access to production. For operations, it outlines security practices like isolating containers, documenting infrastructure, and preventing configuration drift between environments. The goal is to implement security controls through automation and standardization rather than manual reviews.
The document discusses the rise of DevSecOps and its importance for software development. It notes that existing security solutions are no longer adequate due to the speed of modern development, and that security has become a bottleneck. DevSecOps aims to integrate security practices into development workflows to enable continuous and real-time security. It outlines how security responsibilities have evolved from separate teams to being shared among developers, and how tools have progressed from periodic testing to continuous monitoring and automation. The document argues that DevSecOps is necessary now given the costs of data breaches and risks of vulnerabilities in open source components.
This document discusses how security needs to adapt to keep up with rapid changes in technology and development practices. As internet usage and the number of developers have grown massively, the development process has become more complex, involving tools like AWS and DevOps. However, security has struggled to integrate effectively. The document argues security must improve its developer experience by focusing on high-impact issues, speaking the same language as developers, making tools easy to use, and tightly integrating with development workflows. By learning from how quality evolved, security can become a commodity that developers respect and rely on.
Software Supply Chain Automation Removes Roadblocks to Rugged DevOpsSeniorStoryteller
This document summarizes the benefits experienced by MFS after implementing Jenkins and Nexus to help manage growth in their development organization. Some key points:
1) Jenkins and Nexus helped standardize MFS's development environment, shorten onboarding times, and improve security, code quality, and traceability.
2) Their initial implementation had limited success, but replacing build servers and addressing core issues like branching strategy and artifact management led to wider adoption.
3) Benefits included managing external resources better, inventorying all artifacts, understanding open source licensing risks, and gaining visibility into dependencies and modules.
Safely Removing the Last Roadblock to Continuous DeliverySeniorStoryteller
This document discusses how to implement DevSecOps practices to safely enable continuous delivery. It advocates shifting security left by integrating security practices into development workflows from design through deployment. This allows security issues to be identified and addressed early before they become costly problems. The document outlines DevSecOps staffing models and provides examples of how practices like automated security testing, secure baselines and templates, and monitoring can help operationalize security and reduce mean time to remediate issues from months to hours.
The DevSecOps Showdown: How to Bridge the Gap Between Security and DevelopersDevOps.com
DevSecOps requires processes and tools that enable weaving security throughout the DevOps pipeline. It is much more than a buzzword, and if you'd ask most organizations, well, they believe they are in the process of adopting DevSecOps tools and practices. But, are they?
In order to deeply understand the state of DevSecOps implementation we need to learn more about the relationship between developers and security teams. After surveying more than 560 application security professionals and software developers we found several insights.
Join Jeff Martin, associate VP of product management, and Rhys Arkins, director of product management at WhiteSource, to learn about:
The current challenges of the security and development teams when it comes to AppSec
The contradicting views and gaps between the teams on DevSecOps maturity
How to break the silos and advance toward DevSecOps maturity
Discussion of how security is in crisis but DevSecOps offers a new playbook and gives security a path to influence. Taking a look at the WAF space, we look at how Signal Sciences has created feedback between Dev and Ops and Security to create new value.
DevSecOps is a very loaded term and it includes many topics. Despite what some will lead you to believe, DevSecOps is not just an integration of security testing tools. Nor is it merely a focus on achieving security quality attributes on CI and CD. DevSecOps is beyond the automatizing security testing and there are common misconceptions and roadblocks on how you can establish it successfully.
Learning Objectives:
1: Identify key principles of DevSecOps and see how it relates to DevOps principles.
2: Analyze common pitfalls and see where integration security takes part in DevSecOps.
3: Demonstrate how to do “Continuous Security” by using a lifecycle approach.
(Source: RSA Conference USA 2018)
The practical DevSecOps course is designed to help individuals and organisations in implementing DevSecOps practices, to achieve massive scale in security. This course is divided into 13 chapters, each chapter will have theory, followed by demos and any limitations we need to keep in my mind while implementing them.
More details here - https://www.practical-devsecops.com/
*** DevSecOps: The Evolution of DevOps ***
Have you ever asked yourself the following questions:
What does DevSecOps means?
How is this different from DevOps?
What can we learn from the DevOps movement?
Presentation by James Betteley who shares his experience of shaping DevOps and what he foresees will happen with DevSecOps.
Taking Open Source Security to the Next LevelWhiteSource
Join us for a webinar featuring Forrester VP and Research Director Amy DeMartine to learn more about why open source security has become critical for securing modern applications, the main considerations when evaluating an open source security and license compliance solution and what she sees in store for the future.
Additionally, WhiteSource Senior Director of Product Marketing, Jeff Crum, will discuss recent analysis of the Software Composition Analysis (SCA) market, including takeaways from The Forrester Wave™: Software Composition Analysis, Q2 2019.
The document announces events from DevSecOps Singapore to bring together developers, operations, and security professionals. It describes monthly meetups for talks and networking, workshops over 4 months on integrating security testing into the SDLC, and an annual conference in 2017. It provides announcements for the workshops and conference and calls for speakers, office space, and volunteers to help build the community.
Silver Lining for Miles: DevOps for Building Security SolutionsSeniorStoryteller
This document summarizes a presentation about how security teams can adapt to DevOps and continuous deployment models. It discusses how code deployment has shifted to near-instantaneous changes, security is no longer a gatekeeper, and workarounds will happen if security causes delays. To embrace agility, security must decentralize and provide visibility into the development process for all teams, not just security, by surfacing security data. The key lessons are that embracing DevOps actually helps rather than harms security when done with visibility across rapid iterative changes.
This document discusses DevSecOps and provides information about integrating security practices into the DevOps process. It describes how DevSecOps improves upon traditional DevOps by adding security checks to code, containers, and infrastructure. These checks help detect vulnerabilities, sensitive information, and non-compliance before code is deployed. The document also introduces the open-source auditing tool Lynis, which scans servers to identify vulnerabilities and compliance issues across the operating system, network settings, authentication methods, and more.
Organizations enjoy the speed that DevOps brings to development and delivery. However, most security and compliance monitoring tools have not been able to keep up, becoming the most significant barrier to continuous delivery.
Now some good news: you can easily integrate security into your existing processes to solve this challenge.
In this session, Shiri Ivtsan, Senior Product Manager at WhiteSource, will discuss:
- Leveraging the DevSecOps approach to help speed up security
- Scaling security into your agile processes
- 5 easy ways to start driving DevSecOps in your organization
Open Source Security: How to Lay the Groundwork for a Secure CultureWhiteSource
Open-source components are prevalent in approximately 97% of modern applications and dominate anywhere between 60-80% of their codebases. This is hardly surprising given how integrating open source accelerates software development and enables organizations to keep up with today's frantic release pace and standards of constantly supplying new features and improvements.
However, taking into consideration the fact that recent years have seen an upsurge in reported open-source vulnerabilities, whose details and exploits are publicly available, it's no wonder that organizations are increasingly directing focus towards ensuring that their open-source components are securely integrated into their software.
Join Guy Bar-Gil, Product Manager at WhiteSource, as he discusses:
1. The four layers of open-source security
2. How to integrate continuous security into your SDLC
3. Best practices for organizations to own and execute the security process
This document discusses the concepts of DevSecOps at a high level. It begins with a brief history of development methodologies, from Waterfall to Agile, and how Ops became a bottleneck. This led to trends in Agile Operations and collaboration between Dev and Ops, known as DevOps. DevSecOps expands this to incorporate security. It discusses the importance of culture, processes, and technologies for effective communication, automation, and collaboration across Dev, Ops, and Security. The goal is to enable organizations to deliver inherently secure software at DevOps speed through a high-trust environment and automated security pipelines integrated into the software development lifecycle.
In the world of DevSecOps as you may predict we have three teams working together. Development, the Security team and Operations.
The “Sec” of DevSecOps introduces changes into the following:
• Engineering
• Operations
• Data Science
• Compliance
This document discusses DevSecOps, which involves infusing security practices into the development lifecycle to enable faster release cycles while maintaining security. It notes that over 53,000 cybersecurity incidents occurred in India in 2017. Implementing DevSecOps requires changes across an organization's people, processes, tools, and governance to embed security responsibilities across all teams. The typical DevSecOps pipeline shifts security left through activities like threat modeling, security testing, and monitoring throughout the development lifecycle.
DevOps continues to be a buzzword in the software development and operations world, but is it really a paradigm shift? It depends on what lens you view it through.
Roman Garber, an active software security engineering and software team lead thinks so. Ed Adams, Security Innovation CEO, a 20-year software quality veteran and former mechanical engineer, curmudgeonly disagrees.
DevSecCon Asia 2017 Shannon Lietz: Security is Shifting LeftDevSecCon
The document discusses the concept of DevSecOps, which involves taking a holistic approach to shift security left in the software development process. It involves collaboration between developers, operations, and security teams. DevSecOps aims to build security and compliance into software development from the beginning through processes and tools. The document provides examples of how DevSecOps operates and is organized, the skills required, challenges to adoption, and emphasizes the importance of experimentation. It argues that with everyone participating in DevSecOps, safer software can be developed sooner.
DevSecOps is an increasingly popular approach to software development that emphasizes collaboration between development, security, and operations teams to ensure the security of applications throughout the entire software development lifecycle. In this post, we will explore what DevSecOps is and how it can benefit enterprises. We will also discuss the challenges of implementing DevSecOps and strategies for overcoming them. Finally, we will look at some best practices for enterprise DevSecOps and some tools to consider.
This document discusses the evolution of security practices to enable secure innovation at speed and scale through a DevSecOps approach. It outlines how traditional security controls can be transformed into self-aware, self-reporting components that integrate seamlessly into the DevOps pipeline. Specific examples are provided for how perimeter testing, configuration management, encrypting sensitive data, access management, and multi-factor authentication can move from annual certifications to continuous monitoring and enforcement. The document advocates for collaboration, experimentation, and a focus on simplicity and automation to evolve security practices for DevOps.
DevSecOps is a new way to deliver security as part of the Software Supply Chain. It supports a built-in process and faster security feedback loop for DevOps teams.
Outpost24 webinar: Turning DevOps and security into DevSecOpsOutpost24
DevOps is a revolution starting to deliver. The “shift left” security approach is trying to catch up, but challenges remain. We will go over concrete security approaches and real data that overcome these challenges.
It takes more than adding “hard to find” security talent to your DevOps team to reach DevSecOps benefits. Our discussion focuses on the practical side and lessons-learned from helping organizations gear up for this paradigm shift.
Resolving the Security Bottleneck Why DevSecOps is Better compared to DevOps.pdfMobibizIndia1
DevSecOps is a development methodology that combines security measures at every stage of the software development lifecycle in order to provide reliable and secure systems. DevSecOps, in general, increases the benefits of a DevOps service.
DevSecOps without DevOps is Just SecurityKevin Fealey
The best DevSecOps practices are built alongside strong DevOps practices. However, DevSecOps processes and tooling are often decided within a security silo, rather than by a DevSecOps collective. Security ends up more integrated and efficient than in the past, but the approach is still “bolt-on” and not ultimately streamlined.
Collaboration between security and other DevOps groups around roadmaps and sharing of resources can lead to greater efficiency and innovation, while better supporting the value stream.
This talk will discuss foundational considerations when building a DevSecOps practice. You will learn about the top prerequisites for a successful DevSecOps practice – most of which are provided by groups other than security; and we’ll discuss case studies, both from organizations who have embraced DevOps as a foundation for DevSecOps, and those who haven’t. Attendees will walk away with questions to ask their counterparts in DevOps to understand current DevOps maturity and where security can leverage existing and planned DevOps resources to enable effective DevSecOps.
Dev secops indonesia-devsecops as a service-Amien HarisenNadira Bajrei
DevSecOps is gaining popularity to recent years, thanks to the rapid expansion and adoptions of DevOps. The traditional penetration testing is considered a blocker in a rapid CI/CD deployment. So integrating security in a seamless manner is considered an important upgrade to the DevOps environment.
However, the traditional DevSecOps require huge amount of time, money and effort to implement. Traditional and DevSecOps principle is a culture that depends on teamwork between, the Dev ,Sec, and Ops team, which in real life situation its pretty difficult to realize.
This talk is about how to minimize the whole effort to implement DevSecOps in the current DevOps environment.
First debrief of the Outcomes of the Owasp Summit 2017 (with keynote slides and photos)
Full details at https://owaspsummit.org/
Outcomes at https://owaspsummit.org/Outcomes/
DevSecOps - It can change your life (cycle)Qualitest
QualiTest explains how a secured DevOps (DevSecOps) delivery process can be achieved using automated code scan, enabling significant shift left of issues detection and minimizing the time to fix. Whether you are considering DevSecOps, on the path, or already there, this slide is for you.
For more information, please visit www.QualiTestGroup.com
Outpost24 webinar - application security in a dev ops world-08-2018Outpost24
As DevOps continue to advance, and agile development continues to be widely adopted, the latest OWASP top 10 list shows little to no movement at the top in terms of the most serious vulnerabilities affecting web applications. With a plethora of tools and information to help reduce application vulnerabilities and increase the level of security awareness in development team available, why do we still see web applications as a significant attack vector?
Security teams are often seen as roadblocks to rapid development or operations implementations, slowing down production code pushes. As a result, security organizations will likely have to change so they can fully support and facilitate cloud operations.
This presentation will explain how DevOps and information security can co-exist through the application of a new approach referred to as DevSecOps.
1. The document discusses how security is changing with new technologies like cloud computing, DevOps, and agile development. Traditional security practices are no longer effective.
2. It advocates migrating security left in the development process so it is designed into applications from the beginning. This allows for a faster security feedback loop.
3. Security needs to be automated and tested using tools and data platforms. Monitoring and inspecting everything is important for the new dynamic environments. Security decisions and controls are also changing to adapt to these new realities.
The document discusses product security and how it relates to application security, infrastructure security, and security operations for a specific product or system. It argues that applying DevOps methodologies to traditional application security practices can help make security part of everyday work for developers and operations teams. This will help change an organization's security culture to focus on designing security into products from the start.
DevOps and Devsecops- What are the Differences.Techugo
Pharmaceutical manufacturing software is a tool that streamlines the manufacturing process of pharmaceutical products. The difference between different pharmaceutical manufacturing software lies in their features and capabilities. Some software may focus on specific areas of manufacturing, such as quality control, while others may provide end-to-end solutions for the entire manufacturing process. Factors such as scalability, customization, and regulatory compliance are also important considerations when choosing pharmaceutical manufacturing software. Ultimately, the right software should meet the unique needs of a pharmaceutical manufacturing company and improve their operational efficiency.
10 things to get right for successful dev secopsMohammed Ahmed
This document discusses 10 things that are important to get right for successful DevSecOps implementation. It recommends that security testing be integrated seamlessly into the development process without disrupting developers. It also advises focusing first on identifying and fixing known critical vulnerabilities in libraries and components before custom code, and accepting that not all vulnerabilities can be eliminated. Developers should receive basic secure coding training without being expected to become security experts. The overall goal is to make security processes transparent to developers in order to balance security and speed of development.
DevOps and Devsecops- Everything you need to know.Techugo
DevOps is a software development approach that emphasizes collaboration and communication between developers and IT operations teams to streamline the development and deployment of software. DevSecOps extends DevOps by integrating security into every stage of the software development lifecycle, from planning to deployment, to ensure that security risks are identified and addressed early on.
A two hour workshop that provides a practical introduction to secure coding. This was part of the {DECIPHER} Hackathon (https://www.eventbrite.sg/e/decipher-hackathon-tickets-57968120208).
In the software engineering world, change is the only constant. And in the course of the last decades, the frequency of that change has exploded. What Agile has brought to software teams, DevOps is now bringing to the entire organization. And the results speak for themselves. The DevOps high-performers are killing it. Insane deploy frequencies of features, high reliability of applications, and high productivity of cross-functional teams have amplified the speed at which ideas become a reality.
In parallel, Application Security was doing its own thing and to a large part remained oblivious to all the impressive improvements that were happening in software engineering. Because breaking an application doesn’t need any knowledge of how it was created in the first place.
This talk will cover anti-patterns that are preventing application security from being adopted by development teams, such as:
* Issues Overload
* Acronym Overuse
* Sales team Wall
A Tale of Three Horses - RSAC 2017 APJ - DevOps Connect: DevSecOps Edition, S...Stefan Streichsbier
The document summarizes lessons learned from three companies ("horses") attempting digital transformations. Horse 1 had some quick wins using automation but lacked institutionalization. Horse 2 had a strong team but faced delays and lack of management support. Horse 3 had immense scale and speed but faced communication bottlenecks. The key takeaways are to have full executive support, limit scope, work with experts, automate, and focus on building sustainable habits.
Talk about application security in an agile world. How can security be integrated into agile and how can DevSecOps be leveraged to achieve security at scale at speed.
Application Security in an Agile World - Agile Singapore 2016Stefan Streichsbier
This document discusses application security in an agile development world. It begins with a brief history of application security and defines it as a quality aspect that contributes to business success like user experience and performance. Application security was traditionally handled by network teams but is now the responsibility of developers. The document advocates for adopting a DevSecOps approach where security is integrated into the development process through activities like threat modeling, design reviews, security testing, and monitoring. This allows catching issues earlier in the development cycle when they are cheaper to fix. The document provides examples of how to incorporate security into agile frameworks like Scrum.
Application Security at DevOps Speed - DevOpsDays Singapore 2016Stefan Streichsbier
The document discusses how to integrate security practices into DevOps workflows at speed. It recommends a three step approach: 1) Make security part of agile planning and processes like Scrum, including security training, requirements, testing and demos. 2) Implement a "DevSecOps" pipeline that automates security checks and testing at each stage of development. 3) Continuously measure and reduce security debt and improve app robustness and security skills over time. The goal is to shift security left and make it part of fast-paced DevOps cycles.
Spark is a powerhouse for large datasets, but when it comes to smaller data workloads, its overhead can sometimes slow things down. What if you could achieve high performance and efficiency without the need for Spark?
At S&P Global Commodity Insights, having a complete view of global energy and commodities markets enables customers to make data-driven decisions with confidence and create long-term, sustainable value. 🌍
Explore delta-rs + CDC and how these open-source innovations power lightweight, high-performance data applications beyond Spark! 🚀
Special Meetup Edition - TDX Bengaluru Meetup #52.pptxshyamraj55
We’re bringing the TDX energy to our community with 2 power-packed sessions:
🛠️ Workshop: MuleSoft for Agentforce
Explore the new version of our hands-on workshop featuring the latest Topic Center and API Catalog updates.
📄 Talk: Power Up Document Processing
Dive into smart automation with MuleSoft IDP, NLP, and Einstein AI for intelligent document workflows.
Designing Low-Latency Systems with Rust and ScyllaDB: An Architectural Deep DiveScyllaDB
Want to learn practical tips for designing systems that can scale efficiently without compromising speed?
Join us for a workshop where we’ll address these challenges head-on and explore how to architect low-latency systems using Rust. During this free interactive workshop oriented for developers, engineers, and architects, we’ll cover how Rust’s unique language features and the Tokio async runtime enable high-performance application development.
As you explore key principles of designing low-latency systems with Rust, you will learn how to:
- Create and compile a real-world app with Rust
- Connect the application to ScyllaDB (NoSQL data store)
- Negotiate tradeoffs related to data modeling and querying
- Manage and monitor the database for consistently low latencies
How Can I use the AI Hype in my Business Context?Daniel Lehner
𝙄𝙨 𝘼𝙄 𝙟𝙪𝙨𝙩 𝙝𝙮𝙥𝙚? 𝙊𝙧 𝙞𝙨 𝙞𝙩 𝙩𝙝𝙚 𝙜𝙖𝙢𝙚 𝙘𝙝𝙖𝙣𝙜𝙚𝙧 𝙮𝙤𝙪𝙧 𝙗𝙪𝙨𝙞𝙣𝙚𝙨𝙨 𝙣𝙚𝙚𝙙𝙨?
Everyone’s talking about AI but is anyone really using it to create real value?
Most companies want to leverage AI. Few know 𝗵𝗼𝘄.
✅ What exactly should you ask to find real AI opportunities?
✅ Which AI techniques actually fit your business?
✅ Is your data even ready for AI?
If you’re not sure, you’re not alone. This is a condensed version of the slides I presented at a Linkedin webinar for Tecnovy on 28.04.2025.
Semantic Cultivators : The Critical Future Role to Enable AIartmondano
By 2026, AI agents will consume 10x more enterprise data than humans, but with none of the contextual understanding that prevents catastrophic misinterpretations.
Technology Trends in 2025: AI and Big Data AnalyticsInData Labs
At InData Labs, we have been keeping an ear to the ground, looking out for AI-enabled digital transformation trends coming our way in 2025. Our report will provide a look into the technology landscape of the future, including:
-Artificial Intelligence Market Overview
-Strategies for AI Adoption in 2025
-Anticipated drivers of AI adoption and transformative technologies
-Benefits of AI and Big data for your business
-Tips on how to prepare your business for innovation
-AI and data privacy: Strategies for securing data privacy in AI models, etc.
Download your free copy nowand implement the key findings to improve your business.
Artificial Intelligence is providing benefits in many areas of work within the heritage sector, from image analysis, to ideas generation, and new research tools. However, it is more critical than ever for people, with analogue intelligence, to ensure the integrity and ethical use of AI. Including real people can improve the use of AI by identifying potential biases, cross-checking results, refining workflows, and providing contextual relevance to AI-driven results.
News about the impact of AI often paints a rosy picture. In practice, there are many potential pitfalls. This presentation discusses these issues and looks at the role of analogue intelligence and analogue interfaces in providing the best results to our audiences. How do we deal with factually incorrect results? How do we get content generated that better reflects the diversity of our communities? What roles are there for physical, in-person experiences in the digital world?
Increasing Retail Store Efficiency How can Planograms Save Time and Money.pptxAnoop Ashok
In today's fast-paced retail environment, efficiency is key. Every minute counts, and every penny matters. One tool that can significantly boost your store's efficiency is a well-executed planogram. These visual merchandising blueprints not only enhance store layouts but also save time and money in the process.
Enhancing ICU Intelligence: How Our Functional Testing Enabled a Healthcare I...Impelsys Inc.
Impelsys provided a robust testing solution, leveraging a risk-based and requirement-mapped approach to validate ICU Connect and CritiXpert. A well-defined test suite was developed to assess data communication, clinical data collection, transformation, and visualization across integrated devices.
Book industry standards are evolving rapidly. In the first part of this session, we’ll share an overview of key developments from 2024 and the early months of 2025. Then, BookNet’s resident standards expert, Tom Richardson, and CEO, Lauren Stewart, have a forward-looking conversation about what’s next.
Link to recording, presentation slides, and accompanying resource: https://bnctechforum.ca/sessions/standardsgoals-for-2025-standards-certification-roundup/
Presented by BookNet Canada on May 6, 2025 with support from the Department of Canadian Heritage.
This is the keynote of the Into the Box conference, highlighting the release of the BoxLang JVM language, its key enhancements, and its vision for the future.
TrustArc Webinar: Consumer Expectations vs Corporate Realities on Data Broker...TrustArc
Most consumers believe they’re making informed decisions about their personal data—adjusting privacy settings, blocking trackers, and opting out where they can. However, our new research reveals that while awareness is high, taking meaningful action is still lacking. On the corporate side, many organizations report strong policies for managing third-party data and consumer consent yet fall short when it comes to consistency, accountability and transparency.
This session will explore the research findings from TrustArc’s Privacy Pulse Survey, examining consumer attitudes toward personal data collection and practical suggestions for corporate practices around purchasing third-party data.
Attendees will learn:
- Consumer awareness around data brokers and what consumers are doing to limit data collection
- How businesses assess third-party vendors and their consent management operations
- Where business preparedness needs improvement
- What these trends mean for the future of privacy governance and public trust
This discussion is essential for privacy, risk, and compliance professionals who want to ground their strategies in current data and prepare for what’s next in the privacy landscape.
Procurement Insights Cost To Value Guide.pptxJon Hansen
Procurement Insights integrated Historic Procurement Industry Archives, serves as a powerful complement — not a competitor — to other procurement industry firms. It fills critical gaps in depth, agility, and contextual insight that most traditional analyst and association models overlook.
Learn more about this value- driven proprietary service offering here.
6. 1. Existing solutions are no longer adequate
Provide A Terrible
User Experience
Enterprise Solutions Come
From The Waterfall Era
Enterprise Means
Overpriced
7. 2. SaaS enable wide-spread distribution
Your Users Are EverywhereNo Need To Go
To A Physical Location
No Need to Create
WW Sales Teams
8. 3. Cheaper to create & operate Software
Startup Ecosystems
Empower Entrepreneurs
Open Source Software
Provides Building Blocks
Cloud Computing Provides
Low Barrier of Entry
9. To summarize
The existing solutions
are ripe for replacement
Creating new technology
solutions was never faster
Software can be
Distributed globally
10. DevSecOps:
How important is it really?
• Agile took us from months to days to deliver software
• DevOps took us from months to minutes to deploy software
• More applications are mission critical
• Now security has become the bottleneck
11. The real impact of hacks & breaches
News is full of high-profile breaches that get widespread attention.
But they are not the only target of hackers
43% of all cyber attacks target
small businesses.
60%
of small businesses that are
Hacked go out of business
within 6 months.
1/5
data breaches are the result
of attackers abusing
insecure web applications.
13. The Evolution of Security Tools
Secure SDLCPenetration Testing DevSecOps
Duration 2-4 weeks 1-2 weeks Continuous and Real-time
Tools
• Port Scanners
• Vulnerability Scanners
• Exploitation Tools
Audience
• Security Professionals
Tools
• Code Security Scanners
• Dynamic Security Scanners
• Vulnerability Scanners
Audience
• Security Professionals in
Enterprise Security Teams
Tools
• Code Security Scanners
• Interactive Security Scanners
• Runtime Application Self Protection
Audience
• Developers in Product Teams
14. Security
Development
Operations
The Evolution of Security Teams
Secure SDLCPenetration Testing DevSecOps
Security
Development
Operations
Security
Development
Operations
“Department of NO” “Let’s work together” “How can we help you succeed?”
15. Modern security teams empower dev teams!
100 10 1
Dev Ops Sec: :
: :
Looks like we have a scale problem
18. Mindset within your product teams
• Have Shared Pain and Shared Goals
• Clearly defined global delivery goals (no competing KPIs)
• Measure outcome (customer value), not output
• Be Autonomous
• Maximize flow (minimize cycle times)
• Implement fast automated test suites
• Never pass defects downstream
• Create quality at the source (provide knowledge where needed)
• Full decision authority
• Full Accountability
• Good or bad - you own it. There is no one else to blame
20. Understanding benefits of security controls
Create Test Monitor
Challenges
• Changing human behavior
• Difficult to enforce
• People churn
Benefits
• Reduce new vulnerabilities
Challenges
• Vulnerability Noise
• Fixing issues
• Coverage of issues
Benefits
• Enforceable
• Provide Metrics
Challenges
• Coverage of issues
• Org wide rollout
Benefits
• Enforceable
• Provide Metrics
• Block attacks
Security
21. DevSecOps - Monitor
Are your applications currently
under attack?
Are we automatically defending
against this attack?
What are attackers going after?
• Micro Segmentation
• Runtime Application Self Protection (RASP)
• Bug Bounties
Questions you should be able to answerAvailable Technologies
22. DevSecOps - Test
Do the latest changes introduce
new security issues?
Does our code contain hard-
coded secrets?
Do any of our 3rd party libraries have
known security issues?
Questions you should be able to answer
• Static Application Security Testing (SAST)
• Sensitive Information Scanners (SIS)
• Software Composition Analysis (SCA/CCA)
• Dynamic Security Scanning (DAST)
• Interactive Application Security Testing (IAST)
Available Technologies
24. Where do these tools live?
Source: https://twitter.com/djschleen
25. DevSecOps - Create
Do your teams know the most
common successful attacks?
Who is the dedicated security
contact in a team?
Do your teams know how
to detect and avoid them?
Questions you should be able to answer
• Security Awareness
• Secure Coding Training
• Shared Knowledge Base
• Security Focused Hackathons
• Security Champion Program
Available Options
26. DevSecOps
Do we really need it now?
There are some compelling statistics
• It’s 30 times cheaper to fix security defects in development vs production
• 80% to 90% of modern applications consist of open source components
• An average data breach costs 5M+ USD
• Most of the DevOps high-performers include security in their delivery process
Security as Competitive Advantage
27. State of DevSecOps - Conclusion
Security TeamTechnologies Product Team
• Tools have improved
• Choose them wisely
• Solve technology problems
• Cover the whole portfolio
• Start acting on data in prod
• Department of YES
• Empowering product teams
• Use scarce resources wisely
• Knowledge is power
• Turn developers into security champs
• Be mindful that change is slow
• Build it, run it, secure it
29. Get a curated list of security resources
Consisting of:
• Awesome security lists
• Developer trainings
• List of great security tools
• Security Page templates
• Free digital copy of my book
• the slides
• … and more
Then send an email to:
[email protected]
Editor's Notes
#2: Welcome everonye,
good to be here,
Great turnout
#4: The are all from Indonesia!
They are all tech companies.
The are all considered unicorns (valued over 1 billion)
They didn’t exist 10 years ago.
#5: And by the way, how many of you here today are in a fintech or any other kind of tech company startup? fintech slide -> You may join the unicorn club soon.
#6: It's astonishing how this game of david and goliath has changed the world in the last decade.Now, why is that possible?
Software has become mission-critical!
#7: 1.) The existing solutions (in all industries) typically suck. -> The foundation of this opportunity.Simply put a lot of the existing incumbent solutions (in all industries) are coming from the waterfall era, have a terrible User Experience and follow an enterprise software model.Think about it, even the online banking solutions that exist today are typically much more user-friendly for consumers than they are for business users. -> Waterfall vs Agile vs DevOps"Wait, I have to use this stuff to collaborate? If I can use Facebook Messenger at home, why do I have this crummy messaging tool at work?" So that's certainly been one angle that I think has changed things.
#8: 2.) Software as a service and the internet in general allow wide-spread and instant distribution.Second is, obviously software as a service and the internet generally, you know, our ability, so we sell into 170 different countries now, so we never could have done that in a traditional enterprise model. We would have needed sales people all over the world, etc. So we can spread out the revenue generation, if you like, much more around the globe, much more quickly.
#9: 3.) The cost of producing and operating software has gone down significantly.The entry barrier is almost removed. And at the same time, the cost of producing that service or creating that software has gone down rapidly with open source, and cloud computing in terms of AWS, things like that. So we can effectively deliver a better product for cheaper and kind of instantly get it around the world and just let it bubble up.Cloud providers offer up to 100k credits for startups.Every major Saas product that a company needs either offers free plans for startups or heavily reduced prices.
Cloud computing
#10: Litmus test, how long does it take you to get one line of code through your system?
#11: DevOps is all about breaking down barriers, have developers work with the business, with the ops team and simply out-innovate and out-ship the competition.
Software has become mission-critical!
#12: While hacking-related data breaches and subsequent ransom demands to large corporations like HBO, Target, and Home Depot understandably garner widespread attention, t
he resulting assumption that only large companies face this growing digital threat couldn’t be further from the truth. In fact, a study in 2016 found that 43% of all cyber attacks targeted small businesses.
Even more alarming is that a staggering 60% of small businesses hit with a cyber attack or data breach go out of business within 6 months.
Software has become mission-critical!
#14: Different Tools come from different eras and are focused on outcomes and different audiences.
#15: Working as an audit/control function
Working as security gates in the lifecycle
Empowering DevOps teams to move fast and be safe.
#16:
Alright, so the purpose of security teams
Is to support the engineering organization
To ensure that the business can achieve
Their goals.
However, there is a scale problem.
Think about how many developers you have in your organization.
How many DevSecOps ready security folks?
There is a global shortage of 2m cyber security professionals,. It just can’t be solved by throwing security people at the problem
You gotta be smart,
#17: The traditional model is that you take your software to the wall that separates development and operations, and throw it over and then forget about it.
Let’s look at how the big organizations are doing it.
https://www.slideshare.net/ufried/the-truth-about-you-build-it-you-run-it
#18: You build it you secure it. What does that mean?
It’s not a question of responsibility it’s a question of accountability.
Why would any third party come and tell you what to do, they don’t know the context, don’t know the other stuff.
Why would they run a tool for you that produces a million findings, and leave you with the results to clean it up?
Oh and by the way, you have to get rid of all the medium and high before going live.
The security team can not be accountable. Ok, so who is accountable?
That also means that business can make decisions to override security requirements.
Believe me, I am coming from a pentesting background, and there is no perfect security posture.
So you gotta think about getting the guardrails established, at the very minimum. Get rid of all the low hanging fruits.
Avoid counter productive best practices.
#21: Outside in approach
Get data -> attacks, vulnerabilities, etc
Don’t focus on 1 application, focus on getting this data for the whole portfolio (prioritize by business risk).
Where can you solve technology problems reliably across
Quality, Performance, Security
#22: Think Application Performance monitoring for security
Understanding how your app is abused and misused helps with prioritization.
#23: Think Application Performance monitoring for security
Understanding how your app is abused and misused helps with prioritization.
#27: To give an analogy, Software doesn't have to be of high quality and excellent user experience. most of the successful enterprise software did not provide these and they did succeed - until now at least. But now many of these organizations are struggling heavily, because their entire culture and processes are outdated and they are moving very slow. No matter how much money these orgs have, it is still a tricky process, because it's attempting to change the culture. Another example is Tesla. Stunning cars, that delight users all over the world. They designed a new car from the ground up. Many of their competitors spending a lot of money and time to retrofit their cars and convert them into more and more smart cars. But Tesla is a supercomputer on wheels and is out innovating the competition. The key point is that certain aspects that may not seem that relevant at the moment, will become the decisive advantage in the future.
You can’t develop software and expect it to be secure after an audit at the end.
Same way you can’t say now that the feature is shipped make sure it performs well and doesn’t have any bugs.
Thebest time to plant a tree was 20 years ago. The second best time is now.
That’s why we see many new organisations succeed, because they don’t carry the same baggage and can get things right from the start.
Despite the challenges of identifying quality metrics that apply to all organizations, we can identify good proxies for quality that work across companies and industries.These include how time is spent, because it can tell us if we are working on value-add work or non-value-add work.
#28: Focus on the right improvements, e.g measuring defect density, etc.
E.G if a technology can reliably identify and prevent a vulnerability in production, without having to involve humans to fix it, then
That’s a good start. If you can have technology that alerts you of breaches while containing them, that’s great. Use it.
If you have tools that you can embed in your pipeline to get more continuous security feedback into the hands of developers, then use that
Be smart about where to use human efforts on and where not to.
Security team should help engineering teams to succeed and achieve their mission.
Not say no and delay releases like an audit function.
Start with general training programs, there is excellent free training out there for engineers and basic security awareness.
As you get more data from your tools, then you will be able to prioritize the next focus areas and teams that require that training.
Teaching people and changing the culture is hard and takes a long time. It is still important but make sure all the other aspects are
Reducing your risk while simultaneously buying time.