TK Study

Software Engineering › Key terms › Y12 Secure Software Architecture › Hardening systems

Hardening systems

Term Key terms bank Y12 Secure Software Architecture

Also listed as: Hardening

Definition

Reducing the attack surface by removing unused services and default accounts, applying patches and using strong configuration and least privilege.

Example: Disable unused ports.

Found in: syllabus, school notes.

Short version to memorise (key terms bank)

Reducing attack surface through configuration and patching.

Where it is used in the test

Syllabus area: Y12 Secure Software Architecture.

Question types it can appear in

No past question in this bank is linked to this term yet. It can still be tested through the question types above.

Study links

How to use it in an answer

A model sentence

General advice, built from the definition and example above

“Reducing the attack surface by removing unused services and default accounts, applying patches and using strong configuration and least privilege.” Then apply it: Disable unused ports.

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

General advice

No linked question shows the command word for this term. Across the past short answer 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

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: Determining vulnerabilities · Handling breaches · Business continuity · Disaster recovery · Code review · Static application security testing (SAST) · Dynamic application security testing (DAST) · Vulnerability assessment · Penetration testing

← Handling breachesIn Y12 Secure Software ArchitectureInput validation →