USENIX Security Writing Style

A USENIX Security paper argues like an engineer under oath: state what the adversary can do, show what you built or broke, measure it honestly, and say plainly what does not follow. The style advice here is calibrated to the '26 CFP's format rules and to the venue's reviewing culture; format numbers are one cycle's snapshot.

Structure: the threat model is load-bearing

Readers at this venue locate every claim relative to an adversary. Put the threat model early (typically Section 2 or 3), make it precise, and never let the evaluation quietly assume a stronger or weaker attacker than the model granted: