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.1.1 to 9.1.6, Annex B (normative), Annex C (informative)
For 9.1, ISO/IEC 17021-1 applies, explained in 17021-10. The IS addition is set out here.
IS 9.1.1 requires the body to require of the client a documented and implemented ISMS that conforms to ISO/IEC 27001 and the other documents required for certification. 9.1.2 Application review contains no IS addition.
IS 9.1.3 requires the audit programme for ISMS audits to take the determined information-security controls into account.
The body's procedures may not presuppose a particular way of implementing an ISMS or a particular format for documentation and records. Certification procedures shall be directed at determining that the client's ISMS fulfils the requirements specified in ISO/IEC 27001 and the client's policies and objectives. A note refers to ISO/IEC 27007 for further auditing guidance. That edition is not available.
The body shall require the client to make all needed arrangements for access to internal-audit reports and to reports of independent reviews of information security. In stage 1 the client shall at least provide general information on the ISMS and the activities it covers, as well as a copy of the ISMS documentation required by ISO/IEC 27001 and, where required, the associated documentation.
The body may not certify an ISMS unless it has undergone at least one management review and one internal ISMS audit covering the certification scope.
The audit team shall audit the client's ISMS in the specified scope against all applicable certification requirements. Within the scope of the client's ISMS the body shall confirm that clients address the requirements of ISO/IEC 27001, 4.3. Clause 2 dates this reference to ISO/IEC 27001:2013. The wording of 4.3 of the 2022 edition is in 27001-02 and is not the sentence this PDF cites here.
Bodies shall ensure that the client's information-security risk assessment and risk treatment properly reflect its activities and extend to the boundaries of its activities as specified in the certification scope. They shall confirm that this is reflected in the scope of the client's ISMS and in the statement of applicability. The body shall check that there is at least one statement of applicability for each certification scope. Bodies shall ensure that interfaces to services or activities not fully within the ISMS scope are addressed in the ISMS to be certified and included in the client's information-security risk assessment. The PDF example is shared use of facilities with other organizations, for example IT systems, databases and telecommunications systems, or outsourcing of a business function.
The criteria against which a client's ISMS is audited shall be the ISMS standard ISO/IEC 27001. Other documents may be required for certification insofar as they are relevant to the function performed. “May”. IS 5.2 refers to this when the body describes its interpretation of the requirements of the certification-audit standards; see 27006-01.
IS 9.1.4 requires bodies to allow auditors enough time for all activities of an initial, surveillance or recertification audit. Calculation of total audit time shall include enough time for audit reporting. The body shall use Annex B to determine the audit time. A note refers to Annex C for further guidance and examples.
IS 9.1.5 permits sampling when the client has several sites that meet three criteria. All sites work under the same ISMS, which is centrally administered and audited and subject to a central management review. All sites are included in the client's internal ISMS audit programme. All sites are included in the client's ISMS management-review programme. If a client meets these three points, bodies may consider a sampling approach for the multi-site certification audit. “May”. This sentence does not contain an obligation to sample every client with several sites.
A body that wants to use the sampling approach shall have procedures ensuring the following. The initial contract review recognizes differences between sites as far as possible, so that an adequate sampling level is determined. A representative number of sites is sampled, taking thirteen aspects into account: results of internal audits of the central office and the sites; results of the management review; differences in site size; differences in the business purpose of the sites; complexity of the information systems at the different sites; differences in working methods; differences in the activities performed; differences in the design and operation of controls; possible interaction with critical information systems or with information systems that process sensitive information; differing legal requirements; geographical and cultural aspects; the risk situation of the sites; information security incidents at the individual sites. A representative sample is selected from all sites in the scope of the client's ISMS. This selection shall be based on a judgemental choice that reflects the aspects of the previous point, and shall contain a random element. Every site in the ISMS that is subject to significant risks is audited by the body before certification. The audit programme is designed in the light of the requirements named and, within the three-year period, covers representative samples of the scope of the ISMS certification. If a nonconformity is found at the central office or at an individual site, the corrective-action procedure applies to the central office and to all sites covered by the certificate.
At the end of 9.1.5.1 two further requirements stand. The audit shall address the activities of the client's central office to ensure that a single ISMS applies to all sites and provides central direction at the operational level. The audit shall address all the points previously outlined. Permission to sample remains bound to the three criteria.
IS 9.1.6 permits accepting integrated documentation, for example for information security, quality, occupational health and safety and the environment, as long as the ISMS together with the appropriate interfaces to the other systems is clearly recognizable. “May”. The ISMS audit may be combined with audits of other management systems, provided it can be shown that the audit fulfils all requirements for certification of the ISMS. All elements important to an ISMS shall appear clearly in the audit reports and be easily recognizable. The quality of the audit may not be impaired by combining the audits.
Annex B is normative and contains further requirements on ISO/IEC 17021-1, 9.1. It gives minimum requirements and pointers so that a body develops its own procedures for determining the time for certifying ISMS scopes of different size and complexity. Bodies shall determine the audit time for initial certification, surveillance and recertification for each client and each certified ISMS. Using the annex in audit planning leads to a consistent approach. In addition, audit time may be adjusted on the basis of what emerges during the audit, especially in stage 1. The PDF examples are a different assessment of the complexity of the ISMS scope, or additional sites in the scope. “May”.
The annex divides terms in B.2, requirements on the procedures for the audit steps in B.3 to B.5, and multi-site audit requirements in B.6. Examples illustrating Annex B are in Annex C.
A basic assumption is a recommendation. A calculation scheme for audit time should consider only demonstrable characteristics that can be determined, be simple enough to be applied efficiently by bodies, and complex enough to differentiate sufficiently. “Should”.
Determination of audit time is based on the figures in Table B.1, “Audit time chart”, and shall take contributing factors for adjustment into account. The cells of the table are not reproduced here. Anyone who needs a day count reads Table B.1 in the standard. In substance the table is the starting point in auditor days for the initial audit. This number covers stage 1 and stage 2 together. The rows are bands of the number of persons who perform work under the control of the organization. The table shows columns for QMS, EMS and ISMS and the reference to the adjustment factors. The starting point is changed by a positive or negative weight according to the significant factors of the ISMS scope.
B.2.1 takes as its starting point the total number of persons who perform work under the control of the organization for all shifts. A note says ISO/IEC 17021-1 calls this term personnel. Part-time persons count proportionally by the hours worked compared with a full-time person. This determination shall depend on the hours worked compared with a full-time employee.
B.2.2 sets “Auditzeit” in the table as “Auditortage”. The basis of the calculation in Annex B is an 8-hour working day.
B.2.3 defines a temporary site as a place other than the sites named in the certification documents, at which activities within the certification scope are implemented for a specified period. The range can extend from large project-management sites to small service or installation sites. “Could”. Whether such sites are to be visited and the extent of sampling should be based on an evaluation of the risks that the information-security objectives are missed because of a nonconformity arising at the temporary site. “Should”. The selected sample should reflect the range of the organization's competence needs and service variants, taking sizes and types of activities and the different stages of ongoing projects into account. For the general sample the text refers to 9.1.5.1.
B.3.1 requires that the calculation of audit time follow a documented procedure.
B.3.2 deals with remote audit activity. Where techniques such as interactive web-based collaboration, web meetings, teleconferences or electronic verification of the organization's processes are used, these activities should be identified in the audit plan, see 9.2.3, and they may be taken into account as a partial contribution to the total on-site audit time. “Should” and “may”. If the body develops an audit plan in which the remote audit activities make up more than 30 percent of the planned on-site audit time, it shall justify the audit plan and obtain a special approval of the accreditation body before implementation. A note says on-site audit time means the on-site audit time allocated to individual sites. Electronic audits of remote sites count as remote audits even if they are carried out physically on the organization's premises. The 30 percent threshold is the obligation to justify and to obtain approval. There is no prohibition of remote techniques there.
B.3.3 describes the table as the starting point for an average number of initial-audit days that experience shows is adequate for an ISMS scope with a given number of persons. The number includes stage 1 and stage 2. Experience also shows that ISMS scopes of similar size sometimes need more time and sometimes less. The framework that shall be used for audit planning determines the starting point from the total number of persons for all shifts and adjusts it for the significant factors by giving each factor a positive or negative weight. The table shall be used, taking the contributing factors and the limits on the greatest deviation in B.3.4 and B.3.5 into account.
B.3.4 prohibits using the table in isolation. The allocated time shall also take into account factors related to the complexity of the ISMS and thus to the audit effort. Complexity of the ISMS, for example criticality of the information and the risk situation. Nature of the business in scope. Previously demonstrated performance of the ISMS. Extent and variety of technology used, for example the number of different IT platforms and the number of separate networks. Extent of outsourcing and third-party arrangements in scope. Extent of information-system development. Number of sites and number of disaster-recovery sites, in the PDF “Disaster Recovery (DR) sites”. For surveillance or recertification: the extent and scope of change relevant to the ISMS under ISO/IEC 17021-1, 8.5.3. Annex C gives examples of how these factors can be taken into account. “Can”.
Further example factors that require additional audit time are complicated logistics with more than one building or location, personnel who speak more than one language and therefore need interpreters or prevent auditors from working independently, or documentation in more than one language, activities that require visits to temporary sites in order to confirm the activities of the permanent sites, and a large number of standards and regulations that apply to the ISMS. Example factors that permit less audit time are products or processes with no or low risk, processes with a single general activity, for example service only, a high proportion of persons who perform the same tasks, prior knowledge of the organization, for example when the same body has already certified the organization to another standard, a high level of client preparation, for example already certified or recognized by another third-party programme, and high maturity of the existing management system. The PDF marks these points as examples.
Where the client provides a product or service at temporary sites, it is important that assessments of such sites are included in the certification-audit and surveillance programmes. “It is important”. The factors named shall be taken into account, and the adjustments are to be made for the factors that justify more or less audit time for an effective audit. Additions may be set off against reductions. “May”. In all cases where the time from the audit table is adjusted, sufficient evidence and records shall be maintained that justify the deviation.
B.3.5 limits the reduction. To ensure effective audits and reliable, comparable results, the audit time given in the table may not be reduced by more than 30 percent. Adequate reasons for the deviation shall be established and documented. The sentence limits the reduction. It names no upper limit for additions.
B.3.6 states an expectation. It is expected that the time calculated jointly for planning and report writing should not typically reduce the total on-site audit time to less than 70 percent of the time given in the table. “It is expected” and “should not typically”. Where additional time for planning or report writing is needed, that shall not serve as justification for reducing the on-site audit time. “Shall not”. Auditors' travel time is not included in this calculation and is added to the audit time of the table. A note says 70 percent is a factor gained from experience with ISMS audits.
B.4 on surveillance in the first certification cycle is predominantly a recommendation. Surveillance time for a given organization should be in proportion to the initial-audit time, and the total time spent annually on surveillance should be about one third of the initial-audit time. “Should” and “about 1/3”. Planned surveillance time should be reviewed from time to time to take account of changes that affect audit time. The time spent on a surveillance audit shall be increased so that changes in the ISMS can be audited, for example new or changed controls. This increase is a “shall”.
B.5 binds the total recertification time to the results of each previous audit, as specified in 9.4.3 and in ISO/IEC 17021-1, 9.6.3. “Shall”. The time spent on recertification should be in proportion to the time that would be spent on an initial certification audit of the same organization, and should be at least two thirds of the time that would be needed for an initial certification audit of the same organization at the time the recertification is audited. “Should” for the proportion and for “at least 2/3”.
B.6 requires the number of auditor days per site, including the central office, to be calculated for each site. Reductions may be applied to take account of the parts of the audit that are not relevant to the central office or the local sites. “May”. The body shall record the reasons for such reductions.
Annex C is informative. C.1 gives further guidance for deriving a formula for calculating audit time. C.2 gives an example of grading factors that can serve as the basis of the calculation, in Table C.1 for the factors from B.3.4. C.3 gives an example of the calculation, with further tables. The text says the grading can be used by bodies to derive a scheme consistent with 9.1.4.1. “Can”. The tables and the worked example are not copied here. An unused example from Annex C is not a nonconformity. The requirements stand in 9.1.4 and in Annex B.
Records: The calculation follows a documented procedure (B.3.1). Adjustments from the table need sufficient evidence and records (B.3.4). Reasons for a deviation are to be established and documented (B.3.5). Reasons for site reductions are to be recorded (B.6). An audit plan with more than 30 percent remote audit activity needs the justification and the accreditation body's approval before implementation (B.3.2).
Not in this text: the day counts and person bands from Table B.1, the grading tables and the numerical example from Annex C, the cycle and the time limits from ISO/IEC 17021-1, 9.1.3, and an obligation to sample every multi-site client. Objectives, team, stage 1 and stage 2 follow in 27006-05.