Threatless Labs
Original research into how organizations are really exposed.
Threatless Labs is the research wing of Threatless. It studies how attacks actually work, develops the methods the AI-native engines depend on, and publishes only what it can prove. What it learns in the field goes back into the technology; what the technology sees in the field sharpens the research.
- Authors
- Named researchers who did the work
- Dates
- Publication date, plus every substantive update
- Method
- How the work was done, in reproducible detail
- Limitations
- What the work does not show
- Artifacts
- Code or data, where safe and licensed to share
- Disclosure
- Coordination status for any vulnerability
Areas of inquiry
The questions Labs works on.
Areas of investigation, not announcements of results. Findings are published only when they meet the standard.
- 01
Attack surface intelligence
How organizations can discover, attribute and understand what they expose, and where outside-in views mislead. - 02
Evidence and validation
What makes a finding trustworthy: evidence, reproducibility and validation that is safe to perform. - 03
Exposure prioritization
How context, reachability and ownership should shape what gets fixed first, and how to test that it works. - 04
Disclosure practice
How to coordinate responsibly with vendors and owners when research finds weaknesses in systems we do not own.
Publications
Every piece of work, labeled for what it is.
A reader should always know what they are reading: a reviewed study, an engineering note or an advisory.
Go to the research index- Research papers
- Original investigations with method, results and limitations. Reviewed internally before publication; any external peer review is identified as such.
- Technical notes
- Shorter engineering write-ups on methods, tooling and lessons learned, clearly labeled as in-house work.
- Advisories
- Vulnerability write-ups, published only after coordinated disclosure with the affected party.
- Tools and datasets
- Released only where it is safe to do so and the licensing is clear.
Research ethics
How Labs handles sensitive work.
- 01
Authorization for active testing
Any active testing has written authorization and a defined scope, including test environments used for research. - 02
Coordinated disclosure
Weaknesses found in third-party systems are reported to the affected party first, with time to fix them before any publication. - 03
No harmful releases
Labs does not publish exploit material that would put people at risk, and removes identifying details of systems and organizations. - 04
Independence, stated plainly
When Threatless software contributes to a finding, the publication says so. In-house evaluation is never presented as independent validation.
Collaboration
Work with Threatless Labs.
Researchers, academics and engineering teams with a shared question are welcome to get in touch. Tell us about the problem, your approach and how you would like to collaborate.
Start a research conversationHow does Threatless Labs relate to Threatless Technologies?
Threatless Labs is the research wing of Threatless: it develops the methods the AI-native engines depend on and publishes its own work to a named standard. Threatless Technologies builds and delivers the platforms, products and services those methods go into.
Does Labs publish vulnerability details?
Only after coordinated disclosure with the affected party, and without details that would put people at risk.
I found a vulnerability in a Threatless system. Who do I tell?
Please follow our vulnerability disclosure policy on the security page rather than the general research contact.
Are there publications yet?
The research index opens with the first publication that meets the standard, and lists nothing before then.
Reporting a vulnerability? Go to security and disclosure.
Related
Threatless Labs
Bring us a hard question.
If you are working on a problem in attack surface intelligence, assessment evidence or exposure prioritization, we would like to hear about it.