Hosting
- Amazon Web Services, United States
- Database in a private network with no internet access
- Standby database in a second data centre
Qualsted supports compliance with 21 CFR Part 11 and EU GMP Annex 11. Here's exactly how each control works, how it's verified, and what remains your responsibility.
| Clause | How Qualsted meets it |
|---|---|
| §11.10(a) · Annex 11 §4 | Validation evidence with every release. Requirements traced to automated tests, installation checks and deviations, in a report for your validation file. |
| §11.10(b) · Annex 11 §8 | Accurate and complete copies. Server-made PDFs and CSV exports, stating who printed them and when; every export is audited. |
| §11.10(c) · Annex 11 §7, §17 | Records protected for their whole life. No hard deletes anywhere: the app's database role can't delete. Records are archived; published versions and files are kept. |
| §11.10(d) · Annex 11 §12 | Access limited to authorized people. Unique accounts, two-step sign-in, single sign-on, and permission checks on the server for every request. |
| §11.10(e) · Annex 11 §9 | Secure, computer-generated, time-stamped audit trails. Append-only in the database, with server time; before and after values for every change. |
| §11.10(f) · Annex 11 §15 | Operational sequence checks. Review workflows enforce signing order; records lock in review and after publication. |
| §11.10(g) | Authority checks. Only designated signers from the step's group can sign; only managers change structure; only admins manage people. |
| §11.50 | Signature manifestations. Printed name, date and time, and meaning, shown wherever the signature appears, including printouts. |
| §11.70 | Signature and record linking. A SHA-256 hash of the signed content is stored with each signature; any later difference is flagged. |
| §11.100 · §11.300(a) | Unique to one person. Accounts are never deleted and emails never reused; vendor support accounts are separate and can never sign. |
| §11.200 | Signature components. A fresh password, or a fresh single sign-on confirmed by the identity provider, at the moment of signing. |
| §11.300(b)–(d) | Password and misuse controls. NIST 800-63B password rules; five failed attempts lock the account and alert admins at once; lost authenticators are reset by an admin. |
Quality and lab standards ask for controlled documents and trustworthy records. Here's where Qualsted's controls answer them.
| Standard | What it asks, and how Qualsted supports it |
|---|---|
| ISO 9001 §7.5 | Control of documented information. Review and approval before release, versions with history, protection from unintended change, and access by permission. |
| ISO 13485 §4.2.4 · §4.2.5 | Control of documents and records. Approved, versioned documents; records kept legible and retrievable, with changes identified. Also the basis of the FDA's QMSR. |
| ISO/IEC 17025 §7.5 · §8.4 | Technical records and their control. Every change traceable to the previous value, the person and the time; records protected and kept. |
| AS9100 · IATF 16949 §7.5 | Documented information and retention. Controlled records kept for their retention period: nothing is ever hard-deleted, only archived. |
| 21 CFR 117 Subpart F | Food safety records. Records made at the time of the activity, with the date and time and the signature of the person who did it. |
Your auditor judges your quality system as a whole: these are the record-keeping controls Qualsted provides toward it.
Each release is checked by the full automated test suite and documented in a validation report, so your computerized system validation can focus on your intended use.
Aligned with a risk-based, GAMP 5 and FDA CSA approach: automated, repeatable evidence rather than paper scripts.
| ID | Requirement | Tests | Result |
|---|---|---|---|
| ACC-06 | Lockout and alerting | 2 | PASS |
| AUD-01 | Audit trail append-only | 4 | PASS |
| SIG-01 | Credentials at signing | 2 | PASS |
| DAT-01 | No hard deletes | 7 | PASS |
| PLT-04 | Hosting safeguards | 14 | PASS |
Use a key from your own AWS account for your files and secrets. If you disable or revoke it, they become unreadable to everyone, us included, within minutes.
Our engineers request access with a reason. Your admin approves it for a level and a time window, or denies it, and can withdraw it at once. Support accounts can never sign records or grant themselves anything, and everything they do is in your audit trail.
There's no such certification for software. FDA doesn't certify systems; compliance is the result of the system's controls together with your procedures and validation. Qualsted provides the controls and the supplier evidence that they work.
Not yet. An independent penetration test and a SOC 2 audit are on our roadmap, and we'll share the reports with customers when they're complete. Until then we're glad to answer your security questionnaire in detail and walk your team through the controls. See the trust center for what's available today.
Yes. We support supplier qualification, including questionnaires, documentation review and audits, as part of onboarding.
Qualsted is built with the HIPAA Security Rule's technical safeguards in mind (access control, audit controls, integrity, authentication and encryption). Talk to us before storing protected health information, so we can agree the right terms first.
Your records, files and audit trail are yours. You can export any table as CSV or PDF at any time, and when you leave we hand over a complete copy of your records, files and audit trail. Nothing is deleted while you're a customer.
What each clause asks for, what's on your vendor and what stays with you.
ValidationFDA's risk-based approach, with a worked example for a configurable system.
RegulationsWhat the draft changes and a gap checklist to start now.
We'll show the audit trail, signatures and validation report on a live workspace, and answer your supplier questionnaire.