OX Radar and Response Center | Why “Does This Threat Affect Us?” Is the New Security Question

Reading Time: 5 min

OX Security has launched OX Radar and a new Response Center, two tools built around one question every security team asks after a big disclosure: does this threat actually affect us? The company announced both on November 18, 2026. OX Radar watches for new vulnerabilities, poisoned packages and actively exploited threats. The Response Center then checks each one against a customer’s own code and environment.

The timing fits the moment. In a single week, defenders faced a critical Java runtime bug, a poisoned Microsoft package on PyPI and dozens of AI-found Apple flaws. Most teams cannot read every advisory, let alone check every system by hand. Tools that answer “are we exposed?” in minutes rather than days are becoming a core part of the security stack.

What OX Radar and the Response Center Do

The two tools work as a pair. One watches the outside world. The other looks inward at the customer’s environment.

OX Radar watches the threat feed

OX Radar scans CVE databases, known-exploited vulnerability catalogs, security advisories and vendor research about every ten minutes. For customers, it focuses on compromised or malicious dependencies, exploited vulnerabilities and critical CVEs. A separate public feed tracks new npm and PyPI packages, AI skills and Model Context Protocol (MCP) servers.

The Response Center checks your exposure

When a threat appears, the Response Center maps it to the customer’s assets. It finds which repositories, libraries and services are affected and adds context and fix guidance. Teams can start an investigation from a CVE ID, a GitHub Security Advisory ID or an advisory URL.

Signals it combines

  • CISA and ENISA known-exploited vulnerability catalogs
  • EPSS scores, which predict the chance of exploitation
  • VEX statements on whether a product is truly exploitable
  • AI-generated exploit checks and runtime visibility from the OX platform

From finding to fix

Teams can rank risk by severity, active exploitation, code usage and reachability. They can then open tickets, pick safe versions and create fix pull requests from the same place. The tool also keeps a record of each response, which helps with audits and post-incident reviews.

The question is no longer "is this threat dangerous?" It is "is it dangerous to us?"

Why “Does It Affect Us?” Is Now the Key Question

OX CEO Neatsun Ziv framed the launch around relevance rather than raw danger. That shift reflects a real problem across the industry.

Too many alerts, too little time

Tens of thousands of new CVEs appear every year. AI-assisted research is adding even more, faster. Security teams spend hours checking advisories, asset lists and scanner output just to learn whether a new threat applies to them. Many alerts turn out to be noise, but nobody can know without checking.

Severity alone misleads

A CVSS score of 9.8 means little if the vulnerable function never runs in your code. A medium bug can be urgent if attackers already exploit it and it sits on an internet-facing service. Real priority depends on three things: is it exploited, is it present, and is it reachable?

Supply chain attacks move in minutes

Poisoned packages now appear and vanish quickly. This week’s Microsoft Agent Framework PyPI compromise lasted about 55 minutes. A daily scan would miss it entirely. Feeds that refresh every few minutes give teams a better chance to react before damage spreads.

Where OX Radar Fits in the Market

OX is not alone in chasing this problem. Still, its approach shows where application security is heading.

Part of a wider platform

Former Check Point executives Neatsun Ziv and Lior Arzi founded OX Security in 2021, after the SolarWinds supply chain attack. The company calls its platform an AI-native application protection platform (AINAPP). It covers code scanning, cloud security, AI agent security and an agentic pentester. OX Radar and the Response Center plug into that platform for existing customers.

A crowded and fast-moving field

Application security posture management (ASPM), software composition analysis and cloud security vendors are all adding exploitability and reachability context to their tools. The market is moving away from long lists of findings toward short, ranked answers. For buyers, the real test is accuracy on fresh threats, speed of the first verdict and how well the tool fits existing developer workflows.

Vendor claims need testing

OX has not published detection rates, false-positive figures or independent tests for the new tools. Buyers should run them against real recent threats, such as Java4Shell or the PyPI compromise, and compare the results with their own manual findings.

How to Build “Does It Affect Us?” Into Your Process

You can improve exposure triage with or without a new product.

  1. Know what you run. Keep an up-to-date SBOM for every application and container image.
  2. Prioritize by exploitation. Put KEV entries and high EPSS scores at the top of the queue, above raw CVSS.
  3. Check reachability. Confirm whether the vulnerable code path actually runs before you escalate.
  4. Watch your registries. Monitor npm, PyPI and MCP servers for malicious or hijacked packages that your teams use.
  5. Automate the fix path. Link findings to tickets and pull requests so fixes ship fast.
  6. Measure time to answer. Track how long it takes to say “affected” or “not affected” after a major disclosure. Our supply chain security guide explains how to build this capability.
The fastest team is not the one that patches everything. It is the one that knows what to patch first.

OX Radar and the Response Center are a vendor answer to an industry-wide problem. Whether they deliver will depend on real-world accuracy, not launch claims. But the idea behind them is sound. Exposure, not volume, should drive the security queue.

As AI floods the world with new vulnerabilities, the teams that win will be those that can separate the threats that matter to them from the noise, and act on them within hours.

Want to see what a fast-moving supply chain attack looks like up close?

Read our deep-dive: Java4Shell CVE-2026-114938 | How an AI-Found Base64 Bug Puts Enterprise Java at Risk.

Know your exposure before the next disclosure lands in your inbox.
SECITHUB FAQ banner for OX Radar, the OX Security Response Center and exposure-based vulnerability prioritization
What is OX Radar?

OX Radar is a threat monitoring service from OX Security. It scans vulnerability databases, exploited-vulnerability catalogs and advisories about every ten minutes for threats that may affect customers.

What does the OX Security Response Center do?

It checks a new threat against a customer’s code and environment, finds affected assets and provides context, prioritization and fix guidance.

What signals does the Response Center use?

CISA and ENISA known-exploited catalogs, EPSS exploit predictions, VEX exploitability statements, AI-generated exploit checks and runtime visibility.

Is OX Radar available to everyone?

The Response Center and customer OX Radar are part of the OX Security platform. A broader OX Radar research feed is public on the OX Security website.

Why is reachability important in vulnerability prioritization?

A vulnerable library only matters if the affected code runs in your application. Reachability analysis helps teams skip noise and fix real risks first.

How can teams triage new threats faster without new tools?

Maintain SBOMs, prioritize by KEV and EPSS, check reachability, monitor package registries and automate tickets and fix pull requests.

Sources

OX Security launches OX Radar and Response Center – Cybersecurity Insiders

Known Exploited Vulnerabilities Catalog – CISA

OX Security launched OX Radar and a Response Center to show teams which new threats actually affect them. Here is how they work, why exposure-based triage matters and how to build it into your own process.
0 0 votes
Article Rating
Subscribe
Notify of
guest

0 Comments
Oldest
Newest Most Voted