# We invited a direct competitor into Security Hub Extended. Here’s why.

> Quelle: AWS Security Blog — https://aws.amazon.com/blogs/security/we-invited-a-direct-competitor-into-security-hub-extended-heres-why/

## Maßnahmen

- [ ] Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
- [ ] Originalquelle / Hersteller-Advisory lesen: https://aws.amazon.com/blogs/security/we-invited-a-direct-competitor-into-security-hub-extended-heres-why/
- [ ] Verfügbaren Patch oder Workaround einspielen und dokumentieren.