Prepare an audit
Gather the objects in scope, the applications and their dependencies in one shared base. Identify missing information before the review and give the people involved a consistent reading of the information system.
- Define the scope of the review.
- Check the objects, their attributes and their relationships.
- Prepare the views needed for the discussions.
Prepare a migration or a server decommissioning
Before changing a component, examine its documented relationships with applications, flows and infrastructure. This reading helps identify the points to check with the teams in charge.
- Identify the component concerned.
- Examine its known dependencies.
- Confirm the relationships with the owners before the change.
Document dependencies for a DRP/BCP
Link business processes to the applications and infrastructure that support them. This knowledge helps teams discuss recovery priorities. Recovery objectives, procedures and tests remain to be defined as part of your continuity approach.
Share knowledge of the information system
A shared map makes discussions easier between colleagues who do not have the same level of technical understanding. It helps explain a scope to a newcomer and document knowledge that was previously scattered.
Turn findings into actions
With Studio, prioritise risks by business impact, identify personal data and simulate the loss of a component. After review, findings can become planned, assigned and dated actions. The fictional case of Aurelia Diffusion illustrates this journey with an IT department and a CISO.