Validation means the confirmation, with objective evidence, that the requirements for a specific intended use have been fulfilled. Can your company show, for example, the results of tests that demonstrate validation?
Another approach is to consider that your organization only performs a final verification to put the products on a catalog and that validation is done with the customer, after the customization and final customer approval. Normally, I use customer final approval as a sign of validation.
The following material will provide you information about design validation:
First of all I would like to mention that cross border transfer refers to the situation where personal data is stored or accessed from outside the EEA. So in your case if the data is stored in UK but it can be accessed from the US than it is definitely a cross border data transfer.
Quality policy and quality objectives
Answer:
How does your organization wins its most desirable customers? What do they value the most? Are there relevant interested parties that help you win businesses? What do they value the most? The answers to these questions help you assess the strategic orientation of your organization.
When I work with the top management of an organization I follow this recipe:
Who we are and what is our business (for example, our business is not what we manufacture but the results that our customers get);
To whom do we work;
In what kind of challenges do we need to be the best;
And include the two commitments of the standard (continual improvement and meeting customer and regulatory requirements)
For example:
"Company name" is an industrial company specialized in comfort footwear.
We serve customers who need a supply of comfort footwear for professional uses.
In order to better serve our customers, we believe that we must seek to continuously improve:
Our ability to develop, to be able to respond quickly to requests for samples;
A language of product that differentiates us and supports the promise of comfort;
The ace card of being a manufacturer and being able to be faster and more flexible in production;
The fulfillment of our commitments.
Considering this example of quality policy, quality objectives can be:
Average time to finish a sample request;
Ratio of success of samples to target customers;
Ratio of complying with agreed delivery dates;
Ratio of complaints
Internal defects rate (number of defect per 1000 produced pairs)
Look how objectives allow you to monitor the promises made in the quality policy.
The following material will provide you information about quality policy and objectives:
2. Is a separate DPIA required each time this occurs? The spreadsheet provided as a template doesn't seem to speak to these events
Answers:
1. According to EU GDPR article 35 – “ Data protection impact assessment” (https://advisera.com/eugdpracademy/gdpr/data-protection-impact-assessment/) a DPIA is required if you are processing “personal data relating to criminal convictions and offences”. Although the EU GDPR also mentions that the processing activity would need to be on a “large scale” I would strongly advise you to perform an DPIA for background checking prior to employment.
2. You don’t need a DPIA each time you do a background check you can just mention the background checking as processing activity and this would cover all the cases you do a background check provided that you process the same data in a similar way.
Publishing Privacy Policy
Answer:
Based on your description bellow it does not make sense to publish the Privacy Policy on your website unless you use the website to collect data for example CVs for recruitment purposes or get data subjects to set up an account.
In the case above you just need to publish the Privacy Policy on your intranet for example.
Regarding DSARS these should come from the data subjects for which you are acting as controllers so you need to provide this information only to them. For example, in case of requests from your employees you can provide the information on your intranet. However, bear in mind that also former employees have these rights so the informat ion should be available to them as well so Intranet might not be sufficient in this case.
The antivirus protects data only as regards to certain types of threats usually external threats and this is hardly enough to prove that you are keeping the data safe.
However, is up to the controllers and processors to establish “appropriate technical and organizational measures” based on the types and categories of personal data they are processing as well as the purpose of the processing (obviously a Bank would nee to have more strict security measures than an online shop selling flowers). In our folder 8_Security of Processing in our EU GDPR Documentation Toolkit (https://advisera.com/eugdpracademy/eu-gdpr-documentation-toolkit/ ).
When I look at the SOA, it lists all of the Appendix A controls. My question is if the identified number of category 3 and 4 risks is low, then logically there will be a high number of SOA controls that do not apply and I would need to say “NO” in the Applicability column in the SOA table.
Answer: Your assumption is partially correct. If you have a low number of risks considered unacceptable, and that will require the implementation of security controls to be treated, then there is a great chance that for most controls in the SoA you will state them as non applicable. But you should note that controls may be required because of legal requirements (e.g., a law or contract), or because Top management decid ed for their implementation (by considering them as "good practice").
By the way, included in the toolkit you bought you have access to a video tutorial that can help you understand and fill the risk assessment and risk treatment templates.
Answer: The risk assessment report presents a brief explanation about the risk assessment methodology, the identified risks and those risks evaluated as unacceptable by the organization. The risk treatment report presents a brief explanation about the risk treatment methodology, and the treatments chosen to all risks the organization considered unacceptable, as well as to those the organization decided to treat based on other reasons (e.g., because of legal requirements or because it considers the treatment as a best practice).
Generally, the risk assessment and risk treatment reports are presented as a single document.
The statement of applicability presents a summary of which controls are necessary, the justification for their inclusions, whether they are implemented or not, and the justification for exclusions of controls from Annex A.
Answer: ISO 27001 does not specify the form of the scope, only the minimal information that must be considered in its definition:
- external and internal related issues related to the understanding of the organization and its context;
- the requirements of relevant interested parties; and
- interfaces and dependencies between the organization and other organizations.
Answer: Let's start with the differences:
- ISO 27001 Lead Implementer – this certification recognizes people who have competency on the ISO 27001 implementation process.
- ISO 27001 Lead Auditor – this certification recognizes people who have competency on auditing an ISMS against ISO 27001 requirements and want to become certification auditor (and with this provides more confidence to an organization for being certified).
So, the decision about which one to take will depend on your professional purposes. If you plan to work on an information Security Management System certification process, then you should consider the Lead Implementer certification. If you plan to ensure the operation of an ISMS, then you should consider the Lead Auditor certification.
Risks and opportunities and organizational knowledge
If you already have FMEA, you covered the risks for the main processes. All you need to do now is to identify risks for the rest of the internal (organizational structure, culture, competence of the employees, etc.) and external (legal requirements, competition, etc.) context and the opportunities. The easiest way to do this is to arrange a brainstorming session with the key people in the organization and make a list of risks and opportunities and to define actions to address them. All this information can be recorded in the same document and this can be sufficient evidence that you identified the risks and opportunities and planned actions to address them.
For more information, see: How to address risks and opportunities in ISO 9001
2) Organizational knowledge – what documents to support this clause 7.1.6?
This clause does not require any documented information, so you don't need to produce any additional procedures and records regarding it. Organizational knowledge is to some extent already documented through the organization's procedures and work instructions and the organization itself can decide to what level the knowledge of the organization should be documented.