Regulations

EU GMP Annex 11

EU GMP guidance on computerized systems (2011 version, in force). Each clause below says what it asks for, in our words, and how nil answers it.

Built 13Partly built 3Planned 4Customer's procedure 2Vendor 1Not applicable 3

Annex 11, clause by clause
ClauseAsks for (paraphrased)How nil answers itStatus
PrincipleValidate the application, qualify infrastructure; no added risk over the manual processThe vendor validates nil; the customer validates their configuration; infrastructure qualification comes with the deployment, which is not decided yet.

Several requirements; see nil’s validation report.

Partly built
§1Risk management decides how far validation and data-integrity controls goEvery vendor requirement carries a risk level; on the customer side, each requirement on a Configuration Validation record carries a risk and its reason, and High and Medium risks need a test.

Proved by requirementAC-cv-testing-1and testcv_test::a_cv_is_tested_against_its_approved_protocolPassing

Built
§2Defined responsibilities, qualifications, and accessRoles and groups explain who can do what and why

Several requirements; see nil’s validation report.

Built
§3.1–3.4Agreements with suppliers; risk-based supplier assessment; supplier QMS information for inspectorsnil is the supplier: vendor assurance pack (validation report, threat models, SBOM, QMS summary) Planned
§4.1–4.2Validation covers the lifecycle; includes change control records and deviation reportsVendor: a validation report per release. Customer: the Configuration Validation record holds the change, its tests and their runs, test incidents, and the signed approval.

Proved by requirementAC-cv-records-1and testcv_test::only_what_was_tested_is_releasedPassing

Built
§4.3Inventory and, for critical systems, an up-to-date system descriptionConfiguration specification generated from the live system

Proved by requirementAC-configuration-1and testconfiguration_test::the_specification_is_generated_from_the_live_configurationPassing

Built
§4.4User requirements, risk-based, traceable through the lifecycleVendor: acceptance criteria traced to tests. Customer: intended use and requirements, each with its risk, on the Configuration Validation record, traced to tests in a generated traceability matrix.

Proved by requirementAC-cv-testing-7and testcv_test::validation_documents_are_generated_and_fixed_by_freezePassing

Built
§4.5The system is developed under an appropriate QMS; supplier assessedVendor's QMS; the validation kit is its evidence Vendor
§4.6Bespoke systems: formal quality and performance reportingnil is a configured product, not bespoke Not applicable
§4.7Evidence of test methods and scenarios: limits, data limits, error handling; test tools assessed; test environments assessed for adequacyTests cover empties, limits, and malformed input; no retries in validation runs. Environments run PROD's exact release and start from PROD's configuration with a matching fingerprint, kept apart from PROD by process and database role, and say on every page that they aren't production

Proved by requirementAC-validation-kit-2and testvalidation_report::tests_are_traced_through_their_doc_commentsPassing

Built
§4.8Data migration doesn't alter value or meaningDocument import checks every row in a dry run and is all or nothing, with a hashed report. Configuration copied into an environment travels as a hashed package; a release applies exactly the tested changes to production, only if both configuration fingerprints match.

Proved by requirementAC-cv-records-3and testcv_test::only_what_was_tested_is_releasedPassing

Built
§5Built-in checks on data exchanged with other systemsNo interfaces yet (API: none). Entry checks are cited here too; strictly §6 is the better fit Not applicable
§6Extra accuracy check on critical manual entries (second person or validated electronic means)Server-side validation of every value; a workflow can add a second-person verification step

Proved by requirementAC-option-lists-2and testoption_lists_test::records_take_only_allowed_optionsPassing

Built
§7.1Stored data protected, checked for accessibility, readability, accuracyAudit chain verified daily and on demand; stored files never overwritten or deleted, and checked against their SHA-256 on every read

Proved by requirementAC-audit-trail-4and testaudit_entry::verification_finds_an_altered_entryPassing

Built
§7.2Regular backups; restore checked during validation and periodicallyNot built Planned
§8.1Clear printed copiesExports; printable configuration specification

Proved by requirementAC-configuration-4and testconfiguration_test::exports_are_canonicalPassing

Built
§8.2Printouts show whether data changed since entry (batch release)Record printout with its change history Planned
§9Audit trail of GMP-relevant changes; reason recorded; intelligible; regularly reviewedAudit trail with reasons as the settings require, readable and filterable

