Connect with us


US-CERT issues guide on how to properly dispose of your electronic devices



The old hard disk drive is disintegrating in space. Conception of passage of time and obsolete technology

Getty Images/iStockphoto

Over the past few years, there have been numerous reports, and studies about how second-hand devices that have been put up for sale still contained information from previous owners, exposing those individuals to scams, blackmailing, or identity theft.

This week, the United States Computer Emergency Readiness Team (US-CERT), a division part of the Department of Homeland Security (DHS), has published an official advisory with instructions and recommendations for properly deleting data from electronic devices that a user wishes to dispose of in one form or another.

These instructions are universal and can be applied to computers, smartphones, tablets, cameras, media players, external storage devices, and even gaming consoles.

Many of these recommendations are also common knowledge for IT industry veterans, but the guide was also written with non-technical users in mind. So let’s take a deep dive into the proper device sanitization procedures.

1. Backing up data

The first –and pretty obvious– step before attempting any device sanitization operation is to back up your data. We won’t go too deep into this one. There are various methods and software that can help you with that. Any cursory Google search will unearth hundreds of tutorials for backing up data from almost any type of device, from PCs to gaming consoles.

2. Deleting data

This second step might sound simple, but it’s not. Deleting data might not be as trivial as it sounds, and sometimes deleted data still hangs around, depending on your device and its OS quirks, and data may reside in memory cards you forget to pull out of the devices you sell.

  • Computers – Use disk cleaning software designed for your OS to permanently remove the data stored on a computer hard drive or other attached storage mediums to prevent the possibility of recovery. There are plenty of open source tools for performing a “secure erase,” but some operating systems also come with built-in tools. Check step 3 for some links.
  • Smartphones and tablets – Ensure that all data is removed from your device by performing a “hard reset.” This will return the device to its original factory settings. Each device has a different hard reset procedure, but most smartphones and tablets can be reset through their settings. In addition, physically remove the memory card and the subscriber identity module (SIM) card, if your device has one, before giving away or selling the device.
  • Digital cameras, media players, and gaming consoles – Perform a standard factory reset (i.e., a hard reset) and physically remove the hard drive or memory card.
  • Office equipment (e.g., copiers, printers, fax machines, multifunction devices) – Remove any memory cards from the equipment. Perform a full manufacture reset to restore the equipment to its factory default.

It is advised that users don’t sell or give away devices that still contain their old memory cards. Memory cards should be pulled from any device. But if you have to, it’s advised to delete any data from those cards as well. Attaching the memory card to a card reader or through the device itself, and then connecting it to a PC will let users securely wipe the card.

3. Overwriting your old data

But just deleting your data isn’t usually enough. Leftover information can still reside in unallocated storage space. Forensics software can help buyers or new owners investigate old devices for any data that was left over on a device’s storage.

To prevent attackers from recovering any old files, it is recommended that users overwrite storage devices with random binary data.

Windows has a built-in utility that can do this, named cipher.exe, but users can also use the “format” command with special parameters.

Macs also have a built-in feature to securely wipe and overwrite any attached storage, while on Linux there a tool named shred that can help users delete and overwrite data with one command.

Don’t forget. Don’t just overwrite hard drives. This operation can also be performed on USB thumb drives, memory cards, network attached storage (NAS) devices, and other storage systems.

4. Destroying

If you’re selling or handing down your device, this step is obviously optional. But if you’re working for a company or performing a Mr. Robot-like wipe down, here’s what US-CERT recommends in the case you need to physically destroy your old equipment, for legal or compliancy reasons.

Physical destruction of a device is the ultimate way to prevent others from retrieving your information. Specialized services are available that will disintegrate, burn, melt, or pulverize your computer drive and other devices. These sanitization methods are designed to completely destroy the media and are typically carried out at an outsourced metal destruction or licensed incineration facility. If you choose not to use a service, you can destroy your hard drive by driving nails or drilling holes into the device yourself. The remaining physical pieces of the drive must be small enough (at least 1/125 inches) that your information cannot be reconstructed from them. There are also hardware devices available that erase CDs and DVDs by destroying their surface.

  • Magnetic media degaussers. Degaussers expose devices to strong magnetic fields that remove the data that is magnetically stored on traditional magnetic media.
  • Solid-state destruction. The destruction of all data storage chip memory by crushing, shredding, or disintegration is called solid-state destruction. Solid-State Drives should be destroyed with devices that are specifically engineered for this purpose.
  • CD and DVD destruction. Many office and home paper shredders can shred CDs and DVDs (be sure to check that the shredder you are using can shred CDs and DVDs before attempting this method).

A NIST guideline from 2014 also provides additional instructions, if you have the time to go through 64 pages of more technical information.

If not, the instructions put forward by US-CERT should be more than enough. The advice is sorely needed, as several studies and surveys from past years have proven that many users tend to forget to wipe data from their devices:

  • A 2010 survey revealed that 50% of the second-hand mobile phones sold on eBay came with files and data on previous owners.
  • A 2012 survey conducted by the UK’s Information Commissioner’s Office (ICO) showed that one in ten second-hand hard drives still contained data from previous owners.
  • A 2015 study found that three-quarters of used hard drives contained data from previous owners.
  • A 2018 study by the University of Hertfordshire revealed that almost two-thirds of second-hand memory cards still contain data artifacts from previous owners.


Source link

Continue Reading
Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *


Managing Vulnerabilities in a Cloud Native World



This free 1-hour webinar from GigaOm Research brings together experts in Cloud Native Vulnerability Management, featuring analyst Iben Rodriguez and special guest from Palo Alto Networks, John Morello. The discussion will focus on optimizing cloud security posture and integration with enterprise tool sets.

We will review platforms delivering Security Posture Management and Workload Protection for Microservice based and Hybrid Cloud Workloads.

Registrants will learn how new customers can benefit from Prisma Cloud to better secure their complex multi-cloud environments. Existing customers will learn about new features they can take advantage of and how to optimize their limited resources.

Register now to join GigaOm and Palo Alto Networks for this free expert webinar.

The post Managing Vulnerabilities in a Cloud Native World appeared first on Gigaom.

Continue Reading


Security Tools Help Bring Dev and Security Teams Together



Software development teams are increasingly focused on identifying and mitigating any issues as quickly and completely as possible. This relates not only to software quality but also software security. Different organizations are at different levels when it comes to having their development teams and security teams working in concert, but the simple fact remains that there are far more developers out there than security engineers.

Those factors are leading organizations to consider security tooling and automation to proactively discover and resolve any software security issues throughout the development process. In the recent report, “GigaOm Radar for Developer Security Tools,” Shea Stewart examines a roundup of security tools aimed at software development teams.

Stewart identified three critical criteria to bear in mind when evaluating developer security tools. These include:

  • Vendors providing tools to improve application security can and should also enhance an organization’s overall security posture.
  • The prevailing “shift-left” mindset doesn’t necessarily mean the responsibility for reducing risk should shift to development, but instead focusing on security earlier in the process and continuing to do so throughout the development process will reduce risk and the need for extensive rework.
  • Security throughout the entire software development lifecycle (SDLC) is critical for any organization focused on reducing risk.

Figure 1. How Cybersecurity Applies Across Each Stage of the Software Development Lifecycle *Note: This report focuses only on the Developer Security Tooling area

Individual vendors have made varying levels of progress and innovation toward enhancing developer security. Following several acquisitions, Red Hat, Palo Alto Networks, and Rapid7 have all added tooling for developer security to their platforms. Stewart sees a couple of the smaller vendors like JFrog and Sonatype as continuing to innovate to remain ahead of the market.

Vendors delving into this category and moving deeper into “DevSecOps” all seem to be taking different approaches to their enhanced security tooling. While they are involving security in every aspect of the development process, some tend to be moving more quickly to match the pace of the SDLC. Others are trying to shore up existing platforms by adding functionality through acquisition. Both infrastructure and software developers are now sharing toolsets and processes, so these development security tools must account for the requirements of both groups.

While none of the 12 vendors evaluated in this report can provide comprehensive security throughout the entire SDLC, they all have their particular strengths and areas of focus. It is therefore incumbent upon the organization to fully and accurately assess its SDLC, involve the development and security teams, and match the unique requirements with the functionality provided by these tools. Even if it involves using more than one at different points throughout the process, focus on striking a balance between stringent security and simplifying the development process.

Read more: Key Criteria for Evaluating Developer Security Tools, and the Gigaom Radar for Developer Security Tool Companies.

The post Security Tools Help Bring Dev and Security Teams Together appeared first on Gigaom.

Continue Reading


Key Criteria for Evaluating User and Entity Behavior Analytics (UEBA)



Cybersecurity is a multidisciplinary practice that not only grows in complexity annually but evolves nearly as quickly. A survey of the security landscape today would reveal concerns ranging from the classic compromised servers to the relatively new DevSecOps practices aimed at securing the rapid deployment of new code and infrastructure. However, some things remain constant no matter how much change is introduced. While technology evolves and complexity varies, there is almost always a human component in
risks presented to an organization.

User Behavior Analysis (UBA) was designed to analyze the actions of users in an organization and attempt to identify normal and abnormal behaviors. From this analysis, malicious or risky behaviors can be detected. UBA solutions identify events that are not detectable using other methods because, unlike classic security tools (an IDS or SIEM for example), UBA does not simply pattern match or apply rule sets to data to identify security events. Instead, it looks for any and all deviations from baseline user activity.

As technology advanced and evolved, and the scope of what is connected to the network grew, the need to analyze entities other than users emerged. In response, entity analysis has been added to UBA to create UEBA or User and Entity Behavior Analysis. The strategy remains the same, but the scope of analysis has expanded to include entities involving things like daemons, processes, infrastructure, and so on.

How to Read this Report

This GigaOm report is one of a series of documents that helps IT organizations assess competing solutions in the context of well-defined features and criteria. For a fuller understanding consider reviewing the following reports:

Key Criteria report: A detailed market sector analysis that assesses the impact that key product features and criteria have on top-line solution characteristics—such as scalability, performance, and TCO—that drive purchase decisions.

GigaOm Radar report: A forward-looking analysis that plots the relative value and progression of vendor solutions along multiple axes based on strategy and execution. The Radar report includes a breakdown of each vendor’s offering in the sector.

Solution Profile: An in-depth vendor analysis that builds on the framework developed in the Key Criteria and Radar reports to assess a company’s engagement within a technology sector. This analysis includes forward-looking guidance around both strategy and product.

The post Key Criteria for Evaluating User and Entity Behavior Analytics (UEBA) appeared first on Gigaom.

Continue Reading