Define the operating boundary
A useful definition names the triggering event, required inputs, governing source, accountable owner, decision or action, exception path, evidence retained, and downstream handoff. Buyers should adapt those elements to their own population, jurisdictions, policies, systems, and control model before writing requirements.
The most important distinction is between a label and an operational capability. A provider may document device and product software-supply-chain risk while depending on customer-supplied policy, licensed content, third-party data, integration partners, manual review, or services. The demonstration should expose those dependencies rather than hiding them behind a completed interface.
What a demonstration should prove
- Begin with representative source records and a named policy, standard, or controlled rule.
- Show the normal path, an ambiguous case, missing data, an exception, an override, and a material source change.
- Identify who can change rules, who can approve or reject, and how accountability is preserved.
- Trace every output back to inputs, versions, timestamps, user actions, and governing evidence.
- Export the resulting record and reconcile it with downstream systems and retained obligations.
Authority and operating context
ISA/IEC 62443-2-1:2024
Part 2-1 defines security-program requirements for asset owners across governance, risk, implementation, maintenance, and continuous improvement of IACS security. It creates an owner-specific program lens that product capability lists cannot satisfy by themselves.
ISA/IEC 62443-4-1
Part 4-1 defines secure-development-lifecycle requirements for IACS product suppliers. Buyers need process-scope and certificate evidence rather than assuming one certified product makes an installed system secure.
IEC 62443-4-2
Part 4-2 defines technical security requirements for IACS components using the foundational requirements and security-level framework. Component claims should identify exact product, version, certification scheme, target level, and system dependency.
CISA CPGs
CISA publishes a prioritized set of cybersecurity practices intended to reduce common and consequential risks across critical-infrastructure sectors. The CPGs give buyers a risk-reduction lens for access, segmentation, backups, inventory, monitoring, incident response, and supplier decisions.
CISA Secure by Demand for OT
The guide presents security considerations and questions for OT buyers addressing product configuration, logging, identity, updates, vulnerability handling, support, and secure-by-design behavior. It turns cybersecurity into a procurement and lifecycle evidence decision rather than an after-deployment add-on.
EU Cyber Resilience Act
The CRA establishes horizontal cybersecurity requirements for products with digital elements, including design, vulnerability handling, economic-operator, conformity, reporting, and market-surveillance provisions. Industrial product and device providers need exact role, scope, support-period, vulnerability-handling, technical-documentation, conformity, and reporting evidence rather than a generic CRA-ready claim.
NIS2
NIS2 establishes cybersecurity risk-management, reporting, governance, supervision, and supply-chain requirements across essential and important entities. OT operators need jurisdiction-specific mappings from legal requirements to accountable controls, reporting, supplier, and evidence workflows.
C2M2 v2.1
C2M2 supports evaluation and improvement of cybersecurity capabilities across domains such as risk, assets, access, threat and vulnerability, situational awareness, response, continuity, third parties, workforce, architecture, and program management. It helps frame program and operating-capability evidence without turning a product feature into a maturity score.
Operating domains
Vulnerability, exposure, and remediation governance
The operating process that connects a device, product, component, vulnerability, exploit context, exposure path, process consequence, compensating control, vendor guidance, maintenance window, decision, and retained evidence.
Product security and software supply chain
The lifecycle evidence connecting industrial product design, components, firmware, provenance, secure development, vulnerabilities, updates, support, suppliers, integrators, customers, and end-of-life responsibilities.
Resilience, recovery, and cyber-informed engineering
The integration of cybersecurity with physical mission, safety, reliability, design, spares, configuration baselines, backups, manual capability, tested restoration, and recovery decision authority.
Governance, authorities, and assurance
The system for identifying applicable authorities and commitments, assigning accountable roles, translating requirements into controls, collecting evidence, testing effectiveness, managing exceptions, reporting risk, and preserving change history.
Evidence and comparison limits
Official provider documentation can establish product positioning. Provider confirmation can clarify package or availability. Independent observation requires a disclosed scenario, environment, date, inputs, and reproducible result. None of those sources alone establishes buyer-specific legal, clinical, regulatory, quality, or operational fitness.
Buyer questions
- What exact outcome and evidence should device and product software-supply-chain risk produce?
- Which source, version, and customer facts govern the workflow?
- Which decisions remain human and who is accountable for them?
- What is native, configured, integrated, service-delivered, or planned?
- How does a changed source affect open and historical records?
Recent changes
Accenture announces agreements involving Dragos, runZero, and NetRise — The proposed combination could alter ownership, packaging, data, services, partner relationships, and the OT security market architecture.
EU Cyber Resilience Act Chapter IV begins applying — Industrial product suppliers and buyers need exact legal-role, product, conformity, reporting, support, and evidence records tied to the staged dates.
IEC publishes PAS 62443-1-6:2025 — IIoT reviews need explicit device, gateway, edge, cloud, identity, data, update, supplier, and owner responsibilities.
CISA partners publish Secure by Demand for OT buyers — Security requirements and evidence should be negotiated before purchase and retained through acceptance, operation, support, and end of life.