ETSI EN 319 401 Gap Analysis

A clause-by-clause self-assessment for trust service providers

ETSI EN 319 401 sets the general policy requirements for trust service providers. Conformity assessments of a qualified trust service provider under eIDAS are normally built on it. Answer the 141 questions below to see which clauses you already cover and where the gaps are.

Based on: ETSI EN 319 401 V3.2.1 (2026-01), the current edition when this checklist was written. Clause numbers and titles follow that edition; check etsi.org for a newer one before you rely on the result.

What this is not: a conformity assessment. It is a self-assessment aid. The questions summarise each clause in our own words and do not cover every requirement, so the standard itself is authoritative. EN 319 401 is also only the base layer: service-specific standards such as EN 319 411-1 and -2 for certificates or EN 319 421 for time-stamps add requirements on top.

Your answers are saved in this browser only, so you can leave and come back. Nothing you enter is sent to our server.

Both fields are only used in the exported report.

Summary

0 of 141 questions answered

  • 0 met
  • 0 partly
  • 0 not met
  • 0 not applicable
  • 141 unanswered

4 Overview

0 of 3 answered

  • 0 met
  • 0 partly
  • 0 not met
  • 0 not applicable
  • 3 unanswered
  • 0 met
  • 0 partly
  • 0 not met
  • 0 not applicable
  • 5 unanswered

6 Policies and practices

0 of 13 answered

  • 0 met
  • 0 partly
  • 0 not met
  • 0 not applicable
  • 13 unanswered
  • 0 met
  • 0 partly
  • 0 not met
  • 0 not applicable
  • 120 unanswered

4 Overview

4.2 Applicability of Conditional Requirements

0 of 3 answered

Have you gone through the requirements the standard marks as depending on proportionality and recorded, for each one, whether and how you apply it?
Does every decision not to apply one of them have a written justification based on your risk exposure, your size, and how likely and how severe incidents would be — rather than simply on being a small provider?
Have you checked that the requirements you left out do not, taken together, weaken the security of the service?

Evidence an auditor typically expects: An applicability analysis filed with the risk assessment, showing the reasoning behind each decision and who approved it, in a form you could hand to the supervisory body.

5 Risk Management Framework and Risk Assessment

0 of 5 answered

Is there a documented risk assessment for the trust service that covers business and technical risks, including third-party dependencies and single points of failure?
Do you work to a defined risk methodology, with risk criteria and risk tolerance levels derived from a risk appetite that management has approved?
Is there a risk treatment plan that names an owner and a deadline for each measure, and is progress on it tracked?
Has management approved the risk framework and formally accepted the residual risks, with the reasons written down?
Are the risk assessment and treatment plan reviewed at least once a year and after significant incidents or changes, and do you measure whether the security measures actually work?

Evidence an auditor typically expects: The risk methodology, the current risk register and treatment plan, management approval and residual-risk acceptance (minutes or a signed record), the review history, and the procedure and results for measuring the effectiveness of controls.

6 Policies and practices

6.1 Trust Service Practice statement

0 of 5 answered

Do you have a practice statement that explains how you meet each requirement of the trust service policy you claim to follow?
Is it approved by a management body with final authority, and is there a defined review process with someone responsible for maintaining it?
Is the current version available to subscribers and relying parties (sensitive details can be left out) and published promptly after each approval?
Does it set out the obligations of the external organisations that support the service?
Do you give advance notice of changes that could affect acceptance of the service, and does the statement describe what happens if the service is terminated?

Evidence an auditor typically expects: The published practice statement with its version history, approval records, the review procedure, change notices in your repository, and the sections on subcontractors and on termination.

Related tool: CPS Builder — draft an RFC 3647-structured practice statement for a CA.

6.2 Terms and Conditions

0 of 3 answered

Can subscribers and relying parties read the precise terms and conditions before they enter into an agreement — both in a public place and presented to them individually?
For each policy you support, do the terms cover the points the standard lists — among them usage limits, subscriber obligations, guidance for relying parties, how long event logs are kept, liability limits, governing law, complaint handling, conformity assessment status, contact details and any availability commitment?
Are they written in language the reader can readily understand and delivered through a durable medium, such as a versioned PDF rather than only a web page that can change?

Evidence an auditor typically expects: The published terms (or PKI disclosure statement), the sign-up or ordering flow showing the terms are presented before the contract is concluded, and archived earlier versions.

