60
Insecure software makers are the real cyber villains – CISA (www.theregister.com)
submitted 22 hours ago by [email protected] to c/[email protected]
5 comments fedilink hide all child comments

Software suppliers who ship buggy, insecure code are the true baddies in the cyber crime story, Jen Easterly, boss of the US government's Cybersecurity and Infrastructure Security Agency, has argued.

"The truth is: Technology vendors are the characters who are building problems" into their products, which then "open the doors for villains to attack their victims," declared Easterly during a Wednesday keynote address at Mandiant's mWise conference.

Easterly also implored the audience to stop "glamorizing" crime gangs with fancy poetic names. How about "Scrawny Nuisance" or "Evil Ferret," Easterly suggested.

Even calling security holes "software vulnerabilities" is too lenient, she added. This phrase "really diffuses responsibility. We should call them 'product defects,'" Easterly said. And instead of automatically blaming victims for failing to patch their products quickly enough, "why don't we ask: Why does software require so many urgent patches? The truth is: We need to demand more of technology vendors."

you are viewing a single comment's thread
view the rest of the comments
[-] [email protected] 11 points 21 hours ago

That seems like a myopic view. Service misconfiguration is not always a vendor's fault, and demanding software vendors to patch their products is not going to fix OSS vulnerabilities. In fact, we've seen examples this year of increased pressure to fix "issues" leading to developers unwittingly accepting malicious commits.

Mind you, I'm not contesting that some vendors produce dogshit products (looking at you, CrowdStrike), but calling all vendors villains is a bit of a stretch.

[-] [email protected] 4 points 20 hours ago

I'm not sure I fully agree with you, partly because she's not talking about OSS alone. Let's look at a recent but important example.

Yubikeys manufactured before firmware version 5.7 (before May 2024), are vulnerable to a specific type of attack that is not novel, due to a faulty IC via its code. It's something that should have been caught during QA. Who is to blame?

Yubikey didn't make the faulty IC, so obviously the IC maker should bear at least a good chunk of it, but I think it's Yubikey's responsibility to verify their work, especially since they're the ones making the ultimate promise of cryptographic suitability that businesses and governments rely upon.

I don't know if it's right to call companies like this "villains," but I think "lazy or lax" might be appropriate. Additionally, I like the idea of calling cybercrime groups funny names.

load more comments (1 replies)
this post was submitted on 21 Sep 2024
60 points (96.9% liked)

Cybersecurity

5409 readers
238 users here now

c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.

THE RULES

Instance Rules

Community Rules

If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.

Learn about hacking

Hack the Box

Try Hack Me

Pico Capture the flag

Other security-related communities [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]

Notable mention to [email protected]

founded 1 year ago
MODERATORS
[email protected]
[email protected]