This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "OWASP Top 10 Privacy Risks Project"

From OWASP
Jump to: navigation, search
m
 
(199 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
=Main=
 
=Main=
  
−
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>
+
<div style="width:100%;height:90px;border:0,margin:0;overflow: hidden;">[[File: lab_big.jpg|link=OWASP_Project_Stages#tab.3DLab_Projects]]</div>
  
 
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
−
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
+
| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |
  
−
==OWASP Top 10 Privacy Risks Project in a nutshell==
+
==The project in a nutshell==
−
 
 
−
The OWASP Top 10 Privacy Risks Project aims to develop a top 10 list for privacy risks in web applications because currently there is no such catalog available. The list will cover technological and organizational aspects like missing data encryption or the lack of transparency.
 
−
 
 
−
 
 
−
==Introduction==
 
−
 
 
−
Discussions about how to protect privacy and personal data are ongoing and mostly pushed by lawyers and legal experts. But there is no specific description of privacy risks for web applications that companies can apply during development and for users to check whether their privacy is protected well. There are helpful concepts like Privacy by Design, but no detailed description of real life risks causing incidents and privacy breaches in practice. This project will mitigate this gap and create a Top 10 list with technical and organizational privacy risks in web applications and possible counter-measures. Beyond that, we want to raise the awareness of the management and people who are involved in creating and operating web applications for privacy risks during the SDLC and the usage of the data, bring visibility to the right issues and create a community of people that gives practical input for further developement of this project.
 
  
 +
The OWASP Top 10 Privacy Risks Project provides a top 10 list for privacy risks in web applications and related countermeasures. It covers technological and organizational aspects that focus on real-life risks, not just legal issues. The Project provides tips on how to implement privacy by design in web applications with the aim of helping developers and web application providers to better understand and improve privacy. The list uses the OECD Privacy Guidelines as a framework and can also be used to assess privacy risks associated with specific web applications.
  
 
==Top 10 Privacy Risks==
 
==Top 10 Privacy Risks==
  
−
Under development.
+
:P1&nbsp;&nbsp;&nbsp;&nbsp;Web Application Vulnerabilities
−
 
+
:P2&nbsp;&nbsp;&nbsp;&nbsp;Operator-sided Data Leakage
−
 
+
:P3&nbsp;&nbsp;&nbsp;&nbsp;Insufficient Data Breach Response
−
==Licensing==
+
:P4&nbsp;&nbsp;&nbsp;&nbsp;Insufficient Deletion of personal data
−
OWASP Top 10 Privacy Risks Project is free to use. It is licensed under the GNU GPL v3 License.
+
:P5&nbsp;&nbsp;&nbsp;&nbsp;Non-transparent Policies, Terms and Conditions
−
 
+
:P6&nbsp;&nbsp;&nbsp;&nbsp;Collection of data not required for the primary purpose
−
 
+
:P7&nbsp;&nbsp;&nbsp;&nbsp;Sharing of data with third party
−
| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
+
:P8&nbsp;&nbsp;&nbsp;&nbsp;Outdated personal data
 +
:P9&nbsp;&nbsp;&nbsp;&nbsp;Missing or Insufficient Session Expiration
 +
:P10&nbsp;&nbsp;Insecure Data Transfer
 +
Further information is provided in the Top 10 Privacy Risks tab.
  
 
== Contact us ==
 
== Contact us ==
  
−
* Primary: [mailto:Stefan.Burgmair@owasp.org Stefan Burgmair]
+
{{Template:Contact
−
* Secondary: [mailto:florian.stahl@owasp.org Florian Stahl]
+
| name = Florian Stahl
 +
| email = florian.stahl@owasp.org
 +
| username = Florian_Stahl
 +
}}<br />
 +
Stefan Burgmair [mailto:Stefan.Burgmair@owasp.org @]
  
 +
== Quick Download ==
  
−
== Project Leader ==
+
* [https://www.owasp.org/images/0/0a/OWASP_Top_10_Privacy_Countermeasures_v1.0.pdf Top 10 Privacy Risks Countermeasures v1.0 (PDF)]
 +
* [https://www.owasp.org/images/d/df/OWASP_Top10PrivacyRisks_20150529.pptx Top 10 Privacy Risks Presentation (PPTX)]
 +
* [https://www.owasp.org/images/6/6f/OWASPTop10PrivacyRisks_20141209.pdf Results presentation at German OWASP Day 2014]
 +
* [https://www.owasp.org/images/c/c3/Top10PrivacyRisks_IAPP_Summit_2015.pdf Presentation from IAPP Global Privacy Summit 2015]
 +
* [https://www.owasp.org/images/2/27/Presentation_HowToBoostPrivacy_IAPP_Intensive_2016.pdf Presentation of countermeasures from IAPP Data Protection Intensive 2016]
  
−
[https://www.owasp.org/index.php/User:Florian_Stahl Florian Stahl]
+
==Licensing==
 +
OWASP Top 10 Privacy Risks Project is free to use. It is licensed under the Creative Commons CC-BY-SA v3.0 License.
  
 +
| style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |
  
−
== Related Projects ==
+
== Download Infographic version ==
 +
[[File:Top_10_Risks.png | 200px]]
  
−
* [https://www.owasp.org/index.php/Projects/OWASP_Mobile_Security_Project_-_Top_Ten_Mobile_Risks OWASP Top 10 Mobile Risks]
+
| style="padding-left:25px;width:200px;" valign="top" |
−
* [https://www.owasp.org/index.php/OWASP_Security_Labeling_System_Project OWASP Security Labeling System Project]
 
  
−
 
+
== News ==
−
 
+
* [Ongoing] Update of the OWASP Top 10 Privacy Risks
−
| valign="top"  style="padding-left:25px;width:200px;" |
+
* [8 April 2016] Countermeasures v1.0 published
−
 
+
* [1 July 2015] German Translation available
−
== News and Events ==
+
* [21 Sep 2014] Top 10 Privacy Risks v1.0 published
 
* [20 Feb 2014] Project Start
 
* [20 Feb 2014] Project Start
−
* [07 Apr 2014] Method draft
 
−
* [04 Jul 2014] Draft list
 
−
* [04 Aug 2014] Survey started
 
−
* [26 Aug 2014] Survey results published
 
−
 
−
 
−
 
−
== Quick Download ==
 
−
 
−
* [https://docs.google.com/document/d/1nHM9LH2rP6ac3DvJ7lehDNb9qVP5YADOQGNEuiy5okg/edit?usp=sharing Method in Google Docs]
 
−
* [https://docs.google.com/document/d/1WMljvy09nulPnzv5XkFc2uxn1bSR-ftKqx5VoayTzW8/edit Draft list of 20 Privacy Risks]
 
−
* [https://www.owasp.org/images/c/c8/PrivacyTop10Survey.pdf Survey results]
 
−
 
  
 
== External Links ==
 
== External Links ==
 
[http://www.oecd.org/sti/ieconomy/2013-oecd-privacy-guidelines.pdf OECD Privacy Guidelines]
 
[http://www.oecd.org/sti/ieconomy/2013-oecd-privacy-guidelines.pdf OECD Privacy Guidelines]
−
[https://soundcloud.com/owasp-podcast/owasp-top-10-privacy-risks-project-with-florian-stahl-and-stefan-burgmair Podcast about the project]
+
[https://secure.edps.europa.eu/EDPSWEB/edps/EDPS/IPEN Internet Privacy Engineering Network - IPEN]<br>
−
[https://secure.edps.europa.eu/EDPSWEB/edps/EDPS/IPEN Internet Privacy Engineering Network - IPEN
+
[https://www.youtube.com/watch?v=mO7bjmUAq-Q Video from IPEN workshop at Berlin state parliament]<br>
−
 
+
[https://www.youtube.com/watch?v=6SEdnWlSZyk Video from panel discussion at CPDP 2015 in Brussels]<br>
 +
[https://www.youtube.com/watch?v=WXSZiWNyPZA Video from presentation at AppSec EU 2015]<br>
 +
[https://privacyscore.org/ Check your website with PRIVACYSCORE]
  
 
==Classifications==
 
==Classifications==
Line 73: Line 70:
 
   {| width="200" cellpadding="2"
 
   {| width="200" cellpadding="2"
 
   |-
 
   |-
−
   | align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]
+
   | rowspan="2" width="50%" valign="top" align="center" | [[File:Midlevel projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Lab_Projects]]
−
   | align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=]]   
+
   | width="50%" valign="top" align="center" | [[File:Owasp-builders-small.png|link=]]   
 
   |-
 
   |-
−
   | align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=]]
+
   | width="50%" valign="top" align="center" | [[File:Owasp-defenders-small.png|link=]]
 
   |-
 
   |-
−
   | colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]]
+
   | colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]]
 
   |-
 
   |-
−
   | colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]]
+
   | colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]]
 
   |}
 
   |}
  
 
|}
 
|}
  
−
=FAQs=
+
=Top 10 Privacy Risks=
  
−
; Why is this project only about web applications and not about any kind of software?
+
==Top 10 Privacy Risks 2014==
−
: Web applications can easily collect data from users without their permission or informing them about the usage of their data. Trackers and cookies deliberately enable the monitoring of the users behaviour, often for selling those data. That is the reason why this subject is so important, especialy for web applications.
 
  
−
; What is the difference between this project and the OWASP top 10?
+
Version 1.0 of the OWASP Top 10 Privacy Risks list. Further information and related countermeasures are provided in [https://www.owasp.org/images/0/0a/OWASP_Top_10_Privacy_Countermeasures_v1.0.pdf this PDF document].
−
: There are two main differences. First, the OWASP top 10 describes technical risks, that are not primarily affecting privacy. Second, the OWASP top 10 does neither regard intended parts of the software like cookies or trackers nor organisational issues like privacy agreements or profiling.
 
  
−
; Why should companys and other organisations be concerned about privacy risks?
+
<table style="background-color:#FFFFFF;border-collapse:collapse;border:1px solid #000000;color:#000000;width:100%" cellspacing="3" cellpadding="3" border="1">
−
: Privacy risks may have serious consequences for an organisation, such as:  
+
<tr>
−
* perceived harm to privacy;
+
<td bgcolor="#D8D8D8"><b>No.</b></td>
−
* a failure to meet public expectations on the protection of personal information;
+
<td bgcolor="#D8D8D8"><b>Title</b></td>
−
* retrospective imposition of regulatory conditions;
+
<td bgcolor="#D8D8D8"><b>Frequency</b></td>
−
* low adoption rates or poor participation in the scheme from both the public and partner organisations;
+
<td bgcolor="#D8D8D8"><b>Impact&nbsp;&nbsp;&nbsp;&nbsp;</b></td>
−
* the costs of redesigning the system or retro-fitting solutions;
+
<td bgcolor="#D8D8D8"><b>Description</b></td>
−
* collapse of a project or completed system;
 
−
* withdrawal of support from key supporting organisations due to perceived privacy harms; and/ or
 
−
* failure to comply with the law, leading to enforcement action from the regulator or compensation claims from individuals.
 
−
(Source: http://ico.org.uk/pia_handbook_html_v2/html/1-Chap2-2.html)
 
  
 +
</tr>
 +
<tr>
 +
<td>P1</td>
 +
<td>Web Application Vulnerabilities</td>
 +
<td bgcolor="orange">High</td>
 +
<td bgcolor="red">Very high</td>
 +
<td>Vulnerability is a key problem in any system that guards or operates on sensitive user data. Failure to suitably design and implement an application, detect a problem or promptly apply a fix (patch) is likely to result in a privacy breach. This risk also encompasses the OWASP Top 10 List of web application vulnerabilities and the risks resulting from them.
 +
</td>
 +
</tr>
 +
<tr>
 +
<td>P2</td>
 +
<td>Operator-sided Data Leakage</td>
 +
<td bgcolor="orange">High</td>
 +
<td bgcolor="red">Very high</td>
 +
<td>Failure to prevent the leakage of any information containing or related to user data, or the data itself, to any unauthorized party resulting in loss of data confidentiality. Introduced either due to intentional malicious breach or unintentional mistake e.g. caused by insufficient access management controls, insecure storage, duplication of data or a lack of awareness.
 +
</td>
 +
</tr>
 +
<tr>
 +
<td>P3</td>
 +
<td>Insufficient Data Breach Response</td>
 +
<td bgcolor="orange">High</td>
 +
<td bgcolor="red">Very high</td>
 +
<td>Not informing the affected persons (data subjects) about a possible breach or data leak, resulting either from intentional or unintentional events; failure to remedy the situation by fixing the cause; not attempting to limit the leaks.
 +
</td>
 +
</tr>
 +
<tr>
 +
<td>P4</td>
 +
<td>Insufficient Deletion of Personal Data</td>
 +
<td bgcolor="red">Very high</td>
 +
<td bgcolor="orange">High</td>
 +
<td>Failure to effectively and/or timely delete personal data after termination of the specified purpose or upon request.
 +
</td>
 +
</tr>
 +
<tr>
 +
<td>P5</td>
 +
<td>Non-transparent Policies, Terms and Conditions</td>
 +
<td bgcolor="red">Very high</td>
 +
<td bgcolor="orange">High</td>
 +
<td>Not providing sufficient information to describing how data is processed, such as its collection, storage, and processing. Failure to make this information easily-accessible and understandable for non-lawyers.
 +
</td>
 +
</tr>
 +
<tr>
 +
<td>P6</td>
 +
<td>Collection of data not required for the primary purpose</td>
 +
<td bgcolor="red">Very high</td>
 +
<td bgcolor="orange">High</td>
 +
<td>Collecting descriptive, demographic or any other user-related data that are not needed for the purposes of the system. Applies also to data for which the user did not provide consent.
 +
</td>
 +
</tr>
 +
<tr>
 +
<td>P7</td>
 +
<td>Sharing of Data with Third Party</td>
 +
<td bgcolor="orange">High</td>
 +
<td bgcolor="orange">High</td>
 +
<td>Providing user data to any third-party, without obtaining the user’s consent. Sharing results either due to transfer or exchanging for a monetary compensation or otherwise due to inappropriate use of third-party resources included in the web site like widgets (e.g. maps, social networks buttons), analytics or web bugs (e.g. beacons).
 +
</td>
 +
</tr>
 +
<tr>
 +
<td>P8</td>
 +
<td>Outdated personal data</td>
 +
<td bgcolor="orange">High</td>
 +
<td bgcolor="red">Very high</td>
 +
<td>The use of outdated, incorrect or bogus user data. Failure to update or correct the data.
 +
</td>
 +
</tr>
 +
<tr>
 +
<td>P9</td>
 +
<td>Missing or insufficient Session Expiration</td>
 +
<td bgcolor="yellow">Medium</td>
 +
<td bgcolor="red">Very high</td>
 +
<td>Failure to effectively enforce session termination. May result in collection of additional user-data without the user’s consent or awareness.
 +
</td>
 +
</tr>
 +
<tr>
 +
<td>P10</td>
 +
<td>Insecure Data Transfer</td>
 +
<td bgcolor="yellow">Medium</td>
 +
<td bgcolor="red">Very high</td>
 +
<td>Failure to provide data transfers over encrypted and secured channels, excluding the possibility of data leakage. Failure of enforcing mechanisms limiting the leak surface, e.g. allowing to infer any user data out of the mechanics of Web application operation.</td>
 +
</tr>
 +
</table>
 +
Note: The values between 0 to 3 used for frequency and impact rating were replaced by a textual description: 0-1: Low, 1-1.5: Medium, 1.5-2: High, > 2: Very high
  
−
= Acknowledgements =
+
= Participation and Discussion =
−
==Volunteers==
 
−
The Top 10 Privacy Risk list is developed by a team of volunteers. The primary contributors to date have been:
 
  
−
* Stefan Burgmair
+
==Participate==
−
* R. Jason Cronk
 
−
* Edward Delaporte
 
−
* Prof. Hans-Joachim Hof
 
−
* Florian Stahl
 
  
−
==Partners==
+
Some ways you can help:
−
* [http://www.cs.hm.edu/en/home/index.en.html University of Applied Sciences Munich]
+
* Discuss with us in the mailing list or Google docs
−
* [https://secure.edps.europa.eu/EDPSWEB/edps/EDPS/IPEN European Data Protection Supervisory's Internet Privacy Engineering Network (IPEN)]
+
* Tell your colleagues and friends about the project
−
* [http://privacyassociation.org/ International Association of Privacy Professionals (IAPP)]
+
* Provide feedback (feel free to contact us)
 +
* Apply the results in practice to improve web application privacy
  
−
==Sponsors==
+
Sign up to our [https://groups.google.com/a/owasp.org/forum/#!forum/top-10-privacy-risks-project/join mailing list] to stay informed.
−
* [http://www.msg-systems.com/ msg systems]
 
  
−
= Road Map and Getting Involved =
+
==Discussions and Documentation==
−
As of February 2014, the proceeding is:
 
−
* Collection of interested participants and supporters (building a team) – until march 14
 
−
* Developing a method for identifying the risks – until mid-march 2014
 
−
* Creating a draft list of risks - until first week of april 2014
 
−
* Discussing the draft list - until end of april 2014
 
−
* Developing a rating method - until end of april 2014
 
−
* Rating the risks, creating the list of Top 10 Privacy Risks (Version 1.0) and discus the results - until end of may 2014
 
−
* Creating papers, best practices, etc. - Q3/2014
 
−
* Ongoing improvement, rerating etc. - Q3/2014
 
  
−
Involvement in the development and promotion of the project is actively encouraged!
+
To avoid overwriting issues we use Google Docs for our discussions.
−
You do not have to be a security or privacy expert in order to contribute.
 
−
Some of the ways you can help:
 
−
* Discuss with us at the Forum for Discussions and Progress
 
−
* Answer the questionnaire for identifying and rating the Top 10 privacy list (will be provided soon)
 
−
* Tell your colleagues and friends about the project
 
−
* Provide feedback and input (feel free to contact us)
 
  
−
Sign up to our [https://lists.owasp.org/mailman/listinfo/owasp_top_10_privacy_risks_project mailing list] to stay informed.
+
===Update 2019-2020===
 +
Impact rating (open discussion): https://docs.google.com/document/d/1VuusvZnhHpWvmPFeAovM68iB_Do3XFZCH2EsITGuAKg/edit<br>
 +
Privacy Risk Candidate List: https://docs.google.com/document/d/1eEU7TsoaPG56-zhJi4bi1SD53Jto84GQ8dDGTajL8TY/edit<br>
 +
Method Update: https://docs.google.com/document/d/1AlAg2cybvo5VX-frzF5uHeAcib3X2rTAA2p97XH8fHw/edit
  
−
=Forum for Discussions and Progress=
+
===Closed discussions and documents===  
−
To avoid overwriting issues we will use google docs for our discussions.
+
Countermeasures document: https://docs.google.com/document/d/1GaoJDPtyXMv09wIw9xXTVPYTR_6fQROlptszPhxVc1s/edit?usp=sharing
−
+
<br>Method: https://docs.google.com/document/d/1nHM9LH2rP6ac3DvJ7lehDNb9qVP5YADOQGNEuiy5okg/edit
−
:Method: https://docs.google.com/document/d/1nHM9LH2rP6ac3DvJ7lehDNb9qVP5YADOQGNEuiy5okg/edit
+
<br>Privacy Risk list 2014: https://docs.google.com/document/d/1ufAuGtW42gUHtJF-9_VOzNZEegZJnMyqDcyfzmsjJeQ/edit
−
:Privacy Risk List 2014: https://docs.google.com/document/d/1ufAuGtW42gUHtJF-9_VOzNZEegZJnMyqDcyfzmsjJeQ/edit
+
<br>Draft list: https://docs.google.com/document/d/1WMljvy09nulPnzv5XkFc2uxn1bSR-ftKqx5VoayTzW8/edit
−
:Draft list (already closed for 2014): https://docs.google.com/document/d/1WMljvy09nulPnzv5XkFc2uxn1bSR-ftKqx5VoayTzW8/edit  
+
<br>Impact rating: https://docs.google.com/a/owasp.org/document/d/1Gjd5XVJyGWHryUA2WyPSRQ0gQuaD5zWUCHU76_FHMKU/edit
 +
<br>Calculation of the complete Privacy Risks list v1.0: https://docs.google.com/spreadsheets/d/1q7Xh4gclSieXNpVbdvyFwsZMENo2r3BoN2S3ww_W5-M/edit
 +
<br>Brainstorming for countermeasures: https://docs.google.com/a/owasp.org/document/d/1g4Q_XDVGEAbVR_7DLNIbDN2men57BQ0pNn8CyRc2od8/edit
  
−
=Survey=
+
==Survey Results==
−
==OWASP Top 10 Privacy Risks Survey==
 
  
 
A survey was performed to determine the frequency of occurrence of privacy violations in web applications.
 
A survey was performed to determine the frequency of occurrence of privacy violations in web applications.
Line 310: Line 366:
 
Average Rating: 2.6
 
Average Rating: 2.6
  
 +
=FAQs=
 +
 +
==Frequently Asked Questions==
 +
 +
===Why is this project only about web applications and not about any kind of software?===
 +
Web applications can easily collect data from users without their permission or without adequately informing them how their data is used. Cookies, and other trackers, enable the monitoring of user's behaviour, and this information may be used for a variety of commercial purposes, including targeted advertising, profiling, and the sale of aggregated data. This is why the subject is so important, especially for web applications.
 +
 +
===Are the Top 10 Privacy Risks applicable for mobile apps as well?===
 +
Privacy risks for mobile apps are very similar. The rating might be slightly different and there might be some additional risks related to the loss of devices and the use of location data, but in general the Top 10 Privacy Risks are applicable for mobile apps as well. 
 +
 +
===What is the difference between this project and the OWASP Top 10?===
 +
There are two main differences. First, the OWASP Top 10 describes technical risks, that are not primarily affecting privacy. Second, the OWASP Top 10 do not address software such as cookies or trackers, or organisational issues like privacy notices, profiling, or the sharing of data with third parties.
 +
 +
===Why should companies and other organisations be concerned about privacy risks?===
 +
Privacy risks may have serious consequences for an organisation, such as:
 +
* perceived harm to privacy;
 +
* a failure to meet public expectations on both the use and protection of personal information;
 +
* retrospective imposition of regulatory conditions;
 +
* low adoption rates or poor participation in the scheme from both the public and partner organisations;
 +
* the costs of redesigning the system or retro-fitting solutions;
 +
* failure of a project or completed system;
 +
* withdrawal of support from key supporting organisations due to perceived privacy harms; and/ or
 +
* failure to comply with the law, leading to enforcement action from the regulator or compensation claims from individuals.
 +
(Source: http://ico.org.uk/pia_handbook_html_v2/html/1-Chap2-2.html)
 +
 +
= Translation =
 +
Currently project documentation is available in English and German. If you are interested in helping to translate to another language, please contact the project leaders. 
 +
==German==
 +
===Top 10 Datenschutzrisiken===
 +
 +
<table style="background-color:#FFFFFF;border-collapse:collapse;border:1px solid #000000;color:#000000;width:100%" cellspacing="3" cellpadding="3" border="1">
 +
<tr>
 +
<td bgcolor="#D8D8D8"><b>Nr.</b></td>
 +
<td bgcolor="#D8D8D8"><b>Titel</b></td>
 +
<td bgcolor="#D8D8D8"><b>Häufigkeit</b></td>
 +
<td bgcolor="#D8D8D8"><b>Schaden&nbsp;&nbsp;&nbsp;&nbsp;</b></td>
 +
<td bgcolor="#D8D8D8"><b>Beschreibung</b></td>
 +
 +
</tr>
 +
<tr>
 +
<td>P1</td>
 +
<td>Schwachstellen in Webanwendungen</td>
 +
<td bgcolor="orange">Hoch</td>
 +
<td bgcolor="red">Sehr hoch</td>
 +
<td>Schwachstellen sind ein zentrales Problem in jedem System, mit dem sensible Nutzerdaten erhoben, verarbeitet und genutzt werden. Bestehen Fehler im Design oder in der Implementierung der Applikation, werden Probleme nicht entdeckt oder Sicherheitspatches nicht unverzüglich eingespielt, führt dies mit hoher Wahrscheinlichkeit zu einer Verletzung des Persönlichkeitsrechts. Dieses Risiko wird bereits in anderen Projekten behandelt, wie der OWASP Top 10 Liste der häufigsten Sicherheitsrisiken für Webanwendungen.
 +
</td>
 +
</tr>
 +
<tr>
 +
<td>P2</td>
 +
<td>Datenabfluss beim Betreiber</td>
 +
<td bgcolor="orange">Hoch</td>
 +
<td bgcolor="red">Sehr hoch</td>
 +
<td>Wird die unerwünschte Preisgabe personenbezogener oder personenbeziehbarer Daten an nicht autorisierte Personen nicht wirksam verhindert, ist dies ein Verlust der Vertraulichkeit. Ursachen sind entweder ein vorsätzlich durchgeführter Datenabzug oder unbeabsichtigte Fehler wie beispielsweise unzureichendes Zugriffsmanagement, unsichere Datenablage, Datendopplung oder fehlendes Problembewusstsein (Awareness).</td>
 +
</tr>
 +
<tr>
 +
<td>P3</td>
 +
<td>Unzureichende Reaktion bei einer Datenpanne</td>
 +
<td bgcolor="orange">Hoch</td>
 +
<td bgcolor="red">Sehr hoch</td>
 +
<td>Betroffene werden nicht &uuml;ber m&ouml;gliche Pannen oder Datenlecks benachrichtigt, die durch Angriffe oder unbeabsichtigte Ereignisse entstehen. Angemessene Abhilfemaßnahmen zum Schließen der Lücken und Beseitigung der Ursache fehlen.</td>
 +
</tr>
 +
<tr>
 +
<td>P4</td>
 +
<td>Unzureichende Löschung personenbezogener Daten</td>
 +
<td bgcolor="red">Sehr hoch</td>
 +
<td bgcolor="orange">Hoch</td>
 +
<td>Personenbezogene Daten werden nicht termingerecht oder nicht effektiv nach Zweckablauf bzw. aufgrund einer L&ouml;schanfrage gelöscht.</td>
 +
</tr>
 +
<tr>
 +
<td>P5</td>
 +
<td>Intransparente Nutzungsbedingungen</td>
 +
<td bgcolor="red">Sehr hoch</td>
 +
<td bgcolor="orange">High</td>
 +
<td>Informationen zur Datenverarbeitung wie Erhebung, Speicherung und Nutzung personenbezogener Daten sind unzureichend. Diese Informationen sind nicht leicht zugänglich oder für juristische Laien nicht verständlich aufbereitet.
 +
</td>
 +
</tr>
 +
<tr>
 +
<td>P6</td>
 +
<td>Sammeln von Daten, die über den eigentlichen Zweck hinaus gehen</td>
 +
<td bgcolor="red">Sehr hoch</td>
 +
<td bgcolor="orange">Hoch</td>
 +
<td>Es werden Beschreibungsdaten, demographische Daten oder sonstige personenbezogene Daten gesammelt, die nicht für den vereinbarten Zweck der Anwendung benötigt werden. Ebenso werden Daten gesammelt, für deren Erhebung der Nutzer keine Einverständniserklärung abgegeben hat.
 +
</td>
 +
</tr>
 +
<tr>
 +
<td>P7</td>
 +
<td>Weitergabe von Daten an Dritte</td>
 +
<td bgcolor="orange">Hoch</td>
 +
<td bgcolor="orange">Hoch</td>
 +
<td>Personenbezogene Daten werden ohne Einverständnis des Nutzers an Dritte weiter gegeben bzw. diesen zur Verfügung gestellt. Die Weitergabe von Daten und Erkenntnissen erfolgt entweder direkt oder auf Anfrage, gegen Zahlung oder auch durch unsachgemäßen Einsatz von Diensten Dritter wie beispielsweise Widgets für Webseiten (z.B. Landkarten, Buttons von sozialen Netzwerken), Analysetools oder Web Bugs (z.B. Beacons).
 +
</td>
 +
</tr>
 +
<tr>
 +
<td>P8</td>
 +
<td>Veraltete personenbezogene Daten</td>
 +
<td bgcolor="orange">Hoch</td>
 +
<td bgcolor="red">Sehr hoch</td>
 +
<td>Es werden veraltete, inkorrekte oder gefälschte personenbezogene Daten genutzt. Datenaktualisierungen oder -korrekturen finden nicht in ausreichendem Maße statt.
 +
</td>
 +
</tr>
 +
<tr>
 +
<td>P9</td>
 +
<td>Fehlendes oder unzureichendes Session-Ende</td>
 +
<td bgcolor="yellow">Mittel</td>
 +
<td bgcolor="red">Sehr hoch</td>
 +
<td>Unzureichendes Beenden von Sessions. Dies kann dazu führen, dass zusätzliche Nutzerdaten ohne Einverständnis oder Wissen des Nutzers gesammelt werden.
 +
</td>
 +
</tr>
 +
<tr>
 +
<td>P10</td>
 +
<td>Unsichere Datenübertragung</td>
 +
<td bgcolor="yellow">Mittel</td>
 +
<td bgcolor="red">Sehr hoch</td>
 +
<td>Die Datenübermittlung erfolgt nicht auf verschlüsselten und sicheren Kanälen, so dass ein unautorisierter Zugriff nicht verhindert wird. Mechanismen zum Verringern der Angriffsfläche, werden nicht umgesetzt. Hierzu gehört es zu verhindern, dass durch das Verhalten der Webanwendung Rückschlüsse auf Nutzerdaten möglich sind.
 +
</td>
 +
</tr>
 +
</table>
 +
 +
===Presentation===
 +
[https://www.it-sa.de/de/events/2/2015-10-06/forum-rot-management/11939/#12089 Video and presentation] from it-sa Security Expo and Congress 2015
 +
 +
 +
===Flyer===
 +
[[File:Top_10_Privacy_Risks_German.png | 200px]]
 +
 +
==Japanese==
 +
[https://speakerdeck.com/owaspjapan/introducing-owasp-top10-privacy-risks-number-owasp-night-21th Link to slidedeck]
 +
 +
= Acknowledgements =
 +
==Volunteers==
 +
The Top 10 Privacy Risk list is developed by a team of volunteers. The primary contributors to date have been:
 +
 +
* Stefan Burgmair
 +
* R. Jason Cronk
 +
* Edward Delaporte
 +
* Tim Gough
 +
* Prof. Hans-Joachim Hof
 +
* Lukasz Olejnik
 +
* Florian Stahl
 +
 +
==Partners==
 +
* [http://www.cs.hm.edu/en/home/index.en.html University of Applied Sciences Munich]
 +
* [https://secure.edps.europa.eu/EDPSWEB/edps/EDPS/IPEN European Data Protection Supervisory's Internet Privacy Engineering Network (IPEN)]
 +
* [http://privacyassociation.org/ International Association of Privacy Professionals (IAPP)]
 +
 +
==Sponsors==
 +
* [http://www.msg-systems.com/ msg systems]
 +
 +
Feel free to contact us in case you are also interested to support the OWASP Top 10 Privacy Risks project.
  
 
=Project About=
 
=Project About=
Line 316: Line 521:
 
__NOTOC__ <headertabs />  
 
__NOTOC__ <headertabs />  
  
−
[[Category:OWASP Project]]  [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]]  [[Category:OWASP_Document]]
+
[[Category:OWASP Project]]   
 +
[[Category:OWASP_Builders]]  
 +
[[Category:OWASP_Defenders]]   
 +
[[Category:OWASP_Document]]

Latest revision as of 12:28, 19 December 2019

Lab big.jpg

The project in a nutshell

The OWASP Top 10 Privacy Risks Project provides a top 10 list for privacy risks in web applications and related countermeasures. It covers technological and organizational aspects that focus on real-life risks, not just legal issues. The Project provides tips on how to implement privacy by design in web applications with the aim of helping developers and web application providers to better understand and improve privacy. The list uses the OECD Privacy Guidelines as a framework and can also be used to assess privacy risks associated with specific web applications.

Top 10 Privacy Risks

P1    Web Application Vulnerabilities
P2    Operator-sided Data Leakage
P3    Insufficient Data Breach Response
P4    Insufficient Deletion of personal data
P5    Non-transparent Policies, Terms and Conditions
P6    Collection of data not required for the primary purpose
P7    Sharing of data with third party
P8    Outdated personal data
P9    Missing or Insufficient Session Expiration
P10  Insecure Data Transfer

Further information is provided in the Top 10 Privacy Risks tab.

Contact us

Florian Stahl @
Stefan Burgmair @

Quick Download

Licensing

OWASP Top 10 Privacy Risks Project is free to use. It is licensed under the Creative Commons CC-BY-SA v3.0 License.

Download Infographic version

Top 10 Risks.png

News

  • [Ongoing] Update of the OWASP Top 10 Privacy Risks
  • [8 April 2016] Countermeasures v1.0 published
  • [1 July 2015] German Translation available
  • [21 Sep 2014] Top 10 Privacy Risks v1.0 published
  • [20 Feb 2014] Project Start

External Links

OECD Privacy Guidelines Internet Privacy Engineering Network - IPEN
Video from IPEN workshop at Berlin state parliament
Video from panel discussion at CPDP 2015 in Brussels
Video from presentation at AppSec EU 2015
Check your website with PRIVACYSCORE

Classifications

Midlevel projects.png Owasp-builders-small.png
Owasp-defenders-small.png
Cc-button-y-sa-small.png
Project Type Files DOC.jpg

Top 10 Privacy Risks 2014

Version 1.0 of the OWASP Top 10 Privacy Risks list. Further information and related countermeasures are provided in this PDF document.

No. Title Frequency Impact     Description
P1 Web Application Vulnerabilities High Very high Vulnerability is a key problem in any system that guards or operates on sensitive user data. Failure to suitably design and implement an application, detect a problem or promptly apply a fix (patch) is likely to result in a privacy breach. This risk also encompasses the OWASP Top 10 List of web application vulnerabilities and the risks resulting from them.
P2 Operator-sided Data Leakage High Very high Failure to prevent the leakage of any information containing or related to user data, or the data itself, to any unauthorized party resulting in loss of data confidentiality. Introduced either due to intentional malicious breach or unintentional mistake e.g. caused by insufficient access management controls, insecure storage, duplication of data or a lack of awareness.
P3 Insufficient Data Breach Response High Very high Not informing the affected persons (data subjects) about a possible breach or data leak, resulting either from intentional or unintentional events; failure to remedy the situation by fixing the cause; not attempting to limit the leaks.
P4 Insufficient Deletion of Personal Data Very high High Failure to effectively and/or timely delete personal data after termination of the specified purpose or upon request.
P5 Non-transparent Policies, Terms and Conditions Very high High Not providing sufficient information to describing how data is processed, such as its collection, storage, and processing. Failure to make this information easily-accessible and understandable for non-lawyers.
P6 Collection of data not required for the primary purpose Very high High Collecting descriptive, demographic or any other user-related data that are not needed for the purposes of the system. Applies also to data for which the user did not provide consent.
P7 Sharing of Data with Third Party High High Providing user data to any third-party, without obtaining the user’s consent. Sharing results either due to transfer or exchanging for a monetary compensation or otherwise due to inappropriate use of third-party resources included in the web site like widgets (e.g. maps, social networks buttons), analytics or web bugs (e.g. beacons).
P8 Outdated personal data High Very high The use of outdated, incorrect or bogus user data. Failure to update or correct the data.
P9 Missing or insufficient Session Expiration Medium Very high Failure to effectively enforce session termination. May result in collection of additional user-data without the user’s consent or awareness.
P10 Insecure Data Transfer Medium Very high Failure to provide data transfers over encrypted and secured channels, excluding the possibility of data leakage. Failure of enforcing mechanisms limiting the leak surface, e.g. allowing to infer any user data out of the mechanics of Web application operation.

Note: The values between 0 to 3 used for frequency and impact rating were replaced by a textual description: 0-1: Low, 1-1.5: Medium, 1.5-2: High, > 2: Very high

Participate

Some ways you can help:

  • Discuss with us in the mailing list or Google docs
  • Tell your colleagues and friends about the project
  • Provide feedback (feel free to contact us)
  • Apply the results in practice to improve web application privacy

Sign up to our mailing list to stay informed.

Discussions and Documentation

To avoid overwriting issues we use Google Docs for our discussions.

Update 2019-2020

Impact rating (open discussion): https://docs.google.com/document/d/1VuusvZnhHpWvmPFeAovM68iB_Do3XFZCH2EsITGuAKg/edit
Privacy Risk Candidate List: https://docs.google.com/document/d/1eEU7TsoaPG56-zhJi4bi1SD53Jto84GQ8dDGTajL8TY/edit
Method Update: https://docs.google.com/document/d/1AlAg2cybvo5VX-frzF5uHeAcib3X2rTAA2p97XH8fHw/edit

Closed discussions and documents

Countermeasures document: https://docs.google.com/document/d/1GaoJDPtyXMv09wIw9xXTVPYTR_6fQROlptszPhxVc1s/edit?usp=sharing
Method: https://docs.google.com/document/d/1nHM9LH2rP6ac3DvJ7lehDNb9qVP5YADOQGNEuiy5okg/edit
Privacy Risk list 2014: https://docs.google.com/document/d/1ufAuGtW42gUHtJF-9_VOzNZEegZJnMyqDcyfzmsjJeQ/edit
Draft list: https://docs.google.com/document/d/1WMljvy09nulPnzv5XkFc2uxn1bSR-ftKqx5VoayTzW8/edit
Impact rating: https://docs.google.com/a/owasp.org/document/d/1Gjd5XVJyGWHryUA2WyPSRQ0gQuaD5zWUCHU76_FHMKU/edit
Calculation of the complete Privacy Risks list v1.0: https://docs.google.com/spreadsheets/d/1q7Xh4gclSieXNpVbdvyFwsZMENo2r3BoN2S3ww_W5-M/edit
Brainstorming for countermeasures: https://docs.google.com/a/owasp.org/document/d/1g4Q_XDVGEAbVR_7DLNIbDN2men57BQ0pNn8CyRc2od8/edit

Survey Results

A survey was performed to determine the frequency of occurrence of privacy violations in web applications.

63 people participated in total. The survey was online for 3 weeks from 4 to 25 August 2014.


Here is a summary of the results or you can download the full report.


Part 1:

Q1 Do or did you work as a:

Software Developer 26.98%

Software Designer 12.70%

Legal Practitioner 4.76%

Software Project Manager 11.11%

Data Privacy Expert 33.33%

Security Expert 66.67%

Public Servant 12.70%

Other 11.11%


Q2 In total, how many years of professional experience do you have related to privacy?

Average: 6.2 years


Q3 In total, how many years of professional experience do you have related to web applications?

Average: 8.1 years


Part 2:

The following ratings are between 1 and 4.

The possible choices for answers where:

[1] Up to one out of four web applications. (0-25%)

[2] Up to ev ery second web application. (26-50%)

[3] Up to three out of four web applications. (51-75%)

[4] More than three out of four web applications. (76-100%)

[excluded] N/A


01. Collection of data not required for main purpose

Average Rating: 3.1


02. Collection of Incorrect Data

Average Rating: 2.0


03. Collection without consent

Average Rating: 3.0


04. Problems with getting Consent

Average Rating: 2.6


05. Outdated Personal Data

Average Rating: 2.6


06. Inability of users to modify stored data

Average Rating: 2.3


07. Insufficient deletion of personal data

Average Rating: 3.3


08. Unrelated use

Average Rating: 2.7


09. Data Aggregation and Profiling

Average Rating: 2.4


10. Sharing of data with third party

Average Rating: 2.8


11. Operator-sided Data Leakage

Average Rating: 2.7


12. Insecure data transfer

Average Rating: 2.3


13. Web Application Vulnerabilities

Average Rating: 2.9


14. Insufficient Data Breach Response

Average Rating: 2.6


15. Form field design issues

Average Rating: 2.2


16. Missing or Insufficient Session Expiration

Average Rating: 2.4


17. Misleading Content

Average Rating: 2.3


18. Non-transparent Policies, Terms and Conditions

Average Rating: 3.2


19. Inappropriate Policies, Terms and Conditions

Average Rating: 2.7


20. Transfer or processing through third party

Average Rating: 2.6

Frequently Asked Questions

Why is this project only about web applications and not about any kind of software?

Web applications can easily collect data from users without their permission or without adequately informing them how their data is used. Cookies, and other trackers, enable the monitoring of user's behaviour, and this information may be used for a variety of commercial purposes, including targeted advertising, profiling, and the sale of aggregated data. This is why the subject is so important, especially for web applications.

Are the Top 10 Privacy Risks applicable for mobile apps as well?

Privacy risks for mobile apps are very similar. The rating might be slightly different and there might be some additional risks related to the loss of devices and the use of location data, but in general the Top 10 Privacy Risks are applicable for mobile apps as well.

What is the difference between this project and the OWASP Top 10?

There are two main differences. First, the OWASP Top 10 describes technical risks, that are not primarily affecting privacy. Second, the OWASP Top 10 do not address software such as cookies or trackers, or organisational issues like privacy notices, profiling, or the sharing of data with third parties.

Why should companies and other organisations be concerned about privacy risks?

Privacy risks may have serious consequences for an organisation, such as:

  • perceived harm to privacy;
  • a failure to meet public expectations on both the use and protection of personal information;
  • retrospective imposition of regulatory conditions;
  • low adoption rates or poor participation in the scheme from both the public and partner organisations;
  • the costs of redesigning the system or retro-fitting solutions;
  • failure of a project or completed system;
  • withdrawal of support from key supporting organisations due to perceived privacy harms; and/ or
  • failure to comply with the law, leading to enforcement action from the regulator or compensation claims from individuals.

(Source: http://ico.org.uk/pia_handbook_html_v2/html/1-Chap2-2.html)

Currently project documentation is available in English and German. If you are interested in helping to translate to another language, please contact the project leaders.

German

Top 10 Datenschutzrisiken

Nr. Titel Häufigkeit Schaden     Beschreibung
P1 Schwachstellen in Webanwendungen Hoch Sehr hoch Schwachstellen sind ein zentrales Problem in jedem System, mit dem sensible Nutzerdaten erhoben, verarbeitet und genutzt werden. Bestehen Fehler im Design oder in der Implementierung der Applikation, werden Probleme nicht entdeckt oder Sicherheitspatches nicht unverzüglich eingespielt, führt dies mit hoher Wahrscheinlichkeit zu einer Verletzung des Persönlichkeitsrechts. Dieses Risiko wird bereits in anderen Projekten behandelt, wie der OWASP Top 10 Liste der häufigsten Sicherheitsrisiken für Webanwendungen.
P2 Datenabfluss beim Betreiber Hoch Sehr hoch Wird die unerwünschte Preisgabe personenbezogener oder personenbeziehbarer Daten an nicht autorisierte Personen nicht wirksam verhindert, ist dies ein Verlust der Vertraulichkeit. Ursachen sind entweder ein vorsätzlich durchgeführter Datenabzug oder unbeabsichtigte Fehler wie beispielsweise unzureichendes Zugriffsmanagement, unsichere Datenablage, Datendopplung oder fehlendes Problembewusstsein (Awareness).
P3 Unzureichende Reaktion bei einer Datenpanne Hoch Sehr hoch Betroffene werden nicht über mögliche Pannen oder Datenlecks benachrichtigt, die durch Angriffe oder unbeabsichtigte Ereignisse entstehen. Angemessene Abhilfemaßnahmen zum Schließen der Lücken und Beseitigung der Ursache fehlen.
P4 Unzureichende Löschung personenbezogener Daten Sehr hoch Hoch Personenbezogene Daten werden nicht termingerecht oder nicht effektiv nach Zweckablauf bzw. aufgrund einer Löschanfrage gelöscht.
P5 Intransparente Nutzungsbedingungen Sehr hoch High Informationen zur Datenverarbeitung wie Erhebung, Speicherung und Nutzung personenbezogener Daten sind unzureichend. Diese Informationen sind nicht leicht zugänglich oder für juristische Laien nicht verständlich aufbereitet.
P6 Sammeln von Daten, die über den eigentlichen Zweck hinaus gehen Sehr hoch Hoch Es werden Beschreibungsdaten, demographische Daten oder sonstige personenbezogene Daten gesammelt, die nicht für den vereinbarten Zweck der Anwendung benötigt werden. Ebenso werden Daten gesammelt, für deren Erhebung der Nutzer keine Einverständniserklärung abgegeben hat.
P7 Weitergabe von Daten an Dritte Hoch Hoch Personenbezogene Daten werden ohne Einverständnis des Nutzers an Dritte weiter gegeben bzw. diesen zur Verfügung gestellt. Die Weitergabe von Daten und Erkenntnissen erfolgt entweder direkt oder auf Anfrage, gegen Zahlung oder auch durch unsachgemäßen Einsatz von Diensten Dritter wie beispielsweise Widgets für Webseiten (z.B. Landkarten, Buttons von sozialen Netzwerken), Analysetools oder Web Bugs (z.B. Beacons).
P8 Veraltete personenbezogene Daten Hoch Sehr hoch Es werden veraltete, inkorrekte oder gefälschte personenbezogene Daten genutzt. Datenaktualisierungen oder -korrekturen finden nicht in ausreichendem Maße statt.
P9 Fehlendes oder unzureichendes Session-Ende Mittel Sehr hoch Unzureichendes Beenden von Sessions. Dies kann dazu führen, dass zusätzliche Nutzerdaten ohne Einverständnis oder Wissen des Nutzers gesammelt werden.
P10 Unsichere Datenübertragung Mittel Sehr hoch Die Datenübermittlung erfolgt nicht auf verschlüsselten und sicheren Kanälen, so dass ein unautorisierter Zugriff nicht verhindert wird. Mechanismen zum Verringern der Angriffsfläche, werden nicht umgesetzt. Hierzu gehört es zu verhindern, dass durch das Verhalten der Webanwendung Rückschlüsse auf Nutzerdaten möglich sind.

Presentation

Video and presentation from it-sa Security Expo and Congress 2015


Flyer

Top 10 Privacy Risks German.png

Japanese

Link to slidedeck

Volunteers

The Top 10 Privacy Risk list is developed by a team of volunteers. The primary contributors to date have been:

  • Stefan Burgmair
  • R. Jason Cronk
  • Edward Delaporte
  • Tim Gough
  • Prof. Hans-Joachim Hof
  • Lukasz Olejnik
  • Florian Stahl

Partners

Sponsors

Feel free to contact us in case you are also interested to support the OWASP Top 10 Privacy Risks project.

PROJECT INFO
What does this OWASP project offer you? 		RELEASE(S) INFO
What releases are available for this project?
what is this project?
Name: OWASP Top 10 Privacy Risks Project (home page)
Purpose: The OWASP Top 10 Privacy Risks Project provides a top 10 list for privacy risks in web applications and related countermeasures. It covers technological and organizational aspects that focus on real-life risks, not just legal issues. The Project provides tips on how to implement privacy by design in web applications with the aim of helping developers and web application providers to better understand and improve privacy. The list uses the OECD Privacy Guidelines as a framework and can also be used to assess privacy risks associated with specific web applications.
License: Creative Commons Attribution Share Alike 3.0
who is working on this project?
Project Leader(s):
  • Florian Stahl @
  • Stefan Burgmair @
how can you learn more?
Project Pamphlet: View
Project Presentation: View
Mailing list: Mailing List Archives
Project Roadmap: View
Key Contacts
  • Contact Florian Stahl @ to contribute to this project
  • Contact Florian Stahl @ to review or sponsor this project
current release
Top 10 Privacy Risks v1 - September 2014 (risk list / final, v1.0) & June 2015 (countermeasures / alpha) - (no download available)
Release description: N/A
Rating: Projects/OWASP Top 10 Privacy Risks Project/GPC/Assessment/Top 10 Privacy Risks v1
last reviewed release
Not Yet Reviewed


other releases

Retrieved from "https://wiki.owasp.org/index.php?title=OWASP_Top_10_Privacy_Risks_Project&oldid=256454"