[OWASP-Bangalore] [null] Re: SourceNAT IP to be in scope for Scanning or not?
N. V. R. K. RAJU
nvrkraju4 at gmail.com
Thu Jul 31 19:29:18 UTC 2014
thank you for the response, so scanning NAT IP from external source doesn't
make a sense. It is good idea to scan only from internal source, correct?
On Mon, Jul 28, 2014 at 9:20 PM, karniv0re <riyazwalikar at gmail.com> wrote:
> If the management IP is covered then you wouldn't normally scan the NAT
> IP. However, you would need to check for the following before you take a
> 1. There may be different set of services that are listening on the
> management and source NAT since you can bind services on different IP
> addresses on the same device.
> 2. Certain VLANs/IP addresses may have access to certain services or to
> the management or source NAT IP.
> Take additional feedback from the community for your query and then you
> may be able to conclusively decide.
> On Monday, 28 July 2014 22:21:13 UTC-4, Raju wrote:
>> Hi All,
>> I am unable to come to a conclusion to say the sourceNAT IP of a firewall
>> should be covered or in-scope for vulnerability scanning.
>> I get to hear from my network team that firewall managment IP is already
>> covered to find issues related to Firewall, having source NAT IP included
>> inscope does not make any sense.
>> I do agree to them for certain extent that scanning source NAT IP from
>> external perspective does not fetch any results or may be I could be wrong?
>> However, I feel there should be a scan performed atleast internally.
>> Kindly, help me clearing my query.
> null - Spreading the right Information
> null Mailing list charter:
> You received this message because you are subscribed to the Google Groups
> "null" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to null-co-in+unsubscribe at googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OWASP-Bangalore