Signed Apple Profiles
What
With the release of FileWave 15.5, all configuration profiles deployed to Apple devices are now automatically signed. Profile signing enhances security by verifying the authenticity and integrity of the profiles, ensuring they haven’t been altered or tampered with during deployment. Additionally, FileWave allows you to export these signed profiles for use outside of the FileWave environment.
When/Why
When Does Profile Signing Occur?
- Automatic Signing Upon Deployment: Starting from FileWave 15.5, any profile you deploy to Apple devices is signed by default. There’s no need to manually select or trigger the signing process.
Why Is Profile Signing Important?
- Enhanced Security: Automatic signing ensures that all profiles are trusted and have not been modified maliciously.
- Integrity Assurance: Guarantees that the profile content remains unchanged from the point of signing to installation.
- Compliance Requirements: Helps meet organizational security policies and industry compliance standards by providing proof of profile authenticity.
- Flexible Use: The ability to export signed profiles allows you to use them in other tools like Apple Configurator, ensuring consistency across different methods.
How
Deploying Signed Profiles
Since profiles are automatically signed upon deployment in FileWave 15.5 and later, you don’t need to take any extra steps for signing during the deployment process.
Exporting Signed Profiles
If you need to use the signed profiles outside of FileWave—for example, in Apple Configurator—you can export them as signed payloads, by way of Fileset Properties view, as shown below: