تحسينات أمنية

يعمل Android باستمرار على تحسين قدراته وعروضه الأمنية. راجع قوائم التحسينات حسب الإصدار في شريط التنقل الأيمن.

أندرويد 14

Every Android release includes dozens of security enhancements to protect users. Here are some of the major security enhancements available in Android 14:

  • Hardware-assisted AddressSanitizer (HWASan), introduced in Android 10, is a memory error detection tool similar to AddressSanitizer. Android 14 brings significant improvements to HWASan. Learn how it helps prevent bugs from making it into Android releases, HWAddressSanitizer
  • In Android 14, starting with apps that share location data with third-parties, the system runtime permission dialog now includes a clickable section that highlights the app's data-sharing practices, including information such as why an app may decide to share data with third parties.
  • Android 12 introduced an option to disable 2G support at the modem level, which protects users from the inherent security risk from 2G's obsolete security model. Recognizing how critical disabling 2G could be for enterprise customers, Android 14 enables this security feature in Android Enterprise, introducing support for IT admins to restrict the ability of a managed device to downgrade to 2G connectivity.
  • Added support to reject null-ciphered cellular connections, ensuring that circuit-switched voice and SMS traffic is always encrypted and protected from passive over-the-air interception. Learn more about Android's program to harden cellular connectivity.
  • Added support for multiple IMEIs
  • Since Android 14, AES-HCTR2 is the preferred mode of filenames encryption for devices with accelerated cryptography instructions.
  • Cellular connectivity
  • Documentation added for Android Safety Center
  • If your app targets Android 14 and uses Dynamic Code Loading (DCL), all dynamically-loaded files must be marked as read-only. Otherwise, the system throws an exception. We recommend that apps avoid dynamically loading code whenever possible, as doing so greatly increases the risk that an app can be compromised by code injection or code tampering.

Check out our full AOSP release notes and the Android Developer features and changes list.

أندرويد 13

Every Android release includes dozens of security enhancements to protect users. Here are some of the major security enhancements available in Android 13:

  • Android 13 adds multi-document presentation support. This new Presentation Session interface enables an application to do a multi-document presentation, something which isn't possible with the existing API. For further information, refer to Identity Credential
  • In Android 13, intents originating from external apps are delivered to an exported component if and only if the intents match their declared intent-filter elements.
  • Open Mobile API (OMAPI) is a standard API used to communicate with a device's Secure Element. Before Android 13, only applications and framework modules had access to this interface. By converting it to a vendor stable interface, HAL modules are also capable of communicating with the secure elements through the OMAPI service. For more information, see OMAPI Vendor Stable Interface.
  • As of Android 13-QPR, shared UIDs are deprecated. Users of Android 13 or higher should put the line `android:sharedUserMaxSdkVersion="32"` in their manifest. This entry prevents new users from getting a shared UID. For further information on UIDs, see Application signing.
  • Android 13 added support Keystore symmetric cryptographic primitives such as AES (Advanced Encryption Standard), HMAC (Keyed-Hash Message Authentication Code), and asymmetric cryptographic algorithms (including Elliptic Curve, RSA2048, RSA4096, and Curve 25519)
  • Android 13 (API level 33) and higher supports a runtime permission for sending non-exempt notifications from an app. This gives users control over which permission notifications they see.
  • Added per-use prompt for apps requesting access to all device logs, giving users the ability to allow or deny access.
  • introduced the Android Virtualization Framework (AVF), which brings together different hypervisors under one framework with standardized APIs. It provides secure and private execution environments for executing workloads isolated by hypervisor.
  • Introduced APK signature scheme v3.1 All new key rotations that use apksigner will use the v3.1 signature scheme by default to target rotation for Android 13 and higher.

Check out our full AOSP release notes and the Android Developer features and changes list.

أندرويد 12

Every Android release includes dozens of security enhancements to protect users. Here are some of the major security enhancements available in Android 12:

  • Android 12 introduces the BiometricManager.Strings API, which provides localized strings for apps that use BiometricPrompt for authentication. These strings are intended to be device-aware and provide more specificity about which authentication type(s) may be used. Android 12 also includes support for under-display fingerprint sensors
  • Support added for under-display fingerprint sensors
  • Introduction of the Fingerprint Android Interface Definition Language (AIDL)
  • Support for new Face AIDL
  • Introduction of Rust as a language for platform development
  • The option for users to grant access only to their approximate location added
  • Added Privacy indicators on the status bar when an app is using the camera or microphone
  • Android's Private Compute Core (PCC)
  • Added an option to disable 2G support

