Firebind Recon Provides "Table Stakes" Security Policy Validation
Perimeter defense or zero-trust? On-prem, cloud, or hybrid? VPN directly to the office or connect through a CASB (cloud access security broker)?
Long gone are the days of an on-prem firewall being the only policy enforcement engine focused on keeping your network secure. Firewalls, IPS and IDS, DLP and other network security devices or software instances are all enforcing more security policies than ever before. And while testing those policy enforcement engines has always been a “table stakes” activity, especially after changes are made, that testing has always been one of the most difficult auditing tasks to complete, frequently leading to rule modification validation being done poorly if at all. The migration of critical workloads to the cloud has further compounded the problem due to the introduction of new, unfamiliar configuration interfaces that can operate in a very different manner due to their virtual nature.
There have been many approaches to network security policy testing over the years, whether it be open source tools like netcat and ncat or more advanced approaches that wrapped those tools inside some python scripting. However, what always remained the same was the need to set up a “listener” or “target” host along with running a sequence of command line instructions, all to receive results that weren’t always definitive.
Enter Firebind Recon, a BAS (breach and attack simulation tool) that deploys agents that focus exclusively on enumerating network security controls by putting real payloads “on the wire” to see how the network reacts.