ISO/IEC 27001 case study
ISO 27001 case study: a BPO provider protecting client code, data and its own intellectual property
Clause by clause: ISO/IEC 27001:2022 requirements: every clause explained →
A BPO provider entrusted with client code and data adopted controls based on ISO/IEC 27001 to protect its clients' intellectual property and its own, then achieved certification that attracted security-conscious clients and supported its growth.
Key points
- A business process outsourcing provider trusted with client code and data needed to protect that material and its own intellectual property at the same time.
- It adopted controls based on ISO/IEC 27001, which sharply reduced its exposure to breaches, unauthorised access and theft of intellectual property.
- Certification gave security-conscious clients visible proof of commitment, helped attract them and supported the company's growth.
- The certificate itself comes from an independent, accredited certification body; Sterling does not certify.
The organisation and what it needed
The organisation in this ISO 27001 case study is a BPO provider whose clients hand over more than routine work. They entrust it with their source code and their data, which means a single lapse could expose material that belongs to someone else.
The provider faced two obligations at once. It had to safeguard the intellectual property of every client whose code and records passed through its hands, and it had to protect its own intellectual property as well.
The organisation is not named here, and this account keeps to what its case record states.
What was implemented
The provider put in place controls based on ISO/IEC 27001, the international standard for an information security management system. The case record describes the work at that level: an ISMS whose controls were aimed squarely at the three risks the business cared about most, namely breaches, unauthorised access to systems and information, and the theft of intellectual property, whether the client's or its own.
With the controls in place, the provider went on to certification. Under ISO/IEC 27001, that decision is taken by an independent certification body after its own two-stage assessment, not by the organisation or its consultant.
What changed
The first change was in exposure. The ISO/IEC 27001 controls sharply cut the risk of breaches, unauthorised access and intellectual property theft, the very threats that had made the project necessary.
The second change was in how clients saw the business. Certification demonstrated a firm commitment to information security, and that commitment attracted security-conscious clients. In turn, the certificate supported the company's growth.
The third change was cultural. Its chief technology officer said the certificate showed clients that their code and data were in careful hands, and that security has now become part of the company's software DNA.
About ISO/IEC 27001
ISO/IEC 27001 sets out how an organisation governs the confidentiality, integrity and availability of the information it holds. The current edition is ISO/IEC 27001:2022, read together with Amendment 1:2024, which asks organisations to consider whether climate change is a relevant issue. Certificates issued against the 2013 edition lapsed on 31 October 2025, so a valid accredited certificate today names the 2022 edition.
The standard does not hand every organisation the same fixed checklist. It requires a risk assessment against criteria the organisation defines, a decision on how each risk will be treated, and a comparison of the chosen controls with Annex A, whose 93 controls fall into organisational, people, physical and technological themes. The result is recorded in a Statement of Applicability.
Certification is the job of an independent body accredited to ISO/IEC 17021-1 and ISO/IEC 27006-1. It carries out a Stage 1 readiness review and a Stage 2 audit, then returns for surveillance audits in the following years.
How Sterling runs a programme like this
The description below is how Sterling approaches ISO/IEC 27001 programmes in general; it is not an account of this particular client's engagement. Every programme starts with a gap analysis that compares existing policies, controls and records with the standard, keeps what already works and sets an action plan with owners and dates.
| Support level | How the work is shared |
|---|---|
| Design™ | We develop, you implement under our expert advice and supervision. |
| Drive™ | We design and build under your approval, fully managed. |
Design™ and Drive™ are alternatives: an organisation chooses the one that fits its capacity rather than moving from one to the other. Either way, the engagement includes Effivity, the ISMS software used in 50+ countries, at no additional cost, together with a vulnerability assessment and internal auditor training for your audit team, as applicable to your standard.
How Sterling supports ISO/IEC 27001
Protect client code, data and your own intellectual property with an ISMS clients trust
Since 2003, Sterling has supported 8,100+ client engagements in 60+ countries, with offices in 21 countries. Our expert and experienced consultants build the ISMS with your people and prepare you for the certification body's assessment. We ensure successful certification for our clients.
Book a free discovery callISO/IEC 27001 for BPO providers: questions buyers ask
Does ISO/IEC 27001 protect client source code and intellectual property, or only personal data?
It covers whatever information the organisation brings into its ISMS scope, including source code, designs and business records as well as personal data. The risk assessment identifies those assets, and Annex A offers controls for asset classification, access, secure development and data leakage prevention that the provider selects where its risks call for them.
Who in a BPO should own the information security management system?
The standard places the commitment with top management, which approves the security policy and assigns roles, responsibilities and authority. IT runs many technical controls, but operations, HR, facilities and account teams own risks too, and an ISMS that sits with IT alone tends to struggle at audit.
Once a BPO is certified, how is the certificate kept valid?
The certification body returns for surveillance audits each year and carries out a recertification audit in the third year. Between those visits the provider keeps repeating its risk assessments, access reviews, internal audits and management reviews, because the auditor looks for evidence that the system is still operating.
More ISO/IEC 27001 guides
Every guide in the ISO/IEC 27001 series is written for one question and links back to the hub for the whole picture.
- Annex A: the 93 controls by theme, explained
- ISO/IEC 27001 for banking, fintech and financial services
- ISO/IEC 27001 benefits
- ISO/IEC 27001 for BPO and shared services
- ISO/IEC 27001 certification process, step by step
- ISO/IEC 27001 checklist
- Choosing an ISO/IEC 27001 certification body
- ISO/IEC 27001 certification cost: what moves the price
- ISO/IEC 27001 requirements explained, clause by clause
- ISO/IEC 27001 risk assessment and treatment, step by step
- The Statement of Applicability: how to write one that survives the audit
- ISO/IEC 27001 vs SOC 2: which one, or both?
Keep exploring
Explore more about ISO/IEC 27001
Watch a video on how to implement ISO 27001 here.
Watch a video on ISO 27001 requirements here.
ISO/IEC 27001 resources
Services for ISO/IEC 27001
Talk to a consultant
Plan an ISMS that keeps client code and data in careful hands.
Tell us your goals, locations and target date. We’ll help you define the scope, timeline and next steps.
hello@sterling-grc.com+1 201 263 4443 (global headquarters) · your nearest office and its number are at the top of this page
What would you like to achieve?
Choose a starting point. The enquiry form takes about a minute.
Book my free discovery callContinue to the enquiry form to share your details. Please do not include passwords, sensitive personal information or confidential files. A Sterling consultant replies within one working day. Privacy notice