Give me an example on how I could apply the Strong Link - Weak Link principle in designing a security component for a piece of software. Is there such a concept of "weak" modules in software security, where in case of an attack these will deliberately fail first, and determine the impossibility of the attacker to access and compromise any other, more sensitive data?
+1
A:
One thing that can happen accidentally is to fail (as DoS) under a dictionary attack. Generally you would want to throttle, which I guess is a weaker version of weak module.
Tom Hawtin - tackline
2009-10-23 12:41:30