“Mydatalife Security”

Apply enough time, talent and machine power to any computers security protection and it is probable that even the most extreme care could never be absolutely good enough. Thus no organisation can do more than to embrace all currently known technology to protect the data environment.

However in establishing the structure for mydatalife we do have some aspects going for us that will limit intrusion, the first being that every individual account is a unique silo on its own. Where a corporate holds data, on its customers for instance, then once the server is penetrated then multiple files will be accessible. In this case only one single record can be read at a time, meaning that it is both very much harder and far less rewarding for an attacker.

The second advantage is that we always absolutely know who has the right to access the file, meaning that anybody else can be blocked by default. Indeed we can build a security alert around any attempted access, meaning we can take positive protective action, close ranks until we know where the attack came from.

Thirdly we can invite customers to enhance their protection through the various possible uses of multi factor authentication, perhaps adopting different levels throughout their file, so that photos (perhaps) have lesser protection than commercially sensitive documents. Thus customers will have access to their own security controls within their account.

Of course encryption is a standard defence; however note please that within the design of the file architecture (see ) we had to consider making certain aspects searchable. Thus we allow customers to apply encryption overall, but with specific exceptions within which they can place information that can be found via an authorised and controlled search. Clearly no confidential information should ever appear in an unencrypted field, that being entirely within the owner’s control. Where a consent connector has privileged access to a specific field it also has a decryption capability, with every access being logged and recorded, so once again (using management by exception) we can create triggers for any unexpected activity.

The final specific aspect to a mydatalife file is that we would discourage customers from using it for the storage of bulk data that does not have a security restriction. Examples would be music files, films, photographs, books etc. Subject to your being happy to pay the charges we apply for extensive storage, then you may do so, but the specialist provider probably has much more useful control features than we purport to supply. For the purpose of control of your digital life you may, of course, store a link to your chosen source.

You are the owner and controller of the file, and any breach threat will come to you in the first instance. As the system architects we will be constantly seeking to apply any fresh security thinking, and once again you will be involved in that, applying it as you see fit.