I've worked in airgapped compliance-driven environments before.
Normally--and this is just being bluntly honest--the 'security'
folks you're dealing with understand compliance and come
from a mindset 'well of course everybody follows the rules'
when attackers quite simply never do and never will; you can't
fight bad guys if you hamstring your defenders by disallowing them
to utilize the same tools and techniques that the bad guys will.
And NO hacks I'm aware of centered on executing ZAP. Generally
speaking, when an organization gets hit, they get hit by phishing,
and if they can drive-by-download random people in your company,
the last thing they're going to care about is "Hey, this machine's
running ZAP! I bet we can use that!" The amount of damage they
can do is far more severe than this.
I'll even offer myself up for a conversation here. I'm the
project co-lead on OWASP's ESAPI-Java-Legacy and have been
bringing tools like ZAP to developers for well over 11 years now,
including DoD customers. As a matter of fact when I was
still "just a developer" you'd never find me without a web proxy
tool in my toolchain because it radically speeds up your ability
to troubleshoot various problems.
--
You received this message because you are subscribed to the Google Groups "OWASP ZAP User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zaproxy-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/zaproxy-users/190e63a6-9210-4680-a982-8d5dd2aaa78an%40googlegroups.com.