I brought this up in an older thread but noticed it that it still occurs in the 3.1 beta release. Can this please be resolved?
When importing from Cisco ASA, security rules that specifically allow all TCP ports (but not UDP ports) - i.e. "access-list NET1 extended permit tcp host 10.10.10.1 any" - will be imported as rules that allow all TCP and UDP ports.
The same applies to ASA rules that only permit all UDP ports (but not TCP ports). The rule will be imported into the tool as a rule that allows all UDP and all TCP ports.
I can confirm that this occurs with ASA code 8.2. I don't know for sure about 8.3+.
A suggested fix would be:
- Auto-create a Service object that contains the entire tcp/udp port range.
- Use that Service object in the imported rule
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!
The Live Community thanks you for your participation!