Learn How to Secure and Audit AWS at AWS re:Invent 2016
AWS re:Invent 2016 will take place next week, November 28–December 2, 2016, in Las Vegas, Nevada. Designed to give you increased opportunities to connect, collaborate and learn about AWS solutions, this year’s event will also include sessions and vendors on the exhibit floor focused on AWS security. To get you started, we’ve compiled a few resources that will help you learn how to decrease audit times, improve AWS security and show why IP addresses and VPNs don’t work. Don’t have time before the event? Connect with us there and find out more!
AWS Access & Compliance Control – Remove Complexity, Scale Security
Securing access to enterprise systems on AWS – and proving that systems are only accessed by authorized users – is a top concern. Cryptzone will be on hand at booth number 1918 to show you an easier way to secure and audit AWS user access:
- Automate tightly controlled user-access in highly dynamic cloud environments.
- Comply with system access policies knowing exactly who accessed which resources, from where, and when – in near real-time – saving your teams thousands of hours of audit prep work.
When we talk to customers about their greatest concerns about moving workloads to the cloud, inevitably one of the top barriers is compliance-related activities. They feel they have an understanding of the technology, how it works and how it will be implemented. But they still have concerns about how they will deal with audit / regulatory compliance issues. In addition, companies are always looking for ways to decrease the time and complexity of their audits. Read more.
AWS offers many benefits and as it continues to lead the IaaS pack, security professionals must look to secure it in the same way they secure internal networks. Because employees access AWS from anywhere or contractors use it from various locations, it becomes a possible hole in your network. And where there is a hole, there is a hacker.
Yet public cloud security is a shared responsibility. AWS takes responsibility for security ‘of’ the cloud, but puts the onus on the customer for security ‘in’ the cloud. Those adopting AWS need to reconcile tightly controlled access with wide open access. Read more.
It’s no secret that companies worldwide are embracing rapid application delivery and DevOps in the cloud. However, in AWS, security is a shared responsibility. Before building new apps, companies need to securely connect their developers. The simplest way to do this is to allow the entire IP range of the internal corporate network to access all workloads running on AWS. But of course, organizations want to apply some level of access control. Read more.
Everyone using Amazon Web Services (AWS) quickly becomes familiar with the Shared Responsibility model for security. This is a necessary, and well-thought-out part of the AWS design, clearly delineating what customers and AWS are responsible for from a security perspective.
While some of these aspects are very straightforward to integrate into an enterprise’s standard tools and processes – like OS patching – others, in particular network security, are not so simple. Read more.
Want more? Watch the webinar on simplifying, securing and scaling user access.