Current pilot boundary
Data minimization and redaction
Retain stable join IDs, timestamps, outcome/event type, actor class, financial amounts, currency and invoice/credit references. Remove or mask names, emails, phone numbers, addresses, internal usernames, unrelated free text and unnecessary account metadata wherever they are not required for reconciliation.
Passwords, API keys, tokens, full payment-card data, government IDs and authentication secrets should not be sent.
Chain of custody
Sources are hashed with SHA-256 before transformation. The operating process records logical filename, source role, byte size, hash, received timestamp and intake status. The objective is reproducibility from source bytes to claim evidence and rulebook version.
Current limitations
The managed-pilot security posture should not be represented as a mature enterprise security program. Recon Engine v1.1 does not currently provide:
- application-managed at-rest encryption;
- RBAC, SSO or SAML;
- automatic PII detection/redaction;
- a secrets vault;
- SOC 2 or ISO 27001 certification;
- digitally signed evidence packages or an immutable superseding receipt chain.
These controls belong after real-data qualification demonstrates sufficient demand to justify the enterprise build.