Skip to content

Security Widely confirmed5 publishers 3 min read Published Updated

CISA ran the same tradecraft at two organisations; only the water utility caught it

Detection at the first hop forced CISA's red team onto donated access at Organization B. It did not stop the team reaching the same sensitive systems it reached at Organization A.

The Watch · Security desk

Send a correction

What happened

  • CISA ran two red team assessments at the same time using similar tradecraft and got two different defensive responses.
  • At Organization A, a government services and facilities body, the team took multiple workstations, domain privileges, sensitive business systems and cloud without being detected.
  • At Organization B, a water and wastewater utility, defenders spotted the initial compromise and quarantined the affected systems.
  • From that host the team reached sensitive business systems, cloud and an OT DMZ bastion host, where defenders detected and isolated it again.

Why it matters

  • What's now possible capability One early catch is the only thing in either engagement that changed the attacker's economics: after it, further progress had to be granted by the defender rather than taken.
  • What it limits constraint Catching the first hop does not harden anything behind it, so the utility bought containment at the edge of the intrusion rather than depth against it.
  • Who's exposed exposure Any application that can send mail from an internal address turns forgotten default credentials into an authenticated phishing channel, and recipients get no signal to distrust it.
  • What it sets up precedent Publishing a paired comparison with both organisations' agreement sets up defender performance, not tradecraft novelty, as the thing critical infrastructure advisories are read for.

The assume-breach pivot is the measurement. Once Organization B's defenders quarantined the systems compromised at initial access, CISA could not proceed on its own footing, so trusted agents inside the organisation handed the team a host built to replicate the access it would have held had nobody noticed [4]. Everything the advisory then records at Organization B, up to and including the bastion host in the OT demilitarized zone, ran on access the team was given rather than access it took [5][16]. That is the honest accounting of what one early catch bought: the earned portion of the intrusion ended at the first hop [16].

What it did not buy was an interior that held. Seated on an equivalent host, the same tradecraft arrived at the same classes of target in both organisations, sensitive business systems and cloud resources alike [13]. Organization B's second detection came at the OT DMZ, after that reach had already been demonstrated [5], and CISA notes it showed the ability to touch OT systems without actually doing so [11].

Organization A's entry is the part worth reading twice. Reconnaissance turned up a web application whose built-in accounts still carried default credentials, which let the team send mail from an internal address; phishing from that address put them on four workstations [8]. From there they ran a BloodHound collector modified to slip static EDR signatures while scraping users, computers, groups, access control lists, organisational units and group policy objects [9]. The customisation is the tell: endpoint detection and response was present enough at Organization A to be worth engineering around, and it produced nothing across initial access, domain-level privilege escalation and lateral movement to sensitive business systems and cloud [3][9][17]. One compromised workstation also sat at the default Machine Account Quota of 10, meaning unprivileged users could add computer accounts [10].

Set the two counts side by side. Organization B's defenders acted twice; Organization A's recorded nothing at all [17]. In the advisory's own framing of the divergence, the variable is defender action, detection followed by quarantine and later isolation, and not any stated difference in product inventory, headcount or spend [14]. The organisation that caught it was the water and wastewater one, and the one that did not was in government services and facilities [2][7].

CISA published the comparison with both assessed organisations' agreement, describing the activity, the defensive responses and the lessons for critical infrastructure [6]. The pairing is what makes it useful. Two engagements, similar tradecraft, one difference in outcome [1], and the difference lands on whether anyone was watching the first phished host rather than on how deep the intrusion could eventually go. Depth was available in both cases [13].

What to watch

  • Whether the advisory's technical detail or mitigations name the specific control or alert that fired at Organization B's initial compromise.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence76
Adoption
Not scored
Hype gap+12
Incentives35
Confidence72

Perspective Coverage

