Android Studio: Security - Revision history

Onnowpurbo at 09:23, 5 May 2015

2015-05-05T09:23:21Z

Onnowpurbo at 02:55, 4 May 2015

2015-05-04T02:55:22Z

Onnowpurbo at 02:54, 4 May 2015

2015-05-04T02:54:08Z

Onnowpurbo at 02:53, 4 May 2015

2015-05-04T02:53:40Z

Onnowpurbo at 02:36, 4 May 2015

2015-05-04T02:36:26Z

Onnowpurbo: New page: Sumber: https://source.android.com/devices/tech/security/ Android is a modern mobile platform that was designed to be truly open. Android applications make use of advanced hardware and so...

2015-05-04T02:30:21Z

New page: Sumber: https://source.android.com/devices/tech/security/ Android is a modern mobile platform that was designed to be truly open. Android applications make use of advanced hardware and so...

New page

Sumber: https://source.android.com/devices/tech/security/

Android is a modern mobile platform that was designed to be truly open. Android applications make use of advanced hardware and software, as well as local and served data, exposed through the platform to bring innovation and value to consumers. To protect that value, the platform must offer an application environment that ensures the security of users, data, applications, the device, and the network.

Securing an open platform requires a robust security architecture and rigorous security programs. Android was designed with multi-layered security that provides the flexibility required for an open platform, while providing protection for all users of the platform. For information about reporting security issues and the update process, see Security Updates and Resources.

Android was designed with developers in mind. Security controls were designed to reduce the burden on developers. Security-savvy developers can easily work with and rely on flexible security controls. Developers less familiar with security will be protected by safe defaults.

Android was designed with device users in mind. Users are provided visibility into how applications work, and control over those applications. This design includes the expectation that attackers would attempt to perform common attacks, such as social engineering attacks to convince device users to install malware, and attacks on third-party applications on Android. Android was designed to both reduce the probability of these attacks and greatly limit the impact of the attack in the event it was successful.

This documentation outlines the goals of the Android security program, describes the fundamentals of the Android security architecture, and answers the most pertinent questions for system architects and security analysts. This document focuses on the security features of Android's core platform and does not discuss security issues that are unique to specific applications, such as those related to the browser or SMS application. Recommended best practices for building Android devices, deploying Android devices, or developing applications for Android are not the goal of this document and are provided elsewhere.
Background

Android provides an open source platform and application environment for mobile devices.

The sections and pages below describe the security features of the Android platform. Figure 1 summarizes the security components and considerations of the various levels of the Android software stack. Each component assumes that the components below are properly secured. With the exception of a small amount of Android OS code running as root, all code above the Linux Kernel is restricted by the Application Sandbox.

Figure 1: Android software stack

Figure 1: Android software stack.

The main Android platform building blocks are:

Device Hardware: Android runs on a wide range of hardware configurations including smart phones, tablets, and set-top-boxes. Android is processor-agnostic, but it does take advantage of some hardware-specific security capabilities such as ARM v6 eXecute-Never.

Android Operating System: The core operating system is built on top of the Linux kernel. All device resources, like camera functions, GPS data, Bluetooth functions, telephony functions, network connections, etc. are accessed through the operating system.

Android Application Runtime: Android applications are most often written in the Java programming language and run in the Dalvik virtual machine. However, many applications, including core Android services and applications are native applications or include native libraries. Both Dalvik and native applications run within the same security environment, contained within the Application Sandbox. Applications get a dedicated part of the filesystem in which they can write private data, including databases and raw files.

Android applications extend the core Android operating system. There are two primary sources for applications:

Pre-Installed Applications: Android includes a set of pre-installed applications including phone, email, calendar, web browser, and contacts. These function both as user applications and to provide key device capabilities that can be accessed by other applications. Pre-installed applications may be part of the open source Android platform, or they may be developed by an OEM for a specific device.

User-Installed Applications: Android provides an open development environment supporting any third-party application. Google Play offers users hundreds of thousands of applications.

Google provides a set of cloud-based services that are available to any compatible Android device. The primary services are:

Google Play: Google Play is a collection of services that allow users to discover, install, and purchase applications from their Android device or the web. Google Play makes it easy for developers to reach Android users and potential customers. Google Play also provides community review, application license verification, application security scanning, and other security services.

Android Updates: The Android update service delivers new capabilities and security updates to Android devices, including updates through the web or over the air (OTA).

Application Services: Frameworks that allow Android applications to use cloud capabilities such as (backing up) application data and settings and cloud-to-device messaging (C2DM) for push messaging.

These services are not part of the Android Open Source Project and are out of scope for this document. But they are relevant to the security of most Android devices, so a related security document titled “Google Services for Android: Security Overview” is available.

Security updates and resources
In this document

Reporting Security Issues
Android Updates
Other Resources

