Operations

6/21/2018
02:40 PM
100%
0%

7 Places Where Privacy and Security Collide

Privacy and security can experience tension at a number of points in the enterprise. Here are seven - plus some possibilities for easing the strain.
Previous
1 of 8
Next

(Image: Joyseulay)

(Image: Joyseulay)

In a recent interview with Dark Reading, Cisco chief privacy officer Michelle Dennedy said that privacy was all about the contents of the metaphorical data pipe, while security concerned itself with the architecture of the pipe. For IT security professionals, issues arise when protecting the contents of the pipe, and the pipe itself, create tensions in how security operates.

There are a number of points at which these tensions arise in the "privacy versus security" dance. One of the most visible twirls around it is the topic of encryption, which can be used to both protect the privacy of individuals and shield the true nature of malware.

But that's not the only place where the needs of privacy and security can collide. Here, we take a look at seven — and want to know about others you have encountered. At which points have you seen privacy and security considerations collide? Let us know in the comments, below.

Why Cybercriminals Attack: A DARK READING VIRTUAL EVENT Wednesday, June 27. Industry experts will offer a range of information and insight on who the bad guys are – and why they might be targeting your enterprise. Go here for more information on this free event.

 

Curtis Franklin Jr. is Senior Editor at Dark Reading. In this role he focuses on product and technology coverage for the publication. In addition he works on audio and video programming for Dark Reading and contributes to activities at Interop ITX, Black Hat, INsecurity, and ... View Full Bio

Previous
1 of 8
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Joe Stanganelli
0%
100%
Joe Stanganelli,
User Rank: Ninja
6/22/2018 | 6:10:49 PM
security vs. privacy, or security vs. security?
Encryption vs. visibility is not just a security vs. privacy issue; it's also a security vs. security issue as enterprise IT organizations find that they have to contend with the bad guys encrypting their own malicious traffic. At that point, how do you know what to attempt to decrypt, what to let through, what to guard against?

Cases in point: securitynow.com/author.asp?section_id=706&doc_id=743513&
What We Talk About When We Talk About Risk
Jack Jones, Chairman, FAIR Institute,  7/11/2018
Ticketmaster Breach Part of Massive Payment Card Hacking Campaign
Jai Vijayan, Freelance writer,  7/10/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Flash Poll
The State of IT and Cybersecurity
The State of IT and Cybersecurity
IT and security are often viewed as different disciplines - and different departments. Find out what our survey data revealed, read the report today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-14084
PUBLISHED: 2018-07-16
An issue was discovered in a smart contract implementation for MKCB, an Ethereum token. If the owner sets the value of sellPrice to a large number in setPrices() then the "amount * sellPrice" will cause an integer overflow in sell().
CVE-2018-14085
PUBLISHED: 2018-07-16
An issue was discovered in a smart contract implementation for UserWallet 0x0a7bca9FB7AfF26c6ED8029BB6f0F5D291587c42, an Ethereum token. First, suppose that the owner adds the evil contract address to his sweepers. The evil contract looks like this: contract Exploit { uint public start; function swe...
CVE-2018-14086
PUBLISHED: 2018-07-16
An issue was discovered in a smart contract implementation for SingaporeCoinOrigin (SCO), an Ethereum token. The contract has an integer overflow. If the owner sets the value of sellPrice to a large number in setPrices() then the "amount * sellPrice" will cause an integer overflow in sell(...
CVE-2018-14087
PUBLISHED: 2018-07-16
An issue was discovered in a smart contract implementation for EUC (EUC), an Ethereum token. The contract has an integer overflow. If the owner sets the value of buyPrice to a large number in setPrices() then the "msg.value * buyPrice" will cause an integer overflow in the fallback functio...
CVE-2018-14088
PUBLISHED: 2018-07-16
An issue was discovered in a smart contract implementation for STeX White List (STE(WL)), an Ethereum token. The contract has an integer overflow. If the owner sets the value of amount to a large number then the "amount * 1000000000000000" will cause an integer overflow in withdrawToFounde...