Perimeter

6/1/2012
09:21 AM
50%
50%

Systems Are Not Compliant; Organizations Are Compliant

IT cannot make your organization compliant

Computer systems do not operate in a vacuum. They are neither isolated from people, disconnected from other computers, nor are they sealed off from the outside world. Rather, computer systems are tools your staff uses to run your organization. Companies are operated by people using their tools to perform tasks, create products, and provide services.

Car manufacturers and auto service departments cannot make you a good driver. Buying a high-tech kitchen will not make you a great chef, and buying a smart phone does not make you smarter. The car, oven, and phone are only tools. How well, or how poorly, you use these tools is determined by your willingness and attitude. It’s the same with the technology tools you use in your business.

“Compliance” is defined by the laws, regulations, and rules an organization meets, so compliance is more about how things are done, than which tools are used. Of course, compliance requires the appropriate technology tools, but none of them alone can make your company compliant.

When we discuss security and compliance assessments with potential new clients, usually the first thing they do is introduce us to the person in charge of IT. The problem is, the head of IT is rarely in charge of the business processes within the organization or the management of non-technical staff. These aspects of the business, however, are crucial to compliant operations.

IT must provide secure, usable systems. They must fine tune these tools to help an organization maintain appropriate privacy, risk management, accountability, and protection. The tools must be accessible in every way necessary for effective business operations.

Unfortunately, too many (including some in IT leadership) believe a common myth: that making the tools secure creates sufficient security and compliance. This myth is sometimes a result of misunderstanding compliance, and other times it is merely a convenient excuse for handing off work by management. To be candid, many embrace this myth to avoid dealing with the real issues. “Make our systems secure,” is an easy order for a busy leader to make, but extremely often, it is a flawed decision.

System security alone will never bring a company into compliance with applicable requirements. Employees must also operate in compliant ways, must follow secure processes, and have the discipline to avoid unsecure and non-compliant shortcuts.

Technical system security alone does not make an organization compliant with any law, regulation, or rules. It is only one element in an organization’s successful compliance program.

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
MROBINSON000
50%
50%
MROBINSON000,
User Rank: Apprentice
6/12/2012 | 12:15:32 PM
re: Systems Are Not Compliant; Organizations Are Compliant
Indeed, many IT people believe
that making the tools secure creates sufficient security and compliance. Security
training has to extend beyond a statement of policies to a new hire and the
annual training. That means everyone has to have a role, from management to
admin staff. You can find more details on this topic here: http://blog.securityinnovation...
Devastating Cyberattack on Email Provider Destroys 18 Years of Data
Jai Vijayan, Freelance writer,  2/12/2019
Up to 100,000 Reported Affected in Landmark White Data Breach
Kelly Sheridan, Staff Editor, Dark Reading,  2/12/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-8354
PUBLISHED: 2019-02-15
An issue was discovered in SoX 14.4.2. lsx_make_lpf in effect_i_dsp.c has an integer overflow on the result of multiplication fed into malloc. When the buffer is allocated, it is smaller than expected, leading to a heap-based buffer overflow.
CVE-2019-8355
PUBLISHED: 2019-02-15
An issue was discovered in SoX 14.4.2. In xmalloc.h, there is an integer overflow on the result of multiplication fed into the lsx_valloc macro that wraps malloc. When the buffer is allocated, it is smaller than expected, leading to a heap-based buffer overflow in channels_start in remix.c.
CVE-2019-8356
PUBLISHED: 2019-02-15
An issue was discovered in SoX 14.4.2. One of the arguments to bitrv2 in fft4g.c is not guarded, such that it can lead to write access outside of the statically declared array, aka a stack-based buffer overflow.
CVE-2019-8357
PUBLISHED: 2019-02-15
An issue was discovered in SoX 14.4.2. lsx_make_lpf in effect_i_dsp.c allows a NULL pointer dereference.
CVE-2013-2516
PUBLISHED: 2019-02-15
Vulnerability in FileUtils v0.7, Ruby Gem Fileutils <= v0.7 Command Injection vulnerability in user supplied url variable that is passed to the shell.