Poor Infrastructure Security -- Model

Poor Infrastructure Security -- Model Definition

In evaluating Figure 5.4, Example of a model shown as a process diagram. A pattern language approach to usability knowledge management. ( From Hughes, M. 2006. Journal of Usability Studies 2 ( 1): 76 -- 90 it is apparent how critical consistency of security roles, processes and definitions of technique and function are across an enterprise. The intent of this analysis is to provide a tabulation of roles, technique or function, knowledge use and data criteria, showing the effects of poor infrastructure security. Figure 1, a proposed Security Equilibrium Model, illustrates how critical it is to keep organizational and individual security models consistent with one another, taking into account the velocity or rapidity of change over time. All of these factors must be anchored in a sold series of governance and process requirements in order to stay stable over time as well. This proposed model also speaks to the role of users, team members, and facilitators as shown in Figure 5.4 as all these of these roles must be consistently managed or governed across the span of the proposed model below.

Figure 1: Proposed Security Equilibrium Model

In terms of the tabulation of roles for users, team members, and facilitators, the relative technique and function of security, knowledge use, access level, and data criteria, the proposed model overcomes the inherent limitations of the one shown in Figure 5.4. First from the tabulation of roles standpoint, the users, team members and facilitators each have a different responsibility in terms of creating and sharing knowledge. As a result, each must have a highly differentiated series of decision points or rules that govern access to which specific data elements and data sources when. The use of role-based knowledge management and security is implied in the structure of the proposed security equilibrium model. Anchoring this model in security governance and processes allows access to data and information to be role-based, measured for accuracy and much more aligned to the specific goals of users, team members, and facilitators. The technique or function to attain this level of role-based access to data needs to begin with a focus on creating profiles for each variation of users, team members and facilitators that only provides access to data of relevance. Finally the quantification of trust through the use of analytics and metrics can also ensure this model delivers credible, transferrable results on a dependable basis over time. Rather than relying on a series of theories to anchor the model, actual dashboards of scorecards can be used to effectively manage the levels of role definition, risk, and underscore the credibility of the model for the long-term. The nature of the first model shown in Figure 5.4 shows the need for changing perceptions to anchor information exchange. With his model the focus can be on creating a measurable outcome of effective security strategies, alleviating the confusion over roles and missed system integration points that can lead to more effective enterprise-wide security over time.