💻 IT & Coding concepts,
clear in 60 seconds.

Authentication verifies who you are, while authorization determines what you can do.

OpenID Connect allows apps to authenticate users and verify their identities securely.

Session-based authentication uses cookies to remember users after login.

Secure API design requires multiple strategies to protect sensitive data and access.

OAuth 2.0 lets apps access user data securely without passwords.

mTLS allows microservices to verify each other's identities using certificates.

Access tokens are short-lived tokens for API access, while refresh tokens renew them without re-login.

API keys help identify clients and control their access to APIs securely.

JWTs allow secure user authentication without needing session storage.

CSRF tricks your browser into making requests without your consent.

Token expiration and refresh token rotation secure user sessions by limiting token lifespan and preventing unauthorized access.

Zero Trust Architecture ensures that no user or device is trusted by default.

Hashing is one-way for verification, while encryption is two-way for confidentiality.

Password hashing with unique salts ensures security by creating different hashes for identical passwords.

The CAP Theorem explains the trade-offs in distributed systems during network failures.

KMS securely manages encryption keys to protect data from theft.

SSRF is a vulnerability where an attacker tricks a server into making unintended requests.

Symmetric encryption uses one key, while asymmetric uses a pair of keys for security.

Transactions ensure database operations are reliable using ACID properties.

Encryption at rest and in transit are essential for protecting data both stored and in motion.

Active-passive architecture ensures a standby system takes over if the main system fails.

The TLS handshake establishes a secure connection for HTTPS, ensuring data safety.