UTC: 00:00:00
SID: UNAUTHEN...
SYNC_ID: --
ENCRYPTION: ACTIVE (AES-256)
DEFCON: Lvl 4
● LIBR_ENGINE: DETECTED_DIP [$14,500 RECOVERED] ● ENTITY_RESOLUTION: FLAGGED_CRYPTO_TRANSFER [COINBASE -> UNKNOWN_WALLET] ● INTEL_ANALYSIS: BLOCKED_HOSTILE_TEXT [RISK_LEVEL: HIGH] ● ALERT: NEW_OFFSHORE_NODE_IDENTIFIED ● SYSTEM_STATUS: ENCRYPTION_ACTIVE (AES-256) ● LIBR_ENGINE: DETECTED_DIP [$14,500 RECOVERED] ● ENTITY_RESOLUTION: FLAGGED_CRYPTO_TRANSFER [COINBASE -> UNKNOWN_WALLET]
Field Manual // SEC-OPS-01

How to Use Our PGP Infrastructure

Follow these protocols to ensure asymmetric encryption for sensitive case data and verify the authenticity of official communications.

View Public Key

Protocol A: Encrypting Data

01
Import Public Key

Download our `.asc` key and import it into your PGP client (GPG, Kleopatra, or Canary Mail).

02
Encrypt File/Message

Select the files you wish to protect and choose "Encrypt" using the **Exit Protocol Inc.** key.

03
Transmit Securely

Send the resulting `.gpg` or `.pgp` file to our secure intake line. Only our hardware security modules can decrypt it.

Protocol B: Verifying Signatures

01
Locate Signature

Official documents/canaries contain a block starting with `-----BEGIN PGP SIGNED MESSAGE-----`.

02
Run Verification

Paste the message into your PGP tool and click "Verify".

03
Confirm Fingerprint

Ensure the signer is verified as **support@exitprotocols.com** with the matching fingerprint.

TERMINAL_OPERATIONS

Import via curl:

$ curl https://exitprotocols.com/pgp.asc | gpg --import

Encrypt a report:

$ gpg --encrypt --recipient support@exitprotocols.com data.pdf
Recommended Forensic Tools
Kleopatra (Gpg4win)
GPG Suite (GPGTools)
GNU Privacy Guard (CLI)
SECURITY ALERT: DATA EXPORT BLOCKED // INTERNAL USE ONLY