ISO 27001 Quality Management System: What It Really Covers
ISO 27001 is not a quality management system: it's an information security management system standard, while ISO 9001 is the quality one. If you treat it as another folder of quality procedures, you'll miss what the security audit actually checks.
The advice I'd push back on is building a separate compliance operation for each standard. You need real security expertise, but you don't need duplicate management meetings or corrective action logs. Running a small document-sharing company, I'd rather have one routine with clear ownership than two systems nobody has time to maintain.
Is ISO 27001 a quality management system? No, it's information security
ISO 27001 specifies an information security management system, usually shortened to ISMS. That means a structured way to identify information-security risks, decide how to treat them and keep those decisions under review.
The confusion starts with the words management system. They describe how you organise responsibility and check whether work happens properly. They don't make every management-system standard a quality standard.
The standard connects security decisions
ISO/IEC 27001 has had three editions: the first in 2005, a second in 2013 and the current one in October 2022. Its current Annex A contains 93 controls across four categories: organisational, people, physical and technological controls.
Those categories cover subjects such as access control, cryptography, physical protection and incident management. They aren't a shopping list of security software. A password manager or encryption service might support a control, but buying it doesn't establish who owns the process or prove that staff follow it.
For a document-sharing service, the practical connections matter. Access permissions need an owner. Incident response needs a route from detection to action. Supplier oversight needs evidence rather than an assumption that someone else has handled security.
Here's how I'd put the difference. A quality system checks how consistently you deliver what was specified. A security system checks who holds the keys, what they can reach and how you track that access. It's a rough split, but it helps when a procurement questionnaire mixes product reliability with information protection. An auditor isn't certifying that every document you send is accurate or persuasive. They're assessing whether the organisation operates a functioning, risk-based security management system.
When you translate security compliance requirements into daily work, start with the information and the decisions surrounding it, not a policy template.
ISO 9001 and ISO 27001 side by side
ISO 9001 and ISO 27001 compared
| Aspect | ISO 9001 | ISO 27001 |
|---|---|---|
| Core purpose | Consistent product or service quality and customer satisfaction | Protecting confidentiality, integrity and availability of information |
| Subject matter | Quality of processes, products and services | Information security risks and the controls that treat them |
| Risk approach | Risk-based thinking applied across processes | Formal risk assessment with defined risk-acceptance criteria |
| Controls | Processes defined by the organisation | Annex A controls selected and justified through risk treatment |
| Typical owner | Quality manager | CISO, security lead or IT head |
| Certification cycle | Initial certification, surveillance and recertification | Initial certification, surveillance and recertification |
| Common structure | Shared management-system clauses covering context through improvement | The same management-system structure, applied to information security |
Read the purpose row before deciding which certificate you need. A customer complaining that every delivery arrives with a different finish is describing a quality problem. A customer asking who can download their confidential proposal is describing an information-security problem.
Think of a coatings manufacturer: the ISO 9001 question is whether production consistently delivers the required finish, not whether a particular employee can open a customer's files.
Your business model changes the starting point
If you manufacture goods or deliver a repeatable service, quality management can be the natural starting point. You want staff to follow a controlled process and catch departures from the agreed specification. The owner needs enough authority to change how work happens, not just collect inspection records.
If your business holds customer documents or regulated records, information-security questions arrive quickly. Who can access the information? Can someone alter it without authorisation? Can you recover it when a system fails?
These aren't competing priorities. A consultancy can deliver an excellent report and still send it to the wrong person. Equally, a securely delivered report can contain poor work.
A buyer asking for a certificate should be clear about the failure they're trying to prevent.
When a customer asks for an ISO 27001 quality management system, clarify their concern before answering. If they mean consistent delivery, discuss quality assurance. If they mean confidential information, discuss the ISMS and its scope.
Don't substitute one certificate for the other because the names look similar. You can run both through shared governance, but each standard still needs its own evidence.
Risk assessment and the Statement of Applicability
Risk assessment is where ISO 27001 stops looking like a generic process manual. You must explain which information could be harmed, how that could happen and what you'll do about it.
In ISO/IEC 27001, Clause 6.1.2 requires a defined assessment process with explicit acceptance criteria, repeatable and comparable results, identification of confidentiality, integrity and availability risks, and named risk owners. Clause 6.1.3 then requires risk treatment, approval of residual risk and a Statement of Applicability, or SoA, documenting necessary controls, implementation status and justified exclusions.
Turn the requirements into a working register
You don't need an elaborate scoring application to begin. You need an agreed method that different people can apply consistently, plus somewhere to keep the decisions.
- List the assets. Include uploaded documents, viewer identity data, page-level telemetry, email notifications and encryption keys. Identify where each asset lives and who uses it.
- Score likelihood and impact using an agreed method. Define the scoring terms before assessing individual risks, so serious doesn't mean something different to every assessor.
- Assign an owner and treatment deadline. The owner must be able to make or escalate the decision, not just receive reminders.
- Record the residual rating and evidence location. Show what risk remains after treatment and retain its approval.
- Write the SoA entry for each control, explaining its relevance, implementation status or exclusion.
Say a notification email exposes information to someone who shouldn't receive it. The risk assessment should consider the information contained in the message and how recipients are selected. Treatment might include changing notification content or checking permissions before dispatch.
A control choice should answer an identified risk, not simply fill an empty row in a spreadsheet.
Consistent criteria produce comparable assessments. Comparable assessments make control choices defensible. Written reasons let an auditor or customer follow the decision without reconstructing it through email.
ISO 27001 doesn't prescribe a single risk-scoring method. A qualitative approach can work, as can a quantitative one, provided the results are consistent and reproducible.
Apply that discipline to secure file sharing for business: follow the information through its actual workflow, rather than assessing storage while ignoring sharing.
Metrics that show your ISMS is working
A passed audit isn't enough to tell you whether security work is improving. Look at trends, especially recurring failures and overdue corrections.
If the team repeatedly fixes the same notification-access defect, closing each ticket doesn't demonstrate a lasting fix. You need to know why the defect returns and whether the release process tests the relevant permission boundary.
Starter metrics for an ISMS
| Metric | What it tells you | What a worsening trend means |
|---|---|---|
| Privileged accounts reviewed on schedule | Whether access reviews happen when planned | Unnecessary access may be accumulating |
| Mean time to revoke access | How quickly leavers and role changes are actioned | Former staff or contractors may retain access |
| Encryption key rotation compliance | Share of applicable keys rotated within policy | Keys remain in use beyond your policy |
| Mean time to detect and contain incidents | Speed of spotting and stopping a security event | Monitoring or response steps need attention |
| Critical vulnerabilities fixed within SLA | Patch discipline against your deadlines | Remediation capacity isn't keeping up |
| Backup restore success rate | Whether tested backups can be recovered | Recovery arrangements may not work when needed |
| Corrective action closure time | How quickly findings are resolved | Ownership or root-cause work may be weak |
Define the measure before setting a target
These are management measures, not universal ISO pass marks. Set thresholds using your risk appetite, contractual commitments and operating history. A deadline without a reason encourages people to optimise the dashboard rather than reduce risk.
For access revocation, define when the clock starts. Is it the employee's departure time, the manager's request or the moment IT receives a ticket? If teams use different starting points, the average won't help you compare performance.
For backup restoration, record what you restored and whether it was usable. A successful job notification isn't the same as recovering the information your service needs. For corrective actions, distinguish completed work from work whose effectiveness has been checked.
Review rule: When a measure worsens, assign a decision or investigation, not just a comment in the meeting minutes.
Start with a small set your team can maintain reliably. Put the results in the management review meeting and ask the owner to explain exceptions. Expand only when collecting and acting on the existing measures has become routine.
For sensitive workflows such as HIPAA-compliant video sharing, choose measures that reflect how information could escape or become unavailable. A neat dashboard of unrelated infrastructure statistics won't answer that question.
Certification stages, surveillance and renewal
A policy folder doesn't earn a certificate. Certification involves reviewing the design of the ISMS and checking whether people operate it in practice.
Certification usually runs in two stages. Stage 1 reviews documentation, risk assessment and the Statement of Applicability, while Stage 2 tests implementation. The certificate normally lasts three years, with surveillance audits in the first and second years and recertification in the third.
Plan for evidence, not just audit dates
During the documentation review, the certification body needs to understand your system. That includes the boundaries you've chosen and how your risk decisions support the controls you say are necessary. Contradictions between the scope, risk register and SoA deserve attention before implementation is assessed.
During implementation assessment, expect questions that connect policy to evidence. If your procedure requires access reviews, where are the completed reviews? If you identified a nonconformity, what changed and how did you check that the change worked?
| Audit activity | What to prepare |
|---|---|
| Initial documentation review | Scope, policies, risk assessment and SoA |
| Implementation assessment | Operating records, interviews and control evidence |
| Surveillance | Updated evidence, changes and corrective action records |
| Recertification | Evidence that the system remains suitable and effective |
Use an independent certification body. UK organisations seeking formally recognised certification commonly look for UKAS accreditation. Check that accreditation is relevant to the certification being offered, rather than assuming any accreditation logo answers the question.
The budgeting trap is to pay for the initial assessment and treat everything afterwards as somebody else's administrative task. Surveillance still requires staff time, current records and attention to changes in the business.
Budget for the whole certification lifecycle. Name an internal owner for each assessment and make evidence collection part of ordinary work, not a scramble before the auditor arrives.
Check the scope before you trust a certificate
A certificate applies to its written scope, not automatically to everything a supplier does. That distinction matters more than the logo on a sales deck.
This guide to designing an enterprise ISMS, from a GRC software vendor, explains that scope identifies the organisational boundaries, locations, systems and services covered by the ISMS. A valid certificate can cover a particular business unit or service while leaving another product outside it.
Match the certificate to what you're buying
Say you're buying hosted software for confidential customer documents. The supplier's corporate office might sit inside a certified ISMS, but you need to establish whether the service handling your files does too. Don't infer that connection from the company name alone.
Use this checklist before signing:
- Obtain the certificate and written scope statement. Read the service names and boundaries, not just the headline.
- Confirm the certification body's accreditation. For UK procurement, check the relevant UKAS accreditation where formally recognised certification is required.
- Check that the hosted service, supporting infrastructure and information-handling processes sit inside the scope. Include the relevant personnel and outsourced dependencies.
- Request the Statement of Applicability or an available summary of audit evidence. A supplier may restrict detailed documents, so establish what assurance it can share securely.
- Check certificate validity and surveillance status. Confirm that the certificate is current rather than relying on an old attachment.
A narrow scope isn't automatically misleading. It can be appropriate for a clearly bounded service. The problem is a mismatch between the service you rely on and the assurance you think you're receiving.
Apply the same scrutiny to us
LiveDocument holds an ISO 27001 certification and a SOC 2 report, and I'm happy for buyers to ask for the scope statement and the report. They support due diligence, but they shouldn't replace your own review of whether the assurance matches how you intend to use the product. The details are on our security page.
I wouldn't want a buyer to treat a badge as permission to stop asking questions. Your team still needs to understand its own access responsibilities and what information it intends to share. A supplier's management system doesn't make those decisions for you.
Run the checklist before signing, then file the scope statement with the contract. That gives the person approving renewal something concrete to review when the service or your use of it changes.
Questions people ask about ISO 27001 and quality
Is ISO 27001 the same as ISO 9001?
No. ISO 9001 manages the quality of processes, products and services, while ISO 27001 manages information-security risk. Their shared management structure lets a team coordinate administration, but the evidence must still answer the requirements of each standard.
Can one certificate cover both standards?
Each standard needs its own certification decision and clearly identified certification coverage. A certification body can coordinate or combine audit activities, so this doesn't necessarily mean completely separate audit visits. Your internal audit programme and corrective action process can support both without duplicating every record.
Does an ISO 27001 certificate mean a supplier is secure?
It means an independent certification body assessed a risk-based management system within a defined scope. Where the certificate is accredited, accreditation provides an additional check on the certification body's competence. It doesn't promise perfect controls, prevent every incident or provide assurance about activities outside that scope.
Can a small team run quality and security together?
Yes, provided responsibilities stay clear and the team has access to the necessary security expertise. Keep shared governance proportionate, and retain evidence from normal workflows wherever possible. The test is whether someone can explain a decision and show that the agreed process happened, not how many policy documents you've produced.
About the Author
Cameron JamesCameron is the founder of LiveDocument. He writes about sharing documents, PDFs, decks and contracts, and why pairing a video walkthrough with a document beats sending it cold.