Nope

I wouldn’t do anything. I’d bring the list of issues and servers to stakeholders and business owners and ask them what’s important to them, along with any pros/cons/technical challenges with implementing each item.

Once you have a prioritized list from them, you have two things:

1. A list of improvements you made as you make them, in case anything backfires
2. Written proof that you told them about these things in case anything happens as a result of not implementing them

Until then, it’s a meaningless bunch suggestions.

Remember: you don't work for the Microsoft vulnerability report. It doesn't pay you to do anything.

Nope

I wouldn’t do anything. I’d bring the list of issues and servers to stakeholders and business owners and ask them what’s important to them, along with any pros/cons/technical challenges with implementing each item.

Once you have a prioritized list from them, you have a few things:

1. A list of improvements you made as you make them
2. Approval for all changes, in case anything backfires
3. Written proof that you told them about these things, in case anything happens as a result of not implementing them

Until then, it’s a meaningless bunch suggestions.

Remember: you don't work for the Microsoft vulnerability report. It doesn't pay you to do anything.

Nope

I wouldn’t do anything. I’d bring the list of issues and servers to stakeholders and business owners and ask them what’s important to them, along with any pros/cons/technical challenges with implementing each item.

Once you have a prioritized list from them, you have two things:

1. A list of improvements you made as you make them, in case anything backfires
2. Written proof that you told them about these things in case anything happens as a result of not implementing them

Until then, it’s a meaningless bunch suggestions.

Nope

I wouldn’t do anything. I’d bring the list of issues and servers to stakeholders and business owners and ask them what’s important to them, along with any pros/cons/technical challenges with implementing each item.

Once you have a prioritized list from them, you have two things:

1. A list of improvements you made as you make them, in case anything backfires
2. Written proof that you told them about these things in case anything happens as a result of not implementing them

Until then, it’s a meaningless bunch suggestions.

Remember: you don't work for the Microsoft vulnerability report. It doesn't pay you to do anything.