أندرويد 11

يتضمن كل إصدار من إصدارات Android العشرات من التحسينات الأمنية لحماية المستخدمين. للحصول على قائمة ببعض التحسينات الأمنية الرئيسية المتوفرة في Android 11 ، راجع ملاحظات إصدار Android .

أندرويد 10

Every Android release includes dozens of security enhancements to protect users. Android 10 includes several security and privacy enhancements. See the Android 10 release notes for a complete list of changes in Android 10.

Security

BoundsSanitizer

Android 10 deploys BoundsSanitizer (BoundSan) in Bluetooth and codecs. BoundSan uses UBSan's bounds sanitizer. This mitigation is enabled on a per-module level. It helps keep critical components of Android secure and shouldn't be disabled. BoundSan is enabled in the following codecs:

  • libFLAC
  • libavcdec
  • libavcenc
  • libhevcdec
  • libmpeg2
  • libopus
  • libvpx
  • libspeexresampler
  • libvorbisidec
  • libaac
  • libxaac

Execute-only memory

By default, executable code sections for AArch64 system binaries are marked execute-only (nonreadable) as a hardening mitigation against just-in-time code reuse attacks. Code that mixes data and code together and code that purposefully inspects these sections (without first remapping the memory segments as readable) no longer functions. Apps with a target SDK of Android 10 (API level 29 or higher) are impacted if the app attempts to read code sections of execute-only memory (XOM) enabled system libraries in memory without first marking the section as readable.

Extended access

Trust agents, the underlying mechanism used by tertiary authentication mechanisms such as Smart Lock, can only extend unlock in Android 10. Trust agents can no longer unlock a locked device and can only keep a device unlocked for a maximum of four hours.

Face authentication

Face authentication allows users to unlock their device simply by looking at the front of their device. Android 10 adds support for a new face authentication stack that can securely process camera frames, preserving security and privacy during face authentication on supported hardware. Android 10 also provides an easy way for security-compliant implementations to enable app integration for transactions such as online banking or other services.

Integer Overflow Sanitization

Android 10 enables Integer Overflow Sanitization (IntSan) in software codecs. Ensure that playback performance is acceptable for any codecs that aren't supported in the device's hardware. IntSan is enabled in the following codecs:

  • libFLAC
  • libavcdec
  • libavcenc
  • libhevcdec
  • libmpeg2
  • libopus
  • libvpx
  • libspeexresampler
  • libvorbisidec

Modular system components

Android 10 modularizes some Android system components and enables them to be updated outside of the normal Android release cycle. Some modules include:

OEMCrypto

Android 10 uses OEMCrypto API version 15.

Scudo

Scudo is a dynamic user-mode memory allocator designed to be more resilient against heap-related vulnerabilities. It provides the standard C allocation and deallocation primitives, as well as the C++ primitives.

ShadowCallStack

ShadowCallStack (SCS) is an LLVM instrumentation mode that protects against return address overwrites (like stack buffer overflows) by saving a function's return address to a separately allocated ShadowCallStack instance in the function prolog of nonleaf functions and loading the return address from the ShadowCallStack instance in the function epilog.

WPA3 and Wi-Fi Enhanced Open

Android 10 adds support for the Wi-Fi Protected Access 3 (WPA3) and Wi-Fi Enhanced Open security standards to provide better privacy and robustness against known attacks.

Privacy

App access when targeting Android 9 or lower

If your app runs on Android 10 or higher but targets Android 9 (API level 28) or lower, the platform applies the following behavior:

  • If your app declares a <uses-permission> element for either ACCESS_FINE_LOCATION or ACCESS_COARSE_LOCATION, the system automatically adds a <uses-permission> element for ACCESS_BACKGROUND_LOCATION during installation.
  • If your app requests either ACCESS_FINE_LOCATION or ACCESS_COARSE_LOCATION, the system automatically adds ACCESS_BACKGROUND_LOCATION to the request.

Background activity restrictions

