Black-box or grey-box analysis of your application: binary reverse engineering, local storage and keychain, network communications and pinning, IPC and XPC surfaces, anti-tampering and anti-debug protections. The goal is not to produce a compliance checklist, but the attack scenarios a real adversary would take.
A payment, DRM, anti-fraud or MDM SDK embedded in your application inherits all of its privileges, without you ever seeing its source code. Analysis of the shipped binary — dylib, framework or XCFramework, ARM64e included — to establish what it actually collects, what it exposes, and the risk it transfers to your product.
Deploying an application across an iOS fleet means knowing precisely what it does. Decision-oriented black-box analysis: data actually collected and where it is sent, permissions and entitlements requested, embedded third-party dependencies, robustness of authentication and encryption mechanisms.
Part of my time remains dedicated to research on Apple's own systems, under the Security Bug Bounty: in-depth binary analysis, fuzzing campaigns, dynamic instrumentation, and the development of the tooling that work demands — static analysis of IPSW files, Mach-O binary tracing, IDA Pro extensions.
Support with development and remediation on iOS & macOS remains available as a follow-on to an audit.
Discuss your needs