Friday, May 29, 2015

Protect Your Net: Shared Security Responsibility in the Cloud

It’s no secret why businesses small and large continue to move workloads to the cloud. The agility and flexibility it provides, combined with the ability to focus on their business versus running a data center means companies are now asking, “what can’t I move to the cloud” versus, “what can I?”

And now that you’re moving to the cloud – leveraging the secure cloud offerings from AWS or Azure and others – it’s imperative to understand how the security model changes.

Much like soccer, cloud security is a team sport. In soccer, each player on the team has her role, and in cloud security, you and your cloud provider each have specific security responsibilities.

Specifically, your cloud service provider, such as AWS or Microsoft Azure, is responsible for securing the cloud infrastructure up to the hypervisor layer, including:

  • Physical infrastructure
  • Network infrastructure
  • Virtualization layer

 

While you, as the user of the cloud service, are responsible for securing everything you put in the cloud, including:

  • Applications
  • Data
  • Operating systems/ platform

 

But how do you approach security now that you’re in the open field of the cloud, without physical perimeters on which to put your controls?

Trend Micro Deep Security has been built from the ground up to protect cloud workloads – without getting in the way. It helps you meet most of your shared security responsibilities, including:

  • Preventing exploitation of vulnerabilities like Shellshock
  • Protecting networks from attack
  • Keeping malware off your workloads
  • Providing actionable insight into system activity
  • Augmenting AWS controls to help speed PCI-DSS compliance

 

Click here to learn more about how Deep Security can help secure your cloud environment. To dive into specific security information for the leading cloud service providers, visit:



from Trend Micro Simply Security http://ift.tt/1FRMkgn
via IFTTT

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.