Misplaced Pages

User:Guy Macon/sandbox: Difference between revisions

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
< User:Guy Macon Browse history interactively← Previous editNext edit →Content deleted Content addedVisualWikitext
Revision as of 08:53, 2 May 2021 editGuy Macon (talk | contribs)Extended confirmed users, File movers, New page reviewers, Pending changes reviewers, Rollbackers59,290 edits test2Tag: Reverted← Previous edit Revision as of 08:54, 2 May 2021 edit undoGuy Macon (talk | contribs)Extended confirmed users, File movers, New page reviewers, Pending changes reviewers, Rollbackers59,290 edits RestoreTag: Manual revertNext edit →
Line 1: Line 1:
https://w.wiki/3d7
{{short description|Framework for systems engineering}}
{{Use dmy dates|date=April 2020|cs1-dates=y}}
'''Privacy by design''' is an approach to ] initially developed by ] and formalized in a joint report on ] by a joint team of the ] (Canada), the ], and the ] in 1995.<ref name="Privacy Enhancing Technologies: the path to anonymity">{{cite web|last=Hes|first=R|title=Privacy Enhancing Technologies: the path to anonymity|url=http://www.ontla.on.ca/library/repository/mon/10000/184530.pdf}}</ref><ref name="deliveringthepromises">{{cite journal|last=Hustinx|first=Peter|title=Privacy by Design: Delivering the Promises|journal=Identity in the Information Society|volume=3|issue=2|pages=253–255|doi=10.1007/s12394-010-0061-z|year=2010|doi-access=free}}</ref> The privacy by design framework was published in 2009<ref name="7principles" /> and adopted by the International Assembly of Privacy Commissioners and Data Protection Authorities in 2010.<ref name="resolution" /> Privacy by design calls for ] to be taken into account throughout the whole engineering process. The concept is an example of ], i.e., taking human values into account in a well-defined manner throughout the process.<ref name="YGJt2">{{Cite journal|last1=Xu|first1=Heng|last2=Crossler|first2=Robert E.|last3=Bélanger|first3=France|date=2012-12-01|title=A Value Sensitive Design Investigation of Privacy Enhancing Tools in Web Browsers|url=http://www.sciencedirect.com/science/article/pii/S0167923612001868|journal=Decision Support Systems|language=en|volume=54|issue=1|pages=424–433|doi=10.1016/j.dss.2012.06.003|issn=0167-9236}}</ref><ref name="EAqHF">{{Cite journal|last=Cavoukian|first=Ann|date=2011|title=Privacy by Design|url=https://iapp.org/media/pdf/resource_center/pbd_implement_7found_principles.pdf|journal=Information and Privacy Commissioner}}</ref>


{{ambox|type=content|text='''Some ] ] says that ] with this page. That editor can't be troubled to fix it or even ] it on the article talk page, but we can all sleep easy knowing that they ].'''<br /><small>Please ] this tag to languish indefinitely at the top of this page, since ] it is here.</small>}}
Cavoukian's approach to privacy has been criticized as being vague,<ref name="Designing Privacy by Design" /> challenging to enforce its adoption,<ref name="Counterfactual" /> difficult to apply to certain disciplines,<ref name="Engineering Privacy by Design" /> as well as prioritizing corporate interests over consumers' interests<ref name="Designing Privacy by Design" /> and placing insufficient emphasis on minimizing data collection.<ref name="Engineering Privacy by Design" />
A ''']''' is a place to experiment with editing Misplaced Pages pages. This is Guy Macon's personal sandbox.


