Table of contents
At a glance
How do you control remote support access from the original request through closure?
Annex 11 links supplier responsibilities, access control, controlled changes and incident assessment. Define the purpose, individual, target system, permitted actions and evidence for each remote support task. Limit access to the assignment, handle unplanned interventions separately and verify revocation and the relevant data and system states afterwards. Closing a ticket alone does not demonstrate that access ended or that the issue was resolved.
- A maintenance agreement does not replace the release and limitation of individual batches.
- The registration, actual activities, and results are separate documentation requirements.
- The closure includes effective access reduction and evaluation of relevant changes.
1. Delimit remote maintenance as a concrete activity
Annex 11 § 3.1 explicitly lists remote access maintenance as an example of a third-party service. Appropriate controls for authorizations, changes, and incidents are also required. The relevant version listed as valid as of 7 October 2026 remains the January 2011 edition within the human medicinal product GMP domain.
Each individual action requires a clear instruction. "Repair the system" is ambiguous regarding the environment, data, or settings involved. Identify the observed malfunction, the scope of the approved investigation, and the responsible operational contact. An existing agreement may provide general guidelines; the specific procedure ensures their application is traceable.
2. Prior to access, provide the necessary information
Clearly define the target system and instance. A similar naming convention for test and production environments can lead to significant confusion. Specify which data are required for the investigation and whether sensitive content is visible. Data protection and information security considerations may require a separate technical assessment.
In addition, clarify the initial state: Which version and configuration are relevant, what processes are currently running, and what restrictions apply? If a change is planned, its prerequisites must align with the approved change control procedure. The mere presence of an internal personnel at the screen does not constitute prior agreement on authorized interventions.
3. Define a limited support task
The following internal work aid structures an assignment. It does not specify a particular ticketing system or remote monitoring product. What is important is that the task, person, and activity can be consolidated and that relevant extensions to the task do not occur unnoticed.
The first reading of the diagnostic access can prove to be inadequate in the course of the process. Then it is necessary to decide whether and under what conditions a writing intervention is permitted. This decision should be based on the possible effect. A small technical change can be technically significant, for example if it influences a material status assignment.
| Information | Definition in the example | Purpose |
|---|---|---|
| Objective | Production instance DOC-P | Avoid confusion with test environment |
| Trigger | Incorrect display of a released document | Limit the scope of the investigation |
| Person | Specifically assigned support personnel | Keep the activity attributable |
| Initial scope | Readiness diagnosis of configuration and error log | No silent data correction is permitted |
| Extension | Authoritative change only after new decision | Scope and purpose remain linked |
| Closure | Activity Report, System Status Review, Access Termination | Assess technical and professional outcomes |
4. Limit and authenticate access appropriately
Assess rights, accessible systems, and usable access pathways. Access should enable the assigned activity without unnecessarily exposing additional data or environments. Individual identifiability is important to allow a technical access point to be reliably linked to a specific individual.
PIC/S PI 041-1 addresses remote access to critical data via the Internet, including additional authentication techniques. Transfer this specific security concern to your architecture. This does not imply a universal equivalence between remote access, electronic signatures, and a particular product. Even strong authentication provides limited protection if subsequent unrestricted rights or unmonitored alternative access paths remain.
5. Example: Use with pre-defined desired value
Example: In DOC-P, an incorrect display appears for document SOP-018. The released order initially permits only read-only diagnosis. Support identifies a configuration root cause and proposes a correction. In the intended model, such a change may only be executed after additional operational decision-making.
Following the amendment, the correct display and reference to the current document revision will be verified. Access will then be terminated in a controlled manner. The following matrix describes expected outcomes, not actual product testing. In particular, it is not assumed that each remote maintenance tool terminates sessions or privileges in the same way.
| Situation | Predefined expected result | Subject for evaluation |
|---|---|---|
| Reading instruction | No independent data or configuration modification | Tasks and available authorities |
| Change will be required | Expansion will be evaluated and decided | Relationship with altered scope of order |
| Change performed | Agreed state established | Activity, Result, and Relevant Inspection |
| Task completed | No further authorized access granted | Review rights and, if applicable, existing session |
| Unforeseen data access | Impact is assessed and escalated | Incident reference instead of silent ticket closure |
6. Demonstrate that activities are clearly understood
A successful registration does not validate all subsequent actions. Select evidence that enables identification of relevant activities and changes. Appropriate technical logs, configuration comparisons, and a specific activity report may serve this purpose. The required combination depends on the task and potential impact.
Annex 11 does not require complete screen capture of every session. Such capture would also not automatically replace professional assessment. What is essential is whether, at a later date, you can trace back which relevant interventions took place, whether they were authorized, and whether the intended effect was achieved without unexplained adverse outcomes.
7. Separate access and disruption to be addressed independently
Verify how access is actually terminated. Removing a permission may affect existing sessions differently than new logins. Additionally, supplementary accounts, temporary network grants, or archived auxiliary files may still be relevant. The actual deactivation must align with the technical environment.
Evaluate independently of the technical outcome. Has the disturbance been resolved? Have altered data or settings been reviewed? Are open questions documented? Annex 11 § 13 distinguishes between the evaluation of all incidents and the root cause investigation of critical incidents. Not every technical error requires the same level of formal root cause analysis; however, its potential consequences must not remain unassessed.
8. Make the process feasible within a small team
Establish a regular procedure and a limited emergency procedure. If the normally responsible individual is unavailable, it must be clearly defined who has authority to make decisions and which interventions remain permissible. A continuously open, comprehensive access is not a necessary consequence of a small organization.
Walk through the process with IT, system ownership, QA, and the contractor in a specific case scenario. Assess whether the required evidence is actually generated and made available. An ideal form does little good if the contract, the tool, or the readiness organization does not support the intended steps.
- Target instance, rationale, named individual, and initial scope defined.
- Rights and authentication are assessed to be appropriate for the actual architecture.
- Expansion from read-only to controlled edit capability.
- Appropriate evidence of activities and outcomes is required.
- Effective access verified including additional releases reviewed.
- Technical conclusion, open items, and incident assessment documented.
Project experience and collaboration
Define the permitted scope of a remote intervention and document its outcome
With IT, process owners and the service provider, we prepare a typical remote maintenance task. Before the session, we agree its purpose, required permissions, permitted changes and how to check the result. Read-only diagnosis may need different controls from changes to production settings. We test the logging that is actually available and verify access removal. The records should identify who did what and which effect on the business process was assessed.
Frequently asked questions about Remote maintenance in GxP
Can a supplier fundamentally access GMP systems remotely?
Remote access is explicitly mentioned as a possible third-party function in Annex 11 § 3.1. Appropriate agreements and controls are required. Remote access alone does not render an implementation unacceptable or sufficiently secured; what is decisive are the tasks, rights, traceability, and implications.
Sources: [1]
Does a valid maintenance agreement exist for each access?
It may establish general functions and responsibilities. However, for each specific instance, the purpose, reason, individual involved, and authorized activities must remain clearly defined. A broadly worded support agreement does not demonstrate that each specific intervention in any environment has been professionally authorized.
Must someone be on watch throughout the entire session?
No. Annex 11 requires agreements with third parties (3.1), access controls (12), and evaluation of incidents (13), but does not mandate continuous monitoring of each session. The level of oversight and documentation required for a particular activity must be determined based on its risk profile. Simple observation alone does not constitute effective control, recording, and review of results.
Is screen capture always required?
No. Annex 11 does not require screen recordings of remote monitoring activities. Select evidence demonstrating that relevant activities and their outcomes can be traced. A video neither replaces a professional assessment of changes nor serves as a validation of adverse effects. Additionally, consider the protection of any potentially visible data.
How do we handle an initially read access that requires changes?
Evaluate the order expansion prior to implementing the change within the regular workflow. Assess implications, authorization, and appropriate supporting evidence. For emergencies, establish a defined decision pathway; the ongoing session must not automatically translate into an unbounded change authorization.
Sources: [1]
What authentication is appropriate?
It must align with actual exposure and criticality. PIC/S specifies additional authentication methods for remote access to critical data via the Internet. Additionally, verify individual assignment and rights limitation. Relying on a single technique alone does not establish complete control over the support process.
When is access truly terminated?
When the access rights granted for the task are effectively revoked within the intended scope, consider existing sessions, additional accounts, and temporary authorizations. A closed ticket or the statement "logged out" may lack sufficient technical substantiation to confirm such revocation.
Must every support error trigger a CAPA?
Annex 11 §13 requires reporting and evaluation of incidents, including root cause identification for critical incidents as the basis for appropriate corrective and preventive actions. Assess the significance and implications. A generic automated CAPA for every defect report or a blanket exclusion of technical incidents is not justified.
Sources: [1]
Can the contractor itself confirm the successful completion?
He may report his activities and technical outcomes. Whether this evidence is sufficient to support your professional conclusion must be assessed by the responsible roles. A resolved alert may still require a reconciliation of the affected document revisions or previously completed activities.
What do we assess first for an existing remote monitoring solution?
Sources and review date
Source date: 07.10.2026. The relevant area here is human medicinal product GMP. EudraLex incorporates Annex 11 and Chapter 4 as of January 2011; the consulted draft from 2025 is not considered a current regulatory requirement. The completed examples and tables are internal work aids and do not constitute official template documents.
- EU GMP Annex 11: Computerised SystemsRevision January 2011; Effective date 30.06.2011; Access date 07.10.2026. Citations: §§2–3, 9–13, 16
- EU GMP Chapter 4: DocumentationRevision January 2011; Effective date 30.06.2011; Access date 07.10.2026. References: §§4.1, 4.5, 4.8–4.10
- EU GMP Chapter 7: Outsourced ActivitiesRevision 1, in effect since 31.01.2013; accessed on 07.10.2026. Relevant sections: §§7.1, 7.4, 7.6–7.8, 7.14–7.17
- PIC/S PI 041-1: Good Practices for Data Management and IntegrityPI 041-1, 01.07.2021; Access date 07.10.2026. Citations: §9.5, in particular page 42–43 Remote access and network; §9.6
- European Commission: EudraLex Volume 4Status as of 07.10.2026: Human medicinal product section implements Annex 11 January 2011 and Chapter 4 January 2011; Access date 07.10.2026. Relevant provisions: Human medicines / Annex 11
- European Commission: Consultation 2025 on Chapter 4, Annex 11 and Annex 22Status as of 07.10.2026: closed; 07.07.–07.10.2025. Occurrences: details; revision of Annex 11; links explicitly marked as draft guidelines. Serves solely for status demarcation and is not considered an authoritative source of requirements.
Sources checked: .
Address the specific control and verification requirements
Daniel Herrmann Consulting supports you in adapting this procedure to your system portfolio, evaluating gaps, and preparing appropriate validation evidence. The scope and level of involvement are determined by your actual process.
- 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.

