Regulations and compliance · Practical guide

Part 11 open and closed systems: how to assess scope

Under Part 11, an on-premises installation is not necessarily closed, and an internet-connected cloud service is not necessarily open. Identify who controls access and who is responsible for the content of the electronic records. Document the boundary, including external users, administrators and relevant data transfers.

Table of contents

At a glance

When is a system open or closed under Part 11?

Part 11 distinguishes open and closed systems by whether the people responsible for the electronic records control system access. Cloud, internet or on-premises deployment alone does not settle the question. Section 11.10 describes controls for closed systems. Section 11.30 requires corresponding controls for open systems and additional measures where needed to protect authenticity, integrity and, as appropriate, confidentiality.

  • First establish Part 11 applicability, then define the specific system boundaries.
  • External users or contractors do not automatically result in classification "open".
  • A encryption function alone does not demonstrate either closed operation or all required controls.

1. The definition is based on access control

§11.3(b)(4) describes a closed system as an environment whose access is controlled by personnel responsible for the content of electronic records. In an open system as defined in §11.3(b)(9), such control does not exist. This phrasing places responsibility and actual access control at the center.

It does not provide a specific network type as sufficient evidence. Therefore, a corporate building, a VPN, or an isolated network alone is not adequate proof. Conversely, an externally operated environment may have controlled access. Document who has the authority to grant, modify, or revoke access and how these permissions are linked to the respective record process.

Sources: [1]

2. First determine which environment you are assessing

Before entering "open" or "closed" status, determine the Part 11 scope for the affected records. The presence of a publicly accessible prospect server does not automatically constitute a Part 11 system. For the actual record processing process, application, identity management, administrative access, and handover pathway may be relevant.

As a work aid, identify the stages from creation to the intended recipient. Specify the relevant documentation and responsible parties for each stage. Export data may leave the controlled environment without automatically implying that all subsequent environments adopt the same classification. Explicitly evaluate this boundary.

Sources: [1] [2]

3. Consider more than the registration of standard users

A personal login is a critical component, but still not a complete picture. Who is authorized to create new users, modify roles, edit data via administrative tools, or obtain access through an interface? What technical accounts exist, and who is responsible for their usage? These questions clarify access control.

For a service provider, assess contractual responsibilities alongside effective technical controls. Provider personnel do not automatically make a system open. A contract alone provides insufficient evidence that it is closed. Verify that the access paths described are actually controlled.

Sources: [1]

4. Classify three access scenarios separately

The following matrix does not classify any existing installation. The respective assumptions are intended to illustrate which information supports a justified decision and when the data available is still insufficient for classification.

Own Architecture Matrix: Responsibility and Access
SituationFixed assumptionClassification and Remaining Question
A: Local use for a supervised record process Responsible parties control all relevant user and administrative access rights in accordance with defined authorizations. Under this assumption, the review of the effectiveness of the controls as per §11.10 remains to be assessed.
B: Cloud portal with employees and authorized external inspectors User access is controlled; procedures and authorities for provider administration have not been validated. Cloud and external auditors do not decide the classification. Complete proof of responsibility and access; leave status open until then.
C: Electronic record passes through a transfer environment The individuals responsible for record content do not control access to this considered environment. Open to this assumed environment. Determine appropriate §11.30 controls and handovers to the recipient.

Sources: [1]

5. Closed does not mean uncontrolled

Section 11.10 mentions, among other things, validation, appropriate copies, protection during storage, access restrictions, audit trails, and operational, authorization, and potentially equipment checks. The classification "closed" therefore serves as the starting point for a control assessment, not a simplified conformity certificate.

Example: All users were properly authorized, but an authorized reader may accidentally modify data sets. Permission assessment at the account level then does not adequately address the authorization question for a specific action. Test relevant actions with appropriate roles, rather than only verifying successful login and password error scenarios.

Sources: [1]

6. Match additional controls to the open environment

§11.30 requires appropriate procedures and controls for open systems to ensure authenticity, integrity, and, where applicable, confidentiality from creation through to receipt. This includes the controls specified in §11.10, to the extent they are appropriate, as well as additional measures. The text mentions, for example, encryption and appropriate digital signature standards, where such measures are required under the circumstances.

It does not follow that a universal algorithm exists nor that every open connection must be secured identically. Justify the selection based on the data pathway and associated risks. Encryption of transmission alone does not address questions such as whether the intended recipient receives the correct record or whether an outdated version is erroneously treated as current.

Sources: [1]

7. Check access withdrawal and transfer with clear target values

In the example case, three test identities have access: Operator A, Reader B, and external auditor C. C loses their authorization. Thereafter, two active, authorized identities should remain. Additionally, record R-42, Revision 7, is transferred to a designated recipient. The numbers are for traceability only; a correct number of users does not prove the correct individual authorizations.

The case is a separate test recommendation. It does not assume a specific product behaviour nor guaranteed interface functions. If a system does not provide a relevant control, the suitability of the intended overall procedure is to be evaluated; a process document does not compensate for the gap automatically.

Example: Test scenario for access and record transfer
Test stepExpectedStatement and Scope
Remove access C C cannot further utilize the considered record pathway; A and B remain authorized according to their roles. 3 minus 1 = 2 authorized identities; additionally, verify the specific access paths.
Reader B attempts a change Changes are prevented according to the defined read authorization. Checks authorization for this action, not all role functions.
R-42 Revision 7 transferred Recipient, record ID, and revision match the intended package. The same number of files is not sufficient as proof of content.
Deviation from current status R-42 Revision 6 to be proposed A deviation is identified within the intended control procedure and investigated prior to unauthorized use. No automatic version restriction is claimed for a specific product.

