Practical guides · Practical guide

SSO, MFA and electronic signatures in GxP systems

An employee signs in with MFA and later clicks “Approve”. What evidence shows that the decision carries the required electronic signature? Assess authentication, session management and signing together while preserving the purpose of each.

Table of contents

At a glance

Does an MFA sign-in replace an electronic signature under Part 11?

Not automatically. SSO handles access through a shared identity mechanism, and MFA strengthens authentication. An electronic signature additionally needs a reliable link between the individual signatory, signature meaning, time and signed record. For Part 11 signatures, assess signature components and session context. Re-entering a password alone is not a complete demonstration either.

Three functions with different purposes

Single sign-on enables access to several applications through common sign-in infrastructure. Multi-factor authentication uses several appropriate factors to verify identity. An electronic signature records a person's confirmation of a particular record. These functions can work together. A secure login alone does not establish what the user subsequently signed.

First, determine whether an action should serve as an electronic signature and which requirements are applicable to it. Not every status click is automatically a Part-11 signature. Part 11's scope of application depends, among other things, on the relevant electronic records and underlying FDA requirements. Annex 11 describes its own expectations for electronic signatures. Avoid a flat-rate equation between EU GMP and US regulation, even if many practical controls fit together.

Sources: [1] [2]

Trace identity from account to decision.

A unique identity begins prior to the first login. Verify attachments, user assignments, role allocations, account modifications, and account revocation. A personal signature user must not be used without appropriate controls involving multiple personnel. Upon employee separation, access must be terminated, while necessary historical assignments must remain clearly documented. A deleted display name may complicate future investigations.

Follow identity throughout the entire technical pathway. The Identity Provider, the specialized application, and a downstream signing service may employ different identifiers. Determine which identifier is permanently significant and how name changes should be handled. A token containing an email address is not automatically a permanently unique personal linkage. Also assess technical accounts: Background processing must not appear without appropriate evidence of an employee's personal authorization.

Sources: [2] [1]

Evaluate session and signature components correctly

For non-biometric Part-11 signatures, § 11.200(a)(1) requires at least two distinct identification components, for example, username and password. During a single, continuous, controlled session, the first signature is performed using all components. For subsequent signatures within the same session, at least one component must be executable only by the signer. Outside of such a session, each signature must utilize all components. A mere reference to SSO or MFA login at the start of the day does not demonstrate compliance with these rules. Verify the actual workflow including session transitions and proxy attempt.

Describe when a session starts, ends, or is considered no longer under control. Consider workstation locking, inactivity, browser switching, shared devices, and reauthentication. Assess whether another employee could potentially use an open session. The signature action must be deliberately performed and correctly assigned to the intended signer. Verify component- and session-specific requirements against the actual implementation concept, rather than concluding compliance solely based on an authentication logo.

Sources: [2]

What the signed record must demonstrate

Determine the significance of approval: created, reviewed, authorized, or another defined statement. The user must understand the specific status being confirmed. Electronic signatures within the scope of Part 11 must include, in plain text, the name of the signatory, the date, and the time of the signature, along with a clear statement of the signature's intent (§ 11.50(a)). These elements must be present in any human-readable form of the signed record, such as display or printout (§ 11.50(b)). The signature must remain linked to the record (§ 11.70). A standalone entry such as "User X approved" without a clear version reference may be insufficient.

Verify display and output. Is signature information remain clearly legible within the required electronic access and, if applicable, in printed form? What occurs if record content is altered after signature? The prior signature reference must not inadvertently transfer to a new content without notice. Define the process for correction, revalidation, and historical review. The validation evidence thus extends beyond successful password acceptance.

Sources: [2] [1]

Example: Approve SOP revision

In the example, reviewer P approves revision 7 of an SOP. They authenticate through the enterprise Identity Provider and then perform the defined signing action. The required package includes P, the exact document version, the signing timestamp, and the statement "reviewed and approved." Following a subsequent amendment, revision 8 is created and must not be considered covered by the signature of the previous version.

Include a session transition, an expired login, and access by an unauthorized user. Assess not only positive usage. A centrally revoked account may still maintain an active application session depending on the architecture; this state must be evaluated. The following matrix serves as an independent work aid. It does not establish a universal token validity period nor a uniform implementation across all signature products.

Test cases for approval of SOP Revision 7
CaseTest stepExpected relationship
Correct version Sign Revision 7 Signature exactly assigned to this revision
Significance Certify awareness deliberately Explanation clearly identifiable
End of session After completion, sign again Appropriate Authentication
Workstation available Attempting external usage Unauthorized signature prevented
Role removed Attempt to use the previous permission again Withdrawal in accordance with concept effective
Content modified Create revision 8 Old signature does not verify new content

Sources: [2] [1]

Set suitable roles and segregation of duties

Verify who is authorized to create, modify, review, and sign off on records. Role separation is derived from the process and its associated risks. Not every application requires identical role models, but unauthorized combinations must be prevented. Test with realistic user accounts. An administrator may hold privileges that should be excluded from routine processes.

