The What, How, Where, Who, When, & Why of Security Architecture

 

Our EACOE Enterprise Architecture practice has looked at security as part of Enterprise Architecture, not as a separate activity. Simply, the objective ensures only authorized access to a process or a data component.


Starting with this objective – not after the fact – is key. In the physical world, look at the game-changer brought about by the Ring doorbell – warn me before someone enters the house, rather than telling me someone is in the house.

If you are guided by FEA, TOGAF ®, or UAF, we hope that this additional Enterprise Architecture insight will provide the outline you need for a robust view of security and security architecture.

Security is a business strategy first - not only an implementation technology concern. Security is an after-the-fact approach in most organizations, unfortunately, rather than an architected approach, we suggest.

Please tune in to hear how to address this growing concern in organizations, well before it is actually needed.

Locks, passwords, etc., only keep honest people honest.

 
Previous
Previous

DM Radio: Enterprise Architecture in the Era of Hybrid Cloud

Next
Next

Enterprise Architect Participants?