Building blocks of secure design

Any discussion about the requisite tools in your design toolbox wouldn't be complete without some discussion of the actual security mechanisms that you'll employ as part of your design. These represent specific measures you might use—and specific objectives that you might target—as part of a broader, overarching security design.

It's important to understand what these controls are and are not. They are not implementations. Any given control can be implemented in a myriad of different ways. For example, you might have a control specifying that any administrative access to production systems (and system components) must be logged and recorded. However, this control doesn't outline how you'd do that; instead, context, circumstances, and the organization itself will dictate how. For example, if access to the production system happens via a terminal (that is, a user at the keyboard), you might use the native logging...