IDMS database sizing guidance
IDMS Storage Description
The IDMS stores information pertaining to the user’s identity details, proofing life cycle state, and credential status. Additionally, organization information for security, data sources and reporting are also stored. The table below provides a listing of the estimated data sizes for each category of data.
Storage Considerations
Identity data: The table below lists the type and size of data stored for each user that is proofed and credentialed.
Data Storage Type | Description | Size |
|---|---|---|
Biographic Information | Name, email, organization | 1MB |
Fingerprint capture | Fingerprint captures (rolls, flats, 378 templates) | 9MB |
Photo capture | Facial image of individual | 1MB |
Document capture | I-9 Document capture of individual | 10MB |
| Organization specific documents | Supplemental documentation for organization specific proofing requirements | 4MB |
| Handwritten capture | Image of the handwritten signature capture | 2MB |
Certificates and state information | Base64 encoded certificates; credential state information | 2MB |
Average Total Storage Per User | 29MB per person | |
Database sizing modeling
When planning the size of the database for the installation, the following model can be used to set the initial size of the database.
| Data Storage Type | Will be captured | Size |
|---|---|---|
| Biographic Information | YES | 1MB |
| Fingerprint capture | NO | |
| Photo capture | NO | |
| Document capture | YES | 10MB |
| Organization specific documents | YES | 4MB |
| Handwritten capture | YES | 2MB |
| Certificates and state information | YES | 2MB |
| State Tracker | YES | 1MB |
| Audit Events | YES | 1MB |
| Average MB Total Per User | 21 | |
| x Planned users | 10,000 | |
| Minimum Initial DB size recommended | 210 GB | |
Growth settings
To accommodate for future growth, it is recommended the organization factor in their future credential growth numbers to set the auto growth accordingly. For example, if the organization plans to enroll 50 more users a month, the auto growth setting should be set to 1 GB, if they are planning 500 more users a month, then the auto growth setting should be 10 GB.
IDMS configuration settings: The table below lists the type and size of data required for IDMS configuration and security needs.
Data Storage Type | Description | Size |
|---|---|---|
Authentication and authorization | Certificate serial number, role information, user ID, account state | 2MB/Operator |
Data source | Configurations for directory, database, mail server | 1MB/Data Source |
Reporting: The data stored for reporting needs. Note that the size of the data is also depended on the numbers of queries executed. Each query also generates security events which impact the size the data required.
Data Storage Type | Description | Size |
|---|---|---|
Id State Tracker | Tracks the user’s individual state changes. | 1MB/ entire life cycle tracked |
General Audit events | Tracks various security events | .05 MB/ entire life cycle tracked .05 MB/ per operator query |
Memory and Processor Considerations
The memory and processing requirement is dependent on the issuance model implemented by the organization. The tables below detail the IPE transactions and the general recommended memory and processor guidance based on issuance model.
Identity Processing Event | Description |
|---|---|
Biometric acquisitions | Identity data such as photo, fingerprints and I9 documents are sent from the biometric capture stations to the database. |
Approvals | Identity data such as photo, fingerprints and I9 documents are fetched from the database and presented to the web user interface. |
CMS Provisioning | Identity data including the photo and fingerprint data is fetched from the database and sent to the CMS |
CMS Encoding | Credential data from the CMS is sent to the IDMS and stored in the database. |
Reporting | Log information is fetched from the database and presented to the web user interface or API. |
In this context, an issuance model is an architecture that is implemented to perform the necessary IPE transaction to proof the user, issue a credential and monitor the system. The table below describes common issuance models and the recommended processing needs.
Issuance Model | Minimum Recommended Memory | Minimum Recommended Processor Speed |
|---|---|---|
Single capture and encoding station | 4GB | X64 2.3GHZ |
4 capture and 4 encoding stations | 8GB | X64 2.5GHZ |
10 capture and 10 encoding stations | 16GB | X64 2.9GHZ |
25 capture and 25 encoding stations | 64GB | Intel Xeon E5-2676 |