The DBMS-iTC develops internationally agreed Common Criteria security requirements and evaluation activities for database management systems, their cryptographic protections, and their tenant-operated and provider-operated cloud deployment models.
Current evaluation baseline DBMS cPP Version 2.0 and Supporting Document Version 2.0. |
DRAFT MODULE REVIEW PP-Modules and PP-Configurations Version 0.5 Crypto + Cloud and Crypto + DBaaS review families; not an authoritative release. |
-
Version 2.0 authoritative documents
Current evaluation baseline and release history -
PP-Configuration architecture
Base, Crypto, Cloud, and DBaaS composition -
Technical Decisions
No Technical Decisions issued for Version 2.0 -
Document source repository
AsciiDoc sources and issue tracking -
Common Criteria Portal
DBMS-iTC community page -
Contribute or contact the iTC
Use GitHub Issues or Discussions
1. Introduction
The Database Management Systems international Technical Community brings together Certification Bodies, Common Criteria laboratories, vendors, government participants, and subject-matter experts to create requirements for repeatable database security evaluations.
The DBMS protection-profile family is being organized around a stable Base cPP and two composed module families: Cryptographic Functions + Cloud for tenant-operated deployments, and Cryptographic Functions + DBaaS for provider-operated managed services. PP-Configurations define the valid combinations presented in a Security Target.
2. Current Status
The site presents three separate publication states:
-
Authoritative release identifies Version 2.0, the documents currently published for evaluation use.
-
Archived baseline identifies the superseded Version 1.3 cPP and Version 1.1 Supporting Document, retained for traceability.
-
Draft module review identifies the complete Version 0.5 Crypto + Cloud and Crypto + DBaaS review set. It is available for feedback but does not replace the authoritative Version 2.0 Base-document set.
4. Module Review: Full PP-Module and PP-Configuration Set Version 0.5
FULL MODULE SET — PUBLIC REVIEW DRAFT 1
- Publication date
-
30 June 2026
- Last revised
-
20 July 2026
- Review phase
-
Public Review Draft 1
The coordinated review release contains all three PP-Modules, all three Supporting Documents, and all three PP-Configurations. The deployment-oriented review is organized around two complete composition families: Crypto + Cloud and Crypto + DBaaS. The Cryptographic Functions Module is included in both families and is reviewed in the context of each deployment model.
| Review family | Included module documents | Version | PP-Configuration |
|---|---|---|---|
Crypto + Cloud |
DBMS Cryptographic Functions Module and SD; DBMS in the Cloud Module and SD |
0.5 |
Base cPP + Crypto + Cloud |
Crypto + DBaaS |
DBMS Cryptographic Functions Module and SD; Database-as-a-Service Module and SD |
0.5 |
Base cPP + Crypto + DBaaS |
The Crypto-only PP-Configuration remains in the review package as the foundational Base cPP + Crypto composition used by both deployment-oriented families.
5. Security Architecture at a Glance
-
Base cPP — establishes the common DBMS TOE, security problem, core SFRs, assurance requirements, and evaluation baseline.
-
Cryptographic Functions Module — appears in both review families and owns the common cryptographic requirements, protected channels, key-management integration, D@RE cryptography, and the coordinated classical/PQC selections.
-
Crypto + Cloud — combines those cryptographic requirements with the security behavior and evidence for a tenant-operated cloud deployment.
-
Crypto + DBaaS — combines those cryptographic requirements with tenant isolation, provider-role separation, and the evidence model for a provider-operated managed database service.
-
PP-Configuration — identifies the valid Base-plus-module composition claimed by the Security Target.
The interactive review supplement provides a reader-oriented architecture walkthrough and traces SFRs, operations, dependencies, Evaluation Activities, and tests to the owning documents.
6. Technical Decisions
No Technical Decisions are currently issued for Version 2.0. The Version 2.0 document text is authoritative for evaluations.
The legacy TD_DBMS_B_001 and TD_DBMS_B_002 resolutions are incorporated into Version 2.0. Their historical records are retained with the Version 1.3 cPP and Version 1.1 Supporting Document in the archive below.
7. Archives and Previous Versions
Archived material remains available for traceability. These artifacts are neither the current authoritative release nor an active review set, and their presence does not indicate that they are acceptable for new evaluations.
| Document family | Version | Status | Links |
|---|---|---|---|
DBMS Base cPP |
1.3 |
Superseded by Version 2.0 on 17 August 2026. TD_DBMS_B_001 and TD_DBMS_B_002 are archived historical records; their resolutions are incorporated into Version 2.0. |
|
DBMS Supporting Document |
1.1 |
Superseded by Version 2.0 on 17 August 2026. TD_DBMS_B_002 is an archived historical record; its resolution is incorporated into Version 2.0. |
|
DBMS Base cPP and Supporting Document public-review record |
2.0 |
Historical public-review record |
|
DBMS Base cPP |
1.0 |
Previous public release |
|
DBMS Supporting Document |
1.0 |
Previous public release |
|
DBMS PP-Modules and PP-Configurations |
0.4 |
Previous public-review snapshot |
8. Participate and Source Repositories
Public review depends on input from Certification Bodies, laboratories, vendors, users, and researchers. Use a GitHub Issue for a specific document change that should be tracked to resolution, or a GitHub Discussion for a broader design, community, or participation topic.
The PDF, PP-Module, PP-Configuration, and Supporting Document artifacts are authoritative. HTML editions and the requirements-map application are provided to improve navigation and review.