SeanWrightSec

SeanWrightSec

@seanwrightsec.com

Principal Application Security Engineer focused on all things #AppSec. Occasionally dabble in my own research. Also keen gamer and aspiring photographer.

1.9K followers124 following305 posts

This is a really tough time of the year for me. I lost my own father 7 years ago. And while it does become easier to cope over time, it’s still difficult. What makes it harder this time is seeing people celebrating the death of someone else’s father all because they don’t agree with their viewpoints

I’ve given this advice to several folk, and it’s worth sharing with others. Learning how to become comfortable with not knowing something is liberating. It’ll help give you the confidence to then do something about it.

This is so important in our field as we have a constant barrage of new things (technology, attack types, etc). It’s not an easy thing to do, and does take time. But once you are at peace with it, it’ll help things for the better.

A really important reason why it’s important to have security tooling working and operating as you expect. It’s already difficult to get other teams to buy into these tools so when they are constantly “wrong”, getting those teams onboard is almost impossible.

Important to note that CVE is not a database per se. This is why we have the likes of NVD. So if anything, ENISA would be competing with NVD. But I still have concerns of how this may fragment the ecosystem.

One key item of security is accountability. Without it, there’s no single person to go to get a system patched. Processes and procedures don’t get revised or updated. The same procedures and processes are not followed. And the list goes on.

This may actually be a good model to follow instead. Being reliant on a single source has its obvious risks. This is somewhat similar to Let’s Encrypt in some sense, and look at how that turned out and the change it is having. Perhaps this is a better path forward?

Daniel Cuthbert@dcuthbert.bsky.social

Positive www.thecvefoundation.org Without the CVE process, we don't have any real way, besides legislation (which I'm arguing will help too) to keep vendors honest and hold them to account. Here's hoping good comes out of recent events

Another great writeup by @kateoflaherty.bsky.social. Thank you for including my comments. I think it’s important to avoid speculation at this stage and wait for the details to come out. And then take it from there. Who knows what the eventual outcome may be.

Already seen a lot of confusion going on. It’s important to understand that Mitre does not operate the National Vulnerability Database (NVD). While NVD does ingest CVE’s from Mitre, it does not operate this database…

View full thread

So the recent news about Mitre’s contract would likely only affect new vulnerabilities. Historical vulnerabilities should not be affected. It’s important to call this distinction out, as there’s already been some confusion.

While not great, hopefully we will be able to find out further details in the next couple of days. Also important, it’s the NVD team that enriches the CVE (e.g. assign a CVSS score).

Already seen a lot of confusion going on. It’s important to understand that Mitre does not operate the National Vulnerability Database (NVD). While NVD does ingest CVE’s from Mitre, it does not operate this database…