ISO/IEC 27001

ISO/IEC 27001 Information Security Management System Consultancy

Puts information security under a managed system, with risks assessed and controls justified.

Saudi Arabia: serving clients in Riyadh, Jeddah, Dammam, Jubail, Yanbu and the industrial cities

  • Enterprise Sales Unblocked
  • Cyber Insurance Terms
  • Breach Cost Contained
  • Leaver Risk Handled

Free · 15 minutes · assured discount

Score your readiness out of 100 before you spend a rupee.
Know exactly what to ask for — instead of being sold a package.

Practice area
Cyber Security
Industries
9
Delivery
Onsite, remote, hybrid

Get a quotation

Tell us who is asking for the certification and by when.

What are you looking for?

We reply within one working day. Your details stay with our consultants.

Why expert advice is worth having

Organisations rarely fail ISO/IEC 27001 because the standard is hard. They fail because the evidence does not match what the auditor asks for.

1

It has to survive after we leave

A ISO/IEC 27001 system that only works while a consultant is on site fails its first surveillance audit. We build it so your own people can run it, and train them to do so.

2

Surveillance never stops

A ISO/IEC 27001 certificate is the start of a three year cycle, not the end of a project. Building for the surveillance audits from day one costs far less than rebuilding before each one.

3

A date you can actually commit to

Knowing which parts of ISO/IEC 27001 can be compressed and which cannot is the difference between meeting a tender deadline and explaining why you missed it.

4

Experience across sectors

Having implemented ISO/IEC 27001 in very different operating environments, we can tell you quickly which of your worries are real and which are inherited from someone else's situation.

Quick question about ISO/IEC 27001? Message us and get an answer today.

What ISO/IEC 27001 is worth to you

Certification is a commercial decision before it is a technical one. This is where the return usually shows up.

Enterprise Sales Unblocked

Large clients send security questionnaires that stall deals for months, and a certificate answers most of those questions in one document.

Cyber Insurance Terms

Insurers underwrite certified organisations on better terms because documented controls reduce the loss they expect to have to pay out.

Breach Cost Contained

Defined incident response means a compromise is spotted and closed within hours instead of being reported to you by a customer.

Leaver Risk Handled

Access revocation and asset return become routine process, so departing employees stop walking out with client data on personal devices.

Industries where ISO/IEC 27001 applies

Open a sector to see every standard it is usually asked for.

Working to a deadline on ISO/IEC 27001? Send us the date.

Send us the details

See the documentation

Look at how it is structured before you commit

Documentation for ISO/IEC 27001 fails when it describes a company nobody recognises. Ours maps clause by clause onto how you actually operate, so the manual, the procedures and the record formats hang together and an auditor can follow the thread. Book a demo and we will show you that structure on screen, not describe it.

ISO/IEC 27001 in detail

The documents ISO/IEC 27001 asks you to have

A standard does not ask for a library. It asks for evidence that you decide things deliberately and can show how. This is what an auditor will look for on a ISO/IEC 27001 system — specific to the standard first, then the records every management system needs.

  • Information security policy and topic-specific policies beneath it
  • Scope of the information security management system, including interfaces and dependencies
  • Risk assessment and risk treatment methodology, and the results of applying it
  • Statement of Applicability — every Annex A control, whether it applies, and why
  • Risk treatment plan with owners and dates
  • Asset inventory and information classification scheme
  • Access control records, and evidence of access reviews
  • Supplier security agreements and monitoring records
  • Incident management records, and business continuity test results
  • Roles, responsibilities and authorities, written down and known to the people holding them
  • Competence and training records for anyone whose work affects the system
  • Internal audit programme, audit reports and the findings raised
  • Management review minutes, showing what was decided rather than that a meeting happened
  • Nonconformity and corrective action records, with root cause and effectiveness checked
  • Document and record control — what is current, who approved it, how long it is kept

Length is not compliance. A procedure nobody follows is worse than no procedure, because an auditor will find the gap between the two. Our test is whether the person who has to do the job recognises their own work in it.

How to start

The first instinct is usually to look for a template pack. It is the most expensive way to begin, because a system written before anybody looked at how the work is actually done has to be re-written once somebody does. Start here instead.

  • Establish what is being asked, and by whom. A customer, a tender, a regulator and a parent company each want something slightly different, and the answer decides the scope.
  • Fix the scope in writing — which sites, which activities, which products. Scope drives cost more than any other single decision, and a scope widened after the audit is booked is re-work.
  • Have a gap assessment done against ISO/IEC 27001, on evidence rather than on a questionnaire. You can score yourself first with the free readiness checklist on this site; the expert assessment is what turns that score into a plan.
  • Appoint somebody internally who owns it. Not necessarily full time, but named, and senior enough to get decisions made.
  • Document only what the gap assessment showed is missing, in the words the people doing the work already use.
  • Train, then run the system long enough to generate real records. Three months of genuine records cannot be produced in a fortnight, and this is the step organisations try hardest to skip.
  • Audit yourself, hold a management review that actually decides something, then book the certification audit.

