/ CPX SYSTEMS / GHOSTKEY / COMMAND
SAFE LAB MODE
SECURITY ENGINEERING / FIELD OPERATIONS GX / 002
⊕ GHOSTKEY ADVERSARY ASSURANCE SYSTEM LAB BUILD 2.0

Every signal
has a story.

Trace the credential. Challenge the trust boundary. Prove what the evidence can—and cannot—establish.

00 real lock tests07 modeled threatsOFFLINE / READ-ONLY BY DEFAULT
ACCESS TRUST TOPOLOGYCONCEPT MODEL / NOT LIVE TELEMETRY
TRUST BOUNDARY ◈CARD / FOB ▱KEY ISSUANCE ⌑LOCK READER ▤AUDIT EVIDENCE FIG.01 / MODEL-BASED ASSURANCE NO ACTIVE RF INTERACTION
NFC METADATA POLICY RULES LOG EVIDENCETOPO // 001
P0 / FIELD VALIDATION STILL MISSING

Two real targets. No invented results.

Start by identifying the IHG card, then document legitimate door behavior and obtain authorized vendor audit evidence.

OPERATIONAL PICTUREREAL DATA IS LABELED / UNVERIFIED IS VISIBLE
HARDWARE EVIDENCE↗
0/4
Four physical tag slots
THREAT VALIDATION⌁
0/7
Synthetic scenario runs
DOOR INTELLIGENCE◫
0
Imported or simulated events
PHYSICAL VALIDATION—
0
Controlled lock tests to date
FIELD WORKFLOWS CHOOSE YOUR NEXT OPERATION
ENGAGEMENT GOVERNANCE ROE / 01
⌁
Rules of engagementRequired for physical NFC operations
POLICY / A
Hard boundary. No active hotel-key duplication, lock bypass, protected-sector extraction, or live-door command sequences.
PROVENANCE / WHAT WE ACTUALLY KNOW

Keep observation separate from interpretation.

OBSERVEDMIFARE Classic 1KOne white card + blue fob from earlier NFC Tools screenshots
NOT PROVENDoor authorizationNone connected
GHOSTKEY BY CPX / RESEARCH SYSTEMLAB BUILD 2.0 — LOCAL EVIDENCE — PRIVILEGED ACCESS DISABLED