You can use ranges as Marcabal described above, or you can use variables. If you have IP address ranges that are used across multiple Event Action Filters you can assign them in CSM's "Policy Object Manager" Networks/Hosts (consider this a global variable). If you have the same Event Action Filters on multiple sensors with different IP address ranges, make the above "overwritable" and customize each sensor under CSM's "Device Properties" Networks/Hosts (this would be a similar to a local variable).
We want to use several IPs as in the Marcabal's example but in the CSM appears "Invalid value". We have tried with different separators apart from a comma. It has no sense creating a variable for each filter we use.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...