![\"\"](\"https:\/\/www.paloaltonetworks.com\/blog\/wp-content\/uploads\/2012\/02\/DC2-230x140.jpg\" "\\"DC\\"")
<\/p>\nI feel sorry for security IT admins these days. The enterprise network used to be relatively easy to protect; crunchy on the outside, chewy and soft in the middle. Protect the perimeters, and you were safe. Now that boundaries have disappeared, threats have evolved, and BYOD (Bring Your Own Device) has become a reality, where should enterprises focus their security efforts?<\/p>\n
I say the data center. Of course I subscribe to the notion of defense-in-depth, but if there is one place security should never be neglected, it\u2019s where all your important servers and data reside.<\/p>\n
In principle, data center security is pretty straightforward. It\u2019s ensuring secure application access by authorized users to approved applications. You have to do that while preventing threats and complying with regulatory requirements. Of course, you must also ensure that you do not impact performance or productivity; more on that later. I want to go back to the secure application enablement challenge.<\/p>\n
Ensuring secure application access by authorized users to approved applications should be simple right? After all, you know what applications are running in your data center, and you know who your users are. Well, in theory you do, but your enterprise is probably made up of geeky application developers who are not only supporting off-the-shelf enterprise applications, but also developing home-grown custom apps that are using a variety of different ports. You\u2019re either opening every port on your legacy firewall, or incurring the wrath of your app developers by taking too long to enable the right policy on the right firewall, the right VLAN, the right access.<\/p>\n
<\/p>\n
How many data center legacy firewall ACLs are modified every day just to keep up with application adds, moves and changes? How long does it typically take to enable an application? And what about the \u201cuser\u201d aspect of secure application enablement. Remember the X-Files mantra, \u201cTrust No One<\/strong>\u201d?<\/p>\n Forrester Research's\u00a0Zero Trust Model<\/a> advocates that we apply it to networks today. Not \u201cTrust but verify\u201d, but \u201cDo not trust, always verify<\/em>\u201d. This means you need to identify users or groups of users accessing applications. Based on the usage of the applications, you also need to segment parts of the data center to reduce the scope of vulnerability (i.e. the development apps should be separate from the production apps; the PCI servers should be segmented from the rest of the network and accessible only to the finance users).<\/p>\n Let\u2019s add more complexities to the DC security problem. As I indicated earlier, the first mission of the data<\/p>\n center is to serve applications. \u00a0Any network security infrastructure that interferes with this primary mission cannot be placed in the data center. Network security infrastructure should be flexible enough to accommodate high-performance AND security. \u00a0It should also be flexible enough to accommodate changes in the nature of network security controls or policy (for example, adding content scanning or threat prevention), without having to add more devices, or re-design the network. It should be<\/p>\n flexible enough to integrate with the networking infrastructure, no matter what types of design (traditional data centers, next-generation Ethernet fabric designs, virtualized data center).<\/p>\n Phew, so what have we got now? A long long list of data center security requirements. How do we address this at Palo Alto Networks? I invite you to attend one of our worldwide Data Center Summits<\/a><\/strong>. We are kicking off this multi-city tour in Dallas, Texas on Feb 21st<\/sup>.<\/p>\n We have an excellent agenda planned. This data center tour is an all-day exploration of data center security designs and considerations with Forrester Research (for North America venues) and IDC (for Europe and Asia venues), and our data center partner Brocade. We\u2019ll provide details of how we align with Forrester\u2019s Zero Trust Model and<\/p>\n deliver data center security with no compromises. Additionally, we will show how Palo Alto Networks\u2019 next-generation firewalls integrate into next-generation data centers powered by Brocade VCS Fabric Technology. This promises to be an interesting seminar. Don\u2019t forget to register<\/a> soon, spots are filling up. I hope to see you there!<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" I feel sorry for security IT admins these days. The enterprise network used to be relatively easy to protect; crunchy on the outside, chewy and soft in the middle. Protect the perimeters, …<\/p>\n","protected":false},"author":40,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[75],"tags":[71,12,72,73],"coauthors":[771],"class_list":["post-1986","post","type-post","status-publish","format-standard","hentry","category-data-center-2","tag-application-visibility","tag-data-center","tag-data-center-summit","tag-zero-trust"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/posts\/1986","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/users\/40"}],"replies":[{"embeddable":true,"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/comments?post=1986"}],"version-history":[{"count":50,"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/posts\/1986\/revisions"}],"predecessor-version":[{"id":4004,"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/posts\/1986\/revisions\/4004"}],"wp:attachment":[{"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/media?parent=1986"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/categories?post=1986"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/tags?post=1986"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/coauthors?post=1986"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"\"](\"https:\/\/www.paloaltonetworks.com\/blog\/\/wp-content\/uploads\/2012\/02\/DCinvite.jpg\" "\\"DCinvite\\"")
<\/span><\/div><\/a><\/p>\n