Cybersecurity Under Pressure podcast artworkCybersecurity Under PressureReal Attacks. Real Lessons.Subscribe
Home / Library / Resources
Standards & Resources164 authoritative records

Cybersecurity standards, advisories and technical evidence.

Browse standards, official security advisories, vulnerability records, primary research and technical references already cited across automotive, OT/ICS, railway and product security Analysis. Each record links back to the context where it informs an engineering or security decision.

164 resources
Standards in engineering practice

Start with the framework. Follow the evidence.

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.

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.

Compare all six worksheets →

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 →

Standards & regulation

39
PRIMARY / GUIDANCEUsed in 8 Analysis

UNECE · UN Regulation No. 155

unece.org
Open source ↗
The BYD Shark 6 Case Shows Why Remote Authority Needs Explicit Boundaries →R155 and R156 Keep Cybersecurity Inside the Type-Approval Chain →How a Software-Defined Vehicle Could Inherit Compromise Before Delivery →
Show 5 more related AnalysisThe Connected Vehicle Perimeter Includes Dealer APIs →Euro 7 Turns Emissions Compliance into a Cybersecurity Evidence Chain →Aftermarket Security Devices Can Become Part of the Vehicle Attack Surface →An IDPS Alert Is Not an Incident Response Capability →The Next Production Delay May Be Missing Cybersecurity Evidence →
PRIMARY / GUIDANCEUsed in 7 Analysis

ISO · ISO/SAE 21434 overview

iso.org
Open source ↗
The BYD Shark 6 Case Shows Why Remote Authority Needs Explicit Boundaries →AutoHack Shows Why IDS Validation Must Follow the Real Attack Path →A Trusted Automotive Update Path Can Become the Malware Delivery Path →
Show 4 more related AnalysisThe Bendix EC80 Recall Shows Why Safety Fixes Need a Cybersecurity Handoff →A Valid Signature Does Not Make Vulnerable Firmware Safe →An IDPS Alert Is Not an Incident Response Capability →The Next Production Delay May Be Missing Cybersecurity Evidence →
PRIMARY / REFERENCEUsed in 7 Analysis

UNECE Regulation No. 156

unece.org
Open source ↗
Automotive OTA Patch Assurance Depends on Virtual Tests, Physical Evidence and Supplier Authority →R155 and R156 Keep Cybersecurity Inside the Type-Approval Chain →A Trusted Automotive Update Path Can Become the Malware Delivery Path →
Show 4 more related AnalysisA Valid Signature Does Not Make Vulnerable Firmware Safe →How a Software-Defined Vehicle Could Inherit Compromise Before Delivery →Euro 7 Turns Emissions Compliance into a Cybersecurity Evidence Chain →An IDPS Alert Is Not an Incident Response Capability →

Official advisories & records

91
OT RESILIENCE CONTEXTUsed in 8 Analysis

NIST · SP 800-82 Rev. 3, Guide to Operational Technology Security

csrc.nist.gov
Open source ↗
Rockwell Logix Shows Why PLC Vulnerability Management Must Include Recovery →An OT Alert Is Not Protection Until It Becomes a Safe Physical Action →Zero Trust in OT Should Mediate Authority, Not Modernise Every PLC →
Show 5 more related AnalysisSafety Independence Must Survive a Cyber Compromise →When Legitimate Engineering Workflows Can Carry Malicious Control Logic →Oldsmar Is a Warning About Standing Remote Authority →The Restart Bottleneck Is Not the Backup. It Is the Evidence. →The Remote Access Path Nobody Questions Anymore →

Primary research

33

Technical references

1