New Florida Wing Commnader

[Cecil DP]

I just received the following announcement from the Florida WingE-mail list.

Lt Col Christian F. Moersch III, CAPID 231449 has been chosen as the Florida Wing Commander effective 02 February 2008.  The Change of Command Ceremony will be conducted at the Florida Wing Conference in Orlando.

[flyguy06]

Just curious. Why did you feel the need to post his CAPID? Isn't that an OPSEC violation? Couldn't you have just posted his name? And even then it isnt official yet. Do you want another IAWG thing to happen. You guys kill me with wanting to jump the gun before things come down official channels. That something the meda likes to do.
Sorry to vent. I just think some things need to be left internal until officially posted by official people through officaial channels and not a web Blog

[Tim Medeiros]

One would think that with it being signed by the region commander is official enough (now I realize that information wasn't relayed in the message on this thread, however that information I would consider an OPSEC violation as it was signed with the region commanders name and contact information which looks much like a business card which is what most of the SER staff use to sign their emails these days), that message is copied word for word from the email announcement sent over the wing general email list, squadron command list, group command list, wing command list and wing staff list.  It was not in a web-log (commonly known as a blog), it was through the primary method of mass communication available to the entire wing.  His CAPID in of itself does not contain any personal information nor can it be used by the standard lay-person to gather information, unless that person has access to the NHQ database.  Even then, for those not assigned to FL001, SER001 or NHQ999, about all you could pull up is what is in the National Reports module of the My Operations Qualifications/National Reports application under CAP Utilities which does not contain the kind of information one would consider personal.

[JohnKachenmeister]

That's why we went back to a CAP ID number instead of using the SSN.  It doesn't violate OPSEC as far as I know.

[SSgt Rudin]

Actually even posting some one's SS# wouldn't be an OPSEC violation it would be a Privacy Act Violation.

directly from CAP OPSEC training:
OPSEC deals primarily with protecting sensitive but unclassified information that can serve as indicators about our mission, operations and capabilities

Just lets you know how many people just click their way threw the training.

[BillB]

Personally I think Col. Rushing made an excellent choice for Florida Wing Commander. LCol Moresch has Group Command experience, and was Wing Chief of Staff for Operations.

[flyguy06]

Ok, I am just saying I dont wanna get any mess started like the other so called appointed Wing CC. I didnt know about it being signed. Nobody mentioned that. I was just replying to the info that was presented to me.

I met the COL at the SERWE. He is a good guy. He is an airline pilot so thats good enough for me.

[RAZOR]

 "i just think some things need to be left internal until officially posted by official people through officaial channels and not a web Blog."


This announcment was signed by the SER Commander, COl Rushing, who by the way will be removed himself, shortly.  Just wait for it, it is coming,

[lordmonar]

Redacted as someone already beat me to the punch.

[mikeylikey]

This announcment was signed by the SER Commander, COl Rushing, who by the way will be removed himself, shortly.  Just wait for it, it is coming,

IBM used to follow a practice that if your boss got fired or removed, then you also get re-evaluated.  EXAMPLE:  Jim Bob gets promoted by Timmy John, Timmy John gets fired 1 week later.  IBM bigwigs visit Jim Bob to see if he was truely the right person for the job.

I think CAP should follow suit.  If the newly appointed Wing King has served less than a year and his Region Commander is removed (for some specific reason) than the Wing King should be scrutinized by the new Region Commander. 

[flyguy06]

"i just think some things need to be left internal until officially posted by official people through officaial channels and not a web Blog."


This announcment was signed by the SER Commander, COl Rushing, who by the way will be removed himself, shortly.  Just wait for it, it is coming,

LOL. I met COL Rushing. He's a cool guy

[ADCAPer]

OPSEC deals primarily with protecting sensitive but unclassified information that can serve as indicators about our mission, operations and capabilities

Just lets you know how many people just click their way threw the training.

Not only can you just click through the training, once your done you have no guidance on what type of information you're supposed to be protecting.

Was this an OPSEC violation?  Absolutely. Will anything be done about it, absolutely not.

The problem is that CAP rushed out another program without fully developing it. Anyone who's ever dealt with OPSEC knows that you have to have the Critical Information List established to manage the program. Without that list no one knows what information they are actually supposed to protect.

At least this time the violation wasn't as bad as the one that was committed by the Georgia Wing Director of Operations the day after Christmas. He sent an e-mail out to every member of the GAWG naming the pilots that were no longer allowed to fly for some reason.  As if that wasn't enough, he also included their CAPID and Units Number.

[SamFranklin]

Is it just me, or is CAP-Talk dysfunctional? Even mundane announcements like "Florida gets a new commander" quickly sink into the weeds of OPSEC one-up-manship or yet another uniform thread.

Congratulations, Colonel Moersch. Florida is a big wing. Your new job will be a challenge. Best wishes for a fun and rewarding term.

(See how easy that was.)

[RiverAux]

He sent an e-mail out to every member of the GAWG naming the pilots that were no longer allowed to fly for some reason.  As if that wasn't enough, he also included their CAPID and Units Number.

How is that a "violation"?  It was a communication within the CAP community of non-sensitive information.  Every member of a unit has access to that information on their unit if they log into eservices. 

[ADCAPer]

How is that a "violation"?  It was a communication within the CAP community of non-sensitive information.  Every member of a unit has access to that information on their unit if they log into eservices. 

The purpose of OPSEC is supposed to be to control the release of non-sensitive information, which is generally unclassified, but which concerns your intentions and/or your capabilities. You do this by identifying, controlling, and protecting the indicators associated with your planning or operations.

The e-mail that was sent out by the GAWG/DO went to the ALL GAWG USERS group, and there is no way to ensure that the information stayed within the CAP community. For example, there are Cadets who use their parents e-mail accounts, and their parents are not bound by a NDA. On top of that, these pilots were not all from the same unit, they were from several units around the Wing.

Now, does that information mean anything by itself? Not necessarily, but that's the point of OPSEC, because there is no way to tell who is paying attention to it, or what else they have managed to pick up. I will bet that there's at least one group of people out there who would be interested in knowing the status of our pilots, it might make their life a little easier if they know they aren't being watched for a while because CAP stood down a large number of pilots.

The point is that this information should not have been sent to all users like this, it was an obvious violation. Information concerning our capabilities should be limited to the people who have a need to know, not passed out to everyone including the lowest ranking Cadet on an e-mail list.

[Eclipse]

OK, OPSEC aside, what I want to know is...

...what the heck is a Commnader?

[SarDragon]

Oh, as if you've got a lot of room to talk, Bob.   

[lordmonar]

OPSEC is designed to protect unclassified sensitive information that may help and adversary gain insight into OPERATIONS.

Posting someones CAPID is not OPSEC.
Posting the list of those pilots no longer allowed to fly MAYBE and OPSEC issue assuming you were able to correlate that list to wing operational readiness levels.


Again...OPSEC is to protect OPERATIONS.....and that is all.

[afgeo4]

I concur. This info isn't operationally sensitive, so no OPSEC violation. However, some courtesies should be given to CAP members. Not publishing and distributing their CAP numbers I would think should be one of those courtesies. The CAPID number shouldn't have been sent to FLWG members in the first place. If it was, there should have been a "For your eyes only" reminder so the info does not get spread.

The info was e-mailed to the public and then it was spread because no warnings were posted. As such, the member in question here didn't do anything wrong.

[dwb]

...what the heck is a Commnader?

Now that's pretty durn funny.