Software Engineering › Learn step by step › Y12 Secure Software Architecture
Item 210 of 426 · Year 12: Secure Software Architecture, 33 of 57
Sanitisation
Term Key terms bank
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
Cleaning input by removing or escaping dangerous characters so it cannot be run as code (for example HTML or SQL).
Example: Escape < and > so a script tag is displayed as text, not run.
Found in: syllabus, sample exam and familiarisation guidelines, school notes.
Cleaning or encoding input to neutralise dangerous characters.
Where you'll use it 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.
- Fill in the blanks: Choose this term to complete a statement or table.
Where it has appeared in the paper
Secure Software Architecture (Part B). Part letters follow each paper’s own layout.
Related past questions
- Sample exam Q18a (3 marks): Defensive data input handling Secure Software Architecture (Part B) · 3 marks
How to use it
A model sentence
“Cleaning input by removing or escaping dangerous characters so it cannot be run as code (for example HTML or SQL).” Then apply it: Escape < and > so a script tag is displayed as text, not run.
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
- Explain: Relate cause and effect; make the relationship between things evident; provide why and/or how. (Sample exam Q18a (3 marks): Defensive data input handling)
Official worked answer
Sample exam Q18a (3 marks): Defensive data input handling (3 marks): official criteria and sample answer
Criteria
3: Explains how defensive data input handling practices can be implemented for the website. 2: Outlines some features of data input handling practices. 1: Some relevant information.
Sample answer
Data sanitisation using client-side scripting can clean the data and remove dangerous input. Input validation on the client-side can check that entered data meets all of the requirements before getting processed by the server. Errors generated by data not meeting rules can be shown to the user.
Go deeper
- Flashcard: Sanitisation in Secure Software Architecture (Year 12) · study that set
- Memorise: Defensive data input handling: validation, sanitisation, error handling
- Key terms bank entry: Sanitisation
- Notes: Defensive data input handling: validation, sanitisation, error handling (Secure Software Architecture (Year 12))
- Notes: Design, develop and implement code using defensive data input handling practices,… (Secure Software Architecture (Year 12))
- Notes: Describe the benefits of developing secure software, including data protection and… (Secure Software Architecture (Year 12))
- Full term page: every question, note and marking comment for Sanitisation
Check yourself
Explain “Sanitisation” in one sentence, give an example, and name a question type that could test it.
Reveal the answer
Cleaning input by removing or escaping dangerous characters so it cannot be run as code (for example HTML or SQL).
Example: Escape < and > so a script tag is displayed as text, not run.
Could be tested as: Short answer, Multiple choice, Fill in the blanks.