Answer: Basically you have to ask questions based on standard's requirements, to identify if they are being meet or not.
For example, for requirements such as "The organization shall determine...", the question should be "Did the organization determine...". For requirements such as "The organization shall consider", the question should be "Did the organization consider...", and so on.
This simple questionnaire will help you and your client to visualize which specific elements of a information security management system he has already implemented, and what he still needs to do.
EU GDPR questions
2. How long do we keep the log files for? Also if an unmanaged customer stops the service and asks for deletion of all data and the vps ( I guess we are obliged to delete everything but if that customers was dealing in unlawful activities and the police asks for information we won’t have any to give. (hoe does this work?)
3. If a customer complains about a bridge on their website that is handled by them on a shared hosting platform are we required to have tools that will identify such bridge and from where it came from? Now we use tools to prevent this from happening such as brute force attacks, sql injection etc…
4. Just to add further the data we ask and keep for Billing purposes for the customers is as follows:
Company Name, Contact Name, Address, V.A.T number, Email address
We use the above only for billing and email them for maintenance and invoices. Are the above considered Personal data as all this c an be found on their website? We don’t provide this info to 3rd parties.
Answers:
1. All documents except for the ones in folder 4 “Managing Data Subject Rights” can be used by both processors and controllers so we strongly suggest you go through all of them. Also, there is a document called List of Documents EU GDPR Toolkit where you can find out which documents are mandatory according to the EU GDPR.
2. Regarding the retention period the EU GDPR in article 5 - Principles relating to processing of personal data (https://advisera.com/gdpr/principles-relating-to-processing-of-personal-data/) states that personal data shall not be kept for “ longer than is necessary for the purposes for which the personal data are processed” this means that controllers have to delete the data once is no longer needed for processing unless there is a specific legal requirement that allows them to keep them for longer ( e.g regulatory compliance). As far as your activity as a processor goes the retention periods should be defined by the controllers and communicated to you. If a manages services customer asks you to delete the data you need first to assess if you can comply with the request or not by assessing the local legislation and if there is no reason to hold on to the data for longer you can delete it.
3. Your platform should be designed to prevent and detect data breaches. However, if the data breach originates from a customer is the duty of the customer to detect an report the breach when necessary (EU GDPR article 33 - Notification of a personal data breach to the supervisory authority - https://advisera.com/eugdpracademy/gdpr/notification-of-a-personal-data-breach-to-the-supervisory-authority/; EU GDPR article - Communication of a personal data breach to the data subject - https://advisera.com/eugdpracademy/gdpr/communication-of-a-personal-data-breach-to-the-data-subject/) . If the customer has a breach on their website is their duty to deal with that and notify the appropriate entities, you however, if acting as a processor might be required to assist.
4. The contact name and email address (provided it belong to an individual) on invoices are personal data. Usually invoices have to be kept by companies for regulatory compliance for periods up to 15 years. You should check your local legislation (usually the Tax Code) to see which is the retention period for invoices .
The identification method used in cases of DSARs depends on various factors such as the information you hold about the data subject as well as how the DSAR was received.
For example, if the data subject sends the request via email and the email is already in your database as it was provided by the data subject you can safely assume that the data subject is the one sending the email. If you receive the request via telephone you can just ask the data subject some ID verification questions same as banks do such as ( the last recorded address, the social security number, etc.).
One easy way is to establish a set of identification questions to be used to check the ID of the data subjects whenever a request is received. If the request comes form another person then the data subject you need to ask for a authorization from the data subject by which he empowers anoth er party to submit a DSAR on his/her behalf.
To learn more about how to handle DSARs you can book a seat at our webinar - Data Subject Rights under the EU GDPR - https://advisera.com/eugdpracademy/webinar/data-subject-rights-under-the-eu-gdpr-free-webinar-on-demand/
You can also check out our EU GDPR Foundations Course https://advisera.com/training/eu-gdpr-foundations-course/
Procesos y procedimientos
Respuesta: De acuerdo a la filosofía de ISO 9000, un procedimiento es una forma específica para llevar a cabo un proceso, por tanto no hay mucha diferencia con respecto a los procedimientos, por lo que podrías usar el artículo que comentas para implementar procesos.
Would we have a scope of entire organisation, but exclude physical management and operation of the Helpdesk/Monitoring system and ensure some sort of ISO compliance from the Datacenter provider. I assume we would then write policy for our staff access to Datacenter/Helpdesk and Monitoring and have defined roles ?
Answer: I'm assuming that by excluding physical management and operation of the Helpdesk/Monitoring system you are referring to focus only on using the Helpdesk/Monitoring system (like a Software as a Service - SaaS).
Considering that, for the relation with the datacenter provider you should consider a service agreement, establishing clauses to ensure it will apply the security controls you require for your business (e.g., based on ISO 27001 and ISO 27017). These clauses should cover not only the policy for your staff to access the Datacenter/Helpdesk and Monitoring system and necessary roles, but also refer to other controls, like your right to audit the provider operation and receive periodic performance reports.
Answer: We provide documentation toolkits to support implementation of ISO 27001, and included in the toolkit you can schedule meetings with one of our experts so he can help you overcome potential difficulties. Additionally, you can send filled documents for review, and we will answer with orientations on how to improve them so they can become ISO compliant.
3- And, is there any common knowledge on the cost?
Answer: There are a significant number of variables to be considered when estimating an implementation cost, so without more detailed information it's not possible to precise a value. What I can tell you are some cost issues you should consider:
- Training and literature
- External assistance
- Technologies to be updated / implemented
- Employee's effort and time
- The certification process
Answer: I'm assuming you are referring to the ISO 27001 Lead Auditor certification. Considering that, a certified lead auditor can audit a company to verify if it is ISO 27001 compliant, but only audits performed by auditors in the name of certification bodies are considered valid as a formal recognition that an organization is ISO compliant.
Answer: In general way, the benefits of ISO 27001 are related to:
- Enhanced competitive edge
- Reduction on losses due to security incidents
- Reduction on fines due to legal or contractual non conformity
- Improvement of internal organization
Answer: I'm assuming you are referring to ISAE 3402, an assurance standard. Considering that, you must first evaluate your needs regarding compliance to legal requirements (e.g., laws, regulations and contracts). If you need to comply with multiple legal requirements, then ISO 27001 has a more comprehensive approach (it requires you to identify, evaluate and treat all requirements that can impact your organization in terms of information security, while ISAE 3402 focus on documenting that an organization has adequate internal controls, generally approached from a financial perspective).
Answer: It is perfectly possible to combine ISO 27001 and ISO 9001 internal audit processes, since both standards have a lot of requirements in common (the requirements for internal audit in both standards are practically the same).
2. Is it mandatory for the author of the security policies and procedures to have appropriate trainings? Shall he/she be an internal certified auditor?
Answer: ISO 27001 requires that people with roles in ISO 27001 must have proper competencies, which can be fulfilled by means of training, education or experience, so it is not mandator y for the author of security policies to have related trainings, if he can demonstrate by other means (e.g., experience) that he has the necessary competence to elaborate the polices. The same applies to the need for an certified internal auditor.
3. Where shall I document the applicable legislation for the company?