Perimeter
Guest Blog // Selected Security Content Provided By Sophos
What's This?
9/25/2012
12:13 PM
Dark Reading
Dark Reading
Security Insights
50%
50%

Whether You Call It Modern Or Metro, Here Are Eight Security Tips For Windows 8

Windows 8 a case of improved security, increased vigilance

The naming of its user interface aside, on Oct. 26 Microsoft is releasing Windows 8, the newest version of the Windows operating system. Although Windows 8 offers enhanced security features, it also raises new security concerns because of changes to the graphical user interface and a new online app store. Courtesy of Darren Teagles, senior poduct manager, Sophos, here are eight security tips that can help you stay secure as you move to Windows 8.

1. Exercise caution with apps for the new Windows 8 user interface. Some familiar applications have been completely rewritten for the new Windows 8 UI. As a result, they may work completely differently, despite looking the same. For example, an application historically delivered as an executable could now be entirely Web-based. This impacts the visibility your existing security and monitoring tools have into these apps.

2. Use the Windows 8 style UI version of Internet Explorer. By default, plug-ins are disabled, blocking a major target for exploit kits and Blackhole attacks.

3. Make sure your security vendor can flag malicious Windows 8 UI apps. Windows 8 UI apps have important differences from regular applications, and your security product should be able to distinguish the two. The security product should correctly flag malicious or modified Windows 8 UI applications (tampered, modified, invalid license).

4. Disable hard-drive encryption hibernation. Hard-drive encryption is a cornerstone of data protection. If possible, disable the hibernation option in Windows 8 through group policy because it doesn’t always work well with encryption.

5. Make sure your hardware carries the "Designed for Windows 8" logo. To carry this logo, hardware must be UEFI-compliant. This means you can take advantage of the secure boot functionality available in Windows 8. Secure boot is designed to ensure the pre-OS environment is secure to minimize the risk from boot loader attacks.

6. Make application control a priority. The Windows 8 app store makes application control increasingly important for both malware prevention and productivity control. While the Windows Store will be secured, history shows that malicious apps are likely to slip through. Disable the use of apps that aren’t relevant to your organization.

7. Treat Windows RT (ARM) devices like any other mobile device. Make sure you impose the same security levels on Windows RT devices as all others. You should have the ability to control, track, remote wipe, and encrypt them.

8. Block near field communications features you don’t need. Windows 8 now caters to near field communications within the operating system. Because it uses Wi-Fi, it’s another potential vector for security attacks. Block or disable features you don't need to close unnecessary security holes.

Bonus tip: Don't allow sign-in to Windows 8 PCs with a Live ID. Live ID sign-on lets your users personalize their computers based on their own settings, regardless of which computer they sign onto. In doing so, all Windows 8 Style UI apps will be reacquired along with their settings, and apps will be automatically signed in where they use a Windows Live ID. This opens the potential for accidental data loss.

Of course, all the old security rules also apply with Window 8. It's still a bad idea to disable the lock screen or allow automatic log-on. Keep to your principles and, above all, remain vigilant.

Download a PDF of "The Top Eight Security Tips for Windows 8"on Sophos Security News and Trends.

Brian Royer, a security subject matter expert, Sophos U.S., is partnering with SophosLabs to research and report on the latest trends in malware, web threats, endpoint and data protection, mobile security, cloud computing and data center virtualization.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
CBess
50%
50%
CBess,
User Rank: Apprentice
10/4/2012 | 6:56:09 PM
re: Whether You Call It Modern Or Metro, Here Are Eight Security Tips For Windows 8
When you say-ádisable NFC-á"Because it uses Wi-Fi", you left me a little confused NFC works around 13 MHz where Wi-Fi is in the multiple gigahertz range. What did you mean?
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading December Tech Digest
Experts weigh in on the pros and cons of end-user security training.
Flash Poll
Title Partner’s Role in Perimeter Security
Title Partner’s Role in Perimeter Security
Considering how prevalent third-party attacks are, we need to ask hard questions about how partners and suppliers are safeguarding systems and data.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-5426
Published: 2014-11-27
MatrikonOPC OPC Server for DNP3 1.2.3 and earlier allows remote attackers to cause a denial of service (unhandled exception and DNP3 process crash) via a crafted message.

CVE-2014-2037
Published: 2014-11-26
Openswan 2.6.40 allows remote attackers to cause a denial of service (NULL pointer dereference and IKE daemon restart) via IKEv2 packets that lack expected payloads. NOTE: this vulnerability exists because of an incomplete fix for CVE 2013-6466.

CVE-2014-6609
Published: 2014-11-26
The res_pjsip_pubsub module in Asterisk Open Source 12.x before 12.5.1 allows remote authenticated users to cause a denial of service (crash) via crafted headers in a SIP SUBSCRIBE request for an event package.

CVE-2014-6610
Published: 2014-11-26
Asterisk Open Source 11.x before 11.12.1 and 12.x before 12.5.1 and Certified Asterisk 11.6 before 11.6-cert6, when using the res_fax_spandsp module, allows remote authenticated users to cause a denial of service (crash) via an out of call message, which is not properly handled in the ReceiveFax dia...

CVE-2014-7141
Published: 2014-11-26
The pinger in Squid 3.x before 3.4.8 allows remote attackers to obtain sensitive information or cause a denial of service (out-of-bounds read and crash) via a crafted type in an (1) ICMP or (2) ICMP6 packet.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Now that the holiday season is about to begin both online and in stores, will this be yet another season of nonstop gifting to cybercriminals?