6.3 Information and Network Security Policy

0 of 5 answered

Is there a dated, management-approved security policy for your network and information systems that sets objectives, commits resources and continual improvement, assigns roles, and lists the topic-specific policies and the records to be kept?
Has it been communicated to and acknowledged by the staff and external parties it affects, and are changes passed on to third parties where relevant?
Does management review the policy at least once a year and after significant incidents or changes, and is the outcome of each review documented?
Do you have a procedure for telling the supervisory body about changes to the service at least one month ahead, and about a planned cessation at least three months ahead?
Are system configurations checked regularly for changes that breach the security policy, and is the maximum interval between checks stated in the practice statement?

Evidence an auditor typically expects: The approved policy with approval date, staff acknowledgements, review minutes, the supervisory-body notification procedure with any past notifications, and configuration-check reports.

7 TSP management and operation

7.1 Internal organization

7.1.1 General

0 of 4 answered

Are responsibilities and authorities for network and information security assigned to named roles and made known to management?
Does at least one person report directly to the management body on security matters?
Are staff and third parties required to follow the security policy and the topic-specific policies and procedures?
Are roles, responsibilities and authorities reviewed at planned intervals and after significant incidents or changes?

Evidence an auditor typically expects: An organisation chart, role descriptions or a responsibility matrix, the appointment of the security lead with the reporting line, and records of role reviews.

7.1.2 Organization reliability

0 of 4 answered

Are your practices non-discriminatory, and is the service open to any applicant within your declared field of operation who accepts the terms?
Do you hold enough financial resources or liability insurance to cover liabilities arising from the service, as applicable law requires?
Can you show the financial stability and resources needed to keep operating in line with your policy?
Is there a documented procedure for resolving complaints and disputes from customers and relying parties?

Evidence an auditor typically expects: The insurance certificate, recent financial statements or a parent-company guarantee, and the complaints procedure together with the complaints log.

7.1.3 Segregation of duties

0 of 2 answered

Have you identified duties that conflict — for example requesting and approving, or administering and auditing — and assigned them to different people?
Where full separation is not feasible, are the compensating controls (extra oversight, additional logging) documented?

Evidence an auditor typically expects: A role-conflict matrix, the current list of who holds which role, and system access settings that enforce the separation.

7.2 Human resources

0 of 5 answered

Are trusted roles defined — at least security officer, system administrator, system operator and system auditor — with people formally appointed by senior management and accepting the appointment?
Are there written criteria for which roles need background verification, is it completed before the person starts, and is access to trusted functions withheld until then?
Do staff and subcontractors have the expertise and training their role needs, including security and data protection training, and do people in trusted roles get an update on new threats at least every 12 months?
Do job descriptions reflect segregation of duties and least privilege, and are people in trusted roles free of conflicts of interest?
Do you have a communicated disciplinary process, contractual security duties that continue after employment ends, and — if you allow remote work — a remote working policy?

Evidence an auditor typically expects: Trusted-role appointment and acceptance records, the screening policy and evidence that checks were completed, training records, job descriptions, conflict-of-interest declarations, confidentiality clauses in contracts and the remote working policy.

7.3 Asset management

7.3.1 General requirements

0 of 2 answered

Are your assets, including information assets, protected at a level that matches their importance to the service?
Are assets you obtain through suppliers covered by your supply chain controls (see 7.14)?

Evidence an auditor typically expects: The asset management policy and a mapping that shows which protective controls apply to which class of asset.

7.3.2 Assets classification

0 of 4 answered

Do you keep an accurate, current inventory of assets?
Does every asset or group of assets carry a classification level based on its confidentiality, integrity, authenticity and availability needs, and are the levels reviewed periodically?
Do the availability requirements of classified assets match the recovery objectives in your business continuity and disaster recovery plans?
Are there documented rules for acceptable use and handling of information and assets, and a procedure for getting assets back when staff or contractors leave or change role?

Evidence an auditor typically expects: The asset inventory with owners and classification levels, the classification scheme, acceptable-use rules, and joiner/mover/leaver checklists showing returned assets.

7.3.3 Storage media and asset handling

0 of 4 answered

