The Management System
Clauses 4 to 10: scope, leadership, risk assessment and treatment, documented information, internal audit, management review, continual improvement. This is the half that gets skipped.
We build and run the information security management system your certification body audits. ITS gets you ready and keeps you ready. The certificate comes from them.
Almost nobody fails ISO 27001 on technology. They fail on the management system: the parts that have to be decided, written down, reviewed and evidenced. These are the seven that surface at the worst moment. The standard is one framework inside our wider IT compliance services, and the 2022 revision is the version you start on.
The findings we are called in to fix:
ISO 27001 is voluntary. People pursue it anyway for three reasons, and only one of them is security.
ISO 27001 is an international certificate awarded by an accredited body for a management system. SOC 2 is an American attestation report written by a CPA firm about a window of time. Buyers in Europe usually ask for ISO 27001; buyers in the United States usually ask for SOC 2. If both are being asked for, the control work overlaps heavily and the evidence can be collected once. The audits cannot.
ISO 27001 has two halves. The clauses define the management system you have to run, and Annex A lists 93 controls in four themes that you select from and justify. Here is the whole shape of it.
Annex A counts as published by ITS in "What Does the ISO 27001 Update Mean for Your Business?": 37 plus 8 plus 14 plus 34 equals 93, and the four themes are the 2022 revision's own grouping rather than an editorial one.
Clauses 4 to 10: scope, leadership, risk assessment and treatment, documented information, internal audit, management review, continual improvement. This is the half that gets skipped.
37 controls. Policies and roles, supplier and cloud security, threat intelligence, incident management, continuity, and the statement of applicability that justifies your choices.
8 controls. Screening, terms of employment, awareness and training, the disciplinary process, remote working, and reporting security events.
14 controls. Secure areas and perimeters, equipment siting and maintenance, storage media, clear desk and screen, and physical security monitoring.
34 controls. Access and authentication, cryptography, logging and monitoring, secure development, configuration management, data masking, information deletion and web filtering.
Scope, build, then audit. You can stop after any step.
We agree what the ISMS covers, which systems, sites and people are in it, then assess where you stand against the clauses and Annex A. Scope decides cost, so this is the step worth slowing down for.
Risk assessment and treatment, statement of applicability, policies people will actually follow, and the controls running underneath: access, logging, patching, backup, training. Then internal audit and management review, on a schedule.
An accredited certification body reviews your documentation, then audits the system in operation. ITS prepares the evidence, coordinates with the auditor and works the findings. We do not conduct the audit, and no managed provider should.
Two ITS clients who had to satisfy somebody else's security requirements, in their own words. Neither is quoted about ISO 27001.
ITS led significant, transformational changes at Eastern Plumas Health Care to ensure we weren’t susceptible to attacks. Looking back, prior to that partnership, we had a lot of risks on campus. I’m glad nothing happened, but I’m even more proud that after implementing those systems, we’ve avoided data breaches and HIPAA violations throughout our five-year partnership.
We always get a technician or an engineer that can solve the problem remotely and we have very little downtime. We’ve had a couple of times where we have had an employee that is prevented from working, and when we call in and we escalate quickly, we always have someone readily available to solve the problem.
ISO/IEC 27001 is the international standard for information security management, published by the International Organization for Standardization. It does not hand you a list of technology to buy. It requires you to run aninformation security management system, an ISMS: a defined scope, a risk assessment, controls chosen and justified, internal audits, and management review. Certification means an accredited certification body has audited that system and found it conforms. The certificate is issued by that body, not by your IT provider and not by your consultant.
Source: ITS, "What Does the ISO 27001 Update Mean for Your Business?", published 2023-02-07.
Ask them for the wording, because they are different deliverables. ISO 27001 is an international certificate awarded by an accredited body for a management system. SOC 2 is an American attestation report written by a CPA firm about a window of time. Buyers in Europe usually ask for ISO 27001; buyers in the United States usually ask for SOC 2. If both are being asked for, the control work overlaps heavily and the evidence can be collected once. The audits cannot. If you want the detail of what a SOC 2 report contains, we have written it up.
No, and no managed service provider can. Certification has to come from an accredited certification body that is independent of the people running your controls, which is the whole point of it being worth something to your buyer. What ITS does is the rest: scope the system, run the gap assessment, build the ISMS, operate the day to day controls, prepare the evidence, and coordinate with your auditor through the audit. Anyone who tells you they will certify you has misunderstood the standard, or is hoping you have.
The management system clauses barely moved. Annex A was rebuilt: 114 controls became 93, reorganized from fourteen groupings into four themes, Organizational, People, Physical and Technology. Eleven controls are new, and they are the modern ones: threat intelligence, cloud services, data masking, information deletion, data leakage prevention, monitoring activities, web filtering, secure coding, configuration management, ICT readiness for continuity, and physical security monitoring. If you are starting now, you start on the current version and none of this is migration work.The full breakdownis on our blog.
Source: same ITS post. Note that post attributes Annex A to ISO 27002; the controls are published in ISO/IEC 27001 Annex A with implementation guidance in ISO/IEC 27002, and this answer uses the correct attribution.
They overlap and they are not interchangeable. ISO 27001 certifies an information security management system for any organization in any sector. TISAX is the automotive industry's own assessment and exchange mechanism, built on an information security questionnaire derived from ISO 27001 and required by many manufacturers of their suppliers. If an original equipment manufacturer asked you for TISAX, ISO 27001 alone will not satisfy them. We have written the comparison up in full.
On its own, no. ISO 27001 is a voluntary standard, and nobody fines you for not holding it. What makes it feel mandatory is commercial: an enterprise customer, an international partner, a procurement questionnaire or an insurer asks for it, and the deal waits. That is a real deadline, but it is your customer's, not a regulator's. Worth knowing before you budget for it, because it changes who inside your business owns the project and how it gets justified.
A scoping conversation, an honest read on your gaps against the clauses and Annex A, and a written plan. No obligation at the end of it.