Application security for your industry

Enterprise mobile app security

Otukan protects internal and workforce apps on company-owned and personal phones, keeping work data inside the app whether or not the device is managed.

  • Android
  • iOS
  • Flutter
  • React Native
  • Owned or personal, protected

    Protection travels inside the app, so a contractor's own phone and a company-issued device get the same controls without enrolling either.

  • Work data stays put

    Encrypted storage and copy, share and capture controls keep records inside the work app rather than in personal apps and backups.

  • Clear lines of ownership

    App protection, device administration and identity each have an owner. Otukan makes the boundaries explicit so nothing falls between teams.

How Otukan handles workforce threats

Select a risk to see what Otukan detects, how the work app responds and what your teams receive.

Work data copied out

  1. Detect

    Otukan sees copy, share and open-in actions that move content from protected screens toward other apps.

  2. Respond

    The action is blocked or limited to approved work apps, per your policy.

  3. Report

    Attempted exports reach the security team with app version and platform.

Compromised personal phone

  1. Detect

    Root on Android, jailbreak on iOS, and hooking of the work app are detected at launch and during use.

  2. Respond

    Sensitive features are restricted while the rest of the app stays available.

  3. Report

    Device integrity status accompanies sign-in and each sensitive request.

Unofficial app copy

  1. Detect

    Integrity checks recognise a repackaged or re-signed work app installed outside your distribution channel.

  2. Respond

    The copy refuses to open internal data and directs the user to the approved install.

  3. Report

    Your backend sees that the request came from an unrecognised build.

Lifted session token

  1. Detect

    Attestation shows whether a request carrying a valid token comes from the genuine app instance it was issued to.

  2. Respond

    Unattested requests are refused or sent back for fresh sign-in.

  3. Report

    Attestation results travel to your identity provider and API gateway.

Screens captured

  1. Detect

    Otukan recognises screen recording and mirroring on Android and iOS while sensitive views are open, and screenshots taken on iOS.

  2. Respond

    Sensitive views are hidden during recording and mirroring; on Android they are kept out of screenshots.

  3. Report

    Capture events are recorded per user session, with app version and platform.

Workforce risks and the Otukan controls that meet them

Each card pairs a risk common to internal apps with the Otukan control built for it.

  • Work data controls

    Limits copy, paste, share and open-in actions from the work app, so internal records stay out of personal apps.

  • Leak prevention

    Hides sensitive screens during recording, mirroring and in app-switcher previews, blocks screenshots on Android, and records attempted exports for the security team.

  • Managed app integration

    Accepts policy through the managed app configuration channel your device management tool already uses on Android and iOS.

  • Single sign-on evidence

    Adds app and device integrity evidence to sign-in with your identity provider, so access decisions consider the state of the phone.

  • In-app threat defence

    Detects rooted Android phones, jailbroken iPhones, hooking and, on Android, malicious apps from inside the work app, without an agent on the device.

  • Enterprise access

    Lets internal services admit only protected, attested instances of the work app, alongside a per-app VPN where you use one.

How Otukan works with your workforce apps

  1. List apps and devices

    We inventory your workforce apps, device ownership models and the data each app holds.

  2. Draw the boundaries

    App protection, device administration and identity are assigned to named owners.

  3. Protect each build

    Otukan fits your existing build and release pipeline; signing keys stay with your organisation.

  4. Connect sign-in

    App evidence reaches your identity provider and internal services at access time.

  5. Tune by population

    Policies start in observe mode and tighten separately for company-owned and personal devices.

Free for app publishers

Check your app's exposure

A passive review of your published app by an Otukan engineer. No files, no access to your systems. Findings go by email to the verified publisher.

You finish the request on the next page.

Organisations protect internal apps across employee devices by putting the protection inside the app. Otukan hardens each workforce app, encrypts the work data it stores, controls how that data leaves the app, and sends integrity evidence to your identity provider and internal services at sign-in. The same controls run on company-owned devices and on personal phones, with or without device management. Where you do manage devices, Otukan uses that context rather than replacing it. Each control has its own Android and iOS scope, and fleet administration remains a separate job with its own owner.

Workforce scenarios

The same app often runs on very different devices. Policy should follow the device ownership model, not assume one.

