Technical and regulatory foundations

Security and cyber resilience

Before deployment, we define who may work with data and tools, where processing may occur and how critical operations can be traced. We take the same care with information about our people, clients and projects.

What we verify by design

The checks for each deployment reflect data sensitivity, risk and the approved operating environment.

TLS · IPsec

Encryption in transit

TLS 1.3 is the baseline for new systems. We use TLS 1.2 for justified compatibility with suites that meet the security policy. Legacy versions and weak ciphers are removed. A restricted network may require an approved IPsec tunnel and mutual certificate authentication (mTLS).

Zero Trust · MFA · PKI

Identity and access

Access decisions draw on identity, permissions, resource sensitivity and available signals about device health. Partner access is designed around organisational SSO and phishing-resistant multifactor authentication such as a FIDO2 security key or an appropriate passkey. Departmental systems may require smart cards and organisational PKI.

EU/EEA · KMS · HSM

Data storage and protection in the EU/EEA

We design client deployments for cloud regions in the EU/EEA or for the client’s own infrastructure. Applicable law and the contract determine where data can be stored, processed and backed up. The deployment can be restricted to a specified country. Where remote access or another flow of personal data constitutes a transfer outside the EEA, we assess whether the transfer is permitted and what safeguards Chapter V of the GDPR requires.

We use TLS to protect data in transit and encrypt data at rest, including backups. Before deployment, we define who manages the encryption keys and who can use them. The project may call for a hardware security module (HSM) to protect the keys.

Only authorised people and services have access, limited to what their role requires. Our staff and approved suppliers can access data only as needed for agreed work or support. We record access as specified for the project.

We do not use client data to train or fine-tune our own models or third-party models without the client’s explicit permission.

RBAC · HITL

Limits on models and agents

Agents receive only the data and tools needed for a defined task. Changes with material consequences require human approval. Audit records capture the sources, decision, approval and action needed for later review.

EDR · SBOM

Resilience and incident response

Acceptance checks cover endpoint health, containment and recovery from backups. Operational requirements cover vulnerability fixes, software bills of materials (SBOMs), build provenance and secure incident reporting.

Requirements by jurisdiction and contract

Before each engagement, we identify the applicable laws, contractual controls and evidence to provide. The overview draws on public sources.

Czech Republic

Act No. 264/2025 Coll. and implementing rules set obligations according to the scope and regime of a regulated service. For public-sector cloud use, check the applicable DIA catalogue listing and security level. Only a state cloud provider can serve the critical level. Citizen Identity methods include the eGovernment Mobile Key, NIA ID, electronic identity cards and bank identity, subject to the participating service. Under Act No. 412/2005 Coll., classified information requires attention to NÚKIB certification of the specific information system, approval to operate, cryptographic, physical and personnel safeguards, and protection against compromising emissions (TEMPEST) where applicable.

European Union

For NIS2 we check the national implementation relevant to each country, service and supplier role. Under GDPR we assess permissible transfers, for example an applicable adequacy decision, the EU–US Data Privacy Framework for participating recipients or standard contractual clauses (SCCs). AI Act duties depend on the system’s intended use, risk and the organisation’s role. We track EUCS as ENISA’s candidate scheme for cloud services.

Germany

BSI IT-Grundschutz supports the design and assessment of information security. BSI C5 specifies criteria for cloud services. TISAX is a mechanism for assessing and sharing results, principally in the automotive sector. The required scope depends on the buyer and supply chain.

United Kingdom

Some public contracts call for Cyber Essentials, Cyber Essentials Plus or equivalent controls under procurement rules. For personal data processing and transfers we consider the UK GDPR, Data Protection Act and applicable international transfer mechanisms.

NATO and defence procurement

Industrial security and applicable access evidence, such as a Facility Security Clearance, are assessed against classification and contract. The applicable CIS rules determine security requirements for communications and information systems. Contracts may cite AQAP 2110 for quality assurance, AQAP 2210 for software or AQAP 2310 for aviation, space and defence.

Standards and independent assurance

For information security and AI management systems we use ISO/IEC 27001 and ISO/IEC 42001 requirements as references. Depending on the engagement, BSI C5 or SOC 2 Type 2 reports may be relevant when assessing cloud suppliers. Evidence is evaluated against its scope, validity and the controls it covers.

How we evaluate the design

Research and technical specifications inform how we assess model risks, verify access and establish where outputs came from.

AI search on ZOXIVA

Ask in your own words or filter by topic. Search covers our public pages, and your query stays in your browser.

Filter by topic