For IT, security, data protection and procurement teams

Security and compliance

Where we process data and who our sub-processors are, who can access the issuer panel, which controls we apply, which continuity parameters we put in the contract and what happens to credentials when it ends. A summary of the Credentium Technical FAQ.

As of 22 November 2026

Request the full technical FAQ

Where the data is and who processes it

Credentium is a cloud SaaS service that CloudTeam runs on Microsoft Azure in the West Europe region. Sign-in and transactional email run on AWS services in Frankfurt. We store production data and backups in the EU, in 4 countries: the Netherlands, Ireland, Germany and Poland. Production runs in a dedicated Azure subscription, separate from the test environments.

Platform components, operators and locations
ComponentOperator / serviceLocation
Issuer panel, wallet, background processingMicrosoft Azure: App Service, Functions, Durable FunctionsWest Europe, the Netherlands
Databases (issuer and wallet, separate)Azure SQL Database, TDE encryption, sign-in through Entra ID onlyThe Netherlands; geo-redundant backups: Ireland
Credential files (PDF, JSON-LD, images)Azure Blob Storage, SSE encryption, RA-GRSThe Netherlands; replica: Ireland
File backup vault (separate tenant)Azure Blob Storage, continuous replication, immutable versionsPoland Central, Poland
Queues, secrets, telemetry and logsAzure Storage Queues, Key Vault, Application Insights, Log AnalyticsWest Europe, the Netherlands
HTTPS traffic: DNS, WAF, TLS proxyCloudflare; processes traffic after decryptionGlobal network, data centre closest to the user; also outside the EEA
Credential file validator (validate.credentium.com)AWS Lambda, S3, CloudFront; uploaded files deleted after 1 dayFrankfurt, Germany; delivered through the CloudFront edge network, also outside the EEA
Accounts, MFA, transactional emailAmazon Cognito, Amazon SESFrankfurt, Germany
Qualified seal, timestampEuroCertPoland
AI template draftAmazon Bedrock (EU inference profile)AWS regions in the EU
Background processing errorsSentry (no personal data)EU ingest, Germany
USOS connector (optional)The university's own infrastructureAt the university
  • Processing outside the EEA

    HTTPS traffic to Credentium is handled by Cloudflare (DNS, WAF and TLS proxy). Cloudflare processes the traffic after decryption, including sign-in data and credential content, in the data centre closest to the user, which may be outside the EEA. The validator is delivered through the Amazon CloudFront edge network, whose locations may also be outside the EEA.

  • Service access and transfer basis

    Providers whose corporate groups are based in the USA (Microsoft, AWS, Cloudflare, Sentry) may have limited remote service access. Data is transferred outside the EEA under the standard contractual clauses (Commission Implementing Decision (EU) 2021/914) with supplementary measures and, for certified providers, also under the EU-US Data Privacy Framework.

  • Roles under the GDPR

    For data in the issuer panel and data passed on for issuing credentials, the institution is the controller and CloudTeam the processor. We sign the data processing agreement as a separate written document. Holders create their wallet accounts themselves; for the data of those accounts, CloudTeam is the controller.

  • Sub-processor list

    The binding, complete list of sub-processors, with the scope of data and locations and also covering email, the ticketing system and providers being phased out, is published on the CloudTeam website. We announce changes 10 working days in advance, and the customer has the right to object.

Identity, roles and audit log

Who can access the issuer panel, what they can do there and where every operation leaves a trace, including those made through the API.

Roles in the issuer panel
RolePermissions
AdministratorFull access: users and their roles, organisation profile, logo and settings, templates, manual and bulk issuing, viewing, searching and revoking credentials, and their audit trail.
ManagerCreating, editing and archiving templates, manual and bulk issuing, viewing, searching and revoking credentials, and their audit trail. No user or organisation management.
OperatorManual and bulk issuing, viewing, searching and revoking credentials, and their audit trail. No template, user or organisation management.
  • Sign-in through your own identity provider (SSO)

    Staff sign in to the issuer panel with their work account through the institution's Microsoft Entra ID (SSO, OIDC); signing in with a Google account is also supported. Disabling the account in the institution's directory closes access to the panel. Nothing changes in the holder's wallet.

  • Mandatory two-step verification

    When staff sign in with a Credentium account, two-step verification (TOTP) in the issuer panel remains mandatory. Two-step verification resets and role changes are recorded in the audit log like any other administrative operation.

  • Four-eyes principle

    Issuing and revoking can require approval by a second person: the request waits until an authorised person approves it.

  • Isolated units

    Faculties and departments work as units with their own templates and participants, isolated from each other. The central administrator has a single view of the whole institution.

  • Corrections in the panel

    The institution corrects the data of an issued credential itself. The credential gets a new seal and keeps its identifier.

  • Scoped API keys

    Keys have a limited scope of permissions and an expiry date, and can be rotated and revoked. We store only their hash. Integrations need only outbound connections from the institution's network.

  • Audit log

    Sign-ins (successful and failed), administrative operations, approvals and API calls attributed to the specific key, each with the actor, time and IP address. The administrator filters the log in the panel and downloads it as CSV, and the institution's SIEM pulls it incrementally through the REST API with a key that has the audit:read scope. We keep the log for 12 months, longer under special terms in the contract.

