1. Typo fixes for Android 10 CDD
    
    Bugs: 160330923
    Test: cdd-gen.sh script to build
    
    Change-Id: I01a08d586925a52c6db2ecf919274848b90112d0
    
  2. CDD: Added local regulations carveout to Device Identifiers requirements.
    
    Updating device identifiers requirements to allow apps to have access
    to SIM serial number/ICCID where local regulations require the app to
    detect changes in subscriber identity.
    
    Change-Id: I5b9eef79c58e546c3ef3d859def0e515342821cc
    BUG: 168387648
    
  3. Docs: Almost final Cleanup CL.
    
    Bug: 140142603
    
    Test: ./cdd_gen.sh --version <version-number> --branch <branch-name>
    Change-Id: Ib0a8e55035eab94ff6ab28ad3c6aa6c7c1ae19d3
    
  4. Docs: Fix typos
    
    Bug: 149871806
    Test: N/A
    Change-Id: I83bbd389c22a168744472a575616ae68aa8178e2
    
  5. Merge "Docs: Fix bullet list formatting" into android10-dev
  6. Docs: Fix bullet list formatting
    
    See screenshots attached to the bug.
    
    Bug: 149871806
    Test: needs to be confirmed by rendering
    Change-Id: I7ab2880fc13cb79c015bd13811ed5330b1cbea66
    
  7. Docs: consistently follow convention to capitalize auxiliaries
    
    Specific auxiliaries fixed in this CL:
     * MUST
     * SHOULD
     * STRONGLY RECOMMEND
     * VERY STRONGLY ENCOURAGED
    
    See also https://www.britannica.com/topic/auxiliary
    
    Bug: 149871806
    Test: N/A
    Change-Id: Ibeab9037bf58ead36ad3b0983845efcc37d94ada
    
  8. Merge "CDD: Carveout automotive from Restricted profiles" into android10-dev
  9. Merge "CDD: TrustAgent and Biometric Carve-out" into android10-dev
  10. CDD: TrustAgent and Biometric Carve-out
    
    7.3.10: Relaxing C-1-8 biometrics requirement for upgrading devices.
    9.11.1: Relaxing C-7-8 trustagent requirement for Automotive, considering
    driver distraction could be of concern.
    
    Bug: 141269831
    Test: NA
    Change-Id: I922d92300ad6565d99adff732877052e02f14850
    
  11. CDD: User consent message substantially same as AOSP.
    
    Test: make_cdd.sh script
    Change-Id: I4fa138bd6cbfb9b31fd87231be8ce8930033c9b9
    
  12. CDD: Location permissions for BLE scans
    
    Test: make_cdd.sh script
    Change-Id: Ie2cdd1d0827e6cbe77629147190e4e311cf1918a
    
  13. Docs: Update to clarify what's allowed for Trust Agent
    
    Test: make_cdd.sh script
    Change-Id: I7bf9bc3d0313ffc719f176eda3c80a9bd7b0d6c9
    
  14. CDD: Carveout automotive from Restricted profiles
    
    Removed the multiple user restricted profiles from
    the core requirement and add them to all the
    device configurations except automotive
    
    Bug: 143736934
    Test: N/A
    Change-Id: Ia9d8e606a50567c2dfab190423923c809ecc5ca2
    
  15. Docs: Editorial Fixes for Section 9.8 and 5.2.5 (video codec table)
    
    bug: b/140142603
    test: NA
    
    Change-Id: Ie5047a8497c94c4cb4e9f0b2bbea51efab9f2eda
    
  16. Docs: Whitespace at EOF
    
    Last line of file should end with a single newline.
    
    Bug: 140034464
    Test: N/A
    Change-Id: Icdaaf61f25a0448fdf866fee4295b0ee15348812
    
  17. Docs: Fix misspellings
    
    Bug: 140034464
    Test: N/A
    Change-Id: If526c0b31459c7f368c623a0d0e916bfc3fd344f
    
  18. CDD: Lockscreen and biometrics changes
    
    - Introducing new biomatrics tier model, adding
     the requirements and constraints for each tier.
    - Some editorial changes by reorganizing and folding some sections
    - Transferred ag/6940471 on master to qt-branch
    
    Bug: 126002559
    Bug: 120995257 (7.3.10/C-2-5)
    Bug: 124243324 (9.11.1/C-7-12)
    Bug: 124403616 (7.3.10 additional background)
    Bug: 123365828 (9.11.1/C-7-11)
    Test: NA
    
    Change-Id: Ib36d40935c77ec370a2494ddb1506b0a952fd525
    
  19. CDD: Updating location and corresponding privacy requirements
    
    - Some minor changes for reporting GNSS measurements
    - Bumping up from Should to SR for 3-axis accelerometer
    - Update privacy requirements related to the user's location to align
    with the updated privacy policy
    
    Bug: 124539379
    Bug: 124405285
    Bug: 124405354
    Bug: 123593924
    Bug: 124404671
    Bug: 124404696
    Test: N/A
    Change-Id: I6278b6af8f1f3f00fe455d66fa051d3d7f5a2dc7
    
  20. CDD: Tighten keystore req
    
    - Tighten the security consistently for Android ecosystem.
    - Remove the condition of a secure lock screen for Keystore reqs for
    form-factors (i.e. Handheld, Auto, TV) that have adopted keystore reqs.
    
    Bug: 111748530
    
    Change-Id: If7682e1410b52390135627d3edc9724d779a265f
    
  21. CDD: Require user consent for screen casting and screen recording
    
    - Provide more transparency for users about casting/screen recording.
    
    Bug: 135560873
    Test: N/A
    
    Change-Id: I36c4f4e26e113bd24737bb0b5fc1476f6d378c83
    
  22. CDD: Update clipboard requirement
    
    - Updating the clipboard requirement to improve privacy.
    
    Test: N/A
    Fixes: 121159550
    Change-Id: Id1cd6237ee741acdf2a24c43a9c4f5f2ec09d0ee
    
  23. Merge "CDD: Require runtime permission for location and physical Activity" into qt-dev
  24. CDD: Require runtime permission for location and physical Activity
    
    - Ensure the correct permission model is implemented for both location
     and proprietary APIs that return location and physical activity.
    - Correspond with the improved location/activity permission in Q.
    
    Test: N/A
    Bug: 124308476
    Bug: 124124462
    
    Change-Id: If5deec3f9c45c1784f66ebf24936e50602cd24a3
    
  25. CDD: Update privacy requirements for capturing contents
    
    - Ensure the data captured on the device will not be leaked and abused.
    
    Bug: 124510178
    Test: none
    
    Change-Id: I9840d1fca81b85c5198882ba8ddbdff527896e02
    
  26. CDD: priv apps root of trust on Verified Boot
    
    - This is a minor language improvement for the spirit.  Previously, the
      document explicitly requires /system, but actually all partition
      protected by Verified Boot is fine.
    
    Test: None
    Bug: 123365823
    Change-Id: I405371c69323bb95bc07e18c09b78ed2d1bcf46e
    
  27. Merge "CDD: Scope Factory Data Reset(FDR) wording to userdata partition." into qt-dev
  28. CDD: Revise section about Android Protected Confirmation API
    
     - Make the security requirements more concise to cover a larger design
       space of possible implementations while preserving the expected
       security guarantees.
    
    Bug: 119186987
    Test: n/a
    Change-Id: I64a7b52a1218df8f16a2a6bb63f1d78465b9d916
    
  29. CDD: Scope Factory Data Reset(FDR) wording to userdata partition.
    
    This is to improve user data privacy.
    
    Bug: 124238463
    Test: None
    Change-Id: I0a098daec3362417b105bda7be56cea424f62253
    
  30. CDD: Permisssions for the hardRestricted level
    
    - The permission model (including permission) restriction is the most
      important mechanism to protect the users privacy
    - Apps need a consitent permission model to be able to effectivly deal
      with user data
    
    Fixes: 124522273
    Change-Id: If85a3f266ab75de64e5ac840101fb3ce983e179d
    
  31. CDD: Clarify privacy requirement for bugreports.
    
    Clarify that bugreports are covered by the following requirement:
    MUST NOT preload or distribute software components out-of-box that send
    user's private information off the device without the user's consent or
    clear ongoing notifications.
    
    Bug: 132458597
    Test: N/A
    Change-Id: I4d1732bb45153e5eccce1964437f9bdf25350d54
    
  32. CDD: Require new device identifier access restrictions
    
    Devices must prevent access to all device identifiers from
    an app that does not meet one of the new requirements.
    
    Bug: 123367433
    Test: N/A
    Change-Id: I683ff569f8f51c38fa4defa0f60c898ea48414ab
    
  33. Merge "CDD: Relax hardware vulnerability requirements" into qt-dev
  34. Merge "CDD: Update CDD for CFI and SCS" into qt-dev
  35. CDD: Strongly recommend StrongBox for devices with secure processors
    
    This arguably is a weakening of the P recommendation, but it's part of
    an incremental strategy to mandate StrongBox across the entire
    ecosystem.  We'll start by recommending it for devices with the
    necessary hardware, then move to mandating it for such devices and
    recommending that all devices add such hardware, then mandate it for
    all devices.
    
    Bug: 135707870
    Test: N/A
    Change-Id: Idf18fde8fc163ee0944a6ce1e611441414ebc461
    
  36. Merge "CDD: Align mic and playback capture requirement" into qt-dev
  37. CDD: Relax hardware vulnerability requirements
    
    Limit mitigation requirements to vulnerable hardware.
    
    Bug: 122834364
    Change-Id: If81385671bfd42f0d100f139c081fd759de81cd0
    
  38. CDD: Align mic and playback capture requirement
    
    - The two audio sources should have the same privacy requirements.
    - Some typo correction for section 5.4.
    
    
    Test: N/A
    Bug: 124333245
    Change-Id: Ida67df090b028b35f0dbea84c1e43de8339c5696
    Signed-off-by: Kevin Rocard <krocard@google.com>
    
  39. CDD: Update CDD for CFI and SCS
    
    -Strongly recommend shadow-call-stack (SCS) and control-flow-integrity
    (CFI) for the kernel and userspace to provide additional protection
    against code-reuse attacks.
    
    Bug: 123365748
    Test: --
    Change-Id: Ida7b2f190da26439443d5247d467047e134933c1
    
  40. CDD: Remove "shared device" exception for encryption
    
     -This can potentially be used to try to gain exceptions for devices
    we never envisioned (for example, many phones allow multiple user
    accounts, and any device shipping with family features is
    pretty much by definition going to be "shared").
    
     -This exception was also somewhat designed for devices with
    lower hardware capabilities.  But with Adiantum available, we
    haven't seen any data showing such an exception is still
    needed.
    
    Bug: 124123642
    Test: None
    Change-Id: Ie2b3f0b5be2c8cda80176160255558e6e5a2cff5
    
  41. CDD: Remove encryption performance exception
    
    We now require encryption on all devices, without any
    exceptions for performance.
    
    For devices which lack AES CPU instructions, and thus have
    performance concerns with AES, we allow the use of Adiantum as
    the encryption method.
    
    Bug: 118200376
    Test: None
    Change-Id: I219fd6d1733c053741d8b71b7f5bd067938d1196
    
  42. CDD: Remove FDE, mandate FBE where encryption is mandated
    
    - Already-launched devices are exempted, and must instead follow
    mandates of their launch CDD.
    
    Bug: 118760699
    Test: not applicable to CDD changes
    Change-Id: Icea70b46c986af187248d9b946e5c17d2b8ef1dd
    
  43. CDD: Clarify data deletion requirements
    
    - Make it clear that all generated data, not just user-generated data
    should be deleted on factory device reset.
    - Clarify that only operating system files on read-only filesystems are
    exempt from being deleted.
    
    Bug: 124238463
    Test: None
    Change-Id: I3cd0bb57ed2c425763b7a50849dc216bc5dcab50
    
  44. Docs: Errata for Android 9 CDD.
    
    - Fixed Section 9.10 by removing C-2-1 due to the introduction of C-0-2
    - Fixed typos in other sections
    
    Bug: 112010610
    
    Test: ./cdd_gen.sh --version 9 --branch pie-dev
    Change-Id: Ie4003beb20425a7fc83cf68ea23772aca389b85b
    
  45. Merge pi-dev as of ag/4582919 into stage-aosp-master.
    
    Bug: 112189069
    Change-Id: I67297b2d6eb189283acb350c1001010f0e9c81d9
    
  46. CDD: Move the req of supporting encryption under perf carve-out
    
    - Ensure the consistent security across devices
    - Replace the carve-out of secure lock screen with the perf carve-out
     for supporting encryption
    
    Test: None
    Bug: 71909258
    Change-Id: Ied56bb0bdd99e3f27e68c13829073c5982019c74
    
  47. Merge "CDD: Require logging of some basic events available to app developers through statsd." into pi-dev
  48. CDD: Clarifying kernel page table isolation
    
    - Modifying the requirement language for C-0-12(kernel page table isolation)
     requirement to add clarity.
    
    Bug: 79088532
    Change-Id: If3b3da40b78203c177cb4b833ea49837336a72b7
    
  49. Merge "CDD: Requirements for services that have access to "android.permission.RECOVER_KEYSTORE"" into pi-dev
  50. CDD: Require logging of some basic events available to app developers through statsd.
    
    Enlist required fields to be more specific about what is
    needed for developer tools and what is needed for privacy.
    
    Bug: 76161779
    Bug: 74125988
    
    Test: None
    Change-Id: I4ff9a73f72c3270caaac0f116297d666a58561fb
    
  51. CDD: Requirements for services that have access to "android.permission.RECOVER_KEYSTORE"
    
    - Prevent brute-force attacks on the lockscreen knowledge factor.
    
    Bug: 73599998
    
    Test: None
    Change-Id: I8f7fa701b11f015e26429c4683a36d37aa2faa47
    
  52. Merge "CDD: Add section about Android Protected Confirmation API" into pi-dev
  53. Merge "CDD: Update CDD language for biometrics and lockscreen." into pi-dev
  54. CDD: Add section about Android Protected Confirmation API
    
     - Device implementations with secure hardware may implement the
       Android Protected Confirmation API to request the user to
       approve a textual message.
    
    Bug: 73001803
    Test: n/a
    Change-Id: I96c5929b0b4ab99b31a9fe7ca0ac82710f94cdca
    
  55. CDD: Update CDD language for biometrics and lockscreen.
    
    This CL makes CDD changes that are aimed at providing more explicit
    guidance on creating secure biometric based unlocks, and on
    consolidating the CDD language for secure lockscreens to make the
    authentication model consistent with our security bar.
    
    More specifically, it changes the following things:
    (1) A new section similar to "7.3.10 Fingerprint Sensors" that's more
    generic and applicable to all biometric sensors. Should have mostly
    the same constraints but slightly altered where necessary.
    (2) Language that deals with match-on-chip solutions for biometrics.
    (3) A new requirement in 9.11 that mandates keeping a minimum
    Sleep timeout of at most 15 seconds.
    (4) New requirements in "9.11.1 Secure Lock Screens" that:
      (a) Constrain what a primary authentication can be.
      (b) Adds information related to alternate biometric unlocks and
      adhering to the SAR/IAR bar that was introduced in the 8.1 CDD
      (c) Adds requirements around 'passive' biometric unlocks like Face
      when used to unlock keystore keys.
      (d) Clarifies some language around falling back to requiring primary
      auth every 72 hours for all non-primary modes of authentication
    (5) Removes the API requirement to return false for both the KeyguardManager.isKeyguardSecure() and the KeyguardManager.isDeviceSecure() methods.
    
    Bug: 73723272
    Bug: 77656214
    Bug: 111053551
    Test: --
    Change-Id: Iede9eba5ac79de56802cd830c3dc4e521f40e098
    
  56. CDD: 9.10. Device Integrity: Change verified boot items from SR to MUST.
    
    Change STRONGLY RECOMMENDED to MUST for verified boot items and slight
    cleanup of language used:
    
     - MUST use tamper-evident storage: for storing whether the bootloader
       is unlocked. Tamper-evident storage means that the boot loader can
       detect if the storage has been tampered with from inside Android.
    
     - MUST prompt the user, while using the device, and require physical
       confirmation before allowing a transition from boot loader locked
       mode to boot loader unlocked mode.
    
     - MUST implement rollback protection for the partitions used by
       Android (e.g. boot, system partitions) and use tamper-evident
       storage for storing the metadata used for determining the minimum
       allowable OS version.
    
    Test: n/a
    Bug: 72919368
    Change-Id: Ifcb0c994cb86f92a422dcde6fa6da1ca064d4ca0
    
  57. Merge "CDD: StrongBox requirements" into pi-dev
  58. Merge "CDD: Update CDD changes for CFI and IOSAN" into pi-dev
  59. Merge "CDD: Recommend metadata encryption" into pi-dev
  60. Merge "CDD: Require verified boot on all devices, including low ram devices" into pi-dev
  61. CDD: Update CDD changes for CFI and IOSAN
    
    This CL renames section 9.7 to 'Security Features' (instead of kernel
    security features), and adds a new sub-section for userspace specific
    security feature advice. There's only a single recommendation in for
    P, but we will be using this section to add more details and
    recommendations/constraints for Q.
    
    Bug: 73724250
    Test: --
    
    Change-Id: If45c5fd9b7668dcafc9ce8dbd2a59b9c4418ca42
    
  62. CDD: StrongBox requirements
    
    - Tighten the security by supporting StrongBox.
    - Clarifying the requirements if StrongBox is supported.
    
    Bug: 73002261
    Test: N/A
    Change-Id: I9834ced2e697bee013cb0725f31745826da1f0c5
    
  63. CDD: Require verified boot on all devices, including low ram devices
    
    We remove the low RAM exception for verified boot.
    
    Test: None
    Bug: 73374550
    Change-Id: I340e8753c8648bbe2a68426123851359d4cba1cb
    
  64. Merge "CDD: Handheld MUST include an application that handles intents related to Storage Access Framework (SAF)" into pi-dev
  65. Merge "Docs: clarify that that CONFIG_ARM_LPAE is not allowed for 32-bit ARM" into pi-dev
  66. Docs: clarify that that CONFIG_ARM_LPAE is not allowed for 32-bit ARM
    
    - It's incompatible with PAN emulation for arm32 kernels.
    - This is already implicitly tested when checking for
    CONFIG_CPU_SW_DOMAIN_PAN.
    
    Bug: 109828784, 74078653, 79088532, 73728376
    Test: n/a
    Change-Id: Idb6a96d6f8c13a959b4bdc2c5580294beeff2d7c
    
  67. CDD: Allow escrow keys to unlock CE storage.
    
    - Much of the purpose of escrow keys is to allow storage
      to be unlocked when a user forgets their LSKF, so we
      must allow this in CDD.
    
    Bug: 111561428
    Test: Documentation change.
    Change-Id: I0de44228e35728713405a8d84ec3b8e6f8a9ecbf
    
  68. Merge "CCD: Add recommendations for Full Stack Integrity" into pi-dev
  69. Merge "CDD: Require to include only the data with 'DEST_AUTO' in the incident report" into pi-dev
  70. CDD: Recommend metadata encryption
    
    - Tighten the security.
    
    Bug: 73662717
    Test: Compiled and inspected HTML
    Change-Id: Ib2be403ef2db8525c9ad579a289eca79132696e9
    
  71. CDD: MUST NOT send user's private data off the device without the user's consent
    
    - Ensure that user's private data is protected and is not sent off the device without user's consent.
    
    Bug: 74620344
    Change-Id: I41559d7d3903ea3d44d1471abe896ad7698ef6be
    Test: N/A
    
  72. CDD: Require to include only the data with 'DEST_AUTO' in the incident report
    
    Ensure that the data other than `DEST_AUTO` is not included in the report for
    privacy protection. As fields or messages annotated with DEST_AUTO
    can be sent by automatic means, without per-sending user consent. The user
    still must have previously accepted a consent to share this information.
    
    Bug: 76161779
    Test: N/A
    Change-Id: I813c96d43395b092ab0e8681893cf205723d26bb
    
  73. CCD: Add recommendations for Full Stack Integrity
    
    Android P adds support for extending the protections of Verified Boot
    beyond OS partitions to privileged apps that are installed on /data.
    This change recommends that device implementations perform
    integrity checks of these privileged apps.
    
    Test: None
    Bug: 73001552
    Change-Id: I773c4ad431ab0f2c16a762ba342653502ea98912
    
  74. Merge "CDD: Tightening kernel security requirements from SR to MUST" into pi-dev
    am: c180b33ab7
    
    Change-Id: I98f56e36e38a6ae993da734547f56bc5985abbaa
    
  75. Merge "CDD: Tightening kernel security requirements from SR to MUST" into pi-dev
  76. CDD: Tightening kernel security requirements from SR to MUST
    
    - The tightened MUST requirements are applicable for devices that
    originally ship with API level 28 and above.
    
    These security requirements provide better protections for the kernel by
    mitigating common classes of vulnerabilities and privilege escalation
    techniques.
    
    Bug: 74078653
    Bug: 79088532
    Bug: 73728376
    Test: n/a
    Change-Id: I62450948e5474939d94b22b280d11a6d56e35f3e
    
  77. Merge "CDD: add per-app selinux requirements for P" into pi-dev
    am: 3240eddfe2
    
    Change-Id: I7824a7cb89d99f2b4b3ccfe2d74756f3ad63ee93
    
  78. Merge "CDD: add per-app selinux requirements for P" into pi-dev
  79. CDD: Describe subscription plan security model.
    am: 0b1792e034
    
    Change-Id: I4c22a009fb2e6debb7e6087aca04ae56bd61037a
    
  80. CDD: Describe subscription plan security model.
    
    Bug: 71816837
    Test: ./cdd_gen.sh
    Change-Id: I670a694bd37436e71b37f4746c5261d2d93b6b91
    
  81. CDD: add per-app selinux requirements for P
    
    Apps that target Android P can no longer share data with other apps
    using world-accessible Unix permissions. This change improves the
    integrity of the Android Application Sandbox, particularly the
    requirement that an app's private data is accessible only by that
    app. [1]
    
    To share files with another another app, use a content provider
    or shared space in external storage.
    
    This feature enforces an existing requirement that files saved in
    internal storage are accessible by the owning app. [2]
    
    [1] https://developer.android.com/guide/topics/data/data-storage.html#filesInternal
    [2] https://developer.android.com/training/data-storage/files.html#PublicFiles
    
    Bug: 73728376
    Test: n/a
    Change-Id: Ib2a93fde25f660782f315d5e02978637680f7594
    
  82. Merge "CDD: Clarify the requirement for kernel stack buffer overflow protections." into oreo-dev am: ab75ac73a1 am: 85a4240862
    am: b7330a04e2
    
    Change-Id: If466bbca8c242284d38bf61ecf993e04331dd262
    
  83. Merge "CDD: Clarify the requirement for kernel stack buffer overflow protections." into oreo-dev
    am: ab75ac73a1
    
    Change-Id: I9e7a3349b07a45559129352cc14d397ced014266
    
  84. Merge "CDD: Clarify the requirement for kernel stack buffer overflow protections." into oreo-dev
  85. CDD: Clarify the requirement for kernel stack buffer overflow protections.
    
    - Update 9.7. Kernel Security Features [C-0-7].
    - Differentiate the requirement and the sample mechanism.
    
    Bug: 67317614
    Test: N/A
    Change-Id: I1c79e59d611b22d469e85fc81b976cbb98221234
    
  86. resolve merge conflicts of e7278fe2c0fc37b428b14dcbd4b37ef05eb69678 to oc-mr1-dev-plus-aosp
    
    Test: I solemnly swear I tested this conflict resolution.
    Change-Id: I2b54c7d9f68e6a57fa002bbbea78bde979ee2122
    
  87. CDD: Clarify the key attestation is required only for new devices
    am: 59f5208e19
    
    Change-Id: Id1b0fe34aa6891ee65cc7efaae346fcc7af8a08d
    
  88. CDD: Clarify the key attestation is required only for new devices
    
    - Add the clarification note for 9.11 [C-1-4].
    - Clarified for old devices with earlier version of Android to be
    exempted from the key attestation requirement.
    
    Bug: 72461553
    Change-Id: I9b14119bcd67b5aa2063b3fb21b995fd658fc9d7
    
  89. Merge "CDD: Require verified boot when device has enough RAM vs. good AES-crypto performance" into oc-mr1-dev
    am: 3028793cd4
    
    Change-Id: I4bb0ee4bf995d362f35677cea7fba3cdaa64b225
    
  90. Merge "CDD: Require verified boot when device has enough RAM vs. good AES-crypto performance" into oc-mr1-dev
  91. Merge "CDD: Require secure storage of lock screen credentials" into oc-mr1-dev
    am: 0ea6e466a7
    
    Change-Id: Id91984da103cbdc1991259ef1606c70455ddf5de
    
  92. Merge "CDD: Require secure storage of lock screen credentials" into oc-mr1-dev
  93. CDD: Require verified boot when device has enough RAM vs.
    good AES-crypto performance
    
    Update verified boot requirement to be MUST for devices that report
    feature flag android.hardware.ram.normal
    
    Bug: 35039737
    Test: N/A
    Change-Id: If7346873f92879a551935b55597762a46b5e89c8
    
  94. Merge "CDD: Changes to measure biometric unlock security." into oc-mr1-dev
    am: 3a6ff29410
    
    Change-Id: Icfeef51e12db5335f3238adc0fc62cc25153abd1
    
  95. Merge "CDD: Changes to measure biometric unlock security." into oc-mr1-dev
  96. Merge "CDD: AES encrypt the encryption key by default" into oc-mr1-dev
    am: 009ff2c391
    
    Change-Id: I85ef23cb266b77f816ab462b189ee2fc36d72aac
    
  97. Merge "CDD: AES encrypt the encryption key by default" into oc-mr1-dev
  98. CDD: Require secure storage of lock screen credentials
    
    - With credential-based Factory Reset Protection, the
    credential handle is stored on an unencrypted partition. To maintain
    security guarantees, implementations must make sure that the handle
    does not leak information about the credential.
    
    Bug: 64209214
    Test: n/a
    Change-Id: I55f15cc75502016824d9307c03d947c4041744b0
    
  99. CDD: Changes to measure biometric unlock security.
    
    Adds imposter and spoof acceptance rate metrics for biometric based
    unlocks, and mandates showing a disclosure of the risks involved when
    an unlock modality does not meet the bar.
    
    Bug: 66013719
    Bug: 63910023
    Test: N/A
    Change-Id: I6a129481c0036c756f8c7d95cf3da1bab9f3f0f1
    
  100. CDD: AES encrypt the encryption key by default
    
    For Android O-MR1 we are requiring that all encryption keys are
    encrypted with AES by default, unless the user explicitly opts out.
    
    Bug: 33744049
    Change-Id: Ic74dcd960ef89b752f580bd2ce2e42acca643c1f
    Test: Not necessary -- this is a policy change.