Starting in Android 10, the system places restrictions on starting activities from the background. This behavior change helps minimize interruptions for the user and keeps the user more in control of what's shown on their screen. As long as your app starts activities as a direct result of user interaction, your app most likely isn't affected by these restrictions.
To learn more about the recommended alternative to starting activities from the background, see the guide on how to alert users of time-sensitive events in your app.

Camera metadata

Android 10 changes the breadth of information that the getCameraCharacteristics() method returns by default. In particular, your app must have the CAMERA permission in order to access potentially device-specific metadata that is included in this method's return value.
To learn more about these changes, see the section about camera fields that require permission.

Clipboard data

Unless your app is the default input method editor (IME) or is the app that currently has focus, your app cannot access clipboard data on Android 10 or higher.

Device location

To support the additional control that users have over an app's access to location information, Android 10 introduces the ACCESS_BACKGROUND_LOCATION permission.
Unlike the ACCESS_FINE_LOCATION and ACCESS_COARSE_LOCATION permissions, the ACCESS_BACKGROUND_LOCATION permission only affects an app's access to location when it runs in the background. An app is considered to be accessing location in the background unless one of the following conditions is satisfied:

  • An activity belonging to the app is visible.
  • The app is running a foreground service that has declared a foreground service type of location.
    To declare the foreground service type for a service in your app, set your app's targetSdkVersion or compileSdkVersion to 29 or higher. Learn more about how foreground services can continue user-initiated actions that require access to location.

External storage

By default, apps targeting Android 10 and higher are given scoped access into external storage, or scoped storage. Such apps can see the following types of files within an external storage device without needing to request any storage-related user permissions:

To learn more about scoped storage, as well as how to share, access, and modify files that are saved on external storage devices, see the guides on how to manage files in external storage and access and modify media files.

MAC address randomization

On devices that run Android 10 or higher, the system transmits randomized MAC addresses by default.
If your app handles an enterprise use case, the platform provides APIs for several operations related to MAC addresses:

  • Obtain randomized MAC address: Device owner apps and profile owner apps can retrieve the randomized MAC address assigned to a specific network by calling getRandomizedMacAddress().
  • Obtain actual, factory MAC address: Device owner apps can retrieve a device's actual hardware MAC address by calling getWifiMacAddress(). This method is useful for tracking fleets of devices.

Non-resettable device identifiers

Starting in Android 10, apps must have the READ_PRIVILEGED_PHONE_STATE privileged permission in order to access the device's non-resettable identifiers, which include both IMEI and serial number.

If your app doesn't have the permission and you try asking for information about non-resettable identifiers anyway, the platform's response varies based on target SDK version:

  • If your app targets Android 10 or higher, a SecurityException occurs.
  • If your app targets Android 9 (API level 28) or lower, the method returns null or placeholder data if the app has the READ_PHONE_STATE permission. Otherwise, a SecurityException occurs.

Physical activity recognition

Android 10 introduces the android.permission.ACTIVITY_RECOGNITION runtime permission for apps that need to detect the user's step count or classify the user's physical activity, such as walking, biking, or moving in a vehicle. This is designed to give users visibility of how device sensor data is used in Settings.
Some libraries within Google Play services, such as the Activity Recognition API and the Google Fit API, don't provide results unless the user has granted your app this permission.
The only built-in sensors on the device that require you to declare this permission are the step counter and step detector sensors.
If your app targets Android 9 (API level 28) or lower, the system auto-grants the android.permission.ACTIVITY_RECOGNITION permission to your app, as needed, if your app satisfies each of the following conditions:

  • The manifest file includes the com.google.android.gms.permission.ACTIVITY_RECOGNITION permission.
  • The manifest file doesn't include the android.permission.ACTIVITY_RECOGNITION permission.

If the system-auto grants the android.permission.ACTIVITY_RECOGNITION permission, your app retains the permission after you update your app to target Android 10. However, the user can revoke this permission at any time in system settings.

/proc/net filesystem restrictions

On devices that run Android 10 or higher, apps cannot access /proc/net, which includes information about a device's network state. Apps that need access to this information, such as VPNs, should use the NetworkStatsManager or ConnectivityManager class.

Permission groups removed from UI

As of Android 10, apps cannot look up how permissions are grouped in the UI.

Removal of contacts affinity

