About Null Sec

We Make Sense of the Noise.

Threat intelligence from various threat sources often has hidden correlating data, which is where the larger picture can get lost. We work on a problem you've probably already encountered: one intrusion, reported by a CERT, a few vendors and an ISAC, each with its own name, partially overlapping IOCs for the actor and its own part of the evidence. We analyze those reports against each other and the broader threat landscape corpus. We build tools for analysts doing the same work. Our first research publication explains a method; our threat research will paint the picture that the data supports.

fig. 1 · lockupx00
Fig. 1The Null Sec logoPlate I
An engraving of a split stone, its two halves side by side, each holding one side of a fossil fern.
Fig. 2Two halves of one split stone. Each holds one side of the same fossil fern.Plate II

One Intrusion, Reported Five Times Under Four Names - and Does It Correlate With Any Others?

Read one at a time, each report looks complete. Read side by side, you might glean additional details despite different names and dates. They could often hold different pieces of the evidence, and it gets hard to tell what is new from what nobody has verified.

We think the useful work is in that comparison: saying what the evidence supports and what it doesn't, and crediting whoever reported it first. That's the research we do. Asterism does the reading and linking at a scale one analyst can't.

fig. 3 · construction0x00
Fig. 3The mark in outline on its 64-unit grid, with two zeros from the site's own monospace face cut out of it.Plate III

The Byte That Ends Every String

A null byte (represented as 0x00 in hex, \0 in code, or all zeros in a single 8-bit character block) is essentially an indicator of absolute nothingness that dictates the boundaries of data. In low-level programming languages like C and C++, it serves as a "string terminator." Computers don't inherently know how long a piece of text is, so they read characters sequentially until they hit a null byte, which tells them: "Stop reading, the text ends here."

Our mark is that byte as this site draws it: the lit 00 from the hex dump on the home page, two zeros cut out of a cell, in the same monospace face. You'll also see the name written x00, the way the byte appears in an escape sequence.

In threat intelligence, it serves as a conceptual pivot point - representing either a cloaking mechanism used by adversaries to blind security tools or a digital fingerprint left behind in malware memory structures.

null secNull Security, LLC
Asterismby Null Sec

Our Service to the Community

The principles are on the home page; this is how the work runs day to day. We believe in strong data integrity principles, and report data as we process it.

  1. 0x01

    Names Stay With Their Vendors

    An actor name in a report carries the vendor that uses it. When two clusters share infrastructure we say they overlap; we don't call them one actor unless the evidence says so. Sources are always cited.

  2. 0x02

    Every Count Has a Window

    A count in a report says when it was taken ("as of 3 Nov"), so a later report can be compared with it. All times are in UTC.

  3. 0x03

    Corrections Carry a Date

    When a report is wrong, we fix it in place and add a dated line saying what changed. Whoever caught it gets the credit, if they want it.

  4. 0x04

    Individually Owned and Operated

    Null Sec is operated by a tiny but dedicated team of individuals who have a strong passion for cyber threat intelligence (CTI).

Things we don't do

  • Name victims beyond what is already public.
  • Show customer logos, badges or quotes we don't have.
  • Sell consulting or incident response.

Work We Build On

Our research and Asterism stand on public data and on other people's reporting. These are the sources we lean on most.

sourcefromwhat we use it for
ATT&CK®The MITRE CorporationThe MITRE CorporationTechnique IDs in our reports and in Asterism
Known Exploited VulnerabilitiesCISACISAWhich vulnerabilities are known to be exploited
EPSSFIRSTFIRSTExploit prediction scores
Traffic Light Protocol 2.0FIRSTFIRSTThe markings we publish and share under
MISP galaxiesMISP ProjectMISP ProjectActor and tool clusters, with their aliases
Reportsvendors, CERTs, researchersvendors, CERTs, researchersThe evidence itself, named in the references of everything we publish
Fig. 4MITRE ATT&CK® is a registered trademark of The MITRE Corporation.Plate V

Writing to Null Sec

The contact page has a form. A person on our team reads the form and both addresses below.

  1. General

    info@null-sec.io

  2. Security

    security@null-sec.io

  3. Asterism

    Request access