Building a CTI Platform from a Host on VPS: From IOC Collection to Malware Analysis and Data Sharing with MISP Community
This guide walks through building a Cyber Threat Intelligence (CTI) platform from a host on a VPS, covering IOC collection, malware analysis, and data sharing with the MISP...
This guide walks through building a Cyber Threat Intelligence (CTI) platform from a host on a VPS, covering IOC collection, malware analysis, and data sharing with the MISP community. It uses open-source tools deployable on NVMe Cloud VPS with Docker, Nginx, and databases, suitable for DevOps, security, and advanced threat analysis environments.
Introduction to the CTI Platform and Objectives
This topic focuses on building a Cyber Threat Intelligence (CTI) system from a physical or virtual host on a VPS, capable of collecting Indicators of Compromise (IOCs) such as IP addresses, URLs, and file hashes from sources like system logs, web servers, or monitoring tools. These IOCs are then analyzed to identify threats, especially malware, using static and dynamic analysis tools. Finally, the data is standardized and shared with the MISP (Malware Information Sharing Platform) community to support other organizations in threat prevention. The goal is to create an automated, open, and scalable system suitable for organizations with limited budgets but needing professional threat analysis capabilities.
Setting Up the Environment on VPS
To deploy the platform, a Linux-based NVMe Cloud VPS (Ubuntu 22.04 or Debian 12) is required. Use the NVMe Cloud VPS for Docker, Nginx & Databases service to ensure high performance and scalability. Install the necessary tools:
sudo apt update
sudo apt upgrade -y
sudo apt install -y docker.io docker-compose git python3-pip
sudo systemctl enable docker
sudo systemctl start docker
Then, create a project directory and initialize the required Docker containers. For example, use Docker Compose to deploy services like MISP, Suricata (for IOC collection), and malware analysis tools such as YARA, VirusTotal API (if you have an account), or Cuckoo Sandbox (in a safe environment).
Collecting IOCs and Analyzing Malware
IOCs (Indicators of Compromise) are signs that a system may be compromised. They include IP addresses, URLs, file hashes, or malicious code patterns. To collect IOCs, you can use:
- Suricata: An open-source network monitoring tool that can be deployed on the VPS to monitor traffic and generate IOCs from suspicious activities.
- Osquery: A system monitoring tool that allows querying system information such as running processes, network connections, and files.
- Logstash/ELK Stack: To collect and process logs from multiple sources, standardize data, and store it for later analysis.
To analyze malware, you can use:
- YARA: A tool for detecting malware using rules that define malicious patterns.
- Cuckoo Sandbox: A dynamic malware analysis tool that runs code in an isolated environment and logs its behavior.
- VirusTotal API: Connect to the popular malware analysis service to check file hashes or URLs.
Analysis can be automated using Python or shell scripts, leveraging open-source APIs and tools to process IOCs and identify threats.
Sharing Data with the MISP Community
MISP is an open-source threat intelligence sharing platform widely used in the security community. To share data, deploy MISP on the VPS or use a public MISP service (if available). Key steps include:
- Deploy MISP using Docker or from source.
- Set up API keys to connect with IOC collection and analysis tools.
- Create events in MISP containing IOCs, threat descriptions, and related information.
- Integrate with analysis tools to automatically generate and share events when threats are detected.
Data sharing can be done via the MISP API or XMPP protocol. Organizations can join the MISP community to receive information from other sources and share their own data.
Testing and Maintenance
To ensure the system runs stably, perform regular checks:
- Test the entire workflow from IOC collection to data sharing.
- Monitor the performance of services like MISP, Suricata, and Cuckoo Sandbox.
- Update tools and YARA rules to respond to new threats.
- Ensure data is backed up regularly and a disaster recovery plan is in place.
To test the connection to MISP, use the cURL command:
curl -X GET "https://your-misp-instance/api/events" -H "Authorization: YOUR_API_KEY" -H "Accept: application/json"
If the connection succeeds, you will receive a list of shared events.
Troubleshooting
Common issues when deploying a CTI platform include:
- IOCs not being collected: Check Suricata or Osquery configurations and ensure log sources are correctly provided.
- Malware analysis failing: Verify the connection to the VirusTotal API or Cuckoo Sandbox configuration.
- Unable to share data with MISP: Check API keys, access permissions, and network connectivity to the MISP instance.
To resolve, review logs from each service and ensure all services are running correctly.
References
For more information on the technologies used, refer to:
Recommended NVMe Cloud VPS Plans to Deploy This Setup
Enterprise RAID 10 NVMe SSDs, CMC & FPT District 9 uplinks with Anycast Anti-DDoS and 99.99% SLA.
VPS-3E
10% VAT included
- CPU: 2 vCPU
- RAM: 4 GB
- SSD: 50 GB NVMe
