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

Decision Proposal 034 - Supported Authorisation Flows #34

Closed
JamesMBligh opened this issue Oct 21, 2018 · 3 comments
Closed

Decision Proposal 034 - Supported Authorisation Flows #34

JamesMBligh opened this issue Oct 21, 2018 · 3 comments
Assignees
Labels
Category: InfoSec Information Security Technical Working Group Decision Proposal Status: No Decision Taken No determination for this decision has been made

Comments

@JamesMBligh
Copy link
Contributor

JamesMBligh commented Oct 21, 2018

No description provided.

@JamesMBligh JamesMBligh added Status: Proposal Pending A proposal for the decision is still pending Category: InfoSec Information Security Technical Working Group Decision Proposal labels Oct 21, 2018
@JamesMBligh JamesMBligh self-assigned this Oct 21, 2018
@JamesMBligh JamesMBligh added Status: Open For Feedback Feedback has been requested for the decision and removed Status: Proposal Pending A proposal for the decision is still pending labels Oct 25, 2018
@JamesMBligh
Copy link
Contributor Author

Please Note
Leading up to the definition of the first draft of the standards, the security working group decision proposals will be high level only. Due to the sensitivities around sharing security concerns and discussing current implementations in the financial sector the Advisory Committee has requested detailed security design decisions to be formulated via a series of in person meetings. These in person meetings will be co-ordinated using the security working group mailing list. You can sign up to this list at http://eepurl.com/dCNaTn.

The end result of this process will be a working draft proposal that will then be published and opened for transparent public comment, as has been the practice to date for the Data Standards Body.

For this reason this proposal, and others in this series, will focus on high level decisions that shape the overall approach to security under the regime rather than low level technical specifics.

-JB-

@JamesMBligh JamesMBligh added Status: Proposal Pending A proposal for the decision is still pending and removed Status: Open For Feedback Feedback has been requested for the decision labels Oct 25, 2018
@JamesMBligh
Copy link
Contributor Author

Apologies, I uploaded the internally reviewed proposal for authentication to the authorisation placeholder by mistake. I believe I have now set this right. Sorry for the confusion.

-JB-

@JamesMBligh
Copy link
Contributor Author

Due to time constraints and the pivot towards discussing security considerations via workshops with subsequent publishing of draft proposals for public comment this proposal has not be authored. It will be decommissioned for the time being without a proposal being presented.

-JB-

@JamesMBligh JamesMBligh added Status: No Decision Taken No determination for this decision has been made and removed Status: Proposal Pending A proposal for the decision is still pending labels Nov 1, 2018
@ConsumerDataStandardsAustralia ConsumerDataStandardsAustralia locked as resolved and limited conversation to collaborators Nov 1, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Category: InfoSec Information Security Technical Working Group Decision Proposal Status: No Decision Taken No determination for this decision has been made
Projects
None yet
Development

No branches or pull requests

1 participant