This is the root of OpenBMC security documentation.
The audience is the OpenBMC development team, projects that use OpenBMC, and IT security professionals. Readers are assumed to have general familiarity with the firmware development process and with OpenBMC's capabilities.
Security is broadly defined to mean avoiding negative impacts to the confidentiality, integrity, and availability of the BMC's resources. Resources include information stored by the BMC and its capability to control itself and its host server.
The documentation begins with stories that parallel OpenBMC development activities. The stories capture the essence of each activity, identify security risks, and explain how OpenBMC addresses those risks. Conceptually, all other security work is rooted in these stories.
The content and depth of the information presented here is primarily intended to foster the development of secure OpenBMC implementations. It may also be useful in formal security evaluation processes such as Common Criteria.
OpenBMC Server Security Architecture. This describes OpenBMC's security features including what OpenBMC does to protect the BMC against security threats. Features include user authentication, transport level security, and secure boot. Example components include:
OpenBMC development team security practices. This highlights specific practices the development team uses to help ensure only reliable, reviewed, tested code goes into the OpenBMC project. Example topics include:
OpenBMC downstream security best practices. This talks about how to protect the BMC from security threats that develop over its lifecycle spanning firmware development, building the install image, provisioning, operation, and decommissioning. Example topics include:
The OpenBMC team has established the following processes: