Software Engineering › Key terms › Y12 Secure Software Architecture › Determining vulnerabilities
Determining vulnerabilities
Term Y12 Secure Software Architecture
Definition
Finding weaknesses before attackers do, using code review, SAST, DAST, vulnerability assessment and penetration testing.
Example: Run a vulnerability assessment before release.
Found in: syllabus, school notes.
Where it is used in the test
Syllabus area: Y12 Secure Software Architecture.
Question types it can appear in
- Short answer: Define, outline or explain it and tie it to the scenario.
- Multiple choice: Pick the option that matches the definition or example.
- Extended response: Use it as a supporting point linked to the stimulus.
No past question in this bank is linked to this term yet. It can still be tested through the question types above.
Study links
- Flashcard: Determining vulnerabilities in Secure Software Architecture (Year 12) · study that set
- Memorise: Test and evaluate security and resilience
- Notes: Test and evaluate the security and resilience of software by determining… (Secure Software Architecture (Year 12))
How to use it in an answer
A model sentence
“Finding weaknesses before attackers do, using code review, SAST, DAST, vulnerability assessment and penetration testing.” Then apply it: Run a vulnerability assessment before release.
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
No linked question shows the command word for this term. Across the past short answer and extended response questions in this bank the words used most are: Explain, Outline, Describe, Compare, Classify, Analyse. Check the actual word in your question.
Technique for the question types
- Short answer: One clear point per mark, use the stimulus and course terms, and answer the command word.
- Multiple choice: Read all four options, rule out wrong ones, pick one; no penalty for guessing so never leave blank.
- Extended response: Plan with the command word, give a judgement or explanation supported by named details from the stimulus, use course terms and cover both sides when asked.
Common mistakes
- 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.
Related terms
Same group in the syllabus: Hardening systems · Handling breaches · Business continuity · Disaster recovery · Code review · Static application security testing (SAST) · Dynamic application security testing (DAST) · Vulnerability assessment · Penetration testing