Security and Compliance

DOI Bookmark:

http://doi.ieeecomputersociety.org/10.1109/MSP.2004.22

May-June 2004 (vol. 2 no. 3) pp. 96

	This Article
	PURCHASE ARTICLE: $19 PDF HTML IEEE Xplore Subscribers
	Share
	Email this Article to a friend
	Bibliographic References
	ASCII Text BibTex RefWorks Procite/RefMan/Endnote
	Add to:
	Digg Furl Spurl Blink Simpy Google Del.icio.us Y!MyWeb
	Search
	Similar Articles Articles by Bruce Schneier

	ASCII Text	x
	Bruce Schneier, "Security and Compliance," IEEE Security and Privacy, vol. 2, no. 3, pp. 96, May-June, 2004.

	BibTex	x
	@article{ 10.1109/MSP.2004.22, author = {Bruce Schneier}, title = {Security and Compliance}, journal ={IEEE Security and Privacy}, volume = {2}, number = {3}, issn = {1540-7993}, year = {2004}, pages = {96}, doi = {http://doi.ieeecomputersociety.org/10.1109/MSP.2004.22}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, }

	RefWorks Procite/RefMan/Endnote	x
	TY - MGZN JO - IEEE Security and Privacy TI - Security and Compliance IS - 3 SN - 1540-7993 SP EP EPD - 96 A1 - Bruce Schneier, PY - 2004 KW - data privacy KW - software liability KW - security KW - deata security protection VL - 2 JA - IEEE Security and Privacy ER -

Bruce Schneier, Counterpane Internet Security

Just as I advocate software liability as a way to bring the externalities of insecure software into the software manufacturer?s decision-making process, I see data privacy laws as a way to force organizations to take personal data security protection more seriously.

Index Terms:

data privacy, software liability, security, deata security protection

Citation:

Bruce Schneier, "Security and Compliance," IEEE Security and Privacy, vol. 2, no. 3, pp. 96, May 2004, doi:10.1109/MSP.2004.22

Peer Review Notice | Give Us Feedback

Usage of this product signifies your acceptance of the Terms of Use.