ISO 17799 to ISO 27002: A Warning

It is well known that ISO 17799 has been renamed to ISO 27002. This was confirmed by the appropriate ISO Technical Committee some weeks ago.

A number of people questioned the need for this, and have asked why this couldn't wait until the next upgrade of the standard. Nonetheless, it went ahead, and we waited for the renamed copy to be made available.

Here is the crux though: ISO have now made this available... BUT.... it is simply ISO 17799:2005 with a single accompanying PDF sheet stating "Replace '17799' with '27002'". Seriously, that is it!

So the warning is that if you already have a copy of ISO 17799:2005 and were thinking of buying another copy to replace it, don't, unless the situation changes (and it may not).

If you don't have a copy of ISO 17799:2005 and were thinking of buying a copy of ISO 27002, go for ISO 17799:2005 instead if you can find that cheaper than ISO offer it for (and you can), unless the situation changes (and it may not).


We will continue to monitor the situation and will immediately post any changes which we identify.

And Another Emerges: ISO 27033

The next ISO 27000 series standard is on the starting block: ISO 27033.

On 12th July a formal note was distributed by the appropriate ISO committee (JTC 1 / SC 27) announcing a letter ballot for early revision and renumbering (to 27033) of existing standard 18028.

Obviously, this is the very start of a lengthy process, but the note also revealed the proposed structure of the new standard, which it is proposed would comprise seven parts:

1. Guidelines for network security
2. Guidelines for design/implementation of network security
3. Reference networking scenarios
4. Securing communications between networks using gateways
5. Securing remote access
6. Securing communications across networks using VPNs
7. Guidelines for securing

Momentum for the series continues to increase.

Update On ISO 27799: ISO 27789?

ISO 27799 will be the health sector specific version of ISO 17799/27002. The above though is a bit of a misleading title, because it is still under approval and there is no 'update' at all!

However, whilst scanning the airways for progress we identified another health sector related ISO 27000 standard. This is ISO 27789. Like ISO27799 it is specific to the health sector. Its provisional title is: Audit trails for electronic health records. The planned publication date is late 2009.

It looks therefore like the ISO 277nn prefix may have been bagged by the health sector.

TO WATCH:
In the US, the relationship between ISO27799 and HIPAA (Health Insurance Portability and Accountability Act). Will HIPAA become a driver for the adoption of ISO 27799? Will 27799 be used as an example of due diligence with respect to certain aspects of the act? Time will tell.

ISO27000 Interviews

We are planning a series of short interviews with leading industry figures. These will be posted from this page as and when they are published.

The list of early contenders is currently being drawn up. We will then approach the lucky interviewees!

Please return to this page for more information.

How is ISO27000 Related to ISO 31000 And BS31100?

The answer is: we don't know! So why ask the question? Because it probes the relationship between different aspects of risk assessment, and different sets of standards.

We tripped upon two holding sites: one for ISO 31000 and one for BS31100. Scratching the surface with both ISO and BSI didn't reveal too much extra. However, it does appear that these BOTH address risk management at a corporate/organizational level. Security risk assessment is part of this, but only part of it.

Why 31000 and 31100? Clearly this similarity indicates SOME relationship and forethought, but at this stage we could not determine specifically what this was. It does appear that BS31100 is much closer to fruition than ISO31000, but how they are related will be interesting to determine, as will the scope for BS31100 to become ISO 31100 or perhaps ISO 31001.

The precise relationship between these and BS7799-3, and/or ISO27005, will also be interesting to see. There will surely be cross reference between these, as there are logical relationships between them. How much further that goes remains to be seen.

This does illustrate however that it isn't just the ISO2700 series which is 'shrouded in mystery', but others too. For those of us who thrive on clarity, it is a bit of a nightmare!

The 27000 Who's Who

This is another ongoing project. Over time we will build up a comprehensive "Who's Who" of the ISO 27000 world. The current list is below:

David Watson
The very first BS7799/ISO17799/ISO27001 (take your pick) auditor. David Watson is still busy in the infosec arena, owning a consultancy company in the UK and moderating the Dr Watson forum on the ISO 17799/27001 Community. He is also an accomplished author.

Kate Hartley
The driving force behind the biggest online user group dedicated to the standards (17799.com)

Ted Humphreys
A long established consultant, Ted Humphreys has been a key player in the development of the standards, and holds a pivotal role on the relevant ISO technical committee.

Gary Hinson
Gary a consultant and is ISSA's UK Secretary. He also runs several websites, including a very easy to read blog (noticebored.com).

Andrew Smith
A policy writer and consultant, but best known as the moderator of the major Yahoo user groups.

Brian Doswell
Manages a consultancy practice and is a member of BCI's advisory board. Brian is also a published (ISO 17799) information security author.


This of course is an initial seed list, which will be added to. Please add your own suggestions via the comment option below.

ISO 27000: ISO 27031 and Business Continuity Numbering

The assignment of numbers within the ISO 27000 series has been the subject of ongoing debate for some time. The confusion with respect to future intentions is no better exemplified than with respect to business continuity.

ISO 27031 has long been understood to be earmarked for at least one aspect of business continuity. Clarity was been a long time in coming, but it does now appear that this number will be assigned to a standard pertaining to ICT Readiness for Business Continuity, based perhaps upon SS507. Or does it? Confirmation can still not be found on the ISO website.

If ISO27031 is to be assigned to ICT, then what about other aspects of business continuity? If ICT readiness fits under the ISO 27000 billing, what about planning or service continuity?

Other Business Continuity Standards
BS25999 is currently setting about filling the void for business continuity planning (BCP). This is interesting because its structure is the same as ISO standards tend to be: a code of practice and a specification. BS25999-1 is the code of practice. BS25999-2 is the specification.

Does that sound familiar? It should do. Think ISO 27001 and ISO 27002. Think the two parts of ISO 20000. The list is rather long.

So if 25999 is to evolve to be an ISO standard, where does that fit in the 27000 numbering system?

It doesn't end here. What about PAS77? This BSI document relates to IT service continuity, which is part of the ISO 20000 scene. It is aligned with that standard. Unofficial word has it that this is to become a BS standard (this site: BS25777.Info - is a bit of a giveaway). So where is this to fit if it evolves into the ISO system? It is hard to imagine that ISO will not embrace such a standard given the success of ISO 20000.


We have heard a number of rumours with respect to business continuity numbering, but repeating them probably wouldn't serve a positive purpose at this time. A little more clarity from ISO might, however.

The Official ISO27001 Certification Register

We frequently see questions asked regarding this issue, largely as people search for data regarding existing certifications, or perhaps to get an idea of the total number of certificates issued.

There simply is no official worldwide register.

Searching the internet reveals a couple of efforts to build credible registers, but in truth these are sourced by a very tiny minority of certification bodies. They are thus not even remotely complete.

The most interesting approach is the one adopted by the ISO17799/27001 Guide, which is a dedicated Wiki. This operates a voluntary register, which enables certified organizations to enter their own details. This is surely the most valid approach.

Voluntary v Involuntary
Not every certified organization wants its details paraded on the internet. There may be a variety of reasons for this.

For example, there is a school of thought which believes that specifying in public which security framework has been followed is in itself something of a security risk. If something is missing from that framework, then it is quite possible that it is missing from the security implementation too, and stating this in public is not sensible. Another example could be the loss of competitive advantage if the certification of part of an organization is made public in the circumstance in which others are to follow shortly.

Whatever the reason, however, surely the certified organization should be the party to determine when, where and whether this is made public. A voluntary arrangement supports this proposition.

It has to be accepted that this approach will never create a complete register, but at least the playing field will be level and equal, and not driven by selected certification bodies.

The voluntary register is a worthy initiative.