Reporting Security Issues

Note: The preferred way to report security issues is sending an email detailing the issue to security@android.com.

Any developer, Android user, or security researcher can notify the Android security team of potential security issues. Your message can be encrypted using the Android security team PGP key here.

Sending an email to security@android.com is preferable to using the public Android bug tracker. Bugs marked as security issues are not externally visible, but they may eventually be made visible. If you plan to submit a patch to resolve a security issue, please contact security@android.com and wait for a response before submitting the patch to AOSP.
Android Updates

Android provides system updates for both security and feature related purposes.

There are two ways to update the code on most Android devices: over-the-air (OTA updates) or side-loaded updates. OTA updates can be rolled out over a defined time period or be pushed to all devices at once, depending on how the OEM and/or carrier would like to push the updates. Side-loaded updates can be provided from a central location for users to download as a zip file to their local desktop machine or directly to their handset. Once the update is copied or downloaded to the SD card on the device, Android will recognize the update, verify its integrity and authenticity, and automatically update the device.

If a dangerous vulnerability is discovered internally or responsibly reported to Google or the Android Open Source Project, the Android security team will start the following process.

The Android team will notify companies who have signed NDAs regarding the problem and begin discussing the solution.
The owners of code will begin the fix.
The Android team will fix Android-related security issues.
When a patch is available, the fix is provided to the NDA companies.
The Android team will publish the patch in the Android Open Source Project
OEM/carrier will push an update to customers.

The NDA is required to ensure that the security issue does not become public prior to availabilty of a fix and put users at risk. Many OHA members run their own code on Android devices such as the bootloader, wifi drivers, and the radio. Once the Android Security team is notified of a security issue in this partner code, they will consult with OHA partners to quickly find a fix for the problem at hand and similar problems. However, the OHA member who wrote the faulty code is ultimately responsible for fixing the problem.

If a dangerous vulnerability is not responsibly disclosed (e.g., if it is posted to a public forum without warning), then Google and/or the Android Open Source Project will work as quickly as possible to create a patch. The patch will released to the public (and any partners) when the patch is tested and ready for use.

At Google I/O 2011, many of the largest OHA partners committed to providing updates to devices for 18 months after initial shipment. This will provide users with access to the most recent Android features, as well as security updates.

Any developer, Android user, or security researcher can notify the Android security team of potential security issues by sending email to security@android.com. If desired, communication can be encrypted using the Android security team PGP key available here: https://developer.android.com/security_at_android_dot_com.txt.
Other Resources

Information for Android application developers is here: https://developer.android.com.

The Android Security team can be reached at security@android.com.

Security information exists throughout the Android Open Source and Developer Sites. A good place to start is here: https://developer.android.com/guide/topics/security/security.html.

A Security FAQ for developers is located here: https://developer.android.com/resources/faq/security.html.

Security Best Practices for developers is located here: https://developer.android.com/guide/practices/security.html.

A community resource for discussion about Android security exists here: https://groups.google.com/forum/?fromgroups#!forum/android-security-discuss.

==Referensi==

* https://source.android.com/devices/tech/security/
* https://source.android.com/devices/tech/security/overview/updates-resources.html

@@ Line 39: / Line 39: @@
 * Android Updates: The Android update service delivers new capabilities and security updates to Android devices, including updates through the web or over the air (OTA).
-    Application Services: Frameworks that allow Android applications to use cloud capabilities such as (backing up) application data and settings and cloud-to-device messaging (C2DM) for push messaging.
+* Application Services: Frameworks that allow Android applications to use cloud capabilities such as (backing up) application data and settings and cloud-to-device messaging (C2DM) for push messaging.
 These services are not part of the Android Open Source Project and are out of scope for this document. But they are relevant to the security of most Android devices, so a related security document titled “Google Services for Android: Security Overview” is available.

@@ Line 54: / Line 54: @@
- Security updates and resources
+==Security updates and resources==
 Note: The preferred way to report security issues is sending an email detailing the issue to security@android.com.
@@ Line 76: / Line 70: @@
 If a dangerous vulnerability is discovered internally or responsibly reported to Google or the Android Open Source Project, the Android security team will start the following process.
-    The Android team will notify companies who have signed NDAs regarding the problem and begin discussing the solution.
+* The Android team will notify companies who have signed NDAs regarding the problem and begin discussing the solution.
-    The owners of code will begin the fix.
+* The owners of code will begin the fix.
-    The Android team will fix Android-related security issues.
+* The Android team will fix Android-related security issues.
-    When a patch is available, the fix is provided to the NDA companies.
+* When a patch is available, the fix is provided to the NDA companies.
-    The Android team will publish the patch in the Android Open Source Project
+* The Android team will publish the patch in the Android Open Source Project
-    OEM/carrier will push an update to customers.
+* OEM/carrier will push an update to customers.
 The NDA is required to ensure that the security issue does not become public prior to availabilty of a fix and put users at risk. Many OHA members run their own code on Android devices such as the bootloader, wifi drivers, and the radio. Once the Android Security team is notified of a security issue in this partner code, they will consult with OHA partners to quickly find a fix for the problem at hand and similar problems. However, the OHA member who wrote the faulty code is ultimately responsible for fixing the problem.
