The total number is regularly changing, with the occasional withdrawal of some standards and the regular addition of others (several drafts of new standards have not been included here). How, then, is one to know which ones are mandatory and which are guidelines/advisories? The answer to this question has evolved from our research for ISO 27001 courses and can be found below.
The first step towards understanding the ISO 27001 series of standards is to divide them by type. The eight types and their application are as follows:
These Standards, such as ISO 27001, set out the requirements that must be fulfilled to achieve compliance with the Standard. Certification bodies gather and record evidence of such compliance as the basis for their issuing Certifications of Compliance.
Standards here, such as ISO 27000, define the terms and definitions and explain the concepts associated with Information Security. They are advisory by their nature and do not constitute requirements.
A code of practice is a document that complements a requirements standard to provide detailed practical guidance on complying with those requirements. While not itself constituting a set of requirements, the Code should be followed unless another solution with the same or better outcome is in place.
For a given topic or situation, these provide detailed practical guidance on how to comply with requirements. Again, they do not constitute requirements but generate an expectation that they will be applied if they are applicable to the given circumstances.
For sectors with particular requirements regarding information security, e.g., telecommunications organizations, these provide detailed practical guidance on how to comply with requirements.
They also identify additional vulnerabilities associated with the sector and identify controls to address the threats arising. They do not constitute requirements but generate an expectation that they will be applied if they are applicable to the given circumstances.
These guidelines provide detailed practical guidance on how to meet the requirements for assets with particular vulnerabilities or circumstances regarding information security, such as network security and software application security.
Again, they do not constitute requirements but do generate an expectation that they will be applied where applicable.
A technical discussion document on a topic of interest and/or relevance.
A set of requirements that are advisory in nature, i.e., they do not constitute formal requirements.
Standards other than requirements standards offer non-mandatory guidance and establish concepts and definitions that help in establishing and maintaining effective information security systems.
Such documents are used by external auditors to direct their evidence gathering and to provide a logical basis for their findings.
In circumstances where they might have been followed but were not, auditors can challenge you to demonstrate how a corresponding level of control and security is being achieved by alternative means.
We have analyzed all 57 documents based on the eight types of standards. The Table of standards, shown below, was developed using a color-coded legend.
While the Table is 11 pages long, it can be quickly reviewed to establish a comprehensive list of all the Standards that may apply to your circumstances. Enjoy!
This is a Sample Page:
As mentioned above, several new Standards in the series are in the draft stage. We will monitor progress, and as new Standards are added, we will update the Table above and advise our Subscribers interested in ISMS and ISO 27001 of these developments.
In
We have chosen ISO 21001 certification because, unlike IRCA and Exemplar badges (which, in our opinion, are commercially compromised), it is based on independent third-party assessment. It is a 'university grade' standard used globally by schools, colleges, and universities to demonstrate competence.
We provide Courses for ISO 9001, ISO 13485, ISO 14001, ISO 17025, ISO 27001, ISO 45001, Risk Management, Data Protection, and more.