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
Compliance: The Surprising Gift Of Windows XP
Newest First  |  Oldest First  |  Threaded View
Marilyn Cohodas
100%
0%
Marilyn Cohodas,
User Rank: Strategist
6/5/2014 | 9:42:04 AM
Re: Interesting Y2K analogy
Great points all! Plus, there's one other difference, that just occurred to me. In the runup to Y2k (1999-2000), compliance regs like HiPAA and Sarbanes-Oxley weren't even on the drawing board. Those laws came into existence later in the decade. 
gphillips35101
50%
50%
gphillips35101,
User Rank: Author
6/5/2014 | 9:33:37 AM
Re: Interesting Y2K analogy
Hi Marilyn, I agree with you that Y2K had much more of a doomsday sentiment and for a number of reasons. Still, XP end-of-support is one of the rate "events" similar to Y2K since Y2K. I have small business clients finally updating computers and our large clients have been even more focused on the task.

There is even more focus in organizations with compliance requriements, where waiting until a refesh cycle completes is not an option. And if they have a proper refresch cycle, they should not have hit this deadline with any XP computers. There is not the general public fear of course but it is still one of the rare events that was not ignored. Thanks!! G
Marilyn Cohodas
100%
0%
Marilyn Cohodas,
User Rank: Strategist
6/3/2014 | 3:17:51 PM
Interesting Y2K analogy
Hi Glenn. I take your point that Y2k presented a unique opportunity for organizations to spend money and update antiquated computer systems -- and perhaps the same will hold true for the end of life support for XP. Still, if my memory servers me correctly, there was much more of a doomsday sentiment surrounding Y2k. With XP organizations can ignore and keep using, pull off line, or continue with their traditional desktop refresh cycles until they are fully replaced. 


Data Privacy Protections for the Most Vulnerable -- Children
Dimitri Sirota, Founder & CEO of BigID,  10/17/2019
Sodinokibi Ransomware: Where Attackers' Money Goes
Kelly Sheridan, Staff Editor, Dark Reading,  10/15/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
2019 Online Malware and Threats
2019 Online Malware and Threats
As cyberattacks become more frequent and more sophisticated, enterprise security teams are under unprecedented pressure to respond. Is your organization ready?
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-18214
PUBLISHED: 2019-10-19
The Video_Converter app 0.1.0 for Nextcloud allows denial of service (CPU and memory consumption) via multiple concurrent conversions because many FFmpeg processes may be running at once. (The workload is not queued for serial execution.)
CVE-2019-18202
PUBLISHED: 2019-10-19
Information Disclosure is possible on WAGO Series PFC100 and PFC200 devices before FW12 due to improper access control. A remote attacker can check for the existence of paths and file names via crafted HTTP requests.
CVE-2019-18209
PUBLISHED: 2019-10-19
templates/pad.html in Etherpad-Lite 1.7.5 has XSS when the browser does not encode the path of the URL, as demonstrated by Internet Explorer.
CVE-2019-18198
PUBLISHED: 2019-10-18
In the Linux kernel before 5.3.4, a reference count usage error in the fib6_rule_suppress() function in the fib6 suppression feature of net/ipv6/fib6_rules.c, when handling the FIB_LOOKUP_NOREF flag, can be exploited by a local attacker to corrupt memory, aka CID-ca7a03c41753.
CVE-2019-18197
PUBLISHED: 2019-10-18
In xsltCopyText in transform.c in libxslt 1.1.33, a pointer variable isn't reset under certain circumstances. If the relevant memory area happened to be freed and reused in a certain way, a bounds check could fail and memory outside a buffer could be written to, or uninitialized data could be disclo...