Security
Assess weaknesses that could expose the application and its data. Review access, interfaces and protective measures within the agreed scope.
Documented findings, remaining checks and actions to prioritize.
Our approach
Connect application knowledge to industrial decisions.
Chrysalid structures a shared approach for business teams, IT and decision-makers. Scope, requirements and expected evidence are defined during scoping with your business teams and our experts.
Three dimensions of the assessment.
Application value is considered alongside its ability to remain secure, maintainable and useful to operations.
Strategic viability
Anticipate obsolescence, end of support and loss of expertise. Assess dependencies on technologies, vendors and key people.
Milestones and dependencies that may constrain the company’s future choices.
Operational continuity
Relate application criticality to business usage. Review the impact of unavailability and the arrangements for maintaining or recovering operations.
Functions to preserve and continuity requirements to validate with the teams.
Verified findings, assumptions and missing information remain distinct. The assessment relies on accessible evidence and team validation; it is not, on its own, a security certification.
IdentifyAssessPrioritizeDecideGovern
- Our actionsOur commitments
Identify
Map critical applications, business usage, interfaces and ownership.
Shared knowledge of the current environment and its application dependencies.
- Our actionsOur commitments
Assess
Distinguish business value from security, obsolescence and continuity weaknesses. Identify what remains to be verified.
Evidence-based findings and a risk assessment.
- Our actionsOur commitments
Prioritize
Rank interventions by their criticality, operational continuity deadlines, support level and operational maintainability.
A list of applications ranked by change priority and operational deadlines, jointly validated with the application owners.
- Our actionsOur commitments
Decide
For each application, compare retaining the existing application with replacing it, according to risks, requirements and resources needed.
A documented decision and its acceptance conditions.
- Our actionsOur commitments
Govern
Update risks, ownership, action plans and decisions through agreed reviews.
Lifecycle oversight and a three-to-five-year investment roadmap.
Four possible decisions for each application.
Age alone does not justify transformation. Retention remains an option when no intervention is warranted. When modernization or replacement is being considered, the documentation review prepares the choice of target.
Retain
Keep a useful application when its risk level is acceptable, with defined review conditions.
Secure
Address technical or organizational weaknesses while preserving business functions.
Adapt
Change selected workflows or interfaces to meet business needs and target requirements.
Document
For each application, we complete your existing documentation by describing the functionality in use through mockups, together with its business rules.
A shared functional baseline before selecting the target.
Modernize
Use this documented baseline to prepare component upgrades or a partial or complete rewrite, according to the needs identified.
Replace
Use the mockups and business rules to seek a market solution through targeted vendor selection.
A functional target to prepare worthwhile changes.
When a change is being considered, a functional mockup for each in-scope application clarifies workflows, rules and interfaces to retain or modify. It completes existing documentation and supports adaptation, a partial or complete rewrite, or the search for a market solution through targeted vendor selection.
The upgrade plan specifies target requirements and acceptance criteria. The mockup does not replace technical testing or acceptance of the final application.
Inform an acquisition beyond its budget.
For investors and M&A teams, the assessment relates application risks, operational continuity, integration choices and required investment. Costs, timelines and residual risks are compared for each option.
Cost estimates document scope, assumptions, exclusions and uncertainty. They distinguish upgrade or integration costs from recurring costs. They complement risk and business-value assessment rather than determine the decision alone.