Skip to content

Security & malwareDevice & system

iOS Configuration Profiles and MDM Enrolment

Configuration profiles and MDM on iOS: where installed profiles, profile events and enrolment details live, what they change, and how to spot abuse.

Location
/private/var/containers/Shared/SystemGroup/systemgroup.com.apple.configurationprofiles/Library/ConfigurationProfiles/ (profile stubs, MCProfileEvents.plist, CloudConfigurationDetails.plist and others)
Proves
Which configuration profiles were installed or removed and when, what they contained (root certificates, VPN, proxy, Wi-Fi, restrictions, MDM payloads), and whether the device was enrolled in MDM or Automated Device Enrollment
Timestamps
Property list dates (NSDate, Cocoa time), shown as UTC; install times in MCProfileEvents.plist
Acquisition
Reaches an iTunes / Finder backup (SysSharedContainerDomain-systemgroup.com.apple.configurationprofiles), as MVT's backup modules rely on; a full file system extraction adds the rest of the system group
Retention
Installed profiles remain until removed; MCProfileEvents.plist keeps install and removal events for longer, but not indefinitely
Collection
idevicebackup2, iMazing, Full file system extraction

What it is

A configuration profile is a signed or unsigned XML property list (.mobileconfig) that changes iOS settings in bulk: it can install a root certificate, configure a VPN or a global proxy, add Wi-Fi networks and mail accounts, restrict features, or enrol the device in Mobile Device Management (MDM). Companies and schools use profiles legitimately. Attackers, stalkerware vendors and fraudulent app distributors use them to intercept traffic, sideload apps or keep control of a device.

iOS keeps installed profiles, their payloads and an event history in the system group container of the configuration profiles service. Examining it answers two questions quickly: is this device managed, and has anyone installed something that can intercept or control it?

Where it lives

All paths are under /private/var/containers/Shared/SystemGroup/systemgroup.com.apple.configurationprofiles/Library/ConfigurationProfiles/:

FileContentNotes
profile-* files (.stub)Installed profiles, one per file (plist)Full payloads; some wrap the profile in an OTAProfileStub key with signer certificates
MCProfileEvents.plistInstall and removal events per profile identifierWith dates and the process that performed them
CloudConfigurationDetails.plistAutomated Device Enrollment (DEP) detailsOrganisation name, MDM server, whether enrolment is mandatory
ProfileTruth.plist, PayloadManifest.plist, EffectiveUserSettings.plistProfile list, payload inventory and resulting settingsNames and presence vary by release

In a backup the same files sit in the domain SysSharedContainerDomain-systemgroup.com.apple.configurationprofiles, relative path Library/ConfigurationProfiles/. Resolve them through Manifest.db.

What it proves

  • Which profiles are installed, with identifier, display name, organisation, signer and payloads.
  • When each profile was installed or removed, and by which process (user in Settings, MDM, Apple Configurator).
  • Whether the device is supervised or enrolled in MDM, and by which organisation.
  • The settings imposed: trusted root certificates, VPN and proxy configurations, restrictions, managed apps and domains.

It does not show traffic that went through a VPN or proxy. It shows that the capability existed.

Key fields

File / keyMeaning
stub: PayloadIdentifier, PayloadDisplayName, PayloadOrganizationProfile identity
stub: PayloadContent[] with PayloadTypePayloads, e.g. com.apple.security.root, com.apple.vpn.managed, com.apple.proxy.http.global, com.apple.mdm, com.apple.wifi.managed
stub: InstallDate (where present)Installation time
stub: signer certificatesWho signed the profile, if signed
MCProfileEvents.plistPer profile identifier: operation (install, remove), timestamp, process
CloudConfigurationDetails.plist: OrganizationName, ConfigurationURL, IsMandatory, IsSupervisedAutomated enrolment details

Keys vary by release and by the tool that generated the profile. Dump each plist rather than relying on a fixed list.

Timestamps

Dates are property list date values, stored as Cocoa time and shown in UTC:

plutil -p MCProfileEvents.plist
plutil -convert xml1 -o - profile-<hash>.stub | grep -A1 -E 'PayloadType|InstallDate|PayloadOrganization'

Retention

Installed profiles remain until removed by the user, the MDM server or an erase. MCProfileEvents.plist can keep events for profiles that are no longer installed, which is valuable when a suspect removed a profile before seizure. How long events are kept is not documented.

Collection

  • A standard backup includes the configuration profiles domain. MVT's check-backup extracts it.
  • On a live, unlocked device, Settings > General > VPN & Device Management shows installed profiles. Photograph it; do not remove anything.
  • A full file system extraction adds the complete system group container and related MDM state.

Parsing

  • MVT has two backup modules: ConfigurationProfiles (full payloads, with alerts on profile UUIDs listed in indicator files and on payload types linked to past abuse, such as notification settings) and ProfileEvents (install and removal events).
  • iLEAPP and commercial suites summarise profiles and MDM state.
  • plutil for manual review of each file.

Investigator tips

  • A root certificate payload combined with a VPN or global proxy allows traffic interception. On a personal device, that combination needs an explanation.
  • Compare the MDM organisation with the owner's employer. An unknown organisation or a consumer "parental control" service can indicate covert management.
  • MDM can push TCC decisions, Wi-Fi networks and managed apps. Check auth_reason values and managed app lists before attributing a setting to the user.
  • Removal events shortly before seizure are significant. Correlate with shutdown.log reboots and the device and accounts guide workflow.

See also