Table of Contents

Class ErasureCertificate

Namespace
Excalibur.Compliance
Assembly
Excalibur.Compliance.Abstractions.dll

Signed record of a completed GDPR Article 17 erasure request.

public sealed record ErasureCertificate : IEquatable<ErasureCertificate>
Inheritance
ErasureCertificate
Implements
Inherited Members

Remarks

A certificate is a record of the request, not proof that the data was disposed of. Its signature does not cover every claim it carries, and the evidence of disposal is the key-management service's record of each key deletion. They are retained for 7 years to support regulatory audits and legal discovery.

The certificate includes: - Anonymized data subject reference (hash) - Erasure method and summary - Verification proof from KMS - Digital signature for integrity

Properties

Payload

Gets everything this certificate asserts — and exactly what Signature covers.

public required ErasureCertificatePayload Payload { get; init; }

Property Value

ErasureCertificatePayload

Remarks

The signature is computed over a canonical serialization of this payload in full. Nothing outside it is signed, and nothing inside it is skipped, so "what the document claims" and "what was signed" cannot diverge.

Signature

Gets the HMAC-SHA256 signature over Payload.

public required string Signature { get; init; }

Property Value

string

Remarks

The signature lives on the envelope rather than on the payload, and that placement is the fix. While it sat among the claims it had to be excluded from its own input, and an exclusion is a list somebody maintains — the moment a second self-referential field appears, forgetting to exclude it is an infinite regress that fails closed only by luck. Here there is no exclusion list to forget.

Consumer obligation: a signature authenticates the payload it covers and nothing else. Verify it against a canonical serialization of Payload, and read Version from INSIDE the verified payload — never from an untrusted envelope — when deciding which scheme to apply.