Security controls

Controls in the development process, in the infrastructure and in vulnerability handling. The platform runs on PaaS services of the cloud providers Microsoft Azure and AWS, which hold ISO/IEC 27001 certificates and SOC 2 reports — these are the providers' certifications, not Credentium's.

Application and infrastructure safeguards
AreaImplementation
Development processReview of every change; protected production branch with required CI checks; deployment through the sandbox, with approval and from the same immutable package.
Code and dependency analysis (SAST, SCA)Semgrep; NuGet and npm dependency scan in which high and critical vulnerabilities block the change; secret scanning of the repository history (gitleaks); Dependabot.
Dynamic testing (DAST)On the sandbox environment, alongside automated tests on every change.
Vulnerabilities and SBOMA written policy with remediation deadlines; CycloneDX SBOM for every release.
WAFWeb application firewall in front of all applications.
Resource protectionA PaaS platform without its own virtual machines, so an EDR agent does not apply. Resources are protected by Microsoft Defender for App Service, SQL, Storage (with file scanning), Key Vault and Resource Manager.
EncryptionTLS 1.2+ and HSTS in transit; TDE and SSE at rest.
Keys and secretsAzure Key Vault with purge protection; managed identities instead of passwords; API keys stored as hashes; RSA 4096, SHA-256 seal with its key in an HSM/QSCD at EuroCert.
Data accessEntra ID identities only, with no passwords or keys; databases reachable only from the application network; deletion locks; HTTP security headers.
Customer separationLogical: an organisation filter in every query; separate issuer and wallet databases.
Infrastructure as codeTerraform, checked with tflint and checkov.
Immutable backups and DRA vault in a separate Azure tenant in Poland with continuous file replication and immutable versions; a disaster recovery plan and a restore drill on production every quarter.
  • Vulnerability remediation deadlines

    Critical: 7 days, high: 30 days, medium: 90 days, counted from confirmation of the vulnerability. Exceptions to the policy are controlled and have a review date.

  • Vulnerability notices

    We inform institution administrators about critical or actively exploited vulnerabilities affecting Credentium within 24 hours of confirmation, with an impact assessment, recommendations and a remediation date, and we confirm closure once the issue is fixed.

  • External reports

    Vulnerabilities can be reported to security@credentium.com, as described in the security.txt file and in the coordinated vulnerability disclosure policy.

CloudTeam staff access to production

Administrative access to production is limited to designated members of the CloudTeam team.

  • Just-in-time access

    Administrative roles are activated through Microsoft Entra PIM for a set time, with a stated reason, and expire automatically. There are no standing owner roles in the production subscription.

  • Strong authentication

    Named Entra ID accounts with phishing-resistant MFA (FIDO2 keys). No shared accounts.

  • Full trail

    Administrative operations in the cloud, database auditing and access to the key vault are recorded in immutable storage (WORM).

  • Institution data

    Staff access an institution's data only when handling its ticket or incident, and the access is noted in the ticket.

  • Vetting and training

    Before granting production access we require references and a certificate of no criminal record for offences against the protection of information. A confidentiality obligation applies, also after the cooperation ends, along with training in cybersecurity and personal data protection once a year.

  • Access reviews

    We review permissions every quarter and revoke access on the day the cooperation ends.

NIS2 and the Polish Cybersecurity Act (KSC)

