How does it work?
Typically the process starts by determining the scope of your organisation that is to be included in your ISMS and subject to the ISO 27001 standard, it is preferable to cover the entire organisation but in some cases this is simply not practical.
The next stage is to determine what information assets are within the scope defined, these can be everything from the customer data to website logs, employee ID tags to shipping manifests.
Once a list if information assets has been created, it’s possible to evaluate the threats to these assets in a risk register.
Once the risks have been identifed, the risks must be mitigated to an acceptable level via controls which are defined in a risk treatment plan, which in turn identifies which ISO 27001 controls are required (these are recorded in a statement of applicability).
If your organisation already has security controls in place, a gap analysis can help determine which security controls are already in place and which still need to be implemented.
Security controls are defined and implemented via company policies and procedures, these should be authored in a way that is aligned to the standard for easier audting and reference in the future.
Lastly, the ISMS, it’s policies and supporting documentation are audting by a third party to ensure compliance with the standard and ISO 27001 certification is given.