Application Security

6/27/2018
09:00 AM
50%
50%

IEEE Calls for Strong Encryption

Newly issued position statement by the organization declares backdoor and key-escrow schemes could have 'negative consequences.'

The IEEE this week issued a position statement in support of strong encryption and in opposition to government efforts to require backdoors.

"IEEE supports the use of unfettered strong encryption to protect confidentiality and integrity of data and communications. We oppose efforts by governments to restrict the use of strong encryption and/or to mandate exceptional access mechanisms such as 'backdoors' or 'key escrow schemes' in order to facilitate government access to encrypted data," the organization's statement reads.

Backdoors and key escrow apporaches would open the door for vulnerabilities and other negative impacts on encryption, according to the IEEE. Law enforcement has other options besides backdoors, including legal action, forensic analysis, and requiring suspects to hand over keys and passwords, it said.

Read the full statement here

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
6/29/2018 | 2:38:47 PM
IEEE supports the use of unfettered strong encryption to protect confidentiality and integrity of data and communications
Good to see the IEEE is taking a stand to support data protection. Regardless of which side of the fence you fall on, if you support the core CIA principles you realize that strong encryption is the answer. And you can't have strong data protections if you are storing the keys in many locations.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
6/29/2018 | 2:36:10 PM
Backdoors and key escrow apporaches
This defeats the purpose of encryption. If there is a need for this data by the government then due process should be followed to work with the provider of the data to decrypt. It is ill advised to have the government always have the keys to your house, no matter how good their intentions may be.
WebAuthn, FIDO2 Infuse Browsers, Platforms with Strong Authentication
John Fontana, Standards & Identity Analyst, Yubico,  9/19/2018
Turn the NIST Cybersecurity Framework into Reality: 5 Steps
Mukul Kumar & Anupam Sahai, CISO & VP of Cyber Practice and VP Product Management, Cavirin Systems,  9/20/2018
NSS Labs Files Antitrust Suit Against Symantec, CrowdStrike, ESET, AMTSO
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/19/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Flash Poll
The Risk Management Struggle
The Risk Management Struggle
The majority of organizations are struggling to implement a risk-based approach to security even though risk reduction has become the primary metric for measuring the effectiveness of enterprise security strategies. Read the report and get more details today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-17321
PUBLISHED: 2018-09-22
An issue was discovered in SeaCMS 6.64. XSS exists in admin_datarelate.php via the time or maxHit parameter in a dorandomset action.
CVE-2018-17322
PUBLISHED: 2018-09-22
Cross-site scripting (XSS) vulnerability in index.php/index/category/index in YUNUCMS 1.1.4 allows remote attackers to inject arbitrary web script or HTML via the area parameter.
CVE-2018-14889
PUBLISHED: 2018-09-21
CouchDB in Vectra Networks Cognito Brain and Sensor before 4.3 contains a local code execution vulnerability.
CVE-2018-14890
PUBLISHED: 2018-09-21
Vectra Networks Cognito Brain and Sensor before 4.2 contains a cross-site scripting (XSS) vulnerability in the Web Management Console.
CVE-2018-14891
PUBLISHED: 2018-09-21
Management Console in Vectra Networks Cognito Brain and Sensor before 4.3 contains a local privilege escalation vulnerability.