aosp-part-security

Consolidate Android security topics across SELinux, Keystore, Trusty TEE, AVB, and DRM.

122|30|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/aospbooks/aosp-internal-book --skill aosp-part-security
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aosp-part-security
Source: https://github.com/aospbooks/aosp-internal-book/tree/main/agents/claude/skills/aosp-part-security
Command: npx skills add https://github.com/aospbooks/aosp-internal-book --skill aosp-part-security

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Android security is multi-layered and complex, spanning SELinux policy, keystore/keymint, Trusty TEE, gatekeeper/weaver, AVB, dm-verity, and the DRM/Credential Manager surface. This Skill provides a structured reference and reasoning framework for understanding how these components interact and how to analyze security properties across the AOSP Part IX stack.

Core Features & Use Cases

  • Comprehensive mapping of security subsystems including SELinux, Verified Boot, hardware-backed attestation, and key management.
  • End-to-end reasoning about Credential Manager, passkeys/FIDO2, and DRM (MediaDrm, Widevine, OEMCrypto) across system server, framework, and HAL boundaries.
  • Use Case: Assess a device's secure boot chain, from hardware root of trust to per-app sandbox, or evaluate a new credential provider integration.

Quick Start

Summarize SELinux policy, key management flows, and DRM session interactions for a quick security assessment.

Frequently Asked Questions about aosp-part-security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does SELinux policy interact with the Android Verified Boot chain?

Android Verified Boot establishes a hardware root of trust chain that SELinux policy relies on, enforcing mandatory access controls across validated per-app sandboxes. This Skill maps these subsystem interactions to evaluate security architectures.

How do I evaluate a new Credential Manager provider integration for passkeys and FIDO2?

Evaluating a Credential Manager provider requires reasoning about passkeys and FIDO2 integrations across system server, framework, and HAL boundaries. This Skill provides structured analysis for assessing credential provider designs end-to-end.

What is the role of Trusty TEE and Gatekeeper in Android keystore and key management?

Trusty TEE and Gatekeeper secure Android keystore and Keymint operations by providing hardware-backed isolation for device authentication. This Skill analyzes these key management flows to assess security properties across the AOSP stack.

Can I analyze the DRM lifecycle including MediaDrm and Widevine across HAL boundaries?

You can analyze the DRM lifecycle including MediaDrm and Widevine across system server, framework, and HAL boundaries. This Skill offers end-to-end reasoning about DRM session interactions and OEMCrypto implementations.

Do I need to understand dm-verity and AVB to assess Android secure boot architectures?

Understanding dm-verity and Android Verified Boot is required to assess secure boot architectures from the hardware root of trust to per-app sandboxes. This Skill requires knowledge of AVB designs for comprehensive security evaluation.

Why does hardware-backed attestation matter for key management flows in Android?

Hardware-backed attestation verifies Android device integrity before trusting key management flows, ensuring keys are generated in a secure environment. This Skill maps attestation alongside keystore and Keymint to evaluate security properties.