Upgrade to Pro — share decks privately, control downloads, hide ads and more …

The Red Teamer's Guide To Building A Program

The Red Teamer's Guide To Building A Program

HOU.SEC.CON 2022 (Oct/22)

Organizations continue to build internal red teams and penetration testing programs to keep up with the latest threats. The challenge, however, becomes apparent in the first few months of deploying the program: executives want to know if it is cost-effective, the integration with other teams quickly becomes a nightmare, and talent acquisition and retention can be demanding.

We also want our red team to push boundaries and help improve the company’s security posture and ability to survive actual attacks.

So how can we build and deploy red team programs that are meaningful to the enterprise and go beyond frameworks and continuous testing? This talk tackles the problem by:

- Outlining challenges, positive results, and setbacks resulting from building an internal red team program;
- Proposing approaches to select targets for testing and improving the communication between different teams consuming the testing results;
- Discussing the definition of metrics to help track the program, identify improvement opportunities, and demonstrate effectiveness.

HOU.SEC.CON 2022 - https://web.cvent.com/event/0ac8a54d-fbe9-4a16-8510-49dcf538389f/websitePage:dd3dff4f-9597-4a4b-960e-eb732a9a3853

Daniel Marques

October 20, 2022
Tweet

More Decks by Daniel Marques

Other Decks in Technology

Transcript

  1. Disclaimer: The views and opinions expressed in this talk are

    my own and do not necessarily represent those of my employer. These slides are for educational purpose only and are not to be relied upon as professional advice.
  2. Penetration Testing vs. Breach & Attack Simulation vs. Red Teaming?

    They all have different goals and serve different purposes. Coverage and exploitability Automation and scalability Improve detection and response
  3. THE RED TEAM GOAL IS TO HELP IMPROVE RESILIENCE Challenging

    Assumptions Demonstrating Impact Emulating Adversaries
  4. DO YOU NEED A. RED TEAM PROGRAM? Which bears the

    question, Structured red team operations Tailored to organization needs Improve support for teams Demonstrate value Maybe.
  5. THERE ARE CHALLENGES, SPECIALLY INTEGRATING WITH OTHER FUNCTIONS Misalignment with

    business objectives Define reasonable metrics Communicating objectives and results
  6. Why How What Simon Sinek’s Golden Circle Define the mission,

    vision, and goals focused on your business. “Start with the why”
  7. Think in terms of initiatives the red team can support.

    START SMALL BUT PLAN FOR THE FUTURE
  8. Relationships matter. Remember: It is not about us. It is

    about them. https://danielmiessler.com/study/red-blue-purple-teams/
  9. Are you testing what matters? TALK TO YOUR RISK MANAGEMENT

    TEAM. They might point out to a Business Impact Analysis, critical business processes, and key stakeholders.
  10. we need a taxonomy. To improve communication https://attack.mitre.org/ Contextualize vulnerabilities

    Blue team: Map threat behavior to attack path Structured profile-based operations
  11. When communicating results up ALIGN FIRST WITH OTHER TEAMS Show

    improvements for detection and response Prepare a remediation plan Tell a story that makes sense and demonstrates impact
  12. answer questions Metrics should What has the team achieved? What

    positive impact is the red team creating? Are we helping other teams to advance?
  13. .Program metrics. vs .Campaign metrics. Is the program advancing? What

    was the operation’s outcome? Operations Planned x Performed Mean time to initial access Time to initial access Time to detection Time to recover Attack Path Initial Detection Mean time to detect Based on the works of Jordan Potti, Cedric Owens, and Daniel Marques Attack Path Stage Reached Mean time to recover Critical processes covered
  14. Key. Takeaways Communication is essential Be flexible and support other

    cybersecurity teams Standardize early and review often Adopt reasonable metrics
  15. Thank you to the folks that collaborated with this work

    Alex Andrucioli David Trollman Hao Wang Josh Theimer Keith Mularski Marcos Matos Mehul Purohit Mike Fotso Paul Hissem Pipe Rodanant Romulo Rocha Victoria Dea Vitor Mendes Yuri Melo
  16. Images • https://www.pexels.com/photo/hands-typing-on-a-laptop-keyboard-5483077/ • https://www.pexels.com/photo/top-view-photo-of-people-near-wooden-table-3183150/ • https://www.pexels.com/photo/person-rock-climbing-3077882/ • https://www.pexels.com/photo/words-in-dictionary-4440720/ •

    https://www.pexels.com/photo/road-landscape-mountains-nature-63324/ • https://www.pexels.com/photo/marketing-businessman-person-hands-6801647/ • https://www.pexels.com/photo/start-written-on-asphalt-2646531/ • https://www.pexels.com/photo/three-woman-talking-near-white-wooden-table-inside- room-1181619/ • https://www.pexels.com/photo/red-hoodie-3054218/ • https://www.pexels.com/photo/black-and-white-browsing-business-coffee-265152/