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

9/9/2008
03:44 PM
Keith Ferrell
Keith Ferrell
Commentary
50%
50%

Top Tips For Preventing Identity Theft

Your customers' and clients' private information should be as important to you as their business -- and should be protected just as carefully, according to a new book on identity theft prevention techniques. Take a look at the top tips below.

Your customers' and clients' private information should be as important to you as their business -- and should be protected just as carefully, according to a new book on identity theft prevention techniques. Take a look at the top tips below.Jim Stickley's The Truth About Identity Theft, out in paperback the first of September, includes nugget after nugget of good information about how to make sure your customers' data remains their and, just as important, if it does get lost it wasn't you or any of your employees who lost it.

Among the top tips:

Only ask for the customer information you need; extra information creates extra risk and in the case of some date such as Social Security numbers, the request may actually be illegal.

Encrypt all data on your computers and, crucially, encrypt all archival backups.

If you backup your own data, store the backup tape or disc in a secure place: a bank safety deposit box, for instance.

Enable firewall protection on your computers.

Patch all systems as soon as patches become available: delay equals increased risk.

Insist that all passwords be at least 10 characters, mixing numbers and letters in random fashion (don't use recognizable words, however obscure) and include at least one random symbol (the @ # $ % % & and so on above the numeral keys.)

Test the strength of your passwords at qqq.microsoft.com/protect/yourself/password/checker.mspx

If you do have a data breach inform your customers at the same time you inform all other parties (financial institutions, law enforcement agencies.) Don't make things worse by waiting.

Plenty more in the book, all of it good advice from a recognized breach expert.

Might add another tip: have your employees read Jim Stickley's book.

Some audio samples are available here.

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/3/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
New 'Nanodegree' Program Provides Hands-On Cybersecurity Training
Nicole Ferraro, Contributing Writer,  8/3/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-16248
PUBLISHED: 2020-08-09
** DISPUTED ** Prometheus Blackbox Exporter through 0.17.0 allows /probe?target= SSRF. NOTE: follow-on discussion suggests that this might plausibly be interpreted as both intended functionality and also a vulnerability.
CVE-2020-15820
PUBLISHED: 2020-08-08
In JetBrains YouTrack before 2020.2.6881, the markdown parser could disclose hidden file existence.
CVE-2020-15821
PUBLISHED: 2020-08-08
In JetBrains YouTrack before 2020.2.6881, a user without permission is able to create an article draft.
CVE-2020-15823
PUBLISHED: 2020-08-08
JetBrains YouTrack before 2020.2.8873 is vulnerable to SSRF in the Workflow component.
CVE-2020-15824
PUBLISHED: 2020-08-08
In JetBrains Kotlin before 1.4.0, there is a script-cache privilege escalation vulnerability due to kotlin-main-kts cached scripts in the system temp directory, which is shared by all users by default.