Evidence annex
The Adversary Evidence Annex
Our control-evasion research and detection-gap analysis, described here at category level and released in full only under a mutual non-disclosure agreement.
Why it is gated
This material is dual use
The annex is gated for three specific reasons, none of which is a sales mechanic. If any of them stopped applying, the gate would come off.
The three reasons
- Published openly, evasion tradecraft is a capability transfer to exactly the people our customers are defending against.
- Naming a specific product's weakness in public is legally exposed and professionally discourteous, and it is not necessary to make the point.
- A detection gap in a widely deployed control is a live risk to every organisation running it until that control is updated.
How access works
- 01
Request
Write to security@ with your organisation, your role and which control categories are relevant to you.
- 02
Verification
We verify that the requester holds a security role at the organisation named, through a channel the organisation controls.
- 03
Mutual NDA
A mutual non-disclosure agreement is executed. It is mutual because your interest in the material is as confidential as ours.
- 04
Scoped release
You receive the sections covering the categories you operate, not the whole annex, with the reproduction harness where one exists.
Contents
What the annex covers
By control category and artefact type. This description is generated from a content model that holds two identifiers per entry and nothing else, so this page has no field in which a product name or a finding could appear.
Endpoint detection and response
- Evasion tradecraft
- Detection-gap analysis
Network detection and response
- Detection-gap analysis
SIEM and detection content
- Detection-gap analysis
Email security
- Evasion tradecraft
Data loss prevention
- Evasion tradecraft
Web application firewalls
- Evasion tradecraft
Identity and access management
- Executed-action logs
AI guardrail layers
- Reproduction harness
Moderation layers
- Reproduction harness
Airspace and counter-drone telemetry
- Detection-gap analysis
Operational-technology telemetry
- Detection-gap analysis
Physical-security telemetry
- Executed-action logs
No finding, product name, version, bypass claim or exploit detail appears anywhere on this page, and the structure of the underlying content makes it impossible to add one here by accident.
Request access
How to ask
Access is granted to security practitioners at the organisation operating the controls concerned. We decline requests we cannot verify.
Include in your request
- Your organisation and your role within it
- A work email address at that organisation's domain
- The control categories relevant to your estate
- Whether you need the reproduction harness
- Your preferred route for executing the mutual NDA
- Any deadline you are working to
Send requests to security@veync.com
This deployment has no form service configured, so sending will open a pre-filled message in your email client. Nothing is transmitted to a third party.
Or start with what is public
The platform, the modules and the framework mapping are all documented openly. The annex only adds the material that cannot responsibly be published.
Veync operates only under written authorization and defined rules of engagement.