PAGES
← all tools
◆ Digital Forensics & Incident Response

cortex-analyzers

3.10.5 open-source

Free plan: not checked yet · Open source: yes

Starting price: not checked yet

Collection of Cortex analyzers and responders for automating observable analysis and response actions in TheHive Project.

What you can do now

Checking Plays…

Summary

cortex-analyzers is an open-source AGPL repository of Cortex analyzers and responders for DFIRDFIRDigital forensics and incident response, investigating what happened during a security incident and containing it. The work includes preserving evidence, reconstructing activity and restoring systems. teams, used alongside TheHive and Cortex rather than as a standalone application. It connects incident-response workflows to services such as VirusTotal, AbuseIPDB, OpenCVE, CrowdStrike Falcon, OpenCTI, and Zscaler, including enrichment, malware analysis, URL intelligence, and actions such as submitting abuse reports or saving IDSIDSAn intrusion detection system, monitoring traffic or host activity for suspicious behavior and producing alerts. Detection alone does not necessarily block the activity. and YARA rules. Its documentation supports analyzers written in Linux-compatible languages including Python, Ruby, and Perl, so SOCSOCA security operations center, the team or function that monitors threats, investigates alerts and coordinates incident response. Its work can be internal, outsourced or shared. and incident-response analysts can configure or extend it. The project had five tracked releases, with the last released this week.

Collection of Cortex analyzers and responders for automating observable analysis and response actions in TheHive Project.

How cortex-analyzers helps

Which protocols or versions are active on a specific server?

a port scanner answers this by listing what is listening and its version

Which manifests would be blocked by a specific policy?

the analyzer runs the entire rule set against a directory of YAML and lists every violation found by file and rule

Which workloads request privileges that were not approved?

the analyzer compares each pod spec against the rule set and names the containers requesting host access or root, along with the rule that was violated

Did a recent rule change accidentally expose something?

the analyzer replays a saved set of manifests against both versions of a rule and displays any discrepancies in the resulting verdict

Are all pipelines using the same security rules?

every run records the git reference of the policies it used, showing a mismatch if a pipeline judges against an outdated set of rules

What intelligence can be gathered about an IP address or domain?

the analyzer can use specialized integrations to look up threat intelligence, such as querying services or analyzing specific records.

all 9 features, with the evidence for each →

Languages

Not documented

Features

9 capabilities across 3 capability groups

Built from cortex-analyzers's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • cortex-analyzers covers 3 of the 8 investigation and response capabilities we track.

What cortex-analyzers offers you

  • Command-line interface

Response playbook automation 2 features Investigation and response since 2024
Active response and blocking Executes automated actions to block indicators, revoke sessions, or trigger takedowns in external systems. 12 releases · first seen Nov 2024

Shared capability: Response playbook automation

Verdict-based automated response Triggers automated response actions based on analysis verdicts via the Suspicious_Verdict responder. 5 releases · 1 other source · first seen Nov 2024

Shared capability: Response playbook automation

Threat indicator matching 2 features Investigation and response since 2024
Threat intelligence enrichment Queries external threat intelligence platforms to enrich observables with context such as indicators, vulnerabilities, or malicious status. 23 releases · first seen Feb 2024

Shared capability: Threat indicator matching

Email breach lookups Checks whether email addresses appear in known data breaches via the XposedOrNot analyzer, without requiring an API key. 3 releases · first seen Mar 2025

Shared capability: Threat indicator matching

Malware sandbox analysis 1 feature Investigation and response since 2026
Sandbox analysis Submits observables to the ANY.RUN sandbox for dynamic analysis, with support for proxy configuration, alternative domains, and automated interactivity options. 1 release · first seen Oct 2026

Shared capability: Malware sandbox analysis

Other / not yet classified 4 features Features we have not matched to a capability yet. A suggested match is marked.
Domain and IP registration lookups Retrieves domain and IP registration data using the RDAP protocol via the RDAP analyzer. 12 releases · first seen Feb 2024
Malware scanning suggested Scans observables for malware via the ScanMalware analyzer. 5 releases · first seen Nov 2024

Suggested capability: Static malware analysis. This is our guess, not confirmed.

MAC address enrichment suggested Looks up MAC address metadata via the macaddress.com analyzer. 2 releases · first seen Oct 2026

Suggested capability: Threat indicator matching. This is our guess, not confirmed.

