| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Stop wasting time looking for files and revisions. Connect your Gmail, DriveDropbox, and Slack accounts and in less than 2 minutes, Dokkio will automatically organize all your file attachments. Learn more and claim your free account.

View
 

Web-Posting Policy for MORS

Page history last edited by leonard.sadauskas.ctr@... 11 years, 3 months ago

MORS wants to use the internet, however, we need to ensure that the participation of our members does not adversely affect them in their employment.  Any member participating in a community of practice should be aware of the policy.  The DoD policy for posting on websites are sumarized below. 

 

MORS legal counsel has provided the following  Wiki Policy.doc

 

The DoD policy for posting on the web are available at  http://www.defenselink.mil/webmasters/policy/dod_web_policy_12071998_with_amendments_and_corrections.html#part1.  In particular, Paragraph 5.5.2 states DoD Components shall "Ensure all information placed on publicly accessible Web sites is properly reviewed for security, levels of sensitivity and other concerns before it is released. Detailed requirements for clearance of information for public release are located in DoD Directive 5230.9 and DOD Instruction 5230.29 (references (h) and (o)) and Part II of this document." 

 

DoD Directive 5230.9 is available at http://stinet.dtic.mil/stinfo/data/DoDD_52309.pdf.  It states "DoD personnel, while acting in a private capacity and not in connection with their official duties, have the right to prepare information for public release through non-DoD forums or media."  In this sense, planning and organizing MORS events may be considered acting in a private capabicity. 

 

The DoD Instruction 5230.29 is available at http://www.dtic.mil/whs/directives/corres/pdf/523029p.pdf.  It states, "6.2.7. Information intended for placement on electronic bulletin boards accessible through the INTERNET, or other publicly accessible computer servers, requires review and clearance for public release if, it meets the requirements of subsection 6.1.

6.1.1. Originates or is proposed for release in the Washington, DC area;

6.1.2. Is or has the potential to become an item of national or international

interest;

6.1.3. Affects national security policy or foreign relations;

6.1.4. Concerns a subject of potential controversy among the DoD

Components or with other Federal Agencies;

6.1.5. Is presented by a DoD employee, who by virtue of rank, position, or expertise would be considered an official DoD spokesperson;

6.1.6. Contains technical data, including data developed under contract or independently developed and controlled by the ITAR (reference (f)) that may be militarily critical and subject to limited distribution, but on which a distribution determination has not been made; or,

6.1.7. Bears on any of the following subjects:

6.1.7.1. New weapons or weapons systems, or significant modifications or improvements to existing weapons or weapons systems, equipment, or techniques.

6.1.7.2. Military operations, significant exercises, and operations security.

6.1.7.3. National Command Authorities; command, control, communications, computers, and intelligence; information operations and computer

security.

6.1.7.4. Military activities or application in space; nuclear weapons, including nuclear weapons effects research; chemical warfare and defensive biological

warfare; and arms control treaty implementation.

6.1.7.5. Any other contemporary topic that is designated by the Head of a DoD Component.6.1.5. Is presented by a DoD employee, who by virtue of rank, position, or expertise would be considered an official DoD spokesperson;"

DOD Information Security/Website Alert,  6 Aug 2006, is available at http://www.defenselink.mil/webmasters/policy/infosec20060806.html.  It states

"5. WHERE COLLABORATION WITH NON,-DOD PERSONNEL REGARDING UNCLASSIFIED OFFICIAL INFORMATION WILL BENEFIT THE DEPARTMENT, OFFICIAL *CHAT ROOMS* OR COLLABORATION SITES SHALL BE ESTABLISHED AND REGULATED THROUGH THE USE OF POSITIVE TECHNICAL CONTROLS SUCH AS PROXY SERVICES AND SCREENED SUBNETS IN ACCORDANCE WITH DODI 8500.2, *INFORMATION ASSURANCE (IA) IMPLEMENTATION* AND APPROVED BY THE DESIGNATED APPROVING AUTHORITY (DAA). COLLABORATION CAN TAKE PLACE AMONG DOD PERSONNEL OR AMONG DOD PERSONNEL AND AUTHORIZED NON-DOD PERSONNEL (INCLUDING PUBLIC MEMBERS OF THE SCIENTIFIC COMMUNITY) WITHIN SECURITY AND INFORMATION DISSEMINATION GUIDELINES (E.G., EXPORT CONTROL RESTRICTIONS). NON-DOD PERSONNEL SHALL BE AUTHORIZED ACCESS TO THE *CHAT ROOM* OR COLLABORATION SITE ON A BY-NAME BASIS BY THE DOD SPONSOR IN ACCORDANCE WITH PROCEDURES ESTABLISHED BY THE DAA. USER AUTHENTICATION SHALL BE REQUIRED FOR SYSTEM ACCESS."


The necessity to have postings to a wiki approved by my command is a severe impediment to my participation. For me to obtain approval for the public release of a document, the document needs to be reviewed by:

1. Branch head

2. Division head

3. Department head

4. Publications

5. Security

6. Chief Scientist

7. Export control

8. Technical Director

This Industrial Age policy is not designed for the quick turn-around associated with wikis. It takes a week if you hand carry the document. If you do not expedite it, approval takes closer to two weeks.

Ted Bennett

Right now, we have two options for websites that do not require DoD employees obtaining permission to post, however both significantly restrict participation. The first option is DoD provided sites, particularly either Defense Knowledge Online or Air Force Knowledge Now, which provide forums that require either a Common Access Card (CAC) or being sponsored as a guest. The second option is to use SPIRNET sites. Joint Data Support provides both secret wikis and discussion forums for the analytic community.  My suggestion is we try either or both of these options for Communities of Practice (COPs).  I do not recommend the wikis that we are using for MORSNet. 

Very Respectfully,

Mark Gallagher

 

I would strongly urge we do not consider these two options because they would exclude too many people from participation in this COP. These fora are difficult to access for people who are not in the DoD organizations.  As someone in a DOE organizationan I have to be sponsored by someone in DOD.  This would hold also for our new DHS members.  For those who do not have.any DoD ties, like the social science community we want to engage, this could be an impossible hurdle.

John

John R. Hummel

Argonne National Laboratory

 

Is the choice between an impossible hurdle for DoD employees versus non-DoD employees?  Can anyone propose an option that works for both?

Very Respectfully,

Mark Gallagher


Some years ago I participated in the start up of a DoD sponsored CoP.  We went through the same series of narrow interpretations of the regulations that I see here.  The bottom line is that we are able to accomodate both the intent of the regs and offer the benefits of a accessable web site to the community.  See the acquisition community connection site at https://acc.dau.mil

Sincerely,

Len Sadauskas

 

Insert comments and suggestions on how we can proceed with MORSNet and Communities of Practice below:

 

 

Comments (1)

Ted Bennett said

at 3:27 pm on Aug 25, 2008


The necessity to have postings to a wiki approved by my command is a severe impediment to my participation. For me to obtain approval for the public release of a document, the document needs to be reviewed by:

1. Branch head
2. Division head
3. Department head
4. Publications
5. Security
6. Chief Scientist
7. Export control
8. Technical Director

This Industrial Age policy is not designed for the quick turn-around associated with wikis. It takes a week if you hand carry the document. If you do not expedite it, approval takes closer to two weeks.

Ted

You don't have permission to comment on this page.