Our Cisco ASA logs sometimes contain names that represent objects instead of the IP address.
Dec 18 05:37:49 10.163.19.1 %ASA-6-302013: Built outbound TCP connection 1372634579 for outside:184.108.40.206/443 (220.127.116.11/443) to inside:IND062GFP016/29631 (18.104.22.168/56892)
In this example, you'll see IND062GFP016 instead of an IP address (in this case for a src). I know that we could put in all of our Cisco configs the command "no names" to remove the names. However, when I looked at the CIM, it shows that the src/dest (Network Traffic data model) is a string that can represent an IPv4, IPv6, or a name.
I created new regex statements to pull out the name and alias it to either the src or dest fields. However, now my threatlist reports are not working correctly.
So my questions are:
1. Can we really use names instead of IPs?
2. If we can, then is the other parts like threatlist searches broke?
3. Are my fixes for the props.conf correct or should they be in transforms.conf?
Yes, you can use names, but in order to use threat lists you might have to do a DNS lookup on the particular hostname to get the IP. I don't believe the ASA app accounts for this case.
EXTRACTs are perfectly valid, but since the app already uses transforms I'd advise you to put your regexes in transforms.conf and reference them in props.conf with REPORT-class_name = stanza_name_in_transforms.conf
Sensible stanza names might be cisco_destination_hostname_port, cisco_destination and cisco_source_hostname_port or just use the regexes already in transforms.conf as a base. An easy way to test your regex is through a site like Rubular.com