Starting in Android 10, the platform doesn't keep track of contacts affinity information. As a result, if your app conducts a search on the user's contacts, the results aren't ordered by frequency of interaction.
The guide about ContactsProvider contains a notice describing the specific fields and methods that are obsolete on all devices starting in Android 10.

Restricted access to screen contents

To protect users' screen contents, Android 10 prevents silent access to the device's screen contents by changing the scope of the READ_FRAME_BUFFER, CAPTURE_VIDEO_OUTPUT, and CAPTURE_SECURE_VIDEO_OUTPUT permissions. As of Android 10, these permissions are signature-access only.
Apps that need to access the device's screen contents should use the MediaProjection API, which displays a prompt asking the user to provide consent.

USB device serial number

If your app targets Android 10 or higher, your app cannot read the serial number until the user has granted your app permission to access the USB device or accessory.
To learn more about working with USB devices, see the guide on how to configure USB hosts.

Wi-Fi

Apps targeting Android 10 or higher cannot enable or disable Wi-Fi. The WifiManager.setWifiEnabled() method always returns false.
If you need to prompt users to enable and disable Wi-Fi, use a settings panel.

Restrictions on direct access to configured Wi-Fi networks

To protect user privacy, manual configuration of the list of Wi-Fi networks is restricted to system apps and device policy controllers (DPCs). A given DPC can be either the device owner or the profile owner.
If your app targets Android 10 or higher, and it isn't a system app or a DPC, then the following methods don't return useful data:

أندرويد 9

يتضمن كل إصدار من إصدارات Android العشرات من التحسينات الأمنية لحماية المستخدمين. للحصول على قائمة ببعض التحسينات الأمنية الرئيسية المتوفرة في Android 9 ، راجع ملاحظات إصدار Android .

أندرويد 8

Every Android release includes dozens of security enhancements to protect users. Here are some of the major security enhancements available in Android 8.0:

  • Encryption. Added support to evict key in work profile.
  • Verified Boot. Added Android Verified Boot (AVB). Verified Boot codebase supporting rollback protection for use in boot loaders added to AOSP. Recommend bootloader support for rollback protection for the HLOS. Recommend boot loaders can only be unlocked by user physically interacting with the device.
  • Lock screen. Added support for using tamper-resistant hardware to verify lock screen credential.
  • KeyStore. Required key attestation for all devices that ship with Android 8.0+. Added ID attestation support to improve Zero Touch Enrollment.
  • Sandboxing. More tightly sandboxed many components using Project Treble's standard interface between framework and device-specific components. Applied seccomp filtering to all untrusted apps to reduce the kernel's attack surface. WebView is now run in an isolated process with very limited access to the rest of the system.
  • Kernel hardening. Implemented hardened usercopy, PAN emulation, read-only after init, and KASLR.
  • Userspace hardening. Implemented CFI for the media stack. App overlays can no longer cover system-critical windows and users have a way to dismiss them.
  • Streaming OS update. Enabled updates on devices that are are low on disk space.
  • Install unknown apps. Users must grant permission to install apps from a source that isn't a first-party app store.
  • Privacy. Android ID (SSAID) has a different value for each app and each user on the device. For web browser apps, Widevine Client ID returns a different value for each app package name and web origin. net.hostname is now empty and the dhcp client no longer sends a hostname. android.os.Build.SERIAL has been replaced with the Build.SERIAL API which is protected behind a user-controlled permission. Improved MAC address randomization in some chipsets.

أندرويد 7

Every Android release includes dozens of security enhancements to protect users. Here are some of the major security enhancements available in Android 7.0:

  • File-based encryption. Encrypting at the file level, instead of encrypting the entire storage area as a single unit, better isolates and protects individual users and profiles (such as personal and work) on a device.
  • Direct Boot. Enabled by file-based encryption, Direct Boot allows certain apps such as alarm clock and accessibility features to run when device is powered on but not unlocked.
  • Verified Boot. Verified Boot is now strictly enforced to prevent compromised devices from booting; it supports error correction to improve reliability against non-malicious data corruption.
  • SELinux. Updated SELinux configuration and increased seccomp coverage further locks down the application sandbox and reduces attack surface.
  • Library load-order randomization and improved ASLR. Increased randomness makes some code-reuse attacks less reliable.
  • Kernel hardening. Added additional memory protection for newer kernels by marking portions of kernel memory as read-only, restricting kernel access to userspace addresses and further reducing the existing attack surface.
  • APK signature scheme v2. Introduced a whole-file signature scheme that improves verification speed and strengthens integrity guarantees.
  • Trusted CA store. To make it easier for apps to control access to their secure network traffic, user-installed certificate authorities and those installed through Device Admin APIs are no longer trusted by default for apps targeting API Level 24+. Additionally, all new Android devices must ship with the same trusted CA store.
  • Network Security Config. Configure network security and TLS through a declarative configuration file.

