Start a new topic and get direct answers from the Expert Advice Community.
CREATE NEW TOPIC +Guest
Please note that this section consolidates information about how to handle records mentioned in the content of the document (e.g., who is responsible for them, where they are stored, for how long they need to be kept, etc.). This information is needed to help fulfill requirements from section 7.5 of the standard (Documented Information).
So our recommendation is for you to keep this section (the alternative would be to include the above-mentioned information in the place where the record is mentioned, what would turn the document more complex to read).
This article will provide you a further explanation about documents:
This material will also help you regarding document management:
First is important to note that ISO 27001 only requires incident management related documents and records if controls from section A.16 are stared as applicable in the Statement of Applicability.
Considering that, provided that your implemented solution (help desk system) fulfills the standard's requirements for incident management, you do not need to implement a specific incident management form.
These articles will provide you a further explanation about the incident management:
8.5.3 it is applicable because certified organizations should take care and protect customers’ intellectual property.
7.5.3 may be applicable because of the need to control relevant documents of external origin.
The following material will provide you more information:
ISO 27001 does not prescribe the use of 2FA on VPNs. To identify if such implementation is needed you have the verify the results of risk assessment and applicable legal requirements (e.g., laws, regulations, and contracts), to see if such implementation will properly treat relevant risk, or fulfill legal clauses.
These articles will provide you a further explanation about the selection of controls and 2FA:
ISO 27001 does not prescribe signatures for documents, only that documents are approved before use. Considering that, provided you can ensure that documents content, in physical or electronic format, are approved before use you can adopt any approach you see fit (e.g., signing the front page of each document, keeping electronic versions of approved documents in a specific folder, etc.).
Signing a single document for all processes like you suggested is acceptable but not recommended, because users of documents won't be able to easily check if the document they have on hand is an approved version (signing the front page, or use of specific electronic folder, are examples which provides a balance between the need for signing and easiness of approval verification)
This material will also help you regarding document control:
1. What is to be included in the scoping document beyond simply stating the locations that are 'In-scope for the ISMS?
The most important information to be included in the ISMS scope is the information the ISMS is intended to protect. Information like location, processes, or business units included in the scope helps clarify the scope.
To see how an ISMS scope document looks like, I suggest you take a look at the free demo of our ISMS scope document at this link: https://advisera.com/27001academy/documentation/isms-scope-document/
For more information, see:
2. and when does this document need to be created - before the Project Plan Is signed off?
The ISMS scope is created after the Project Plan is signed off.
This article will provide you a further explanation about ISO 27001 implementation steps:
This material will also help you regarding ISO 27001:
At this moment we are working on updating the book according to the 2019 version of ISO 22301 (to be released soon), but we already can say that this new version of the standard has fewer changes in terms of additions (reviewers work heavily on making ISO 22301 lighter in terms of documentation requirements)
These articles will provide you a further explanation about changes in new ISO 22301:
Your questions is not very clear to me. If you are asking if there are any other ISO standards that require mandatory ISO 17025 accreditation, as part of their requirements; then the answer is no. There are a number of standards or programmes, either mandatory or voluntary for certain sectors, that may require that any required testing or calibration activity is performed by an ISO 17025 laboratory. An example is GLOBALG.A.P. - The Worldwide Standard for Good Agricultural Practices.
ISO 17025 is part of the Conformity assessment family of standards (ISO 17000 family), however each has it’s own specific purpose. ISO 17025 promotes confidence in the operation of laboratories through a guideline of requirements to support the competence, impartiality and consistent operation of laboratories. Accreditation bodies attest to the competency of laboratories through the process of accreditation.
When going for the certification audit, you should have most of your controls implemented, and make sure that controls that mitigate the biggest risks are fully implemented, or the certification auditor can consider that the ISMS is not ready for certification yet.
In other words, you can leave only a smaller number of less significant controls to be implemented after the certification. In your case, you have to ask risk owners to accept the residual risks related to this control still "in progress".
This article will provide you a further explanation about certification:
This material will also help you regarding certification:
While ISO 9001 has as its purpose meeting and improving customer satisfaction. ISO 22000 has as its purpose food safety.
I can understand that an organization applies to both certifications since they have different purposes and can signalize different messages to interested parties.
The following material will provide you more information about ISO 9001:2015: