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
Adding Safeguards to DPV #23
Comments
DPV: Updates and additions to purposes, tech-org measures, entities, legal basis (new module). DPV-GDPR: Updates and additions to data transfers (new module). Updated labels and descriptions of terms for consistency. For detailed changelog, see /dpv/changelog.html and /dpv-gdpr/changelog.html respectively. fixes w3c#25 purpose diagram typo relevant to w3c#23 safeguard as a concept relevant to w3c#22 expanding purpose taxonomy
Note that DPV now contains safeguards as a concept, as well as the data transfer safeguards from GDPR. A review of their sufficiency is to be undertaken and its outcome to determine closing of this issue. |
Reviewed this topic , From A GDPR perspective need to model the appropriate safeguards from Article 46 Appropriate safeguards We also need to consider adding in Transfer Impact assessment and Supplementary measures, which are part of any international transfer to a non-adequate country I looked at HIPPA safeguards and they mainly relate to Technical and Organisational measures. I t believe we have sufficient coverage in that area |
Thanks Paul. From that list, what concepts are missing in DPV? I think we have all of them (across DPV + DPV-GDPR) Also please note that "Supplementary Measures" doesn't have a definition by itself, and instead is what we use to refer to additional TOMs to safeguard the data. And because the term is EU-specific, I would not create a separate concept with that label since Safeguard/RiskMitigationMeasure also has the same role. |
Agreed, I confirm that DPV-GDPR contains items a to F |
Thanks, closing the issue as completed. |
How and where to model
Safeguard
as a concept within the DPV.The text was updated successfully, but these errors were encountered: