Archives
- ► 2012 (8)
- ► 2011 (157)
- ► 2010 (174)
- ► 2009 (12)
Which topics would you like us to cover more?
Latest comments
- How to reset you Kindle
3, eve...
Thanks for this article and the related "Inside th...
By H K - How to reset you Kindle
3, eve...
How do you drain power on the board? I dont have r...
By Grace - How to reset you Kindle
3, eve...
You're welcome!
By Bas - How to reset you Kindle
3, eve...
Thanks man....removing the battery worked like a c...
By DaveMan - nHapi
example
Hi Slypete, Thank you for your comment. This way w...
By Bas - nHapi
example
Hello, Employing .Net dynamics, one can implement ...
By slypete - Implementing MLLP in C#
Hi Mayura, I'm not sure I understand your question...
By Bas - Implementing MLLP in C#
I have used SSL stream to secure the MLLP transact...
By Mayura
Latest tweets
| Security is a quality attribute |
| Written by Division by Zero |
| Monday, 12 April 2010 09:20 |
|
On 25 march Valissa commented on my article "The security dilemma revisited". The comment is: "Ok let's think aloud. If I summarize this it would be: "Customers don't want security, they want quality". This is true. Customers (our business) don't want security. Think about it. If you buy a house, you don't want locks. Locks limit your freedom to freely walk in and out of your house and they are in the way if your door is locked and you carry bags in both of your hands. What you want if live in this house comfortably. What you also want is to let some people in to your house and other people, especially the ones you don't know and in the middle of the night, out. So you put up with the disadvantages of locks, because locks give us more comfort than discomfort. Reading the ISO 9126 standard for software quality, security is a quality attribute under functionality. Our job is to implement security like this: it has to give more comfort than discomfort. Only that way user will put up with the security functionality. As said: customers don't want security just as we (software specialists) don't want locks on our doors. But what do customers want? We often (and should!) base our security measures on CIA: Confidentiality, Integrity and Availability. Herein lies what a customer want. How well protected must the data be and what is the risk I'm willing to take. How important is it to me that no-one is able to tamper the data or what level of tampering isn't that bad? And when and where should the data be available to me and to my clients and what is the risk when it's not available? The conclusion is that if you want to deliver a quality software product, security must be an aspect of this quality. Tags:
|
If the human brain was simple enough for us to understand we'd be so simple we couldn't understand. - Unknown



thinking from the perspective of a customer I ask myself why should
I need security, what are the benefits for me?
