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.

Risk

12/9/2009
12:29 PM
Fredric Paul
Fredric Paul
Commentary
50%
50%

5 Tips To Help SMBs Stop Identity Theft

Many SMBs like to think identity theft is someone else's problem. Sure, consumers have to worry about it, and so do large corporations that collect information on millions of customers. But not smaller companies, right? After all, who'd bother targeting a run-of-the-mill SMB?

Many SMBs like to think identity theft is someone else's problem. Sure, consumers have to worry about it, and so do large corporations that collect information on millions of customers. But not smaller companies, right? After all, who'd bother targeting a run-of-the-mill SMB?Well, it turns out that you don't even have to be targeted to be vulnerable -- in a couple of different ways. First of all, losing a laptop or misplacing a thumb drive can dump sensitive data into the hands of folks who might misuse it. Secondly, consumers want to feel safe buying from your company, and many will go elsewhere if you can't give them confidence that their data is secure. The costs can add up.

According to Scott Mitic, CEO of TrustedID, which specializes in helping companies avoid identity theft attacks, The Center for Identity Management & Information Protection tracked 50% of the identity theft cases to information lost by a business. And the Identity Theft Resource Center estimates that since 2007, identity theft has cost businesses $49 billion.

So what can your business do about it? Mitic offers 5 tips:

1. Collect only information you need from your customers. The more information you store, the higher your storage costs, the more information you can lose, and the your greater potential liability.

2. Invest in software and hardware to protect your customers' data. There are a number of industry best practices for secure data storage and privacy. Online businesses should create a Privacy Policy that details how the company collects, stores, secures, and shares data. Make sure that customers know about the policy.

3. Limit access to sensitive information. Only employees who have a valid business reason should be able to access that data. And no matter how trustworthy you consider your workers, you may want to err on the side of caution and require background checks and even drug tests.

4. Secure your physical workplace. Identity thieves can steal information directly from offices, so it's important to routinely lock mailboxes, desks, file cabinets, computers... anything that might contain valuable information. At the very least, you should require all office doors to be locked every night, and you might want to consider installing video cameras to monitor nighttime activity.

5. Properly dispose of information when you no longer need it. Use a cross-cut shredder on all paper documents -- even ones you don't think are sensitive. Make sure electronic files are completely destroyed -- simply deleting them in Windows is nowhere near good enough. Fortunately, there are plenty of industrial-strength tools to fully destroy electronic files. If your company deals with of large amounts of sensitive information, consider hiring a trustworthy outside company to do handle it for you.

More From bMighty:

Follow Fredric Paul on Twitter @ http://twitter.com/TheFreditor Follow bMighty.com on Twitter @ http://twitter.com/bMighty Put a bMighty toolbar on your browser Put a bMighty gadget on your iGoogle page Get bMighty on your mobile device

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
I 'Hacked' My Accounts Using My Mobile Number: Here's What I Learned
Nicole Sette, Director in the Cyber Risk practice of Kroll, a division of Duff & Phelps,  11/19/2019
DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Attackers' Costs Increasing as Businesses Focus on Security
Robert Lemos, Contributing Writer,  11/15/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-2079
PUBLISHED: 2019-11-22
A cross-site request forgery (CSRF) vulnerability in the Activity module 6.x-1.x for Drupal.
CVE-2019-11325
PUBLISHED: 2019-11-21
An issue was discovered in Symfony before 4.2.12 and 4.3.x before 4.3.8. The VarExport component incorrectly escapes strings, allowing some specially crafted ones to escalate to execution of arbitrary PHP code. This is related to symfony/var-exporter.
CVE-2019-18887
PUBLISHED: 2019-11-21
An issue was discovered in Symfony 2.8.0 through 2.8.50, 3.4.0 through 3.4.34, 4.2.0 through 4.2.11, and 4.3.0 through 4.3.7. The UriSigner was subject to timing attacks. This is related to symfony/http-kernel.
CVE-2019-18888
PUBLISHED: 2019-11-21
An issue was discovered in Symfony 2.8.0 through 2.8.50, 3.4.0 through 3.4.34, 4.2.0 through 4.2.11, and 4.3.0 through 4.3.7. If an application passes unvalidated user input as the file for which MIME type validation should occur, then arbitrary arguments are passed to the underlying file command. T...
CVE-2019-18889
PUBLISHED: 2019-11-21
An issue was discovered in Symfony 3.4.0 through 3.4.34, 4.2.0 through 4.2.11, and 4.3.0 through 4.3.7. Serializing certain cache adapter interfaces could result in remote code injection. This is related to symfony/cache.