Главная
Study mode:
on
1
Introduction
2
Alarm went off
3
Why is this important
4
Security is hard job
5
Agenda
6
Quick recap
7
Timeline
8
Log4J
9
InsecureBank
10
Log for Shell
11
Vulnerability detection
12
Instrumentation
13
Risk Analysis
14
Summary
15
Continuous Security Scanning
16
Automate through tooling
17
What does Captain do
18
Captain overview
19
The big picture
20
Wrap up
Description:
Explore the impact of Log4Shell on DevSecOps practices and learn strategies to strengthen software supply chain security in this DevOpsDays Boston 2022 conference talk. Delve into real-world stories from DevSecOps teams on the frontlines during the Log4Shell incident, examining application security approaches and tools for detecting vulnerabilities during delivery and production. Discover how open-source projects like Falco and Keptn can help enforce a "Secure by Default" policy. Gain insights into vulnerability detection, instrumentation, risk analysis, and continuous security scanning. Understand the importance of automating security processes through tooling and explore the role of Captain in enhancing DevSecOps workflows.

DevSecOps by Default: Lessons from Log4Shell - What We Have, Can, and Must Learn

Confreaks
Add to list