Question

Which of the following is a transparency risk of closed source software?

1) Closed source software may not be accessible to independent auditors.
2) Closed source software cannot be reviewed by the organization that developed it.
3) Closed source software cannot be shared with business partners.
4) Closed source software includes obfuscated code that cannot be read by a human.

Answer 1

The transparency risk of closed source software is that it may not be available for review by independent auditors, hindering verification of its security and quality.

Step-by-step explanation:

The transparency risk of closed source software is that closed source software may not be accessible to independent auditors. This limitation means that the internal workings, code, and implementation details of the software are not available for external review. This lack of transparency can prevent independent verification of the software's security, quality, and adherence to standards, which may lead to issues in analyzing, parameterizing, and communicating the software's process or finding potential improvements. However, it is worth noting that such transparency may come with its own set of challenges, as legal and technical scrutiny of complex code can be both expensive and difficult to implement effectively.