Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

Re^3: Pre-pen testing code review

by sundialsvc4 (Monsignor)
on Apr 18, 2014 at 14:47 UTC ( #1082779=note: print w/ replies, xml ) Need Help??


in reply to Re^2: Pre-pen testing code review
in thread Pre-pen testing code review

No, honestly, I would let the software fail the pen-test if it is going to.   If the pen-tester is competent, this will yield far more results than you ever expected to see, and only then will you be in the proper position to evaluate them all and to create an appropriate remediation plan.

The way that I encourage clients to look at this sort of thing is ... “Look, those defects are out there.   The most important thing is to discover them, not to bemoan the fact that they exist.   In any and in every piece of software, they do exist.”   There is no room for ‘politics’ here, nor for pride.   Discover them, fix them, prove they’re gone and that they stay gone.”

Budget for at least two pen-tests.


Comment on Re^3: Pre-pen testing code review

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1082779]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others browsing the Monastery: (10)
As of 2014-09-16 12:57 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    How do you remember the number of days in each month?











    Results (19 votes), past polls