أندرويد 6

يتضمن كل إصدار من إصدارات Android العشرات من التحسينات الأمنية لحماية المستخدمين. فيما يلي بعض التحسينات الأمنية الرئيسية المتوفرة في Android 6.0:

  • أذونات وقت التشغيل . تطلب التطبيقات أذونات في وقت التشغيل بدلاً من منحها في وقت تثبيت التطبيق. يمكن للمستخدمين تبديل الأذونات وإيقاف تشغيلها لكل من تطبيقات M و pre-M.
  • تم التحقق من التمهيد . يتم إجراء مجموعة من فحوصات التشفير لبرامج النظام قبل التنفيذ للتأكد من أن الهاتف يتمتع بصحة جيدة من أداة تحميل التشغيل وصولاً إلى نظام التشغيل.
  • الأمان المعزول عن الأجهزة . طبقة تجريد جديدة للأجهزة (HAL) مستخدمة بواسطة Fingerprint API و Lockscreen و Device Encryption و Client Certificates لحماية المفاتيح من اختراق kernel و / أو الهجمات المادية المحلية
  • بصمات الأصابع . يمكن الآن فتح قفل الأجهزة بلمسة واحدة فقط. يمكن للمطورين أيضًا الاستفادة من واجهات برمجة التطبيقات الجديدة لاستخدام بصمات الأصابع لقفل وفتح مفاتيح التشفير.
  • اعتماد بطاقة SD . يمكن اعتماد الوسائط القابلة للإزالة على جهاز وتوسيع مساحة التخزين المتاحة لبيانات التطبيق المحلية والصور ومقاطع الفيديو وما إلى ذلك ، ولكن تظل محمية بواسطة تشفير على مستوى الكتلة.
  • مسح حركة النص . يمكن للمطورين استخدام StrictMode جديد للتأكد من أن تطبيقهم لا يستخدم نصًا واضحًا.
  • تصلب النظام . تصلب النظام من خلال السياسات التي تفرضها SELinux. يوفر هذا عزلًا أفضل بين المستخدمين ، وتصفية IOCTL ، وتقليل تهديد الخدمات المكشوفة ، وزيادة تشديد نطاقات SELinux ، والوصول المحدود للغاية / proc.
  • التحكم في الوصول عبر USB: يجب على المستخدمين التأكيد للسماح بوصول USB إلى الملفات أو التخزين أو الوظائف الأخرى على الهاتف. الافتراضي هو المسؤول الآن فقط مع الوصول إلى مساحة التخزين التي تتطلب موافقة صريحة من المستخدم.

أندرويد 5

5.0

