Platform
Evidence for your standards.
The engineering standards and organisational frameworks Neural Inverse produces evidence toward, and the industries where each applies. Certification stays with you and your assessor.
What we claim
Evidence, not certification.
Evidence towardWe produce records your assessor can use: who changed what, which checks ran, who approved it and when. We never say a product is certified to a standard, or that using it makes your system compliant.
Your certificationCertification and qualification stay with your organisation and its assessor, against your own plans and processes.
Your qualified toolsYour compilers, simulators and analysers do the verification. Neural Inverse runs them and records the results; it does not replace their qualification.
What each record provesEach check and evidence record says what it looked at. A passing check means it found what it looks for, not that a control is met.
Engineering standards
By standard, with the industries it applies to.
ASPICEEvidence toward ASPICE assessments: every change kept with its reason, review and approval. (Automotive)
Change controlEach change with its reason, approver and time, exported for your quality system's audits. (CNC and machining)
DO-178CEvidence toward DO-178C: changes to requirements, trace data and release branches with their approver and reason, in a tamper-evident record. (Avionics)
DO-254Evidence toward DO-254: each implementation run kept with the commit it came from, and each RTL change with its review and approval. (Avionics, Defence and space, Semiconductors and FPGA)
DO-330Evidence toward DO-330: agents are denied changes to qualified-tool configuration, and every decision is logged. (Avionics)
ECSS-E-ST-40CEvidence toward ECSS-E-ST-40C: change records, test results and approvals for your software reviews. (Defence and space)
Electronic recordsSignature records support your own controls for electronic records and signatures. Identity verification at enrolment stays your process. (Medical devices)
IEC 61131-3Structured Text for TwinCAT 3, built by your vendor compiler, with every change kept with its approval. (Industrial automation)
IEC 61850Station files checked against the IEC 61850-6 schema and the module's own rules. Conformance testing of devices stays with you and the vendors. (Energy and utilities)
IEC 62304Evidence toward IEC 62304: changes to requirements and released software with their approver, and SOUP additions reviewed before install. (Medical devices)
IEC 62443Evidence toward IEC 62443: agent rules keep agents off the station and plant networks you name, and every change keeps its approver. (Energy and utilities)Evidence toward IEC 62443: agents kept out of plant network zones and away from controller downloads, with every decision logged. (Industrial automation)
ISO 14971Evidence toward ISO 14971: every agent change to risk management files reviewed by a named approver. (Medical devices)
ISO 26262Evidence toward ISO 26262: changes to safety-relevant components with their named approver, and generated code kept out of agents' reach. (Automotive)Evidence toward ISO 26262: constraint changes reviewed by a named approver, and every change kept with its approval. (Semiconductors and FPGA)
ISO/SAE 21434Evidence toward ISO/SAE 21434: agent reads of ECU keys and certificates are denied and logged. (Automotive)
MIL-STD-882EEvidence toward MIL-STD-882E: changes to safety-related software with their approver and reason. Hazard analysis stays in your safety process. (Defence and space)
PCI DSSEvidence toward PCI DSS: agent reads of cardholder data and production credentials are denied and logged. (Banking and mainframe)
SOXEvidence toward SOX change control: the finance template makes payment and ledger changes and pushes to main wait for a named approver. (Banking and mainframe)
TL 9000Evidence toward TL 9000: each change kept with its reason, test and approval, in a record your auditor can verify offline. (Telecommunications)
Organisational frameworks
Rule packs in Govern.
Govern runs each pack's checks against your organisation's own records and keeps the evidence for your assessor.
SOC 2Rule pack with checks against your organisation's records, and evidence records per control.
ISO/IEC 42001Rule pack for an AI management system, with evidence records per control.
EU AI ActRule pack, with records of decisions and approvals for the AI systems you govern.
GDPRRule pack, plus Article 22 decision records and data residency by region.
HIPAARule pack, with data loss prevention on prompts and context.
PCI DSSRule pack with checks against your organisation's records.
FedRAMPRule pack with checks against your organisation's records.
NIST AI RMFRule pack for AI risk management, with evidence records.
Our own security
This page is about your certification, not ours.
For how we protect your code and data, and for our security documentation and questionnaire responses, see Security and trust.
Talk to our team.
Neural Inverse is available by request. We work with your engineering, security and procurement teams from the first conversation.