On Thu, Jan 30, 2014 at 3:22 PM, Saunders, Thomas D. II <thomas.d.saunders...@saic.com> wrote: > To Whom it may concern: > I have questions in regarding how to configure Open Office securely to > conform to DOD guidelines and policies. Do you have some guide in how to > configure Open Office to a secure environment?
Hi Tom, I'm stripping the longer cc list. You can fill them in when you have the info you need. First, I want to make sure that you know that OpenOffice is an open source software application. It is developed by a community of volunteers. I'm pretty sure that none of us works for the DOD, and I'd be surprised if any of us was intimately familiar with DOD guidelines and policies. The same would go for the internal security policies of any organization. The intent is for Apache OpenOffice to be secure out-of-the-box for most users and most uses. If I had to guess, hardening OpenOffice would entail things like: 1) Disabling macro execution for unsigned documents 2) Changing default encryption algorithm to AES256 3) Disabling automatic update notifications, with the idea of the organization managing updates themselves. (Maybe other list members have additional ideas?) But this is only speculation, since I'm not an expert on DOD requirements. To really answer your question, about DOD requirements specifically, you'll need to figure out what these requirements are, and ask specific questions regarding OpenOffice capabilities. Or find a consultant able to do this analysis for you. We have a list of consultants on our website here: http://www.openoffice.org/bizdev/consultants.html Regards, -Rob > v/r > Tom Saunders > Senior Information Assurance & Security Engineer / Security Specialist > Mobile: 540-408-3087 > > Classification: UNCLASSIFIED//FOR OFFICIAL USE ONLY > > ------------------------------------------- List Conduct Guidelines: http://openoffice.apache.org/list-conduct.html To unsubscribe, e-mail: users-unsubscr...@openoffice.apache.org For additional commands, e-mail: users-h...@openoffice.apache.org