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...
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading December Tech Digest
Experts weigh in on the pros and cons of end-user security training.
Flash Poll
Title Partner’s Role in Perimeter Security
Title Partner’s Role in Perimeter Security
Considering how prevalent third-party attacks are, we need to ask hard questions about how partners and suppliers are safeguarding systems and data.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-5395
Published: 2014-11-21
Multiple cross-site request forgery (CSRF) vulnerabilities in Huawei HiLink E3276 and E3236 TCPU before V200R002B470D13SP00C00 and WebUI before V100R007B100D03SP01C03, E5180s-22 before 21.270.21.00.00, and E586Bs-2 before 21.322.10.00.889 allow remote attackers to hijack the authentication of users ...

CVE-2014-7137
Published: 2014-11-21
Multiple SQL injection vulnerabilities in Dolibarr ERP/CRM before 3.6.1 allow remote authenticated users to execute arbitrary SQL commands via the (1) contactid parameter in an addcontact action, (2) ligne parameter in a swapstatut action, or (3) project_ref parameter to projet/tasks/contact.php; (4...

CVE-2014-7871
Published: 2014-11-21
SQL injection vulnerability in Open-Xchange (OX) AppSuite before 7.4.2-rev36 and 7.6.x before 7.6.0-rev23 allows remote authenticated users to execute arbitrary SQL commands via a crafted jslob API call.

CVE-2014-8090
Published: 2014-11-21
The REXML parser in Ruby 1.9.x before 1.9.3 patchlevel 551, 2.0.x before 2.0.0 patchlevel 598, and 2.1.x before 2.1.5 allows remote attackers to cause a denial of service (CPU and memory consumption) a crafted XML document containing an empty string in an entity that is used in a large number of nes...

CVE-2014-8469
Published: 2014-11-21
Cross-site scripting (XSS) vulnerability in Guests/Boots in AdminCP in Moxi9 PHPFox before 4 Beta allows remote attackers to inject arbitrary web script or HTML via the User-Agent header.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Now that the holiday season is about to begin both online and in stores, will this be yet another season of nonstop gifting to cybercriminals?