Difference between revisions of "OpenId Foundation Activities"

From IPEN Wiki
Jump to: navigation, search
 
(4 intermediate revisions by the same user not shown)
Line 41: Line 41:
 
|}
 
|}
  
<parsererror style="display: block; white-space: pre; border: 2px solid #c77; padding: 0 1em 0 1em; margin: 1em; background-color: #fdd; color: black">
+
=== <span style="font-size: 18.2520008087158px; line-height: 21.902400970459px;">Shared Signals and Events WG</span> ===
=== This page contains the following errors: ===
+
<div style="font-family:monospace;font-size:12px">error on line 1 at column 394: attributes construct error </div>
+
=== Below is a rendering of the page up to the first error. ===
+
</parsererror>
+
=== <span style="font-size:larger;">Shared Signals and Events WG</span><span style="font-size: 18.2520008087158px; line-height: 21.902400970459px;"></span> ===
+
  
 
{| border="1" cellspacing="1" cellpadding="1" style="line-height: 20.7999992370605px; width: 900px;"
 
{| border="1" cellspacing="1" cellpadding="1" style="line-height: 20.7999992370605px; width: 900px;"
Line 52: Line 47:
 
| Chair
 
| Chair
 
|  
 
|  
 +
Annabelle Richard (Amazon), Atul Tulshibagwale (Google), Marius Scurtescu (Coinbase)
 +
 +
|-
 +
| Overview
 +
|
 +
The goal of the Shared Signals and Events Working Group is to enable the sharing of security events, state changes, and other signals between related and/or dependent systems in order to:
 +
 +
#&nbsp;Manage access to resources and enforce access control restrictions across distributed services operating in a dynamic environment.
 +
#Prevent malicious actors from leveraging compromises of accounts, devices, services, endpoints, or other principals or resources to gain unauthorized access to additional systems or resources.
 +
#Enable users, administrators, and service providers to coordinate in order to detect and respond to incidents.
 +
 +
|-
 +
| Web pages
 +
| [https://openid.net/wg/sse/ https://openid.net/wg/sse/]
 +
|-
 +
| Documentation
 +
|
 +
|-
 +
| Comments
 +
|
 +
 +
 
|}
 
|}

Latest revision as of 22:00, 28 April 2020

Openid-r-logo-900x360.png


Introduction

The objective of this page is to provide a high-level view of activities related to privacy standards in the OpenId foundation.http://openid.net/

"The OpenID Foundation (OIDF) promotes, protects and nurtures the OpenID community and technologies. The OpenID Foundation is a non-profit international standardization organization of individuals and companies committed to enabling, promoting and protecting OpenID technologies. Formed in June 2007, the foundation serves as a public trust organization representing the open community of developers, vendors, and users. OIDF assists the community by providing needed infrastructure and help in promoting and supporting expanded adoption of OpenID. This entails managing intellectual property and brand marks as well as fostering viral growth and global participation in the proliferation of OpenID."

Current working groups and projects related to privacy standards

Heart WG

Chair
Overview

The HEART Working Group intends to harmonize and develop a set of privacy and security specifications that would enable an individual to manage the authorization, consent and release of their health related data via RESTful data sharing APIs, and to facilitate the development of interoperable implementations of these specifications by others
List of current working documents / projects are as follows:

  • Health Relationship Trust Profile for OpenID Connect 1.0
  • Health Relationship Trust Profile for OAuth 2.0
  • Health Relationship Trust Profile for User Managed Access 1.0
  • Health Relationship Trust Profile for
  • Fast Healthcare Interoperability Resources (FHIR) OAuth 2.0 Scopes
Web pages http://openid.net/wg/heart/
Documentation
Comments


Shared Signals and Events WG

Chair

Annabelle Richard (Amazon), Atul Tulshibagwale (Google), Marius Scurtescu (Coinbase)

Overview

The goal of the Shared Signals and Events Working Group is to enable the sharing of security events, state changes, and other signals between related and/or dependent systems in order to:

  1.  Manage access to resources and enforce access control restrictions across distributed services operating in a dynamic environment.
  2. Prevent malicious actors from leveraging compromises of accounts, devices, services, endpoints, or other principals or resources to gain unauthorized access to additional systems or resources.
  3. Enable users, administrators, and service providers to coordinate in order to detect and respond to incidents.
Web pages https://openid.net/wg/sse/
Documentation
Comments