> ## Content Index
> Fetch the complete content index at: https://www.healthdatacon.io/llms.txt
> Use this file to discover other available public pages before exploring further.

# Information Insecurity, Inside Edition
- URL: https://www.healthdatacon.io/articles/information-insecurity-inside-edition/
- Published: 2011-09-29T04:00:00.000Z
- Updated: 2026-11-10T10:57:36.000Z
- Description: Heres what to do to protect yourself from threats inside your organization.
- Author: HDM Staff
- Tags: Cybersecurity

Health care organizations put up elaborate safeguards to protect their data from external threats, but internal security breachesstealing data for malicious purposes, or clinicians peeking at medical records of celebrities and friends/neighborsare all too common. Following are tips on how to protect the inside perimeter.  
  
  
FROM: Randy Trzeciak , Computer Emergency Response Team, Carnegie Mellon University; and, Insider Threats: Actual Attacks by  
Current and Former Software Engineers, Computer Emergency Response Team, Carnegie Mellon University.  

  
## Develop an insider incident response plan.

![](https://hdmpublishing.wpengine.com/wp-content/uploads/2015/11/16planmove.jpg)

  
Develop clear plans on how to respond to a digital breach or a physical beach. Whos on the response team? How will you identify the perpetrator? What if the perpetrator is on the response team? Protect all forensic efforts that track what your response involves. Document all aspects of the response. Separate all responsibilities on the response team.  
  
  
Do a post mortem. How will you respond next time?  
  
  
## Enforce separation of duties and least privilege.  

![](https://hdmpublishing.wpengine.com/wp-content/uploads/2015/11/15separate.jpg)

  
Make sure the separation of duties and the authorization of the least amount of needed privileges applies to all business processes. In particular, make sure it applies to the information technology department.

  
## Implement secure backup and recovery processes.  

![](https://hdmpublishing.wpengine.com/wp-content/uploads/2015/11/14backup.jpg)

  
Individuals who intend harm will disrupt critical servers or systems, even disrupt backups. Separate duties, again. Make sure no one has access to both raw data and the applications or forms that turn it into information. Similarly, make sure no one has both access to original copies of information and the backups. Test your systems, before disaster occurs.

  
## Implement strict password and account management policies and practices.  

![](https://hdmpublishing.wpengine.com/wp-content/uploads/2015/11/13password.jpg)

  
Make sure passwords are complex. Change often. Make sure a persons privileges are commensurate with job responsibility. Dont let privileges accumulate as person changes jobs. Add and remove privileges at each role change.

  
## Track and secure the physical environment.  

![](https://hdmpublishing.wpengine.com/wp-content/uploads/2015/11/12lock.jpg)

  
Pulling a plug or cutting a cable can be damaging. Use cages, locks, biological identification to keep intruders out. Use cameras to watch whats going on.

  
## Deactivate computer access following termination.  

![](https://hdmpublishing.wpengine.com/wp-content/uploads/2015/11/11off.jpg)

  
Monitor computer activity before the person leaves. Cut the person off immediately. Most important: Dont just terminate the individuals personal account in the companys network. Remove the person from any testing, development or group account, of any type. Take back all equipment, from laptops to tokens, before the person goes out the door. Disks and thumb drives, too.  
  
  
## Anticipate and manage negative workplace issues.  

![](https://hdmpublishing.wpengine.com/wp-content/uploads/2015/11/10negative.jpg)

  
If you see a downsizing coming in your organization, go on alert. Raise level of both digital and physical security observation.  
  
  
## Use layered defense against remote attacks.  

![](https://hdmpublishing.wpengine.com/wp-content/uploads/2015/11/9layers.jpg)

  
Decide not just what privileges a person needs when working inside the office, but what privileges are needed when working remotely. Limit remote privileges to bare minimum. Then, authenticate on multiple levels. User name. Password. Token, Biological identification (fingerprint scan or other).

  
## Log, monitor, and audit employee online actions.  

![](https://hdmpublishing.wpengine.com/wp-content/uploads/2015/11/8log.jpg)

  
Watch for attempts to access critical assets or attempts to modify same. Critical assets access attempts. Make sure alerts of such incidents are instant. Otherwise, your intellectual property could be gone before you can do anything about it. Block transmission of certain files without secondary approval.

  
Shut down critical systems automatically, if breached.  

  
## Monitor and respond to suspicious or disruptive behavior, beginning with the hiring process.  

![](https://hdmpublishing.wpengine.com/wp-content/uploads/2015/11/7behave.jpg)

  
Advise staff to watch for abnormal behavior and report it. Unusual outbursts, verbal altercations, sexual harassment. Before hiring, do background checks. Not just for criminal records. Do the facts in their resumes check out?

  
## Institute periodic security awareness training for all employees.  

![](https://hdmpublishing.wpengine.com/wp-content/uploads/2015/11/6aware.jpg)

  
Security awareness does not just apply to software engineers or system managers. Make security a top priority for anyone with any form of digital or physical access to critical assets. This includes administrative staff, janitorial staff, cafeteria staff. Log entries into buildings and systems at all times.

  
## Implement system change controls.  

![](https://hdmpublishing.wpengine.com/wp-content/uploads/2015/11/5control.jpg)

  
When things change, can you track the change? Tools are available that consistently identify any changes to your system and report them. Follow their processes. Verify requests for changes. And, of course, make sure the person who requested the change cant approve the change.

  
## Use extra caution with system administrators and technical or privileged users.  

![](https://hdmpublishing.wpengine.com/wp-content/uploads/2015/11/4caution.jpg)

  
These folks have the skill to leave some sort of malicious code in place and wait for the impact later. They can take something with them. Or modify data in a critical system, generating, say, an unauthorized payment. Segregate duties. A person who generates check cant approve a check. Or require double approval of a check. Make sure that a person who generates logs or backs up data doesnt have access to them after that is done.

  
## Clearly document and consistently enforce policies and controls.  

![](https://hdmpublishing.wpengine.com/wp-content/uploads/2015/11/3policies.jpg)

  
Set policies, at the top. Then communicate them to everyone. In particular to managers who must enforce them. Inconsistent application of policies can motivate sabotage. of senior execs. Should start at the top.  
  
  
## Consider insider threats in the software development life cycle.  

![](https://hdmpublishing.wpengine.com/wp-content/uploads/2015/11/2life.jpg)

  
Programmers can introduce malicious code into an application or system that is unknown to the organization. Employ stringent change controls. Make sure one person cant write, test and approve code. Be equally stringent during product development and maintenance.

  
## Consider threats from insiders and business partners in enterprise-wide risk assessments.  

![](https://hdmpublishing.wpengine.com/wp-content/uploads/2015/11/p16f67ljvs1bu412t71j9q7o7cvc6.jpg)

  
Most companies protect the perimeter of their operations. You must protect inside the perimeter. Consider all persons with access to your critical assets as threats: Employees. Former employees. Contractors. Former contractors. Business partners. Many leave some backdoor way for them to get back in to your systems.