Sources: [1]

8. Maintain the operational classification up to date

A new portal, an additional service provider, or a different identity provider may alter the previous justification. Review the relevant responsibilities, access rights, and handovers in such cases. A complete reclassification of every minor update is not a necessary objective.

For a small team, a concise architecture document with reference to validation evidence is practical: system boundary, record owner, controlling roles, and known open points. IT provides the technical pathways; the functionally responsible party defines the record purpose and authorized actions. The decision must align with both perspectives.

  • Determine the applicability of Part 11 for the considered records.
  • Clearly delimit the evaluated environment and the transfer.
  • Assign responsibility for content and access control.
  • Consider user, administrative, and technical access rights.
  • Support the classification with evidence that is actually available.
  • Select specific additional controls required for open environment conditions.
  • User access revocation, authorities, and relevant transfer errors to be verified.
  • Handle changes and unresolved access gaps in a traceable manner.

Sources: [1]

Project experience and collaboration

Assess access controls at the actual system boundary

Using a relevant data path, we establish with IT and record owners who grants, revokes and monitors access. We include external users, providers and transfers. Actual control may affect the classification and additional safeguards required. Cloud hosting alone does not determine either. We describe the boundary so protective measures and corresponding tests have an unambiguous scope.

Frequently asked questions about Open and closed systems

Are cloud systems always open systems under Part 11?

No. The definition relies on control of access by personnel responsible for the records. Cloud operation alone does not address this question. Verify user access, administration, responsibilities, and relevant handovers for the specific environment.

Sources: [1]

Is the local application automatically closed?

Even a local installation requires justified access control. The presence of a network location or corporate building alone does not suffice. Uncontrolled administrative access or unclear responsibilities must be evaluated, even if the application is not publicly accessible from the Internet.

Sources: [1]

Do external auditors make the system open?

Not solely based on external affiliation. If access and permissions within the relevant procedure are controlled, external role status is not an automatic exclusion criterion. Specifically assess the assignment, scope, duration, and revocation of authorizations.

Sources: [1]

Must we be able to personally identify each provider administrator?

The definition does not include such a blanket list of names. However, it must be possible to assess whether the relevant access control and responsibility measures are feasible. The type of personal or process-related documentation that is appropriate depends on the specific operating agreement and data pathway.

Sources: [1]

Does password protection suffice for the status assignment "closed"?

A password protection is part of a broader set of access controls. It does not alone address who creates accounts, who uses privileged access, or who enables interfaces. Assess the complete environment and the responsibilities associated with access rights.

Sources: [1]

Is an open system fundamentally unacceptable under Part 11?

No. §11.30 explicitly describes controls for open systems. Appropriate implementation must align with the data pathway. This is not an automatic suitability assurance: if authenticity, integrity, and required protection are not adequately ensured, a relevant gap remains.

Sources: [1]

Does §11.30 always require a digital signature?

The text mentions additional measures such as encryption and appropriate digital signature standards, where applicable and required under the given circumstances. A one-size-fits-all approach for every architecture would be overly broad. Justify which controls are required for your specific open environment.

Sources: [1]

Can the same process chain have different system boundaries?

Yes. A controlled application and a separate transfer environment may exhibit different access scenarios. Explicitly describe the boundaries and handovers. The classification of a station must not be unverifiedly applied to all subsequent pathways.

Sources: [1]

Does encrypted transmission demonstrate full compliance with Part 11?

No. Encryption alone addresses only certain protection concerns. It does not, for example, ensure correct recipient assignment, complete records, appropriate authorizations, or required signature verification. Evaluate the full applicable control suite for the specific purpose.

Sources: [1]

When must we re-evaluate the classification?

When relevant access paths, responsibilities, or system boundaries change. Examples include a new external access point, altered administration procedures, or an additional transmission pathway. These triggers are a practical derivation from the definition and controls, not a universal calendar-based review period.

Sources: [1]

Sources and review date

Source date: October 6, 2026: 21 CFR Part 11, particularly §§11.3, 11.10, and 11.30; eCFR display up to October 2, 2026. The FDA Guidance Scope and Application 2003 is used for pre-emptive applicability assessment. Architecture and testing cases are standalone reference documents, not a classification of a specific cloud product.

  1. 21 CFR Part 11 — Electronic Records; Electronic SignatureseCFR: Title 21 consolidated through 02.10.2026; Title 21 last amended on 30.09.2026. The display does not constitute a claim of a Part 11 amendment on this date. Citations: §11.1(a)–(e) and sector-specific exemptions (f)–(p); §11.2; §11.3(b)(4),(5),(6),(7),(9); §11.10(a)–(k); §11.30; §§11.50, 11.70, 11.100, 11.200, 11.300
  2. FDA: Part 11 — Scope and Application, Original-PDFOriginal cover page August 2003, Pharmaceutical CGMPs; Contains nonbinding recommendations. Currently listed by FDA as Final. Reference locations: I. Introduction, printed pages 1–2; III.A, page 4; III.B.1–2, pages 5–6; III.C.1–5, pages 6–8

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Applicability and targeted review of evidence

Daniel Herrmann Consulting supports you in defining your specific process and the appropriate documentation requirements. The scope and responsibilities are aligned with actual needs.

  • Computer system validation →

    Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

Send a project enquiry Customer testimonials →