The Thinking Person's Guide to the Cloud, Part 3a (a digression)
(Part 1, Part 2)
Before we dive into specific patterns and practices for building countermeasures in the Cloud, let's look at some design goals for building countermeasures.
What we have is a design problem
and its not just that we need stronger mechanisms
they must also be safe
And they have to be USEFUL and UNDERSTANDABLE by real people - developers, architects, QA and so on.
Our security designs should lead people in the RIGHT direction
Help them solve problems
and its not just that we need stronger mechanisms
they must also be safe
And they have to be USEFUL and UNDERSTANDABLE by real people - developers, architects, QA and so on.
Our security designs should lead people in the RIGHT direction
Help them solve problems
The mechanism should not create new/worse problems
Just because the mechanism WORKS doesn't mean it solves our problem. Look at the bike lock and think about SSL. SSL works great just like the bike lock, what it doesn't do is protect the asset.
...but what kind of security services should we build? We'll look at this in Part 3b
**
Reference
* Failblog
Comments