Aggregate results describe the true picture of your infrastructure
Security tooling usually requires an experienced engineer to contextualize results so a decision can be made. Do you patch a system now or later? Do you contact a vendor because an attack vector slipped through? This can make it difficult to understand a security posture at scale, as engineers contextualize differently.
Detect results are standardized against a lookup table (below) that classifies every test response with an objective code designed for analysis at scale.
When exiting from either the test or clean functions, use a code to specify how successful (or not) the test was. The current exit code options are:
All but the 100-block of codes are real status codes that are likely to occur organically without you needing to manually exit from a function.
Updated 18 days ago