Addressing Security Concerns with WSO2 Governance Registry Policy Store - Tuesday, June 25, 2013
- By Kushlani De Silva
- |
- 25 Jun, 2013
Security threats exist in almost all organizations. While distributed access is required, many enterprises are faced with the challenge of protecting their resources from unauthorized access. Access to organizational assets can be prevented by enforcing well structured policies within networked environments.
The WSO2 Governance Registry addresses these security concerns by acting as a central repository to store policies. It acts as a policy enforcement point beyond the fact that it governs the assets stored in it. As a policy Store, the WSO2 Governance Registry enables the WSO2 ESB and WSO2 Identity Server to enforce policies at design time as well as run time.
Join Eranda Suriyabandara and Sriragu Arudsothy on this webinar as they explain
- The importance of policies to restrict access.
- A sample policy file and its elements.
- How to enforce policies in design time and run time.
- A sample scenario on how the WSO2 Governance Registry can be used as a policy store
Eranda Sooriyabandara
Software Engineer
Eranda joined WSO2 in the fall of 2011. He is a software engineer in the integrations technologies team where he worked as the release manager for the WSO2 Governance Registry 4.5.3. In addition to his product development efforts he is also an active contributor to the Apache Derby and Apache Tuscany projects of the Apache Software Foundation.
Sriragu Arudsothy
Senior Software Engineer
Sriragu joined WSO2 in October 2012. He is a senior software engineer in the integration technologies team where he mainly focuses on the WSO2 Governance Registry.
During his MSc at the University of Greenwich he worked on a project titled “ mobile based order processing system for sales representatives working in telecom sectors ". Based on multiple case studies carried out.
