Exiger Software Supply Chain Security (aDolus FACT) IT Security-Operations Integration And APIs: evidence and evaluation

What the source record establishes

Exiger presents software-supply-chain analysis that can derive bills of materials from firmware or binaries and surface component, vulnerability, provenance, and quality context; the capability incorporates aDolus FACT technology.

The maintained taxonomy connects that documented market position to IT Security-Operations Integration And APIs. This page keeps the claim at the level supported by the source: Exiger Software Supply Chain Security (aDolus FACT) presents an offering relevant to this work. It does not silently convert a product description into an observed result, a conformity finding, or a universal recommendation.

Current fit signal: Asset owners, OEMs, and integrators evaluating provenance, composition, vulnerability, and trust evidence for industrial software and firmware after Exiger acquired aDolus in 2024.

What IT security-operations integration and APIs means in this market

IT Security-Operations Integration And APIs should be evaluated as an operating chain rather than a feature label. The chain begins with a named business condition and governed input, passes through configured logic and accountable review, produces an output or action, handles exceptions, and preserves enough evidence for another person to reconstruct the decision later.

Asset inventory, context, and lifecycle

The maintained operating record for each OT asset's identity, role, location, owner, criticality, communications, dependencies, versions, configuration, support state, exposure, and recovery relevance.

Boundary: Discovery activity in production OT requires site authorization, engineering review, and method-specific safety constraints; a record is not proof of completeness.

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.

Boundary: Composition and certification evidence informs risk; it does not prove absence of defects, exploitability, secure integration, or product suitability.

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.

Boundary: A maintained mapping supports assurance work but does not establish legal applicability, compliance, certification, or effective risk reduction.

Activities that may sit inside the review

asset identity and taxonomy
active and passive collection
criticality and process role
software and firmware
ownership and lifecycle
secure development

Who owns the decision

A capability can be technically available while operating ownership remains fragmented. The evaluation should name the person accountable for policy or business interpretation, the person responsible for configuration and data, the reviewer with authority to resolve exceptions, the approver of release or action, and the owner of monitoring and retirement.

Related domain records commonly place responsibility with OT cybersecurity, control engineering, maintenance, reliability, enterprise asset management, product security. The local operating model may assign those roles differently, but it should not leave them implicit.

Exiger Software Supply Chain Security (aDolus FACT) should be asked to distinguish what the product decides, what it recommends, what it merely displays, and what remains an organizational judgment. A generic “human in the loop” statement is inadequate unless the human has time, context, evidence, and authority.

Evidence package to request from Exiger Software Supply Chain Security (aDolus FACT)

The exact product and package proposed, with a dated list of native, integrated, partner, service, and customer-owned components.
A representative input set, its authoritative source, permitted use, quality checks, and version history.
The configured workflow from intake through review, exception, approval, action, retention, and export.
A normal result and at least two difficult exceptions, including one caused by missing or contradictory evidence.
Role and access definitions for configuration, review, approval, override, monitoring, and administration.
An implementation map naming integrations, migrations, customer work, provider work, services, test environments, and release gates.
A retained decision record showing source, logic or model version, user action, timestamps, disposition, and downstream effect.
A measurement plan with baseline, observation period, population, error threshold, exclusions, and stop condition.

Demonstration script

Which exact Exiger Software Supply Chain Security (aDolus FACT) product, edition, module, service, and geography support IT security-operations integration and APIs?
What source data, content, rules, and integrations does Exiger Software Supply Chain Security (aDolus FACT) require before the workflow can begin?
Where does human judgment enter, and which person can approve, reject, override, or stop the IT security-operations integration and APIs workflow?
How does the proposed configuration handle missing data, conflicting evidence, changed rules, and an expired or revoked approval?
What record preserves inputs, transformations, user actions, exceptions, outputs, timestamps, and downstream consequences?
Which parts are native, partner-delivered, service-delivered, or left to the customer?
What can be exported at implementation, audit, renewal, migration, and exit?
Which observation would falsify the current fit hypothesis for Exiger Software Supply Chain Security (aDolus FACT)?
What population and network boundary does each collection method see?
How are duplicate, transient, dormant, serial, virtual, and replacement assets resolved?
Which active methods are approved for each device class and operating state?
Can every field retain source, confidence, observation time, and responsible owner?

