Security Overview | AppDeploy for Apple Business

Security posture in plain language

AppDeploy is built for internal app distribution, so the security model focuses on who can publish apps, who can access them, how Apple Business workflows are connected, and how administrators can review rollout activity.

AppDeploy does not currently claim ISO 27001 or SOC 2 certification. This page separates operational controls from formal third-party assurance so procurement teams can review the product clearly.

Current controls

Product traffic is served over HTTPS, workspace users authenticate through secure sessions, and protected actions check roles and permissions before changes are allowed.

Each organisation has its own workspace boundary. Application controls and database policies help keep customer data separated, while Enterprise audit logs make important administrative and Apple Business events reviewable.

• Role-based workspace access for members, app managers, auditors, organisation admins, and superadmins
• Enterprise audit logs with actor, IP address, action, entity, timestamp, and metadata
• Apple Business credentials and private integration material encrypted at rest
• SCIM provisioning for supported Enterprise identity providers
• SAML/OIDC single sign-on for configured Enterprise workspaces
• Abuse protection on sign-in, registration, public install, and API surfaces
• Operational logging and monitoring for incident investigation
• Stripe-hosted billing flows for paid Business subscriptions
• No full MDM enrollment required for the AppDeploy distribution workflow

Workspace isolation model

Every workspace is attached to an organisation, and protected actions are checked against that workspace boundary.

Database-level safeguards add another layer of protection behind the application controls.

• Workspace-level separation for customer data
• Role and permission checks on protected admin actions
• Database policies for tenant boundary enforcement
• Controlled migration and rollback process for schema changes

What an enterprise review should cover

An enterprise review should walk through the exact rollout paths your users will touch rather than only checking a generic security list.

For most teams, that means reviewing Apple Business token sync, Managed Apple ID matching, Enterprise SCIM provisioning, SAML/OIDC SSO, employee portal access, app upload controls, audit logs, backup expectations, and incident response ownership.

Enterprise readiness roadmap

Upcoming priorities include deeper upload validation and scanning, more install-flow coverage, admin network restrictions, and additional security evidence for larger buyers.

The public security posture will continue to distinguish implemented controls from formal certification work.