Proved by requirementAC-settings-1and testsettings_test::reasons_follow_their_settingPassing

Partly built
§10Changes, including configuration, only in a controlled way under a procedureProduction accepts changes to validated configuration only as a package released by an approved Configuration Validation record: designed in a changeset, tested in a validation environment, approved by someone independent, released only between the tested fingerprints. Every page states the validation state, and a daily and start-up check finds any change made outside nil.

Proved by requirementAC-cv-records-6and testcv_test::the_gate_refuses_validated_changes_outside_a_releasePassing

Built
§11Periodic evaluation that the system remains validAccess reviews; baseline diffs; the validation state on every page and the daily check that production remains in its validated state. Planned: a generated periodic evaluation pack

Proved by requirementAC-configuration-3and testconfiguration_test::comparing_a_snapshot_lists_every_differencePassing

Partly built
§12.1–12.4Access controls by criticality; access changes recorded; identity on every entryAccess model; every access change audited with impact preview. Environments: entered only through PROD's sign-in (single-use, one-minute hand-over), no passwords of their own

Proved by requirementAC-environments-4and testenvironments_test::handover_tokens_are_single_use_and_short_livedPassing

Built
§13Incidents reported and assessed; root cause for critical ones; CAPAThe Deviations and CAPA modules can carry system incidents Customer's procedure
§14E-signatures equivalent to handwritten, permanently linked, time-stampedE-signatures

Proved by requirementAC-e-signatures-3and testsignatures_test::the_signature_shows_name_time_meaning_and_whether_it_holdsPassing

Built
§15Batch release only by Qualified Persons, e-signedNot a medicinal-product batch system Not applicable
§16Business continuity for critical processesThe customer's plan; nil supplies exports Customer's procedure
§17Archived data stays accessible, readable, and intact across system changesNot built Planned

The 2025 draft revision

A draft for consultation, not in force. Its requirements are far more specific than the 2011 text; these rows are what it adds or sharpens.

Annex 11 2025 draft, clause by clause
ClauseAsks for (paraphrased)How nil answers itStatus
§6.6Configuration options described in the requirements; the chosen configuration documented in a controlled configuration specificationThe configuration specification generated from the live system, with signed validated baselines

Proved by requirementAC-configuration-validation-1and testconfiguration_validation_test::the_specification_shows_the_linePassing

Built
§8.1–8.7Alarms where the user relies on being notified; acknowledged by authorized people with a comment; an alarm log, searchable and reviewedThe alarm for a change made outside nil: emailed, shown in red on every page, and decided in a Configuration deviation with what happened and a signature; all in the audit trail

Proved by requirementAC-configuration-validation-6and testconfiguration_validation_test::changes_made_outside_nil_turn_the_state_redPassing

Built
§9.2Validation scope based on a documented risk assessment of individual requirementsEach requirement on a CV carries a risk and the reason; High and Medium need a test

Proved by requirementAC-cv-testing-1and testcv_test::a_cv_is_tested_against_its_approved_protocolPassing

Built
§9.5Test cases traceable to requirements, e.g. a traceability matrixA generated traceability matrix per CV; vendor tests trace to acceptance criteria

Proved by requirementAC-cv-testing-7and testcv_test::validation_documents_are_generated_and_fixed_by_freezePassing

Built
§9.7Validation according to approved plans, protocols, and test scriptsThe test protocol is approved, signed, before testing starts

Proved by requirementAC-cv-testing-2and testcv_test::a_cv_is_tested_against_its_approved_protocolPassing

Built
§9.8Conditional approval with documented assessment of deficienciesTest incidents explain failed runs (what failed, why, impact, resolution) and appear in the summary report

Proved by requirementAC-cv-testing-4and testcv_test::a_cv_is_tested_against_its_approved_protocolPassing

Built
§9.9Vendor documentation reviewed and authorized by the regulated userThe vendor validation report per release, for the user to review

Several requirements; see nil’s validation report.

Built
§11.4Passwords set by someone else changed at first loginAccounts start from an invitation: people set their own password

Several requirements; see nil’s validation report.

Built
§11.5Password rules commensurate with risk: length, mixed characters, no dictionary words, different from previousMinimum length and a check against common passwords; composition rules aren't enforced (current NIST guidance prefers length)

