Skip to main content

Overview

The platform is carefully designed with the following goals in mind:

  • easy management of the data
  • extensibility and flexibility
  • technology agnostic
  • easy to use and maintain
  • quick installation

See the development lifecycle for how the platform itself is built, reviewed and evidenced.

Concept of the platform​

It is designed as a microservice architecture with the ability to be flexible in various occasions.

It is based on the principle that the Core is acting as a middleman between the Client and the Connector providing the logic of all operations. The Connector contains the full implementation of a particular technology. It accepts the request from the Core, processes it, and sends back the response in a format the Core can understand. Connector is also designed to be completely independent from other platform components.

Architecture​

The architecture of the platform is based on the following parts:

PartBrief description
DatabaseStores the data. SQL Database is used by default.
CoreThis is the brain of the platform. It contains the full logic of request processing.
InterfacesInterfaces provided and used by the platform.
ConnectorTechnology implementations that interact with the Core to perform the designated operation on the technology.
Access ControlRoles and permissions in the platform.
A^2 EngineA^2 Engine is a component that provides the ability to define and manage attributes.
NotificationsInternal and External notifications.
ApprovalsApproval of operations by designated users before the platform executes them.
SchedulerScheduled execution of platform tasks, such as discoveries and certificate status updates, and their history.
CachingIn-memory caches that keep authentication, authorization and other lookups fast, and when changes take effect.
WorkflowsRules, triggers and actions that automate processing, for example of discovered certificates.
Columns and ViewsColumns, sorting and saved views of the inventory lists.
Post-Quantum ReadinessPost-quantum readiness verdict of every cryptographic asset, decided by rules the platform ships.

See the Architecture Overview for more details about the architecture of the platform.

Core Components​

The platform consists of the following components:

ComponentsBrief description
CredentialStores the credentials for the Connectors.
AuthorityAuthority instances representing access to specific certification authority technology.
RA ProfileRA Profile abstracts the configuration of certificate-related attributes and provides a service for the Clients to manage them.
Compliance ProfileCollection of rules to be applied on a certificate to determine whether it satisfies the organizational compliance policy
EntityEntity representing the end user of the certificates and cryptographic key.
LocationStorage for certificates and keys that the platform manages through an Entity.
CertificateCertificate is an inventory object that contains all information about its lifecycle.
Request AttributeA value the requester supplies when asking for a certificate, mapped to a field of the certificate request.
GroupGrouping allows to manage multiple certificates with the same characteristics.
TokenToken instance representing access to specific cryptographic device or technology.
KeyCryptographic key object that can be managed and contains relevant information about its lifecycle.
Token ProfileToken Profile abstracts the configuration of cryptographic service for the Clients to request cryptographic operations.
VaultConnection to a secret provider and the storage where its secrets are kept.
Vault ProfileConfiguration for managing the secrets of a Vault in a more granular way.
SecretA secret stored in a Vault and managed through a Vault Profile.
NotificationNotification instance representing access to specific notification technology.
Notification ProfileWho receives a notification, how it is delivered, and when.
Approval ProfileThe steps and approvers an operation needs before the platform executes it.
CBOMCryptographic Bill of Materials providing inventory and management of cryptographic assets based on CycloneDX specification.
CommentMessages attached to an inventory object, with threads and notifications.

Modules​

Platform modules provide the following functionality:

ModuleBrief description
Certificate ManagementProvides certificate lifecycle management functions.
Certificate InventoryInventory of all certificates that are consistently visible and managed.
DiscoverySearching for certificates and keys in various sources, providing detailed results about what was found.
DashboardsVisual dashboards providing quick information about the current state of the inventories.
Key ManagementProvides key lifecycle management functions and cryptographic operations.
Key InventoryInventory of all keys that are consistently visible and managed in technology-agnostic way.
Secret ManagementProvides secret management operations across vault technologies.
Secret InventoryInventory of all secrets that can be managed by the platform.
Cryptographic Asset InventoryInventory of the cryptographic assets declared by the synchronized CBOMs, each listed once.