Is there a policy for handling assets and storage media through their whole life — acquisition, use, storage, transport and disposal — that everyone who handles them knows about?
Are storage media protected against damage, theft, unauthorised access and obsolescence for as long as the records on them must be kept?
Is removable media technically blocked unless there is a justified need, with auto-run disabled and malware scanning before use?
Are media erased or destroyed so the data cannot be recovered, and do you keep evidence of it?

Evidence an auditor typically expects: The media handling and removable media policies, endpoint settings that block removable media, transport records and destruction certificates.

7.4 Access control

7.4.1 General

0 of 5 answered

Do you have documented logical and physical access control policies that cover staff, visitors, suppliers and system-to-system access?
Are access rights granted on need-to-know and least privilege, authorised by the right person, recorded in a register, and are changes to them logged?
Are access rights adjusted or removed promptly when someone leaves or changes role, and is third-party access limited in scope and duration?
Do your systems enforce the separation of trusted roles, and are staff individually identified, authenticated and held accountable for what they do in critical applications?
Are the access control policies reviewed at planned intervals and after significant incidents or changes?

Evidence an auditor typically expects: The access control policy, access request and approval records, the access rights register, periodic access review reports, leaver tickets and system role configuration.

7.4.2 Privileged and system administration accounts

0 of 3 answered

Is there a policy for privileged and administration accounts that requires strong authentication such as multi-factor authentication?
Are administration accounts separate, personal, restricted as far as possible, and used only for administration tasks on administration systems?
Are privileged access rights reviewed at planned intervals, with the results and the resulting changes documented?

Evidence an auditor typically expects: The privileged access policy, a list of privileged accounts with named owners, authentication settings, and dated privileged-access review records.

7.4.3 Administration systems

0 of 2 answered

Are the systems you use for administration used for nothing else?
Are they logically separated from other application software, with access protected by authentication and encryption?

Evidence an auditor typically expects: Network and system diagrams showing the administration systems (jump hosts, management consoles), their hardening baseline and their access configuration.

7.4.4 Identification

0 of 3 answered

Does every user and every system have a unique identity, with each user identity tied to exactly one person?
Are shared identities allowed only for a documented operational reason, with explicit approval, and are they considered in the risk assessment?
Are identities reviewed regularly and deactivated without delay when no longer needed, and are identity management actions logged?

Evidence an auditor typically expects: An export from the identity directory, the list of approved shared or service accounts with justification, identity review records and identity-management logs.

7.4.5 Authentication

0 of 4 answered

Is the strength of authentication matched to the classification of the asset being accessed?
Are credentials issued in a way that keeps them confidential, and changed on first use, at defined intervals and when compromise is suspected?
Are accounts blocked after a defined number of failed log-ins, and are idle sessions terminated?
Do privileged and administrative accounts use separate credentials, and are authentication methods reviewed at planned intervals?

Evidence an auditor typically expects: The authentication policy, password and lockout settings, session timeout settings, the credential issuance procedure and the record of the last review of authentication methods.

7.4.6 Multi-factor authentication

0 of 2 answered

Is multi-factor (or continuous) authentication enforced for users and devices accessing the systems whose classification calls for it?
Is it documented which systems require it and why, in line with your asset classification?

Evidence an auditor typically expects: Authentication configuration for each system in scope and the list linking asset classification levels to the authentication required.

7.5 Cryptographic controls

0 of 4 answered

Is there a cryptography policy that states which algorithms, key lengths and protocols are approved for data at rest and in transit, tied to your asset classification?
Does key management cover the whole life of a key — generation, distribution, storage, rotation, compromise, revocation, recovery, backup and destruction — with the activities logged?
Are cryptographic devices such as HSMs controlled from commissioning to decommissioning?
Is the policy reviewed at planned intervals against the state of the art (for example ETSI TS 119 312), with crypto agility in mind?

Evidence an auditor typically expects: The cryptography policy, key management procedures, key ceremony scripts and signed records, the HSM inventory with certification details, and the latest algorithm review.

Related tool: Key Ceremony Planner — produce the ceremony script and sign-off sheets an auditor will ask for.

7.6 Physical and environmental security

0 of 5 answered

Are critical components housed inside a defined security perimeter with access control and intrusion alarms, and is access limited to authorised individuals?
Are the premises monitored continuously for unauthorised physical access?
Are facilities protected against failure of supporting utilities such as power, cooling and telecommunications, with redundancy and monitoring where appropriate?
Based on the risk assessment, are there protections against environmental threats such as fire and flooding, with thresholds that are monitored and alerted on?
Are the physical access, utility and environmental protections tested and reviewed regularly and after significant incidents or changes?

