The IT Law Wiki

COTS software

32,080pages on
this wiki
Add New Page
Add New Page Talk0

Overview Edit

COTS software is used 'as-is.' COTS products are designed to be easily installed and configured to interoperate with existing system components. Almost all software bought by the average computer user and much of the software used by the U.S. Government and the DoD is COTS. Examples include operating systems, database management systems, email servers, application servers, and office product suites.

Because it is mass-produced, one of the major advantages of COTS software is the relatively low cost of acquiring, maintaining and achieving technology refresh. Given these low costs and the competitive forces at work, COTS software producers may or may not know, manage or track the provenance of their software, except to the extent needed to ensure that the necessary licenses are obtained for embedded components. In addition, they generally do not make source code available, so supplier identity and software content is often blurred by the reuse of legacy code, subcontracting, outsourcing, and use of Open Source Software (OSS).

Risks of COTS software Edit

COTS software development environments can be more easily penetrated than custom development environments because:

The risk of damage from maliciously introduced vulnerabilities increases with the ease of adversarial access to the development environment. U.S. businesses and foreign businesses with development based in the United States are not immune to adversary manipulation by U.S. citizens or "outsiders" infiltrated into a domestic operation. That said, an adversary with "home court advantage" finds it safer and cheaper to manipulate the production and distribution of software products in its own control.

Source Edit

Also on Fandom

Random Wiki