{"id":119,"date":"2006-01-24T00:00:00","date_gmt":"2006-01-24T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2006\/01\/24\/19-ways-to-build-physical-security-into-a-data-center\/"},"modified":"2021-12-30T11:36:33","modified_gmt":"2021-12-30T11:36:33","slug":"19-ways-to-build-physical-security-into-a-data-center","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2006\/01\/24\/19-ways-to-build-physical-security-into-a-data-center\/","title":{"rendered":"19 Ways to Build Physical Security into a Data Center"},"content":{"rendered":"<p>There are plenty of complicated documents that can guide companies through the process of designing a secure data center&#8212;from the gold-standard specs used by the federal government to build sensitive facilities like embassies, to infrastructure standards published by industry groups like the Telecommunications Industry Association, to safety requirements from the likes of the National Fire Protection Association.  Read this [excellent] article to find out how a fictional data center is designed to withstand everything from corporate espionage artists to terrorists to natural disasters.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>1. Build on the right spot<br \/>\n2. Have redundant utilities<br \/>\n3. Pay attention to walls<br \/>\n4. Avoid windows<br \/>\n5. Use landscaping for protection<br \/>\n6. Keep a 100-foot buffer zone around the site<br \/>\n7. Use retractable crash barriers at vehicle entry points<br \/>\n8. Plan for bomb detection<br \/>\n9. Limit entry points<br \/>\n10. Make fire doors exit only<br \/>\n11. Use plenty of cameras<br \/>\n12. Protect the building&#8217;s machinery<br \/>\n13. Plan for secure air handling<br \/>\n14. Ensure nothing can hide in the walls and ceilings<br \/>\n15. Use two-factor authentication<br \/>\n16. Harden the core with security layers<br \/>\n17. Watch the exits too.<br \/>\n18. Prohibit food in the computer rooms<br \/>\n19. Install visitor rest rooms<\/p>\n<p>http:\/\/www.csoonline.com\/read\/110105\/datacenter.html<\/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-119","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\/119","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=119"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/119\/revisions"}],"predecessor-version":[{"id":2606,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/119\/revisions\/2606"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=119"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=119"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=119"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}