Si ahora mismo su organización sólo quiere implementar una norma, en este caso ISO 9001:2015 sólo debe determinar el alcance para el Sistema de Gestión de Calidad. Si en un futuro decidiese integrar dicha norma con otras entonces debería definir el alcance para ese Sistema Integrado, y contar con un único alcance preferiblemente. También podría establecer alcances distintos para diferentes normas, pero no se lo recomiendo, ya que la integración sería muy compleja.
If you receive the data from the controller and you are acting as a processor, you need to only process the data based on the controller's instructions. So, if the controller does not instruct you to enter into contracts with the data subject you may be in breach of the Processing Agreement you have with the controller. Moreover, you may also have a non-competition clause in the commercial agreement with the controller forbidding you to “steal” the controller customers. Anyway is difficult to say unless I have all the details.
To find out more about what processors are allowed to do, check out this article: EU GDPR controller vs. processor – What are the differences? ( https://advisera.com/eugdpracademy/knowledgebase/eu-gdpr-controller-vs-processor-what-are-the-differences/ )
Answer:
The risk is about what can deviate your organization from expected results or what can promote the occurrence of undesired results.
Your company implemented actions to handle risks and opportunities (risks are negative deviations and opportunities are positive deviations) if you were able to meet the desired results and or avoid the undesired results your actions were effective.
2. What are the examples of continual improvement that can be implemented in my company 10.3
Answer:
Continual improvement is finding ways to make the quality management system more suitable, adequate, and effective in a planned and incremental way. Where you want to make your quality management system better, define a target for improving that process, and then make a plan and assign resources to make this improvement happen. For example, maybe your company want to improve the product development process; or to improve product or service specifications, or to improve new employee integration.
Answer:
Authority is about the power of decision, the power of command. Responsibility is about obligation. For example, an operator may have the responsibility to perform quality control and identify the nonconforming product (he or she has the obligation to do it, he or she is expected to do it), and may not have the authority to decide what to do with the identified nonconforming product.
>1 - We use the Microsoft Azure Public cloud heavily to provide Web Services to clients. One of my executives is asking if we can just include this platform in the scope and have the IT department that ‘interfaces’ with it as an ‘interested party’, therefore reducing the amount of work involved. Only the IT Department interfaces with this platform.
In summary, are we able to only include a ‘platform’ or does the scope have to include an organisational unit.
Answer: You can include cloud environments in your ISMS scope without problems, and the extension you have to include them in your ISMS scope will depend of the type of service you have:
- If you have an Infrastructure as a Service (IaaS) agreement, then software and data should be in the ISMS scope, while physical location and hardware are completely out.
- If you have an Platform as a Service (PaaS) agreement, then data and all application software should be included in the ISMS scope, while everything else is out, including all system software.
- If you have an Software as a Service (SaaS) agreement, then only th e data should be in the ISMS scope.
Regarding who will interface with the cloud provider, you can define the IT department without problem also.
>2 - Also, once I have ironed out the requirements of the scope for the meeting, how do I go about recording it efficiently? Am I best using a spreadsheet of some kind?
This document can help clearly define the boundaries of the ISMS fulfilling the requirements of ISO 27001 standard.
Application of BCP on ISO 27001
Answer:
Any control from ISO 27001 Annex must be applied only if one of the following occurs:
- There are risks identified as unacceptable in the risk assessment that require the implementation of the control
- There are legal requirements (e.g., contracts, laws, and regulations) that require the implementation of the control
- There is a top management decision requiring the implementation of the control
If none of these occur there is no need to implement any control considering ISO 27001 requirements, including BCPs.
So, considering your scenario, besides risks and contracts you should also verify if there are no laws and regulations applicable to your business requiring the implementation of BCPs, and the explicit intention of top management not to implement BCPs for ISO 27001.
To obtain a certification your organization has to hire an accredited certification body to perform the certification audit. And although price is an important criteria, you should consider other aspects like reputation, experience, and flexibility.
To help you find a certification body near your location, I suggest you to use this link: https://advisera.com/
Yes, as long as those documents are documented information that support the operation of processes you will need to register them. ISO 9001:2015 in clause 7.5 requires an organization to “Maintain documented information to the extent necessary to support the operation of processes and retain documented information to the extent necessary to have confident that the processes are being carried out as planned.”
Basically you will need to document, no matter what format you decide to use, the following:
- Documenting critical portions of the quality management system (QMS) such as its scope, key operational processes, policies, and objectives.
Documenting important, but less critical information that supports the QMS such as process flowcharts, specific quality and operational procedures, schedules, information collection approaches (i.e. forms, surveys), business plans, etc.