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 Tech Digest, Dec. 19, 2014
Software-defined networking can be a net plus for security. The key: Work with the network team to implement gradually, test as you go, and take the opportunity to overhaul your security strategy.
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-8142
Published: 2014-12-20
Use-after-free vulnerability in the process_nested_data function in ext/standard/var_unserializer.re in PHP before 5.4.36, 5.5.x before 5.5.20, and 5.6.x before 5.6.4 allows remote attackers to execute arbitrary code via a crafted unserialize call that leverages improper handling of duplicate keys w...

CVE-2013-4440
Published: 2014-12-19
Password Generator (aka Pwgen) before 2.07 generates weak non-tty passwords, which makes it easier for context-dependent attackers to guess the password via a brute-force attack.

CVE-2013-4442
Published: 2014-12-19
Password Generator (aka Pwgen) before 2.07 uses weak pseudo generated numbers when /dev/urandom is unavailable, which makes it easier for context-dependent attackers to guess the numbers.

CVE-2013-7401
Published: 2014-12-19
The parse_request function in request.c in c-icap 0.2.x allows remote attackers to cause a denial of service (crash) via a URI without a " " or "?" character in an ICAP request, as demonstrated by use of the OPTIONS method.

CVE-2014-2026
Published: 2014-12-19
Cross-site scripting (XSS) vulnerability in the search functionality in United Planet Intrexx Professional before 5.2 Online Update 0905 and 6.x before 6.0 Online Update 10 allows remote attackers to inject arbitrary web script or HTML via the request parameter.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Join us Wednesday, Dec. 17 at 1 p.m. Eastern Time to hear what employers are really looking for in a chief information security officer -- it may not be what you think.