04 — testing & measurement

Tune/test split

Dividing a corpus once into a half the tuning work may see and a locked half it may not. Doing it stratified — so both halves carry the same mix of attack families and transformation axes — matters as much as doing it at all, since an unstratified random split can hand one half every homoglyph sample and make the result meaningless. The gap between the two halves' scores is the honest measure of how much of the performance is memorisation.

Related terms

  • Held-out set Testing & measurement

    Test samples deliberately kept away from whoever is building the detection, so the score answers "does this generalise?" rather than "does this…

  • Overfitting Testing & measurement

    Fitting the examples instead of the phenomenon. In detection work it usually looks like a rule matched to the exact phrasings in the corpus — a pattern…

Testing & measurement

The words that decide whether a published detection number is evidence or decoration. Most vendor numbers in this space are quoted without any of them; see how we test for how these are applied in practice.

Tune/test split is term 2 of 15 in this part of the glossary.

Get started free Full glossary → How we test → Community agent on GitHub ↗

This page is one entry from the agentic AI security glossary, which defines 60 terms in the same style. Where a term belongs to a published taxonomy or standard — the HackAgent attack families, the OWASP lists, AMTSO's guidelines, MITRE ATLAS, ISO/IEC 42001, the NIST AI RMF, the EU AI Act — the authoritative wording is the source document's, not ours, and specifics should be verified there. "Lethal trifecta" is Simon Willison's term. OWASP® is a trademark of the OWASP Foundation; ATT&CK® and ATLAS™ are trademarks of The MITRE Corporation. Naming a framework here is description, not a claim of certification or endorsement.

glick.run — AGPL-3.0