08-04-2020 09:29 AM
Hi,
We had a external pen test done and we were told that our firewall is leaking internal IP address. (Waiting for the official report)
I started gathering some logs and did find nmap from external to internal host. (Source was public IP and destination was our internal IP)
I am a beginner level and I have checked ASA and I do not find any holes.
Can someone please point me in right direction.
We have one to one static NAT for our public facing services. ASA 5515
Attach is a screenshot from PCAP file.
Thank you,
Brian
08-04-2020 10:04 AM
More than once I have seen external "pen tests" report false positives. If you can share more details we can have a look at it.
08-04-2020 11:04 AM
08-04-2020 11:27 AM
08-04-2020 12:06 PM
I ran the one nmap from a system on public internet targeting our web server public IP and I ran second nmap from a system inside our network targeting our webserver internal IP.
Both the results were same.
PORT STATE SERVICE VERSION
80/tcp open http Microsoft HTTPAPI httpd 2.0 (SSDP/UPnP)
443/tcp open ssl/http Microsoft HTTPAPI httpd 2.0 (SSDP/UPnP)
Service Info: OS: Windows; CPE: cpe:/o:microsoft:windows
08-04-2020 11:05 AM
08-04-2020 10:06 AM
08-04-2020 11:18 PM
I did the NMAP scan from public internet to our public facing server public IP and capture the logs from my ASA.
The logs on ASA showed my laptop public IP as source but showed my public facing server private IP as destination.
That's probably cause of NAT?
Is that a normal for ASA so show private IP of my public server as destination under the logs? Rather than public IP on which NMAP was ran?
My SIEM get's logs from ASA and since ASA has destination IP as private IP, my SIEM alerts me of an External to Internal one on one scan.
Brian.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide