Sage 100

As a follow up to the crypto virus rearing its ugly head again, any ideas on protecting the Sage shared directory? My client yesterday that was hit is questioning why the Sage shared directory was affected but not other shares.

Great question. is it due to the sage requirement that users have full control?

Or due to the person who originally got the virus only working on Sage on the network at the time?

I'm not sure. The client is in the financial services industry and have a locked down network to say the least. They are asking if it is a Sage vulnerability and clearly Sage isn't going to answer that question. I don't really know how to explain why other shares weren't affected.

Perhaps they should try to pinpoint the entry point to ascertain WHAT was going on at the time and also take a look at THEIR virus scanning software to determine why it is ANYWHERE on their network??? Good luck with this finger pointing exercise.