Regulations and compliance · Practical guide

Are ISO 27001 and SOC 2 enough for GxP software?

A certificate may cover one organisational unit or service. Verify that the service you actually use falls within scope. Check the entity named, the period covered and the evidence available before relying on it for a particular risk.

Table of contents

At a glance

Do ISO 27001 or SOC 2 replace GxP validation?

No. An ISO/IEC 27001 certificate or SOC 2 report can provide valuable supplier assessment evidence. It does not establish that the software implements your GxP process suitably. Check scope, covered controls, limitations and responsibilities that remain with your organisation.

Scope and Applicability

ISO/IEC 27001 relates to an information security management system. SOC 2 is a reporting and assessment approach for controls within a service organization. Both should be evaluated based on their actual scope, rather than treated as general GxP compliance badges.

Sources: [1] [2]

Please inquire about the statement behind the logo

A detailed report can make controls, checks and restrictions more understandable than a sales sheet. It remains crucial whether these controls fit your relevant questions: for example access protection, restoration or change control. Exceptions and measures required by the customer deserve special attention.

Add provider information including validation of its usage. Roles, interfaces, technical calculations, and release authorizations often emerge only through your configuration. A provider's security assurance does not automatically confirm the technical accuracy of their implementation.

Sources: [1] [2] [3]

What the evidence each time considers

ISO/IEC 27001 addresses an information security management system. A certificate refers to a specified scope of application. SOC reports evaluate specific controls of an organization or service within the relevant assessment framework. Both can provide valuable insights for supplier assessment, but they do not constitute a general affirmation of your own GxP application.

First, verify whether the actually performed function is adequately covered. A corporate certificate does not need to include every location or service. A report on a platform may consider components other than your specific solution. The provider's name alone does not establish this linkage.

Distinguish between existence and content of evidence. A logo in a presentation provides little insight into scope, time period, exceptions, or customer tasks. Request appropriate information within the permissible framework and assess its relevance. Confidential reports must not be unlawfully disseminated.

Sources: [1] [2] [3]

Develop an evidence matrix for supplier assessment

Link each individual requirement to the available evidence and its limit. A report may, for example, support specific operational or access controls. The correct configuration of your roles, calculations, or quality processes is not automatically confirmed. The matrix makes these remaining tasks visible.

A missing reference may necessitate additional questions or investigations. Evaluate not only whether a document appears up to date, but also whether a new report on a different service is more useful than an older, more directly relevant document with explicit updating justification. The decision must be based on substance and context.

Internal Work Aid: Develop an evidence matrix for supplier evaluation
Own questionPotential contribution to evidenceRemaining inspection
Is the service scope defined? Scope and System Description Reference to the actually performed service
Which controls were considered? Control Procedure Description Relevance for own usage
What time period applies? Date and specified inspection period Changes and gaps thereafter
Are there exceptions? Findings or limitations Impact on own risks from a professional standpoint
What must the customer do? Named customer controls Implementation in own operation
Does our application function? Only limited contribution Configuration and Process Validation

Sources: [1] [2] [3]

Example: certified supplier, unassessed customer interface

A SaaS provider maintains an appropriate security certificate. The customer implements an interface that accepts result values through its own mapping. This mapping swaps two units. The provider's security certification does not address this customer-specific data transformation.

The supplier assessment may utilise appropriate security and operational information. Additionally, mapping, privileges, failure pathways, and subject-matter end-use purposes are reviewed. These activities complement one another. The statement "The supplier is certified" must not be used as a substitute for the organisation's own end-to-end validation evidence.

Also verify the customer-defined tasks mentioned. If a report assumes that the customer appropriately manages user access, this responsibility should be included in your operational model. A control listed in a report but not actually implemented internally remains a gap. Link responsibility to tangible evidence.

Internal Work Aid – Example: certified supplier, unassessed customer interface
Evaluation stepOwn actionExpected finding
Review scope Compare services and locations Evidence relates to correct performance
Exemptions apply Assess relevant findings Impact on own usage is known
Customer control Internal review of rights process Own task completed
Interface Unit transformation testing Proper technical handling
Change Assess the scope of the new service offering Existing evidence remains adequate or will be supplemented.

Sources: [1] [2] [3]

Handle time-stamped data and track changes transparently

A report describes a specific period or time frame. Assess whether any significant changes have occurred since then. A supplementary letter may provide additional information, but it is not automatically considered the same type of independent audit as the original report. Accurately describe the source and statement.

For outsourced services, it must be assessed which components are actually incorporated and which information is missing. An externalized storage or identity service may be relevant to your application. Supplier evaluation should take into account the required dependencies, without performing an exhaustive deep dive into every external component.

Establish an appropriate update pathway. Changes, new insights, or relevant findings may trigger a renewed evaluation. Simply storing updated PDFs on a calendar schedule without content review is insufficient. Conversely, a fully new audit is not required for editorially amended reports.

Sources: [1] [2] [3]

Safety justification and GxP responsibility are interlinked.

Information security supports confidentiality, integrity, and availability. GxP suitability also includes the intended technical process and appropriate evidence for data and decisions. Both perspectives overlap but are not identical. A robust security control does not validate the correct calculation formula.

Assign responsibilities between supplier and customer. Who operates the infrastructure? Who configures user roles? Who evaluates updates? Who verifies quality usage? Annex 11, Sections 3.2 to 3.4 addresses supplier qualification, assessment of standard product documentation, and available quality and audit information. The specific allocation is described in your model and supported by appropriate documentation.

