ISO & GRC consulting across India since 2003 Find consultants near you
Home / ISO Certification Blog / ISO/IEC 27001 & information security / ISO/IEC 27001 documents required: what you must have and what you can skip
ISO/IEC 27001 & INFORMATION SECURITY / GUIDE

ISO/IEC 27001 documents required: what you must have and what you can skip

A clear split between the documents ISO/IEC 27001 insists on and the ones you write only because your risks call for them.

TOPIC
ISO/IEC 27001 & information security
READING TIME
5 min
WRITTEN BY
Lakshy Content Team

Talk to a Lakshy ISO/GRC expert

Our ISO/IEC 27001 & information security expert will get back to you within one business day.

NO SPAM · NO OBLIGATION · CONFIDENTIAL
SUMMARY

The short answer

ISO/IEC 27001 requires a defined scope, an information security policy, risk assessment and treatment methods, a Statement of Applicability, a risk treatment plan and security objectives, plus records such as audit and management review results. Other documents are optional and depend on your risks.

Ask ten security managers what makes ISO/IEC 27001 hard and most will say “the paperwork”. It need not be. The standard is quite specific about what must exist in writing, and equally clear that you decide the rest. Once you know the difference, documentation becomes a tidy set of working records instead of a pile of files nobody opens.

Why documentation matters for ISO/IEC 27001

An information security management system (ISMS) has to be repeatable. If protection depends on one careful engineer remembering what to do, it disappears the day that person resigns. Written policies and procedures make good practice survive staff changes, and records give the auditor evidence that the system actually runs.

Documents also serve your customers. Many Indian IT and BPO firms are asked for proof of their controls during vendor onboarding, and a clean document set answers most of those questions quickly.

Mandatory documents and records

The standard distinguishes between documented information you must maintain (policies, plans, procedures) and records you must retain (evidence that something happened). In plain terms, a certification body will expect to see:

  • The scope of the ISMS: which locations, teams, systems and services are inside it.
  • The information security policy, approved by top management.
  • The risk assessment method and the risk treatment method: how you find, rate and decide what to do about risks.
  • The Statement of Applicability: every control from the standard’s Annex, with a yes or no on whether it applies and why.
  • The risk treatment plan, with owners for each action.
  • Your information security objectives and how you will measure them.

The records side covers evidence of staff competence, results of risk assessments, monitoring and measurement results, the internal audit programme and its findings, management review outputs, and corrective actions for nonconformities.

Documents that are useful but optional

Everything beyond that list is your call. Most organisations still choose to write down an access control policy, acceptable use rules, backup and recovery procedures, supplier security requirements, an incident response procedure and a business continuity plan. None is compulsory in itself. They exist because your risk assessment shows you need them, and the Statement of Applicability should say so.

A simple test

Ask: “If this were missing, could a new joiner or an auditor misunderstand how we protect information?” If yes, write it. If no, leave it out.

How much detail is enough

Write for the person who has to follow the document, not for the auditor. A one-page procedure that staff actually use beats a twenty-page manual that sits on a shared drive. Small teams can often keep policies short and rely on clear job roles; larger or regulated organisations will need more depth.

The standard requires that the documentation be appropriate to the size of your organisation, the complexity of its processes and the competence of its people. That sentence gives you real freedom, so use it.

Keeping documents under control

Documents only help if people read the current version. Each one should carry a title, owner, version and approval, and be reviewed at planned intervals. Make sure outdated copies are withdrawn, and that access is limited to those who need it, since some security documents are themselves sensitive.

A document management tool makes this far easier than email attachments. Effivity, the software that comes with Lakshy engagements, keeps versions, approvals and review reminders in one place.

Common documentation mistakes

  • Copying every control into a procedure “just in case”, then failing to follow half of them.
  • Writing a Statement of Applicability without a real risk assessment behind it.
  • Leaving the scope vague, so the auditor cannot tell what is covered.
  • Policies approved once and never reviewed.
  • Keeping documents but no records, so nothing proves the system is working.

A gap assessment before you start usually exposes these early, while they are cheap to fix.

Using templates without losing your identity

Templates save time, but an auditor can tell when a document describes someone else’s company. Treat a template as a skeleton. Replace generic wording with your own systems, teams, tools and customers, and delete any section that does not apply. Your risk method can follow the guidance in ISO/IEC 27005, as long as the result reflects how you really work.

Getting expert help with ISO/IEC 27001 documents

With Lakshy’s Design™ service, an experienced ISO/GRC expert develops the documents with your team and you implement them under our guidance. Where you would rather hand over the effort, Drive™ covers development and implementation end to end. Either way, the aim is a lean system that your staff recognise as their own. See the full picture on our ISO/IEC 27001 page, or read how internal audits test whether your documents match practice.

WATCH

ISO 27001 in three minutes

How to implement ISO 27001How a Lakshy project runs, step by stepFilm page and summary →
FAQS

Frequently asked questions

Is a risk register mandatory for ISO/IEC 27001?

The standard requires you to keep records of risk assessment results and a risk treatment plan. It does not insist on a file called a risk register, but most organisations use one because it neatly holds the risks, ratings, owners and treatment decisions in one place.

How many policies do I need for ISO/IEC 27001?

There is no fixed number. You must have an information security policy and the other documents the standard lists. Beyond that, write the policies your risks justify, such as access control, backup or supplier security, and explain those choices in the Statement of Applicability.

Can we keep ISO/IEC 27001 documents in electronic form only?

Yes. Documented information can be on paper or in electronic form. What matters is control: current versions are available where needed, changes are approved, access is protected and older versions are withdrawn. Many Indian organisations manage everything in a document control tool.

NEXT STEPS

Plan your next step

Talk to an experienced ISO/GRC expert about building an ISO/IEC 27001 document set that fits your business.

Related reading:

Get a free gap assessment Talk to a specialist

KEEP READING

More from the ISO Certification Blog

New guides every week on ISO standards, audits and certification in India.

Visit the blog More on ISO/IEC 27001 & information security

NEXT STEP

Start with a free ISO/IEC 27001 gap assessment.

Thirty minutes with a senior specialist, benchmarking your organisation against every requirement of the standard. No cost. No obligation.

Book My Free Session
BUYER BEWAREA certificate in 7–10 days — no audit, no implementation — is not certification. It is paper.Know the red flags →
Scroll to Top