Operations

6/17/2016
11:10 AM
50%
50%

NATO Officially Declares Cyberspace A Domain For War

Cyberattack on a NATO ally will now trigger a collective response.

The North Atlantic Trade Organization (NATO) has officially declared cyberspace a warfare domain and said cyberattack on any of its allies will be tackled collectively. This was announced at a meeting by NATO secretary general Jens Stoltenberg, reports Infosecurity.

The declaration makes it official that a cyberattack on a NATO ally would activate Article 5 and call for collective response, indicating how crucial cyberspace has become in the face of attacks on computer grids, networks and systems from foreign agents.

NATO countries will now work together and provide support to each other on cyber defense strategies apart from developing capabilities to protect NATO cyber networks, said Stoltenberg.

“Since it's very hard to imagine a military conflict today without a cyber dimension, this is important, related to almost all possible conflicts we can foresee in the future,” Stoltenberg added.

However, security experts have criticized this move with one saying that NATO is not equipped to collectively ward off a cyberattack on an ally since it has no assets to deploy in the cyber domain.

For more on this, click 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/20/2016 | 2:13:57 PM
Nato Criticism
I think that final criticism is accurate. For defense and retribution against cyber crime at the nation level you need a overarching organization, but to what end are the equipped to enforce such measures? Has NATO released a potential plan of action?
Want Your Daughter to Succeed in Cyber? Call Her John
John De Santis, CEO, HyTrust,  5/16/2018
New Mexico Man Sentenced on DDoS, Gun Charges
Dark Reading Staff 5/18/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
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-11354
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, the IEEE 1905.1a dissector could crash. This was addressed in epan/dissectors/packet-ieee1905.c by making a certain correction to string handling.
CVE-2018-11355
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, the RTCP dissector could crash. This was addressed in epan/dissectors/packet-rtcp.c by avoiding a buffer overflow for packet status chunks.
CVE-2018-11356
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the DNS dissector could crash. This was addressed in epan/dissectors/packet-dns.c by avoiding a NULL pointer dereference for an empty name in an SRV record.
CVE-2018-11357
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the LTP dissector and other dissectors could consume excessive memory. This was addressed in epan/tvbuff.c by rejecting negative lengths.
CVE-2018-11358
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the Q.931 dissector could crash. This was addressed in epan/dissectors/packet-q931.c by avoiding a use-after-free after a malformed packet prevented certain cleanup.