Binary / artifact

Hardening of a shipped artifact (NX / PIE / RELRO / stack canary), dangerous imports and embedded secrets.

Family facts

Code: FAM-BINARY
Status: ready — code maturity
Availability: available — whether it is offerable
Ingest: upload — how a target enters
Rules of Engagement: Not required
Kind: Family (a selectable assessment)

What it decides

Whether a compiled artifact’s hardening posture, imports and embedded contents meet the stated binary invariants.

How it works

It checks a set of binary invariants over ELF/PE artifacts: exploit-mitigation posture (non-executable stack, position independence, full RELRO, stack canaries, control-flow guard), banned or unsafe imported functions, and embedded secret candidates — reasoning about the real exposure of the artifact rather than listing flags.

Capability, disassembly and signature adapters feed the invariants, and diff-aware checks guard against a mitigation regressing or a banned import being newly added.

Declared limits

Note

Severity is advisory; packing detection is architecturally out of scope today; no external held-out validation.

References

References point to public, well-known technical sources for further study.

Source code

ready · available

Design / vibe coding

beta · partial

How the catalog works

Families, states and the honesty guard.