OX Security
Introducing Agent Activity: See What Your AI Agents Are Actually Doing (2026-10-28) commercialThe section your link pointed to isn't on OX Security's page any more, so we've brought you to the top.
Summary
OX Security is a commercial appsec platform, run as a SaaSSaaSSoftware delivered over the internet and run on the provider's infrastructure, so the buyer pays a subscription instead of installing or operating anything locally. service, that governs risk from AI agent activity through to cloud runtime. Rather than just flagging vulnerabilities, it inspects every package an AI agent tries to install against policy, blocking known-malicious ones before they reach a developer machine, and can hold newly published packages back until the community has had time to flag them. It extends this into runtime through a CNAPPCNAPPA cloud-native application protection platform that combines checks across cloud configuration, workloads and development. It helps teams connect risks that separate tools might report apart. layer covering cloud, Kubernetes and data posture, with graph-based attack pathattack pathA possible sequence of steps an attacker could take to reach a valuable target. It connects weaknesses, permissions and reachable systems rather than treating each finding separately. mapping and reachability filtering to cut unreachable findings from the backlog. It is built for application security and platform teams dealing with AI-generated code and agentic tooling rather than traditional static scanning alone, and sits in the CNAPP and AI-security management space rather than any single named category. The project is active, with 28 tracked releases and the most recent only 17 days old.
How OX Security helps
Which AI agent packages are safe to install before they land on a developer machine or in the SBOM?
checks each install attempt against policy and blocks known-malicious packages outright, and can hold newly published packages for a cool-down period until the community has flagged problems
Which AI agents, models, MCP servers and non-human identities exist in this environment, and what can each one reach?
discovers them through agentic-level inspection and maps the assets, data and systems they are able to touch, surfacing hidden backdoors and reachable exposures
What is an AI agent, model or MCP server actually doing right now?
detects AI-driven activity and configuration across cloud and runtime in real time, showing agents calling tools, models accessing data, and MCP servers executing autonomously
Which vulnerabilities and misconfigurations in this backlog are actually exploitable?
filters findings by reachability, dropping vulnerable packages, misconfigurations and supply-chain issues that cannot be reached in the running environment and keeping only what is evidenced as exploitable
Who touched what during a runtime incident, and what else could they have reached?
alert detail views show who or what acted, what they touched, and the further blast radius available to them, drawing on the cloud graph of asset relationships
What does the full inventory of workloads, identities, data stores, clusters and AI agents running in the cloud look like right now?
maintains a continuously updated inventory across cloud accounts and Kubernetes clusters, including shadow AI and unmanaged non-human identities
Languages
Screenshots
From the release notes, newest first. Click one to see it full size.Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
Five scores for OX Security, 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 → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
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 OX Security 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…
Website history
ox.security, every changeOX Security's home page and 20 more pages as they looked each month from September 2022 to October 2026: 33 renders, 7 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
5 entries
No entries match these filters.
- October 20262
- September 20263
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.