Skip to content
Snippets Groups Projects
Commit 20b4e53c authored by Chris Moberly's avatar Chris Moberly
Browse files

Threat Intelligence Iterations

parent bb315a42
No related branches found
No related tags found
1 merge request!10216Threat Intelligence Iterations
......@@ -2,17 +2,17 @@
title: Threat Intelligence Team
---
## <i class="fas fa-bullseye" id="biz-tech-icons"></i> Engaging Threat Intelligence
## Engaging Threat Intelligence
Please follow our [RFI process](#requests-for-information-rfi) to contact the team.
For a less formal discussion, you can find us in Slack in the `#sd_security_threat_intel` channel.
## <i class="fas fa-rocket" id="biz-tech-icons"></i> Our Vision
## Our Vision
Empower GitLab to make informed, intelligence-driven decisions that keep our company and customers secure, while setting a new standard for transparency and collaboration across the industry.
## <i class="fas fa-compass" id="biz-tech-icons"></i> Our Mission Statement
## Our Mission Statement
Our mission is to provide actionable intelligence that empowers GitLab to make informed, proactive decisions about security.
......@@ -20,22 +20,22 @@ We monitor the threat landscape with a focus on identifying the most relevant ri
By staying vigilant and sharing targeted intelligence, we strive to help GitLab anticipate challenges, move swiftly, and protect our customers and our platform.
## <i class="fas fa-users" id="biz-tech-icons"></i> The Team
## The Team
### Current Structure
The Threat Intelligence initiative is driven by cross-functional participants from SIRT and the Red Team, who dedicate 10-20% of their time to the program while still prioritizing their primary roles. They focus on building capabilities, delivering actionable intelligence, and demonstrating early results.
We are in the early stages of our Threat Intelligence journey, and currently have one dedicated engineer. This is augmented by cross-functional participants from SIRT and the Red Team, who dedicate 10-20% of their time to the program while still prioritizing their primary roles. They focus on building capabilities, delivering actionable intelligence, and demonstrating early results.
### Current Priorities
The initiative's current priorities are:
The teams's current priorities are:
1. **Delivering actionable intelligence**: Preparing and presenting concise, actionable reports that inform GitLab of relevant threats, their potential impact, and recommended actions.
1. **Building meaningful connections**: Establishing relationships with industry peers, government entities, and other experts who specialize in the top threats most impactful to GitLab.
As the program matures, we will also include automation and AI as top priorities.
As the program matures, we will focus on program efficiencies using data correlation, automation, and AI.
## <i class="fas fa-stream" id="biz-tech-icons"></i> Services We Provide
## Services We Provide
### Threat Intelligence Reports
......@@ -66,20 +66,20 @@ Recommendations linked to Flash Reports are often time-sensitive and critical. T
Flash Reports use [this template](https://gitlab.com/gitlab-com/gl-security/security-operations/threat-intelligence-public/resources/threat-intelligence-templates/-/blob/main/.gitlab/issue_templates/flash_report.md?ref_type=heads).
#### Threat Insights
#### Threat Briefings
Threat Insights offer regular, high-level updates on the evolving threat landscape. They highlight the most relevant trends, actors, and campaigns that could affect GitLab in the coming weeks or months.
Threat Briefings offer regular, high-level updates on the evolving threat landscape. They highlight the most relevant trends, actors, and campaigns that could affect GitLab in the coming weeks or months.
These reports help team members stay informed, vigilant, and prepared.
Recommendations linked to Threat Insights are not as time-sensitive as those from a Flash Report. They are leveraged for activities like:
Recommendations linked to Threat Briefings are not as time-sensitive as those from a Flash Report. They are leveraged for activities like:
- Product roadmap and prioritization
- Standard iterations to security controls and detection capabilities
- Training on security awareness and job-specific skills
- Purchasing decisions and vendor evaluations
Threat Insights are produced monthly using [this template](https://gitlab.com/gitlab-com/gl-security/security-operations/threat-intelligence-public/resources/threat-intelligence-templates/-/blob/main/.gitlab/issue_templates/threat_insights.md?ref_type=heads) and include a live presentation with a Q&A session.
Threat Briefings are produced monthly using [this template](https://gitlab.com/gitlab-com/gl-security/security-operations/threat-intelligence-public/resources/threat-intelligence-templates/-/blob/main/.gitlab/issue_templates/threat_briefings.md?ref_type=heads) and include a live presentation with a Q&A session.
### Threat Actor Tracking
......@@ -103,7 +103,7 @@ Supporting S1 incidents will always take priority over all other work.
Requests for Information use [this template](https://gitlab.com/gitlab-com/gl-security/security-operations/threat-intelligence-public/resources/threat-intelligence-templates/-/blob/main/.gitlab/issue_templates/rfi.md?ref_type=heads).
## <i class="fas fa-chart-simple" id="biz-tech-icons"></i> How We Measure Success
## How We Measure Success
We measure the success of our threat intelligence program using three key metrics: Impact, Adoption Rate, and Attribution. We track these metrics using GitLab.com issues and custom labels.
......@@ -136,7 +136,7 @@ Monitoring these metrics helps us continually refine our services, prioritize hi
**Attribution Labels (source of validated intelligence):**
- Threat Insights (`TIAttribution::ThreatInsights`)
- Threat Briefings (`TIAttribution::ThreatBriefings`)
- Flash Reports (`TIAttribution::FlashReport`)
- Threat Actor Tracking (`TIAttribution:ThreatActorTracking`)
- Request for Information (`TIAttribution::RFI`)
......@@ -147,6 +147,6 @@ Monitoring these metrics helps us continually refine our services, prioritize hi
- Intelligence allowed us to identify an attempted attack (`TIImpact::Detection`)
- Intelligence allowed us to respond to an incident (`TIImpact::Response`)
## <i class="fas fa-link" id="biz-tech-icons"></i> Additional Resources
## Additional Resources
- [Threat Intelligence Templates](https://gitlab.com/gitlab-com/gl-security/security-operations/threat-intelligence-public/resources/threat-intelligence-templates): Public template repository for reports, RFIs, etc.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment