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.

Risk

12/14/2009
07:37 PM
George V. Hulme
George V. Hulme
Commentary
50%
50%

U.S. And Russia Talk Internet Security

According to news reports, the American and Russian governments are engaged in talks designed to pave a way for a more secure Internet and a treaty to limit certain types of cyberweapons.

According to news reports, the American and Russian governments are engaged in talks designed to pave a way for a more secure Internet and a treaty to limit certain types of cyberweapons.For awhile now, the U.S. and Russia have been talking about crafting a treaty that would aim to improve Internet security and place some type of control over digital weapons. The talks haven't progressed far, and based on this NY Times story that ran this summer, the friction stems from a difference in philosophy. The Russians want to handle international cyber security with a treaty, just like those used for nuclear arms and biological weapons. While the U.S. wants cyber-security treated more as a law enforcement effort.

Now, according to a story that ran on the NYTimes.com over the weekend, the talks have, somewhat, progressed:

Many countries, including the United States, are developing weapons for use on computer networks that are ever more integral to the operations of everything from banks to electrical power systems to government offices. They include "logic bombs" that can be hidden in computers to halt them at crucial times or damage circuitry; "botnets" that can disable or spy on Web sites and networks; or microwave radiation devices that can burn out computer circuits miles away.

The Russians have focused on three related issues, according to American officials involved in the talks that are part of a broader thaw in American-Russian relations known as the "reset" that also include negotiations on a new nuclear disarmament treaty. In addition to continuing efforts to ban offensive cyberweapons, they have insisted on what they describe as an issue of sovereignty calling for a ban on "cyberterrorism."

My take: if we are ever going to solve cyber-crime and limit cyberattacks, we are going to need more international law enforcement cooperation. How that works out in a way that is acceptable to most nations, I'm not sure. I don't see the Chinese or the Russians agreeing to searches being conducted by forgien agents on systems within their borders. Nor do I see the U.S. allowing the same. But there's certainly plenty of room for more openess and cooperation among nations when it comes to cyberlaw.

As for the effectiveness of such a cyberwarfare treaty: my hopes are not high. Viruses, worms, keystroke loggers, logic bombs, and spyware can be written by most anyone. Botnet development skills are widespread, too. There's no way to control the development and eventual use of weapons that can be developed in anyone's bedroom on a notebook. And it's too easy for the origination of such attacks to be obfuscated to the point that it's impossible to reasonably prove who launched them.

And the countries answer to risks associated with microwave radiation, or E-bombs, is to harden the power grid from such attacks.

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/6/2020
Ripple20 Threatens Increasingly Connected Medical Devices
Kelly Sheridan, Staff Editor, Dark Reading,  6/30/2020
DDoS Attacks Jump 542% from Q4 2019 to Q1 2020
Dark Reading Staff 6/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15505
PUBLISHED: 2020-07-07
MobileIron Core and Connector before 10.3.0.4, 10.4.x before 10.4.0.4, 10.5.x before 10.5.1.1, 10.5.2.x before 10.5.2.1, and 10.6.x before 10.6.0.1, and Sentry before 9.7.3 and 9.8.x before 9.8.1, allow remote attackers to execute arbitrary code via unspecified vectors.
CVE-2020-15506
PUBLISHED: 2020-07-07
MobileIron Core and Connector before 10.3.0.4, 10.4.x before 10.4.0.4, 10.5.x before 10.5.1.1, 10.5.2.x before 10.5.2.1, and 10.6.x before 10.6.0.1 allow remote attackers to bypass authentication mechanisms via unspecified vectors.
CVE-2020-15507
PUBLISHED: 2020-07-07
MobileIron Core and Connector before 10.3.0.4, 10.4.x before 10.4.0.4, 10.5.x before 10.5.1.1, 10.5.2.x before 10.5.2.1, and 10.6.x before 10.6.0.1 allow remote attackers to read files on the system via unspecified vectors.
CVE-2020-15096
PUBLISHED: 2020-07-07
In Electron before versions 6.1.1, 7.2.4, 8.2.4, and 9.0.0-beta21, there is a context isolation bypass, meaning that code running in the main world context in the renderer can reach into the isolated Electron context and perform privileged actions. Apps using "contextIsolation" are affecte...
CVE-2020-4075
PUBLISHED: 2020-07-07
In Electron before versions 7.2.4, 8.2.4, and 9.0.0-beta21, arbitrary local file read is possible by defining unsafe window options on a child window opened via window.open. As a workaround, ensure you are calling `event.preventDefault()` on all new-window events where the `url` or `options` is not ...