Cybersecurity entity

U.S. Central Command

organization

Donald Trump is the most frequent co-covered peer, appearing in 3 of the 3 tracked stories. Coverage clusters in security, which accounts for 2 of those 3, with the remainder spread across 1 other category. The 8.7 average consequence score is above the beat benchmark of 7.1 in the same window.

Last mentioned: Jul 12, 2026

Entity pulse

Recent coverage · U.S. Central Command

3 stories
8.7 avg impact
0% positive
100% negative

Coverage balance Negative coverage leads. Negative coverage exceeds positive coverage by 100 percentage points.

  • 100% negative

Figures are computed live from our source-verified story record — see our methodology for how impact and sentiment are derived.

What the coverage shows about U.S. Central Command

Donald Trump is the most frequent co-covered peer, appearing in 3 of the 3 tracked stories. Coverage clusters in security, which accounts for 2 of those 3, with the remainder spread across 1 other category. The 8.7 average consequence score is above the beat benchmark of 7.1 in the same window. The 12-day window averages about 1.8 stories each week. They are better corroborated than the beat average, carrying 3.3 original sources each against 3 for the same window. We currently track 3 Cybersecurity stories that mention U.S. Central Command, published between March 1, 2026 and March 12, 2026.

Stories tracked
3
Per week
1.8
Sources per story
3.3

Computed from the 3 stories linked to this entity, with beat comparisons drawn from all 169 Cybersecurity stories published in the same date window. Shares are omitted below five stories and comparisons below a twenty-story baseline.

Coverage cohort

Appears alongside

Other entities that clear the same relevance threshold in stories also covering U.S. Central Command. Shared-story counts are live from our verified record — not editorial picks.

Timeline

  1. DIA Link Revealed

    AP sources confirm the strike was based on outdated coordinates provided by the Defense Intelligence Agency.

  2. Senate Demand

    A group of 45+ senators sends a formal inquiry to the Pentagon regarding targeting failures.

  3. NYT Report

    The New York Times reports that a preliminary investigation points to U.S. responsibility for the school bombing.

  4. Initial Strike

    U.S. forces carry out a missile strike on what was identified as a military target in Iran.

  5. Reports Surface

    WSJ and other outlets report the military's continued use of the banned technology due to deep integration.

  6. Tehran Compound Strike

    US and Israeli forces target the central Tehran compound of Ayatollah Ali Khamenei.

  7. Netanyahu Address

    Israeli PM states there are 'growing signs' the Supreme Leader was killed in the attack.

  8. Trump Regime Change Call

    US President releases a video urging Iranians to take over their government.

  9. IRGC Retaliation

    Revolutionary Guard launches drones and missiles; Israel issues nationwide warnings.

  10. Executive Order Signed

    President Trump signs a mandate requiring all federal agencies to immediately cease using Anthropic's AI technologies.

  11. Iran Strikes Commenced

    US and Israeli forces launch massive strikes on Iranian targets hours after the ban was issued.

  12. CENTCOM Defiance

    Military commanders continue using Claude AI for real-time intelligence analysis during the strikes.

Stories mentioning U.S. Central Command 3

Security Negative

Defense-Tech Crisis: CENTCOM Deploys Banned Anthropic AI in Iran Strikes

The US military reportedly utilized Anthropic’s Claude AI for intelligence and targeting during recent strikes on Iran, directly contravening an executive order from President Trump. The incident highlights a growing rift between the administration’s ideological tech bans and the operational realities of deeply embedded AI in modern warfare.

3 sources

U.S. Central Command is linked from 3 stories on this site, each scored at or above our 35% relevance threshold — see how these pages are built.

See something wrong on this page — a misattributed entity, a wrong stat, a broken source link? Report a data issue.