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. 9.2 to 9.6, the additions marked “IS”
For Clauses 9.2 to 9.6, ISO/IEC 17021-1 applies. Objectives, scope and team are in 17021-11, stage 1 and stage 2 in 17021-12, conduct and the report in 17021-13, the decision in 17021-15, surveillance, recertification and special audits in 17021-16, suspension, withdrawal and reduction in 17021-17. The IS addition is set out here. 9.6.1 and 9.6.5 contain no IS addition.
IS 9.2.1 requires the audit objectives to include determining the effectiveness of the management system, in order to ensure that the client has implemented applicable controls on the basis of the risk assessment and has achieved the specified information security objectives.
IS 9.2.2 requires the audit team to be formally appointed and provided with the appropriate working documents. The assignment to the team shall be clearly defined and made known to the client. An audit team may consist of one person, provided that person fulfils all the criteria of 7.1.2.1. “May”. The criteria are in 27006-02.
The requirements of 7.1.2 apply. For surveillance and special audits, only the requirements that are relevant to the planned surveillance and the planned special audit apply. In selecting and leading the team, the body shall ensure that the competence brought to each assignment is adequate. The team shall have adequate technical knowledge of the specific activities within the ISMS scope for which certification is sought and, where relevant, of associated processes and their potential information-security risks. Technical experts may fulfil this function. “May”. The team shall understand the client sufficiently to conduct a reliable certification audit of its ISMS, given the scope and context of the ISMS in the organization in handling the information-security aspects of its activities, products and services. It shall adequately understand the legal and regulatory requirements that apply to the client's ISMS. A note says adequate understanding does not mean an in-depth legal background. The clause names no particular law.
IS 9.2.3 requires the audit plan for ISMS audits to take the determined information-security controls into account. The plan shall identify the network-assisted audit techniques used during the audit, as far as appropriate. Such techniques may include, for example, teleconferences, web meetings, interactive web-based communication and remote electronic access to ISMS documentation or to ISMS processes. “May”. The focus of such techniques should be to increase the effectiveness and efficiency of the audit, and it should support the integrity of the audit process. “Should”.
On the timing of the audit there is a recommendation. The body should agree with the organization to be audited the timing that best shows the full extent of the organization. The consideration could include season, month, day or days and shift, as far as appropriate. “Should” and “could”.
IS 9.3.1.1 on stage 1 requires the body to obtain documentation on the design of the ISMS that covers the documentation required by ISO/IEC 27001. It shall gain a sufficient understanding of the design of the ISMS, in the context of the client's organization, of the risk assessment and risk treatment including the determined controls, of the information security policy and the objectives, and in particular of the client's readiness for the audit. The text says this makes it possible to plan for stage 2. The results of stage 1 shall be documented in a written report. The body shall review the stage 1 report before it decides on proceeding to stage 2 and before it selects the members of the stage 2 team with the needed competence. It shall draw the client's attention to the further kinds of information and records that may be required for the detailed examination in stage 2. “May”.
IS 9.3.1.2.1 says: On the basis of the findings documented in the stage 1 report, the body develops an audit plan for conducting stage 2. This sentence does not set a “shall”. In addition to assessing the effective implementation of the ISMS, the objectives of stage 2 are a single letter: to confirm that the client adheres to its own policies, objectives and procedures.
IS 9.3.1.2.2 says that, for this, the audit shall be directed at eight subjects of the client. Leadership and commitment of top management to the information security policy and the information security objectives. The documentation requirements listed in ISO/IEC 27001. The assessment of information-security-related risks and that the assessments produce consistent, valid and comparable results when they are repeated. The determination of control objectives and controls on the basis of the information-security risk assessment and risk treatment processes. The English wording is “control objectives and controls”. That is the language of the edition to which this PDF is bound. Information security performance and the effectiveness of the ISMS, evaluated against the information security objectives. The correspondence between the determined controls, the statement of applicability and the results of the risk assessment and risk treatment, and the information security policy and objectives. The implementation of the controls, with a reference to Annex D, taking into account the external and internal context and the associated risks, and the organization's monitoring, measurement and analysis of the information security processes and controls, in order to determine whether the controls are implemented and effective and meet their stated information security objectives. Programmes, processes, procedures, records, internal audits and reviews of the effectiveness of the ISMS, in order to ensure that these can be traced back to decisions of top management and to the information security policy and objectives. What Annex D does on this and where it ends is in 27006-07. The requirements of the 2022 edition on risk assessment, risk treatment and the statement of applicability are in 27001-04 and 27001-05. This focus list does not state them.
IS 9.4 requires documented procedures for the initial certification audit of a client's ISMS in accordance with ISO/IEC 17021-1 and for surveillance and recertification audits in accordance with ISO/IEC 17021-1 on a periodic basis, for continuing conformity with the relevant requirements and for verifying and recording that a client takes timely corrective actions to resolve all nonconformities.
The body, represented by the audit team, shall require evidence from the client that the assessment of information-security-related risks is relevant and appropriate to the operation of the ISMS within the ISMS scope. It shall determine whether the client's procedures for the identification, examination and evaluation of information-security-related risks and the results of their implementation are consistent with the client's policy, objectives and targets. “Objectives and targets”. It shall also determine whether the procedures used in the risk assessment are sound and properly implemented.
IS 9.4.3 adds to the reporting requirements in ISO/IEC 17021-1, 9.4.8. The audit report shall provide the following information or refer to it. An account of the audit including a summary of the document review. An account of the certification audit of the client's information-security risk analysis. Deviations from the audit plan, for example more or less time for certain planned activities. The scope of the ISMS.
The report shall be detailed enough to enable and support the certification decision. It shall contain: the significant audit trails followed and the audit methods used, with a reference to 9.1.3.2; findings, positive, for example notable features, and negative, for example potential nonconformities; comments on the conformity of the client's ISMS with the certification requirements, with a clear statement of nonconformity, a reference to the version of the statement of applicability and, where applicable, a useful comparison with the results of previous certification audits of the client.
Completed questionnaires, checklists, observations, logs or auditor notes may form an integral part of the audit report. “May”. If these means are used, these documents shall be submitted to the body as evidence to support the certification decision. Information on the samples assessed in the audit shall be included in the audit report or in other certification documentation. The report shall consider the adequacy of the internal organization and of the procedures adopted by the client, insofar as they give confidence in the ISMS.
In addition to ISO/IEC 17021-1, 9.4.8, the report shall cover: a summary of the most important findings, positive as well as negative, on the implementation and effectiveness of the ISMS requirements and of the information-security controls, and the audit team's recommendation as to whether the client's ISMS should be certified or not, with information supporting that recommendation. The “should” stands in the recommendation as to whether it should be certified. The “shall” requires the report to cover this recommendation and its support.
IS 9.5 requires that the certification decision, in addition to the requirements of ISO/IEC 17021-1, be based on the audit team's certification recommendation as it stands in the certification audit report, see 9.4.3. The persons or committees that decide on granting should not normally overturn a negative recommendation of the audit team. “Should not normally”. If this case occurs, the body shall document and justify the basis of the decision to overturn the recommendation. Certification may not be granted to the client until sufficient evidence shows that arrangements for management reviews and internal ISMS audits are implemented, are effective and are maintained.
IS 9.6.2 requires that the procedures for surveillance audits be consistent with the procedures for the certification audit of the client's ISMS, as described in this International Standard. The purpose of surveillance is to verify that the approved ISMS continues to be implemented, to consider the consequences of changes to this system brought about by changes in the client's operations, and to confirm continued compliance with the certification requirements.
Surveillance audit programmes shall at least cover: the elements of system maintenance, such as the information-security risk assessment and maintenance of the controls, internal ISMS audit, management review and corrective action; communications from external parties as required by the ISMS standard ISO/IEC 27001 and other documents required for certification; changes to the documented system; areas subject to change; selected requirements of ISO/IEC 27001; other selected areas, as far as appropriate.
Each surveillance by the body shall at least examine: the effectiveness of the ISMS with regard to achieving the objectives of the client's information security policy; the functioning of the procedures for the periodic evaluation and review of compliance with relevant information-security legislation and regulations; changes to the determined controls and the resulting changes to the statement of applicability; implementation and effectiveness of the controls in accordance with the audit programme. The sentence on legislation and regulations names no particular law.
The body shall be able to adapt its surveillance programme to the information-security issues related to risks and impacts on the client, and shall justify this programme. Surveillance audits may be combined with audits of other management systems. “May”. The reporting shall clearly identify the aspects relevant to each management system. During the surveillance audits the bodies shall examine the records of appeals and complaints brought before the body and, where a nonconformity or a failure to meet the certification requirements comes to light, that the client has investigated its own ISMS and its procedures and has taken appropriate corrective actions.
A surveillance report shall in particular contain information on the closure of previously identified nonconformities, the version of the statement of applicability and important changes since the previous audit. The reports arising from surveillance shall at least complement one another so that they cover the requirements of 9.6.2.1.1 and 9.6.2.1.2 in total. “Build up to cover in totality”. The obligation to examine the four points of 9.6.2.1.2 at each surveillance remains alongside that.
IS 9.6.3 requires that the procedures for the recertification audit be consistent with the procedures for the initial certification audit of the client's ISMS, as described in this International Standard. The time allowed for implementing the corrective action shall match the severity of the nonconformity and the associated information-security risk. The time limits and the cycle from ISO/IEC 17021-1, 9.6.3 remain that standard, explained in 17021-16.
IS 9.6.4 requires that the activities for special audits be subject to a special provision when a client with a certified ISMS makes significant changes to its system or when other changes occur that could impair the basis of its certification. “Could”. What ISO/IEC 17021-1, 9.6.4 requires on extension and short-notice audits remains that standard. This PDF does not fill in the content of the “special provision” any further.
Records: Stage 1 ends in a written report, which the body reviews before the decision on stage 2. For initial certification as well as for surveillance and recertification, the body needs documented procedures, including the verification and recording of timely corrective actions. The audit report has the content named in 9.4.3. If a negative recommendation of the team is overturned, the basis and the justification are to be documented. Surveillance reports name in particular the closure of earlier nonconformities, the version of the statement of applicability and important changes.
Not in this text: the certification cycle, the distinction between major and minor nonconformities, the six-month rule after stage 2 and the rules on suspension and withdrawal. That remains ISO/IEC 17021-1. Also the content of Annex D as a checklist and any transfer of the control objectives onto Annex A of 2022 stay outside. Complaints follow in 27006-06.