5 publishers
Builder
Builder 39%
Operator
Operator 53%
Investor
Investor 8%
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    CISA conducted two concurrent red team assessments using similar tradecraft and observed different defensive responses.

    Reported SupportedView cited source
  2. [2]

    Organization A is a Government Services and Facilities Sector organization; Organization B is a Water and Wastewater Systems Sector organization.

    Reported SupportedView cited source
  3. [3]

    At Organization A, the red team gained initial access to multiple workstations, gained elevated privileges over the domain, and moved laterally to sensitive business systems and cloud resources undetected.

    Reported SupportedView cited source
  4. [4]

    Because Organization B detected the initial compromise, the red team moved to an assume breach model in which Organization B trusted agents provided access to a host that replicated the level of access the red team would have had if defenders had not detected their activity.

    Reported SupportedView cited source
  5. [5]

    From the trusted-agent-provided host, the red team escalated privileges and moved laterally to sensitive business systems, cloud resources, and a bastion host in the OT demilitarized zone, where defenders again detected activity and isolated the system.

    Reported SupportedView cited source
  6. [6]

    In coordination with the assessed organizations, CISA released the advisory to describe the red team's activity and the organizations' defensive responses and to share lessons learned that critical infrastructure organizations can use to strengthen IT, cloud and OT cybersecurity posture.

    Reported SupportedView cited source
  7. [7]

    At Organization B, network defenders quickly detected the initial compromise and quarantined the affected systems.

    Reported SupportedView cited source
  8. [8]

    During reconnaissance at Organization A, the red team identified a web application with default credentials for multiple built-in user accounts that allowed the team to send emails from an internal email address; it used that address to send phishing emails and gained initial access to four workstations.

    Reported SupportedView cited source
  9. [9]

    From the workstations, the red team used a modified BloodHound collector, customized to avoid static endpoint detection and response signatures, to query and scrape Active Directory users, computers, groups, access control lists, organizational units and group policy objects.

    Reported SupportedView cited source
  10. [10]

    One compromised Organization A workstation had the default Machine Account Quota of 10, allowing unprivileged users to add up to 10 computer accounts.

    Reported SupportedView cited source
  11. [11]

    At Organization B the red team attempted to demonstrate its ability to access OT systems without actually doing so.

    Reported SupportedView cited source
  12. [12]

    The advisory maps the red team's activity to the MITRE ATT&CK Matrix for Enterprise framework, version 19.

    Reported SupportedView cited source
  13. [13]

    Once the red team held workstation-level access in either organization, it reached the same classes of target: sensitive business systems and cloud resources.

    Derived Supported
  14. [14]

    In the advisory's introduction and overview, the difference between the two engagements is stated in terms of defender action (detection, quarantine, isolation), with no difference in tooling, staffing or funding stated as the explanation.

    Derived Supported
  15. [15]

    CISA defines sensitive business systems as applications, data stores or infrastructure components where compromise would materially impact the organization's operations, finances or customer data, and they are selected by the assessed organization.

    Reported SupportedView cited source
  16. [16]

    At Organization B only the initial access phase was earned by the red team; every later step proceeded from access supplied by the organization's trusted agents.

    Derived Supported
  17. [17]

    Organization B's defenders produced two recorded detection events, at initial compromise and at the OT DMZ bastion host, while Organization A produced none across initial access, domain privilege escalation and lateral movement to sensitive business systems and cloud.

    Derived Contested

Sources

5 independent publishers whose own reporting we read for this story.

  1. cisa.gov

    1 article · August 25, 2026

    A Tale of Two SOCs: Insights From Two Red Team Assessments
  2. cyberscoop.com

    2 articles · August 26, 2026

    Water sector passes, government sector fails attempts to spot and halt simulated CISA attack
  3. scworld.com

    1 article · August 27, 2026

    CISA red team finds critical infrastructure vulnerabilities
  4. securityaffairs.com

    1 article · August 26, 2026

    CISA Red Team Fully Compromised Two Critical Infrastructure Orgs
  5. thehackernews.com

    1 article · August 26, 2026

    CISA Red Team Compromised Two Critical Infrastructure Orgs, One Detected Nothing

Topics and entities

Entities