Analyze the threat landscape using MISP (Malware Information Sharing Platform) by querying event statistics, attribute distributions, threat actor galaxy clusters, and tag trends over time.
2 stars
0 votes
0 copies
0 views
Added November 7, 2026
securitypythongobashtestingapisecurity
Works with
api
Security analysis
A92/100
mediumInstalls packages at runtime which could introduce malicious dependencies
Installs into .claude/skills of the current project.
Are you the author of Webapp Analyzing Threat Landscape With Misp?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/bitbytelabio-webapp-analyzing-threat-landscape-with-misp)
---
name: webapp-analyzing-threat-landscape-with-misp
description: Analyze the threat landscape using MISP (Malware Information Sharing Platform) by querying event statistics, attribute distributions, threat actor galaxy clusters, and tag trends over time.
domain: webapp
category: threat-intelligence
hide: true
license: Apache-2.0
metadata:
manifest_entry: src/corpus/webapp-analyzing-threat-landscape-with-misp/SKILL.md
---
## Helper prerequisites
This bundled skill supplies operational methodology; execution should use evidence_exec or the documented underlying security binaries directly in accordance with engagement scope.
# Analyzing Threat Landscape with MISP
## When to Use
- When investigating security incidents that require analyzing threat landscape with misp
- When building detection rules or threat hunting queries for this domain
- When SOC analysts need structured procedures for this analysis type
- When validating security monitoring coverage for related attack techniques
## Detection Gaps & Validation
- **Attribute-type coverage:** counting only `ip-dst`/`domain`/`sha256` undercounts the landscape -- MISP also stores `ip-src`, `hostname`, `url`, `md5`, `sha1`, `filename|sha256`, and `btc`. Enumerate the full `Attribute.type` set or your IOC-type breakdown is biased.
- **Galaxy/tag inconsistency:** actor attribution lives in `galaxy` clusters (`mitre-intrusion-set`, `threat-actor`) and free-text `Tag`s applied unevenly -- APT28 may appear as "Sofacy", "Fancy Bear", or a galaxy UUID. Normalize via galaxy synonyms before ranking top actors.
- **Sharing/visibility gaps:** API-key org permissions and event `distribution` levels mean `search()` returns only visible events; "top threat level" skews to what your org can see.
- **Stale events:** old events inflate counts unless you bound by `--days`/`timestamp`.
To validate: confirm event totals from PyMISP `search()` match the MISP web UI for the same date range and filters; verify pagination is not truncating results (default page limits). Re-run the technique ranking with galaxy-synonym normalization and confirm duplicate actors collapse. Sanity-check that `T1566`-style technique counts come from ATT&CK galaxy clusters, not ad-hoc tags, before reporting a "top technique."
## Prerequisites
- Familiarity with threat intelligence concepts and tools
- Access to a test or lab environment for safe execution
- Python 3.8+ with required dependencies installed
- Appropriate authorization for any testing activities
## Instructions
1. Install dependencies: `pip install pymisp`
2. Configure MISP URL and API key.
3. Run the agent to generate threat landscape analysis:
- Pull event statistics by threat level and date range
- Analyze attribute type distributions (IP, domain, hash, URL)
- Identify top MITRE ATT&CK techniques from event tags
- Track threat actor activity via galaxy clusters
- Generate temporal trend analysis of IOC submissions
```bash
evidence_exec --misp-url https://misp.local --api-key YOUR_KEY --days 90 --output landscape_report.json
```
## Examples
### Threat Landscape Summary
```
Period: Last 90 days
Events analyzed: 1,247
Top threat level: High (43%)
Top attribute type: ip-dst (31%), domain (22%), sha256 (18%)
Top MITRE technique: T1566 Phishing (89 events)
Top threat actor: APT28 (34 events)
```