Fig-12: Pushing configurations from model.
Fig-12: Pushing configurations from model.
Fig-13: Configuration from Model (the numbering indicates typical sequence of events)
TAS3 is pervasively model driven. Fig-12 shows how a business process model can drive auditing processes, or even influence the Dashboard user interface so that Users can visualize the processes.
Fig-10, shows how models are used to configure policies for the PDPs. It also shows an alternate approach where PEP itself can be directly configured, e.g. using Identity Governance Framework [IGF] CARML and/or AAPML.
From the model the Trust Guarantor is able to derive
Basic trust configuration, i.e. who belongs to the network
a white list of members
metadata to configure trust in the members
Configurations to be pushed to operational elements of the network so that they will consistently enforce the process and trust model and the security model of the Trust Network.
Operations Monitoring setup, e.g. if alerts are coming from some node, what Networks Operations Centre (NOC) process should they enter, where should they be disseminated, who should see them, and who is responsible for response
On-line compliance testing configuration. This will drive a robot, spider if you like, that will comb through the Trust Network on a regular basis to verify that each service is in compliance with the policies that it publicly manifests.
The Organizations A and B participate in the Trust Network. They also model their business processes, extending and refining the global model. They, too, will benefit from ability to automatically configure and monitor the components of their infrastructure.