ScenarioWho controls the deviceWhat the app can rely onWhere Otukan focuses
Company-owned, fully managedYour IT teamDevice policy, approved app catalogue, managed configurationApp hardening, integrity evidence at sign-in, capture controls
Personal phone with a work areaThe employee, with a managed work areaAndroid work profile or iOS User Enrollment separates work appsWork data controls, encrypted storage, jailbreak and root signals
Personal phone, unmanagedThe employee or contractor aloneNothing beyond the app itselfThe whole in-app control set, attestation, strict export controls
Shared or frontline deviceA team or shiftKiosk or dedicated-device settingsFast re-authentication, session protection, capture controls

Unmanaged phones deserve the most attention. They are common among contractors and partners, and the work app is the only place your controls can live.

Shared frontline devices need their own treatment. Several people sign in to the same phone during a day, so Otukan protects the session rather than trusting the device owner: sign-in evidence is fresh for each user, sensitive screens are hidden from capture, and work data cached by one user is not left readable for the next.

Control fit

App data protection

Work data at rest is encrypted by the app with keys the platform protects, and Android and iOS each have their own implementation. For platform detail, see Android app data encryption and iOS app data encryption. In use, Otukan limits copy, share and open-in actions from protected screens and hides sensitive views during recording, mirroring and in the app switcher, with screenshots blocked on Android and reported on iOS. Work data controls are covered on work app data controls.

Identity and management interfaces

Otukan adds app and device integrity evidence to sign-in with your identity provider, so access decisions weigh app integrity alongside root, jailbreak and hooking signals from the phone. On managed devices, Otukan accepts policy through the managed app configuration channel that Android and iOS provide to device management tools. Internal services can then admit only protected, attested app instances. For managed configuration in detail, see managed app integration.

Ownership

App protection and fleet administration answer different questions. Keeping them apart avoids gaps and duplicated effort.

ResponsibilityApp protection (Otukan Application Security)Fleet administration (device management)Identity
Is this the genuine, unmodified app?YesNoConsumes the evidence
Is the phone rooted, jailbroken or hooked?Detected from inside the appReported on managed devicesConsumes the evidence
Can work data leave the app?Enforced in the appEnforced on managed work areasNo
Which apps are installed and updated?NoYesNo
Who may sign in, and with which factors?Supplies evidenceSupplies device stateDecides

The same split applies when a signal fires. If the work app detects a hooked process on a personal phone, the app restricts its own sensitive features at once, your identity provider can refuse the next sign-in, and the security team receives the event. Nobody needs to touch the employee’s personal device, and no team waits on another to act.

Otukan also offers device management as a separate product for organisations that want fleet administration from the same company; it is described on mobile device management. Otukan app protection runs just as well alongside an existing device management tool, and the boundaries above hold either way.

Work apps delivered as progressive web apps through the stores are covered on progressive web app protection. For the wider application security picture, return to mobile app security. A workforce app published in the public stores can be reviewed first through a free App Exposure Check.

Common questions

  • Do we need device management to protect a workforce app?

    No. Otukan's application protection is part of the app itself, so it works on unmanaged personal phones, contractors' devices and company-owned devices alike. Where you already manage devices, Otukan uses that context: policy can arrive through managed app configuration, and company-owned devices can be treated differently. Device management and app protection solve different problems and work best side by side.

  • How does this respect employee privacy on personal phones?

    Otukan works inside the work app. It checks the integrity of the app and the conditions it runs in, such as root, jailbreak or hooking, and controls how work data leaves the app. It does not manage personal apps, read personal content or wipe the device. That boundary is easier to explain to employees and works councils than device-wide enrolment.

  • Can we apply different rules to contractors?

    Yes. Policy can be set per device ownership model and per user population, so a contractor on a personal phone can see a narrower set of features than an employee on a company-issued device. Signals start in observe mode, and each rule is enforced only after its effect on genuine users is measured.

On the mobile engineering team?

How protection fits your build, signing and release, platform by platform.

Keep work data safe on any phone

Tell us which workforce apps you run, the platforms and frameworks, the mix of company-owned and personal devices, and the data those apps handle. We never ask for binaries, signing keys, employee data or production credentials.

Or request a technical demo