IaaS platforms such as Amazon Web Services (AWS) provide an excellent layer of foundational security, but the shared responsibility model is clear: businesses are still responsible for the confidentiality, integrity, and availability of their data in the cloud. Organisations that are storing sensitive data in the cloud, which is 93 per cent according to a recent Forrester survey, need a consistent security model across on-premises and IaaS to reduce the risk of data breach.1 Yet Gartner predicts that 95 per cent of IaaS security failures will be the customer’s fault, and more than half of those will be attributed to inadequate management of identities, access and privileges.2
“Leveraging built-in IaaS security is a great start, but not a complete solution according to the AWS Shared Responsibility Model and AWS Security Best Practices,” says Bill Mann, chief product officer at Centrify. “Centrify makes it easy to securely move infrastructure and apps to AWS, and take advantage of the benefits of the cloud, by providing identity freedom, deployment freedom and a single, consistent security model across on-premises and cloud infrastructure and apps.”
Identity Freedom
As IT organisations look to migrate internal servers and applications to the public cloud, the fact that these on-premises workloads are hard-wired to on-premises infrastructure such as Active Directory (AD) can slow down the ability of IT organisations to quickly and cost-effectively move those workloads to the cloud. Customers want to avoid the costs and challenges associated with managing shared EC2 user accounts and replicating their on-premises identity infrastructure to the cloud. At the same time, IT organisations may still want to leverage their historic investment in Active Directory while maintaining uniform high levels of security across on-premises, private cloud, and public cloud infrastructure and applications.
Centrify’s new Identity Broker capability seamlessly connects servers deployed in the cloud to the customer’s identity provider of choice ? including Active Directory and LDAP directories— without having to replicate complex identity infrastructure in the cloud or set up site-to-site VPNs or one-way trusts and Read Only Domain Controllers (RODCs). For further identity freedom, Centrify customers can now disaggregate themselves from the use of on-premises Active Directory as the backend identity repository for server authentication and solely leverage cloud-based directories such as the Centrify Directory or Google G-Suite Directory.
This new capability extends Centrify’s robust privileged access security solution for hybrid cloud environments. Centrify’s solution simplifies and streamlines the secure adoption of IaaS, implementing and extending AWS security best practices. Centrify vaults AWS Account credentials, controls access to and role membership for the AWS console, audits all privileged activity, and secures privileged access to Amazon EC2 instances and the apps that run on them, all while enforcing Multi-Factor Authentication for identities. This complements Centrify’s single sign-on (SSO) support for thousands of cloud-based Software-as-a-Service (SaaS) applications as well as on-premise applications migrating to the public cloud via Centrify’s support for SAML ? including Centrify’s SAML Toolkit for customer-developed applications that are built in the cloud. Deployment Freedom
Centrify offers a single privileged access security solution for hybrid IT that can be deployed as a service, in a private cloud or on-premises. Deployment tools and scripts make it easy for IT admins to deploy the Centrify solution, enroll servers in the Centrify Cloud Service, vault root accounts, and automate setup of user access to servers.
AWS Security Best Practices
- Setting up a common security model. Conventional security and compliance concepts still apply in the hybrid cloud. Leverage and extend on-premises access polices to deploy infrastructure and apps quickly and securely in AWS.
- Eliminating EC2 key pairs. Minimise attack points by leveraging Active Directory, LDAP and cloud directories such as Google’s versus creating local accounts and managing EC2 key pairs for authentication.
- Ensuring Accountability. Leverage existing user accounts or federate access to services and resources in AWS. Create fine-grained permissions to resources, and apply them to users through groups or roles.
- Implementing least privilege access.Grant users just the access they need in the AWS console, on EC2 instances and to apps. Implement cross platform privilege management for AWS console, Windows and Linux.
- Auditing everything.Log and monitor both authorised and unauthorised activity in EC2 instances. Associate all activity to an individual, and report on both privileged activity and access.
- Implementing MFA everywhere.Thwart in-progress attacks in AWS. Consistently implement MFA for AWS service management, on login and privilege elevation for EC2 instances, and when accessing enterprise apps.
“Centrify is the only vendor that comprehensively addresses identity for SaaS, IaaS and on-premises with a single architecture,” added Mann.
