Privacy Violation - Revision history

Wichers at 22:17, 9 February 2013

2013-02-09T22:17:07Z

KirstenS at 13:39, 27 February 2009

2009-02-27T13:39:00Z

KirstenS: /* References */

2009-02-27T13:38:35Z

‎References

KirstenS: /* References */

2009-02-27T13:37:50Z

‎References

KirstenS: /* Description */

2009-02-27T13:36:43Z

‎Description

KirstenS at 13:46, 19 February 2009

2009-02-19T13:46:52Z

KirstenS at 15:34, 5 November 2008

2008-11-05T15:34:46Z

KirstenS at 12:55, 30 September 2008

2008-09-30T12:55:10Z

Weilin Zhong at 16:47, 19 July 2006

2006-07-19T16:47:29Z

Weilin Zhong at 14:51, 19 July 2006

2006-07-19T14:51:31Z

@@ Line 1: / Line 1: @@
 {{Template:Vulnerability}}
 [[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]
 ==Description==
@@ Line 35: / Line 31: @@
 Despite these regulations, privacy violations continue to occur with alarming frequency.
 ==Examples==
@@ Line 51: / Line 43: @@
 The code in the example above logs a plaintext password to the filesystem. Although many developers trust the filesystem as a safe storage location for data, it should not be trusted implicitly, particularly when privacy is a concern.
 ==References==
-* [1] J. Oates. AOL man pleads guilty to selling 92m email addies. The Register, 2005. http://www.theregister.co.uk/2005/02/07/aol_email_theft/
+* [1] J. Oates. AOL man pleads guilty to selling 92m email addresses. The Register, 2005. http://www.theregister.co.uk/2005/02/07/aol_email_theft/
 * [2] Safe Harbor Privacy Framework. U.S. Department of Commerce. http://www.export.gov/safeharbor/.
 * [3] Financial Privacy: The Gramm-Leach Bliley Act (GLBA). Federal Trade Commission. http://www.ftc.gov/privacy/privacyinitiatives/glbact.html.

← Older revision		Revision as of 13:39, 27 February 2009
Line 2:		Line 2:
	{{Template:Fortify}}		{{Template:Fortify}}

		+	Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''

−	[[~~ASDR~~ Table of Contents]]	+	[[ASDR_TOC_Vulnerabilities\|Vulnerabilities Table of Contents]]
−
−	~~Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''~~

@@ Line 117: / Line 117: @@
 [[Category:Sensitive Data Protection Vulnerability]]
 [[Category:Code Snippet]]
 [[Category:Vulnerability]]

@@ Line 81: / Line 81: @@
 * [1] J. Oates. AOL man pleads guilty to selling 92m email addies. The Register, 2005. http://www.theregister.co.uk/2005/02/07/aol_email_theft/
 * [2] Safe Harbor Privacy Framework. U.S. Department of Commerce. http://www.export.gov/safeharbor/.
-* [3] Financial Privacy: The Gramm-Leach Bliley Act (GLBA). Federal Trade Commission. http://www.ftc.gov/privacy/glbact/index.html.
+* [3] Financial Privacy: The Gramm-Leach Bliley Act (GLBA). Federal Trade Commission. http://www.ftc.gov/privacy/privacyinitiatives/glbact.html.
 * [4] Health Insurance Portability and Accountability Act (HIPAA). U.S. Department of Human Services. http://www.hhs.gov/ocr/hipaa/.
 * [5] California SB-1386. Government of the State of California, 2002. http://info.sen.ca.gov/pub/01-02/bill/sen/sb_1351-1400/sb_1386_bill_20020926_chaptered.html.

@@ Line 9: / Line 9: @@
 ==Description==
-Mishandling private information, such as customer passwords or social security numbers, can compromise user privacy and is often illegal.
+Mishandling private information, such as customer passwords or social security numbers, can compromise user privacy, and is often illegal.
 Privacy violations occur when:
@@ Line 26: / Line 26: @@
 Security and privacy concerns often seem to compete with each other. From a security perspective, you should record all important operations so that any anomalous activity can later be identified. However, when private data is involved, this practice can in fact create risk.
-Although there are many ways in which private data can be handled unsafely, a common risk stems from misplaced trust. Programmers often trust the operating environment in which a program runs, and therefore believe that it is acceptable store private information on the file system, in the registry, or in other locally-controlled resources. However, even if access to certain resources is restricted, this does not guarantee that the individuals who do have access can be trusted. For example, in 2004, an unscrupulous employee at AOL sold approximately 92 million private customer e-mail addresses to a spammer marketing an offshore gambling web site [1].
+Although there are many ways in which private data can be handled unsafely, a common risk stems from misplaced trust. Programmers often trust the operating environment in which a program runs, and therefore believe that it is acceptable to store private information on the file system, in the registry, or in other locally-controlled resources. However, even if access to certain resources is restricted, this does not guarantee that the individuals who do have access can be trusted. For example, in 2004, an unscrupulous employee at AOL sold approximately 92 million private customer e-mail addresses to a spammer marketing an offshore gambling web site [1].
 In response to such high-profile exploits, the collection and management of private data is becoming increasingly regulated. Depending on its location, the type of business it conducts, and the nature of any private data it handles, an organization may be required to comply with one or more of the following federal and state regulations:
@@ Line 36: / Line 36: @@
 Despite these regulations, privacy violations continue to occur with alarming frequency.
 ==Risk Factors==

@@ Line 2: / Line 2: @@
 {{Template:Fortify}}
 [[ASDR Table of Contents]]
 Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
 ==Description==
 Mishandling private information, such as customer passwords or social security numbers, can compromise user privacy and is often illegal.

@@ Line 2: / Line 2: @@
 {{Template:Fortify}}
-[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
+__TOC__
 Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
-[[ASDR Table of Contents]]
+[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
@@ Line 125: / Line 125: @@
 [[Category:Privacy]]
 [[Category:Policy]]

← Older revision		Revision as of 16:47, 19 July 2006
Line 1:		Line 1:
		+	{{Template:Vulnerability}}
	{{Template:Fortify}}		{{Template:Fortify}}
−	~~{{Template:Vulnerability}}~~

	==Abstract==		==Abstract==

← Older revision		Revision as of 14:51, 19 July 2006
Line 1:		Line 1:
	{{Template:Fortify}}		{{Template:Fortify}}
−
	{{Template:Vulnerability}}		{{Template:Vulnerability}}