|
Grex > Coop12 > #123: Proposal to modify selection of corporate officers | |
|
| Author |
Message |
| 25 new of 118 responses total. |
jmsaul
|
|
response 77 of 118:
|
Sep 5 22:47 UTC 2002 |
<shrug> I don't think Grex has a responsibility to retain the information,
honestly.
|
scott
|
|
response 78 of 118:
|
Sep 5 23:13 UTC 2002 |
I think Grex does have a responsibility to maintain the information.
|
tod
|
|
response 79 of 118:
|
Sep 6 00:00 UTC 2002 |
Grex doesn't fall under SEC or HIPAA, so legally, it doesn't.
As a matter of preference, it might.
|
jmsaul
|
|
response 80 of 118:
|
Sep 6 02:29 UTC 2002 |
HIPAA? Huh?
Re #78: What are you basing that on, specifically?
|
krj
|
|
response 81 of 118:
|
Sep 6 04:21 UTC 2002 |
HIPAA: the Health Insurance Portability and Accountability Act,
according to a Google search.
|
mdw
|
|
response 82 of 118:
|
Sep 6 08:41 UTC 2002 |
I think in a sense both Scott & Joe are right. I would agree with Joe
that there is no legal *requirement* that we keep any identification
records whatsoever. I also agree with Scott, in that I think as a
matter of sound operating principle it's in our *interest* to keep such
material, and that we have the *right* to keep such material. This is
all a matter of balancing various risks, including the risk somebody
might commit fraud against us; the risk someone else either private or
gov't might come after us due to fraud committed by the first person;
the risk keeping such materials might give us should such materials be
stolen; the risk people might not give us money should we require
sufficient id or retain proof; etc.
A lot of these risks are pretty hard or impossible to measure. I don't
know how to measure the risk that some future treasurer might decide to
register his 6 deceased grandparents as members plus all his nieces and
nephews and swing the election in his favor. I can say with certainty
that there *are* people who would like to gain unauthenticated full
access to the internet through grex, and that giving such people access
would not be in grex's best interest. I can't say how much such people
would hurt grex, except to say that systems that give such access are
far less stable, and tend not to last as long as grex has. We've never
had law enforcement actually ask for information on an authenticated
member, so we don't know if what we keep is either sufficient, or what
exactly would happen if we did not have such information.
Unfortunately, I don't think this disproves the value of such
information -- it's like wearing seatbelts; you don't want to ever need
them, and they're not a panacea, but things could get a lot worse in an
accident without them so they're still worth wearing. We certainly do
lose members over our identification requirements. I would not say it's
a huge % - most of the people who've reacted negatively here are people
who have already indicated their unwillingness to contribute $ for
assorted other reasons. We have also had would-be members submit
fradulent identification data, and been able to detect it.
I think the current identification process evolved in 2 stages: there
was whatever was originally decided upon very early in grex's history,
when it was just a dial-up system. I'm sure that received plenty of
public scrutiny as there was less distinction between users, members,
board & staff (all of these latter groups comprised a much larger % of
the former due to the much smaller total population pool and lack of
geographical dispersion.) The internet identification process happened
later, and was part of a 2 prog effort to deal with potential network
abuse; the other part was the network blocks we put into the kernel.
This was before the modern vandal community evolved, but I don't think
we did so bad a job of identifying the risks. There was board and
membership debate about this as well; and our modern policy is I believe
a pretty direct implementation of what was then decided. There were
elements of the decision that as I recall were deliberately left up to
staff discretion; I think that included the exact forms of ID the
treasurer could accept. To this day, I can still hear Mary arguing for
that specific point, although I can't remember if she was at that time a
board member or just a member at large. Mary has always been a
consistent advocate of not overcomplicating or micromanaging any
process, for which I think she deserves proper credit and praise.
All of this is not, BTW, something that should belong in the bylaws.
Bylaws define the decision making *process*, it is not a recording *of*
the decisions. Our bylaws provide for 2 ways to make decisions (either
via the board, or via a membership vote), and those decisions could be
either short term (the board & staff will go out, buy a laptop for not
more than $2000, and configure it with *bsd or linux for the use of the
treasurer) or long-term (the treasurer will only store grex confidential
electronic data on grex provided computers, and will only transmit such
data via secure means whenever needed for lawful purposes.) Our bylaws
also permit the membership to elect board members or change the bylaws.
The board can't change the bylaws on their own, which I think is an
important and useful safegard in our bylaws.
|
mary
|
|
response 83 of 118:
|
Sep 6 12:35 UTC 2002 |
I'd be careful about promising we'd never release identification except
under court order. If a vandal did something that turned out to be very
destructive and costly, there might be a need for us to ask the police for
help. We might then volunteer what information we had.
I think we're pretty cautious and senstive about the information people
offer us. I think we're pretty clear about why we need it. Giving your
information is voluntary. Sorry, I don't see an issue here.
But carry on.
|
cross
|
|
response 84 of 118:
|
Sep 6 13:43 UTC 2002 |
Regarding #83; The issue is what data is provided, how it's handled, and
how long it's retained after a membership expires. I was kind of surprised
to hear that Mark had credit card data for members who had long since left
grex.
|
jmsaul
|
|
response 85 of 118:
|
Sep 6 13:47 UTC 2002 |
Re #81: Ken, I know what HIPAA is. I work with it for a living. I just
don't know why Todd's mentioning it here.
|
mary
|
|
response 86 of 118:
|
Sep 6 14:30 UTC 2002 |
What "data is provided" is totally up the the person sending the
identification. We accept pretty much anything for a good reasons, first,
we want to make it easy for someone to comply and two, we're going to
trust people to do the right thing unless we find out otherwise. So far
this philosophy has worked pretty well.
How this identification has been handled was to keep it so secure only one
person has access to the data, the elected treasurer. Someone has raised
concern that maybe the computer the treasurer uses should never be
connected to a modem because there is a very slim chance something could
get hacked. As slim as this chance is a number of staff and board are now
looking into making sure this can't happen.
The reason indentifying information will be kept for a long time, or at
least longer than a person might be a member, is because the window for
needing that information for identification doesn't end when someone
leaves Grex. What that person has done on the Internet isn't undone when
they leave Grex.
|
mooncat
|
|
response 87 of 118:
|
Sep 6 14:33 UTC 2002 |
I really agree with Mary at this point. (from a couple responses ago...
several slipped in while I was preparing this post-and trying to get
somework done)
As a corporation Cyberspace Communications, Inc. has a responsibility
to maintain an accurate up-to-date list of members.
Now it has been stated that because of what Grex is we don't fall under
SEC or HIPAA jurisdiction, so we don't have to maintain our records
(i.e. my company has to keep certain types of records for seven years).
Okay, so at this point it’s debatable whether or not we 'have' to
maintain the records- what's to keep that from changing? I honestly
think that it would be irresponsible of Grex NOT to keep records for
several years running.
I would not want to belittle anyone's concerns about this ID issue. To
me it seems like mountains out of molehills. If you're concerned then
you're concerned. However, what is the basis of the concern, what is
the real factor inducing so much fear in people?
Are those concerned worried about this information getting out on the
web somewhere? Are you concerned that the treasurer is being sloppy
with the protection of privacy of member info? What's really the issue
here?
If the issue is merely data handling, what’s the problem with what
we’re doing now, I mean really, all paranoia aside, what’s the real
problem?
|
aruba
|
|
response 88 of 118:
|
Sep 6 14:57 UTC 2002 |
I received an alternate ID from the one member whose credit card we still
were using. I decided that the one who had just expired is probably gone
for good, so I destroyed the piece of paper on which I had written their
numbers. So now we're not saving any credit card numbers at all.
|
jmsaul
|
|
response 89 of 118:
|
Sep 6 16:02 UTC 2002 |
I can live with that.
|
tod
|
|
response 90 of 118:
|
Sep 6 17:15 UTC 2002 |
re #85 see #87
(Yes, I was referencing data retention responsibilities. As a non-profit,
there is very little to worry about in that regards to retention schedules
other than for IRS and preferential financials that might be used down the
road for venture capital, etc)
I think its great there aren't any credit card numbers in storage.
What about the option to accept paypal as a validation method? If a
membership includes a manual(3 month), isn't it possible to require the
address for shipping if a paypal for "goods" is accepted?
|
jp2
|
|
response 91 of 118:
|
Sep 6 18:11 UTC 2002 |
This response has been erased.
|
aruba
|
|
response 92 of 118:
|
Sep 6 18:34 UTC 2002 |
Paypal validates some users and not others. When I get a payment, it either
says "this user's address has been verified" or "this user's address is
unverified".
|
tod
|
|
response 93 of 118:
|
Sep 6 20:00 UTC 2002 |
Is it possible you could waive the ID requirement on the stipulation that they
are a paypal user with a verified address?
|
mary
|
|
response 94 of 118:
|
Sep 6 20:04 UTC 2002 |
That puts the responsibility on PayPal to keep the information
for as long as we need it. I'd say no, that if we need the info,
then we should collect it and be responsible for safeguarding it.
Again, nobody has to give us any information they are uncomfortable
having us hold. It's that easy.
|
tod
|
|
response 95 of 118:
|
Sep 6 20:12 UTC 2002 |
What is the expected data retention period? The length of the membership?
What will be the field of data expected from each member?
|
cross
|
|
response 96 of 118:
|
Sep 6 20:20 UTC 2002 |
Regarding the idea that grex needs to maintain information after a user
has let his or her membership expire; why? They're gone; what they did on
grex is history, and if you haven't heard about it by the time they leave,
you're probably never going to hear about it. What right does Cyberspace
Communications, Inc. have to retain that data beyond a reasonable grace
period, say 6 months? We were talking about people who's data was still
around after a couple of years, if I understood Mark correctly.
The issue here is identity theft, more than anything. Some folks are
trying to raise questions about grex's propriety, but I think that's a
non-issue. It's clear that grex isn't interested in ``tracking'' people
so much as being able to tell a cop or fed, ``Joe Smith is a member;
here's a copy of his driver's license that he sent us.'' However, it's
a fact of probability theory that the longer grex retains that data, the
greater the chance that someone might be able to steal it. It's another
fact that grex might be retaining more data than it needs; I don't see how
you need anything other than a name, address, and maybe a phone number.
A sufficient argument that more is required hasn't been made, either.
Unfortunately, identity theft is real, and a serious problem. Ask anyone
who's ever had their social security card stolen.
I don't think that anyone is arguing gthat grex doesn't need to know
who its users *are*, but what's in question is the manner in which grex
finds that out, and then what they do with it, and when they get rid
of it. Six months I can see. But two years? Come on.
ps- it's been stated that only one person has access to the ID data: the
treasurer. However, that position turns over periodically, presumably
the data migrates along with the position, so it's not strictly true
that only one person can see it. Rather, only one position within the
corporation is authorized to see it.
|
mary
|
|
response 97 of 118:
|
Sep 6 21:05 UTC 2002 |
You are right, we don't need anything more than a name, address and maybe
a phone number. It's all voluntary. Nobody is forced to submit ID. You
could send in a library card photocopy and be granted membership
privileges. We'll keep whatever information you give us on file for
probably longer than you'll be living at the address, mostly because the
treasurer's job is hard enough without having to go back and find out who
left when and keep track of when their ID should be destroyed.
I'd come up with a number but I'm sure you won't like it.
I'm far more worried about the treasurer's job getting over-the-top
complex than with the information Mark holds being lost or abused.
|
tod
|
|
response 98 of 118:
|
Sep 6 21:18 UTC 2002 |
I agree, Mark's job should be simple and painless with little effort as
possible. It's also the reason I'm posing questions..not to make any red
herrings, but just to see where the buck stops. ;)
|
other
|
|
response 99 of 118:
|
Sep 7 03:11 UTC 2002 |
I think that the fear that member validation data stored by Grex poses a
threat is vastly out of proportion to the reality of that threat. Our
data is not being handled by a profit-driven bureaucracy or large scale
data management systems with security-ignorant or no oversight at all.
What with the simple steps being taken to protect the electronic records
maintained by the treasurer, the risk is tremendously overshadowed by the
value to Grex in assuring the integrity of its membership and disouraging
abuse of its access and resources.
|
jp2
|
|
response 100 of 118:
|
Sep 7 16:56 UTC 2002 |
This response has been erased.
|
aruba
|
|
response 101 of 118:
|
Sep 7 17:28 UTC 2002 |
Yup.
|