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.

Comments
GDPR Doesnt Need to be GDP-Argh!
Newest First  |  Oldest First  |  Threaded View
atrisk
50%
50%
atrisk,
User Rank: Strategist
4/6/2017 | 10:49:55 AM
GDPR- proactive approach
GDPR is the real deal.  Companies will take notice after a few fines are levied. IT needs to look at all devices that can act as a risk gateway. Mobile is a clear candidate and organizations need to look at services beyond pen testing. Have all the security on the server side simply means that they have already broken down your front door. Secure the mobile applications that are being used on devices, especially those on BYOD. Encrypt and monitor them, creating a barrier that prevents access to your servers. 
Joe Stanganelli
0%
100%
Joe Stanganelli,
User Rank: Ninja
4/5/2017 | 3:30:23 PM
Joe's take x3
Good tips.  My take on some of these items:

1) €20 million or 4 percent of your worldwide annual gross revenue, depending on the violation.

Good luck, I say, to EU regulators.  This is a hefty, scary max penalty.  In reality, I suspect that smaller enterprises/businesses have more to fear here than larger and more entrenched enterprises.  (I'm thinking now of the VW diesel scandal that, had US regulators gone full throttle, could have completely bankrupted and obliterated VW.)  For companies that regularly do business in the EU and aren't tech companies with which the EU already has a major bone to pick (e.g., Google, Facebook, etc.), there may be some leniency.

On the other hand, the first tests of this will show us just how serious the EU is when it comes to privacy matters, I suppose.  So while I have my pet theories, nothing surprises me anymore in the data privacy and data stewardship realm.



2) Encrypt data both at-rest and in-transit.


This advice -- which may be seen as a bit silly -- is an unfortunately important one, even in the US and in other more lightly regulated jurisdictions.  Even in the absence of regulations, the revelation of the lack of at-rest encryption in the case of a data breach -- even where it would not have actually helped mitigate matters any -- can be highly brand damaging.  (Remember the Anthem nee Wellpoint breach?)


3) Backups. Backups. Backups.

And -- more to the point -- SECURE your backups!  Seems like a "duh!" imperative, no?  Well, that "common sense" was lost on Adobe when they suffered their major breach of their backup systems, impacting over 150 million users.

I always have more to say on this topic because I work in the field, but for now I'll shut up.  3 bulletpoints in an Internet comment is enough for now.  ;)


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Enterprises Are Assessing Cybersecurity Risk in Today's Environment
The adoption of cloud services spurred by the COVID-19 pandemic has resulted in pressure on cyber-risk professionals to focus on vulnerabilities and new exposures that stem from pandemic-driven changes. Many cybersecurity pros expect fundamental, long-term changes to their organization's computing and data security due to the shift to more remote work and accelerated cloud adoption. Download this report from Dark Reading to learn more about their challenges and concerns.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-46547
PUBLISHED: 2022-01-27
Cesanta MJS v2.20.0 was discovered to contain a SEGV vulnerability via /usr/local/bin/mjs+0x2c17e. This vulnerability can lead to a Denial of Service (DoS).
CVE-2021-46548
PUBLISHED: 2022-01-27
Cesanta MJS v2.20.0 was discovered to contain a SEGV vulnerability via add_lineno_map_item at src/mjs_bcode.c. This vulnerability can lead to a Denial of Service (DoS).
CVE-2021-46549
PUBLISHED: 2022-01-27
Cesanta MJS v2.20.0 was discovered to contain a SEGV vulnerability via parse_cval_type at src/mjs_ffi.c. This vulnerability can lead to a Denial of Service (DoS).
CVE-2021-46550
PUBLISHED: 2022-01-27
Cesanta MJS v2.20.0 was discovered to contain a SEGV vulnerability via free_json_frame at src/mjs_json.c. This vulnerability can lead to a Denial of Service (DoS).
CVE-2021-46553
PUBLISHED: 2022-01-27
Cesanta MJS v2.20.0 was discovered to contain a SEGV vulnerability via mjs_set_internal at src/mjs_object.c. This vulnerability can lead to a Denial of Service (DoS).