Start a new topic and get direct answers from the Expert Advice Community.
CREATE NEW TOPIC +Guest
1 - Is it a fundamental prerequisite for certification in the standard?
Process mapping is not a prerequisite for ISO 27001 certification, although it is useful to facilitate understanding of the context and the identification of risks.
2 - How deep should the mapping and documentation for the scope be?
Since this is not a mandatory requirement, just a good practice for understanding the context and establishing the scope, the process mapping does not need to be done, or documented in the scope document.
If the organization decides to carry out the mapping, its level of detail will depend on what the organization considers sufficient to decide that the scope is properly defined.
3 - Overall, I still have a lot of questions about the topic "Organization context" and everything it should cover ...
First is important to note that the context of the organization do not need to be documented.
Considering that, the context of the organization is any internal or external factor that can affect the ISMS, and concrete examples of elements of organizational context are:
Based on these you can identify elements that can help you understand how information security must be considered.
This article will provide you a further explanation about the Context of the organization for 27001:
These materials will also help you regarding the Context of the organization for 27001:
1 - É um pré-requisito fundamental para a certificação na norma?
O mapeamento de processos não é um pré-requisito para a certificação ISO 27001, embora ele seja útil para facilitar o entendimento do contexto e a identificação de riscos.
2 - Quão profundo deve ser o mapeamento e documentação para o escopo?
Uma vez que não se trata de um requisito mandatório, apenas uma boa prática para entendimento do contexto e estabelecimento do escopo, o mapeamento de processo não precisa ser feito, ou documentado no documento do escope.
Caso a organização decida realizar o mapeamento, seu nível de detalhamento vai depender do que a organização considera suficiente para que decidir que o escopo está adequadamente definido.
3 - No geral, ainda tenho muitas dúvidas sobre o tópico "Contexto da organização" e tudo o que ele deve abranger...
Em primeiro lugar, é importante observar que o contexto da organização não precisa ser documentado.
Considerando isso, o contexto da organização é qualquer fator interno ou externo que pode afetar o SGSI. Exemplos concretos de elementos do contexto organizacional são:
Com base neles, você pode identificar elementos que podem ajudá-lo a entender como a segurança da informação deve ser considerada.
Este artigo fornecerá uma explicação adicional sobre o contexto da organização para 27001:
Esses materiais também irão ajudá-lo com relação ao contexto da organização para 27001:
First is important to note that using ISO 27001 is not mandatory for fulfilling GDPR requirements. To perform risk assessment, you can use any approach your organization sees fit for its purpose.
Additionally, ISO 27001 does not prescribe any method to perform risk assessment, only defines requirements to be fulfilled by the adopted risk assessment process.
Considering that, the purpose of GDPR is the protection of personal information from being accessed, modified, or destroyed in an uncontrolled manner, so an example of risk assessment considering the elements you mentioned are:
- an unattended computer storing biometric data can be stolen or invaded
- an untrained employee can inadvertently delete biometric data
- a biometric reader can fail during a data-gathering section
This material will also help you regarding risk management:
- ISO 27001/ISO 27005 risk assessment & treatment – 6 basic steps https://advisera.com/27001academy/knowledgebase/iso-27001-risk-assessment-treatment-6-basic-steps/
- Book ISO 27001 Risk Management in Plain English https://advisera.com/books/iso-27001-annex-controls-plain-english/
First of all, sorry for this inconvenience. Every time you find such discrepancies between the tutorials and documentation, please consider the information in the templates as the correct one, because they are the most updated version.
First is important to note that using ISO 27001 is not mandatory for fulfilling GDPR requirements. To perform risk assessment, you can use any approach your organization sees fit for its purpose.
Additionally, ISO 27001 does not prescribe any method to perform risk assessment, only defines requirements to be fulfilled by the adopted risk assessment process.
Considering that, the purpose of GDPR is the protection of personal information from being accessed, modified, or destroyed in an uncontrolled manner, so an example of risk assessment considering the elements you mentioned are:
This material will also help you regarding risk management:
Please note that organizations that issue certifications are certification bodies. An accreditation body is another type of organization, the organization which authorizes organizations to act as certification bodies.
Considering that, to certify an organization your company has to be accredited by an accreditation body (e.g., UKAS for the UK, or ANAB for the USA), and for this purpose, your organization has to be certified by an accreditation body against ISO/IEC 17065. You can have an overview of this standard here: https://www.iso.org/obp/ui/#iso:std:iso-iec:17065:ed-1:v1:en
This article will provide you a further explanation about accreditation and certification:
Please note that included in your toolkit you have access to video tutorials that can guide you through the risk assessment and treatment processes, including the filling of the SoA. These video tutorials include examples with real data.
Since you did not say you already saw the video tutorials, I suggest you start with these and contact us if some doubts remain.
In addition to these video tutorials, I suggest you these materials (the articles are in the suggested reading sequence):
First is important to note that although process mapping can help the implementation process, it is not a mandatory requirement for ISO 27001.
Considering that, the general steps for ISO 27001 implementation are:
1) getting management buy-in for the project;
2) defining ISMS basic framework (e.g., scope, objectives, organizational structure), by understanding organizational and requirements of interested parties;
3) development of risk assessment and treatment methodology;
4) perform a risk assessment and define a risk tent plan (at this point you can make use of processes frameworks like ISO 38500 and ISO 20000 as a reference to help identify risks, but please note that this approach is not mandatory by the standard);
5) controls implementation (e.g., policies and procedures documentation, acquisitions, etc.);
6) people training and awareness;
7) controls operation;
8 performance monitoring and measurement;
9) perform internal audit;
10) perform management critical review; and
11) address nonconformities, corrective actions, and opportunities for improvement.
This article will provide you a further explanation about ISMS implementation:
Regarding implementation approaches, the most common are:
Each one of them has its advantages and disadvantages. For more information, I suggest you the following materials:
These materials will also help you regarding ISO 27001 implementation:
Unfortunately, we are unaware of such type of statistics (most probably because attacked organizations often keep details about incidents of the media).
What we can infer is that ISO 27001 and ISO 27701 certified organizations are recognized as more secure and resilient to attacks, because insurance companies consider their implementation as good practices and in some cases, it is a criterion to reduce the premium to be paid by companies with one or both certifications.
These links can provide more information:
For more about ISO 27001 benefits, please see: