Glossary

Asset: An asset is a valuable resource that must be properly maintained and managed. The state of an asset must be carefully monitored and controlled to prevent vulnerabilities or errors from causing harm or decreasing an assets value.
CI: Continuous Integration: process that automates the integration of new changes to the repositories. More information here.
Code Owner: High-level role in the administration of a repository, marked and invited by a maintainer to oversee the development of one or multiple subsystems in a repository. More information here.
Developer
Contributor: Internal or external developer that in any way contributes to the project. More information here.
Maintainer: Top-level role in the administration of a repository. More information here.
MISRA: Set of software development guidelines for the C programming language developed by The MISRA Consortium and followed by the Bao project. More information here
PACV: The Partition Access Control Vector (PACV) is a data structure that contains the access control policy for a system’s partitions. This policy establishes the permissions for each partition to access the platform’s resources.
PIV: The Platform Initialization Vector (PIV) is a data structure that stores information regarding the initialization state of different system components at both the CPU and platform level.
PR: Pull-Request: changes to be pushed into a branch of a repository. More information here.
Subject: A subject is an entity that can access or interact with a system, its resources and its assets. This can include individuals, other systems (e.g., through a remote connection), and specific system components such as VMs and VMMs.
VM: A Virtual Machine (VM) is a software-emulated environment that runs programs, including operating systems, as if they were executing directly on physical hardware. VMs are created and managed by a hypervisor, which enables the consolidation of multiple VM-based isolated systems on a single platform.