March 6, 2018 PSAF Call
Jump to navigation Jump to search
|.||Member Name||.||Member Name||.||Member Name||.||Member Name|
|.||John Moehrke Security Co-chair||x||Kathleen Connor Security Co-chair||.||Alexander Mense Security Co-chair||.||Trish Williams Security Co-chair|
|x||Christopher Shawn] Security Co-chair||x||Suzanne Gonzales-Webb||x||Mike Davis||.||David Staggs|
|.||Mohammed Jafari||x||Beth Pumo||.||Ioana Singureanu||.||Rob Horn|
|x||Diana Proud-Madruga||x||Francsico Jauregui||.||Joe Lamy||.||Galen Mulrooney|
|.||Paul Knapp||.||Grahame Grieve||.||Johnathan Coleman||.||Aaron Seib|
|.||Ken Salyards||.||Jim Kretz||.||Gary Dickinson||x||Dave Silver|
|.||Oliver Lawless||.||||.||David Tao||x||Greg Linden|
- (3 min) Roll Call, Agenda Approval
- (5 min) Review and Approval of the Feb. 27th Minutes
- (50 min) TF4FA Ballot Work Session - Mike Davis and Chris Shawn
- Chris chaired.
- Agenda approved.
- Minutes were reviewed. Kathleen moved to approve. Beth seconded. approved 5-0-0
- Mike walked through several updated models noting that these reflect the focus change to exclude the access control components of the foundational PMAC and DAM models.
- Mike showed the group the Trust Context Model, which simplifies previous TF4FAby making the initiating Domain's (Domain A) trust proposal dependent on the recipient Domain's (Domain B) approval. If Domain A's proposal meets or exceeds Domain B's trust policies, then Domain B countersigns Domain A's proposal thereby executing a trust contract. If Domain A's trust proposal does not meet Domain B's trust policies, Domain B can decline the proposal or offer suggested "trust elevation" policies to bring Domain B into conformance to some extent, even if the result is that Domain A is not able to access all of the information it requested or with the same handling instructions. Domain A may counter with a new proposal, and this interaction continues until either B executes an agreed to trust contract or either drops out of the negotiations.
- Mike showed how trust policies may include specializations as security and privacy policies, and that these policies may have either one or a combination of jurisdictional, organizational, and subject of care policies.
- Mike described the underlying authorization policies as having one or a combination of access control schemes as required by the recipient Domain, including RBAC, ABAC< ACL, ReBAC among others. There is a March Harmonization proposal to bring Authorization and access control scheme policies into HL7 vocabulary.
- Second model diagram for Policy Bridging is similar to the PASS ACS services of Trust. Plan to harmonize with PASS ACS actor names.
- 3rd model is Trust Reference Model Federated Domain Model, which is not a systems theory cube or a VENN diagram or related to set theory since it is not an intersection.
- In summary, PMAC, which we are adopting is an Access Control Policy, and the Composite, Role, Groups, Management are part of Access control.
- But we don't need those for trust. At run time you'll have all policies available from the trust contract for that. The purpose of the basic policy is for purpose of negotiating trust.
- Mike will have latest models posted next week, and will discuss any update on next PSAF call.
- Meeting adjourned.