IMPLEMENTED BACKEND
Engineering functionality exists in the backend. This does not imply field deployment, a finished dashboard, or general commercial availability.
SentinelOT / Product Capabilities
SentinelOT is developing a passive, read-only industrial security investigation platform. Its backend foundations include standardized measurements, transparent detections, incident correlation, and evidence-backed assessment.
The capabilities below are classified according to their engineering maturity. Backend implementation does not mean commercial availability or verified deployment in an industrial facility.
00 / DEVELOPMENT TRANSPARENCY
IMPLEMENTED BACKEND
Engineering functionality exists in the backend. This does not imply field deployment, a finished dashboard, or general commercial availability.
QUALIFICATION PENDING
Engineering work exists, but additional approval, real-data validation, or integration checks remain.
PLANNED
Part of the future product direction. A complete, validated customer-facing capability is not currently available.
01 / DATA & DETECTION
Build a traceable foundation for investigating unusual process behavior.
F01 / PRODUCT CAPABILITY
Bring process observations into a consistent data foundation, preserving essential measurement and source information for investigation.
ILLUSTRATIVE EXAMPLE
Review a standardized sensor observation with its timestamp, source, and quality context.
ENGINEERING STATUS
Implemented (backend)
F02 / PRODUCT CAPABILITY
Exercise SentinelOT's investigation foundation using controlled replay workflows while preserving source context.
ILLUSTRATIVE EXAMPLE
Replay a prepared measurement sequence to test how the backend processes observations.
ENGINEERING STATUS
Implemented (backend)
F03 / PRODUCT CAPABILITY
Trace unusual process behavior to understandable detection rules and the measurements that triggered them.
ILLUSTRATIVE EXAMPLE
Review an abnormal measurement alongside the documented rule responsible for its detection.
ENGINEERING STATUS
Implemented (backend)
F04 / PRODUCT CAPABILITY
Keep observations linked to supporting evidence and data-quality context rather than hiding gaps in the source data.
ILLUSTRATIVE EXAMPLE
Identify when incomplete or delayed telemetry limits the evidence available for investigation.
ENGINEERING STATUS
Implemented (backend)
02 / INCIDENT INVESTIGATION
Organize related findings and understand their documented operational relationships.
F05 / PRODUCT CAPABILITY
Organize related alerts as incidents and preserve their investigation timeline.
ILLUSTRATIVE EXAMPLE
Examine a group of related process findings in a single chronological incident record.
ENGINEERING STATUS
Implemented (backend)
F06 / PRODUCT CAPABILITY
Add approved site, asset, and process-stage context to investigations when verified mapping data is available.
ILLUSTRATIVE EXAMPLE
Associate an incident with a documented process stage using an approved site profile.
ENGINEERING STATUS
Implemented (backend)
03 / EXPLAINABLE ASSESSMENT
Keep operational importance, supporting evidence, and uncertainty understandable.
F07 / PRODUCT CAPABILITY
The backend includes versioned risk inputs, traceable evidence snapshots, independent-support logic, and a separate evidence-confidence calculation.
ILLUSTRATIVE EXAMPLE
Review which evidence supports an assessment and whether required information is missing.
ENGINEERING STATUS
Implemented (backend components)
F08 / PRODUCT CAPABILITY
A deterministic backend scoring workflow evaluates documented operational factors while keeping evidence confidence separate. Synthetic end-to-end tests have passed; real-data validation and formal acceptance remain outstanding.
ILLUSTRATIVE EXAMPLE
Inspect deviation, operational importance, persistence, and independent evidence support without treating the result as attack probability.
ENGINEERING STATUS
Backend implemented; field qualification pending
04 / PRODUCT ROADMAP
These capabilities are planned or not yet validated as customer-facing features.
F09 / PRODUCT CAPABILITY
SentinelOT is designed with future passive integration into operational technology environments in mind. Safe field deployment has not been verified.
ILLUSTRATIVE EXAMPLE
Future authorized deployments would require site-specific integration and safety validation.
ENGINEERING STATUS
Planned / Not field-verified
F10 / PRODUCT CAPABILITY
The roadmap includes bounded, evidence-grounded analyst assistance. Supporting backend contracts and validation safeguards are being developed, but no complete customer-facing AI investigation feature is available.
ILLUSTRATIVE EXAMPLE
A future assistant could distinguish observed facts, interpretations, and unanswered questions.
ENGINEERING STATUS
Planned (customer-facing capability)
F11 / PRODUCT CAPABILITY
A dedicated analyst interface is planned for reviewing incidents, operational context, supporting evidence, and explanations.
ILLUSTRATIVE EXAMPLE
A future workspace could bring incident timelines and evidence details into one interface.
ENGINEERING STATUS
Planned
F12 / PRODUCT CAPABILITY
A guided public demonstration using fictional, predefined scenarios is planned separately from the production investigation backend.
ILLUSTRATIVE EXAMPLE
Visitors will be able to explore an illustrative investigation without connecting to an industrial system.
ENGINEERING STATUS
Planned (WEB-08)
05 / INTERPRETING ASSESSMENTS
Operational priority, evidence confidence, and cyberattack attribution represent different questions. They must not be treated as interchangeable.
01 / OPERATIONAL PRIORITY
OCRS evaluates documented process-related factors to support an investigation order. It is not a probability that a cyberattack occurred.
02 / EVIDENCE CONFIDENCE
Evidence confidence evaluates the support available for an analysis. It is calculated separately and does not increase or decrease the OCRS score.
03 / CYBER ATTRIBUTION
Unusual process behavior does not prove malicious activity. A cyber cause may remain unknown when verified supporting evidence is unavailable.
Operational scoring has been validated with synthetic engineering scenarios. Real industrial qualification and formal approval remain separate requirements.
Explore SentinelOT
A public demonstration is being prepared using fictional, predefined scenarios. It will illustrate investigation concepts without executing the real detection engine or connecting to an industrial system.
SentinelOT remains in development. No live industrial deployment is claimed.