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

  • Workforce
    White House rainbow light shutterstock ID : 1130423963 By zhephotography

    White House rolls out DEIA strategy

    On Tuesday, the Biden administration issued agencies a roadmap to guide their efforts to develop strategic plans for diversity, equity, inclusion and accessibility (DEIA), as required under a as required under a June executive order.

  • Defense
    software (whiteMocca/Shutterstock.com)

    Why DOD is so bad at buying software

    The Defense Department wants to acquire emerging technology faster and more efficiently. But will its latest attempts to streamline its processes be enough?

Stay Connected