Art. 76(6)

Hardware-design-flaw exploitation (primary: Art. 88(1)) requires periodic effectiveness assessment per 76(6) of test-coverage against design-flaw classes.

Code-flaw mitigation (primary: Art. 88(1) testing programme) needs the effectiveness-assessment policy 76(6) requires — periodic verification that risk-management measures actually catch FSW defects.

FSW testing (primary: Art. 88(1)) is one input to the effectiveness-assessment-policy 76(6) requires — assessing whether testing actually surfaces flaws.

OS-layer testing efficacy (primary: Art. 88(1)) is reviewed under the effectiveness-assessment policy 76(6) requires.

Side-channel testing efficacy (primary: Art. 88(1)) requires effectiveness assessment per 76(6) — periodic verification that operator measurement equipment matches adversary capabilities.

Dev-environment testing (primary: Art. 88(1)) effectiveness needs the assessment policy 76(6) requires — ensuring dev-pipeline integrity checks remain effective.

Hypervisor-escape testing (primary: Art. 88(1)) — separation-kernel boundary fuzzing — is reviewed under 76(6)'s effectiveness-assessment-policy.

Backdoor-detection efficacy (primary: Art. 88(1) TLPT) is reviewed under 76(6)'s effectiveness-assessment-policy obligation.

Hardware-backdoor detection (primary: Art. 88(1)) requires effectiveness assessment per 76(6) — given the difficulty of test-coverage validation in hardware backdoor scenarios.

Software-backdoor detection (primary: Art. 88(1)) needs ongoing effectiveness assessment per 76(6).