We help the institution assess the security of the service and document the safeguards in place for the purposes of the Polish National Cybersecurity System Act (KSC): before the decision, in the contract and after deployment.

  • Vendor assessment before deployment

    The IT or security team can review the architecture description, data locations and the sub-processor list before the decision. On request we provide results of automated security tests, a software bill of materials (SBOM) and the record of the most recent backup restore test.

  • Contract documents

    The disaster recovery plan, the vulnerability management policy, the incident handling procedure and the exit plan with the migration procedure are annexes to the contract.

  • Right to audit

    An audit is possible once a year, with 14 days' notice; remotely, and on site where justified. Regardless of this limit, we allow an audit at the request of the institution's competent cybersecurity authority and after a serious incident.

  • Incident reporting

    We report a security incident affecting the service or the institution's data, including a personal data breach, without undue delay, within the period set in the data processing agreement, to the addresses the institution designates. The first notice contains the information the institution needs to report in the S46 system; updates follow, and after a P1 or P2 incident a final report within 10 working days.

  • Working with the institution's CSIRT and SOC

    We classify incidents by priority P1–P4, exchange indicators of compromise and take part in the analysis. Every secured evidence file gets a SHA-256 checksum, and the chain of custody is kept in the incident register.

  • After deployment

    The institution grants and revokes permissions itself, checks who issued or revoked a credential, and pulls the audit log into its own monitoring system (SIEM).

  • High-risk vendors

    No product, service or ICT process used in Credentium, including by sub-processors, is covered by a published decision designating a high-risk vendor under the KSC Act. We follow the decisions published in Monitor Polski and the Public Information Bulletin (BIP); if a decision covers a component we use, we inform institutions within 5 working days of publication and replace it within the period set by the decision.

These measures support the institution's information security management system but do not replace the risk assessment the institution carries out itself. The full technical FAQ maps the requirements of the KSC Act to Credentium's safeguards.

Backups, RPO and RTO

Databases and credential files are protected in layers: point-in-time restore, geo-redundancy and a backup vault in a separate environment in Poland. Recovery objectives are set in the disaster recovery plan.

  • 14 dayspoint-in-time restore of databases and files
  • 12 monthsmonthly backups, stored geo-redundantly
  • 3 EU countriesthe Netherlands, Ireland (replica) and a vault with immutable versions in Poland
  • every quarterrestore drill on production, with a written record
Recovery objectives under the disaster recovery plan
ScenarioRPO (maximum data loss)RTO (time to restore)
Deletion or corruption of dataDatabases: 15 minutes; files: no loss for changes from the last 30 days4 working hours
Loss of the West Europe regionDatabases: 1 hour; files: usually a dozen or so minutes2 working days
Malicious deletion or encryption of dataAs for data deletion2 working days

Most recent restore drill: 13 October 2026, result positive. Records are available on request.

  • Long-term backups

    Weekly for 5 weeks and monthly for 12 months. Data deleted from the system disappears from all backups within 12 months at the latest.

  • Geo-redundancy

    Backups of both databases and a replica of the files in the paired EU region (Ireland).

  • File protection

    Versioning of every file and soft delete for files and containers for 30 days; deletion locks on databases and storage accounts.

  • Vault out of reach of production accounts

    A separate Azure tenant in Poland, with separate accounts, continuous replication of credential files and immutable versions. Taking over an account in the main tenant gives no access to it.

Service availability and SLA

SLA parameters depend on the support package. Standard is included in the subscription; Premium Support is a paid add-on, provided until the end of the contract term. The chosen package and its parameters are written into the contract.

SLA parameters by support package
ParameterStandard (included)Premium Support (add-on)
Monthly availability99.00%, i.e. at most 7 h 12 min of downtime in 30 days99.50%, i.e. at most 3 h 36 min of downtime in 30 days
Support hoursMon–Fri 9:00–17:00, excluding public holidaysP1: every day 8:00–20:00; P2 and P3: Mon–Fri 8:00–20:00
Response time P1 (critical)within 4 working hourswithin 1 hour
Response time P2 (high)within 8 working hourswithin 4 working hours
Response time P3 (standard)within 2 working daysby the next working day
Support channelhelp@credentium.com, support.credentium.com portalDedicated support address
SLA credit (% of the monthly fee)below 99.00%: 5% · below 98.50%: 10% · below 98.00%: 20%below 99.50%: 10% · below 99.00%: 20% · below 98.50%: 35%
  • Availability measurement

    Automatic, published on the public status page: current service status, history and availability. The status page opens an incident by itself after consecutive failed checks and closes it when the service is back.

  • Excluded from measurement

    Maintenance windows announced at least 5 working days in advance, outside 8:00–18:00 on working days, up to 8 hours a month in total; outages at the trust service provider (issuing is then paused and resumed automatically, and verification keeps working); force majeure.

  • Missed availability

    SLA credit according to the package, settled as a reduction of future fees or as additional credentials to issue of the same value, plus a report with the cause and a remediation plan within 10 working days.

  • Common to both packages

    RPO and RTO, backups, vulnerability remediation deadlines and notice of security incidents and personal data breaches (without undue delay, within the period set in the data processing agreement) apply in both packages. The institution reports a suspected incident through its package's support channel, during its support hours.