== What is a sandbox? ==
The European ] regulation incorporates privacy by design.<ref name="Opinion" />
This is Guy Macon's personal sandbox. ''']''' is a sandbox that ''anyone'' can use -- see '']'' for details.


== Temporary stuff I might need later 01 ==
==History and background==
The privacy by design framework was developed by ], ], following her joint work with the ] and the ] in 1995.<ref name="Privacy Enhancing Technologies: the path to anonymity" /><ref name="Opinion" />
In 2009, the ] co-hosted an event, ''Privacy by Design: The Definitive Workshop'', with the Israeli Law, Information and Technology Authority at the 31st International Conference of Data Protection and Privacy Commissioner (2009).<ref name="MrPfr">{{cite web|title=Privacy Conference 2009 Fifth Plenary Session – Privacy by Design|url=http://www.privacyconference2009.org/program/Programa_detallado/index-iden-idweb.html#sesion5}}</ref><ref name="report2011">{{cite web|title=Report on the State of PbD to the 33rd International Conference of Data Protection and Privacy Commissioners|url=https://ipc.v51.com/wp-content/uploads/Resources/PbDReport.pdf}}</ref>


]
In 2010 the framework achieved international acceptance when the International Assembly of Privacy Commissioners and Data Protection Authorities unanimously passed a resolution on privacy by design<ref name="foreword">{{cite journal|title=Privacy by Design: the definitive workshop. A foreword by Ann Cavoukian, Ph.D|journal=Identity in the Information Society|volume=3|issue=2|pages=247–251|url=https://rd.springer.com/content/pdf/10.1007%2Fs12394-010-0062-y.pdf|doi=10.1007/s12394-010-0062-y|year=2010|last1=Cavoukian|first1=Ann|s2cid=144133793}}</ref> recognising it as an international standard at their annual conference.<ref name="report2011" /><ref name="TgjrM">{{cite web|title='Privacy by Design' approach gains international recognition |url=https://www.itbusiness.ca/news/video-rewind-privacy-by-design-approach-gains-international-recognition/15626}}</ref><ref name="qUcNp">{{cite web|title= Landmark Resolution passed to preserve the Future of Privacy|url=http://www.ipc.on.ca/english/Resources/News-Releases/News-Releases-Summary/?id=992|archive-url = https://web.archive.org/web/20101108031015/http://www.ipc.on.ca/english/Resources/News-Releases/News-Releases-Summary/?id=992|archive-date = 2010-11-08}}</ref><ref name="resolution">{{cite web|title=32nd International Conference of Data Protection and Privacy Commissioners Jerusalem, Israel 27-29 October, 2010 Resolution on Privacy by Design|url=https://edps.europa.eu/sites/edp/files/publication/10-10-27_jerusalem_resolutionon_privacybydesign_en.pdf}}</ref> Among other commitments, the commissioners resolved to promote privacy by design as widely as possible and foster the incorporation of the principle into policy and legislation.<ref name="resolution" />


]
==Global usage==
Germany released a statute (§ 3 Sec. 4 ''Teledienstedatenschutzgesetz'' ) back in July 1997.<ref name="31Cp1">{{Cite web |url=https://www.bgbl.de/xaver/bgbl/start.xav?start=//*%5B@attr_id=%27bgbl197s1870.pdf%27%5D#__bgbl__%2F%2F*%5B%40attr_id%3D%27bgbl197s1870.pdf%27%5D__1531906349003 |title=Bundesgesetzblatt}}</ref> The new EU ] (GDPR) includes ‘data protection by design’ and ‘data protection by default’,<ref name="European Commissioner (January 2012)">{{cite web|title=Regulation of the European Parliament and of the Council on the protection of individuals with regard to the processing of personal data and on the free movement of such data (General Data Protection Regulation)|url=http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=COM:2012:0011:FIN:EN:PDF|work=European Commissioner (January 2012)}}</ref><ref name="liDeM">{{cite web|title=European Commission - Fact Sheet Questions and Answers – General Data Protection Regulation|url=http://europa.eu/rapid/press-release_MEMO-18-387_en.htm}}</ref><ref name="Opinion" /> the second foundational principle of privacy by design. Canada’s Privacy Commissioner included privacy by design in its report on ''Privacy, Trust and Innovation – Building Canada’s Digital Advantage''.<ref name="QbwUO">{{cite web|title=Privacy, Trust and Innovation – Building Canada's Digital Advantage|url=https://www.priv.gc.ca/en/opc-actions-and-decisions/submissions-to-consultations/sub_de_201007/|date=2010}}</ref><ref name="3Q23P">{{cite web|title=Towards Privacy by Design: Review of the Personal Information Protection and Electronic Documents Act. Report of the Standing Committee on Access to Information, Privacy and Ethics |url=http://publications.gc.ca/collections/collection_2018/parl/xc73-1/XC73-1-1-421-12-eng.pdf}}</ref> In 2012, U.S. ] recognized privacy by design as one of its three recommended practices for protecting online privacy in its report entitled ''Protecting Consumer Privacy in an Era of Rapid Change'',<ref name="FTC Report (March 2012)">{{cite web|title=Protecting Consumer Privacy in an Era of Rapid Change: Recommendations for businesses and policy-makers.|url=http://www.ftc.gov/sites/default/files/documents/reports/federal-trade-commission-report-protecting-consumer-privacy-era-rapid-change-recommendations/120326privacyreport.pdf|work=FTC Report (March 2012)}}</ref> and the FTC included privacy by design as one of the key pillars in its ''Final Commissioner Report on Protecting Consumer Privacy''.<ref name="Z1zzp">{{cite web|title=FTC Issues Final Commission Report on Protecting Consumer Privacy|url=https://www.ftc.gov/news-events/press-releases/2012/03/ftc-issues-final-commission-report-protecting-consumer-privacy|date=2012-03-26}}</ref> In Australia, the Commissioner for Privacy and Data Protection for the State of Victoria (CPDP) has formally adopted privacy by design as a core policy to underpin information privacy management in the Victorian public sector.<ref name="JuvJ2">{{cite web|title=Office of the Victorian Information Commissioner - Privacy by Design|url=https://www.cpdp.vic.gov.au/menu-privacy/privacy-organisations/privacy-organisations-privacy-by-design}}</ref> The UK Information Commissioner’s Office website highlights privacy by design<ref name="JOMoA">{{cite web|title=UK ICO - Privacy by Design|url=https://ico.org.uk/for-organisations/guide-to-data-protection/privacy-by-design/|archive-url=https://web.archive.org/web/20180524070513/https://ico.org.uk/for-organisations/guide-to-data-protection/privacy-by-design/|archive-date=2018-05-24}}</ref> and data protection by design and default.<ref name="qMHDF">{{cite web|title=UK ICO - Data protection by design and default|url=https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/accountability-and-governance/data-protection-by-design-and-default/|date=2018-11-23}}</ref> In October 2014, the Mauritius Declaration on the Internet of Things was made at the 36th International Conference of Data Protection and Privacy Commissioners and included privacy by design and default.<ref name="xZCEM">{{cite web|title=Mauritius Declaration on the Internet of Things|url=https://icdppc.org/wp-content/uploads/2015/02/Mauritius-Declaration.pdf}}</ref> The Privacy Commissioner for Personal Data, Hong Kong held an educational conference on the importance of privacy by design.<ref name="5SaCA">{{cite web|title=About the Privacy by Design Conference|url=https://www.pcpd.org.hk/pbdconference/privacy-by-design-conference.html}}</ref><ref name="8TiTn">{{cite web|title=Privacy Commissioner for Personal Data – Privacy by Design|url=https://www.pcpd.org.hk/pbdconference/privacy-by-design.html}}</ref>


]
In the private sector, ] commits to privacy by design principles;<ref name="7xU3L">{{cite web|title=Sidewalk Toronto commits to privacy by design principles amid citizen concerns|url=https://www.itbusiness.ca/news/sidewalk-toronto-commits-to-privacy-by-design-principles-amid-citizen-concerns/101598}}</ref> Brendon Lynch, Chief Privacy Officer at ], wrote an article called ''Privacy by Design at Microsoft'';<ref name="kgdVQ">{{cite web|title=Privacy by Design at Microsoft|url=https://blogs.microsoft.com/on-the-issues/2010/11/30/privacy-by-design-at-microsoft/|date=2010-11-30}}</ref> whilst ] relates certifiably trustworthy to privacy by design.<ref name="i44vK">{{cite web|title=Ryerson, Deloitte partner to offer privacy certification|url=https://www2.deloitte.com/ca/en/pages/risk/articles/Privacybydesign.html}}</ref>


https://en.wikipedia.org/User_talk:Doc_James#13_years
== Foundational principles ==
Privacy by design is based on seven "foundational principles":<ref name="7principles">{{cite web|last=Cavoukian|first=Ann|url=https://www.ipc.on.ca/wp-content/uploads/Resources/7foundationalprinciples.pdf|title=7 Foundational Principles}}</ref><ref name="7principlesFIPmapping" /><ref name="pbdPrimer" /><ref name="7P-Ryerson" />


https://en.wikipedia.org/Wikipedia:Administrators%27_noticeboard#Suggestion
# Proactive not reactive; preventive not remedial<ref name="7principles" /><ref name="7principlesFIPmapping" /><ref name="pbdPrimer" /><ref name="7P-Ryerson" />
# Privacy as the default setting<ref name="7principles" /><ref name="7principlesFIPmapping" /><ref name="pbdPrimer" /><ref name="7P-Ryerson" />
# Privacy embedded into design<ref name="7principles" /><ref name="7principlesFIPmapping" /><ref name="pbdPrimer" /><ref name="7P-Ryerson" />
# Full functionality – positive-sum, not zero-sum<ref name="7principles" /><ref name="7principlesFIPmapping" /><ref name="pbdPrimer" /><ref name="7P-Ryerson" />
# End-to-end security – full lifecycle protection<ref name="7principles" /><ref name="7principlesFIPmapping" /><ref name="pbdPrimer" /><ref name="7P-Ryerson" />
# Visibility and transparency – keep it open<ref name="7principles" /><ref name="7principlesFIPmapping" /><ref name="pbdPrimer" /><ref name="7P-Ryerson" />
# Respect for user privacy – keep it user-centric<ref name="7principles" /><ref name="7principlesFIPmapping" /><ref name="pbdPrimer" /><ref name="7P-Ryerson" />


https://en.wikipedia.org/User_talk:Jimbo_Wales/Archive_236#13_years
The principles have been cited in over five hundred articles<ref name="iZdNo">{{cite web|url=https://scholar.google.com/scholar?cites=10949576998236199397|title=Citations for ''Privacy by Design in Law, Policy and Practice''|publisher=Google Scholar}}</ref> referring to the ''Privacy by Design in Law, Policy and Practice'' white paper by ].<ref name="pbdLawPolicyPracitice">{{cite web|last=Cavoukian|first=Ann|url=http://www.ontla.on.ca/library/repository/mon/25008/312239.pdf|title=Privacy by Design in Law, Policy and Practice – A White Paper for Regulators, Decision-makers and Policy-makers}}</ref>


https://phabricator.wikimedia.org/T6845
=== Foundational principles in detail ===
====Proactive not reactive; preventive not remedial====
The privacy by design approach is characterized by proactive rather than reactive measures. It anticipates and prevents privacy invasive events before they happen. Privacy by design does not wait for privacy risks to materialize, nor does it offer remedies for resolving privacy infractions once they have occurred — it aims to prevent them from occurring. In short, privacy by design comes before-the-fact, not after.<ref name="7principlesFIPmapping">{{cite web|last=Cavoukian|first=Ann|url=https://www.ipc.on.ca/wp-content/uploads/Resources/pbd-implement-7found-principles.pdf|title=The 7 Foundational Principles Implementation and Mapping of Fair Information Practices|date=January 2011|publisher=Information and Privacy Commissioner of Ontario}}</ref><ref name="pbdPrimer">{{cite web|last=Cavoukian|first=Ann|url=https://ipc.v51.com/wp-content/uploads/Resources/pbd-primer.pdf|title=Privacy by Design – Primer}}</ref><ref name="7P-Ryerson">{{cite web|last=Cavoukian|first=Ann|url=https://www.ryerson.ca/content/dam/pbdce/seven-foundational-principles/The-7-Foundational-Principles.pdf|title=Privacy by Design – The 7 Foundational Principles|publisher=Privacy and Big Data Institute}}</ref>


https://meta.wikimedia.org/Talk:Wikimedia_Foundation_Board_of_Trustees#13_years
====Privacy as the default====
Privacy by design seeks to deliver the maximum degree of privacy by ensuring that personal data are automatically protected in any given IT system or business practice. If an individual does nothing, their privacy still remains intact. No action is required on the part of the individual to protect their privacy — it is built into the system, by default.<ref name="7principlesFIPmapping" /><ref name="pbdPrimer" /><ref name="7P-Ryerson" />


https://meta.wikimedia.org/Wikimedia_Foundation_Board_noticeboard#13_years
====Privacy embedded into design====
Privacy by design is embedded into the design and architecture of IT systems as well as business practices. It is not bolted on as an add-on, after the fact. The result is that privacy becomes an essential component of the core functionality being delivered. Privacy is integral to the system without diminishing functionality.<ref name="7principlesFIPmapping" /><ref name="pbdPrimer" /><ref name="7P-Ryerson" />


https://meta.wikimedia.org/User_talk:Raystorm#Unanswered_question
====Full functionality – positive-sum, not zero-sum====
Privacy by design seeks to accommodate all legitimate interests and objectives in a positive-sum “win-win” manner, not through a dated, zero-sum approach, where unnecessary trade-offs are made. Privacy by design avoids the pretense of false dichotomies, such as privacy versus security, demonstrating that it is possible to have both.<ref name="7principlesFIPmapping" /><ref name="pbdPrimer" /><ref name="7P-Ryerson" />


https://en.wikipedia.org/Wikipedia:Wikipedia_Signpost/2016-11-26/Op-ed
====End-to-end security – full lifecycle protection====
Privacy by design, having been embedded into the system prior to the first element of information being collected, extends securely throughout the entire lifecycle of the data involved — strong security measures are essential to privacy, from start to finish. This ensures that all data are securely retained, and then securely destroyed at the end of the process, in a timely fashion. Thus, privacy by design ensures cradle-to-grave, secure lifecycle management of information, end-to-end.<ref name="7principlesFIPmapping" /><ref name="pbdPrimer" /><ref name="7P-Ryerson" />


https://en.wikipedia.org/Talk:Australia#Other_discussions_about_religion_in_country_infoboxes
====Visibility and transparency – keep it open====
Privacy by design seeks to assure all stakeholders that whatever the business practice or technology involved, it is in fact, operating according to the stated promises and objectives, subject to independent verification. Its component parts and operations remain visible and transparent, to users and providers alike. Remember, trust but verify.<ref name="7principlesFIPmapping" /><ref name="pbdPrimer" /><ref name="7P-Ryerson" />


https://search.creativecommons.org/
====Respect for user privacy – keep it user-centric====
Above all, privacy by design requires architects and operators to keep the interests of the individual uppermost by offering such measures as strong privacy defaults, appropriate notice, and empowering user-friendly options. Keep it user-centric.<ref name="7principlesFIPmapping" /><ref name="pbdPrimer" /><ref name="7P-Ryerson" />


https://wikimediafoundation.org/?noredirect=en_US
==Design and standards==
] (ISO) approved the Committee on Consumer Policy (COPOLCO) proposal for a new ISO standard: ''Consumer Protection: Privacy by Design for Consumer Goods and Services'' (ISO/PC317).<ref name="kIkIQ">{{cite web|title=ISO/PC 317 - Consumer protection: privacy by design for consumer goods and services|url=https://www.iso.org/committee/6935430.html}}</ref> The standard will aim to specify the design process to provide consumer goods and services that meet consumers’ domestic processing privacy needs as well as the personal privacy requirements of ]. The standard has the UK as secretariat with thirteen participating members<ref name="ISOPC317Members">{{cite web|title=ISO/PC 317 - Participating Members|url=https://www.iso.org/committee/6935430.html?view=participation}}</ref> and twenty observing members.<ref name="ISOPC317Members" />


https://en.wikipedia.org/search/?title=MediaWiki:Wikimedia-copyrightwarning&action=edit
The ] (SCC) is one of the participating members and has established a mirror Canadian committee to ISO/PC317.<ref name="xqVNM">{{cite web|title=SCC ISO/PC 317 - Consumer protection: privacy by design for consumer goods and services|url=https://www.scc.ca/en/standards/committees/iso-pc-317-consumer-protection-privacy-design-for-consumer-goods-and-services|date=2018-04-09}}</ref>


https://meta.wikimedia.org/Requests_for_comment/Superprotect_rights
The OASIS Privacy by Design Documentation for Software Engineers (PbD-SE)<ref name="OASIS">{{cite web|title=OASIS Privacy by Design Documentation for Software Engineers (PbD-SE) TC|url=https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=pbd-ses}}</ref> Technical Committee provides a specification to operationalize privacy by design in the context of software engineering. Privacy by design, like security by design, is a normal part of the software development process and a risk reduction strategy for software engineers. The PbD-SE specification translates the PbD principles to conformance requirements within software engineering tasks and helps software development teams to produce ]s as evidence of PbD principle adherence. Following the specification facilitates the documentation of privacy requirements from software conception to retirement, thereby providing a plan around adherence to privacy by design principles, and other guidance to privacy best practices, such as NIST’s 800-53 Appendix J (NIST SP 800-53) and the Fair Information Practice Principles (FIPPs) (PMRM-1.0).<ref name="OASIS" />


<!-- https://meta.wikimedia.org/Grants_talk:IdeaLab/Partnership_between_Wikimedia_community_and_Tor_community#Proposal:_Create_a_Wikipedia-only_read-only_Tor_exit_node -->
==Relationship to privacy-enhancing technologies==
Privacy by design originated from ] (PETs) in a joint 1995 report by Ann Cavoukian and John Borking.<ref name="Privacy Enhancing Technologies: the path to anonymity" /> In 2007 the ] provided a memo on PETs.<ref name="RRYdE">{{cite web|title=Privacy Enhancing Technologies (PETs)|url=http://europa.eu/rapid/press-release_MEMO-07-159_en.htm}}</ref> In 2008 the British Information Commissioner's Office commissioned a report titled ''Privacy by Design – An Overview of Privacy Enhancing Technologies''.<ref name="7Lfm1">{{cite web|title=Privacy by Design – An Overview of Privacy Enhancing Technologies|url=http://www.dsp.utoronto.ca/projects/surveillance/docs/pbd_pets_paper.pdf}}</ref>


Update ] with data from ?
There are many facets to privacy by design, including software and systems engineering<ref name="ddEzj">{{Cite journal|title=privacy and data protection by design from policy to engineering|journal=ENISA}}</ref> as well as administrative elements (e.g. legal, policy, procedural), other organizational controls, and operating contexts. Privacy by design evolved from early efforts to express fair information practice principles directly into the design and operation of information and communications technologies.<ref name="Z4Nc6">{{cite web|last=Cavoukian|first=Ann|title=Privacy by Design: Origins, Meaning, and Prospects for Assuring Privacy and Trust in the Information Era)|url=https://www.researchgate.net/publication/289769458}}</ref> In his publication ''Privacy by Design: Delivering the Promises''<ref name="deliveringthepromises" /> ] acknowledges the key role played by ] and John Borking, then Deputy Privacy Commissioners, in the joint 1995 publication ''Privacy-Enhancing Technologies: The Path to Anonymity''.<ref name="Privacy Enhancing Technologies: the path to anonymity" /> This 1995 report focussed on exploring technologies that permit transactions to be conducted anonymously.


And possibly https://grafana.wikimedia.org/d/000000002/api-backend-summary
Privacy-enhancing technologies allow online users to protect the privacy of their personally identifiable information (PII) provided to (and handled by) services or applications. Privacy by design evolved to consider the broader systems and processes in which PETs were embedded and operated. ] (CDT) in ''The Role of Privacy by Design in Protecting Consumer Privacy''<ref name="RoleProtectingConsumers">{{cite web|title=The Role of Privacy by Design in Protecting Consumer Privacy|url=https://cdt.org/insight/the-role-of-privacy-by-design-in-protecting-consumer-privacy-1/}}</ref> distinguishes PET from privacy by design noting that “PETs are most useful for users who already understand online privacy risks. They are essential user empowerment tools, but they form only a single piece of a broader framework that should be considered when discussing how technology can be used in the service of protecting privacy.”<ref name="RoleProtectingConsumers" />


https://en.wikiversity.org/Statistical_analysis_of_Wikimedia_Foundation_financial_reports
==Criticism and recommendations==
The privacy by design framework attracted academic debate, particularly following the 2010 International Data Commissioners resolution, these provide criticism of privacy by design with suggestions by legal and engineering experts to better understand how to apply the framework into various contexts.<ref name="Designing Privacy by Design" /><ref name="Engineering Privacy by Design" /><ref name="Counterfactual" />


https://en.wikipedia.org/File:Wikimedia_Foundation%27s_expenses_evolution_by_rubrics_in_US_Dollars.svg
Privacy by design has been critiqued as "vague"<ref name="Designing Privacy by Design">{{cite book|last=van Rest|first=Jeroen|title=Designing Privacy by Design|volume=8319|pages=55–72|doi=10.1007/978-3-642-54069-1_4|chapter=Designing Privacy-by-Design|series=Lecture Notes in Computer Science|year=2014|isbn=978-3-642-54068-4}}</ref> and leaving "many open questions about their application when engineering systems."<ref name="Engineering Privacy by Design">{{cite web|title=Engineering Privacy by Design|url=http://www.cosic.esat.kuleuven.be/publications/article-1542.pdf|work=Seda Gurses, ], and Claudia Diaz}}</ref>


https://en.wikipedia.org/Predatory_open_access_publishing#Beall.27s_List
In 2007, researchers at K.U. Leuven published ''Engineering Privacy by Design'' noting that “The design and implementation of privacy requirements in systems is a difficult problem and requires translation of complex social, legal and ethical concerns into systems requirements”. The authors claim that their statement regarding that the principles of privacy by design "remain vague and leave many open questions about their application when engineering systems", may be viewed as criticism. However, the purpose of the paper is to propose that "starting from data minimization is a necessary and foundational first step to engineer systems in line with the principles of privacy by design". The objective of their paper is to provide an "initial inquiry into the practice of privacy by design from an engineering perspective in order to contribute to the closing of the gap between policymakers’ and engineers’ understanding of privacy by design."<ref name="Engineering Privacy by Design" />


https://upload.wikimedia.org/wikipedia/en/4/40/NPP_flowchart.png
It has also been pointed out that privacy by design is similar to ] schemes in industries impacting the environment, and thus lacks the teeth necessary to be effective, and may differ per company. In addition, the evolutionary approach currently taken to the development of the concept will come at the cost of privacy infringements because evolution implies also letting unfit phenotypes (privacy-invading products) live until they are proven unfit.<ref name="Designing Privacy by Design" /> Some critics have pointed out that certain business models are built around customer surveillance and data manipulation and therefore voluntary compliance is unlikely.<ref name="Counterfactual">{{cite journal|date=2012-08-11|title=Privacy by Design: A Counterfactual Analysis of Google and Facebook Privacy Incidents|url=https://papers.ssrn.com/sol3/papers.cfm?abstract_id=2128146|journal=Ira Rubinstein and Nathan Good|ssrn=2128146}}</ref>


https://www.mediawiki.org/Help:CirrusSearch#Regular_expression_searches
In 2011, the Danish National It and Telecom Agency published as a discussion paper on "New Digital Security Models" the publication references "Privacy by Design" as a key goal in creating a security model that is compliant with "Privacy by Design." This is done by extending the concept to "Security by Design" with an objective of balancing anonymity and surveillance by eliminating identification as much as possible.<ref name="New Digital Security Models">{{cite web|title=New Digital Security Models|url=https://www.digitaliser.dk/resource/896495/artefact/NewDigitalSecurityModels.pdf?artefact=true&PID=1792137|work=Danish National It and Telecom Agency}}</ref>


https://en.wikipedia.org/Special:ListUsers
In 2013, Rubinstein and Good used ] and ] privacy incidents to conduct a counterfactual analysis in order to identify lessons learned of value for regulators when recommending privacy by design. The first was that “more detailed principles and specific examples” would be more helpful to companies. The second is that “usability is just as important as engineering principles and practices”. The third is that there needs to be more work on “refining and elaborating on design principles–both in privacy engineering and usability design”. including efforts to define international privacy standards. The final lesson learned is that “regulators must do more than merely recommend the adoption and implementation of privacy by design.”<ref name="Counterfactual" />


== Temporary stuff I might need later 02 ==
Another criticism is that current definitions of privacy by design do not address the methodological aspect of systems engineering, such as using decent system engineering methods, e.g. those which cover the complete system and data life cycle. The concept also does not focus on the role of the actual data holder but on that of the system designer. This role is not known in privacy law, so the concept of privacy by design is not based on law. This, in turn, undermines the trust by data subjects, data holders and policy-makers.<ref name="Designing Privacy by Design" />


’Twas brillig, and the slithy toves did gyre and gimble in the wabe: All mimsy were the borogoves, and the mome raths outgrabe. “Beware the Jabberwock, my son! The jaws that bite, the claws that catch! Beware the Jubjub bird, and shun the frumious Bandersnatch!” He took his vorpal sword in hand; Long time the manxome foe he sought— So rested he by the Tumtum tree and stood awhile in thought. And, as in uffish thought he stood, the Jabberwock, with eyes of flame, Came whiffling through the tulgey wood, and burbled as it came! One, two! One, two! And through and through the vorpal blade went snicker-snack! He left it dead, and with its head he went galumphing back. “And hast thou slain the Jabberwock? Come to my arms, my beamish boy! O frabjous day! Callooh! Callay!” he chortled in his joy. ’Twas brillig, and the slithy toves did gyre and gimble in the wabe: all mimsy were the borogoves, and the mome raths outgrabe.
The advent of ] with its maximum fine of 4% of global turnover now provides a balance between business benefit and turnover and addresses the ] criticism and requirement from Rubinstein and Good that “regulators must do more than merely recommend the adoption and implementation of privacy by design”.<ref name="Counterfactual" /> Rubinstein and Good also highlighted that privacy by design could result in applications that exemplified Privacy by Design and their work was well received.<ref name="CorporateHotness">{{cite web|title=Why 'Privacy By Design' Is The New Corporate Hotness|url=https://www.forbes.com/sites/kashmirhill/2011/07/28/why-privacy-by-design-is-the-new-corporate-hotness|work=Kashmir Hill}}</ref><ref name="Counterfactual" />
* https://en.wikibooks.org/Using_Wikibooks
* https://en.wikibooks.org/Wikibooks:What_is_Wikibooks
* https://en.wikibooks.org/Using_Wikibooks/Starting_A_New_Wikibook
* https://en.wikibooks.org/Wikibooks:Reading_room/Assistance#Experienced_Wikipedia_editor_wanting_to_get_started_on_Wikibooks
* https://en.wikiversity.org/Mathematics_software
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*


== Temporary stuff I might need later 03 ==
The May 2018 ] ]'s paper ''Preliminary Opinion on Privacy by Design'' states, "While privacy by design has made significant progress in legal, technological and conceptual development, it is still far from unfolding its full potential for the protection of the fundamental rights of individuals. The following sections of this opinion provide an overview of relevant developments and recommend further efforts".<ref name="Opinion">{{cite web|title=Preliminary Opinion on privacy by design|url=https://edps.europa.eu/sites/edp/files/publication/18-05-31_preliminary_opinion_on_privacy_by_design_en_0.pdf|work=Giovanni Buttarelli}}</ref>


] and or * ] AKA unroutable addresses:
The executive summary makes the following recommendations to EU institutions:
* ]
* To ensure strong privacy protection, including privacy by design, in the ],
* ]
* To support privacy in all legal frameworks which influence the design of technology, increasing incentives and substantiating obligations, including appropriate liability rules,
* ]
* To foster the roll-out and adoption of privacy by design approaches and PETs in the EU and at the member states’ level through appropriate implementing measures and policy initiatives,
* ]
* To ensure competence and resources for research and analysis on privacy engineering and privacy-enhancing technologies at EU level, by ENISA or other entities,
* ]
* To support the development of new practices and business models through the research and technology development instruments of the EU,
* ]
* To support EU and national public administrations to integrate appropriate privacy by design requirements in public procurement,
* ]
* To support an inventory and observatory of the “state of the art” of privacy engineering and PETs and their advancement.
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]


]s AKA Open DNS Servers
The EDPS will:
* ]
* Continue to promote privacy by design, where appropriate in cooperation with other data protection authorities in the ] (EDPB),
* ]
* Support coordinated and effective enforcement of Article 25 of the GDPR and related provisions,
* ]
* Provide guidance to controllers on the appropriate implementation of the principle laid down in the legal base, and
* ]
* Together with ] of Austria, Ireland and Schleswig-Holstein, award privacy friendly apps in the mobile health domain.<ref name="Opinion" />
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]


== Temporary stuff I might need later 04 ==
==Implementing privacy by design==
The ] ] set out the requirement to implement privacy by design in his article.<ref name="upRbo">{{cite web|title=Privacy by Design - Privacy Engineering|url=https://edps.europa.eu/sites/edp/files/publication/18-01-25_privacy_by_design_privacy_engineering_cpdp_en_3.pdf|work=Giovanni Buttarelli}}</ref> The ] (ENISA) provided a detailed report ''Privacy and Data Protection by Design – From Policy to Engineering'' on implementation.<ref name="7hMKb">{{cite web|title=Privacy and Data Protection by Design – from policy to engineering|url=https://www.enisa.europa.eu/publications/privacy-and-data-protection-by-design/at_download/fullReport|work=ENISA}}</ref> The Summer School on real-world crypto and privacy provided a tutorial on "Engineering Privacy by Design".<ref name="GWDwv">{{cite web|title=Engineering privacy by design|url=https://summerschool-croatia.cs.ru.nl/2017/slides/Engineering%20privacy%20by%20design.pdf}}</ref> The for web applications that gives hints on how to implement privacy by design in practice. The OASIS Privacy by Design Documentation for Software Engineers (PbD-SE)<ref name="OASIS" /> offers a privacy extension/complement to OMG’s Unified Modeling Language (UML) and serves as a complement to OASIS’ eXtensible Access Control Mark-up Language (XACML) and Privacy Management Reference Model (PMRM). Privacy by Design guidelines are developed to operationalise some of the high-level privacy-preserving ideas into more granular actionable advice.<ref name="jAr6e">{{Cite journal|last1=Perera|first1=Charith|last2=Barhamgi|first2=Mahmoud|last3=Bandara|first3=Arosha K.|last4=Ajmal|first4=Muhammad|last5=Price|first5=Blaine|last6=Nuseibeh|first6=Bashar|date=February 2020|title=Designing privacy-aware internet of things applications|url=https://linkinghub.elsevier.com/retrieve/pii/S0020025519309120|journal=Information Sciences|language=en|volume=512|pages=238–257|doi=10.1016/j.ins.2019.09.061|s2cid=60044}}</ref><ref name="cqpih">{{Cite web|title=Implementing Privacy By Design|url=https://www.privacypolicies.com/blog/privacy-by-design/|access-date=2020-12-13|website=Privacy Policies|language=en}}</ref>


Do we really need all of these?
==See also==
* ] * ]
* ]
* ]
* ]
* ]
* ] * ]
** ] * ]
** ] * ]
** ] * ]
* ] * ]
* ] * ]
* ]
* ]
* ] * ]
* ] * ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]
* ]


Perhaps a list of apartment types (for long term rentals) and a list of hotel types (for short term rentals) could encompass them all... --] (]) 19:11, 25 May 2020 (UTC)
==References==
{{reflist}}


== Temporary stuff I might need later 05 ==
{{Design}}


===Refname test ===
]
* Refname test #1: <ref name="foo-11"></ref> (bare URL:)
]
* Refname test #2: <ref name="-12"></ref> (bare URL:)
]
* Refname test #3: <ref name="13"></ref> (bare URL:)
]
* Refname test #4: <ref name="14-"></ref> (bare URL:)
* Refname test #5: <ref name="Fifteen"></ref> (bare URL:)
* Refname test #6: <ref name=" "></ref> (bare URL:)
{{reflist-talk}}

Note that Reference #3 silently disapears. That's because Misplaced Pages doesn't allow a positive integer but does allow a negative integer as the refname. It also adds a newline, which appears to be a bug. --] (])

Misplaced Pages:Requests for adminship/Guy Macon

== Copyright (lack of copyright, actually) notice ==

{{CC-0 Release}}

Revision as of 08:54, 2 May 2021

https://w.wiki/3d7

Some random editor says that something is wrong with this page. That editor can't be troubled to fix it or even discuss it on the article talk page, but we can all sleep easy knowing that they stuck on a tag.
Please allow this tag to languish indefinitely at the top of this page, since nobody knows exactly why it is here.

A Sandbox is a place to experiment with editing Misplaced Pages pages. This is Guy Macon's personal sandbox.

What is a sandbox?

This is Guy Macon's personal sandbox. Misplaced Pages:Sandbox is a sandbox that anyone can use -- see Misplaced Pages:About the Sandbox for details.

Temporary stuff I might need later 01

User:Guy Macon/WikiURLs

meta:Office actions/Community consultation on partial and temporary office actions/draft

meta:Talk:Office actions/Community consultation on partial and temporary office actions/draft

https://en.wikipedia.org/User_talk:Doc_James#13_years

https://en.wikipedia.org/Wikipedia:Administrators%27_noticeboard#Suggestion

https://en.wikipedia.org/User_talk:Jimbo_Wales/Archive_236#13_years

https://phabricator.wikimedia.org/T6845

https://meta.wikimedia.org/Talk:Wikimedia_Foundation_Board_of_Trustees#13_years

https://meta.wikimedia.org/Wikimedia_Foundation_Board_noticeboard#13_years

https://meta.wikimedia.org/User_talk:Raystorm#Unanswered_question

https://en.wikipedia.org/Wikipedia:Wikipedia_Signpost/2016-11-26/Op-ed

https://en.wikipedia.org/Talk:Australia#Other_discussions_about_religion_in_country_infoboxes

https://search.creativecommons.org/

https://wikimediafoundation.org/?noredirect=en_US

https://en.wikipedia.org/search/?title=MediaWiki:Wikimedia-copyrightwarning&action=edit

https://meta.wikimedia.org/Requests_for_comment/Superprotect_rights


Update Misplaced Pages:Downtime with data from ?

And possibly https://grafana.wikimedia.org/d/000000002/api-backend-summary

https://en.wikiversity.org/Statistical_analysis_of_Wikimedia_Foundation_financial_reports

https://en.wikipedia.org/File:Wikimedia_Foundation%27s_expenses_evolution_by_rubrics_in_US_Dollars.svg

https://en.wikipedia.org/Predatory_open_access_publishing#Beall.27s_List

https://upload.wikimedia.org/wikipedia/en/4/40/NPP_flowchart.png

https://www.mediawiki.org/Help:CirrusSearch#Regular_expression_searches

https://en.wikipedia.org/Special:ListUsers

Temporary stuff I might need later 02

’Twas brillig, and the slithy toves did gyre and gimble in the wabe: All mimsy were the borogoves, and the mome raths outgrabe. “Beware the Jabberwock, my son! The jaws that bite, the claws that catch! Beware the Jubjub bird, and shun the frumious Bandersnatch!” He took his vorpal sword in hand; Long time the manxome foe he sought— So rested he by the Tumtum tree and stood awhile in thought. And, as in uffish thought he stood, the Jabberwock, with eyes of flame, Came whiffling through the tulgey wood, and burbled as it came! One, two! One, two! And through and through the vorpal blade went snicker-snack! He left it dead, and with its head he went galumphing back. “And hast thou slain the Jabberwock? Come to my arms, my beamish boy! O frabjous day! Callooh! Callay!” he chortled in his joy. ’Twas brillig, and the slithy toves did gyre and gimble in the wabe: all mimsy were the borogoves, and the mome raths outgrabe.

Temporary stuff I might need later 03

Private networks and or * Reserved IP addresses AKA unroutable addresses:

Public recursive name servers AKA Open DNS Servers

Temporary stuff I might need later 04

Do we really need all of these?

Perhaps a list of apartment types (for long term rentals) and a list of hotel types (for short term rentals) could encompass them all... --Guy Macon (talk) 19:11, 25 May 2020 (UTC)

Temporary stuff I might need later 05

Refname test

  • Refname test #1: (bare URL:)
  • Refname test #2: (bare URL:)
  • Refname test #3: Cite error: The <ref> tag name cannot be a simple integer (see the help page). (bare URL:)
  • Refname test #4: (bare URL:)
  • Refname test #5: (bare URL:)
  • Refname test #6: (bare URL:)

References

  1. Refname test #1
  2. Refname test #2
  3. Refname test #4
  4. Refname test #5
  5. Refname test #6

Note that Reference #3 silently disapears. That's because Misplaced Pages doesn't allow a positive integer but does allow a negative integer as the refname. It also adds a newline, which appears to be a bug. --Guy Macon (talk)

Misplaced Pages:Requests for adminship/Guy Macon

Copyright (lack of copyright, actually) notice

Released into public domain
I agree to release my text and image contributions, unless otherwise stated, under the terms of the Creative Commons Zero license. Please be aware that other contributors might not do the same, so if you want to use my contributions under Creative Commons Zero terms, please check the multi-licensing guide.
Category: