Meeting the requirements for information protection
One app supports several algorithm suites. Your organisation turns on the one its regulator requires – with no separate version of the app and no “negotiating” down to a weaker option.
Meets the requirements of your country
The suite is chosen in CUBRA Console and applies to the whole organisation. We go through certification together with the customer.
Ukraine
- Ukrainian national DSTU standards for encryption and hashing
- Requirements of the State Service for Special Communications of Ukraine
- Ready for expert review and attestation of an integrated information security system (KSZI)
European Union
- Recommendations of BSI (Germany) and ANSSI (France)
- Post-quantum protection following the recommendations of European regulators
- Ready for Common Criteria certification (EUCC scheme)
USA and NATO
- Requirements for national security systems
- Strengthened post-quantum suite
- Ready for FIPS 140-3 cryptographic module validation
Minimal data – by design
- Keys stay only on people’s devices, not on the server
- The server does not know who is writing to whom
- Event log for audits – without message content
- A CUBRA Node on your premises: data does not leave your organisation
Working without the internet
For networks separated from the internet, the licence and updates are delivered as a file, and messages go through the one-way CUBRA Offline Gateway, which holds no keys (CUBRA Offline Gateway — after release).
How algorithm suites work
Each algorithm suite in CUBRA has its own number. The administrator chooses a suite in CUBRA Console, and it applies to everyone in the organisation. Devices do not “negotiate” down to a weaker option: if the other person does not support the required suite, the app will tell you so plainly instead of silently switching to another one. People can see in the conversation which protection suite is in use.
An organisation can have several suites – for example, a national one for internal correspondence and an international one for partners abroad. Any weakening of protection happens only with explicit consent and is available only to regulated organisations that are required to do so by law.
Attestation and expert review: how we help
- We prepare documentation for the cryptographic core and products to the extent the regulator requires.
- We deploy the system the way attestation requires: on your premises, in a closed network, with the required algorithm suite.
- We go through the expert review together with the customer and answer the experts’ questions.
- We keep an event log for audits – without message content.
Personal data: protection by design
Personal data protection laws – in Ukraine and in the EU – require you to collect only what is necessary and to protect what you collect. CUBRA is built exactly this way: only the people in the conversation can see what is written, the server does not know who is writing to whom, and service data is limited to exactly what delivery needs. For organisations we prepare a data processing agreement (DPA), and a CUBRA Node on your premises keeps data inside the organisation.
Where a regulated organisation should start
- Determine which requirements your system has to meet: national, European or your partners’ requirements.
- Tell us about them – we will choose an algorithm suite and a deployment scheme.
- Start with a pilot group of employees while preparation for attestation is under way.
- Expand the system without reinstalling – the licence is based on the number of people.
Requirements by industry
Banks and insurers answer to the financial regulator for protecting customer data and keeping services running. Hospitals answer for patient confidentiality. Government bodies answer for protecting official information and for system attestation. Energy, water and transport answer for the resilience of critical infrastructure. For each of these industries we have gathered typical risks and protection schemes on separate pages – from finance and healthcare to the public sector and energy.
Common to all: requirements are easier to meet when the content of correspondence is technically inaccessible to anyone except the people in the conversation, and the event log shows who did what in the system without message content. A regulator’s inspection then comes down to documents and the log, not to the question of who had access to the correspondence.
Documents we provide
- A description of the system architecture and of which data is stored where.
- A list of algorithm suites and the standards they are based on.
- A threat model and a description of the protection mechanisms – to the extent needed for expert review.
- Administrator and user guides in Ukrainian.
- A data processing agreement (DPA) and a privacy policy.
- A description of internal testing and, after release, an independent audit report.
Keys under your organisation’s control
Correspondence keys exist only on people’s devices. The service keys of a CUBRA Node are protected by enclosure sensors, and restoring operation after an incident requires the consent of several trusted people in the organisation. The licence works without a network connection and does not depend on our availability: even if the connection with us is lost, your system will keep working, and messages you have received will always open (case sensors — after release).
Frequently asked questions about regulatory requirements
Can one organisation have several algorithm suites?
Yes. For example, a national suite for internal correspondence and an international one for partners abroad. People can see in the conversation which suite is in use.
Does CUBRA work in closed networks without the internet?
Yes. The licence and updates are delivered as a file, and communication between closed networks goes through the one-way CUBRA Offline Gateway (CUBRA Offline Gateway — after release).
Can CUBRA hand over correspondence at the request of the authorities?
No: we do not have the keys to your correspondence – they exist only on people’s devices. How we respond to requests from authorities is described in our legal information.
How long does preparation for attestation take?
It depends on the class of the system and the regulator’s requirements. A pilot group can start straight away, and attestation can run in parallel – without interrupting people’s work.
Can the system be deployed entirely on our own premises?
Yes. The CUBRA Node or cluster sits with you, the licence works without a network connection, and updates can be delivered as a file. No external servers are needed for it to work.
Who in the organisation chooses the algorithm suite?
The administrator, in CUBRA Console, and risky changes to settings are confirmed by several people. Every change is recorded in the event log.
Can employees see which protection suite is in use?
Yes. Every conversation shows which protection suite is in use, so people know their correspondence meets their organisation’s requirements. If the other person does not support the required suite, the app will say so plainly instead of silently switching to a weaker one.
Is CUBRA suitable for organisations in the EU?
Yes. There is an algorithm suite based on the recommendations of European regulators, and for personal data processing we prepare a DPA.
Is CUBRA certified?
The products are built in line with the requirements and are ready for certification. We go through certification for a specific system together with the customer – in the way the regulator of their country requires.
Can CUBRA’s own cipher be turned off if the regulator requires national algorithms only?
Yes. The administrator chooses the mode in CUBRA Console, and people can see in the conversation which protection suite is in use.
Will this help with personal data protection requirements?
CUBRA collects only what the service cannot work without, and the content of correspondence is available only to the people in the conversation. For organisations we prepare a data processing agreement (DPA) – see our legal information.
Tell us which requirements you need to meet
We will choose an algorithm suite and a deployment scheme to suit your regulator.