Start a new topic and get direct answers from the Expert Advice Community.
CREATE NEW TOPIC +Guest
The auditor focused your attention in a particular problem, the non-conformity raised. Developing a corrective action means finding the root cause(s) and eliminate it/them.
First you have to expand your mind by answering to the question why. Why did this nonconformity occur?
A team can brainstorm a set of answers. The answers are hypothesis about what can be behind the non-conformity. Hypothesis are theories not the truth. Then, the most promising theories are selected, and information is collected, or tests are made to eliminate the wrong ones and keep the good ones. Now, we know what is behind the non-conformity, we know the root-cause(s). A root cause is something that has a strong impact in the occurrence of the non-conformity, and it is something that can be managed. It is time to develop a solution, something that will remove or reduce the frequency of the non-conformity. More than one solution may be available, normally one is chosen based on cost, or effectiveness, or easiness or resistance.
For example, during an audit a nonconformity was raised because there were no evidences of performance of a quality control during the night shift.
Why there was no control at the night shift?
Because people:
After some investigation. For example, what shifts missed the records? Who worked on those shifts? What kind of training did they had? You may realize that they never had training (hypothesis 5 and 2) because they were admitted in a rush to answer to a surge in orders.
In this article you can find an answer to the question about the difference between a major and a minor non-conformity - Major vs. minor nonconformities in the certification audit - https://advisera.com/27001academy/blog/2014/06/02/major-vs-minor-nonconformities-in-the-certification-audit/
The following material will provide you with information about root cause analysis:
No, you do not need to memorize the standard for successful ISO9001 implementation. You study the standard and distill requirements to your processes and introduce or improve practices based on those requirements. People doing quality control do nor need to know that they are applying clause 8.6 and they treat non-conformities according to the standard without knowing that it is clause 8.7.
I think that the process approach can be a great help in doing this because it allows an organization to draw a model of how it works, a model that people can relate to. Then, it is easy to distribute ISO 9001 clauses over the model. The model stands as reference, it is what people know.
Please check this example:
The following material will provide you more information about the process approach:
To update the SoA considering your stated scenario, you need to:
After approving the updated risk assessment and treatment you can update the SoA accordingly.
This article will provide you a further explanation about SoA:
For common risks and safeguards related to working remotely, please read:
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/