I was visiting a web page of some invoicing / time tracking web-app and saw this text in their FAQ:
“In the very unlikely event of a security incident, we’d be in more peril of someone duplicating our application and attempting to resell it than you losing your data or someone stealing your identity.”
Eeeee… wrong answer!! Totally!!!
Well, the service seems very solid otherwise so maybe it’s just a case of not well thought out PR.
Security is a very complex subject..
You can never simply cover all the corners and go to sleep. There are no absolutes. Linear/feed forward thinking of do/pay more/better to get more in not very effective. It’s about being smart, creating a system that will by design minimize certain problems (better than other problems).
So although you really want none of security issues to happen, you must get a very clear priority of things you want to prevent.
At cebelca.biz which is a local small business application the priorities are (from most important to least, number is the level of importance from 100 to 0):
- 100
- A hacker gets to data of our users.
- 95
- A hacker destroys the data of our users.
- 35
- A hacker for noticeable period disables our service.
- 20
- A hacker gets the source code of our application.
To me, our users data is of top priority, they trusted us with their data. And our source code… meh… capable developers want to code and design their solutions according to their ideas, not copy someone else’s stuff and get a outdated copy of something that already exists.
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=c30d3bea-9bca-417f-bae4-7f9b5650a22f)

![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=0d0519fb-c8f7-4797-9429-f3edf9818a8a)


![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=84a41baa-60f1-4eeb-b0cd-a57b9760a341)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=9e35d757-a403-4622-a2a8-e83e128f467f)
