When the builder plans the construction process, she or he needs to assemble a team of experts in each of the building trades that will be needed: the bricklayer, the plasterer, the electrician, the plumber, the carpenter, and so on. Each one of these brings some very specific production skills and some very specific products to the overall construction process.

​

It is the same in the construction of information systems. The builder needs to assemble a series of products from specialist vendors and a tea with the integration skills to join these products together during an implementation of the design.

​

Each of the integrators is the equivalent of a tradesman, working with specialist products and system components that are the equivalent of building materials and components. Some of these 'trades'  are hardware-related, some are software-related, and some are service oriented. The 'tradesmen' work with a series of components that are hardware items, software items, and interface specifications and standards. Hence this layer of the architectural model is also called the 'component security architecture' (Sherwood, Clark, & Lynas, 2005).

​

The component security architecture is connected with:

​

What? Data field specifications, address specifications and other detailed data structure specifications;

​

Why? Security standards;

​

How? Products and tools (both hardware and software);

​

Who? User identities, privileges, functions, actions and access control lists (ACLs);

​

Where? Computer processes, node addresses, and inter-process protocols;

​

When? Security step timings and sequencing  (Sherwood, Clark, & Lynas, 2005).

​

​

Source:

​

Sherwood, J., Clark, A., & Lynas, D. (2005). The Tradesman's View. In J. Sherwood, A. Clark, & D. Lynas,

        Enterprise  Security Architecture (p. 39). San Francisco: CMP Books.

​