Every Android release includes dozens of security enhancements to protect users. Here are some of the major security enhancements available in Android 5.0:

  • Encrypted by default. On devices that ship with L out-of-the-box, full disk encryption is enabled by default to improve protection of data on lost or stolen devices. Devices that update to L can be encrypted in Settings > Security.
  • Improved full disk encryption. The user password is protected against brute-force attacks using scrypt and, where available, the key is bound to the hardware keystore to prevent off-device attacks. As always, the Android screen lock secret and the device encryption key are not sent off the device or exposed to any application.
  • Android sandbox reinforced with SELinux. Android now requires SELinux in enforcing mode for all domains. SELinux is a mandatory access control (MAC) system in the Linux kernel used to augment the existing discretionary access control (DAC) security model. This new layer provides additional protection against potential security vulnerabilities.
  • Smart Lock. Android now includes trustlets that provide more flexibility for unlocking devices. For example, trustlets can allow devices to be unlocked automatically when close to another trusted device (via NFC, Bluetooth) or being used by someone with a trusted face.
  • Multi user, restricted profile, and guest modes for phones & tablets. Android now provides for multiple users on phones and includes a guest mode that can be used to provide easy temporary access to your device without granting access to your data and apps.
  • Updates to WebView without OTA. WebView can now be updated independent of the framework and without a system OTA. This will allow for faster response to potential security issues in WebView.
  • Updated cryptography for HTTPS and TLS/SSL. TLSv1.2 and TLSv1.1 is now enabled, Forward Secrecy is now preferred, AES-GCM is now enabled, and weak cipher suites (MD5, 3DES, and export cipher suites) are now disabled. See https://developer.android.com/reference/javax/net/ssl/SSLSocket.html for more details.
  • non-PIE linker support removed. Android now requires all dynamically linked executables to support PIE (position-independent executables). This enhances Android’s address space layout randomization (ASLR) implementation.
  • FORTIFY_SOURCE improvements. The following libc functions now implement FORTIFY_SOURCE protections: stpcpy(), stpncpy(), read(), recvfrom(), FD_CLR(), FD_SET(), and FD_ISSET(). This provides protection against memory-corruption vulnerabilities involving those functions.
  • Security Fixes. Android 5.0 also includes fixes for Android-specific vulnerabilities. Information about these vulnerabilities has been provided to Open Handset Alliance members, and fixes are available in Android Open Source Project. To improve security, some devices with earlier versions of Android may also include these fixes.

أندرويد 4 وأقل

يتضمن كل إصدار من إصدارات Android العشرات من التحسينات الأمنية لحماية المستخدمين. فيما يلي بعض التحسينات الأمنية المتوفرة في Android 4.4:

  • وضع الحماية لنظام Android معزز بـ SELinux. يستخدم Android الآن SELinux في وضع الفرض. SELinux هو نظام تحكم بالوصول (MAC) إلزامي في Linux kernel يستخدم لزيادة نموذج الأمان القائم على التحكم في الوصول التقديري (DAC). يوفر هذا حماية إضافية ضد الثغرات الأمنية المحتملة.
  • لكل مستخدم VPN. على الأجهزة متعددة المستخدمين ، يتم الآن تطبيق شبكات VPN لكل مستخدم. يمكن أن يسمح هذا للمستخدم بتوجيه كل حركة مرور الشبكة عبر VPN دون التأثير على المستخدمين الآخرين على الجهاز.
  • دعم مزود ECDSA في AndroidKeyStore. لدى Android الآن مزود مخزن مفاتيح يسمح باستخدام خوارزميات ECDSA و DSA.
  • تحذيرات مراقبة الجهاز. يوفر Android للمستخدمين تحذيرًا إذا تمت إضافة أي شهادة إلى مخزن شهادات الجهاز مما قد يسمح بمراقبة حركة مرور الشبكة المشفرة.
  • FORTIFY_SOURCE. يدعم Android الآن المستوى 2 من FORTIFY_SOURCE ، ويتم تجميع جميع التعليمات البرمجية باستخدام وسائل الحماية هذه. تم تحسين FORTIFY_SOURCE للعمل مع clang.
  • تثبيت الشهادة. يكتشف Android 4.4 ويمنع استخدام شهادات Google الاحتيالية المستخدمة في اتصالات SSL / TLS الآمنة.
  • إصلاحات أمنية. يتضمن Android 4.4 أيضًا إصلاحات للثغرات الأمنية الخاصة بنظام Android. تم توفير معلومات حول هذه الثغرات الأمنية لأعضاء Open Handset Alliance والإصلاحات متوفرة في مشروع Android Open Source Project. لتحسين الأمان ، قد تتضمن بعض الأجهزة التي تعمل بإصدارات سابقة من Android أيضًا هذه الإصلاحات.

