Some of you will remember the 1970s film Marathon Man which starred Dustin Hoffman. The most famous scene involves him being asked over and over ‘is it safe?’, not having a clue what his interrogators are after his answers range from exclaiming: he doesn’t know what they are talking about to a series of positive and negative confirmations. All along he is being tortured through dentistry.
If you are involved in information security, privacy, and/or, compliance, you will no doubt have been involved in evaluating the security, privacy, and compliance of software. Sometimes called a risk assessment and/or privacy impact assessment, hopefully taking a risk-based perspective in the context of the ask. The merry dance of trying to discover if the software is secure from a whole host of angles, whilst the requestor is waiting agitated in the wings proclaiming that ‘big company acme already uses this, surely it is fine…’. A kind of torture where the people you are asking the questions are not always 100% sure they know or want to share the answers, or the questions.
This is only getting harder, as software increasingly uses AI (well, machine learning, well, algorithms) and the speed of adoption is increasing. Bear in mind people expect a SaaS (Software as a Service) solution to be spun up in days and even hours. Or, a new software app to be developed in quick order to follow a marketing campaign timeline. And so on. And why not chuck in for good measure increased scrutiny around compliance and the law, especially so in financial and healthcare, which reflects in tougher contractual obligations.
There is a kind of value in inefficiency here, just like the law. In a way the slowing down of a project creates an opportunity to think. Scary to think, for me anyway, that to fix this people are seriously implementing AI law software to replace judges.
Healthcare is waking up to the fact that we are more than a body and equal attention is being paid to mental health issues, at least it appears so. The scene in Marathon Man is equally psychologically and physically disturbing. Likewise, I think we should be asking not only if the physical devices we use will not harm us physically, but that the software we use will not harm us mentally.
I wonder if we looked at all this a different way and just said ‘is it safe?’ and nothing further. One question.
I had a go at what ‘Is it safe?’ means: the software itself and its surrounding support network is technically secure so a flaw within it cannot unreasonably increase the risk to you physically or mentally. Not quite right, but a start.
When you think that using Twitter could end up with someone in the background using a tool called ‘Creepy’ to track your movements, based on your tweets as you travel, would a company like them say ‘yes, it is safe’?
Of course, we all know nothing is 100% secure, or safe, but next time you are evaluating the security of a system, just ask ‘is it safe?’ and see what response you get.

Comments
Post a Comment