At the end of 2019, Axenic’s leadership team agreed to implement our strategy to achieve ISO 27001 certification. This took the form of setting aside resources to spend time on designing and implementing our Information Security Management System (ISMS). In this blog series, we will be taking you through Axenic’s journey to certification – to catch up on Part One of the series click here. In our second blog of the Axenic ISO 27001 certification journey, we take a look at the planning stage and what was involved in this important step.
Last week was an exciting week for the Axenic team with some big news. We are extremely proud that we achieved the ISO/IEC 27001:2013 certification and we don’t underestimate what a huge accomplishment this is for our business and importantly – our customers. Information security is at the core of what we do at Axenic, and we wanted to practice what we preach. You may be interested in getting ISO/IEC:2013 27001 certification for your organisation – read on to find out why we went through this process and what it means for our clients.
In my previous two articles in this series focused on developing an Information Security Management System (ISMS) based on ISO 27001:2013, I presented the common myths associated with the standard. In this article, I am going to provide an overview of the standard and section 4 Context of the organisation.
Okay, I know I promised to delve into and discuss the requirements defined in 4 Context of the organisation. However, I realised that they are other common myths that I should dispel for those of you that are interested in implementing an Information Security Management System (ISMS) that conforms with ISO/IEC 27001:2013 (ISO 27001).