Letter: The danger of standard configuration

In reference to "Use of brand names in solicitations still a problem," I empathize with Red Hat and other viable software companies with regard to the well-intended work of OMB and NIST to advance standardized security configurations. Unfortunately, the message contained in both OMB and NIST recommendations is very vendor-specific and recommends the adoption of a single vendor configuration. This clearly puts the open source community at a disadvantage, since they have not been given an equal opportunity to participate in this effort, and it works in favor of Microsoft, which already has unfair advantage.


The real harm comes from having agencies get so caught up in moving to enterprise agreements that support these configurations that they overlook the real needs of the user community and miss emerging innovations that could provide greater value at lower cost. 


John Weiler, The Interoperability Clearinghouse


****


What do you think? Post a comment (registration required) or e-mail it to letters@1105govinfo.com and we will post it for you.

Featured

  • FCW PERSPECTIVES
    sensor network (agsandrew/Shutterstock.com)

    Are agencies really ready for EIS?

    The telecom contract has the potential to reinvent IT infrastructure, but finding the bandwidth to take full advantage could prove difficult.

  • People
    Dave Powner, GAO

    Dave Powner audits the state of federal IT

    The GAO director of information technology issues is leaving government after 16 years. On his way out the door, Dave Powner details how far govtech has come in the past two decades and flags the most critical issues he sees facing federal IT leaders.

  • FCW Illustration.  Original Images: Shutterstock, Airbnb

    Should federal contracting be more like Airbnb?

    Steve Kelman believes a lighter touch and a bit more trust could transform today's compliance culture.

Stay Connected

FCW Update

Sign up for our newsletter.

I agree to this site's Privacy Policy.