Cydarm vs DFIR-IRIS

Cydarm is a cyber incident response management platform for security operations teams. It combines case management, data enrichment, editable playbooks, reporting, collaboration, and response-time SLAs. Teams can assign tasks using an open-source playbook format, while attribute-based access controls restrict visibility from whole cases down to individual comments or data types. Listed integrations include OpenAPI, email polling, webhooks, Jira, ServiceNow, Teams, PagerDuty, Slack, and SMS. Cydarm is offered as a hosted managed service or an enterprise deployment on a customer’s infrastructure, with web, API, and self-hosted platforms. It supports SSO through Microsoft Entra ID, Okta, Google, and AWS, with no SSO fee. Cydarm Technologies states it meets ISO 27001:2022 requirements and has achieved certification. Security information describes disk encryption, TLS 1.2 or higher, dedicated hosted infrastructure, and network segmentation. Pricing is on request; a 30-day trial costs nothing and needs no credit card.

DFIR-IRIS is an open-source incident response platform for teams conducting investigations in a shared workspace. Case records organize assets, indicators of compromise, tasks, evidence and notes with an audit trail. Alerts from SIEM, EDR, MISP, IntelOwl or REST endpoints can be collected, triaged and promoted into cases. Evidence can be checked with SHA-256, MD5 or SHA-1, while access restrictions and logs cover downloads, views and changes. War rooms provide real-time chat, threads, room-specific teams and slash commands that record decisions and case actions. Configurable Jinja templates generate PDF or DOCX executive summaries, technical reports or court-ready documents. The project lists modules including IrisVT, IrisMISP, IrisCheck and IrisWebHooks, along with a REST API and 162 hook binding points. Permissions include deny-all, read-only and full-access case controls. Docker and Docker Compose are recommended; Linux and macOS are officially supported, while Windows may need Dockerfile changes for file storage paths. Documentation identifies v3.0.0-beta.1 as the current v3 release and says beta versions are not production-ready. The project advises restricting access and not exposing IRIS to the Internet.