Based on the description you would most likely be a data processor and the universities would be the data controllers. There is no specific toolkit version for the data processors because most of the documents are relevant for both controllers and processors. There are some documents that may be less relevant to processors such as the documents related to managing data subjects rights in folder 4 of the EU GDPR Consultation Toolkit.
However, consider that f you are established in the EU you will be a controller as opposed to the data of your employee s.
1. Is it necessary to request the express consent of the interested party for the transfer of data?
2. Is it sufficient to inform that the data are advanced and at the end of the clause request the express consent for the corresponding purpose?
One of the most common and easy to use safeguards are the “Standard contractual clauses” or “Model clauses” which need to be singed by the data exporter and data importer. These standard documents can be found in folder 6 of our EU GDPR Documentation Toolkit.
So, in a nutshell if you use the “Standard contractual clauses” as a safeguard the consent is not needed but the information ab out the intended data transfer needs to be included in the “Privacy Notice”.
>Thanks a lot for the support. I read it, but it dosent have answer to points 1to3. Request you to help me with the first 3 points mentioned my questions.
>
>I would like to know what I should keep in content of these? Or like share samples if possible.
Answer: The content of policies and procedures related to information transfer, log on and log off, and publication of public information shall depend of the relevant risks identified in your risk assessment, and legal requirements applicable to your organization, so there isn't a definitive answer for your question.
ISO 27002, a supporting standard for implementation of ISO 27001 Annex A controls can provide you a comprehensive set of guidance's and recommendations that you can use to tailor your documents. You should consider at least these controls:
- 9.1.1 Access control policy
- 9.4.2 Secure log-on procedures
- 13.2.1 Information transfer policies and procedures
- 13.2.2 Agreements on information transfer
- 13.2.4 Confidentiality or non-disclosure agreements
I know have a better understanding of the 'Assets' that should be recorded in the risk register, you did answer a question yesterday for me about listing every server and you suggest to group them together.
So, if I have an asset of a 'Database Server' on the risk register, what would I put in the 'Information Asset Inventory'? I was thinking of then breaking it down to the different applications that use the database server, does that sound correct?
Answer: In the 'Information Asset Inventory' you must include all assets you identified in your risk register. Since the standard doesn't define to which level of details the assets need to be described in the Inventory of assets, you can list servers in general or not only the 'Database Server' but also all the different applications that use the database server that you have identified in your risk register.
"Risk assessment is a crucial step in Information Security Management System (ISMS) implementation because it tells you the following: you should implement security controls (safeguards) only if there are risks (potential incidents) that would justify that particular control. In other words, the higher the risk, the more you need to invest in controls; but, on the other hand, if there are no risks that would justify a particular control, then implementing it would be a waste of time and money"
Answer: Controls from ISO 27001 Annex A 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., laws, regulations, contracts, etc.) that require the implementation of the control
- There is a top management decision requiring the implementation of the control
If none of these occurs there is no need to implement a control considering ISO 27001 requirements.
Answer:
The requirements for product safety are directly related to your product. If you have a product with hazards (such as a battery with a hazard of shocking someone while using it) then you need to identify these hazards and decide what needs to be done (such as warning labels, protective covers, etc.) If your product does not have any safety hazard then you could simply demonstrate that this has been assessed and therefore no actions are required.
Continual improvement is the incremental, planned changes that you implement to make things better in your organization (as opposed to continuous which means everything is improving all the time). This is to be applied to your products and service and the QMS to meet customer needs and enhance customer satisfaction (clause 10.1) as well as looking for opportunities to improve other aspects of the QMS not directly related to customer requirements or satisfaction (clause 10.3). In many ways one of t he biggest ways that a company demonstrates continual improvement is through the use of we planned quality objectives which give a target for improvement and follow through on plans to achieve them.
The other is ceramic dielecric powder company (ISO9001) who designs product for the customer. This company does provide SDS with the shipments.
Will the auditor be reviewing SDS during the audit based on "statutory and regulatory requirements"?
Answer:
This is something that has two answers, and they are the same for AS9100 Rev D and ISO 9001:2015.
First when it comes to having SDSs for the chemicals and materials that are used within the company comes under “Environment for operation of processes” (Clause 7.1.4). If these SDSs are required in your country to have in order to use the chemicals you must therefore have them to perform your processes. This was also previously the case in the last standard under clause 6.4 for “work environment”. If you needed to have these in place to perform your process then it is a resource that you needed to have and was therefore auditable.
Secondly, if you are creating a chemical that requires an SDS to be sent with it, then this is a requirement of your product. Therefore, it falls under the standard in clause 8.2.2 “Determining the requirements for products and services”. If there is a requirement that you need to meet and are not doing so this could be an audit nonconformance. Again, in the previous version of the standards this was also a requirement in clause 7.2.1 “Determination of requirements related to the product” where it also stated that you shall determine statutory and regulatory requirements applicable to the product.
So, this has really not changed. The auditors could have reviewed SDS during an audit against these requirements. That being said, just because an auditor can look at one aspect of a process does not meant hat they will.
Gender and date of birth
Title (Mr/Mrs/Ms etc)
Date of Birth
Gender
Are any or all of these classed as “Sensitive Personal Data” ? What extra precautions do we need to take for these?
Answer:
Gender and date of birth are not sensitive personal data as per the definition provided by the EU GDPR, there are no extra precautions needed.
We are located in Eindhoven - NL. Our primary business is providing a SAAS solution, we work with an 27001 certified hosting partner.
Answer: I'm assuming you are referring to certification bodies instead of auditing agencies. Considering that, we do not know Netherlands market in details to recommend specific certification bodies, but you should consider these references:
- SGS https://www.sgs.nl/en
- BSI https://www.bsigroup.com/nl-NL/
This website stores cookies on your computer. These cookies are used to collect information about how you interact with our website and allow us to remember you. We use this information in order to improve and customize your browsing experience and for analytics and metrics about our visitors both on this website and other media. To find out more about the cookies we use, see our Privacy Policy.
If you decline, your information won't be tracked when you visit this website. A single cookie will be used in your browser to remember your preference not to be tracked.