Start a new topic and get direct answers from the Expert Advice Community.
CREATE NEW TOPIC +Guest
First is important to note that, for the documents you mentioned, only the ISMS scope and list of requirements documents are mandatory for ISO 27001.
Considering that, there are some core documents that must be developed and approved before start writing other documents. For example, the ISMS scope must be approved before other documents are written. Another example is that risks must be identified, and treatment for the relevant ones defined, and the Statement of Applicability (SoA) must be approved, before documents related to security controls are written.
This article will provide you a further explanation about ISO 27001 mandatory documents:
- List of mandatory documents required by ISO 27001 (2013 revision) https://advisera.com/27001academy/knowledgebase/list-of-mandatory-documents-required-by-iso-27001-2013-revision/
This material will provide you further explanation the order to develop and approve documents:
- Project checklist for ISO 27001 implementation (MS Word) https://info.advisera.com/27001academy/free-download/project-checklist-for-iso-27001-implementation
These materials will also help you regarding Iso 27001 implementation:
- Book Secure & Simple: A Small-Business Guide to Implementing ISO 27001 On Your Own https://advisera.com/books/secure-and-simple-a-small-business-guide-to-implementing-iso-27001-on-your-own/
- Free online training ISO 27001 Foundations Course https://advisera.com/training/iso-27001-foundations-course/
Strategies refer to high-level actions to be developed to achieve defined objectives, while solutions are related to how these actions will be implemented.
For example, to ensure the objective of recovering operations in a defined timeframe, the strategy adopted may be the use of an alternative site, and the solution would be the definition of the alternative site (e.g., by hiring a third party to provide the alternate site, or the organization can build its own main site.
Another example is a backup strategy (which could be incremental, differential, etc.), and the solution would refer to the specific hardware and software bought.
This article will provide you a further explanation 22301:2019:
This material will also help you regarding 22301:
1. When doing the Access Control policy we found ourselves relatively short of content in the policy document (this has not appeared to be the case in all policies we’ve worked through). Are you able to give us any guidance on where we could find resources with more prescriptive control examples, than are found in the ISO 27002 standard? The challenge we seem to have is the policies are not all encompassing in terms of coverage of the controls, and when we turn to the controls in the standard, the controls appear quite vague in some cases. Is there somewhere a next level down of control examples? Any comments / insights you can offer around this would be appreciated.
For more prescriptive examples you can use to customize your Access Control Policy, I suggest you consult the NIST SP 800-53 document.
For further information, see:
2. Is there anything at all stopping us from incorporating the controls found in CSA CCM into our documentation suite? Many map to ISO controls, but in some cases appear to be more specific.
If we were doing this, do you have any suggestions or comments we should keep in mind when approaching this?
ISO 27001 does not limit applicable controls to those listed on Annex A, so organizations can develop their own controls, or use controls from other sources, so you incorporate controls from CSA CCM into your documents.
As a recommendation for using this approach, you must remember to include a reference to controls external to Annex A into your Statement of Applicability. This can be done either by including a new control in the SoA list (if the new controls cannot be mapped to controls from Annex A), or by including a comment in the implementation method column referring to the mapped control.
These articles will provide you a further explanation about developing documents:
This material will also help you regarding security controls:
Your assumption is correct. Since you do not do any software development, you do not need to complete the Secure Development Policy.
Since this document will not be used by your organization, you must update the Statement of Applicability to reflect this situation.
These articles will provide you a further explanation:
This material will also help you:
First is important to note that ISO 27031 has a focus on the recovery of Information and Communication Technology, which is only one part of a business disaster recovery (e.g., it does not cover the recovery of operational and administrative processes).
Considering that, you should evaluate if the content provided by ISO 27031 is enough to cover your needs (i.e., at this point you only need technical guidance), or you need a more comprehensive view of the business, to prioritize business process (in this case you should start with ISO 22301).
These articles will provide you a further explanation about ISO 27031 and ISO 22301:
This material will also help you:
Besides hardware and software, other commonly used categories for information asset are people (e.g., experts, top management, line managers, users, etc.), documentation (e.g., contracts, blueprints, manuals, etc.), infrastructure (e.g., offices, warehouses, etc.), and outsourced services (e.g., communication providers, electrical power supply, etc.).
To see a list of assets commonly used for ISO 27001 ISMS, please take a look at the free demo of our Risk Assessment Table at this link: https://advisera.com/27001academy/documentation/risk-assessment-table/
This article will provide you a further explanation about assets management:
These materials will also help you regarding asset management:
Yes, you're right, Clinical evaluation is covered in requirement 7.3.7 Desing and development validation.
In our ISO 13485:2016 & MDR Documentation toolkit we have prepared the necessary documentation for clinical evaluation according to the MDR. You can see its preview on the following link:
I would like to know if you are planning to have a session on how to audit ISO 9001:2015 management system, please?
Answer:
Yes, you can subscribe the next webinar on auditing ISO 9001:2015, next February 11th in the following link - https://advisera.com/9001academy/webinar/how-to-perform-an-iso-9001-2015-internal-audit-free-webinar-on-demand/
Part of the Standard which covers management, please? Clause 4, 5, 6, 7.1? Also when auditing management only should clause 10.1 and 10.3 be audited during management audit?
Answer:
When auditing top management, I include all the clauses that you mentioned and also 9.3. Management review is very important.
You can find more information below:
About the 'ISO document numbering system,' there is no particular prescription from ISO 9001:2015. The only requirement is that your organization has a method that allows for the unique identification of each document. Different organizations use different methods. Use a method to identify the document and the version, by a number or a date.
Normally, I number processes and all documents related to a particular process start with that number. For example, in process “3.Win order”, we have P3.1 (for a procedure) and WI3.1 and WI3.2 (for a work instruction). For forms, I just use a counting system 1, 2, 3, 4 …
You can find more information about records below:
Unfortunately, I cannot provide you with an example, but I can try to guide you in writing one. Gather a group of people that work on deliveries and that are internal suppliers and internal customers of deliveries.
First, think about the flow of activities
Then, ask: what can go wrong?
For each step in the flow add one or more control activities to minimize or eliminate what can go wrong. For example, before “Charge cargo” check if the container is clean. You can add a checklist, a visual control operation.
For each step in the flow identify who participates, who has responsibilities, who has authority.
Then you can write the procedure for each step: what needs to be done by whom, what documents are used, and what records are generated.
You can find some help in this free webinar on-demand - The Process Approach - What it is, why it is important, and how to do it - https://advisera.com/9001academy/webinar/iso-9001-process-approach-free-webinar-on-demand/ I show how to relate processes, risks, training, documentation, and control.