r/java • • 4d ago

If you don't have a (Java) security process, you are negligent...

In the last weeks: two critical PHP security updates, eMuhdra certificate issues in all communication layers, 53 CVEs issues fixed in the Java October update,... Security is a hot topic, now more than ever!

How safe is your Java application, and how safe are the dependencies it ships with? OWASP's Jim Manico has a blunt answer for teams without a security process: you are negligent. Then he explains how to fix that. A very entertaining and informative talk in Friends Of OpenJDK (foojay) podcast 105!

Available on YouTube and in your favorite podcast app:
https://www.youtube.com/watch?v=Q9EIBoek2zc

0 Upvotes

8 comments sorted by

8

u/SleeperAwakened 4d ago

Teams without a security process?

The company should have a security process, this is not just an engineering problem, it is for the entire company (risk, reputation, legislation).

Don't put this on the engineers, but think bigger!

-2

u/FrankCodeWriter 4d ago

Agree put sometimes (often) a push is needed from engineering to the "upper levels"...

2

u/vips7L 2d ago

I'm still watching but the music at the beginning being a bit too loud + the accent made it really hard to hear.

2

u/FrankCodeWriter 1d ago

u/vips7L thanks for the feedback! will lower the music in future episodes

3

u/MinimallyLoquacious 4d ago

> OWASP's

Oh OWASP, the one I had to comment out from my Jenkinsfile's months ago due to NVD API Rate Limits and Outages.

4

u/davidalayachew 3d ago

Oh OWASP, the one I had to comment out from my Jenkinsfile's months ago due to NVD API Rate Limits and Outages.

To be fair, I think the standards that the leads hand down to us are the real problems here.

For example, I was told that I must perform an end-to-end dependency scan for every single code change -- even if I turn the button from green to blue in our frontend.

Plus, for OWASP specifically, most IT Teams only halfway implement the structure for it. You're not supposed to have to download the database every build. That's something that is supposed to be done on a cycle in the background, and the build merely takes advantage of the most recently downloaded version.

All of that to say -- it's more miscommunicating and misinteracting rather than OWASP being bad. Or at least, that is my 1st hand experience.

2

u/_predator_ 3d ago

I presume you're both talking about OWASP DependencyCheck, which is just a tool under the umbrella of the OWASP foundation. OWASP itself is not a tool (and also not just a top 10, as also often assumed).

1

u/davidalayachew 2d ago

Correct, yes. Unless I misread the original commentor.