Art. 23(2)

Primary mapping to Art. 23(1) establishes that ransomware against ground or mission-control infrastructure is a significant incident triggering the reporting obligation. Art. 23(2) addresses the timing dimension (notification without undue delay after becoming aware), which automatically applies once Art. 23(1) is triggered.

Primary mapping to Art. 23(1) treats wiper malware as a significant incident triggering reporting. Art. 23(2) addresses the timing requirement (without undue delay after becoming aware), automatic on Art. 23(1).

Primary mapping to Art. 23(1) treats resource-flooding (DoS-class) attacks as a significant incident. Art. 23(2) timing applies once that obligation is triggered.

Primary mapping to Art. 23(1) treats compromise of the mission ground system as a significant incident. Art. 23(2) timing (without undue delay after awareness) applies automatically.

Primary mapping to Art. 23(1) treats compromise of partner infrastructure as a significant incident. Art. 23(2) timing applies once Art. 23(1) is triggered.

Primary mapping to Art. 23(1) treats successful initial access into the ground system as a significant incident. Art. 23(2) timing applies once Art. 23(1) is triggered.

Primary mapping to Art. 23(1) treats malicious commanding via a valid GS as a significant incident. Art. 23(2) timing applies once Art. 23(1) is triggered.

Primary mapping to Art. 23(1) treats deception/misdirection at impact scale as a significant incident. Art. 23(2) timing applies once Art. 23(1) is triggered.

Primary mapping to Art. 23(1) treats disruption as a significant incident. Art. 23(2) timing applies once Art. 23(1) is triggered.

Primary mapping to Art. 23(1) treats denial as a significant incident. Art. 23(2) timing applies once Art. 23(1) is triggered.

Primary mapping to Art. 23(1) treats degradation as a significant incident. Art. 23(2) timing applies once Art. 23(1) is triggered.

Primary mapping to Art. 23(1) treats destruction as a significant incident. Art. 23(2) timing applies once Art. 23(1) is triggered.

Primary mapping to Art. 23(1) treats theft of mission data as a significant incident. Art. 23(2) timing applies once Art. 23(1) is triggered.

Primary mapping to Art. 23(1) treats constellation-hopping via crosslink as a significant incident. Art. 23(2) timing applies once Art. 23(1) is triggered.

Primary mapping to Art. 23(1) treats persistent attacker presence in the ground system as a significant incident. Art. 23(2) timing applies once Art. 23(1) is triggered.

Primary mapping to Art. 23(1) treats compromise of the entity's infrastructure (used as resource staging) as a significant incident. Art. 23(2) timing applies once Art. 23(1) is triggered.

Primary mapping to Art. 23(1) treats compromise of the mission-operated GS (as adversary infrastructure) as a significant incident. Art. 23(2) timing applies once Art. 23(1) is triggered.

Primary mapping to Art. 23(1) treats compromise of a third-party GS as a significant incident. Art. 23(2) timing applies once Art. 23(1) is triggered.