ISO 27001 Documented Information Explained Simply

Home / ISO 27001 Tutorials / ISO 27001 Documented Information Explained Simply

Introduction

In this tutorial we are going to cover ISO 27001  Documented Information.

    You will learn

    • What it is ISO 27001 Documented Information
    • How to implement ISO 27001 Documented Information

    Watch

    If you prefer to watch rather than read you can watch: How to implement ISO 27001 Clause 7.5 Documented Information | Step-by-Step Guide

    The Ultimate ISO 27001 Toolkit

    All of the ISO 27001 Documentation you need is in the ultimate ISO 27001 Toolkit.

    Designed to fast track and provided everything that is required in the format that is required.

    DO IT YOURSELF ISO27001

    Stop Spanking £10,000’s on Consultants and Platforms

    ISO 27001 Toolkit Business Edition

    ISO 27001 Documented Information General

    The Requirement

    the organisation’s Information Security Management System (ISMS) shall include documented information required by this document  and documented information determined by the organisation as being necessary for the effectiveness of the information security management system.

    How to implement it

    Brilliant! Right, so what does it say? It says you need some documents but you need the documents that you need. Now what we have is the ISO 27001 Toolkit, the ultimate ISO 27001 toolkit that actually contains all of the documents that you do need, that the standard itself, in the various Clauses that it goes through requires of you, I provide that for you. So, you can take a look at the ISO 27001 toolkit and if you want to know what those documents are rather than me regurgitate existing content take a look at this particular video, here, which is a walk through, it’s The Grand Tour of the ISO 27001 Toolkit that basically talks you through, well, very basically talks you through the structure of what the documents are, how they hang together and it shows you the exact documents that you need.

    So, the point here is it wants the documents required by the management system. You can create them however, if you want the ISO 27001 toolkit that I provide you, it does it in the most effective and efficient way. At the time of writing, it’s been downloaded thousands of times and used over many, many years. It is the most efficient way but you can do it however you want.

    It says that we’re going to have information determined by us as being necessary. Now actually some of the documentation is necessary to affect the management system itself but it does give you some leeway. I mean you could always argue we didn’t determine it was necessary and you could still pass. I mean good luck with that but you could.

    The notes that it gives us here is the extent of the documented information can differ depending on size. So, it acknowledges that. Now the ISO 27001 toolkit meets businesses and organisations of all sizes, from two, three people all the way up to hundreds and thousands of employees and many of the clients fall into all of those categories but you are going to have your documentation based on

    • your size
    • your activity
    • your products,
    • your services
    • the complexity of who you are
    • your processes
    • and the competency of persons.

    I do like the standard, right, I mean technically we could say we didn’t deem it necessary and we’re not competent. I mean it’s never going to happen but you could.

    What I would say is to implement this, get a copy of the ISO 27001 toolkit. If you don’t get the ISO 27001 toolkit watch the video on the ISO 27001 toolkit walkthrough, see the documents that you do need, every document is available on YouTube with a guide so worst case tappy-tappy you type it in and you could write it yourself but you’re going to need that documentation.

    ISO 27001 Creating and Updating Documented Information

    The Requirement

    When creating and updating documented information the organisation shall ensure appropriate identification and description – e.g. a title, a date, an author or a reference number. It will ensure appropriate format, language, software, version, graphics and media and it will review and approve for suitability and adequacy.

    How to implement it

    So, what is it saying? It’s saying have some documents, which you’re going to have. If you followed any of my videos you see that all of my documents have

    • Version Control
    • Classification
    • Document Owner
    • Last Review Date.

    So, you’re going to make sure that you have all that in place. You’re going to make sure that you review and approve your documentation on a periodic basis, at least annually, so nice, good common sense approach to things within there.

    Then when it comes to the control of documented information so …

    Documented information required by the information security management

    The Requirement

    Documented information required by the information security management system (ISMS) and by this document shall be controlled to ensure it is available and suitable for use, no brainer, where and when it is needed, of course, and it is adequately protected, of course, from loss of confidentiality and proper use or loss of Integrity. For the control of documented information the organisation shall address the following activities as applicable – distribution, access, retrieval and use, storage and preservation, control of changes and retention and disposal of. Documented information of external origin determined by the organisation to be necessary for the planning and operation of the information security management system (ISMS)  shall be identified as appropriate and controlled.

    How to implement it

    There’s a lot to go at there. Control your documentation, make sure you’re putting it on your document storage, make sure that you’re following your usual access control, make sure you’re backing it up, is appropriate, make sure that your version control is correct, that you’re keeping your revision history. Nice, easy, control of documentation.

    Documents and Record Policy

    So, what I want to do is I’m going to have a little look through the documents and records policy that actually sets all of that out for you. So, when we go through the document and records policy what you’re going to see is that we have a purpose, that the purpose of the policy is the control of documents and records in the information security management system (ISMS). You’re going to see the scope of that, the principle of that, then what you see in our policy is we talked to the creating and updating of documents, so, when creating and updating documented information the company ensures the appropriate identification, description and the format. We talk in our policy about the availability of documents, so basically, we’re taking the requirements of the standard and we’re putting them into a policy, so, all of that is available for you. I’m not going to read that policy for you, I’m going to show you that, I’m going to highlight that, I’m going to say go to the link and download that.

    Implementation Summary

    What I would say here is a full page of information not really telling you very much, you know how to manage documents, you know how to store them, you know how to grant access, you know how to back them up. Disaster Recovery you know that. What might be new to you here is document markup with the Version Control, the classification, the document owner. That’s fine make sure that your documents have that, make sure that you have a process of approval in place and then when it comes to this particular Clause you are going to be golden.

    Get a copy of the ISO 27001 toolkit. Look through the ultimate guide, the ISO 27001 Documents Grand Tour Video that shows you what documents that you need, as a minimum grab yourself a copy of the document and records policy that shows you a bare minimum what you need to do and you are going to be golden.

    My name is Stuart Barker. I am the ISO 27001 Ninja. That was ISO 27001 Clause 7.5 Documented Information. Until the next tutorial peas out

    ISO 27001:2022 requirements

    Organisational Controls - A5

    ISO 27001 Annex A 5.1 Policies for information security

    ISO 27001 Annex A 5.2 Information Security Roles and Responsibilities

    ISO 27001 Annex A 5.3 Segregation of duties

    ISO 27001 Annex A 5.4 Management responsibilities

    ISO 27001 Annex A 5.5 Contact with authorities

    ISO 27001 Annex A 5.6 Contact with special interest groups

    ISO 27001 Annex A 5.7 Threat intelligence – new

    ISO 27001 Annex A 5.8 Information security in project management

    ISO 27001 Annex A 5.9 Inventory of information and other associated assets – change

    ISO 27001 Annex A 5.10 Acceptable use of information and other associated assets – change

    ISO 27001 Annex A 5.11 Return of assets

    ISO 27001 Annex A 5.11 Return of assets

    ISO 27001 Annex A 5.13 Labelling of information

    ISO 27001 Annex A 5.14 Information transfer

    ISO 27001 Annex A 5.15 Access control

    ISO 27001 Annex A 5.16 Identity management

    ISO 27001 Annex A 5.17 Authentication information – new

    ISO 27001 Annex A 5.18 Access rights – change

    ISO 27001 Annex A 5.19 Information security in supplier relationships

    ISO 27001 Annex A 5.20 Addressing information security within supplier agreements

    ISO 27001 Annex A 5.21 Managing information security in the ICT supply chain – new

    ISO 27001 Annex A 5.22 Monitoring, review and change management of supplier services – change

    ISO 27001 Annex A 5.23 Information security for use of cloud services – new

    ISO 27001 Annex A 5.24 Information security incident management planning and preparation – change

    ISO 27001 Annex A 5.25 Assessment and decision on information security events 

    ISO 27001 Annex A 5.26 Response to information security incidents

    ISO 27001 Annex A 5.27 Learning from information security incidents

    ISO 27001 Annex A 5.28 Collection of evidence

    ISO 27001 Annex A 5.29 Information security during disruption – change

    ISO 27001 Annex A 5.31 Identification of legal, statutory, regulatory and contractual requirements

    ISO 27001 Annex A 5.32 Intellectual property rights

    ISO 27001 Annex A 5.33 Protection of records

    ISO 27001 Annex A 5.34 Privacy and protection of PII

    ISO 27001 Annex A 5.35 Independent review of information security

    ISO 27001 Annex A 5.36 Compliance with policies and standards for information security

    ISO 27001 Annex A 5.37 Documented operating procedures 

    Technology Controls - A8

    ISO 27001 Annex A 8.1 User Endpoint Devices

    ISO 27001 Annex A 8.2 Privileged Access Rights

    ISO 27001 Annex A 8.3 Information Access Restriction

    ISO 27001 Annex A 8.4 Access To Source Code

    ISO 27001 Annex A 8.5 Secure Authentication

    ISO 27001 Annex A 8.6 Capacity Management

    ISO 27001 Annex A 8.7 Protection Against Malware

    ISO 27001 Annex A 8.8 Management of Technical Vulnerabilities

    ISO 27001 Annex A 8.9 Configuration Management 

    ISO 27001 Annex A 8.10 Information Deletion

    ISO 27001 Annex A 8.11 Data Masking

    ISO 27001 Annex A 8.12 Data Leakage Prevention

    ISO 27001 Annex A 8.13 Information Backup

    ISO 27001 Annex A 8.14 Redundancy of Information Processing Facilities

    ISO 27001 Annex A 8.15 Logging

    ISO 27001 Annex A 8.16 Monitoring Activities

    ISO 27001 Annex A 8.17 Clock Synchronisation

    ISO 27001 Annex A 8.18 Use of Privileged Utility Programs

    ISO 27001 Annex A 8.19 Installation of Software on Operational Systems

    ISO 27001 Annex A 8.20 Network Security

    ISO 27001 Annex A 8.21 Security of Network Services

    ISO 27001 Annex A 8.22 Segregation of Networks

    ISO 27001 Annex A 8.23 Web Filtering

    ISO 27001 Annex A 8.24 Use of CryptographyISO27001 Annex A 8.25 Secure Development Life Cycle

    ISO 27001 Annex A 8.26 Application Security Requirements

    ISO 27001 Annex A 8.27 Secure Systems Architecture and Engineering Principles

    ISO 27001 Annex A 8.28 Secure Coding

    ISO 27001 Annex A 8.29 Security Testing in Development and Acceptance

    ISO 27001 Annex A 8.30 Outsourced Development

    ISO 27001 Annex A 8.31 Separation of Development, Test and Production Environments

    ISO 27001 Annex A 8.32 Change Management

    ISO 27001 Annex A 8.33 Test Information

    ISO 27001 Annex A 8.34 Protection of information systems during audit testing