@@ Line 90: / Line 84: @@
 Any developer, Android user, or security researcher can notify the Android security team of potential security issues by sending email to security@android.com. If desired, communication can be encrypted using the Android security team PGP key available here: https://developer.android.com/security_at_android_dot_com.txt.

@@ Line 9: / Line 9: @@
 Android dirancang dengan pengguna perangkat dalam pikiran. Pengguna disediakan visibilitas ke bagaimana aplikasi bekerja, dan kontrol atas aplikasi mereka. Desain ini meliputi perkiraan bahwa penyerang akan mencoba untuk melakukan serangan umum, seperti serangan rekayasa sosial untuk meyakinkan pengguna perangkat untuk menginstal malware, dan serangan terhadap aplikasi pihak ketiga di Android. Android dirancang untuk mengurangi kemungkinan serangan ini dan sangat membatasi dampak serangan jika hal itu terjadi.
-This documentation outlines the goals of the Android security program, describes the fundamentals of the Android security architecture, and answers the most pertinent questions for system architects and security analysts. This document focuses on the security features of Android's core platform and does not discuss security issues that are unique to specific applications, such as those related to the browser or SMS application. Recommended best practices for building Android devices, deploying Android devices, or developing applications for Android are not the goal of this document and are provided elsewhere.
+Dokumentasi ini menguraikan tujuan dari program keamanan Android, menjelaskan dasar-dasar arsitektur keamanan Android, dan menjawab pertanyaan-pertanyaan yang paling relevan untuk arsitek sistem dan analis keamanan. Dokumen ini berfokus pada fitur keamanan platform inti Android dan tidak membahas masalah keamanan yang unik untuk aplikasi tertentu, seperti yang terkait dengan aplikasi browser atau SMS. Praktik terbaik yang direkomendasikan untuk membangun perangkat Android, penggelaran perangkat Android, atau mengembangkan aplikasi untuk Android tidak tujuan dokumen ini dan disediakan tempat lain.
-Background
 Android provides an open source platform and application environment for mobile devices.

@@ Line 16: / Line 16: @@
 The sections and pages below describe the security features of the Android platform. Figure 1 summarizes the security components and considerations of the various levels of the Android software stack. Each component assumes that the components below are properly secured. With the exception of a small amount of Android OS code running as root, all code above the Linux Kernel is restricted by the Application Sandbox.
-Figure 1: Android software stack
+[[Image:Android-software-stack.png|center|300px|thumb|Android software stack]]
-The main Android platform building blocks are:
+Building block utama dari Android Platform adalah:
-    Device Hardware: Android runs on a wide range of hardware configurations including smart phones, tablets, and set-top-boxes. Android is processor-agnostic, but it does take advantage of some hardware-specific security capabilities such as ARM v6 eXecute-Never.
+* Device Hardware: Android runs on a wide range of hardware configurations including smart phones, tablets, and set-top-boxes. Android is processor-agnostic, but it does take advantage of some hardware-specific security capabilities such as ARM v6 eXecute-Never.
-    Android Operating System: The core operating system is built on top of the Linux kernel. All device resources, like camera functions, GPS data, Bluetooth functions, telephony functions, network connections, etc. are accessed through the operating system.
+* Android Operating System: The core operating system is built on top of the Linux kernel. All device resources, like camera functions, GPS data, Bluetooth functions, telephony functions, network connections, etc. are accessed through the operating system.
-    Android Application Runtime: Android applications are most often written in the Java programming language and run in the Dalvik virtual machine. However, many applications, including core Android services and applications are native applications or include native libraries. Both Dalvik and native applications run within the same security environment, contained within the Application Sandbox. Applications get a dedicated part of the filesystem in which they can write private data, including databases and raw files.
+* Android Application Runtime: Android applications are most often written in the Java programming language and run in the Dalvik virtual machine. However, many applications, including core Android services and applications are native applications or include native libraries. Both Dalvik and native applications run within the same security environment, contained within the Application Sandbox. Applications get a dedicated part of the filesystem in which they can write private data, including databases and raw files.
 Android applications extend the core Android operating system. There are two primary sources for applications:
-    Pre-Installed Applications: Android includes a set of pre-installed applications including phone, email, calendar, web browser, and contacts. These function both as user applications and to provide key device capabilities that can be accessed by other applications. Pre-installed applications may be part of the open source Android platform, or they may be developed by an OEM for a specific device.
+* Pre-Installed Applications: Android includes a set of pre-installed applications including phone, email, calendar, web browser, and contacts. These function both as user applications and to provide key device capabilities that can be accessed by other applications. Pre-installed applications may be part of the open source Android platform, or they may be developed by an OEM for a specific device.
-    User-Installed Applications: Android provides an open development environment supporting any third-party application. Google Play offers users hundreds of thousands of applications.
+* User-Installed Applications: Android provides an open development environment supporting any third-party application. Google Play offers users hundreds of thousands of applications.
 Google provides a set of cloud-based services that are available to any compatible Android device. The primary services are:
-    Google Play: Google Play is a collection of services that allow users to discover, install, and purchase applications from their Android device or the web. Google Play makes it easy for developers to reach Android users and potential customers. Google Play also provides community review, application license verification, application security scanning, and other security services.
+* Google Play: Google Play is a collection of services that allow users to discover, install, and purchase applications from their Android device or the web. Google Play makes it easy for developers to reach Android users and potential customers. Google Play also provides community review, application license verification, application security scanning, and other security services.
-    Android Updates: The Android update service delivers new capabilities and security updates to Android devices, including updates through the web or over the air (OTA).
+* Android Updates: The Android update service delivers new capabilities and security updates to Android devices, including updates through the web or over the air (OTA).
      Application Services: Frameworks that allow Android applications to use cloud capabilities such as (backing up) application data and settings and cloud-to-device messaging (C2DM) for push messaging.

@@ Line 1: / Line 1: @@
 Sumber: https://source.android.com/devices/tech/security/
-Android is a modern mobile platform that was designed to be truly open. Android applications make use of advanced hardware and software, as well as local and served data, exposed through the platform to bring innovation and value to consumers. To protect that value, the platform must offer an application environment that ensures the security of users, data, applications, the device, and the network.
+Android adalah platform mobile modern yang dirancang untuk menjadi benar-benar terbuka. Aplikasi android menggunakan hardware canggih dan software, serta data lokal dan disajikan, ter-expose melalui platform untuk membawa inovasi dan nilai kepada konsumen. Untuk melindungi nilai tersebut, platform harus menawarkan lingkungan aplikasi yang menjamin keamanan pengguna, data, aplikasi, perangkat, dan jaringan.
-Securing an open platform requires a robust security architecture and rigorous security programs. Android was designed with multi-layered security that provides the flexibility required for an open platform, while providing protection for all users of the platform. For information about reporting security issues and the update process, see Security Updates and Resources.
+Mengamankan platform terbuka memerlukan arsitektur keamanan yang kuat dan program keamanan yang ketat. Android dirancang dengan keamanan berlapis-lapis yang menyediakan fleksibilitas yang diperlukan untuk platform terbuka, sambil memberikan perlindungan bagi semua pengguna platform. Untuk informasi tentang pelaporan masalah keamanan dan proses update, lihat Security Updates and Resources.
-Android was designed with developers in mind. Security controls were designed to reduce the burden on developers. Security-savvy developers can easily work with and rely on flexible security controls. Developers less familiar with security will be protected by safe defaults.
+Android dirancang dengan developer dalam pikiran. Kontrol keamanan yang dirancang untuk mengurangi beban pengembang. Developer yang familiar dengan keamanan dapat dengan mudah bekerja dengan dan bergantung pada kontrol keamanan yang fleksibel. Pengembang kurang familiar  dengan keamanan akan dilindungi oleh default yang aman.
-Android was designed with device users in mind. Users are provided visibility into how applications work, and control over those applications. This design includes the expectation that attackers would attempt to perform common attacks, such as social engineering attacks to convince device users to install malware, and attacks on third-party applications on Android. Android was designed to both reduce the probability of these attacks and greatly limit the impact of the attack in the event it was successful.
+Android dirancang dengan pengguna perangkat dalam pikiran. Pengguna disediakan visibilitas ke bagaimana aplikasi bekerja, dan kontrol atas aplikasi mereka. Desain ini meliputi perkiraan bahwa penyerang akan mencoba untuk melakukan serangan umum, seperti serangan rekayasa sosial untuk meyakinkan pengguna perangkat untuk menginstal malware, dan serangan terhadap aplikasi pihak ketiga di Android. Android dirancang untuk mengurangi kemungkinan serangan ini dan sangat membatasi dampak serangan jika hal itu terjadi.
 This documentation outlines the goals of the Android security program, describes the fundamentals of the Android security architecture, and answers the most pertinent questions for system architects and security analysts. This document focuses on the security features of Android's core platform and does not discuss security issues that are unique to specific applications, such as those related to the browser or SMS application. Recommended best practices for building Android devices, deploying Android devices, or developing applications for Android are not the goal of this document and are provided elsewhere.