Kaspersky Threat Intelligence Portal vs Pulse Intelligence

Kaspersky Threat Intelligence Portal is a cloud investigation workspace that gives security teams access to current cyberthreat intelligence. Its tools support indicator enrichment, malware analysis, threat actor and campaign tracking, and incident response. Threat Lookup connects related threats in Kaspersky’s knowledge base, while Threat Analysis examines suspicious files using multiple analysis layers. AI features provide summaries for triage and investigation, actor profiles linking updated tactics, techniques, procedures, campaigns, and indicators in related reports, plus OSINT search and relationship tracing through KIRA. Remote MCP can connect compatible assistants such as Claude and ChatGPT to portal data. Users can look up IP addresses, hashes, domains, and web addresses; registered users can submit URLs to a sandbox for reports on page activity. The REST API supports URL lookups using a token and file submissions for sandbox analysis, with a documented maximum file size of 256 MB. Listed connectors include Maltego, MISP, Splunk Enterprise Security, IBM QRadar, and Elastic SIEM. Free access is available, with limited suspicious-file and URL executions. General access may show no data in some report sections; full reports require demo access.

Pulse Intelligence is an open-source, self-hosted threat intelligence workspace for analyst workflows. It organizes threat actors, aliases, campaigns, indicators, reports, sources, CVEs and ATT&CK mappings, and ingests public feeds including CISA KEV, NVD, FIRST EPSS, abuse.ch, OTX, vendor blogs and security news. Indicator enrichment uses OTX, AbuseIPDB and VirusTotal, with Redis-backed quota controls. Analysts can save hunts across indicator fields, receive alerts for new matches and export results as CSV, STIX 2.1, MISP JSON, or Snort and Suricata rules. Scheduled Markdown reports can cover new indicators, KEV additions, hunt alerts and feed health. A public read-only API with scoped keys supports integrations; its default limit is 120 requests per API key per 60-second window, and indicator pages are capped at 500. The project lists Argon2id passwords, database-backed session cookies, hashed API keys and an admin-only audit log. Deployment requires Node.js 20.9+, PostgreSQL 17 or compatible PostgreSQL, and a Redis-compatible server. Native and Docker Compose deployment paths are documented.