Skip to main content

Using Open Source Software

Using open source software within a financial services organisation poses unique challenges. This article outlines some of the potential pitfalls and solutions when getting started.

Making the Argument Over Proprietary Software​

An organisation may have some fixed ideas about what is useful for developers to use. For example, a firm might be "A Microsoft shop", where they have paid for an expensive licence for the Microsoft product suite and therefore expect everyone to use Visual Basic, C#, PowerBuilder etc. Although these are powerful tools, are well-supported and have a third party supervising their integrity against vulnerabilities, a single firm can't compete with the extraordinary diversity of the entire open source ecosystem.

  • The first barrier to open source might be in convincing the organisation's tech team that there is a need for using open source software over and above what has been provided.

  • Assemble a group of like-minded individuals who also need to use open source. A community can more easily advocate for open source usage and identify compelling use cases.

  • Popular open source tools like Python or R might be a convincing use-case.

  • You want to avoid creating a headache for an infrastructure team. Make sure they don't get the burden of extra support as a result of your efforts.

  • Sometimes, the argument for proprietary software is about support. It can be argued that it's better to have a large ecosystem than a support hotline. You can draw from a large pool of Java or Python developers to support each other within the organisation and to find talent and advice externally.

  • Finally, an argument against commercial software (and especially a single vendor) is that it creates a monopoly which can mean higher costs. Commercial software licenses can change, often for the worse.

Opening the Firewall​

Often it is impossible to download software from the Internet when working at a regulated firm. Either, download sites are blocked or particular types of traffic are restricted. This is to protect internal systems against malware or trojan-style attacks. However, it is another barrier to consuming open source. There are two approaches to solving this:

  1. You can try to get dispensation to access certain public repositories where open source software is held (e.g npmjs.com or Maven Central). However, your firm might rightly point out that this is a potential malware vector. This might be acceptable if your software is running only on your own PC and not entering "production" (i.e. more sensitive parts of the bank's network, or being made available on the internet).

  2. You can get the infrastructure team to run an Artifact Repository from which open source software can be downloaded. This is the recommended approach as it sets you on the right path for tackling License Compliance and Software Inventory later in your open source journey.

Accessing GitHub / GitLab​

In order to prevent Data and Intellectual Property Leakage many "social media" websites (or sites generally that support uploading of data) are blocked. However, this often prevents access from within the firm to sites like GitHub and GitLab.

Often, the instructions for using open source software is on these sites, whether in the form of a README file or in the answers to issues raised and solved on the open source projects. Further, for some projects in compiled languages, this will be the only place where you can view the source code of the projects. If you have an issue using open source, viewing the source code can sometimes be a helpful way to solve it.

So, without access to the project's open source home page, your effectiveness is limited. There are two potential approaches here:

  1. You can petition for an exception for access to one of these sites. This is typically allowed by many financial services so long as there is good reason and approval is given.

  2. You can view the site using your own hardware (e.g. mobile phone). However, this is much less effective and you need to be careful to abide by firm rules.

Choosing Open Source Components​

Carefully choosing open source dependencies is crucial for the success and security of your projects. As well the considerations mentioned so far here are further hints to help you make informed decisions:

  • Popularity and Community Support: Look for open source dependencies with a large and active community. Consider also the pedigree of the developers and foundation (if any) that the software originates from.
  • Documentation and Code Quality: Ensure that the chosen dependency has clear and comprehensive documentation.
  • Security and Vulnerability Management: Consider the security track record of the dependency. Look for any reported security vulnerabilities and assess the project's response time in fixing them.
  • Type of License: it’s worth considering the specific license clauses beyond whether it is allowed by your firm and whether this fits the specific needs of your project.
  • Available Versions: are up-to-date versions of the dependency available in your approved repository for you to use?
  • Contribution Potential: consider whether the project is one that your firm is currently contributing to. If you think contributions may be necessary to make the most of this dependency, you should raise this ahead of time with your OSPO or line manager.

(This section taken from LFD137)

Build a Community​

As mentioned above, there is strength in numbers. Gather people that are interested in open source usage, to build momentum within your organization. Interact with stakeholders in technology and operations to build awareness of your community’s needs and present yourself as a partner, not a security risk.

Within the community, you can address firm-specific issues, restrictions and solutions. Finding colleagues with the same issues you have generates a consensus around solving them.

Presenting your open source efforts to executives or within a townhall, can demonstrate how you innovate, gain efficiency, and reduce cost (while also addressing potential risks).

An open source-focused community is a fantastic way to share knowledge and network beyond your immediate circle of colleagues.

Learning Outside Your Firm​

One final point: open source isn't just something you need to do at work. Have your own open source profile e.g. on GitHub and develop in personal repositories. Experiment with open source contribution outside of work if it isn't allowed internally.

Training Materials​

A Beginner's Guide to Open Source Software Development

This course is addressed to software developers seeking to understand the ‘rules of the road’ of creating open source software, either as a newbie or as someone with experience primarily in creating proprietary code.