Perimeter

5/8/2012
09:13 AM
50%
50%

Screw Compliance, We're Trying to Survive

In tough times, compliance efforts may seem optional

I have a healthcare-related client for which we develop custom software and database programs. It is a relatively small company, but it has a growing national presence. Nice people.

The CEO is what I consider an accidental entrepreneur. She has a great work ethic, knows her industry, and has innovative services of great value to her clients. But she never prepared to run and grow a business. As with many leaders of small and midsize businesses, knowing how to do something can be very different from knowing how to run a business that does that thing.

As my team worked on software projects, we noticed a number of clear HIPAA compliance issues unrelated to our work. I suggested to the CEO that we could provide a HIPAA assessment and action plan to address issues in a cost-effective manner. She admitted the company had issues it needed to address, but she sighed and said she had to focus all of her resources on revenue generation. She wanted to address these issues, but said they would simply have to wait.

As an entrepreneur and investor in start-up companies, I get it: starting and growing a business can be a bit sloppy at times. I even consider this to be normal. Young companies often have too few staff doing too many different jobs. Too little is documented, and deferring expenses can be critical just to survive.

So what is such a struggling or growing company to do? I believe it starts with leadership. A business culture of proper, measured risk management leads to the foundation successful businesses can build on. Compliance cannot be treated as an add-on to work. It must be a normal fact of life, addressed in each new process and with each new employee. And it must be continually supported and reinforced.

This approach does not have to be expensive. In fact, when thoughtful leaders build their companies with a focus on the future, they ingrain their work processes and work culture with the tools that inherently reduce risk and naturally build compliant systems. In the long run, this is less expensive, too.

Even businesses (or departments) without such a foundation can implement a plan that methodically builds a new foundation. But it takes discipline, focus, and leadership. That leadership ideally comes from the CEO or COO, but it can also come from thoughtful leaders within departments who add business value through culture and execution.

Times are tough for many business organizations. But I contend that by using compliance requirements as a guide, even gradually, many businesses can become stronger and more valuable without breaking the bank (or themselves).

Glenn S. Phillips, the president of Forte' Incorporated, works with business leaders who want to leverage technology and understand risks within. He 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

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
DWEBER460
50%
50%
DWEBER460,
User Rank: Apprentice
5/14/2012 | 7:21:37 PM
re: Screw Compliance, We're Trying to Survive
Your comments are spot on. Compliance definitely-begins with good leadership who encourage top of mind awareness. Also, when instituted properly, compliance should be-a small part of the day to day efforts of the organization and not a major undertaking when the epiphany occurs.- Unfortunately the latter is most often the case however. Xeneros proivides license and credential tracking services for the insurance and healthcare industries and our most successful service (not part of the original business)-is our compliance audit becuase so many companies have not taken the time to implement good license management practices.-
Google Engineering Lead on Lessons Learned From Chrome's HTTPS Push
Kelly Sheridan, Staff Editor, Dark Reading,  8/8/2018
White Hat to Black Hat: What Motivates the Switch to Cybercrime
Kelly Sheridan, Staff Editor, Dark Reading,  8/8/2018
PGA of America Struck By Ransomware
Dark Reading Staff 8/9/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-3937
PUBLISHED: 2018-08-14
An exploitable command injection vulnerability exists in the measurementBitrateExec functionality of Sony IPELA E Series Network Camera G5 firmware 1.87.00. A specially crafted GET request can cause arbitrary commands to be executed. An attacker can send an HTTP request to trigger this vulnerability...
CVE-2018-3938
PUBLISHED: 2018-08-14
An exploitable stack-based buffer overflow vulnerability exists in the 802dot1xclientcert.cgi functionality of Sony IPELA E Series Camera G5 firmware 1.87.00. A specially crafted POST can cause a stack-based buffer overflow, resulting in remote code execution. An attacker can send a malicious POST r...
CVE-2018-12537
PUBLISHED: 2018-08-14
In Eclipse Vert.x version 3.0 to 3.5.1, the HttpServer response headers and HttpClient request headers do not filter carriage return and line feed characters from the header value. This allow unfiltered values to inject a new header in the client request or server response.
CVE-2018-12539
PUBLISHED: 2018-08-14
In Eclipse OpenJ9 version 0.8, users other than the process owner may be able to use Java Attach API to connect to an Eclipse OpenJ9 or IBM JVM on the same machine and use Attach API operations, which includes the ability to execute untrusted native code. Attach API is enabled by default on Windows,...
CVE-2018-3615
PUBLISHED: 2018-08-14
Systems with microprocessors utilizing speculative execution and Intel software guard extensions (Intel SGX) may allow unauthorized disclosure of information residing in the L1 data cache from an enclave to an attacker with local user access via a side-channel analysis.