Cookies on this site. Help us understand what works and improve your experience. Essential cookies keep the site working. With your permission, our visit insights and Google Analytics measure usage, and Google Ads measures advertising. Optional cookies are not required to use the free kit. Change your choice anytime in Cookie settings. Privacy policyCookie policy
Control read and write access to source code, development tools and libraries.
Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.
Why this control matters
Access to source code fails when developers, contractors, or service accounts accumulate broad read and write rights without review. Teams should connect repository permissions, branch rules, and secrets handling to role accountability, so changes are traceable and unsafe merges are blocked before release. Retain evidence of exceptions, temporary access, and removal after role change.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
Repository access lists include former staff or vendors, suggesting rights reviews are not tied to joiner-mover-leaver events or project end dates.
Branch protection is configured inconsistently, allowing direct commits or self-approval on sensitive branches without documented risk acceptance.
Secrets appear in commit history, configuration files, or test fixtures, showing developers lack a controlled pattern for keys, tokens, and connection strings.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
Assign the repository owner or engineering manager to approve access by role, project, and environment, with a quarterly review against active work tickets, support needs, and supplier involvement. Use private repositories, least-privilege groups, and separate write access for maintainers, release managers, and temporary fix teams.
Define branch protection for sensitive code paths: mandatory pull requests, at least one independent review, status checks, signed commits where practical, and blocked direct pushes. Pair this with emergency change handling so hotfix access is time-bound, logged, and revoked after post-change review.
Maintain a source code access matrix covering developers, testers, DevOps, library mirrors, CI runners, and admin accounts. Record requested scope, approval, start and end dates, and the business reason. Remove orphaned accounts through an automated reconciliation step with HR or project rosters.
Require secure handling of secrets outside repositories, with code scanning on commits, pre-receive checks, and a documented response path when exposure is found. Keep evidence of remediation, such as secret rotation tickets, affected-branch review notes, and the decision to rebase, invalidate, or archive compromised credentials.
What an auditor will ask to see
Repository permission export showing named roles, privileged maintainers, and last review date against the access register.
Pull request records with reviewer names, branch protection status, build checks, and exception approvals for urgent fixes.
Secret scanning alerts, remediation tickets, and proof of token rotation or credential revocation after exposure.
Baseline documents in the kit
These free kit documents help you document or evidence A.8.4. Each one is tailored to your organization when you build your kit.
Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.
For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.
Get these documents tailored to your organization
109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.