Harmonic Security

PLT-009 · formerly GOV-004

Control telemetry residency, retention, encryption, deletion and masking

.md .json

Acceptance criteria

Validate region, retention period, encryption, deletion behavior, identity masking and exclusions with Legal and Privacy.

Why it matters

Residency, retention and masking are the first questions privacy and legal teams ask.

How to verify

The vendor documents region, retention, encryption, deletion and masking, and shows the settings.

OWASP adoption context

Telemetry protection and retention choices apply across adoption tiers; actual data, deployment location and applicable obligations determine the settings.

Framework mappings

  • Validation of telemetry encryption, masking, retention and deletion provides assurance inputs for data protection and applicable confidentiality/privacy objectives. Stored and transmitted data need separate consideration; validation alone does not demonstrate operating safeguards, and these frameworks do not prescribe a universal hosting region or retention period. SOC 2: C1.1/C1.2 require the Confidentiality category and relevant information in scope; P4.2/P4.3 require Privacy and relevant information in scope. ISO/IEC 27001: These settings do not establish cryptographic key governance.

  • Legal and Privacy review of masking, location, retention and deletion provides evidence for examination and documentation of AI privacy risk. It is one part of assessing that risk across the system lifecycle.

  • Telemetry location, retention and handling settings provide facts for documenting AI data resources. A.4.3 does not itself prescribe all the listed safeguards, a hosting region or a retention minimum.