Several requirements; see nil’s validation report.

Partly built
§11.6Multifactor authentication for remote access to critical systemsTwo-factor sign-in with an authenticator app. A validated setting requires it for everyone: anyone without it sets it up before doing anything else, and nobody can turn it off

Proved by requirementAC-user-administration-13and testauth_totp_test::required_two_factor_must_be_set_up_firstPassing

Built
§11.7Accounts locked after failed attempts, unlocked only by an administratorSign-in pauses after 5 failures. After a set number of wrong passwords in a row (10 by default, a validated setting) the account locks: no sign-in method opens it, a password reset included, until an administrator unlocks it with a rationale. Both are audited and in the person's access log

Proved by requirementAC-user-administration-12and testadmin_users_test::an_account_locks_after_repeated_failed_sign_insPassing

Built
§11.8Automatic inactivity logout the user can't changeSession idle timeout set for everyone by the administrator

Several requirements; see nil’s validation report.

Built
§11.9An access log of logins and logouts (incl. inactivity logouts), searchable or exportableSign-ins, failures, sign-outs, revoked sessions, and sessions ended by inactivity or their time limit (at the moment they ended), recorded per person

Proved by requirementAC-user-administration-11and testauth_core_test::an_ended_session_is_logged_when_it_endedPassing

Built
§11.10Segregation of duties (GMP users without administrative rights) and least privilegeAllow-only roles from a fixed permission catalog; the customer decides who administers

Several requirements; see nil’s validation report.

Built
§11.11Recurrent access reviews, including the access of rolesSigned periodic access reviews over a frozen snapshot of who holds what

Several requirements; see nil’s validation report.

Built
§12.2Audit trail: who (with their role, if they hold several), what (old and new), when (with time zone), why (prompted)Who with the roles they held at that moment, what with old and new values, when (UTC), and why where the settings ask for a rationale

Proved by requirementAC-audit-trail-14and testsignatures_test::the_signature_and_audit_entry_name_the_signers_rolesPassing

Built
§12.3Audit trail locked; changing its settings or the time recorded; only by an administrator outside GMP workAlways on, append-only and hash-chained; settings changes are audited; time from the server clock

Several requirements; see nil’s validation report.

Built
§12.4, §12.9Audit trail searchable and sortable; a complete electronic copy that can be searchedThe audit trail browser with filters; CSV export with its hashes

Several requirements; see nil’s validation report.

Built
§12.5–12.8Documented, risk-based, independent, and timely audit trail reviewsPlanned: scheduled audit trail review records, signed Planned
§13.3Full re-authentication for a signature; password only for signatures in immediate sequenceUser ID and password on the first signature in a session, password after

Several requirements; see nil’s validation report.

Built
§13.6A signature's manifestation: full name, username, role, meaning, and date and time (with time zone)Name, the roles the signer held when signing, user ID (email), meaning, and date and time in UTC

Proved by requirementAC-e-signatures-12and testsignatures_test::the_signature_and_audit_entry_name_the_signers_rolesPassing

Built
§13.8A signed record changed later shows as unsignedEach signature holds the hash of what was signed and shows whether it is still valid

Several requirements; see nil’s validation report.

Built
§13.9Hybrid: a hash of the electronic record printed on the signature pagePDFs carry the content hash

Several requirements; see nil’s validation report.

Built
§14.2(iii)Undocumented changes found, e.g. by configuration auditingA daily and start-up check finds any change made outside nil

Proved by requirementAC-configuration-validation-6and testconfiguration_validation_test::changes_made_outside_nil_turn_the_state_redPassing

Built
§14.1–14.3Periodic reviews of the system's validated state, by planPlanned: a periodic evaluation pack with the changes, reviews, and incidents since the last one Planned
§15–17Security, backup, restore tests, and archivingThe hosting and the customer's procedures; nil never deletes data Vendor

Reading this table

Built
In nil today. Where one requirement answers the clause, its trace names that requirement and the test that proves it, passing in nil’s suite; where several do, the row says so and nil’s validation report lists them.
Partly built
Part of the clause is in nil today; the row says which part is not yet.
Planned
On the roadmap, not in nil today.
Customer's procedure
Met by your procedures; nil may record or support it.
Vendor
Met by nil’s supplier quality system rather than by the software.
Not applicable
The clause does not apply to a system like nil; the row says why.