# The screen is an attack surface too.

> The IVI engine assesses Android infotainment units over ADB. It performs recon of packages, permissions, exposed components, pullable files and SELinux posture, runs static analysis of APKs (manifest flags and secret scanning), and can run functional tests with screenshots and live logcat streaming. Findings are grouped by severity with per-finding remediation and flow into the shared fix plan.

AutoST checks Android infotainment over ADB: dangerous permissions, exposed components, pullable files, SELinux posture and APK static analysis, with per-finding fixes.

Source: https://auto-st.com/ivi-security-testing

Modern infotainment runs Android, with apps, permissions and services like any device. AutoST connects over ADB and runs a full hardening assessment of the head unit.

## A full head-unit hardening check

### Permissions & components

Dangerous permissions granted to shell, exposed activities and services, and the SELinux posture of the device.

### Pullable files

System and app files that can be pulled off the device, a common path to secrets and sensitive data.

### APK static analysis

Manifest flags and secret scanning across installed APKs, to catch debuggable builds and hard-coded credentials.

### Functional & logcat

Functional tests with screenshots and live logcat streaming, so you see the device as it runs.

## FAQ

**How does AutoST connect to the IVI?**

Over ADB, the Android Debug Bridge, to a head unit or an emulator. From there it enumerates packages, permissions, components and files.

**Does it just list issues?**

No. Each finding comes with remediation, and all of them flow into the shared fix plan alongside the UDS, DoIP and SOME/IP findings.

---
AutoST by Zyberum. Canonical page: https://auto-st.com/ivi-security-testing
