Photo of author

Written by Alan Parker, certified Lead Auditor

Published 10 April 2025 · Last reviewed 12 November 2026

Annex A Controls Explained

ISO 27001 Control 8.4: Access to Source Code

Last Updated: 12 November 2026

Alan Parker, ISO 27001 Consultant & Internal Auditor,
Helping UK SMEs hit ISO 27001 in 90 days.
B.Sc (Hons) Information Systems · Certified ISO 27001 Lead Auditor · CISMP · ITIL Expert · 30+ years in IT governance and security.
Read full bio →

ISO 27001 Control 8.4: Access to Source Code
Read and write access to source code, development tools and software libraries shall be appropriately managed.

https://www.iso.org/standard/27001

Key Takeaways

  • Control 8.4 requires access to source code, tools and libraries to be managed.
  • Most development teams already protect their repositories with SSO, MFA and protected branches.
  • Release control is the common weakness: changes pushed with little review and no notice to support.
  • A named approver, a release note and telling support is usually proportionate.
  • Remove former staff and contractors from repositories promptly.

ISO 27001 Control 8.4: Access to Source Code

Introduction

In short: ISO 27001 control 8.4, access to source code, requires read and write access to source code, development tools and libraries to be managed. For a software business that means SSO and MFA on your code platform, protected branches with peer review, controlled releases, and prompt removal of leavers and contractors.

Software development companies tend to be good at protecting their code pipeline, because they have to be. Code lives in GitHub or GitLab, access is controlled, branches are protected, and pull requests are reviewed. That part of control 8.4 I rarely worry about.

Where they fall down is release. I regularly see changes pushed to production with little peer review and no communication with customer support, who then find out about a new feature, or a broken one, when customers start calling. In my previous roles running IT operations I would never have allowed that.

Control 8.4 asks you to manage read and write access to source code, development tools and software libraries. This page covers access to the code itself, and the release controls that should sit around it.


What control 8.4 actually asks for

The control requires read and write access to source code, development tools and software libraries to be appropriately managed. In practice:

  • Access restricted to people who need it, with write access narrower than read.
  • Changes reviewed before they are merged.
  • Protected main branches so nobody can push straight to production code.
  • Releases controlled, approved and communicated.
  • Access removed promptly when people leave, including contractors.

In the 2013 edition this was control A.9.4.5.


The code itself

Most development teams already have the basics: an organisation account in GitHub or GitLab, SSO and MFA enforced, protected branches that require pull request approval, and secrets kept out of the repository. Check that contractors and former staff have been removed, that personal accounts are not used, and that nobody has admin on the organisation who does not need it.


Release is the weak point

Reviewing code and controlling releases are different things. A pull request review checks the code. Release control checks that the change should go out now, that it has been tested, that it can be rolled back, and that the people who will deal with the consequences know about it.

That does not need a heavyweight change board. For most small teams it means a release note, a named approver who is not the author, a check that support and customer success have been told, and a record of what went out and when. This links directly to control 8.32 on change management.


Not just code

Some organisations use Git for document control too, keeping policies and procedures in a repository with full history. That works well, and the same access rules should apply.

Privileged Access Register Download
For this control, the Source code access and Release control tabs record who can merge, who can release, and who approved each release.


What auditors will look for

For source code, I look at the repository settings and the last few releases.

  1. Repository access. Who has write and admin access, and are any of them leavers or contractors?
  2. Branch protection. Can anyone push directly to main?
  3. A recent release. Who approved it, and was support told?
  4. Secrets. How do you keep credentials out of code?

Common issues

  • Developers able to push straight to the main branch.
  • Releases approved by the person who wrote the change, or by nobody.
  • Support teams finding out about releases from customers.
  • Former contractors still in the GitHub organisation.

The self-check

Look at your last release before answering.

  • Can anyone push to main without review?
  • Who approved your last release?
  • Did customer support know before it went out?
  • When did you last remove someone from your code repository?

From rogue releases to a weekly CAB

At the ship-tracking software company where I contracted, the release process was documented, but a few developers did not follow it, and nobody was overseeing whether they did. The result was a run of outages caused by releases, followed by fixes early the next week. The service desk and support teams were furious: they took the customers’ anger and often did not know what had been changed in the first place.

The company hired a service delivery manager specifically to close the gap between teams and act as the custodian of production. He introduced a weekly change advisory board, went through upcoming changes with all the key stakeholders, and made sure QA, development and support had all signed off before anything went live. The improvement was dramatic: fewer incidents, fewer rollbacks, and a much happier support team.

A small business does not need a formal board to get the same benefit. It needs a named person who owns production, a second pair of eyes on every release, and support told before customers are. See control 8.32 for change management more broadly.

It is still the exception. Among the software businesses I have audited or implemented ISO 27001 for since 2024, only around a quarter had someone other than the developer approve a release and tell support before it went live (see my findings).


Frequently asked questions

Is code review enough for 8.4?

Code review covers write access to the code. You also need to control who can release, and make sure releases are approved and communicated.

Do we need a change advisory board?

Not for most small teams. A named approver, a release note and telling support is usually proportionate.


Sources and further reading

Official guidance and standards referred to on this page.

Internal Audit Service

Get an independent view of your ISO 27001 ISMS before you go into an audit.

“Alan from Iseo Blue truly came to our rescue. His support ahead of our internal audit was outstanding, and he helped us get our ISMS 100% ready for the Phase 2 audit.“

– Quartile.

✓ Gain confidence
✓ Audit plan
✓ Independent view
✓ An ISO 27001 requirement

✓ Audit findings report
✓ Recommendations
✓ Review meeting
✓ Fixed price

£2,500

+ VAT where applicable

internal audit report screenshot