TopScan Reviews

Summary: A practical choice if you'd rather not run code checks and perimeter scans with two different vendors. Everything we needed was working within the first week.

Positive: We use both halves. Pull requests on our repos get a security check, dependencies included, and our public apps and servers get scanned every week. Developers see code issues where they already work, and I get the external picture without a second vendor.

Negative: Connecting the repositories took a couple of attempts because of org permissions on our side. Not really the tool's fault, though a clearer note in the docs would have saved time.

Summary: Works well as the external scanning part of our setup. Low maintenance, and the team learned it fast.

Positive: Connecting our AWS account brought in our instances and DNS zones in one go, with the tags we already had. That saved us adding everything by hand, and we could start scanning by environment right away.

Negative: It looks at exposure and vulnerabilities, not cloud configuration. For IAM policies and bucket settings we still use AWS's own tools.

Summary: Reliable way to keep external vulnerabilities from piling up again after you've cleaned them up. Fits the way our DevOps team already works.

Positive: When a fixed issue reappears, after a rollback or an old image getting redeployed, it shows up as a regression instead of a fresh finding. That tells us our process slipped somewhere, so we fix the cause and not only the symptom.

Negative: I'd like a longer-term view of how open issues trend over several months. For quarterly reviews I still put that together myself.

Summary: Topscan is good value for a company our size. I now have a regular, documented check of everything we have facing the internet, and something concrete to show management when they ask.

Positive: I'm an IT manager, not a security person, and I didn't need to become one to use this. I added our domains and public IPs and had the first results the same day. Each finding tells you in plain English what to do next.

Negative: It took me a while to figure out how to group assets so that filters and schedules made sense. Once tags clicked it was fine, it just isn't obvious on day one.

Summary: Good for keeping on top of external vulnerabilities without heaps of admin. A couple of workflow extras and it'd be a five from me.

Positive: You can mark a finding as noise, or snooze it with a reason and an end date, and the history stays attached. Our open list only shows real work, and when someone asks why an issue was parked, the answer is right there with a name next to it.

Negative: I'd like to assign findings to specific people inside the tool. For now ownership lives in our own tickets.