[23505] in APO-L

home help back first fref pref prev next nref lref last post

Re: [APO-L] Question of posting National Board Policy Manual onli ne

daemon@ATHENA.MIT.EDU (Finder, Randolph J Mr NGB-ARNG)
Tue Feb 4 10:02:11 2003

Date:         Tue, 4 Feb 2003 10:05:34 -0500
Reply-To: "Finder, Randolph J Mr NGB-ARNG" <Randolph.Finder@ngb.army.mil>
From: "Finder, Randolph J Mr NGB-ARNG" <Randolph.Finder@ngb.army.mil>
To: APO-L@LISTSERV.IUPUI.EDU

>
> > Not to put a damper on this, but .htaccess is not a secure solution,
> > just like Telnet or FTP aren't secure.
>
> No solution is completely secure, it's the nature of
> computers. As a General
> at Fort Huachuca once stated to me a number of years ago the
> ONLY way to
> secure a computer is to cut all cables coming out of the CPU;
> encase it in
> cement; and sit a private with a gun on it. What we have
> these days are
> solutions that make a break in less probable, but don't
> delude yourself that
> "you're secure". Your biggest point of failure in any
> computer system isn't
> the technology, but the people using it. If security is too
> tight people will
> intentionally circumvent it.

Um. You don't have to encase it in cement, putting it in a concrete room
will do. Also, because of the way that promotions work in the military
generally the first promotion to Private 2 (E-2 for army) will occur before
the Soldier would have his Top Secret clearance. General clearances (I need
the people in my unit cleared so we can be assigned to guard this) go slower
than specifics of (we need John Michaelson cleared so that he can use his
specialized skills on Task X). The guards in the Secure Vault where I work
are generally Specialist (E-4) and the Sergeants up to E-7.

People intentionally circumventing the security generally doesn't happen
when the security gets above a certain level unless they would have done so
anyway for the purposes of spying.

And besides, if the Soldier is sitting on the computer, it cuts down on his
field of fire.


However (bringing it back on to APO) little of this is applicable to Alpha
Phi Omega.

I'm going to split our desire for security into three pieces:
1)Ritual based (ceremonies and such)
2)Corporate based (Board Policy Manual , how much Judy Mitchell makes ,
Marilyn Tischinski's annual review, etc.)
3)Contact based (phone numbers and address for the board, chapters and
extension efforts)

1)Ritual Based. Alpha Phi omega is nowhere near at the level as other Greek
Letter Organizations and Adult Fraternal Societies. Some of the Social
Fraternities print their ritual books themselves and deliver them by hand
only... The fact that this fraternity hired a National Executive Director
who was not a brother and as such shouldn't have seen the ritual (until a
chapter honorary/advisored him, which they now have) indicates that we have
some level of give and take on the subject

2)Corporate based. The comparison should not be with IBM or Coca-Cola, it
needs to be with the United Way or BSA or Circle K. I don't know if
publishing how much Judy Mitchell makes would put the fraternity at risk of
legal action, but I wouldn't want to try it. OTOH, the fact that The NED and
the DCS are hired directly by the board and the others are hired by the NED
(Not sure on Development Director) is something that does not have the same
need for privacy.

3)Contact based. The national fraternity goes out of its way to make sure
that no one can just grab the mailing address of all of the active chapters
to make sure they aren't targetted for mailing, under similar reasoning the
Extension Status Report has a limited audience. However, This information I
could see on the national site in a passworded area. There are some Social
Greek Letter Organizations that do that.



YiLFS

Randolph Finder
Army National Guard Readiness Center

home help back first fref pref prev next nref lref last post