What the advisory says

Security updates often affect more than the server listed in a public asset register. Reverse proxies can run in a container, a Kubernetes ingress controller, a cloud appliance, a hosting platform or a vendor product. Separate teams may own these copies, and each can have its own release schedule.

An inventory should connect the public hostname to the component that terminates TLS, the package or image, its owner and the route to update it. Include staging, internal gateways and disaster-recovery environments. Record which protocol and modules are enabled because some advisories apply only to specific features.

Checks for your systems

Start with DNS and cloud load balancer records, then compare them with host, container, orchestration and supplier inventories. Ask each service owner to confirm the running version and package source. Mark unknown ownership as work to resolve rather than assuming an asset is not in use.

After an update, verify the running process or image digest, not only the configuration repository. Check traffic health, TLS, upstream routes and logs. Keep the inventory current through change management so the next security advisory can be mapped to real systems quickly.