tech blog header

Free Whitepaper

Follow Us

Your email:

Blog Topics

Cloud Computing, Exchange 2013

Current Articles | RSS Feed RSS Feed

Failure to Comply: Why Breaches Occur due to Non-Compliance

 

frustration non-complianceIf your organization falls under any of the types of government compliance, it’s crucial that employees follow the proper protocol to be compliant with IT security policies. Executives designate the process of ensuring that compliance standards are followed to IT leaders generally. The IT department determines where there are compliance gaps and applies the necessary measures and policies. However, for these measures to work efficiently, everyone in the organization must follow them. Unfortunately, employee non-compliance with policies can happen and when it does, security breaches are possible.

Here are the top five causes of breaches due to non-compliance: 

  1. Employee exits: Employees often have access to sensitive information within an organization. When an employee leaves an organization, either voluntarily or otherwise, damage to confidential information can occur. Therefore, even when a trusted employee leaves, the same protocol must be followed – immediate removal of access to all areas of data, including networks, email, and company intranet. Though it may sound extreme, it’s better to be safe than sorry when critical information is at stake.
  2. Unintentional misuse of company data: While everyone wants to be helpful to both current clients and potential ones, sometimes that eagerness can have negative consequences. For example, providing confidential information to potential clients, vendors, or simply answering general inquiries can mean that sensitive data could be exposed. To ensure that sensitive data remains private, each department should regularly review security policies with its staff and encourage employees to ask when unsure.
  3. External attacks: Virus infiltration, spam, and other external attacks can easily threaten any area of a business and affect business continuity or access to data. Keeping a checklist of the tasks that need to be done to prevent against attacks, and also actions to take in the case of a successful attack, can help prevent or minimize intrusions.
  4. Insecure networks: Hackers seem to enjoy finding loopholes in networks and exploiting them in order to hinder a company's ability to function. In addition to attempting to prevent external attacks, an organization should constantly monitor its networks. Using server monitoring, an organization can understand the most likely areas for a breach to occur and proactively take measures to prevent one from happening.
  5. Phishing (Social Engineering): Brute force hacking isn’t the only way that hackers can access to networks. A special type of attack, called phishing, occurs when hackers send legitimate looking "emails" from someone in the network to employees, hoping that they will open them. This form of social engineering can allow access to a business's entire network through one click of an employee. By implementing specific email format standards, applying backend rules, and using virus scans, the number of phishing attacks that make it to the email stage can be dramatically reduced.


IT policies are only as good as the employees who follow them. Not following security policies can result in a severe loss of productivity, damage to an organization’s brand and reputation, and possible financial and legal repercussions. Aside from this accountability, implementing strong and customized solutions is paramount to the successful compliance and security of a business.

iCorps is a leader in IT and government compliance consulting, helping satisfy the unique IT needs of businesses in Boston, Philadelphia and New York. Don't let a breach due to non-compliance disrupt your business. Contact iCorps today for a free consultation, then read our whitepaper on data backup and disaster recovery.

6ca9dc62-e5a3-40d8-8b9e-6727c78a4e7f


Comments

Currently, there are no comments. Be the first to post one!
Post Comment
Name
 *
Email
 *
Website (optional)
Comment
 *

Allowed tags: <a> link, <b> bold, <i> italics