Art. 88(1)

88(1)'s testing programme can include adversarial-input testing on monitoring models — surfacing clean-label backdoors and biased-sampling artifacts.

Rootkit detection requires offline integrity attestation, image hashing, and kernel-introspection testing — within 88(1)'s testing programme scope.

88(1)'s testing programme and 88(3)'s Threat Led Penetration Testing can include behavioral testing across the orbital trajectory — surfacing geofenced triggers that fire only at specific positions or times.

88(1)'s testing programme can include hardware-design fuzzing, scan-chain testing, and FPGA partial-reconfig validation — surfacing the design-flaw classes EX-0005.01 enumerates.

88(1)'s testing programme, with 88(3)'s 3-yearly Threat Led Penetration Testing, is the operator's discipline that surfaces software defects before adversaries find them.

88(1)'s testing programme, with 88(3)'s 3-yearly TLPT, is the operator discipline that surfaces FSW parser, command-handler, and table-loader defects before adversaries find them.

OS-level testing (kernel fuzzing, syscall fuzzing, privilege boundary validation) is part of the testing programme 88(1) requires.

88(1)'s testing programme, including TLPT, validates that legitimate update/file-transfer/maintenance pathways do not accept malicious payloads.

Regular tests under 88(1) — including out-of-band integrity attestation and offline image verification — surface rootkit-induced discrepancies that runtime telemetry alone hides.

88(1)'s testing programme can include adversarial-input testing and model-validation against poisoned-corpus scenarios — surfacing clean-label backdoors and decision-boundary skew.

88(1)'s testing programme can include side-channel and fault-injection testing during integration — surfacing leakage and glitch susceptibility.

88(1)'s testing programme can include side-channel and fault-injection testing — surfacing leakage and glitch susceptibility in operator products.

88(1)'s testing programme should extend to test harnesses, simulators, and flight builds — verifying that compromised dev artifacts cannot reach production silently.

88(1)'s testing programme obligation can include supply-chain integrity checks (e.g., verification of dependency provenance, signed-build validation) that detect dependency-confusion or build-poisoning attempts before deployment.

Hypervisor/separation-kernel boundary testing — fuzzing of message ports, IOMMU validation — is within 88(1)'s testing programme scope.

Backdoors are detected through testing — 88(1)'s testing programme, including 88(3)'s 3-yearly Threat Led Penetration Testing, is the operator discipline that surfaces hidden command handlers and undocumented service modes.

Hardware-backdoor detection requires test/scan-chain validation, fuse-state checks, and reverse engineering — within 88(1)'s testing programme scope.

Software backdoors hide in code paths the testing programme under 88(1) is meant to surface — code review, fuzzing, and TLPT under 88(3) are the operator-side disciplines.

Reconnaissance of the operator's testing programme (static analyzers, fuzzers, formal-methods coverage) discloses test gaps; 88(1)'s testing programme obligation places operator responsibility on what is tested and how.

88(1)'s testing programme obligation, including (88)(3)'s 3-yearly Threat Led Penetration Testing, validates that the operator's products are tested against known-vulnerability catalogs.