{"id":1289,"date":"2004-02-20T00:00:00","date_gmt":"2004-02-20T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/02\/20\/marimba-to-update-security-patch-managment-software\/"},"modified":"2021-12-30T11:39:06","modified_gmt":"2021-12-30T11:39:06","slug":"marimba-to-update-security-patch-managment-software","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/02\/20\/marimba-to-update-security-patch-managment-software\/","title":{"rendered":"Marimba to Update Security Patch Managment Software"},"content":{"rendered":"<p>Marimba Inc. on Monday,02\/23\/2004 will step up its efforts to move into the patch-management space with the launch of Version 2 of Marimba Security Patch Management.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The new user-driven features include an integrated patch repository that can automatically collect patch information from Microsoft Corp. and Sun Microsystems Inc. as well as Shavlik Technologies LLC, a small patch-management vendor that collects information about patches and provides it in machine-readable format, including dependencies and meta data associated with a patch.<\/p>\n<p>&#8220;This product allows you to simulate a patch being installed on an end-point, and you can do end-path analysis,&#8221; described Purnima Padmanabhan, director of product management at Marimba of Mountain View, Calif.<\/p>\n<p>The simulator can determine before deployment which patches will install on end-points and which will not, which patches are obsolete; and it will identify patch conflicts and installation order.<\/p>\n<p>Within one shot, you know how many [end-points] are compliant or are not compliant,&#8221; Padmanabhan said.<\/p>\n<p>http:\/\/www.eweek.com\/article2\/0,4149,1533017,00.asp?kc=EWRSS03119TX1K0000594<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-1289","post","type-post","status-publish","format-standard","hentry","category-product"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1289","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=1289"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1289\/revisions"}],"predecessor-version":[{"id":3776,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1289\/revisions\/3776"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1289"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1289"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1289"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}