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

1.8.X new requirements #1005

Closed
mgeramb opened this issue May 26, 2021 · 7 comments
Closed

1.8.X new requirements #1005

mgeramb opened this issue May 26, 2021 · 7 comments
Assignees
Labels
2) Awaiting response Awaiting a response from the original poster

Comments

@mgeramb
Copy link

mgeramb commented May 26, 2021

In the EU in particular, the handling of personal data is strictly regulated (DSGVO). I know that with 1.8.2 everything should be fine. But maybe additional requirements makes it more clear.

e.g.:

  • Provide functions to delete or anonymize old personal data
  • Store only personal data which is required by your business process
  • Verify the location (EU, USA, etc) where data is stored match the requirements of the local law

What is your opinion?

Best,
Michael

@elarlang
Copy link
Collaborator

Just mapping it here.

Current section Sensitive Private Data contains requirements like:

  • 8.3.2 Verify that users have a method to remove their data on demand.
  • 8.3.9 Verify that users have a method to export their data on demand.

One related issue: #883

@mgeramb
Copy link
Author

mgeramb commented May 31, 2021

@elarlang You are right, but I see the first chapter more as guidlines for the architecture and design, while the chapter 8.X is more relevant for the developers. Maybe it makes sense to add some requirements to the architecture part as well.
At least, I can not find anything related to:

  • Store only personal data which is required by your business process

@elarlang
Copy link
Collaborator

Like I wrote, I was just mapping those pieces here, because those belong to the same topic.

In big picture my vision is to move to solution (but I'm not deciding it :) ) where V1 describes architecture and business-logical decisions and other categories have requirements, where you can check are those really implemented. So, this vision is matching with your latest comment well.

To make other's life easier, @mgeramb , can you please provide quotes and references from regulations behind your proposals.

@mgeramb
Copy link
Author

mgeramb commented May 31, 2021

@elarlang You mean like this: "Store only personal data which is required by your business process" -> see DSGVO Chapter II, Article 5, (c)"
DSGVO Enlish

@elarlang
Copy link
Collaborator

Yes, something which support those requirements. Those references are not pre-conditions, but the less conflicts are between different standards and regulations, the easier it is to work with them. And if there is difference, it should be argumented one.

@elarlang elarlang added the 2) Awaiting response Awaiting a response from the original poster label Jul 14, 2021
@jmanico
Copy link
Member

jmanico commented Aug 31, 2021

Ping. I think we should drop section 1.8 and merge 1.8.1 and 1.8.2 into section 8.1 and close this out!

@mgeramb
Copy link
Author

mgeramb commented Sep 3, 2021

I agree, thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2) Awaiting response Awaiting a response from the original poster
Projects
None yet
Development

No branches or pull requests

3 participants