If your company manages Apple devices, MDM and Declarative Device Management (DDM) sit with IT. That is normal. What is not is that Apple’s CloudConfig path can enroll a device under a DDM administrator with no user-visible profile, no confirmation, and no limit on how many outside devices can be credentialed as Owner against an executive Apple ID. Screen share and proximity sessions can follow without anything appearing in Settings. There is no official way for the person being managed to audit the managers. Forensic Monitor is that audit. It reads Apple’s own rapportd and bluetoothd output in real time and alerts when a foreign device authenticates as owner of the account. The record is Apple’s, timestamped and sealed — including the screen-share and AWDL markers counsel can put in front of a court. You do not take IT’s word for it. You do not have to ask.
SAMPLE DATA:
CRIMINAL EVIDENCE OF PROXY STALKING → 18 U.S.C § 2261A
CRIMNAL EVIDENCE OF UNAUTHORIZED SCREEN-SHARING → 18 U.S.C. § 2511
CRIMINAL EVIDENCE OF AUTOMOTIVE TAMPERING → 18 U.S.C. § 1030, 33
FROM DDM INJECTION TO FEDERAL CRIME → HOW A DDM EXPLOIT WORKS
FEATURES:
PROXY TRACKING AND DEVICE ID→
DEVICE TRACKING IN 10 FT INCREMENTS →
Plug it in. It captures the invisible — unknown devices, crowdsourced operations, individuals — authenticating against your Apple account through unauthorized MDM/DDM installation without your knowledge, their proximity to you, use of their peer-to-peer connection to your device to obtain screen sharing, camera sharing and keyboard access.
The evidence is immutable. Every captured device is logged, timestamped, and sealed under a SHA-256 chain of custody that cannot be altered without breaking the math.
Print the Vault Hardening Report. Hand it to your attorney.
The logs are presumed authentic under Federal Rules of Evidence 902(13) and 902(14). The defendants have to prove the impossible — that the math is wrong.
This type of exploit is undetectable to the user and to the Apple Store Genius Bar. Apple will tell you to wipe your hard drive which has no effect. If you hand our FM report to the Apple Store you will find they have no protocol in place for the criminal use of their MDM software and send you away without a repair and do not report it to the corporate office. Compounding this, once the nefarious DDM is installed there is no cap on the amount of unauthorized accounts that can be added.
FM Light first locates your trusted Apple mobile device linked to your account by plugging your device into your laptop or computer. FM reads your CoreBluetoothDevice ID (IDID) instantly. Next it hunts for your Rapport Bluetooth Address (rpBA)—the hexadecimal beacon ID your device broadcasts. This beacon number is software-driven and rotates to obfuscate your identity.2 FM counts the total number of beacons within a 33 ft radius and determines which one is you then continues to sample local BLE beacons.
After that it looks for impostors—other rpBAs sharing your account ID (IDS) and claiming authorized ownership access.3 If it finds them—evidence of unauthorized DDM access—FM separates those from your ID tags and flags them.
While it’s doing that, it also looks for services that have been provisioned against your device. On an exploited device you will typically see these first, because your attacker—once in—will flood your device with screen sharing and keyboard sharing to harvest intel. FM flags those as well, in separate listings.
rapportd — Apple's Continuity authentication daemon — in real time using macOS's built-in log stream command.1 Every entry in the output is written by Apple's software, not by this tool. The monitor captures; it does not generate.LIVE_STREAM.log produced by this tool constitutes the primary forensic record produced by this tool.generate_report.sh. Each report documents daemon status, vault integrity, live forensic statistics, and asserts the evidentiary basis under Federal Rules of Evidence 902(13) and 902(14). The report is sealed in the root vault and its SHA-256 hash is appended to the master chain of custody at the exact moment of generation. Run it before any court filing, discovery response, or supplemental submission.1. Milan Stute, Alexander Heinrich, Jannik Lorenz, and Matthias Hollick, “Disrupting Continuity of Apple’s Wireless Ecosystem Security: New Tracking, DoS, and MitM Attacks on iOS and macOS Through Bluetooth Low Energy, AWDL, and Wi-Fi,” in Proceedings of the 30th USENIX Security Symposium (USENIX Association, 2021), 3920–22, §§3.3, 3.6.2. Documents analysis of Apple Continuity through rapportd using the macOS log stream command, and identifies rapportd as the secure transport for Continuity services.
2. Stute et al., “Disrupting Continuity,” 3924, 3929, §§4.1.3, 5.4. Identifies rpBA as a randomized, rotating device identifier carried in Apple’s companion-link service records.
3. Stute et al., “Disrupting Continuity,” 3923–24, §§4.1.1, 4.1.3. Documents that same-account device resolution depends on keys synchronized through the account’s iCloud keychain (RPIdentity-SameAccountDevice and Bluetooth Identity Resolving Keys).
Full text: usenix.org/system/files/sec21-stute.pdf →