Why is it that security guys always think their issues are more important than any other issues?
Like well done you, you ran an automated tool over the codebase and it picked up some outdated dependencies.
We cant just update these dependencies because the newer versions have breaking changes and we already have a backlog of 32767 issues to deal with.
It’s not security debt, it’s just general technical debt.
Why is the issue that is only exploitable in a contorted scenario where the user has broken out of a VM and gained root on the hypervisor more important than the issue preventing our largest customer from tripling their volume on our platform?
Not to mention the joke that’s been made of the CVE system due to resume padding by the security industry…
Generally a regular issue is much less likely to get you hacked.
Security issues often come with legal liability which is why a bad security department will act overly important and stomp around demanding changes be made right the fuck now.
But I do get it, a good security team should be enabling their dev teams to solve issues in the least disruptive way possible, not just thrown them work and barking orders.
In some places I have worked, the sec teans will find an issue and push PRs to fix them, explaining the security concern, and requesting only a review and merge.
Why is it that security guys always think their issues are more important than any other issues?
Like well done you, you ran an automated tool over the codebase and it picked up some outdated dependencies.
We cant just update these dependencies because the newer versions have breaking changes and we already have a backlog of 32767 issues to deal with.
It’s not security debt, it’s just general technical debt.
Why is the issue that is only exploitable in a contorted scenario where the user has broken out of a VM and gained root on the hypervisor more important than the issue preventing our largest customer from tripling their volume on our platform?
Not to mention the joke that’s been made of the CVE system due to resume padding by the security industry…
Generally a regular issue is much less likely to get you hacked.
Security issues often come with legal liability which is why a bad security department will act overly important and stomp around demanding changes be made right the fuck now.
But I do get it, a good security team should be enabling their dev teams to solve issues in the least disruptive way possible, not just thrown them work and barking orders.
In some places I have worked, the sec teans will find an issue and push PRs to fix them, explaining the security concern, and requesting only a review and merge.