Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DSB Item - Attacker Model, Security Controls, Authentication and Identity Proofing Risk Framework (Initial consultation) #48

Closed
CDR-API-Stream opened this issue Aug 31, 2021 · 2 comments
Assignees
Labels
complete The item is now complete and no more work is occurring maturity: ready for work Indicates the problem statement is well defined and work on a proposal can begin sector: all The item is cross-sector in nature and impacts the CDR regime more broadly

Comments

@CDR-API-Stream
Copy link
Contributor

Problem Statement

In Decision 182, the Data Standards Chair approved four recommendations. This Future Plan item covers Recommendation 3 and the targeted consultation to determine appropriate risk-based security controls and supported authentication methods.

Feedback strongly supported the development of an attacker model to identify the risks the Information Security model seeks to address, and the controls required to manage those risks. This attacker model can leverage the FAPI 2 attacker model as a baseline developed by the OIDF.

The Data Standards Chair notes that the Future Directions report includes several key recommendations to enhance security, flexibility, and choice for consumers. These recommendations seek to adopt a risk-based approach to assessing which authentications methods be supported and when they are appropriate. In considering which authentication methods are suitable, the convenience and consumer experience of different authentication mechanisms should be considered against the actions being instructed and the risks both within a given sector and across the CDR. This recommendation supports and complements the Future Direction report's recommendations.

A risk-based authentication framework should look at when and how second factors of authentication are required and opportunities to support decoupled authentication (otherwise referred to as app2app).

In conjunction broadening authentication standards, the risk framework should consider the identity proofing requirements when initiating different actions.

Key Future Directions Recommendations

  • Recommendation 1.1 – Balanced approach to safety, efficiency and effectiveness
  • Recommendation 4.14 – Authentication requirements by data holders
  • Recommendation 4.15 – More explicit requirements for accredited persons to authenticate customers
  • Recommendation 5.11 – Authentication requirements for payment initiation
  • Recommendation 8.1 – Support for development of authentication solutions interoperable with the Consumer Data Right
  • Recommendation 8.2 – Minimum assurance standard for authentication to apply to data holders and accredited data recipients
  • Recommendation 8.3– Minimum assurance standard for authentication to include a risk taxonomy and matrix
  • Recommendation 8.10 – When diverging from open international standards
@CDR-API-Stream CDR-API-Stream added maturity: ready for work Indicates the problem statement is well defined and work on a proposal can begin sector: all The item is cross-sector in nature and impacts the CDR regime more broadly labels Aug 31, 2021
@CDR-API-Stream CDR-API-Stream self-assigned this Aug 31, 2021
@JamesMBligh
Copy link

Significant planning on this item has been conducted but it has been shifted to Q1 2022 for ongoing work

@JamesMBligh JamesMBligh changed the title DSB Item - Attacker Model, Security Controls, Authentication and Identity Proofing Risk Framework DSB Item - Attacker Model, Security Controls, Authentication and Identity Proofing Risk Framework (Initial consultation) Jan 19, 2022
@JamesMBligh
Copy link

A plan for engagement has been developed and has been internally circulated and reviewed. Currently working through the budgetary process to determine an appropriate timetable to schedule the actual engagements

@JamesMBligh JamesMBligh added the complete The item is now complete and no more work is occurring label Jul 12, 2022
@CDR-API-Stream CDR-API-Stream moved this to Complete in DSB Future Work Plan May 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complete The item is now complete and no more work is occurring maturity: ready for work Indicates the problem statement is well defined and work on a proposal can begin sector: all The item is cross-sector in nature and impacts the CDR regime more broadly
Projects
Archived in project
Development

No branches or pull requests

2 participants