Would you think this was a bit sus?
08 August 2012, 10:14 AM
#31
Scooby Regular
Join Date: Mar 2011
Posts: 546
Likes: 0
Received 0 Likes
on
0 Posts
Not knowing what your company does, this is something to consider.
Storing any sort of customer details on your system means that you have to comply to a lot of data protection laws - having your system unprotected could mean you are breaking some/many of them.
Scenario: systems gets hacked (very simple if it's just a load of machines plugged into various hubs/home routers), customer details stolen, intrusion traced back to your machines, find out what data was stored and how, now you're to blame for what could be anything from ID fraud, to £££££££'s being stolen.
Sounds extreme, but it happens! Get your security sorted!
Scott.
(Studying computer networks & security degree, and also Certified Ethical Hacker)
Storing any sort of customer details on your system means that you have to comply to a lot of data protection laws - having your system unprotected could mean you are breaking some/many of them.
Scenario: systems gets hacked (very simple if it's just a load of machines plugged into various hubs/home routers), customer details stolen, intrusion traced back to your machines, find out what data was stored and how, now you're to blame for what could be anything from ID fraud, to £££££££'s being stolen.
Sounds extreme, but it happens! Get your security sorted!
Scott.
(Studying computer networks & security degree, and also Certified Ethical Hacker)
This is all true.
additionally, if you have employee data on there, such as payroll details, addresses etc, then you have a statutory obligation to protect that personally identifiable information as well...
Thread
Thread Starter
Forum
Replies
Last Post