What it does

What Crosswalk does, screen by screen

Every picture below is the real application, in two example projects that ship with it: an invented machine builder and our own compliance file.

Try the example Claim your free Lite licence

Lite is free. Renews every year at no cost. Essentials €99 a month, excl. VAT. See plans

Home and scope

Find your way.

HomeSee the next step.Home shows the stages with their state and names the one step that comes next.

The Next step on Home of an invented machine builder: the organisation's vulnerability handling under the CRA, with the one requirement not in place.
Home of an invented machine builder.

ScopeChoose the scope once.One control narrows what you see to the organisation or one product. One click shows everything again.

The scope control opened on its products: three products of an invented machine builder, each with its requirements in place, its open actions, its documents and its stage.
The scope control, opened on its products.

Set up · Assess · Fix · Prove

Work through the four stages.

Set upSettle what applies.Plain questions pre-fill a verdict for each law, with the article behind it. You keep the last word.

The verdict for the CRA from the answers to its questions: likely applies.
The CRA's verdict, from the answers.

AssessRead the law beside it.Each checklist says what you assess and why, with the provisions one click away.

The basis of vulnerability handling in the CRA: Annex I Part II and Articles 13(5), 13(8), 13(9), 13(10) and 14, why they bind, and the provisions one click away.
Vulnerability handling, with its basis in the CRA.

FixGive every action an owner.Every action on one list, with the requirement it answers, an owner and a date.

The Work queue of our own compliance file: one sentence that says whose open actions are listed and how many, a switch to everyone's with its count, a search, and an action on two lines: its title, then its checklist, law, requirement and due date.
The Work queue of our own compliance file.

ProveKnow what is still missing.Prove lists what the organisation and each product hand over, and says what still keeps it from done.

Prove for an invented machine builder: not done yet, two declarations not issued, and the documents of the organisation and of each of its three products.
What still keeps Prove from done.

ProvePublish your disclosure policy.A coordinated vulnerability disclosure policy and a security.txt, built from your own contacts and a remediation matrix. From the Essentials plan.

The remediation matrix by CVSS severity: from critical to low, the time to acknowledge and triage, and the time to a fix.
The remediation matrix, by CVSS severity.

Claim your free Lite licence See plans

Incident

Handle what happens.

IncidentStart from what happened.One action, Something happened, lists the situations in your own words, and each opens the record it needs.

Something happened, opened: the security events first, someone reported a vulnerability, an incident happened, a component has a known vulnerability, we need to warn our users.
Something happened: the security events first.

IncidentMeet every reporting clock.Each report becomes a case: a triage one question at a time, then the reporting duties per regime with their deadlines.

Two incident cases of an invented machine builder, both closed: an actively exploited vulnerability, all reported under the CRA, and an upstream library vulnerability that was not reportable.
Two cases, each with its duty per law.

IncidentKeep every date in view.Every date the project knows, the nearest first, exportable to your own calendar. On the Professional plan.

The compliance calendar: what is coming first, each date with how far away it is, two releases and a training due date.
What is coming first, the nearest at the top.

Reference

Check every change.

Every change is recorded on every plan, in a chain whose integrity can be checked. The Logbook page: from the Essentials plan.

Entries of the Logbook of an invented machine builder, each with when, who and what: the line saying its history is invented, an EU declaration of conformity issued with CRA Art. 28 and Annex V, and a document generated.
Every change, with who made it and when.

No sign-up

Start with the example.

Try the example Claim your free Lite licence

Nothing to install, no sign-up, no payment details.

Reference

Look up the details.

WhatPlan
Incident cases, with their decision trailOn every plan
The Logbook, kept and exported as CSV or JSONOn every plan
The Logbook page, with its filters and the chain checkFrom the Essentials plan
Attaching evidence files, and the evidence binderFrom the Essentials plan
The disclosure policy and security.txtFrom the Essentials plan
The AI assistant's interview, opt-inOn a paid plan
Supplier due diligenceOn the Professional plan
The compliance calendar, exported as .icsOn the Professional plan
Home and the scope

Home shows the stages as a row of steps with their state and says what still keeps Prove from done. Under Incident it names a running reporting clock or a case still waiting for its triage.

The scope control sits at the top of the sidebar, in the address, and as the scope filter of the compliance calendar, the Logbook and Figures; the Work queue lists the sidebar's scope. Its panel lists the organisation and every product with their requirements in place and open actions; type to find a product.

Set up

Tick the laws that apply: the CRA, NIS2, GDPR, the Machinery Regulation and RED. The standards follow per law, and a product can say what it is, so the RED sections disappear for a product that is not radio equipment.

Our scope and roles is the record behind everything else: the laws and standards you are measured against, your role in the supply chain, each product's class and support period, and the requirements you set aside with how many of them carry a written reason. Each line says what it changes, when it was recorded and which page it is made on.

The Products page lists every product with where it stands in each stage. Search it, sort any column, and open a product or one of its stages.

Assess

The organisation and each product have their own checklists, the laws first and then the standards, each with its requirements in place out of those that apply. A requirement counts as in place when its evidence is recorded too.

How mature are we reads the same answers as a maturity picture, and the risk analysis holds the risk register, a threat model per product and supplier due diligence. On a paid plan the AI assistant can interview you and fill a section in from your answers, for you to accept. AI is opt-in.

Fix

The Work queue lists the actions of the scope chosen in the sidebar, your own first, with one switch to everyone's and one search over the action, its requirement, its checklist and law, and who holds it. Tick an action off there, open it to read or edit it, or go to its requirement; done actions fold away under the list.

The link beside the Work queue's title lists the requirements that are not in place yet, by area or by severity. Click one and its checklist opens at that requirement.

Prove

Prove lists what the organisation and each product hand over: the audit report set, a document per law, the technical file, the EU declaration of conformity and the security datasheet. Each document keeps the date it was generated, and one that is out of date says what changed since.

Prove is done when every document is generated and up to date and every product that needs one has an issued declaration. The disclosure policy can be copied or downloaded as Markdown.

Incident

The Incident page of the organisation and of each product starts with what needs attention: the open cases, red while a triage waits or a reporting clock runs. Something happened opens the situations: someone reported a vulnerability, an incident happened, a component has a known vulnerability, you need to warn your users; then the planned work, a change to the product or a release. Below them, what is due in the next 90 days and the open work.

A case opens on its receipt, the report as it came in. The becoming-aware triage asks one question at a time, and an answer waits for the evidence it rests on. The staged reporting duties then appear per regime with their deadlines, the CRA's 24 hour early warning among them, and the decision trail stays with the case.

Your files and the price

In Chrome and Edge your projects can be plain files in a folder you choose, and they stay readable and exportable whatever happens to the subscription.

The Lite licence covers all five laws, to find out where you stand inside your organisation. Free. Renews every year at no cost. What it makes carries the Lite watermark and a small “Made with Crosswalk Lite” credit. Paid plans, for the proof you hand over, from €99 per licence per month.

Reading on this site

Two things that used to sit in the application are reading material, so they live on this site: where the five laws ask for the same thing, and the harmonised standards requested for the CRA with their state of play. In the application, Reference holds the Logbook, the glossary and the mapping of the CRA to IEC 62443.

The documents it produced for the example
DocumentPages
CRA product audit42
CRA technical file8
CRA organisation audit30
NIS2 dossier8
Management review6

Start with the example.

Try the example Claim your free Lite licence