[ SECURITY_PROTOCOL_V1.0 ] [ SECURITY_PROTOCOL ]

All client repositories are analyzed within isolated, air-gapped forensic environments. Analysis occurs strictly on encrypted volumes with network egress disabled.

• • NO cloud-based IDEs are used.
• • NO code is pasted into public LLMs (ChatGPT/Claude).
• • Analysis is performed using local static analysis tools and self-hosted models.

Upon delivery of the Final Artifact (or 48 hours after project termination), the following sequence is executed:

1. 1. The forensic environment is dismantled and access is revoked.
2. 2. Storage sanitization via NIST SP 800-88 Rev. 1 (cryptographic erase for SSDs, secure overwrite for HDDs).
3. 3. All intermediate artifacts (logs, analysis graphs, cached data) are purged from memory and disk.
4. 4. Encrypted volumes are cryptographically wiped via key destruction.

A destruction attestation is recorded in the engagement log. For SSDs, we prefer ATA Secure Erase where supported.

All client engagements will be governed by a strict Mutual Non-Disclosure Agreement (NDA).

• • Professional Liability Insurance (E&O) required before client intake ($1M-2M coverage).
• • Zero retention of IP rights (guaranteed via MSA).
• • All engagements governed by lawyer-drafted NDA and MSA/SOW templates.

In the event of a security anomaly:

• • EMAIL: miguel.ingram.research@gmail.com
• • PGP KEY: 2A55 89CB 674A 52C6