Answer:
ISO 9000:2015 defines nonconformity as the non-fulfilment of a requirement. Your NCR should record information about the occurrence of the nonconformity (day, hour, product, type of nonconformity, decision about the action to treat the nonconformity, responsible for the decision and when the decision is correction of the product, verification of effectiveness in the elimination of the nonconformity?
It is not mandatory to have the same kind of form to record all nonconformities. For example, I worked with a bottling company, there was a line operator that checked if labels in the bottles were correctly fitted and not stained. When there was a nonconformity, he removed the bottle from the line and made a mark in the product ion records. The occurrence was recorded without mentioning the action because the action was standard.
It is not mandatory that every nonconformity generates a corrective action. Corrective actions require an investment in searching the root cause(s) of the nonconformity and, sometimes, nonconformities are not serious enough to justify the investment.
After solving a nonconformity, your organization should ask: is this type of nonconformity serious enough or frequent enough to require a corrective action?
ISO 9000:2015 defines corrective action as the action to eliminate the cause of a nonconformity. Most of the time, causes are not obvious, it is needed to investigate and make trials to determine and verify the root cause(s).
The following material will provide you information about nonconformities and root causes:
Advisera's ISO 27001 Lead Auditor Course provides you the basics of risk management - how to identify assets, threats, vulnerabilities, calculate the level of risk, choose controls to mitigate risks, create reports, etc. It does not cover specific threats like manpower life threats although he does provide a couple of real-life examples using difference threats and vulnerabilities.
Answer 1: Although in the previous version of ISO 27001:2005 the preventive actions were included explicitly, in the current ISO 27001:2013 it is not referenced, so we don’t have a template for this anymore, because basically it is not necessary
2.- Also I've got one question about the Risk Assessment: Is it necessary to add the serial number for each computer/laptop inside the company or can I just name the asset and the owner?
Answer 2: From my point of view, the serial number of each computer/laptop is not relevant for the risk assessment, so you don’t need to include this information in the risk assessment, but for your asset management can be very interesting to have a control of the serial number of each equipment, because each equipment (with his serial number, that is unique), will be assigned to a specific person. So, you can include this specific information in your asset inventory.
I really thanks for your reply and got answer for root cause analysis
Data processing agreement
Answer:
Based on your description both you and the company that would hire the seafarers are acting as independent controllers. Except for the instance where the hiring company would provide you with the data of somebody for you to contact and interview on your behalf.
In the independent controller scenario, although is not strictly mandated by the GDPR, you could have a Controller to Controller GDPR Addendum (we are working in developing such a template) and for the scenario where you would be a processor, the hiring company would most likely ask you to sign a Supplier Data Processing Agreement similar to the one in our EU GDPR Documentation Toolkit ( https://advisera.com/eugdpracademy/eu-gdpr-documentation-toolkit/ )
Segregation duties
Answer: I am sorry, we don’t have a template for the segregation of duties, because this is not a mandatory document according to ISO 27001. Anyway, to implement this control, basically you need:
1. Identification of functions that are indispensable to the organization’s activities
2.- Division of the function into separate steps
3.- Definition of one or more segregation principles to be applied to the functions
1) Is it possible for someone who doesn't have a certificate to be an auditor? Is experience enough?
2) Can a company without ISO certificate conduct an ISO process or help another company / business to be ISO certified? Isn't a legal issue?”
Answer:
It is up to the client of the audit to specify the requirements of competency to be an auditor. Different clients will have different requirements. Interestingly, the last version of ISO 19011 removed competency requirements from the auditor definition.
There is no legal issue involved. A company without ISO certificate can help a company / business to be certified. Naturally, a certified company con argue commercially that it has first-hand experience of the process.
The following material will provide you information about internal audits:
There is no universal answer. In the past, I advised some companies to do precisely that, to have a particular internal audit with EMS documentation as the scope of the audit. Can be useful, particularly during the implementation phase or afyer several problems with documentation control.
The following material will provide you information about internal audits:
Answer: From my point of view, the part that takes most time is the risk assessment & treatment, because it is also the most complex and most important part. Remember that the main objective of ISO 27001 is the protection of information, identifying risks and treating them.
thank you for your response, I agree with your comments; however, I am of the opinion that before deciding on the encryption key length whether 128, 512 or etc an assessment should be performed