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 [email protected] and we will post it for you.

Featured

  • Budget
    Stock photo ID: 134176955 By Richard Cavalleri

    House passes stopgap spending bill

    The current appropriations bills are set to expire on Oct. 1; the bill now goes to the Senate where it is expected to pass.

  • Defense
    concept image of radio communication (DARPA)

    What to look for in DOD's coming spectrum strategy

    Interoperability, integration and JADC2 are likely to figure into an updated electromagnetic spectrum strategy expected soon from the Department of Defense.

Stay Connected