You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit dbf3a0d
Browse filesBrowse the repository at this point in the historyBrowse files
Run the scan engines through a local sign in proxy, on by default
mitmproxy already ships in the dynamic scanning environment. Each scan now
starts a local instance the stock engines run through, with an addon that does
two things to every request they make: it stamps the site's session on it, so
every engine sees what a signed in user sees rather than only the engines that
sign in well on their own, and it refuses any host the scan is not scoped to,
so an engine that follows a link or a redirect off the target cannot reach it.
It is on by default and needs no setup: when mitmproxy is present the scan uses
it, and when it is not the engines go direct exactly as before, so nothing
breaks. testssl always reads the site's own TLS directly, not through the
proxy. A setting on the DAST admin page turns it off.
Verified on a live site: an in scope request is forwarded with the session
added, an out of scope host is refused, and the engines fall back cleanly when
the proxy is not there.
0 commit comments