Consider standing in for and absence. An authorized substitution does not imply that an individual is using the identity of the original approver. The actual signer and their authority must remain clearly traceable. Additionally, review delegated actions and automations. If a system automatically processes additional data records following a status change, it must be clearly identifiable which personal approval was in effect and which subsequent action was performed technically.

Sources: [1] [2]

Outage, retry, and historical investigation review

An Identity Provider outage may prevent login or signing. Define which processes may continue and which must be placed on hold. Emergency access requires a deliberate evaluation procedure; it must not represent uncontrolled bypassing of signing requirements. Review the subsequent reconciliation and the handling of already initiated but not completed signing actions.

Test a technically interrupted process: Was if the signature was saved but the interface was not updated? Can the "Repeat" function generate a duplicate or conflicting confirmation? The user needs a reliable pathway to clarify the current state. For historical investigation, recording, identity, and signature context are retrieved together. Provider changes, account renaming, or archiving must not inadvertently sever this linkage.

Sources: [1] [3]

Make a defensible justification for suitability determination

Document the scope, architecture, identity and session concept, signature significance, and verification evidence. Explicitly identify what SSO and MFA cover, as well as the additional functions provided by the domain application. A certificate issued to the Identity Provider does not automatically validate the complete signature chain. Conversely, not every organizational control needs to be implemented within the same technical component, provided the overall concept is appropriate.

Define relevant changes: new registration method, different session duration, change of Identity Provider, new signature role, or altered logging. Assess the implications of these changes prior to implementation. Quality lies in a clear, verified linkage between person, statement, and content. A visually compelling signature window lacking this linkage is equally insufficient, as is secure authentication without controlled decision-making.

Sources: [1] [2]

Project experience and collaboration

Distinguish logging in from signing a specific record

With process owners and IT, we follow a signature on a known record. Who signs, which version do they confirm and what does the signature mean? We test login, session behaviour, signature components and the subsequently readable evidence. For an existing function, focused tests may cover session changes and prohibited use by someone else. A new identity service also requires attention to handovers and ownership. The signature's purpose and applicable requirements determine the design.

Frequently asked questions about SSO, MFA and electronic signatures

Is SSO the same as MFA?

No. SSO describes single sign-on across multiple applications. MFA describes authentication of identity using multiple appropriate factors. Both can be combined. Whether the subsequent signing action is appropriate must be further evaluated based on the documentation reference, the declaration, and the applicable regulatory framework.

Must a password be entered before each electronic signature?

For non-biometric Part 11 signatures, a single password dialog is not required for every signing instance. Section 11.200(a)(1) mandates at least two distinct identification components, such as user identifier and password. The first signature within a continuous, controlled session utilizes all components; subsequent signatures within the same session require at least one component that can only be performed by the signatory. Outside of such a session, each signature must utilize all components. Biometric signatures are separately addressed under Section 11.200(b). A successful SSO- or MFA-authentication alone does not constitute valid signature activity. Annex 11, Item 14, does not specify particular components but outlines the required business impact, persistent linkage, and timestamp.

Sources: [2] [1]

Can a click on "Approve" constitute an electronic signature?

It may constitute part of an appropriate signature function. Key considerations include intentional action, authorized signer, significance, timestamp, and reliable linkage to the correct record. Additionally, verify authentication and session control. The button text alone does not determine suitability or regulatory impact.

What happens when the signer's name is changed?

The historical assignment must remain clear. Verify permanent identification, the previous name representation, and current identity management. A simple email address may change or be reassigned. The process must prevent historical signatures from appearing to be linked to the wrong individual.

Can an administrator sign on behalf of an authorized signatory?

A technical administrative authority is not a personal authorization granted under a false identity. The actual signer and their authorization must be verifiable. Authorized delegation is defined within the process and executed using a distinct identity. Review administrative options for modifying signature data separately.

Does Part 11 apply to every system with SSO?

No. The use of SSO alone does not establish applicability under Part 11. This depends on the specific electronic records, signatures, and underlying FDA requirements. The actual determination of applicability occurs prior to the selection and evaluation of the necessary controls.

Sources: [2]

Sources and review date

Status: October 14, 2026. Regulatory classification is based on the listed original sources. Examples and test matrices are internal reference tools. Targeted cross-check conducted on October 18, 2026: Sections 11.50, 11.70, and 11.200 in the secured eCFR original as of October 14, 2026, and Annex 11, Item 14. The remaining historical source material was not re-evaluated as a result.

  1. European Commission: EU GMP Annex 11, Computerised Systems (2011)Current version as per EudraLex inventory as of 14.10.2026. Application, risks, operation, and data lifecycle; specific testing proposals are derived independently.
  2. eCFR: 21 CFR Part 11, Electronic Records; Electronic SignaturesScope and in particular Sections 11.50, 11.70, 11.100, and 11.200. No general obligation arises solely from the use of a registration. Reviewed on 14.10.2026.
  3. 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: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

How we can support you

Daniel Herrmann Consulting combines professional assessment with hands-on work on the specific system. During the first meeting, we clarify your intended use, existing documentation, and the next most appropriate action step.

  • 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 →