Answer: There is no specific template, or section in the templates, covering the definition of roles and responsibilities because these are described all along the documents. Please note that any time that there is an action to be performed there is also an associated field called [job title], or similar, identifying who should be responsible for that.
Selection of internal auditors
Nosotros tenemos un comité de implementación (quien lleva la implementación) y estamos en la fase de verificación de los controles implementados.
Mi consulta es si las auditorías internas nos corresponde hacerlas nosotros o personal externo especializado en el tema.
(Our institution is in the process of implementing the NTP-ISO / IEC 27001: 2014 (it is the Peruvian Technical Standard that adopted in ISO 27001: 2013).
We have an implementation committee (who is implementing) and we are in the verification phase of the implemented controls.
My query is if the internal audits we are required to do by us or external staff specialized in the subject.)
Answer: According to ISO 27001, clause 9.2 e), to select internal auditors you only have to ensure objectivity and the impartiality of the audit process, and for doing this you can either use external staff or organization's staff that is not direct ly involved in the process being audited (an auditor should not audit his own work).
Documenting actions to address risks and opportunities
Answer:
ISO 9001:2015 does not require action plans for addressing risks and opportunities and it is not required for the actions or their planning to be documented.
All the standard requires is to identify risks and opportunities and plan actions to address them, it doesn't require any document to be created. However, it is usual to make some records about risks and opportunities and actions for addressing them simply because it is easier to monitor accomplishment of the actions and their effectiveness.
On the grounds of documenting risks and opportunities or actions for addressing them, certification auditor can only issue you recommendations but he or she cannot issue you n onconformity.
Answer:
These techniques are related to problem analysis. There are many techniques und usual ones (beside mentioned pain value analysis, pereto and Kepner and Tregoe) are:
- chronological analysis
- brainstorming
- 5-whys
- fault isolation
- affinity mapping
- hypothesis testing
- technical observation post
- Ishikawa diagrams
Answer:
Implementing a tool always require multidimensional approach.(see the article to find out more "5 things to beware of when selecting an ITSM tool" https://advisera.com/20000academy/blog/2016/03/08/5-things-to-beware-of-when-selecting-an-itsm-tool/).
However, major IT equipment vendors have tools supporting asset management functionality.
Analytic companies (like e.g. Gartner) also do analysis.
Asset management is usual part of most of the IT Service Management tools, so that provides you with more choice.
Regarding ISO standards, I'd recommend ISO 31000 (Risk management) and ISO 31010 ( Risk management — Risk assessment techniques). These will provide you a wider view of risk management that can help you with IT risks not necessarily related to information security.
Clause 8.1 have general requirements for process control and document information required are applicable to all process in the QMS (Quality Management System).
First, the standard requires organization to determine and keep documented information to extent necessary to have confidence that the process is carried out as planned. This means that you need to determine what processes and activities need to have documented procedures or wok instruction or any other document that will describe how the process or activity is conducted. The key phrase here is "to extent necessary", this means that you don't have to document all processes or all activities but rather those that are complicated, or rarely performed so there is a greater chance of nonconformity occur rence. Example of such document are production procedures, quality plans, etc.
The second requirements is to demonstrate conformance of products and services to their requirements, this is usually record of quality control or quality inspection performed on the end of production process. This can also be approval for shipment or delivery.
One definition of quality assurance is: all the planned and systematic activities implemented within the quality system that can be demonstrated to provide confidence that a product or service will fulfill requirements for quality.
Quality assurance (QA) is a way of preventing mistakes or defects in manufactured products and avoiding problems when delivering solutions or services to customers; which ISO 9000 defines as "part of quality management focused on providing confidence that quality requirements will be fulfilled". This defect prevention in quality assurance differs subtly from defect detection and rejection in quality control, and has been referred to as a shift left as it focuses on quality earlier in the process.
The terms "quality assurance" and "quality control" are often used interchangeably to refer to ways of ensuring the quality of a service or product.