Start a new topic and get direct answers from the Expert Advice Community.
CREATE NEW TOPIC +Guest
Since ISO 27001 and ISO 22301 share many requirements (e.g., document management, internal audit, management review, etc.), the effort to implement the specifics of ISO 22301 (i.e., mainly clauses 6 and 8) is roughly 30% of the cost of ISO 27001 implementation.
Please note that the information security roles and responsibilities are defined and allocated along all the templates in the toolkit.
High-level roles and responsibilities are defined in the Information Security Policy, while specific ones are defined in specific policies and procedures.
For example, you can find this type of structure in the Backup Policy:
[job title] must perform backup copies at planned intervals.
[job title] must test backup copies to ensure the backup was performed successfully.
For further information, see this article on documenting roles and responsibilities according to ISO 27001.
Please note that ISO 27001 does not prescribe any specific documentation for clause 10.1 Continual Improvement.
Our ISO 27001 Documentation Toolkit covers all mandatory documents and some documents that are not mandatory. A Continual Improvement policy do not need to be documented according to the standard, and in our opinion it would be an overhead to document it in a small company.
Our toolkit is created specifically for smaller companies that want to implement ISO 27001 in a quick way, without unnecessary paperwork; for larger companies that require more documents we recommend getting some other solution.
This article will also help you: List of mandatory documents required by ISO 27001 (2013 revision)
Commitment to continual improvement is defined in the Information Security Policy, which can be found in folder 05 General Policies.
Examples of how you can demonstrate continual improvement are:
These articles will provide you with further explanation about continual improvement:
- Why is management review important for ISO 27001 and ISO 22301?
- Achieving continual improvement through the use of maturity models
You are basically right - if the HR department is outside of the ISMS scope, from the ISMS point of view it will have the same status as a third-party provider; of course, legally speaking, your HR department is not a third-party provider, but a organizational unit of your company.
This article will provide you with further explanation about scope definition: This tool can also help you:To align procurement with ISO 9001:2015, organizations need to consider the following:
You can find more information at the following link:
First is important to note that in this module, you need to list only the requirements of customers and regulators you need to comply with. Requirements related to suppliers are handled only in case there are risks that justify handling them.
Considering that, you should list each regulation as a unique entry because they are typically related to a specific reference (e.g., data privacy in Europe refers to GDPR and in Brazil to LGPD).
Regarding clients, you can group the clients with the same requirements together (e.g. if you have the same agreement signed with all of them), or you should list them separately if their security requirements are very different.
Regarding the level of detail, you can include only a summary of the requirement and refer to another document where more detailed information can be found.
ISO 9001:2015 does not specifically require organizations to use a consultant for QMS implementation or to acquire an auditor's certificate. ISO 9001 emphasizes that organizations are responsible for developing, implementing, and maintaining their QMS
The decision to engage a consultant or acquire auditor certification is typically at the discretion of the organization. Many organizations choose to work with consultants for various reasons, including expertise, guidance, and resources. However, this is a business decision and not a mandatory requirement outlined in the ISO 9001 standard.
It's important to note that while the ISO 9001 standard doesn't mandate these activities, organizations should ensure that their chosen consultants or auditors are qualified and competent to provide the necessary expertise and meet the standard's requirements. Additionally, some industries or sectors may have specific regulations or customer requirements that influence the use of consultants or auditors, but this is not a requirement dictated by the ISO 9001 standard itself.
You can find more information below:
To define strategic risk assessment separately from operational risk assessment and assign appropriate rankings, first, identify strategic risks that could affect your long-term objectives, such as market changes or regulatory shifts. Develop a unique set of criteria for strategic risks, considering their impact and likelihood
For these strategic risks I use clauses 4.1, 4.2 and 6.1.1. Please check this free webinar-on-demand - How to Implement Risk Management in ISO 9001:2015 slide 11. Although it is about ISO 9001, I think it can help.
For operational risks, focus on environmental aspects and impacts and consider abnormal and emergency situations. Then, assign rankings based on the specific criteria for each category. Strategic risks may receive rankings based on their potential impact on long-term goals, while operational risks are ranked according to their daily impact and likelihood.
You can find more information in:
As the purpose of a standard operating procedure is to minimise deviations by standardising the process, documenting a process as an SOP starts with knowing the risks and critical steps that should be controlled and carefully communicated. The depth of detail in the SOP will depend on the context of your laboratory, for example, the number of people performing the task and their competency.
Standard operating procedures for any laboratory are typically divided into two categories – Management (nontechnical) and technical. An example of a management procedure would be for handling non-conformances and corrective actions. Technical SOPS could either document, for example, the approach to method validation or document the test methods itself. As the purpose is to minimise deviations by standardising the process, documenting a process as an SOP starts with knowing the risks and critical steps that should be controlled and carefully communicated. The depth of detail in the SOP will depend on the context of your laboratory, for example, the number of people performing the task and their competency. Either way, it is recommended that you have a standard format. For more information, have a look at the Advisera Toolkit https://advisera.com/toolkits/?standard=iso-17025 and a previous question. https://community.advisera.com/topic/document-and-record-control-procedure-means-what-are-the-procedure-will-include/