{"id":123,"date":"2006-02-15T00:00:00","date_gmt":"2006-02-15T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2006\/02\/15\/security-in-the-cloud-is-not-the-way-to-go\/"},"modified":"2021-12-30T11:36:34","modified_gmt":"2021-12-30T11:36:34","slug":"security-in-the-cloud-is-not-the-way-to-go","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2006\/02\/15\/security-in-the-cloud-is-not-the-way-to-go\/","title":{"rendered":"&#8216;Security in the cloud&#8217; is not the way to go"},"content":{"rendered":"<p>One of the basic philosophies of security is defense in-depth: overlapping systems designed to provide security even if one of them fails.  An example is a firewall coupled with an intrusion-detection system (IDS).  Defense in-depth provides security because there&#8217;s no single point of failure and no assumed single vector for attacks.  If we could build a new Internet today from scratch, we would embed a lot of security functionality in the cloud.  [For email ]They do a great job of filtering out spam and viruses, but it would be folly to consider them a substitute for anti-virus security on the desktop.  <\/p>\n<p>Smart organizations build defense in-depth: e-mail filtering inside the cloud plus anti-virus on the desktop.  Real-time monitoring and response is what&#8217;s most important; where the equipment goes is secondary.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>It is for this reason that a choice between implementing network security in the middle of the network &#8212; in the cloud &#8212; or at the endpoints is a false dichotomy.  An organization had no choice but to put its firewalls, IDSs and anti-virus software inside its own network.  Security would be vastly improved if the major carriers implemented cloud-based solutions, but they&#8217;re no substitute for traditional firewalls, IDSs and IPSs.<\/p>\n<p>http:\/\/www.computerworld.com.au\/index.php\/id;1786107200;fp;16;fpid;0<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-123","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/123","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=123"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/123\/revisions"}],"predecessor-version":[{"id":2610,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/123\/revisions\/2610"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=123"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=123"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=123"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}