Language Selection

English French German Italian Portuguese Spanish

Don't Let Data Theft Happen to You

Filed under
Security

ABOUT two weeks ago, I was alarmed by a phone message from my bank alerting me to some "unusual activity" on my debit card. Unusual wasn't the word. Someone had gone on a shopping spree - $556.46 and $650.81 at one store, $264.99 and $300 in charges that were pending at another - and none of it was mine.

My debit card was still in my wallet. I hadn't used it in days. The bank said thieves might have created a counterfeit card. Someone - a store clerk, waiter, whoever - could have used a card reader to harvest the information imbedded in the magnetic strip to create a fake one. The bank assured me the debit account was closed and the thieves no longer had access to my cash - but who could be sure? How much of my personal information did these thieves get?

Between bouts of tears and frantic phone calls to my bank, I became obsessed with what I might have done to prevent this.

UNFORTUNATELY, although there are steps you can take to protect yourself - and you should - there are no guarantees. "You cannot protect yourself completely," said Edmund Mierzwinski, consumer program director at the U.S. Public Interest Research Group in Washington. "The best thing you can do is react swiftly if it does happen."

Besides the standard advice to shred personal documents, following are some tips I found useful:

Full Article

Ironic

Ironic, an article about Identity theft requires me to willing give up some of my identity to read the article. Sure I could make up a user profile, or use bugmenot, but instead, I choose not to support them in any way, shape, or form. I don't need (at least yet) to show photo ID to purchase their overrated rag, why do I need the equivalent to read their stuff on-line?

re: yeah baby - here's the rest of it

¶Avoid letting your cards out of your sight. Do not let store clerks take your card away on the pretext that there's a "problem."

¶Restrict the access to your personal data by signing up for the National Do Not Call Registry (www.donotcall.gov); remove your name and address from the phone book and reverse directories - and, most important, from the marketing lists of the credit bureaus to reduce credit card solicitations. The site www.optoutprescreen.com can help.

¶Consider freezing your credit report, an option available in a growing number of states. Freezing prevents anyone from opening up a new credit file in your name (a password lets you gain access to it), and it doesn't otherwise affect your credit rating.

¶Protect your home computer with a firewall, especially if you have a high-speed connection.

¶Rein in your Social Security number. Remove it from your checks, insurance cards and driver's license. Ask your bank not to use it as your identification number. Refuse to give your Social Security number to merchants, and be careful even with medical providers. The only time you are required by law to give your number, Mr. Mierzwinski said, is when a company needs it for government purposes, like tax matters, Social Security and Medicare.

¶Curtail electronic access to your bank accounts. Pay bills through snail mail. Avoid linking your checking to savings. Use a credit card for purchases rather than a debit card. Although I was able to get all $1,772.26 reimbursed, I was lucky. While individual liability for fraudulent credit card purchases is only $50, it can be higher for debit cards: up to $500 or even all the money in your account in some cases.

These and other preventive steps may help, but people really can't safeguard their money and their data on their own. Robert Douglas, the chief executive of PrivacyToday.com, a privacy advocate, believes that this is not an issue of consumer responsibility but of corporate negligence. "These companies are trying to tell people it's their fault, but the largest breaches have been within the financial services industry itself," Mr. Douglas said.

Mr. Douglas and Mr. Mierzwinski say that shredding documents is fine, but calling your state and local representatives is better. "Companies have refused to give consumers control over their financial DNA and they've refused to take responsibility for their actions," Mr. Mierzwinski said. "What will stop identity theft are stronger notification laws and stronger penalties, which we don't have now."

----
You talk the talk, but do you waddle the waddle?

yeah baby...

My thoughts exactly...from the ny times to a myriad of others...I simply refuse and write them to 'splain why. and we wonder why we end up on so many mailing lists and get so much spam. Oh, we won't sell your information. yeah right.

helios

re: ironic

I'm sorry guys, I forgot that it was sign up for site. Sad I usta try to post the whole thing and just give it a "source" link, but I got to where I forget which ones is which now. Sorry. I used to hate that too!!! But I signed up with a few of them since starting this site.

----
You talk the talk, but do you waddle the waddle?

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Docker 1.13, Containers, and DevOps

  • Introducing Docker 1.13
    Today we’re releasing Docker 1.13 with lots of new features, improvements and fixes to help Docker users with New Year’s resolutions to build more and better container apps. Docker 1.13 builds on and improves Docker swarm mode introduced in Docker 1.12 and has lots of other fixes. Read on for Docker 1.13 highlights.
  • Docker 1.13 Officially Released, Docker for AWS and Azure Ready for Production
    Docker announced today the general availability of Docker 1.13, the third major update of the open-source application container engine for GNU/Linux, macOS, and Microsoft Windows operating systems. Docker 1.13 has been in development for the past couple of months, during which it received no less than seven RC (Release Candidate) versions that implemented numerous improvements for the new Swarm Mode introduced in Docker 1.12, a few security features, as well as a new Remote API (version 1.25) and Client.
  • Distributed Fabric: A New Architecture for Container-Based Applications
    There’s a palpable sense of excitement in the application development world around container technology. Containers bring a new level of agility and speed to app development, giving developers the ability to break large monolithic apps into small, manageable microservices that can talk to one another, be more easily tested and deployed, and operate more efficiently as a full application. However, containers also demand a new architecture for the application services managing these microservices and apps, particularly in regards to service discovery — locating and consuming the services of those microservices.
  • DevOps trends emerging for 2017 and beyond
    Finally, one of the biggest trends for 2017 will not be just a focus on engaging and implementing some of these DevOps best practices into your enterprise, but a sweeping adoption of the DevOps/agile culture. This is because one of the most important – if not the absolute most key –tenets to a successful DevOps organization is culture. The enterprises that most espouse the shared responsibility, the empowered autonomous teams, the can-do attitudes, and the continuous learning environment in which DevOps thrives will see the biggest benefits.

Kernel Space/Linux

  • Optimizing Linux for Slow Computers
    It’s interesting, to consider what constitutes a power user of an operating system. For most people in the wider world a power user is someone who knows their way around Windows and Microsoft Office a lot, and can help them get their print jobs to come out right. For those of us in our community, and in particular Linux users though it’s a more difficult thing to nail down. If you’re a LibreOffice power user like your Windows counterpart, you’ve only really scratched the surface. Even if you’ve made your Raspberry Pi do all sorts of tricks in Python from the command line, or spent a career shepherding websites onto virtual Linux machines loaded with Apache and MySQL, are you then a power user compared to the person who knows their way around the system at the lower level and has an understanding of the kernel? Probably not. It’s like climbing a mountain with false summits, there are so many layers to power usership. So while some of you readers will be au fait with your OS at its very lowest level, most of us will be somewhere intermediate. We’ll know our way around our OS in terms of the things we do with it, and while those things might be quite advanced we’ll rely on our distribution packager to take care of the vast majority of the hard work.
  • Long-Term Maintenance, or How to (Mis-)Manage Embedded Systems for 10+ Years
    In this presentation, kernel hacker Jan Lübbe will explain why apparently reasonable approaches to long-term maintenance fail and how to establish a sustainable workflow instead.
  • Linux 4.9 Is the Next Long-Term Supported Kernel Branch, Says Greg Kroah-Hartman
    Linux kernel maintainer Greg Kroah-Hartman confirmed today, January 19, 2017, in a short message, on his Google+ page, that the Linux 4.9 branch is now marked as "longterm," or as some of you know as LTS (Long-Term Support). The story behind Linux kernel 4.9 becoming the next long-term supported series dates from way before it's launch last month, on December 11, when Linus Torvalds officially announced the new branch. It all started back on August 12, 2016, when Greg Kroah-Hartman dropped a quick Google+ post to say "4.9 == next LTS kernel."
  • Maintainers Don't Scale
    First let’s look at how the kernel community works, and how a change gets merged into Linus Torvalds’ repository. Changes are submitted as patches to mailing list, then get some review and eventually get applied by a maintainer to that maintainer’s git tree. Each maintainer then sends pull request, often directly to Linus. With a few big subsystems (networking, graphics and ARM-SoC are the major ones) there’s a second or third level of sub-maintainers in. 80% of the patches get merged this way, only 20% are committed by a maintainer directly. Most maintainers are just that, a single person, and often responsible for a bunch of different areas in the kernel with corresponding different git branches and repositories. To my knowledge there are only three subsystems that have embraced group maintainership models of different kinds: TIP (x86 and core kernel), ARM-SoC and the graphics subsystem (DRM).

Graphics in Linux

  • RADV Vulkan Driver Has Geometry Shader Support For Testing
    David Airlie has published a set of 31 patches for testing that provide initial support for geometry shaders within the RADV Radeon Vulkan driver. While RadeonSI has long supported geometry shaders, it's been a bigger work item bringing it to this open-source Radeon Vulkan driver within Mesa. The patches are enough for Vulkan geometry shaders to get working on RADV, but Airlie explains that the support isn't gold: "This is a first pass at geometry shader support on radv, all the code should be here in reviewable pieces, it seems to mostly pass CTS tests but triggers some llvm 3.9 bugs around kill, and there might still be a GPU hang in here, but this should still be a good place to start reviewing."
  • libinput 1.6.0
    This release fixes the slow touchpad acceleration on touchpads with less than 1000dpi, a missing call to normalized the deltas was the source of the issue.
  • Libinput 1.6 Released With New Touchpad Acceleration
    Libinput 1.6.0 was announced a short time ago on wayland-devel.
  • Mesa 17 Gets a First Release Candidate, Final Planned for Early February 2017
    Collabora's Emil Velikov announced today, January 19, 2017, the availability of the first of many Release Candidate (RC) development versions of the upcoming and highly anticipated Mesa 17.0.0 3D Graphics Library. Mesa 17 is shaping up to be a huge milestone that should dramatically improve the performance of the bundled open-source graphics drivers for Intel, AMD Radeon, Nvidia graphics cards on a Linux-based operating system. Just the other day it enabled OpenGL 4.5 support for Intel Haswell GPUs, which is already a big achievement.

Android Leftovers

  • Donald Trump has surrendered his Android phone
    Donald Trump has given up his beloved Android phone ahead of today’s inauguration, the Associated Press reports, though it is unclear what type of device he will use in the White House. According to The New York Times, Trump is now using a more secure, encrypted handset that was approved by the Secret Service. He also has a different phone number, the Times reports, citing people close to the president-elect. Trump doesn’t use email, but he does use his Android phone to tweet. He’s also been very accessible throughout the presidential campaign and transition, taking calls from reporters, politicians, and world leaders. Malcolm Turnbull, the prime minister of Australia, called Trump to congratulate him on his electoral victory after getting his cellphone number from professional golfer Greg Norman.
  • Best affordable Android smartphones you can buy [January 2017]
    There are new smartphones hitting the market constantly, but which is the best to pick up when you’re trying to save a buck or two? We’ve seen some great launches this summer and we’re only expecting more over the coming months, but for now, let’s go over the best affordable Android smartphones you can go pick up today…
  • A list of every Samsung phone getting Android 7.0 Nougat this year
  • WatchMaker to support Gear S2 & Gear S3, 1000s of watchfaces incoming
    WatchMaker, a popular Android and Android Wear watchface platform, has some good news for our readers. They are currently in the process of expanding their supported platforms and will be targeting Tizen and its latest wearable smartwatches, the Samsung Gear S2 and Gear S3.