Explanations of ISO/IEC 27006:2015
The source is ISO/IEC 27006:2015(E), third edition, 2015-10-01. Title: Information technology — Security techniques — Requirements for…
Read articleISO/IEC 27006:2015
Version note. In the document itself, ISO/IEC 17021-1:2015 and ISO/IEC 27001:2013 are the normative references. Annex D reviews the controls of 27001:2013. Annex D is not applied to 27001:2022.
For: EA
Source: ISO/IEC 27006:2015(E), English. Annex D (informative), in connection with 9.3.1.2.2 g)
The heading of Annex D reads: Guidance for review of implemented ISO/IEC 27001:2013, Annex A controls. The annex is informative.
D.1 says the implementation of the controls that the client has determined as needed for the ISMS, in accordance with the statement of applicability, shall be examined in stage 2 of the initial audit and at surveillance or recertification. “Shall”. The sentence refers to 9.3.1.2.2 g), see 27006-05. There stands the requirement of the main text that the audit be directed at the implementation of the controls, with a reference to Annex D. D.1 repeats this “shall” in the informative annex and binds it to that clause. The evidence the body collects shall be sufficient to draw a conclusion on whether the controls are effective. How a control is expected to work may, for example, be specified in procedures or policies of the client. “May, for example”.
D.1.1 describes the quality of evidence. The best quality comes from observation by the auditor. Evidence can come from the results of performing a control, from direct examination or repeated performance by the auditor, and from interviews of persons who perform work under the control of the organization and of contractors, combined with determining whether that is factually the case. “Can”. The PDF names examples of this: a locked door is locked, persons sign confidentiality agreements, the asset inventory exists and contains the assets observed, system settings are appropriate, printouts of access rights and of processing authorizations are signed by the person responsible, records of the closure of incidents, minutes of meetings, attempts to carry out tasks that are supposed to be prohibited by the controls, determining whether software against malicious code is installed and up to date. These are examples in the annex for the quality of evidence. An obligation to use each of these methods for every control does not stand in D.1.1. The examples are not turned into a checklist of controls here.
D.2.1 says Table D.1 gives pointers for reviewing the implementation of the controls listed in ISO/IEC 27001:2013, Annex A, and for collecting audit evidence of their performance during the initial audit and later audits. The next sentence reads: “The Table is not intended to provide guidance for reviewing controls other than those in ISO/IEC 27001:2013, Annex A.” The table is a pointer for the controls of Annex A of the 2013 edition. It is not a checklist for Annex A of ISO/IEC 27001:2022. The controls of the 2022 edition are explained in 27001-13 and the following articles from that PDF. A mapping of the rows of Table D.1 onto these controls does not stand in the present PDF and is not made here. Table D.1 is not copied. The German ISO/IEC 27002:2017 is not used to transfer the table onto the 2022 edition.
D.2.2 explains the columns “Organizational control” and “Technical control”. An “X” shows whether the control is organizational or technical. Some controls are both, and then entries can stand in both columns. The crosses are not reproduced here. Evidence of the performance of organizational controls can be collected by examining the records of performance, through interviews, observation and physical inspection. Evidence of the performance of technical controls can often be collected by system testing or by special audit or reporting tools. “Can”.
D.2.3 defines system testing as direct examination of information systems, for example examination of system settings or configuration. The auditor's questions can be answered at the system console or by evaluating test tools. If the client uses a computer-supported tool known to the auditor, it can support the audit, or the results of an assessment by the client or its subcontractors can be examined. “Can”. The table contains two categories for the examination of technical controls. “Possible”: a system test is possible for assessing the implementation, but dispensable in an ISMS audit. “May not be necessary”. “Recommended”: a system test is usually necessary in an ISMS audit. “Usually necessary”. Both explain columns of an informative table on the controls of 2013. A note says that in this annex “system” means an information system, unless something else is indicated.
D.2.4 defines visual inspection so that these controls usually require a visual inspection on site in order to assess their effectiveness. Examining the documentation on paper or through interviews is not sufficient for that. The auditor should examine the control at the place where it is implemented. “Should”.
D.2.5 says the column “Audit review guidance” provides possible focal points for assessing the control, as a further pointer for the auditor. The column is not copied.
Not in this text: Table D.1, a checklist for Annex A of ISO/IEC 27001:2022, a mapping of the fourteen groups from 7.1.2.1.3 onto the controls of 2022, and any ICB-internal audit rule for certifications to the 2022 edition. No edition of ISO/IEC 27006 that references ISO/IEC 27001:2022 is available for that.