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 | |
|---|---|---|
| 1Rating: Met | AThe case study shows the practice is missing or ignores the criterion, so the risk is left open. | |
| 2Rating: Not met | BThe rating does not match the evidence. Reviews that happen only sometimes show the criterion is at most partly met. | |
| 3A justification quotes a specific detail from the case study as evidence for the rating. | CEvidence: "Developers share one admin password." | |
| 4A justification explains the consequence of the practice, linking the evidence to a security risk. | DConsequence: a stolen password exposes all systems. | |
| 5Criterion: Access control. Rating: Not met. | EThe rating has no justification: there is no quoted evidence from the case study and no consequence explained. | |
| 6Rating: Met. Evidence: "Code is reviewed only if time allows." | FThe case study gives evidence that the practice fully satisfies the criterion, so no significant gap exists. |
Complete each line of code by filling in the missing parts.
Shade in the letter of the line that contains an error.
rate and justify — Judge a practice as met, partly met or not met against one criterion, then justify the rating by quoting evidence from the case study and explaining the consequence.Criterion: Code is peer reviewed
Evidence: "Every change is reviewed"
Rating: MetCriterion: Secrets kept out of code
Evidence: "Keys in .env, one in the code"
Rating: Partly metCriterion: Backups are tested
Rating: Not met
Evidence: "No restore test was ever done"Rating: Not met
Evidence: "Staff share one admin login"
Consequence: Attacker gains full accessCriterion: Data is encrypted in transit
Evidence: "Customer data is sent as plain
text"
Rating: Not met