Harmonic Security

PLT-011 · formerly GOV-012

Inspect uploaded content without permanent file retention

.md .json

Acceptance criteria

Webhook, pointer or in-place inspection so source files stay in enterprise-controlled storage.

Why it matters

Copying every uploaded file into another vendor's storage creates a second copy to protect.

How to verify

The vendor documents and shows how uploads are inspected without permanent retention.

OWASP adoption context

Upload inspection across the listed employee AI contexts should avoid unnecessary permanent copies, regardless of which tool receives the content.

Framework mappings

  • In-place or pointer-based inspection can examine data in use while limiting copied personal data and unnecessary retention by the inspection service. Buffers, logs, derived content and subprocessors still need checking; reduced copying does not prove zero retention or an operated leakage-prevention workflow.

  • Avoiding permanent copies can support personal-data retention limits when the Privacy category and relevant inspection service are in scope. Verify buffers, logs, derived content and subprocessors; enterprise source-file retention remains separate. Non-retention does not demonstrate that less personal information was collected or read.

  • Keeping inspected files in enterprise-controlled storage can limit unnecessary PII copies. The privacy link depends on personal data being present and actual copying limits, including caches, previews, derived content and subprocessors. Non-retention does not demonstrate deletion or an operated leakage-prevention workflow.