A certificate may influence the scope of supplier assessments if its suitability can be demonstrably evaluated. Automatic exemption from any further assessment does not follow. The decision should integrate risk, available evidence, and remaining gaps.

Sources: [1] [2] [3]

Prepare a concise, actionable evaluation record

The document should integrate service considerations, evidence, boundaries, customer responsibilities, and conclusions. Avoid lengthy general summaries without performance context. A subsequent reviewer should be able to identify which specific risk decision was supported by which document.

Assign remaining tasks to the responsible roles. A supplier assessment that identifies open customer audits becomes practically useful only when these tasks are received in operations. Link them to access, change, or recovery procedures, as appropriate. Thus, a certificate archive becomes a basis for actionable decisions.

Sources: [1] [2] [3]

Worksheet for mapping supplier evidence to your own application

Start with the actually performed service. In the example, a provider operates a SaaS platform, while your organization configures roles and result ownership. Assess which portion a certificate or report covers. A shared corporate brand is not sufficient scope evidence.

Carry over remaining customer tasks into your own execution. A report may assume certain controls at the user level. These should not only be documented in the supplier folder but also be linked to a responsible process and supported by evidence. The matrix links external evidence to internal accountability.

Document the conclusion with clear boundaries. An appropriate justification may influence the depth of internal review, but does not automatically replace all required activities. If the scope or time period is unclear, appropriate questions should be raised. A general green assessment based solely on a known logo would be insufficient.

Sample filling example – internal work aid
Evidence fieldExample entryAssessment question
Service Designated SaaS capability and location. Is it within scope?
Time Date or considered period. Has any subsequent change been clarified?
Control Operating or access control. Which own requirement supports her?
Exception Relevant determination or limitation. What impact does this have on our usage?
Customer request Own user and role management. Actually implemented and verified?
Outstanding evidence Custom Mapping and Workflow. Is own professional assessment available?

Sources: [1] [2] [3]

Next steps

  • Request the relevant original evidence and its scope.
  • Evaluate relevant controls and restrictions.
  • Assign remaining supplier and customer responsibilities.
  • Add your own process and configuration proofs.
Further reading:

Project experience and collaboration

Compare the certificate and report with the service you purchased

With your supplier managers, we read the scope and limits of the actual certificate or audit report. Which service, site and period does it cover, and which controls does it assume the customer operates? Infrastructure may need different additional evidence from a business application. We map the evidence to the GxP use and prepare outstanding questions for the supplier. A recognised certification mark does not establish that your use is covered.

Frequently asked questions about ISO 27001 and SOC 2

Is a certified supplier automatically GxP-qualified?

No. Suitability depends on performance, evidence, and intended use. A certificate may serve as one element of this evaluation.

Sources: [1] [2]

Does every supplier necessarily require ISO 27001?

No. Annex 11 does not name a particular certificate. Under section 3.2 the supplier's competence and reliability matter, and the need for an audit follows a risk assessment. An ISO 27001 certificate or a SOC 2 report can contribute information. Assess the actual services and your GxP use separately.

Sources: [1] [2]

Can a SOC-2 report support a supplier audit?

Yes, if the scope, statement, and timeliness are appropriate. Whether additional checks are required must be justified and decided.

Sources: [1] [2]

Does ISO 27001 replace our GxP validation?

No. An appropriate justification can support information security and supplier assessments. The suitability of your specific configuration, data processing, and quality processes is not automatically confirmed. Review the scope and boundaries and supplement with the necessary internal justifications for the intended use.

Is a SOC report without exceptions automatically sufficient?

Not solely for that reason. Review the system scope, time period, control activities considered, and the customer tasks specified. Even a seemingly routine report may fail to cover your specific interface or application. The conclusion must be based on the actual delivered performance and remaining responsibilities.

How do we handle a report with a relevant exception?

Assess the nature, extent, and potential impact on performance. A deviation is not automatically a grounds for rejection, but it is also not to be treated as inherently unimportant. Leverage additional information and appropriate in-house controls. The conclusion should justify why continued use remains appropriate or specify the applicable limits.

What should be verified when engaging a new subcontractor?

Consider its actual function and impact on your application. Clarify available evidence and responsibility boundaries. Not every external component requires the same level of scrutiny, but critical dependencies must not remain invisible. The existing validation evidence will be assessed for its continued suitability for the modified service.

Sources and review date

Information on ISO 27001 and SOC 2 defines the scope and implications of a certificate or report. Annex 11 provides the GMP framework for suppliers. The comparative questions in the article are internal guidance tools and do not constitute a general equivalence assessment of these certifications.

  1. European Commission: EU GMP Annex 11, Computerised Systems (2011)Annex 11, January 2011: 3.1 regarding formal agreements, and 3.2–3.4 relating to suitability, standard product documentation, and quality or audit information. A specific ISO certificate or SOC report for each supplier is not required.
  2. ISO: ISO/IEC 27001:2022 – Information security management systemsInformation security management system; no evidence of specific professional GxP suitability for a particular application.
  3. AICPA & CIMA: System and Organization Controls – SOC Suite of ServicesReport types and intended use. Scope and actual controls shall be verified in the individual report.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Evaluate supplier documentation for GxP use cases

We support you in assessing the current situation, clarifying responsibilities, and implementing appropriate evidence within operations. The type of support that is most effective depends on your system, your team, and the specific objective.

  • Cloud and SaaS validation →

    Maintain the validated state of cloud and SaaS systems as suppliers issue new versions. We define the boundary between your responsibilities and the supplier’s and agree how each release will be assessed.

Send a project enquiry Customer testimonials →