Analyzer development tooling Provides a TestAnalyzer utility that supports artifact-based observable testing to aid in developing and validating custom analyzers. 1 release · first seen Oct 2026

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for cortex-analyzers, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail cortex-analyzers puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Coverage

Missing something? Tell us

What cortex-analyzers connects to, runs on and detects, read from its release notes and docs. So far: 8 new integrations, 1 updated integration.

Show

9 changes, tracked since Sep 3, 2026.

  • Oct 62026

    new RDAP Analyzer

    Add RDAP analyzer by @yatuk in https://github.com/TheHive-Project/Cortex-Analyzers/pull/1484

    3.10.1 Source ↗

  • Oct 62026

    new XposedOrNot Analyzer

    Add XposedOrNot analyzer (email breach lookup, no API key required) by @DevaOnBreaches in https://github.com/TheHive-Project/Cortex-Analyzers/pull/1471

    3.10.1 Source ↗

  • Oct 62026

    new macadress.com Analyzer

    Add macadress.com analyzer for MAC address enrichment by @samymassoud in https://github.com/TheHive-Project/Cortex-Analyzers/pull/1495

    3.10.1 Source ↗

  • Oct 62026

    new ScanMalware Analyzer

    Add ScanMalware analyzer by @jonaslejon in https://github.com/TheHive-Project/Cortex-Analyzers/pull/1497

    3.10.1 Source ↗

  • Oct 62026

    new Suspicious_Verdict Responder

    Add Suspicious_Verdict Responder by @EnzoCyberSec in https://github.com/TheHive-Project/Cortex-Analyzers/pull/1503

    3.10.1 Source ↗

  • Oct 62026

    updated Splunk Integration — ES Notable Status Sync

    Splunk Integration - ES notable status sync by @nusantara-self in https://github.com/TheHive-Project/Cortex-Analyzers/pull/1499

    3.10.1 Source ↗

Changes per month New Updated Retired
2026-093
2026-106
How we count

Read from 4 of 51 release notes and docs updates we hold for cortex-analyzers. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through cortex-analyzers's life, so an old integration can show a recent first-seen date.

Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.

Releases

Show
Coverage in all entries

50 entries

  1. November 20261
  2. October 20262
  3. September 20261
  4. August 20262
  5. July 20261
  6. June 20262
  7. May 20261
  8. April 20263
  9. March 20264
  10. February 20263
  11. January 20264
  12. December 20252
  13. November 20251
  14. October 20252
  15. August 20253
  16. July 20251
  17. June 20252
  18. May 20253
  19. April 20251
  20. March 20255
  21. February 20251
  22. January 20251
  23. December 20243
  24. November 20241
    Show
    Coverage in all entries

    50 entries

    All 51 releases

    Project health

    Issue, contributor and maintainer activity in thehive-project/cortex-analyzers, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors not measured distinct committers, last 12 months
    2. Maintainers not measured core set, last 12 months
    3. Bus factor not measured committers behind half the commits
    4. Community-filed 100% of issues opened, last 12 months
    5. Median time to close 28 days first maintainer reply 14 days
    6. Open backlog 116 of 738 issues ever filed
    1. Issues opened / month 4 · 0 communitymaintainers
    2. Open backlog 116
    3. Contributors / month not measured
    4. Commits / month not measured
    5. Stars not measured
    Issue themes, last 12 months
    • other 100%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    No high or critical advisory in the lockfiles we checked.

    Fixed in cortex-analyzers 3.10.2 (it locked pillow 13.0.0, which has GHSA-332p-7hrc-92wf).

    Fixed in cortex-analyzers 3.10.2 (it locked pillow 13.0.0, which has GHSA-332p-7hrc-92wf).

    Fixed in cortex-analyzers 3.10.2 (it locked black 26.10.1, which has GHSA-cg8m-r9f2-5wm2).

    Fixed in cortex-analyzers 3.10.2 (it locked nbconvert 7.17.2, which has GHSA-pjvx-prjx-h659).

    Fixed in cortex-analyzers 3.10.4 (it locked pillow 13.0.0, which has GHSA-332p-7hrc-92wf).

    We check the lockfiles its release builds images from: 22 Python. Go modules, other lockfiles and vendored code aren't checked.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    Saved in this browser. Sign in to sync your tools.