🌍 Backend Development · flashcards

Backend Development Authentication, Authorization and Security Flashcards

51 question-and-answer cards covering Authentication, Authorization and Security as it is examined in Backend Development. 24 of them are printed below, taken from across the deck — no signup, no paywall on the preview.

51Cards in deck
24Free preview
22Syllabus topics
~229Chars per answer
FreePrice

24 sample cards from the Authentication, Authorization and Security deck

Sampled from the end of the deck, so these are different cards from the ones shown on the syllabus page.

  1. Compare SAML and OIDC for SSO.

    SAML is XML-based, mature, and common in enterprise/web-SSO. OIDC is JSON/JWT-based, built on OAuth 2.0, and better suited to modern mobile and single-page applications and APIs. Both federate identity via an IdP.

  2. In SAML, what are the roles of the Identity Provider (IdP) and Service Provider (SP)?

    The IdP authenticates the user and issues assertions. The SP is the application the user wants to access; it trusts and consumes the IdP's assertions to grant access without authenticating the user itself.

  3. Define Role-Based Access Control (RBAC).

    An access-control model where permissions are assigned to roles, and users are assigned roles. Access is determined by the user's role(s) rather than by individual user identity, simplifying administration.

  4. Define Attribute-Based Access Control (ABAC) and how it differs from RBAC.

    ABAC grants access based on policies evaluating attributes of the subject, resource, action, and environment (e.g., department, time, location). Unlike RBAC's fixed roles, ABAC is more dynamic and fine-grained, expressing context-aware rules.

  5. Give an example ABAC policy that RBAC alone could not easily express.

    "Allow access only if user.department == resource.department AND time is between 9am-5pm AND user.clearance >= resource.classification." This combines multiple contextual attributes rather than a single static role.

  6. What is an Access Control List (ACL)?

    A list attached to a resource (object) that specifies, per subject (user or group), which operations (read, write, execute) are permitted or denied. It is object-centric authorization.

  7. Contrast the object-centric ACL model with the capability-based model.

    An ACL is attached to the object and lists who may access it (answers "who can access this file?"). A capability is held by the subject as an unforgeable token/reference granting rights (answers "what can this user access?").

  8. In access control, distinguish the PEP, PDP, and PAP.

    PEP (Policy Enforcement Point) intercepts requests and enforces the decision. PDP (Policy Decision Point) evaluates policies and returns permit/deny. PAP (Policy Administration Point) is where policies are authored and managed. Often a PIP (Information Point) supplies attributes.

  9. What is the principle of least privilege?

    Every user, process, or system should be granted only the minimum permissions necessary to perform its function, and no more, reducing the attack surface and blast radius of a compromise.

  10. What is the difference between a default-deny (whitelist) and default-allow (blacklist) authorization policy, and which is safer?

    Default-deny blocks everything except explicitly permitted actions; default-allow permits everything except explicitly forbidden actions. Default-deny is safer because forgotten cases fail closed (denied) rather than being unintentionally exposed.

  11. What is the OWASP Top 10?

    A regularly updated awareness document listing the ten most critical web application security risks, published by the Open Worldwide Application Security Project to guide developers on the most common and impactful vulnerabilities.

  12. Name five categories from the OWASP Top 10 (2021).

    Broken Access Control, Cryptographic Failures, Injection, Insecure Design, Security Misconfiguration (others: Vulnerable and Outdated Components, Identification and Authentication Failures, Software and Data Integrity Failures, Security Logging and Monitoring Failures, Server-Side Request Forgery).

  13. What category ranked #1 in the OWASP Top 10 2021?

    Broken Access Control—flaws that let users act outside their intended permissions (e.g., accessing other users' data, privilege escalation, IDOR).

  14. What is an injection attack, and what is the root cause?

    An attack where untrusted input is interpreted as part of a command or query (SQL, OS, LDAP, NoSQL). The root cause is mixing untrusted data with code/commands without proper separation, so the data is executed as instructions.

  15. What is the primary defense against SQL injection?

    Parameterized queries / prepared statements, which bind user input strictly as data separate from the SQL code so it can never be interpreted as commands. Supplement with input validation, least-privilege DB accounts, and ORMs.

  16. What is Cross-Site Scripting (XSS)?

    An injection vulnerability where an attacker injects malicious scripts into web content that executes in other users' browsers, enabling session/cookie theft, defacement, or actions on the victim's behalf.

  17. Distinguish stored, reflected, and DOM-based XSS.

    Stored: malicious script is persisted on the server (e.g., in a comment) and served to victims. Reflected: script is embedded in a request and reflected back in the immediate response (e.g., via a link). DOM-based: the vulnerability is in client-side JavaScript manipulating the DOM with untrusted data, never reaching the server.

  18. What is the primary defense against XSS?

    Context-aware output encoding/escaping of untrusted data when rendering into HTML, attributes, JS, or URLs, plus input validation, using safe frameworks/APIs (avoiding innerHTML), and a Content Security Policy as defense in depth.

  19. What is Cross-Site Request Forgery (CSRF)?

    An attack that tricks an authenticated user's browser into sending a forged state-changing request to a site where they are logged in, exploiting automatically-sent credentials (cookies) to perform actions without consent.

  20. Name the main defenses against CSRF.

    Anti-CSRF synchronizer tokens (unpredictable per-session/per-request token validated server-side), the SameSite cookie attribute, double-submit cookies, and verifying Origin/Referer headers for state-changing requests.

  21. Why does the SameSite=Lax or Strict cookie attribute help mitigate CSRF?

    It instructs the browser not to send the cookie on cross-site requests (Strict) or only on top-level navigations (Lax), so a forged request from an attacker's site arrives without the victim's authentication cookie.

  22. What does the Content-Security-Policy (CSP) header do, and which attack does it primarily mitigate?

    CSP restricts which sources the browser may load scripts, styles, images, etc. from (e.g., script-src 'self'), primarily mitigating XSS and data-injection by blocking inline/unauthorized scripts.

  23. What does the HTTP Strict-Transport-Security (HSTS) header enforce?

    It forces browsers to use HTTPS-only connections to the site for a specified max-age, preventing protocol-downgrade and SSL-stripping man-in-the-middle attacks and blocking use of the plain HTTP version.

  24. Compare symmetric and asymmetric encryption in terms of keys, speed, and typical use.

    Symmetric uses one shared secret key for both encryption and decryption—fast, ideal for bulk data (e.g., AES). Asymmetric uses a public/private key pair (encrypt with one, decrypt with the other)—slower, used for key exchange, digital signatures, and identity (e.g., RSA, ECC). TLS combines both: asymmetric to exchange a symmetric session key.

What this deck covers

The Authentication, Authorization and Security deck follows the Backend Development Authentication, Authorization and Security syllabus — 5 chapters and 22 topics — so questions land on material that is genuinely examinable rather than trivia around it. That works out to roughly 10.2 cards per chapter.

Answers are written to be recallable, not just readable — averaging about 229 characters, which is long enough to carry the reasoning and short enough to say out loud.

A deck like this earns its keep on the second and third pass. Read the syllabus first so you know the shape of the subject, then use the cards to find the specific facts that have not stuck.

Authentication, Authorization and Security flashcards FAQ

How many Authentication, Authorization and Security flashcards are in this Backend Development deck?

51 cards. This page previews 24 of them, sampled evenly across the deck so you can judge the difficulty before installing anything.

Are these Backend Development flashcards free?

Yes. The preview here is free to read with no signup, and the full 51-card deck is free inside the Examius app.

What do the Authentication, Authorization and Security cards cover?

They follow the Backend Development Authentication, Authorization and Security syllabus — 5 chapters and 22 topics — so the questions track what is actually examinable.

How should I use these flashcards?

Read the syllabus first so you know the shape of the subject, then drill the deck. Examius schedules each card with spaced repetition, so cards you keep missing come back sooner and ones you know drift further apart.