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.

Operations

2/21/2017
10:30 AM
Udi Yavo
Udi Yavo
Commentary
Connect Directly
Twitter
LinkedIn
RSS
E-Mail vvv
50%
50%

Preparing Security For Windows 7 End-Of-Life Support

Moving to Microsoft's latest OS may give you flashbacks to when XP support ended.

Last month, Microsoft announced it will end support for Windows 7 in 2020, giving customers three years to upgrade their systems to Windows 10. In the short term, computers running Windows 7 will still work, and Microsoft will still share security updates for the operating system. The latter is good, especially as most cyber attacks today target Windows 7 simply because it’s one of the most popular operating systems.

Attacks on Windows 7 typically rely on vulnerabilities in the OS, and each time a vulnerability is found, Microsoft works to develop and release a patch. However, in January 2020, once Windows 7 reaches the end of its life, any new vulnerability found and reported will not be patched. Thus, in a few years, Windows 7 will become even more vulnerable.

Attackers are taking note of the latest news and will soon begin to look at Windows 7 as even-lower-hanging fruit — much as they did with Windows XP over the last couple of years. As you'll recall, support for Windows XP ended April 8, 2014, but the vulnerabilities in the old OS remain (not to mention, XP still has millions of users globally).

For myriad enterprise users of Windows 7, three years to get everything transitioned over to Windows 10 is actually not that long. After all, it's not just the changing of some application; rather, it requires installing a new operating system and making sure that the upgrade doesn't cause current applications to break.

If you’re planning to make the move, note well: it will be costly. First, there’s an actual cost of an upgrade — from the cost of the license to the IT used to support the installation and testing. Second, those enterprises that don't hit the public deadline might need to pay additional fees for customized extended support programs. These customized extended support licenses were offered by Microsoft when XP expired. In fact, enterprises (ironically, budget-tight organizations including the US government) have admitted to paying millions of dollars for XP extended support because they needed more time to transition.

The sad reality for those planning to pay for an extension is that this type of support is effective only against very simple attacks. For example, bypasses are now a common technique in the attacker's toolbox to navigate around Enhanced Mitigation Experience Toolkit (EMET), Microsoft's freeware security toolkit for Windows.

Here are some tips for staying secure while tackling the upgrade process:

  • Segment the network by cutting off critical devices from others in the network. Take it a step further and remove any unnecessary devices from the network.
  • Ensure that security controls on the devices are turned on (believe it or not, they're not necessarily enabled).
  • Place third-party solutions on these devices to close the gaps on legacy systems and ensure that data is protected.

Before you get too overwhelmed by the task of upgrading, note that this won’t be nearly as complicated or expensive as upgrading from XP. Windows XP still supported old DOS applications while DOS was pretty much obliterated since Windows 7, thus expiring legacy applications that were still functioning.

Related Content:

Udi Yavo has more than 15 years of experience in cybersecurity with a proven track record in leading cutting-edge cybersecurity R&D projects. Prior to enSilo, Udi spearheaded the direction of the cybersecurity unit at the National Electronic Warfare Research & Simulation ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
aolcustomerservice
50%
50%
aolcustomerservice,
User Rank: Apprentice
3/29/2018 | 4:01:29 AM
Windows 7
I think Windows is the secure operating system. Microsoft always brings updates in order to secure it.  I have some queries its security then visit Windows 7 Customer Care Helpline.The assured me that it is secure.
technicalaccademy
50%
50%
technicalaccademy,
User Rank: Apprentice
3/17/2017 | 5:03:05 AM
microsofttechnology
nice post
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-15564
PUBLISHED: 2020-07-07
An issue was discovered in Xen through 4.13.x, allowing Arm guest OS users to cause a hypervisor crash because of a missing alignment check in VCPUOP_register_vcpu_info. The hypercall VCPUOP_register_vcpu_info is used by a guest to register a shared region with the hypervisor. The region will be map...
CVE-2020-15565
PUBLISHED: 2020-07-07
An issue was discovered in Xen through 4.13.x, allowing x86 Intel HVM guest OS users to cause a host OS denial of service or possibly gain privileges because of insufficient cache write-back under VT-d. When page tables are shared between IOMMU and CPU, changes to them require flushing of both TLBs....
CVE-2020-15566
PUBLISHED: 2020-07-07
An issue was discovered in Xen through 4.13.x, allowing guest OS users to cause a host OS crash because of incorrect error handling in event-channel port allocation. The allocation of an event-channel port may fail for multiple reasons: (1) port is already in use, (2) the memory allocation failed, o...
CVE-2020-15567
PUBLISHED: 2020-07-07
An issue was discovered in Xen through 4.13.x, allowing Intel guest OS users to gain privileges or cause a denial of service because of non-atomic modification of a live EPT PTE. When mapping guest EPT (nested paging) tables, Xen would in some circumstances use a series of non-atomic bitfield writes...
CVE-2020-15563
PUBLISHED: 2020-07-07
An issue was discovered in Xen through 4.13.x, allowing x86 HVM guest OS users to cause a hypervisor crash. An inverted conditional in x86 HVM guests' dirty video RAM tracking code allows such guests to make Xen de-reference a pointer guaranteed to point at unmapped space. A malicious or buggy HVM g...