When I look at my IDS logs in IEV, all of my out/in traffic uses my NAT adddress as the local address. Is there a way to configure it differently so I can see the actual internal IP? Because it doesn't do me much good to see that my NAT'd address was a victim of the BLASTER worm.
The sensor reports the IP in the packets that it saw.
So this is a result of where you have the sensor deployed.
It sounds like your sensor is monitoring on internet side of your fireall so it is seeing packets with the NAT address. So the alarms will all report the NAT address. The sensor nor IEV will do any reverse translation to figure out the actual address because this would require constant polling of the firewall for it's translation tables.
If you move the sniffing interface of your sensor to the Inside of your firewall then the packets will have the actual internal ip addresses and not the NAT address.
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...