Data export and the end of the contract

The institution's data is portable. The administrator orders a full export with a single request in the panel: no limit on the number of credentials, regardless of their status, prepared in the background. The export can be repeated throughout the contract, including as a trial run before a migration, and when migrating to another solution we help read the formats.

What the full export contains

  • Sealed JSON-LD (EDC) and sealed PDF of every credential, including revoked ones
  • Metadata in CSV: identifiers, status, issue and expiry dates, recipient, revocation date and reason
  • Revocation register in JSON, also in a version with a qualified seal
  • List of templates
  • The organisation's audit log
  • Manifest with SHA-256 checksums of all export files

Ending the cooperation: proposed contract clause

  1. Up to 90 days before the end Control export A full export is made and checked together with us.
  2. End date Read-only mode Issuing is switched off in every channel: in the panel, in the API, in CSV import, in Moodle and in USOS. The administrator can still sign in, browse the data and repeat the export.
  3. Read-only period Verification as before The status page reached from the QR code, the sealed revocation register and the verification API keep working unchanged, at the same addresses.
  4. After that period too Independent verification The seal is checked by the European Commission's DSS validator, and the revocation status by the register the institution publishes.

The read-only period lasts 90 days from the day the contract ends. We enter the end date in advance, and the panel announces it to all users at the institution. When the read-only period ends, we delete the institution's data in the issuer panel, including the panel's users, recipients' personal data, and the content and files of the credentials. The full export therefore has to be downloaded before then. So that issued credentials can still be checked, the following stay: the record of each credential without personal data (among other things its identifier, title, dates and status, including revocation), the sealed revocation register, and the institution's name and identification data (tax number, country). Also kept: view, download and share counters without personal data, the record of the deletion and of the warnings sent, and the evidence that the terms of service and the data processing agreement were accepted, with the details of the person who accepted them (name, e-mail, IP address, browser). By default, staff sign-in accounts stay in the shared sign-in pool, because the same account can be used for the wallet; they no longer lead to the issuer panel. Copies of credentials in wallets belong to their holders and stay with them. The exit plan, annexed to the contract, describes the procedure step by step.

from December 2026 Credential verification hosted under the institution's own domain — part of being ready for the end of the contract.

Verifiable for years

The qualified eIDAS seal (EuroCert) with a qualified timestamp lets anyone check a credential without Credentium, also after the contract ends. Credentials issued before 13 October 2026 may have the BASELINE-T level.

  • Released after the LTA seal

    A credential is released only after its seal has been verified at LTA level. When the timestamp service is unavailable, issuing is paused and resumed automatically.

  • Everything needed inside the file

    PDF as PAdES-BASELINE-LTA, JSON-LD as JAdES-BASELINE-LTA: the certificate chain, OCSP responses, CRLs and an archival qualified timestamp. Checking the seal needs no access to Credentium's infrastructure or to the seal provider's services.

  • Automatic renewal

    Copies in the system and every new export get a new archival timestamp a year before the previous one expires. We renew the revocation registers in the same way.

  • Copies held by holders

    Copies already downloaded by holders are not renewed. They stay self-contained until the certificate of the last timestamp expires (for files issued now: until April 2035); after that, a renewed copy from the system or from a current export confirms validity. After the contract ends, the institution takes over renewing the stored copies.

  • Independent of CloudTeam

    The seal certificate was issued by a qualified trust service provider on the EU trusted list, not by CloudTeam, so files held by holders remain verifiable even if the service goes bankrupt, is wound up or is permanently shut down. On their own they suffice until the certificate of the last timestamp expires (for files issued now: until April 2035); after that, a copy renewed by the institution confirms validity. Revocation statuses are in a register with a qualified seal, which the institution has in its full export and can publish itself.

  • Who attests the origin

    A qualified seal carries the presumption of integrity of the data and of correctness of the origin of that data from the entity that applied it. In the default model CloudTeam applies the seal; with the institution's own seal, under its own agreement with EuroCert, the institution does. That is why we suggest the institution's own seal from the start of the contract.

Holder privacy

