The seventh re-release allows an approved polymer archive workload to receive a short-lived service identity after attestation. That repair closes the inherited-selector path, but it introduces a living dependency: verifier policy and reference values must stay synchronized with approved workload changes.
A later attestation failure can mean a compromised or misconfigured workload. It can also mean that an approved image, kernel or deployment owner changed while the verifier still compares evidence with an obsolete reference set. Relaxing the verifier is unsafe; freezing every scientific workflow indefinitely is unnecessary. Surveillance must distinguish the two.
The Gold Standard is an evidence-continuous update path. It observes attestation results, reference provenance, credential issuance and archive actions together, then opens an eighth escalation only when uncertainty or recurrence exceeds a declared gate.
A practical orientation
Reference values are controlled claims used during appraisal, not timeless truths. Their owner, source, version, effective period and approval evidence matter as much as the value itself.
The worked example follows a legitimate base-image patch that causes 27 denials. It shows why the correct response is quarantine plus reference reconciliation, not an automatic allow-list expansion.
- Map the surveillance chain — for platform, quality and archive owners.
- Diagnose reference drift — for verifier and change-management teams.
- Follow the patch example — for the complete evidence sequence.
- Apply eighth-escalation gates — for containment and governance.
- Transfer the method — for instrument and analysis workloads.
Chapter contents
Open a route that matches the decision in front of you, or read straight through. Each route returns to the same evidence chain.
Start with the operating question
Build the evidence chain
Separate reference-value drift from workload drift
Work the example
Stress-test the decision
1. Map the post-re-release attestation chain
Link the attester, evidence, verifier, appraisal policy, reference-value provider, attestation result, relying party, credential issuer and archive action. Surveillance that stops at “pass” or “fail” cannot tell whether a denial protected the archive or reflected stale verifier state.
Record workload image digest, deployment owner, namespace, evidence freshness, verifier-policy version, reference-set version, result, credential audience and package action. Keep scientific package state separate from identity-control state so a control event is not mistaken for polymer degradation.
- Attester and workload owner.
- Evidence claims and freshness marker.
- Reference values and provenance.
- Verifier and relying-party policy versions.
- Credential issuance, renewal and archive scope.
- Package integrity, access and downstream-use evidence.
2. Monitor results, coverage and decision consequences
Track pass, deny and indeterminate results by workload, image, environment and policy version. Add coverage: which approved workloads actually produced current evidence, which reference values were exercised and which failover paths remained untested.
Join attestation results to credential and archive decisions. A verifier denial followed by an emergency credential is not a safe failure. A pass with no archive action is not evidence that the full relying-party path works.
| Layer | Measure | Question |
|---|---|---|
| Evidence | Age, completeness and signing path | Can the verifier rely on the submitted claims? |
| Reference | Version, owner and approval lineage | Is appraisal using current approved values? |
| Appraisal | Pass, deny and indeterminate by policy | What decision did the verifier produce? |
| Reliance | Credential and archive action | Did the relying party enforce the result? |
| Science | Package integrity and use | What polymer evidence or decision was affected? |
3. Separate reference-value drift from workload drift
Reference-value drift occurs when the approved workload state changes but appraisal data does not follow, or when a reference set changes without the workload and policy owners agreeing on its meaning. Workload drift occurs when evidence departs from the approved state. The symptoms can be identical: a digest mismatch.
Check the change record, build provenance, deployment owner, signed image, effective time and verifier distribution. A legitimate ticket alone is insufficient; prove that the running workload matches the approved artifact and that the reference update itself followed controlled review.
- Was the workload change approved before deployment?
- Does the running digest match the signed approved artifact?
- Was the reference provider updated from the same evidence?
- Did all verifiers receive the same version and effective time?
- Were old values retired without erasing prior decisions?
4. Treat reference updates as controlled evidence releases
A reference update should carry source, value, scope, policy compatibility, effective time, superseded value and approver. Distribute it through an authenticated path and confirm receipt. A value copied into a verifier without provenance can turn a protective control into a silent bypass.
Use overlap deliberately when rollout cannot be atomic. The overlap must name which workload versions are valid, how long both sets remain accepted and how the relying party prevents a retired vulnerable version from regaining access.
| State | Workload evidence | Reference state | Action |
|---|---|---|---|
| Approved new image | Signed digest and owner match | New value not distributed | Quarantine; complete controlled distribution |
| Unapproved image | Digest or owner outside change record | Any | Deny and escalate |
| Approved overlap | Old and new versions declared | Timed dual set | Allow only within scope and expiry |
| Expired old image | Retired digest observed | Old value still accepted | Deny; repair reference retirement |
5. Preserve decision continuity across policy changes
Store enough of each attestation decision to identify evidence, reference version, appraisal policy and result without retaining secrets unnecessarily. Later review must distinguish a pass under an older policy from a pass under today’s policy.
Link replacement values and policies to the same incident or change case. Do not overwrite the failed trace. The denial that exposed stale references is part of the evidence that the update path needed repair.
6. Worked example: 27 denials after an approved patch
An approved polymer archive workload moves from signed base image A17 to A18 after a security patch. Deployment owner and namespace remain correct. During the first hour, 27 of 84 runs are denied by one verifier pool, while another pool accepts A18. No denied run receives a credential.
Evidence shows the A18 digest matches the approved build and change record. The failing pool still uses reference bundle R41; the accepting pool uses R42. The team quarantines the inconsistent pool, preserves denials and package traces, distributes R42 through the controlled path and tests A17 retirement. It does not add a wildcard digest.
| Check | Observed evidence | Decision |
|---|---|---|
| Running artifact | Signed A18; approved owner | Legitimate workload change |
| Verifier pools | R41 denies; R42 accepts | Reference distribution split |
| Credential issuer | No credential after denial | Fail-closed path works |
| Archive packages | No denied action; hashes stable | No observed package change |
| Retirement test | A17 denied after expiry | Old reference removed correctly |
7. Recover without weakening appraisal
Remove the inconsistent verifier pool from reliance or keep its workloads quarantined. Reconcile reference bundles, verify policy compatibility, test approved A18 and explicitly test that unapproved digests and retired A17 remain denied.
Restore traffic gradually. Observe evidence freshness, appraisal result, credential issuance, renewal, failover and archive scope. A single successful A18 pass does not prove that every verifier, renewal path or emergency route is consistent.
8. Set eighth-escalation gates
Escalate when reference provenance is unknown, verifier pools disagree without a controlled rollout, a denied workload receives authority, a retired value remains accepted, evidence freshness cannot be established, or package access occurs outside the attested path. These gates concern control credibility, not only denial volume.
The eighth escalation should name containment scope, scientific consequence, evidence owners and exit tests. A high denial rate from a proven stale bundle may be operationally disruptive but contained; one credential issued after a denial can be more serious.
- Unknown or unauthenticated reference provenance.
- Unexplained verifier disagreement.
- Fail-open credential or archive action.
- Retired value still accepted after expiry.
- Evidence or policy version not reconstructable.
- Control recurrence across a repaired distribution path.
9. Monitor the update system, not just workload results
Measure reference publication-to-receipt time, verifier-version convergence, expiry compliance, failed retrievals and rollback. Exercise a representative update in a non-production or bounded path so the distribution mechanism is known before an urgent patch.
Assign owners to reference generation, approval, distribution, verifier operation and relying-party policy. Shared responsibility without named decision rights creates gaps that no cryptographic signature can repair.
10. Know the limits of attestation surveillance
A current reference and passing result do not prove benign future behavior, application correctness or polymer-method validity. Evidence roots, verifier policy and reference providers can fail. Downstream credentials can be stolen or misused after issuance.
Package provenance, analytical method, instrument state and scientific acceptance remain separate controls. Join them for consequence analysis, but do not let identity evidence substitute for material evidence.
11. Misconceptions, practical questions and transfer
Common mistakes are treating every digest mismatch as compromise, accepting every change ticket as proof, widening references to restore availability, deleting old policy decisions and measuring only verifier uptime. The repair is a controlled evidence-and-reference lifecycle.
Transfer the method to an instrument-data ingestion service. Replace image digest and archive scope with the instrument firmware, measurement service, dataset audience and release evidence appropriate to that environment.
Should an approved patch be allowed before reference distribution finishes?
Only through an explicitly controlled overlap or constrained route with declared scope, expiry and evidence. A general bypass defeats the appraisal chain.
Does a high denial rate justify relaxing the verifier?
No. Diagnose evidence, workload, reference and policy versions. Restore consistency while preserving fail-closed behavior for unapproved states.
12. Changed-context evidence check and authoritative sources
A strong check can reconstruct why one workload passed or failed, identify the exact reference and policy used, prove whether authority followed the result and show that retired values remain denied. If those facts are missing, restrict the affected relying path until evidence continuity is restored.
RFC 9334 defines attester, verifier, relying party, reference values and appraisal policies in the Remote ATtestation procedureS architecture. NIST SP 800-207A describes identity-based access control for cloud-native applications and service identities. They support the architecture; local polymer quality and change procedures determine scientific release consequences.
Continue through the Gold Standard ecosystem
Return to the Polymer Science subject root, the Gold Standard of Education parent, or the How X Works hub.
Immediate predecessor: seventh-escalation recovery and workload attestation · Earlier guide: post-sixth service-identity surveillance · Polymer Science root
These routes are grouped by learning purpose: prerequisite model, immediate predecessor, and the wider transfer framework. They are not substitutes for the evidence and limits stated in this guide.