In Brief

10 Rules for Responsible Investigations

Readers' best practices for making sure the sleuth work matches the allegation

By Sarah D. Scalet

April 13, 2007CSO

How do you run a responsible investigation, one that’s done not only in a legal and ethical way (of course that’s a prerequisite) but that’s also effective? To find out, and as a follow-up to our analysis of Hewlett-Packard’s recent troubles over its inquiry into boardroom leaks, we asked readers of CSOonline.com. We posted a preliminary list of best practices at Disclosures, the blog from CSO’s editors, and invited readers to add their own. Below, the results.

1) Don’t break the law. Don’t hire anyone (or hire anyone who will hire anyone) who will break the law.

2) Before you start, agree on some general objectives. What do you want to accomplish? Set milestones to measure your progress. The overarching goal, of course, is to protect the corporation—both from whatever allegation you’re investigating and from the possible repercussions of how you investigate it.

3) Seek the truth. Don’t start with a preconceived outcome and try to make the facts fit—even if it is more convenient for the company.

4) Match the investigation to the crime. Don’t launch a $10,000 investigation into a $1,000 crime. Beware of a tendency to hit the ground running to catch the bad guys quickly, which could result in an investigation that veers off course and creates a larger issue than the reason the investigation was started in the first place.

5) Match the investigatory methods to your corporate culture. There’s a huge gray area of ethics in investigations. Make sure that what you’re doing makes sense for your company and follows practices that your CEO would be willing to defend on camera.

6) Be consistent. Don’t treat a high-performing employee different from the slacker for the same offense. Apply even standards in how you manage contractors and subcontractors. Ensure that whatever practice you use is well documented, can be replicated and can be presented to opposing counsel.

7) Practice strict “need to know” rules during the investigation. Don’t allow allegations to ruin someone’s reputation. Expand the base of people involved only when absolutely necessary, even at the expense of ruffling some senior corporate egos. There will be plenty of time to brief people once the allegations are confirmed.

8) Make sure employees know their rights. Your personnel policy should state clearly that phone conversations on company phones and data that traverses the company network or company equipment is the property of the company and as such may be monitored, tracked and audited.

9) Decide when to tell the subject of an investigation. Have a formal policy for when those under investigation will (or will not) be notified.

RESOURCE CENTER
Loading...
VIRTUAL CONFERENCE
Data Center Directions Virtual Conference

Data Center VCAttend this free, 100% online event exploring tools and techniques for making your data center deliver for today and tomorrow.

» Learn more and register here

WEBCAST
The Surest Path to Effective and Efficient Compliance

VeriSignIn this webcast, we explore why and how — with best practices, practical tips and solutions that work — to ease your compliance challenge.

» View the webcast

Featured Sponsors
Sponsored Links

Think your data is safe? Think again. It's time to Outthink the Threat. Get eBook now

Prepare for (ISC)2® Certification With Villanova - Online

Rolling the dice with your security? Take the Self-Assessment Test now

Diebold: Frost & Sullivan Global Physical Security Systems Integrator of the Year

Revolutionizing Endpoint Security with a Single Agent

Envision Identity-Based Access Control for the Datacenter

IT Service Management: Metrics That Matter

ITCi White Paper: Challenges and Opportunities of PCI

Effective Security with a Continuous Approach to ISO 27001 Compliance

E-LOAN Maintains Reputation as a Privacy Leader with Symantec

Data Loss Prevention: Keeping Sensitive Data Out of the Wrong Hands

Prudential Financial Protects its Brand with Symantec

Envision Identity-Based Access Control for the Datacenter

Digital Identity Protection and Data Security Get Personal

Welcome to the age of Service-Oriented Security (SOS)

Enabling Compliance with Converged Mainframe Security and Storage

The Case for Business Software Assurance ~ Securing Your Applications

Forrester Total Economic Impact (TEI) report: Save Millions in Fraud Losses.

Learn how the new Quad-Core AMD Opteron™ processor improves performance

Configuration Audit and Control for Virtualized Environments

Take our CSO role survey and receive a copy of the results

Ponemon Study: How Much Does a Data Breach "Cost"?

Data Protection: Challenges for the Traveling User

Key strategies for C-level executives and security staff

Configuration Assessment: Choosing the Right Solution

The PCI Data Security Standard

Configuration Audit and Control for Virtualized Environments

7 Requirements of Data Loss Prevention

Information Security: Data Drains and How to Prevent Loss

How Are Open Source Development Communities Embracing Security Best Practices?

IDC Defines an Identity and Access Management Submarket

Using Likewise to Comply with PCI Data Security Standard

IDC Defines an Identity and Access Management Submarket for Managing Privileged User Accounts and Meeting GRC Requirements

Everything Today's CISO Needs to Know About Using SSO to Succeed in the Web 2.0 Era

Solving Online Credit Fraud Using Device Reputation