Architecture
Architecture
Overview
We use the C4 Model for diagrams throughout the documentations.
Xenguard is designed with modularity and composibality in mind. Its components are self-contained and the communication succeeds over well-defined interfaces. The diagram above gives an overview of the components (click for an interactive version). Each component is described on its own page, linked below.
Important
The terms Software System, Container, Component, and Code has concrete definitions in context of the C4 Model. See here for more.
Containers
In the C4 Mode, containers are defined as follows:
A container is essentially a runtime boundary around some code that is being executed or some data that is being stored.
For each container, we use three badges:
- : Container has an external interface (e.g., to developer).External
- : Container does not provide any external interface.Internal
- : Container can be configured (e.g., by Admin).Configurable
Note: The containers are listed in alphabetical order and not significance.
InternalConfigurableInspects an artifact and generates a report, e.g., an SBOM.
InternalConfigurableRecords the signals emitted by the proxy and correlates them with analysis data.
InternalConfigurableManages identities and evaluates security and compliance policies.
ExternalAdministrative interface, available as Web GUI and on the command line.
InternalConfigurableStores analyzer results so an artifact is never inspected twice.
ExternalShows developers and admins the events and activities on Xenguard.
ExternalCentral coordination unit and point of entry for users.