01.04: Cryptography, Sandboxing and Compliance

Cryptography, sandboxing and compliance, explained for HSC Software Engineering (Year 12, Secure Software Architecture). Security by design: the four security features the syllabus wants built in (data protection, security, privacy, regulatory compliance), then cryptography with the two kinds of encryption, hashing a password with a salt in Python, and sandboxing as running code in a box it cannot leave. In this video: • The breach where the passwords stayed secret • Four security features the syllabus wants built in • Cryptography: two kinds of encryption • Hashing a password with a salt • Sandboxing: run it in a box it cannot leave • Exam Lens: a sample question, the marks, the command word, and what a top answer includes Syllabus: NSW HSC Software Engineering (NESA), Year 12, Secure Software Architecture. • Apply security features incorporated into software including data protection, security, privacy and regulatory compliance • Use and explain the contribution of cryptography and sandboxing to the 'security by design' approach in the development of software solutions Video 4 of 40 in the Year 12 series. Watch in order: {{YEAR12_PLAYLIST_LINK}} Next: 1.5 Privacy by design Every video in the series covers one cluster of syllabus points in about five minutes: a real story, the teaching, an Exam Lens question and a one-breath recap. Made by a NSW teacher for students across the state doing HSC Software Engineering. The content follows the NESA syllabus, but the ideas are the ones any software engineer needs. #HSC #SoftwareEngineering #Year12