CS 5511 Introduction to WS Authorization Brian P. Barrett

CS 5512 Authorization  WS-Authorization – Complete?  Steps of Authorization  Security Token Acquisition  SAML  Authorization in Firewall  Map of Authorization  Authorization in Code  References

CS 5513 Where does Authorization fit in?  Authorization is an aspect of security that falls in with other categories: Secure Conversation Federation Policy Trust Federation Privacy Is this Authorized?

CS 5514 Security  Authentication Determine identity of a person/object  Authorization Determine what the person is allowed to do  Integrity Ensure the data was not altered on its way to you  Signature Validate the source of the data  Confidentiality Limit the people allowed to view the data  Privacy Make sure no one abuses your data  Digital Rights Management Limit users from doing whatever they want  Authentication Determine identity of a person/object  Authorization Determine what the person is allowed to do  Integrity Ensure the data was not altered on its way to you  Signature Validate the source of the data  Confidentiality Limit the people allowed to view the data  Privacy Make sure no one abuses your data  Digital Rights Management Limit users from doing whatever they want

CS 5515 How does Authorization work with other services?  If Authorization were to be on a layer working with other Services. It would work in conjunction with the Federation layer. WS-Federation WS-Secure Conversation WS-Authorization

CS 5516 Authorization with other WS

CS 5517

8 PMI or Privilege Management Infrastructure  Privilege Management Infrastructure: Source of Authority (SOA) = The topmost root of trust, sometimes also referred to as trust anchor Attribute Authority (AA) (also Privilege Allocator, Authoritative Entity) = The issuer of an attribute certificate Certificate Holder / Privilege Holder = The User or Subject of an Attribute Certificate

CS 5519 Security Token Authorized The Web Service Obtains security Token Web Service Trusts Established. Request was Processed and response returned Auth and Trust are Validated. Service must find Data and policies that are authorized for the user. The Data and policies will be Validated for that Particular client Requestor Issues a request.

CS SAML – Security Assertion Markup Language  SAML’s purpose was to be a Security language that could be used as an industry standard for security. It uses XML digital signatures with XML encryption.  The languages uses assertions made in the code that can convey information about authentication functions, and authorization decisions.

CS SAML Authorization Map

CS PEP- Policy Enforcement Point  Definition  Dependence upon the resource  PDP-Policy Decision Point

CS Authorization in Firewall Processing Claims officer/ Customer Insurance Co. Web-Service

CS Authorization Process Map Client -Give server trust -Invocate policy -consult policy Authorization Process Role based Authorization Instance based Authorization Capability listings Server -Access Policy -Give client resource -Policy authority

CS How does the the Authorization code fit?

CS Authorization in code Show SAML code and explain. SAML doc Authorization decision: by subject S, for access type A, to resource R, given evidence E.

CS Code Example * //medico.com/records.* read

CS References  Primary –Globus is a resource to see the latest changes with WS-Authorization and other new standards. –If you go here and choose XML Security under Lecture slides you will find some detail about coding with SAML and its interaction for Authorization processes.  Secondary us/dnwssecur/html/securitywhitepaper.asp –Here you will fine some significant images that detail security over the web. –At this site you can learn new technology dealing with XML, SAML and XMACL.