{"id":2010,"date":"2003-11-08T00:00:00","date_gmt":"2003-11-08T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2003\/11\/08\/banking-on-it-compliance-commitment-and-credibility\/"},"modified":"2021-12-30T11:40:28","modified_gmt":"2021-12-30T11:40:28","slug":"banking-on-it-compliance-commitment-and-credibility","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2003\/11\/08\/banking-on-it-compliance-commitment-and-credibility\/","title":{"rendered":"Banking on IT: Compliance, Commitment, and Credibility"},"content":{"rendered":"<p>By 2005\/06, DR operational availability models (technology and process) and business continuity planning (BCP) will overlap.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>CIOs should provision contingencies for business continuity and address the disaster recovery and continuous availability of systems to minimize the impacts of outages and to further ensure the IT organization&#8217;s credibility.<\/p>\n<p>A note of caution, however: two-hour recovery time objectives (RTOs) are typically 10x regular operating costs.<\/p>\n<p>Short-term vs. long-term compliance activities: Some CIOs will find it in necessary to provide for a longer implementation period in light of their organization&#8217;s respective risk profile, level of resilience, and unique business circumstances.<\/p>\n<p>Bottom Line: CIOs must commit to robust recovery capabilities and prepare the ITO to respond to a wide-scale disruption by adopting sound BCP and DR practices.<\/p>\n<p>META Group originally published this article on 29 October 2003.<\/p>\n<p>More info: [url=http:\/\/techupdate.zdnet.com\/techupdate\/stories\/main\/Banking_on_IT.html?tag=tu.scblog.meta.6673]http:\/\/techupdate.zdnet.com\/techupdate\/stories\/main\/Banking_on_IT.html?tag=tu.scblog.meta.6673[\/url]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11],"tags":[],"class_list":["post-2010","post","type-post","status-publish","format-standard","hentry","category-trends"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2010","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=2010"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2010\/revisions"}],"predecessor-version":[{"id":4497,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2010\/revisions\/4497"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=2010"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=2010"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=2010"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}