Follow these links for each risk’s controls, verification and residual assumptions. Each chapter owns its guidance; this index adds no requirements.
Find the relevant explanation§
- Executed code crosses into publication authority
Execution boundaries, Action wrappers and effective settings.
- Storage or an upgrade substitutes executable bytes
Artifact admission, provisioning, tool selection and upgrades.
- Tested source or assets differ from the delivered release
Release evidence, example archives and native-input publication.
- Source roles or native targets are confused
- Partial, stale or unrelated results appear successful
- A test hangs, hides diagnostics or substitutes smoke for deeper testing
- Utility copies, companions or interfaces drift
- Composition records omit components or bind the wrong artifact
- Documentation or an assessment overstates the checks
Documentation claims, retrievable formats, diagram rendering and maintaining explanations.