ANALYSIS ...which systems are affected by compliance regulations. For example:
- Assess perimeter controls to ensure that regulated data is protected from intrusion or attack that could result in disclosure.
- Assess storage systems at the server level (access
controls/permissions, strong authentication) to ensure that if an
intruder does penetrate the network, he can't access the systems on
which the protected data is stored.
- Assess disk and file level security (encryption) to ensure that if
an intruder is able to access the server, he won't be able to read the
information in the files.
- Assess communications applications (email, instant messaging) to
ensure that protected data can't be leaked in that way. This may
require active monitoring, keyword filtering of outgoing traffic and
the like. You must also assess archiving policies to ensure the safety
of stored messages.
Ensuring scalability
If scalability is a priority a modular solution may be the answer. This
means security can be upgraded or capacity can be expanded at different
levels independently. It may mean using different vendors' products to
provide different levels of protection (such as firewall/perimeter,
storage, server, communications).
Many companies offer "turnkey" compliance solutions that integrate
with the company's existing network infrastructure. These are targeted
toward specific industries. For example, last June Qumas announced a
pre-configured compliance solution for pharmaceutical firms called
PharmaQCompliance that uses a subscription licensing model based on
number of users. SenSage offers separate out-of-the-box solutions
designed to help companies comply with SOX or HIPAA.
Another option is to find a service provider that provides security
by diverting your network traffic through their own networks. These
managed security services can take a load off your network
administrators' backs or offer protection against attack; managed
firewall and VPN services; email security, encryption; and suchlike.
Compliance Solutions can provide a full outsourced compliance
department.
Either way, a big question is whether the product or service is
actually a compliance solution developed by software professionals or a
software solution developed by compliance professionals. The ideal, of
course, comes from a collaboration of the two.
Talkback
Rule of thumb. The best solutions are often those that, 1, work well, 2, can easily be ripped out or replaced with something else, 3, comply to your environment. The worse solutions are often those that, 1, somewhat work as promised, 2, must be amputated to get rid off, 3, force your environment to comply to theirs.
31 Oct 05 21:46 ReplyYou might want to reflect such mentality into various clauses that are part of the legal contract between you and others. Along with fines and all that. Sort of: put your money where your mouth is.
As for compliancy in general. It's good to be compliant (usually cheaper, more profiting or less risky) but keep in mind that compliancy requirements do change over time. And they might impact the overall organization in ways most project leaders won't be equipped to handle or even oversee in the shorter and longer run. Or even top brass for that matter. So keep that in mind. Maybe it's best to not appoint a project team (tactical) but rather a program team (strategic) that keeps focus on the overall and longer term picture.