Conundrum Intelligence
Platform overview How the whole intelligence cycle runs

The intelligence cycle

DirectionSet your requirements, and everything else follows CollectionAutomated open-source collection, with health checks AnalysisTriage, question and map to frameworks

 

ProductionWrite, and check generated reports against sources DisseminationRoute it to the people and systems that need it FeedbackTeam input loops back in, with manual approval
Solutions overview One platform, every major framework

By industry

Financial servicesBanks, insurers, payments HealthcareProviders, payers, life sciences GovernmentAgencies and defence suppliers

By use case

Threat intelligenceCollection through to reporting Vulnerability managementPrioritise what's actually exploited ICRMCollection resource management
Services
Resources overview Learn the craft, then the platform

Learn

Knowledge BaseIntelligence tradecraft, explained properly Threat landscapeThe five major attack vectors DocumentationUsing the platform

Verify

Trust CenterHow we check our own output API & integrationsWebhooks, MCP, REST NewsletterWeekly read on the landscape
Company Pricing
Log in Request a demo
Platform overview Direction Collection Analysis Production Dissemination Feedback
Solutions overview Financial services Healthcare Government Threat intelligence Vulnerability management ICRM
Services
Resources overview Knowledge Base Threat landscape Documentation Trust Center API & integrations Newsletter
Company Pricing
Log in Request a demo

Compliance & security

Built with security-first principles, and mapped to the standards every regulated organisation faces.

Frameworks

The regimes differ in wording. One intelligence workflow produces the evidence each of them asks for.

NIST CSF 2.0

Aligned to the core functions (Govern, Identify, Protect, Detect, Respond and Recover) with continuous threat monitoring and intelligence-driven risk assessment supporting Govern, Identify and Detect.

NIS 2

Operationalises the continuous-monitoring, risk-management and incident-documentation duties NIS 2 introduces. Dated requirements and tagged dissemination logs evidence risk-based prioritisation, supply-chain oversight and timely incident reporting (Arts 21, 23–24).

GDPR

Data minimisation in collection, clear consent mechanisms, data portability support and the right to erasure. The privacy policy details how personal data is processed and protected.

ISO 27001:2022

Information security management aligned to the standard: formal risk assessment, access control policies, incident response procedures and continuous monitoring of security posture.

DORA

Supports all five pillars: evidence for ICT risk management, enriched reports for major-incident reporting, real-world TTPs to shape resilience testing, and threat monitoring to inform third-party risk.

Audit-ready evidence

One workflow is the proof for all five: dated requirements show what you prioritised, consolidated reports show how you analysed it, and dissemination tagging shows who you told and when: the timestamped, traceable trail regulators ask for.

Security practices

  • Encryption: all data encrypted in transit (TLS 1.3) and at rest (AES-256). Keys and credentials stored using environment-level encryption.
  • Access controls: role-based access with tenant-level isolation, plus session management on every account.
  • Monitoring: continuous security monitoring, automated vulnerability scanning, and incident response procedures.
Conundrum Intelligence

Right Answer. Right Person. Right Time.

Platform

Overview ICRM Pricing API docs

Solutions

Financial services Healthcare Government All solutions

Resources

Knowledge Base Threat landscape Trust Center Documentation Newsletter

Company

About Careers Services Contact Privacy
© 2026 Conundrum Intelligence