Restricted software migration
Migration from CryptoPro, MaxPatrol and Secret Net
We plan the replacement of cryptography and cybersecurity platforms while preserving required data, integrations and transition control.
Discuss your project →What the migration covers
We begin with an inventory of products, versions, servers, workstations, integrations and process owners. Inclusion in the official list is a reason to review the environment, but it does not automatically determine the target. Selection follows functional, security, operational and budget requirements.
- certificates, key workflows and trust chains
- correlation rules, policies and exceptions
- log sources and directory integrations
- VPN, access, WAF and response requirements
How the target is selected
We create a vendor-neutral requirements matrix covering critical functions, formats, APIs, hosting, support, export and team capability. Alternatives are tested on a control set before bulk migration. No single product is presented as a universal replacement for every organisation.
Validation and handover
Cryptographic keys are not automatically portable across incompatible systems. We first design the new trust environment, parallel period, re-issuance where required and validation of every critical integration.
Fit before scope
Is this the right starting point?
Use these criteria for an initial orientation. The final recommendation follows a review of your context, data and constraints.
A good fit when
- Software is restricted, unsupported or creates operational risk
- Data, history and integrations must be preserved
- Process and acceptance owners are available
Resolve this first when
- Only licence procurement is required without dependency analysis
- A target was selected without validating processes and data
- No one owns reconciliation and the cutover decision
A verifiable first stage
What you can use to make the next decision
The exact scope is agreed before work begins. These are typical decision artefacts, not promised business results.
Dependency inventory
Versions, users, processes, data, integrations and critical support dates.
Replacement-wave plan
Target options, sequence, parallel operation, training and rollback path.
Acceptance rules
Reconciliations, control operations and evidence your team will use to approve the result.
Five questions · no datasets or credentials
Support calendar
Examples from Ukraine's official list
| Product or group | Status |
|---|---|
| КриптоПро CSP / DSS | Listed |
| MaxPatrol SIEM / VM | Listed |
| Secret Net | Listed |
| Континент VPN / WAF | Listed |
Sources: Ukraine's State Service of Special Communications - open list, page dated 5 August 2026
Frequently asked questions
Frequently asked questions
Must everything be replaced at once?
No. Inventory defines waves based on criticality, dependencies, export feasibility and change windows.
Does listing mean a fine for every private business?
This page makes no such conclusion. Scope and obligations depend on the organisation and applicable rules. Seek qualified legal advice for a legal assessment.
How is migration completeness demonstrated?
Control samples, quantitative reconciliation, critical scenarios and an acceptance record are agreed before migration.
Ideas on this topic