Docs: Add Certificate Authorities section to App security article
Bug: 28295905

Change-Id: I0e7975be2d6276fe4128aff43f6c2abcf9bd4765
diff --git a/src/security/overview/app-security.jd b/src/security/overview/app-security.jd
index c7b7799..8b011fa 100644
--- a/src/security/overview/app-security.jd
+++ b/src/security/overview/app-security.jd
@@ -280,6 +280,32 @@
   time, the installer will prompt the user asking if the application can access
   the information. If the user does not grant access, the application will not be
+<h2 id="certificate-authorities">Certificate authorities</h2>
+Android includes a set of installed system Certificate Authorities, which are
+trusted system-wide. Prior to Android 7.0, device manufacturers could modify the
+set of CAs shipped on their devices. However, devices running 7.0 and above will
+have a uniform set of system CAs as modification by device manufacturers is no
+longer permitted.
+To be added as a new public CA to the Android stock set, the CA must complete
+the <a href="">Mozilla CA Inclusion
+Process</a> and then file a feature request against Android (<a
+to have the CA added to the stock Android CA set in the <a
+href="">Android Open Source Project</a>
+There are still CAs that are device-specific and should not be included in the
+core set of AOSP CAs, like carriers’ private CAs that may be needed to securely
+access components of the carrier’s infrastructure, such as SMS/MMS gateways.
+Device manufacturers are encouraged to include the private CAs only in the
+components/apps that need to trust these CAs. See <a
+Security Configuration</a> for more details.
 <h2 id="application-signing">Application Signing</h2>
 <p>Code signing allows developers to identify the author of the application and to
   update their application without creating complicated interfaces and