Patterns of Conflict, Easier on the Eyes
I’ve been posting a fair bit about Boyd. Boyd’s wrote very little. Most of his communication was in the form of briefs. At least two of you have publicly admitted to getting the slides, and, if you’re like me, struggled with the form of the presentation: A scan of a typed, hand-annotated presentation book. There’s a new Powerpoint version available, edited by Chet Richards and Chuck Spinney, and produced and designed by Ginger Richards. It’s far easier on the eyes. There are a few places where the presentation is unfortunately dense 8 point type, but that’s the breakdown in what Boyd wrote.
Thanks for the link. Signifigantly more readable than the handwritten ones. OODA loops are a great analogy to the problems inherent in being the defender in an IT Security context. At first blush, unfortuantely, it makes things look even more hopeless, especially for the folks who are completely reliant on 3rd parties for their main IT products be in applications or operating systems.
-DM
Well, it clearly implies that a few loops are broken. If you’re trying to learn about new patches (observe), discover if the other security measures you have obviate the need for them, and if not, test them (orient), decide when to install them, and then act, while your attacker is running automated attack code, you’re in trouble. The solution probably involves more attack resistant architectures, but that doesn’t actually shorten your loop, it just reduces the times you run through it. (Which probably means each iteration is longer.)