What we do, and how.
Oblisk is a standing record of the open-source intelligence surface: what's exposed, what works, and what just changed. It is not news. News expires. A record compounds: the same fields, logged every day, become a dataset no one else holds.
Every entry is dated, sourced, and structured. Status is earned, not assumed. Nothing is edited after logging, corrections are appended, so the record stays honest about what was known, and when.
We log breaches as intelligence: sector, scale, exposure type, vector. We never host, mirror, or link the exposed data itself. The posture is passive and the framing is defensive: understanding how the surface fails is how you defend against it.
Behind the record is a working Discord community where the day's entries get argued over and a weekly challenge runs. The record is open to all. The wire is on the other side of a door.
How the record holds up.
Entries cite a source and carry a status. Verified means corroborated against a primary or a sample. Unconfirmed means reported but not yet stood up. We would rather log an honest Unconfirmed than a confident error.
Verified · Unconfirmed · Updated · Degraded · Dead · Opening · Closing · Documented. Each means one specific thing; see the tag on any entry.
No exposed records are hosted, mirrored, or linked. Breach entries are metadata and analysis only. Case files describe method and outcome, not private data.
Passive collection, defensive framing. The record exists to help practitioners understand and defend the surface.
The record is not rewritten. Corrections and updates are appended and dated.
OBLISK