homicide-erumpent
Notebook
May 3rd, 2007 by Double Tap

I’m not done yet.

There may yet be a way to conform to the spirit of this new Army Operational Security regulation - without ending my blogging, and without have to get every one of my Internet utterances pre-screened.

I know my boss isn’t going to want to read every single blog post I make, nor will I want to read every post my own soldiers make on their own blogs or MySpace accounts (I know of three already, and that in a 22-soldier unit).

As a commander, I believe I am staying within Army regulation by setting policy outlining what they can or can’t say, and then have their blogs reviewed every once in awhile by myself or someone I designate. At least that’s what the guy who wrote this new regulation has said. As for this blog, I’m hoping my boss will let me self-police, or, at least go along with a similar policy as I’ve just described.

In the meantime, dear readers, my posts will be few and far between. Hopefully, I can get this worked out within a week or so. *fingers crossed*

UPDATE - The Army must be feeling the heat, because they released a statement today that backs down from the original requirements of the new regulation. Unfortunately, I don’t have the original link, but it’s been posted in numerous locations on the internet. Here’s what I’ve got:

• In no way will every blog post/update a Soldier makes on his or her blog need to be monitored or first approved by an immediate supervisor and Operations Security (OPSEC) officer. After receiving guidance and awareness training from the appointed OPSEC officer, that Soldier blogger is entrusted to practice OPSEC when posting in a public forum.

• Army Regulation 350-1, “Operations Security,” was updated April 17, 2007 – but the wording and policies on blogging remain the same from the July 2005 guidance first put out by the U.S. Army in Iraq for battlefield blogging. Since not every post/update in a public forum can be monitored, this regulation places trust in the Soldier, Civilian Employee, Family Member and contractor that they will use proper judgment to ensure OPSEC.

o Much of the information contained in the 2007 version of AR 530-1 already was included in the 2005 version of AR 530-1. For example, Soldiers have been required since 2005 to report to their immediate supervisor and OPSEC officer about their wishes to publish military-related content in public forums.

o Army Regulation 530-1 simply lays out measures to help ensure operations security issues are not published in public forums (i.e., blogs) by Army personnel.

• Soldiers do not have to seek permission from a supervisor to send personal E-mails. Personal E-mails are considered private communication. However, AR 530-1 does mention if someone later posts an E-mail in a public forum containing information sensitive to OPSEC considerations, an issue may then arise.