Start a new topic and get direct answers from the Expert Advice Community.
CREATE NEW TOPIC +Guest
1. Is there a difference between ISO 27001: 2013 and ISO 27001: 2014? We understood that 2014 was the most current version. Our implementation we wanted based on 2014.
I’m assuming you are referring to UNE-ISO/IEC 27001:2014.
Considering that, please note that this is the Spanish translation of ISO 27001, released by the UNE Normalización Española, so it contains the same information and content of the international standard. You can use either ISO/IEC 27001:2013 or UNE-ISO/IEC 27001:2014 for your implementation.
2. We are currently within our process, we are in the Diagnostic stage, to see the critical factors within the processes. For this stage, which Templates would be more recommended to use.
The beginning of the implementation process involves the identification of organizational context and requirements, and interested parties, so you should consider using the templates in folder 02:
For further information, see
3. Once the Diagnostic part was finished, our next stage was to carry out the implementation of the ISMS indicating the controls Necessary and Monitoring. In this regard, is there any recommendation with which template to start the implementation part?
Please note that after the definition of organizational context and identification of interested parties, you need to define the ISMS scope, ISMS Policy, and define the risk assessment and risk treatment methodology, before identifying necessary controls.
Considering that, for a streamlined implementation, you should implement the documents in the order they appear in the toolkit.
By the way, included in the toolkit you bought, you have access to a video tutorial that can help you fill in the most critical documents, using real data examples.
These articles will provide you a further explanation about ISO 27001 implementation:
These materials will also help you regarding ISO 27001 implementation:
ISO 27001 does not prescribe how to handle the information according to their classification level. Such treatment must be based on results of risk assessment and applicable legal requirements (e.g., laws, regulations, and contracts). For example, if the risks related to keeping confidential information on the public cloud are unacceptable, then one rule to be defined is that confidential documents must not be kept on the public cloud. Another example is that a contractual clause may define that confidential documents must be kept on local servers.
To see how rules to handle information compliant with ISO 27001 looks like, please see the free demo of our Information Classification Policy template at this link: https://advisera.com/27001academy/documentation/information-classification-policy/
This article will provide you a further explanation about information classification:
These materials will also help you regarding information classification and handling:
The official ISO 27001 revision is from 2013, and it was confirmed in 2019 - you can see the details here: https://www.iso.org/standard/54534.html
When you mention ISO 27001:2017, this is probably a standard that was re-published by a European or a local standardization body in a particular country - however, even though it has the year "2017" it is again the same as the original ISO 27001:2013.
This article can also help you: European 2017 Revision of ISO/IEC 27001: What has changed? https://advisera.com/27001academy/blog/2017/10/25/european-2017-revision-of-isoiec-27001-what-has-changed/
Adding, changing, or excluding a control from SoA is a natural and necessary thing to maintain the ISMS.
To do that, considering the requirements of the standard, you need to review your risk assessment and risk treatment, and your list of applicable legal requirements, to verify if there is any change in your context that can justify a change in SoA. Additionally, you need to check if there is any management decision to implement a control (in such cases there will be no changes in risk management nor in legal requirements).
Once a need for change is identified, you need to define an implementation plan to perform the change.
These articles will provide you a further explanation about SoA:
The importance of Statement of Applicability for ISO 27001 https://advisera.com/27001academy/knowledgebase/the-importance-of-statement-of-applicability-for-iso-27001/
ISO 27001/ISO 27005 risk assessment & treatment – 6 basic steps https://advisera.com/27001academy/knowledgebase/iso-27001-risk-assessment-treatment-6-basic-steps/
How to identify ISMS requirements of interested parties in ISO 27001 https://advisera.com/27001academy/blog/2017/02/06/how-to-identify-isms-requirements-of-interested-parties-in-iso-27001/
The data you are going to process belongs to the special category of personal data under Article 9 GDPR (some legislation call them sensitive data) because this kind of data contains information which may end up in discrimination and in threats to the freedom and rights of individuals. Therefore, the EU GDPR requires controllers and processors to pay particular attention when processing this kind of data.
Before starting processing, you will need a Data Protection Impact Assessment as Article 35 GDPR requires in order to verify the risk for freedom and rights of data subjects arising from your data process and assess the risks with appropriate safeguards. This will also help you to comply with privacy by design and privacy by default principles.
From the information you wrote, your data processing will be likely based on consent. Therefore, you will need to pay attention to the information provided to data subjects in your privacy notice and the request for consent.The register of processing activities will also be required.You will need to establish a procedure to deal with Data Subjects Access Request (DSAR) because data subjects may always withdraw the consent and you need to be able to verify the request and proceed with the exercise of DSAR and also comply with the right of erasure if requested so.
Be sure to inform data subjects that their data will be processed also in the US.
Then, transferring data to a processor in the US may request safeguards: adoption of a data protection agreement with the approved standard contractual clauses is necessary because the EU Court of Justice invalidated the US Privacy Shield with the so-called Shrems II decision. You may also adopt secure transfer protocols and encryption (if you can anonymize data it would be a plus while pseudonymization is highly recommended).
Here you can find more information:
To have a deeper idea of the list of requirements of GDPR you can consider enrolling in our free online training EU GDPR Foundations Course: https://advisera.com/training/eu-gdpr-foundations-course//
Thank you so much
You can write the procedures in either world, excel, or another format.
The procedure writing method for IATF 16949:2016 standard is not different from ISO 9001:2015 standard.
As you know a procedure states how the process needs to be done.
A procedure offers a general description of how a company meets a process requirement and the procedure consists of more specifics.
This includes scope, objective, responsibilities, references, application, specific tools, methods, measurements, and historical change of procedure.
There are 7 steps in writing quality management system procedures for ISO 9001:2015 and IATF 16949:2016 standards.
These 7 procedure writing steps are listed below, respectively:
For more information please read the following article:
You can also see our IATF 16949:2016 Documentation Toolkit here: https://advisera.com/16949academy/iatf-16949-2016-documentation-toolkit/
I’m assuming you are referring to convince leadership to support an ISO 27001 implementation.
Considering that, to improve your chances to get support for an ISO 27001 initiative in your organization you should provide real examples of benefits related to:
Another important point to be considered is the presentation. For top management, you should avoid using technical jargon (concentrate on business benefits).
These articles will provide you a further explanation about ISO 27001 benefits and top management:
These materials will also help you regarding ISO 27001 benefits and top management:
You can download an explanation of ISO 22301 standard here: Clause-by-clause explanation of ISO 22301 https://info.advisera.com/27001academy/free-download/clause-by-clause-explanation-of-iso-223012008
In the ISO 27001 & ISO 22301 toolkit you purchased, you will find the document called "List of documents" - it defines which documents are needed for ISO 22301 implementation.
To simplify this, if you want to implement only ISO 22301 without ISO 27001, you would need to implement documents from these folders, in this very sequence:
00 Document management
01 Preparations for the project
02 Identification of requirements
05 Risk assessment and treatment
08 Annex A controls - A.17 Business continuity
09 Training and awareness
10 Internal audit
11 Management review
12 Corrective actions