G2

Nikitas K.

Network Consultant

Small-Business (50 or fewer emp.)

7/29/2026

"Rule Analysis and App Mapping That Make Firewall Migrations Faster"

4.5/5

What do you like best about AlgoSec Horizon?

Doing ASA-to-FTD and Palo Alto migrations for a living, the thing that sold me on Horizon was AFA's rule analysis before you even touch a device. You get told which rules are actually being hit, which ones are dead weight, and which ones are a liability, with the traffic history to back it up. On a migration with hundreds of legacy ASA rules, that alone saves days of manual comparison.

FireFlow is where the change management side clicks. Every request has a state, an owner, and a paper trail, so nobody's asking "wait, who approved this NAT rule" three months later.

AppViz is the one that changes how you talk to other teams. Instead of a spreadsheet of IPs and ports, you can show someone the actual application flow and point at exactly which policy is blocking it. Cuts the back and forth with dev teams down to nothing.

A few other things that stood out:

Clean UI - doesn't bury you in menus, you can get to compliance status or a specific rule fast.

Change automation - pushing a firewall or cloud security group change through FireFlow instead of doing it by hand cuts down on the "wrong object-group" mistakes.

Compliance reports - PCI-DSS and similar are basically ready to export, which matters during audit season.

Handles scale - ran it against a fairly large hybrid estate and it didn't choke.

Don't treat it as just a firewall dashboard. The application mapping is genuinely useful when you need to explain a security decision to someone who doesn't care about ports and protocols. Review collected by and hosted on G2.com.

What do you dislike about AlgoSec Horizon?

The onboarding phase takes real effort. It's not really a Horizon problem, it's that the tool surfaces every undocumented device and forgotten segment in your network, so if your topology docs are stale, you'll spend the first few weeks fixing collectors instead of doing the fun stuff.

The custom reporting side could use work too. The out-of-the-box compliance templates are fine, but building something custom branded for an exec presentation takes longer than it should. A proper drag-and-drop report builder would help. Review collected by and hosted on G2.com.

What problems is AlgoSec Horizon solving and how is that benefiting you?

The biggest one is visibility across a hybrid estate that used to live in three different heads at once, ours, the client's, and whoever built the original ASA rulebase five years ago. Horizon pulls all of that into one place, so when a migration starts, we're not spending the first two weeks just figuring out what's actually running.

It's also cut down the back and forth with app owners a lot. Before, a "why is my app broken" ticket meant pulling logs from three devices and guessing. Now we can point at the AppViz map and say exactly which rule or path is the problem, so tickets close in minutes instead of days.

On the compliance side, it's saved a ton of manual prep before audits. Reports that used to take a day to assemble by hand now export in a few clicks.

Integration wise, it plays well with the Cisco ASA/FTD and Palo Alto stacks we deal with most, and the API access has made it straightforward to pull data into our own tracking without living inside the Horizon UI all day.

On pricing, it's not cheap, and licensing scales with the number of devices, so for a smaller shop it can be a hard sell up front. For anything running a genuinely hybrid, multi vendor estate though, the time saved on rule cleanup and audit prep tends to justify it within a few migrations. Review collected by and hosted on G2.com.