What the source record establishes
Cylus presents CylusOne as a rail-specific cybersecurity platform for trackside, rolling-stock, signaling, command-and-control, station, and maintenance environments.
The maintained taxonomy connects that documented market position to Topology, Communication, And Dependency Mapping. This page keeps the claim at the level supported by the source: CylusOne 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: Passenger, freight, urban, and mainline rail operators evaluating asset visibility, vulnerability context, detection, investigation, and standards evidence for rail operational systems.
What topology, communication, and dependency mapping means in this market
Topology, Communication, And Dependency Mapping 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.
Network architecture, segmentation, and conduits
The design and maintained evidence for security zones, conduits, trust boundaries, routable paths, industrial DMZs, enforcement points, fail states, and allowed communication supporting physical operations.
Boundary: A discovered flow, recommended rule, or reference architecture is not authority to reconfigure production networks or proof of safe segmentation.
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
- zones and conduits
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. The local operating model may assign those roles differently, but it should not leave them implicit.
CylusOne 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 CylusOne
- 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 CylusOne product, edition, module, service, and geography support topology, communication, and dependency mapping?
- What source data, content, rules, and integrations does CylusOne require before the workflow can begin?
- Where does human judgment enter, and which person can approve, reject, override, or stop the topology, communication, and dependency mapping 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 CylusOne?
- 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
- a flat topology picture
- firewall presence as proof of segmentation
- automatic blocking without operational authority
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 CylusOne 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
NERC CIP-015-1
The standard creates a concrete evidence and operating-model test for network telemetry, anomaly detection, evaluation, escalation, and record retention.
Interpretation boundary: Only the controlling NERC standard, implementation plan, entity registration, asset classification, and facts determine applicability and compliance.
This mapping identifies a workflow that may help organize evidence. It does not state that CylusOne conforms to, complies with, or is certified against the authority.
NIST SP 800-82 Rev. 3
Provider and architecture claims can be tested against a mature OT-specific control context without pretending the guide certifies a product or environment.
Interpretation boundary: NIST guidance supports risk management. It does not establish organization-specific compliance, a safe configuration, or product fitness.
This mapping identifies a workflow that may help organize evidence. It does not state that CylusOne conforms to, complies with, or is certified against the authority.
ISA/IEC 62443-3-2
It provides the central architecture language for comparing discovery, segmentation modeling, enforcement, remote access, and controlled-transfer products.
Interpretation boundary: Tool-generated zones, scores, or diagrams do not replace accountable system definition, risk assessment, or engineering approval.
This mapping identifies a workflow that may help organize evidence. It does not state that CylusOne conforms to, complies with, or is certified against the authority.
Comparable records to inspect
The following organizations also have current official positioning mapped to topology, communication, and dependency mapping. Inclusion is a research pathway, not a shortlist or claim of equivalence.
- Claroty — OT Visibility And Threat-Detection Platform with documented positioning relevant to Topology, Communication, And Dependency Mapping
- Darktrace / OT — OT Visibility And Threat-Detection Platform with documented positioning relevant to Topology, Communication, And Dependency Mapping
- Dragos Platform — OT Visibility And Threat-Detection Platform with documented positioning relevant to Topology, Communication, And Dependency Mapping
- EmberOT — OT Visibility And Threat-Detection Platform with documented positioning relevant to Topology, Communication, And Dependency Mapping
- Exalens — OT Visibility And Threat-Detection Platform with documented positioning relevant to Topology, Communication, And Dependency Mapping
- Nozomi Networks — OT Visibility And Threat-Detection Platform with documented positioning relevant to Topology, Communication, And Dependency Mapping
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 CylusOne or establish product conformity.
NERC CIP-015-1
Open the official authority source and confirm the current text, effective date, scope, and organization-specific applicability before relying on this mapping.
NIST SP 800-82 Rev. 3
Open the official authority source and confirm the current text, effective date, scope, and organization-specific applicability before relying on this mapping.
ISA/IEC 62443-3-2
Open the official authority source and confirm the current text, effective date, scope, and organization-specific applicability before relying on this mapping.
Conditional conclusion
CylusOne belongs in deeper evaluation for topology, communication, and dependency mapping when its documented OT visibility and threat-detection 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.