Book Image

Cybersecurity Attacks – Red Team Strategies

By : Johann Rehberger
Book Image

Cybersecurity Attacks – Red Team Strategies

By: Johann Rehberger

Overview of this book

It's now more important than ever for organizations to be ready to detect and respond to security events and breaches. Preventive measures alone are not enough for dealing with adversaries. A well-rounded prevention, detection, and response program is required. This book will guide you through the stages of building a red team program, including strategies and homefield advantage opportunities to boost security. The book starts by guiding you through establishing, managing, and measuring a red team program, including effective ways for sharing results and findings to raise awareness. Gradually, you'll learn about progressive operations such as cryptocurrency mining, focused privacy testing, targeting telemetry, and even blue team tooling. Later, you'll discover knowledge graphs and how to build them, then become well-versed with basic to advanced techniques related to hunting for credentials, and learn to automate Microsoft Office and browsers to your advantage. Finally, you'll get to grips with protecting assets using decoys, auditing, and alerting with examples for major operating systems. By the end of this book, you'll have learned how to build, manage, and measure a red team program effectively and be well-versed with the fundamental operational techniques required to enhance your existing skills.
Table of Contents (17 chapters)
1
Section 1: Embracing the Red
6
Section 2: Tactics and Techniques

Targeting telemetry collection to manipulate feature development

These days, most software sends data about its usage patterns back to the mothership. This collection can be quite extensive and includes what buttons a user clicks, and of course, what features are used, or not, used by customers. It might also include error messages so that they can learn what features commonly do not work correctly.

Your organization might make business decisions and start future feature development based on the telemetry information they've gathered.

What if an adversary or competitor manipulates the telemetry pipeline to cause de-investments in certain areas of your products or services?

As an example, during a red team operation at one point in my career, the team spoofed the operating system from which telemetry was sent. Instead of sending the Windows or Linux version, the red team sent millions of spoofed requests coming from a Commodore 64 up the telemetry endpoint.

The result...