|
This diagram shows the process of vulnerability alert propagation within our system.
Step 1: The process initiates when a security expert identifies a new vulnerability affecting a software component, in this case, 'AAA'. The expert informs this vulnerability to the system.
Step 2: The service then requests DID document of 'AAA' from the DID resolver.
Step 3: Once the DID document is retrieved, the service discovers the address of SC_AAA.
Step 4: The service notifies SCAAA of the newly discovered vulnerability and triggers the creation and propagation of an alert.
Step 5: SCAAA emits an alert event containing vulnerability information. The components with a direct dependency on AAA listen to this event, and then generate and emit their own alert events. This process continues recursively, propagating the alerts to all components that have transitive dependencies with AAA.
Step 6: Participants who subscribed to receive events about XXX receive the alert event on XXX, becoming aware of the vulnerability in AAA that they depend on, and can promptly respond.
|