Evidence an auditor typically expects: Site plans showing security zones, physical access lists and logs, alarm and CCTV records, UPS and generator test reports, environmental monitoring records and the data centre contract or certification if hosting is outsourced.

7.7 Operation security

0 of 5 answered

Are security requirements analysed at the specification and design stage of every development or acquisition project, and do secure development rules cover in-house and outsourced work, including testing and test data?
Do change management procedures cover releases, modifications, emergency changes and configuration changes, with each change documented and — based on risk — tested and assessed before it goes live?
Are security patches applied within a defined reasonable time, tested first, taken from trusted sources and integrity-checked, with a documented justification whenever a patch is not applied?
Are secure configurations defined for hardware, software, services and networks, monitored with tooling and reviewed regularly, and are systems protected against malicious and unauthorised software?
Is there a security testing policy that sets the scope, type and frequency of tests from the risk assessment, with results, severity ratings and remediation documented?

Evidence an auditor typically expects: Secure development rules, change tickets including emergency changes, patch reports and documented exceptions, configuration baselines with monitoring output, and security test reports with remediation tracking.

7.8 Network security

0 of 5 answered

Is the network segmented into zones based on risk, with critical systems in secured zones, separation from third-party networks, and traffic between zones limited to what operation requires?
Is the administration network separate from the operational network, and is production separate from development and test, including their backups?
Are vulnerability scans run at least quarterly on your public and private addresses, and a penetration test at least once a year and after significant changes, by competent and independent testers, with the evidence kept?
Are firewalls configured to block everything the service does not need, unneeded connections and services disabled, and malware protection updated at least daily?
Is the network architecture documented and current, and do you have an implementation plan for moving to current network-layer protocols, modern e-mail security standards and good practice for DNS and routing security?

Evidence an auditor typically expects: A current network diagram, firewall rule sets and their review records, quarterly scan reports, the annual penetration test report with tester qualifications, and remediation tracking.

7.9 Vulnerabilities and Incident management

7.9.1 Monitoring and logging

0 of 5 answered

Is activity on your network and systems monitored — automatically where feasible — so that abnormal activity raises an alarm against defined thresholds and gets a timely, qualified response?
For a risk-based list of assets, do the logs cover network traffic, account and permission changes, access and authentication events, administrator activity, changes to critical configuration, security tool output and, where relevant, physical access and environmental events?
Are logs kept and backed up for a defined period, protected against unauthorised access or changes, and reviewed regularly for unusual trends?
Are system clocks synchronised so that logs from different systems can be correlated?
Are the monitoring and logging systems redundant, and is their availability monitored independently of the systems they watch?

Evidence an auditor typically expects: The logging and monitoring procedure, the list of logged assets, SIEM or log platform configuration and alert rules, log review records, time synchronisation settings and retention settings.

7.9.2 Incident response

0 of 5 answered

Is there an incident handling policy with roles, incident categories, escalation paths and communication plans, covering detection, analysis, containment, eradication, recovery, documentation and reporting?
Do you know which legal reporting obligations apply to you (for example under eIDAS, NIS2 and GDPR), and do you have communication plans for the CSIRT or authorities, your staff and external stakeholders?
Are critical vulnerabilities addressed within 48 hours of discovery, and for every other vulnerability is there either a mitigation plan or a documented reason why none is needed?
Are incident response roles and procedures tested at planned intervals and updated after incidents, and is incident handling coordinated with business continuity?
Are incident response activities logged with evidence preserved, and are trusted-role staff assigned to follow up alerts?

Evidence an auditor typically expects: The incident handling policy, response manuals, escalation charts and contact lists, incident records, the vulnerability register showing dates of discovery and treatment, and reports from incident response exercises.

7.9.3 Reporting

0 of 4 answered

Do you have a procedure for notifying the appropriate authorities within 24 hours of identifying a breach of security or loss of integrity that significantly affects the service or the personal data it holds?
Are the people and organisations you serve told without undue delay when a breach is likely to harm them?
Is there a simple, communicated way for staff, contractors, suppliers and customers to report suspected incidents and suspicious events, and are staff trained to use it?
Have you adopted the criteria in this clause for when an incident counts as significant — financial loss, duration of unavailability, share of users affected, compromised physical access or data, and recurring incidents?

