Some checks failed
validation / verify (push) Failing after 10s
Evidence was grouped only by the kind of problem, and a group gets one lesson, so what kept recurring inside "validation proposed a Check" could not be seen. A proposed or unimplementable Check is now also counted under each provider setting or resource type it names; a subject seen in two or more Executions is its own group and reaches the curator past triage. Over 32 Executions that gave five proposals. The owner approved three, now published: L-07 location Checks, L-08 Cloud SQL backup encryption, L-09 backend service capabilities. L-10 is held for more evidence and L-11 rejected. Also: retiring a lesson marks its proposal, so publish no longer brings a retired lesson back. L-04 had returned to the Skill that way. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
27 lines
834 B
Markdown
27 lines
834 B
Markdown
# L-11: CMEK encryption checks
|
|
|
|
Status: wontfix
|
|
Deliverable: target_architecture
|
|
Evidence-key: 5cd8dc3cda
|
|
Proposed: 2026-10-10
|
|
|
|
## Rule
|
|
|
|
Whenever a requirement mandates encryption at rest, explicitly create a Check ensuring that the `kms_key_name` (or the equivalent CMEK argument) is configured on every applicable Element.
|
|
|
|
## Why
|
|
|
|
Without an explicit Check, elements may default to Google-managed keys, leading to validation failures against security constraints.
|
|
|
|
## Evidence
|
|
|
|
Seen in 2 of 32 Executions, 2 times in all: validation proposed a Check about `kms_key_name` that the design lacked.
|
|
|
|
## Proof
|
|
|
|
Not yet measured.
|
|
|
|
## Comments
|
|
|
|
Rejected by the owner on 2026-10-10, on the agent's view: encryption at rest is on by default, and this rule would put customer-managed keys on designs whose requirements did not ask for them.
|