Skip to content

Application security with engineering context.

AppArmorX is being built around one evidence-backed model: understand the application, evaluate risk, apply policy, and carry the result into delivery.

A shared platform foundation

Source and artifact analysis

Environment-specific analyzers feed shared facts, rules, policy, reporting, and governance. Android and iOS analysis and APK/IPA intake form the mobile foundation. Different targets retain their own evidence and coverage limits.

Engineering intelligence

Foundation in development

Project topology and dependency-health facts add context around findings. Broader build metrics, historical trends, and deeper architecture intelligence remain development directions, not a complete production feature suite.

Developer infrastructure

CLI, policy, and reporting

Canonical JSON and SARIF, finding identity, baselines, and suppressions support repeatable analysis and visible decisions. The core scanning and policy path is deterministic and does not depend on an AI service.

Android runtime engine

Separate pre-release product surface

The Gradle-delivered Android engine adds lifecycle instrumentation, native probes, and a dependency firewall. It is a separate implementation and distribution path. A unified dashboard or automatic correlation with platform scans is not currently offered.

Interpretation and expansion

Evolving foundations and roadmap

Interpretation hints and a starter web analysis lane exist in the local platform. Backend and cloud coverage, autonomous remediation, and AI-assisted interpretation require further work. AI remains an optional layer above structured evidence.