One Intrusion, Followed to an Answer You Can Cite
Scroll down to watch four figures follow one sample intrusion through Asterism. CRANE-41, Hold Music and every report below are invented for this page, and the addresses and domains sit in ranges reserved for documentation.
Fig. 1 · Noise
Four Names for One Week of Intrusions
A CERT bulletin, two vendor write-ups, a researcher's thread and an ISAC digest describe the same week of help-desk intrusions. They call the intruder four different things, and one address,
198.51.100[.]23, turns up in four of them.Read one at a time, they look like four separate stories.
- 21 Oct 09:12cert.exampleadvisoryActivity cluster 2026-114: help-desk resetscluster 2026-114198.51.100[.]23T1566.004
- 21 Oct 14:12vendor-a.examplerssCRANE-41 calls the help deskCRANE-41198.51.100[.]23helpdesk-sso.example[.]netT1656
- 22 Oct 05:12vendor-b.examplepdfHold Music returns with new infrastructureHold Music198.51.100[.]23helpdesk-sso.example[.]netT1656T1556.006
- 22 Oct 20:12researcher.examplethreadSame infra, new domains"the help-desk crew"198.51.100[.]23sso-verify.example[.]com
- 24 Oct 09:12isac.examplemailDaily digest, one TLP:CLEAR itemhelpdesk-sso.example[.]netsso-verify.example[.]comT1556.006
4 names for one intruder1 address in 4 reports1 domain in 3
Fig. 1Five sample reports as they arrive, newest last.Plate II Fig. 2 · Extraction
Pull Out Everything You Could Pivot On
Each report is read for indicators, threat actors and their aliases, malware, tools, CVEs and ATT&CK techniques. Indicators are refanged for matching and shown defanged.
A name nobody has used before stays a candidate, out of every count and export, until a second organization reports it or an analyst approves it. One blog post can't invent an actor.
paragraph 3The intruders, a cluster we track as CRANE-41, phoned the service desk while posing as a contractor and talked an agent into resetting a password. Within the hour the account signed in from 198.51.100[.]23, and the next morning helpdesk-sso.example[.]net went live.
- actorCRANE-41candidate · 1 organization so far, held out of counts
- ipv4198.51.100[.]23also in 3 other reports
- domainhelpdesk-sso.example[.]netalso in 2 other reports
- techniqueT1656Impersonation · also in 1 other report
Fig. 2One paragraph, four entities, each typed and linked back to the sentence it came from.Plate III Fig. 3 · Correlation
Link the Reports That Share Evidence
Shared infrastructure and techniques pull the five reports into one Story. Gravity then tests each pairing of entities against chance and ranks it by a conservative lower bound, and an organization that repeats itself counts as one witness.
A pairing seen by one organization is never counted as evidence; where the graph shows it, it's dashed. CRANE-41 stays a hollow candidate until a second organization names it.
CRANE-41198.51.100[.]23Fig. 3Grey lines are mentions. Teal lines are Gravity scores at their 95% lower bound, with the number of independent organizations behind each. Dashed pairs have one organization and are never counted as evidence.Plate IV Fig. 4 · Answer
Ask the Question You Came With
Ask in AQL, the Asterism Query Language, or click any entity and every view refocuses on it. Defanged indicators work as typed.
Here the question is who saw this intrusion first and what each later report added. The Story answers it, and the four names stay side by side for an analyst to judge.
ip:198.51.100[.]23 published:>now-14d
4 reports, all in 1 Story of 5 reports from 5 organizations · names in use: cluster 2026-114, CRANE-41, Hold Music, the help-desk crew, all held as candidates
- certfirst · address, T1566.004 (cluster 2026-114)
- vendor-a+5 h · domain, T1656 (CRANE-41)
- vendor-b+20 h · T1556.006 (Hold Music)
- researcher+35 h · sso-verify domain (the help-desk crew)
- isac+3 d · nothing new
Fig. 4The Story view's lanes, redrawn: who reported first, each source's lag, and what it added.Plate V



