Technical Specifications of the System
| Parameter | Basic | Extended | Individual |
|---|---|---|---|
| Stored Incidents | 500,000 | 1,000,000 | 1,000,000+ |
| CPU | 2 | 4 | on request |
| RAM | 16 GB | 48 GB | on request |
| CPU Cores | 8 | 16 | on request |
| Storage | 60 GB | 80 GB | 80 GB + 1 GB/50,000 incidents |
| Data Channels | 100 Mbps | 100 Mbps | 100 Mbps |
| System Software | Windows/Unix + Docker | Windows/Unix + Docker | Windows/Unix + Docker |
| Middleware | Docker Compose/K8s | Docker Compose/K8s | Docker Compose/K8s |
Processing speed - 50,000 incidents per minute
Calculations and Recommendations for Database Sizes
The following databases (DBs) are used in TRON.ASOC to store data, events, files, etc.:
- PostgreSQL - storing data for system formation (core entities used in the system)
- Clickhouse - storing data for system formation (the total number of security issues found during scans, as well as the number of issue changes (events) within the actions performed (triage) on vulnerabilities).
- MinIO - storing files in custom fields of projects and reports generated by the user.
❕ To ensure database backup and recovery, additional disk space must be allocated. The recommended volume is from double (x2) to triple (x3) the size of the database. A more precise coefficient is determined by the backup policy parameters.
Below are the recommendations for disk space for the used databases (calculated per month, according to the number of stored incidents from the table above).
| DB | Basic | Extended | Individual |
|---|---|---|---|
| PostgreSQL | 4-5 GB | 8-10 GB | 10 GB+ |
| Clickhouse | 8-10 GB | 16-20 GB | 20 GB+ |
| MinIO* | 5-6 GB | 10-12 GB | 12 GB+ |
*Calculations for MinIO are performed considering the average size of one file - 50 MB.
When calculating for a year, it is recommended to allocate x12 according to the table above.
Example limits for the Basic system characteristic for 1 year:
- PostgreSQL = 50 GB
- Clickhouse = 100 GB
- MinIO = 60 GB