Figure 9 - uploaded by David W. Enström
Content may be subject to copyright.
-Static Model of Audit.

-Static Model of Audit.

Source publication
Conference Paper
Full-text available
This paper defines an enterprise security model that provides a cohesive structure for the definition and implementation of security services. The complete framework is described, but with a focus on subjects, and protected objects and how access is controlled. Multiple layers of security are defined, building upon the “defence in depth” concept, a...

Contexts in source publication

Context 1
... static view is shown in . The new classes in Figure 9 are: Figure 9 Security Audit -implements the logging of security events and information for and about the protected objects and other sensitive information within a domain. Audit information is always traceable to the subject involved in the activity. ...
Context 2
... static view is shown in . The new classes in Figure 9 are: Figure 9 Security Audit -implements the logging of security events and information for and about the protected objects and other sensitive information within a domain. Audit information is always traceable to the subject involved in the activity. ...
Context 3
... dynamic view of audit is shown in Figure 10. The only changes to this model of audit (compared to Figure 9) are the addition of the "Dynamic Role Assignment and Delegation Policy", and the removal of the "Static Role Assignment and Delegation Policy" (for clarity purposes). ...

Similar publications

Conference Paper
Full-text available
The current trends in South African cellular Value-Added Services are a melting-pot of consumer dissatisfaction. Only recently have regulations begun ensuring consumer protection. However recent experiences with subscription-based Value-Added Services have shown that the stricter regulations do not protect the consumer in a timely manner. The autho...

Citations

Conference Paper
A precise definition of IT architecture and its relationship to engineering is described. The components used to define architecture are generically defined along with relationships among these components. These concepts are then used, along with a particular architecture viewpoint and system context to document an example of architecture components using structural and behavioural signatures to express form and function. The end result is a well defined approach for the documentation of IT architectures, based upon a concise definition of architecture, the components used to describe the architecture, and the relationships and structures among these components.
Conference Paper
Full-text available
Dynamic business environments require concurrent, distributed, and flexible architectures that must provide an agreeable level of reliability and acceptable level of trust. A three level undisruptive business driven planning process has been formulated using a risk analysis model that provides a justifiable direction for implementing a low risk solution and selecting appropriate products. The methodology includes identification of “Risk Priority” through assessment of risks for: business effectiveness, logical IT solution architecture (PIM) aspects, and physical IT solution architecture (PSM) aspects. It also introduces a risk dependency analysis process as an aid in understanding relationships between architectural layers. This proposed methodology aids in understanding and prioritizing risks within the context of the organization; it has broadened the concept of a TRA into a risk controlled solution architecture domain.