TK Study

Software Engineering › Key terms › Y12 Secure Software Architecture › Broken authentication and session management

Broken authentication and session management

Term Y12 Secure Software Architecture

Definition

Weaknesses in login or session handling (weak passwords, guessable or reused session IDs, no timeout) that let attackers act as another user.

Example: Use long random session IDs and timeouts.

Found in: syllabus.

Where it is used in the test

Syllabus area: Y12 Secure Software Architecture.

Question types it can appear in

Where it has appeared in the paper

Secure Software Architecture (Part A). Part letters follow each paper’s own layout.

Related past questions

These are the questions the flashcard set links to this term. Open each one and compare your answer with its marking criteria.

Study links

How to use it in an answer

A model sentence

General advice, built from the definition and example above

“Weaknesses in login or session handling (weak passwords, guessable or reused session IDs, no timeout) that let attackers act as another user.” Then apply it: Use long random session IDs and timeouts.

In a short answer, give the definition in your own words first, then tie it to the situation in the question. Do not copy the example above unless it fits the scenario.

Command words used with it

From the linked past questions
  • Identify: Recognise and name. (2025 HSC Q8 (1 mark): User action controls)

Technique for the question types

Common mistakes

General advice
  • Use the term exactly as the syllabus words it, then link it to the scenario in the question; the 2025 feedback repeatedly rewards using the stimulus.
  • Answer the command word: outline gives main points only, explain gives a reason or cause, discuss gives both sides.

Same group in the syllabus: Cross-site scripting (XSS) · Cross-site request forgery (CSRF) · Invalid forwarding and redirecting · Race condition · File attacks · Side channel attack