In the browser wallet, holders decide what they show and to whom. Credentials are private by default, and every act of making one public needs the holder's decision.

  • Private by default

    Only the holder can see a credential until they make it public.

  • Link under control

    The holder turns the public link on and off; switching it off takes effect immediately.

  • No search engines

    Indexing is blocked by default and needs the holder's deliberate consent.

  • Date of birth

    The holder decides separately whether to show it.

  • Revoked credentials

    A revoked credential automatically stops being public.

  • Portfolio and collections

    The public portfolio and collections have their own visibility settings.

  • Files and account

    Holders download their credentials as PDF and JSON-LD and can delete their account themselves, confirming with a code and password. Two-step verification in the wallet is optional.

Digital accessibility

  • Status in the statement

    The platform is partially compliant with the Polish Digital Accessibility Act. The accessibility statement lists the non-compliances and explains how to report an accessibility problem.

  • Tests after every deployment

    After every deployment of the platform, automated accessibility tests check the key pages of the issuer panel, the wallet and the public pages.

  • Accessibility mechanisms

    Page language declaration, text alternatives for images, ARIA attributes and a visible keyboard focus.

Questions and answers

Where does Credentium store data?

We store production data and backups in the EU, in 4 countries: the Netherlands (Azure West Europe), Ireland (geo-redundant backups), Germany (AWS in Frankfurt, Sentry) and Poland (EuroCert, backup vault in Azure Poland Central). HTTPS traffic is handled by Cloudflare, which processes it after decryption in the data centre closest to the user, and the validator is delivered through the Amazon CloudFront edge network; in both cases the location may be outside the EEA.

Who is the controller of personal data?

For data in the issuer panel and data passed on for issuing credentials, the institution is the controller and CloudTeam the processor; we sign the data processing agreement as a separate written document. For the data of wallet accounts, which holders create themselves, CloudTeam is the controller.

Can staff sign in with their work account?

Yes. Staff sign in to the issuer panel with their work account through the institution's Microsoft Entra ID (SSO, OIDC); signing in with a Google account is also supported. Disabling the account in the institution's directory closes access to the panel. When signing in with a Credentium account, two-step verification remains mandatory, and nothing changes in the holder's wallet.

How long is the audit log kept, and can it go into our SIEM?

We keep the audit log for 12 months, longer under special terms in the contract. It covers sign-ins, administrative operations and API calls attributed to the key used. The institution's SIEM pulls it incrementally through the REST API with a key that has the audit:read scope, and the administrator can download the view from the panel as CSV.

How quickly will we hear about a security incident?

We report an incident affecting the service or the institution's data, including a personal data breach, without undue delay, within the period set in the data processing agreement. The first notice contains the information needed to report in the S46 system, and after a P1 or P2 incident we deliver a final report within 10 working days.

What are the RPO and RTO?

For deletion or corruption of data, the database RPO is 15 minutes and the RTO 4 working hours. For the loss of the West Europe region, the database RPO is 1 hour and the RTO 2 working days. We rehearse recovery on production every quarter, with a written record.

What availability does the contract guarantee?

99.00% monthly availability in the Standard package and 99.50% with Premium Support. We measure availability automatically and publish it on status.credentium.com; if it is not met, an SLA credit applies according to the package.

What happens to credentials after the contract ends?

The account switches to read-only mode for 90 days: issuing is switched off, while the status page reached from the QR code, the sealed revocation register and the verification API keep working unchanged, at the same addresses. After that, we delete the institution's data in the issuer panel; the record of each credential without personal data and the sealed revocation register stay, so that credentials can still be checked. The institution has its full export, and files held by holders remain verifiable independently of CloudTeam until the certificate of the last timestamp expires (for files issued now: until April 2035); after that, a copy renewed by the institution confirms validity.

Can a credential be verified without Credentium?

Yes. The qualified seal is checked by the European Commission's DSS validator, and a PDF also by Adobe Acrobat. The file contains everything needed for verification and an archival timestamp, so on its own it suffices until the certificate of the last timestamp expires (for files issued now: until April 2035); after that, a renewed copy confirms validity. The revocation status is in a register with a qualified seal, which the institution can publish itself.

Which security certifications apply to the platform?

The platform runs on PaaS services of the cloud providers Microsoft Azure and AWS, which hold ISO/IEC 27001 certificates and SOC 2 reports; these are the providers' certifications. To assess Credentium itself, on request we provide automated security test results, the SBOM and the record of the most recent restore test, and the institution can carry out an audit once a year.

Questions from your IT or security team?

The full technical FAQ covers the credential standard, the seal, architecture, integrations, permissions, security, the KSC Act, backups, SLA and contract exit in detail. On request we also provide a sample production credential with DSS and SHACL validation reports, the SBOM and security test results.

Request the full technical FAQ