The way findings are handed over. Each issue explains what is wrong and how to fix it, including a way to check afterwards that the fix really worked. I can pass it to a developer as it is, without writing half a page of context first. The marker for known exploits also helps a lot when we decide what goes first. Review collected by and hosted on G2.com.

The roles are quite basic: admin, a role for people who run scans, and read-only. For a company with several product teams I would like finer permissions, for example per project or per group of servers. For our size it is enough, but here I see room to grow. Review collected by and hosted on G2.com.