Run a multi-step OWASP ZAP scan from one YAML plan

The ZAP Automation Framework drives OWASP ZAP from one declarative YAML plan instead of a fixed scan script. A plan lists jobs in order: import an OpenAPI or GraphQL definition, spider the site, run passive and active scan rules, then write a report. Because the plan is a file, the same scan reproduces exactly and lives in version control next to the code it tests.

The node inputs supply that plan and shape how it runs. The autorun file holds the jobs, openapifile and openapiurl import an API definition, graphqlfile and graphqlurl bring in a GraphQL schema, and config patches a single key=value setting without touching the plan. Silent mode stops unsolicited requests, lowmem backs the scan with a database instead of RAM, and certload adds a Root CA so ZAP can proxy TLS traffic.

On Trickest, zap-automation-framework is a Scanners node that reads a plan plus optional input files and writes a file and a folder of results. Reach for it when one baseline or full scan is too blunt and you need an ordered, repeatable ZAP run wired into a workflow that spiders, scans, and hands findings downstream for triage.