{"id":4942,"date":"2016-11-08T09:39:48","date_gmt":"2016-11-08T15:39:48","guid":{"rendered":"https:\/\/www.poweradmin.com\/blog\/?p=4942"},"modified":"2016-11-01T16:43:59","modified_gmt":"2016-11-01T21:43:59","slug":"micro-segmentation-best-practices","status":"publish","type":"post","link":"https:\/\/www.poweradmin.com\/blog\/micro-segmentation-best-practices\/","title":{"rendered":"Micro-Segmentation Best Practices"},"content":{"rendered":"

\"virtual<\/a>With the growth of software-defined networking (SDN) and the evolution of software-defined data center (SDDC) technologies, network administrators, data center operators and security officers are increasingly looking to micro-segmentation, for enhanced and more flexible network security.<\/span><\/p>\n

\u00a0<\/p>\n

In this article, we\u2019ll be considering the nature and characteristics of the process, and looking at ways to effectively plan, implement, and manage network micro-segmentation deployments.<\/span><\/p>\n

What Is Micro-Segmentation?<\/span><\/h2>\n

To assist in administration, security enforcement and the management of data collision domains, network segmentation or the division of a network into smaller sub-sections allows administrators to minimize the access privileges granted to people, applications and servers, and the rationing of access to sensitive or mission-critical information on an \u201cas-needed\u201d basis.<\/span><\/p>\n

\u00a0<\/p>\n

In its traditional form, network segmentation is achieved by creating a set of rules to govern communication paths, then configuring firewalls and VLANs to provide the means to partition the network into smaller zones. For comprehensive security coverage, a network should be split into multiple zones, each with their own security requirements \u2013 and there should be a strict policy in place to restrict what\u2019s allowed to move from one zone to another.<\/span><\/p>\n

\u00a0<\/p>\n

It\u2019s a physical process that can soon reach the limits of its effectiveness, once traditional or even next-generation firewalls become overloaded and the burden on IT staff of manually fine-tuning configurations and policies becomes too great as networks expand beyond a certain size or are simply overwhelmed by changing conditions.<\/span><\/p>\n

\u00a0<\/p>\n

Micro-segmentation takes network partitioning to the next level, by exploiting virtualization and software-defined network technologies to allow policy-based security to be assigned to the network at a granular level \u2013 with security assignments possible down to individual workloads.<\/span><\/p>\n

\u00a0<\/p>\n

Benefits And Drawbacks<\/span><\/h2>\n

For micro-segmentation, hardware-based firewalls aren\u2019t required to enable security to be directly integrated with virtualized workloads. So security policies may be synchronized with virtual machines (VMs), virtual networks, operating systems, or other virtual security assets, with security assignments down to the level of a single workload or network interface. And if a network is reconfigured or migrated, VMs and workloads will move together with their associated security policies.<\/span><\/p>\n

\u00a0<\/p>\n

By enabling such fine-grained security controls, micro-segmentation can drastically reduce the available attack surface that a network presents. It enables more granular control over the traditional \u201cchoke points\u201d of a network, and allows for security controls which are customized for each virtual environment.<\/span><\/p>\n

\u00a0<\/p>\n

Should an attack occur, the effective separation of each zone into its own secured environment helps limit the spread of incursion and any sideways spread into the rest of the network. Micro-segmentation can also simplify and speed up incident responses, and enhance forensics in the event of a security breach or other network event.<\/span><\/p>\n

\u00a0<\/p>\n

On the downside, micro-segmentation can be a complex process requiring detailed design and careful administration. The increased overhead in areas like system monitoring and alerts or identity management may translate into increased financial and staffing costs for the enterprise \u2013 unless the deployment is properly planned and executed. The following recommendations should help.<\/span><\/p>\n

Start With Analytics<\/span><\/h2>\n

Mapping a network\u2019s security requirements down to its lowest level requires a detailed knowledge of its inner workings \u2013 a fine-grained and 360-degree view of the network<\/a> which goes beyond what manual observation can achieve. Visibility must be gained into communication patterns and network traffic flows to, from, and within the enterprise campus, and software analytics should be employed to establish key relationships and traffic patterns (groups of related workloads, critical applications, shared services, etc.)<\/span><\/p>\n

\u00a0<\/p>\n

The policies and security rules to be used under micro-segmentation will also be determined by the results of network analytics. Models should be drawn up and assessed to highlight important relationships, and to help spot network elements and workloads that may potentially pose problems. Analytical results will also assist in crafting policy definitions and the orchestration system needed for pushing micro-segmentation out to all the infrastructure on the network.<\/span><\/p>\n

Adopt A Zero Trust Attitude<\/span><\/h2>\n

Denial of access should be the default philosophy, with communications on the network selectively allowed on the basis of the previous analysis. Throughout the micro-segmentation deployment, \u201czero trust zones\u201d should be created, with policies and rules set to allow only that access to users, systems, and processes that they essentially need to do their jobs.<\/span><\/p>\n

\u00a0<\/p>\n

Whitelisting may be of value here, as network analytics should reveal what are known to be safe communication paths. Everything else can be blocked.<\/span><\/p>\n

Choose Your Tools Wisely<\/span><\/h2>\n

Software-defined networking technologies may facilitate the enhancement of legacy infrastructure and security protections for micro-segmentation \u2013 but this will depend on a careful selection of hypervisor and tools for virtualization. This would typically include a single tool or platform for visualizing the interactions occurring between the physical and software-defined layers of the network. Tools should also be integrated and user-friendly for all the personnel involved \u2013 be they assigned to operations, networking, cloud, storage, administration, or security.<\/span><\/p>\n

\u00a0<\/p>\n

Look for features like automated provisioning and move\/change\/add for workloads, scale-out performance for firewalling, and distributed enforcement in-kernel and at each virtual interface.<\/span><\/p>\n

Consider The Cloud<\/span><\/h2>\n

Cloud-based technologies<\/a> can relieve much of the burden of a micro-segmentation deployment. Network traffic analytics tools may be employed at the design stage to help trace critical communication paths and inter-relationships, and to throw up potential network security and micro-segmentation weaknesses, based on known best practice configurations.<\/span><\/p>\n

\u00a0<\/p>\n

Deep insights into network operations may be obtained without the need for investing in on-premises hardware and software. And web-based administration platforms may be used to manage and orchestrate the dispersal of micro-segmentation policies across the entire network.<\/span><\/p>\n

Create Best Practice Zones For Compliance<\/span><\/h2>\n

Compliance regimes such as PCI-DSS<\/a> give guidelines for the clear separation of data within a network \u2013 and micro-segmentation is ideally suited to ensuring this. For instance, it\u2019s easy to create zones where confidential information like financial records or credit card data are isolated from the less sensitive data moving through the rest of the network.<\/span><\/p>\n

\u00a0<\/p>\n

For audit purposes, micro-segmentation may be employed to create \u201cbest practice zones\u201d on the network, while any issues thrown up may be quickly addressed without the need for downtime, reconfiguration across the network, or buying new hardware.<\/span><\/p>\n

Some General Tips<\/span><\/h2>\n

\u00b7 Route network traffic patterns<\/a> to force specific flows with greater numbers of check-points.<\/span><\/p>\n

\u00a0<\/p>\n

\u00b7 Deploy security controls at multiple layers of the network architecture to make it harder for intruders to gain access to sensitive data \u2013 but balance the number of controls to keep complexity down to manageable levels.<\/span><\/p>\n

\u00a0<\/p>\n

\u00b7 Set up different zones as determined by where sensitive information lies.<\/span><\/p>\n

\u00a0<\/p>\n

\u00b7 Use a whitelist approach to determine where secure communication channels exist, and block access to all other areas.<\/span><\/p>\n

\u00a0<\/p>\n

\u00b7 Step back from time to time to see the big picture: Areas where restrictions may be too severe, or zones where access is being given unnecessarily.<\/span><\/p>\n

Repeat And Fine-Tune<\/span><\/h2>\n

As conditions change, you\u2019ll need to revisit your micro-segmentation design stages. So continue analyzing<\/a> network traffic, and using the results to distill and fine-tune your security policies and rules.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

With the growth of software-defined networking (SDN) and the evolution of software-defined data center (SDDC) technologies, network administrators, data center operators and security officers are increasingly looking to micro-segmentation, for enhanced and more flexible network security. \u00a0 In this article, we\u2019ll be considering the nature and characteristics of the process, and looking at ways to […]<\/p>\n","protected":false},"author":10,"featured_media":4944,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-4942","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-general-it"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/posts\/4942","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/comments?post=4942"}],"version-history":[{"count":3,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/posts\/4942\/revisions"}],"predecessor-version":[{"id":4946,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/posts\/4942\/revisions\/4946"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/media\/4944"}],"wp:attachment":[{"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/media?parent=4942"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/categories?post=4942"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/tags?post=4942"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}