Answer:
The best way to avoid nonconformities is performing demanding internal audits and preparing auditees to be open and cooperative during those internal audits. Give them training and make them partners in improving the quality management system.
Remember having minor nonconformities in the certification audit is not an obstacle to getting certification.
Lean thinking in combination with ISO 9001 can help organizations to improve their processes within the quality management system by identifying and removing waste from the processes. The most used tools and principles among companies are value stream mapping, 5S, lean metrics, and takt time
Their integration can provide an better value for organization and your customer, but also a good return on your investment.
1. Confidentiality level mandatory on each document?
Answer: The label displaying confidentiality level is mandatory only if control A.8.2.2 Labeling of information is applicable to your ISMS, because of results of risk assessment, legal requirements, or top management decision.
2. Confidentiality Statement for Employees: [name of contract on the basis of which the person will have access to confidential information], is this the employment contract?
Answer: This information can be in the employment contract for regular employees, but also can be on a service agreement for temporary employees. This situation must be considered on a case by c ase basis.
3. Do I also have to list the records and / or appendices in the 'Statement of Acceptance of ISMS Documents' ?
Answer: You have to make reference to all documents you want the person to state acknowledge to. For example, if the Backup policy is not referred on the 'Statement of Acceptance of ISMS Documents' the person cannot be held responsible for not complying with it.
< 4. Control A.11.2.1 Equipment siting and protection: I assume this does not include the work laptops of the employees, this only includes network and system architecture, right?
Answer: This control includes all equipment included in the ISMS scope, even work laptops of the employees. The mobile nature of laptops may also require additional controls related to security off-premises, but protection on premises is mostly accomplished by control A.11.2.1.
5. List of legal, regulatory, statutory and contractual requirements:
a) Do we have to document all the employment contracts, NDAs, SLAs, etc...?
Answer: Contracts normally have clauses establishing rights and duties regarding information security, and in these cases they must be documented.
b) Also, to be ISO 27001 certified, we don't have to be compliant with GDPR as an example right?
Answer: If you have to comply with some law or regulation that defines information security requirements related to your ISMS scope, then you need to be compliant with them to become ISO 27001 certified. For example if your ISMS scope handles EU citizens personal data, then you have to be compliant with EU GDPR Article 32.
How can I do it? Should I define this in the scope document as an exclusion or maybe I should not mention it at all (I mean that I will only mention a department which works with the serviceA in the „Organizational Units“ section)? I understand that I will have to assess the risks that the serviceB may cause and I will mitigate them with some policy (Acceptable Use, Access Control) and also some technical controls.
Also a similar situation could be like this: a department consists of 10 employe es. Only two of them work with the serviceA (which is in scope). Can I include only those two? And how to do that? What exactly should be defined in the „Exlusions from the scope“ section of the ISMS Scope Document? Is it something that we cannot control but it affects the security? What I want to emphasize by asking this is why should we define exclusions – maybe we do not need to exclude anything since it is not included in the scope?
Answer:
You should only use the "Exclusions from the scope" section to explicitly define elements that are inside your statement of scope but you do not want the ISMS to handle them. If you can make this separation when defining the scope, there is no need to define exclusions.
A good example is your department scenario. You can define only the two roles that have access service A as part of the ISMS scope (in this case there are no exclusions), or you can define your department as a whole inside the ISMS scope and include the roles that do not need access service A as "Exclusions from the scope".
Considering your other scenario, if service B is completely unrelated to, or can be easily separated from, service A, there is no need to mention service B as "Exclusion from the scope". On the other hand, if service B is part of service A, then you should include service B on "Exclusions from the scope" so your ISMS does not need to manage it.
On both cases, to keep the document as simple as possible we suggest you to make the necessary separation when defining the scope.
Answer:
Your dilemma is not uncommon when there is a split of functions between facilities. The final decision will come down to the customer requirements placed on you; if they are only for manufacturing the this is acceptable, but not if the customers are expecting engineering to fall under the same aerospace requirements. If your customers are not requiring AS9100, then the decision of how you apply the standards becomes more up to you since you will have different scopes and then treat the other facilities as suppliers into your processes.
The difficulty comes in your scope definition. Many of the additional requirements in AS9100 Rev D are manufacturing and product related, but not all (for instance, some are design and purchasing relat ed). You will need to justify why these non-manufacturing requirements are being excluded form your AS9100 scope when they are actually done for your company, especially if some of the design verification occurs in your manufacturing facility (such as building prototypes).
One final thing to consider is the difficulty in performing common processes (such as internal audit and management review) if you have different scopes in different facilities. You will likely end up duplicating these processes which can end up costing you more than the separate scopes save. Unless the facilities function completely separately from each other, having different scopes can be difficult and time consuming. I would often recommend against it.
2. ¿Cada cuanto se debe Renovar?
3. ¿Quien Certifica en Norma ISO 14001?
Respuestas:
1. El coste de certificación va a variar dependiendo del país en que se encuentre. Le recomiendo que se ponga en contacto con varias entidades de certificación independientes que le pedirán una serie de datos para la elaboración del presupuesto.
2. La certificación normalmente se realiza cada 3 años. Aunque existen las llamadas auditorías de control que verifican el mantenimiento del sistema de gestión ambiental cada año y que incluyen únicamente partes del sistema.
3. La certificación de la Norma ISO 14001 se lleva a cabo por parte de una entidad certificadora independiente, que verifica que efectivamente la empresa, producto o servicio cumple con los requisitos de la norma. Le recomiendo que lea este artículo (en inglés) que le permite elegir a la mejor entidad certificadora - How to choose a certification body for ISO 14001: https://advisera.com/blog/2021/01/11/how-to-choose-an-iso-certification-body/
It is not relevant how your company name your documents as long as you comply with ISO 14001:2015 requirements, in this case with the requirements of clause 9.1. of the standard.
Auditing company manufacturing wood and plastic products
Answer:
In my answer, I will just focus on what is specific of that manufacturing company: wood and plastic products.
I would consider the life cycle of those materials. Does the wood come from certified forests? Does the wood include recycled wood? Does recycled wood come from operators with a permit? Does the organization buy recycled plastic? Does recycled plastic come from operators with a permit? Does the organization reuse plastic and wood?
The same exercise can be made based on the environmental assessment of aspects and impacts and risks and opportunities, and on the legislation and regulation applicable.
Answer: Each of the EU branches of your organisation should have in place a Controller to Controller Data Transfer Agreement with the US Headquarter (document 7.1 in the EU GDPR Documentation Toolkit).
2. What forms do our volunteers need to sign so we can transfer the data to them? I'm not finding something applicable in the templates we purchased. It would be a cross-border transfer to one of o ur volunteer members but we do not have a commercial agreement with our volunteers. Sometimes at events, our volunteers would be data controllers on behalf of the organization as well but I am specifically asking about data transfer from our headquarters to our volunteer leaders in the EU region, and our volunteers would contact the members directly on behalf of the organization.
Answer: The volunteers would act as your processor and should be treated as such. You would need to have a DPA in place (document 8.1 of the EU GDPR Documentation Toolkit) .
Applying ISO 14001
Answer:
Honestly, I see no difficulty for a health and environmental officer to apply ISO 14001 in his work area. Perhaps training in ISO 14001 foundations could be useful to learn the basics of the standard. After that, ISO 14001 is very project oriented and focused on improving or maintaining an organization’s interaction with the environment.