Trust TRU-014

Collector identity

Collector identity explains the control, evidence and limitation a reviewer should use when evaluating Domain Signals. Trust comes from showing how a conclusion was reached, where the boundary sits and what the evidence cannot establish.

Bounded, non-exploitative Authorised external assessment.

Bounded evidence. Explicit responsibility. No hidden inference.

The useful answer

Collector identity explains the control, evidence and limitation a reviewer should use when evaluating Domain Signals.

Collector identity explains the control, evidence and limitation a reviewer should use when evaluating Domain Signals. Collector identity explains the control, evidence and limitation a reviewer should use when evaluating Domain Signals. Trust comes from showing how a conclusion was reached, where the boundary sits and what the evidence cannot establish.

Route-specific context

The decision this page is designed to support

01
Review audience
Network operator, security reviewer
02
Control objective
Identify legitimate Domain Signals observation traffic. Collector identity explains the control, evidence and limitation a reviewer should use when evaluating Domain Signals.
03
Proof boundary
The exact target, source, observation time, responsibility and evidence state remain available to entitled readers. Evidence basis: Collector policy and protocol adapter tests.

A deliberate path

From permission to retained evidence

  1. 01

    Review the governed control described by collector identity.

  2. 02

    Trace each statement to its stated evidence basis, owner and review date.

  3. 03

    Carry the published limitation into procurement, assurance or technical interpretation rather than treating silence as approval.

Evidence before assertion

What the product can support

Every governed capability ends with an explicit disposition. Current observations can support a strength or an action; missing, stale or unavailable evidence remains an unknown and cannot become reassurance. The exact target, source, observation time, responsibility and evidence state remain available to entitled readers.

Supported capability

The assessment uses direct protocol observations and passive intelligence but stops before exploitation, authentication attempts, brute force and fuzzing.

Collector policy and protocol adapter tests

Qualified statement

The public collector identity and opt-out process describe how authorised observations are made.

Publish scanner identity, fixed egress, security.txt and tested opt-out workflow

Direct answers

Questions a careful reader should ask

What does Collector identity establish?

Collector identity explains the control, evidence and limitation a reviewer should use when evaluating Domain Signals. It establishes only what the governed evidence supports.

What does it not establish?

It does not prove complete organisational security, exploitability, breach likelihood or the absence of unobserved weaknesses.

How can I verify the conclusion?

Use the linked evidence or capability record to inspect source, observation time, target, responsibility and the condition required for closure.