One of our clients subcontracts to an organisation that places a very high emphasis on security. To take their laptops onto that organisation’s site, they have to have a blank login account with virtually none of their data on the machine. The only application on the laptop is ours. It contains only the information they need for the site visit. When they return to their office, it downloads the information to the server and wipes everything about the site visit off the laptop itself.
Another project involved confidential interviews. While the interviews were recorded anonymously on netbook computers, we also ensured that during the subsequent download process they were sufficiently randomised that nobody could deduce the interviewer by working out which interview on which machine was which. Nor could anybody see the answers after the interview was completed because it was vital to record the interviewee’s anonymity.
On another, smaller legacy site we were called in to reconfigure a system to work on a server instead of a local machine. Unfortunately, we weren’t called in until an ex-employee had already left with a copy of the system, including the client list and about 10 years’ worth of sales records on a memory stick…
These are very specific and diverse cases that highlight the necessity of understanding just what security really means to you. Interestingly, not one of them involves credit card fraud, hackers, firewall breaches, encryption cracking or any other things security experts will tell you that you need to guard against.
That’s not to say you don’t need all these things: you do. But as a business person, you shouldn’t really know too much about the technical side of security; it is a highly specialised field best left to the experts. What you do need to understand is how much security and would sort of security is relevant to your business. You need to understand your needs: what are the real threats to your business and what is the most effective way to deal with them.
For instance, in the memory stick case: the need is to restrict access to the sensitive data without otherwise encumbering staff. It is quite easy for your IT people to implement a set of restrictions that prevent anything being copied onto a memory stick. However, this can be somewhat restrictive in practice, as there are many perfectly valid reasons for staff to use memory sticks. It is more appropriate to locate the sensitive files in a secure location on a server so that staff can access them for bona fide purposes but cannot copy them.
How about access to data within an application? Do you let your staff have access to your accounting program? Have you restricted their access by use of accounts and passwords so they can only use the parts they need to use? Are they properly trained? Can they export data? Or edit it, or delete it? Are you sure?
A regular request for us is to build a front-end to an accounting system that lets staff perform their various functions, but completely obviates the need for non-admin staff to have any access to the accounting program at all. This sort of thing becomes much more relevant as mobile computing starts to become a mainstream event. It is not just a case of preventing people from hacking in to your systems; there is increasingly a very real issue as to knowing who is actually at the keyboard at the other end and controlling just what they are doing offsite. Even for the same staff member, it can be a very real consideration to decide that what they can do ‘in-house’ is not the same as what they can do while ‘on the road’. And if you reach that conclusion, then you are going to have to decide how to implement it.
One last thought: how do you know your IT people are doing the business re security if you can’t be expected to understand it all? In short: peer review. Periodically, get one of their competitors in to have a look at your system. They will be pitching for your business, so you may have to take it with a pinch of salt, but they may well uncover some interesting issues.