Start a new topic and get direct answers from the Expert Advice Community.
CREATE NEW TOPIC +Guest
ISO 27001 does not prescribe how to document your information security policies, so organizations are free to document them as they see fit.
The general practice is to have information security policies as internal operational documents, and including only references to them in contracts, as contractual clauses.
This article will provide you a further explanation about documenting policies and developing employment contracts:
After the warranty complaints are received by the dealer if the problem is part of the warranty scope and is not related to end-user (driver/passenger) error; the subject and the faulty part should be forwarded to the relevant automotive OEM company. Especially if it is an issue related to faulty part driver and vehicle safety than much faster reaction must be shown.
Depending on the situation, either a part replacement or temporary vehicle supply is provided. According to the investigation result of the OEM company, the customer must be answered in writing.
Generally, this process is carried out by departments such as after-sales services, etc
IATF 16949 rules have no defined time frame for the transition from ISO 9001:2015 to IATF 16949:2016. When the organization is ready according to IATF 16949:2016, it must take the stage 1 audit and, if the result is ‘’ready’’ then to start stage 2 audit, which is the main audit within 90 days after stage 1 audit. In my experience, a firm that effectively implements ISO 9001: 2015 says it will be ready for the IATF 16949: 2016 audit, with 6 months of work.
For more information, this article might be useful:
According to the IATF 16949: 2016 standard, any documented information should be under control. As you know, the documented information, all kinds of records such as procedure, instruction, control plan, processes, training records, job descriptions, etc.
My advice is, create a form number, revision number for the to-do list so that everyone in the organization can use the same to-do list.
Thus, the to-do list becomes a controlled document.
SO 27001 does not provide specific controls for cloud computing, but you can adopt and adapt some of its controls for cloud computing.
For example, you can use control A.8.3.2 Disposal of media (which states that media must be disposed in a secure and formal way when no longer required), considering that virtual machine as a "media".
For specific recommendations about cloud computing, you can consult ISO 27017 and ISO 27018, which provides specifics applicable to cloud computing regarding controls from ISO 27001 Annex A.
These articles can provide you more details on data disposal in ISO 27001:
These articles will provide you a further explanation about ISO 27017 and ISO 27018:
Training on ITIL covers some topics related to information security that can provide evidence of competence that can help achieve ISO 27001 compliance.
These articles will provide you a further explanation about competences, ITIL, and ISO 27001:
This material will also help you regarding competences on information security:
ISO 27001 does not prescribe how to test a Disaster Recovery Plan, so organizations are free to use the approach that better suits them, provided they can show evidence that the plan is fit for purpose.
This article will provide you a further explanation about testing a DRP (although it is about ISO 22301, the same concepts apply to ISO 27001):
This material will also help you regarding a DRP:
Thank you for your answer.
ISO 9001 can be useful for a Quality Analyst to develop a management view about how an organization works, that way it can be useful for evolving for other positions in an organization. It can be a way of moving from a technical to a management position.
The following material will provide you more information: