Knowing where vulnerabilities exist is only helpful when you can actually treat them. Unfortunately, a vast majority can only be corrected within an organization’s custom code.
Some organizations write custom patches, but contend with open source software package updates that break those custom patches, so there are significant forward compatibility challenges.
There’s no point in playing security whack-a-mole.
#OSS #cybersecurity
There’s no point in playing security whack-a-mole.
#OSS #cybersecurity
What dev, security & infrastructure teams need to know to improve test cycles:
👉 What software components are running in a workload
👉 What components actually gets used
👉 What components can be eliminated
👉 What vulnerabilities exist after unused components are eliminated
👉 What software components are running in a workload
👉 What components actually gets used
👉 What components can be eliminated
👉 What vulnerabilities exist after unused components are eliminated
It’s more important to understand how a workload functions than it is to understand where vulnerabilities exist.
Get the full scoop in on how to Stop Chasing Vulnerabilities & Start Improving Test Cycles: loom.ly/OakpAAE
Get the full scoop in on how to Stop Chasing Vulnerabilities & Start Improving Test Cycles: loom.ly/OakpAAE
• • •
Missing some Tweet in this thread? You can try to
force a refresh
