liveBook · Manning

Credential management

As explained in Secure APIs

Credential management is the practice of creating, storing, protecting, validating, and replacing authentication credentials.

Credential management protects the credentials and access tokens that establish user identity and permissions. Weak passwords, repeated credentials, or exposed tokens can let attackers take over accounts and undermine API security. section 4.4

Reduce common credential-management failures by:

  • Enforcing stronger password policies and preventing repeated brute-force attempts. section 4.4
  • Defending against credential stuffing when users reuse credentials leaked from other websites. section 4.4
  • Keeping passwords and access tokens out of URLs, and requiring password confirmation before changing sensitive account details. section 4.4
  • Treating multistep login flows as an enumeration risk unless threat detection prevents account discovery. section 4.4
Figure 4.3 An authentication system manages users’ identities, credentials, and access permissions. When a user logs in, they get back an API access token with specific permissions.
figure

Use the authentication-system diagram to connect identities and credentials with issued API access tokens and permissions. section 4.4

Figure 4.4 Credential stuffing is a common exploit in which threat actors use leaked user credentials from other websites and insert (stuff) them into our API to try to take over other user accounts.
figure

Use the credential-stuffing figure to visualize how leaked credentials from another website can drive account takeover. section 4.4

How Secure APIs covers it

How deep it goes
Explains password, brute-force, stuffing, enumeration, exposure, and token-validation failures, but does not detail storage algorithms.
Examples
Uses reused leaked credentials, multistep login, credentials in URLs, and unsigned or expired tokens as concrete failure cases.
What it assumes
Assumes only basic familiarity with user accounts, passwords, login flows, and API access tokens.
What you can do after
Diagnose/debug with it by identifying weak login controls, account-enumeration paths, exposed credentials, and improperly accepted tokens.
How it connects
Connects authentication with authorization, access tokens, credential stuffing, brute-force attacks, and user enumeration.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Secure APIs. The section links point to the parts of the book it draws on.