Crystal Box Testing<\/b>: the team is provided all the information they request before and during testing. They are provided a liaison to help provide additional information about the environment as the team’s actions move them through the clients resources.<\/li>\n<\/ul>\nEach of these different testing methods has its weaknesses and advantages. For Black Box testing, the weaknesses are that many vulnerabilities (potentially critical) may be missed. However, when the penetration testers do compromise something, there is no denying the fact that malicious attackers could have accomplished the same thing. Gray Box testing reduces both of these cases. A few vulnerabilities may still be missed during the assessment. Additionally, some people and managers will argue that the reason the testing was successful is directly associated with the inside knowledge provided to the testing team and that attackers would not have been able to accomplish the same thing. White Box testing is performed with the expectation that most of the critical vulnerabilities will be identified during the assessment. However, some people will argue that the penetration team was basically operating as an administrator within the environment since they had access to the resources or data and certain findings are not vulnerabilities.<\/p>\n
To conclude, Wendy stated, “If you\u2019re serious about security, you can\u2019t assume any part of your infrastructure is \u2018safe\u2019 or \u2018out of scope.\u2019 Because to the attacker, it isn\u2019t.” She is absolutely correct. Attackers are never limited by where they go within an organization and what they are permitted to do. Penetration testers will ALWAYS be limited, and rightfully so. However, an organization can use this to their advantage. If you have a list of resources, services, or data that is off limits, you really need to identify “why.” If you can fix that limitation then you very well may have addressed a critical security situation. Critical resources should be robust and resistant to failure and attack.<\/p>\n
I hope this helps.<\/p>\n
Go forth and do good things.<\/p>\n","protected":false},"excerpt":{"rendered":"
Original Post Author: Don C. Weber [Twitter: @cutaway] Original Date Published: 28 March 2013 John Sawyer pointed me to a blog post Getting the most out of your pentesting by Wendy Nather of 451 Security. I would like to provide a little bit more context in the hopes that it will help CIO’s, managers, administrators, […]<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"categories":[67],"tags":[19,21,20,17,18],"_links":{"self":[{"href":"https:\/\/zed.inguardians.com\/wp-json\/wp\/v2\/posts\/366"}],"collection":[{"href":"https:\/\/zed.inguardians.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/zed.inguardians.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/zed.inguardians.com\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/zed.inguardians.com\/wp-json\/wp\/v2\/comments?post=366"}],"version-history":[{"count":1,"href":"https:\/\/zed.inguardians.com\/wp-json\/wp\/v2\/posts\/366\/revisions"}],"predecessor-version":[{"id":458,"href":"https:\/\/zed.inguardians.com\/wp-json\/wp\/v2\/posts\/366\/revisions\/458"}],"wp:attachment":[{"href":"https:\/\/zed.inguardians.com\/wp-json\/wp\/v2\/media?parent=366"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/zed.inguardians.com\/wp-json\/wp\/v2\/categories?post=366"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/zed.inguardians.com\/wp-json\/wp\/v2\/tags?post=366"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}