Tell us what you need for ISO/IEC 27001

Who is asking for it, how many sites, and by when. The more specific you are, the more useful our first reply will be.

How to choose a certification body

The body you choose matters more than most people expect, and for a reason that has nothing to do with price: their accreditation is what makes your certificate mean something to the party that demanded it.

Four things decide it. Accreditation: the body should be accredited for your standard and your industry by a recognised accreditation body, and the certificate should carry that mark. Sector competence: an auditor who has audited your industry asks better questions and wastes less of your time. Recognition: ask the customer or tender that triggered this whether they name particular bodies. Cost and diary: audit days are set by your headcount and scope, so quotes should be comparable — and if one is far cheaper, look at the audit days before the price.

Among the bodies most widely recognised, in no particular order: BSI, TÜV, SGS, SIS Certifications, Intertek, DNV, BVQI.

MSCi works with a pool of accredited certification bodies rather than one. That is a commercial advantage to you, and worth being plain about why: bodies differ in audit-day rates, in travel cost to your location, in how quickly they can get an auditor to you, and in which sectors they are accredited for. Having several to approach means we can put your scope in front of the ones that fit it and bring you back comparable quotes, instead of you taking the first number offered.

What it does not change is the audit. We cannot influence a finding and would not try — the body's independence is the entire value of the certificate, and any consultancy offering otherwise is selling you something worthless. We prepare you so that the audit is uneventful, and the body decides.

Note also that whoever builds your management system must not be the body that certifies it. Accreditation rules prohibit it, which is why we prepare and never certify.

What ISO/IEC 27001 is usually taken with

Few organisations stop at one standard, and the second costs far less than the first — the clauses that take longest are the ones they share. Where ISO/IEC 27001 sits next to something else, this is what carries over.

  • ISO/IEC 27701 consultancy — extends this standard for privacy: the same risk method, the same Statement of Applicability, with personal data added.
  • ISO 22301 consultancy — covers the continuity that Annex A only asks you to consider, and supplies the impact analysis behind it.
  • ISO/IEC 42001 consultancy — applies the same management system pattern to AI, and reuses your risk assessment and supplier controls.
  • ISO 9001 consultancy — shares clauses 4 to 10 with this standard, so context, leadership, competence, internal audit and management review are built once and audited together.

Certified to more than one, you hold a single management system with one set of objectives, one internal audit programme and one management review — audited in one visit. Run as separate systems they cost roughly twice as much to keep, which is the usual reason a second certificate feels harder than it was.

Scroll inside the panel for the rest of it.

Free · 15 minutes · assured discount

Score your ISO/IEC 27001 readiness out of 100

Answer the questions an auditor would ask and see where you stand before anybody quotes you a price.

Have it as a document

Send me the ISO/IEC 27001 checklist

The questions an auditor asks, to work through in your own time.

The route to your ISO/IEC 27001 certificate

  1. 1Gap analysis
  2. 2Documentation
  3. 3Training
  4. 4Implementation
  5. 5Internal audits
  6. 6Closure of gaps
  7. 7Management review
  8. 8Certification audit
  9. 9Surveillance audits

Would half an hour on ISO/IEC 27001 with a consultant be useful?

ISO/IEC 27001 questions we are asked most

What will we have to put in place for ISO/IEC 27001?

The requirements fall into four buckets: define it, document it, run it long enough to generate records, then audit it yourself before the certification body does.

What is a realistic timeline for ISO/IEC 27001?

Two to four months is the honest range for most organisations, measured from gap analysis to the certification audit. What moves it is how much you already document, how quickly people can be released for training, and the certification body's own diary.

Do you issue the ISO/IEC 27001 certificate yourselves?

No, and no consultant should. The certificate comes from an independent accredited certification body after their own audit. We prepare you to pass it and we are there on the day to close findings. That separation is exactly what makes the certificate worth holding.

What does ISO/IEC 27001 consultancy cost?

We price per engagement rather than per seat, because a single site business and a five site group need very different amounts of work. You get a written proposal covering scope, audit days and fees before committing to anything.

Which industries need ISO/IEC 27001?

We map ISO/IEC 27001 to 9 sectors and it sits in our cyber security practice. Organisations usually arrive because a specific buyer, regulator or tender committee has asked. Tell us who is asking and we will confirm whether this is the standard that satisfies them.

Do you have to visit our premises?

Both, and hybrid. Gap analysis and audit day usually benefit from someone physically present, while documentation and training work perfectly well remotely. We fit delivery to your sites and schedule rather than the reverse.

Prefer to just ask someone about ISO/IEC 27001 rather than fill in a form?

Ready to start on ISO/IEC 27001?

Book a short session and we will tell you what is involved, how long it takes and what it costs.