Sarge, the CodeMarine mascot

Field Manual

Security in plain English

Listen up. Security news is written in code words. This manual decodes them.

Life of a bug

How a flaw travels from discovery to your patch queue.

  1. 1. Flaw found

    Someone spots a security flaw in a product.

  2. 2. CVE assigned

    A CVE Numbering Authority gives it an ID, so everyone means the same bug.

  3. 3. Advisory

    The official notice: what is broken and which versions are hit.

  4. 4. Patch

    The update that repairs the flaw. Attackers read advisories too.

  5. 5. Exploited, added to CISA KEV

    Attackers hit real targets. With reliable evidence and a clear fix, it goes on the list.

  6. 6. You patch

    Move to the fixed version, then check for signs of compromise.

Real bugs do not always march in this order. A zero-day is attacked before any fix exists, and plenty of bugs never reach step 5.

CVSS severity scale

What the numbers mean. It rates how bad a flaw is, not how likely it is to hit you.

None
0.0
Low
0.1 to 3.9
Medium
4.0 to 6.9
High
7.0 to 8.9
Critical
9.0 to 10.0
Ranges from the FIRST CVSS v4.0 specification.

Agents and scripts can read /learn.md, /learn.json or /llms-full.txt.