Why you should isolate un-patchable, end-of-life software

in acrac •  5 years ago 


And another blog post from the recent past I outlined why a patch policy and an update policy maybe critical for survival of an organization.

On rare occasions, and actually more often than desirable critical software upon which the organization relies to operate cannot be updated or patched simply because this piece of software has reached its end-of-life.

Normally, I T staff will start running around like decapitated chicken, and try to find alternative Solutions to this very important problem.

If the software in question does not require Internet access it is possible to run it in virtualized environment's so that it does not endanger rest of the system that is connected to the network and the Internet.

If you're willing to take a bit of risk you may consider limited Internet access if the software requires it.

https://lars-hilse.de/lhx18/2019/10/why-you-should-isolate-un-patchable-end-of-life-software/
Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!
Sort Order:  

Congratulations @larshilse! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) :

You received more than 10 upvotes. Your next target is to reach 50 upvotes.

You can view your badges on your Steem Board and compare to others on the Steem Ranking
If you no longer want to receive notifications, reply to this comment with the word STOP

Vote for @Steemitboard as a witness to get one more award and increased upvotes!