{"id":601,"date":"2005-09-02T00:00:00","date_gmt":"2005-09-01T22:00:00","guid":{"rendered":"https:\/\/wwwneu.strehle.de\/tim\/weblog\/archives\/2005\/09\/02\/536\/"},"modified":"2005-09-02T00:00:00","modified_gmt":"2005-09-01T22:00:00","slug":"536","status":"publish","type":"post","link":"https:\/\/www.strehle.de\/tim\/weblog\/archives\/2005\/09\/02\/536\/","title":{"rendered":"Time for a stand-down review"},"content":{"rendered":"<p>Roger A. Grimes at InfoWorld &#8211; <a href=\"http:\/\/www.infoworld.com\/article\/05\/09\/02\/36OPsecadvise_1.html\" title=\"Time for a stand-down review | InfoWorld | Column | 2005-09-02 | By Roger A. Grimes\">Time for a stand-down review<\/a>:<\/p>\n<p>\u201cI propose that one of the best cost\/benefit security moves any company can make is to take a step back, review the current security configuration of its assets, and fix the basics before looking into more advanced solutions. Spending a week or two doing this can provide immediate returns, compared with waiting for a three-year payback on an unproven device or solution.<\/p>\n<p>I have to admit that this idea isn\u2019t my own \u2013 it\u2019s stolen from the military. For example, every few years the military suffers from a spate of \u201crandom\u201d incidents such as, say, airplane or helicopter crashes, accidental weapons fire, or unpredictable cases of post-traumatic stress. When management (the generals, admirals, or commanders) note a spike in such events, they often order a stand-down, which requires the entire affected force to drop all non-essential duties for the entirety of the stand-down period.<\/p>\n<p>Everyone must re-examine current SOPs (standard operating procedures) to see if they need to be modified or, more likely, how they aren\u2019t being universally applied. Either way, after the stand-down review period, the spate of random incidents always seems magically to decrease.\u201d<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Roger A. Grimes at InfoWorld &#8211; Time for a stand-down review: \u201cI propose that one of the best cost\/benefit security moves any company can make is to take a step back, review the current security configuration of its assets, and fix the basics before looking into more advanced solutions. Spending a week or two doing [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","_share_on_mastodon":"0"},"categories":[1],"tags":[],"class_list":["post-601","post","type-post","status-publish","format-standard","hentry","category-weblog"],"share_on_mastodon":{"url":"","error":""},"_links":{"self":[{"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/posts\/601","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/comments?post=601"}],"version-history":[{"count":0,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/posts\/601\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/media?parent=601"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/categories?post=601"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/tags?post=601"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}