# Secure Realm boot with Arm CCA BootSync

## In this learning path

- [Introduction](https://learn.arm.com/learning-paths/servers-and-cloud-computing/cca-bootsync/)
- [Understand Arm CCA BootSync and the Boot Injection protocol](https://learn.arm.com/learning-paths/servers-and-cloud-computing/cca-bootsync/cca-bootsync/)
- [Configure UEFI Secure Boot and disk encryption in Arm CCA Realms](https://learn.arm.com/learning-paths/servers-and-cloud-computing/cca-bootsync/flow/)
- [Next Steps](https://learn.arm.com/learning-paths/servers-and-cloud-computing/cca-bootsync/_next-steps/)

## About this Learning Path

|  |  |
| --- | --- |
| Skill level: | Advanced |
| Reading time: | 1 hr |
| Last updated: | 03 Nov 2026 |

|  |
| --- |
| Authors: |
| Anton Antonov , Arm<br>Pareena Verma , Arm<br>[GitHub](https://github.com/pareenaverma)<br>[LinkedIn](https://linkedin.com/in/pareena-verma-7853607) |
| Arm IP: |
| [Neoverse](https://support.arm.com/?tab=compute-ip&Product%20Type=Infrastructure%20Processors) [Cortex-A](https://support.arm.com/?tab=compute-ip&Product%20Type=Application%20Processors) |
| Tags: |
| [Performance and Architecture](https://learn.arm.com/tag/performance-and-architecture/) [Linux](https://learn.arm.com/tag/linux) [FVP](https://learn.arm.com/tag/fvp) [RME](https://learn.arm.com/tag/rme) [CCA](https://learn.arm.com/tag/cca) [Docker](https://learn.arm.com/tag/docker) [EDK2](https://learn.arm.com/tag/edk2) [Cryptsetup](https://learn.arm.com/tag/cryptsetup) |

| Arm IP:                                      |                  |
|----------------------------------------------|------------------|
| [Neoverse](https://support.arm.com/?tab=compute-ip&Product%20Type=Infrastructure%20Processors) |                  |
| [Cortex-A](https://support.arm.com/?tab=compute-ip&Product%20Type=Application%20Processors) |                  |

| Tags:                        |                  |
|-----------------------------|------------------|
| [Performance and Architecture](https://learn.arm.com/tag/performance-and-architecture/) |                  |
| [Linux](https://learn.arm.com/tag/linux)        |                  |
| [FVP](https://learn.arm.com/tag/fvp)            |                  |
| [RME](https://learn.arm.com/tag/rme)            |                  |
| [CCA](https://learn.arm.com/tag/cca)            |                  |
| [Docker](https://learn.arm.com/tag/docker)      |                  |
| [EDK2](https://learn.arm.com/tag/edk2)          |                  |
| [Cryptsetup](https://learn.arm.com/tag/cryptsetup) |              |

### Who is this for?
This Learning Path is for developers who want to understand how Arm Confidential Compute Architecture (CCA) BootSync supports early Realm boot workflows such as UEFI Secure Boot and encrypted disk boot.

### What will you learn?
After completing this Learning Path, you'll be able to perform the following tasks:
- Understand why BootSync is needed before the Realm guest operating system has networking.
- Understand how the Boot Injection Protocol uses key exchange, attestation, and Boot Information Blocks to support the BootSync workflow.
- Use BootSync to inject UEFI variables and secret data into an Arm CCA Realm.
- Launch Arm CCA Realms with UEFI Secure Boot and an encrypted root file system on an Armv9-A AEM Base Fixed Virtual Platform (FVP) with Realm Management Extension (RME) support.

### Prerequisites
Before starting, you'll need the following prerequisites:
- A cloud-based instance or an AArch64 or x86_64 computer running Linux. For more information about using cloud-based instances, see the [Arm cloud service providers](https://learn.arm.com/learning-paths/servers-and-cloud-computing/csp/) Learning Path.
- Completion of the [Run an application in a Realm using Arm CCA](https://learn.arm.com/learning-paths/servers-and-cloud-computing/cca-container/) Learning Path.

### Summary
You’ll use Arm CCA BootSync on an RME-enabled Armv9-A AEM Base FVP to deliver UEFI variables and secrets to a Realm during early boot, then validate Secure Boot and encrypted disk startup. First, you’ll launch a Realm without injected data to observe firmware attestation. Next, you’ll provide variable data for BootSync to complete and verify that Secure Boot rejects the unsigned kernel. After signing the kernel, you’ll verify that Secure Boot is active. Finally, you’ll encrypt the Realm root file system, inject the file system decryption secret through BootSync, and confirm that the disk unlocks during boot.
