report. A Red Team that tells the story of an engagement with simple facts can convey a strong message without blame. Even if an organization did poorly, the facts would be more than enough to get the point across.
Remember, a Red Team's job is not to demonstrate how elite their hacking skills are but to exercise a threat scenario that allows an organization to learn and improve their security. A
Red Team's story should convey the significant failures that led to a successful compromise.
A good rule of practice is non-attribution, or not attributing failures to specific people. Many organizations blame security failures on certain individuals instead of recognizing organizational gaps or failures. Placing blame on individuals seems to present an easy fix but rarely improves security.
Blaming Bob in accounting for clicking a phishing email is not why all intellectual property was stolen.
On
occasion, a Red Team maybe presented with an unusually hostile person or possibly a hostile technical team. In these scenarios, diffusing hostilities becomes just as important as the information
being conveyed otherwise, the information may not be ingested as intended. The Red Team can use three simple questions to begin diffusing the situation.
Share with your friends: