{{first_name | Reader}},

In partnership with:

Opal Security — Meet Opal Zero, the first end-to-end access governance platform for AI agents. Zero standing access. Zero human toil. Zero friction. [Product Launch]

Smallstep — SCEP is a password. Passwords get stolen. Real Zero Trust starts with the device — begin with Wi-Fi, extend across apps and infrastructure.

LockThreat — AI-powered GRC that replaces legacy tools and unifies compliance, risk, audit and vendor management in one platform.

Cite the record - The record behind this brief is public, inspectable, and citable.

The weekly brief is where things get worked out. The daily CISO briefing on Spotify is the fast version: two minutes each weekday on what actually moved. Follow it here.

CYBERSECURITYHQ

Issue No. 39 · 22 September 2026

CHQ maintains ratings on a standing set of structural security conditions. Each rating reflects the current maturity and confirmation of a condition, not a forecast. Conditions carry their permanent identifiers from the public CHQ Structural Conditions Registry, where dated definitions and falsification criteria are maintained. From this issue, rating actions cite the provisions of the CHQ Criteria Governance Standard under which they are taken. The report leads with what changed; the full board follows.

No rating changed this week. One condition sits under review with its evidence pinned, and the review is Thursday.

Last issue this board voided an upgrade to the timing condition, SC-2026-006, because the criterion behind it was found to measure the wrong thing. The condition has stayed under review since, displaying its last valid rating, Strengthening, while a replacement criterion was adopted for the September 24 review. That replacement asks the only question the condition's name ever meant: was a vulnerability exploited before anyone had publicly disclosed it?

The review runs Thursday, and for the first time this board can say exactly what it will decide on. PaperCut's print-management flaws were exploited on August 26, by the timestamp in a responder's own log, and publicly disclosed by the vendor on August 27. One day, two dated fields, two named sources. That is a qualifying instance under the revised criterion, and it is the only one in the window whose dates are pinned at the grade the Standard requires. Five other candidates carry zero-day labels and no dates; a label is not a chronology, and they stay indeterminate until a source supplies a day.

Why it matters is simple. If the instance holds against its two primary sources on Thursday, the condition returns to Confirmed through a valid instrument. If it does not hold, the condition stays under review honestly. Either way the reader will see the two dates, the two sources, and the rule.

The tooling condition's quiet streak ended two weeks ago; it has been the loudest condition on the board since. Cisco's Firewall Management Center returned on September 9 with an authentication bypass reaching root. The Secure Email Gateway followed on the 14th with an unauthenticated SQL injection, also to root. The Identity Services Engine, the network-access-control platform, followed on the 16th. Three products whose job is to secure other things, each reached without credentials, inside eight days.

What this is and is not, by rule. It is a cluster: three catalog entries, one vendor, three security products. Cisco Talos separately describes three intrusion clusters exploiting vulnerabilities in the Firewall Management Center, including one it assesses as a ransomware operator; those clusters span two management-center vulnerabilities and do not establish linkage across the three catalog entries. It is not, on this evidence, a campaign, because campaign linkage is a separate proposition from exploitation and does not inherit exploitation's grade (CGS-3.2); three entries in a week is adjacency, and adjacency is not linkage (CGS-6.2). The condition's review trigger is linkage evidence, not entry count. The Outlook moved to Accumulating on the second entry and stays there.

SC-2026-002 · Edge and Management-Plane Compromise: affirmed CONFIRMED. MikroTik RouterOS entered with a two-vulnerability chain confirmed under active exploitation by CERT Polska; Zyxel switches followed yesterday. GitLab entered at the top of the severity scale with an unauthenticated file read on its commits API, the second source-control platform in three weeks, with in-the-wild probing reported within hours of public disclosure. One chronology resolved: Citrix's NetScaler bulletin is dated August 19, fifteen days before exploitation was observed, so that case is post-disclosure and non-qualifying under the timing criterion, and a fifteen-day vendor lead on the vendor-signal ledger.

