Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Operations

6/21/2018
02:40 PM

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.
2 of 8

Everything Versus Limits
When security researchers are seeking the facts around an incident, it's almost impossible for them to have access to too much information. But to protect privacy, it's important to collect as little information as possible. The tension between the two is the first in the dance.
Security professionals will argue that strong security can protect information in the system. Privacy advocates will point out that no security regime is foolproof, and the easiest information to protect is that which you never collect in the first place.
The key to relieving this tension is to carefully define the information required for security (and 'everything' is not a valid definition), and then keep it only as long as required for reasonable forensics. Then per the established policy, purge everything personally identifiable.
(Image: mantinov VIA SHUTTERSTOCK)

Everything Versus Limits

When security researchers are seeking the facts around an incident, it's almost impossible for them to have access to too much information. But to protect privacy, it's important to collect as little information as possible. The tension between the two is the first in the dance.

Security professionals will argue that strong security can protect information in the system. Privacy advocates will point out that no security regime is foolproof, and the easiest information to protect is that which you never collect in the first place.

The key to relieving this tension is to carefully define the information required for security (and "everything" is not a valid definition), and then keep it only as long as required for reasonable forensics. Then per the established policy, purge everything personally identifiable.

(Image: mantinov VIA SHUTTERSTOCK)

2 of 8
Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
Joe Stanganelli
50%
50%
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&
Navigating Security in the Cloud
Diya Jolly, Chief Product Officer, Okta,  12/4/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-16772
PUBLISHED: 2019-12-07
The serialize-to-js NPM package before version 3.0.1 is vulnerable to Cross-site Scripting (XSS). It does not properly mitigate against unsafe characters in serialized regular expressions. This vulnerability is not affected on Node.js environment since Node.js's implementation of RegExp.prototype.to...
CVE-2019-9464
PUBLISHED: 2019-12-06
In various functions of RecentLocationApps.java, DevicePolicyManagerService.java, and RecognitionService.java, there is an incorrect warning indicating an app accessed the user's location. This could dissolve the trust in the platform's permission system, with no additional execution privileges need...
CVE-2019-2220
PUBLISHED: 2019-12-06
In checkOperation of AppOpsService.java, there is a possible bypass of user interaction requirements due to mishandling application suspend. This could lead to local information disclosure no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVers...
CVE-2019-2221
PUBLISHED: 2019-12-06
In hasActivityInVisibleTask of WindowProcessController.java there?s a possible bypass of user interaction requirements due to incorrect handling of top activities in INITIALIZING state. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction ...
CVE-2019-2222
PUBLISHED: 2019-12-06
n ihevcd_parse_slice_data of ihevcd_parse_slice.c, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-8.0 Android...