Look, it’s great news that MITRE got funded for another year of CVE but we all know this is only a bandaid and the real solution to the CVE problem is going to be my shared google sheet.

@jerry lol

Penetrate and patch is dead. Long live penetrate and patch.

@jerry pls snd to my signal thx!
@pH_0x05 @jerry oh that’s a good idea, wouldn’t want hackers to get access to the list of vulnerabilities
Bernard Quatermass (@[email protected])

In keeping with our new modern vulnerability aesthetic all security flaws will be issued Lamer Llama IDs. Discussion of any flaws must be referred to as Lamer Llama Ding Dongs.

Infosec Exchange
@jerry And here we are again, it's that time of the... *checks notes* week.
https://xkcd.com/927/
Standards

xkcd
@christopherkunz this will definitely be the one spreadsheet to rule them all
GitHub - CVEProject/cvelistV5: CVE cache of the official CVE List in CVE JSON 5 format

CVE cache of the official CVE List in CVE JSON 5 format - CVEProject/cvelistV5

GitHub
@jerry no, it should be an Excel sheet with tons of macros on an SMB share with versioning done by copying the file into a directory called "backup" and appending the current date to the name
@jerry Is that the same google sheet you store your passwords in? I like to keep all my eggs in one basket security wise. Makes all the answers easy to find.
@jerry I feel like that Google sheet needs to be replicated in Excel in M365 and backed up to an S3 bucket. Now that’s security!!