Android runtime · 0.1.1
These capabilities describe the first published AppArmorX product: the Android runtime engine. Each future product will publish its own supported scope and validation.
Apply lifecycle guards and reroute supported clipboard, identifier, location and TLS-setup calls in app bytecode and supported dependency JAR/AARs. Unsupported, reflected or dynamically injected calls remain outside this boundary.
Collect root, debugger, hooking, integrity and related signals. CLEAR, DETECTED and UNAVAILABLE separate recorded outcomes from checks that could not run. Signals can be evaded; detection is not universal prevention.
Choose response policies and review explicit overrides. Debuggable builds suppress enforcement against the developer. Hooking response is a separate opt-in; no profile is proof against every attack.
Inspect coverage, manifest findings, policy weakenings and payload evidence. Build-time presence does not establish runtime authenticity. Evaluate the final signed release on the devices you support.
Local protection does not require an AppArmorX account. Optional reports go to infrastructure you configure. Attestation helpers do not provide a complete server-verification or Play Integrity token flow.
No shipped iOS runtime SDK, web SDK, backend verifier or unified operations console is offered today. Source/artifact analysis and deeper engineering context belong to the wider product direction; they are not a publicly available cross-platform suite.