What should a KillChains.com citation include?
Include the page title, KillChains.com as publisher, release or visible review date, canonical URL, access date, and the relevant evidence-state wording.
Read the supporting sectionCitation and reuse
How to cite KillChains.com pages, evidence records, datasets, and simulations
Citations should preserve the canonical page, release version, visible review date, access date, source state, and the distinction between public evidence and synthetic simulation output.
Version-specificEvidence-state awareStable canonical URLs
Answer-first summary
Direct answers
Can a saved Atlas URL be treated as immutable evidence?
No. It reproduces a view of the current release; cite the release version, visible record, source trail, and access date as well as the URL.
Read the supporting sectionPublic page
Cite the page as a versioned web publication.
Recommended elements: page title, publisher, release version, visible content-review date, canonical URL, and access date.
KillChains.com. “What Is a Kill Chain? Definitions.” Release 1.4.0, reviewed 2026-08-01. https://killchains.com/what-they-are.php. Accessed 2026-08-01.
For styles that place the access date before the URL, retain the same information. Do not treat the release date as the date of an underlying government or manufacturer source.
Evidence Atlas
Cite both the Atlas view and the underlying source trail.
KillChains.com. “Global Kill Chain Evidence Atlas.” Release 1.4.0, reviewed 2026-08-01. https://killchains.com/atlas.php. Accessed 2026-08-01.
A shared Atlas URL can preserve filters, selected entities, comparison choices, and timeline state. It is a view of the current release—not an immutable archival record. Record the release version and cite the visible source IDs or original sources supporting the claim.
Synthetic challenge
Identify the result as a fictional instructional artifact.
KillChains.com. “Daily Break the Chain: [challenge title and code].” Synthetic interactive simulation, release 1.4.0, seed [seed if relevant]. https://killchains.com/?challenge=[id]&seed=[seed]. Accessed 2026-08-01.
State explicitly that timings, confidence values, evidence objects, actors, locations, and outcomes are synthetic. A replay demonstrates consequences inside a scripted causal model; it does not predict real system performance or establish a real-world fact.
Claim attribution
Carry the evidence state into the citation sentence.
| Visible state | Recommended wording |
|---|---|
| Officially documented | “The organization’s public policy states…” or “The official program description identifies…” |
| Manufacturer-described | “The manufacturer says…”; do not rewrite as independently verified field behavior. |
| Independent analysis | “The study concludes…” or “The analysts interpret…” with the method and limitation preserved. |
| Disputed or alleged | Name the claimant, the response or dispute, and the absence of decisive public verification. |
| Publicly unspecified | State that reviewed public evidence does not establish the mode, authority, threshold, or status. |
| Fictional simulation value | Label it synthetic and avoid presenting it as a measurement of any real system. |
Machine-readable discovery
Use indexes for discovery, then cite the human-readable record.
content-index.jsonlists canonical routes, page summaries, topics, and direct questions.source-index.jsonmirrors the public source registry with source IDs and bounded support statements.feed.xmlandfeed.jsonexpose current release discovery entries.llms.txtis a nonstandard convenience map, not a citation, access-control file, or ranking guarantee.
Machine-readable files are derived from repository-owned page and source registries. The canonical page and original public source remain the human-readable evidence path.
Quotation and reuse
Preserve context, attribution, and uncertainty.
Short quotations should identify KillChains.com and link to the canonical page. Do not crop away “synthetic scenario,” “manufacturer claim,” “unknown,” generation date, review date, or source-state labels from shared artifacts. External source material remains subject to the rights and terms of its original publisher.
For code and repository material, review LICENSE and THIRD_PARTY_NOTICES.md.