Evidence an auditor typically expects: The notification procedure with authority contact details and templates, records of past notifications, the reporting channel as published to customers, and your incident classification criteria.

7.9.4 Event assessment and classification

0 of 3 answered

Are reported events assessed against criteria defined in advance and triaged to decide whether they are incidents and how severe they are?
Are events reassessed and reclassified when new information comes in?
Do you correlate and analyse logs as part of event assessment, and check for recurring incidents at least every quarter?

Evidence an auditor typically expects: The triage criteria, event and incident tickets showing classification and any reclassification, and the quarterly recurring-incident review.

7.9.5 Post-incident reviews

0 of 3 answered

Do you keep track of technical vulnerabilities in all the systems you use, assess your exposure and act on it?
Does every incident lead to a post-incident review that identifies the root cause and records the lessons learned?
Do review results feed back into your security approach, risk treatment and incident procedures, and do you check at planned intervals that the reviews were actually held?

Evidence an auditor typically expects: Vulnerability advisories you subscribe to and the resulting assessments, post-incident review reports, and the actions they triggered in the risk treatment plan.

7.10 Collection of evidence

0 of 4 answered

Do you record and keep — for a defined period that continues after the service ends — the information about data issued and received that would be needed as legal evidence, and can you produce it on request?
Is the retention period consistent with what your terms and conditions tell subscribers and relying parties?
Are current and archived records protected for confidentiality and integrity, and logged in a way that prevents them from being easily deleted or destroyed during the retention period?
Is the precise time of significant environmental, key management and clock synchronisation events recorded, and is the audit-log clock synchronised with UTC at least once a day?

Evidence an auditor typically expects: The records retention schedule, archive configuration (write-once storage, off-site copies), a sample retrieval of an archived record, and time-source configuration with synchronisation logs.

7.11 Business continuity management

7.11.1 General

0 of 3 answered

Is there a business continuity plan with defined restoration times that covers disasters including compromise of a private signing key or another credential?
Based on the risk assessment, is there at least partial redundancy of systems, facilities and equipment, competent personnel and communication channels?
Are continuity test results documented and corrective actions taken, and does recovery include fixing the cause so the disaster does not recur?

Evidence an auditor typically expects: The business impact analysis, the continuity and disaster recovery plans (including the key-compromise scenario), redundancy design, and test reports with follow-up actions.

7.11.2 Back up

0 of 4 answered

Is there a maintained backup plan that defines recovery times, retention periods and the restore approval process, and that includes configuration data and data held in cloud services?
Are backup copies stored outside the network of the system they protect and far enough from the main site, with physical and logical protection that matches their classification?
Are backup copies integrity-checked regularly?
Are restores from backup and failover to redundant systems tested at planned intervals, with results documented and findings corrected?

Evidence an auditor typically expects: The backup plan, backup job reports, integrity check logs, off-site storage arrangements and dated restore test reports.

7.11.3 Crisis management

0 of 4 answered

Is there a crisis management process that assigns roles and steps to staff and, where relevant, suppliers, and keeps security controls in place during a crisis?
Are communication channels with the competent authorities defined for both mandatory and voluntary communication?
Do you have a process for acting on information from the national CSIRT or authorities about incidents, vulnerabilities and threats?
Is the crisis management plan tested and reviewed at planned intervals and updated after significant incidents or changes?

Evidence an auditor typically expects: The crisis management plan, the crisis team contact list, records showing how CSIRT advisories were handled, and reports from crisis exercises.

7.12 TSP termination and termination plans

0 of 5 answered

Do you have an up-to-date termination plan, and are its provisions summarised in your practice statement?
Does the plan cover informing subscribers, relying parties, other providers you have agreements with and the supervisory body before termination, and ending the authorisation of subcontractors to act for you?
Is there an arrangement to hand over the evidence records, and to keep public keys or trust service tokens available, through a reliable party for a reasonable period?
Does the plan provide for destroying private keys, including backups, or withdrawing them from use so they cannot be retrieved?
Is there an arrangement that covers the cost of termination if you become bankrupt or otherwise cannot pay for it yourself?

Evidence an auditor typically expects: The termination plan with its last review date, the agreement with the party that takes over records, the financial arrangement (escrow, insurance or guarantee), and the termination section of the practice statement.

7.13 Compliance

0 of 4 answered

Can you show how you meet the legal requirements that apply to the service, for example with a register of applicable law and the evidence for each item?
Are the service and the end-user products used with it accessible to persons with disabilities where feasible, taking standards such as EN 301 549 into account?
Do technical and organisational measures protect personal data against unauthorised or unlawful processing and against accidental loss, destruction or damage?
Is there a compliance reporting system that gives management an informed view of the current state of risk management?

Evidence an auditor typically expects: A legal requirements register, accessibility statement or assessment, GDPR records (processing register, DPIAs, processor agreements) and periodic compliance reports to management.

7.14 Supply chain

7.14.1 Supply chain policy

0 of 3 answered

Is there a supply chain security policy that governs relations with your direct suppliers and service providers, states your own role in the supply chain, and has been communicated to them?
Does it define criteria for selecting and contracting suppliers — their security practices, their ability to meet your requirements, the quality and resilience of what they deliver, and your ability to diversify supply and limit lock-in?
Do you monitor suppliers' security practices (service level reports, supplier incidents, the risk of changes) and review the policy at planned intervals and after significant incidents?

Evidence an auditor typically expects: The supply chain security policy, supplier selection records showing the criteria applied, supplier performance and incident reviews, and the policy review history.

7.14.2 Supply chain procedures and processes

0 of 5 answered

Are security requirements defined for acquiring ICT products and services, and are suppliers required to pass them on through their own supply chain?
Do you ask product suppliers for a description of the software components in their products, the security functions implemented and the configuration needed to operate them securely?
Do you validate that delivered products and services meet the stated requirements, are genuine and unaltered, and behave as expected without unwanted features?
Are critical components identified, traceable to their origin, and managed over their life cycle, including availability and end of support?
Is there a topic-specific policy on the use of cloud services and on how you manage the risks that come with them?

Evidence an auditor typically expects: Procurement security requirements, supplier documentation such as software bills of materials and hardening guides, acceptance test records, the list of critical components with support dates, and the cloud usage policy.

7.14.3 Responsibility, third parties agreements and SLA

0 of 5 answered

Is there a documented agreement with every subcontractor, outsourcer or other third party that sets out their obligations, liability and the controls they must implement — while you keep overall responsibility?
Where appropriate, do contracts cover security requirements, staff competence and background checks, prompt incident notification, vulnerability handling, a right to audit or to receive audit reports, rules on subcontracting, and obligations when the contract ends?
Do you keep an up-to-date register of direct suppliers and service providers with contact points, what each one provides, the agreements in place and where your information is held?
Are supplier agreements and suppliers' security practices reviewed at least once a year and after supplier-related incidents?
If you rely on a trust service component from another provider, have you verified that it meets your policy requirements and that you use its interface the way that provider specifies?

Evidence an auditor typically expects: Supplier contracts and service level agreements with their security clauses, the supplier register, supplier audit reports or certifications, and annual supplier review records.

Gaps to close

Questions answered Not met come first, then Partly, each in clause order.

Nothing here yet. Questions you answer Not met or Partly are listed here.

Want a second pair of eyes on the gaps before the conformity assessment body arrives? MI Support IT provides PKI consulting for trust service providers — audit preparation, CP/CPS documentation and key ceremonies.

How to use the result

Where EN 319 401 sits

It covers what every trust service has in common: risk management, policies, people, access control, operations, incidents, continuity, termination and suppliers. What is specific to issuing certificates or time-stamps lives in the service standards that build on it. Annexes A to C of the standard map its clauses to DORA, eIDAS and the NIS2 implementing regulation (EU) 2024/2690.

Answer from evidence

An auditor does not accept "we do that". Choose Met only when you could put the document or record on the table today, Partly when the practice exists but is undocumented or incomplete, and use the note to record where the evidence lives.

Closing documentation gaps

Two common gaps are a practice statement that no longer matches operations and missing key ceremony records. The CPS Builder gives you a structured draft for the first, and the Key Ceremony Planner a script with sign-off sheets for the second.

Related tools

  • CPS Builder — draft the practice statement that clause 6.1 asks for
  • Key Ceremony Planner — script the key generation ceremony behind your cryptographic controls

Privacy: Your answers and notes are stored only in your browser's local storage and are never sent to us. Read our privacy policy.