يتضمن كل إصدار من إصدارات Android العشرات من التحسينات الأمنية لحماية المستخدمين. فيما يلي بعض التحسينات الأمنية المتوفرة في Android 4.3:

  • صندوق حماية Android معزز بـ SELinux. يعمل هذا الإصدار على تعزيز وضع الحماية لنظام Android باستخدام نظام SELinux الإلزامي للتحكم في الوصول (MAC) في Linux kernel. إن تعزيز SELinux غير مرئي للمستخدمين والمطورين، ويضيف المتانة إلى نموذج أمان Android الحالي مع الحفاظ على التوافق مع التطبيقات الحالية. لضمان استمرار التوافق، يسمح هذا الإصدار باستخدام SELinux في وضع متساهل. يقوم هذا الوضع بتسجيل أي انتهاكات للسياسة، ولكنه لن يؤدي إلى تعطيل التطبيقات أو التأثير على سلوك النظام.
  • لا توجد برامج setuid/setgid. تمت إضافة دعم لقدرات نظام الملفات إلى ملفات نظام Android وإزالة جميع برامج setuid/setguid. وهذا يقلل من سطح هجوم الجذر واحتمال وجود ثغرات أمنية محتملة.
  • مصادقة بنك التنمية الآسيوي. منذ Android 4.2.2، تتم مصادقة الاتصالات بـ ADB باستخدام زوج مفاتيح RSA. وهذا يمنع الاستخدام غير المصرح به لـ ADB حيث يكون للمهاجم حق الوصول الفعلي إلى الجهاز.
  • تقييد Setuid من تطبيقات Android. تم الآن تثبيت قسم /system على nosuid للعمليات التي ولدت الزيجوت، مما يمنع تطبيقات Android من تنفيذ برامج setuid. وهذا يقلل من سطح هجوم الجذر واحتمال وجود ثغرات أمنية محتملة.
  • حدود القدرة. يستخدم Android zygote وADB الآن prctl(PR_CAPBSET_DROP) لإسقاط الإمكانات غير الضرورية قبل تنفيذ التطبيقات. وهذا يمنع تطبيقات Android والتطبيقات التي يتم تشغيلها من الغلاف من الحصول على إمكانيات مميزة.
  • مزود AndroidKeyStore. يمتلك Android الآن مزودًا لتخزين المفاتيح يسمح للتطبيقات بإنشاء مفاتيح استخدام حصرية. يوفر هذا للتطبيقات واجهة برمجة التطبيقات (API) لإنشاء أو تخزين مفاتيح خاصة لا يمكن استخدامها بواسطة تطبيقات أخرى.
  • KeyChain هي خوارزمية BoundKey. توفر Keychain API الآن طريقة (isBoundKeyType) تسمح للتطبيقات بالتأكد من أن المفاتيح على مستوى النظام مرتبطة بجذر ثقة الجهاز الخاص بالجهاز. يوفر هذا مكانًا لإنشاء أو تخزين المفاتيح الخاصة التي لا يمكن تصديرها خارج الجهاز، حتى في حالة اختراق الجذر.
  • NO_NEW_PRIVS. يستخدم Android zygote الآن prctl(PR_SET_NO_NEW_PRIVS) لمنع إضافة امتيازات جديدة قبل تنفيذ رمز التطبيق. وهذا يمنع تطبيقات Android من تنفيذ العمليات التي يمكن أن ترفع الامتيازات عبر execve. (يتطلب هذا إصدار Linux kernel 3.5 أو أحدث).
  • تحسينات FORTIFY_SOURCE. تم تمكين FORTIFY_SOURCE على Android x86 وMIPS ومكالمات strchr() وstrrchr() وstrlen() وumask() المحصنة. يمكن أن يكشف هذا عن ثغرات أمنية محتملة في تلف الذاكرة أو ثوابت السلسلة غير المنتهية.
  • حماية النقل. تم تمكين عمليات نقل القراءة فقط (relro) للملفات التنفيذية المرتبطة بشكل ثابت وإزالة جميع عمليات نقل النص في كود Android. وهذا يوفر دفاعًا متعمقًا ضد الثغرات الأمنية المحتملة لتلف الذاكرة.
  • تحسين الانتروبياميكسر. يقوم EntropyMixer الآن بكتابة الإنتروبيا عند إيقاف التشغيل/إعادة التشغيل، بالإضافة إلى الخلط الدوري. يسمح هذا بالاحتفاظ بكل الإنتروبيا التي تم إنشاؤها أثناء تشغيل الأجهزة، وهو مفيد بشكل خاص للأجهزة التي يتم إعادة تشغيلها مباشرة بعد التزويد.
  • إصلاحات الأمان. يتضمن Android 4.3 أيضًا إصلاحات للثغرات الأمنية الخاصة بنظام Android. تم توفير معلومات حول نقاط الضعف هذه لأعضاء Open Handset Alliance وتتوفر الإصلاحات في Android Open Source Project. لتحسين الأمان، قد تتضمن بعض الأجهزة التي تحتوي على إصدارات سابقة من Android هذه الإصلاحات أيضًا.

