transferring alert filters between zap instances

[g]

I am running scans with ZAP 2.8.0 on my local machine. I would like to create a set of alert filters locally and then transfer the alert filters to a zap instance running in the cloud.

I am trying to do this with global alert filters, but I am willing to use context level filters if that is easier.

How do you transfer global filters from one zap instance to another?

Additional info:

I started importing/exporting my contexts, but I always create a new session when I run a new scan.

I discovered today that filters are stored in zap's internal database. Is it possible to use a sql script to populate the alerts table with filters, or what is the best practice?

Thanks

[Simon Bennetts]

Global alert filters are actually stored in the standard ZAP config file.

This FAQ explains how you can work out what keys you need to use for any config element: https://github.com/zaproxy/zaproxy/wiki/FAQconfigValues

You can put the config values for all of the global alert filters in one file, copy them to the relevant instances and then start ZAP with those values via the '-configfile' parameter.

[g]

Thanks for getting back to me Simon.

I'm trying to load alert filters via a config file, but I don't see them in the UI under Tools/Options/Global Alert Filters.

Yet when I look at zap.log it looks like they are loading.

I've attached my config with the alert filters and an excerpt from zap.log

I'm using zap 2.8.0 on MacOS.

This is the command I'm using to start zap:

/Applications/OWASP\ ZAP.app/Contents/MacOS/OWASP\ ZAP.sh -configfile ~/zap_config

[g]

Please disregard my previous post. I just realized I had typos in my config.

Alert filters are loading after the typos were fixed.

[Simon Bennetts]

No problem - thanks for letting us know :)