Recommendation: 7. Associate data, flows, applications and security to allow their identification and traceability
Is each component deployed qualified from the point of view of its lifespan, and are the deprovisioning procedures systematically expressed ?
Life cycle
B People
B Planet
B Prosperity
Difficulty
*
Priority
Medium
Recurrence
Periodic
Tests
What lifespan is associated with each component?
How often is expired data reviewed?
Precisions
All the resources of a component must be managed and a lifetime, a withdrawal process must be in place. These elements must also take into account recurring processing (batch, CRON, etc.), data and backups. Maintaining or forgetting inactive components on production systems is both a waste of resources, but also a weakness in security.
Use Case
Each items refered in technical documentation have an End Of Life information
Additional elements
Operational issues related to the project
Rule for assessing the level of compliance of the criterion
Formalized = 100 ; Planned = 75 ; Identified = 50 ; Ignored = 0 / 100
Life cycle
Fin de Vie
4 other criteria related to the recommendation: Associate data, flows, applications and security to allow their identification and traceability
Software Design Sustainable IT
Has data frugality been incorporated ?
Software Design Sustainable IT
Does the application minimize the data to be exchanged with other applications or users with the use of a flow matrix ?
Software design
Are the security, accessibility, and Responsible Digital aspects treated in the same way for each element of the architecture ?
Software design
Is the traceability of security requirements guaranteed ?