Start a new topic and get direct answers from the Expert Advice Community.
CREATE NEW TOPIC +Guest
"If we are coordinating a European project, and the data we collect is basic personal data (name, phone, email) from different EU city employees who take part in that project, are we, as a coordinator, responsible for how other project partners handle this data? i.e. the project makes us ensure that many partners also view this data (it wouldn't serve a purpose if we anonymize it) and then how can we control what the partner organisations do with this data, whether they delete it on time, etc.? so far we had a project document called DP management, where we would write down procedures, including that the data needs to be deleted after the project ends and so on.
You need to evaluate if your project partners process data on your behalf, you can be considered as the leader of the project, and therefore they will be seen as a data processor. In this case, you need to appoint them and determine procedures, controls, and require compliance with your policies.
Your partners may be seen also as a joint controller, under article 26 GDPR, if they determine with you the mean and the purposes of data processing. In this case, you can make a data processing agreement and determine jointly policies to follow. Each will be accountable for the data processed by its company.
Is this enough to show our accountability as coordinators?
If your partner is a data processor, you need to appoint them as a data processor with a data processing agreement. Article 28 GDPR requires a written legal undertaking. Of course, you can demand to follow your policies and rules and also control if they comply with it.
Here you can find more information
If you want to know more about GDPR compliance you can consider enrolling in this EU GDPR Foundations Course: https://advisera.com/training/eu-gdpr-foundations-course//
ISO 27001 does not prescribe that Nonconformities must be graded, so you can treat all of them only as Nonconformities in the internal audit. The use of minor and major Nonconformities are more used for certification bodies as a best practice.
Considering that, for certification purposes, you only need to ensure that any nonconformity is remediated by the time of the next surveillance/certification audit and that there is no recurrence of the same situation.
This article will provide you with a further explanation about nonconformities:
For further information, see:
Site preparation depends on the type of production you have for your medical device. If that is a sterile medical device, then a lot of attention needs to be on the cleanliness of the premises. It means for example: the separate entrance of the raw material and exit of the finished product, special rules for clothing and behavior in the facility (protective clothing and other equipment, not allowed to eat or drink in the production area).
If you produce a non-sterile device, then also there must be special attention to the work environment which is applicable for that kind of device.
If you produce software, rules for the work environment are less important, although it is important for the server room to have proper temperature and humidity.
In the warehouse, you need to have a properly labeled place for non-conforming products.
Other elements that cover site preparation mean that you need to have everything properly labeled, eg. shelves, lockers, locations in the premises.
For more information on this topic, please see the following articles:
The first requirement to obtain IATF 16949: 2016 certification is to manufacture for the automotive industry (Original Equipment Manufacturer ‘’OEM’’ or Original Equipment Service ‘’OES’’) and to fit the part on the vehicle. Sales organizations, distributors, dealers, etc. cannot deserve this certificate as they do not produce the parts.
I understand you are the sales organization and therefore you cannot apply for the IATF 16949: 2016 certification.
For more information, please read the following:
Unfortunately, we do not have that kind of article for the whole standard. However, the following articles can help you:
Yes, a medical device can do self-calibration, but this performance must be validated. Also, if it is applicable, self-calibration has to be explained in the instruction of use.
For more information regarding the validation and calibration, please see the following articles:
The purpose of a QMS is about having a planned way of working in order to deliver agreed products and services and enhance customer satisfaction.
A newly developed company can take advantage from a QMS through setting priorities, setting direction, establishing overall objectives and by planning what to do, how to do it with what resources. It also requires having indicators and monitoring and measuring performance.
Please check these articles about the benefits of implementing a QMS - Six Key Benefits of ISO 9001 Implementation - https://advisera.com/9001academy/knowledgebase/six-key-benefits-of-iso-9001-implementation/ and What are the benefits of ISO 9001 for your employees? - https://advisera.com/9001academy/blog/2016/06/14/what-are-the-benefits-of-iso-9001-for-your-employees/
The following material will provide you more information:
An auditor can formulate an idea about how an organization works with customer focus by collecting information about:
You can find more information below:
Article 37 GDPR states that the controller shall appoint a Data Protection Officer (DPO) when(a)the processing is carried out by a public authority or body;(b) the core activities of the controller or the processor consist of processing operations which require regular and systematic monitoring of data subjects on a large scale; or(c) the core activities of the controller or the processor consist of processing on a large scale of special categories of data pursuant to Article 9 (included health data).
Therefore, if your company process data on a large scale or there is regular and systematic monitoring of data subjects on a large scale (i.e. an app tracking Covid infections) you should appoint a DPO. You need to consider the scale of processing rather than the dimension of the company. Large scale is not defined by the GDPR, however, the former Working Party (a group study established the EU Commission) defined few examples of large scale (https://ec.europa.eu/information_society/newsroom/image/document/2016-51/wp243_annex_en_40856.pdf):
Here you can find more information:
If you want to know more about GDPR compliance you can consider enrolling in this EU GDPR Foundations Course: https://advisera.com/training/eu-gdpr-foundations-course//
1. Tough I would like to approach this topic from a more pragmatic and analytic way. I have seen on your website a categorization of ISO27k controls into organizational, technological, etc. on a pie chart so show with numbers. Could you please send me such a categorization which controls fall into which category?
Please note that this is not a definitive list, because other people can use criteria different for grouping the controls. Broadly speaking we have:
2. It would be also much appreciated if you could suggest on high-level which control main-or sub-chapters would you suggest to include as generally applicable for doing risk assessment for a Domain Controllers and a VPN gateway.
Since Domain Controllers and VPN gateways are technological solutions, controls from sections A.9, A.10, A.12, A.13. A.14, A.16, A.17 would be generally applicable for risk treatment. Please note that for risk assessment you can consider such controls as guidance to help identify potential risks (controls are not used during risk assessment).
3. Furthermore in case doing risk assessment for such infrastructure elements, would you suggest to include additional assets like administrators therein? Or even documentation, facilities, because that is also related to my above question, if we have around 30 organizational type controls, the evaluation of those could be more or less the very same way applied to all infrastructure elements or what would you suggest to avoid double work?
This we could also discuss personally in the course of the online expert support session offered, I am available for this purpose tomorrow or today afternoon.
In your risk assessment, you should include all infrastructure elements that can impact information security, not only technical equipment (e.g., human error on DC configuration may be a relevant risk for you, or lack of formal procedures may cause important records not to be registered).
During the assessment, what you can do to minimize rework is to assess how the risk related to these assets impacts the information security, not the DC or the VPN gateway.