1.0Step 01 of 4
Separate signals
Security sees commands and alerts. Operations sees equipment and process data. Neither view says whether the plant is at risk.
- SOC: a write to PLC-07, no process context
- Control room: pressure drift on PT-22, no network context
- Two queues, two tools, one event
SOC · NetworkAlert queue
Write to PLC-07 from engineering stationalert
New setpoint, valid function codeinfo
No process contextgap
Control room · ProcessTrend
PT-22 pressure flat after P-101 startdrift
Pump P-101 commanded onstate
No network contextgap
No shared question
Learned site model
One classification for both teamsOperationalCyberMixedUnknown
Cyber suspectedNot a verified incident. Verify operator identity and physical valve state before escalation. Inside the site boundaryVardar applianceLearn, detect, explainRaw OT data stays local
Mirrored traffic inFindings outNothing raw leaves
2.0Step 02 of 4
Evidence comparison
Vardar reads both paths against the learned site model. Agreement raises confidence; a single abnormal path stays under investigation.
- Network: write outside the learned sequence
- Process: command without a consistent response
- Both abnormal, so the event is corroborated
SOC · NetworkAlert queue
Write to PLC-07 from engineering stationabnormal
New setpoint, valid function codeinfo
No process contextresolved
Control room · ProcessTrend
PT-22 pressure flat after P-101 startabnormal
Pump P-101 commanded onstate
No network contextresolved
No shared question
Learned site model
One classification for both teamsOperationalCyberMixedUnknown
Cyber suspectedNot a verified incident. Verify operator identity and physical valve state before escalation. Inside the site boundaryVardar applianceLearn, detect, explainRaw OT data stays local
Mirrored traffic inFindings outNothing raw leaves
3.0Step 03 of 4
Shared decision
One classification for both teams: Operational, Cyber, Mixed or Unknown, with the evidence and the next check attached.
- Cyber suspected, not a verified incident
- Next check: operator identity and physical valve state
- Response ships closed; a person approves anything that acts
SOC · NetworkAlert queue
Write to PLC-07 from engineering stationabnormal
New setpoint, valid function codeinfo
No process contextresolved
Control room · ProcessTrend
PT-22 pressure flat after P-101 startabnormal
Pump P-101 commanded onstate
No network contextresolved
No shared question
Learned site model
One classification for both teamsOperationalCyberMixedUnknown
Cyber suspectedNot a verified incident. Verify operator identity and physical valve state before escalation. Inside the site boundaryVardar applianceLearn, detect, explainRaw OT data stays local
Mirrored traffic inFindings outNothing raw leaves
4.0Step 04 of 4
Local deployment
Everything that decides anything runs on one appliance inside the site boundary. Mirrored traffic and read-only process data in, findings out, nothing raw leaves.
- Passive SPAN or TAP, never in the path
- Air-gap ready, signed updates by approved media
- Raw OT data and the site model stay on site
SOC · NetworkAlert queue
Write to PLC-07 from engineering stationabnormal
New setpoint, valid function codeinfo
No process contextresolved
Control room · ProcessTrend
PT-22 pressure flat after P-101 startabnormal
Pump P-101 commanded onstate
No network contextresolved
No shared question
Learned site model
One classification for both teamsOperationalCyberMixedUnknown
Cyber suspectedNot a verified incident. Verify operator identity and physical valve state before escalation. Inside the site boundaryVardar applianceLearn, detect, explainRaw OT data stays local
Mirrored traffic inFindings outNothing raw leaves