SELinux wasn't added until after Android 4.3. Android's Application Sandboxing primarily relies on Linux's user security model. Each app is assigned a UID and

SELinux wasn't added until after Android 4.3. Android's Application Sandboxing primarily relies on Linux's user security model. Each app is assigned a UID and run in that "user's" context. To quote the official docs: > The sandbox is simple, auditable, and based on decades-old UNIX-style user separation of processes and file permissions. https://source.android.com/security/app-sandbox https://source.android.com/security/app-sandbox SELinux is an extra layer of security that really benefited system services, drivers, and other exploit vectors. All apps remain sandboxed via normal user security on Linux, and then SELinux sprinkled on top for further hardening: > Prior to Android 4.3, these sandboxes were defined by the creation of a unique Linux UID for each application at time of installation. Android 4.3 and later uses SELinux to further define the boundaries of the Android application sandbox. https://source.android.com/security/selinux https://source.android.com/security/selinux