Increased monitoring as a compensating control
Increased monitoring is a detective control: it shortens the time to notice an attack and prevents nothing. For PHP2Shell (CVE-2026-109618, KEV 26 Oct 2026) CISA's SIGMA rule gives a monitor eight match branches to run. For F5 CVE-2026-94127 (KEV 22 Sep 2026) neither F5 nor CISA published anything to match.
On this page
What it changes and what it does not
Eight of the nine register entries reduce the chance of exploitation. This one reduces the time between exploitation and response. It prevents nothing, and for a flaw already exploited in the wild it is a weak control on its own.
NIST SP 800-53 SI-4 e gives the trigger for raising it: "Adjust the level of system monitoring activity when there is a change in risk to organizational operations and assets, individuals, other organizations, or the Nation;". A newly disclosed, unpatched flaw is a change in risk, and the entry should say monitoring was raised for that reason on that date. SI-4 d turns collection into a control: "Analyze detected events and anomalies;". Collection with no analysis and no owner is a log.
Do not confuse it with the monitoring step in SP 800-40 Rev. 4 Section 2.2, "Continuously monitor the risk response", which watches that a mitigation stays in place. This page is about watching for exploitation.
What a monitor has to match
A rule needs something to match. The four KEV records below give very different amounts, and the amount decides how much the control is worth.
| CVE | Published in the advisory or CISA alert | What a monitor can match |
|---|---|---|
| CVE-2026-94127 (F5 BIG-IP APM) | Advisory 22 Sep 2026, KEV the same day, due 25 Sep 2026 | No log strings, file paths or indicator addresses from F5 or CISA. Only the configuration and version can be read |
| CVE-2026-0322 (PAN-OS) | Advisory and KEV 14 Oct 2026, due 17 Oct 2026 | Three indicator addresses: 66[.]42[.]72[.]14, 208[.]83[.]239[.]114, 149[.]248[.]47[.]234. No log signatures or file indicators |
| CVE-2026-104286 (FortiMail) | Advisory and KEV 1 Oct 2026, due 4 Oct 2026 | Two addresses, three System event log patterns and two Encryption log lines, printed on the disable-a-feature page |
| CVE-2026-109618 (PHP) | Alert 21 Oct 2026, SIGMA rule added 23 Oct, KEV 26 Oct 2026 | CISA's SIGMA rule (8 branches, 95 indicator strings), PHP worker processes launching shells, AH00051 error entries, outbound connections from workers |
Monitoring fits the last two rows. The PHP2Shell rule is worked next. F5 shows the empty end: CVE-2026-94127 (heap buffer overflow in BIG-IP APM, CVSS 4.0 base score 9.3) came with an iRule on request through an F5 support ticket and no log string or address (F5 CVE record, read 19 Nov 2026). CISA's wording is to apply the iRule "as a temporary step to allow proactive forensic triage", then patch. BOD 26-04 defines the text "& forensic triage" as meaning "the agency must complete remediation or mitigation action within the timeline (three days) and carry out a forensic triage of the asset to assess whether the system is compromised." KEV added the CVE on 22 Sep 2026, due 25 Sep. There monitoring cannot be the entry: it only tells you whether the window already cost something.
Worked case: CISA's SIGMA rule for PHP2Shell, CVE-2026-109618
CISA's alert of 21 Oct 2026 gained a SIGMA rule on 23 Oct. The file read on 19 Nov 2026 is CISA_SIGMA_261429_r2v1_CVE_2026_109618-109619_PHP2Shell_TLP_CLEAR.yaml in the cisagov/SIGMA_Rules repository: rule ID 741682b9-041e-4a31-b314-c58b15a82cf2, status test, level critical, dated 21 Oct 2026 and marked modified 5 Nov 2026. It is one condition that ORs eight branches; inside a branch every keyword group must be present. The table lists what each branch matches and the log it needs.
| Branch | Log it needs | Matches (all groups in the branch) |
|---|---|---|
| 1 Request | Web or WAF log that carries request headers and body text, which a default access log does not | POST, index.php, PHPSESSID and PHP_SESSION_UPLOAD_PROGRESS, plus one of 15 request markers such as php2shell, B7kQpoc61, multipart/form-data or filename |
| 2 Process | EDR or audit process events on the web hosts | A web or PHP process name (php-cgi, apache2, httpd, php-fpm, mod-php) with one of 12 shell or tool words (/bin/sh, /bin/bash, cmd, powershell, python, curl, wget, netcat, nc, whoami, id, uname) |
| 3 PHP error log | PHP or Apache error log | "PHP Fatal error:", "Allowed memory" and " in Unknown " |
| 4 Web shell line | Web root file contents or response capture | The fragments <, php, echo, system, a $_GET lookup and > in one record |
| 5 Crash trace | Core dump or crash log | pDestructor, zif_system and libphp.so |
| 6 Upload progress | Web or WAF log with body text | multipart, PHP_SESSION_UPLOAD_PROGRESS, "very large", request or repeated, fields or form-data, and memory |
| 7 Cookie | Web or WAF log with response headers | Set-Cookie, PHPSESSID and "unusually large cookie value" |
| 8 Indicator list | Any log that holds addresses, names or hashes | Any one of 95 strings: 56 IP addresses, 17 file hashes, and 22 domain names, tool names and request markers |
Fastly, which measured the traffic, found no payload string to match, because the exploit is a failure condition, and said source IPs and User-Agent strings go stale within a day. Branch 8 therefore ages fastest; branches 2 and 3 describe what a compromised or failing worker does.
Checks for this rule
- Convert the rule with Sigma for your SIEM. Its logsource is the placeholder product cisa, and the file says to edit it only if you know your logsources, so map it and record which of the eight branches have a real log feeding them. A branch with no source cannot fire.
- Run it over every retained log back to 21 Oct 2026, 03:59 UTC, the first PHP2Shell-named request in Fastly's telemetry. On 19 Nov 2026 that is 29 days. A 30-day retention covers it; a 14-day retention reaches only 5 Nov.
- Test branch 3 on a test index: add one synthetic line holding the three phrases ("PHP Fatal error:", "Allowed memory", " in Unknown ") and confirm the alert fires, then delete the line. Do not send anything to a production host.
- Triage hits by branch. A branch 8 hit on an address or marker shows contact only; Fastly found about a third of the PHP2Shell-named traffic it saw labeled itself as authorized exposure or patch-state checking. A branch 2 or branch 3 hit, or an outbound connection from a PHP worker, points to a host that needs forensic triage. Branch 2 keywords such as id, nc and cmd also match inside longer words, so expect noise.
- Name the alert owner and the time to first look, and set the stop date: the entry ends when PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35 (or your distribution's patched package) is installed and the triage is closed.
What to record
Control: Increased monitoring (detective)
Finding: <CVE> on <asset group>, preventive control paired: <name>
Raised on: <date>; reason: change in risk (SI-4 e)
Detection rule ID and logic: <id>, <what it matches and source>
Branches with a live log source: <list>; branches without: <list>
Lookback run: from <date and time> over <days> of retained logs; hits: <n>
Match source published by: <vendor or CISA> on <date>, or none found on <date>
Test alert: <ticket or log line>, <date>
Owner and runbook: <name>, <link>; time to first look: <hours>
Alert review log: <location>
Stops or reviewed on: <date>
Forensic triage: <done / due date / not required>
Alert volume needs an owner who reviews it inside the stated time, because a rule that fires hundreds of times a day without review is not a control. Used alone against a flaw under active exploitation it is not enough: pair it with a preventive entry such as removing internet exposure. It is reasonable as the only control for a low-likelihood finding with a dated exception, which is the case the exception register is for. The effect of monitoring on the residual figure is in residual risk after mitigation, and the decision table shows when a mitigation may stand in for a fix.
Sources
- NIST SP 800-53 Rev. 5.2.0, SI-4, read 19 Nov 2026
- NIST SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning, Sections 2.1 and 2.2, read 19 Nov 2026
- CISA BOD 26-04, Appendix A, notes to Table 1, read 19 Nov 2026
- F5 CVE record for CVE-2026-94127 on CVE Services (vendor data: workaround, hotfixes), read 19 Nov 2026
- Fortinet PSIRT advisory FG-IR-26-175 (vendor), read 19 Nov 2026
- CISA alert, Critical Vulnerabilities in PHP Require Immediate Patching, read 19 Nov 2026
- CISA Known Exploited Vulnerabilities catalog, feed version 2026.11.18, read 19 Nov 2026
- CISA SIGMA_Rules, PHP2Shell rule r2v1 (rule text, modified 5 Nov 2026), read 19 Nov 2026
- Fastly, how Fastly detected and responded to PHP2Shell: first request time, indicator staleness, look-alike traffic, read 19 Nov 2026
Last reviewed