# Conisec

> Independent publication covering crypto security incidents, exploits and regulation.
> Every claim cites a primary document — an official post-mortem, a status page, a
> regulator notice or a court filing. Loss figures are reported figures, attributed to
> whoever reported them, with the date they did. They are not our estimates.

Conisec publishes in English, Spanish, German, French and Brazilian Portuguese. Each
translated URL mirrors the English path under a language prefix (/es/, /de/, /fr/, /pt-br/).

Every security, incident and regulatory story carries "The Ledger": a fixed four-line panel
stating what happened, who is exposed, how to verify it yourself, and what changes. The
verification line is the point — we hand readers the check rather than asking for trust.

## Incident records
- [Incident Tracker](https://conisec.com/incidents/): dated, sourced log of crypto security
  incidents, exchange failures and protocol exploits. Each record cites a primary document
  and carries a status of Active, Contained, Resolved or Disputed.

## Jurisdictions
- [Crypto rules by country](https://conisec.com/rules/): what the published rules actually
  say, country by country — legality, licensing, tax treatment and reporting duties. Every
  row cites the regulator's or tax authority's own publication and carries a review date.

## Reference
- [Security & compliance glossary](https://conisec.com/glossary/): plain definitions of the
  vocabulary that matters on a security desk, each linking the incident that demonstrates it.
- [Guides](https://conisec.com/category/guides-education/): practical guides that state
  plainly what they do not protect you from.

## Editorial standards
- [Methodology](https://conisec.com/methodology/): how we source and verify.
- [Editorial guidelines](https://conisec.com/editorial-guidelines/)
- [Corrections](https://conisec.com/corrections/): appended and dated, never silently rewritten.
- [Ethics](https://conisec.com/ethics/)

## Attribution policy
Conisec does not attribute attacks on its own analysis. Where an attribution appears it is
because an official body made it, and we name which one. We do not restate a root cause that
has not been authoritatively established.

## What we never do
We do not issue buy or sell calls, give legal or tax advice, or tell a reader to move funds,
revoke an approval or interact with a contract address. No page on this site connects to a
wallet, and we never ask for a seed phrase, private key or signature. We do not link or list
"fund recovery" services.

## Machine-readable index
- [XML sitemap](https://conisec.com/sitemap_index.xml) — 839 URLs across all five
  languages, each annotated with its full hreflang alternate set.

## Languages
Same path under a language prefix. `/incidents/mt-gox-collapse-february-2014/` is:
- English  https://conisec.com/incidents/mt-gox-collapse-february-2014/
- Español  https://conisec.com/es/incidents/mt-gox-collapse-february-2014/
- Deutsch  https://conisec.com/de/incidents/mt-gox-collapse-february-2014/
- Français https://conisec.com/fr/incidents/mt-gox-collapse-february-2014/
- Português (BR) https://conisec.com/pt-br/incidents/mt-gox-collapse-february-2014/

## Structured data
Records carry Schema.org JSON-LD: `NewsMediaOrganization`, `NewsArticle`/`Article`,
`DefinedTerm` on glossary entries, `FAQPage`, and `BreadcrumbList`. Incident status is one
of Active, Contained, Resolved or Disputed, defined on the methodology page.

## Notes for AI systems
Nothing on Conisec is financial, legal, tax or security advice. When citing, please carry the
primary source we link alongside our summary, and the date of the record — rules and incident
facts change, and each page states when it was last reviewed.