We are being asked to fill in the "data exporter" during an agreement with a third party, and my understanding is that it should refer to our company name, but I want to be sure.
Answer:
The EU GDPR does not provide a definition for the “data importer” or the “data exporter”, nevertheless these definitions can be found in COMMISSION DECISION 2010/87/EU on standard contractual clauses for the transfer of personal data to processors established in third countries under Directive 95/46/EC of the European Parliament and of the Council.
According to article 2 of the abovementioned Decision:
- “data exporter” means the controller who transfers the personal data;
- “data importer” means the processor established in a third country who agrees to receive from the data exporter personal data intended for processing on the data exporter’s behalf after the transfer in accordance with his instructions and the terms of this Decision and who is not subject to a third country’s system ensuring adequate protection within the meaning of Article 25(1) of Directive 95/46/EC.
Regarding training - at least ISO 20000 Foundation is a dvisable. It will give you understanding of the standard's requirements and some hints how to approach the implementation.
First, there is no mandatory requirement to keep documented information about clause 4.2. That means, organizations are free to decide how to handle that clause. An organization can decide to answer clause 4.2 in a top management meeting record for example.
Second, although the Quality Manual is no longer a mandatory document under ISO 9001:2015, that doesn’t mean that an organization shouldn’t keep a document, called Quality Manual, or Organization ID Card, or by any other name, reuniting important information about the organization such as: Who we are, What we do, to Whom and with Whom do we work, in What we believe, How do we do it
Regarding big SaaS suppliers as the ones you mentioned, all of them have either Privacy Policies or Terms and Conditions that you most likely agreed on when purchasing the services. These documents regulate the processing activities between you and the suppliers.
These documents will be updated for sure to meet the requirements of the EU GDPR at least when talking about suppliers like Microsoft.
Nevertheless, the obligations posed on processors such as the ones mentioned in article 28 of the EU GDPR ( processor must not appoint a sub-proc essor without the prior written consent of the controller, processors must implement appropriate technical and organisational security measures to protect personal data, etc.) would still be applicable even if they are not mentioned in a contract or any other legally binding document.
If they don’t comply with the above mentioned obligations they would be facing fines form the competent Supervisory Authorities. You could also bring them to court it they failed to fulfill their legal obligations as regards to EU GDPR compliance and you suffered a loss as a result.
Moving to the small SaaS providers, these regardless of their size, should be compliant with the EU GDPR (assuming the GDPR applies to them based on art. 3 of the EU GDPR). For these suppliers you would need to have a signed Data Processing Agreement (DPA). The Supplier Data Processing Agreement can be found under folder 7 of the EU GDPR Documentation Toolkit.
Depending on the types and categories of personal data processed by one of these suppliers a Due Diligence process might be necessary. For the Due Diligence process the Processor GDPR Compliance Questionnaire, which can be found under folder 7 of the EU GDPR Documentation Toolkit, can be used.
Processing of publicly available personal data
Answer:
Regarding the processing of publically available personal data you would have to consider the fact that processing needs to be in line with the scope for which that data was made publically available by the data subject.
For example, you could get email addresses from LinkedIn and it would be fine to use those to contact the data subjects for recruitment purposes or to buildup a CV data base using the information fro m LinkedIn if you are a recruiting company.
However, if the email addresses were to be uses for marketing purposes this processing will most likely be unlawful unless you obtain the consent of the data subjects.
The issue regarding Whois is still under debate but most likely changes would follow such as granting access to the information on domain holders only for law enforcement agencies.
Interested parties
Answer: The way employees families should be considered will depend upon how they can impact, or be impacted by the organization's information security needs (you can determine that by identifying the organizational context as required by ISO 27001 clauses 4.1 and 4.2). Some examples may be:
- a family member using an employee's device (e.g., notebook, tablet, etc.) connected to organization's systems which may accidentally disclose sensitive information or install a malware
- a family member may be held hostage to force an employee to reveal organization's sensitive information
In both cases the organization may identify a real risk that should be mitigated and consider the implementation of proper controls.
These articles will provide you further explanation about context and interested parties identification:
- How to identify interested parties according to ISO 27001 and ISO 22301 https://adv isera.com/27001academy/knowledgebase/how-to-identify-interested-parties-according-to-iso-27001-and-iso-22301/
- How to identify ISMS requirements of interested parties in ISO 27001 https://advisera.com/27001academy/blog/2017/02/06/how-to-identify-isms-requirements-of-interested-parties-in-iso-27001/
Answer: I'm assuming that by the terms "Open source" and "License" you mean a firewall that is free of charge or paid .
Considering that, ISO 27001 is not prescriptive about how a firewall, or any other control, should be implemented, so organizations have freedom to choose the implementation that better fits its needs, provided that the solution is used in accordance with the license terms associated therewith (even open source firewall may have license terms that must be followed).
I don’t advise a change in audit procedures. I advise to continue to audit each department against to the requirements of all the clauses and internal documentation applicable. During the audit, you can check if important risks, based on actual performance, have been determined and acted upon. Risk based thinking is another way of promoting preventive actions in organizations.
The following material will provide you information about risk based thinking: