Table of contents
At a glance
Are technical service accounts permitted in GxP systems?
Technical accounts may be necessary for automated services or interfaces. Give each a defined purpose, limited privileges and an accountable owner. Its actions should remain traceable for the process concerned. Do not use a service account for personal decisions or signatures in a way that obscures individual responsibility.
Scope and Applicability
A technical service must be distinguished from a shared personal user account. Annex 11, Section 12.4 addresses the recording of the individual responsible, §11.100(a) requires unique personal assignment of electronic signatures, and §11.300(a) mandates in the applicable context unique combinations of username and password. Therefore, for integration, you must specifically describe the technical action performed by the service and at which point an additional personal action or decision must remain attributable.
Technical identity and personal actions are distinct
A service account supports automated processing, such as interfaces, jobs, or system services. It does not automatically represent the identity of a natural person. Describe the purpose, personal data involved, required actions, and responsible parties. A general term such as "integration" is insufficient when multiple independent processes operate over it.
The required rights align with the task. Result inheritance may necessitate read or write access to specific objects, but does not inherently require full application administration. Assess the actual scope and alternative approaches. A functioning process under maximum privileges does not demonstrate appropriate restriction.
Personal electronic signatures must not be ambiguously represented as actions of a technical account. When a human initiates a decision and a service technically processes it, the required link to the actual person must be preserved. Automation and personal authentication must be distinguished in the documentation.
Maintain an inventory of purpose, permissions and dependencies
Capture system, account type, operator, data pathways, and required authorizations. Specify authentication method, responsibility for account credentials, and the procedure to follow in case of disruption. The inventory should not contain any sensitive values in plain text. It should describe where and by whom such values are controlled and managed.
Distinguish between productive and test identities appropriately. A test account with elevated privileges may mask errors. A shared identity can obscure the link between environment and action. The specific solution depends on architecture and risk, not on a universal naming convention.
| Inventory field | Own question | Example |
|---|---|---|
| Purpose | Which automated task is performed? | LIMS data transfer result |
| Scope | Which systems and objects are achieved? | Interfaced endpoint and target objects |
| Rights | What actions are required? | Source reading and limited writing in the target |
| Responsibility | Who authorizes and oversees access? | Named technical and scientific responsible party |
| Dependency | What occurs during withdrawal or modification? | Planned Job and Error Notification |
| Lifecycle | When is the review or closure performed? | Roll, system, or contract modification |
Example: Removal of rights unobserved ends the result transfer
A technical access is disabled during a general authorization revocation. The associated job reports an error, but the notification uses the same compromised connection. Results are missing at the destination. As a result, a formally purged account has generated an unresolved data impact.
Before making any changes, assess dependencies. Test account deactivation, detection, and restoration in an appropriate environment. Compare expected versus actually applied actions. Simply reactivating the account does not confirm whether data was lost or duplicated during the period.
An appropriate retry obtains business references and evaluates the target state. Identify who investigates missing data. The error notification should be effective under the considered conditions. Not every service requires a complex backup system; detection must nonetheless align with the potential risk.
| Test case | Action | Expected finding |
|---|---|---|
| Permitted task | Perform the specified transaction | Required processing function works |
| Unnecessary action | Attempt further access | Selected rights limitation applies |
| System unavailability | Account control disable | Disruption is detected |
| Intermediate stock balance | Compare expected processes | Missing or duplicate data identified |
| Recovery | Perform a scheduled retry | Correct target state without undefined multi-effectivity |
Personal responsibility and technical execution are linked.
The assignment may involve multiple levels. A human initiates an authorized process, followed by a technical service transferring the associated data. Evidence must distinguish between these roles and link the activity through stable references. The technical account alone does not constitute proof of human authorization.
The operation is also relevant. An expired secret can disable a interface; uncontrolled replacement can alter the tested access. Plan changes, monitoring, and restarts such that no silent data gaps arise.
Treat secrets and rotation as a change of operation
Access credentials should be managed through an appropriate and secured administrative pathway. They should not be present in publicly accessible scripts, general tables, or uncontrolled emails. The technical solution may vary depending on the environment. What is essential is appropriate access, authorization, and traceable changes.
A rotation may impact multiple services. Plan sequence, available transition options, and functional validation. The test should confirm actual processing, not merely successful authentication. Verify how partially updated connections are detected.
For certificates or other time-limited authentication tools, their expiry dates must be considered. A calendar reminder alone may fail if no responsible party is assigned. Link technical monitoring to designated responsible personnel. The document does not establish a universal rotation period for all service accounts.
Obtain traceability of automatic processing
A technical account can manage multiple data sets. Connection to the respective job, run, and business object is required, as appropriate for the investigation. A protocol line containing only the account name would be insufficient. Additional contextual information should be targeted and appropriately protected.
When a human input triggers a process, determine the required personnel responsibility. The service must not appear ambiguously as the original subject-matter decision-maker. For a purely automated rule, the rule and its approved version must be traceable. Both scenarios have distinct implications.
Check alternative interactive use. An account that is intended exclusively for a service should not serve unresolved as a common user for manual work. The appropriate limitation follows the technical possibilities and the own procedure. Exceptions are consciously evaluated and not run as an invisible habit.
Review, handover and decommissioning planning
Review permissions and purpose against actual use. Is the service still active? Does it still need the same objects? Are there additional integrations that have yet to be assessed? An unchanged account name cannot confirm an unchanged purpose. Link changes back to the inventory.
Upon system decommissioning, access is terminated in the correct sequence. Final exports, historical investigations, or archiving tasks may still depend on him. An unnecessarily active access remains subject to handling. The decision balances data requirements, technical dependencies, and access security.
Assign responsibility, failure recovery pathway, and required evidence. An operations team should be able to investigate a system failure without needing to contact the original developer to retrieve a password stored elsewhere. The inventory supports this capability without disseminating sensitive information.
Draft: Amendment to a technical access without an unexplained data breach
The table outlines a change in technical access. Review a known business case before and after the access change and clarify the handling of an interim inventory that arose during the transition. Document the protected administrative pathway and authority, without including confidential access values in the general audit file.
| Field being changed | Example entry | Assessment question |
|---|---|---|
| Purpose | Automatic result transfer. | Which task must continue to function? |
| Dependency | Job and notification use the connection. | Are all relevant end-users identified? |
| Rights | Only required objects and actions. | Is maximum access restricted so that no account holds it without justification? |
| swap | Designated sequence and responsibility. | No uncontrolled cut-off? |
| Intermediate data | Activities during interruption. | Has missing or duplicate processing been resolved? |
| Closure | Reference case and error detection verified. | Is the system actually again suitable for use? |
Next steps
- Inventory technical identities with intended use and operator.
- Define the minimum required actions and data areas.
- Assign, rights, and error cases review.
- Record changes, monitoring, and withdrawal from operation.
Project experience and collaboration
Change service account access while preserving dependent data flows
With IT and process owners, we trace a service credential to the services and notifications that use it. Before changing it, we agree the sequence, monitoring and a known reference transaction. A single connection may need a straightforward switch. Several dependent jobs require a coordinated handover. Afterwards, we check that transactions occurring during the change were processed correctly. Secret values stay in the designated protected management system and are excluded from general control records.
Frequently asked questions about Service accounts
Must each service account belong to a single individual?
Can a service account electronically sign?
A service account alone cannot substitute for a personal electronic signature. According to 21 CFR § 11.3(b)(7), a person must perform, accept, or authorize the signature; § 11.100(a) requires unambiguous personal attribution. Annex 11, Section 14 also addresses the effect of a handwritten signature. A service can handle the technical processing of a personal signature, but it must then clearly retain the identity of the signing individual and their declaration, rather than acting as the signatory itself.
Is a password change without testing sufficient?
Should a service account be treated like a personal user?
A regulated lifecycle, appropriate authorities and responsibilities are required. Its technical function, however, differs from that of a natural person. Personal decisions and electronic signatures must not ambiguously be attributed to the service. Describe the actual assignment and verify it within the data flow.
Is regular password change alone an adequate control?
No. Purpose, rights, administration, dependencies, and error detection must also align. Uncoordinated changes can disrupt services and create data gaps. Plan and verify the actual process. Appropriate authentication and change frequency should be determined based on the organization's own security and operational model; a universal deadline is not assumed.
Why should a service account review consider actual usage?
An unchanged user name can currently support additional tasks or systems. Verify purpose, rights, and dependencies against the current actual configuration. A simple comparison with an outdated approval list may fail to identify such expansions. The decision should confirm current requirements and appropriate boundaries.
How do we deactivate a technical account during system decommissioning?
First, review and clear the most recent exports, historical access logs, and remaining services. Terminate access in the appropriate sequence and document the actual implementation. Premature access removal may prevent required data transfer; an unnecessarily active access remains subject to further action.
Sources and review date
Annex 11, Part 11, and PIC/S are applied within their respective domains for access control and traceability. The examples differentiate between technical implementation and personal declaration; user accounts and change management procedures are standalone support tools.
- European Commission: EU GMP Annex 11, Computerised Systems (2011)§ 12: Access and responsibility; technical identity and personal signature actions are evaluated separately. Current version as of EudraLex on 14.10.2026; no universal project or deadline assignment.
- eCFR: 21 CFR Part 11 – Electronic Records; Electronic SignaturesCurrent regulatory text. Applicability and additional documentation obligations must be assessed on a process-by-process basis.
- PIC/S: PI 041-1, Good Practices for Data Management and Integrity (2021)Inspection Guidance on Data Integrity; in particular electronic data, transmission, access, and review.
Sources checked: .
Control technical access throughout their lifecycle
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.
- 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.

