{"id":559,"date":"2004-09-02T00:00:00","date_gmt":"2004-09-02T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/09\/02\/security-vendor-directory-to-aid-responsible-disclosure\/"},"modified":"2021-12-30T11:37:41","modified_gmt":"2021-12-30T11:37:41","slug":"security-vendor-directory-to-aid-responsible-disclosure","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/09\/02\/security-vendor-directory-to-aid-responsible-disclosure\/","title":{"rendered":"Security vendor directory to aid responsible disclosure"},"content":{"rendered":"<p>In a step that researchers hope will improve the responsible disclosure process, the Open Source Vulnerability Database (OSVDB) today published a free security vendor directory that it hopes will serve as a centralized resource for vendor contact information.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>&#8220;The function of the [directory] is merely a foundation for how OSVDB intends to revolutionize the way vulnerabilities are disclosed to the vendor,&#8221; Brandon Shilling, a member of the OSVDB development team, said in a statement.<\/p>\n<p>&#8220;[It&#8217;s] the first phase for additional upcoming services including assisting researchers with ethically disclosing vulnerabilities, helping to verify vulnerabilities and the OSVDB vulnerability portal.<\/p>\n<p>http:\/\/searchsecurity.techtarget.com\/originalContent\/0,289142,sid14_gci1003346,00.html<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29],"tags":[],"class_list":["post-559","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/559","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=559"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/559\/revisions"}],"predecessor-version":[{"id":3046,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/559\/revisions\/3046"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=559"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=559"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=559"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}