Solutions      Products       Company       Partners       News & Events
 
Virtual Private Webs Empowering Information-Sharing
 
Professional Services
Training Services •
Customer Support
Services
 
Course: Epok Federated Acess Manager Architecture Design

Description and Intended Audience:

This course will prepare solution architects, systems engineers, and systems integrators for the process of designing Epok solutions based on information-sharing problems. Students will learn how to assess the existing information environment, determine the policies and agreements that need to be in place, define the user population and resource control structure, and define communities, resource groups, user groups, and publications for the purpose of sharing sensitive information.

Skill Objectives:
At the end of this course, students will be able to:
  • Understand the value of using Epok Federated Acess Manager to meet cross-domain information-sharing requirements
  • Describe the business requirements in Epok Federated Acess Manager terms:
    • Sub-domains
    • Policy requirements
    • Sensitivity and trust requirements
    • Information flow: General information-sharing requirements between organizations
  • Organize resources into Resource Control Points and Resource Nodes according to established principles.
  • Organize user systems and user populations into external groups and Epok Group Nodes
  • Define static communities and define the rules for creating new communities in an Authority Network
  • Apply good design principles to the design of an Authority Network architecture
Training Outline:
  • Introduction
    • The architecture of an Epok Solution
  • Capturing the Business Problem
    • Information sharing
    • Capturing existing user, resource, and policy systems
    • Elements of a business problem that are of interest for Authority Net
    • Re-casting the problem in terms of the Epok model
    • Analysis Tools
  • Defining the AuthorityNet
    • Initial User Groups
    • Initial Resource Groups
    • Initial Communities
    • Partners and Subdomains
    • Projecting Dynamic Activity
  • Mapping the existing network (physical architecture)
    • Partners, Domains, Subdomains
      • Epok Server Distribution (where they will be and who owns them)
    • Agreements and relationships
    • Mapping the user system
      • User roles: Insight, Architect, Helm
      • Users and usergroups in a subdomain
    • Mapping Resources
      • Resource repositories
      • Defining Control Points
      • RPA locations
      • External Policy Systems
      • Resource Granularity
    • Conclusion and Summary
< Back
Privacy Statement :: Terms of Use :: Trademarks
© 2007 Epok, Inc. All Rights Reserved.