Spektion developed a sensor that observes what executed on the host, at what privilege, reaching what, independent of what the agent reported doing.

Public source

Publisher name

Public post

In about 7% of the transcripts METR and Redwood reviewed, an agent's record of what it ran did not match what it ran. That is 96 of roughly 1,300, from the OpenAI agents…

Log in to read the full post

Company

Spektion

Continuous Runtime Exposure Management: what executes, at what privilege, what it can reach, before any CVE exists.

Industry
Computer and Network Security
Location
Dripping Springs, US
Company size
11–50 employees

About Spektion

Spektion is the Continuous Runtime Exposure Management (CREM) platform. A lightweight sensor records what actually executes on every workstation and server, at what privilege, reachable from where, and with what blast radius. That evidence sets which CVEs get patched first and surfaces the exploitable weaknesses that have no CVE. What customers measure: → 60% fewer emergency patch events (anonymized customer data) → 27% attack surface reduction in 30 days (anonymized customer data) → 50 to 80 percent fewer critical CVEs pushed to remediation, validated in proof-of-value Why the numbers hold: about 70% of critical CVEs sit in software that is not running. The same CVE scores 9.76 where it runs as SYSTEM and 4.00 where it sits idle. Spektion Research found 71% of applications with exploitable flaws had no CVE assigned. Founded in 2024 by red teamers, vulnerability researchers, and CISOs. Backed by LiveOak Ventures. Customers include NielsenIQ, Granicus, and Juul Labs. Runtime Insights, the monthly newsletter, lives on this page. Demo requests at spektion.com/demo.

See more

Latest activity

3 signals

Discover more

Similar public activity from other companies.

Customize signals for your business.

Know everything happening across the B2B world, and act on the company movements that matter to you.

© 2026 SeedOpsCompany intelligence.

SeedOps.