iPhone Device, Accounts and Permissions Forensics
Identify an iPhone and its users: device identifiers, Apple Account and other accounts, installed apps, TCC permissions, profiles and MDM enrolment.
Before reading a single message, an examiner should be able to answer four questions about an iPhone: what device is this, who is signed into it, what is installed on it, and what has been allowed to do what. The answers anchor attribution, decide which cloud providers to approach, point to the app containers worth examining, and often settle stalkerware and insider cases on their own.
This guide lists the sources for each question, which acquisition level reaches them, and how to combine them.
Question 1: what device is this?
Record identifiers from the device itself (Settings > General > About) during seizure if the screen is accessible, then confirm them from data:
| Source | What it gives | Reaches |
|---|---|---|
ideviceinfo / pymobiledevice3 lockdown info | Model, serial, UDID, iOS version and build, phone number, IMEI and more | Live device, trusted pairing |
Backup Info.plist | Device name, product type and version, serial, UDID, IMEI, phone number, last backup date, installed apps | Every backup, not encrypted |
Backup Manifest.plist | Encryption flag, lockdown data, apps, date | Every backup |
SystemVersion.plist | iOS version and build | Full file system, sysdiagnose |
data_ark.plist and lockdown files | Activation and device state values | Full file system |
sysdiagnose remotectl_dumpstate.txt | Hardware and OS details | sysdiagnose |
The iOS build matters as much as the version: artifact schemas and tool support change within a major release. Put it at the top of every report.
The device's time zone and clock also belong here. Record the time shown against a reference clock at seizure, and extract the configured time zone; pattern-of-life sources record changes.
Question 2: who is signed in?
Accounts3.sqlite is the central source. It lists the Apple Account and its children (iCloud services, IDS for iMessage and FaceTime, Game Center), mail, calendar and contacts accounts (Exchange, Google, IMAP, CalDAV), and third-party accounts registered through the Accounts framework, with user names and creation dates.
Corroborate with:
- Screen Time user tables (
ZCOREUSER): Apple Account, DSID, family member type. - iMessage and FaceTime handles in sms.db (
message.account) and call history. - App Store purchaser in each app's
iTunesMetadata.plist, via installed apps. - Keychain entries, if the extraction includes it: tokens and passwords for services, organised by keychain access group.
- Third-party app containers: most apps keep their own user identifiers in preferences and databases.
Creation dates in Accounts3 can predate the device when the phone was restored from a backup or migrated. Establish the device's history (activation, first backup, restore traces) before interpreting them.
An unexpected Apple Account, or the owner's account known to another person, is the most common route for covert access on iOS: iCloud backups, Messages in iCloud, Photos and Find My all follow the account.
Question 3: what is installed?
There is no single list. Combine:
- Backup
Info.plistandManifest.plistfor a quick inventory, readable without decrypting. applicationState.dbfor bundle IDs and container paths.iTunesMetadata.plistin each bundle for purchaser, purchase date and source app.- Container metadata plists to map UUID folders to bundle and group IDs.
mobile_installation.logfiles andUninstalledApplications.plistfor events, where present.
The installed apps page details each source. For apps removed before seizure, look for traces in DataUsage, crash reports, Biome and knowledgeC app install streams, interactionC.db, and older backups on the owner's computers.
Pay attention to the installation source. Apps from TestFlight, enterprise certificates, MDM or, in the EU, alternative marketplaces follow different paths than App Store apps and deserve a closer look in security cases.
Question 4: what is allowed to do what?
Privacy permissions (TCC)
TCC.db stores, per app and service, whether access to the camera, microphone, photos, contacts, calendars, reminders, Bluetooth, motion and other resources was denied, allowed or limited, why (user, system, MDM), and when that last changed (Unix seconds). It reaches a backup, and a copy sits in sysdiagnose archives.
Read it with the question "which apps could do what, since when?". It does not prove use: for that, turn to PowerLog camera and audio tables and Biome streams.
Location permissions
Location is outside TCC. locationd keeps authorisations in clients.plist, which reaches a backup under RootDomain. See locationd. An app with "Always" location access and an unfamiliar name is a priority in stalkerware cases.
Configuration profiles and MDM
Configuration profiles can install root certificates, VPNs, global proxies, Wi-Fi networks, restrictions and MDM enrolment. The profiles container (systemgroup.com.apple.configurationprofiles) holds the installed profiles, MCProfileEvents.plist with install and removal events and the process that performed them, and CloudConfigurationDetails.plist for Automated Device Enrollment. It reaches a backup.
A corporate device with its employer's MDM is normal. A personal device with a profile from an unknown organisation, or with a root certificate plus a VPN, needs an explanation. MDM can also set TCC decisions (auth_reason MDM policy) and push Wi-Fi networks, so check before attributing a setting to the user.
Network settings
Known Wi-Fi networks (encrypted backup or full file system) record networks, BSSIDs and last joins, and whether a network came from a profile or sync. VPN configurations appear in profiles and in network extension preferences.
Trusted computers and pairing
A device that trusts a computer can be backed up by it, so pairing is part of "who has access". On the phone, pairing and lockdown activity appear in lockdown logs within a sysdiagnose and in unified logs while they last. On the computer side, pairing records sit in /private/var/db/lockdown/ on macOS and in %ProgramData%\Apple\Lockdown\ on Windows, named after the device UDID, and backups sit in MobileSync/Backup. Finding a pairing record for the examined iPhone on a computer that is not the owner's is a strong lead: that computer could create backups of the phone while it was unlocked.
The iPhone can clear trusted computers through Reset Location & Privacy. That is a remediation step, not a forensic one: record the state first.
Sources by acquisition level
| Source | Unencrypted backup | Encrypted backup | Full file system | sysdiagnose |
|---|---|---|---|---|
| Info.plist, Manifest.plist | Yes | Yes | n/a | n/a |
| Accounts3.sqlite | Commonly | Commonly | Yes | No |
| TCC.db | Yes | Yes | Yes | Copy |
| locationd clients.plist | Yes | Yes | Yes | No |
| Configuration profiles | Yes | Yes | Yes | Partial |
| Known Wi-Fi networks | No | Yes | Yes | Copy |
| applicationState.db, installation logs | No | No | Yes | Logs only |
| Keychain | No | Partly | Depends on method | Metadata only |
"Commonly" means the file is present on the builds documented publicly: confirm it in the backup's Manifest.db before relying on it.
Putting it together: a device profile sheet
For every case, fill one page before analysis:
- Model, serial, UDID, IMEI, iOS version and build, device name.
- Acquisition levels obtained, device state (BFU or AFU), dates and tools.
- Time zone, clock offset at seizure.
- Apple Account and other accounts with creation dates.
- Installed apps of interest, with install source and purchaser.
- Permissions of note (camera, microphone, contacts, location "Always").
- Profiles and MDM enrolment, with install dates.
- Known networks of note.
This sheet is what the rest of the analysis, and the report, will lean on.
Stalkerware and coercive control
Most covert access to iPhones abuses features rather than exploits. The sources above are the core of that investigation:
- Accounts: a second Apple Account, or the owner's account with devices the owner does not recognise.
- Profiles: MDM or VPN profiles installed while someone else had the phone.
- Apps and permissions: apps with microphone, camera or location access that the owner did not install.
- Sharing: Find My location sharing, family groups, shared albums.
- Timing: install and permission change times against periods when someone else had the unlocked phone.
Pair this with the spyware triage guide and involve safety planning before removing anything.
Timestamps in this area
| Source | Format |
|---|---|
Accounts3.sqlite ZDATE | Cocoa seconds |
TCC.db last_modified | Unix seconds |
| Profile and Wi-Fi plists | Plist dates (UTC) |
iTunesMetadata.plist purchaseDate | Plist date (UTC) |
mobile_installation.log | Local time text, no offset |
Mixing Cocoa and Unix seconds is an easy error here: a TCC date read as Cocoa time lands 31 years late. See Mac Absolute Time.
Collecting these sources
Most of this area is reachable without a full file system extraction, which makes it a good first pass while an extraction is pending.
ideviceinfo > ./case/device/ideviceinfo.txt # identity from lockdown (trusted pairing)
ideviceinfo -k ProductVersion; ideviceinfo -k BuildVersion
idevicebackup2 encryption on '<case-password>'
idevicebackup2 backup --full ./case/backup/
plutil -p ./case/backup/<UDID>/Info.plist | less # device and installed applications
After decrypting the backup (for example with mvt-ios decrypt-backup), resolve Accounts3.sqlite, TCC.db, locationd clients.plist and the configuration profiles domain through Manifest.db, copy them out, and hash them. From a full file system, add applicationState.db, the Bundle/Application metadata, the container metadata plists, installation logs and the full profiles container. From a sysdiagnose, add the TCC copy, installation logs and remotectl_dumpstate.txt.
Keep screenshots of the Settings pages you consulted on the live device (About, Apple Account and its device list, VPN & Device Management), with the time taken. They are often the clearest exhibit for a court, and they document what the device displayed before any examination tool touched it.
A worked example
A personal iPhone is examined after the owner reports that an ex-partner seems to know her location and read her messages. The device profile sheet shows iOS 18 on a phone bought eight months earlier. Accounts3.sqlite lists the owner's Apple Account with a creation date matching the purchase, and no second Apple Account. The configuration profiles container holds no profile, and MCProfileEvents.plist shows none installed or removed. TCC.db shows no unfamiliar app with microphone or camera access, and clients.plist has no unknown location client.
The Apple Account's device list, however, shows an iPad the owner does not use. Screen Time's cloud store confirms an iPad named after the ex-partner's child reporting usage under the owner's account. The finding is not malware but account sharing: the iPad, signed into her Apple Account, receives her iMessages and her Find My location. The report states this, lists what was checked and found clean, and leaves the account remediation to a safety plan with the owner.
Common mistakes
- Reporting the iOS version without the build.
- Taking Accounts3 creation dates at face value on a restored device.
- Treating a TCC grant as proof that the camera or microphone was used.
- Looking for location permissions in TCC.db.
- Attributing MDM-pushed settings to the user.
- Removing a suspicious profile before recording its payloads and install events.