Information security policies
ISO/IEC 27022

Search this site

Security awareness content

ISO/IEC 27022 — Information technology — Security techniques — Guidance for ISMS processes [DRAFT]


According to the NWIP, this is intended to be a “detailed but generic blueprint regarding the core processes of an ISMS and - if suitable - information about management and support processes.”

The proposal is based on an academic thesis.



According to the NWIP, the standard will supplement ISO/IEC 27001, 27003 etc. “with an operational, process oriented perspective. So it will not be in conflict or duplicate the content of existing standards.”


Purpose and justification



Structure and content




Drafting started in 2018.  The standard is due to be published in 2022.

It is currently at 2nd Working Draft stage.

The abbreviation “ISMS” will need to be expanded in the title when the standard is published.


Personal comments

It won’t be easy to adapt an academic approach to address the real world problems of organizations struggling to identify and treat information risks, within various constraints (not least the existing structure of ISO27k) ... but who knows, it might just move things along in a helpful direction.

Having said that, it’s hardly a revolutionary approach to treat an ISMS as a suite of processes.  Many organizations already have processes for:

  1. Business continuity management (see ISO 22301);
  2. Change management plus configuration management and version control;
  3. Continuous improvement and maturity management;
  4. Database [security] management;
  5. Exemption management (management-approved noncompliance with policies);
  6. Identity, access rights and user account management;
  7. Incident management including incident investigation and forensics;
  8. Information management in general;
  9. Information [security] risk management (partly covered by ISO/IEC 27005);
  10. Information security management (covered by ISO/IEC 27001, 27002, 27003 and others);
  11. Internal audits and certification audits;
  12. Key management, plus the rest of cryptography;
  13. Log management, plus alarms and alerts;
  14. Metrics and management information management (partly covered by ISO/IEC 27004);
  15. Performance and capacity management;
  16. Preventive and corrective actions;
  17. Quality management, especially quality assurance;
  18. Service management [organizations that are heavily process-oriented may have ITIL/ISO20000, in which case ISO/IEC 27013 is applicable];
  19. Supplier/vendor management;
  20. System and network [security] management;
  21. System and software development

... and more.

Perhaps the intention is to document and integrate these somehow? Providing generally-applicable advice without imposing further constraints will be challenging. The 2nd WD includes several process diagrams that need to be carefully reviewed and updated to ensure they are flexible enough to cater for myriad differences between organizations while clarifying the essential elements of each process. In particular, the processes need to be valuable (cost-effective) in practice to justify their existence, for instance by:

  • Removing unnecessary bureaucracy, rationalising and justifying whatever remains;
  • Facilitating or encouraging process automation and innovation where applicable;
  • Facilitating or encouraging use of existing processes, such as applying risk, supplier, incident, business continuity, policy, compliance, departmental, people, finance and project management processes to the ISMS realm, adapting them where necessary - perhaps even using effective ISMS processes elsewhere in the organization;
  • Managing the processes themselves e.g. processes for monitoring, reviewing, evaluating and maintaining the processes, responding to changes, exploiting improvement opportunities etc.



< Previous standard      ^ Up a level ^      Next standard >

Copyright © 2019 IsecT Ltd.