Open Source Project Idea: Security Asset Database for Keys, Certificates, Secrets, and Policies

Updated: 03/18/2024

I found an excellent candidate for the underlying database technology:


This component is conceptualized as a secure and reliable database system, specifically designed for managing sensitive information such as encryption keys and secrets.

Essential Requirements

The essential requirements for this database include:

Durability

Guarantees that keys and secrets are preserved without loss, using advanced data persistence methods to withstand failures. For example, S3 offers an SLA of 11 nines, while Spanner provides a five-nine SLA.

Reliability

Ensures continuous service availability, engineered to be always accessible to meet the demands of critical operations.

Read Efficiency

Facilitates the swift retrieval of secrets and decryption of keys, minimizing latency to enable immediate access and use of secure data.

Write/Update Consistency

Prioritizes strong consistency for write and update operations. Although these processes may be slower, they must ensure complete data integrity and consistency across the system.

Multi-Tenancy and Data Isolation

Supports access for multiple users or tenants while ensuring strict data isolation, providing secure and separate environments for each tenant’s data.

Why FoundationDB?

FoundationDB emerges as an excellent choice for this security asset database because it:

  • Provides ACID transactions with strong consistency guarantees
  • Offers excellent scalability and performance characteristics
  • Has proven reliability in production environments (used by Apple for iCloud)
  • Supports multi-tenancy through its key-value abstraction
  • Provides the durability and availability required for critical security infrastructure

This makes FoundationDB an ideal foundation for building a comprehensive security asset management system that can handle the demanding requirements of enterprise security infrastructure.