That notification is from an administrative monitor.
Administrative monitor visibility is controlled from the “Manage Jenkins” / “System” page. On that page, there is a button “Administrative monitors” that expands to show the monitors with their enabled and disabled state.
I confirmed if N notifications are “dismissed” then at the http://localhost:8080/manage/configure page in the Administrative monitors section which has the Administrative monitors select box appears the items unchecked.
Therefore in my case as an experiment I applied two “dismess” to
Building on the built-in node can be a security issue. You should set up distributed builds. See the documentation.
Jenkins can enforce Content Security Policy (CSP). CSP tells web browsers what they are allowed to do while rendering a web page. This limits or even eliminates the impact of vulnerabilities like cross-site scripting (XSS). CSP is disabled by default for backward compatibility, but it is recommended to enable it, if possible.
Where each one is matched with the following items respectively:
Built-in Node Without Agents Executors Configured Monitor
Recommend Content Security Policy
If they are re-checked then the two originals notifications appear again