Chapter 35. You Can’t Get Information Security Right Without Getting Identity Right
Sarah Cecchetti
Security is Job Zero for every cloud engineer. It is critical to remember that in a cloud environment, you are building for multiple tenants who should never be able to access or change one another’s data. Every permission has to be perfect every time. The subfield of information security that handles people and permissions is called identity and access management—and it’s a fascinating field!
The place where you store users’ information is called a directory or identity store. If you don’t have existing users, their information will be collected when they sign up with your application, and stored in your directory. If you do have existing users, you may want to consider a federation model. Such a model uses existing credentials (usually a username and password) to log users in, so that they don’t have to go through the hassle of creating a new account. The most popular federation standards are Security Assertion Markup Language (SAML) and OpenID Connect (OIDC).
The most secure way to have users log in is through multifactor authentication. For this you want the user’s credentials to cover two of these three categories: something they know (like a password), something they have (like a phone), or something they are (like ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access