Note: SIE Standalone build is deprecated and no longer supported. The last stable build tag was v22.10_SIE_REL1.1.0. SIE ACS is now integrated with IR, ES, SR Bands. Please Refer to respective README for instructions.
The SystemReady Security Interface Extension provides a way to certify that Secure Boot and secure firmware update are implemented as prescribed by the Arm Base Boot Security Specification (BBSR). The Security Interface Extension is an extension to the bands of the SystemReady program and a pre-requisite for a Security Interface Extension certification in one of the IR, ES, or SR bands.
The Security Interface Extension ACS tests the following security related interfaces:
- Authenticated variables
- Secure Boot variables
- Secure firmware update using update capsules
- For systems with TPMs, TPM measured boot and the TCG2 protocol
This section describes the steps to build the ACS or obtain the pre-built live image.
- Code Quality: v1.1.0
- The latest pre-built release of the Security Interface Extension ACS is available for download here: v22.10_SIE_REL1.1.0
- The Security Interface Extension tests are written for version 1.1 of the BBSR specification.
- The compliance suite is not a substitute for design verification.
- To review the ACS logs, Arm licensees can contact Arm directly through their partner managers.
- New Features
- New features in this release include tests for the UEFI Image Information Execution table and TPM-based measured boot.
- Limitations
- This release is limited to the Security Interface Extension ACS tests only. It is not supported to use this release for SystemReady ES and IR band testing. See the SystemReady ACS page for links to the latest SystemReady IR and ES tests.
- To pick up the latest stable version of the code, checkout the release tag v22.10_SIE_REL1.1.0
- Pre-built images for each release are available in the prebuilt_images folder. You can either choose to use these images or build your own image by following the steps below.
- To access the prebuilt_images, click this link : prebuilt_images
- If you choose to use the pre-built image, skip the build steps and jump to the test suite execution section below.
Before starting the ACS build, ensure that the following requirements are met:
- Ubuntu 18.04 LTS with at least 64GB of free disk space.
- Must use Bash shell.
- User should have sudo privilege to install tools required for build.
- git must be installed in order to clone the ACS repo.
-
Clone the arm-systemready repository
git clone https://github.com/ARM-software/arm-systemready
-
Navigate to the SIE/scripts directory
cd arm-systemready/SIE/scripts
-
Run get_source.sh to download all related sources and tools for the build. Provide the sudo permission when prompted
./build-scripts/get_source.sh
-
To start the build of the Security Interface Extension ACS live image, execute the below step
./build-scripts/build-security-extension-live-image.sh
-
If all of above steps are successful, the compressed, bootable image will be available at:
/[path-to-arm-systemready]/SIE/scripts/output/sie_acs_live_image.img.xz
This image comprises of two FAT file system partitions recognized by UEFI:
- 'acs-results'
Stores logs and is used to install UEFI-SCT. (Approximate size: 128 MB) - 'boot'
Contains bootable applications and test suites. (Approximate size: 500 MB)
The test suite consists of both automated and manual tests. See the Security Interface Extension ACS Users Guide for addition information.
-
UEFI Self Certification Tests (UEFI-SCT) TAG: 421a6997ef362c6286c4ef87d21d5367a9d1fb58
Arm SystemReady Security Interface Extension ACS test suite may run at a higher privilege level. An attacker may utilize these tests as a means to elevate privilege which can potentially reveal the platform security assets. To prevent the leakage of secure information, it is strongly recommended that the ACS test suite is run only on development platforms. If it is run on production systems, the system should be scrubbed after running the test suite.
System Ready ACS is distributed under Apache v2.0 License.
- For feedback, use the GitHub Issue Tracker that is associated with this repository.
- For support, please send an email to "[email protected]" with details.
- Arm licensees can contact Arm directly through their partner managers.
- Arm welcomes code contributions through GitHub pull requests.
Copyright (c) 2022-2023, Arm Limited and Contributors. All rights reserved.