NVD slowdown leaves thousands of vulnerabilities without analysis data

The United States National Institute of Standards and Technology (NIST) has almost completely stopped adding analysis to Common Vulnerabilities and Exposures (CVEs) listed in the National Vulnerability Database. That means big headaches for anyone using CVEs to maintain their security.  It was just another day, February 15th, …

[Doctor Syntax]

I doubt the opposition is slowing down.

[ChoHag]

> What can we do?

Pay up.

[Munchausen's proxy]

I'd bet $5 that it was two people doing all the work, and they left, one at a time while HR was was completely ignoring their manager's desperate cries for a new hire or two.

[OrangeDog]

It gets worse

Meanwhile, the NVD API basically died a week ago, with major outages causing various scanning tools to fail, and people to scrabble about looking for mirrors and caches.

[Anonymous Coward]

Re: It gets worse

The NVD API changes have been announced for absolutely ages. Those not paying attention and making the required changes (or demanding that their vendors make the required changes) only have themselves to blame.

Our NVD access is still live and updated at 0815 this morning, the NVD API is working fine.