Application Security

Protection for Android and iOS apps in your build and release process.
Application Security overview
Get a free app exposure check
Protections

Mobile fraud prevention
Mobile API protection
App threat monitoring
Capabilities

App shielding
Runtime self-protection (RASP)
Code obfuscation
Anti-tampering
Android root detection
iOS jailbreak detection
App attestation
Platforms

Android
iOS
Flutter
React Native
Industries

Banking
Fintech and payments
How it works

Integration
Performance and compatibility
DevSecOps
Device Security

Embedded protection for device makers and controlled device programmes.
Device Security overview
Product

OEM integration
Firmware integrity
Sovereign device security
Programmes

Use cases
Evaluate Device security evaluation guide A repeatable way for an OEM to evaluate device security, model by model.
MDM

Management for enterprise fleets and device makers’ own channels.
MDM overview
Capabilities

Enrollment
Kiosk and dedicated devices
Control

Data sovereignty
OEM device management
Plan MDM requirements checklist The fleet requirements to agree before you compare MDM options.
Resources

Guides, references and research for mobile security teams.
Resources overview
Learn

Knowledge base
Solution guides
Reports
Read

Blog
FAQ
Latest article Better mobile privacy: follow the data through every flow Improve mobile app privacy by tracing each piece of data through a flow, using pickers and coarse values, cleaning diagnostics and testing changed choices.
Company

Who builds Otukan and how we handle security.
Company overview
Company

About
Technology ownership
Partners
Newsroom
Careers
Trust

Responsible disclosure
For security reviewers Security and trust What a security reviewer can check about how Otukan keeps your keys and data with you.

Resources

iOS app security guides

Technical guides for iOS teams: Face ID and Touch ID done right, privacy manifest conflicts, re-signed and modded apps, and modified Frida builds on iOS.

Discuss your app integration

Guides for teams that build, sign and release iOS apps. Each one covers a single iOS mechanism, how attackers work around it and what your app and your server should check. Nothing here is carried over from Android: iOS has its own sandbox, signing model and attestation service, and each guide is written for them.

What the guides cover

Task	Guide
Bind Face ID and Touch ID to a key your server can trust	iOS biometric attributes
Fix privacy manifest conflicts from SDKs and static libraries	iOS privacy manifest conflicts
Stop modded, re-signed copies of your app	Mods that require re-signing
Detect Frida and its modified builds on iOS	Modified Frida builds in iOS apps

Where these fit

For how Otukan protects iOS apps, control by control, see iOS app security. For guides that cover both platforms, browse the knowledge base.

In this collection

Technical guideiOS biometric attributes implementation guide
Implement Face ID and Touch ID on iOS with the right LAPolicy, a Secure Enclave key bound to the current biometric set and a server-signed challenge.
Technical guideHow to prevent conflicts with iOS privacy manifest in iOS apps
Fix the Multiple commands produce PrivacyInfo.xcprivacy error, package SDK manifests in their own bundles and declare required-reason APIs before review.
Technical guideHow to prevent mods hacks that require re signing iOS apps
Stop re-signed iOS app mods from reaching your service: App Attest on the server, Team ID and provisioning checks in the app, and tested signing changes.
Technical guideHow to detect modified Frida builds in iOS apps
Detect modified Frida builds in iOS apps with dyld image checks, inline-hook tests, thread, port and exception-port artefacts, and server-side App Attest.

Discuss your iOS release requirements

Tell us your iOS app framework, build and distribution context, and the protection or release task you need to address. We never ask for binaries, signing keys, credentials or production data.

Discuss your app integration

Or request a technical demo