Back to matrix

F21-CG: Yes

Rationale

Pinned ION BpDelivery associates bundleSourceEid, primaryIntegrityVerified and payloadAuthVerified with the delivered ADU. Receiver policy selection includes the bundle source; successful BIB target verification sets the corresponding flags. With exact-origin policies, distinct sender/receiver-only keys and primary-plus-payload coverage, the application may treat the source as authenticated only when both flags are true. This supplies final-peer provenance without another application authentication exchange; unflagged delivery is not authenticated.

Assessment method

Independent scope review of the pinned API witness used in Secure DTN; no inherited verdict or experiment

Source context

Pinned native BP delivery and BPSec receiver-policy code

Outstanding qualification

Pin complete security/convergence-layer integration and exercise valid, missing, corrupted, wrong-key and source-substitution bundles through bp_receive. Verify both flags and source/ADU association after restart; do not treat waypoint-only keys, one flag, or an address alone as final-peer proof. This is shared-key authentication, not nonrepudiation or replay protection.

Public sources

Editorial evidence references

The following identifiers refer to research records not included in this public package; they are not public links.