purple team cover Giacomo Lanzi

Red Team, Blue Team and Purple Team: what are the differences?

Estimated reading time: 6 minutes

When we talk about cybersecurity and find ourselves on the side of the attacked, we often limit ourselves to thinking in terms of defense, protection and containment of threats. However, the approach that works best is one in which you put yourself in the attacker’s shoes and treat your infrastructure as the target of their actions. Only in this way is it possible to address the discussion holistically and not from a single point of view. To execute this change of mentality, we refer to the various actors in the scene as teams: red team, blue team and purple team. Today we shed some light on the differences between the hacker teams involved in the action.

Definition of Teams and their purpose

The Red Teams are internal or external entities dedicated to testing the effectiveness of a security program emulating the tools and techniques of likely attackers as realistically as possible. The practice is similar to, but not identical to Penetration Testing, and involves the pursuit of one or more goals, usually performed as a campaign.

The Blue Team they refer to Internal security team that defends against both real attackers and Red Teams. Blue Teams must be distinguished from standard security teams in most organizations, as most security operations teams do not have a mindset of constant vigilance against attacks, which is the mission and outlook of a true Blue Team.

The best Blue Team members are those who can employ adversarial empathy techniques, that is, think deeply like the enemy. This mentality is usually dictated more than anything else by attacking experience.

This mentality is usually dictated more than anything else by attacking experience. They do this by integrating the defensive tactics and controls of the Blue Team with the threats and vulnerabilities found by the Red Team in a single action that maximizes both. Ideally, the Purple Team shouldn’t be a team, but rather a permanent dynamic between Red and Blue.

Purple Team Multiscreen

To further delve into the points of view, let’s take a closer look at the teams.

Red Team

Red Teams are often confused with Penetration Testers, but while they have a huge overlap in skills and functions, they are not the same thing. They have a number of attributes that separate them from other offensive security teams. The most important of these are:

1. Emulazione delle TTP(tecniche, tattiche e procedure)utilizzate dagli avversari. They use tools similar to bad actors: exploits, pivot methodologies and typical objectives of a black hat hacker.
2. Campaign-based testing that extends over an extended period of time, for example, multiple weeks or months of emulating the same attacker.

Penetration testing is when a security team uses standard tools, runs tests for only a week or two, and tries to achieve a standard set of objectives. For example, breaking into the internal network, stealing data or obtaining domain administration. A Red Team campaign uses a customized set of TTPs and objectives over an extended period of time.

Of course, you can create a Red Team campaign that uses the best known TTPs, a combination of ongoing pentesting tools, techniques and objectives, and run it as a campaign.

Blue Team

The goal here is not to protect entry, but rather to encourage curiosity and a proactive mindset. Blue Teams are a company’s proactive defenders from a cybersecurity perspective.

There are a number of defense-oriented tasks that are not considered worthy of the Blue Team. For example, a Level 1 SOC analyst who has no training or interest in offensive techniques, no curiosity about the interface he is looking at, and no creativity in following up on any potential alerts is unlikely to be a valuable member of a Blue Team.

All Blue Teams are defenders, but not all defenders are part of a Blue Team.

What constitutes a Blue Team member and differentiates it from dealing with defense is the mentality. Here’s how to make the distinction: Blue Teams have and use:

1. A proactive, non-reactive mindset
2. Deep curiosity about things that are out of the ordinary
3. Continuous improvement in detection and response

It’s not about whether someone is a self-taught Level 1 SOC analyst or a former Red Team member. It’s about curiosity and the desire to constantly improve.

Purple Team

The Purple Team is more of a cooperative mindset between attackers and defenders working on the same side. As such, it should be thought of as a function rather than a separate team.

The true purpose of a Red Team is to find ways to improve the Blue Team, so Purple Teams should not be necessary in organizations where Red Team/Blue Team interaction is healthy and functioning properly.

The best uses of the term Purple Team are when a group unfamiliar with offensive techniques wants to learn how attackers think. It could be an incident response group, a detection group, a developer group, anything. If the good guys are trying to learn from white hat hackers, this can be considered a Purple Team exercise.

Purple Team Collaboration

Conclusions

While Red and Blue Teams have the same goal of improving an organization’s security, they are too often unwilling to share their “secrets.” Attackers sometimes don’t reveal the methods they used to infiltrate systems, while defense teams don’t say how attacks were detected and blocked.

However, sharing these “secrets” is critical to strengthening the company’s security posture. The value of the red and blue teams is null if they do not share their research and reporting data. This is where the Purple Team comes in.

Purple Team members get their Red and Blue teammates to work together and share insights into their assets, relationships and knowledge. To do this, you should focus on promoting communication and collaboration between members of the two core teams.

How to use these mentalities in the company

When you outsource enterprise security with SOCaaS and the execution of Vulnerability Assessments and Penetration Tests, the various teams are completely external. The services offered by SOD are based on best practices regarding the work of Red and Blue Teams, generating a Purple Team mentality.

With us the security of your company is in good hands. Our engineers have experience and are used to collaborating to achieve maximum results.

Contact us to find out more about how our services can help in corporate defense, we will be happy to answer any questions.

