Start a new topic and get direct answers from the Expert Advice Community.
CREATE NEW TOPIC +Guest
First is important to note that only ISO 27001 is a certifiable standard. ISO 27002 is a support standard which provides guidance and recommendations for implementation of controls from ISO 27001 Annex A.
Considering that, in a general way, after getting support for the certification (through approval of an ISO 27001 certification project plan) and approval of the Procedure for Document and Record Control, you should consider these for implementation:
This article will provide you a further explanation about ISMS implementation:
To see how documents compliant with ISO 27001 looks like, I suggest you take a look at the free demo of our ISO 27001 Documentation Toolkit at this link: https://advisera.com/27001academy/iso-27001-documentation-toolkit/
As for the shortest way to get ISO 27001 certified, it would involve hiring a consultant, because this approach will rapidly provide the knowledge, expertise, and methods to implement the standard, although it is the most expensive approach.
Other approaches that can be adopted are implementing the standard using your own employees (the cheapest and longest way), and implementing the standard with a DIY approach and using external know-how (a mid-term approach).
These articles will provide you a further explanation about implementation approaches:
These materials will also help you regarding ISO 27001 implementation:
In environmental management systems I’m always going back to the list of significant environmental aspects and impacts to renew the list of environmental objectives. Also, I try to connect environmental objectives with business objectives. For example, if an organization competes based on price what significant environmental objectives can best contribute to reduce costs?
Please check this information below with more detailed answers:
You can define the scope in terms of only the part of the organization (i.e. the Database), but in general, for small and mid-sized business, the best approach is to include the entire organization in the ISMS scope, because the effort to separate the scope for such organizations may not be worthy.
These articles will provide you a further explanation about the scope definition:
These materials will also help you regarding scope definition:
Patch management and vulnerability management would be best covered in A.12.1 - Security Procedures for IT Department, located on folder 08 Annex A Security Controls >> A.12 Operations Security since it involves change management.
This article will provide you a further explanation:
Você pode definir o escopo em termos de apenas uma parte da organização (ou seja, o Banco de Dados), mas em geral, para pequenas e médias empresas, a melhor abordagem é incluir toda a organização no escopo do SGSI, porque o esforço para separar o escopo para tais organizações pode não valer a pena.
Estes artigos fornecerão uma explicação adicional sobre a definição do escopo:
Esses materiais também irão ajudá-lo com relação à definição do escopo:
Once you have identified the disruptive scenarios you have to handle, broadly speaking, the development of a continuity plan based on ISO 22301: 2012 requires the development of:
These materials will provide you a further explanation about developing a continuity plan:
To see how a Business Continuity Plan compliant with ISO 22301 looks like, I suggest you see the free demo of our Business Continuity Plan at this link: https://advisera.com/27001academy/documentation/business-continuity-plan/
Thank you, Rhand!
The ISMS scope states the information you want your ISMS to protect, so what you want to protect (in your example data and application software) needs to be stated in the ISMS. The detail that it is located in a cloud solution can be kept to be stated during the Risk Assessment.
This article will provide you a further explanation about the scope definition in the cloud:
1 - My situation is that I am an intern at a small company whose servers are in the cloud (***), and they have a website of their own. So my question is implementing ISO27001 would be meaningless for such architecture, if not how should i define the context of the organization in such a case.
SO 27001 aims the protection of information regardless of where it is, so it is also applicable when the information to be protected is hosted in a cloud solution.
The definition of the ISMS scope when information is on a cloud solution will depend on the control you have over the cloud
This article will provide you a further explanation about defining a scope considering cloud models:
2 - Also what sources would help a beginner like me to achieve this implementation of the standard. By the way, I started the course online in advisera titled "ISO 27001:2013 Lead Implementer Course" is it a good start?
To help beginners to implement ISO 27001 Advisera provides several articles and downloadable materials the can provide guidance.
Additionally, I suggest you take a look at the free demo of our ISO 27001 Documentation Toolkit at this link: https://advisera.com/27001academy/iso-27001-documentation-toolkit/
This toolkit has the mandatory and most commonly used documents for an ISO 27001 implementation, and they include comments that can help to customize the documents to your organization's needs.
Regarding the Lead Implementer course, it is a good way to start an understanding of how to implement ISO 27001.
These articles will provide you a further explanation about ISO 27001:
These materials will also help you regarding ISO 27001: