UN R155 engineering guide →
A cybersecurity management system is useful only when its processes reach the vehicle decision. Follow the evidence from supplier inputs and product configuration to monitoring, response and the approval boundary.
Knowledge LibraryCurated evidence, not another feed
Build context once. Reuse it when the decision matters.
Explore the same evidence behind Cybersecurity Under Pressure through guided reading, privacy-first technical video and authoritative source records.
6 Reading Paths191 recordings · 146 CUP originals164 authoritative resources
Standards in engineering practice
Start with the framework. Follow the evidence.
IEC 62443 engineering guide →
Start with the industrial system, the accountable roles and the decision being reviewed. Then connect risk, architecture and operational evidence rather than collecting product labels without their deployment context.
Free tools & worksheets
One review. A practical action plan.
Choose the decision in front of you. Identify missing evidence, assign owners and export a report to take into your next review.
A supplier needs access to your plant.
OT remote access →
Review one supplier connection: who can connect, what they can change, when access ends and who can stop it.
You need to assess a vulnerability claim.
SBOM & VEX assurance →
Challenge one product-component-vulnerability claim and record the evidence, response owner and unresolved actions.
A vehicle change or update needs a review.
Automotive cybersecurity & updates →
Review one vehicle change or software update across engineering evidence, supplier responsibilities and the release decision.
You need evidence for an industrial system.
IEC 62443 system assurance →
Connect an industrial system boundary, accountable roles and implementation evidence to the operational acceptance decision.
You are preparing a product for CRA review.
CRA product readiness →
Scope one product and market activity, then review product security, vulnerability handling and reporting-readiness evidence.
An AI use case needs a deployment decision.
AI Act use-case review →
Define one AI use case, your role and the applicable pathway, then identify evidence gaps before a deployment decision.
Free · No account required · Fictional examples included. Entries stay in your browser; use non-sensitive references only. These tools organise evidence and actions; they do not certify compliance.
Looking for a comparison of the frameworks? Open the separate R155 & IEC 62443 evidence map →
Reading Paths
Follow a decision through related Analysis and podcast episodes rather than browsing chronologically.
Explore 6 paths →Curated audiovisual learningVideo Library
Technical videos, attack demonstrations, webinars and briefings, organised by topic and format.
Browse 191 recordings →Primary evidenceStandards & Resources
Standards, regulation, official records and primary research already used across the Analysis library.
Browse 164 resources →