Recommendation : 1. Reduce the impact of data from its storage and access
Can data be backed up incrementally ?
What is the cumulative volume of backups over a month?
One piece of data might be present in several different environments, notably on each backup. This will consume space and transfer flows if the backups are outsourced. The presence of unmodified data on all sets of backups brings very little value compared to the cost involved. Incremental backup solutions should be implemented to reduce the impact of this essential security.
Rule for assessing the level of compliance of the criterion
0 / 0
19 other criteria related to the recommendation: Reduce the impact of data from its storage and access
Is the number of requests kept to a minimum (no looping) ?
Is an alternative to SQL queries used when possible (local storage or similar) ?
Do implemented queries use joins rather than multiple queries ?
Is the removal of obsolete data being managed ?
Are database indexes consistent with operations ?
Is an alternative to the relational model being considered ?
Is a NoSql solution more efficient than its relational equivalent ?
Have the different data access solutions (queries, triggers, stored procedures) been tested ?
Are EXPLAIN clauses used on "Slow queries" to optimize indexes ?
Are the slow query detection thresholds set effectively ?
Are "live" and "dead" data handled differently (eg: Slow storage for "dead" data) ?
Is frequently accessed data available in RAM ?
Are data replications between multiple Database Engine (Cluster) instances appropriate for sensitivity and availability requirement ?
Does the data have an expiration date when it is deleted ?
Is sensitive data collected ?
Is the data collected really useful ?
Does the API provide limits, filters and the list of fields to return ?
Is sensitive user data secure ?
Does regulated data (personal, health, financial) comply with the recommendations for structuring these categories of data ?