Styxis
Company
Knowledge

Separate CRA reporting roles and effective dates before applying one rule

A CRA reporting contract should distinguish actor role, effective date, awareness time and reporting stage.

One interface does not mean one obligation

The tempting shortcut in security reporting is to apply one clock and one set of required fields to every row. Different actor roles make that shortcut unreliable. A complete-looking table can still describe the wrong reporting population. Truthound belongs after the organisation has established its role: it can check the resulting input contract, rather than decide who has a legal obligation.

Launch and applicability are different

ENISA's Single Reporting Platform FAQ identifies September 11, 2026 as the platform's operational start. The guidance updated October 15, 2026 distinguishes manufacturers from open-source software stewards, whose relevant obligations are described as applying from December 11, 2027. Access to an operational reporting interface does not itself establish the same obligations for every actor.

Start with the actor register

A preparation register should therefore include more than product and organisation identifiers. Record the actor role and who confirmed it. Keep incident type separate from the reporting stage, such as an initial notification or follow-up. Replacing an unknown role with a convenient default makes later stage-specific checks misleading.

Do not collapse the clocks

Awareness, internal confirmation and submission are different events. Copying submission time into an awareness field can produce a plausible sequence while erasing the actual chronology. Preserve timezone and correction references. The security and reporting owners need to agree what each clock means before the software checks their order.

A narrow validation boundary

Truthound Core Python SDK 3.3.4, operating on a prepared Polars table, includes ConditionalExpressionValidator, which applies a caller-defined then expression to rows matching a supplied condition. After roles and stages are established, it can express required evidence for a particular stage. DateOrderValidator can compare two date fields. Neither interprets a statutory starting point; date meaning, null handling and timezone policy must remain explicit.

An existing predicate is also an option

Pandera 0.35.0 provides a reasonable alternative when a team already maintains these predicates in its pandas checks. Compare the outcomes for manufacturer and steward rows, initial and follow-up stages, and missing timestamps. Until both paths are evaluated against the same prepared examples, their documentation offers no basis for claiming one is more complete.

A role belongs to the reporting context

An organisation's name is not enough to fix its role across products and reporting contexts. Keep the role determination attached to the relevant product and submission context. When another party takes responsibility for a follow-up, do not silently copy the earlier actor classification into the new row.

Who owns a correction?

Later evidence may change the original classification. Attach a corrected version and its owner instead of silently replacing the earlier record. A failed contract also does not mean an attack occurred. An unresolved role, an entry error and a change in incident facts need separate exception routes.

Pause before the transition

Before switching contracts, try rows with no role, a date before the relevant applicability period, and a submission time without an awareness time. Confirm that each is held for the appropriate owner. Keep the currently applicable contract beside the future version. A reporting workflow becomes more dependable when this boundary is understandable before submission is automated.

Conditions

Apply checks after the responsible owner confirms actor role, reporting stage and timestamp meanings.

Alternatives

Keep existing Pandera 0.35.0 pandas predicates when they implement the required stage-specific exception handling.

Limitations

  • Valid date ordering and predicates do not determine legal applicability or a statutory starting point.

Evidence

Event checked
Subject checked
Modified