Picus Security

picus → validate control <id>

Validates a security control with Picus (BAS), executing the control's attack and measuring whether detection or prevention works.

Run it in the purple team lab when you want validation with Picus's BAS platform: the control (the technique with its variations) is validated — the platform executes the control's attack and measures the outcome: prevented (blocked), detected, or uncovered. It's scale validation with the platform: Picus's attack library and the per-control metric. In purple teaming, Picus (and BAS) automate continuous validation: the control is validated, coverage is measured, and gaps are worked — the per-control metric guides detections.

Don't use it without the deployment: Picus needs the agents (sensors) and the subscription — infrastructure and licensing are the requirement. The validation attacks are real: the lab is the place. And note: the platform measures coverage of its library — environment-specific controls are defined separately. The metric (prevented vs. detected) is interpreted with context. For a tight budget, open-source alternatives cover the ground.