Use the same scenario with every finalist. Let the provider explain differences in architecture, but keep the business condition, required evidence, exception, and expected decision record constant. That makes the evaluation comparable without pretending that unlike products should receive one synthetic score.

Failure modes and boundary conditions

a one-time network scan
device counts without identity confidence
internet search as an authorized site inventory
SBOM presence as proof of security
certificate logo without scope
vendor questionnaire as independently verified fact

This seed review did not independently test deployment safety, detection efficacy, protocol depth, sensor performance, integration behavior, operational impact, implementation effort, package availability, or customer outcomes.

A buyer should also distinguish absence of public evidence from evidence of absence. If Exiger Software Supply Chain Security (aDolus FACT) has not publicly documented a required detail, the correct status is “not established in this review” until a current, attributable source or direct observation resolves it.

Authority and standards context

NIST SP 800-82 Rev. 4 pre-draft

Teams should monitor the revision without silently relabeling Rev. 3 mappings as Rev. 4 or presenting proposed structural changes as final requirements.

Interpretation boundary: A pre-draft call establishes the revision process and questions, not final Rev. 4 content or dates.

This mapping identifies a workflow that may help organize evidence. It does not state that Exiger Software Supply Chain Security (aDolus FACT) conforms to, complies with, or is certified against the authority.

Joint OT asset inventory guidance

It raises the evaluation bar from device counts to governed identity, taxonomy, criticality, ownership, dependency, lifecycle, and use across operating functions.

Interpretation boundary: The guidance does not endorse a discovery method or permit unsafe active scanning of a production environment.

CISA Secure by Demand for OT

It turns cybersecurity into a procurement and lifecycle evidence decision rather than an after-deployment add-on.

Interpretation boundary: The guide supports buyer diligence; it does not certify products or replace site-specific engineering and procurement judgment.

Comparable records to inspect

The following organizations also have current official positioning mapped to IT security-operations integration and APIs. Inclusion is a research pathway, not a shortlist or claim of equivalence.

Industrial Defender — OT Asset Inventory And Configuration-Risk Platform with documented positioning relevant to IT Security-Operations Integration And APIs
NetRise — OT Asset Inventory And Configuration-Risk Platform with documented positioning relevant to IT Security-Operations Integration And APIs
Octave Cyber Integrity — OT Asset Inventory And Configuration-Risk Platform with documented positioning relevant to IT Security-Operations Integration And APIs
OTbase — OT Asset Inventory And Configuration-Risk Platform with documented positioning relevant to IT Security-Operations Integration And APIs
ABB Industrial Cybersecurity — Industrial OEM Security Portfolio with documented positioning relevant to IT Security-Operations Integration And APIs
ANDRITZ RAM² — Industrial Cyber-Risk And Governance Platform with documented positioning relevant to IT Security-Operations Integration And APIs

Official authority sources

The following primary authority pages support the standards context used in this record. They define an evaluation boundary; they do not endorse Exiger Software Supply Chain Security (aDolus FACT) or establish product conformity.

NIST SP 800-82 Rev. 4 pre-draft

Open the official authority source and confirm the current text, effective date, scope, and organization-specific applicability before relying on this mapping.

Joint OT asset inventory guidance

Open the official authority source and confirm the current text, effective date, scope, and organization-specific applicability before relying on this mapping.

CISA Secure by Demand for OT

Open the official authority source and confirm the current text, effective date, scope, and organization-specific applicability before relying on this mapping.

Conditional conclusion

Exiger Software Supply Chain Security (aDolus FACT) belongs in deeper evaluation for IT security-operations integration and APIs when its documented OT asset inventory and configuration-risk platform operating model matches the buyer's real workflow, the proposed package contains the required components, and a representative test produces reviewable evidence through normal and exception paths. The conclusion should be reversed or narrowed when the product boundary, source data, authority mapping, integration burden, human decision rights, exportability, or measured result does not meet the stated approval conditions.