Tip: Choose Save as PDF in the print dialog to download. Use A4 paper size.
Shade in the A or B circle for each question.
Draw a line connecting each item on the left to its match on the right.
| Left column | Right column | |
|---|---|---|
| 1Unpatched developer laptop | AA developer's machine missing OS or tool updates, so attackers can use known flaws to reach source code and saved credentials | |
| 2Unpatched build server | BDev machines and test servers hold code and data too. Leaving them unpatched gives attackers a way in, so they must be patched as well. | |
| 3Patch gap: the delay between a patch being released and it being installed, during which known flaws can be exploited | CDelaying installation widens the patch gap. Known flaws stay open and attackers can exploit them, so patches should be installed promptly after testing. | |
| 4A development environment is only as secure as its oldest unpatched part, so every OS, tool, library and server needs patching | DA server that compiles and tests code but is missing security updates, so attackers can use it to tamper with builds or read project data | |
| 5Only patch the production server; leave developer laptops and test servers as they are | Efor each item in [OS, IDE, library, server]: if patch_available: install_patch(item) | |
| 6if patch_available: wait_until_next_year() | Fpatch_released = 1 June; patch_installed = 30 June; exposed_days = 29 |
Complete each line of code by filling in the missing parts.
Shade in the letter of the line that contains an error.
Unpatched software — Software missing security updates, so known flaws stay open. In a dev environment, attackers can use them on developer machines or build servers to reach code and data.if installedVersion < patchedVersion:
print("Update needed")delayDays = installDay - releaseDayfor server in buildServers:
applyPatch(server)if delayDays > 14:
print("Patch overdue")if devLaptopPatched == False:
print("Unpatched developer laptop")