Skip to the content ForoHackers
Log inJoin

Identity and access: start here

Identity and access
#3275 · · Quote · Report

Identity and access management answers two questions for every request: who is this, and what may they do? Passwords, tokens, single sign-on and permissions all serve those answers. It matters because stolen or over-broad credentials are behind a large share of real breaches.

Key concepts

  • Authentication: proving who you are, with something you know, have or are; more than one factor is stronger.
  • Authorisation: deciding what an authenticated identity may do, by roles, attributes or explicit rules.
  • Federation and single sign-on: one identity provider vouches for you to many services, using standards such as OAuth 2.0, OpenID Connect and SAML.
  • Credential lifecycle: issuing, rotating, revoking and auditing accounts, keys and tokens, including those of machines.
  • Least privilege: grant the minimum and expire it; review who has access to what.

Vocabulary

  • MFA: multi-factor authentication.
  • Token: a signed or opaque credential presented instead of a password.
  • RBAC and ABAC: access control by role, or by attributes of user, resource and context.
  • Passkey: a public-key credential bound to a device and a site, resistant to phishing.

What to study, in order

  1. How password storage works: salted, slow hashes, and why plain or fast hashes fail.
  2. Add login with hashed passwords and a second factor to a small app of your own.
  3. The OAuth 2.0 and OpenID Connect flows, traced in a local setup with an open-source identity provider.
  4. Token details: expiry, audience, signature checks and revocation, and the mistakes in each.
  5. Design a role model for a small team, with a review process for removing access.

Related tags

#cryptography #appsec #web-security #cloud-security #privacy

You are not logged in, so this goes up anonymously: no account, no name and no address is stored with it, and it may carry no link and no image. Log in or join to post under your name. Our web server's logs keep the address and time of every request for up to 14 days; to keep yours out of them, use Tor. To reach the staff in confidence, use the drop. Sign as a returning source (a key kept only in this browser)

Sending takes a few seconds here: your browser first works out a proof of work against spam.

Reply