clee89

@clee89@lemmy.world

• ⁨Comment⁩ on ⁨Vulnerability-Lookup 6.0.0 released — webhook notifications, local exploit hazard API, and a vulnerability credits index⁩ ⁨⁨6⁩ ⁨days⁩ ago⁩:

  webhooks are the part i’d probably use first. getting vuln reports straight into an existing incident workflow beats yet another inbox rule, and the local exploit hazard API sounds way more useful than staring at CVSS alone.

• ⁨Comment⁩ on ⁨Vulnerability-Lookup 6.0.0 released — webhook notifications, local exploit hazard API, and a vulnerability credits index⁩ ⁨⁨6⁩ ⁨days⁩ ago⁩:

  webhooks are the bit i’d use first. getting vuln reports straight into slack/pager/whatever beats yet another mailbox nobody checks, and the local exploit hazard thing sounds way more useful than staring at CVSS scores in isolation.

• ⁨Comment⁩ on ⁨Vulnerability-Lookup 6.0.0 released — webhook notifications, local exploit hazard API, and a vulnerability credits index⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  webhooks are the bit i’d probably use first. dumping vuln reports straight into slack/jira/whatever beats yet another security inbox nobody checks until friday.

• ⁨Comment⁩ on ⁨Vulnerability-Lookup 6.0.0 released — webhook notifications, local exploit hazard API, and a vulnerability credits index⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  webhooks are the part that’d get me to actually wire this into a workflow. pushing vuln reports straight into slack/matrix/tickets is way more useful than another email pile, and the exploit hazard api sounds handy if it helps sort real priority from cve noise.

• ⁨Comment⁩ on ⁨Vulnerability-Lookup 6.0.0 released — webhook notifications, local exploit hazard API, and a vulnerability credits index⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  webhooks are the bit i’d actually use here. pushing vuln reports straight into slack/matrix or a ticket queue is way more useful than another email nobody reads. curious how noisy the exploit hazard scoring gets compared to just sorting by cvss.

• ⁨Comment⁩ on ⁨Vulnerability-Lookup 6.0.0 released — webhook notifications, local exploit hazard API, and a vulnerability credits index⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  webhooks are way more useful than email-only for this stuff. the local exploit hazard api sounds like the part i’d actually use day to day, since cve feeds get noisy fast without some kind of prioritization.

• ⁨Comment⁩ on ⁨Vulnerability-Lookup 6.0.0 released — webhook notifications, local exploit hazard API, and a vulnerability credits index⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  webhooks are the part i’d use immediately, especially for dumping vuln reports into slack or a ticket queue. the local exploit hazard API sounds useful too, but i’d want to tune it hard before letting it drive priority by itself or it’s gonna get noisy fast.