CyberKit

OAuth

Also called OAuth 2.0.

A framework for delegating limited access without sharing a password.

What it is

An authorization framework that lets a user grant a third-party application scoped access to their resources by issuing it a token, rather than sharing their actual credentials. It defines flows for different client types.

Why it matters

OAuth governs how apps gain access on a user's behalf, and abuse such as consent phishing for malicious app grants, leaked tokens, or open redirects in the flow is a recurring incident theme.

In practice

A rogue application requesting broad mailbox permissions so that, once consented, it reads mail without a password.

What to look for

  • Consent grants to unfamiliar apps with broad scopes.
  • Redirect URIs that are not exact matches.
  • Refresh tokens used from new locations.

Common mistake

Reviewing users but not apps. A malicious app with consent keeps access after a password reset.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

Read next

Sources