All techniques
EX-0012.04
ST0004Execution
sub-technique

App/Subscriber Tables

Parent: EX-0012

Description

In publish/subscribe flight frameworks, applications and subsystems register interest in specific message classes via subscriber (or application) tables. These tables map message IDs/topics to subscribers, define delivery pipes/queues, and often include filters, priorities, and rate limits. By altering these mappings, an adversary can quietly reshape information flow: critical consumers stop receiving health or sensor messages; non-critical tasks get flooded; handlers are rebound so an opcode or message ID reaches the wrong task; or duplicates create feedback loops that consume bandwidth and CPU. Because subscription state is usually read at init or refreshed on command, subtle edits can persist across reboots or take effect at predictable times. Similar effects appear in legacy MIL-STD-1553 deployments by modifying Remote Terminal (RT), subaddress, or mode-code configurations so that messages are misaddressed or dropped at the bus interface. The net result is control-by-misdirection: the software still “works,” but the right data no longer reaches the right recipient at the right time.

Mappings

EU regulation articles

  • craAnnex I, Part I, (2)(f)
    addresses
    high
    derived

    Integrity protection on subscriber tables resists modification of message-ID-to-subscriber mappings.

  • eu-space-actArt. 84(2)
    addresses
    moderate
    direct

    App/subscriber tables in pub/sub flight frameworks are network-and-information-system state under 84(2) — Annex VII point 5.1 includes integrity protection on subscription bindings.

  • nis2Art. 21(2)(i)
    addresses
    moderate
    direct

    Subscriber/application tables and 1553 RT/subaddress configurations are access-controlled configuration assets; Art. 21(2)(i)'s access-control + asset-management obligation governs the edits that reshape who hears what and when.

  • nis2-implAnnex 6.3.1
    addresses
    moderate
    derived

    Configuration-management obligations cover application and subscriber tables as part of the documented configuration baseline whose deviations must be detected and reviewed.

  • nis2-implAnnex 6.4.1
    addresses
    moderate
    derived

    App/subscriber table modifications are configuration changes; change-management procedures govern release, modification and emergency edits to these tables.

ENISA controls

  • Application/subscriber tables are configuration items under configuration management; modifications outside the baseline are flagged.

  • Integrity checking on tables and configuration data detects unauthorised modifications to subscriber lists.

Cross-reference controls

SPARTA countermeasures

Cite as SafeMode Space, EX-0012.04 (SPARTA v3.2).

Built 2026-07-25 from 216 techniques, 334 regulation articles, 125 ENISA controls, 2,610 framework controls, and 90 countermeasures.