# PLO — Session 7: Security and identity

**CLO:** By the end of this session, the student can inventory and classify the course's credentials, scope each to the smallest action and resource the platform allows, prove a denied action and an expiring capability, rotate a secret, and defend five residual-risk judgements with audit evidence.

| PLO | Role | Research answer | Lab evidence | Points | Evidence | Rubric |
|---|---|---|---:|---:|---|---|
| PLO3 | primary | 4 | 3 | 7 | An 800–1,200-word trust-boundary analysis with 5–8 sources; the credential inventory, the denied-action proof, the presigned-URL expiry, the rotated Worker secret, the audit events, the five-row register and justification | Research 4/3/2/1; Lab 3/2/1/0 |
| PLO2 | secondary | 0 | 0 | 0 | Lecture context only; not scored | — |
| **Total** | | **4** | **3** | **7** | | |

**Total: 7 points**

## Four-level descriptors

**Research (4/3/2/1).** 4 = one concrete asset path traced through capture, storage, edge and inference, with the provider control, customer control and data class named at each step, the shared-responsibility model and PDPA cross-border rule cited, and a residual-risk judgement; a weak counterargument is addressed. 3 = a sound trace with most controls and a judgement, one step thin or the counterargument missing. 2 = recites the shared-responsibility slogan without choosing an asset or a boundary. 1 = a summary with fewer than five sources. 0 = nothing submitted or misconduct.

**Lab (3/2/1/0).** 3 = the read-only token is denied delete, the presigned URL works then expires, the Worker secret rotates under a single-Worker token, the audit events are recorded, the five-row register is valid and the top risks are justified, and teardown and cost are respected. 2 = mostly complete, one check thin. 1 = partial controls or an incomplete register/teardown. 0 = nothing submitted, unsafe data, or no teardown.

The full course arithmetic is in `production/baseline.md`; this file is the weekly instance.