SC-2026-010 · Vendor Risk-Signal Reliability: affirmed EMERGING, Outlook Receding. Under the registry's chronology test, seven vendor-ahead cases since the reset and no documented reversal; the Citrix lead above is an eighth candidate pending the ledger session. Re-escalation requires three new reversals.

SC-2026-008 · Autonomous AI Attack Operations: affirmed CONFIRMED. Counted set unchanged. The Position-candidacy review opened by the ceiling rule has produced a draft, disclosed below.

SC-2026-007 · Enterprise Application Plane Exploitation: affirmed CONFIRMED. Quiet this week; Acronis Backup, a recovery console, routed to platform administration rather than here.

SC-2026-004 · AI Agent Runtime Compromise: affirmed EMERGING. Quiet on its own mechanism.

Evidence note: materiality without impact. Two filings surfaced this week in which companies determined a cyber incident material while stating in the same document that it had no material effect on operations or financial results: a healthcare-IT provider in March, on the sensitivity of the data involved, and a fintech in April, on reputational, legal, and response-cost exposure. This board records that as a third determination class beside operational disruption and extortion: qualitative materiality. Together, the two filings demonstrate that a company can determine a cyber incident material on the nature and potential consequences of the event even where current operational and financial effects are not material. Read with the routing gap reported last issue, that widens the range of what a materiality determination can rest on; it does not, on two filings, establish a general rule.

Governance. The Criteria Governance Standard, declared last issue, is in force from today. Rating actions cite its provisions; this issue's citations are inline. Nothing in the Standard changed this week, and the reader should expect that: it changes only under its own Section 11.

Position pending. The escalation trigger met on September 3 opened a Position-candidacy review under the ceiling rule (CGS-8.7). The review found the issuance gate's sufficiency test met and produced a draft, on agent containment as a structural condition of agent deployment, with falsification criteria declared and an adversarial paragraph carrying the one-operator objection. It awaits ratification and is not a registry entry until ratified.

Intake. Seven consecutive runs under the deterministic intake mechanism (CGS-9.1): the registry matched the catalog byte-for-byte on four of them and admitted new entries at zero or one day's lag on the other three. Two scheduled source passes have slipped twice on tooling and are gated to Wednesday with a fallback declared. Catalog census from the versioned file: 1,717.

Criteria versions in force or scheduled for this review cycle. Rating scale v1.2; Watch and Outlook v1.0; state machine, pause and reset v1.0; ceiling-consequence rule v1.0; SC-2026-010 independence unit v1.0; SC-2026-006 criterion v2.0 (effective 24 Sep 2026); criterion-invalidation and void-action rule v1.0; sub-class accrual rule v1.0; CHQ Criteria Governance Standard v1.0 (effective 22 Sep 2026).

For exploitation conditions, the confirmation threshold is confirmed production exploitation; each non-exploitation condition declares its own threshold in the registry. Under review is an analytical status, not a rating; the last valid rating remains displayed until a valid criterion produces a subsequent action.

Outlook describes the direction of evidence accumulation in the trailing window: Accumulating, Stable, Receding. It is not a prediction. Watch indicates a defined reclassification trigger is mechanically near, and is directional; when proximity exists in both directions, both are shown.

Three of one vendor's security products were exploited inside eight days, each reached without credentials, each a system whose purpose is to secure other systems. That creates a concentration question distinct from the vulnerability of any individual product. The question for the reader: when the console that manages your firewalls, the gateway that inspects your mail, and the platform that admits your devices all come from the same company, is that concentration written anywhere as a risk, or is it recorded only as a discount?

Three questions for your own program this week. For each management console in your estate, who can reach it from a user segment today, and when was that last verified rather than assumed? For the two most recent zero-days that touched your estate, can you state the date exploitation was first observed and the date it was disclosed, with a source for each? And when your disclosure counsel determines materiality, is the basis written down as consequence, as impact, or as whichever fits?

CybersecurityHQ publishes independent structural intelligence for security leadership. Conditions, positions, and falsification criteria are maintained at record.cybersecurityhq.com. Ratings reflect observable structural conditions at a point in time. They are not forecasts and do not assess applicability to any specific organization's environment.