Campus jueves


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Slide 1:Hello, my name is ________________ and I am ___________________ for HP Networking’s security business unit. And today I’d like to talk to you about HP TippingPoint’s new Virtual Controller plus Virtual Firewall and our Virtual Management Center.  
  • Slide 2:Specifically, I’ll go through:The Data Center Virtualization Trends that we seeChallenges enterprise organization face due to VirtualizationPresent HP TippingPoint’s Secure Virtualization Framework, andOur new Virtual Controller plus Virtual Firewall, and Virtual Management Center products
  • Slide 3:So first let’s look at today’s data center virtualization trends.  
  • Slide 4:First let’s look at the increased IT focus on data center virtualization. Gartner conducted a CIO survey in early 2010 and found that the #1 technology priority for CIO’s is data center virtualization. This is a huge change given that virtualization wasn’t even on the list 2 years previously and it has displaced business intelligence which held the top spot for the last 5 years. But, it’s not just security of virtualization CIO’s are concerned about. They are interested in the business benefits of virtualization, ensuring their existing processes and procedures work with a virtualized environment, ensuing they are properly securing these virtual environments, and that they are maintaining the necessary separation of duties within IT. Second, in late 2009 Gartner estimated that 50% of enterprise workloads would be running on virtualized infrastructure by the end of 2012. This is again a huge increase from the 16% that were running on virtualized infrastructure at the beginning of 2010.  
  • Slide 5:Next, let’s look how enterprise data centers are changing. In the past enterprises built out data centers in an effort to connect everyone in the organization to the applications and data they required. But in most companies the result was a dispersed data center infrastructure. Now the need to reduce costs and improve data center efficiency is driving a physical consolidation of the data center. Companies are simply trying to do more with less. And tools like virtualization software, and higher density blade servers are helping to drive this consolidation. All of this is resulting in higher bandwidth in these data centers. [Build 1]In addition, new applications, new protocols and new traffic types are all appearing in the data center. An increase in web applications, voice and video traffic and even IPv6 protocols are changing the data center environment from a security perspective. [Build 2]Finally, the threat landscape outside the data center is changing. Threats are now more sophisticated, targeted and mostly financially motivated. And because of this companies no longer rely on a single security perimeter around the enterprise network. Companies are now building separate security perimeters around individual assets in the network like the data center. This is a trend often referred to as Re-Perimeterization.  
  • Slide 6:Now let’s look at what it takes to actually secure the data center and protect the entire Attack Surface of the data center. There are several components in today’s data center attack surface, each of which has vulnerabilities that we must protect.We have to prevent attacks on Network Device vulnerabilities,Vulnerabilities in Operating Systems running within the data center,Vulnerabilities in Enterprise Applications running within the data center, andEven vulnerabilities in Web Applications running within the data center. Fortunately, this is exactly what the Intrusion Prevention System or IPS is designed to accomplish. [Build 1]In fact, most people don’t even realize that that the HP TippingPoint IPS can be used to protect Web Application Vulnerabilities. [Build 2]Finally, when combined with vulnerability scanners, customers can scan the entire data center attack surface, identify all of the vulnerabilities that exist, and then ensure that the IPS protection profiles are configured to protect those vulnerabilities. So at the end of the day, the IPS is the best way to protect the entire data center attack surface.  
  • Slide 7:Now let’s look at the security challenges posed by the implementation of virtualization in the data center.  
  • Slide 8:There are several areas that security professionals are concerned about when it comes to securing the data center and specifically virtualized data center infrastructure. First is the introduction of the Hypervisor into the data center. The hypervisor becomes a mission critical component in the data center and is now also a new part of the data center attack surface that we must protect. Second companies need to be able to inspect traffic moving between one physical host and another to prevent one compromised host from attacking another. Third, we must also be able to inspect traffic moving from one Virtual Machine or VM to another VM, even if the VMs are on the same virtualized host. And fourth, virtualization makes it very easy for a VM and its applications to move from one physical host to another, to another within the data center. So we have to ensure that the security posture for that VM stays the same no matter where the VM moves within the data center.  
  • Slide 9:Now let’s look at the HP TippingPoint Secure Virtualization Framework and how we address these virtualization challenges.  
  • Slide 10:HP TippingPoint introduced the Secure Virtualization Framework in the spring of 2010. It is a combination of products designed to secure the entire data center including virtualized data center infrastructure, and it consists of 3 different products:The physical IPS Platform shown here hung off the Core SwitchThe Virtual Controller plus Virtual Firewall or vController+vFW, shown here installed on a virtualized hostAnd the Virtual Management Center or VMC shown here installed on a virtualized host on the management network The one point I want to make about the Secure Virtualization Framework, and I will emphasize this point in several places during this presentation, it that it is all about giving our customers a “Single Security Model for Securing Both the Physical and Virtualized Data Center”. So let’s now look at the Secure Virtualization Framework in more detail.
  • Slide 11:So the first thing we do is install the HP TippingPoint IPS at the perimeter of the data center as shown here. Not the perimeter of the network, but at the perimeter of the data center, isolating the data center from the rest of the network and the outside world. What we’re showing here is the IPS installed at the perimeter of a simple data center with both physical hosts and virtualized hosts, a top of rack switch and a core switch, which could also be a distribution switch. This gives us the ability to inspect all traffic moving into and out of the data center effectively segmenting the data center for the rest of the network. This is also where we protect the entire Data Center Attack Surface that we discussed earlier from outside attacks including attacks on vulnerabilities in the virtualization software or hypervisor and even virtual desktop infrastructure. This is also where our Virtual Patching concept comes in. HP TippingPoint has always been focused on providing vulnerability filters in our IPS to prevent attacks on entire vulnerabilities as opposed to individual exploits, and so once you enable our vulnerability filters on the IPS it is like having all of the systems in the data center fully patched against the latest vulnerabilities or in essence having a “Virtual Patch” in place. In fact, in many cases we have protection for undisclosed vulnerabilities well before the software vendor discloses the vulnerability or makes a patch available to the public. So with this step we have a single set of security polices at the perimeter protecting both the physical and virtual data center assets.  
  • Slide 12:Next we need to visualize or discover the entire virtualized infrastructure and deploy the vController+vFW on each of the discovered virtualized hosts. [Build 1]The first step is the simple installation of the Virtual Management Center or vMC on a stand-alone server or virtual machine. In fact, it can be installed in a VM on the same server hosting VMware’s vCenter. Once vMC is installed on the Management Network it communicates with the VMware vCenter which is the VMware management console. [Build 2]At that point the vMC is able to auto-discover the entire virtualized data center including providing real-time visibility of every virtualized host, and every virtual machine on each host. In addition, it provides a logical overview of the network topology showing how all of the virtual machines are interconnected in the data center. This allows customers to get their hands around the entire virtual data center so they can easily start to visualize and control VM sprawl and can identify mis-configurations in the virtual network as well. [Build 3]Once vMC identifies all of the virtualized hosts, it can be used to auto-deploy a vController+vFW installation on each of the virtualized hosts. There is a single instance of vController installed on each virtualized host regardless of how many virtual machines are running on each host.
  • Slide 13:Now at this point we have all the pieces of the Secure Virtualization Framework in place. In the graphic here on the right, you can see the physical IPS installed at the perimeter, the vMC installed on the management network, and the vController+vFW installed in the Service VM on this exploded view of one of the virtualized hosts in the data center. Again, there is only a single installation of vController+vFW on each virtualized host. It is installed in the Service VM and plugs into the VMware hypervisor via the VMware VMsafe API. Once in place the vController+vFW essentially introduces a “firewall like policy ” into the hypervisor. Basically, vController+vFW can see all traffic coming from any of the application VMs on the virtualized host and allows us to apply a policy that allows us to do 3 things:First, is the traffic permitted or not? If it is allowed the traffic is allowed to pass.Second, if the traffic is not allowed, we can block it outright at the hypervisor level with the vFW capability.And third, if the traffic is permitted, should it be inspected? If we want to inspect the traffic, the vController redirects the traffic via a dedicated VLAN to the physical IPS for inspection. The IPS inspects the traffic, blocks any malicious content, and then passes the inspected traffic back to the vController via a dedicated VLAN where vController then directs the traffic to its original destination. So now we can completely enforce our security policies in the both the physical and virtual data center. This includes the ability to inspect:Traffic coming into and going out of the data center at the perimeter,Traffic between physical hosts in the data center,Traffic between physical host and VMs, and evenTraffic between two VMs on the same virtualized host. And because every vController+vFW in the data center has all of our security redirection policies, we have the same security posture in place for each VM or application no matter where it moves in the data center. We now have a single set of security policies and for the entire data center including the ability to enforce those policies in both the physical and virtual data center. 
  • Slide 14:The components of our Secure Virtualization Framework are VMware certified per the VMware Ready program. First, the vController+vFW is fully integrated with the VMware hypervisor via the VMsafe API.Second, the vMC is fully integrated with the VMware management console vCenter. I should however mention that currently our solution is only compatible with the VMware virtualization solution, and not with Microsoft’s Hyper-V or with Citrix solutions.
  • Slide 15:So in conclusion, the Secure Virtualization Framework gives us the ability to deliver a single security model for the physical and virtual data center. We can use our physical IPS Platform to segment different physical trust zones in the network. For example, companies may want to require inspection for all traffic between their R&D applications and their Finance applications. This is easily accomplished by routing the traffic through the physical IPS Platform. But now, we can enforce the same security policies in the virtualized data center. We can completely segment or enforce inspection between the R&D applications and Finance applications even when those applications are running on VMs on the same virtualized host. 
  • Slide 16:Thank you for your time today. May I answer any questions you have?  
  • Campus jueves

    1. 1. Alvaro Ferro<br />CCSP – CISSP – CCIE Security Written<br />30de Junio.<br />SECURITY IN THE DATACENTER<br />
    2. 2. Data Center Virtualization Trends<br />Security in virtual environment<br />Challenges due to Virtualization<br />Secure Virtualization Framework<br />Virtual Controller and Virtual Management Center<br />Agenda<br />30 June 2011<br />2<br />
    3. 3. Data Center Virtualization Trends<br />vController+vFW and vMC<br />
    4. 4. #1 Technology Priority in 2010<br />Survey of 1,586 CIOs<br />Displaces Business Intelligence which held top position for the last 5 years!<br />Source: Gartner EXP, Jan 2010<br />2010 – virtualization reaches a tipping point<br />Increased Data Center Security Focus<br />50% of Workloads by 2012<br /><ul><li>Today 16% of workloads are running in virtual machines
    5. 5. Source: Gartner, Oct 2009</li></ul>50%<br />~ 58 million deployed x86 machines<br />16%<br />2010<br />2011<br />2012<br />30 June 2011<br />4<br />
    6. 6. Do more with less<br />Connect everyone to everything<br />Present & Future<br />Past<br />Efficiency Drives<br />Consolidation<br />Virtualization, Blades,<br />Increased Bandwidth<br />Dispersed, Physical <br />New Apps,<br />Protocols & Traffic<br />Legacy + Web, IPv4 + IPv6, Data + Voice + Video<br />Legacy, Client Server,<br />IPv4, Data<br />Data Center Trends<br />Threat Landscape<br />Change<br />Sophisticated Targeted Attacks, Re-Perimeterization<br />Worms, Viruses,<br />Trojans, DDoS<br />30 June 2011<br />5<br />
    7. 7. Securing the Data Center Attack Surface<br />Data at Rest<br />Attack Surface<br />Attack Traffic<br />Web Apps<br />Vulnerability Scanning<br />Protects<br />Web App Vulnerabilities<br />Enterprise<br />Apps<br />IPS Platform<br />Operating Systems<br />Network <br />Devices<br />30 June 2011<br />6<br />
    8. 8. Security in virtual environment<br />30 June 2011<br />7<br />
    9. 9. ENTENDAMOS LO SIGUIENTE<br />“40% de los proyectos de implementación de ambientes virtualizados se llevaron a cabo sin la participación del equipo de seguridad en la arquitectura inicial y las etapas de planificación ”<br />Riesgos mas comunes en proyectos de Virtualización<br />La falta de visibilidad y controles en la comunicación entre VM-a-VM. <br />Perdida potencial en la separación de deberes (SOD) entre las áreas de redes y seguridad cuando se virtualiza. <br />Cargas de trabajo se consolidan en un servidor físico.<br />Controles de acceso administrativo (Hypervisor/VMM).<br />Source: MacDonald, Neal. Addressing the Most Common Security Risks in Data Center Virtualization Projects, Gartner, Inc. January 25, 2010<br />
    10. 10. <ul><li>Hyper-jacking</li></ul>Son ataques de rootkit diseñados para tomar el control de las máquinas virtuales mientras están en funcionamiento.<br /><ul><li>VM Escape </li></ul>Es un exploit que permite moverse dentro de una máquina virtual.<br /><ul><li>VM Hopping</li></ul>Cuando una máquina virtual es capaz de acceder a otra máquina virtual.<br /><ul><li>VM Theft</li></ul>Acceso no autorizado para la adquisición de algún archivo que contiene el VM<br /><ul><li>VM Sprawl</li></ul>Proliferación de cargas de trabajo de los servidores virtualizados<br />AMENAZAS: SEGURIDAD DE LA VIRTUALIZACIÓN<br />Todas son posibilidades reales pero hay realidades prácticas!<br />
    11. 11. CARACTERÍSTICAS: DEFENSA POR CAPAS<br /><ul><li>Implemente inspección y bloqueo de amenazas “in-line” contra ataques dirigidos “hypervisor”
    12. 12. Utilice programas de protección para Zeroday
    13. 13. Convergencia en soluciones IPS (virtual & physical) para la segmentación de zonas de confianzas</li></ul>Core<br />Virtualized Server<br />VM<br />VM<br />VM<br />Secure Network Fabric Switch<br />App<br />App<br />App<br />OS<br />OS<br />OS<br />vNICs<br />vNICs<br />vNICs<br />vSwitch<br />Hypervisor<br />pNICs<br />Virtualized Servers<br />Physical Servers<br />
    14. 14. HP Secure®Virtualization Framework<br /><ul><li>Que incluye
    15. 15. Plataforma IPS con VLAN translation
    16. 16. Virtual Controller (vController)
    17. 17. Virtual IPS (vIPS)
    18. 18. SMS / VMC</li></ul>TippingPontvIPS<br /><ul><li>Beneficios
    19. 19. Active la amenaza de bloqueo-para el centro de datos virtual
    20. 20. Coherente política de seguridad & cumplimiento-entre el centro de datos virtuales y físicos
    21. 21. Full aislamiento de seguridad VM- desde maquinas virtuales y hosts
    22. 22. Visibilidad y control</li></ul>- integración VMC<br /><ul><li>Protección y rendimiento optimizado con VmSafe-con opciones para la inspección
    23. 23. Seguridad para VMs (Móvil)- seguridad sigue VMs
    24. 24. Cobertura de amenazas de DVLabs– la mejor cobertura disponible</li></ul>TIPPINGPOINT vCONTROLLER<br />
    25. 25. Operacion: Vcontroller<br />
    26. 26. Operacion: Vcontroller<br />Operacion: Vcontroller<br />
    27. 27. Challenges Due to Virtualization<br />vController+vFW and vMC<br />
    28. 28. Core Switch<br />Hypervisor Security<br /><ul><li>Mission critical
    29. 29. Can’t be secured with virtual IPS
    30. 30. Patches must be immediate</li></ul>Host to Host Threats<br /><ul><li>Can’t deploy IPS in front of every server
    31. 31. Also need VM to Host security</li></ul>VM to VM Threats<br /><ul><li>Virtual trust zones
    32. 32. Traffic does not enter the physical network for inspection
    33. 33. A victim VM can attack other VMs</li></ul>VM Mobility<br /><ul><li>vMotion launches VMs in separate sites for DR or other purposes
    34. 34. Physical IPS options are cost prohibitive for these uses</li></ul>1<br />IPS Platform<br />2<br />Top of Rack Switch<br />3<br />2<br />Virtualized Host<br />Virtualized Host<br />Virtualized Host<br />3<br />4<br />1<br />VM<br />VM<br />VM<br />VM<br />VM<br />VM<br />OS<br />OS<br />OS<br />OS<br />OS<br />OS<br />App<br />App<br />App<br />App<br />App<br />App<br />VMs moved to separate site<br />4<br />The Virtual Network Visibility Gap<br />30 June 2011<br />15<br />
    35. 35. Secure Virtualization Framework, VController and vMC<br />vController+vFW and vMC<br />
    36. 36. VMC<br />Core Switch<br />What’s Included<br /><ul><li>IPS Platform
    37. 37. Virtual Controller + Virtual Firewall (vController+vFW)
    38. 38. SMS / Virtual Management Center (vMC)</li></ul>Securing Virtualization DC security solution<br /><ul><li>Single, purpose-built DC security solution</li></ul>Extend IPS solution into the virtual DC<br /><ul><li>Leverage previous IPS investments</li></ul>Flexibly Inspect Data in Both the Physical and Virtual DC<br />TippingPoint IPS<br />VMware vCenter<br />Management Network<br />Top of Rack Switch<br />Virtualized Host<br />Hypervisor<br />vSwitch<br />VMsafe Kernel Module<br />Redirect Policy<br />vController<br />+ vFW<br />OS<br />OS<br />OS<br />OS<br />App<br />App<br />App<br />App<br />Application VMs<br />Service VM<br />Secure Virtualization Framework (SVF)<br />30 June 2011<br />17<br />
    39. 39. Core Switch<br />Start with DC Perimeter Protection<br /><ul><li>Inspect ingress / egress traffic</li></ul>Protect DC Attack Surface<br /><ul><li>Virtualization tools / hypervisor
    40. 40. Network infrastructure
    41. 41. Host servers and operating systems
    42. 42. Enterprise and Web applications
    43. 43. Virtual desktop infrastructure (VDI)</li></ul>Virtual Patching<br /><ul><li>Protects rolled-back VMs
    44. 44. Protects VMs with out-of-date patching due to server/VM shut-downs</li></ul>Single Set of Security Policies across Physical and Virtual DC<br />TippingPoint IPS<br />Top of Rack Switch<br />Virtualized Hosts<br />Physical Hosts<br />Protect the High Value Data Center<br />30 June 2011<br />18<br />
    45. 45. VMC<br />Core Switch<br />Visualize the DC and Deploy VController<br />Simple VMC Installation<br /><ul><li>VMware vCenter integration</li></ul>TippingPoint IPS<br />VMware vCenter<br />VMC Auto-Discovery of Virtualized Hosts and VMs<br /><ul><li>Real time visibility of virtual DC
    46. 46. Topology mapping of network paths</li></ul>Management Network<br />Top of Rack Switch<br />VMC Auto-Deployment of vControllers to Virtualized Hosts<br /><ul><li>User initiated, auto-deployment</li></ul>Control VM Sprawl<br />Virtualized Hosts<br />Physical Hosts<br />30 June 2011<br />19<br />
    47. 47. VMC<br />Core Switch<br />TippingPoint IPS<br />Enforce Security Policies<br /><ul><li>Incoming DC traffic
    48. 48. Outgoing DC traffic
    49. 49. Physical host to physical host traffic
    50. 50. Physical host to VM traffic
    51. 51. VM to VM traffic</li></ul>Security Policies Follow VMs<br /><ul><li>Policies apply to mobile VMs</li></ul>Default Security Policies<br /><ul><li>Apply to all new VMs or copied VMs
    52. 52. Untrusted VMs or zones</li></ul>Single Set of Security Policies for Entire DC Protection<br />VMware vCenter<br />Management Network<br />Top of Rack Switch<br />Virtualized Host<br />Hypervisor<br />vSwitch<br />VMsafe Kernel Module<br />Redirect Policy<br />vController<br />+ vFW<br />OS<br />OS<br />OS<br />OS<br />App<br />App<br />App<br />App<br />Application VMs<br />Service VM<br />Apply Security Policies Between DC Trust Zones<br />30 June 2011<br />20<br />
    53. 53. VMware VMSafe Hypervisor Integration<br />vController is fully integrated with VMware vSphere using the VMSafe API<br />VMware vCenter Integration<br />VMC is fully integrated with VMware’s vCenter management console<br />Member of VMware Global Technology Alliance Partner (TAP) Program<br />Certified per “VMware Ready” Program<br />Supports VmwarevShere 4 (ESX / ESXi4)<br />VmWARE Ready<br />30 June 2011<br />21<br />
    54. 54. N-Platform IPS<br />Top of Rack Switch<br />Physical Finance Servers<br />Physical R&D Servers<br />Distributed vSwitch<br />vController+vFW<br />vController+vFW<br />vController+vFW<br />Finance Zone<br />DMZ Zone<br />R&D Zone<br />OS<br />OS<br />OS<br />OS<br />OS<br />OS<br />OS<br />OS<br />OS<br />OS<br />OS<br />OS<br />App<br />App<br />App<br />App<br />App<br />App<br />App<br />App<br />App<br />App<br />App<br />App<br />Virtualized Servers Cluster<br />Single security model for the physical AND virtual data center<br />Data Center Security<br />30 June 2011<br />22<br />
    55. 55. Q&A<br />
    56. 56. Outcomes that matter.<br />