Security Policy Assertion Language (SecPAL) provides a flexible and robust declarative authorization language developed for large-scale Grid Computing Environments.
Project Home Page
Welcome to the SecPAL Research Workspace. We have set this workspace up to support community members who may have questions relating to the preview release of SecPAL which is available from
. From time to time we may also post additional samples which will also demonstrate other aspects of SecPAL that were not covered in the initial preview
This CodePlex site is intended to support evaluation of SecPAL - it does not include a copy of the .NET implementation of SecPAL. The .NET implementation (and associated design papers is available from this site:
- August 27, 2007 SecPAL Parser sample available from
- July, 2007 "Fine Grained Access Control for GridFTP using SecPAL" accepted for 8th IEEE/ACM International Conference on Grid Computing (Grid 2007)
- May 15, 2007 "SecPAL: A security policy language to support grid on demand" presented at Software as a Service Architecture Forum - Presentation is available in the "Releases" section
SecPAL Presentation for SaaS Conference
- May 07, 2007 GridToday Special Feature "Access Control in Grid Computing Environments"
- Apr 30, 2007 Linux Insider "Microsoft Invites Collaboration With Grid Computing Research"
- Mar 02,2007 SecPAL preview release available
- Feb 08,2007 An updated version of the SecPAL Formal Model is available at
- Sept 13,2006 eWeek article "Microsoft building Security Language for Grids"
If you have downloaded the SecPAL MSI from the MSR site and have any questions about our API's or scenario coverage please feel free to post a question in the Discussions section.
Frequently Asked Questions
to see our FAQ's
For Questions about our 1.1 release, click
Heaven forbid! While we have tried hard to test SecPAL as we developed it, we are a small "incubation" team with limited resources so it is possible that you will find bugs! Please post bugs, along with detailed reproduction steps in the Issuer Tracker
section. As these releases are simply for research purposes we are tentatively planning an update in / around July depending if bugs are actually found or not. We will consider the community bug scores to help us prioritize which bugs to focus on.