Software Engineering › Learn step by step › Y12 Secure Software Architecture
Item 217 of 426 · Year 12: Secure Software Architecture, 40 of 57
Broken authentication and session management
Term
Jump to a topic
- Exam format, question types and command words (46)
- Year 11: Programming Fundamentals (69)
- Year 11: The Object-Oriented Paradigm (33)
- Year 11: Programming Mechatronics (29)
- Year 12: Secure Software Architecture (57)
- Year 12: Programming for the Web (59)
- Year 12: Software Automation (35)
- Year 12: The Software Engineering Project (47)
- Diagrams and modelling tools (18)
- Python, SQL, pseudocode and CSS patterns (33)
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 you'll use it in the test
Syllabus area: Y12 Secure Software Architecture.
Question types it can appear in
- Multiple choice: Pick the option that matches the definition or example.
- Short answer: Define, outline or explain it and tie it to the scenario.
- Fill in the blanks: Choose this term to complete a statement or table.
Where it has appeared in the paper
Secure Software Architecture (Part A). Part letters follow each paper’s own layout.
Related past questions
- 2025 HSC Q8 (1 mark): User action controls Secure Software Architecture (Part A) · 1 mark
How to use it
A model sentence
“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
- Identify: Recognise and name. (2025 HSC Q8 (1 mark): User action controls)
Go deeper
- Flashcard: Broken authentication and session management in Secure Software Architecture (Year 12) · study that set
- Memorise: User action controls: broken authentication, XSS, CSRF, forwarding, race conditions
- Notes: User action controls: broken authentication, XSS, CSRF, forwarding, race conditions (Secure Software Architecture (Year 12))
- Full term page: every question, note and marking comment for Broken authentication and session management
Check yourself
Explain “Broken authentication and session management” in one sentence, give an example, and name a question type that could test it.
Reveal the answer
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.
Could be tested as: Multiple choice, Short answer, Fill in the blanks.