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.

Perimeter

12/11/2012
02:35 PM
50%
50%

Hauling That 50-Pound Sack Of Compliance

Done wrong, your compliance efforts can needlessly weigh your team down

A business owner recently told me she was aware her business had done little toward necessary HIPAA compliance. She had reasons, of course. The economy was making business difficult, they were short on cash for extra projects, their profit margins were too small, and the staff was spread too thin to take on any new tasks or projects.

I understand her challenges. I've faced the similar issues as a business owner for more than 20 years. I also learned, the hard way I might add, that as your business grows, doing more of what you've been doing all along doesn't always support business growth.

What do I mean by that? I mean that healthy business growth is rarely doing the same things in the same way, only in volume. Businesses must change how they approach the different challenges that different stages of growth demand. As my wife, Doris, an entrepreneur in her own right, once said, "What works for one does not work for two. What works for two does not work for three." You can apply this to just about any task, process, number of locations, or number of employees.

Let's again consider the noncompliant business owner. Because she is comfortable with the idea that her company is small, she's trying to operate it as if it were still small, even though the problems she faces are far beyond small-shop challenges. She will never have the resources, in cash or staff, to address her compliance issues until she changes her business model to reflect its new, larger scale. And that assumes she survives long enough to evolve into that new business model.

Until this business owner transitions her business processes, requiring compliance would be like asking her employees to carry around a 50-pound sack. Even if the 50-pound sack has important contents, the extra weight and unwieldiness of it all will cause her business to slow further, maybe to stall -- a stall that may not be survivable.

So what is she, and others like her, to do about the seemingly weighty demands of compliance and security? The exact same thing any organization of any size should do: Build processes and operations to match the real business needs. Don't add compliance and security later; incorporate them from the start. To wait until later means you didn't plan for the extra weight these requirements place on your business.

If your organization cannot manage the cost of time, people, or money to incorporated compliance and security, then you either have not planned it correctly, or you do not have an economically viable business model. In the former case, develop plans that work. If you need help, many others have done this successfully, and hiring them can be less expensive in the long run than failing or risking noncompliance.

In the case you are simply not economically viable, you have a hard decision to make. You can find a new way, stop now before you suffer more, or die a slow business death that wastes more money and days of your life.

Glenn S. Phillips would like to lose about ten pounds. He is the president of Forte' Incorporated where he works with business leaders who want to leverage technology and understand the often hidden risks within. Glenn is the author of the book Nerd-to-English and you can find him on twitter at @NerdToEnglish. Glenn works with business leaders who want to leverage technology and understand the often hidden risks awaiting them. The Founder and Sr. Consultant of Forte' Incorporated, Glenn and his team work with business leaders to support growth, increase profits, and address ... View Full Bio

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/9/2020
Omdia Research Launches Page on Dark Reading
Tim Wilson, Editor in Chief, Dark Reading 7/9/2020
Mobile App Fraud Jumped in Q1 as Attackers Pivot from Browsers
Jai Vijayan, Contributing Writer,  7/10/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
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 Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-14174
PUBLISHED: 2020-07-13
Affected versions of Atlassian Jira Server and Data Center allow remote attackers to view titles of a private project via an Insecure Direct Object References (IDOR) vulnerability in the Administration Permission Helper. The affected versions are before version 7.13.6, from version 8.0.0 before 8.5....
CVE-2019-20901
PUBLISHED: 2020-07-13
The login.jsp resource in Jira before version 8.5.2, and from version 8.6.0 before version 8.6.1 allows remote attackers to redirect users to a different website which they may use as part of performing a phishing attack via an open redirect in the os_destination parameter.
CVE-2019-20898
PUBLISHED: 2020-07-13
Affected versions of Atlassian Jira Server and Data Center allow remote attackers to access sensitive information without being authenticated in the Global permissions screen. The affected versions are before version 8.8.0.
CVE-2019-20899
PUBLISHED: 2020-07-13
The Gadget API in Atlassian Jira Server and Data Center in affected versions allows remote attackers to make Jira unresponsive via repeated requests to a certain endpoint in the Gadget API. The affected versions are before version 8.5.4, and from version 8.6.0 before 8.6.1.
CVE-2019-20900
PUBLISHED: 2020-07-13
Affected versions of Atlassian Jira Server and Data Center allow remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability in the Add Field module. The affected versions are before version 8.7.0.