Internal detection: a capability that stays home
Internal detection is tooling a vendor describes as held inside the company. The signal in the file may be real, and the person holding that file is not the person who can interrogate it. As of 2026-09-22.
| The term | Internal detection |
|---|---|
| What it names | Detection tooling a vendor describes as internal to itself |
| What it is not | An absence of detection, or a refusal to detect |
| Where the register uses it | One entry's detection fact |
Inclusion rule. Words this site uses in a narrow sense, where the ordinary sense would lead a reader to misread a cell. No vendor statement appears on this page. Order. Fixed order: what the word names, what it excludes, then where it is used here.
1A filled cell that helps only one party
One entry here names a metadata standard for every asset and, separately, describes internal tools for assessing whether a video or audio came from its products. The first fills the file-contents column; the second says who can act on it, and the answer is the vendor.
That is why the register keeps marking and detection as separate facts. A reader comparing filled cells across entries would otherwise treat a claim with a public reader and a claim with none as equivalent, and for a publisher they are not close.
2Why a company might keep the reader
A public detector is also a public target: anybody wanting to defeat a mark can test against it. Keeping detection internal makes the mechanism harder to probe, at the cost of making it useless to everybody the mark was supposedly for.
The register does not adjudicate that trade. It records which entries publish a route a recipient can use and which describe one they cannot, because those are different products from the point of view of anybody receiving a file.
3What it leaves a publisher with
An assurance rather than a capability. A file is said to carry something, and demonstrating it to a client, a platform or a regulator requires going through the vendor, which is a process with a timetable and an interest attached.
For most practical purposes that returns a publisher to the visible layer, which is the one they can inspect themselves. That is a recurring conclusion across this register and the reason the visible-mark columns carry most of its content.
Nothing on this page is a vendor statement; the values it helps read are on the support table, with the page and the date each one was read from. See also the user toggle column, source documents. Nearby terms: metered access, two-route product, download route.