OAuth 2.0 Fundamentals
OAuth 2.0 as scoped token-based access between clients, users, and resource servers.
Authentication, authorisation, encryption, abuse prevention, and defence-in-depth patterns for protecting systems, data, and trust boundaries.
OAuth 2.0 as scoped token-based access between clients, users, and resource servers.
JWTs as signed tokens with a header, payload, and verifiable signature.
Sessions, cookies, JWTs, SSO, and OAuth 2.0 mapped to identity and access flows.
HTTPS handshakes, certificate checks, and encrypted HTTP over TLS.
Single sign-on through shared authentication, trust, and application sessions.
Network security controls and common threats mapped across OSI layers.
OAuth 2.0 flows for public clients, confidential clients, devices, and delegated access.
HTTP cookies store browser state and return it on matching later requests.
TOTP authenticators through shared secrets, time windows, and code validation.
VPN tunnelling through encrypted links, route changes, and trust boundaries.
SSH sessions through key exchange, host verification, and encrypted channels.
Cookies, sessions, JWT, and PASETO compared by state, transport, and revocation.
HTTPS safety through TLS trust, endpoint security, and controlled interception.
JWTs through signed claims, local verification, and stateless session design.
Session and JWT authentication compared by state storage and validation flow.
Symmetric and asymmetric encryption compared by key model, speed, and usage.
TLS handshakes through certificates, key exchange, and session encryption.
Sensitive data handling through minimisation, segregation, encryption, and audit.
Digital signatures combine hashing, private-key signing, and public verification.
Authentication mechanisms for password checks, session state, delegated access, and MFA.
Firewall policies for ports, addresses, applications, segmentation, and attack filtering.
Secure system design through trust boundaries, least privilege, and layered controls.
Tokens, cookies, and sessions as separate parts of a web authentication flow.
HTTP cookies through browser storage, scoping rules, and session continuity.
Cookies and sessions compared by client storage and server-side state.
Firewalls enforce network policy through packet, stateful, and application checks.
Passkeys through public-key login, phishing resistance, and device trust.
Password managers through local encryption, key derivation, and encrypted sync.
Permission system models including ACL, RBAC, ABAC, DAC, and MAC.
Password storage with slow hashes, per-user salts, and careful verification.
Encoding, encryption, and tokenization compared by representation and exposure.
DevSecOps embeds security checks and controls throughout software delivery.