Technical detail ยท Edge Processing for Big Data
Audit controls for versioned edge evidence
| Risk | Failure Mode | Control | Evidence to Forward |
|---|---|---|---|
| Model drift | Edge scores become less reliable after equipment, environment, or sensor changes. | Monitor score distribution, retrain with reviewed raw windows, and version model deployments. | Model id, feature vector summary, confidence, reviewed label, and drift metric. |
| Clock skew | Backfilled data lands in the wrong stream window or dashboard period. | Synchronize clocks, publish event time and arrival time, and mark outage backfill. | Event timestamp, gateway timestamp, arrival timestamp, and batch id. |
| Privacy leak | Raw images, audio, or personal identifiers are forwarded when summaries would suffice. | Redact locally, enforce allowlists, and audit payload classes before upload. | Policy id, redaction state, payload class, and reviewer approval for exceptions. |
| Unsafe replay | Delayed commands or duplicate alerts trigger actions twice. | Use sequence numbers, idempotent commands, expiry times, and acknowledgement state. | Command id, sequence, expiry, local state, and acknowledgement result. |