Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: rules of engagement scope |
|---|---|
| Date: | Thu, 18 May 2006 20:47:14 -0300 |
Sorry, I still don't understand the point being made. Again, why is it bad to define a scope for the pentest? Michael Sierchio wrote:
Ivan Arce wrote:Frankly I don't see what kind of logical reasoning leads from defining the scope for a penetration test ex-ante to committing fraud, maybe I need some rest to ponder about these things more seriously.In some states in the US there is a cause for civil action known as "fraud by exceeding the scope of consent".
The original author (Mr. Nasty) equated defining the scope of a penetration test to committing (or attempting to commit) fraud on the basis that if you define a precise scope then you are purposely leaving out things that may be important to the general public (I am assuming that he intended to apply that rational to government,public service organization and public companies). So you are talking about a different thing: Fraud (or is it phraud?) committed by the penetration tester because she exceed the scope of what she was allowed to do, whereas Mr. Nasty proposed that having a scope defined by the organization subject to the test is somehow equivalent to fraud (if the results of the test are not made public) I submit that scope definition prior to a penetration test is a good thing because it syncs both the tester and the testee on what is considered important, valid, desired, etc., ant helps to plan resource allocation accordingly and to understand and align expectations. BTW you can still define the scope as: "Anything goes, no restrictions whatsoever" but then you would be letting the penetration tester do whatever she feels like doing and unless both parties have a good and long standing relationship it becomes harder for both to assess the costs and the value of the work.
As an individual consultant in this litigious society, I want more than an affirmative defense, which may bankrupt me even if I am found not at fault.
Ever heard the term "professional liability insurance" ? Sincerely, -ivan --- "Buy the ticket, take the ride" -HST Ivan Arce CTO CORE SECURITY TECHNOLOGIES http://www.coresecurity.com PGP Fingerprint: C7A8 ED85 8D7B 9ADC 6836 B25D 207B E78E 2AD1 F65A ------------------------------------------------------------------------------ This List Sponsored by: Cenzic Concerned about Web Application Security? Why not go with the #1 solution - Cenzic, the only one to win the Analyst's Choice Award from eWeek. As attacks through web applications continue to rise, you need to proactively protect your applications from hackers. Cenzic has the most comprehensive solutions to meet your application security penetration testing and vulnerability management needs. You have an option to go with a managed service (Cenzic ClickToSecure) or an enterprise software (Cenzic Hailstorm). Download FREE whitepaper on how a managed service can help you: http://www.cenzic.com/news_events/wpappsec.php And, now for a limited time we can do a FREE audit for you to confirm your results from other product. Contact us at request@cenzic.com for details. ------------------------------------------------------------------------------
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: rules of engagement scope (DoS testing), Craig Wright |
|---|---|
| Next by Date: | Re: How to pentest Skype?, Chris Eagle |
| Previous by Thread: | Re: rules of engagement scope, Michael Sierchio |
| Next by Thread: | Re: rules of engagement scope, Sol Invictus |
| Indexes: | [Date] [Thread] [Top] [All Lists] |