Deception Check

Who watches the SIEM?

FortiSIEM response notes: carousel text equivalent.

1. Who watches the SIEM?

When the monitoring system is the target, its own clean-looking dashboard is not enough.

Schematic: an appliance and an independent record sit on opposite sides of an access boundary. The record remains outside the appliance.

Keep an independent record.

CVE context: Fortinet / Response: Deception Check.

2. Internal service. Actual reachability.

For CVE-2026-106173, check access to TCP 27918. Keep required FortiSIEM peer traffic; restrict unnecessary paths.

Reachability schematic: a required FortiSIEM peer path points to the TCP 27918 service. An unnecessary path ends at a restriction marker before the service.

Check the route, not the label.

Service guidance: Fortinet FG-IR-26-180.

3. A connection is not execution.

Connection seen. Request understood. File changed. Code executed. Each needs its own evidence.

Four independent evidence records: connection seen; request understood; file changed; code executed. There is no arrow asserting that one record proves the next.

State what your telemetry can actually show.

Visibility guidance: Deception Check.

4. Patch the flaw. Explain the change.

Use a trusted same-build baseline. Correlate unexpected file changes with independent activity records.

Investigation schematic: a trusted same-build baseline and a changed file are compared, with independent activity records below them.

An unchanged timestamp is not an all-clear.

Investigation guidance: Deception Check.

5. Separate storage. Separate control.

Can the appliance's credentials alter the evidence copy? Can another analyst retrieve it if the appliance is unavailable?

Access-boundary schematic: appliance credentials and the evidence copy are separated. The label "another analyst" appears on the evidence side of the boundary.

A second copy needs its own access boundary.

Evidence-handling guidance: Deception Check.

6. Fixed? Investigated?

Record the supported update and exposure controls separately from the investigation, evidence gaps, and next action.

Two closure records: fixed, supported update and exposure controls; investigated, investigation, evidence gaps, and next action. Each record has an owner.

Give every open question an owner.

Response checklist: Deception Check.

Sources and analysis

Vulnerability and service guidance: Fortinet FG-IR-26-180. Reported exploit mechanics: Horizon3.ai analysis. Evidence handling, investigation, and closure guidance: Deception Check.

Download the carousel PDF