Marking guideline and sample response
Review a full-mark extended response, a completed security goal analysis table, and detailed marking criteria to strengthen your exam technique.
Completed planning table (model answer)
Security concept
How sandboxing helps
Confidentiality
Isolates untrusted code or components so they cannot access or leak private data.
Integrity
Prevents external modules or scripts from modifying internal data or application logic.
Availability
Contains faults or failures within a sandbox, reducing the risk of full system crashes.
Authorisation
Enforces boundaries between user roles or components, limiting access to only permitted actions.
Accountability
Assigns responsibility to sandboxed processes or users, making misuse easier to trace.
Marking guideline
5
Clearly explains how sandboxing supports the design stage. Demonstrates strong understanding of security by design. Accurately relates sandboxing to at least two named security concepts with relevant examples.
4
Explains sandboxing in the context of system design. Relates to at least one security concept with an example. May not fully develop all points.
3
Describes sandboxing with some link to security. Mentions a relevant security concept but lacks clear explanation or example.
2
Provides general or superficial comments on sandboxing or system design with limited relevance to security concepts.
1
Demonstrates minimal or confused understanding. May define sandboxing without linking to security or system design.
Sample response
Sandboxing supports the system design stage of the SSDLC by enforcing security by design — isolating untrusted or potentially risky components to prevent them from compromising the wider system. In this stage, developers make architectural decisions that determine how software modules interact, what resources they can access, and how failures are contained.
For example, a system might be designed so that third-party plug-ins run in a restricted environment where they cannot access sensitive files or memory. This supports the security goals of confidentiality by preventing data leaks and integrity by stopping unauthorised modification of core system data.
Sandboxing also contributes to authorisation, because it limits what permissions or APIs an isolated module can access, and to availability, because faults in one sandboxed area are less likely to crash the entire application. By embedding these constraints at the design level, sandboxing helps ensure the system remains secure, resilient, and accountable.
Last updated
Was this helpful?