|
I have always scanned from the outside
in. That is, scan the external network first with a remote penetration
audit, and then scan from inside the network. This would show to your
prospective customer the associated risks from internal and external threats.
I’ve also typically started the external penetration audit without using
any of the data the customer has provided me. I always attempt to find their
IP addresses via information creep. Use email headers and web server IP’s
or domain registrations to attempt to find the IP range. Then use
the IP’s provided to compare what information creep is out there.
This will help you evaluate how difficult it is for an attacker to target the
customer vs. just stumbling onto the vulnerability. The first scan will show you what the
script kiddies would see, the second set of results would should you what an
attacker would see if they are inside the network either through an inside job
or some type of threat such as a Trojan or root kit. Also, as
a result of the two reports, you can compare your data to see what your
firewall/IPS and other security controls are reporting and how well they are
performing. If you throw both results into a report
you can then help your customer with a risk assessment to deem how real an
internal and external threat is. Do they need to spend
the money on implementing new controls to mitigate risks such a Trojans, root
kits and viruses? Do they need an IDS/IPS on internal and external
segments of their networks? Do they need to throw their servers into a DMZ
or secondary network? Do they need a better firewall than a Best regards,
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of -soundlux- I appreciate the feedback so far...
Celebrate Earth Day everyday! Discover 10 things you can do to help
slow climate change. Yahoo!
Earth Day |
_______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