Useful links:

Share


RSS

More Articles…

Categories …

Tags

RSS darkreading

RSS Full Disclosure

  • CVE-2024-31705 April 14, 2024
    Posted by V3locidad on Apr 14CVE ID: CVE-2024-31705 Title : RCE to Shell Commands" Plugin / GLPI Shell Command Management Interface Affected Product : GLPI - 10.X.X and last version Description: An issue in Infotel Conseil GLPI v.10.X.X and after allows a remote attacker to execute arbitrary code via the insufficient validation of user-supplied input. […]
  • SEC Consult SA-20240411-0 :: Database Passwords in Server Response in Amazon AWS Glue April 14, 2024
    Posted by SEC Consult Vulnerability Lab via Fulldisclosure on Apr 14SEC Consult Vulnerability Lab Security Advisory < 20240411-0 > ======================================================================= title: Database Passwords in Server Response product: Amazon AWS Glue vulnerable version: until 2024-02-23 fixed version: as of 2024-02-23 CVE number: - impact: medium homepage: https://aws.amazon.com/glue/ found:...
  • [KIS-2024-03] Invision Community <= 4.7.16 (toolbar.php) Remote Code Execution Vulnerability April 11, 2024
    Posted by Egidio Romano on Apr 10------------------------------------------------------------------------------ Invision Community
  • [KIS-2024-02] Invision Community <= 4.7.15 (store.php) SQL Injection Vulnerability April 11, 2024
    Posted by Egidio Romano on Apr 10-------------------------------------------------------------------- Invision Community
  • Multiple Issues in concretecmsv9.2.7 April 11, 2024
    Posted by Andrey Stoykov on Apr 10# Exploit Title: Multiple Web Flaws in concretecmsv9.2.7 # Date: 4/2024 # Exploit Author: Andrey Stoykov # Version: 9.2.7 # Tested on: Ubuntu 22.04 # Blog: http://msecureltd.blogspot.com Verbose Error Message - Stack Trace: 1. Directly browse to edit profile page 2. Error should come up with verbose stack trace […]
  • OXAS-ADV-2024-0001: OX App Suite Security Advisory April 11, 2024
    Posted by Martin Heiland via Fulldisclosure on Apr 10Dear subscribers, We&apos;re sharing our latest advisory with you and like to thank everyone who contributed in finding and solving those vulnerabilities. Feel free to join our bug bounty programs for OX App Suite, Dovecot and PowerDNS at YesWeHack. This advisory has also been published at https://documentation.open-xchange.com/appsuite/security/advisories/html/2024/oxas-adv-2024-0001.html. […]
  • Trojan.Win32.Razy.abc / Insecure Permissions (In memory IPC) April 11, 2024
    Posted by malvuln on Apr 10Discovery / credits: Malvuln (John Page aka hyp3rlinx) (c) 2024 Original source: https://malvuln.com/advisory/0eb4a9089d3f7cf431d6547db3b9484d.txt Contact: malvuln13 () gmail com Media: twitter.com/malvuln Threat: Trojan.Win32.Razy.abc Vulnerability: Insecure Permissions (In memory IPC) Family: Razy Type: PE32 MD5: 0eb4a9089d3f7cf431d6547db3b9484d SHA256: 3d82fee314e7febb8307ccf8a7396b6dd53c7d979a74aa56f3c4a6d0702fd098 Vuln ID: MVID-2024-0678...
  • CVE-2023-27195: Broken Access Control - Registration Code in TM4Web v22.2.0 April 11, 2024
    Posted by Clément Cruchet on Apr 10CVE ID: CVE-2023-27195 Description: An access control issue in Trimble TM4Web v22.2.0 allows unauthenticated attackers to access a specific crafted URL path to retrieve the last registration access code and use this access code to register a valid account. If the access code was used to create an Administrator […]
  • [CFP] IEEE CSR Workshop on Cyber Forensics& Advanced Threat Investigations in Emerging Technologies 2024 April 5, 2024
    Posted by Andrew Zayine on Apr 05Dear Colleagues, IEEE CSR Workshop on Cyber Forensics and Advanced Threat Investigations in Emerging Technologies organizing committee is inviting you to submit your research papers. The workshop will be held in Hybrid mode. The in-person mode will held at Hilton London Tower Bridge, London from 2 to 4 September […]
  • Backdoor.Win32.Agent.ju (PSYRAT) / Authentication Bypass RCE April 5, 2024
    Posted by malvuln on Apr 05Discovery / credits: Malvuln (John Page aka hyp3rlinx) (c) 2024 Original source: https://malvuln.com/advisory/0e6e40aad3e8d46e3c0c26ccc6ab94b3.txt Contact: malvuln13 () gmail com Media: twitter.com/malvuln Threat: Backdoor.Win32.Agent.ju (PSYRAT) Vulnerability: Authentication Bypass RCE Family: PSYRAT Type: PE32 MD5: 0e6e40aad3e8d46e3c0c26ccc6ab94b3 Vuln ID: MVID-2024-0677 Disclosure: 04/01/2024 Description: The PsyRAT 0.01 malware listens on...

Customers

Newsletter

{subscription_form_1}