.net runtimes and ASP.net Frameworks, is there any good rules of thumb to keeping them updated?

Even with about 30 years in the industry, I whole heartedly admit I have no idea what all the different .net runtimes and ASP.net frameworks are doing on any given machine or how to keep them updated/secure. We usually feel confident about same version updates but there's sooo many different ones and different ones seem to be deprecated and versions are kinda all over the place with name changes etc...

Our vuln management is littered with a bunch of servers …

asp cybersecurity doing frameworks good idea industry machine .net rules version