Between the 72-hour notification and the final report, the CSIRT or competent authority may request an intermediate report on relevant status updates, and the entity has to be able to produce one. There is no fixed deadline attached, which makes the obligation about readiness rather than timing: the entity needs a maintained incident record from which a status update can be drawn on short notice, and a named point of contact that the authority can actually reach while the incident is running. Entities that manage incidents in chat threads and calls, with the written record assembled afterwards, are the ones that struggle here, because there is nothing to report from until the incident is over.
This control maps to 7 controls across 6 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
NIS2 Directive Art.23.4.c is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIS2 Directive your existing evidence covers. Hold DORA and 17 of 28 NIS2 Directive controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the DORA pair alone.
The graph holds this control, the 7 it maps to, and the evidence behind each claim, over MCP and REST.