SNIP_CLASSIC_IDSM_SECTION_7_8_2_Propagation_of_QSEvs_IdsR_Sink

7.8.2 Propagation of QSEvs: IdsR Sink [SWS_IdsM_01202] ⌈The IdsM shall provide the functionality for forwarding qualified on-board security events QSEvs to other ECUs via the PduR module.⌋ Note: The transmission of QSEv to the backend (for use cases like off-board analysis) is supported by the IdsM concept but performed by another component (IdsR). Consult the [4, Specification of Intrusion Detection System Protocol] for the different message formats available for the transport of the event frame. [SWS_IdsM_01203] QSEv transmission Upstream requirements: RS_Ids_00510 ⌈The IdsM shall be able to use the sink IdsR for the configured events. The IdsMSinkIdsR indicates that the corresponding QSEv shall be sent via PduR in a IDS Message to the communication network.⌋ [SWS_IdsM_01209] Enable/Disable QSEv Transmission ⌈IdsM shall support enabling and disabling the forwarding of qualified security events to the sink IdsR during run-time over the API IdsM_TransmissionSetState .⌋ [SWS_IdsM_01210] Transmission State ⌈The IdsM shall be informed by the BswM module about the transmission state with the callback service IdsM_TransmissionSetState. This information shall be used when a QSEv is generated for transmission.⌋ Manager [SWS_IdsM_01211] Transmission ON ⌈IdsM shall forward QSEvs to the sink IdsR only when the transmission is enabled IDSM_TRANSMISSION_STATE_ON.⌋