ENGAGEMENT CONTROL / V1.0
Think like an attacker.
Prove the defense.
Four NFC devices. One controlled evidence pipeline. Credential-threat emulation and door-audit correlation without mistaking scans for successful access.
0%evidence coverage
ENGAGEMENT SCOPE
REQUIRED FOR HARDWARERules of engagement
Assess only devices you own or are expressly authorized to test. Simulations never access a physical lock.
Scope boundary: no live hotel-key copying, credential extraction, card emulation or physical-door bypass.
ATTACK SURFACE
5 CONTROLSAccess trust chain
01CredentialNFC / BLE
→02ReaderProtocol
→03PolicyGrant / deny
→04AuditProof
Chip compatibility never establishes door authorization. A compromised or offline lock may produce incomplete or misleading event records.
Current lock telemetry: None connected
MISSION INTELLIGENCE
What is known vs. what is not
Previously observed
White card 1 and blue fob were identified as MIFARE Classic 1K in NFC Tools screenshots. Three cards previously showed empty NDEF records.
Not established
No cryptographic card identity, hotel-lock firmware, issued credential ledger, verified entry event, or valid cloned credential.
DISCOVERY / PASSIVE NFC
Hardware reconnaissance
Identify all three white cards and the blue fob. Reader identifiers are volatile comparison hints, not proof of cryptographic ownership.
LIVE SENSOR
READ ONLYChoose a test device
Select a device. Use Chrome on Android with NFC enabled.
The reader supplied no identifier. You cannot verify that this is a different physical device.
FALLBACK
USER-ENTEREDNFC Tools classification
IMPORT / REPLAY
Load previous GHOSTkey evidence
Sample preview uses only your previously reported NDEF classifications. It is not a fresh scan or chip authentication.
BENIGN COPY LAB / CPX-OWNED ONLY
WRITE OPERATIONDuplicate a harmless NDEF record
Use a previously checked, blank white card. This writes the same non-secret lab text to each card; it does not copy chip identity, protected sectors, authentication keys or any hotel credential.
FIXED TEST RECORD
CPX-GHOSTKEY-LAB-NONACCESS-2026-10-31Select white card 01–03 above. Never write this test onto an active hotel key or unknown card.
After a successful browser write, verify the exact plaintext with NFC Tools → READ. A write acknowledgement alone is not independent proof of byte-for-byte persistence.
CONTROLLED ATTACK SIMULATION
Adversary emulation
Seven threat hypotheses across credential replay, policy, issuance, and audit integrity. Simulated detections are never reported as real-world exploit confirmation.
MISSION ENGINE
SYNTHETIC DATADetection validation suite
No scenarios executed. No physical systems are connected.
SCOPE OF TESTING
Attack-chain coverage
Credential content SimulatedIssuance policy SimulatedReader validation Not connectedDoor audit Synthetic / import
ACCESS EVENTS / READ ONLY
Door audit intelligence
Correlate authorized, anonymized vendor log exports. The browser cannot interrogate a hotel door or retrieve its historical records.
READER PROFILE
Target context
Identify the lock using its visible label or supported manufacturer documentation. No live-door probing.
AUDIT INGEST
Evidence intake
Input must contain anonymized pseudonyms, approved data provenance, and no guest identities, room numbers, raw card IDs, passwords or keys.
No vendor events available.
CORRELATION OUTPUT
NO REAL AUDIT DATAAccess anomaly stream
No lock events analyzed. Run the synthetic demonstration to inspect the detector.
ASSURANCE / EVIDENCE
Findings & reporting
Separate observed facts, synthetic simulations, coverage gaps, and unresolved risks. No claimed exploit without evidence.
EVIDENCE QUALITY
Verification matrix
REMEDIATION
Control priorities
DELIVERABLES
LOCAL FILES ONLYExport assessment
All results remain on this page until you export them. The application never uploads tag data or audit records.