BackTrack 4: Assuring Security by Penetration Testing

BackTrack 4: Assuring Security by Penetration Testing

Book rating: 05 Paperback

By (author) Shakeel Ali, By (author) Tedi Heriyanto

$49.53

Free delivery worldwide
Available
Dispatched in 4 business days
When will my order arrive?

  • Publisher: Packt Publishing Limited
  • Format: Paperback | 371 pages
  • Dimensions: 208mm x 272mm x 28mm | 1,061g
  • Publication date: 19 April 2011
  • Publication City/Country: Birmingham
  • ISBN 10: 1849513945
  • ISBN 13: 9781849513944
  • Illustrations note: black & white illustrations
  • Sales rank: 329,803

Other people who viewed this bought:

Showing items 1 to 10 of 10

Other books in this category

Showing items 1 to 11 of 11
Categories:

Customer reviews

By Dainius Valatka 15 May 2011 5

This review is from: BackTrack 4: Assuring Security by Penetration Testing (Paperback)
The authors tackle a persistent danger to many websites and networks that hang off the Internet, where often the complexity of the operating systems and applications and the interactions between these can open doors to attackers. So the basic idea of penetration testing is to preemptively probe ('attack') your system. Find the weaknesses first, before others do so.

In part, the text offers a good overview of the field, separate from the usages of BackTrack. So you get a summary of several common security testing methodologies. Including the Open Source Security Testing Methodology Manual. If you have a background in science experiments, you'll see clear parallels in how this OSSTMM approach investigates an unknown system.

As far as BackTrack is concerned, its capabilities are explored in depth through most of the text. It does seem to have covered all the bases. Like checking/scanning for open TCP and UDP ports on target machines. Or looking for live machines on a network. One thing that becomes clear is that you can treat BackTrack as a repertoire of free tools. And you can pick just a subset of these tools to initially use against your network, if you have specific needs or suspicions,

To be sure, the recommended usage is a top down one, where you treat BackTrack as an integrated whole and you systematically first plan out your entire testing. No argument from me. You should do this, if you decide to use BackTrack in the first place. But a pragmatic incremental approach might still have some nuopelnas. Where you can just choose a tool and look up its usage in the text and run it. Easy to get some experience and confidence.