It may seem counterintuitive to pay someone to tell you your shortcomings, but smart companies today are shelling out dollars and resources to do just that, in the form of red teaming.
Red teaming is the practice of testing the security of an organization’s systems by emulating a malicious actor and hacking into secure systems or data. A red team can be an externally contracted group of penetration testers or a team within your own organization, designed to hack your system to prepare for a wide variety of cyberattacks and breach scenarios before they occur. If your organization has outstanding penetration testing tools and endpoint detection processes, for instance, red teams may try phishing or breaching physical access controls during a simulation.
If your company doesn’t currently conduct red teaming exercises, then you might be unaware of potential vulnerabilities in your networks, systems, and data storage ecosystem. Here, we’ll explain the basics of how red teaming works, who are normally involved, and best practices when conducting simulations.
Get the Free Pen Testing Active Directory Environments EBook
Red Teams exists alongside many other teams in the cybersecurity landscape. Blue Teams can work alongside Red Teams but are focused on improving system security from the inside. Purple Teams use a combination of adversarial and defensive approaches. Red Teaming, though, is one of the least understood practices in cybersecurity management, and many organizations are still reluctant to use the practice.
In this guide, we’ll explain exactly what Red Teaming is, and how bringing Red Team practices into your organization can help improve your security. Our goal is to show you how Red Teaming can dramatically improve the security of your IT systems.
What is red teaming?
Red teaming is a multi-layered, full-scope cyberattack simulation designed to test the effectiveness of an organization’s security controls. This includes networks, applications, physical safeguards, and even employees. As stated above, the purpose of conducting red teaming is to allow companies to understand how resistant they are to real-world hacking adversaries.
Your Blue Team will then be tasked with defending the attack as if it was a real one.
Red teaming is similar to ethical hacking, during which actors don’t attempt any actual harm but instead hack into systems to uncover vulnerabilities with the goal of improving defenses. Red teaming is based on the idea that a company can’t really know how secure its systems are until they are attacked. Rather than running the risk of real-world damage that may come from a genuinely malicious attack, simulating one first via red teaming will uncover an organizations’ vulnerabilities so they can be addressed before it’s too late.
How does red teaming work?
The best way to understand the details of red teaming is by looking at the process of how a typical red team exercise unfolds. Most red teaming simulations have several stages:
- Goal-mapping: Organizations will first set primary goals for their red team. For example, one goal may be to extract a particular piece of sensitive data from a particular server.
- Target reconnaissance: Once the red team is clear on their objectives, they will begin mapping out the systems to be targeted, including networks, web applications, employee portals, and even physical spaces.
- Exploit vulnerabilities: This is where the action in red teaming exercises really begins. Once the red team knows which attack vectors they’ll use, they will employ tactics such as phishing or XSS exploits to access your systems.
- Probing and escalation: Your red team will then try to move within your systems to achieve their primary goal, and determine if there are additional vulnerabilities to exploit. Red teams will continually escalate until the target is reached.
- Reporting and analysis: After the red team’s simulated attack is complete, you’ll go through a reporting and analysis process to determine the path forward. You’ll see how your blue (defensive security) team performed and which key vulnerabilities need to be addressed.
Experienced red teams use a wide variety of techniques to perform each of these steps. The main thing to consider when reviewing the attack is that small vulnerabilities in single systems can build into catastrophic failures when chained together. Real-world hackers will always be greedy and look to exploit more systems and data than they originally came for.
Red teaming tools and common tactics
When executed properly, red teaming will result in a mock full-spectrum attack on your networks, systems, and data. Red teams will use as many tools and techniques available to malicious hackers as they can. Some of the more common red teaming tools and tactics are:
- Application penetration testing: App-level pen testing is designed to identify application layer flaws such as cross-site request forgery, injection flaws, and weak session management.
- Network penetration testing: This type of pen test is for identifying network and system-level flaws. This includes misconfigurations, wireless network vulnerabilities, rogue services, and more.
- Physical penetration testing: You also need to understand the strength and effectiveness of physical security controls through real-life exploitation. Red teams may try to stroll past physical controls directly into server rooms or employee work terminals.
- Intercepting communication: To map your network or gain more information about the environment, red teams will circumvent common security techniques by hacking communications such as internal emails, texts, or even phone calls. to.
- Social engineering: Red teams will try to exploit weaknesses in people within your organization by relying on human nature. They’ll try to manipulate employees into giving up access credentials via phishing, phone calls, text messaging, or falsifying an identity on-site.
Red teaming is a full-scope, multi-layered attack simulation designed to measure how well your people, networks, application, and physical security controls can withstand an attack from a real-life adversary. Therefore, a strong red team will employ an array of tools, tactics, and strategies to breach your defenses.
Red teaming benefits
At the broadest level, the value of red teaming is that it provides a comprehensive picture of cybersecurity within your organization. Red teams should be as creative and resourceful as real-life malicious actors who will inevitably probe and test every square inch of the potential attack surface.
The assessment doesn’t conclude after initial vulnerabilities are discovered and exposed, however. The exercise will extend towards re-testing, lateral movement, and remediation phases that will test just about every aspect of your cybersecurity strategy. You’ll be able to completely assess your capability to detect, remediate and prevent targeted attacks.
In fact, the real work typically begins after a red team intrusion, when you’ll perform forensic analysis of the attack and formulate ways to mitigate vulnerabilities. Red teaming also offers several other benefits when used in conjunction with other threat analysis techniques:
- Identification of the risk and susceptibility of attack against key business information assets and technology systems.
- Simulation of techniques, tactics, and procedures (TTPs) used by genuine threat actors in a risk-managed and controlled environment.
- Assessment of your organization’s ability to detect, respond, and prevent sophisticated and targeted threats before they take place.
- Encouragement of close engagement with internal incident response teams to provide meaningful mitigation and comprehensive post-assessment debrief workshops.
- Compliance assistance; strengthen your cyber defense posture to be up to par with relevant frameworks such as CCPA, FISMA, or HIPAA.
- Training and cybersecurity education of your entire staff, from the executive level down to rank-and-file workers.
- Performance-metric gathering with regards to cyber defenses without the downside of a real-life attack. You’ll collect measurements that are relevant to real-world performance.
- Prioritization of cybersecurity initiatives and expenses based on the results of the exercise. Become more cost-efficient and address the most pressing needs first.
These are just a few of the main benefits that red teaming provides. Next, we’ll cover how to decide if your organization needs red teaming and who benefits.
Who needs red teaming?
Just about any company and organization – public or private – can benefit from some form
of red teaming. Even if your company doesn’t work in technology or isn’t necessarily IT-focused, it’s still likely that red teaming will be useful as hackers might be after the personal sensitive information of customers in data stores or internal employees.
For smaller firms, it’s understandably more costly and difficult to deploy the significant resources needed for comprehensive red teaming exercises. In this case, it’s typically worthwhile to contract out the red teaming process, using experienced cybersecurity and compliance partner.
Red teaming considerations
Though almost every company can benefit from red teaming, the best time to undertake this practice –and how frequently to do it – will vary according to your sector and the maturity of your cybersecurity defenses.
Here are some key considerations to make when planning your future red teaming exercises:
- Automation: You should already be engaged in activities such as asset investigation and vulnerability analysis. Your organization should also be combining automated technology with human intelligence by implementing regular, robust penetration testing. Process automation will make it easier to conduct, and measure the results of, red teaming.
- Preparation: Once you’ve completed several business cycles of vulnerability and pen testing, you can start red teaming. Only after you’ve completed these preparations can the total value of red teaming be realized. Attempting to bring in red teaming before establishing a solid and consistent cybersecurity baseline will produce very little value.
- Comparison: To be truly effective, the insights produced by the red team need to be given context by comparing against previous penetration testing and vulnerability assessment activity.
We’ve mentioned penetration testing as both a tactic and key consideration within the realm of red teaming. Therefore, it’s important to understand the differences and similarities between red teaming and pen-testing.
Red teaming vs. penetration testing
Though pen testing is important, it is only one part of what a red team does. Red team operations have broader objectives than pen testers, whose goal is often just to get access to a network.
Red team exercises are designed to emulate a more real-world advanced persistent threat (APT) scenario and result in reviewing defensive strategies and detailed risk analysis. Penetration testing is only a small part of red teaming. Red teaming includes evasion and persistence, privilege escalation, and exfiltration, whereas penetration testing exercises only the first part of the cyber kill chain.
This is the time frame in which each activity is conducted. For pen testing, the time box is extremely narrow – typically less than one day. For red teaming, the time box can be extended over multiple days, weeks, and even months.
Pen testing and red teaming also employ different tools and technologies. Employees will typically conduct a pen test using commercially available software. Red teams are encouraged to use any tool, trick, or tactic in their arsenal and think creatively while attempting to breach systems.
This is one of the most distinct differences between Pen Testing and red teaming. With Pen Testing, most of your employees are aware of what’s taking place. But red teaming exercises require that your organization is completely unaware to get a real picture of your cyber defenses.
Which vulnerabilities are attacked will also differ. In pen testing, known vulnerabilities are specified and targeted to see how well-defended they are. Red teams won't just exploit a single vulnerability, however. They’ll also seek out new ones in your network and attempt to move laterally.
When conducting penetration testing, your test target vulnerabilities will be narrow and pre-defined. You’ll target a specific firewall or password system, for instance. Red team targets are more fluid, ranging across multiple domains and networks.
Penetration testing involves testing each system independently, one at a time, and is a much more siloed approach than red teaming. When implementing red teaming, all your systems are targeted simultaneously throughout the time box, giving you a better idea of your plan of defense and response to a real hack.
Now that you’re informed about what red teaming is (and what it isn’t)it’s time to get up-to-speed on what’s involved in the process and preparation.
What’s involved in a red team exercise?
To get the most out of a red team exercise, you’ll need to make the right preparations. This includes knowing who and what will be involved. The systems and processes used by each organization are different, and a high-quality red team exercise needs to be specifically tailored toward finding vulnerabilities in your systems. For that reason, it’s important to understand several factors.
Know what you’re looking for
First, it’s important to understand which systems and processes you want to test. It’s possible that you know you want web application testing, but you don’t have a sense of what that means for you, and which of your other systems are integrated with your web apps. You need to understand your systems well and patch any obvious vulnerabilities before you start a red team exercise.
Know your network
The better able you are to quantify your testing environment, the more accurate and specific your red teaming exercises will be. Knowing the technical specifications of your network will also make post-analysis more effective and valuable.
Know your budget
Red teaming can be performed at various levels of intensity, and a full spectrum simulated attack on your network can prove costly, as you'll need to include social engineering and physical intrusion for a comprehensive exercise. For this reason, it’s important to understand how much you are willing to spend on your red team exercise and to set your scope accordingly.
Know your risk level
Some organizations tolerate a high level of risk as part of their standard business procedures. Others, and particularly those working in industries in which there are detailed and complex compliance requirements, need to have far lower risk tolerance. When conducting a red team exercise, it’s important to focus on risks that present consequences for your business.
Red teaming examples
A great way to understand the basics of red teaming is to review some examples of how exercises take place and what’s involved. Below are four different red team scenarios that illustrate what you can potentially expect.
Social engineering: After online research of individuals within your organization, the red team then attempts a social engineering attack. Legitimate-seeming emails or social media messages are sent to try and trick employees to give up their access credentials or download malware. If the red team does manage to fool someone, they’ll continue to move about the system undetected indefinitely while testing even more vulnerabilities along the way.
Filtering bypass: The red team will test your web-based vulnerability by attempting to overcome your file filtering system using an SQL injection. During a filtering bypass exercise, red teams will likely exploit any software or safeguards that haven’t been patched because external attacks are easier when the operating systems or programs are outdated. When complete, these scenarios relay exactly how many vulnerable, unpatched programs or operating systems are present in a network.
Physical breach: During the reconnaissance phase, red teams will closely examine and monitor your physical security measures in relation to your IT systems. They’ll see who comes and goes and how they enter. They’ll then attempt to physically enter your server room by using a cloned employee badge or building PIN code acquired via social engineering efforts. And in the case of extremely weak physical access controls, red teams may even be able to walk the premises undetected and unimpeded.
Application exploit: Web applications are often the first thing attackers encounter when looking at a network perimeter, thereby presenting them with the most immediate opportunity of compromise. The red team will attempt to exploit web application vulnerabilities through tactics such as cross-site scripting, SQL injections, and cross-site request forgery. Once the ethical hackers gain control over a single web application, they’ll use it as a springboard for further attack exercise activities.
These are simply a few potential scenarios of how red teaming might look at your organization. You’ll want to work directly with your cybersecurity or red team partner to create and customize exercises and scenarios that best suit your organization.
Red teaming FAQ
Q: What’s the difference between Red and Blue Teaming?
A: Red teaming consists of trying to conduct a cyberattack as a real-life hacker would. Blue Teaming is the other side of the coin, playing defense in real-time against the Red Teams activities. Red Teams can be a mix of your employees and external contractors, while Blue Teams are typically your own personnel.
Q: How long do red teaming exercises take?
A: The overall time depends on the size and complexity of your technology assets and ecosystem. This includes your physical location, the number of staff you have, and the breadth of your technology infrastructure. Most red teaming scenarios take anywhere between two to six weeks to complete.
Q: Is red teaming different from penetration testing?
A: Yes, very different. While penetration testing can be one aspect or tactic involved in a red teaming exercise, it’s not a comprehensive test of your entire cybersecurity posture. The goal of pen testing is to determine if a specific measure or area of your systems can be penetrated within a narrow time frame. Red teaming is a much more thorough and lengthier process and tests multiple entities at once.
Q: Can I perform my own red teaming or do I need a partner?
A: Either option is viable, but which approach you choose depends on factors such as internal expertise, budget, and complexity of systems. For the most comprehensive and effective red team exercises possible, it’s best to enlist the help of a contractor or partner. However, if your internal IT staff has red teaming experience and capabilities, you can certainly conduct scenarios on your own.
One of the biggest mistakes you can make is underestimating hackers’ interest or motivation in accessing your company. They could be after your data or even seek to add you to a botnet group for separate attacks. Red teaming exercises provide a comprehensive look at just about any tactic, vulnerability, or entry point cybercriminals might use to breach your systems for any number of reasons.
Successful red teaming doesn’t happen overnight. You’ll need a good assessment of your current vulnerabilities and whether you’ll need external help conducting exercises. You’ll need to prepare by automating data security processes so that you have the basics covered. Lastly, you will find vulnerabilities you might not otherwise have detected and be able to correct them before experiencing real-world ramifications from an actual attack.
What you should do now
Below are three ways we can help you begin your journey to reducing data risk at your company:
- Schedule a demo session with us, where we can show you around, answer your questions, and help you see if Varonis is right for you.
- Download our free report and learn the risks associated with SaaS data exposure.
- Share this blog post with someone you know who'd enjoy reading it. Share it with them via email, LinkedIn, Reddit, or Facebook.
David is a professional writer and thought leadership consultant for enterprise technology brands, startups and venture capital firms.