Android provides a multi-layered security model described in the Android Security Overview. Each update to Android includes dozens of security enhancements to protect users. The following are some of the security enhancements introduced in Android 4.2:

  • Application verification - Users can choose to enable “Verify Apps" and have applications screened by an application verifier, prior to installation. App verification can alert the user if they try to install an app that might be harmful; if an application is especially bad, it can block installation.
  • More control of premium SMS - Android will provide a notification if an application attempts to send SMS to a short code that uses premium services which might cause additional charges. The user can choose whether to allow the application to send the message or block it.
  • Always-on VPN - VPN can be configured so that applications will not have access to the network until a VPN connection is established. This prevents applications from sending data across other networks.
  • Certificate Pinning - The Android core libraries now support certificate pinning. Pinned domains will receive a certificate validation failure if the certificate does not chain to a set of expected certificates. This protects against possible compromise of Certificate Authorities.
  • Improved display of Android permissions - Permissions have been organized into groups that are more easily understood by users. During review of the permissions, the user can click on the permission to see more detailed information about the permission.
  • installd hardening - The installd daemon does not run as the root user, reducing potential attack surface for root privilege escalation.
  • init script hardening - init scripts now apply O_NOFOLLOW semantics to prevent symlink related attacks.
  • FORTIFY_SOURCE - Android now implements FORTIFY_SOURCE. This is used by system libraries and applications to prevent memory corruption.
  • ContentProvider default configuration - Applications which target API level 17 will have "export" set to "false" by default for each Content Provider, reducing default attack surface for applications.
  • Cryptography - Modified the default implementations of SecureRandom and Cipher.RSA to use OpenSSL. Added SSL Socket support for TLSv1.1 and TLSv1.2 using OpenSSL 1.0.1
  • Security Fixes - Upgraded open source libraries with security fixes include WebKit, libpng, OpenSSL, and LibXML. Android 4.2 also includes fixes for Android-specific vulnerabilities. Information about these vulnerabilities has been provided to Open Handset Alliance members and fixes are available in Android Open Source Project. To improve security, some devices with earlier versions of Android may also include these fixes.

يوفر Android نموذج أمان متعدد الطبقات موصوف في نظرة عامة على أمان Android . يتضمن كل تحديث لنظام Android العشرات من التحسينات الأمنية لحماية المستخدمين. فيما يلي بعض التحسينات الأمنية التي تم تقديمها في إصدارات Android من 1.5 إلى 4.1:

أندرويد 1.5
  • ProPolice لمنع تجاوز المخزن المؤقت للتكدس (-fstack-protector)
  • Safe_iop لتقليل فيض الأعداد الصحيحة
  • امتدادات لـ OpenBSD dlmalloc لمنع الثغرات الأمنية المزدوجة المجانية ولمنع هجمات الدمج الجماعي. تعد هجمات الدمج المقطوعة طريقة شائعة لاستغلال تلف الكومة.
  • OpenBSD calloc لمنع تجاوز عدد صحيح أثناء تخصيص الذاكرة
أندرويد 2.3
  • حماية الثغرات الأمنية لسلسلة التنسيق (-Wformat- الأمان- خطأ = تنسيق-الأمان)
  • لا يعتمد على الأجهزة (NX) لمنع تنفيذ التعليمات البرمجية على المكدس والكومة
  • Linux mmap_min_addr للتخفيف من تصعيد امتياز إشارة مرجعية للمؤشر الفارغ (تم تحسينه بشكل أكبر في Android 4.1)
أندرويد 4.0
عشوائية تخطيط مساحة العنوان (ASLR) لترتيب المواقع الرئيسية بشكل عشوائي في الذاكرة
أندرويد 4.1
  • دعم PIE (المنصب المستقل القابل للتنفيذ)
  • عمليات النقل للقراءة فقط / الربط الفوري (-Wl ، -z ، relro -Wl ، -z ، الآن)
  • تم تمكين dmesg_restrict (تجنب تسريب عناوين kernel)
  • تم تمكين kptr_restrict (تجنب تسريب عناوين kernel)