This is the second in a series of seven on the five pillars for well-architected AWS security. For the entire series, visit the Five pillars – AWS blog page here.
Traditionally, customers look at IAM from the standpoint of users. Users, which can be further categorized into groups, will also have associated roles, and permissions associated to these roles.
Even within similar organizations – example, a company may have multiple groups within a larger development organization, with different permissions associated both to the roles those users have and the groups to which they belong. It is not necessarily a linear relationship.
Similarly, companies in the cloud have come to understand that services can be subject to the same IAM as users. This is an important construct when organizations look to leverage cloud services for transformation – those services need to be understood in terms of how they are accessed and managed.
Within AWS, IAM will allow authorized IT administrators to take action on specific resources and provide those administrators with visibility and control across that whole infrastructure. This can quickly get complex, with hundreds of organizations, workgroups, and projects. IAM becomes the first “window” into who’s doing what.
In the AWS infrastructure, privilege management is primarily supported by the AWS Identity and Access Management (IAM) service, which allows you to control user and programmatic access to AWS services and resources. Within AWS, you should also require strong password practices, such as complexity level, avoid re-use, and enforce multi-factor authentication (MFA).
See what three things you need to develop a well-architected #IAM pillar #CloudSecurityClick To TweetTo develop a well-architected IAM pillar, customers must:
- Manage credentials and authentication
- Control human access
- Control programmatic access
To read more on AWS Well-Architected Cloud Security, visit Managing Credentials and Authentication in the AWS Well-Architected Labs documentation series.
Next week we’ll take a look at Detective Controls and how they are implemented in AWS. To follow this series in its entirety, visit the Five Pillars – AWS blog page here.
Barracuda Cloud Security Guardian has been designed from the ground up to integrate with AWS and leverage built-in security and alerting features. For a free scan, visit our website here.
Rich est directeur marketing pour les produits de cloud public chez Barracuda. Il a rejoint l'équipe dans le cadre de l'acquisition de C2C Systems en 2014. Rich est l'un des experts du cloud public de Barracuda. Il travaille directement sur les écosystèmes cloud et est cité dans des ebooks de Microsoft sur la sécurisation du cloud public. Il est également contributeur régulier des blogs thématiques sur le cloud de Barracuda. Dans le cadre de notre travail sur le cloud, il aide au développement de stratégies et à leur exécution avec nos partenaires et nos équipes commerciales.
Si vous souhaitez entrer en contact avec Rich, vous pouvez vous connecter avec lui sur LinkedIn et le suivre sur Twitter.
Vous pouvez contacter Rich par e-mail à l'adresse rturner@barracuda.com.