Skip to content
Notifications
Clear all

Switched from Firepower back to a classic ASA with FirePOWER module.

1 Posts
1 Users
0 Reactions
1 Views
(@cloud_ops_learner_99)
Estimable Member
Joined: 1 month ago
Posts: 137
Topic starter   [#13488]

Just wanted to share my experience. I was managing a new Cisco Firepower Threat Defense (FTD) deployment for a few months and... honestly, it overwhelmed me. The interface felt heavy, and troubleshooting was confusing for someone still learning.

I switched back to a classic ASA with the FirePOWER module. Having the ASA handle the firewall policies and VPN, while the module just does IPS/IDS, feels much clearer. It's like separating my infrastructure concerns.

For example, my basic ASA config is straightforward and I can version control it:

```
object-group network AWS-SERVERS
network-object 10.10.1.0 255.255.255.0
access-list OUTSIDE-IN extended permit tcp any object-group AWS-SERVERS eq 443
access-group OUTSIDE-IN in interface outside
```

I feel more in control. Did anyone else make this switch? How do you handle the security policy split between ASA and the module? I'm worried about missing something 😅



   
Quote