Blue team (computer security)
A blue team is a group of individuals who perform an analysis of information systems to ensure security, identify security flaws, verify the effectiveness of each security measure, and make certain all security measures will continue to be effective after implementation.[1]
Some blue team objectives include:
- Using risk intelligence and digital footprint analysis to find and fix vulnerabilities and prevent possible security incidents.
- Conduct regular security audits such as incident response and recovery.[2]
History
[edit | edit source]As part of the United States computer security defense initiative, red teams were developed to exploit other malicious entities that would do them harm. As a result, blue teams were developed to design defensive measures against such red team activities.[3]
Incident response
[edit | edit source]If an incident does occur within the organization, the blue team will perform the following six steps to handle the situation:
- Preparation
- Identification
- Containment
- Eradication
- Recovery
- Lessons learned[4]
Operating system hardening
[edit | edit source]In preparation for a computer security incident, the blue team will perform hardening techniques on all operating systems throughout the organization.[5]
Perimeter defense
[edit | edit source]The blue team must always be mindful of the network perimeter, including traffic flow, packet filtering, proxy firewalls, and intrusion detection systems.[5]
Tools
[edit | edit source]Blue teams employ a wide range of tools allowing them to detect an attack, collect forensic data, perform data analysis and make changes to thwart future attacks and mitigate threats. The tools include:
Log management and analysis
[edit | edit source]Security information and event management (SIEM) technology
[edit | edit source]SIEM software supports threat detection and security incident response by performing real-time data collection and analysis of security events. This type of software also uses data sources outside of the network including indicators of compromise (IoC) threat intelligence.
See also
[edit | edit source]References
[edit | edit source]- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).